ICRA>D P^DI


VA FileMan 22.2


Select OPTION: PRINT FILE ENTRIES  

Output from what File: INTEGRATION REFERENCES//   (7646 entries)
Sort by: IA #// NUMBER
Start with NUMBER: FIRST// 
  Within NUMBER, Sort by: 
First Print FIELD: [CAPTIONED        
  
Include COMPUTED fields:  (N/Y/R/B): NO//  - No record number (IEN), no Computed
 Fields
Heading (S/C): INTEGRATION REFERENCES List  Replace List With Redacted List as o
 20261106
  Replace 
   INTEGRATION REFERENCES Redacted List as of 20261106
DEVICE: ;;999999999999  Linux Telnet / SSH
INTEGRATION REFERENCES Redacted List as of 20261106
                                                     NOV 09, 2026@17:23   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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4                               IA #: 4
  GLOBAL ROOT: XUTL(                    DATE CREATED: JUL 27, 1989
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  NAME: DBIA4-A                         ORIGINAL NUMBER: 4
  ID: XUTL(
GLOBAL REFERENCE: XUTL('ORUM'
 GLOBAL DESCRIPTION:   Used to store protocols menus so thy don't have to be
 rebuilt everytime .  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 5                               IA #: 5
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19,
  DATE CREATED: JUL 27, 1989            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA5-A
  ORIGINAL NUMBER: 5                    ID: DIC(19,
GLOBAL REFERENCE: DIC(19,...
 GLOBAL DESCRIPTION:   Used to access options and their fields.  ^ 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 6                               IA #: 6
  DATE CREATED: JUL 27, 1989            CUSTODIAL PACKAGE: 1
  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: 8                               IA #: 8
  DATE CREATED: MAR 15, 1990
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: OR1
  NAME: DBIA8                           ORIGINAL NUMBER: 8
  ID: OR1
 GENERAL DESCRIPTION:   KERNEL  6.5 USES/HAS INCLUDED  ADD^OR1 & AFT^OR1 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ADD
COMPONENT/ENTRY POINT: AFT
SUBSCRIBING PACKAGE: KERNEL (parent)    ISC: Oakland

NUMBER: 9                               IA #: 9
  DATE CREATED: MAR 15, 1990
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Other                           NAME: DBIA9
  ORIGINAL NUMBER: 9
 GENERAL DESCRIPTION:   KERNEL AND TOOLKIT USES VA NAMESPACE FOR ^VA(200,
 PERSON FILE.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: KERNEL (parent)    ISC: Oakland
SUBSCRIBING PACKAGE: TOOLKIT            ISC: Oakland

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: 14                              IA #: 14
  DATE CREATED: FEB 23, 1990
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         ROUTINE: GMRVUT0
  NAME: DBIA14                          ORIGINAL NUMBER: 14
  ID: GMRVUT0                           STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   Obtain vitals information.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY     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: Controlled Subscription
  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
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 4/23/24, effective with patches DG*5.3*1104 and
 PX*1.0*240 

NUMBER: 18                              IA #: 18
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA18
  ORIGINAL NUMBER: 18                   ID: SC(
GLOBAL REFERENCE: SC(D0,0)
FIELD NUMBER: 1                         FIELD NAME: ABBREVIATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Hospital Location file (44) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
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
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  ISC: Hines

NUMBER: 20                              IA #: 20
  DATE CREATED: MAY 07, 1987            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDACS
  NAME: DBIA20                          ORIGINAL NUMBER: 20
  ID: SDACS                             STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN3
 COMPONENT DESCRIPTION:   Used to enter clinic stops.  
SUBSCRIBING PACKAGE: REHAB MEDICAL SERVICES
  ISC: Salt Lake City

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 eligibility for Dental
 Care.  
FIELD NUMBER: 220.1
  FIELD NAME: DENTAL ELIGIBILITY EXPIRATION
  LOCATION: DENT;2                      ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The expiration 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
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 11/10/25 effective with Dispatch file 
 HS.Local.VA.HC.ServiceBroker.DispatchVDIFDental Request R/W w/Fileman access
 to fields, 220, 220.1.  

NUMBER: 22                              IA #: 22
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA22
  ORIGINAL NUMBER: 22                   ID: SC(
GLOBAL REFERENCE: SC(D0,'S')
FIELD NUMBER: 1900                      FIELD NAME: ALL
  LOCATION: S;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The following routines will use the ("S") sub-tree of the
 Hospital Location File to access Patients by clinic location (^SC(DO,"S"): 
    GMTSPL, GMTSPD, AND GMTSPNJ 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 23                              IA #: 23
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: JAN 18, 1990            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA23
  ORIGINAL NUMBER: 23                   ID: DPT(
GLOBAL REFERENCE: DPT('CN',
 GLOBAL DESCRIPTION:   Non-clinic locations, patients lists are generated by
 visiting the "CN" cross-reference of ^DPT( 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 24                              IA #: 24
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA24
  ORIGINAL NUMBER: 24                   ID: SC(
GLOBAL REFERENCE: SC(D0,'S',
FIELD NUMBER: 1900                      FIELD NAME: ALL
  LOCATION: S;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   ^SC(DO,"S" is referenced for Action Profiles 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 25                              IA #: 25
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG(
  DATE CREATED: SEP 18, 1989
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA25
  ORIGINAL NUMBER: 25                   ID: PSDRUG(
GLOBAL REFERENCE: PSDRUG(D0,0)
FIELD NUMBER: .01                       FIELD NAME: GENERIC NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Reference to ^PSDRUG, Read only to .01 field, drug name. 
 The data referenced is stored in pointer format in ^YS(615.2,
 Seclusion/Restraint.  
 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 EMAIL GROUP using
 Microsoft Outlook. Redaction applied since Retired.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Salt Lake City

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: 28                              IA #: 28
  DATE CREATED: MAR 21, 1989            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: DGUTL
  NAME: DBIA28                          ORIGINAL NUMBER: 28
  ID: DGUTL
 GENERAL DESCRIPTION:   *****TEMPORARY SUPPORTED CALL FOR IFCAP V2 TEST SITES
 ONLY***** 
                 call to ZIS^DGUTL 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ZIS
 COMPONENT DESCRIPTION:   DURATION:  Till completion of IFCAP, version 2,
 testing.  
SUBSCRIBING PACKAGE: IFCAP              ISC: Oakland

NUMBER: 29                              IA #: 29
  GLOBAL ROOT: DD(                      DATE CREATED: FEB 13, 1990
  CUSTODIAL PACKAGE: 1                  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: 30                              IA #: 30
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: NOV 14, 1989            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA30-A
  ORIGINAL NUMBER: 30                   ID: DPT(
GLOBAL REFERENCE: DPT(D0,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: .09                       FIELD NAME: SOCIAL SECURITY NUMBER
  LOCATION: 0;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.1)
FIELD NUMBER: .1                        FIELD NAME: WARD LOCATION
  LOCATION: .1;1                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.101)
FIELD NUMBER: .101                      FIELD NAME: ROOM-BED
  LOCATION: .101;1                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.103)
FIELD NUMBER: .103                      FIELD NAME: TREATING SPECIALTY
  LOCATION: .103;1                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.104)
FIELD NUMBER: .104                      FIELD NAME: PROVIDER
  LOCATION: .104;1                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.35)
FIELD NUMBER: .351                      FIELD NAME: DATE OF DEATH
  LOCATION: .35;1                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT('BS',
GLOBAL REFERENCE: DPT('BS5',
GLOBAL REFERENCE: DPT('CN',
GLOBAL REFERENCE: DPT('SSN',
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTO REPLENISHMENT/WARD STOCK
  ISC: Birmingham

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
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 03/22/21 for Mental Health's Suicide Prevention
 Project, patch YS*5.01*135.  

NUMBER: 32                              IA #: 32
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: NOV 14, 1989            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA32
  ORIGINAL NUMBER: 32                   ID: DPT(
 GENERAL DESCRIPTION:   Inpatient Medic ations will be referenceing the
 following files & fields: 
  
      FILE 2     401 ADMISSION DATE/TIME  subfile & all fields 
                   2 TRANSFER DATE/TIME     "           " 
                   5 TREATING SPECIALTY     "           " 
                57.1 HEIGHT 
                57.2 WEIGHT 
                53   REACTIONS 
                55   GENERIC DRUG subfile 
                57    ALLERGIES/DISORDERS subfile 
        X-REF    "AA","AD","AT" 
  
 EXPIRED AS OF THE RELEASE OF MAS 5 
  STATUS: Expired                       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: 34                              IA #: 34
  FILE NUMBER: 50.5                     GLOBAL ROOT: PS(50.5,
  DATE CREATED: JUN 10, 2003            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA34-A
  ORIGINAL NUMBER: 34                   ID: PS(50.5,
 GENERAL DESCRIPTION:   Direct references are made to the globals to get
 allergy information.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 35                              IA #: 35
  DATE CREATED: MAR 22, 1989
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Other                           NAME: DBIA35
  ORIGINAL NUMBER: 35
 GENERAL DESCRIPTION:   Variables VADM & VAIN are used when calling ^VADPT 
  
 Global ^DIC(16 is used to lookup person requesting orders and to print
 attending physician.  
  
 Routines OERR^VADPT & INP^VADP are used to get patient variables.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

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: 37                              IA #: 37
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: MAR 22, 1989            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA37
  ORIGINAL NUMBER: 37                   ID: DPT(
GLOBAL REFERENCE: DPT(D0,.101)
FIELD NUMBER: .101                      FIELD NAME: TREATING SPECIALTY
  LOCATION: .101;1                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,'PA',
 GLOBAL DESCRIPTION:   For patient allergies.  
GLOBAL REFERENCE: DPT(D0,'PI',
 GLOBAL DESCRIPTION:   For patient allergies.  
GLOBAL REFERENCE: DPT(D0,'PF',
 GLOBAL DESCRIPTION:   For patient allergies.  
GLOBAL REFERENCE: DPT(D0,'PG',
 GLOBAL DESCRIPTION:   For patient allergies.  
GLOBAL REFERENCE: DPT('CN',
 GLOBAL DESCRIPTION:   Cross reference used for ward reports.  
 GENERAL DESCRIPTION:   Uses the variable DFN and the following globals: 
   ^DPT(DFN,.101  for Treating Specialty 
   ^DPT(DFN,"PA"  for patient allergies 
   ^DPT(DFN,"PI"    "            " 
   ^DPT(DFN,"PF"    "            " 
   ^DPT(DFN,"PG"    "            " 
   ^DPT  "CN" X-Reference  for ward reports 
  STATUS: Retired                       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: 39                              IA #: 39
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: JAN 23, 1990            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA39
  ORIGINAL NUMBER: 39                   ID: DPT(
GLOBAL REFERENCE: DPT(D0,.3)
FIELD NUMBER: .301                      FIELD NAME: SERVICE CONNECTED?
  LOCATION: .3;1                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.31)
FIELD NUMBER: .313                      FIELD NAME: CLAIM NUMBER
  LOCATION: .31;3                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.36)
FIELD NUMBER: .361                      FIELD NAME: PRIMARY ELIGIBILITY CODE
  LOCATION: .36;1                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.362)
FIELD NUMBER: .36205                    FIELD NAME: RECEIVING A&A BENEFITS?
  LOCATION: .362;12                     ACCESS: Read w/Fileman
FIELD NUMBER: .36235                    FIELD NAME: RECEIVING A VA PENSION?
  LOCATION: .362;14                     ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.29)
FIELD NUMBER: .291                      FIELD NAME: DATE RULED INCOMPETENT
  LOCATION: .29;1                       ACCESS: Read w/Fileman
FIELD NUMBER: .293                      FIELD NAME: RATED INCOMPETENT?
  LOCATION: .29;12                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.31)
FIELD NUMBER: .312                      FIELD NAME: CLAIM FOLDER LOCATION
  LOCATION: .31;2                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,'DA',ADN,1)
 GLOBAL DESCRIPTION:   DATE OF DISCHARGE 
  
 Duration: Till version 5 of MAS.  
 GENERAL DESCRIPTION:   AMIE uses the following: 
   INP^VADPT to get inpatient information 
  STATUS: Expired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany

NUMBER: 40                              IA #: 40
  FILE NUMBER: 16                       GLOBAL ROOT: DIC(16,
  DATE CREATED: FEB 10, 1989            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA40
  ORIGINAL NUMBER: 40                   ID: DIC(16,
 GENERAL DESCRIPTION:   File 16 (old Person File) exported with version 3 of
 Patient Funds.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED PATIENT FUNDS
  ISC: Washington/Silver Spring

NUMBER: 41                              IA #: 41
  GLOBAL ROOT: DIBT(                    DATE CREATED: JUN 06, 1990
  CUSTODIAL PACKAGE: 1                  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: 45                              IA #: 45
  FILE NUMBER: 43                       GLOBAL ROOT: DG(43,
  DATE CREATED: JUN 26, 1990            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA45
  ORIGINAL NUMBER: 45                   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: Retired                       DURATION: Till Otherwise Agreed

NUMBER: 46                              IA #: 46
  DATE CREATED: MAR 15, 1990
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: OR1
  NAME: DBIA46                          ORIGINAL NUMBER: 46
  ID: OR1
 GENERAL DESCRIPTION:   ADD^OR1 AND AFT^OR1 are necessary integration links
 between OE/RR & Kenrel 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ADD
COMPONENT/ENTRY POINT: AFT
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

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: 48                              IA #: 48
  FILE NUMBER: 80.2                     GLOBAL ROOT: ICD(
  DATE CREATED: JUL 25, 1990            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA48                          ORIGINAL NUMBER: 48
  ID: ICD(
GLOBAL REFERENCE: ICD(D0,0)
FIELD NUMBER: 2                         FIELD NAME: WEIGHT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Used for lookups.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Salt Lake City

NUMBER: 49                              IA #: 49
  FILE NUMBER: 3.7                      GLOBAL ROOT: XMB(3.7, or XMBA(
  DATE CREATED: AUG 07, 1990            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA49
  ORIGINAL NUMBER: 49                   ID: XMB(3.7, or XMBA(
GLOBAL REFERENCE: XMB(3.7,.5,2,'B',
 GLOBAL DESCRIPTION:   This reference will change to XMBA( in MailMan 7.2.  I
 recommend using FM provided roots to avoid need to when a site changes from
 7.1 to 7.2.  
 GENERAL DESCRIPTION:   The only package granted a DBA to extract data from
 MailMan's file 3.7 is Albany's Site Installation Report.  
  
  
 References and extracts data from ^XMB global.  $O's thru the Postmaster's 
 basket, ^XMB(3.7,.5.2."B" ,to get IFN for URL, then $O's thru messages in the
 basket & extracts data into a FM file.  
  
 DURATION: Till next version of Fileman (v.18) when filegram and mail server
 functionality is available.  
  
 If this DBA is NOT OUT-OF-DATE and to be deleted, please note change suggested
 below.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: FEB 24, 1995
SUBSCRIBING PACKAGE: SOFTWARE INSTALLATION REPORT
  ISC: Albany

NUMBER: 50                              IA #: 50
  FILE NUMBER: 420.1                    GLOBAL ROOT: PRCD(420.1,
  DATE CREATED: OCT 17, 1990            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIA50
  ORIGINAL NUMBER: 50                   ID: PRCD(420.1,
GLOBAL REFERENCE: PRCD(420.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   DMMS Points to and reads the .01 field (cost center) of
 file 420.1 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

NUMBER: 51                              IA #: 51
  FILE NUMBER: 720                      DATE CREATED: OCT 22, 1990
  CUSTODIAL PACKAGE: 1                  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: 52                              IA #: 52
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG(
  DATE CREATED: JUN 10, 2003            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA52
  ORIGINAL NUMBER: 52                   ID: PSDRUG(
 GENERAL DESCRIPTION:   The "B" cross reference on the .01 field of the Drug
 File is 40 characters rather than the standard 30.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

NUMBER: 53                              IA #: 53
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA53
  ORIGINAL NUMBER: 53                   ID: PSRX(
GLOBAL REFERENCE: PSRX(D0,0)
FIELD NUMBER: 2                         FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PROVIDER
  LOCATION: 0;4                         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: 11                        FIELD NAME: MAIL/WINDOW
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 17                        FIELD NAME: UNIT PRICE OF DRUG
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: DAYS SUPPLY
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   DSS reads the entire zero node into a local variable.
 The above fields are then used.  
GLOBAL REFERENCE: PSRX(D0,2)
FIELD NUMBER: 20                        FIELD NAME: DIVISION
  LOCATION: 2;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 22                        FIELD NAME: FILL DATE
  LOCATION: 2;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(D0,1,D1,0)
FIELD NUMBER: 1                         FIELD NAME: QTY
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: MAIL/WINDOW
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: DIVISION
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1.1                       FIELD NAME: DAYS SUPPLY
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1.2                       FIELD NAME: CURRENT UNIT PRICE OF DRUG
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: PROVIDER
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   DSS reads the entire zero node into a local variable.
 The above fields are then used for REFILLS.  
GLOBAL REFERENCE: PSRX(D0,P,D1,0)
FIELD NUMBER: .02                       FIELD NAME: MAIL/WINDOW
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: QTY
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: DIVISION
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .041                      FIELD NAME: DAYS SUPPLY
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .042                      FIELD NAME: CURRENT UNIT PRICE OF DRUG
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: PROVIDER
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   DSS reads the entire zero node into a local variable.
 The above fields are used for PARTIAL FILLS.  
GLOBAL REFERENCE: PSRX(D0,IB)
FIELD NUMBER: 106                       FIELD NAME: IB NUMBER
  LOCATION: IB;2                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(D0,1,D1,IB)
FIELD NUMBER: 9                         FIELD NAME: IB NUMBER
  LOCATION: IB;1                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   DSS Extracts references the following data from the
 PRESCRIPTION file(#52).  
   
 For the extract date range, DSS uses the following cross references: 
  "AD" cross reference    ^PSRX("AD",DATE,D0,REFILL# or 0 for NEW RX 
  "AL" cross reference    ^PSRX("AL",DATE,D0,REFILL# or 0 for NEW RX 
  "AM" cross reference    ^PSRX("AM",DATE,D0,PARTIAL_REFILL# 
  "AR" cross reference    ^PSRX("AR",DATE,D0,FILL# 
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  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: 1                  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: 1                  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: 59                              IA #: 59
  FILE NUMBER: 68                       GLOBAL ROOT: LRO(68,
  DATE CREATED: MAY 25, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: DBIA59-A
  ORIGINAL NUMBER: 59                   ID: LRO(68,
 GENERAL DESCRIPTION:   - ECT namspaced option runs routine ^LRUPACA 
     Enter ACTION: S DIC=68,DIC(0)="QEAM" D ^DIC K DIC I Y>0 S LRAA=+Y, 
                   LRAA(1)=$P(Y,U,2) 
  
 - ECT namespaced option runs routine ^LRCAPS.  
  
 - Refences file 68 Accession (read only) 
    2  DATE 
       .01 DATE 
         1 ACCESSION NUMBER 
           .01 LRDFN 
            11 TESTS 
               .01 TESTS 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTERIM MANAGEMENT SUPPORT
  ISC: Birmingham

NUMBER: 60                              IA #: 60
  DATE CREATED: DEC 11, 1990            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSOHCSUM
  NAME: DBIA60-A                        ORIGINAL NUMBER: 60
  ID: PSOHCSUM
 GENERAL DESCRIPTION:   Version 1 of Health summaries exports and calls routine
 PSOHCSUM.  It is exported as routine GMTSPSZO and renamed if needed.  Health
 Summary post-inits check the environment for existance of PSOHCSUM.  
  
     - If PSOHCSUM does not exist or is an earlier version than 6, 
       GMTSPSZO is renamed PSOHCSUM.  
                  
     - If PSOHCSUM exists and is version 6 or greater, no changes are 
       made.  
                  
 ^GMTSPSO is the component driver, which sets up the context and calls the
 extract routine prior to printing.  ^PSOHCSUM extracts data from the pharmacy
 files for use with the Health Summary.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

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 - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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(
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).  
FIELD NUMBER: .01                       FIELD NAME: CASE NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: CAATRGORY OF EXAM
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: CONTRACT/SHARING SOURCE
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: IMAGING ORDER
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
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
GLOBAL REFERENCE: RADPT('AR',
FIELD NUMBER: .01                       FIELD NAME: EXAM DATE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This EXAM DATE field contains the date/time of the
 registered imaging exam.  
GLOBAL REFERENCE: RADPT('AO',
FIELD NUMBER: 11                        FIELD NAME: IMAGING ORDER
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Used to link the Radiology/Nuclear Medicine Request/Order
 to the Exam.  
GLOBAL REFERENCE: RADPT(D0,'DT',D1,'P',D2,DX,D3,0)
FIELD NUMBER: .01                       FIELD NAME: SECONDARY DIAGNOSTIC CODE
  LOCATION: 0;1                         ACCESS: Direct Global 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
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
KEYWORDS: RA PCE
KEYWORDS: PX*1*211 utility
KEYWORDS: DSSV
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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 DETAILS:   PATIENT CARE ENCOUNTER (PCE) subscribes to access
 radiology exam data by date using the 'AR' cross-reference on the EXAM DATE
 (#.01) field on the REGISTERED EXAMS (#2) sub-file (#70.02).  
  
 Updated on 07/20/2020 to include mention of PX*1*211.  
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 09/14/2022, effective with DSSV 1.1. DSS Class 2
 product. Document Only. DSSV is adding C3 is requesting access to the
 following fields/indexes from file 70:                                         
 Index AO                                               Subfile 70.02  
 ^RADPT(D0,'DT',D1,0) 
       2 TYPE OF IMAGING 
       4 IMAGING LOCATION Subfile 70.03 ^RADPT(D0,"DT",D1,"P",D2,0) 
       .01 CASE NUMBER 
       2 PROCEDURE 
       3 EXAM STATUS 
       4 CATEGORY OF EXAM 
       9 CONTRACT/SHARING SOURCE 
       11 IMAGING ORDER 
       13 PRIMARY STAFF / PRIMARY DIAGNOSTIC CODE 
       13.1 SECONDARY DIAGNOSTIC CODE 
       17 REPORT TEXT Subfile 70.14  ^RADPT(D0,DT,D1,P,D2,DX,D3,0) 
       .01 SECONDARY DIAGNOSTIC CODE 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/03/23, effective with patch OR*3.0*535, to
 access the IMAGING ORDER (#11) field in the RAD/NUC MED PATIENT (#70) file
 under the GLOBAL REFERENCE: RADPT(D0,'DT','D1','P',D2,0) section to allow CPRS
 to display the ordering provider related to certain notifications.  
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI
 SUBSCRIBING DETAILS:   Added 9/16/24, effective with patch DSIR*8.2*16,
 fdirect read the of the ^RADPT(D0,'DT',D1,0) global reference, field .01 EXAM
 DATE to determine if the patient has records in the file. 
  DATE ACTIVATED: OCT 03, 2023

NUMBER: 66                              IA #: 66
  FILE NUMBER: 16                       GLOBAL ROOT: DIC(16,
  DATE CREATED: NOV 25, 1990            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA66
  ORIGINAL NUMBER: 66                   ID: DIC(16,
 GENERAL DESCRIPTION:   Part of file 16 is exported with IFCAP THIS AGREEMENT
 SHOULD END BY LATE 1992.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IFCAP              ISC: Washington/Silver Spring

NUMBER: 67                              IA #: 67
  FILE NUMBER: 60                       GLOBAL ROOT: LAB(60,
  DATE CREATED: JAN 31, 1991            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File
  NAME: LAB TEST NAMES, PANELS, REFERENCE VALUES
  ORIGINAL NUMBER: 67                   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: 3                         FIELD NAME: TYPE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAB(60,D0,1,D1,0)
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
GLOBAL REFERENCE: LAB(60,D0,9,D1,0)
FIELD NUMBER: .01                       FIELD NAME: VERIFY WKLD CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAB(60,'C',
GLOBAL REFERENCE: LAB(60,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: LAB TEST
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Contains the test that are members of a panel.  
GLOBAL REFERENCE: LAB(60,D0,.1)
FIELD NUMBER: 51                        FIELD NAME: PRINT NAME
  LOCATION: .1;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAB(60,'B'
GLOBAL REFERENCE: LAB(60,'AB',
 GLOBAL DESCRIPTION:   Allows direct global read of "AB" cross-reference which
 contains listing of tests and the panels they are members.  
  
 LAB(60,"AB",file #60 ien,file #60 panel parent,ien of entry multiple) 
  
 where: 
  file #60 ien = file #60 internal entry number.  
  file #60 panel parent = file #60 ien of panel it's a member. 
  ien of entry multiple = sequence number of test within panel 
  
  
 Example: LAB(60,"AB",5072,5073,2)="" 
  
 Lab Test with ien 5072 is a member of panel test with ien 5073 and it's 
 sequence within the panel is 2.  
  
 GENERAL DESCRIPTION:   Allows access to several group of fields in LABORATORY
 TEST file (#60).  
  STATUS: Other                         DURATION: Till Otherwise Agreed
KEYWORDS: PANELS
KEYWORDS: LAB TEST
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS
 SUBSCRIBING DETAILS:   ADDED 4/23/09 

NUMBER: 68                              IA #: 68
  DATE CREATED: JAN 31, 1991            CUSTODIAL PACKAGE: UNIT DOSE PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSJEEU0
  NAME: DBIA68-A                        ORIGINAL NUMBER: 68
  ID: PSJEEU0
 GENERAL DESCRIPTION:   ^GMTSPSG is the component driver, which sets up the
 context and calls the extract routine prior to printing.  
  
 ^PSJEEU0 extracts data from the pharmacy files for use with the health 
 summary.  If ^PSJEEU0 is not available (i.e., Inpatient Meds package not yet
 installed), then ^GMTSPSGE is called, which accesses the same fields as
 ^PSJEEU0.  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PSJEEU0
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 69                              IA #: 69
  DATE CREATED: JAN 31, 1991            CUSTODIAL PACKAGE: IV PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSJEEU0
  NAME: DBIA69-A                        ORIGINAL NUMBER: 69
  ID: PSJEEU0
 GENERAL DESCRIPTION:   ^PSJEEU0 routine available in version 3 of Inpatient
 Medications Package will be used to extracts data from the pharmacy files for
 use with the health summary.  If ^PSJEEU0 is not available (i.e., Inpatient
 Meds package not yet installed), then ^GMTSPSIE is called, which accesses the 
 same fields as ^PSJEEU0. 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PSJEEU0
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 70                              IA #: 70
  DATE CREATED: FEB 01, 1991            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Other                           NAME: DBIA70
  ORIGINAL NUMBER: 70
 GENERAL DESCRIPTION:   Version 1 of Health Summaries exports a partial DD for
 the Lab Orders File (#60), which includes a new whole-file cross-reference 
 named "D", which indexes the file by Patient, Collection date and Specimen #. 
 In addition, the routines LROW2A, LRORDST, LRORDST1 and LROC, which have been
 modified to execute the SET and KILL logic for the "D" cross-reference, are
 renamed and exported in the following manner: 
  
                   LROW2A        as      GMTSLRZ1, 
                   LRORDST       as      GMTSLRZ2, 
                   LRORDST1      as      GMTSLRZ3 and 
                   LROC          as      GMTSLRZ4.  
  
 When the post-init routine, GMTSPOST is run, it renames the GMTSLRZ* routines
 as their corresponding LRO-namespaced routines as outlined above, if and only
 if the following conditions are met: 
  
              1.  The Laboratory Package is installed.  
              2.  The installed version of Lab is NOT less than 5.0.  
              3.  The installed version of Lab IS less than 5.1.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

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: 72                              IA #: 72
  DATE CREATED: FEB 04, 1991
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Other                           NAME: DBIA72
  ORIGINAL NUMBER: 72
 GENERAL DESCRIPTION:   Permission has been granted for Health Summary to
 export the routines: 
  
                  ORF4  as GMTSORF4 and 
                  ORF5  as GMTSORF5.  
  
 GMTSPOST, the Health Summary post-init, will rename the GMTSORF* routines as
 their ORF* counterparts, if and only if ORF4 is not found in the UCI by
 execution of ^%ZOSF("TEST").  
  STATUS: Retired                       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: 74                              IA #: 74
  FILE NUMBER: 121                      GLOBAL ROOT: GMR(121,
  DATE CREATED: FEB 04, 1991            CUSTODIAL PACKAGE: PROGRESS NOTES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: DBIA74-A
  ORIGINAL NUMBER: 74                   ID: GMR(121,
GLOBAL REFERENCE: 121
FIELD NUMBER: .03                       FIELD NAME: DATE/TIME OF PROGRESS NOTE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TITLE
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: AUTHOR
  LOCATION: 1;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4.1                       FIELD NAME: SIGNATURE IN CHART
  LOCATION: 1;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: COSIGNER
  LOCATION: 5;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: 121.01
FIELD NUMBER: .01                       FIELD NAME: TEXT
  LOCATION: 10;0                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: 121.03
FIELD NUMBER: .01                       FIELD NAME: COMMENTS/CORRECTIONS
  LOCATION: 70;0                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Agreement has been made for Health Summary to access
 specific fields in the Generic Progress Notes files.  
  
           - The cross-references ^GMR(121,"AJ2" and "AC", are traversed.  
           - Globals accessed are: 
                ^GMR(121,      Generic Progress Notes 
  STATUS: Retired                       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: 76                              IA #: 76
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: MAR 12, 1990            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA76
  ORIGINAL NUMBER: 76                   ID: DPT(
 GENERAL DESCRIPTION:   For MAS versions preceeding 5: 
  
 The following cross references are used to access ADT information 
    ^DPT(D0,"DA","AA",         Admissions 
    ^DPT(D1,"DA",D0,2,"ATT"    Transfers 
    ^DPT(D1,"DA",D0,"T",       Treating specialties 
  
 The DGLOS routine will be used to get the length of stay.  
  STATUS: Retired                       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: 79                              IA #: 79
  DATE CREATED: FEB 05, 1991            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Other                           NAME: DBIA79
  ORIGINAL NUMBER: 79
 GENERAL DESCRIPTION:   Permission has been granted for Health Summary to
 export the routines: 
  
                         XQOR   as  GMTSXQ01 
                         XQOR1  as  GMTSXQ02 
                         XQOR2  as  GMTSXQ03 
                         XQOR3  as  GMTSXQ04 
                         XQOR4  as  GMTSXQ05 
                         XQORM  as  GMTSXQ06 
                         XQORM1 as  GMTSXQ07 
                         XQORM2 as  GMTSXQ08 
                         XQORM3 as  GMTSXQ09 
                         XQORM4 as  GMTSXQ10 
                         XQORM5 as  GMTSXQ11 
                         XQORMX as  GMTSXQ12 
                         XQORO  as  GMTSXQ13 
  
 GMTSPOST, the Health Summary post-init, will rename GMTSXQ* as the 
 corresponding XQOR* routines if and only if the version of XQOR found in the
 account is less than 6.52.  
  STATUS: Retired                       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
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 

NUMBER: 81                              IA #: 81
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: FEB 05, 1991            CUSTODIAL PACKAGE: PATIENT FILE
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA81
  ORIGINAL NUMBER: 81                   ID: DPT(
 GENERAL DESCRIPTION:   The Health Summary "Adverse Reaction/Allergies"
 Component refers to some fields marked with * for eventual removal: 
  
    ^DPT( 2   PATIENT File 
        2.57  *Allergies/Disorders 
        2.55  *Generic Drug 
      
    ^DIC(57,  Allergy/Disorder File (#57) ^PSDRUG(     Drug File (File #50) 
  
 When the new Allergies package is disseminated we will be converting to 
 accessing allergies from that package.  Until that time we would like to
 continue gathering this information from the Patient File.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 82                              IA #: 82
  DATE CREATED: MAY 15, 1991            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: XQORM
  NAME: DBIA82                          ORIGINAL NUMBER: 82
  ID: XQORM
 GENERAL DESCRIPTION:   To facilitate selection and collection of multiple
 items, a call is made to EN^XQORM with XQORM as a required variable in
 addition to the variables supported from ^XQOR (see supported references).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 83                              IA #: 83
  DATE CREATED: JUL 09, 1991            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDACS
  NAME: DBIA83                          ORIGINAL NUMBER: 83
  ID: SDACS
 GENERAL DESCRIPTION:   Lab uses suported call EN3^SDACS for adding stop codes. 
 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN3
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Salt Lake City

NUMBER: 84                              IA #: 84
  DATE CREATED: JUL 09, 1991            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDACS
  NAME: DBIA84                          ORIGINAL NUMBER: 84
  ID: SDACS
 GENERAL DESCRIPTION:   Pharmacy uses EN3^SDACS for adding stop codes.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN3
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

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: 86                              IA #: 86
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDUTL
  NAME: DBIA86                          ORIGINAL NUMBER: 86
  ID: SDUTL
 GENERAL DESCRIPTION:   Create Requests for Records and Pull lists from clinic
 appointments: 
  
 Record Tracking queues a task which parses the scheduling  global for Record
 Tracking 'Borrowers' ie 'Clinics' which have appointments in a date range and
 creates Requested Records and Pull list entries for patients with 
 appointments.  
  
  IF there is a clinic appointment: An entry is made in the Pull list file
 #194.2 with a name derived from the clinic name 
                    SC(1,0)=Dr Jones Clinic^ 
                    RTV(194.2,n)=Dr Jones Clinic [04/01/91]^ 
  
 An entry is made in the Requested Records file #190.1    ^RTV(190.1,n) 
  
 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 call from CREATE+11^RTQ2 to 
  RTSET^SDUTL 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RTSET
SUBSCRIBING PACKAGE: RECORD TRACKING    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
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

NUMBER: 90                              IA #: 90
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA90-A
  ORIGINAL NUMBER: 90                   ID: PSRX(
GLOBAL REFERENCE: PSRX(D0,0)
FIELD NUMBER: 1                         FIELD NAME: ISSUE DATE
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PATIENT STATUS
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: CLINIC
  LOCATION: 0;5                         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: 8                         FIELD NAME: DAYS SUPPLY
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: # OF REFILLS
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SIG
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 17                        FIELD NAME: UNIT PRICE OF DRUG
  LOCATION: 0;17                        ACCESS: Read w/Fileman
FIELD NUMBER: 100                       FIELD NAME: STATUS
  LOCATION: 0;15                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,2)
FIELD NUMBER: 22                        FIELD NAME: FILL DATE
  LOCATION: 2;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   ICR may use a direct global read to get the FILL DATE.  
FIELD NUMBER: 26                        FIELD NAME: EXPIRATION DATE
  LOCATION: 2;6                         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 DESCRIPTION:   ICR may use a direct global read to get the REFILL DATE.  
FIELD NUMBER: 1                         FIELD NAME: QTY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.1                       FIELD NAME: DAYS SUPPLY
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 1.2                       FIELD NAME: CURRENT UNIT PRICE OF DRUG
  LOCATION: 0;11                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,3)
FIELD NUMBER: 101                       FIELD NAME: LAST DISPENSED DATE
  LOCATION: 3;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Amended November 1, 1993.  Amended August 30, 1994.  
 Amended October 28, 1997.  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 Pharmacy Reengineering developers in the C development team mail 
 group at EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY
  ISC: Hines
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  ISC: Oakland
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
SUBSCRIBING PACKAGE: MYHEALTHEVET
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

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
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 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expires on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA needs access to the Laboratory Test (#60) file for
 VIAB LOAD RPC and OrderMgmtSvc - getLabTestSpecificParams.  

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
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.  
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA
 SUBSCRIBING DETAILS:   MPI is requesting global read access to the 'B' cross
 reference and FileMan read access to the Admission Date (#2) and Discharge
 Date (#70) fields to support the validity of date of death of patients.  MPI
 needs access to the PTF file to search for records that may be non-VA care 
 (FEE) related.  This ICR provides the needed data elements to search through
 the global to find such records as the FEE entries are not complete PTF
 records.  
  
 The application will look for activity that could indicate the patient is not
 deceased as of a given date.  If the date of death is defined and after the
 proposed date of death or an admission date is defined after the proposed date
 of death, the record is logged for additional follow up.  The PTF file is used
 for this validity check to check for both VA and Fee Basis inpatient activity. 
 

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
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TYPE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This ICR allows direct global read and read with
 fileman access to the Stop Code Number (#8), Name (#.01), and Type (#2)
 fields. Name field direct read access is used to determine if a value exists
 and the Type field direct read access is used to determine the Hospital
 Location type before it can execute another task in TIUSRVP. 
  
 Revision History: 
  - 12/3/24: A previously missing Description was added to reflect the new 
 changes. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY
  ISC: Oakland
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  ISC: Oakland
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Updated 12/3/24 effective with TIU*1.0*369 patch to
 include fields #.01 and #2 to check if values exist in TIUSRVP Routine.  
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.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. 

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: 96                              IA #: 96
  DATE CREATED: FEB 21, 1991            CUSTODIAL PACKAGE: NURSING SERVICE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         ROUTINE: NURSAWL0
  NAME: DBIA96                          ORIGINAL NUMBER: 96
  ID: NURSAWL0
 GENERAL DESCRIPTION:   (1)NURSING SERVICE                    Nursing
 Workload/AMIS 1106 DIRECT CALL TO YOUR ROUTINE Direct call to routine
 EN1^NURSAWL0 to print 'Nursing Workload/ AMIS 1106 Report'.  
   
 NUR*2.2*20 will insure that the routine is there, ECT*1.05*2 will set up the
 proper global root before calling the routine.  
   
 (2)NURSING SERVICE                    Nursing Personnel Inquiry REFERENCING
 FIELDS FROM YOUR FILE IMS will determine global root by using ^DIC(210,0,"GL")
 and will then use a VA FileMan EN^DIQ call to display all fields in file 210
 (Nurs Staff).  
   
 Patch ECT*1.05*1 sets up the proper global root.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN1
SUBSCRIBING PACKAGE: INTERIM MANAGEMENT SUPPORT
  ISC: Birmingham

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: 102                             IA #: 102
  FILE NUMBER: 221                      GLOBAL ROOT: DENT(221,
  DATE CREATED: NOV 09, 2005            CUSTODIAL PACKAGE: DENTAL
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIA102-A
  ORIGINAL NUMBER: 102                  ID: DENT(221,
 GENERAL DESCRIPTION:   The following fields are accessed in a read-only
 manner: 
  
               ^DENT(221          DENTAL TREATMENT (AMIS) File 
                            4.5   PATIENT CATEGORY 
                            5     BED SECTION 
                            6     SCREENING/COMPLETE EXAM 
                            6.2   INTERDISCIPLINARY CONSULT 
                            6.4   EVALUATION 
                            6.6   PRE AUTH/2ND OPINION EXAM 
                            6.8   SPOT CHECK DISCREPANCY # 
                            6.7   SPOT CHECK EXAM 
                            7     ADMIN PROCEDURE 
                            7.1   COMPLETIONS/TERMINATIONS 
                            8     X-RAYS EXTRAORAL # 
                           10     X-RAYS INTRAORAL # 
                           11     PROPHY NATURAL DENTITION 
                           12     PROPHY DENTURE 
                           14     NEOPLASM CONFIRMED MALIGNANT # 
                           15     NEOPLASM REMOVED # 
                           16     BIOPSY/SMEAR # 
                           17     FRACTURE # 
                           19     OTHER SIGNIF. SURG. (CTV) 
                           21     SURFACES RESTORED # 
                           22     ROOT CANAL THERAPY # 
                           23     PERIODONTAL QUADS (SURGICAL) # 
                           24     PERIO QUADS (ROOT PLANE) # 
                           25     PATIENT ED. (CTV) 
                           27     INDIVIDUAL CROWNS # 
                           28     POST & CORES # 
                           29     FIXED PARTIALS   (ABUT) # 
                           30     FIXED PARTIALS   (PONT ONLY) # 
                           31     REMOVABLE PARTIALS # 
                           32     COMPLETE DENTURES # 
                           33     PROSTHETIC REPAIR # 
                           34     SPLINTS & SPEC. PROCS.   (CTV) 
                           35     EXTRACTIONS # 
                           36     SURGICAL EXTRACTIONS # 
                           37     OTHER SIGNIFICANT TREAT   (CTV) 
                           38     OPERATING ROOM 
                           39     FACTOR (NOT USED) 
                           61     DATE RELEASED 
  
               Eligible records will be determined by using the "E" cross 
               reference to determine matches with patients in the 
               Immunology Case Registry.  Records which have a value in 
               field #61, DATE RELEASED, will be accessed.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY
  ISC: Oakland

NUMBER: 103                             IA #: 103
  FILE NUMBER: 130                      GLOBAL ROOT: SRF(
  DATE CREATED: JUL 28, 1991            CUSTODIAL PACKAGE: SURGERY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: SURGERY file (#130)             ORIGINAL NUMBER: 103
  ID: SRF(
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.  
GLOBAL REFERENCE: SRF(D0,50,D1,0)
FIELD NUMBER: .213                      FIELD NAME: ANES CARE TIME BLOCK
  LOCATION: 50;0                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The ANES CARE TIME BLOCK multiple was added to this ICR
 in support of the DSS FY17 Annual Sustainment Patch ECX*3*161.  
  
 The ANES CARE MULTIPLE START TIME and ANES CARE MULTIPLE END TIME fields are
 used in calculating the patient's total anesthesia time.  
FIELD NUMBER: .01
  FIELD NAME: ANES CARE MULTIPLE START TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ANES CARE MULTIPLE END TIME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,63,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ORGANS TO BE TRANSPLANTED
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The ORGANS TO BE TRANSPLANTED multiple was added to this
 ICR in support of the DSS FY18 Annual Sustainment Patch ECX*3*166.  
  
 The ORGANS TO BE TRANSPLANTED field will be used to identify organs 
 transplanted during the operation.  
 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI
 SUBSCRIBING DETAILS:   Added 8/28/24 effective with DSIR*8.2*16 in order to
 read patient name field for given patient in the SURGERY (#130) file, field
 .01 PATIENT using FILEMAN. I $$GET1^DIQ(130,DSIRCHK_",",.01,"I" 
  DATE ACTIVATED: OCT 24, 2013

NUMBER: 104                             IA #: 104
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: OCT 04, 1991            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA104-A
  ORIGINAL NUMBER: 104                  ID: DPT(
 GENERAL DESCRIPTION:   #2 Patient file 
            .35 node 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 105                             IA #: 105
  DATE CREATED: OCT 04, 1991            CUSTODIAL PACKAGE: RECORD TRACKING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Other                           NAME: DBIA105
  ORIGINAL NUMBER: 105
 GENERAL DESCRIPTION:   Record Tracking: 
  
        - ^RTV(190.1,"AD" 
  
 Record Tracking option: RT RPT-RETRIEVAL STATS 
  
  If the option is removed from the Record Tracking Menu then the following
 entry and exit action needs to be added: 
      ENTRY ACTION: D OVERALL^RTPSET 
       EXIT ACTION: D KILL^RTPSET 
  
 The above references will be made from the QIP1RTP* routines which, while 
 belonging to the QIP namespace, will be maintained by the record tracking 
 developers.  Coordination of release and patches will be through the QIP 
 custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 106                             IA #: 106
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG(
  DATE CREATED: JUN 20, 2005
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA106
  ORIGINAL NUMBER: 106                  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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
  
 Routine QIP3POLY reads the following fields: In file 50, DRUG 
  .01 - GENERIC NAME 
    2 - VA CLASSIFICATION 
    3 - DEA, SPECIAL HDLG 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 107                             IA #: 107
  FILE NUMBER: 130                      GLOBAL ROOT: SRF(
  DATE CREATED: JUN 20, 2005            CUSTODIAL PACKAGE: SURGERY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA107-A
  ORIGINAL NUMBER: 107                  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: .09                       FIELD NAME: DATE OF OPERATION
  LOCATION: 0;9                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   In file 130, SURGERY, the "AC" cross reference (on field
 .09, DATE OF OPERATION) is accessed: 
   ^SRF("AC",$E(DATE,1,7),DA)=$P(^SRF(DA,0),"^") 
GLOBAL REFERENCE: SRF(D0,.1)
FIELD NUMBER: .14                       FIELD NAME: SURGEON
  LOCATION: .1;4                        ACCESS: Read w/Fileman
FIELD NUMBER: .165                      FIELD NAME: ATTENDING CODE
  LOCATION: .1;16                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: SRF(D0,.2)
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: .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,0)
FIELD NUMBER: .37                       FIELD NAME: ANESTHESIA TECHNIQUE
  LOCATION: (M 130.06)                  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
GLOBAL REFERENCE: SRF(D0,10,0)
FIELD NUMBER: 1.14                      FIELD NAME: INTRAOPERATIVE COMPLICATIONS
  LOCATION: (M 130.13)                  ACCESS: Read w/Fileman
GLOBAL REFERENCE: SRF(D0,10,D1,0)
FIELD NUMBER: 3                         FIELD NAME: COMPLICATION CATEGORY
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: SRF(D0,13,0)
FIELD NUMBER: .42                       FIELD NAME: OTHER PROCEDURES
  LOCATION: (M 130.16)                  ACCESS: Read w/Fileman
GLOBAL REFERENCE: SRF(D0,13,D1,2)
FIELD NUMBER: 3                         FIELD NAME: OTHER PROCEDURE CPT CODE
  LOCATION: 2;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: SRF(D0,16,0)
FIELD NUMBER: 1.16                      FIELD NAME: POSTOP COMPLICATION
  LOCATION: (M 130.22)                  ACCESS: Read w/Fileman
GLOBAL REFERENCE: SRF(D0,16,D1,0)
FIELD NUMBER: .5                        FIELD NAME: COMPLICATION CATEGORY
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DATE COMP NOTED
  LOCATION: 0;7                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: SRF(D0,30)
FIELD NUMBER: 17                        FIELD NAME: CANCEL DATE
  LOCATION: 30;1                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: SRF(D0,31)
FIELD NUMBER: 10                        FIELD NAME: SCHEDULED START TIME
  LOCATION: 31;4                        ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: SCHEDULED END TIME
  LOCATION: 31;5                        ACCESS: Read w/Fileman
FIELD NUMBER: 18                        FIELD NAME: CANCEL REASON
  LOCATION: 31;8                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: SRF(D0,NON)
FIELD NUMBER: 118                       FIELD NAME: NON-OR PROCEDURE
  LOCATION: NON;1                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: SRF(D0,OP)
FIELD NUMBER: 26                        FIELD NAME: PRINCIPAL PROCEDURE
  LOCATION: OP;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 27                        FIELD NAME: PRINCIPAL PROCEDURE CODE
  LOCATION: OP;2                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The following references will be made from the QIP3SR*
 routines which, while belonging to the QIP namespace, will be maintained by
 the surgery developers.  Coordination of release and patches will be through
 the QIP custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 108                             IA #: 108
  FILE NUMBER: 211.4                    GLOBAL ROOT: NURSF(211.4,
  DATE CREATED: OCT 04, 1991            CUSTODIAL PACKAGE: NURSING SERVICE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA108-A
  ORIGINAL NUMBER: 108                  ID: NURSF(211.4,
 GENERAL DESCRIPTION:   NURS LOCATION FILE #211.4 
  
 .01 Name 
  
 The above references will be made from the QIP4* routines which, while 
 belonging to the QIP namespace, will be maintained by the nursing developers. 
 Coordination of release and patches will be through the QIP custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 109                             IA #: 109
  FILE NUMBER: 62.05                    GLOBAL ROOT: LAB(62.05,
  DATE CREATED: OCT 04, 1991            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA109-A
  ORIGINAL NUMBER: 109                  ID: LAB(62.05,
GLOBAL REFERENCE: LAB(62.05,D0,0)
FIELD NUMBER: .01                       FIELD NAME: URGENCY
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The above references will be made from the QIP5* routines
 which, while belonging to the QIP namespace, will be maintained by the lab
 developers.  Coordination of release and patches will be through the QIP
 custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 110                             IA #: 110
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Other                           NAME: DBIA110-A
  ORIGINAL NUMBER: 110
 GENERAL DESCRIPTION:   The following option will be placed on the QUIC menu
 structure: 
            SDM - Make Appointment 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

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: 112                             IA #: 112
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDROUT2
  NAME: DBIA112                         ORIGINAL NUMBER: 112
  ID: SDROUT2
 GENERAL DESCRIPTION:   Display a patient's eligibility and disabilities the
 same way MAS does on the routing sheet..  
  
 The subroutine DIS^SDROUT2 make several global references: 
  
   ^DPT(DFN,.372, 
   ^DG(391, 
   ^DIC(31, 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DIS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 113                             IA #: 113
  FILE NUMBER: 80.1                     GLOBAL ROOT: ICD0(
  DATE CREATED: NOV 09, 2005            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA113-A
  ORIGINAL NUMBER: 113                  ID: ICD0(
GLOBAL REFERENCE: ICD0(D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY
  ISC: Oakland

NUMBER: 114                             IA #: 114
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: AUG 24, 1991            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA114
  ORIGINAL NUMBER: 114                  ID: DPT(
 GENERAL DESCRIPTION:   Checks 1st piece of the .35 node for death 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SURGERY            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
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: 117                             IA #: 117
  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                            NAME: DBIA117
  ORIGINAL NUMBER: 117                  ID: PS(55,
GLOBAL REFERENCE: PS(55,D0,5,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ORDER NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: MED ROUTE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: TYPE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: SCHEDULE TYPE
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .25                       FIELD NAME: ORIGINAL ORDER NUMBER
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 12                        FIELD NAME: DOSE LIMIT
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 39                        FIELD NAME: *TOTAL UNITS DISPENSED
  LOCATION: computed                    ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   calculated by X $P(^DD(55.06,39,0),U,5,99) 
GLOBAL REFERENCE: PS(55,D0,5,D1,2)
FIELD NUMBER: 26                        FIELD NAME: SCHEDULE
  LOCATION: 2;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: START DATE/TIME
  LOCATION: 2;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 34                        FIELD NAME: STOP DATE/TIME
  LOCATION: 2;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,D0,5,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: DISPENSE DRUG
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: UNITS PER DOSE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,DFN,5,'AUS',
 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 EMAIL GROUP 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.  Amended August 30, 1994.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY
  ISC: Oakland
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  ISC: Oakland
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES

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
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: 122                             IA #: 122
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: OCT 06, 1991            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA122
  ORIGINAL NUMBER: 122                  ID: VA(200,
 GENERAL DESCRIPTION:   Fields in the NEW PERSON File for OE/RR 
  
 100.11 PRIMARY OE/RR MENU 100.12 PRIMARY ORDER MENU 100.13 PRIMARY ORDER
 DISPLAY FORMAT 100.14 PRIMARY WARD 100.15 PRIMARY PATIENT LIST 100.16 SELECT
 PATIENT DEFAULT 100.17 PRIMARY CLINIC 100.18 DEFAULT CLINIC START DATE 100.19
 DEFAUTL CLINIC STOP DATE 100.21 SUMMARY DEFAULT 100.22 PATIENT LIST ORDER 
 100.23 PATIENT LIST PROCESS 100.24 PRIMARY PROFILE MENU 100.25 PRIMARY
 PROVIDER 100.26 PRIMARY SPECIALTY 100.27 NEW ORDERS DEFAULT 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 123                             IA #: 123
  FILE NUMBER: 736                      GLOBAL ROOT: QIP(736,
  DATE CREATED: OCT 06, 1991
  CUSTODIAL PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA123
  ORIGINAL NUMBER: 123                  ID: QIP(736,
 GENERAL DESCRIPTION:   Following fields point to file 736 (QUIC SORT FILE) 
  
  field 2 (SITE NATIONAL) in file 59 (PHARMACY SITE) 
  
  field 12 (SITE) in file 1900.1 (CLOZARIL REPORTS) 
  
 In addition, since the extended clozaril patch may go to test sites before the
 QUIC package does, and since the test sites will almost certainly be
 different, file 736 will be exported (with data) with the extended clozaril
 patch.  
  
 We understand that there is at least one field in file 736 that is not to be
 sent to the sites, but only to the national data base and we agree not to send
 that field to the sites.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  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
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: 133                             IA #: 133
  DATE CREATED: DEC 09, 1991            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Other                           NAME: DBIA133
  ORIGINAL NUMBER: 133
 GENERAL DESCRIPTION:   
  The data for fields *Allergy/Disorders (57) and *Generic Drug (55) of the 
 Patient (2) file will be converted by the Allergy Tracking System V2.2 and 
 moved into the Patient Allergies (120.8) file.  The data in the the two fields
 will be deleted after it is converted.  The two  DD's for the two fields, 55
 and 57, will be deleted also.  
  
 The Allergy Tracking System is using  +$G(^DG(43,1,"VERSION")) to check for 
 the version number of MAS currently installed at the site.  If this value is
 less than 5, the INIT process will abort.  
  
 The Allergy Tracking System is hanging the GMRA DGPM MARK CHART protocol off 
 the DGPM MOVEMENT EVENTS protocol.  The code that is executed from the GMRA 
  DGPM MARK CHART protocol sets up a TaskManager job if appropriate.  The input
 variables expected by the GMRA DGPM MARK CHART protocol are: 
     DFN = IFN of patient in Patient file.  
     DGPMP = Zeroth node in Patient Movements file prior to whatever MAS 
       action has taken place.  
     DGPMA = Zeroth node in Patient Movements file after whatever MAS action 
        has taken place.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

NUMBER: 134                             IA #: 134
  DATE CREATED: DEC 09, 1991            CUSTODIAL PACKAGE: DIETETICS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Other                           NAME: DBIA134
  ORIGINAL NUMBER: 134
 GENERAL DESCRIPTION:   
  The data for the Food Allergies (.1) field of the Dietetics Patient (115) 
 file will be converted by the Allergy Tracking System V2.2 and moved into the
 Patient  Allergies (120.8) file.  The data in the the field will be deleted
 after it is converted.  The DD's for field .1 will be deleted also.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

NUMBER: 135                             IA #: 135
  GLOBAL ROOT: DD(                      DATE CREATED: DEC 09, 1991
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  NAME: DBIA135                         ORIGINAL NUMBER: 135
  ID: DD(
GLOBAL REFERENCE: DD('VERSION')
 GENERAL DESCRIPTION:   
  The Allergy Tracking System is using +$G(^DD("VERSION")) to check for the 
 version number of the VA FileManager currently installed at the site.  If this
 value is less than 18, the INIT process will abort.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

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
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: 137                             IA #: 137
  DATE CREATED: DEC 09, 1991
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: ORVOM
  NAME: DBIA137                         ORIGINAL NUMBER: 137
  ID: ORVOM
 GENERAL DESCRIPTION:   The ORVOM utility from Order Entry/Results
 Reporting(OE/RR) V2.15 is used to create the GMRAO* routines to export the
 GMRA DGPM MARK CHART protocol used by the Allergy Tracking System V2.2.  These
 GMRAO* routines will not be included in the integrity checker routine GMRANTEG
 created by Kernel.  These routines will run correctly under any version of
 OE/RR, including the verified V1.96.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

NUMBER: 138                             IA #: 138
  DATE CREATED: DEC 09, 1991            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSOHCSUM
  NAME: DBIA138                         ORIGINAL NUMBER: 138
  ID: PSOHCSUM                          STATUS: Retired
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: JAN 12, 1994
COMPONENT/ENTRY POINT: PSOHCSUM
 COMPONENT DESCRIPTION:   
  The Allergy Tracking System V2.2 uses a call to ^PSOHCSUM to extract data 
 pertaining to outpatient pescriptions.  A call to ^%ZOSF("TEST") is made to 
 check for the existence of PSOHCSUM before it is called.  
  
 The input variables are: 
    DFN = IFN of patient in Patient file.  
    PSOBEGIN = The date/time to begin the search for prescriptions.  
  
 The data is returned in the following arrays: 
    ^UTILITY("PSOO",$J,IFD,0)=ID^FD^DR^PR^ST^RX^QT^RF^IF^CF^EX 
    ^UTILITY("PSOO",$J,IFD,1)=SIG 
    
 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.  
     SIG = Medication instruction for this Rx.  
VARIABLES: DFN                          TYPE: Input
VARIABLES: PSOBEGIN                     TYPE: Input
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

NUMBER: 139                             IA #: 139
  DATE CREATED: DEC 09, 1991            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSJEEU0
  NAME: DBIA139                         ORIGINAL NUMBER: 139
  ID: PSJEEU0                           STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ENHS
 COMPONENT DESCRIPTION:   The Allergy Tracking System V2.2 uses a call to
 ENHS^PSJEEU0 to extract data pertaining to inpatient med orders.  The
 ^%ZOSF("TEST") global is used to test for the existence of the PSJEEU0 routine
 before it is called.  
  
 The input variables are: 
     DFN = IFN of patient in Patient file.  
     PSJEDT = The date to begin the search for orders.  
  
 The data is returned in two arrays: 
  
 Unit dose data is returned in the following array: 
     ^UTILITY("PSG",$J,IDT)=SDT^FDT^DRG^PR^ST^DO^MR^SCH^SCT 
     
 where: 
     IDT = Inverse start date of order.  
     SDT = Start date of order.  
     FDT = Stop date of order 
     DRG = Drug ordered. This variable has format A;B where A is the internal 
 pointer and B is the 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 order.  This variable has format A;B where A is the 
 internal representation and B is external printable form.  
     DO = Dosage of drug ordered.  
     MR = Medication route of drug ordered.  This variable has format A;B where
 A is the internal pointer and B is external printable form.  
     SCH = Administration schedule of order.  
     SCT = Schedule type of SCH.  This variable has format A;B where A is the 
 internal representation and B is external printable 
  
 IV data is returned in the following arrays: 
    ^UTILITY("PSIV",$J,-SDT,0)=SDT^FDT^PR^ST^IR^SCH 
  
 Array of additives in order: 
    ^UTILITY("PSIV",$J,-SDT,"A",Number)=ADT^STR 
   
 Array of solutions in order: 
    ^UTILITY("PSIV",$J,-SDT,"S",Number)=SOL^VOL 
    
 where: 
     SDT = Start date of order.  
     FDT = Stop date of order 
     PR = Provider.  This variable has format A;B where A is the internal 
 pointer and B is the external printable form.  
      ST = Status of order.  This variable has format A;B where A is the 
 internal representation and B is external printable form.  
      IR = Infusion rate of order.  
     SCH = Administration schedule of order.  
     ADT = One additive of order. This variable has format A;B where A is the 
            internal pointer and B is external printable form.  
     STR = Strength of additive ADT in order.  
     SOL = One solution of order. This variable has format A;B where A is the 
            internal pointer and B is external printable form.  
     VOL = Volume of solution SOL in order.  
VARIABLES: DFN                          TYPE: Input
VARIABLES: PSJEDT                       TYPE: Input
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

NUMBER: 140                             IA #: 140
  DATE CREATED: JAN 07, 1992            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Routine                         ROUTINE: PRCSUT
  NAME: DBIA140-A                       ORIGINAL NUMBER: 140
  ID: PRCSUT
 GENERAL DESCRIPTION:   1.  EN3^PRCSUT - Checks for Fund Control Point user
 authorization access.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN3
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Salt Lake City

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
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   Access will be used for VIAB SCDIS RPC 

NUMBER: 143                             IA #: 143
  DATE CREATED: FEB 05, 1992
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Other                           NAME: DBIA143
  ORIGINAL NUMBER: 143
 GENERAL DESCRIPTION:   Patch DVB*4.0*71 is a partial decommission of Hospital
 Inquiry (HINQ), as it disables the ability to submit HINQ requests in support
 of WebHINQ. As a result, this ICR is Retired.  
  
 HINQ v4 inits will transfer data from field 14.9 in File 3 to field 14.9 in 
 File 200.  
  STATUS: Retired                       EXPIRATION DATE: MAR 04, 2022
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: 149                             IA #: 149
  FILE NUMBER: 50.416                   GLOBAL ROOT: PS(50.416,
  DATE CREATED: MAR 25, 1992            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA149-A
  ORIGINAL NUMBER: 149                  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 NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Use FileMan call to look-up entry using the "P"
 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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
  
 The Adverse Reaction Tracking (ART) package will point to the Drug Ingredient
 (50.416) file. Also, ART can do lookups on this file using the 'P'
 cross-reference. ART will do a direct global read on the NAME field (.01).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

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
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
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: 152                             IA #: 152
  DATE CREATED: APR 01, 1992            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: DGPMUTL
  NAME: DBIA152                         ORIGINAL NUMBER: 152
  ID: DGPMUTL
 GENERAL DESCRIPTION:   A call to WARD^DGPMUTL, to find the ward at discharge,
 in the routine QIP1DIS.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: WARD
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

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: 158                             IA #: 158
  FILE NUMBER: 70                       GLOBAL ROOT: RADPT(
  DATE CREATED: JUN 02, 1992
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA158
  ORIGINAL NUMBER: 158                  ID: RADPT(
 GENERAL DESCRIPTION:   
   The following fields are used from the Radiology package for determining
 radiology procedures that use contrast media that were associated with
 complications: 
  
 To determine procedures performed for a date range: 
   "AR" cross-reference on the EXAM DATE field - 70.02,.01 
  
 To determine procedure performed and whether or not contrast media was used,
 and if so, was there a complication: 
  
 Field          Global Reference          Name 
 -------     ---------------------       -------
      2             70.03,2              RADIOLOGY PROCEDURE 
      3             70.03,3              EXAM STATUS 
     10             70.03,10             CONTRAST MEDIA USED 
     16             70.03,16             COMPLICATION 
      9             71,9                 CPT 
    .01             71.03,.01            AMIS CODE 
    .01             78.1,.01             COMPLICATION 
  
 The above references will be made from the QIP1Q46 routine which, while 
 belonging to the QIP namespace, will be maintained by the radiology 
 developers.  Coordination of release and patches will be through the QIP
 custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 159                             IA #: 159
  FILE NUMBER: 741                      GLOBAL ROOT: QA(741,
  DATE CREATED: JUN 02, 1992            CUSTODIAL PACKAGE: OCCURRENCE SCREEN
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA159-A
  ORIGINAL NUMBER: 159                  ID: QA(741,
 GENERAL DESCRIPTION:   The following references will be made from the QIP4QAO*
 routines which, while belonging to the QIP namespace, will be maintained by
 the occurrence screen developers.  Coordination of release and patches will be
 through the QIP custodial ISC.  
  
 #741 QA OCCURRENCE SCREEN file 
      .01 Date 
      4 Ward/Clinic 
      11 Status 
      10 Reviewer (multiple) 
           .01 Review Level 
           4 Findings 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

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
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: 168                             IA #: 168
  FILE NUMBER: 6                        GLOBAL ROOT: DIC(6,
  DATE CREATED: JUN 16, 1992            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA168
  ORIGINAL NUMBER: 168                  ID: DIC(6,
 GENERAL DESCRIPTION:   DSS extracts information from a number of DHCP files. 
 In many of the extracts, provider information is one of the data elements.  
 Because this information is being shipped out of DHCP, we opted to send
 pointer values rather than names.  Since most packages currently point to file
 6 and will ultimately point to 200 and since we don't want to try to
 coordinate releases with all packages, we have chosen to send data in the form
 of pointer-file.  We are looking at the second "P" piece of the second "^"
 piece of the zero node of the DD for the field in question. 
  
 Till supported call is available.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

NUMBER: 169                             IA #: 169
  DATE CREATED: JUN 17, 1992            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: XQORM
  NAME: DBIA169-A                       ORIGINAL NUMBER: 169
  ID: XQORM
 GENERAL DESCRIPTION:   The Consult/Request Tracking package populates the
 Protocol File (101) with protocol items representing responses to prompts. 
 These responses are selectable via calls to the Menu Utility, XQORM, routines.
 For example, "Select Action: ", "Place of Consultation: ", and "Urgency: " 
 prompts all use the XQORM routines to handle the users response.  Variable,
 XQORM("NO^^"), has been added for those responses that it is inappropriate to
 "^^" jump.  
   
 Variables set to call XQORM 
  
    XQORM=variable pointer to Protocol File (101) entry.  The Protocol File
 entries specified are all Protocol Menu Type entries.(e.g., GMRCPLACEM -
 INPATIENT is the Protocol Name of a distributed Protocol Menu used at "Place
 of Consultation: " prompts.) 
  
   XQORM("NO^^")="" When defined, this variable tells XQORM not to allow "^^"
 jumping at the prompt.  
  
   XQORM(0)=This controls the display and prompting of the menu.  XQORM(0) may
 contain a number, and/or letters A,D, and F.  If there is a number, it must
 always be at the beginning of the string.  The parameters do the following: 
     #: maximum number of selections allowed.  If there is no number, as many
 selections as menu items are allowed.  
  
     A: The user will be prompted to make a selection.  
  
     D: The menu will be displayed.  
  
     F: Selection will NOT be saved in ^DISV.  
    
   For example, XQORM(0)="2A" will allow the user to make a maximum of two 
 selections.  The menu will not be displayed (unless a ? is typed), and the 
 selections will be saved in ^DISV.  
  
   XQORM("A")=Text here will be used as the select prompt.  
  
   XQORM("B")=Text here will be used as the default menu selection.  
  
   XQORM("?")=MUMPS code that replaces the standard help.  
  
   XQORM("S")=(Not used by Consult/Request Tracking)  MUMPS code that will 
 screen the items on the menu.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: XQORM
VARIABLES: XQORM                        TYPE: Input
VARIABLES: XQORM()                      TYPE: Input
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: 1                  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 - DECISION SUPPORT SYSTEM 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
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
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: 179                             IA #: 179
  DATE CREATED: JUN 18, 1992            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDACS
  NAME: DBIA179                         ORIGINAL NUMBER: 179
  ID: SDACS
 GENERAL DESCRIPTION:   Radiology uses supported call EN3^SDACS for adding stop
 codes.  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN3
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  ISC: Albany

NUMBER: 180                             IA #: 180
  DATE CREATED: JUN 18, 1992            CUSTODIAL PACKAGE: 1
  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: 1
  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
  GOOD ONLY FOR VERSION: 5.3
COMPONENT/ENTRY POINT: N
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 183                             IA #: 183
  DATE CREATED: JUL 16, 1992            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: PSOSD1
  NAME: DBIA183                         ORIGINAL NUMBER: 183
  ID: PSOSD1
 GENERAL DESCRIPTION:   Health Summary will use the entry point DFN^PSOSD1,
 which can be called with DFN and PSTYPE=1, to print the Action Profile.  NOTE: 
 This DBIA has been replaced by DBIA #1281.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 09, 1998
COMPONENT/ENTRY POINT: DFN
VARIABLES: DFN                          TYPE: Input
VARIABLES: PSTYPE                       TYPE: Input
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 184                             IA #: 184
  DATE CREATED: JUL 16, 1992            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSOSD1
  NAME: DBIA184                         ORIGINAL NUMBER: 184
  ID: PSOSD1
 GENERAL DESCRIPTION:   OE/RR will use the entry point DFN^PSOSD1, which can be
 called with DFN and PSTYPE=1, to print the Action Profile.  NOTE:  This DBIA
 has been replaced by DBIA #1281.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 09, 1998
COMPONENT/ENTRY POINT: DFN
VARIABLES: DFN                          TYPE: Input
VARIABLES: PSTYPE                       TYPE: Input
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

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 

NUMBER: 188                             IA #: 188
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDAMBAE4
  NAME: DBIA188-A                       ORIGINAL NUMBER: 188
  ID: SDAMBAE4
 GENERAL DESCRIPTION:   
  
 STATUS^SDAMBAE4-- Incorporated current Ambulatory Procedure active status into
 a CPT status function that also includes BASC and AMA status 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: STATUS
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 189                             IA #: 189
  DATE CREATED: AUG 03, 1992            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: DGPMDDCF
  NAME: DBIA189                         ORIGINAL NUMBER: 189
  ID: DGPMDDCF
 GENERAL DESCRIPTION:   Record Tracking routines RTDPA31,RTSM and
 ^DD(195.9,.01,"V",,2) 'Ward location variable pointer screen' call 
  
 WIN^DGPMDDCF with DO=IFN of WARD LOCATION FILE to screen inactive wards as
 borrowers/file areas.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: WIN
SUBSCRIBING PACKAGE: RECORD TRACKING    ISC: Albany

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: 191                             IA #: 191
  DATE CREATED: AUG 18, 1992
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSOPS
  NAME: DBIA191-A                       ORIGINAL NUMBER: 191
  ID: PSOPS
 GENERAL DESCRIPTION:   
      ^PSOPS: 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.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES

NUMBER: 192                             IA #: 192
  GLOBAL ROOT: DD(                      DATE CREATED: JUN 20, 2005
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  NAME: DBIA192                         ORIGINAL NUMBER: 192
  ID: DD(
 GENERAL DESCRIPTION:   FileMan agrees that Quality Improvement Checklist can
 call the following routine occurrences of ^DD references: 
  
 ROUTINE OCCURRENCES OF ^DD REFERENCES: 
  
 QIPEXT+2:  I $D(QIPCUS) W !!,"This option displays the report 
 specifications",!,"for the QUIC",$P($P(";"_$P 
 (^DD(738.1,1,0),"^",3),";"_QIPCUS_":",2)," ;")," extract report(s).",! G EN 
  
 QIPEXTR+9:  I $D(QIPCUS) S PNAME=$P($P(";"_$P(^DD(738.1,1,0),"^",3), CUS_":
 ",2),";") 
  
 QIPEXTR+18:  K LOC,NAME,PM,PNAME S LOC=^QIP(738.1,OPTN,0),NAME=$P 
 (LOC,"^"),PM=$P(LOC,"^",2),PNAME=$P($P(";"_$P(^DD(738.1,1,0),"^",3), 
 ";"_PM_":",2),"; ") 
  
 QIPEXTU1+21:  W !?10,$J(CNT,2),". ",NAME,"  -  ",$P($P(";"_$P(^DD 
 (738.1,1,0),"^",3),";"_PM_":",2),";")_$S($G(^QIP(738.1,OPTN,"NA")) 
 &(QIP'="V"):"  <<NOT AVAILABLE>>",1:"") 
  
 GLOBAL LISTINGS OF THE REFERENCED DDs: 
  
 ^DD("42",".03","0")="SERVICE^RSX^M:MEDICINE;S:SURGERY;P:PSYCHIATRY; 
 NH:NHCU;NE:NEUROLOGY;I:INTERMEDIATE MED;R:REHAB MEDICINE;SCI:SPINAL CORD
 INJURY;D:DOMICILIARY;B:BLIND REHAB;NC:NON-COUNT;^0;3^Q" 
  
 ^DD("738.1","1","0")="PARENT MENU^RS^L:LABORATORY;M:MAS;N:NURSING; 
 P:PHARMACY;S:SURGERY;Q:QUALITY MANAGEMENT;R:RADIOLOGY;^0;2^Q"  
   
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

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: 195                             IA #: 195
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDROUT2
  NAME: DBIA195                         ORIGINAL NUMBER: 195
  ID: SDROUT2
 GENERAL DESCRIPTION:   Display a patient's eligibility and disabilities the
 same way MAS does on the routing sheet.  
  
 The subroutine DIS^SPROUT2 makes several global references: 
  
 ^DPT(DFN,.372, ^DG(391, ^DIC(31, 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DIS
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  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: 199                             IA #: 199
  FILE NUMBER: 736                      GLOBAL ROOT: QIP(736,
  DATE CREATED: DEC 04, 1992
  CUSTODIAL PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA199-A
  ORIGINAL NUMBER: 199                  ID: QIP(736,
 GENERAL DESCRIPTION:   1) The ALPHA PROJECT DATA file (#734) would like to
 point to File 736, 
     QUIC SORT DATA file.  
     .01 VAMC in File 734 is a dinum pointer to File 736.  
  
 2) ALPHA routines access the following QUIC fields in a read-only manner: 
    File 736 QUIC SORT DATA 
             .01 STATION NAME 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ALPHA              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: 203                             IA #: 203
  FILE NUMBER: 162.1                    GLOBAL ROOT: FBAA(162.1,
  DATE CREATED: JAN 31, 2006            CUSTODIAL PACKAGE: FEE BASIS
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: FEE BASIS PHARMACY INVOICE
  ORIGINAL NUMBER: 203                  ID: FBAA(162.1,
GLOBAL REFERENCE: FBAA(162.1,'AA'
 GLOBAL DESCRIPTION:   The AA cross reference.  It is defined as
 FBAA(162.1,"AA",date_certified,patient,da(1),da) where       
       date_certified is the DATE CERTIFIED FOR PAYMENT (#15) 
       patient        is the PATIENT (4) 
       da(1)          is the IEN of the FEE BASIS PHARMACY INVOICE 
       da             is the IEN of the PRESCRIPTION NUMBER multiple 
GLOBAL REFERENCE: FBAA(162.1,D0,RX,D1,0)
FIELD NUMBER: 6.5                       FIELD NAME: AMOUNT PAID
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 204                             IA #: 204
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA204
  ORIGINAL NUMBER: 204                  ID: SC(
 GENERAL DESCRIPTION:   Read Only access to the Hospital Location File (#44), 
 Field 1900 (Appointment), to read scheduling information from the global
 ^SC(D0,S,D1,1,D2,0).  The information read will be stored in a Prosthetics
 package file and used in the quarterly compilation of AMIS reports.  
  
 Read access to the ^SC(D0,"I") node to check the inactivate date (field #2505)
 and the re-activate date (field #2506) to allow Prosthetics to Select an
 active Clinic when entering Prosthetics Clinics in the Prosthetics Site
 Parameter File.  
  
 Until V. 6.0 of Registration.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Salt Lake City

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
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
  ISC: Birmingham

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
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 - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham
SUBSCRIBING PACKAGE: INTEGRATED BILLING

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
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

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 EMAIL GROUP 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
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

NUMBER: 222                             IA #: 222
  FILE NUMBER: 81                       GLOBAL ROOT: CPT FILE
  DATE CREATED: APR 02, 1993            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA222-A
  ORIGINAL NUMBER: 222                  ID: CPT FILE
GLOBAL REFERENCE: DD(81,0,'ID',2)
 GENERAL DESCRIPTION:   The DD for the CPT file (81) includes the following
 node which causes the CPT code description to be displayed when a lookup is 
 done on the CPT file: 
    ^DD(81,0,"ID",2)="W "   ",$P(^(0),U,2) I $D(SRSITE) D ^SROCPT" 
  
 Part 1: An agreement is established for Surgery to call ^DD(81,0,"ID",2). 
 This DD node will remain in place to assist with CPT lookups from within the 
 Surgery package.  Surgery will be responsible for support of the conditional
 call to ^SROCPT.  
   
 Part 2: In the routine SROCPT, the DESCRIPTION multiple is accessed (READ
 only).  Surgery has permission to read the DESCRIPTION sub-fields.  Each 
 description for a CPT code is stored in ^ICPT(X,"D",Y,0) where X is the
 internal entry for the CPT code and Y is the internal entry for the
 description.  The Surgery package loops through ^ICPT(X,"D",Y,0) to get all
 the descriptions for a CPT code.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SURGERY            ISC: Birmingham

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: 225                             IA #: 225
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Other                           NAME: DBIA225-A
  ORIGINAL NUMBER: 225
 GENERAL DESCRIPTION:   Prosthetics has permission from MAS to call the
 following: 
  
 Addition of the Prosthetics Protocol RMPR SCHED EVENT as an item on the SDAM
 APPOINTMENTS EVENTS Protocol in File 101.  Below is a display of the RMPR
 SCHED EVENT protocol: 
  
 RMPR SCH EVENT ITEM TEXT: Prosthetics Scheduling file update TYPE: action 
 PACKAGE: PROSTHETICS 
  
 Updates the Prosthetics Scheduling Events file whenever an appointment is
 created or updated. The Clinic must be in the Prosthetics Site Parameter file
 before the Prosthetics files can be updated by MAS.  
  
 ENTRY ACTION:  D ^RMPRSC 
  
 SDAM APPOINTMENT EVENTS          ITEM TEXT: Appointment Event Driver 
      TYPE: extended action            CREATOR: POSTMASTER 
  
 This extended action contains all the actions that need to be performed when
 an action is taken upon an appointment, such as checking in.  
  
 ITEM: SDAM LATE ENTRY                       SEQUENCE: 2 ITEM: IBACM OP LINK    
                     SEQUENCE: 1 ITEM: RMPR SCH EVENT                       
 SEQUENCE: 3 TIMESTAME: 55576,33406 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Salt Lake City

NUMBER: 226                             IA #: 226
  DATE CREATED: MAY 03, 1993            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: DGPTFCR
  NAME: DBIA226-A                       ORIGINAL NUMBER: 226
  ID: DGPTFCR                           STATUS: Retired
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: OCT 23, 2006
COMPONENT/ENTRY POINT: CREATE
SUBSCRIBING PACKAGE: FEE BASIS          ISC: Albany

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: 1
  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: 1
  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: 235                             IA #: 235
  DATE CREATED: JUN 02, 1993            CUSTODIAL PACKAGE: MCCR BACKBILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: DGCRNS
  NAME: DBIA235                         ORIGINAL NUMBER: 235
  ID: DGCRNS
 GENERAL DESCRIPTION:   Call ^DGCRNS and DISP^DGCRNS to get and display the 
 names of all current insurance carriers for a Veteran.  
  
 Until approx. 18 mo. after release of MCCR V2 
  STATUS: Retired                       DURATION: Next Version
COMPONENT/ENTRY POINT: DGCRNS
COMPONENT/ENTRY POINT: DISP
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Salt Lake City

NUMBER: 236                             IA #: 236
  DATE CREATED: JUN 15, 1993            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSOSD1
  NAME: DBIA236                         ORIGINAL NUMBER: 236
  ID: PSOSD1
 GENERAL DESCRIPTION:   PIMS (MAS) users often have a need to print a Drug
 Profile after printing the 10-10.  PIMS, therefore, is given permission from 
 Outpatient Pharmacy to allow PIMS to call the line tag DFN^PSOSD1.  This call
 allows tasked or non-tasked Drug Profile printout.  NOTE:  This DBIA has been
 replaced by DBIA #1281.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DFN
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   the internal entry number for the Patient File)
 [Required] 
VARIABLES: PSTYPE                       TYPE: Input
 VARIABLES DESCRIPTION:   (1 for Action Profile, 0,null, or undefined for
 Informational) 
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).  
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Albany

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(
GLOBAL REFERENCE: DPT(D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: SEX
  LOCATION: 0;2
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DATE OF BIRTH
  LOCATION: 0;3
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .09                       FIELD NAME: SSN
  LOCATION: 0;9
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.11
FIELD NUMBER: .111                      FIELD NAME: STREET ADDRESS [LINE 1]
  LOCATION: .11;1
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .112                      FIELD NAME: STREET ADDRESS [LINE 2]
  LOCATION: .11;2
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .113                      FIELD NAME: STREET ADDRESS [LINE 3]
  LOCATION: .11;3
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .114                      FIELD NAME: CITY
  LOCATION: .11;4
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .115                      FIELD NAME: STATE
  LOCATION: .11;5
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .116                      FIELD NAME: ZIP CODE
  LOCATION: .11;6
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .117                      FIELD NAME: COUNTY
  LOCATION: .11;7
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .1171                     FIELD NAME: PROVINCE
  LOCATION: .11;8
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .1172                     FIELD NAME: POSTAL CODE
  LOCATION: .11;9
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .1173                     FIELD NAME: COUNTRY
  LOCATION: .11;10
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .1112                     FIELD NAME: ZIP+4
  LOCATION: .11;12
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.13
FIELD NUMBER: .131                      FIELD NAME: PHONE NUMBER [RESIDENCE]
  LOCATION: .13;1
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .132                      FIELD NAME: PHONE NUMBER [WORK]
  LOCATION: .13;2
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.29
FIELD NUMBER: .291                      FIELD NAME: Date Ruled Incompetent (VA) 
  LOCATION: .29;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .292
  FIELD NAME: Date Ruled Incompetent (CIVIL) 
  LOCATION: .29;2                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .293                      FIELD NAME: Rated Incompetent? 
  LOCATION: .29;12                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.3
FIELD NUMBER: .301                      FIELD NAME: SERVICE CONNECTED?
  LOCATION: .3;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .302                      FIELD NAME: SERVICE CONNECTED PERCENTAGE
  LOCATION: .3;2                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.31
FIELD NUMBER: .314                      FIELD NAME: CLAIM FLODER LOCATION
  LOCATION: .31;2                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .313                      FIELD NAME: CLAIM NUMBER
  LOCATION: .31;3                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.32
FIELD NUMBER: .324
  FIELD NAME: Service Discharge Type [LAST] 
  LOCATION: .32;4                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .325                      FIELD NAME: Service Branch [LAST] 
  LOCATION: .32;5                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .326                      FIELD NAME: Service Entry Date [LAST] 
  LOCATION: .32;6                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .327
  FIELD NAME: Service Separation Date [LAST] 
  LOCATION: .32;7                       ACCESS: Direct Global Read & w/Fileman
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,.361
FIELD NUMBER: .3611                     FIELD NAME: Eligibility Status 
  LOCATION: .361;1                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .3612                     FIELD NAME: Eligibility Status Date 
  LOCATION: .361;2                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.362
FIELD NUMBER: .36205                    FIELD NAME: Receiving A&A Benefits? 
  LOCATION: .362;12                     ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .32635                    FIELD NAME: RECEIVING A VA PENSION?
  LOCATION: .362;14                     ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.372,D1
FIELD NUMBER: .01                       FIELD NAME: Rated Disabilities (VA) 
  LOCATION: .372;1                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: Disability %
  LOCATION: .372;2                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: Service Connected
  LOCATION: .372;3                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.52
FIELD NUMBER: .525                      FIELD NAME: POW STATUS INDICATED?
  LOCATION: .52;5
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,'DIS',D1,0
FIELD NUMBER: .01                       FIELD NAME: Log-in Date/Time 
  LOCATION: 'DIS';1                     ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,'S',D1,0
FIELD NUMBER: .01                       FIELD NAME: CLINIC
  LOCATION: 'S';1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9.5                       FIELD NAME: APPOINTMENT TYPE
  LOCATION: 'S';17                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,'VET'
FIELD NUMBER: 1901                      FIELD NAME: VETERAN (Y/N)?
  LOCATION: 'VET';1                     ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
  
  AMIE has permission from PIMS to make calls to a variety of field and 
 cross-references. All fields accessible to AMIE through this agreement are
 based on FileMan. AMIE also has LAYGO access to the Patient file per agreement
 with the MASSIUG.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AMIE
KEYWORDS: DPT
KEYWORDS: FILE 2
KEYWORDS: PATIENT FILE
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany
 SUBSCRIBING DETAILS:   Updated 12/23/25 effective with patch DVBA*2.7*257.  
 Three fields .01,.314, and .36235 were added. 
  DATE ACTIVATED: DEC 08, 2010

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: 247                             IA #: 247
  FILE NUMBER: 3.9                      GLOBAL ROOT: XMB(3.9,
  DATE CREATED: DEC 01, 1991            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA247
  ORIGINAL NUMBER: 247                  ID: XMB(3.9,
 GENERAL DESCRIPTION:   Refenences to the MESSAGE File  (3.9) 
  
    ^XMB(3.9,i,0)    Field .01   Subject 
    ^XMB(3.9,i,2,j,0)   Field 3  Text 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: REMOTE ORDER/ENTRY SYSTEM
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Salt Lake City

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
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 1/22/21 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Added 1/22/21 

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
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
  ISC: Birmingham

NUMBER: 255                             IA #: 255
  GLOBAL ROOT: DD(301.5,                DATE CREATED: JUL 28, 1993
  CUSTODIAL PACKAGE: 1                  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
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: 261                             IA #: 261
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDM
  NAME: DBIA261-A                       ORIGINAL NUMBER: 261
  ID: SDM
 GENERAL DESCRIPTION:   The option HBHC Appointment uses the MAS routine ^SDM
 as the Run Routine, and employs SDM^SDKILL in the exit action.  
  
 Select OPTION to edit: HBHC APPOINTMENT          Make Appointment NAME: HBHC
 APPOINTMENT// MENU TEXT: Make Appointment// PACKAGE: HOSPITAL BASED HOME
 CARE// DESCRIPTION: 
   1>This option utilizes the MAS Scheduling Option, Make Appointment [SDM], 
   2>for entry of appointment data.  The Exit Action on this option runs a 
   3>routine that creates records in the HBHC Visit File (HBHC(632)) using 
   4>the appointment data entered.  Only data for clinics contained in the 
   5>HBHC Clinic File (HBHC(631.6)) will be added to the HBHC Visit File.  
  
 EDIT Option: TYPE: run routine// ENTRY ACTION: D:$T(HDLKILL^SDAMEVT)]""
 HDLKILL^SDAMEVT EXIT ACTION: D SDM^SDKILL K ORACTION,ORVP,XQORQUIT W
 !!,"Adding entries 
   to the visit file..." D WAIT^DICD,^HBHCAPPT 
   D:$T(HDLKILL^SDAMEVT)]"" HDLKILL^SDAMEVT 
           Replace ROUTINE: SDM// 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HOME BASED PRIMARY CARE
  ISC: Hines

NUMBER: 262                             IA #: 262
  DATE CREATED: AUG 09, 1993            CUSTODIAL PACKAGE: 1
  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
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: 1                  ISC: Oakland

NUMBER: 265                             IA #: 265
  DATE CREATED: AUG 17, 1993            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA265
  ORIGINAL NUMBER: 265
 GENERAL DESCRIPTION:   
  
 Clinical Monitoring System and MAS for 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 
  
 PURPOSE OF VISIT              PATIENT 
     1                         1900                    2 
     2                         9                       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.) 
  
 COVERED BY HEALTH INSURANCE?  PATIENT 
     1                         .3192                   2 
  
 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 
  
 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 
  
 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 
  
 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 
  
 MAS MOVEMENT TRANSACTION TYPE MAS MOVEMENT TRANSACTION TYPE 
     1                        .01                      405.3 
  
 NAME                          DISPOSITION 
     1                        .01                       37 
  
 NAME                          FACILITY TREATING SPECIALTY 
     1                        .01                       45.7 
  
 FACILITY TREATING SPECIALTY   SERVICE 
     1                         2                        45.7 
  
 NAME                          MAS MOVEMENTT TYPE 
     1                        .01                      405.2 
  
 NAME                          APPOINTMENT TYPE 
     1                        .01                      409.1 
  
 CODE NUMBER                   ICD DIAGNOSIS 
     1                        .01                       80 
  
 CODE NUMBER                   ICD OPERATION/PROCEDURE 
     1                        .01                       80.1 
  
 PATIENT                       HOSPITAL LOCATION 
     1                        1900                       44 
     2                           2                       44.001 
     3                         .01                       44.003 
  
  
  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 
  
 DATA GLOBAL                   HOSPITAL LOCATION 
  
   XREF: ^SC(D0,"S",D1,1,D2,...  
                 ^     ^
                 |     |-- PATIENT 
                 |-- APPOINTMENT 
  
 CLOSE OUT DATE                PTF CLOSE OUT 
  
   XREF: AC 
  
 DATA GLOBAL                   PTF 
  
   XREF: ^DGPT(D0,"S",D1,...  
                   ^
                   |-- SURGERY/PROCEDURE DATE 
  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM
  ISC: Hines

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. Exporting, deleting, updating List Template by Namespace via
 KIDS is permitted.  
  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: 273                             IA #: 273
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG(
  DATE CREATED: AUG 30, 1993
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA273-A
  ORIGINAL NUMBER: 273                  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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
  
 #50  DRUG FILE   ^PSDRUG( 
     To maintain backward compatibility with 
       Outpatient Pharmacy V5.6 50,623001     DALLAS COMMENTS        623001;1 
 FREE TEXT 50,623002     LAB TEST MONITOR       623002;1 POINTER TO 
                                               LABORATORY 
                                               TEST FILE 
                                               (#60) 50,623003     MONITOR MAX 
 DAYS       623002;2 NUMBER 50,623004     SPECIMEN TYPE          623002;3 
 POINTER TO 
                                               TOPOGRAPHY 
                                               FIELD FILE 
                                               (#61) 50,623008     MONITOR 
 ROUTINE        623008;1 FREE TEXT 
  
     To maintain compatibility with 
       Outpatient Pharmacy V6.0 50,17.2       LAB TEST MONITOR       CLOZ;1  
 POINTER TO 
                                               LABORATORY 
                                               TEST FILE 
                                               (#60) 50,17.3       MONITOR MAX 
 DAYS       CLOZ;2   NUMERIC 50,17.4       SPECIMEN TYPE          CLOZ;3  
 POINTER TO 
                                               TOPOGRAPHY 
                                               FIELD FILE 
                                               (#61) 50,17.5       MONITOR 
 ROUTINE        CLOZ1;1  FREE TEXT 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: MENTAL HEALTH      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: 275                             IA #: 275
  FILE NUMBER: 101                      GLOBAL ROOT: ORD(101,
  DATE CREATED: SEP 09, 1993            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA275-A
  ORIGINAL NUMBER: 275                  ID: ORD(101,
 GENERAL DESCRIPTION:   Purpose: 
  
 Request an integration agreement between the Discharge Summary Team and the
 OE/RR Team at the Salt Lake ISC for Discharge Summary version 1.0: 1.  to
 access protocol descriptions by direct reference to the ^ORD(101, and 2.
 permission to call ^XQORM as described below.  
  
 Description: To allow the user to get a detailed description of the actions
 that are executable from each of our menu-type protocols, we 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.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DISCHARGE SUMMARY  ISC: Salt Lake City

NUMBER: 276                             IA #: 276
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG(
  DATE CREATED: SEP 09, 1993
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA276-A
  ORIGINAL NUMBER: 276                  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.  
  
  
 Mental Health V. 5.0 references the following Outpatient pharmacy files and
 fields: 
               File  #50    -   Drug 
               Field #.01   -   Generic Name  -  ^PSDRUG(D0,0)  piece  1 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas

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: 280                             IA #: 280
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9(
  DATE CREATED: SEP 13, 1993            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA280                         ORIGINAL NUMBER: 280
  ID: ICD9(
 GENERAL DESCRIPTION:   We are requesting that a sharing agreement be
 established between the Hospital Based Home Care software and the Global
 ^ICD9( for the following fields.  
 **********************************************************
 ******* Fields ******************************************** 
 **********************************************************
 FIELD             .01      (node: 0, piece: 1) TYPE OF ACCESS    READ GLOBAL   
         ^ICD9( 
  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HOME BASED PRIMARY CARE
  ISC: Hines

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: 285                             IA #: 285
  FILE NUMBER: 442                      GLOBAL ROOT: PRC(442,
  DATE CREATED: SEP 02, 2003            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIA285-A
  ORIGINAL NUMBER: 285                  ID: PRC(442,
 GENERAL DESCRIPTION:   Also see DBIA's 804-810 Most of the calls below are
 interfaces between AR and IFCAP for the creation of CALM code sheets.  After
 all of the sites convert to FMS, these calls will no longer be needed.  These
 calls will need to be supported in future versions of the packages or until
 all of the sites convert to FMS.  
   
 Integration agreements between IFCAP and AR for use of tje IFCAP Vendor File 
 440 will be needed through-out the life of the AR package.  The AR routine
 calls to IFCAP to support the CALM code sheets.  
   
 Fields that AR routines set and/or reference in the Procurement & Accounting 
 Transaction File (#442) of IFCAP include: 
  
 442,.01      - Purchase Order Number            (0;1) 442.09       - 
 Obligation Data sub-file 442.09,.01  - TT/DATE/REF                          
 (0;1) 442.09,1     - Obligated By                            (0;2) 442.09,3   
  - Code Sheet Number                 (0;4) 442,.1         - P.O. Date         
                         (1;15)        
     
 442,.02       - Method of Processing              (0;2)  442,5.1       - 
 Debtor                                     (1;16)         
       
 442,19        - Agent Assigned P.O.                (12;4) 442,19.2     - Date 
 P.O. Assigned                   (12;5) 442,102      - Document 
 Identifier/Common No.   (18;3) Fiscal Year sub-file 430.01, Pat Ref. No. Field
 430.01,2 (0;3) -   
      points to Procurement & Accounting Transaction File (#442) 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  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 

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 

NUMBER: 291                             IA #: 291
  GLOBAL ROOT: DD(142.1,                DATE CREATED: OCT 18, 1993
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: Salt Lake City
  USAGE: Private                        TYPE: File
  NAME: DBIA291                         ORIGINAL NUMBER: 291
  ID: DD(142.1,
 GENERAL DESCRIPTION:   The Allergy Tracking System V3.0 uses ^DD(142.1,0,"VR") 
 to determine which version of the Health Summary package is currently running. 
 This information is needed to determine which array will be returned by the
 GMTSLROE and GMTSLRSE utilities.  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

NUMBER: 292                             IA #: 292
  DATE CREATED: OCT 18, 1993            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMTSLROE
  NAME: DBIA292                         ORIGINAL NUMBER: 292
  ID: GMTSLROE
 GENERAL DESCRIPTION:   The Allergy Tracking System V3.0 uses a call to 
 XTRCT^GMTSLROE to extract lab order data.  A call to ^%ZOSF("TEST") is used to
 check for the existence of this routine on the system before it is called.  
  
 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: 
 @REF@("LRO",$J,IDT,SN_FN)=CDT^TST^SPC^URG^OS^MD^ODT 
                             ^ACC^RDT^COL^CD where: REF = "^UTILITY" if Health
 Summary V1.2, or 
            "^TMP" if Health Summary V2.5+.  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 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 
       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.  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: XTRCT
VARIABLES: DFN                          TYPE: Input
VARIABLES: SEX                          TYPE: Input
VARIABLES: GMTS1                        TYPE: Input
VARIABLES: GMTS2                        TYPE: Input
VARIABLES: MAX                          TYPE: Input
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

NUMBER: 293                             IA #: 293
  DATE CREATED: OCT 18, 1993            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMTSLRSE
  NAME: DBIA293                         ORIGINAL NUMBER: 293
  ID: GMTSLRSE
 GENERAL DESCRIPTION:   The Allergy Tracking System V3.0 uses a call to 
 XTRCT^GMTSLRSE to extract lab results.  A call to ^%ZOSF("TEST") is used to
 check for the existence of this routine on the system before it is called.  
  
 The input variables are: 
   LRDFN = IFN of patient in Lab Data (63) file.  
     SEX = Sex of patient.  
   GMTS1 = Inverse end date of search for lab results.  
   GMTS2 = Inverse start date of search for lab results.  
   MAX = Maximum number of lab results to be extracted 
   TEST = IFN of lab test which results are sought in 
            Laboratory Test (60) file.  The data is returned in the following
 array: @REF@("LRS",$J,NUM,IDT)=DDT^SPC^TST^RSL^FLG^UNT^LO^HI where: 
    REF = "^UTILITY" if Health Summary V1.2, or 
              "^TMP" if Health Summary V2.5+.  
    NUM = Order (1 to MAX).  
    IDT = Inverse draw date/time of result.  
    DDT = Draw date/time of result.  
    SPC = Specimen for lab order.  This variable has 
       format A;B where A is the internal pointer 
       and B is external printable form.  TST = Lab test ordered.  This
 variable has format 
       A;B where A is the internal pointer and B 
       is 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.  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: XTRCT
VARIABLES: LRDFN                        TYPE: Input
VARIABLES: SEX                          TYPE: Input
VARIABLES: GMTS1                        TYPE: Input
VARIABLES: GMTS2                        TYPE: Input
VARIABLES: MAX                          TYPE: Input
VARIABLES: TEST                         TYPE: Input
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

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: HOME BASED PRIMARY 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
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: 1                  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

NUMBER: 303                             IA #: 303
  FILE NUMBER: 60                       GLOBAL ROOT: LAB(60,
  DATE CREATED: JUN 20, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA303-A
  ORIGINAL NUMBER: 303                  ID: LAB(60,
GLOBAL REFERENCE: LAB(60,D0,0)
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,.2)
FIELD NUMBER: 400                       FIELD NAME: DATA NAME
  LOCATION: .2;1                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   QUIC is granted an integration agreement with
 Laboratory to obtain the rate of completion of at least one Glycosalated
 Hemoglobin measurement within one year for diabetic patients on a medication
 regimen.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

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
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
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
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: 1                  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 

NUMBER: 316                             IA #: 316
  GLOBAL ROOT: DD(                      DATE CREATED: NOV 01, 1993
  CUSTODIAL PACKAGE: 1                  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: 320                             IA #: 320
  DATE CREATED: NOV 23, 1993            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Other                           NAME: DBIA320
  ORIGINAL NUMBER: 320
 GENERAL DESCRIPTION:   An integration agreement is approved to use the VA
 FileMan undocumented variable DIWESUB.  This variable will be set in the 
 Enter/Edit option of all objects and sub-objects of the ADP Plan Manager
 Version 10 software.  The variable will be used in conjunction the a VA
 FileMan call to EN^DIWE for users to edit both the Initiative Description and
 the Equipment Justification.  When using the full screen editor to edit word
 processing fields, the entire screen is blanked, and could be potentially
 confusing to the user.  In all cases the variable will be set immediately 
 prior to the call to EN^DIWE, and will be killed immediately afterword. 
 Following is a short sample of the code which is used to edit the Initiative
 Description.  
   
 EDIT; 
      S DIWEPSE=1 
      S DIC="^PRAPIN(PRASTN,""IN"",PRASIN,""ID""," 
      S DWLW="75",DWPK="1" 
      S DIWESUB="Description" 
      D EN^DIWE K DIWESUB 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ADP PLANNING       ISC: Birmingham

NUMBER: 321                             IA #: 321
  FILE NUMBER: 757.01                   DATE CREATED: DEC 01, 1993
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  NAME: MODIFY 'B' XREF OF 757.01       ORIGINAL NUMBER: 321
 GENERAL DESCRIPTION:   The FM team grants the request of the Clinical Lexicon
 package to modify the "B" index of file 757.01 as follows: 
  
 S ^GMP(757.01,"B",$E($$UP^XLFSTR(X),1,63),DA)="" K
 ^GMP(757.01,"B",$E($$UP^XLFSTR(X),1,63),DA) 
  
 It is further agreed that the following tools will not be used with this file:
 DIFROM, COMPARE/MERGE and TRANSFER.  These tools rely on an unmodified 'B'
 index to function properly.  Using the modified 'B' index of file 757.01 along
 with any of the named tools may produce unexpected results.  
  
  STATUS: Expired                       DURATION: Next Version
  EXPIRATION DATE: APR 03, 2007         GOOD ONLY FOR VERSION: LEXICON 1.0
SUBSCRIBING PACKAGE: LEXICON UTILITY    ISC: Salt Lake City

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 - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 *****************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
 *****************************************************
SUBSCRIBING PACKAGE: DIETETICS
 SUBSCRIBING DETAILS:   EPIP Intake 11, NSR 20170519 has a requirement to print
 the Diet orders next to the patient supplemental feeding list.  To  find the
 order it is necessary to find the admission date to access the data in
 NUTRITION PERSON FILE# 115. Existing Dietetics option Run SF Labels/Consolid
 Ingred List, [FHNO2], will be updated in patch FH*5.5*43.  

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:DT<X!(2000000>X) 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:DT<X!(2000000>X) 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:DT<X!(1800000>X) 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:DT<X!(2000000>X) 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:DT<X!(1800000>X) 
                    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: 1
  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: 1
  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
 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.  
  
 Revision History: 
  - Added 3/4/25 effective with PSO*7*650 and OR*3*561 to add the Complex Doses
 for Non-VA medications.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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. 
  
 Patch PSO*7*441 added Indication ("IND") node to the Rx entry. If an 
 Indication is populated then ^TMP("PSOO",$J,IFD,"IND")=Indication^Indication
 flag (1-Indication is included in the Sig, 0 or null-Indication is not
 included in the Sig) 
  
 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) 
  
 NON-VA Meds: Complex doses (node 3) were added with PSO*7*650 
  
 ^TMP("PSOO",$J,"NVA",n,3,nn)=dosage^schedule (expanded)^duration 
 (expanded)^conjunction (expanded) 
  
  
 ^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 
  
 Patch PSS*1*187 added Indication ("IND") node to the NON-VA entry. If an 
 Indication is populated then ^TMP("PSOO",$J,"NVA",n,"IND")=Indication 
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 
  DATE ACTIVATED: MAR 04, 2025

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: 335                             IA #: 335
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA335-A
  ORIGINAL NUMBER: 335                  ID: SC(
 GENERAL DESCRIPTION:   Pharmacy Prescription Practices Prototype is granted
 this DBIA with Scheduling to make the following calls: 
  
 I.   Direct read access to the SC global.  
  
      A.   ^SC("AC","C",CLINIC) -> Used to obtain a list of all 
           clinics currently in the file.  
  
      B.   ^SC(CLINIC,"S",DATE) -> Used to check for patients 
           scheduled for clinic on a specified date.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  ISC: Albany

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: <form iew>^<form name> 
      $$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: 339                             IA #: 339
  DATE CREATED: MAY 19, 2003            CUSTODIAL PACKAGE: LEXICON UTILITY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMPTDUSR
  NAME: DBIA339                         ORIGINAL NUMBER: 339
  ID: GMPTDUSR
 GENERAL DESCRIPTION:   
  The Problem List Application has permission to use the entry point ^GMPTDUSR.
 This entry point will be used to setup user-specific look-up defaults.  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GMPTDUSR
 COMPONENT DESCRIPTION:   Returned:          None 
  Global Nodes Set: ^GMP(757.2,<application>,200,DUZ,1)   Default  
                     filter 
                    ^GMP(757.2,<application>,200,DUZ,2)   Default  
                     display 
                    ^GMP(757.2,<application>,200,DUZ,3)   Default  
                     vocabulary 
VARIABLES: GMPTAP                       TYPE: Input
 VARIABLES DESCRIPTION:   Where GMPTAP = Application Namespace ('GMPL') 
SUBSCRIBING PACKAGE: PROBLEM LIST       ISC: Salt Lake City

NUMBER: 340                             IA #: 340
  DATE CREATED: MAY 19, 2003            CUSTODIAL PACKAGE: LEXICON UTILITY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMPTSET
  NAME: DBIA340                         ORIGINAL NUMBER: 340
  ID: GMPTSET                           STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CONFIG(GMPTNS,GMPTSS)
 COMPONENT DESCRIPTION:   This entry point will be used to setup 
 package-specific defaults and look-up variables.  
VARIABLES: GMPTNS                       TYPE: Input
 VARIABLES DESCRIPTION:   Application Namespace ('GMPL') 
VARIABLES: GMPTSHOW                     TYPE: Output
 VARIABLES DESCRIPTION:   Display, when not defined by the user 
VARIABLES: GMPTSS                       TYPE: Input
 VARIABLES DESCRIPTION:   Any valid subset mnemonic indexed at either
 ^GMP(757.2,"AA"or ^GMP(757.2,"AB" 
VARIABLES: DIC('S')                     TYPE: Output
VARIABLES: GMPTSUB                      TYPE: Output
 VARIABLES DESCRIPTION:   Vocabulary, when not defined by the user.  
VARIABLES: GMPTUN                       TYPE: Output
 VARIABLES DESCRIPTION:   Unresolved Narratives flag 
VARIABLES: DIC                          TYPE: Used
 VARIABLES DESCRIPTION:   Set and not killed 
VARIABLES: DIC(0)                       TYPE: Used
 VARIABLES DESCRIPTION:   Set and not killed 
VARIABLES: XT*                          TYPE: Used
 VARIABLES DESCRIPTION:   All XT namespaced variables listed in the programmers
 API (supported references for the Kernel Toolkit's Multi-Term look-up Utility. 
 These variables are killed after the look-up.  
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: 344                             IA #: 344
  FILE NUMBER: 101                      GLOBAL ROOT: ORD(101,
  DATE CREATED: JAN 31, 1994            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA344-A
  ORIGINAL NUMBER: 344                  ID: ORD(101,
 GENERAL DESCRIPTION:   The following DBIA is granted between the Unwinder and
 OE/RR.  
  
 Read Access to File 101:  The XQOR routines navigate the Protocol file (101). 
 To provide this navigation, XQOR needs read access to File 101.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: UNWINDER           ISC: Salt Lake City

NUMBER: 345                             IA #: 345
  GLOBAL ROOT: DD(                      DATE CREATED: FEB 02, 1994
  CUSTODIAL PACKAGE: 1                  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
SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  ISC: Albany

NUMBER: 351                             IA #: 351
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19,
  DATE CREATED: FEB 28, 1994            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA351-A
  ORIGINAL NUMBER: 351                  ID: DIC(19,
 GENERAL DESCRIPTION:   Read Access to File 19:  When an Option that is a
 protocol (O) or protocol menu (Q) is encountered by menu manager, control is
 turned over to XQOR.  XQOR needs to have read access to File 19 to be able to 
 provide the navigation of these protocols.  This agreement would replace DBIA
 #5, which was between OE/RR and Menu Driver.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

NUMBER: 352                             IA #: 352
  GLOBAL ROOT: DD(                      DATE CREATED: FEB 28, 1994
  CUSTODIAL PACKAGE: 1                  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
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
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 "C" or "S" or "L" 
             or "", if problem is related to exposure to Agent Orange, 
             Ionization, Persian Gulf, Head and/or Neck Cancer, Military 
             Sexual Trauma, Combat Veteran, SHAD, Camp Lejeune 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).  
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: 356                             IA #: 356
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA356
  ORIGINAL NUMBER: 356                  ID: SC(
 GENERAL DESCRIPTION:   Read access to the following fields and
 cross-references.  
  
  
  FIELDS: 
  
 ELEMENT                       FILE 
     DD LEVEL                  FIELD #                 DD NUMBER 
  
 **PATIENT                       HOSPITAL LOCATION 
     1                        1900                       44 
     2                           2                       44.001 
     3                         .01                       44.003 
  
 **DATA GLOBAL                   HOSPITAL LOCATION 
  
   XREF: ^SC(D0,"S",D1,1,D2,...  
                 ^     ^
                 |     |-- PATIENT 
                 |-- APPOINTMENT 
  
  STATUS: Retired                       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
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 8/12/2022, effective with DSSV*1.1 DSS Class 3
 product Document Only 

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
SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM
  ISC: Hines
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 364                             IA #: 364
  FILE NUMBER: 409.1                    GLOBAL ROOT: SD(409.1,
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA364
  ORIGINAL NUMBER: 364                  ID: SD(409.1,
 GENERAL DESCRIPTION:   Read access to the following fields: 
  
  FIELDS: 
  
 ELEMENT                       FILE 
     DD LEVEL                  FIELD #                 DD NUMBER 
  
 NAME                          APPOINTMENT TYPE 
     1                        .01                      409.1 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM
  ISC: Hines
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Salt Lake City

NUMBER: 365                             IA #: 365
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9(
  DATE CREATED: MAR 03, 1994            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA365                         ORIGINAL NUMBER: 365
  ID: ICD9(
 GENERAL DESCRIPTION:   Read access to the following fields: 
  
  FIELDS: 
  
 ELEMENT                       FILE 
     DD LEVEL                  FIELD #                 DD NUMBER 
  
 CODE NUMBER                   ICD DIAGNOSIS 
     1                 0      .01                       80 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM
  ISC: Hines

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: 368                             IA #: 368
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9(
  DATE CREATED: MAR 09, 1994            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA368
  ORIGINAL NUMBER: 368                  ID: ICD9(
 GENERAL DESCRIPTION:   
  Request to directly reference the following fields in the ICD DIAGNOSIS 
     (#80) file: 
  
     Field Name (#)        Location   Reason 
     ===================================================================
     DIAGNOSIS (3)           0;3      Print and display the diagnosis name 
     USE ONLY WITH SEX (9.5) 0;10     Bill diagnoses appropriate for the 
                                      patient's sex 
     DESCRIPTION (10)        1;1      Print and display the diagnosis 
                                      description 
     INACTIVE FLAG (100)     0;9      Only active diagnoses can be billed 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 369                             IA #: 369
  FILE NUMBER: 80.1                     GLOBAL ROOT: ICD0(
  DATE CREATED: MAR 09, 1994            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA369
  ORIGINAL NUMBER: 369                  ID: ICD0(
 GENERAL DESCRIPTION:   
  Request to directly reference the following fields in the ICD 
     OPERATION/PROCEDURE (#80.1) file: 
  
     Field Name (#)        Location   Reason 
     ===================================================================
     OPERATION/PROCEDURE (4) 0;4      Print and display the procedure name 
     INACTIVE DATE (102)     0;11     Only active procedures are billable 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 370                             IA #: 370
  FILE NUMBER: 80.2                     GLOBAL ROOT: ICD(
  DATE CREATED: MAR 09, 1994            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA370                         ORIGINAL NUMBER: 370
  ID: ICD(
 GENERAL DESCRIPTION:   
  Request to store pointers to the DRG (#80.2) file from 
     Integrated Billing.  The pointers are needed to retrieve 
     data from the file at the time that claims are generated.  
  
     Request to directly reference the following fields in the DRG (#80.2) 
     file: 
  
     Field Name (#)        Location   Reason 
     ===================================================================
     NAME (.01)              0;1      Print and display the DRG number 
     DESCRIPTION (1)    ^ICD(ien,1,1,0)  Print and display the DRG name 
  
  STATUS: Retired
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

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
  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.  
  DATE ACTIVATED: JUL 18, 2014

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: 375                             IA #: 375
  FILE NUMBER: 424                      GLOBAL ROOT: PRC(424,
  DATE CREATED: SEP 02, 2003            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIA375
  ORIGINAL NUMBER: 375                  ID: PRC(424,
GLOBAL REFERENCE: PRC(424,D0,0)
FIELD NUMBER: .01                       FIELD NAME: AUTHORIZATION #
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: OBLICATION #
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: TRANSACTION TYPE
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: .05                       FIELD NAME: AUTHORIZATION BALANCE
  LOCATION: 0;5                         ACCESS: Write w/Fileman
FIELD NUMBER: .07                       FIELD NAME: DATE/TIME
  LOCATION: 0;7                         ACCESS: Write w/Fileman
FIELD NUMBER: .08                       FIELD NAME: USER
  LOCATION: 0;8                         ACCESS: Write w/Fileman
FIELD NUMBER: .1                        FIELD NAME: REFERENCE
  LOCATION: 0;10                        ACCESS: Write w/Fileman
FIELD NUMBER: .12                       FIELD NAME: AUTHORIZATION AMOUNT
  LOCATION: 0;12                        ACCESS: Write w/Fileman
FIELD NUMBER: .13                       FIELD NAME: ORIGINAL OBLIGATION AMOUNT
  LOCATION: 0;13                        ACCESS: Write w/Fileman
GLOBAL REFERENCE: PRC(424,D0,1)
FIELD NUMBER: 1.1                       FIELD NAME: COMMENTS
  LOCATION: 1;1                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: PRC(424,D0,2)
FIELD NUMBER: 4                         FIELD NAME: INTERFACE ID
  LOCATION: 2;2                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: PRC(424,'AD',
 GLOBAL DESCRIPTION:   Read access to check for an established obligation
 number.  
 GENERAL DESCRIPTION:   
      Request a one time DBA agreement for patch RMRP*2*4.  
  
      When a Prosthetics New Purchase is initiated the estimated 
      amount of the Purchase is calculated using the %Discount 
      and the total cost for all items or services.  On occasion 
      the estimated amount may be a four decimal digit 
      (e.g. 165.4321) after the calculation is done.  Once the 
      calculation is completed the New Purchase is posted to 
      IFCAP and a 1358 Daily Record entry is created.  
      When the Prosthetics New Purchase Estimated amount is 
      posted to IFCAP it is rejected by Fileman because the Data 
      Dictionary for the Authorization amount field for file 424 will 
      only accept a two decimal digit number.  A incomplete 1358 
      Daily Record is created and the Authorization number is 
      passed back to the Prosthetics New Purchase.  
  
      Upon Close out of the Prosthetics Purchase an error message 
      'Insufficient authorization funds to post payment' is 
      displayed and the Prosthetics Purchase cannot be closed out 
      because the estimated amount was not posted when the 
      Purchase was initiated.  
  
      Patch RMPR*2*4 corrects this problem by using $JUSTIFY to 
      ensure that the Estimated amount for the initial Prosthetics 
      Purchase is rounded to a two decimal digit.  
  
      Patch RMPR*2*4 also has a conversion routine that will 
      correct the Phantom 1358 entries and allow the Prosthetics 
      Service to close out purchases associated with the 
      incomplete 1358 Daily Record entries.  
  
      The Conversion Routine RMPSCON finds all 1358 daily record 
      entries created by the DHCP Prosthetics Package that are 
      missing the authorization balance.  Routine RMPSCON reads 
      and updates the following fields in Files #442 (PROCUREMENT 
      AND ACCOUNTING TRANSACTIONS), 442.3 (PURCHASE ORDER STATUS), 
      424 (1358 DAILY RECORD FILE), and 424.1 (1358 AUTHORIZATION 
      DETAIL).  
  STATUS: Retired
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Salt Lake City

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
 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

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
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
FIELD NUMBER: 8                         FIELD NAME: CURRENT STATUS
  LOCATION: 0;8                         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: 
  
  Revision History: 
   11/22/24 - Added CURRENT STATUS Field (#8) to ^PRCA(430,BN,0) Global 
 Reference for Automated Community Claims (ACC) project for use in IB*2.0*770.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
  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: 1                  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
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

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: 401                             IA #: 401
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA401
  ORIGINAL NUMBER: 401                  ID: SC(
GLOBAL REFERENCE: SC(
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 FIELD DESCRIPTION:   This pointer is used to associate procedures with
 clinics, and to flag clinics as non-billable.  
FIELD NUMBER: 8                         FIELD NAME: STOP CODE NUMBER
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Display the stop code associated with the clinic on
 reports 
FIELD NUMBER: 2502                      FIELD NAME: NON-COUNT CLINIC? (Y OR N)
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Non-count clinics are non-billable 
FIELD NUMBER: 2503                      FIELD NAME: CREDIT STOP CODE
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2505                      FIELD NAME: INACTIVATE DATE
  LOCATION: I;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2506                      FIELD NAME: REACTIVATE DATE
  LOCATION: I;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,'S',D1,1,
FIELD NUMBER: 30                        FIELD NAME: ELIGIBILITY OF VISIT
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The visit eligibility is checked before including the
 visit on reports.  
FIELD NUMBER: 310                       FIELD NAME: APPOINTMENT CANCELLED?
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Cancelled appointments are not billed 
 GENERAL DESCRIPTION:   It is understood that these references will need to be
 changed when Scheduling's new APIs are available.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  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                            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 
FIELD NUMBER: .13                       FIELD NAME: ELIGIBILITY OF ENCOUNTER
  LOCATION: 0;13                        ACCESS: Read w/Fileman
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: Under Revision
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.  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 11/13/25, effective with patch PX*1.0*244 for 
 documenting ICR in legacy code. 
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 11/14/25, effective with Class 
 HS.Local.VA.HC.ServiceBroker.DispatchVDIFVWSLEncounter Requesting read access
 to fields listed in this ICR.  

NUMBER: 403                             IA #: 403
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDCO3
  NAME: DBIA403                         ORIGINAL NUMBER: 403
  ID: SDCO3                             STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SET(SDOE)
 COMPONENT DESCRIPTION:   This call is used to develop a list of providers
 associated with an outpatient encounter.  
VARIABLES: SDOE                         TYPE: Input
 VARIABLES DESCRIPTION:   POINTER TO AN OUTPATIENT ENCOUNTER IN FILE #409.68 
VARIABLES: SDPRY(n)                     TYPE: Output
 VARIABLES DESCRIPTION:   =1^2, where 
       1=ptr to provider record in file #409.44 
       2=ptr to provider in file #200 
VARIABLES: SDCNT                        TYPE: Output
 VARIABLES DESCRIPTION:   # of elements in the SDPRY array.  
COMPONENT/ENTRY POINT: LIST(.SDPRY)
 COMPONENT DESCRIPTION:   There is no variable output from this call.  This
 call displays the list of providers in the SDPRY array.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 404                             IA #: 404
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDCO4
  NAME: DBIA404                         ORIGINAL NUMBER: 404
  ID: SDCO4                             STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SET(SDOE)
 COMPONENT DESCRIPTION:   This call is used to develop a list of diagnoses
 associated with an outpatient encounter.  
VARIABLES: SDOE                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to an outpatient encounter in file #409.68 
VARIABLES: SDDXY(n)                     TYPE: Output
 VARIABLES DESCRIPTION:   = 1^2, where 
      1 = ptr to diagnosis record in file #409.43 
      2 = ptr to diagnosis in file #80 
VARIABLES: SDCNT                        TYPE: Output
 VARIABLES DESCRIPTION:   # of elements in the SDDXY array 
COMPONENT/ENTRY POINT: LIST(.SDDXY)
 COMPONENT DESCRIPTION:   There is no variable output from this call.  This
 call displays the list of diagnoses in the SDDXY array.  
VARIABLES: SDDXY                        TYPE: Input
 VARIABLES DESCRIPTION:   The array defined in the call to SET^SDCO4(SDOE) 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Albany

NUMBER: 405                             IA #: 405
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: SDROUT1
  NAME: DBIA405                         ORIGINAL NUMBER: 405
  ID: SDROUT1                           STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   There is no variable output from this call.  This
 call is used by the Print Manager to print Routing Slips.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the patient in file #2 
VARIABLES: DIV                          TYPE: Input
 VARIABLES DESCRIPTION:   pointer to the division in file #40.8 
VARIABLES: SDPARMS('START')             TYPE: Input
 VARIABLES DESCRIPTION:   Start Date for appointments 
VARIABLES: SDPARMS('DO NOT CLOSE')      TYPE: Input
 VARIABLES DESCRIPTION:   1=don't close print device 
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Albany
SUBSCRIBING PACKAGE: REGISTRATION

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 

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
  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
SUBSCRIBING PACKAGE: EVENT CAPTURE
  DATE ACTIVATED: MAR 15, 2007

NUMBER: 408                             IA #: 408
  FILE NUMBER: 409.5                    GLOBAL ROOT: SDV(
  DATE CREATED: APR 04, 1994            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA408
  ORIGINAL NUMBER: 408                  ID: SDV(
GLOBAL REFERENCE: SDV(D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This date/time is used as the procedure date.  
FIELD NUMBER: 3                         FIELD NAME: DIVISION
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The division is used to select stops within a specified
 division 
GLOBAL REFERENCE: SDV('C',
 GLOBAL DESCRIPTION:   The "C" cross-reference is used to look at all stops for
 a patient.  
GLOBAL REFERENCE: SDV(D0,'CS',D1,0)
FIELD NUMBER: .01                       FIELD NAME: CLINIC STOP CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The stop code is printed on several reports 
FIELD NUMBER: 3                         FIELD NAME: ASSOCIATED CLINIC
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The clinic in which the stop occurred is printed on
 several reports 
FIELD NUMBER: 4                         FIELD NAME: ELIGIBILITY FOR VISIT
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The eligibility for the stop is printed on several
 reports 
FIELD NUMBER: 5                         FIELD NAME: APPOINTMENT TYPE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The appointment type is used to determine if the stop is
 billable 
FIELD NUMBER: 8                         FIELD NAME: OUTPATIENT ENCOUNTER
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The pointer to the outpatient encounter is used to
 determine the classification answers for the stop 
GLOBAL REFERENCE: SDV(D0,'CS','B',
 GLOBAL DESCRIPTION:   The "B" cross reference is to find all stop codes for a
 specific patient visit.  
 GENERAL DESCRIPTION:   It is understood that these references will need to be
 changed when Scheduling's new APIs are available.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Albany

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: 411                             IA #: 411
  FILE NUMBER: 409.43                   GLOBAL ROOT: SDD(409.43,
  DATE CREATED: APR 04, 1994            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA411
  ORIGINAL NUMBER: 411                  ID: SDD(409.43,
GLOBAL REFERENCE: SDD(409.43,'AO',
 GLOBAL DESCRIPTION:   Request to directly reference the "AO" cross reference
 of the OUTPATIENT DIAGNOSIS (#409.43) file.  The cross reference is used to
 find all diagnoses associated with an outpatient encounter.  The diagnoses are
 then added to bills.  
  STATUS: Retired                       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
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
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 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
 **************************************************************************
  
  
  
 HMP v.2.0 is using the Institution File Pointer (#.07) field as part of the
 patient sync process that syncs the data between the local VistA system and
 the JSON DATA System (JDS).  HMP collects admission data including the ward
 and institution.  
  
 The HMP code gets the division from the Ward Location File (#42), Division
 (#.015) field (pointer to Medical Center Division (#40.8) file) and then uses
 this value to get the value from the Institution File Pointer (#.07) field. 
 $$NS^XUAF4 is used to get the text name and station number for the
 institution.  
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
 SUBSCRIBING DETAILS:   The Existing Product Intake Program (EPIP) Project,
 Patch PSB*3.0*100 (Bar Code Medical Administration, PSB), will access the
 fields specified in ICR #417 for file #40.8, Medical Center Division.  
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   Added 7/15/21. DSS FY22 Annual Sustainment project,
 patch ECX*3*181, requires modifications to an existing report, Active MAS WARD
 report.  For the modifications, DSS requires FileMan and direct global read
 access to two fields: .07 Institution file pointer and 1 Facility Number.  
 Another ICR, 2817, covers the related access to 40.8 from the ECXMTL routine.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/24/24 effective with OR*3.0*561 patch so OR
 code can access the (#.07)INSTITUTION FILE POINTER field of the (#40.8)
 MEDICAL CENTER DIVISION file.  

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.  
FIELD NUMBER: 14                        FIELD NAME: INITIAL DATE OF SERVICE
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field determines the earliest date a billable event
 can occur.  
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: PRINCIPAL DX
  LOCATION: 70;10                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The PRINCIPAL DIAGNOSIS is printed on the Amb Proc check
 off sheet.  
FIELD NUMBER: 79.16                     FIELD NAME: SECONDARY DX 1
  LOCATION: 70;16                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The SECONDARY DIAGNOSIS 1 is printed on the Amb Proc
 check off sheet.  
FIELD NUMBER: 79.17                     FIELD NAME: SECONDARY DX 2
  LOCATION: 70;17                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The SECONDARY DIAGNOSIS 2 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: SECONDARY DX 3
  LOCATION: 70;18                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.19                     FIELD NAME: SECONDARY DX 4
  LOCATION: 70;19                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.201                    FIELD NAME: SECONDARY DX 5
  LOCATION: 70;20                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.21                     FIELD NAME: SECONDARY DX 6
  LOCATION: 70;21                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.22                     FIELD NAME: SECONDARY DX 7
  LOCATION: 70;22                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.23                     FIELD NAME: SECONDARY DX 8
  LOCATION: 70;23                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.24                     FIELD NAME: SECONDARY DX 9
  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 NUMBER: 6                         FIELD NAME: ICD 2
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: ICD 3
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: ICD 4
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: ICD 5
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
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.  
FIELD NUMBER: 11                        FIELD NAME: ICD 6
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 12                        FIELD NAME: ICD 7
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 13                        FIELD NAME: ICD 8
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: ICD 9
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: ICD 10
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
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 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
FIELD NUMBER: 9                         FIELD NAME: PROCEDURE CODE 6
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: PROCEDURE CODE 7
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: PROCEDURE CODE 8
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 12                        FIELD NAME: PROCEDURE CODE 9
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 13                        FIELD NAME: PROCEDURE CODE 10
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: PROCEDURE CODE 11
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: PROCEDURE CODE 12
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: PROCEDURE CODE 13
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 17                        FIELD NAME: PROCEDURE CODE 14
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 18                        FIELD NAME: PROCEDURE CODE 15
  LOCATION: 0;19                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 19                        FIELD NAME: PROCEDURE CODE 16
  LOCATION: 0;20                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 20                        FIELD NAME: PROCEDURE CODE 17
  LOCATION: 0;21                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 21                        FIELD NAME: PROCEDURE CODE 18
  LOCATION: 0;22                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 22                        FIELD NAME: PROCEDURE CODE 19
  LOCATION: 0;23                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 23                        FIELD NAME: PROCEDURE CODE 20
  LOCATION: 0;24                        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 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 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
FIELD NUMBER: 13                        FIELD NAME: OPERATION CODE 6
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: OPERATION CODE 7
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: OPERATION CODE 8
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: OPERATION CODE 9
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 17                        FIELD NAME: OPERATION CODE 10
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 18                        FIELD NAME: OPERATION CODE 11
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 19                        FIELD NAME: OPERATION CODE 12
  LOCATION: 0;19                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 20                        FIELD NAME: OPERATION CODE 13
  LOCATION: 0;20                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 21                        FIELD NAME: OPERATION CODE 14
  LOCATION: 0;21                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 22                        FIELD NAME: OPERATION CODE 15
  LOCATION: 0;22                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 23                        FIELD NAME: OPERATION CODE 16
  LOCATION: 0;23                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 24                        FIELD NAME: OPERATION CODE 17
  LOCATION: 0;24                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 25                        FIELD NAME: OPERATION CODE 18
  LOCATION: 0;25                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 26                        FIELD NAME: OPERATION CODE 19
  LOCATION: 0;26                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 27                        FIELD NAME: OPERATION CODE 20
  LOCATION: 0;27                        ACCESS: Direct Global Read & w/Fileman
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 
GLOBAL REFERENCE: DGPT(D0,71
FIELD NUMBER: 79.241                    FIELD NAME: SECONDARY DX 10
  LOCATION: 71;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.242                    FIELD NAME: SECONDARY DX 11
  LOCATION: 71;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.243                    FIELD NAME: SECONDARY DX 12
  LOCATION: 71;3                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.244                    FIELD NAME: SECONDARY DX 13
  LOCATION: 71;4                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.245                    FIELD NAME: SECONDARY DX 14
  LOCATION: 71;5                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.246                    FIELD NAME: SECONDARY DX 15
  LOCATION: 71;6                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.247                    FIELD NAME: SECONDARY DX 16
  LOCATION: 71;7                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.248                    FIELD NAME: SECONDARY DX 17
  LOCATION: 71;8                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.249                    FIELD NAME: SECONDARY DX 18
  LOCATION: 71;9                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.2491                   FIELD NAME: SECONDARY DX 19
  LOCATION: 71;10                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.24911                  FIELD NAME: SECONDARY DX 20
  LOCATION: 71;11                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.24912                  FIELD NAME: SECONDARY DX 21
  LOCATION: 71;12                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.24913                  FIELD NAME: SECONDARY DX 22
  LOCATION: 71;13                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.24914                  FIELD NAME: SECONDARY DX 24
  LOCATION: 71;14                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.24915                  FIELD NAME: SECONDARY DX 24
  LOCATION: 71;15                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPT(D0,82
FIELD NUMBER: 82.01                     FIELD NAME: POA PRINCIPAL DX
  LOCATION: 82;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.02                     FIELD NAME: POA SECONDARY DX 1
  LOCATION: 82;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.03                     FIELD NAME: POA SECONDARY DX 2
  LOCATION: 82;3                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.04                     FIELD NAME: POA SECONDARY DX 3
  LOCATION: 82;4                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.05                     FIELD NAME: POA SECONDARY DX 4
  LOCATION: 82;5                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.06                     FIELD NAME: POA SECONDARY DX 5
  LOCATION: 82;6                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.07                     FIELD NAME: POA SECONDARY DX 6
  LOCATION: 82;7                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.08                     FIELD NAME: POA SECONDARY DX 7
  LOCATION: 82;8                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.09                     FIELD NAME: POA SECONDARY DX 8
  LOCATION: 82;9                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.1                      FIELD NAME: POA SECONDARY DX 9
  LOCATION: 82;10                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.11                     FIELD NAME: POA SECONDARY DX 10
  LOCATION: 82;11                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.12                     FIELD NAME: POA SECONDARY DX 11
  LOCATION: 82;12                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.13                     FIELD NAME: POA SECONDARY DX 12
  LOCATION: 82;13                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.14                     FIELD NAME: POA SECONDARY DX 13
  LOCATION: 82;14                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.15                     FIELD NAME: POA SECONDARY DX 14
  LOCATION: 82;15                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.16                     FIELD NAME: POA SECONDARY DX 15
  LOCATION: 82;16                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.17                     FIELD NAME: POA SECONDARY DX 16
  LOCATION: 82;17                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.18                     FIELD NAME: POA SECONDARY DX 17
  LOCATION: 82;18                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.19                     FIELD NAME: POA SECONDARY DX 18
  LOCATION: 82;19                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.2                      FIELD NAME: POA SECONDARY DX 19
  LOCATION: 82;20                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.21                     FIELD NAME: POA SECONDARY DX 20
  LOCATION: 82;21                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.22                     FIELD NAME: POA SECONDARY DX 21
  LOCATION: 82;22                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.23                     FIELD NAME: POA SECONDARY DX 22
  LOCATION: 82;23                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.24                     FIELD NAME: POA SECONDARY DX 23
  LOCATION: 82;24                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.25                     FIELD NAME: POA SECONDARY DX 24
  LOCATION: 82;25                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPT(D0,'M',D1,81
FIELD NUMBER: 81.01                     FIELD NAME: ICD 11
  LOCATION: 81;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 81.02                     FIELD NAME: ICD 12
  LOCATION: 81;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 81.03                     FIELD NAME: ICD 13
  LOCATION: 81;3                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 81.04                     FIELD NAME: ICD 14
  LOCATION: 81;4                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 81.05                     FIELD NAME: ICD 15
  LOCATION: 81;5                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 81.06                     FIELD NAME: ICD 16
  LOCATION: 81;6                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 81.07                     FIELD NAME: ICD 17
  LOCATION: 81;7                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 81.08                     FIELD NAME: ICD 18
  LOCATION: 81;8                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 81.09                     FIELD NAME: ICD 19
  LOCATION: 81;9                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 81.1                      FIELD NAME: ICD 20
  LOCATION: 81;10                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 81.12                     FIELD NAME: ICD 22
  LOCATION: 81;12                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 81.11                     FIELD NAME: ICD 21
  LOCATION: 81;11                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 81.13                     FIELD NAME: ICD 23
  LOCATION: 81;13                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 81.14                     FIELD NAME: ICD 24
  LOCATION: 81;14                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 81.15                     FIELD NAME: ICD 25
  LOCATION: 81;15                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPT(D0,'M',D1,82
FIELD NUMBER: 82.01                     FIELD NAME: POA FOR ICD 1
  LOCATION: 82;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.02                     FIELD NAME: POA FOR ICD 2
  LOCATION: 82;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.03                     FIELD NAME: POA FOR ICD 3
  LOCATION: 82;3                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.04                     FIELD NAME: POA FOR ICD 4
  LOCATION: 82;4                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.05                     FIELD NAME: POA FOR ICD 5
  LOCATION: 82;5                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.06                     FIELD NAME: POA FOR ICD 6
  LOCATION: 82;6                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.07                     FIELD NAME: POA FOR ICD 7
  LOCATION: 82;7                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.08                     FIELD NAME: POA FOR ICD 8
  LOCATION: 82;8                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.09                     FIELD NAME: POA FOR ICD 9
  LOCATION: 82;9                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.1                      FIELD NAME: POA FOR ICD 10
  LOCATION: 82;10                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.11                     FIELD NAME: POA FOR ICD 11
  LOCATION: 82;11                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.12                     FIELD NAME: POA FOR ICD 12
  LOCATION: 82;12                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.13                     FIELD NAME: POA FOR ICD 13
  LOCATION: 82;13                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.14                     FIELD NAME: POA FOR ICD 14
  LOCATION: 82;14                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.15                     FIELD NAME: POA FOR ICD 15
  LOCATION: 82;15                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.16                     FIELD NAME: POA FOR ICD 16
  LOCATION: 82;16                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.17                     FIELD NAME: POA FOR ICD 17
  LOCATION: 82;17                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.18                     FIELD NAME: POA FOR ICD 18
  LOCATION: 82;18                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.19                     FIELD NAME: POA FOR ICD 19
  LOCATION: 82;19                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.2                      FIELD NAME: POA FOR ICD 20
  LOCATION: 82;20                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.21                     FIELD NAME: POA FOR ICD 21
  LOCATION: 82;21                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.22                     FIELD NAME: POA FOR ICD 22
  LOCATION: 82;22                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.23                     FIELD NAME: POA FOR ICD 23
  LOCATION: 82;23                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.24                     FIELD NAME: POA FOR ICD 24
  LOCATION: 82;24                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 82.25                     FIELD NAME: POA FOR ICD 25
  LOCATION: 82;25                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPT(D0,'P',D1,1
FIELD NUMBER: 24                        FIELD NAME: PROCEDURE CODE 21
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 25                        FIELD NAME: PROCEDURE CODE 22
  LOCATION: 1;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 26                        FIELD NAME: PROCEDURE CODE 23
  LOCATION: 1;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 27                        FIELD NAME: PROCEDURE CODE 24
  LOCATION: 1;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 28                        FIELD NAME: PROCEDURE CODE 25
  LOCATION: 1;5                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPT(D0,'S',D1,1
FIELD NUMBER: 28                        FIELD NAME: OPERATION CODE 21
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 29                        FIELD NAME: OPERATION CODE 22
  LOCATION: 1;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 30                        FIELD NAME: OPERATION CODE 23
  LOCATION: 1;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 31                        FIELD NAME: OPERATION CODE 24
  LOCATION: 1;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 32                        FIELD NAME: OPERATION CODE 25
  LOCATION: 1;5                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: COMPUTED
FIELD NUMBER: 9                         FIELD NAME: DRG
  LOCATION: COMPUTED                    ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Only Integrated Billing has permission to reference this
 field.  
 GENERAL DESCRIPTION:   This ICR supports access to PTF (#45) file
 cross-references and data fields.  Data fields may be accessed using a Direct
 Global Read or with Fileman.  
     
 NOTE: Existing subscribers to this ICR are grandfathered in for accessing PTF
 (#45) Diagnosis, Present on Admission (POA), Procedure code, and Surgical code
 data fields. However, current subscribers are encouraged to use ICR 6130 in
 the future.  ICR 6130 supports the use of PTF Utility API's to access PTF
 (#45) Diagnosis, Present on Admission (POA) indicators, Procedure code, and
 Surgical code fields, instead of accessing fields directly or using Fileman. 
 New subscribers should not be added to this ICR if PTF (#45) file data fields
 may be obtained using the PTF Utility API's supported by ICR 6130.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PTF
KEYWORDS: DGPT
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
 SUBSCRIBING DETAILS:   Added Initial Date of Service effective with
 IB*2.0*714, released 4/6/22 without Custodian approval.  
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 

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                            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.  
FIELD NUMBER: .27                       FIELD NAME: VISIT FILE ENTRY
  LOCATION: 0;27                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field points to the entry in the VISIT file
 (#9000010) associated with the patient 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
KEYWORDS: PATIENT MOVEMENT
KEYWORDS: DGPM
KEYWORDS: COMPACT ACT
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 
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   
  ADDED 12/15/2021, effective with DSSV*1.1 
  DSS Class 3 product  
  The justification for using direct global 
  read vs FileMan is because this code is called 
  multiple times in a grid of data 
  (hundreds of records).  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 8/22/24, effective with PX*1.0*241 

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
  STATUS: Active                        DURATION: Till Otherwise Agreed
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^11, 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] 
                11 = Medal of Honor [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
  DATE ACTIVATED: MAR 04, 2011

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
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
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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 
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   PATIENT CARE ENCOUNTER, with PX*1.0*244 releasing
 around 11/1/25, is documenting that it has been doing a global read on the MAS
 ELIGIBILITY CODE field in file 8.  

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,
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
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

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
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

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,
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
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 
  DATE ACTIVATED: APR 09, 2013

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 

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
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be referencing the Name (#.01) field in the
 MAS Movement Transaction Type (#405.3) file in VIAB BMS RPC.  

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 EMAIL GROUP 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

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 EMAIL GROUP 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

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                            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: Retired                       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                         ROUTINE: VAQUPD25
  NAME: DBIA439-B                       ORIGINAL NUMBER: 439
  ID: VAQUPD25                          STATUS: Retired
  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.DNS 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: 442                             IA #: 442
  DATE CREATED: APR 11, 1994            CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PPPFMX2                      NAME: DBIA439-D
  ORIGINAL NUMBER: 439                  ID: PPPFMX2
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PDXTRIG(.)
VARIABLES: TRANPTR                      TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to VAQ - TRANSACTION file 
VARIABLES: MODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Which 'logic' to use (SET or KILL) 1 = SET (default) 
 0 = KILL 
SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  ISC: Albany

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                            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: Retired                       DURATION: Till Otherwise Agreed
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                            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: Retired                       DURATION: Till Otherwise Agreed
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                            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: Retired                       DURATION: Till Otherwise Agreed
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: Controlled Subscription
  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
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   Added 12/21/21, effective with DSSV*1.0*1. DSS Class 3
 product. Document Only.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Added 12/4/24 effective with TIU*1*369 patch to allow
 determination if a value exists in the NAME (#.01) field to satisfy
 MAKE^TIUSRVP API.  

NUMBER: 448                             IA #: 448
  FILE NUMBER: 9000011                  GLOBAL ROOT: AUPNPROB(
  DATE CREATED: APR 12, 1994
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: DBIA448
  ORIGINAL NUMBER: 448                  ID: AUPNPROB(
GLOBAL REFERENCE: AUPNPROB(D0,0)
FIELD NUMBER: .02                       FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Points to #9000001  PATIENT/IHS FILE 
 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: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROBLEM LIST       ISC: Salt Lake City

NUMBER: 449                             IA #: 449
  DATE CREATED: APR 12, 1994            CUSTODIAL PACKAGE: 1
  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: 450                             IA #: 450
  DATE CREATED: MAY 09, 1995            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Other                           NAME: DBIA450
  ORIGINAL NUMBER: 450
 GENERAL DESCRIPTION:   The CPT package would like to make the following
 integration request with the Scheduling package: 
  
     Request to export the following scheduling routine 
     change to Scheduling v5.3 with the CPT annual release: 
  
     Routine             Reason 
     -----------------------------------------------------------------------
     SDAMBAE3            Update the effective date reference for current 
                         release.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CPT/HCPCS CODES    ISC: Albany

NUMBER: 451                             IA #: 451
  FILE NUMBER: 409.71                   GLOBAL ROOT: SD(409.71,
  DATE CREATED: APR 12, 1994            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA451
  ORIGINAL NUMBER: 451                  ID: SD(409.71,
GLOBAL REFERENCE: SD(409.71
 GLOBAL DESCRIPTION:   
  
  
 GENERAL DESCRIPTION:   Reason:  To populate the Ambulatory Procedure file with
 all the CPT codes.  
  STATUS: Retired                       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
SUBSCRIBING PACKAGE: CPT/HCPCS CODES    ISC: Albany

NUMBER: 453                             IA #: 453
  FILE NUMBER: 121.2                    GLOBAL ROOT: GMR(121.2,
  DATE CREATED: APR 12, 1994            CUSTODIAL PACKAGE: PROGRESS NOTES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: DBIA453
  ORIGINAL NUMBER: 453                  ID: GMR(121.2,
GLOBAL REFERENCE: GMR(121.2,'B',
 GLOBAL DESCRIPTION:   Direct global read access to the "B" cross-reference
 will be used to determine the internal entry number for that record.  
GLOBAL REFERENCE: GMR(121.2,D0,0)
FIELD NUMBER: .02                       FIELD NAME: PROGRESS NOTE TYPE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   A "one time only" change to the .01 value of File 121.2.  
 GENERAL DESCRIPTION:   The Adverse Reaction Tracking package (ART) needs to be
 able to check for the existence of the ALLERGY/ADVERSE REACTION entry in the B
 cross reference in the Generic Progress Notes Title (#121.2) file. The ART
 v4.0 post-init routine will change the .01 value of this File 121.2 entry to 
 ADVERSE REACTION/ALLERGY. After ART v4.0 is installed, ART will check for the
 existence of the new value in the B cross reference of File 121.2.  
  
 Also, ART needs to do a direct global read of the second piece of the zero
 node of this File 121.2 entry to determine the PROGRESS NOTE TYPE value.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

NUMBER: 454                             IA #: 454
  FILE NUMBER: 121.1                    GLOBAL ROOT: GMR(121.1,
  DATE CREATED: APR 12, 1994            CUSTODIAL PACKAGE: PROGRESS NOTES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: DBIA453
  ORIGINAL NUMBER: 453                  ID: GMR(121.1,
GLOBAL REFERENCE: GMR(121.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PROGRESS NOTE TYPE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Direct global access read to determine if entry is
 GENERAL NOTE.  
 GENERAL DESCRIPTION:   The Adverse Reaction Tracking (ART) package needs to
 look at first piece of the Generic Progress Notes Type (121.1) file to find
 the GENERAL NOTE entry.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

NUMBER: 455                             IA #: 455
  DATE CREATED: FEB 13, 1996            CUSTODIAL PACKAGE: PROGRESS NOTES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMRPART
  NAME: GMRPART                         ORIGINAL NUMBER: 455
  ID: GMRPART
 GENERAL DESCRIPTION:   The Adverse Reaction Tracking (ART) package will use
 the GMRPART utility to generate a progress note with a title of
 ALLERGY/ADVERSE REACTION. ART will pass the necessary data, by reference, to
 the GMRPART routine with the exception of the text of the progress note which
 will exist in the TMP global (^TMP("GMRP",$J,) at the time GMRPART is called.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PN
 COMPONENT DESCRIPTION:   The Progress Note utility call is: 
                    
 $$PN^GMRPART(GMRPDFN,GMRPDUZ,GMRPDT,GMRPTTL,LOC) 
VARIABLES: GMRPDUZ                      TYPE: Input
 VARIABLES DESCRIPTION:   The user's DUZ number (File #200).  
VARIABLES: GMRPDFN                      TYPE: Input
 VARIABLES DESCRIPTION:   The patient's internal entry number (File #2).  
VARIABLES: GMRPDT                       TYPE: Input
 VARIABLES DESCRIPTION:   The date/time (FileMan format) of the Progress Note.  
VARIABLES: GMRPTTL                      TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the Progress Note Title
 (File #121.2).  
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the Hospital Location
 for the patient (File #44).  
VARIABLES: TMP('GMRP',$J,               TYPE: Input
 VARIABLES DESCRIPTION:   This temporary global contains the text of the
 Progress Note.  
VARIABLES: GMRPIFN                      TYPE: Output
 VARIABLES DESCRIPTION:   This variable is passed by reference. If GMRPIFN=-1,
 then no progress note was created. If GMRPIFN=0 then a progress note was
 created, but not signed.  
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

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
  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
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
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
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
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
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
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
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
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham

NUMBER: 466                             IA #: 466
  DATE CREATED: OCT 20, 2003            CUSTODIAL PACKAGE: IMAGING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Routine                         ROUTINE: MAGMIM
  NAME: DBIA466                         ORIGINAL NUMBER: 466
  ID: MAGMIM
 GENERAL DESCRIPTION:   The Medicine package has been given permission by the
 Imaging package to do the following: 
  
 Make calls to the ^MAGMIM routine through the ^MCMAG routine.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MAGMIM
 COMPONENT DESCRIPTION:   ^MAGMIM routine allows the set-up of the variables
 necessary for image capture.  The routine is used during the Image Capture
 option of the various Medicine modules.  This option allows the imaging
 package to associate images with the various Medicine procedures.  
VARIABLES: MCFILE                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the file number of the procedure.  
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   EN1^MAGMIM entry-point is the same as MAGMIM with the
 expectation that it happens after the editing of a Medicine procedure.  
VARIABLES: MCFILE                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the file number for the current procedure.  
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Washington/Silver Spring

NUMBER: 467                             IA #: 467
  DATE CREATED: OCT 20, 2003            CUSTODIAL PACKAGE: IMAGING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Routine                         ROUTINE: MAGDISP
  NAME: DBIA467                         ORIGINAL NUMBER: 467
  ID: MAGDISP
 GENERAL DESCRIPTION:   The Medicine package has been given permission by the
 Imaging package to do the following: 
  
 Make calls to the ^MAGDISP routine through the ^MCMAG routine.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MAGDISP
 COMPONENT DESCRIPTION:   ^MAGDISP routine allows the display of images with a
 Medicine procedure during the printing of that procedure.  
VARIABLES: MCFILE                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the file number for the current procedure.  
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Washington/Silver Spring

NUMBER: 468                             IA #: 468
  DATE CREATED: OCT 20, 2003            CUSTODIAL PACKAGE: IMAGING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Routine                         ROUTINE: MAGSUM
  NAME: DBIA468                         ORIGINAL NUMBER: 468
  ID: MAGSUM
 GENERAL DESCRIPTION:   The Medicine package has been given permission by the
 Imaging package to the following: 
  
   Make calls to the ^MAGSUM routine through the ^MCMAG routine.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MAGSUM
 COMPONENT DESCRIPTION:   ^MAGSUM routine displays a series of patient images. 
 This routine is used during the Summary of Patient Procedures options.  
VARIABLES: MCFILE                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the file number for the current procedure.  
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Washington/Silver Spring

NUMBER: 469                             IA #: 469
  DATE CREATED: OCT 20, 2003            CUSTODIAL PACKAGE: IMAGING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Other                           NAME: DBIA469
  ORIGINAL NUMBER: 469
 GENERAL DESCRIPTION:   The Medicine package has permission by the Imaging
 package to Kill the ^TMP("MAG",$J,"COL") and ^TMP("MAG",$J,"ROW") globals
 within the Medicine package upon exiting the Summary of Patient Procedures
 options.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Washington/Silver Spring

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
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
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham

NUMBER: 473                             IA #: 473
  FILE NUMBER: 52.6                     GLOBAL ROOT: PS(52.6,
  DATE CREATED: APR 26, 1994
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA473
  ORIGINAL NUMBER: 473                  ID: PS(52.6,
GLOBAL REFERENCE: PS(52.6,D0,0)
FIELD NUMBER: 1                         FIELD NAME: GENERIC DRUG
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   D&PPM uses the IV Additives file to obtain the Generic
 Drug name.  
  STATUS: Retired
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham

NUMBER: 474                             IA #: 474
  FILE NUMBER: 52.7                     GLOBAL ROOT: PS(52.7,
  DATE CREATED: APR 26, 1994
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA473
  ORIGINAL NUMBER: 473                  ID: PS(52.7,
GLOBAL REFERENCE: PS(52.7,D0,0)
FIELD NUMBER: 1                         FIELD NAME: GENERIC DRUG
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Pharmacy Benefits Management uses the IV solutions file
 to obtain the generic drug name.  
  STATUS: Retired
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
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham

NUMBER: 476                             IA #: 476
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: MAY 10, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA476
  ORIGINAL NUMBER: 476                  ID: DPT(
GLOBAL REFERENCE: DPT(DFN,.311)
FIELD NUMBER: .31115                    FIELD NAME: EMPLOYMENT STATUS
  LOCATION: .311,15                     ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DFN,.31)
FIELD NUMBER: .3192                     FIELD NAME: COVERED BY HEALTH INSURANCE
  LOCATION: .31,11                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DFN,.11)
FIELD NUMBER: .115                      FIELD NAME: STATE
  LOCATION: .11,5                       ACCESS: Read w/Fileman
FIELD NUMBER: .117                      FIELD NAME: COUNTY
  LOCATION: .11,7                       ACCESS: Read w/Fileman
FIELD NUMBER: .116                      FIELD NAME: ZIP CODE
  LOCATION: .11,6                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DFN,.36)
FIELD NUMBER: .361                      FIELD NAME: PRIMARY ELIGIBILITY CODE
  LOCATION: .36,1                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DFM,VET)
FIELD NUMBER: 1901                      FIELD NAME: VETERAN (Y/N)?
  LOCATION: VET,1                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DFN,.321)
FIELD NUMBER: .32101                    FIELD NAME: VIETNAM SERVICE INDICATED?
  LOCATION: .321,1                      ACCESS: Read w/Fileman
FIELD NUMBER: .32102
  FIELD NAME: AGENT ORANGE EXPOS. INDICATED?
  LOCATION: .321,2                      ACCESS: Read w/Fileman
FIELD NUMBER: .32103
  FIELD NAME: RADIATION EXPOSURE INDICATED?
  LOCATION: .321,3                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DFN,.52)
FIELD NUMBER: .525                      FIELD NAME: POW STATUS INDICATED?
  LOCATION: .52,5                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DFN,.32)
FIELD NUMBER: .323                      FIELD NAME: PERIOD OF SERVICE
  LOCATION: .32,3                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DFN,0)
FIELD NUMBER: .14                       FIELD NAME: CURRENT MEANS TEST STATUS
  LOCATION: 0,14                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The DSS operations committee has identified several
 data elements in the patient file to be extracted and sent to the commercial
 software.  We request read access to these fields.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: EVENT CAPTURE      ISC: Birmingham

NUMBER: 477                             IA #: 477
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG(
  DATE CREATED: JUN 13, 1994
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA477
  ORIGINAL NUMBER: 477                  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: 3                         FIELD NAME: DEA, SPECIAL HDLG
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSDRUG(DA,2)
FIELD NUMBER: 31                        FIELD NAME: NDC
  LOCATION: 2;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSDRUG(DA,660)
FIELD NUMBER: 16                        FIELD NAME: PRICE PER DISPENSE UNIT
  LOCATION: 660;6                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 14.5                      FIELD NAME: DISPENSE UNIT
  LOCATION: 660;8                       ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   The entire 660 node is read into a local variable. The
 fields above are then used.  
GLOBAL REFERENCE: PSDRUG(DA,ND)
FIELD NUMBER: 20                        FIELD NAME: NATIONAL DRUG FILE ENTRY
  LOCATION: ND;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 22                        FIELD NAME: PSNDF VA PRODUCT NAME ENTRY
  LOCATION: ND;3                        ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   The entire ND node is read into a local variable. The
 fields above are then used.  
 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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
  
 DSS Extracts will reference the following data from the DRUG file (#50).  
   
 DSS uses the "B" cross reference on the GENERIC NAME field.  
   
 The DSS Extracts IV EXTRACT DATA file (#728.113) and UNIT DOSE EXTRACT DATA
 file (#728.904) contain a field, DRUG, which is a pointer to the DRUG file
 (#50).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

NUMBER: 478                             IA #: 478
  FILE NUMBER: 3.1                      GLOBAL ROOT: DIC(3.1
  DATE CREATED: JUN 13, 1994            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA478
  ORIGINAL NUMBER: 478                  ID: DIC(3.1
GLOBAL REFERENCE: DIC(3.1,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 title file for
 provider identificaiton for DSS 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  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
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
SUBSCRIBING PACKAGE: VISIT TRACKING     ISC: Albany

NUMBER: 481                             IA #: 481
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA481
  ORIGINAL NUMBER: 481                  ID: SC(
GLOBAL REFERENCE: SC(D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TYPE
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3.5                       FIELD NAME: DIVISION
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: STOP CODE
  ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,SL)
FIELD NUMBER: 1916                      FIELD NAME: PRINCIPAL CLINIC
  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 Field 
    ----------------
   #22 Hospital Location      Pointer to the Hospital Location File #44 
                              Visit Tracking code checks the following fields 
                              in the Hospital Location file: 
  
                              Field / Name 
                              -----------------------
                              2       Type 
                              3.5     Division 
                              8       Stop Code 
                              1916    Principal Clinic 
        
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
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
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
SUBSCRIBING PACKAGE: VISIT TRACKING     ISC: Albany
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 10/2/19 for Mental Health's Suicide Prevention
 Project (SPP) adding new functionality in patch YS*5.01*140 (MHA Forms) to
 provide clinicians with a web-based interface to submit a form as an Unsigned
 Note.  

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
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
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
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: 1                  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
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[<number of days>]
           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(<xxx>) 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(<ien>)                  TYPE: Output
 VARIABLES DESCRIPTION:   
     N^S[^1]
          where:
          -1 = <Visit not created>
          -2 = <Visit Tracking Parameters not set to ON for a package>
          N = <internal entry number of visit> 
          S = <value of .01 field of visit>
                    1 = <indicates that a new visit was added>
VARIABLES: VSIT(<ien>,xxx)              TYPE: Output
 VARIABLES DESCRIPTION:   
     where:
                    <ien> = IEN of visit.
                    <xxx> = 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) 
VARIABLES: VSIT(IR)                     TYPE: Input
 VARIABLES DESCRIPTION:   IONIZING RADIATION EXPOSURE(set) 
VARIABLES: VSIT(MST)                    TYPE: Input
 VARIABLES DESCRIPTION:   MILITARY SEXUAL TRAUMA (set) 
VARIABLES: VSIT(CV)                     TYPE: Input
 VARIABLES DESCRIPTION:   COMBAT VETERAN (set) 
VARIABLES: VSIT(SHAD)                   TYPE: Input
 VARIABLES DESCRIPTION:   PROJ 112/SHAD (set) 
VARIABLES: VSIT(CLV)                    TYPE: Input
 VARIABLES DESCRIPTION:   CAMP LEJEUNE EXPOSURE (set) 

NUMBER: 490                             IA #: 490
  DATE CREATED: SEP 19, 1995
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: vsitoe
  NAME: DBIA490                         ORIGINAL NUMBER: 490
  ID: vsitoe
 GENERAL DESCRIPTION:   This is an entry point for getting a list of visits
 that match defined criteria.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LST
VARIABLES: VDT                          TYPE: Input
 VARIABLES DESCRIPTION:   
   Visit Date/Time in FM format.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   
   Patient File Pointer.  
VARIABLES: PRAM                         TYPE: Input
 VARIABLES DESCRIPTION:   
   The routine ^VSIT uses extrinsic functions.  VSIT(0) will be passed 
   to the parameter PRAM.  $$GET(VDT,DFN,PRAM,.VSIT) 
   
   VSIT(0)  A string of characters which defines how the visit processor 
   will function.  
     
            F - Force adding a new entry 
            I - Interactive mode 
            E - Use pt's primary eligibility if not passed on call 
                w/VSIT("ELG") 
            N - Allow creation of a new visit 
            D - Look back "n" number of days for a match, default is one.  
                e.g. VSIT(0)="D5" (look back 5 days) 
            M - Impose criteria on matching or creation of visits.  
                Used the VSIT("XXX") array: 
                - If trying to match with existing visit, matching elements 
                  must equal their corresponding field.  
                - If creating a new visit, will use array elements as defaults 
                  or stuff values depending if in interactive mode or not 
                  and the exact field.  
  
VARIABLES: VSIT                         TYPE: Input
 VARIABLES DESCRIPTION:   
   Array w/mnemonic subscript.  
VARIABLES: VSIT(IEN)                    TYPE: Input
 VARIABLES DESCRIPTION:   
  NUMBER (internal entry number) 
VARIABLES: VSIT(VDT)                    TYPE: Input
 VARIABLES DESCRIPTION:   
  VISIT/ADMID DATE&TIME (date) 
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 (pointer to PATIENT file #2) 
          (IHS file DINUM'ed to PATIENT file #2) 
VARIABLES: VSIT(INS)                    TYPE: Input
 VARIABLES DESCRIPTION:   
  LOC.OF ENCOUNTER (pointer to LOCATION file #9999999.06) 
  (IHS file DINUM'ed to INSTITUTION file #4) 
VARIABLES: VSIT(SVC)                    TYPE: Input
 VARIABLES DESCRIPTION:   
  SERVICE CATEGORY (set) 
VARIABLES: VSIT(CLN)                    TYPE: Input
 VARIABLES DESCRIPTION:   
  CLINIC (pointer to CLINIC STOP file #40.7) 
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 to VISIT file) 
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:   
  LEVEL OF SERVICE (pointer to CPT CODE file) 
VARIABLES: VSIT(COD)                    TYPE: Input
 VARIABLES DESCRIPTION:   
  CHECK OUT DATE & TIME (date) 
VARIABLES: VSIT(ELG)                    TYPE: Input
 VARIABLES DESCRIPTION:   
  ELIGIBILITY (pointer to ELIGIBILITY CODE file #8) 
VARIABLES: VSIT(LOC)                    TYPE: Input
 VARIABLES DESCRIPTION:   
  HOSPITAL LOCATION (pointer to HOSPITAL LOCATION file #44) 
VARIABLES: VSIT(USR)                    TYPE: Input
 VARIABLES DESCRIPTION:   
  CREATED BY USER (pointer to USER file #200) 
VARIABLES: VSIT(OPT)                    TYPE: Input
 VARIABLES DESCRIPTION:   
  OPTION USED TO CREATE (pointer to OPTION file #19) 
VARIABLES: VSIT(AMT)                    TYPE: Input
 VARIABLES DESCRIPTION:   
  AMOUNT BILLED (number) 
VARIABLES: VSIT(OUT)                    TYPE: Input
 VARIABLES DESCRIPTION:   
  OUTSIDE LOCATION (free text) 
VARIABLES: VSIT(SC)                     TYPE: Input
 VARIABLES DESCRIPTION:   
  SERVICE CONNECTED (set) 
VARIABLES: VSIT(AO)                     TYPE: Input
 VARIABLES DESCRIPTION:   
  AGENT ORANGE EXPOSURE (set) 
VARIABLES: VSIT(IR)                     TYPE: Input
 VARIABLES DESCRIPTION:   
  IONIZING RADIATION EXPOSURE (set) 
VARIABLES: VSIT(EC)                     TYPE: Input
 VARIABLES DESCRIPTION:   
  PERSIAN GULF EXPOSURE (set) 
COMPONENT/ENTRY POINT: VSITAPI()
 COMPONENT DESCRIPTION:   D VSITAPI^VSITOE( DFN, START D/T, END D/T, H.L.,Last) 
 If no START D/T, END D/T,HL, Last--- then all visits for patient in reverse
 chron order.  If START D/T, END D/T are passed but no HL --- then all with in
 the time range for the patient.  If  START D/T, END D/T, HL and not Last ---
 then all for Location If all parameters are passed then last visit for clinic
 is assumed.  Requested returned array in, ^TMP("VSIT",$J, Visit IEN,
 numerical/chronical order) =  "Date Time of visit^location ien;location
 text^Clinic ien;clinic name^service conneted flag^patient status in/out" All
 fields will be reported if known, if not known reported as "".  It is
 acknowledged that the visits will be in strict reverse order by date.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   
     PATIENT NAME (pointer PATIENT file #9000001)
               (IHS file DINUMed to PATIENT file #2) 
VARIABLES: Start Date/Time              TYPE: Input
 VARIABLES DESCRIPTION:   Start date and or time for looking for a visit.  
VARIABLES: End Date/Time                TYPE: Input
 VARIABLES DESCRIPTION:   End date and or time for looking for a visit.  
VARIABLES: Hospital Location pointer    TYPE: Input
 VARIABLES DESCRIPTION:   
     HOSPITAL LOCATION (pointer HOSPITAL LOCATION file #44)
VARIABLES: Last Only                    TYPE: Input
 VARIABLES DESCRIPTION:   Pass "L" for last only for patient 

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
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
SUBSCRIBING PACKAGE: EVENT CAPTURE      ISC: Birmingham

NUMBER: 493                             IA #: 493
  FILE NUMBER: 40.9                     GLOBAL ROOT: DIC(40.9,
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA493
  ORIGINAL NUMBER: 493                  ID: DIC(40.9,
GLOBAL REFERENCE: DIC(40.9,DA,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The patient oriented extracts in DSS distinguish
 between inpatients and outpatients.  To make this distinction, a field in the
 extract log points to the LOCATION TYPE file (40.9).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: EVENT CAPTURE      ISC: Birmingham
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

NUMBER: 494                             IA #: 494
  FILE NUMBER: 13                       GLOBAL ROOT: DIC(13,
  DATE CREATED: JUN 13, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA494
  ORIGINAL NUMBER: 494                  ID: DIC(13,
GLOBAL REFERENCE: DIC(13,DA,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Among the demographic data extracted for DSS, patient
 religion is one element.  To this end, we request read access to the .01 field
 of the RELIGION file (13) 
  
 The DSS Extracts ADMISSIONS EXTRACT file (#727.802) and ADMISSION SETUP 
 EXTRACT file (#727.82) contain a field, RELIGION, which is a pointer to the
 RELIGION file (#13).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  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: Controlled Subscription
  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
FIELD NUMBER: 7                         FIELD NAME: VERIFIED DATE
  LOCATION: 0;7                         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
GLOBAL REFERENCE: RARPT(D0,2050,0
FIELD NUMBER: 2005                      FIELD NAME: IMAGE
  LOCATION: 2005;0                      ACCESS: Read w/Fileman
FIELD NUMBER: .01                       FIELD NAME: IMAGE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   RADIOLOGY REPORTS FILE                                  
             Amended:  11/25/22 to add Field 7 VERIFIED DATE for COMPREHENSIVE
 CARE COORDINATION 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RA-CLASS 3
KEYWORDS: DSSV CLASS 3
KEYWORDS: ROR
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   C3 is requesting access to the following field from
 file 74: 5 REPORT STATUS and to add field 7 VERIFIED DATE ADDED 11/25/2022,
 effective with DSSV*1.1 AMENDED 10/5/2023, to add Subfile 74.02005: .01 IMAGE 
 DSS Class 3 product Document Only 

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
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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,
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: 505                             IA #: 505
  FILE NUMBER: 19.1                     GLOBAL ROOT: DIC(19.1,
  DATE CREATED: JUL 27, 1989            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA5-B
  ORIGINAL NUMBER: 5                    ID: DIC(19.1,
GLOBAL REFERENCE: DIC(19.1
 GLOBAL DESCRIPTION:   Used to access security keys.  
 GENERAL DESCRIPTION:   This ICR had been retired, but was reactivated due to a
 review of patch OR*3*397, where SQA found ORUPREF1 had some pre-existing code
 (probably going back to the original package release) that reads from file
 19.1.  The reads are to: 
  1.      ^DIC(19.1,"B",X,D0) ? B cross-reference 
  2.      ^DIC(19.1,D0,1,D1,0) ? Description 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 506                             IA #: 506
  FILE NUMBER: 3                        GLOBAL ROOT: DIC(3,
  DATE CREATED: JUL 27, 1989            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA5-C
  ORIGINAL NUMBER: 5                    ID: DIC(3,
GLOBAL REFERENCE: DIC(3
 GLOBAL DESCRIPTION:   Used to print user name.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  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: 1                  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: 509                             IA #: 509
  GLOBAL ROOT: DIC(                     DATE CREATED: NOV 07, 2005
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  NAME: DBIA6-C                         ORIGINAL NUMBER: 6
  ID: DIC(
 GENERAL DESCRIPTION:   Fileman calls.  
  STATUS: Retired                       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: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DISV
  ORIGINAL NUMBER: 6                    ID: DISV(
 GENERAL DESCRIPTION:   Used to process 'space-bar return' on user input.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  Added read access to
 ^DISV(DUZ,"^TIU("_FILE_",") for TIU*1*197.  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:   10-23-2006 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 
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   REGISTRATION: 
  
 After a user selects a patient in the PTF file (#45) in routine DGPTF, the 
 routine will set the following DISV node for recall: 
  
 ^DISV(DUZ,"^DPT(") to recall the selected patient 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
 **************************************************************************
  
  
 Health MGMT Platform (HMP) uses ^DISV(DUZ, "HMPM EVT QUE MGR", X), where X can
 be HMPSRV, HMPDOM, HMPFIL, HMPDFN, HMPLIM.  This allows HMP to recall default
 values for the user in routine HMPEQLM.  READ and WRITE access to ^DISV(DUZ,
 "HMPM EVT QUE MGR", X) allowed.  
  DATE ACTIVATED: FEB 29, 2012

NUMBER: 511                             IA #: 511
  GLOBAL ROOT: DIC(                     DATE CREATED: JUL 27, 1989
  CUSTODIAL PACKAGE: 1                  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: 516                             IA #: 516
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG(
  DATE CREATED: MAR 13, 1989
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA34-B
  ORIGINAL NUMBER: 34                   ID: PSDRUG(
 GENERAL DESCRIPTION:   Direct references are made to the globals to get
 allergy information.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 517                             IA #: 517
  FILE NUMBER: 57                       GLOBAL ROOT: DIC(57
  DATE CREATED: MAR 13, 1989            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA34-C
  ORIGINAL NUMBER: 34                   ID: DIC(57
 GENERAL DESCRIPTION:   Direct references are made to the globals to get
 allergy information.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 518                             IA #: 518
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA36-B
  ORIGINAL NUMBER: 36                   ID: SC(
 GENERAL DESCRIPTION:   
    ^SC(      Used to get patient variables 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

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: FACILITY TREATING SPECIALTY (#45.7) File Access
  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
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (Kiosks) VPS will use the "B" cross
 reference on file #45.7 to get the IEN of a Facility Treating Specialty.  
  DATE ACTIVATED: JUL 17, 2015

NUMBER: 520                             IA #: 520
  DATE CREATED: MAY 25, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: LRUPACA
  NAME: DBIA59-B                        ORIGINAL NUMBER: 59
  ID: LRUPACA
 GENERAL DESCRIPTION:   - ECT namspaced option runs routine ^LRUPACA 
     Enter ACTION: S DIC=68,DIC(0)="QEAM" D ^DIC K DIC I Y>0 S LRAA=+Y, 
                   LRAA(1)=$P(Y,U,2) 
  
 SEE DBIA59-A 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTERIM MANAGEMENT SUPPORT
  ISC: Birmingham

NUMBER: 521                             IA #: 521
  DATE CREATED: MAY 25, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: LRCAPS
  NAME: DBIA59-C                        ORIGINAL NUMBER: 59
  ID: LRCAPS
 GENERAL DESCRIPTION:   - ECT namespaced option runs routine ^LRCAPS.  
  
 - Refences file 68 Accession (read only) 
    2  DATE 
       .01 DATE 
         1 ACCESSION NUMBER 
           .01 LRDFN 
            11 TESTS 
               .01 TESTS 
  
 SEE DBIA59-A 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTERIM MANAGEMENT SUPPORT
  ISC: Birmingham

NUMBER: 522                             IA #: 522
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: DEC 11, 1990
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA60-B
  ORIGINAL NUMBER: 60                   ID: PS(55,
GLOBAL REFERENCE: PS(55,D0,P,0)
FIELD NUMBER: .01                       FIELD NAME: PRESCRIPTION PROFILE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(55,DFN,'P','A',DATE,
 GLOBAL DESCRIPTION:   Used if active only is indicated.  
 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 EMAIL GROUP 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 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 523                             IA #: 523
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA60-C
  ORIGINAL NUMBER: 60                   ID: PSRX(
GLOBAL REFERENCE: PSRX(D0,0)
FIELD NUMBER: .01                       FIELD NAME: RX #
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ISSUE DATE
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PHYSICIAN
  LOCATION: 0;4                         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: 9                         FIELD NAME: # OF REFILLS
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SIG
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 100                       FIELD NAME: STATUS
  LOCATION: 0;15                        ACCESS: Read w/Fileman
FIELD NUMBER: 17                        FIELD NAME: UNIT PRICE OF DRUG
  LOCATION: 0;17                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,2)
FIELD NUMBER: 26                        FIELD NAME: EXPIRATION DATE
  LOCATION: 2;6                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,3)
FIELD NUMBER: 101                       FIELD NAME: LAST FILL
  LOCATION: 3;1                         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
 GENERAL DESCRIPTION:   This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: HEALTH SUMMARY     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,
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 - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
  DATE ACTIVATED: MAY 24, 2012

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
FIELD NUMBER: .04                       FIELD NAME: VERIFY PERSON
  LOCATION: 0;4                         ACCESS: 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. 
 
GLOBAL REFERENCE: LR(D0,'CH',D1,'ORUT',D2,0)
FIELD NUMBER: 3                         FIELD NAME: CPRS ORDER #
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,'CY',D1,'ORUT',D2,0)
FIELD NUMBER: 3                         FIELD NAME: CPRS ORDER #
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,'EM',D1,'ORUT',D2,0)
FIELD NUMBER: 3                         FIELD NAME: CPRS ORDER #
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,'MI',D1,'ORUT',D2,0)
FIELD NUMBER: 3                         FIELD NAME: CPRS ORDER #
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,'SP',D1,'ORUT',D2,0)
FIELD NUMBER: 3                         FIELD NAME: CPRS ORDER #
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 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, 
  
 Revisions: 
     Added 10/12/23, effective with OR*3*535    
  
  GLOBAL REFERENCE: 
    ^LR(D0,'CH',D1,'ORUT',D2,0) 
      3        CPRS ORDER #         0;3      Direct Global Read & w/Fileman 
  
  GLOBAL REFERENCE: 
    ^LR(D0,'CY',D1,'ORUT',D2,0) 
      3        CPRS ORDER #         0;3      Direct Global Read & w/Fileman 
  
  GLOBAL REFERENCE: 
    ^LR(D0,'EM',D1,'ORUT',D2,0) 
      3        CPRS ORDER #         0;3      Direct Global Read & w/Fileman 
  
  GLOBAL REFERENCE: 
    ^LR(D0,'MI',D1,'ORUT',D2,0) 
      3        CPRS ORDER #         0;3      Direct Global Read & w/Fileman 
  
  GLOBAL REFERENCE: 
    ^LR(D0,'SP',D1,'ORUT',D2,0) 
      3        CPRS ORDER #         0;3      Direct Global Read & w/Fileman 
  
  
  
  
  
  STATUS: Active                        DURATION: Next Version
  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 DETAILS:   See revisions dated 10/12/23 for new fields added,
 effective with OR*3*535 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS
 SUBSCRIBING DETAILS:   ADDED 4/23/09 
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   Added 11/22/2021, effective with DSSV*1.0*1 and added
 .04 VERIFY PERSON field for completed LABS.  DSS Class 3 product Document Only 
  DATE ACTIVATED: OCT 13, 2023

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

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
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
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
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: Controlled Subscription
  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
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  

NUMBER: 533                             IA #: 533
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: JAN 31, 1991
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA68-B
  ORIGINAL NUMBER: 68                   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 EMAIL GROUP 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
 December 31, 2006.  
  
 The following fields are accessed from ^PS( and ^PSDRUG( in a read-only 
 manner: 
  
 For verified orders: 
  
   ^PS(       55                PHARMACY PATIENT FILE 
              55.06     1       Provider 
                        3       Medicinal Route (pointer to ^PS(51.2,) 
                        7       Schedule Type 
                       10       Start Date/Time 
                       26       Schedule 
                       28       Status 
                       34       Stop Date/Time 
              55.07     .01     Drug (pointer to ^PSDRUG() 
                        1       Dosage Ordered 
  
 The following cross-references are used: 
  
   ^PS(       55.06    "AUS"    Stop Date/Time 
   
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
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,
GLOBAL REFERENCE: 53.1
FIELD NUMBER: .24                       FIELD NAME: PRIORITY
  LOCATION: 2;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PROVIDER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: MED ROUTE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: SCHEDULE TYPE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: SPECIAL INSTRUCTIONS
  LOCATION: 6;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: START DATE/TIME
  LOCATION: 2;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 25                        FIELD NAME: STOP DATE/TIME
  LOCATION: 2;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 26                        FIELD NAME: SCHEDULE
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 28                        FIELD NAME: STATUS
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 41                        FIELD NAME: FREQUENCY (in minutes)
  LOCATION: 2;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 53                        FIELD NAME: IV TYPE
  LOCATION: 8;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 54                        FIELD NAME: CHEMOTHERAPY TYPE
  LOCATION: 8;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 59                        FIELD NAME: INFUSION RATE
  LOCATION: 8;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 63                        FIELD NAME: REMARKS
  LOCATION: 9;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 66                        FIELD NAME: PROVIDER COMMENTS
  LOCATION: 12;0                        ACCESS: Read w/Fileman
FIELD NUMBER: 109                       FIELD NAME: DOSAGE ORDERED
  LOCATION: .2;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 111                       FIELD NAME: INSTRUCTIONS
  LOCATION: .3;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 113                       FIELD NAME: CLINIC
  LOCATION: DSS;1                       ACCESS: Read w/Fileman
FIELD NUMBER: 116                       FIELD NAME: DURATION
  LOCATION: 2.5;2                       ACCESS: Read w/Fileman
FIELD NUMBER: 120                       FIELD NAME: DOSE
  LOCATION: .2;5                        ACCESS: Read w/Fileman
FIELD NUMBER: 121                       FIELD NAME: UNIT
  LOCATION: .2;6                        ACCESS: Read w/Fileman
FIELD NUMBER: 127                       FIELD NAME: REQUESTED IV LIMITATION
  LOCATION: 2.5;4                       ACCESS: Read w/Fileman
FIELD NUMBER: 128                       FIELD NAME: IV TYPE CATEGORY
  LOCATION: 2.5;5                       ACCESS: Read w/Fileman
FIELD NUMBER: 132                       FIELD NAME: INDICATION FOR USE
  LOCATION: 18;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 135                       FIELD NAME: SPECIAL INSTRUCTIONS
  LOCATION: 15;0                        ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: TYPE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: 53.11
FIELD NUMBER: .01                       FIELD NAME: DISPENSE DRUG
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: INACTIVE DATE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: 53.157
FIELD NUMBER: .01                       FIELD NAME: ADDITIVE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: STRENGTH
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: BOTTLE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: 53.158
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
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Added TYPE (#4) for GMTS*2.7*145.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 09/14/2022, effective with DSSV 1.1. DSS Class 2
 product. Document Only. DSSV is adding fields Direct Global Read & w/Fileman:  
                     a) .24,1,3,8,26,28,41,53,54,59,63,66,109,111,113,     
    116,120,121,127,128,132,135                        b) .01,.03 for subfile
 53.11                         c) .01,1 for subfile 53.158                      
      d) .01,1,2 for subfile 53.157                         from the
 NON-VERIFIED ORDERS (#53.1) file.  
  DATE ACTIVATED: MAR 03, 2023

NUMBER: 535                             IA #: 535
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: NOV 14, 2005
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA69-B
  ORIGINAL NUMBER: 69                   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 EMAIL GROUP 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 following fields are accessed from ^PS( and ^PSDRUG( in a read-only 
 manner: 
  
 ^PS(55,                     PHARMACY PATIENT FILE 
           55.01     .02     Start Date/Time 
                     .03     Stop Date/Time 
                     .06     Physician 
                     .08     Infusion Rate 
                     .09     Schedule 
                     100     Status 
           55.02     .01     Additive (Pointer to ^PS(52.6,) 
                     .02     Strength 
           55.11     .01     Solution (Pointer to ^PS(52.7,) 
                     1       Volume 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 536                             IA #: 536
  FILE NUMBER: 52.6                     GLOBAL ROOT: PS(52.6,
  DATE CREATED: JAN 31, 1991
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA69-C
  ORIGINAL NUMBER: 69                   ID: PS(52.6,
 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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
  
 ^PS(52.6,                   IV ADDITIVE FILE 
           52.6      .01     Additive Name 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
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 EMAIL GROUP 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

NUMBER: 538                             IA #: 538
  FILE NUMBER: 121.1                    GLOBAL ROOT: GMR(121.1,
  DATE CREATED: FEB 04, 1991            CUSTODIAL PACKAGE: PROGRESS NOTES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: DBIA74-B
  ORIGINAL NUMBER: 74                   ID: GMR(121.1,
GLOBAL REFERENCE: 121.1
FIELD NUMBER: .01                       FIELD NAME: PROGRESS NOTE TYPE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Health Summary is accessing fields in the Generic
 Progress Notes Type file, GMR(121.1, to retrieve the Title for display on 
 various components.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

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: 552                             IA #: 552
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: NOV 01, 1993
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA90-B
  ORIGINAL NUMBER: 90                   ID: PS(55,
GLOBAL REFERENCE: PS(55,D0,'P',D1,0)
FIELD NUMBER: .01                       FIELD NAME: PRESCRIPTION PROFILE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(55,DFN,'P','A',DATE,
 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 EMAIL GROUP 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 December 31, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY
  ISC: Oakland
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  ISC: Oakland
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES

NUMBER: 553                             IA #: 553
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG(
  DATE CREATED: NOV 01, 1993
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA90-C
  ORIGINAL NUMBER: 90                   ID: PSDRUG(
GLOBAL REFERENCE: PSDRUG(D0,
FIELD NUMBER: 21                        FIELD NAME: VA PRODUCT NAME
  LOCATION: ND;2                        ACCESS: Read w/Fileman
FIELD NUMBER: .01                       FIELD NAME: GENERIC NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 16                        FIELD NAME: PRICE PER DISPENSE UNIT
  LOCATION: 660;6                       ACCESS: Read w/Fileman
FIELD NUMBER: 20                        FIELD NAME: NATIONAL DRUG FILE ENTRY
  LOCATION: ND;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 25                        FIELD NAME: NATIONAL DRUG CLASS
  LOCATION: ND;6                        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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
  
 Amended August 30, 1994.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY
  ISC: Oakland
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  ISC: Oakland
SUBSCRIBING PACKAGE: MYHEALTHEVET

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
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.  

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
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  ISC: Oakland

NUMBER: 556                             IA #: 556
  FILE NUMBER: 409.5                    GLOBAL ROOT: SDV(
  DATE CREATED: SEP 11, 1991            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA93-B
  ORIGINAL NUMBER: 93                   ID: SDV(
GLOBAL REFERENCE: SDV(D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: SDV(D0,'CS',D1,0)
FIELD NUMBER: .01                       FIELD NAME: CLINIC STOP CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: SDV('C',X,DA)
 GLOBAL DESCRIPTION:   Eligible records will be determined by using the 'C'
 cross reference of the SCHEDULING VISITS file to determine matches with
 patients.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY
  ISC: Oakland
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
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 - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL

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)

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: 562                             IA #: 562
  FILE NUMBER: 220.4                    GLOBAL ROOT: DIC(220.4,
  DATE CREATED: NOV 09, 2005            CUSTODIAL PACKAGE: DENTAL
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIA102-B
  ORIGINAL NUMBER: 102                  ID: DIC(220.4,
GLOBAL REFERENCE: DIC(220.4,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DENTAL BED SECTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The following fields are accessed in a read-only
 manner: 
  
               ^DIC(220.4 
                          .01     Dental Bed Section 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY
  ISC: Oakland

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 - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

NUMBER: 564                             IA #: 564
  FILE NUMBER: 45                       GLOBAL ROOT: DGPT(
  DATE CREATED: JUN 20, 2005            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA104-B
  ORIGINAL NUMBER: 104                  ID: DGPT(
 GENERAL DESCRIPTION:   #45 PTF file 
  
 ^DGPT("ADS",   cross-reference: When using the ^DGPT(PTF,0) node, the software
 checks the 11th piece for the type of record (i.e., PTF or CENSUS).  For
 example:  Q:$P(^DGPT(QI P1IFN,0),U,11)'=1 ".  
  
 ^DGPT("AAD", cross-reference The following nodes and multiples from File 45: 
            0 node 
            70 node 
            401 multiple 
            501 multiple 
            601 multiple 
  
 Other referenced nodes: 
            ^DGPT(,"S" 
            ^DGPT(,"M","AM" x-ref 
  
 The internal entry number (D1) of the sub-file entry is obtained
 (^DGPT(D0,"M",D1)) and used to find the zero node.  The zero node of the "M"
 multiple (^DGPT(D0,"M",D1,0)) contains the movement records (1-1000) for this
 episode of care.  Two pieces of information are obtained from the movement
 record.  First, is the losing specialty (field #2).  This field contains the
 losing bedsection for this movement and is a pointer to the SPECIALTY file
 (#42.4).  If the description of the losing specialty does not contain "NHCU"
 or "DOMICILIARY", routine execution continues.  The second field obtained is
 the ICD 1 field (#5) which contains the diagnosis responsible for the greatest
 length of stay in this bedsection.  It is a pointer to the ICD DIAGNOSIS file
 (#80).  If the diagnosis is a substance abuse diagnosis, the entry is stored
 to a temporary file (^TMP) and the patient is listed on the report.  All
 movement records for a patient will be checked until a match is found at which
 time routine execution will proceed to the next patient.  If no matches are
 found, the patient is not reported and  execution proceeds to the next
 patient.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas

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
SUBSCRIBING PACKAGE: SURGERY            ISC: Birmingham

NUMBER: 566                             IA #: 566
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: JUN 20, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA106-B
  ORIGINAL NUMBER: 106                  ID: PSRX(
 GENERAL DESCRIPTION:   Routine QIP3POLY reads the following fields: 
  
 In file 52, PRESCRIPTION 
    6 - DRUG 
  101 - LAST DISPENSED DATE Amendment to DBIA 106 approved 10/10/93: 
  
 QUIC is requesting the following be added to DBIA #106. The additional 
 files/fields will be used to report the rate of completion of at least one
 Glycosalated Hemoglobin measurement within one year for diabetic patients on a
 medication regimen.  Add under #52 PRESCRIPTION file 
    100 STATUS 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 567                             IA #: 567
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: JUN 20, 2005
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA106-C
  ORIGINAL NUMBER: 106                  ID: PS(55,
 GENERAL DESCRIPTION:   Routine QIP3POLY reads the following fields: In file
 55, PHARMACY PATIENT, the cross reference 
  ^PS(55,DFN,"P","A",DATE,RX) 
  
 The above references will be made from the QIP3POLY routine which, while 
 belonging to the QIP namespace, will be maintained by the pharmacy developers. 
 Coordination of release and patches will be through the QIP custodial ISC.  
  
 Amendment to DBIA 106 approved 10/10/93: 
  
 QUIC is requesting the following be added to DBIA #106. The additional 
 files/fields will be used to report the rate of completion of at least one
 Glycosalated Hemoglobin measurement within one year for diabetic patients on a
 medication regimen.  #55, PHARMACY PATIENT file 
   .01 NAME 
     55.06,55.02,.01 DISPENSED DRUG 
     55.06,28 STATUS 
     55.01,55.02,.01 ADDITIVES 
     55.01,100 STATUS 
     Cross reference ^PS(55,DFN,5,"AUS",DATE/TIME,DA) 
  
 With the "AUS" cross reference, I am referencing the DISPENSE DRUG and TATUS
 (#28) fields.  5,D0,5,D1,0)=^^^^^^^^ (#28) STATUS [9S] ^ (55,D0,5,D1,1,D2,0)=
 (#.01) DISPENSE DRUG [1P] ^ 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 568                             IA #: 568
  FILE NUMBER: 52.6                     GLOBAL ROOT: PS(52.6,
  DATE CREATED: JUN 20, 2005
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA106-D
  ORIGINAL NUMBER: 106                  ID: PS(52.6,
GLOBAL REFERENCE: PS(52.6,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PRINT NAME
  LOCATION: 0;1                         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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
  
 Amendment to DBIA 106 approved 10/10/93: 
  
 QUIC is requesting the following be added to DBIA #106. The additional 
 files/fields will be used to report the rate of completion of at least one
 Glycosalated Hemoglobin measurement within one year for diabetic patients on a
 medication regimen.  
  
 #52.6, IV ADDITIVES file 
     .01 PRINT NAME 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 569                             IA #: 569
  FILE NUMBER: 132.9                    GLOBAL ROOT: SRO(132.9,
  DATE CREATED: JUN 20, 2005            CUSTODIAL PACKAGE: SURGERY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA107-B
  ORIGINAL NUMBER: 107                  ID: SRO(132.9,
 GENERAL DESCRIPTION:   Custodial package - Surgery: 
 ----------------------------
 Routine QIP3SR accesses the following fields: In file 132.9, ATTENDING CODES 
     1 - CODE 
  
 The above references will be made from the QIP3SR* routines which, while 
 belonging to the QIP namespace, will be maintained by the surgery developers. 
 Coordination of release and patches will be through the QIP custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: SEP 07, 1994
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 570                             IA #: 570
  FILE NUMBER: 210                      GLOBAL ROOT: NURSF(210,
  DATE CREATED: JUN 20, 2005            CUSTODIAL PACKAGE: NURSING SERVICE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA108-B
  ORIGINAL NUMBER: 108                  ID: NURSF(210,
 GENERAL DESCRIPTION:   NURS STAFF FILE #210 
  
 .01 Employee Name 
  
   3 Assignment (multiple) 
     1 Service Position 
     3 Location 
  
   5 Status 
  
  20 Date of Seperation from Hospital 
  
 Version 2.5: 
  
 NURS STAFF FILE #210 
  
 .01 Employee Name 
  
   5 Status 
  
 The above references will be made from the QIP4* routines which, while 
 belonging to the QIP namespace, will be maintained by the nursing developers. 
 Coordination of release and patches will be through the QIP custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 571                             IA #: 571
  FILE NUMBER: 211.8                    GLOBAL ROOT: NURSF(211.8,
  DATE CREATED: OCT 04, 1991            CUSTODIAL PACKAGE: NURSING SERVICE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA108-C
  ORIGINAL NUMBER: 108                  ID: NURSF(211.8,
 GENERAL DESCRIPTION:   NURS POSITION CONTROL FILE #211.8 
  
 .01 Location 
  
   2 Occupancy/Transferred Date (Multiple) 
     .03 Service Position 
       3 Vacancy Date 
  
 The above references will be made from the QIP4* routines which, while 
 belonging to the QIP namespace, will be maintained by the nursing developers. 
 Coordination of release and patches will be through the QIP custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 572                             IA #: 572
  FILE NUMBER: 68                       GLOBAL ROOT: LRO(68,
  DATE CREATED: OCT 04, 1991            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA109-B
  ORIGINAL NUMBER: 109                  ID: LRO(68,
 GENERAL DESCRIPTION:   68 ACCESSION FILE 
      68.01,.01 DATE 
      68.02,12 LAB ARRIVAL TIME 
      68.02,13 DATE/TIEM RESULTS AVAILABLE 
      68.04,.01 TESTS 
      68.04,1 URGENCY OF TEST 
      68,.02 LR SUBSCRIPT 
      68.02,.01 LRDFN 
      68.02,1 FILE # 
      68.02,94 ORDERING LOCATION 
      68.02,9 DRAW TIME 
      68.02,13.5 INVERSE DATE 
      68.05,.01 SPECIMEN 
  
 The above references will be made from the QIP5* routines which, while 
 belonging to the QIP namespace, will be maintained by the lab developers.  
 Coordination of release and patches will be through the QIP custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 573                             IA #: 573
  FILE NUMBER: 61.2                     GLOBAL ROOT: LAB(61.2
  DATE CREATED: OCT 04, 1991            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA109-C
  ORIGINAL NUMBER: 109                  ID: LAB(61.2
GLOBAL REFERENCE: LAB(61.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The above references will be made from the QIP5* routines
 which, while belonging to the QIP namespace, will be maintained by the lab
 developers.  Coordination of release and patches will be through the QIP
 custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 574                             IA #: 574
  FILE NUMBER: 62.06                    GLOBAL ROOT: LAB(62.06,
  DATE CREATED: OCT 04, 1991            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA109-D
  ORIGINAL NUMBER: 109                  ID: LAB(62.06,
GLOBAL REFERENCE: LAB(62.06,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DRUG NODE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   The above references will be made from the QIP5*
 routines which, while belonging to the QIP namespace, will be maintained by
 the lab developers.  Coordination of release and patches will be through the
 QIP custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 575                             IA #: 575
  FILE NUMBER: 63                       GLOBAL ROOT: LR(
  DATE CREATED: OCT 04, 1991            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA109-E
  ORIGINAL NUMBER: 109                  ID: LR(
 GENERAL DESCRIPTION:   63 LAB DATA 
      63,.01 LRDFN 
      63,.02 PARENT FILE 
      63,.03 NAME 
      63.04,.01 DATE/TIME SPECIMEN TAKEN 
      63.3,.01 ORGANISM 
      63.3,* FIELDS FOR ANTIBIOTICS 
      63.017,.01 TRANSFUSION DATE/TIME 
      63.017,.02 COMPONENT 
      63.017,.08 TRANSFUSION REACTION 
      63.04,* ALL LAB TEST FIELDS 
  
 The above references will be made from the QIP5* routines which, while 
 belonging to the QIP namespace, will be maintained by the lab developers.  
 Coordination of release and patches will be through the QIP custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 576                             IA #: 576
  FILE NUMBER: 66                       GLOBAL ROOT: LAB(66,
  DATE CREATED: OCT 04, 1991            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA109-F
  ORIGINAL NUMBER: 109                  ID: LAB(66,
GLOBAL REFERENCE: LAB(66,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The above references will be made from the QIP5* routines
 which, while belonging to the QIP namespace, will be maintained by the lab
 developers.  Coordination of release and patches will be through the QIP
 custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 577                             IA #: 577
  FILE NUMBER: 62                       GLOBAL ROOT: LAB(62,
  DATE CREATED: OCT 04, 1991            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA109-G
  ORIGINAL NUMBER: 109                  ID: LAB(62,
GLOBAL REFERENCE: LAB(62,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DEFAULT SPECIMEN
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   The above references will be made from the QIP5*
 routines which, while belonging to the QIP namespace, will be maintained by
 the lab developers.  Coordination of release and patches will be through the
 QIP custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 578                             IA #: 578
  FILE NUMBER: 60                       GLOBAL ROOT: LAB(60,
  DATE CREATED: OCT 04, 1991            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA109-H
  ORIGINAL NUMBER: 109                  ID: LAB(60,
 GENERAL DESCRIPTION:   60 LABORATORY TEST FILE 
      60,3 TYPE 
      60,4 SUBSCRIPT 
      60,400 DATA NAME 
  
 The above references will be made from the QIP5* routines which, while 
 belonging to the QIP namespace, will be maintained by the lab developers.  
 Coordination of release and patches will be through the QIP custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 579                             IA #: 579
  FILE NUMBER: 61                       GLOBAL ROOT: LAB(61,
  DATE CREATED: OCT 04, 1991            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA109-I
  ORIGINAL NUMBER: 109                  ID: LAB(61,
GLOBAL REFERENCE: LAB(61,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The above references will be made from the QIP5* routines
 which, while belonging to the QIP namespace, will be maintained by the lab
 developers.  Coordination of release and patches will be through the QIP
 custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 580                             IA #: 580
  FILE NUMBER: 40.7                     GLOBAL ROOT: DIC(40.7,
  DATE CREATED: JUN 20, 2005            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA110-B
  ORIGINAL NUMBER: 110                  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:   - Determining the percentage of no-show visits versus the
 total number of visits: 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

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: 582                             IA #: 582
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9(
  DATE CREATED: APR 21, 2003            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA113-B                       ORIGINAL NUMBER: 113
  ID: ICD9(
GLOBAL REFERENCE: ICD9(D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY
  ISC: Oakland

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
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
FIELD NUMBER: 12                        FIELD NAME: TYPE OF IMAGING
  LOCATION: 0;12                        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
KEYWORDS: RA-Class 3
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)
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Patch MECH*1.0*1 processes HL7 new-order messages about
 imaging studies performed in the community but not entered through VistA.  In
 order to do this, it needs to invoke Radiology routines and make FileMan calls
 to add entries to the RAD/NUC MED PATIENT File (#70) (for existing VA
 patients), the ORDER File (#100), and the RAD/NUC MED ORDERS File (#75.1). The
 patch then creates an HL7 order-update message that transmits the study's 
 accession number to the sender. ADDED 3/2/2022, effective with MECH*1.0*1 
 Medicom Class 3 product Document Only 
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 10/13/2022, effective with DSSV*1.1 DSS Class 3
 product Document Only Access to field 9 - CPT CODE 

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
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  ISC: Oakland
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP 2.0 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
 **************************************************************************

NUMBER: 588                             IA #: 588
  DATE CREATED: APR 21, 2003            CUSTODIAL PACKAGE: RECORD TRACKING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: RTQ3
  NAME: DBIA120-B                       ORIGINAL NUMBER: 120
  ID: RTQ3
 GENERAL DESCRIPTION:   
       2. When a patient is registered, records may be requested by a 
          call from REFILE+2^DGREG0 to ADM^RTQ3    ^RTV(190.1,n) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ADM
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 589                             IA #: 589
  DATE CREATED: NOV 06, 1991            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Other                           NAME: DBIA124-B
  ORIGINAL NUMBER: 124
 GENERAL DESCRIPTION:   
   Export of options PSOCP TRANSACTION and PSOCP RESET COPAY STATUS in 
  version 1 of the Integrated Billing Package.Export of the IB 
  SERVICE/SECTION field of the Pharmacy Site file (59) and the CO-PAY 
  TRANSACTION TYPE, IB NUMBER and REFILL DATE (entire multiple) fields of the
 Prescription file in version 1 of the 
  Integrated Billing Package.  Export of routines PSOCP, PSOCPA, PSOCPB, 
 PSOCPC, PSOCPD, PSOCPVW, PSOLBL, PSONEW, PSONEW3,PSORENW1, PSORXDL, PSORXED, 
  PSORXL, PSOSD0, PSOSD1,PSOSD 2, PSOSULB1, and PSOSULBL. Export PSO NEWSITE 
  input template of the Pharmacy Site file (59).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

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 EMAIL GROUP 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: 591                             IA #: 591
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA124-D
  ORIGINAL NUMBER: 124                  ID: PSRX(
 GENERAL DESCRIPTION:   
  
 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.  
  
  
 Direct reference to ^PSRX by Integrated Billing to determine if the link 
 between Integrated Billing and the Prescription file is intact.  
  
 Direct global reads of the ICD DIAGNOSIS multiple's fields.  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 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
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 595                             IA #: 595
  FILE NUMBER: 430                      GLOBAL ROOT: PRCA(430,
  DATE CREATED: NOV 06, 1991            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIA127-D
  ORIGINAL NUMBER: 127                  ID: PRCA(430,
 GENERAL DESCRIPTION:   Look-up of the Accounts Receivable file (430) by
 Integrated Billing for an option to print by Coarge ID (bill number).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
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: 597                             IA #: 597
  DATE CREATED: NOV 06, 1991            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Other                           NAME: DBIA127-F
  ORIGINAL NUMBER: 127
 GENERAL DESCRIPTION:   Updating of pointer values in data by Version 1 of
 Integrated Billings 
  post-initialization routine as necessary.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 598                             IA #: 598
  FILE NUMBER: 412                      GLOBAL ROOT: PRC(412,
  DATE CREATED: SEP 02, 2003            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIY127-G
  ORIGINAL NUMBER: 598                  ID: PRC(412,
 GENERAL DESCRIPTION:   Direct reference to the global ^PRC(412 in the Version
 1 post 
  initialization routine to set the STATEMENT DAY field.  
  STATUS: Retired                       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: Controlled Subscription
  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
SUBSCRIBING PACKAGE: REMOTE ORDER/ENTRY SYSTEM
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 10/13/23, effective with patch PX*1.0*235 for
 documenting ICR in legacy code. 

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: 605                             IA #: 605
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA131-B
  ORIGINAL NUMBER: 131                  ID: SC(
 GENERAL DESCRIPTION:   Read access to File 44 field .01 and Appointment
 sub-fields 'Clinic Stop Code' and 'Patient Name' 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SOCIAL WORK        ISC: Birmingham

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: 607                             IA #: 607
  DATE CREATED: JAN 07, 1992            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Routine                         ROUTINE: PRCS58CC
  NAME: DBIA140-B                       ORIGINAL NUMBER: 140
  ID: PRCS58CC
 GENERAL DESCRIPTION:   2. ^PRCS58CC - 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 (0ne) 
          piece 2 = a free-text error message.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Salt Lake City

NUMBER: 608                             IA #: 608
  FILE NUMBER: 420.5                    GLOBAL ROOT: PRCD(420.5,
  DATE CREATED: JAN 07, 1992            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIA140-C
  ORIGINAL NUMBER: 140                  ID: PRCD(420.5,
 GENERAL DESCRIPTION:   3.  Read access to file 420.5 (Unit of Issue) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Salt Lake City

NUMBER: 609                             IA #: 609
  FILE NUMBER: 440                      GLOBAL ROOT: PRC(440,
  DATE CREATED: JAN 07, 1992            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIA140-D
  ORIGINAL NUMBER: 140                  ID: PRC(440,
 GENERAL DESCRIPTION:   4.  Prosthetics to have Read, Write, and LAYGO access
 to files 440 (vendor) and 441 (Item Master), thru 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.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Salt Lake City

NUMBER: 610                             IA #: 610
  FILE NUMBER: 441                      GLOBAL ROOT: PRC(441,
  DATE CREATED: JAN 07, 1992            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIA140-E
  ORIGINAL NUMBER: 140                  ID: PRC(441,
 GENERAL DESCRIPTION:   4.  Prosthetics to have Read, Write, and LAYGO access
 to files 440 (vendor) and 441 (Item Master), thru 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.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Salt Lake City

NUMBER: 611                             IA #: 611
  FILE NUMBER: 410                      GLOBAL ROOT: PRCS(410,
  DATE CREATED: JAN 07, 1992            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIA140-F
  ORIGINAL NUMBER: 140                  ID: PRCS(410,
 GENERAL DESCRIPTION:   Read access to file 410 (Control Point Activity) -
 Access required to check the status of 2237's.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Salt Lake City

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 EMAIL GROUP 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
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham

NUMBER: 618                             IA #: 618
  FILE NUMBER: 50.605                   GLOBAL ROOT: PS(50.605,
  DATE CREATED: FEB 27, 1995            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA149-C
  ORIGINAL NUMBER: 149                  ID: PS(50.605,
GLOBAL REFERENCE: PS(50.605,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CLASSIFICATION 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
FIELD NUMBER: .01                       FIELD NAME: CLASSIFICATION CODE
  LOCATION: 0;1                         ACCESS: Pointed to
FIELD NUMBER: .01                       FIELD NAME: CLASSIFICATION CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(50.605,'B',
 GLOBAL DESCRIPTION:   Direct global read access to the "B" cross-reference
 will be used to determine the internal entry number for a record.  
GLOBAL REFERENCE: PS(50.605,'C',
 GLOBAL DESCRIPTION:   DIrect global read access to the "C" cross-reference
 will be used to lookup an entry by its CLASSIFICATION (#1) value.  
 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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
  
 The Adverse Reaction Tracking (ART) package will point to the VA Drug Class
 (50.605) file.  
    
 The ART package can do lookups on this file using the "C" cross-reference.  
 The package can do a direct global read of the the "C" cross-reference node.  
  
 The ART package will: 
      a. Use the "B" cross-reference of the VA Drug Class (50.605) file to 
         find the internal entry number (IEN) of a record, e. g., 
                IEN=$O(^PS(50.605,"B",Class_Code,"")).  
          
      b. Use a direct global read on the CLASSIFICATION CODE (.01) field in 
         the VA Drug Class (50.605), e.g., 
                Class_code=$P(PS(50.605,IEN,0),"^").  
  
      c. Use a direct global read on the CLASSIFICATION (1) field in the VA 
         Drug Class (50.605), e. g., 
                Class=$P(^PS(50.605,IEN,0),"^",2).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

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 EMAIL GROUP 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
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

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: 621                             IA #: 621
  FILE NUMBER: 741.1                    GLOBAL ROOT: QA(741.1,
  DATE CREATED: JUN 02, 1992            CUSTODIAL PACKAGE: OCCURRENCE SCREEN
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA159-B
  ORIGINAL NUMBER: 159                  ID: QA(741.1,
 GENERAL DESCRIPTION:   The following references will be made from the QIP4QAO*
 routines which, while belonging to the QIP namespace, will be maintained by
 the occurrence screen developers.  Coordination of release and patches will be
 through the QIP custodial ISC.  
  
 #741.1 QA OCCURRENCE SCREEN CRITERIA file 
      .01 Code 
      100 Screen Status 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 622                             IA #: 622
  FILE NUMBER: 741.2                    GLOBAL ROOT: QA(741.2,
  DATE CREATED: JUN 02, 1992            CUSTODIAL PACKAGE: OCCURRENCE SCREEN
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA159-C
  ORIGINAL NUMBER: 159                  ID: QA(741.2,
 GENERAL DESCRIPTION:   The following references will be made from the QIP4QAO*
 routines which, while belonging to the QIP namespace, will be maintained by
 the occurrence screen developers.  Coordination of release and patches will be
 through the QIP custodial ISC.  
  
 #741.2 QA OCCURRENCE REVIEW LEVEL file 
      1 Review Level Number 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 623                             IA #: 623
  FILE NUMBER: 741.6                    GLOBAL ROOT: QA(741.6,
  DATE CREATED: JUN 02, 1992            CUSTODIAL PACKAGE: OCCURRENCE SCREEN
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA159-D
  ORIGINAL NUMBER: 159                  ID: QA(741.6,
 GENERAL DESCRIPTION:   The following references will be made from the QIP4QAO*
 routines which, while belonging to the QIP namespace, will be maintained by
 the occurrence screen developers.  Coordination of release and patches will be
 through the QIP custodial ISC.  #741.6 QA OCCURRENCE FINDINGS file 
      .01 Code 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 624                             IA #: 624
  DATE CREATED: JUN 02, 1992            CUSTODIAL PACKAGE: OCCURRENCE SCREEN
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         ROUTINE: QIP1DIS
  NAME: DBIA159-E                       ORIGINAL NUMBER: 159
  ID: QIP1DIS
 GENERAL DESCRIPTION:   The following references will be made from the QIP4QAO*
 routines which, while belonging to the QIP namespace, will be maintained by
 the occurrence screen developers.  Coordination of release and patches will be
 through the QIP custodial ISC.  Call to EXTDIS^QIP1DIS to get discharge data.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EXTDIS
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  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: 632                             IA #: 632
  DATE CREATED: JUN 17, 1992            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: XQORM1
  NAME: DBIA169-B                       ORIGINAL NUMBER: 169
  ID: XQORM1
 GENERAL DESCRIPTION:   DISP^XQORM1  If the standard menu help has been
 replaced by defining XQORM(??),DISP^XQORM1 may be called by the help code to
 display the selections on the menu.  Remember DISP^XQORM1 may only be called
 by the code used in XQORM(??) and X must be "?" when it is called.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DISP
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: 634                             IA #: 634
  DATE CREATED: SEP 21, 2005            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSGAMSA
  NAME: DBIA172-B                       ORIGINAL NUMBER: 172
  ID: PSGAMSA
 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: Retired                       DURATION: Till Otherwise Agreed
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. Date drug dispensed (no time).  
  3. Order number 
  4. The drug dispensed.  
  5. Units (amount) dispensed.  
  6. The ward.  
  7. Provider who order the drug.  
  8. Cost of units dispensed.  
  9. Order Start Date/Time.  
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

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
 GENERAL DESCRIPTION:   Revision History: 
  - 9/19/24: Integrated Billing (IB) has asked Registration (DG) to 
    modify routine DGMTUB to include the Means Test status of 3 - No 
    Longer Required to the $$CK tag and to return a 1 only when called by 
    menu option "IB CANCEL/EDIT/ADD CHANGES".  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$BIL
 COMPONENT DESCRIPTION:   Determine if a patient was Category C on a specified
 date.  If Medal of Honor Indicator is "YES" Means Test is not required.  
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.  If Means Test status is 3
 - No Longer Required and called from menu option "IB CANCEL/EDIT/ADD CHANGES",
 return a 1.  
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 ACTIVATED: FEB 15, 2019

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: 647                             IA #: 647
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9(
  DATE CREATED: JUL 22, 1992            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA186-G
  ORIGINAL NUMBER: 186                  ID: ICD9(
 GENERAL DESCRIPTION:   80   ICD9      ICD DIAGNOSIS--Used when diagnosis (PTF
 and Billing) are printed on the patient appointment Check-off Sheet 
  
       .01      CODE NUMBER 
         3      DIAGNOSIS 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 648                             IA #: 648
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT(
  DATE CREATED: JUL 22, 1992            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA186-H                       ORIGINAL NUMBER: 186
  ID: ICPT(
 GENERAL DESCRIPTION:   Now covered by supported ICR #5408,CPT/HCPCS Procedure
 File 81.  81    ICPT      CPT FILE-- Since the new form of billing is based on
 CPTs this file is used throughout the BASC functionality: used to create the
 new table files, the Check-off Sheets, and reports on billing activity,
 pointed to by PROCEDURE field in the UPDATE BILLABLE AMBULATORY SURGICAL CODE
 file (350.41) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 12, 2015
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
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   Access will be used by VIAB SCDIS RPC.  

NUMBER: 650                             IA #: 650
  FILE NUMBER: 5                        GLOBAL ROOT: DIC(5,
  DATE CREATED: JUN 10, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA186-J
  ORIGINAL NUMBER: 186                  ID: DIC(5,
GLOBAL REFERENCE: DIC(5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

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: 659                             IA #: 659
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDAM1
  NAME: DBIA188-B                       ORIGINAL NUMBER: 188
  ID: SDAM1
 GENERAL DESCRIPTION:   If outpatient, get appointment status 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$STATUS
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Albany

NUMBER: 660                             IA #: 660
  DATE CREATED: JUL 22, 1992            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDUL
  NAME: DBIA188-C                       ORIGINAL NUMBER: 188
  ID: SDUL                              STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Enter list processor to review charges, enter list
 processor to review admissions 
COMPONENT/ENTRY POINT: REFRESH
 COMPONENT DESCRIPTION:   Refresh list screen 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 661                             IA #: 661
  DATE CREATED: JUL 22, 1992            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDUL1
  NAME: DBIA188-D                       ORIGINAL NUMBER: 188
  ID: SDUL1                             STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CLEAR
 COMPONENT DESCRIPTION:   CLEAR SCREEN, RESET IO 
COMPONENT/ENTRY POINT: $$FDATE
COMPONENT/ENTRY POINT: $$SETSTR
 COMPONENT DESCRIPTION:   Build strings for list processor array 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 662                             IA #: 662
  DATE CREATED: JUL 22, 1992            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDUL2
  NAME: DBIA188-E                       ORIGINAL NUMBER: 188
  ID: SDUL2                             STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SEL
 COMPONENT DESCRIPTION:   Select action item, list of items, or range of items 
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Select extended action, list of items, or range of
 items 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 663                             IA #: 663
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: VADPT
  NAME: DBIA188-F                       ORIGINAL NUMBER: 188
  ID: VADPT                             STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SDA
 COMPONENT DESCRIPTION:   Patient appointment data used in selecting and then
 printing appointment Check-off Sheets 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

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
  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 
SUBSCRIBING PACKAGE: PROBLEM LIST
 SUBSCRIBING DETAILS:   Added 6/19/2018.  
  DATE ACTIVATED: JUN 03, 2009

NUMBER: 665                             IA #: 665
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA188-H
  ORIGINAL NUMBER: 188                  ID: SC(
 GENERAL DESCRIPTION:   Used in finding and printing Check-off Sheets for
 patient appointments, the user is allowed to select all Check-off Sheets for a
 particular clinic 
  
       .01      NAME -- Used in searching, sorting, and printing the Clinic CPT
 Usage' report 
  
         2      TYPE -- Used in searching, sorting, and printing the'Clinic CPT
 Usage' report 
  
        15      MEDICAL CENTER DIVISION -- Used in BASC charge calculation on 
 the Check-off Sheet and the 'Clinic CPT Usage' report 
  
        25      PROCEDURE CHECK-OFF SHEET -- New field, associates a clinic and
 a Check-off Sheet 
  
      1900      APPOINTMENT SUBFILE -- Printed on a patients Check-off Sheet 
  .01       APPOINTMENT DATE/TIME 
    1       PATIENT 
  
      X-REF:      AF 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Albany

NUMBER: 666                             IA #: 666
  FILE NUMBER: 409.1                    GLOBAL ROOT: SD(409.1,
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA188-I
  ORIGINAL NUMBER: 188                  ID: SD(409.1,
 GENERAL DESCRIPTION:   
      SD(409.1  APPOINTMENT TYPE FILE 
  
       .01      NAME 
                Printed on a patients Check-off Sheet 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 667                             IA #: 667
  FILE NUMBER: 409.5                    GLOBAL ROOT: SDV(
  DATE CREATED: JUL 22, 1992            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA188-J
  ORIGINAL NUMBER: 188                  ID: SDV(
 GENERAL DESCRIPTION:   SDV       SCHEDULING VISITS-- Used to sort, search and
 print the 'Unbilled BASC for Insured Patient Appointment' and the 'Clinic CPT
 Usage' reports.  
  
         2      PATIENT 
        21      PROCEDURE 1 
        22      PROCEDURE 2 
        23      PROCEDURE 3 
        24      PROCEDURE 4 
        25      PROCEDURE 5 
  
      X-REF:      AP 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Albany

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: 670                             IA #: 670
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA188-M
  ORIGINAL NUMBER: 188                  ID: SC(
 GENERAL DESCRIPTION:   ^SC(HOSPITAL LOCATION--  ^IBOVOP1: scan clinic visits
 ^SDV(Scheduling Visits file)  ^IBECEA3: check stop codes for a c&p 
           - "CS" CLINIC STOP 
           - "B" xref 
           - 0;5 APPOINTMENT TYPE 
           - "ADT" appointment date ^IBECEA3 ^SD(409.1,APPOINTMENT TYPE-- 
 ^IBOVOP1: get appointment type name 
  
 SC        HOSPITAL LOCATION FILE-- Pointer to the Check-off sheet associated
 with this clinic 
  
       25       PROCEDURE CHECK-OFF SHEET 
  
      x-ref:    AF 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Albany

NUMBER: 671                             IA #: 671
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Other                           NAME: DBIA188-N
  ORIGINAL NUMBER: 188
 GENERAL DESCRIPTION:   IB Templates that look at MAS Files 
  
 IB CPT RG DISPLAY on file 409.71-- Displays a procedures billing fields: 
   .01   CODE history 
   .015  SHORT NAME 
    205   CURRENT ACTIVE STATUS 
  STATUS: Retired                       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

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: 677                             IA #: 677
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: AUG 18, 1992
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA191-E
  ORIGINAL NUMBER: 191                  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 EMAIL GROUP 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 
  
      ^PS(55,DA,"P") and ^PS(55,DA,"ARC") in order to screen the 
      file for relevant data.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Washington/Silver Spring

NUMBER: 678                             IA #: 678
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA191-F
  ORIGINAL NUMBER: 191                  ID: PSRX(
 GENERAL DESCRIPTION:   
      ^PSRX(DA, for prescription data.  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
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 EMAIL GROUP 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: 683                             IA #: 683
  FILE NUMBER: 738                      GLOBAL ROOT: QIP(738,
  DATE CREATED: DEC 04, 1992
  CUSTODIAL PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA199-B
  ORIGINAL NUMBER: 199                  ID: QIP(738,
 GENERAL DESCRIPTION:   1) ALPHA routines access the following QUIC fields in a
 read-only manner: 
    File 738 QUALITY IMPROVEMENT CHECKLIST 
             .01 STATION NAME 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ALPHA              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(
 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
  DEFERRED UNTIL: MAR 28, 2007
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,
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

NUMBER: 693                             IA #: 693
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: APR 21, 1993
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA221-C
  ORIGINAL NUMBER: 221                  ID: PS(55,
 GENERAL DESCRIPTION:   Outpatient Pharmacy is given permission by Pharmacy to
 make the following calls: 
  
 GLOBAL MAP DATA DICTIONARY #55 -- PHARMACY PATIENT FILE            2/26/93 
 STORED IN ^PS(55,           SITE: ISC BIRMINGHAM 
 ----------------------------------------------------------------------
 ^PS(55,D0,0)= (#.01) NAME [1P] ^ (#.02) CAP [2S] ^ (#.03) MAIL [3S] ^ 
            ==>(#.04) DIALYSIS PATIENT [4S] ^ ^PS(55,D0,1)= (#1) NARRATIVE [1F]
 ^ ^PS(55,D0,40)= (#40) COMMUNITY NURSING HOME [1S] ^ (#40.1) NURSING HOME 
         ==>CONTRACT [2S] ^ (#40.2) LAST DATE OF CONTRACT [3D] ^ 
         ==>(#41) RESPITE PATIENT START DATE [4D] ^ (#41.1) RESPITE 
         ==>PATIENT END DATE [5D] ^ ^PS(55,D0,ARC,0)=^55.13DA^^  (#101) ARCHIVE
 DATE ^PS(55,D0,ARC,D1,0)= (#.01) ARCHIVE DATE [1D] ^ ^PS(55,D0,P,0)=^55.03P^^ 
 (#52) PRESCRIPTION PROFILE ^PS(55,D0,P,D1,0)= (#.01) PRESCRIPTION PROFILE [1P]
 ^ ^PS(55,D0,PS)= (#3) PATIENT STATUS [1P] ^ ^PS(55,D0,SAND)= (#53) CLOZAPINE
 REGISTRATION NUMBER [1F] ^ (#54) 
       ==>CLOZAPINE STATUS [2S] ^ (#55) DATE OF LAST CLOZAPINE RX [3D] ^ 
       ==>(#56) DEMOGRAPHICS SENT [4S] ^ (#57) RESPONSIBLE PROVIDER 
       ==>[5P] ^ (#58) REGISTRATION DATE [6D] ^ 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

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,
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
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: APR 17, 2007

NUMBER: 695                             IA #: 695
  FILE NUMBER: 59.9                     GLOBAL ROOT: DIC(59.9,
  DATE CREATED: JUL 27, 2005
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA221-E
  ORIGINAL NUMBER: 221                  ID: DIC(59.9,
 GENERAL DESCRIPTION:   Outpatient Pharmacy is given permission by Pharmacy to
 make the following calls: 
  
 GLOBAL MAP DATA DICTIONARY #59.9 -- *PHARMACY FUNCTIONS FILE    STORED IN
 ^DIC(59.9     SITE: ISC BIRMINGHAM all fields in the file.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

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: 697                             IA #: 697
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT(
  DATE CREATED: APR 02, 1993            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA222-B
  ORIGINAL NUMBER: 222                  ID: ICPT(
GLOBAL REFERENCE: ICPT(X,'D',Y,0)
 GENERAL DESCRIPTION:   The DD for the CPT file (81) includes the following
 node which causes the CPT code description to be displayed when a lookup is 
 done on the CPT file: 
    ^DD(81,0,"ID",2)="W "   ",$P(^(0),U,2) I $D(SRSITE) D ^SROCPT" 
  
 An agreement is established for Surgery to call ^DD(81,0,"ID",2).  This DD
 node will remain in place to assist with CPT lookups from within the Surgery
 package.  Surgery will be responsible for support of the conditional call to
 ^SROCPT.  
   
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
SUBSCRIBING PACKAGE: SURGERY            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:   1/10/22: Patient Representative Decom patch QAC*2.0*25
 has been released on 01/10/2022 with a Compliance date of 2/10/22. Patient
 Representative subscription retired effective with a Compliance date of
 2/10/22.  
  
 Original usage information below: 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 

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: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: FEB 27, 2018
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: 1
  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: 709                             IA #: 709
  DATE CREATED: JUN 15, 1993            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         ROUTINE: XMA21
  NAME: DBIA239-B                       ORIGINAL NUMBER: 239
  ID: XMA21                             STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DES
VARIABLES: XMMG                         TYPE: Input
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: 712                             IA #: 712
  FILE NUMBER: 5                        GLOBAL ROOT: DIC(5,
  DATE CREATED: JUN 10, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA241-C
  ORIGINAL NUMBER: 241                  ID: DIC(5,
GLOBAL REFERENCE: DIC(5,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(5,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: COUNTY
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(5,'B',
  STATUS: Retired                       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: 719                             IA #: 719
  FILE NUMBER: 45                       GLOBAL ROOT: DGPT(
  DATE CREATED: JUN 15, 1993            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA243-C
  ORIGINAL NUMBER: 243                  ID: DGPT(
 GENERAL DESCRIPTION:   PTF file (#45) 
  
 ^DGPT(D0,0)= (#.01) PATIENT [1P] ^ (#2) ADMISSION DATE [2D] ^ (#3) 
              FACILITY [3N] ^ (#5) SUFFIX [5F] ^ (#11) TYPE OF RECORD 
              [11S] 
  
 ^DGPT(D0,70)= (#71) DISCHARGE SPECIALTY [2P] ^ (#75) PLACE OF DISPOSITION 
         [6P] ^ (#79) DXLS [10P] ^ (#79.16) ICD 2 [16P] ^ (#79.17) 
         ICD 3 [17P] ^ (#79.18) ICD 4 [18P] ^ (#79.19) ICD 5 [19P] ^ 
         (#79.201) ICD 6 [20P] ^ (#79.21) ICD 7 [21P] ^ (#79.22) ICD 
         8 [22P] ^ (#79.23) ICD 9 [23P] ^ (#79.24) ICD 10 [24P] 
  
 ^DGPT(D0,101)= (#20) SOURCE OF ADMISSION [1P] 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: EVENT DRIVEN REPORTING
  ISC: Albany

NUMBER: 720                             IA #: 720
  FILE NUMBER: 405.2                    GLOBAL ROOT: DG(405.2,
  DATE CREATED: JUN 15, 1993            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA243-D
  ORIGINAL NUMBER: 243                  ID: DG(405.2,
 GENERAL DESCRIPTION:   MAS Movement Type file (#405.2) 
  
 ^DG(405.2,D0,0) - $D check on zero node 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: EVENT DRIVEN REPORTING
  ISC: Albany

NUMBER: 721                             IA #: 721
  FILE NUMBER: 42.4                     GLOBAL ROOT: DIC(42.4,
  DATE CREATED: JUN 15, 1993            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA243-E
  ORIGINAL NUMBER: 243                  ID: DIC(42.4,
 GENERAL DESCRIPTION:   Specialty file (#42.4) 
  
 ^DIC(42.4,D0,0) - $D check on zero node 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: EVENT DRIVEN REPORTING
  ISC: Albany

NUMBER: 722                             IA #: 722
  FILE NUMBER: 405.4                    GLOBAL ROOT: DG(405.4,
  DATE CREATED: JUN 15, 1993            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA243-F
  ORIGINAL NUMBER: 243                  ID: DG(405.4,
 GENERAL DESCRIPTION:   Room-Bed file (#405.4) 
  
 ^DG(405.4,D0,0)= (#.01) NAME [1F] 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: EVENT DRIVEN REPORTING
  ISC: Albany

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

NUMBER: 724                             IA #: 724
  FILE NUMBER: 45.1                     GLOBAL ROOT: DIC(45.1,
  DATE CREATED: JUN 15, 1993            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA243-H
  ORIGINAL NUMBER: 243                  ID: DIC(45.1,
 GENERAL DESCRIPTION:   Source of Admission file (#45.1) 
  
 ^DIC(45.1,D0,0)= (#.01) PTF CODE [1F] 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: EVENT DRIVEN REPORTING
  ISC: Albany

NUMBER: 725                             IA #: 725
  FILE NUMBER: 45.7                     GLOBAL ROOT: DIC(45.7,
  DATE CREATED: JUN 15, 1993            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA243-I
  ORIGINAL NUMBER: 243                  ID: DIC(45.7,
 GENERAL DESCRIPTION:   ^DIC(45.7,D0,0)= (#1) SPECIALTY [2P] 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: EVENT DRIVEN REPORTING
  ISC: Albany

NUMBER: 726                             IA #: 726
  FILE NUMBER: 45.6                     GLOBAL ROOT: DIC(45.6
  DATE CREATED: JUN 15, 1993            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA243-J
  ORIGINAL NUMBER: 243                  ID: DIC(45.6
 GENERAL DESCRIPTION:   Place of Disposition file (#45.6) 
  
 ^DIC(45.6,D0,0)= (#2) CODE [2F] 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: EVENT DRIVEN REPORTING
  ISC: Albany

NUMBER: 727                             IA #: 727
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9(
  DATE CREATED: JUN 15, 1993            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA243-K
  ORIGINAL NUMBER: 243                  ID: ICD9(
 GENERAL DESCRIPTION:   ICD Diagnosis file (#80) 
  
 ^ICD9(D0,0)= (#.01) CODE NUMBER [1F] 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: EVENT DRIVEN REPORTING
  ISC: Albany

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
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 
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   Added 01/24/20 to support Pharmacy API's for Virtual
 Patient Record.  

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(
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: .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
GLOBAL REFERENCE: DGPM('AMV1')
GLOBAL REFERENCE: DGPM('APTT1')
GLOBAL REFERENCE: DGPM('APID')
GLOBAL REFERENCE: DGPM('AMVS')
GLOBAL REFERENCE: DGPM('B')
 GENERAL DESCRIPTION:   This ICR provides access to the Patient Movement file
 (#405) for selected fields and cross-references.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany
 SUBSCRIBING DETAILS:   Updated 12/23/25 effective with patch DVBA*2.7*257 
 Adding field .03 Patient and the "B" cross-reference 

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,
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
  DATE ACTIVATED: SEP 27, 2007

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: 735                             IA #: 735
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA244-I
  ORIGINAL NUMBER: 244                  ID: SC(
 GENERAL DESCRIPTION:   ^SC(           0;1            Hopital Location name 
      ^SC("C" 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany

NUMBER: 736                             IA #: 736
  FILE NUMBER: 409.1                    GLOBAL ROOT: SD(409.1,
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA244-J
  ORIGINAL NUMBER: 244                  ID: SD(409.1,
 GENERAL DESCRIPTION:   ^SD(409.1      0;1            Appointment Type name 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany
SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL

NUMBER: 737                             IA #: 737
  FILE NUMBER: 409.5                    GLOBAL ROOT: SDV(
  DATE CREATED: JUN 15, 1993            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA244-K
  ORIGINAL NUMBER: 244                  ID: SDV(
 GENERAL DESCRIPTION:   ^SDV(          0              Checks for the existence
 of 
  STATUS: Retired                       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: 739                             IA #: 739
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDM
  NAME: DBIA244-M                       ORIGINAL NUMBER: 244
  ID: SDM                               STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: OERR
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany

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
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
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 1/22/21 

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: 747                             IA #: 747
  DATE CREATED: AUG 09, 1993            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDKILL
  NAME: DBIA261-B                       ORIGINAL NUMBER: 261
  ID: SDKILL
 GENERAL DESCRIPTION:   The option HBHC Appointment uses the MAS routine ^SDM
 as the Run Routine, and employs SDM^SDKILL in the exit action.  The option
 HBHC Cancel Appointment uses ^SDCNP as the Run Routine, and the SDCNP^SDKILL 
 in the Exit Action.                                                 
  
 Select OPTION to edit: HBHC APPOINTMENT          Make Appointment NAME: HBHC
 APPOINTMENT// MENU TEXT: Make Appointment// PACKAGE: HOSPITAL BASED HOME
 CARE// DESCRIPTION: 
   1>This option utilizes the MAS Scheduling Option, Make Appointment [SDM], 
   2>for entry of appointment data.  The Exit Action on this option runs a 
   3>routine that creates records in the HBHC Visit File (HBHC(632)) using 
   4>the appointment data entered.  Only data for clinics contained in the 
   5>HBHC Clinic File (HBHC(631.6)) will be added to the HBHC Visit File.  
  
 EDIT Option: TYPE: run routine// ENTRY ACTION: D:$T(HDLKILL^SDAMEVT)]""
 HDLKILL^SDAMEVT EXIT ACTION: D SDM^SDKILL K ORACTION,ORVP,XQORQUIT W
 !!,"Adding entries 
   to the visit file..." D WAIT^DICD,^HBHCAPPT 
   D:$T(HDLKILL^SDAMEVT)]"" HDLKILL^SDAMEVT 
           Replace ROUTINE: SDM// 
  
  
 Select OPTION to edit: HBHC CANCEL APPOINTMENT          Cancel Appointment 
 NAME: HBHC CANCEL APPOINTMENT  Replace MENU TEXT: Cancel Appointment// 
 PACKAGE: HOSPITAL BASED HOME CARE DESCRIPTION: 
   1>This option utilizes the MAS Scheduling Option, Cancel Appointment 
   2>[SD CANCEL APPOINTMENT], for cancelling appointments.  The Exit Action 
   3>on this option runs a routine that updates records in the HBHC Visit 
   4>File (HBHC(632)) using the cancellation data entered.  EDIT Option: 
  
 TYPE: run routine// ENTRY ACTION: D:$T(HDLKILL^SDAMEVT)]"" HDLKILL^SDAMEVT 
 EXIT ACTION: D SDCNP^SDKILL W !!,"Updating entries in the visit 
     file..." D WAIT^DICD,^HBHCCAN D:$T(HDLKILL^SDAMEVT)]"" HDLKILL^SDAMEVT 
            Replace ROUTINE: SDCNP// 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SDM
COMPONENT/ENTRY POINT: SDCNP
SUBSCRIBING PACKAGE: HOME BASED PRIMARY CARE
  ISC: Hines

NUMBER: 748                             IA #: 748
  DATE CREATED: AUG 09, 1993            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDCNP
  NAME: DBIA261-C                       ORIGINAL NUMBER: 261
  ID: SDCNP
 GENERAL DESCRIPTION:   The option HBHC Cancel Appointment uses ^SDCNP as the
 Run Routine, and the SDCNP^SDKILL in the Exit Action.                          
                       
  
 Select OPTION to edit: HBHC CANCEL APPOINTMENT          Cancel Appointment 
 NAME: HBHC CANCEL APPOINTMENT  Replace MENU TEXT: Cancel Appointment// 
 PACKAGE: HOSPITAL BASED HOME CARE DESCRIPTION: 
   1>This option utilizes the MAS Scheduling Option, Cancel Appointment 
   2>[SD CANCEL APPOINTMENT], for cancelling appointments.  The Exit Action 
   3>on this option runs a routine that updates records in the HBHC Visit 
   4>File (HBHC(632)) using the cancellation data entered.  EDIT Option: 
  
 TYPE: run routine// ENTRY ACTION: D:$T(HDLKILL^SDAMEVT)]"" HDLKILL^SDAMEVT 
 EXIT ACTION: D SDCNP^SDKILL W !!,"Updating entries in the visit 
     file..." D WAIT^DICD,^HBHCCAN D:$T(HDLKILL^SDAMEVT)]"" HDLKILL^SDAMEVT 
            Replace ROUTINE: SDCNP// 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HOME BASED PRIMARY CARE
  ISC: Hines

NUMBER: 749                             IA #: 749
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: AUG 09, 1993            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA261-D
  ORIGINAL NUMBER: 261                  ID: SC(
 GENERAL DESCRIPTION:   In routine HBHCAPPT 
         $O(^SC(HBHCCLN,"S",HBHCAPDT)) 
         $O(^SC(HBHCCLN,"S",HBHCAPDT,1,HBHCSCN)) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HOME BASED PRIMARY CARE
  ISC: Hines

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
 GENERAL DESCRIPTION:   Supported calls for building of HL7 ZPD segment (VA
 Specific Patient Demographics).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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

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: 757                             IA #: 757
  DATE CREATED: AUG 10, 1993            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: VAFHLZDP
  NAME: DBIA263-I                       ORIGINAL NUMBER: 263
  ID: VAFHLZDP
 GENERAL DESCRIPTION:   duplicate of IA 751 
  STATUS: Retired                       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
 GENERAL DESCRIPTION:   This generic extrinsic function returns the HL7
 VA-Specific Temporary Address (ZTA) segment.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$EN
 COMPONENT DESCRIPTION:   
  Returns HL7 ZTA segment containing temporary address data.  
VARIABLES: DFN                          TYPE: Input
  VARIABLE SEQUENCE NUMBER: 1
 VARIABLES DESCRIPTION:   internal entry number of the PATIENT file 
VARIABLES: VAFSTR                       TYPE: Input
  VARIABLE SEQUENCE NUMBER: 2
 VARIABLES DESCRIPTION:   string of fields requested separated by commas 
VARIABLES: VAFNUM                       TYPE: Input
  VARIABLE SEQUENCE NUMBER: 3
 VARIABLES DESCRIPTION:   SETId - set to 1 
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  ISC: Birmingham
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Added 9/12/25, effective with patch PSJ*5.0*453 
 Methadone Dispense Tracking will have to make reference to the REGISTRATION
 package, to access the $$EN function call to return HL7 PID segment of a given
 patient.  

NUMBER: 759                             IA #: 759
  DATE CREATED: AUG 10, 1993            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: VASITE
  NAME: DBIA263-K                       ORIGINAL NUMBER: 263
  ID: VASITE                            STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$SITE
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  ISC: Birmingham

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: 762                             IA #: 762
  DATE CREATED: AUG 10, 1993            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGMTU21                      NAME: DBIA263-N
  ORIGINAL NUMBER: 263                  ID: DGMTU21
 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:           ALL^DGMTU21 
  STATUS: Other                         DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$ALL(DFN,DGTYPE,DGDT,DGRTY,DGMT)
 COMPONENT DESCRIPTION:   This call is used to get patient relation, individual
 annual income, and income relation arrays of internal entry numbers for the
 veteran, spouse, and dependents at the time of the veteran's means test.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN points to the patient in file #2.  
VARIABLES: DGTYPE                       TYPE: Input
 VARIABLES DESCRIPTION:   DGTYPE is the type of relation which can indicate
 veteran, spouse, dependent children, all dependents.  
VARIABLES: DGDT                         TYPE: Input
 VARIABLES DESCRIPTION:   DGDT is the date on which the arrays should be
 located.  
VARIABLES: DGRTY                        TYPE: Input
 VARIABLES DESCRIPTION:   DGRTY is the type of array which can indicate patient
 relation, individual annual income, and income relation.  
VARIABLES: DGMT                         TYPE: Input
 VARIABLES DESCRIPTION:   DGMT points to the means test in file #408.31.  
VARIABLES: DGREL                        TYPE: Output
 VARIABLES DESCRIPTION:   DGREL is the patient relation IEN array.  
VARIABLES: DGINC                        TYPE: Output
 VARIABLES DESCRIPTION:   DGINC is the individual annual income IEN array.  
VARIABLES: DGINR                        TYPE: Output
 VARIABLES DESCRIPTION:   DGINR is the income relation IEN array.  
VARIABLES: DGDEP                        TYPE: Output
 VARIABLES DESCRIPTION:   DGDEP is the number of dependents.  
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  ISC: Birmingham
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM

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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
 **************************************************************************
  
  
  
 HMP routines HMPDJ00 and HMPDJ00A are doing a direct global read of the second
 piece of the zero node for the record in the DG Security Log file (#38.1) in
 order to determine if the patient is marked as a sensitive patient.  This is
 part of the patient sync process that keeps the local VistA in sync with the
 JDS database for eHMP. As part of the sync, they are sending this flag with
 the patient record.  At that point, the data is simply being collected and not
 viewed. When HMP users see the data in the user interface the PTSEC^DGSEC4
 call is being made.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Added 3/19/25, effective with DVBA*2.7*255 so that
 displayed or reported information can be restricted for sensitive patients as
 needed in AMIE/CAPRI display of patient information in reports and user
 screens within the CAPRI application. File access within AMIE/CAPRI will be 
 read-only and as per the existing ICR description below.  

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: 769                             IA #: 769
  DATE CREATED: AUG 25, 1993            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: VASITE
  NAME: DBIA268-E                       ORIGINAL NUMBER: 268
  ID: VASITE
 GENERAL DESCRIPTION:   The PDX development team request permission to use the
 $$SITE^VASITE entry point in determining site.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$SITE
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: 780                             IA #: 780
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA273-B
  ORIGINAL NUMBER: 273                  ID: PSRX(
 GENERAL DESCRIPTION:   #52  PRESCRIPTION FILE  ^PSRX( 
  
 52,.01        RX #                   0;1 FREE TEXT 
                                          (Required) 52,4          PHYSICIAN   
           0;4 POINTER TO PROVIDER 
                                          FILE (#6) 52,6          DRUG         
          0;6 POINTER TO DRUG 
                                          FILE (#50) 
                                          (Required) 52,20         DIVISION    
           2;9 POINTER TO PHARMACY 
                                          SITE FILE (#59) 52,301       
 CLOZAPINE DOSAGE (MG/DAY) SAND;1 NUMBER 52,302        WBC RESULTS           
 SAND;2 NUMBER 52,303        DATE OF WBC TEST       SAND;3 DATE 
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Albany

NUMBER: 781                             IA #: 781
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: AUG 30, 1993
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA273-C
  ORIGINAL NUMBER: 273                  ID: PS(55,
GLOBAL REFERENCE: PS(55,
FIELD NUMBER: 53
  FIELD NAME: CLOZAPINE REGISTRATION NUMBER
  LOCATION: SAND;1                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 54                        FIELD NAME: CLOZAPINE STATUS
  LOCATION: SAND;2                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 55                        FIELD NAME: DATE OF LAST CLOZAPINE RX
  LOCATION: SAND;3                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 56                        FIELD NAME: DEMOGRAPHICS SENT
  LOCATION: SAND;4                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 57                        FIELD NAME: RESPONSIBLE PROVIDER
  LOCATION: SAND;5                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 58                        FIELD NAME: REGISTRATION DATE
  LOCATION: SAND;6                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,'ASAND',DA)
 GLOBAL DESCRIPTION:   Read Access to x-ref.  
GLOBAL REFERENCE: PS(55,'ASAND1',DA)
 GLOBAL DESCRIPTION:   Read Access to x-ref.  
 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 EMAIL GROUP 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.  
  
 #55  PHARMACY PATIENT FILE  ^PS(55 
  
 55,53         CLOZAPINE REGISTRATION NUMBER SAND;1 FREE TEXT 55,54        
 CLOZAPINE STATUS       SAND;2 SET 55,55         DATE OF LAST CLOZAPINE RX 
 SAND;3 DATE 55,56         DEMOGRAPHICS SENT      SAND;4 SET 55,57        
 RESPONSIBLE PHYSICIAN  SAND;5 POINTER TO 
                                             PROVIDER FILE 
                                             (#6) 55,58         REGISTRATION 
 DATE      SAND;6 DATE 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Albany

NUMBER: 782                             IA #: 782
  FILE NUMBER: 52.52                    GLOBAL ROOT: PS(52.52
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA273-D
  ORIGINAL NUMBER: 273                  ID: PS(52.52
 GENERAL DESCRIPTION:   #52.52  CLOZAPINE PRESCRIPTION OVERRIDES FILE 
 ^PS(52.52 
  
 Entire File 
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Albany

NUMBER: 783                             IA #: 783
  FILE NUMBER: 59                       GLOBAL ROOT: PS(59,
  DATE CREATED: AUG 30, 1993            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA273-E
  ORIGINAL NUMBER: 273                  ID: PS(59,
 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 EMAIL GROUP 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 December 31, 2006.  #59 -- PHARMACY SITE FILE  ^PS(59 
  
 59,1          SITE DEA NUMBER        SAND;1 FREE TEXT 59,2          SITE 
 (NATIONAL NAME)   SAND;2 POINTER TO QUIC 
                                             SORT DATA FILE 
                                             (#736) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Albany

NUMBER: 784                             IA #: 784
  DATE CREATED: SEP 09, 1993
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: XQORM
  NAME: DBIA275-B                       ORIGINAL NUMBER: 275
  ID: XQORM
 GENERAL DESCRIPTION:   Purpose: 
  
 Request an integration agreement between the Discharge Summary Team and the
 OE/RR Team at the Salt Lake ISC for Discharge Summary version 1.0: 1.  to
 access protocol descriptions by direct reference to the ^ORD(101, and 2.
 permission to call ^XQORM as described below.  
  
 Description: To allow the user to get a detailed description of the actions
 that are executable from each of our menu-type protocols, we 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.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DISCHARGE SUMMARY  ISC: Salt Lake City

NUMBER: 785                             IA #: 785
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA276-B
  ORIGINAL NUMBER: 276                  ID: PSRX(
GLOBAL REFERENCE: PSRX(
FIELD NUMBER: .01                       FIELD NAME: RX #
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PATIENT STATUS
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PROVIDER
  LOCATION: 0;4                         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: 9                         FIELD NAME: # OF REFILLS
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SIG
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 17                        FIELD NAME: UNIT PRICE OF DRUG
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 100                       FIELD NAME: STATUS
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 27                        FIELD NAME: NDC
  LOCATION: 2;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 101                       FIELD NAME: LAST DISPENSED DATE
  LOCATION: 3;1                         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
 GENERAL DESCRIPTION:   This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas

NUMBER: 786                             IA #: 786
  FILE NUMBER: 52.5                     GLOBAL ROOT: PS(52.5,
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA785-C
  ORIGINAL NUMBER: 785                  ID: PS(52.5,
GLOBAL REFERENCE: PS(52.5,
FIELD NUMBER: 2                         FIELD NAME: PRINTED
  LOCATION: P;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: RX#
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   "B" x-ref also used in a Direct Global Read 
FIELD NUMBER: .02                       FIELD NAME: SUSPENSE DATE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   "C" x-ref also used in a Direct Global Read 
FIELD NUMBER: .05                       FIELD NAME: PARTIAL
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
  ISC: Birmingham
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 787                             IA #: 787
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: SEP 09, 1993
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA786-D
  ORIGINAL NUMBER: 786                  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 EMAIL GROUP 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 
  
               File  #55    -   Pharmacy Patient 
               Field #52    -   Prescription Profile - ^PS(55,D0,P,0)=^55.03^^ 
               Field  #.01  -   Prescription Profile - ^PS(55,D0,P,D1,0) 1 
                                Pointer to the Prescription file #52 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas

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: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  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
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 10/19/23, effective with patch PX*1.0*235 to
 document ICR in legacy code 

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
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   APAT and Above PAR request permission for READ access
 to the UNIT OF ISSUE (#420.5) file using FileMan APIs during the creation and
 display of purchase orders, stock issues, and Orthotic and Lab Work Orders
 (OWL) in order to procure or display using the correct packaging unit.  Fields 
 accessed include .01 NAME and 1 FULL NAME.  The "B" cross reference is used in
 determining that a UNIT OF ISSUE is valid.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   APAT and Above PAR request permission for READ access
 to the UNIT OF ISSUE (#420.5) file using FileMan APIs during the creation and
 display of purchase orders, stock issues, and Orthotic and Lab Work Orders
 (OWL) in order to procure or display using the correct packaging unit.  Fields 
 accessed include .01 NAME and 1 FULL NAME.  The "B" cross reference is used in
 determining that a UNIT OF ISSUE is valid. 

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: 811                             IA #: 811
  DATE CREATED: OCT 05, 1993            CUSTODIAL PACKAGE: DISCHARGE SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMRDXTRT
  NAME: DBIA288-B                       ORIGINAL NUMBER: 288
  ID: GMRDXTRT
 GENERAL DESCRIPTION:   Discharge Summary hereby grants permission for Health
 Summary to call into the routine MAIN^GMRDXTRT with the formal parameters DFN,
 TIME1 (inverted late dictation date/time), TIME2 (inverted early dictation
 date/time), OCCLIM (occurrence limit), and TEXT (a boolean flag indicating
 whether or not to include the textual report). This entry point is called by
 both GMTSDS and GMTSDSB to extract the information appropriately, and will be
 supported by Discharge Summary as described here until otherwise agreed.  
  
 In fact, rather than creating a GMRD namespaced option to call the ad hoc
 Health Summary, we're letting DIFROM attach the GMTS HS ADHOC option to the
 GMRD DICTATION HELP MENU option.  The return array for Discharge Summary's
 extract routine, GMRDXTRT, will look like this: 
  
 ^TMP("GMRD",$J,INVERSE DICT DATE,COUNT)=ADM DATE^DISCH DATE 
                ^DICTATING PHYS^ATTENDING PHYS^TREATING SPECIALTY 
                ^SIGNATURE STATUS^COSIGNATURE DATE/TIME ^TMP("GMRD",$J,INVERSE
 DICT DATE,COUNT,"TEXT",LINE,0)=EACH LINE OF THE REPORT TEXT 
  
 This structure for the return array will be maintained indefinitely, until
 otherwise agreed.  
  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MAIN
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

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: 816                             IA #: 816
  DATE CREATED: OCT 25, 1993            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: HEALTH SUMMARY COMPONENTS FOR PDX
  ORIGINAL NUMBER: 297
 GENERAL DESCRIPTION:   The PDX application is granted permission to extract
 the following Health Summary Components using the function documented in
 integration agreement #815: 
  
    Health Summary Component      Abbreviation 
    ---------------------------   ------------
    ADVERSE REACTIONS/ALLERGIES   ADR 
    CLINICAL WARNINGS             CW 
    CRISIS NOTES                  CN 
    DIETETICS                     DI 
    EKG                           EKG 
    LAB BLOOD AVAILABILITY        BA 
    LAB BLOOD TRANSFUSIONS        BT 
    LAB CHEMISTRY & HEMATOLOGY    CH 
    LAB CUMULATIVE SELECTED       SCLU 
    LAB CUMULATIVE SELECTED 1     SCL1 
    LAB CUMULATIVE SELECTED 2     SCL2 
    LAB CUMULATIVE SELECTED 3     SCL3 
    LAB CUMULATIVE SELECTED 4     SCL4 
    LAB CYTOPATHOLOGY             CY 
    LAB MICROBIOLOGY              MIC 
    LAB MICROBIOLOGY BRIEF        BMIC 
    LAB ORDERS                    LO 
    LAB ORDERS BRIEF              BLO 
    LAB SURGICAL PATHOLOGY        SP 
    LAB TESTS SELECTED            SLT 
    MAS ADMISSIONS/DISCHARGES     ADC 
    MAS ADT HISTORY               ADT 
    MAS CLINIC VISITS FUTURE      CVF 
    MAS CONTACTS                  CON 
    MAS CLINIC VISITS PAST        CVP 
    MAS DEMOGRAPHICS              DEM 
    MAS DEMOGRAPHICS BRIEF        BDEM 
    MAS DEMOGRAPHICS OTHER        CDEM 
    MAS DISABILITIES              DS 
    MAS DISCHARGE DIAGNOSIS       DD 
    MAS DISCHARGES                DC 
    MAS MH CLINIC VISITS FUTURE   MHFV 
    MAS PROCEDURES ICD CODES      PRC 
    MAS SURGERIES ICD CODES       OPC 
    MAS TRANSFERS                 TR 
    MAS TREATING SPECIALTY        TS 
    MEDICINE SUMMARY              MED 
    MEDS BY DRUG CLASS            RXDC 
    MEDS BY RX ORD ITEM           RXOI 
    MH HIGH RISK PRF HX           MHRF 
    MH TREATMENT COORDINATOR      MHTC 
    ORDERS CURRENT                ORC 
    ORDERS PENDING                ORP 
    PCE IMMUNIZATIONS             IM 
    PCE IMMUNIZATIONS DETAILED    DIM 
    PHARMACY (OP BY DRUG CLASS)   RXDC 
    PHARMACY (OP BY RX ORD ITEM)  RXOI 
    PHARMACY INTRAVENOUS          RXIV 
    PHARMACY OUTPATIENT           RXOP 
    PHARMACY UNIT DOSE            RXUD 
    PROGRESS NOTES                PN 
    PROGRESS NOTES BRIEF          BPN 
    PROGRESS NOTES SELECTED TITLE SPNT 
    RADIOLOGY IMPRESSION          RI 
    RADIOLOGY PROFILE             RP 
    RADIOLOGY STATUS              RS 
    SURGERY ONLY REPORTS          SRO 
    SURGERY NON OR PROCEDURES     NSR 
    SURGERY REPORTS               SR 
    SURGERY REPORTS BRIEF         BSR 
    SURGERY SEL NON OR PROCEDURES SNSR 
    VITAL SIGNS                   VS 
    VITAL SIGNS SELECTED          SVS 
    WH PREGNANCY DOCUMENTATION    WHP 
    WH LACTATION DOCUMENTATION    WHL 
    WH PREGNANCY & LACTATION DOC  WHPL 
  
 Amended 5/13/2022: Added MAS DEMOGRAPHICS OTHER for sexual orientation.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE
  ISC: Albany
  DATE ACTIVATED: JUN 12, 2015

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: 1                  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: 822                             IA #: 822
  FILE NUMBER: 50.6                     GLOBAL ROOT: PSNDF(
  DATE CREATED: OCT 25, 1993            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA302-B
  ORIGINAL NUMBER: 302                  ID: PSNDF(
 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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
  
 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.6    .01     0;1          VA GENERIC NAME                  B 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
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 EMAIL GROUP 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

NUMBER: 824                             IA #: 824
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA302-D
  ORIGINAL NUMBER: 302                  ID: PSRX(
 GENERAL DESCRIPTION:   
    File    Field   Node;Piece   Description    (Field name)      X-Refs 
    -----   -----   ----------   ------------------------------   ------
    52      .01     0;1          RX #                             B 
            1       0;13         ISSUE DATE 
            4       0;4          PROVIDER 
            6       0;6          DRUG                  << see note (i) >> 
            7       0;7          QTY 
            8       0;8          DAYS SUPPLY 
            9       0;9          # OF REFILLS 
            10      0;10         SIG                   << see note (ii) >> 
            12      3;7          REMARKS 
            16      0;16         CLERK CODE 
            20      2;9          DIVISION 
            22      2;2          FILL DATE 
            26      2;6          EXPIRATION DATE 
            52     (multiple in  REFILL                           B 
                    file 52.1) 
            100     0;15         STATUS                << see note (iii) >> 
            101     3;1          LAST DISPENSED DATE   << see note (iv) >> 
  
    File    Field   Node;Piece   Description    (Field name)      X-Refs 
    -----   -----   ----------   ------------------------------   ------
    52.1    .01     0;1          REFILL DATE                      B 
  
   Notes: 
       (i) Points to the DRUG file (#50), not the NATIONAL DRUG 
           file (#50.6).  This could give incorrect drug name if pointer 
           is in the NATIONAL DRUG file.  
      (ii) This is parsed by spaces within the free text.  If an entry 
           is not found in the MEDICATION INSTRUCTION file (#51), the 
    &      free text is used.  
     (iii) This is calculated using the module STAT^PSOEXDT 
      (iv) This will always be the last fill, not just last refill 
  
  This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE
  ISC: Albany
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham
 SUBSCRIBING DETAILS:   Needed only for OP v 6.  

NUMBER: 825                             IA #: 825
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: OCT 25, 1993
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA302-E
  ORIGINAL NUMBER: 302                  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 EMAIL GROUP 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.  
  
   File    Field   Node;Piece   Description    (Field name)      X-Refs 
    -----   -----   ----------   ------------------------------   ------
    55      .01     0;1          NAME                             B 
            1       1;1          NARRATIVE 
            52     (multiple in  PRESCRIPTION PROFILE 
                    file 55.03) 
  
     File    Field   Node;Piece   Description    (Field name)      X-Refs 
    -----   -----   ----------   ------------------------------   ------
    55.03   .01     0;1          PRESCRIPTION PROFILE             B,A 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE
  ISC: Albany
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas

NUMBER: 826                             IA #: 826
  FILE NUMBER: 61                       GLOBAL ROOT: LAB(61,
  DATE CREATED: JUN 20, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA303-B
  ORIGINAL NUMBER: 303                  ID: LAB(61,
 GENERAL DESCRIPTION:   QUIC is granted an integration agreement with
 Laboratory to obtain the rate of completion of at least one Glycosalated
 Hemoglobin measurement within one year for diabetic patients on a medication
 regimen.  The lab files/fields used in the QIP3* routines are: 
  
  
 GLOBAL MAP DATA DICTIONARY #61 -- TOPOGRAPHY FIELD FILE TORED IN ^LAB(61,      
          SITE: ISC BIRMINGHAM 
 -------------------------------------------------------------------------
 ^LAB(61,D0,0)= (#.01) NAME [1F] ^ 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 827                             IA #: 827
  FILE NUMBER: 63                       GLOBAL ROOT: LR(
  DATE CREATED: JUN 20, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA303-C
  ORIGINAL NUMBER: 303                  ID: LR(
 GENERAL DESCRIPTION:   QUIC is granted an integration agreement with
 Laboratory to obtain the rate of completion of at least one Glycosalated
 Hemoglobin measurement within one year for diabetic patients on a medication
 regimen.  The lab files/fields used in the QIP3* routines are: 
  
 GLOBAL MAP DATA DICTIONARY #63 -- LAB DATA FIELD STORED IN ^LR(                
    SITE: ISC BIRMINGHAM 
 --------------------------------------------------------------------------
 ^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 of patient's Glycosalated 
           Hemoglobin test ^ 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

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: 1                  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
  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 
  DATE ACTIVATED: APR 26, 2012

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: 1
  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
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

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: 838                             IA #: 838
  FILE NUMBER: 409.5                    GLOBAL ROOT: SDV(
  DATE CREATED: DEC 23, 1993            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA325-D
  ORIGINAL NUMBER: 325                  ID: SDV(
 GENERAL DESCRIPTION:   
                For SCHEDULING VISITS (#409.5) file: 
  
       "ADT" cross reference  (^SDV("ADT",DFN,Visit Date)=ptr): 
  
       This cross-reference is used to find all of a patient's stops 
       on a specific date.  
  
       CLINIC STOP CODE (#10) field (sub-file #409.51): 
       Zeroth node  (^SDV(ptr,"CS",ien,0)): 
  
       Field Name/#/Piece on node                 Reason Needed 
       ============================               =============
       ASSOCIATED CLINIC (#3)  (3)                Need clinic to see of it 
                                                  is non-count 
       APPOINTMENT TYPE (#5)  (5)                 Need to see if Appointment 
                                                  Type is billable 
       OUTPATIENT ENCOUNTER (#8)  (8)             Need pointer to the 
                                                  Outpatient Encounter (if 
                                                  it exists) to see if visit 
                                                  was related to claimed 
                                                  exposures 
  STATUS: Retired                       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: 1
  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: 841                             IA #: 841
  GLOBAL ROOT: DIC(                     DATE CREATED: JAN 12, 1994
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  NAME: DBIA329-C                       ORIGINAL NUMBER: 329
  ID: DIC(
 GENERAL DESCRIPTION:   DICRW+5^ESPFM, the reference to ^DIC(+Y,0,"GL") 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: POLICE & SECURITY  ISC: Dallas

NUMBER: 842                             IA #: 842
  GLOBAL ROOT: DD(                      DATE CREATED: JAN 12, 1994
  CUSTODIAL PACKAGE: 1                  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: 843                             IA #: 843
  FILE NUMBER: 61                       GLOBAL ROOT: LAB(61,
  DATE CREATED: JAN 14, 1994            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA333-B
  ORIGINAL NUMBER: 333                  ID: LAB(61,
 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 #61 -- TOPOGRAPHY FIELD FILE STORED IN ^LAB(61,     
           SITE: BIRMINGHAM ISC 
 --------------------------------------------------------------------------
 ^LAB(61,D0,0)= (#.01) NAME [1F] ^ 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

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: 853                             IA #: 853
  GLOBAL ROOT: DIC(                     DATE CREATED: FEB 02, 1994
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  NAME: DBIA345-B                       ORIGINAL NUMBER: 345
  ID: DIC(
 GENERAL DESCRIPTION:   
        Read only access for ^DIC(FN,0,"GL"), where FN is a file number, to
 verify the the value of DIC prior to initiating the look-up (GMPTA4).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL LEXICON UTILITY
  ISC: Salt Lake City

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: 857                             IA #: 857
  DATE CREATED: FEB 04, 1994            CUSTODIAL PACKAGE: TOOLKIT
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Other                           NAME: DBIA346-E
  ORIGINAL NUMBER: 346
 GENERAL DESCRIPTION:   
        Agreement is to add XTLK name-spaced Option XTLKUSER2 to the GMPT
 CLINICAL LEXICON MGT MENU so managers can add keywords, short-cuts and
 synonyms to the ^XT(8984.* files without leaving the Clinical Lexicon Manager
 menu.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LEXICON UTILITY    ISC: Salt Lake City

NUMBER: 858                             IA #: 858
  GLOBAL ROOT: XUTL                     DATE CREATED: FEB 28, 1994
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  NAME: DBIA351-B                       ORIGINAL NUMBER: 351
  ID: XUTL
 GENERAL DESCRIPTION:   Use of ^XUTL:  The XQOR routines use ^XUTL("XQORM") and
 ^XUTL("XQORW") to store compiled protocol menus.  An agreement to allow use of
 these global nodes would partially replace DBIA #4 (which erroneously 
 identifies the node used as ^XUTL("ORUM")).  The portion of DBIA #4 which
 allows OE/RR to use ^XUTL("OR",$J,package namespace) would need to remain as
 is.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

NUMBER: 859                             IA #: 859
  GLOBAL ROOT: DISV(                    DATE CREATED: FEB 28, 1994
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Controlled Subscription        TYPE: File
  NAME: DBIA351-C                       ORIGINAL NUMBER: 351
  ID: DISV(                             STATUS: Retired
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: UNWINDER
 SUBSCRIBING DETAILS:   read/write access to ^DISV(DUZ,"XQORM") 
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   READ and WRITE access to ^DISV(DUZ,"XQ") 

NUMBER: 860                             IA #: 860
  DATE CREATED: FEB 28, 1994            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         ROUTINE: XQ12
  NAME: DBIA351-D                       ORIGINAL NUMBER: 351
  ID: XQ12
 GENERAL DESCRIPTION:   Call to ABT^XQ12:  The Unwinder calls ABT^XQ12.  I
 believe this is part of the response time monitoring.  The local variable,
 XQXFLG, is also checked when making this call.  Agreement is made to call
 ABT^XQ12 and check the XQXFLG variable or this needs to be placed on the list
 of supported references.  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ABT
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

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
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

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
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

NUMBER: 863                             IA #: 863
  DATE CREATED: SEP 07, 2004
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: ORUPREF2
  NAME: ORUPREF2                        ORIGINAL NUMBER: 863
  ID: ORUPREF2                          STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN3
 COMPONENT DESCRIPTION:   Utility for 'on-the-fly' protocol creation.  See
 OE/RR Developers guide.  
VARIABLES: ORPKG                        TYPE: Input
 VARIABLES DESCRIPTION:   Package pointer.  
VARIABLES: ORDEF                        TYPE: Input
 VARIABLES DESCRIPTION:   Default protocol for setting up protocols.  
VARIABLES: ORFL                         TYPE: Input
 VARIABLES DESCRIPTION:   File link - variable pointer for procedure file.  
VARIABLES: ORDANM                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional name of the protocol.  
VARIABLES: ORDA                         TYPE: Input
 VARIABLES DESCRIPTION:   Internal number of an existing protocol to be
 updated.  
VARIABLES: OREA                         TYPE: Input
 VARIABLES DESCRIPTION:   Action used in lieu of default defined in OROEF.  
VARIABLES: ORTXT                        TYPE: Input
 VARIABLES DESCRIPTION:   Name of protocol; if not defined, the .01 filed of
 the procedure referenced is used.  
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: GEN. MED. REC. - VITALS
  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

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
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

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
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

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
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

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
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

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
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

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
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

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
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

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
  STATUS: Active                        DURATION: Till Otherwise Agreed
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 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA added as a subscriber to ICR #871 for access to
 EN~ORX8.  This API will be referenced in VIAB MEDHIST RPC for their
 OrderMgmtSv - getMedHistory.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Added 4/13/21, effective with PXRM*2.0*45 and
 OR*3.0*377.  
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   Added 8/30/22, effective with EDP*2*20 
  DATE ACTIVATED: MAR 03, 2009

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
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: 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
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   
  3/27/25 - Historic use documented, as found in patch IB*2.0*770.  

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
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 
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This documents the Vista Integration Adapter
 application's use of the DISPLAY GROUP file (#100.98). The ICR will be used by
 the following RPCs and Services:  VIAB MEDHIST  OrderMgmtSvc - getMedHistory 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 4/18/19 
SUBSCRIBING PACKAGE: CMOP
 SUBSCRIBING DETAILS:   Added 4/18/19 
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   Added 8/26/22 effective with PSS*1*254 patch for the
 FDB v4.4 Upgrade Project 
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 11/10/2022, effective with DSSV 1.1 utilizing the
 "B" index DSS Class 2 product Document Only 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Added 1/17/23, effective with PXRM*2*45 to determine
 the internal entry number (IEN) for a given display group entry 

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
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

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
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
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 4/18/19.  
SUBSCRIBING PACKAGE: CMOP
 SUBSCRIBING DETAILS:   Added 4/18/19.  
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   Added 1/25/22 effective with EDP*2*16 to read File
 100.01 

NUMBER: 885                             IA #: 885
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA885
  ORIGINAL NUMBER: 885                  ID: PSRX(
GLOBAL REFERENCE: PSRX(D0,2)
FIELD NUMBER: 31                        FIELD NAME: RELEASED DATE/TIME
  LOCATION: 2;13                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(AL)
FIELD NUMBER: 31                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(D0,0)
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: 1                         FIELD NAME: ISSUE DATE
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: EXTERNAL PEER REVIEW
  ISC: Albany
 SUBSCRIBING DETAILS:   The Office of Quality Management has requested that the
 External Peer Review software be enhanced to identify patients receiving drugs
 in certain VA classes.  To complete this enhancement, we plan to $ORDER 
 through the AL cross reference on release date in the prescription file for
 the date range involved (the month two months prior to the run date), pull the
 patient and drug (fields 2 and 6) and the VA class of the drug (field 2 of
 file 50).  
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham

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 EMAIL GROUP 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
SUBSCRIBING PACKAGE: EXTERNAL PEER REVIEW
  ISC: Albany

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
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: 1
  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
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: 1
  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
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
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
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
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
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
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.  
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

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: 897                             IA #: 897
  FILE NUMBER: 9001000                  GLOBAL ROOT: APCCCTRL
  DATE CREATED: SEP 06, 1994            CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: DBIA897
  ORIGINAL NUMBER: 897                  ID: APCCCTRL
GLOBAL REFERENCE: APCCCTRL(D0,0)
GLOBAL REFERENCE: APCCCTRL(D0,11,0)
GLOBAL REFERENCE: APCCCTRL(D0,11,D1,0)
GLOBAL REFERENCE: APCCCTRL(D0,11,D1,800)
 GLOBAL DESCRIPTION:   This 800 node has been added by the VA for use with the
 PCE modules.  PCE has the file number series from 800-839, which is why 800
 was used.  
 GENERAL DESCRIPTION:   The PCE Patient/IHS Subset package (PXPT) requests a
 DBIA with Indian Health Service to distribute the PCC MASTER CONTROL FILE
 (9001000).  
  
 The UNCODED ICD DIAGNOSIS CODE and UNCODED ICD PROCEDURE CODE fields were
 added by IHS to support differences in the codes the VA and IHS can use when
 an ICD9 code could not be found for a provider narrative.  These fields are
 only used by PCC logic at this time.  The Clinical Lexicon is currently coded
 to use a VA default ICD9 code only, and does not make use of these fields.  
  
 The PXPT developers added a file description and added an 800 node to the
 Package multiple for Historical load Control and Last Patient Loaded.  
  
 The DEFAULT HEALTH SUMMARY TYPE field is used by PCC logic at the Tucson VAMC. 
 This field is currently only used by PCC logic.  
  
 The following is the Data Dictionary definition being distributed by PXPT: 
 -------------------------------------------------------------------------
 STANDARD DATA DICTIONARY #9001000 -- PCC MASTER CONTROL FILE   09/6/94 
  PAGE 1 STORED IN ^APCCCTRL(  (1 ENTRY)   SITE: SLC   UCI: DVA,DEV 
  
 DATA          NAME                  GLOBAL        DATA ELEMENT       TITLE     
            LOCATION      TYPE 
 ---------------------------------------------------------------------------
 This file is used by both IHS PCC and VA PCE to control interactions between
 DHCP packages and their links to populate visit related files.  
  
  
               DD ACCESS: @ 
              DEL ACCESS: @ 
            AUDIT ACCESS: @ 
  
  
 CROSS REFERENCED BY: SITE(B) 
  
  
 9001000,.01   SITE                   0;1 POINTER TO LOCATION FILE (#9999999 
                                 .06) (Required) 
  
               INPUT TRANSFORM:  S:$D(X) DINUM=X 
               DESCRIPTION:      This is the facility's site name.  This is 
                                 a pointer to the SITE file.  
  
                                 Enter the name of the site used for this 
                                 facility.  
  
               NOTES:            XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER 
  
               CROSS-REFERENCE:  9001000^B 
                                 1)= S ^APCCCTRL("B",$E(X,1,30),DA)="" 
                                 2)= K ^APCCCTRL("B",$E(X,1,30),DA) 
  
  
 9001000,.02   TYPE OF LINK           0;2 SET (Required) 
  
                                 '0' FOR DATE ONLY REQUIRED; 
                                 '1' FOR TIME REQUIRED; 
               LAST EDITED:      APR  2, 1990 
               DESCRIPTION:      This flag is set in order to allow some 
                                 flexibility in how visits are created. Some 
                                 sites might be such that they only want to 
                                 use the date were other sites require that 
                                 a time is used in the visit.  
  
                                 Enter a code which represents which type of 
                                 visit is allowed. enter a "0" for date only 
                                 or a "1" for date and time being required.  
  
  
 9001000,.03   DEFAULT HEALTH SUMMARY TYPE 0;3 POINTER TO HEALTH SUMMARY TYP 
                                 E FILE (#142) 
  
               LAST EDITED:      MAY  7, 1992 
               HELP-PROMPT:      Select a summary type from the VA Health 
                                 Summary Type file to be used as a default 
                                 when generating a health summary.  
               DESCRIPTION:      This is the default Health Summary type 
                                 that will be used for this site.  It is 
                                 chosen from the list of Health Summaries in 
                                 the "Health Summary Type" file.  
  
                                 Select a summary type that you wish to be 
                                 the default for this site.  
  
  
 9001000,.04   TYPE OF VISIT          0;4 SET 
  
               TYPE OF VISIT FOR STATISTICAL PURPOSES 
                                 'I' FOR IHS; 
                                 'C' FOR CONTRACT; 
                                 'O' FOR OTHER; 
                                 'T' FOR TRIBAL; 
                                 '6' FOR 638 PROGRAM; 
                                 'V' FOR VA; 
               LAST EDITED:      MAY 31, 1990 
               DESCRIPTION:      This is the type of visit that is made at 
                                 this site. It is generally used for 
                                 statistical purposes.  
  
                                 Enter the code that best describes the 
                                 visits made at this site.  
  
  
 9001000,.05   UNCODED ICD DIAGNOSIS CODE 0;5 POINTER TO ICD DIAGNOSIS FILE 
                                 (#80) 
  
               LAST EDITED:      MAR 29, 1993 
               HELP-PROMPT:      Select an ICD DIAGNOSIS code to represent 
                                 "uncodable" diagnoses.  
  
 9001000,.06   UNCODED ICD PROCEDURE CODE 0;6 POINTER TO ICD OPERATION/PROCE 
                                 DURE FILE (#80.1) 
  
               LAST EDITED:      MAR 29, 1993 
               HELP-PROMPT:      Select an ICD OPERATION/PROCEDURE code to 
                                 represent "uncodable" procedures.  
  
 9001000,1101  PACKAGE                11;0 POINTER Multiple #9001000.011 
                                  (Add New Entry without Asking) 
  
               DESCRIPTION:      This is the ancillary package that has 
                                 links to the v files.  
  
                                 Enter the name of a package.  
  
  
 9001000.011,.01 PACKAGE                0;1 POINTER TO PACKAGE FILE (#9.4) 
                                    (Required) (Multiply asked) 
  
                 INPUT TRANSFORM:  S:$D(X) DINUM=X 
                 DESCRIPTION:      This is the ancillary package that has 
                                   links to the v-file.  
  
                                   Enter the name of an ancillary package.  
  
                 NOTES:            XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAM MER 
  
  
 9001000.011,.02 PASS DATA TO PCC ?     0;2 SET (Required) 
  
                                   '0' FOR NO; 
                                   '1' FOR YES; 
                 HELP-PROMPT:      If you want data to be passed from this 
                                   package to the v-files you must answer 1 
                                   (YES).  
                 DESCRIPTION:      This is the on and off flag that allows 
                                   data to be passed from an ancillary 
                                   package to the v-files.  
  
                                   Enter a "0" to turn off the link or a "1" 
                                   to turn on the link.  
  
  
 9001000.011,.03 PACKAGE FLAG           0;3 FREE TEXT 
  
                 INPUT TRANSFORM:  K:$L(X)>10!($L(X)<1) X 
                 LAST EDITED:      JUN  5, 1990 
                 HELP-PROMPT:      Answer must be 1-10 characters in length.  
                 DESCRIPTION:      This flag is for internal use by the 
                                   package.  
  
  
 9001000.011,800.01HISTORICAL LOAD CONTROL 800;1 SET 
  
                                   '0' FOR NO; 
                                   '1' FOR YES; 
                 LAST EDITED:      NOV 16, 1993 
                                   This field is currently not inuse.  
  
  
 9001000.011,800.02LAST PATIENT LOADED  800;2 FREE TEXT 
  
                 INPUT TRANSFORM:  K:$L(X)>30!($L(X)<1) X 
                 LAST EDITED:      FEB  2, 1994 T:      Answer must be 1-30
 characters in length.  
                 DESCRIPTION:      This is a field that allows a process to 
            keep track of the last patient that was 
                                   processed. In case of failure that 
                                   process can find out where it last 
                                   completed a process and where to restart 
                                   at.  
  
                                   Enter the number or name of the last 
                                   patient processed.  
  
  
  
  
  
       FILES POINTED TO                      FIELDS 
  
 HEALTH SUMMARY TYPE (#142)        DEFAULT HEALTH SUMMARY TYPE (#.03) 
  
 ICD DIAGNOSIS (#80)               UNCODED ICD DIAGNOSIS CODE (#.05) 
  
 ICD OPERATION/PROCEDURE (#80.1)   UNCODED ICD PROCEDURE CODE (#.06) 
  
 LOCATION (#9999999.06)            SITE (#.01) 
  
 PACKAGE (#9.4)                    PACKAGE:PACKAGE (#.01) 
  
  
 INPUT TEMPLATE(S): 
  
 PRINT TEMPLATE(S): 
  
 SORT TEMPLATE(S): 
  
 The PXPT Post Installation routine creates a PCC Master Control File entry if
 it does not exist for the facility.  The DEFAULT INSTITUTION field in the
 Kernel Site Parameters File is used as the facility.  
  
  STATUS: Retired
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   The Patient/IHS Subset package will be the custodial
 package of the PCC Master Control File for distribution in the VA.  

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: 899                             IA #: 899
  FILE NUMBER: 101.11                   GLOBAL ROOT: XUTL('XQORW',
  DATE CREATED: JUN 02, 1994
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: DBIA899
  ORIGINAL NUMBER: 899                  ID: XUTL('XQORW',
 GENERAL DESCRIPTION:   When OE/RR handles the prompting for generic orders,
 prompts that require word processing answers store the entered text
 temporarily in file 101.11 (XQOR WORD PROCESSING).  The lifespan of an entry 
 in this file is several minutes.  The Unwinder uses this file when handling
 the order prompting for OE/RR.  Since this file is an OE/RR file, the Unwinder
 needs an integration agreement for both read and write access to this file.  
  
 It would be possible to move this file into the Unwinder package.  However,
 this portion of the Unwinder is currently used exclusively by OE/RR.  Since
 the portion of OE/RR that handles order dialogs is being rewritten (so OE/RR
 can handle the front door), I would prefer to wait until version 3 of OE/RR
 before shifting around the custody of files too much.  
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 2.5
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

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
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
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
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: 903                             IA #: 903
  GLOBAL ROOT: DD(                      DATE CREATED: JUL 08, 2003
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  NAME: DBIA903                         ORIGINAL NUMBER: 903
  ID: DD(
GLOBAL REFERENCE: DD(42,.03,0)
GLOBAL REFERENCE: DD(50,62,.02,0)
GLOBAL REFERENCE: DD(50,62.03 0)
GLOBAL REFERENCE: DD(50,62.04,0)
GLOBAL REFERENCE: DD(50,62.05,0)
GLOBAL REFERENCE: DD(50,212,0)
GLOBAL REFERENCE: DD(50,212.2,0)
GLOBAL REFERENCE: DD(50.3,1,0)
GLOBAL REFERENCE: DD(50.3,2,0)
GLOBAL REFERENCE: DD(52.6,2,0)
GLOBAL REFERENCE: DD(52.6,16,1,0)
GLOBAL REFERENCE: DD(53.1,53,0)
GLOBAL REFERENCE: DD(53.1,X,Y)
GLOBAL REFERENCE: DD(55.01)
GLOBAL REFERENCE: DD(55.01,.04,1,0)
GLOBAL REFERENCE: DD(55.01,.100,0)
GLOBAL REFERENCE: DD(55.04,.02,0)
GLOBAL REFERENCE: DD(55,06)
GLOBAL REFERENCE: DD(55.06)
GLOBAL REFERENCE: DD(55.06,0)
GLOBAL REFERENCE: DD(55.06,.01,0)
GLOBAL REFERENCE: DD(55.06,6,1,0)
GLOBAL REFERENCE: DD(55.06,42,1,0)
GLOBAL REFERENCE: DD(55.06,54,1,0)
GLOBAL REFERENCE: DD(55.06,63,1,0)
GLOBAL REFERENCE: DD(55.06,71,O)
GLOBAL REFERENCE: DD(55.06,[1,10,25,106])
GLOBAL REFERENCE: DD(55.07,.07,1,0)
GLOBAL REFERENCE: DD(55.07,.12,1,0)
GLOBAL REFERENCE: DD(59.51,.02,0)
GLOBAL REFERENCE: DD(101,10,0)
GLOBAL REFERENCE: DD(53.1,28,0)
GLOBAL REFERENCE: DD(53.1,.24,0)
 GENERAL DESCRIPTION:   Inpatient Medications version 5.0 accesses the zero
 node of fields in ^DD(42, ^DD(50, ^DD(50.3, ^DD(52.6, ^DD(53.1, ^DD(55,
 ^DD(59, and ^DD(101, 
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 4.5
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham

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
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 

NUMBER: 906                             IA #: 906
  FILE NUMBER: 121.2                    GLOBAL ROOT: GMR(121.2,
  DATE CREATED: JUL 07, 1994            CUSTODIAL PACKAGE: PROGRESS NOTES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: DBIA906
  ORIGINAL NUMBER: 906                  ID: GMR(121.2,
GLOBAL REFERENCE: GMR(121.2,D0,0)
FIELD NUMBER: .02                       FIELD NAME: TYPE OF PROGRESS NOTE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Health Summary is accessing file GMR(121.2, to get the
 title of a progress note for displaying in the Progress Notes components.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

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
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 
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 4/10/24 effective with patch DSSO*2.0*6 for a
 cross-reference to be added to the VISIT (#1) field of the DSSO PCE STATUS
 (#23645.3) file.  

NUMBER: 908                             IA #: 908
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA908
  ID: SC(
GLOBAL REFERENCE: SC(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: 3                         FIELD NAME: INSTITUTION
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TYPE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3.5                       FIELD NAME: Division
  LOCATION: 0:15                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,'I')
FIELD NUMBER: 2505                      FIELD NAME: INACTIVATE DATE
  LOCATION: I;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2506                      FIELD NAME: REACTIVATE DATE
  LOCATION: I;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC('B',
FIELD NUMBER: .01                       FIELD NAME: NAME
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   B Cross Reference 
GLOBAL REFERENCE: SC('C',
FIELD NUMBER: 1                         FIELD NAME: ABBREVIATION
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   C Cross Reference 
GLOBAL REFERENCE: SC(D0,'S',D1,1,D2,0)
GLOBAL REFERENCE: SC(n,42)
FIELD NUMBER: 42                        FIELD NAME: WARD LOCATION FILE POINTER
  LOCATION: 42;1                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Read only access for the ^SC global.  
  
      Read ^SC(n,0) to obtain Hospital Location name, abbreviation and 
       Division.  
  
      Read ^SC(n,42) to obtain ward location file pointer to obtain field 
       #.017 Specialty in the Ward Location file #42.  
  
      Read ^SC("B", and ^SC("C", cross references to get patient location 
           internal entry #: $O(^SC("B",X,0)) and $O(^SC("C",X,0)).  
  
      Read access to the ^SC(D0,"I") node to obtain inactivate date 
        (field # 2505) and re-activate date (field # 2506).  
  
      Read only access to ^SC(D0,"S",D1,1,D2,0) to access patients by 
        clinic location and clinic date to print lab report.  
  
      Read only access to ^SC(D0,"S",DATE) used to check if a clinic 
        meets on a specified date.         
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  ISC: Hines
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN

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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 910                             IA #: 910
  DATE CREATED: JUL 20, 1994            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Other                           NAME: DBIA910
  ORIGINAL NUMBER: 910
 GENERAL DESCRIPTION:   
  
 Lab is requesting a new domain for the purpose of uploading a monthly
 laboratory workload reports to Austin.  The increase in traffic should be less
 than 30K per institution once per month.  Typically a message is about 200
 lines.  
  
 NAME:NONE                  FLAGS: S 
   DNS  DHCP ROUTING INDICATOR:LAB 
   PHYSICAL LINK DEVICE:  MINIOUT TRANSMISSION SCRIPT: SCRIPT TEXT: 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 912                             IA #: 912
  GLOBAL ROOT: DIC(                     DATE CREATED: JUL 21, 1994
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  NAME: DBIA912                         ORIGINAL NUMBER: 912
  ID: DIC(
 GENERAL DESCRIPTION:   ^DIC("AC" - Screen lookup on files for the Lab
 application group.  ^DIC("AC","LR" 
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: Fileman 20
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
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
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: 1                  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                        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: 917                             IA #: 917
  GLOBAL ROOT: DISV(                    DATE CREATED: JUL 26, 1994
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  NAME: DBIA917                         ORIGINAL NUMBER: 917
  ID: DISV(
 GENERAL DESCRIPTION:   NOTE: This DBIA has been combined into DBIA #510 and
 has been retired.  
  
 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:"?") 
  
 Lab needs an agreement for read/write access to ^DISV(DUZ,"LRACC") and
 ^DISV(DUZ,"LRAN") 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 920                             IA #: 920
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA920
  ORIGINAL NUMBER: 920                  ID: PSRX(
GLOBAL REFERENCE: PSRX(x,0)
FIELD NUMBER: 6                         FIELD NAME: DRUG
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,DFN,'P',X)
FIELD NUMBER: .01                       FIELD NAME: PRESCRIPTION PROFILE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Read only access for the ^PSRX(x,0) node.  
  
 In routines LRBLPE1 and LRBLPH: 
  
 ...I $D(^PSRX(Y,0)) S ^TMP($J,+$P(^(0),"^",6))=O 
  
 We are $O(^PS(55,DFN,"P",X)) to build the ^TMP( array.  We then use that array
 for possible data.  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
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 EMAIL GROUP 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: 922                             IA #: 922
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55
  DATE CREATED: JUL 27, 1994
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA922
  ORIGINAL NUMBER: 922                  ID: PS(55
GLOBAL REFERENCE: PS(55,dfn,'IV',x,'AD',y,0)
FIELD NUMBER: .01                       FIELD NAME: ADDITIVE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,dfn,5,x,1,y,0)
FIELD NUMBER: .01                       FIELD NAME: DRUG
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 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 EMAIL GROUP 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 
  
 Read only access to the following nodes in the Pharmacy Patient file #55.  
  
 All these references are found in routines LRBLPE1 and LRBLPH.  
  
 ^PS(55,DFN,"IV",X,"AD",Y,0) 
  
 K ^TMP($J) F X=0:0 S X=$O(^PS(55,DFN,"IV",X)) Q:'X!(R[U)  F Y=0:0 
      S Y=$O(^PS(55,DFN,"IV",X,"AD",Y)) Q:'Y!(R[U)  S ^TMP($J,+^(Y,0))="" 
  
 ^PS(55,DFN,5,X,1,Y,0) 
  
 K ^TMP($J) F X=0:0 S X=$O(^PS(55,DFN,5,X)) Q:'X!(R[U)  F Y=0:0 
      S Y=$O(^PS(55,DFN,X,1,Y)) Q:'Y!(R[U)  S ^TMP($J,+^(Y,0)="" 
  
 NOTE: Inpatient Medication allows direct access to the Inpatient Medication 
 data, with the understanding that this structure may change in Inpatient Meds
 version 5.0. If a change is necessary, Lab will need to supply a patch to call
 an Inpatient utility to provide this data rather than directly accessing the
 global.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 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,
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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
  DATE ACTIVATED: SEP 01, 2010

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,
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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
  DATE ACTIVATED: SEP 02, 2010

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(
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
  DATE ACTIVATED: AUG 01, 1994

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
 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
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 
                CV^COMBAT VET, SHD^SHAD, 
                CLV^CAMP LEJEUNE 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("CLV")       = 1 or
 0, if problem is 
                        related to Camp Lejeune 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("CLV")       = 1 or
 0, if problem is 
                        related to Camp Lejeune 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
  DATE ACTIVATED: AUG 18, 2015

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: 931                             IA #: 931
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT(
  DATE CREATED: AUG 03, 1994            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA931
  ORIGINAL NUMBER: 931                  ID: ICPT(
GLOBAL REFERENCE: ICPT(x,'D',z,0)
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ICPT(x,'LR',y,0)
FIELD NUMBER: 66                        FIELD NAME: BLOOD COMPONENT REQUEST
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Direct read access to the ^ICPT( global, CPT file #81.  
  
 In routine LRBLPCSS, Blood Bank Pre-op Component selection, 
  read node ^ICPT(x,"D",z,0) to print description field.  
  
 In routine LRBLPOST, Blood Bank Post-init, read node ^ICPT(x,"LR").  This will
 move all 66 fields to our own field in ^LAB(66.5, .  This is one time for V.
 5.2 installation only.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
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
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
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

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
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
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: 1                  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

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
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
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
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
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
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
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
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
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
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
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
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
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(
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
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  ISC: Albany
  DATE ACTIVATED: FEB 21, 2014

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
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
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
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
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  ISC: Albany

NUMBER: 956                             IA #: 956
  DATE CREATED: AUG 22, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VAFHLZIR                     NAME: DBIA956
  ID: VAFHLZIR
 GENERAL DESCRIPTION:   The IVM package requests use of the function
 $$EN^VAFHLZIR to extract veteran income relation data to transmit to the IVM
 Center.  
  
 The Ambulatory Care Database Project requests use of the function 
 $$EN^VAFHLZIR to extract veteran income relation data to transmit to NPCDB. 
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$EN(IEN,FLDS,SETID)
 COMPONENT DESCRIPTION:   This function call is made to create the HL7 ZIR
 segment string.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN is the internal entry number for the entry in the
 INCOME RELATION (#408.22) file for which data is to be extracted.  
VARIABLES: FLDS                         TYPE: Input
 VARIABLES DESCRIPTION:   FLDS contains a list of the fields in the HL7 ZIR
 segment, concatenated with commas, which should be extracted for the entry.  
VARIABLES: SETID                        TYPE: Input
 VARIABLES DESCRIPTION:   SETID is used to specify the SET ID field in the HL7
 ZIR segment.  
VARIABLES: SEG                          TYPE: Output
 VARIABLES DESCRIPTION:   SEG is the HL7 ZIR segment string returned by the
 function.  
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  ISC: Albany
SUBSCRIBING PACKAGE: SCHEDULING

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
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
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
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
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
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: 962                             IA #: 962
  DATE CREATED: AUG 22, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGMTU11                      NAME: DBIA962
  ID: DGMTU11
 GENERAL DESCRIPTION:   The IVM package files new Means Tests into the PIMS
 Means Test module.  The routine DGMTU11 is used to retrieve active dependent
 information and update the veteran's income relation record with that data.  
  STATUS: Other                         DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$GETREL(DFN,DGTYPE,DGDT,DGMT)
 COMPONENT DESCRIPTION:   This function call is used to determine all of a
 veteran's active dependents at the time of his Means Test.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN points to the patient in file #2.  
VARIABLES: DGTYPE                       TYPE: Input
 VARIABLES DESCRIPTION:   DGTYPE is a string which contains the type of
 dependents to locate.  
VARIABLES: DGDT                         TYPE: Input
 VARIABLES DESCRIPTION:   DGDT is the date on which active dependents should be
 located.  
VARIABLES: DGREL                        TYPE: Output
 VARIABLES DESCRIPTION:   The output array DGREL contains pointers to all
 desired active dependents in the PATIENT RELATION (#408.12) file.  
VARIABLES: DGDEP                        TYPE: Input
 VARIABLES DESCRIPTION:   DGDEP contains the total number of active dependents. 
 
VARIABLES: DGMT                         TYPE: Input
 VARIABLES DESCRIPTION:   DGMT points to the means test in file #408.31.  
COMPONENT/ENTRY POINT: $$RESET(DFN,DGDT)
 COMPONENT DESCRIPTION:   This call is used to update the veteran's income
 relation record in file #408.22 with the number of dependent children (field
 #.13) and whether he has dependent children (#.08).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN points to the patient in file #2.  
VARIABLES: DGDT                         TYPE: Input
 VARIABLES DESCRIPTION:   DGDT is the date on which active dependents should be
 found.  
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
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  ISC: Albany
SUBSCRIBING PACKAGE: SURGERY            ISC: Birmingham
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 6/24/2025, effective with patch PX*1*244 PCE
 needs to read the field "NON-COUNT CLINIC?" to determine if the hospital
 location for an encounter is billable.  
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Added 6/12/2026, effective with patch MECH*1.0 MECH 1.0
 needs to read the NON-COUNT CLINIC field (44,2502) to determine with Hospital
 Locations should be returned for a user to select as the Ordering Location.  

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
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
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
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
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  ISC: Albany

NUMBER: 969                             IA #: 969
  FILE NUMBER: 408.12                   GLOBAL ROOT: DGPR(408.12,
  DATE CREATED: AUG 22, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA969                         ID: DGPR(408.12,
GLOBAL REFERENCE: DGPR(408.12,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the patient associated with the patient relation. 
 
FIELD NUMBER: .02                       FIELD NAME: RELATIONSHIP
  LOCATION: 0;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the relationship of the relation to the patient.  
FIELD NUMBER: .03                       FIELD NAME: PERSON
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to the relation in either the PATIENT
 (#2) or INCOME PERSON (#408.13) file.  
 GLOBAL DESCRIPTION:   These fields are updated when a new patient relation is
 added to the database along with a new Means Test for the patient.  
GLOBAL REFERENCE: DGPR(408.12,'B',
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This cross-reference is used to find all patient
 relations for a specific patient.  
 GLOBAL DESCRIPTION:   The patient relation records are required to find all
 active dependents of the patient.  
GLOBAL REFERENCE: DGPR(408.12,D0,'E',D1,0)
FIELD NUMBER: .01                       FIELD NAME: EFFECTIVE DATE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the effective date for dependency of the patient
 relation.  
FIELD NUMBER: .02                       FIELD NAME: ACTIVE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field indicates whether the relation is an active or
 inactive dependent of the patient.  
FIELD NUMBER: .03                       FIELD NAME: FILED BY IVM
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field indicates whether the date has been filed by
 the IVM Center.  
FIELD NUMBER: .04                       FIELD NAME: IVM TEST
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to the the IVM Means Test.  
 GLOBAL DESCRIPTION:   A new effective date of dependency is added for all IVM
 dependents and all VAMC dependents inactivated.  
GLOBAL REFERENCE: DGPR(408.12,D0,'E','B',
FIELD NUMBER: .01                       FIELD NAME: EFFECTIVE DATE
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The B cross reference for the effective date multiple is
 used to look at all of the effective dates of dependency for a relation.  
 GLOBAL DESCRIPTION:   These records are needed to determine when a relation
 needs to be inactivated.  
GLOBAL REFERENCE: DGPR(408.12,'AIVM',
FIELD NUMBER: .04                       FIELD NAME: IVM TEST
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This cross-reference is used for the IVM Means Test when
 an effective date is added.  
 GLOBAL DESCRIPTION:   This records are need to determine what records have to
 be deleted when an IVM Means Test is deleted.  
 GENERAL DESCRIPTION:   The IVM package files new Means Tests in the PIMS Means
 Test module.  IVM requests permission to add and update entries in the PATIENT 
 RELATION (#408.12) file, as part of adding a new Means Test.  Additionally,
 permission is requested to delete entries from that file (if the IVM Center
 mistakenly sends a Means Test to a facility).  
  STATUS: Other                         DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  ISC: Albany

NUMBER: 970                             IA #: 970
  FILE NUMBER: 408.13                   GLOBAL ROOT: DGPR(408.13,
  DATE CREATED: AUG 22, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA970                         ID: DGPR(408.13,
GLOBAL REFERENCE: DGPR(408.13,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the name of the relation.  
FIELD NUMBER: .02                       FIELD NAME: SEX
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the sex of the relation.  
FIELD NUMBER: .03                       FIELD NAME: DATE OF BIRTH
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the date of birth of the relation.  
FIELD NUMBER: .09                       FIELD NAME: SOCIAL SECURITY NUMBER
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the Social Security Number of the relation.  
 GLOBAL DESCRIPTION:   These fields are updated when a new income person is
 added to file #408.13 or when IVM data is different then VAMC data.  
 GENERAL DESCRIPTION:   The IVM package files new Means Tests in the PIMS Means
 Test module.  IVM requests permission to add and update entries in the INCOME 
 PERSON (#408.13) file, as part of adding a new Means Test.  Additionally,
 permisssion is requested to delete entries from that file (if the IVM Center
 mistakenly sends a Means Test to a facility).  
  STATUS: Other                         DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  ISC: Albany

NUMBER: 971                             IA #: 971
  FILE NUMBER: 408.21                   GLOBAL ROOT: DGMT(408.21,
  DATE CREATED: AUG 22, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA971
  ID: DGMT(408.21,
GLOBAL REFERENCE: DGMT(408.21,D0,0)
FIELD NUMBER: .01                       FIELD NAME: YEAR
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the income year for the income record.  
FIELD NUMBER: .02                       FIELD NAME: PATIENT RELATION
  LOCATION: 0;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the patient relation in file #408.12 from whom
 the income was reported.  
FIELD NUMBER: .08                       FIELD NAME: SOCIAL SECURITY (NOT SSI)
  LOCATION: 0;8                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: .09                       FIELD NAME: U.S. CIVIL SERVICE
  LOCATION: 0;9                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: .1                        FIELD NAME: U.S. RAILROAD RETIREMENT
  LOCATION: 0;10                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: .11                       FIELD NAME: MILITARY RETIREMENT
  LOCATION: 0;11                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: .12                       FIELD NAME: UNEMPLOYMENT COMPENSATION
  LOCATION: 0;12                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: .13                       FIELD NAME: OTHER RETIREMENT
  LOCATION: 0;13                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: .14                       FIELD NAME: TOTAL INCOME FROM EMPLOYMENT
  LOCATION: 0;15                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: .15
  FIELD NAME: INTEREST, DIVIDEND, OR ANNUITY
  LOCATION: 0;15                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: .16                       FIELD NAME: WORKERS COMP. OR BLACK LUNG
  LOCATION: 0;16                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: .17                       FIELD NAME: ALL OTHER INCOME
  LOCATION: 0;17                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: .18                       FIELD NAME: COPIED DATA
  LOCATION: 0;18                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is used to determine if the income data was
 copied from the previous income year.  
 GLOBAL DESCRIPTION:   All of this income information is collected when the IVM
 Center verifies a Means Test.  
GLOBAL REFERENCE: DGMT(408.21,D0,1)
FIELD NUMBER: 1.01                      FIELD NAME: MEDICAL EXPENSES
  LOCATION: 1;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: 1.02                      FIELD NAME: FUNERAL AND BURIAL EXPENSES
  LOCATION: 1;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: 1.03                      FIELD NAME: EDUCATIONAL EXPENSES
  LOCATION: 1;3                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
 GLOBAL DESCRIPTION:   All of this income information is collected when the IVM
 Center verifies a Means Test.  
GLOBAL REFERENCE: DGMT(408.21,D0,2)
FIELD NUMBER: 2.01
  FIELD NAME: CASH, AMOUNTS IN BANK ACCOUNTS
  LOCATION: 2;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: 2.02                      FIELD NAME: STOCKS AND BONDS
  LOCATION: 2;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: 2.03                      FIELD NAME: REAL PROPERTY
  LOCATION: 2;3                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: 2.04                      FIELD NAME: OTHER PROPERTY OR ASSETS
  LOCATION: 2;4                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
FIELD NUMBER: 2.05                      FIELD NAME: DEBTS
  LOCATION: 2;5                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is normally reported with the income record.  
 GLOBAL DESCRIPTION:   All of this income information is collected when the IVM
 Center verifies a Means Test.  
GLOBAL REFERENCE: DGMT(408.21,D0,'USR')
FIELD NUMBER: 101                       FIELD NAME: ENTERED BY
  LOCATION: USR;1                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the person who entered the income record.  
FIELD NUMBER: 102                       FIELD NAME: ENTERED ON
  LOCATION: USR;2                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the date on which the income record was filed.  
 GENERAL DESCRIPTION:   The IVM package files new Means Tests in the PIMS Means
 Test module.  IVM requests permission to add and update entries in the
 INDIVIDUAL ANNUAL INCOME (#408.21) file, as part of adding a new Means Test.  
 Additionally, permission is requested to delete entries from that file (if the
 IVM Center mistakenly sends a Means Test to a facility).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  ISC: Albany

NUMBER: 972                             IA #: 972
  FILE NUMBER: 408.22                   GLOBAL ROOT: DGMT(408.22,
  DATE CREATED: AUG 22, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA972                         ID: DGMT(408.22,
GLOBAL REFERENCE: DGMT(408.22,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the patient associated with the income relation.  
FIELD NUMBER: .02                       FIELD NAME: INDIVIDUAL ANNUAL INCOME
  LOCATION: 0;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the annual income record in file #408.21
 associated with the income relation.  
FIELD NUMBER: .05                       FIELD NAME: MARRIED LAST CALENDAR YEAR
  LOCATION: 0;5                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field indicates whether the relation was married in
 the year prior to the Means Test.  
FIELD NUMBER: .06                       FIELD NAME: LIVED WITH PATIENT
  LOCATION: 0;6                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field indicates whether the relation lived with the
 patient.  
FIELD NUMBER: .07                       FIELD NAME: AMOUNT CONTRIBUTED TO SPOUSE
  LOCATION: 0;7                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the amount contributed to the spouse by the
 patient, if the patient did not live with the spouse.  
FIELD NUMBER: .08                       FIELD NAME: DEPENDENT CHILDREN
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field indicated whether the patient had any
 dependent children.  
FIELD NUMBER: .09                       FIELD NAME: INCAPABLE OF SELF-SUPPORT
  LOCATION: 0;9                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field indicates that a child is incapable of
 self-support.  
FIELD NUMBER: .1                        FIELD NAME: CONTRIBUTED TO SUPPORT
  LOCATION: 0;10                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field indicates that the patient contributed to a
 child's support.  
FIELD NUMBER: .11                       FIELD NAME: CHILD HAD INCOME
  LOCATION: 0;11                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field indicates that the child had income in the
 year prior to the Means Test.  
FIELD NUMBER: .12                       FIELD NAME: INCOME AVAILABLE TO YOU
  LOCATION: 0;12                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field indicates whether a child's income was
 available for use by the patient.  
FIELD NUMBER: .13                       FIELD NAME: NUMBER OF DEPENDENT CHILDREN
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the number of dependent children of the patient.  
 GLOBAL DESCRIPTION:   This information is added for all income relations
 associated with the veteran's Means Test.  
 GENERAL DESCRIPTION:   The IVM package files new Means Tests in the PIMS Means
 Test module.  IVM requests permission to add and update entries in the INCOME 
 RELATION (#408.22) file, as part of adding a new Means Test.  Additionally,
 permission is requested to delete entries from that file (if the IVM Center
 mistakenly sends a Means Test to a facility).  
  STATUS: Other                         DURATION: Till Otherwise Agreed
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
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 974                             IA #: 974
  DATE CREATED: AUG 23, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  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
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
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Added 7/14/25, effective with IB*2.0*793, to use the
 lookup for the Means test Status name 

NUMBER: 975                             IA #: 975
  FILE NUMBER: 1.5                      GLOBAL ROOT: DIW(1.5,
  DATE CREATED: AUG 29, 1994            CUSTODIAL PACKAGE: 1
  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
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
SUBSCRIBING PACKAGE: LETTERMAN          ISC: Washington/Silver Spring

NUMBER: 977                             IA #: 977
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19,
  DATE CREATED: AUG 29, 1994            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA977
  ID: DIC(19,
 GENERAL DESCRIPTION:   This integration agreement permits IFCAP to remove
 entries from the OPTION file (#19) until the release and availability of KIDS. 
 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IFCAP              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
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
  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
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
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
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
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: 984                             IA #: 984
  FILE NUMBER: 51.2                     GLOBAL ROOT: PS(51.2,
  DATE CREATED: AUG 30, 1994
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            NAME: MED ROUTES
  ID: PS(51.2,
GLOBAL REFERENCE: PS(51.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Pending
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  ISC: Oakland

NUMBER: 985                             IA #: 985
  FILE NUMBER: 53                       GLOBAL ROOT: PS(53,
  DATE CREATED: AUG 30, 1994            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            NAME: RX PATIENT STATUS
  ID: PS(53,
GLOBAL REFERENCE: PS(53,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Pending
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  ISC: Oakland

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
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
  ISC: Birmingham

NUMBER: 987                             IA #: 987
  GLOBAL ROOT: DD(                      DATE CREATED: SEP 26, 1994
  CUSTODIAL PACKAGE: 1                  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:   
 ************************************************************************
 The Library package was decommissioned with LBR*2.5*15.  This ICR was retired
 with the release of the Library patch.  
 ************************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
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
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
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
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: 993                             IA #: 993
  FILE NUMBER: 45                       GLOBAL ROOT: DGPT
  DATE CREATED: SEP 30, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA993-A
  ORIGINAL NUMBER: 993                  ID: DGPT
GLOBAL REFERENCE: DGPT("AFEE",DFN,ADMISSION DATE,DA)
FIELD NUMBER: 4                         FIELD NAME: FEE BASIS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field indicates if the PTF record is a Fee Basis
 record.  
 GLOBAL DESCRIPTION:   check for IEN in file 45 by
 $O(^DGPT("AFEE",DFN,ADMISSION DATE,0)) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 23, 2006
SUBSCRIBING PACKAGE: FEE BASIS          ISC: Albany
 SUBSCRIBING DETAILS:   Fee Basis uses the "AFEE" cross-reference in the PTF
 file to locate a Non-VA PTF record that is created on admission to a Non-VA
 facility.  There are times when the admission is cancelled or entered in error 
 and fee locates the PTF record, assures it is not closed out by checking in
 file 45.84, and deletes the stub record.  

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
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES

NUMBER: 995                             IA #: 995
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: AUG 31, 1994
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA995
  ID: PS(55,
GLOBAL REFERENCE: PS(55,DFN,'P',X,0)
FIELD NUMBER: .01                       FIELD NAME: PRESCRIPTION PROFILE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 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 EMAIL GROUP 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.  
  
 Read only access to the following nodes in the Pharmacy Patient file #55.  
  
 This reference is found in routines LRBLPE1 and LRBLPH.  
  
 ^PS(55,DFN,"P",X,0) 
  
 F X=0:0 S X=$O(^PS(55,DFN,"P",X)) Q:'X  I $D(^(X,0)) S Y=+^(0) 
      I $D(^PSRX(Y,0))...  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

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: STATUS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: TYPE OF IMAGING
  LOCATION: 0;7                         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
  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
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Patch MECH*1.0*1 processes HL7 new-order messages about
 imaging studies performed in the community but not entered through VistA.  In
 order to do this, it needs to invoke Radiology routines and make FileMan calls
 to add entries to the RAD/NUC MED PATIENT File (#70) (for existing VA
 patients), the ORDER File (#100), and the RAD/NUC MED ORDERS File (#75.1). The
 patch then creates an HL7 order-update message that transmits the study's 
 accession number to the sender. ADDED 3/9/2022, effective with MECH*1.0*1 
 Medicom Class 3 product Document Only 

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
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
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: 1                  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
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 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 3/7/23, effective with OR*3*588 for CPRS v32c 

NUMBER: 1002                            IA #: 1002
  FILE NUMBER: 137.45                   GLOBAL ROOT: SRO(137.45,
  DATE CREATED: JUN 20, 2005            CUSTODIAL PACKAGE: SURGERY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA1002
  ID: SRO(137.45,
GLOBAL REFERENCE: SRO(137.45,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The following reference will be made from the QIP3SR*
 routines which, while belonging to the QIP namespace, will be maintained by
 the Surgery developers.  Coordination of release and patches will be through
 the QIP custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

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
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.  

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: 1007                            IA #: 1007
  FILE NUMBER: 50.6                     GLOBAL ROOT: PSNDF(
  DATE CREATED: JUN 20, 2005            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA106-E
  ID: PSNDF(
GLOBAL REFERENCE: PSNDF(D0,0)
FIELD NUMBER: .01                       FIELD NAME: VA GENERIC NAME
  LOCATION: 0;1                         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 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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
  
 The following references will be made from the QIP3POL* and QIP3NUR* routines
 which, while belonging to the QIP namespace, will be maintained by the
 Pharmacy developers.  Coordination of release and patches will be through the
 QIP custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 1008                            IA #: 1008
  FILE NUMBER: 43                       GLOBAL ROOT: DG(43,
  DATE CREATED: JUN 20, 2005            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA104-D
  ID: DG(43,
GLOBAL REFERENCE: DG(43,D0,GL)
FIELD NUMBER: 11                        FIELD NAME: MULTIDIVISION MED CENTER?
  LOCATION: GL;2                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The following reference will be made from the ^QIP1NS
 routine which, while belonging to the QIP namespace, will be maintained by the
 PIMS developers.  Coordination of release and patches will be through the QIP
 custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

NUMBER: 1009                            IA #: 1009
  FILE NUMBER: 409.5                    GLOBAL ROOT: SDV(
  DATE CREATED: SEP 27, 1994            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA110-C
  ID: SDV(
GLOBAL REFERENCE: SDV(D0,0)
FIELD NUMBER: 2                         FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SDV(D0,CS,D1,PR)
FIELD NUMBER: 21                        FIELD NAME: PROCEDURE 1
  LOCATION: PR;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 22                        FIELD NAME: PROCEDURE 2
  LOCATION: PR;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 23                        FIELD NAME: PROCEDURE 3
  LOCATION: PR;3                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 24                        FIELD NAME: PROCEDURE 4
  LOCATION: PR;4                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 25                        FIELD NAME: PROCEDURE 5
  LOCATION: PR;5                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The following references will be made from the ^QIP1*
 routines which, while belonging to the QIP namespace, will be maintained by
 the PIMS developers.  Coordination of release and patches will be through the
 QIP custodial ISC.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany

NUMBER: 1010                            IA #: 1010
  FILE NUMBER: 45.83                    GLOBAL ROOT: DGP(45.83,
  DATE CREATED: SEP 30, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA1010
  ID: DGP(45.83,
 GENERAL DESCRIPTION:   This is associated with 993 and 994 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 23, 2006
SUBSCRIBING PACKAGE: FEE BASIS          ISC: Albany
 SUBSCRIBING DETAILS:   Fee also references ^DGP(45.83, PTF RELEASE file prior
 to deleting a PTF stub record.  

NUMBER: 1011                            IA #: 1011
  DATE CREATED: SEP 30, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: VATRAN
  NAME: DBIA1011                        ID: VATRAN
 GENERAL DESCRIPTION:   Fee will look into changing to the mailman mailgroup
 functionality in a future version.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: called from top'
 COMPONENT DESCRIPTION:   
         ;Pass in  VATNAME=name (.01 field) as in File 407.7 
         ;Returns  VATERR=null if no error 
         ;         VATERR=1 or 2 or 3 can't process (see error messages
 ERR^VATRAN) 
         ;         if VATERR=null, then VAT array is returned as follows: 
         ;         VAT(1),VAT(2),...=Receiving User(s),format: 'receiving
 user"@" domain mail router' 
         ;         VAT("F")=MailMan Message Length - Fixed record 
         ;         VAT("V")=MailMan Message Length - Variable record 
SUBSCRIBING PACKAGE: FEE BASIS          ISC: Albany
 SUBSCRIBING DETAILS:   Fee uses the transmission router file and associated
 VATRAN routine for transmission of records to a remote location.  

NUMBER: 1012                            IA #: 1012
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: JUN 20, 2005            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA110-D
  ID: DPT(
GLOBAL REFERENCE: DPT(D0,S,D1,0)
FIELD NUMBER: 3                         FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Routine QIP1NS will use the following field to
 determine to percentage of no-show visits versus the total number of visits: 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUALITY IMPROVEMENT CHECKLIST
  ISC: Birmingham

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
COMPONENT/ENTRY POINT: DOLRO
 COMPONENT DESCRIPTION:   Save local symbol table.  
SUBSCRIBING PACKAGE: 1                  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
SUBSCRIBING PACKAGE: 1                  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
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
  DATE ACTIVATED: MAR 15, 2007

NUMBER: 1016                            IA #: 1016
  DATE CREATED: OCT 17, 1994            CUSTODIAL PACKAGE: 1
  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
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: 1
  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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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: 1018                            IA #: 1018
  FILE NUMBER: 101                      GLOBAL ROOT: ORD(
  DATE CREATED: JUN 10, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: UPDATE FILE 101 & 100.99
  ID: ORD(
GLOBAL REFERENCE: ORD(101
FIELD NUMBER: ALL                       ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   KIDS will update all the fields in File 101. Field 5,
 pointer to file 200, will be deleted before installing.  The following pointer
 fields will be resolved: 
   6    FILE LINK (V), [5;1] 
  10    ITEM (M), [10;0] 
        .01 ITEM (P101), [0;1] 
          4 MODIFYING ACTION (P101), [0;4] 
  12    PACKAGE (P9.4), [0,12] 
  100.3 ACCESS (M), [3;0] 
        .01 ACCESS (P19.1), [0;1] 
GLOBAL REFERENCE: ORD(100.99,1,5,
FIELD NUMBER: 5                         FIELD NAME: PACKAGE PARAMETERS
  LOCATION: 5;0                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   KIDS will update this multiple and all fields under the
 multiple.  Field .01 (Pointer to 9.4) and Field 1.1 (pointer to 100.98) will 
 be resolved.  
 GENERAL DESCRIPTION:   Kernel Installation and Distributions System needs to
 update the Protocol file, 101, and the Package Parameter multiple in the Order 
 Parameter file, 100.99.  KIDS needs to extract data from these files during
 Package transportations.  KIDS also needs to update these files during package
 installation.  
  STATUS: Retired
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
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
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
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: Routine                         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 its 
   components to the VAQ - DATA SEGMENT file and will use the entry point 
   $$UPDSEG^VAQUTL50() to update the VAQ - DATA SEGMENT file entries when 
   the corresponding component is modified.  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).  
  
   Revision History: 
   06/01/2023 - Effective with VAQ*1.5*46 and GMTS*2.7*144: 
                Added new component $$UPDSEG 
                Corrected component $$ADDSEG to reflect how released code 
                works 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$FIRSTUP(TEXT)
 COMPONENT DESCRIPTION:   This component will convert a string so that the
 first letter of every word is uppercase and the remaining characters in the
 word are lowercase.  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   String to convert 
VARIABLES: $$FIRSTUP                    TYPE: Output
 VARIABLES DESCRIPTION:   Passed-in string with the first letter of every word
 in uppercase and the remaining letters in lowercase.  
COMPONENT/ENTRY POINT: $$ADDSEG(HSPTR,MAXTIME,MAXOCCUR)
 COMPONENT DESCRIPTION:   This component will add a new data segment given a
 Health Summary component.  
   
   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.  
VARIABLES: HSPTR                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to HEALTH SUMMARY COMPONENT file (#142.1) 
VARIABLES: MAXTIME                      TYPE: Input
 VARIABLES DESCRIPTION:   Max time limit allowed for auto processing 
VARIABLES: MAXOCCUR                     TYPE: Input
 VARIABLES DESCRIPTION:   Max occurrence limit allowed for auto processing 
VARIABLES: $$ADDSEG                     TYPE: Output
 VARIABLES DESCRIPTION:   0 - VAQ - DATA SEGMENT file (#394.71) entry was 
     successfully added 
  
 -1^Error_Text - Entry not created 
COMPONENT/ENTRY POINT: $$UPDSEG(VAQHSPTR,VAQMAXTIME,VAQMAXOCCUR)
 COMPONENT DESCRIPTION:   This component will update an existing data segment
 to match the Health Summary component passed in, such as a change in name.  
  
   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.  
VARIABLES: VAQHSPTR                     TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the HEALTH SUMMARY COMPONENT file (#142.1) 
VARIABLES: VAQMAXTIME                   TYPE: Input
 VARIABLES DESCRIPTION:   Max time limit allowed for auto processing 
VARIABLES: VAQMAXOCCUR                  TYPE: Input
 VARIABLES DESCRIPTION:   Max occurrence limit allowed for auto processing 
VARIABLES: $$UPDSEG                     TYPE: Output
 VARIABLES DESCRIPTION:   0 - VAQ - DATA SEGMENT file (#394.71) entry was 
     successfully updated 
  
 -1^Error_Text - Entry not updated 
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
  DATE ACTIVATED: JUN 09, 2023

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
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
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 10/19/23, effective with patch PX*1.0*240 to
 document ICR in legacy code.  

NUMBER: 1025                            IA #: 1025
  FILE NUMBER: 409.5                    GLOBAL ROOT: SDV(,
  DATE CREATED: OCT 17, 1994            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: Health Summary access to 409.5
  ID: SDV(,
GLOBAL REFERENCE: SDV(D0,CS,D1,0)
FIELD NUMBER: 3                         FIELD NAME: ASSOCIATED CLINIC
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: APPOINTMENT TYPE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Unscheduled clinic stop codes and Ambulatory Procedures
 stored here.  
 GENERAL DESCRIPTION:   Health Summary accesses file 409.5, Scheduling Visits
 file to display the Associated Clinic and Appointment Type in one of its
 components, Clinic Past Visits (CVP).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 1026                            IA #: 1026
  FILE NUMBER: 409.1                    GLOBAL ROOT: SD(409.1,
  DATE CREATED: OCT 17, 1994            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File
  NAME: Health Summary access to file 409.1
  ID: SD(409.1,
GLOBAL REFERENCE: SD(409.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Health Summary accesses file 409.1, Appointment Type
 File, to display the name of the Appointment Type in one of its components, 
 Clinic Past Visits (CVP).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

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
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
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
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
  GOOD ONLY FOR VERSION: 21
SUBSCRIBING PACKAGE: 1                  ISC: Oakland

NUMBER: 1035                            IA #: 1035
  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                            NAME: TRANSFER TEXT FROM MAIL MESSAGE
  ID: XMB(3.9)
GLOBAL REFERENCE: XMB(3.9,D0,2,
 GLOBAL DESCRIPTION:   In ^DIWE3, Fileman directly accesses the TEXT from the
 message in order to transfer it to another message.  
GLOBAL REFERENCE: XMB(3.9,D0,3,
 GLOBAL DESCRIPTION:   In ^DIWE3, FileMan directly accesses the RESPOSE from
 the message in order to transfer it to another message.  
 GENERAL DESCRIPTION:   VA FileMan looks directly at the MESSAGE file to
 transfer text from one mail message to another, using the UTILITY, TRANSFER
 TEXT option in the line editor.  
  
 FM is requesting the DBIA until mailman provides the interface for
 transferring message text.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: 1                  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
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
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
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: 1041                            IA #: 1041
  DATE CREATED: OCT 25, 1994            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMTSLTR
  NAME: DBIA1041                        ID: GMTSLTR
 GENERAL DESCRIPTION:   Progress Notes rtn ^GMRPNR5 (exported w/GMRP*2.5*31) is
 using Health Summary rtn ^GMTSLTR to delimit locations selected using the
 GMRPN PRINT BATCH option.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 1042                            IA #: 1042
  DATE CREATED: OCT 25, 1994            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Other                           NAME: USE OF XMSUB IN FM SCREEN EDITOR
 GENERAL DESCRIPTION:   The Screen Editor in VA FileMan checks for the
 existence of the variable XMSUB.  If XMSUB exists, the Screen Editor displays
 the first 30 characters of that variable between "greater than" and "less
 than" symbols (< and >) on the top ruler line of the screen.  When an original
 MailMan message is edited, XMSUB contains the subject of the message; when a 
 response is edited, XMSUB contains an "R" concatenated with the number of the
 original message.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LOCAL VARIABLE XMSUB
VARIABLES: XMSUB                        TYPE: Used
 VARIABLES DESCRIPTION:   Local variable XMSUB is used to display subject of a
 mail message, when editing a mail message using the VA FileMan screen editor.  
SUBSCRIBING PACKAGE: 1                  ISC: Oakland

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
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
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
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
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.  

NUMBER: 1047                            IA #: 1047
  FILE NUMBER: 121                      GLOBAL ROOT: GMR(121,
  DATE CREATED: OCT 28, 1994            CUSTODIAL PACKAGE: PROGRESS NOTES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File
  NAME: MENTAL HEALTH - PROGRESS NOTE #1047
  ID: GMR(121,
GLOBAL REFERENCE: GMR(121,D0,30)
FIELD NUMBER: 30                        FIELD NAME: DXLS
  LOCATION: 30;1                        ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   Mental Health V. 5.01 requests to convert data stored
 in the Generic Progress Notes file (#121), in the field DXLS (#30).  Only data
 stored in this field that points to the DSM-III-R (#627.5) file will be
 modified to point to the new DSM (#627.7) file.  
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.01
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas

NUMBER: 1048                            IA #: 1048
  DATE CREATED: NOV 01, 1994            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         ROUTINE: XMGAPI1
  NAME: MAILMAN: Initialize Mailman Environment
  ID: XMGAPI1
 GENERAL DESCRIPTION:   NOTICE!  NOTICE!  NOTICE! 
  
 XMGAPI1 is being RETIRED as a supported reference.  Use INIT^XMVVITAE instead. 
  
 This routine contains two application programmer entry points:  
  
     $$EN^XMGAPI1(DUZ,.HEADERS) which initializes mailman to access DUZ's mail
 and is the preferred technique for programs to use.  OPTIONS should continue
 to invoke EN^XM.  
  
     $$READ^XMGAPI1() which returns the "next" line in the body of a message   
                      -- typically for a server 
  STATUS: Retired                       EXPIRATION DATE: NOV 25, 2000
COMPONENT/ENTRY POINT: $$EN
 COMPONENT DESCRIPTION:   Purpose of $$EN^XMGAPI1: to initialize the MailMan
 environment, e.g. set up all necessary variables and clean up the environment
 for the user.  
  
 Note: It is not necessary to call the EN^XM entry point or the $$EN^XMAGAPI1 
 function when calling entry points to send or receive messages.  They are only
 used when setting up one of the MailMan options as a separate option in the
 entry action of the menu or option, and is for "Interactive" processes only.
 They should also NOT be used to initialize MailMan variables when creating or
 sending messages or bulletins.  Use the XMA2 entry points for these functions. 
  
  
 Usage:         =$$EN^XMGAPI1(DUZ,.HEADERS)   
  
 Parameters:    DUZ      Pointer to Person File record for recipient of 
                                 message 
               .HEADERS  Array into which you would like the MailMan header 
                                 for that user returned.  Inputs:        None
 (!) 
              
 Returns:  # - meaning [Explanation]     [Both # and meaning are returned.] 
                           Hint: EN=+$$EN D $S(EN=1:....). ] 
  
        1 - No DUZ           [No pointer to the Mail box] 
  
        2 - No Access Code   [In New Person record -- hence deny access] 
  
        3 - Mail box Maintenance Underway       
            [The Message file is locked and you can't send or reply] 
  
        4 - No Mail box   [There is no Mail box for the user specified pointer] 
  
        5 - Priority mail [There is Priority mail for this person] 
  
        6 - Message in Buffer [There was a partially created 
            message from this user detected] 
  
       7 - No Introduction [Site Parameters call for users to have 
           introductions and this user has none] 
  
       8 - No Person  [No entry for the Mail box pointer specified 
           in the New Person file] 
  
 Variables Initialized 
  
        XMDISPI Tells MailMan how to display different attributes for this user 
  
        XMDUN   The human readable name of the user     
  
 ?      XMK     Mail box pointer 
  
 ?      XMKN    Mail basket name 
  
 ?      XMLOCK  Controls 
  
        XMNSEND Indicator that no "writes" (replies or new 
                        messages) can be made for this session 
  
 ?      XMY     Detailed Recipient chain 
  
 ?      XMY0    Summary Recipient chain 
  
 ?      XMZ     Message number 
  
  
  
 Description: 
  
 The function $$EN^XMGAPI1(DUZ,.HEADERS) initializes mailman to access person
 DUZ's mail.  On exit, "HEADERS" contains a list of lines which hold the mail
 system header for that user.  The number of lines returned depends on the
 user.  
  
  
 Examples: 
  
 >W $$EN^XMGAPI1(DUZ,.WHAT) 
  
 >ZW WHAT WHAT=2 WHAT(1)=VA MailMan 7.2T1 service for EMAIL GROUP WHAT(2)=You
 last used MailMan: 01 Nov 94 11:09 
  
  
 WHAT(3,4,...) could contain any number of lines, e.g. number of postmaster NEW
 messages for postmaster surrogates.  
  
 ZW  (except for WHAT and XUP defined variables) 
  
 XMDISPI=XA^I XMDUN=LAST,FIRST XMDUZ=4 XMK=0 XMKN= XMLOCK= XMZ=0 XQXFLG=^^XUP 
COMPONENT/ENTRY POINT: $$READ
 COMPONENT DESCRIPTION:   Usage:       S X=$$READ^XMGAPI1() 
  
 Parameters:  None 
  
 Inputs:      XMZ    Message Number 
              XMPOS  Line Number 
  
 Outputs:     $$READ^XMGAPI1()   The "next" line (line XMPOS) in message XMZ 
              XMPOS              The number of the line returned 
              XMER   0 if function returns a line; -1 if no more line 
                     numbers greater than XMPOS (which will normally be the 
                     number of the last line and function returns "") 
                              
  
 Description: 
  
 This function returns the "next" line after line XMPOS in the body of message
 XMZ (and sets XMER=0) if there is such a line.  Otherwise, XMER is -1.  If
 XMPOS is undefined or less than .99, it is set to .99. (REC^XMS3 does the real
 work.) 

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
  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,
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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
  ISC: Birmingham
  DATE ACTIVATED: SEP 09, 2010

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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 1052                            IA #: 1052
  DATE CREATED: NOV 07, 1994            CUSTODIAL PACKAGE: 1
  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: 1
  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: 1
  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: 1
  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: 1
  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: 1
  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: 1
  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
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: 1
  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 
  STATUS: Active                        DURATION: Next Version
  EXPIRATION DATE: JUN 01, 1995         GOOD ONLY FOR VERSION: 5.3
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 1060                            IA #: 1060
  DATE CREATED: NOV 09, 1994            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: PSOLSET
  NAME: DBIA1030-B                      ORIGINAL NUMBER: 1030
  ID: PSOLSET
 GENERAL DESCRIPTION:   This entry point can be used to get the site number of
 the site running the Outpatient Pharmacy package.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PSOLSET
VARIABLES: PSOPAR                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the site parameters of the Outpatient
 Pharmacy package as defined at the site.  

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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added OE/RR as subscriber to reflect usage of this ICR
 effective prior to CPRS v31b.  Discovered during ICR review.  

NUMBER: 1062                            IA #: 1062
  DATE CREATED: JAN 12, 1995            CUSTODIAL PACKAGE: 1
  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
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: 1063                            IA #: 1063
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19
  DATE CREATED: NOV 16, 1994            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA1063-A
  ORIGINAL NUMBER: 1063                 ID: DIC(19
GLOBAL REFERENCE: DIC(19,'B'
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DIC(19,D0,200)
FIELD NUMBER: 200                       FIELD NAME: QUEUED TO RUN AT WHAT TIME
  LOCATION: 200;1                       ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
      The Outpatient routines PSODISP and PSORESK need to make sure that the
 Drug Acct. background job, PSA IV ALL LOCATIONS is scheduled to run before
 updating ^XTMP("PSA".  This agreement supports the look-up to the OPTION file
 for a Kernel version 7.1 environment.  
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: OP6.0/K7.1
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

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
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
  ISC: Birmingham

NUMBER: 1065                            IA #: 1065
  FILE NUMBER: 58.8                     GLOBAL ROOT: PSD
  DATE CREATED: NOV 17, 1994            CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: D&PPM
  ID: PSD
GLOBAL REFERENCE: PSD(58.8,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DRUG
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: BREAKDOWN UNIT
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: PACKAGE SIZE
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Pharmacy Benefits Management package will extract
 data on a monthly basis from the "Drug Accountability Stats" file number 58.8. 
 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham

NUMBER: 1066                            IA #: 1066
  FILE NUMBER: 58.81                    GLOBAL ROOT: PSD
  DATE CREATED: NOV 17, 1994            CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: D&PPM
  ID: PSD
GLOBAL REFERENCE: PSD(58.81,D0,0)
FIELD NUMBER: 5                         FIELD NAME: QUANTITY
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 17                        FIELD NAME: NAOU
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSD(58.81,D0,4)
FIELD NUMBER: 50                        FIELD NAME: NEW QUANTITY
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Drug & Pharmeacuticl Product Management (D&PPM)
 package will extract data on a monthly basis from the "Drug Accountability
 Transactions file" number 58.81.  The primary sorting process through this
 file is on the "AF" cross- reference of the DATE/TIME field.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  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
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham

NUMBER: 1068                            IA #: 1068
  FILE NUMBER: 627.7                    GLOBAL ROOT: YSD
  DATE CREATED: NOV 21, 1994            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA1068                        ID: YSD
 GENERAL DESCRIPTION:   Progress Notes has a variable pointer, DXLS, file 121,
 field 30 that is as follows: 
        FILE    ORDER   PREFIX  LAYGO   MESSAGE 
         80      1      I       n       ICD9 Code 
        627.5    2      D       n       DSM-III-R Code This is for use with
 Mental Health v4.18 and Mental Health v5.0.  
  
 With the release of Mental Heath v5.01 this will be changed to: 
        FILE    ORDER   PREFIX  LAYGO   MESSAGE 
         80      1      I       n       ICD9 Code 
        627.7    2      D       n       DSM-IV 
  
 PNs should have had an agreement to use this file.  Prior to the release of
 Progress Notes v2.5 this data was a part of the Mental Health progress notes
 global 606.  The agreement was somehow overlooked when the data was converted
 to ^GMR(121.  
  
 GMRP*2.5*26 will make Progress Notes fully compatible with versions 4.18, 5.0
 and 5.01 of Mental Health.  
  
 Progress Notes rtns ^GMRPNP3 and ^GMRPNP4 have been modified to check for the
 existence of all 3 possible globals and accomplish the prting accordingly.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

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
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
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: 1071                            IA #: 1071
  DATE CREATED: DEC 09, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: DGPMSTAT
  NAME: DGPMSTAT                        ID: DGPMSTAT
 GENERAL DESCRIPTION:   Obtain Inpatient Status.  
  STATUS: Pending
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Returns corresponding admission and movement data of
 a patient as of a specified date.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IFN 
VARIABLES: DGT                          TYPE: Input
 VARIABLES DESCRIPTION:   Date to check if patient was inpatient.  
VARIABLES: DGA1                         TYPE: Output
 VARIABLES DESCRIPTION:   Corresponding admission movement IFN of ^DGPM.  
VARIABLES: DG1                          TYPE: Output
 VARIABLES DESCRIPTION:   ward^room-bed^mvt type(for xfrs only) 
VARIABLES: DGXFR0                       TYPE: Output
 VARIABLES DESCRIPTION:   0th of last xfr movement for admission.  

NUMBER: 1072                            IA #: 1072
  DATE CREATED: DEC 09, 1994
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: VACPT
  NAME: VACPT                           ID: VACPT
 GENERAL DESCRIPTION:   Display CPT Copyright Information.  
  STATUS: Pending

NUMBER: 1073                            IA #: 1073
  DATE CREATED: DEC 09, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: VADATE
  NAME: VADATE                          ID: VADATE
 GENERAL DESCRIPTION:   Generic Date Routine.  This was designed many years ago
 (1988-1989) for use with the MAS package.  Since this time, the ToolKit
 package has released function calls in XLFDT.  It is our feeling at this point
 that those tools should be used for new code.  This integration agreement is 
 entered for legacy code only.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: VADATE
 COMPONENT DESCRIPTION:   Call routine from top.  D ^VADATE 
  
 If nothing is passed in, NOW will be returned in internal and external 
 formats:  VADATE("I") and VADATE("E").  
VARIABLES: VADAT                        TYPE: Input
 VARIABLES DESCRIPTION:   The IA options won't allow entry of the following
 subscripted input variables.  All variables defined below are optional: 
  
 VADAT("F") - use this to have the date returned in a format other than FM.  
              set to 1 for MM-DD-YY format 
              set to 2 for military or DD-MMM-YY format 
              if defined and set to anything other than 1 or 2, it will 
                 assume VA fileman format.  VADAT("D") - If VADAT("F") is
 defined, this variable may be passed to 
              contain a delimiter if one other than the dash ("-") is 
              desired.  Pass VADAT("D")="/" to receive MM/DD/YY, for 
              example.  VADAT("T") - Define if you do NOT want time returned
 regardless of date 
              passed.  VADAT("W") - If a time other than NOW is desired, pass
 this as any 
              date/time (or date) in VA fileman format VADAT("H") - If you only
 want to see portions of the date, you may pass 
              this variable.  '1' will denote day, '2' - month, and '3' - 
              year.  So to see just month and year, pass VADAT("H") as '23' 
              or '32'.  Note:  If VADAT("T") is not defined and a time 
              exists, it will also be returned.  VADAT("S") - If defined,
 seconds will be returned.  If not defined, no 
              seconds will be returned.  VADAT("J") - Pass this as a numeric
 value to justify the external 
              date/time returned.  If the date/time is longer than the 
              value passed, the entire date/time will be returned.  VADAT("S")
 - pass this if you WANT to see seconds.  
VARIABLES: VADATE                       TYPE: Output
 VARIABLES DESCRIPTION:   The IA options don't allow entry of subscripted
 input/output variables.  The following are always returned from this call: 
  
 VADATE("I") - the internal format of the date VADATE("E") - the external
 format of the date 
COMPONENT/ENTRY POINT: KVAR
 COMPONENT DESCRIPTION:   Kills VADAT and VADATE variables.  

NUMBER: 1074                            IA #: 1074
  DATE CREATED: DEC 09, 1994
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: VATRAN
  NAME: VATRAN                          ID: VATRAN
 GENERAL DESCRIPTION:   Establish VADATS Transmission Variables 
  STATUS: Pending
COMPONENT/ENTRY POINT: VATRAN
VARIABLES: VATNAME                      TYPE: Input
 VARIABLES DESCRIPTION:   Name (.01 field) of file 407.7 
VARIABLES: VATERR                       TYPE: Output
 VARIABLES DESCRIPTION:   null if no error. 1,2 or 3 representing an error
 code.  
VARIABLES: VAT()                        TYPE: Output
 VARIABLES DESCRIPTION:   Returned if no errors.  VAT(1), VAT(2),... Receiving
 User(s); format: User @ Domain VAT("F")=mailman message length - fixed record 
 VAT("V")=mailman message length - variable record.  

NUMBER: 1075                            IA #: 1075
  DATE CREATED: DEC 09, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: VATREDIT
  NAME: VATREDIT                        ID: VATREDIT
 GENERAL DESCRIPTION:   Enter/Edit Transmission Routers File.  
  STATUS: Pending

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
 GENERAL DESCRIPTION:   Quick Lookup for Patient Data.  
  STATUS: Active
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: DEC 10, 1994

NUMBER: 1077                            IA #: 1077
  DATE CREATED: DEC 09, 1994
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: VAUTOMA
  NAME: VAUTOMA                         ID: VAUTOMA
 GENERAL DESCRIPTION:   Generic One, Many, All Routine.  
  STATUS: Pending

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
  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: 1079                            IA #: 1079
  GLOBAL ROOT: PSRX(                    DATE CREATED: DEC 02, 2005
  CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA1079-A
  ORIGINAL NUMBER: 1079                 ID: PSRX(
GLOBAL REFERENCE: PSRX(RXIFN,0)
FIELD NUMBER: .01                       FIELD NAME: RX NUMBER
  ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ISSUE DATE
  ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PHYSICIAN
  ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: DRUG
  ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: QUANTITY
  ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SIGNATURE
  ACCESS: Read w/Fileman
FIELD NUMBER: 101                       FIELD NAME: LAST FILL DATE
  ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Direct read access to PS global.  Used to extract
 pharmacy outpatient RX data.  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  ISC: Albany

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
SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  ISC: Albany

NUMBER: 1081                            IA #: 1081
  DATE CREATED: DEC 13, 1994            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSOBBC
  NAME: DBIA1079-C                      ORIGINAL NUMBER: 1079
  ID: PSOBBC
 GENERAL DESCRIPTION:   This routine needs to maintain the calls to Pharmacy
 Prescription Practices (PPP).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$PDA~PPPPDA1(X1)
 COMPONENT DESCRIPTION:   Pharmacy Data Alert 
VARIABLES: 0                            TYPE: Output
 VARIABLES DESCRIPTION:   normal termination 
VARIABLES: 9001                         TYPE: Output
 VARIABLES DESCRIPTION:   returns -9001 when there is a parameter error 
VARIABLES: 9003                         TYPE: Output
 VARIABLES DESCRIPTION:   returns -9003 when an invalid DFN for patient is
 passed 
VARIABLES:  
VARIABLES: X1                           TYPE: Input
 VARIABLES DESCRIPTION:   patient DFN from Patient file 
SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  ISC: Albany

NUMBER: 1082                            IA #: 1082
  DATE CREATED: DEC 13, 1994            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSONUM
  NAME: DBIA1079-D                      ORIGINAL NUMBER: 1079
  ID: PSONUM
 GENERAL DESCRIPTION:   This routine needs to maintain the calls to Pharmacy
 Prescription Practices (PPP).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$PDA~PPPPDA1(X1)
 COMPONENT DESCRIPTION:   Pharmacy Data Alert 
VARIABLES: 0                            TYPE: Output
 VARIABLES DESCRIPTION:   normal termination 
VARIABLES: 9001                         TYPE: Output
 VARIABLES DESCRIPTION:   returns -9001 when there is a parameter error 
VARIABLES: 9003                         TYPE: Output
 VARIABLES DESCRIPTION:   returns -9003 when an invalid DFN for patient is
 passed 
VARIABLES: X1                           TYPE: Input
 VARIABLES DESCRIPTION:   patient DFN from Patient file 
SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  ISC: Albany

NUMBER: 1083                            IA #: 1083
  DATE CREATED: DEC 13, 1994
  CUSTODIAL PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PPPGET7                      NAME: DBIA1079-E
  ORIGINAL NUMBER: 1079                 ID: PPPGET7
 GENERAL DESCRIPTION:   This routine needs to maintain the calls to Pharmacy
 Prescription Practices (PPP).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$GETVIS~PPPGET7(DFN,TARRY)
 COMPONENT DESCRIPTION:   Extract Utility 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   patient DFN from patient file 
VARIABLES: $$GETVIS                     TYPE: Output
 VARIABLES DESCRIPTION:   0 - no pharmacy data available from other facilities 
 1 - pharmacy data available from other facilities 
VARIABLES: TARRY                        TYPE: Output
 VARIABLES DESCRIPTION:   array looks like this: 
  
 @TARRY@(STATION NAME, 0) = DATA AVAILABLE^PDX DATA FILE IFN^STATION NUMBER 
 @TARRY@(STATION NAME, 1) = PATIENT NAME^DATE OF BIRTH @TARRY@(STATION NAME, 2)
 = STATION NAME^LAST PDX DATE^LAST PDX STATUS 
                         ^PHARMACY DATA AVAILABLE 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 1084                            IA #: 1084
  DATE CREATED: DEC 13, 1994            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSORX
  NAME: DBIA1079-F                      ORIGINAL NUMBER: 1079
  ID: PSORX
 GENERAL DESCRIPTION:   This routine needs to maintain the calls to Pharmacy
 Prescription Practices (PPP).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$PDA~PPPPDA1(X1)
 COMPONENT DESCRIPTION:   patient DFN from Patient file 
VARIABLES: X1                           TYPE: Input
 VARIABLES DESCRIPTION:   patient DFN from Patient file 
VARIABLES: 0                            TYPE: Output
 VARIABLES DESCRIPTION:   normal termination 
VARIABLES: 9001                         TYPE: Output
 VARIABLES DESCRIPTION:   returns -9001 when there is a parameter error 
VARIABLES: 9003                         TYPE: Output
 VARIABLES DESCRIPTION:   returns -9003 when an invalid DFN for patient is
 passed 
SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  ISC: Albany

NUMBER: 1085                            IA #: 1085
  DATE CREATED: DEC 13, 1994
  CUSTODIAL PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PPPPRT9                      NAME: DBIA1079-G
  ORIGINAL NUMBER: 1079                 ID: PPPPRT9
 GENERAL DESCRIPTION:   This routine needs to maintain the calls to Pharmacy
 Prescription Practices (PPP).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  GOOD ONLY FOR VERSION: 1.0
COMPONENT/ENTRY POINT: PLP(DFN)
 COMPONENT DESCRIPTION:   Print Label Profile 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN from patient file.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 1086                            IA #: 1086
  DATE CREATED: DEC 13, 1994            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Other                           ROUTINE: PSOSD
  NAME: DBIA1079-H                      ORIGINAL NUMBER: 1079
  ID: PSOSD
 GENERAL DESCRIPTION:   The following PSO routines will be distributed as part 
 of the PPP v1.0 release.  The routines will be sent in the PPP namespace and
 then translated back to their PSO namespace as part of the PPP post init.  At
 that point PSO becomes custodian of the routines and will be responsible for
 any reported problems.  PSO will be responsible for entering an informational
 patch describing the destribution of the PSO routines by PPP.  The routines
 are: 
  
        1.  PSOBBC              PPPSE01 
        2.  PSONUM              PPPSE02 
        3.  PSOPRF              PPPSE03 
        4.  PSORX               PPPSE04 
        5.  PSOSD               PPPSE05 
  
  
 The patch number is PSO*6*105 
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 1.0
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.  
  STATUS: Active                        DURATION: Next Version
  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
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
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
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Washington/Silver Spring

NUMBER: 1091                            IA #: 1091
  DATE CREATED: JAN 05, 1995            CUSTODIAL PACKAGE: 1
  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
  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
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
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
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
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
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.  

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: 1101                            IA #: 1101
  GLOBAL ROOT: DPT(                     DATE CREATED: APR 03, 2003
  CUSTODIAL PACKAGE: SCHEDULING         CUSTODIAL ISC: Albany
  USAGE: Controlled Subscription        TYPE: File
  NAME: Patient File Scheduling Node    ID: DPT(
GLOBAL REFERENCE: DPT(D0,S)
FIELD NUMBER: .01                       FIELD NAME: CLINIC
  LOCATION: 1                           ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to the Hospital Location File.  
  
FIELD NUMBER: 3                         FIELD NAME: STATUS
  LOCATION: 2                           ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Set of codes indicating appointment status.  
  
FIELD NUMBER: 12
  FIELD NAME: AUTO-REBOOKED APPT. DATE/TIME
  LOCATION: 10                          ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   If the appointment was canceled and auto-rebooked, this
 field contains the appointment date/time of the new appointment.  
  
FIELD NUMBER: 19                        FIELD NAME: DATA ENTRY CLERK
  LOCATION: 18                          ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to the New Person file.  
  
FIELD NUMBER: 20                        FIELD NAME: DATE APPT. MADE
  LOCATION: 19                          ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the date the appointment was entered
 into Scheduling.  
  
 GLOBAL DESCRIPTION:   
  
 This is the Scheduling Node (multiple) on the patient's record in the Patient
 file.  
  
 GENERAL DESCRIPTION:   
  
 AMIE references the described fields on the 'S' Node of the Patient file to
 implement C&P appointment linking for release with V2.7.  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas

NUMBER: 1102                            IA #: 1102
  GLOBAL ROOT: SC(D0,S,                 DATE CREATED: APR 03, 2003
  CUSTODIAL PACKAGE: SCHEDULING         CUSTODIAL ISC: Albany
  USAGE: Private                        TYPE: File
  NAME: Hospital Location File Scheduling Node
  ID: SC(D0,S,
GLOBAL REFERENCE: SC(D0,S,D1,1,D2,0)
FIELD NUMBER: 8                         FIELD NAME: DATE APPOINTMENT MADE
  LOCATION: 7                           ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the date the appointment was entered
 into Scheduling.  
  
FIELD NUMBER: 7                         FIELD NAME: DATA ENTRY CLERK
  LOCATION: 6                           ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to the New Person file.  
  
 GLOBAL DESCRIPTION:   
  
 This is the Scheduling Node (multiple) on the hospital location's record in
 the Hospital Location file.  
  
 GENERAL DESCRIPTION:   
  
 AMIE references the described fields on the 'S' Node of the Hospital Location
 file to implement C&P appointment linking for release with V2.7. 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany

NUMBER: 1103                            IA #: 1103
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDAM1
  NAME: AMIE use of SDAM1               ID: SDAM1
 GENERAL DESCRIPTION:   
  
 AMIE calls $$STATUS^SDAM1 to retrieve for output the status of a given 
 appointment.  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$STATUS
 COMPONENT DESCRIPTION:   
  
  
 STATUS(DFN,SDT,SDCL,SDATA,SDDA) 
  
 This is a Function entry point with the following parameters passed: 
  
   input:        DFN := ifn of pat.  
                 SDT := appt d/t 
                SDCL := ifn of clinic 
               SDATA := 0th node of pat appt entry 
                SDDA := ifn for ^SC(clinic,"S",date,1,ifn) {optional} 
  output: [returned] := appt status ifn ^ status name ^ print status ^ 
                        check in d/t ^ check out d/t ^ adm mvt ifn 
  
  
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany

NUMBER: 1105                            IA #: 1105
  FILE NUMBER: 423.5                    GLOBAL ROOT: PRCF(423.5,
  DATE CREATED: JAN 06, 1995            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIA1105
  ID: PRCF(423.5,
 GENERAL DESCRIPTION:   This file contains a listing of the transactions that
 can be handled by the PRCOISM IFCAP server. This file also contains the
 mailgroup that will receive any transaction processing error message and the
 entry point (TAG^ROUTINE) for each different transaction processing. It
 contains only four fields: TRANSACTION CODE, MAILGROUP, TAG and ROUTINE.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IFCAP              ISC: Washington/Silver Spring

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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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=<null>. 
 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
COMPONENT/ENTRY POINT: CONTROL
 COMPONENT DESCRIPTION:   This entry point is provided for IFCAP to build the
 FMS control segments CTL, BAT, DOC, and <tc>1 where <tc> 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 <tc>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
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 7/21/22, effective with DSIY*1.5*4 

NUMBER: 1109                            IA #: 1109
  FILE NUMBER: 409.5                    GLOBAL ROOT: SDV(
  DATE CREATED: JAN 26, 1995            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: Use of Cross References
  ID: SDV(
GLOBAL REFERENCE: SDV('ADT'
 GENERAL DESCRIPTION:   Read access to the following cross references is being
 requested.  These cross references will be used to count the clininc stops and
 the stop codes for a particular patient.  The AMIE code will $O through these 
 structures.  
   ^SDV("ADT" 
   ^SDV("C" 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany

NUMBER: 1110                            IA #: 1110
  FILE NUMBER: 15                       GLOBAL ROOT: DD(15
  DATE CREATED: JUN 10, 2003            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: 1110
  ID: DD(15
GLOBAL REFERENCE: DD(15,0,'IX','AMFI',15,999999901)
GLOBAL REFERENCE: DD(15,0,'IX','APOT',15,.04)
GLOBAL REFERENCE: DD(15,0,'IX','AZ1',15,.05)
GLOBAL REFERENCE: DD(15.01101,0,'IX','ARDY',15.01101,.02)
 GENERAL DESCRIPTION:   Kernel Toolkit needs this agreement with FileMan to be
 able to clean up some "IX" nodes in the data dictionary of the DUPLICATE
 RECORD (#15) file.  The "IX" nodes which are killed during the post-init
 contain the names of the X-refs. which do not exist.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TOOLKIT            ISC: Oakland

NUMBER: 1111                            IA #: 1111
  GLOBAL ROOT: DD(                      DATE CREATED: JAN 10, 1995
  CUSTODIAL PACKAGE: 1                  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
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(
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:   
  
GLOBAL REFERENCE: DG(391,'B'
 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 
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 10/16/23, effective with patch PX*1.0*235 to
 document missed ICR usage in legacy code.  

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
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
COMPONENT/ENTRY POINT: REBUILD
 COMPONENT DESCRIPTION:   This entry point is provided for IFCAP to rebuild the
 FMS control segments CTL, BAT, DOC, and <tc>1 where <tc> 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 <tc>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
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
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 7/21/22, effective with DSIY*1.5*4 

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
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
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: 1119                            IA #: 1119
  FILE NUMBER: 70                       GLOBAL ROOT: RADPT(
  DATE CREATED: JAN 11, 1995
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File
  NAME: Contrast Medium Allergy Field Access
  ID: RADPT(
GLOBAL REFERENCE: RADPT(DFN,0)
FIELD NUMBER: .05                       FIELD NAME: CONTRAST MEDIUM ALLERGY
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field can contain four values or null.  The four
 values are Y=YES, N=NO, U=UNKNOWN and sometimes YES=YES.  
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 4.0
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

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
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: 1121                            IA #: 1121
  FILE NUMBER: 450                      GLOBAL ROOT: PRSPC
  DATE CREATED: JAN 19, 1995            CUSTODIAL PACKAGE: PAID
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA1121
  ID: PRSPC
GLOBAL REFERENCE: PRSPC
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 accessing PRSPC( to obtain hourly rate
 information in order to accurately compute labor costs.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Salt Lake City

NUMBER: 1122                            IA #: 1122
  FILE NUMBER: 409.5                    GLOBAL ROOT: SDV(
  DATE CREATED: JAN 27, 1995            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: STOP CODES
  ID: SDV(
GLOBAL REFERENCE: SDV(DATE,'CS',
 GENERAL DESCRIPTION:   Read access is being requested to loop through the 'CS'
 node of the Scheduling Visits file.  The AMIE software will $O through this
 node collecting the stop codes.  The stop codes or any pointers will not be 
 stored in the AMIE database.  The 'CS' node is the subfile that contains the
 list of stop codes.  The node looks like ^SDV(DATE,"CS",..  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany

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
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
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
SUBSCRIBING PACKAGE: TOOLKIT            ISC: Oakland

NUMBER: 1126                            IA #: 1126
  GLOBAL ROOT: DD(                      DATE CREATED: FEB 01, 1995
  CUSTODIAL PACKAGE: 1                  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
SUBSCRIBING PACKAGE: TOOLKIT            ISC: Oakland

NUMBER: 1127                            IA #: 1127
  DATE CREATED: FEB 03, 1995            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File
  NAME: Lookup on B x-ref in globals DIE, DIBT, DIPT
GLOBAL REFERENCE: DIE('B',
GLOBAL REFERENCE: DIBT('B',
GLOBAL REFERENCE: DIPT('B',
  STATUS: Retired
SUBSCRIBING PACKAGE: IFCAP              ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   This integration agreement requests the functionality
 to lookup on the B cross-reference in the input, sort, and print templates
 (^DIE, ^DIBT, ^DIPT).  
  
 The pre-init for IFCAP Inventory $orders through the B cross-reference to 
 clean up the input, sort, and print templates using the routine DIK to delete
 them.  
  
 An example of the code looks like: 
  
 S NAME="PRCP" F  S NAME=$O(^DIE("B",NAME)) Q:$E(NAME,1,4)'="PRCP" ... D ^DIK 
  
 DURATION:  Version 5 only.  
SUBSCRIBING PACKAGE: NURSING SERVICE    ISC: Hines
 SUBSCRIBING DETAILS:   The Nursing Package has permission to reference the "B"
 cross-reference of the Input Template file (^DIE().  
  
 The Nursing Package has permission to delete entries from the Input Template
 file using ^DIK.  
  
 DURATION: Version 3.0 only.  

NUMBER: 1128                            IA #: 1128
  DATE CREATED: FEB 03, 1995            CUSTODIAL PACKAGE: 1
  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
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
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

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).  
  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
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
 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
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
  DATE ACTIVATED: OCT 13, 2010

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
  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: 1140                            IA #: 1140
  DATE CREATED: FEB 19, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         ROUTINE: XMDF
  NAME: MAILMAN: (old) Message Forwarding (Extr.Fun.)
  ID: XMDF
 GENERAL DESCRIPTION:   NOTICE!  NOTICE!  NOTICE! 
  
 XMDF is being RETIRED as a supported reference.  Use ENT1^XMD instead.  
  
 $$ENT^XMD  is an interface in the same routine as the other interfaces for 
 forwarding messages.  It has identical parameters and results and calls this
 one -- which will remain supported since documented first.  
  
 $$ENT^XMDF is a newly created extrinsic function to forward a message for 
 immediate delivery TO LOCAL RECIPIENTS ONLY. This is processed while the user
 waits. It is not passed on to background filer(s) as with most mail messages. 
  
  
 Usage: S X=$$ENT^XMDF(RECIPIENT,TOBASKET,MESSAGE,FORWARDER) 
  
 Where: 
        RECIPIENT  =  Recipient DUZ (Pointer to the New Person file) 
        TO_BASKET  =  Number of Basket (to recipient; typically null; if 
                                             less than 1, set to 1 (IN)) 
        MESSAGE    =  IEN of message in the Message file (XMZ) 
        FORWARDER  =  DUZ of person who forwarded message 
  
  
 Output:  If successful, +X>0.(1 or 10) ...or 
          If unsuccessful, X=Human readable error (+X<1); for example: 
                     "-0: Already a recipient" 
  
  
 Example: S X=$$ENT^XMDF(.5,"",XMZ,DUZ) I X<1 W *7,!,"**** Message NOT 
                                                          forwarded: ",X 
  STATUS: Retired                       EXPIRATION DATE: NOV 25, 2000

NUMBER: 1141                            IA #: 1141
  DATE CREATED: FEB 20, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine
  NAME: MAILMAN: Ext. Fun. to view/edit Info. Only Flag
 GENERAL DESCRIPTION:   $$INFO^XMA11 
  
 This extrinsic function allows the user to view and, potentially, change the
 type of a message to "Information Only".  
  
 Usage:         S X=$$INFO^XMA11(XMZ) 
  
 Where:         XMZ = Message Number (IEN in file 3.9) 
  
  
 Always returns a "0" (zero) and whatever would be returned by a DIE call.  
  
 Invokes DIE call in interactive mode.  
  
  
 Example: 
  
 S X=$$INFO(XMZ) 
  
 INFORMATION ONLY?: ? 
      If "YES", the message will be considered "INFORMATION ONLY" for all 
      recipients.  
      Choose from: 
        y        YES 
        n        NO INFORMATION ONLY?: ?? 
      This field, if set to "YES", will cause all recipients to be considered 
      "INFORMATION ONLY", which disables responses to the message. 
       
      If a sender wishes to individually restrict responses, "INFO:" before 
      the recipient's names will restrict their responses.  
       
      Messages which are broadcast (by naming a recipient "*"), are
 automatically 
      set to INFORMATION ONLY.  
      Choose from: 
        y        YES 
        n        NO INFORMATION ONLY?: 
  STATUS: Withdrawn

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
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(<subject>,1,65) 
  Interactive:  "Entered subject too long "1^$E(<subject>,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.^<subject> 
  Interactive:  "Control characters removed (<subject> is Subject accepted)." 
 (Control characters are removed and checking continues.) 
  
 Subject is null 
  Non-interact: <subject> 
  Interactive:  <subject> 
  
 Subject is "?" 
  Non-interact: 4-Enter a Message Subject, between 3 & 65 characters long or
 '^' to exit.^<subject> 
  Interactive:  "Enter a Message Subject, between 3 & 65 characters long or '^'
 to exit." 
                1^<subject> 
  
 Subject is too short 
  Non-interact: 1-SUBJECT must be at least 3 characters long.^<subject> 
  Interactive:  "SUBJECT must be at least 3 characters long." 
                1^<subject> 
  
 Subject is reserved format 
  Non-interact: 2-Subject names of this format (1""R""1.N) are RESERVED
 ^<subject> 
  Interactive:  "Subject names of this format (1""R""1.N) are RESERVED" 
                1^<subject> 
  
 Subject is OK 
  Non-interact: ^<subject> 
  Interactive:  ^<subject> 
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
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
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
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: 1149                            IA #: 1149
  DATE CREATED: FEB 20, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         ROUTINE: XMAREAD
  NAME: MAILMAN: User Question & Answer Driver and Validator
  ID: XMAREAD
 GENERAL DESCRIPTION:   NOTICE!  NOTICE!  NOTICE! 
  
 XMAREAD supported calls are being RETIRED.  Use FileMan's ^DIR instead.  
  
 ^XMAREAD contains the following application programmer functions: 
  
 $$READ^XMAREAD(prompt,question_type,default,anti-illegals_flag,.help_array) is
 a question and answer driver that will allow the caller to specify a question
 type, a prompt and a default.  
  
 $$CHECK^XMAREAD(question_type,string-to-be-tested) is a silent form of 
 $$READ^XMAREAD, e.g. it does not ask questions.  
  
  
  
  
 $$READ^XMAREAD(prompt,question_type,default,anti-illegals_flag,.help_array) 
  
 This function is a question and answer driver that will allow the caller to
 specify a question type, a prompt and a default.  The senders' exact input or
 the default (except in the case where a "Yes" or "No" question is answered) is
 returned to the caller.  All basic input checking is completed without
 changing or setting any variables.  
  
 Suggestions for Improvement to this interface are welcomed.  
  
  
 The way the function is used is as follows: 
  
 Usage: S X=$$READ^XMAREAD(A,B,C,D,.E) 
  
    Where: A (prompt) is a string that will be used as a prompt 
           B (question_type) is a question type C (default) is the default 
 answer to the questions 
           D (no_illegals_flag) If non-zero, do not store illegal characters 
           E (.help_array) is the array of help text (leading period is 
 required!) 
  
  
 There are four different types of questions (second parameter): 
  
   U      Abort (This question type will always append the message 
          "Enter <RET> to continue, "^" to abort") 
   F      Free Text 
   N      Number 
   Y      Yes or No 
  
  
 Illegal characters are control characters and any of these: 
                              @^!()#~_-=%$|[]\""><
  
  
 The value returnable for each type is: 
  
 Type   Handling 
  
 U      Whatever the user types -- the caller must interpret it.  
  
 F      A string of 3-30 characters which does not contain any control 
 characters or @, ^, !, (, ), #, -, _, =, %, $, |, [, ], \,", <, >.  If the
 third parameter is non-zero and not null or the variable XMREADNO exists,
 special characters are allowed.  Otherwise only numbers, spaces and letters
 are accepted.  
  
 N      Only integers are acceptable inputs.  
  
 Y      Any leading substrings of "Yes" or "No" are acceptable.  In either 
 case, "1" is returned for Yes, "0" for No.  
  
  
  
  $$CHECK^XMAREAD(Y,Z) 
  
 This function is the same as $$READ^XMAREAD, except it does not ask questions. 
 It merely puts any answers through a validity check.  
  
 Usage: S X=$$CHECK^XMAREAD(Y,Z) 
  
 Where: Y = The Type (U,N,F, or Y) 
        Z = The input to be validated 
  
 If the input is valid, the null string is returned.  If the input is NOT 
 valid, a text string which documents why the string is not valid is returned.  
  STATUS: Retired                       EXPIRATION DATE: NOV 25, 2000

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 DNS may receive a
 message addressed to it from DNS.  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@DNS 
  
 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,"LAST,FIRST@DNS") 
  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
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

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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Added 12/28/21, effective with PSJ*5*375. The CPRS-v33
 project, working on NSR #20090602, adds a function to enter stop and start
 dates for medications in CPRS as part of patch PSJ*5*375. Modifications were
 made to routines PSGOEF1 and PSIVORFB to read File #100.9. The direct file
 reference is made to get data needed to generate a notification to the
 provider when the Start/Stop Dates(duration)is not used.                      

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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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 and API calls that can be used to
 manage Options in the Options file. The LKOPT function is used to lookup all
 options.  The ADD and DELETE functions are used to add/delete menu items.  The
 OUT, RENAME, LOCK, and RLOCK are APIs used to populate certain fields for a
 given option.  
  STATUS: Active
KEYWORDS: KIDS
KEYWORDS: OPTION
KEYWORDS: MENU
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,
 field #2.  
  
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.  
  
COMPONENT/ENTRY POINT: LOCK
 COMPONENT DESCRIPTION:   LOCK(OPT,TXT) is used to set the LOCK field #3, in
 the OPTION file #19 for the given option.  
VARIABLES: OPT                          TYPE: Input
 VARIABLES DESCRIPTION:   OPT is the name of the option you want to lock.  
VARIABLES: TXT                          TYPE: Input
 VARIABLES DESCRIPTION:   TXT is the Key name used to lock the option.  It must
 match an entry in the SECURITY KEY file #19.1 
COMPONENT/ENTRY POINT: RLOCK
 COMPONENT DESCRIPTION:   RLOCK(OPT,TXT) is used to set the REVERSE/NEGATIVE
 field #3.01, in the OPTION file #19 for a given option.  
VARIABLES: OPT                          TYPE: Input
 VARIABLES DESCRIPTION:   OPT is the name of the option you want to reverse
 lock.  
VARIABLES: TXT                          TYPE: Input
 VARIABLES DESCRIPTION:   TXT is the Key name used to reverse lock the option. 
 It must match an entry in the SECURITY KEY file #19.1 
  DATE ACTIVATED: MAY 16, 2018

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
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: 1
  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
  GOOD ONLY FOR VERSION: 2.11
SUBSCRIBING PACKAGE: ONCOLOGY           ISC: Washington/Silver Spring

NUMBER: 1161                            IA #: 1161
  GLOBAL ROOT: ICD9(                    DATE CREATED: MAR 14, 1995
  CUSTODIAL PACKAGE: DRG GROUPER        CUSTODIAL ISC: Albany
  USAGE: Private                        TYPE: File
  NAME: DBIA1161-A                      ORIGINAL NUMBER: 1161
  ID: ICD9(
GLOBAL REFERENCE: ICD9(FE,
FIELD NUMBER: .01                       FIELD NAME: CODE NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DIAGNOSIS
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Diagnosis that the code represents 
 GLOBAL DESCRIPTION:   Contains all valid ICD diagnosis codes 
 GENERAL DESCRIPTION:   Converts IDC9 codes to there text equivalents 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MINIMAL PATIENT DATASET
  ISC: Albany

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
SUBSCRIBING PACKAGE: MINIMAL PATIENT DATASET
  ISC: Albany
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
 SUBSCRIBING DETAILS:   ADDED 12/11/2008 

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
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
SUBSCRIBING PACKAGE: MINIMAL PATIENT DATASET
  ISC: Albany

NUMBER: 1165                            IA #: 1165
  FILE NUMBER: 4.2                      GLOBAL ROOT: DIC(4.2,
  DATE CREATED: MAR 14, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBAI1165
  ID: DIC(4.2,
GLOBAL REFERENCE: DIC(4.2,B
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the name of the domain, as used in network
 adressing 
FIELD NUMBER: 13                        FIELD NAME: station
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the domains station # 
 GENERAL DESCRIPTION:   Used to build PPP DOMAIN XREF file (#1020.8).  This is
 a file of station numbers and domains.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  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: Retired
SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  ISC: Albany

NUMBER: 1167                            IA #: 1167
  DATE CREATED: APR 14, 1995            CUSTODIAL PACKAGE: 1
  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
  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: 1
  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
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
SUBSCRIBING PACKAGE: MINIMAL PATIENT DATASET
  ISC: Albany
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: SURGERY            ISC: Birmingham

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                            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.  
GLOBAL REFERENCE: RARPT(DA,0)
 GLOBAL DESCRIPTION:   VistA Radiology allows Imaging to read the ^RARPT(DA,0)
 global directly and with VA FileMan.  
 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.  
  
 As of 12/05/2019 (MAG*3.0*231) radiology allows Imaging to read the zero 
 ^RARPT(DA,0) global directly and with VA FileMan.  
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
KEYWORDS: MAG
KEYWORDS: MAG*3.0*231
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: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA1172                        ID: RADPT
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.  
GLOBAL REFERENCE: RADPT('ADC1',DA(2),DA(1),DA
 GLOBAL DESCRIPTION:   This is the cross-reference for the SITE ACCESSION
 NUMBER field.  (70.03;31).  
GLOBAL REFERENCE: RADPT(DA,0)
 GLOBAL DESCRIPTION:   VistA Radiology grants VI permission to look at the
 entire zero node ^RADPT(DA,0) directly and with FileMan read.  
 GENERAL DESCRIPTION:   As of 12/05/2019 VistA Radiology gives Imaging
 permission to read file #70 ^RADPT(DA,0) directly and with VA FileMan.  
  
 VistA Radiology grants permission to VistA Imaging (VI) to read cross- 
 reference ^RADPT('AO'.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAGDRCPB
KEYWORDS: outside orders
KEYWORDS: RA-MAG meds & radiopharms
KEYWORDS: MAG*3.0*231
KEYWORDS: ISI
KEYWORDS: ISI*1.1*110 DFN
KEYWORDS: VistARad COTS
KEYWORDS: MEDICOM
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 "ADC" or "ADC1"
 cross-references 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. 
SUBSCRIBING PACKAGE: ISI IMAGING
 SUBSCRIBING DETAILS:   Added 1/10/23, effective with ISI*1.1*110 ISI Rad
 software is a direct replacement to the VistARad workstation, which 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. The accesses to RADPT 
 function in the same manner as VistARad, as described in this IA.  
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Added 9/9/24 effective with Patch MECH*1.0*1 This patch
 processes HL7 messages about Imaging studies. As part of this processing this 
 Patch needs to gather patient demographics that are Imaging related.  
  DATE ACTIVATED: JAN 10, 2023

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                            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)
 GLOBAL DESCRIPTION:   With MAG*3.0*231 VI is granted permission to read the
 entire zero node of the RAD/NUC MED PROCEDURES file directly and with VA
 FileMan.  
 GENERAL DESCRIPTION:   VistA Radiology gives permission to Imaging (VI) to
 read the entire zero node of the RAD/NUC MED PROCEDURES (#71) file directly
 and with VA FileMan.  
  
 VistA Radiology gives permission to Imaging (VI) to read the MODALITY field
 (#.01) of the MODALITY sub-file (71.0731) directly and with VA FileMan.  
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
KEYWORDS: MAG
KEYWORDS: MAG*3.0*231
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.  
  
 With MAG*3.0*231 VI is granted permission to read the entire zero node of the
 RAD/NUC MED PROCEDURES file directly and with VA FileMan.  

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: Controlled Subscription
  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
KEYWORDS: ISI
KEYWORDS: ISI*1.1*110 DFN
KEYWORDS: VistARad COTS
KEYWORDS: MEDICOM
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Imaging needs to read the status field on a specified
 accession number.  
SUBSCRIBING PACKAGE: ISI IMAGING
 SUBSCRIBING DETAILS:   Added 1/10/23 effective with ISI*1.1*110 
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Added 9/6/24 effective with Patch MECH*1.0*1 MEDICOM
 TECHNOLOGIES requests read access to the EXAM STATUS (#.01) field when
 processing HL7 order messages.  

NUMBER: 1176                            IA #: 1176
  FILE NUMBER: 74                       GLOBAL ROOT: RARPT(
  DATE CREATED: MAY 05, 1995
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA1176
  ID: RARPT(
GLOBAL REFERENCE: RARPT(D0,2005
FIELD NUMBER: 2005                      FIELD NAME: IMAGE
  LOCATION: 2005;0                      ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Radiology gives permission to Imaging to read file #74
 (^RARPT).  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

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.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: RARIC                        NAME: DBIA1178
  ID: RARIC
 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.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAGDIR9A
KEYWORDS: MAGGTRA
KEYWORDS: ISI
KEYWORDS: ISI*1.1*110 DFN
KEYWORDS: VistARad COTS
KEYWORDS: MEDICOM
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
SUBSCRIBING PACKAGE: ISI IMAGING
 SUBSCRIBING DETAILS:   Added 12/28/22 effective with ISI*1.1*110 
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Added 09/11/24, effective with patch MECH*1.0*1 to
 access CREATE^RARIC. When processing an incoming Radiology order to create a
 stud for the new order.  
  DATE ACTIVATED: AUG 05, 2009

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
 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.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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

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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP v.2.0 attaches HMP INPT EVENTS protocol as an item
 to the DGPM MOVEMENT EVENTS protocol to trigger unsolicited patient updates
 from VistA to JDS when a patient movement action occurs.  
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
 **************************************************************************

NUMBER: 1182                            IA #: 1182
  DATE CREATED: MAR 24, 1995            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: IBRFN2
  NAME: NATIONAL DATA BASE CALL TO IB   ID: IBRFN2
 GENERAL DESCRIPTION:   National Data Base Routine (RCNR4) calls $$CRIT^IBRFN2
 to get insurance information.  
  STATUS: Withdrawn
COMPONENT/ENTRY POINT: $$CRIT
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Washington/Silver Spring

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                            STATUS: Active
  DURATION: Till Otherwise Agreed
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/CV/SHD/CL) 
  
     ^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
  DATE ACTIVATED: AUG 12, 2015

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
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
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
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
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
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
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

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
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

NUMBER: 1191                            IA #: 1191
  DATE CREATED: OCT 20, 2003            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIA1189-C
  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 displaying Medicine package Summary fields associated with Images.  
  
 The Imaging functions require direct global read access to the 
 Procedure/Subspecialty file (697.2), the Image multiple of each of the 
 Medicine Procedure files listed below, and the Summary field each of the Files
 Listed below.  
  
 Medicine Procedure 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: MAGDISP,
 MAGMIM, MAGSUM, and MAGABLP.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

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
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

NUMBER: 1194                            IA #: 1194
  DATE CREATED: APR 06, 1995            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: IBARXEU
  NAME: DBIA1194                        ID: IBARXEU
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RXST
 COMPONENT DESCRIPTION:   $$RXST^IBARXEU(DFN,IBDT) 
  
 This function is used by are to determine if a patient is RX Copay exempt or
 not.  
  
 It will return one of the following: 
  
 -1 if no data exists 0 if patient is non-exempt 1 if patient is exempt.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file pointer 
VARIABLES: ibdt                         TYPE: Input
 VARIABLES DESCRIPTION:   Date to check for (optional) default is today.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Washington/Silver Spring

NUMBER: 1195                            IA #: 1195
  FILE NUMBER: 55                       GLOBAL ROOT: DD(55.06,10,1,
  DATE CREATED: JUN 10, 2003            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File
  NAME: INPATIENT MEDICATIONS XREF CLEAN UP
  ID: DD(55.06,10,1,
GLOBAL REFERENCE: DD(55.06,10,1,
FIELD NUMBER: 10                        FIELD NAME: START DATE/TIME
  ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   
  This is the date and time the order is to begin.  This package initially 
 assigns the START DATE/TIME to the closest administration time, next
 admininistration time, or NOW depending on the value of the DEFAULT START DATE
 CALCULATION field in the INPATIENT WARD PARAMETERS. START DATE/TIME may not be
 entered prior to 7 days from the order's LOGIN DATE.  
 GENERAL DESCRIPTION:   Inpatient Medications 4.5 exported the AUDS cross
 reference on the START DATE/TIME(#10) field of the UNIT DOSE(#55.06) multiple
 of the PHARMACY PATIENT(#55) file. This cross reference is not referenced by
 the Inpatient Medications software, and since this field is "hard set", the
 cross reference is never set. This causes problems with locally created sort 
 templates on this field when running VA FILEMAN V21.  
  
 To elminate this problem, a routine will be exported in PSJ*4.5*12 that will
 identify and delete this cross reference from the Data Dictionary.  
  
 The routine to be used for this is listed below: 
  
 PSJUTL2 ;B'ham ISC/MLM - REMOVE AUDS XREF FROM 55.06,10 ; 14 Apr 95 / 9:59AM 
         ;;4.5; Inpatient Medications ;**12**;7 Oct 94 
         ;
 EN      ; Entry point from programmer mode to delete the AUDS xref.  
         ;
         W "This routine was exported as part of PSJ*4.5*12 to delete the
 AUDS",! 
         W "cross reference from the PHARMACY PATIENT(#55) file.",!! 
         N X,DIR 
         S DIR(0)="Y",DIR("B")="NO",DIR("A")="Delete this cross reference?" 
         S DIR("?")="Enter ""YES"" to continue with this process or ""NO"" to
 abort." 
         D ^DIR Q:$D(DIRUT) 
         F X=0:0 S X=$O(^DD(55.06,10,1,X)) Q:'X  D 
         .K:$G(^DD(55.06,10,1,X,0))="55^AUDS" ^DD(55.06,10,1,X) 
         K ^DD(55,0,"IX","AUDS",55.06,10) 
         W !!,"Done." 
         Q 
  
  
 Inpatient Medications requests a PRIVATE DBIA with VA FILEMAN to directly K
 ^DD(55.06,10,1,X), where X is the IEN of the AUDS cross reference.  
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 4.5
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham

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
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
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
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
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: 1200                            IA #: 1200
  FILE NUMBER: 55                       GLOBAL ROOT: DD(55,
  DATE CREATED: JUN 10, 2003            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File
  NAME: INPATIENT MEDICATIONS XREF CLEAN UP
  ID: DD(55,
GLOBAL REFERENCE: DD(55,0,'IX','AUDS',55.06,10)
FIELD NUMBER: 10                        FIELD NAME: START DATE/TIME
 FIELD DESCRIPTION:   
  This is the date and time the order is to begin.  This package initially 
 assigns the START DATE/TIME to the closest administration time, the next
 admininistration time, or NOW depending on the value of the DEFAULT START DATE
 CALCULATION field in the INPATIENT WARD PARAMETERS. START DATE/TIME may not be
 entered prior to 7 days from the order's LOGIN DATE.  
 GENERAL DESCRIPTION:   Inpatient Medications 4.5 exported the AUDS cross
 reference on the START DATE/TIME(#10) field of the UNIT DOSE(#55.06) multiple
 of the PHARMACY PATIENT(#55) file. This cross reference is not referenced by
 the Inpatient 
  
 Medications software, and since this field is "hard set", the cross reference
 is never set. This causes problems with locally created sort templates on this
 field when running VA FILEMAN V21.  
  
 To elminate this problem, a routine will be exported in PSJ*4.5*12 that will
 identify and delete this cross reference from the Data Dictionary.  
  
 The routine to be used for this is listed below: 
  
 PSJUTL2 ;B'ham ISC/MLM - REMOVE AUDS XREF FROM 55.06,10 ; 14 Apr 95 / 9:59AM 
         ;;4.5; Inpatient Medications ;**12**;7 Oct 94 
         ;
 EN      ; Entry point from programmer mode to delete the AUDS xref.  
         ;
         W "This routine was exported as part of PSJ*4.5*12 to delete the
 AUDS",! 
         W "cross reference from the PHARMACY PATIENT(#55) file.",!! 
         N X,DIR 
         S DIR(0)="Y",DIR("B")="NO",DIR("A")="Delete this cross reference?" 
  
         S DIR("?")="Enter ""YES"" to continue with this process or ""NO"" to
 abort." 
         D ^DIR Q:$D(DIRUT) 
         F X=0:0 S X=$O(^DD(55.06,10,1,X)) Q:'X  D 
         .K:$G(^DD(55.06,10,1,X,0))="55^AUDS" ^DD(55.06,10,1,X) 
         K ^DD(55,0,"IX","AUDS",55.06,10) 
         W !!,"Done." 
         Q 
  
 Inpatient Medications requests a PRIVATE DBIA with VA FILEMAN to directly K
 ^DD(55.06,0,"IX","AUDS",55.06,10).  
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 4.5
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham

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
  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
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
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: 1                  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
  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
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 - DECISION SUPPORT SYSTEM 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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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
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: 1218                            IA #: 1218
  FILE NUMBER: 6914                     GLOBAL ROOT: ENG(6914
  DATE CREATED: MAY 05, 1995            CUSTODIAL PACKAGE: ENGINEERING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: ENGINEERING/IMAGING
  ID: ENG(6914
GLOBAL REFERENCE: ENG(6914,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ENTRY
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Equipment item sequential number from Inventory File.  
 GLOBAL DESCRIPTION:   Inventory File.  
 GENERAL DESCRIPTION:   Imaging Package is given permission to point to File
 6914.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

NUMBER: 1219                            IA #: 1219
  FILE NUMBER: 6928                     GLOBAL ROOT: ENG(6928
  DATE CREATED: MAY 05, 1995            CUSTODIAL PACKAGE: ENGINEERING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: ENNGINEERING/IMAGING SPACE
  ID: ENG(6928
GLOBAL REFERENCE: ENG(6928,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ROOM NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Room number in medical center 
 GLOBAL DESCRIPTION:   Engineering space file contains detailed information
 about each room in the Medical Center.  
 GENERAL DESCRIPTION:   The Imaging Package is given permission to point to 
 File 6928.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            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
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham

NUMBER: 1221                            IA #: 1221
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: JUL 31, 1998            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA1220-B
  ORIGINAL NUMBER: 1220                 ID: PSRX(
GLOBAL REFERENCE: PSRX(D0,0)
FIELD NUMBER: .01                       FIELD NAME: RX #
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ISSUE DATE
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PATIENT STATUS
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PROVIDER
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: CLINIC
  LOCATION: 0;5                         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: 8                         FIELD NAME: DAYS SUPPLY
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: # OF REFILLS
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SIG
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: MAIL/WINDOW
  LOCATION: 0;11                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: CLERK CODE
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 100                       FIELD NAME: STATUS
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(D0,1,D1,0)
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: 1.1                       FIELD NAME: DAYS SUPPLY
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: MAIL/WINDOW
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: REMARKS
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PHARMACIST NAME
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: LOT NUMBER
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: CLERK CODE
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: LOGIN DATE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: DIVISION
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10.1                      FIELD NAME: DISPENSE DATE
  LOCATION: 0;19                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 13                        FIELD NAME: EXPIRATION DATE
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: PROVIDER
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 17                        FIELD NAME: RELEASED DATE/TIME
  LOCATION: 0;18                        ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: PSRX(D0,1,D1,1)
FIELD NUMBER: 16                        FIELD NAME: GENERIC PROVIDER
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(D0,2)
FIELD NUMBER: 20                        FIELD NAME: DIVISION
  LOCATION: 2;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 21                        FIELD NAME: LOGIN DATE
  LOCATION: 2;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: 23                        FIELD NAME: PHARMACIST
  LOCATION: 2;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 24                        FIELD NAME: LOT #
  LOCATION: 2;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 25                        FIELD NAME: DISPENSED DATE
  LOCATION: 2;5                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 26                        FIELD NAME: EXPIRATION DATE
  LOCATION: 2;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 27                        FIELD NAME: NDC
  LOCATION: 2;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 28                        FIELD NAME: MANUFACTURER
  LOCATION: 2;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 29                        FIELD NAME: MAN EXPIRATION DATE
  LOCATION: 2;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 30                        FIELD NAME: GENERIC PROVIDER
  LOCATION: 2;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 31                        FIELD NAME: RELEASED DATE/TIME
  LOCATION: 2;13                        ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: PSRX(D0,'MP')
FIELD NUMBER: 35                        FIELD NAME: METHOD OF PICKUP
  LOCATION: MP;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(D0,'P',
FIELD NUMBER: .01                       FIELD NAME: PARTIAL DATE
  LOCATION: P;1                         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,'TN')
FIELD NUMBER: 6.5                       FIELD NAME: TRADE NAME
  LOCATION: TN;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(D0,3)
FIELD NUMBER: 12                        FIELD NAME: REMARKS
  LOCATION: 3;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 26.1                      FIELD NAME: CANCEL DATE
  LOCATION: 3;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 101                       FIELD NAME: LAST DISPENSED DATE
  LOCATION: 3;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 102                       FIELD NAME: NEXT POSSIBLE FILL
  LOCATION: 3;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 102.1                     FIELD NAME: PRIOR FILL DATE
  LOCATION: 3;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 109                       FIELD NAME: COSIGNING PHYSICIAN
  LOCATION: 3;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(D0,'A'
FIELD NUMBER: .01                       FIELD NAME: ACTIVITY LOG (Multiple-52.3)
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: REASON
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: INITIATOR OF ACTIVITY
  LOCATION: 0;3                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: RX REFERENCE
  LOCATION: 0;4                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: COMMENT
  LOCATION: 0;5                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: PSRX(D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: TRANSMISSION NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: SEQUENCE #
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: RX INDICATOR
  LOCATION: 0;3                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: STATUS
  LOCATION: 0;4                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: NDC
  LOCATION: 0;8                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: CANCELLED DATE/TIME
  LOCATION: 0;5                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This global is created by the CMOP package and consists
 of information relating to the prescription data transmitted. Data on this
 node is created and maintained by the CMOP package.  
FIELD NUMBER: 6                         FIELD NAME: RESUBMIT STATUS
  LOCATION: 0;6                         ACCESS: Direct Global R/W & w/Fileman
 GLOBAL DESCRIPTION:   This global is created by the CMOP package and consists
 of information relating to the prescription data transmitted. Data on this
 node is created and maintained by the CMOP package.  
GLOBAL REFERENCE: PSRX(D0,4,D1,1)
FIELD NUMBER: 8                         FIELD NAME: CANCELLED REASON
  LOCATION: 1;1                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: PSRX(D0,5,D1,0)
FIELD NUMBER: .01                       FIELD NAME: LOT/EXP
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: EXPIRATION DATE
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: RX INDICATOR
  LOCATION: 0;3                         ACCESS: Direct Global R/W & w/Fileman
 GLOBAL DESCRIPTION:   This global is created by the CMOP package and consists
 of information relating to the prescription data transmitted. Data on this
 node is updated and maintained by the CMOP package.  
GLOBAL REFERENCE: PSRX('AR',RELDT,DA,FILL)
 GLOBAL DESCRIPTION:   This cross reference is set by the CMOP package for
 prescriptions released by the CMOP. RELDT is the release date/time,DA is the
 internal entry number of the prescription record in file #52, and FILL is the
 number of the fill of the prescription i.e.(0=original fill,1=refill
 one,2=refill two,etc.).  
GLOBAL REFERENCE: PSRX('AS',TRNDT,DA,FILL)
 GLOBAL DESCRIPTION:   This cross reference is set by the CMOP package for
 prescriptions which have been transmitted by the CMOP software, but not yet
 released by the CMOP.  TRNDT is the transmission date/time,DA is the internal
 entry number of the prescription record in file #52, and FILL is the number of
 the fill of the prescription i.e.(0=original fill,1=refill one,2=refill
 two,etc.).  
GLOBAL REFERENCE: PSRX('B',RX#,DA)
 GLOBAL DESCRIPTION:   This cross reference is used by the CMOP package to
 lookup prescriptions in the Prescription file #52.  RX# is the value of the
 .01 field and DA is the internal entry number of the record.  
GLOBAL REFERENCE: PSRX('AD',PSXD,PSXR,PSXF)
 GLOBAL DESCRIPTION:   This cross reference is used by the CMOP package to
 lookup prescriptions in the Prescription file #52. PSXD is the date of the
 fill, PSXR is the internal entry number of the prescription, and PSXF is the
 number of the fill for the prescription.  
GLOBAL REFERENCE: PSRX('ADL',FILLDATE,DRUG POINTER,DA)
 GLOBAL DESCRIPTION:   This cross reference is used by the CMOP package Direct
 Global R/W for completing and updating prescription data in the Prescription 
 file #52.  
 GENERAL DESCRIPTION:   The Consolidated Mail Outpatient Pharmacy package will
 extract data on a daily basis. Fields noted with write access will be updated
 on a daily basis. The extensive overhead associated with building transmission 
 data prevents the CMOP software from utilizing the supported reference for
 Outpatient Pharmacy Version 7.0 as described in DBIA 1878.  This agreement is
 PRIVATE and designed for use ONLY by the CMOP software.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham

NUMBER: 1222                            IA #: 1222
  FILE NUMBER: 52.5                     GLOBAL ROOT: PS(52.5,
  DATE CREATED: MAY 09, 1995            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA1220-C
  ORIGINAL NUMBER: 1220                 ID: PS(52.5,
GLOBAL REFERENCE: PS(52.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: RX #
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: SUSPENSE DATE
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: PATIENT
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: TYPE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: PARTIAL
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: DIVISION
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: CMOP INDICATOR
  LOCATION: 0;7                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PRINT DATE
  LOCATION: 0;8                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: PRINTED BY
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: DEA SPECIAL HDLG
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: SEQUENCE
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: REPRINT
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: FILL
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(52.5,D0,'P')
FIELD NUMBER: 2                         FIELD NAME: PRINTED
  LOCATION: P;1                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: PS(52.5,'C',SUSDT,DA)
 GLOBAL DESCRIPTION:   This cross reference is used by the CMOP package to
 lookup prescription entries in file # 52.5. SUSDT is the suspense date of the
 prescription and DA is the internal entry number of the record.  
GLOBAL REFERENCE: PS(52.5,'AC',DFN,SUSDT,DA)
 GLOBAL DESCRIPTION:   This cross reference is used by the CMOP package to
 manage RX SUSPENSE file entries for CMOP data transmissions. This cross
 reference is both set and killed by the CMOP package. The kills and sets are
 determined by the screening criteria for designating a CMOP prescription.  DFN
 is the internal entry numb of the Patient file #2, SUSDT is the suspense
 date/time, and DA is the internal entry number of the record.  
GLOBAL REFERENCE: PS(52.5,'B',RXIEN,DA)
 GLOBAL DESCRIPTION:   This cross reference is used by the CMOP package to
 lookup prescription entries in the Rx Suspense file #52.5. RXIEN is the .01
 field of the entry, and DA is the internal entry number of the record.  
GLOBAL REFERENCE: PS(52.5,'AL',SUSDT,DFN,DA)
 GLOBAL DESCRIPTION:   This cross reference is set by the CMOP package when the
 CMOP Indicator field #3 is set to LOADING FOR TRANSMISSION. SUSDT is the
 suspense date/time DFN is the Patient file #2 internal entry number, and DA is
 the internal entry number of the record.  
GLOBAL REFERENCE: PS(52.5,'AP',SUSDT,DFN,DA)
 GLOBAL DESCRIPTION:   This cross reference is set by the CMOP package when the
 CMOP Indicator field is set to PRINTED LOCALLY. SUSDT is the suspense
 date/time DFN is he Patient file #2 internal entry number, and DA is the
 internal entry number of the record.  
GLOBAL REFERENCE: PS(52.5,'AS',PRNT_DT,PRNTD_BY,DIV,SEQ,DA)
 GLOBAL DESCRIPTION:   This cross-reference is used for batching suspense
 prints, so different batches within a day can be reset. This cross-reference
 also sets the 'APR' cross-reference. The 'APR' cross-reference will list CMOP
 Rx's by batch for reseting. Only the 'AS' or the 'APR' will exist for an Rx.  
 For non-CMOP prescriptions, it sets the global ^PS(52.5,"AS",Print 
 Date,Printed By,Division,Sequence,DA)="".  For CMOP prescriptions, it sets the
 global ^PS(52.5,"APR",Print Date,Printed By,Division,Sequence,DA)="".  
GLOBAL REFERENCE: PS(52.5,'AQ',SUSDT,DFN,DA)
 GLOBAL DESCRIPTION:   This cross reference is set by the CMOP package when the
 CMOP Indicator field #3 is set to QUEUED FOR TRANSMISSION. SUSDT is the 
 suspense date/time DFN is the Patient file #2 internal entry number, and DA is
 the internal entry number of the record.  
GLOBAL REFERENCE: PS(52.5,'AX',SUSDT,DFN,DA)
 GLOBAL DESCRIPTION:   This cross reference is set by the CMOP package when the
 CMOP Indicator field #3 is set to TRANSMISSION COMPLETED. SUSDT is the 
 suspense date/time DFN is the Patient file #2 internal entry number, and DA is
 the internal entry number of the record.  
 GENERAL DESCRIPTION:   The Consolidated Mail Outpatient Pharmacy package will
 extract data from this file on a daily basis. The CMOP INDICATOR field (#3) is
 created by the CMOP software and is used to manage the prescription data for
 CMOP transmission.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
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
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham

NUMBER: 1224                            IA #: 1224
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG(
  DATE CREATED: MAY 08, 1995
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA1220-E
  ORIGINAL NUMBER: 1220                 ID: PSDRUG(
GLOBAL REFERENCE: PSDRUG(D0,3)
FIELD NUMBER: 213                       FIELD NAME: CMOP DISPENSE
  LOCATION: 3;1                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: PSDRUG(D0,4,0)
FIELD NUMBER: 214                       FIELD NAME: ACTIVITY LOG
  LOCATION: 4;0                         ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   The CONSOLIDATED MAIL OUTPATIENT PHARMACY package
 creates and maintains data in these fields.  
  STATUS: Retired
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham

NUMBER: 1227                            IA #: 1227
  DATE CREATED: SEP 28, 1995            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: DGACT
  NAME: TREATING SPECIALTY INACTIVATION
  ID: DGACT
 GENERAL DESCRIPTION:   This is a supported reference to screen on active
 Facility Treating Specialties or Specialties.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ACTIVE(FILE,IEN,DGDT)
 COMPONENT DESCRIPTION:   
   Input -- FILE to determine if checking facility TS or TS 
                FACILITY TREATING SPECIALTY (45.7) 
                SPECIALTY (42.4) 
        IEN is the internal IFN of whichever file passed in 
     DGDT as 'as of' date (uses DT if undefined) 
  Output -- 1 if active, 0 otherwise 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   To determine if checking facility TS or TS FACILITY
 TREATING SPECIALTY (45.7) SPECIALTY (42.4) 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The internal IFN of whichever file passed in.  
VARIABLES: DGDT                         TYPE: Input
 VARIABLES DESCRIPTION:   'as of' date (uses DT if undefined) 
SUBSCRIBING PACKAGE: INCIDENT REPORTING
  ISC: Albany

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
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.  

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
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
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
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
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN

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
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
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: 1                  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
  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 
  STATUS: Active                        DURATION: Till Otherwise Agreed
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 20070122 

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: IMMUNIZATION EXTRACT
  ID: PXRHS03
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to retrieve immunization data. Subscribers can retrieve data on
 administrations, contraindications, and refusals.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IMMUNIZATION ADMINISTRATION
KEYWORDS: IMMUNIZATION CONTRAINDICATION
KEYWORDS: IMMUNIZATION REFUSAL
COMPONENT/ENTRY POINT: IMMUN(DFN,PXFG,PXFILTER)
 COMPONENT DESCRIPTION:   This line tag returns data on immunization
 administrations for the given patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number (IEN) of the patient's entry in
 the PATIENT file (#2).  
VARIABLES: PXFG                         TYPE: Input
 VARIABLES DESCRIPTION:   Primary sorting order. (Optional; defaults to "S") 
   "S": Alphabetical by either immunization short 
        name or name (if short name is null).  
        (Since short name is not standardized and 
        is null for newer immunizations added after 
        patch PX*1*201 was installed, the "S" 
        argument is deprecated and is only 
        supported for backward compatibility 
        purposes).  
   "A": Alphabetical by immunization name.  
   "C": Chronological 
   "R": Reverse chronological 
VARIABLES: PXFILTER                     TYPE: Input
 VARIABLES DESCRIPTION:   Filter entries returned. (Optional) 
   "G:XXX": Only return immunizations for Vaccine 
            Group Name XXX.  
   "I:XXX": Only return immunizations IEN XXX.  
   "C:XXX": Only return immunizations for CVX 
            Code XXX.  
VARIABLES: TMP GLOBAL                   TYPE: Output
 VARIABLES DESCRIPTION:   Return data from V Immunization file (#9000010.11) is
 structured in the TMP global as follows: ^TMP("PXI",$J,Sort,Sort2,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,Sort,Sort2,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,Sort,Sort2,IFN,2) = 
    ROUTE OF ADMIN [E;1302] ^ 
    SITE OF ADMIN [E;1303] ^ DOSAGE [E;1312.5] ^ 
    DOCUMENTER [E;1206] ^TMP("PXI",$J,Sort,Sort2,IFN,3) = LOT [E;.05] ^ 
    MANUF [E;9999999.41;.02] ^ 
    EXP DATE [I;9999999.41;.09] ^TMP("PXI",$J,Sort,Sort2,IFN,4) = 
    RESULTS [E;1401] ^ READING [E;1402] ^ 
    DATE/TIME READ [I;1403] ^ READER [E;1404] ^ 
    READING RECORDED [I;1405] ^ 
    HOURS READ [E;1406] ^TMP("PXI",$J,Sort,Sort2,IFN,"RCOM") = 
    READING COMMENT [E;1501] ^TMP("PXI",$J,Sort,Sort2,IFN,"FN",CNT) = 
    CDC FULL VACCINE NAME [E;9999999.14;2] 
 ^TMP("PXI",$J,Sort,Sort2,IFN,"R",CNT) = 
    REMARKS [E;1101] ^TMP("PXI",$J,Sort,Sort2,IFN,"S") = 
    DATA SOURCE [E;80102] ^TMP("PXI",$J,Sort,Sort2,IFN,"VIS",CNT) = 
    VIS OFFERED TO PATIENT [E;2] ^ 
    EDITION DATE [I;920;.02] 
     
  [] = [I(nternal)/E(xternal); Optional file #; 
        Record #] 
     
     Subscripts: 
         If PXFG 
         Equals:    Then subscript will be: 
         =======    ===========================
   Sort -   S       Immunization short name, 
                    or Name truncated to 10 
                    characters (if short name 
                    is null) 
            A       Immunization Name 
            C       FileMan date of Date of Event 
                    or Visit 
            R       Inverse FileMan date of Date of 
                    Event or Visit 
  Sort2 - C or R    Immunization name 
          A or S    Inverse FileMan date of Date of 
                    Event or Visit 
     
  IFN   - Internal Record # 
COMPONENT/ENTRY POINT: CONREF(DFN,PXFG,PXFILTER)
 COMPONENT DESCRIPTION:   This line tag returns data on immunization
 contraindications and refusals for the given patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number (IEN) of the patient's entry in
 the PATIENT file (#2).  
VARIABLES: PXFG                         TYPE: Input
 VARIABLES DESCRIPTION:   Primary sorting order. (Optional; defaults to "A")  
   "A": Alphabetical by immunization name.  
   "C": Chronological 
   "R": Reverse chronological 
VARIABLES: PXFILTER                     TYPE: Input
 VARIABLES DESCRIPTION:   Filter entries returned. (Optional) 
   "G:XXX": Only return immunizations for Vaccine 
            Group Name XXX.  
   "I:XXX": Only return immunizations IEN XXX.  
   "C:XXX": Only return immunizations for CVX 
            Code XXX.  
VARIABLES: TMP GLOBAL                   TYPE: Output
 VARIABLES DESCRIPTION:   Return data from V IMM CONTRA/REFUSAL EVENTS file
 (#9000010.707) is structured in the TMP global as follows: 
 ^TMP("PXCRI",$J,PXSORT,PXSORT2,PXSORT3,IFN,0) = 
    IMMUNIZATION [E;.04] ^ 
    EVENT DATE/TIME [I;1201] or VISIT/ADMIT 
      DATE&TIME [I;.03] ^ 
    TYPE [VARIABLE POINTER PREFIX;.01] ^ 
    CONTRAINDICATION/REFUSAL [E;.01] ^ 
    WARN UNTIL DATE [I;.05] ^ 
    REFUSED VACCINE GROUP [E;1205] ^ 
    ENCOUNTER PROVIDER [E;1204] ^ 
    CONTRAINDICATION/PRECAUTION [E;920.4;.06] 
 ^TMP("PXCRI",$J,PXSORT,PXSORT2,PXSORT3,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("PXCRI",$J,PXSORT,PXSORT2,PXSORT3,IFN,"COM")= 
    COMMENTS [E;81101] ^TMP("PXCRI",$J,PXSORT,PXSORT2,PXSORT3,IFN,"FN",CNT)= 
    CDC FULL VACCINE NAME [E;9999999.14;2] 
 ^TMP("PXCRI",$J,PXSORT,PXSORT2,PXSORT3,IFN,"RGROUP", 
      GNAME,IMMIEN)= 
    IMMUNIZATION [E;.04] 
  
  [] = [I(nternal)/E(xternal); Optional file #; 
        Field #] 
     
     Subscripts: 
          If PXFG 
          Equals:    Then subscript will be: 
          =======    ===========================
 PXSORT -    A       Immunization Name 
             C       FileMan date of Date of Event 
                     or visit 
             R       Inverse FileMan date of Date 
                     of Event or visit 
  
 PXSORT2 - C or R    Immunization name 
           A         Inverse FileMan date of Date 
                     of Event or visit 
  
 PXSORT3 - A, C, R   Type; "C" for Contraindication 
                     or "R" for Refusal 
  
   IFN   - N/A       Internal Record Number 
  
 GNAME   - N/A       VACCINE GROUP NAME 
                     [E;9999999.14;7] 
  
 IMMIEN  - N/A       Vaccine Internal Entry Number 
                     [I;9999999.14] 
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 ACTIVATED: OCT 10, 2023

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
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
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
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
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
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: 1
  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) 
  
  ^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
  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
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
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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Added 11/21/18, effective with PXRM*2*44.  

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
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
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
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
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.  
  DATE ACTIVATED: FEB 15, 2013

NUMBER: 1258                            IA #: 1258
  GLOBAL ROOT: DD(                      DATE CREATED: AUG 08, 1995
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: File
  NAME: VARIABLES IN PROGRAMMER HOOKS   ID: DD(
 GENERAL DESCRIPTION:   The following DBIA describes the variables that are
 available and what values these variables are set to within programmer hooks.  
 (define programmer hook here) 
  STATUS: Withdrawn

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
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: Controlled Subscription
  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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI
 SUBSCRIBING DETAILS:   Added 9/11/24 effective with DSIR*8.2*16, in order to
 check for a given patient in PROBLEM file (#9000011) field .02 PATIENT NAME
 using FILEMAN. I $$GET1^DIQ(9000010,DSIRCHK_",",.02,"I")) 

NUMBER: 1262                            IA #: 1262
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: AUG 09, 1995            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            NAME: DBIA1262
  ID: VA(200,
GLOBAL REFERENCE: VA(200,450)
FIELD NUMBER: 450                       FIELD NAME: PAID EMPLOYEE
  LOCATION: 450;1                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field is a pointer to the PAID EMPLOYEE (#450) file. 
 
FIELD NUMBER: 9                         FIELD NAME: SSN
  LOCATION: 1;9                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The PAID 4.0 development team is requesting permission
 to add a new field to the NEW PERSON file and a new cross-reference to the NEW
 PERSON SSN field.  
  
 The new field will be PAID EMPLOYEE (#450) and will be a pointer to the PAID
 EMPLOYEE (#450) file.  This field will be uneditable.  
  
 The new MUMPS cross-reference will be the AJ cross-reference on the SSN (#9)
 field.  This cross-reference will set or kill the NEW PERSON pointer in the
 PAID EMPLOYEE file and the PAID EMPLOYEE pointer in the NEW PERSON file 
 whenever the SSN value is changed or deleted.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 1264                            IA #: 1264
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT(
  DATE CREATED: AUG 09, 1995            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA1264
  ID: ICPT(
GLOBAL REFERENCE: ICPT(IEN,0)
FIELD NUMBER: .01                       FIELD NAME: CPT CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   
  This field contains codes that represent procedures from CPT, AMA, and HCFA.  
FIELD NUMBER: 2                         FIELD NAME: SHORT NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   
  This field contains a short description of the CPT code.  
FIELD NUMBER: 3                         FIELD NAME: CPT CATEGORY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   
  This field contains the CPT Category associatied with the CPT code. It is a
 pointer to the CPT Category File.  
FIELD NUMBER: 5                         FIELD NAME: INACTIVE FLAG
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   
   This field is used to inactivate a CPT code. If this field contains a '1'
 then the code is inactive.  
GLOBAL REFERENCE: ICPT(B,
 GLOBAL DESCRIPTION:   This is the "B" cross reference.    Global Read.  
GLOBAL REFERENCE: ICPT(C,
 GLOBAL DESCRIPTION:   This is the "C" cross reference.    Global Read.  
 GENERAL DESCRIPTION:   
   This is an agreement to look at several fields in the CPT FILE #81 using
 Fileman.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany
REMINDER: JUN 06, 2007

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
  GOOD ONLY FOR VERSION: 3.0
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1267                            IA #: 1267
  FILE NUMBER: 9999999.14               GLOBAL ROOT: AUTTIMM(
  DATE CREATED: AUG 11, 1995            CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: DBIA1265-C IMMUNIZATION
  ORIGINAL NUMBER: 1265                 ID: AUTTIMM(
 GENERAL DESCRIPTION:   The PCE Patient Care Encounter Package requests a DBIA
 to distribute the Indian Health Services IMMUNIZATION file (9999999.14) 
  
 STANDARD DATA DICTIONARY #9999999.14 -- IMMUNIZATION FILE   08/11/95 PAGE 1 
 STORED IN ^AUTTIMM(  (38 ENTRIES)   SITE: ISCSLC   UCI: DVA,DEV 
  
 DATA          NAME                  GLOBAL        DATA ELEMENT       TITLE     
            LOCATION      TYPE 
 ------------------------------------------------------------------
 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.  
  
  
  
 IDENTIFIED BY: SHORT NAME (#.02) 
  
 POINTED TO BY: SELECTION ITEM field (#4) of the FILE SELECTION 
                    CRITERIA sub-field (#142.94) of the HEALTH 
                    SUMMARY MAINT ITEM File (#142.9) 
                SELECTION ITEM field (#.01) of the SELECTION ITEM 
                    sub-field (#142.944) of the FILE SELECTION 
                    CRITERIA sub-field (#142.94) of the HEALTH 
                    SUMMARY MAINT ITEM File (#142.9) 
                FILE ENTRY field (#.01) of the PCE CODE MAPPING 
                    File (#811.1) 
                RELATED SUPPORTING FILE ENTRY field (#.02) of the 
                    PCE CODE MAPPING File (#811.1) 
                MULTIPLE VALUES field (#3101) of the PCE TAXOTIPLE VALUES field 
                   (#.01) of the MULTIPLE VALUES 
                    sub-field (#811.23101) of the PCE TAXONOMY File 
                    (#811.2) 
                SELECTION ITEM field (#.01) of the SELECTION ITEM 
                    sub-field (#811.944) of the FILE SELECTION 
                    CRITERIA sub-field (#811.94) of the PCE 
                    REMINDER/MAINTENANCE ITEM File (#811.9) 
                IMMUNIZATION field (#.01) of the V IMMUNIZATION 
                    File (#9000010.11) 
                IMMUNIZATION field (#.04) of the IMMUNIZATION LOT 
                    File (#9999999.41) 
  
  
 CROSS REFERENCED BY: NAME(B), MNEMONIC(B), CODE(C), SHORT NAME(D) 
  
  
 9999999.14,.01NAME                   0;1 FREE TEXT (Required) 
  
               INPUT TRANSFORM:  K:$L(X)>45!($L(X)<3)!'(X'?1P.E)!(X 
                                 '?.ANP) X 
               LAST EDITED:      APR 11, 1988 
               HELP-PROMPT:      ANSWER WITH IMMUNIZATION (3-45 
                                 CHARACTERS) 
               DESCRIPTION:      This is the name of the 
                                 Immunization (e.g. Tetanus 
                                 Toxoid).  
  
                                 Enter the Name of the Immunization 
                                 using 3 to 45 characters.  
  
               CROSS-REFERENCE:  9999999.14^B 
                                 1)= S ^AUTTIMM("B",$E(X,1,30),DA)="" 
                                2)= K ^AUTTIMM("B",$E(X,1,30),DA) 
  
  
 9999999.14,.02SHORT NAME             0;2 FREE TEXT (Required) 
  
               INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L 
                                 (X)>10!($L(X)<2) X 
               LAST EDITED:      OCT 08, 1986 
               HELP-PROMPT:      ANSWER WITH A SHORT NAME (2-10 
                                 CHARACTERS) 
               DESCRIPTION:      This is the "Short" name for this 
                                 immunization such as an acronym, 
                                 Nick name, or other name by which 
                                 it might be called (e.g. Tet Tox).  
  
  
                                 Enter the short name using 2 to 10 
                                 characters (e.g. Tet Tox).  
  
               CROSS-REFERENCE:  9999999.14^D 
                                 1)= S ^AUTTIMM("D",$E(X,1,30),DA)= 
                                 ""
  
                                 2)= K ^AUTTIMM("D",$E(X,1,30),DA) 
  
  
 9999999.14,.03CODE                   0;3 FREE TEXT (Required) 
  
  
               INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L 
                                 (X)>2!($L(X)<2)!'(X?2N) X I $D(X), 
                                 $D(^AUTTIMM("C",X)),'$D(^AUTTIMM(" 
                                 C",X,DA)) K X W "    Already used! 
                                  "
               LAST EDITED:      JAN 25, 1994 
               HELP-PROMPT:      ANSWER MUST BE 2 CHARACTERS IN 
                                 LENGTH 
               DESCRIPTION:      This is a 2 digit code that 
                                 represents the immunization.  
  
                                 Enter a 2 digit code that 
                                 represents the immunization code.  
  
               NOTES:            XXXX--CAN'T BE ALTERED EXCEPT BY PR OGRAMMER 
  
               CROSS-REFERENCE:  9999999.10),DA)="" 
                                 
  
                                 2)= K ^AUTTIMM("C",$E(X,1,30),DA) 
  
  
 9999999.14,.05MAX # IN SERIES        0;5 SET 
  
                                 '0' FOR NON-SERIES; 
                                 '1' FOR 1; 
                                 '2' FOR 2; 
                                 '3' FOR 3; 
                                 '4' FOR 4; 
                                 '5' FOR 5; 
                                 '6' FOR 6; 
                                 '7' FOR 7; 
                                 '8' FOR 8; 
               LAST EDITED:      DEC 09, 1987 
               DESCRIPTION:      (Optional) This is the maximum 
                                 number of vaccinations that can be 
                                 given for this immunization.  
  
                                 Enter the number between 0 and 8 
                                 that represents the maximum 
                                 allowable vaccinations that can be 
                                 given for this immunization.  
  
  
 9999999.14,.06CHILDHOOD IMMUNIZATION 0;6 SET (Required) 
  
                                 '0' FOR NO; 
                                 '1' FOR YES; 
               LAST EDITED:      AUG 29, 1988 
               DESCRIPTION:      This is a yes(1)/no(2) answer to 
                                 the question "Was this 
                                 immunization given during 
                                 childhood?" 
  
                                 Enter a 0 for no or a 1 for yes.  
  
  
 9999999.14,8801MNEMONIC              88;1 FREE TEXT 
  
               INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L 
                                 (X)>3!($L(X)<1) X 
               LAST EDITED:      NOV 04, 1987 
               HELP-PROMPT:      ANSWER MUST BE 1-3 CHARACTERS IN 
                                 LENGTH 
               DESCRIPTION:      This is the mnemonic for this 
                                 Immunization.  
  
                                 Enter a 1 to 3 character mnemonic.  
  
  
               CROSS-REFERENCE:  9999999.14^B^MNEMONIC 
                                 1)= S ^AUTTIMM("B",$E(X,1,30),DA)= 
                                 1 
  
                                 2)= K ^AUTTIMM("B",$E(X,1,30),DA) 
  
  
 INPUT TEMPLATE(S): 
  
 PRINT TEMPLATE(S): 
  
 SORT TEMPLATE(S): 
  
 FORM(S)/BLOCK(S): 
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  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
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 1269                            IA #: 1269
  FILE NUMBER: 9999999.15               GLOBAL ROOT: AUTTEXAM(
  DATE CREATED: AUG 11, 1995            CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: DBIA1265-D EXAM
  ORIGINAL NUMBER: 1265                 ID: AUTTEXAM(
 GENERAL DESCRIPTION:   The PCE Patient Care Encounter Package requests a DBIA
 to distribute the Indian Health Services EXAM file (9999999.15) in the VA 
  
  
 STANDARD DATA DICTIONARY #9999999.15 -- EXAM FILE   08/11/95  PAGE 1 STORED IN
 ^AUTTEXAM(  (29 ENTRIES)   SITE: ISCSLC   UCI: DVA,DEV ( VERSION 1T) 
  
 DATA          NAME                  GLOBAL        DATA ELEMENT       TITLE     
            LOCATION      TYPE 
 -----------------------------------------------------------------
 This file is a list of Physical Exams and associated codes developed
 specifically for use in the IHS for entering Examinations performed on an
 Outpatient or Inpatient Encounter.  Some of the Exams are used in 
  
  
  
  
 POINTED TO BY: SELECTION ITEM field (#4) of the FILE SELECTION 
                    CRITERIA sub-field (#142.94) of the HEALTH 
                    SUMMARY MAINT ITEM File (#142.9) 
                SELECTION ITEM field (#.01) of the SELECTION ITEM 
                    sub-field (#142.944) of the FILE SELECTION 
                    CRITERIA sub-field (#142.94) of the HEALTH 
                    SUMMARY MAINT ITEM File (#142.9) 
                MULTIPLE VALUES field (#3101) of the PCE TAXONOMY 
                    File (#811.2) 
                MULTIPLE VALUES field (#.01) of the MULTIPLE 
                    VALUES sub-field (#811.23101) of the PCE 
                    TAXONOMY File (#811.2) 
                SELECTION ITEM field (#.01) of the SELECTION ITEM 
                    sub-field (#811.944) of the FILE SELECTION 
                    CRITERIA sub-field (#811.94) of the PCE 
                    REMINDER/MAINTENANCE ITEM File (#811.9) 
                EXAM field (#.01) of the V EXAM File (#9000010.13) 
                MEMBERS field (#.01) of the MEMBERS sub-field 
                    (#9001020.15) of the STRUCTURE sub-field 
                    (#9001020.01) of the HEALTH SUMMARY FLOWSHEET 
                    File (#9001020) 
  
  
 CROSS REFERENCED BY: NAME(B), MNEMONIC(B), CODE(C) 
  
  
 9999999.15,.01NAME                   0;1 FREE TEXT (Required) 
  
               INPUT TRANSFORM:  K:$L(X)>30!($L(X)<3)!'(X'?1P.E)!( 
                                 X'?.ANP) X 
               HELP-PROMPT:      ANSWER WITH THE NAME OF THE EXAM 
                                 (3-3ON:      This is the name of the 
                                 examination being given to a 
                                 patient.  
  
                                 Enter the name of the exam using 
                                 3 to 30 characters.  
  
  
               CROSS-REFERENCE:  9999999.15^B 
                                 1)= S ^AUTTEXAM("B",$E(X,1,30),DA 
                                 )=""
  
                                 2)= K ^AUTTEXAM("B",$E(X,1,30),DA 
                                 )
  
  
 9999999.15,.02CODE                   0;2 FREE TEXT (Required) 
  
               INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$ 
                                 L(X)>2!($L(X)<2)!'(X?2N) X I $D(X 
                                 ),$D(^AUTTEXAM("C",X)),'$D(^AUTTE 
                                 XAM("C",X,DA)) K X W "    Already 
                                  used! " 
               LAST EDITED:      DEC 22, 1989 
               HELP-PROMPT:      ANSWER MUST BE 2 CHARACTERS IN 
                                 LENGTH 
               DESCRIPTION:      This is a 2-digit code associated 
                                 with the exam given.  
  
                                 Enter a two digit number.  
  
  
               NOTES:            XXXX--CAN'T BE ALTERED EXCEPT BY P ROGRAMMER 
  
               CROSS-REFERENCE:  9999999.15^C 
                                 1)= S ^AUTTEXAM("C",$E(X,1,30),DA 
                                 )=""
  
                                 2)= K ^AUTTEXAM("C",$E(X,1,30),DA 
                                 )
  
  
 9999999.15,.03SEX SPECIFIC           0;3 SET 
  
                                 'M' FOR MALE; 
                                 'F' FOR FEMALE; 
               LAST EDITED:      FEB 09, 1989 
               HELP-PROMPT:      ENTER M OR F IF THIS EXAM IS SEX 
                                 SPECIFIC 
               DESCRIPTION:      (Optional) This is the indicator 
                                 for psecifying the sex for which 
                                 the exam is given.  
  
                                 Enter an "M" for male or an "F" 
                                 for Female.  
  
  
 9999999.15,8801MNEMONIC              88;1 FREE TEXT 
  
               INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$ 
                                 L(X)>2!($L(X)<1) X 
               LAST EDITED:      DEC 16, 1985 
               HELP-PROMPT:      ANSWER MUST BE 1-2 CHARACTERS IN 
                                 LENGTH 
               DESCRIPTION:      This is a 1 - 2 character 
                                 mnemonic for this exam.  
  
                                 Enter a 1monic.  
  
  
               CROSS-REFERENCE:  9999999.15^B^MNEMONIC 
                                 1)= S ^AUTTEXAM("B",$E(X,1,30),DA 
                                 )=1 
  
                                 2)= K ^AUTTEXAM("B",$E(X,1,30),DA 
                                 )
  
  
 INPUT TEMPLATE(S): 
  
 PRINT TEMPLATE(S): 
  
 SORT TEMPLATE(S): 
  
 FORM(S)/BLOCK(S): 
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Salt Lake City

NUMBER: 1270                            IA #: 1270
  FILE NUMBER: 9999999.17               GLOBAL ROOT: AUTTTRT(
  DATE CREATED: AUG 11, 1995            CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: DBIA1265-E TREATMENT
  ORIGINAL NUMBER: 1265                 ID: AUTTTRT(
 GENERAL DESCRIPTION:   The PCE Patient Care Encounter Package requests a DBIA
 to distribute the Indian Health Services TREATMENT file (9999999.17) in the
 VA.  
  
 STANDARD DATA DICTIONARY #9999999.17 -- TREATMENT FILE   08/11/95 PAGE 1 
 STORED IN ^AUTTTRT(  (293 ENTRIES)   SITE: ISCSLC   UCI: DVA,DEV (V ERSION 1T) 
  
 DATA          NAME                  GLOBAL        DATA ELEMENT       TITLE     
            LOCATION      TYPE 
 ------------------------------------------------------------------
 This file is a table developed by the IHS for recording Patient Treatments
 which are not covered in the ICD-9-CM Procedures.  These are primarily Nursing
 Activities perfomed during a Patient Visit, such as Ear Irriga- tion, or
 Instructions or Counseling given to a patient for a Medical Problem.  
  
  
  
  
 POINTED TO BY: TREATMENT field (#.01) of the V TREATMENT File 
                    (#9000010.15) 
  
  
 CROSS REFERENCED BY: NAME(B), MNEMONIC(B), CODE(C) 
  
  
 9999999.17,.01NAME                   0;1 FREE TEXT (Required) 
  
               INPUT TRANSFORM:  K:$L(X)>30!($L(X)<3)!'(X'?1P.E)!(X 
                                 '?.ANP) X 
               HELP-PROMPT:      ANSWER WITH TREATMENT NAME (3-30 
                                 CHARACTERS) 
               DESCRIPTION:      The name of the treatment that is 
                                 being administered.  
  
                                 Enter the ntheme of a treatment 
                                 using 3 to 30 characters.  
  
               CROSS-REFERENCE:  9999999.17^B 
                                 1)= S ^AUTTTRT("B",$E(X,1,30),DA)= 
                                 ""
  
                                 2)= K ^AUTTTRT("B",$E(X,1,30),DA) 
  
  
 9999999.17,.02CODE                   0;2 FREE TEXT (Required) 
  
               INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L 
                                 (X)>6!($L(X)<6)!'(X?6N) X I $D(X), 
                                 $D(^AUTTTRT("C",X)),'$D(^AUTTTRT(" 
                                 C",X,DA)) K X W "    Already used! 
                                  "
               LAST EDITED:      DEC 22, 1989 
               HELP-PROMPT:      ANSWER MUSNGTH 
               DESCRIPTION:      This is an IHS code which 
                                 represents the treatment being 
                                 rendered.  
  
                                 Enter a 6 digit code.  
  
               NOTES:            XXXX--CAN'T BE ALTERED EXCEPT BY PR OGRAMMER 
  
               CROSS-REFERENCE:  9999999.17^C 
                                 1)= S ^AUTTTRT("C",$E(X,1,30),DA)= 
                                 ""
  
                                 2)= K ^AUTTTRT("C",$E(X,1,30),DA) 
  
  
 9999999.17,.03SUMMARY FLAG           0;3 FREE TEXT (Required) 
  
               INPUT TRANSFORM:  K:$L(X)>1!($L(X)<1)!'((X="0")!(X=" 
                                 1")) X 
               HELP-PROMPT:      ANSWER MUST BE 1 CHARACTER IN 
                                 LENGTH 
  
 9999999.17,8801MNEMONIC              88;1 FREE TEXT 
  
               INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L 
                                 (X)>6!($L(X)<1) X 
               LAST EDITED:      MAR 16, 1987 
               HELP-PROMPT:      ANSWER MUST BE 1-6 CHARACTERS IN 
                                 LENGTH 
               DESCRIPTION:      (Optional) This is a mnemonic for 
                                 this treatment.  
  
  
               CROSS-REFERENCE:  9999999.17^B^MNEMONIC 
                                 1)= S ^AUTTTRT("B",$E(X,1,30),DA)= 
                                 1 
  
                                 2)= K ^AUTTTRT("B",$E(X,1,30),DA) 
  
  
 INPUT TEMPLATE(S): 
  
 PRINT TEMPLATE(S): 
  
 SORT TEMPLATE(S): 
  
 FORM(S)/BLOCK(S): 
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Salt Lake City

NUMBER: 1271                            IA #: 1271
  FILE NUMBER: 9999999.28               GLOBAL ROOT: AUTTSK(
  DATE CREATED: AUG 11, 1995            CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: DBIA1265-F SKIN TEST
  ORIGINAL NUMBER: 1265                 ID: AUTTSK(
 GENERAL DESCRIPTION:   The PCE Patient Care Encounter Package requests a DBIA
 to distribute the Indian Health Services SKIN TEST file (9999999.28) in the
 VA.  
  
 STANDARD DATA DICTIONARY #9999999.28 -- SKIN TEST FILE   08/11/95 PAGE 1 
 STORED IN ^AUTTSK(  (9 ENTRIES)   SITE: ISCSLC   UCI: DVA,DEV (VERS ION 1T) 
  
 DATA          NAME                  GLOBAL        DATA ELEMENT       TITLE     
            LOCATION      TYPE 
 ------------------------------------------------------------------
 This file contains Skin Tests and their associated codes developed by the IHS. 
 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.  
  
  
  
  
 POINTED TO BY: SELECTION ITEM field (#4) of the FILE SELECTION 
                    CRITERIA sub-field (#142.94) of the HEALTH 
                    SUMMARY MAINT ITEM File (#142.9) 
                SELECTION ITEM field (#.01) of the SELECTION ITEM 
                    sub-field (#142.944) of the FILE SELECTION 
                    CRITERIA sub-field (#142.94) of the HEALTH 
                    SUMMARY MAINT ITEM File (#142.9) 
                FILE ENTRY field (#.01) of the PCE CODE MAPPING 
                    File (#811.1) 
                RELATED SUPPORTING FILE ENTRY field (#.02) of the 
                    PCE CODE MAPPING File (#811.1) 
                MULTIPLE VALUES field (#3101) of the PCE TAXONOMY 
                    File (#811.2) 
                MULTIPLE VALUES field (#.01) of the MULTIPLE VALUES 
                    sub-field (#811.23101) of the PCE TAXONOMY File 
                    (#811.2) 
                SELECTION ITEM field (#.01) of the SELECTION ITEM 
                    sub-field (#811.944) of the FILE SELECTION 
                    CRITERIA sub-field (#811.94) of the PCE 
                    REMINDER/MAINTENANCE ITEM File (#811.9) 
                SKIN TEST field (#.01) of the V SKIN TEST File 
                    (#9000010.12) 
  
  
 CROSS REFERENCED BY: NAME(B), MNEMONIC(B), CODE(C) 
  
  
 9999999.28,.01NAME                   0;1 FREE TEXT (Required) 
  
               INPUT TRANSFORM:  K:$L(X)>10!($L(X)<3)!'(X'?1P.E)!(X 
                                 '?.ANP) X 
               LAST EDITED:      DEC 16, 1985 
               HELP-PROMPT:      ANSWER WITH SKIN TEST NAME (3-10 
                                 CHARACTERS) 
               DESCRIPTION:      This is the name of the skin test 
                                 (e.g Cocci,PPD).  
  
                                 Enter a name using 3 to 10 
                                 characters.  
  
               CROSS-REFERENCE:  9999999.28^B 
                                 1)= S ^AUTTSK("B",$E(X,1,30),DA)=" 
                                 "
  
                                 2)= K ^AUTTSK("B",$E(X,1,30),DA) 
  
  
 9999999.28,.02CODE                   0;2 FREE TEXT (Required) 
  
               INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L 
                                 (X)>2!($L(X)<2)!'(X?2N) X I $D(X), 
                                 $D(^AUTTSK("C",X)),'$D(^AUTTSK("C" 
                                 ,X,DA)) K X W "    Already used! " 
               LAST EDITED:      DEC 22, 1989 
               HELP-PROMPT:      ANSWER MUST BE 2 CHARACTERS IN 
                                 LENGTH 
               DESCRIPTION:      This is a 2 character IHS code for 
                                 the skin test.  
  
                                 Enter a 2 character code.  
  
  
               NOTES:            XXXX--CAN'T BE ALTERED EXCEPT BY PR OGRAMMER 
  
               CROSS-REFERENCE:  9999999.28^C 
                                 1)= S ^AUTTSK("C",$E(X,1,30),DA)=" 
                                 "
  
                                 2)= K ^AUTTSK("C",$E(X,1,30),DA) 
  
  
 9999999.28,8801MNEMONIC              88;1 FREE TEXT 
  
               INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L 
                                 (X)>2!($L(X)<1) X 
               LAST EDITED:      DEC 16, 1985 
               HELP-PROMPT:      ANSWER MUST BE 1-2 CHARACTERS IN 
                                 LENGTH 
               DESCRIPTION:      (Optional) This is a 1-2 character 
                                 mnemonic for the skin test.  
  
                                 Enter a 1-2 character mnemonic.  
  
               CROSS-REFERENCE:  9999999.28^B^MNEMONIC 
                                 1)= S ^AUTTSK("B",$E(X,1,30),DA)=1 
                                 2)= K ^AUTTSK("B",$E(X,1,30),DA) 
  
  
 INPUT TEMPLATE(S): 
  
 PRINT TEMPLATE(S): 
  
 SORT TEMPLATE(S): 
  
 FORM(S)/BLOCK(S): 
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  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
COMPONENT/ENTRY POINT: VISIT(DFN,FROM,RECNO,OCCLIM,CATCODE,PSTAT)
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 1274                            IA #: 1274
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT(
  DATE CREATED: JUN 01, 1995            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA1274
  ID: ICPT(
GLOBAL REFERENCE: ICPT(
FIELD NUMBER: .01                       FIELD NAME: CPT CODE
  ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: SHORT NAME
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: ICPT(D0,"D",
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Includes access to "C" x-ref 
 GENERAL DESCRIPTION:   The Health Summary Package desires to set up an
 integration agreement with the CPT/AMB Procedures Update Package to access the
 CPT (#81) file.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 1275                            IA #: 1275
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9(
  DATE CREATED: JUN 01, 1995            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA1275
  ID: ICD9(
GLOBAL REFERENCE: ICD9(REC #,0)
FIELD NUMBER: .01                       FIELD NAME: CODE NUMBER
  ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DIAGNOSIS
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: ICD9(REC #,1)
FIELD NUMBER: 10                        FIELD NAME: DESCRIPTION
  ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Health Summary Package desires to see up an
 integration agreement with the DRG Grouper Package to access the ICD Diagnosis
 (#80) file.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
SUBSCRIBING PACKAGE: HEALTH SUMMARY

NUMBER: 1276                            IA #: 1276
  FILE NUMBER: 80.1                     GLOBAL ROOT: ICD0(
  DATE CREATED: JUN 01, 1995            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA1276
  ID: ICD0(
GLOBAL REFERENCE: ICD0(REC #,0)
FIELD NUMBER: .01                       FIELD NAME: CODE NUMBER
  ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: OPERATION/PROCEDURE
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: ICD0(REC #,1)
FIELD NUMBER: 10                        FIELD NAME: DESCRIPTION
  ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Health Summary Package desires to set up an
 integration agreement with the DRG Grouper Package to access the ICD
 Operation/Procedure (#80.1) file.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
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
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
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
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 1280                            IA #: 1280
  FILE NUMBER: 90                       GLOBAL ROOT: MR(
  DATE CREATED: JUN 06, 1995            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Dallas                 USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA1280                        ID: MR(
GLOBAL REFERENCE: MR(DFN,'PE',DATE)
FIELD NUMBER: 100                       FIELD NAME: PHY
  LOCATION: PE;0                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,.01                 FIELD NAME: PHY
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,.02                 FIELD NAME: HEIGHT IN INCHES
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,.03                 FIELD NAME: WEIGHT IN POUNDS
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,.04                 FIELD NAME: TEMP.
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,.05                 FIELD NAME: PULSE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,.06                 FIELD NAME: B.P.
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,.07                 FIELD NAME: RESPS.
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,.9                  FIELD NAME: GENERAL APPEARANCE
  LOCATION: .8;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,2                   FIELD NAME: HEAD
  LOCATION: .9;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,2.9                 FIELD NAME: HEAD AB
  LOCATION: 1;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,3                   FIELD NAME: EYES
  LOCATION: .9;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,3.1                 FIELD NAME: EOM
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,3.2                 FIELD NAME: PUPIL SIZE
  LOCATION: 2;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,3.3                 FIELD NAME: FUNDI
  LOCATION: 2;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,3.4                 FIELD NAME: RLA
  LOCATION: 2;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,3.9                 FIELD NAME: EYES AB
  LOCATION: 2;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,4                   FIELD NAME: EARS
  LOCATION: .9;3                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,4.1                 FIELD NAME: HEARING
  LOCATION: 3;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,4.2                 FIELD NAME: EXTERNAL MEATUS
  LOCATION: 3;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,4.3                 FIELD NAME: DRUMS
  LOCATION: 3;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,4.9                 FIELD NAME: EARS AB
  LOCATION: 3;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,5                   FIELD NAME: NOSE
  LOCATION: .9;4                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,5.9                 FIELD NAME: NOSE AB
  LOCATION: 4;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,6                   FIELD NAME: MOUTH
  LOCATION: .9;5                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,6.9                 FIELD NAME: MOUTH AB
  LOCATION: 5;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,7                   FIELD NAME: NECK
  LOCATION: .9;6                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,7.9                 FIELD NAME: NECK AB
  LOCATION: 6;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,8                   FIELD NAME: CHEST AND BREASTS
  LOCATION: .9;7                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,8.9                 FIELD NAME: CHEST AB
  LOCATION: 7;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,9                   FIELD NAME: LUNGS
  LOCATION: .9;8                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,9.9                 FIELD NAME: LUNGS AB
  LOCATION: 8;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,10                  FIELD NAME: HEART
  LOCATION: .9;9                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,10.9                FIELD NAME: HEART AB
  LOCATION: 9;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,11                  FIELD NAME: ABDOMEN
  LOCATION: .9;10                       ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,11.9                FIELD NAME: ABDOMEN AB
  LOCATION: 10;9                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,12                  FIELD NAME: GENITALIA
  LOCATION: .9;11                       ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,12.1                FIELD NAME: TESTES
  LOCATION: 11;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,12.2                FIELD NAME: EPIDIDYMIDES
  LOCATION: 11;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,12.3                FIELD NAME: PENIS
  LOCATION: 11;3                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,12.4                FIELD NAME: PROSTATE
  LOCATION: 11;4                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,13                  FIELD NAME: PELVIC
  LOCATION: .9;12                       ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,13.9                FIELD NAME: PELVIC AB
  LOCATION: 12;9                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,14                  FIELD NAME: RECTUM
  LOCATION: .9;13                       ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,14.9                FIELD NAME: RECTUM AB
  LOCATION: 13;9                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,15                  FIELD NAME: BACK
  LOCATION: .9;14                       ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,15.9                FIELD NAME: BACK AB
  LOCATION: 14;9                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,16                  FIELD NAME: EXTREMITIES
  LOCATION: .9;15                       ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,16.9                FIELD NAME: EXTREMITIES AB
  LOCATION: 15;9                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,17                  FIELD NAME: NEUROLOGICAL
  LOCATION: .9;17                       ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,17.9                FIELD NAME: NEUROLOGICAL AB
  LOCATION: 16;9                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,18                  FIELD NAME: SKIN
  LOCATION: .9;17                       ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,18.9                FIELD NAME: SKIN AB
  LOCATION: 17;9                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,19                  FIELD NAME: LYMPH
  LOCATION: .9;18                       ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,19.9                FIELD NAME: LYMPH AB
  LOCATION: 18;9                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,30                  FIELD NAME: COMMENTS
  LOCATION: 19;0                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 90.02,.01                 FIELD NAME: COMMENTS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 90.01,31                  FIELD NAME: INITIAL IMPRESSION
  LOCATION: 20;0                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 90.03,.01                 FIELD NAME: INITIAL IMPRESSION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 90.01,32                  FIELD NAME: HEIGHT IN CENTIMETERS
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,33                  FIELD NAME: WEIGHT IN KILOGRAMS
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,34                  FIELD NAME: TEMPERATURE CENTIGRADE
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,12.9                FIELD NAME: GENITALIA AB
  LOCATION: 11;9                        ACCESS: Read w/Fileman
FIELD NUMBER: 90.01,29                  FIELD NAME: EXAMINER
  LOCATION: 0;10                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Health Summary Package requests of the Mental
 Health Package permission to access the Medical Record (#90) file in order to 
 display/print Mental Health Physical Exam data.  
  
 This DBIA will be effective until the next version of either Health Summary or
 Mental Health at which time a Mental Health API will need to be set up.  
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: MH 5.01
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

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
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 '<NMSP> GECS*' will have the ENTRY and EXIT ACTION
 changed.  <NMSP> 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
  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
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)=<name of the menu option> 
  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: 1293                            IA #: 1293
  FILE NUMBER: 9999999.64               GLOBAL ROOT: AUTTHF(
  DATE CREATED: AUG 11, 1995            CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: DBIA1265-G HEALTH FACTORS
  ORIGINAL NUMBER: 1265                 ID: AUTTHF(
 GENERAL DESCRIPTION:   
  
 The PCE Patient Care Encounter Package requests a DBIA to distribute the 
 Indian Health Services HEALTH FACTORS file (9999999.64) in the VA.  
  
  
 STANDARD DATA DICTIONARY #9999999.64 -- HEALTH FACTORS FILE   08/11 /95  PAGE
 1 STORED IN ^AUTTHF(  (15 ENTRIES)   SITE: ISCSLC   UCI: DVA,DEV (VER SION 1T) 
  
 DATA          NAME                  GLOBAL        DATA ELEMENT       TITLE     
            LOCATION      TYPE 
 ------------------------------------------------------------------
 Changes to this data dictionary should be coordinated thru the IHS DBA.  
  
  
  
 IDENTIFIED BY: ENTRY TYPE (#.1) 
  
 POINTED TO BY: SELECTION ITEM field (#.01) of the SELECTION ITEM 
                    sub-field (#142.14) of the STRUCTURE sub-field 
                    (#142.01) of the HEALTH SUMMARY TYPE File 
                    (#142) 
                SELECTION ITEM field (#4) of the FILE SELECTION 
                    CRITERIA sub-field (#142.94) of the HEALTH 
                    SUMMARY MAINT ITEM File (#142.9) 
                SELECTION ITEM field (#.01) of the SELECTION ITEM 
                    sub-field (#142.944) of the FILE SELECTION 
                    CRITERIA sub-field (#142.94) of the HEALTH 
                    SUMMARY MAINT ITEM File (#142.9) 
                HEALTH FACTOR field (#.01) of the V HEALTH 
                    FACTORS File (#9000010.23) 
                HEALTH FACTOR field (#.01) of the HEALTH STATUS 
                    File (#9000019) 
                HEALTH FACTOR TYPE field (#1) of the HEALTH FACTORS 
                    PANEL sub-field (#9001015.08) of the HEALTH 
                    SUMMARY TYPE File (#9001015) 
                CATEGORY field (#.03) of the HEALTH FACTORS File 
                    (#9999999.64) 
                NOT USED WITH field (#.01) of the NOT USED WITH 
                    sub-field (#9999999.641101) of the HEALTH 
                    FACTORS File (#9999999.64) 
                                                                                
                           
                    SUMMARY TYPE File (#9001015) 
                CATEGORY field (#.03) of the HEALTH FACTORS File 
                    (#9999999.64) 
                NOT USED WITH field (#.01) of the NOT USED WITH 
                    sub-field (#9999999.641101) of the HEALTH 
                    FACTORS File (#9999999.64) 
  
  
 CROSS REFERENCED BY: CATEGORY(AC), ENTRY TYPE(AD), FACTOR(B), 
                CODE(C), SYNONYM(D) 
  
  
 9999999.64,.01FACTOR                 0;1 FREE TEXT (Required) 
  
               INPUT TRANSFORM:  K:$L(X)>30!($L(X)<3)!'(X'?1P.E) X 
               LAST EDITED:      JUL 01, 1991 
               HELP-PROMPT:      ANSWER WITH HEALTH FACTOR NAME 
                                 (3-30 CHARACTERS) 
               DESCRIPTION:      This is the name of the Health 
                                 Factor (e.g., Current Smoker, 
                                 Non-Tobacco User) 
  
               CROSS-REFERENCE:  9999999.64^B 
                                 1)= S ^AUTTHF("B",$E(X,1,30),DA)=" 
                                 "
  
                                 2)= K ^AUTTHF("B",$E(X,1,30),DA) 
  
  
 9999999.64,.02CODE                   0;2 FREE TEXT 
  
               INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L 
                                 (X)>4!($L(X)<4)!'(X?4N) X 
               LAST EDITED:      JUL 01, 1991 
               HELP-PROMPT:      Answer must be 4 characters in 
                                 length.  
               DESCRIPTION:      (Optional) This is a short IHS 4 
                                 digit numeric code for this health 
                                 factor.  
  
                                 Enter a 4 digit number.  
  
               CROSS-REFERENCE:  9999999.64^C 
                                 1)= S ^AUTTHF("C",$E(X,1,30),DA)=" 
                                 "
  
                                 2)= K ^AUTTHF("C",$E(X,1,30),DA) 
  
  
 9999999.64,.03CATEGORY               0;3 POINTER TO HEALTH FACTORS 
                                  FILE (#9999999.64) (Required) 
  
               INPUT TRANSFORM:  S DIC("S")="I $P(^(0),U,10)'=""F"" 
                                 " D ^DIC K DIC S DIC=DIE,X=+Y K:Y< 
                                 0 X 
               LAST EDITED:      OCT 15, 1991 
               HELP-PROMPT:      Select the category to which this 
                                 factor belongs.  
               DESCRIPTION:       This is the Health Factor that 
                                 categorizes several factors into 
                                 one group.  For instance, Non 
                                 smoker and Frequent Smoker would 
                                 have the category of Tobacco.  
  
                                 Enter the name of the Health 
                                 Factor Category.  
  
               SCREEN:           S DIC("S")="I $P(^(0),U,10)'=""F"" 
                                 "
               EXPLANATION:      Screening to prevent pointing to a 
                                  non category type factor.  
               CROSS-REFERENCE:  9999999.64^AC 
                                 1)= S ^AUTTHF("AC",$E(X,1,30),DA)= 
                                 ""
  
                                 2)= K ^AUTTHF("AC",$E(X,.04SHORT NAME          
  0;4 FREE TEXT 
  
               INPUT TRANSFORM:  K:$L(X)>10!($L(X)<2) X 
               LAST EDITED:      JUL 01, 1991 
               HELP-PROMPT:      Answer must be 2-10 characters in 
                                 length.  
               DESCRIPTION:      (Optional) This is a 'short name' 
                                 for this health factor. If 
                                 defined, it will be used on the 
                                 Health Factors Component of the 
                                 Health Summary 
  
                                 Enter a 2-5 character short name 
                                 for this health factor.  
  
  
 9999999.64,.05USE ONLY WITH SEX      0;5 SET 
  
                                 'F' FOR FEMALE; 
                                 'M' FOR MALE; 
               LAST EDITED:      JUL 01, 1991 
               DESCRIPTION:      (Optional) This is the sex that 
                                 this health factor is used for.  
  
                                 Enter an "F" for female or an "M" 
                                 for male.  
  
  
 9999999.64,.06LOWER AGE              0;6 NUMBER 
  
               INPUT TRANSFORM:  K:+X'=X!(X>99999)!(X<0)!(X?.E1"."1 
                                 N.N) X 
               LAST EDITED:      JUL 01, 1991 
               HELP-PROMPT:      Type a Number between 0 and 99999, 
                                 0 Decimal Digits 
               DESCRIPTION:      (Optional) Tmit that might apply to this 
                                 health factor.  
  
                                 Enter an age between 0 and 99999.  
  
  
 9999999.64,.07UPPER AGE              0;7 NUMBER 
  
               INPUT TRANSFORM:  K:+X'=X!(X>99999)!(X<0)!(X?.E1"."1 
                                 N.N) X 
               LAST EDITED:      JUL 01, 1991 
               HELP-PROMPT:      Type a Number between 0 and 99999, 
                                 0 Decimal Digits 
               DESCRIPTION:      (Optional) This is the upper age 
                                 limit that applies to this health 
                                 factor.  
  
                                 Enter a number between 0 and 
                                 99999.  
  
  
 9999999.64,.08DISPLAY ON HEALTH SUMMARY 0;8 SET 
  
                                 'Y' FOR YES; 
                                 'N' FOR NO; 
               LAST EDITED:      JUL 01, 1991 
               DESCRIPTION:      (Optional) This allows the health 
                                 factor to be displayed on Health 
                                 Summaries.  
  
                                 Enter a yes to display or a no to 
                                 not display.  
  
  
 9999999.64,.09SYNONYM                0;9 FREE TEXT 
  
               INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L 
                                 (X)>30!($L(X)<2) X 
               LAST EDITED:      JUL 01, 1991 
               HELP-PROMPT:      Answer must be 2-30 characters in 
                                 length.  
               DESCRIPTION:      (Optional) This this the synonym 
                                 for this health factor.  
  
                                 Enter a 3 to 30 character synonym 
                                 for this health factor.  
  
               CROSS-REFERENCE:  9999999.64^D 
                                 1)= S ^AUTTHF("D",$E(X,1,30),DA)=" 
                                 "
  
                                 2)= K ^AUTTHF("D",$E(X,1,30),DA) 
  
  
 9999999.64,.1 ENTRY TYPE             0;10 SET (Required) 
  
                                 'C' FOR CATEGORY; 
                                 'F' FOR FACTOR; 
               LAST EDITED:      OCT 15, 1991 
               HELP-PROMPT:      SMOKER or NON-SMOKER would be 
                                 FACTORS. TOBACCO would be the 
                                 Category that SMOKER and 
                                 NON-SMOKER would belong to. Are 
                                 you entering a FACTOR or a 
                                 CATEGORY ? 
               DESCRIPTION:      This is the type of health factor, 
                                 (e.g.,"F" for factor or "C" for 
                                 category).  
  
                                 Enter an "F" for factor or a "C" 
                                 for category.  
  
               CROSS-REFERENCE:  9999999.64^AD 
                                 1)= S ^AUTTHF("AD",$E(X,1,30),DA)= 
                                 ""
  
                                 2)= K ^AUTTHF("AD",$E(X,1,30),DA) 
  
  
 9999999.64,1101NOT USED WITH         11;0 POINTER Multiple #999999 
                                 9.641101 
  
               DESCRIPTION:      Some health factors are not used 
                                 with others. This is the group of 
                                 health factors that this factor is 
                                 not used with.  
  
  
 9999999.641101,.01NOT USED WITH        0;1 POINTER TO HEALTH FACTO 
                                   RS FILE (#9999999.64) 
                                    (Multiply asked) 
  
                 LAST EDITED:      JUL 01, 1991 
                 DESCRIPTION:      This is the health factor that 
                                   the health factor is not used 
                                   with.  
  
                                   Enter the name of a health 
                                   factor that is laready in this 
                                   file.  
  
                 CROSS-REFERENCE:  9999999.641101^B 
                                   1)= S ^AUTTHF(DA(1),11,"B",$E(X, 
                                   1,30),DA)="" 
  
                                   2)= K ^AUTTHF(DA(1),11,"B",$E(X, 
                                   1,30),DA) 
  
  
  
  
  
       FILES POINTED TO                      FIELDS 
  
 HEALTH FACTORS (#9999999.64)      CATEGORY (#.03) 
                                   NOT USED WITH:NOT USED WITH (#.01 
 )
  
  
 INPUT TEMPLATE(S): PX EDIT HEALTH FACTORS        JUL 20, 1995@10:26  USER
 #1217 
  
 PRINT TEMPLATE(S): CAPTIONED                                         USER #0 
  
 SORT TEMPLATE(S): 
  
 FORM(S)/BLOCK(S): 
  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Salt Lake City

NUMBER: 1294                            IA #: 1294
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9(
  DATE CREATED: AUG 15, 1995            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA 1294 ICD DIAGNOSIS
  ID: ICD9(
GLOBAL REFERENCE: ICD9(DO,0)
FIELD NUMBER: .01                       FIELD NAME: CODE NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The ICD Diagnosis Code Number.  
FIELD NUMBER: 3                         FIELD NAME: DIAGNOSIS
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The displayable text of a diagnosis. Used to display 
 text.  
FIELD NUMBER: 5                         FIELD NAME: MAJOR DIAGNOSTIC CATEGORY
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   A pointer to the MAJOR DIAGNOSTIC CATEGORY file. Used to
 group several diagnosises into groups. Used to populate PROVIDER NARRATIVE 
 CATEGORY in the V POV file.  
FIELD NUMBER: 100                       FIELD NAME: INACTIVE FLAG
  LOCATION: 0;9                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Inactive or not Flag. Used to check to see if this code
 is active.  
FIELD NUMBER: 102                       FIELD NAME: INACTIVE DATE
  LOCATION: 0;11                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   
  Date that the code became inactive. Used to check to see if the code was 
 active at the time of the visit.  
  
  
GLOBAL REFERENCE: ICD9(DO,1)
FIELD NUMBER: 10                        FIELD NAME: DESCRIPTION
  LOCATION: 1;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The Description of the Diagnosis. Used as the Provider 
 Narrative in the V POV file and is stored as text in the PROVIDER NARRATIVE
 file.  
GLOBAL REFERENCE: ICD9(AB,
 GLOBAL DESCRIPTION:   This is the "AB" cross reference.   Direct Global Read.  
GLOBAL REFERENCE: ICD9(BA,
 GLOBAL DESCRIPTION:   This is the "BA" cross reference.   Direct Global Read.  
GLOBAL REFERENCE: ICD9(D,
 GLOBAL DESCRIPTION:   This is the "D" cross reference.   Direct Global Read. 
 GENERAL DESCRIPTION:   The PCE package is requesting to look at and extract
 from several fields in the ICD DIAGNOSIS FILE (#80).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1295                            IA #: 1295
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA 1295 HOSPITAL LOCATION     ID: SC(
GLOBAL REFERENCE: SC(DO,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The name of the HOSPITAL LOCATION. Used to display to
 user and to is saved as a pointer value to this entry.  
FIELD NUMBER: 8                         FIELD NAME: STOP CODE NUMBER
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The stop code Number for this hospital location.  
FIELD NUMBER: 3                         FIELD NAME: INSTITUTION
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Used in the PCE Clinical Reports 
GLOBAL REFERENCE: SC(DO,S,D1,1,D2,0)
FIELD NUMBER: 30                        FIELD NAME: ELIGIBILITY
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The Eligibility of the patient for the visit to the
 clinic. Used as the Default Eligibility when none other is supplied by the
 user.  
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Used to finde patients entry.  
GLOBAL REFERENCE: SC(D0,S,D1,1,D2,C)
FIELD NUMBER: 303                       FIELD NAME: CHECKED OUT
  LOCATION: C:3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 309                       FIELD NAME: CHECKED-IN
  LOCATION: C;1                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   These two are used in asking the check out date/time.  
 GENERAL DESCRIPTION:   The PCE package is requesting to look at and extract
 data from the HOSPITAL LOCATION file (# 44).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany
  DATE ACTIVATED: DEC 20, 2024

NUMBER: 1296                            IA #: 1296
  DATE CREATED: AUG 15, 1995
  CUSTODIAL PACKAGE: AUTOMATED INFO COLLECTION SYS
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: IBDF18A
  NAME: DBIA 1296 GETLST~IBDF18A        ID: IBDF18A
 GENERAL DESCRIPTION:   The PCE team requests an agreement to call the
 following API.  
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
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 
               P3 := quantity (number of occurrences) 
               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
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   Used for Patient Service-getVisitTypeCptByClinic.  
  DATE ACTIVATED: APR 12, 2012

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
  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 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)="" 
  
 In cases where there is an Immunization VIS, Other Diagnosis, or Remarks, 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",V SUBFILE RECORD)=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 
   "ICR"  = V Imm Contra/Refusal Events 
              9000010.707 
   "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" 
  
 Subscript Piece:  8 Description: For Immunizations that contain VIS, Other
 Diagnosis, or 
   Remarks, this subscript will contain the Internal Entry Number (IEN) of 
   the multiple for this sub-file entry.  
  
  
  
 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
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 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP PCE EVENTS protocol 
  
 ********************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
 ********************************************************
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 10/3/23, effective with patch VPR*1*8 to document
 subscribing protocol: VPR PCE EVENTS 
  DATE ACTIVATED: SEP 19, 2016

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 EMAIL GROUP 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
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
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,9" corresponding to SC,CV,AO,IR,EC,SHAD,MST,HNC,CLV.  
  
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 
FIELD NUMBER: 9.5                       FIELD NAME: APPOINTMENT TYPE
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Pointer to Appointment Type File (#409.1) 
 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
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany
 SUBSCRIBING DETAILS:   Updated 1/12/26, effective with patch PX*1.0*250.  If
 there is an appointment associated with an encounter, PCE needs to read the
 APPOINTMENT TYPE, field 9.5.  
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
  GOOD ONLY FOR VERSION: 3.0
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1303                            IA #: 1303
  DATE CREATED: AUG 18, 1995            CUSTODIAL PACKAGE: QUALITY ASSURANCE
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: QAQAHOC*
  NAME: PAID - QAQ AD HOC REPORTS       ID: QAQAHOC*
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PAID               ISC: Hines

NUMBER: 1304                            IA #: 1304
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDAM
  NAME: SDAM                            ID: SDAM
 GENERAL DESCRIPTION:   The PCE developers request the following DBIA with the
 Scheduling developers. We are aware that these are not publicly supported
 calls and request only PRIVATE USE BY PCE.  
  
        LIST^SDAM 
  
 All calls assume you are in a List Manager(LM) environment, so appropriate LM
 variables have been initialized.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LIST~SDAM
 COMPONENT DESCRIPTION:   
  
 LIST^SDAM call: Set up appointment status type array and 
                 build appointment arrays 
   Input: 
      X        := status group you want appointment for 
      SDBEG    := begin date/time for appointment search 
      SDEND    := end date/time for appointment search 
      SDAMTYP  := [P for patient or C for clinic] 
      SDFN     := DFN  or SDCLN := Hospital Location pointer 
                    - depends on how SDAMTYP is set.  
  
   Output: 
      SDAMLIST := array of specific appointment statuses 
  
      ^TMP("SDAM",$J,<LM Line #>,0) 
              := array of appointments use for List Manager Display 
         Format: free text for display 
  
  
      ^TMP("SDAMIDX",$J,<Appt Selection #>) := 
              := raw data array elements that correspond to items on 
                 the List Manager Display array [^TMP("SDAM")] 
         Format: Piece 1: LM line # 
                 Piece 2: DFN 
                 Piece 3: date/time of appt 
                 Piece 4: Hospital Location ien 
                 Piece 5: ien to 44.003 sub-file 
                           (only set for clinic centric build) 
  
      ^TMP("SDAM",$J,"IDX", <LM Line #>, <Appt Selection #>) 
              := array indexing LM line #'s to appt selection #.  
         Format: None. (It's equal to null.) 
  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Salt Lake City

NUMBER: 1305                            IA #: 1305
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDAMBAE6
  NAME: SDAMBAE6                        ID: SDAMBAE6
 GENERAL DESCRIPTION:   The Patient Care Encounter Developers request an IA to
 call the following API.  
  
 FREE^SDAMBAE6 
  
 This API is called from an action protocol in the PCE's user interface which
 allows a user to create a stand alone stop code whithout lieaving PCE's
 Interface.  This is so the user can get their workload credit and enter
 billable data. If they were to enter this data into PCE, the data would not
 get to the Scheduling package if the visit cannot be associated with the
 appointment.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: FREE
 COMPONENT DESCRIPTION:   Inputs:    SDAMTYP="P" if calling with a patient 
            SDAMTYP="C" if you do not have a patient 
            DFN ien of a patient if SDAMTYP="P" Outputs:   NONE 
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  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
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
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
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
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
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
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
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
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
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
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany

NUMBER: 1316                            IA #: 1316
  DATE CREATED: AUG 21, 1995            CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE
  USAGE: Private                        TYPE: Other
  NAME: V MEASUREMENT FILE
 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: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Salt Lake City

NUMBER: 1317                            IA #: 1317
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDAM1
  NAME: SDAM1                           ID: SDAM1
 GENERAL DESCRIPTION:   The PCE developers request the following DBIA with the
 Scheduling developers. We are aware that these are not publicly supported
 calls and request only PRIVATE USE BY PCE.  
  
        BLD^SDAM1 
  
 This call assumes you are in a List Manager(LM) environment, so appropriate LM
 variables have been initialized.  
  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: BLD
 COMPONENT DESCRIPTION:   BLD^SDAM1 call: Build appointment arrays for patient 
   Input: 
      SDAMLIST := array of specific appointment statuses 
      SDBEG    := begin date/time for appointment search 
      SDEND    := end date/time for appointment search 
      SDFN     := DFN 
  
   Output: 
      ^TMP("SDAM",$J,<LM Line #>,0) 
              := array of appointments use for List Manager Display 
         Format: free text for display 
  
  
      ^TMP("SDAMIDX",$J,<Appt Selection #>) := 
              := raw data array elements that correspond to items on 
                 the List Manager Display array [^TMP("SDAM")] 
         Format: Piece 1: LM line # 
                 Piece 2: DFN 
                 Piece 3: date/time of appt 
                 Piece 4: Hospital Location ien 
  
      ^TMP("SDAM",$J,"IDX", <LM Line #>, <Appt Selection #>) 
              := array indexing LM line #'s to appt selection #.  
         Format: None. (It's equal to null.) 
  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Salt Lake City

NUMBER: 1318                            IA #: 1318
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDAM3
  NAME: SDAM3                           ID: SDAM3
 GENERAL DESCRIPTION:   The PCE developers request the following DBIA with the
 Scheduling developers. We are aware that these are not publicly supported
 calls and request only PRIVATE USE BY PCE.  
  
 BLD^SDAM3 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: BLD
 COMPONENT DESCRIPTION:   BLD^SDAM3 call: Build appointment arrays for clinic 
   Input: 
      SDAMLIST := array of specific appointment statuses 
      SDBEG    := begin date/time for appointment search 
      SDEND    := end date/time for appointment search 
      SDCLN    := Hospital Location pointer 
  
   Output: 
      ^TMP("SDAM",$J,<LM Line #>,0) 
              := array of appointments use for List Manager Display 
         Format: free text for display 
  
  
      ^TMP("SDAMIDX",$J,<Appt Selection #>) := 
              := raw data array elements that correspond to items on 
                 the List Manager Display array [^TMP("SDAM")] 
         Format: Piece 1: LM line # 
                 Piece 2: DFN 
                 Piece 3: date/time of appt 
                 Piece 4: Hospital Location ien 
                 Piece 5: ien to 44.003 sub-file 
  
      ^TMP("SDAM",$J,"IDX", <LM Line #>, <Appt Selection #>) 
              := array indexing LM line #'s to appt selection #.  
         Format: None. (It's equal to null.) 
  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Salt Lake City

NUMBER: 1319                            IA #: 1319
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDAMEP
  NAME: SDAMEP                          ID: SDAMEP
 GENERAL DESCRIPTION:   The PCE developers request the following DBIA with the
 Scheduling developers. We are aware that these are not publicly supported
 calls and request only PRIVATE USE BY PCE.  
  
        EN^SDAMEP 
  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   EN^SDAMEP call: Select appointment and show details
 of 
                 appointment.  
  
   Input: 
      ^TMP("SDAMIDX",$J,<Appt Selection #>) := 
              := raw data array elements that correspond to items on 
                 the List Manager Display array [^TMP("SDAM")] 
         Format: Piece 1: LM line # 
                 Piece 2: DFN 
                 Piece 3: date/time of appt 
                 Piece 4: Hospital Location ien 
                 Piece 5: ien to 44.003 sub-file 
                           (only set for clinic centric build) 
  
      ^TMP("SDAM",$J,"IDX", <LM Line #>, <Appt Selection #>) 
              := array indexing LM line #'s to appt selection #.  
         Format: None. (It's equal to null.) 
  
  
   Output: 
      None.  
  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Salt Lake City

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
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:   Added 10/23/2006. The subscribing Protocol is: SDAM
 APPOINTMENT EVENTS 
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.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (Kiosks) needs to provide real-time
 patient appointment status changes to the VetLink staff-facing module.   VPS 
 requests to add the subscribing protocol VPS SEND APPT to SDAM APPOINTMENT
 EVENTS protocol.  The VPS SEND APPT protocol will be invoked in response to
 SDAM appointment trigger events to send and HL7 message with a patients new or
 changed appointment status.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   3/2/16-Inpatient Meds has been added as a subscriber to
 ICR #1320 for the Pharmacy Interface Automation Project (PSJ*5*317). 
 Inpatient Meds is not directly calling SDAM APPOINTMENT EVENTS.  The PIA
 software is subscribing to the event driver through VAFC HL7 OUTPATIENT
 CAPTURE by adding PSJ SIU-SDAM ROUTER protocol as a subscriber to VAFC
 ADT-A08-SDAM SERVER.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP v.2.0 adds HMP APPT EVENTS protocol as an item to
 the SDAM APPOINTMENT EVENTS protocol to trigger unsolicited updates from VistA
 to JDS when appointment actions and/or activities occur. 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************

NUMBER: 1321                            IA #: 1321
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Other                           NAME: SCCV ENCOUNTER CONVERSION EVENTS
 GENERAL DESCRIPTION:   This is the event that is invoked when an encounter is
 converted as part of the Scheduling redesign.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   The subscribing protocol is: PXK CPT-SCH TO V-CPT 

NUMBER: 1322                            IA #: 1322
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA1322
  ID: SC(
GLOBAL REFERENCE: SC(clinic,"PR",
FIELD NUMBER: 2600                      FIELD NAME: PROVIDER
  ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   References to the Provider multiple of the Hospital
 Location file (44).  
              - returns list of providers for a clinic for printing on an 
                encounter form.  References ^SC(clinic,"PR", and 
                ^SC("ADPR",clinic, 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Albany
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 1323                            IA #: 1323
  DATE CREATED: AUG 24, 1995
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRHM
  NAME: Clinical Reminder/Maintenance API
  ID: PXRHM
 GENERAL DESCRIPTION:   Request permission to call the
 MAIN^PXRHM(DFN,AGE,SEX,PXRITEM,PXRHM) entry point to retrieve Clinical
 Reminder/Maintenance data generated by the PCE PACKAGE. Listed below is the
 details on accessing this entry point and the data that should be returned.  
  
 MAIN(DFN,AGE,SEX,PXRITEM,PXRHM) 
  
 INPUT:     DFN     - Pointer to Patient File (#2) 
            AGE     - Age of patient 
            SEX     - Sex of patient 
            PXRITEM - Internal entry of PCE Reminder/Maintenance Item 
            PXRHM   - Flag to indicate level of information needed 
                          1 - Health Maintenance 
                          0 - Reminders DUE NOW only OUTPUT: Data found related
 to the PCE Reminder/Maintenance Item (811.9) file 
  
 ^TMP("PXRHM",$J,PXRITEM,"Reminder Item Text"="DUE NOW" or null 
      ^ date due (Internal FM Date) ^ Last activity date (Internal FM date) 
  
 Note: The following items are only returned if PXRHM = 1.  
  
 If activity was found in files related to the reminder/maintenance item: 
 ^TMP("PXRHM",$J,PXRITEM,"Reminder Item Text",inverted FM date of activity)= 
      Type of data^Internal FM date of activity^Name of activity 
  
 If there is text to describe the reminder/maintenance criteria: 
 ^TMP("PXRHM",$J,PXRITEM,"Reminder Item Text","TXT",1 to N)= 
      Text about rule and patient findings 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MAIN(DFN,AGE,SEX,PXRITEM,PXRHM)
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

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
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
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
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
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
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
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
COMPONENT/ENTRY POINT: OPTION GMRA PATIENT A/AR EDIT
 COMPONENT DESCRIPTION:   Enter/Edit Patient Reaction Data menu option.  
SUBSCRIBING PACKAGE: DIETETICS          ISC: Hines

NUMBER: 1334                            IA #: 1334
  DATE CREATED: SEP 11, 1995            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: DGYACPT
  NAME: CPT CODE/MODIFIERS              ID: DGYACPT
 GENERAL DESCRIPTION:   This a function which will return a 1/0 value,
 indicating either the modifier can be used with the CPT code or not.  If a
 modifier is not passed in the 1/0 value will relate to whether the code passed
 is a valid CPT code.  There are two functions within the routine.  
  
 MODE(CODE,MOD)  ; Returns 1/0 if modifier can be used with code 
         ;
         ;  Input:    CODE = CPT code (external format) 
         ;             MOD = CPT modifier [Optional] (external format) 
         ; Output:     0/1 = 0 cannot be used with code 
         ;                   0 not a valid CPT code if modifier not passed in 
         ;                   1 can be used with code 
         ;                   1 a valid CPT code if modifier not passed in 
 MODI(CODE,MOD)  ; Returns 1/0 if modifier can be used with code 
         ;
         ;  Input:    CODE = CPT code (internal format) 
         ;             MOD = CPT modifier [Optional] (internal format) 
         ; Output:     0/1 = 0 cannot be used with code 
         ;                   0 not valid CPT code if modifier not passed in 
         ;                   1 can be used with code 
         ;                   1 valid CPT code if modifier not passed in 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MODE(CPT CODE,MODIFIER)
 COMPONENT DESCRIPTION:   Input:    CODE = CPT code (external format) 
            MOD = CPT modifier [Optional] (external format) 
  
COMPONENT/ENTRY POINT: MODI(CPT CODE,MODIFIER)
 COMPONENT DESCRIPTION:   Input:    CODE = CPT code (internal format) 
            MOD = CPT modifier [Optional] (internal format) 
  

NUMBER: 1335                            IA #: 1335
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA1335
  ID: SC(
GLOBAL REFERENCE: SC(ifn,99)
FIELD NUMBER: 99                        FIELD NAME: TELEPHONE
  LOCATION: 99;1                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The TELEPHONE field #99 contains the phone number of the
 hospital location.  
 GLOBAL DESCRIPTION:   This field is used to find the telephone number of the
 hospital location.  
GLOBAL REFERENCE: SC(ifn,I)
FIELD NUMBER: 2505                      FIELD NAME: INACTIVATE DATE
  LOCATION: I;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the date the location was
 inactivated.  
FIELD NUMBER: 2506                      FIELD NAME: REACTIVATE DATE
  LOCATION: I;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the date the location was
 reactivated.  
 GLOBAL DESCRIPTION:   Radiology/Nuclear Medicine uses this field to determine
 whether a hospital location is a valid, active entry.  
GLOBAL REFERENCE: SC(ifn,SL)
FIELD NUMBER: 1916                      FIELD NAME: PRINCIPAL CLINIC
  LOCATION: SL;5                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains a pointer to the principal clinic for
 the hospital location entry.  
 GLOBAL DESCRIPTION:   Radiology/Nuclear Medicine uses this field to populated
 the principal clinic field of our exam record.  
 GENERAL DESCRIPTION:   This DBIA documents references made by the
 Radiology/Nuclear Medicine package to fields in the Hospital Location file
 #44.  The references are global reads.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  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
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
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  ISC: Hines
SUBSCRIBING PACKAGE: QUASAR             ISC: Birmingham
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany
 SUBSCRIBING DETAILS:   DSS EXTRACTS reads only the NAME field (#.01) and the
 SERVICE field (#3) using FileMan (EN^DIQ1).  

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
  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

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
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
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
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
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
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
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: 1347                            IA #: 1347
  DATE CREATED: APR 25, 1996            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  NAME: CONTRACT NURSING HOME           STATUS: Withdrawn

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
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
SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST
  ISC: Washington/Silver Spring

NUMBER: 1350                            IA #: 1350
  FILE NUMBER: 356                      GLOBAL ROOT: IBT(356
  DATE CREATED: SEP 21, 1995            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA1350
  ID: IBT(356
GLOBAL REFERENCE: IBT(356,'ADIS',DATE,
FIELD NUMBER: .01                       FIELD NAME: ENTRY ID
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is used as the .01 field in the IBQ File
 (#538).  
FIELD NUMBER: .02                       FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is directly accessed to further return 
 demographics from the PATIENT File (#2).  
FIELD NUMBER: .05                       FIELD NAME: ADMISSION
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field (patient movement) is directly accessed to
 return information in other files which use the PATIENT MOVEMENT as a entry
 number.  
FIELD NUMBER: .18                       FIELD NAME: EVENT TYPE
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is directly accessed and used to check the
 reviews validity.  
FIELD NUMBER: .2                        FIELD NAME: INACTIVE
  LOCATION: 0;20                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is directly accessed for use in checking
 reviews validity.  
FIELD NUMBER: .25                       FIELD NAME: TRACKED AS RANDOM SAMPLE?
  LOCATION: 0;25                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is used as part of the Enrollment Code in the
 IBQ package.  
FIELD NUMBER: .26
  FIELD NAME: TRACKED AS SPECIAL CONDITION?
  LOCATION: 0;26                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is used as part of the Enrollment Code in the
 IBQ package.  
FIELD NUMBER: .27                       FIELD NAME: TRACKED AS LOCAL ADDITION?
  LOCATION: 0;27                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is used as part of the Enrollment Code in the
 IBQ package.  
FIELD NUMBER: 1.09                      FIELD NAME: ACUTE CARE DISCHARGE DATE
  LOCATION: 1;9                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is used for ACUTE CARE DISCHARGE DATE in the
 IBQ package.  
 GLOBAL DESCRIPTION:   The 'ADIS' x-ref is used as the center point
 (discharges) to most lookups for patient reporting in the IBQ package.  
 GENERAL DESCRIPTION:   The IBQ package needs to retrieve information from the
 Claims Tracking File (#356) for rollup to the National Database.  The "ADIS"
 x-ref is used to gather discharged patients from the Claims Tracking File
 (#356) for use in IBQ.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP
  ISC: Albany

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
SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP
  ISC: Albany

NUMBER: 1352                            IA #: 1352
  FILE NUMBER: 356.94                   GLOBAL ROOT: IBT(356.94
  DATE CREATED: SEP 21, 1995            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA1352
  ID: IBT(356.94
GLOBAL REFERENCE: IBT(356.94,'C',DGPM,
FIELD NUMBER: .03                       FIELD NAME: PROVIDER
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is used to return the Providers number for use
 in the IBQ package.  
FIELD NUMBER: .04                       FIELD NAME: TYPE PROVIDER
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is used to determine the fields used in the
 IBQ package for Admitting, Attending, and Resident providers.  
 GLOBAL DESCRIPTION:   The 'C' x-ref is used to retrieve patient provider
 information related to the PATIENT MOVEMENT of the patient.  
 GENERAL DESCRIPTION:   The IBQ package needs to retrieve the providers from
 the INPATIENT PROVIDER File (#356.94) that correspond to the patient's Claims
 Tracking information.  The 'C' x-ref is used to retrieve the patient's
 providers, given the PATIENT MOVEMENT number.  PATIENT MOVEMENT is retrieved
 in IA 1350 using the ADMISSION field from File (#356).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP
  ISC: Albany

NUMBER: 1353                            IA #: 1353
  FILE NUMBER: .402                     GLOBAL ROOT: DIE(
  DATE CREATED: SEP 21, 1995            CUSTODIAL PACKAGE: 1
  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
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
SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP
  ISC: Albany

NUMBER: 1355                            IA #: 1355
  FILE NUMBER: .4                       GLOBAL ROOT: DIPT(
  DATE CREATED: SEP 21, 1995            CUSTODIAL PACKAGE: 1
  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
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  ISC: Hines

NUMBER: 1356                            IA #: 1356
  FILE NUMBER: 356.4                    GLOBAL ROOT: IBE(356.4
  DATE CREATED: SEP 21, 1995            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA1356
  ID: IBE(356.4
GLOBAL REFERENCE: IBE(356.4,IEN,0
FIELD NUMBER: .02                       FIELD NAME: CODE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is directly accessed to return a readable,
 external code used for the Reason fields in the IBQ package.  
 GENERAL DESCRIPTION:   The IBQ package needs to retrieve the external codes in
 the CLAIMS TRACKING NON-ACUTE CLASSIFICATION File (#356.4).  Internal entry
 numbers of codes to convert come from the REASON fields in the Hospital Review 
 File (#356.1).  Refer to IA-1351 for use of the REASON fields in the IBQ 
 package.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP
  ISC: Albany

NUMBER: 1357                            IA #: 1357
  FILE NUMBER: 356.3                    GLOBAL ROOT: IBE(356.3
  DATE CREATED: SEP 21, 1995            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA1357
  ID: IBE(356.3
GLOBAL REFERENCE: IBE(356.3,IEN,0)
FIELD NUMBER: .03                       FIELD NAME: CODE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is directly accessed to return a readable,
 external code used for Severity of Illness and Intensity of Service in the IBQ
 package.  
 GENERAL DESCRIPTION:   The IBQ package needs to retrieve the external codes
 found in the CLAIMS TRACKING SI/IS CATEGORIES File (#356.3).  Internal entry
 number of codes to convert come from the SI and IS fields in the HOSPITAL
 REVIEW File (#356.1).  Refer to IA-1351 for use of the SI and IS fields in the
 IBQ package.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP
  ISC: Albany

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
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
SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP
  ISC: Albany
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be referencing the Name (#.01) field in the
 Facility Treating Specialty (#45.7) file in VIAB BMS RPC.  

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
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
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
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
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
 SUBSCRIBING DETAILS:   Added 3/10/20: Vitals patch GMRV*5*40 needs to generate
 a new alert.  

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
  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
  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
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 "C" or "S" or 
              "L" or "", if problem is related to exposure to 
              Agnet Orange, Ionization, Persian Gulf, Head 
              and/or Neck Cancer, Militery Sexual Trauma, 
              Combat Vet. SHAD, Camp Lejeune 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 "C" or "S" or 
              "L" or "", if problem is related to exposure to 
              Agent Orange, Ionization, Persian Gulf Head 
              and/or Neck Cancer, Military Sexual Trauma, 
              Combat Vet, SHAD, Camp Lejeune 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
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be referencing the DSELECT^GMPLENFM API in
 VIAB ACTPROB RPC.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 12/12/22 effective with SD*5.3*828 to reference
 the DSELECT^GMPLENFM API in the SDES PCESAVE RPC.  

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
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
 GENERAL DESCRIPTION:   APIs and extrinsic functions that can be used to
 control the Security Key File.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SECURITY KEYS
KEYWORDS: KEYS
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 Internal
 Entry Number (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.  
VARIABLES: key_value                    TYPE: Input
 VARIABLES DESCRIPTION:   Security Key name or Internal Entry Number (IEN).  
VARIABLES: value                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns either the Security Key name or IEN,
 depending on the Input variable key_value.  
COMPONENT/ENTRY POINT: DEL
 COMPONENT DESCRIPTION:   Usage:  D DEL^XPDKEY(key_ien) 
  
 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_ien                      TYPE: Input
 VARIABLES DESCRIPTION:   The Internal Entry Number (IEN) of the Security Key
 to delete.  
  DATE ACTIVATED: MAR 12, 2008

NUMBER: 1368                            IA #: 1368
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: OE/RR conversion needs recent/future appts
  ID: SC(
GLOBAL REFERENCE: SC(IEN,'S',DATE
 GLOBAL DESCRIPTION:   Loops through ^SC(ien,"S",date to get patients with
 appointments in all clinics within a date range (date range is from 30 days
 before installation to 30 days after installation).  
GLOBAL REFERENCE: SC(IEN,'S',DATE,1,APPTIEN)
 GLOBAL DESCRIPTION:   Loops through appointments within clinic at specific
 date/time.  
GLOBAL REFERENCE: SC(IEN,'S',DATE,1,APPTIEN,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This will allow us to retrieve the PATIENT file pointer
 for appts within the date range.  We use this to pass to the orders conversion
 process.  This ensures patients who were recently seen (or who will be seen in
 the near future) get their orders converted as early as possible in the 
 process.  
 GENERAL DESCRIPTION:   We would like permission for the OE/RR version 3.0
 orders conversion to loop through appointments in the HOSPITAL LOCATION file. 
 It will loop through appointments within 30 days of the conversion run date
 (+/-).  
  STATUS: Retired
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

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
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: 1
  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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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                            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: PRINCIPAL DX
  LOCATION: 70;10                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 80                        FIELD NAME: PRINCIPAL DX PRE 1986
  LOCATION: 70;11                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.16                     FIELD NAME: SECONDARY DX 1
  LOCATION: 70;16                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.17                     FIELD NAME: SECONDARY DX 2
  LOCATION: 70;17                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.18                     FIELD NAME: SECONDARY DX 3
  LOCATION: 70;18                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.19                     FIELD NAME: SECONDARY DX 4
  LOCATION: 70;19                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.201                    FIELD NAME: SECONDARY DX 5
  LOCATION: 70;20                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.21                     FIELD NAME: SECONDARY DX 6
  LOCATION: 70;21                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.22                     FIELD NAME: SECONDARY DX 7
  LOCATION: 70;22                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.23                     FIELD NAME: SECONDARY DX 8
  LOCATION: 70;23                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.24                     FIELD NAME: SECONDARY DX 9
  LOCATION: 70;24                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.33
  FIELD NAME: TRT FOR ACUTE SUICIDAL CRISIS
  LOCATION: 70;33                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The TRT FOR ACUTE SUICIDAL CRISIS field indicates whether
 the given PTF is associated with an Acute Suicidal Crisis for COMPACT Act
 purposes.  
GLOBAL REFERENCE: DGPT(D0,P,0)
FIELD NUMBER: 60                        FIELD NAME: 601
  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
FIELD NUMBER: 9                         FIELD NAME: PROCEDURE CODE 6
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: PROCEDURE CODE 7
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: PROCEDURE CODE 8
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 12                        FIELD NAME: PROCEDURE CODE 9
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 13                        FIELD NAME: PROCEDURE CODE 10
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: PROCEDURE CODE 11
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: PROCEDURE CODE 12
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: PROCEDURE CODE 13
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 17                        FIELD NAME: PROCEDURE CODE 14
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 18                        FIELD NAME: PROCEDURE CODE 15
  LOCATION: 0;19                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 19                        FIELD NAME: PROCEDURE CODE 16
  LOCATION: 0;20                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 20                        FIELD NAME: PROCEDURE CODE 17
  LOCATION: 0;21                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 21                        FIELD NAME: PROCEDURE CODE 18
  LOCATION: 0;22                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 22                        FIELD NAME: PROCEDURE CODE 19
  LOCATION: 0;23                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 23                        FIELD NAME: PROCEDURE CODE 20
  LOCATION: 0;24                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPT(D0,S,0)
FIELD NUMBER: 40                        FIELD NAME: 401
  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
FIELD NUMBER: 13                        FIELD NAME: OPERATION CODE 6
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: OPERATION CODE 7
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: OPERATION CODE 8
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: OPERATION CODE 9
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 17                        FIELD NAME: OPERATION CODE 10
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 18                        FIELD NAME: OPERATION CODE 11
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 19                        FIELD NAME: OPERATION CODE 12
  LOCATION: 0;19                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 20                        FIELD NAME: OPERATION CODE 13
  LOCATION: 0;20                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 21                        FIELD NAME: OPERATION CODE 14
  LOCATION: 0;21                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 22                        FIELD NAME: OPERATION CODE 15
  LOCATION: 0;22                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 23                        FIELD NAME: OPERATION CODE 16
  LOCATION: 0;23                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 24                        FIELD NAME: OPERATION CODE 17
  LOCATION: 0;24                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 25                        FIELD NAME: OPERATION CODE 18
  LOCATION: 0;25                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 26                        FIELD NAME: OPERATION CODE 19
  LOCATION: 0;26                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 27                        FIELD NAME: OPERATION CODE 20
  LOCATION: 0;27                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPT('B',DFN,PTF)
 GLOBAL DESCRIPTION:   DIRECT GLOBAL READ 
GLOBAL REFERENCE: DGPT(D0,71)
FIELD NUMBER: 79.241                    FIELD NAME: SECONDARY DX 10
  LOCATION: 71;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.242                    FIELD NAME: SECONDARY DX 11
  LOCATION: 71;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.243                    FIELD NAME: SECONDARY DX 12
  LOCATION: 71;3                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.244                    FIELD NAME: SECONDARY DX 13
  LOCATION: 71;4                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.245                    FIELD NAME: SECONDARY DX 14
  LOCATION: 71;5                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.246                    FIELD NAME: SECONDARY DX 15
  LOCATION: 71;6                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.247                    FIELD NAME: SECONDARY DX 16
  LOCATION: 71;7                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.248                    FIELD NAME: SECONDARY DX 17
  LOCATION: 71;8                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.249                    FIELD NAME: SECONDARY DX 18
  LOCATION: 71;9                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.2491                   FIELD NAME: SECONDARY DX 19
  LOCATION: 71;10                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.24911                  FIELD NAME: SECONDARY DX 20
  LOCATION: 71;11                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.24912                  FIELD NAME: SECONDARY DX 21
  LOCATION: 71;12                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.24913                  FIELD NAME: SECONDARY DX 22
  LOCATION: 71;13                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.24914                  FIELD NAME: SECONDARY DX 23
  LOCATION: 71;14                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 79.24915                  FIELD NAME: SECONDARY DX 24
  LOCATION: 71;15                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPT(D0,'P',D1,1)
FIELD NUMBER: 24                        FIELD NAME: PROCEDURE CODE 21
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 25                        FIELD NAME: PROCEDURE CODE 22
  LOCATION: 1;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 26                        FIELD NAME: PROCEDURE CODE 23
  LOCATION: 1;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 27                        FIELD NAME: PROCEDURE CODE 24
  LOCATION: 1;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 28                        FIELD NAME: PROCEDURE CODE 25
  LOCATION: 1;5                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPT(D0,'S',D1,1)
FIELD NUMBER: 28                        FIELD NAME: OPERATION CODE 21
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 29                        FIELD NAME: OPERATION CODE 22
  LOCATION: 1;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 30                        FIELD NAME: OPERATION CODE 23
  LOCATION: 1;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 31                        FIELD NAME: OPERATION CODE 24
  LOCATION: 1;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 32                        FIELD NAME: OPERATION CODE 25
  LOCATION: 1;5                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The health summary packages needs the ability to access
 PTF data to display in several of the health summary components.  
  
 NOTE: Existing subscribers to this ICR are grandfathered in for accessing PTF
 (#45) Diagnosis, Procedure code, and Surgical code data fields.  However,
 current subscribers are encouraged to use ICR 6130 in the future.  ICR 6130
 supports the use of PTF Utility API's to access PTF (#45) Diagnosis, Present
 on Admission (POA) indicators, Procedure code, and Surgical code fields,
 instead of accessing fields directly or using Fileman.  New subscribers should
 not be added to this ICR if PTF (#45) file data fields may be obtained using
 the PTF Utility API's supported by ICR 6130.  
  
 Revision History: 
  -  8/21/24: Added 79.33 field to GLOBAL REFERENCE ^DGPT(D0,70) effective with
 PX*1.0*241 
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
KEYWORDS: PTF
KEYWORDS: DGPT
KEYWORDS: COMPACT ACT
KEYWORDS: ACUTE SUICIDAL CRISIS
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Birmingham
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany
 SUBSCRIBING DETAILS:   
  8/21/24 - added 79.33 field to GLOBAL REFERENCE ^DGPT(D0,70) effective 
  with patch PX*1.0*241 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
  DATE ACTIVATED: SEP 18, 2015

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
SUBSCRIBING PACKAGE: HEALTH LEVEL SEVEN
  ISC: Albany
SUBSCRIBING PACKAGE: VISTA DATA EXTRACTION FRAMEWORK
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 

NUMBER: 1374                            IA #: 1374
  DATE CREATED: OCT 18, 1995
  CUSTODIAL PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PPPPDA1
  NAME: DBIA1030-D                      ID: PPPPDA1
 GENERAL DESCRIPTION:   This function determines if the patient has been to
 other hospitals and whether there is any prescription information in the PDX
 data file for the patient.  If there is data, the user is given the option to
 view it.  Prescrition Practices is not required.  A check is done for the 
 existance of the routine PPPPDA1.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$PDA(PSODFN)
VARIABLES: PSODFN                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number of the patient. 
 This variable will be passed in using parameter passing and will retain its
 value upon return from PPPPDA1.  
VARIABLES: $$PDA                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns one of three values: 
     0 - Normal Termination -9001 - Input Parameter Format Error -9003 -
 Invalid Patient DFN 
SUBSCRIBING PACKAGE: VENDOR - AUDIOFAX, INC.
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 1375                            IA #: 1375
  DATE CREATED: NOV 07, 1995            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: DGACT
  NAME: DGACT                           ID: DGACT
 GENERAL DESCRIPTION:   This function will determine if a treating specialty
 entry is active or inactive in either the SPECIALTY (#42.4) file or the
 FACILITY TREATING SPECIALTY (#45.7) file.  The function will return a 1 if the
 treating specialty is active or 0 otherwise.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$ACTIVE(FILE,IEN,DGDT)
 COMPONENT DESCRIPTION:   
      Input:  -- FILE to determine if checking SPECIALTY file (#42.4) 
                 or FACILITY TREATING SPECIALTY file (#45.7) 
              -- IEN as the internal entry number of treating specialty 
              -- DGDT as 'as of' date (uses DT if undefined) 
  
      Output: -- 1 if active, 0 otherwise 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   File number of SPECIALTY file (#42.4) or FACILITY
 TREATING SPECIALTY file (#45.7).  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of treating specialty.  
VARIABLES: DGDT                         TYPE: Used
 VARIABLES DESCRIPTION:   'As of' date (uses DT if not defined).  

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
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,
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
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 
  DATE ACTIVATED: JUL 10, 2009

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
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 

NUMBER: 1379                            IA #: 1379
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19,
  DATE CREATED: NOV 07, 1995            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: OPTION FILE
  ID: DIC(19,
GLOBAL REFERENCE: DIC(19,D0,0)
FIELD NUMBER: 2                         FIELD NAME: OUT OF ORDER MESSAGE
  LOCATION: 0;3                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: DIC(19,'B',
 GLOBAL DESCRIPTION:   Direct global read on the "B" cross-reference.  
 GENERAL DESCRIPTION:   This integration agreement is only for Nursing V3.0,
 Vitals/Measurements 3.0 and Intake/Output 3.0.  
  
 Permission to access the "B" xref on the option file.  
  
 Persmission to set the OUT OF ORDER field in file 19 using ^DIE.  
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 3.0
SUBSCRIBING PACKAGE: NURSING SERVICE    ISC: Hines
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  ISC: Hines
SUBSCRIBING PACKAGE: INTAKE/OUTPUT      ISC: Hines

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
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
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Inpatient Meds added for the PharmacyInterface
 Automation (PIA) project and patch PSJ*5*317.  
  
 The project involves sending Inpatient order information to Pharmacy Automated
 Dispensing Equipment (PADE) cabinets placed in wards. The setup allows to
 assign room beds under a group and the location (send area) of the PADE
 cabinets that holds the medications where the orders needs to be sent for
 those patients.  Within our setup, we store the IENs of these room beds and we
 scan the B x-ref of 405.4 to ensure they exist when we send the orders to the
 respective PADE cabinets.  

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
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************

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
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 

NUMBER: 1383                            IA #: 1383
  FILE NUMBER: 120.52                   GLOBAL ROOT: GMRD(120.52,
  DATE CREATED: NOV 07, 1995
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: GMRV VITAL SITE
  ID: GMRD(120.52,
GLOBAL REFERENCE: GMRD(120.52,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.  
GLOBAL REFERENCE: GMRD(120.52,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: VITAL TYPE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Nursing has permission to access the following fields
 in the GMRV Vital Site (120.52) file.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NURSING SERVICE    ISC: Hines

NUMBER: 1384                            IA #: 1384
  FILE NUMBER: 120.53                   GLOBAL ROOT: GMRD(120.53,
  DATE CREATED: NOV 07, 1995
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: GMRV VITAL SITE
  ID: GMRD(120.53,
GLOBAL REFERENCE: GMRD(120.53,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This DBIA also allows Nursing to LAYGO to this file using
 FileMan.  
GLOBAL REFERENCE: GMRD(120.53,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: VITAL TYPE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Nursing has permission to access the following fields
 in the GMRV Vital Site (120.53) file.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NURSING SERVICE    ISC: Hines

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
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
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
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
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
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
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
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
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
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
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
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
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
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: 1398                            IA #: 1398
  FILE NUMBER: 452                      GLOBAL ROOT: PRSE(452,
  DATE CREATED: APR 21, 1997            CUSTODIAL PACKAGE: EDUCATION TRACKING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PRSE STUDENT EDUCATION TRACKING
  ID: PRSE(452,
GLOBAL REFERENCE: PRSE(452,D0,
FIELD NUMBER: .01                       FIELD NAME: STUDENT NAME
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PROGRAM/CLASS TITLE
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2.1
  FIELD NAME: PRSE PROGRAM/CLASS LENGTH HRS
  LOCATION: 0;16                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2.4                       FIELD NAME: PROGRAM/CLASS SUPPLIER
  LOCATION: 6;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PROGRAM/CLASS CATEGORY
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: TYPE OF EDUCATION
  LOCATION: 0;21                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: CONTACT HOURS
  LOCATION: 0;10                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 9.1                       FIELD NAME: C.E.U.s
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 12                        FIELD NAME: SERVICE/SECTION
  LOCATION: 0;13                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 13                        FIELD NAME: ENDING DATE
  LOCATION: 0;14                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 13.5                      FIELD NAME: PROGRAM/CLASS LOCATION
  LOCATION: 0;15                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: LOCAL NON-LOCAL
  LOCATION: 6;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: HOURS A/A REQUESTED
  LOCATION: 0;17                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 17                        FIELD NAME: HOURS A/A GRANTED
  LOCATION: 0;18                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 20                        FIELD NAME: ROUTINE/NON-ROUTINE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 77                        FIELD NAME: C.E.U. COMMENTS
  LOCATION: 5;0                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is a word processing field which expands into the
 ^PRSE(452,D0,5, global reference.  
 GLOBAL DESCRIPTION:   Also the following cross-references on the PRSE Student
 Education Tracking are permitted to be accessed: 
  
    Xref    Type of Access 
    ----    --------------
    AA      Direct global read/write 
    AK      Direct global read/write 
    AL      Direct global write 
    B       Direct global read/write 
    CAT     Direct global write 
    CLAS    Direct global write 
    CLS     Direct global write 
    DAT     Direct global write 
    G       Direct global read/write 
    H       Direct global write 
    SER     Direct global write 
    SOR     Direct global write 
  
  
 Also supported are direct global reads of the ^PRSE(452,D0,0) and 
 ^PRSE(452,D0,6) node, as well as direct global read/write of the ^PRSE(452,0)
 node.  
GLOBAL REFERENCE: PRSE(452,D0,3,D1,
FIELD NUMBER: .01                       FIELD NAME: FUNDS REQUESTED
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: AMOUNT REQUESTED
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
 GLOBAL DESCRIPTION:   Also supported is direct global reads on
 ^PRSE(452,D0,3,D1) to $Order through the multiple, direct global reads/writes
 of the ^PRSE(452,D0,3,0) node, direct global reads of ^PRSE(452,D0,3,D1,0),
 and direct global reads of the "B" cross-reference of the Funds Requested
 sub-file.  
GLOBAL REFERENCE: PRSE(452,D0,4,D1,
FIELD NUMBER: .01                       FIELD NAME: FUNDS AUTHORIZED
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: AMOUNT AUTHORIZED
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
 GLOBAL DESCRIPTION:   Also supported is direct global reads on
 ^PRSE(452,D0,4,D1) to $Order through the multiple, direct global read/write on
 the ^PRSE(452,D0,4,0) node, direct global reads of the ^PRSE(452,D0,4,D1,0)
 node, and direct global reads of the "B" cross-reference on the Funds
 Authorized sub-file.  
GLOBAL REFERENCE: PRSE(452,D0,1,D1,
FIELD NUMBER: 8                         FIELD NAME: OBJECTIVES
  ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Also supported is direct global reads on
 ^PRSE(452,D0,1,D1) to $Order through this word processing multiple and direct
 global reads on the nodes (i.e., PRSE(452,D0,1,DA,0)) that make up the lines
 of this word processing multiple.  
 GENERAL DESCRIPTION:   Nursing has permission to access the PRSE Student
 Education Tracking (452) fields as described in this DBIA.  
  STATUS: Other                         DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NURSING SERVICE    ISC: Hines

NUMBER: 1399                            IA #: 1399
  FILE NUMBER: 452.1                    GLOBAL ROOT: PRSE(452.1,
  DATE CREATED: FEB 14, 1997            CUSTODIAL PACKAGE: EDUCATION TRACKING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PRSE PROGRAM/CLASS              ID: PRSE(452.1,
GLOBAL REFERENCE: PRSE(452.1,D0,
FIELD NUMBER: .01                       FIELD NAME: PROGRAM CLASS/TITLE
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2
  FIELD NAME: PRSE PROGRAM/CLASS LENGTH HRS
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: REQUIRED FREQUENCY
  LOCATION: 0;6                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: TYPE OF EDUCATION
  LOCATION: 0;7                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: SERVICE
  LOCATION: 0;8                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: OPEN/CLOSED
  LOCATION: 0;9                         ACCESS: Direct Global R/W & w/Fileman
 GLOBAL DESCRIPTION:   Also supported are direct global read/writes to the
 ^PRSE(452.1,0) node, direct global read/writes on the "B" and "C"
 cross-references of the PRSE Program/Class file, and direct global read of the
 ^PRSE(452.1,D0,0) node.  
 GENERAL DESCRIPTION:   Nursing has permission to access the PRSE Program/Class
 fields specified in this DBIA.  
  STATUS: Other                         DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NURSING SERVICE    ISC: Hines

NUMBER: 1400                            IA #: 1400
  FILE NUMBER: 452.3                    GLOBAL ROOT: PRSE(452.3,
  DATE CREATED: FEB 14, 1997            CUSTODIAL PACKAGE: EDUCATION TRACKING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PRSE MANDATORY TRAINING (MI) CLASS GROUP
  ID: PRSE(452.3,
GLOBAL REFERENCE: PRSE(452.3,D0,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: SERVICE
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
 GLOBAL DESCRIPTION:   Also included are direct global read/write of the
 ^PRSE(452.3,0) node, direct global read/write of the "B" cross-reference of
 the 452.3 file, and direct global write of the "D" cross-reference of the
 452.3 file.  
GLOBAL REFERENCE: PRSE(452.3,D0,1,D1,
FIELD NUMBER: .01                       FIELD NAME: MANDATORY CLASSES
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
 GLOBAL DESCRIPTION:   Also included here are direct global read/write of the
 ^PRSE(452.3,D0,1,0) node, direct global read/write of the "B" cross-reference
 of the Mandatory Classes sub-file, and direct global write of the "C"
 cross-reference of the Mandatory Classes sub-file.  
 GENERAL DESCRIPTION:   Nursing has permission to access the PRSE Mandatory
 Training (MI) Class Group file fields described in this DBIA.  
  STATUS: Other                         DURATION: Till Otherwise Agreed
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
SUBSCRIBING PACKAGE: NURSING SERVICE    ISC: Hines

NUMBER: 1402                            IA #: 1402
  FILE NUMBER: 450                      GLOBAL ROOT: PRSPC(
  DATE CREATED: FEB 14, 1997            CUSTODIAL PACKAGE: PAID
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PAID EMPLOYEE                   ID: PRSPC(
GLOBAL REFERENCE: PRSPC(D0,
FIELD NUMBER: .01                       FIELD NAME: EMPLOYEE NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: SSN
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 27                        FIELD NAME: SALARY DATE
  LOCATION: 0;28                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 28                        FIELD NAME: SALARY
  LOCATION: 0;29                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 80                        FIELD NAME: SEPARATION IND
  LOCATION: 1;33                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 458                       FIELD NAME: COST CENTER/ORGANIZATION
  LOCATION: 0;49                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 30                        FIELD NAME: SERVICE COMPUTATION DATE
  LOCATION: 0;31                        ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Also included here are direct global reads of the "ACC"
 and "SSN" cross-references of the PAID Employee file, and direct global reads
 of the ^PRSPC(D0,0) and ^PRSPC(D0,1) nodes.  
GLOBAL REFERENCE: PRSPC(D0,5,D1,
FIELD NUMBER: .01                       FIELD NAME: MI REVIEW GROUP
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DATE ASSIGNED
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
 GLOBAL DESCRIPTION:   Also included here are direct global read/write of the
 "B" cross-reference of the MI Review Group sub-file, direct global read/write
 of the ^PRSPC(D0,5,0) node, direct global read of ^PRSPC(D0,5,D1) to loop
 through the multiple, and direct global read of the ^PRSPC(D0,5,D1,0) node.  
GLOBAL REFERENCE: PRSPC(D0,6,D1,
FIELD NUMBER: .01                       FIELD NAME: MANDATORY CLASS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DATE ASSIGNED
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Also included here are direct global reads of
 ^PRSPC(D0,6,D1) to $Order thorugh the multiple and direct global read of the
 ^PRSPC(D0,6,D1,0) node.  
 GENERAL DESCRIPTION:   Nursing has permission to access the PAID Employee file
 fields as described in this DBIA.  
  STATUS: Other                         DURATION: Till Otherwise Agreed
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
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
SUBSCRIBING PACKAGE: NURSING SERVICE    ISC: Hines

NUMBER: 1405                            IA #: 1405
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100,
  DATE CREATED: NOV 08, 1995
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: ORDER
  ID: OR(100,
GLOBAL REFERENCE: OR(100,'AO',
 GLOBAL DESCRIPTION:   Direct global read is allowed on the "AO"
 cross-reference of the Order (100) file.  
 GENERAL DESCRIPTION:   Vitals/Measurements has permission to access the Order
 (100) file as described in this DBIA.  This agreement shall be only valid for
 V2.5 of the Order Entry package.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  ISC: Hines

NUMBER: 1406                            IA #: 1406
  FILE NUMBER: 3.6                      GLOBAL ROOT: XMB(3.6,
  DATE CREATED: NOV 08, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: BULLETIN
  ID: XMB(3.6,
GLOBAL REFERENCE: XMB(3.6,D0,
 GLOBAL DESCRIPTION:   Direct global read access of the "B" cross-reference on
 the Bulletin file is supported.  
  
 Killing entries in the Bulletin file using ^DIK.  
 GENERAL DESCRIPTION:   Nursing has permission to access the Bulletin (3.6)
 file as described in this DBIA.  
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 3.0
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
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: 1408                            IA #: 1408
  DATE CREATED: FEB 19, 1997            CUSTODIAL PACKAGE: EDUCATION TRACKING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PRSEUTL5                     NAME: PRSEUTL5
  ID: PRSEUTL5
 GENERAL DESCRIPTION:   Nursing can use the PRSEUTL5 utility as described in
 this DBIA.  
  STATUS: Other                         DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN1(PRSED0)
 COMPONENT DESCRIPTION:   This component will take the current MI review groups
 assigned to a PAID Employee (450) file entry and update the Mandatory Class
 multiple for that record.  
VARIABLES: PRSED0                       TYPE: Input
 VARIABLES DESCRIPTION:   Passed in via parameter passing, this variable is the
 IEN of the PAID Employee (450) file entry to be updated.  
SUBSCRIBING PACKAGE: NURSING SERVICE    ISC: Hines

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
SUBSCRIBING PACKAGE: GEN. MED. REC. - I/O
  ISC: Hines
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
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
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: 1
  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
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
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,
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
SUBSCRIBING PACKAGE: NURSING SERVICE    ISC: Hines
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: SEP 01, 2010

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
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: 1416                            IA #: 1416
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: HOSPITAL LOCATION
  ID: SC(
GLOBAL REFERENCE: SC(D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Nursing has permission to LAYGO entries to the Hospital
 Location file using ^DIC.  These entries will have a Type=OTHER and Type
 Extension=NURSING.  
  
 Nursing has permission to delete entries in this file using ^DIK.  The only 
 entries that can be deleted are those with Type=OTHER, and Type 
 Extension=NURSING.  
FIELD NUMBER: 2                         FIELD NAME: TYPE
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 2.1                       FIELD NAME: TYPE EXTENSION
  LOCATION: 0;22                        ACCESS: Write w/Fileman
FIELD NUMBER: 3                         FIELD NAME: INSTITUTION
  LOCATION: 0;4                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   Nursing can access the Hospital Location (44) file as
 described in this DBIA.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
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
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
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 <CR> 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
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
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
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
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
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
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
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
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: 1427                            IA #: 1427
  FILE NUMBER: 59.7                     GLOBAL ROOT: PS(59.7,
  DATE CREATED: NOV 20, 1995
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: PHARMACY SYSTEM
  ID: PS(59.7,
GLOBAL REFERENCE: PS(59.7,D0,
FIELD NUMBER: 20.1
  FIELD NAME: VERSION NUMBER LAST INITS RUN
  LOCATION: 20;1                        ACCESS: Direct Global Read & w/Fileman
 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 EMAIL GROUP 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 December 31, 2006.  Vitals/Measurements can access the Pharmacy
 Sytsem (59.7) file as described in this DBIA.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  ISC: Hines

NUMBER: 1428                            IA #: 1428
  FILE NUMBER: 52.7                     GLOBAL ROOT: PS(52.7,
  DATE CREATED: NOV 20, 1995            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: IV SOLUTIONS
  ID: PS(52.7,
GLOBAL REFERENCE: PS(52.7,DA,
FIELD NUMBER: .01                       FIELD NAME: PRINT NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Patient Intake/Output V3.0 can access the IV Solutions
 (52.7) file as described in this DBIA.  
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 3.0
SUBSCRIBING PACKAGE: INTAKE/OUTPUT      ISC: Hines

NUMBER: 1429                            IA #: 1429
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: NOV 20, 1995            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: PHARMACY PATIENT
  ID: PS(55,
GLOBAL REFERENCE: PS(55,D0,'IV',0)
 GLOBAL DESCRIPTION:   Direct global read of this node to determine if any IV
 data exists.  
GLOBAL REFERENCE: PS(55,D0,'IV',D1,
FIELD NUMBER: .04                       FIELD NAME: TYPE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: INFUSION RATE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 100                       FIELD NAME: STATUS
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,D0,'IV',D1,'SOL',0)
 GLOBAL DESCRIPTION:   Direct global read to see if any solutions exist for an
 IV.  
GLOBAL REFERENCE: PS(55,D0,'IV',D1,'SOL',D2,
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 DESCRIPTION:   Direct global read of ^PS(55,D0,"IV",D1,"SOL",D2) to
 loop through solution multiple is allowed.  
GLOBAL REFERENCE: PS(55,D0,'IV','B',
 GLOBAL DESCRIPTION:   Direct global read of "B" cross-reference of IV multiple
 is allowed to loop through the entries in the IV multiple.  
 GENERAL DESCRIPTION:   Intake/Output V3.0 can access the Pharmacy Patient (55)
 file as described in this DBIA.  
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 3.0
SUBSCRIBING PACKAGE: INTAKE/OUTPUT      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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
 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)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  

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
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
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
  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: 1
  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
  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
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
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
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: 1454                            IA #: 1454
  DATE CREATED: JAN 11, 1996            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         ROUTINE: XPDMENU
  NAME: XPDMENU TO GET OPTION IEN       ID: XPDMENU
 GENERAL DESCRIPTION:   This IA will allow the registration package to call
 LKOPT^XPDMENU to acquire the IEN of a menu option when passed the option name. 
 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LKOPT
 COMPONENT DESCRIPTION:   $$LKOPT^XPDMENU("OPTION NAME") called to retrieve the
 option's IEN in file 19.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   name of option 
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 1455                            IA #: 1455
  DATE CREATED: JAN 11, 1996            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         ROUTINE: XUTMOPT
  NAME: XUTMOPT used to reschedule task
  ID: XUTMOPT
 GENERAL DESCRIPTION:   This IA will allow the registration package to
 reschedule a task if it is not already scheduled in the future.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RESCH
 COMPONENT DESCRIPTION:   The following code is used to reschedule the 'DG G&L
 RECALCULATION OPTION' if it is not already scheduled in the future: 
  
 D RESCH^XUTMOPT("DG G&L RECALCULATION AUTO",DT_.2100,,,"L") 
VARIABLES: OPTION                       TYPE: Input
 VARIABLES DESCRIPTION:   Name of option to be rescheduled.  
VARIABLES: WHEN                         TYPE: Input
 VARIABLES DESCRIPTION:   Time option is to be scheduled.  
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   Set to L to allow LAYGO into the OPTION SCHEDULING
 file.  
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 1456                            IA #: 1456
  FILE NUMBER: 19.2                     GLOBAL ROOT: DIC(19.2,
  DATE CREATED: JAN 11, 1996            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DIC(19.2 usage
  ID: DIC(19.2,
GLOBAL REFERENCE: DIC(19.2,'B',
 GLOBAL DESCRIPTION:   Allows use of B cross-reference to loop through all
 entries in the OPTION SCHEDULING file for a given option.  
GLOBAL REFERENCE: DIC(19.2,IEN,0)
FIELD NUMBER: 2                         FIELD NAME: QUEUED TO RUN AT WHAT TIME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Allows comparison of date scheduled to now to see if
 option is scheduled in the future.  
 GENERAL DESCRIPTION:   Allows use of the "B" cross-reference of the OPTION
 SCHEDULING file (#19.2) to loop though queued times for a given option.  Also
 allows access of the QUEUED TO RUN AT WHAT TIME (#2) field which is the 2nd
 piece of the 0 node of the file.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: REGISTRATION       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
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
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
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
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
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
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
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
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
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
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
 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
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 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP GMRA EVENTS protocol 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  DATE ACTIVATED: SEP 30, 2014

NUMBER: 1468                            IA #: 1468
  DATE CREATED: JAN 19, 1996
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Other
  NAME: GMRA MEDWATCH DATA COMPLETE PROTOCOL
 GENERAL DESCRIPTION:   This extended action protocol is created with v4.0 and
 is invoked whenever the Pharmacy and Therapeutics Committee completes a
 MedWatch form on a patient's adverse reaction. Action protocols from other
 applications may be added 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) 
   
      GMRAPA1 = The Internal Entry Number of the reaction in 
                File 120.85 (ADVERSE REACTION REPORTING) 
   GMRAPA1(0) = The zero node of the entry in File 120.85.  
                Below is a description of the data for that node.  
   
                $P  Field name              Field type 
                -----------------------------------------------------------
                1   DATE/TIME OF EVENT      Date/Time (FM format) 
                2   PATIENT                 Pointer to File 2 (PATIENT) 
                3   QUESTION #1             Set of Codes (y=YES,n=NO) 
                4   QUESTION #2             Set of Codes (y=YES,n=NO) 
                5   QUESTION #3             Set of Codes (y=YES,n=NO) 
                6   QUESTION #4             Set of Codes (y=YES,n=NO) 
                7   QUESTION #5             Set of Codes (y=YES,n=NO) 
                8   NO. DAY HOSPITALIZED    Numeric 
                9   QUESTION #6             Set of Codes (y=YES,n=NO) 
                10  QUESTION #7             Set of Codes (y=YES,n=NO) 
                11  QUESTION #8             Set of Codes (y=YES,n=NO) 
                12  DATE MD NOTIFIED        Date/Time (FM format) 
                13  OBSERVER                Pointer to File 200 (NEW 
                                            PERSON) 
                14  SEVERITY                Set of Codes 
                                            (1=Mild, 
                                             2=Moderate, 
                                             3=Severe) 
                15  RELATED REACTION        Pointer to File 120.8 (PATIENT 
                                            ALLERGIES) 
                16  QUESTION #9             Set of Codes (y=YES,n=NO) 
                17  QUESTION #10            Set of Codes (y=YES,n=NO) 
  
  
  
 *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: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DIETETICS          ISC: Hines

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
 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
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 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP GMRA SIGN-OFF ON DATA protocol 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  DATE ACTIVATED: SEP 30, 2014

NUMBER: 1470                            IA #: 1470
  DATE CREATED: MAR 09, 2020
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: GMRA VERIFY DATA PROTOCOL
 GENERAL DESCRIPTION:   This extended action protocol is created with v4.0 and
 is invoked whenever an allergy/adverse reaction tracking incident is verified
 on a patient.  Action protocols from other applications may be added to this
 event upon approval.  
  
 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
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Approved 3/9/20, effective with VPR*1*14. 
  DATE ACTIVATED: MAR 09, 2020

NUMBER: 1471                            IA #: 1471
  DATE CREATED: JAN 23, 1996
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         ROUTINE: RAUTL3
  NAME: RAUTL3                          ID: RAUTL3
 GENERAL DESCRIPTION:   The Adverse Reaction Tracking (ART) package requests
 permission to call the ALLERGY^RAUTL3 entry point in the Rad/Nuc Med package
 if the version of the Rad/Nuc Med package is 4.0 or 4.5. In version 4.0 of the
 Rad/Nuc Med package this entry point updated the Contrast Medium Allergy field 
 (.05) in the Rad/Nuc Med Patient file (70). That data is now stored in the ART
 package. With the recent release of Rad/Nuc Med v4.5 this entry point is
 merely a Quit command. It exists to provide ART with backward compatibility.
 We ask that the Rad/Nuc Med package keep this entry point through its version
 4.5 after which Rad/Nuc Med can delete the entry point and ART will modify its
 code to no longer reference this routine entry point.  
  STATUS: Retired                       DURATION: Next Version
COMPONENT/ENTRY POINT: ALLERGY
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number (File #2).  
VARIABLES: YN                           TYPE: Input
 VARIABLES DESCRIPTION:   YN = 'Y' if user is adding contrast media allergy 
  
 YN = 'N' if user is entering a contrast media allergy in error.  
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

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
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
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: 1474                            IA #: 1474
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Other                           NAME: DBIA1474
 GENERAL DESCRIPTION:   Quality: Audiology and Speech Pathology Audit and
 Review (QUASAR), will place the PIMS option [SDCLINIC WORKLOAD] on the QUASAR 
 Reports menu tree during the post-init process.  This will provide Audiology
 and Speech Pathology workload data to A&SP users.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
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
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
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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 02/02/24, effective with OR*3*608 to document
 historical usage of .372 Rated Disabilities 

NUMBER: 1477                            IA #: 1477
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: Global Read of S node of File 44
  ID: SC(
GLOBAL REFERENCE: SC(D0,'S',D1,1,0)
FIELD NUMBER: 2                         FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,'S',0)
FIELD NUMBER: 1900                      FIELD NAME: APPOINTMENT
  ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,'S',D1,0)
FIELD NUMBER: .01                       FIELD NAME: APPOINTMENT DATE/TIME
  LOCATION: 0;1                         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 of the Hospital
 Location file (#44) in order to get the PATIENT (#2) field value of the
 APPOINTMENT multiple (#1900).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

NUMBER: 1478                            IA #: 1478
  FILE NUMBER: 409.5                    GLOBAL ROOT: SDV(
  DATE CREATED: FEB 09, 1996            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: Global Read zero and CS nodes of File 409.5
  ID: SDV(
GLOBAL REFERENCE: SDV(D0,'CS',0)
FIELD NUMBER: 10                        FIELD NAME: CLINIC STOP CODE
  ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SDV(D0,'CS'D1,0)
FIELD NUMBER: 3                         FIELD NAME: ASSOCIATED CLINIC
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SDV(D0,0)
FIELD NUMBER: 2                         FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Adverse Reaction Tracking package requests
 permission to do a direct global read of the "CS" nodes in the Scheduling
 Visits file (#409.5) in order to get the ASSOCIATED CLINIC field (#3) value of
 the CLINIC STOP CODE (#10) multiple. Also, we wish to do a direct global read
 of the zero node in order to get to the PATIENT (#2) field value.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

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
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

NUMBER: 1480                            IA #: 1480
  FILE NUMBER: 405                      GLOBAL ROOT: DGPM(
  DATE CREATED: FEB 09, 1996            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File
  NAME: Global Read of zero node and AMV1 nodes in File 405
  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: .06                       FIELD NAME: WARD LOCATION
  LOCATION: 0;6                         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: .03                       FIELD NAME: PATIENT
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPM('AMV1'
 GLOBAL DESCRIPTION:   Direct Global Read of this cross-reference.  
GLOBAL REFERENCE: DGPM('ATT1'
 GLOBAL DESCRIPTION:   Direct Global Read of this cross-reference.  
GLOBAL REFERENCE: DGPM('ATT3'
 GLOBAL DESCRIPTION:   Direct Global Read of this cross-reference.  
 GENERAL DESCRIPTION:   The Adverse Reaction Tracking package requests
 permission to do a direct global read of the zero node of the PATIENT MOVEMENT
 file (#405) in order to read the DATE/TIME (#.01), WARD LOCATION (#.06) and
 DISCHARGE/CHECK-OUT MOVEMENT (#.17) fields. Also, we request permission to do
 a direct global read of the "AMV1' cross-reference nodes.  
  STATUS: Other                         DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

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
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines

NUMBER: 1482                            IA #: 1482
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA1482
  ID: SC(
GLOBAL REFERENCE: SC(D0,
FIELD NUMBER: 8                         FIELD NAME: STOP CODE NUMBER
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Quality: Audiology and Speech Pathology Audit and
 Review (QUASAR) will reference the zero node of the HOSPITAL LOCATION file,
 fields .01 NAME and field 8 STOP CODE NUMBER.  
  
 Quality: Audiology and Speech Pathology Audit and Review (QUASAR) Package, 
 A&SP CLINIC VISIT File (#509850.6),  CLINIC LOCATION Field (#2.6) points to
 the HOSPITAL LOCATION File (#44) to accommodate recording, tracking and
 reporting workload by clinic.  
  
 Quality: Audiology and Speech Pathology Audit and Review (QUASAR) Package, 
 A&SP SITE PARAMETER File (#508950.8),  CLINIC Multiple (#1), CLINIC LOCATION
 (# .01) points to the HOSPITAL LOCATION File (#44) to accommodate recording,
 tracking and reporting workload by clinic.  
  
 Quality: Audiology and Speech Pathology Audit and Review (QUASAR) Package, 
 A&SP DELETE VISIT File (#509850.9),  CLINIC Field (#20) points to the HOSPITAL
 LOCATION File (#44) to accommodate recording, tracking and reporting workload
 by clinic.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: QUASAR             ISC: Birmingham
 SUBSCRIBING DETAILS:   Quality: Audiology and Speech Pathology Audit and
 Review (QUASAR) will reference the zero node of the HOSPITAL LOCATION file,
 fields .01 NAME and field 8 STOP CODE NUMBER.  
  
 Quality: Audiology and Speech Pathology Audit and Review (QUASAR) Package, ASP
 CLINIC VISIT File (#509850.6),  CLINIC LOCATION Field (#2.6) points to the
 HOSPITAL LOCATION File (#44) to accommodate recording, tracking and reporting
 workload by clinic.  
  
 Quality: Audiology and Speech Pathology Audit and Review (QUASAR) Package, ASP
 SITE PARAMETER File (#508950.8),  CLINIC Multiple (#1), CLINIC LOCATION (#
 .01) points to the HOSPITAL LOCATION File (#44) to accommodate recording,
 tracking and reporting workload by clinic.  
  
 Quality: Audiology and Speech Pathology Audit and Review (QUASAR) Package, ASP
 DELETE VISIT File (#509850.9),  CLINIC Field (#20) points to the HOSPITAL
 LOCATION File (#44) to accommodate recording, tracking and reporting workload
 by clinic.  
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: DENTAL

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
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
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
SUBSCRIBING PACKAGE: ENGINEERING        ISC: Washington/Silver Spring

NUMBER: 1486                            IA #: 1486
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: Global Read of I nodes in File 44
  ID: SC(
GLOBAL REFERENCE: SC(D0,'I')
FIELD NUMBER: 2505                      FIELD NAME: INACTIVATE DATE
  LOCATION: I;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2506                      FIELD NAME: REACTIVATE DATE
  LOCATION: I;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Adverse Reaction Tracking package requests
 permission to do a direct global read of the "I" nodes in the HOSPITAL
 LOCATION file (#44) in order to get the INACTIVATE DATE (#2505) and the
 REACTIVATE DATE (#2506) field values.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  ISC: Hines
SUBSCRIBING PACKAGE: SURGERY            ISC: Birmingham
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 1487                            IA #: 1487
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9(
  DATE CREATED: FEB 13, 1996            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA1487
  ID: ICD9(
GLOBAL REFERENCE: ICD9(DO,0)
FIELD NUMBER: .01                       FIELD NAME: CODE NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DIAGNOSIS
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ICD9('BA',CODE NUMBER,DO)
 GENERAL DESCRIPTION:   Quality: Audiology and Speech Pathology Audit and
 Review (QUASAR) will reference the following fields from the ICD DIAGNOSIS
 file to convert ICD9 codes to their text equivalents.  Specifically, fields
 .01 CODE NUMBER and field 3 DIAGNOSIS.  Additionally for QUASAR reports, we
 will reference the "BA" cross-reference.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
SUBSCRIBING PACKAGE: QUASAR             ISC: Birmingham

NUMBER: 1488                            IA #: 1488
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT(
  DATE CREATED: FEB 13, 1996            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA1488
  ID: ICPT(
GLOBAL REFERENCE: ICPT(DO,0)
FIELD NUMBER: .01                       FIELD NAME: CPT CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: SHORT NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: INACTIVE FLAG
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ICPT('B',
 GENERAL DESCRIPTION:   Quality: Audiology and Speech Pathology Audit and
 Review (QUASAR) will reference the following fields from the CPT file to
 convert CPT codes to their text equivalents.  Specifically, field .01 CPT CODE
 , field 2 SHORT NAME, and field 5 INACTIVE FLAG.  Additionally for QUASAR
 reports, we will reference the "B" cross-reference.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
SUBSCRIBING PACKAGE: QUASAR             ISC: Birmingham

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
  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
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
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
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
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
  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
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
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
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
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
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
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: 1501                            IA #: 1501
  DATE CREATED: MAR 01, 1996            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSJAC
  NAME: Info for Network Health Exchange (NHE)
  ID: PSJAC
 GENERAL DESCRIPTION:   Network Health Exchange (NHE) would like to call 
 ENIV^PSJAC in order to obtain Inpatient Medications information.  
  STATUS: Withdrawn                     DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
COMPONENT/ENTRY POINT: ENIV
SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE
  ISC: Oakland

NUMBER: 1502                            IA #: 1502
  DATE CREATED: MAR 01, 1996            CUSTODIAL PACKAGE: DISCHARGE SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMRDLIBC
  NAME: Info for Network Health Exchange (NHE)
  ID: GMRDLIBC
 GENERAL DESCRIPTION:   Network Health Exchange (NHE) would like to call: 
        $$STATUS^GMRDLIBC in order to obtain informations on report status.  
  STATUS: Withdrawn                     DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
COMPONENT/ENTRY POINT: $$STATUS
 COMPONENT DESCRIPTION:   Evaluate status of reports 
SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE
  ISC: Oakland

NUMBER: 1503                            IA #: 1503
  DATE CREATED: MAR 01, 1996            CUSTODIAL PACKAGE: DISCHARGE SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMRDLIBP
  NAME: Info for Network Health Exchange (NHE)
  ID: GMRDLIBP
 GENERAL DESCRIPTION:   Network Health Exchange (NHE) would like to call 
 $$CANSEE^GMRDLIBP to determine if a clinician may view a report on-screen.  
  STATUS: Withdrawn                     DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
COMPONENT/ENTRY POINT: $$CANSEE
 COMPONENT DESCRIPTION:   Check whether clinician may see a report on Review
 Screen 
SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE
  ISC: Oakland

NUMBER: 1504                            IA #: 1504
  DATE CREATED: MAR 01, 1996            CUSTODIAL PACKAGE: DISCHARGE SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMRDLIBS
  NAME: Info for Network Health Exchange (NHE)
  ID: GMRDLIBS
 GENERAL DESCRIPTION:   Network Health Exchange (NHE) would like to call 
 $$DATE^GMRDLIBS  and $$NAME^GMRDLIBS  to get information on Discharge
 Summarys.  
  STATUS: Withdrawn                     DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
COMPONENT/ENTRY POINT: $$DATE
 COMPONENT DESCRIPTION:   Call with X=2910419.01 and FMT=Return Format of date
 ("MM/DD") 
COMPONENT/ENTRY POINT: $$NAME
 COMPONENT DESCRIPTION:   Call with X="LAST,FIRST MI", FMT=Return Format
 ("LAST, FI") 
SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE
  ISC: Oakland

NUMBER: 1505                            IA #: 1505
  DATE CREATED: MAR 01, 1996            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMTSU
  NAME: Info for Network Health Exchange (NHE)
  ID: GMTSU
 GENERAL DESCRIPTION:   Network Health Exchange would like to call 
 FMHL7DTM^GMTSU  in order to obtain information.  
  STATUS: Withdrawn                     DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
COMPONENT/ENTRY POINT: FMHL7DTM
 COMPONENT DESCRIPTION:   Recieves X as CCYYMMDDHHMM and returns X as internal
 date/time 
SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE
  ISC: Oakland

NUMBER: 1506                            IA #: 1506
  DATE CREATED: JUL 15, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         ROUTINE: LROC1
  NAME: Info for Network Health Exchange (NHE)
  ID: LROC1
 GENERAL DESCRIPTION:   Network Health Exchange (NHE) would like to call ^LROC1
 in order to obtain valid lab order information.  
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
COMPONENT/ENTRY POINT: LROC1
 COMPONENT DESCRIPTION:   TO CLEAN UP LAB ANCILLARY FILE 
SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE
  ISC: Oakland

NUMBER: 1507                            IA #: 1507
  DATE CREATED: MAR 01, 1996
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: OR1
  NAME: Info for Network Health Exchange (NHE)
  ID: OR1
 GENERAL DESCRIPTION:   Network Health Exchange (NHE) would like to call 
 SAVE^OR1 to gather information.  
  STATUS: Withdrawn                     DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
COMPONENT/ENTRY POINT: SAVE
 COMPONENT DESCRIPTION:   Save OR variables from OR,OR2 
SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE
  ISC: Oakland

NUMBER: 1508                            IA #: 1508
  DATE CREATED: MAR 01, 1996
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: OR4
  NAME: Info for Network Health Exchange (NHE)
  ID: OR4
 GENERAL DESCRIPTION:   Network Health Exchange would like to call  AFT^OR4  to
 obtain information to be included in the NHE reports (Health Summary clones).  
  STATUS: Withdrawn                     DURATION: Next Version
  GOOD ONLY FOR VERSION: 5,1
COMPONENT/ENTRY POINT: AFT
 COMPONENT DESCRIPTION:   Process accepted orders from XQORO 
SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE
  ISC: Oakland

NUMBER: 1509                            IA #: 1509
  DATE CREATED: MAR 01, 1996
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: ORREV3
  NAME: Info for Network Health Exchange (NHE)
  ID: ORREV3
 GENERAL DESCRIPTION:   Network Health Exchange (NHE) would like to call 
        $$TX^ORREV3 and 
        TXOLD^ORREV3 to obtain information for the NHE reports (Health Summary
 clones).  
  STATUS: Withdrawn                     DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
COMPONENT/ENTRY POINT: $$TX
 COMPONENT DESCRIPTION:   Get text in ORTX() 
COMPONENT/ENTRY POINT: TXOLD
 COMPONENT DESCRIPTION:   Get text using old field 
SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE
  ISC: Oakland

NUMBER: 1510                            IA #: 1510
  DATE CREATED: MAR 01, 1996
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: ORUDPA
  NAME: Info for Network Health Exchange (NHE)
  ID: ORUDPA
 GENERAL DESCRIPTION:   Network Health Exchange (NHE) would like to call 
 END^ORUDPA  to collect information for NHE reports (Health Summary clones).  
  STATUS: Withdrawn                     DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
COMPONENT/ENTRY POINT: END
 COMPONENT DESCRIPTION:   from ORUHDR,ORS3 
SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE
  ISC: Oakland

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
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: 1512                            IA #: 1512
  DATE CREATED: MAR 08, 1996            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Private                        TYPE: Routine
  ROUTINE: LEXU                         NAME: USE OF ICDONE
  ID: LEXU
 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^LEXU when
 released 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: Retired                       DURATION: Till Otherwise Agreed
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
 from another 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.  

NUMBER: 1513                            IA #: 1513
  DATE CREATED: MAR 11, 1996            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: XUVERIFY
  NAME: DBIA1513                        ID: XUVERIFY
 GENERAL DESCRIPTION:   This is a new supported reference in the routine
 XUVERIFY.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: WITNESS
 COMPONENT DESCRIPTION:   This entry point was created for Controlled Subs
 Version 3.0, but and DHCP can ask to subscribe to the entry point.  
  
 Userage: $$WITNESS^XUVERIFY(prefix_text,keys) 
  
   Returns the IEN of a entry in the new person file that has entered a 
   valid ACCESS/VERIFY code pair and would be allowed to sign on.  
   There is no feedback as to why a user is not accepted as a valid witness.  
   
   prefix_text is a string that will be displayed before both the ACCESS 
   and VERIFY code prompts.  
   
   keys is a list of '^' delimited security KEY names, One of which the 
   person entering the A/V code must have so that the IEN is returned.  
  

NUMBER: 1514                            IA #: 1514
  DATE CREATED: MAR 12, 1996
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: ORF4
  NAME: ORF4 ENTRY POINT                ID: ORF4
 GENERAL DESCRIPTION:   Request permission to call ^ORF4 routine to get order
 data.  
  
 Input variables: 
        ORUPKG=ptr to package file, ORUSTS=status0^status1^status2...  
        ORUVP=variable pointer of patient "dfn;DPT(" 
        ORUPRES=pre-defined context 1>All 2>Current 3>DC'ed 4>Expd 
                5>Exp 6>New 7>Pend 8>Act (OPTIONAL) 9>Expanded 
        ORDR=1 will put data into ^TMP("OR",$J,"OUT",9999999-ORSTRT,ORIFN) 
             (OPTIONAL) 
        ORUSTART=date/time to start looking in FM format (OPTIONAL) 
        ORUEND=date/time to stop looking in FM format (OPTIONAL) 
   
 Output Variables from Order (#100) file: 
   ^TMP("ORR",$J,ORLIST,i)=ORIFN_^_STATUS 
       
      or optionally 
  
   ^TMP("OR",$J,"OUT",Inverse Start Date,IFN,"ORNP") = (field 1) 
       Internal Current Agent/Provider ^ External Current Agent/Provider 
   ^TMP("OR",$J,"OUT",Inverse Start Date,IFN,"ORSTOP")= (field 22) 
       Stop Date 
   ^TMP("OR",$J,"OUT",Inverse Start Date,IFN,"ORSTS")= (field  5) 
       Internal Status ^ External Status 
   ^TMP("OR",$J,"OUT",Inverse Start Date,IFN,"ORSTRT")= (field 21.1) 
       Current Start Date 
   ^TMP("OR",$J,"OUT",Inverse Start Date,IFN,"ORTX",Line cnt)= (field .11) 
       Order Text 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ORF4 OR EN
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 1515                            IA #: 1515
  DATE CREATED: MAR 12, 1996            CUSTODIAL PACKAGE: 1
  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
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
  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
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: 1518                            IA #: 1518
  FILE NUMBER: 8989.3                   GLOBAL ROOT: XTV(8989.3,
  DATE CREATED: MAR 22, 1996            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            NAME: DEFAULT INSTITUTION
  ID: XTV(8989.3,
GLOBAL REFERENCE: XTV(8989.3,1,XUS)
FIELD NUMBER: 217                       FIELD NAME: DEFAULT INSTITUTION
  LOCATION: XUS;17                      ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Record Tracking needs to find the institution
 associated with a borrower when the borrower is an entry in the NEW PERSON
 file.  We plan to first look at the division multiple of the NEW PERSON file. 
 If there are no entries in that multiple, we would like to use the DEFAULT
 INSTITUTION field (#217) of the KERNEL SITE PARAMETERS file (#8989.3).  This
 same logic is used in routines such as XUP and XUS1.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RECORD TRACKING    ISC: Albany
SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE

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
 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
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
  DATE ACTIVATED: JUN 20, 2012

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
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
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
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
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
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
SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST
  ISC: Washington/Silver Spring

NUMBER: 1526                            IA #: 1526
  DATE CREATED: APR 04, 1996            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Routine                         ROUTINE: PRCSCK
  NAME: DBIA1526                        ID: PRCSCK
 GENERAL DESCRIPTION:   The NX module requests permission to use checks
 currently in use when creating a 2237.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: 2
 COMPONENT DESCRIPTION:   Entry point with sub-field 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number for the 2237.  
VARIABLES: DA(1)                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number for a line item on the 2237 
VARIABLES: PRCSERR                      TYPE: Output
 VARIABLES DESCRIPTION:   After checking for certain error conditions, returns
 error flag.  
COMPONENT/ENTRY POINT: QRB
 COMPONENT DESCRIPTION:   Checks for quantity entered.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number for a line item on the 2237.  
VARIABLES: DA(1)                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number for the 2237.  
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
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
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
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
  ISC: Birmingham
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
 SUBSCRIBING DETAILS:   Patch PSB*3.0*103 (with the project Existing Product
 Intake Program, (EPIP) needs to access the NURS LOCATION file (#211.4) to
 determine active Nursing wards with patients receiving care.  

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
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 - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: EVENT CAPTURE      ISC: Birmingham

NUMBER: 1532                            IA #: 1532
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT(
  DATE CREATED: MAY 06, 1996            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  USAGE: Private                        TYPE: File
  NAME: DBIA1532                        ID: ICPT(
 GENERAL DESCRIPTION:   Store a variable pointer in the Event Capture files
 that has a primary lookup to CPT file (#81). This is read only. The second
 lookup is contained locally in the Event Capture file range.  
  
 Global read access to the CPT file (#81) to display the CPT CODE field (.01)
 and SHORT NAME field (2) on input screens and reports within the Event Capture
 software.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
SUBSCRIBING PACKAGE: EVENT CAPTURE      ISC: Birmingham

NUMBER: 1533                            IA #: 1533
  FILE NUMBER: 725                      GLOBAL ROOT: EC(725,
  DATE CREATED: MAY 07, 1996            CUSTODIAL PACKAGE: 1
  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
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
  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: 1
  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
  GOOD ONLY FOR VERSION: 2.7
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 1536                            IA #: 1536
  DATE CREATED: MAY 29, 1996
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Other                           NAME: Deleting Options
 GENERAL DESCRIPTION:   The Nursing package can delete the following
 Vitals/Measurements options using the appropriate KIDS supported method to do
 this: 
  
   GMRV CUSTOM V/M, GMRV PULSE RADIAL, GMRVOR DGADM, GMRVOR DGDIS, GMRVOR 
   DGPM, GMRVOR DGXFR, GMRVORADMIT V/M, GMRVORB/P, GMRVORHT, GMRVORMENU, 
   GMRVORP CUM REPORT, GMRVORP DISP VITALS, GMRVORP SF511, GMRVORPULSE, 
   GMRVORRESP, GMRVORTEMP, GMRVORTPR, GMRVORTPR B/P, GMRVORWT 
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 3
SUBSCRIBING PACKAGE: NURSING SERVICE    ISC: Hines

NUMBER: 1537                            IA #: 1537
  DATE CREATED: MAY 29, 1996            CUSTODIAL PACKAGE: GEN. MED. REC. - I/O
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Other                           NAME: Deleting Options
 GENERAL DESCRIPTION:   The Nursing package can delete the following
 Intake/Output options using the appropriate KIDS supported method to do this: 
 GMRY IV SHIFT AND EVENT.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NURSING SERVICE    ISC: Hines

NUMBER: 1539                            IA #: 1539
  DATE CREATED: JUN 12, 1996            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: IBRFN3
  NAME: DBIA1539                        ID: IBRFN3
 GENERAL DESCRIPTION:   IB routine IBRFN3 
  
 This routine collects billing information from the Bill/Claims file (#399) 
 which is used by the Regional Counsel interface of the Accounts Receivable 
 package for the purpose of sending via E-mail to a site's Regional Counsel 
 office.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: BILL(IBIFN,ARRAY)
VARIABLES: IBIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Bill/Claims file (#399) entry.  
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   Input: Array name preceeded by a period (Example: .BI
 for BI array).  
  
 Output: 0 = No billing information, 1 = Billing information exists 
  
 If ARRAY=1, output will also be ARRAY() containing the following: 
  
 ARRAY("BN") = BILL NUMBER ARRAY("SR") = SENSITIVE RECORD? (Y/N) ARRAY("STF") =
 STATEMENT COVERS FROM DATE - first date covered by bill ARRAY("STT") =
 STATEMENT COVERS TO DATE - last date covered by bill ARRAY("TCG") = TOTAL
 CHARGES ARRAY("TOC") = BILL TYPE (INPATIENT OR OUTPATIENT) ARRAY("TCF") = BILL
 FORM TYPE ARRAY("PIN") = PRIMARY INSURANCE CARRIER NAME ^ HOSPITAL PROVIDER
 NUMBER ^ 
                GROUP NAME ^ GROUP NUMBER ^ NAME OF INSURED ^ SUBSCRIBER ID ^ 
                RELATIONSHIP TO INSURED ARRAY("PIN","MMA") = PRIMARY INSURANCE
 CARRIER MAIN STREET ADDDRESS #1 ^ 
                      STREET ADDRESS #2 ^ STREET ADDRESS #3 ^ CITY ^ STATE ^ 
                      ZIP ^ PHONE NUMBER ARRAY("RVC") = NUMBER OF REVENUE CODES
 ON BILL (multiple) ARRAY("RVC",X) = REVENUE CODE ^ REVENUE CODE DESCRIPTION ^
 CHARGE PER UNIT ^ 
                  NUMBER OF UNITS ^ TOTAL CHARGE FOR REV CODE ARRAY("OPV") =
 NUMBER OF OUTPATIENT VISIT DATES ON BILL (multiple) ARRAY("OPV",X) =
 OUTPATIENT VISIT DATE ARRAY("PRC") = NUMBER OF PROCEDURES ON BILL (multiple) 
 ARRAY("PRC",X) = PROCEDURE CODE ^ PROCEDURE DESCRIPTION ^ PROCEDURE DATE ^ 
                  PLACE OF SERVICE CODE ^ PLACE OF SERVICE ^ 
                  TYPE OF SERVICE CODE ^ TYPE OF SERVICE ARRAY("DXS") = NUMBER
 OF DIAGNOSIS ON BILL (multiple) ARRAY("DXS,X) = DIAGNOSIS CODE ^ DIAGNOSIS 
 ARRAY("RXF") = NUMBER OF PRESCRIPTION REFILLS ON BILL (multiple) 
 ARRAY("RXF",X) = PRESCRIPTION # ^ REFILL DATE ^ DRUG NAME ^ DAYS SUPPLY ^ 
                  QUANTITY ^ NDC # ARRAY("PRD") = NUMBER OF PROSTHETIC ITEMS ON
 BILL (multiple) ARRAY("PRD",X) = PROSTHETIC DEVICE ^ DELIVERY DATE IF
 CONDITION RELATED TO: 
    EMPLOYMENT: ARRAY("CRE") = "EMPLOYMENT" 
    AUTO ACCIDENT: ARRAY("CRA") = "AUTO ACCIDENT/STATE" 
    OTHER ACCIDENT: ARRAY("CRO") = "OTHER ACCIDENT" 
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Washington/Silver Spring

NUMBER: 1540                            IA #: 1540
  FILE NUMBER: 0                        GLOBAL ROOT: DD(440
  DATE CREATED: JUN 13, 1996            CUSTODIAL PACKAGE: 1
  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             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
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: 1542                            IA #: 1542
  FILE NUMBER: 9.6                      GLOBAL ROOT: XPD
  DATE CREATED: JUN 18, 1996            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: BUILD File Read
  ID: XPD
GLOBAL REFERENCE: XPD(9.6,'B',SCPATCH
 GENERAL DESCRIPTION:   For PCMM (SD*5.3*41), as part of the installation
 environment checker, SCMCENV, we check for the existence of the following
 global using $DATA: 
     ^XPD(9.6,"B",SCPATCH) 
     This is NAME cross-reference of the BUILD File (#9.6) 
  
 Due to the concurrent development of PCMM and the RPC BROKER software, it was
 necessary to check for the existence of the specific BUILD NAME. If the BUILD
 file check fails, we use $$VERSION^XPDUTL as a check for the existence of the
 appropriate RPC BROKER version.  If both checks fail, we abort the install of
 PCMM.  
  STATUS: Withdrawn                     DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.3*41
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 1543                            IA #: 1543
  DATE CREATED: JUN 18, 1996            CUSTODIAL PACKAGE: 1
  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
  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
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 
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

NUMBER: 1545                            IA #: 1545
  FILE NUMBER: 8930                     GLOBAL ROOT: USR(8930
  DATE CREATED: JUN 18, 1996
  CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: GLOBAL READ OF USR & USR(8930
  ID: USR(8930
 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 (The USR CLASS File (#8930) 
  
 We do the following operations: 
  o  Read of ^USR(8930,ien,0) 
  o  $DATA check of ^USR(8930) 
  o  $DATA check of ^USR( 
  o  $ORDER read of ^USR(8930,"B",SCX) 
  o  $ORDER read of ^USR(8930,"B",SCX,SCI) 
  o  Look-up, using ^DIC 
  o  RPC Broker Lister lookup of File #8930 
  o  The USER CLASSIFICATION Field (#.02) of the STANDARD POSITION File 
     (#403.46) points to File #8930.  
  o  The USER CLASS Field (#.13) of the TEAM POSITION File (#404.57) 
     points to File #8930.  
  o  The USE USR CLASS FUNCTIONALITY Field (#801) of the SCHEDULING 
     PARAMETERS File (#404.91) does a $DATA check in its input transform 
     for the existence of the ^USR global - requiring this global for the 
     value 'YES' to be set.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

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
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 1547                            IA #: 1547
  GLOBAL ROOT: DD(SCFILE,SCFLD,0        DATE CREATED: JUN 18, 1996
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  NAME: DD GLOBAL READ                  ID: DD(SCFILE,SCFLD,0
GLOBAL REFERENCE: DD(SCFILE,SCFLD,0)
 GENERAL DESCRIPTION:   The Scheduling Developers would like the following
 integration agreement with the FileMan Developers: 
  
 Read access to the DD global in the following fashion: 
  IF $P($G(^DD(SCFILE,SCFLD,0)),U,4)[";0" 
  
  SCFILE = Filenumber of concern 
  SCFLD  = Fieldnumber of concern 
  
 This code is used to determine if the field is a word-processing field.  When
 the PCMM software is updated to use VA FileMan's components, this DBIA will no
 longer be needed.  Per previous discussions with FileMan Component developers,
 this DBIA is needed because of the poor response time that resulted from use
 of supported calls.  
  STATUS: Withdrawn                     DURATION: Next Version
  GOOD ONLY FOR VERSION: SD*5.3
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 1548                            IA #: 1548
  FILE NUMBER: 3.1                      GLOBAL ROOT: DIC(3.1
  DATE CREATED: JUN 19, 1996            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA1548-A
  ORIGINAL NUMBER: 1548                 ID: DIC(3.1
GLOBAL REFERENCE: DIC(3.1,DA,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The title of an individual.  
 GENERAL DESCRIPTION:   IA combined with IA 1234.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST
  ISC: Washington/Silver Spring

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
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
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
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
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: 1
  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
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
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
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 1556                            IA #: 1556
  FILE NUMBER: 1                        GLOBAL ROOT: DIC(
  DATE CREATED: JUL 01, 1996            CUSTODIAL PACKAGE: 1
  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
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

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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION

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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany
SUBSCRIBING PACKAGE: QUASAR             ISC: Birmingham

NUMBER: 1562                            IA #: 1562
  FILE NUMBER: 723                      GLOBAL ROOT: ECC(723,
  DATE CREATED: JUL 18, 1996            CUSTODIAL PACKAGE: EVENT CAPTURE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: MEDICAL SPECIALTY file 723
  ID: ECC(723,
GLOBAL REFERENCE: ECC(723,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   DSS Extracts will reference Event Capture data from the
 MEDICAL SPECIALTY file (#723).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  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-ACD.DNS' 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
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
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
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
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 1567                            IA #: 1567
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870,
  DATE CREATED: JUL 19, 1996            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA1567
  ID: HLCS(870,
GLOBAL REFERENCE: HLCS(870,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 2                         FIELD NAME: LLP PARAMETERS
  LOCATION: 0;2                         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 LOGICAL LINK file (#870) 
    
             NAME (#.01): AMB-CARE 
     LLP PARAMETERS (#2): AMB-CARE 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 1568                            IA #: 1568
  FILE NUMBER: 1                        GLOBAL ROOT: DIC(
  DATE CREATED: JUL 30, 1996            CUSTODIAL PACKAGE: 1
  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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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

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
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
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: 1576                            IA #: 1576
  FILE NUMBER: 40.8                     GLOBAL ROOT: DG(40.8
  DATE CREATED: AUG 08, 1996            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: DIVISION FILE LOOKUP
  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:   AICS allows printing of Encounter Forms and various
 package reports to be sorted by Division.    It is necessary to access the .01
 field in file 40.8 (Medical Center Division) to resolve the data that is 
 returned in calls made to VAUTOMA.  This request is for direct global read 
 access to the .01 field in file 40.8.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Washington/Silver Spring
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES

NUMBER: 1577                            IA #: 1577
  DATE CREATED: AUG 08, 1996            CUSTODIAL PACKAGE: LEXICON UTILITY
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: LEXSET
  NAME: CLINICAL LEXICON REFERENCES     ID: LEXSET
 GENERAL DESCRIPTION:   The purpose of this IA is to access line tag CONFIG in
 routine ^LEXSET.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CONFIG
VARIABLES: GMPL                         TYPE: Input
VARIABLES: PL1                          TYPE: Input
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Washington/Silver Spring

NUMBER: 1578                            IA #: 1578
  DATE CREATED: AUG 08, 1996            CUSTODIAL PACKAGE: LEXICON UTILITY
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: GMPTSET
  NAME: CLINICAL LEXICON UTILITY        ID: GMPTSET
 GENERAL DESCRIPTION:   AICS would like to request access to call linetag
 CONFIG^GMPTSET until the new version of the Clinical Lexicon Utility is
 released.  At that point, we will reference routine ^LEXSET.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CONFIG
VARIABLES: GMPL                         TYPE: Input
VARIABLES: PL1                          TYPE: Input
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Washington/Silver Spring

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
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 
COMPONENT/ENTRY POINT: CLV
 COMPONENT DESCRIPTION:   Ask Camp Lejeune Classification 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file IEN 
VARIABLES: SDOE                         TYPE: Input
 VARIABLES DESCRIPTION:   Outpatient Encounter file IEN (optional) 
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 

NUMBER: 1580                            IA #: 1580
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: SDAMU
  NAME: SDAMU                           ID: SDAMU
 GENERAL DESCRIPTION:   Request ability to call into two linetags within
 routine SDAMU.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CLINIC
 COMPONENT DESCRIPTION:   
  ; -- generic screen for hos. loc. entries 
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   IFN of Hospital Location file 
COMPONENT/ENTRY POINT: CURRENT
 COMPONENT DESCRIPTION:   Retrieve current status of an appointment.  
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Washington/Silver Spring
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany

NUMBER: 1581                            IA #: 1581
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: SDCOU
  NAME: CHECK OUT                       ID: SDCOU
 GENERAL DESCRIPTION:   This IA is for the purpose of determining if the
 checkout is complete.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: COMDT
 COMPONENT DESCRIPTION:   COMDT(SDOE)     ;Check Out Process Completion
 Date/Time 
VARIABLES: SDOE                         TYPE: Input
 VARIABLES DESCRIPTION:   OPT Encounter file IEN 
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Washington/Silver Spring

NUMBER: 1582                            IA #: 1582
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: SDAM2
  NAME: INPATIENT APPT                  ID: SDAM2
 GENERAL DESCRIPTION:   This IA is for the purpose of calling into routine
 ^SDAM2 to determine if an appointment is for an inpatient.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: INP
 COMPONENT DESCRIPTION:   INP(DFN,VDATE)  ; -- determine inpat status ; dom is
 not an inpat appt 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient ien 
VARIABLES: VDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   Date of visit 
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Washington/Silver Spring
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany
SUBSCRIBING PACKAGE: EVENT CAPTURE      ISC: Albany

NUMBER: 1583                            IA #: 1583
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: SDM1A
  NAME: CHECKOUT REQUIRED?              ID: SDM1A
 GENERAL DESCRIPTION:   The purpose of this IA is to call in to REQ^SDM1A to
 determine if checkout is required.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: REQ
 COMPONENT DESCRIPTION:   REQ(SDT)        ; -- which is required check in(CI)
 or out(CO) 
VARIABLES: SDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Appointment~ 
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Washington/Silver Spring
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany

NUMBER: 1584                            IA #: 1584
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: SDM
  NAME: SDM                             ID: SDM
 GENERAL DESCRIPTION:   The purpose of this IA is to call into routine ^SDM
 from the top with the patient defined, so that a follow up appointment can be
 made for the patient.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Based upon a site parameter, a call may be made in to
 ^SDM after completing data entry of an encounter form, so that a follow up 
 appointment can be made for the patient.  

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
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: 1586                            IA #: 1586
  FILE NUMBER: 80.3                     GLOBAL ROOT: ICM(
  DATE CREATED: AUG 08, 1996            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA1586                        ID: ICM(
GLOBAL REFERENCE: ICM(D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This will enable reads both directly and through
 FileMan the code name in the MAJOR DIAGNOSTIC CATEGORY file (#80.3) 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany

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
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
  DATE ACTIVATED: JAN 12, 2015

NUMBER: 1588                            IA #: 1588
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: SC GLOBAL REFERENCES
  ID: SC(
GLOBAL REFERENCE: SC(D0,'PC'
FIELD NUMBER: 2801                      FIELD NAME: DEFAULT TO PC PRACTITIONER
  LOCATION: PC;1                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The purpose of this IA is to determine if flag is set
 to default to PC practitioner.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Washington/Silver Spring

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
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

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
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: 1591                            IA #: 1591
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: SCHEDULED APPOINTMENTS
  ID: SC(
GLOBAL REFERENCE: SC(D0,'S'
 GLOBAL DESCRIPTION:   Appointment multiple.  
 GENERAL DESCRIPTION:   This IA is for the purpose of finding all patients with
 an appointment for a clinic on a given day.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Washington/Silver Spring

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
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
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 
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

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
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: 1
  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
  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
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
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
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
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
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
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
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.  
GLOBAL REFERENCE: AUPNPROB('B')
 GLOBAL DESCRIPTION:   Needed to traverse the "B" index to the .01 field 
 pointing to ICD file #80.  
  
GLOBAL REFERENCE: AUPNPROB(D0,800)
FIELD NUMBER: 80001                     FIELD NAME: SNOMED CT CONCEPT CODE
  LOCATION: 800;1                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is a SNOMED CT Code found in the Lexicon CODES file
 #757.02.  
  
 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
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

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
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
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).  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 1
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 1617                            IA #: 1617
  FILE NUMBER: 0                        GLOBAL ROOT: DD(2,0,'ID'
  DATE CREATED: AUG 29, 1996            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: Scheduling Reads DD(2,0,'ID',...
  ID: DD(2,0,'ID'                       STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 1618                            IA #: 1618
  DATE CREATED: SEP 13, 1996            CUSTODIAL PACKAGE: 1
  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
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: 1
  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
  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
 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
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

NUMBER: 1622                            IA #: 1622
  FILE NUMBER: 3.8                      GLOBAL ROOT: XMB(3.8,
  DATE CREATED: OCT 18, 1996            CUSTODIAL PACKAGE: 1
  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
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
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
SUBSCRIBING PACKAGE: EVENT CAPTURE

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
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
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: 1626                            IA #: 1626
  DATE CREATED: NOV 17, 2006            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Remote Procedure                NAME: XWB FILE LIST
  REMOTE PROCEDURE: XWB FILE LIST       STATUS: Retired

NUMBER: 1627                            IA #: 1627
  DATE CREATED: NOV 17, 2006            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Remote Procedure                NAME: XWB FILENAME CHECK
  REMOTE PROCEDURE: XWB FILENAME CHECK  STATUS: Retired

NUMBER: 1628                            IA #: 1628
  DATE CREATED: NOV 17, 2006            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Remote Procedure                NAME: XWB API LIST
  REMOTE PROCEDURE: XWB API LIST        STATUS: Retired

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:   Added 20061128 
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: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   Added 9/27/19 
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Effective with DSIY*1.5*0 released 9/22/21 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 7/24/25, effective with DSSO*2.0 released 2018 
 APAT will call this RPC to retrieve the values of M variables.  

NUMBER: 1630                            IA #: 1630
  DATE CREATED: JUN 29, 1999            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Remote Procedure                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
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   Added 9/27/19 
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   Added 12/08/21, in order for the Emergency Department
 Integration System (EDIS) to continue to have login functionality once the
 Vista Integration Adapter (VIA) is retired, EDIS requires use of this remote
 procedure call (RPC). Patch EDP*2*16 will allow  EDIS to communicate with this
 RPC.  
SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM
 SUBSCRIBING DETAILS:   In order for the Blind Rehabilitation application to
 continue to have login functionality once the Vista Integration Adapter (VIA)
 is retired, ANRV requires use of this remote procedure call (RPC). Patch
 ANRV*5.1*1 will allow Blind Rehabilitation to communicate with this RPC.  
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 5/13/25 effective with YS*5.01*236 patch. Cloud
 application MHA is migrating from VistALink to Cocytus, to communicate with
 VistA. In order to continue to have login functionality with Cocytus, MHA 
 requires use of this RPC.  

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
SUBSCRIBING PACKAGE: RPC BROKER         ISC: Oakland
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   Added 9/27/19 

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
  STATUS: Active                        DURATION: Till Otherwise Agreed

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
SUBSCRIBING PACKAGE: RPC BROKER         ISC: Oakland

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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   Added 08/07/2025, effective with NHIN*1*26, this RPC is
 defined in the NHIN/DAS context option "NHIN DAS CC", which is defined in the
 REMOTE APPLICATION file entry name "NHIN DAS CC". The RPC is called to provide 
 read only data to the calling system.  

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
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 a vendor to provide the Behavioral Health Lab (BHL) software. BHL is a
 vendor product that calls this VistA RPC.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
 SUBSCRIBING DETAILS:   Added as a subscriber for JLV 2.6 release 
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/18/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce  product sharing the CRMS
 namespace. The CRMS VAHC Remote Application includes the CRMS VAHC Option,
 which includes required RPCs. TIU GET RECORD TEXT is one of the Remote
 Procedures included in the CRMS VAHC Option. The Remote Application uses Data
 Access Services/National Health Information Network (DAS/NHIN) as the
 middleware to interface with VistA.  
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 8/14/25 effective with patch CDSP*1.0*2 Lung
 Cancer Screening Platform version 2 will utilize this RPC to view TIU
 documents that support Lung Cancer Screening coordinators in the jobs and 
 tasks they do for tracking patients through Lung Cancer Screening.  
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   Added 10/28/2025, effective with NHIN*1*26, this RPC is
 defined in the NHIN/DAS context option "NHIN DAS CC", which is defined in the
 REMOTE APPLICATION file entry name "NHIN DAS CC". This is to facilitate the
 CTO office processing of additional community provider data using the existing
 DAS account, remote application, and context option. This is specific to the
 DAS VistA service account which processes Community Care data to VistA. The
 use case is a community provider completing an exam and faxes the results into
 a VAMC. These results are stored in a file share and a process that the CTO
 office is building picks up these result files for processing. The results
 need to be written back to VistA and the originating Consult closed out.  
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI
 SUBSCRIBING DETAILS:   Added 4/3/26 effective with patch DSIR*8.2*17.  The VHA
 Privacy office has requested to have Note text returned which excludes any
 retracted items. We are planning to read through the text and exclude any
 retracted items.  

NUMBER: 1636                            IA #: 1636
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT VAMC PATIENTS
  REMOTE PROCEDURE: ORQPT VAMC PATIENTS
  STATUS: Withdrawn

NUMBER: 1637                            IA #: 1637
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT DEMOG
  REMOTE PROCEDURE: ORQPT DEMOG         STATUS: Withdrawn

NUMBER: 1638                            IA #: 1638
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT ADDR
  REMOTE PROCEDURE: ORQPT ADDR          STATUS: Withdrawn

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
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 1640                            IA #: 1640
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQAL RXN
  REMOTE PROCEDURE: ORQQAL RXN          STATUS: Withdrawn

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
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
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
 SUBSCRIBING DETAILS:   Added 10/23/2006. 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.  

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
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
 SUBSCRIBING DETAILS:   Added 10-23-2006. 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.  

NUMBER: 1644                            IA #: 1644
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQXQA PATIENT
  REMOTE PROCEDURE: ORQQXQA PATIENT     STATUS: Withdrawn

NUMBER: 1645                            IA #: 1645
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQXQA USER
  REMOTE PROCEDURE: ORQQXQA USER        STATUS: Withdrawn

NUMBER: 1646                            IA #: 1646
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT NAME
  REMOTE PROCEDURE: ORQPT NAME          STATUS: Withdrawn

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
 GENERAL DESCRIPTION:   The array returned will be in the format: 
  Vitals IEN 
  Vital Type Short Label - ie 'T' for Temperature 
  Metric measurement (if available), including units. If no metric value 
          is available, the imperial measurement is returned here.  
  Date/time Vital measurement taken 
  Imperial measurement, including units 
  STATUS: Active
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
  DATE ACTIVATED: AUG 19, 2020

NUMBER: 1648                            IA #: 1648
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT DEFAULT PATIENTS
  REMOTE PROCEDURE: ORQPT DEFAULT PATIENTS
  STATUS: Withdrawn

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
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************

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
SUBSCRIBING PACKAGE: MENTAL HEALTH
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

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
SUBSCRIBING PACKAGE: MENTAL HEALTH
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************

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
SUBSCRIBING PACKAGE: MENTAL HEALTH
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  

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
SUBSCRIBING PACKAGE: MENTAL HEALTH
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************

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
SUBSCRIBING PACKAGE: MENTAL HEALTH
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************

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
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

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
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 2/14/25, effective with CDSP*1.0*2 which contain
 the CDSP Task Manager (TM) application. This RPC will be defined in the CDSP
 RPC CONTEXT option. Once a CDSP TM user has selected their relevant team, the 
 application will use the ORQPT TEAM PATIENTS RPC to get a list of patients
 associated with that team. With this, the user will not have to search for
 each individual patient, reducing clinical burden and speeding up their
 workflow. 

NUMBER: 1657                            IA #: 1657
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT WARD PATIENTS
  REMOTE PROCEDURE: ORQPT WARD PATIENTS
  STATUS: Withdrawn

NUMBER: 1658                            IA #: 1658
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT CLINICS
  REMOTE PROCEDURE: ORQPT CLINICS       STATUS: Withdrawn

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
 GENERAL DESCRIPTION:   The following is a capture of the Remote Procedure
 ORQQPS LIST: 
  
 NAME: ORQQPS LIST                       TAG: LIST 
   ROUTINE: ORQQPS                       RETURN VALUE TYPE: ARRAY 
   AVAILABILITY: SUBSCRIPTION DESCRIPTION:   
  Function returns a list of a patient's medications.  
  
 INPUT PARAMETER: PATIENT ID             PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 16               REQUIRED: YES DESCRIPTION:   
  Patient id (DFN) from Patient File (#2).  
  
 INPUT PARAMETER: START DATE/TIME        PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 16               REQUIRED: NO DESCRIPTION:   
  Start date/time in FileMan format indicating what date/time to begin listing
 medications.  
  
 INPUT PARAMETER: STOP DATE/TIME         PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 16               REQUIRED: NO DESCRIPTION:   
  Stop date/time in FileMan format indicating what date/time to end listing 
 medications.  
  
 RETURN PARAMETER DESCRIPTION:   
  Array medications in the format: medication id^nameform (orderable item)^ 
 stop date/time^route^schedule/iv rate^refills remaining 
  
  
    REMOTE PROCEDURE: ORQQPS LIST 
    Function returns a list of a patient's medications.  
  
         TAG^ROUTINE: LIST^ORQQPS 
            KEYWORDS: 
  STATUS: Active
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 8/9/23, effective with SD*5.3*853, Scheduling
 needs to display a patient's medications list in the new VSE GUI 

NUMBER: 1660                            IA #: 1660
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORB LIST
  REMOTE PROCEDURE: ORB LIST            STATUS: Withdrawn

NUMBER: 1661                            IA #: 1661
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORB LIST ON/OFF
  REMOTE PROCEDURE: ORB LIST ON/OFF     STATUS: Withdrawn

NUMBER: 1662                            IA #: 1662
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT PROVIDER TEAM PATIENTS
  REMOTE PROCEDURE: ORQPT PROVIDER TEAM PATIENTS
  STATUS: Withdrawn

NUMBER: 1663                            IA #: 1663
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT PROVIDER TEAMS
  REMOTE PROCEDURE: ORQPT PROVIDER TEAMS
  STATUS: Withdrawn

NUMBER: 1664                            IA #: 1664
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQRA DETAIL
  REMOTE PROCEDURE: ORQQRA DETAIL       STATUS: Withdrawn

NUMBER: 1665                            IA #: 1665
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQRA LIST
  REMOTE PROCEDURE: ORQQRA LIST         STATUS: Withdrawn

NUMBER: 1666                            IA #: 1666
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQRA SEVEN LIST
  REMOTE PROCEDURE: ORQQRA SEVEN LIST   STATUS: Withdrawn

NUMBER: 1667                            IA #: 1667
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQLR LIST
  REMOTE PROCEDURE: ORQQLR LIST         STATUS: Withdrawn

NUMBER: 1668                            IA #: 1668
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQLR HX
  REMOTE PROCEDURE: ORQQLR HX           STATUS: Withdrawn

NUMBER: 1669                            IA #: 1669
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQLR ORDER
  REMOTE PROCEDURE: ORQQLR ORDER        STATUS: Withdrawn

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
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
 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
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   CPRS approved adding Dental as a subscriber for Dental
 Record Manager to this ICR on 8/11/2009 to document existing references. 
 However the update was not made to the ICR until 2/9/18.  
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   Added 08/19/2025, effective with NHIN*1*26, this RPC is
 defined in the NHIN/DAS context option "NHIN DAS CC", which is defined in the
 REMOTE APPLICATION file entry name "NHIN DAS CC". The RPC is called to provide 
 read only data to the calling system. NHIN will use this RPC to facilitate the
 CTO office processing of additional community provider data using the existing
 DAS account, remote application and context option. This is specific to the
 DAS VistA service account which processes Community Care data to VistA. The
 use case is a community provider completes an exam and faxes the results into
 a VAMC. These results are stored in a file share and a process that the CTO
 office is building picks up these results need to be written back to VistA and
 the originating Consult closed out. 
  DATE ACTIVATED: APR 21, 2011

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
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   The Advanced Prosthetics Acquisition Tool (APAT) GUI
 uses RPC ORQQCN DETAIL in several places to return detailed information
 regarding a Consult Request for display on the GUI. This information is
 displayed when the user selects the consult from a list of Prosthetic Suspense 
 items. 
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   Added 2/19/2026, effective with NHIN*1*26, this RPC is 
 defined in the NHIN/DAS context option "NHIN DAS CC", which is defined in the
 REMOTE APPLICATION file entry name "NHIN DAS CC". The RPC is called to provide
 read only data to the calling system. 

NUMBER: 1673                            IA #: 1673
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORK TRIGGER
  REMOTE PROCEDURE: ORK TRIGGER         STATUS: Withdrawn

NUMBER: 1674                            IA #: 1674
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORB FOLLOW-UP STRING
  REMOTE PROCEDURE: ORB FOLLOW-UP STRING
  STATUS: Withdrawn

NUMBER: 1675                            IA #: 1675
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORB DELETE ALERT
  REMOTE PROCEDURE: ORB DELETE ALERT    STATUS: Withdrawn

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
SUBSCRIBING PACKAGE: MENTAL HEALTH
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************

NUMBER: 1677                            IA #: 1677
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORB FOLLOW-UP TYPE
  REMOTE PROCEDURE: ORB FOLLOW-UP TYPE  STATUS: Withdrawn

NUMBER: 1678                            IA #: 1678
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORB FOLLOW-UP ARRAY
  REMOTE PROCEDURE: ORB FOLLOW-UP ARRAY
  STATUS: Withdrawn

NUMBER: 1679                            IA #: 1679
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORB FOLLOW-UP WP
  REMOTE PROCEDURE: ORB FOLLOW-UP WP    STATUS: Withdrawn

NUMBER: 1680                            IA #: 1680
  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: ORQOR DETAIL                    REMOTE PROCEDURE: ORQOR DETAIL
  STATUS: Active
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
 SUBSCRIBING DETAILS:   Added as a subscriber for JLV 2.6 release.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   Added 1/23/2023, effective with DSSV 1.2 Class 2
 product Document Only 
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   Added 09/26/2025, effective with NHIN*1*26, this RPC is
 defined in the NHIN/DAS context option "NHIN DAS CC", which is defined in the
 REMOTE APPLICATION file entry name "NHIN DAS CC". The RPC is called to provide 
 read only data to the calling system. NHIN will call this RPC to facilitate
 the CTO office processing of additional community provider data using the
 existing DAS account, remote application and context option. This is specific
 to the DAS VistA service account which processes Community Care data to VistA.
 The use case is a community provider completes an exam and faxes the results
 into a VAMC. These results are stored in file share and a process that the CTO
 office is building picks up. These results need to be written back to VistA
 and the originating Consult closed out.  
  DATE ACTIVATED: AUG 22, 2017

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
SUBSCRIBING PACKAGE: MENTAL HEALTH
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL

NUMBER: 1682                            IA #: 1682
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT VAMC PATIENTS LONG
  REMOTE PROCEDURE: ORQPT VAMC PATIENTS LONG
  STATUS: Withdrawn

NUMBER: 1683                            IA #: 1683
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT DEFAULT CLINIC DATE RANG
  REMOTE PROCEDURE: ORQPT DEFAULT CLINIC DATE RANG
  STATUS: Withdrawn

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
 GENERAL DESCRIPTION:   NOTE: (Added 3/12/25) 
  New subscribers should be aware that this Remote Procedure is often 
  updated due to Congressional Mandates. Developers should ensure they have 
  the most recent release of the Remote Procedure in their development  
  accounts. 
  STATUS: Active
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   5/10/13-The Mental Health Program Office contracted
 with a vendor to provide the Behavioral Health Lab (BHL) software. BHL is a
 vendor product that calls this VistA RPC.  
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
 SUBSCRIBING DETAILS:   Added 10-23-2006. 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
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 3/12/25, effective with CDSP*1.0*2 Use of this
 RPC will allow the CDSP Task Manager TM)APP to accomplish the following - TM
 will use the ID INFO RPC to get the DOB, SSN, and Full name of a patient so
 that the clinical users of the application can verify they have selected the 
 correct patient and we can display the needed information in the UI.  

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
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.  
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 ********************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **********************************************************
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/31/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS
 namespace.The CRMS VAHC Remote Application includes the CRMS VAHC Option,
 which includes required RPCs.  ORWPT LIST ALL is one of the Remote Procedures
 included in the CRMS VAHC Option.  The Remote Application uses Data Access 
 Services/National Health Information Network (DAS/NHIN) as the middleware to
 interface with VistA.  
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 8/21/24, effective with CDSP*1.0*1 , to include
 ORWPT LIST ALL in the CDSP RPC CONTEXT Option.  The Precision Oncology
 Clinical Decision support (CDS) application delivers an Integrated Resulting
 Service that supports Veterans Affairs (VA) clinicians by streamlining the
 order resulting workflow for molecular tests. The impact on patient care and 
 clinical provider workflow are to reduce bottlenecks in the resulting 
 workflow, improve the clinician experience of processing new lab results and
 co-create with clinicians to facilitate better outcomes for the patients. 
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   Added 08/19/2025, effective with NHIN*1*26, this RPC is
 defined in the NHIN/DAS context option "NHIN DAS CC", which is defined in the
 REMOTE APPLICATION file entry name "NHIN DAS CC". The RPC is called to provide 
 read only data to the calling system. NHIN will use this RPC to facilitate the
 CTO office processing of additional community provider data using the existing
 DAS account, remote application and context option. This is specific to the
 DAS VistA service account which processes Community Care data to VistA. The
 use case is a community provider completes an exam and faxes the results into
 a VAMC. These results are stored in a file share and a process that the CTO
 office is building picks up these results need to be written back to VistA and
 the originating Consult closed out.  

NUMBER: 1686                            IA #: 1686
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWUH POPUP
  REMOTE PROCEDURE: ORWUH POPUP         STATUS: Withdrawn

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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expires on 10/27/17 when
 HMP will be shutdown.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
  
 On 11/3/16, the CPRS team disapproved use of the ORWLR CUMULATIVE REPORT RPC
 and recommended HMP use the EN~LR7OSUM API rather than going through CPRS.  On
 10/3/17, the HMP project team stated the ORWLR CUMULATIVE REPORT RPC is not
 used but is included in the HMP UI CONTEXT option.  
  
 HMP was added as a subscriber on 10/26/17 to document HMP's use of the ICR. 
 If HMP is reactivated in the future, the HMP project team will need to work
 with the CPRS team to resolve this issue.  

NUMBER: 1688                            IA #: 1688
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT PATIENT APPTS
  REMOTE PROCEDURE: ORQPT PATIENT APPTS
  STATUS: 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
SUBSCRIBING PACKAGE: MENTAL HEALTH

NUMBER: 1690                            IA #: 1690
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQVS LIST
  REMOTE PROCEDURE: ORQQVS LIST         STATUS: Withdrawn

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
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
  DATE ACTIVATED: MAR 06, 2014

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
SUBSCRIBING PACKAGE: DENTAL

NUMBER: 1695                            IA #: 1695
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Supported
  TYPE: Remote Procedure                NAME: ORR ORDERS
  REMOTE PROCEDURE: ORR ORDERS          STATUS: Pending

NUMBER: 1697                            IA #: 1697
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWOR CURRENT
  REMOTE PROCEDURE: ORWOR CURRENT       STATUS: Withdrawn

NUMBER: 1698                            IA #: 1698
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWOR CATEGORY
  REMOTE PROCEDURE: ORWOR CATEGORY      STATUS: 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
SUBSCRIBING PACKAGE: DENTAL

NUMBER: 1700                            IA #: 1700
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQVS DETAIL NOTES
  REMOTE PROCEDURE: ORQQVS DETAIL NOTES
  STATUS: Withdrawn

NUMBER: 1701                            IA #: 1701
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQVS DETAIL SUMMARY
  REMOTE PROCEDURE: ORQQVS DETAIL SUMMARY
  STATUS: Withdrawn

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
SUBSCRIBING PACKAGE: DENTAL

NUMBER: 1703                            IA #: 1703
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQXQA ALLPAT
  REMOTE PROCEDURE: ORQQXQA ALLPAT      STATUS: Withdrawn

NUMBER: 1704                            IA #: 1704
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQOR STATI
  REMOTE PROCEDURE: ORQOR STATI         STATUS: Withdrawn

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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
 SUBSCRIBING DETAILS:   Added as a subscriber for JLV 2.6 release.  

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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 1707                            IA #: 1707
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORB SORT METHOD
  REMOTE PROCEDURE: ORB SORT METHOD     STATUS: Withdrawn

NUMBER: 1708                            IA #: 1708
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWDPSO LOAD
  REMOTE PROCEDURE: ORWDPSO LOAD        STATUS: Withdrawn

NUMBER: 1709                            IA #: 1709
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORQQXMB MAIL GROUPS
  REMOTE PROCEDURE: ORQQXMB MAIL GROUPS
  STATUS: Withdrawn

NUMBER: 1710                            IA #: 1710
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT ATTENDING/PRIMARY
  REMOTE PROCEDURE: ORQPT ATTENDING/PRIMARY
  STATUS: Withdrawn

NUMBER: 1711                            IA #: 1711
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWD DEF
  REMOTE PROCEDURE: ORWD DEF            STATUS: Withdrawn

NUMBER: 1712                            IA #: 1712
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQ NULL LIST
  REMOTE PROCEDURE: ORQ NULL LIST       STATUS: Withdrawn

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: 1716                            IA #: 1716
  DATE CREATED: NOV 17, 2006            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Remote Procedure                NAME: SC FIND
  REMOTE PROCEDURE: SC FIND             STATUS: Under Revision

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
  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: 1742                            IA #: 1742
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT PROVIDER PERSONAL LISTS
  REMOTE PROCEDURE: ORQPT PROVIDER PERSONAL LISTS
  STATUS: Withdrawn

NUMBER: 1743                            IA #: 1743
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQLR SEARCH RANGE
  REMOTE PROCEDURE: ORQQLR SEARCH RANGE
  STATUS: Withdrawn

NUMBER: 1744                            IA #: 1744
  DATE CREATED: NOV 17, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQQAL LIST REPORT
  REMOTE PROCEDURE: ORQQAL LIST REPORT  STATUS: Withdrawn

NUMBER: 1745                            IA #: 1745
  DATE CREATED: NOV 17, 2006            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Remote Procedure                NAME: XWB EGCHO STRING
  REMOTE PROCEDURE: XWB EGCHO STRING    STATUS: Retired

NUMBER: 1746                            IA #: 1746
  DATE CREATED: NOV 17, 2006            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Remote Procedure                NAME: XWB EGCHO LIST
  REMOTE PROCEDURE: XWB EGCHO LIST      STATUS: Retired

NUMBER: 1747                            IA #: 1747
  DATE CREATED: NOV 17, 2006            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Remote Procedure                NAME: XWB EGCHO BIG LIST
  REMOTE PROCEDURE: XWB EGCHO BIG LIST  STATUS: Retired

NUMBER: 1748                            IA #: 1748
  DATE CREATED: NOV 17, 2006            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Remote Procedure                NAME: XWB EGCHO SORT LIST
  REMOTE PROCEDURE: XWB EGCHO SORT LIST
  STATUS: Retired

NUMBER: 1749                            IA #: 1749
  DATE CREATED: NOV 17, 2006            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Remote Procedure                NAME: XWB EGCHO MEMO
  REMOTE PROCEDURE: XWB EGCHO MEMO      STATUS: Retired

NUMBER: 1750                            IA #: 1750
  DATE CREATED: NOV 17, 2006            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Remote Procedure                NAME: XWB RPC LIST
  REMOTE PROCEDURE: XWB RPC LIST        STATUS: Retired

NUMBER: 1751                            IA #: 1751
  DATE CREATED: NOV 17, 2006            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Remote Procedure                NAME: XWB CREATE CONTEXT
  REMOTE PROCEDURE: XWB CREATE CONTEXT  STATUS: Active
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: MEDICAL DOMAN WEB SERVICE
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   Added 9/27/19 
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   Added 12/08/21, in order for the Emergency Department
 Integration System (EDIS) to continue to have login functionality once the
 Vista Integration Adapter (VIA) is retired, EDIS requires use of this remote
 procedure call (RPC). Patch EDP*2*16 will allow  EDIS to communicate with this
 RPC.  
SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM
 SUBSCRIBING DETAILS:   In order for the Blind Rehabilitation application to
 continue to have login functionality once the Vista Integration Adapter (VIA)
 is retired, ANRV requires use of this remote procedure call (RPC). Patch
 ANRV*5.1*1 will allow Blind Rehabilitation to communicate with this RPC.  
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 5/13/25 effective with YS*5.01*236 patch. Cloud
 application MHA is migrating from VistALink to Cocytus, to communicate with
 VistA. In order to continue to have login functionality with Cocytus, MHA 
 requires use of this RPC.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 3/23/26, effective with DSIY*1.4*0 released
 2/8/19 APAR granted approval based on the historic usage.  
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 3/23/26, effective with DSSQ*2.0 released
 4/16/20. APAT granted approval based on the historic usage.  
  DATE ACTIVATED: APR 09, 2014

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
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 

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
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
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 

NUMBER: 1785                            IA #: 1785
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWD ODEF
  REMOTE PROCEDURE: ORWD ODEF           STATUS: Withdrawn

NUMBER: 1786                            IA #: 1786
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT PRIMARY TEAM
  REMOTE PROCEDURE: ORQPT PRIMARY TEAM  STATUS: Withdrawn

NUMBER: 1787                            IA #: 1787
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT TEAM PROVIDERS
  REMOTE PROCEDURE: ORQPT TEAM PROVIDERS
  STATUS: Withdrawn

NUMBER: 1788                            IA #: 1788
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWORDG GRPSEQB
  REMOTE PROCEDURE: ORWORDG GRPSEQB     STATUS: Withdrawn

NUMBER: 1789                            IA #: 1789
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWORR GET
  REMOTE PROCEDURE: ORWORR GET          STATUS: Withdrawn

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
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 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
 **************************************************************************
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/18/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce  product sharing the CRMS
 namespace. The CRMS VAHC Remote Application includes the CRMS VAHC Option,
 which includes required RPCs. TIU SIGN RECORD is one of the Remote Procedures
 included in the CRMS VAHC Option. The Remote Application uses Data Access 
 Services/National Health Information Network (DAS/NHIN) as the middleware to
 interface with VistA.  
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 8/14/2025 effective with CDSP*1*2, RPC will allow
 CDSP USER to apply the user's electronic signature to a TIU document while
 evaluating authorization, and validating the user's electronic signature. This
 will be used to associate apps like Lung Cancer Screening Risk Calculator.  

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
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:   Added 10-23-2006. 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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   Added 12/10/21,in order for the Emergency Department
 Integration System (EDIS) to continue to have login functionality once the
 Vista Integration Adapter (VIA) is retired, EDIS requires use of this remote
 procedure call (RPC). Piece 2 (Name) and 13 (Site Name) will be used from
 USERINFO.  Patch EDP*2*16 will allow EDIS to communicate with this RPC.  
SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM
 SUBSCRIBING DETAILS:   Added 11/3/22 Blind Rehabilitation application (ANRV),
 to use this remote procedure call (RPC), in order to continue to have login
 functionality once the Vista Integration Adapter (VIA) is retired effective
 with Patch ANRV*5.1*1. Piece 2 (Name) and 13 (Site Name) will be used from
 USERINFO.  

NUMBER: 1792                            IA #: 1792
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWD SAVE
  REMOTE PROCEDURE: ORWD SAVE           STATUS: Withdrawn

NUMBER: 1793                            IA #: 1793
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWD SIGN
  REMOTE PROCEDURE: ORWD SIGN           STATUS: Withdrawn

NUMBER: 1794                            IA #: 1794
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWD SIGNOK
  REMOTE PROCEDURE: ORWD SIGNOK         STATUS: Withdrawn

NUMBER: 1795                            IA #: 1795
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWD OI
  REMOTE PROCEDURE: ORWD OI             STATUS: Withdrawn

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
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
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP*2.0*2 
  
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
 **************************************************************************
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/18/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce  product sharing the CRMS
 namespace. The CRMS VAHC Remote Application includes the CRMS VAHC Option,
 which includes required RPCs. TIU UPDATE RECORD is one of the Remote
 Procedures included in the CRMS VAHC Option. The Remote Application uses Data
 Access Services/National Health Information Network (DAS/NHIN) as the
 middleware to interface with VistA.  

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
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 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expires on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR to address any potential changes.  
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/17/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace.
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes 
 required RPCs. TIU REQUIRES COSIGNATURE is one of the Remote Procedures 
 included in the CRMS VAHC Option. The Remote Application uses Data Access 
 Services/National Health Information Network (DAS/NHIN) as the middleware to
 interface with VistA.  

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
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
 SUBSCRIBING DETAILS:   ADDED JUNE2009 

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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  TIU*1.0*300 patch is associated with the
 VIAB*1*5 patch to set the APP PROXY ENABLED field to Yes.  
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   Added 08/07/2025, effective with NHIN*1*26, this RPC is
 defined in the NHIN/DAS context option "NHIN DAS CC", which is defined in the
 REMOTE APPLICATION file entry name "NHIN DAS CC". The RPC is called to provide 
 read only data to the calling system.  

NUMBER: 1803                            IA #: 1803
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWDLR DEF
  REMOTE PROCEDURE: ORWDLR DEF          STATUS: Withdrawn

NUMBER: 1804                            IA #: 1804
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWDLR LOAD
  REMOTE PROCEDURE: ORWDLR LOAD         STATUS: Withdrawn

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
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 
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/18/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce  product sharing the CRMS
 namespace. The CRMS VAHC Remote Application includes the CRMS VAHC Option,
 which includes required RPCs. TIU CREATE ADDENDUM RECORD is one of the Remote
 Procedures included in the CRMS VAHC Option. The Remote Application uses Data
 Access Services/National Health Information Network (DAS/NHIN) as the
 middleware to interface with VistA.  

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
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.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   Effective with VPS*1*3 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP*2.0*2 
  
 ****************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ****************************************************
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/16/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace.
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes 
 required RPCs. TIU CREATE RECORD is one of the Remote Procedures included in
 the CRMS VAHC Option. The Remote Application uses Data Access 
 Services/National Health Information Network (DAS/NHIN) as the middleware to
 interface with VistA.  
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 8/21/24, effective with CDSP*1.0*1, to include
 TIU CREATE RECORD in the CDSP RPC CONTEXT Option. CDSP needs to call TIU
 CREATE RECORD to facilitate Lung Cancer Screening Platform version2 (LCSPv2)
 to achieve its goal to aggregate a robust set of data points to support LCS
 (Lung Cancer Screening) coordinators in the jobs and tasks they do for
 tracking patients through Lung Cancer Screening.  

NUMBER: 1807                            IA #: 1807
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORQPT PATIENT TEAM PROVIDERS
  REMOTE PROCEDURE: ORQPT PATIENT TEAM PROVIDERS
  STATUS: Withdrawn

NUMBER: 1808                            IA #: 1808
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWDLR ABBSPEC
  REMOTE PROCEDURE: ORWDLR ABBSPEC      STATUS: Withdrawn

NUMBER: 1809                            IA #: 1809
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWDLR ALLSAMP
  REMOTE PROCEDURE: ORWDLR ALLSAMP      STATUS: Withdrawn

NUMBER: 1810                            IA #: 1810
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWDLR OIPARAM
  REMOTE PROCEDURE: ORWDLR OIPARAM      STATUS: Withdrawn

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
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************

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
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
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
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
 SUBSCRIBING DETAILS:   ADDED JUNE 2009 
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
SUBSCRIBING PACKAGE: VISTA WEB
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   Added 10/2018 
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/30/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace.
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes 
 required RPCs. ORWU VALIDSIG is one of the Remote Procedures included in the
 CRMS VAHC Option. The Remote Application uses Data Access Services/National
 Health Information Network (DAS/NHIN) as the middleware to interface with
 VistA.  

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
SUBSCRIBING PACKAGE: MENTAL HEALTH
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************

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
 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.  
  DATE ACTIVATED: APR 21, 2011

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
 GENERAL DESCRIPTION:   Returns a list of admissions for a patient (for visit
 selection).  
  
 Input: 
       DFN   [required]  = IEN from the Patient file #2 
  
 Output: 
      LST(n)=DATA  delimited by "^"  where n=1,2,3,4,. . .  
  
 Return Parameter Description 
  
 If successful: LST(n)=p1^p2^p3^p4^p5^p6 
  
 Where: p1 := MOVEMENT DATE/TIME p2 := IEN from Hospital Location file#44 p3 :=
 Location name-the external value from file #44,.01 p4 := Type name -the
 external value from the Facility Movement Type file #405.1,.01 p5 := IEN from
 Patient Movement file #45 p6 := IEN from TIU DOCUMENT file #8925,otherwise 0
 if no discharge summary p7 := 1 if there is discharge summary, otherwise 0 
  STATUS: Active
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
SUBSCRIBING PACKAGE: MENTAL HEALTH
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
 SUBSCRIBING DETAILS:   Added as a subscriber for JLV release 2.6 

NUMBER: 1818                            IA #: 1818
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWU VALDT
  REMOTE PROCEDURE: ORWU VALDT          STATUS: Withdrawn

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
SUBSCRIBING PACKAGE: MENTAL HEALTH

NUMBER: 1820                            IA #: 1820
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWD FORMID
  REMOTE PROCEDURE: ORWD FORMID         STATUS: Withdrawn

NUMBER: 1821                            IA #: 1821
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWD GET4EDIT
  REMOTE PROCEDURE: ORWD GET4EDIT       STATUS: Withdrawn

NUMBER: 1822                            IA #: 1822
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWD VALIDACT
  REMOTE PROCEDURE: ORWD VALIDACT       STATUS: Withdrawn

NUMBER: 1823                            IA #: 1823
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWD SAVEACT
  REMOTE PROCEDURE: ORWD SAVEACT        STATUS: Withdrawn

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
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE

NUMBER: 1825                            IA #: 1825
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWDCSLT LOOK200
  REMOTE PROCEDURE: ORWDCSLT LOOK200    STATUS: Withdrawn

NUMBER: 1826                            IA #: 1826
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWDCSLT DEF
  REMOTE PROCEDURE: ORWDCSLT DEF        STATUS: Withdrawn

NUMBER: 1827                            IA #: 1827
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWD PROVKEY
  REMOTE PROCEDURE: ORWD PROVKEY        STATUS: Withdrawn

NUMBER: 1828                            IA #: 1828
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWDGX LOAD
  REMOTE PROCEDURE: ORWDGX LOAD         STATUS: Withdrawn

NUMBER: 1829                            IA #: 1829
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWDPS LOAD
  REMOTE PROCEDURE: ORWDPS LOAD         STATUS: Withdrawn

NUMBER: 1830                            IA #: 1830
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWDRA DEF
  REMOTE PROCEDURE: ORWDRA DEF          STATUS: Withdrawn

NUMBER: 1831                            IA #: 1831
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWDGX VMDEF
  REMOTE PROCEDURE: ORWDGX VMDEF        STATUS: Withdrawn

NUMBER: 1832                            IA #: 1832
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWDPS DEF
  REMOTE PROCEDURE: ORWDPS DEF          STATUS: Withdrawn

NUMBER: 1833                            IA #: 1833
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWDLR STOP
  REMOTE PROCEDURE: ORWDLR STOP         STATUS: Withdrawn

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
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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 1836                            IA #: 1836
  DATE CREATED: OCT 13, 2023
  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
 GENERAL DESCRIPTION:   When CPRS v33MOE releases, this RPC call will be
 replaced in the CPRS GUI application. The new RPC call is ORNEWPERS NEWPERSON.
 The plan is to remain backward compatibility with ORWU NEWPERS while allowing
 expansion capabilities with ORNEWPERSON NEWPERSON.  
  
 For anyone updating ORNEWPERSON NEWPERSON, remember that you must ensure that
 ORWU NEWPERS still functions correctly.  
  STATUS: Active
KEYWORDS: ORNEWPERS
KEYWORDS: ORNEWPERS NEWPERSON
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.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
 SUBSCRIBING DETAILS:   Added 10-23-2006. 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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 ********************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ********************************************************
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added effective 10/13/23, effective with patch
 CDSP*1*0, CDSP is developing a Precision Oncology workflow to automatically 
 ingest genetic test results into VistA and VistA imaging. The workflow needs
 to identify patients based on demographic data present in test     results.
 This RPC is used to get a list of providers in order to search for a provider
 who ordered a genetic test and subsequently notify the provider about the test
 results.  
  DATE ACTIVATED: OCT 16, 2023

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
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
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
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************

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
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

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
  STATUS: Active
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
 SUBSCRIBING DETAILS:   Added as a subscriber for JLV 2.6 release 
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added July 23, 2025, effective with CDSP*1*2, This RPC
 will allow CDSP to retrieve the report text for a selected report on the CPRS
 GUI Reports tab.  The report output will be used in the Lung Cancer Screening
 Risk Calculator and other CDSP Applications.  
  DATE ACTIVATED: DEC 20, 2009

NUMBER: 1842                            IA #: 1842
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORWRP PRINT REPORT
  REMOTE PROCEDURE: ORWRP PRINT REPORT  STATUS: Withdrawn

NUMBER: 1843                            IA #: 1843
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORWLR REPORT LISTS
  REMOTE PROCEDURE: ORWLR REPORT LISTS  STATUS: Withdrawn

NUMBER: 1844                            IA #: 1844
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: ORWLR CUMULATIVE SECTION
  REMOTE PROCEDURE: ORWLR CUMULATIVE SECTION
  STATUS: Withdrawn

NUMBER: 1845                            IA #: 1845
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: ORWU URGENCY
  REMOTE PROCEDURE: ORWU URGENCY        STATUS: Withdrawn

NUMBER: 1846                            IA #: 1846
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA1846
  ID: SC(
GLOBAL REFERENCE: SC(D0,0)
FIELD NUMBER: 3.5                       FIELD NAME: DIVISION
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: STOP CODE NUMBER
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2502                      FIELD NAME: NON-COUNT CLINIC? (Y OR N)
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2503                      FIELD NAME: CREDIT STOP CODE
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   For a selected patient, DSS reads the entire zero node
 into a local variable. The fields above are used.  
GLOBAL REFERENCE: SC(D0,I)
FIELD NUMBER: 2505                      FIELD NAME: INACTIVATE DATE
  LOCATION: I;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2506                      FIELD NAME: REACTIVATE DATE
  LOCATION: I;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,S,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: LENGTH OF APP'T
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 310                       FIELD NAME: APPOINTMENT CANCELLED?
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   DSS examines the APPOINTMENT DATE/TIME field (.01)
 within the APPOINTMENT multiple (1900) and within that multiple, the PATIENT
 multiple (2). The entire zero node is read into a local variable. The fields
 above are used.  
GLOBAL REFERENCE: SC(D0,S,D1,1,D2,C)
FIELD NUMBER: 303                       FIELD NAME: CHECK OUT
  LOCATION: C;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,S,D1,1,D2,OB)
FIELD NUMBER: 9                         FIELD NAME: OVERBOOK
  LOCATION: OB;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,SL)
FIELD NUMBER: 1912                      FIELD NAME: LENGTH OF APP'T
  LOCATION: SL;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1913                      FIELD NAME: VARIABLE APP'NTMENT LENGTH
  LOCATION: SL;2                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   In addition to fields which are supported by DBIA
 10040, DSS Extracts will reference the following data from the HOSPITAL 
 LOCATION file (#44).  
   
 Numerous DSS extract files contain a field (e.g., WARD, CLINIC NAME, LOSING
 WARD, OR ROOM NUMBER, LOCATION (WARD OR CLINIC)) which is a pointer to the
 HOSPITAL LOCATION file (#44).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham
SUBSCRIBING PACKAGE: EVENT CAPTURE      ISC: Albany
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  ISC: Hines

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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany
SUBSCRIBING PACKAGE: DIETETICS          ISC: Hines
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 03/22/21, effective with Mental Health's Suicide
 Prevention Project, patch YS*5.01*135.  

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                            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: Under Revision                DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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 - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany
SUBSCRIBING PACKAGE: SURGERY
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
 SUBSCRIBING DETAILS:   ADDED JUNE 2009 

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
FIELD NUMBER: 3                         FIELD NAME: PRINT ON ABNORMAL REPORT
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: GENERATE ABNORMAL ALERT?
  LOCATION: 0;4                         ACCESS: 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   
     ADDED 9/22/2022, effective with DSSV*1.1 
     Fields added: #3 and #4 
     DSS Class 3 product 
     Document Only 

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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
GLOBAL REFERENCE: RA(79,D0,L,0)
FIELD NUMBER: .01                       FIELD NAME: IMAGING LOCATION
  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.  
  
 Revision History: 
  
 11/05/2024 Added IMAGING LOCATION field for use by MEDICOM.  
  
 Radiology Custodian Noted that both 79'& 79.1's top-level .01's are pointers
 themselves to the INSTITUTION & HOSPITAL LOCATION files.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MEDICOM
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Added 9/27/24 effective with Patch MECH 1.0 MEDICOM
 TECHNOLOGIES is requesting to read via the FileMan, the following fields: 
 DIVISION (#.01), IMAGING LOCATION (#79.01;.01) 

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
FIELD NUMBER: 6                         FIELD NAME: TYPE OF IMAGING
  LOCATION: 0;6                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 19                        FIELD NAME: INACTIVE
  LOCATION: 0;19                        ACCESS: Read w/Fileman
FIELD NUMBER: 21                        FIELD NAME: CREDIT METH
  LOCATION: 0;21                        ACCESS: Read w/Fileman
FIELD NUMBER: 25                        FIELD NAME: RAD/NUC MED DIVISION
  LOCATION: DIV;1                       ACCESS: 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
KEYWORDS: MEDICOM
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Patch MECH*1.0*1 processes HL7 new-order messages about
 imaging studies performed in the community but not entered through VistA.  In
 order to do this, it needs to invoke Radiology routines and make FileMan calls
 to add entries to the RAD/NUC MED PATIENT File (#70) (for existing VA
 patients), the ORDER File (#100), and the RAD/NUC MED ORDERS File (#75.1). The
 patch then creates an HL7 order-update message that transmits the study's 
 accession number to the sender. ADDED 3/2/2022, effective with MECH*1.0*1 
 Medicom Class 3 product Document Only 

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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham
 SUBSCRIBING DETAILS:   DSS EXTRACTS uses a FileMan read (EN^DIQ1) to obtain
 data from the ABBREVIATION field (#2).  

NUMBER: 1862                            IA #: 1862
  FILE NUMBER: 220.2                    GLOBAL ROOT: DIC(220.2,
  DATE CREATED: DEC 04, 1996            CUSTODIAL PACKAGE: DENTAL
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA1862
  ID: DIC(220.2,
GLOBAL REFERENCE: DIC(220.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CLASSIFICATION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The DSS Extracts DENTAL EXTRACT file (#727.806)
 contains a field, PATIENT CATEGORY, which is a pointer to the DENTAL
 CLASSIFICATION file (#220.2).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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(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: .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.  
GLOBAL REFERENCE: DGPM(D0,'USR')
FIELD NUMBER: 100                       FIELD NAME: ENTERED BY
  LOCATION: USR;1                       ACCESS: Read w/Fileman
FIELD NUMBER: 101                       FIELD NAME: ENTERED ON
  LOCATION: USR;2                       ACCESS: Read w/Fileman
 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Data is extracted from the Patient Movement (#405) file
 and used as part of the patient sync that syncs the VistA data with the JSON
 Data System (JDS).  This data is then used to create the patient record that
 is available to the users.  
  
 Fields used by HMP are:  Date/Time (#.01), Transaction (#.02), Attending 
 Physician (#.19), Facility Treating Specialty (#.09) and Ward Location (#.06). 
  
 HMP is also using the ATID1, APMV, B and C cross references to look up data in
 the file. 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
 **************************************************************************
  DATE ACTIVATED: OCT 26, 2018

NUMBER: 1866                            IA #: 1866
  FILE NUMBER: 408.32                   GLOBAL ROOT: DG(408.32,
  DATE CREATED: DEC 05, 1996            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA1866
  ID: DG(408.32,
GLOBAL REFERENCE: DG(408.32,D0,0)
FIELD NUMBER: .02                       FIELD NAME: CODE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   DSS Extracts references the following data from the
 MEANS TEST STATUS file (#408.32).  
   
 The use of utilities to extract this information will be investigated prior to
 the release of a verified version of DSS Extracts (e.g., $$LST^DGMTU).  
   
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

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
SUBSCRIBING PACKAGE: IFCAP              ISC: Washington/Silver Spring

NUMBER: 1868                            IA #: 1868
  FILE NUMBER: 409.5                    GLOBAL ROOT: SDV(
  DATE CREATED: DEC 05, 1996            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA1868
  ID: SDV(
GLOBAL REFERENCE: SDV(D0,0)
FIELD NUMBER: 2                         FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DIVISION
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SDV(D0,CS,D1,0)
FIELD NUMBER: 3                         FIELD NAME: ASSOCIATED CLINIC
  LOCATION: CS;3                        ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   DSS examines the CLINIC STOP CODE multiple (#409.51)
 using the "B" cross reference.  
 GENERAL DESCRIPTION:   DSS Extracts references the following data from the
 SCHEDULING VISITS file (#409.5).  
   
 As of 12/5/96, it is understood that this file may soon become obsolete as
 part of the ambulatory care development.  
   
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

NUMBER: 1871                            IA #: 1871
  FILE NUMBER: 720.2                    GLOBAL ROOT: ECK(
  DATE CREATED: DEC 05, 1996            CUSTODIAL PACKAGE: EVENT CAPTURE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA1871
  ID: ECK(
GLOBAL REFERENCE: ECK(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
 EVENT CODE SCREENING file (#720.2).  
   
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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=<current version number> 
   
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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(
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
KEYWORDS: SPINAL CORD
KEYWORDS: DSS
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
 SUBSCRIBING DETAILS:   
  
SUBSCRIBING PACKAGE: MYHEALTHEVET
  DATE ACTIVATED: JAN 23, 2007

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,
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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany
SUBSCRIBING PACKAGE: MYHEALTHEVET

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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
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: 1879                            IA #: 1879
  FILE NUMBER: 50.8                     GLOBAL ROOT: PS(50.8,
  DATE CREATED: DEC 11, 1996            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA1879
  ID: PS(50.8,
GLOBAL REFERENCE: PS(50.8,D0,0)
FIELD NUMBER: .01                       FIELD NAME: IV ROOM
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(50.8,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DATE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   From the DATE multiple (50.803).  
GLOBAL REFERENCE: PS(50.8,D0,2,D1,2,D2,0)
FIELD NUMBER: .01                       FIELD NAME: IV DRUG
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: AVERAGE DRUG COST PER UNIT
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: TYPE
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   From the IV DRUG multiple (50.805).  
GLOBAL REFERENCE: PS(50.8,D0,2,D1,2,D2,1,D3,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DISPENSED UNITS (PATIENT)
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: RETURNED UNITS (PATIENT)
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: WARD PTR
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: CANCELED UNITS (PATIENT)
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   DSS reads the entire zero node into a local variable.
 The above fields from the PATIENT multiple (50.806) are used.  
 GENERAL DESCRIPTION:   DSS Extracts references the following data from the IV
 STATS file (#50.8).  
   
 DSS uses the "AC" cross reference on the IV DRUG field.  Global:      
 ^PS(50.8,IV_ROOM,2,DATE,2,"AC",FILE_52_.6 or .7,IEN_addtv_or_soln,IV_DRUG#) 
  Example: ^PS(50.8,2,2,2910513,2,"AC",52.6,24,2) = 
           ^PS(50.8,2,2,2910513,2,"AC",52.7,7,3) = 
   
 References to the IV STATS file (#50.8), occur 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: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

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
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
  ISC: Birmingham

NUMBER: 1881                            IA #: 1881
  FILE NUMBER: 52.7                     GLOBAL ROOT: PS(52.7,
  DATE CREATED: DEC 12, 1996
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA1881
  ID: PS(52.7,
GLOBAL REFERENCE: PS(52.7,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
 SOLUTIONS file (#52.7).  
   
 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: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

NUMBER: 1882                            IA #: 1882
  DATE CREATED: DEC 12, 1996
  CUSTODIAL PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
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: 1883                            IA #: 1883
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: DEC 13, 1996
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA1883
  ID: PS(55,
GLOBAL REFERENCE: PS(55,D0,IV,D1,2)
FIELD NUMBER: .22                       FIELD NAME: IV ROOM
  LOCATION: 2;2                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   From the IV multiple (55.01).  
 GENERAL DESCRIPTION:   DSS Extracts references the following data from the
 PHARMACY PATIENT file (#55).  
   
 This integration agreement is for version 4.5 (or less) of Inpatient 
 Medications. When version 5.0 of Inpatient Medications is released, this
 reference must be replaced. At that time, the information will be returned as
 part of the data stream that is passed in PSIVSTAT.  
   
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 4.5
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

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 EMAIL GROUP DEV using Microsoft Outlook.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
  ISC: Birmingham

NUMBER: 1885                            IA #: 1885
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: DEC 19, 1996            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: File
  NAME: IFCAP Vendor Display Format  $P(.VA(200,,400),U,2)
  ID: VA(200
 GENERAL DESCRIPTION:   
  
 This field stores the user's desired format for displaying a list of vendors. 
 Terminal users have requested a minimum number of lines per vendor so that
 vendors won't scroll of the top of the screen. The Horizontal (2 line) format
 and a Vertical 4-6 line format are illustrated below.  Entry of VS or HS will
 make that choice automatically throughout this session, i.e. until you log in
 again.  Entry of VA or HA will mean you won't be prompted for a choice again.  
  
  
                                 Normal Usage 
  
 Select VENDOR NAME: ?? 
  
 Choose from: 
    1               AOBC SEE WHAT SHOWS UP FOR LONG NAME   How should Vendor
 Addresses be displayed? :  (HR/VR/HS/VS/HA/VA): VR// ? 
  
 'Session' means until you log in again. 'Always' means never seeing this 
 again.  
  
      Select one of the following: 
  
           HR        Horizontal (minimum # of lines) -- Reask every selection 
           VR        Vertical (Postal Format) -- Reask '' 
           HS        Horizontal -- every time this Session 
           VS        Vertical   -- '' 
           HA        Always Horizontal -- never Ask again 
           VA        Always Vertical   -- '' 
  
  
  
 Field can also be set explicitly via the 
              Enter/Edit Vendor Display Format option 
  
  
  
  
 200,402       Vendor Display Format  400;2 SET 
  
               VENDOR DISPLAY FORMAT     
                                 'HR' FOR Horizontal (minimum # of lines) - 
                                      Reask every list; 
                                 'VR' FOR Vertical (Postal Format) - ''; 
                                 'HS' FOR Horizontal -- rest of Session; 
                                    5               CENTRAL BUSINESS SERVICES 
                                 AND SUPP      EDI VENDOR   202 491- 0231  NO.
 5 
  
                                 FMS VENDOR CODE:NAME: 37844821002: SPECIAL 
                                 FACTORS: VENDOR MUST BE CALLED PRIOR TO
 MAILING 
                                 PO ORDERING ADDRESS: 4000 RESERVOIR ROAD 
                                                    WASHINGTON, DC 20008 
                                    6               **MILAN   >> INACTIVE   No 
                                 substitute defined 
                                    7               SAM'S      512-876-4433 
 NO.  
                                 7 FMS VENDOR CODE:NAME: MISC1234501: SPECIAL 
                                 FACTORS: ORDERING ADDRESS:  4 HIGH ST 
                                                    AUSTIN, TX 75434 
                                    8               GENERIC GENERAL STORE     
                                 301-427-3700  NO. 8 FMS VENDOR CODE:NAME: 
                                 123456798: SPECIAL FACTORS: ORDERING ADDRESS: 
                                 111 MAIN STREET 
                                                    SILVER SPRING, MD 20910 
                                  
                                  
                                 Horizontal Format Example: 
                                  
                                    4              DAN'S DOG FOOD SUPPLY  `14 
                                 123-4567 
                                        Order From: 1234 STATE STREET; ; ; ; ZW 
                                 DQ, MD 20708 
                                    5               CENTRAL BUSINESS SERVICES 
                                 AND SUPP  `5  202 491-0231 
                                             FMS #-NAME: 37844821002- 
                                             Note: VENDOR MUST BE CALLED PRIOR 
                                 TO MAILING PO 
                                        EDI   Fax: 301 427-3700  Order From: 
                                 4000 RESERVOIR ROAD; SUITE 200; ; 
                                             WASHINGTON, DC 20008 
                                    6               **MILAN   >> INACTIVE   No 
                                 substitute defined 
                                         
                                    7               SAM'S  `7  512-876-4433 
 FMS 
                                 #-NAME: MISC1234501- 
                                        Order From: 4 HIGH ST; CHECK THIS OUT;
 ; 
                                 ; AUSTIN, TX 75434 
                                  
                                  
                                 DESCRIPTION 
                                 This field stores the user's desired format
 for 
                                 displaying a list of vendors.  Terminal users 
                                 have requested a minimum number of lines per 
                                 vendor so that vendors won't scroll of the top 
                                 of the screen. The Horizontal (2 line) format 
                                 and a Vertical 4-6 line format are illustrated 
                                 below.  Entry of VS or HS will make that
 choice 
                                 automatically throughout this session, i.e.  
                                 until you log in again.  Entry of VA or HA
 will 
                                 mean you won't be prompted for a choice again. 
  
  
               SCREEN:           S DIC("S")="I Y'=""B""!(DUZ(0)=""@"")" 
               EXPLANATION:      Programmers have an additional option.  
               SOURCE OF DATA:   User decision 
               DATA DESTINATION: PRCH69 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IFCAP              ISC: Washington/Silver Spring

NUMBER: 1886                            IA #: 1886
  FILE NUMBER: 631                      GLOBAL ROOT: HBHC(631,
  DATE CREATED: JAN 16, 1997
  CUSTODIAL PACKAGE: HOME BASED PRIMARY 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
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: HOME BASED PRIMARY 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
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
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
 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,"CLV")                                          Optional 
         This encounter is related to Camp Lejeune.  
         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,"PL CLV")               Required for PCE      Optional for PL 
         This problem is related to Camp Lejeune.  
         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,"READER")                                       Optional 
         The person who read the skin test.  
         Format: Pointer to New Person file (200) 
     "SKIN TEST",i,"ORD PROVIDER")                                 Optional 
         The provider who ordered this skin test.  
         Format: Pointer to New Person file (200) 
     "SKIN TEST",i,"D/T PLACEMENT RECORDED")                       Optional 
         The date and time of documentation of the placement 
         of the skin test.  
         Format: FileMan Internal Format for date/time 
     "SKIN TEST",i,"ANATOMIC LOC")                                 Optional 
         The anatomic location of skin test placement.  
         Format: Pointer to Imm Administration Site (Body) 
                 file (920.3) 
     "SKIN TEST",i,"D/T READING RECORDED")                         Optional 
         The date and time of documentation of the reading 
         of the skin test.  
         Format: FileMan Internal Format for date/time 
     "SKIN TEST",i,"READING COMMENT")                              Optional 
         Comment related to the reading of the patient's 
         skin test.  
         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.  
  
    Effective with PX*1*209, the "IMMUNIZATION" node contains modifications 
    to include additional fields: Event Info Source, Dosage, Route, Admin 
    Site, Lot #. These new fields are optional, and therefore backward 
    compatible. 
     
    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,"LOT NUM")                                   Optional 
         The lot number of the Immunization entered for this event.  
         Format:  Pointer to Immunization Lot file (9999999.41) 
     "IMMUNIZATION",i,"INFO SOURCE")                               Optional 
         The source of the information obtained for this immunization 
             event.  
         Format:  Pointer to Immunization Info Source file (920.1) 
     "IMMUNIZATION",i,"ADMIN ROUTE")                               Optional 
         The method this vaccine was administered.  
         Format:  Pointer to Imm Administration Route file (920.2) 
     "IMMUNIZATION",i,"ANATOMIC LOC")                              Optional 
         The area of the patient's body through which the vaccine was 
             administered. 
         Format:  Pointer to Imm Administration Site (Body) file (920.3) 
     "IMMUNIZATION",i,"DOSE")                                      Optional 
         The amount of vaccine product administered for this 
         immunization.  
         Format: Numeric (between 0 and 999, 2 fractional digits) 
     "IMMUNIZATION",i,"DOSE UNITS")                                Optional 
         The units that reflect the actual quantity of the 
         vaccine product administered.  
         Format: Pointer to the UCUM Codes file (#757.5) 
     "IMMUNIZATION",i,"VIS",SEQ #,0)=VISIEN^DATE                   Optional 
         The Vaccine Information Statement (VIS) offered to or 
         given to the patient before administration of the 
         immunization, and the date it was offered or given.  
         Format: "VISIEN" is a pointer to the Vaccine Information 
         Statement file (#920). "DATE" is a date (without time) in 
         FileManager internal format.  
         NOTE: If the caller is updating a previously recorded 
         immunization: 
         1) If the caller passes in VIS data in the "VIS" 
            subscript, the system will purge the previously filed 
            VIS data before filing the updates. 
         2) If the caller does not pass in any VIS data, the 
            previously filed VIS data persists.  
         3) If the caller wants to delete the previously filed VIS 
            without replacing it with anything else, that is done 
            explicitly by setting the "VIS" subscript as follows: 
            "IMMUNIZATION",i,"VIS")="@" 
     "IMMUNIZATION",i,"REMARKS",SEQ #,0)                           Optional 
         Comments related to the immunization encounter with 
         the patient.  
         Format: Free-text in the format of a FileManager 
         word-processing field.  
         NOTE: If the caller is updating a previously recorded 
         immunization: 
         1) If the caller passes in remarks in the "REMARKS" 
            subscript, the system will purge the previously filed 
            remarks before filing the updates.  
         2) If the caller does not pass in any remarks, the 
            previously filed remarks persist.  
         3) If the caller wants to delete the previously filed 
            remarks without replacing it with anything else, 
            that is done explicitly by setting the "REMARKS" 
            subscript as follows: "IMMUNIZATION",i,"REMARKS")="@"  
     "IMMUNIZATION",i,"ORD PROVIDER")                              Optional 
         The provider who ordered the immunization.  
         Format: Pointer to New Person file (#200).  
     "IMMUNIZATION",i,"WARNING ACK")                               Optional 
         This field indicates acknowledgement of a 
         contraindication/refusal event warning for this 
         immunization with the decision to proceed with 
         administration.  
         Format: [ 1 | 0 | null ] 
     "IMMUNIZATION",i,"OVERRIDE REASON"                            Optional 
         This is the reason for overriding the warning of 
         existing contraindication and/or refusal reasons.  
         Format: Free Text (3-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 ]| 
  
  
    IMM CONTRA/REFUSAL:  The "IMM CONTRA/REFUSAL" node may have multiple 
    entries (i). To delete the entire "IMM CONTRA/REFUSAL" entry, set the 
    "DELETE" node to 1.  
        
    SUBSCRIPT DESCRIPTION: 
        
     "IMM CONTRA/REFUSAL",i,"CONTRA/REFUSAL")                      Required 
         The Contraindication or Refusal Reason.  
         Format:  Variable Pointer to: IMM Contraindication 
         Reasons file (920.4) or IMM Refusal Reasons file (920.5).  
     "IMM CONTRA/REFUSAL",i,"IMMUN")                               Required 
         The immunization contraindicated or refused.  
         Format:  Pointer to Immunization file (9999999.14) 
     "IMM CONTRA/REFUSAL",i,"WARN UNTIL DATE")                     Optional 
         The date until which a warning should be given for this 
         contraindication/refusal.  
         Format: FileManager Internal Format for date.  
     "IMM CONTRA/REFUSAL",i,"EVENT D/T")                           Optional 
         The date/time of this contraindication/refusal event.  
         Format:  FileManager Internal Format for date/time. 
     "IMM CONTRA/REFUSAL",i,"ENC PROVIDER")                        Optional 
         This is the provider who recorded the 
         contraindication/refusal event.  
         Format:  Pointer to New Person file (#200).  
     "IMM CONTRA/REFUSAL",i,"COMMENT")                             Optional 
         Comment.  
         Format:  Free Text (1-245 characters).  
     "IMM CONTRA/REFUSAL",i,"DELETE")                              Optional 
         This is a flag that denotes deletion of the IMM 
         Contra/Refusal 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
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:   ADDED 11/28/2006 
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   ADDED 10/10/2008 
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
 SUBSCRIBING DETAILS:   ADDED 8/28/09 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 8/14/18.  Added 03/12/24, in patch DSSO*2.0*6,
 APAT will create visits for Prosthetic Billing.  
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 2/21/23, the IZ Gateway (IZG) project, as a part
 of VDIF (Middleware), will be using DATA2PCE^PXAPI to store immunization data
 that is sent by the State IISs (Immunization Information Systems) via the
 CDC's IZ Gateway to update the patient's EHR in VistA. This will enable VA 
 healthcare providers to view the patient's immunizations that were 
 administered at a non-VA facility.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   Added 3/1/23, effective with DSSV*1*2, a Class 2 patch,
 using DATA2PCE^PXAPI to store health factors in historical event visits.  
  DATE ACTIVATED: JAN 10, 2017

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
  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 
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   ADDED 5/29/2020 

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 
                   Camp Lejeune 
             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 
             9. Camp Lejeune 
  
      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 
             13. Camp Lejeune 
  
      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
  DATE ACTIVATED: JAN 10, 2017

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 
             Camp Lejeune 
          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 
          13. Camp Lejeune 
  
 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 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).  
  
 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 
             Camp Lejeune 
          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 
          13. Camp Lejeune 
  
 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 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).  
  
 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
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   Added 11/30/22, effective with DSSV*1.1. Document only
 Class 2 

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
  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:   APIs to obtain encounter information.  
  
 Updated 1/16/2026 to include the addition of V STANDARD CODES, and the
 addition of the 900 nodes in the VISIT and V POV files.  The 900 nodes replace
 the 800 nodes to store the Service Connected and Special Authority (SC/SA)
 applicability for an encounter. For encounters created after the installation
 of PX*1*244 an 800 node will be constructed from the 900 node to provide
 backwards compatibility. Effective with patch PX*1*244.  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 1.0
COMPONENT/ENTRY POINT: GETENC
 COMPONENT DESCRIPTION:   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 ^ 
     
    Returned Data: 
    Identical to that returned by ENCEVENT^PXAPI, see above. 
    If the input data matches more than one Visit file entry 
    there will be sets of 
    ^TMP("PXKENC",$J,VISIT IEN) entries for each of them.  
COMPONENT/ENTRY POINT: ENCEVENT
 COMPONENT DESCRIPTION:   
   ENCEVENT^PXAPI(VISITIEN,DONTKILL) 
     
    This API was developed to extract all PCE encounter data 
    for a single encounter. The data represents elements 
    that are stored in the Visit file 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 initialized. Enter 0 or 
                 "" (NULL) to initialize the array, and 1 
                 to retain it.  
     
    Returned Data: 
     
    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: Name spaced variable: "PXKENC".  
     Subscript 2: Job Number, $J. 
     Subscript 3: Internal Entry Number (IEN) of the Visit.  
     Subscript 4: String representing the Visit or V file data category. 
                  "CPT"   = V CPT (procedure)     #9000010.18 
                  "HF"    = V Health Factors      #9000010.23 
                  "ICR"   = V Imm Contra/Refusal  #9000010.707 
                            Events  
                  "IMM"   = V Immunization        #9000010.11 
                  "PED"   = V Patient Ed          #9000010.16 
                  "POV"   = V POV (diagnosis)     #9000010.07 
                  "PRV"   = V Provider            #9000010.06 
                  "SC"    = V Standard Codes      #9000010.71 
                  "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: DD node/subscript where the data is stored.  
                  Only the DD nodes that have data are 
                  published.  
     
    Returned Data: 
     
 The data to the right of the equal sign is a copy the data in the PCE file. In
 the example below, the encounter consists of the Visit file entry with
 IEN=7589 and the various V-file entries pointing to it. For example, 
     
 ^TMP("PXKENC",2241218,7589,"CPT",3445,0)="99601^140^7589^829^^^^^^^^^^^^1" is
 the 0 node of the V CPT entry IEN=3445. You can determine what each piece of
 data is by examining the data dictionary for V CPT. The same applies for the
 12 and 812 nodes. In this example, the other V CPT nodes do not have any data
 so they are not published.  
  
    Output Example: 
  
 ^TMP("PXKENC",2241218,7589,"CPT",3445,0)="99601^140^7589^829^^^^^^^^^^^^1" 
 ^TMP("PXKENC",2241218,7589,"CPT",3445,12)=3260106.165547 
 ^TMP("PXKENC",2241218,7589,"CPT",3445,812)="^170^19" 
 ^TMP("PXKENC",2241218,7589,"HF",137,0)="648303^140^7589" 
 ^TMP("PXKENC",2241218,7589,"HF",137,12)=3260108.165546 
 ^TMP("PXKENC",2241218,7589,"HF",137,220)="0^623" 
 ^TMP("PXKENC",2241218,7589,"HF",137,811)="This is a HF test comment." 
 ^TMP("PXKENC",2241218,7589,"HF",137,812)="^170^19" 
 ^TMP("PXKENC",2241218,7589,"HF",138,0)="550276^140^7589" 
 ^TMP("PXKENC",2241218,7589,"HF",138,12)=3260108.165546 
 ^TMP("PXKENC",2241218,7589,"HF",138,220)="30^533" 
 ^TMP("PXKENC",2241218,7589,"HF",138,811)="This is a HF test comment." 
 ^TMP("PXKENC",2241218,7589,"HF",138,812)="^170^19" 
 ^TMP("PXKENC",2241218,7589,"PED",67,0)="39^140^7589^^^1" 
 ^TMP("PXKENC",2241218,7589,"PED",67,12)="3240701.075^^^991" 
 ^TMP("PXKENC",2241218,7589,"PED",67,812)="^170^19" 
 ^TMP("PXKENC",2241218,7589,"POV",920,0)="503195^140^7589^827^^^^^^^^P" 
 ^TMP("PXKENC",2241218,7589,"POV",920,12)="3260106.165547^^^991" 
 ^TMP("PXKENC",2241218,7589,"POV",920,800,0,0)="0^1^0" 
 ^TMP("PXKENC",2241218,7589,"POV",920,812)="^170^19" 
 ^TMP("PXKENC",2241218,7589,"POV",920,900,1,0)="2^1" 
 ^TMP("PXKENC",2241218,7589,"POV",920,900,2,0)="3^0" 
 ^TMP("PXKENC",2241218,7589,"POV",920,900,3,0)="1^0" 
 ^TMP("PXKENC",2241218,7589,"POV",921,0)="503268^140^7589^828^^^^^^^^S" 
 ^TMP("PXKENC",2241218,7589,"POV",921,12)="3260106.165548^^^991" 
 ^TMP("PXKENC",2241218,7589,"POV",921,800,0,0)="1^" 
 ^TMP("PXKENC",2241218,7589,"POV",921,812)="^170^19" 
 ^TMP("PXKENC",2241218,7589,"POV",921,900,1,0)="2^-1" 
 ^TMP("PXKENC",2241218,7589,"POV",921,900,2,0)="1^1" 
 ^TMP("PXKENC",2241218,7589,"POV",921,900,3,0)="13^1" 
 ^TMP("PXKENC",2241218,7589,"PRV",3186,0)="520824698^140^7589^P^^144" 
 ^TMP("PXKENC",2241218,7589,"PRV",3186,812)="^170^19" 
 ^TMP("PXKENC",2241218,7589,"PRV",3187,0)="991^140^7589^S^^1" 
 ^TMP("PXKENC",2241218,7589,"PRV",3187,812)="^170^19" 
 ^TMP("PXKENC",2241218,7589,"VST",7589,0)="3260106.165546^3260107.165551^V^ 
 ^140^5 00^A^141^9^^^^3260107.16574^^^^^^^^15^240^991^46" 
 ^TMP("PXKENC",2241218,7589,"VST",7589,150)="1DD2-ALN^0^P" 
 ^TMP("PXKENC",2241218,7589,"VST",7589,800)="1^1^0^^^^^^^0^0^0^0" 
 ^TMP("PXKENC",2241218,7589,"VST",7589,812)="^170^19" 
 ^TMP("PXKENC",2241218,7589,"VST",7589,900,1,0)="1^1" 
 ^TMP("PXKENC",2241218,7589,"VST",7589,900,2,0)="13^1" 
 ^TMP("PXKENC",2241218,7589,"VST",7589,900,3,0)="2^1" 
 ^TMP("PXKENC",2241218,7589,"VST",7589,900,4,0)="3^0" 
     
 The ^TMP("PXKENC",$J) global may be killed before and/or after the call.  
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   Added 3/15/17 
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   Added 2/2/21, effective with DG*5.3*1034 
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   Added 12/5/22, effective with DSSV*1.1. Document only
 Class 2, using $D before calling ENCEVENT.  
  DATE ACTIVATED: SEP 19, 2016

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
  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)

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
  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
  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
  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 
           <PROVIDER IEN> 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",<PROVIDER IEN>) 
              LOCAL("PROBLEM",<PROVIDER IEN>) 
              LOCAL("SOURCE") 
              LOCAL("ENCOUNTER") 
              LOCAL("DIAGNOSIS",<PROVIDER IEN>) 
              LOCAL("PROCEDURE",<PROVIDER IEN>) 
              LOCAL("PROVIDER",<PROVIDER IEN>) 
              LOCAL("IMMUNIZATION",<PROVIDER IEN>) 
              LOCAL("SKIN TEST",<PROVIDER IEN>) 
              LOCAL("EXAM",<PROVIDER IEN>) 
              LOCAL("PATIENT ED",<PROVIDER IEN>) 
              LOCAL("HEALTH FACTORS",<PROVIDER IEN>) 
              LOCAL("VITALS",<PROVIDER IEN>) 
                     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",<NODE>,<PROVIDER 
                        IEN>,<i>,<PIECE>)="Free text message^REJECTED VALUE" 
              Where     <NODE>      ::=  "ENCOUNTER" | "VITALS" | 
                                         "DIAGNOSIS" | "PROCEDURE" | 
                                         "PROBLEM" | rest of list| 
                        <PROVIDER IEN>   ::=    internal entry number of 
                                         provider. Is 0 (ZERO) for ENCOUNTER 
                                         and SOURCE 
                              <i>   ::=  sub-entry 'i' for that provider 
                                         Is 0 (ZERO) for ENCOUNTER, SOURCE 
                                         and PROVIDER 
                              <PIECE>    ::=    $P( selector in 
                                         LOCAL(<NODE>,<PROVIDER IEN>,<i>) 
                                         that failed.  
                                           The value of <PIECE> 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",<NODE>,<PROVIDER IEN>,<i>,<PIECE>) 
                        ="Free text message^QUESTIONABLE VALUE" 
              Where     <NODE>      ::=  "ENCOUNTER" | "VITALS" | 
                                         "DIAGNOSIS" | "PROCEDURE" | 
                                         "PROBLEM" 
                        <PROVIDER IEN>   ::=    internal entry number of 
                                         provider. Is 0 (ZERO) for ENCOUNTER 
                                         and SOURCE 
                              <i>   ::=  sub-entry 'i' for that provider 
                                         Is 0 (ZERO) for ENCOUNTER, SOURCE, 
                                         and PROVIDER 
                              <PIECE>    ::=    $P( selector in 
                                         LOCAL(<NODE>,<PROVIDER IEN>,<i>) in 
                                         question.  
                                           The value of <PIECE> 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 <PROVIDER IEN> 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",<PROVIDER IEN>, 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",<PROVIDER IEN>,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",<PROVIDER IEN>))is true.  
    LOCAL("DIAGNOSIS",<PROVIDER IEN>,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",<PROVIDER IEN>)) is true.  
    LOCAL("PROCEDURE",<PROVIDER IEN>,i) = 1^2^3^4^5^6^7^8^9^10^ 
         11^12^13^14,(pieces defined below) 
    LOCAL("PROCEDURE",<PROVIDER IEN>,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",<PROVIDER IEN>)) is true.  
    LOCAL("PROBLEM",<PROVIDER IEN>,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",<PROVIDER IEN>= 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",<PROVIDER IEN>)) 
    is true.  
  
    LOCAL ("IMMUNIZATION",<PROVIDER IEN>,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",<PROVIDER IEN>)) is 
    true.  LOCAL ("SKIN TEST",<PROVIDER IEN>,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",<PROVIDER IEN>)) is true. 
    LOCAL ("EXAM",<PROVIDER.IEN>")=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",<PROVIDER 
    IEN>)) is true.  LOCAL ("PATIENT ED",<PROVIDER IEN>,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",<PROVIDER IEN>)) is true.  LOCAL ("HEALTH 
    FACTORS",<PROVIDER IEN>,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",<PROVIDER IEN>)) is true.  
    LOCAL("VITALS",<PROVIDER IEN>,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",<PROVIDER IEN>)) is true.  
    LOCAL("LOCAL",<PROVIDER IEN>,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

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                   <visit date [and time] in FM format> 
                                     VSIT("VDT") may be used instead of VSIT.  
                                     (time will default to 12 noon if not 
                                     specified) 
     
              DFN                    <patient file pointer> 
                                     VSIT("PAT") may be used instead of DFN.  
     
              [VSIT(0)]              <a string of characters that defines how 
                                     the visit processor will function, see 
                                     package-wide variables> 
     
              [VSIT("<xxx>")]        <array with mnemonic subscript> 
                                     (used in match logic if VSIT(0)["M") 
                                     (for SVC, TYP, INS, CLN, ELG, LOC) 
                                     Note: For multiple field values use 
                                     [<field value>[^...]] 
                                     i.e., VSIT("SVC")="H^D"  (will find both) 
     
              VSITPKG                <package name space> 
                                     VSIT("PKG") may be used instead of 
                                     VSITPKG.  
     
      OUTPUT: 
              VSIT(<ien>)            N^S[^1] 
                                     where: 
                                     N = <internal entry number of visit> 
                                          or -1 if could not get a visit 
                                          or -2 if calling package is not 
                                          active in Visit Package Parameters 
                                     S = <value of .01 field of visit> 
                                     1 = <indicates that a new visit was added 
     
              VSIT(<xxx>)            array passed in with all the entries 
                                     defined and the defaulted values added 
     
              VSIT(<ien>,<xxx>)      returns the data that is stored in the 
                                     Visit file in the same format as 
                                     VSIT(<xxx>) 
     
    Variable descriptions: 
     
    VSIT(<xxx>)         Variable Names for VISIT file fields, 
                        Where <xxx> 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[<number of days>] 
                                      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(<xxx>) 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(<ien>) N^S[^1] 
                                    where: 
                                      N = <internal entry number of visit> 
                                      S = <value of .01 field of visit> 
                                      1 = <indicates that a new visit was 
                                            added> 
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 2.0
COMPONENT/ENTRY POINT: VSIT
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
  DATE ACTIVATED: JAN 10, 2017

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: VISIT FILE DATE LAST MODIFIED
  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) 
     80009   VSIT("CLV")  CAMP LEJEUNE EXPOSURE (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
  GOOD ONLY FOR VERSION: 2.0
COMPONENT/ENTRY POINT: UPD
COMPONENT/ENTRY POINT: MODIFIED
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany
  DATE ACTIVATED: MAR 29, 2016

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
  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
  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
  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 

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
  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)

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(<ien>,<xxx>) or VSIT(<xxx>) 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) 
     80009   VSIT("CLV")   CAMP LEJEUNE EXPOSURE (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
  GOOD ONLY FOR VERSION: 2.0
COMPONENT/ENTRY POINT: LOOKUP
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  DATE ACTIVATED: JAN 10, 2017

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
  GOOD ONLY FOR VERSION: 2.0
COMPONENT/ENTRY POINT: HISTORIC
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES

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
  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
  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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
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>^         
   <today's date (int FM)>^                        ^TMP("TIUP",$J,1,0)="<first
 line of text>"        ^TMP("TIUP",$J,2,0)="<second line of text>"       
 ^TMP("TIUP",$J,3,0)="<third line of text>"        ^TMP("TIUP",$J,n,0)="<nth
 line of text>"          
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 

NUMBER: 1912                            IA #: 1912
  DATE CREATED: JAN 28, 1997            CUSTODIAL PACKAGE: 1
  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
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
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: 1915                            IA #: 1915
  FILE NUMBER: 63                       GLOBAL ROOT: LR(
  DATE CREATED: JAN 29, 1997            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA1915
  ID: LR(
GLOBAL REFERENCE: LR(
FIELD NUMBER: 2005                      FIELD NAME: IMAGE
  LOCATION: 2005,0                      ACCESS: Read w/Fileman
  STATUS: Pending
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

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
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: 1917                            IA #: 1917
  DATE CREATED: FEB 06, 1997            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SCAPMC
  NAME: PCMM CALLS FOR CPRS/OERR - SCAPMC
  ID: SCAPMC
 GENERAL DESCRIPTION:   These are the PCMM supported calls in the SCAPMC
 routine for Team and Personal Patient lists used by CPRS/OERR which are not
 supported elsewhere: 
  
 ACPRTP^SCAPMC ACPTTM^SCAPMC ACPTTP^SCAPMC ACTM^SCAPMC ACTMNM^SCAPMC 
 ACTP^SCAPMC ACTPNM^SCAPMC INPTTM^SCAPMC TMAU^SCAPMC TMINST^SCAPMC TMPR^SCAPMC 
 TPPR^SCAPMC TPTM^SCAPMC 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ACPRTP
 COMPONENT DESCRIPTION:   Change practitioner-position assignment 
COMPONENT/ENTRY POINT: ACPTTM
 COMPONENT DESCRIPTION:   Add a patient to a team.  
COMPONENT/ENTRY POINT: ACPTTP
 COMPONENT DESCRIPTION:   Assign a patient to a position.  
COMPONENT/ENTRY POINT: ACTM
 COMPONENT DESCRIPTION:   Change team status using team ien.  
COMPONENT/ENTRY POINT: ACTMNM
 COMPONENT DESCRIPTION:   Change team status using team name.  
COMPONENT/ENTRY POINT: ACTP
 COMPONENT DESCRIPTION:   Change position status using ien.  
COMPONENT/ENTRY POINT: ACTPNM
 COMPONENT DESCRIPTION:   Change position status using name.  
COMPONENT/ENTRY POINT: INPTTM
 COMPONENT DESCRIPTION:   Inactivate patient from a team.  
COMPONENT/ENTRY POINT: TMAU
 COMPONENT DESCRIPTION:   List teams for an autolink.  
COMPONENT/ENTRY POINT: TMINST
 COMPONENT DESCRIPTION:   List teams for an institution.  
COMPONENT/ENTRY POINT: TMPR
 COMPONENT DESCRIPTION:   List teams for a practitioner.  
COMPONENT/ENTRY POINT: TPPR
 COMPONENT DESCRIPTION:   Positions for a practitioner.  
COMPONENT/ENTRY POINT: TPTM
 COMPONENT DESCRIPTION:   Positions for a team.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1918                            IA #: 1918
  DATE CREATED: FEB 06, 1997            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: SCAPMCU1                     NAME: PCMM CALLS FOR SCAPMCU1
  ID: SCAPMCU1
 GENERAL DESCRIPTION:   These are the PCMM supported calls in the SCAPMCU1
 routine for Team and Personal Patient lists which are not supported elsewhere: 
  
 DATES^SCAPMCU1 RSNDICS^SCAPMCU1 TEAMCNT^SCAPMCU1 
  
 ICR was originally created for use by OE/RR.  As of 10/11/17, no references to
 routine SCAPMCU1 were found in OR* routines.  Removed OE/RR as a subscriber.  
  
 **************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library for list of retired HMP ICRs.  
 **************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
COMPONENT/ENTRY POINT: DATES
 COMPONENT DESCRIPTION:   Get latest activation and inactivate dates.  
COMPONENT/ENTRY POINT: RSNDICS
 COMPONENT DESCRIPTION:   Get type of reason.  
COMPONENT/ENTRY POINT: TEAMCNT
 COMPONENT DESCRIPTION:   Get number of patients on a team for a specific date. 
 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP will be using TEAMCNT entry points in routine
 SCAPMCU1 in HMP version 2.0.  
  DATE ACTIVATED: OCT 11, 2017

NUMBER: 1919                            IA #: 1919
  DATE CREATED: FEB 06, 1997            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SCAPMCU3
  NAME: PCMM CALLS FOR CPRS/OERR - SCAPMCU3
  ORIGINAL NUMBER: 1919                 ID: SCAPMCU3
 GENERAL DESCRIPTION:   These are the PCMM supported calls in the SCAPMCU3
 routine for Team and Personal Patient lists used by CPRS/OERR which are not
 supported elsewhere: 
  
 GETEAM^SCAPMCU3 GETREC^SCAPMCU3 SETREC^SCAPMCU3 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETEAM
 COMPONENT DESCRIPTION:   Get team demographics 
COMPONENT/ENTRY POINT: GETREC
 COMPONENT DESCRIPTION:   Get team record with autolink data.  
COMPONENT/ENTRY POINT: SETREC
 COMPONENT DESCRIPTION:   Add/edit autolink data to a team.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1920                            IA #: 1920
  FILE NUMBER: 404.51                   GLOBAL ROOT: SCTM
  DATE CREATED: FEB 06, 1997            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: PCMM FILE USED BY CPRS/OERR - SCTM(404.51
  ORIGINAL NUMBER: 1919                 ID: SCTM
 GENERAL DESCRIPTION:   The file SCTM(404.51 is supported by PCMM for use by
 CPRS/OERR Team and Personal Patient lists.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1921                            IA #: 1921
  FILE NUMBER: 404.57                   GLOBAL ROOT: SCTM
  DATE CREATED: FEB 06, 1997            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: PCMM FILE USED BY CPRS/OERR - SCTM(404.57
  ORIGINAL NUMBER: 1919                 ID: SCTM
 GENERAL DESCRIPTION:   The file SCTM(404.57 is supported by PCMM for use by
 CPRS/OERR Team and Personal Patient lists.  
  
 4/24/15-Status changed from Pending to Withdrawn with concurrence from CPRS
 team and PCMM representative.  No references to this file found in CPRS/OR
 code.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1922                            IA #: 1922
  FILE NUMBER: 404.42                   GLOBAL ROOT: SCPT
  DATE CREATED: FEB 06, 1997            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: File
  NAME: PCMM FILE USED BY CPRS/OERR - SCPT(404.42
  ORIGINAL NUMBER: 1919                 ID: SCPT
 GENERAL DESCRIPTION:   The file SCPT(404.42 is supported by PCMM for use by
 CPRS/OERR Team and Personal Patient lists.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1923                            IA #: 1923
  FILE NUMBER: 404.56                   GLOBAL ROOT: SCTM
  DATE CREATED: FEB 06, 1997            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: PCMM FILE USED BY CPRS/OERR - SCTM(404.56
  ORIGINAL NUMBER: 1919                 ID: SCTM
 GENERAL DESCRIPTION:   The file SCTM(404.56 is supported by PCMM for use by
 CPRS/OERR Team and Personal Patient lists.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1924                            IA #: 1924
  FILE NUMBER: 404.52                   GLOBAL ROOT: SCTM
  DATE CREATED: FEB 06, 1997            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: PCMM FILE USED BY CPRS/OERR - SCTM(404.52
  ORIGINAL NUMBER: 1919                 ID: SCTM
 GENERAL DESCRIPTION:   The file SCTM(404.52 is supported by PCMM for use by
 CPRS/OERR Team and Personal Patient lists.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1925                            IA #: 1925
  FILE NUMBER: 404.58                   GLOBAL ROOT: SCTM
  DATE CREATED: FEB 06, 1997            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: PCMM FILE USED BY CPRS/OERR - SCTM(404.58
  ORIGINAL NUMBER: 1919                 ID: SCTM
 GENERAL DESCRIPTION:   The file SCTM(404.58 is supported by PCMM for use by
 CPRS/OERR Team and Personal Patient lists.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1926                            IA #: 1926
  FILE NUMBER: 404.59                   GLOBAL ROOT: SCTM
  DATE CREATED: FEB 06, 1997            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: PCMM FILE USED BY CPRS/OERR - SCTM(404.59
  ORIGINAL NUMBER: 1919                 ID: SCTM
 GENERAL DESCRIPTION:   The file SCTM(404.59 is supported by PCMM for use by
 CPRS/OERR Team and Personal Patient lists.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1927                            IA #: 1927
  FILE NUMBER: 120.5                    GLOBAL ROOT: GMR
  DATE CREATED: FEB 07, 1997
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File
  NAME: Vitals File Access for CPRS/OERR - GMR(120.5
  ORIGINAL NUMBER: 1927                 ID: GMR
 GENERAL DESCRIPTION:   The file GMR(120.5 is supported by Vitals/Measurements
 for use by CPRS/ OERR to return most recent vitals for a patient.  The "AA"
 x-ref and zero nodes are used.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1928                            IA #: 1928
  FILE NUMBER: 120.51                   GLOBAL ROOT: GMRD
  DATE CREATED: FEB 07, 1997
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File
  NAME: Vitals File Access for CPRS/OERR - GMRD(120.51
  ORIGINAL NUMBER: 1927                 ID: GMRD
 GENERAL DESCRIPTION:   The file GMRD(120.51 is supported by
 Vitals/Measurements for use by CPRS/ OERR to return most recent vitals for a
 patient.  The "B" x-ref is used.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

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
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
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
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
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES

NUMBER: 1933                            IA #: 1933
  DATE CREATED: FEB 14, 1997            CUSTODIAL PACKAGE: HINQ
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Other                           NAME: DBIA1933
  ORIGINAL NUMBER: 1933
 GENERAL DESCRIPTION:   Distribute HINQ input template.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DVBHINQ UPDATE
 COMPONENT DESCRIPTION:   Input Template: DVBHINQ UPDATE  Compiled Routine:
 DVBHCE  File: 2 
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

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
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
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
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
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
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
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: 1
  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
  GOOD ONLY FOR VERSION: AICS V3.0
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Washington/Silver Spring

NUMBER: 1942                            IA #: 1942
  FILE NUMBER: 40.8                     GLOBAL ROOT: DG(40.8
  DATE CREATED: FEB 27, 1997            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: REGISTRATION FILE USED BY CPRS/OERR - DG(40.8
  ID: DG(40.8
 GENERAL DESCRIPTION:   CPRS/OERR extracts data from the MEDICAL CENTER
 DIVISION FILE [#40.8].  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1943                            IA #: 1943
  FILE NUMBER: 403.44                   GLOBAL ROOT: SD(403.44
  DATE CREATED: FEB 27, 1997            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: PCMM FILE USED BY CPRS/OERR - SD(403.44
  ID: SD(403.44
 GENERAL DESCRIPTION:   The file SD(403.44 is supported by PCMM for use by
 CPRS/OERR Team and Personal Patient lists.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 1944                            IA #: 1944
  FILE NUMBER: 403.46                   GLOBAL ROOT: SD(403.46
  DATE CREATED: FEB 27, 1997            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: PCMM FILE USED BY CPRS/OERR - SD(403.46
  ID: SD(403.46
 GENERAL DESCRIPTION:   The file SD(403.46 is supported by PCMM for use by
 CPRS/OERR Team and Personal Patient lists.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
COMPONENT/ENTRY POINT: LRCAPDSS
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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,IEN,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: TYPE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: SUBSCRIPT
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAB(60,IEN,64)
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 NTL 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
KEYWORDS: MAG HL7 MESSAGES
KEYWORDS: VI HL7 MESSAGES
KEYWORDS: PACS HL7
KEYWORDS: MAGT7MA
KEYWORDS: MAG*3.0*183
KEYWORDS: DICOM modality worklist
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham
SUBSCRIBING PACKAGE: VBECS
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   VistA Imaging (VI) requests to obtain TYPE (#3) and
 SUBSCRIPT(#4) field data from the LABORATORY TEST (#60) file.  
  
 VI also requests to obtain data from the NATIONAL VA LAB CODE (#64) field from
 the LABORATORY TEST (#60) file.  
  DATE ACTIVATED: AUG 09, 2017

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
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(
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
KEYWORDS: LOINC
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham
  DATE ACTIVATED: JUN 06, 2011

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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany
  DATE ACTIVATED: JAN 29, 2007

NUMBER: 1952                            IA #: 1952
  FILE NUMBER: 69                       GLOBAL ROOT: LRO(69,
  DATE CREATED: MAR 04, 1997            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA1952
  ID: LRO(69,
GLOBAL REFERENCE: LRO(69,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE ORDERED
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LRO(69,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: LRDFN
  LOCATION: 0;1                         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: 23                        FIELD NAME: ORDERING LOCATION
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Within the SPECIMEN multiple (1), the entire zero node
 is read into a local variable. The fields above are used.  
   
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: 3                         FIELD NAME: ACCESSION AREA
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Within the SPECIMEN multiple (1), DSS examines the TEST
 multiple (6).  The entire zero node is read into a local variable. The fields
 above are used.  
 GENERAL DESCRIPTION:   DSS Extracts references the following data from the LAB
 ORDER ENTRY file (#69).  
   
 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: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: 2000
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

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
COMPONENT/ENTRY POINT: LRCAPDAR
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany

NUMBER: 1955                            IA #: 1955
  FILE NUMBER: 727.2                    GLOBAL ROOT: ECX(727.2
  DATE CREATED: MAR 04, 1997
  CUSTODIAL PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Birmingham

NUMBER: 1957                            IA #: 1957
  FILE NUMBER: 1                        GLOBAL ROOT: DIC
  DATE CREATED: MAR 10, 1997            CUSTODIAL PACKAGE: 1
  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
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: LR7OSUM                      NAME: DBIA1958
  ID: LR7OSUM
 GENERAL DESCRIPTION:   This API will get Lab results for a given patient based
 on various input parameters.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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: 1959                            IA #: 1959
  DATE CREATED: MAY 24, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: LRAURPT                      NAME: DBIA1959
  ID: LRAURPT
 GENERAL DESCRIPTION:   This agreement is to use routine LRAURPT to produce an
 autopsy report for images captured under the Autopsy Lab specialty. At the
 present time, there is no supported API for this functionality. 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: QUE
 COMPONENT DESCRIPTION:   This routine will printout a formatted autopsy
 report.  
VARIABLES: LRQ(8)                       TYPE: Input
 VARIABLES DESCRIPTION:   Variable defining the accession prefix.  
VARIABLES: LRAP                         TYPE: Input
 VARIABLES DESCRIPTION:   Set to LRDFN 
VARIABLES: LRDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient's DFN in the Lab Data file, 63.  
VARIABLES: LRD                          TYPE: Input
 VARIABLES DESCRIPTION:   Set to 1 for printing weights, measures and coding
 (if present).  
VARIABLES: LRSAV                        TYPE: Input
 VARIABLES DESCRIPTION:   Set to null - not to Save protocol list for
 reprinting.  
VARIABLES: LRAN                         TYPE: Input
 VARIABLES DESCRIPTION:   Accession number 
VARIABLES: LRAA                         TYPE: Input
 VARIABLES DESCRIPTION:   Autopsy IEN 
VARIABLES: LRSS                         TYPE: Input
 VARIABLES DESCRIPTION:   AP Section.  
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Images captured under the Autopsy specialty are saved
 with references to the Autopsy accession number and pointers to the Image
 subfields in the Lab Data file, 63.  These references will be used to pass the
 patient dfn and autopsy accession number when the routine LRAURPT is called.  
 Imaging routine, MAGGTRPT, does verify that the Autopsy reports has been 
 release prior to executing the LRAURPT routine. 

NUMBER: 1961                            IA #: 1961
  FILE NUMBER: 51.5                     GLOBAL ROOT: DIC(51.5,
  DATE CREATED: MAR 20, 1997
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA1961
  ID: DIC(51.5,
GLOBAL REFERENCE: DIC(51.5,D0,1,0)
FIELD NUMBER: .01                       FIELD NAME: SYNONYM
  LOCATION: 1;0                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The SYNONYM field contains the order unit from the prime
 vendor that is different from the ORDER UNIT field for the unit of order.  
 GLOBAL DESCRIPTION:   The SYNONYM multiple contains order units from the prime
 vendor that are different from the ORDER UNIT field for the unit of order.  
 GENERAL DESCRIPTION:   Drug Accountability v3.0 needs write access to the
 ORDER UNIT (51.5) file.  A new SYNONYM multiple needs to be written to.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
  ISC: Birmingham

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
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
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
SUBSCRIBING PACKAGE: VBECS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD

NUMBER: 1964                            IA #: 1964
  DATE CREATED: MAR 22, 1997            CUSTODIAL PACKAGE: GEN. MED. REC. - I/O
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         ROUTINE: GMRYCATH
  NAME: GMRYCATH                        ID: GMRYCATH
 GENERAL DESCRIPTION:   The Nursing Service package has permission to call the
 GMRYCATH routine in order to display or print its End of Shift report.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: FINDCA
 COMPONENT DESCRIPTION:   This entry point finds a catheter for a selected IV
 site.  
VARIABLES: GSITE                        TYPE: Input
 VARIABLES DESCRIPTION:   This is an array containing IV infusion location
 (e.g., LEFT WRIST). The NURCES2 routine passes the parameter GSITE by
 reference. For example: 
  
 GSITE=LEFT WRIST 
VARIABLES: II                           TYPE: Output
 VARIABLES DESCRIPTION:   The variable II is a single dimension array. It is
 the formal parameter associated with GSITE. Each subscripted element contains
 the value of the IV CATHETER TYPE/SIZE field from the GMRY PATIENT I/O FILE
 (#126) for a patient. It returns the name of the IV catheter for a given IV
 infusion location and patient. For example: 
  
 GSITE("LEFT WRIST")=TRIPLE LUMEN 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The calling routine must have DFN defined.  
SUBSCRIBING PACKAGE: NURSING SERVICE    ISC: Hines

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
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
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].  
SUBSCRIBING PACKAGE: VISTA SYSTEM MONITOR
 SUBSCRIBING DETAILS:   Environment check routine in patch KMPV*1*1 will verify
 the new domain added by XM*999*178 existgs before proceeding with KMPV patch 
 installation.  
SUBSCRIBING PACKAGE: PROBLEM LIST
 SUBSCRIBING DETAILS:   Effective with patch GMPL*2.0*49 - the application will
 check for any default selection list parameter settings and prohibit any list
 deletions if current assignments are active. If any lists cannot be deleted,
 the application will display the list of current parameter entity/value 
 assignments. This may include any default lists that are assigned at the 
 system/domain level. The domain name is retrieved for the purpose of this 
 display.  
  DATE ACTIVATED: FEB 14, 2017

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
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
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
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
  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
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
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
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
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: 1975                            IA #: 1975
  FILE NUMBER: 53                       GLOBAL ROOT: PS(53
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA1975
  ID: PS(53
GLOBAL REFERENCE: PS(53,D0,0)
FIELD NUMBER: 5                         FIELD NAME: RENEWABLE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ABBR
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DAYS SUPPLY
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: REFILLS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: SC/A&A/OTHER/INPATIENT
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: EXEMPT FROM COPAYMENT
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: EXEMPT FROM CHAMPUS BILLING
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
 SUBSCRIBING DETAILS:   Only uses field 6.  

NUMBER: 1976                            IA #: 1976
  FILE NUMBER: 59                       GLOBAL ROOT: PS(59
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA1976
  ID: PS(59
 GENERAL DESCRIPTION:   The subscribing pharmacy packages are allowed direct
 global read access to all fields and cross-references of file #59.  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 1977                            IA #: 1977
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA1977
  ID: PSRX(
 GENERAL DESCRIPTION:   The CMOP package requires direct R/W access to all
 fields and cross-references in file 52.  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: INTEGRATED BILLING

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
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
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
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   ADDED 6/27/2011 

NUMBER: 1981                            IA #: 1981
  FILE NUMBER: 59.7                     GLOBAL ROOT: PS(59.7
  DATE CREATED: MAR 28, 1997
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA1981
  ID: PS(59.7
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;3                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 40.13                     FIELD NAME: REFILL/RENEW DIVISION
  LOCATION: 40.1;4                      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
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
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham

NUMBER: 1982                            IA #: 1982
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55
  DATE CREATED: MAR 28, 1997
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA1982
  ID: PS(55
GLOBAL REFERENCE: PS(55,D0,0)
FIELD NUMBER: .02                       FIELD NAME: CAP
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: MAIL
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: MAIL STATUS EXPIRATION DATE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,D0,P,0)
FIELD NUMBER: .01                       FIELD NAME: PRESCRIPTION PROFILE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham

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
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham

NUMBER: 1984                            IA #: 1984
  FILE NUMBER: 452.6                    GLOBAL ROOT: PRSE(452.6
  DATE CREATED: MAR 29, 1997            CUSTODIAL PACKAGE: EDUCATION TRACKING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: FILE 452.6
  ID: PRSE(452.6
GLOBAL REFERENCE: PRSE(452.6,DA,0)
FIELD NUMBER: .01                       FIELD NAME: REASON FOR EMPLOYEE TRAINING
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Nursing Service package has permission to do a
 global read of the zero node of the PRSE SVC REASONS FOR TRAINING file
 (#452.6) and to print the first piece of that node (i.e., REASON FOR EMPLOYEE
 TRAINING) for its Nursing personnel education reports.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NURSING SERVICE    ISC: Hines

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
  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: 1                  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
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
  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)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP*2.0*2 
  
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************

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
  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)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
 **************************************************************************

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
FIELD NUMBER: .03                       FIELD NAME: CATEGORY
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   This file contains a descriptive name of health factors,
 and their health factor category.  
GLOBAL REFERENCE: AUTTHF("AC"
GLOBAL REFERENCE: AUTTHF("B"
 GENERAL DESCRIPTION:   This integration agreement authorizes global reference
 to the zeroth 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
  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
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Added with HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 6/3/19. Effective with YS*5.01*140.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   Added 12/21/2021, effective with DSSV*1.0*1 DSS Class 3
 Product Document Only 
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Added 8/22/2025, effective with PSJ*5*461 The Methadone 
 Dispensing Tracking Project will have to make reference to the PCE PATIENT
 CARE ENCOUNTER index { ^AUTTHF("B" } in order to determine a patient's current
 authorization status for reporting to the state Prescription Drug Monitoring
 Program (PDMP).  

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
FIELD NUMBER: .03                       FIELD NAME: CVX CODE
  LOCATION: 0;3                         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
  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)
  DATE ACTIVATED: NOV 16, 2021

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
  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)

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
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: 1993                            IA #: 1993
  DATE CREATED: APR 08, 1997            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDAMBAE3
  NAME: DBIA1993                        ID: SDAMBAE3
 GENERAL DESCRIPTION:   This is a one-time only DBIA with Scheduling to allow
 the CPT v.6.0 package update to revise routines SDAMBAE2 and SDAMBAE3 to
 eliminate references to files 409.72 and 409.71, which will no longer be
 maintained.  
  
 In addition, the EFFECTIVE DATE will now be referenced by API, and not be 
 hard-coded into these routines.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SCREEN
 COMPONENT DESCRIPTION:   Checks that procedure code is active.  
COMPONENT/ENTRY POINT: ID
 COMPONENT DESCRIPTION:   Checks that procedure code is active.  
COMPONENT/ENTRY POINT: LOC
 COMPONENT DESCRIPTION:   eliminates reference to local codes - no longer
 permitted.  
SUBSCRIBING PACKAGE: CPT/HCPCS CODES    ISC: Albany

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
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
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(<modifier>)= 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
 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
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 
  DATE ACTIVATED: SEP 18, 2008

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
 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
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. 
 
  DATE ACTIVATED: SEP 18, 2008

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
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: 1999                            IA #: 1999
  FILE NUMBER: 690                      GLOBAL ROOT: MCAR(690,
  DATE CREATED: OCT 20, 2003            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA1999
  ID: MCAR(690,
GLOBAL REFERENCE: MCAR(690,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   By providing read access to file 690, the Medical
 Patient file, offer the user a list of existing medicine procedures to apphend
 Images to.  
  
 For a list of patient procedures Imaging reads: 
   ^MCAR(690,"AC",DFN,Inverted FM Date/Time,File #) 
  
 This IA will be modified as Medicine APIs are released to replace its
 functions.  Imaging and Medicine will participate actively in the testing
 process to be sure API's meet Imaging's needs.  Imaging will migrate to the
 use of API's as soon as possible.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
SUBSCRIBING PACKAGE: SURGERY            ISC: Birmingham

NUMBER: 2000                            IA #: 2000
  FILE NUMBER: 697.2                    GLOBAL ROOT: MCAR(697.2,
  DATE CREATED: OCT 20, 2003            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA2000
  ID: MCAR(697.2,
GLOBAL REFERENCE: MCAR(697.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: GLOBAL LOCATION
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1.1                       FIELD NAME: MEDICAL PATIENT
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: TYPE OF PROCEDURE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: PRINT NAME
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: MCAR(697.2,D0(1),'CPT',D0,0)
FIELD NUMBER: 1000                      FIELD NAME: CPT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Retired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 2.3
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

NUMBER: 2001                            IA #: 2001
  FILE NUMBER: 691                      GLOBAL ROOT: MCAR(691,
  DATE CREATED: OCT 20, 2003            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA2001
  ID: MCAR(691,
GLOBAL REFERENCE: MCAR(691,D0,0)
FIELD NUMBER: 1                         FIELD NAME: 1 MEDICAL PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: MCAR(691,D0(1),2005,D0,0)
FIELD NUMBER: .01                       FIELD NAME: IMAGE
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: MCAR(691,D0,.2)
FIELD NUMBER: 600                       FIELD NAME: PROCEDURE SUMMARY
  LOCATION: .2;2                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   For the purpose of appending an Image to an existing
 Medicine procedure or placing an Image into a new Medicine Procedure
 read/write access is require for ECHOCARDIOGRAPHY.  FILE^DICN is used to
 create a new file 691 entry, when necessary. The IMAGE multiple, field 2005,
 is processed by direct global read/writes.  
  
 This IA will be modified as Medicine APIs are released to replace its
 functions.  Imaging and Medicine will participate actively in the testing
 process to be sure API's meet Imaging's needs.  Imaging will migrate to the
 use of API's as soon as possible.  
  STATUS: Withdrawn                     DURATION: Next Version
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

NUMBER: 2002                            IA #: 2002
  FILE NUMBER: 691.1                    GLOBAL ROOT: MCAR(691.1,
  DATE CREATED: APR 10, 1997            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA2002
  ID: MCAR(691.1,
GLOBAL REFERENCE: MCAR(691.1,D0,0)
FIELD NUMBER: 1                         FIELD NAME: MEDICAL PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: MCAR(691.1,D0(1),3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PROCEDURE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: MCAR(691.1,D0(1),2005,D0,0)
FIELD NUMBER: .01                       FIELD NAME: IMAGE
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: MCAR(691.1,D0,.2)
FIELD NUMBER: 600                       FIELD NAME: PROCEDURE SUMMARY
  LOCATION: .2;2                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   For the purpose of appending an Image to an existing
 Medicine procedure or placing an Image into a new Medicine Procedure
 read/write access is require for CARDIAC CATHETERIZATION. FILE^DICN is used to
 create a new file 691.1 entry,when necessary. The IMAGE multiple, field 2005,
 is processed by direct global read/writes.  
  STATUS: Withdrawn                     DURATION: Next Version
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

NUMBER: 2003                            IA #: 2003
  FILE NUMBER: 691.5                    GLOBAL ROOT: MCAR(691.5,
  DATE CREATED: APR 11, 1997            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA2003
  ID: MCAR(691.5,
GLOBAL REFERENCE: MCAR(691.5,D0,0)
FIELD NUMBER: 1                         FIELD NAME: MEDICAL PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: MCAR(691.5,D0(1),2005,D0,0)
FIELD NUMBER: .01                       FIELD NAME: IMAGE
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: MCAR(691.5,D0,.2)
FIELD NUMBER: 600                       FIELD NAME: PROCEDURE SUMMARY
  LOCATION: .2;2                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   For the purpose of appending an Image to an existing
 Medicine procedure or placing an Image into a new Medicine Procedure
 read/write access is require for ELECTROCARDIOGRAM. FILE^DICN is used to
 create a new file 691.5 entry,when necessary. The IMAGE multiple, field 2005,
 is processed by direct global read/writes.  
  STATUS: Withdrawn                     DURATION: Next Version
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

NUMBER: 2004                            IA #: 2004
  FILE NUMBER: 694                      GLOBAL ROOT: MCAR(694,
  DATE CREATED: APR 11, 1997            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA2004
  ID: MCAR(694,
GLOBAL REFERENCE: MCAR(694,D0,0)
FIELD NUMBER: 1                         FIELD NAME: MEDICAL PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: PROCEDURE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: MCAR(694,D0(1),2005,D0,0)
FIELD NUMBER: .01                       FIELD NAME: IMAGE
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: MCAR(694,D0,.2)
FIELD NUMBER: 600                       FIELD NAME: PROCEDURE SUMMARY
  LOCATION: .2;2                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   For the purpose of appending an Image to an existing
 Medicine procedure or placing an Image into a new Medicine Procedure
 read/write access is require for HEMATOLOGY. FILE^DICN is used to create a new 
 file 694 entry, when neccessary.  
  The IMAGE multiple, field 2005, is processed by direct global read/writes.  
  STATUS: Withdrawn                     DURATION: Next Version
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

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
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

NUMBER: 2006                            IA #: 2006
  FILE NUMBER: 699                      GLOBAL ROOT: MCAR(699,
  DATE CREATED: APR 11, 1997            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA2006
  ID: MCAR(699,
GLOBAL REFERENCE: MCAR(699,D0,0)
FIELD NUMBER: .02                       FIELD NAME: MEDICAL PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PROCEDURE
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: APPOINTMENT DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: MCAR(699,D0(1),2005,D0,0)
FIELD NUMBER: .01                       FIELD NAME: IMAGE
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: MCAR(694,D0,.2)
FIELD NUMBER: 600                       FIELD NAME: PROCEDURE SUMMARY
  LOCATION: .2;2                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   For the purpose of appending an Image to an existing
 Medicine procedure or placing an Image into a new Medicine Procedure
 read/write access is require for ENDOSCOPY/CONSULT. FILE^DICN is used to
 create a new file 699 entry,when necessary. The IMAGE multiple, field 2005, is 
 processed by direct global read/writes.  
  STATUS: Withdrawn                     DURATION: Next Version
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

NUMBER: 2007                            IA #: 2007
  FILE NUMBER: 699.5                    GLOBAL ROOT: MCAR(699.5,
  DATE CREATED: APR 11, 1997            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA2007
  ID: MCAR(699.5,
GLOBAL REFERENCE: MCAR(699.5,D0,0)
FIELD NUMBER: .02                       FIELD NAME: MEDICAL PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: SUBSPECIALTY
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: MCAR(699.5,D0(1),2005,D0,0)
FIELD NUMBER: .01                       FIELD NAME: IMAGE
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: MCAR(699.5,D0,.2)
FIELD NUMBER: 600                       FIELD NAME: PROCEDURE SUMMARY
  LOCATION: .2;2                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   For the purpose of appending an Image to an existing
 Medicine procedure or placing an Image into a new Medicine Procedure
 read/write access is require for GENERALIZED PROCEDURE/CONSULT. FILE^DICN is
 used to create a new file 699.5 entry, when nessary. The IMAGE multiple, field
 2005, is processed by direct global read/writes.  
  STATUS: Withdrawn                     DURATION: Next Version
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

NUMBER: 2008                            IA #: 2008
  FILE NUMBER: 701                      GLOBAL ROOT: MCAR(701,
  DATE CREATED: APR 11, 1997            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA2008
  ID: MCAR(701,
GLOBAL REFERENCE: MCAR(701,D0,0)
FIELD NUMBER: 1                         FIELD NAME: MEDICAL PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: MCAR(701,D0(1),2005,D0,0)
FIELD NUMBER: .01                       FIELD NAME: IMAGE
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: MCAR(701,D0,.2)
FIELD NUMBER: 600                       FIELD NAME: PROCEDURE SUMMARY
  LOCATION: .2;2                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   For the purpose of appending an Image to an existing
 Medicine procedure or placing an Image into a new Medicine Procedure
 read/write access is require for RHEUMATOLOGY. FILE^DICN is used to create a 
 new file 701 entry, when necessary. The IMAGE multiple, field 2005, is 
 processed by direct global read/writes.  
  STATUS: Withdrawn                     DURATION: Next Version
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

NUMBER: 2009                            IA #: 2009
  DATE CREATED: OCT 20, 2003            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         ROUTINE: MCMAGDSP
  NAME: DBIA2009                        ID: MCMAGDSP
 GENERAL DESCRIPTION:   This supported reference allows the Imaging package
 user to view a medicine package textual report which is linked to the image.  
  STATUS: Retired                       DURATION: Next Version
COMPONENT/ENTRY POINT: REPRT
 COMPONENT DESCRIPTION:   This entry point is called with the file internal
 entry number(IEN) and the file number in the actual list.  For example:  DO
 REPRT^MCMAGDSP(ien,file) 
  
 The Medicine package routine MCMAGDSP calls the appropriate routine.  
VARIABLES: ien                          TYPE: Input
 VARIABLES DESCRIPTION:   Medicine procedure IEN.  
VARIABLES: file                         TYPE: Input
 VARIABLES DESCRIPTION:   Medicine procedure file number.  
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

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
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
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
 SUBSCRIBING DETAILS:   Added 10/23/26, effective retroactively with patch
 IVM*2.0*211.  Allow access to the global values in the INCONSISTENT DATA 
 ELEMENTS(#38.6) file for all patient record inconsistencies.  

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
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
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 EMAIL GROUP 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
SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY
  ISC: Hines

NUMBER: 2016                            IA #: 2016
  FILE NUMBER: 50.6                     GLOBAL ROOT: PSNDF(
  DATE CREATED: APR 29, 1997            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2016
  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.  
 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.  
  
  
 Amended october 28, 1997.  
  
 The Immunology Case Registry package (ICR) requests a DBIA to reference the 
 following data in the National Drug file (#50.6).                          
                                                                            
 Global: ^PSNDF(             National Drug file (#50.6) Field: .01      VA
 GENERIC NAME            DIRECT GLOBAL READ 
  
 Also, the NDF ENTRY field of the ICR SITE PARAMETERS file (#158.9) may point
 to the National Drug file.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY
  ISC: Hines

NUMBER: 2017                            IA #: 2017
  DATE CREATED: APR 30, 1997            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         ROUTINE: MCUIMAGO
  NAME: DBIA2017                        ID: MCUIMAGO
 GENERAL DESCRIPTION:   This DBIA implements two new Medicine APIs for the
 Imaging package to call.  
  
 The UPDATE^MCUIMAG0() API creates new entries, if needed, in the Medical 
 Patient file and the Medicine Procedure data files.  It also allows the 
 Imaging package to populate the Image multiple in the Medicine Procedure data
 files.  
  
 The KILL^MCUIMAG0() API removes entries from the Image multiples in the 
 Medicine Procedure data files.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: UPDATE
 COMPONENT DESCRIPTION:   
  D UPDATE^MCUIMAGO(MCDATE,MCPROCD0,MCDFN,.MCMAGPTR,[.]MCD0,.OK) 
  
 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.  
  
  Input 
  ~~~~~
  MCDATE     =  Date/Time of a procedure (VA FileMan internal format) 
  
  MCPROCD0   =  A pointer to the Procedure/Subspecialty file (#697.2), 
                e.g., ^MCAR(697.2,MCPROCD0,...  
  
  MCDFN      =  A pointer to the Patient file (#2), e.g., ^DPT(MCDFN,...  
  
  MCMAGPTR() =  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.) 
  
  MCD0       =  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.  
  
  OK         =  A return flag variable 
  
  Output 
  ~~~~~~
  MCMAGPTR() =  An array whose subscripts are pointers to the Image 
                file (#2005)  Returned as: MCMAGPTR('File_#2005_Pointer')= 
                MCFILE ^ MCD0 ^ MCD1, e.g., 
                ^MCAR(MCFILE,MCD0,2005,MCD1,0)='File_#2005_Pointer' 
  
  OK         =  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).  
COMPONENT/ENTRY POINT: KILL
 COMPONENT DESCRIPTION:   
  D KILL^MCUIMAG0(MCFILE,MCD0,MCD1,.OK) 
  
 This entry point removes entries from the Image multiples in the Medicine 
 Procedure data files.  
  
  Input 
  ~~~~~
  MCFILE  =  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) 
  
  MCD0    =  A pointer to one of the entries in one of the Medicine 
             Procedure data files, e.g., ^MCAR(MCFILE,MCD0,...  
  
  MCD1    =  A pointer to one of the entries in the in the Image multiple 
             e.g., ^MCAR(MCFILE,MCD0,2005,MCD1,0)='File_#2005_Pointer' 
  
  OK      =  A return flag variable 
  
  Output 
  ~~~~~~
  OK      =  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.  

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
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
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: 2020                            IA #: 2020
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2020
  ID: PSRX(
GLOBAL REFERENCE: PSRX(D0,0)
FIELD NUMBER: 17                        FIELD NAME: UNIT PRICE OF DRUG
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   A direct reference to the Prescription file is
 requested for the Unit Price of Drug field so the VA Cost of a prescription
 fill can be calculated and billed.  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 2021                            IA #: 2021
  DATE CREATED: MAY 16, 1997            CUSTODIAL PACKAGE: 1
  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
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: 1
  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
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 2023                            IA #: 2023
  GLOBAL ROOT: DD(                      DATE CREATED: MAY 19, 1997
  CUSTODIAL PACKAGE: 1                  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
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
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: 2025                            IA #: 2025
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDCODD
  NAME: DBIA2025                        ID: SDCODD
 GENERAL DESCRIPTION:   This will return the External Value of the Outpatient
 Classification from file 209.41 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$VAL(SCDCTI,Y)
 COMPONENT DESCRIPTION:   Determines External Value of of the Outpatient
 Classification.  
  
 Usage:  S X=$$VAL^SDCODD(SDCTI,Y) 
VARIABLES: SDCTI                        TYPE: Input
 VARIABLES DESCRIPTION:   Outpatient Classification TYPE 
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   Internal value 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   External Value 
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER

NUMBER: 2026                            IA #: 2026
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: SDPCE                        NAME: SDPCE
  ID: SDPCE
 GENERAL DESCRIPTION:   This DBIA will permit PCE to use exiting Scheduling
 function calls to get Eligibility, Appointment Type, and Status of an 
 encounter.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SDPCE
COMPONENT/ENTRY POINT: $$ELAP
 COMPONENT DESCRIPTION:   This function call returns the patient eligibility
 and appointment type data in the following string: 
  
 Elig ptr^ Elig text^ Appt Ptr^ Appt Text 
  
 Usage:  S OUTPUT=$$ELAP^SDPCE(DFN,SC) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient 
VARIABLES: SC                           TYPE: Input
 VARIABLES DESCRIPTION:   Clinic IEN 
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   String:  Elig ptr^ Elig text^ Appt Ptr^ Appt Text 
COMPONENT/ENTRY POINT: $$STATUS
 COMPONENT DESCRIPTION:   This returns the status of an encounter.  
  
 Usage:  S OUTPUT=$$STATUS^SDPCE(SDVSIT) 
VARIABLES: SDVSIT                       TYPE: Input
 VARIABLES DESCRIPTION:   VISIT file IEN 
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   Status of the encounter Internal IEN^External Value 
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Originally EN^SDPCE was run by the Entry Action on
 the protocol SDAM PCE EVENT which is an item on the protocol PXK VISIT DATA
 EVENT. In order to run PXK VISIT DATA EVENT as a TaskMan job the call to
 EN^SDPCE was moved to the routine EVENT^PXKMAIN in patch PX*1*211.  
  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  DATE ACTIVATED: APR 03, 2003

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
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
 and/or FileMan Read to the Visit file: all fields and all cross references.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA
 SUBSCRIBING DETAILS:   MVI requires read access to Visit File to support the
 validity of Date of Death of patients. MVI will determine whether a given
 patient reported as deceased is actually deceased by looking at the Visit file
 to determine if the patient has had any type of interaction at the site.  
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 8/12/24, effective with DSSO*2.0*6. APAT needs
 FileMan read access to the PCE VISIT FILE to check the PATIENT NAME (file
 #9000010 field #.05) field to ensure that the PATIENT NAME (#.02) field in the
 RECORD OF PROS APPLIANCE/REPAIR (#660) record refers to the same patient as
 the VISIT (#1) field in the DSSO PCE STATUS (#23645.3) file.  This was 
 necessary because records can be deleted from the RECORD OF PROS 
 APPLIANCE/REPAIR (#660) file, the IENs may be reused.  

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
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
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
 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
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

NUMBER: 2032                            IA #: 2032
  FILE NUMBER: 3.9                      GLOBAL ROOT: DD(3.91
  DATE CREATED: JUN 10, 1997            CUSTODIAL PACKAGE: 1
  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 
  
 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) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: SEP 01, 1997
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
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
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
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: 1
  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
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
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
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
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

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
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

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
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

NUMBER: 2042                            IA #: 2042
  DATE CREATED: JUN 26, 1997            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: MAGGTPTS
  NAME: DG Patient Sensitivity          ID: MAGGTPTS
 GENERAL DESCRIPTION:   In order to provide a method of maintaining sensitive
 patient protocol through a remote procedure call (RPC), Imaging has copied and 
 modified the code for DGSEC and placed it in MAGGTPTS. 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DGSEC
 COMPONENT DESCRIPTION:   This entry point tests for patient sensitivity.  
VARIABLES: ry                           TYPE: Output
 VARIABLES DESCRIPTION:   RY="0^    not a sensitive patient or access is
 allowed.  RY="-1^   error, patient's sensitivity not determined 
           or user can't access a sensitive patient.  RY="1^    sensitive
 patient. App needs to display message, 
           ask to continue, and  log access if user continues.  
VARIABLES: DFN                          TYPE: Input
COMPONENT/ENTRY POINT: ACCESS
 COMPONENT DESCRIPTION:   RPC Call to send bulletin, and log access by user.  
VARIABLES: RY                           TYPE: Output
VARIABLES: DFN                          TYPE: Input
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

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
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
SUBSCRIBING PACKAGE: SURGERY
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 10/26/18 for VPR*1*8, to support the new
 HealthShare effort.  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 10/13/23, effective with patch PX*1.0*235 for
 documenting ICR in legacy code. 
  DATE ACTIVATED: OCT 26, 2018

NUMBER: 2046                            IA #: 2046
  FILE NUMBER: 409.44                   GLOBAL ROOT: SDD(409.44,
  DATE CREATED: JUN 30, 1997            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  NAME: DBIA2046                        ID: SDD(409.44,
GLOBAL REFERENCE: SDD(409.44,'OE'
 GLOBAL DESCRIPTION:   This cross-reference will be used to look up the ifn of
 the record associated with the OUTPATIENT ENCOUNTER.  
GLOBAL REFERENCE: SDD(409.44,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PROVIDER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This contains the pointer to the NEW PERSON file (#200)
 for the PROVIDER.  
 GENERAL DESCRIPTION:   This will allow the user to use the "OE"
 cross-reference to obtain the ifn of a record, in order to find the value of
 the PROVIDER (.01) field in the OUTPATIENT PROVIDER file (#409.44).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HOME BASED PRIMARY CARE

NUMBER: 2047                            IA #: 2047
  FILE NUMBER: 409.43                   GLOBAL ROOT: SDD(409.43,
  DATE CREATED: JUN 30, 1997            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  NAME: DBIA2047                        ID: SDD(409.43,
GLOBAL REFERENCE: SDD(409.43,'OE',
 GLOBAL DESCRIPTION:   This cross-reference will be used to look up the ifn of
 the record associated with the OUTPATIENT ENCOUNTER.  
GLOBAL REFERENCE: SDD(409.43,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DIAGNOSIS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This contains a pointer to the ICD9 DIAGNOSIS file (#80),
 for the DIAGNOSIS associated with the encounter.  
FIELD NUMBER: .03                       FIELD NAME: DIAGNOSIS RANKING
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the ranking of the particular
 diagnosis related to the encounter.  
 GENERAL DESCRIPTION:   This will allow the user to use the "OE"
 cross-reference to obtain the ifn of a record, in order to find the values of
 the DIAGNOSIS (.01) and the DIAGNOSIS RANKING (.03) fields in the OUTPATIENT
 DIAGNOSIS file (#409.43).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HOME BASED PRIMARY CARE
SUBSCRIBING PACKAGE: MENTAL HEALTH

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
SUBSCRIBING PACKAGE: HOME BASED PRIMARY 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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 2050                            IA #: 2050
  DATE CREATED: JUL 02, 1997            CUSTODIAL PACKAGE: 1
  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
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: 1
  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
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: 1
  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
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: 1
  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
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
 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: 1
  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
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.  
INTEGRATION REFERENCES Redacted List as of 20261106
                                                     NOV 09, 2026@17:23   PAGE 2
--------------------------------------------------------------------------------

  
 Output: $Truth value - 1 equals lock obtained; 0 equals lock failed.  

NUMBER: 2055                            IA #: 2055
  DATE CREATED: JUL 02, 1997            CUSTODIAL PACKAGE: 1
  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
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. 

NUMBER: 2056                            IA #: 2056
  DATE CREATED: JUL 02, 1997            CUSTODIAL PACKAGE: 1
  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
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. 

NUMBER: 2057                            IA #: 2057
  FILE NUMBER: 3.5                      GLOBAL ROOT: %ZIS(1,
  DATE CREATED: JUL 07, 1997            CUSTODIAL PACKAGE: DEVICE HANDLER
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: RETRIEVE CLOSES PRINTER
  ID: %ZIS(1,
GLOBAL REFERENCE: %ZIS(1,IEN,99)
FIELD NUMBER: 16                        FIELD NAME: CLOSEST PRINTER
  LOCATION: 99;1                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Lab package utilizes the CLOSEST PRINTER field in
 the DEVICE field.  Lab requests permission to directly reference
 ^%ZIS(1,ien,99) to retreive this information.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

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
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 
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 9/12/25, effective with patch PX*1.0*244 When PCE
 is deleting data related to the visit in its own file, it verifies the PACKAGE
 the data points to by verifying the existence of the 0 node for the pointer
 value PCE is storing 

NUMBER: 2059                            IA #: 2059
  FILE NUMBER: 100.99                   GLOBAL ROOT: ORD(100.99,
  DATE CREATED: JUL 09, 1997
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: LAB USE OF ORD(100.99
  ID: ORD(100.99,
GLOBAL REFERENCE: ORD(100.99,1,2)
FIELD NUMBER: 22                        FIELD NAME: ELECTRONIC RECORD
  LOCATION: 2;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Lab would like permission to reference the ELECTRONIC
 RECORD field (#22) of the ORDER PARAMETERS file (#100.99).  This is only
 needed while OE/RR 2.5 is running at sites.  Once OE/RR 3.0 is installed
 everywhere, the code can be removed and the DBIA cancelled.  
  STATUS: Withdrawn                     DURATION: Next Version
  GOOD ONLY FOR VERSION: 2.5 of OE/RR
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

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,
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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
 SUBSCRIBING DETAILS:   
  
  DATE ACTIVATED: APR 13, 2012

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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
  ISC: Birmingham
SUBSCRIBING PACKAGE: SURGERY RISK ASSESSMENT
 SUBSCRIBING DETAILS:   Added 6/11/20, effective with SRA*3*3 

NUMBER: 2062                            IA #: 2062
  FILE NUMBER: 771.2                    GLOBAL ROOT: HL(771.2
  DATE CREATED: JUL 11, 1997            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA2062
  ID: HL(771.2
 GENERAL DESCRIPTION:   This agreement is to add the 2.3 version to each
 message.  
  STATUS: Pending
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 2063                            IA #: 2063
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870
  DATE CREATED: JUL 11, 1997            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA2063
  ID: HLCS(870
 GENERAL DESCRIPTION:   This agreement is for FileMan read access to the HL
 LOGICAL LINK (#870) file, field LLP PARAMETER (#2).  
  STATUS: Pending
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

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
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
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 10/13/23, effective with patch PX*1.0*235 for
 documenting ICR in legacy code. 

NUMBER: 2066                            IA #: 2066
  DATE CREATED: JUL 21, 1997            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Other                           NAME: DBIA2066
 GENERAL DESCRIPTION:   This constitutes an agreement whereby the DHCP
 Engineering Package (also known as AEMS/MERS) is allowed to use Field #62
 (named 'RESERVED') of the Terminal Type File (#3.2) to allow sites to
 customize the way they print bar coded equipment and location labels.  
  
 The bar code printing routines (ENLBL4 and ENLBL7) within the Engineering 
 Package contain program segments that send formatting instructions and print
 requests to the user-selected bar code printer. The Engineering Package
 assumes that the bar code printer is an Intermec 86xx compatible device and
 that the site wants standard formatting.  
  
 Engineering needs: 
  
        1) a mechanism for interfacing to bar code printers that are not 
           Intermec 86xx compatible, and 
        2) a mechanism to allow sites to tailor the formats of their bar 
           coded equipment and location labels to meet local needs, if they 
           so desire.  
           
 This private integration agreement gives the Engineering Package permission to
 reference Field #62 of the Terminal Type File (#3.2) entry that is pointed to
 by the Device File (#3.5) entry of the selected bar code printer. The syntax
 of the reference will be: 
  
        S X=$$GET1^DIQ(3.2,ENBCIOST(0),62) 
  
 where ENBCIOST(0) is the internal entry number of the bar code printer within
 the Terminal Type File.  
  
 If $P(X,":") is equal to "ENG" then the Engineering Package will know that
 pieces 2 through 5 (using ":" as a delimiter) will be executable statements,
 as follows: 
  
        $P(X,":",2) will specify equipment formatting, 
        $P(X,":",3) will specify equipment data, 
        $P(X,":",4) will specify location formatting, and 
        $P(X,":",5) will specify location data.  
  
 An example of what a representative entry may look like is: 
  
        ENG:D EQFOR^ENZLBL:D EQDAT^ENZLBL:D LOCFOR^ENZLBL:D LOCDAT^ENZLBL 
  
 In this example: 
  
   program segment EQFOR^ENZLBL would be executed instead of FORMAT1^ENLBL7 
      "      "     EQDAT^ENZLBL   "   "     "        "    "  NXPRT1^ENLBL7 
      "      "     LOCFOR^ENZLBL  "   "     "        "    "  FORMAT1^ENLBL7 
      "      "     LOCDAT^ENZLBL  "   "     "        "    "  LOCPRT^ENLBL4 
  
 If any of pieces 2 through 5 in a RESERVED field that begins with 'ENG:' is
 null, then the corresponding code in routine ENLBL4 or ENLBL7 will be 
 executed.  
  
 Local variables in the ENBC* namespace will be passed to each of the 
 executable statements, as follows: 
  
        ENBCIO      will be the IO    variable of the bar code printer 
        ENBCIOSL      "  "   "  IOSL     "     "   "   "   "     " 
        ENBCIOF       "  "   "  IOF      "     "   "   "   "     " 
        ENBCION       "  "   "  ION      "     "   "   "   "     " 
        ENBCIOST      "  "   "  IOST     "     "   "   "   "     " 
        ENBCIOST(0)   "  "   "  IOST(0)  "     "   "   "   "     " 
  
 Local variable DA will be passed to the executable code that processes 
 equipment data and to the executable code that processes location data. In the
 case of equipment data, DA will be the internal entry number of a record in
 the Equipment File (#6914). For location data, DA will be the internal entry
 number of a record in the Space File (#6928).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ENGINEERING        ISC: Washington/Silver Spring

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 FILE VERSION/APPLICATION HISTORY
  ID: XPDIP
 GENERAL DESCRIPTION:   These functions can be used during the Pre or Post
 Install routine to update the VERSION multiple and the PATCH APPLICATION
 HISTORY multiple in the PACKAGE file.  
  STATUS: Active
KEYWORDS: PACKAGE
KEYWORDS: VERSION
KEYWORDS: APPLICATION HISTORY
COMPONENT/ENTRY POINT: $$PKGPAT(package ien, version, .ARRAY)
 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.  
  e.g.  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 the Description 
                  e.g.  ^XTMP($J,""WP"") 
VARIABLES: $$PKGPAT                     TYPE: Output
 VARIABLES DESCRIPTION:   version ien^patch ien 
COMPONENT/ENTRY POINT: $$PKGVER(package ien, .version)
 COMPONENT DESCRIPTION:   Update the VERSION multiple in the PACKAGE file, #9.4 
VARIABLES: package ien                  TYPE: Input
 VARIABLES DESCRIPTION:   PACKAGE file entry ien 
VARIABLES: version                      TYPE: Input
 VARIABLES DESCRIPTION:   This can be either a string or array.  If it is an
 array, then it must be passed by reference.  
  
  version= 
   version number^date distributed^date installed^installed by user ien 
  
  
  version(1) = closed global root of the location of the Description 
   e.g.  ^XTMP($J,""WP"") 
  
  
  all date values must be internal FileMan date format 
  version number must contain a decimal point 
VARIABLES: $$PKGVER                     TYPE: Output
 VARIABLES DESCRIPTION:   version ien 
  DATE ACTIVATED: FEB 02, 2018

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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: SEP 1997
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                            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: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE
  ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   1/10/22: Patient Representative Decom patch QAC*2.0*25
 has been released on 01/10/2022 with a Compliance date of 2/10/22. Patient
 Representative subscription retired effective with a Compliance date of
 2/10/22.  

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
GLOBAL REFERENCE: DPT('SSN',
FIELD NUMBER: .09                       FIELD NAME: SOCIAL SECURITY NUMBER
  LOCATION: x-ref                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This cross-reference is used by CIRN (Clinical
 Information Resource Network) and Master Patient Index VistA as a means of
 data validation when determining if a PATIENT (File #2) record exists and
 reporting functions.  
 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.  
  
 Revision History: 
  
   06/23/26 MPIF*1.0*81 Historical External Reference update: 
            Global Reference for ^DPT('SSN', added for read access 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA
 SUBSCRIBING DETAILS:   Updated 06/23/26 to include ^DPT('SSN') read access 
SUBSCRIBING PACKAGE: HEALTH DATA REPOSITORY
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   TIU access is only permitted for the AICN x-ref.  
  DATE ACTIVATED: AUG 04, 1997

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
SUBSCRIBING PACKAGE: FEE BASIS          ISC: Washington/Silver Spring
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 2073                            IA #: 2073
  FILE NUMBER: 740                      GLOBAL ROOT: QA(740,
  DATE CREATED: AUG 14, 1997
  CUSTODIAL PACKAGE: QUALITY ASSURANCE INTEGRATION
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: PATIENT REPRESENTATIVE
  ID: QA(740,
GLOBAL REFERENCE: QA(740.01)
FIELD NUMBER: 741.1                     FIELD NAME: MULTI-DIVISIONAL FACILITY
  LOCATION: OS;9                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: QA(740.02
FIELD NUMBER: .01                       FIELD NAME: HOSPITAL DIVISION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   
  
 The Patient Representation package needs to become multi-divisional.  There is
 a QUALITY ASSURANCE SITE PARAMETER file (#740) that stores information for all
 the Quality Assurance packages.  This file belongs to Quality Assurance
 Integration.  Patient Representative would like to ask sites (in a pre-install
 patch routine) if they should be multi-divisional and if so, ensure that the
 hospital divisions are listed.  There are existing fields to store this
 information.  
        field #741.1   Multi-divisional Facility 
        field #741.11  Hospital Division (multiple) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE
  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
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
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
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
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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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: 1
  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) 
  STATUS: Active                        DURATION: Next Version
  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
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
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
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
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
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
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
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany

NUMBER: 2089                            IA #: 2089
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Other                           NAME: DBIA2089
 GENERAL DESCRIPTION:   PCE has a copy of Schedulings protocol SDAM LIST MENU
 called PXCE SDAM LIST MENU with a default of Total Appt Profile and different
 Entry and Exit actions.  This DBIA is to allow PCE to include Scheduling's
 protocols listed below on PCE's protocol.  
  
 NAME: PXCE SDAM LIST MENU               ITEM TEXT: Appointment Lists 
   TYPE: menu 
   PACKAGE: PCE PATIENT CARE ENCOUNTER 
  DESCRIPTION:   This action allows you to change which appointments will 
  be displayed based on their status of the appointments. For example, you 
  may change the display to list cancelled, checked in, checked out, future 
  appointments, inpatient appointments, appointment where no action has 
  been taken, non count appointments, no show appointments or all 
  appointments.  
  
   COLUMN WIDTH: 40                      IDENTIFIER: AL ITEM: SDAM LIST CHECKED
 IN              MNEMONIC: CI 
   SEQUENCE: 1 ITEM: SDAM LIST NO SHOWS                MNEMONIC: NS 
   SEQUENCE: 2 ITEM: SDAM LIST ALL                     MNEMONIC: TA 
   SEQUENCE: 3 ITEM: SDAM LIST NO ACTION               MNEMONIC: NA 
   SEQUENCE: 4 ITEM: SDAM LIST CANCELLED               MNEMONIC: CA 
   SEQUENCE: 5 ITEM: SDAM LIST FUTURE                  MNEMONIC: FU 
   SEQUENCE: 6 ITEM: SDAM LIST INPATIENT               MNEMONIC: IP 
   SEQUENCE: 7 ITEM: SDAM LIST NON-COUNT               MNEMONIC: NC 
   SEQUENCE: 8 ITEM: SDAM LIST CHECKED OUT             MNEMONIC: CO 
   SEQUENCE: 9 
   EXIT ACTION: S:'$D(VALMBCK) VALMBCK="" D EXIT^PXCESDAM 
   ENTRY ACTION: D FULL^VALM1 S XQORM(0)="1A" 
   HEADER: W ""                          MENU PROMPT: Select List: 
   MENU DEFAULT: Total Appt Profile      TIMESTAMP: 57166,50591 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
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(
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
GLOBAL REFERENCE: DGPM('C',DFN,DA
 GENERAL DESCRIPTION:   THIS ICR ALLOWS ACCESS TO PATIENT MOVEMENT DATA.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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 
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 03/22/21, effective with Mental Health's Suicide
 Prevention Project, patch YS*5.01*135.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 3/3/2022, effective with DSSV*1.1 DSS Class 3
 product Document Only DSSV is using the "APTT3" cross-reference to find most
 recent admission/discharge in given date 
  
 1/31/2023, added "C" index to retrieve the movement before discharge 
  DATE ACTIVATED: OCT 12, 2012

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
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
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: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: CHECK FOR INACTIVE PROVIDER     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
FIELD NUMBER: 53.1
  FIELD NAME: AUTHORIZED TO WRITE MEDS ORDER
  LOCATION: PS;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 53.3                      FIELD NAME: VA#
  LOCATION: PS;3                        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.  
  
 Revision History: 
  - 2/26/25-Added OE/RR as a subscriber to document historical usage, which
 resulted in adding Field 53.1 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany
 SUBSCRIBING DETAILS:   PCE uses Field 53.4 INACTIVE DATE 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 2/26/25 effective with OR*3.0*633 to document
 historical use of Field 53.1 AUTHORIZED TO WRITE MEDS ORDER and 53.4 INACTIVE
 DATE since approximately 2020 or earlier.  
  
 Updated 11/4/26 effective with patch OR*3.0*640 to document historical use of
 Field 53.3 VA# since approximately 2020 or earlier.  

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
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
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: 1
  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
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: 1
  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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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 
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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. 127.0.0.15 
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
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
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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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: 2123                            IA #: 2123
  FILE NUMBER: 3.081                    GLOBAL ROOT: XUSEC(
  DATE CREATED: SEP 05, 1997            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2123
  ID: XUSEC(
GLOBAL REFERENCE: XUSEC('PSJ RPHARM',DUZ)
 GLOBAL DESCRIPTION:   This file records sign-on/sign-off times by user,
 device, job, UCI, and CPU. It is cross-referenced by user, device, and
 sign-off time.  
 GENERAL DESCRIPTION:   Drug Accountability/Inventory Interface v3.0 is
 requesting an integration agreement to read the SIGN-ON LOG FILE's (#3.081)
 ^XUSEC("PSJ RPHARM") node. It is used to determine if the user holds the
 pharmacist key.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
  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
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

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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

NUMBER: 2126                            IA #: 2126
  FILE NUMBER: 59.6                     GLOBAL ROOT: PS(59.6
  DATE CREATED: SEP 08, 1997            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: ACCESS FILE 59.6
  ID: PS(59.6
GLOBAL REFERENCE: PS(59.6,D0,0)
FIELD NUMBER: 1                         FIELD NAME: MAR ORDER SELECTION DEFAULT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: PRINT PENDING ORDERS ON MAR
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DAYS UNTIL STOP DATE/TIME
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: SAME STOP DATE ON ALL ORDERS
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05
  FIELD NAME: DEFAULT START DATE CALCULATION
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .07                       FIELD NAME: TIME OF DAY ORDERS STOP
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .08                       FIELD NAME: START TIME FOR 24 HOUR MAR
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .09                       FIELD NAME: STOP TIME FOR MAR
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .11                       FIELD NAME: DAYS NEW LABELS LAST
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .12                       FIELD NAME: LABEL FOR WARD STAFF
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .13                       FIELD NAME: WARD LABEL PRINTER
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .14                       FIELD NAME: PHARMACY LABEL PRINTER
  LOCATION: 0;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .15                       FIELD NAME: LABEL ON AUTO-DISCONTINUE
  LOCATION: 0;15                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .16                       FIELD NAME: LABEL FOR PHARMACY
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   PDM requests permission to look at INPATIENT WARD
 PARAMETERS file 59.6.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham
  DATE ACTIVATED: SEP 01, 2020

NUMBER: 2127                            IA #: 2127
  FILE NUMBER: 50.3                     GLOBAL ROOT: PS(50.3
  DATE CREATED: SEP 08, 1997
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  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:   This file was originally associated with Inpatient
 Medications as the custodial package.  Due to the conversion of Rational to
 GitHub, this file is now assigned to the Pharmacy Data Management Package,
 making this ICR no longer necessary because PDM was the only subscribing
 package.  Additionally the 50.3 file is no longer used, but has not gone
 through a formal retirement in the ICRs.  
  
 Old text before 9/1/20: PDM requests permission to look at PRIMARY DRUG file
 50.3.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: SEP 01, 2020
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham
  DATE ACTIVATED: SEP 01, 2020

NUMBER: 2128                            IA #: 2128
  FILE NUMBER: 57.7                     GLOBAL ROOT: PS(57.7
  DATE CREATED: SEP 08, 1997            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2128
  ID: PS(57.7
GLOBAL REFERENCE: PS(57.7,DO,0)
FIELD NUMBER: .01                       FIELD NAME: WARD
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PS(57.7,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: TEAM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PS(57.7,D0,1,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: ROOM-BED
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   PDM requests permission to look at MEDICATION
 ADMINISTERING TEAM file 57.7.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

NUMBER: 2129                            IA #: 2129
  FILE NUMBER: 57.5                     GLOBAL ROOT: PS(57.5
  DATE CREATED: SEP 08, 1997            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2129
  ID: PS(57.5
GLOBAL REFERENCE: PS(57.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: TYPE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4
  FIELD NAME: LENGTH OF PICK LIST (in hours)
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PS(57.5,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: WARD
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PS(57.5,D0,2)
FIELD NUMBER: 2                         FIELD NAME: PICK LIST DATA
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PS(57.5,D0,3)
FIELD NUMBER: 30                        FIELD NAME: BAXTER ATC DEVICE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 31                        FIELD NAME: USE OLD ATC INTERFACE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PS(57.5,D0,5)
FIELD NUMBER: 5.01                      FIELD NAME: PICK LIST - ROOM/BED SORT
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.02                      FIELD NAME: PICK LIST - OMIT WARD SORT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.03
  FIELD NAME: PICK LIST - OMIT ROOM-BED SORT
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   PDM requests permission to look at WARD GROUP file
 57.5.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

NUMBER: 2130                            IA #: 2130
  FILE NUMBER: 53.2                     GLOBAL ROOT: PS(53.2
  DATE CREATED: SEP 08, 1997            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2130
  ID: PS(53.2
GLOBAL REFERENCE: PS(53.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PS(53.2,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DRUG
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: DAY (nD) OR DOSE (nL) LIMIT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: MED ROUTE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7                         FIELD NAME: SCHEDULE TYPE
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8                         FIELD NAME: SCHEDULE
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DOSAGE ORDERED
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: START DAY AND TIME
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PS(53.2,D0,1,D1,1)
FIELD NUMBER: 9                         FIELD NAME: SPECIAL INSTRUCTIONS
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PS(53.2,D0,1,D1,2,D2,0)
FIELD NUMBER: .01                       FIELD NAME: DISPENSE DRUG
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: UNITS PER DOSE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   PDM requests permission to look at UNIT DOSE ORDER SET
 file 53.2.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

NUMBER: 2134                            IA #: 2134
  FILE NUMBER: 50.2                     GLOBAL ROOT: PS(50.2
  DATE CREATED: SEP 08, 1997            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2134
  ID: PS(50.2
GLOBAL REFERENCE: PS(50.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PS(50.2,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: IV DRUG
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: GENERIC DRUG
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   PDM requests permission to look at IV CATEGORY file
 50.2.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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: 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
FIELD NUMBER: 49                        FIELD NAME: ORDERS FILE ENTRY
  LOCATION: 0;21                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the pointer value to the ORDER (#100) File.  
FIELD NUMBER: 62                        FIELD NAME: IV ROOM
  LOCATION: 8;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 113                       FIELD NAME: CLINIC
  LOCATION: DSS;1                       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).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham
  DATE ACTIVATED: JAN 29, 2020

NUMBER: 2141                            IA #: 2141
  FILE NUMBER: 51.5                     GLOBAL ROOT: DIC(51.5,
  DATE CREATED: SEP 09, 1997
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2141
  ID: DIC(51.5,
GLOBAL REFERENCE: DIC(51.5,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SYNONYM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The SYNONYM field contains the order unit from the prime
 vendor that is different from the ORDER UNIT field for the unit of order.  
 GLOBAL DESCRIPTION:   The SYNONYM multiple contains order units from the prime
 vendor that are different from the ORDER UNIT field for the unit of order.  
 GENERAL DESCRIPTION:   Drug Accountability/Inventory Interface (DA) is
 requesting an integration agreement with Pharmacy Data Management to create
 and write to a new SYNONYM field in a new SYNONYM multiple. In the DA v3.0
 prime vendor interface, the prime vendor sends an invoice data file containing
 line items that were shipped. Each line item has a two-character order unit.
 If their order unit is not in the ORDER UNIT FILE, the user is asked to match 
 it to an existing order unit. When the data is verified, the prime vendor's
 two-character order unit is added to the SYNONYM field (#.01) in the SYNONYM
 multiple and in a new "APV" cross-reference.  
  
 The next time the order unit is received the link is used to the ABBREVIATION
 field (#.01). This is done by reading the "APV" cross-reference.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
  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:   
 ************************************************************************
 The Library package was decommissioned with LBR*2.5*15.  This ICR was retired
 with the release of the Library patch.  
 ************************************************************************
  
 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: Retired                       DURATION: Next Version
  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:   
 ************************************************************************
 The Library package was decommissioned with LBR*2.5*15.  This ICR was retired
 with the release of the Library patch.  
 ************************************************************************
  
 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: Retired                       DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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

NUMBER: 2147                            IA #: 2147
  DATE CREATED: SEP 17, 1997            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSGFILD1
  NAME: DBIA2147                        ID: PSGFILD1
 GENERAL DESCRIPTION:   PDM requests permission to use PSGFILD1 Inpatient
 Medications routine.  A ZOSF test will be done before invoking the routine.  
 This routine is invoked by routine PSSFIl which prompts the user to be 
 displayed instructions for auto-discontinue set-up.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ENWAI
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

NUMBER: 2148                            IA #: 2148
  DATE CREATED: SEP 17, 1997            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSGGAO
  NAME: DBIA2148                        ID: PSGGAO
 GENERAL DESCRIPTION:   PDM requests permission to use the PSGGAO Inpatient
 Medications routine.  A ZOSF test will be done before invoking the routine.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

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
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

NUMBER: 2152                            IA #: 2152
  DATE CREATED: SEP 17, 1997            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSGSET
  NAME: DBIA2152                        ID: PSGSET
 GENERAL DESCRIPTION:   PDM requests permission to use the PSGSET Inpatient
 Medications routine.  A ZOSF test will be done before invoking the routine.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

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
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

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
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

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
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

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
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

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
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

NUMBER: 2159                            IA #: 2159
  DATE CREATED: SEP 29, 1997            CUSTODIAL PACKAGE: 1
  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." 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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
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: 2162                            IA #: 2162
  FILE NUMBER: 771.2                    GLOBAL ROOT: HL(771.2,
  DATE CREATED: OCT 29, 1997            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            NAME: HL7 MESSAGE TYPE
  ORIGINAL NUMBER: 2161                 ID: HL(771.2,
GLOBAL REFERENCE: HL(771.2,'B'
 GLOBAL DESCRIPTION:   The "B" cross-reference may be checked.  Pre-approved
 entries may be added to the file.  
 GENERAL DESCRIPTION:   The creation of new entries must be cleared through the
 HL7 development team.  New entries may be added with a call to FILE^DICN and a
 call to IX1^DIK during the package post-installation.  
  STATUS: Pending

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
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
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.  

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
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 

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: Controlled Subscription
  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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  

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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham

NUMBER: 2168                            IA #: 2168
  FILE NUMBER: 771.4                    GLOBAL ROOT: HL(771.4,
  DATE CREATED: OCT 30, 1997            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: HL7 DATA TYPE
  ORIGINAL NUMBER: 2161                 ID: HL(771.4,
GLOBAL REFERENCE: HL(771.4,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 FIELD DESCRIPTION:   The two character HL7 data type abbreviation.  
 GENERAL DESCRIPTION:   The Baxter Sure-Med Pharmacy Interface requests an
 agreement with the HL7 module to reference the HL7 Data Type file (#771.4).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 2169                            IA #: 2169
  DATE CREATED: OCT 30, 1997            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSGVBW
  NAME: VERIFY PHARMACY ORDERS          ORIGINAL NUMBER: 2161
  ID: PSGVBW
 GENERAL DESCRIPTION:   The Baxter Sure-Med Pharmacy Interface requests
 approval to copy program PSGVBW to VEFPVER and modify it to call HL7 RDE
 segment API.  This generates a RDE HL7 message to transmit to the Baxter 
 Sure-Med Dispensing Cabinet.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GO
 COMPONENT DESCRIPTION:   At line GO+6,  code was added to call VEFPRDE, the
 RDE HL7 API. Routine was renamed because of additional code.  
VARIABLES: PSGOEA                       TYPE: Used
 VARIABLES DESCRIPTION:   If defined as "V", then order is being verified. 
 Only verified orders will be sent to the Baxter Sure-Med host system.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN.  
VARIABLES: PSGORD                       TYPE: Input
 VARIABLES DESCRIPTION:   Order IEN.  
VARIABLES: VORSTAT                      TYPE: Input
 VARIABLES DESCRIPTION:   The order event code.  The codes are as follows: 
   NW = New Order 
   CA = Cancel Order 
   DC = Discontinue Order 
   HD = Hold Order 
   RL = Release Previous Hold 

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
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 
  
COMPONENT/ENTRY POINT: $$HPADD
 COMPONENT DESCRIPTION:   This function returns the correct historical physical
 address information, if available, for an Institution in an up-arrow delimited 
 string (street addr^city^state^zip) for a given Internal Entry Number and 
 Effective Date. If no historical physical address information is available
 based on the ien and effective date, a null value will be returned.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number 
VARIABLES: XUEDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Effective Date for Historical Address search 
COMPONENT/ENTRY POINT: $$CERNER
 COMPONENT DESCRIPTION:   This function checks if a facility has been converted
 to CERNER.  
  ; Take in STA = Station number 
  ; Return -1 for invalid station number 
  ; Return 1 for CERNER station 
VARIABLES: STA                          TYPE: Input
 VARIABLES DESCRIPTION:   Station number 
  DATE ACTIVATED: MAR 12, 2020

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
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
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
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
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
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
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
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: INSTITUTED BY
  LOCATION: 0;6                         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
FIELD NUMBER: .07                       FIELD NAME: INTERVENTION
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .09                       FIELD NAME: WAS PROVIDER CONTACTED
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .11                       FIELD NAME: PROVIDER CONTACTED
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .12                       FIELD NAME: RECOMMENDATION ACCEPTED
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .13                       FIELD NAME: AGREE WITH PROVIDER
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .16                       FIELD NAME: DIVISION
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .17                       FIELD NAME: FINANCIAL COST
  LOCATION: 0;17                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1100                      FIELD NAME: OTHER FOR INTERVENTION
  LOCATION: 11;0                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1200                      FIELD NAME: OTHER FOR RECOMMENDATION
  LOCATION: 12;0                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1300                      FIELD NAME: REASON FOR INTERVENTION
  LOCATION: 13;0                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1400                      FIELD NAME: ACTION TAKEN
  LOCATION: 14;0                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1500                      FIELD NAME: CLINICAL IMPACT
  LOCATION: 15;0                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1600                      FIELD NAME: FINANCIAL IMPACT
  LOCATION: 16;0                        ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Inpatient Medications requests permission to look at
 APSP INTERVENTION file 9009032.4.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 5/28/24 to execute code through middleware
 HealthConnect.  
  DATE ACTIVATED: MAY 28, 2025

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
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 

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.  
  
 Revisions: The CPRS33 project included updates to add two new fields, approved
 by the DBA: 
  59.7,103      DURATION OVERRIDE HANDLING                   62;1 
  59.7,104      DURATION OVERRIDE MESSAGE                    62;2 
  
 The new fields will be used (read) by the INPATIENT MEDICATIONS application,
 PSS*1*251 and PSJ*5.0*375.  
  
 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 
  59.7,103      DURATION OVERRIDE HANDLING                   62;1 
  59.7,104      DURATION OVERRIDE MESSAGE                    62;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
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham
  DATE ACTIVATED: AUG 17, 2023

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                              STATUS: Active
  DURATION: Till Otherwise Agreed
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)
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
 SUBSCRIBING DETAILS:   Added 5/10/24, effective with patch GMRV*5.0*40 to call
 FIDATA^PXRM. In order for Vitals to determine if a patient has CHF, the
 recommendation was to use a Reminder Taxonomy and then utilize PXRM to
 evaluate a reminder to obtain the information.  
SUBSCRIBING PACKAGE: HEALTH DATA REPOSITORY
 SUBSCRIBING DETAILS:   Added 7/13/26, effective with patch HDS*1*100 to call
 MAIN^PXRM. The VET-HOME agents need to reference Toxic Exposure Screening
 reminder when assisting veterans.  
  DATE ACTIVATED: JUN 27, 2012

NUMBER: 2183                            IA #: 2183
  FILE NUMBER: 3.081                    GLOBAL ROOT: XUSEC(
  DATE CREATED: OCT 15, 1997            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2183
  ID: XUSEC(
GLOBAL REFERENCE: XUSEC(PSJ RPHARM,D0)
FIELD NUMBER: .01                       FIELD NAME: USER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the user that signed on. 
 GLOBAL DESCRIPTION:   This file records sign-on/sign-off times by user,
 device, job, UCI, and CPU. It is cross-referenced by user, device, and
 sign-off time.  
 GENERAL DESCRIPTION:   Drug Accountability/Inventory Interface v3.0 is
 requesting an integration agreement to read the SIGN-ON LOG FILE's (#3.081)
 ^XUSEC("PSJ RPHARM") node. It is used to determine if the user holds the
 pharmacist key.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
  ISC: Birmingham

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
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
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
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 

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
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
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
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
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

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
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
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE

NUMBER: 2193                            IA #: 2193
  DATE CREATED: OCT 22, 1997            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSGAMSA
  NAME: DBIA2193                        ID: PSGAMSA
 GENERAL DESCRIPTION:   Drug Accountability/Inventory Interface is requesting
 an integration agreement with Inpatient Medications to insert two lines of
 code in routine PSGAMSA. This code is used to collect Unit Dose dispensing, 
 returns, extras, & pre-exchange needs.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ENLOG+7 & ENLOG+8
 COMPONENT DESCRIPTION:   The inserted code is executed only if Drug
 Accountability/Inventory V. 3.0 or greater is installed. If so, a check for
 the existence of routine PSAPSI5 is made. If the routine is on the system
 EN^PSAPSI5 is executed.  
  
 Inserted DA code at ENLOG+7 & ENLOG+8 
 -------------------------------------
 I +$$VERSION^XPDUTL("DRUG ACCOUNTABILITY")'<3.0 D .I $D(^%ZOSF("TEST")) S
 X="PSAPSI5" X ^%ZOSF("TEST") K X I  D EN^PSAPSI5 
VARIABLES: PSGBK                        TYPE: Used
 VARIABLES DESCRIPTION:   PSBBK checks for Drug Acct background job Kernel V.
 8.0 & Kernel V. 7.1.  
VARIABLES:  
VARIABLES: PSGDRG                       TYPE: Input
 VARIABLES DESCRIPTION:   PSGDRG is the drug internal entry number in the DRUG
 file (#50). It is passed from PSGAMSA to PSAPSI5. It is used to determine if
 the drug is stored in the pharmacy location. If so, PSGDRG is stored in the 
 ^XTMP("PSAPL") global along with its dispensing data.  
VARIABLES: PSGWARD                      TYPE: Input
 VARIABLES DESCRIPTION:   PSGWARD is the ward's internal entry number in the
 WARD LOCATION file (#42). It is passed from PSGAMSA to PSAPSI5. It is used to
 determine if the ward is assigned to the pharmacy location.  
VARIABLES: PSGPLFDT                     TYPE: Input
 VARIABLES DESCRIPTION:   PSGPLFDT is the file date of the pick list. It is
 stored in the ^XTMP("PSAPL") global.  
VARIABLES: PSGX                         TYPE: Input
 VARIABLES DESCRIPTION:   PSGX is the number of dispense units. It is stored in
 the ^XTMP("PSAPL") global.  
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
  ISC: Birmingham

NUMBER: 2194                            IA #: 2194
  DATE CREATED: OCT 22, 1997            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSGPLF
  NAME: DBIA2194                        ID: PSGPLF
 GENERAL DESCRIPTION:   Drug Accountability/Inventory Interface is requesting
 an integration agreement with Inpatient Medications to insert a line of code
 in routine PSGPLF. This code is used to collect Unit Dose dispensing, returns, 
 extras, & pre-exchange needs.  
  
 Existing Code at FILE+9 
 -----------------------
   S $P(ND,"^",2+PS)=$P(ND,"^",2+PS)+Y,$P(ND,"^",3+PS)=$P(ND,"^",3+PS)+COSD 
 1,1,D2,1,D3,0) G:Z OS 
  
 Inserted Code at FILE+9:FILE+12 
 ------------------------------
   S $P(ND,"^",2+PS)=$P(ND,"^",2+PS)+PSGY,$P(ND,"^",3+PS)=$P(ND,"^",3+PS) 
 +COST,^PS(57.6,D0,1,D1,1,D2,1,D3,0)=ND L -^PS(57.6,D0,1,D1,1,D2,1,D3,0) 
   I +$$VERSION^XPDUTL("DRUG ACCOUNTABILITY")'<3.0 D 
   .I $D(^%ZOSF("TEST")) S X="PSAPSI5" X ^%ZOSF("TEST") K X I  S PSGRTN= 
 "PSGPLF" D EN^PSAPSI5 K PSGRTN 
   G:PSGZ OS 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: FILE+9:FILE+12
 COMPONENT DESCRIPTION:   FILE+9 is broken before G:PSGZ OS. The inserted code
 is executed only if Drug Accountability/Inventory V. 3.0 or greater is
 installed. If so, a check for the existence of routine PSAPSI5 is made. If the
 routine is on the system EN^PSAPSI5 is executed. G:PSGZ OS is places at
 FILE+12.  
  
 Inserted Code at FILE+9:FILE+12 
 ------------------------------
   S $P(ND,"^",2+PS)=$P(ND,"^",2+PS)+PSGY,$P(ND,"^",3+PS)=$P(ND,"^",3+PS) 
 +COST,^PS(57.6,D0,1,D1,1,D2,1,D3,0)=ND L -^PS(57.6,D0,1,D1,1,D2,1,D3,0) 
   I +$$VERSION^XPDUTL("DRUG ACCOUNTABILITY")'<3.0 D 
   .I $D(^%ZOSF("TEST")) S X="PSAPSI5" X ^%ZOSF("TEST") K X I  S PSGRTN= 
 "PSGPLF" D EN^PSAPSI5 K PSGRTN 
   G:PSGZ OS 
VARIABLES: D3                           TYPE: Input
 VARIABLES DESCRIPTION:   D3 is the drug internal entry number in the DRUG file
 (#50). It is passed from PSGPLF to PSAPSI5. It is used to determine if the
 drug is stored in the pharmacy location. If so, D3 is stored in the
 ^XTMP("PSAPL") global along with its dispensing data.  
VARIABLES: D1                           TYPE: Input
 VARIABLES DESCRIPTION:   D1 is the ward's internal entry number in the WARD
 LOCATION file (#42). It is passed from PSGPLF to PSAPSI5. It is used to
 determine if the ward is assigned to the pharmacy location.  
VARIABLES: D0                           TYPE: Input
 VARIABLES DESCRIPTION:   D0 is the file date of the pick list. It is stored in
 the ^XTMP("PSAPL") global.  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   Y is the number of dispense units. It is stored in
 the ^XTMP("PSAPL") global.  
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
  ISC: Birmingham

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
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   Added 5/13/16,ICR subscription missed from previous
 project 

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 EMAIL GROUP 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
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING

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
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 
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 10/14/25 effective with DSIY*1.5*6 to retrieve
 Install date & time.  

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
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
  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: Controlled Subscription
  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
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
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 6/6/19 so VPR provide Custom Services to the
 Pharmacy Advanced Medication Platform (AMPL) GUI project for prescription
 display information. Effective with VPR*1*14.  

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
COMPONENT/ENTRY POINT: AREC
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 2202                            IA #: 2202
  DATE CREATED: OCT 28, 1997            CUSTODIAL PACKAGE: CMOP
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSXOPUTL
  NAME: DBIA2202                        ID: PSXOPUTL
 GENERAL DESCRIPTION:   The Outpatient Pharmacy package routine, PSOORNE3,
 calls the CMOP routine, PSXOPUTL to get CMOP information from the Outpatient
 Pharmacy files and the CMOP files. This information is used to display
 information about CMOP prescriptions.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
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
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
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
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
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
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
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
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: 2210                            IA #: 2210
  FILE NUMBER: 62                       GLOBAL ROOT: LAB(62
  DATE CREATED: MAR 01, 2006            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: FILE 62
  ID: LAB(62
GLOBAL REFERENCE: LAB(62,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES

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
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
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
  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
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: INTEGRATION BILLING ACTION FILE ACCESS
  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 application.  
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.  
FIELD NUMBER: .11                       FIELD NAME: AR BILL NUMBER
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The AR BILL NUMBER in external format.  
FIELD NUMBER: .12                       FIELD NAME: AR TRANSACTION NUMBER
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the pointer value to the AR TRANSACTION file.  
FIELD NUMBER: .05                       FIELD NAME: STATUS
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the current status of the INTEGRATED BILLING file
 entry.  
 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 requests permission to
 look at the INTEGRATED BILLING ACTION file 350.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
  DATE ACTIVATED: MAR 09, 2018

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
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 2217                            IA #: 2217
  FILE NUMBER: 60                       GLOBAL ROOT: LAB(60
  DATE CREATED: OCT 30, 1997            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA2217
  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:   This is the name of the Laboratory test.  
FIELD NUMBER: 5                         FIELD NAME: LOCATION (DATA NAME)
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the exact character representation of
 the corresponding entry in the RESULTS file.  
FIELD NUMBER: 400                       FIELD NAME: DATA NAME
  LOCATION: .2;1                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   THis field points to CHEM, HEM, TOX, RIA, SER, etc.  
 GLOBAL DESCRIPTION:   This is the file that holds the names of tests ordered.  
GLOBAL REFERENCE: LAB(60,D0,1,D1,0)
FIELD NUMBER: 6                         FIELD NAME: UNITS
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field points to the DELTA CHECK file.  
 GLOBAL DESCRIPTION:   This file is a pointer multiple. Processing type for
 each entry in the LAB COLLECTION Sample field.  
 GENERAL DESCRIPTION:   The Outpatient Pharmacy package request permission to
 look at the LABORATORY TEST file 60.  
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 2218                            IA #: 2218
  FILE NUMBER: 63.04                    GLOBAL ROOT: LR(D0,'CH',D1,0)
  DATE CREATED: OCT 30, 1997            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA2218
  ID: LR(D0,'CH',D1,0)
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 DESCRIPTION:   This field contains the date and time that the lab
 specimen was taken.  
FIELD NUMBER: .03                       FIELD NAME: DATE REPORT COMPLETED
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the date the report was completed.  
FIELD NUMBER: .05                       FIELD NAME: SPECIMEN TYPE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field conatins the specimen type.  
 GLOBAL DESCRIPTION:   This file contains the patient's laboratory data.  
 GENERAL DESCRIPTION:   The Outpatient Pharamcy package request permission to
 look at the LAB DATA file 63.  
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

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
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: VBECS
 SUBSCRIBING DETAILS:   ADDED 11/27/2007 

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
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.  
COMPONENT/ENTRY POINT: FINAL
VARIABLES: VISIT                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the visit at hand.  
VARIABLES: PKXVST                       TYPE: Input
SUBSCRIBING PACKAGE: EVENT CAPTURE      ISC: Albany
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 7/16/25 effective with patch PX*1.0*244 this
 patch is documenting PCE has been calling       FINAL^SCDXHLDR when checking
 out a Visit in PCE     ListManager.             

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
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

NUMBER: 2222                            IA #: 2222
  FILE NUMBER: 50.606                   GLOBAL ROOT: PS(50.606
  DATE CREATED: NOV 03, 1997
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2222
  ID: PS(50.606
 GENERAL DESCRIPTION:   The Outpatient Pharmacy package request permission to
 look at DOSAGE FORM file 50.606.  
  
 This file was previously in National Drug File, but now it has been moved to
 Pharmacy Data Management 1.0. It is used extensively throughout our routines.
 Therefore, we are requesting read/write access to the entire file and
 cross-references through Fileman and direct reads/write.  
  STATUS: Retired
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

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
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
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
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
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
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Added 9/12/25, effective with patch PSJ*5*453.  As part
 of Methadone Dispensing Tracking Project, will have to make reference to File
 54 (RX CONSULT) , direct global read to the .01 NAME field, in order to
 determine medical warning(s) associated with a specific drug.  

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
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: CMOP
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH

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
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
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
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
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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING

NUMBER: 2234                            IA #: 2234
  FILE NUMBER: 408.32                   GLOBAL ROOT: DG(408.32,
  DATE CREATED: NOV 06, 1997            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA2234
  ID: DG(408.32,
GLOBAL REFERENCE: DG(408.32,D0,0)
FIELD NUMBER: .02                       FIELD NAME: CODE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Enter in this field the code associated with the
 financial test status.  
 GLOBAL DESCRIPTION:   This file contains the statuses associated with the
 means test.  
 GENERAL DESCRIPTION:   DSS Extracts has permission to execute a direct global
 read to the CODE field (#.02) (O;2) in the MEANS TEST STATUS file (#408.32).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany

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,
GLOBAL REFERENCE: DIC(4,'LOC'
 GLOBAL DESCRIPTION:   This cross reference contains the name of the
 institution that may be used to enter Event Capture data.  
GLOBAL REFERENCE: DIC(4,'EC'
FIELD NUMBER: 720                       FIELD NAME: CURRENT LOCATION
  LOCATION: EC;1                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field is used to identify if the location is one
 that can be used within Event Capture.  
 GENERAL DESCRIPTION:   This agreement gives permission to execute a $Order
 direct global read of the 'LOC' Cross Reference on the Institution file (#4).  
  
 In addition, editing of the CURRENT LOCATION field (#720) in the Institution
 file, using supported FileMan calls, is also allowed.  Edits to this field
 affect the 'LOC' Cross Reference by setting or killing it as needed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CURRENT LOCATION
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany
SUBSCRIBING PACKAGE: EVENT CAPTURE
  DATE ACTIVATED: AUG 14, 2017

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
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 - DECISION SUPPORT SYSTEM 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
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

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
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
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
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
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                            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: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE
  ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   1/10/22: Patient Representative Decom patch QAC*2.0*25
 has been released on 01/10/2022 with a Compliance date of 2/10/22. Patient
 Representative subscription retired effective with a Compliance date of
 2/10/22.  

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
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
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
 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
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 - DECISION SUPPORT SYSTEM 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. 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Routine HMPDJ00 calls this API in order to retrieve
 data for the Treating Specialty from the Treating Specialty file (#45.7) and
 the Specialty file (#42.4) if the file exists.  
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
 **************************************************************************
  DATE ACTIVATED: MAY 20, 2010

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
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,
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
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
  DATE ACTIVATED: JAN 21, 2011

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 

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
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: 1
  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
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham

NUMBER: 2254                            IA #: 2254
  FILE NUMBER: 50.5                     GLOBAL ROOT: PS(50.5
  DATE CREATED: DEC 09, 1997
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA-2254
  ID: PS(50.5
GLOBAL REFERENCE: PS(50.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is a descriptive name for a classification
 number.  
 GLOBAL DESCRIPTION:   This is the DRUG CLASSIFICATION file used to do the
 duplicate class checks.  
 GENERAL DESCRIPTION:   Outpatient Pharmacy package request permission to look
 at DRUG CLASSIFICATION file 50.5 via direct global read and Fileman.  
  STATUS: Retired
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 2255                            IA #: 2255
  FILE NUMBER: 0                        GLOBAL ROOT: DD(
  DATE CREATED: DEC 30, 1997            CUSTODIAL PACKAGE: 1
  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
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: 1
  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
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: <none> 
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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
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
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
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
 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
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.  
  
  DATE ACTIVATED: NOV 09, 2012

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
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 2265                            IA #: 2265
  DATE CREATED: JAN 20, 1998
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Chicago                USAGE: Supported
  TYPE: Routine                         ROUTINE: RAO7PC1
  NAME: Rad/Nuc Med return report narrative text (exam)
  ID: RAO7PC1
 GENERAL DESCRIPTION:   EN3^RAO7PC1 can be used to return report narrative text
 associated with a patient's exam.  
  
 ***************************************************************************
 ***************** REASON FOR STUDY data will NOT be available until AFTER 
 ***************** the release of patch RA*5.0*75 by the RADIOLOGY product.  
 ***************************************************************************
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
  GOOD ONLY FOR VERSION: SEE WARNING
COMPONENT/ENTRY POINT: EN3(X)
 COMPONENT DESCRIPTION:   ** Please note that REASON FOR STUDY data will not be
 captured until the release of RA*5.0*75 ** 
  
 EN3^RAO7PC1(X) 
    Input: X = 'X' can assume one of two values: the first retrieves a 
               single report for a single exam.  Passed in as: Patient's 
               DFN^inverse exam date/time^Case IEN (delimited by '^') 
  
               If report(s) for a set of exams are requested, the input 
               value for 'X' will not contain a Case ien value.  Passed 
               in as: Patient's DFN^inverse exam date/time (delimited by 
               '^')
  
    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, but a 'NO 
                REPORT' status if a stub report record was created to 
                contain a pointer to the Imaging package file of images.  
  
                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: Internal entry number 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 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) 
  
            ^TMP($J,"RAE2",patient ien,case ien,procedure name,"TCOM",1) 
  
            Array value 
            -----------
            most recent technologist comment for this case 
  DEFERRED UNTIL: MAR 28, 2007
REMINDER: MAR 28, 2007

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
 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
  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 
  DATE ACTIVATED: FEB 20, 2008          DEFERRED UNTIL: MAR 28, 2007

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
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.  

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
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

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
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
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
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 

NUMBER: 2272                            IA #: 2272
  FILE NUMBER: 392                      GLOBAL ROOT: DGBT(392
  DATE CREATED: FEB 02, 1998            CUSTODIAL PACKAGE: BENEFICIARY TRAVEL
  USAGE: Private                        TYPE: File
  NAME: DBIA2272                        ID: DGBT(392
GLOBAL REFERENCE: DGBT(392,'C'
 GLOBAL DESCRIPTION:   "C" xref.  
GLOBAL REFERENCE: DGBT(392,D0,0)
FIELD NUMBER: 10                        FIELD NAME: AMOUNT PAYABLE
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGBT(392,D0,M)
FIELD NUMBER: 31                        FIELD NAME: ONE WAY/ROUND TRIP
  LOCATION: M;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 33                        FIELD NAME: TOTAL MILEAGE AMOUNT
  LOCATION: M;3                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2273                            IA #: 2273
  FILE NUMBER: 161.8                    GLOBAL ROOT: FBAA(161.8
  DATE CREATED: FEB 02, 1998            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  NAME: DBIA2273                        ID: FBAA(161.8
GLOBAL REFERENCE: FBAA(161.8,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2274                            IA #: 2274
  FILE NUMBER: 162.1                    GLOBAL ROOT: FBAA(162.1
  DATE CREATED: FEB 02, 1998            CUSTODIAL PACKAGE: FEE BASIS
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA2274
  ID: FBAA(162.1
GLOBAL REFERENCE: FBAA(162.1,'AD'
 GLOBAL DESCRIPTION:   'AD' xref.  
GLOBAL REFERENCE: FBAA(162.1,D0,0)
FIELD NUMBER: 3                         FIELD NAME: VENDOR
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: FBAA(162.1,D0,'RX',D1,0)
FIELD NUMBER: 1                         FIELD NAME: DRUG NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1.6                       FIELD NAME: QUANTITY
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6.5                       FIELD NAME: AMOUNT PAID
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2275                            IA #: 2275
  FILE NUMBER: 162                      GLOBAL ROOT: FBAAC(
  DATE CREATED: FEB 02, 1998            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  NAME: DBIA2275                        ID: FBAAC(
GLOBAL REFERENCE: FBAAC('AB'
 GLOBAL DESCRIPTION:   'AB' xref.  
GLOBAL REFERENCE: FBAAC(D0,1,D1,1,D2,1,D3,0)
FIELD NUMBER: .01                       FIELD NAME: SERVICE PROVIDED
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: AMOUNT PAID
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2276                            IA #: 2276
  FILE NUMBER: 162.5                    GLOBAL ROOT: FBAAI(
  DATE CREATED: FEB 02, 1998            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  NAME: DBIA2276                        ID: FBAAI(
GLOBAL REFERENCE: FBAAI('D'
 GLOBAL DESCRIPTION:   'D' xref.  
GLOBAL REFERENCE: FBAAI(D0,0)
FIELD NUMBER: 2                         FIELD NAME: VENDOR
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: TREATMENT FROM DATE
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: TREATMENT TO DATE
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: AMOUNT PAID
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: FEE PROGRAM
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2277                            IA #: 2277
  FILE NUMBER: 161.2                    GLOBAL ROOT: FBAAV(
  DATE CREATED: FEB 02, 1998            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  NAME: DBIA2277                        ID: FBAAV(
GLOBAL REFERENCE: FBAAV(D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

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

NUMBER: 2281                            IA #: 2281
  FILE NUMBER: 399                      GLOBAL ROOT: DGCR(399
  DATE CREATED: FEB 02, 1998            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: DBIA2281                        ID: DGCR(399
GLOBAL REFERENCE: DGCR(399,'C'
 GLOBAL DESCRIPTION:   'C' xref.  
GLOBAL REFERENCE: DGCR(399,D0,'U')
FIELD NUMBER: 151                       FIELD NAME: STATEMENT COVERS FROM
  LOCATION: U;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 152                       FIELD NAME: STATEMENT COVERS TO
  LOCATION: U;2                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2282                            IA #: 2282
  FILE NUMBER: 357.69                   GLOBAL ROOT: IBE(357.69
  DATE CREATED: FEB 02, 1998
  CUSTODIAL PACKAGE: AUTOMATED INFO COLLECTION SYS
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA2282
  ID: IBE(357.69
GLOBAL REFERENCE: IBE(357.69,'B'
 GLOBAL DESCRIPTION:   'B' xref.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

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
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
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
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
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
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: 2288                            IA #: 2288
  DATE CREATED: FEB 03, 1998            CUSTODIAL PACKAGE: LEXICON UTILITY
  CUSTODIAL ISC: Salt Lake City         USAGE: Supported
  TYPE: Routine                         ROUTINE: LEXU
  NAME: LEXU                            ID: LEXU
 GENERAL DESCRIPTION:   LEXU is a utility routine for the Lexicon Utility which
 contains functions useful in retrieving classification codes for a term.  This
 agreement is an amendment to DBA #1573.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$CPCONE(IEN)
 COMPONENT DESCRIPTION:   Returns either a single 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).  

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
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
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
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
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
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
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
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
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL

NUMBER: 2297                            IA #: 2297
  FILE NUMBER: 405                      GLOBAL ROOT: DGPM(
  DATE CREATED: FEB 07, 1998            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: DBIA2297                        ID: DGPM(
GLOBAL REFERENCE: DGPM('C'
 GLOBAL DESCRIPTION:   'C' xref.  
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: .04                       FIELD NAME: TYPE OF MOVEMENT
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: FACILITY TREATING SPECIALTY
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2298                            IA #: 2298
  DATE CREATED: MAR 05, 1998            CUSTODIAL PACKAGE: 1
  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
SUBSCRIBING PACKAGE: HEALTH LEVEL SEVEN
  ISC: Oakland

NUMBER: 2299                            IA #: 2299
  FILE NUMBER: 42.4                     GLOBAL ROOT: DIC(42.4
  DATE CREATED: FEB 07, 1998            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: DBIA2299                        ID: DIC(42.4
GLOBAL REFERENCE: DIC(42.4,D0,0)
FIELD NUMBER: 3                         FIELD NAME: SERVICE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

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
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2301                            IA #: 2301
  FILE NUMBER: 70                       GLOBAL ROOT: RADPT(
  DATE CREATED: FEB 07, 1998
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  NAME: DBIA2301                        ID: RADPT(
GLOBAL REFERENCE: RADPT(D0,DT,B,
 GLOBAL DESCRIPTION:   'B' xref. of REGISTERED EXAMS multiple.  
GLOBAL REFERENCE: RADPT(D0,DT,D1,P,D2,0)
FIELD NUMBER: 2                         FIELD NAME: PROCEDURE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: EXAM STATUS
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: WARD
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: PRINCIPAL CLINIC
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2302                            IA #: 2302
  FILE NUMBER: 71                       GLOBAL ROOT: RAMIS(71,
  DATE CREATED: FEB 07, 1998
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  NAME: DBIA2302                        ID: RAMIS(71,
GLOBAL REFERENCE: RAMIS(71,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2303                            IA #: 2303
  FILE NUMBER: 660                      GLOBAL ROOT: RMPR(660
  DATE CREATED: FEB 07, 1998            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  NAME: DBIA2303                        ID: RMPR(660
GLOBAL REFERENCE: RMPR(660,C,
 GLOBAL DESCRIPTION:   'C' xref.  
GLOBAL REFERENCE: RMPR(660,D0,0)
FIELD NUMBER: 2                         FIELD NAME: TYPE OF TRANSACTION
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: ITEM
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: QTY
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: DELIVERY DATE
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: TOTAL COST
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2304                            IA #: 2304
  FILE NUMBER: 661                      GLOBAL ROOT: RMPR(661
  DATE CREATED: FEB 07, 1998            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  NAME: DBIA2304                        ID: RMPR(661
GLOBAL REFERENCE: RMPR(661,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2305                            IA #: 2305
  FILE NUMBER: 667                      GLOBAL ROOT: RMPR(667
  DATE CREATED: FEB 07, 1998            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  NAME: DBIA2305                        ID: RMPR(667
GLOBAL REFERENCE: RMPR(667,C,
 GLOBAL DESCRIPTION:   'C' xref.  
GLOBAL REFERENCE: RMPR(667,D0,0)
FIELD NUMBER: .01                       FIELD NAME: VEHICLE ID#
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2306                            IA #: 2306
  FILE NUMBER: 667.1                    GLOBAL ROOT: RMPR(667.1
  DATE CREATED: FEB 07, 1998            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  NAME: DBIA2306                        ID: RMPR(667.1
GLOBAL REFERENCE: RMPR(667.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2307                            IA #: 2307
  FILE NUMBER: 667.3                    GLOBAL ROOT: RMPR(667.3
  DATE CREATED: FEB 07, 1998            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  NAME: DBIA2307                        ID: RMPR(667.3
GLOBAL REFERENCE: RMPR(667.3,C
 GLOBAL DESCRIPTION:   'C' xref.  
GLOBAL REFERENCE: RMPR(667.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE PROCESSED
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ITEM
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: COST
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2.5                       FIELD NAME: QTY
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2308                            IA #: 2308
  FILE NUMBER: 9000011                  GLOBAL ROOT: AUPNPROB(
  DATE CREATED: FEB 07, 1998            CUSTODIAL PACKAGE: PROBLEM LIST
  USAGE: Controlled Subscription        TYPE: File
  NAME: DBIA2308                        ID: AUPNPROB(
GLOBAL REFERENCE: AUPNPROB("AC",
 GLOBAL DESCRIPTION:   'AC' xref.  
GLOBAL REFERENCE: AUPNPROB(D0,
 GLOBAL DESCRIPTION:   Fileman captioned output of entire PROBLEM record.  
GLOBAL REFERENCE: AUPNPROB("MODIFIED",
 GLOBAL DESCRIPTION:   direct global read of the MODIFIED x-ref is allowed.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES

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
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
SUBSCRIBING PACKAGE: WOMEN'S HEALTH

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
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
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
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(
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
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
 SUBSCRIBING DETAILS:   BCMA added 12/12/08 /jsh 
  DATE ACTIVATED: AUG 28, 2009

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
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
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
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  

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
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
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
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
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.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 1/20/23, effective with DSSV*1.2 DSS Class 2 
 Product Document only. C3 is requesting access to the following fields/indexes
 from  file 8925.1: .01  NAME .04  TYPE 

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
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
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 4/11/25 effective with PSO*7*770 patch to check
 whether a user can perform an action on a specific TIU document.  
SUBSCRIBING PACKAGE: HEALTH DATA REPOSITORY
 SUBSCRIBING DETAILS:   Added 7/13/26 effective with HDS*1*100 patch to call
 TIU API $$CANDO^TIULP to determine the TIU note sensitivity, passing the TIU
 Note IEN with "VIEW" action for a given HDR VistA Proxy user.  This was 
 required because HDR Generic Observation Service (IRIS class 
 VISTA.HDSREPGSP.cls) invokes the VPR GET PATIENT DATA RPC to retrieve TIU 
 documents, which does not determine whether a TIU note is restricted by 
 TIU/ASU security. This functionality resides in an IRIS SQL procedure stored
 in HDR IRIS database (HDRHX VistA namespace) on VistA system.  

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
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.  
COMPONENT/ENTRY POINT: CLINDOC
 COMPONENT DESCRIPTION:   Returns the Clinical Document subclass for a given
 document type.  
VARIABLES: TIUTYP                       TYPE: Input
 VARIABLES DESCRIPTION:   Document Type 
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN for the record in the TIU DOCUMENT FILE (#8925).  
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
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 7/21/26. Effective with patch CDSP*1*4, to call
 PNAME^TIULC1 and add Component CLINDOC.  

NUMBER: 2324                            IA #: 2324
  DATE CREATED: FEB 10, 1998
  CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: USRLM
  NAME: DBIA2324                        ID: USRLM
 GENERAL DESCRIPTION:   When checking if a user should have access to a
 particular document TIU needs to determine if a user is a member of a class
 that can access the document. Therefore TIU requests permission to call the
 function ISA^USRLM.  
  
 Health Summary needs to extract user class data to build a class selection 
 list for Health Summary Parameters referenced by the Parameters tools in the 
 Parameter file.  Therefore GMTS request permission to call the function 
 WHATIS^USRLM.  
  
 Health Summary needs to retrieve the name (.01) of a user class referenced by
 the Parameters file.  The call to CLNAME^USRLM will return the Class display
 name (.04).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$ISA(USER,CLASS,ERR)
 COMPONENT DESCRIPTION:   This is a Boolean function that returns true is USER
 is a member of CLASS, false otherwise.  
VARIABLES: USER                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file 200,NEW PERSON file.  
VARIABLES: CLASS                        TYPE: Output
VARIABLES: ERR                          TYPE: Output
 VARIABLES DESCRIPTION:   If there was an error then this variable contains the
 error message.  
VARIABLES: CLASSS                       TYPE: Input
 VARIABLES DESCRIPTION:   The function determines if the user is a member of
 this class. Pointer to file 8930, USR CLASS.  
COMPONENT/ENTRY POINT: $$WHATIS(USER,CLASS,NAME01)
 COMPONENT DESCRIPTION:   This component when passed a users's DUZ and the name
 of an output array  will return all the USR classes a user has subscribed to.  
VARIABLES: USER                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file 200, NEW PERSON file.  
VARIABLES: CLASS                        TYPE: Output
 VARIABLES DESCRIPTION:   Contains the name of the output array.  
VARIABLES: NAME01                       TYPE: Input
 VARIABLES DESCRIPTION:   NAME01 is optional and controls what is returned in
 the variable CLASS. If NAME01>0 return NAME (field .01) otherwise, return
 DISPLAY NAME (field .04).  
  
  
COMPONENT/ENTRY POINT: $$CLNAME(CLASS,NAME01)
 COMPONENT DESCRIPTION:   This entry point when passed a class IEN will return
 either the USR class NAME (field .01) or the DISPLAY NAME (field .04).  
  
VARIABLES: CLASS                        TYPE: Input
VARIABLES: NAME01                       TYPE: Input
 VARIABLES DESCRIPTION:   NAME01 is optional and controls what is returned by
 $$CLNAME. If NAME01>0 return NAME (field .01) otherwise, return DISPLAY NAME 
 (field .04). 
  
COMPONENT/ENTRY POINT: $$SUBCLASS(CLASS1,CLASS2)
 COMPONENT DESCRIPTION:   Return 1 if CLASS1 is a subclass of CLASS2, otherwise
 return 0.  
  
VARIABLES: CLASS1                       TYPE: Input
 VARIABLES DESCRIPTION:   NAME or internal entry number of a user class.  
  
VARIABLES: CLASS2                       TYPE: Input
 VARIABLES DESCRIPTION:   NAME or internal entry number of a user class.  
  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: SURGERY
SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   added 10/21/2009 
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP is using WHATIS entry point for HMP v.2.0.  
  
 HMP's subscription to this ICR expires on 10/27/17 with the shut down of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 9/10/26 effective with patch YS*5.01*268 The MHA
 application will call $$WHATIS to gather the user's attributes including USER
 CLASS in order to control workflows and access to different functions.  

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
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
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
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
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
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
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
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
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
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
  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
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
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 

NUMBER: 2340                            IA #: 2340
  DATE CREATED: MAR 05, 1998            CUSTODIAL PACKAGE: 1
  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
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 

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
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
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
 GENERAL DESCRIPTION:   The routine XUSER has supported entry points to lookup
 a user, check to determine if a user is active, DEA# details, DETOX#,
 authorized to write Controlled Substances, etc. 
  
  
 Amended - Added 1/30/2023 The API's are designed to be backward compatible, so
 that calls to APIs that formerly returned DEA information stored in the DEA#
 field (#53.2), DEA EXPIRATION DATE field (#747.44), and the SCHEDULE fields
 (#55.1-55.6) will now receive the same information from new fields in the DEA
 NUMBERS file (#8991.9). Pharmacy code changes that use the new APIs and new
 input parameters are in the Pharmacy Operational Updates Release 3 patches 
 PSO*7*545, PSJ*5*372, and OR*3*499.  
  STATUS: Active
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.  If the
 parameter is set to "A" then don't select current users who have a termination
 date prior to today's date 
  
 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 
VARIABLES: Input
VARIABLES: XUF                          TYPE: Input
 VARIABLES DESCRIPTION:   Parameter "Q" or "A" passed in.  
COMPONENT/ENTRY POINT: $$ACTIVE
 COMPONENT DESCRIPTION:   This API returns the active status indicator and
 latest signon information of a user in the NEW PERSON (#200) file.  
  
 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(XUDA,XUF) Parameter: IEN=pointer to the NEW PERSON
 file.  
            XUF=flag to control processing 
                0 or not passed, do not include Visitors 
                1 include Visitors 
              
 It returns the following codes: 
     ""  No user record.  
     "0^TERMINATED^2980310"  User terminated on date.  
     "1" Has a record and no termination date.  
VARIABLES: XUDA                         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.  
VARIABLES: XUF                          TYPE: Input
 VARIABLES DESCRIPTION:   Flag to control processing.  
  
       0 or not passed, do not include Visitors 
       1 include Visitors 
COMPONENT/ENTRY POINT: $$DEA
 COMPONENT DESCRIPTION:   The initial patch XU*8*580 provides this API and adds
 a new field, FACILITY DEA NUMBER (#52), to the INSTITUTION file (#4). 
  
       Usage:   S X=$$DEA^XUSER(FLAG,IEN,DATE,DEA) 
  
 When the FLAG input parameter is set to one (1), and the IEN input parameter
 represents a VA prescriber, and the DEA parameter is not populated, and the
 user's DEA number is expired, the value of the VA# (#53.3) field in the NEW
 PERSON (#200) file is returned. Non-VA prescribers cannot use VA#; therefore,
 the FLAG input parameter is ignored for non-VA prescribers.  
  
 A VA prescriber is a user whose NON-VA PRESCRIBER (#53.91) field in the NEW
 PERSON (#200) file is not set to YES, and whose PROVIDER TYPE (#53.6) field in
 the NEW PERSON file is not set to "FEE BASIS" or "C & A". A non-VA prescriber
 is a user whose NON-VA PRESCRIBER (#53.91) field in the NEW PERSON (#200) file
 is set to YES, or whose PROVIDER TYPE (#53.6) field in the NEW PERSON file is
 set to "FEE BASIS" or "C & A".  
  
 With patch XU*8*689, if the DEA input parameter is NULL, this API returns a
 user's 'default' Inpatient DEA number, if it exists. This is the DEA number in
 the user's NEW DEA #'S multiple field (#53.21) in the NEW PERSON (#200) file,
 that points to an entry in the DEA NUMBERS file (#8991.9) for which the USE
 FOR INPATIENT ORDERS? Field (#.06) is set to YES. A provider may have more
 than one DEA number, but only one of their DEA numbers may be flagged as USE
 FOR INPATIENT ORDERS.  
  
 When the DATE input parameter is passed in: 
   1) The DEA number is returned if it is (or was) valid on the 
      date represented by the DATE input parameter.  
   2) NULL is returned if the DEA number is (or was) not valid 
      on the date represented by the DATE input parameter.  When the DATE input
 parameter is not passed in: 
   1) The DEA number is returned if it is valid on the current 
      date.  
   2) NULL is returned if it is not valid on the current date.  
  
 If the DEA number is expired, the user's VA# (#53.3) field is populated, the
 user meets the definition of a VA prescriber, and the PSOEPCS EXPIRED DEA
 FAILOVER parameter is not set to NO, the return value will consist of the
 facility DEA number with the user's VA# as a suffix, separated by a dash "-".
 For example, if the user's DEA number is AB1234567, and their VA# is
 AX1234567, the return value would be "AB123467-AX123467".  
  
 The definition of a VA prescriber is a user whose NON-VA PRESCRIBER (#53.91)
 field in the NEW PERSON (#200) file is not set to YES, and whose PROVIDER TYPE
 (#53.6) field in the NEW PERSON file is not set to "FEE BASIS" or "C & A".  
VARIABLES: $$DEA                        TYPE: Output
 VARIABLES DESCRIPTION:   Example 1: 
 ---------
 The NEW DEA#'s (#53.21) multiple field pointing to active DEA number 
 "AB1234567" in the DEA NUMBERS file (#8991.9) entry having the USE FOR 
 INPATIENT ORDERS? field (#.06) set to YES.  
  
 The IEN points to a VA prescriber.  
  
 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: 
 ---------
 The NEW DEA#'s (#53.21) multiple field doesn't contain any DEA numbers.  
           
 The IEN input parameter points to a VA prescriber.  
  
 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: 
  ---------
 The NEW DEA#'s (#53.21) multiple field doesn't contain any DEA numbers.  
 FACILITY DEA NUMBER field (#52) is "VA7654321" 
  
 The IEN input parameter points to a VA prescriber.  
  
 The VA# field (#53.3) is null.  
  
 If the FLAG input parameter is null or "0", this API would return "" (NULL).  
  
 If the FLAG input parameter is "1", this API would return "" (NULL).  
  
                             
 Example 4: 
 ---------
 The NEW DEA#'s (#53.21) multiple field doesn't contain any DEA numbers.  
  
 The IEN input parameter points to a VA prescriber.  
  
 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 "" (NULL).  
  
 If the FLAG input parameter is "1", this API would return "" (NULL).  
  
                             
 Example 5: 
 ----------
 The NEW DEA#'s (#53.21) multiple field points to expired DEA "AB1234567" in
 the DEA NUMBERS file (#8991.9) having the USE FOR INPATIENT ORDERS? field
 (#.06) set to YES.  
  
 The IEN input parameter points to a VA prescriber.  
  
 FACILITY DEA NUMBER field (#52) is "VA7654321".  
                     
 VA# field (#53.3) is "789". 
  
 If the XPAR parameter 'PSOEPCS EXPIRED DEA FAILOVER' is set to 'Yes', the API
 would return "VA7654321-789".  
  
 If the XPAR parameter 'PSOEPCS EXPIRED DEA FAILOVER' is set to 'No', the API
 would return null ("").  
           
                   
 Example 6: 
 ---------
 The NEW DEA#'s (#53.21) multiple field pointing to a record in the DEA NUMBERS
 file (#8991.9) having the USE FOR INPATIENT ORDERS? field (#.06) set to YES is
 "AB1234567".  
  
 The IEN input parameter points to a VA prescriber.  
                 
 The EXPIRATION DATE field (#.04) in the DEA NUMBERS is in the past, for 
 example, 3201106, representing November 6, 2020. 
  
 FACILITY DEA NUMBER (#52) field in the INSTITUTION (#4) file is "VA7654321".  
  
 The user pointed to by the IEN parameter has a VA# field (#53.3) equal to 
 "789".  
  
 If the DATE parameter passed in is less than the EXPIRATION DATE of the DEA
 number, (e.g., "3201104", representing November 4, 2020), this API returns
 "AB1234567".  
          
 If the DATE parameter "3201106" passed in is equal to or greater than DEA 
 EXPIRATION DATE, this API returns "AB1234567-789" if the FLAG input parameter
 is not passed in.  
  
 If the DATE parameter "3201106" passed in is equal to or greater than DEA 
 EXPIRATION DATE, this API returns "AB1234567-789" if the FLAG input parameter
 is passed in.  
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 VA
 prescriber does not have a valid DEA number. A user with no valid DEA number
 may have no DEA number or an expired DEA number.  
  
  
 * FLAG is null or "0" - This routine will check to see if a VA prescriber has
 a value in the VA# (#53.3) field of the NEW PERSON (#200) file and the 
 FACILITY DEA NUMBER (#52) field of the INSTITUTION (#4) file. 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 a VA prescriber has a value
 in the VA# (#53.3) field of the NEW PERSON (#200) file. If a value is found in
 that field, this routine will return that value. Otherwise, this routine
 returns an empty string.  
VARIABLES: DATE (optional)              TYPE: Input
 VARIABLES DESCRIPTION:   This parameter to enter in VA FileMan format.  The
 date to be checked against the DEA# Expiration Date instead of default DT
 (today's date).  
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: 
  
  - If the Prescriber has a valid Individual DEA number, the 
    the DEA number's SCHEDULE fields (#2.1-#2.6) in the DEA 
    NUMBERS file (#8991.9) determine the explicit set of DEA 
    prescribing permissions.  
  
  - If the Prescriber has a no valid Individual DEA numbers, 
    but has a valid Institutional DEA number, the SCHEDULE 
    fields (#55.1-#55.6) in the Prescriber's NEW PERSON file 
    (#200) entry determine the explicit set of DEA prescribing 
    permissions.  
  
  - If the Prescriber has an expired Individual DEA number, no 
    valid Institutional DEA numbers, the Prescriber's NON-VA 
    PRESCRIBER field (#53.91) in the NEW PERSON file (#200) is 
    not set to YES, the PROVIDER TYPE field (#53.6) in the NEW 
    PERSON file (#200) is not set to "FEE BASIS" or "C & A", 
    the Prescriber has a VA#, and the PSOEPCS EXPIRED DEA 
    FAILOVER parameter is not set to NO, the SCHEDULE fields 
    (#55.1-#55.6) in the Prescriber's NEW PERSON file (#200) 
    entry determine the explicit set of DEA prescribing 
    permissions.  
  
  - If the Prescriber has an expired Individual DEA number, no 
    valid Institutional DEA numbers, and the PSOEPCS EXPIRED 
    DEA FAILOVER parameter is set to NO or the Prescriber's 
    NON-VA PRESCRIBER field is set to YES, or the Prescriber's 
    PROVIDER TYPE field is set to "C & A" or "FEE BASIS", then 
    the VA# is ignored and the Prescriber is not permitted to 
    prescribe any scheduled medications.  
  
  - If the Prescriber has no DEA numbers in the NEW DEA#'s 
    multiple field (#53.21) in the NEW PERSON file (#200), 
    their NON-VA PRESCRIBER field (#53.91) in the NEW PERSON 
    file (#200) is not set to YES, the PROVIDER TYPE field 
    (#53.6) is not set to "FEE BASIS" or "C & A", and the 
    Prescriber has a VA#, the SCHEDULE fields (#55.1-#55.6)  
    in the Prescriber's NEW PERSON file (#200) entry determine 
    the explicit set of DEA prescribing permissions.  
  
  - If the Prescriber has no DEA numbers in the NEW DEA#'s 
    multiple field (#53.21) in the NEW PERSON file (#200), and 
    their NON-VA PRESCRIBER field (#53.91) in the NEW PERSON 
    file (#200) is set to YES or their PROVIDER TYPE field 
    (#53.6) is set to "FEE BASIS" or "C & A", then the PSOEPCS 
    EXPIRED DEA FAILOVER parameter is ignored, the VA# is 
    ignored, and the Prescriber is not permitted to prescribe 
    any scheduled medications.  
  
    (Note: All of these checks do not apply to documentation of 
    non-VA medication.) 
  
    Usage:  S X=$$SDEA^XUSER(FG,IEN,PSDEA,DATE) 
VARIABLES: FG (optional)                TYPE: Input
 VARIABLES DESCRIPTION:   Not used, retained for backward compatibility.  
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 - No valid DEA number found.  
  
 2 - DEA number not authorized for schedule PSDEA.  
  
 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.  
VARIABLES: DATE (optional)              TYPE: Input
 VARIABLES DESCRIPTION:   Date in VA FileMan format. The date to be checked
 against the DEA# Expiration Date instead of default DT (today's date).  
VARIABLES: IDEA (optional)              TYPE: Input
 VARIABLES DESCRIPTION:   This parameter is a DEA number or "I". If a DEA
 number is passed in, the DEA number's permissions are checked. If an "I" is
 passed in, only the permissions for the user's DEA number that has the USE FOR
 INPATIENT ORDERS? (#.06) field in the DEA NUMBERS (#8991.9) file is checked.  
COMPONENT/ENTRY POINT: $$DETOX
 COMPONENT DESCRIPTION:   This API obtains the value stored in the DETOX NUMBER
 (#.03) field in the DEA NUMBERS (#8991.9) file.  
  
 Usage:  S X=$$DETOX^XUSER(IEN,DATE) 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of user in NEW PERSON file (#200).  
VARIABLES: $$DETOX                      TYPE: Output
 VARIABLES DESCRIPTION:   Returns: one of the following: 
  
 - User's DETOX number from the DETOX NUMBER (#.03) field in the DEA 
   NUMBERS (#8991.9) file.  
  
 - NULL - DETOX NUMBER from the DETOX NUMBER (#.03) field in the DEA 
   NUMBERS (#8991.9) file is NULL.  
VARIABLES: DATE(optional)               TYPE: Input
 VARIABLES DESCRIPTION:   This parameter to enter in VA FileMan format.  The
 date to be checked against the DEA# Expiration Date instead of default DT
 (today's date).  
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.  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.")="" 
COMPONENT/ENTRY POINT: $$PRDEA
 COMPONENT DESCRIPTION:   The DEA electronic Prescribing of Controlled
 Substances (ePCS) module requires an API to determine a provider's Default DEA
 number, indicated by the DEA number in NEW DEA#'s multiple field (#53.21) in
 the Prescriber's NEW PERSON file (#200) entry pointing to a DEA number in the
 DEA NUMBERS file (#8991.9) for which the USER FOR INPATIENT ORDERS? field
 (#.06) is set to YES.  
  
 Usage:  S X=$$PRDEA^XUSER(IEN) 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN of the user in the NEW PERSON File
 (#200).  
VARIABLES: $$PRDEA                      TYPE: Output
 VARIABLES DESCRIPTION:   Returns:  The provider's default DEA number,
 indicated by the DEA number in NEW DEA#'s multiple field (#53.21) in the
 prescriber's NEW PERSON file (#200) entry pointing to a DEA number in the DEA
 NUMBERS File (#8991.9) for which the USER FOR INPATIENT ORDERS? field (#.06)
 is set to YES.  
COMPONENT/ENTRY POINT: $$PRXDT
 COMPONENT DESCRIPTION:   The expiration date of a provider's DEA number is
 required for reporting purposes, to facilitate searches for recently expired
 and soon to expire DEA number.                 
  
 Usage:  S X=$$PRXDT^XUSER(IEN) 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN of the user in the NEW PERSON file
 (#200).  
VARIABLES: $$PRXDT                      TYPE: Output
 VARIABLES DESCRIPTION:   Returns: The Prescriber's DEA expiration date from
 the EXPIRATION DATE field (#.04) in the DEA NUMBERS file (#8991.8) for which
 the USE FOR INPATIENT ORDERS field is set to YES.  
  
 Usage:  S X=$$PRXDT^XUSER(IEN) 
COMPONENT/ENTRY POINT: $$PRSCH
 COMPONENT DESCRIPTION:   The Prescriber's DEA permissions from their default
 DEA number. The permissions are retrieved from the SCHEDULE fields (#2.1-#2.6)
 in the DEA NUMBERS file (#8991.8), pointed to by the NEW DEA#'s multiple field
 in the NEW PERSON file. The Prescriber's default DEA number is determined by
 the USE FOR INPATIENT ORDERS? field (#.06) in the DEA NUMBERS file (#8991.9) 
 being set to YES. 
  
 Usage: S X=$$PRSCH^XUSER 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN of the user in the NEW PERSON file
 (#200).  
VARIABLES: $$PRSCH                      TYPE: Output
 VARIABLES DESCRIPTION:   Returns: The Prescriber's DEA permissions from their
 default DEA number.  The permissions are retrieved from the SCHEDULE fields
 (#2.1-#2.6) in the DEA NUMBERS file (#8991.8), pointed to by the NEW DEA#'s
 multiple field in the NEW PERSON file. 
  
 The Prescriber's default DEA number is determined by the USE FOR INPATIENT 
 ORDERS? field (#.06) in the DEA NUMBERS file (#8991.9) being set to YES.  The
 DEA permissions are returned in internal format with delimiters. For example,
 1^1^1^1^1^1 indicates permissions for all schedules, and 0^0^0^0^0^0 indicates
 no permissions. The mapping of the delimited string to the SCHEDULE fields in
 the DEA NUMBERS file (#8991.9) is as follows: 
  
    Piece   Field #   Field Name 
    1       2.1       SCHEDULE II NARCOTIC 
    2       2.2       SCHEDULE II NON-NARCOTIC 
    3       2.3       SCHEDULE III NARCOTIC 
    4       2.4       SCHEDULE III NON-NARCOTIC 
    5       2.5       SCHEDULE IV 
    6       2.6       SCHEDULE V 
  DATE ACTIVATED: FEB 08, 2023

NUMBER: 2344                            IA #: 2344
  DATE CREATED: MAR 11, 1998            CUSTODIAL PACKAGE: CMOP
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSXEDUTL
  NAME: DBIA2344                        ID: PSXEDUTL
 GENERAL DESCRIPTION:   The Outpatient Pharmacy package (V 6.0) requests an
 integration agreement to call the Consolidated Mail Outpatient Pharmacy (CMOP)
 package routine PSXEDUTL.  This routine was designed for the exclusive use of
 Outpatient Pharmacy Edit and Release functions. The IEN of an Rx# is passed to
 the CMOP routine and evaluated against CMOP criteria for the associated 
 Outpatient Pharmacy action. The functionality contained in this routine has
 been integrated into V 7.0 of Outpatient Pharmacy.  
  STATUS: Withdrawn
COMPONENT/ENTRY POINT: OREL
VARIABLES: RXP                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN Prescription file (#52) 
VARIABLES: ISUF                         TYPE: Output
 VARIABLES DESCRIPTION:   Returned as 1 or "".  
COMPONENT/ENTRY POINT: RREL
VARIABLES: RXP                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN Prescription file (#52).  
VARIABLES: ISUF                         TYPE: Output
 VARIABLES DESCRIPTION:   Returned as 1 or "".  
COMPONENT/ENTRY POINT: SUS
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN Prescription file (#52).  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

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
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
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 
 --------------------------------------------------------------------------
 ANRVPATIENT,ONE                 000-00-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
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
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 encounter 
   VISIT    (optional) pointer to VISIT file (#9000010) for the encounter 
               if know 
  
 Output Parameters: 
   RETURN   this is an array subscripted by "SC","CV","AO","IR","EC", 
              "SHAD","MST", "HNC", and "CLV" that contains two pieces 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("CV") = "0^" 
     RETURN("MST") = "0^" 
     RETURN("HNC") = "0^" 
     RETURN("SHAD") = "0^" 
     RETURN("CLV") = "1^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
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

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
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 

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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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

NUMBER: 2352                            IA #: 2352
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG
  DATE CREATED: OCT 15, 1999
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: READ/WRITE DRUG FILE (#50)
  ID: PSDRUG
GLOBAL REFERENCE: PSDRUG(D0,
FIELD NUMBER: 2                         FIELD NAME: VA CLASSIFICATION
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2.1                       FIELD NAME: PHARMACY ORDERABLE ITEM
  LOCATION: 1;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 213                       FIELD NAME: CMOP DISPENSE
  LOCATION: 3;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 20                        FIELD NAME: NATIONAL DRUG FILE ENTRY
  LOCATION: ND;1                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 21                        FIELD NAME: VA PRODUCT NAME
  LOCATION: ND;2                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 22                        FIELD NAME: PSNDF VA PRODUCT NAME ENTRY
  LOCATION: ND;3                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 23                        FIELD NAME: PACKAGE SIZE
  LOCATION: ND;4                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 24                        FIELD NAME: PACKAGE TYPE
  LOCATION: ND;5                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 25                        FIELD NAME: NATIONAL DRUG CLASS
  LOCATION: ND;6                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 27                        FIELD NAME: CMOP ID
  LOCATION: ND;10                       ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   
  
  
 National Drug File is given permission by Pharmacy Data Management to make the
 following references with direct global reads and writes to the fields and
 direct global references to the fields' cross-references.  
  
 1. (#2) VA CLASSIFICATION          $P(^PSDRUG(D0,0),"^",2) 
  
  
 2. (#2.1) PHARMACY ORDERABLE ITEM  $P(^PSDRUG(D0,1),"^",2) 
  
  
 3. (#213) CMOP DISPENSE            $P(^PSDRUG(D0,3),"^",1) 
  
  
 4. (#51) LOCAL NON-FORMULARY  $P(^PSDRUG(D0,0),"^",9) 
  
  
 5. (#52) VISN NON-FORMULARY  $P(^PSDRUG(D0,0),"^",11) 
  
  
 6. (#37) DRUG TEXT ENTRY (multiple)  $P(^PSDRUG(D0,9,D1,0),"^") 
  
  
 7.  All fields contained on the "ND" Node 
  
 ^PSDRUG(D0,"ND")= (#20) NATIONAL DRUG FILE ENTRY [1P] ^ (#21) VA PRODUCT 
             ==>NAME [2F] ^ (#22) PSNDF VA PRODUCT NAME ENTRY [3N] ^ (#23) 
             ==>PACKAGE SIZE [4P] ^ (#24) PACKAGE TYPE  (#25) NATIONAL DRUG 
             ==>CLASS [6P] ^  ^  ^  ^ (#27) CMOP ID [10F] ^ (#29) NATIONAL 
             ==>FORMULARY INDICATOR [11S] ^ 
  
 8. ^PSDRUG(D0,"OND")   This global node was eliminated by previous 
                        versions of the software. NDF V3.18 is the last 
                        version that will include the cleanup routine 
                        containing code to delete this node if it exists.  
  
  
 9.  Hard Coded sets and kills to the following cross references; 
  
     ^PSDRUG("AND") 
     ^PSDRUG("APC") 
     ^PSDRUG("AQ") 
     ^PSDRUG ("AQ1") 
     ^PSDRUG("NDC") 
     ^PSDRUG("VAC") 
     ^PSDRUG("VAPN") 
     ^PSDRUG("APN") 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
  ISC: Birmingham

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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

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
FIELD NUMBER: .03                       FIELD NAME: VISIT
  LOCATION: [0;3]                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1201                      FIELD NAME: EVENT DATE AND TIME
  LOCATION: [12;1]                      ACCESS: Direct Global 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.  
  
 Amendment: Added .03 and 1201 effective with OR*3*405 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
  DATE ACTIVATED: DEC 23, 2022

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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

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
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: 2359                            IA #: 2359
  DATE CREATED: APR 07, 1998            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Other                           NAME: DBIA2359
 GENERAL DESCRIPTION:   In order to provide internal workstation identification
 by way of the Kernal/Broker session, read access of the session variable
 IO("CLNMN") is required for the purpose of controlling remote processes.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 2361                            IA #: 2361
  DATE CREATED: APR 16, 1998            CUSTODIAL PACKAGE: 1
  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
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
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
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
SUBSCRIBING PACKAGE: ASISTS             ISC: Hines

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
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
 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: 2367                            IA #: 2367
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG
  DATE CREATED: APR 28, 1998
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2367
  ID: PSDRUG
GLOBAL REFERENCE: PSDRUG(D0,
FIELD NUMBER: 213                       FIELD NAME: CMOP DISPENSE
  LOCATION: 3;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 21                        FIELD NAME: VA PRODUCT NAME
  LOCATION: ND;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 27                        FIELD NAME: CMOP ID
  LOCATION: ND;10                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 20                        FIELD NAME: NATIONAL DRUG FILE ENTRY
  LOCATION: ND;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2.1                       FIELD NAME: PHARMACY ORDERALBE ITEM
  LOCATION: 1;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Consolidated Mail Outpatient Pharmacy is given
 permission  by Pharmacy Data Management to make the following references to
 ^PSDRUG.  
  
 1. (#213) CMOP DISPENSE         $P(^PSDRUG(D0,3),"^",1) 
  
 2. All fields contained on the "ND" node - Global Read Access only 
 ^PSDRUG(D0,"ND")= (#20) NATIONAL DRUG FILE ENTRY [1P] ^ (#21) VA PRODUCT 
             ==>NAME [2F] ^ (#22) PSNDF VA PRODUCT NAME ENTRY [3N] ^ (#23) 
             ==>PACKAGE SIZE [4P] ^ (#24) PACKAGE TYPE  (#25) NATIONAL DRUG 
             ==>CLASS [6P] ^  ^  ^  ^ (#27) CMOP ID [10F] ^ 
  
 3. Hard coded sets and kills to the following cross references: 
      ^PSDRUG("AQ") 
      ^PSDRUG("AQ1") 
  
 4. (#2.1) PHARMACY ORDERABLE ITEM   $P(^PSDRUG(D0,1),"^",2) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham

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         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: 2372                            IA #: 2372
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Other
  NAME: SC CLINIC ENROLL/DISCHARGE EVENT DRIVER protocol
 GENERAL DESCRIPTION:   The SC CLINIC ENROLL/DISCHARGE EVENT DRIVER protocol is
 provided to post information whenever a patient is enrolled in or discharged
 from a clinic.  
  
 It is exported with the SC TEAM AUTO-ADD protcol attached to it.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SC CLINIC ENROLL/DISCHARGE EVENT DRIVER
 COMPONENT DESCRIPTION:   This is the protocol which can be used to access
 clinic enrollment/discharge information.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Order Entry/Results Reporting v3.0 attached the ORU
 AUTOLIST CLINIC protocol  This protocol is used to update Order Entry teams
 lists that are based on clinic enrollment.  

NUMBER: 2373                            IA #: 2373
  FILE NUMBER: 1.2                      GLOBAL ROOT: DIST(1.2,
  DATE CREATED: APR 29, 1998            CUSTODIAL PACKAGE: 1
  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
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: 1
  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
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: 1                  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
SUBSCRIBING PACKAGE: TOOLKIT            ISC: Oakland

NUMBER: 2376                            IA #: 2376
  DATE CREATED: APR 30, 1998            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  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
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
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   Added 3/17/25 effective with the PSS*1*262 patch for
 the MOCHA 3.0 project to retrieve all active Inpatient medication orders to be
 used in suppression rules for the Pharmacogenomic (PGx) order checks.  

NUMBER: 2377                            IA #: 2377
  DATE CREATED: APR 30, 1998            CUSTODIAL PACKAGE: 1
  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
  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: 2378                            IA #: 2378
  DATE CREATED: MAY 06, 1998
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  CUSTODIAL ISC: Salt Lake City         USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMRAOR                       NAME: TEST FOR ADVERSE REACTION TO AGENT
  ID: GMRAOR
 GENERAL DESCRIPTION:   This integration agreement allows a package to
 determine if a patient has an adverse reaction to an agent defined by the
 parameters TYP and PTR.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORDER CHECK
KEYWORDS: ALLERGY ORDER CHECK
COMPONENT/ENTRY POINT: $$ORCHK(DFN,TYP,PTR,LOC)
 COMPONENT DESCRIPTION:   This call checks if the patient has an adverse
 reaction to an agent defined by the parameters TYP and PTR.  
  
 **NOTE: Patch GMRA*4*46 was released on 05/24/2016 with a compliance date of
 06/24/2016. This patch included the new $$ORCHK2 component, which is intended
 to replace this component. New subscribers should use the $$ORCHK2 component.
 A future patch will phase out the use of this component as subscribing
 applications move to the $$ORCHK2 component.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's internal entry number (IEN) in the PATIENT
 file (#2).  
VARIABLES: TYP                          TYPE: Input
 VARIABLES DESCRIPTION:   The type of agent to check. Possible values are: 
  "CM" - Contrast Media Reaction 
  "DR" - Drug Reaction 
  "IN" - Drug Ingredient 
  "CL" - Drug Class 
VARIABLES: PTR                          TYPE: Input
 VARIABLES DESCRIPTION:   The agent to check for. Possible values are: 
  If TYP="CM", PTR is ignored.  
  If TYP="DR", PTR is formatted as PSNDA.PSNVPN, 
               where PSNDA is the IEN to the 
               VA GENERIC file (#50.6) and PSNVPN 
               is the IEN to the VA PRODUCT file 
               (#50.68).  
  If TYP="IN", PTR is the IEN to the DRUG 
               INGREDIENTS file (#50.416).  
  If TYP="CL", PTR is the IEN to the VA DRUG CLASS 
               file (#50.605).  
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   An optional location type flag.  
  
 If TYP="CM" and LOC is defined and greater than 0, the type of site that 
 documented the reaction ("LOCAL", "REMOTE SITE(S)", or "LOCAL AND REMOTE 
 SITE(S)") will be returned in the second caret piece of $$ORCHK.  
  
 If TYP="DR", TYP="IN", or TYP="CL", LOC is ignored.  
VARIABLES: $$ORCHK                      TYPE: Output
 VARIABLES DESCRIPTION:   For all values of TYP, $$ORCHK will be defined as
 either an empty string if the parameters are incorrect or 0 if the patient has
 no reactions to the agent defined by the TYP and PTR parameters.  
  
 The following additional values are returned depending on the value of TYP: 
  
 If TYP="CM", $$ORCHK will be defined as either an empty string if the patient
 is not in the Adverse Reaction Tracking database or 1 if the patient has a
 reaction to contrast media. Additionally, if LOC is greater than zero, the
 second caret piece will contain the type of site that documented the reaction
 ("LOCAL", "REMOTE SITE(S)", or "LOCAL AND REMOTE SITE(S)").  
  
 If TYP="IN" or TYP="CL", $$ORCHK will be defined as 1 if the patient has a
 reaction to the agent defined by the PTR parameter.  
  
 If TYP="DR" and the patient has a reaction to the agent defined in the PTR
 parameter, $$ORCHK will be defined as either 1 or 2. If the patient has a
 reaction to one of the ingredients in the agent defined by the PTR parameter,
 it will be 1. If the patient has a reaction to one of the drug classes to
 which the agent defined by the PTR parameter belongs, it will be 2.  
VARIABLES: GMRAING                      TYPE: Output
 VARIABLES DESCRIPTION:   The calling application should either NEW this
 variable before calling this component or KILL this variable after it is no
 longer needed.  If TYP="DR", this array will contain the drug ingredients in
 the agent defined by the PTR parameter to which the patient has a reaction to. 
 
   Format: 
   GMRAING(NUM)="ING (SD)" 
   NUM - has a value of 1 for the first 
         ingredient and increments by one 
         for subsequent ingredients.  
   ING - the name of the ingredient.  
    SD - the type of site that documented the 
         reaction. Possible values are "LOCAL" if 
         only the current site documented the 
         reaction, "REMOTE SITE(S)" if only a 
         remote site documented the reaction, or 
         "LOCAL AND REMOTE SITE(S)" if both the 
         current and remote sites documented the 
         reaction.  
  
 If TYP="CM", TYP="IN", or TYP="CL", this array will be undefined.  
VARIABLES: GMRADRCL                     TYPE: Output
 VARIABLES DESCRIPTION:   The calling application should either NEW this
 variable before calling this component or KILL this variable after it is no
 longer needed.  If TYP="DR" and the patient does not have a reaction to any of
 the drug ingredients in the agent defined by the PTR parameter (GMRAING is 
 undefined), this array will be defined. It will contain the drug classes of
 the agent defined by the PTR parameter to which the patient has a reaction to. 
 
   Format: 
   GMRADRCL(NUM)="DCC^DCN (SD)" 
   NUM - has a value of 1 for the first 
         drug class and increments by one 
         for subsequent drug classes.  
   DCC - five character code assigned to the 
         drug class.  
   DCN - the name of the drug class.  
    SD - the type of site that documented the 
         reaction. Possible values are "LOCAL" if 
         only the current site documented the 
         reaction, "REMOTE SITE(S)" if only a 
         remote site documented the reaction, or 
         "LOCAL AND REMOTE SITE(S)" if both the 
         current and remote sites documented the 
         reaction.  
  
 If TYP="CM", TYP="IN", or TYP="CL", this array will be undefined.  
VARIABLES: GMRAIEN                      TYPE: Output
 VARIABLES DESCRIPTION:   The calling application should either NEW this
 variable before calling this component or KILL this variable after it is no
 longer needed.  
  
 If TYP="IN", this array will contain the PATIENT ALLERGIES file (#120.8) 
 internal entry numbers (IENs) that match the ingredient defined by the PTR 
 parameter as subscripts. If TYP="CL", this array will contain the PATIENT 
 ALLERGIES file (#120.8) IENs that match the class defined by the PTR parameter
 as subscripts.  
   Format: 
   GMRAIEN(120.8_IEN)="" 
  
 If TYPE="CM" or TYP="DR", this array will be undefined.  
VARIABLES: $T                           TYPE: Output
 VARIABLES DESCRIPTION:   $T will be defined as 1 (True) if the patient has an
 allergy to an agent defined by the TYP and PTR variables, else it returns 0
 (False).  
  
 **NOTE: As of August 6, 1996 this variable is no longer supported.  
COMPONENT/ENTRY POINT: $$ORCHK2(DFN,TYP,PTR,LOC,RETURN)
 COMPONENT DESCRIPTION:   This call checks if the patient has an adverse
 reaction to an agent defined by the parameters TYP and PTR.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's internal entry number (IEN) in the PATIENT
 file (#2).  
VARIABLES: TYP                          TYPE: Input
 VARIABLES DESCRIPTION:   The type of agent to check. Possible values are: 
  "CM" - Contrast Media Reaction 
  "DR" - Drug Reaction 
  "IN" - Drug Ingredient 
  "CL" - Drug Class 
VARIABLES: PTR                          TYPE: Input
 VARIABLES DESCRIPTION:   The agent to check for. Possible values are: 
  If TYP="CM", PTR is ignored.  
  If TYP="DR", PTR is formatted as 
               PSNDA.PSNVPN.LPTR, 
               where PSNDA is the IEN to the 
               VA GENERIC file (#50.6), PSNVPN 
               is the IEN to the VA PRODUCT file 
               (#50.68) and LPTR is the IEN to 
               the DRUG file (#50). If PSNDA is 
               passed in, then PSNVPN is required 
               and LPTR is optional. LPTR may be 
               passed in by itself, but the caller 
               must include two preceding periods 
               (i.e., "..1068").  
  If TYP="IN", PTR is the IEN to the DRUG 
               INGREDIENTS file (#50.416).  
  If TYP="CL", PTR is the IEN to the VA DRUG CLASS 
               file (#50.605).  
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   An optional location type flag.  
  
 If TYP="CM" and LOC is defined and greater than 0, the name of every site that
 documented the reaction and when each site documented the reaction will be
 returned in the second caret piece of $$ORCHK.  
  
 If TYP="DR", TYP="IN", or TYP="CL", LOC is ignored.  
VARIABLES: RETURN                       TYPE: Input
 VARIABLES DESCRIPTION:   Name of array in which to return order check
 messages. The name cannot be RETURN.  
  
 If TYP="DR", data is returned in the named array.  
  
 If TYP="IN", TYP="CL", or TYP="CM", RETURN is ignored.  
VARIABLES: $$ORCHK2                     TYPE: Output
 VARIABLES DESCRIPTION:   For all values of TYP, $$ORCHK2 will be defined as -1
 if the parameters are incorrect, an empty string if the patient does not have
 an assessment or 0 if the patient has no known reactions to the agent defined
 by the TYP and PTR parameters.  
  
 The following additional values are returned depending on the value of TYP: 
  
 If TYP="CM" and the patient has a reaction to contrast media, $$ORCHK2 will be
 defined as 1. Additionally, if LOC is greater than zero, the second caret
 piece of $$ORCHK2 will contain the name of every site that documented the
 reaction and when each site documented the reaction.  
  
 If TYP="IN" or TYP="DR" and the patient has a reaction to the agent defined in
 the PTR parameter, $$ORCHK2 will be defined as 1.  
  
 If TYP="CL" and the patient has a reaction to the agent defined in the PTR
 parameter, $$ORCHK2 will be defined as 2.  
VARIABLES: GMRAING                      TYPE: Output
 VARIABLES DESCRIPTION:   The calling application should either NEW this
 variable before calling this component or KILL this variable after it is no
 longer needed. If TYP="IN", this array will contain the drug ingredients in
 the agent defined by PTR to which the patient has a reaction to.  
   Format: 
   GMRAING(PTR)=Offender(s)^Caret-delimited string 
   PTR - for local reactions, the internal entry 
         number (IEN) in the PATIENT ALLERGIES file 
         (#120.8) and for remote reactions, "R" 
         followed by the reaction's number in the 
         ^XTMP("ORRDI","ART",DFN) global (DFN is 
         the patient's IEN in the PATIENT file, 
         #2).  
   Offender(s) - Drug ingredient(s) found in both 
                 the reaction and in the agent.  
                 Contains two sub-fields 
                 separated by the pipe character.  
                 Multiple ingredients are separated 
                 by "~".  
                 Sub-field 1: NAME field (#.01) in 
                              the DRUG INGREDIENTS 
                              file (#50.416) 
                 Sub-field 2: IEN in the DRUG 
                              INGREDIENTS file 
                              (#50.416) 
   Caret-delimited string: 
     For those pieces that contain sub-fields, the 
     sub-fields are separated by the pipe 
     character.  
  Piece   Value 
 ==================================================
  1       Station Documenting Reaction 
          Sub-field 1: NAME field (#.01) in the 
                       INSTITUTION file (#4) 
          Sub-field 2: IEN in the INSITUTION file 
                       (#4) 
  2       Site Type of Documenting Station 
          Sub-field 1: External format ("REMOTE" or 
                       "LOCAL") 
          Sub-field 2: Internal format ("R" or "L") 
  3       ORIGINATION DATE/TIME field (#4) in the 
          PATIENT ALLERGIES file (#120.8) 
          Sub-field 1: External format 
          Sub-field 2: Internal FileMan format 
  4       Severities String 
  5       REACTIONS field (#10) in the PATIENT 
          ALLERGIES file (#120.8) 
          Sub-field 1: External format 
          Sub-field 2: Internal format 
          Multiple reactions are separated from 
          each other with "~".  
  6       REACTANT field (#.02) in the PATIENT 
          ALLERGIES file (#120.8) 
  7       GMR ALLERGY field (#1) in the PATIENT 
          ALLERGIES file (#120.8) 
          Sub-field 1: External format 
          Sub-field 2: Internal format 
  8       OBSERVED/HISTORICAL field (#6) in the 
          PATIENT ALLERGIES file (#120.8) 
          Sub-field 1: External format 
          Sub-field 2: Internal format 
  9       Database Type 
          Sub-field 1: External format ("VISTA" or 
                       "COTS") 
          Sub-field 2: Internal format ("V" or "C") 
   Severities String - The reaction's severities.  
     Contains two sub-fields separated by "|".  
     Multiple severities are separated by "~".  
       Subfield 1: DATE/TIME OF EVENT field (#.01) 
                   in the ADVERSE REACTION 
                   REPORTING file (#120.85) 
       Subfield 2: SEVERITY field (#14.5) in the 
                   ADVERSE REACTION REPORTING file 
                   (#120.85) 
  
 If TYP="CM", TYP="DR", or TYP="CL", this array will be undefined.  
VARIABLES: GMRADRCL                     TYPE: Output
 VARIABLES DESCRIPTION:   The calling application should either NEW this
 variable before calling this component or KILL this variable after it is no
 longer needed. If TYP="CL", this array will be defined. It will contain the
 drug classes of the agent defined by PTR to which the patient has a reaction
 to.  
   Format: 
   GMRADRCL(PTR)="Offender(s)^Caret-delimited 
                 string" 
   PTR - for local reactions, the internal entry 
         number (IEN) in the PATIENT ALLERGIES file 
         (#120.8) and for remote reactions, "R" 
         followed by the number in the 
         ^XTMP("ORRDI","ART",DFN) global (DFN is 
         the patient's IEN in the PATIENT file, 
         #2).  
   Offender(s) - VA drug class(es) found in both 
                 the reaction and in the agent.  
                 Contains two sub-fields separated 
                 by the pipe character. Multiple VA 
                 drug classes are separated by "~".  
                 Sub-field 1: NAME field (#.01) in 
                              the VA DRUG CLASS 
                              file (#50.605) 
                 Sub-field 2: IEN in the VA DRUG 
                              CLASS file (#50.605) 
   Caret-delimited string: refer to the caret 
   delimited string section in the GMRAING output 
   variable.  
  
 If TYP="CM", TYP="DR", or TYP="IN", this array will be undefined.  
VARIABLES: RETURN                       TYPE: Output
 VARIABLES DESCRIPTION:   The calling application should either NEW the
 variable identified by the INPUT parameter RETURN before calling this
 component or KILL the variable identified by the INPUT parameter RETURN after
 it is no longer needed. If TYP="DR", this array will contain the data needed
 to construct the order check messages as well as the reaction data related to
 the message data.  
   Format: 
   RETURN=N 
     N - total number of order check messages 
  
   RETURN(X,PTR)=Caret-delimited string 
     X - message number; starts at one and 
         increments by one 
     PTR - for local reactions, the internal entry 
           number (IEN) in the PATIENT ALLERGIES 
           file (#120.8) and for remote reactions, 
           "R" followed by the reaction's number in 
           the ^XTMP("ORRDI","ART",DFN) global (DFN 
           is the patient's IEN in the PATIENT 
           file, #2).  
     Caret-delimited string - Reaction data 
                              associated with 
                              message X; all fields 
                              are in internal 
                              format 
  
  Piece   Value 
 ==================================================
  1       Station Documenting Reaction 
          IEN in INSTITUTION file (#4) 
  2       Site Type of Documenting Station 
          "R" or "L" 
  3       ORIGINATION DATE/TIME field (#4) in the 
          PATIENT ALLERGIES file (#120.8) 
  4       Severities String 
  5       REACTIONS field (#10) in the PATIENT 
          ALLERGIES file (#120.8) 
          Multiple reactions are separated from 
          each other with "~".  
  6       REACTANT field (#.02) in the PATIENT 
          ALLERGIES file (#120.8) 
  7       GMR ALLERGY field (#1) in the PATIENT 
          ALLERGIES file (#120.8) 
  8       OBSERVED/HISTORICAL field (#6) in the 
          PATIENT ALLERGIES file (#120.8) 
  9       Database Type 
          "V" or "C" 
    Severities String - The reaction's severities.  
      Contains two sub-fields separated by "|".  
      Multiple severities are separated by "~".  
        Subfield 1: DATE/TIME OF EVENT field (#.01) 
                    in the ADVERSE REACTION 
                    REPORTING file (#120.85) 
        Subfield 2: SEVERITY field (#14.5) in the 
                    ADVERSE REACTION REPORTING file 
                    (#120.85) 
  
   RETURN(X,"MESSAGE",1)=N 
     N - total number of stations included in this 
         message 
  
   RETURN(X,"MESSAGE",1,Y)=Caret-delimited string 
     Y - internal entry number (IEN) of the 
         documenting station's entry in the 
         INSTITUTION file (#4) 
     Caret-delimited string - site-specific data; 
                              all fields are in 
                              external format 
  Piece   Value 
 ==================================================
  1       Station documenting reaction 
          NAME field (#.01) in the INSTITUTION file 
          (#4) 
  2       Site Type of Documenting Station 
          "REMOTE" or "LOCAL" 
  3       ORIGINATION DATE/TIME field (#4) in the 
          PATIENT ALLERGIES file (#120.8) 
  4       OBSERVED/HISTORICAL field (#6) in the 
          PATIENT ALLERGIES file (#120.8) 
  
   RETURN(X,"MESSAGE",1,Y,1,Z)=Caret-delimited 
                               string 
     Z - Severity number; starts at one and 
         increments by one. Corresponds to the 
         severity's position number in the 
         severities string in RETURN(X,PTR).  
     Caret-delimited string - observation data; all 
                              fields are in 
                              external format 
  
 Piece   Value 
 ==================================================
  1       DATE/TIME OF EVENT field (#.01) in the 
          ADVERSE REACTION REPORTING file (#120.85) 
  2       SEVERITY field (#14.5) in the ADVERSE 
          REACTION REPORTING file (#120.85) 
  
   RETURN(X,"MESSAGE",2)=Caret-delimited string 
     Caret-delimited string - reaction-specific 
                              data combined from 
                              all sites included in 
                              message X; all fields 
                              are in external 
                              format 
  
 Piece   Value 
 ==================================================
  1       REACTIONS field (#10) in the PATIENT 
          ALLERGIES file (#120.8) 
  2       REACTANT field (#.02) in the PATIENT 
          ALLERGIES file (#120.8) 
  3       GMR ALLERGY field (#1) in the PATIENT 
          ALLERGIES file (#120.8) 
  
   RETURN(X,"MESSAGE","OFFENDERS",SUB)= 
                            Tilde-delimited string 
     SUB - the type of reaction item that was 
           matched with the agent; "ING" for 
           ingredient, "CLS" for class or "REC" 
           for reactant (GMR ALLERGY field, #1, 
           in the PATIENT ALLERGIES file, #120.8) 
     Tilde-delimited string - the causative agents 
                              that were matched in 
                              external format 
                              delimited by "~" 
  
 If TYP="IN", TYP="CL" or TYP="CM", the variable identified by the INPUT 
 parameter RETURN will not be modified.  
  DATE ACTIVATED: JUN 01, 1998

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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

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 EMAIL GROUP 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
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
  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
 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
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,"RMV",0)= # of LINES 
  ^TMP("PS",$J,TFN,"RMV",D1,0)=REMOVAL TIMES 
    Where:  Removal 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 
  ^TMP("PS",$J,TFN,"IND",0)=INDICATION 
VARIABLES: OCL                          TYPE: Output
 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
  DATE ACTIVATED: JUL 28, 2008

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
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,"ALOG",0) = # of LINES from ACTIVITY LOG multiple of File #53.1 
  ^TMP("PS",$J,"ALOG",D1,0) = ACTIVITY LOG DATE^ACTIVITY LOG USER [IEN into VA
 200]^ACTION [IEN into File #53.3]^FIELD CHANGED DUE TO ACTIVITY^OLD FIELD DATA 
  ^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,"RMV",0)= # of LINES 
  ^TMP("PS",$J,"RMV",D1,0)=REMOVAL TIMES 
     Where: Removal 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,"IND",0)=1 
  ^TMP("PS",$J,"IND",1,0)=INDICATION 
  ^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
  DATE ACTIVATED: OCT 10, 2018

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
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: 1
  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
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
FIELD NUMBER: 4                         FIELD NAME: MAX. ORDER FREQ.
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4.5                       FIELD NAME: SINGLE DAY MAX ORDER FREQ
  LOCATION: 0;7                         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
FIELD NUMBER: 2                         FIELD NAME: BLOCK ORDERING
  LOCATION: 0;3                         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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   
  
SUBSCRIBING PACKAGE: VBECS
  DATE ACTIVATED: FEB 20, 2024

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,
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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be using the access in this ICR for VIAB
 ALLSPEC RPC and OrderMgmtSvc - getLabTestSpecPickLs 
  DATE ACTIVATED: FEB 20, 2013

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,
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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be using the access in the ICR for their VIAB
 ALLSAMP RPC and OrderMgmtSvc - getLabSamplePickList 
  DATE ACTIVATED: APR 23, 2012

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
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
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 EMAIL GROUP 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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 2393                            IA #: 2393
  FILE NUMBER: 50.605                   GLOBAL ROOT: PS(50.605
  DATE CREATED: MAY 10, 1998            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: OE/RR USE OF PS(50.605,
  ID: PS(50.605
GLOBAL REFERENCE: PS(50.605,'C',
 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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
  
 Order Entry/Results Reporting requests teh ability to use the "C" x-ref in the
 VA DRUG CLASS file (#50.605) when checking whether an allergy is associated
 with a class of drugs.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 2394                            IA #: 2394
  FILE NUMBER: 50.6                     GLOBAL ROOT: PSNDF(
  DATE CREATED: MAY 10, 1998            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: OE/RR USAGE OF PSNDF
  ID: PSNDF(
GLOBAL REFERENCE: PSNDF('B',
GLOBAL REFERENCE: PSNDF('T',
 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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
  
 Order Entry/Results Reporting requests the ability to use the "B" and "T" 
 x-refs in the NATIONAL DRUG file (#50.6) when checking whether an allergy is
 associated with a drug.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
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
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

NUMBER: 2396                            IA #: 2396
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: MAY 10, 1998
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: OE/RR USAGE OF PS(55,
  ID: PS(55,
GLOBAL REFERENCE: PS(55,
FIELD NUMBER: 52.1                      FIELD NAME: RX UPDATE
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Field is used by the Orders conversion included with CPRS
 v1.  
FIELD NUMBER: 104                       FIELD NAME: CONVERSION COMPLETED
  LOCATION: 5.1;11                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,DA,'P','A',
 GLOBAL DESCRIPTION:   As part of the pre-CPRS functionality that is released
 with OR*2.5*49, an estimate of global growth is given.  One of the components
 of that growth is the backfilling of outpatient pharmacy prescriptions.  
  
 In order to calculate the number of prescriptions that might be backfilled, we
 loop through the PHARMACY PATIENT file and then through the "A" x-ref of the
 PRESCRIPTION PROFILE multiple (#55.03).  We then get the pointer to the
 PRESCRIPTION file (from the cross-reference) and navigate to that file to
 perform additional checks.  
 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 EMAIL GROUP 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.  
  
 Order Entry/Results Reporting requests global read access to the Pharmacy 
 Patient file (#55) for the fields listed below.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

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
  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
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
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
 GENERAL DESCRIPTION:   Order Entry/Results Reporting requests approval to make
 the following calls to PSOORRL.  
  
 Patch PSO*7*622 updated OCL^PSOORRL with two new parameters to accept a second
 set of date ranges for Inpatient Medications. Previously, this API only
 supported one set of date ranges used for both Outpatient Medications and
 Inpatient Medications. Existing callers of this API will not see any change in
 behavior, as if nothing is passed into the new parameters, it will behave as
 it did previously. Only if a caller wishes to use different date ranges for
 Outpatient/Non-VA Medications and Inpatient Medication they need to utilize
 the new parameters.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: OCL
 COMPONENT DESCRIPTION:   Called to return a list of meds.  
  
 OCL^PSOORRL(DFN,STARTDATEOUT,ENDDATEOUT,VIEW,STARTDATEINP,ENDDATEINP)  
  
 Passed: DFN - Patient's Internal Pointer 
  
 StartdateOut - Date/Time to start search for Outpatient & Non-VA 
                medications (optional) 
   EnddateOut - Date/Time to terminate search for Outpatient & Non-VA 
                medications (optional) 
         View - Sort format for the returned display. (optional) StartdateInp -
 Date/Time to start search for Inpatient medications 
                (Optional) 
   EnddateInp - Date/Time to terminate search for Inpatient medications 
                (Optional) Note: If both StartdateInp and EnddateInp are not
 passed in to the API, then StartdateOut and EnddateOut will also be used for
 the Inpatient medications date range.  
  
  
 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), 
   N;O = Non-VA Med (file #55, subfile #55.05), 
   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,"RMV",0)= # of LINES ^TMP("PS",$J,"RMV",D1,0)=REMOVAL TIMES
 Where: Removal 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.  
  
 ^TMP("PS",$J,D0,"IND",0)=INDICATION 
VARIABLES: DFN                          TYPE: Input
VARIABLES: BEGDATEOUT                   TYPE: Input
 VARIABLES DESCRIPTION:   Beginning date for search of Outpatient & Non-VA
 medications.  
VARIABLES: ENDDATEOUT                   TYPE: Input
 VARIABLES DESCRIPTION:   Ending date for search of Outpatient & Non-VA
 medications.  
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.  
VARIABLES: BEGDATEINP                   TYPE: Input
 VARIABLES DESCRIPTION:   Beginning date for search of Inpatient medications.  
VARIABLES: ENDDATEINP                   TYPE: Input
 VARIABLES DESCRIPTION:   Ending date for search of Inpatient medications.  
  
 Note: If both BEGDATEINP and ENDDATEINP are not passed in to the API, then 
 BEGDATEOUT and ENDDATEOUT will also be used for the Inpatient medications date
 range.  
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 TIMES Where: administration time = 
 Free text 2-119 characters 
  
 ^TMP("PS",$J,"RMV",0)= # of LINES 
  
 ^TMP("PS",$J,"RMV",D1,0)=REMOVAL TIMES Where: Removal 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 
  
 ^TMP("PS",$J,"IND",0)=1 
  
 ^TMP("PS",$J,"IND",1,0)=INDICATION 
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)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: JUL 28, 2008

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
  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
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
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
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
  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
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

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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  

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
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
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
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
  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

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
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.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Protocol is HMP XQOR EVENTS 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************

NUMBER: 2416                            IA #: 2416
  DATE CREATED: MAY 15, 1998
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Other                           NAME: PS EVSEND OR
 GENERAL DESCRIPTION:   This agreement will allow certain packages to attach
 protocols as Items under the PS EVSEND OR protocol, which is an Extended
 Action protocol used to pass Pharmacy order information from Pharmacy packages
 to other packages in the form of an array.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   CPRS will use this protocol to process Pharmacy order
 information.  
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham
 SUBSCRIBING DETAILS:   CIRN will use this protocol to process Pharmacy order
 information.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

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
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
 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
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
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIABDX SAVE RPC references PSSJORDF routine.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Added 8/24/20 
  DATE ACTIVATED: MAY 10, 2011

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
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
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
 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
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)
  DATE ACTIVATED: JAN 09, 2015

NUMBER: 2422                            IA #: 2422
  DATE CREATED: MAY 21, 1998
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  CUSTODIAL ISC: Salt Lake City         USAGE: Supported
  TYPE: Routine                         ROUTINE: GMRAOR2
  NAME: Detailed Adverse Reaction       ID: GMRAOR2
 GENERAL DESCRIPTION:   This integration agreement allows a package to retrieve
 detailed information for a specific adverse reaction.  
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
KEYWORDS: DETAILED ADVERSE REACTION DATA
COMPONENT/ENTRY POINT: EN1(IEN,ARRAY)
 COMPONENT DESCRIPTION:   **NOTE: Patch GMRA*4*46 was released on 05/24/2016
 with a compliance date of 06/24/2016. This patch included the new EN2
 component, which is intended to replace this component. New subscribers should
 use the EN2 component. A future patch will phase out the use of this component
 as subscribing applications move to the EN2 component.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number (IEN) for the allergy/adverse
 reaction in the PATIENT ALLERGIES file (#120.8).  
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   Optional variable indicating the name of the array in
 which to return results. If this is undefined, data is returned in GMRACT().  
VARIABLES: GMRACT                       TYPE: Output
 VARIABLES DESCRIPTION:   Caret-delimited string: NOTE: Unless specified
 otherwise, all fields are 
       returned in external format.  
  Piece   Value 
 ================================================
   1      REACTANT field (#.02) in the PATIENT 
          ALLERGIES file (#120.8) 
   2      ORIGINATOR field (#5) in the PATIENT 
          ALLERGIES file (#120.8) 
   3      TITLE field (#8) in the NEW PERSON file 
          (#200) for the ORIGINATOR 
   4      VERIFIED field (#19) in the PATIENT 
          ALLERGIES file (#120.8) 
   5      OBSERVED/HISTORICAL field (#6) in the 
          PATIENT ALLERGIES file (#120.8) 
   6      MECHANISM field (#17) in the PATIENT 
          ALLERGIES file (#120.8) 
   7      ALLERGY TYPE field (#3.1) in the 
          PATIENT ALLERGIES file (#120.8) 
   8      VERIFIER field (#21) in the PATIENT 
          ALLERGIES file (#120.8) 
   9      VERIFICATION DATE/TIME field (#20) in 
          the PATIENT ALLERGIES file (#120.8) 
   10     ORIGINATION DATE/TIME field (#4) in the 
          PATIENT ALLERGIES file (#120.8) 
VARIABLES: GMRACT('C',Y)                TYPE: Output
 VARIABLES DESCRIPTION:   Array of comments for this reaction. Comments is a
 multiple field, and word processing: <date/time entered^source
 (verifier/originator)> 
VARIABLES: GMRACT('C',Y,Z,0)            TYPE: Output
 VARIABLES DESCRIPTION:   Word processing text for comment GMRACT('C',Y).  
VARIABLES: GMRACT('O',Y)                TYPE: Output
 VARIABLES DESCRIPTION:   Array of observation dates/severities for this
 reaction: <observation date^severity>.  
VARIABLES: GMRACT('S',Y)                TYPE: Output
 VARIABLES DESCRIPTION:   Array of signs/symptoms for this reaction:
 <sign/symptom>.  
VARIABLES: GMRACT('V',Y)                TYPE: Output
 VARIABLES DESCRIPTION:   Array of VA drug classes for this reaction: <VA drug
 class code^VA drug class name>.  
VARIABLES: GMRACT('I',Y)                TYPE: Output
 VARIABLES DESCRIPTION:   Array of drug ingredients for this reaction: <drug
 ingredient name>.  
COMPONENT/ENTRY POINT: EN2(IEN,ARRAY)
 COMPONENT DESCRIPTION:   This call returns data for the adverse reaction
 specified by IEN.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number (IEN) of the adverse reaction
 within the PATIENT ALLERGIES file (#120.8) to return data for.  
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   Name of the array to return data in. If not defined,
 data is returned in GMRACT().  
  
 Returned Data Format: NOTE: Unless specified otherwise, all fields are 
       returned in external format.  
  
 ARRAY=Caret-delimited string 
   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      ORIGINATOR field (#5) in the PATIENT 
            ALLERGIES file (#120.8) 
     3      TITLE field (#8) in the NEW PERSON file 
            (#200) for the ORIGINATOR 
     4      VERIFIED field (#19) in the PATIENT 
            ALLERGIES file (#120.8) 
     5      OBSERVED/HISTORICAL field (#6) in the 
            PATIENT ALLERGIES file (#120.8) 
     6      MECHANISM field (#17) in the PATIENT 
            ALLERGIES file (#120.8) 
     7      ALLERGY TYPE field (#3.1) in the 
            PATIENT ALLERGIES file (#120.8) 
     8      VERIFIER field (#21) in the PATIENT 
            ALLERGIES file (#120.8) 
     9      VERIFICATION DATE/TIME field (#20) in 
            the PATIENT ALLERGIES file (#120.8) 
     10     ORIGINATION DATE/TIME field (#4) in the 
            PATIENT ALLERGIES file (#120.8) 
  
 ARRAY("C",COUNT)=Caret-delimited string 
   COUNT - number that starts at one for the first 
           comment and increments by one for each 
           subsequent comment 
   Caret-delimited string: 
    Piece   Value 
   ================================================
     1      DATE/TIME COMMENT ENTERED sub-field 
            (#.01) in the COMMENTS field (#26) in 
            the PATIENT ALLERGIES file (#120.8) 
     2      COMMENT TYPE sub-field (#1.5) in the 
            COMMENTS field (#26) in the PATIENT 
            ALLERGIES file (#120.8) 
     3      USER ENTERING sub-field (#1) in the 
            COMMENTS field (#26) in the PATIENT 
            ALLERGIES file (#120.8) 
   NOTE: Nodes descendant from ARRAY("C",COUNT) 
         comprise the COMMENTS sub-field (#2) in 
         the COMMENTS field (#26) in the PATIENT 
         ALLERGIES file (#120.8).  
  
 ARRAY("O",COUNT)=Caret-delimited string 
   COUNT - number that starts at one for the first 
           observer and increments by one for each 
           subsequent observer 
   Caret-delimited string: 
    Piece   Value 
   ================================================
     1      DATE/TIME OF EVENT field (#.01) in the 
            ADVERSE REACTION REPORTING file 
            (#120.85) 
     2      SEVERITY field (#14.5) in the ADVERSE 
            REACTION REPORTING file (#120.85) 
  
 ARRAY("S",COUNT)=TEXT 
   COUNT - number that starts at one for the first 
           sign or symptom and increments by one 
           for each subsequent sign or symptom 
   TEXT - REACTION sub-field (#.01) in the 
          REACTIONS field (#10) in the PATIENT 
          ALLERGIES file (#120.8) followed by a 
          space followed by the DATE ENTERED sub- 
          field (#3) in the REACTIONS field (#10) 
          in the PATIENT ALLERGIES file (#120.8) 
          surrounded by parentheses.  
  
 ARRAY("V",COUNT)=Caret-delimited string 
   COUNT - number that starts at one for the first 
           drug class and increments by one 
           for each subsequent drug class 
   Caret-delimited string: 
    Piece   Value 
   ================================================
     1      VA DRUG CLASS sub-field (#.01) in the 
            DRUG CLASSES field (#3) in the PATIENT 
            ALLERGIES file (#120.8) 
     2      CLASSIFICATION field (#1) in the VA 
            DRUG CLASS file (#50.605) for the VA 
            DRUG CLASS sub-field (#.01) entry in 
            the DRUG CLASSES field (#3) in the 
            PATIENT ALLERGIES file (#120.8) 
  
 ARRAY("I",COUNT)=TEXT 
   COUNT - number that starts at one for the first 
           drug ingredient and increments by one 
           for each subsequent drug ingredient 
   TEXT - DRUG INGREDIENT sub-field (#.01) in the 
          DRUG INGREDIENTS field (#3) in the 
          PATIENT ALLERGIES file (#120.8) 
  DATE ACTIVATED: FEB 13, 2017

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
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
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

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
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

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
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

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
 GENERAL DESCRIPTION:   This DBIA will document the calls from Order
 Entry/Results Reporting to GMRCTIU.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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

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
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.  
COMPONENT/ENTRY POINT: COLL(TEST,.Y)
 COMPONENT DESCRIPTION:   Get Collection Sample and Specimen data for a test.  
VARIABLES: TEST                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of file 60 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Array of collection sample and specimen info for a
 test.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA requesting access to TEST, SCOM, DEFURG and
 GCOM~LR7OR3 for use with VIAB LOAD RPC and OrderMgmtSvc -
 getLabTestSpecificParams 
  DATE ACTIVATED: JAN 22, 2021

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
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:   
  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA is using the access in the ICR for VIAB IC VALID
 RPC and OrderMgmtSvc - getImmediateCollectValidText.  It also needs this
 access for VIAB IMMED COLLECT RPC and  OrderMgmtSvc -
 getImmediateCollectMessage.  

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
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: 2431                            IA #: 2431
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDOE
  NAME: DBIA2431                        ID: SDOE
 GENERAL DESCRIPTION:   A need exists in Integrated Billing to be able to get
 the disposition node from the pointer value in the 9th piece of the encounter
 file 0-node.  We would like to call $$ER^SDOE to accomplish this.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ER
 COMPONENT DESCRIPTION:   Function returns 9th piece of Encounter file 0-node
 (EXTENDED REFERENCE - File #409.68, Field #.09).  
VARIABLES: SDOE                         TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of encounter.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

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
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
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
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: 2435                            IA #: 2435
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9
  DATE CREATED: JUN 19, 1998            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: READ FILE 80 FILE HEADER        ID: ICD9
GLOBAL REFERENCE: ICD9(0)
 GENERAL DESCRIPTION:   Clinical Reminders needs to be able to determine when a
 new version of file 80 has been installed in order to keep its expanded
 taxonomy cache current. In order to do this we would like to do a direct read
 of pieces 3 and 4 of the file header, ^ICD9(0).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 2436                            IA #: 2436
  FILE NUMBER: 80.1                     GLOBAL ROOT: ICD0
  DATE CREATED: JUN 19, 1998            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: READ FILE 80.1 FILE HEADER      ID: ICD0
GLOBAL REFERENCE: ICD0(0)
 GENERAL DESCRIPTION:   Clinical Reminders needs to be able to determine when a
 new version of file 80.1 has been installed in order to keep its expanded
 taxonomy cache current. In order to do this we would like to do a direct read
 of pieces 3 and 4 of the file header, ^ICD0(0).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

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
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
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham
SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI
SUBSCRIBING PACKAGE: POLICE & SECURITY
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be referencing the Name (#.01) field in the
 Medical Center Division (#40.8) file in the VIAB BMS RPC.  

NUMBER: 2439                            IA #: 2439
  FILE NUMBER: 44                       GLOBAL ROOT: SC(DO
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA2439
  ID: SC(DO
GLOBAL REFERENCE: SC(DO,0)
FIELD NUMBER: 3.5                       FIELD NAME: Division
  LOCATION: 0;15                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Division pointer. Division name assigned to each entry in
 this file to identify where the specific location is.  
 GLOBAL DESCRIPTION:   
  
 GENERAL DESCRIPTION:   Pharmacy Benefits Management (PBM) software needs to
 access the division pointer from the Hospital Location File in order to 
 extract the facility number from the Medical Center Division File...  Existing
 DBIA #2432 would meet the need.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham
SUBSCRIBING PACKAGE: DENTAL

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
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.  
  
 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 
  STATUS: Retired                       EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  ISC: Hines

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
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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
 SUBSCRIBING DETAILS:   Added 11/07/2006 

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
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
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
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
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
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
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
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
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
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
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
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT

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
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
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
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
  DATE ACTIVATED: JUN 04, 2012

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
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2459                            IA #: 2459
  FILE NUMBER: 161                      GLOBAL ROOT: FBAAA(
  DATE CREATED: JUL 01, 1998            CUSTODIAL PACKAGE: FEE BASIS
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIA2459
  ID: FBAAA(
GLOBAL REFERENCE: FBAAA(D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: FROM DATE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Authorization 'from' date.  
 GLOBAL DESCRIPTION:   Fee Basis authorization multiple.  
 GENERAL DESCRIPTION:   FEE BASIS PATIENT file access.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 23, 2006
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.  
FIELD NUMBER: .322014
  FIELD NAME: SW ASIA COND REGISTRATION DATE 
  LOCATION: .322;14                     ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   SW Asia cond registration date.  
 GLOBAL DESCRIPTION:   Data node.  
GLOBAL REFERENCE: DPT(D0,.3217)
FIELD NUMBER: .321701                   FIELD NAME: CAMP LEJEUNE
  LOCATION: .3217;1                     ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Camp Lejeune eligibility indicator.  
 GENERAL DESCRIPTION:   PATIENT file access.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 10/10/25, effective with patch PX*1.0*244.  PCE
 needs to determine if a veteran is eligible for the Southwest Asia and Camp
 Lejeune Special Authorities. Two fields added SW ASIA COND REGISTRATION DATE
 and CAMP LEJEUNE 

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
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
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE
 SUBSCRIBING DETAILS:   1/10/22: Patient Representative Decom patch QAC*2.0*25
 has been released on 01/10/2022 with a Compliance date of 2/10/22. Patient
 Representative subscription retired effective with a Compliance date of
 2/10/22.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

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
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
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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Call to EN^DGPMSTAT in routine ORQPT2.  

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
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: 2466                            IA #: 2466
  FILE NUMBER: 63                       GLOBAL ROOT: LR(
  DATE CREATED: MAY 25, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: DBIA2466
  ID: LR(
GLOBAL REFERENCE: LR(LRDFN,'CH',TEST,
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME SPECIMEN TAKEN
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   TEST will vary over ALL entries in that subscript
 position.  
GLOBAL REFERENCE: LR(LRDFN,'CY',TEST,
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME SPECIMEN TAKEN
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   TEST will vary over ALL entries in that subscript
 position.  
GLOBAL REFERENCE: LR(LRDFN,'EM',TEST,
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME SPECIMEN TAKEN
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   TEST will vary over ALL entries in that subscript
 position.  
GLOBAL REFERENCE: LR(LRDFN,'MI',TEST,
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME SPECIMEN TAKEN
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   TEST will vary over ALL entries in that subscript
 position.  
GLOBAL REFERENCE: LR(LRDFN,'SP',TEST,
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME SPECIMEN TAKEN
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   TEST will vary over ALL entries in that subscript
 position.  
 GENERAL DESCRIPTION:   CIRN needs read access to the ^LR( global to calculate
 a Master of Record score.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham

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: ORDERABLE ITEMS, PROMPT VALUES
  ID: ORX8
 GENERAL DESCRIPTION:   This integration agreement will allow subscribers to
 retrieve information from a specific order in the ORDER file (#100).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OI
KEYWORDS: VALUE
KEYWORDS: ORDERABLE ITEMS
KEYWORDS: PROMPT
COMPONENT/ENTRY POINT: $$OI(IFN)
 COMPONENT DESCRIPTION:   Returns the first orderable item for the order.  
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The Internal Entry Number (IEN) of the order in 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(IFN,ID,INST,FORMAT)
 COMPONENT DESCRIPTION:   Returns a single value from the content of an order.  
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the order in 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.  
COMPONENT/ENTRY POINT: OIS(RESULT,IFN)
 COMPONENT DESCRIPTION:   Returns an array of orderable items for a given order
 number.  
VARIABLES: RESULT                       TYPE: Both
 VARIABLES DESCRIPTION:   This variable is a reference to an array that will
 contain the order's orderable items. The array is formatted as follows: 
  
   RESULT(OI)=DATA 
     OI: IEN of the orderable item in the ORDERABLE 
         ITEMS file (#101.43).  
     DATA: Caret-delimited ('^') string of field 
           values from the ORDERABLE ITEMS file 
           (#101.43): 
           NAME (#.01) ^ ID (#2) 
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the order in the ORDER file (#100).  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Consult/Request Tracking has been using 2467 since the
 first GMRC patch.  
  
 Effective with GMRC*3.0*106, the Community Care Referrals and Authorizations
 (CCR&A), a part of the Consult/Request Tracking (GMRC) package, is accessing
 the Orders File (#100) to get the Orderable Item from the Orderable Item
 multiple. The information is included in the HL7 message that is sent to the
 HealthShare Referral Manager (HSRM). HSRM is the management platform used to
 track and manage community care consults.  
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.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be calling this API from VIAB MEDHIST RPC.  
  DATE ACTIVATED: DEC 20, 2009

NUMBER: 2468                            IA #: 2468
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDCO23
  NAME: DBIA2468                        ID: SDCO23
 GENERAL DESCRIPTION:   Integration agreement to use the call SC^SDCO23(DFN) to
 display the patient's service connection percentage and rated disabilities as
 part of the help text.  This will display during the Event Capture Data Entry 
 options when a '?' is entered in response to the service connected 
 classification prompt.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SC
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the PATIENT file (#2). 
 
SUBSCRIBING PACKAGE: EVENT CAPTURE      ISC: Albany

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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 2470                            IA #: 2470
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: JUL 07, 1998
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2470
  ID: PS(55,
GLOBAL REFERENCE: PS(55,DFN,'P',NXRX,
FIELD NUMBER: .01                       FIELD NAME: PRESCRIPTION PROFILE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 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 EMAIL GROUP 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.  
  
 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 EMAIL GROUP 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.  
  
 CIRN needs read access to ^PS(55 to calculate the Master of Record score.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham

NUMBER: 2471                            IA #: 2471
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2471
  ID: PSRX(
GLOBAL REFERENCE: PSRX(D0,0)
FIELD NUMBER: 100                       FIELD NAME: STATUS
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   CIRN needs read access to ^PSRX, to calculate the
 Master of Record score.  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham

NUMBER: 2472                            IA #: 2472
  FILE NUMBER: 50.605                   GLOBAL ROOT: PS(50.605,
  DATE CREATED: JUL 09, 1998            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2472
  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 DESCRIPTION:   VA Drug Classification Code.  
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Pointed to
FIELD NUMBER: 1                         FIELD NAME: CLASSIFICATION
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The name of the classification.  
 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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  ISC: Hines

NUMBER: 2473                            IA #: 2473
  FILE NUMBER: 50.605                   GLOBAL ROOT: PS(50.605,
  DATE CREATED: JUL 09, 1998            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA2473
  ID: PS(50.605,
GLOBAL REFERENCE: PS(50.605,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Pointed to
 FIELD DESCRIPTION:   VA Drug Classification Code.  
FIELD NUMBER: .01                       FIELD NAME: CODE
  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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
 The FH SITE PARAMETERS (#119.9) file contains a multiple field called DRUG
 CLASSIFICATIONS (#85) which points to the VA DRUG CLASS (#50.605) file.  This
 allows dietetics users to create a list of drug classes which are of interest
 to clinicians.  These drug classes will be looked for when running the Print
 Nutrition Profile [FHASP1] option.  Under the medications section of that
 report the option will check the medications of the selected patient.  If the
 patient is on any medications that are defined in the DRUG CLASSIFICATIONS
 multiple of the FH SITE PARAMETERS file, the option will display them in this
 report.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: DIETETICS          ISC: Hines
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: DIETETICS          ISC: Hines

NUMBER: 2475                            IA #: 2475
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: JUL 09, 1998
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2475
  ID: PS(55,
GLOBAL REFERENCE: PS(55,DFN,'P','A',DATE,
GLOBAL REFERENCE: PS(55,DFN,5,'AUS',DATE,
GLOBAL REFERENCE: PS(55,DFN,5,ORDER NUMBER,1,1,0)
FIELD NUMBER: .01                       FIELD NAME: DISPENSE DRUG
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 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 EMAIL GROUP 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.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
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
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
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: 2478                            IA #: 2478
  DATE CREATED: JUL 14, 1998            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSOSULB1
  NAME: DBIA2478                        ID: PSOSULB1
  STATUS: Other                         DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DEV1
 COMPONENT DESCRIPTION:   This is the entry point for Outpatient Pharmacy to
 print prescription labels from suspense.  
COMPONENT/ENTRY POINT: $$DSH(REC)
 COMPONENT DESCRIPTION:   This function determines whether the RX SUSPENSE file
 #52.5 has a DAY SUPPLY HOLD condition based on 3/4 elapsed time since last
 fill.  
  
 A 1 (one) is returned if 3/4 of the days supply for a rx/fill has elapsed.  A
 0 (zero) is returned if 3/4 of the days supply for a rx/fill has not elapsed.  
VARIABLES: REC                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to RX SUSPENSE file #52.5.  
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: Controlled Subscription
  TYPE: File                            NAME: RAD/NUC MED REPORTS FILE (#74) ALL
  ID: RARPT
GLOBAL REFERENCE: RARPT(D0)
 GLOBAL DESCRIPTION:   The entire RAD/NUC MED REPORTS file can be read, by
 subscribing VistA applications, with VA 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.  
  
 On August 11th 2020, Clinical Reminders (PXRM) requested subscription to this
 Integration Agreement (IA) to access data in the RAD/NUC MED REPORTS file. It
 was decided at this time that all current and future subscribers to this IA
 would be granted full read with VA FileMan access to all fields in the RAD/NUC
 MED REPORTS file.  
  
 Please note that as of this date (08/20/2020) the following fields are 
 computed and have no global location: 
  
  Field #   Field Name 
  -------   ----------
  102       PROCEDURE 
  103       EXAM STATUS 
  104       CATEGORY OF EXAM 
  106       WARD 
  107       SERVICE 
  108       PRINCIPAL CLINIC 
  109       CONTRACT/SHARING SOURCE 
  109.5     RESEARCH SOURCE 
  112       PRIMARY INTERPRETING RESIDENT 
  113       PRIMARY DIAGNOSTIC CODE 
  114       REQUESTING PHYSICIAN 
  115       PRIMARY INTERPRETING STAFF 
  116       COMPLICATION 
  118       PRIMARY CAMERA/EQUIP/RM 
  119       BEDSECTION 
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
KEYWORDS: RA-PXRM
KEYWORDS: RA-MAG
KEYWORDS: RA-WV
KEYWORDS: RA-SPN
SUBSCRIBING PACKAGE: WOMEN'S HEALTH     ISC: Hines
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   ADDED 8/11/2010 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Clinical Reminders has been granted subscriber status
 to this IA to facilitate the development and release of patch PXRM*2.0*71.  

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
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
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 - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   4/17/14-DSS added as a subscriber to reference the
 "ADC" cross reference.  
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Patch MECH*1.0*1 processes HL7 new-order messages about
 imaging studies performed in the community but not entered through VistA.  In
 order to do this, it needs to invoke Radiology routines and make FileMan calls
 to add entries to the RAD/NUC MED PATIENT File (#70) (for existing VA
 patients), the ORDER File (#100), and the RAD/NUC MED ORDERS File (#75.1). The
 patch then creates an HL7 order-update message that transmits the study's 
 accession number to the sender. ADDED 3/2/2022, effective with MECH*1.0*1 
 Medicom Class 3 product Document Only 
  DATE ACTIVATED: MAY 24, 2012

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
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
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
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
FIELD NUMBER: 100                       FIELD NAME: DISPLAY TEXT
  LOCATION: 1;1                         ACCESS: Read w/Fileman
 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.  
  
 Revision: 
  12/8/23 - Effective with WV*1.0*32, ICR updated to allow access to read a 
  new field DISPLAY TEXT, #100, in file 78.3 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RADx-WV
KEYWORDS: WV-RADx
SUBSCRIBING PACKAGE: WOMEN'S HEALTH     ISC: Hines
  DATE ACTIVATED: DEC 19, 2023

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
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
 GENERAL DESCRIPTION:   API for IVM Patient File. Called in response to
 enrollment events. Determines whether for this patient transmission is
 appropriate, and if so the patient is logged for transmission.  New Input
 Variable "RTAU" added 7/29/2025 with patches IVM*2.0*219 and DG*5.3*1143.      
        
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EVENT(DFN,RTAU)
 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.  
VARIABLES: RTAU                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) The RTAU variable indicates to check if
 the MAS PARAMETERS file(#43) field ENABLE REALTIME ADDRESS UPDATE field(#1403)
 is set to YES. If so, quit do not place this record on the nightly queue.  
SUBSCRIBING PACKAGE: FEE BASIS          ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Updated 4/6/26, New Input Variable "RTAU" added
 7/29/2025 with patches IVM*2.0*219 and DG*5.3*1143.  
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 1/12/24, effective with PX*1.0*241 from the
 COMPACT OHI project, to share critical changes to the COMPACT ACT EPISODE OF
 CARE file #818 to VES via a new HL7 segment added to the existing IVM
 Background Job Full Z07 HL7 message.  

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
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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 2489                            IA #: 2489
  FILE NUMBER: 9.4                      GLOBAL ROOT: DIC(9.4
  DATE CREATED: AUG 05, 1998            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: FILE CORRECTIONS
  ID: DIC(9.4
GLOBAL REFERENCE: DIC(9.4,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: NAMESPACE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(9.4,D1,22,D0,0)
FIELD NUMBER: 1                         FIELD NAME: DATE DISTRIBUTED
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DATE INSTALLED AT THIS SITE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: INSTALLED BY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 41                        FIELD NAME: DESCRIPTION OF ENHANCEMENTS
  LOCATION: 1;0                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(9.4,D0,'VERSION')
FIELD NUMBER: 13                        FIELD NAME: CURRENT VERSION
  LOCATION: VERSION;1                   ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   
  More than one Library Package entry exists from the testing and 
  installation of Version 2.5 and Patches 1-4.  We would like permission 
  to update the site's  Package File #4 with one active and accurate 
  Library entry under the name LIBRARY and namespace LBR.  It will 
  contain a '2.5' VERSION multiple with all the patch installations.  If 
  the '2.5V1' VERSION multiple is present (this was created from the 2.5 
  version installation), we would like to create a '2.5' VERSION 
  multiple as a copy of the '2.5V1' multiple.  If the Package File entry 
  for Library v.1.2 is present, we would like to rename it as 
  LIBRARY(OLD) under the renamed namespace LBRZ.  This would eliminate 
  the need for DBIA #2142 "INSTALL File Read".  If any other entries are 
  located, except the LBRN and LBRT entries (apart of 2.5 installation), 
  we would like to delete them.  We would also like to update the 
  CURRENT VERSION field with the latest version 2.5.  This will prevent 
  any future NOIS logs related to this.  
   
  In order to complete this update, we would like to modify the Package 
  File entry that Patch LBR*2.5*7 linked to in the load.  This 
  modification would use FILE^DIE to update the NAME and PREFIX to 
  LIBRARY and LBR, respectively.  Then to continue with the update, we 
  would like to use FIND^DIC to locate all Package File entries having a 
  PREFIX beginning with "LBR".  From each of these Package file entries, 
  we would like to use FIND^DIC to locate the '2.5V1' VERSION multiple 
  entry.  We would then like to use the IEN from the '2.5V1' VERSION 
  multiple entry and GETS^DIQ to retrieve the DATE DISTRIBUTED (1), DATE 
  INSTALLED AT THIS SITE (2), INSTALLED BY (3), and DESCRIPTION OF 
  ENHANCEMENTS (41) fields to create a '2.5' VERSION multiple.  
   
  To rename the v.1.2 package file entry, we would like to use FILE^DIE 
  to change the NAME and PREFIX fields to LIBRARY(OLD) and LBRZ, 
  respectively.  To remove all unimportant Library Package file entries, 
  we would like to use ^DIK.  
   
  In order to update the CURRENT VERSION field, we would like to use 
  GET1^DIQ to retrieve the present CURRENT VERSION field value and 
  FILE^DIE to change it to "2.5".  
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LIBRARY            ISC: Albany

NUMBER: 2490                            IA #: 2490
  FILE NUMBER: 9.7                      GLOBAL ROOT: XPD(9.7
  DATE CREATED: AUG 05, 1998            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File
  NAME: PATCH INSTALLATION CHECK AND UPDATE
  ID: XPD(9.7
GLOBAL REFERENCE: XPD(9.7
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: STATUS
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PACKAGE FILE LINK
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: INSTALLED BY
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 17                        FIELD NAME: INSTALL COMPLETE TIME
  LOCATION: 1;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   
  In order to complete all corrections to the Package File #9.4 
  referenced in DBIA #2489, we would like to have permission to check 
  and update any Library Package Patch installations stored in the 
  Install File #9.7.  To locate the Library v.2.5 patches, we would like 
  to use FIND^DIC and extract the entries' corresponding data in their 
  STATUS(.02), PACKAGE FILE LINK(1), INSTALLED BY(9), and INSTALL 
  COMPLETE TIME(17) fields.  For each Library patch install entry, we 
  would also like to use GET1^DIQ to extract the internal value for the 
  pointer in the PACKAGE FILE LINK field.  In order to update this field 
  with the pointer to the correct Library Package File entry, we would 
  like to use FILE^DIE.  Error checking for each check and update will 
  be performed. 
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LIBRARY            ISC: Albany

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
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
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

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
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,
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
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.  
  
  DATE ACTIVATED: JUN 26, 2012

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 EMAIL GROUP 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
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES

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
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
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
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
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
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
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)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 11/10/2022, effective with DSSV*1.1 DSS Class 3 
 Document Only 

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
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
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
  ISC: Birmingham

NUMBER: 2506                            IA #: 2506
  FILE NUMBER: 772                      GLOBAL ROOT: HL(772
  DATE CREATED: AUG 20, 1998            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA2506
  ID: HL(772
GLOBAL REFERENCE: HL(772,D0,'IN',
FIELD NUMBER: 200                       FIELD NAME: MESSAGE TEXT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The lab package request a direct read on the "IN"
 subscript of file 772 as follows: S
 LRMN=$P($G(^HL(772,LRMID,"IN",1,0)),HLFS,10) 
  
 This will only be needed `till the next extract update.  
  
  STATUS: Withdrawn                     DURATION: Next Version
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

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
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
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
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
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham

NUMBER: 2511                            IA #: 2511
  FILE NUMBER: 53                       GLOBAL ROOT: PS(53
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA2511
  ID: PS(53
GLOBAL REFERENCE: PS(53,D0,0)
FIELD NUMBER: 6                         FIELD NAME: SC/A&A/OTHER/INPATIENT
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Pharmacy Benefits Management extracts the Rx Patient
 status from the Prescription file to determine the AMIS workload category for
 a prescription. THIS REQUEST IS FOR VERSION 6 OF OUTPATIENT PHARMACY ONLY.  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 2512                            IA #: 2512
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2512
  ID: PSRX(
GLOBAL REFERENCE: PSRX('AD'
 GLOBAL DESCRIPTION:   Cross Reference on fill and refill date fields.  
GLOBAL REFERENCE: PSRX('ADP'
 GLOBAL DESCRIPTION:   Cross Reference on the partial date fi 
GLOBAL REFERENCE: PSRX('AR'
 GLOBAL DESCRIPTION:   Cross Reference on the status field of the CMOP event
 muliple subfile.  This is used to determine whether or not the prescription
 was dispensed by CMOP.  
  
 The above cross references will identify the RX IEN and help obtain the DFN of
 the patient for the particular prescription record.  
  
 The NDC fields and field TPB RX (#201) listed below are not included in the
 supported DBIA 1878.  
GLOBAL REFERENCE: PSRX(
FIELD NUMBER: 2                         FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 27                        FIELD NAME: NDC
  LOCATION: 2;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 201                       FIELD NAME: TPB RX
  LOCATION: TPB;1                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,P,
FIELD NUMBER: 1                         FIELD NAME: NDC
  LOCATION: 0;12                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX('AL'
 GLOBAL DESCRIPTION:   Cross reference on the fields: 
  52,31     Released Date/Time 
GLOBAL REFERENCE: PSRX('AM'
 GLOBAL DESCRIPTION:   Cross reference on the field: 
  52.2,8   Released Date/Time 
GLOBAL REFERENCE: PSRX(D0,1,
FIELD NUMBER: 11                        FIELD NAME: NDC
  LOCATION: 1;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX('AL1'
 GLOBAL DESCRIPTION:   Cross reference on the field:  52.1,17  Released
 Date/Time 
 GENERAL DESCRIPTION:   Pharmacy Benefits Management extracts various data
 elements from the PRESCRIPTION file #52 for a selected time frame. In order to
 obtain the data desired and to use the supported DBIA 1878 provided for
 version 7 of Outpatient Pharmacy access is needed to the following. DBIA 1878 
 requires the DFN and RX IEN, i.e. D EN^PSOORDER(DFN,RX).  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham

NUMBER: 2513                            IA #: 2513
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA2513
  ID: PSRX(
GLOBAL REFERENCE: PSRX('AD'
 GLOBAL DESCRIPTION:   Cross Reference on the fill and refill date fields. This
 X-ref will be used to locate all prescription records filled for a specified
 time range.  
GLOBAL REFERENCE: PSRX(D0,0)
FIELD NUMBER: .01                       FIELD NAME: RX#
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: Patient
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: Patient Status
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: Provider
  LOCATION: 0;4                         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: 8                         FIELD NAME: Days Supply
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: Sig
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: Mail/Window
  LOCATION: 0;11                        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
FIELD NUMBER: 2                         FIELD NAME: Mail/Window
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: Division
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.1                       FIELD NAME: Days supply
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 1.2                       FIELD NAME: Current unit price of drug
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: NDC
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 15                        FIELD NAME: Provider
  LOCATION: 0;17                        ACCESS: Read w/Fileman
FIELD NUMBER: 17                        FIELD NAME: Released date/time
  LOCATION: 0;18                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,2)
FIELD NUMBER: 22                        FIELD NAME: Fill date
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 27                        FIELD NAME: NDC
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 20                        FIELD NAME: Division
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: Released date/time
  LOCATION: 0;13                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,4,D1,0)
FIELD NUMBER: 2                         FIELD NAME: Rx Indicator
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: Status
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: NDC
  LOCATION: 0;8                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX('AR'
 GLOBAL DESCRIPTION:   Cross Reference on the status field of the CMOP event
 multiple. This will be used to determine whether or not a prescription was
 filled by CMOP.  
GLOBAL REFERENCE: PSRX(D0,P,D1,0)
FIELD NUMBER: .01                       FIELD NAME: Partial Date
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: Mail/Window
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: QTY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .09                       FIELD NAME: Division
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: .041                      FIELD NAME: Days supply
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: .042                      FIELD NAME: Current unit Price of drug
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: NDC
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: Provider
  LOCATION: 0;17                        ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: Release date/time
  LOCATION: 0;19                        ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   This cross reference will be used to determine which
 partial prescriptions were filled during a specified time frame.  
GLOBAL REFERENCE: PSRX('AL'
 GLOBAL DESCRIPTION:   Cross Reference on the prescription and refill RELEASED
 DATE/TIME fieldS.  This X-ref will be used to locate all prescription records
 filled for a specified release date time range.  
GLOBAL REFERENCE: PSRX('AM'
 GLOBAL DESCRIPTION:   Cross Reference on the partial RELEASED DATE/TIME field.
 This X-ref will be used to locate all prescription records filled for a
 specified partial release date time range.  
 GENERAL DESCRIPTION:   Pharmacy Benefits Management extracts data elements
 from the PRESCRIPTION file (#52) for a selected time frame. This is for
 version Outpatient Pharmacy V. 6.0 only. 
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
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 EMAIL GROUP 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
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
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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: INTEGRATED BILLING

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
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
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
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
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
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
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
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
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham

NUMBER: 2525                            IA #: 2525
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870
  DATE CREATED: SEP 02, 1998            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: POINTER TO FILE 870
  ID: HLCS(870
GLOBAL REFERENCE: HLCS(870,
FIELD NUMBER: .01                       FIELD NAME: NODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   CIRN would like to store in the CIRN SITE PARAMETER
 file (#991.8) a pointer to the HL LOGICAL LINK file (#870) for the MPI logical
 link.  
  
 In the CIRN SITE PARAMETER file (#991.8), the MPI LINK field (#36) points to
 File #870. The Master Patient Index (MPI) is used to send messages to the MPI
 in Austin.  
  
 IA retired.  See IA 3335 for current documentation.  
  STATUS: Retired
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

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
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 
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
 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
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
  DATE ACTIVATED: APR 13, 2009

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
 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
KEYWORDS: CPTIER
KEYWORDS: COPAY TIER
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^INACTIVE^COPAY TIER 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, CLASS is the five
 character class code for all products associated with the selected drug,
 inactivation date, and COPAY TIER is the IEN for the COPAY TIER multiple (#45)
 of VA Product file (#50.68).  
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: DRGCLS
 COMPONENT DESCRIPTION:   S X=$$DRGCLS^PSNAPIS(IEN) where IEN = (required)
 internal entry number of National Drug Code (NDC) in NDC/UPN file (#50.67).
 Returns CODE (#.01) and PARENT CLASS (#2) from VA DRUG CLASS file (#50.605)
 for a National Drug Code (NDC).  
   X=Drug Class code^Parent Class 
COMPONENT/ENTRY POINT: INTRAN
 COMPONENT DESCRIPTION:   D INTRAN^PSNAPIS(SCR) where SCR = M code for value of
 DIC("S"). Provides input transform lookup functionality for fields that store
 NDC codes. If SCR is not defined, all active entries will be returned.  
   X=NDC field (#1) if input is valid. If no valid input is 
   available, X will be undefined.  
COMPONENT/ENTRY POINT: QLIST
 COMPONENT DESCRIPTION:   D QLIST^PSNAPIS(SCR) where SCR = M code for value of
 DIC("S"). Provides executable help ("?" or "??") for fields that store NDC
 codes. If SCR is not defined, all active entries will be returned.  
   Output: List of selectable codes (NDC field (#1)) 
COMPONENT/ENTRY POINT: CPTIER
 COMPONENT DESCRIPTION:   S X=$$CPTIER^PSNAPIS(VAR1,VAR2,VAR3,VAR4) 
  Where: 
    VAR1 = IEN FOR VA PRODUCT file (#50.68) 
    VAR2 = Date to be verified for Copay Tier 
    VAR3 = IEN for DRUG file (#50) 
    VAR4 = 1 for display or null for billing 
  
 The data returned by this API varies based on the data passed: 
    - VAR1 and/or VAR3 or both can be passed but VAR3 takes 
      precedence.  
  
    - VAR4 equal to 1 indicates that the API will return the 
      stored value for copay tier information to be displayed 
      for options such as Drug Enter/Edit, Lookup into Dispensed 
      Drug file, etc.  
  
    - A null value for VAR4 means the calling application will 
      use the returned information for billing purposes.  The 
      API will return the copay exempt value of 0 (zero) for 
      products with DEA Special Handling field that contains 
      S for Supply Items, I for Investigational Drugs or N for 
      Nutritional Supplement.  The DEA Special Handling 
      supercedes the copay tier field and zero is returned 
      regardless of the copay tier defined on the product.  
  
 The Pharmacy Product System - National (PPS-N) package is used to define copay
 tier information for VA Products.  A check for the DEA Special Handling code
 for the drug/product is an additional check made in Pharmacy to determine if a
 drug is exempt from copay. The copay exempt DEA Special Handling codes are: I
 = Investigational Drug, N = Nutritional Supplement and S for Supply Item.  
  
 Copay Tier determination criteria in order of precedence: 
  
 1. For NDF and PDM display screens (i.e. PSNACT, PSNLOOK, PSSDEE, PSS LOOK),
 this API will return null if the copay tier is not defined or will return the
 defined copay tier for the given date. If the drug is not matched to NDF, null
 is returned. If the tier is null, the selection of drug or product screens 
 will not display the Tier field; however, the body of the display will show
 the Tier and effective date as null.  
  
 2. For billing purposes, this API will return different values based on the
 DEA Special Handling Code and copay tier defined as well as whether the drug
 is matched to NDF.  
  
    a. If the DEA Special Handling Code is exempt from copay and 
       regardless of the copay tier value, this API will return 
       zero. For example, Outpatient Pharmacy (OP) calls this API 
       to determine if a prescription is billable. In this case, 
       the prescription is not billable and would not be sent to 
       IB for a copay charge. The DEA Special Handling Code 
       overrides the nationally defined copay tier.  
  
    b. The product is matched to NDF: 
       -  If the copay tier is 1, 2, or 3 and the DEA code is NOT 
          exempt from copay, this API will return the defined 
          copay tier. For example, OP would send the prescription 
          to IB for a copay charge.  
  
       -  If the copay tier is 0 (zero), this API will return 0 
          (zero).  For example, OP would not would not send the 
          prescription for copay billing charges.  
  
       -  If no copay tier is defined and the product is NOT 
          exempt from copay, this API will return null. For 
          example, OP would send the prescription to IB to 
          charge copay.  
  
    c. The product is not matched to NDF: 
       -  If the DEA special handling code is NOT exempt from 
          copay, this API will return null. For example, OP 
          would send the prescription to IB to charge copay.  
VARIABLES: VAR1                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN FOR VA PRODUCT file (#50.68) 
VARIABLES: VAR2                         TYPE: Input
 VARIABLES DESCRIPTION:   Date to be verified for Copay Tier 
VARIABLES: VAR3                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN for DRUG file (#50) 
VARIABLES: VAR4                         TYPE: Input
 VARIABLES DESCRIPTION:   VAR4 equal to 1 indicates that the API will return
 the stored value for copay tier information to be displayed for options such
 as Drug Enter/Edit, Lookup into Dispensed Drug file, etc.  
  
 A null value for VAR4 means the calling application will use the returned 
 information for billing purposes.  The API will return the copay exempt value
 of 0 (zero) for products with DEA Special Handling field that contains S for
 Supply Items, I for Investigational Drugs or N for Nutritional Supplement. 
 The DEA Special Handling supercedes the copay tier field and zero is returned
 regardless of the copay tier defined on the product.   
VARIABLES: TIER                         TYPE: Output
 VARIABLES DESCRIPTION:   COPAY TIER LEVEL field (#.01) from VA PRODUCT file
 (#50.68) 
VARIABLES: EFFECTIVE DATE               TYPE: Output
 VARIABLES DESCRIPTION:   EFFECTIVE DATE field (#1) from VA PRODUCT file
 (#50.68) 
VARIABLES: END DATE                     TYPE: Output
 VARIABLES DESCRIPTION:   End Date field (#2) from VA PRODUCT field  (#50.68) 
COMPONENT/ENTRY POINT: CMOP
 COMPONENT DESCRIPTION:   S X=$$CMOP^PSNAPIS(CODE) Returns the 5 character NAME
 field (#.01) for the VA PRODUCT file (#50.68) where CODE = 5-character CMOP
 ID. Returns $$CMOP equals corresponding VA Product Name if the CODE is valid
 or null if the CODE is not valid.  
  DATE ACTIVATED: FEB 13, 2017

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
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
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 - DECISION SUPPORT SYSTEM 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
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: MYHEALTHEVET
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/3/24 effective with patch DSSO*2.0*8 to
 support the determination of which Divisions the user is assigned to.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 10/3/24 effective with patch DSIY*1.5*6 to
 support the determination of which Divisions the user is assigned to.  

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
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
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
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.  

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 
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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
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
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 2540                            IA #: 2540
  DATE CREATED: SEP 21, 1998            CUSTODIAL PACKAGE: 1
  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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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
COMPONENT/ENTRY POINT: $$GET
 COMPONENT DESCRIPTION:   The call is $$GET^XUPARAM(<parameter name>[,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: 1
  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
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
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
FIELD NUMBER: .02                       FIELD NAME: REACTANT
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
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.  
  
 Amended August 2022: Patch PSN*4.0*574 needs access to the REACTANT (#.02)
 field. A correction is needed which was caused by an erroneous NDC/UPN
 (#50.67) file entry for "COFLEX". (See patch description for more 
 information.) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
 SUBSCRIBING DETAILS:   
  
  DATE ACTIVATED: AUG 29, 2022

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  STATUS: Active
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:   <pointer>  Outpatient Encounter IEN for first
 standalone encounter 
            found in date range <null>     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:   <pointer>  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:   <pointer>  Outpatient Encounter ID for first
 encounter found in date range <null>     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:   <pointer>  Outpatient Encounter ID for last
 standalone encounter found 
            after date <null>     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
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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  STATUS: Active
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:   <number>  count of records in query's result set 0    
     no records in the query's result set <null>    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:   <pointer>  ID for entry <null>     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: 2549                            IA #: 2549
  FILE NUMBER: 66                       GLOBAL ROOT: LAB(
  DATE CREATED: SEP 22, 1998            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: DBIA2549                        ID: LAB(
 GENERAL DESCRIPTION:   Direct global read of BLOOD PRODUCTS (#66).  The codes
 uses NAME(#.01) and PRODUCT CODE(#.05).  
  STATUS: Pending

NUMBER: 2550                            IA #: 2550
  GLOBAL ROOT: LAB(65.4                 DATE CREATED: SEP 22, 1998
  CUSTODIAL PACKAGE: LAB SERVICE        USAGE: Private
  TYPE: File                            NAME: DBIA2550
  ID: LAB(65.4
 GENERAL DESCRIPTION:   Direct global read of BLOOD BANK UTILITY(#65.4) The
 code uses FULLNAME(#.03) 
  STATUS: Pending

NUMBER: 2551                            IA #: 2551
  FILE NUMBER: 60                       GLOBAL ROOT: LAB(
  DATE CREATED: SEP 22, 1998            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: DBIA2551                        ID: LAB(
 GENERAL DESCRIPTION:   Direct global read of LABORATORY TEST File(#60) The
 code uses LOCATION(DATA NAME)(#5), ASK AMIS/CAP CODES(#501) TYPE(#3) and
 FIELD(#13) 
  STATUS: Pending

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  STATUS: Active
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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  
  STATUS: Active

NUMBER: 2562                            IA #: 2562
  FILE NUMBER: 2                        GLOBAL ROOT: DPT
  DATE CREATED: SEP 22, 1998            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: DBIA2562                        ID: DPT
 GENERAL DESCRIPTION:   Direct of PATIENT file(#2) Direct global read of "LR"
 node. The code uses LABORATORY REFERENCE(#63) 
  STATUS: Pending

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
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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  STATUS: Active

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
 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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  STATUS: Active                        DATE ACTIVATED: APR 10, 2012
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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  STATUS: Active

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://127.0.0.1/softserv/mip/wr/acrpapi.htm 
  STATUS: Active

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
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.  
COMPONENT/ENTRY POINT: $$PGX(PSNPGX1,PSNPGX3)
 COMPONENT DESCRIPTION:   This entry point returns PGx information for a VA
 Product.  
VARIABLES: PSNPGX1                      TYPE: Input
 VARIABLES DESCRIPTION:   Not processed 
VARIABLES: PSNPGX3                      TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number from the VA PRODUCT (#50.68)
 file used to retrieve PGx specific information for a selected VA product.  
VARIABLES: $$PGX                        TYPE: Output
 VARIABLES DESCRIPTION:   Q "PGX ELIGIBLE (#46)^PGX SUPRESSED (#47)" 
COMPONENT/ENTRY POINT: PGXING(PSNING1,PSNING3,PSNLST)
 COMPONENT DESCRIPTION:   This entry point returns PGx information for a VA
 Product and its associated drug ingredient(s).  
VARIABLES: PSNING1                      TYPE: Input
 VARIABLES DESCRIPTION:   Not processed.  
VARIABLES: PSNING3                      TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number from the VA PRODUCT (#50.68)
 file used to retrieve PGx specific information for a selected VA product and
 its associated drug ingredient(s).  
VARIABLES: PSNLST()                     TYPE: Output
 VARIABLES DESCRIPTION:   From the VA PRODUCT (#50.68) file: 
 PSNLST("PROD")="PGX ELIGIBLE (#46)^PGX SUPPRESSED (#47)" 
  
 From the DRUG INGREDIENTS (#50.416) file: PSNLST("ING",IEN)="NAME (#.01)^PGX
 ELIGIBLE (#5)^PGX SUPPRESSED (#6)" 
  DATE ACTIVATED: APR 15, 2025

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
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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
  DATE ACTIVATED: JAN 05, 2011

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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP*2.0*2 
  
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************

NUMBER: 2579                            IA #: 2579
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDAM
  NAME: SDAM                            ID: SDAM
 GENERAL DESCRIPTION:   The [HBHC APPOINTMENT] OPTION CALLS ROUTINE SDAM, USING
 ENTRY POINT EN.  This is IA is needed due to cloning the [SDAM APPT MGT]
 option.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
SUBSCRIBING PACKAGE: HOME BASED PRIMARY CARE
  ISC: Hines
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Hines
 SUBSCRIBING DETAILS:   The Prosthetic Suspense Utility routine RMPRS, makes a
 call to EN^SDAM each time the user exits Suspense Processing.  RMPRS is called
 with every Prosthetic action taken to issue an item or service to a Patient. 
 This includes just about every menu option available within Prosthetics.  

NUMBER: 2580                            IA #: 2580
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDAMEVT
  NAME: SDAMEVT                         ID: SDAMEVT
 GENERAL DESCRIPTION:   THE [HBHC APPOINTMENT] OPTION CALLS ROUTINE SDAMEVT IN
 ITS EXIT ACTION USING ENTRY POINT HDKILL.  
  
 This is IA is needed due to cloning the [SDAM APPT MGT] option.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: HDKILL
SUBSCRIBING PACKAGE: HOME BASED PRIMARY CARE
  ISC: Hines

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
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Washington/Silver Spring

NUMBER: 2582                            IA #: 2582
  FILE NUMBER: 63                       DATE CREATED: SEP 28, 1998
  CUSTODIAL PACKAGE: LAB SERVICE        USAGE: Private
  TYPE: File                            NAME: DBIA2582
 GENERAL DESCRIPTION:   The Electron Microscopy (LAB) performs real time data
 extraction using routine ^RGHOPATH for CIRN. The routine performs the
 following databases function: 
  
 Direct global read of the LAB DATA file (#63) and PARENT FILE field (#.02).  
 Direct global read on the LAB DATA file (#63), NAME field (#.03).  Direct
 global read of the zero node of the SP, CY, and EM subscripts in the LAB DATA
 file (#63).  Direct global read using a $O through the EM subscript nodes .1
 through .2 "EM" subscript includes:  .1 node 63.202 Specimen subfile, .2 node
 63.213 Brief Cliical History Subfile, .3 node 63.214 Preoperative Diagnosis
 subfile .4 node 63.205 Operative Findings subfile, .5 node 63.206
 Postoperative Diagnosis subfile, 1 node 63.201 Gross Description subfile, 1.1
 node 63.211 Microsopic Examination subfile, 1.2 node 63.207 Supplementary
 Report, 1.4 node 63.204 EM Diagnosis subfile, 2 node 63.212 EM Organ/Tissue
 subfile 
  STATUS: Pending
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

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 Read Access 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'
GLOBAL REFERENCE: GMR(123,DA,'UCID')
FIELD NUMBER: 80                        FIELD NAME: UNIQUE CONSULT ID
  LOCATION: UCID;1                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: GMR(123,DA,1
FIELD NUMBER: 1.01                      FIELD NAME: CLINICAL PROCEDURE
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: GMR(123,DA,12
FIELD NUMBER: .126                      FIELD NAME: REMOTE ORDERING PROVIDER
  LOCATION: 12;6                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This DBIA serves as documentation of Read Access 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,.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   added 5/26/2011 
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Added 11/6/19 for access to UNIQUE CONSULT ID (field 80
 or GMR(123,DA,'UCID') global reference, effective with RA*5*161.  
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI
 SUBSCRIBING DETAILS:   Added 9/5/24 effective with DSIR*8.2*16, in order to
 read patient name field for a given patient in the REQUEST/CONSULTATION file
 (#123) field .02 PATIENT NAME using FILEMAN,using ORQQCN LIST to get the
 consult IENs.  I $$GET1^DIQ(123,DSIRCHK_",",.02,"I") 
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   
  Added 10/1/24 effective with Patch MECH*1.0*1, a Class 2 product, requires
 Read w/FileMan access to File 123, REASON FOR REQUEST (#20) and CLINICAL
 PROCEDURE (#1.01) to gather data related to a Radiology order. The Medicom
 ImageX app processes HL7 messages about imaging studies performed in the
 community but might not be entered through VistA. The Medicom app sends a HL7
 query to gather all existing orders for a specific patient in order to
 determine if they 'reconcile' the imaging study. The MECH code utilizes
 OER^GMRCSLM1, GMRCACN^MAGDFCNV, and RAPTREG^RAMAGU04 to determine if the
 patient has any existing Radiology or Consults on file and if found gathers
 data about the orders and VistA then sends the data, via HL7, back to the
 Medicom app.  The presence of this Class 2 subscribers shall not prevent
 modifications to the underlying artifact.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Added 9/4/24, effective with patch TIU*1.0*369,
 requires access to the REMOTE ORDERING PROVIDER, field .126 as part of the
 Copy/Paste Tracking Report. Patch 369 corrects ICR reference for ^GMR data
 access introduced by TIU*1.0*290.  
  DATE ACTIVATED: APR 25, 2019

NUMBER: 2587                            IA #: 2587
  FILE NUMBER: 75.1                     GLOBAL ROOT: RAO(75.1,
  DATE CREATED: SEP 25, 1998
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: OE/RR references to RAO(75.1,
  ID: RAO(75.1,
GLOBAL REFERENCE: RAO(75.1,DA,0)
FIELD NUMBER: 2                         FIELD NAME: PROCEDURE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: CATEGORY OF EXAM
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: REQUEST STATUS
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: REQUEST URGENCY
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: CONTRACT/SHARING SOURCE
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 12                        FIELD NAME: PRE-OP SCHEDULED DATE/TIME
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 13                        FIELD NAME: PREGNANT
  LOCATION: 0:13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 19                        FIELD NAME: MODE OF TRANSPORT
  LOCATION: 0;19                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 20                        FIELD NAME: IMAGING LOCATION
  LOCATION: 0;20                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 21
  FIELD NAME: DATE DESIRED (Not guaranteed)
  LOCATION: 0;21                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: RAO(75.1,DA,'M',
FIELD NUMBER: 125                       FIELD NAME: MODIFIERS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: RAO(75.1,DA,'R')
FIELD NUMBER: 9.5                       FIELD NAME: RESEARCH SOURCE
  LOCATION: R;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The references in this DBIA are made from the OE/RR v3
 orders conversion.only! 
  
 Please note in addition to the fields referenced, the following code is also
 executed: 
  
 I '$D(^RADPT("AO",+ORPK)) S DA=+ORPK,DIK="^RAO(75.1," D ^DIK 
  
 So, if no entries in the RAD/NUC MED PATIENT FILE file, point to the processed
 entry in the RAD/NUC MED ORDERS file, the entry is deleted.  
  STATUS: Retired                       DURATION: Next Version
  EXPIRATION DATE: FEB 15, 2007         GOOD ONLY FOR VERSION: OE/RR v3
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 2588                            IA #: 2588
  FILE NUMBER: 70                       GLOBAL ROOT: RADPT(
  DATE CREATED: SEP 25, 1998
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  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
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 9/27/18 for VPR*1*8, to use the AO index to
 determine the case number from an order (for use in the supported RAO7PC1
 api's).  

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
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
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: 2591                            IA #: 2591
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDGAF
  NAME: SD OUTPATIENT ENCOUNTER GAF SCORE CAPTURE
  ID: SDGAF
 GENERAL DESCRIPTION:   Patient Care Encounter needs to capture GAF scores for
 outpatient encounters.  This call will allow entry of the GAF score, Date/Time
 of the GAF score, and provider determining the GAF score through the
 Scheduling call used in appointment management.  The internal entry number of
 the patient, DFN, is passed into the call as variable DFN.  There is no return 
 from the call.  This call will ask for the score, date/time, and provider for
 posting the GAF score.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN(DFN)
 COMPONENT DESCRIPTION:   Patient Care Encounter needs to capture GAF scores
 for outpatient encounters.  This call will allow entry of the GAF score,
 Date/Time of the GAF score, and provider determining the GAF score through the
 Scheduling call used in appointment management.  The internal entry number of
 the patient, DFN, is passed into the call as variable DFN.  There is no return 
 from the call.  This call will ask for the score, date/time, and provider for
 posting the GAF score.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Contains the internal entry number of the patient in
 the PATIENT File, #2.  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany

NUMBER: 2592                            IA #: 2592
  DATE CREATED: SEP 30, 1998            CUSTODIAL PACKAGE: 1
  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
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 2593                            IA #: 2593
  DATE CREATED: APR 23, 1999            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  ROUTINE: LRRGHOMI                     NAME: DBIA2593
  ID: LRRGHOMI
 GENERAL DESCRIPTION:   The CIRN data extaction routine for Microbiology (LAB)
 ^LRRGHOMI makes several references to the LAB DATA file (#63) in order to
 generate the HL7 message for Microbiology results.  This routine is called
 from ^RGHOMI.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CALL1
 COMPONENT DESCRIPTION:   Gets some initial patient details.  
VARIABLES: RGSTUB                       TYPE: Input
 VARIABLES DESCRIPTION:   Event Stub 
VARIABLES: RGLRD                        TYPE: Output
 VARIABLES DESCRIPTION:   ^LR global pointer 
VARIABLES: RGLRI                        TYPE: Output
 VARIABLES DESCRIPTION:   Inverse date/time for test 
VARIABLES: RGZ                          TYPE: Output
 VARIABLES DESCRIPTION:   $piece 2 of RGZ is the PARENT FILE, and $piece  3 of
 RGZ is the NAME. Both come from the ^LR(RGLRD,0) node.  
COMPONENT/ENTRY POINT: CALL2
 COMPONENT DESCRIPTION:   Gets details from ^LR(RGLRD,"MI",RGLRI,0) node. RGLRD
 and RGLRI are inputs.  
VARIABLES: RGZ                          TYPE: Output
 VARIABLES DESCRIPTION:   $Piece 1 is DATE/TIME SPECIMEN, $Piece 5 is
 SITE/SPECIMEN, $Piece 6 is the ACCESSION ID, $Piece 7 is the PHYSICIAN.  
COMPONENT/ENTRY POINT: CALL3
 COMPONENT DESCRIPTION:   Inputs are same as for CALL2. This call creates the
 HL7 message which is subsequently processed further by the calling routine
 ^RGHOMI. The following Microbiology Result details are accessed from various
 ^LR nodes to be transmitted in the HL7 me ssage : ORGANISM, QUANTITY ; BACT
 RPT REMARK ; PARASITE ; STAGE, QUAN TITY ; COMMENT ; PARASITE RPT REMARK ;
 FUNGUS/YEAST, QUANTITY ; MICOLOGY RPT REM ; ACID FAST STAIN, QUANTITY ;
 MYCOBACTERIUM, QUANTITY ; TB RPT REMARK ; ANTIBIOTIC (for SERUM) ,  DRAW TIME,
 CONC (ug/ml) 
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 2594                            IA #: 2594
  FILE NUMBER: 60                       GLOBAL ROOT: LAB
  DATE CREATED: OCT 16, 1998            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: DBIA2594                        ID: LAB
GLOBAL REFERENCE: LAB(60,D0,0)
FIELD NUMBER: 3                         FIELD NAME: TYPE
  LOCATION: 0,3                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: LOCATION (DATA NAME)
  LOCATION: 0,5                         ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: FIELD
  LOCATION: 0,12                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   For all CIRN Laboratory related packages, including:
 MICROBIOLOGY and SURGICAL PATHOLOGY, the historical load routine (^RGHOLABB -
 Historical load of lab results (all modules)), makes a reference to the
 LABORATORY TEST file (#60), for the purpose of setting an entry in the CIRN 
 processing queue.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 2595                            IA #: 2595
  FILE NUMBER: 61                       GLOBAL ROOT: LAB
  DATE CREATED: MAY 25, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: DBIA2595                        ID: LAB
GLOBAL REFERENCE: LAB(61,D0,0)
FIELD NUMBER: 2                         FIELD NAME: SNOMED CODE
  LOCATION: 0,2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   For all CIRN Laboratory related packages, including:
 MICROBIOLOGY and SURGICAL PATHOLOGY, the historical load routine (^RGHOLABB -
 Historical load of lab results (all modules)), makes a reference to the
 TOPOGRAPHY FIELD file (#61), for the purpose of setting an entry in the CIRN 
 processing queue.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

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
SUBSCRIBING PACKAGE: 1                  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
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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 5/17/21 The Advanced Prosthetics Acquisition Tool
 (APAT) needs to read the VISIT (#9000010) file using FileMan when extracting
 the internal value of the VISIT/ADMIT DATE&TIME (field #.01).  

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
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: Controlled Subscription        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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI
 SUBSCRIBING DETAILS:   Added 9/11/24 effective with patch DSIR*8.2*16 in order
 to read patient name field  for a given patient in the immunization file
 (#9000010.11) field .02 PATIENT NAME using FILEMAN. I
 $$GET1^DIQ(9000010.11,DSIRCHK_",",.02,"I")) 

NUMBER: 2601                            IA #: 2601
  DATE CREATED: OCT 16, 1998            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  ROUTINE: LRRGPATH                     NAME: DBIA2601
  ID: LRRGPATH
 GENERAL DESCRIPTION:   The CIRN data extraction routine ^LRRGPATH creates the
 HL7 messages for Surgical Pathology, Electron Microscopy and Cytology (eg LAB
 transfers). It makes several references to the LAB DATA file (#63) in order to
 create the messages.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CALL1
 COMPONENT DESCRIPTION:   CALL1 gets some initial patient details.  
VARIABLES: LRRGD                        TYPE: Input
 VARIABLES DESCRIPTION:   1st subscript of ^LR 
VARIABLES: LRRGDC                       TYPE: Input
 VARIABLES DESCRIPTION:   3rd subscript of ^LR. Data Class (SP, CY or EM).  
VARIABLES: LRRGI                        TYPE: Input
 VARIABLES DESCRIPTION:   4th subscript of ^LR (piece 2 of event stub).  
VARIABLES: LRRGPAT                      TYPE: Output
 VARIABLES DESCRIPTION:   PARENT FILE 
VARIABLES: LRRGODAT                     TYPE: Output
 VARIABLES DESCRIPTION:   DATA/TIME SPECIMEN TAKEN 
VARIABLES: LRRGFON                      TYPE: Output
 VARIABLES DESCRIPTION:   SURGICAL PATH ACCESSION 
VARIABLES: LRRGPRV                      TYPE: Output
 VARIABLES DESCRIPTION:   SURGEON/PHYSICIAN 
COMPONENT/ENTRY POINT: CALL2
 COMPONENT DESCRIPTION:   Inputs are same as for CALL1. This call creates the
 HL7 message which is subsequently processed further by the calling routine 
 ^RGHOPATH.  The following LAB details are accessed from various ^LR nodes to
 be transmitted in the HL7 message : CLINICAL HISTORY (Sub file # 63.813),
 PREOPERATIVE DIAGNOSIS (#63.814), OPERATIVE FINDINGS (#63.815), POSTOPERATIVE
 DIAGNOSIS (#63.816), GROSS DESCRIPTION (#63.81) MICROSCOPIC DESCRIPTION
 (#63.811), FROZEN SECTION (#63.801), SURGICAL PATH DIAGNOSIS (#63.802),
 ETIOLOGY (#63.217) 
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 2602                            IA #: 2602
  FILE NUMBER: 1.1                      GLOBAL ROOT: DIA
  DATE CREATED: OCT 02, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: READING AUDIT FILE              ID: DIA
GLOBAL REFERENCE: DIA(File number,entry number
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 
GLOBAL REFERENCE: 'B'
 GLOBAL DESCRIPTION:   Direct read access to the 'B' 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
KEYWORDS: AUDIT
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.  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Effective with patch PX*1*215, Patient Care Encounter
 will check the 'C' cross-reference to determine if any information in their
 files have been updated since a given date.  This will allow PCE to quickly
 determine if their cached data is out of date.  The following files are
 audited and locked down by STS: 
     #920        VACCINE INFORMATION STATEMENT 
     #920.1      IMMUNIZATION INFO SOURCE 
     #920.2      IMM ADMINISTRATION ROUTE 
     #920.3      IMM ADMINISTRATION SITE (BODY) 
     #920.4      IMM CONTRAINDICATION REASONS 
     #920.5      IMM REFUSAL REASONS 
     #9999999.04 IMM MANUFACTURER 
     #9999999.14 IMMUNIZATION 
     #9999999.28 SKIN TEST 
  
  If more information is needed from the AUDIT file, PCE will use documented 
 FileMan APIs to retrieve that information.  
  
 Effective with patch PX*1*216, Patient Care Encounter (PCE) will look at the 
 audit data for the V IMMUNIZATION file (#9000010.11) to reconstruct how a 
 record existed at a given point in time. PCE will use the 'B' cross-reference 
 to quickly find all audit entries for a given V IMMUNIZATION record, and will 
 then access those audits, using the approved methods in this ICR, to determine 
 what changed.  
  
  
  
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   The VistA Imaging application, with the release of
 MAG*3.0*183, is looking to identify when the Social Security Number (SSN) is
 changed in a patient record in the PATIENT (#2) file. The old SSN value and
 the new SSN value is broadcast in HL7 messages to keep the subscribers of
 those HL7 messages current with patient demographic and patient identifier
 changes.  
  
 The lookup works as follows: For a known patient (file of interest: PATIENT
 #2) we look through the "B" cross-reference of the AUDIT file looking for
 Social Security Number (SSN) changes. When we find a SSN change, we note the
 DATE/TIME RECORDED (field: .02; node: 0; piece: 2), the old SSN value from
 ^DIA(2,DFN,2) computed and the new SSN value from ^DIA(2,DFN,3) also computed. 
 
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   Added 04/09/21, effective with XU*8.0*743 in support of
 the ongoing Enterprise User Identity Work of the Master Veteran Index (MVI)
 team. This IA (#2602) in combination with IA (#7244) will allow MVI to
 retrieve the Audit Information for display for a given patient's DUZ.  
  DATE ACTIVATED: FEB 05, 2016

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
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
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
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham

NUMBER: 2607                            IA #: 2607
  DATE CREATED: OCT 14, 1998            CUSTODIAL PACKAGE: 1
  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
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: 1
  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
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: 1
  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
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: 1
  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
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
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: PHARMACY DATA MANAGEMENT
  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:   As of 9/1/20 the ICR Team were requested to change the
 custodial package to Pharmacy Data Management, instead of Inpatient 
 Medications. This resulted from the alignment of file ranges under specific
 packages for the conversions from Rational to GitHub.  
  
 Actual Description from prior to 9/1/20: 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 
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: SEP 01, 2020
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
  ISC: Birmingham
  DATE ACTIVATED: SEP 01, 2020

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,
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
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
  ISC: Birmingham
  DATE ACTIVATED: OCT 04, 2010

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
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
  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
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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 8/5/2025, the middleware product, Veterans Data
 Integration and Federation Enterprise Platform (VDIF-EP), will read fields in
 the VISIT file to support the VCRS-HINGE project to retrieve a patient's visit 
 information.  

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
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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 2621                            IA #: 2621
  FILE NUMBER: 59                       GLOBAL ROOT: PS(59
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA2621
  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 NUMBER: .02                       FIELD NAME: MAILING FRANK STREET ADDRESS
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: MAILING FRANK ZIP+4 CODE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: MAILING FRANK CITY
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: MAILING FRANK STATE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES

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
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
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
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: 2625                            IA #: 2625
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19,
  DATE CREATED: OCT 22, 1998            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: PACKAGE POINTER UPDATES
  ID: DIC(19,
GLOBAL REFERENCE: DIC(19,D0,0)
FIELD NUMBER: 12                        FIELD NAME: PACKAGE
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   
  
  In order to complete all corrections to the Package File #9.4 
  referenced in DBIA #2489, we would like to have permission to check 
  and update any Library Package Options stored in the Option File #19.  
  To locate the Library v.2.5 patches, we would like to use FIND^DIC and 
  extract the entries' corresponding data in their PACKAGE(12) field.  
  If the entry is not pointing to the correct Library Package File 
  entry, we would like to update this field with the correct pointer 
  using FILE^DIE.  Error checking for each check and update will be 
  performed. 
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LIBRARY            ISC: Albany

NUMBER: 2626                            IA #: 2626
  FILE NUMBER: 9.6                      GLOBAL ROOT: XPD(9.6,
  DATE CREATED: OCT 22, 1998            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: PACKAGE FILE LINK UPDATES
  ID: XPD(9.6,
GLOBAL REFERENCE: XPD(9.6,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PACKAGE FILE LINK
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   
  
  In order to complete all corrections to the Package File #9.4 
  referenced in DBIA #2489, we would like to have permission to check 
  and update any Library Package KIDS builds stored in the Build File 
  #9.6.  To locate the Library v.2.5 patches, we would like to use 
  FIND^DIC and extract the entries' corresponding data in their PACKAGE 
  FILE LINK(1) field.  If the entry is not pointing to the correct 
  Library Package File entry, we would like to update this field with 
  the correct pointer using FILE^DIE.  Error checking for each check and 
  update will be performed. 
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LIBRARY            ISC: Albany

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
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
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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
 TO GENERATE HL7 PRESCRIPTION MESSAGING.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham

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                            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.  
GLOBAL REFERENCE: RADPT(DO,'DT,'D1,0)
FIELD NUMBER: .01                       FIELD NAME: EXAM DATE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the exam date of the patient radiology procedure. 
  
 GLOBAL DESCRIPTION:   DO is the patient DFN. D1 is the inverse date/time of
 the radiology procedure.  
  
GLOBAL REFERENCE: RADPT(DO,'DT',D1,'P',D2,0)
FIELD NUMBER: .01                       FIELD NAME: CASE NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the computer generated case number of
 the patient radiology exam.  
  
 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: Under Revision                DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 2631                            IA #: 2631
  GLOBAL ROOT: DD(                      DATE CREATED: OCT 27, 1998
  CUSTODIAL PACKAGE: 1                  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
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
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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 2634                            IA #: 2634
  FILE NUMBER: 74                       GLOBAL ROOT: RARPT
  DATE CREATED: OCT 27, 1998
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA2634
  ID: RARPT
GLOBAL REFERENCE: RARPT(D0,0)
FIELD NUMBER: .01                       FIELD NAME: DAY-CASE#
  LOCATION: 0,1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: PATIENT NAME
  LOCATION: 0,2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: EXAM DATE/TIME
  LOCATION: 0,3                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: REPORT STATUS
  LOCATION: 0,5                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: VERIFIED DATE
  LOCATION: 0,7                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RARPT(D0,H,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CLINICAL HISTORY
  LOCATION: 0,1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RARPT(D0,I,D1,0)
FIELD NUMBER: .01                       FIELD NAME: IMPRESSION TEXT
  LOCATION: 0,1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RARPT(D0,R,D1,0)
FIELD NUMBER: .01                       FIELD NAME: REPORT TEXT
  LOCATION: 0,1                         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), makes several references to radiology/nuclear related
 nodes/fields in the RAD/NUC MED REPORTS file (#74), for the purpose of
 creating the HL7 transmission records.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
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
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
SUBSCRIBING PACKAGE: DIETETICS          ISC: Hines

NUMBER: 2637                            IA #: 2637
  DATE CREATED: OCT 29, 1998
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: RGUTDT
  NAME: CIRN DATE/TIME CONVERSION/FORMAT
  ID: RGUTDT
 GENERAL DESCRIPTION:   This DBIA concerns a call to a CIRN utility routine to
 convert and format date/times.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$ENTRY
 COMPONENT DESCRIPTION:   $$ENTRY^RGUTDT(DAT,OPT) 
VARIABLES: DAT                          TYPE: Input
 VARIABLES DESCRIPTION:   A date/time in internal VA FileMan or $HOROLOG
 format.  Defaults to the current date/time if not passed in.  
VARIABLES: OPT                          TYPE: Input
 VARIABLES DESCRIPTION:   A list of option flags used to control the conversion
 process.  Defaults to 0000 if not passed in.  
  
  xxx0 - dd-mmm-yyyy 
  xxx1 - mmm dd,yyyy 
  xxx2 - mm/dd/yyyy 
  xxx3 - mm-dd-yyyy 
  xx0x - hh:mm 
  xx1x - hh:mm xx 
  x0xx - Use space to separate date/time 
  x1xx - Use @ to separate date/time 
  0xxx - Allow leading zeros 
  1xxx - Remove leading zeros 
VARIABLES: RETURN VALUE                 TYPE: Output
 VARIABLES DESCRIPTION:   The external form of the date/time specified by DAT,
 formatted as specified by OPT.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

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) 
  
 This also allows for direct read of the "B" index to determine the list of 
 possible statuses.  
  
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] ^ ^ORD(100.01,"B",STATUS,D0) 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 11/10/2022, effective with DSSV 1.1 DSS Class 2 
 product Document Only DSSV is using field .1 ABBREVIATION 
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   Added 2/4/2026, effective with MAG*3.0*362 Using Direct
 Global Read to access the 'B' cross reference 
  DATE ACTIVATED: MAR 24, 2020

NUMBER: 2639                            IA #: 2639
  DATE CREATED: OCT 29, 1998
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: RGOBJ
  NAME: CIRN CLASS NAME INTERNAL TO EXTERNAL
  ID: RGOBJ
 GENERAL DESCRIPTION:   This DBIA concerns a call to a CIRN utility routine to
 return the name associated with a specified class.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$NAME
 COMPONENT DESCRIPTION:   $$NAME^RGOBJ(CLS,TYP) 
VARIABLES: CLS                          TYPE: Input
 VARIABLES DESCRIPTION:   A pointer to the CIRN Object Dictionary (#990.9).  
VARIABLES: TYP                          TYPE: Input
 VARIABLES DESCRIPTION:   An option flag to specify the type of class name to
 return.  Defaults to 1 if not passed in.  
  
  1 - Preferred/Primary 
  A - Adjectival 
  B - Brief 
  P - Plural 
VARIABLES: RETURN VALUE                 TYPE: Output
 VARIABLES DESCRIPTION:   The external form of the class name specified by CLS
 and TYP.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

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
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

NUMBER: 2642                            IA #: 2642
  FILE NUMBER: 0                        GLOBAL ROOT: DD(
  DATE CREATED: NOV 12, 1998            CUSTODIAL PACKAGE: 1
  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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
GLOBAL REFERENCE: DPT(D0,INS)
FIELD NUMBER: 2001                      FIELD NAME: DATE LAST EICD RUN
  LOCATION: INS;1                       ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This field contains the date that the last EICD
 Identification inquiry was transmitted to the Financial Services Center (FSC) 
 GLOBAL DESCRIPTION:   INSURANCE - NON-POLICY INFO             Direct Global
 R/W & w/Fileman This node references the INSURANCE - NON-POLICY INFO for each
 patient. Fields related to non-policy related insurance will be stored on this
 node.  
 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.
 In addition the INS node references the INSURANCE - NON-POLICY INFO for each 
 patient. Fields related to non-policy related insurance will be stored on this
 node. 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
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
  DATE ACTIVATED: JUN 07, 2018

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
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: 2645                            IA #: 2645
  DATE CREATED: NOV 17, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         ROUTINE: DIOZ
  NAME: Classic FileMan API: Sort Template Compliation
  ID: DIOZ
 GENERAL DESCRIPTION:   This entry point marks a sort template compiled or
 uncompiled.  
  STATUS: Withdrawn
COMPONENT/ENTRY POINT: DIOZ
 COMPONENT DESCRIPTION:   The ^DIOZ entry point asks for the name of the sort
 template to be used, and whether the user wishes (1) to mark it compiled or
 (2) to uncompile it if it is already marked compiled. 
VARIABLES: None

NUMBER: 2646                            IA #: 2646
  DATE CREATED: NOV 18, 1998
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: RGDDHS03
  NAME: CIRN HEALTH SUMMARY DATA EXTRACTS
  ID: RGDDHS03
 GENERAL DESCRIPTION:   This DBIA concerns a calls to two CIRN Health Summary
 extract entry points.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EXTRACT
 COMPONENT DESCRIPTION:   D EXTRACT^RGDDHS03(DFN,[.]CLS,BEG,END,MAX,[.]INS) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   A pointer to the Patient file (#2).  
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: 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: MAX                          TYPE: Input
 VARIABLES DESCRIPTION:   The maximum number of occurrences that should be
 extracted.  
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: RETUTN VALUE                 TYPE: Output
 VARIABLES DESCRIPTION:   The output of this call is in the ^TMP("RGHS",$J,
 global.  
COMPONENT/ENTRY POINT: GETNARTX
 COMPONENT DESCRIPTION:   D GETNARTX^RGDDHS03(IEN,WPL,WPR) 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   A pointer to the CIRN Narrative file (#990.2).  
VARIABLES: WPL                          TYPE: Input
 VARIABLES DESCRIPTION:   The left margin for the text (default = 1).  
VARIABLES: WPR                          TYPE: Input
 VARIABLES DESCRIPTION:   The right margin for the text (DEFAULT = 80).  
VARIABLES: RETURN VALUE                 TYPE: Output
 VARIABLES DESCRIPTION:   The CIRN Narrative word processing text wrapped in
 the margins specified by the user.  The text is returned in
 ^UTILITY($J,"W",WPL,#,0) = Text (same format as the DIWP call in VA FileMan).  
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

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
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: 1
  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
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: 1
  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
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
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
  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
SUBSCRIBING PACKAGE: SURGERY            ISC: Birmingham
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be referencing the Name (#.01) field in the
 Specialty (#42.4) file in VIAB BMS RPC.  

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
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. 
  
 CIRN needs a read access to the PSDRUG (file #50) to generate HL7 prescription
 messaging 
  STATUS: Retired                       EXPIRATION DATE: JUN 01, 2006
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
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
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
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 
  

NUMBER: 2658                            IA #: 2658
  GLOBAL ROOT: DD(2260,0,'ID'           DATE CREATED: DEC 10, 1998
  CUSTODIAL PACKAGE: 1                  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
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",<ien>,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
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',<appt data/time>,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',<inverse log date/time>,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
COMPONENT/ENTRY POINT: PXKNOEVT
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 2661                            IA #: 2661
  DATE CREATED: DEC 11, 1998            CUSTODIAL PACKAGE: 1
  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
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
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
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
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
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
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
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: 2668                            IA #: 2668
  DATE CREATED: DEC 17, 1998
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Other                           NAME: DBIA2668
 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: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RA PROFQUICK
 COMPONENT DESCRIPTION:   Permission to use Option: 
  
   [RA PROFQUICK]  Profile of Rad/Nuc Med Exams 
COMPONENT/ENTRY POINT: RA RPTDISP
 COMPONENT DESCRIPTION:   Permission to use Option: 
  
   [RA RPTDISP]  Display a Rad/Nuc Med Report 
COMPONENT/ENTRY POINT: RA RPTPAT
 COMPONENT DESCRIPTION:   Permission to use Option: 
  
   [RA RPTPAT]  Select Report to Print by Patient 
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany

NUMBER: 2669                            IA #: 2669
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Other                           NAME: DBIA2669
 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: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SDPATIENT
 COMPONENT DESCRIPTION:   Permission to use Option: 
  
   [SDPATIENT]  Patient Profile MAS 
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
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
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
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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 2674                            IA #: 2674
  GLOBAL ROOT: LAB(65.4                 DATE CREATED: DEC 17, 1998
  CUSTODIAL PACKAGE: LAB SERVICE        USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA2674
  ID: LAB(65.4
GLOBAL REFERENCE: LAB(65.4,DO
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The CIRN Term Mapping routine (^RGHOMAP) makes a direct
 global read of the BLOOD BANK UTILITY file (#65.4), for the purpose of setting
 up a mapping reference.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed

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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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: 2677                            IA #: 2677
  FILE NUMBER: 61                       GLOBAL ROOT: LAB(61,
  DATE CREATED: DEC 30, 1998            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: DBIA2677                        ID: LAB(61,
GLOBAL REFERENCE: LAB(61,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The CIRN Cytology  data extraction routine ^RGHOPATH
 makes direct global reads of the TOPOGRAPHY FIELD(#61). The routine  ^RGHOPATH 
  uses this information to generate HL7 message for transmission of Pathology
 reports.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham

NUMBER: 2678                            IA #: 2678
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX
  DATE CREATED: DEC 30, 1998            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  NAME: DBIA2678                        ID: PSRX
GLOBAL REFERENCE: PSRX(D0,2)
FIELD NUMBER: 31                        FIELD NAME: RELEASED DATE/TIME
  LOCATION: 2,13                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(D0,SIG1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SIG1
  LOCATION: 0,1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(D0,1,0)
FIELD NUMBER: 52                        FIELD NAME: REFILL
  LOCATION: 0,3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(D0,1,D1,0)
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
GLOBAL REFERENCE: PSRX(D0,P,D1,0)
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
GLOBAL REFERENCE: PSRX(D0,A,D1,0)
FIELD NUMBER: .02                       FIELD NAME: REASON
  LOCATION: 0,2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: COMMENT
  LOCATION: 0,5                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The CIRN Outpatient Pharmacy data extraction routine
 (^RGHORXO - HL7 Message Generation for Prescriptions), makes several
 references to fields in the PRESCRIPTION file (#52), Version 6 only, for the
 purpose of creating the HL7 transmission records.  *Note: Some of the
 referenced PRESCRIPTION file fields have already been defined in DBIA: 824.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

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
  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: 2680                            IA #: 2680
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: OE/RR use of PSRX global
  ID: PSRX(
GLOBAL REFERENCE: PSRX(DA,0)
FIELD NUMBER: 2                         FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 100                       FIELD NAME: STATUS
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(0)
 GLOBAL DESCRIPTION:   Estimator retrieves the number of entries in ^PSRX by
 getting the 4th piece of the 0 node of the file.  While we realize it's not
 100% accurate, it's close enough (and speedier) for an estimator tool.  
 GENERAL DESCRIPTION:   As part of the pre-CPRS functionality that is released
 with OR*2.5*49, an estimate of global growth is given.  One of the components
 of that growth is the backfilling of outpatient pharmacy prescriptions.  
  
 In order to calculate the number of prescriptions that might be backfilled, we
 loop through the PHARMACY PATIENT file and then through the "A" x-ref of the
 PRESCRIPTION PROFILE multiple (#55.03).  We then get the pointer to the
 PRESCRIPTION file (from the cross-reference) where we check the status of the
 prescription and the existence of a PATIENT file pointer.  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Next Version
  EXPIRATION DATE: DEC 01, 2006         GOOD ONLY FOR VERSION: OE/RR 2.5
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
  GOOD ONLY FOR VERSION: OE/RR v2.5
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 2682                            IA #: 2682
  FILE NUMBER: 59.7                     GLOBAL ROOT: PS(59.7,
  DATE CREATED: DEC 30, 1998
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: OE/RR references to PS(59.7,
  ID: PS(59.7,
GLOBAL REFERENCE: PS(59.7,1,80)
FIELD NUMBER: 81
  FIELD NAME: ORDERABLE ITEM STATUS TRACKER
  LOCATION: 80;2                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   We quit if there is no value or if the value is 1 or 2.  
 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 EMAIL GROUP 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 December 31, 2006.  OR*2.5*49 performs a check to ensure pharmacy
 data management matching is complete prior to letting OR*2.5*49 be installed.  
  STATUS: Retired                       DURATION: Next Version
  EXPIRATION DATE: DEC 31, 2006         GOOD ONLY FOR VERSION: OERR 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
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
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
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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: HEALTHEVET DESKTOP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expires on 10/27/17 when
 HMP will be shutdown.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for sites to shut down the HMP application.  
  
 On 3/30/16 a temporary ICR was approved by the Kernel team until 12/31/16 for
 HMP to modify their code to use Kernel API $$GETLST^XPAR() (Supported ICR
 #2263).  DE4264 was entered to track this defect.  As of 10/18/17, this defect
 has not been resolved.  
  
 If HMP is reactivated in the future, a new expiration date should be discussed
 with the Kernel team.  

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
  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
  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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE
 SUBSCRIBING DETAILS:   1/10/22: Patient Representative Decom patch QAC*2.0*25
 has been released on 01/10/2022 with a Compliance date of 2/10/22. Patient
 Representative subscription retired effective with a Compliance date of
 2/10/22.  

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
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

NUMBER: 2691                            IA #: 2691
  DATE CREATED: JAN 02, 1999
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: ORPR02
  NAME: Calls to ORPR02                 ID: ORPR02
 GENERAL DESCRIPTION:   ORPR02 contains functionality to print various types of
 CPRS-related outputs (chart copies, work copies, requisitions, etc.).  
  STATUS: Withdrawn
COMPONENT/ENTRY POINT: PRINT(ORVP,.ARRAY,.SARRAY,LOC,SELECT,ALTPRAM,NOQUE,ORTIME
S)
 COMPONENT DESCRIPTION:   This entry point allows printing an array of orders
 in a specified format (work copy, chart copy, service copy, requisition,
 etc.).  
VARIABLES: ORVP                         TYPE: Input
 VARIABLES DESCRIPTION:   Variable pointer indicating the person for which the
 orders were placed (typically a pointer to the PATIENT file, but not always). 
 REQUIRED 
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   List of IENs of the ORDER file (#100) denoting orders
 to print [REQUIRED]: 
     
     ARRAY(#) = ORIFN;DA of action 
VARIABLES: SARRAY                       TYPE: Input
 VARIABLES DESCRIPTION:   Device information for the array of orders
 (optional): 
  
    SARRAY(PKG,ORIFN) = device ptr ^ # of copies 
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   Location for which order is placed (optional).  
VARIABLES: SELECT                       TYPE: Input
 VARIABLES DESCRIPTION:   String of ^-delimited pieces describing the type of
 print(s) to be done.  Piece must contain a 1 for output to print.  (optional,
 but failure to pass results in all outputs being printed!) 
  
     Format:  chartcopy^label^requisition^servicecopy^workcopy 
VARIABLES: ALTPRAM                      TYPE: Input
 VARIABLES DESCRIPTION:   Alternate to internal default parameters.  This is
 also a '^'-delimited string.  Pass 1 in the piece to activate parameter. 
 [OPTIONAL] 
  
 Format:  
  PROMPT CC^CC DEVICE^L DEVICE^R DEVICE^PROMPT L^PROMPT R^PROMPT W^W DEVICE 
VARIABLES: NOQUE                        TYPE: Input
 VARIABLES DESCRIPTION:   Set to 1 to force interactive device selection for
 service copies.  [OPTIONAL] 
VARIABLES: ORTIMES                      TYPE: Input
 VARIABLES DESCRIPTION:   Number of copies.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  ISC: Salt Lake City

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
 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
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 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) would like to subscribe to ICR 2692,
 ORQPTQ1 Calls in order to retrieve a list of patients for a specified list.
 Data returned is from the OE/RR List File (#100.21).  
  DATE ACTIVATED: SEP 17, 2008

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
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.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  

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
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: 1
  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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 2696                            IA #: 2696
  FILE NUMBER: .4                       GLOBAL ROOT: DIPT(
  DATE CREATED: JAN 06, 1999            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: RECOMPILATION OF PRINT TEMPLATES
  ID: DIPT(
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
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: APR 03, 2012
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
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
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Added 11/6/19 for access to NAME (.01 field of
 ORD(101.42,D0,0) global reference), effective with RA*5*161.  

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
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
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  

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
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 <sep> 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
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.  

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
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: 2704                            IA #: 2704
  DATE CREATED: JAN 12, 1999
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Private                        TYPE: Routine
  ROUTINE: MPIF001                      NAME: $$SETICN MPIF001
  ID: MPIF001
 GENERAL DESCRIPTION:   This function updates the Intergration Control Number
 (#991.01) and the ICN Checksum (#991.02) fields in the Patient (#2) file on
 the MPI node.  This is being provided for use by the CIRN developers.  
  STATUS: Retired
COMPONENT/ENTRY POINT: $$SETICN
 COMPONENT DESCRIPTION:   $$SETICN^MPIF001(DFN,ICN,CHKSUM)  This function
 update the ICN (#991.01) and ICN Checksum (#991.02) fields 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: ICN                          TYPE: Input
 VARIABLES DESCRIPTION:   ICN - ICN (without checksum) to be updated. 
VARIABLES: CHKSUM                       TYPE: Input
 VARIABLES DESCRIPTION:   CHKSUM - ICN checksum to be updated. 
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 2705                            IA #: 2705
  DATE CREATED: JAN 13, 1999
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Private                        TYPE: Routine
  ROUTINE: MPIF001                      NAME: $$SETLOC MPIF001
  ID: MPIF001
 GENERAL DESCRIPTION:   This function allows the updating the the Local ICN
 field (#991.04) in the Patient file (#2) on the MPI node.  This is provided to
 assist the CIRN developers.  
  STATUS: Retired
COMPONENT/ENTRY POINT: $$SETLOC
 COMPONENT DESCRIPTION:   $$SETLOC^MPIF001(DFN,DELFLAG)  This function updates
 the Locally Assigned ICN (#991.04) 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: DELFLAG                      TYPE: Input
 VARIABLES DESCRIPTION:   DELFLAG - 1 to turn the flag on OR 0 to turn the flag
 off. 
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

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
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
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
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
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
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
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
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
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

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
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA

NUMBER: 2715                            IA #: 2715
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: JAN 19, 1999            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: READ NEW PERSON (#200) FILE NAME & SSN FIELDS
  ID: VA(200,
GLOBAL REFERENCE: VA(200,DUZ,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: VA(200,DUZ,1)
FIELD NUMBER: 9                         FIELD NAME: SSN
  LOCATION: 1;9                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Registration requires direct global read access to the
 Name (#.01) and SSN (#9) fields in the New Person (#200) for Privacy Act
 compliance.  Routine DGSEC will be modified to obtain the user's name and SSN
 from the New Person file.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

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
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
 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: 2717                            IA #: 2717
  DATE CREATED: OCT 11, 2005
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  USAGE: Private                        TYPE: Other
  NAME: MPIF OPTIONS/MENUS ON CIRN MENUS
 GENERAL DESCRIPTION:   MPI is requesting to place some options/menus on CIRN
 namespaced Menus.  
  
  MPIF VISTA MENU on the RG ADMIN COORD MENU 
  MPIF CMOR MGR on the RG ADMIN USER MENU 
  MPIFINIT DPT TO MPI on the RGINIT MENU 
  MPIF COMP MAIN on the RGINIT MENU 
  MPIF SITE PARAMETER on the RG ADMIN COORD MENU 
  STATUS: Retired
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA

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
SUBSCRIBING PACKAGE: 1                  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',<vol>)
 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
SUBSCRIBING PACKAGE: 1                  ISC: Oakland

NUMBER: 2720                            IA #: 2720
  FILE NUMBER: 60                       GLOBAL ROOT: LAB
  DATE CREATED: JAN 21, 1999            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  NAME: DBIA2720                        ID: LAB
 GENERAL DESCRIPTION:   The CIRN Cytology  data extraction routine ^RGHOPATH
 makes direct global reads of the LABORATORY TEST(#60). The routine ^RGHOPATH
 uses this information to generate HL7 message for transmission of Pathology
 reports.  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham

NUMBER: 2721                            IA #: 2721
  FILE NUMBER: 63                       GLOBAL ROOT: LR(
  DATE CREATED: JAN 21, 1999            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: DBIA2721                        ID: LR(
GLOBAL REFERENCE: LR(D0,CY,D1,1.2,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Supplementary  Report
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,CY,D1,.4,D2
FIELD NUMBER: 0;1                       FIELD NAME: Operative Findings
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,EM,D1,.4,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Operative Findings
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,EM,D1,.5,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Postoperative Diagnosis
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,EM,D1,1,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Microsopic Examination
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,EM,D1,1.2,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Supplementary Report
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,EM,D1,1.4,D2,
FIELD NUMBER: 0;1                       FIELD NAME: EM Diagnosis
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,EM,D1,2,D2,
FIELD NUMBER: 0;1                       FIELD NAME: EM Organ/Tissue
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,EM,D1,.2,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Brief Clincal History
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,CY,D1,1,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Gross description
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,CY,D1,1.1,D2
FIELD NUMBER: 0;1                       FIELD NAME: Microscopic examination
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,CY,D1,2,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Cytopath Organ/Tissue
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,CY,D1,.1,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Specimen
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,CY,D1,.3,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Preoperative Diagnosis
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,CY,D1,.2,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Brief Clinical History
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,CY,D1,1.4,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Cytopathology Diagnosis
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,EM,D1,.1,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Speciman
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,EM,D1,.3,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Preoperative Diagnosis
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,EM,D1,1.1,D2
FIELD NUMBER: 0;1                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,SP,D1,.1,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Specimen
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,SP,D1,.2,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Brief Clinical History
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,SP,D1,.3,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Preoperative Diagnosis
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,SP,D1,.4,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Operative Findings
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,SP,D1,.5,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Postoperative Diagnosis
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,SP,D1,1,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Gross Description
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,SP,D1,1.1,D2,
FIELD NUMBER: ,0;1                      FIELD NAME: Microscopic Description
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,SP,D1,1.2,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Supplementary Report
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,SP,D1,1.3,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Frozen Section
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,SP,D1,1.4,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Surgical Path Diagnosis
GLOBAL REFERENCE: LR(D0,SP,D1,2,D2,
FIELD NUMBER: 0;1                       FIELD NAME: Organ/Tissue
  ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The CIRN Cytology  data extraction routine ^RGHOPATH
 makes direct global reads of  the LAB DATA(#63). The routine ^RGHOPATH uses
 this information to generate HL7 message for transmission of Pathology
 reports.  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham

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/CLV 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, IR^SDCO22, and CLV^SDCO22 to determine which of the classification
 questions should be asked. (That takes place in ASKCLASS^ECUTL1 and
 GETCLASS^ECUTL1.) AO^SDCO22, EC^SDCO22, IR^SDCO22, and CLV^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/CLV 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,
 EC, and CLV 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 
    Was treatment related to Camp Lejeune 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 
    PXBDATA(5)=0^1       <-- Camp Lejeune 
       where the 2nd piece indicates the user's answer to the 
       classification prompt -- 0=NO, 1=YES 
   
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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/CLV.  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
  DATE ACTIVATED: JAN 10, 2017

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,<error number>,"TEXT",<line number>)=<error 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
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: 
  
 <number> - 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: <basket IEN>^<basket name>) 
        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:<internal date>^<dd mmm yy hh:mm> 
        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: <internal from>^<external from>) 
        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? 
        <null>   - has not read the message at all 
        0        - has read the message, but no responses 
        <number> - has read through this response 
  
 RESP - how many responses does the message have? 
        0        - none 
        <number> - 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: 
  
 <number> - 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 of messages in basket>".  

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
  GOOD ONLY FOR VERSION: OE/RR 2.5
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 2725                            IA #: 2725
  DATE CREATED: JAN 26, 1999
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: OE/RR READ RADIOLOGY PARAMETERS
 GENERAL DESCRIPTION:   These parameter definitions and values were originally
 distributed via OR*2.5*49 as part of the pre-CPRS setup activities.  
  
 After the initial export, and beginning with OE/RR v3.0, these parameters have
 been read by OE/RR when building the radiology order dialog for use in CPRS
 GUI.  
  
 This ICR entry is being updated with the release of OR*3.0*608, CPRS GUI 
 v33SWD, to reflect the historical and ongoing usage of these parameter 
 definitions by OE/RR and CPRS GUI. No new functionality or access is included
 or implied with this ICR update.  
  
  
 The two RADIOLOGY parameter definitions covered by this ICR are: 
  
  
 RA REQUIRE DETAILED 
  
 RA SUBMIT PROMPT 
  STATUS: Active                        DURATION: Till Otherwise Agreed
  GOOD ONLY FOR VERSION: OE/RR 3.0
KEYWORDS: RADIOLOGY
KEYWORDS: PARAMETER
KEYWORDS: ORCDRA
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 15, 2023

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
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
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
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expires on 10/27/17 when
 HMP will be shutdown.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for sites to shut down the HMP application.  
  
 HMP had temporary approval to ICR #2727 until 12/31/16.  DE4685 was entered
 for HMP to modify their code to use the APIs in routine GMPLUTL2 (ICR #2741). 
 However not all references were removed.  Code in HMPDJ02 and HMPEVNT was out
 of scope for the defect. Remaining modifications may be part of HMP*2.0*4
 which was not released prior to the shutdown of HMP.  
  
 If HMP is reactivated, this ICR should be reviewed and a new expiration date
 discussed with the custodial package.  

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,<error number>,"TEXT",<line number>)=<error text> 
  STATUS: Active
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,<error number>,"TEXT",<line number>)=<error 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:
 <subject of original message>".  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 "@<sitename>" for any addressees at another site: 
        eg: "I:G.group@site.dsn" or "LAST,FIRST@site.dsn" 
  
 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
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
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
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
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).  

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
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
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
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
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
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
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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

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
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)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) subscribes to ICR 2740 in order to
 retrieve a list of consults/procedures.  
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Added 10/1/24 effective with Patch MECH*1.0*1 request
 access to COMPONENT OER. The presence of this Class 2 subscribers shall not
 prevent modifications to the underlying artifact.  

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
 GENERAL DESCRIPTION:   This DBIA documents calls made to routine GMPLUTL2.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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)
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   TIUWRIIS calls LIST^GMPLUTL2.  Documenting with Patch
 TIU*1.0*286 - but the code actually was released in a prior patch.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
 SUBSCRIBING DETAILS:   Added 03/03/20, effective with GMRV*5*40, to support a
 requirement to compare patient's weight gain/loss to the national weight
 gain/loss thresholds for vitals in CPRS.  
SUBSCRIBING PACKAGE: EVENT CAPTURE
 SUBSCRIBING DETAILS:   Added 12/13/21, effective with Patch EC*2.0*156, for
 ECS SustainmentFY22 Development, a new routine will call LIST^GMPLUTL2 and
 DETAIL^GMPLULTL2 to display the following information of a problem: - Problem
 Status - ICD Code - ICD Description - Date of Onset - Date of Last Modified -
 Provider.  
  DATE ACTIVATED: NOV 05, 2014

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
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
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

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
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, Ionizing
 Radiation, Camp LeJeune, Gulf War, Head and/or Neck Cancer, Military Sexual
 Trauma, Combat Veteran, and Shipboard Hazard and Defense.  
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 
VARIABLES: GMPCV                        TYPE: Output
 VARIABLES DESCRIPTION:   Combat Veteran Indicator: 1 if yes, 0 if no, "" if
 unknown 
VARIABLES: GMPSHD                       TYPE: Output
 VARIABLES DESCRIPTION:   Shipboard Hazard and Defense Indicator: 1 if yes, 0
 if no, "" if unknown 
VARIABLES: GMPCLV                       TYPE: Output
 VARIABLES DESCRIPTION:   Camp LeJeune Indicator:  1 if yes, 0 if no, "" if
 unknown 
COMPONENT/ENTRY POINT: SCCOND(DFN,.SC)
 COMPONENT DESCRIPTION:   Returns information on SC, Agent Orange, Ionizing
 Radiation, Camp LeJeune, Gulf War, Head and/or Neck Cancer, Military Sexual
 Trauma, Combat Veteran, and Shipboard Hazard and Defense 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("CLV") = Camp LeJeune Indicator 
   SC("CV")  = Combat Veteran 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 
   SC("SHD") = Shipboard Hazard and Defense 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, delimited 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/CL/CV/SHD   Delimited abbreviation 
    SC(2) = A/I/E/H/M/L/C/S               Delimited Initials 
    SC(3) = AIEHMLCS                      Initials 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
  DATE ACTIVATED: AUG 17, 2015

NUMBER: 2744                            IA #: 2744
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: JAN 29, 1999            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: CIRN Access to DPT File         ID: DPT(
GLOBAL REFERENCE: DPT(D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   CIRN needs a read access to the DPT 0 node file
 (Patient File) in order to build the "B" cross reference to the DGCN(391.98
 file.  CIRN gets the first piece of the DPT 0 node field to build the "B"
 cross reference.  
  
 CROSS-REFEREENCE:  391.98^B^MUMPS 
                    1)= N A S A=$P($G(^DPT(X,0)),U,1) I A]"" S ^DGCN(391.98, 
                        "B",A,DA)="" 
  
                    2)= N A S A=$P($G(^DPT(X,0)),U,1) I A]"" K ^DGCN(391.98, 
                        "B",A,DA)="" 
                        This is the external to help in the sorting.  
  
 A precedent was set with DBIA 321 with the caveat: 
  
   It is further agreed that the following tools will not be used with 
   this file: KIDS, COMPARE/MERGE and TRANSFER.  These tools rely on 
   an unmodified "B" index to function properly.  Using the modified 
   "B" index of file 757.01 along with any of the named tools may 
   produce unexpected results.  
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 2745                            IA #: 2745
  DATE CREATED: JAN 29, 1999            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Supported
  TYPE: Routine                         ROUTINE: GMTSULT2
  NAME: HEALTH SUMMARY TYPE LOOKUP      ID: GMTSULT2
 GENERAL DESCRIPTION:   The lookup for the Healh Summay Type file has been
 changed from a standard DIC lookup to a Multi-Term-Lookup effective patch
 GMTS*2.7*30.  The new lookup routines are in the GMTSULT namespace (Lookup
 Type).  The routine GMTSULT2 builds the list of possible Health Summary Types
 to select from.  The entry point LIST^GMTSULT2 is being support for potential
 GUI applications which need an array of Health Summary Types to select from.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LIST()
 COMPONENT DESCRIPTION:   LIST^GMTSULT2(<search string>) searches the Health
 Summary Type file for entries that match the search string and return the
 findings in a global array.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   This is the text string that will be used in the
 Health Summary Type Lookup.  
  
   D LIST^GMTSULT2(X) 
  
VARIABLES: TMP(GMTSULT                  TYPE: Output
 VARIABLES DESCRIPTION:   This is the global array returned as a result of the
 search.  It is the responsibility of the calling application to kill this
 array when no longer needed.  
  
 ^TMP("GMTSULT",$J,0)=# ^TMP("GMTSULT",$J,#)=<1>^<2>^<3>^<4>^<5>^<6>^<7> 
  
    1.  The first piece is the Internal Entry Number (IEN) in the Health 
        Summary Type file #142.  
  
    2.  The second piece is the name of the Health Summary Type (.01 field 
        of file 142).  
  
    3.  The third piece is the Health Summary Type Title (.02 field of file 
        142).  
  
    4.  The fourth piece is the Health Summary Type Owner (.06 field of file 
        142) 
  
    5.  The fifth piece is the Hospital Location using the Health Summary 
        Type (.01 field of subfile 142.2).  
  
    6.  The sixth piece is the number of components in the Health Summary.  
  
    7.  The seventh piece is the recommend display text (for user selection).  
  

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
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
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

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
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: 2749                            IA #: 2749
  DATE CREATED: FEB 08, 1999            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Other                           NAME: ABC
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Hines

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
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",<patient file ien>,<institution ien>) 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
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA

NUMBER: 2752                            IA #: 2752
  DATE CREATED: MAR 15, 1999            CUSTODIAL PACKAGE: 1
  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
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 2753                            IA #: 2753
  DATE CREATED: MAR 16, 1999            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: VAFCEHU1
  NAME: ADD entries to PATIENT DATA EXCEPTION (#391.98) File
  ID: VAFCEHU1                          STATUS: Withdrawn
COMPONENT/ENTRY POINT: $$ADD(VAFCA,VAFCB)
 COMPONENT DESCRIPTION:   This API provides functionality that adds entries to
 the PATIENT DATA EXCEPTION (#391.98) File. Ex. S
 X=$$ADD^VAFCEHU1(VAFCA,"RGRS") 
VARIABLES: $$ADD(VAFCA,VAFCB)           TYPE: Output
 VARIABLES DESCRIPTION:   0^error message - in the case of a failure 
  
 1 - in the case that the entry is added 
VARIABLES: VAFCA                        TYPE: Input
 VARIABLES DESCRIPTION:   This parameter contains four components.  Below is a
 description of each component: 
  
 Date Received^Event date^From whom^patient IEN 
          
 Date Received - This is the date/time that the exception was received at the
 facility.  Must be in FM format.  
  
 Event date -    This is the date/time when the event occurred that caused this
 information to be sent.  Must be in FM format.  
  
 From whom -     This is who sent the information.  This should be in a free
 text format.  There is a potential that exception could be coming from sources
 other than what is listed in the institution file. FORMAT institution
 name(sender name) 
  
 Patient IEN -   The patient file internal entry number.  
VARIABLES: VAFCB                        TYPE: Input
 VARIABLES DESCRIPTION:   This parameter contains the value or location of the
 array. The array value should either be passed with a local or global
 reference.  The array should be in the following format: 
    X(File#,Field#)=value  Example: RGRS(2,.03)=value 
  
 **Note this is only used for editing Patient (#2) file fields, not subfiles.
 ** 
  
 **NOTE** 
  
 When setting info in the passage array please follow this format for these 
 exceptions. Unspecified or blank data should have no array element or an array
 element set to the mumps null.  If data from a sender can not be resolved then
 set $P(array element,U,2)=1. If you wish to delete what is in the receiving
 facilities field set the array element to "@".  
   EX. S X(1)="""@""" 
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
 SUBSCRIBING DETAILS:   CIRN is using this API to update the following PATIENT
 (#2) file fields: 
  
 .01;.03;.09;.02;.05;.08;.111;.112;.113;.114;.115;.1112; .117;.131;.132;.211
 ;.219;.2403;.31115 

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
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
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
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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 2760                            IA #: 2760
  DATE CREATED: FEB 26, 1999
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  USAGE: Private                        TYPE: Routine
  ROUTINE: RGRSUTL1                     NAME: TEST PATIENT CHECK
  ID: RGRSUTL1
 GENERAL DESCRIPTION:   This function will identify 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(s) or a 0 if it
 does not meet the given parameter(s).  
  STATUS: Withdrawn
COMPONENT/ENTRY POINT: $$SEND2(DFN,PARAMS)
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of PATIENT (#2) file 
VARIABLES: PARAMS                       TYPE: Input
 VARIABLES DESCRIPTION:   PARAMS - "D"ead Patient 
          "T"est Patient 
          "E"mployee 
          "V"eteran (Non) 
          "P"suedo 
VARIABLES: $$SEND2(DFN,PARAMS)          TYPE: Output
 VARIABLES DESCRIPTION:   
  if the parameter list contains: 
  
   input   output      reason 
   "D"       1         Dead patient 
   "T"       1         Test patient 
   "E"       1         Employee 
   "V"       1         Non-Veteran 
   "P"       1         Psuedo 
  
  otherwise the function returns  0 
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA

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
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING

NUMBER: 2762                            IA #: 2762
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: MAR 01, 1999            CUSTODIAL PACKAGE: KERNEL
  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 usage of this
 record.  MPI wants to be sure not to get these patients and is checking for
 the existence 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.  
  
 NOTE:  Duplicate Merge is responsible for setting the -9 node in the Patient
 (#2) file.  The Patient (#2) file is part of the Registration package. 
 However because Duplicate Merge is responsible for setting this node, it was
 decided Kernel should be the Custodial Package as recommended by the DBA.  
  STATUS: Active
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

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
SUBSCRIBING PACKAGE: 1                  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
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  ISC: Salt Lake City

NUMBER: 2765                            IA #: 2765
  DATE CREATED: MAR 04, 1999            CUSTODIAL PACKAGE: FEE BASIS
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Routine                         ROUTINE: FBUTL
  NAME: FBUTL                           ID: FBUTL
 GENERAL DESCRIPTION:   FEE BASIS APIs.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: AUTH
 COMPONENT DESCRIPTION:   Authorization extrinsic function. Indicates if a
 patient has any FEE authorizations in the FEE BASIS PATIENT (#161) file. An
 optional cutoff date can be specified to determine if the patient has any FEE 
 authorizations in effect on or after the specified date.  
  Usage: $$AUTH^FBUTL(FBDA,FBCUT) 
  Returns 1 if true or 0 if false.  
VARIABLES: FBDA                         TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number (DFN) of the PATIENT
 (#2) and FEE BASIS PATIENT (#161) file.  
VARIABLES: FBCUT                        TYPE: Input
 VARIABLES DESCRIPTION:   Optional cutoff date (fileman format). Authorizations
 with a TO DATE prior to the cutoff date (if specified) will not be considered. 
 

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
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
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
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
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
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
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
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).  
COMPONENT/ENTRY POINT: SAVEHPV
 COMPONENT DESCRIPTION:   This components allows an HPV Lab test to be save to
 the Women's Health package when an chemistry lab test is completed.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN is the patient DFN 
VARIABLES: LABARRAY                     TYPE: Input
 VARIABLES DESCRIPTION:   This passed by reference array contains the
 information that is needed to allow the Women's Health package to save the HPV
 test to file 790.1. The structure of LABARRAY is: LABARRAY("ACCESSION")=is the
 completed lab test accession value LABARRAY("ID")=is the inverse date/time of
 the lab procedure LABARRAY("LAB TEST IEN")=is the pointer to the lab test
 entry from file 60.  LABARRAY("LOCATION")=is the ordering location IEN from
 file 44 LABARRAY("LRDFN")=is the IEN from file 63 for the patient 
 LABARRAY("PROVIDER")=is the ordering provider IEN from file 200 
 LABARRAY("SDATE")=is the date the specimen was collected in FileMan format 
 LABARRAY("SUB")=is the completed lab test accession subscript it should be set
 to one of the following CH for Chemistry, CY for Cytopathology, or SP for
 Surgical Pathology 
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Added 8/9/23, effective with PXRM*2.0*81, PXRMPLAB
 calls the new component, SAVEHPV, available in WV*1.0*31.  
  DATE ACTIVATED: AUG 09, 2023

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
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
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: 2775                            IA #: 2775
  DATE CREATED: MAR 09, 1999
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  USAGE: Private                        TYPE: Routine
  ROUTINE: RGRSBUL1                     NAME: CIRN Subscription Bullentin
  ID: RGRSBUL1
 GENERAL DESCRIPTION:   This agreement identifies NOT2^RGRSBUL1 to be an entry
 point that can be called to generate a bulletin to the RG CIRN DEMOGRAPHIC
 ISSUE mail group informing that group with information passed in the parameter
 list.  
  STATUS: Retired
COMPONENT/ENTRY POINT: NOT2(ARRAY)
 COMPONENT DESCRIPTION:   This entry point generates a bulletin to the RG CIRN
 DEMOGRAPHIC ISSUES mail group about invalid subscription information for a
 given patient.  The bulletin information is based on information passed in the
 ARRAY parameter.  This information should explain the differences in your 
 current systems patient information and the inbound facilities patient 
 information.  
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) 
     
 ARRAY("SENDING SITE")  -  sending facilities station number 
  
 ARRAY("MESSAGE",x) - Array of text for the bulletin and x is an integer 
 starting at 1 that will be added to the text listed below.  
  
  
 The CIRN Package has received a message from: 
  
  "Sending sites name" 
  
 This patient has your station as a subscriber, however the patient was not
 found in your database.  
  
 --------------------------------------------------------
  
  Remote Data 
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 2776                            IA #: 2776
  DATE CREATED: MAR 09, 1999
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  USAGE: Private                        TYPE: Routine
  ROUTINE: RGRSBULL                     NAME: CIRN Patient Match Bulletin
  ID: RGRSBULL
 GENERAL DESCRIPTION:   This agreement identifies the entry point,
 MTCHBULL^RGRSBULL, as a callable entry point that will generate a bulletin to
 the RG CIRN DEMOGRAPHIC ISSUES mail group explaining the differences in the
 inbound patient demographic information and the existing PATIENT (#2) file 
 informaton.  
  STATUS: Retired
COMPONENT/ENTRY POINT: MTCHBULL(DFN,ARRAY,NAME,SSN,ICN,CMOR,BULSUB)
 COMPONENT DESCRIPTION:   This entry point generates a bulletin to the RG CIRN
 DEMOGRAPHIC ISSUES mail group explaining differences in the data of a given
 patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN   - IEN in the PATIENT file (#2) 
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   ARRAY("SENDING SITE")  - Contains sending sites
 station number ARRAY("ICN") - Contains the Patient's ICN from the sending site 
 ARRAY("SSN") - Contains the Patient's SSN from the sending site ARRAY("CMOR")
 - Contains Patient's CMOR from the sending site ARRAY("NAME") - Contains the
 Patient's name from the sending site 
VARIABLES: NAME                         TYPE: Input
 VARIABLES DESCRIPTION:   NAME  - Patient's Name 
VARIABLES: SSN                          TYPE: Input
 VARIABLES DESCRIPTION:   SSN   - Patient's SSN 
VARIABLES: ICN                          TYPE: Input
 VARIABLES DESCRIPTION:   ICN   - Patient's ICN (Integration Control Number) 
VARIABLES: CMOR                         TYPE: Input
 VARIABLES DESCRIPTION:   CMOR  - Patient's CMOR (CIRN Master of Record) 
VARIABLES: BULSUB                       TYPE: Input
 VARIABLES DESCRIPTION:   BULSUB - Bulletin subject (Ex. ICN) 
SUBSCRIBING PACKAGE: REGISTRATION

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
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
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.  

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
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

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(
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
SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE
  ISC: Oakland
  DATE ACTIVATED: FEB 21, 2014

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
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM
  ISC: Hines
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
 SUBSCRIBING DETAILS:   Added 6/24/25, effective with patch DSIV*2.2*16 
 INSURANCE CAPTURE BUFFER needs to verify that a patient is currently not
 covered by insurance for the purpose of informing users if they need to verify
 a patient still has no insurance.  

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(
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
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas
  DATE ACTIVATED: FEB 21, 2014

NUMBER: 2783                            IA #: 2783
  DATE CREATED: MAR 23, 1999
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  USAGE: Private                        TYPE: Routine
  ROUTINE: RGMTAUD                      NAME: DBIA2783
  ID: RGMTAUD
 GENERAL DESCRIPTION:   Registration needs an integration agreement with CIRN
 to call the ASK2^RGMTAUD, patient audit entry point from within the Patient
 Data Review [VAFC EXCEPTION HANDLER] option.  This entry point allows the 
 users to view patient audit information from within the list manager Patient
 exception review functionality.  
  STATUS: Withdrawn
COMPONENT/ENTRY POINT: ASK2
 COMPONENT DESCRIPTION:   This entry point prints an Audit File data report for
 a specific Patient and a given date range.  
SUBSCRIBING PACKAGE: REGISTRATION

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
 GENERAL DESCRIPTION:   This private routine agreement allows packages to
 update certain PATIENT (#2) file fields identified by each subscribing
 package.  
  STATUS: Active
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).  
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   2/23/16 - The Emergency Department application was
 added as a subscriber to document an existing use of EDIT^VAFCPTED in routine
 PHONE^EDPUPD.  The API has been used by EDIS since EDIS version 2.0/2.1.2 to
 update the Phone Number [Residence] (#.131), Phone Number [Cellular] (#.134)
 and K-Phone Number (#.219) in the Patient (#2) file. A new request should be 
 submitted for review if the VAFCPTED API will be used in the future to update
 additional Patient (#2) file fields.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP v.2.0 contains calls to VAFCPTED to update the
 following fields: PHONE NUMBER [RESIDENCE] (#.131), PHONE NUMBER [WORK]
 (#.132), PHONE NUMBER [CELLULAR] (#.134), K-PHONE NUMBER (#.219) and E-PHONE
 NUMBER (#.339).  
  
 HMP PUT DEMOGRAPHICS RPC was part of a feature in earlier versions of eHMP,
 and is no longer being used.  Temporary approval to add HMP as a subscriber
 allowed until any calls to this API can be removed in a future patch.  
  
 HMP's subscription to this ICR expires on 10/27/17 when HMP will be shutdown. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
  
 If HMP is reactivated, this ICR should be reviewed and a new expiration date
 set with the custodial application if the call to VAFCPTED was not removed
 prior to the HMP shut down.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   VPR added as a subscriber for VPR*1*3.  This patch was
 installed at 3 test sites but later backed out at these sites.  However the
 patch was released to OSEHRA.  
  
 VPR*1*3 code calls VAFCPTED to update the Phone Number [Residence] (#.131),
 Phone Number [Work] (#.132), Phone Number [Cellular] (#.134), K-Phone Number
 (#.219) and E-Phone Number (#.339) fields in the Patient (#2) file.  
  DATE ACTIVATED: JUL 16, 2007

NUMBER: 2785                            IA #: 2785
  DATE CREATED: MAR 23, 1999            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Other                           NAME: SCD Alert
 GENERAL DESCRIPTION:   This request is to add a new item to the DGPM MOVEMENT
 EVENTS protocol.  The new item will be the SCD MOVEMENT EVENTS protocol.  This
 protocol will make a call to the SPNALERT routine, which in turn will run the
 VADPT API.  If its an admit event then an alert will be sent.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  ISC: Albany
 SUBSCRIBING DETAILS:   When a Spinal Cord Injury patient is admitted send an
 alert to the SPNL SCD COORDINATOR mail group.  This will be done through a
 routine in the SCD name space.  

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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
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
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
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
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.  

NUMBER: 2791                            IA #: 2791
  FILE NUMBER: 2005                     GLOBAL ROOT: MAG(2005,
  DATE CREATED: MAR 31, 1999            CUSTODIAL PACKAGE: IMAGING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: DBIA2791
  ID: MAG(2005,
GLOBAL REFERENCE: MAG(2005,'AC',DFN)
FIELD NUMBER: 5                         FIELD NAME: PATIENT
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to the Patient file (2).  
 GLOBAL DESCRIPTION:   Cross reference on patient dfn.  
GLOBAL REFERENCE: MAG(2005,'APDTPX',DFN,PROC DATE,PROCEDURE,IEN)
FIELD NUMBER: 5                         FIELD NAME: PATIENT
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to the Patient file (2).  
FIELD NUMBER: 6                         FIELD NAME: PROCEDURE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field is an abbreviation for the procedure.  
FIELD NUMBER: 15                        FIELD NAME: PROCEDURE/EXAM DATE/TIME
  LOCATION: 2;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the date and time that the image was captured.  
FIELD NUMBER: 10                        FIELD NAME: SHORT DESCRIPTION
  LOCATION: 2;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Short description of image procedure.  
 GENERAL DESCRIPTION:   Imaging gives permission to Health Summary to read from
 file 2005 for the purpose of displaying image descriptions. [MAGI] 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 2792                            IA #: 2792
  DATE CREATED: JUN 17, 2003
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  USAGE: Private                        TYPE: Routine
  ROUTINE: RGEQ                         NAME: Add Entry to CIRN Event Queue
  ID: RGEQ
 GENERAL DESCRIPTION:   This agreement allows packages to create stub event
 queue entries which are later processed by the Event Queue Daemon.  The Event
 Queue Daemon then creates and broadcasts HL7 messages.  
  STATUS: Retired
COMPONENT/ENTRY POINT: EN(TYPE,STUB)
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   data class (Ex. "CH" for CHemistry) 
  
 Below is the list of all the possible CIRN Event Queue types from the CIRN 
 EVENT ASSOCIATION (#995) File: 
  
 "CH", "CH_BL", "COR", "CPT", "CPT_BL", "CRU", "CY", "CY_BL", "EDU", "EDU_BL",
 "EM", "EM_BL", "ENTRY", "EXM", "EXM_BL", "GMR", "GMR_BL", "HF", "HF_BL",
 "IMM", "IMM_BL", "MFQ","MI", "MI_BL", "MPIF CMOR REQUEST", "MPIF CMOR RESULT",
 "MSR", "MSR_BL", "PL", "PL_BL", "PNT", "PNT_BL", "POV", "POV_BL", "PPF
 REQUEST", "PPF RESULT", "PTF", "PTF_BL", "QRY", "RAD", "RAD_BL", "RX",
 "RX_BL", "SCN_REQ", "SKN", "SKN_BL", "SP", "SP_BL", "TIU", "TIU_BL", "TXN",
 "TXN_BL", "VIS", "VIS_BL", "VTX", "VTX_BL", "XLR", "XLR_BL" 
VARIABLES: STUB                         TYPE: Input
 VARIABLES DESCRIPTION:   
  event stub Ex. (91;7048784.917679;238) 
                 (translated LRDFN;Inverse date  ;data name) 
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA

NUMBER: 2793                            IA #: 2793
  DATE CREATED: APR 06, 1999            CUSTODIAL PACKAGE: EXTENSIBLE EDITOR
  USAGE: Private                        TYPE: Routine
  ROUTINE: RGED2                        NAME: CIRN CALLS TO RGED2
  ID: RGED2
 GENERAL DESCRIPTION:   CIRN ROUTINE DBIA TO CALL RGED2 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: CIRN
KEYWORDS: RGED2
KEYWORDS: EXTENSIBLE EDITOR
COMPONENT/ENTRY POINT: PRMPT
VARIABLES: RGPRMPT                      TYPE: Input
 VARIABLES DESCRIPTION:   If numeric, its absolute value is the index of the
 message in the EXTENSIBLE EDITOR MESSAGE file.  If zero or null, causes the
 default information text to be displayed (see the INFORMATION TEXT field
 description in section 1.1).  If a negative number, indicates that this is an
 error message and causes the editor to sound the bell and clear the iteration
 counter.   Otherwise, is the actual text of the message to be displayed.  In
 any case, the text may contain "|"-delimited replaceable parameters.  
  
VARIABLES: RGLEN                        TYPE: Input
 VARIABLES DESCRIPTION:   If nonzero, the editor awaits user input of up to
 RGLEN characters.  If not specified, defaults to the screen width less the
 length of the message (prompt).  If zero, the editor does not request user
 input (i.e., it only displays the message).  How the editor behaves once the
 specified input length is reached depends upon the setting of the RGFLG
 argument (see the "1", "H", and "T" flags).  
  
COMPONENT/ENTRY POINT: MOVETO
 COMPONENT DESCRIPTION:   Move to a new buffer row and/or column 
  
VARIABLES: RGR                          TYPE: Input
 VARIABLES DESCRIPTION:   The line number to move to.  
VARIABLES: RGC                          TYPE: Input
 VARIABLES DESCRIPTION:   The column position to move to.  
COMPONENT/ENTRY POINT: UPDATE
 COMPONENT DESCRIPTION:   Update changes made to the current line.   For
 efficiency, the editor buffers changes made to the current line in the
 variable RGLN.  Whenever the current line changes or a subroutine needs to
 directly access the buffer, the editor writes the current value of RGLN back
 to the buffer.  Therefore, you should make changes directly to RGLN when 
 modifying the current line and should make a call to UPDATERGED2  before
 directly accessing the edit buffer.  
  
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
 SUBSCRIBING DETAILS:   
  

NUMBER: 2794                            IA #: 2794
  DATE CREATED: APR 06, 1999            CUSTODIAL PACKAGE: EXTENSIBLE EDITOR
  USAGE: Private                        TYPE: Routine
  ROUTINE: RGEDS
  NAME: CIRN AGREEMENT WITH EXTENSIBLE EDITOR FOR CALL TO RGEDS
  ID: RGEDS
 GENERAL DESCRIPTION:   Private Routine DBIA for call to PAINT^RGEDS 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: RGEDS
KEYWORDS: EXTENSIBLE EDITOR
KEYWORDS: CIRN
COMPONENT/ENTRY POINT: PAINT
 COMPONENT DESCRIPTION:   Refresh the entire display.  
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

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
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
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

NUMBER: 2797                            IA #: 2797
  DATE CREATED: APR 06, 1999            CUSTODIAL PACKAGE: EXTENSIBLE EDITOR
  USAGE: Private                        TYPE: Routine
  ROUTINE: RGED
  NAME: CIRN AGREEMENT WITH EXTENSIBLE EDITOR FOR CALLS TO RGED
  ID: RGED
 GENERAL DESCRIPTION:   CIRN AGREEMENT WITH EXTENSIBLE EDITOR FOR CALLS TO RGED 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: CIRN
KEYWORDS: EXTENSIBLE EDITOR
KEYWORDS: RGED
COMPONENT/ENTRY POINT: RGED
 COMPONENT DESCRIPTION:   This is the entry point for invoking the Extensible
 Editor.  It may be invoked outside the editor environment or recursively from
 within the editor environment.  Only the first argument is required.   
VARIABLES: RGDIC                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the global root of the word-processing field
 being edited.  The contents of the word- processing field are loaded into the
 main buffer during editor initialization.  
  
VARIABLES: RGTTL                        TYPE: Input
 VARIABLES DESCRIPTION:   The title of the editing session, displayed in the
 upper left-hand corner of the screen. Replaceable parameters are allowed.  
  
VARIABLES: RGOBJ                        TYPE: Input
 VARIABLES DESCRIPTION:   The name of the object being edited, displayed in the
 upper right-hand corner of the screen.  Replaceable parameters are allowed.  
  
VARIABLES: RGCF                         TYPE: Input
 VARIABLES DESCRIPTION:   The name of the configuration that is to be invoked. 
 This is the name of the .01 field in the Extensible Editor file.  If not
 specified, the editor uses the DEFAULT configuration.  
  
VARIABLES: RGPID                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the instance identifier for the editor.  
 Normally, this parameter is not passed and defaults to the value of $JOB.  If
 the editor is invoked recursively (i.e., from within the editor itself), this
 parameter should be the current value of RGPID.  The editor adds .0001 to this
 value to maintain a unique context across all instances.  
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 2798                            IA #: 2798
  DATE CREATED: APR 06, 1999            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: VAFCPTAD                     NAME: $$ADD VAFCPTAD(ARRAY)
  ID: VAFCPTAD
 GENERAL DESCRIPTION:   MPIF is requesting to add a patient to the patient file
 via the call $$ADD^VAFCPTAD(ARRAY).  
  
 This call will happen when a list of potential matches has been displayed to
 the user after requesting an ICN assignment from the MPI and the user has
 selected from this list (list came from the MPI) a patient that would be new
 to the local patient file.  
  STATUS: Retired
COMPONENT/ENTRY POINT: $$ADD
 COMPONENT DESCRIPTION:   $$ADD^VAFCPTAD(ARRAY) will allow MPIF to add a
 patient to the local patient file passing the data known in the array input
 variable.  The data known would be name, date of birth and SSN. The IEN of the
 entry created in the Patient file is returned.  
VARIABLES: array
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   ARRAY - is an array variable, subscripted by the
 field number of the values passed.  This data is used to create the patient in
 the patient file.  
VARIABLES: DFN                          TYPE: Output
 VARIABLES DESCRIPTION:   DFN is returned as the IEN of the Patient file entry
 that was created in the session.  
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA

NUMBER: 2799                            IA #: 2799
  DATE CREATED: APR 16, 1999            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMTSLRSE
  NAME: DBIA2799                        ID: GMTSLRSE
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: GMTSLRSE
KEYWORDS: LABORATORY
COMPONENT/ENTRY POINT: XTRCT
 COMPONENT DESCRIPTION:   Call with: 
  LRDFN, GMTS1, GMTS2, MAX (Occ. Limit), SEX ("M" or "F"), 
  TEST  (IFN to ^LAB(60)) and RWIDTH (optional) 
  
 where: 
   LRDFN=Lab DFN, GMTS1=start date, GMTS2=end date, MAX=maximum 
   number of results to return, SEX="M" or "F", TEST=Lab test, 
   RWIDTH=width of variable 
  
 Returns: 
   ^TMP("LRS",$J,GMTSI,IDRWDT)=DRWDT^SPEC^TEST^RESULT^FLAG^UNIT^ 
    LO^HI 
  
 where: 
   GMTSI=Order (1 to MAX) and IDRWDT=9999999-Draw Date/time, 
   DRWDT=Draw Date/Time (internal), SPEC=Specimen (int;ext), 
   TEST=Test (int;ext), RESULT=Numeric Result, FLAG=Reference 
   flag (H,*H,L,*L), UNIT=Unit of measure (ext), 
   LO=Reference/Therapeutic Lower bound, HI=Ref/Ther Upper 
   Bound 
  
  
VARIABLES: LRDFN                        TYPE: Input
VARIABLES: GMTS1                        TYPE: Input
VARIABLES: GMTS2                        TYPE: Input
VARIABLES: GMTSI                        TYPE: Input
VARIABLES: MAX                          TYPE: Input
VARIABLES: TEST                         TYPE: Input
VARIABLES: RWIDTH                       TYPE: Input
VARIABLES: TMP(LRS,$J,GMTSI,IDRWDT)     TYPE: Output
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clinical Reminders would like to use a call to
 XTRCT^GMTSLRSE to obtain lab results. These results are used in the evaluation
 of laboratory findings for Clinical Reminders.  
  

NUMBER: 2800                            IA #: 2800
  FILE NUMBER: 40.8                     GLOBAL ROOT: DG(40.8,
  DATE CREATED: APR 14, 1999            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA2800
  ID: DG(40.8,
 GENERAL DESCRIPTION:   In order to accommodate multi-divisional sites, three
 files have been modified to include references to the MEDICAL CENTER DIVISION
 file (#40.8).  
  
 The files and fields are: 
  
        1. ESP DAILY JOURNAL FILE (#916) 
             field  # .5   FACILITY (P40.8') 
  
        2. ESP POLICE REGISTRATION LOG FILE (#910.2) 
                    field  # .08       FACILITY (P40.8') 
  
        3. ESP EVIDENCE FILE (#910.8) 
             field  # .05       FACILITY (P40.8') 
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: POLICE & SECURITY  ISC: Albany

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
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,<dfn>,<notif id>;<triggering user>;<alert date/time> 
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
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,<dfn>,<notif id>;<triggering user>;<alert date/time> 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 2803                            IA #: 2803
  FILE NUMBER: 405                      GLOBAL ROOT: DGPM(
  DATE CREATED: APR 16, 1999            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA2803
  ID: DGPM(
GLOBAL REFERENCE: DGPM(DO,0
FIELD NUMBER: .03                       FIELD NAME: PATIENT
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: WARD
  ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPM('ATT1'
 GLOBAL DESCRIPTION:   Direct global read to 'ATT1' cross reference.  
 GENERAL DESCRIPTION:   The Clinical Reminder Package would like to reference
 the PATIENT MOVEMENT file #405 directly to identify current inpatients and
 admissions within a date range for individual wards.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: INPATIENT WARD
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  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
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
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
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

NUMBER: 2807                            IA #: 2807
  FILE NUMBER: 1                        GLOBAL ROOT: DD(
  DATE CREATED: APR 25, 1999            CUSTODIAL PACKAGE: 1
  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
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
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
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
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
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.  
  
 Revision History 
  4/10/24: A new parameter (CNTSCND) was added to control if the API should 
  count documents that reference the Visit via the Secondary Visit field.  
  When the parameter is not passed in, it will behave as it did previously 
  (it will not include those document counts).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DOCCNT(TIUY,DFN,VSTR,VSIT,CNTSCND)
 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
 IEN.  
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 IEN.  
VARIABLES: CNTSCND                      TYPE: Input
 VARIABLES DESCRIPTION:   Controls if API should count documents that reference
 the Visit via the SECONDARY VISIT field. (Possible values: 1/0; Optional;
 Defaults to 0).  
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 
              appended 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 
              appended 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
  DATE ACTIVATED: APR 10, 2024

NUMBER: 2813                            IA #: 2813
  FILE NUMBER: 8925.1                   GLOBAL ROOT: DD(8925.1,0,'ID'
  DATE CREATED: APR 30, 1999            CUSTODIAL PACKAGE: 1
  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
KEYWORDS: TIU*1*38
KEYWORDS: ID NODE
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 2815                            IA #: 2815
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT(81
  DATE CREATED: MAY 05, 1999            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CPT FILE POINTERS
  ID: ICPT(81
GLOBAL REFERENCE: ICPT(
FIELD NUMBER: .01                       FIELD NAME: CPT CODE
  LOCATION: 0;1                         ACCESS: Pointed to
 FIELD DESCRIPTION:   May be pointed to by other packages' files.  
 GENERAL DESCRIPTION:   Now covered by supported ICR #5408,CPT/HCPCS Procedure
 File 81.This agreement will allow other packages' files to point to file #81, 
 CPT file.  
  
 Direct read of the "B" cross-reference will also be permitted.  
  
 Direct read of the "ACT" cross-reference will also be permitted.  
  
 This, along with DBIAs 1995-1997 will replace IA 10084, which will be 
 inactivated as of June, 2000.  
  STATUS: Retired                       EXPIRATION DATE: JAN 09, 2015
KEYWORDS: CPT

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,
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
KEYWORDS: CPT
KEYWORDS: MODIFIER

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
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 
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 10/19/2020.  
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   Added 9/17/21 to document a previously released patch
 with the routine ECXMTL which accesses the ^DG(40.8,"AD" for the Mental Health
 extract. This extract was disabled, so the code is not currently used in the
 field, but this ICR documents the access. The missing ICR was found during the 
 review of ECX*3*181.  

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
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
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

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: ACCESS TO PTF RELEASE (#45.83) FILE
  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.  
GLOBAL REFERENCE: DGP(45.83,'C',
 GLOBAL DESCRIPTION:   The 'C' cross reference is used to look up the PTF
 records associated with the PTF Release (#45.83) file.The 'C' cross reference
 is a whole file cross reference on the Record (#.01) field in the PTF Record
 (#10) subfile in the PTF Release (#45.83) 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
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
  DATE ACTIVATED: APR 09, 2018

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
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 2821                            IA #: 2821
  FILE NUMBER: .84                      DATE CREATED: AUG 09, 1999
  CUSTODIAL PACKAGE: 1                  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
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: 2822                            IA #: 2822
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDOEUT
  NAME: DBIA2822                        ID: SDOEUT
 GENERAL DESCRIPTION:   This call is needed to determine if data passed to IB
 is from the OUTPATIENT ENCOUNTER file or from PCE.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$OLD(SDOE)
 COMPONENT DESCRIPTION:   Returns true if an opt encounter is stored in
 OUTPATIENT ENCOUNTER (409.68) rather than PCE.  
VARIABLES: SDOE                         TYPE: Input
 VARIABLES DESCRIPTION:   IFN of encounter, pointer to 409.68 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

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
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
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
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.  

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
 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
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

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
 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
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 - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   ADDED 11/16/2010 

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
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
COMPONENT/ENTRY POINT: $$CWAD(DFN)
 COMPONENT DESCRIPTION:   Returns letters C, W, A, D, P, L 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 six 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, D if the patient has advance directives, P if the patient is
 pregnant and L if the patient is breastfeeding.  
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
  DATE ACTIVATED: JUL 06, 2018

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
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
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
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  

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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   
  "time to live" -->  1 Sep 2004 
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIABDX SAVE RPC will be accessing the ID (#2) field in
 the Orderable Items (#101.43) file.  

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
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  ISC: Salt Lake City

NUMBER: 2837                            IA #: 2837
  DATE CREATED: JUN 10, 1999            CUSTODIAL PACKAGE: RPC BROKER
  USAGE: Private                        TYPE: Other
  NAME: RPC Broker Programmatic Login
 GENERAL DESCRIPTION:   The Event Monitor Service at VAPSHCS monitors incoming
 HL7 messages so as to implement automated medical alerts and reminders. The
 application must run as a Windows NT Service in unattended mode.  The Event
 Monitor Service extensively utilizes RPC Broker when implementing medical
 alerts. As a consequence, I am requesting to use the undocumented "silent
 login" feature released in XWB*1.1*4 until such time when an official Broker
 patch supporting this functionality is released.  
  STATUS: Withdrawn

NUMBER: 2838                            IA #: 2838
  DATE CREATED: JUN 01, 1999            CUSTODIAL PACKAGE: RPC BROKER
  USAGE: Supported                      TYPE: Other
  NAME: RPC Broker Silent Feature
 GENERAL DESCRIPTION:   This request is for a new broker "silent running"
 feature.  This feature, when enabled, would dictate that under no 
 circumstances should the broker display message dialogs to the user. A
 possible method of accomplishing this task would be to add an RPC Broker
 boolean property, that, when set to true, disables the display of all user
 dialogs. It is suggested that when the silent property is set, that the the
 broker, as an alternative to displaying a message, merely throw an equivalent
 silent exception.  This feature will allow use of the broker by Windows NT
 services that need to run in unattended mode.  
  STATUS: Withdrawn

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
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
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. 
  
 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: Retired                       EXPIRATION DATE: JUN 01, 2006
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
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,
GLOBAL REFERENCE: ORD(101.43,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ID 
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: CODE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: CODING SYSTEM
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ORD(101.43,D0,.1)
FIELD NUMBER: .1                        FIELD NAME: INACTIVATED
  LOCATION: .1;1                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This agreement allows read access to the Orderable
 Items file #101.43.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Added 11/6/19 for access to NAME (.01 field of
 ORD(101.43,D0,0) global reference, effective with RA*5*161.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 1/19/23, effective with DSSV 1.1 DSS Class 3
 product Document Only 
  DATE ACTIVATED: JUN 22, 2015

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: 1.1                       FIELD NAME: PATIENT LOCATION
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ORDER TYPE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 100                       FIELD NAME: RELATED INSTITUTION
  LOCATION: INI;1                       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
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.  
  DATE ACTIVATED: JAN 29, 2020

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: 5                         FIELD NAME: CLINIC
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 26                        FIELD NAME: EXPIRATION DATE
  LOCATION: 2;6                         ACCESS: Direct Global Read & w/Fileman
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: 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
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.  
  DATE ACTIVATED: JAN 29, 2020

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
COMPONENT/ENTRY POINT: BAT()
SUBSCRIBING PACKAGE: RPC BROKER         ISC: Oakland

NUMBER: 2847                            IA #: 2847
  DATE CREATED: JUN 16, 1999            CUSTODIAL PACKAGE: 1
  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
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
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
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 2850                            IA #: 2850
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: SDAM1
  NAME: TIU use of SDAM1                ID: SDAM1
 GENERAL DESCRIPTION:   TIU calls $$STATUS^SDAM1 to retrieve the status of an
 appointment.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$STATUS
 COMPONENT DESCRIPTION:   STATUS(DFN,SDT,SDCL,SDATA,SDDA) ; -- return appt
 status 
   input: DFN := ifn of pat.  
          SDT := appt d/t 
          SDCL := ifn of clinic 
          SDATA := 0th node of pat appt entry 
          SDDA := ifn for ^SC(clinic,"S",date,1,ifn) -optional 
         
   output: [returned] := appt status ifn ^ status name 
                         ^ print status ^ check in d/t 
                         ^ check out d/t ^ adm mvt ifn 
  
   S = status ; C = ci/co indicator ; Y = 'C' node ; 
   P = print status 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

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
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 2852                            IA #: 2852
  FILE NUMBER: 52                       GLOBAL ROOT: DD(52
  DATE CREATED: JUN 10, 2003            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: Setting ID node (file #52)      ID: DD(52
 GENERAL DESCRIPTION:   Permission to re-set an ID node in file 52.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: ID node
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
 SUBSCRIBING DETAILS:   This request is to allow the Outpatient Pharmacy
 package to re-set an identifier node in the Prescription (#52) file,
 DD(52,0,"ID",6).  In prior versions this node referenced a field that has now
 been moved to a new location within the file.  
  
 This change will be used in patch PSO*7*25 only.  

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
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
KEYWORDS: STATUS PSU
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham

NUMBER: 2855                            IA #: 2855
  DATE CREATED: JUN 24, 1999            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Remote Procedure                NAME: RPCBroker.AccessVerifyCodes
 GENERAL DESCRIPTION:   I am using this call in the RPC Broker for a "silent
 login" to VistA for an Active Server Page DLL component.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
  EXPIRATION DATE: SEP 21, 2001
KEYWORDS: AccessVerifyCodes
KEYWORDS: LOGIN
KEYWORDS: ASP
KEYWORDS: MTS

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
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

NUMBER: 2857                            IA #: 2857
  DATE CREATED: JUN 29, 1999            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: XUS GET USER INFO
  REMOTE PROCEDURE: XUS GET USER INFO
 GENERAL DESCRIPTION:   This rpc is used by BROKER to maintain a User object in
 the Delphi environment.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RPC BROKER         ISC: Oakland
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 8/4/18.  
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   Added 9/27/19 
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 6/9/23. CDSP is developing a CPRS COM extension
 to capture user generated events to trigger clinical decision support
 applications. CDSP is utilizing solutions based on FHIR, SMART on FHIR and CDS
 Hooks standards. CDSP needs to get information about the active user from 
 within the COM object. 
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 3/23/26, effective with DSIY*1.4*0 released
 2/8/19 APAR granted approval based on the historic usage.  

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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
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
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
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  ISC: Hines
 SUBSCRIBING DETAILS:   The DATE ENTERED value will be determined from a
 GET1^DIQ call.  

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
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.  

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
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.  

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
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).  
COMPONENT/ENTRY POINT: $$PERSLOC(USER)
 COMPONENT DESCRIPTION:   This extrinsic function returns the encounter
 location (#44) from the LOCATION BY DAY OF WEEK multiple field (#1) in the
 file TIU PERSONAL PREFERENCES (#8926) for a user based upon the current day of
 the week.  If there is no location for that specific day, the function will
 return the value from the field DEFAULT LOCATION (#.02).  The extrinsic
 function value returned will be in the format: 
    0  -or-   [file_44_ien] ^ [Hospital Location Name] 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   added 3/24/2008 
  DATE ACTIVATED: APR 24, 2017

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
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)
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 11/19/18 for VPR*1.0*8.  

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
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 10/7/22, effective with SD*5.3*827. The VSE team
 is working on an enhancement where a new RPC, SDES GET TIU DOC BY CONTEXT, is
 created to retrieve TIU data tied to the location/clinic ID.  

NUMBER: 2866                            IA #: 2866
  DATE CREATED: JUL 13, 1999            CUSTODIAL PACKAGE: 1
  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
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: 1
  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
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: 1
  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
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: 1
  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
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: 1
  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
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: 1
  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
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: 1
  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
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: 1
  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
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: 1
  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
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
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) 
  
 Revisions: 9/13/23: Component $$BOIL^TIUSRVD added for use by OE/RR 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BOIL
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: 
  
        <Hospital Location>;<Visit Date/Time>;<Service Category> 
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.  
COMPONENT/ENTRY POINT: BOIL
 COMPONENT DESCRIPTION:   $$BOIL is an extrinsic function that is used
 internally by BLRPLT in TIUSRVD.  
VARIABLES: LINE                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the executed boilerplate text.  
VARIABLES: COUNT                        TYPE: Input
 VARIABLES DESCRIPTION:   COUNT does not appear to be in use 
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 DETAILS:   Revised on 9/13/23: CPRS Sustainment added
 $$BOIL^TIUSRVD to this subscription for OE/RR, effective with patch OR*3.0*603
 or OR*3*535, to make it SAC compliant with previous usage of $$BOIL^TIUSRVD.  
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
 SUBSCRIBING DETAILS:   ADDED 8/26/09 
  DATE ACTIVATED: SEP 13, 2023

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
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: 1                  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
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
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
KEYWORDS: BCMA
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN

NUMBER: 2881                            IA #: 2881
  DATE CREATED: JUL 29, 1999            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: SCMCHLZ
  NAME: DBIA2881                        ID: SCMCHLZ
 GENERAL DESCRIPTION:   Contains the supported reference to routine SCMCHLZ for
 the supported API to be released with PCMM patch SD*5.3*177.  
  STATUS: Pending
COMPONENT/ENTRY POINT: ZPC
 COMPONENT DESCRIPTION:   This entry point is an extrinsic function that
 returns an HL7 ZPC segment string.  
   Example: S VAFZPC=$$ZPC^SCMCHLZ("",ID,DATA) 
VARIABLES: SCSTR                        TYPE: Input
 VARIABLES DESCRIPTION:   String of fields requested, separated by commas. If
 null, return all fields.  
VARIABLES: SCID                         TYPE: Input
 VARIABLES DESCRIPTION:   Provider Assignment ID. Unique ID string that Austin
 uses for the key field.  
VARIABLES: SCDATA                       TYPE: Input
 VARIABLES DESCRIPTION:   String containing the following information in the
 following "^" pieces: 
  
   Piece  Description 
   -----  ----------------------------------------
   1      Provider IEN for NEW PERSON file (#200) 
   2      Date provider assigned 
   3      Date provider unassigned 
   4      Provider type (AP or PCP) 
  
 If alll pieces are null (""), Austin will do a delete.  Examples:  
 3^2980605^2990203^PCP 
             6^2980605^2990203^AP 
             ""^""^""^"" (deletion) 

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
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(<string>) The  <string> is
 the users <access code;verify code>.  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:   Added 03/03/2011 

NUMBER: 2883                            IA #: 2883
  FILE NUMBER: 727.5                    GLOBAL ROOT: ECX(727.5,
  DATE CREATED: AUG 10, 1999
  CUSTODIAL PACKAGE: DSS - DECISION SUPPORT SYSTEM 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
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
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 - DECISION SUPPORT SYSTEM 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 - DECISION SUPPORT SYSTEM 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
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: 2886                            IA #: 2886
  DATE CREATED: AUG 11, 1999            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Other
  NAME: Supported DataBase Server DIALOG Numbers
 GENERAL DESCRIPTION:   The listed components are the supported DIALOG numbers
 that are associated with the DataBase Server calls and maybe used with the
 following supported DIALOG calls: 
  
 BLD^DIALOG $$EZBLD^DIALOG MSG^DIALOG 
  STATUS: Withdrawn
KEYWORDS: Data Base Server
KEYWORDS: DIALOG
COMPONENT/ENTRY POINT: 110
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   An attempt to get a lock timed out.  The record is locked and
 the desired action cannot be taken until the lock is released.  
  TEXT:   
  The record is currently locked.  PARAMETER SUBSCRIPT: FILE 
   PARAMETER DESCRIPTION: File or subfile #.  PARAMETER SUBSCRIPT: IENS 
   PARAMETER DESCRIPTION: IEN string of entry numbers.  ROUTINE NAME: DIE       
                LINE TAG: FILE 
COMPONENT/ENTRY POINT: 111
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   An attempt to get a lock timed out. The File Header Node is
 locked, and the desired action cannot be taken until the lock is released.  
  TEXT:   
  The File Header Node is currently locked.  PARAMETER SUBSCRIPT: FILE          
     PARAMETER DESCRIPTION: File #.  ROUTINE NAME: 0 
COMPONENT/ENTRY POINT: 120
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   An error occurred during the Xecution of a FileMan hook (e.g.,
 an input transform, DIC screen).  The type of hook in which the error occurred
 is identified in the text.  When relevant, the file, field, and IENS for which
 the hook was being Xecuted are identified in the PARAM nodes.  The substance
 of the error will usually be identified by a separate error message generated
 during the Xecution of the hook itself.  That error will usually be the one
 preceding this one in the DIERR array.  
  TEXT:   
  The previous error occurred when performing an action specified in a |1|.  
 PARAMETER SUBSCRIPT: 1 
   PARAMETER DESCRIPTION: Type of FileMan Xecutable code.  PARAMETER SUBSCRIPT:
 FILE               PARAMETER DESCRIPTION: File# PARAMETER SUBSCRIPT: FIELD     
         PARAMETER DESCRIPTION: Field#.  PARAMETER SUBSCRIPT: IENS 
   PARAMETER DESCRIPTION: Internal Entry Number String.  
COMPONENT/ENTRY POINT: 200
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   There is an error in one of the variables passed to a FileMan
 call or in one of the parameters passed in the actual parameter list.  
  TEXT:   
  An input variable or parameter is missing or invalid.  
COMPONENT/ENTRY POINT: 202
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The specified parameter is either required but missing or 
  invalid.  
  TEXT:   
  The input parameter that identifies the |1| is missing or invalid.  PARAMETER
 SUBSCRIPT: 1 
   PARAMETER DESCRIPTION: Parameter as identified in the FM documentation.  
 ROUTINE NAME: DIT                       LINE TAG: TRNMRG 
COMPONENT/ENTRY POINT: 204
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   Control characters are not permitted in the database.  
  TEXT:   
  The input value contains control characters.  PARAMETER SUBSCRIPT: 1          
        PARAMETER DESCRIPTION: INPUT VALUE 
COMPONENT/ENTRY POINT: 205
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   Error message output when a file or subfile number, and its
 associated IEN string are not in sync.  (I.E., the number of comma pieces
 represented by the IEN string do not match the file/subfile level according to
 the "UP" nodes.  
  TEXT:   
  File# |1| and IEN string |IENS| represent different subfile levels.  
 PARAMETER SUBSCRIPT: 1 
   PARAMETER DESCRIPTION: File or subfile number PARAMETER SUBSCRIPT: IENS      
         PARAMETER DESCRIPTION: IEN string ROUTINE NAME: DIT3                   
   LINE TAG: IENCHK ROUTINE NAME: DICA3                     LINE TAG: ERR 
COMPONENT/ENTRY POINT: 206
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: Multi. Term Lookup (MTLU) 
  DESCRIPTION:   FileMan is trying to pack fields onto a single node for a 
  record, and the data will not fit. The application has asked for too many 
  fields back for this record.  
  TEXT:   
  The data requested for record |1| is too long to pack together.  PARAMETER
 SUBSCRIPT: 1                  PARAMETER DESCRIPTION: Record Number.  
COMPONENT/ENTRY POINT: 207
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: Multi. Term Lookup (MTLU) 
  DESCRIPTION:   The library function $$HTML^DILF can encode or decode a string
 to and from HTML, used within FileMan to pack a value containing embedded ^s
 into a ^-delimited string. Encoding increases the length of the string. If
 encoding would cause the length to exceed the portable string length limit,
 $$HTML^DILF instead returns this error.  
  TEXT:   
  The value |1| is too long to encode into HTML.  PARAMETER SUBSCRIPT: 1        
          PARAMETER DESCRIPTION: Value.  
COMPONENT/ENTRY POINT: 299
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   A lookup that was restricted to finding a single entry found
 more than one.  
  TEXT:   
  More than one entry matches the value '|1|'.  PARAMETER SUBSCRIPT: 1          
        PARAMETER DESCRIPTION: Lookup Value.  PARAMETER SUBSCRIPT: FILE         
      PARAMETER DESCRIPTION: File #.  PARAMETER SUBSCRIPT: IENS              
 PARAMETER DESCRIPTION: IEN String.  
COMPONENT/ENTRY POINT: 301
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   Flags passed in a variable (like DIC(0)) or in a parameter are
 incorrect.  
  TEXT:   
  The passed flag(s) '|1|' are unknown or inconsistent.  PARAMETER SUBSCRIPT: 1 
   PARAMETER DESCRIPTION: Letter(s) from flag.  
COMPONENT/ENTRY POINT: 302
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The calling application has asked us to add a new record, and
 has supplied a record number, but a record already exists at that number.  
  TEXT:   
  Entry '|IENS|' already exists.  PARAMETER SUBSCRIPT: FILE              
 PARAMETER DESCRIPTION: File #.  PARAMETER SUBSCRIPT: IENS              
 PARAMETER DESCRIPTION: IEN String.  
COMPONENT/ENTRY POINT: 304
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The problem with this IEN string is that it lacks the final
 ','. This is a common mistake for beginners.  
  TEXT:   
  The IENS '|IENS|' lacks a final comma.  PARAMETER SUBSCRIPT: IENS             
  PARAMETER DESCRIPTION: IENS.  
COMPONENT/ENTRY POINT: 305
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   A root is used to identify an input array.  But the array is
 empty.  
  TEXT:   
  The array with a root of '|1|' has no data associated with it.  PARAMETER
 SUBSCRIPT: 1                  PARAMETER DESCRIPTION: Passed root.  ROUTINE
 NAME: DIE                       LINE TAG: FILE 
COMPONENT/ENTRY POINT: 306
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   When an IENS is used to explicitly identify a subfile, not a
 subfile entry, then the first comma-piece should be empty. This one wasn't.  
  TEXT:   
  The first comma-piece of IENS '|IENS|' should be empty.  PARAMETER SUBSCRIPT:
 IENS               PARAMETER DESCRIPTION: IENS.  
COMPONENT/ENTRY POINT: 307
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   One of the IENs in the IENS has been left out, leaving an 
 empty comma-piece.  
  TEXT:   
  The IENS '|IENS|' has an empty comma-piece.  PARAMETER SUBSCRIPT: IENS        
       PARAMETER DESCRIPTION: IENS.  
COMPONENT/ENTRY POINT: 308
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The syntax of this IENS is incorrect. For example, a record
 number may be illegal; or a subfile may be specified as already existing, but
 have a parent that is just now being added.  
  TEXT:   
  The IENS '|IENS|' is syntactically incorrect.  PARAMETER SUBSCRIPT: IENS      
         PARAMETER DESCRIPTION: IENS.  
COMPONENT/ENTRY POINT: 309
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   A multiple field is involved.  Either the root of the multiple
 or the necessary entry numbers are missing.  
  TEXT:   
  There is insufficient information to identify an entry in a subfile.  
COMPONENT/ENTRY POINT: 310
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   Some of the IENS subscripts in this FDA conflict with each 
 other. For example, one IENS may use the sequence number ?1 while another uses
 +1.  This would be illegal because the sequence number 1 is being used to
 represent two different operations. Consult your documentation for an
 explanation of the various conflicts possible. The IENS returned with this
 error happens to be one of the IENS values in conflict.  
  TEXT:   
  The IENS '|IENS|' conflicts with the rest of the FDA.  PARAMETER SUBSCRIPT:
 IENS               PARAMETER DESCRIPTION: IENS.  
COMPONENT/ENTRY POINT: 311
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   Adding an entry to a file without including all required 
 identifiers violates database integrity. The entry identified by this IENS 
 lacks some of its required identifiers in the passed FDA.  
  TEXT:   
  The new record '|IENS|' lacks some required identifiers.  PARAMETER
 SUBSCRIPT: IENS               PARAMETER DESCRIPTION: IENS.  
COMPONENT/ENTRY POINT: 330
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The value passed by the calling application should be a 
 certain data type, but according to our checks it is not.  
  TEXT:   
  The value '|1|' is not a valid |2|.  PARAMETER SUBSCRIPT: 1                 
 PARAMETER DESCRIPTION: Passed Value.  PARAMETER SUBSCRIPT: 2                 
 PARAMETER DESCRIPTION: Data Type.  
COMPONENT/ENTRY POINT: 348
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The calling application passed us a variable pointer value.
 That value points to a file that does not exist, or that lacks a Header Node.  
  TEXT:   
  The passed value '|1|' points to a file that does not exist or lacks a 
  Header Node.  PARAMETER SUBSCRIPT: 1                  PARAMETER DESCRIPTION:
 Passed Value.  
COMPONENT/ENTRY POINT: 351
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   When passing an FDA to the Updater, any entries intended as
 Finding or LAYGO Finding nodes must include a .01 node that has the lookup
 value.  This value need not be a legitimate .01 field value, but it must be a
 valid and unambiguous lookup value for the file.  
  TEXT:   
  FDA nodes for lookup '|IENS|' omit a .01 node with a lookup value.  PARAMETER
 SUBSCRIPT: FILE               PARAMETER DESCRIPTION: File #.  PARAMETER
 SUBSCRIPT: IENS 
   PARAMETER DESCRIPTION: IENS Subscript for Finding or LAYGO Finding node.  
COMPONENT/ENTRY POINT: 352
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: Multi. Term Lookup (MTLU) 
  DESCRIPTION:   When passing an FDA to the Updater, any entries intended as
 LAYGO or LAYGO Findings nodes must include a .01 node. Every new entry must
 have a value for the .01 field.  
  TEXT:   
  The new record '|IENS|' for file #|FILE| lacks a .01 field.  PARAMETER
 SUBSCRIPT: FILE               PARAMETER DESCRIPTION: File number.  PARAMETER
 SUBSCRIPT: IENS 
   PARAMETER DESCRIPTION: IENS subscript for LAYGO or LAYGO Finding node.  
COMPONENT/ENTRY POINT: 401
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The specified file or subfile does not exist; it is not 
 present in the data dictionary.  
  TEXT:   
  File #|FILE| does not exist.  PARAMETER SUBSCRIPT: FILE              
 PARAMETER DESCRIPTION: File number.  
COMPONENT/ENTRY POINT: 402
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The specified file or subfile lacks a valid global root; the
 global root is missing or is syntactically not valid.  
  TEXT:   
  The global root of file #|FILE| is missing or not valid.  PARAMETER
 SUBSCRIPT: FILE               PARAMETER DESCRIPTION: File number.  PARAMETER
 SUBSCRIPT: ROOT               PARAMETER DESCRIPTION: File root.  PARAMETER
 SUBSCRIPT: IENS               PARAMETER DESCRIPTION: IEN String.  
COMPONENT/ENTRY POINT: 403
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The File Header Node, the top level of the data file as 
 described in the Programmer Manual, must be present for FileMan to determine
 certain kinds of information about a file.  
  TEXT:   
  File #|FILE| lacks a Header Node.  PARAMETER SUBSCRIPT: FILE              
 PARAMETER DESCRIPTION: File #.  
COMPONENT/ENTRY POINT: 404
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   We have identified a file by the global node of its data file,
 and found its Header Node. We needed to use the Header Node to identify the
 number of the file, but that piece of information is missing from the Header
 Node.  
  TEXT:   
  The File Header node of the file stored at |1| lacks a file number.  
 PARAMETER SUBSCRIPT: 1                  PARAMETER DESCRIPTION: File Root.  
COMPONENT/ENTRY POINT: 405
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The NO EDIT flag is set for the file.  No instruction to 
  override that flag is present.  
  TEXT:   
  Entries in file |1| cannot be edited.  PARAMETER SUBSCRIPT: 1                 
 PARAMETER DESCRIPTION: File Name.  PARAMETER SUBSCRIPT: FILE              
 PARAMETER DESCRIPTION: File number.  
COMPONENT/ENTRY POINT: 406
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The data definition for a .01 field for the specified file is
 missing.  This file is therefore not valid for most database operations.  
  TEXT:   
  File #|FILE| has no .01 field definition.  PARAMETER SUBSCRIPT: FILE          
     PARAMETER DESCRIPTION: File #.  
COMPONENT/ENTRY POINT: 407
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The subfile number of a word processing field has been passed
 in the place of a file parameter. This is not acceptable. Although we
 implement word processing fields as independent files, we do not allow them to
 be treated as files for purposes of most database activities.  
  TEXT:   
  A word-processing field is not a file.  PARAMETER SUBSCRIPT: FILE 
   PARAMETER DESCRIPTION: Subfile # of word-processing field.  
COMPONENT/ENTRY POINT: 408
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The file lacks a name. For subfiles, $P(^DD(file#,0),U) is 
  null. For root files, $O(^DD(file#,0,"NM",""))="". 
  TEXT:   
  File# |FILE| lacks a name.  PARAMETER SUBSCRIPT: FILE               PARAMETER
 DESCRIPTION: File #.  
COMPONENT/ENTRY POINT: 420
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   A cross reference was specified for look-up, but that cross
 reference does not exist on the file. The file has entries, but the index does
 not.  This error implies nothing about whether the index is defined in the
 file's DD.  
  TEXT:   
  There is no |1| index for File #|FILE|.  PARAMETER SUBSCRIPT: 1 
   PARAMETER DESCRIPTION: Cross reference name.  PARAMETER SUBSCRIPT: FILE      
         PARAMETER DESCRIPTION: File number.  
COMPONENT/ENTRY POINT: 501
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   A search of the data dictionary reveals that the field name or
 number passed does not exist in the specified file.  
  TEXT:   
  File #|FILE| does not contain a field |1|.  PARAMETER SUBSCRIPT: 1 
   PARAMETER DESCRIPTION: Field name or number.  PARAMETER SUBSCRIPT: FILE      
         PARAMETER DESCRIPTION: File number.  PARAMETER SUBSCRIPT: FIELD        
      PARAMETER DESCRIPTION: Field number.  
COMPONENT/ENTRY POINT: 502
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The field has been identified, but some key part of its 
 definition is missing or corrupted. ^DD(file#,field#,0) may not be defined.
 Some key piece of that node may be missing.  
  TEXT:   
  Field# |FIELD| in file# |FILE| has a corrupted definition.  PARAMETER
 SUBSCRIPT: FILE               PARAMETER DESCRIPTION: File #.  PARAMETER
 SUBSCRIPT: FIELD              PARAMETER DESCRIPTION: Field #.  
COMPONENT/ENTRY POINT: 505
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The field name passed is ambiguous.  It cannot be determined
 to which field in the file it refers.  
  TEXT:   
  There is more than one field named '|1|' in File #|FILE|.  PARAMETER
 SUBSCRIPT: 1                  PARAMETER DESCRIPTION: Field name.  PARAMETER
 SUBSCRIPT: FILE               PARAMETER DESCRIPTION: File #.  
COMPONENT/ENTRY POINT: 510
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   For some reason, the data type for the specified field cannot
 be determined.  This may mean that the data dictionary is corrupted.  
  TEXT:   
  The data type for Field #|FIELD| in File #|FILE| cannot be determined.  
 PARAMETER SUBSCRIPT: FIELD              PARAMETER DESCRIPTION: Field number.  
 PARAMETER SUBSCRIPT: FILE               PARAMETER DESCRIPTION: File number.  
COMPONENT/ENTRY POINT: 520
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   An incorrect kind of field is being processed.  For example,
 filing is being attempted for a computed field or validation for a word
 processing field.  
  TEXT:   
  A |1| field cannot be processed by this utility.  PARAMETER SUBSCRIPT: 1 
   PARAMETER DESCRIPTION: Data type or other field characteristic (e.g., .001,
 DI NUMed).  PARAMETER SUBSCRIPT: FILE               PARAMETER DESCRIPTION:
 File #.  PARAMETER SUBSCRIPT: FIELD              PARAMETER DESCRIPTION: Field
 #.  ROUTINE NAME: DIE                       LINE TAG: FILE 
COMPONENT/ENTRY POINT: 537
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   This error means that a certain field in a certain file has a
 data type of pointer, but something is wrong with the rest of the DD info
 needed to make that pointer work. For example, perhaps the number of the
 pointed to file, which should follow the P in the second ^-piece of the field
 descriptor node, is missing. Another problem would be if the global root of
 the pointed to file were missing from the field's definition; that should be
 found in the third ^-piece of the field descriptor.  
  TEXT:   
  Field #|FIELD| in File #|FILE| has a corrupted pointer definition.  PARAMETER
 SUBSCRIPT: FILE               PARAMETER DESCRIPTION: File #.  PARAMETER
 SUBSCRIPT: FIELD              PARAMETER DESCRIPTION: Field #.  
COMPONENT/ENTRY POINT: 601
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The entry identified by FILE and IENS does not exist in the
 database.  
  TEXT:   
  The entry does not exist.  PARAMETER SUBSCRIPT: FILE 
   PARAMETER DESCRIPTION: File or subfile #. (external only) PARAMETER
 SUBSCRIPT: IENS 
   PARAMETER DESCRIPTION: IEN string (external only) 
COMPONENT/ENTRY POINT: 602
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   There is a -9 node for the entry; therefore, the entry cannot
 be accessed.  
  TEXT:   
  The entry is not available for editing.  PARAMETER SUBSCRIPT: FILE 
   PARAMETER DESCRIPTION: File or subfile #. (external only) PARAMETER
 SUBSCRIPT: IENS 
   PARAMETER DESCRIPTION: IEN string. (external only) 
COMPONENT/ENTRY POINT: 603
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   A specific entry in a specific file lacks a value for a 
  required field.  This error message returns which field is missing.  
  TEXT:   
  Entry #|1| in File #|FILE| lacks the required Field #|FIELD|.  PARAMETER
 SUBSCRIPT: 1                  PARAMETER DESCRIPTION: Entry #.  PARAMETER
 SUBSCRIPT: FILE               PARAMETER DESCRIPTION: File #.  PARAMETER
 SUBSCRIPT: FIELD              PARAMETER DESCRIPTION: Field #.  
COMPONENT/ENTRY POINT: 630
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The database is corrupted. The value for a specific field in
 one entry should be a certain data type, but it is not.  
  TEXT:   
  In Entry #|1| of File #|FILE|, the value '|2|' for Field #|FIELD| is not a
 valid |3|.  PARAMETER SUBSCRIPT: 1                  PARAMETER DESCRIPTION:
 Entry #.  PARAMETER SUBSCRIPT: 2                  PARAMETER DESCRIPTION: Field 
 Value.  PARAMETER SUBSCRIPT: 3                  PARAMETER DESCRIPTION: Data
 Type.  PARAMETER SUBSCRIPT: FIELD              PARAMETER DESCRIPTION: Field #. 
 
 PARAMETER SUBSCRIPT: FILE               PARAMETER DESCRIPTION: File #.  
COMPONENT/ENTRY POINT: 648
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The database is corrupted. In a specific variable pointer 
 field of a certain entry, the field's value points to a file that either does
 not exist or that lacks a Header Node.  
  TEXT:   
  In Entry #|1| of File #|FILE|, the value '|2|' for Field #|FIELD| points 
  to a file that does not exist or lacks a Header Node.  PARAMETER SUBSCRIPT: 1 
                 PARAMETER DESCRIPTION: Entry #.  PARAMETER SUBSCRIPT: 2        
          PARAMETER DESCRIPTION: Field Value.  PARAMETER SUBSCRIPT: FILE        
       PARAMETER DESCRIPTION: File #.  PARAMETER SUBSCRIPT: FIELD             
 PARAMETER DESCRIPTION: Field #.  
COMPONENT/ENTRY POINT: 701
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The value is invalid.  Possible causes include:  value did not
 pass input transform, value for a pointer or variable pointer field cannot be
 found in the pointed-to file, a screen was not passed.  
  TEXT:   
  The value '|3|' for field |1| in file |2| is not valid.  PARAMETER SUBSCRIPT:
 1                  PARAMETER DESCRIPTION: Field name.  PARAMETER SUBSCRIPT: 2  
                PARAMETER DESCRIPTION: File name.  PARAMETER SUBSCRIPT: 3 
   PARAMETER DESCRIPTION: Value that was found to be invalid.  PARAMETER
 SUBSCRIPT: FIELD 
   PARAMETER DESCRIPTION: Field number. (external only) PARAMETER SUBSCRIPT:
 FILE 
   PARAMETER DESCRIPTION: File number.  (external only) PARAMETER SUBSCRIPT:
 IENS 
   PARAMETER DESCRIPTION: IEN string identifying entry with invalid value.  
 (exter nal only, sometimes returned) ROUTINE NAME: DIE                      
 LINE TAG: FILE 
COMPONENT/ENTRY POINT: 703
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The value passed cannot be found in the indicated file using
 $$FIND1^DIC.  
  TEXT:   
  The value '|1|' cannot be found in file #|FILE|.  PARAMETER SUBSCRIPT: FILE   
            PARAMETER DESCRIPTION: File #.  PARAMETER SUBSCRIPT: IENS           
    PARAMETER DESCRIPTION: IEN String.  PARAMETER SUBSCRIPT: 1                 
 PARAMETER DESCRIPTION: Lookup Value.  
COMPONENT/ENTRY POINT: 710
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The data dictionary specifies that the field is uneditable.
 Data already exists in the field.  It cannot be changed.  
  TEXT:   
  Data in Field #|FIELD| in File #|FILE| cannot be edited.  PARAMETER
 SUBSCRIPT: FIELD              PARAMETER DESCRIPTION: Field number.  PARAMETER
 SUBSCRIPT: FILE               PARAMETER DESCRIPTION: File number.  
COMPONENT/ENTRY POINT: 712
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   The value of a field cannot be deleted either because it is a
 required field, because it is the .01 of a file, or because the test in the
 "DEL" node was not passed.  
  TEXT:   
  The value of field |1| in file |2| cannot be deleted.  PARAMETER SUBSCRIPT: 1 
                 PARAMETER DESCRIPTION: Field name.  PARAMETER SUBSCRIPT: 2     
             PARAMETER DESCRIPTION: File name.  PARAMETER SUBSCRIPT: FIELD 
   PARAMETER DESCRIPTION: Field number.  (external only) PARAMETER SUBSCRIPT:
 FILE 
   PARAMETER DESCRIPTION: File number.  (external only) ROUTINE NAME: DIE       
                LINE TAG: FILE ROUTINE NAME: DIE2 
COMPONENT/ENTRY POINT: 726
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   There is an attempt to take an action with word processing 
  data, but the specified field is not a word processing field.  
  TEXT:   
  Field #|FIELD| in File #|FILE| is not a word processing field.  PARAMETER
 SUBSCRIPT: FIELD              PARAMETER DESCRIPTION: Field number.  PARAMETER
 SUBSCRIPT: FILE               PARAMETER DESCRIPTION: File number.  
COMPONENT/ENTRY POINT: 730
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   Based on how the data type is defined by a specific field in a
 specific file, the passed value is not valid.  
  TEXT:   
  The value '|1|' is not a valid |2| according to the definition in Field 
  #|FIELD| of File #|FILE|.  PARAMETER SUBSCRIPT: 1                  PARAMETER
 DESCRIPTION: Passed Value.  PARAMETER SUBSCRIPT: 2                  PARAMETER
 DESCRIPTION: Data Type.  PARAMETER SUBSCRIPT: FIELD              PARAMETER
 DESCRIPTION: Field #.  PARAMETER SUBSCRIPT: FILE               PARAMETER
 DESCRIPTION: File #.  
COMPONENT/ENTRY POINT: 740
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: Multi. Term Lookup (MTLU) 
  DESCRIPTION:   When one or more fields are declared as a key for a file, 
 there cannot be duplicate values in those field(s) for entries in the file.
 The values being passed for validation, when combined with values for
 unchanging fields in the entry if necessary, create a duplicate key.  The
 changes destroy the integrity of the key.  Therefore, they are invalid.  
  TEXT:   
  New values are invalid because they create a duplicate Key '|1|' for the |2|
 file.  PARAMETER SUBSCRIPT: 1                  PARAMETER DESCRIPTION: Name of 
 Key.  PARAMETER SUBSCRIPT: 2 
   PARAMETER DESCRIPTION: Name of affected file.  PARAMETER SUBSCRIPT: FILE     
          PARAMETER DESCRIPTION: File number.  PARAMETER SUBSCRIPT: KEY 
   PARAMETER DESCRIPTION: IEN of the invalid key.  PARAMETER SUBSCRIPT: IENS 
   PARAMETER DESCRIPTION: IENS of record with invalid key.  
COMPONENT/ENTRY POINT: 742
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: Multi. Term Lookup (MTLU) 
  DESCRIPTION:   Every field in a key must have a value.  The incoming data 
  cannot delete the value for any field in a key.  
  TEXT:   
  The value of field |1| in the |2| file cannot be deleted because that field
 is part of the '|3|' key.  PARAMETER SUBSCRIPT: 1                  PARAMETER
 DESCRIPTION: Field name PARAMETER SUBSCRIPT: 2                  PARAMETER
 DESCRIPTION: File name PARAMETER SUBSCRIPT: 3                  PARAMETER
 DESCRIPTION: Key name PARAMETER SUBSCRIPT: FILE               PARAMETER
 DESCRIPTION: File number.  PARAMETER SUBSCRIPT: FIELD              PARAMETER
 DESCRIPTION: Field number.  PARAMETER SUBSCRIPT: IENS               PARAMETER
 DESCRIPTION: IENS 
COMPONENT/ENTRY POINT: 744
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: Multi. Term Lookup (MTLU) 
  DESCRIPTION:   Every field that is in a key must have a value.  No value for
 this field exists.  
  TEXT:   
  Field |1| is part of Key '|2|', but the field has not been assigned a value.  
 PARAMETER SUBSCRIPT: 1                  PARAMETER DESCRIPTION: Field name.  
 PARAMETER SUBSCRIPT: 2                  PARAMETER DESCRIPTION: Key name.  
 PARAMETER SUBSCRIPT: FIELD              PARAMETER DESCRIPTION: Field number.  
 PARAMETER SUBSCRIPT: FILE               PARAMETER DESCRIPTION: File number.  
 PARAMETER SUBSCRIPT: IENS 
   PARAMETER DESCRIPTION: IENS of record with incomplete key.  
COMPONENT/ENTRY POINT: 746
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   INTERNAL PARAMETERS NEEDED: YES       PACKAGE: Multi. Term Lookup (MTLU) 
  DESCRIPTION:   A lookup node is present in the FDA, but no Primary Key fields
 are provided.  
  TEXT:   
  No fields in Primary Key '|1|' have been provided in the FDA to look up '
 |IENS|' in the |2| file.  PARAMETER SUBSCRIPT: 1                  PARAMETER
 DESCRIPTION: Key name.  PARAMETER SUBSCRIPT: 2                  PARAMETER
 DESCRIPTION: File name.  PARAMETER SUBSCRIPT: IENS 
   PARAMETER DESCRIPTION: IENS of lookup node.  PARAMETER SUBSCRIPT: KEY        
        PARAMETER DESCRIPTION: Key number.  PARAMETER SUBSCRIPT: FILE           
    PARAMETER DESCRIPTION: File number.  
COMPONENT/ENTRY POINT: 1610
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   PACKAGE: RESOURCE USAGE 
  DESCRIPTION:   A question mark or, in the case of a variable pointer field, a
 <something>.? was passed to the Validator.  The Validator does not process
 help requests.  
  TEXT:   
  Help is being requested from the Validator utility.  PARAMETER SUBSCRIPT:
 FILE               PARAMETER DESCRIPTION: File number.  PARAMETER SUBSCRIPT:
 FIELD              PARAMETER DESCRIPTION: Field number.  ROUTINE NAME: DIE     
                  LINE TAG: FILE 
COMPONENT/ENTRY POINT: 8090
 COMPONENT DESCRIPTION:   TYPE: GENERAL MESSAGE 
   PACKAGE: Multi. Term Lookup  (MTLU) 
  DESCRIPTION:   Used in displaying an error message when the lookup value X 
  does not pass the Pre-lookup transform code (^DD(File#,.01,7.5) node) during 
  ^DIC or Finder lookups.  
  TEXT:   
  Pre-lookup transform (7.5 node) ROUTINE NAME: DIC ROUTINE NAME: DICF 
COMPONENT/ENTRY POINT: 8095
 COMPONENT DESCRIPTION:   TYPE: ERROR 
   PACKAGE: Multi. Term Lookup  (MTLU) 
  DESCRIPTION:   In calls to the Finder, IX^DIC or MIX^DIC, if the first index
 passed (or the default index) is a compound index, then only one index can be
 passed, so DIC(0) (or flags) cannot contain "M".  
  TEXT:   
  First lookup index is compound, so "M"ultiple index lookups not allowed.  
 ROUTINE NAME: DIC31                     LINE TAG: CHKVAL1 

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
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
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
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: 2890                            IA #: 2890
  DATE CREATED: AUG 16, 1999            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Dallas                 USAGE: Supported
  TYPE: Remote Procedure                NAME: DBIA2890
 GENERAL DESCRIPTION:   This RPC returns all psychological test administrations
 for a specified patient during a specified time period. No scoring is
 returned.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed

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
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

NUMBER: 2892                            IA #: 2892
  DATE CREATED: AUG 19, 1999            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Dallas                 USAGE: Supported
  TYPE: Remote Procedure                NAME: DBIA2892
 GENERAL DESCRIPTION:   This RPC 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: Pending                       DURATION: Till Otherwise Agreed

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
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: 2894                            IA #: 2894
  DATE CREATED: AUG 19, 1999            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Dallas                 USAGE: Supported
  TYPE: Remote Procedure                NAME: DBIA2894
 GENERAL DESCRIPTION:   This RPC 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: Pending                       DURATION: Till Otherwise Agreed

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
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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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: 2898                            IA #: 2898
  DATE CREATED: AUG 25, 1999
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Private                        TYPE: Routine
  ROUTINE: MPIFQ0                       NAME: Add ICN via LOCAL MPIFQ0
  ID: MPIFQ0
 GENERAL DESCRIPTION:   This private agreement allows the PIMS software to call
 the LOCAL^MPIFQ0 routine to create a local ICN and CMOR when adding a Treating
 Facility for a patient that does not have an ICN.  
  STATUS: Retired
COMPONENT/ENTRY POINT: LOCAL(DFN)
 COMPONENT DESCRIPTION:   This entry point creates a local ICN and CMOR for
 patient entries that do not already contain an ICN.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN - IEN of the PATIENT (#2) file entry.  
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 2899                            IA #: 2899
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19,
  DATE CREATED: AUG 26, 1999            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: DBIA2899                        ID: DIC(19,
 GENERAL DESCRIPTION:   The PCMM package would like to do the following in
 conjunction with a KIDs install: 
        o Look-up a PCMM Kernel menu option - Use ^DIC 
        o Rename option                     - Use FILE^DIE 
  STATUS: Pending                       DURATION: Next Version
  GOOD ONLY FOR VERSION: sd*5.3*177
KEYWORDS: PCMM
SUBSCRIBING PACKAGE: SCHEDULING

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
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
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

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
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: 1
  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
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: 2905                            IA #: 2905
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File
  NAME: TIU MEDICATION OBJECTS READ PHARMACY FILE
  ID: PSRX
GLOBAL REFERENCE: PSRX(
FIELD NUMBER: 6                         FIELD NAME: DRUG
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 39.2                      FIELD NAME: PHARMACY ORDERABLE ITEM
  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: 
  
 ^PSRX( - PRESCRIPTION FILE (#52) 
   Node 0, piece 6 - DRUG FIELD (#6) 
   Node "OR1", piece 1 - PHARMACY ORDERABLE ITEM FIELD (#39.2) 
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
KEYWORDS: TIU MEDICATION OBJECTS
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 2906                            IA #: 2906
  FILE NUMBER: 52.41                    GLOBAL ROOT: PS(52.41,
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File
  NAME: TIU MEDICATION OBJECTS READ PHARMACY FILE
  ID: PS(52.41,
GLOBAL REFERENCE: PS(52.41,
FIELD NUMBER: 8                         FIELD NAME: PHARMACY ORDERABLE ITEM
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: 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(52.41, - PENDING OUTPATIENT ORDERS FILE (#52.41) 
   Node 0, piece 8 - PHARMACY ORDERABLE ITEM FIELD (#8) 
   Node 0, piece 9 - DRUG FIELD (#11) 
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
KEYWORDS: TIU MEDICATION OBJECTS
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

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: Controlled Subscription
  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 accommodate 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
KEYWORDS: TIU MEDICATION OBJECTS
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 8/16/23 as part of clean-up exercise, effective
 with sustainment patch, OR*3*605 which is addressing INC20179355 - MOCHA
 duplicate order check displaying "UNRELEASED" on a "DISCONTINUED" order. The
 routine that needs to be modified is referencing ^PS(53.1, field #108. 

NUMBER: 2908                            IA #: 2908
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: SEP 15, 1999
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File
  NAME: TIU MEDICATION OBJECTS READ PHARMACY FILE
  ID: PS(55,
GLOBAL REFERENCE: PS(55,DFN,5,
FIELD NUMBER: 108                       FIELD NAME: ORDERABLE ITEM
  ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,DFN,5,DA,1,
FIELD NUMBER: .01                       FIELD NAME: DISPENSE DRUG
  ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,DFN,'IV'
FIELD NUMBER: 130                       FIELD NAME: ORDERABLE ITEM
  ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,DFN,'IV',DA,'AD',
FIELD NUMBER: .01                       FIELD NAME: ADDITIVE
  ACCESS: Direct Global Read & w/Fileman
 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 EMAIL GROUP 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 December 31, 2006.  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(55, - PHARMACY PATIENT FILE (#55) 
   ^PS(55,DFN,5, - UNIT DOSE SUB-FILE (#55.06) 
     Node .2, piece 1 - ORDERABLE ITEM FIELD (#108) 
  
     ^PS(55,DFN,5,DA,1 - DISPENSE DRUG SUB-FILE (#55.07) 
       Node 0, Piece 1 - DISPENSE DRUG FIELD (#.01) 
  
   ^PS(55,DFN,"IV", - IV SUB-FILE (#55.01) 
     Node .2, piece 1 - ORDERABLE ITEM FIELD (#130) 
  
     ^PS(55,DFN,"IV",DA,"AD", - ADDITIVE SUB-FILE (#55.02) 
       Node 0, piece 1 - ADDITIVE FIELD (#.01) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
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. 
  
 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: Retired                       EXPIRATION DATE: JUN 01, 2006
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: 1
  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
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
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: 2912                            IA #: 2912
  DATE CREATED: SEP 15, 1999            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: GMTS1
  NAME: DBIA2912                        ID: GMTS1
 GENERAL DESCRIPTION:   
  
 Network Health Exchange would like to be able to call GMTS1 at entry point
 EN^GMTS1 to extract data from Health Summary.  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE
  ISC: Oakland
 SUBSCRIBING DETAILS:   
  
  
 Routine GMTS1 has the function to extract data from Health Summary by passing
 appropriate parameters.  
  
  

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
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
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
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 2916                            IA #: 2916
  DATE CREATED: SEP 20, 1999            CUSTODIAL PACKAGE: 1
  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
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: 2917                            IA #: 2917
  DATE CREATED: SEP 23, 1999            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Private                        TYPE: Routine
  ROUTINE: XDRMERGB                     NAME: DBIA2917
  ID: XDRMERGB
 GENERAL DESCRIPTION:   
  During special processing related to the Patient Merge, the routine PRCAMRG
 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
 file 340.  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 file
 340, however, the internal entry numbers are determined from the "B"-cross-
 reference, and missing entries need to be handled separately.  
  
  
 Retired and placed under IA 2338.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
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: ACCOUNTS RECEIVABLE

NUMBER: 2918                            IA #: 2918
  DATE CREATED: SEP 23, 1999            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Routine
  ROUTINE: DGENA                        NAME: Patients Priority
  ID: DGENA
 GENERAL DESCRIPTION:   To look up a patients priority for report currently
 using the call: $$PRIORITY^DGENA(DFN) 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$PRIORITY
SUBSCRIBING PACKAGE: INTEGRATED BILLING

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
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.  

NUMBER: 2920                            IA #: 2920
  DATE CREATED: SEP 23, 1999
  CUSTODIAL PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  USAGE: Supported                      TYPE: Routine
  ROUTINE: IEN,"IB"                     NAME: Pharmacy copay information read
  ID: IEN,"IB"
 GENERAL DESCRIPTION:   Direct read of global for pharmacy copay information: 
 ^PSRX(IEN,"IB") 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PSRX
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 2921                            IA #: 2921
  DATE CREATED: SEP 24, 1999
  CUSTODIAL PACKAGE: PHARMACY BENEFITS MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSUTL
  NAME: DBIA 2921                       ID: PSUTL
 GENERAL DESCRIPTION:   This IA provides a common point for data retrieval
 APIs. It presents a friendly front end to DIQ and DIQ1 with special features
 for handling multiples.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: DATA RETRIVAL
KEYWORDS: DIQ
KEYWORDS: DIQ1
KEYWORDS: PSUTL
COMPONENT/ENTRY POINT: $$VAL()
 COMPONENT DESCRIPTION:   
  
 This API returns the external value of the field specified.  
  
 Format:  S X=$$VAL^PSUTL(FILE,IENS,FIELD) 
                                                                        ..
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File or subfile number.  
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Standard IENS indicating internal entry
 numbers.  
  
 Parameter passed: 
  
 1. 'By value' in a string of IENS separated by commas in [NOTE] "D0,D1,D2,.."
 order. Iens can be either numbers or variables.  
  
 2. 'By reference' in a '.array' where the array is a DA array.  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   The field number of the field to be retrieved.  
COMPONENT/ENTRY POINT: $$VALI()
 COMPONENT DESCRIPTION:   
  
 This API returns the internal value of the field specified.  
  
 Format: S X=$$VALI^PSUTL(FILE,IENS,FIELD) 
                                                                        ..
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File or subfile number.  
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Standard IENS indicating internal entry
 numbers.  
  
 Parameter passed: 
  
 1. By 'value' in a string of IENS separated by commas in [NOTE] "D0,D1,D2,.."
 order. Iens can be either numbers or variables.  
  
 2. By 'reference' in a '.array' where the array is a DA array.  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   The field number of the field to be retrieved.  
COMPONENT/ENTRY POINT: GETM()
 COMPONENT DESCRIPTION:   
  
 This returns the multiples of a subfile with their respective submultiple IEN,
 specified fields, and field values in the specified array.  
  
       TARGET_ROOT(IEN,FIELD)=DATA 
  
 Format: D GETM^PSUTL(FILE,IENS,"PFIELD*^FIELDS",TARGET_ROOT,FLAGS) 
  
 Returning format:   TARGET_ROOT(IEN,FIELD)=DATA 
  
 Example: 
  
 >D GETM^PSUTL(200,"DUZ","51*^.01;1;2;3","KEYS") 
  
 >ZW KEYS KEYS(1,.01)=XUPROG KEYS(1,1)=MONTALI,MICHAEL KEYS(1,2)=SEP 30, 1998 
 KEYS(1,3)= KEYS(3,.01)=XUPROGMODE KEYS(3,1)=MONTALI,MICHAEL KEYS(3,2)=SEP 30,
 1998 KEYS(3,3)= 
                                                                        ..
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File or subfile number. This is the DD
 number of the parent of the multiple file desired, not the DD number of the
 multiple.  
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Standard IENS indicating internal entry
 numbers.  
  
 These are the IENS of the parent of the multiple desired.  
  
 Parameter passed: 1. By value in a string of IENS separated by commas in
 >>>NOTE "D0,D1,D2,.." order<<<. Iens can be either numbers or variables.  
  
 2. By reference in a '.array' where the array is a DA array 
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".  N Does not return Null values.  R Resolves field
 numbers to field names in target array subscripts.  Z Word processing fields
 includes Zero nodes.  
VARIABLES: PFIELD                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the parent level field number of the desired
 multiple.  
VARIABLES: TARGET_ROOT                  TYPE: Both
 VARIABLES DESCRIPTION:   Input:         (Required) The name of a closed root
 reference.  
  
 Output:        The output array is in the format: 
                TARGET_ROOT(IEN,FIELD)=DATA.  
  
 If FLAGS has I or E specified then appropriate subscripts will exist.  See
 FLAGS for more options.  WP fields have data descendant from the field nodes
 in the output array.  
VARIABLES: FIELDS                       TYPE: Input
 VARIABLES DESCRIPTION:   A single field number or list of field numbers,
 separated by semicolons.  
COMPONENT/ENTRY POINT: MOVEI()
 COMPONENT DESCRIPTION:   
  
 This API processes arrays that have been created with the "I" flag and moves
 the values: 
  
 to:    TARGET_ROOT(FIELD)=DATA from:  TARGET_ROOT(FIELD,"I")=DATA 
  
 Format:  D MOVEI^PSUTL(TARGET_ARRAY) 
  
 Example: 
  
 >ZW KEY KEY(.01,"I")=3 KEY(1,"I")=12 KEY(2,"I")=2980930 KEY(3,"I")= 
  
 >D MOVEI^PSUTL("KEY") 
  
 >ZW KEY KEY(.01)=3 KEY(1)=12 KEY(2)=2980930 KEY(3)= 
                                                                        ..
VARIABLES: TARGET_ROOT                  TYPE: Both
 VARIABLES DESCRIPTION:   The closed root reference of TARGET_ROOT.  
  
 Must be enclosed in quotes.  
COMPONENT/ENTRY POINT: MOVEMI()
 COMPONENT DESCRIPTION:   
  
 This API processes multiple arrays that have been created with the "I" flag
 and moves the values: 
  
 to:    TARGET_ROOT(IEN,FIELD)=DATA from:  TARGET_ROOT(IEN,FIELD,"I")=DATA 
  
 Format:  D MOVEMI^PSUTL(TARGET_ROOT) 
  
 Example: 
  
 >ZW KEYS KEYS(1,.01,"I")=1 KEYS(1,1,"I")=12 KEYS(1,2,"I")=2980930 
 KEYS(1,3,"I")= KEYS(3,.01,"I")=3 KEYS(3,1,"I")=12 KEYS(3,2,"I")=2980930 
 KEYS(3,3,"I")= 
  
 >D MOVEMI^PSUTL("KEYS") 
  
 >ZW KEYS KEYS(1,.01)=1 KEYS(1,1)=12 KEYS(1,2)=2980930 KEYS(1,3)= KEYS(3,.01)=3 
 KEYS(3,1)=12 KEYS(3,2)=2980930 KEYS(3,3)= 
                                                                        ..
VARIABLES: TARGET_ROOT                  TYPE: Both
 VARIABLES DESCRIPTION:   The closed root reference of TARGET_ROOT.  
  
 Must be enclosed in quotes.  
COMPONENT/ENTRY POINT: GETS()
 COMPONENT DESCRIPTION:   
  
 This API returns the specified fields af a selected in a designated array: 
  
 TARGET_ROOT(FIELD)=DATA 
  
 Format: D GETS^PSUTL(FILE,IENS,TARGET_ARRAY,FLAGS) 
  
 Example: 
  
 >S KEYDA=3 
  
 >D GETS^PSUTL(200.051,"DUZ,KEYDA",".01:3","KEY") 
  
 >ZW KEY KEY(.01)=XUPROGMODE KEY(1)=MONTALI,MICHAEL KEY(2)=SEP 30, 1998 KEY(3)= 
                                                                        ..
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Standard IENS indicating internal entry
 numbers.  
  
 Parameter passed: 
  
 1. By 'value' in a string of IENS separated by commas in [NOTE] "D0,D1,D2,.."
 order. Iens can be either numbers or variables.  
  
 2. By 'reference' in a '.array' where the array is a DA array.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File or subfile number.  
VARIABLES: TARGET_ROOT                  TYPE: Both
 VARIABLES DESCRIPTION:   Input:         (Required) The name of a closed root
 reference.  
  
 Output:        The output array is in the format: 
                TARGET_ROOT(IEN,FIELD)=DATA.  
  
 If FLAGS has I or E specified then appropriate subscripts will exist.  See
 FLAGS for more options.  WP fields have data descendant from the field nodes
 in the output array.  
VARIABLES: FIELDS                       TYPE: Input
 VARIABLES DESCRIPTION:   A single field number, separated by semicolons.  A
 list of field numbers, in the form M:N, where M and N are the end points of
 the inclusive range.  
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".  N Does not return Null values.  R Resolves field
 numbers to field names in target array subscripts.  Z Word processing fields
 includes Zero nodes.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 2922                            IA #: 2922
  DATE CREATED: SEP 28, 1999
  CUSTODIAL PACKAGE: PHARMACY BENEFITS MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSUDBQUE
  NAME: DBIA 2292                       ID: PSUDBQUE
 GENERAL DESCRIPTION:   This API provides the ability to easily double queue
 tasks into a compute cycle (no device attatched) and a print cycle (device
 attatched). The compute and print routines are identified with appropriate
 variables and the tasking is handled by the API.  
  
 Optional variables are available to provide controlling various aspects the
 jobs and process.  
  
 Documentation is also included in the end of the routine.  
  
 General processing protocol information 
  
          %ZIS with "PQM" is called by PSUDBQUE if '$D(PSUIOP).  
         
          The user will be asked to queue if queuing has not been 
          selected.  
         
          IO variables for printing as necessary are automatically 
          stored.  
         
          PSUxx input variables are killed after loading into a PSU 
          array.  
         
          PSUDBQUE can be nested.  
         
          The compute and print phases can call PSUDBQUE individually 
          (PSUIOP is required).  
         
          The appropriate %ZTSK node is killed.  
  
          The use of ^XTMP in the compute cycle for storage of 
          information for the print cycle is typical. Subscript values 
          stored in one of the namespace save variables are automatically 
          reloaded for the next cycle.  
                                                                ..
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: QUEUE
KEYWORDS: PSUDBQUE
KEYWORDS: DOUBLE
COMPONENT/ENTRY POINT: EN
VARIABLES: PSURC                        TYPE: Input
 VARIABLES DESCRIPTION:   Required* 
  
 The string of "label^routine" for the computing cycle.  Format: S
 PSURC="COMPUTE^PSOCMOPR" 
  
 * (Optional if PSURP is defined and only print queuing is desired) 
VARIABLES: PSURP                        TYPE: Input
 VARIABLES DESCRIPTION:   Required* 
  
 The string of "label^routine" for the printing cycle.  Format: S
 PSURP="PRINT^PSOCMOPR" 
  
 * (Optional if PSURC is defined and only compute queuing is desired) 
VARIABLES: PSURX                        TYPE: Input
 VARIABLES DESCRIPTION:   Optional 
  
 The string of "label^routine" for the exit cycle.  Format: S
 PSURX="EXIT^PSOCMOPR" 
  
 If XTMP is used it should be killed in the last of the print cycle and not
 here. ZTSK is handled by the API.  
  
 An EXIT point is recomended particularly if the user is allowed to run the
 software in the foreground.  
VARIABLES: PSUNS                        TYPE: Input
 VARIABLES DESCRIPTION:   PSUNS=namespace(s) of variables to be auto-loaded
 into ZTSAVE("namespace*")="" 
  
 Format: 
  
 PSUNS  ="DG*;AUPN;PS;..." ; (will add '*'if missing).  Or    
 ="DG,AUPN,PS,..." ; (may be semi-colon or comma delimited) Or  
 PSUNS("xxx")="" 
        ZTSAVE variable arrays where xxx is as described for 
        ZTSAVE("xxx")="".  
VARIABLES: PSUFQ                        TYPE: Input
 VARIABLES DESCRIPTION:   Optional 
  
 This controlls queuing.  
  
 If $G(PSUFQ)=1 queuing is forced.  
VARIABLES: PSUDTH                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional 
  
 Tasking date.time in FM format. User is not asked for date & time if this is
 set.  
VARIABLES: PSUIOP                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional 
  
 A preselected device constructed with: 
  
 ION_";"_IOST_";"_IOM_";"_IOSL.  
VARIABLES: PSUPAR                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional 
  
 This variable holds the HOST File parameters to be used with PSUIOP if the
 host file is preselected.  
  
 Note: S:$D(%ZIS("IOPAR") PSUPAR=%ZIS("IOPAR") is suggested if Host File access
 is permitted and preselected device is being used.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

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
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. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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

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
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

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
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: 1                  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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM 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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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,
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
FIELD NUMBER: 1207                      FIELD NAME: SECONDARY VISIT
  LOCATION: 12;7                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1210                      FIELD NAME: ORDER NUMBER
  LOCATION: 12;10                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1405                      FIELD NAME: REQUESTING PACKAGE REFERENCE
  LOCATION: 14;5                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1205                      FIELD NAME: HOSPITAL LOCATION
  LOCATION: 12;5                        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',
GLOBAL REFERENCE: TIU(8925,'DAD',
GLOBAL REFERENCE: TIU(8925,'APTCL',
 GENERAL DESCRIPTION:   This DBIA documents references from OR* routines to the
 TIU DOCUMENT file (#8925).  
  
 Revisions: 
  - 3/6/23 Added 1207 SECONDARY VISIT field 
  - 9/11/23 Effective with Patch OR*3.0*535, ORDER NUMBER (#1210) field and 
   the REQUESTING PACKAGE REFERENCE (#1405) fields were added, to allow 
   CPRS to display the ordering provider related to certain Text 
   Integration Utilities (TIU) notifications to be determined.  
  - 3/20/24 Added 1205 HOSPITAL LOCATION 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   
  Added 3/6/23, effective with OR*3*588 for CPRS 32c; added additional field
 1207, SECONDARY VISIT. 
  Added 3/20/24, effective with OR*3.0*439; added additional field 1205, 
 HOSPITAL LOCATION to document historical use of 1205.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   ADDED 11/10/2010 
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 10/11/22, effective with SD*5.3*827 VSE team is
 working on an enhancement where a new RPC, SDES GET TIU DOC BY CONTEXT, is
 created to retrieve TIU data tied to the location/clinic ID.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 1/20/2023, effective with DSSV*1.1 DSS Class 3
 product Document Only Added APTCL and DAD cross-reference look-up to ICR 
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI
 SUBSCRIBING DETAILS:   Added 9/5/24 effective with DSIR*8.2*16, in order to
 read patient name field  for a given patient in the TIU DOCUMENT (#8925)  
 file  fields .01 and .02  DOCUMENT TYPE and PATIENT using FILEMAN. S
 DSIR892=$$GET1^DIQ(8925,DSIR89,.01,"I") I
 $$GET1^DIQ(8925,DSIRCHK_",",.02,"I")'=DSIRCKDFN S DSIRERR="-1^Patient 
 mis-match" 
  DATE ACTIVATED: SEP 12, 2023

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
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

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
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
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
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: 2943                            IA #: 2943
  DATE CREATED: OCT 29, 1999            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DG10                         NAME: DBIA2943
  ID: DG10
 GENERAL DESCRIPTION:   To support CIRN Exception Handling, CIRN PD needs to
 include an option to Edit Patient Data.  
  STATUS: Withdrawn
COMPONENT/ENTRY POINT: A1
 COMPONENT DESCRIPTION:   Edit patient data.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN to 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
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 10/22/24 effective with patch DSIY*1.5*6 to
 support the reporting of TIU documents.  
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/22/24 effective with patch DSSO*2.0*8 to
 support the reporting of TIU documents.  
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI
 SUBSCRIBING DETAILS:   Added 1/20/26 effective with patch DSIR*8.2*18 to 
 support the reporting of TIU documents.  

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.  
  
 Amended 7/29/22 to add the COMPONENT: $$INFRATE(X), effective with PSJ*5*375,
 OR*3*439.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
COMPONENT/ENTRY POINT: $$INFRATE(X)
 COMPONENT DESCRIPTION:   This entry point validates the infusion rate field
 when ordering an IV order in CPRS.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   The Infusion rate that was entered during order
 entry.  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   The infusion rate (X) is returned if passes
 validation, otherwise, null ("") is returned.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   OE/RR calls ORINF 
  DATE ACTIVATED: OCT 29, 1999

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
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
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   Access to EN^PSSGSGUI for VIAB DFLTSPLY RPC and
 OrderMgmtSvc - isDrugScheduleValid service 

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
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
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,<freq>,<ien>) 
  
 This global array contains all of the entries found during the search.  The
 <freq> is a negative number based on the frequency of use for a given term. 
 <ien> is the internal entry number in the Lexicon Expression file (757.01).  
  
  
 ^TMP("LEXHIT",$J,<seq>) 
  
 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

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
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

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
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

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
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
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
 GENERAL DESCRIPTION:   This DBIA documents calls to routine LR7OU1 
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
  DATE ACTIVATED: MAY 24, 2012

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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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 the 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.  Output 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.  Output 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)
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Added 8/10/23, effective with PXRM*2.0*81 Clinical
 Reminders calls the INTERIMS^LR7OGM API from outine PXRMLTAX in support of the
 Cervical Cancer Screening project.  
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
 SUBSCRIBING DETAILS:   Added 8/10/23, effective with patch WV*1.0*31 Women's
 Health calls the INTERIMS^LR7OGM API from routine WVRPCGF1 in support of the
 Cervical Cancer Screening project.  
SUBSCRIBING PACKAGE: VETEXT
 SUBSCRIBING DETAILS:   Added 3/14/25 effective with VTEX*1*0 to support access
 to VA Point of Service Kiosks for sending clinical reminders to Veterans about
 upcoming medical appointments.  

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
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
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
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
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.  
  
 GMPDT(LCNT,0)=Audit information 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

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
GLOBAL REFERENCE: %ZIS(1,DA,'SUBTYPE')
FIELD NUMBER: 3                         FIELD NAME: SUBTYPE
  LOCATION: SUBTYPE;1                   ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: %ZIS(1,'B')
 GENERAL DESCRIPTION:   This DBIA documents direct access to fields in the
 DEVICE file (#3.5).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
  
 Discovered 1/23/26, OERR's original subscription should have requested adding
 the SUBTYPE field and the "B" cross-reference. The usage of those additional 
 fields dates back to the original subscription around 1999 with the release of
 OR*3*10.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 4/23/25 effective with SD*5.3*906 patch. ISS uses
 device information to process requests.  

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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 4/23/25 effective with SD*5.3*906 patch. ISS uses
 device information to process requests.  

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.1     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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   
  
 ADDED 1/07/2022, effective with DSSV*1.0*1 DSS Class 3 product Document Only -
 Not approved by Custodial SME 

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
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
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 

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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be referencing the fields in the
 Contract/Sharing Agreement (#34) file in VIAB RADSRC RPC.  

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(
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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

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
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',
GLOBAL REFERENCE: GMPL(125,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DATE LAST MODIFIED
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Effective with OR*3.0*429, access to these fields are
 utilized in determining which clinic default selection lists to migrate to the
 new default selection list parameter if a clinic has been assigned to more 
 than one list.  
GLOBAL REFERENCE: GMLP(125,'AD'
GLOBAL REFERENCE: GMPL(125,D0,1,
FIELD NUMBER: .01                       FIELD NAME: CATEGORY NAME
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: SEQUENCE
  LOCATION: 1;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: SUBHEADER
  LOCATION: 1;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: SHOW PROBLEMS
  LOCATION: 1;4                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This DBIA documents access made to the PROBLEM
 SELECTION LIST file (#125).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Added 9/24/25 Patch OR*3.0*508 is retroactively
 documenting this ICR used. The following fields were added CATEGORY NAME, 
 SEQUENCE, SUBHEADER, and SHOW PROBLEMS and the "AD" cross references.  
  DATE ACTIVATED: FEB 14, 2017

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
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
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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
  
 HEALTH MANAGEMENT PLATFORM (HMP) will use the GMPL(125.8,"AD", cross reference
 to get the Problem List Audit in reverse chronological order with seconds.This
 data is used in displaying patient data to the user in the HMP UI.  
     
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 8/13/21 effective with patch VPR*1*27: VPR sends
 patient data to the SDA repository in Health Share when entered, modified, or
 deleted. HS only updates the data fields we send in, so if a value is deleted
 we must explicitly note that in the payload or it will remain untouched. VPR 
 would like access to the PL Audit file to see if any values were removed when
 the problem was last changed, to be able to set this delete flag for HS. 

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
GLOBAL REFERENCE: GMR(123.1,'B'
 GENERAL DESCRIPTION:   This DBIA documents references to the REQUEST ACTION
 TYPES file (#123.1).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   Added 2/10/26, effective with patch MAG*3.0*362 needs
 access to the REQUEST ACTION TYPES field and request to add 'B'
 cross-reference.  

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
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
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(1.17)= 
  GMPFLD(1.18)= 
  GMPFLD(1.19)= 
  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
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 9/27/18 for VPR*1*3 to use the GETFLDS^GMPLEDT3
 api for retrieving internal and external forms of the data.  
  DATE ACTIVATED: AUG 12, 2015

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
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
  
 HEALTH MANAGEMENT PLATFORM (HMP) will use the following API: 
               NEW^GMPLSAVE
     

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
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
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

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 document calls made to routine GMRCGUIB.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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 comments 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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) would like to subscribe to ICR 2980
 to call DOCLIST~GMRCGUIB API to retrieve a list of TIU documents that are
 linked to a specified consult.  
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   APAT will be using $$SFILE - propagate Suspense Note
 updates into the Consult when creating a Request for Quote, Orthotic Lab Work
 Order, Purchase Card Order, and GIP Stock Issue and $$CMT - adds a comment to
 the Consult when creating a Request for Quote, Orthotic Lab Work Order, 
 Purchase Card Order, and Stock Issue.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Added 2/18/22, effective with TIU*1.0*349. The
 Community Care Referrals & Authorization (CCRA) team has been asked to add a
 comment to the Request Processing Activity multiple (#123.02) in the Request
 Services file (#123) when filing a note or note addendum with the consult. The
 comment is logging a Consult Factor that is based on the type of note or
 addendum being filed. CCRA is preparing patch TIU*1.0*349 with this
 modification and will call the CMT line tag in routine GMRCGUIB. This patch
 restricts logging the consult factors to only Community Care consults. 
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Added 11/7/22 effective with RA*5*196 addressing a
 defect and updating the routine to use CMT^GMRCGUIB.  
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   PROSTHETICS VISION 4 SIGHT II Added 04/22/25, effective
 with PROSTHETICS VISION 4 SIGHT II patch RMPV*1*1, the Prosthetics package
 requires access to the routine GMRCGUIB, component $$SFILE 
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   Added 09/30/26, effective with DENT*1.2*96, Dental
 Record Manager Plus (DRM Plus) will be utilizing CMT^GMRCGUIB to file comments
 to consults for the purpose of avoiding the need to copy and paste said
 comments needed for the purposes of Community Care integration.  

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
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

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
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
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
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
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
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: 2987                            IA #: 2987
  DATE CREATED: NOV 18, 1999            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSJPATMR
  NAME: DBIA2987                        ID: PSJPATMR
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   The entry point EN^PSJPATMR is provided by Inpatient
 Medications package to address unique issues involved in the patient merge
 process.  Some sites were unable to merge duplicate patients due to data
 exceptions.  This API provides the patient merge software with an access point
 to call before the package begins it data validation of the FROM and TO
 records of the duplicate patients to clear up some of these data exceptions in
 the PHARMACY PATIENT file (#55) specifically the Unit Dose and IV multiples.  
  
 INPUT  DEFINITION 
    
   DFN1:  From Patient Internal File Number.  
   DFN2:  To Patient Internal File Number.  
    
 OUTPUT DEFINITION 
    
   If 1 is returned, the FROM patient orders will be moved to a higher IEN 
   (Internal Entry Number) range if duplicate IENs were found between the 
   FROM and TO patient. It will return a 0 to NOT continue with the pair 
   if the FROM patient has active inpatient orders or any orders currently 
   on a Pick List that has not been filed away.  
SUBSCRIBING PACKAGE: TOOLKIT            ISC: Oakland

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
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: 2989                            IA #: 2989
  FILE NUMBER: 90                       GLOBAL ROOT: MR(
  DATE CREATED: JUN 10, 2003            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA2989
  ID: MR(
 GENERAL DESCRIPTION:   This is a one time DBIA request to modify the field
 definitions of two fields from the MENTAL HEALTH package's MEDICAL RECORDS
 file (#90.)  This is in response to NOIS calls PUG-1099-51192 and
 HOU-0399-72142.  Patch YS*5.01*58 was created to address these NOIS calls. 
 Here is the patch description from YS*5.01*58: 
  
 This patch corrects an error that occurs in menu option "Identify Potential 
 Merge Problems [XDR VALID CHECK]" of the MEDICINE package.  Although it 
 originally appeared to be a FILEMAN error or a MEDICINE package error, it was
 later determined to be a data dictionary problem with the MEDICAL RECORDS file
 (#90) of the MENTAL HEALTH package.  
  
 The error appears as follows: 
  
 $ZE= DDENTRY+29^DIQGQ:3, %DSM-E-NAME, bad variable name 
  
  ..D  F  S DIQGMDA=$O(@DIQGMGR@(DIQGMDA)) Q:DIQGMDA'>0  D 
 EN($S('DIQGDD:DIQGMDD, 
 1:$$OREF(DIQGMGR)),.DIQGMDA,"**",DIQGPARM,.DIQGTA,"",$S('DIQGDD:"",1:1)) 
  
 Last Global Ref: ^DIC(.12,0,"GL") 
  
 The problem is caused by the DD definition of the COMMENTS field (Sub file 
 #90.02, Sub field #30) of the PHY field (Sub file #90.01, Sub field #100) of 
 the MEDICAL RECORDS file (#90.)  The GETS^DIQ call in routine XDRDVAL was 
 extracting all fields and sub fields for the given record (due to the "**" in
 the FIELD parameter.)  See below: 
  
         D GETS^DIQ(FILE,IEN,"**","EIN",DATAROOT,MESGROOT) 
  
 The COMMENTS field (#30) is defined as a free text multiple but stored as a
 word-processing field.  In a multiple field, the header (or 0) node contains
 the DD entry number of the sub file in the second piece.  Because the DD
 definition of the COMMENTS field (#30) is defined as a multiple field, FILEMAN
 takes the value of the second piece (delimited by "^") of the header node and
 pluses it (+) to get the DD entry number of the sub file.  See below: 
  
        ^MR(7180189,"PE",7069286,19,0) = ^^1^1^2930713^ 
  
 The node above resembles a word processing field but in the DD it is defined
 as a multiple. A multiple should have a sub file number in the second piece. 
 Since nothing is in the second piece, the resulting number returned to FILEMAN
 was a 0 (zero) which confused FILEMAN, causing it to look at the wrong file. 
 The same DD problem exists in the INITIAL IMPRESSION field (Sub file #90.03,
 Sub field #31.) This field is defined as a free text multiple but stored as a
 word-processing field.  
  
 In this situation, no data problem exists.  The data is correct and requires
 no modifications.  The solution is to change the definitions of these fields
 from multiples to word-processing.  Because MEDICAL RECORDS file is an old
 file, it is not possible to make the data dictionary changes using FILEMAN. 
 Therefore, it is necessary to use hard SETS and KILLS to update the data
 dictionary.  
  
 Here is the data as it exists prior to the installation of this patch.  Please
 note that, for better readability, not all nodes have been displayed: 
  
 COMMENTS field (#30) 
  
  ^DD(90.01,30,0) = COMMENTS^90.02A^^19;0 
  ^DD(90.01,30,21,0) = ^^1^1^2930202^ 
  ^DD(90.01,30,21,1,0) = Comments relating to the physical exam.  
   
  ^DD(90.02,0) = COMMENTS SUB-FIELD^NL^.01^1 
  ^DD(90.02,.01,0) = COMMENTS^MF^^0;1^K:$L(X)>70!($L(X)<2) X 
  ^DD(90.02,.01,3) = ANSWER MUST BE 2-70 CHARACTERS IN LENGTH 
  ^DD(90.02,.01,21,0) = ^^2^2^2930202^ 
  ^DD(90.02,.01,21,1,0) = Comments enter by the examiner relating to the 
  physical exam of the 
  ^DD(90.02,.01,21,2,0) = patient.  
  
 INITIAL IMPRESSION field (#31) 
  
  ^DD(90.01,31,0) = INITIAL IMPRESSION^90.03A^^20;0 
  ^DD(90.01,31,21,0) = ^^1^1^2930202^ 
  ^DD(90.01,31,21,1,0) = Examiner's initial impression.  
  
  ^DD(90.03,0) = INITIAL IMPRESSION SUB-FIELD^NL^.01^1 
  ^DD(90.03,0,"NM","INITIAL IMPRESSION") = 
  ^DD(90.03,0,"UP") = 90.01 
  ^DD(90.03,.01,0) = INITIAL IMPRESSION^MF^^0;1^K:$L(X)>70!($L(X)<2) X 
  ^DD(90.03,.01,3) = ANSWER MUST BE 2-70 CHARACTERS IN LENGTH 
  
 Routine YS58POST will run during installation of YS*5.01*58 to perform the 
 following: 
  
 1)  Remove the "A" from the sub field number.  The "A" indicates to 
 automatically add entries without asking: "ARE YOU ADDING A NEW ENTRY?" This
 is no longer applicable for a word processing file.  
  
         S $P(^DD(90.01,30,0),U,2)=90.02     (COMMENTS) 
         S $P(^DD(90.01,31,0),U,2)=90.03     (INITITAL IMPRESSION) 
  
 2)  Reset the field definition which is stored in the data dictionary's zero
 node, field .01, of the sub file.  The "MF" originally in the second piece
 indicates this field is a multiple and free text.  We replace it with "W"
 which indicates a word processing field.  The input transform Mumps code is
 replaced with "Q" in the fifth piece.  
  
         S ^DD(90.02,.01,0)="COMMENTS^W^^0;1^Q" 
         S ^DD(90.03,.01,0)="INITIAL IMPRESSION^W^^0;1^Q" 
  
 3)  Kill the help text in the 3 node.  It is no longer needed.  
  
         K ^DD(90.02,.01,3)  (COMMENTS) 
         K ^DD(90.03,.01,3)  (INITIAL IMPRESSIONS) 
  
 4)  Correct a spelling error for the COMMENTS field (#30.) 
  
         S ^DD(90.02,.01,21,1,0)="Comments entered by the examiner relating 
         to the physical exam" 
  
 This is how the data dictionary entries appear after the changes are made.  
  
 COMMENTS field (#30) 
  
  ^DD(90.01,30,0) = COMMENTS^90.02^^19;0 
  ^DD(90.01,30,21,0) = ^^1^1^2930202^ 
  ^DD(90.01,30,21,1,0) = Comments relating to the physical exam.  
  
  ^DD(90.02,0) = COMMENTS SUB-FIELD^NL^.01^1 
  ^DD(90.02,.01,0) = COMMENTS^W^^0;1^Q 
  ^DD(90.02,.01,21,0) = ^^2^2^2930202^ 
  ^DD(90.02,.01,21,1,0) = Comments entered by the examiner relating to the 
  physical exam of the 
  
 INITIAL IMPRESSION field (#31) 
  
  ^DD(90.01,31,0) = INITIAL IMPRESSION^90.03^^20;0 
  ^DD(90.01,31,21,0) = ^^1^1^2930202^ 
  ^DD(90.01,31,21,1,0) = Examiner's initial impression.  
   
  ^DD(90.03,0) = INITIAL IMPRESSION SUB-FIELD^NL^.01^1 
  ^DD(90.03,.01,0) = INITIAL IMPRESSION^W^^0;1^Q 
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas

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
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: 1                  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
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

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
 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
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
  DATE ACTIVATED: FEB 21, 2014

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
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
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
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 4/22/25, effective with PSO*7*770 patch for Meds
 By Mail team to mark note as electronically signed for document.  

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
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
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
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
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
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
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
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
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
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Added 11/6/19, effective with RA*5*161.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 04/14/22, effective with DSSV 1.1 DSS Class 3
 product Document Only - Not approved by Custodial SME DSSV is using fields 3
 SHORT NAME from ^ORD(100.98 and.01 MEMBER from ^ORD(100.98,D0,1)global
 references.  This access will filter the display of an order based on display
 group.  

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
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,<error number>,"TEXT",<line number>)=<error text> 
  
 Following is information on some common input parameters: 
  
 XMGROUP  - Mail group IEN or name (exact, case-sensitive) 
  STATUS: Active
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
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Washington/Silver Spring

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
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
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.  

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
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
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
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
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
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
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   12/11/15-Added Inpatient Meds for Pharmacy Interface
 Automation (PIA) project 

NUMBER: 3016                            IA #: 3016
  DATE CREATED: JAN 12, 2000            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VAFHLEVN                     NAME: EVN segment generation (CIRN PD)
  ID: VAFHLEVN
 GENERAL DESCRIPTION:   The purpose of this IA is to create a EVN 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
COMPONENT/ENTRY POINT: $$EVN
 COMPONENT DESCRIPTION:   This entry point is passed two input parameters: 
  
 1) the HL7 Event Type 2) the HL7 Event Reason Code 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   This variable represents the HL7 Event Type.  
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   This variable represents the HL7 Event Reason Code.  
COMPONENT/ENTRY POINT: $$EN(VAFEVTYP,VAFEVDT,VAFSTR,VAFHLQ,VAFHLFS)
 COMPONENT DESCRIPTION:   This entry point is used by Ambulatory Care Database
 Project 
     
 This entry point is passed 5 input parameters: 
VARIABLES: VAFEVTYP                     TYPE: Input
 VARIABLES DESCRIPTION:   Event Type Code 
VARIABLES: VAFEVDT                      TYPE: Input
 VARIABLES DESCRIPTION:   Event Date/Time.  Date/Time Event Occurred (same as
 Encounter Date/Time) 
VARIABLES: VAFSTR                       TYPE: Input
 VARIABLES DESCRIPTION:   String of fields requested separated by commas.  
VARIABLES: VAFHLQ                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional HL7 null variable. If not there, use default
 HL7 variable.  
VARIABLES: VAFHLFS                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional HL7 field separator. If not there, use
 default HL7 variable.  
VARIABLES: EVN string                   TYPE: Output
 VARIABLES DESCRIPTION:   String containing desired components of the EVN
 segment.  
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   12/11/15-Added Inpatient Meds for Pharmacy Interface
 Automation (PIA) project 
  DATE ACTIVATED: DEC 15, 2015

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
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
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

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

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

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

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

NUMBER: 3024                            IA #: 3024
  FILE NUMBER: 2                        GLOBAL ROOT: DD(2
  DATE CREATED: JUN 10, 2003            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: ID Nodes in Patient (#2) file   ID: DD(2
 GENERAL DESCRIPTION:   DG*5.3*249, DGSEC Modifications and Privacy Act
 Compliance for Employees, modifies the identifiers on the DOB (#.03) and
 Social Security Number (#.09) fields in the Patient (#2) file to: 
  
 ^DD(2,0,"ID",.03) = D EN^DDIOL($TR($$DOB^DPTLK1(Y,1),"/","-"),,"?$X+2") 
 ^DD(2,0,"ID",.09) = D EN^DDIOL($$SSN^DPTLK1(Y),,"?$X+2") 
  
 The DOB and SSN function calls in DPTLK1 are new with this patch.  If the 
 patient's primary eligibility code is Employee, *SENSITIVE* will be displayed
 for the DOB and SSN fields until the user verifies they want to access the
 restricted record.  
  
 The post-init routine, DG53249P, will set the "ID" nodes: 
  
 DG53249P        ;ALB/JAP - Patch 249 postinstall ; 1/11/00 12:56pm 
         ;;5.3;Registration;**249**;Aug 13, 1993 
         ;
 EN      ;entry point from install 
         ;update identifier code in patient file 
         S ^DD(2,0,"ID",.03)="D 
 EN^DDIOL($TR($$DOB^DPTLK1(Y,1),""/"",""-""),,""?$X+2"")" 
         S ^DD(2,0,"ID",.09)="D EN^DDIOL($$SSN^DPTLK1(Y),,""?$X+2"")" 
         Q 
  STATUS: Retired
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 3025                            IA #: 3025
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT
  DATE CREATED: JAN 24, 2000            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA3025                        ID: ICPT
GLOBAL REFERENCE: ICPT
 GENERAL DESCRIPTION:   Please see supported ICR #5408, CPT/CPCS Procedure File
 81.Integrated Billing and AICS require Fileman lookup to file 81 (^ICPT).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 09, 2015
KEYWORDS: CPT
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Albany

NUMBER: 3026                            IA #: 3026
  FILE NUMBER: 81.3                     GLOBAL ROOT: DIC(81.3,
  DATE CREATED: JAN 24, 2000            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA3026                        ID: DIC(81.3,
 GENERAL DESCRIPTION:   Now covered by supported ICR #2816,CPT MODIFIERS FILE.
 Both Integrated Billing and AICS require Fileman lookup to file #81.3 
 (^DIC(81.3).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 09, 2015
KEYWORDS: CPT MODIFIER
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
  ISC: Albany
SUBSCRIBING PACKAGE: IMAGING

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
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.  

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
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
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: 3030                            IA #: 3030
  DATE CREATED: FEB 03, 2000            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         ROUTINE: XWBLIB
  NAME: Protect Broker Variables in KILL
  ID: XWBLIB
 GENERAL DESCRIPTION:   This DBIA gives Kernel permission to access a tag in a
 Broker routine to extract a list of variables that Broker needs protected when
 KILL^XUSCLEAN is called by a package in an RPC.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: VARLST
 COMPONENT DESCRIPTION:   A comment line containing the list of Broker
 variables that need to be protected.  
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland
 SUBSCRIBING DETAILS:   Called from KILL^XUSCLEAN 

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<station #>,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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3032                            IA #: 3032
  DATE CREATED: FEB 03, 2000            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: XWB DIRECT RPC
  REMOTE PROCEDURE: XWB DIRECT RPC
 GENERAL DESCRIPTION:   XWB DIRECT RPC 
  This is the Broker RPC that is called to request that a RPC be run on a 
 remote system.  The data is passed by HL7 to the remote system as is the 
 return value.  The difference between this and the XWB REMOTE RPC is this is a
 blocking call meaning the user's workstation will not process anything else
 until the data returns from the remote system.  
  
 Parameters: 
  (location<station #>,rpc name,[rpc version],[1 to 10 params to the RPC]) 
  
 Return: 
   The return value is the array of data. In the case of an error condition,
 the first node of the array is equal to a string with the syntax "-1^error
 text".  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3033                            IA #: 3033
  DATE CREATED: FEB 03, 2000            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Remote Procedure                NAME: XWB DEFERRED RPC
  REMOTE PROCEDURE: XWB DEFERRED RPC
 GENERAL DESCRIPTION:   This describes the Broker RPCs that are used in support
 of running a RPC as a background task.  
  
 This RPC will return a HANDLE that can be used to check if the data has 
 returned.  The HANDLE can be used in another RPC to check the status of the
 RPC.  
  
 XWB DEFERRED RPC 
  This is the RPC that is called to request that a RPC be run through taskman
 in the background.  
  
 Parameters: 
  (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 DEFERRED STATUS 
  This RPC will return the status of a deferred RPC.  
  
 Parameters: 
  The HANDLE from the XWB DEFERRED 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" - RPC is still processing 
  "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.  
  
 XWB DEFERRED GETDATA 
  This RPC is used to return the data from the XWB DEFERRED RPC call.  
     
 Parameters: 
  The HANDLE from the XWB DEFERRED 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 DEFERRED CLEAR 
  This RPC is used to CLEAR the data under the HANDLE in the ^XTMP global.  
     
 Parameters: 
  The HANDLE from the XWB DEFERRED RPC.  
     
 Return: 
  The return value is always an array.  The first node of the array is 
  equal to 1.  
  
 XWB DEFERRED CLEARALL 
  This RPC is used to CLEAR ALL the data known to this job in the ^XTMP 
  global.  Makes use of the list in ^TMP("XWBHDL",$J,handle).  
  
 Return: 
  The return value is always an array.  The first node of the array is 
  equal to 1.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DEFERRED

NUMBER: 3034                            IA #: 3034
  FILE NUMBER: 59.7                     GLOBAL ROOT: PS(59.7
  DATE CREATED: FEB 04, 2000
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DRUG ACCOUNTABILITY
  ID: PS(59.7
GLOBAL REFERENCE: PSD(59.7,
FIELD NUMBER: 70                        FIELD NAME: LAST DRUG LINKED
  LOCATION: 70;1                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 70.1                      FIELD NAME: LAST DRUG LINKER
  LOCATION: 70;2                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 70.2                      FIELD NAME: LAST DRUG LINK DATE
  LOCATION: 70;3                        ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   
  When the Drug Acountability package is trying to link the Drug/Item file, 
  the last drug linked is stored in the LAST DRUG LINKED (#70) field. This 
  field is also used as a point at which to resume the loop upon re-entry.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
  ISC: Birmingham
 SUBSCRIBING DETAILS:   
  

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
  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
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
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
  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
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: <NMSP>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 (<NMSP>) 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: 1                  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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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
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
  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
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
  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
  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
  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: Controlled Subscription
  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: Till Otherwise Agreed
  GOOD ONLY FOR VERSION: 1.0
KEYWORDS: PXAA
COMPONENT/ENTRY POINT: $$GETFIELD(IEN,FIELD,EXTERNAL)
 COMPONENT DESCRIPTION:   Returns the value of one field in the VISIT
 (#9000010) file.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the VISIT (#9000010) file.  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the field number or name to be returned.  
VARIABLES: EXTERNAL                     TYPE: Input
 VARIABLES DESCRIPTION:   Should the value be returned in external format?
 (1/0; Optional; Defaults to 0).  
COMPONENT/ENTRY POINT: $$GETFIELDS(ARRAY,IEN,FIELDS,EXTERNAL)
 COMPONENT DESCRIPTION:   Retrieves one or more field values from a VISIT
 (#9000010) record and places the values in an array. 
  
 Will return: 1  - If was able to successfully retrieve the data.  0  - If
 record did not exist.  -1 - If invalid field list passed in.  
VARIABLES: ARRAY                        TYPE: Output
 VARIABLES DESCRIPTION:   Should be passed by reference. If the API was able to
 retrieve the data, ARRAY will be returned in the following format: 
 ARRAY(field_number)=value 
  
 If the API returned -1, ARRAY will be returned as follows: ARRAY(1)="Invalid
 field list." 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the VISIT (#9000010) file.  
VARIABLES: FIELDS                       TYPE: Input
 VARIABLES DESCRIPTION:   The fields to retrieve. 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.  
  
 - Asterisk (*) for all fields.  
VARIABLES: EXTERNAL                     TYPE: Input
 VARIABLES DESCRIPTION:   Should the values be returned in external format?
 (1/0; Optional; Defaults to 0).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: AUG 30, 2023

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
  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
  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
  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
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: 
                 <tab>KILL VAR ; initialize VAR 
                 <tab>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: 
                 <tab>KILL VAR ; initialize VAR 
                 <tab>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
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

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
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
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
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("DNS") =>> 127.0.0.15 
VARIABLES: domain_name                  TYPE: Input
 VARIABLES DESCRIPTION:   domain_name is a fully qualified domain name like
 DNS.  
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
 DNS.  
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 DNS 
  
   Example: K ZX D MAIL(.ZX,"DNS") ZW ZX 
   ZX=2 
   ZX(30)=a2.DNS.^127.0.0.1 
   ZX(50)=gateway.DNS.^127.0.0.1 

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
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
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.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  

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
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: 1
  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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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: 3061                            IA #: 3061
  FILE NUMBER: 740                      GLOBAL ROOT: QA(740,
  DATE CREATED: MAR 09, 2000
  CUSTODIAL PACKAGE: QUALITY ASSURANCE INTEGRATION
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: QAC ROLLUP FIELDS
  ID: QA(740,
GLOBAL REFERENCE: QA(740,1,'QAC')
FIELD NUMBER: 753                       FIELD NAME: QAC LAST RECORD
  LOCATION: QAC;4                       ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Field stored in file #740 (QA Site Parameter file) to
 keep track of the last record sent to the national database from the Patient
 Rep package (QAC).  
FIELD NUMBER: 754                       FIELD NAME: QAC ROLLUP TASK
  LOCATION: QAC;4                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Field stored in file #740 to allow code to check whether
 or not this task is already on the Future Task list.  This should avoid
 multiple duplicate tasks.  
 GENERAL DESCRIPTION:   QAC Last Record field is being created to allow the
 Patient Representative package (QAC) to keep track of the last record sent to
 the national database.  It is field #753.  
  
 QAC Rollup Task field is being created to hold the task number, at a site, of
 the currently scheduled run of the QAC Data Rollup.  The code will check,
 before re-tasking the job, that the task has not already been scheduled.  It
 is field #754.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE
  ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Fields are needed give for managing the daily database
 rollup. Patient Rep does not have a separate site paramter file - this type of
 data is stored int he QA Site Paramter file (#740).  

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
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.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 3/23/20 to find completed PDMP notes.  

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
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
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
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_name<space>Middle_name<space>Suffix 
  
 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 DOE,JOHN A. B. 2ND (TEST)" 
   >D STDNAME^XLFNAME(.MYNAME,"CP",.MYAUD) 
  
   >ZW MYNAME 
   MYNAME=VANDOE,JOHN A B II 
   MYNAME("FAMILY")=VAN DOE 
   MYNAME("GIVEN")=JOHN A.  
   MYNAME("MIDDLE")=B.  
   MYNAME("SUFFIX")=2ND 
  
   >ZW MYAUD 
   MYAUD=VAN DOE,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 
 VANDOE,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_name<space>Middle_name<space>Suffix(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
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: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DISPLAY CONSULT PROCEDURE ORDER INFO
  ID: GMR(123,
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: Both R/W w/Fileman
FIELD NUMBER: 13                        FIELD NAME: REQUEST TYPE
  LOCATION: 0;17                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: PATIENT LOCATION
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TO SERVICE
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.01                      FIELD NAME: CLINICAL PROCEDURE
  LOCATION: 1;1                         ACCESS: Both R/W 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
KEYWORDS: MD*1*65
KEYWORDS: GMR(123
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Hines
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   Added 5/17/23, effective with HDSO Clinical Sustainment
 patch RMPR*30*213, the Prosthetics package requires read access to File 123,
 the PROVISIONAL DIAGNOSIS field (#30.1) in order to correct a defect in the
 ICD field (#1.6) in the PROSTHETIC SUSPENSE FILE (#668) 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 9/5/24 effective with release of patch OR*3*405
 and the ICR # will be documented in patch OR*3.0*561 for routine ORQ2 which is
 referencing PROVISIONAL DIAGNOSIS CODE field (#30.1) of  REQUEST/CONSULTATION
 file #(123).  
  DATE ACTIVATED: JUL 22, 2008

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
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 3069                            IA #: 3069
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: MAR 22, 2000            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: DBIA3069                        ID: VA(200,
GLOBAL REFERENCE: .01
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   PCMM requires direct read access to the Name (.01) and
 SSN (#9) fields in the New Person (#200) for Programmer Management Advisory
 board.  
  STATUS: Pending
KEYWORDS: SSN
KEYWORDS: SOCIAL SECURITY NUMBER
KEYWORDS: NAME FIELD
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

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
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
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.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  

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
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

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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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,
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.  
FIELD NUMBER: 3                         FIELD NAME: TYPE OF IMAGING
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: CATEGORY OF EXAM
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: ORDER
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 18                        FIELD NAME: LAST ACTIVITY DATE/TIME
  LOCATION: 0;18                        ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: REQUESTING PHYSICIAN
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 22                        FIELD NAME: REQUESTING LOCATION
  LOCATION: 0;22                        ACCESS: Read w/Fileman
 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,D0,'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.  
GLOBAL REFERENCE: RAO(75.1,B
 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.  
  
 Revision History: 
         - 9/11/24 added field #22 REQUESTING LOCATION with 
           patch MECH*1.0*1 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VPS KIOSK
KEYWORDS: RA-CLASS 3
KEYWORDS: DSSV CLASS 3
KEYWORDS: MAG
KEYWORDS: MEDICOM
KEYWORDS: OR
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.  
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Patch MECH*1.0*1 processes HL7 new-order messages about
 imaging studies performed in the community but not entered through VistA.  In
 order to do this, it needs to invoke Radiology routines and make FileMan calls
 to add entries to the RAD/NUC MED PATIENT File (#70) (for existing VA
 patients), the ORDER File (#100), and the RAD/NUC MED ORDERS File (#75.1). The
 patch then creates an HL7 order-update message that transmits the study's 
 accession number to the sender. ADDED 3/2/2022, effective with MECH*1.0*1 
 Medicom Class 3 product Document Only 
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   
        2/21/22, effective with DSSV 1.1 DSS Class 3 product Document Only C3
 is requesting access to the following fields/indexes from  file 75.1: 
                           .01  NAME 
                            2  PROCEDURE 
                            3  TYPE OF IMAGING 
                            4  CATEGORY OF EXAM 
                            5  REQUEST STATUS 
                            7  ORDER 
                            18  LAST ACTIVITY DATE/TIME 
                            20  IMAGING LOCATION 
                            "B" The purpose of the B index is to lookup the
 order record given the patient record.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/03/23, effective with patch OR*3.0*535, to
 access the ORDER (#7) and REQUESTING PHYSICIAN (#14) fields to allow CPRS to
 display the ordering provider related to certain notifications.  
  DATE ACTIVATED: OCT 04, 2023

NUMBER: 3075                            IA #: 3075
  DATE CREATED: APR 07, 2000            CUSTODIAL PACKAGE: NDBI
  USAGE: Private                        TYPE: Other
  NAME: A7RCIRN GLOBAL                  STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham

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
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3077                            IA #: 3077
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG
  DATE CREATED: APR 11, 2000
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File
  NAME: Direct global access to the DRUG file (#50)
  ID: PSDRUG
GLOBAL REFERENCE: PSDRUG(D0,
FIELD NUMBER: 901                       FIELD NAME: STRENGTH
  LOCATION: DOS;1                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 902                       FIELD NAME: UNIT
  LOCATION: DOS;2                       ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: PSDRUG(D0,'DOS1',D1,
FIELD NUMBER: .01                       FIELD NAME: DISPENSE UNITS PER DOSE
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DOSE
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: PACKAGE
  LOCATION: 0;3                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: PSDRUG(D0,'DOS2',D1,
FIELD NUMBER: .01                       FIELD NAME: LOCAL POSSIBLE DOSAGE
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PACKAGE
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   Pharmacy Data Management has defined certain data
 change events within National Drug File that should delete certain fields in
 the DRUG file (#50).  To meet that request, National Drug File requests
 permission to do direct global KILLs to nodes ^PSDRUG(D0,"DOS"),
 ^PSDRUG(D0,"DOS1"), and ^PSDRUG(D0,"DOS2").  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
  ISC: Birmingham

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
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://url.visn1.url 
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.  
COMPONENT/ENTRY POINT: ORY
VARIABLES: input
VARIABLES:  
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
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
 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    
  
 Output is returned in the ORY array 
  STATUS: Active                        DURATION: Till Otherwise Agreed
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 
  DATE ACTIVATED: JUN 18, 2018

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
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
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: Health Factors in Clinical Reminders and Health Summary
  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,D1)
FIELD NUMBER: .01                       FIELD NAME: NOT USED WITH
  LOCATION: 11,D1;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.  
GLOBAL REFERENCE: AUTTHF(D0,100)
FIELD NUMBER: 100                       FIELD NAME: CLASS
  LOCATION: 100;1                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 101                       FIELD NAME: SPONSOR
  LOCATION: 100;2                       ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: AUTTHF(D0,200)
FIELD NUMBER: 200                       FIELD NAME: PRINT NAME
  LOCATION: 200                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: AUTTHF(D0,201)
FIELD NUMBER: 201                       FIELD NAME: DESCRIPTION
  LOCATION: 201                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: AUTTHF(D0,210,D1)
FIELD NUMBER: .01                       FIELD NAME: CODING SYSTEM
  LOCATION: 210,D1;1                    ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: CODE
  LOCATION: 210,D1;2                    ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DATE MAPPED
  LOCATION: 210,D1;3                    ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: AUTTHF(D0,220)
FIELD NUMBER: 220                       FIELD NAME: MINIMUM VALUE
  LOCATION: 220;1                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 221                       FIELD NAME: MAXIMUM VALUE
  LOCATION: 220;2                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 222                       FIELD NAME: MAXIMUM DECIMALS
  LOCATION: 220;3                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 223                       FIELD NAME: UCUM CODE
  LOCATION: 220;4                       ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: AUTTHF(D0,230,D1)
FIELD NUMBER: .01                       FIELD NAME: CODING SYSTEM
  LOCATION: 230;1                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: CODE
  LOCATION: 230;2                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DATE DELETED
  LOCATION: 230;3                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: USER
  LOCATION: 230;4                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: MSE REMOVAL COMPLETION DATE
  LOCATION: 230;5                       ACCESS: Direct Global R/W & w/Fileman
 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
KEYWORDS: HEALTH FACTORS
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: HEALTH SUMMARY
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   Health Summary needs the ability to read and display
 fields from Health Factors.  
  
 Added 04/21/2021, effective with patch GMTS*2.7*122.  
  DATE ACTIVATED: MAY 11, 2021

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(
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
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 
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 10/1/19, effective with YS*5.01*135.  
  DATE ACTIVATED: JUN 08, 2009

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: EDUCATION TOPICS IN CLINICAL REMINDERS AND HEALTH SUMMARY
  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
GLOBAL REFERENCE: AUTTEDT(D0,100)
FIELD NUMBER: 100                       FIELD NAME: CLASS
  LOCATION: 100;1                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 101                       FIELD NAME: SPONSOR
  LOCATION: 100;2                       ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: AUTTEDT(D0,201)
FIELD NUMBER: 201                       FIELD NAME: DESCRIPTION
  LOCATION: 201                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: AUTTEDT(D0,210,D1)
FIELD NUMBER: .01                       FIELD NAME: CODING SYSTEM
  LOCATION: 210,D1;1                    ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: CODING SYSTEM
  LOCATION: 210,D1;2                    ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DATE MAPPED
  LOCATION: 210,D1;3                    ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: AUTTEDT(D0,220)
FIELD NUMBER: 220                       FIELD NAME: MINIMUM VALUE
  LOCATION: 220;1                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 221                       FIELD NAME: MAXIMUM VALUE
  LOCATION: 220;2                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 222                       FIELD NAME: MAXIMUM DECIMALS
  LOCATION: 220;3                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 223                       FIELD NAME: UCUM CODE
  LOCATION: 220;4                       ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: AUTTEDT(D0,230,D1)
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 230;1                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: CODING SYSTEM
  LOCATION: 230;2                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DATE DELETED
  LOCATION: 230;3                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: USER
  LOCATION: 230;4                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: MSE REMOVAL COMPLETION DATE
  LOCATION: 230;5                       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
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: EDUCATION TOPICS
KEYWORDS: HEALTH SUMMARY
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   Health Summary needs the ability to read and display
 fields from Education Topics.  
  
 Added 04/21/2021, effective with patch GMTS*2.7*122.  
  DATE ACTIVATED: MAY 11, 2021

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
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: EXAMS IN CLINICAL REMINDERS AND HEALTH SUMMARY
  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,100)
FIELD NUMBER: 100                       FIELD NAME: CLASS
  LOCATION: 100;1                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 101                       FIELD NAME: SPONSOR
  LOCATION: 100;2                       ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: AUTTEXAM(D0,200)
FIELD NUMBER: 200                       FIELD NAME: PRINT NAME
  LOCATION: 200;1                       ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: AUTTEXAM(D0,201)
FIELD NUMBER: 201                       FIELD NAME: DESCRIPTION
  LOCATION: 201                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: AUTTEXAM(D0,210,D1)
FIELD NUMBER: .01                       FIELD NAME: CODING SYSTEM
  LOCATION: 210,D1;1                    ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: CODE
  LOCATION: 210,D1;2                    ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DATE MAPPED
  LOCATION: 210,D1;3                    ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: AUTTEXAM(D0,220)
FIELD NUMBER: 220                       FIELD NAME: MINIMUM VALUE
  LOCATION: 220;1                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 221                       FIELD NAME: MAXIMUM VALUE
  LOCATION: 220;2                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 222                       FIELD NAME: MAXIMUM DECIMALS
  LOCATION: 220;3                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 223                       FIELD NAME: UCUM CODE
  LOCATION: 220;4                       ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: AUTTEXAM(D0,230,D1)
FIELD NUMBER: .01                       FIELD NAME: CODING SYSTEM
  LOCATION: 230;1                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: CODE
  LOCATION: 230;2                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DATE DELETED
  LOCATION: 230;3                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: USER
  LOCATION: 230;4                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: MSE REMOVAL COMPLETION DATE
  LOCATION: 230;5                       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
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: EXAM
KEYWORDS: HEALTH SUMMARY
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   Health Summary needs the ability to read and display
 fields from Education Topics.  
                          
 Added 04/21/2021, effective with patch GMTS*2.7*122.  
  DATE ACTIVATED: NOV 09, 2021

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
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
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
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
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
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
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
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
  
 The Enterprise Health MGMT Platform (HMP) is accessing the V POV file 
 (#9000010.07) to retrieve the POV (.01), Visit (.03), Provider Narrative (.04)
 and the Primary/Secondary (.12) fields.  

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
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
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
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
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
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-DNS 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-DNS.  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
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
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
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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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 entry
 points in the Pharmacy Data Management package to perform updates related to
 matching, re-matching and un-matching Dispense Drugs in the DRUG file (#50) to
 and from NDF VA Products in the VA PRODUCT file (#50.68).  
  
 Note: These entry points should only be used for approved drug matching, 
 re-matching and un-matching functions.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
COMPONENT/ENTRY POINT: UNMDRUG(DRUGIEN)
 COMPONENT DESCRIPTION:   This entry point is used to perform a few updates
 related to un-matching a Dispense Drug from an NDF VA Product. It will delete
 the content of the following fields in the DRUG file (#50): 
  
  NATIONAL DRUG FILE ENTRY (#20) 
  VA PRODUCT NAME (#21) 
  PSNDF VA PRODUCT NAME ENTRY (#22) 
  PACKAGE SIZE (#23) 
  PACKAGE TYPE (#24) 
  CMOP ID (#27) 
  NATIONAL FORMULARY INDICATOR (#29) 
  
 It will also kill all the corresponding cross-references ("VAPN", "AQ1", 
 "APN", "AND" and "APR").  
VARIABLES: DRUGIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the pointer to the DRUG (#50) File  for the
 entry that is being un-matched from an NDF VA Product.  
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
  ISC: Birmingham
 SUBSCRIBING DETAILS:   When a Dispense Drug is matched, re-matched or
 un-matched to and from an NDF VA Product through the National Drug File (NDF)
 application a few updates must be performed to the DRUG file (#50) such as
 updates to the POSSIBLE DOSAGES sub-file (#903) and setting of some related
 fields in the "ND" node.  

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
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
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
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: 3111                            IA #: 3111
  FILE NUMBER: 50.6                     GLOBAL ROOT: PSNDF(50.6
  DATE CREATED: MAY 17, 2000            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA3111
  ID: PSNDF(50.6
GLOBAL REFERENCE: PSNDF(50.6,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
  
 VA GENERIC entries are used as findings in Clinical Reminders. Therefore 
 Clinical Reminders needs to point at the following fields.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: VA GENERIC
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

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
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
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
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
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
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
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
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
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

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
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

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
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. 
COMPONENT/ENTRY POINT: $$NEWUCID(GMRCIEN)
 COMPONENT DESCRIPTION:   This entry point returns a string that uniquely
 identifies this  record across VistAs 
VARIABLES: GMRCIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   This variable is the internal entry number from the  
 REQUEST/CONSULTATION (#123) file.  
VARIABLES: NEWUCID                      TYPE: Output
 VARIABLES DESCRIPTION:   This will return a string that uniquely identifies
 this record across VistAs 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be using PROVDX^GMRCUTL1 for VIAB PROVDX RPC 
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   Added 2/10/26, effective with patch MAG*3.0*362.
 IMAGING needs a Component NEWUCID 

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
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
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
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: RADIOLOGY EXAM DATA RETURN (SLC)
  ID: RADPT(
GLOBAL REFERENCE: RADPT(D0,'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(D0,'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(D0,'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(D0,'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: 0;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(D0,'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).  
GLOBAL REFERENCE: RADPT('AVIST'
FIELD NUMBER: 27                        FIELD NAME: VISIT
  LOCATION: 0;27                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field links the patient specific radiology exam to a
 specific visit (PCE).  
  
 LIST FILE ATTRIBUTES data: 
  
 sub-file   field #     data type (expanded) 
 --------   -------     --------------------
 70.03      27          POINTER: VISIT FILE (#9000010) 
 GLOBAL DESCRIPTION:   'AVSIT' is the RAD/NUC MED PATIENT file-wide index on
 the VISIT field. 
 GENERAL DESCRIPTION:   This Integration Agreement (IA) allows access to the
 ^RADPT global at the EXAMINATIONS (#70.03) sub-file level to obtain radiology
 exam specific data for a patient within a date range or for a patient with a
 PCE visit.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RA - GMTS
KEYWORDS: RA - PX
KEYWORDS: RA - PCE
KEYWORDS: PX*1.0*211
KEYWORDS: RA - SPN
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Patient Care Encounter (PCE) was added as a subscriber
 for patch PX*1.0*211.  

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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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: 3131                            IA #: 3131
  DATE CREATED: JUN 19, 2000
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Other                           NAME: DBIA3131
 GENERAL DESCRIPTION:   This DBIA is used to document Clinical Procedures
 exporting the protocol OR EVSEND GMRC as USE AS LINK FOR MENU ITEMS so the
 protocol MD RECEIVE will be linked to the OR EVSEND GMRC protocol.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed

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
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
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
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 Listener protocol for Clinical
 Procedures is MD RECEIVE OR.  
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   EDIS protocol is EDP OR MONITOR.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Listener protocol for VPR is VPR NA EVENTS to be added
 by VPR*1*3.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
 The protocol for HMP is HMP NA EVENTS 
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   Added 5/27/26, effective with patch NHIN*1*27 The NHIN
 subscriber protocol NHIN DAS EVENTS will be added as an Item on OR EVSEND GMRC
 to support HL7 integration with VA Occupational Health and Data Access
 Services (DAS). 

NUMBER: 3136                            IA #: 3136
  FILE NUMBER: 59.7                     GLOBAL ROOT: PS(59.7
  DATE CREATED: JUN 28, 2000
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File
  NAME: Health Summary Component Outpat Pharm (RXOP)
  ID: PS(59.7
GLOBAL REFERENCE: PS(59.7,DO,40.1
FIELD NUMBER: 40.1                      FIELD NAME: ADMISSION CANCEL OF RXS
  LOCATION: 40.1;1                      ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field is used to determine if outpatient medication
 will be cancelled after 72 hours of an admission to the medical center.  
 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 EMAIL GROUP 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 December 31, 2006.  Health Summary needs to access the parameters
 of the Pharmacy System to determine the appropriate displays for Outpatient
 Pharmacy components.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
KEYWORDS: PS(59.7
KEYWORDS: GMTSPSO
KEYWORDS: GMTSPSO7
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

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
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: 3138                            IA #: 3138
  DATE CREATED: JUN 28, 2000            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         ROUTINE: MDCON
  NAME: DBIA3138                        ID: MDCON
 GENERAL DESCRIPTION:   This DBIA is used to document the usage of the API
 $$PDATETM^MDCON(MDINST).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PDATETM(MDINST)
VARIABLES: MDINST                       TYPE: Input
 VARIABLES DESCRIPTION:   This variable can be a pointer or a variable pointer
 to the CP Instance file #702.  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   The output is Date/Time Performed Internal Fileman
 Format_"^"_Date/Time Performed External Fileman Format_"^"_Procedure Summary
 Code Text.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   API usage: 
   S VARIABLE=$$PDATETM^MDCON(MDINST) 

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
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
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   Added 6/9/21, effective with EHM*1*2 - will not be
 installed nationally.  It will be installed on at sites that are being
 converted to Cerner.   The Image Migration load tool is in 2 parts: 1)
 baseline load and 2) on-going maintenance.  The baseline load creates file
 #1606 (Image Migration) based on the contents of file #123
 (CONSULT/REQUISITION) when the load is run.  Thereafter, file #1606 is added
 to or updated when consults are resulted.  The protocol EHM CONSULTS will be a
 subscriber to GMRC EVSEND OR.  When a result is posted, EHM CONSULTS will
 identify images associated with the consult and post information about them in
 file #1606.  
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   Added 6/17/26, effective with patch NHIN*1*27 The NHIN
 subscriber protocol NHINDASI will be added as an item on GMRC EVSEND OR to
 support HL7 integration with eSHORE Employee Occupational Health and Data
 Access Services (DAS).  

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
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
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                         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 modify their calls to support strong
 authentication when made available by Infrastructure.  
  
 ICR Team: This ICR only allows subscribers to call its own RPCs.  Any other
 usage requires a separate ICR. Refer to the ICR Internal Process Guide for
 instruction on Subscriber approval.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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).  Subsequently, 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 attempting 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 and to send insurance data between VA sites.  
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   For use with the Smart Card.  
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   Added 8/31/26,  effective with patch MPI*1.0*166 
  MPI is approved to call its own RPCs.  
  The original list of called RPCs was removed.  
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
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Added 9/22/20: The Capri CLAIMS server is calling the
 MPI remote procedure "MPI GETCORRESPONDINGIDS", which only exists on the MPI
 environment. This API will be used to determine if a patient has an Active
 Cerner Correlation. This determination will then be used to alert VBA
 employees in the Capri GUI to check Cerner for new patient data.  

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
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
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
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: Controlled Subscription
  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
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 retrieve a listing of  Active'
 REMINDER/MAINTENANCE ITEMs (NAMES, field .01) for the Adhoc Health Summary
 Type (GUI RPC).  
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
 SUBSCRIBING DETAILS:   Added 5/10/24, effective with patch GMRV*5.0*40 for
 access to the 'B' cross-reference for 811.9. Vitals will use a new API to help
 us evaluate patients for Congestive Heart Failure  in conjunction with a 
 Reminder Taxonomy. 

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
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

NUMBER: 3150                            IA #: 3150
  FILE NUMBER: 50.7                     GLOBAL ROOT: DD(50.7
  DATE CREATED: JUN 10, 2003            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: DBIA 3150                       ID: DD(50.7
GLOBAL REFERENCE: DD(50.7,0
 GENERAL DESCRIPTION:   The Pharmacy Data Management (PDM) application would
 like to ask permission to create a new data dictionary global related to the
 ORDERABLE ITEM file (# 50.7).  The new global will be used to set the INACTIVE
 DATE field (#.04) as an identifier in the ORDERABLE ITEM file (# 50.7).  
  
 Here is an example of the new DD global and contents. 
  
 ^DD(50.7,0,"ID",.04) = W "   ",$$FMTE^DILIBF($P(^(0),U,4),6) 
  
 The PSSP32 routine will contain the coding logic to set the new DD global.  
 The PSSP32 routine will only be used by PDM patch # 32 and KIDS will delete
 the PSSP32 routine after the installation.  
  
 Here is a copy of the routine.  
  
 PSSP32 ;BIR/TTH-INACTIVE DATE FIELD IDENTIFIER ; 4-FEB-2000 14:17 
        ;;1.0;PHARMACY DATA MANAGEMENT;**32**;9/30/97 
        ;
 ID     ;In the ORDERABLE ITEM file (#50.7), set the INACTIVE DATE field 
         (#.04) a s an identifier.  
        S ^DD(50.7,0,"ID",.04)="W ""   "",$$FMTE^DILIBF($P(^(0),U,4),6)" 
        Q 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

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: 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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
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,<A,D or T>,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.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 02/01/2023, effective with DSSV 1.2 DSS Class 2
 product. Document Only.  

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
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.  
  DATE ACTIVATED: NOV 06, 2007

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
 GENERAL DESCRIPTION:   This call (RPC^DGPTFAPI) will return data from the
 Patient Treatment (#45) file.  (This IA# is for the API and IA# 3164 is for
 the RPC).  
  
 Input: 
 ------
  PTFNUMBR - The Patient Treatment IFN (.001 of the #45 file record) 
   RESULTS - Results array (passed by reference) 
     
 Output: 
 ------- 
     RESULTS - Results array (passed by reference) with the following 
               nodes.  
  RESULTS(0) - 1 (entry found) OR -1 (error) 
  RESULTS(1) - Type of Disposition (#72)^Place of Disposition (#75)^ 
               Principal Diagnosis (#79)^Coding System Version (pointer 
               to ICD Coding Systems #80.4 file) 
  RESULTS(2) - DX 2^DX 3^...^DX 24 (Secondary Diagnosis 2 through 
               Secondary Diagnosis 24) 
  RESULTS(3) - POA 1^POA 2^...^POA 25 (Present on Admission indicators 
               for Principal Diagnosis and Secondary Diagnosis 2 through 
               Secondary Diagnosis 24) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PTF
KEYWORDS: DGPT
COMPONENT/ENTRY POINT: RPC(.RESULTS,PTFNUMBR)
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   RESULTS - Results array (passed by reference) with 
           the following nodes.  
  
 RESULTS(0) - 1 (entry found) OR -1 (error) 
  
 RESULTS(1) - Type of Disposition (#72)^Place of 
              Disposition (#75)^ Principal 
              Diagnosis (#79)^Coding System Version 
              (pointer to ICD Coding Systems #80.4 
              file) 
  
 RESULTS(2) - DX 2^DX 3^...^DX 24 (Secondary 
              Diagnosis 2 through Secondary 
              Diagnosis 24) 
  
 RESULTS(3) - POA 1^POA 2^...^POA 25 (Present on 
              Admission indicators for Principal 
              Diagnosis and Secondary Diagnosis 2 
              through Secondary Diagnosis 24) 
VARIABLES: PTFNUMBER                    TYPE: Input
 VARIABLES DESCRIPTION:   PTFNUMBR - The Patient Treatment IFN (.001 of the #45
 file record) 
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
  DATE ACTIVATED: AUG 19, 2015

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
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
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
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)

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
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Hines
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Hines
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 6/4/20 for MHA 

NUMBER: 3163                            IA #: 3163
  DATE CREATED: AUG 10, 2000
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Other                           NAME: ATTACH TO GMRC EVSEND OR
 GENERAL DESCRIPTION:   This event takes place when CPRS is updated as a result
 of activity on Consult within Consult/Request Tracking.  
  
 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 activity to CPRS as defined in the
 'OE/RR Version 3 Package Interface Specifications' document.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   The two attached protocols are: OR RECEIVE and OCX
 ORDER CHECK HL7 RECIEVE 

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 (RPC^DGPTFAPI) will return data from the
 Patient Treatment (#45) file. (This IA# is for the RPC and IA# 3157 is for the
 API).  
  
 Input: 
 ------
 PTFNUMBR - The Patient Treatment IFN (.001 of the #45 file record) 
  RESULTS - Results array (passed by reference) 
  
 Output: 
 ------- 
     RESULTS - Results array (passed by reference) with the following 
               nodes.  
  RESULTS(0) - 1 (entry found) OR -1 (error) 
  RESULTS(1) - Type of Disposition (#72)^Place of Disposition (#75)^ 
               Principal Diagnosis (#79)^Coding System Version (pointer 
               to ICD Coding Systems #80.4 file) 
  RESULTS(2) - DX 2^DX 3^...^DX 24 (Secondary Diagnosis 2 through Secondary 
               Diagnosis 24) 
  RESULTS(3) - POA 1^POA 2^...^POA 25 (Present on Admission indicators for 
               Principal Diagnosis and Secondary Diagnosis 2 through 
               Secondary Diagnosis 24) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PTF
KEYWORDS: DGPT
  DATE ACTIVATED: AUG 19, 2015

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
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: Controlled Subscription
  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
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
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIABDX SAVE RPC references PSSDIN routine.  

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: PSJORPOE API
  ID: PSJORPOE
 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
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
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   Access to RESOLVE and SCHREQ in routine PSJORPOE for
 VIABDPS2 OISLCT RPC and OrderMgmtSvc - getMedOrderableItemDefaults.  VIA will
 also use the STARTSTP entry point for VIAB ADMIN RPC.  
  DATE ACTIVATED: JUN 08, 2011

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
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
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  ISC: Salt Lake City

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
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
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

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
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 <RET> 
  
 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
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 <UP-ARROW>, 
 <DOWN-ARROW>, <PREV>, <NEXT>, <TAB>, 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
 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
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

NUMBER: 3175                            IA #: 3175
  DATE CREATED: AUG 28, 2000            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         ROUTINE: XLFMSMT
  NAME: Measurement Functions           ID: XLFMSMT
 GENERAL DESCRIPTION:   This routine contains entry points to allow conversion
 between U.S.  (English) and Metric units.  
  STATUS: Withdrawn
COMPONENT/ENTRY POINT: $$BSA
 COMPONENT DESCRIPTION:   Usage: $$BSA(ht,wt) 
  
 Returns body surface area.  
VARIABLES: ht                           TYPE: Input
 VARIABLES DESCRIPTION:   Height in centimeters.  
VARIABLES: wt                           TYPE: Input
 VARIABLES DESCRIPTION:   Weight in kilograms.  
COMPONENT/ENTRY POINT: $$LENGTH
 COMPONENT DESCRIPTION:   Usage: $$LENGTH(val,from,to) 
  
 Returns conversion between metric length and U.S. length (either direction).
 Returns equivalent value with units.  
VARIABLES: val                          TYPE: Input
 VARIABLES DESCRIPTION:   A positive numeric value. from Unit of measure of
 val. to Unit of measure to convert val to.  
VARIABLES: from                         TYPE: Input
 VARIABLES DESCRIPTION:   Valid units in either uppercase or lowercase are: 
  
 km = kilometers       mi = miles m = meters            yd = yards cm =
 centimeters      ft = feet mm = millimeters      in = inches 
VARIABLES: to                           TYPE: Input
 VARIABLES DESCRIPTION:   Valid units in either uppercase or lowercase are: 
  
 km = kilometers       mi = miles m = meters            yd = yards cm =
 centimeters      ft = feet mm = millimeters      in = inches 
COMPONENT/ENTRY POINT: $$TEMP
 COMPONENT DESCRIPTION:   Usage: $$TEMP(val,from,to) 
  
 Converts metric temperature to U.S. temperature. Returns equivalent value with
 units.  
VARIABLES: val                          TYPE: Input
 VARIABLES DESCRIPTION:   A positive numeric value. from Unit of measure of
 val. to Unit of measure to convert val to.  
VARIABLES: from                         TYPE: Input
 VARIABLES DESCRIPTION:   Valid units in either uppercase or lowercase are: 
  
 f = Fahrenheit      c = Celsius 
VARIABLES: to                           TYPE: Input
 VARIABLES DESCRIPTION:   Valid units in either uppercase or lowercase are: 
  
 f = Fahrenheit      c = Celsius 
COMPONENT/ENTRY POINT: $$VOLUME
 COMPONENT DESCRIPTION:   Usage: $$VOLUME(val,from,to) 
  
 Converts metric volume to U.S. volume and vice versa. Converts milliliters to
 cubic inches or quarts or ounces. Returns equivalent value with units.  
VARIABLES: val                          TYPE: Input
 VARIABLES DESCRIPTION:   A positive numeric value. from Unit of measure of
 val. to Unit of measure to convert val to.  
VARIABLES: from                         TYPE: Input
 VARIABLES DESCRIPTION:   Valid units in either uppercase or lowercase are: 
  
 kl = kiloliter       cf = cubic feet hl = hectoliter      ci = cubic inch dal
 = dekaliter      gal = gallon l = liters           qt = quart dl = deciliter   
    pt = pint cl = centiliter      c = cup ml = milliliter      oz = ounce 
VARIABLES: to                           TYPE: Input
 VARIABLES DESCRIPTION:   Valid units in either uppercase or lowercase are: 
  
 kl = kiloliter       cf = cubic feet hl = hectoliter      ci = cubic inch dal
 = dekaliter      gal = gallon l = liters           qt = quart dl = deciliter   
    pt = pint cl = centiliter      c = cup ml = milliliter      oz = ounce 
COMPONENT/ENTRY POINT: $$WEIGHT
 COMPONENT DESCRIPTION:   Usage: $$WEIGHT(val,from,to) 
  
 Returns conversions between metric weights to approximate U.S. weights (in 
 either direction). Returns equivalent value with units.  
VARIABLES: val                          TYPE: Input
 VARIABLES DESCRIPTION:   A positive numeric value. from Unit of measure of
 val. to Unit of measure to convert val to.  
VARIABLES: from                         TYPE: Input
 VARIABLES DESCRIPTION:   Valid units in either uppercase or lowercase are: 
  
 t = metric tons      tn = tons kg = kilograms       lb = pounds g = grams      
      oz = ounces mg = milligram       gr = grain 
VARIABLES: to                           TYPE: Input
 VARIABLES DESCRIPTION:   Valid units in either uppercase or lowercase are: 
  
 t = metric tons      tn = tons kg = kilograms       lb = pounds g = grams      
      oz = ounces mg = milligram       gr = grain 

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
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
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 

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
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
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: 1
  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

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
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

NUMBER: 3182                            IA #: 3182
  DATE CREATED: SEP 06, 2000            CUSTODIAL PACKAGE: VBECS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: VBECA1
  NAME: DBIA3181-B                      ORIGINAL NUMBER: 3181
  ID: VBECA1
 GENERAL DESCRIPTION:   The entry point ABO^VBECA1 is provided by the Blood
 Bank package to return data from the LAB DATA file (#63) including the field
 ABO GROUP (#.05) for the DFN value provided in the call. The API will return
 the value to the caller of the API for the record found.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
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 ( ` ) 
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 3183                            IA #: 3183
  DATE CREATED: SEP 06, 2000            CUSTODIAL PACKAGE: VBECS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: VBECA1
  NAME: DBIA3181-C                      ORIGINAL NUMBER: 3181
  ID: VBECA1
 GENERAL DESCRIPTION:   The entry point RH^VBECA1 is provided by the Blood Bank
 package to return data from the LAB DATA file (#63) including the fields RH
 TYPE (#.06) for the DFN value provided in the call. The API will return the
 value to the caller of the API for the record found.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
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: 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 ( ` ) 
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 3184                            IA #: 3184
  DATE CREATED: AUG 09, 2005            CUSTODIAL PACKAGE: VBECS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: VBECA1
  NAME: DBIA3181-D                      ORIGINAL NUMBER: 3181
  ID: VBECA1
 GENERAL DESCRIPTION:   The entry point ABID^VBECA1 is provided by the Blood
 Bank package to return data from the ANTIBODIES IDENTIFIED sub-file (#63.075))
 including the fields ANTIBODIES IDENTIFIED (#.01) and ANTIBODIES IDENTIFIED
 COMMENT (#.02) for the DFN value provided in the call. The API will create an 
 array for each antibody record found by the function.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
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.  
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 3185                            IA #: 3185
  DATE CREATED: SEP 06, 2000            CUSTODIAL PACKAGE: VBECS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: VBECA1
  NAME: DBIA3181-E                      ORIGINAL NUMBER: 3181
  ID: VBECA1
 GENERAL DESCRIPTION:   The entry point AGAB^VBECA1 is provided by the Blood
 Bank package to return data from the RBC ANTIGENS ABSENT (other) sub-file
 (#63.016)) including the fields RBC ANTIGENS ABSENT (#.01) and RBC ANTIGENS
 ABSENT COMMENT (#.02) for the DFN value provided in the call. The API will
 create a .ARR array for every absent antigen record found by the function.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: AGAB
 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 absent antigens
 found by the function.  Must be passed by reference.  
  
  
 OUTPUT DEFINITION: 
  
 The function builds an array for all absent antigen records it finds in Blood
 Bank data structures. The name of the array used to store the retrieved data
 should be passed as a parameter in the call to the function. 
  
 If no absent antigen records are found, the array will be returned empty.  
  
 For each absent antigen record found, the array will contain the name of the
 absent antigen in the first data piece of the array and any absent antigen
 comments in the second data piece. The populated array will be returned with
 the following structure: 
  
 ARR("AGAB",n) = Absent Antigen ^ Absent Antigen comment 
  
 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 function builds an array for all absent antigen
 records it finds in Blood Bank data structures. The name of the array used to
 store the retrieved data should be passed as a parameter in the call to the 
 function. 
  
 If no absent antigen records are found, the array will be returned empty.  For
 each absent antigen record found, the array will contain the name of the
 absent antigen in the first data piece of the array and any absent antigen
 comments in the second data piece. The populated array will be returned with
 the following structure: ARR("AGAB",n) = Absent Antigen ^ Absent Antigen
 comment Where "n" is a sequential index number.  
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 3186                            IA #: 3186
  DATE CREATED: SEP 06, 2000            CUSTODIAL PACKAGE: VBECS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: VBECA1
  NAME: DBIA3181-F                      ORIGINAL NUMBER: 3181
  ID: VBECA1
 GENERAL DESCRIPTION:   The entry point AGPRES^VBECA1 is provided by the Blood
 Bank package to return data from the RBC ANTIGENS PRESENT(other) sub-file
 (#63.13)) including the fields RBC ANTIGENS PRESENT (#.01) and RBC ANTIGENS
 PRESENT COMMENT (#.02) for the DFN value provided in the call. The API will
 create a .ARR array for every antigen record found by the function.    
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: AGPRES
 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 antigens found by
 the function.  This array must be passed as a parameter by reference.  
  
  
 OUTPUT DEFINITION: 
  
 The function builds an array for all antigen records it finds in Blood Bank
 data files. The name of the array used to store the retrieved data should be
 passed in as a parameter in the call to the function. 
  
 If no antigens are found, the array will be returned empty.  
  
 For each antigen record found, the array will contain the name of the antigen
 in the first data piece of the array and any antigen comments in the second
 data piece.  The populated array will be returned with the following
 structure: 
  
 ARR("AGPRES",n) = Antigen ^ Antigen comment 
  
 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 an array that will store the value of any
 antigens found by the function.  This array must be passed as a parameter by
 reference.  
  
 The function builds an array for all antigen records it finds in Blood Bank
 data files. The name of the array used to store the retrieved data should be
 passed in as a parameter in the call to the function. 
  
 If no antigens are found, the array will be returned empty.  
  
 For each antigen record found, the array will contain the name of the antigen
 in the first data piece of the array and any antigen comments in the second
 data piece.  The populated array will be returned with the following
 structure: ARR("AGPRES",n) = Antigen ^ Antigen comment Where "n" is a
 sequential index number.  
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 3187                            IA #: 3187
  DATE CREATED: AUG 09, 2005            CUSTODIAL PACKAGE: VBECS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: VBECA1
  NAME: DBIA3181-G                      ORIGINAL NUMBER: 3181
  ID: VBECA1
 GENERAL DESCRIPTION:   The entry point TRRX^VBECA1(DFN, .ARR) is provided by
 the VistA Blood Establishment Computer Software (VBECS) package to return data
 stored in 2 sub-files in the LAB DATA file (#63).  The two sub-files and the 
 respective fields are: 1) TRANSFUSION RECORD sub-file (#63.017) at fields 
 TRANSFUSION DATE/TIME (#.01) and TRANSFUSION REACTION TYPE (#.11) which are
 reactions that are associated with a particular transfusion; and 2) 
 TRANSFUSION REACTION DATE sub-file (#63.0171) at fields TRANSFUSION REACTION
 DATE (#.01) and TRANSFUSION REACTION TYPE (#.02) which are reactions that
 could not be associated with a particular transfusion episode.   The
 Application Programmer Interface (API) will build an array in which each
 element will contain transfusion reaction data for the DFN value provided in
 the call.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: TRRX
 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 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.  
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 3188                            IA #: 3188
  DATE CREATED: SEP 07, 2000            CUSTODIAL PACKAGE: VBECS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: VBECA1
  NAME: DBIA3181-H                      ORIGINAL NUMBER: 3181
  ID: VBECA1
 GENERAL DESCRIPTION:   The entry point BBCMT^VBECA1(DFN, .ARR) is provided by
 the VistA Blood Establishment Computer Software (VBECS) package to return all
 blood bank comments, for a particular patient, stored in BLOOD BANK COMMENTS
 sub-file (#63.076) at field BLOOD BANK COMMENTS (.01).  The Application
 Programmer Interface (API) will build an array in which each element will
 contain a record of the blood bank comments found for the DFN of the patient 
 provided in the function call.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: BBCMT
 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 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 blood bank comments found in Blood Bank patient records via the
 function.  
  
 Retrieve blood bank comments on the patient.  If none exist on record, the 
 array will be returned empty.  
  
 For each blood comment record found, the array element will be assigned the
 blood bank comments.  The populated array be returned with the following
 structure:   
  
 ARR("BBCMT",n) = Blood Bank Comment Text 
  
 Where "n" is a sequential index number 
VARIABLES: DFN                          TYPE: Input
 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.  
VARIABLES: .ARR                         TYPE: Both
 VARIABLES DESCRIPTION:   The name of the array, passed to the API by
 reference, that will be used to store the blood bank comments found in Blood
 Bank patient records via the function.  
  
 Retrieve blood bank comments on the patient.  If none exist on record, the
 array will be returned empty.  
  
 For each blood comment record found, the array element will be assigned the
 blood bank comments.  The populated array be returned with the following
 structure: ARR("BBCMT",n) = Blood Bank Comment Text Where "n" is a sequential
 index number 
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 3189                            IA #: 3189
  DATE CREATED: SEP 07, 2000            CUSTODIAL PACKAGE: VBECS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: VBECA1
  NAME: DBIA3181-I                      ORIGINAL NUMBER: 3181
  ID: VBECA1
 GENERAL DESCRIPTION:   The entry point AUTO^VBECA1(DFN, .ARR) is provided by
 the VistA Blood Establishment Computer Software (VBECS) package to return
 data, for a particular patient, stored in the BLOOD INVENTORY file (#65) using
 fields COMPONENT (.04), EXPIRATION DATE/TIME (#.06), and RESTRICTED FOR (#8).  
 The Application Programmer Interface (API) will build an array in which each
 element will contain the available autologous units found for the DFN of the
 patient provided in the call.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: AUTO
 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 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 available autologous units via the function.  
  
 Retrieve available autologous units on the patient.  If none exist on record,
 the array will be returned empty.  
  
 For each available autologous unit found, the array element will be assigned
 the component type value at the first data piece and the expiration date value
 at the second data piece.  
  
 The populated array be returned with the following structure: 
  
 ARR("AUTO",n) = Component Type ^ Expiration Date 
  
 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 available autologous units via the
 function.  
  
 Retrieve available autologous units on the patient.  If none exist on record,
 the array will be returned empty.  
  
 For each available autologous unit found, the array element will be assigned
 the component type value at the first data piece and the expiration date value
 at the second data piece.  
  
 The populated array be returned with the following structure: ARR("AUTO",n) =
 Component Type ^ Expiration Date Where "n" is a sequential index number.  
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 3190                            IA #: 3190
  DATE CREATED: SEP 08, 2000            CUSTODIAL PACKAGE: VBECS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: VBECA3
  NAME: DBIA3190-A                      ORIGINAL NUMBER: 3190
  ID: VBECA3
 GENERAL DESCRIPTION:   The entry point EN^VBECA3 is provided by the Blood Bank
 package to collect data by calling EN^LR7OSBR with the Laboratory patient
 identifier (LRDFN) value provided in the call. The API will create entries in
 the ^TMP global for every record found by the function.  This is a wrapper
 call to replace the use of EN^LR7OSBR by CPRS.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   INPUT DEFINITION: 
  
 LRDFN = Internal entry number from the Laboratory Data file (#63) (Passed as a
 parameter) 
  
  
 OUTPUT DEFINITION: 
  
 The function will call EN^LR7OSBR and pass the "LRDFN" parameter it receives
 in its own invocation.  EN^LR7OSBR gathers Blood Bank report data and formats
 it for presentation to a CPRS GUI interface.  This API (EN^VBECA3) will not
 change any of the data formatting or logic of EN^LR7OSBR, but simply will be
 the new entry point for CPRS to use in producing the report. ^LR7OSBR calls
 ^LR7OSBR1, which reads Blood Bank data and creates entries in ^TMP("LRC",$J)
 for the presentation of the data.  CPRS agrees to stop calling EN^LR7OSBR and
 instead call EN^VBECA3(LRDFN).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3191                            IA #: 3191
  DATE CREATED: SEP 08, 2000            CUSTODIAL PACKAGE: VBECS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: VBECA3
  NAME: DBIA3190-B                      ORIGINAL NUMBER: 3190
  ID: VBECA3
 GENERAL DESCRIPTION:   The entry point EN1^VBECA3 is provided by the Blood
 Bank package to collect data by calling EN1^LR7OSBR with 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 is a wrapper
 call to replace the use of EN1^LR7OSBR by CPRS.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   INPUT DEFINITION: 
  
 DFN = internal entry number from the PATIENT file (#2) (Passed as a parameter) 
  
  
 OUTPUT DEFINITION: 
  
 The function will call EN1^LR7OSBR and pass the "DFN" parameter it receives in
 its own invocation.  EN1^LR7OSBR gathers Blood Bank report data and formats it
 for presentation to the CPRS ListManager interface.  This API (EN1^VBECA3)
 will not change any of the data formatting or logic of EN1^LR7OSBR, but simply
 will be the new entry point for CPRS to use in producing the report.  ^LR7OSBR
 calls ^LR7OSBR1, which reads Blood Bank data and creates entries in
 ^TMP("LRC",$J) for the presentation of the data.  CPRS agrees to stop calling
 EN1^LR7OSBR and instead call EN1^VBECA3(DFN).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3192                            IA #: 3192
  DATE CREATED: SEP 07, 2000            CUSTODIAL PACKAGE: VBECS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: VBECA5
  NAME: DBIA3192                        ID: VBECA5
 GENERAL DESCRIPTION:   The entry point OBP^VBECA5 is provided by the VistA
 Blood Establishment Computer Software (VBECS) package to return data found in
 the BLOOD PRODUCT file (#66) in which the data found at the CAN BE REQUESTED
 field (#. 15) is equal to "1". The Application Programmer Interface (API) will 
 create entries in the ^TMP global for the records found.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: OBP
 COMPONENT DESCRIPTION:   INPUT DEFINITION: None 
  
 OUTPUT DEFINITION: 
  
 For each record found to match, the function will create an entry in the ^TMP
 global at the subscript ("VBECOBP",$J,NAME) where "NAME" is NAME field (#.01)
 of the BLOOD PRODUCT file.  
  
 If no records in the BLOOD PRODUCT file are found to match, the function will
 create no entries in the ^TMP global.  
  
 The ^TMP global will have the following structure for each entry created: 
  
 ^TMP("VBECOBP",$J,NAME) = NAME 
SUBSCRIBING PACKAGE: SURGERY            ISC: Birmingham

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
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
  
 This functionality is being released in HMP*2.0*2 
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/18/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce  product sharing the CRMS
 namespace. The CRMS VAHC Remote Application includes the CRMS VAHC Option,
 which includes required RPCs. TIU AUTHORIZATION is one of the Remote
 Procedures included in the CRMS VAHC Option. The Remote Application uses Data
 Access Services/National Health Information Network (DAS/NHIN) as the
 middleware to interface with VistA.  
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added July 21, 2025 effective with CDSP*1*1.  
 Requesting access to RPC TIU AUTHORIZATION to support APPS covered by the
 Clinical Decision Support Platform. This will allow the calling CDSP
 application to evaluate privilege to perform any ASU-mediated action on a TIU
 document 

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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 3196                            IA #: 3196
  DATE CREATED: SEP 13, 2000
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                NAME: GMVUTL7
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

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
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
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.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
  
 This functionality is being released in HMP*2.0*2 

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
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.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
 This functionality is being released in HMP*2.0*2 
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/17/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace.
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes 
 required RPCs. TIU IS THIS A CONSULT? is one of the Remote Procedures included
 in the CRMS VAHC Option.  The Remote Application uses Data Access 
 Services/National Health Information Network (DAS/NHIN) as the middleware to
 interface with VistA.  
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 6/10/26, effective with patch CDSP*1.0*4  This
 RPC will be used by CDSP APP Ai Scribe Integration to determine if the note
 title is a consult note during the process of writing notes. This integration
 enables providers to use AI generated progress notes during their clinical
 encounters. 

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
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.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   Effective with VPS*1*3 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
 This functionality is being released in HMP*2.0*2 
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/18/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce  product sharing the CRMS
 namespace. The CRMS VAHC Remote Application includes the CRMS VAHC Option,
 which includes required RPCs. TIU LONG LIST OF TITLES is one of the Remote
 Procedures included in the CRMS VAHC Option. The Remote Application uses Data
 Access Services/National Health Information Network (DAS/NHIN) as the
 middleware to interface with VistA.  

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
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.  

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
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX

NUMBER: 3209                            IA #: 3209
  DATE CREATED: SEP 20, 2000            CUSTODIAL PACKAGE: 1
  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
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
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
 SUBSCRIBING DETAILS:   ADDED JUNE 2009 
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 9/26/23, effective with CDSP*1*0 CDSP is
 developing a Precision Oncology workflow to automatically ingest genetic test
 results into VistA and VistA imaging. The workflow needs to identify patients
 based on demographic data present in test results. This RPC is used to update
 a note generated by VistA imaging to add a clinician as an additional signer
 on the note.  
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/17/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace.
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes 
 required RPCs. TIU UPDATE ADDITIONAL SIGNERS is one of the Remote Procedures
 included in the CRMS VAHC Option.  The Remote Application uses Data Access
 Services/National Health Information Network (DAS/NHIN) as the middleware to
 interface with VistA.  

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
SUBSCRIBING PACKAGE: SCHEDULING

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
 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
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. 
  DATE ACTIVATED: JUL 29, 2009

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
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

NUMBER: 3215                            IA #: 3215
  DATE CREATED: OCT 03, 2000            CUSTODIAL PACKAGE: 1
  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
KEYWORDS: DDR
KEYWORDS: DELETE
KEYWORDS: ENTRY
KEYWORDS: RPC
KEYWORDS: FMDC

NUMBER: 3216                            IA #: 3216
  DATE CREATED: OCT 03, 2000            CUSTODIAL PACKAGE: 1
  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
KEYWORDS: DDR
KEYWORDS: RPC
KEYWORDS: FMDC
KEYWORDS: FILER

NUMBER: 3217                            IA #: 3217
  DATE CREATED: OCT 03, 2000            CUSTODIAL PACKAGE: 1
  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
KEYWORDS: DDR
KEYWORDS: RPC
KEYWORDS: FMDC
KEYWORDS: FIND1

NUMBER: 3218                            IA #: 3218
  DATE CREATED: OCT 03, 2000            CUSTODIAL PACKAGE: 1
  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
KEYWORDS: DDR
KEYWORDS: RPC
KEYWORDS: FMDC
KEYWORDS: FINDER

NUMBER: 3219                            IA #: 3219
  DATE CREATED: SEP 20, 2000            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Remote Procedure                NAME: DDR KEY VALIDATOR
  REMOTE PROCEDURE: DDR KEY VALIDATOR
 GENERAL DESCRIPTION:   This agreement indicates that the DDR KEY VALIDATOR RPC
 necessary for use of the Fileman Delphi Components is a supported reference.  
  STATUS: Withdrawn
KEYWORDS: DDR
KEYWORDS: KEY
KEYWORDS: VALIDATOR
KEYWORDS: RPC
KEYWORDS: FMDC
SUBSCRIBING PACKAGE: FILEMAN DELPHI COMPONENTS
  ISC: Oakland

NUMBER: 3220                            IA #: 3220
  DATE CREATED: OCT 03, 2000            CUSTODIAL PACKAGE: 1
  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
KEYWORDS: DDR
KEYWORDS: RPC
KEYWORDS: FMDC
KEYWORDS: GET
KEYWORDS: DD
KEYWORDS: HELP

NUMBER: 3221                            IA #: 3221
  DATE CREATED: OCT 03, 2000            CUSTODIAL PACKAGE: 1
  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
KEYWORDS: DDR
KEYWORDS: RPC
KEYWORDS: FMDC
KEYWORDS: LISTER

NUMBER: 3222                            IA #: 3222
  DATE CREATED: OCT 03, 2000            CUSTODIAL PACKAGE: 1
  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
KEYWORDS: DDR
KEYWORDS: RPC
KEYWORDS: FMDC
KEYWORDS: LOCK
KEYWORDS: UNLOCK

NUMBER: 3223                            IA #: 3223
  DATE CREATED: OCT 03, 2000            CUSTODIAL PACKAGE: 1
  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
KEYWORDS: DDR
KEYWORDS: RPC
KEYWORDS: FMDC
KEYWORDS: VALIDATOR

NUMBER: 3224                            IA #: 3224
  DATE CREATED: OCT 03, 2000            CUSTODIAL PACKAGE: 1
  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
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
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: 3226                            IA #: 3226
  DATE CREATED: MAY 19, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         ROUTINE: XUTMUTL
  NAME: XUTMUTL                         ID: XUTMUTL
 GENERAL DESCRIPTION:   This routine has some supported API's for access to
 Taskman data.  
  STATUS: Retired
COMPONENT/ENTRY POINT: OPTSTAT(option,.root)
 COMPONENT DESCRIPTION:   This entry point provides access to data about
 scheduled options.  
VARIABLES: option                       TYPE: Input
 VARIABLES DESCRIPTION:   This input parameter is the name of the option to
 return data about.  
VARIABLES: root                         TYPE: Both
 VARIABLES DESCRIPTION:   This parameter is passed by reference (.root) and
 gets the array of returned data.  root=count (the number of entries returned). 
 
 root(i)=task#^ scheduled start time^ re-schedule frequence^ specialqueuing 
  

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
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<space> 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

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
SUBSCRIBING PACKAGE: FEE BASIS          ISC: Washington/Silver Spring

NUMBER: 3229                            IA #: 3229
  DATE CREATED: OCT 24, 2000
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSSCPRS
  NAME: DBIA3229                        ID: PSSCPRS
 GENERAL DESCRIPTION:   If the APPLICATION PACKAGES' USE field (#63) in DRUG
 file (#50) for at least one of the dispense drugs associated with the
 orderable item is marked for IV use and at least one of the IV additives/IV
 solutions associated with the dispense drug are flagged for IV FLUID ORDER
 ENTRY, this field shall be optional. If not, a value in the schedule field
 shall be mandatory. CPRS shall be passed this information from Pharmacy Data
 Management to make this determination.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CPRS
 COMPONENT DESCRIPTION:   D CPRS^PSSCPRS(.array) where the array is defined by
 the calling application returns.  
VARIABLES: ARRAY('DRUG')                TYPE: Input
 VARIABLES DESCRIPTION:   This is the dispense drug IEN variable.  
VARIABLES: ARRAY('ITEM')                TYPE: Input
 VARIABLES DESCRIPTION:   This is the orderable item IEN  variable.  
VARIABLES: ARRAY('DOSAGE')              TYPE: Input
 VARIABLES DESCRIPTION:   This is the Dosage variable.  
VARIABLES: ARRAY('DUPD')                TYPE: Input
 VARIABLES DESCRIPTION:   This is the dispense units per dose variable.  
VARIABLES: ARRAY('PACK')                TYPE: Input
 VARIABLES DESCRIPTION:   This variable determines the original order Package
 (i.e. if it is "O" then the translation will be from Outpatient to Inpatient
 and visa versa.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   A local variable array with the following nodes: 
   
 RESULT(0) 
   The value of this variable will take the following values: 
     1 in case there is data to be returned to CPRS 
    -1 in case of error.  
    
 RESULT(1) 
   This variable contains 4 pieces.  
     Piece 1 is the dispense drug IEN.  
     Piece 2 is the  orderable Item IEN.  
     Piece 3 is the  dosage.  
     Piece 4 is the  dispense units per   dose.  
  
 RESULT(2) 
   This variable will have an error description in case of RESULT(0)=-1, and in 
   some cases.  
  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   This call shall apply transfer rules on the input
 variables, initially it will returns the dispense drug IEN, orderable Item
 IEN, dosage, dispense units per dose, but more data may be returned later.  

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
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: Controlled Subscription
  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 supporting the VISTA
 HIS.  
 GLOBAL DESCRIPTION:   This is the field 1 cross-reference.  
GLOBAL REFERENCE: XMB(1,D0,0)
FIELD NUMBER: 1                         FIELD NAME: TIME ZONE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   04/03/2023 - Effective with DSSO*2.0*3, 
    APAT requests FileMan read access of the 
    TIME ZONE (#1) field of the MAILMAN SITE 
    PARAMETERS (#4.3) file for the purpose of 
    documenting the accurate timing of local 
    events.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 10/14/25 effective with DSIY*1.5*6 for the
 purpose of documenting the accurate timing of local events.  
  DATE ACTIVATED: APR 05, 2023

NUMBER: 3232                            IA #: 3232
  FILE NUMBER: 9.7                      GLOBAL ROOT: XPD(9.7,
  DATE CREATED: OCT 27, 2000            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: FILE COMMENTS
  ID: XPD(9.7,
GLOBAL REFERENCE: XPD(9.7,IEN,2)
FIELD NUMBER: 6                         FIELD NAME: FILE COMMENT
  LOCATION: 2;E1,240                    ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Imaging package usage is to provide extended build
 identification.  
 GLOBAL DESCRIPTION:   This is the latest imaging package install.  
 GENERAL DESCRIPTION:   The Vista Imaging application supports the acquisition
 and storage of clinical images received from diverse, foreign devices and
 databases.  It is our experience that the flexibility necessary to support a
 broad range of products requires timely updates.  This trend results in a loss
 of homogeneity in the software distribution as sites are not always able keep 
 their systems current.  It is an FDA requirement that we track our product so
 that we can anticipate local issues and provide comprehensive support.  It is
 for this reason that the Imaging usage report, which triggers monthly reports
 that update a local Vista Imaging development database, requires a more
 granular build reference.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   The following code demonstrates usage: 
  
         S X=$G(^XPD(9.7,IEN,2)) X ^%ZOSF("UPPERCASE") S LATEST=Y 
         Q VER_U_$P($P(LATEST,VER,2)," ") 

NUMBER: 3233                            IA #: 3233
  DATE CREATED: OCT 27, 2000
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSSORUTL                     NAME: DBIA3233
  ID: PSSORUTL
 GENERAL DESCRIPTION:   With the implementation of the Pharmacy Ordering
 Enhancements project, Dosages will now be stored in the DRUG file (#50), in
 the form of Possible Dosages and Local Possible Dosages. When a medication
 (Orderable Item) is selected in CPRS (Computerized Patient Record System) in
 the medication order entry process, that Orderable Item will be passed to the
 Pharmacy Data Management package, along with the Pharmacy application and
 patient internal entry number. The Pharmacy Data Management package will pass
 back to CPRS Dosage information from the Drugs in the DRUG file (#50) that are 
 matched to that Orderable Item.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DOSE(PSSX,PD,TYPE,PSSDFN)
 COMPONENT DESCRIPTION:   This entry point will be used by CPRS to retrieve all
 of the available Dosages in the DRUG file (#50) for the selected Orderable
 Item.  Additionally, other information will be returned from the DRUG file
 (#50) and the DOSAGE FORM file (#50.606) that will be used by CPRS in the 
 medication order entry process.  
VARIABLES: PSSX                         TYPE: Input
 VARIABLES DESCRIPTION:   This is simply the name of the array to be built that
 will return the information to CPRS.  
VARIABLES: PD                           TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the PHARMACY
 ORDERABLE ITEM file (#50.7) of the selected Orderable Item in the CPRS
 medication order entry process.  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   This variable will indicate the Pharmacy package of
 the order. It will be "O" for Outpatient, "U" for Unit Dose, or "I" for "IV".  
VARIABLES: PSSDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   This variable is optional. It is the internal entry
 number from the PATIENT file (#2). It will only be used for Outpatient package
 orders, to calculate the maximum number of refills allowed.  
VARIABLES: PSSX(#)                      TYPE: Output
 VARIABLES DESCRIPTION:   This is the array returned in the call, subscripted
 with whatever variable name is passed into the call. This output array will
 increment for as many unique Drug dosages that are found. This output array is
 divided into 6 pieces, separated by the "^" character. The pieces are: 
  
 Piece 1 = Possible Dosage. This piece is a numeric value, and will only have
 data if it is a Possible Dosage that is being returned. This is calculated by
 multiplying the Strength by the Dispense Units per Dose.  
  
 Piece 2 = Unit. This is the Unit of measure for the product. This value is
 formatted via the API $$DOSE^PSSORUTE(DOSE) (see IA# 4555) in order to add
 leading zeros to decimal numbers and a blank space between number and unit.  
  
 Piece 3 = Dispense Units per Dose. Similar to piece 1, this is a numeric 
 value, and will only be returned if a Possible Dosage is being returned.  This
 value multiplied by the Strength will be the Possible Dosage.  
  
 Piece 4 = Noun. This is the Noun that is associated with the Dosage. For 
 example, a Dosage Form of TAB would likely have a Noun of TABLET(S).  
  
 Piece 5 = Instructions. This can be used for the dosage selection. For a 
 Possible Dosage, it is the numeric dosage concatenated with the Unit. Some 
 examples would be 325 MG, 650 MG, and 10 MG/15 ML. For a Local Possible 
 Dosage, it would be a text dosage. Some examples would be 1 DROP, 2 DROPS, and
 1 TEAPSOONFUL. This value is formatted via the API $$DOSE^PSSORUTE(DOSE) (see
 IA# 4555) in order to add leading zeros to decimal numbers and a blank space
 between number and unit.  
  
 Piece 6 = Dispense Drug. This is internal entry number from the DRUG file 
 (#50).  
  
 Piece 7 = Price. If the Drug has a Price Per Dispense Unit associated with it,
 this will be that price times the Dispense Units per Dose. If the Dosage does
 not have a Dispense Units per Dose, and does not have a Price Per Dispense
 Unit, this will be null.  
VARIABLES: PSSX('DD',Dispense Drug)     TYPE: Output
 VARIABLES DESCRIPTION:   This array contains specific Drug information of the
 Drug that is associated with the Dosage. For every drug entry (piece 6 of the
 PSSX(#) array), there will be a corresponding entry in this PSSX("DD",
 Dispense Drug IEN) array. The pieces of this array are separated by the "^" 
 character, and they are as follows: 
  
 Piece 1 = Name. This is the name of the Drug, the .01 field of the DRUG file
 (#50).  
  
 Piece 2 = Price Per Dispense Unit. This is the price per dispense unit for 
 this drug.  
  
 Piece 3 = Local Non-formulary flag. If the drug is designated as 
 non-formulary, then a 1 will be returned in this piece, otherwise, a null will
 be returned.  
  
 Piece 4 = Dispense Unit. This is the Dispense Unit for the drug.  
  
 Piece 5 = Strength. This is a value that represents the single dose of 
 medication supplied by this product. This field could be null for some drugs,
 such as multi-ingredient drugs.  
  
 Piece 6 = Unit. This is the unit of measure of this product. This value is
 formatted via the API $$DOSE^PSSORUTE(DOSE) (see IA# 4555) in order to add
 leading zeros to decimal numbers and a blank space between number and unit.  
  
 Piece 7 = Dosage Form. This is the name of the Dosage Form of the product.  
  
 Piece 8 = Maximum # of refills. This will only be returned for Outpatient 
 medication orders. It can be used as a default for the maximum number of 
 refills allowed for the medication order.  
  
 Piece 9 = Schedule requirement flag. This is always set to 1. This piece is
 not currently used.  
  
 Piece 10 = DEA Special Handling Flag. This field can have 1 of 3 values: 
   1 = The DEA Special Handling field contains a "1", or contains a "2". 
    This indicates that a wet signature is required.  
   2 = The DEA Special Handling field does not meet wet signature 
    requirements, but does indicate a Controlled Substance. This is the 
    case if the field contains a "3", or a "4", or a "5".  
   0 = All others.  
  
 Piece 11 = Flag for splitting Dosage Form. This will be a 0 or a 1. The only
 time it will be a 1 is if there are Possible Dosages associated with the drug,
 and there is at least 1 Possible Dosage that is entered for the drug with a
 decimal point. This indicates that the Dosage Form can be split.  
VARIABLES: PSSX('MISC')                 TYPE: Output
 VARIABLES DESCRIPTION:   This array contains information relating to the
 Dosage Form that is associated with the selected Orderable Item. It contains 3
 pieces, separated by the "^" character. The pieces are: 
  
 Piece 1 = Verb. This is the verb associated with the Dosage Form. Examples 
 would be INSTILL for the Dosage Form of SOLN,OTIC, and TAKE for the Dosage 
 Form of TAB.  
  
 Piece 2 = Preposition. This is the preposition associated with the Dosage 
 Form. Examples would be BY for the Dosage Form of TAB, and TO for the Dosage
 Form of CREAM.  
  
 Piece 3 = Conjunction. This is the conjunction associated with the Dosage 
 Form. Most Dosage Forms would have a conjunction of OF.  
VARIABLES: PSSX(#,#)                    TYPE: Output
 VARIABLES DESCRIPTION:   This array contains the same information as the
 PSSX(#) array. This array is only returned when Possible Dosages are being
 returned, and there are duplicate Possible Dosages with different Dispense
 Units per Dose. The PSSX(#) array would contain the Possible Dosage with the
 lowest Dispense Units per Dose, and the PSSX(#,#) arrays would contain all
 other Possible Dosages with higher Dispense Units per Dose.  
VARIABLES: PSSX('PI',#)                 TYPE: Output
 VARIABLES DESCRIPTION:   This array holds the default Patient Instructions
 from the Pharmacy Orderable Item (#50.7) file.  
VARIABLES: PSSX('DEA')                  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
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   Access to DOSE^PSSORUTL for VIABDPS2 OISLCT RPC and
 OrderMgmtSvc - getMedOrderableItemDefaults method 
  DATE ACTIVATED: DEC 15, 2015

NUMBER: 3234                            IA #: 3234
  DATE CREATED: OCT 30, 2000
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSSORPH                      NAME: DBIA3234
  ID: PSSORPH
 GENERAL DESCRIPTION:   With the implementation of the Pharmacy Ordering
 Enhancements project, Dosages will now be stored in the DRUG file (#50), in
 the form of Possible Dosages and Local Possible Dosages. When a Dispense Drug
 is selected during the medication order entry process in the Outpatient
 Pharmacy and Inpatient Medications applications, that drug will be passed to
 the Pharmacy Data Management application, along with the Pharmacy application 
 and Patient. Pharmacy Data Management will pass back the available Dosages 
 from the DRUG file (#50) and other related information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DOSE(PSSX,PD,TYPE,PSSDFN,PSSDUPD)
 COMPONENT DESCRIPTION:   This entry point will be used by the Outpatient
 Pharmacy and the Inpatient Medications applications. Returned in this call
 will be all of the available Dosages for that drug. Additionally, other
 information will be returned from the DRUG file (#50) and the DOSAGE FORM file
 (#50.606) that will be used in the medication order entry process in the
 Pharmacy applications.  
VARIABLES: PSSX                         TYPE: Input
 VARIABLES DESCRIPTION:   This is simply the name of the array to be built that
 will return the information to the Pharmacy applications.  
VARIABLES: PD                           TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the DRUG file
 (#50).  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   This variable will indicate the pharmacy application
 of the order. It will be "O" for Outpatient, "U" for Unit Dose, and "I" for
 IV.  
VARIABLES: PSSDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   This variable is optional. It is the internal entry
 number from the PATIENT file (#2). It will only be used for Outpatient orders,
 to calculate the maximum number of refills allowed.  
VARIABLES: PSSUPD                       TYPE: Input
 VARIABLES DESCRIPTION:   This variable is optional. If this variable is passed
 in, it represents a Dispense Units per Dose value that was entered during the
 medication order entry process in the pharmacy application. A new Dosage will
 be calculated for this Dispense Units per Dose, and returned in the array.  
VARIABLES: PSSX(#)                      TYPE: Output
 VARIABLES DESCRIPTION:   This is the array returned in the call, subscripted
 with whatever variable name is passed into the call. This output array will
 increment for as many unique Drug dosages that are found. This output array is
 divided into 12 pieces, separated by the "^" character. The pieces are: 
  
 Piece 1 = Possible Dosage. This piece is a numeric value, and will only have
 data if it is a Possible Dosage that is being returned. This is calculated by
 multiplying the Strength by the Dispense Units per Dose.  
  
 Piece 2 = Unit. This is the Unit of measure for the product. This value is
 formatted via the API $$DOSE^PSSORUTE(DOSE) (see IA# 4555) in order to add
 leading zeros to decimal numbers and a blank space between number and unit.  
  
 Piece 3 = Dispense Units per Dose, or Local Possible Dosage. If there is data
 in piece 1 of this array, indicating that this is a Possible Dosage, then
 piece 3 will be the Dispense Units per Dose for the Possible Dosage.  If piece
 1 is null, then piece 3 is the Local Possible Dosage.  
  
 Piece 4 = Dispense Drug. This is the internal entry number from the DRUG file
 (#50).  
  
 Piece 5 = Strength. This is a value that represents the single dose of 
 medication supplied by this product. This field could be null for some drugs,
 such as multi-ingredient drugs.  
  
 Piece 6 = Noun. This is the Noun that is associated with the Dosage. For 
 example, a Dosage Form of TAB would likely have a Noun of TABLET(S).  
  
 Piece 7 = Dosage Form. This is the name of the Dosage Form of the product.  
  
 Piece 8 = Verb. This is the verb associated with the Dosage Form. Examples 
 would be INSTILL for the Dosage Form of SOLN,OTIC, and TAKE for the Dosage 
 Form of TAB.  
  
 Piece 9 = Preposition. This is the preposition associated with the Dosage 
 Form. Examples would be BY for the Dosage Form of TAB, and TO for the Dosage
 Form of CREAM.  
  
 Piece 10 = Conjunction. This is the conjunction associated with the Dosage 
 Form. Most Dosage Forms would have a conjunction of OF. This is only returned
 when Local Possible Dosages are being returned.  
  
 Piece 11 = Dosage Display. This is only returned for Possible Dosages. It is a
 combination of Strength and Unit, which makes for a readable selection
 display. This value is formatted via the API $$DOSE^PSSORUTE(DOSE) (see IA#
 4555) in order to add leading zeros to decimal numbers and a blank space
 between number and unit.  
  
 Piece 12 = BCMA Units Per Dose. This will only be returned for Inpatient 
 Orders.  
VARIABLES: PSSX('DD',#)                 TYPE: Output
 VARIABLES DESCRIPTION:   This array contains specific Drug information of the
 Drug that is associated with the Dosage. For every drug entry (piece 3 of the
 PSSX(#) array), there will be a corresponding entry in this PSSX("DD",
 Dispense Drug IEN) array. The pieces of this array are separated by the "^" 
 character, and they are as follows: 
  
 Piece 1 = Name. This is the name of the Drug, the .01 field of the DRUG file
 (#50).  
  
 Piece 2 = Price Per Dispense Unit. This is the price per dispense unit for 
 this drug.  
  
 Piece 3 = Local Non-formulary flag. If the drug is designated as 
 non-formulary, then a 1 will be returned in this piece, otherwise, a null will
 be returned.  
  
 Piece 4 = Dispense Unit. This is the Dispense Unit for the drug.  
  
 Piece 5 = Strength. This is a value that represents the single dose of 
 medication supplied by this product. This field could be null for some drugs,
 such as multi-ingredient drugs.  
  
 Piece 6 = Unit. This is the unit of measure of this product. This value is
 formatted via the API $$DOSE^PSSORUTE(DOSE) (see IA# 4555) in order to add
 leading zeros to decimal numbers and a blank space between number and unit.  
  
 Piece 7 = Maximum # of refills. This will only be returned for Outpatient 
 medication orders. It can be used as a default for the maximum number of 
 refills allowed for the medication order.  
  
 Piece 8 = This piece is not being used.  
  
 Piece 9 = Noun. This is the Noun that is associated with the Dosage. For 
 example, a Dosage Form of TAB would likely have a Noun of TABLET(S).  
  
 Piece 10 = Verb. This is the verb associated with the Dosage Form.  Examples
 would be INSTILL for the Dosage Form of SOLN,OTIC, and TAKE for the Dosage
 Form of TAB.  
  
 Piece 11 = Dosage flag. 1 means that a numeric free text entry in the dosage
 field can be interpreted as a Possible Dosage, with an associated numeric
 Dispense Units per Dose. 0 means that a numeric free text entry in the dosage
 field cannot be interpreted as a Possible Dosage, and must be interpreted as a
 Local Possible Dosage.  
VARIABLES:  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham
  DATE ACTIVATED: SEP 02, 2015

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
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
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<integer> for # of seconds.  M<integer> for # of minutes.  H<integer> for #
 of hours.  D<integer> for # of days.  W<integer> for # of weeks.  L<integer>
 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
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   Access will be used by VIABDPS2 OISLCT RPC for VIA's
 OrderMgmtSvc - getMedOrderableItemDefaults 

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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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.  
COMPONENT/ENTRY POINT: MAXDS(INPUT)
 COMPONENT DESCRIPTION:   This API accepts an array containing the Pharmacy
 Orderable Item (required) and Dispense Drug (optional) and returns the maximum
 number of Days Supply allowed to be dispensed for the specific medication.  
VARIABLES: INPUT('PSOI')                TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PHARMACY ORDERABLE ITEM file (#50.7).
 This parameter is required.  
VARIABLES: INPUT('DRUG')                TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the DRUG file (#50). This parameter is
 optional. If not passed, the API will return the  highest value from all the
 dispense drugs linked to the Pharmacy Orderable Item.  
VARIABLES: $$MAXDS                      TYPE: Output
 VARIABLES DESCRIPTION:   Maximum number of days supply that can be dispensed
 for the orderable item and/or dispense drug.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
  DATE ACTIVATED: OCT 26, 2015

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@DNS", 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.DNS".  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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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@DNS" 
         . 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.DNS",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: 3241                            IA #: 3241
  FILE NUMBER: 9000011                  GLOBAL ROOT: ANPNPROB(D0,0)
  DATE CREATED: NOV 01, 2000            CUSTODIAL PACKAGE: PROBLEM LIST
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA3241
  ID: ANPNPROB(D0,0)
 GENERAL DESCRIPTION:   This DBIA documents Dental Record Manager use of the
 PROBLEM file (9000011).  This IA shall be replaced with an API as the
 Integration Agreement as soon 
    as Problem List can provide the necessary API.  The Dental Record Manager
 Uses FILEMAN to deactivate a Problem List Entry. 
  STATUS: Pending
SUBSCRIBING PACKAGE: DENTAL

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
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
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 messages 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
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 
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Added 10/31/24 effective with RA*5*220, Radiology is
 doing exception handling and needs to look up the radiology HL7 Message ID
 using FM in order to do a status check.  

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
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
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
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
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. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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: 3251                            IA #: 3251
  DATE CREATED: NOV 14, 2000            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         ROUTINE: MCUIMAGO
  NAME: Imaging 3251                    ID: MCUIMAGO
 GENERAL DESCRIPTION:   Vista Imaging is requesting permission to call
 KILL^MCUIMAG0.  This is required to delete an image pointer in a Medicine file
 entry. 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: KILL
 COMPONENT DESCRIPTION:   Deletes the image pointer for the specified entry in
 the specified Medicine file. 
VARIABLES: MCFILE                       TYPE: Input
 VARIABLES DESCRIPTION:   The Medicine file number.  
VARIABLES: MCD0                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to one of the Medicine Procedure data file.  
VARIABLES: MCD1                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to one of the entries in the Imaging multiple
 field.  
VARIABLES: OK                           TYPE: Output
 VARIABLES DESCRIPTION:   A return flag to indicate the success or failure of
 deleting the image pointer.  
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   If the image selected to be deleted has a image pointer
 filed in a Medicine file, the deletion routine will call KILL^MCUIMAG0 to
 remove the image pointer.  

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
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

NUMBER: 3253                            IA #: 3253
  FILE NUMBER: 691                      GLOBAL ROOT: MCAR(691
  DATE CREATED: NOV 15, 2000            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: Imaging 3253
  ID: MCAR(691
GLOBAL REFERENCE: C
FIELD NUMBER: 1                         FIELD NAME: MEDICAL PATIENT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field identifies the medical patient's name.  
 GLOBAL DESCRIPTION:   Cross reference on the Medical Patient field.  
GLOBAL REFERENCE: 0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field identifies the date and time when the echo was
 taken.  
 GENERAL DESCRIPTION:   This request is for the purpose of displaying a list of
 entries for a specified patient and date range in the Medicine file 691
 (ECHO).  
  
 Vista Imaging is acquiring images directly from modalities and on occassion
 the provided pseudo transaction number assigned is incorrect and the automatic
 image processing will require user interaction.   During this user interaction
 the user will be provided with the patient name of the failed image.  The
 end-user will need to match the image to a Medicine file entry that is
 displayed on the screen. 
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   This request is for allowing access to read the "C"
 cross reference of the Medicine file to obtain the entry number and read the
 following fields: procedure subspecialty, patient, and date field.  e 

NUMBER: 3254                            IA #: 3254
  FILE NUMBER: 694                      GLOBAL ROOT: MCAR(694
  DATE CREATED: NOV 15, 2000            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: Imaging 3254
  ID: MCAR(694
GLOBAL REFERENCE: C
FIELD NUMBER: 1                         FIELD NAME: Medical Patient
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field identifies the medical patient name.  
 GLOBAL DESCRIPTION:   Cross refence on the Medical Patient field.  
GLOBAL REFERENCE: 0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field identifies the time and date of entry.  
FIELD NUMBER: 2                         FIELD NAME: PROCEDURE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   
  This field identifies a pointer to the procedure location file.  
 GENERAL DESCRIPTION:   This request is for the purpose of displaying a list of
 entries for a specified patient and date range in the Medicine file 694
 (HEMATOLOGY) 
  
  
 Vista Imaging is acquiring images directly from modalities and on occasion the
 provided pseudo transaction number assigned is incorrect and the automatic
 image processing will require user interaction.   During this user interaction
 the user will be provided with the patient name of the failed image.  The
 end-user will need to match the image to a Medicine file entry that is
 displayed on the screen.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   This request is for allowing access to read the "C"
 cross reference of the Medicine file to obtain the entry number and read the
 following fields: procedure subspecialty, patient, and date field.  

NUMBER: 3255                            IA #: 3255
  FILE NUMBER: 691.1                    GLOBAL ROOT: MCAR(691.1
  DATE CREATED: NOV 15, 2000            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: Imaging 3255
  ID: MCAR(691.1
GLOBAL REFERENCE: C
FIELD NUMBER: 1                         FIELD NAME: MEDICAL PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field identifies the name of the patient.  
 GLOBAL DESCRIPTION:   Cross reference on the medical patient.  
GLOBAL REFERENCE: 0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This date/time field identifies the catheterization
 procedure.  
 GENERAL DESCRIPTION:   This request is for the purpose of displaying a list of
 entries for a specified patient and date range in the Medicine file 691.1
 (CARDIAC CATHETERIZATION) 
  
  
 Vista Imaging is acquiring images directly from modalities and on occasion the
 provided pseudo transaction number assigned is incorrect and the automatic
 image processing will require user interaction.   During this user interaction
 the user will be provided with the patient name of the failed image.  The
 end-user will need to match the image to a Medicine file entry that is
 displayed on the screen.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   
  
 This request is for allowing access to read the "C" cross reference of the 
 Medicine file to obtain the entry number and read the following fields: 
 procedure subspecialty, patient, and date field.  

NUMBER: 3256                            IA #: 3256
  FILE NUMBER: 691.5                    GLOBAL ROOT: MCAR(691.5
  DATE CREATED: NOV 15, 2000            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: IMAGING 3256
  ID: MCAR(691.5
GLOBAL REFERENCE: C
FIELD NUMBER: 1                         FIELD NAME: MEDICAL PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field identifies the patient.  
 GLOBAL DESCRIPTION:   Cross reference on the medical patient field.  
GLOBAL REFERENCE: 0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field identifies the specific date/time for the EKG
 procedure.  
 GENERAL DESCRIPTION:   This request is for the purpose of displaying a list of
 entries for a specified patient and date range in the Medicine file 691.5 
 (ELECTROCARDIOGRAPHY).  
  
  
 Vista Imaging is acquiring images directly from modalities and on occasion the
 provided pseudo transaction number assigned is incorrect and the automatic
 image processing will require user interaction.   During this user interaction
 the user will be provided with the patient name of the failed image.  The
 end-user will need to match the image to a Medicine file entry that is
 displayed on the screen.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   This request is for allowing access to read the "C"
 cross reference of the Medicine file to obtain the entry number and read the
 following fields: procedure subspecialty, patient, and date field.  

NUMBER: 3257                            IA #: 3257
  FILE NUMBER: 699                      GLOBAL ROOT: MCAR(699
  DATE CREATED: NOV 15, 2000            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: IMAGING 3257
  ID: MCAR(699
GLOBAL REFERENCE: C
FIELD NUMBER: .02                       FIELD NAME: MEDICAL PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field identifies the name of the patient.  
 GLOBAL DESCRIPTION:   Cross reference on the Medical Patient field.  
GLOBAL REFERENCE: 0
FIELD NUMBER: .01                       FIELD NAME: APPOINTMENT DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the date/time of the Endscopy
 procedure.  
FIELD NUMBER: 1                         FIELD NAME: PROCEDURE
  LOCATION: 0;12                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   
  This field identifies the specific procedure performed.  
 GENERAL DESCRIPTION:   This request is for the purpose of displaying a list of
 entries for a specified patient and date range in the Medicine file 699
 (ENDOSCOPY).  
  
  
 Vista Imaging is acquiring images directly from modalities and on occasion the
 provided pseudo transaction number assigned is incorrect and the automatic
 image processing will require user interaction.   During this user interaction
 the user will be provided with the patient name of the failed image.  The
 end-user will need to match the image to a Medicine file entry that is
 displayed on the screen.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   his request is for allowing access to read the "C"
 cross reference of the Medicine file to obtain the entry number and read the
 following fields: procedure subspecialty, patient, and date field.  

NUMBER: 3258                            IA #: 3258
  FILE NUMBER: 699.5                    GLOBAL ROOT: MCAR(699.5
  DATE CREATED: NOV 15, 2000            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: IMAGING 3258
  ID: MCAR(699.5
GLOBAL REFERENCE: C
FIELD NUMBER: .02                       FIELD NAME: MEDICAL PATIENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field identifies the patient.  
GLOBAL REFERENCE: 0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Date and time for Generalized procedure.  
FIELD NUMBER: .06                       FIELD NAME: PROCEDURE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field points to file 697.2 and is the generalized
 procedure being performed.  
 GENERAL DESCRIPTION:   This request is for the purpose of displaying a list of
 entries for a specified patient and date range in the Medicine file 699.5
 (GENERIC MEDICINE).  
  
 Vista Imaging is acquiring images directly from modalities and on occasion the
 provided pseudo transaction number assigned is incorrect and the automatic
 image processing will require user interaction.   During this user interaction
 the user will be provided with the patient name of the failed image.  The
 end-user will need to match the image to a Medicine file entry that is
 displayed on the screen.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   This request is for allowing access to read the "C"
 cross reference of the Medicine file to obtain the entry number and read the
 following fields: procedure subspecialty, patient, and date field.  

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,<DFN>).  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,<DFN>)) 
  
 Where DFN is the IEN of the patient in the Patient File.  
  STATUS: Active
COMPONENT/ENTRY POINT: RGHL7(991.1
 COMPONENT DESCRIPTION:   Checking for the existance of
 $D(^RGHL7(991.1,"ADFN",218,<DFN>)) 
  
 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
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 - DECISION SUPPORT SYSTEM EXTRACTS
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Added 7/31/20, effective with TIU*1*290 (CPRS31B) to
 access the .01 field.  

NUMBER: 3261                            IA #: 3261
  GLOBAL ROOT: DD(                      DATE CREATED: NOV 24, 2000
  CUSTODIAL PACKAGE: 1                  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
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: 3262                            IA #: 3262
  FILE NUMBER: 3.5                      GLOBAL ROOT: %ZIS(1,
  DATE CREATED: DEC 04, 2000            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DEVICE FILE
  ID: %ZIS(1,
GLOBAL REFERENCE: %ZIS(1,DA,1)
FIELD NUMBER: 1                         FIELD NAME: $I 
  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,'SUBTYPE')
FIELD NUMBER: 3                         FIELD NAME: SUBTYPE
  LOCATION: SUBTYPE;1                   ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The GEN. MED. REC. - VITALS package (aka Vitals)
 requests permission to read File 3.5 values to handle printing from within the
 GUI environment.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  ISC: Hines

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
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 3265                            IA #: 3265
  FILE NUMBER: 3.2                      GLOBAL ROOT: %ZIS(2,
  DATE CREATED: DEC 04, 2000            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: TERMINAL TYPE FILE
  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,1)
FIELD NUMBER: 1                         FIELD NAME: RIGHT MARGIN
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The GEN. MED. REC. - VITALS package (aka Vitals)
 requests permission to read File 3.2 values to handle printing from within the
 GUI environment.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  ISC: Hines

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
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:   Added 11/28/2006 
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)
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 11/26/2021, effective with DSSV*1.0*1 DSS Class 3
 product Document Only 
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI
 SUBSCRIBING DETAILS:   Added 10/26/26, effective with patch DSIR*8.2*19 The
 application will use the Date of Birth as a partial patient identifier. 

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
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:   Added 11/28/2006 
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. 
 
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   Added 11/29/22, effective with DSSV*1.1. Document only
 Class 2 
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI
 SUBSCRIBING DETAILS:   Added 10/26/26, effective with patch DSIR*8.2*19 The
 application will use the (Last 4 of the) SSN as a partial patient identifier.  

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
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 

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
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
KEYWORDS: ISI
KEYWORDS: ISI*1.1*110 DFN
KEYWORDS: VistARad COTS
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.  
SUBSCRIBING PACKAGE: ISI IMAGING
 SUBSCRIBING DETAILS:   Added 1/10/23 effective with ISI*1.1*110 

NUMBER: 3271                            IA #: 3271
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG(D0,4,0
  DATE CREATED: DEC 19, 2000
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File
  NAME: Direct writes to the DRUG file (#50)
  ID: PSDRUG(D0,4,0
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: NEW VALUE
  LOCATION: 0;5                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: NDF UPDATE
  LOCATION: 0;6                         ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   National Drug File requests approval to directly write
 to the ACTIVITY LOG multiple field (#4) in the DRUG file (#50).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
  ISC: Birmingham

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
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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES

NUMBER: 3274                            IA #: 3274
  DATE CREATED: APR 21, 2003            CUSTODIAL PACKAGE: HINQ
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: DVBLEHNQ
  NAME: HINQ                            ID: DVBLEHNQ
 GENERAL DESCRIPTION:   The GUI Load/Edit process created for the Registration
 Smart Card requires HINQ information and needs to be able to trigger a HINQ
 Inquiry.  Modifications in an existing API (EN^DVBHQZ4) to make it
 non-interactive.  The new API is EN^DVBLEHNQ.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   This is an array that will be sent to the GUI client
 side to report success (1) or failure (0) to initiate a HINQ request on the
 patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient file IEN, passed from the GUI client
 side.  
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 3275                            IA #: 3275
  DATE CREATED: DEC 27, 2000            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: DGLEG7
  NAME: GET IB DATA                     ID: DGLEG7
 GENERAL DESCRIPTION:   The Smart Card GUI client side needs to gather Sponsor
 information for the GUI Load/Edit Registration process.  A Registration RPC
 call will call the existiong IB API GET^IBCNSU4.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: SPONSOR
COMPONENT/ENTRY POINT: HINQ
COMPONENT/ENTRY POINT: SPNSR
VARIABLES: DGDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN from the Patient file (#2).  
VARIABLES: ARRAY                        TYPE: Output
 VARIABLES DESCRIPTION:   An array of Sponsor information that will be used to
 send Sponsor information to the GUI Smart Card client side.  
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 3276                            IA #: 3276
  DATE CREATED: APR 21, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: IBCNSU42
  NAME: DBIA3276                        ID: IBCNSU42
 GENERAL DESCRIPTION:   This agreement allows the Smart Card GUI client to file
 sponsor information in Integrated Billing from the GUI Load/Edit Registration 
 process.  Smart Card will utilize a non-interactive call to the new routine
 IBCNSU42 (which mirrors the interactive routine IBCNSU41) to file the sponsor
 information collected from the GUI client.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: SPONSOR
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This is the callable entry point to file sponsor
 information in the SPONSOR (#355.8), SPONSOR RELATIONSHIP (#355.81), and 
 SPONSOR PERSON (#355.82) files in Integrated Billing.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   This array returns any errors in filing encountered
 by this API.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This variable contains a pointer to the patient in
 the PATIENT (#2) file.  
VARIABLES: IBARR                        TYPE: Input
 VARIABLES DESCRIPTION:   This array contains edited values from the GUI
 Load/Edit functionality for filing in Integrated Billing sponsor files.  The
 value of this array element has the form 
  
       1^2^3^4^5^6^7^8^9^10^11, where 
  
  1 = Sponsor Name 
  2 = Sponsor Social Security Number 
  3 = Sponsor Military Status (A=Active Duty, R=Retired) 
  4 = Sponsor Military Branch (pointer BRANCH OF SERVIVE (#23) file) 
  5 = Sponsor Rank in Military 
  6 = Family Prefix (Relationship of patient to the sponsor) 
  7 = Sponsor Type (T:Tricare, C=CHAMPVA) 
  8 = Sponsor Date of Birth 
  9 = Effective Date of Sponsor Relationship 10 = Expiration Date of Sponsor
 Relationship 11 = Pointer to the sponsor in the SPONSOR (#355.8) file 
VARIABLES: IBI                          TYPE: Input
 VARIABLES DESCRIPTION:   IBI is the value of a subscript that identifies the
 location of the sponsor data in the IBARR input variable array (i.e., 
 IBARR(IBI) is the array element whose value is the eleven concatenated sponsor
 data values).  
VARIABLES: IBARR2                       TYPE: Input
 VARIABLES DESCRIPTION:   This array contains current values from Integrated
 Billing sponsor files.  It will be used to compare to the values in IBARR, to
 determine which fields need filing.  
VARIABLES: IBFD                         TYPE: Output
 VARIABLES DESCRIPTION:   This output variable is a flag which is set to 1 if a
 call to the routine DIE is made, which indicates that some data filing has
 taken place.  
COMPONENT/ENTRY POINT: LIST
 COMPONENT DESCRIPTION:   This is the callable entry point used by the Smart
 Card GUI client to retrieve all of a patient's sponsor relationships from the 
 SPONSOR RELATIONSHIP (#355.81) file.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This variable contains a pointer to the patient in
 the PATIENT (#2) file.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   This output variable array contains all of a
 patient's sponsor relationships.  The array returns the same results as the 
 supported call to GET^IBCNSU4, except that the data is re-formatted to meet
 the needs of the GUI application.  
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

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
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
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
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   Access will be used by VIA for: 
  
   VIABDPS2 OISLCT RPC for OrderMgmtSvc - getMedOrderableItemDefaults 
   VIAB DFLTSPLY RPC for OrderMgmtSvc - getDaysMedicationSupply 

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
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    <tab>K VAR 
                    <tab>S DFN=33,SUB=75 
                    <tab>S FROM=2990101,TO=3001231 
                    <tab>D SUB^MCARUTL2(.VAR,DFN,SUB,FROM,TO) 
               or 
          Case 2    <tab>K VAR 
                    <tab>S DFN=33,SUB="GENERIC SUBSPECIALTY" 
                    <tab>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: 
                    <tab> KILL VAR 
                    <tab> 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
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: 
                   <tab>K IMAGE 
                   <tab>S FN=699.5,IEN=33 
                   <tab>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
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
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
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
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
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
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
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
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   Added 0/22/2025, effective with NHIN*1*26, this RPC is
 defined in the NHIN/DAS context option "NHIN DAS CC", which is defined in the
 REMOTE APPLICATION file entry name "NHIN DAS CC". The RPC is called to provide 
 read only data to the calling system. NHIN will use this RPC to facilitate the
 CTO office processing of additional community provider data using the existing
 DAS account, remote application and context option. This is specific to the
 DAS VistA service account which processes Community Care data to VistA. The
 use case is a community provider completes an exam and faxes the results into
 a VAMC. These results are stored in file share and a process that the CTO
 office is building picks up. These results need to be written back to VistA
 and the originating Consult closed out.  

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
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.  

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
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
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   5/10/13-The Mental Health Program Office contracted
 with a vendor to provide the Behavioral Health Lab (BHL) software. BHL is a
 vendor product that calls this VistA RPC.  
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
 SUBSCRIBING DETAILS:   Added 10-23-2006. 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
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   3/26/15-Scheduling added as a subscriber for PCMM Web.  
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 10/02/23, effective with patch CDSP*1*0 CDSP is
 developing a Precision Oncology workflow to automatically ingest genetic test
 results into VistA and VistA imaging. The workflow needs to identify patients 
 based on demographic data present in test results which includes last 4 digits
 of the SSN.  
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/31/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS
 namespace.The CRMS VAHC Remote Application includes the CRMS VAHC Option,
 which includes required RPCs.  ORWPT LAST5 is one of the Remote Procedures
 included in the CRMS VAHC Option.  The Remote Application uses Data Access 
 Services/National Health Information Network (DAS/NHIN) as the middleware to
 interface with VistA.  
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   Added 08/19/2025, effective with NHIN*1*26, this RPC is
 defined in the NHIN/DAS context option "NHIN DAS CC", which is defined in the
 REMOTE APPLICATION file entry name "NHIN DAS CC". The RPC is called to provide 
 read only data to the calling system. NHIN will use this RPC to facilitate the
 CTO office processing of additional community provider data using the existing
 DAS account, remote application and context option. This is specific to the
 DAS VistA service account which processes Community Care data to VistA. The
 use case is a community provider completes an exam and faxes the results into
 a VAMC. These results are stored in a file share and a process that the CTO
 office is building picks up these results need to be written back to VistA and
 the originating Consult closed out.  

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
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.  
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
 SUBSCRIBING DETAILS:   Added as a subscriber for JLV 2.6 release 

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
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: MENTAL HEALTH
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
 SUBSCRIBING DETAILS:   Added 10-23-2006. 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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
 Effective with HMP*2.0*2 

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
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

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
KEYWORDS: PXRMRPCD
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

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
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
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)="<RESULT>^1^FINANCIAL QUERY SENT" or S RESULT(0)="<RESULT>^1^A
 FINANCIAL QUERY IS NOT REQUIRED FOR THIS PATIENT" if successful, and
 RESULT(0)="<RESULT>^0^UNABLE TO PERFORM FINANCIAL QUERY", S
 RESULT(0)="<RESULT>^1^A FINANCIAL QUERY IS NOT REQUIRED FOR THIS PATIENT" or S
 RESULT(0)="<RESULT>^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
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
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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
 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
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 
  DATE ACTIVATED: FEB 21, 2014

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
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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 3306                            IA #: 3306
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Other
  NAME: SC TEAM INFORMATION List Template
 GENERAL DESCRIPTION:   The [PXCE SC DISPLAY TEAM INFO] protocol uses the SC
 TEAM INFORMATION List Template.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: SC TEAM INFORMATION
KEYWORDS: TEAM INFORMATION
KEYWORDS: DISPLAY TEAM INFORMATION
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   The [PXCE SC DISPLAY TEAM INFO] protocol uses the
 Scheduling List Template SC TEAM INFORMATION to maintain a consistency of
 similar data presented in Scheduling.  

NUMBER: 3307                            IA #: 3307
  DATE CREATED: MAR 10, 2005            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: Other
  NAME: DBIA 3307 - Imaging & Fileman routines
 GENERAL DESCRIPTION:   Fileman gives Imaging permission to distribute and
 download Fileman routines onto their DICOM gateway. 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Imaging will download load FM22 routines with the
 exception of Fileman Init* routines. The FM22 routines are not renamed nor
 modified on the gateways.  Fileman will never be inited on the gateways. 
 Imaging use Fileman DB calls to store entries in the Image file and image 
 pointers in associated application files utilizing API written by the 
 application developers. 
  
  
 The process on these gateway are limited to processing images and sending 
 information to image acquisition devices all done in an automated process that
 does not require user interaction other than to start or stop the process. 
 These gateways only have Imaging M applications and no other VistA Application
 is present. The gateways are in service 24hrs/7days.  

NUMBER: 3308                            IA #: 3308
  DATE CREATED: MAR 02, 2001            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Other
  NAME: DBIA 3308 - Imaging points to file1
 GENERAL DESCRIPTION:   Fileman gives permission to the Imaging package to
 point out to File #1 from the Imaging's PARENT DATA FILE (#2005.03). No LAYGO
 access is allowed to file #1. 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Imaging file 2005.03 (PARENT DATA FILE) has a field
 number .04 (FILE POINTER) defined as a pointer to the file #1.  The field has
 been setup with no LAYGO access.  The file contains all the VistA applications
 that store image pointers and the sublevel where the image pointer is stored.  
 For example the entry for the Radiology Report file looks like: 
  
 FILE/SUBFILE NUMBER: 74                 FILE/SUBFILE NAME: RADIOLOGY 
   ABBREVIATION: RAD                     GLOBAL ROOT TYPE: ROOT1 
   FILE POINTER: RAD/NUC MED REPORTS 
  
 The Imaging KIDS build sends the PARENT DATA file fully populated. This file
 is not updated by any end-user; neither menu option nor GUI application is
 sent to modify the file.  The file is sent with security set to an "@" for all
 levels.  The file is used internally by Imaging routines to verify the
 application where the images pointer will be stored and to limit the
 applications Imaging interfaces with.  
  
  
 Our DD for this fields looks like: 
  
 ^DD(2005.03,.04,0) = FILE POINTER^P1'^DIC(^0;4^Q  

NUMBER: 3309                            IA #: 3309
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  ROUTINE: SDPPTEM                      NAME: PCLINE-SDPPTEM Function Call
  ORIGINAL NUMBER: 3305                 ID: SDPPTEM
 GENERAL DESCRIPTION:   PXCE functionality requires access a patient's PC
 Provider, Associate Provider and Team Information.  Routine PXCE makes a call
 to the API $$PCLINE^SDPPTEM passing Patient's DFN and Date information.  
 $$PCLINE^SDPPTEM as a function returns the necessary data formatted as an 80
 character line, or "" if none.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: Provider
KEYWORDS: Team
KEYWORDS: PCLINE
KEYWORDS: SDPPTEM
COMPONENT/ENTRY POINT: PCLINE
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Input: DFN=patient ifn 
VARIABLES: SDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   Input: SDATE=effective date (optional) 
VARIABLES: PCLINE                       TYPE: Output
 VARIABLES DESCRIPTION:   Output: PC provider, associate and team formatted as
 80 character line, or "" if none 
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany

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
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

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
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

NUMBER: 3312                            IA #: 3312
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Other
  NAME: SC PCMM ROLL Security Key
 GENERAL DESCRIPTION:   The PC Assign or Unassign, [PXCE SC PC
 Assign/Unassign], protocol is locked by the SC PCMM ROLL security key and can
 only be used by users who have this key assigned.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: SC PCMM ROLL
KEYWORDS: PXCE required keys
KEYWORDS: PXCE SC PC
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   [PXCE SC PC Assign/Unassign], SC PC Assign or Unassign
 required key .  

NUMBER: 3313                            IA #: 3313
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  ROUTINE: SDUTL2                       NAME: ELSTAT and COLLAT - SDUTL2
  ID: SDUTL2
 GENERAL DESCRIPTION:   The routine PXCE uses the SCHEDULING "miscellaneous
 utilities" program SDUTL2 to access patient eligibility statuses.  Accessing
 SDUTL2 at entry points ELSTAT and COLLAT, PXCE accesses "eligibility status"
 and "collateral eligibility status" functions respectively.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: SDUTL2
KEYWORDS: ELIGIBILITY STATUS
KEYWORDS: COLLATERAL ELIGIBILITY
KEYWORDS: PXCE
COMPONENT/ENTRY POINT: ELSTAT
 COMPONENT DESCRIPTION:   ELSTAT^SDUTL2 IS A SCHEDULING UTILITY/FUNCTION TO
 ACCESS "ELIGIBILITY STATUS" 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   INPUT:  DA = patient IEN 
VARIABLES: ELSTAT                       TYPE: Output
 VARIABLES DESCRIPTION:   "ELSTAT" FUNCTION OUTPUT OUTPUT: 
      Function Value - returns the internal entry number for 
      patient's eligibility status.  
COMPONENT/ENTRY POINT: COLLAT
 COMPONENT DESCRIPTION:   COLLAT^SDUTL2 IS A SCHEDULING UTILITY PXCE WILL USE
 TO ACCESS "COLLATERAL ELIGIBILITY STATUS" 
VARIABLES: SDEC                         TYPE: Input
 VARIABLES DESCRIPTION:   INPUT:  SDEC = patient eligibility status 
VARIABLES: COLLAT                       TYPE: Output
 VARIABLES DESCRIPTION:   "COLLAT" FUNCTIONAL OUTPUT: 
  
 OUTPUT:  1 = collateral patient  0 = non-collateral patient 
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   PXCE ACCESS TO ELIGIBILITY STATUS. (ELSTAT, COLLAT) 

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
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: 1
  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
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: 3316                            IA #: 3316
  FILE NUMBER: .11                      GLOBAL ROOT: DD('IX'
  DATE CREATED: JUL 22, 2004            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: HARSET DD('IX'                  ID: DD('IX'
GLOBAL REFERENCE: DD('IX',ZZIEN
 GLOBAL DESCRIPTION:   Hardsetting global to contain all filds invovled in new
 cross reference AMPIZZ for the .01 field: 
  
 S ^DD("IX",DA,0)="2^AMPIZZ^Inactivate ICN when patient is ZZ'd or delete 
 d^MU^^F^IR^I^2^^^^^A" 
         S ^DD("IX",DA,.1,0)="^^12^12^3000824^" 
         S ^DD("IX",DA,.1,1,0)="The set of this cross reference is to 
 inactivate a patient with an ICN" 
         S ^DD("IX",DA,.1,2,0)="(991.01) that have been ZZ'd.  The rules for
 inactivation will be" 
         S ^DD("IX",DA,.1,3,0)="enforced." 
         S ^DD("IX",DA,.1,4,0)=" " 
         S ^DD("IX",DA,.1,5,0)="The kill of this cross reference is to 
 inactivate a patient with" 
         S ^DD("IX",DA,.1,6,0)="an ICN (991.01) that has been deleted (@ 
 entered on the.01). " 
         S ^DD("IX",DA,.1,7,0)=" " 
         S ^DD("IX",DA,.1,8,0)="The rules for Inactivtion will be enforced.  If
 in either situation, the" 
         S ^DD("IX",DA,.1,9,0)="rules don't allow for automatically 
 inactivating the ICN, an exception" 
         S ^DD("IX",DA,.1,10,0)="message will be generated." 
         S ^DD("IX",DA,.1,11,0)=" " 
         S ^DD("IX",DA,.1,12,0)="Inactivating an ICN deletes fields 991.01, 
 991.0 2, 991.03 and 991.04" 
         S ^DD("IX",DA,1)="I $T(ZZSET^MPIFDEL)'="""",$E(X2(1),1,2)=""ZZ"" D 
 ZZSET^MPIFDEL(DA,X2(1))" 
         S ^DD("IX",DA,2)="I $T(ZZKILL^MPIFDEL)'="""",X2(1)="""" D 
 ZZKILL^MPIFDEL(DA,X2(1))" 
         S ^DD("IX",DA,11.1,0)="^.114IA^1^1" 
         S ^DD("IX",DA,11.1,1,0)="1^F^2^.01^^^F" 
         S ^DD("IX",DA,11.1,"B",1,1)="" 
         S ^DD("IX",DA,11.1,"BB",1,1)="" 
  
 Hardsetting global to contain all filds invovled in new cross reference  ATSSN
 on the .09 field (the DA value here will be different than the one above): 
  
         S ^DD("IX",DA,0)="2^ATSSN^Inactivates Pts that have 5 leading zeros
 for SSN^MU^^F^IR^I^2^^^^^A" 
         S ^DD("IX",DA,.1,0)="^^5^5^3020111^" 
         S ^DD("IX",DA,.1,1,0)="The set of this cross reference is to 
 inactivate a patient with an ICN" 
         S ^DD("IX",DA,.1,2,0)="(991.01) that have the SSN field value changed
 to a SSN with 5 leading " 
         S ^DD("IX",DA,.1,3,0)="zeros. The rules for inactivation will be
 enforced." 
         S ^DD("IX",DA,.1,4,0)="" 
         S ^DD("IX",DA,.1,5,0)="There is not a kill of this cross reference
 since SSN is a required field." 
         S ^DD("IX",DA,1)="I $T(SSET^MPIFDEL)'="""",$E(X2(1),1,5)=""00000"" D S
 SET^MPIFDEL(DA,X2(1))" 
         S ^DD("IX",DA,2)="Q" 
         S ^DD("IX",DA,11.1,0)="^.114IA^1^1" 
         S ^DD("IX",DA,11.1,1,0)="1^F^2^.09^^^F" 
         S ^DD("IX",DA,11.1,"B",1,1)="" 
         S ^DD("IX",DA,11.1,"BB",1,1)="" 
         S ^DD("IX","IX","ATSSN",DA)="" 
         S ^DD("IX","BB",2,"ATSSN",DA)="" 
         S ^DD("IX","B",2,DA)="" 
         S ^DD("IX","AC",2,DA)="" 
         S ^DD("IX","F",2,.09,DA,1)="" 
 GENERAL DESCRIPTION:   Registration is requesting to export a new cross
 reference to the .01 and .09 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 and .09 of the Patient file (#2) is has changes in test in the
 field for the Name Standardization patch which is on indefinate hold.  
  STATUS: Retired
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
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: 1
  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 
 GENERAL DESCRIPTION:   
 ************************************************************************
 The Library package was decommissioned with LBR*2.5*15.  This ICR was retired
 with the release of the Library patch.  
 ************************************************************************
  STATUS: Retired
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
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
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: 3322                            IA #: 3322
  DATE CREATED: MAR 10, 2005
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Other                           NAME: RADIOLOGY RTNS 3322
 GENERAL DESCRIPTION:   Radiology gives Imaging permission to copy routines
 associated with APIs used by Imaging to update imaging pointers and delete
 image pointers from the Radiology Report file. These routines are downloaded
 unto Imaging gateways.  The routines are not renamed nor modified on the
 gateways.  
  
 This IA will also request the following be provided on any future patches to
 these routines.  This will inform Imaging users on the procedures to follow
 for downloading the Imaging routines on the gateways.  
  
 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." 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Imaging will download the following routines on their
 satellite gateways.  Imaging uses these routines during the Image capture
 process and for deleting the Image pointers during a roll back process, when
 image acquisition encounter a problem.  
  
 Routines: RARIC, RARTE2, RAUTL, RAULT1, RAUTL2, RAUTL20, RAUTL3, RAUTL5, 
 RAXREF, RARIC1 

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
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
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
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
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
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
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
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
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
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
KEYWORDS: PXRMRPCD
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   The ICR was created specifically for the usage within
 CPRS GUI, but OE/RR was never added as a subscriber. This RPC usage is not new
 with OR*3.0*508, but rather found during ICR review of the OR CPRS GUI CHART 
 context option.  

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
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

NUMBER: 3334                            IA #: 3334
  DATE CREATED: MAR 10, 2005            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Other
  NAME: DBIA 3334  Imaging download of XUSRB1
 GENERAL DESCRIPTION:   Kernel developers allow Imaging to dowload the XUSRB1,
 XUMF333, and XULFDT routines onto satellite DICOM gateways. The routines are
 not renamed nor modified on the gateways.  Imaging is using supported APIs
 from these routines. The Imaging DICOM workstations do not have KERNEL
 installed, it has Micronetic M and a limited translation table to the hospital
 datasets.  
  
 This IA will also request the following be provided on any future patches to
 these routines.  This will inform Imaging users on the procedures to follow
 for downloading the Imaging routines on the gateways.  
  
    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." 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Imaging will download load XUSRB1, XUMF333, and XLFDT
 routines onto satellite DICOM gateways. The routines are not renamed nor
 modified on gateways.  Imaging uses the XUSRB1 routine in the supported api
 calls to encrypt and decrypt passwords. The NOW^XLFDT api is used to set the 
 current time to a variable. Routine $$SCN^XUMF333 is used in the .01 field
 screening of the Institution file.  
  
  The process on these gateway are limited to processing images and sending 
 information to acquisition devices all done in an automated process that does
 not require user interaction other than to start or stop the process.  
  These gateways only have Imaging M applications and no other VistA 
 Application is present. The gateways are in service 24hrs/7days.  

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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   OneVA Pharmacy project requested to added Outpatient
 Pharmacy as a subscriber to access the Domain (#.03) field.  

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
FIELD NUMBER: 90.1                      FIELD NAME: SUSPENSION TYPE
  LOCATION: 1;12                        ACCESS: 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
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: NOV 09, 2021

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
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 3338                            IA #: 3338
  DATE CREATED: MAR 10, 2005            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Other
  NAME: DBIA 3338 - Imaging & VADPT routines
 GENERAL DESCRIPTION:   Registration gives permission to VistA Imaging for
 downloading VADPT* routines. Imaging is executing supported calls to
 DEM^VADPT, INPT^VADPT and ADD^VADPT on satellite PC that have Micronetic M
 installed.  
  
 In addition, Imaging is requesting that any future patches to these routines
 will include a message informing Vista Imaging users to update their Imaging
 gateways.  A possible example follows.  
  
 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." 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Imaging will download the following routines onto
 Imaging DICOM gateways.  Routines:  VADPT, VADPT0 VADPT1, VAPT2, VADPT3,
 VADPT30, VADPT31, VADPT32, VADPT4, VADPT5, VADPT6, VADPT60, VADPT61, and
 VADPT62.  These routines are not renamed nor modified on the gateways. 
 Imaging uses supported calls to ADD^VADPT, INPT^VADPT and DEM^VADPT to get the
 most current information from the main hospital database.   The appropriate
 hospital's database globals are translated to the gateway.  
  
 The process on these gateway are limited to processing images and sending 
 information to image acquisition devices all done in an automated process that
 does not require user interaction other than to start or stop the process. 
 These gateways only have Imaging M applications and no other VistA Application
 is present. The gateways are in service 24hrs/7days.  

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
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 
  DATE ACTIVATED: DEC 11, 2008

NUMBER: 3340                            IA #: 3340
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: MAR 09, 2001            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: DBIA 3340 - Imaging & file 2 xreferences
  ID: DPT(
GLOBAL REFERENCE: DPT(DO,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1
 FIELD DESCRIPTION:   Patient's name 
FIELD NUMBER: .03                       FIELD NAME: DATE OF BIRTH
  LOCATION: 0;3
 FIELD DESCRIPTION:   Patient's date of birth 
FIELD NUMBER: .09                       FIELD NAME: SOCIAL SECURITY NUMBER
  LOCATION: 0;9
 FIELD DESCRIPTION:   Patient's social security number.  
 GENERAL DESCRIPTION:   Registration gives VistA Imaging permission to create a
 cross reference on the following fields: .01 (NAME), .03 (DATE OF BIRTH), and
 .09 (SOCIAL SECURITY NUMBER).  The cross reference created will not add to the
 patient file global growth but execute a routine to create an HL7 message
 during the initial entry into these field values or the editing of the field 
 values. 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Vista Imaging sets cross refencences on fields: .01
 (NAME), .03 (DATE OF BIRTH) and .09 (SOCIAL SECURITY NUMBER).  The cross
 reference during the SET command is SET^MAGDHLE and during the KILL command is
 KIL^MAGDHLE. 
  
 The SET^MAGDHLE routine will create a message in HL7 format for newly created
 entries or on edited entries. The KIL^MAGDHLE routine will just quit.  
  
 The setting of these cross references are set by an IRM person at the site 
 that is installing Imaging but only if the site has a commercial PAC system. 
 The information is only requested by the commercial PAC system to update their
 local database. Instruction on setting this cross reference is located in the
 VistA Imaging DICOM Installation manual.  
  
 Imaging requests the site to set the cross reference number to 2005, and the
 index to be MAGAP1 for .01 field, MAGAP3 for .03 field and MAGAPI9 for .09
 field.  Everything is set to the Imaging number space or namepace.  
  
 Example of the cross reference follows.  
  
  Global ^DD(2,.01,1,2005 
  ^DD(2,.01,1,2005,0) = 2^MAGAP1^MUMPS 
  ^DD(2,.01,1,2005,1) = D SET^MAGDHLE 
  ^DD(2,.01,1,2005,2) = D KIL^MAGDHLE 
  ^DD(2,.01,1,2005,"DT") = 2970723 
  Global ^DD(2,.03,1,2005 
         DD(2,.03,1,2005 
  ^DD(2,.03,1,2005,0) = 2^MAGAP3^MUMPS 
  ^DD(2,.03,1,2005,1) = D SET^MAGDHLE 
  ^DD(2,.03,1,2005,2) = D KIL^MAGDHLE 
  ^DD(2,.03,1,2005,"DT") = 2970723 
  Global ^DD(2,.09,1,2005 
         DD(2,.09,1,2005 
  ^DD(2,.09,1,2005,0) = 2^MAGAP9^MUMPS 
  ^DD(2,.09,1,2005,1) = D SET^MAGDHLE 
  ^DD(2,.09,1,2005,2) = D KIL^MAGDHLE 
  ^DD(2,.09,1,2005,"DT") = 2970723 

NUMBER: 3341                            IA #: 3341
  FILE NUMBER: 3.8                      GLOBAL ROOT: XMB
  DATE CREATED: MAR 26, 2001            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: DBIA3341
  ID: XMB
GLOBAL REFERENCE: XMB(3.8,
FIELD NUMBER: 2                         FIELD NAME: MEMBER
  LOCATION: XMB(3.8,D0,1,0              ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   Add POSTMASTER as member to MAIL GROUP "YS GAF
 TRANSMISSION ACK", if no member(s) exist(s).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas
 SUBSCRIBING DETAILS:   Mental Health requests a one time agreement to place
 POSTMASTER as a member of Mail Group 'YS GAF TRANSMISSION ACK', if no members
 exist.  

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
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
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
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.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
 HMP DG UPDATES protocol has been added to the DG FIELD MONITOR protocol by HMP
 v.2.0 to trigger unsolicited patient updates from VistA to JDS when fields
 monitored by this protocol are updated.  

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
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
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
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
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: 3349                            IA #: 3349
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: MAR 28, 2001            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  NAME: DBIA3349                        ID: PSRX(
 GENERAL DESCRIPTION:   Integrated Billing has permission to access the
 following fields on the PRESCRIPTION file (#52): 
  
   GLOBAL REFERENCE: 
  
    ^PSRX(D0,0) 
  
      .01   RX #                         0;1     Direct Global Read 
        6   DRUG                         0;6     Direct Global Read 
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed

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
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
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 

NUMBER: 3352                            IA #: 3352
  DATE CREATED: APR 05, 2001            CUSTODIAL PACKAGE: 1
  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
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

NUMBER: 3354                            IA #: 3354
  DATE CREATED: APR 12, 2001            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: XUMFP XUMFI
  NAME: Master File Server - IFR project
  ID: XUMFP XUMFI
 GENERAL DESCRIPTION:   There are 2 API's used by the Master File Server
 implemented by the Institution File Redesign (IFR) project -- XU*8.0*126.  
  
 MAIN^XUMFP sets up required parameters, and MAIN^XUMFI builds and sends the 
 HL7 message.  
  STATUS: Withdrawn
KEYWORDS: INSTITUTION
KEYWORDS: MASTER FILE
COMPONENT/ENTRY POINT: MAIN(IFN,IEN,TYPE,PARAM,ERROR)
 COMPONENT DESCRIPTION:   These APIs set up required parameters and build/send
 an HL7 message.  This is the Master File Server.  
  
 INPUT 
 -----
  
 IFN     Internal File Number IEN     Internal Entry Number TYPE    Message
 type 
  
 INPUT/OUTPUT 
 ------------
  
 PARAM   Parameter array 
  
 OUTPUT 
 ------
  
 ERROR   Error flag 

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
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
KEYWORDS: FIELD
KEYWORDS: MONITOR
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
SUBSCRIBING PACKAGE: WOMEN'S HEALTH

NUMBER: 3357                            IA #: 3357
  GLOBAL ROOT: DD(                      DATE CREATED: APR 16, 2001
  CUSTODIAL PACKAGE: 1                  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
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,
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: CLINICALLY INDICATED DATE
  LOCATION: 0;24                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the date by which it is clinically appropriate to
 complete the consult. GMRC*3.0*81 released on 3/8/16 changed the field name
 from Earliest Date to Clinically Indicated Date.  
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
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 Component.  
  DATE ACTIVATED: JAN 21, 2009

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
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.  

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
KEYWORDS: SURGERY
KEYWORDS: OPERATING ROOM
SUBSCRIBING PACKAGE: IFCAP              ISC: Washington/Silver Spring
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS

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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
 Effective with HMP*2.0*2 
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   CPRS approved adding Dental as a subscriber for Dental
 Record Manager to this ICR on 8/11/2009 to document existing references. 
 However the update was not made to the ICR until 2/9/18.  
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/16/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace.
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes 
 required RPCs. ORWU DT is one of the Remote Procedures included in the CRMS
 VAHC Option.  The Remote Application uses Data Access Services/National Health
 Information Network (DAS/NHIN) as the middleware to interface with VistA.  

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: 3365                            IA #: 3365
  DATE CREATED: MAR 18, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: ORQQPL PROBLEM LIST             REMOTE PROCEDURE: ORQQPL PROBLEM LIST
 GENERAL DESCRIPTION:   Parameters: 
     
 Patient DFN - DFN of patient from VistA 
     
 Context - The status of problems to return, passed as a single letter: 
 (A)ctive, (I)nactive, (B)oth, (R)emoved.  If null, Active problems will be
 returned.  
  
 Data is returned in ROOT.  ROOT(0) is the number of items returned.  
 Subsequent entries in ROOT are the problems found along with other 
 information.  
  
  
 ROOT(#)=1 ifn ^ 2 status ^ 3 description ^ 4 ICD code ^ 5 onset date ^ 6 last
 modified date ^ 7 Service Connected ("SC","NSC",or "") ^ 8 Special Exposures ^
 9 Condition (T)ranscribed or (P)ermanent ^ 10 Location ^ 11 Location Type ^ 12
 Provider (DFN;NAME) ^ 13 Service ^ 14 Priority ^ 15 Has Comment ^ 16 Date
 Recorded ^ 17 SC Condition ^ 18 Inactive (set to # if the ICD code is
 inactive) ^ 19 ICD Long Description (for problems with ICD codes only) ^ 20
 ICD Coding System Abbreviation (ICD or 10D) 
  
 Sample return array 
  
 ROOT(0)=2 
  
 ROOT(1)="638^A^Hypertension (ICD-9-CM 401.9)^401.9^3050407^3070410^NSC 
 ^^^^^10000000031;CPRSPROVIDER,FIFTY^1018;MEDICAL^C^0^3070410^NSC^^ UNSPECIFIED
 ESSENTIAL HYPERTENSION^ICD"                               
  
 ROOT(2)="1035^A^CAD - Coronary Artery Disease (SCT 53741008)^I25.10^ 
 3170921^3170921^NSC^^P^^^10000000424;CPRSPROVIDER,ONE^^A^1^3170921^NSC ^^^10D" 
  STATUS: Active
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   ADDED 4/21/2011 
  DATE ACTIVATED: FEB 13, 2018

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)

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)

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
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
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
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: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSSUTLA1                     NAME: PSSUTLA1
  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.  
  
 Pharmacy Data Management also returns the Computerized Patient Record System
 (CPRS) Order Number when a Pharmacy Order Number is passed into the PLACER
 component.  
  
 Pharmacy Data Management also returns the most appropriate Order Location when
 a Pharmacy Order Number is passed into the LOC component.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  
COMPONENT/ENTRY POINT: $$PLACER(PSOPDFN,PSOPIEN)
 COMPONENT DESCRIPTION:   This component returns the CPRS Order Number when a
 Pharmacy Order Number is passed in.  
VARIABLES: PSOPDFN                      TYPE: Input
 VARIABLES DESCRIPTION:   This represents the Internal Entry Number from the
 PATIENT File (#2).  
VARIABLES: PSOPIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   This represents the Pharmacy Order number, in the
 form of order number followed by the one character uppercase file indicator,
 as follows: 
  
 ###P - NON-VERIFIED ORDERS File (#53.1), ###U - UNIT DOSE Subfile (#55.06) of
 PHARMACY PATIENT File (#55), ###I - IV Subfile (#55.01) of the PHARMACY
 PATIENT File (#55), ###N - NON-VA MEDS Subfile (#55.05) of the PHARMACY
 PATIENT File (#55), ###S - PENDING OUTPATIENT ORDERS File (#52.41), ###R -
 PRESCRIPTION File (#52) 
  
 For the 'U', 'I' and 'N' entries above, the number represents the Internal 
 Entry Number from the subfile.  
VARIABLES: $$PLACER                     TYPE: Output
 VARIABLES DESCRIPTION:   This represents the Internal Entry Number from the
 ORDER File (#100). (CPRS Order Number). For the Inpatient files (P,U and I),
 the return value may contain a semicolon followed by another number. In those
 cases, the CPRS Order Number is the first piece, with ";" as the delimiter.  
  
 If for any reason a return value cannot be found, a null value is returned.  
COMPONENT/ENTRY POINT: $$LOC(PSSPDFN,PSSPIEN)
 COMPONENT DESCRIPTION:   This component returns the order location when a
 Pharmacy Order Number is passed in.  
VARIABLES: PSSPDFN                      TYPE: Input
 VARIABLES DESCRIPTION:   This represents the Internal Entry Number from the
 PATIENT File (#2).  
VARIABLES: PSSPIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   This represents the Pharmacy Order number, in the
 form of order number followed by the one character uppercase file indicator,
 as follows: 
                             
 ###P - NON-VERIFIED ORDERS File (#53.1), ###U - UNIT DOSE Subfile (#55.06) of
 PHARMACY PATIENT File (#55), ###I - IV Subfile (#55.01) of the PHARMACY
 PATIENT File (#55), ###N - NON-VA MEDS Subfile (#55.05) of the PHARMACY
 PATIENT File (#55), ###S - PENDING OUTPATIENT ORDERS File (#52.41), ###R -
 PRESCRIPTION File (#52) 
                             
 For the 'U', 'I' and 'N' entries above, the number represents the Internal 
 Entry Number from the subfile.  
VARIABLES: $$LOC                        TYPE: Output
 VARIABLES DESCRIPTION:   This represents the most appropriate order location
 of the pharmacy order. It is a 3 piece return with a '^' delimiter, as
 follows: 
  
 Piece 1 = Internal Entry Number for the entry being returned.  Piece 2 = The
 .01 field of the entry being returned.  Piece 3 = The file number that the
 entry being returned belongs to. It 
           can be one of 4 values: 
  
            4  (INSTITUTION) 
         40.8  (MEDICAL CENTER DIVISION) 
           42  (WARD LOCATION) 
           44  (HOSPITAL LOCATION) 
  
 If for any reason a value cannot be determined for the order, the default 
 institution from the INSTITUTION File (#4) is returned.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIABDX SAVE RPC references PSSUTLA1 routine.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Virtual Patient Record can invoke the PLACER component
 to retrieve the CPRS Order Number, and the LOC component to retrieve the most
 appropriate location for a pharmacy order.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 8/16/23, effective with sustainment patch
 PSO*7*671 (addresses SNOW INC20722800 - Error Running Option Complete Orders
 from OERR), where a need was identified to document subscription for
 historical PSO routines calling the extrinsic function $$OIDEA^PSSUTLA1 in
 order to obtain the DEA for an PHARMACY ORDERABLE ITEM.  
  DATE ACTIVATED: OCT 02, 2019

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
 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
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 <DINUM> 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.  <i.e.> "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

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
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 
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 3/23/20 for the PDMP project.  

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
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Hines
SUBSCRIBING PACKAGE: SURGERY
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   Added 1/31/22, To support attaching a note to a
 patient's Sexual Orientation that has been entered/modified in CPRS through
 Clinical Reminders, effective with patch DG*5.3*1071 the REGISTRATION package
 has created a field identified as NOTE (#.05) in the SEXUAL ORIENTATION 
 (#.025) multiple in the PATIENT (#2) file.  

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).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Hines

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
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
  GOOD ONLY FOR VERSION: Version 1.0
KEYWORDS: PSB
KEYWORDS: BCMA

NUMBER: 3381                            IA #: 3381
  DATE CREATED: MAY 21, 2001            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: Other                           NAME: DBIA3380-B
  ORIGINAL NUMBER: 3380
 GENERAL DESCRIPTION:   Dictates to the client what RPC's a user can execute.  
  STATUS: Pending                       DURATION: Next Version
  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
  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
  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
  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
  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
  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                        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
  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
  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
  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
  GOOD ONLY FOR VERSION: Version 1.0
KEYWORDS: PSB
KEYWORDS: BCMA

NUMBER: 3392                            IA #: 3392
  FILE NUMBER: 8989.51                  GLOBAL ROOT: XTV
  DATE CREATED: MAY 22, 2001            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: File                            ROUTINE: PSBPAR
  NAME: DBIA3390-C                      ORIGINAL NUMBER: 3390
  ID: PSBPAR
 GENERAL DESCRIPTION:   Listing of division specific reasons why a meication is
 given PRN.  Up to 60 reasons are allowed.  
  STATUS: Pending                       DURATION: Next Version
  GOOD ONLY FOR VERSION: Version 1.0
KEYWORDS: PSB
KEYWORDS: BCMA
COMPONENT/ENTRY POINT: EN

NUMBER: 3393                            IA #: 3393
  FILE NUMBER: 8989.51                  GLOBAL ROOT: XTV
  DATE CREATED: MAY 22, 2001            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: File                            ROUTINE: PABPAR
  NAME: DBIA3390-D                      ORIGINAL NUMBER: 3390
  ID: PABPAR
 GENERAL DESCRIPTION:   Listing of division specific reasons why a medication
 is held.  Up to 60 reasons are allowed.  
  STATUS: Pending                       DURATION: Next Version
  GOOD ONLY FOR VERSION: Version 1.0
KEYWORDS: PSB
KEYWORDS: BCMA
COMPONENT/ENTRY POINT: EN

NUMBER: 3394                            IA #: 3394
  FILE NUMBER: 8989.51                  GLOBAL ROOT: XTV
  DATE CREATED: MAY 22, 2001            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: File                            ROUTINE: PSBPAR
  NAME: DBIA3390-E                      ORIGINAL NUMBER: 3390
  ID: PSBPAR
 GENERAL DESCRIPTION:   Listing of division specific reasons why a medication
 is refused.  Up to 60 reasons are allowed.  
  STATUS: Pending                       DURATION: Next Version
  GOOD ONLY FOR VERSION: Version 1.0
KEYWORDS: PSB
KEYWORDS: BCMA
COMPONENT/ENTRY POINT: EN

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
  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
  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
KEYWORDS: MCARPS2
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Hines

NUMBER: 3398                            IA #: 3398
  DATE CREATED: APR 21, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: SCMCUT
  NAME: ROUTINE SCMCUT                  ID: SCMCUT
 GENERAL DESCRIPTION:   In support of the Smart Card initiative, Registration
 needs to use routine SCMCUT and the APIs in the routine to ensure that server
 and client software running on both the local site and the remote site can run 
 together.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CLNLST
 COMPONENT DESCRIPTION:   API returns a list of clients that can be run with a
 specific server version.  
VARIABLES: SER                          TYPE: Input
 VARIABLES DESCRIPTION:   Version of the server 
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   Array root that for the list 
VARIABLES: ACT                          TYPE: Input
 VARIABLES DESCRIPTION:   1 - return only active clients 0 - return all clients 
COMPONENT/ENTRY POINT: ACTCLT
 COMPONENT DESCRIPTION:   Function returns the status of a client version.  The
 status indicates whether or not the client is active.  
VARIABLES: CLT                          TYPE: Input
 VARIABLES DESCRIPTION:   This variable is the client version 
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   1 - Active 0 - Not Active -1^Error message 
COMPONENT/ENTRY POINT: ACTSER
 COMPONENT DESCRIPTION:   Returns the status of a server version 
VARIABLES: SER                          TYPE: Input
 VARIABLES DESCRIPTION:   This variable holds the server version 
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   Array root for the results.  1 - success 0 - none
 found 
COMPONENT/ENTRY POINT: UPCLNLST
 COMPONENT DESCRIPTION:   updates the client/server pair, if indicated, in
 files 404.45 and 404.46 
VARIABLES: SCX                          TYPE: Input
 VARIABLES DESCRIPTION:   string with input values SERVER PATCH^CLIENT
 VERSION^ENABLE OVERRIDE (1=BYPASS, 0=NO (DEFAULT))^ACTIVE SERVER
 (1=YES(DEFAULT),0=NO)^ACTIVE CLIENT(1=YES(DEFAULT),0=NO) the first two pieces
 are required 
VARIABLES: SCRESULT                     TYPE: Output
 VARIABLES DESCRIPTION:   1 - success 0 - failure/not allowed 
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany
 SUBSCRIBING DETAILS:   Registration will use these APIs for the Network Data
 Retrieval functionality that is part of the Smart Card initiative.  

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
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
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
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

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

NUMBER: 3404                            IA #: 3404
  FILE NUMBER: .11                      GLOBAL ROOT: DD(
  DATE CREATED: JUN 01, 2001            CUSTODIAL PACKAGE: 1
  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
KEYWORDS: UPDATE DIE
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 3405                            IA #: 3405
  DATE CREATED: JUN 01, 2001            CUSTODIAL PACKAGE: 1
  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
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
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 3407                            IA #: 3407
  FILE NUMBER: 8989.51                  GLOBAL ROOT: XTV(8989.51,
  DATE CREATED: JUN 05, 2001            CUSTODIAL PACKAGE: TOOLKIT
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            NAME: DEFINITIONS AND ENTITIES
  ID: XTV(8989.51,
GLOBAL REFERENCE: XTV(8989.51,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 30                        FIELD NAME: ALLOWABLE ENTITIES
  LOCATION: 30;0                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Multiple 
GLOBAL REFERENCE: XTV(8989.51,D1,30,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PRECEDENCE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ENTITY FILE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: GMTSXAW
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Health Summary needs to lookup and retrieve the name of
 a parameter definition and it's associated allowalble entities (precedence and 
 entity).  These definitions and entites are used to produce a combined listing
 of entities and parameters as specified by the user.  All access is Read
 w/Fileman.  

NUMBER: 3408                            IA #: 3408
  FILE NUMBER: 8989.518                 GLOBAL ROOT: XTV(8989.518,
  DATE CREATED: JUN 05, 2001            CUSTODIAL PACKAGE: TOOLKIT
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PARAMETER ENTITY                ID: XTV(8989.518,
GLOBAL REFERENCE: XTV(8989.518,D0,0)
FIELD NUMBER: .001                      FIELD NAME: FILE NUMBER
  ACCESS: Read w/Fileman
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PREFIX
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: MIXED CASED NAME
  LOCATION: 0;3                         ACCESS: Read w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMTSXAW
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Health Summary needs to preform a lookup in the
 Parameter Entity file and retrieve the file number, name, prefix and mixed
 case name of the allowable entity for the user to select from to add to a
 combined parameter list.  All access is Read w/Fileman.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 5/17/24 to document OE/RR's historical read
 access w/Fileman to the prefix field which is used to identify the identity
 type in the Parameter Entity file. Documentation of the historical use is
 effective with patch OR*3*610.  
  DATE ACTIVATED: JUN 30, 2001

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
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.  

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
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.  
  STATUS: Active                        EXPIRATION DATE: JAN 01, 2002
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
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: 3413                            IA #: 3413
  DATE CREATED: JUN 25, 2001            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: DGQESC5
  NAME: Download VIC Data               ID: DGQESC5
 GENERAL DESCRIPTION:   The Registration package needs to be able to download
 VIC data during the GUI Registration process.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Patient file IEN (file #2).  
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 3414                            IA #: 3414
  DATE CREATED: JUN 25, 2001            CUSTODIAL PACKAGE: RECORD TRACKING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: RTQ2
  NAME: Request Record                  ID: RTQ2
 GENERAL DESCRIPTION:   The Registration package needs to be able to request
 records (and print bar code labels) while Registering a Patient.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DQ
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Patient file IEN (file #2).  
VARIABLES: SDTTM                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the date/time of NOW, derived from NOW^%DTC.  
VARIABLES: SDSC                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the clinic IEN.  
VARIABLES: SDPL                         TYPE: Input
 VARIABLES DESCRIPTION:   SDPL to be set to zero.  
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
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
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
KEYWORDS: GMTSRAE
KEYWORDS: DSSV
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.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 1/20/23, effective with DSSV 1.1 DSS Class 3
 product. Document Only.  

NUMBER: 3418                            IA #: 3418
  FILE NUMBER: 63                       GLOBAL ROOT: LR(
  DATE CREATED: JUL 15, 2001            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: LRBLAPI
  NAME: DBIA3418                        ID: LRBLAPI
GLOBAL REFERENCE: LR(IEN,0
FIELD NUMBER: .05                       FIELD NAME: ABO GROUP
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: RH TYPE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This API retrieves and returns data from the ABO GROUP
 field #.05 and RH TYPE field #.06 in the Lab Data file #63 for a given patient
 if available.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: BLOOD BANK
COMPONENT/ENTRY POINT: ABORH
 COMPONENT DESCRIPTION:   Entry point:  $$ABORH^LRBLAPI(DFN) 
    INPUT:  DFN=internal entry number of patient in Patient file #2 
    OUTPUT: ABO^RH 
            where ABO = blood type [A,B,AB,O] or Null if unavailable 
                        or -1 if error 
                  RH  = Rh factor [POS,NEG] or Null if unavailable 
                        or -1 if error 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of patient in the Patient file
 (#2).  
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany
 SUBSCRIBING DETAILS:   Requested by the SmartCard Pilot project.  

NUMBER: 3419                            IA #: 3419
  FILE NUMBER: 2.98                     GLOBAL ROOT: DPT(DFN,'S',
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: TIU use of Appt. Multiple (#2.98)
  ID: DPT(DFN,'S',
GLOBAL REFERENCE: DPT(DFN,'S',IEN
FIELD NUMBER: .01                       FIELD NAME: CLINIC
  ACCESS: Read w/Fileman
FIELD NUMBER: 100                       FIELD NAME: CURRENT STATUS
  ACCESS: Read w/Fileman
FIELD NUMBER: 9.5                       FIELD NAME: APPOINTMENT TYPE
  ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   TIU uses a call to EN^DIQ1 to retrieve fields
 .01;100;9.5 from the Appointment multiple (#2.98) for a Patient.  
  
 TIU loops through the ^DPT(DFN,"S",IEN global to obtain the Appointment 
 multiple IEN for the patient.  
  
 The variable DA is set to DFN and DA(1) is set to IEN before calling EN^DIQ1
 to obtain the field values.  
  
 The information obtained is then displayed to the user in External Format when
 prompting the user to select a Scheduled Visit in TIU.  
  
 This agreement will have to change with the Scheduling Redesign.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

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.  
  
 Registration developers from 2001 determined that VADPT 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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: HEALTH SUMMARY

NUMBER: 3421                            IA #: 3421
  DATE CREATED: JUL 20, 2001            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         ROUTINE: XUMF4
  NAME: IFR MFS and HL7 AC x-ref        ID: XUMF4
 GENERAL DESCRIPTION:   The IFR project performs a clean up of the INSTITUTION
 file #4.  It first queries FORUM using the HL7 package direct connect.  If for
 some reason the connection drops, HL7 may not clean up HLMA("AC","O",link,mid)
 which causes problems with subsequent direct connects to the same link.  
  
 The HL7 team is working on a patch.  In the mean time I'd like to check for 
 this bad x-ref before I try to connect.  This would allow IFR to proceed with
 patch XU*8*206 (the check would be implemented in XU*8*209.) 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUL 20, 2002
KEYWORDS: IFR
KEYWORDS: HL7
KEYWORDS: INSTITUTION
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

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
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
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
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
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

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
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING
  ISC: Albany

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
  GOOD ONLY FOR VERSION: pre-CoreFLS
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Hines

NUMBER: 3428                            IA #: 3428
  FILE NUMBER: 45.84                    GLOBAL ROOT: DGP(45.84
  DATE CREATED: AUG 08, 2001            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA3428
  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 NUMBER: 3                         FIELD NAME: CLOSE OUT BY
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The IEN is checked with a $D.  
 GENERAL DESCRIPTION:   Incomplete Records Tracking is accessing two fields in
 the PTF CLOSE OUT File (#45.84).  CLOSE OUT DATE Field (#2) is a date field
 and CLOSE OUT BY Field (#3) is a pointer to the NEW PERSON File (#200).  Both
 calls use the $DATA function on the zero node to varify that the node exists
 prior to getting the fields.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING

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
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
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING
  ISC: Albany

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
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING
  ISC: Albany

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
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING
  ISC: Albany

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
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING
  ISC: Albany

NUMBER: 3434                            IA #: 3434
  FILE NUMBER: .84                      GLOBAL ROOT: DI(.84
  DATE CREATED: AUG 13, 2001            CUSTODIAL PACKAGE: 1
  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
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
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: Added HAZ effective with PSB*3*131 
     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 
     HAZ - Hazardous Text Field    (effective with PSB*3*131) 
  
 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.  
  DATE ACTIVATED: AUG 17, 2021

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                           STATUS: Active
  DURATION: Till Otherwise Agreed
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^<Explanatory Message>" 
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: 
  
       "<Document IEN>^<Pt. DFN>^<Tab in CPRS Chart>" 
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<IEN of TIU DOCUMENT>" 
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 

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
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
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.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
 This functionality is being released in HMP*2.0*2 

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^<gui tab indicator> 
   
 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 
   <gui tab indicator> is an arbitrarily set constant based on the 
                       document type.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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
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("<namespace>",$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("<namespace>",$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
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) 

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
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#.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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

NUMBER: 3444                            IA #: 3444
  FILE NUMBER: 43                       GLOBAL ROOT: DG(43,
  DATE CREATED: AUG 16, 2001            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  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
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: PROBLEM LIST
 SUBSCRIBING DETAILS:   Added 6/19/18.  

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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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: 1
  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
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: 1
  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
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
  GOOD ONLY FOR VERSION: 1.0
KEYWORDS: BCMA
KEYWORDS: PSB
KEYWORDS: MEDICATION HISTORY
COMPONENT/ENTRY POINT: HISTORY
 COMPONENT DESCRIPTION:   If the calling routine sets ^TMP("PSBMH",$J)="", then
 PSBML will search only for solutions that are marked as pre-mix. The entry is
 not required. If the calling packages wants all solutions to be searched, no
 set is required.  
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
  DATE ACTIVATED: AUG 03, 2015

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,
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
 assessment 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).  
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the patient who has been asked about allergies/ 
 adverse reactions.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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: VISTA DATA EXTRACTION FRAMEWORK
 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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR 
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 8/20/25 effective with Class HS.Local.VA 
 .HC.ServiceBroker.VistA.AdverseReactionTracking as subscriber.The NAME(.01)
 field was also added.  
  DATE ACTIVATED: SEP 30, 2014

NUMBER: 3450                            IA #: 3450
  FILE NUMBER: 120.51                   GLOBAL ROOT: GMRD(120.51,
  DATE CREATED: SEP 11, 2001
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: File                            NAME: VITALS TYPE POINTER
  ID: GMRD(120.51,
GLOBAL REFERENCE: GMRD(120.51,DO,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 FIELD DESCRIPTION:   This field reflects a list of vital signs/physical
 measurement types.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: GMTS
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
 SUBSCRIBING DETAILS:   GMRV VITAL TYPE entries are used as selected items in
 the Selected Vitals Health Summary Component.  Therefore Health Summary needs
 to point to GMRV VITAL TYPE entries.  

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
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.DNS 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.DNS".  The environment check routine will not allow 
  patch RG*1.0*22 to be installed unless the "MAIL.CIO.DNS" 
  entry exists.  Patch RG*1.0*22 is in support of GCPR.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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 NODE 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: NODE 
   INSTITUTION: OFFICE OF INFORMATION SRV CNTR 
   LLP TYPE: TCP                       AUTOSTART: Enabled 
   DOMAIN: MAIL.CIO.DNS         QUEUE SIZE: 10 
   EXCEED RE-TRANSMIT ACTION: restart  TCP/IP ADDRESS: 127.0.0.1 
   TCP/IP PORT: XXXX                   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 'NODE' 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 'NODE'.  This functionality is in support 
  of GCPR.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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
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
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
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
KEYWORDS: PSB
KEYWORDS: BCMA
COMPONENT/ENTRY POINT: HISTORY
 COMPONENT DESCRIPTION:   If the calling routine sets ^TMP("PSBMH",$J)="", then
 PSBML will search only for solutions that are marked as pre-mix. The entry is
 not required. If the calling packages wants all solutions to be searched, no
 set is required.  
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.  
  DATE ACTIVATED: AUG 03, 2015

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
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
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
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
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
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
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
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
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
 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
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

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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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
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.  

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
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.  

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
SUBSCRIBING PACKAGE: SURGERY            ISC: Birmingham

NUMBER: 3476                            IA #: 3476
  DATE CREATED: NOV 05, 2001            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIEZ
  NAME:  DIEZ UNCOMPILE INPUT TEMPLATES/DELETE COMPILED ROUTINES
  ID: DIEZ
 GENERAL DESCRIPTION:   UNC^DIEZ is a silent VA FileMan call that allows the
 deletion of compiled Input Templates and their associated compiled routines.
 The entry point 'UNC' can accept two input parameters: 
  
 DIEZ = The IEN of the input template to uncompile. DIFLAGS = "D" indicates all
 associated compiled routines are to be deleted.  
  
 The variable DIEZ is required; the variable DIFLAGS is optional.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: UNC
KEYWORDS: DIEZ
KEYWORDS: RA ORDERS
COMPONENT/ENTRY POINT: UNC
 COMPONENT DESCRIPTION:   The UNC entry point allows the deletion of the
 targeted compiled input templates and all associated compiled input template
 routines associated with those compiled input templates.  
VARIABLES: DIEZ                         TYPE: Input
 VARIABLES DESCRIPTION:   DIEZ is the Internal Entry Number (IEN) of the
 compiled input template to be deleted.  
VARIABLES: DIFLAGS                      TYPE: Input
 VARIABLES DESCRIPTION:   DIFLAGS, when set to a value of "D", is used to
 indicate that all compiled input template routines for that compiled input
 template are to be deleted.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   VistA Radiology will set the input variable DIEZ to the
 value of the input template to be deleted. VistA Radiology will set the value
 of the second input variable, DIFLAGS, to "D" to delete the associated
 compiled input template routines.  
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   VistA Registration requests permission to un-compile
 input templates using the unsupported DIEZ call UNC^DIEZ(IEN).  The IEN of the
 input template will be determined by the supported call FIND1^DIC.  
  
 EX: IEN=$$FIND1^DIC(.402,"","X","DVBA C ADD 2507 PAT") 

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
GLOBAL REFERENCE: SRF(D0,TIU
FIELD NUMBER: 1000                      FIELD NAME: TIU OPERATIVE SUMMARY
  LOCATION: TIU;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1001                      FIELD NAME: TIU NURSE INTRAOP REPORT
  LOCATION: TIU;2                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1002                      FIELD NAME: TIU PROCEDURE REPORT
  LOCATION: TIU;3                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1003                      FIELD NAME: TIU ANESTHESIA REPORT
  LOCATION: TIU;4                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1004                      FIELD NAME: DICTATED SUMMARY EXPECTED
  LOCATION: TIU;5                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1005                      FIELD NAME: CPT ON NURSE REPORT
  LOCATION: TIU;6                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1006                      FIELD NAME: ICD ON NURSE REPORT
  LOCATION: TIU;7                       ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Read access to selected fields from SURGERY file, #130.
 This Integration Agreement allows direct global read access to determine if
 data does exist in ^SRF(D0,"TIU" SURGERY file. 
 GENERAL DESCRIPTION:   This DBIA documents references from TIU upload routines
 to the SURGERY (#130), for upload of Surgeon's Dictation into the SURGERY
 file.  
  
  Revision History: 
   - 11/12/24 Added Global Reference SRF(D0,"TIU" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: UPLOAD
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Updated 11/12/24 effective with TIU*1.0*369
 ^SRF(D0,"TIU" Global Reference fields 1000-1006 were added to resolve
 duplicate notes being entered into VistA/CPRS from MD Provation (third party
 application) using HL7 messaging.  
  DATE ACTIVATED: NOV 12, 2024

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
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: 3479                            IA #: 3479
  DATE CREATED: APR 21, 2003            CUSTODIAL PACKAGE: RECORD TRACKING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: RTPSET1
  NAME: RECORD TRACKING RTPSET1 FOR GUI REGISTRATION
  ID: RTPSET1
 GENERAL DESCRIPTION:   Registration needs to call RTPSET1 during the GUI
 version of the Register a Patient functionality.  Entry points SAVE and
 restore will save RT namespaced variables into a temporary array and then
 later restore them to their original values.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: GUI REGISTRATION
COMPONENT/ENTRY POINT: SAVE
 COMPONENT DESCRIPTION:   Subroutine saves "RTAPL","RTSYS","RTFR","RTDIV" into
 an array RTNEW().  
VARIABLES: RTAPP                        TYPE: Input
 VARIABLES DESCRIPTION:   The application being used - either MAS or RAD.  
VARIABLES: RTSYS                        TYPE: Input
 VARIABLES DESCRIPTION:   The Record Tracking Application.  
VARIABLES:  
VARIABLES: RTFR                         TYPE: Input
 VARIABLES DESCRIPTION:   Input Device from the Borrower/File Area file
 (#195.9).  
VARIABLES: RTDIV                        TYPE: Input
 VARIABLES DESCRIPTION:   The Borrower/File Area location.  
COMPONENT/ENTRY POINT: RESTORE
 COMPONENT DESCRIPTION:   Restores variables saves into RTNEW in subroutine
 SAVE.  
VARIABLES: RTAPL                        TYPE: Output
 VARIABLES DESCRIPTION:   The application being used - either MAS or RAD.  
VARIABLES: RTSYS                        TYPE: Output
 VARIABLES DESCRIPTION:   The Record Tracking Application.  
VARIABLES: RTFR                         TYPE: Output
 VARIABLES DESCRIPTION:   Input device from the Borrowers/File Area file
 (195.9) 
VARIABLES: RTDIV                        TYPE: Output
 VARIABLES DESCRIPTION:   The Borrower/File Area location.  
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
  DATE ACTIVATED: JUN 04, 2012

NUMBER: 3482                            IA #: 3482
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9
  DATE CREATED: NOV 26, 2001            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA3482                        ID: ICD9
 GENERAL DESCRIPTION:   Whenever the data in file 80 (ICD DIAGNOSIS) changes,
 the subscribing packages need advance notification in case they need to
 prepare a patch to their software product to be released simultaneously with
 the ICD patch.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DENTAL             ISC: Hines

NUMBER: 3483                            IA #: 3483
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT
  DATE CREATED: NOV 26, 2001            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA3483
  ID: ICPT
 GENERAL DESCRIPTION:   Whenever the data in file 81 (CPT) changes, the
 subscribing packages need advance notification in case they need to prepare a
 patch to their software product to be released simultaneously with the ICPT
 patch.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DENTAL             ISC: Hines

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
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
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
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) = <Date/Time Specimen Taken>^<Surgical Path Acc#> 
  ^TMP("LRA",$J,IDT,.1) = "Site/Specimen"^<Report Release Date/Time> 
  ^TMP("LRA",$J,IDT,.1,sub1) = <Specimen ID>.<Body Site>:<Specimen Type> 
  ^TMP("LRA",$J,IDT,1.4,sub2) = <Surgical Pathology Diagnosis text> 
  ^TMP("LRA",$J,IDT,"facility") = <Facility> 
  
 1.1.1.1.1       Cytopathology Data: 
  ^TMP("LRCY",$J,IDT,0) = <Date/Time Specimen taken>^<Cytopath Acc#> 
  ^TMP("LRCY",$J,IDT,1) = "Site/Specimen"^<Report Release Date/Time> 
  ^TMP("LRCY",$J,IDT,1,sub1) = <Specimen ID>.<Body Site>:<Specimen Type> 
  ^TMP("LRCY",$J,IDT,"NDX",sub2) = <Cytology Diagnosis> 
  ^TMP("LRCY",$J,IDT,"facility") = <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)= <exam date> ^ <procedure> ^ <exam status> ^
 <report status> ^ <prim interpreting resident> ^ <primary interpreting staff>
 ^ <CPT code> ^ <technologist> ^ <case number> 
  
 ^TMP("RAE",$J, GMTSIDT,sub1,"facility") = <Facility> 
  
 ^TMP("RAE",$J, GMTSIDT,sub1,"H",sub2) = <History text> 
  
 ^TMP("RAE",$J, GMTSIDT,sub1,"R",sub2) = report text line, where report text is
 formatted as follows: 
  
 <Test Name> 
  
  Exm Date: <Exam date> 
  Req Phys: <Primary interpreting staff>         Pat Loc: 
                                                         Img Loc: <Location> 
                                                         Service: 
  
 Exam: <Fill id> <Procedure>     CPT: <CPT code> 
  
 Report Status: <report status>  Date verified: <verification date> 
  
  Report: 
  Reason for order: 
         <order comments> Order Comment: 
         <result text> 
  
  
  
 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: 
  
 <Patient Name>    <Social Security Number>             DOB: <Date of Birth> 
  
 <Facility Name> 
  <Movement Date/Time>  <Transaction Type>  <Type of Movement> 
    Provider/Specialty: <Provider/Specialty>  <Ward Specialty> 
        Attending/Ward: <Provider/Attending>  <Ward> 
          Admitting DX: <Admitting Diagnosis> 
           Bed Section: <Bed Section>     LOS: <Length of Stay> 
                  DXLS: <DXLS> 
                ICD DX: <ICD DX> 
     Disposition Place: <Disposition Place> 
   
   Admitting Procedures: 
                <Adm Procedure date/time> <Admitting Procedure> 
   
   Procedure  <Procedure date/time> <Procedure> 
   Procedure  <Procedure date/time> <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     
  
  <Enc Date>     <Facility Name> <Service Code> <Service Text> 
  
  Encounter Provider ID: <Provider ID> 
               PCM Code: <PCM Code> 
              Diagnosis: <ICD9 Code> <Diagnosis Text> 
                             ...
                             <ICD9 Code> <Diagnosis Text> 
              Procedure: <MEPRS code> <Procedure Description> 
                             ... 
                             <MEPRS code> <Procedure Description> 
                E and M: <E and M code> <E and M Description> 
  
 << 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 

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

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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL

NUMBER: 3490                            IA #: 3490
  FILE NUMBER: 43                       GLOBAL ROOT: DG(43
  DATE CREATED: DEC 04, 2001            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: DBIA3490                        ID: DG(43
GLOBAL REFERENCE: DG(43,D0,BT
FIELD NUMBER: 720                       FIELD NAME: BT CERTIFYING OFFICIAL
  LOCATION: BT;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 721                       FIELD NAME: BT OTHER EXPENSES ASKED
  LOCATION: BT;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 722                       FIELD NAME: USE TEMPORARY ADDRESS
  LOCATION: BT;3                        ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Beneficiary Travel has retained full authority for the
 "BT" node and its fields located and maintained in the MAS PARAMETERS (#43)
 File.  This includes development of the data dictionary (DD) for these fields,
 as well as responsiblility for data entry into and data retriveval from these
 fields.  
  
 This agreement is a "delegation of custody" of these fields from Resistration
 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.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
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
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
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
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
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
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
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
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

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 <return> or <enter> key to
 continue.  
  STATUS: Active
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
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
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
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
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
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

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
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 - READ ONLY   ID: RA(79.2,
GLOBAL REFERENCE: RA(79.2,D0,0
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.  
FIELD NUMBER: 5                         FIELD NAME: RADIOPHARMACEUTICALS USED
  LOCATION: 0;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RA(79.2,'C',ABBREVIATION,DA
 GLOBAL DESCRIPTION:   Allows for the look-up of an imaging location by
 abbreviation.  
GLOBAL REFERENCE: RA(79.2,'B',TYPE OF IMAGING,DA
 GLOBAL DESCRIPTION:   Allows for the look-up by TYPE OF IMAGING 
GLOBAL REFERENCE: RA(79.2,'AC'
 GENERAL DESCRIPTION:   Radiology gives Imaging permission to read file 79.2,
 IMAGING TYPE. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ISI
KEYWORDS: ISI*1.1*110 DFN
KEYWORDS: VistARad COTS
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 ***************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ***************************************************
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Patch MECH*1.0*1 processes HL7 new-order messages about
 imaging studies performed in the community but not entered through VistA.  In
 order to do this, it needs to invoke Radiology routines and make FileMan calls
 to add entries to the RAD/NUC MED PATIENT File (#70) (for existing VA
 patients), the ORDER File (#100), and the RAD/NUC MED ORDERS File (#75.1). The
 patch then creates an HL7 order-update message that transmits the study's 
 accession number to the sender. ADDED 3/2O/2022, effective with MECH*1.0*1 
 Medicom Class 3 product Document Only 
SUBSCRIBING PACKAGE: ISI IMAGING
 SUBSCRIBING DETAILS:   Added 1/10/23, effective with ISI*1.1*110 
SUBSCRIBING PACKAGE: DSS OTM RADIOLOGY
 SUBSCRIBING DETAILS:   Added 7/2/25 effective with patch DSSU*1.1*P6 The DSS
 OTM RADIOLOGY package provides a user-friendly methodology as part of the VA
 initiative to enhance its digital transformation efforts.  The DSS OTM
 RADIOLOGY package offers clear visibility into the status of exam and allows
 Protocolling of exams.  This package also gives quick access to many VistA
 functions from the RADIOLOGY/NUCLEAR MEDICING package.  

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
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
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
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
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(
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 DESCRIPTION:   (#79) PRINCIPAL DIAGNOSIS [10P:80] from DD 11/24/17 
FIELD NUMBER: 79.16                     FIELD NAME: ICD2
  LOCATION: 70;16                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   (#79.16) SECONDARY DIAGNOSIS 1 [16P:80] from DD 11/24/17 
FIELD NUMBER: 79.17                     FIELD NAME: ICD3
  LOCATION: 70;17                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   (#79.17) SECONDARY DIAGNOSIS 2 [17P:80] from DD 11/24/17 
FIELD NUMBER: 79.18                     FIELD NAME: ICD4
  LOCATION: 70;18                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   (#79.18) SECONDARY DIAGNOSIS 3 [18P:80] from DD 11/24/17 
FIELD NUMBER: 79.19                     FIELD NAME: ICD5
  LOCATION: 70;19                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   (#79.19) SECONDARY DIAGNOSIS 4 [19P:80] from DD 11/24/17 
FIELD NUMBER: 79.201                    FIELD NAME: ICD6
  LOCATION: 70;20                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   (#79.201) SECONDARY DIAGNOSIS 5 [20P:80] from DD 11/24/17 
FIELD NUMBER: 79.21                     FIELD NAME: ICD7
  LOCATION: 70;21                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   (#79.21) SECONDARY DIAGNOSIS 6 [21P:80] from DD 11/24/17 
FIELD NUMBER: 79.22                     FIELD NAME: ICD8
  LOCATION: 70;22                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   (#79.22) SECONDARY DIAGNOSIS 7 [22P:80] from DD 11/24/17 
FIELD NUMBER: 79.23                     FIELD NAME: ICD9
  LOCATION: 70;23                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   (#79.23) SECONDARY DIAGNOSIS 8 [23P:80] from DD 11/24/17 
FIELD NUMBER: 79.24                     FIELD NAME: ICD10
  LOCATION: 70;24                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   (#79.24) SECONDARY DIAGNOSIS 9 [24P:80] from DD 11/24/17 
FIELD NUMBER: 80                        FIELD NAME: PRINCIPAL DIAGNOSIS
  LOCATION: 70;11                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   (#80) PRINCIPAL DIAGNOSIS pre 1986 [11P:80] from DD
 11/24/17 
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
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham

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
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham
SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   Added 11/30/22, effective with DSSV*1.1. Document only
 Class 2 
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   Added 4/12/24 effective with DENT*1.2*91 to determine
 visit dates for dental historical transactions.  

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
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: Retired
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: Retired
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: Retired
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: Retired
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: Retired
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
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(<field #>)="" 
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",<IDX field data>,<inverse date>,<TIU IEN>) 
  
 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(<field #>)="" 
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",<IDX field data>,<inverse date>,<TIU IEN>) 
  
 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
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
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 = <User name> 
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
 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
COMPONENT/ENTRY POINT: $$OS
 COMPONENT DESCRIPTION:   
         Usage:  I ^%ZOSF("OS")["OpenM" S Y=$$OS^%ZOSV 
  DATE ACTIVATED: JUL 06, 2009

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
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
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
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.  

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
COMPONENT/ENTRY POINT: SETUP
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX

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
COMPONENT/ENTRY POINT: CHECK
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX

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
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

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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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
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: 1
  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     <<Field 9 greater than
 20 ^DIBT(1228,"DC",2)=6^["E"    <<Field 6 contains an "E" 
GLOBAL REFERENCE: DIBT(D0,'DL'
 GLOBAL DESCRIPTION:   The node that contain the search logic responded by the
 user to the 'IF:/OR' prompts, not in legible format.   Example: 
 ^DIBT(1228,"DL")=1 ^DIBT(1228,"DL",0)=^1^2^         << A&B) 
GLOBAL REFERENCE: DIBT(D0,'O'
 GLOBAL DESCRIPTION:   The node that contains the search logic in legible
 format. Example:           DIBT(1228,"O",1,0)=NUMBER OF IMAGES GREATER THAN 20 
 DIBT(1228,"O",2,0)=   and PROCEDURE CONTAINS "E" 
 GENERAL DESCRIPTION:   FileMan gives Imaging permission to read the DIBT
 global.  The Fileman team reserves the right to make changes allowing Imaging
 developers 3 to 6 months notice prior modifications.  This request is to read
 the search criteria stored in the DIBT global.  A call to EN^DIS is initiated
 to start the FileMan search logic dialog.  Imaging understands that the nodes
 read from the DIBT global are not documented and may change.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   
  
 Vistarad generates a temporary file containing a "master" list of radiology
 exam records to display on demand to the workstation in response to an RPC
 call.  It is important that the list is delivered to the workstation within
 one to 2 seconds of initiation of the RPC call.  The actual records to be
 displayed for a given list that is requested generally consist of a subset of
 the master list, filtered according to selection criteria defined in a List
 Definition file (#2006.631).  The code that executes this filtering uses
 search logic that has been created by calling EN^DIS, Fileman search logic
 entry function. To accommodate the needs of the filtering program, the
 internal representation of the Fileman search logic that was generated must be
 stored with the List definition, to be re-used whenever the filtered list is
 produced.  
  
 Since the Fileman Search results are stored in ^DIBT, some of the information
 required to implement the above logic must be read from ^DIBT at the time that
 the search logic is defined.  The specific nodes that are read are: 
  
 ^DIBT(IEN,"DC"), ff.  ^DIBT(IEN,"DL"), ff.  ^DIBT(IEN,"O"), ff.  
  
 The code to read the global is the following, where variable DIARI equals the
 IEN for the entry in the SORT TEMPLATE file, and GREF is the global array for
 an Imaging file, 2006.631: S GREF=$NA(^MAG(2006.631,MAGIEN,"DEF")) 
 ...
 ... 
 S GLIN=$NA(^DIBT(DIARI))  ; Copy search logic to 2006.631 "DEF" nodes F
 TNOD=3,4 S FNOD=$P("^^DC^DL",U,TNOD) D . S T="",CT=0 . F  S
 T=$O(@GLIN@(FNOD,T)) Q:T=""  S X=^(T) I X]"" S 
  CT=CT+1,@GREF@(TNOD,CT)=X . S @GREF@(TNOD,0)=CT S T=0 F  S
 T=$O(@GLIN@("O",T)) Q:T=""  S @GREF@(5,T)=^(T,0) Q 
  
  
 Imaging understands that the nodes read from the DIBT global are not 
 documented and may change.  
  
  
 Please note that the variable DIARI is an undocumented output variable from
 the api EN^DIS. A NOIS entry, ISW-0302-20006, has been entered by Imaging
 requesting the FileMan v22 Programmer Manual to be updated to documenting this
 variable.  this variable. 

NUMBER: 3533                            IA #: 3533
  DATE CREATED: FEB 28, 2002            CUSTODIAL PACKAGE: SURGERY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: SROESTV                      NAME: Calls to Routine SROESTV
  ID: SROESTV
 GENERAL DESCRIPTION:   This DBIA documents calls to the routine SROESTV. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LIST(SRG,SRDFN,SRSDT,SREDT,SRMAX,SRLDOC)
 COMPONENT DESCRIPTION:   Lists surgery cases for a patient with their
 associated documents in TIU.  This list is used to provide the tree view in
 CPRS of cases and associated documents.  
VARIABLES: SRDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN in PATIENT file (#2) 
VARIABLES: SRSDT                        TYPE: Used
 VARIABLES DESCRIPTION:   Beginning date of surgery cases to return 
VARIABLES: SREDT                        TYPE: Used
 VARIABLES DESCRIPTION:   Ending date of surgery cases to return 
VARIABLES: SRMAX                        TYPE: Used
 VARIABLES DESCRIPTION:   Maximum number of cases to return in list 
VARIABLES: SRLDOC                       TYPE: Used
 VARIABLES DESCRIPTION:   Flag to list documents (1) or not (0) (Default is 1,
 list documents) 
VARIABLES: SRG                          TYPE: Used
 VARIABLES DESCRIPTION:   Array in which list of cases with documents will be
 returned.  Note: Array is killed at the beginning of the call.  Calling
 application is responsible for killing the array after use.  If SRG is not
 provided, the default is ^TMP("SRLIST",$J).  
  
 Below is the array layout for a case.  
  
 Node             Piece (Delimited by ^) 
 ----------       ---------------------------------
 @SRG@(NUM1)      1  -  IEN in File #130 
                  2  -  Principal Procedure 
                  3  -  Date of Operation (int) 
                  4  -  Surgeon name (int;ext) 
                  5  -  + (if documents present) 
          
 @SRG@(NUM1,NUM2) 1  -  IEN in File #8925 
                  2  -  Document title 
                  3  -  Reference date/time (int) 
                  4  -  Patient name with last 
                        initial/last 4 of PID 
                  5  -  Author (internal;external) 
                  6  -  Hospital location 
                  7  -  Signature status 
                  8  -  Visit data/time 
                  9  -  discharge date/time 
                  10 -  Variable Pointer to Request 
                  11 -  # of associated images 
                  12 -  Subject 
                  13 -  + (if has children) 
                  14 -  IEN of parent document 
COMPONENT/ENTRY POINT: ONE(SRG,SROP)
 COMPONENT DESCRIPTION:   List documents associated with a single case.  
VARIABLES: SROP                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of case in SURGERY file #130 
VARIABLES: SRG                          TYPE: Used
 VARIABLES DESCRIPTION:   Array in which list of cases documents will be
 returned.  Note: Array is killed at the beginning of the call.  Calling
 application is responsible for killing the array after use.  If SRG is not
 provided, the default is SRTIU.  
  
 Below is the array layout for a case.  
  
 Node             Piece (Delimited by ^) 
 ----------       ---------------------------------
 @SRG@(NUM1)      1  -  IEN in File #130 
                  2  -  Principal Procedure 
                  3  -  Date of Operation (int) 
                  4  -  Surgeon name (int;ext) 
                  5  -  + (if documents are present) 
  
 @SRG@(NUM1,NUM2) 1  -  IEN in File #8925 
                  2  -  Document title 
                  3  -  Reference date/time (int) 
                  4  -  Patient name with last 
                        initial/last 4 of PID 
                  5  -  Author (internal;external) 
                  6  -  Hospital location 
                  7  -  Signature status 
                  8       -  Visit data/time 
                  9  -  discharge date/time 
                  10 -  Variable Pointer to Request 
                  11 -  # of associated images 
                  12 -  Subject 
                  13 -  + (if has children) 
                  14 -  IEN of parent document 
COMPONENT/ENTRY POINT: $$NON(SROP)
 COMPONENT DESCRIPTION:   Determine if case is non-OR procedure.  
  
 Returns:  0 - case is not non-OR procedure 
           1 - case is non-OR procedure 
VARIABLES: SROP                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of case in SURGERY file #130 
COMPONENT/ENTRY POINT: $$OPTOP(SROP)
 COMPONENT DESCRIPTION:   Returns parameter value for showing Op-Top on
 signature.  
  
 Returns:  0 - never display Op-Top 
           1 - always display Op-Top 
           2 - ask to display Op-Top 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   NHIN ADDED 2/9/2011 
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA added as the subcriber for VIAB SRGY RPTLIST RPC
 for get surgery report.  

NUMBER: 3534                            IA #: 3534
  GLOBAL ROOT: DD(2                     DATE CREATED: FEB 28, 2002
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Setting DD fields in post-init routine
  ID: DD(2
 GENERAL DESCRIPTION:   An integration agreement is needed for Registration to
 set ^DD nodes for several PATIENT (#2) file fields in the post initialization
 routine DG53244R for patch DG*5.3*244, Patient Name Standardization.  The
 INPUT TRANSFORM (#.5), 'HELP'-PROMPT (#3) and DESCRIPTION (#21) fields for the 
 following PATIENT (#2) file fields and subfields is updated by DG*5.3*244.  
  
 DG*5.3*620 will also set ^DD nodes for the following fields in its post 
 initialization routine DG53620D. This patch will switch the API called from
 the ^DD, $$FORMAT^DPTNAME, to its equivalent in Kernel, $$FORMAT^XLFNAME7.
 Thus the Input transform referred to in patch DG244 is not longer valid.  
  
         NAME (#.01) 
         K-NAME OF PRIMARY NOK (#.211) 
         K2-NAME OF SECONDARY NOK (#.2191) 
         FATHER'S NAME (#.2401) 
         MOTHER'S NAME (#.2402) 
         MOTHER'S MAIDEN NAME (#.2403) 
         E-NAME (#.331) 
         E2-NAME OF SECONDARY CONTACT (#.3311) 
         D-NAME OF DESIGNEE (#.341) 
  
         Subfields: 
  
         NAME (#.01) field in the ALIAS (#2.01) multiple 
         ATTORNEY'S NAME (#30) field in the DISPOSITION LOG-IN DATE/TIME 
         (#2.101) multiple 
  
 Also, the SET and KILL logic will be updated for the name field.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 3535                            IA #: 3535
  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: TIUSRVP                      NAME: TIUSRVP Calls
  ID: TIUSRVP
 GENERAL DESCRIPTION:   Entry points in this routine provide mechanisms for
 creating, updating, deleting and addending TIU records.  Note that users are
 asked to call MAKEADD^TIUSRVP2 and SIGN^TIUSRVP2 when editing or writing new
 code.  This is effective when TIU*1*184 is released. See IA 4795.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MAKE(SUCCESS,DFN,TITLE,VDT,VLOC,VSIT,TIUX,VSTR,SUPPRESS,N
OASF)
 COMPONENT DESCRIPTION:   This entry point allows the creation of TIU DOCUMENT
 records.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This REQUIRED PARAMETER is the pointer to the patient
 file.  
VARIABLES: TITLE                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the pointer to the TIU DOCUMENT DEFINITION
 FILE which identifies the TITLE of the document to be filed.  
VARIABLES: VDT                          TYPE: Used
 VARIABLES DESCRIPTION:   This optional parameter is the Date/time of visit. 
 If the parameter VSIT is present, this will be ignored.  Otherwise, the RPC
 will attempt to generate a match with a visit based on DFN, VDT, and VLOC
 (visit location).  In the event that the RPC cannot generate such a match, a
 new EVENT-type Visit will be created with the current date/time.  
VARIABLES: VLOC                         TYPE: Used
 VARIABLES DESCRIPTION:   This optional parameter is the Location of Visit
 (e.g., Cardiology Clinic).  It is a pointer to Hospital location (File #44).  
VARIABLES: VSIT                         TYPE: Used
 VARIABLES DESCRIPTION:   This is a pointer to the Visit File (#9000010) entry
 for the visit to which the document is to be linked.  
VARIABLES: TIUX                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the input array in which the identifiers of
 the document, as well as its text, are to be stored in the following format: 
   
  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: VSTR                         TYPE: Used
 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: 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: NOASF                        TYPE: Used
 VARIABLES DESCRIPTION:   This parameter can optionally be set to 1 to indicate
 the ASAVE cross-reference in the TIU Document file (#8925) should not be set
 when call is made.  The intent of this cross-reference is for telnet type 
 sessions where a user could be dropped.  The cross-reference is used to 
 provide the user with an easy way to resume editing the TIU Document they were
 working on when they were dropped.  In the Clinical Procedures realm, for
 example, where the stub is created in the 'background' this cross-reference
 should not be set since the user is not interactively involved in the creation
 of the record.  
VARIABLES: SUCCESS                      TYPE: Both
 VARIABLES DESCRIPTION:   If the call is successful, this will be the record
 number (IEN) of the resulting entry in the TIU DOCUMENT FILE (#8925).  In the
 event of a filing error, the first "^"-piece will be zero, and the second
 "^"-piece of this scalar return variable will be a textual message describing
 the nature of the error (e.g., 0^Invalid TITLE Selected.").  
COMPONENT/ENTRY POINT: UPDATE(SUCCESS,TIUDA,TIUX,SUPPRESS)
 COMPONENT DESCRIPTION:   This API updates the record named in the TIUDA
 parameter, with the information contained in the TIUX(Field #) array.  The
 body of the modified TIU document should be passed in the TIUX("TEXT",i,0)
 subscript, where i is the line number (i.e., the "TEXT" node should be ready
 to MERGE with a word processing field).  Any filing errors which may occur
 will be returned in the single valued ERR parameter (which is passed by 
 reference).  
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: TIUX                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the input array which contains the data to be
 filed in the modified document.  It should look something like this: 
   
  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: Used
 VARIABLES DESCRIPTION:   This BOOLEAN Flag is passed in to suppress the call
 to the COMMIT CODE for the TIU DOCUMENT in question (i.e., SUPPRESS=1 ==>
 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 VistA Consult team can verify what happens in
 their test environment. 3.      The VistA Consult 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.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 3/20/24, effective with PSO*7*746, the Outpatient
 Pharmacy Meds by Mail project is calling the UPDATE^TIUSRVP2 component to
 support documenting communications from the VA Outpatient Pharmacies with the 
 community care providers whenever they have a question about an inbound 
 electronic prescription (eRX). This project also requests access to MAKE and
 DELETE components.  

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
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

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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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
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 

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
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
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This API is called by VIAB TIU SECVST RPC. If the
 patient is an inpatient, it updates the SECONDARY VISIT (field #1207) in the
 TIU DOCUMENT (File #8925). 

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
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
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,
FIELD NUMBER: 73                        FIELD NAME: RAD/NUC MED INACTIVE DATE
  LOCATION: RA;3                        ACCESS: Direct Global Read & w/Fileman
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
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 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 05/21/21, ICR was missing from prior OR patches,
 found while reviewing OR*3*498.  
  DATE ACTIVATED: MAR 12, 2002

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
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
  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.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE
 SUBSCRIBING DETAILS:   1/10/22: Patient Representative Decom patch QAC*2.0*25
 has been released on 01/10/2022 with a Compliance date of 2/10/22. Patient
 Representative subscription retired effective with a Compliance date of
 2/10/22.  
  
 Original usage information below: 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
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
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
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
 Effective with HMP*2.0*2 

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
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.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.) 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   SUBSCRIBING PACKAGE: Outpatient Pharmacy 
                          
 Method:  OneVA Pharmacy, as part of Outpatient Pharmacy, would like to use
 ^HLCS(870,"C",site ien) to find the MAILMAN DOMAIN (#.03) and use it to create
 the Fully Qualified Domain Name.  
  
 Details:  The code used by PSO to access the "C" cross-reference is shown
 below.  
  
 Routine PSORWRAP 
  
 FQDN(SITE,IEN4) ; get Fully Qualified Domain Name 
          ;
          I $G(IEN4)="",$G(SITE)="" Q ""  ; Need site # or institution file IEN 
          ;
          I $G(IEN4)="" D  Q:$G(IEN4)="" "" 
          .S IEN4=$$FIND1^DIC(4,,"X",SITE,"D","I 
 $P(^(0),U,11)=""N"",'$P($G(^(99)),U,4)") 
          ;
          N PSOHLNK,RMSDOM 
          S PSOHLNK=$O(^HLCS(870,"C",IEN4,0)) ; get first entry (should only be
 one but you never know) IA#3550 
          Q:'$G(PSOHLNK) "" 
          ;
          S RMSDOM=$$GET1^DIQ(870,PSOHLNK,.03,"E")  ; get domain name IA#3335 
          Q:$G(RMSDOM)="" "" 
          ;
          S:$$PROD^XUPROD() RMSDOM="HL7."_RMSDOM   ; prefix domain name 
          Q RMSDOM 
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Added 12/31/25 - Effective with patch GMRC*3.0*213 
 Method:    GMRC would like to check for the existence of a logical link to fix
 [INC36516023 - GMRC PACKAGE Interfacility Consults not screening for primary
 VistA sites]                                
  
 Details:    The code used when accessing the C cross-reference is shown below. 
     
                                                 
 ISPRIMARY(INSTIEN) ; TRUE if site is an active primary site N X,Y,STANUM S
 STANUM=$$STA^XUAF4(INSTIEN) Q:STANUM="" 0 Q:'($L(STANUM)=3) 0 ; must be 3
 digits Q:STANUM=200 0 ; not station 200 
  Q:'$D(^HLCS(870,"C",INSTIEN)) 0 ; must have a logical link 
 Q:($$GET1^DIQ(4,INSTIEN_",",13,"","","")="OTHER") 0 ; cannot be type other 
 Q:($$GET1^DIQ(4,INSTIEN_",",101,"","","")) 0 ; quit if INACTIVE FACILITY FLAG
 set to 1 Q 1  

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
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
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^DNS^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: VISTA DATA EXTRACTION FRAMEWORK
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

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
  STATUS: Active                        DURATION: Till Otherwise Agreed
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.  

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
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
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
 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
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 "_<code>_" passed, where <code> is a LOINC or NLT code 
    passed in input parameter LA7SC.  
  
  7 Invalid list of subscripts: '_<subscript>, where <subscript> 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
  DATE ACTIVATED: JUL 14, 2010

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
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
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
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
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
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
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
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
 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
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

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
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
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. 

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
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
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.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
 HMP version 2.0 is using the ISCP and CPCLASS entry points.  

NUMBER: 3569                            IA #: 3569
  GLOBAL ROOT: XMB('NAME'               DATE CREATED: APR 26, 2002
  CUSTODIAL PACKAGE: MAILMAN            USAGE: Private
  TYPE: File
  NAME: REQUEST TO ACCESS THE 'NAME' NODE OF XMB
  ID: XMB('NAME'
GLOBAL REFERENCE: XMB('NAME'
 GENERAL DESCRIPTION:   IB needs to determine Production or Test account and
 would like to use ^XMB("NAME") and ^XMB("NETNAME") to compare with each other
 and to determine if the first "." piece of this value indicates we're in the 
 test account.  We're looking for TEST, MIRROR, TRAIN, MIR, etc. in the node
 name.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: XMB-NAME
KEYWORDS: XMB-NETNAME
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 3570                            IA #: 3570
  FILE NUMBER: 409.68                   GLOBAL ROOT: SCE
  DATE CREATED: APR 26, 2002            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  NAME: WHO IS THE CODER OF PCE         ID: SCE
GLOBAL REFERENCE: SCE(D0,'USER'
FIELD NUMBER: 101                       FIELD NAME: EDITED LAST BY
  LOCATION: USER;1                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 102                       FIELD NAME: DATE/TIME LAST EDITED
  LOCATION: USER;2                      ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   IB would like to determine the name of the coder for
 outpatient encounters/claims.  We shall determine this by the person who most 
 recently edited the outpatient encounter file.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: CODER
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 3571                            IA #: 3571
  FILE NUMBER: 40.8                     GLOBAL ROOT: DG(40.8
  DATE CREATED: APR 26, 2002            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: SENDING THE DIVISION ID TO CLAIMSMANAGER
  ID: DG(40.8
GLOBAL REFERENCE: DG(40.8,D0,0
FIELD NUMBER: 1                         FIELD NAME: FACILITY NUMBER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   IB would like to be able to send the division
 identifier to ClaimsManager which is a COTS claims scrubbing tool.  The
 division ID will allow ClaimsManager to separate claims by their
 'organization' id field and will allow for reports to be able to be broken out
 by VistA division.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

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                 REMOTE PROCEDURE: 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
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. 
 
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   WebVRAM would like to develop a prototype that would
 allow a CPRS user to view their CPRS alerts/notifications for all of their
 sites in a single location with the WebVRAM web application. The alerts
 displayed will be information only, not actionable.  
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Effective with OR*3*622 for the purposes of pulling
 back view alerts to display in the Salesforce CRM application, using the OR
 CRMS MENU Context Option. This is an interim solution. OR CRMS MENU shall be
 replaced by a context option in the CRMS namespace.  

NUMBER: 3573                            IA #: 3573
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870,
  DATE CREATED: MAY 09, 2002            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: File
  NAME: Get Institution from file 870   ID: HLCS(870,
GLOBAL REFERENCE: HLCS(870,SUB,0
FIELD NUMBER: .02                       FIELD NAME: INSTITUTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   MPIF application needs to be able to get the
 institutions for the logical links returned in GET^HLSUB(sub,0,"",.array) 
  
 The following is the actual code that will be used to get the institutions: 
  
 .S INST=$$GET1^DIQ(870,+$P(ARRAY("LINKS",SUBNUM),"^",6)_",",.02,"E") 
  
 IA retired.  See IA 3335 for current documentation.  
  STATUS: Retired
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

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
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
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: 3576                            IA #: 3576
  DATE CREATED: MAY 13, 2002
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMRCTIU
  NAME: TIU use of GMRCTIU              ID: GMRCTIU
 GENERAL DESCRIPTION:   This integration agreement describes calls used by TIU
 in GMRCTIU.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
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 GET^GMRCTIU to update the Consult from TIU.  

NUMBER: 3577                            IA #: 3577
  DATE CREATED: MAY 14, 2002            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMTSDVR
  NAME: DBIA-3577                       ID: GMTSDVR
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ENTR
VARIABLES: DFN                          TYPE: Input
VARIABLES: GMTSTYP                      TYPE: Input
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Run a health summary report to place into a TIU object 

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
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
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
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
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA

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
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: LAB SERVICE

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
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
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
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: 1
  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
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 prior to transmission.  If
 it is not greater than 0, then the transmission is canceled.  
FIELD NUMBER: 9                         FIELD NAME: SPOOL DATA
  LOCATION: 0;10                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The pointer to the Spool File is used to passed the
 document to PDX for transmission of the Health Summary from one site to
 another.  
FIELD NUMBER: 10                        FIELD NAME: INCOMPLETE REPORT INDICATOR
  LOCATION: 0;11                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is a flag to indicate if the report is complete.  If
 set to '1', then the spooled document will be passed to PDX for transmission
 of the Health Summary from one site to another.  
 GENERAL DESCRIPTION:   Health Summary uses Mailman to track spooled documents
 for transmission.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMTSPDX
KEYWORDS: PDX
KEYWORDS: XMB(3.51,
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Health Summary accesses the SPOOL DOCUMENT file to
 determine the status, number of lines and location of the spooled document for
 transmitting a Health Summary from one site to another via the PDX package.  
SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE
SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE

NUMBER: 3588                            IA #: 3588
  FILE NUMBER: 3.519                    GLOBAL ROOT: XMBS(3.519,
  DATE CREATED: MAY 23, 2002            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: HEALTH SUMMARY SPOOLED DATA     ID: XMBS(3.519,
GLOBAL REFERENCE: XMBS(3.519,D1,2,
FIELD NUMBER: 3                         FIELD NAME: TEXT
  LOCATION: 2;0                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the text of the spooled Health Summary to be
 transmitted via PDX.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMTSPDX
KEYWORDS: PDX
KEYWORDS: XMBS(3.519
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Health Summary accesses the Spooled Data file to
 prepare the spooled data in the spooled Health Summary document for
 transmission via PDX.  

NUMBER: 3589                            IA #: 3589
  DATE CREATED: MAY 24, 2002            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUHUI
  NAME: Tasking An Event From a New Style Xref
  ID: XUHUI
 GENERAL DESCRIPTION:   This support API allows other packages to task an
 Option(s) or Protocol(s) from a New Style cross-reference.  
  
 For more details on usage please see: 
   http:// http://vista.url//kernel/apis/OPKG^XUHUI.htm 
  STATUS: Active
COMPONENT/ENTRY POINT: OPKG()
 COMPONENT DESCRIPTION:   
  For detail about this API please see: 
  http:// http://vista.url//kernel/apis/OPKG^XUHUI.htm 
  
  For details how this cross-reference handles the changes, please see Patch
 XU*8*236, Patch Description.  For more detailed information about the new
 style cross-reference please see: 
                      
  http:// http://vista.url//fileman/fileMan_training/online_pres /FMtut_frm.htm 
VARIABLES: XUHUIOP                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional) This parameter is a set of Numeric codes
 that tells the Unwinder whether to use the PROTOCOL file (#101) or the OPTION
 file (#19). If parameter is null, the default value will be used (i.e., 
 "101"): 
  
 101 (default) = PROTOCOL file will be used.  
  
 19 = the OPTION file will be used. 
VARIABLES: XUHUINM                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This parameter is the NAME (#.01) value of
 the Protocol or Option that is to be launched.  
VARIABLES: XUHUIA                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This parameter is a Set of Codes. If
 parameter is null, the default value will be used (i.e., "S"): 
  
 S (default) = The data being passed is from the SETting of the 
               cross-reference.  
  
 K = The data being passed is from the KILLing of the cross-reference. 
VARIABLES: XUHUIXR                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This parameter is the name of the
 cross-reference.  

NUMBER: 3590                            IA #: 3590
  DATE CREATED: MAY 29, 2002            CUSTODIAL PACKAGE: SURGERY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: SROGMTS                      NAME: HEALTH SUMMARY SURGICAL EXTRACT
  ID: SROGMTS                           STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: GMTSR
KEYWORDS: SROGMTS
COMPONENT/ENTRY POINT: HS(IEN)
 COMPONENT DESCRIPTION:   Extracts Surgery Reports from Surgery/TIU globals.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Internal Entry Number of the SURGERY file
 #130.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Effective with the release of Surgery patch #100,
 Health Summary needs to call the entry point HS^SROGMTS(IEN) to extract
 Surgery reports from the Surgery global and TIU documents global, to include
 signature.  

NUMBER: 3591                            IA #: 3591
  FILE NUMBER: .11                      GLOBAL ROOT: DD(.11
  DATE CREATED: MAY 29, 2002            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUHUI236
  NAME: Install 'AXUHUI' and 'AXUHUIKEY' Xrefs
  ID: XUHUI236
 GENERAL DESCRIPTION:   Patch XU*8*236 needs to install/tranport two New Style
 xrefs: 'AXUHUI' and 'AXUHUIKEY' without sending the necessary field DDs too. 
 This request is for a one time IA.  
  STATUS: Active
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland
 SUBSCRIBING DETAILS:   Using UPDATE^DIE the following fields will be
 installed: 
  
 Indexs: AXUHUI & AXUHUIKEY 
  
 .01       FILE .02       NAME .11       SHORT DESCRIPTION .2        TYPE .4    
    EXECUTION .5        ROOT TYPE .51       ROOT FILE .42       USE 1.1      
 SET LOGIC 2.1       KILL LOGIC 2.5       KILL ENTIRE INDEX CODE 11.1     
 CROSS-REFERENCE VALUES 
           .01  ORDER NUMBER 
           1    TYPE OF VALUE 
           2    FILE 
           3    FIELD 
           7    COLLATION 
  
 a call is then made to $$FIND1^DIC() to get the IEN of the installed index and
 then a call is made to WP^DIE() to install: 
  
 .1        DESCRIPTION 

NUMBER: 3592                            IA #: 3592
  FILE NUMBER: 20                       GLOBAL ROOT: VA(20
  DATE CREATED: JUN 10, 2003            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: DBIA3592                        ID: VA(20
GLOBAL REFERENCE: VA(20,D0,1)
FIELD NUMBER: 7                         FIELD NAME: SOURCE NAME FORMAT FLAGS
  LOCATION: 1;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Set XUNOTRIG=1 to prevent ANAME cross reference from
 being executed prior to DIE^FILE call.  
 GENERAL DESCRIPTION:   Clean up routines, as part of the Patient Name
 Standardization (DG*5.3*244) patch, will need to be run at 8-10 test sites. 
 This clean up will correct the name standardization performed in previous test 
 versions of the patch.  This is a one time only clean up.  
  
 In addition to correcting the standardization of patient names, the clean up
 routines will need to populate the SOURCE NAME FORMAT FLAGS (#7) field of the
 NAME COMPONENTS (#20) file for every component entry not having a value. 
  
 In this agreement we are requesting access to add a flag value to the SOURCE
 NAME FORMAT FLAGS (#7) field of the NAME COMPONENTS (#20) file. And, in order
 to prevent the ANAME cross reference from being executed we are requesting the
 ability to set XUNOTRIG=1 before making the DIE^FILE call to add a value to
 the field.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 3593                            IA #: 3593
  DATE CREATED: JUN 03, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DPTLK6                       NAME: DBIA3593
  ID: DPTLK6
 GENERAL DESCRIPTION:   Allow access to the Patient Lookup components for
 checking Means Test Requirements and the Cleveland Alert.  
  STATUS: Active
KEYWORDS: GUIMTD
KEYWORDS: GUIBS5A
KEYWORDS: DPTLK6
COMPONENT/ENTRY POINT: GUIMTD
 COMPONENT DESCRIPTION:   
    CHECKS IF MEANS TEST REQUIRED FOR PATIENT AND 
    CHECKS IF MEANS TEST DISPLAY REQUIRED FOR USER'S DIVISION 
    RETURNS 1 IN 1ST STRING IF BOTH TRUE OTHERWISE 0 
    IF BOTH TRUE RETURNS TEXT IN 2ND AND 3RD STRING (IF ANY) 
VARIABLES: TMP                          TYPE: Both
 VARIABLES DESCRIPTION:   Passed as reference in first parameter.  Returns the
 results array.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patients IEN passed as second parameter.  
COMPONENT/ENTRY POINT: GUIBS5A
 COMPONENT DESCRIPTION:   
    CHECKS IF OTHER PATIENTS ON 'BS5' XREF WITH SAME LAST NAME 
    RETURN 1 OR 0 IN 1ST STRING (-1 IF BAD DFN OR NO ZERO NODE).  
    RETURNS ARRAY NODES WHERE TEXT IS PRECEEDED BY 0 AND PATIENT DATA 
    IS PRECEEDED BY 1.  PATIENT DATA WILL BE IN FOLLOWING FORMAT: 
    1^DFN^PATIENT NAME^DOB^SSN 
VARIABLES: TMP                          TYPE: Both
 VARIABLES DESCRIPTION:   Passed as reference in first parameter.  Returns the
 results array.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patients IEN passed as second parameter.  

NUMBER: 3594                            IA #: 3594
  DATE CREATED: JUN 03, 2002            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DDBR0                        NAME: BROWSER SWITCHING
  ID: DDBR0
 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# 2540.  (This is a continuation of IA# 2540, and is used to cover
 references to the PSR subroutine tag in routine DDBR0.) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PSR
 COMPONENT DESCRIPTION:   Used to display a specific Browser screen without
 user interaction.  (This API is used in conjunction with a call to WP^DDBR2
 covered by IA# 2540.) 
SUBSCRIBING PACKAGE: HEALTH LEVEL SEVEN
  ISC: Oakland

NUMBER: 3595                            IA #: 3595
  FILE NUMBER: 355.1                    GLOBAL ROOT: IBE(355.1
  DATE CREATED: JUN 11, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: INSURANCE PLAN TYPE             ID: IBE(355.1
GLOBAL REFERENCE: IBE(355.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The NAME of the type of plan.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMTSDEM
KEYWORDS: HEALTH SUMMARY
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Health Summary displays insurance information.  It
 receives the type of plan from the supported call to ALL^IBCNS1.  This value
 points to the TYPE OF PLAN (#355.1).  
SUBSCRIBING PACKAGE: FEE BASIS
  DATE ACTIVATED: JUL 10, 2012

NUMBER: 3596                            IA #: 3596
  FILE NUMBER: 36                       GLOBAL ROOT: DIC(36,
  DATE CREATED: JUN 11, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: INSURANCE COMPANY NAME
  ID: DIC(36,
GLOBAL REFERENCE: DIC(36,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Insurance Company Name 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: GMTSDEM
KEYWORDS: HEALTH SUMMARY
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Health Summary displays insurance information.  It
 receives the name of the insurance company from the supported call ALL^IBCNS1. 
 This value points to the INSURANCE COMPANY (#36).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 3597                            IA #: 3597
  FILE NUMBER: 1.1                      GLOBAL ROOT: DIA(985
  DATE CREATED: JUN 12, 2002            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DIA(985
  ID: DIA(985
GLOBAL REFERENCE: DIA(985,IEN
 GLOBAL DESCRIPTION:   This is the global reference to the audit for 985 that
 is being purged.  
GLOBAL REFERENCE: DIA(985,'C'
 GLOBAL DESCRIPTION:   This is the cross reference on the date/time of the
 audit.  The purge job is $O through this cross reference to determine which
 entries should be purged.  The entry is also hard killed when the actual entry
 is purged.  
GLOBAL REFERENCE: DIA(985,'D'
 GLOBAL DESCRIPTION:   This cross reference is on the user that made the edit. 
 It is hard killed for the entry that is being purged.  
GLOBAL REFERENCE: DIA(985,'B'
 GLOBAL DESCRIPTION:   This cross reference is on the entry.  It is being hard
 killed when the entry is being purged.  
 GENERAL DESCRIPTION:   The MPI Austin software is running an audit purge to
 clean up the ^DIA(985 entries for a time range.  The FileMan audit purge ran
 too slow and was not cleaning up completely each of the entries in the purge
 date range.  So MPI Austin wrote its own purge for the ^DIA(985, entries.  
  
 The MPI Austin software is therefore, requesting a DBIA to have direct global
 read and kill of ^DIA(985, ^DIA(985,"C" and direct global kill of ^DIA(985,"D"
 and ^DIA(985,"B".  
  STATUS: Active
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX

NUMBER: 3598                            IA #: 3598
  DATE CREATED: JUN 12, 2002            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSJOERI                      NAME: DBIA 3598
  ID: PSJOERI
 GENERAL DESCRIPTION:   The purpose of this API is to allow Computer Patient
 Record System (CPRS) to reinstate Inpatient Medications orders based on a
 patient being discharged from an Observation treating specialty and
 re-admitted within 24 hours to another treating specialty.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSJOERI
COMPONENT/ENTRY POINT: ENR
 COMPONENT DESCRIPTION:   The ENR component allows the reinstatement of an
 Inpatient Medications order if the status of the order is discontinued and the
 order was auto discontinued.  
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
 reinstated.  (Required) 
VARIABLES: WARD                         TYPE: Input
 VARIABLES DESCRIPTION:   The Internal Entry number of the ward the patient is
 being admitted to. (Required) 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3599                            IA #: 3599
  FILE NUMBER: 19.2                     GLOBAL ROOT: DIC(19.2
  DATE CREATED: JUN 18, 2002            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: OPTION SCHEDULING (#19.2) file  ID: DIC(19.2
GLOBAL REFERENCE: DIC(19.2,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: QUEUED TO RUN AT WHAT TIME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   
  The Master Patient Index (MPI) will read (with FileMan) the following 
  fields from the OPTION SCHEDULING (#19.2) file.  The data is used by 
  the MPI Data Quality Management team on the Austin MPI.  The report 
  shows the status of various tasks that routinely run.  
     
  Example: 
                          MPI STATUS REPORT 
                    (generated Jun 15, 2002@18:52) 
   
  Scheduled Background Job   Last Completed Run       Next Scheduled Run 
  ------------------------   ------------------       ------------------
  MPI Stat Report            JUN 14, 2002@08:21       JUN 16, 2002@02:00 
  Audit Data Purge           JUN 14, 2002@22:00       JUN 15, 2002@22:00 
  Invalid Site Monitor       JUN 14, 2002@22:00       JUN 15, 2002@22:00 
  Dup SSN Compile            JUN 15, 2002@18:45       NOT SCHEDULED 
   
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
  ISC: Birmingham
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 3600                            IA #: 3600
  DATE CREATED: JUN 24, 2002
  CUSTODIAL PACKAGE: ENROLLMENT APPLICATION SYSTEM
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: EASECCAL                     NAME: LTC co-pay API
  ID: EASECCAL
 GENERAL DESCRIPTION:   $$COPAY^EASECCAL(DFN,MNTH,LOS) This extrinsic function
 returns LTC status and maximal monthly LTC copay amounts for the patient for
 specific month if applicable. It is used in calculation of LTC copays in IB
 package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LTC
KEYWORDS: COPAY
COMPONENT/ENTRY POINT: $$COPAY
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN.  
VARIABLES: MNTH                         TYPE: Input
 VARIABLES DESCRIPTION:   Last day of month for the LTC co-pay calculation in
 FM format (e.g. 3020131).  
VARIABLES: LOS                          TYPE: Input
 VARIABLES DESCRIPTION:   (Length of stay) The number of days in the patient's
 LTC episode.  
VARIABLES: $$COPAY                      TYPE: Output
 VARIABLES DESCRIPTION:   function returns 0 or compound string with "^"
 delimiters.  "0" return value indicates that no completed LTC co-pay test on 
     file (there is no 1010EC form) for patient for the month.  if returns
 string then: 
     piece 1: LTC co-pay test status (1=Exempt; 2=Non-Exempt) 
     piece 2: If Exempt, Reason for Exemption  (IEN of file 
              #714.1) 
     piece 3: Calculated LTC co-payment for inpatient care for 
              LOS = 1-180 days.  
     piece 4: Calculated LTC co-payment for inpatient care for 
              LOS = 181+ days.  
     piece 5: Calculated LTC co-payment for outpatients.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: FEE BASIS

NUMBER: 3601                            IA #: 3601
  DATE CREATED: JUN 28, 2002            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: RCBEADJI                     NAME: DBIA3601
  ID: RCBEADJI
 GENERAL DESCRIPTION:   This IA is between PRCA and IB as a temporary IA in
 relation to the Hartford/USAA settlement agreement.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2002
COMPONENT/ENTRY POINT: $$DECREASE
 COMPONENT DESCRIPTION:   This call will decrease the specified bill and
 automatically place comments in the adjustment transaction indicating the bill
 was decreased as a result of the Hartford/USAA settlement.  
VARIABLES: RCBN                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the bill number to be decreased.  It should
 be in the format of just the actual bill number without the station number
 prefix.  
VARIABLES: RCTEST                       TYPE: Input
 VARIABLES DESCRIPTION:   This is an optional flag indicating test only and
 that no decrease adjustment is to be performed.  The return values will
 continue to be returned except the first piece.  The dollar amounts returned
 will only be an estimate.  
VARIABLES: RCAMT                        TYPE: Input
 VARIABLES DESCRIPTION:   This optional variable when specified will decrease
 the specified bill number by the amount.  If there is no amount specified the
 bill will be decreased in full.  
VARIABLES: $$DECREASE                   TYPE: Output
 VARIABLES DESCRIPTION:   The return value of this function will be: 
  
 If an error occurs:  -(error number) ^ error message 
  
  
 If success:    decrease adjust DA ^ decrease amt ^ int amout ^ admin amt 
                ^ marshal amt ^ court amt 
COMPONENT/ENTRY POINT: $$INTADMIN
 COMPONENT DESCRIPTION:   This function is used to exempt all interest, admin,
 marshal, and court fees associated with a receivable in the Hartford/USAA
 settlement.  The decrease adjustment will be flagged indicating it was part of
 this settlement.  
VARIABLES: RCBILLDA                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number for a receivable in
 file 430.  
VARIABLES: RCTEST                       TYPE: Input
 VARIABLES DESCRIPTION:   This is an optional flag indicating test only and
 that no exemption of interest, admin, marshal, and court chares are to be
 performed.  The return values will continue to be returned except the first
 piece.  The dollar amounts returned will only be an estimate.  
VARIABLES: $$INTADMIN                   TYPE: Output
 VARIABLES DESCRIPTION:   Return is the amounts adjusted: 
        
          interest ^ admin ^ marshal ^ court 
        
       OR if error: - (error number) ^ error message 
COMPONENT/ENTRY POINT: $$AMOUNT
 COMPONENT DESCRIPTION:   This function is used to look up the current
 principal balance of ANY entry in file 430.  
VARIABLES: RCBILLDA                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number for a receivable in
 file 430.  
VARIABLES: $$AMOUNT                     TYPE: Output
 VARIABLES DESCRIPTION:   This value will be the current principal balance of
 the receivable specified.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 3602                            IA #: 3602
  FILE NUMBER: 661.1                    GLOBAL ROOT: RMPR(661.1,
  DATE CREATED: JUL 02, 2002            CUSTODIAL PACKAGE: PROSTHETICS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: PROSTHETIC HCPCS FILE
  ID: RMPR(661.1,
GLOBAL REFERENCE: RMPR(661.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: HCPCS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Lookup via FileMan utility like $$FIND1^DIC() using "B"
 cross reference.  
FIELD NUMBER: 5                         FIELD NAME: NPPD REPAIR CODE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like $$GET1^DIQ().  
FIELD NUMBER: 6                         FIELD NAME: NPPD NEW CODE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like $$GET1^DIQ().  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: NPPD
KEYWORDS: HCPCS
SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  ISC: Washington/Silver Spring

NUMBER: 3603                            IA #: 3603
  FILE NUMBER: 668                      GLOBAL ROOT: RMPR(668,
  DATE CREATED: JUL 02, 2002            CUSTODIAL PACKAGE: PROSTHETICS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: PROSTHETIC SUSPENSE
  ID: RMPR(668,
GLOBAL REFERENCE: RMPR(668,D0)
FIELD NUMBER: IEN                       FIELD NAME: Internal Entry Number
  ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Lookup via FileMan utility like $$FIND1^DIC().  
GLOBAL REFERENCE: RMPR(668,D0,0)
FIELD NUMBER: .01                       FIELD NAME: SUSPENSE DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like $$GET1^DIQ().  
FIELD NUMBER: 1                         FIELD NAME: VETERAN
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like EN^DIQ1 or
 $$GET1^DIQ().  
FIELD NUMBER: 2                         FIELD NAME: STATION
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like $$GET1^DIQ().  
FIELD NUMBER: 9                         FIELD NAME: TYPE OF REQUEST
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like $$GET1^DIQ().  
GLOBAL REFERENCE: RMPR(668,D0,2)
FIELD NUMBER: 4                         FIELD NAME: DESCRIPTION OF ITEM/SERVICES
  LOCATION: 2;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like $$GETS^DIQ().  
GLOBAL REFERENCE: RMPR(668,D0,8)
FIELD NUMBER: 1.5                       FIELD NAME: PROVISIONAL DIAGNOSIS
  LOCATION: 8;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like $$GET1^DIQ().  
FIELD NUMBER: 1.6                       FIELD NAME: ICD9
  LOCATION: 8;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like $$GET1^DIQ().  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  ISC: Washington/Silver Spring

NUMBER: 3604                            IA #: 3604
  FILE NUMBER: 669.9                    GLOBAL ROOT: RMPR(669.9,
  DATE CREATED: JUL 02, 2002            CUSTODIAL PACKAGE: PROSTHETICS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: PROSTHETICS SITE PARAMETERS
  ID: RMPR(669.9,
GLOBAL REFERENCE: RMPR(669.9,D0,0)
FIELD NUMBER: 1                         FIELD NAME: STATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like EN^DIQ1 or
 $$GET1^DIQ().  Lookup entry in file via FileMan utility like $$FIND1^DIC()
 using the "C" cross reference.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PROSTHETICS SITE
SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  ISC: Washington/Silver Spring

NUMBER: 3605                            IA #: 3605
  DATE CREATED: JUL 02, 2002            CUSTODIAL PACKAGE: PROSTHETICS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Other
  NAME: PROSTHETICS ORDER CONTROL SERVER OPTIONS
 GENERAL DESCRIPTION:   The COMMUNICATIONS SERVICE LIBRARY needs to send an
 e-mail message to Prosthetics Server type options announcing the arrival of
 data from the coreFLS database and to indicate in which part of the ^XTMP
 global the data is stored.  This is the mechanism for handoff of data from the 
 COMMUNICATIONS SERVICE LIBRARY to PROSTHETICS.  
  
  Option Names       Interface                 Message Content 
  RMPR_OC_SPL        Send Patient List         ^XTMP("CSLPRSP;"_MCID,doc# 
  RMPR_OC_PURGE      Purge Patient List        ^XTMP("CSLPRSU8;"_MCID,doc# 
  RMPR_OC_HO         Send Bulk Order           ^XTMP("CSLPRSU5;"_MCID,doc# 
  RMPR_OC_SPO_OK     Send Approved PO (ok)     ^XTMP("CSLPRPO;"_MCID 
  RMPR_OC_SPO_RJT    Send Approved PO (reject) ^XTMP("CSLPRPO;"_MCID 
  RMPR_OC_UNFREEZE   Send Unfreeze Request     ^XTMP("CSLPRPO;"_MCID 
  
 Note:  MCID is the Message Control ID of the initial HL7 message in the 
 dialog.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: coreFLS Interface
SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  ISC: Washington/Silver Spring

NUMBER: 3606                            IA #: 3606
  DATE CREATED: JUL 02, 2002            CUSTODIAL PACKAGE: PROSTHETICS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         ROUTINE: RMPR9EOU
  NAME: RMPR9EOU                        ID: RMPR9EOU
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: coreFLS Purchase Order
COMPONENT/ENTRY POINT: $$PO1
 COMPONENT DESCRIPTION:   Call this entry point to check for the existence of a
 Purchase Order in the Prosthetics database, when supplied with the coreFLS 
 Purchase Order identifiers. 
  
                        Returns: 0 or 1.  
                                 0 =  Not Present 
                                 1 =  Present 
VARIABLES: F50                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the SEGMENT1 (external PO#) value from the
 PO_HEADERS_ALL table of Oracle Purchasing.  
VARIABLES: F51                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the PO_HEADER_ID (internal PO#) value from
 the PO_HEADERS_ALL table of Oracle Purchasing.  
VARIABLES: F52                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the ORG_ID (Organizational Code) value from
 the PO_HEADERS_ALL table of Oracle Purchasing.  
COMPONENT/ENTRY POINT: $$HCPC
 COMPONENT DESCRIPTION:   Call this component to verify that a Purchase Order
 line item with this Prosthetics HCPCS code may be imported from CoreFLS.  This
 extrinsic function returns '1' if the HCPCS code is acceptable and '0'
 otherwise.  
VARIABLES: HCPCS                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the unique 5-8 character Prosthetics HCPCS
 code.  
SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  ISC: Washington/Silver Spring

NUMBER: 3610                            IA #: 3610
  DATE CREATED: JUL 02, 2002
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Other                           NAME: coreFLS PURCHASE ORDER
 GENERAL DESCRIPTION:   This global subtree of ^XTMP contains data for a Single
 Patient, Approved Purchase Order created in coreFLS and sent to VistA
 Prosthetics for processing. The COMMUNICATIONS SERVICE LIBRARY package sets up
 this global upon receipt of the HL7 ORM^O01 message and the PROSTHETICS
 package then extracts the data.  
  
 MCID is the Message Control ID from the HL7 message's MSH segment.  
  
 GLOBAL REFERENCES: 
  
  ^XTMP("CSLPRPO;"_MCID,0)=Purge date^Create Date^"PO Sent from coreFLS to 
     VistA" 
  ^XTMP("CSLPRPO;"_MCID,"CONSULT")=Consult ID^Inpatient or Outpatient 
     ^station 
  ^XTMP("CSLPRPO;"_MCID,"ITEM",counter,"ACCOUNTING")=ACS^Alias^Purchase 
     Card Number 
  ^XTMP("CSLPRPO;"_MCID,"ITEM",counter,"DELIVERY")=Location Code^Location 
     Description^Date Needed 
  ^XTMP("CSLPRPO;"_MCID,"ITEM",counter,"DETAIL",1)=PO_LINE_ID^ITEM_ID 
     (internal item number)^SEGMENT1 (external item number)^Quantity^Unit 
     code;name^Unit Price 
  ^XTMP("CSLPRPO;"_MCID,"ITEM",counter,"DETAIL",2)=Manufacturer 
     code;name^Vendor Product Number^Contract Number 
  ^XTMP("CSLPRPO;"_MCID,"ITEM",counter,"DETAIL",3)=HCPC Code^NPPD Line 
     ^Patient Category^Transaction Type 
  ^XTMP("CSLPRPO;"_MCID,"ITEM",counter,"DETAIL",4)=Date Last Edited 
  ^XTMP("CSLPRPO;"_MCID,"ITEM",counter,"DETAIL",5)=Line Counter^"ITEM 
     DESCRIPTION" 
  ^XTMP("CSLPRPO;"_MCID,"ITEM",counter,"DETAIL",5,counter,0)=Description 
     Text 
  ^XTMP("CSLPRPO;"_MCID,"ITEM",counter,"DETAIL",6)=Line Counter^"NOTE TO 
     SUPPLIER" 
  ^XTMP("CSLPRPO;"_MCID,"ITEM",counter,"DETAIL",6,counter,0)=Note to 
     Supplier Text 
  ^XTMP("CSLPRPO;"_MCID,"ITEM",counter,"DETAIL",7)=Line Counter^"NOTE TO  
     RECEIVER" 
  ^XTMP("CSLPRPO;"_MCID,"ITEM",counter,"DETAIL",7,counter,0)=Note to 
     Receiver Text 
  ^XTMP("CSLPRPO;"_MCID,"ITEM",counter,"DETAIL",8)=Line Counter^"ITEM 
     ATTACHMENT" 
  ^XTMP("CSLPRPO;"_MCID,"ITEM",counter,"DETAIL",8,counter,0)=Item 
     Attachment Text 
  ^XTMP("CSLPRPO;"_MCID,"ORDER CONTROL")=Order Control^Reason 
  ^XTMP("CSLPRPO;"_MCID,"PO",1)=SEGMENT1 (external PO number)^ 
     PO_HEADER_ID (internal PO number)^Station^ORG_ID^Enter Date^ 
     Enter Agent SSN^Approved Date^Action Agent SSN^Lastname^First Name^ 
     Middlename^Suffix 
  ^XTMP("CSLPRPO;"_MCID,"PO",2)=Authorization Status^Version Number^Version 
     Date 
  ^XTMP("CSLPRPO;"_MCID,"PO",4)=Line Counter^"COMMENTS" 
  ^XTMP("CSLPRPO;"_MCID,"PO",4,counter,0)=Comments Text 
  ^XTMP("CSLPRPO;"_MCID,"PATIENT")=ICN^'NI' or 'LR'^Station^DFN^Station 
     ^SSN^Lastname^Firstname^Middlename^Suffix 
  ^XTMP("CSLPRPO;"_MCID,"PPA")=SSN^Lastname^Firstname^Middlename^Suffix 
  ^XTMP("CSLPRPO;"_MCID,"SHIPPING",1)=Location Code^Address Line1^Address 
     Line2 
  ^XTMP("CSLPRPO;"_MCID,"SHIPPING",2)=City^State^Zip Code 
  ^XTMP("CSLPRPO;"_MCID,"SHIPPING",3)=FOB^Ship to Terms^S&H Charges 
     ^Currency^Shipping PO_LINE_ID 
  ^XTMP("CSLPRPO;"_MCID,"VENDOR","ADDRESS")=Address Line1^Address 
     Line2^City^State^Zip Code 
  ^XTMP("CSLPRPO;"_MCID,"VENDOR","ID")=Name^ID Number 
  ^XTMP("CSLPRPO;"_MCID,"VENDOR","PHONE")=Voice^Fax 
  ^XTMP("CSLPRPO;"_MCID,"ZERRORS",counter)=Error description 
  
 Note: All dates are in FileMan format, converted from HL7 date format, if 
 necessary.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: coreFLS PURCHASE ORDER
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Hines

NUMBER: 3612                            IA #: 3612
  DATE CREATED: JUL 03, 2002            CUSTODIAL PACKAGE: SURGERY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: SROESL                       NAME: Calls to Routine SROESL
  ID: SROESL
 GENERAL DESCRIPTION:   Build TMP global of Surgery cases electronically signed
 for a given Report Identifier (RI) to be used in Reports Tab in CPRS (GUI).  
  
 ^TMP("SROLST",$J,case #,RI)=Report Status^TIU DOCUMENT FILE # 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CASLIST(SDFN,SIDN)
 COMPONENT DESCRIPTION:   Calling this component will result in generating a
 list of all signed Surgery reports of a given Report Identifier type for that
 patient.  
VARIABLES: SDFN                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN in PATIENT file (#2).  
VARIABLES: SIDN                         TYPE: Input
 VARIABLES DESCRIPTION:   Report Identifier: 1-OPERATION REPORT, 
                    2-NURSE INTRAOPERATIVE REPORT, 
                    3-PROCEDURE REPORT (NON-O.R.).  
                    4-ANESTHESIA REPORT, and 
                    5-The above item 1,2, and 4 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3613                            IA #: 3613
  DATE CREATED: JUL 03, 2002            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: MDRPCOP                      NAME: Imaging - Visit Info
  ID: MDRPCOP
 GENERAL DESCRIPTION:   Imaging has permission, for a limited time, to call
 GETVST^MDRPCOP and obtain a list of patient visit information.  The time frame
 to be identified by Clinical Procedures when the code in GETVST^MDRPCOP is 
 changed to call the approved API (SELECTED^VSIT).  Clinical Procedures will
 coordinate with Imaging on the release of the patch and identify the passing
 parameters used in the call to SELECTED^VSIT to ensure continuity with both
 applications (Imaging and Clinical Procedures).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDRPCOP
COMPONENT/ENTRY POINT: GETVST
 COMPONENT DESCRIPTION:   This sub-module returns a list of visits for a given
 patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's dfn.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   A subscripted array that contains a list of visits: 
  1st piece has 3 pieces delimited by an ";" 
        - type of visit  ("A","I","V") 
        - date and time 
        - hospital location ien 
  2nd piece  - date/time of visit (internal format) 
  3rd & 4 piece - (external format) hospital location and status.  
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Imaging is calling GETVST^MDRPCOP to obtain a patient's
 list of visits.  

NUMBER: 3614                            IA #: 3614
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: JUL 03, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: PROSTHETICS PATIENT ELIGIBILITY
  ID: DPT(
GLOBAL REFERENCE: DPT(D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like $$GET1^DIQ().  
FIELD NUMBER: .09                       FIELD NAME: SOCIAL SECURITY NUMBER
  LOCATION: 0;9                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like $$GET1^DIQ().  
GLOBAL REFERENCE: DPT(D0,.36)
FIELD NUMBER: .361                      FIELD NAME: PRIMARY ELIGIBILITY CODE
  LOCATION: .36;1                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like EN^DIQ1.  
GLOBAL REFERENCE: DPT(D0,.362)
FIELD NUMBER: .36205                    FIELD NAME: RECEIVING A&A BENEFITS?
  LOCATION: .362;12                     ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like EN^DIQ1.  
FIELD NUMBER: .36215
  FIELD NAME: RECEIVING HOUSEBOUND BENEFITS?
  LOCATION: .362;13                     ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like EN^DIQ1.  
GLOBAL REFERENCE: DPT(D0,.372,D1)
FIELD NUMBER: IEN                       FIELD NAME: Internal Entry Number
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Loop through subfile entries as via $O(^DPT(D0,.372,D1)). 
 
GLOBAL REFERENCE: DPT(D0,.372,D1,0)
FIELD NUMBER: .01                       FIELD NAME: RATED DISABILITIES (VA)
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like EN^DIQ1.  
FIELD NUMBER: 2                         FIELD NAME: DISABILITY %
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like EN^DIQ1.  
FIELD NUMBER: 3                         FIELD NAME: SERVICE CONNECTED
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like EN^DIQ1.  
GLOBAL REFERENCE: DPT(D0,.52)
FIELD NUMBER: .525                      FIELD NAME: POW STATUS INDICATED?
  LOCATION: .52;5                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like EN^DIQ1.  
GLOBAL REFERENCE: DPT(D0,.53)
FIELD NUMBER: .531                      FIELD NAME: CURRENT PH INDICATOR
  LOCATION: .53;1                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like EN^DIQ1.  
FIELD NUMBER: .532                      FIELD NAME: CURRENT PURPLE HEART STATUS
  LOCATION: .53;2                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like EN^DIQ1.  
FIELD NUMBER: .533                      FIELD NAME: CURRENT PURPLE HEART REMARKS
  LOCATION: .53;3                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like EN^DIQ1.  
GLOBAL REFERENCE: DPT(D0,"MPI")
FIELD NUMBER: 991.04                    FIELD NAME: LOCALLY ASSIGNED ICN
  LOCATION: MPI;4                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Extract data via FileMan utility like EN^DIQ1.  
 GENERAL DESCRIPTION:   The following are patient data to be passed to coreFLS
 to support Purchasing and Inventory functions.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  ISC: Washington/Silver Spring

NUMBER: 3615                            IA #: 3615
  FILE NUMBER: 130                      GLOBAL ROOT: SRF(
  DATE CREATED: JUL 08, 2002            CUSTODIAL PACKAGE: SURGERY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            NAME: Surgery on CPRS Reports Tab
  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: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global 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: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,15,D1,0)
FIELD NUMBER: .01                       FIELD NAME: OTHER POSTOP DIAGS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,13,D1,0)
FIELD NUMBER: .01                       FIELD NAME: OTHER OPERATIVE PROCEDURE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PLANNED OTHER PROC CPT CODE
  LOCATION: 2;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,'OP')
FIELD NUMBER: 26                        FIELD NAME: PRINCIPAL PROCEDURE
  LOCATION: OP;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 27                        FIELD NAME: PLANNED PRIN PROCEDURE CODE
  LOCATION: OP;2                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,33)
FIELD NUMBER: 32                        FIELD NAME: PRINCIPAL PRE-OP DIAGNOSIS
  LOCATION: 33;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,34)
FIELD NUMBER: 34                        FIELD NAME: PRINCIPAL POST-OP DIAG
  LOCATION: 34;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,'VER')
FIELD NUMBER: 43                        FIELD NAME: CASE VERIFICATION
  LOCATION: VER;1                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,.2)
FIELD NUMBER: .232                      FIELD NAME: TIME PAT OUT OR
  LOCATION: .2;12                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,9,D1,0)
FIELD NUMBER: 49                        FIELD NAME: SPECIMENS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Word Processing 
GLOBAL REFERENCE: SRF(D0,'CON')
FIELD NUMBER: 35                        FIELD NAME: CONCURRENT CASE
  LOCATION: CON;1                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,'TIU')
FIELD NUMBER: 1000                      FIELD NAME: TIU OPERATIVE SUMMARY
  LOCATION: TIU;1                       ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Read access to selected fields from SURGERY file, #130. 
  
 This Integration Agreement also allows direct global read access to the "B"
 cross reference of the Surgery file.  
  STATUS: Other                         DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
REMINDER: DEC 22, 2008

NUMBER: 3616                            IA #: 3616
  DATE CREATED: JUL 09, 2002
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORBCMA2
  NAME: ORDERABLE ITEM DATA             ID: ORBCMA2
 GENERAL DESCRIPTION:   The entry point EN^ORBCMA2 is provided by OE/RR to
 return orderable item data to Bar Code Med Admin to be used for administering
 medications.  
  STATUS: Active
KEYWORDS: ORBCMA
COMPONENT/ENTRY POINT: $$EN(PSID)
VARIABLES: PSID                         TYPE: Input
 VARIABLES DESCRIPTION:   DRUG INTERNAL FILE NUMBER (Required) 
VARIABLES: $$EN                         TYPE: Output
 VARIABLES DESCRIPTION:   ORDERABLE ITEM IEN ^ ORDERABLE ITEM NAME ^ INACTIVITY
 ^ INPATIENT MEDICATION 
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN

NUMBER: 3617                            IA #: 3617
  FILE NUMBER: 101                      GLOBAL ROOT: ORD(101,B
  DATE CREATED: JUL 10, 2002            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA3617                        ID: ORD(101,B
 GENERAL DESCRIPTION:   Clinical Reminders Package requests to access the B
 index on the protocol file (#101) directly.  
  
 Existing Reminder Package options with LIST MANAGER interfaces use XQORM to 
 allow selection from a list by entering the list item number. 
  
 e.g.  
  
 XQORM   S XQORM("#")=$O(^ORD(101,"B",PROTOCOL_NAME,0))_U_"1:"_VALMCNT 
         S XQORM("A")="Select Item: " 
         Q 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORD(101
KEYWORDS: PROTOCOL
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   ADDED 4/28/2011 
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   3/26/15-Scheduling added as a subscriber for PCMM Web.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 4/30/19 

NUMBER: 3618                            IA #: 3618
  DATE CREATED: JUL 11, 2002            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XIPUTIL                      NAME: POSTAL CODE AND COUNTY CODE APIS
  ID: XIPUTIL
 GENERAL DESCRIPTION:   Allow access to look-up Postal Code and County Code
 data based on supported API references.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: POSTAL
KEYWORDS: COUNTY
KEYWORDS: 5.12
KEYWORDS: 5.13
COMPONENT/ENTRY POINT: POSTAL
 COMPONENT DESCRIPTION:   The POSTAL^XIPUTIL(PCODE,.XIP) entry point will
 provide all data related to the postal code that is input.  
VARIABLES: PCODE                        TYPE: Input
 VARIABLES DESCRIPTION:   Postal Code for which to return the data 
VARIABLES: XIP                          TYPE: Output
 VARIABLES DESCRIPTION:   
      XIP("POSTAL CODE") - the value used to lookup postal data        
      XIP("CITY") - the city that the USPS assigned to this PCODE      
      XIP("COUNTY") - The county associated with this PCODE            
      XIP("COUNTY POINTER") - pointer to the county in file #5.13      
      XIP("STATE") - The state associated with this PCODE              
      XIP("STATE POINTER") - pointer to the state in file #5           
      XIP("INACTIVE DATE") - date on which this PCODE was inactivated  
      XIP("FIPS CODE") - 5 digit FIPS code associated with the county  
      XIP("ERROR") - returns errors encountered during look-up 
COMPONENT/ENTRY POINT: $$FIPS
 COMPONENT DESCRIPTION:   This extrinsic function will return the 5-digit FIPS
 code that uniquely identifies this county.  If the 5-digit FIPS code cannot be
 determined, then "0^error message" is returned.  
VARIABLES: PCODE                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the Postal code for which a 5-digit FIPS code
 will be found.  
COMPONENT/ENTRY POINT: CCODE
 COMPONENT DESCRIPTION:   The CCODE^XIPUTIL(FIPS,.XIPC) entry point will return
 the XIPC array containing components related to the input FIPS county code.  
VARIABLES: FIPS                         TYPE: Input
 VARIABLES DESCRIPTION:   FIPS - 5 digit FIPS County Code for which to return
 the data 
VARIABLES: XIPC                         TYPE: Output
 VARIABLES DESCRIPTION:   The XIPC array will be returned with the following
 subscripts: 
  
 XIPC("FIPS CODE") - 5 digit FIPS county code XIPC("COUNTY") - The county
 associated with this FIPS code XIPC("STATE") - The state associated with this
 FIPS code XIPC("STATE POINTER") - pointer to the state in file #5 
 XIPC("INACTIVE DATE") - date this FIPS code was inactivated XIPC("ERROR") -
 returns errors encountered during look-up 
  
COMPONENT/ENTRY POINT: $$FIPSCHK
 COMPONENT DESCRIPTION:   This extrinsic function will determine if the 5-digit
 FIPS county code that is passed in exists in the County Code (#5.13) file.  If
 the FIPS code exists, then the 5.13 ien for this entry is returned.  If it
 does not exist, then the returned value will be 0.  
VARIABLES: FIPS                         TYPE: Input
 VARIABLES DESCRIPTION:   FIPS - Unique 5-digit FIPS county code associated
 with the county to be checked.  
COMPONENT/ENTRY POINT: POSTALB
 COMPONENT DESCRIPTION:   This API returns all of the active ZIP Codes for a
 single ZIP Code.  
  
 S ZCODE=26452 
  
 >S ZTMP="" 
  
 D POSTALB^XIPUTIL(ZCODE,.ZTMP) 
  
 >ZW ZTMP,ZCODE ZCODE=26452 ZTMP=2 ZTMP(1,"CITY")=WESTON* ZTMP(1,"CITY
 ABBREVIATION")= ZTMP(1,"CITY KEY")=X29362 ZTMP(1,"COUNTY")=LEWIS 
 ZTMP(1,"COUNTY POINTER")=335 ZTMP(1,"FIPS CODE")=54041 ZTMP(1,"POSTAL
 CODE")=26452 ZTMP(1,"PREFERRED CITY KEY")=X29362 ZTMP(1,"STATE")=WEST VIRGINIA 
 ZTMP(1,"STATE POINTER")=54 ZTMP(1,"UNIQUE KEY")=26452X29362 
 ZTMP(2,"CITY")=VALLEY CHAPEL ZTMP(2,"CITY ABBREVIATION")= ZTMP(2,"CITY
 KEY")=X2A444 ZTMP(2,"COUNTY")=LEWIS ZTMP(2,"COUNTY POINTER")=335 ZTMP(2,"FIPS
 CODE")=54041 ZTMP(2,"POSTAL CODE")=26452 ZTMP(2,"PREFERRED CITY KEY")=X29362 
 ZTMP(2,"STATE")=WEST VIRGINIA ZTMP(2,"STATE POINTER")=54 ZTMP(2,"UNIQUE
 KEY")=26452X2A444 
VARIABLES: PCODE                        TYPE: Both
 VARIABLES DESCRIPTION:   (required) Postal Code for which the data is being
 requested.  
VARIABLES: .XIP(n)                      TYPE: Both
 VARIABLES DESCRIPTION:   (required) The number of primary subscripts in an
 array: XIP(n,"CITY") City that the USPS assigned to this PCODE. An asterisk
 "*" indicates which city is PREFERRED (DEFAULT).  XIP(n"CITY KEY") USPS's
 assigned city key.  XIP(n,"CITY ABBREVIATION") USPS's assigned abbreviation.  
 XIP(n,"COUNTY") County associated with this PCODE.  XIP(n,"COUNTY POINTER")
 Pointer to the county in File #5.13.  XIP(n,"FIPS CODE") 5-digit FIPS code
 associated with the county.  XIP(n,"POSTAL CODE") Value used to look up postal
 data.  XIP(n,"PREFERRED CITY KEY") USPS's preferred (DEFAULT) city key.  
 XIP(n,"STATE") State associated with this PCODE.  XIP(n,"STATE POINTER")
 Pointer to the state in File #5.  XIP(n,"UNIQUE KEY") Unique lookup value.  
  
 XIP("ERROR") Errors encountered during lookup.  
  DATE ACTIVATED: JAN 25, 2007

NUMBER: 3619                            IA #: 3619
  DATE CREATED: JUL 11, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGREGDD1                     NAME: GMT SECURITY KEY API
  ID: DGREGDD1
 GENERAL DESCRIPTION:   This API will be used to determine if the user
 attempting to edit a patient's state and county (outside of population based
 on Address Indexing) holds the appropriate security key to make to edit (based
 on Address Indexing business rules).  If the Postal code entered does not
 exist in the Postal Code (#5.12) file, then the security key is not necessary
 for the edit.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMT
KEYWORDS: COUNTY
KEYWORDS: POSTAL
COMPONENT/ENTRY POINT: $$KEY
 COMPONENT DESCRIPTION:   Determine if a security key is necessary for editing
 a patient's state and county fields.  If it is necessary, then determine if
 this user holds it. If the user holds the security key or if no security key
 is necessary, the function will return a 1.  Otherwise, it will return a 0.  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   DUZ - ien for the #200 file of the user 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN - ien of the #2 file for the patient 
VARIABLES: $$KEY                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the value returned from the extrinsic
 function call.  If the user holds the correct security key or if no security
 key is necessary to perform this fuction, the function will return a 1. 
 Otherwise, it will return a 0.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: FEE BASIS
SUBSCRIBING PACKAGE: INTEGRATED PATIENT FUNDS
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
SUBSCRIBING PACKAGE: HINQ

NUMBER: 3620                            IA #: 3620
  DATE CREATED: JUL 15, 2002
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORCFLAG                      NAME: ORCFLAG
  ID: ORCFLAG
 GENERAL DESCRIPTION:   This agreement documents an interactive entry point
 that allows an order to be flagged or unflagged.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN1(ORIFN)
 COMPONENT DESCRIPTION:   This interactive entry point allows access to the
 CPRS actions to flag and unflag an order, from outside of CPRS; the user will
 be prompted to enter a reason for un/flagging the order, as well as a user who
 should receive an alert to review the order.  No output is returned from this 
 call, the order is simply updated in the Orders file #100.  
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Order number in the form "D0;D1", where D0 is the IEN
 in the Orders file #100 and D1 is the IEN of the current Order Action in the
 order's subfile #100.008.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   added 3/31/2008 prompted change to controlled from
 private 

NUMBER: 3621                            IA #: 3621
  DATE CREATED: JUL 17, 2002
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSSHUIDG                     NAME: Data updates
  ID: PSSHUIDG
 GENERAL DESCRIPTION:   In support of the Hawaii DoD project, Pharmacy Data
 Management needs to know when changes are made to entries in the DRUG file
 (#50).  National Drug File data updates make changes to entries in this file. 
 To meet this need, NDF requests permission to call routine PSSHUIDG at entry
 point PSN.  The array ^TMP($J,"^",IEN where IEN is the internal entry number
 in the DRUG file (#50) wil be sent to this entry point.  The matching and
 unmatching processes also make changes to the drug file that need to be sent
 to PDM.  To this end, NDF requests permission to call routine PSSHUIDG at
 entry point DRG with the variable PSNB (if an entry is being matched) or DA
 (if an entry is being unmatched) representing the internal entry number in the
 drug file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PSN
VARIABLES: global TMP($J,               TYPE: Input
 VARIABLES DESCRIPTION:   
  ^TMP($J,"^",IEN) is the array of entries in file 50 that have been edited.  
COMPONENT/ENTRY POINT: DRG
VARIABLES: PSNB                         TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of an entry in file 50.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of an entry in file 50.  
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
  ISC: Birmingham
 SUBSCRIBING DETAILS:   NDF data updates will make a call to %ZTLOAD to queue
 PSN^PSSHUIDG and pass in ^TMP($J,"^" via ZTSAVE.  Matching and unmatching will
 make a call to DRG^PSSHUIDG(DA).  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: CMOP

NUMBER: 3622                            IA #: 3622
  DATE CREATED: SEP 30, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA 3622 - IMAGING 
 GENERAL DESCRIPTION:   Text Integration Utilities developers give permission
 to the VistA Imaging application to copy the TIUSRVPL, TIULC1 and TIULS
 routines into their Imaging gateways. These routines will not be renamed or
 modified at the destination.  
  
 Routine PNAME^TIULC1 is used by the output transform on field .01 (DOCUMENT
 TYPE) of file 8925 (TIU DOCUMENT).  This module will also execute
 $$MIXED^TIULS.  
  STATUS: Active
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Imaging will place a copy of routines TIUSRVPL, TIULC1,
 and TIULS into a transport global to be downloaded into the Imaging gateways.
 The routines are used by Imaging to store Image pointers in the Text
 Integration Utilities package. 
  
 Imaging is also requesting the following information to be provided on each
 released patch to the aforementioned 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 version of this TIU routine (TIUSRVPL) as well as MAS and Radiology
 routines to be copied to the gateway systems." 

NUMBER: 3623                            IA #: 3623
  FILE NUMBER: .46                      GLOBAL ROOT: DIST(.46,
  DATE CREATED: JUL 23, 2002            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3623
  ID: DIST(.46,
 GENERAL DESCRIPTION:   DSS is granted permission to export the INPUT TEMPLATE
 file via KIDS with a single entry.  This entry is used when importing data
 into the DSS Department Table.  This is a one time agreement.  Patch number is
 ECX*3.0.45.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 3624                            IA #: 3624
  DATE CREATED: JUL 23, 2002
  CUSTODIAL PACKAGE: ENROLLMENT APPLICATION SYSTEM
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: EASWTAPI                     NAME: PATIENT ENROLLMENT DATE
  ID: EASWTAPI
 GENERAL DESCRIPTION:   This IA is between EAS and Scheduling as a temporary IA
 in relation to the Clinic Waiting Time report.  This report requires the
 correct enrollment date from the PATIENT ENROLLMENT File, #27.11.  Until 
 corrections and data cleanup are accomplished on both the Health Eligibility
 Center and VistA sides, this IA will need to remain in effect.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ENROLLMENT DATE
KEYWORDS: PATIENT ENROLLMENT
COMPONENT/ENTRY POINT: $$ENROLL(DFN)
 COMPONENT DESCRIPTION:   This call will return the correct Enrollment Date and
 associated data from the PATIENT ENROLLMENT File, #27.11, based on current
 buisness rules in place.  This call is a result of the mandated Clinic Waiting
 Time Report.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN (Internal Entry Number) in the
 PATIENT File, #2, for the patient for which the correct enrollment date is
 being requested.  
VARIABLES: $$ENROLL                     TYPE: Output
 VARIABLES DESCRIPTION:   The return value of this call will be: 
  
    If no enrollment date can be determined: 0 (zero) 
  
    If success: 1 ^ IEN ^ Enrollment Date ^ Type 
  
                    1 - Success 
                  IEN - Internal Entry Number in file #27.11 for the date 
      Enrollment Date - Date in internal VA FileMan format 
                 Type - "E" Date returned is Enrollment date, Field #.1 
                        "A" Date returned is Application date, Field #.01 
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 3625                            IA #: 3625
  FILE NUMBER: 405                      GLOBAL ROOT: DGPM(
  DATE CREATED: JUL 23, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA3625
  ID: DGPM(
GLOBAL REFERENCE: DGPM(D0,0)
FIELD NUMBER: .04                       FIELD NAME: TYPE OF MOVEMENT
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: WARD LOCATION
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Withdrawn

NUMBER: 3626                            IA #: 3626
  FILE NUMBER: 1                        GLOBAL ROOT: DD(
  DATE CREATED: JUL 24, 2002            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3626
  ID: DD(
GLOBAL REFERENCE: DD(300.11,20.51,9) => WRITE ACCESS
 GLOBAL DESCRIPTION:   The current write access in the #20.51 field of the
 #300.11 file is set to the "^" character, which prevent any updates (including
 programmer updates).  This access will be changed to "@" with the following
 code: S ^DD(300.11,20.51,9)="@" 
 GENERAL DESCRIPTION:   This integration agreement is necessary in order to
 facilitate a change to the write access on field #20.51 (ADDRESS CHANGE DATE)
 of the #300.11 (VIVA) file.  The write access is currently set to the "^"
 character, and will be changed to "@", in order to allow the filing of new
 data into the field.  
  
 The PRE^IVMB686 tag will be used for this purpose.  The patch number, 
 IVMB*2*686, will only be installed on the HEC system, and this request is for 
 a one-time use only. The Fileman team provided preliminary approval of this
 request.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ADDRESS INDEXING
KEYWORDS: FILEMAN
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  ISC: Albany
 SUBSCRIBING DETAILS:   This request is for 1 time use only, and will occur on
 the HEC system.  

NUMBER: 3627                            IA #: 3627
  FILE NUMBER: 4                        GLOBAL ROOT: DIC(4,
  DATE CREATED: JUL 26, 2002            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: 'D' X-REF                       ID: DIC(4,
GLOBAL REFERENCE: DIC(4,'D'
 GENERAL DESCRIPTION:   
  MPI/PD has permission to execute a $ORDER direct global read 
  of the 'D' Cross Reference on the INSTITUTION (#4) file.  This 
  is done specifically to identify existing anomalies with the HL 
  links used for MPI/PD messaging (e.g., multiple "D" cross 
  references in the file for a station number).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham
SUBSCRIBING PACKAGE: NDBI

NUMBER: 3628                            IA #: 3628
  DATE CREATED: JUL 30, 2002            CUSTODIAL PACKAGE: SURGERY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: SROVAR                       NAME: SET VARIABLES FOR OPERATION REPORT
  ID: SROVAR
 GENERAL DESCRIPTION:   DBIA for AMIE II (Automated Medical Information
 Exchange) to use SET^SROVAR routine in a remote procedure to run Surgery
 Operation Report. Integration Agreement will be only until the Electronic
 Signature for Operative Reports patch (SR*3*100) is installed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2002
KEYWORDS: SROVAR
COMPONENT/ENTRY POINT: SET
 COMPONENT DESCRIPTION:   SET^SROVAR will be used to set site parameters for
 the Operation Report.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN - Patient identification number 
VARIABLES: SRTN                         TYPE: Input
 VARIABLES DESCRIPTION:   
  
 SRTN - Surgery Case Number 
VARIABLES: SRSITE                       TYPE: Input
 VARIABLES DESCRIPTION:   SRSITE equals the pointer from the SURGERY SITE
 PARAMETER file 
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany
 SUBSCRIBING DETAILS:   The Opertion Report is currently being access through
 AMIE II (Automated Medical Information Exchange) report menu options. AMIE
 would like a DBAI to use SET^SROVAR routine in a remote procedure for CAPRI
 GUI to set the site parameters for the Operation Report.   
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI

NUMBER: 3629                            IA #: 3629
  DATE CREATED: JUL 30, 2002            CUSTODIAL PACKAGE: SURGERY
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: SROPRPT1                     NAME: PRINT OPERATION REPORT
  ID: SROPRPT1
 GENERAL DESCRIPTION:   DBIA for AMIE II (Automated Medical Information
 Exchange) to use ^SROPRPT1 routine in a remote procedure to print Surgery
 Operation Report. Integration Agreement will be only until the Electronic
 Signature for Operative Reports patch (SR*3*100) is installed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2002
KEYWORDS: SROPRPT1
COMPONENT/ENTRY POINT: SROPRPT1
 COMPONENT DESCRIPTION:   Print the Surgery Case Operation Report 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN : Patient Identification Number 
VARIABLES: SRTN                         TYPE: Input
 VARIABLES DESCRIPTION:   SRTN : Surgery Case Number 
VARIABLES: SRSITE                       TYPE: Input
 VARIABLES DESCRIPTION:   SRSITE : Site Parameter 
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany
 SUBSCRIBING DETAILS:   The Opertion Report is currently being access through
 AMIE II (Automated Medical Information Exchange) report menu options. AMIE
 would like a DBAI to use SROPRPT1 routine in a remote procedure for CAPRI GUI
 to print surgery case operation report.  
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 3630                            IA #: 3630
  DATE CREATED: JUL 30, 2002            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFCQRY
  NAME: VAFCQRY APIs                    ID: VAFCQRY
 GENERAL DESCRIPTION:   MPIF and RG would like to call the generic segment
 builders for version 2.4 messages for the PID, EVN and PD1 segments.  
  STATUS: Active
COMPONENT/ENTRY POINT: BLDEVN
 COMPONENT DESCRIPTION:   The entry point builds the EVN segment via version
 2.4 including the Treating Facility last treatment date and event reason.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN - Internal Entry Number of the patient in the
 Patient (#2) file.  
VARIABLES: SEQ                          TYPE: Input
 VARIABLES DESCRIPTION:   SEQ - variable consisting of sequence numbers
 delimited by commas that will be used to build the message.  
VARIABLES: EVN                          TYPE: Input
 VARIABLES DESCRIPTION:   EVN (passed by reference) - array location to place
 EVN segment result, the array can have existing values when passed.  
VARIABLES: HL                           TYPE: Input
 VARIABLES DESCRIPTION:   HL - array that contains the necessary HL variables
 (init^hlsub) 
VARIABLES: EVR                          TYPE: Input
 VARIABLES DESCRIPTION:   EVR - event reason that triggered this message.  
VARIABLES: ERR                          TYPE: Input
 VARIABLES DESCRIPTION:   ERR - array that is used to return an error.  
COMPONENT/ENTRY POINT: BLDPD1
 COMPONENT DESCRIPTION:   This entry point will build the version 2.4 PD1
 segment.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN - internal entry number of the patient in the
 PATIENT (#2) file.  
VARIABLES: SEQ                          TYPE: Input
 VARIABLES DESCRIPTION:   SEQ - variable consisting of sequence numbers
 delimited by commas that will be used to build the message.  
VARIABLES: PD1                          TYPE: Input
 VARIABLES DESCRIPTION:   PD1 (passed by reference) - array location to place
 PD1 segment result, the array can have existing values when passed.  
VARIABLES: HL                           TYPE: Input
 VARIABLES DESCRIPTION:   HL - array that contains the necessary HL variables
 (init^hlsub) 
VARIABLES: ERR                          TYPE: Input
 VARIABLES DESCRIPTION:   ERR - array that is used to return an error.  
COMPONENT/ENTRY POINT: BLDPID
 COMPONENT DESCRIPTION:   This entry point will build the version 2.4 PID
 segment.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN - internal entry number of the patient in the
 PATIENT (#2) file.  
VARIABLES: CNT                          TYPE: Input
 VARIABLES DESCRIPTION:   CNT - value to be place in PID seq#1 (SET ID) 
VARIABLES: SEQ                          TYPE: Input
 VARIABLES DESCRIPTION:   SEQ - variable consisting of sequence numbers
 delimited by commas that will be used to build the message.  
  
 "ALL" can be passed to get all available fields in the PID segment that are
 available.  This is the default.  
VARIABLES: PID                          TYPE: Input
 VARIABLES DESCRIPTION:   PID (passed by reference) - array location to place
 PID segment result, the array can have existing values when passed.  
VARIABLES: HL                           TYPE: Input
 VARIABLES DESCRIPTION:   HL - array that contains the necessary HL variables
 (init^hlsub) 
VARIABLES: ERR                          TYPE: Input
 VARIABLES DESCRIPTION:   ERR - array that is used to return an error.  
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   ADDED 3/19/09 
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 9/12/22, effective with DSSO*2.0*5 to call
 Registration routine BLDPID^VAFCQRY to create a PID segment during the Record
 of Pros Appliance/Repair (#660) extract process which is used in determining 
 whether a patient has received duplicate Prosthetic HCPCS's.  

NUMBER: 3631                            IA #: 3631
  DATE CREATED: JUL 30, 2002            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VBECA5A
  NAME: VBECS/Surgery API               ID: VBECA5A
 GENERAL DESCRIPTION:   The VBECA5A API has been created to allow the Surgery
 package to convert the existing pointer fields  used to list available Blood
 Products contained in the Blood Product file (#66), with a free text field. 
 The transition of the Blood Bank system from the existing M based system to a 
 .NET/SQL based system will eliminate the ability of the Surgery package to
 access the Blood Product data using the current method.  The affected files
 and fields are: 
     File                             Field 
     SURGERY (#130)                   REQ BLOOD KIND (.01 field in 
                                                      sub-file #130.14) 
     SURGERY SITE PARAMETERS (#133)   DEFAULT BLOOD REQUEST 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ITRAN
 COMPONENT DESCRIPTION:   INPUT DEFINITION: 
  
 X = The variable X is the input from the user.  X will be used to attempt to
 match a Blood Product returned from Blood Bank that will be passed to the
 Surgery package for use in REQ BLOOD KIND field in the Surgery file(#130) and
 the DEFAULT BLOOD REQUEST field in the Surgery Site Parameter (#133) file.  
  
 OUTPUT DEFINITION: 
  
 The variable X will be returned as the selected Blood Product based on the 
 user supplied input.  If no valid input is available, X will be not be 
 returned.  
COMPONENT/ENTRY POINT: LIST66
 COMPONENT DESCRIPTION:   This is the executable help for the REQ BLOOD KIND
 field in the SURGERY file.  
COMPONENT/ENTRY POINT: OUT66
 COMPONENT DESCRIPTION:   This is the executable help for the DEFAULT BLOOD
 COMPONENT field in the SURGERY SITE PARAMETERS file.  
SUBSCRIBING PACKAGE: SURGERY

NUMBER: 3632                            IA #: 3632
  DATE CREATED: AUG 05, 2002
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORX8                         NAME: Use of $$ES,$$AND api's
  ID: ORX8
 GENERAL DESCRIPTION:   This agreement documents the api's $$ES^ORX8, which
 returns the signature status of an order, and $$AND^ORX8, which returns a true
 or false value if all conjunctions in the medication order are "AND".  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: $$ES
KEYWORDS: $$AND
COMPONENT/ENTRY POINT: $$ES(ORIFN)
 COMPONENT DESCRIPTION:   This api will return the signature status of an
 order.  
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Order number in the form "D0;D1", where D0 is the IEN
 in the Orders file #100 and D1 is the IEN of the desired Order Action in the
 order's subfile #100.008.  
VARIABLES: $$ES                         TYPE: Output
 VARIABLES DESCRIPTION:   The result of the extrinsic function will be one of
 the following: 
  -1 = invalid order# 
  "" = no signature required 
   0 = not signed (needs ES) 
   1 = electronically or digitally signed 
   2 = signed on chart 
   3 = corrected or canceled order (ES not needed) 
COMPONENT/ENTRY POINT: $$AND(ORIFN)
 COMPONENT DESCRIPTION:   This api will return true or false, if all
 conjunctions between doses in a medication order are "AND" or not.  
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Order IEN in the Orders file #100 
VARIABLES: $$AND                        TYPE: Output
 VARIABLES DESCRIPTION:   This will return a 1 if all conjunctions entered to
 created this order are "AND", or if none are present; if a conjunction other
 than "AND" is found, then this will return a 0.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham

NUMBER: 3633                            IA #: 3633
  FILE NUMBER: 340                      GLOBAL ROOT: RCD(340,
  DATE CREATED: AUG 05, 2002            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3633
  ID: RCD(340,
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3634                            IA #: 3634
  DATE CREATED: AUG 05, 2002
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MPIF002
  NAME: MPIF002                         ID: MPIF002
 GENERAL DESCRIPTION:   $$GETDFNS(SSN) returns all DFNs for a given SSN.  
  STATUS: Active
COMPONENT/ENTRY POINT: GETDFNS
 COMPONENT DESCRIPTION:   Find ALL DFNs for a given SSN 
VARIABLES: SSN                          TYPE: Input
 VARIABLES DESCRIPTION:   Social Security Number being used to find all Patient
 (#2) file entries with this SSN.  
VARIABLES: LIST                         TYPE: Output
 VARIABLES DESCRIPTION:   LIST=$$GETDFNS^MPIF002(SSN) 
  
 LIST is returned as DFN1^DFN2^.... or -1^error message 
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 3635                            IA #: 3635
  FILE NUMBER: 342.1                    GLOBAL ROOT: RC(342.1
  DATE CREATED: AUG 06, 2002            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3635
  ID: RC(342.1
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3636                            IA #: 3636
  FILE NUMBER: 430                      GLOBAL ROOT: PRCA(430
  DATE CREATED: AUG 06, 2002            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3636
  ID: PRCA(430
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3637                            IA #: 3637
  DATE CREATED: AUG 06, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGMTUTL                      NAME: DBIA3637
  ID: DGMTUTL
 GENERAL DESCRIPTION:   Means Test generic utilities routine.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$PA(DGMTI)
 COMPONENT DESCRIPTION:   Determines if the Pending Adjudication is for MT or
 GMT.  
  
 Extrinsic function, output returns "MT", "GMT", or "" if it can't be 
 determined.  
VARIABLES: DGMTI                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Annual Means Test file #408.31 
VARIABLES: $$PA                         TYPE: Output
 VARIABLES DESCRIPTION:   returns "MT", "GMT" or "" if it can't be determined 
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 3638                            IA #: 3638
  FILE NUMBER: 161.2                    GLOBAL ROOT: FBAAV(
  DATE CREATED: AUG 07, 2002            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3638
  ID: FBAAV(
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  
 M Data Extractor is on the TRM and approved with constraints.  However no 
 routines in the M Data Extractor (DES) namespace were found.  No documentation
 in the VDL and no entries in the National Patch Module. A search of Fee Basis
 routines did not find any calls to routines in the DES namespace.   The ICR
 description  states the ICR was created in 2002 as a temporary ICR for CoreFLS
 and expected to be retired after data was extracted from the sites.  Based on
 on the description in the ICR and recommendations by reviewers, this ICR was
 retired on 2/26/18.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: FEB 26, 2018
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3639                            IA #: 3639
  FILE NUMBER: 4                        GLOBAL ROOT: DIC(4
  DATE CREATED: AUG 07, 2002            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3639
  ID: DIC(4
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3640                            IA #: 3640
  FILE NUMBER: 20                       GLOBAL ROOT: VA(20
  DATE CREATED: AUG 07, 2002            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3640
  ID: VA(20
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3641                            IA #: 3641
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: AUG 07, 2002            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3641
  ID: VA(200
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3642                            IA #: 3642
  FILE NUMBER: 36                       GLOBAL ROOT: DIC(36
  DATE CREATED: AUG 07, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3642
  ID: DIC(36
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3643                            IA #: 3643
  FILE NUMBER: 450                      GLOBAL ROOT: PRSPC(
  DATE CREATED: AUG 07, 2002            CUSTODIAL PACKAGE: PAID
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3643
  ID: PRSPC(
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3644                            IA #: 3644
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: AUG 07, 2002            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3644
  ID: DPT(
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3645                            IA #: 3645
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT(
  DATE CREATED: AUG 07, 2002            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  USAGE: Private                        TYPE: File
  NAME: DBIA3645                        ID: ICPT(
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3646                            IA #: 3646
  DATE CREATED: MAY 25, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGSEC4                       NAME: EMPLOYEE ELIGIBILITY CODE CHECK
  ID: DGSEC4                            STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: DGSEC4
KEYWORDS: EMPLOYEE
COMPONENT/ENTRY POINT: $$EMPL(DFN,DGCHELIG)
 COMPONENT DESCRIPTION:   This entry point will determine if either the
 patient's primary and/or secondary eligibility codes are set to EMPLOYEE,
 depending on the parameter passed (P-primary, S-secondary, or both).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN = Patient (#2) file IEN.  
VARIABLES: DGCHELIG                     TYPE: Input
 VARIABLES DESCRIPTION:   DGCHELIG is an optional parameter that determines
 which eligibility code is checked.  If left undefined or if an illegal value
 is passed, the value will be defaulted to "PS".  Value of the parameter can
 contain any combination of the following characters: 
     "P" - check primary eligibility code 
     "S" - check secondary eligibility codes 
VARIABLES: $$EMPL                       TYPE: Output
 VARIABLES DESCRIPTION:   
  1  -- Patient has EMPLOYEE as an eligibility code 
  0  -- Patient doesn't have EMPLOYEE as an eligibility code 
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   11/3/2006 - Imaging would like to subscribe to DBIA
 3646 to pick up the employee flag for HL7 messaging.  

NUMBER: 3647                            IA #: 3647
  DATE CREATED: NOV 07, 2003
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMVPXRM                      NAME: GMVPXRM
  ID: GMVPXRM                           STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN(.GMVDATA,GMVIEN,GMVIB)
 COMPONENT DESCRIPTION:   This entry point returns either the internal or both
 the internal and external values (pieces 1 and 2 respectively) for the
 following fields of the FILE 120.5 entry selected: 
  
  GMVDATA(1)=.01 (DATE/TIME VITALS TAKEN) 
  GMVDATA(2)=.02 (PATIENT) 
  GMVDATA(3)=.03 (VITAL TYPE) 
  GMVDATA(4)=.04 (DATE/TIME VITALS ENTERED) 
  GMVDATA(5)=.05 (HOSPITAL LOCATION) 
  GMVDATA(6)=.06 (ENTERED BY) 
  GMVDATA(7)=1.2 (RATE) 
  GMVDATA(8)=1.4 (SUPPLEMENTAL O2) 
  GMVDATA(9)=2   (ENTERED IN ERROR) 
  GMVDATA(10)=3  (ERROR ENTERED BY) 
  GMVDATA(11,n)=4 (REASON ENTERED IN ERROR)  <--multiple 
  GMVDATA(12,n)=5 (QUALIFIER)                <--multiple 
  
 If the lookup failed then: GMVDATA(1)=-1^error text.  
  
 This is an example of returning internal values only. The array name is 
 GMVDATA which is passed by reference. The record number is 394.  
  
  > D EN^GMVPXRM(.GMVDATA,394,"I") 
  > ZW GMVDATA 
  > GMVDATA(1)=3020805.2324 
  > GMVDATA(2)=67 
  > GMVDATA(3)=2 
  > GMVDATA(4)=3020805.232531 
  > GMVDATA(5)=1 
  > GMVDATA(6)=547 
  > GMVDATA(7)=100.1 
  > GMVDATA(8)= 
  > GMVDATA(9)=1 
  > GMVDATA(10)=547 
  > GMVDATA(11,1)=4 
  > GMVDATA(12,1)=6 
  
 This is an example of returning internal and external values. The array name
 is GMVDATA which is passed by reference. The record number is 394.  
  
  > D EN^GMVPXRM(.GMVDATA,394,"B") 
  > GMVDATA(1)=3020805.2324^AUG 05, 2002@23:24 
  > GMVDATA(2)=67^GMVTEST,PATIENTSIXTYSEVEN 
  > GMVDATA(3)=2^TEMPERATURE 
  > GMVDATA(4)=3020805.232531^AUG 05, 2002@23:25:31 
  > GMVDATA(5)=1^2AS 
  > GMVDATA(6)=547^GMVUSER,NURSEFIVEFOURSEVEN 
  > GMVDATA(7)=100.1^100.1 
  > GMVDATA(8)=^ 
  > GMVDATA(9)=1^YES 
  > GMVDATA(10)=547^GMVUSER,NURSEFIVEFOURSEVEN 
  > GMVDATA(11,1)=4^INVALID RECORD 
  > GMVDATA(12,1)=6^ORAL 
VARIABLES: .GMVDATA                     TYPE: Both
 VARIABLES DESCRIPTION:   The first variable in the parameter list. It
 specifies the name of the array to return the information in and is passed by
 reference. This variable is required.  
VARIABLES: GMVIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   The second variable in the parameter list. It is the
 internal entry number of the FILE 120.5 entry. It is required.  
VARIABLES: GMVIB                        TYPE: Input
 VARIABLES DESCRIPTION:   The third variable in the parameter list. It is
 optional. 
  
 Use an uppercase letter I (i.e., "I") to return only the internal values of
 the entry.  
  
 Use an uppercase letter B (i.e., "B") to return both the internal and external
 values of the entry. "B" is the default. If GMVIB is not "I" or "B", then "B"
 is used.  
COMPONENT/ENTRY POINT: VITALS
 COMPONENT DESCRIPTION:   This entry point is for use by the Clinical Reminders
 package to re-index the ACR cross-reference nodes for FILE 120.5.  
  a) This entry point kills the ACR cross-reference nodes for FILE 120.5 
     i.e., ^PXRMINDX(120.5).  
  b) Re-builds the ACR cross-reference nodes.  
  c) Calls the Clinical Reminders package to generate a mail message 
     summarizing the rebuilding of the ACR cross-reference.  
  
 There are no input or output variables for this entry point.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   added 10/10/08 
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

NUMBER: 3648                            IA #: 3648
  FILE NUMBER: 6911                     GLOBAL ROOT: ENG(6911
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3648
  ORIGINAL NUMBER: 3648                 ID: ENG(6911
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3649                            IA #: 3649
  FILE NUMBER: 6912                     GLOBAL ROOT: ENG('MFG'
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3649
  ORIGINAL NUMBER: 3648                 ID: ENG('MFG'
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 8/15/18 - retrieves fields .01;1;2;3;4;5;6;7 

NUMBER: 3650                            IA #: 3650
  FILE NUMBER: 6914                     GLOBAL ROOT: ENG(6914
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3650
  ORIGINAL NUMBER: 3648                 ID: ENG(6914
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3651                            IA #: 3651
  FILE NUMBER: 6914.1                   GLOBAL ROOT: ENG(6914.1
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3651
  ORIGINAL NUMBER: 3648                 ID: ENG(6914.1
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the  data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3652                            IA #: 3652
  FILE NUMBER: 6914.2                   GLOBAL ROOT: ENG(6914.2
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3652
  ORIGINAL NUMBER: 3648                 ID: ENG(6914.2
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3653                            IA #: 3653
  FILE NUMBER: 6914.4                   GLOBAL ROOT: ENG(6914.4
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3653
  ORIGINAL NUMBER: 3648                 ID: ENG(6914.4
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3654                            IA #: 3654
  FILE NUMBER: 6915.9                   GLOBAL ROOT: ENG(6915.9
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3654
  ORIGINAL NUMBER: 3648                 ID: ENG(6915.9
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3655                            IA #: 3655
  FILE NUMBER: 6917                     GLOBAL ROOT: ENCSN(6917
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3655
  ORIGINAL NUMBER: 3648                 ID: ENCSN(6917
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3656                            IA #: 3656
  FILE NUMBER: 6920                     GLOBAL ROOT: ENG(6920
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3656
  ORIGINAL NUMBER: 3648                 ID: ENG(6920
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3657                            IA #: 3657
  FILE NUMBER: 6920.1                   GLOBAL ROOT: ENG(6920.1
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3657
  ORIGINAL NUMBER: 3648                 ID: ENG(6920.1
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3658                            IA #: 3658
  FILE NUMBER: 6921                     GLOBAL ROOT: DIC(6921
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3658
  ORIGINAL NUMBER: 3658                 ID: DIC(6921
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 8/15/18: Access Work Center Code File ^DIC(6921),
 fields .01 and WORK CENTER CODE (35.5).  

NUMBER: 3659                            IA #: 3659
  FILE NUMBER: 6922                     GLOBAL ROOT: DIC(6922
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3659
  ORIGINAL NUMBER: 3658                 ID: DIC(6922
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: CoreFLS
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3660                            IA #: 3660
  FILE NUMBER: 6926                     GLOBAL ROOT: ENG('KEY'
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3660
  ORIGINAL NUMBER: 3658                 ID: ENG('KEY'
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3661                            IA #: 3661
  FILE NUMBER: 6927                     GLOBAL ROOT: ENG('LK'
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3661
  ORIGINAL NUMBER: 3658                 ID: ENG('LK'
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3662                            IA #: 3662
  FILE NUMBER: 6928                     GLOBAL ROOT: ENG('SP'
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3662
  ORIGINAL NUMBER: 3658                 ID: ENG('SP'
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3663                            IA #: 3663
  FILE NUMBER: 6928.1                   GLOBAL ROOT: ENG(6928.1
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3663
  ORIGINAL NUMBER: 3658                 ID: ENG(6928.1
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 8/15/18. Access ENG SPACE FUNCTIONS (6928.1),
 Field NAME (.01).  

NUMBER: 3664                            IA #: 3664
  FILE NUMBER: 6928.2                   GLOBAL ROOT: ENG(6928.2
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3664
  ORIGINAL NUMBER: 3658                 ID: ENG(6928.2
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3665                            IA #: 3665
  FILE NUMBER: 6928.3                   GLOBAL ROOT: ENG(6928.3
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3665
  ORIGINAL NUMBER: 3658                 ID: ENG(6928.3
GLOBAL REFERENCE: ENG(6928.3,'D'
 GLOBAL DESCRIPTION:   'D' cross reference for field DIVISION (#.2) 
 GENERAL DESCRIPTION:   ICR originally created for MDE to pull data from this
 file to support populating COREFLS. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: Above PAR
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   MDE no longer needs this ICR because COREFLS
 development was discontinued.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 8/16/18. ENG BUILDING (6928.3), Field Name (.01),
 used in RPC: DSIYBC04 ENGSPACE LIST to get the Name when printing a label.  
  DATE ACTIVATED: SEP 12, 2022

NUMBER: 3666                            IA #: 3666
  FILE NUMBER: 6929                     GLOBAL ROOT: ENG('EMP'
  DATE CREATED: AUG 12, 2002            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3666
  ORIGINAL NUMBER: 3658                 ID: ENG('EMP'
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3667                            IA #: 3667
  FILE NUMBER: 413                      GLOBAL ROOT: PRCN(413
  DATE CREATED: AUG 12, 2002
  CUSTODIAL PACKAGE: EQUIPMENT/TURN-IN REQUEST
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3667-A
  ORIGINAL NUMBER: 3667                 ID: PRCN(413
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3668                            IA #: 3668
  FILE NUMBER: 413.1                    GLOBAL ROOT: PRCN(413.1
  DATE CREATED: AUG 12, 2002
  CUSTODIAL PACKAGE: EQUIPMENT/TURN-IN REQUEST
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3667-B
  ORIGINAL NUMBER: 3667                 ID: PRCN(413.1
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3669                            IA #: 3669
  FILE NUMBER: 413.2                    GLOBAL ROOT: PRCN(413.2
  DATE CREATED: AUG 12, 2002
  CUSTODIAL PACKAGE: EQUIPMENT/TURN-IN REQUEST
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3667-C
  ORIGINAL NUMBER: 3667                 ID: PRCN(413.2
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3670                            IA #: 3670
  FILE NUMBER: 413.3                    GLOBAL ROOT: PRCN(413.3
  DATE CREATED: AUG 12, 2002
  CUSTODIAL PACKAGE: EQUIPMENT/TURN-IN REQUEST
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3667-D
  ORIGINAL NUMBER: 3667                 ID: PRCN(413.3
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3671                            IA #: 3671
  FILE NUMBER: 413.5                    GLOBAL ROOT: PRCN(413.5
  DATE CREATED: AUG 12, 2002
  CUSTODIAL PACKAGE: EQUIPMENT/TURN-IN REQUEST
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3667-E
  ORIGINAL NUMBER: 3667                 ID: PRCN(413.5
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3672                            IA #: 3672
  FILE NUMBER: 410.2                    GLOBAL ROOT: PRCS(410.2
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3672
  ID: PRCS(410.2
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3673                            IA #: 3673
  FILE NUMBER: 410.4                    GLOBAL ROOT: PRCS(410.4
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3673
  ID: PRCS(410.4
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3674                            IA #: 3674
  FILE NUMBER: 410.5                    GLOBAL ROOT: PRCS(410.5
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3674
  ID: PRCS(410.5
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3675                            IA #: 3675
  FILE NUMBER: 410.6                    GLOBAL ROOT: PRCS(410.6
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3675
  ID: PRCS(410.6
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3676                            IA #: 3676
  FILE NUMBER: 410.7                    GLOBAL ROOT: PRCS(410.7
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3676
  ID: PRCS(410.7
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3677                            IA #: 3677
  FILE NUMBER: 410.8                    GLOBAL ROOT: PRCS(410.8
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3677
  ID: PRCS(410.8
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3678                            IA #: 3678
  FILE NUMBER: 411                      GLOBAL ROOT: PRC(411
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3678
  ID: PRC(411
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3679                            IA #: 3679
  FILE NUMBER: 420                      GLOBAL ROOT: PRC(420
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3679
  ID: PRC(420
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3680                            IA #: 3680
  FILE NUMBER: 420.2                    GLOBAL ROOT: PRCD(420.2
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3680
  ID: PRCD(420.2
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   ADDED 4/3/08 

NUMBER: 3681                            IA #: 3681
  FILE NUMBER: 420.6                    GLOBAL ROOT: PRCD(420.6
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3681
  ID: PRCD(420.6
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3682                            IA #: 3682
  FILE NUMBER: 420.7                    GLOBAL ROOT: PRCF(420.7
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3682
  ID: PRCF(420.7
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3683                            IA #: 3683
  FILE NUMBER: 420.8                    GLOBAL ROOT: PRCD(420.8
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3683
  ID: PRCD(420.8
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3684                            IA #: 3684
  FILE NUMBER: 421                      GLOBAL ROOT: PRCF(421
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3684
  ID: PRCF(421
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3685                            IA #: 3685
  FILE NUMBER: 421.1                    GLOBAL ROOT: PRCF(421.1
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3685
  ID: PRCF(421.1
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3686                            IA #: 3686
  FILE NUMBER: 421.5                    GLOBAL ROOT: PRCF(421.5
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3686
  ID: PRCF(421.5
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3687                            IA #: 3687
  FILE NUMBER: 424                      GLOBAL ROOT: PRC(424
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3687
  ID: PRC(424
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3688                            IA #: 3688
  FILE NUMBER: 424.1                    GLOBAL ROOT: PRC(424.1
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3688
  ID: PRC(424.1
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3689                            IA #: 3689
  FILE NUMBER: 440.2                    GLOBAL ROOT: PRC(440.2
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3689
  ID: PRC(440.2
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3690                            IA #: 3690
  FILE NUMBER: 440.5                    GLOBAL ROOT: PRC(440.5
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3690
  ID: PRC(440.5
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3691                            IA #: 3691
  FILE NUMBER: 440.6                    GLOBAL ROOT: PRCH(440.6
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3691
  ID: PRCH(440.6
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3692                            IA #: 3692
  FILE NUMBER: 440.7                    GLOBAL ROOT: PRCH(440.7
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3692
  ID: PRCH(440.7
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3693                            IA #: 3693
  FILE NUMBER: 441.2                    GLOBAL ROOT: PRC(441.2
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3693
  ID: PRC(441.2
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3694                            IA #: 3694
  FILE NUMBER: 441.3                    GLOBAL ROOT: PRC(441.3
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3694
  ID: PRC(441.3
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MDE
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3695                            IA #: 3695
  FILE NUMBER: 441.6                    GLOBAL ROOT: PRCD(441.6
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3695
  ID: PRCD(441.6
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3696                            IA #: 3696
  FILE NUMBER: 441.7                    GLOBAL ROOT: PRC(441.7
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3696
  ID: PRC(441.7
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3697                            IA #: 3697
  FILE NUMBER: 442                      GLOBAL ROOT: PRC(442
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3697
  ID: PRC(442
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3698                            IA #: 3698
  FILE NUMBER: 442.7                    GLOBAL ROOT: PRC(442.7
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3698
  ID: PRC(442.7
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3699                            IA #: 3699
  FILE NUMBER: 442.8                    GLOBAL ROOT: PRC(442.8
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3699
  ID: PRC(442.8
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3700                            IA #: 3700
  FILE NUMBER: 443                      GLOBAL ROOT: PRC(443
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3700
  ID: PRC(443
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3701                            IA #: 3701
  FILE NUMBER: 443.4                    GLOBAL ROOT: PRC(443.4
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3701
  ID: PRC(443.4
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3702                            IA #: 3702
  FILE NUMBER: 443.6                    GLOBAL ROOT: PRC(443.6
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3702
  ID: PRC(443.6
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3703                            IA #: 3703
  FILE NUMBER: 443.8                    GLOBAL ROOT: PRC(443.8
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3703
  ID: PRC(443.8
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3704                            IA #: 3704
  FILE NUMBER: 444                      GLOBAL ROOT: PRC(444
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3704
  ID: PRC(444
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3705                            IA #: 3705
  FILE NUMBER: 444.1                    GLOBAL ROOT: PRC(444.1
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3705
  ID: PRC(444.1
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3706                            IA #: 3706
  FILE NUMBER: 445                      GLOBAL ROOT: PRCP(445
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3706
  ID: PRCP(445
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3707                            IA #: 3707
  FILE NUMBER: 445.2                    GLOBAL ROOT: PRCP(445.2
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3707
  ID: PRCP(445.2
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3708                            IA #: 3708
  FILE NUMBER: 445.3                    GLOBAL ROOT: PRCP(445.3
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3708
  ID: PRCP(445.3
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3709                            IA #: 3709
  FILE NUMBER: 445.4                    GLOBAL ROOT: PRCP(445.4
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3709
  ID: PRCP(445.4
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3710                            IA #: 3710
  FILE NUMBER: 445.6                    GLOBAL ROOT: PRCP(445.6
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3710
  ID: PRCP(445.6
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3711                            IA #: 3711
  FILE NUMBER: 445.7                    GLOBAL ROOT: PRCP(445.7
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3711
  ID: PRCP(445.7
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3712                            IA #: 3712
  FILE NUMBER: 445.8                    GLOBAL ROOT: PRCP(445.8
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3712
  ID: PRCP(445.8
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3713                            IA #: 3713
  FILE NUMBER: 446                      GLOBAL ROOT: PRCP(446
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3713
  ID: PRCP(446
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3714                            IA #: 3714
  FILE NUMBER: 446.1                    GLOBAL ROOT: PRCP(446.1
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3714
  ID: PRCP(446.1
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3715                            IA #: 3715
  FILE NUMBER: 446.5                    GLOBAL ROOT: PRCT(446.5
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3715
  ID: PRCT(446.5
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3716                            IA #: 3716
  FILE NUMBER: 446.6                    GLOBAL ROOT: PRCT(446.6
  DATE CREATED: AUG 14, 2002            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3716
  ID: PRCT(446.6
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is short-term and will be
 retired after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3717                            IA #: 3717
  DATE CREATED: AUG 13, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBAECU
  NAME: DBIA3717                        ID: IBAECU
 GENERAL DESCRIPTION:   Integrated Billing API to return the maximum daily
 rates for LTC copayments.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$MAXRATE
 COMPONENT DESCRIPTION:   Determines the maximum daily rate for copayments for
 inpatient and outpatient LTC services.  
VARIABLES: IBDT                         TYPE: Input
 VARIABLES DESCRIPTION:   Effective date for copayment rate 
VARIABLES: $$MAXRATE                    TYPE: Output
 VARIABLES DESCRIPTION:   Piece 1 = outpatient rate Piece 2 = inpatient rate 
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM

NUMBER: 3718                            IA #: 3718
  DATE CREATED: AUG 14, 2002
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: DBIA3718-A
  ORIGINAL NUMBER: 3718
 GENERAL DESCRIPTION:   RPC BROKER CALL TIU SIGN RECORD 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE

NUMBER: 3719                            IA #: 3719
  DATE CREATED: AUG 14, 2002
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: DBIA3718-B
  ORIGINAL NUMBER: 3718
 GENERAL DESCRIPTION:   RPC CALL IS ORWPT APPTLST 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE

NUMBER: 3720                            IA #: 3720
  DATE CREATED: AUG 14, 2002
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: DBIA3718-C
  ORIGINAL NUMBER: 3718
 GENERAL DESCRIPTION:   RPC CALL IS ORWPT ADMITLST 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE

NUMBER: 3722                            IA #: 3722
  DATE CREATED: AUG 14, 2002
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: DBIA3718-E
  ORIGINAL NUMBER: 3718
 GENERAL DESCRIPTION:   RPC CALL IS ORQPT WARD PATIENTS 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   10/27/17-HMP's subscription to this ICR expires on
 10/27/17 when HMP will be shutdown.  HMP*2.0*12 released on 10/17/17 is an
 informational patch outlining the steps for the sites to shut down the
 application.  
  
 CPRS disapproved access to this RPC on 11/3/16. On 10/18/17, HMP stated their
 code was modified to use the DGWPT BYWARD RPC.  However the ORQPT WARD
 PATIENTS RPC was not removed from the HMP UI CONTEXT option prior to the
 shutdown of HMP on 10/27/17. HMP logged defect DE8609 to track this issue. HMP
 added as a subscriber to document RPC is not used by HMP but is in their
 context option.  
  
 If HMP is reactivated in the future, a new expiration date should be discussed
 with the CPRS team.  At that time it should be determined if ICR #3722 should
 be activated or if a new ICR is needed.  
  
 HMP is also a subscriber to ICR #4904.   ICR #4904 is an active ICR with OE/RR
 as the Custodial Package and Bar Code Expansion, VistA Integration Adaptor and
 HMP as subscribers for access to ORWPT BYWARD RPC. HMP may want to review
 ORQPT WARD PATIENTS (ICR #3725), ORWPT BYWARD (#4904), and DGWPT BY WARD (ICR
 #6759) to see if these RPCs all provide the same information.  It may not be
 necessary for HMP to have access to multiple RPCs.  

NUMBER: 3723                            IA #: 3723
  DATE CREATED: AUG 14, 2002
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: DBIA3718-F
  ORIGINAL NUMBER: 3718
 GENERAL DESCRIPTION:   RPC CALL TIU REQUIRES COSIGNATURE 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE

NUMBER: 3724                            IA #: 3724
  DATE CREATED: AUG 14, 2002
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: DBIA3718-G
  ORIGINAL NUMBER: 3718
 GENERAL DESCRIPTION:   RPC CALL IS TIU GET PERSONAL PREFERENCES 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE

NUMBER: 3725                            IA #: 3725
  DATE CREATED: AUG 14, 2002
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: DBIA3718-H
  ORIGINAL NUMBER: 3718
 GENERAL DESCRIPTION:   RPC CALL IS ORWPCE LEX 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   10/30/17-HMP's subscription to this ICR expires on
 10/27/17 when HMP will be shutdown.  HMP*2.0*12 released on 10/17/17 is an
 informational patch outlining the steps for the sites to shut down the
 application.  
  
 The CPRS team disapproved use of this RPC by HMP on 11/3/16 recommending HMP
 look at ORWLEX GETI10DX RPC.  At the time of the HMP shutdown on 10/27/17, the
 ORWLEX PCE RPC was in the HMP UI CONTEXT option and it is not known if this
 RPC is used by HMP.  
  
 If HMP is reactivated in the future, the HMP team will need to work with the
 CPRS team to discuss use of this RPC by HMP.   At that time, it will also need
 to be decided if ICR #3725 should be activated or a new ICR created.  
  
 ICR #6017 provides access to the ORWLEX GETI10DX RPC. This ICR was not 
 reviewed by CPRS prior to HMP's shut down on 10/27/17.  

NUMBER: 3726                            IA #: 3726
  DATE CREATED: AUG 14, 2002
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: DBIA3718-I
  ORIGINAL NUMBER: 3718
 GENERAL DESCRIPTION:   RPC CALL IS GMRCLIST CONSULT REQUEST 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE

NUMBER: 3727                            IA #: 3727
  DATE CREATED: AUG 14, 2002
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: DBIA3718-J
  ORIGINAL NUMBER: 3718
 GENERAL DESCRIPTION:   RPC CALL is ORWPT ENCTITL 
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 3729                            IA #: 3729
  DATE CREATED: AUG 14, 2002
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: DBIA3728-B
  ORIGINAL NUMBER: 3728
 GENERAL DESCRIPTION:   RPC CALL IS TIU LONG LIST OF TITLES 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE

NUMBER: 3730                            IA #: 3730
  DATE CREATED: AUG 14, 2002
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: DBIA3728-C
  ORIGINAL NUMBER: 3728
 GENERAL DESCRIPTION:   TIU LOCK RECORD is the RPC call.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE

NUMBER: 3731                            IA #: 3731
  DATE CREATED: JUL 28, 2004
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: RAPXRM
  NAME: RAPXRM                          ID: RAPXRM
 GENERAL DESCRIPTION:   This agreement allows the Clinical Reminders package to
 call routine RAPXRM with the exam node string, to receive external values of
 certain fields of that exam.  
  
 RA*5.0*153: returns HOSPITAL DIVISION and IMAGING LOCATION data from the 
 REGISTERED EXAMS (#70.02) sub-file to our Clinical Reminders subscriber.  
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
KEYWORDS: RA*5.0*153
KEYWORDS: RA custodian to PXRM
KEYWORDS: PXRM subscriber to RA
KEYWORDS: RA custodian to CPRS
KEYWORDS: CPRS subscriber to RA
COMPONENT/ENTRY POINT: EN1
VARIABLES: RADAS                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the exam subscript string from either the
 ^PXRMINDX(70,"IP" and the ^PXRMINDX(70,"PI" cross-references.  
VARIABLES: RARM                         TYPE: Both
 VARIABLES DESCRIPTION:   For input, this variable must be passed by reference. 
 
 For output, this variable is an array of external values: 
    RARM("EXAM D/T") = Exam Date and time in yyymmdd.hhmm format 
    RARM("EXAM STATUS") = Exam Status name 
    RARM("PROCEDURE") = Procedure name 
    RARM("INTERPRETING PHYSICIAN") = Primary Staff; else Primary Resident 
    RARM("DIV") = Name ^ Station Number ^ Facility Type (IA #2171) 
    RARM("I-LOC") = Name (origin: IMAGING LOCATION #79.1 file) 
COMPONENT/ENTRY POINT: RAD
 COMPONENT DESCRIPTION:   This entry point will build the Radiology and Nuclear
 Medicine entries into the Clinical Reminders Index. No input variables are
 required.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Subscriber determines the input data string from the
 last subscript of one of two cross-references: 
 ^PXRMINDX(70,"IP",procedure,examstatus,dfn,examdttm,examsubscriptstring) 
 ^PXRMINDX(70,"PI",dfn,examstatus,procedure,examdttm,examsubscriptstring) 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 3732                            IA #: 3732
  FILE NUMBER: 19.2                     GLOBAL ROOT: DIC(19.2
  DATE CREATED: AUG 20, 2002            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: REMOVE OPTION FROM FILE #19.2   ID: DIC(19.2
 GENERAL DESCRIPTION:   Permission to lookup and delete entries in 19.2 with VA
 FileMan APIs for entries in the custody of the application doing the lookup.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  ISC: Birmingham
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Clinical Reminders will utilize this ICR to delete the
 Schedule Options that run the QUERI extracts every month.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Effective with DSIY*1.5*0 released 9/22/21, to remove
 Above PAR's Enterprise Reporting task from OPTION scheduler. The option name
 is DSIY ENTERPRISE REPORTING.  

NUMBER: 3733                            IA #: 3733
  DATE CREATED: AUG 21, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: IBAGMT                       NAME: GMT Related IB utilities (IA#3733)
  ID: IBAGMT
 GENERAL DESCRIPTION:   This IA provides one GMT-related API call from the IB
 Package to be used by the PRCA (Accounts Receivable) package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMT
COMPONENT/ENTRY POINT: ISGMTBIL
 COMPONENT DESCRIPTION:   The API call created to check, is the bill
 GMT-related.  
  
 $$ISGMTBIL^IBAGMT(BILLNUM), where: 
    BILLNUM (Input) - The number of AR bill (not IEN!) 
    $$ISGMTBIL (Output) - The Boolean value (0 or 1), indicating, whether 
    the bill's amount was affected by the GMT Copayment status of the 
    patient, or not.  
    1 - The bill's amount was affected by the Patient's GMT Status 
    0 - The bill's amount was not affected by GMT.  
  
 Comments: the input parameter is Bill Number, not Bill IEN, because the file
 #350 "INTEGRATED BILLING ACTION" stores (and supports Cross-Reference by) Bill
 Number - see file #350, field #.11 "AR BILL NUMBER".  
VARIABLES: BILLNUM                      TYPE: Input
 VARIABLES DESCRIPTION:   Bill number 
VARIABLES: $$ISGMTBIL                   TYPE: Output
 VARIABLES DESCRIPTION:   The function returns Boolean value (0 or 1),
 indicating, whether 
    the bill's amount was affected by the GMT Copayment status of the 
    patient, or not.  
    1 - The bill's amount was affected by the Patient's GMT Status 
    0 - The bill's amount was not affected by GMT.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   The Accounts Receivable will use API call
 $$ISGMTBIL^IBAGMT(BILLNUM) for two purposes: 
  - to prepare Patient's Statement for CCPC 
  - to reprint Patient's Statement 
  
 If the API call will return "true" for a bill, included to the Statement, the
 following message will be added to the Statement: "REDUCTION OF INPATIENT
 COPAYMENT DUE TO GEOGRAPHIC MEANS TEST STATUS" 

NUMBER: 3734                            IA #: 3734
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870,IEN,0)
  DATE CREATED: AUG 27, 2002            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: HLCS(870,IEN,0) - NODE field (#.01)
  ID: HLCS(870,IEN,0)
 GENERAL DESCRIPTION:   This integration agreement covers direct global reads
 of the NODE field (#.01) of the HL Logical Link file (#870.)  The NODE field
 is the first piece of the ^HLCS(870,IEN,0) node of an entry in this file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland
 SUBSCRIBING DETAILS:   Kernel Master File Server (MFS) is a subscriber to
 integration agreement #3550.  IA# 3550 covers the use by MFS of the "C" 
 cross-reference of the HL Logical Link file (#870.)  As can be seen by the MFS
 code included in IA# 3550, after accessing the "C" cross-reference to find the
 internal entry number (IEN) for a particular entry in this file, the first
 piece of the zero node (i.e., the #.01 field) is viewed.  This reading of the
 first piece of the zero node also requires an integration agreement.  So, IA#
 3550 covers the Kernel MFS use of the "C" cross-reference, and this
 integration agreement covers the use of the NODE field (#.01) in the HL
 Logical Link file.  

NUMBER: 3735                            IA #: 3735
  FILE NUMBER: 50.68                    GLOBAL ROOT: PSNDF(
  DATE CREATED: AUG 28, 2002            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA3735                        ID: PSNDF(
GLOBAL REFERENCE: PSNDF(50.68,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 19                        FIELD NAME: CS FEDERAL SCHEDULE
  LOCATION: 7;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: NDC LINK TO GCNSEQNO
  LOCATION: 1;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: GCNSEQNO
  LOCATION: 1;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2000                      FIELD NAME: SERVICE CODE
  LOCATION: PFS;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 EMAIL GROUP 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.  
  
 Pharmacy Data Management requests an integration agreement to have read access
 to the National Drug file 50.68.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
KEYWORDS: VA PRODUCT FILE
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 3736                            IA #: 3736
  DATE CREATED: AUG 29, 2002            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXRMP12I
  NAME: CROSS-REFERENCE CREATION ERROR MESSAGE
  ID: PXRMP12I
 GENERAL DESCRIPTION:   This will give calling packages the ability to generate
 a cross-reference creation error message.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: CROSS-REFERENCE
KEYWORDS: CLINICAL REMINDER
COMPONENT/ENTRY POINT: DCERRMSG
VARIABLES: MSG                          TYPE: Output
 VARIABLES DESCRIPTION:   MSG is an array that contain's the FileMan generated
 error message. 
VARIABLES: XREF                         TYPE: Output
 VARIABLES DESCRIPTION:   XREF is an array that contain's, the cross-reference
 setup information. 
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany
SUBSCRIBING PACKAGE: PROBLEM LIST       ISC: Salt Lake City
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  ISC: Hines
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  ISC: Hines

NUMBER: 3737                            IA #: 3737
  DATE CREATED: AUG 29, 2002
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSSOPKI                      NAME: PSSOPKI
  ID: PSSOPKI
 GENERAL DESCRIPTION:   Pharmacy Data Management returns the most restrictive
 CS FEDERAL SCHEDULE code / DEA SPECIAL HDLG code for a Pharmacy Orderable
 Item, based on the Dispense Drugs that are associated with that Pharmacy
 Orderable Item.  The CS FEDERAL SCHEDULE code / DEA SPECIAL HDLG code is
 derived as follows: If any of the active dispense drugs associated with the
 orderable item for the specified package are matched to an entry in the
 National Drug File, then the most restrictive CS FEDERAL SCHEDULE code from
 the National Drug File will be returned. If there is no match or the CS
 FEDERAL SCHEDULE code is undefined then the most restrictive DEA SPECIAL HDLG
 code mapped to the corresponding CS FEDERAL SCHEDULE code as listed below will
 be returned.  
  
 DEA, SPECIAL HDLG      CS FEDERAL SCHEDULE 
  1                      1    (Schedule I narcotics) 
  2A                     2    (Schedule II narcotics) 
  2C                     2n   (Schedule II non-narcotics) 
  3A                     3    (Schedule III narcotics) 
  3C                     3n   (Schedule III non-narcotics) 
  4                      4    (Schedule IV narcotics) 
  5                      5    (Schedule V narcotics) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DETOX
COMPONENT/ENTRY POINT: OIDEA(PSSXOI,PSSXOIP)
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 will have the most restrictive
 CS FEDERAL SCHEDULE code or the DEA SPECIAL HDLG code as mapped to the
 corresponding CS FEDERAL SCHEDULE code (as defined in the description), of the 
 active Dispense Drugs that are matched to the Pharmacy Orderable Item for the
 specified package.  
  
 This variable can have one of the following values: 
  
  1;1  -  Schedule I Narcotics 
  1;2  -  Schedule II Narcotics - requires a wet signature 
  1;2n -  Schedule II Non-Narcotics - requires a wet signature 
  2;3  -  Schedule III Narcotics 
  2;3n -  Schedule III Non-Narcotics 
  2;4  -  Schedule IV Narcotics 
  2;5  -  Schedule V Narcotics 
  0    -  None of the above but there are active drugs matched to the 
          Pharmacy Orderable Item for the specified package 
  "" (Null)- There are no active drugs for the specified package matched to 
             the Pharmacy Orderable Item.  Schedule I-V Narcotics will return a
 2 piece value separated by a semicolon. 1st piece makes it compatible with the
 old API 3373, where 1 requires a wet signature and 2 does not.  
  
 2nd piece provides the exact nature of the Narcotics.  
COMPONENT/ENTRY POINT: $$DETOX(PSSDIEN)
 COMPONENT DESCRIPTION:   This API will identify a drug as a detoxification
 drug when its name contains "BUPREN".  
  
 Format: 
  S X=$$DETOX^PSSOPKI(PSSDIEN) 
VARIABLES: PSSDIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN of the DRUG file (#50).  
VARIABLES: $$DETOX                      TYPE: Output
 VARIABLES DESCRIPTION:   Where the output value is: 
  0 (zero) = not a detoxification drug 
  1 (one) = a detoxification drug 
COMPONENT/ENTRY POINT: $$OIDETOX(PSSXOI,PSSXOIP)
 COMPONENT DESCRIPTION:   This API will identify a Pharmacy Orderable Item as a
 detoxification drug based on the Dispense Drugs that are associated with that
 Pharmacy Orderable Item and at least one of them contains "BUPREN" in the
 name.  
  
 Format: 
  S X=$$OIDETOX(PSSXOI,PSSXOIP) 
VARIABLES: PSSXOI                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Pharmacy Orderable Item file (#50.7).  
VARIABLES: PSSXOIP                      TYPE: Input
 VARIABLES DESCRIPTION:   Application Package usage.  
  I - Inpatient 
  U - Unit Dose 
  O - Outpatient 
VARIABLES: $$OIDETOX                    TYPE: Output
 VARIABLES DESCRIPTION:   Where the output value is: 
  0 (zero) = not a detoxification drug 
  1 (one) = a detoxification drug 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Outpatient Pharmacy has permission to make the $$DETOX
 call.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIABDX SAVE RPC references PSSOPKI routine.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Added 2/28/25 effective with PSJ*5*424 for routine
 PSGOE42 to call $$OIDEA^PSSOPKI.  
  DATE ACTIVATED: DEC 07, 2011

NUMBER: 3738                            IA #: 3738
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFS
  NAME: PXRM INDEX FOR PHARMACY PATIENT FILE
  ID: PXRMXRFS
 GENERAL DESCRIPTION:   This entry point will set an Inpatient Pharmacy index
 entry.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: INPATIENT PHARMACY
KEYWORDS: CLINICAL REMINDER INDEX
KEYWORDS: PXRM
COMPONENT/ENTRY POINT: SPSPA
 COMPONENT DESCRIPTION:   This entry point global allows Inpatient Medications 
 to set the Clinical Reminder Index nodes for the Pharmacy file, file # 55
 entries.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to the Patient Stop
 Date/Time, X(2) is set to the Status.  
VARIABLES: DA                           TYPE: Input
VARIABLES: NODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Node denotes where the data is from either the Unit
 Dose or the IV multiple.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham

NUMBER: 3739                            IA #: 3739
  DATE CREATED: AUG 29, 2002
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSSOPKI1                     NAME: PSSOPKI1
  ID: PSSOPKI1
 GENERAL DESCRIPTION:   When a medication (Orderable Item) is selected in
 Computerized Patient Record System (CPRS) in the medication order entry
 process, that Orderable Item will be passed to the Pharmacy Data Management
 package (PDM), along with the Pharmacy application and patient internal entry 
 number. The PDM will pass back to CPRS, Dosage information from the Drugs in
 the DRUG file (#50) that are associated to that Orderable Item.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DOSE(PSSX,PD,TYPE,PSSDFN)
 COMPONENT DESCRIPTION:   This entry point will be used by CPRS to retrieve all
 of the available Dosages in the DRUG file (#50) for the selected Orderable
 Item. Additionally, other information will be returned from the DRUG file
 (#50) and the DOSAGE FORM file (#50.606) that will be used by CPRS in the 
 medication order entry process.  
VARIABLES: PSSX                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the name of the array to be built that will
 return the information to CPRS.  
VARIABLES: PD                           TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the PHARMACY
 ORDERABLE ITEM file (#50.7) of the selected Orderable Item in the CPRS
 medication order entry process.  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   This variable will indicate the Pharmacy package of
 the order. It will be "O" for Outpatient, "U" for Unit Dose, or "I" for "IV".  
VARIABLES: PSSDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   This variable is optional. It is the internal entry
 number from the PATIENT file (#2). It will only be used for Outpatient package
 orders, to calculate the maximum number of refills allowed.  
VARIABLES: PSSX(#)                      TYPE: Output
 VARIABLES DESCRIPTION:   This is the array returned in the call, subscripted
 with whatever variable name is passed into the call. This output array will
 increment for as many unique Drug dosages that are found. This output array is
 divided into 7 pieces, separated by the "^" character. The pieces are: 
  Piece 1 = Possible Dosage. This piece is a numeric value, and will only 
            have data if it is a Possible Dosage that is being returned. 
            This is calculated by multiplying the Strength by the Dispense 
            Units per Dose.  
  Piece 2 = Unit. This is the Unit of measure for the product. This value is
 formatted via the API $$DOSE^PSSORUTE(DOSE) (see IA# 4555) in order to add
 leading zeros to decimal numbers and a blank space between number and unit.  
  Piece 3 = Dispense Units per Dose. Similar to piece 1, this is a numeric 
            value, and will only be returned if a Possible Dosage is being 
            returned. This value multiplied by the Strength will be the 
            Possible Dosage.  
  Piece 4 = Noun. This is the Noun that is associated with the Dosage. For 
           example, a Dosage Form of TAB would likely have a Noun of 
           TABLET(S).  
  Piece 5 = Instructions. This can be used for the dosage selection. For a 
           Possible Dosage, it is the numeric dosage concatenated with the 
           Unit. Some examples would be 325 MG, 650 MG, and 10 MG/15 ML. For a 
           Local Possible Dosage, it would be a text dosage. Some examples 
           would be 1 DROP, 2 DROPS, and 1 TEAPSOONFUL. This value is formatted
 via the API $$DOSE^PSSORUTE(DOSE) (see IA# 4555) in order to add leading zeros
 to decimal numbers and a blank space between number and unit.  
  Piece 6 = Dispense Drug. This is internal entry number from the DRUG file 
            (#50).  
  Piece 7 = Price. If the Drug has a Price Per Dispense Unit associated 
            with it, this will be that price times the BCMA Units per Dose 
            for that Dosage. If there is no BCMA Units per Dose for that 
            Dosage, this will be Price Per Dispense Unit times the Dispense 
            Units per Dose. If the Dosage does not have a BCMA Units per 
            Dose, and does not have a Price Per Dispense Unit, this will be 
            null.  
VARIABLES: PSSX('DD',Dispense Drug)     TYPE: Output
 VARIABLES DESCRIPTION:   This array contains specific Drug information of the
 Drug that is associated with the Dosage. For every drug entry (piece 6 of the
 PSSX(#) array), there will be a corresponding entry in this PSSX("DD",
 Dispense Drug IEN) array. The pieces of this array are separated by the "^" 
 character, and they are as follows: 
  Piece 1 = Name. This is the name of the Drug, the .01 field of the DRUG 
            file (#50).  
  Piece 2 = Price Per Dispense Unit. This is the price per dispense unit 
            for this drug.  
  Piece 3 = Local Non-formulary flag. If the drug is designated as 
           non-formulary, then a 1 will be returned in this piece, 
           otherwise, a null will be returned.  
  Piece 4 = Dispense Unit. This is the Dispense Unit for the drug.  
  Piece 5 = Strength. This is a value that represents the single dose of 
            medication supplied by this product. This field could be null 
            for some drugs, such as multi-ingredient drugs.  
  Piece 6 = Unit. This is the unit of measure of this product. This value is
 formatted via the API $$DOSE^PSSORUTE(DOSE) (see IA# 4555) in order to add
 leading zeros to decimal numbers and a blank space between number and unit.  
  Piece 7 = Dosage Form. This is the name of the Dosage Form of the 
            product.  
  Piece 8 = Maximum # of refills. This will only be returned for Outpatient 
            medication orders. It can be used as a default for the maximum 
            number of refills allowed for the medication order.  
  Piece 9 = Schedule requirement flag. This is always set to 1. This piece 
            is not currently used.  
  Piece 10 = CS FEDERAL SCHEDULE code / DEA SPECIAL HDLG code, it can 
             have one of the following values: 
             1;1  -  Schedule I Narcotics 
             1;2  -  Schedule II Narcotics 
             1;2n -  Schedule II Non-Narcotics 
             2;3  -  Schedule III Narcotics 
             2;3n -  Schedule III Non-Narcotics 
             2;4  -  Schedule IV Narcotics 
             2;5  -  Schedule V Narcotics 
             0    -  for other active drugs 
             "" (Null)- There are no active drugs for the given package.  
             
             Schedule I-V Narcotics will have a 2 piece value separated 
             by a semicolon. 1st piece makes it compatible with the old API 
             3233, where 1 requires a wet signature and 2 does not.  
             2nd piece provides the controlled substance schedule.  
  
  Piece 11 = Flag for splitting Dosage Form. This will be a 0 or a 1. The 
             only time it will be a 1 is if there are Possible Dosages 
             associated with the drug, and there is at least 1 Possible 
             Dosage that is entered for the drug with a decimal point. This 
             indicates that the Dosage Form can be split.  
VARIABLES: PSSX('MISC')                 TYPE: Output
 VARIABLES DESCRIPTION:   This array contains information relating to the
 Dosage Form that is associated with the selected Orderable Item. It contains 3
 pieces, separated by the "^" character. The pieces are: 
  Piece 1 = Verb. This is the verb associated with the Dosage Form. 
            Examples would be INSTILL for the Dosage Form of SOLN,OTIC, and 
            TAKE for the Dosage Form of TAB.  
  Piece 2 = Preposition. This is the preposition associated with the Dosage 
            Form. Examples would be BY for the Dosage Form of TAB, and TO 
            for the Dosage Form of CREAM.  
  Piece 3 = Conjunction. This is the conjunction associated with the Dosage 
            Form. Most Dosage Forms would have a conjunction of OF.  
VARIABLES: PSSX(#,#)                    TYPE: Output
 VARIABLES DESCRIPTION:   This array contains the same information as the
 PSSX(#) array. This array is only returned when Possible Dosages are being
 returned, and there are duplicate Possible Dosages with different Dispense
 Units per Dose. The PSSX(#) array would contain the Possible Dosage with the
 lowest Dispense Units per Dose, and the PSSX(#,#) arrays would contain all
 other Possible Dosages with higher Dispense Units per Dose.  
VARIABLES: PSSX('PI',#)                 TYPE: Output
 VARIABLES DESCRIPTION:   This array holds the default Patient Instructions
 from the Pharmacy Orderable Item (#50.7) file.  
VARIABLES: PSSX('DEA')                  TYPE: Output
 VARIABLES DESCRIPTION:   This output returns the most restrictive CS FEDERAL
 SCHEDULE code / DEA SPECIAL HDLG code for a Pharmacy Orderable Item, based on
 the Dispense Drugs that are associated with that Pharmacy Orderable Item, and
 they are derived as follows: If any of the active dispense drugs associated
 with the orderable item for the specified package are matched to an entry in
 the National Drug File, then the most restrictive CS FEDERAL SCHEDULE code
 from the National Drug File will be returned. If there is no match or the CS
 FEDERAL SCHEDULE code is undefined then the most restrictive DEA SPECIAL HDLG
 code mapped to the corresponding CS FEDERAL SCHEDULE code as listed below will
 be returned.  
  
    DEA, SPECIAL HDLG      CS FEDERAL SCHEDULE 
     1                      1    (Schedule I narcotics) 
     2A                     2    (Schedule II narcotics) 
     2C                     2n   (Schedule II non-narcotics) 
     3A                     3    (Schedule III narcotics) 
     3C                     3n   (Schedule III non-narcotics) 
     4                      4    (Schedule IV narcotics) 
     5                      5    (Schedule V narcotics) 
  
 This output variable will have the most restrictive CS FEDERAL SCHEDULE code
 or the DEA SPECIAL HDLG code as mapped to the corresponding CS FEDERAL
 SCHEDULE code (as defined below), of the active Dispense Drugs that are
 matched to the Pharmacy Orderable Item for the specified package.  
  
 It can have one of the following values: 
  
 1;1  -  Schedule I Narcotics 1;2  -  Schedule II Narcotics - requires a wet
 signature 1;2n -  Schedule II Non-Narcotics - requires a wet signature 2;3  - 
 Schedule III Narcotics 2;3n -  Schedule III Non-Narcotics 2;4  -  Schedule IV
 Narcotics 2;5  -  Schedule V Narcotics 0    -  None of the above but there are
 active drugs matched to the 
         Pharmacy Orderable Item for the specified package "" (Null)- There are
 no active drugs for the specified package matched to 
            the Pharmacy Orderable Item.  Schedule I-V Narcotics will return a
 2 piece value separated by a semicolon. 1st piece makes it compatible with the
 old API 3233, where value 1 requires a wet signature and 2 does not.  
  
 2nd piece provides the controlled substance schedule.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   
  VIABDX SAVE RPC references PSSOPKI1 routine.  
  DATE ACTIVATED: DEC 15, 2015

NUMBER: 3740                            IA #: 3740
  DATE CREATED: SEP 12, 2002
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: CSLVQ                        NAME: Vendor Query (for CoreFLS)
  ORIGINAL NUMBER: 3740                 ID: CSLVQ
 GENERAL DESCRIPTION:   Vendor Query 
 -------------
  
 Purpose: To allow a user to query CoreFLS for a vendor matching a given set of
 search criteria 
  
 Behavior: The user is prompted for prompted for one or more query strings, as
INTEGRATION REFERENCES Redacted List as of 20261106
                                                     NOV 09, 2026@17:23   PAGE 3
--------------------------------------------------------------------------------

 follows.  
  
 >D VENQ^CSLVQ(.out,"NCS","A") 
  
 Vendor Name: CITI City: San Francisco State: CA 
  
 Any matching values are displayed to the user in the style of ^DIC. Each
 matching value will have an associated multiline identifier consiting of the
 vendor address. Once the user selects a record, the "out" array will be
 populated with the set of attributes for that vendor reurned by CoreFLS (for
 details, see "OUTPUT" below).  
  
 The set of fields for which the user will be prompted is controlled by the
 second parameter to the vendor query (see below under "Syntax"). If no
 parameters are supplied, the default is to query for name only. Any fields for
 which the user supplies no value are ignored, otherwise, the search criterion
 will be the Boolean AND of the supplied parameters (i.e., each field must
 match).  
  
 By default, if the user enters an unquoted string, it will be intepreted as a
 (case sensitive) initial substring. Thus, CITI matches CITIBANK, but Citi will
 not. (In this case, if the user enters CITI, the string actually sent to
 CoreFLS is "CITI%"). As an alternative, users may enter either exact matches
 or patterns involving the SQL wildcard characters '%' and '_' in quotes. E.g., 
  
 Vendor Name: "CITI%NK" City: "L_s Ang%es" 
  
  
 Example: 
  
 Vendor Name: "%TEMS%" 
 . . . . . . . . 
     
    Choose from: 
    1    ACCESS SYSTEMS 
         1116 SMITH ST 
         CHARLESTON, WV  25301 
  
    2    BARD ACCESS SYSTEMS 
         5425 W AMELIA EARHART DR 
         SALT LAKE CITY, UT  84116-3713 
  
 etc.  
    
     
 Select QUERY RESULTS SEQ NO: 2   BARD ACCESS SYSTEMS 
         5425 W AMELIA EARHART DR 
         SALT LAKE CITY, UT  84116-3713 
  
  
  
  
  
 Syntax: 
  
 D VENQ^CSLVQ(.out,flags,display_flags) 
  
  
 INPUT This call has three parameters, a reference to an array that will be
 populated with the attributes of the selected vendor, a scalar variable
 containing 0 or more flags indicating which fields should be used as input
 parameters/searchable fields, and a scalar variabld containing 0 or more flags 
 controlling what will be displayed to the user as identifying text (i.e., as
 Fileman identifiers).  
  
 The format of the output array is described below under "OUTPUT". The second
 parameter may contain any combination of the following flags (order is
 unimportant): 
  
  
 N = Name 
  
 n = Vendor Number 
  
 a = Area Code 
  
 p = Phone Number 
  
 C = City 
  
 S = State 
  
 T = Tax ID/SSN 
  
 1 = Address Line 1 
  
 2 = Address Line 2 
  
 3 = Address Line 3 
  
 P = Postal Code 
  
 c = Chain number 
  
 For example, to query by name and SSN, use "NT". If this parameter is omitted
 (or if it is equal to the empty string), the default is to search by name
 only. However, if a value is supplied, "N" will not be automatically added to
 the list. Thus, "T" will cause the user to be prompted for Tax ID only.  
  
 The display_flags parameter may contain any combination of the following flags
 (again, order is unimportant): 
  
 n = CoreFLS Vendor ID / CoreFLS Site ID 
  
 A = address 
  
 t = telephone no.  
  
 T = Tax ID 
  
 C = Chain no.  
  
 P = Participation code 
  
 a = Attributes (Purchasing, Pay-to, etc.) 
  
 Note: If the "n" flag is included, the CoreFLS vendor ID and CoreFLS site ID
 will appear on the first line of the identifying text displayed for that
 vendor with the vendor name immediately below.  
  
 If this parameter is missing or null, the default is to display only address
 information (i.e., the default is "A").  
  
 OUTPUT 
  
 A single array is passed by reference ("out" in the above syntax example). If
 the user selects a vendor, the array will be populated with the attributes of
 that vendor as follows: 
  
  
 out("NAME") - Vendor name 
  
 out("NUMBER") - numeric vendor ID 
  
 out("INACTIVE") - vendor will be inactive after this date (FM format) 
  
 out("TAXID") - Tax ID 
  
 out("AREA_CODE") - area code 
  
 out("PHONE") - phone number 
  
 out("FAX_AREA_CODE") - FAX area code 
  
 out("FAX") - FAX number 
  
 out("ADDRESS1") - address line 1 
  
 out("ADDRESS2") - address line 2 
  
 out("ADDRESS3") - address line 3 
  
 out("CITY") - City 
  
 out("STATE") - State 
  
 out("COUNTY") - County 
  
 out("ZIP") - Postal code 
  
 out("COUNTRY") - Country 
  
 out("SITE_CODE") - Site Code 
  
 out("CHAIN_NO") - Chain Number 
  
 out("COMMENTS") - Comments 
  
 out("PARTICIPATION_CODE") - Participation  Code 
  
 out("LAST_UPDATED") - date vendor record last updated on CoreFLS 
  
 In addition, there are a number of optional vendor attributes. If an attribute
 is present, the appropriate top level subscript will be set. For example, for
 an EDI vendor, we will have 
  
 out("EDI_VENDOR")=1 
  
 The complete list of attribute subscripts is 
  
 ON_HOLD PRIMARY_PAY_TO RFQ PURCHASING PAY_TO PROCUREMENT_CARD PRICER_EXEMPT 
 FEE_VENDOR EDI_VENDOR PO_HOLD NEW_PAY_HOLD ALL_PAY_HOLD 
  
  
 Fields have no value will not appear in the out array 
  
 Errors: If an error should occur during the query, the node out("ERROR") will
 be set. There are two special cases: 
  
 Network timeout - In this case, out("ERROR")="NETWORK TIMEOUT" 
  
 No Selection - If the user does not select a vendor (e.g., by exiting by
 typing "^") it will be the case that out("ERROR")="NO SELECTION" 
  
 In all other cases, out("ERROR") will be set to the error message returned by
 CoreFLS or possibly to a value indicating an internal error in the
 Communications Service Library (the specific value being a string indicating
 the nature of the error).  
  
 Caveat: Note that the vendor query API does not clear the out variable, so it
 is best to explicitly NEW this variable (which should be namespaced) before
 making the call.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COREFLS
KEYWORDS: VENDOR
KEYWORDS: QUERY
COMPONENT/ENTRY POINT: VENQ(.out,flags,display_flags)
 COMPONENT DESCRIPTION:   This entry point is used to initiate a query to
 CoreFLS for attributes of matching vendors. Optional flags control what
 criteria the user is allowed to use to search and what identifying information
 (in the sense of Fileman identifiers) will be displayed to the user. This
 allows the application developer to control the look and feel of the query to
 a certain extent and avoid asking for (or displaying) fields that are not 
 relevant to the given application.  
VARIABLES: out                          TYPE: Output
 VARIABLES DESCRIPTION:   This variable is an array passed by reference. It is
 used to return vendor attributes to the calling application, or to signal that
 an error or other exceptional condition (network timeout, or user made no 
 selection) has occured. (This variable should be namespaced.) 
VARIABLES: flags                        TYPE: Input
 VARIABLES DESCRIPTION:   This variable is used to control which fields will be
 used in the search process. (This variable should be namespaced.) 
VARIABLES: display_flags                TYPE: Input
 VARIABLES DESCRIPTION:   This variable controls what identifying information
 will be displayed to the user. (This variable should be namespaced.) 
SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING
SUBSCRIBING PACKAGE: PROSTHETICS

NUMBER: 3742                            IA #: 3742
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: AUG 29, 2002            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ACCESS TO ADDRESS FIELDS IN DPT
  ID: DPT(
GLOBAL REFERENCE: DPT(DFN,.11
FIELD NUMBER: .111                      FIELD NAME: STREET ADDRESS [LINE 1]
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .114                      FIELD NAME: CITY
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .115                      FIELD NAME: STATE
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1112                     FIELD NAME: ZIP+4
  ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(DFN,.13
FIELD NUMBER: .131                      FIELD NAME: PHONE NUMBER [RESIDENCE]
  ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Scheduling is requesting access to several address
 fields in the Patient (#2) file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 3743                            IA #: 3743
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFK
  NAME: PXRM DELETE FOR PHARMACY PATIENT FILE INDEX
  ID: PXRMXRFK
 GENERAL DESCRIPTION:   This entry point will delete an Inpatient Pharmacy
 index entry.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: INPATIENT MEDICATIONS
KEYWORDS: CLINICAL REMINDER
KEYWORDS: INDEX DELETE
KEYWORDS: PXRM
COMPONENT/ENTRY POINT: KPSPA
 COMPONENT DESCRIPTION:   This entry point global allows Inpatient Medications
 to delete the Clinical Reminder Index nodes for the Pharmacy file, file # 55
 entries.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to the Patient Stop
 Date/Time, X(2) is set to the Status.  
VARIABLES: DA                           TYPE: Input
VARIABLES: NODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Node denotes where the data is from either the Unit
 Dose or the IV multiple.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham

NUMBER: 3744                            IA #: 3744
  DATE CREATED: SEP 03, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VADPT                        NAME: DBIA3744
  ID: VADPT                             STATUS: Active
KEYWORDS: TEST PATIENT
COMPONENT/ENTRY POINT: $$TESTPAT
 COMPONENT DESCRIPTION:   Function call returns whether or not a given patient
 is a test patient.  A test patient is defined as a patient whose SSN has five
 leading zeros (ex: 000001234) or whose TEST PATIENT INDICATOR field (#6) is
 set to 'YES'.  
  
  Sample Use 
  ----------
  S DFN=xxxxx 
  S X=$$TESTPAT^VADPT(DFN) 
  W !,"Patient is ",$S('X:"not ",1:""),"a test patient" 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   
  Pointer to PATIENT file (#2) 
VARIABLES: Output of function call      TYPE: Output
 VARIABLES DESCRIPTION:   
  1 = Test patient 
  0 = Not a test patient 

NUMBER: 3745                            IA #: 3745
  DATE CREATED: SEP 03, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VAFHLRO3                     NAME: DBIA3745
  ID: VAFHLRO3                          STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PERSON
 COMPONENT DESCRIPTION:   Procedure returns an array containing the pieces
 needed to build an HL7 Role Person for a given user.  
  
  Notes 
  -----
  * Existance and validity of input is assumed 
  * Initializtion (i.e. KILLing) of ARRAY() must be done by the 
    calling program 
  * ARRAY() will not be set if role can not be calculated 
  
  Sample Use 
  ----------
  S PTR200=xxxxx 
  S ARRAY=$NA(^TMP("ZJRP",$J)) 
  S NULL=$C(34,34) 
  D PERSON^VAFHLRO3(PTR200,ARRAY,NULL) 
VARIABLES: PTR200                       TYPE: Input
 VARIABLES DESCRIPTION:   
  Pointer to entry in NEW PERSON file (#200) 
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   
  Input: Array to store info in (full global reference) 
  
  Output: ARRAY will be set as follows 
   ARRAY(1,comp#) = Value 
   ARRAY(1,comp#,sub#) = Value 
     Comp 1: 2 Sub-components 
       Sub 1: DUZ 
       Sub 2: Facility number 
     Comp 2 - 7: Name in HL7 format 
     Comp 8: VA200 (literal) 
   ARRAY(2,comp#) = Value 
     Comp 1: Provider SSN 
     Comp 9: SSA (literal) 
VARIABLES: NULL                         TYPE: Input
 VARIABLES DESCRIPTION:   
  HL7 null designation 
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
 SUBSCRIBING DETAILS:   Cover use of call by PCMM 

NUMBER: 3746                            IA #: 3746
  FILE NUMBER: 0                        GLOBAL ROOT: DD(FILE,0,'ID')
  DATE CREATED: FEB 03, 2003            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA3746                        ID: DD(FILE,0,'ID')
GLOBAL REFERENCE: DD(FILE,0,'ID',ID)
 GENERAL DESCRIPTION:   This IA will document that the Medicine package can 
 loop through the ^DD(file number,0,"ID") with $O to get the identifier 
 numbers.  The file numbers that the Medicine will loop through ranges from 690
 to 701.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Hines

NUMBER: 3747                            IA #: 3747
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFS
  NAME: PXRM INDEX FOR PRESCRIPTION FILE
  ID: PXRMXRFS
 GENERAL DESCRIPTION:   This entry point will set an Outpatient Pharmacy index
 entry.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: OUTPATIENT PHARMACY
KEYWORDS: CLINICAL REMINDER
KEYWORDS: PXRM INDEX
COMPONENT/ENTRY POINT: SPSRX
 COMPONENT DESCRIPTION:   This entry point global allows Outpatient Pharmacy to
 set the Clinical Reminder Index nodes for the Prescription File, file # 52
 entries.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to the Days Supply, X(2)
 is set to the Release Date/Time.  
VARIABLES: DA                           TYPE: Input
VARIABLES: NODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Node denotes where the data is from either the
 Original, Partial (subfile 52.2), or Refill (subfile 52.1).  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 3748                            IA #: 3748
  DATE CREATED: SEP 05, 2002            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXRMXSRFK
  NAME: PXRM DELETE FOR PRESCRIPTION FILE INDEX
  ID: PXRMXSRFK
 GENERAL DESCRIPTION:   This entry point will delete an Outpatient Pharmacy
 index entry.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OUTPATIENT PHARMACY
KEYWORDS: CLININCAL REMINDER
KEYWORDS: INDEX DELETE
KEYWORDS: PXRM
COMPONENT/ENTRY POINT: KPSRX
 COMPONENT DESCRIPTION:   This entry point global allows Outpatient Pharmacy to
 delete the Clinical Reminder Index nodes for the Prescription File, file # 52
 entries.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to the Days Supply, X(2)
 is set to the Release Date/Time.  
VARIABLES: DA                           TYPE: Input
VARIABLES: NODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Node denotes where the data is from either the
 Original, Partial (subfile 52.2), or Refill (subfile 52.1).  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 3749                            IA #: 3749
  FILE NUMBER: 8989.3                   GLOBAL ROOT: XTV(8989.3,
  DATE CREATED: SEP 06, 2002            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: KERNEL SITE PARAMETERS          ID: XTV(8989.3,
GLOBAL REFERENCE: XTV(8989.3,1,'DNS'
FIELD NUMBER: 51                        FIELD NAME: DNS IP
  LOCATION: DNS;1                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Access to this field is needed to determine whether it is
 null or not.  If null, DNS call will not be used.  
  
 Actual code used: 
  
 Q:$P($G(^XTV(8989.3,1,"DNS")),U,1)="" 0  ; No DNS IP address 
 GENERAL DESCRIPTION:   MailMan requests read access to KERNEL SITE PARAMETERS
 file (#8989.3) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MAILMAN            ISC: Oakland

NUMBER: 3750                            IA #: 3750
  DATE CREATED: SEP 06, 2002
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORWOR1                       NAME: PKI VERIFY DS DATA
  ORIGINAL NUMBER: 3750                 ID: ORWOR1
 GENERAL DESCRIPTION:   This agreement is between CPRS and Pharmacy to handle
 calls used in the processing of digitally signed orders for the DEA/PKI
 project.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: VERIFY
 COMPONENT DESCRIPTION:   This is used to verify the correctness of a digitally
 signed order.  Returned values are: 
  1 for verified 
  "-1^error message" for error during parameter check 
  "898020xx^error message" for error during verification 
  
  Reason Error Code          Error Message 
  89802000               Order Text is blank 
  89802001               DEA # missing 
  89802002               Drug Schedule missing 
  89802003               DEA # not valid 
  89802004               Valid Certificate not found 
  89802005               Couldn't load CSP 
  89802006               Smart card Reader not found 
  89802007               Certificate with DEA # not found 
  89802008               Certificate not valid for schedule 
  89802010               Crypto Error (contact IRM) 
  89802015               Corrupted (Decode failure) 
  89802016               Corrupted (Hash mismatch) 
  89802017               Certificate revoked 
  89802018               Verification failure 
  89802019               Before Cert effective date 
  89802020               Certificate expired 
VARIABLES: ORDER                        TYPE: Input
 VARIABLES DESCRIPTION:   ORIFN;ACTION - NOTE: if no ACTION then 1 (new order)
 is assumed ORIFN is the internal order number of the order from the ORDERS
 file (#100) ACTION is the associated action, found at ^OR(100,ORIFN,8,ACTION 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the patient DFN.  
COMPONENT/ENTRY POINT: GETDATA
 COMPONENT DESCRIPTION:   This API gets Pharmacy/DEA data that has been stored
 with the order.  The returned values are: 
  Y = 1^ Order # ^ Nature of order ^ Order Status ^ Date Signed 
  Y(1) = Patient name ^ Street1 ^ Street2 ^ Street3 ^ City ^ State ^ Zip 
  Y(2) = Drug name_strength_dosage form (Dispense Drug) ^ Drug IEN (file 50) ^
 Drug quantity prescribed ^ Schedule of medication ^ DEA Schedule 
  Y(3) = Directions for use (SIG) 
  Y(4) = Practitioner's name ^ DUZ ^ Practitioner's (DEA) registration number 
  Y(5) = SiteName ^ SiteStreet1  ^ SiteStreet2 ^ SiteCity  ^ SiteState ^
 SiteZip 
  Y(6) = Orderable Item ^ Orderable Item IEN (file 101.43) If an error occurs,
 then error is returned: 
  ;Y = "-1^Error message" 
  
VARIABLES: ORDER                        TYPE: Input
 VARIABLES DESCRIPTION:   
   ORIFN;ACTION - NOTE: if no ACTION then 1 (new order) is assumed 
   ORIFN is the internal order number of the order from the ORDERS file (#100) 
   ACTION is the associated action, found at ^OR(100,ORIFN,8,ACTION 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the patient DFN.  
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
  ISC: Birmingham
 SUBSCRIBING DETAILS:   
  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 3752                            IA #: 3752
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFS
  NAME: PXRM INDEX FOR GMRV VITAL MEASUREMENT FILE
  ID: PXRMXRFS
 GENERAL DESCRIPTION:   This entry point will set a GMRV Vital Measurement
 index entry.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: PXRM INDEX
KEYWORDS: CLINICAL REMINDER
KEYWORDS: GMRV VITAL MEASUREMENT
COMPONENT/ENTRY POINT: SVITAL
 COMPONENT DESCRIPTION:   This entry point global allows Gen. Med. Rec. -
 Vitals to set the Clinical Reminder Index nodes for the GMRV VITAL
 MEASUREMENT, file # 120.5 entries.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to Date/Time, X(2)is set
 to DFN, X(3) is set to Vital Type, X(4) is set to Entered In Error.  
VARIABLES: DA                           TYPE: Input
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  ISC: Hines

NUMBER: 3753                            IA #: 3753
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFK
  NAME: PXRM DELETE FOR GMRV VITAL MEASUREMENT FILE INDEX
  ID: PXRMXRFK
 GENERAL DESCRIPTION:   This entry point will delete a Gen. Med. Rec. - Vitals
 index entry.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: PXRM INDEX DELETE
KEYWORDS: CLINICAL REMINDER
KEYWORDS: GEN. MED. REC. - VITALS
COMPONENT/ENTRY POINT: KVITAL
 COMPONENT DESCRIPTION:   This entry point global allows Gen. Med. Rec. -
 Vitals to delete the Clinical Reminder Index nodes for the GMRV VITAL
 MEASUREMENT file, file # 120.5 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to Date/Time, X(2)is set
 to DFN, X(3) is set to Vital Type, X(4) is set to Entered In Error.  
VARIABLES: DA                           TYPE: Input
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  ISC: Hines

NUMBER: 3754                            IA #: 3754
  DATE CREATED: SEP 11, 2002            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXRMXLAB                     NAME: PXRM INDEX FOR LAB DATA FILE
  ID: PXRMXLAB
 GENERAL DESCRIPTION:   This routine will set a Lab Data index entry or delete
 one.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: LAB
KEYWORDS: PXRM INDEX
KEYWORDS: CLINICAL REMINDER
COMPONENT/ENTRY POINT: CHSET
 COMPONENT DESCRIPTION:   This entry point global allows Lab Service to set the
 Clinical Reminder Index nodes for the Lab Data file, file # 63 entries.  
VARIABLES: LRDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   LRDFN is set the Lab Record DFN 
VARIABLES: LRIDT                        TYPE: Input
 VARIABLES DESCRIPTION:   LRIDT is set to the Inverse Date/Time 
COMPONENT/ENTRY POINT: CHKILL
 COMPONENT DESCRIPTION:   This entry point global allows Lab Service to delete
 the Clinical Reminder Index nodes for the Lab Data file, file # 63 entries.  
VARIABLES: LRDFN                        TYPE: Input
VARIABLES: LRIDT                        TYPE: Input
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 3755                            IA #: 3755
  DATE CREATED: SEP 18, 2002
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                NAME: TIU UNLOCK RECORD
  REMOTE PROCEDURE: TIU UNLOCK RECORD   ORIGINAL NUMBER: 3755
 GENERAL DESCRIPTION:   TIU UNLOCK RECORD 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE

NUMBER: 3756                            IA #: 3756
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFS
  NAME: PXRM INDEX FOR THE RAD/NUC MED PATIENT FILE
  ID: PXRMXRFS
 GENERAL DESCRIPTION:   This entry point will set an Radiology index entry.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: CLININCAL REMINDER
KEYWORDS: RADIOLOGY
COMPONENT/ENTRY POINT: SRAD
 COMPONENT DESCRIPTION:   This entry point global allows Radiology/Nuclear
 Medicine to set the Clinical Reminder Index nodes for the Rad/Nuc Med Patient
 file, file # 70 entries.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   DA(2) is set to the DFN, DA(1) is set to the inverse
 Exam Date, DA is set to the Examination Entry.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X(2) is set to the Procedure, X(1) is set to the Exam
 Status.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  ISC: Hines

NUMBER: 3757                            IA #: 3757
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFK
  NAME: PXRM DELETE FOR THE RAD/NUC MED PATIENT FILE INDEX
  ID: PXRMXRFK
 GENERAL DESCRIPTION:   This entry point will delete an Radiology/Nuclear
 Medicine index entry.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: PXRM DELETE INDEX
KEYWORDS: RADIOLOGY/NUCLEAR MED
COMPONENT/ENTRY POINT: KRAD
 COMPONENT DESCRIPTION:   This entry point global allows Radiology/Nuclear
 Medicine to delete the Clinical Reminder Index nodes for the Rad/Nuc Med
 Patient file, file # 70 entries.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   DA(2) is set to the DFN, DA(1) is set to the inverse
 Exam Date, DA is set to the Examination entry.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X(2) is set to the Procedure, X(1) is set to the Exam
 Status.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  ISC: Hines

NUMBER: 3758                            IA #: 3758
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFS
  NAME: PXRM INDEX FOR PSYCH INSTRUMENT PATIENT FILE
  ID: PXRMXRFS
 GENERAL DESCRIPTION:   This entry point will set a Mental Health index entry.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: CLINICAL REMINDER
KEYWORDS: MENTAL HEALTH 
KEYWORDS: PSYCH INSTRUMENT PATIENT FILE
KEYWORDS: PXRM INDEX
COMPONENT/ENTRY POINT: SMH
 COMPONENT DESCRIPTION:   This entry point global allows Mental Health to set
 the Clinical Reminder Index nodes for the Psych Instrument Patient file, file
 #601.2 entries.  
  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to Completion Date.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   DA is an array. DA(2) is set to the DFN, DA(1) is set
 to the Instrument, DA is set to the Completion Date 
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas

NUMBER: 3759                            IA #: 3759
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFK
  NAME: PXRM DELETE FOR PSYCH INSTRUMENT PATIENT FILE INDEX
  ID: PXRMXRFK
 GENERAL DESCRIPTION:   This entry point will delete a Mental Health index
 entry.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: MENTAL HEALTH
KEYWORDS: CLINICAL REMINDERS
COMPONENT/ENTRY POINT: KMH
 COMPONENT DESCRIPTION:   This entry point global allows Mental Health to
 delete the Clinical Reminder Index nodes for the Pharmacy file, file #601.2
 entries.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to Completion Date.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   DA is an array. DA(2) is set to the DFN, DA(1) is set
 to the Instrument, DA is set to the Completion Date.  
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas

NUMBER: 3760                            IA #: 3760
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFS
  NAME: PXRM INDEX FOR THE PROBLEM FILE
  ID: PXRMXRFS
 GENERAL DESCRIPTION:   This entry point will set a Problem List index entry.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: PROBLEM LIST
COMPONENT/ENTRY POINT: SPROB
 COMPONENT DESCRIPTION:   This entry point global allows Problem List to set
 the Clinical Reminder Index nodes for the Problem file, file # 9000011
 entries.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to Diagnosis, X(2) is set
 to DFN, X(3) is set to Date Last Modified, X(4) is set to Status, X(5) is set
 to Priority, X(6) is set to Condition.  
VARIABLES: DA                           TYPE: Input
SUBSCRIBING PACKAGE: PROBLEM LIST       ISC: Salt Lake City

NUMBER: 3761                            IA #: 3761
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFK
  NAME: PXRM DELETE FOR PROBLEM FILE INDEX
  ID: PXRMXRFK
 GENERAL DESCRIPTION:   This entry point will delete a Problem List index
 entry.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: CLININCAL REMINDERS
KEYWORDS: PROBLEM LIST
COMPONENT/ENTRY POINT: KPROB
 COMPONENT DESCRIPTION:   This entry point global allows Problem List to delete
 the Clinical Reminder Index nodes for the Problem file, file #9000011 entries. 
 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to Diagnosis, X(2) is set
 to DFN, X(3) is set to Date Last Modified, X(4) is set to Status, X(5) is set
 to Priority, X(6) is set to Condition.  
VARIABLES: DA                           TYPE: Input
SUBSCRIBING PACKAGE: PROBLEM LIST       ISC: Salt Lake City

NUMBER: 3762                            IA #: 3762
  FILE NUMBER: 660                      GLOBAL ROOT: RMRP(660
  DATE CREATED: SEP 16, 2002            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  NAME: test                            ID: RMRP(660
GLOBAL REFERENCE: RMPR(660
FIELD NUMBER: .01                       FIELD NAME: asd
  LOCATION: asdf
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed

NUMBER: 3763                            IA #: 3763
  DATE CREATED: NOV 30, 2004
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU SET DOCUMENT TEXT           REMOTE PROCEDURE: TIU SET DOCUMENT TEXT
  ORIGINAL NUMBER: 3755
 GENERAL DESCRIPTION:   TIU SET DOCUMENT TEXT 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE

NUMBER: 3764                            IA #: 3764
  DATE CREATED: SEP 11, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: ORWCV VST                       REMOTE PROCEDURE: ORWCV VST
  ORIGINAL NUMBER: 3755
 GENERAL DESCRIPTION:   ORWCV VST This RPC returns a list of appointments and
 admissions for a patient based on parameters that define the beginning and
 ending range for CPRS GUI.  
  
 Input: 
        DFN    [required] = IEN from the Patient file #2 
        BEG    [optional] = Beginning Date 
        END    [optional] = End Date 
        SKIP   [optional] = 0 or null if you want to return the list of 
                         admissions for a patient, otherwise, 1.  
  
 Output: 
        ORVISIT = Return the values in a subscripted array format.  
  
 Return Parameter Description 
  
 -       If successful find, then return the following data: 
 ORVISIT(n)=p1^p2^p3^p4    for n=1,2,3,4,. . .  
  
 Where: p1  :=appointment status code; appointment date/time;IEN from file #44 
 p2  :=appointment date/time p3  :=location name from #44,.01, the external
 value p4  :=appointment status 
  
 -       If problems are encountered, then return: 
    ORVISIT(1)=^error_message^error_message 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE
 SUBSCRIBING DETAILS:   Per RMIM*1*12, this package will be decommissioned in
 the future.  
SUBSCRIBING PACKAGE: TOOLKIT
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   ADDED 5/26/11 
SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL
 SUBSCRIBING DETAILS:   Added 04/16/12 as subscriber 
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 *********************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ************************************
 Effective with HMP*2.0*2 
SUBSCRIBING PACKAGE: MEDICAL HEALTH ESCREENING
 SUBSCRIBING DETAILS:   Added 5/12/21 as Document Only, where VA Custodian
 developer could not approve access because a product developer was not
 available to discuss access. The product is an innovation project that was in
 a pilot at 6 sites for 9 years, then OIT requested a national Class 1 product
 distribution which is effective with MHE*1*0.  
SUBSCRIBING PACKAGE: VETEXT
 SUBSCRIBING DETAILS:   Added 4/11/25 effective with VTEX*1.0 to enable AVS to
 identify a list of appointments and admissions for Veterans.  
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Added to document historic use in VistA, Capri GUI
 (DVBA CAPRI GUI entry in the OPTION file) is using this RPC.  

NUMBER: 3765                            IA #: 3765
  DATE CREATED: SEP 20, 2002
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MPIFA31B
  NAME: $$A31 MPIFA31B                  ID: MPIFA31B
 GENERAL DESCRIPTION:   This entry point will create an A31 HL7 2.4 standard
 message for the patient specified by DFN.  
  STATUS: Active
COMPONENT/ENTRY POINT: $$A31
 COMPONENT DESCRIPTION:   S ERR=$$A31^MPIFA31B(DFN) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN - Patient's Internal Entry Number from the
 Patient file (#2) 
VARIABLES: ERR                          TYPE: Output
 VARIABLES DESCRIPTION:   -1 ^ Error message OR the resulting HL7 message
 number.  
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: TOOLKIT
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH

NUMBER: 3766                            IA #: 3766
  DATE CREATED: SEP 23, 2002            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA3766
 GENERAL DESCRIPTION:   This is a temporary IA to clean up the "AD" x-ref of
 the OPTION (#19) file so IB can delete some old options.  
  
 In this IA, IB will KILL the "AD" cross reference of the whole OPTION (#19)
 file.  Then IB will loop through every entry in the OPTION (#19) file and
 re-build the multiple cross reference using ENALL^DIK.  
  
 This will be performed during a pre-install to ensure the "AD" cross reference
 is clean prior to the patch being installed to delete old options.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 22, 2002
KEYWORDS: OPTION
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
 SUBSCRIBING DETAILS:   This is a one-time clean up to be released with
 IB*2*163 as a pre-init and the routine will be deleted when the install is
 completed.  

NUMBER: 3767                            IA #: 3767
  DATE CREATED: SEP 24, 2002
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RGADTP1
  NAME: PIDP RGADTP1                    ID: RGADTP1
 GENERAL DESCRIPTION:   This API will process the PID segment into an array
 subscripted by the fields that are taken from the PID segment (v2.4).  
  STATUS: Active
COMPONENT/ENTRY POINT: PIDP
 COMPONENT DESCRIPTION:   The API will process the PID segment (v2.4) setting
 the components into an array subscripted by the component name/description.  
VARIABLES: MSG                          TYPE: Input
 VARIABLES DESCRIPTION:   MSG or MSG(I) will contain the PID segment (v2.4).  
VARIABLES: ARRAY                        TYPE: Output
 VARIABLES DESCRIPTION:   This array will be returned populated with the
 components from the PID segment.  The array will be subscripted as follows: 
  
           SSN - patient SSN 
           ICN - patient ICN 
           DFN - sites local identifier 
           MPISSITE - authoritative source (station# of sending site) 
           SEX - patient's SEX 
           MPIDOB - Date of Birth 
           NAME,SURNAME,FIRST,MIDDLE,PREFIX,and SUFFIX - Patient Name 
           MMN - Mother's maiden name 
           POBCITY, POBSTATE - Place of birth city and state 
VARIABLES: HL                           TYPE: Input
 VARIABLES DESCRIPTION:   Array of the Health Level Seven (HL7) application
 variables.  
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA

NUMBER: 3768                            IA #: 3768
  DATE CREATED: SEP 25, 2002            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSOPRA                       NAME: DBIA3768
  ID: PSOPRA
 GENERAL DESCRIPTION:   The purpose of this agreement is to provide the APIs
 necessary for the My HealtheVet system to make refill requests via the
 internet. The APIs will provide the ability to submit a request and get the
 status of each request.  
  STATUS: Active
KEYWORDS: REFILL
KEYWORDS: PRESCRIPTION
KEYWORDS: INTERNET
COMPONENT/ENTRY POINT: $$AP1(PSODFN,PSORX)
 COMPONENT DESCRIPTION:   The AP1 call provides My HealtheVet system to file a
 refill request.  
VARIABLES: PSODFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN Number (Required).  
VARIABLES: PSORX                        TYPE: Input
 VARIABLES DESCRIPTION:   Prescription Number (Required).  
VARIABLES: $$AP1                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns the following status: 
  Value    Meaning 
   -5      DFN does not match RX 
   -4      Unable to resolve patient 
   -3      Unable to resolve prescription 
   -2      Status is pending 
   -1      Result is back but not picked up 
    0      Other error 
    1      Filed in PRESCRIPTION REFILL REQUEST file (#52.43)   
COMPONENT/ENTRY POINT: $$AP2(PSODFN,PSORX)
 COMPONENT DESCRIPTION:   The AP2 call provides the status of a refill request. 
 
VARIABLES: PSODFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN Number (Required).  
VARIABLES: PSORX                        TYPE: Input
 VARIABLES DESCRIPTION:   Prescription Number (Required).  
VARIABLES: $$AP2                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns the following status: 
  Value   Meaning 
   -6     RX not in file #52.43 
   -5     DFN does not match RX 
   -4     Unable to resolve patient 
   -3     Unable to resolve prescription 
   -2     Status is pending 
   -1     Result is back but not picked up 
    1     Filled 
    2     Not Filled 
  n^x     n - Date the refill request was processed.  
          x - The result of the processing. This 
              will be either FILLED or NOT FILLED.  
COMPONENT/ENTRY POINT: $$AP5(PSODFN,PSORX)
 COMPONENT DESCRIPTION:   The purpose of this API is to update PRESCRIPTION
 REFILL REQUEST file #52.43 when My HealtheVet picks up a refill request.  
VARIABLES: PSODFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN Number (Required).  
VARIABLES: PSORX                        TYPE: Input
 VARIABLES DESCRIPTION:   Prescription Number (Required).  
VARIABLES: $$AP5                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns the following status: 
  Value  Meaning 
  -6     RX not in file #52.43 
  -4     Unable to resolve patient 
  -3     Unable to resolve prescription 
  -2     Status is pending 
   0     The update was not successful. This will occur if any of the 
         information provided (PSODFN,PSORX) are invalid 
   1     The update was successful 
COMPONENT/ENTRY POINT: $$AP6(PSODIEN,PSOAP6)
 COMPONENT DESCRIPTION:   The purpose of this API is to provide Outpatient
 Pharmacy Division information to the My HealtheVet system.  
VARIABLES: PSODIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   Outpatient Pharmacy Division IEN.  1. Single Division
 IEN.  2. Delimited list of Division IEN's (IEN1,IEN2,IEN3).  3. Text word
 "ALL".  
VARIABLES: PSOAP6                       TYPE: Both
 VARIABLES DESCRIPTION:   Information return Array.  
 PSOAP6(DIV)=Active(0)/Inactive(1) PSOAP6(DIV,1)=Division Name^Area Code^Phone
 Number PSOAP6(DIV,2,1)=Narrative text 1st line.  PSOAP6(DIV,2,n)=Narrative
 text nth line.  
VARIABLES: $$AP6                        TYPE: Output
 VARIABLES DESCRIPTION:   
  
  0 (Process failure) 
  1 (Process success) 
SUBSCRIBING PACKAGE: MYHEALTHEVET

NUMBER: 3769                            IA #: 3769
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFS
  NAME: PXRM INDEX FOR PTF FILE         ID: PXRMXRFS
 GENERAL DESCRIPTION:   These entry point will set a PTF index entry for ICD0
 and ICD9 data.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: PTF
COMPONENT/ENTRY POINT: SDGPT0
 COMPONENT DESCRIPTION:   This entry point global allows Registration to set
 the Clinical Reminders Index nodes for the ICD0 codes in the PTF file, file #
 45 entries.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. For the S Node, X(1) is set to the
 Surgery/Procedure Date, X(2) is set to ICD0 code (S Node fields #45.01,8;
 45.01,9; 45.01,10; 45.01,11; 45.01,12).  For the P Node, X(1) is set to the
 Procedure Date, X(2) is set to the ICD0 code (P node fields #45.05,4; 45.05,5;
 45.05,6;45.05,7; 45.05,8).  
VARIABLES: NODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Node denotes where the data is from either an "S" for
 Surgery or a "P" for Procedure Node.  
VARIABLES: NUM                          TYPE: Input
 VARIABLES DESCRIPTION:   NUM is set to the Operation Code Number.  
VARIABLES: DA                           TYPE: Input
COMPONENT/ENTRY POINT: SDGPT9
 COMPONENT DESCRIPTION:   This entry point global allows Registration to set
 the Clinical Reminders Index nodes for the ICD9 codes in the  PTF file, file #
 45 entries.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to the DFN, X(2) is set to
 the Admission Date, X(3) is set to the ICD9 code. 
  
 ICD9 from nodes: 45,79; 45,80; 45,79.16 45,79.17; 45,79.18; 45,79.19;
 45,79.20; 45,79.21; 45,79.22; 45,79.22; 45.79.23; 45.79.24.  
VARIABLES: DA                           TYPE: Input
VARIABLES: NODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Node denote where the data is from either DXLS,
 Principal Diagnosis, and ICD 2 through ICD 10.  
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 3770                            IA #: 3770
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFS
  NAME: PXRM INDEX FOR PCE FILES        ID: PXRMXRFS
 GENERAL DESCRIPTION:   These entry points will set indexes for a regular V
 file entry and set indexes for V Files with coded entries.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: PCE
COMPONENT/ENTRY POINT: SVFILE
 COMPONENT DESCRIPTION:   This entry point global allows PCE to set the
 Clinical Reminders Index nodes for regular V File entries.  
VARIABLES: FILENUM                      TYPE: Input
 VARIABLES DESCRIPTION:   Filenum is set to the File Number.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to Item, X(2) is set to
 patient DFN, X(3) is set to the Visit IEN.  
VARIABLES: DA                           TYPE: Input
COMPONENT/ENTRY POINT: SVFILEC
 COMPONENT DESCRIPTION:   This entry point global allows PCE to set the
 Clinical Reminders Index nodes for regular V File with coded entries.  
VARIABLES: FILENUM                      TYPE: Input
 VARIABLES DESCRIPTION:   Filenum is set to the File number.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to Item, X(2) is set to
 patient DFN, X(3) is set to the Visit IEN, X(4) is set to Principal Procedure
 for V CPT entries or X(4) is set to Primary/Secondary for V POV entries.  
VARIABLES: DA                           TYPE: Input
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany

NUMBER: 3771                            IA #: 3771
  DATE CREATED: OCT 01, 2002            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUDHGUI                      NAME: XUDHGUI
  ID: XUDHGUI
 GENERAL DESCRIPTION:   VISTA Graphical User Interface (GUI)-based applications
 can use this API to look up devices. This API retrieves the first 20 devices
 that meet the specifications passed. This API was made available with Kernel
 Patch XU*8.0*220.  
  
 See the Web for more info: http:// http://vista.url//kernel/apis/index.shtml 
  STATUS: Active
COMPONENT/ENTRY POINT: DEVICE
 COMPONENT DESCRIPTION:   VISTA Graphical User Interface (GUI)-based
 applications can use this API to look up devices. This API retrieves the first
 20 devices that meet the specifications passed. This API was made available
 with Kernel Patch XU*8.0*220.  Usage: DEVICE^XUDHGUI(.LIST,STARTING
 POINT,DIRECTION,RIGHT MARGIN RANGE) 
VARIABLES: STARTING POINT               TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This parameter indicates where to start
 the $ORDERing of the Global. "P" will only return devices whose name starts
 with "P"; "P*" will return up to 20 devices the first starting with "P".  
VARIABLES: DIRECTION                    TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This parameter indicates whether to $ORDER
 up or down from the STARTING POINT parameter. The acceptable values are 1 and
 -1: 
VARIABLES: RIGHT MARGIN RANGE           TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This parameter is used to specify a width
 range of devices: Exact Width (e.g., "132-132") 
  
 At Least Width (e.g., "132") 
  
 Range (e.g., "80-132") 
VARIABLES: .LIST                        TYPE: Both
 VARIABLES DESCRIPTION:   (Required) The data will be returned to this array.
 Data is returned in the following format: 
  
   IEN^NAME^DISPLAY NAME^LOCATION^RIGHT MARGIN^PAGE LENGTH 
  DATE ACTIVATED: JAN 22, 2009

NUMBER: 3772                            IA #: 3772
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFK
  NAME: PXRM DELETE FOR PTF FILE INDEX  ID: PXRMXRFK
 GENERAL DESCRIPTION:   These entry point will delete a PTF index entry for
 ICD0 and ICD9 data.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: PTF
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: PXRM INDEX DELETE
COMPONENT/ENTRY POINT: KDGPT0
 COMPONENT DESCRIPTION:   This entry point global allows Registration to delete
 the Clinical Reminders Index nodes for the ICD0 codes in the PTF file, file #
 45 entries.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. For the S Node, X(1) is set to the
 Surgery/Procedure Date, X(2) is set to ICD0 code (S Node fields #45.01,8;
 45.01,9; 45.01,10; 45.01,11; 45.01,12).  For the P Node, X(1) is set to the
 Procedure Date, X(2) is set to the ICD0 code (P node fields #45.05,4; 45.05,5;
 45.05,6;45.05,7; 
  45.05,8).  
VARIABLES: NODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Node denotes where the data is from either an "S" for
 Surgery or a "P" for Procedure Node.  
VARIABLES: NUM                          TYPE: Input
 VARIABLES DESCRIPTION:   NUM is set to the Operation Code Number.  
VARIABLES: DA                           TYPE: Input
COMPONENT/ENTRY POINT: KDGPT9
 COMPONENT DESCRIPTION:   This entry point global allows Registration to delete
 the Clinical Reminders Index nodes for the ICD9 codes in the PTF file, file #
 45 entries.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to the DFN, X(2) is set to
 the Admission Date, X(3) is set to the ICD9 code.  ICD9 from nodes: 45,79;
 45,80; 45,79.16 45,79.17; 45,79.18; 45,79.19; 45,79.20; 45,79.21; 45,79.22;
 45,79.22; 45.79.23; 45.79.24.  
VARIABLES: DA                           TYPE: Input
VARIABLES: NODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Node denote where the data is from either DXLS,
 Principal Diagnosis, and ICD 2 through ICD 10.  
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 3773                            IA #: 3773
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFK
  NAME: PXRM DELETE FOR PCE FILES       ID: PXRMXRFK
 GENERAL DESCRIPTION:   These entry points will delete indexes for a regular V
 file entry and delete indexes for V Files with coded entries 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: PXRM 
KEYWORDS: PXRM INDEX
KEYWORDS: PXRM DELETE INDEX
KEYWORDS: PCE
KEYWORDS: CLINICAL REMINDERS
COMPONENT/ENTRY POINT: KVFILE
 COMPONENT DESCRIPTION:   This entry point global allows PCE to delete the
 Clinical Reminders Index nodes for regular V File entries.  
VARIABLES: FILENUM                      TYPE: Input
 VARIABLES DESCRIPTION:   Filenum is set to the File Number.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to Item, X(2) is set to
 patient DFN, X(3) is set to the Visit IEN.  
VARIABLES: DA                           TYPE: Input
COMPONENT/ENTRY POINT: KVFILEC
 COMPONENT DESCRIPTION:   This entry point global allows PCE to delete the
 Clinical Reminders Index nodes for regular V File with coded entries.  
VARIABLES: filenum                      TYPE: Input
 VARIABLES DESCRIPTION:   Filenum is set to the File number.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to Item, X(2) is set to
 patient DFN, X(3) is set to the Visit IEN, X(4) is set to Principal Procedure
 for V CPT entries or X(4) is set to Primary/Secondary for V POV entries.  
VARIABLES: DA                           TYPE: Input
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany

NUMBER: 3774                            IA #: 3774
  FILE NUMBER: 142.99                   GLOBAL ROOT: GMT(142.99
  DATE CREATED: OCT 04, 2002            CUSTODIAL PACKAGE: HEALTH SUMMARY
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HEALTH SUMMARY PARAMETERS
  ID: GMT(142.99
GLOBAL REFERENCE: GMT(142.99,
FIELD NUMBER: .04                       FIELD NAME: SPOOL DEVICE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Name of a spool device to which Health Summary output is
 directed.  (PDX uses direct global access; NHE uses FileMan) 
 GENERAL DESCRIPTION:   Network Health Exchange (NHE) and Patient Data Exchange
 (PDX) seek to legalize existing code which does a FileMan read, using
 $$GET1^DIQ, of fields in the HEALTH SUMMARY PARAMETERS file #142.99. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE
  ISC: Oakland
SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE
  ISC: Oakland

NUMBER: 3775                            IA #: 3775
  FILE NUMBER: 8930.3                   GLOBAL ROOT: USR(8930.3,
  DATE CREATED: OCT 07, 2002
  CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: TIU DIRECT READ OF USER CLASS FILE
  ID: USR(8930.3,
GLOBAL REFERENCE: USR(8930.3,
FIELD NUMBER: .01                       FIELD NAME: MEMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: EFFECTIVE DATE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: EXPIRATION DATE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: USR(8930.3,'AUC',
 GLOBAL DESCRIPTION:   Multi-field x-ref on Person and User Class.  
 GENERAL DESCRIPTION:   TIU requests the ability to directly read the ASU User
 CLass Memebership File #8930.3 - ^USR(8930.3, specifically the "AUC" cross
 reference and the 0 node fields (#.03) EFFECTIVE DATE and (#.04) EXPIRATION
 DATE to verify the user's membership status.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU
KEYWORDS: USR(8930.3
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 3776                            IA #: 3776
  FILE NUMBER: 8930                     GLOBAL ROOT: USR(8930,
  DATE CREATED: OCT 07, 2002
  CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: TIU DIRECT READ OF USER CLASS FILE
  ID: USR(8930,
GLOBAL REFERENCE: USR(8930,D0,1,
FIELD NUMBER: .01                       FIELD NAME: SUBCLASS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   TIU requests the ability to directly read the ASU User
 CLass File #8930; specifically,  ^USR(8930, using only the subclass multiple
 ^USR(8930,D0,1,D1,0) -- the SUBCLASS field (#.01) to verify a user's
 applicable subclasses and membership status.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU
KEYWORDS: ASU
KEYWORDS: USR(8930
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 3777                            IA #: 3777
  DATE CREATED: OCT 07, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBAGMT
  NAME: DBIA3777                        ID: IBAGMT
 GENERAL DESCRIPTION:   Integrated Billing API to release billing charges that
 were placed on hold as of 10/1/02 (effective date for Geographic Means
 Testing).  The charges will be released from hold when the during the
 conversion process that will determine if the veteran's means test status will 
 become GMT Copay Required or remain MT Copay Required.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$RELHOLD
 COMPONENT DESCRIPTION:   Release billing charges from hold starting with
 effective date for GMT and recalculate charges for patients with GMT Copay
 Required status.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file IEN 
VARIABLES: IBACNT                       TYPE: Output
 VARIABLES DESCRIPTION:   Count of charges that were released from hold.  
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM
 SUBSCRIBING DETAILS:   The API will be called from routine IVMCM6 during the
 Z10 upload process.  

NUMBER: 3778                            IA #: 3778
  DATE CREATED: OCT 07, 2002            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: MCORMN                       NAME: DBIA3778
  ID: MCORMN
 GENERAL DESCRIPTION:   This IA documents the
 HL1^MCORMN(SAP,PATID,BDATE,EDATE,OCC,ATYPE) entry point in Medicine version
 2.3 after the installation of patch MC*2.3*36.  This interface will allow
 Health Summary to get patient data for a brief summary, a brief summary for
 only abnormal values, a full summary, a full captioned summary, and one line
 medicine summary.  This interface is setup in an HL7 compliant manner.  HS
 will need to have the Patient DFN, Beginning Date, Ending Date, # of
 occurrences, and Type of report (Full or Brief).  The
 HL1^MCORMN(SAP,PATID,BDATE,EDATE,OCC,ATYPE) call will retrieve data based on
 the above specifications and returned the data via a ^TMP("MCAR1",$J,#)
 global.  The data that will be returned is the DATE/TIME, PROCEDURE, SUMMARY,
 PROCEDURE SUMMARY, and the PROCEDURE REPORT.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  GOOD ONLY FOR VERSION: 1.0
COMPONENT/ENTRY POINT: HL1(MCSAP,MCDFN,MCB,MCE,MCOCC,MCTYP)
 COMPONENT DESCRIPTION:   This is an entry point that returns the
 ^TMP("MCAR1",$J) global holding the returned information.  
VARIABLES: MCSAP                        TYPE: Input
 VARIABLES DESCRIPTION:   The package that is calling the API.  
VARIABLES: MCDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The patient DFN.  
VARIABLES: MCB                          TYPE: Input
 VARIABLES DESCRIPTION:   Starting date in internal Fileman format.  
VARIABLES: MCE                          TYPE: Input
 VARIABLES DESCRIPTION:   Ending date in internal Fileman format.  
VARIABLES: MCOCC                        TYPE: Input
 VARIABLES DESCRIPTION:   The number of records to return.  
VARIABLES: MCTYP                        TYPE: Input
 VARIABLES DESCRIPTION:   The type of report to be returned.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 3779                            IA #: 3779
  FILE NUMBER: 4.2                      GLOBAL ROOT: DIC(4.2
  DATE CREATED: OCT 07, 2002            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: LOOKUP AND READ                 ID: DIC(4.2
GLOBAL REFERENCE: DIC(4.2,D0)
FIELD NUMBER: 1                         FIELD NAME: FLAGS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Both direct global reads and read with FileMan are OK.  
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   It's OK to look up a domain name using a FileMan call and
 the B and C cross references.  
 GENERAL DESCRIPTION:   Permission is granted to: 
  
 1. Perform a FileMan lookup on file #4.2, DOMAIN, using the B and C cross 
 references. 
  
 2. Read the FLAGS field #1, using either direct global access or FileMan read. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE
  ISC: Oakland
SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE
  ISC: Oakland
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: FEE BASIS
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: LEXICON UTILITY
SUBSCRIBING PACKAGE: MYHEALTHEVET
SUBSCRIBING PACKAGE: IFCAP
 SUBSCRIBING DETAILS:   ADDED 4/21/2011 
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   Patch DG*5.3*884 checks the B cross-reference during
 the pre-installation routine of the patch to confirm the site created the new
 Q-PTI.DNS entry.  
SUBSCRIBING PACKAGE: TOOLKIT
 SUBSCRIBING DETAILS:   Added 4/15/20, effective with XT*7.3*143.  

NUMBER: 3780                            IA #: 3780
  DATE CREATED: OCT 08, 2002            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: MCARAPI                      NAME: DBIA3780
  ID: MCARAPI
 GENERAL DESCRIPTION:   This IA documents the API interface between Medicine
 version 2.3 and Immunology Case Registry version 2.1.  Prior to calling the
 API GET^MCARAPI(RESULTS,MCARDFN,MCSDT,MCEDT,MCFLDS), ICR should check the 
 existence of patch MC*2.3*34.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GET(RESULTS,MCARDFN,MCSDT,MCEDT,MCFLDS)
 COMPONENT DESCRIPTION:   This API returns a list of data from the
 Electrocardiogram file (#691.5) for a patient for a specified start and end
 date.  Only the Electrocardiogram records in the following statuses will be 
 returned in the list: 
   
 RELEASED ON-LINE VERIFIED                                    RELEASED OFF-LINE
 VERIFIED                                      RELEASED NOT VERIFIED            
                             RELEASED ON-LINE VERIFIED OF SUPERSEDED            
           RELEASED OFF-LINE VERIFIED OF SUPERSEDED                        
VARIABLES: RESULTS                      TYPE: Both
 VARIABLES DESCRIPTION:   Input: The global ^TMP array in which to return
 results. (Required) 
  
 Output: Passed by Reference 
         Global array returned in the FM DIQ call 
         format.  
VARIABLES: MCARDFN                      TYPE: Input
 VARIABLES DESCRIPTION:   The Patient DFN (Required).  
VARIABLES: MCSDT                        TYPE: Input
 VARIABLES DESCRIPTION:   The start date of the date range to return the data
 in.  This must be in FM internal format.  (Required) 
VARIABLES: MCEDT                        TYPE: Input
 VARIABLES DESCRIPTION:   The end date of the date range to return the data in. 
 This must be in FM internal format. (Required) 
VARIABLES: MCFLDS                       TYPE: Input
 VARIABLES DESCRIPTION:   A list of fields from file #691.5 to be returned in
 RESULTS.  MCFLDS should contain a list of fields delimited by ";"  (Required) 
  
          example: MCFLDS=".01;11;20..." 
                                                                 
 Example API call: 
                                                
 S RESULTS="^TMP(""NAMESPACE"",$J)"                 D
 GET^MCARAPI(.RESULTS,162,2900101,3021001, 
               ".01;11") 
                                                                     
 return: 
                                                                    
   ^TMP("NAMESPACE",$J,file #,record ien_",",field #,"E")=Data 
   ^TMP("NAMESPACE",$J,subfile #,entry #_","_record ien 
         field of the multiple,"E")=data 
             
         RESULTS(0) will equal one of the following, 
         if the call failed: 
            -1^No Patient DFN.  
            -1^No Start Date Range 
            -1^No End Date Range.  
            -1^Start Date greater than End Date.  
            -1^No fields defined.  
            -1^Global TMP array only.         
   
         If no return array defined,^TMP("MCAPI",$J,0) 
         equals 
            -1^No return array global.  
           
         If no data, RESULTS(0) equals 
            -1^No data for patient.  
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES

NUMBER: 3781                            IA #: 3781
  DATE CREATED: OCT 09, 2002            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine
  NAME: AUTOMATIC ADDITION OF CONTROL CODES
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 3782                            IA #: 3782
  DATE CREATED: OCT 10, 2002
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: CSLVQ
  NAME: Vendor Update API               ID: CSLVQ
 GENERAL DESCRIPTION:   Vendor Update API 
  
 The vendor update operates asynchronously using a callback model. The first
 step in running the vendor update is to build a (typically global) array
 containing the vendor ID, site ID and modification date for each vendor to be
 updated. In addition to the asynchronous (background) entry point, there is a
 synchronous (foreground) call that may be used to interactively retrieve the
 full set of attributes that would be returned for a vendor using the
 background update. The foregound call involves no modification date, and
 returns the vendor attributes unconditionally.  
  
 The format of the array is 
  
 ...
 ARRAY(index) = vendor_id^site_id^timestamp 
 ...
  
 (where timestamp is in Fileman format). 
  
 Note: The timestamp will be the value previously received from CoreFLS, not
 the time the local file was updated or any other timestamp generated within
 VistA.  
  
 Example: 
  
 ^TMP(4375,1)="ACME_DRUGS_AND_SUPPLIES^SAN_FRANCISCO_2^3021008.191213" 
 ^TMP(4375,2)="PEERLESS_AMBULANCE_CO^ATLANTA_7^3020721.1542" 
  
 The name of this array (not a reference) will be one parameter to the vendor
 update.  
  
 Example: 
  
 In this case, the array name is $NA(^TMP(4375)), or simply "^TMP(4375)".  
  
 The second parameter will be an entry point to user supplied routine in the
 format "ENTRY^ROUTINE" (i.e., no parameters will be listed). The actual call
 is 
  
 D UPDATE^CSLVQ(ARRAY,"ENTRY^ROUTINE") 
  
 The array passed as the first parameter may safely be KILLed by the caller at
 any point after this call returns.  
  
 If an error occurs, CSLERR will be set a value in the format 
 "errno^description".  
  
 The callback has one parameter, the name of an array containing one or more
 vendor records. The format of the array is 
  
 ARRAY(index, field_subscript) = value 
  
 Exception: Index value 0 is reserved for system use, so ARRAY(0, ...) must not
 be treated as data. Typically, data will be stored under numeric subscripts
 starting with 1.  
  
 The possible values of field_subscript are 
  
  
         VENDOR_ID 
         VENDOR_NAME 
         TAX_ID 
         INACTIVE_DATE [1] 
         AREA_CODE 
         PHONE_NO 
         FAX_AREA_CODE 
         FAX_NO 
         ADDRESS_LINE_1 
         ADDRESS_LINE_2 
         ADDRESS_LINE_3 
         CITY 
         STATE 
         COUNTY 
         POSTAL_CODE 
         COUNTRY 
         VENDOR_SITE 
         CHAIN_NO 
         COMMENTS [2] 
         LAST_UPDATED [1] 
         PARTICIPATION_CODE 
         VENDOR_TYPE 
         TYPE_OF_VENDOR 
         MEDICARE_ID 
         SPECIALTY_CODE 
         NO_OF_BEDS 
         INSPECTED/ACCREDITED 
         LAST_ASSESSMENT [1] 
         CERTIFIED_MEDICARE/MEDICAID 
         ON_HOLD 
         FEE_VENDOR 
  
 Notes: 
  
 [1] Dates are Fileman format 
  
 [2] A word-processing field will be stored in the format 
  
  
  
 SUBARRAY(1,0)=line 1 SUBARRAY(2,0)=line 2 
 ...
  
 For example, the comments field might be stored as 
  
 ^TMP(1,34567830,"COMMENTS",1,0)="Line 1 of comments 
 ^TMP(1,34567830,"COMMENTS",2,0)="Line 2 of comments 
  
  
 In addition, there are a number of optional vendor attributes. If an attribute
 is present, the appropriate top level subscript will be set. For example, for
 an EDI vendor, we will have 
  
 ARRAY(index,"EDI_VENDOR")=1 
  
 The complete list of attribute subscripts is 
  
  
  
  
 ON_HOLD PRIMARY_PAY_TO RFQ PURCHASING PAY_TO PROCUREMENT_CARD PRICER_EXEMPT 
 FEE_VENDOR EDI_VENDOR PO_HOLD NEW_PAY_HOLD ALL_PAY_HOLD 
  
  
  
 WARNING 
  
 It is the responsibility of the user supplied routine to file the data, 
 performing any necessary locking. It is important to be aware that this 
 routine can be called at any time, and it is possible for it to be called any
 number of background tasks running concurrently.  
  
 A second entry point ("interactive update") exists as a convenience to the
 user/programmer. This entry point is an extrinsic function ($$IUPDT^CSLVQ)
 taking the vendor ID and vendor site name as parameters and returning he name
 of an array containing the vendor attributes (in the same format). In this
 case, no date of last update is supplied, and the vendor data is returned
 unconditionally.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VENDOR
KEYWORDS: UPDATE
COMPONENT/ENTRY POINT: UPDATE
 COMPONENT DESCRIPTION:   This entry point is used to initiate an update. There
 are two parameters, a list of records to be updated (with timestamps) and a
 callback to be invoked by CSL to perform the update. Each subscribing package
 must provide an IA allowing CSL to invoke the callback.  
VARIABLES: data                         TYPE: Input
 VARIABLES DESCRIPTION:   Name of a (typically global) array containing ID,
 Site ID and Date of Last Update for each vendor to be updated, the format is 
  
 ^TMP(4375,1)="248^SAN_FRANCISCO_2^3021008.191213" 
 ^TMP(4375,2)="57^ATLANTA_7^3020721.1542" 
 ...
  
 (This variable should be namespaced.) 
VARIABLES: cback                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the callback invoked by CSL to hand the new
 record values back to the invoking application. It should be in the format
 "TAG^ROUTINE" with no parentheses or argument. It will, of course, be invoked
 with a single argument, but only the tag and routine name should be used.
 (This variable should be namespaced.) 
COMPONENT/ENTRY POINT: UPDATE
COMPONENT/ENTRY POINT: $$IUPDT(vendor_id,site_id)
 COMPONENT DESCRIPTION:   This extrinsic function returns the name of a global
 array containing attributes for a vendor returned unconditionally (without
 regard to the date of last update).  
  
 Example: 
  
 After 
  
 S X=$$IUPDT^CSLVQ(vendor_id,site_id) 
  
 X will be equal to the name of a global array containing attributes for the
 given vendor, e.g.  
  
 ^XTMP("CSLUPDATE5163074","DATA") 
  
 The format of this array is identical to the format of the global array passed
 to the callback in the background update (D UPDATE^CSLVQ).  
VARIABLES: vendor_id                    TYPE: Input
 VARIABLES DESCRIPTION:   This is the (numeric) CoreFLS Vendor ID. (This
 variable should be namespaced.) 
VARIABLES: site_id                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the (alphanumeric) CoreFLS Vendor Site ID.
 (This variable should be namespaced.) 
SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING
SUBSCRIBING PACKAGE: PROSTHETICS

NUMBER: 3783                            IA #: 3783
  FILE NUMBER: 100.21                   GLOBAL ROOT: OR(100.21,
  DATE CREATED: OCT 11, 2002
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PATIENT LIST READ FROM GLOBAL   ID: OR(100.21,
GLOBAL REFERENCE: OR(100.21,D0,10,
FIELD NUMBER: .01                       FIELD NAME: MEMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: VIEW DATE/TIME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Package is reading node 10 of ^OR(100.21  to build an
 array of patients on a specific CPRS patient list.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CPRS
KEYWORDS: OE/RR
KEYWORDS: PATIENT LIST
KEYWORDS: CAPRI
KEYWORDS: AMIE
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany
 SUBSCRIBING DETAILS:   This global is directly read in tag TEAMPTS in routine
 DVBAB1, which supports RPC's for the CAPRI GUI interface to AMIE.  
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 3784                            IA #: 3784
  DATE CREATED: OCT 15, 2002
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSSUTIL1                     NAME: DEA SPECIAL HANDLING CODE
  ID: PSSUTIL1
 GENERAL DESCRIPTION:   Pharmacy Data Management will return a DEA Special
 Handling code to Computerized Patient Record System (CPRS) for an Orderable
 Item, when selected through the CPRS IV Fluids order dialogue, for an
 outpatient. This DEA code will be based on the Dispense Drugs matched to that 
 Orderable Item. If the second parameter in this call is an "A" for Additive,
 then a DEA Special Handling code will only be evaluated for a Dispense Drug if
 that Dispense Drug has at least one active IV Additive matched to the Dispense
 Drug. If the second parameter is an "S" for Solution, then a DEA Special
 Handling code will only be evaluated for a Dispense Drug if that Dispense Drug
 has at least one active IV Solution matched to the Dispense Drug.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DEA
COMPONENT/ENTRY POINT: $$IVDEA(PSSIVOI,PSSIVOIP)
 COMPONENT DESCRIPTION:   This entry point will return a DEA Special Handling
 code for a Pharmacy Orderable Item selected through the CPRS IV Fluids Order
 dialogue.  
VARIABLES: PSSIVOI                      TYPE: Input
 VARIABLES DESCRIPTION:   This variable is the internal entry number from the
 Pharmacy Orderable Item (#50.7) file.  
VARIABLES: PSSIVOIP                     TYPE: Input
 VARIABLES DESCRIPTION:   This variable indicates the type of Orderable Item.
 If the Orderable Item was derived from a selection from the Solutions Tab,
 then an "S" will be passed in. If it was derived from a selection from the
 Additives Tab, then an "A" will be passed in.  
VARIABLES: $$IVDEA                      TYPE: Output
 VARIABLES DESCRIPTION:   This output variable indicates the DEA Special
 Handling code at the Pharmacy Orderable Item level, based on the Dispense
 Drugs matched to the Orderable Item. This call should only be made from the IV
 Fluids dialogue in CPRS, and only when the order is for an outpatient. This
 variable can be one of four values, a "1", a "2", a "3", or null. If a "1" is 
 returned, that indicates that there is at least one active Dispense Drug 
 matched to the Orderable Item that has a DEA Special Handling code that
 contains a "1" or contains a "2". This means a wet signature is required. If a
 "2" is returned, that indicates the first condition wasn't met, and that there
 is at least one active Dispense Drug matched to the Orderable Item 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 Dispense Drugs matched to the Orderable Item. If
 there are no active Dispense Drugs matched to the Orderable Item, then a null
 is returned. In all of these cases, an active Dispense Drug also implies that
 the drug has an active Additive or Solution tied to that drug, depending on
 what is passed in as the second input parameter.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3785                            IA #: 3785
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: OCT 15, 2002
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            ROUTINE: PXRMSXRD
  NAME: PXRM DIRECT READ OF PHARMACY PATIENT FILE
  ID: PXRMSXRD
GLOBAL REFERENCE: PS(55,D0,5,
FIELD NUMBER: .01                       FIELD NAME: ORDER NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 34                        FIELD NAME: STOP DATE/TIME
  LOCATION: 2;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,D0,"IV",D1,0
FIELD NUMBER: .03                       FIELD NAME: STOP DATE/TIME
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,0
FIELD NUMBER: 4                         FIELD NAME: NUMBER OF RECORDS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This piece is the fourth piece of the header node.  
GLOBAL REFERENCE: PS(55,D0,"IV",D1,"AD",
FIELD NUMBER: .01                       FIELD NAME: ADDITIVE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,D0,"IV",D1,"SOL"
FIELD NUMBER: .01                       FIELD NAME: SOLUTION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,D0,5,D1,1
FIELD NUMBER: .01                       FIELD NAME: DISPENSE DRUG
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 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 EMAIL GROUP 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.  
  
 Clinical Reminders requests the ability to do a global read on the Patient
 File #55 specifically, ^PS(55, using multiple fields from the Unit Dose
 multiple, and the IV multiple to populate the new Clinical Reminders Index.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
KEYWORDS: INPATIENT MEDICATION
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: PS
KEYWORDS: PXRM
COMPONENT/ENTRY POINT: PSPA
 COMPONENT DESCRIPTION:   This entry point will loop through file #55 and piece
 out several pieces of data from the Unit Dose multiple and the IV multiple.  
VARIABLES: NERROR                       TYPE: Input
 VARIABLES DESCRIPTION:   NERROR is an array. NERROR is a null array unless an
 error message is generate in this entry point then NERROR will be populated
 with the error message.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3786                            IA #: 3786
  FILE NUMBER: 52.6                     GLOBAL ROOT: PS(52.6,
  DATE CREATED: OCT 15, 2002
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXRMSXRD
  NAME: PXRM RETRIEVE THE DRUG VALUE FROM FILE 52.6
  ID: PXRMSXRD
GLOBAL REFERENCE: PS(52.6,
FIELD NUMBER: 1                         FIELD NAME: GENERIC DRUG
  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 EMAIL GROUP DEV
 using Microsoft Outlook.  
  
 Clinical Reminders request the ability to populate the new Clinical Reminders
 Index with the IEN of the Drug file found in the IV ADDITIVES File, file 52.6
 (piece two of the zero node).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 01, 2006
KEYWORDS: PXRM
KEYWORDS: PS
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: IV ADDITIVES
COMPONENT/ENTRY POINT: PSPA
 COMPONENT DESCRIPTION:   This entry point will piece out the Generic Drug
 Value from File 52.6 for a specific IEN.  
VARIABLES: NERROR                       TYPE: Input
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3787                            IA #: 3787
  DATE CREATED: AUG 06, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3787
 GENERAL DESCRIPTION:   In conjunction with the "fuzzy" lookup capacity that
 will be introduced by the Patient Name Standardization patch DG*5.3*244, a
 flag variable DPTNOFZY has been implemented to allow the suppression of fuzzy
 lookups where appropriate.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DPTNOFZY
KEYWORDS: DPTLK
KEYWORDS: PATIENT NAME STANDARDIZATION
KEYWORDS: DPTNOFZK
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   This agreement allows the IB application to set the
 flag variable DPTNOFZY to suppress fuzzy lookups performed by the DPTLK lookup 
 functionality of the PATIENT file.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany
 SUBSCRIBING DETAILS:   This agreement allows the AR application to set the
 flag variables DPTNOFZY and DPTNOFZK to suppress fuzzy lookups performed by
 the DPTLK.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   This agreement allows INPATIENT MEDICATION to directly
 use the DPTLK lookup functionality with or without the use of the flag
 variables.  

NUMBER: 3788                            IA #: 3788
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: OCT 19, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: Work Phone Number
  ID: DPT(
GLOBAL REFERENCE: DPT(DFN,.13)
FIELD NUMBER: .132                      FIELD NAME: PHONE NUMBER [WORK]
  LOCATION: .13;2                       ACCESS: Read w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   The Patient's work phone number is not available using
 VADPT extracts. OERR/CPRS has permission to retrieve this field using Fileman. 
 

NUMBER: 3789                            IA #: 3789
  DATE CREATED: OCT 20, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGMTU
  NAME: DISPLAY MEANS TEST & ELIGIBILITY INFO
  ID: DGMTU
 GENERAL DESCRIPTION:   Display Means Test info.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DIS
 COMPONENT DESCRIPTION:   Display a patients current means test status, their
 eligibility for care, any deductible information, the date of test and the
 date of completion.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the Patient file.  Pre-exist before
 calling entry point.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Used for Patient Inquiry.  

NUMBER: 3790                            IA #: 3790
  FILE NUMBER: 42                       GLOBAL ROOT: DIC(42,
  DATE CREATED: OCT 20, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: SERVICE OF WARD LOCATION
  ID: DIC(42,
GLOBAL REFERENCE: DIC(42,D0,0)
FIELD NUMBER: .03                       FIELD NAME: SERVICE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   AMIS service for a particular ward location.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   OERR/CPRS needs to check the service of a ward location
 prior to displaying data in the patient inquiry.  

NUMBER: 3791                            IA #: 3791
  DATE CREATED: OCT 20, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: IBARXEU
  NAME: DISPLAY COPAYMENT EXEMPTION INFO
  ID: IBARXEU                           STATUS: Pending
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DISP
 COMPONENT DESCRIPTION:   Displays the 'Medication Copayment Exemption Status'
 and 'Test date' 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to Patient file #2.  
VARIABLES: IBDT                         TYPE: Input
 VARIABLES DESCRIPTION:   Date to check for, if not passed, defaults to DT
 (today).  
  
VARIABLES: NO                           TYPE: Input
 VARIABLES DESCRIPTION:   Number of lines to print (1, 2, or 3).  
VARIABLES: NULL                         TYPE: Input
 VARIABLES DESCRIPTION:   NULL = if zero print 'UNKNOWN', if non-zero quit.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Used for Patient Inquiry.  

NUMBER: 3792                            IA #: 3792
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File
  NAME: PXRM DIRECT READ OF THE PRESCRIPTION FILE 
  ID: PSRX(
GLOBAL REFERENCE: PSRX(0
FIELD NUMBER: 4                         FIELD NAME: NUMBER OF RECORDS 
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This piece is the fourth piece of the header node.  
GLOBAL REFERENCE: PSRX(
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: 8                         FIELD NAME: DAYS SUPPLY
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 31                        FIELD NAME: RELEASED DATE/TIME
  LOCATION: 2;13                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(D0,1,
FIELD NUMBER: 1.1                       FIELD NAME: DAYS SUPPLY
  LOCATION: 0;10                        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: .041                      FIELD NAME: DAYS SUPPLY
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Clinical Reminders requests the ability to do a global
 read on the PRESCRIPTION FILE #52 specifically, ^PSRX(, using multiple fields
 from the Refill multiple, and the Partial Date multiple to populate the new
 Clinical Reminders Index.  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: OUTPATIENT PHARMACY
KEYWORDS: PRESCRIPTION FILE
KEYWORDS: PSRX
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3793                            IA #: 3793
  DATE CREATED: OCT 21, 2002            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PSOPXRM1                     NAME: PSOPXRM1
  ID: PSOPXRM1                          STATUS: Under Revision
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PSRX
 COMPONENT DESCRIPTION:   This entry point returns the internal and external
 values (pieces 1 and 2 respectively) for the following fields of the file 52
 (Prescription): 
  
  
VARIABLES: DAS                          TYPE: Input
 VARIABLES DESCRIPTION:   String containing the subscripts for an entry in the
 ^PSRX global. Example "39433;1;1;0".  
VARIABLES: RXAR                         TYPE: Output
 VARIABLES DESCRIPTION:   Name of the array (or global) which will contain the
 fields returned by this API for the Prescription entry specified by DAS; e.g.,
 "TMP","^TMP($J)".  
COMPONENT/ENTRY POINT: NVA(DAS,.DATA)
 COMPONENT DESCRIPTION:   This entry point returns the pharmacy data in
 reference to a NVA meds.  
VARIABLES: DAS                          TYPE: Input
 VARIABLES DESCRIPTION:   String containing the subscripts for an entry in the
 ^PS(55, global. Example "39432;NVA;1;0".  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   DATA is an array that is passed by reference upon
 completion, DATA will contain fourteen subscripts.  
  
 DATA("ORDERABLE ITEM") DATA("DOSAGE FORM") DATA("DISPENSE DRUG") 
 DATA("DOSAGE") DATA("MEDICATION ROUTE") DATA("SCHEDULE") DATA("STATUS") 
 DATA("DISCONTINUED DATE") DATA("ORDER NUMBER") DATA("START DATE") 
 DATA("DOCUMENTED DATE") DATA("DOCUMENTATED BY") DATA("CLINIC") 
 DATA("INDICATION") 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 3794                            IA #: 3794
  DATE CREATED: MAR 04, 2003            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSNPPIO                      NAME: PUT PMI SHEET INFO IN TMP
  ID: PSNPPIO
 GENERAL DESCRIPTION:   The purpose of this call is to return the appropriate
 Patient Medication Information (PMI) text in a TMP global in the following
 format: 
  
 ^TMP($J,"PSNPMI",0)=DRUG NAME ^TMP($J,"PSNPMI",SECTION,0)=^^# OF LINES OF TEXT 
 ^TMP($J,"PSNPMI",SECTION",n,0)=SECTION TEXT 
  
 The valid values for SECTION are: C - Common Brand Names D - Missing Dose F -
 Phonetics H - How to Take I - Drug Interactions M - Medic Alert N - Notes O -
 Overdose P - Precautions R - Storage S - Side Effects U - Uses W - Warnings Z
 - Disclaimer 
  STATUS: Active
KEYWORDS: pmi
KEYWORDS: PSNPPIO
COMPONENT/ENTRY POINT: $$EN(PSNDRUG,.MSG)
VARIABLES: PSNDRUG                      TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number from the DRUG file (#50).
 Required 
VARIABLES: $$EN                         TYPE: Output
 VARIABLES DESCRIPTION:   0 - no PMI returned 1 - PMI returned in
 ^TMP($J,"PSNPMI" 
VARIABLES: MSG                          TYPE: Output
 VARIABLES DESCRIPTION:   The text describing why the PMI information was not
 returned.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 3795                            IA #: 3795
  DATE CREATED: OCT 22, 2002            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUMF
  NAME: XUMF                            ID: XUMF
 GENERAL DESCRIPTION:   Master File Server API 
  STATUS: Active
KEYWORDS: INSTITUTION
KEYWORDS: MFS
KEYWORDS: CODING SYSTEM
KEYWORDS: IDENTIFIER
COMPONENT/ENTRY POINT: $$IEN(IFN,CDSYS,ID)
 COMPONENT DESCRIPTION:   Returns the IEN for a given IFN, coding system, and
 identifier.  
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   File Number 
VARIABLES: CODSYS                       TYPE: Input
 VARIABLES DESCRIPTION:   Coding system 
VARIABLES: ID                           TYPE: Input
 VARIABLES DESCRIPTION:   Identifier 
VARIABLES: $$IEN                        TYPE: Output
 VARIABLES DESCRIPTION:   Internal Entry Number 

NUMBER: 3796                            IA #: 3796
  FILE NUMBER: 41.1                     GLOBAL ROOT: DGS(41.1,
  DATE CREATED: OCT 23, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: SCHEDULED ADMISSIONS
  ID: DGS(41.1,
GLOBAL REFERENCE: DGS(41.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The name of the patient that is scheduled for a future
 admission at this facility.  
FIELD NUMBER: 2                         FIELD NAME: RESERVATION DATE/TIME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The date/time this patient is scheduled to appear at your
 facility for this admission.  
FIELD NUMBER: 8                         FIELD NAME: WARD
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The name of the ward this patient will be admitted to.  
FIELD NUMBER: 9                         FIELD NAME: TREATING SPECIALTY
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The name of the treating specialty under which this
 patient will be treated.  
FIELD NUMBER: 13                        FIELD NAME: DATE/TIME CANCELLED
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the date and time a scheduled admission was
 cancelled.  
FIELD NUMBER: 17                        FIELD NAME: ADMITTED
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   If the patient was admitted for this scheduled admission,
 then this field will point to the admission in the PATIENT MOVEMENT file #405. 
 
FIELD NUMBER: 5                         FIELD NAME: PROVIDER
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The name of the provider who has ordered this admission.  
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
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   OERR needs to access the SCHEDULED ADMISSION file to
 extract data for the patient inquiry on the CPRS cover sheet.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 **************************************************************************
  
  
 HMP is using the Patient (#.01), Reservation Date/Time (#2), Date/Time 
 Cancelled (#13) and Admitted (#17) fields along with the "B" cross reference.  
  
 This data is collected as part of the patient sync process that syncs the data
 in VistA with the eHMP JSON Data System (JDS). 

NUMBER: 3797                            IA #: 3797
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: OCT 23, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PATIENT ENROLLMENT CLINIC/APPOINTMENTS
  ID: DPT(
GLOBAL REFERENCE: DPT(D0,'DE',D1,0)
FIELD NUMBER: .01                       FIELD NAME: ENROLLMENT CLINIC
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the Hospital Location/Clinic where the patient is
 enrolled.  
FIELD NUMBER: 2                         FIELD NAME: CURRENT STATUS
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field will contain 'I' for inactive if this patient
 is no longer enrolled in this clinic (patient has been discharged from the
 clinic).  
 GLOBAL DESCRIPTION:   ENROLLMENT CLINIC sub-file #2.001 of the PATIENT file
 #2.  
GLOBAL REFERENCE: DPT(DO, S',<date>,0)
FIELD NUMBER: .01                       FIELD NAME: CLINIC
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the Hospital Location/Clinic where the patient
 has/had an appointment.  
FIELD NUMBER: 3                         FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the 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:   This is the reason this patient has this clinic
 appointment. 
 GLOBAL DESCRIPTION:   APPOINTMENT sub-file #2.98 of the PATIENT file #2.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   OERR needs patient enrollment and appointment data to
 display on the patient inquiry on the cover sheet of CPRS.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VPS is reading the fields .01, and 3 to provide a
 patient's appointment status and hospital location to VetLink.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 12/01/2021, effective with DSSV*1.0*1 DSS Class 3
 product Document Only Due to the fact that the DSSV package is going through
 thousands of records,e DSSV is approved to use direct global reads for faster
 turn around.  

NUMBER: 3798                            IA #: 3798
  DATE CREATED: OCT 23, 2002
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: TIUHSOBJ                     NAME: HS OBJECT EXIST IN TIU
  ID: TIUHSOBJ                          STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$EXIST(X)
 COMPONENT DESCRIPTION:   This Function checks the linkage between a Health
 Summary Object and a TIU Object.  
  
 Returns 1  =  Yes, HS Object is being used by TIU 
         0  =  No, HS Object is NOT being used by TIU 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number to the Health Summary Object
 file #142.5 (contained in patch GMTS*2.7*58).  
VARIABLES:  
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Before deleting a Health Summary Object, it is
 important to first check to see if the Health Summary Object is in use by the
 Text Integration Utility (TIU).  This agreement allow Health Summary to call
 EXIST^TIUHSOBJ to check any linkage between a Health Summary Object and TIU
 before deleting the object.  

NUMBER: 3799                            IA #: 3799
  DATE CREATED: OCT 23, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGUTL4                       NAME: DBIA3799
  ID: DGUTL4
 GENERAL DESCRIPTION:   This integration agreement contains the listing of
 supported calls for interaction with the RACE (#10), ETHNICITY (#10.2), and
 RACE AND ETHNICITY COLLECTION METHOD (#10.3) files.  
  
 Calls supported are: 
  1) $$PTR2TEXT^DGUTL4(VALUE,TYPE) 
  2) $$INACTIVE^DGUTL4(VALUE,TYPE) 
  3) $$PTR2CODE^DGUTL4(VALUE,TYPE,CODE) 
  4) $$CODE2PTR^DGUTL4(VALUE,TYPE,CODE) 
  STATUS: Active
KEYWORDS: RACE
KEYWORDS: ETHNICITY
COMPONENT/ENTRY POINT: $$PTR2TEXT
 COMPONENT DESCRIPTION:   Function call converts a pointer to the RACE,
 ETHNICITY, or RACE AND ETHNICITY COLLECTION METHOD file (numbers 10, 10.2, and
 10.3 respectively) into it's displayable name (i.e. .01 field).  
  
  Sample Use 
  ----------
  S VALUE=xxxxx 
  S TYPE=1 
  S X=$$PTR2TEXT^DGUTL4(VALUE,TYPE) 
  W !,"Entry number ",VALUE," in the RACE file is ",X 
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to RACE file (#10), ETHNICITY file (#10.2),
 or RACE AND ETHNICITY COLLECTION METHOD file (#10.3) 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Flag indicating which file VALUE is for 
  1 = Race (default) 
  2 = Ethnicity 
  3 = Collection Method 
VARIABLES: $$PTR2TEXT                   TYPE: Output
 VARIABLES DESCRIPTION:   Text (.01 field).  NULL ("") returned on bad input or
 if there is no code.  
COMPONENT/ENTRY POINT: $$INACTIVE
 COMPONENT DESCRIPTION:   Function call returns whether or not a given entry in
 the RACE or ETHNICITY file (numbers 10 and 10.2 respectively) is marked as
 inactive.  
  
  Sample Use 
  ----------
  S VALUE=xxxxx 
  S TYPE=1 
  S X=$$INACTIVE^DGUTL4(VALUE,TYPE) 
  W:'X !,"Entry is currently active" 
  W:X !,"Entry was inactived on ",$$FMTE^XLFDT($P(X,"^",2)) 
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to RACE file (#10) or ETHNICITY file (#10.2) 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Flag indicating which file VALUE is for 
  1 = Race (default) 
  2 = Ethnicity 
VARIABLES: $$INACTIVE                   TYPE: Output
 VARIABLES DESCRIPTION:   
  0 - Entry not inactive 
  1^Date - Entry inactive (Date in FileMan format) 
          
 Note that 0 (zero) returned on bad input and that collection methods can not
 currently be inactivated 
COMPONENT/ENTRY POINT: $$PTR2CODE
 COMPONENT DESCRIPTION:   Function call converts a pointer to the RACE,
 ETHNICITY, or RACE AND ETHNICITY COLLECTION METHOD file (numbers 10, 10.2, and
 10.3 respectively) into it's abbreviation, HL7, CDC, or PTF code.  
  
  Sample Use 
  ----------
  S VALUE=xxxxx 
  S TYPE=1 
  S CODE=4 
  S X=$$PTR2CODE^DGUTL4(VALUE,TYPE,CODE) 
  S Y=$$PTR2TEXT^DGUTL4(VALUE,TYPE) 
  W:X'="" !,"The PTF code for ",Y," is ",X 
  W:X="" !,Y," does not have a PTF code" 
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to RACE file (#10), ETHNICITY file (#10.2),
 or RACE AND ETHNICITY COLLECTION METHOD file (#10.3) 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   TYPE - Flag indicating which file VALUE is for 
  1 = Race (default) 
  2 = Ethnicity 
  3 = Collection Method 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Flag indicating which code to return 
  1 = Abbreviation (default) 
  2 = HL7 
  3 = CDC (not applicable for Collection Method) 
  4 = PTF 
VARIABLES: $$PTR2CODE                   TYPE: Output
 VARIABLES DESCRIPTION:   Requested code.  NULL ("") returned on bad input or
 if there is no code.  
COMPONENT/ENTRY POINT: $$CODE2PTR
 COMPONENT DESCRIPTION:   Function call converts an abbreviation, HL7, CDC, or
 PTF code into a pointer to it's entry in the RACE, ETHNICITY, or RACE AND
 ETHNICITY COLLECTION METHOD file (numbers 10, 10.2, and 10.3 respectively).  
  
  Sample Use 
  ----------
  S VALUE=xxxxx 
  S TYPE=1 
  S CODE=4 
  S X=$$CODE2PTR^DGUTL4(VALUE,TYPE,CODE) 
  S Y=$$PTR2TEXT^DGUTL4(X,TYPE) 
  W:X !,VALUE," is the PTF code for ",Y 
  W:'X !,VALUE," is not a valid PTF code" 
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   Code to convert 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Flag indicating which file VALUE is from 
  1 = Race (file #10) (default) 
  2 = Ethnicity (file #10.2) 
  3 = Collection Method (file #10.3) 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Flag indicating which code VALUE is for 
  1 = Abbreviation (default) 
  2 = HL7 
  3 = CDC (not applicable for Collection Method) 
  4 = PTF 
VARIABLES: $$CODE2PTR                   TYPE: Output
 VARIABLES DESCRIPTION:   Pointer to file.  0 (zero) returned on bad input or
 if an entry can't be found.  

NUMBER: 3800                            IA #: 3800
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100,
  DATE CREATED: OCT 23, 2002
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PXRM DIRECT READ OF ORDER FILE  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 NUMBER: 4                         FIELD NAME: WHEN ENTERED
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: PATIENT LOCATION
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 21                        FIELD NAME: START DATE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,D0,.1,
FIELD NUMBER: .01                       FIELD NAME: ORDERABLE ITEM
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Clinical Reminders requests the ability to do a global
 read on the Order File #100 specifically, ^OR(100, using multiple fields from
 the Zero node, and the Orderable Items multiple to populate the new Clinical
 Reminders Index.  
  
 Amended: Added 01/18/2023: New functionality was released in patch PXRM*2*45,
 with a compliance date of 09/30/2020, which used the WHEN ENTERED (#4) and 
 PATIENT LOCATION (#6) fields. Clinical Reminders uses these fields to 
 determine whether a patient is pregnant and if that conflicts with the data
 stored in the Women's Health package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORDERS
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
  DATE ACTIVATED: JAN 19, 2023

NUMBER: 3801                            IA #: 3801
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFS
  NAME: PXRM INDEX FOR THE ORDER FILE   ID: PXRMXRFS
 GENERAL DESCRIPTION:   This entry point will set an Order Entry/Results
 Reporting index entry.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: ORDER
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
COMPONENT/ENTRY POINT: SOR
 COMPONENT DESCRIPTION:   This entry point global allows Order Entry/Results
 Reporting to set the Clinical Reminder Index nodes for the Order File, file
 #100 entries.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to the Object of Order,
 X(2) is set to the Orderable Item, X(3) is set to the Start Date.  
VARIABLES: DA                           TYPE: Input
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3802                            IA #: 3802
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: PXRMXRFK
  NAME: PXRM DELETE FOR THE ORDER FILE  ID: PXRMXRFK
 GENERAL DESCRIPTION:   This entry point will delete an Order Entry/Results
 Reporting index entry.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: ORDER ENTRY/RESULTS REPORTING
KEYWORDS: PXRM INDEX
KEYWORDS: PXRM INDEX DELETE
COMPONENT/ENTRY POINT: SOR
 COMPONENT DESCRIPTION:   This entry point global allows Order Entry/Results
 Reporting to delete the Clinical Reminder Index nodes for the Order File, file
 #100 entries.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is an array. X(1) is set to the Object of Order,
 X(2) is set to the Orderable Item, X(3) is set to the Start Date.  
VARIABLES: DA                           TYPE: Input
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3803                            IA #: 3803
  FILE NUMBER: 70                       GLOBAL ROOT: RADPT(
  DATE CREATED: OCT 23, 2002
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PXRM DIRECT READ OF RAD/NUC MED PATIENT FILE
  ID: RADPT(
GLOBAL REFERENCE: RADPT(0
FIELD NUMBER: 4                         FIELD NAME: NUMBER OF RECORDS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This piece is the fourth piece of the header node.  
GLOBAL REFERENCE: RADPT(D0,
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: 2                         FIELD NAME: PROCEDURE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Clinical Reminders requests the ability to do a global
 read on the Rad/Nuc Med patient File, specifically, ^RADPT( using multiple
 fields from the Zero Node, Registered Exams multiple, and the Examinations
 multiple to populate the new Clinical Reminders Index.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RAD/NUC MED
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3804                            IA #: 3804
  DATE CREATED: OCT 24, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCVA1
  NAME: DBIA3804                        ID: IBCVA1
 GENERAL DESCRIPTION:   Patch PRCA*4.5*179 formally releases the MCCF Data Mart
 Extract as an official part of the AR package. All sites have been running the
 monthly MCCF Extract for over 2 years as Class III software. This patch serves 
 to convert the MCCF Data Mart Extract to Class I software. The extract now can
 be run from a menu option instead of programmer mode. It solely performs
 read-only processing on all data.  
  
 The Revenue Office has assigned a name to the extract and the associated 
 database on the VHA/CFO Data Mart. The name is VA Revenue Information (VARI).
 All previous references in the software and documentation have been changed
 from MCCF extract to VARI extract.  
  
 The information and analysis derived from these data are currently shared with
 the VISNs and Facilities CFOs, as well as the Operations and Revenue Offices.
 MCCF Collections supports ADP procurements and other medical care operations.  
  
 This Integration Agreement accesses the following functions within routine 
 IBCVA1: PROC 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
COMPONENT/ENTRY POINT: PROC
 COMPONENT DESCRIPTION:   Builds procedures in array variable IBPROC.  
VARIABLES: IBPROC                       TYPE: Output
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 3805                            IA #: 3805
  FILE NUMBER: 0                        GLOBAL ROOT: DD(
  DATE CREATED: OCT 25, 2002            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: File restriction issues within VistA Blood Bank. 
  ID: DD(
GLOBAL REFERENCE: DD(65,0,'DI')
 GLOBAL DESCRIPTION:   This is an undocumented data dictionary node that
 restricts a file from a VistA user. 
GLOBAL REFERENCE: DD(65.4,0,'DI')
 GLOBAL DESCRIPTION:   This is an undocumented data dictionary node that
 restricts a file from a VistA user.  
GLOBAL REFERENCE: DD(65.5,0,'DI')
 GLOBAL DESCRIPTION:   This is an undocumented data dictionary node that
 restricts a file from a VistA user.  
GLOBAL REFERENCE: DD(66,0,'DI')
 GLOBAL DESCRIPTION:   This is an undocumented data dictionary node that
 restricts a file from a VistA user.  
GLOBAL REFERENCE: DD(66.2,0,'DI')
 GLOBAL DESCRIPTION:   This is an undocumented data dictionary node that
 restricts a file from a VistA user.  
GLOBAL REFERENCE: DD(66.5,0,'DI')
 GLOBAL DESCRIPTION:   This is an undocumented data dictionary node that
 restricts a file from a VistA user.  
GLOBAL REFERENCE: DD(66.9,0,'DI')
 GLOBAL DESCRIPTION:   This is an undocumented data dictionary node that
 restricts a file from a VistA user.  
 GENERAL DESCRIPTION:   The purpose on this integration agreement is to
 restrict certain VistA Blood Bank files from all VistA users.  
  
 The manipulation of data within these files is prohibited.  The following 
 VistA Blood Bank files are targeted for restricted status: 
  
 File Name                 File Number   File Restriction Method 
 ===============================================================
 BLOOD INVENTORY               65         S ^DD(65,0,"DI")="^Y" BLOOD BANK
 UTILITY            65.4       S ^DD(65.4,0,"DI")="^Y" BLOOD DONOR              
     65.5       S ^DD(65.5,0,"DI")="^Y" BLOOD PRODUCT                 66        
 S ^DD(66,0,"DI")="^Y" BLOOD BANK VALIDATION         66.2       S
 ^DD(66.2,0,"DI")="^Y" OPERATION (MSBOS)             66.5       S
 ^DD(66.5,0,"DI")="^Y" BLOOD COMPONENT REQUEST       66.9       S
 ^DD(66.9,0,"DI")="^Y" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: restricted file

NUMBER: 3806                            IA #: 3806
  DATE CREATED: OCT 29, 2002            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FBCSLVUP
  NAME: Add/Update Vendor               ID: FBCSLVUP
 GENERAL DESCRIPTION:   Logic is called by subscribing software  at entry point
 UPD^FBAAVUP.  It is defined with 1 argument in the formal parameter list,
 which is the name of a local or global array.  The array is indexed and could 
 contain one to many vendor records to be added or updated in file 161.2.  The
 call will be executed as:  D UPD^FBAAVUP(ARRAY)    Logic will add a new record
 or access an existing record and update the record with the values contained
 in ARRAY.  
  STATUS: Retired
KEYWORDS: VENDOR
COMPONENT/ENTRY POINT: UPD
 COMPONENT DESCRIPTION:   Once vendor records are available for add or update
 to the Fee Basis Vendor file (161.2), the UPD^FBAAVUP entry point is invoked
 using DO command.  It is defined with one argument in the formal parameter
 list, which is the name of the array, not a reference, containing the vendor
 record(s).  
  
 The format of the array is: 
     
    ARRAY(index, field_subscript) = value 
  
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   The input array is passed to API as the name of a
 global or local arrary (not passed by reference).  The array is indexed and
 could contain one to many vendor records to be added or updated in file 161.2. 
 The format of the array is: ARRAY(index, field_subscript) = value 
  
 The first subscript 'index' will equal a value > 0.  
  
 The second subscript represented as 'field_subscript' are literal values.  
 Data will be stored at the second subscript of the array.  The literal value
 defined at the second subscript will represent the data value stored at that
 node.  The second subscript literal values are listed as follows: 
  
            VENDOR_ID 
            VENDOR_NAME 
            TAX_ID 
            INACTIVE_DATE [1] 
            AREA_CODE 
            PHONE_NO 
            FAX_AREA_CODE 
            FAX_NO 
            ADDRESS_LINE_1 
            ADDRESS_LINE_2 
            ADDRESS_LINE_3 
            CITY 
            STATE 
            COUNTY 
            POSTAL_CODE 
            COUNTRY 
            VENDOR_SITE 
            CHAIN_NO 
            COMMENTS [2] 
            LAST_UPDATED [1] 
            PARTICIPATION_CODE 
            VENDOR_TYPE 
            TYPE_OF_VENDOR 
            MEDICARE_ID 
            SPECIALTY_CODE 
            NO_OF_BEDS 
            INSPECTED/ACCREDITED 
            LAST_ASSESSMENT [1] 
            CERTIFIED_MEDICARE/MEDICAID 
  
SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY

NUMBER: 3807                            IA #: 3807
  DATE CREATED: OCT 25, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCSC61
  NAME: DBIA3807                        ID: IBCSC61
 GENERAL DESCRIPTION:   This Integration Agreement accesses function
 $$NAME^IBCSC61 for the MCCF Data Mart Extract.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
COMPONENT/ENTRY POINT: $$NAME(TYPE,ITEM)
 COMPONENT DESCRIPTION:   Returns name of drug, prosthetic, DRG, or billing
 item.  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Type code.  
VARIABLES: ITEM                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file 80.2, 362.4, 362.5, or 363.21 
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 3808                            IA #: 3808
  DATE CREATED: OCT 25, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCSC4D
  NAME: DBIA3808                        ID: IBCSC4D
 GENERAL DESCRIPTION:   This Integration Agreement accesses function
 SET^IBCSC4D for the MCCF Data Mart Extract.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
COMPONENT/ENTRY POINT: SET(IFN,DXARR,POARR)
 COMPONENT DESCRIPTION:   Returns arrays of diagnonses for a bill.  
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file 399.  
VARIABLES: DXARR                        TYPE: Input
 VARIABLES DESCRIPTION:   Diagnosis array variable name #1, or null.  
VARIABLES: POARR                        TYPE: Input
 VARIABLES DESCRIPTION:   Diagnonsis array variable name #2.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 3809                            IA #: 3809
  DATE CREATED: OCT 25, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCF32
  NAME: DBIA3809                        ID: IBCF32
 GENERAL DESCRIPTION:   This Integration Agreement accesses function 32^IBCF32
 for the MCCF Data Mart Extract.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
COMPONENT/ENTRY POINT: 32
 COMPONENT DESCRIPTION:   Adds occurrence codes/spans to print array.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 3810                            IA #: 3810
  DATE CREATED: OCT 25, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCSC5B
  NAME: DBIA3810                        ID: IBCSC5B
 GENERAL DESCRIPTION:   This Integration Agreement accesses functions
 $$PIN^IBCSC5B and SET^IBCSC5B for the MCCF Data Mart Extract.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
COMPONENT/ENTRY POINT: SET(IFN,PDARR)
 COMPONENT DESCRIPTION:   Returns array of prosthetic items for a bill.  
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file 399.  
VARIABLES: PDARR                        TYPE: Input
 VARIABLES DESCRIPTION:   Prosthetic array variable name.  
COMPONENT/ENTRY POINT: $$PIN(PITEM)
 COMPONENT DESCRIPTION:   Returns name of prosthetic item.  
VARIABLES: PITEM                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file 661.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 3811                            IA #: 3811
  DATE CREATED: OCT 25, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCSC5A
  NAME: DBIA3811                        ID: IBCSC5A
 GENERAL DESCRIPTION:   This Integration Agreement accesses function
 SET^IBCSC5A for the MCCF Data Mart Extract.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
COMPONENT/ENTRY POINT: SET(IFN,RXARR,RXARRP)
 COMPONENT DESCRIPTION:   Returns arrays of RX refills for a bill.  
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file 399.  
VARIABLES: RXARR                        TYPE: Input
 VARIABLES DESCRIPTION:   RX refill array variable name #1.  
VARIABLES: RXARRP                       TYPE: Input
 VARIABLES DESCRIPTION:   RX refill array variable name #2, or null.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 3812                            IA #: 3812
  DATE CREATED: OCT 25, 2002            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGENA
  NAME: DBIA3812                        ID: DGENA
 GENERAL DESCRIPTION:   Patch PRCA*4.5*179 formally releases the MCCF Data Mart
 Extract as an official part of the AR package. All sites have been running the
 monthly MCCF Extract for over 2 years as Class III software. This patch serves
 to convert the MCCF Data Mart Extract to Class I software. The extract now can
 be run from a menu option instead of programmer mode. It solely performs
 read-only processing on all data.  
  
 The Revenue Office has assigned a name to the extract and the associated 
 database on the VHA/CFO Data Mart. The name is VA Revenue Information (VARI).
 All previous references in the software and documentation have been changed
 from MCCF extract to VARI extract.  
  
 The information and analysis derived from these data are currently shared with
 the VISNs and Facilities CFOs, as well as the Operations and Revenue Offices.
 MCCF Collections supports ADP procurements and other medical care operations. 
  
 This Integration Agreement accesses the following functions within routine 
 DGENA: $$FINDPRI 
  
 -----------------------------
 Patch DG*5.3*909 added 4 new fields to the output array DGENR. The Enrollment
 Application System (EAS) have a need to obtain enrollment data from Patient
 Enrollment File (#27.11). This can be accomplished using the API in the
 Registration Enrollment routine DGENA.  
  
 This Integration Agreement accesses the following functions within routine 
 DGENA: $$GET  
     
 Added piece 24, 25, 26, and 27 to the variable NODE from file 27.11.  The 
 DGENR array is set up from the variable NODE.  
  
           CAMP LEJEUNE INDICATED? 
           CAMP LEJEUNE DATE 
           CAMP LEJEUNE CHANGE SITE 
           CAMP LEJEUNE SOURCE 
 -----------------------------
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: DG*5.3*909
COMPONENT/ENTRY POINT: $$FINDPRI(DGENRIEN)
 COMPONENT DESCRIPTION:   Returns a patient's prior enrollment record (pointer
 to file 27.11).  
VARIABLES: DGENRIEN                     TYPE: Both
 VARIABLES DESCRIPTION:   Input: Pointer to file 27.11 
  
 Output: Returns the internal entry number of the prior enrollment for the
 patient if there is one, NULL otherwise.  
COMPONENT/ENTRY POINT: $$FINDCUR(DFN)
 COMPONENT DESCRIPTION:   Returns a patient's current enrollment record
 (pointer to file 27.11).  
VARIABLES: DFN                          TYPE: Both
 VARIABLES DESCRIPTION:   Input: Pointer to file 2.  
  
 Output: Returns the internal entry number of the patient's current enrollment
 if there is one, NULL otherwise.  
COMPONENT/ENTRY POINT: $$GET(DGENRIEN,DGENR)
 COMPONENT DESCRIPTION:   Obtains a record from file 27.11 and loads it into an
 array.  
VARIABLES: DGENRIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file 27.11 
VARIABLES: DGENR                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 on success along with the Enrollment record
 array name, the return array as specified by the DGENR variable returns 0 on
 failure.  
COMPONENT/ENTRY POINT: $$STATUS
 COMPONENT DESCRIPTION:   Returns ENROLLMENT STATUS from the patient's current
 enrollment.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: DGENRIEN                     TYPE: Output
 VARIABLES DESCRIPTION:   Function Value - If the patient has a current
 ENROLLMENT STATUS this function will return its value, otherwise it returns
 NULL.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
 SUBSCRIBING DETAILS:   8/7/15-IVM added as a subscriber by the ICR team when
 it was discovered IVM calls the $$FINDCUR and $$STATUS entry points to the
 DGENA API but were not a subscriber to the ICR.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 8/9/19 for access to $$FINDCUR^DGENA and
 $$GET^DGENA.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 12/7/23, effective with patch SD*5.3*867 to use
 the API's in routine DGENA to retrieve enrollment related data.  
  
 Updated 10/26/26, effective with patch SD*5.3*963 for access to $$STATUS 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Added 3/5/25, effective with patch IB*2.0*770 to use
 the APIs in routine DGENA to retrieve enrollment related data for use by the
 Automated Community Care claims initiative worklists.  
  DATE ACTIVATED: AUG 07, 2015

NUMBER: 3813                            IA #: 3813
  DATE CREATED: OCT 26, 2002            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMTSOBJ                      NAME: HEALTH SUMMARY OBJECTS API
  ID: GMTSOBJ
 GENERAL DESCRIPTION:   This agreement details APIs that may be subscribed to
 to access and edit Health Summary Objects.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HEALTH
KEYWORDS: SUMMARY
KEYWORDS: OBJECTS
KEYWORDS: GMTSOBJ
COMPONENT/ENTRY POINT: $$CRE(NAME)
 COMPONENT DESCRIPTION:   This entry point creates a Health Summary Object with
 the name provided by the input variable NAME.  If a Health Summary object of
 the given name already exist, the user will be able to edit it.  This function
 returns the Internal Entry Number of Object file the object is created or
 edited.  
VARIABLES: NAME                         TYPE: Input
 VARIABLES DESCRIPTION:   Freetext name of an Object to create or edit, 3 to 30
 characters in length.  
COMPONENT/ENTRY POINT: TYPE(NAME)
 COMPONENT DESCRIPTION:   This entry point allows a user to edit a Health
 Summary Type with the name provided by the input variable.  
VARIABLES: NAME                         TYPE: Input
 VARIABLES DESCRIPTION:   Freetext of Health Summary Type to edit, 3 to 30
 characters in length.  
COMPONENT/ENTRY POINT: ARY(DFN,OBJ,ROOT)
 COMPONENT DESCRIPTION:   This entry point will get a Health Summary Object
 (OBJ), using the clinical data based on the patient provided by the input 
 variable DFN, and place the data in a global array defined by the input
 variable ROOT.  
  
 Returns global/local array of Health Summary data 
                                      
    ROOT     ^TMP("GMTSOBJ",$J,DFN) 
    Returns  ^TMP("GMTSOBJ",$J,DFN,#) 
                                      
    ROOT     ^TMP("TIUHSOBJ",$J,"FGBL") 
    Returns  ^TMP("TIUHSOBJ",$J,"FGBL",#) 
                                      
    ROOT     MYARRAY 
    Returns  MYARRAY(#) 
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN for Patient (file #2) 
VARIABLES: OBJ                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN for Health Summary Object (file #142.5) 
VARIABLES: ROOT                         TYPE: Input
 VARIABLES DESCRIPTION:   Closed root (global or local array).  
COMPONENT/ENTRY POINT: GET(DFN,OBJ)
 COMPONENT DESCRIPTION:   This entry point will get a Health Summary Object,
 using the clinical data based on the patient provided by the input variable 
 DFN, and place the data in a global array.  
  
 Returns Global array of Health Summary data in: 
  
     ^TMP("GMTSOBJ",$J,DFN,#,0) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN for Patient (file #2) 
VARIABLES: OBJ                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN for Health Summary Object (file #142.5) 
COMPONENT/ENTRY POINT: $$TIU(DFN,OBJ)
 COMPONENT DESCRIPTION:   Similar to GET(DFN,OBJ), but the output is formatted
 for TIU.  This entry point will get a Health Summary Object (OBJ), using the
 clinical data based on the patient provided by the input variable DFN, and
 place the data in a global array for the Text Integration Utility (TIU).  
  
 Output    Global Root ~@^TIU("TIUHSOBJ",$J,"FGBL") 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN for Patient (file #2).  
VARIABLES: OBJ                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN for Health Summary Object (file #142.5).  
COMPONENT/ENTRY POINT: SHOW(OBJ)
 COMPONENT DESCRIPTION:   This entry point will display a Health Summary Object
 Definition based on the object supplied by the input variable NAME.  It will
 display the definition, followed by a short example.  If you do not need the
 example displayed set the variable GMTSABBR before calling SHOW^GMTSOBJ(OBJ)
 for an abbreviated display.  
VARIABLES: OBJ                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN for Health Summary Object (#142.5).  
COMPONENT/ENTRY POINT: EXTRACT(OBJ,.ARY)
 COMPONENT DESCRIPTION:   This entry point will extract the data from a Health
 Summary Object based on the input variable OBJ, and place the data in the
 array ARY, passed by reference.  This entry point eliminates the need for a
 file type integration agreement for file #142.5.  
VARIABLES: OBJ                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN for Health Summary Object (file #142.5) 
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   Array to use for output, passed by reference.  
VARIABLES: ARY()                        TYPE: Output
 VARIABLES DESCRIPTION:   Array containing subscripts for the Object being
 extracted (IEN), and the fields being extracted, and the format extracted. 
 With the exception of the Description field, all fields are extracted in the
 internal format ("I"), the external format ("E"), and includes the field's
 name ("NAME") and the name in mixed case ("PROMPT").  
  
    ARY(IEN,FIELD,"I") = Internal Value 
    ARY(IEN,FIELD,"E") = External Value 
    ARY(IEN,FIELD,"NAME") = Field Name 
    ARY(IEN,FIELD,"PROMPT") = Mixed Case of Field Name 
COMPONENT/ENTRY POINT: DEF(OBJ,.ARY)
 COMPONENT DESCRIPTION:   This entry point is used to extract an Health Summary
 Object definition and place that definition into the array passed by
 reference.  This entry point will also include an pseudo-example of the
 object.  
VARIABLES: OBJ                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Health Summary Object file (#142.5).  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   Array to receive the definition, passed by reference. 
 
VARIABLES: ARY()                        TYPE: Output
 VARIABLES DESCRIPTION:   Output array containing the Health Summary Object
 Definition and Example, passed by reference.  
  
   ARY("D",0) = # of lines in Definition 
   ARY("D",#) = Definition Text 
   ARY("E",0) = # of lines in Example 
   ARY("E",#) = Example Text 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Text Integration Utilities need these APIs to embed
 Health Summary Objects in TIU documents, to create Health Summary Objects, and
 to edit Health Summary Objects.  

NUMBER: 3814                            IA #: 3814
  FILE NUMBER: 142.5                    GLOBAL ROOT: GMT(142.5,
  DATE CREATED: OCT 27, 2002            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: TIU/HEALTH SUMMARY OBJECT CONVERSION
  ID: GMT(142.5,
GLOBAL REFERENCE: GMT(142.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: OBJECT LABEL
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: HEALTH SUMMARY TYPE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: REPORT PERIOD
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05                       FIELD NAME: SUPPRESS COMPONENTS W/O DATA
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: SUPPRESS HEADER
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .07                       FIELD NAME: PRINT LABEL
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .08                       FIELD NAME: PRINT BLANK LINE AFTER LABEL
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .09                       FIELD NAME: PRINT REPORT DATE AND TIME
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .1                        FIELD NAME: PRINT CONFIDENTIALITY BANNER
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .11                       FIELD NAME: PRINT REPORT HEADERS
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .12                       FIELD NAME: PRINT COMPONENT HEADER
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .13                       FIELD NAME: UNDERLINE COMPONENT HEADERS
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .14                       FIELD NAME: PRINT TIME-OCCURRENCE LIMITS
  LOCATION: 0;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .15                       FIELD NAME: FORCE BLANK LINE
  LOCATION: 0;15                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .16                       FIELD NAME: PRINT DECEASED INFORMATION
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .17                       FIELD NAME: CREATOR
  LOCATION: 0;17                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .18                       FIELD NAME: DATE CREATED
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .19                       FIELD NAME: DATE LAST MODIFIED
  LOCATION: 0;19                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .2                        FIELD NAME: NATIONAL OBJECT
  LOCATION: 0;20                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: GMT(142.5,D0,1)
FIELD NUMBER: .01                       FIELD NAME: OBJECT DESCRIPTION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU
KEYWORDS: HEALTH
KEYWORDS: SUMMARY
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   TIU is granted Read/Write access using Fileman for all
 fields in the Health Summary Object file (#142.50) for the purpose of 
 converting TIU Objects that use Health Summary Types into Health Summary
 Objects.  

NUMBER: 3815                            IA #: 3815
  FILE NUMBER: 1                        GLOBAL ROOT: DD(
  DATE CREATED: OCT 30, 2002            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3815
  ID: DD(
GLOBAL REFERENCE: DD(5.12,0,'UP')
 GENERAL DESCRIPTION:   In order to protect against database corruption, this
 Integration Agreement will be used as a one-time only action to check for the
 existance of the ^DD(5.12,0,"UP") global node prior to the installation of
 patch XU*8*246.  
  
 This node was found to have existed in one of our test accounts, and may exist 
 in one or more Production VistA accounts.  If this node exists during 
 installation of the patch, the install will halt and prompt the user to 
 contact NVS for further assistance.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: UP
KEYWORDS: 5.12
KEYWORDS: GMT
SUBSCRIBING PACKAGE: KERNEL             ISC: Albany
 SUBSCRIBING DETAILS:   This request is for one-time only use during the
 XU*8*246 pre-install.  

NUMBER: 3817                            IA #: 3817
  FILE NUMBER: 45                       GLOBAL ROOT: DGPT(
  DATE CREATED: NOV 15, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PXRM DIRECT READ OF THE PTF FILE
  ID: DGPT(
GLOBAL REFERENCE: DGPT(
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPT(0
FIELD NUMBER: 4                         FIELD NAME: NUMBER OF RECORDS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This piece is the fourth piece of the header node.  
GLOBAL REFERENCE: DGPT(D0,'S',
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(D0,'P',
FIELD NUMBER: .01                       FIELD NAME: PROCEDURE DATE
  LOCATION: 0;1                         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: 4                         FIELD NAME: PROCEDURE CODE 1
  LOCATION: 0;5                         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,70
FIELD NUMBER: 70                        FIELD NAME: DISCHARGE DATE
  LOCATION: 70;1                        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: 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
GLOBAL REFERENCE: DGPT(D0,'M',
FIELD NUMBER: 10                        FIELD NAME: MOVEMENT DATE
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: ICD 1
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: ICD 2
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: ICD 3
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: ICD 4
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: ICD 5
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: ICD 6
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 12                        FIELD NAME: ICD 7
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 13                        FIELD NAME: ICD 8
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: ICD 9
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: ICD 10
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Clinical Reminders requests the ability to do a global
 read on the PTF File, specifically, ^DGPT(, using multiple fields from the
 Zero Node, 70 node, 601, 501, and 401 to populate the new Clinical Reminders
 Index.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: PTF FILE
KEYWORDS: DGPT
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3818                            IA #: 3818
  DATE CREATED: NOV 01, 2002            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMTSDGP                      NAME: PTF PROCEDURES
  ID: GMTSDGP                           STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ICDS
 COMPONENT DESCRIPTION:   Returns Surgical Procedures.  
VARIABLES: PTF                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number to the Patient Treatment File -
 PTF (#45) 
VARIABLES: T1                           TYPE: Input
 VARIABLES DESCRIPTION:   Beginning date in Fileman format.  
VARIABLES: T2                           TYPE: Input
 VARIABLES DESCRIPTION:   Ending date in Fileman format.  
VARIABLES: GMS(<inverse date>)          TYPE: Output
 VARIABLES DESCRIPTION:   Array of surgical ICD procedures performed by
 (inverse) date of surgery within the date range.  
VARIABLES: ICDS(80.1,IEN,FLD)           TYPE: Output
 VARIABLES DESCRIPTION:   Array of ICD procedures performed within the input
 date range by Internal Entry Number of the ICD Procedure file (#80.1) and 
 field number (.01 code and 4 Operation/Procedure) 
COMPONENT/ENTRY POINT: ICDP
 COMPONENT DESCRIPTION:   Returns Non-Surgical ICD Procedures within a date
 range.  
VARIABLES: PTF                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number to the Patient Treatment File -
 PTF (#45).  
VARIABLES: T1                           TYPE: Input
 VARIABLES DESCRIPTION:   Beginning date in Fileman format.  
VARIABLES: T2                           TYPE: Input
 VARIABLES DESCRIPTION:   Ending date in Fileman format.  
VARIABLES: GMS(<inverse date>)          TYPE: Output
 VARIABLES DESCRIPTION:   Array of non-surgical ICD procedures performed by
 inverse date.  
VARIABLES: ICDP(80.1,IEN,FLD)           TYPE: Output
 VARIABLES DESCRIPTION:   Array of non-surgical ICD procedures performed within
 the input date range by Internal Entry Number of the ICD Procedure file 
 (#80.1) and field number (.01 code and 4 Operation/Procedure) 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   OERR needs to call ICDS^GMTSDGP to retrieve surgical
 procedures and ICDP^GMTSDGP to retrieve non-surgical procedures.  

NUMBER: 3819                            IA #: 3819
  FILE NUMBER: 601.2                    GLOBAL ROOT: YTT(601.2,
  DATE CREATED: NOV 01, 2002            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PXRM DIRECT READ OF THE PSYCH INSTRUMENT PATIENT FILE
  ID: YTT(601.2,
GLOBAL REFERENCE: YTT(601,2
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: YTD(601.2,D0,1,
FIELD NUMBER: .01                       FIELD NAME: INSTRUMENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: YTD(601.2,D0,1,D1,1
FIELD NUMBER: .01                       FIELD NAME: COMPLETION DATE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: YTT(601.2,0
FIELD NUMBER: 4                         FIELD NAME: NUMBER OF RECORDS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This piece is the fourth piece of the header node.  
 GENERAL DESCRIPTION:   Clinical Reminders requests the ability to do a global
 read on the Psych Instrument Patient File, specifically, ^YTT(601.2, using the
 first piece from the Zero Node, Instrument multiple, and the Date multiple to
 populate the new Clinical Reminders Index.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM INDEX
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: MENTAL HEALTH
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3820                            IA #: 3820
  FILE NUMBER: 399                      GLOBAL ROOT: DGCR(399,
  DATE CREATED: NOV 03, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA3820-A                      ORIGINAL NUMBER: 3820
  ID: DGCR(399,
GLOBAL REFERENCE: DGCR(399,
FIELD NUMBER: .27                       FIELD NAME: BILL CHARGE TYPE
  LOCATION: 0;27                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .22                       FIELD NAME: DEFAULT DIVISION
  LOCATION: 0;22                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: RATE TYPE
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .18                       FIELD NAME: SC AT TIME OF CARESC
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2                        FIELD NAME: AUTO
  LOCATION: 0;20                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .21                       FIELD NAME: CURRENT BILL PAYER SEQUENCE
  LOCATION: 0;21                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: EVENT DATE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: LOCATION OF CARE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: BILL CLASSIFICATION
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: TIMEFRAME OF BILL
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: PROCEDURE CODING METHOD
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .13                       FIELD NAME: STATUS
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .14                       FIELD NAME: STATUS DATE
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .24                       FIELD NAME: UB92 LOCATION OF CARE
  LOCATION: 0;24                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .25                       FIELD NAME: UB92 BILL CLASSIFICATION
  LOCATION: 0;25                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .26                       FIELD NAME: UB92 TIMEFRAME OF BILL
  LOCATION: 0;26                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: BILL NUMBER
  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: 151                       FIELD NAME: STATEMENT COVERS FROM
  LOCATION: U;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 152                       FIELD NAME: STATEMENT COVERS TO
  LOCATION: U;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 155                       FIELD NAME: IS THIS A SENSITIVE RECORD
  LOCATION: U;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 156                       FIELD NAME: ASSIGNMENT OF BENEFITS
  LOCATION: U;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 163                       FIELD NAME: TREATMENT AUTHORIZATION
  LOCATION: U;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 202                       FIELD NAME: OFFSET AMOUNT
  LOCATION: U1;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 215                       FIELD NAME: ADMITTING DIAGNOSIS
  LOCATION: U2;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 216                       FIELD NAME: COVERED DAYS
  LOCATION: U2;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 217                       FIELD NAME: NON-COVERED DAYS
  LOCATION: U2;3                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 218                       FIELD NAME: PRIMARY PRIOR PAYMENT
  LOCATION: U2;4                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 219                       FIELD NAME: SECONDARY PRIOR PAYMENT
  LOCATION: U2;5                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 220                       FIELD NAME: TERTIARY PRIOR PAYMENT
  LOCATION: U2;6                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: AUTHORIZATION DATE
  LOCATION: S;10                        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: 135                       FIELD NAME: BILL PAYER CARRIER
  LOCATION: MP;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 122                       FIELD NAME: PRIMARY PROVIDER
  LOCATION: M1;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 123                       FIELD NAME: SECONDARY PROVIDER
  LOCATION: M1;3                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 124                       FIELD NAME: TERTIARY PROVIDER
  LOCATION: M1;4                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .11                       FIELD NAME: WHO'S RESPONSIBLE FOR BILL?
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGCR(399,D0,CV,
FIELD NUMBER: .01                       FIELD NAME: VALUE CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: VALUE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGCR(399,D0,RC,
FIELD NUMBER: .01                       FIELD NAME: REVENUE CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: CHARGES
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: UNITS OF SERVICE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: TOTAL
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: BEDSECTION
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: NON-COVERED DAYS
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1                        FIELD NAME: TYPE
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .11                       FIELD NAME: ITEM
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGCR(399,D0,OP,
FIELD NUMBER: .01                       FIELD NAME: OP VISIT DATE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGCR(399,D0,OC,
FIELD NUMBER: .01                       FIELD NAME: OCCURENCE CODE
  LOCATION: OC;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: DGCR(399,D0,CV
 GLOBAL DESCRIPTION:   
  
 GENERAL DESCRIPTION:   Requesting a direct global read of the following fields
 to file 399 Bill Claims. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
KEYWORDS: Data
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany
 SUBSCRIBING DETAILS:   
  

NUMBER: 3821                            IA #: 3821
  FILE NUMBER: 399.1                    GLOBAL ROOT: DGCR(399.1
  DATE CREATED: NOV 04, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA3820-B                      ORIGINAL NUMBER: 3820
  ID: DGCR(399.1
GLOBAL REFERENCE: DGCR(399.1,
FIELD NUMBER: .12                       FIELD NAME: BEDSECTION
  LOCATION: 0                           ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .11                       FIELD NAME: OCCURENCE CODE
  LOCATION: 0                           ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .17                       FIELD NAME: OCCURENCE SPAN
  LOCATION: 0                           ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: CODE
  LOCATION: 0                           ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Accounts Receivable package is requesting a direct
 global read access of file 399.1 MCCR UTILITY file, for the following fields
 listed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany
 SUBSCRIBING DETAILS:   
  

NUMBER: 3822                            IA #: 3822
  FILE NUMBER: 399.3                    GLOBAL ROOT: DGCR(399.3
  DATE CREATED: NOV 04, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA3820-C                      ORIGINAL NUMBER: 3820
  ID: DGCR(399.3
GLOBAL REFERENCE: DGCR(399.3,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The subscribing packages are requesting direct global
 and FileMan read access to file 399.3 RATE TYPE for the NAME field (.01).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCR
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany
 SUBSCRIBING DETAILS:   
  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: AUG 25, 2010

NUMBER: 3823                            IA #: 3823
  FILE NUMBER: 355.3                    GLOBAL ROOT: IBA(355.3
  DATE CREATED: NOV 04, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: DBIA3820-D
  ORIGINAL NUMBER: 3820                 ID: IBA(355.3
GLOBAL REFERENCE: IBA(355.3,
FIELD NUMBER: .03                       FIELD NAME: GROUP NAME
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: GROUP NUMBER
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: TYPE OF PLAN
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Accounts Receivable package is requesting direct
 global read access to file 355.3 GROUP INSURANCE PLAN for the following fields
 listed below.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany
 SUBSCRIBING DETAILS:   
  
  
SUBSCRIBING PACKAGE: PROSTHETICS

NUMBER: 3824                            IA #: 3824
  FILE NUMBER: 362.3                    GLOBAL ROOT: IBA(362.3
  DATE CREATED: NOV 04, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA3820-E
  ORIGINAL NUMBER: 3820                 ID: IBA(362.3
GLOBAL REFERENCE: IBA(362.3,
FIELD NUMBER: .01                       FIELD NAME: DIAGNOSIS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: BILL NUMBER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: ORDER
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Accounts Receivable package is requesting direct
 global read access to file 362.3 IB BILL/CLAIMS DIAGNOSIS for the following 
 fields listed below.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany
 SUBSCRIBING DETAILS:   
  
  

NUMBER: 3825                            IA #: 3825
  FILE NUMBER: 362.4                    GLOBAL ROOT: IBA(362.4
  DATE CREATED: NOV 04, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA3820-F
  ORIGINAL NUMBER: 3820                 ID: IBA(362.4
GLOBAL REFERENCE: IBA(362.4,
FIELD NUMBER: .02                       FIELD NAME: BILL NUMBER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Accounts Receivable package is requesting direct
 global read access to file 362.4 IB BILL/CLAIMS PRESCRIPTION REFILL for field
 (.02) BILL NUMBER on the AIFN1 cross-reference.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany
 SUBSCRIBING DETAILS:   
  

NUMBER: 3826                            IA #: 3826
  FILE NUMBER: 362.5                    GLOBAL ROOT: IBA(362.5
  DATE CREATED: NOV 04, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA3820-G
  ORIGINAL NUMBER: 3820                 ID: IBA(362.5
GLOBAL REFERENCE: IBA(362.5,
FIELD NUMBER: .02                       FIELD NAME: BILL NUMBER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Accounts Receivable package is requesting direct
 global read access to file 362.5 IB BILL/CLAIMS PROSTHETICS for field (.02)
 BILL NUBER.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany

NUMBER: 3827                            IA #: 3827
  FILE NUMBER: 350.9                    GLOBAL ROOT: IBE(350.9
  DATE CREATED: NOV 04, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA3820-H
  ORIGINAL NUMBER: 3820                 ID: IBE(350.9
GLOBAL REFERENCE: IBE(350.9,
FIELD NUMBER: 1.21                      FIELD NAME: MEDICARE PROVIDER NUMBER
  LOCATION: 1;21                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Accounts Receivable package is requesting direct
 global read access to file 350.9 IB SITE PARAMETERS for field (1.21) MEDICARE
 PROVIDER NUMBER.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany

NUMBER: 3828                            IA #: 3828
  FILE NUMBER: 355.1                    GLOBAL ROOT: IBE(355.1
  DATE CREATED: NOV 04, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA3820-I                      ORIGINAL NUMBER: 3820
  ID: IBE(355.1
GLOBAL REFERENCE: IBE(355.1,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: MAJOR CATEGORY
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Accounts Receivable package is requesting direct
 global read access to file 355.1 TYPE OF PLAN for the following fields listed
 below.^ 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: MCCF
KEYWORDS: Information
KEYWORDS: Revenue
KEYWORDS: VARI
KEYWORDS: Extract
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany
 SUBSCRIBING DETAILS:   
  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
 SUBSCRIBING DETAILS:   ADDED JUNE 2009 
  DATE ACTIVATED: NOV 20, 2002

NUMBER: 3829                            IA #: 3829
  FILE NUMBER: 35                       GLOBAL ROOT: DIC(35
  DATE CREATED: NOV 04, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA3829-A
  ORIGINAL NUMBER: 3829                 ID: DIC(35
GLOBAL REFERENCE: DIC(35,
FIELD NUMBER: 1                         FIELD NAME: ABBREVIATION
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Accounts Receivable package requesting a Direct global
 read of the following field (1) ABBREVIATION in file 35 OTHER FEDERAL AGENCY 
 to set into a variable for use by the package.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany

NUMBER: 3830                            IA #: 3830
  FILE NUMBER: 81.3                     GLOBAL ROOT: DIC(81.3
  DATE CREATED: NOV 04, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA3829-B
  ORIGINAL NUMBER: 3829                 ID: DIC(81.3
GLOBAL REFERENCE: DIC(81.3,
FIELD NUMBER: .03                       FIELD NAME: CODE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   
  
 GENERAL DESCRIPTION:   Accounts Receivable package requesting a Direct global
 read of the following field (.03) CODE in file 81.3 CPT MODIFIER to set into a
 variable for use by the package.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany

NUMBER: 3831                            IA #: 3831
  FILE NUMBER: 36                       GLOBAL ROOT: DG(36
  DATE CREATED: NOV 04, 2002            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: DBIA3829-C
  ORIGINAL NUMBER: 3829                 ID: DG(36
GLOBAL REFERENCE: DG(36,
FIELD NUMBER: .111                      FIELD NAME: STREET ADDRESS [LINE 1]
  LOCATION: .11;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .112                      FIELD NAME: STREET ADDRESS [LINE 2]
  LOCATION: .11;2                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .113                      FIELD NAME: STREET ADDRESS [LINE 3]
  LOCATION: .11;3                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .114                      FIELD NAME: CITY
  LOCATION: .11;4                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .115                      FIELD NAME: STATE
  LOCATION: .11;5                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .116                      FIELD NAME: ZIP
  LOCATION: .11;6                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .119                      FIELD NAME: FAX NUMBER
  LOCATION: .11;9                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 131                       FIELD NAME: PHONE NUMBER
  LOCATION: .13;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .11                       FIELD NAME: HOSPITAL PROVIDER NUMBER
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Accounts Receivable package is requesting a Direct
 global read of the following fields in file 36 INSURANCE COMPANY to set into a
 variable for use by the package.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PRCA*4.5*179
KEYWORDS: MCCF
KEYWORDS: Data
KEYWORDS: Mart
KEYWORDS: Extract
KEYWORDS: VARI
KEYWORDS: Revenue
KEYWORDS: Information
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany

NUMBER: 3832                            IA #: 3832
  DATE CREATED: NOV 04, 2002
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMRCHL7
  NAME: Imaging - Consult/Request HL7 message
  ID: GMRCHL7
 GENERAL DESCRIPTION:   The Consult/Request Tracking developer has given
 Imaging permission to call routine GMRCHL7 to generate HL7 message segments. 
  STATUS: Active
COMPONENT/ENTRY POINT: ORC
 COMPONENT DESCRIPTION:   This component will build the ORC message segment in
 HL7 format.  
VARIABLES: GMRCIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry in file
 Request\Consultation (#123).  
VARIABLES: GMRCTL                       TYPE: Input
 VARIABLES DESCRIPTION:   This is order control code for the ORC message
 segment.  
VARIABLES: ORCPLCR                      TYPE: Input
 VARIABLES DESCRIPTION:   This the person who placed the order.  
VARIABLES: MAIN                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the variable that controls whether to perform
 a group updated.  
VARIABLES: GMRCDT                       TYPE: Input
 VARIABLES DESCRIPTION:   The date and time of the activity.  
VARIABLES: ORC                          TYPE: Output
 VARIABLES DESCRIPTION:   The return variable that contains all the input
 values formatted accordingly to HL7 standards.  
COMPONENT/ENTRY POINT: ZSV
 COMPONENT DESCRIPTION:   The submodule for the message segment contains that
 contains the service and display text for the order.  
VARIABLES: GMRC0                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry in file
 Request\Consultation (#123).  
VARIABLES: ZSV                          TYPE: Output
 VARIABLES DESCRIPTION:   The variable that has the HL7 formatted message.  
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Main entry point for sending "GMRC EVSEND OR" event
 message.  
VARIABLES: PATID                        TYPE: Input
 VARIABLES DESCRIPTION:   Same as DFN - Patients internal entry number from
 DPT( 
VARIABLES: GMRCIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry in file
 Request\Consultation (#123).  
VARIABLES: GMRCTYPE                     TYPE: Input
 VARIABLES DESCRIPTION:   Consult type: GMRC REQUEST or GMRC CONSULT 
VARIABLES: RMBED                        TYPE: Input
 VARIABLES DESCRIPTION:   Hospital Room/Bed if patient is hospitalized 
VARIABLES: ORCTRL                       TYPE: Input
 VARIABLES DESCRIPTION:   Code from HL-7 table 119 (Appendix A) Order Control
 Codes 
VARIABLES: GMRCPLCR                     TYPE: Input
 VARIABLES DESCRIPTION:   Person who is entering the order ; usually passed as
 DUZ for new order, "" for existing order 
VARIABLES: VISIT                        TYPE: Input
 VARIABLES DESCRIPTION:   Visit as a DATE/TIME in Fileman Format.  
VARIABLES: GMRCOM                       TYPE: Input
 VARIABLES DESCRIPTION:   Comment array flag: 1 if there is comment array, 0
 otherwise 
VARIABLES: GRPUPD                       TYPE: Input
 VARIABLES DESCRIPTION:   Group update of consults - sends nature as
 MAINTENANCE 
VARIABLES: ACTDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Date/time of activity if sent 
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Imaging is building HL7 messages to provide worklists
 to the HealthCare Provider equipment interface for applications such as:
 Dental, Optometry, etc. The worklist is generated from Consult/Request made to
 clinics that have been defined in Imaging files as recipients of Modality
 worklists.  
  
 Imaging is calling routine GMRCHL7 to build the HL7 message for segments ORC
 and ZSV.  
  
 Updated 2/19/26, effective with patch MAG*3.0*362 Added Component: EN Imaging
 is also calling EN^GMRCHL7 to create the HL7 message for the new
 consult/procedure that is created for a Point of Care device.  These orders 
 are created "on the fly" after the DICOM images are acquired rather than
 beforehand and then scheduled as traditionally done.  

NUMBER: 3833                            IA #: 3833
  DATE CREATED: NOV 04, 2002
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMRCHL72                     NAME: Imaging - GMRCHL72 
  ID: GMRCHL72
 GENERAL DESCRIPTION:   The Consult/Request Tracking developer has given
 Imaging permission to call routine GMRCHL72 to generate HL7 message segments.  
  STATUS: Active
COMPONENT/ENTRY POINT: OBR
 COMPONENT DESCRIPTION:   The submodule to build the OBR message segment in HL7
 format.  
VARIABLES: GMRCIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry in file
 Request\Consultation (#123).  
VARIABLES: RESBY                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal value for person entering/interpreting
 result & signing report.  
VARIABLES: GMRCACDT                     TYPE: Input
 VARIABLES DESCRIPTION:   The date/time of activity in FileMan format.  
VARIABLES: OBR                          TYPE: Output
 VARIABLES DESCRIPTION:   The return variable that contains all the input
 values formatted accordingly to HL7 standards.  
COMPONENT/ENTRY POINT: OBX
 COMPONENT DESCRIPTION:   The submodule to build the OBX message segment in HL7
 format.  
VARIABLES: GMRCIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry in file
 Request\Consultation (#123).  
VARIABLES: OBX                          TYPE: Output
 VARIABLES DESCRIPTION:   The variable that has the HL7 formatted message.  
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Imaging is building HL7 messages to provide worklists
 to the HealthCare Provider equipment interface for applications such as:
 Dental, Optometry, etc. The worklist is generated from Consult/Request made to
 clinics that have been defined in Imaging files as recipients of Modality
 worklists.  
  
 Imaging is calling routine GMRCHL72 to build the HL7 message for segments OBR
 and OBX.  

NUMBER: 3834                            IA #: 3834
  DATE CREATED: NOV 05, 2002
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: CSLEC
  NAME: CSL Cost Center table update    ID: CSLEC
 GENERAL DESCRIPTION:   With the replacement of IFCAP by the CoreFLS system,
 the lookup of a Cost Center value will be done through a local Cost Center
 file. This file will be updated by Event Capture once a year or as needed
 through a query to retrieve active cost centers from the CoreFLS system.  
  
 According to VA handbook 4671.1, cost center codes from 8000** through 8999**
 will cover all possible VHA activities. The cost center file update query will
 issue a request to the CoreFLS system to transmit all cost center codes which
 start with an 8 (8*****) to VistA.  
  
 The CC table update query function call provided to the subscriber will return
 a value of 1 indicating the query sent to CoreFLS system was successful, or a
 0 to indicate the query failed. Example: 
  
   S X=$$CCTBL^CSLEC()    to send CC table update query to CoreFLS system 
  
 After CC table update query is received by the CoreFLS system, an HL7 message
 containing all the cost center codes that start with an 8 (8*****) will be
 generated and transmitted to VistA for processing. The HL7 package in VistA
 will invoke routine CSLEC1 to parse the HL7 message and store the most recent
 active cost center codes into table 536.3. Before the table is updated, the
 active flag for all cost center codes in the table will be changed to 0
 (inactive). If an existing cost center is included in the HL7 message
 received, the active flag will be updated to 1 (active).  
  
 To prevent table 536.3 from being partially updated while processing the HL7 
 messages, the data will be parsed to a temparary file ^XTMP first then to the
 file 536.3.  
     
 In order to decide whether the CC table update is successful or not, the 
 subscriber need to check the 5 parameters provided by the CC table update 
 query. The following 5 parameters will be defined in file 8989.51 through the
 pre-install routine, CSLEC2, when the CSL package is installed at site for the
 first time. The value of these parameters are stored in file 8989.5 and will
 be updated each time the CC table update query is invoked.  
   
   1. CSL CC UPDATE REQUEST   (store the query request date) 
   2. CSL CC UPDATE START     (store the table update start date) 
   3. CSL CC UPDATE END       (store the table update end date) 
   4. CSL CC UPDATE STATUS    (1: processing, 0: completed) 
   5. CSL CC UPDATE NOTE      (store status note) 
     
 The following logic decide whether the update is successful or not: 
  
   If Request date > Start date 
      Start date > End date             table partially updated and 
                                        data is not usable 
      Start date <= End date            table not updated but data is 
                                        usable.  
    
   If Request date <= Start date 
      Start date > End date             table partially updated and data 
                                        is not usable.  
      Start date <= End date            table updated successfully 
   
  STATUS: Active
KEYWORDS: CSLEC
KEYWORDS: cost center
KEYWORDS: CSL cost center
KEYWORDS: cost center update
KEYWORDS: update
COMPONENT/ENTRY POINT: $$CCTBL()
 COMPONENT DESCRIPTION:   This entry point is used to initiate a CC table
 update query. This function will return a 1 to indicate the query has been
 sent successfully or a 0 to indicate the query request failed. Once the query
 is sent, the subscriber of this IA needs to check the 5 parameters described
 in the IA description for the status of query processing.  
VARIABLES: $$CCTBL                      TYPE: Output
 VARIABLES DESCRIPTION:   1 - Indicates the CC table update query transmitted
 successfully.  0 - Indicates the CC table update query failed to transmit.  
SUBSCRIBING PACKAGE: EVENT CAPTURE
 SUBSCRIBING DETAILS:   Event Capture utilizes the Cost Center during the setup
 of the DSS Units in the Event Capture package. User can enter the CC code or
 the CC text. Current lookup of the CC value is done via an interface with
 IFCAP. With the replacement of IFCAP by the CoreFLS system, the lookup of a CC
 value will be done via an interface between Event Capture and CoreFLS.  

NUMBER: 3835                            IA #: 3835
  FILE NUMBER: 120.5                    GLOBAL ROOT: GMR(120.5,
  DATE CREATED: NOV 05, 2002
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PXRM DIRECT READ OF GMRV VITAL MEASUREMENT FILE
  ID: GMR(120.5,
GLOBAL REFERENCE: GMR(120.5,
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME VITALS TAKEN
  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: VITAL TYPE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ENTERED IN ERROR
  LOCATION: 2;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: GMR(120.5,0
FIELD NUMBER: 4                         FIELD NAME: NUMBER OF RECORDS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This piece is the fourth piece of the header node.  
 GENERAL DESCRIPTION:   Clinical Reminders requests the ability to do a global
 read on the GMRV Vital Measurement File, specifically, ^GMR(120.5. using
 multiple fields from the Zero Node to populate the new Clinical Reminders
 Index.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: VITALS
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3836                            IA #: 3836
  DATE CREATED: NOV 06, 2002            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: PSJPXRM1
  NAME: PSJPXRM1                        ID: PSJPXRM1
 GENERAL DESCRIPTION:   The entry point OEL^PSJPXRM1 is provided by Inpatient
 Medciations package to return the detailed information on a patient's unit
 dose or IV order for the Clinical Reminders package to use.  
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
KEYWORDS: PSJPXRM1
COMPONENT/ENTRY POINT: OEL
VARIABLES: DAS                          TYPE: Input
 VARIABLES DESCRIPTION:   The input variable DAS is a string in the following
 format: DFN;FILE IDENTIFIER;ORDER NUMBER;SUBFILE IDENTIFIER;SUBFILE ENTRY #;0 
  
 The Inpatient Medications package will only be using the first 3 pieces to
 extract the order information requested by Clinical Reminders.  
VARIABLES: NAME                         TYPE: Both
 VARIABLES DESCRIPTION:   The variable NAME is used to specify the array name
 that the Clinical Reminders package wishes for the data to be returned in.  
  
  @NAME@("AD",0)        Additive Counter 
  @NAME@("AD",1,0)      ADDITIVE PRINT NAME^ 
                    ADDITIVE DRUG UNIT  (Multiple) 
  @NAME@("ADM")         ADMINISTRATION TIMES 
  @NAME@("ADM",0)       ADMINISTRATION TIMES 
  @NAME@("DD",0)        Dispense Drug COUNTER 
  @NAME@("DD",CNT,0)    DISPENSE DRUG^ 
                    UNITS PER DOSE^ 
                    CORRESPONDING OUTPATIENT NAME^ 
                    RESTRICTION 
  @NAME@("DN")          ORDERABLE ITEM 
  @NAME@("DO")          DOSAGE ORDERED 
  @NAME@("INDICATION")  INDICATION FOR USE 
  @NAME@("INFUS")       INFUSION RATE 
  @NAME@("INST")        INSTRUCTIONS 
  @NAME@("MDR",0)       MEDICATION ROUTE FLAG 
  @NAME@("MDR",1,0)     MEDICATION ROUTE 
                      ABBREVIATION OR NAME 
  @NAME@("MR")          MEDICATION ROUTE 
                      ABBREVIATION OR NAME 
  @NAME@("NOTGIVEN")    'NOT TO BE GIVEN' FLAG 
  @NAME@("OERR")        ORDERS FILE ENTRY 
  @NAME@("PENDRENEWAL") EQUALS 1 IF (ORDER 
                      STATUS="P") AND 
                      (REASON ORDER CREATED="R") 
  @NAME@("PROVIDER")    PRIVIDER IEN^PROVIDER NAME 
  @NAME@("SCH")         SCHEDULE 
  @NAME@("SCH",0)       SCHEDULE 
  @NAME@("SIG",0)       INSTRUCTIONS 
  @NAME@("SIO")         OTHER PRINT INFO 
  @NAME@("SIO",0)       OTHER PRINT INFO 
  @NAME@("SOL",0)       Solutions Counter 
  @NAME@("SOL",1,0)     SOLUTION^VOLUME (Multiple) 
  @NAME@("START")       START DATE/TIME 
  @NAME@("STAT")        STATUS (TEXT) 
  @NAME@("STOP")        STOP DATE/TIME 
  @NAME@("UNITS")       UNITS PER DOSE 
  @NAME@("VERPHARM")    VERIFYING PHARMACIST 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 3837                            IA #: 3837
  FILE NUMBER: 9000011                  GLOBAL ROOT: AUPNPROB(
  DATE CREATED: NOV 18, 2002            CUSTODIAL PACKAGE: PROBLEM LIST
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PXRM DIRECT READ OF THE PROBLEM FILE
  ID: AUPNPROB(
GLOBAL REFERENCE: AUPNPROB(0)
FIELD NUMBER: _                         FIELD NAME: NUMBER OF RECORDS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Number of entries in the file, stored in the fourth caret
 piece of the file header node.  
 GLOBAL DESCRIPTION:   File header node.  
GLOBAL REFERENCE: AUPNPROB(D0,
FIELD NUMBER: .01                       FIELD NAME: DIAGNOSIS
  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: DATE LAST MODIFIED
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: FACILITY
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .12                       FIELD NAME: STATUS
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1.02                      FIELD NAME: CONDITION
  LOCATION: 1;2                         ACCESS: Direct Global Read & 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.14                      FIELD NAME: PRIORITY
  LOCATION: 1;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 80001                     FIELD NAME: SNOMED CT CONCEPT CODE
  LOCATION: 800;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 80201                     FIELD NAME: DATE OF INTEREST
  LOCATION: 802;1                       ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Clinical Reminders requests the ability to do a global
 read on the Problem File, specifically, ^AUPNPROB(, using multiple fields from
 the Zero Node, and the first node to populate the new Clinical Reminders
 Index.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: PROBLEM FILE
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Effective with PXRM*2*45, fields .03, .06, 1.03, 1.04,
 1.05, and 802001 are added to determine whether a patient is pregnant or
 lactating and if that conflicts with the data stored in the Women's Health
 package. This functionality was released in patch PXRM*2*45 with a compliance
 date of 09/30/2020.  
  DATE ACTIVATED: FEB 07, 2023

NUMBER: 3838                            IA #: 3838
  FILE NUMBER: 9000010                  GLOBAL ROOT: AUPNVSIT(
  DATE CREATED: NOV 18, 2002
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: PXRM DIRECT READ OF THE VISIT FILE
  ID: AUPNVSIT(
GLOBAL REFERENCE: AUPNVSIT(
FIELD NUMBER: .01                       FIELD NAME: VISIT/ADMIT DATE&TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Clinical Reminders requests the ability to do a global
 read on the Visit File, specifically, the first piece of the zero node to
 populate the new Clinical Reminders Index. 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: VISIT FILE
KEYWORDS: PXRM INDEX
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3839                            IA #: 3839
  FILE NUMBER: 9000010.18               GLOBAL ROOT: AUPNVCPT(
  DATE CREATED: NOV 18, 2002
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PXRM DIRECT READ OF THE V CPT FILE
  ID: AUPNVCPT(
GLOBAL REFERENCE: AUPNVCPT(
FIELD NUMBER: .01                       FIELD NAME: CPT
  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: .07                       FIELD NAME: PRINCIPAL PROCEDURE
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: AUPNVCPT(0
FIELD NUMBER: 4                         FIELD NAME: NUMBER OF RECORDS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the fourth piece of the header node.  
 GENERAL DESCRIPTION:   Clinical Reminders requests the ability to do a global
 read on the V CPT File, specifically, ^AUPNVCPT(, using multiple fields from
 the Zero Node to populate the new Clinical Reminders Index.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: V CPT FILE
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3840                            IA #: 3840
  DATE CREATED: APR 02, 2003            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Controlled Subscription        TYPE: Routine
  NAME: ACCESS TO DRG FILE #80.2        STATUS: Withdrawn
KEYWORDS: CSV
KEYWORDS: DRG

NUMBER: 3841                            IA #: 3841
  FILE NUMBER: 9000010.11               GLOBAL ROOT: AUPNVIMM(
  DATE CREATED: NOV 18, 2002
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: PXRM DIRECT READ OF THE V IMMUNIZATION FILE
  ID: AUPNVIMM(
GLOBAL REFERENCE: AUPNVIMM
FIELD NUMBER: .01                       FIELD NAME: IMMUNIZATION
  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
GLOBAL REFERENCE: AUPNVIMM(0
FIELD NUMBER: 4                         FIELD NAME: NUMBER OF RECORDS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the fourth piece of the header node.  
 GENERAL DESCRIPTION:   Clinical Reminders requests the ability to do a global
 read on the V Immunization File, specifically, ^AUPNVIMM(, using multiple
 fields from the Zero Node to populate the new Clinical Reminders Index.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: V IMMUNIZTION FILE
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3842                            IA #: 3842
  FILE NUMBER: 9000010.16               GLOBAL ROOT: AUPNVPED(
  DATE CREATED: NOV 18, 2002
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: PXRM DIRECT READ OF THE V PATIENT ED FILE
  ID: AUPNVPED(
GLOBAL REFERENCE: AUPNVEPD(
FIELD NUMBER: .01                       FIELD NAME: TOPIC
  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
GLOBAL REFERENCE: AUPNVPED(0
FIELD NUMBER: 4                         FIELD NAME: NUMBER OF RECORDS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the fourth piece of the header node.  
 GENERAL DESCRIPTION:   Clinical Reminders requests the ability to do a global
 read on the V Patient Ed File, specifically, ^AUPNVPED(, using multiple fields
 from the Zero Node to populate the new Clinical Reminders Index.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: V PATIENT ED
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3843                            IA #: 3843
  FILE NUMBER: 9000010.17               GLOBAL ROOT: AUPNVPOV(
  DATE CREATED: NOV 18, 2002
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PXRM DIRECT READ OF THE V POV FILE
  ID: AUPNVPOV(
GLOBAL REFERENCE: AUPNVPOV(
FIELD NUMBER: .01                       FIELD NAME: POV
  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: .12                       FIELD NAME: PRIMARY/SECONDARY
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: AUPNVPOV(0
FIELD NUMBER: 4                         FIELD NAME: NUMBER OF RECORDS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the fourth piece of the header node.  
 GENERAL DESCRIPTION:   Clinical Reminders requests the ability to do a global
 read on the V POV File, specifically, ^AUPNVPOV(, using multiple fields from
 the Zero Node to populate the new Clinical Reminders Index.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: V POV FILE
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3844                            IA #: 3844
  FILE NUMBER: 9000010.12               GLOBAL ROOT: AUPNVSK(
  DATE CREATED: NOV 18, 2002
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: PXRM DIRECT READ OF THE V SKIN TEST FILE
  ID: AUPNVSK(
GLOBAL REFERENCE: AUPNVSK(
FIELD NUMBER: .01                       FIELD NAME: SKIN TEST
  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
GLOBAL REFERENCE: AUPNVSK(0
FIELD NUMBER: 4                         FIELD NAME: NUMBER OF RECORDS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the fourth piece of the header node.  
 GENERAL DESCRIPTION:   Clinical Reminders requests the ability to do a global
 read on the V Skin Test File, specifically, ^AUPNVSK(, using multiple fields
 from the Zero Node to populate the new Clinical Reminders Index.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: V SKIN TEST FILE
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3845                            IA #: 3845
  FILE NUMBER: 9000010.13               GLOBAL ROOT: AUPNVXAM(
  DATE CREATED: NOV 18, 2002
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File
  NAME: PXRM DIRECT READ OF THE V EXAM FILE
  ID: AUPNVXAM(
GLOBAL REFERENCE: AUPNVXAM(
FIELD NUMBER: .01                       FIELD NAME: EXAM
  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
GLOBAL REFERENCE: AUPNVXAM(0
FIELD NUMBER: 4                         FIELD NAME: NUMBER OF RECORDS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Clinical Reminders requests the ability to do a global
 read on the V Exam File, specifically, ^AUPNVXAM(, using multiple fields from
 the Zero Node to populate the new Clinical Reminders Index.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PXRM INDEX
KEYWORDS: V EXAM FILE
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3846                            IA #: 3846
  DATE CREATED: NOV 19, 2002            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: SDPPRT
  NAME: Print Full (Patient Profile MAS) Report
  ID: SDPPRT
 GENERAL DESCRIPTION:   DBIA for AMIE II (Automated Medical Information
 Exchange) to use routine PRINT^SDPPRT in a remote procedure to print Full
 (Patient Profile MAS) Report.  Integration Agreement will be only until
 Scheduling Replacement begin.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PRINT
 COMPONENT DESCRIPTION:   The routine PRINT^SDPPRT will be used in a remote
 procedure call to print Full (Patient Profile MAS) Report.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN : Patient Identification Number 
VARIABLES: SDR                          TYPE: Input
 VARIABLES DESCRIPTION:   SDR : R/Range or A/All 
VARIABLES: SDBD                         TYPE: Input
 VARIABLES DESCRIPTION:   SDBD : Beginning date 
VARIABLES: SDED                         TYPE: Input
 VARIABLES DESCRIPTION:   SDED : Ending date 
VARIABLES: SDP                          TYPE: Input
 VARIABLES DESCRIPTION:   SDP : Do you want to print the profile? 1 OR 0 
VARIABLES: SDTYP(2)                     TYPE: Input
 VARIABLES DESCRIPTION:   SDTYP(2) : Do you want to print appointments? 1 OR 0 
VARIABLES: SDTYP(1)                     TYPE: Input
 VARIABLES DESCRIPTION:   SDTYP(1) : Do you want to print add/edits? 1 or 0 
VARIABLES: SDTYP(4)                     TYPE: Input
 VARIABLES DESCRIPTION:   SDTYP(4) : Do you want to print enrollments? 1 or 0 
VARIABLES: SDTYP(3)                     TYPE: Input
 VARIABLES DESCRIPTION:   SDTYP(3) : Do you want to print dispositions? 1 OR 0 
VARIABLES: SDTYP(7)                     TYPE: Input
 VARIABLES DESCRIPTION:   SDTYP(7) : Do you want to print team information? 1
 OR 0 
VARIABLES: SDTYP(5)                     TYPE: Input
 VARIABLES DESCRIPTION:   SDTYP(5) : Do you want to print mean test? 1 OR 0 
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany
 SUBSCRIBING DETAILS:   DBIA for AMIE II (Automated Medical Information
 Exchange) to use routine PRINT^SDPPRT in a remote procedure to print Full
 (Patient Profile MAS) Report.  Integration Agreement will be only until
 Scheduling Replacement begin.  

NUMBER: 3847                            IA #: 3847
  FILE NUMBER: 430                      GLOBAL ROOT: PRCA(430,
  DATE CREATED: NOV 20, 2002            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: dba-test
  ID: PRCA(430,
GLOBAL REFERENCE: PRCA(430
FIELD NUMBER: .01                       FIELD NAME: BILL NUMBER
  LOCATION: 0;1
 GENERAL DESCRIPTION:   testing 
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 3848                            IA #: 3848
  FILE NUMBER: 52.41                    GLOBAL ROOT: PS(52.41,'AD',
  DATE CREATED: NOV 20, 2002            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA 3848                       ID: PS(52.41,'AD',
 GENERAL DESCRIPTION:   This agreement gives the Controlled Substance package
 read access to the PENDING OUTPATIENT ORDERS (#52.41) file and the "AD" (LOGIN
 DATE) cross reference. This access will be needed to generate the Digitally
 Signed CS Order Report for controlled substance orders entered electronically
 and signed digitally through Computerized Patient Record System (CPRS) as part 
 of the DEA/VA PKI project.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
  ISC: Birmingham
 SUBSCRIBING DETAILS:   Controlled Substance can do a global read using "AD"
 x-ref to get the needed information from the PENDING OUTPATIENT ORDERS
 (#52.41) file for digitally signed controlled substance orders.  

NUMBER: 3849                            IA #: 3849
  FILE NUMBER: 130                      GLOBAL ROOT: SRF(D0,0
  DATE CREATED: NOV 21, 2002            CUSTODIAL PACKAGE: SURGERY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: Surgery file #130
  ID: SRF(D0,0
GLOBAL REFERENCE: SRF('B',DFN
 GLOBAL DESCRIPTION:   Patient x-ref 
GLOBAL REFERENCE: SRF(D0,0
FIELD NUMBER: .09                       FIELD NAME:  DATE OF OPERATION
  LOCATION: 9                           ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   SRF(DO,0)= (#.09) DATE OF OPERATION 
GLOBAL REFERENCE: SRF(D0,OP
FIELD NUMBER: 26                        FIELD NAME: PRINCIPAL PROCEDURE
  LOCATION: 1                           ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   SRF(DO,OP)= (#26) PRINCIPAL PROCEDURE [1F] 
GLOBAL REFERENCE: SRF(D0,.2
FIELD NUMBER: .22                       FIELD NAME: TIME OPERATION BEGAN
  LOCATION: 2                           ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   SRF(DO,.2)= (#.22) TIME OPERATION BEGAN [2D] 
FIELD NUMBER: .205                      FIELD NAME: TIME PAT IN OR
  LOCATION: 10                          ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   SRF(DO,.2)= (#.205) TIME PAT IN OR [10D] 
FIELD NUMBER: .232                      FIELD NAME: TIME PAT OUT OR 
  LOCATION: 12                          ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   SRF(DO,.2)= (#.232) TIME PAT OUT OR [12D] 
GLOBAL REFERENCE: SRF(D0,30
FIELD NUMBER: 17                        FIELD NAME: CANCEL DATE
  LOCATION: 1                           ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   SRF(DO,30)= (#17) CANCEL DATE [1D] 
GLOBAL REFERENCE: SRF(D0,31
FIELD NUMBER: 10                        FIELD NAME: SCHEDULED START TIME
  LOCATION: 4                           ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   SRF(DO,31)= (#10) SCHEDULED START TIME [4D] 
FIELD NUMBER: 18                        FIELD NAME: CANCEL REASON 
  LOCATION: 8                           ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   SRF(DO,31)= (#18) CANCEL REASON [8P] 
GLOBAL REFERENCE: SRF(D0,REQ
FIELD NUMBER: 36                        FIELD NAME: REQUESTED
  LOCATION: 1                           ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   SRF(DO,REQ)= (#36) REQUESTED [1N] 
 GENERAL DESCRIPTION:   Integration agreement to use the several fields from
 Surgery file #130 in a remote procedure call.  The fields will be used to list
 the patient case status.  
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany
 SUBSCRIBING DETAILS:   Integration agreement to use the several fields from
 Surgery file #130 in a remote procedure call.  The fields will be used to list
 the patient case status.  
  

NUMBER: 3850                            IA #: 3850
  DATE CREATED: JUN 02, 2003
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: CSLARACS
  NAME: Fund Query                      ID: CSLARACS
 GENERAL DESCRIPTION:   Fund Query 
 ----------
  
 Purpose: To allow a user to query coreFLS for funds matching a given query
 string.  
  
 Behavior: The user is prompted for a query string as follows 
  
 Fund: 
  
 and then enters a string that will be used to query coreFLS. Any matching
 values are displayed to the user in the style of ^DIC. A fund may then be
 selected. 
  
 Example: 
  
 >D FUNDQ^CSLARACS 
  
 Fund: 8180 
 . . 
     
    Choose from: 
    1   8180DA100XXXX   GENERAL POST FUND-ALLOCATION 
    2   8180DG100XXXX   GENERAL POST FUND-GENERAL 
    3   8180DM100XXXX   OFFICE OF SECRTY-MUSEUM FUND 
    4   8180DS100XXXX   GENERAL POST FUND-SPECIFIC 
    5   P8180DA100XXX   8180DA100XXXX 
    6   P8180DS100XXX   8180DS100XXXX 
     
 Select QUERY RESULTS SEQUENCE NO: 1  8180DA100XXXX   GENERAL POST 
 FUND-ALLOCATIO N >W CSLY 8180DA100XXXX 
 >
  
  
 Syntax: 
  
 D FUNDQ^CSLARACS 
  
  
 This call has no input variables or parameters 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FUND
COMPONENT/ENTRY POINT: FUNDQ
 COMPONENT DESCRIPTION:   Allow the user to query CoreFLS for a fund or funds
 matching a search string.  
VARIABLES: CSLY                         TYPE: Output
 VARIABLES DESCRIPTION:   This output variable will be equal to the numeric
 value of the selected fund upon success. Upon success it will always be true
 that +CSLY>0.  
  
 Upon failure, we will alway have +CSLY<0 and the value CSLY will be: 
  
 -1 upon network timeout -2 if the user either provided no response or exited
 with "^" when prompted for a fund.  -3 if the user either provided no response
 or exited with "^" when prompted to select a fund from several matching
 values.  -4 if no matching value was found.  -5 if there was an internal
 error.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 3851                            IA #: 3851
  DATE CREATED: NOV 22, 2002
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: CSLARACS                     NAME: BOC/RSC Query
  ID: CSLARACS
 GENERAL DESCRIPTION:   BOC/RSCQuery 
 ----------
  
 Purpose: To allow a user to query coreFLS for BOC or RSC matching a given
 query string.  
  
 Behavior: The user is prompted for a query string as follows 
  
 RSC: 
  
 and then enters a string that will be used to query coreFLS. Any matching
 values are displayed to the user in the style of ^DIC. A fund may then be
 selected. 
  
 Example: 
  
  
 >D BOCQ^CSLARACS 
  
 BOC/RSC: R101 
 . . . 
    1   R10100   INTEREST REVENUE 
     
 Select QUERY RESULTS SEQUENCE NO: 1  R10100   INTEREST REVENUE 
  
  
  
 Syntax: 
  
 D BOCQ^CSLARACS 
  
  
 This call has no input variables or parameters 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: BOC
KEYWORDS: RSC
COMPONENT/ENTRY POINT: BOCQ
 COMPONENT DESCRIPTION:   Allow the user to query for a Budget Object Code
 (BOC) or Revenue Source Code (RSC) matching a search string.  
VARIABLES: CSLY                         TYPE: Output
 VARIABLES DESCRIPTION:   This output variable will be equal to the numeric
 value of the selected BOC or RSC upon success. Upon success it will always be
 true that +CSLY>0.  
  
 Upon failure, we will alway have +CSLY<0 and the value CSLY will be: 
  
 -1 upon network timeout -2 if the user either provided no response or exited
 with "^" when prompted for a BOC (or RSC).  -3 if the user either provided no
 response or exited with "^" when prompted to select a fund from several
 matching values.  -4 if no matching value was found.  -5 if there was an
 internal error.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 3852                            IA #: 3852
  FILE NUMBER: 536.3                    GLOBAL ROOT: CSLCC(
  DATE CREATED: NOV 25, 2002
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CSL Cost Center file 536.3
  ID: CSLCC(
GLOBAL REFERENCE: CSLCC(DA,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Cost Center Code 
FIELD NUMBER: 1                         FIELD NAME: Description
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Cost Center description.  
FIELD NUMBER: 2                         FIELD NAME: Active Flag
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Active Flag will set to 1 at table update to indicate the
 Cost Center code is valid. If set to 0, the Cost Center is invalid.  
 GLOBAL DESCRIPTION:   CSL Cost Center file 
 GENERAL DESCRIPTION:   Event Capture utilizes the Cost Center during the setup
 of the DSS Units in the Event Capture package. With the replacement of IFCAP
 by the CoreFLS system, the lookup of a Cost Center value will be done through
 a local Cost Center file which will be updated by Event Capture once a year or
 as needed through a query to retrieve active cost center from the CoreFLS 
 system.  
  
 The CSL Cost Center file, 536.3, contains 3 fields: Cost Center Code, 
 description, and Active Flag.  
  STATUS: Active
KEYWORDS: CSL Cost Center
KEYWORDS: Cost Center
KEYWORDS: Cost Center code
SUBSCRIBING PACKAGE: EVENT CAPTURE

NUMBER: 3853                            IA #: 3853
  FILE NUMBER: 60                       GLOBAL ROOT: LAB(60,'B',
  DATE CREATED: NOV 26, 2002            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: LAB file 60 'B' x-ref
  ID: LAB(60,'B',
GLOBAL REFERENCE: LAB(60,'B',
FIELD NUMBER: .01                       FIELD NAME: 'B' x-ref
  ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES

NUMBER: 3854                            IA #: 3854
  DATE CREATED: NOV 26, 2002            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: MDAPI1                       NAME: DBIA3854
  ID: MDAPI1
 GENERAL DESCRIPTION:   This IA documents the API interface between Clinical
 Procedures and Clinical Case Registries version 1.0.  Prior to calling the API 
 GET^MDAPI1(RESULTS,MDARDFN,MDSDT,MDEDT,MDFLDS), the subscriber should check
 the existence of patch MD*1*1.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GET(RESULTS,MDARDFN,MDSDT,MDEDT,MDFLDS)
 COMPONENT DESCRIPTION:   This API returns a list of data from the
 Electrocardiogram file (#691.5) for a patient for a specified start and end
 date.  Only the Electrocardiogram records in the following statuses will be 
 returned in the list: 
   
 RELEASED ON-LINE VERIFIED                                       RELEASED
 OFF-LINE VERIFIED                                     RELEASED NOT VERIFIED    
                                     RELEASED ON-LINE VERIFIED OF SUPERSEDED    
                     RELEASED OFF-LINE VERIFIED OF SUPERSEDED                   
    
VARIABLES: RESULTS                      TYPE: Both
 VARIABLES DESCRIPTION:   Input: The global ^TMP array in which to return
 results. (Required) 
   
 Output: Passed by Reference 
         Global array returned in the FM DIQ call 
         format: 
VARIABLES: MDARDFN                      TYPE: Input
 VARIABLES DESCRIPTION:   The patient DFN  (Required).  
VARIABLES: MDSDT                        TYPE: Input
 VARIABLES DESCRIPTION:   The start date of the date range to return the data
 in.  This must be in FM internal format. (Required).  
VARIABLES: MDEDT                        TYPE: Input
 VARIABLES DESCRIPTION:   The end date of the date range to return the data in. 
 This must be in FM internal format.  (Required).  
VARIABLES: MDFLDS                       TYPE: Input
 VARIABLES DESCRIPTION:   A list of fields from file #691.5 to be returned in
 RESULTS.  MDFLDS should contain a list of fields delimited by ";"  (Required). 
 
       example: MDFLDS=".01;11;20..." 
                                                
 Example API call: 
                                                 
 S RESULTS="^TMP(""NAMESPACE"",$J)"                 D
 GET^MDAPI1(.RESULTS,162,2900101,3021001, 
               ".01;11") 
                                                    
 return: 
                                                   
   ^TMP("NAMESPACE",$J,file #,record ien_"," 
        ,field #,"E")=Data   
   ^TMP("NAMESPACE",$J,subfile #,entry #_","_ 
         record ien field of the multiple,"E")=data 
                                                          
         ^TMP("NAMESPACE",$J,0) will equal one of the 
         following, 
           If the call failed: 
             -1^No Patient DFN.  
             -1^No Start Date Range 
             -1^No End Date Range.  
             -1^Start Date greater than End Date.  
             -1^No fields defined.  
                                                     
           If a local variable is defined in RESULTS,  
             ^TMP("MDAPI",$J,0) equals 
             -1^Global TMP array only.         
                                                          
           If no return array defined, ^TMP("MDAPI",$J,0) equals 
             -1^No return array global.  
                                                               
           If no data, ^TMP("NAMESPACE",$J,0) equals 
             -1^No data for patient.  
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES

NUMBER: 3855                            IA #: 3855
  DATE CREATED: DEC 06, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGRP                         NAME: Registration For DGRP Routine
  ID: DGRP
 GENERAL DESCRIPTION:   AMIE will need to access the View Registration report
 for use in the CAPRI GUI application.  This Integration Agreement covers the
 use of EN1^DGRP.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DGRP
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   To use EN1^DGRP in a routine to print patient
 Registration Data.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN : The Patient Identification Number.  
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany
 SUBSCRIBING DETAILS:   
  

NUMBER: 3856                            IA #: 3856
  DATE CREATED: DEC 06, 2002            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: LR7OR2                       NAME: TIU use of LR7OR2
  ID: LR7OR2
 GENERAL DESCRIPTION:   This integration agreement describes a call by TIU to
 LR7OR2.  
  
 Routine: LR7OR2 Component: TEST(.TIUY,DFN,  ,$G(TIUEDT),$G(TIULDT),  ,TIUSTS) 
  
 This call returns labs in the format: 
  
 ^TMP("LRAPI",$J,CTR)=9999999-IVDT_"^"_SSUB_"^"_^TMP("LRRR" 
 ,$J,DFN,SSUB,IVDT,SEQ) 
  
         ^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 by^^Therapeutic 
                flag^Print Name^Accession^Order# 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: TEST
VARIABLES: TIUY                         TYPE: Output
 VARIABLES DESCRIPTION:   Used to store results.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patients DFN 
VARIABLES: TIUEDT                       TYPE: Input
 VARIABLES DESCRIPTION:   Start date to begin search 
VARIABLES: TIULDT                       TYPE: Input
 VARIABLES DESCRIPTION:   End date to end search 
VARIABLES: TIUTST                       TYPE: Used
 VARIABLES DESCRIPTION:   Lab test, from file #60, to do look-up on.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 3857                            IA #: 3857
  DATE CREATED: DEC 03, 2002            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGSEC                        NAME: PATIENT SECURITY CHECK
  ID: DGSEC
 GENERAL DESCRIPTION:   The Record Tracking package has several NOIS calls
 indicating that the patient sensitivity/security check is no longer being done
 on patient lookups.  
  
 This problem surfaced after DG*5.3*223 was released on May 1, 2000. Prior to
 that release, the patient security/sensitivity check was done as part of the
 post-selection process when looking up a patient on the Patient File #2 using
 File Manager.  DG/223 prevented this check if the DIC(0) variable contained an
 "I" which was the case for CIRN.  Record Tracking also contains an "I" when
 doing these lookups, therefore the security check stopped being done. 
  
 The solution is to call ^DGSEC from two routines: RTB for normal patient
 lookup RTDPA for lookup using bar code scanner 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PATIENT SECURITY
COMPONENT/ENTRY POINT: DGSEC
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Y=DFN (IEN OF FILE #2) 
SUBSCRIBING PACKAGE: RECORD TRACKING    ISC: Albany
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   ADDED 9/27/07 

NUMBER: 3858                            IA #: 3858
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: DEC 09, 2002            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Reference EMAIL ADDRESS field in the New Person file 
  ID: VA(200
GLOBAL REFERENCE: VA(200,
FIELD NUMBER: .151                      FIELD NAME: EMAIL ADDRESS
  LOCATION: .15;1                       ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  ISC: Albany
 SUBSCRIBING DETAILS:   
  
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 05/02/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires Read w/Fileman
 access to Field .151 

NUMBER: 3859                            IA #: 3859
  DATE CREATED: DEC 12, 2002            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDAMA201
  NAME: APPOINTMENT DATA BY PATIENT     ID: SDAMA201
 GENERAL DESCRIPTION:   This DBIA contains a list of the supported calls for
 interaction with Appointment data contained in the Patient appointment
 sub-file 2.98 and the Hospital Location appointment sub-file 44.001.  This
 DBIA is associated with Scheduling patch SD*5.3*275, to be released to NVS on 
 1/10/03.  
  
 The supported calls are: 
  
 GETAPPT^SDAMA201 and  $$NEXTAPPT^SDAMA201 
  STATUS: Active
COMPONENT/ENTRY POINT: GETAPPT
 COMPONENT DESCRIPTION:   A call to this entry point will return appointment
 data for a specific patient.  
VARIABLES: SDIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient ID 
VARIABLES: SDFIELDS                     TYPE: Input
 VARIABLES DESCRIPTION:   Appointment fields requested 
VARIABLES: SDAPSTAT                     TYPE: Input
 VARIABLES DESCRIPTION:   Appointment Status filter (optional parameter) 
VARIABLES: SDSTART                      TYPE: Input
 VARIABLES DESCRIPTION:   Start date for appointment search (optional
 parameter) 
VARIABLES: SDEND                        TYPE: Input
 VARIABLES DESCRIPTION:   End date for appointment search (optional parameter) 
VARIABLES: .SDRESULT                    TYPE: Input
 VARIABLES DESCRIPTION:   Variable to contain the count of returned
 appointments (optional parameter) 
VARIABLES: SDIOSTAT                     TYPE: Input
 VARIABLES DESCRIPTION:   Patient Status filter (optional parameter) 
VARIABLES: TMP($J,SDAMA201,GETAPPT)     TYPE: Output
 VARIABLES DESCRIPTION:   The output array ^TMP($J,"SDAMA201","GETAPPT",X,Y)
 will contain the requested appointment data.  Output array 
 ^TMP($J,"SDAMA201","GETAPPT","ERROR",error_code) will contain any errors that
 were generated.  
  
 The calling application is responsible for deleting the temporary globals when
 they have finished processing the appointment data or errors.  
VARIABLES: SDRESULT                     TYPE: Output
 VARIABLES DESCRIPTION:   A count of the returned appointments 
COMPONENT/ENTRY POINT: $$NEXTAPPT
 COMPONENT DESCRIPTION:   A call to this entry point will return appointment
 data for the NEXT appointment for a specific patient.  
VARIABLES: SDIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient ID 
VARIABLES: SDFIELDS                     TYPE: Input
 VARIABLES DESCRIPTION:   Appointment fields requested 
VARIABLES: SDAPSTAT                     TYPE: Input
 VARIABLES DESCRIPTION:   Appointment Status filter (optional parameter) 
VARIABLES: SDIOSTAT                     TYPE: Input
 VARIABLES DESCRIPTION:   Patient Status filter (optional parameter) 
VARIABLES: $$NEXTAPPT                   TYPE: Output
 VARIABLES DESCRIPTION:   -1 if error 0 if no future appointment found 1 if
 future appontment found 
VARIABLES: TMP($J,SDAMA201,NEXTAPPT)    TYPE: Output
 VARIABLES DESCRIPTION:   The output array ^TMP($J,"SDAMA201","NEXTAPPT",X,Y)
 will contain the requested appointment data.  Output array 
 ^TMP($J,"SDAMA201","NEXTAPPT","ERROR",error_code) will contain any errors that
 were generated.  
  
 The calling application is responsible for deleting the temporary globals      
 when they have finished processing the appointment data or errors.             
VARIABLES: SDRESULT                     TYPE: Output
 VARIABLES DESCRIPTION:   A count of the returned appointments 
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: DIETETICS
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI
SUBSCRIBING PACKAGE: MYHEALTHEVET
 SUBSCRIBING DETAILS:   added 9/15/08 
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
SUBSCRIBING PACKAGE: EVENT CAPTURE

NUMBER: 3860                            IA #: 3860
  DATE CREATED: JUL 08, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGPFAPI                      NAME: DGPF PATIENT RECORD FLAG
  ID: DGPFAPI
 GENERAL DESCRIPTION:   
  The purpose of this API is to facilitate the retrieval of specific data 
  that can be used for the displaying of or the reporting of only ACTIVE 
  Patient Record Flag (PRF) Assignment information for a patient.  
  The following Patient Record Flag files are used: 
  (#26.15) PRF NATIONAL FLAG 
  (#26.11) PRF LOCAL FLAG 
  (#26.13) PRF ASSIGNMENT 
  (#26.14) PRF ASSIGNMENT HISTORY 
  (#26.16) PRF TYPE 
  The primary mechanism is from within the Registration package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$GETACT(DFN,TARGET_ROOT)
 COMPONENT DESCRIPTION:   This entry point is used to obtain only ACTIVE
 Patient Record Flag (PRF) Assignment information for a patient that can be
 used for Inquiry and Reporting purposes.  All ACTIVE Patient Record Flag
 Assignments will be returned in a multiple subscripted local or global array,
 "TARGET_ROOT", as a closed root reference.  Note that the TARGET_ROOT will be
 initialized (killed) before being used.  
  
 MUMPS code example of use: 
 -------------------------------------
 I $$GETACT^DGPFAPI(DFN,"DGPFAPI") W !,"DGPFAPI array contains all Active 
 Patient Record Flag Assignments for this patient." 
  
VARIABLES: DFN   [Required]             TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of patient in the PATIENT File
 (#2).  
VARIABLES: $$GETACT                     TYPE: Output
 VARIABLES DESCRIPTION:   
  "0" = No Active Patient Record Flag for 
        the patient 
  "nn" = Total number of Active Flags being 
         returned in array 
         This number will be used to provide a 
         unique number for each Active Patient 
         Record Flag being returned.  
VARIABLES: TARGET_ROOT   [Optional]     TYPE: Both
 VARIABLES DESCRIPTION:   Input: Target Array name that should be passed as 
        a closed root reference.  
        If the parameter is not passed, then the 
        default name of the TARGET_ROOT is set 
        equal to "DGPFAPI".  
  
 Output: A multiple subscripted local or global array 
         format is used.  
  
 TARGET_ROOT(nn,subscript) = field value 
  where: 
   nn = a unique number for each Active Record Flag 
   subscript = a subscript being derived from the 
               following table below 
   field #/file # = global location of data value 
   field value = Internal value^External value 
                 2 piece string caret(^)-delimited 
                 ie... "int^ext" 
  
  subscript  field name             field #/file # 
  ---------  -------------          --------------
  "APPRVBY"  Approved By            (.05)/(#26.14) 
             The field value contains the pointer 
             to the NEW PERSON FILE (#200) of the 
             person approving the assignment of a 
             patient record flag to a patient.  
             The field values will be one of the 
             following two explanations: 
             1. If calling site IS the Originating 
                Site: 
             PIECE 1 = IEN of the (#200) file 
             PIECE 2 = Name of Person 
             2. If calling site NOT the Originating 
                Site: 
             PIECE 1 = .5 
             PIECE 2 = "CHIEF OF STAFF" 
       Note: The .5 (POSTMASTER) internal field 
             value triggers an output transform 
             that converts the external value of 
             "POSTMASTER" to "CHIEF OF STAFF".  
  "ASSIGNDT" Assignment Date/Time   (.02)/(#26.14) 
             The field value contains a FileMan 
             internal^external Date and Time of the 
             initial assignment of the Patient 
             Record Flag.  
  "REVIEWDT" Review Date            (.06)/(#26.13) 
             The field value contains a FileMan 
             internal^external date that the flag 
             assignment is due for review to 
             determine continuing appropriateness.  
  "FLAG"     Flag Name              (.02)/(#26.13) 
             The field value contains the Patient 
             Record Flag name that is assigned to 
             the patient as a variable pointer.  
             PIECE 1 = IEN variable pointer to the 
                       (#26.11) or (#26.15) file 
             PIECE 2 = Name of Flag 
  "FLAGTYPE" Type of Flag (.03)/(#26.11 or #26.15) 
             The field value contains the Record 
             Flag Type usage classification.  
             (i.e. BEHAVIORAL,RESEARCH,CLINICAL) 
             PIECE 1 = IEN of the flag Type 
                       (pointer to (#26.16) file) 
             PIECE 2 = Name of flag Type 
  "CATEGORY" National or Local Flag    (computed) 
             The field value contains the type of 
             category the flag represents.  
             I (NATIONAL) = (#26.15) PRF NATIONAL 
             II (LOCAL)   = (#26.11) PRF LOCAL 
             PIECE 1 = I (NATIONAL) or II (LOCAL) 
             PIECE 2 = (same value as PIECE 1) 
  "OWNER"    Owner Site             (.04)/(#26.13) 
             The field value contains the Site 
             that owns the patient's Record Flag 
             Assignment.  Only the Owner Site may 
             edit a patients flag assignment.  
             PIECE 1 = IEN of the site (pointer 
                       to INSTITUTION FILE (#4)) 
             PIECE 2 = Name of Institution 
  "ORIGSITE" Originating Site       (.05)/(#26.13) 
             The field value contains the Site 
             that first entered the Patient Record 
             Flag on this patient.  
             PIECE 1 = IEN of the site (pointer 
                       to INSTITUTION FILE (#4)) 
             PIECE 2 = Name of Institution "TIUTITLE"  TIU PN TITLE
 (.07)/(#26.11)or(#26.15) 
             The field value contains the pointer 
             to the TIU Progress Note Title that is 
             associated with the Record Flag name.  
             PIECE 1 = IEN of the (#8925.1) file 
             PIECE 2 = TIU DOCUMENT DEFINITION name 
       Note: The "TIUTITLE" subscript will not 
             be returned in the array if the 
             calling site is not the Owner Site.  
  "TIULINK"  TIU PN LINK            (.06)/(#26.14) 
             The field value contains the pointer 
             to the TIU Progress Note that is 
             linked to the patients PRF Assignment 
             History record.  
             PIECE 1 = IEN of the (#8925) file 
             PIECE 2 = TIU DOCUMENT name 
       Note: The "TIULINK" subscript will not 
             be returned in the array if the 
             calling site is not the Owner Site.  
  "NARR"     Assignment Narrative     (1)/(#26.13) 
             (word-processing, multiple nodes) 
             The field value contains the reason 
             narrative for this patients assignment 
             of a Patient Record Flag.  
             The format is in a word-processing 
             value that may contain multiple nodes 
             of text.  Each node of text will be 
             less than 80 characters in length. 
             The format is as follows: 
       TARGET_ROOT(nn,"NARR",line#,0) = text 
        where: 
            nn = a unique number for each Flag 
         line# = a unique number starting at 1 
                 for each word processing line 
                 of narrative text 
             0 = standard subscript format for 
                 the nodes of a FileMan Word 
                 Processing field 
COMPONENT/ENTRY POINT: GETACT(DFN,TARGET_ROOT)
 COMPONENT DESCRIPTION:   See $$GETACT 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   added 4/4/08 
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   effective 6/9/2010 
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   GMTS is subscribing to this API so it can display PRF
 owner site and history information from a Health Summary.  This is targeted
 for release in GMTS*2.7*104 in October 2012.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 ****************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ****************************************************
  
  
 HMP makes calls to the GETACT^DGPFAPI to retrieve Active Patient Record Flag
 (PRF) Assignment information for a patient that can be used for inquiry and
 reporting purposes. 
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 3/11/20 for access to GETACT^DGPFAPI.  
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Added 5/11/20, Effective with Patch DVBA*2.7*220 
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 10/2/24 effective with patch DSIY*1.5*6 to
 support obtaining Patient record flags for patient inquiry and reporting.  
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/2/24 effective with patch DSSO*2.0*8 to
 support obtaining Patient record flags for patient inquiry and reporting.  

NUMBER: 3861                            IA #: 3861
  FILE NUMBER: 123.5                    GLOBAL ROOT: GMR(123.5
  DATE CREATED: JAN 03, 2003
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: REFERENCES TO REQUEST SERVICES FILE
  ID: GMR(123.5
GLOBAL REFERENCE: GMR(123.5,
FIELD NUMBER: .01                       FIELD NAME: SERVICE NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: PROSTHETICS
SUBSCRIBING PACKAGE: SURGERY
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   The MBAA NO PATIENT CSLT LOOKUP RPC will be referencing
 the Service (#.01) field of the Request Services (#123.5) file.  

NUMBER: 3862                            IA #: 3862
  FILE NUMBER: 392.31                   GLOBAL ROOT: DGPT(392.31
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BENEFICIARY TRAVEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3862
  ID: DGPT(392.31
GLOBAL REFERENCE: DGPT(392.31,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointed to by: COREFLS CARRIER field (#14) of the
 BENEFICIARY TRAVEL 
                  CLAIM File (#392) 
                TRANSCRIBED BY field (#10.04) of the INCOMPLETE RECORDS 
                  File (#393) 
                MICROFILM COREFLS VENDOR field (#2.6) of the LOCAL SERIALS 
                   File (#680) 
                DEFAULT COREFLS VENDOR field (#.09) of the LIBRARY 
                   PARAMETERS File (#680.6) 
                COREFLS VENDOR field (#3.01) of the LBRY DISPOSITION File 
                   (#681) 
FIELD NUMBER: .02                       FIELD NAME: VENDOR NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: SITE CODE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: TAX ID
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: AREA CODE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: PHONE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: FAX AREA CODE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: .08                       FIELD NAME: FAX NUMBER
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.01                      FIELD NAME: ADDRESS 1
  LOCATION: 1;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.02                      FIELD NAME: ADDRESS 2
  LOCATION: 1;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.03                      FIELD NAME: ADDRESS 3
  LOCATION: 1;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 2.01                      FIELD NAME: CITY
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2.02                      FIELD NAME: STATE
  LOCATION: 2;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2.03                      FIELD NAME: ZIP CODE
  LOCATION: 2;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3.01                      FIELD NAME: LAST UPDATED DATE
  LOCATION: 3;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 3.02                      FIELD NAME: INACTIVE DATE
  LOCATION: 3;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This file contains vendors of the Core Financial
 Logistics System (coreFLS) used by the site's local system. Entries should
 only be added and updated through the applications interfaced with coreFLS,
 routine DGBTCSL.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING

NUMBER: 3864                            IA #: 3864
  DATE CREATED: JAN 06, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         NAME: SCHEDULING API
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: SCHEDULING
KEYWORDS: API
KEYWORDS: APPOINTMENT

NUMBER: 3865                            IA #: 3865
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BENEFICIARY TRAVEL
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGBTCSL
  NAME: DBIA3865                        ID: DGBTCSL
 GENERAL DESCRIPTION:   The DGBTCSL routine is the interface for the Patient
 Management System packages (Beneficiary Travel, Incomplete Records Tracking,
 and Library) to the CoreFLS system.  This routine consists of a module for a 
 standalone query to add CoreFLS vendors to the LOCAL VENDOR file (#392.31). 
 It also handles output transform and Filemanager calls from Library and
 Beneficiary Travel templates and routines when edits to there pointed fields
 to the LOCAL VENDOR file (#392.31) are made.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: STAND
 COMPONENT DESCRIPTION:   Component used by Beneficiary Travel, Incomplete
 Records Tracking, and Library to add CoreFLS vendors into the LOCAL VENDOR
 file (#392.31) through standalone menus.  
  
 Makes a check for the COMMUNICATIONS SERVICE LIBRARY (CSL) package, then 
 queries the CoreFLS system for a vendor.  Selected vendor will be added to the
 LOCAL VENDOR file (#392.31).  
COMPONENT/ENTRY POINT: PREV
 COMPONENT DESCRIPTION:   Component used by Beneficiary Travel and Library.  
  
 Called by the output transform, it sets a variable to the current LOCAL VENDOR
 file (#392.31) value.  It then uses this value for evaluation when called in
 the input transform.  
  
 PREV(Y) ; called from OUTPUT TRANSFORM 
         ; input:  Y     := internal value sent by Output Transform 
         ; output: Y     := converted to external value 
         ;         DGBTV := internal value 
COMPONENT/ENTRY POINT: AFTER
 COMPONENT DESCRIPTION:   Component used by Beneficiary Travel and Library.  
  
 Called from an input template or DR string which sends four parameters 
 including the evaluated variable from the Output Tranform.  This module 
 determines whether to prompt for CoreFLS query and add a new entry to the 
 pointed field of the LOCAL VENDOR file (#392.31).  
  
 AFTER(FILE,IEN,X,DGBTV) ; called from template or DR string.  
         ; input   FILE   := File number of field to update.  
         ;         IEN    := Dzero variable 
         ;         X      := entered response (X) from call.  
         ;         DGBTV  := previous value 
         ; output: -1     := no success with entry 
         ;         >0     := vendor successfully updated 
  
         FILE = 392 will update COREFLS CARRIER field (#14) of the 
                BENEFICIARY TRAVEL CLAIM file (#392).  
         FILE = 680 will update MICROFILM COREFLS VENDOR field (#2.6) of 
                the LOCAL SERIALS file (#680).  
         FILE = 680.6 will update DEFAULT COREFLS VENDOR field (#.09) of 
                the LIBRARY PARAMETERS file (#680.6).  
         FILE = 681 will update COREFLS VENDOR field (3.01) of the LBRY 
                DISPOSITION file (#681).  
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING

NUMBER: 3866                            IA #: 3866
  FILE NUMBER: 680                      GLOBAL ROOT: LBRY(680
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: LIBRARY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3866
  ID: LBRY(680
GLOBAL REFERENCE: LBRY(680,
FIELD NUMBER: 2.6                       FIELD NAME: MICROFILM COREFLS VENDOR
  LOCATION: 2;6                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is a pointer to the LOCAL VENDOR file
 (#392.31).  When a new requests and query to CoreFLS for vendor is made,
 routine DGBTCSL executes the new entry into the MICROFILM COREFLS VENDOR
 field.  
 GENERAL DESCRIPTION:   
 ************************************************************************
 The Library package was decommissioned with LBR*2.5*15.  This ICR was retired
 with the release of the Library patch.  A Beneficiary Travel patch will be
 released in the future removing references to the Library package.  
 ************************************************************************ 
  
 LOCAL SERIALS file (#680) contains the field MICROFILM COREFLS VENDOR (#2.6)
 which is a pointer containing CoreFLS vendors from the LOCAL VENDOR file
 (#392.31). 
  
 Through the Library application when entering a MICROFILM COREFLS VENDOR, if
 the query to CoreFLS is made to enter a new vendor to the LOCAL VENDOR file,
 then the routine DGBTCSL is executed that will add the new vendor to the LOCAL
 VENDOR file and add the entry to the MICROFILM COREFLS VENDOR field.  
  
 This agreement allows the routine DGBTCSL of the Beneficiary Travel package
 which controls the LOCAL VENDOR file of CoreFLS vendors with the ability to
 update the MICROFILM COREFLS VENDOR from the DGBTFLS routine.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL
 SUBSCRIBING DETAILS:   Routine DGBTCSL of the Beneficiary Travel package is
 the interface between Library and the CoreFLS system of vendors.  

NUMBER: 3867                            IA #: 3867
  FILE NUMBER: 680.6                    GLOBAL ROOT: LBRY(680.6
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: LIBRARY
  USAGE: Private                        TYPE: File
  NAME: DBIA3867                        ID: LBRY(680.6
GLOBAL REFERENCE: LBRY(680.6,
FIELD NUMBER: .09                       FIELD NAME: DEFAULT COREFLS VENDOR
  LOCATION: 0;9                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is a pointer to the LOCAL VENDOR file
 (#392.31).  When a new requests and query to CoreFLS for vendor is made,
 routine DGBTCSL executes the new entry into the DEFAULT COREFLS VENDOR field. 
 GENERAL DESCRIPTION:   
 ***********************************************************************
 The Library package was decommissioned with LBR*2.5*15.  This ICR was retired
 with the release of the Library patch.  A Beneficiary Travel patch will be
 released in the future removing references to the Library package.  
 ***********************************************************************
  
 LIBRARY PARAMETERS file (#680.6) contains the field DEFAULT COREFLS VENDOR 
 (#.09) which is a pointer containing CoreFLS vendors from the LOCAL VENDOR 
 file (#392.31). 
  
 Through the Library application when entering a DEFAULT COREFLS VENDOR, if the
 query to CoreFLS is made to enter a new vendor to the LOCAL VENDOR file, then
 the routine DGBTCSL is executed that will add the new the LOCAL VENDOR file
 and add the entry to the DEFAULT COREFLS VENDOR field.  
  
 This agreement allows the routine DGBTCSL of the Beneficiary Travel package
 which controls the LOCAL VENDOR file of CoreFLS vendors with the ability to
 update the DEFAULT COREFLS VENDOR from the DGBTFLS routine.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL
 SUBSCRIBING DETAILS:   Routine DGBTCSL of the Beneficiary Travel package is
 the interface between Library and the CoreFLS system of vendors.  

NUMBER: 3868                            IA #: 3868
  FILE NUMBER: 681                      GLOBAL ROOT: LBRY(681
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: LIBRARY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3868
  ID: LBRY(681
GLOBAL REFERENCE: LBRY(681,
FIELD NUMBER: 3.01                      FIELD NAME: COREFLS VENDOR
  LOCATION: 3;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is a pointer to the LOCAL VENDOR file
 (#392.31).  When a new requests and query to CoreFLS for vendor is made,
 routine DGBTCSL executes the new entry into the COREFLS VENDOR field.  
 GENERAL DESCRIPTION:   
 ************************************************************************
 The Library package was decommissioned with LBR*2.5*15.  This ICR was retired
 with the release of the Library patch.  A Beneficiary Travel patch will be
 released in the future removing references to the Library package.  
 ************************************************************************
  
 LBRY DISPOSITION file (#681) contains the field COREFLS VENDOR (#3.01) which
 is a pointer containing CoreFLS vendors from the LOCAL VENDOR file (#392.31). 
  
 Through the Library application when entering a COREFLS VENDOR, if the query
 to CoreFLS is made to enter a new vendor to the LOCAL VENDOR file, then the
 routine DGBTCSL is executed that will add the new vendor to the LOCAL VENDOR
 file and add the entry to the COREFLS VENDOR field. 
  
 This agreement allows the routine DGBTCSL of the Beneficiary Travel package
 which controls the LOCAL VENDOR file of CoreFLS vendors with the ability to
 update the COREFLS VENDOR from the DGBTFLS routine.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL
 SUBSCRIBING DETAILS:   Routine DGBTCSL of the Beneficiary Travel package is
 the interface between Library and the CoreFLS system of vendors.  

NUMBER: 3869                            IA #: 3869
  DATE CREATED: JAN 08, 2003            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDAMA202
  NAME:  APPOINTMENT DATA BY CLINIC     ID: SDAMA202
 GENERAL DESCRIPTION:   This IA contains a list of the supported calls for
 interaction with Appointment data contained in the Patient sub-file 2.98 and
 the Hospital Location appointment sub-file 44.001.  This IA is associated with 
 Scheduling patch SD*5.3*275, to be released to NVS on 1/10/03.  
  STATUS: Active
COMPONENT/ENTRY POINT: GETPLIST
 COMPONENT DESCRIPTION:   A call to this entry point will return appointment
 data for a specific clinic.  
VARIABLES: SDIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Clinic ID 
VARIABLES: SDFIELDS                     TYPE: Input
 VARIABLES DESCRIPTION:   Appointment fields requested 
VARIABLES: SDAPSTAT                     TYPE: Input
 VARIABLES DESCRIPTION:   Appointment Status filter (optional parameter) 
VARIABLES: SDSTART                      TYPE: Input
 VARIABLES DESCRIPTION:   Start date for appointment search (optional
 parameter) 
VARIABLES: SDEND                        TYPE: Input
 VARIABLES DESCRIPTION:   End date for appointment search (optional parameter) 
VARIABLES: .SDRESULT                    TYPE: Input
 VARIABLES DESCRIPTION:   Variable to contain the count of returned
 appointments (optional parameter) 
VARIABLES: SDIOSTAT                     TYPE: Input
 VARIABLES DESCRIPTION:   Patient Status filter (optional parameter) 
VARIABLES: SDRESULT                     TYPE: Output
 VARIABLES DESCRIPTION:   A count of the returned appointments 
VARIABLES: TMP($J,SDAMA202,GETPLIST)    TYPE: Output
 VARIABLES DESCRIPTION:   The output array ^TMP($J,"SDAMA202","GETPLIST",X,Y)
 will contain the requested appointment data.  Output array 
 ^TMP($J,"SDAMA202","GETPLIST","ERROR",error_code) will contain any errors that
 were generated.  
  
 The calling application is responsible for deleting the temporary globals when
 they have finished processing the appointment data or errors.  
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   Added 10-23-2006. Health Summary makes a call to
 GETPLIST^SDAMA202 in order to get a list of patients with appointments in a
 specific date range in order to build Health Summary Reports.  
SUBSCRIBING PACKAGE: SOCIAL WORK
SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Inpatient Meds added as a subscriber for the Pharmacy
 Interface Automation project and PSJ*5*317.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   TIU added as subscriber for the Existing Product Intake
 Program (EPIP) and the TIU*1.0*305 patch, which has a call to the tag GETPLIST
 in the routine SDAMA202 so that TIU can get appointment data for a clinic.  

NUMBER: 3870                            IA #: 3870
  DATE CREATED: JAN 10, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: DG OPTIONS/MENUS ON SECURITY OFFICER MENU
 GENERAL DESCRIPTION:   Health Information Security Service is requesting to
 place some DG options/menus on INFORMATION SECURITY OFFICER MENU [XUSPY].  
  
  DG SECURITY OFFICER MENU 
  DG PATIENT INQUIRY 
  DG PARAMETER ENTRY 
  DG BULLETIN LOCAL 
  STATUS: Active
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

NUMBER: 3872                            IA #: 3872
  FILE NUMBER: 661.1                    GLOBAL ROOT: RMPR(661.1
  DATE CREATED: JAN 10, 2003            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3872
  ID: RMPR(661.1
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is sort-term and will be retired
 after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3873                            IA #: 3873
  FILE NUMBER: 661.2                    GLOBAL ROOT: RMPR(661.2
  DATE CREATED: JAN 10, 2003            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3873
  ID: RMPR(661.2
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is sort-term and will be retired
 after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3874                            IA #: 3874
  FILE NUMBER: 661.3                    GLOBAL ROOT: RMPR(661.3
  DATE CREATED: JAN 10, 2003            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA3874
  ID: RMPR(661.3
 GENERAL DESCRIPTION:   MDE will pull the data from this file to support the
 population of the new CoreFLS system. This IA is sort-term and will be retired
 after the data has been extracted from all sites.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: MDE
SUBSCRIBING PACKAGE: M DATA EXTRACTOR   ISC: Washington/Silver Spring

NUMBER: 3875                            IA #: 3875
  FILE NUMBER: 441                      GLOBAL ROOT: DD(441
  DATE CREATED: JAN 14, 2003            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: ID Write identifier node File #441
  ID: DD(441
 GENERAL DESCRIPTION:   The National Item File's Item Number (NIF ITEM NUMBER
 field #51) needs to be added as a write identifier to the ITEM MASTER File
 #441.  Field #51, is not a user-editable field, therefore it can not be
 defined as a field identifier.  As KIDS does not have a mechanism to transport
 write identifiers without exporting the entire file definition, it is
 requested that for patch PRC*5.1*63 (NATIONAL ITEM FILE - PHASE 1) IFCAP be 
 permitted to set the ID node via the post-init routine PRC5163P.  The proposed
 code is as follows: 
  
 EN     ;Entry point 
        ;Adding NIF Item # as write identifier for ITEM MASTER file (#441) 
        S ^DD(441,0,"ID","Z")="W:$P($G(^(0)),U,15)>0 ""   NIF#""_ 
 $P($G(^(0)),U,1 5)" 
        Q 
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
KEYWORDS: IDENTIFIER
KEYWORDS: ITEM MASTER FILE
SUBSCRIBING PACKAGE: IFCAP              ISC: Washington/Silver Spring

NUMBER: 3876                            IA #: 3876
  DATE CREATED: JAN 15, 2003            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSJBCBU                      NAME: PSJBCBU
  ID: PSJBCBU
 GENERAL DESCRIPTION:   This API is for use with the BCMA National Contingency
 Plan.  
  
 Entry point EN returns in an array specified by the calling routine Inpatient
 Meds order data in an HL7 format.  
  
 Entry point EN2 returns an ^TMP global with active orders.  
  
 OUTPUT DEFINITION: 
  
 ^TMP("PSJBU",$J,Index,0) = DFN ^ ON (Order number from Inpatient Medications
 V. 5.0 package)^ ON_V/U/P 
  
 NOTE: 
                 
 - ^TMP("PSJBU",$J,1,0) = -1 will be returned if no active orders are found.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PCJBCBU
COMPONENT/ENTRY POINT: EN
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Internal Entry Number for the patient
 from the Pharmacy Patient file (#55).  
VARIABLES: ON                           TYPE: Input
 VARIABLES DESCRIPTION:   This is the Internal Entry Number for the order
 concantenated with a "P" for pending orders, a "U" for unit dose orders, or a
 "V" for IV orders.  
VARIABLES: PSJNAME                      TYPE: Both
 VARIABLES DESCRIPTION:   This contains the name of the array the calling
 routine wishes the data to be returned in.  
COMPONENT/ENTRY POINT: EN2
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient Internal File Number (required).  
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Date used to start searching for orders that stop
 after this date (optional). If BDT is not included, NOW is used as the time to
 start searching for active orders.  
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
  ISC: Birmingham

NUMBER: 3877                            IA #: 3877
  FILE NUMBER: 354.7                    GLOBAL ROOT: IBAM(354.7
  DATE CREATED: JAN 16, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA 3877                       ID: IBAM(354.7
GLOBAL REFERENCE: IBAM(354.7,D0,1,
FIELD NUMBER: .01                       FIELD NAME: MONTH/YEAR
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: CAP REACHED
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: TOTAL AMOUNT BILLED
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Purpose is to retrieve billing information with regard
 to missing Outpatient Pharmacy copay bills.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 3878                            IA #: 3878
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19
  DATE CREATED: JAN 20, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Resource device filing in server option
  ID: DIC(19
 GENERAL DESCRIPTION:   When a KIDS distribution installs a server type option
 that has an attached resource device (SERVER DEVICE field #227), the internal
 entry number (ien) of the device on the origin system and not the resolved ien 
 of the corresponding device on the destination system files.  Thus the 
 installed server type option is usually now pointing to the wrong device or a
 non-existent device.  As KIDS does not have a mechanism for finding the
 appropriate device entry and resolving the pointer value, it is requested that
 for patch PRC*5.1*63 (NATIONAL ITEM FILE - PHASE 1) IFCAP be permitted by VA
 FileMan database server calls to lookup the appropriate entry and file its ien
 into the server type option PRCHITEM_UPDATE during execution of the post-init
 routine PRC5163P.  
  
 The proposed code from module EN^PRC5163P is: 
  
         ;Linking resource device to server option 
         N PRCERR,PRCD,PRCDA,PRCDA2 
         K PRCERR 
         S PRCDA=$$FIND1^DIC(3.5,"","X","PRCHITEM","B","I $P(^(""TYPE""),U)= 
 ""RES""","PRCERR") 
         I PRCDA'>0!$D(PRCERR) D  G EX 
         . N PRCT S PRCT(1)="Lookup of resource device PRCHITEM failed." 
         . S PRCT(2)="  You will have to manually link resource device PRCHITEM 
 to server" 
         . S PRCT(3)="  option PRCHITEM_UPDATE." 
         . D MES^XPDUTL(.PRCT) 
         K PRCERR 
         S PRCDA2=$$FIND1^DIC(19,"","X","PRCHITEM_UPDATE","B","","PRCERR") 
         I PRCDA2'>0!$D(PRCERR) D  G EX 
         . N PRCT S PRCT(1)="Lookup of server option PRCHITEM_UPDATE failed." 
         . S PRCT(2)="  Please contact NVS as there were patch installation 
 problems." 
         . D MES^XPDUTL(.PRCT) 
         K PRCD,PRCERR 
         S PRCD(19,PRCDA2_",",227)=PRCDA 
         D FILE^DIE("K","PRCD","PRCERR") 
         I $D(PRCERR) D  G EX 
         . N PRCT S PRCT(1)="Automated linkage of resource device PRCHITEM to 
 server option" 
         . S PRCT(2)="  PRCHITEM_UPDATE failed.  You will have to manually link 
 it." 
         . D MES^XPDUTL(.PRCT) 
         N PRCT S PRCT(1)="Resource device PRCHITEM was successfully linked to 
 server" 
         S PRCT(2)="  option PRCHITEM_UPDATE." 
         D MES^XPDUTL(.PRCT) 
  
 EX      ; 
         Q 
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
KEYWORDS: SERVER
KEYWORDS: RESOURCE DEVICE
SUBSCRIBING PACKAGE: IFCAP              ISC: Washington/Silver Spring

NUMBER: 3879                            IA #: 3879
  DATE CREATED: JAN 21, 2003            CUSTODIAL PACKAGE: VBECS
  CUSTODIAL ISC: Dallas                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VBECA3A                      NAME: DBIA3879-A
  ORIGINAL NUMBER: 3879                 ID: VBECA3A
 GENERAL DESCRIPTION:   The entry point DFN^VBECA3A is provided by the Blood
 Bank package to return Blood Bank patient related data for use by CPRS.  This
 data will be used to populate the Blood Bank Report listed under the Reports
 tab.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DFN(DFN)
 COMPONENT DESCRIPTION:   This function will return the data for the patient
 provided in the call as required for the CPRS Blood Bank report.  
  
 ^TMP("VBDATA",$J,"COMPONENT REQUEST",n)=COMP CLASS NAME^UNITS REQUESTED^DATE
 REQUESTED^DATE WANTED^REQUESTOR ID^ENTERED BY ID^ORDER # 
  
  COMP CLASS NAME = Component class name requested 
  UNITS REQUESTED = Number of units requested 
  DATE REQUESTED = Date of request 
  DATE WANTED = Date units should be available for transfusion 
  REQUESTOR ID = IEN from the NEW PERSON file (#200) of person requesting 
 components 
  ENTERED BY ID = IEN from the NEW PERSON file (#200) of person entering 
 request in CPRS 
  ORDER # = CPRS order number associated with request 
  
  
 ^TMP("VBDATA",$J,"SPECIMEN",n)=ORDER #^DIVISION^TECH ID^TEST NAME^PRINT 
 NAME^REQUESTOR ID^RESULT^TEST DATE 
  
  ORDER # = CPRS order number associated with request 
  DIVISION = Blood Bank Division where testing was performed 
  TECH ID = IEN from the NEW PERSON file (#200) of Blood Bank tech entering 
 test results 
  TEST NAME = Full test name 
  PRINT NAME = Short name of test for display 
  REQUESTOR ID = IEN from the NEW PERSON file (#200) of person requesting test 
  RESULT = Blood Bank test result 
  TEST DATE = Date testing was performed 
  
  
 ^TMP("VBDATA",$J,"UNIT",n)=EXP DATE^PRODUCT^ABO^RH^DIVISION^LOCATION^STATUS^ID 
  
  EXP DATE = Unit expiration date/time 
  PRODUCT = Blood Product type associated with unit 
  ABO = ABO Group of unit 
  RH = Rh Type of unit 
  DIVISION = VAMC division where unit is currently located 
  LOCATION = Hospital location of division where unit is currently located 
  STATUS = Coded element representing unit availability 
           C = Crossmatched units 
           S = Assigned units 
           A = Autologous units reserved 
           D = Directed units reserved 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   internal entry number from the PATIENT file (#2).  
VARIABLES: TEMP GLOBAL                  TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP("VBDATA",$J is returned. The DBIA description
 lists the possible subscripts and their associated data.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3880                            IA #: 3880
  DATE CREATED: JAN 21, 2003            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VBECA3B                      NAME: DBIA3879-B
  ORIGINAL NUMBER: 3879                 ID: VBECA3B
 GENERAL DESCRIPTION:   The entry point CPRS^VBECA3B is provided by the Blood
 Bank package to convert data from the ^TMP array created by VBECA3A for use by
 CPRS.  This data will be used to populate the Blood Bank Report listed under
 the Reports tab.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CPRS
 COMPONENT DESCRIPTION:   This function will convert data from the ^TMP array
 created by VBECA3A for use by CPRS and place it in the ^TMP("BBD") array.  
VARIABLES: TMP("VBDATA")                TYPE: Input
 VARIABLES DESCRIPTION:   ^TMP("VBDATA",$J contains the raw data for the CPRS
 Blood Bank Report.  
VARIABLES: TMP("BBD")                   TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP("BBD",$J contains the processed data for the
 CPRS Blood Bank Report.  
  
 The files, fields, and data format returned are in this format: 
  
                                 63.084,.01 (Blood Component Request) 
                                                        63.084,.04 (Number of
 Units) 
                                                          63.084,.03 (Request
 Date/Time) 
                                                                            
 63.084,.05 (Date/Time Units Wanted) 
                                                                                
                63.084,.09 
                                                                                
                (Requesting Person) 
                                                                                
                       63,.084,.08 
                                                                                
                       (Entering 
                                                                                
                        Person DUZ) 
  
 ^TMP("BBD",$J,"COMPONENT REQUEST",44)=CPDA-1 RED BLOOD CELLS^3^JUN 11, 
 2001@08:47^JUN 11, 2001@08:47^MORTON^7^ ^TMP("BBD",$J,"COMPONENT
 REQUEST",64)=FRESH FROZEN PLASMA, CPDA-1,FROZEN^1^MAR 22, 2002@13:27^MAR 22,
 2002@13:28^MORT^7^ 
  
                          65,.01 (Unit ID) 
                                65,.04 (Component) 
                                                       65,.07 (ABO Group) 
                                                         65,.08 (RH Type) 
                                                                  65,.06 
 (Expiration Date/Time) 
                                                                              
 65,.16 (Division) 
                                                                                
            65.03,.04 (Location) 
                                                                                
                       (Note: Most 
                                                                                
                        recent entry 
                                                                                
                        is reported 
                                                                                
                        here) 
  
 ^TMP("BBD",$J,"CROSSMATCH",67)=04ABC^CPDA-1 RED BLOOD CELLS^O^POSITIVE^APR 25,
 2002^Dallas CIOFO^^ ^TMP("BBD",$J,"CROSSMATCH",69)=04ABC2^CPDA-1 RED BLOOD 
 CELLS^O^POSITIVE^APR 25, 2002^Dallas CIOFO^5 DALLAS^ 
  
                   63.01,.01 (Date/Time Specimen Taken) 
                                   63.01,.03 (Date Report Completed) 
                                                      63.01,.01 (Date/Time 
 Specimen Taken) 
                                                                           
 63.01,10 (ABO Interpretation) 
                                                                             
 63.01,2.9 (DIRECT AHG INTERPRETATION) 
                                                                                
  63.01,2.1 (DIRECT 
                                                                                
             AHG(POLYSPECIFIC)) 
                                                                                
   63.01,2.4 (Anti-IgC) 
                                                                                
    63.01,2.6 (ANTI-COMPLEMENT) 
                                                                                
     63.01,11 (RH Interpretation) 
                                                                                
         63.01,6 (Antibody Screen 
                                                                                
                  Interpretation) 
  
 ^TMP("BBD",$J,"SPECIMEN",3010529.091751)=MAY 30, 2001@12:40^MAY 29, 
 2001@09:17:51^^^^^^^^^ 
                                                   63.199,.01 (Specimen 
 Comment) ^TMP("BBD",$J,"SPECIMEN",3010529.091751,"63.199,.01",1)=*TRANSFUSION 
 REQUEST Not Performed: 05/29/2001 9:27 am by 1336 
 ^TMP("BBD",$J,"SPECIMEN",3010529.091751,"63.199,.01",2)=*NP Reason:DON'T FEEL
 LIKE DOING IT ^TMP("BBD",$J,"SPECIMEN",3010529.092452)=MAY 29, 2001@09:30^MAY
 29, 2001@09:24:52^O^^^^^^POS^NEG^ ^TMP("BBD",$J,"SPECIMEN",3010530.123232)=MAY
 30, 2001@12:33^MAY 30, 2001@12:32:32^^NEGATIVE^N^N^N^NEGATIVE^^NEG^ 
 ^TMP("BBD",$J,"SPECIMEN",3010530.152121)=MAY 30, 2001@15:22^MAY 30, 
 2001@15:21:21^O^^^^^^POS^NEG^ ^TMP("BBD",$J,"SPECIMEN",3010531.084117)=MAY 31,
 2001@08:44^MAY 31, 2001@08:41:17^O^^^^^^POS^NEG^ 
 ^TMP("BBD",$J,"SPECIMEN",3010608.06)=JUN 08, 2001@08:54^JUN 08, 2001@06:00^NOT
 DONE^NEGATIVE^N^N^N^NEGATIVE^NOT DONE^NEG^ 
 ^TMP("BBD",$J,"SPECIMEN",3010608.06,"63.199,.01",1)=*TRANSFUSION REQUEST Not
 Performed: 06/08/2001 8:42 am by 1336 
 ^TMP("BBD",$J,"SPECIMEN",3010608.06,"63.199,.01",2)=*NP Reason:DUPLICATE TEST 
 ^TMP("BBD",$J,"SPECIMEN",3010608.06,"63.199,.01",3)=ABO INTERPRETATION changed
 from: ^TMP("BBD",$J,"SPECIMEN",3010608.06,"63.199,.01",4)=Above changed:Jun
 08, 2001 09:10 By:MURCH,CLAUDETTE Y 
 ^TMP("BBD",$J,"SPECIMEN",3010608.06,"63.199,.01",5)=RH  INTERPRETATION changed
 from: ^TMP("BBD",$J,"SPECIMEN",3010608.06,"63.199,.01",6)=Above changed:Jun
 08, 2001 09:10 By:MURCH,CLAUDETTE Y ^TMP("BBD",$J,"SPECIMEN",3010608.07)=JUN
 08, 2001@08:48^JUN 08, 2001@07:00^O^^^^^^POS^NEG^ 
 ^TMP("BBD",$J,"SPECIMEN",3010611.084714)=JUN 11, 2001@08:48^JUN 11, 
 2001@08:47:14^O^^^^^^POS^NEG^ ^TMP("BBD",$J,"SPECIMEN",3020322.142203)=MAR 25,
 2002@10:28^MAR 22, 2002@14:22:03^O^^^^^^POS^POS^ 
 ^TMP("BBD",$J,"SPECIMEN",3020322.142203,"63.46,.01",16)=ANTI E 
 ^TMP("BBD",$J,"SPECIMEN",3020903.134547)=JAN 15, 2003@13:13^SEP 03, 
 2002@13:45:47^^^^^^^^^ 
                                         63.01,2.91 (DIRECT AHG TEST COMMENT) 
 ^TMP("BBD",$J,"SPECIMEN",3020903.134547,2.91)=STRONG COLD AGGLUTININ PRESENT 
                                                    63.012,.01 (ELUATE 
 ANTIBODY) ^TMP("BBD",$J,"SPECIMEN",3020903.134547,"63.012,.01",21)=ANTI G 
 ^TMP("BBD",$J,"SPECIMEN",3020903.134547,"63.199,.01",1)=A SPECIMEN COMMENT 
 ^TMP("BBD",$J,"SPECIMEN",3020903.134547,"63.199,.01",2)=ANOTHER SPECIMEN 
 COMMENT ^TMP("BBD",$J,"SPECIMEN",3020903.134547,"63.199,.01",3)=A THIRD
 SPECIMEN COMMENT 
                                                  63.46,.01 (SERUM ANTIBODY) 
 ^TMP("BBD",$J,"SPECIMEN",3020903.134547,"63.46,.01",4)=ANTI A 
 ^TMP("BBD",$J,"SPECIMEN",3020903.134547,"63.46,.01",19)=ANTI Fy(a) 
 ^TMP("BBD",$J,"SPECIMEN",3020903.134547,"63.46,.01",64)=ANTI M 
 ^TMP("BBD",$J,"SPECIMEN",3020903.134547,"63.46,.02",4)=COMMENT FOR ANTI A 
                                                   63.46,.02 (ANTIBODY COMMENT) 
 ^TMP("BBD",$J,"SPECIMEN",3020903.134547,"63.46,.02",19)=ANTI F COMMENT 
 ^TMP("BBD",$J,"SPECIMEN",3020903.134547,"63.46,.02",64)=ANTI M COMMENT 
                                                  63.48,.01 (ANTIBODY SCREEN
 COMMENT) ^TMP("BBD",$J,"SPECIMEN",3020903.134547,"63.48,.01",1)=REPEAT PENDING 
 ^TMP("BBD",$J,"SPECIMEN",3020903.134547,"63.48,.01",2)=OK 
 ^TMP("BBD",$J,"SPECIMEN",3020903.134547,"63.48,.01",3)=OKL 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3881                            IA #: 3881
  DATE CREATED: JAN 21, 2003            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VBECA1A                      NAME: DBIA3879-C
  ORIGINAL NUMBER: 3879                 ID: VBECA1A
 GENERAL DESCRIPTION:   The entry point PAT^VBECA1A is provided by the Blood
 Bank package to validate the patient information used when calling the VBECS
 API's.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PATID
 COMPONENT DESCRIPTION:   The internal entry number in the file designated in
 the PARENT local.  
VARIABLES: PATNAM                       TYPE: Both
 VARIABLES DESCRIPTION:   The patient name as it appears in the file designated
 in the PARENT local for input and in the FILEROOT local for output.  
VARIABLES: PATDOB                       TYPE: Both
 VARIABLES DESCRIPTION:   The Date of Birth as it appears in the file
 designated in the PARENT local for input and in the FILEROOT local for output. 
 
VARIABLES: PARENT                       TYPE: Input
 VARIABLES DESCRIPTION:   Either "2" or "67" to designate either the PATIENT
 file (#2)or the REFERRAL file (#67).  
VARIABLES: IFN                          TYPE: Output
 VARIABLES DESCRIPTION:   The internal entry number in the file designated in
 the PARENT local.  
VARIABLES: FILEROOT                     TYPE: Output
 VARIABLES DESCRIPTION:   Either "2" or "67" to designate either the PATIENT
 file (#2)or the REFERRAL file (#67).  
VARIABLES: LRDFN                        TYPE: Output
 VARIABLES DESCRIPTION:   The internal entry number of this patient in the LAB
 DATA FILE for the patient designated in the IFN variable.  
VARIABLES: VBECERR                      TYPE: Output
 VARIABLES DESCRIPTION:   An array containing any error messages generated
 during the data validation.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   internal entry number from the PATIENT file (#2)
 (Passed as a parameter).  You must precede the internal entry number with the
 accent grave character ( ` ).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3882                            IA #: 3882
  DATE CREATED: JAN 22, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA3882
 GENERAL DESCRIPTION:   The Controlled Substance V3.0 Narcotics Monitoring Menu
 [PSD NM MENU] will include Kernel's Option Access by User [XUOPTWHO] option.  
   
 The Narcotics Monitoring enhancement is distributed in the PSD*3.0*41 KIDS
 build which transports the [XUOPTWHO] option as an 'Attach to Menu'.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XUOPTWHO
COMPONENT/ENTRY POINT: Option Access by User [XUOPTWHO]
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
  ISC: Birmingham

NUMBER: 3883                            IA #: 3883
  DATE CREATED: JAN 28, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: %ZOSV
  NAME: Use of DOLRO~ZOSV by VistA HL7 Application Developers
  ID: %ZOSV
 GENERAL DESCRIPTION:   Patch HL*1.6*93 allows application developers to modify
 four routing- related fields in the MSH segment of HL7 messages.  There are
 two ways these changes can be made: 
  
 (1) Calling GENERATE^HLMA or DIRECT^HLMA with the string literal value to 
     be used for the routing-related fields, or 
  
 (2) Call GENERATE^HLMA or DIRECT^HLMA and specify M code to evaluate the 
     environment and make changes to specified (and a limited number of) 
     local variables.  
  
 Even though the M code called by the new HL*1.6*93 software can only make a
 limited number of changes to local variables, evaluation of the total local
 variable environment is extremely important.  
  
 The DOLRO^%ZOSV API has been built into the current HL7 software to make it
 easier for application developers to perform the necessary evaluation and
 actions.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DOLRO
 COMPONENT DESCRIPTION:   The DOLRO^%ZOSV stores all local variables in the
 global storage location specified by the variable X.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   When X is set to an open global reference, (like
 '^XTMP("ZZHL",25,'), all local variables existent when DOLRO^%ZOSV is called
 are stored in the location specified by the open global reference.  These
 variables, now stored in the X-specified global location, may be listed and
 examined by application developers.  
SUBSCRIBING PACKAGE: HEALTH LEVEL SEVEN
  ISC: Oakland
 SUBSCRIBING DETAILS:   The DOLRO^%ZOSV API is used by application developers
 during the initial development phase of their software.  This API is used to
 "discover" and display all local variables.  These local variables are then
 used to determine actions to take.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: VISTA SERVICES ASSEMBLER

NUMBER: 3884                            IA #: 3884
  FILE NUMBER: 3.2                      GLOBAL ROOT: %ZIS(2,
  DATE CREATED: MAR 04, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSOLLU2                      NAME: BUILD CONTROL CODES
  ID: PSOLLU2
GLOBAL REFERENCE: %ZIS(2,D0,55,
FIELD NUMBER: .01                       FIELD NAME: CTRL CODE ABBREVIATION
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 1                         FIELD NAME: FULL NAME
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 2                         FIELD NAME: CONTROL CODE
  LOCATION: 1;1                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   Outpatient Pharmacy V. 7.0 utilizes the CONTROL CODES
 field (#55) of the TERMINAL TYPE file (#3.2) in order to provide a generic
 print routine that will handle laser labels.  
  
 There are 30+ control codes to be built in order to properly format the 
 output. Since standard PCL 5 escape sequences are being used 90% of them will
 be the same for every printer. In order to assist sites with building the
 control codes, this agreement will allow Outpatient Pharmacy V. 7.0 to provide
 a routine to automatically build the control codes.  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 7.0
KEYWORDS: %zis
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN

NUMBER: 3885                            IA #: 3885
  DATE CREATED: FEB 03, 2003            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: DI OPTIONS/MENUS ON SECURITY OFFICER MENU
 GENERAL DESCRIPTION:   Health Information Security Service is requesting to
 place some DI options/menu on INFORMATION SECURITY MENU [XUSPY].  
  
 DIPRINT on the XUDIACCESS FOR ISO menu.  DISEARCH on the XUDIACCESS FOR ISO
 menu.  DIINQUIRE on the XUDIACCESS FOR ISO menu.  DILIST on the XUDIACCESS FOR
 ISO menu.  DIAUDIT on the XUDIACCESS FOR ISO menu.  DIAUDITED FIELDS on the
 DIAUDIT menu.  DIAUDIT DD on the DIAUDIT menu.  DIAUDIT PURGE DATA on the
 DIAUDIT menu.  DIAUDIT PURGE DD on the DIAUDIT menu.  DIAUDIT TURN ON/OFF on
 the DIAUDIT menu.  
  STATUS: Active
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

NUMBER: 3886                            IA #: 3886
  DATE CREATED: FEB 03, 2003            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: XM OPTION ON SECURITY OFFICER MENU
 GENERAL DESCRIPTION:   Health Information Security Service is requesting to
 place a XM option on INFORMATION SECURITY MENU [XUSPY].  
  
 XM SUPER SEARCH on XUAUDIT MAINT menu.  
  STATUS: Active
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

NUMBER: 3887                            IA #: 3887
  DATE CREATED: FEB 04, 2003
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MPIFCMRP
  NAME: LM MPIFCMRP                     ID: MPIFCMRP
 GENERAL DESCRIPTION:   Patient Data Review List Manager entry point for
 pushing the CMOR was requested by the MPI/PD team 
  STATUS: Active
COMPONENT/ENTRY POINT: LM
 COMPONENT DESCRIPTION:   This entry point allows for the pushing of a CMOR to
 another site in the treating facility list.  
VARIABLES: PAT                          TYPE: Input
 VARIABLES DESCRIPTION:   PAT = Interal Entry Number of the patient in the
 Patient file (#2) to have its CMOR changed.  
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   This is for use by the MPI/PD portion of PIMS --
 patient data review option(s).  

NUMBER: 3888                            IA #: 3888
  DATE CREATED: FEB 06, 2003            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMTSXAL                      NAME: GMTSXAL
  ID: GMTSXAL
 GENERAL DESCRIPTION:   Get Health Summary Type Parameter List.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETLIST
 COMPONENT DESCRIPTION:   Get Health Summary Type Parameter List for a user.  
VARIABLES: GMTSL                        TYPE: Both
 VARIABLES DESCRIPTION:   Local or global array of Health Summary Parameters,
 controlled by the GBL parameter.  
  
VARIABLES: GMTSUSR                      TYPE: Input
 VARIABLES DESCRIPTION:   DUZ or internal pointer value to the NEW PERSON file
 (#200).  
VARIABLES: GBL                          TYPE: Input
 VARIABLES DESCRIPTION:   If set to a number, the returned array is a global as
 specified by the input variable GMTSL (closed global root).  
VARIABLES: ERR                          TYPE: Output
 VARIABLES DESCRIPTION:   Is set if an error condition has occurred.  
  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   
  

NUMBER: 3889                            IA #: 3889
  DATE CREATED: FEB 06, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSBO                         NAME: BCMA GUI REPORTS
  ID: PSBO
 GENERAL DESCRIPTION:   This Remote Procedure Call returns specific information
 for the BCMA report requested.  
  
 The temp global, ^TMP("PSBO", is where the report text that will be displayed 
 or printed is returned. Killing of the ^TMP("PSBO" global is permitted with 
 this integration agreement.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB
KEYWORDS: REPORTS
COMPONENT/ENTRY POINT: RPC
VARIABLES: RESULTS                      TYPE: Input
 VARIABLES DESCRIPTION:   Return Variable.  
VARIABLES: PSBTYPE                      TYPE: Input
 VARIABLES DESCRIPTION:   
   INPUT PARAMETER: PSBTYPE 
   PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 2 
   REQUIRED: YES 
   SEQUENCE NUMBER: 1 
  
 Contains the character designation for the needed report DL: Due Lisgt MH:
 Medication Administration History ML: Medication Log WA: Ward Administration
 Times MM: Missed Medication PE: PRN Effectiveness PM: Patient Medication
 History WA: Ward Administration Times MV: Medication Variance Log BL: Bar Code
 Label MD: Missing Dose by Ward AL: Allergy Request PI: Patient Inquiry DO:
 Display Order 
VARIABLES: PSBDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   
   INPUT PARAMETER: PSBDFN 
   PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 10 
   REQUIRED: YES 
   SEQUENCE NUMBER: 2 
   
 Patient IEN 
VARIABLES: PSBSTRT                      TYPE: Input
 VARIABLES DESCRIPTION:   
   INPUT PARAMETER: PSBSTRT 
   PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 20 
   REQUIRED: YES 
   SEQUENCE NUMBER: 3 
   
 Internal Fileman Start Date/Time 
VARIABLES: PSBSTOP                      TYPE: Input
 VARIABLES DESCRIPTION:   
   INPUT PARAMETER: PSBSTOP 
   PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 20 
   REQUIRED: YES 
   SEQUENCE NUMBER: 4 
   
 Fileman Stop Date/Time 
VARIABLES: PSBINCL                      TYPE: Input
 VARIABLES DESCRIPTION:   
   INPUT PARAMETER: PSBINCL 
   PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 1 
   REQUIRED: YES 
   SEQUENCE NUMBER: 5 
  
 Contains the parameters for a Due List in up-arrow pieces.  
  
 Piece   1: 1/0 Include Continuous Meds 
         2: 1/0 Include PRN Meds 
         3: 1/0 Include OnCall Meds 
         4: 1/0 Include OneTime Meds 
         5: 1/0 Include Comments 
         6: 1/0 Include Audits 
  
VARIABLES: PSBDEV                       TYPE: Input
 VARIABLES DESCRIPTION:   
   INPUT PARAMETER: PSBDEV 
   PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 30 
   REQUIRED: NO 
   SEQUENCE NUMBER: 6 
   
 Contains the name of the device that the report prints to.  
VARIABLES: PSBSORT                      TYPE: Input
 VARIABLES DESCRIPTION:   
   INPUT PARAMETER: PSBSORT 
   PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 1 
   REQUIRED: YES 
   SEQUENCE NUMBER: 7 
   
 Sorts the report by patient or by ward 
VARIABLES: PSBOI                        TYPE: Input
 VARIABLES DESCRIPTION:   Select INPUT PARAMETER: PSBOI 
   INPUT PARAMETER: PSBOI 
   PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 7 
   REQUIRED: YES 
   SEQUENCE NUMBER: 8 
   
 Order/Orderable Item number 
VARIABLES: PSBWLOC                      TYPE: Input
 VARIABLES DESCRIPTION:   
   INPUT PARAMETER: PSBWLOC 
   PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 30 
   REQUIRED: NO 
   SEQUENCE NUMBER: 8 
   
 Ward Location 
VARIABLES: PSBWSORT                     TYPE: Input
 VARIABLES DESCRIPTION:   
   INPUT PARAMETER: PSBWSORT 
   PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 1 
   REQUIRED: NO 
   SEQUENCE NUMBER: 10 
   
 Sort By Patient - "P" 
   or By Bed     - "B" 
VARIABLES: PSBFUTR                      TYPE: Input
 VARIABLES DESCRIPTION:   
   INPUT PARAMETER: PSBFUTR 
   PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 1 
   REQUIRED: YES 
   SEQUENCE NUMBER: 11 
  
 Contains the parameters for Due list in up-arrow pieces 
  
 Piece   1: 1/0 Include Blanks (Changes/Addendums) 
         2: 1/0 Include IV Meds 
         3: 1/0 Include Unit Dose Meds 
         4: 1/0 Include Future Orders 
  
VARIABLES: ~TMP('PSBO',$J               TYPE: Output
 VARIABLES DESCRIPTION:   
  Report text returned in ^TMP("PSBO",$J,n,0) 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be calling this API in VIAB MEDHIST RPC.  

NUMBER: 3890                            IA #: 3890
  FILE NUMBER: 3.6                      GLOBAL ROOT: XMB(3.6,
  DATE CREATED: FEB 11, 2003            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: BULLETIN LOOKUP AND EDIT        ID: XMB(3.6,
 GENERAL DESCRIPTION:   MailMan does not have any APIs which enable a package
 to edit its own bulletins.  Therefore, for the purpose of editing an existing 
 bulletin, owned by a package, permission is granted to: 
  
 1. Look up a bulletin using FileMan's ^DIC, such as $$FIND1^DIC.  
  
 2. Add/edit data in the bulletin using FileMan's ^DIE, such as UPDATE^DIE or
 FILE^DIE.  
  STATUS: Active

NUMBER: 3891                            IA #: 3891
  DATE CREATED: FEB 12, 2003
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Remote Procedure                ROUTINE: csl
  NAME: This is a Test                  ID: csl
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: test
COMPONENT/ENTRY POINT: csl
SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  ISC: Washington/Silver Spring

NUMBER: 3892                            IA #: 3892
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU GET ADDITIONAL SIGNERS
  REMOTE PROCEDURE: TIU GET ADDITIONAL SIGNERS
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/26/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace. 
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes 
 required RPCs. TIU GET ADDITIONAL SIGNERS is one of the Remote Procedures 
 included in the CRMS VAHC Option. The Remote Application uses Data Access 
 Services/National Health Information Network (DAS/NHIN) as the middleware to
 interface with VistA.  

NUMBER: 3893                            IA #: 3893
  DATE CREATED: FEB 12, 2003
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: GMRC LIST CONSULT REQUESTS
  REMOTE PROCEDURE: GMRC LIST CONSULT REQUESTS
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   CPRS approved adding Dental as a subscriber for Dental
 Record Manager on 8/11/2009.  Dental was not added at that time but was added
 as a subscriber on 2/9/18.  
  DATE ACTIVATED: JAN 23, 2018

NUMBER: 3894                            IA #: 3894
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU GET DS URGENCIES            REMOTE PROCEDURE: TIU GET DS URGENCIES
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3895                            IA #: 3895
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU IDENTIFY CONSULTS CLASS
  REMOTE PROCEDURE: TIU IDENTIFY CONSULTS CLASS
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3896                            IA #: 3896
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU JUSTIFY DELETE?             REMOTE PROCEDURE: TIU JUSTIFY DELETE?
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3897                            IA #: 3897
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU LOCK RECORD                 REMOTE PROCEDURE: TIU LOCK RECORD
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   Added VPS (KIOSK) as subscriber with VPS*1*3. A
 clinician performing medication and allergy assessments has a need to lock TIU
 documents before calling TIU SET DOCUMENT TEXT using the VPS Kiosk
 provider-facing Kiosk application.  VPS Kiosk desires to use component LOCK in
 routine TIUSRVP to provide this functionality.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 ****************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ****************************************************
  
  
 This functionality is being released in HMP*2.0*2 
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/16/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace.
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes 
 required RPCs. TIU LOCK RECORD is one of the Remote Procedures included in the
 CRMS VAHC Option. The Remote Application uses Data Access Services/National
 Health Information Network (DAS/NHIN) as the middleware to interface with
 VistA.  

NUMBER: 3898                            IA #: 3898
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU LONG LIST CONSULT TITLES
  REMOTE PROCEDURE: TIU LONG LIST CONSULT TITLES
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
 SUBSCRIBING DETAILS:   ADDED JUNE 2009 

NUMBER: 3899                            IA #: 3899
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU NOTES 16 BIT                REMOTE PROCEDURE: TIU NOTES 16 BIT
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3900                            IA #: 3900
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU UNLOCK RECORD               REMOTE PROCEDURE: TIU UNLOCK RECORD
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 ****************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ****************************************************
  
  
 This functionality is being released in HMP*2.0*2 
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/18/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce  product sharing the CRMS
 namespace. The CRMS VAHC Remote Application includes the CRMS VAHC Option,
 which includes required RPCs. TIU UNLOCK RECORD is one of the Remote
 Procedures included in the CRMS VAHC Option. The Remote Application uses Data
 Access Services/National Health Information Network (DAS/NHIN) as the
 middleware to interface with VistA.  

NUMBER: 3901                            IA #: 3901
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU WHICH SIGNATURE ACTION
  REMOTE PROCEDURE: TIU WHICH SIGNATURE ACTION
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/18/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce  product sharing the CRMS
 namespace. The CRMS VAHC Remote Application includes the CRMS VAHC Option,
 which includes required RPCs. TIU WHICH SIGNATURE ACTION is one of the Remote
 Procedures included in the CRMS VAHC Option. The Remote Application uses Data
 Access Services/National Health Information Network (DAS/NHIN) as the
 middleware to interface with VistA.  

NUMBER: 3902                            IA #: 3902
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE CHECK BOILERPLATE
  REMOTE PROCEDURE: TIU TEMPLATE CHECK BOILERPLATE
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3903                            IA #: 3903
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE CREATE/MODIFY
  REMOTE PROCEDURE: TIU TEMPLATE CREATE/MODIFY
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3904                            IA #: 3904
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE DELETE             REMOTE PROCEDURE: TIU TEMPLATE DELETE
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3905                            IA #: 3905
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE GETPROOT           REMOTE PROCEDURE: TIU TEMPLATE GETPROOT
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3906                            IA #: 3906
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE LISTOWNR           REMOTE PROCEDURE: TIU TEMPLATE LISTOWNR
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3907                            IA #: 3907
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE SET ITEMS          REMOTE PROCEDURE: TIU TEMPLATE SET ITEMS
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3908                            IA #: 3908
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE ACCESS LEVEL
  REMOTE PROCEDURE: TIU TEMPLATE ACCESS LEVEL
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3909                            IA #: 3909
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE GET DEFAULTS
  REMOTE PROCEDURE: TIU TEMPLATE GET DEFAULTS
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3910                            IA #: 3910
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE GET DESCRIPTION
  REMOTE PROCEDURE: TIU TEMPLATE GET DESCRIPTION
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3911                            IA #: 3911
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE SET DEFAULTS
  REMOTE PROCEDURE: TIU TEMPLATE SET DEFAULTS
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3912                            IA #: 3912
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE PERSONAL OBJECTS
  REMOTE PROCEDURE: TIU TEMPLATE PERSONAL OBJECTS
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3913                            IA #: 3913
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE LOCK               REMOTE PROCEDURE: TIU TEMPLATE LOCK
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3914                            IA #: 3914
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE GETBOIL            REMOTE PROCEDURE: TIU TEMPLATE GETBOIL
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   Added 5/31/19 for adding TIU TEMPLATE GETBOIL as an RPC
 to the VIAB WEB SERVICE OPTION in VIAB*1*16.  

NUMBER: 3915                            IA #: 3915
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE GETITEMS           REMOTE PROCEDURE: TIU TEMPLATE GETITEMS
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: DENTAL

NUMBER: 3916                            IA #: 3916
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE GETROOTS           REMOTE PROCEDURE: TIU TEMPLATE GETROOTS
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: DENTAL

NUMBER: 3917                            IA #: 3917
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE GETTEXT            REMOTE PROCEDURE: TIU TEMPLATE GETTEXT
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: DENTAL

NUMBER: 3918                            IA #: 3918
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE ISEDITOR           REMOTE PROCEDURE: TIU TEMPLATE ISEDITOR
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3919                            IA #: 3919
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE UNLOCK             REMOTE PROCEDURE: TIU TEMPLATE UNLOCK
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3920                            IA #: 3920
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE GETLINK            REMOTE PROCEDURE: TIU TEMPLATE GETLINK
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: DENTAL

NUMBER: 3921                            IA #: 3921
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU TEMPLATE ALL TITLES
  REMOTE PROCEDURE: TIU TEMPLATE ALL TITLES
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 3922                            IA #: 3922
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU GET LIST OF OBJECTS
  REMOTE PROCEDURE: TIU GET LIST OF OBJECTS
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: DENTAL

NUMBER: 3923                            IA #: 3923
  DATE CREATED: MAR 05, 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 TITLE          REMOTE PROCEDURE: TIU GET DOCUMENT TITLE
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 ***************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ***************************************************
  
 This functionality is being released in HMP*2.0*2 
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   Added 7/22/24, effective with DENT*1.2*91, DENTAL, also
 referred to as Dental Record Manager Plus (DRM Plus) needs to retrieve the
 internal entry number based on the title to support the DRM Plus GUI.  

NUMBER: 3924                            IA #: 3924
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU GET DEFAULT PROVIDER
  REMOTE PROCEDURE: TIU GET DEFAULT PROVIDER
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3925                            IA #: 3925
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU GET SITE PARAMETERS
  REMOTE PROCEDURE: TIU GET SITE PARAMETERS
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3926                            IA #: 3926
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU IS USER A PROVIDER?
  REMOTE PROCEDURE: TIU IS USER A PROVIDER?
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3927                            IA #: 3927
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU GET PRINT NAME              REMOTE PROCEDURE: TIU GET PRINT NAME
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3928                            IA #: 3928
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU WAS THIS SAVED?             REMOTE PROCEDURE: TIU WAS THIS SAVED?
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 3929                            IA #: 3929
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU LONG LIST BOILERPLATED
  REMOTE PROCEDURE: TIU LONG LIST BOILERPLATED
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3930                            IA #: 3930
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU GET BOILERPLATE             REMOTE PROCEDURE: TIU GET BOILERPLATE
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3931                            IA #: 3931
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD CAN EDIT              REMOTE PROCEDURE: TIU FIELD CAN EDIT
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3932                            IA #: 3932
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD EXPORT                REMOTE PROCEDURE: TIU FIELD EXPORT
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3933                            IA #: 3933
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD IMPORT                REMOTE PROCEDURE: TIU FIELD IMPORT
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3934                            IA #: 3934
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD LIST                  REMOTE PROCEDURE: TIU FIELD LIST
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3935                            IA #: 3935
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD DELETE                REMOTE PROCEDURE: TIU FIELD DELETE
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3936                            IA #: 3936
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD LOAD                  REMOTE PROCEDURE: TIU FIELD LOAD
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: DENTAL

NUMBER: 3937                            IA #: 3937
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD LOAD BY IEN           REMOTE PROCEDURE: TIU FIELD LOAD BY IEN
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3938                            IA #: 3938
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD LOCK                  REMOTE PROCEDURE: TIU FIELD LOCK
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3939                            IA #: 3939
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD NAME IS UNIQUE
  REMOTE PROCEDURE: TIU FIELD NAME IS UNIQUE
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3940                            IA #: 3940
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD SAVE                  REMOTE PROCEDURE: TIU FIELD SAVE
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3941                            IA #: 3941
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD UNLOCK                REMOTE PROCEDURE: TIU FIELD UNLOCK
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3942                            IA #: 3942
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU REMINDER DIALOGS            REMOTE PROCEDURE: TIU REMINDER DIALOGS
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3943                            IA #: 3943
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU REM DLG OK AS TEMPLATE
  REMOTE PROCEDURE: TIU REM DLG OK AS TEMPLATE
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3944                            IA #: 3944
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD DOLMTEXT              REMOTE PROCEDURE: TIU FIELD DOLMTEXT
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3945                            IA #: 3945
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU DIV AND CLASS INFO          REMOTE PROCEDURE: TIU DIV AND CLASS INFO
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3946                            IA #: 3946
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU USER CLASS LONG LIST
  REMOTE PROCEDURE: TIU USER CLASS LONG LIST
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3947                            IA #: 3947
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU ID ATTACH ENTRY             REMOTE PROCEDURE: TIU ID ATTACH ENTRY
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3948                            IA #: 3948
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU ID CAN ATTACH               REMOTE PROCEDURE: TIU ID CAN ATTACH
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3949                            IA #: 3949
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU ID CAN RECEIVE              REMOTE PROCEDURE: TIU ID CAN RECEIVE
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3950                            IA #: 3950
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU ID DETACH ENTRY             REMOTE PROCEDURE: TIU ID DETACH ENTRY
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3951                            IA #: 3951
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD CHECK                 REMOTE PROCEDURE: TIU FIELD CHECK
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3952                            IA #: 3952
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD LIST ADD              REMOTE PROCEDURE: TIU FIELD LIST ADD
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 3953                            IA #: 3953
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU FIELD LIST IMPORT           REMOTE PROCEDURE: TIU FIELD LIST IMPORT
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3954                            IA #: 3954
  DATE CREATED: MAR 05, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIU SET DOCUMENT TEXT           REMOTE PROCEDURE: TIU SET DOCUMENT TEXT
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
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.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   Effective with VPS*1*3 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 ***************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ***************************************************
  
  
 This functionality is being released with HMP*2.0*2 
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/16/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace.
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes 
 required RPCs. TIU SET DOCUMENT TEXT is one of the Remote Procedures included
 in the CRMS VAHC Option. The Remote Application uses Data Access 
 Services/National Health Information Network (DAS/NHIN) as the middleware to
 interface with VistA.  
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 8/12/25 effective with CDSP*1*1, This RPC buffers
 the transmittal of text (i.e., the body of TIU Documents) from varied Clinical
 Decision Support Platform (CDSP) app. Example of these app are the Lung Cancer
 Screening Risk Calculator. It allows documents of indefinite size to be filed, 
                             

NUMBER: 3955                            IA #: 3955
  DATE CREATED: FEB 13, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSBO                         NAME: PSB REPORT
  REMOTE PROCEDURE: PSB REPORT          ID: PSBO
 GENERAL DESCRIPTION:   This RPC returns specific information for BCMA reports. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB
KEYWORDS: REPORTS
COMPONENT/ENTRY POINT: RPC
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 3956                            IA #: 3956
  DATE CREATED: JUN 04, 2003            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Dallas                 USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: YS GAF API                      REMOTE PROCEDURE: YS GAF API
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3957                            IA #: 3957
  DATE CREATED: FEB 19, 2003
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMRCP513
  NAME: TIU CALL TO GMRCP513            ID: GMRCP513
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: TIUEN
COMPONENT/ENTRY POINT: TIUEN(GMRCIEN)
VARIABLES: GMRCIEN                      TYPE: Input
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 3959                            IA #: 3959
  FILE NUMBER: 811.9                    GLOBAL ROOT: PXD(811.9
  DATE CREATED: FEB 19, 2003
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: GLOBAL READ OF PXD(811.9
  ID: PXD(811.9                         STATUS: Withdrawn
  DURATION: Till Otherwise Agreed

NUMBER: 3960                            IA #: 3960
  FILE NUMBER: 811.7                    GLOBAL ROOT: PXRMD(811.7,
  DATE CREATED: MAR 02, 2004            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: File 811.7                      ID: PXRMD(811.7,
GLOBAL REFERENCE: PXRMD(811.7,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is the name of the Reminder category.  
 GENERAL DESCRIPTION:   This DBIA allows for a global read of the .01 field of
 file 811.7.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRMD(811.7
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3962                            IA #: 3962
  FILE NUMBER: 8925.98                  GLOBAL ROOT: TIU(8925.98,
  DATE CREATED: JUL 18, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: File 8925.98
  ID: TIU(8925.98,
GLOBAL REFERENCE: TIU(8925.98,
FIELD NUMBER: .01                       FIELD NAME: PERSON
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3963                            IA #: 3963
  FILE NUMBER: 8926                     GLOBAL ROOT: TIU(8926,
  DATE CREATED: FEB 19, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: File 8926
  ID: TIU(8926,                         STATUS: Withdrawn
  DURATION: Till Otherwise Agreed

NUMBER: 3964                            IA #: 3964
  DATE CREATED: MAY 15, 2003
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMRCP5A                      NAME: GMRCP5A
  ID: GMRCP5A                           STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PRNT(GMRCIFN,TIUFLG,GMRCQUED,GMRCCPY,GMRCGUI,GMRCAUDT)
VARIABLES: GMRCIFN                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Consult/Request in file 123.  
VARIABLES: TIUFLG                       TYPE: Input
 VARIABLES DESCRIPTION:   Called from TIU?  1 = Yes  0 = No 
VARIABLES: GMRCQUED                     TYPE: Input
 VARIABLES DESCRIPTION:   Queued job ?  1 = Yes  0 = No 
VARIABLES: GMRCCPY                      TYPE: Input
 VARIABLES DESCRIPTION:   Chart Copy ?  C = Chart Copy  W = Working Copy  null
 = Not Applicable 
VARIABLES: GMRCGUI                      TYPE: Input
 VARIABLES DESCRIPTION:   Called from the GUI.  Only produce output in a
 formatted global.  
VARIABLES: GMRCAUDT                     TYPE: Input
 VARIABLES DESCRIPTION:   Set to 1 in GMRCUTL1 if NW or DC consult.  
VARIABLES: ZTIO                         TYPE: Input
 VARIABLES DESCRIPTION:   Output device when job is tasked.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3965                            IA #: 3965
  DATE CREATED: APR 25, 2003            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMTSADOR                     NAME: GMTSADOR
  ID: GMTSADOR                          STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: BUILD
VARIABLES: GMTSTITL                     TYPE: Input
 VARIABLES DESCRIPTION:   Title of Health Summary report ("AD HOC") 
VARIABLES: GMTSTYP                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Health Summary Type, File 142, found using DIC
 lookup.  
VARIABLES: GMTSQIT                      TYPE: Output
 VARIABLES DESCRIPTION:   Flag/variable that is set to 0 at beginning of
 report.  With each line of text that is printed, a check is made to see if the
 report is at the end of a page.  If the report is being viewed interactively, 
 then the user can "^" uparrow out of the report at the end of a page.  The
 user response of an "^" at the end of a page sets GMTSQIT to 1, and the
 processing of the Health Summary report stops.  Example of use:  W ! D
 CKP^GMTSUP Q:$D(GMTSQIT) 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3966                            IA #: 3966
  DATE CREATED: JUL 16, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU IS THIS A SURGERY?
  REMOTE PROCEDURE: TIU IS THIS A SURGERY?
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 ***************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ***************************************************
  
 This functionality is being released in HMP*2.0*2 
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/17/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace.
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes 
 required RPCs. TIU IS THIS A SURGERY? is one of the Remote Procedures included
 in the CRMS VAHC Option. The Remote Application uses Data Access 
 Services/National Health Information Network (DAS/NHIN) as the middleware to
 interface with VistA.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/6/25, This RPC usage is not new with
 OR*3.0*508, but rather found during ICR review of the OR CPRS GUI CHART
 context option. In all likelihood the ICR was created specifically for the
 usage within CPRS GUI, but OE/RR was never added as a subscriber.  
  DATE ACTIVATED: MAR 13, 2014

NUMBER: 3967                            IA #: 3967
  DATE CREATED: APR 29, 2003            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMTSMCMA                     NAME: GMTSMCMA
  ID: GMTSMCMA                          STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: HSUM(PATID,BDATE,EDATE,OCC,WH,ATYPE)
VARIABLES: PATID                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Patient file #2.  
VARIABLES: BDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   Fileman Beginning Date.  
VARIABLES: EDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   Fileman Ending Date.  
VARIABLES: OCC                          TYPE: Input
 VARIABLES DESCRIPTION:   Number of Occurrences to print.  
VARIABLES: WH                           TYPE: Input
 VARIABLES DESCRIPTION:   Null (not used after GMTS*2.7*62 due to remote views) 
VARIABLES: ATYPE                        TYPE: Input
 VARIABLES DESCRIPTION:   Report Type - "B"rief, "F"ull, "C"ondensed 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3968                            IA #: 3968
  DATE CREATED: APR 29, 2003            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMTSRAE                      NAME: GMTSRAE
  ID: GMTSRAE                           STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MAIN
COMPONENT/ENTRY POINT: MAIN(MODE)
VARIABLES: MODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Flag to determine the type of Radiology Report to
 extract.  
  1 = Radiology Impressions 
  2 = Radiology Profile 
VARIABLES: ~TMP("RAE",$J,               TYPE: Output
 VARIABLES DESCRIPTION:   Results returned.  (IA 3417)  ^TMP("RAE",$J, may be
 killed before and after calling.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3969                            IA #: 3969
  DATE CREATED: APR 25, 2003            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMTSROB                      NAME: GMTSROB
  ID: GMTSROB                           STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: STATUS
VARIABLES: GMDT                         TYPE: Input
 VARIABLES DESCRIPTION:   Date of operation from Surgery File, #130.  
VARIABLES: GMN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN from Surgery File, #130.  
VARIABLES: STATUS                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns status of case from Surgery File, #130.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   ADDED 2/10/2011 
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be using STATUS entry point in routine GMTSROB
 in the VIAB SRGY RPTLIST RPC.  

NUMBER: 3970                            IA #: 3970
  DATE CREATED: JUL 29, 2003            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMTSXAL
  NAME: GMTSXAL                         ID: GMTSXAL
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETLIST(.GMTSL,GMTSUSR)
VARIABLES: GMTSL                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the list of Health Summary Types to display
 on the reports tab of the CPRS GUI, passed by reference.  
VARIABLES: GMTSUSR                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN of the New Person file.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3971                            IA #: 3971
  DATE CREATED: FEB 19, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: IBDF18A
  NAME: CALL TO IBDF18A                 ID: IBDF18A
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GLL
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Albany

NUMBER: 3972                            IA #: 3972
  DATE CREATED: FEB 05, 2004            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: LR7OGU                       NAME: CALL TO LR7OGU
  ID: LR7OGU                            STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DEMO
 COMPONENT DESCRIPTION:   This call sets up Patient related variables used in
 calls to Lab API's 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient identifier 
VARIABLES: LRDFN                        TYPE: Output
 VARIABLES DESCRIPTION:   Lab Patient identifier 
VARIABLES: PNM                          TYPE: Output
 VARIABLES DESCRIPTION:   Patient Name 
VARIABLES: AGE                          TYPE: Output
 VARIABLES DESCRIPTION:   Patient Age 
VARIABLES: SEX                          TYPE: Output
 VARIABLES DESCRIPTION:   Patient Sex 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3973                            IA #: 3973
  DATE CREATED: FEB 19, 2003            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         ROUTINE: LRAPS3
  NAME: CALL TO LRAPS3                  ID: LRAPS3
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Dallas

NUMBER: 3974                            IA #: 3974
  DATE CREATED: FEB 19, 2003            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         ROUTINE: LRBLPD1
  NAME: CALL TO LRBLPD1                 ID: LRBLPD1
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Dallas

NUMBER: 3975                            IA #: 3975
  DATE CREATED: FEB 19, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: PSBO
  NAME: CALL TO PSBO                    ID: PSBO
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RPC
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Birmingham

NUMBER: 3976                            IA #: 3976
  DATE CREATED: JAN 16, 2004
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: TIULA3
  NAME: Screen Default Cosigner selection for USER
  ID: TIULA3                            STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$SCRDFCS(USER,Y)
 COMPONENT DESCRIPTION:   Screen Default Cosigner selection for USER 
VARIABLES: USER                         TYPE: Both
VARIABLES: Y                            TYPE: Input
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3977                            IA #: 3977
  DATE CREATED: JAN 16, 2004
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: TIULA4
  NAME: Boolean fn to screen selection of classes
  ID: TIULA4                            STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$CLASPICK(PARENT,Y,TYPES)
 COMPONENT DESCRIPTION:   Boolean fn to screen selection of classes 
VARIABLES: PARENT                       TYPE: Input
VARIABLES: Y                            TYPE: Input
VARIABLES: TYPES                        TYPE: Input
VARIABLES: $$CLASPICK                   TYPE: Output
 VARIABLES DESCRIPTION:   
  1 == may view 
  0 == may not view 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3978                            IA #: 3978
  DATE CREATED: FEB 14, 2004
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: TIUVSIT                      NAME: CALL TO TIUVSIT
  ID: TIUVSIT                           STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETAPPT(DFN)
 COMPONENT DESCRIPTION:   Get list of appointments 
  
 ^TMP global outputs may be killed before and after use.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN for Patient 
VARIABLES: ~TMP("TIUVN",$J,             TYPE: Output
VARIABLES: ~TMP("TIUVNI",$J,            TYPE: Output
VARIABLES: ~TMP("TIUNOT",$J,            TYPE: Output
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3979                            IA #: 3979
  DATE CREATED: FEB 19, 2003            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: YSGAFAP1                     NAME: YSGAFAP1
  ID: YSGAFAP1
 GENERAL DESCRIPTION:   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 ENT call will return the following: 
  
  YSDATA(1)="[ERROR]" 
  YSDATA(2)="With DSM 5, no new GAFs allowed" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ENT(YSDATA,YS)
VARIABLES: YSDATA                       TYPE: Input
VARIABLES: YS                           TYPE: Input
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
  DATE ACTIVATED: NOV 08, 2013

NUMBER: 3980                            IA #: 3980
  DATE CREATED: FEB 19, 2003            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         ROUTINE: YTAPI4
  NAME: OR CALL TO YTAPI4               ID: YTAPI4
 GENERAL DESCRIPTION:   This API allows scoring of patient responses to a test
 or interview without making changes in the M database. The patient ien, the
 test code, and administration date is required along with the responses. All 
 responses are checked for validity. Scoring is returned in the output 
 documented in the SCOREIT API.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PREVIEW(YSDATA,YS)
VARIABLES: YS                           TYPE: Input
 VARIABLES DESCRIPTION:   
  DFN: patient internal identifier 
                         
  CODE: Test code from file 601 or "ASI" e.g. "CAGE", "BDI" 
                             
  ADATE: inclusive administration date in %DT acceptable format (11/11/2011) 
                             
  Staff: DUZ of professional ordering the test 
                             
  R1: string of patient responses 1-200 
                             
  R2: string of patient responses 201-400 [as needed] 
                             
  R3: string of patient responses 401-600 [as needed] 
                             
  Output: 
  -------
  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")=6 
  YS("ADATE")="T" 
  YS("CODE")="ZUNG" 
  YS("STAFF")=67 
  YS("R1")="12121212121212121212" 
                             
  Output 
  ------
  YSDATA(1)=[DATA] 
  YSDATA(2)=CAPP,ANDY W^MMPI2^---ZUNG ---^2940509^05/09/1994^CAULFIELD,MARY A 
  YSDATA(3)="12121212121212121212" 
  YSDATA(4)=R2^ 
  YSDATA(5)=R3^ 
  YSDATA(6)=S1^Total^12^ 
  YSDATA("ON")= A mood disorder screening test (ZUNG) was in the low range 
                (score = 12).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 3981                            IA #: 3981
  FILE NUMBER: 69.51                    GLOBAL ROOT: LAB(69.51
  DATE CREATED: JUL 28, 2004            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: GLOBAL READ OF 69.51            ID: LAB(69.51
GLOBAL REFERENCE: LAB(69.51,'B',
 GENERAL DESCRIPTION:   Clinical Reminders request permission to do a direct
 global read on file # 69.51 "B" cross-reference for the Hep C. EPI Extract
 project.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: LAB
KEYWORDS: LAB(69.51
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 3982                            IA #: 3982
  DATE CREATED: JAN 26, 2005            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: YTAPI4                       NAME: YTAPI4
  ID: YTAPI4                            STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PREVIEW(YSDATA,YS)
 COMPONENT DESCRIPTION:   This API allows scoring of patient responses to a
 test or interview without making changes in the M database. The patient ien,
 the test code, and administration date is required along with the responses.
 All responses are checked for validity. Scoring is returned in the output
 documented in the SCOREIT^YTAPI2(.YSDATA,.YS).  
VARIABLES: YS                           TYPE: Input
 VARIABLES DESCRIPTION:   
  Input array .YS 
  ---------------
  DFN: Patient internal identifier 
  
 CODE: Test code from file 601 or "ASI" e.g. "CAGE", "BDI" 
  
 ADATE: Inclusive administration date in %DT acceptable format (11/11/2011) 
  
 Staff: DUZ of professional ordering the test 
  
 R1: String of patient responses 1-200 
  
 R2: String of patient responses 201-400 [as needed] 
  
 R3: String of patient responses 401-600 [as needed] 
  
  Example: 
  --------
  YS("DFN")=6 
  YS("ADATE")="T" 
  YS("CODE")="ZUNG" 
  YS("STAFF")=67 
  YS("R1")="12121212121212121212" 
VARIABLES: YSDATA                       TYPE: Output
 VARIABLES DESCRIPTION:   Output: 
  -------
  Array(1)=[Data]  ;indicates a successful call 
  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: 
  --------
  Output 
  ------
  YSDATA(1)=[DATA] 
  YSDATA(2)=CAPP,ANDY W^MMPI2^--- ZUNG ---^2940509^05/09/1994^CAULFIELD,MARY A 
  YSDATA(3)="12121212121212121212" 
  YSDATA(4)=R2^ 
  YSDATA(5)=R3^ 
  YSDATA(6)=S1^Total^12^ 
  YSDATA("ON")= A mood disorder screening test (ZUNG) was in the low range 
               (score = 12).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 9/4/24 to clarify that PREVIEW^YTAPI4 is
 deprecated and is not actually called by OE/RR (it is just checking if that
 API exists). In the future, OE/RR will remove the reference to this API.  

NUMBER: 3983                            IA #: 3983
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123,
  DATE CREATED: FEB 24, 2003
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA3983                        ID: GMR(123,
GLOBAL REFERENCE: GMR(123,
FIELD NUMBER: .02                       FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TO SERVICE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: CPRS STATUS
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: URGENCY
  LOCATION: 0;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: GMR(123,'R',
 GENERAL DESCRIPTION:   Patch TIU*1*144, CONSULTS WITH MISMATCHED PATIENTS,
 generates a list of TIU Consult documents whose patient differs from the
 patient of the associated Consult Request.  The site is asked to clean up the
 patient mismatches for these documents.  So far as we know, the software
 errors which created these mismatches have all been corrected, so we expect
 this cleanup effort to be a one-time effort, though it may take the site some 
 time.  
  
 When displaying these documents in a list, TIU needs to provide enough 
 information on each document for the site to identify and locate the document
 and the associated Consult Request.  For this, TIU needs to read fields .02,
 1, 5, and 8.  
  
 Also, TIU needs to identify on the list any documents which are linked on the
 Consults side with a request in addition to or different from the request with
 which the document is linked on the TIU side. So far as we know, this
 situation occurs only when sites have edited file GMR(123 with FileMan. It
 causes the appropriate TIU cleanup action, LINK WITH REQUEST, to misbehave. 
 In such cases, the patch asks sites to request help from NVS. For this, TIU
 needs to read the "R" cross-reference on field 50, ASSOCIATED RESULTS.  
  
 Amendment: Added 10/12/22, effective with patch TIU*1.0*354 the Community Care 
 Referrals and Authorization (CCRA) project uses the CPRS STATUS field to reset
 the status to its original state once a CCRA note is filed with the consult.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 3984                            IA #: 3984
  DATE CREATED: MAR 06, 2003            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBGMT2                       NAME: FEE BASIS AUTHORIZATION INFO
  ID: FBGMT2                            STATUS: Retired
COMPONENT/ENTRY POINT: $$AUTH(FBDFN)
VARIABLES: FBDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient ID 
VARIABLES: $$AUTH                       TYPE: Output
 VARIABLES DESCRIPTION:   function returns 0 or the date in File Man format.
 "0" return value indicates that there is no any authorization for this patient
 in Fee Basis. Otherwise the return value is the END DATE for Fee Basis
 authorization for the patient. If the patien t has more than one
 authorizations than return value will contain the END DATE of the
 authorization with the latest END DATE for the patient.  
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM

NUMBER: 3985                            IA #: 3985
  FILE NUMBER: 8989.5                   GLOBAL ROOT: XTV
  DATE CREATED: FEB 25, 2003            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Direct access to 8989.5 and 8989.51
  ID: XTV
GLOBAL REFERENCE: 8989.5
GLOBAL REFERENCE: 8989.51
 GENERAL DESCRIPTION:   As part of the installation of patch OR*3*141 (GUI
 v20), 4 CPRS parameters became obsolete and were deleted.  However, the 
 parameters were deleted directly and their corresponding entities were not
 removed before the parameters were deleted.  
  
 Patch OR*3*177 will include a post-init (ORY177) that will go through file 
 8989.5 and identify any system level entities that are pointing to 
 non-existent entries in 8989.51. The entries from 8989.5 will then be deleted. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: AUG 24, 2003
KEYWORDS: xpar
KEYWORDS: 8989.5
KEYWORDS: 8989.51
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Request a one-time use agreement to access and
 potentially delete entries from 8989.5 due to incorrectly deleted parameters.  

NUMBER: 3986                            IA #: 3986
  DATE CREATED: APR 09, 2003
  CUSTODIAL PACKAGE: VENDOR - DOCUMENT STORAGE SYS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VEJDIBSC
  NAME: DBIA3986                        ID: VEJDIBSC
 GENERAL DESCRIPTION:   The IB package requests use of EN^VEJDIBSC to send a
 single bill to the QuadraMed Claims Scrubber.  The bill passed to the scrubber
 will have passed all IB edits but will not yet be authorized.  If the bill
 does not pass the scrubber then the bill will not be allowed to be authorized. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Pass a single bill to the DSS/QuadraMed Claims
 Scrubber.  
VARIABLES: IBIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal File Number of the bill in the Bill/Claims
 file (#399).  
VARIABLES: IBQMED                       TYPE: Output
 VARIABLES DESCRIPTION:   This variable will be returned from the scrubber
 equal to 0 if the bill did not pass the scrubber. Otherwise this variable will
 be returned equal to 1.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 3987                            IA #: 3987
  DATE CREATED: APR 09, 2003
  CUSTODIAL PACKAGE: VENDOR - DOCUMENT STORAGE SYS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VEJDIBE1
  NAME: DBIA3987                        ID: VEJDIBE1
 GENERAL DESCRIPTION:   The IB package requests use of DSS/Quadramed calls to
 sequence a bill's procedures and assign the CPT codes associated Diagnosis.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CTCOPY
 COMPONENT DESCRIPTION:   Sequence all CPT codes on a bill and link them to
 their associated Diagnosis.  
VARIABLES: IBIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal File Number of the bill in the Bill/Claims
 file (#399).  
COMPONENT/ENTRY POINT: DX
 COMPONENT DESCRIPTION:   Sequence one CPT code on a bill and link it to the
 associated Diagnosis.  
VARIABLES: IBIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal File Number of the bill in the Bill/Claims
 file (#399).  
VARIABLES: IBPROC                       TYPE: Input
 VARIABLES DESCRIPTION:   Internal Number of the procedure to be modified in
 the CP multiple of the bill in the Bill/Claims file (#399).  
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 3988                            IA #: 3988
  DATE CREATED: MAR 06, 2003            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: HLCSHDR4                     NAME: Dynamic Routing Header Help Code
  ID: HLCSHDR4
 GENERAL DESCRIPTION:   The Dynamic Routing patch HL*1.6*93 gives application
 developers writing calls to the VistA HL7 package's DIRECT^HLMA and
 GENERATE^HLMA APIs the ability to directly control the routing-related fields. 
 These fields are the SENDING APPLICATION (MSH-3), SENDING FACILITY (MSH-4),
 RECEIVING APPLICATION (MSH-5), and the RECEIVING FACILITY (MSH-6).  
  
 Refer to chapter 12 of the VistA HL7 Site Manager and Developer manual for
 complete information about the use of the DIRECT^HLMA and the GENERATE^HLMA
 APIs.  
  
 The Dynamic Routing patch HL*1.6*93 expands the data that can be passed into
 these APIs to include HLP("SUBSCRIBER") and HLP("SUBSCRIBER",n) local array
 entries. When passing HLP("SUBSCRIBER") or HLP("SUBSCRIBER",n) local array
 data, an M API created by the application developer can be called to evaluate
 the environment and, if appropriate, change the local variables used to create
 the routing-related fields in the MSH segment. 
  
 A new API, M^HLCSHDR4, has been created to assist application developers in
 the early stages of using M code to control the routing-related fields in the
 MSH segment.  
  
 When the HLP("SUBSCRIBER") or HLP("SUBSCRIBER",n) local array data references
 M^HLCSHDR4, this is how M^HLCSHDR4 is executed, and the actions taken: 
  
 Step  Action and Comments 
 -------------------------------------------------------------------------
  #1   DIRECT^HLMA or GENERATE^HLMA is called, with HLP("SUBSCRIBER") or 
       HLP("SUBSCRIBER",n) local array defined with a reference to 
       M^HLCSHDR4.  
  #2   Execution of DIRECT^HLMA or GENERATE^HLMA code proceeds, coming to 
       the code that creates the MSH segment.  
  #3   The HLP("SUBSCRIBER") and HLP("SUBSCRIBER",n) data is evaluated, and 
       the call to M^HLCSHDR4 is found.  
  #4   M^HLCSHDR4 is called, and the following actions occur: 
       - The local variables that will be used in the creation of the 
         routing-related fields in the MSH segment are displayed, 
         accompanied with explanation of each variable, it's significance, 
         and from what source the variable was created.  
       - Application developer can interactively enter new values for the 
         routing-related fields. 
       - If new values are entered, the application developer is informed 
         on-screen the actions taken by M^HLCSHDR4 based on the newly 
         entered value for the routing-related field(s).  (I.e., the 
         local variable(s) used in the creation of the routing-related 
         fields is reset to the new value entered by the developer.) 
  #5   The MSH segment is built using the routing-related 
       local variables, (some of which might have been interactively 
       changed by the developer when answering the M^HLCSHDR4 queries.) 
  #6   Execution of DIRECT^HLMA or GENERATE^HLMA code proceeds, the MSH 
       segment and the complete message is created, and all processing of 
       the message completes.  
  
 Because of the display of explanatory information by M^HLCSHDR4, and because
 the developer is informed of the actions being taken in resetting the
 routing-related variables, this API is a valuable training tool.  
  
 Application developers calling M code via HLP("SUBSCRIBER") or 
 HLP("SUBSCRIBER",n) are encouraged to use the M^HLCSHDR4 API during the 
 initial phases of their development.  After learning how to use M code to 
 control the routing-related fields in the MSH segment, developers must remove
 the educational M^HLCSHDR4 reference, substituting their own M code API.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HL7
KEYWORDS: DYNAMIC ROUTING
KEYWORDS: ROUTING
COMPONENT/ENTRY POINT: M
 COMPONENT DESCRIPTION:   Local array data can be passed-by-reference into the
 DIRECT^HLMA and GENERATE^HLMA APIs in the VistA HL7 package.  The local array
 data may contain HLP("SUBSCRIBER") or HLP("SUBSCRIBER",n) entries, used to
 control the routing related fields.  These array entries may also hold
 references to executable M code that may directly control the values of the 
 routing-related fields in the MSH segment.  
  
 The M subroutine in the HLCSHDR4 routine can be called to interactively set
 the local variables used to create the routing-related fields in the MSH
 segment.  
  
 M^HLCSHDR4 is to be used as an educational aid by the application developer
 learning how to create their own application-specific executable M code APIs. 
 This API must be removed prior to release of any software, and appropriate
 application-specific APIs substituted.  

NUMBER: 3989                            IA #: 3989
  DATE CREATED: MAR 06, 2003
  CUSTODIAL PACKAGE: ENROLLMENT APPLICATION SYSTEM
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: EASUER
  NAME: NOTIFICATION OF FEE BASIS AITHORIZATION CHANGE
  ID: EASUER
 GENERAL DESCRIPTION:   This DBIA contains a supported Enrollment API call that
 Fee Basis uses to notify Enrollment about every change of the value of the
 field "TO DATE" of the file #161 FEE BASIS PATIENT. The DBIA is associated
 with Enrollment patch EAS*1.0*25.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMT
COMPONENT/ENTRY POINT: FBAUTH
 COMPONENT DESCRIPTION:   This call was designed to allow the Fee Basis package
 to send to Enrollment two parameters: patient's DFN and TO DATE of the Fee
 Basis authorization.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   PATIENT file#2 internal number (patient's IEN) 
VARIABLES: TDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   TO DATE (end date) of the Fee Basis authorization for
 the patient with internal number specified in DFN. If the patient has more
 than one authorization then TO DATE of the authorization which has the latest 
 TODATE will be used.  
SUBSCRIBING PACKAGE: FEE BASIS          ISC: Albany
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 3990                            IA #: 3990
  DATE CREATED: MAR 12, 2003            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: ICDCODE
  NAME: ICD Code APIs                   ID: ICDCODE
 GENERAL DESCRIPTION:   This agreement contains the references to routine 
 ICDCODE for the supported APIs.  These entry points will retrieve ICD-9 code
 related data.  For ICD-10 data see routine ICDEX (ICR 5747) 
  
 All entry points will return 
   -1^error description in an error condition.  in an error condition.  
  
  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: 3990
KEYWORDS: 3991
COMPONENT/ENTRY POINT: $$ICDDX(CODE,CDT,DFN,SRC)
 COMPONENT DESCRIPTION:   Extrinsic function that returns basic information for 
 an ICD Diagnosis Code.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   ICD Diagnosis Code, IEN or .01 format (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Code Date to check. (Optional) 
  
     If CDT < 10/1/1978, use 10/1/1978.  
     If CDT > DT, validate with newest effective dates 
     If CDT is year only, use first of the year 
     If CDT is year and month only, use first of the month 
     Default = Today (FileMan format) 
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This variable is not used and not supported at this
 time.  
  
VARIABLES: SRC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Source Flag. (Optional) 
        
   0 = exclude local VA codes, use national codes only (default) 
   1 = include local VA codes and national codes 
  
VARIABLES: $$ICDDX                      TYPE: Output
 VARIABLES DESCRIPTION:   19 piece "^" delimited string containing the
 following information: 
         
 Piece    Description 
 -----    -----------
   1      IEN in ^ICD9( 
   2      ICD DX Code (#.01) 
   3      Identifiers (#2) 
   4      Versioned Dx Short Name (#67) 
   5      Unacceptable as Principal Dx (#101) 
   6      Versioned Major Dx Category (#72) 
   7      MDC13 (#5.5) 
   8      Do not use, see piece 19 for CC 
   9      ICD Expanded (#8) 
  10      Status (#66) 
  11      Sex (#9.5) 
  12      Inactive Date (#66) 
  13      MDC24 (#5.7) 
  14      MDC25 (#5.9) 
  15      Age Low (#14) 
  16      Age High (#15) 
  17      Activation Date (#66) 
  18      Message - Notice of Textual Inaccuracy 
  19      Versioned Complication/Comorbidity (CC) (#103) 
         
            or 
         
          -1^Error Description 
  
COMPONENT/ENTRY POINT: $$ICDOP(CODE,CDT,DFN,SRC)
 COMPONENT DESCRIPTION:   Extrinsic function that returns basic information for
 an ICD Operation/Procedure Code.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   ICD Procedure Code, IEN or .01 format (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Code Date to check. (Optional) (Fileman Format) 
        
     If CDT < 10/1/1978, use 10/1/1978.  
     If CDT > DT, validate with newest effective dates 
     If CDT is year only, use first of the year 
     If CDT is year and month only, use first of the month 
     Default = Today (FileMan format) 
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This variable is not used and not supported at this
 time.  
  
VARIABLES: SRC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Source Flag. (Optional) 
               
   0 = exclude local VA codes, use national codes only (default) 
   1 = include local VA codes and national codes 
  
VARIABLES: $$ICDOP                      TYPE: Output
 VARIABLES DESCRIPTION:   14 piece "^" delimited string containing the
 following information: 
                
 Piece    Description 
 -----    -----------
   1      IEN in ^ICD9( 
   2      ICD Procedure Code (#.01) 
   3      Identifiers (#2) 
   4      MDC24 (#5) 
   5      Versioned Oper/Proc (#67) 
   6      <null> 
   7      <null> 
   8      <null> 
   9      ICD Expanded (#8) 
  10      Status (#66) 
  11      Use with Sex (#9.5) 
  12      Inactive Date (#66) 
  13      Activation Date (#66) 
  14      Message - Notice of Textual Inaccuracy 
                
            or 
                
          -1^Error Description 
  
COMPONENT/ENTRY POINT: $$ICDD(CODE,'OUTARR',CDT)
 COMPONENT DESCRIPTION:   Extrinsic function that returns the full description
 of a code, from the "1" node (field 10) of the ICD9 file or the ICD0 file.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   ICD Diagnosis or Procedure Code (Required) 
  
VARIABLES: OUTARR                       TYPE: Both
 VARIABLES DESCRIPTION:   Array to store description 
     name of array - e.g. "ABC" or "ABC("TEST")" 
     or temp array.      Default = ^TMP("ICDD",$J) 
     The calling routine is responsible for killing 
     ^TMP("ICDD",$J) after the call, if used.  
  
 On return, the array contains corresponding lies of text of the code's
 versioned description (field 68).  OUTARR(1) = 1st line of versioned
 description (field #68) OUTARR(last) = last line of versioned description
 (field #68) OUTARR(last+1) = blank line OUTARR(last+2) = NOTICE OF TEXTUAL
 INACCURACY 
  where last+2 is the value returned by $$ICDD.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Code Date to check - not used currently, 
         Included in anticipation of future need.  
     Default = Today (FileMan format) 
     If CDT < 10/1/1978, use 10/1/1978.  
     If CDT > DT, use 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 
VARIABLES: $$ICDD                       TYPE: Output
 VARIABLES DESCRIPTION:   Contains number of lines (number of subscripts) in
 the description (array) 
  
COMPONENT/ENTRY POINT: $$CODEN(CODE,FILE)
 COMPONENT DESCRIPTION:   Extrinsic function that returns the internal entry 
 number and the global root of an ICD Code.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   ICD Code  REQUIRED 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   File Number in which to check for ICD code 
       80 for ICD Diagnosis file 
     80.1 for ICD Operation/Procedure file 
VARIABLES: $$CODEN                      TYPE: Output
 VARIABLES DESCRIPTION:   String, containing the following information in the
 following "~" pieces: 
  
 Piece    Description 
 =====    ===========
   1      ien of the ICD Code 
   2      "^ICD9(" if FILE=80; "^ICD0(" if FILE=80.1 
COMPONENT/ENTRY POINT: $$CODEC(IEN,FILE)
 COMPONENT DESCRIPTION:   This API returns the ICD Code of an IEN in the file
 specified.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) of an ICD
 Diagnosis or Procedure Code.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the File Number to search for code 
  
   80   = ICD Diagnosis file 
   80.1 = ICD Operation/Procedure file 
  
VARIABLES: $$CODEC                      TYPE: Output
 VARIABLES DESCRIPTION:   This is an ICD Diagnosis or ICD Procedure Code based
 on IEN and the file specified 
  
 or 
  
 -1 if no code is found or on error 
  
  DATE ACTIVATED: SEP 04, 2014

NUMBER: 3991                            IA #: 3991
  DATE CREATED: MAR 12, 2003            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: ICDAPIU
  NAME: ICD Utility APIs                ID: ICDAPIU
 GENERAL DESCRIPTION:   This ICR will be retired upon ICD10 Implementation
 (retire action estimated to occur April 1,2016). New development efforts
 should use ICR 5747.  
  
 This contains the references to routine ICDAPIU for the supported APIs to be
 released with v.20.0 of ICD.  
  
 These include extrinsic functions for retieving Code History, performing
 Status checks, retrieving Next/Previous Codes, retrieving Dates based on the
 Business Rules, and retrieving a notice of a code's textual inaccuracy.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: APR 01, 2016
KEYWORDS: 3990
KEYWORDS: 3991
COMPONENT/ENTRY POINT: $$STATCHK(CODE,CDT)
 COMPONENT DESCRIPTION:   Extrinsic function that returns the Status of an ICD
 Code.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   ICD Code  REQUIRED 
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Code Date to check, Default = Today (FileMan format) 
     If CDT < 10/1/1978, use 10/1/1978.  
     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: $$STATCHK                    TYPE: Output
 VARIABLES DESCRIPTION:   String, containing the following information in the
 following "^" pieces: 
  
 Piece    Description 
 =====    ===========
   1      STATUS where 1:active; 0:inactive 
   2      IEN of code, -1 if not found 
COMPONENT/ENTRY POINT: $$NEXT(CODE)
 COMPONENT DESCRIPTION:   Extrinsic function that returns the Next ICD Code
 (active or inactive) 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   ICD Code  REQUIRED 
VARIABLES: $$NEXT                       TYPE: Output
 VARIABLES DESCRIPTION:   The Next ICD Code, Null if there is none.  
COMPONENT/ENTRY POINT: $$PREV(CODE)
 COMPONENT DESCRIPTION:   Extrinsic function that returns the Previous ICD Code
 (active or inactive) 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   ICD Code  REQUIRED 
VARIABLES: $$PREV                       TYPE: Output
 VARIABLES DESCRIPTION:   The Previous ICD Code, Null if there is none.  
COMPONENT/ENTRY POINT: $$HIST(CODE,ARY)
 COMPONENT DESCRIPTION:   Extrinsic function that returns the activation
 history of an ICD Code.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   ICD Code  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
 history entries, -1 if error ARY(date) = STATUS where 1:active; 0:inactive 
                'date' is in FileMan format ARY("IEN") = Internal Entry Number
 of ICD Code 
VARIABLES: $$HIST                       TYPE: Output
 VARIABLES DESCRIPTION:   The number of activation history entries are
 returned, -1 if error 
COMPONENT/ENTRY POINT: $$DTBR(CDT,CS)
 COMPONENT DESCRIPTION:   Extrinsic function that returns a date after applying 
 several Business Rules, depending on the Coding System.  
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 
VARIABLES: CS                           TYPE: Input
 VARIABLES DESCRIPTION:   Code System (0:ICD, 1:CPT/HCPCS, 2:DRG, Default=0) 
VARIABLES: $$DTBR                       TYPE: Output
 VARIABLES DESCRIPTION:   If CDT < 10/1/1978 and CS=0, return 10/1/1978 If CDT
 <  1/1/1989 and CS=1, return  1/1/1989 If CDT < 10/1/1982 and CS=2, return
 10/1/1982 Otherwise, return CDT 
COMPONENT/ENTRY POINT: $$MSG(CDT,CS)
 COMPONENT DESCRIPTION:   Extrinsic function that returns a message to inform
 someone that the code text may be inaccurate.  
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 
VARIABLES: CS                           TYPE: Input
 VARIABLES DESCRIPTION:   Code System (0:ICD, 1:CPT/HCPCS, 2:DRG, 3:LEX,
 Default=0) 
VARIABLES: $$MSG                        TYPE: Output
 VARIABLES DESCRIPTION:   A warning stating: "CODE TEXT MAY BE INACCURATE" 
COMPONENT/ENTRY POINT: PERIOD(CODE,ARY)
 COMPONENT DESCRIPTION:   Funtion that returns Activation/Inactivation Period
 in ARY 
  
 ARY(0) = IEN  (or, -1 if error) ARY(Act_date) = Inactivation Date^Versioned
 Short Name Text (field #67) 
VARIABLES: COD                          TYPE: Input
 VARIABLES DESCRIPTION:   ICD Code     REQUIRED 
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   Array, passed by Reference     REQUIRED 

NUMBER: 3992                            IA #: 3992
  FILE NUMBER: 4.2                      GLOBAL ROOT: DIC(4.2,
  DATE CREATED: MAY 05, 2004            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  NAME: DBIA3992                        ID: DIC(4.2,
 GENERAL DESCRIPTION:   The API in patch SD*5.3*301 makes a call to the DOMAIN
 file (#4.2) to pull the STATION field (#5.5). This AI will allow the
 Scheduling software to access this data to provide it to application teams in
 the encapsulation process of Scheduling Replacement.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 3993                            IA #: 3993
  FILE NUMBER: 8925                     GLOBAL ROOT: TIU(8925,
  DATE CREATED: MAR 12, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: File 8925
  ID: TIU(8925,
GLOBAL REFERENCE: TIU(8925,"F",
FIELD NUMBER: 1201                      FIELD NAME: ENTRY DATE/TIME
  LOCATION: 12;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: TIU(8925,D0,14)
FIELD NUMBER: 1405                      FIELD NAME: REQUESTING PACKAGE REFERENCE
  LOCATION: 14;5                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: TIU(8925,D0,0)
 GENERAL DESCRIPTION:   Consults $ORDERs thru the "F" x-ref on the ENTRY
 DATE/TIME field and $GETs the 5th piece (REQUESTING PACKAGE REFERENCE field)
 on the 14 node.  It also checks for data on the 0 node.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  ISC: Salt Lake City

NUMBER: 3994                            IA #: 3994
  FILE NUMBER: 8925.97                  GLOBAL ROOT: TIU(8925.97,
  DATE CREATED: MAR 12, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: File 8925.97
  ID: TIU(8925.97,                      STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 3995                            IA #: 3995
  FILE NUMBER: 8989.5                   GLOBAL ROOT: XTV(8989.5,
  DATE CREATED: MAR 12, 2003            CUSTODIAL PACKAGE: TOOLKIT
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: File 8989.5
  ID: XTV(8989.5,                       STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 3996                            IA #: 3996
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: GMV ADD VM                      REMOTE PROCEDURE: GMV ADD VM
 GENERAL DESCRIPTION:   
  NAME: GMV ADD VM 
  TAG: EN1                             
  ROUTINE: GMVDCSAV 
  RETURN VALUE TYPE: SINGLE VALUE      
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE                     
  WORD WRAP ON: TRUE 
  DESCRIPTION:   
  This remote procedure call is used to enter a new Vital/Measurement 
  record in the GMRV Vital Measurement file (#120.5).  
   
  This remote procedure call is documented in Integration Agreement 3996.  
  INPUT PARAMETER: GMRVDATA              
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 255             
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  This variable contains the data needed to create a Vital/Measurement 
  record in the GMRV Vital Measurement (#120.5) file. The values are parsed 
  out of the GMRVDATA variable and filed.  
   
  GMRVDATA has the following data: 
   piece1^piece2^piece3^piece4^piece5 
   
   where: 
    piece1 = date/time in FileMan internal format 
    piece2 = patient number from FILE 2 (i.e., DFN) 
    piece3 = vital type, a semi-colon, the reading, a semi-colon, and 
             oxygen flow rate and percentage values [optional] (e.g., 
             21;99;1 l/min 90%) 
    piece4 = hospital location (FILE 44) pointer value 
    piece5 = user number from FILE 200 (i.e., DUZ), an asterisk, and the 
             qualifier (File 120.52) internal entry numbers separated by 
             colons (e.g., 547*50:65) 
  RETURN PARAMETER DESCRIPTION:   
  RESULT does not return a value. 
   
  The data is filed in the GMRV VITAL MEASUREMENT (#120.5) file.  
   
  Example: 
   
   > S GMRVDATA="3051011.1635^134^1;120/80;^67^87*2:38:50:75" 
   > D EN1^GMVDCSAV(.RESULT,GMRVDATA) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI
SUBSCRIBING PACKAGE: SURGERY
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 ***************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ***************************************************
  
  
 This functionality is being released in HMP*2.0*2 

NUMBER: 3997                            IA #: 3997
  FILE NUMBER: 9999999.27               GLOBAL ROOT: AUTNPOV(
  DATE CREATED: MAR 12, 2003            CUSTODIAL PACKAGE: PROBLEM LIST
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            NAME: File 9999999.27
  ID: AUTNPOV(                          STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LEXICON UTILITY    ISC: Salt Lake City

NUMBER: 3998                            IA #: 3998
  FILE NUMBER: 405                      GLOBAL ROOT: DGPM(
  DATE CREATED: MAR 12, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: File 405
  ID: DGPM(                             STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 3999                            IA #: 3999
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB INSTRUCTOR                  REMOTE PROCEDURE: PSB INSTRUCTOR
 GENERAL DESCRIPTION:   
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSB INSTRUCTOR
KEYWORDS: BCMA
KEYWORDS: CAREFUSION
KEYWORDS: INSTRUCTOR
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4000                            IA #: 4000
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB CHECK SERVER                REMOTE PROCEDURE: PSB CHECK SERVER
 GENERAL DESCRIPTION:   
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSB CHECK SERVER
KEYWORDS: BCMA
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4001                            IA #: 4001
  DATE CREATED: APR 01, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: XTMP('ORLK'
 GENERAL DESCRIPTION:   Background: DBIA #867 is not usable. The existing
 process of protecting orders in OE/RR by using a system of locks on the order
 file is not usable due to the limited capacity of the lock tables and the
 number of prescriptions that are in CONSOLIDATED MAIL OUTPATIENT PHARMACY
 (CMOP) transmissions. 
  
 CMOP is given direct write and read permission of the ^XTMP("ORLK-"_ORDER) 
  
 global.  
  
 CMOP will set for each prescription RXIEN: 
  
       where ORDER=+$P($G(^PSRX(RXIEN,"OR1")),"^",2) 
  
 1. S NOW=$$NOW^XLFDT,NOW1=$$FMADD^XLFDT(NOW,1) 2. S
 ^XTMP("ORLK-"_+ORDER,0)=NOW1_U_NOW_"^CPRS/CMOP Order Lock",^(1)=DUZ_U_$J 
  
 ^XTMP("ORLK-14913",0) = 3030328.104006^3030327.104006^CPRS/CMOP Order Lock 
 ^XTMP("ORLK-14913",1) = 11872^541086169 
  
 CMOP will delete ^XTMP("ORLK-"_+ORDER) when each transmission completes.  CMOP
 recovery will include clearing entries from ^XTMP("ORLK"_+ORDER) if 
 ^(0)["CPRS/CMOP" 
  
 CPRS/OERR will include in calls to $$LOCK1^ORX2(order ien), the test of 
 existence of ^XTMP("ORLK-"_+ORDER,0) and if it exists with (^0) containing
 "CPRS/CMOP", will return  "0^CMOP Transmission".  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CMOP
KEYWORDS: ORX2
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham

NUMBER: 4002                            IA #: 4002
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB USERLOAD                    REMOTE PROCEDURE: PSB USERLOAD
 GENERAL DESCRIPTION:   
  (0) = -1^Error Description 
  
 or 
  
  (0) = DUZ 
  (1) = User name 
  (2) = Student Key Flag 
  (3) = Manager Key flag 
  (4) = CPRS Med Order Button Key Flag     
  (5) = Window settings 
        Window Left 
        Window Height 
        Window Top 
        Window Width 
  (6) = Virtual Due List Setup 
  (7) = Division number ^ Site ID ^ (if production system "1", if test 
        system "0") 
  (8) = Division name 
  (9) = ESIG flag 
  (10) = BCMA Online flag 
  (11) = Time      
  (12) = Unit Dose column widths 
  (13) = Check digit 
  (14) = IVPB column widths 
  (15) = IV column widths 
  (16) = Printer user default IEN 
  (17) = Printer user default IEN^Name 
  (18) = Read Only Security Key flag 
  (19) = User's preference per Coversheet Views' column sort 
        Medication Overview sort col #_ / 
        PRN Overview sort col #_ / 
        IV Overview sort col #_ / 
        Expired/Expiring sort col # 
  (20) = User's preference per Coversheet View1 columns' widths 
  (21) = User's preference per Coversheet View2 columns' widths 
   
  (22) = User's preference per Coversheet View3 columns' widths 
   
  (23) = User's preference per Coversheet View4 columns' widths 
  (24) = BCMA Managing Scanning Failure Security Flag ( 1 if user holds 
         BCMA MSF key, 0 if not ) 
  (25) = 5 Rights Override/Unit Dose Administration Flag (0 = no override, 
         1 = override)  [PSB FR UNIT DOSE OVERRIDE] 
  (26) = 5 Rights Override/IV Administration Flag (0 = no override, 1 = 
         override)  [PSB FR IV OVERRIDE] 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB USERLOAD
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN
  DATE ACTIVATED: DEC 08, 2008

NUMBER: 4003                            IA #: 4003
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB PARAMETER                   REMOTE PROCEDURE: PSB PARAMETER
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB PARAMETER
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4004                            IA #: 4004
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB SERVER CLOCK VARIANCE
  REMOTE PROCEDURE: PSB SERVER CLOCK VARIANCE
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB SERVER CLOCK VARIANCE
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4005                            IA #: 4005
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB SCANPT                      REMOTE PROCEDURE: PSB SCANPT
 GENERAL DESCRIPTION:   If no patient or multiple patients are found with the
 scan value an error is returned in the following format: 
  
    Results[0] = 1 
    Results[1] = '-1^Unable to Determine Patient ID' 
  
 If a unique patient is found the following data is returned to the user: 
  
    Results[0]  = Count of returned records 
  
 In the case of an error: 
     Results[1]  = '-1^  "the appropriate error message"  ' 
  
     Results[1]  = DFN 
     Results[2]  = Name 
     Results[3]  = SSN^Dashed SSN 
     Results[4]  = Internal DOB^External DOB 
     Results[5]  = Age 
     Results[6]  = Internal Sex^External Sex 
     Results[7]  = Internal Last Mvmt^External Last Mvmt 
     Results[8]  = Internal Type Mvmt^External Type Mvmt 
     Results[9]  = Internal Ward Location^External Ward Location^ 
                     Internal Hospital Location^External Hospital Location 
     Results[10] = Internal Bed Location^External Bed Location 
     Results[11] = Internal P-Care Physician^External P-Care Physician 
     Results[12] = Internal Treating Speciality^ 
                     External Treating Speciality 
     Results[13] = Movement Diagnosis 
     Results[14] = 1 if in Bed Status 0 if not in Bed Status (i.e. Pass) 
     Results[15] = Expected return date from Pass 
     Results[16] = Reactions 
     Results[17] = Height 
     Results[18] = Weight 
     Results[19] = Means Tests 
     Results[20] = ICN umber 
     Results[21] = " Admission Status message " 
     Results[22] = This NODE begins 'other' patient information.  
                   This NODE may be null.  Records on this NODE will 
                   have a header.  A header will consist of one of the 
                   following: 
  
  
                        "PATFLG" 
  
                               The PATFLG header will initiate a patient 
                               flag record.  The patient flag record will 
                               be constructed as follows: 
                                         "PATFLG" ^ FLAG NAME ^ index# 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB SCANPT
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4006                            IA #: 4006
  FILE NUMBER: 40.8                     GLOBAL ROOT: DG(40.8,
  DATE CREATED: MAR 18, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: File 40.8
  ID: DG(40.8,                          STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4007                            IA #: 4007
  FILE NUMBER: 45.7                     GLOBAL ROOT: DIC(45.7,
  DATE CREATED: MAR 18, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: File 45.7
  ID: DIC(45.7,                         STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4008                            IA #: 4008
  FILE NUMBER: 63                       GLOBAL ROOT: LR(63,
  DATE CREATED: MAR 18, 2003            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: File 63
  ID: LR(63,                            STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4009                            IA #: 4009
  FILE NUMBER: 2005                     GLOBAL ROOT: MAG(2005,
  DATE CREATED: MAR 18, 2003            CUSTODIAL PACKAGE: IMAGING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            NAME: File 2005
  ID: MAG(2005,                         STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4011                            IA #: 4011
  FILE NUMBER: 8994                     GLOBAL ROOT: XWB(8994,
  DATE CREATED: JAN 19, 2006            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: File 8994                       ID: XWB(8994,
 GENERAL DESCRIPTION:   Permission to add or delete entries via FM APIs.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VISTALINK
SUBSCRIBING PACKAGE: IMAGING

NUMBER: 4012                            IA #: 4012
  FILE NUMBER: 9.8                      GLOBAL ROOT: DIC(9.8,
  DATE CREATED: MAR 18, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: File 9.8
  ID: DIC(9.8,                          STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LEXICON UTILITY    ISC: Salt Lake City

NUMBER: 4013                            IA #: 4013
  FILE NUMBER: 9000001                  GLOBAL ROOT: AUPNPAT(
  DATE CREATED: MAR 18, 2003
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  NAME: File 9000001                    ID: AUPNPAT(
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4014                            IA #: 4014
  FILE NUMBER: 9999999.06               GLOBAL ROOT: AUTTLOC(
  DATE CREATED: MAR 18, 2003
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  NAME: File 9999999.06                 ID: AUTTLOC(
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4015                            IA #: 4015
  FILE NUMBER: 405.3                    GLOBAL ROOT: DG(405.3,
  DATE CREATED: MAR 18, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: File 405.3
  ID: DG(405.3,                         STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4016                            IA #: 4016
  FILE NUMBER: 405.4                    GLOBAL ROOT: DG(405.4,
  DATE CREATED: MAR 18, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: File 405.4
  ID: DG(405.4,                         STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4017                            IA #: 4017
  FILE NUMBER: 8927.1                   GLOBAL ROOT: DD(8927.1,
  DATE CREATED: MAR 18, 2003            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: File 8927.1
  ID: DD(8927.1,                        STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4018                            IA #: 4018
  FILE NUMBER: 45.6                     GLOBAL ROOT: DIC(45.6,
  DATE CREATED: MAR 18, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            NAME: File 45.6
  ID: DIC(45.6,
GLOBAL REFERENCE: DIC(45.6,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: CODE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: TYPE OF CARE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION

NUMBER: 4020                            IA #: 4020
  FILE NUMBER: 4.3                      GLOBAL ROOT: XMB(1,
  DATE CREATED: MAY 05, 2004            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  NAME: DBIA4020                        ID: XMB(1,
 GENERAL DESCRIPTION:   The API in patch SD*5.3*301 makes a call to the MAILMAN
 SITE PARAMETERS file (#4.3) to pull the NAME field (#.01). This AI will allow
 the Scheduling software to access this data to provide it to application teams 
 in the encapsulation process of Scheduling Replacement.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 4021                            IA #: 4021
  DATE CREATED: MAR 18, 2003
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: GMRVSR0
  NAME: OR call to GMRVSC0              ID: GMRVSR0
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN6
COMPONENT/ENTRY POINT: EN3
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4022                            IA #: 4022
  DATE CREATED: MAR 18, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         ROUTINE: GMRPNOR1
  NAME: OR call to GMRPNOR1             ID: GMRPNOR1
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4023                            IA #: 4023
  DATE CREATED: MAR 18, 2003
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: GMRVSR0
  NAME: OR call to GMRVSR0              ID: GMRVSR0
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN6
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4024                            IA #: 4024
  DATE CREATED: MAR 18, 2003
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: GMRVUTL
  NAME: OR call to GMRVUTL              ID: GMRVUTL
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN4
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4025                            IA #: 4025
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55
  DATE CREATED: MAR 18, 2003
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: GMTS reference to 55
  ID: PS(55                             STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 4026                            IA #: 4026
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB ALLERGY                     REMOTE PROCEDURE: PSB ALLERGY
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB ALLERGY
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4027                            IA #: 4027
  DATE CREATED: MAR 25, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB GETORDERTAB                 REMOTE PROCEDURE: PSB GETORDERTAB
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB GETORDERTAB
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4028                            IA #: 4028
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB FMDATE                      REMOTE PROCEDURE: PSB FMDATE
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB FMDATE
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4029                            IA #: 4029
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB VALIDATE ORDER              REMOTE PROCEDURE: PSB VALIDATE ORDER
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB VALIDATE ORDER
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4030                            IA #: 4030
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB SCANMED                     REMOTE PROCEDURE: PSB SCANMED
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB SCANMED
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4031                            IA #: 4031
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB TRANSACTION                 REMOTE PROCEDURE: PSB TRANSACTION
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB TRANSACTION
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4032                            IA #: 4032
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB SUBMIT MISSING DOSE
  REMOTE PROCEDURE: PSB SUBMIT MISSING DOSE
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB SUBMIT MISSING DOSE
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4033                            IA #: 4033
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB GETPRNS                     REMOTE PROCEDURE: PSB GETPRNS
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB GETPRNS
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4034                            IA #: 4034
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB IV ORDER HISTORY            REMOTE PROCEDURE: PSB IV ORDER HISTORY
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB IV ORDER HISTORY
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4035                            IA #: 4035
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB BAG DETAIL                  REMOTE PROCEDURE: PSB BAG DETAIL
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSB BAG DETAIL
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4036                            IA #: 4036
  DATE CREATED: MAR 25, 2003            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XMAPHOST                     NAME: XMAPHOST User Interactions
  ID: XMAPHOST
 GENERAL DESCRIPTION:   Kernel requests an IA to use entry points in routine
 XMAPHOST to be called by routine ZISPL, which converts spool documents to mail
 messages.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: FROMWHOM
 COMPONENT DESCRIPTION:   This entry point asks the user whether the resulting
 message should be from the user himself, or from the postmaster.  If the
 message is from the user himself, then the resulting message will not appear
 new when delivered.  If the message is from the postmaster, then it will.  
  
 Usage:  D FROMWHOM^XMAPHOST(DUZ,.XMINSTR,.XMABORT) 
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The DUZ of the user.  
VARIABLES: XMINSTR                      TYPE: Output
 VARIABLES DESCRIPTION:   If the user wants the message to be from the
 postmaster, then XMINSTR("FROM") will be set to .5; otherwise, nothing will be
 set.  
VARIABLES: XMABORT                      TYPE: Both
 VARIABLES DESCRIPTION:   The calling program will set XMABORT=0.  If, inside
 the called routine, the user enters up-arrow, then XMABORT will be set to 1 to
 indicate that the user chose to abort the process.  
COMPONENT/ENTRY POINT: SENDMSG
 COMPONENT DESCRIPTION:   This entry point takes the special instructions in
 XMINSTR and uses them to set related fields within the message that is being
 created.  
  
 This entry point also tells the user that the message is being sent, and then
 sends it.  
  
 Usage:  D SENDMSG^XMAPHOST(DUZ,XMZ,.XMINSTR) 
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The DUZ of the user sending the message.  
VARIABLES: XMZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The message number of the message.  
VARIABLES: XMINSTR                      TYPE: Input
 VARIABLES DESCRIPTION:   Special instructions for the message, such as who the
 message is to appear to be from, and what basket the user wants the message to
 be delivered to in his own mailbox.  
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

NUMBER: 4037                            IA #: 4037
  FILE NUMBER: 8925.9                   GLOBAL ROOT: TIU(8925.9
  DATE CREATED: AUG 04, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: File 8925.9                     ID: TIU(8925.9
GLOBAL REFERENCE: TIU(8925.9
FIELD NUMBER: 6                         FIELD NAME: ICD9 DIAGNOSIS
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: TIU(8925.9,"B"
FIELD NUMBER: .01                       FIELD NAME: DOCUMENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Order Entry $ORDERs thru the B x-ref and $GETs the 6th
 piece of the 0 node, the ICD9 DIAGNOSIS field.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4038                            IA #: 4038
  FILE NUMBER: 1                        GLOBAL ROOT: %ZTER(1
  DATE CREATED: MAR 26, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            NAME: OR reference to file 1
  ID: %ZTER(1                           STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4040                            IA #: 4040
  FILE NUMBER: 405.1                    GLOBAL ROOT: DG(405.1
  DATE CREATED: MAR 26, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: TIU reference to file 405.1
  ID: DG(405.1                          STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4041                            IA #: 4041
  DATE CREATED: MAR 26, 2003            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         ROUTINE: YTAPI5
  NAME: OR call to YTAPI5               ID: YTAPI5
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GAFURL
COMPONENT/ENTRY POINT: PRIVL
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4042                            IA #: 4042
  DATE CREATED: APR 10, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCEOB
  NAME: DBIA4042                        ID: IBCEOB
 GENERAL DESCRIPTION:   File 361.1 EXPLANATION OF BENEFITS is shared by
 Accounts Receivable and Integrated Billing.  While A/R has full read access to
 the data in this file, adding the data and updating it require entrypoints in
 Integrated Billing.  There are also certain standard functions that are
 needed/used by both Integrated Billing and Accounts Receivable to manipulate
 the data in this file. AR would like to be able to use these functions.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$DUP(IBMSG,IBIFN,IBAMT)
 COMPONENT DESCRIPTION:   This function determines if the EOB data for a given
 bill number already exists in the EXPLANATION OF BENEFITS file (#361.1) by
 comparing the calculated checksum of the raw 835 data of the new EOB for the
 bill against the checksums of each of the bill's existing EOB records.  
VARIABLES: IBIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The pointer (ien) to the bill in file 399.  
VARIABLES: $$DUP                        TYPE: Output
 VARIABLES DESCRIPTION:   FUNCTION RETURNS: 0 if no duplicate was found or the
 ien of the existing entry if found to be a duplicate EOB.  
COMPONENT/ENTRY POINT: $$ADD3611(IBMSG,IBTBILL,IBBATCH,IBIFN,IBAR)
 COMPONENT DESCRIPTION:   Adds a stub record to file 361.1.  
VARIABLES: IBMSG                        TYPE: Input
 VARIABLES DESCRIPTION:   The mailman message # in which the EOB was received.  
VARIABLES: IBTBILL                      TYPE: Input
 VARIABLES DESCRIPTION:   The pointer to the transmitted bill in file 364. 
 Optional for calls from A/R.  
VARIABLES: IBBATCH                      TYPE: Input
 VARIABLES DESCRIPTION:   The pointer to the batch in file 364.1 that the
 transmitted bill was in.  Optional for calls from A/R.  
VARIABLES: IBIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The pointer (ien) to the bill in file 399.  
VARIABLES: IBAR                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag set equal to 1 to indicate the call
 was made from Accounts Receivable.  
VARIABLES: $$ADD3611                    TYPE: Output
 VARIABLES DESCRIPTION:   FUNCTION RETURNS: = -1 if record is not added, ien of
 record if successful.  
COMPONENT/ENTRY POINT: $$UPD3611(IBEOB,IBTDA,IBAR)
 COMPONENT DESCRIPTION:   Adds detail from electronic EOB to file 361.1.  
VARIABLES: IBEOB                        TYPE: Input
 VARIABLES DESCRIPTION:   The ien of the entry in file 361.1 being updated.  
VARIABLES: IBTDA                        TYPE: Input
 VARIABLES DESCRIPTION:   The entry # in the source file where the detail data
 to be stored can be found.  
VARIABLES: IBAR                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag set equal to 1 to indicate the call
 was made from Accounts Receivable.  This determines the name of the source
 file where the detail data will be found.  
COMPONENT/ENTRY POINT: ERRUPD(IBEOB,IBEGBL)
 COMPONENT DESCRIPTION:   Adds error messages to the MESSAGE STORAGE ERRORS
 field.  
VARIABLES: IBEOB                        TYPE: Input
 VARIABLES DESCRIPTION:   The ien of the entry in file 361.1 being updated.  
VARIABLES: IBEGBL                       TYPE: Input
 VARIABLES DESCRIPTION:   The subscript in global ^TMP(subscript,$J, where the
 error text to be stored can be found.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4043                            IA #: 4043
  DATE CREATED: APR 02, 2003            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCAUDT
  NAME: DBIA4043                        ID: PRCAUDT
 GENERAL DESCRIPTION:   It has been decided that an auto-audit of bills in AR
 should be performed when certain electronic claim status messages are received
 in IB.  A new entrypoint is needed with AR to accomplish this.  
  
 ACTION NEEDED: PERFORM AUTO-AUDIT OF A SPECIFIC BILL IN AR 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: AUDITX(PRCABN)
 COMPONENT DESCRIPTION:   PERFORM AUTO-AUDIT OF A SPECIFIC BILL IN AR 
VARIABLES: PRCABN                       TYPE: Input
 VARIABLES DESCRIPTION:   The ien of the bill to be audited in file 430 
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4044                            IA #: 4044
  DATE CREATED: APR 08, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCECSA6
  NAME: DBIA4044                        ID: IBCECSA6
 GENERAL DESCRIPTION:   Return the data from an EOB in a display format.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETEOB(IBCNT,IBSRC)
VARIABLES: IBCNT                        TYPE: Input
 VARIABLES DESCRIPTION:   The ien of the entry in file 361.1 to be displayed.  
VARIABLES: IBSRC                        TYPE: Input
 VARIABLES DESCRIPTION:   A flag to determine the format to return the data in:
 If set to 0 ==> Assumes call was from IB and all data is returned in
 ^TMP("IBCECSD",$J).  If set to 1 ==> Assumes call was from A/R and data is
 returned in ^TMP("PRCA_EOB",$J), but excludes EOB data found on the header
 record when the EOB was received. If set to 2 ==> Assumes call was from A/R
 and all data is returned in ^TMP("PRCA_EOB",$J) 
VARIABLES: OUTPUT GLOBALS               TYPE: Output
 VARIABLES DESCRIPTION:   If the parameter IBSRC is set to 1 or 2, the output
 is provided for AR in ^TMP("PRCA_EOB",$J,n) = a line of formatted data from
 file 361.1 
   where n is the sequential line # for the formatted data from file 361.1 
  
 If the parameter IBSRC = 0 or null, the output is provided for IB in a List
 Manager Format where VALMCNT = the line # within the list manager display CNT
 = the entry # for List Manager selection ^TMP("IBCECSD",$J,VALMCNT,0) = a line
 of formatted data from file 361.1 ^TMP("IBCECSD",$J,"IDX",VALMCNT,CNT) = "" 
 ^TMP("IBCECSD",$J,CNT) = VALMCNT^ien of the entry in file 361.1 
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4045                            IA #: 4045
  DATE CREATED: APR 14, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBJTCA
  NAME: DBIA4045                        ID: IBJTCA
 GENERAL DESCRIPTION:   An entrypoint is needed by A/R to access the TPJI
 (Third Party Joint Inquiry) option from a PROTOCOL action.  The level of entry
 needs to be at the point where a bill number can be assumed and the
 appropriate TPJI list manager screen will be invoked.  This entry point
 already exists at line EN^IBJTCA and A/R would like to have access to this
 call.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TPJI
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Entrypoint to allow access to Third Party Joint
 Inquiry option at the point where the bill and patient iens' are known.  
VARIABLES: IBIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the ien of the bill in the BILL/CLAIMS file
 (#399).  This is a required variable.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The ien of the patient from the PATIENT file (#2). 
 This is a required variable.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4046                            IA #: 4046
  DATE CREATED: APR 09, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: TIUQRY                       NAME: TIU DOCUMENTS
  ID: TIUQRY
 GENERAL DESCRIPTION:   For CPRS Query application, user is allowed to run a
 query to retrieve the TIU document results by specifying the document date
 range, document class, document title etc. An existed TIU API QUERY^TIUQRY
 need to be called to return all of the TIU document query results.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU DOC API
KEYWORDS: TIU QUERY API
COMPONENT/ENTRY POINT: QUERY(ORY,.ORDOC,.ORYPAT)
VARIABLES: ORDOC                        TYPE: Input
 VARIABLES DESCRIPTION:   query strings for TIU documents 
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   TIU document query result.  
VARIABLES: ORYPAT                       TYPE: Input
 VARIABLES DESCRIPTION:   patient data for TIU document query.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4047                            IA #: 4047
  DATE CREATED: APR 09, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBECEA
  NAME: DBIA4047                        ID: IBECEA
 GENERAL DESCRIPTION:   Entrypoint to invoke the Cancel/Edit/Add Patient
 Charges option from Accounts Receivable ERA Worklist option.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN1AR
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4048                            IA #: 4048
  DATE CREATED: APR 11, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBOHPT1
  NAME: DBIA4048                        ID: IBOHPT1
 GENERAL DESCRIPTION:   Entrypoint to invoke the LIST ON HOLD CHARGES option
 from Accounts Receivable ERA Worklist option.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MAIN
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4049                            IA #: 4049
  FILE NUMBER: 350.9                    GLOBAL ROOT: IBE(350.9,
  DATE CREATED: APR 07, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: DBIA4049                        ID: IBE(350.9,
GLOBAL REFERENCE: IBE(350.9,D0,
FIELD NUMBER: 2.06                      FIELD NAME: AGENT CASHIER PHONE NUMBER
  LOCATION: 2;6                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   When an electronic EOB is received in error at a site,
 EDI Lockbox has functionality to transfer that EOB electronically to another
 site.  The AGENT CASHIER PHONE NUMBER field contains the contact information
 for the receiving site to use to contact the sending site if there are
 questions regarding the EOB. Accounts Receivable needs to have read access to
 this data to allow it to be included in the transferred EOB.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4050                            IA #: 4050
  DATE CREATED: APR 07, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCEOBAR
  NAME: DBIA4050                        ID: IBCEOBAR
 GENERAL DESCRIPTION:   File 361.1 EXPLANATION OF BENEFITS is shared by
 Accounts Receivable and Integrated Billing.  When an EOB is applied to A/R
 bills, sometimes a payment is made to the wrong bill or the payment is made to
 one bill and it should have been split between multiple bills. In order to
 keep the AR system in balance with the EOBs on file in file 361.1, AR needs to
 update the AR AMOUNTS DISTRIBUTION field in this file.  This IA is requested
 for an entrypoint to a call within IB to allow A/R to update this data in file 
 361.1, field 8 AR DISTRIBUTION AMOUNTS (multiple field).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SPL1(IB3611,IBBILL,IBBREF,IBAMT)
 COMPONENT DESCRIPTION:   File the corrected payment distribution into the EOB
 in file 361.1 
VARIABLES: IB3611                       TYPE: Input
 VARIABLES DESCRIPTION:   The ien of the entry in file 361.1 to be updated.  
VARIABLES: IBBILL                       TYPE: Input
 VARIABLES DESCRIPTION:   The free text bill number to be added.  
VARIABLES: IBBREF                       TYPE: Input
 VARIABLES DESCRIPTION:   If the bill is in file 399, the pointer to 399,
 otherwise null.  
VARIABLES: IBAMT                        TYPE: Input
 VARIABLES DESCRIPTION:   The amount of the payer's payment to be applied to
 the bill.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4051                            IA #: 4051
  FILE NUMBER: 361.1                    GLOBAL ROOT: IBM(361.1,
  DATE CREATED: APR 07, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4051
  ID: IBM(361.1,
GLOBAL REFERENCE: IBM(361.1,
FIELD NUMBER: .01                       FIELD NAME: BILL
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   File 361.1 EXPLANATION OF BENEFITS is used by
 Integrated Billing to store Electronic Remittance Advices (ERA) that are
 received electronically from MEDICARE (MRAs).  The Accounts Receivable system
 will be receiving Electronic Remittance Advices from payers other than
 MEDICARE via the Third Party Lockbox system.  The file is currently structured
 to allow both types of ERAs to be stored, so it was decided to use the same
 file to store the data, since the data for both is derived from an X12 835
 message and is delivered to VistA using the same file format. As a result of
 this decision, this IA is requested to allow Accounts Receivable to have full 
 direct read access and the ability to use Fileman to define a field as a
 pointer to this file so it can access the data for functions specific to AR
 needs.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4052                            IA #: 4052
  DATE CREATED: JUL 14, 2003            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ICDGTDRG                     NAME: DRG Code APIs
  ID: ICDGTDRG                          STATUS: Active
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: DEC 05, 2019
KEYWORDS: CSV
KEYWORDS: DRG
COMPONENT/ENTRY POINT: $$DRG(CODE,EDT)
 COMPONENT DESCRIPTION:   This DBIA contains a supported DRG API call that can
 be used to access data contained in DRG file (# 80.2). Returns a string of
 information from the DRG file (#80.2) for a given DRG code and effective date. 
 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   REQUIRED - DGN code, ien or .01 value 
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   OPTIONAL - Effective date, default = today (Fileman
 format) 
VARIABLES: $$DRG                        TYPE: Output
 VARIABLES DESCRIPTION:   If DRG code DOES exist in the database then the
 function returns a "^" delimited string with the following pieces: 
  
   1  DRG name (field #.01) 
   2  Weight (field #2) 
   3  Low Trim (days) (field #3) 
   4  High Trim (days) (field #4) 
   5  MDC (field #5) 
   6  Surgery Flag (field #.06) 
   7  <null> 
   8  Avg Length of Stay (days) (field 10) 
   9  Local Low Trim Days (field #11) 
  10  Local High Trim Days (field #12) 
  11  <null> 
  12  Local Breakeven (field #13) 
  13  Activation Date (.01 field of the 66 multiple) 
  14  Status (.03 field of the 66 multiple) 
  15  Inactivation Date (.01 field of the 66 multiple) 
  16  Effective date (.01 field of the 66 multiple) 
  17  Internal Entry Number (IEN) 
  18  Effective date of CSV (.01 field of the 66 multiple) 
  
 If DRG code DOES NOT exist in the database then the function returns a "^"
 delimited string with the following pieces: 
  
   1  -1 
   2  NO SUCH ENTRY 
  14  Status 0=inactive 
  
COMPONENT/ENTRY POINT: $$GETDRG(CODE,DGNDT,FILE)
 COMPONENT DESCRIPTION:   This DBIA contains a supported DRG API call that can
 be used to access data contained in the ICD DIAGNOSIS CODE file (#80) or the
 ICD OPERATION/PROCEDURE CODE file (#80.1). It returns a string of information
 from the file for a given ICD DIAGNOSIS or OPERATION/PROCEDURE CODE and
 effective date.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   REQUIRED - IEN number of the #80 or #80.1 file 
VARIABLES: DGNDT                        TYPE: Input
 VARIABLES DESCRIPTION:   OPTIONAL - Effective date, default = today (Fileman
 format) 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   REQUIRED - file to access - 9:ICD9 (#80), 0:ICD0
 (#80.1) 
VARIABLES: $$GETDRG                     TYPE: Output
 VARIABLES DESCRIPTION:   If the code exists in the database, then the function
 returns a string with ";" delimiters:   
  
 DRG(s) associated with the code (delimited by "^") - can be 1+ (piece
 1);Effective date (piece 2);status flag (piece 3) 
  
 If the code DOES NOT exist in the database then the function returns: 
  
 Piece #1 : -1 Piece #2 : error message Piece #3 : Status = 0 = Inactive 
COMPONENT/ENTRY POINT: $$GETDATE(PATNUM)
 COMPONENT DESCRIPTION:   This DBIA contains a supported DRG API call that can
 be used to access data in the PTF file (#45).  It returns the proper effective
 date for a patient to use in accessing Code Set Versioned data.  
VARIABLES: PATNUM                       TYPE: Input
 VARIABLES DESCRIPTION:   REQUIRED - ien or .01 value for PTF file (#45) 
VARIABLES: $$GETDATE                    TYPE: Output
 VARIABLES DESCRIPTION:   The function returns a Fileman-formatted date of the
 proper date to be used as the effective date.  This date can be either the
 census, discharge, surgery, or movement date.  If all previous dates are
 undefined, today's date is returned.  
COMPONENT/ENTRY POINT: $$ISVALID
 COMPONENT DESCRIPTION:   This DBA contains a supported DRG API call that can
 be used to determine if an ICD DIAGNOSIS CODE (#80) or ICD OPERATION/ 
 PROCEDURE CODE (#80.1)is active for a given effective date.  This API is
 designed for use in DIC("S") Fileman calls.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   REQUIRED  - IEN number of the #80 or #80.1 file entry 
VARIABLES: DGNDT                        TYPE: Input
 VARIABLES DESCRIPTION:   OPTIONAL -Effective date, default = today (Fileman
 format) 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   REQUIRED - file to access - 9:ICD9(#80),
 0:ICD0(#80.1) 
VARIABLES: $$ISVALID                    TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 if the code is active/valid for the
 effective date or 0 if it is undefined or inactive.  
COMPONENT/ENTRY POINT: $$DRGD(CODE,ARRAY,DFN,DATE)
 COMPONENT DESCRIPTION:   Extrinsic function that returns the full versioned
 description of a Diagnostic Related Group (DRG) code, from the 68 node (field
 68) of the DRG file.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either a DRG Code or an Internal Entry Number
 (IEN) in the DRG file (#80.2) 
VARIABLES: ARRAY                        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("DRGD",$J,.  The calling routine is responsible for killing
 ^TMP("DRGD",$J) after the call, if used.  
                             
 On return, the array contains corresponding lines of text of the code's
 versioned description (field 68) 
                             
  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 $$DRGD.  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a Fileman compliant date.  Time is ignored. 
 If the date is not supplied, then today's date is used.  The DRG description
 (long text) will be appropriate for that date.  If no text is found that
 corresponds with the date provided, the oldest possible text will be returned
 and an message will be returned that the "text may be inaccurate".  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the Patient File #2 (for future
 use) 
SUBSCRIBING PACKAGE: FEE BASIS          ISC: Albany
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4053                            IA #: 4053
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XWBSEC                       NAME: DBIA4053
  ID: XWBSEC                            STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
COMPONENT/ENTRY POINT: CHKPRMIT
 COMPONENT DESCRIPTION:   To check whether a user is permitted to execute RPC.  
VARIABLES: FIRST PARAMETER              TYPE: Input
 VARIABLES DESCRIPTION:   This is the name of the RPC for which we would like
 to check if the user has permission to execute.  
VARIABLES: XWBSEC                       TYPE: Output
 VARIABLES DESCRIPTION:   If XWBSEC is not defined the call is considered
 successful, the user has permission to execute the RPC.  
  
 If XWBSEC is defined, the user is considered NOT to have permission to execute
 the RPC, and XWBSEC may contain an explanatory message.  
COMPONENT/ENTRY POINT: CRCONTXT
 COMPONENT DESCRIPTION:   To create a valid RPC Broker context.  
VARIABLES: SECOND PARAMETER             TYPE: Input
 VARIABLES DESCRIPTION:   Name of the option who's context we would like assert
 on behalf of the user.  
VARIABLES: FIRST PARAMETER              TYPE: Output
 VARIABLES DESCRIPTION:   When returned, +result will be 1 if successful, or 0
 if unsuccessful ; if unsuccessful, result may (or may not) also contain the
 textual reason for failure.  
COMPONENT/ENTRY POINT: SET
 COMPONENT DESCRIPTION:   To store the value of DUZ in Broker "state" prior to
 calling CVC^XUSRB (which requires the value to be stored in Broker "state").  
VARIABLES: FIRST PARAMETER              TYPE: Input
 VARIABLES DESCRIPTION:   Variable name to store in RPC Broker State 
VARIABLES: SECOND PARAMETER             TYPE: Input
 VARIABLES DESCRIPTION:   Value of variable to store in RPC Broker state.  
SUBSCRIBING PACKAGE: VISTALINK SECURITY
  ISC: Oakland
SUBSCRIBING PACKAGE: VISTA SERVICES ASSEMBLER

NUMBER: 4054                            IA #: 4054
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUSRB                        NAME: DBIA4054
  ID: XUSRB                             STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
COMPONENT/ENTRY POINT: LOGOUT
 COMPONENT DESCRIPTION:   To log out a VistaLink user from M.  
COMPONENT/ENTRY POINT: CVC
 COMPONENT DESCRIPTION:   To change a VistaLink user's verify code.  
VARIABLES: DUZ                          TYPE: Output
 VARIABLES DESCRIPTION:   If DUZ is defined, we consider the "change verify
 code" operation to have been successful.  
COMPONENT/ENTRY POINT: VALIDAV
 COMPONENT DESCRIPTION:   To validate a VistaLink user's credentials for signon
 to M.  
VARIABLES: FIRST PARAMETER              TYPE: Output
 VARIABLES DESCRIPTION:   
  ;Return R(0)=DUZ, R(1)=(0=OK, 1,2...=Can't sign-on for some reason) 
  ; R(2)=verify needs changing, R(3)=Message, R(4)=0, R(5)=msg cnt, R(5+n) 
  ; R(R(5)+6)=# div user must select from, R(R(5)+6+n)=div 
VARIABLES: SECOND PARAMETER             TYPE: Input
 VARIABLES DESCRIPTION:   A credential (typically the encoded "access
 code;verify code" string) to use to attempt a signon for the current user.  
COMPONENT/ENTRY POINT: SETUP
 COMPONENT DESCRIPTION:   To setup a VistaLink user's partition in M prior to
 signon. 
VARIABLES: XWBTIP                       TYPE: Input
 VARIABLES DESCRIPTION:   We set XWBTIP to the return value of $$GETPEER^%ZOSV
 prior to calling SETUP^XUSRB.  
VARIABLES: FIRST PARAMETER              TYPE: Output
 VARIABLES DESCRIPTION:   upon return, has values set in the following
 subscripts of the first parameter passed by reference: ;0=server name,
 1=volume, 2=uci, 3=device, 4=# attempts, 5=skip signon-screen 
VARIABLES: XWBVER                       TYPE: Input
 VARIABLES DESCRIPTION:   If undefined, or set to less than 1.1, initiating
 Kernel auto-signon will not be supported. If set to 1.1 or higher, the call to
 SETUP^XUSRB will also set up the signon environment such that a subsequent
 call to AUTOXWB^XUSRB can initiate Kernel auto-signon (i.e., create a handle
 with the Broker client agent), if the client agent is running on the 
 workstation.  
COMPONENT/ENTRY POINT: INTRO
 COMPONENT DESCRIPTION:   To retrieve the introductory text from M to display
 in VistaLink.  
VARIABLES: FIRST PARAMETER              TYPE: Output
 VARIABLES DESCRIPTION:   Each line in the introductory text is returned as a
 value stored at the first subscript level node of the pass-by-reference first
 parameter to the method call. E.g., 
  
 RETURN(0)=line 1 RETURN(1)=line 2 etc.  
COMPONENT/ENTRY POINT: $$VCVALID()
 COMPONENT DESCRIPTION:   Used during the VistALink reauthentication process,
 which includes support for the login capabilities of FatKAAT and KAAJEE, to
 check whether a user's verify code is current.  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN for the user in the New Person file.  
VARIABLES: $$VCVALID                    TYPE: Output
 VARIABLES DESCRIPTION:   Performs validity checks using the DUZ value.  
  0 if the verify code is current 
  1 if the verify code needs to be changed 
COMPONENT/ENTRY POINT: $$INHIB1()
 COMPONENT DESCRIPTION:   Used by VistALink prior to listener creation and also
 during the reauthentication process to check whether logins are inhibited for
 a volume set.  
  
 Environment/volume set parameters are already defined via call to XUVOL^XUS
 (see IA #4762 for more information).  
VARIABLES: $$INHIB1                     TYPE: Output
 VARIABLES DESCRIPTION:   
  0 - if logins are allowed 
  1 - if logins to volume set are inhibited (disabled) 
COMPONENT/ENTRY POINT: $$INHIB2()
 COMPONENT DESCRIPTION:   
  Used by VistALink prior to listener creation to check if all available job
 slots for a volume set are used.  
  
 Environment/volume set parameters are already defined via call to XUVOL^XUS
 (see IA #4762 for more information).  
VARIABLES: $$INHIB2                     TYPE: Output
 VARIABLES DESCRIPTION:   
  0 - if job slots are available 
  2 - if all job slots are used 
SUBSCRIBING PACKAGE: VISTALINK SECURITY
  ISC: Oakland
SUBSCRIBING PACKAGE: VISTA SERVICES ASSEMBLER

NUMBER: 4055                            IA #: 4055
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUSRB2                       NAME: DBIA4055
  ID: XUSRB2                            STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
COMPONENT/ENTRY POINT: DIVGET
 COMPONENT DESCRIPTION:   Retrieve the list of divisions for the current user.  
VARIABLES: FIRST PARAMETER              TYPE: Output
 VARIABLES DESCRIPTION:   If + of the value at the first-level 0 subscript of
 the return value is false, then the user does not have any divisions to select
 from.  
  
 Otherwise, for each division that a user has, a node will be present in the
 return value, at the first subscript level, starting at 0 and incrementing
 from there. The value of the node is three pieces: 
  
   ien^division name^station # 
VARIABLES: SECOND PARAMETER             TYPE: Input
 VARIABLES DESCRIPTION:   The DUZ of the user we're getting the division list
 for.  
COMPONENT/ENTRY POINT: DIVSET
 COMPONENT DESCRIPTION:   Set the division for the current user.  
VARIABLES: FIRST PARAMETER              TYPE: Output
 VARIABLES DESCRIPTION:   If +return value is true, division selection is
 considered successful. If false, division selection failed.  
VARIABLES: SECOND PARAMETER             TYPE: Input
 VARIABLES DESCRIPTION:   This is the division to select. If passed with a
 leading ` an IEN is being passed and will be processed as such.  
COMPONENT/ENTRY POINT: USERINFO
 COMPONENT DESCRIPTION:   Retrieve various user demographic info for current
 user.  
VARIABLES: FIRST PARAMETER              TYPE: Output
 VARIABLES DESCRIPTION:   RETURN(1)=user's name from the .01 field of the New
 Person file RETURN(2)=concatenated user name from the NAME COMPONENTS file 
 RETURN(3)=logged on division: ien^name^number RETURN(4)=user's title from New
 Person file RETURN(5)=user's service section from New Person file (external
 format) RETURN(6)=user's language from the New Person file RETURN(7)=user's
 timeout 
SUBSCRIBING PACKAGE: VISTALINK SECURITY
  ISC: Oakland
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: VISTA SERVICES ASSEMBLER
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 10/3/24 effective with patch DSIY*1.5*6 to
 support functionality associated with determining which Divisions the user has
 access to.  
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/3/24 effective with patch DSSO*2.0*8 to
 support functionality associated with determining which Divisions the user has
 access to.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 2/26/25, effective with patch OR*3*361, released
 8/5/2014, to call USERINFO^XUSRB2. 
SUBSCRIBING PACKAGE: PROBLEM LIST
 SUBSCRIBING DETAILS:   Added 2/26/25, effective with patch GMPL*2*36, released
 6/10/2013, to call USERINFO^XUSRB2. 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Added 2/26/25, effective with patch TIU*1*244, released
 6/3/2010, to call USERINFO^XUSRB2.  

NUMBER: 4056                            IA #: 4056
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: %ZOSV                        NAME: DBIA4056
  ID: %ZOSV
 GENERAL DESCRIPTION:   VistaLink requests use of the following API: 
  
 GETPEER^%ZOSV 
  
 The VistaLink security module uses this to retrieve an IP address value for
 the current session, which is required as input (in the XWBTIP variable) into
 another call, SETUP^XUSRB.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETPEER
 COMPONENT DESCRIPTION:   The VistaLink security module uses this to retrieve
 an IP address value for the current session, which is required as input (in
 the XWBTIP variable) into another call, SETUP^XUSRB.  
VARIABLES: RETURN VALUE                 TYPE: Output
 VARIABLES DESCRIPTION:   The IP address of the current connected session to M. 
 
SUBSCRIBING PACKAGE: VISTALINK SECURITY
  ISC: Oakland

NUMBER: 4057                            IA #: 4057
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUS2                         NAME: DBIA4057
  ID: XUS2                              STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
COMPONENT/ENTRY POINT: AVHLPTXT
 COMPONENT DESCRIPTION:   Retrieves help text to display to the user when they
 change their verify code.  
VARIABLES: RETURN VALUE                 TYPE: Output
 VARIABLES DESCRIPTION:   The help text for a user to use when entering a new
 verify code. 
SUBSCRIBING PACKAGE: VISTALINK SECURITY
  ISC: Oakland

NUMBER: 4058                            IA #: 4058
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4058                        ID: VA(200
GLOBAL REFERENCE: VA(200,D0,2,"AX1",1,
 GLOBAL DESCRIPTION:   ^VA(200,DUZ,2,"AX1",1,_____) is the index on default
 division for the user. If they've designated a default division, the IEN of
 that division in the Insitution file will be the first sixth-level subscript
 at the global location above.  
GLOBAL REFERENCE: VA(200,"A",2,AC,
 GLOBAL DESCRIPTION:   The A x-ref is used to obtain the user's DUZ from the
 encrypted value for the Access Code.  
GLOBAL REFERENCE: VA(200,
FIELD NUMBER: 11                        FIELD NAME: VERIFY CODE
  LOCATION: .1;2                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
SUBSCRIBING PACKAGE: VISTALINK SECURITY
  ISC: Oakland

NUMBER: 4059                            IA #: 4059
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4059
 GENERAL DESCRIPTION:   VistaLink requests permission to set, check and kill
 the local variables XQY and XQY0 which represent a user's RPC Broker context. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
COMPONENT/ENTRY POINT: XQY
 COMPONENT DESCRIPTION:   This is one of two variables that represent a user's
 RPC Broker context.  
COMPONENT/ENTRY POINT: XQY0
 COMPONENT DESCRIPTION:   This is one of two variables that represent a user's
 RPC Broker context.  
SUBSCRIBING PACKAGE: VISTALINK SECURITY
  ISC: Oakland

NUMBER: 4060                            IA #: 4060
  DATE CREATED: MAY 29, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUS1B                        NAME: DBIA4060
  ID: XUS1B
 GENERAL DESCRIPTION:   VistaLink wishes to use the Kernel entry point
 $$AUTOXWB^XUS1B to support Kernel auto-signon. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: AUTOXWB
 COMPONENT DESCRIPTION:   This entry point decides whether to perform a Kernel
 auto-signon for the current process. If circumstances (prior login, matching
 IP address to prior login, Kernel setting, etc.) are correct, this call
 returns the DUZ of the user, meaning that signon of this user will be through
 Kernel auto-signon; then, two subsequent calls (NOW^XUSRB and $$POST^XUSRB)
 can be made to complete the Kernel auto-signon. Otherwise, the user should be 
 signed on the normal way, not through Kernel auto-signon.  
VARIABLES: $$AUTOXWB                    TYPE: Output
 VARIABLES DESCRIPTION:   If return value is greater than 0, auto-signon was
 successful. The return value will be set to the what DUZ *should* be set to;
 it is then the responsibility of the code calling $$AUTOXWB to actually set
 DUZ to the value returned by $$AUTOXWB.  
  
 Otherwise, if the return value not greater than zero, auto-signon failed, and
 the calling code should kill DUZ if it exists.  
SUBSCRIBING PACKAGE: VISTALINK SECURITY
  ISC: Oakland

NUMBER: 4061                            IA #: 4061
  DATE CREATED: JUN 04, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUSRB                        NAME: DBIA4061
  ID: XUSRB
 GENERAL DESCRIPTION:   VistaLink wishes to use two calls, NOW^XUSRB and
 $$POST^XUSRB, to complete Kernel auto-signon for users that pass the initial
 auto-signon check ($$AUTOXWB^XUS1B). 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: NOW
 COMPONENT DESCRIPTION:   Sets up certain Kernel environment variables.  
VARIABLES: U                            TYPE: Output
 VARIABLES DESCRIPTION:   Sets to "^".  
VARIABLES: XUNOW                        TYPE: Output
 VARIABLES DESCRIPTION:   Sets to the current FileMan Date/Time.  
VARIABLES: DT                           TYPE: Output
 VARIABLES DESCRIPTION:   Sets to the current FileMan date.  
VARIABLES: XUDEV                        TYPE: Output
 VARIABLES DESCRIPTION:   Sets to 0.  
COMPONENT/ENTRY POINT: $$POST
 COMPONENT DESCRIPTION:   Finishes setting up user partition as part of signon.
 In support of Kernel auto-signon, can be called after successful sequenced
 calls to AUTOXWB^XUS1B() and NOW^XUSRB.  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The DUZ of the user, as returned by $$AUTOXWB^XUS1B.  
VARIABLES: $$POST                       TYPE: Output
 VARIABLES DESCRIPTION:   In the context of autosignon: 
  
 If the return value from $$POST is 0, then the call was successful.  
  
 If the return value is greater than 0, then the call was unsuccessful, and the
 calling code should kill DUZ (if it exists), as auto-signon was unsuccessful.  
VARIABLES: DUZ                          TYPE: Output
 VARIABLES DESCRIPTION:   DUZ("AG") is returned as the user's agency code.  
  
 DUZ(2) is returned set to the institution # the user is affiliated with. Note
 that if the user is multidivisional, the value returned from this call does
 not reflect that, and so an additional call to another function is required to
 determine if a user is multidivisional, and if so, to select from their list
 of divisions -- which will change the value of DUZ(2) at that point.  
VARIABLES: DTIME                        TYPE: Output
 VARIABLES DESCRIPTION:   DTIME is set to the user's DTIME setting after this
 call.  
SUBSCRIBING PACKAGE: VISTALINK SECURITY
  ISC: Oakland

NUMBER: 4069                            IA #: 4069
  FILE NUMBER: 772                      GLOBAL ROOT: HL(772,
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: HL7 MESSAGE TEXT FILE (#772)    ID: HL(772,
GLOBAL REFERENCE: HL(772,
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: 5                         FIELD NAME: RELATED MAILMAN MESSAGE
  LOCATION: 0;5                         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
FIELD NUMBER: 200                       FIELD NAME: MESSAGE TEXT
  LOCATION: IN;D1;0                     ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: HL(772,"B",
 GLOBAL DESCRIPTION:   Direct global read access to "B" x-ref.  
 GENERAL DESCRIPTION:   This integration agreement will be used for all
 references to all structures in the HL7 Message Text File (#772) file.  Each
 reference by package is included in the SUBSCRIBING DETAILS for each
 subscribing package.  
  
 As new requests to this file are received and accepted by the VistA HL7 
 development staff, this integration agreement will be updated.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IFCAP
 SUBSCRIBING DETAILS:   Read access to DATE/TIME ENTERED field .01 and MESSGE
 TEXT field 200.  
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
 SUBSCRIBING DETAILS:   Read access to RELATED MAILMAN MESSAGE field 5.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Read access to ^HL(772,"B", 
SUBSCRIBING PACKAGE: EVENT CAPTURE
 SUBSCRIBING DETAILS:   Read access to MESSAGE TEXT field 200.  
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
 SUBSCRIBING DETAILS:   Read access to DATA/TIME ENTERED field .01 
           TRANSMISSION TYPE field 4 
           RELATED EVENT PROTOCOL field 10 
           ^HL(772,"B", x-ref 
           STATUS field 20 
           DATE/TIME PROCESSED field 21 
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   Read access to STATUS field 20.  
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   Read access only.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
 SUBSCRIBING DETAILS:   Read access only.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   3/10/25 Update: Since May 2024, effective with
 GMRC*3.0*196 patch CPRS Sustainment team stopped sending messages into the
 interface. This wasn't a full deprecation or removal of all the pieces but
 doing just the bare minimum to disable the interface such as disabling of
 protocols, links and minimal code changes to quit out of any process hooks
 into the interface.  
  
 Read Access only. GMRC has an HL7 interface with a Referral & Authorization
 System (RAS) database in the Austin FSC. Certain types of consults are sent to
 RAS in support of Veterans being approved for community (non-VA) care.
 Occasionally, there may be an issue in parsing the data sent from GMRC to RAS.
 When this occurs, a mail message is generated from the data in the ACK
 message. The mail message contains the Message ID of the offending HL7
 message. GMRC would like to extend the information in the mail message by
 adding the consult record number. To do that, GMRC will take the Message ID
 from the ACK, look up the associated HL7 Message Text, and then parse the
 Message Text (772;200) in order to retrieve the consult record number.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Read access only. Added 3/5/25 effective with TIU*1*360
 patch to extract fields from the HL7 record(s) and put into a new file
 (#101.22)  This file will be used to display a dispensing report from
 VistA/CPRS for the OTP clinics. The Methadone Dispensing Tracking Project
 improves the ability to safely manage the dispensing and monitoring of the
 Medications for Opioid Use Disorder (MOUD) for Veterans participating in an
 Opioid Treatment Program (OTP). TIU will be using the HL7 interface to create
 a dispense report from those sites using an OTP (Opioid Treatment Program)
 system. The routine will use data from the HL7 MESSAGE TEXT file (#772) and
 will need direct global read/fileman access to FIELD # .01, FIELD #10, and
 FIELD NUMBER 200.  
  DATE ACTIVATED: JAN 24, 2007

NUMBER: 4071                            IA #: 4071
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSOLBL3                      NAME: 4071
  ID: PSOLBL3                           STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: CMOP
KEYWORDS: SIG
KEYWORDS: Other Language
COMPONENT/ENTRY POINT: OTHL1
 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 obtain the prescription SIG in the other
 language.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   The input variable RX, which contains the internal
 entry number from the Prescription file(#52), is passed to PSOLBL3.  
VARIABLES: SIG(XX)                      TYPE: Output
 VARIABLES DESCRIPTION:   The "other language" SIG is appended to the SIG2(xx)
 array.  
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham

NUMBER: 4072                            IA #: 4072
  FILE NUMBER: 8925.6                   GLOBAL ROOT: TIU(8925.6,
  DATE CREATED: APR 10, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORRHCT                       NAME: Access to TIU STATUS file
  ID: ORRHCT
GLOBAL REFERENCE: TIU(8925.6,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Users using CPRS Query application are allowed to query
 TIU document results by defining the query categories such as document status,
 document class etc.  In order to present users the list of document statuses
 for selection, the access to the "TIU STATUS" file is needed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: access to TIU file
COMPONENT/ENTRY POINT: DOCSTS
COMPONENT/ENTRY POINT: DOCCLS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING

NUMBER: 4073                            IA #: 4073
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: RPC BROKER
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS GET TOKEN
  REMOTE PROCEDURE: XUS GET TOKEN
 GENERAL DESCRIPTION:   From inside CPRS, the Event Capture Interface could be
 launched without presenting the scond log on window for user(so called silent
 sign-on). In order to fulfill it, CPRS need to call broker's RPC "XUS GET
 TOKEN" to get application handle and pass this handle to the Event Capture for
 silent log on. Because the RPC "XUS GET TOKEN" is not automatically available
 to the CPRS user, OE/RR has to export this RPC into the CPRS menu option "OR
 CPRS GUI CHART" to avoid missing RPC error when launching Event Capture
 Interface application.  
  
 CPRS will insert RPC "XUS GET TOKEN" into "OR CPRS GUI CHART" menu option by 
 following code: EN     ;       N RPC,MENU 
         S RPC="XUS GET TOKEN" 
         S MENU="OR CPRS GUI CHART" 
         D INSERT(MENU,RPC) 
         Q 
         ;
 INSERT(OPTION,RPC)      ; Call FM Updater with each RPC 
         ; Input  -- OPTION   Option file (#19) Name field (#.01) 
         ;           RPC      RPC sub-file (#19.05) RPC field (#.01) 
         ; Output -- None 
         N FDA,FDAIEN,ERR,DIERR 
         S FDA(19,"?1,",.01)=OPTION 
         S FDA(19.05,"?+2,?1,",.01)=RPC 
         D UPDATE^DIE("E","FDA","FDAIEN","ERR") 
         Q 
  
 Will no longer be needed after release of XWB*1.1*30.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 2003
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4074                            IA #: 4074
  DATE CREATED: APR 02, 2003            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSJORUT2                     NAME: OR Call to PSJORUT2
  ID: PSJORUT2
 GENERAL DESCRIPTION:   This API is intended for use only for Med Order Button
 IV Orders. It will return the list of valid Additives and Solutions to CPRS
 for the creation of an IV Order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ENVOL2
 COMPONENT DESCRIPTION:   This is intended for use for Med Order Button IV
 orders only.  
VARIABLES: PN                           TYPE: Input
 VARIABLES DESCRIPTION:   This variable must contain  "A" or "B" or this API
 will quit.  "A" represents Additives, and "B" represents Solutions.  
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   This is an array that is initially passed in from
 CPRS by reference. When built by this API, the array will have the following
 structure: 
  
 ARRAY = n 
  
 ARRAY(IEN) = ^DRUG UNIT (for Additives) 
  
 ARRAY(IEN) = VOLUME (for Solutions) 
  
 n = 0 or 1.  The value is 0 if there is no data found, or 1 if there is data.  
  
 IEN = the IEN in ^PS(52.6 for additives and in ^PS(52.7 for solutions.  
  
 DRUG UNIT = the drug units for the additive.  Examples are MG, MMOL, etc.  
  
 VOLUME = the volume of the solution.  Examples are ML and L.  
  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
  DATE ACTIVATED: JUL 28, 2008

NUMBER: 4075                            IA #: 4075
  DATE CREATED: MAR 02, 2004
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: TIUSRVP                      NAME: OR CALL TO TIUSRVP
  ID: TIUSRVP                           STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$VSTRBLD(VISIT)
 COMPONENT DESCRIPTION:   if TIU has a 1207 node, then we let you create the
 visit string.  Otherwise we do it ourselves.  
VARIABLES: VISIT                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN in file 8925 
VARIABLES: $$VSTRBLD                    TYPE: Output
 VARIABLES DESCRIPTION:   
  VSTR^AUTHOR for a note 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be referencing this API in VIAB NOTEVSTR RPC.  

NUMBER: 4076                            IA #: 4076
  FILE NUMBER: 405                      GLOBAL ROOT: DGPM
  DATE CREATED: AUG 16, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: TIU Reference to file DGPM      ID: DGPM
GLOBAL REFERENCE: DGPM(
FIELD NUMBER: .17                       FIELD NAME: DISCHARGE/CHECK-OUT MOVEMENT
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4077                            IA #: 4077
  DATE CREATED: APR 02, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         ROUTINE: XQORM1
  NAME: OR Call to XQORM1               ID: XQORM1
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4078                            IA #: 4078
  FILE NUMBER: 2                        GLOBAL ROOT: DD(2
  DATE CREATED: APR 09, 2003            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ID Node in PATIENT (#2) file, field 994
  ID: DD(2
 GENERAL DESCRIPTION:   
  DG*5.3*505 exports a new field, MULTIPLE BIRTH INDICATOR (#994), to the 
  PATIENT (#2) file.  This field is to be an identifier.  
     
  KIDS does not automatically export the identifier on the new field, as 
  it is distributed in a partial DD.  
   
  The post-init routine, DG505PST, will set the "ID" node: 
   
  DG505PST -- 
         ;BIR/PTD-PATCH DG*5.3*505 POST INSTALLATION ROUTINE ;4/7/03 
        ;;5.3;Registration;**505**;Aug 13, 1993 
        ;
  EN     ;Entry point 
        ;Update identifier code for MULTIPLE BIRTH INDICATOR (#994) field 
         in PATIENT (#2) file 
        D BMES^XPDUTL(" Updating the identifier code for the MULTIPLE 
         BIRTH INDICATOR (#994) field.") 
        S ^DD(2,0,"ID",994)="D EN^DDIOL($$GET1^DIQ(2,Y_"","",994),"""", 
         ""?$X+2"")" 
        Q 
        ;
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4079                            IA #: 4079
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: APR 08, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Edit PATIENT (#2) file fields
  ID: DPT(
GLOBAL REFERENCE: DPT(D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
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: .09                       FIELD NAME: SOCIAL SECURITY NUMBER
  LOCATION: 0;9                         ACCESS: Write w/Fileman
FIELD NUMBER: .092                      FIELD NAME: PLACE OF BIRTH [CITY]
  LOCATION: 0;11                        ACCESS: Write w/Fileman
FIELD NUMBER: .093                      FIELD NAME: PLACE OF BIRTH [STATE]
  LOCATION: 0;12                        ACCESS: Write w/Fileman
FIELD NUMBER: .2403                     FIELD NAME: MOTHER'S MAIDEN NAME
  LOCATION: .24;3                       ACCESS: Write w/Fileman
FIELD NUMBER: 994                       FIELD NAME: MULTIPLE BIRTH INDICATOR
  LOCATION: MPIMB;1                     ACCESS: Write w/Fileman
GLOBAL REFERENCE: DPT(D0,.01
FIELD NUMBER: .01                       FIELD NAME: ALIAS
  LOCATION: .01;1                       ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   
  To support the MPI Changes Project - Iteration One, selected identifying 
  fields in the PATIENT (#2) file must be asked before the query to the MPI 
  system.  This allows these fields to be available to be used in an enhanced 
  matching algorithm.  
  
  Therefore, Master Patient Index Vista requests permission to add the 
  following PATIENT (#2) file fields to the API that is currently called 
  from the various registration options where this functionality is needed.  
   
  The code added to routine ^MPIFAPI does the following.  
  1. check for variable MPIFS - if it exists, don't ask anything since 
  this is from the background job for SmartCard.  
  2. check for variable DGNEW 
           If $G(DGNEW)=1, this is registration of a new patient; only ask 
           for the following fields since NAME, DOB, SEX, SSN, MULTIPLE 
           BIRTH INDICATOR have just been asked.  
                MOTHER'S MAIDEN NAME 
                PLACE OF BIRTH [CITY] 
                PLACE OF BIRTH [STATE] 
                ALIAS 
           If DGNEW="" or doesn't exist, this is an existing patient; so 
           also ask/verify the following fields.  
                NAME 
                DATE OF BIRTH 
                SEX 
                SOCIAL SECURITY NUMBER 
                MULTIPLE BIRTH INDICATOR 
   
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA

NUMBER: 4080                            IA #: 4080
  DATE CREATED: APR 09, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGUTL3                       NAME: BAD ADDRESS INDICATOR
  ID: DGUTL3
 GENERAL DESCRIPTION:   This DBIA will allow applications outside of
 Registration to access the Bad Address Indicator field added with patch
 DG*5.3*506.  This should help prevent the mailing of medication and other
 correspondence to known bad addresses, and will also prevent Bad Addresses
 from being shared with other facilities through the Health Eligibility Center
 (via Z07/Z05 messaging).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BAD ADDRESS
KEYWORDS: ADDRESS
COMPONENT/ENTRY POINT: $$BADADR(DFN)
 COMPONENT DESCRIPTION:   This extrinsic function will return the "Bad Address
 Indicator" for a patient. This will be a supported API for outside packages to
 call when/if they need to return the Bad Address Indicator.  
  
 If the patient has a Bad Address Indicator set, the return value will be 1, 2, 
 or 3.  If the Indicator is not set, then null is returned.  The following list 
 identifies what the numeric values represent: 
  
      1 - UNDELIVERABLE 
      2 - HOMELESS 
      3 - OTHER 
  
 Please see field # .121 of the Patient file (#2) for further details.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number of the patient in
 the Patient (#2) file.  

NUMBER: 4081                            IA #: 4081
  FILE NUMBER: 8925                     GLOBAL ROOT: TIU(8925
  DATE CREATED: APR 25, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Advanced Directives Query       ID: TIU(8925
GLOBAL REFERENCE: TIU(8925,'B',TITLE,D0)
 GLOBAL DESCRIPTION:   The purpose of this index read is to find notes of a
 given title. 
GLOBAL REFERENCE: TIU(8925,
FIELD NUMBER: 1507                      FIELD NAME: COSIGNATURE DATE/TIME
  LOCATION: 15;7                        ACCESS: Read w/Fileman
FIELD NUMBER: 1501                      FIELD NAME: SIGNATURE DATE/TIME
  LOCATION: 15;1                        ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: STATUS
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 1603                      FIELD NAME: AMENDMENT SIGNED
  LOCATION: 16;3                        ACCESS: Read w/Fileman
FIELD NUMBER: 1606                      FIELD NAME: ADMINISTRATIVE CLOSURE DATE
  LOCATION: 16;6                        ACCESS: Read w/Fileman
FIELD NUMBER: 1613                      FIELD NAME: ADMINISTATIVE CLOSURE MODE
  LOCATION: 16;13                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   We have been tasked to report the total 30-day count of
 advanced directives at sites and to compare that count to the Imaging packages 
 "scanned" Advanced directives.  This report is to be used by Vista 
 administrators as a productivity tool (metric) and has been requested by Laura
 Miller, the VHA's Deputy under-secretary of Health. I have a server job that
 runs on the 15th of every month that gathers a comprehensive set of Vista
 activity values that includes Images captured and displayed, software version
 numbers, patient counts, provider counts, image types.  My plan  is to use
 this server methodology to deliver the advanced directives counts to our local
 account that rolls up this data into a viewable database.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: HEALTH SUMMARY

NUMBER: 4082                            IA #: 4082
  FILE NUMBER: 8925.1                   GLOBAL ROOT: TIU(8925.1,
  DATE CREATED: APR 10, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Access to TIU DOCUMENT DEFINITION file
  ID: TIU(8925.1,
GLOBAL REFERENCE: TIU(8925.1,D0,10,
FIELD NUMBER: .01                       FIELD NAME: ITEM
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: MENU TEXT
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Users using CPRS Query application are allowed to query
 TIU document results by defining the query categories such as document status,
 document class etc.  In order to present users the list of TIU document
 classes for selection, the access to "TIU DOCUMENT DEFINITION" file is needed 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: access to TIU file
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4083                            IA #: 4083
  DATE CREATED: APR 14, 2003            CUSTODIAL PACKAGE: LEXICON UTILITY
  CUSTODIAL ISC: Dallas                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: LEXSRC2                      NAME: LEXICON CODE STATUS
  ID: LEXSRC2                           STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: LEXSRC2
KEYWORDS: STATCHK
COMPONENT/ENTRY POINT: $$STATCHK(CODE,DATE,.LEX,SAB)
 COMPONENT DESCRIPTION:   This entry point is used to check the activation
 status of a code in the Lexicon Utility.  
VARIABLES: CODE                         TYPE: Input
  VARIABLE SEQUENCE NUMBER: 1
 VARIABLES DESCRIPTION:   This is a code taken from a classification system 
 contained in the Lexicon (i.e., ICD, CPT, etc.) 
VARIABLES: DATE                         TYPE: Input
  VARIABLE SEQUENCE NUMBER: 2
 VARIABLES DESCRIPTION:   This is the date used to determine if a code was
 either active or inactive on a specific date.  If not supplied, TODAY will be
 used as the date.  
VARIABLES: .LEX                         TYPE: Input
  VARIABLE SEQUENCE NUMBER: 3
 VARIABLES DESCRIPTION:   (Optional) This is a local array, passed by
 reference.  When passed it will return information about the code.  
VARIABLES: SAB                          TYPE: Input
  VARIABLE SEQUENCE NUMBER: 4
 VARIABLES DESCRIPTION:   (Optional) This is the source of the code.  It is
 either a pointer to the CODING SYSTEMS file 757.03 or the source abbreviation
 expressed as the first 3 characters of the source in file 757.03.  
VARIABLES: $$STATCHK                    TYPE: Output
 VARIABLES DESCRIPTION:   This is a two piece "^" delimiteds tring in the
 following formats: 
  
 RETURNS                    INDICATES 
 -----------------          ---------------------------------
 1 ^ IEN ^ Date             The code is active on the date returned and 
                            stored in ^LEX(757.02,IEN,0) 
  
 0 ^ IEN ^ Date             The code is inactive on the date returned and 
                            stored in ^LEX(757.02,IEN,0) 
  
 0 ^ -1                     Code is not found in the Lexicon 
VARIABLES: LEX                          TYPE: Output
 VARIABLES DESCRIPTION:   (Optional) This is a local array passed by reference. 
 If passed it will contain information about the code in the following
 formatted subscripts: 
  
 LEX(0) = <ien 757.02> ^ <code> 
           2-piece String containing the IEN of the code and the code 
  
 LEX(1) = <ien 757.01> ^ <expression> 
           2-piece String containing the IEN of the code's expression 
           and the expression 
  
 LEX(2) = <ien 757.03> ^ <abbr> ^ <nomen> ^ <name> 
           4-peice String containing the IEN of the code's classification 
           system, the source abbreviation, Nomenclature and the name of 
           the classification system 
  DATE ACTIVATED: SEP 18, 2008

NUMBER: 4084                            IA #: 4084
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 30, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: FILE 44 AC X-REF                ID: SC(
GLOBAL REFERENCE: SC('AC',
FIELD NUMBER: 2.1                       FIELD NAME: TYPE EXTENSION
  LOCATION: 0;22                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This agreement allows permission to loop through the AC
 cross-reference on the HOSPITAL LOCATION file (#44). The AC cross-reference is
 on the TYPE EXTENSION field (#2.1). Using the AC cross-reference will allow us
 to get the internal entry numbers (IENs) for locations by their type (e.g.,
 retrieve only clinics). Using the AC cross-reference will speed up the
 retrieval of IENs.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AC
KEYWORDS: TYPE EXTENSION
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  ISC: Hines
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE
  DATE ACTIVATED: JAN 31, 2007

NUMBER: 4085                            IA #: 4085
  DATE CREATED: APR 30, 2003            CUSTODIAL PACKAGE: RPC BROKER
  USAGE: Private                        TYPE: File
  NAME: DBIA4085                        STATUS: Withdrawn
SUBSCRIBING PACKAGE: VISTALINK          ISC: Albany

NUMBER: 4086                            IA #: 4086
  FILE NUMBER: 19.2                     GLOBAL ROOT: DIC(19.2,
  DATE CREATED: MAY 05, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: MODIFY OPTION SCHEDULING FILE FIELDS
  ID: DIC(19.2,
GLOBAL REFERENCE: DIC(19.2,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: SPECIAL QUEUEING
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(19.2,DA(1),2,0)
FIELD NUMBER: 10                        FIELD NAME: OTHER PARAMETERS
  LOCATION: 2;0                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This multiple holds name-value pairs that are setup
 before the option is run.  
FIELD NUMBER: .01                       FIELD NAME: VARIABLE NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Read, write and remove name-value pairs 
FIELD NUMBER: 1                         FIELD NAME: VALUE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Read, write and remove name-value pairs 
 GENERAL DESCRIPTION:   Add VistALink option XOBV LISTENER STARTUP to the
 OPTIONS SCHEDULING file (#19.2) during the post-installation phase of the
 VistALink package.  Also, perform a lookup on the "B" cross reference of the
 new entry, and as part of the post-installation display this record's zero
 node.  
  
 Revision History: 
  - 2/28/25, effective with DVBA*2.7*253, added new OTHER PARAMETERS (#10) 
 multiple, and the VARIABLE NAME (#.01) and VALUE (#1) fields, where field 
 content can be added, modified or removed when the package owns the namespaced
 entry being modified.   
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
SUBSCRIBING PACKAGE: VISTALINK          ISC: Albany
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Added 2/28/25, effective with DVBA*2.7*253 to add,
 modify and remove OTHER PARAMETERS variable name-value pairs.  

NUMBER: 4087                            IA #: 4087
  FILE NUMBER: 14.7                     GLOBAL ROOT: %ZIS(14.7,
  DATE CREATED: MAY 05, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4087                        ID: %ZIS(14.7,
GLOBAL REFERENCE: %ZIS(14.7,'B',
 GENERAL DESCRIPTION:   Perform a "B" cross reference lookup on the BOX-VOLUME
 PAIR field of the TASKMAN SITE PARAMETERS file (#14.7) to obtain the
 BOX-VOLUME pair for the current system.  This will be used to lookup the
 correct entry in the VISTALINK SITE PARAMETERS file (#18.01) prior to starting
 a VistALink Listener configuration on a Cache-NT system.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
SUBSCRIBING PACKAGE: VISTALINK          ISC: Albany

NUMBER: 4088                            IA #: 4088
  FILE NUMBER: 8989.3                   GLOBAL ROOT: XTV(8989.3,
  DATE CREATED: MAY 15, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4088                        ID: XTV(8989.3,
GLOBAL REFERENCE: XTV(8989.3,1,4,'B',
 GENERAL DESCRIPTION:   Perform a lookup on the "B" cross reference of the
 VOLUME SET sub-field (#.01) within the VOLUME SET multiple (#8989.304) of the
 KERNEL SITE PARAMETERS file (#8989.3) to obtain the volume set.  This will be
 used as an input variable (XUVOL) to the call $$INHIBIT^XUSRB() to determine
 if a new process can be started.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
SUBSCRIBING PACKAGE: VISTALINK          ISC: Albany

NUMBER: 4089                            IA #: 4089
  DATE CREATED: MAY 05, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4089
 GENERAL DESCRIPTION:   During the installation of the VistALink package, add
 the Foundations Management submenu to the Operations Management menu under the
 Systems Manager (EVE) menu.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
SUBSCRIBING PACKAGE: VISTALINK          ISC: Albany

NUMBER: 4090                            IA #: 4090
  DATE CREATED: JUN 16, 2003            CUSTODIAL PACKAGE: VISTALINK
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XOBVLIB                      NAME: VISTALINK SUPPORTED CALLS
  ID: XOBVLIB
 GENERAL DESCRIPTION:   Supported reference to allow other packages to access
 VistALink application developer calls.  These calls address XML processing and
 RPC timeout handling.  
  
 XML processing call tags 
 ======================== 
 $$XMLHDR()                                                             
 $$CHARCHK(STR)                                                         
  
 RPC timeout handling call tags 
 ============================== 
 $$STOP()                                                               
 $$GETTO()                                                              
 $$SETTO(TO)                                                            
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
KEYWORDS: XML
KEYWORDS: RPC
COMPONENT/ENTRY POINT: $$XMLHDR()
 COMPONENT DESCRIPTION:   Provides the current XML standard header.  
  
 Example: 
  
 DEV> W $$XMLHDR^XOBVLIB                                        <?xml
 version="1.0" encoding="utf-8" ?> 
VARIABLES: $$XMLHDR()                   TYPE: Output
 VARIABLES DESCRIPTION:   Output is the current XML header.  
COMPONENT/ENTRY POINT: $$CHARCHK(STR)
 COMPONENT DESCRIPTION:   Performs character resolution to replace XML
 character limits with XML entities.  
  
 Example: 
  
 DEV>W $$CHARCHK^XOBVLIB("This is an example of what call <charchk> does.") 
  
 This is an example of what call &lt;charchk&gt; does.  
VARIABLES: STR                          TYPE: Input
 VARIABLES DESCRIPTION:   
  Input: 
    STR  - string of characters to input 
VARIABLES: $$CHARCHK(STR)               TYPE: Output
 VARIABLES DESCRIPTION:   Output string of characters with XML entities
 replacing character limits.  
COMPONENT/ENTRY POINT: $$STOP()
 COMPONENT DESCRIPTION:   Used by the application to determine if processing
 should stop. Below are the development steps an application would use: 
  
 RPC Time Out Process 
 ====================
  
 Step    Where         Description 
 ====    =====         ===========
 1       Client        Set time out property at 
                       RpcRequest.setRpcClientTimeOut(int) 
                                                            
                       [int :: number of seconds] 
  
 2       Server        Periodically check if timed out or 
                       system needs for process to stop by 
                       calling $$STOP^XOBVLIB() 
  
                       [returns ;: 1 - stop processing 
                       0 - continue processing] 
  
 3       Client        Catch RpcTimeOutFaultException 
                       [Related DIALOG Entry :: 182007] 
VARIABLES:  
VARIABLES: $$STOP()                     TYPE: Output
 VARIABLES DESCRIPTION:   Indicator to stop processing (value = 1) or continue
 processing (value = 0).  
COMPONENT/ENTRY POINT: $$GETTO()
 COMPONENT DESCRIPTION:   Get the current timeout value (default = 300
 seconds).  
VARIABLES: $$GETTO()                    TYPE: Output
 VARIABLES DESCRIPTION:   Timeout value if it exists (in seconds) or default of
 300 seconds.  
COMPONENT/ENTRY POINT: $$SETTO(TO)
 COMPONENT DESCRIPTION:   Used to reset the RPC timeout value.  Will override
 the current timeout setting received from the client via
 RpcRequest.setRpcClientTimeout(int) or the default.  
  
 Note:  In processing, the new timeout value will take effect the next time
 $$STOP^XOBVLIB() is called. 
VARIABLES: TO                           TYPE: Input
 VARIABLES DESCRIPTION:   TO is the RPC timeout value in seconds.  
VARIABLES: $$SETTO(TO)                  TYPE: Output
 VARIABLES DESCRIPTION:   Function sets the RPC timeout value (in seconds) and
 returns a 1 to indicate value successfully reset or 0 if not successful.  

NUMBER: 4092                            IA #: 4092
  DATE CREATED: APR 29, 2003            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FBCSL01
  NAME: COREFLS INTERFACE UPDATES       ID: FBCSL01
 GENERAL DESCRIPTION:   CSL will need to call several Fee Basis APIs for the
 processing of authorization and payment documents and records.  Depending on
 the HL7 message event, the respective API will be invoked by the subscribing
 package (CSL) after receiving and processing the HL7 message exported to VistA
 by CoreFLS.  
  STATUS: Retired
COMPONENT/ENTRY POINT: $$POUPD(CSLMID)
 COMPONENT DESCRIPTION:   Logic is an extrinsic function with a single argument
 in the formal parameter list, which is a scalar variable.  The returned
 argument represents whether or not processing was successful.  
  
 The function is invoked by the subscribing package after receipt and
 processing of the PO Update message exported by CoreFLS.  The subscribing
 package shall store CoreFLS PO update results at ^XTMP(CSLMID) where CSLMID is
 equal to the name-spaced routine of the subscribing package and the numeric
 VistA HL7 messag ID separated by a semi-colon (e.g., "CSLrtname;nnnnnnn"). 
 The function shall be invoked by the SET or WRITE command as: 
 $$POUPD^FBCSL01(CSLMID).  
VARIABLES: CSLMID                       TYPE: Input
 VARIABLES DESCRIPTION:   A scalar variable that is equal to the name-spaced
 routine of the subscribing package and the numeric VistA HL7 message ID
 (assigned to the exported messasge) separated by a semi-colon.  example: 
 CSLMID = "CSLFBnn;123456789" 
  
 The structure of the temporary global array shall be built as: 
 ^XTMP(CSLMID,0)=PurgeDate^CreateDate^descriptive message 
  
 where purge date shall be greater than 2 days but not more than 7 days.  
   
 ^XTMP(CSLMID, field_subscipt) = data  
  
 The second subscript represented, as 'field_subscript' are literal values.  
 Data will be stored at the second subscript of the array.  The literal value
 defined at the second subscript will represent the data value stored at that
 node.  The second subscript literal values are listed as follows: 
         EVENT_CODE 
         VETERAN_NAME 
         VETERAN_SSN 
         VETERAN_ICN 
         AUTHORIZATION_ID 
         PO_NUMBER 
         PO_STATUS 
         TREATMENT_FROM_DATE 
         TREATMENT_TO_DATE 
         ESTIMATED_AMOUNT 
         ERROR_DESCRIPTION   
VARIABLES: $$POUPD                      TYPE: Output
 VARIABLES DESCRIPTION:   1 == the transaction was processed successfully 
 0^error text  == the transaction received an exception and did not update
 VistA.  
COMPONENT/ENTRY POINT: $$GLUPD(CSLMID)
 COMPONENT DESCRIPTION:   Logic is an extrinsic function with a single argument
 in the formal parameter list, which is a scalar variable.  The returned
 argument represents whether or not processing was successful.  
  
 The function shall be invoked by the subscribing package after receipt and 
 processing of the General Ledger(GL) Journal Entry(JE) Update message exported 
 by CoreFLS.  The subscribing package shall place CoreFLS GL JE update results 
 at ^XTMP(CSLMID) where CSLMID is equal to the name-spaced routine of the 
 subscribing package and the numeric VistA HL7 message ID separated by a 
 semi-colon (e.g., "CSLrtname;nnnnnnn"). The function shall be invoked by the 
 SET or WRITE command as: $$GLUPD^FBCSL01(CSLMID).  
VARIABLES: CSLMID                       TYPE: Input
 VARIABLES DESCRIPTION:   A scalar variable that is equal to the name-spaced
 routine of the subscribing package and the numeric VistA HL7 message ID
 (assigned to the exported message) separated by a semi-colon.  example: CSLMID
 = "CSLFBnn;123456789" 
  
 The structure of the temporary global array shall be built as: 
 ^XTMP(CSLMID,0)=PurgeDate^CreateDate^descriptive message 
  
 where Purge Date shall be greater than 2 days but not more than 7 days.  
  
 ^XTMP(CSLMID, field_subscipt) = data 
  
 The second subscript represented, as 'field_subscript' are literal values.  
 Data will be stored at the second subscript of the array.  The literal value 
 defined at the second subscript will represent the data value stored at that 
 node.  The second subscript literal values are listed as follows: 
        EVENT_CODE 
        VETERAN_NAME 
        VETERAN_SSN 
        VETERAN_ICN 
        AUTHORIZATION_ID 
        JE_NAME 
        JE_STATUS 
        TREATMENT_FROM_DATE 
        TREATMENT_TO_DATE 
        ESTIMATED_AMOUNT 
        ERROR_DESCRIPTION 
VARIABLES: $$GLUPD                      TYPE: Output
 VARIABLES DESCRIPTION:   1 == the transaction was processed successfully 
 0^error text  == the transaction received an exception and did not update 
 VistA.  
COMPONENT/ENTRY POINT: $$APUPD(CSLMID)
 COMPONENT DESCRIPTION:   Logic is an extrinsic function with a single argument
 in the formal parameter list, which is a scalar variable.  The returned
 argument represents whether or not processing was successful.  
  
 The function shall be invoked by the subscribing package after receipt and 
 processing of the the Invoice Creation Update message exported by CoreFLS.  
 The subscribing package shall place Invoice Creation results at ^XTMP(CSLMID) 
 where CSLMID is equal to the name-spaced routine of the subscribing package
 and the numeric VistA HL7 message ID separated by a semi-colon (e.g., 
 "CSLrtname;nnnnnnn"). The function shall be invoked by the SET or WRITE
 command as: $$APUPD^FBCSL01(CSLMID).  
VARIABLES: CSLMID                       TYPE: Input
 VARIABLES DESCRIPTION:   A scalar variable that is equal to the name-spaced
 routine of the subscribing package and the numeric VistA HL7 message ID
 (assigned to the exported message) separated by a semi-colon.  example: CSLMID
 = "CSLFBnn;123456789" 
  
 The structure of the temporary global array shall be built as: 
 ^XTMP(CSLMID,0)=PurgeDate^CreateDate^descriptive message 
  
 where purge date shall be greater than 30 days but not more than 40 days.  
       
 ^XTMP(CSLMID, field_subscipt) = data 
  
 The second subscript represented as 'field_subscript' are literal values. 
 Data will be stored at the second subscript of the array.  The literal value 
 defined at the second subscript will represent the data value stored at that 
 node.  The second subscript literal values are listed as follows: 
        EVENT_CODE 
        VETERAN_NAME 
        VETERAN_SSN 
        VETERAN_ICN     
        BATCH_ID 
        INVOICE_NUMBER 
        INVOICE_AMOUNT 
        INVOICE_STATUS 
        HOLD_REASON 
        HOLD_STATUS 
        ERROR_DESCRIPTION 
VARIABLES: $$APUPD                      TYPE: Output
 VARIABLES DESCRIPTION:   1 == the transaction was processed successfully 
 0^error text  == the transaction received an exception and did not update
 VistA.  
COMPONENT/ENTRY POINT: $$CONF(CSLMID)
 COMPONENT DESCRIPTION:   Logic is an extrinsic function with a single argument
 in the formal parameter list, which is a scalar variable.  The returned
 argument represents whether or not processing was successful.  
  
 The function shall be invoked by the subscribing package after receipt and 
 processing of the the payment confirmation/cancellation message exported by 
 CoreFLS.  The subscribing package shall place Confirmation/Cancellation 
 results at ^XTMP(CSLMID) where CSLMID is equal to the name-spaced routine of 
 the subscribing package and the numeric VistA HL7 message ID separated by a 
 semi-colon (e.g.,"CSLrtname;nnnnnnn"). The function shall be invoked by the 
 SET or WRITE command as: $$CONF^FBCSL01(CSLMID).  
VARIABLES: CSLMID                       TYPE: Input
 VARIABLES DESCRIPTION:   A scalar variable that is equal to the name-spaced
 routine of the subscribing package and the numeric VistA HL7 message ID
 (assigned to the exported message) separated by a semi-colon.  example: 
 CSLMID = "CSLFBnn;123456789" 
  
 The structure of the temporary global array shall be built as: 
  ^XTMP(CSLMID,0)=PurgeDate^CreateDate^descriptive text 
  
 where Purge Date shall be greater than 30 days but not more than 40 days.  
                       
 ^XTMP(CSLMID, field_subscipt) = data  
  
 The second subscript represented as 'field_subscript' are literal values. 
 Data will be stored at the second subscript of the array.  The literal value 
 defined at the second subscript will represent the data value stored at that 
 node.  The second subscript literal values are listed as follows: 
        FEE_PROGRAM 
        ACTIVITY_CODE 
        INVOICE_STATUS 
        INVOICE_NO 
        LINE_NUM 
        LINE_AMT 
        CHECK_NO 
        CHECK_DATE 
        DISBURSED_AMT 
        INTEREST_AMT 
        CANCEL_DT 
        REASON_CODE 
        CANCEL_CODE 
        VETERAN_NAME 
        VETERAN_ID 
        VETERAN_ICN 
VARIABLES: $$CONF                       TYPE: Output
 VARIABLES DESCRIPTION:   1 == the transaction was processed successfully 
 0^error text  == the transaction received an exception and did not update
 VistA 
SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY
 SUBSCRIBING DETAILS:   Fee Basis shall exchange data with the CoreFLS Oracle
 database through an M Service Library.  The M Service Library is a collection
 of M routines consisting of several APIs.  The collection of routines exists
 in VistA as the COMMUNICATIONS SERVICE LIBRARY (CSL) package.  

NUMBER: 4093                            IA #: 4093
  FILE NUMBER: 392.31                   GLOBAL ROOT: DD(392.31
  DATE CREATED: APR 24, 2003            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Setting ID node (file #392.31)
  ID: DD(392.31
GLOBAL REFERENCE: DD(392.31,0,'ID','Z')
 GENERAL DESCRIPTION:   Beneficiary Travel would like to add a hard-set routine
 call in the "ID" node of the ^DD file of #392.31.  This hard-set routine call
 will display phone, fax, and address information needed to distinguish between
 like vendors. The variable Y will be used as the input variable and  the 
 EN^DDIOL call will be used to output the information.  Hard-set in the ^DD 
 will look like the following: 
  
 ^DD(392.31,0,"ID","Z") = G START^DGBTID 
  
 With the letter 'I' being placed in the 2nd piece of the File Header: 
  
 ^DGBT(392.31,0) = LOCAL VENDOR^392.31OI^12^11 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL

NUMBER: 4094                            IA #: 4094
  FILE NUMBER: 8925.1                   GLOBAL ROOT: TIU(8925.1
  DATE CREATED: APR 25, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Advanced Directives Query       ID: TIU(8925.1
GLOBAL REFERENCE: TIU(8925.1,'B',DOCDEF,
 GLOBAL DESCRIPTION:   The purpose of this index read is to loop through the
 TIU DOCUMENT DEFINITION file screening on ADVANCE DIRECTIVE.  
GLOBAL REFERENCE: TIU(8925.1,
FIELD NUMBER: .04                       FIELD NAME: TYPE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The purpose of this read is to enable screening by
 document class (DC).  
GLOBAL REFERENCE: TIU(8925.1,10,'B',SUB
 GLOBAL DESCRIPTION:   The purpose of this index read to screen for ADVANCE
 DIRECTIVE titles.  
 GENERAL DESCRIPTION:   We have been tasked to report the total 30-day count of
 advanced directives at sites and to compare that count to the Imaging packages 
 "scanned" Advanced directives.  This report is to be used by Vista 
 administrators as a productivity tool (metric) and has been requested by Laura
 Miller, the VHA's Deputy under-secretary of Health. I have a server job that
 runs on the 15th of every month that gathers a comprehensive set of Vista
 activity values that includes Images captured and displayed, software version
 numbers, patient counts, provider counts, image types. My plan  is to use this
 server methodology to deliver the advanced directives counts to our local
 account that rolls up this data into a viewable database. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

NUMBER: 4095                            IA #: 4095
  FILE NUMBER: 8925.6                   GLOBAL ROOT: TIU(8925.6
  DATE CREATED: APR 25, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Advanced Directives Query       ID: TIU(8925.6
GLOBAL REFERENCE: TIU(8925.6,'B',STATU,
 GLOBAL DESCRIPTION:   The purpose of this index read is to aggregate the
 status references for "AMENDED" and "COMPLETED" documents. 
 GENERAL DESCRIPTION:   We have been tasked to report the total 30-day count of
 advanced directives at sites and to compare that count to the Imaging packages 
 "scanned" Advanced directives.  This report is to be used by Vista 
 administrators as a productivity tool (metric) and has been requested by Laura
 Miller, the VHA's Deputy under-secretary of Health. I have a server job that
 runs on the 15th of every month that gathers a comprehensive set of Vista
 activity values that includes Images captured and displayed, software version
 numbers, patient counts, provider counts, image types. My plan  is to use this
 server methodology to deliver the advanced directives counts to our local
 account that rolls up this data into a viewable database. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

NUMBER: 4097                            IA #: 4097
  FILE NUMBER: 801.41                   GLOBAL ROOT: PXRMD(801.41,
  DATE CREATED: MAY 05, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: CLINICAL REMINDER DIALOG EXCLUDE FROM PROGRESS NOTE
  ID: PXRMD(801.41,
GLOBAL REFERENCE: PXRMD(801.41,
FIELD NUMBER: 4                         FIELD NAME: TYPE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 51                        FIELD NAME: SUPPRESS CHECKBOX
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 23                        FIELD NAME: EXCLUDE FROM PROGRESS NOTE
  LOCATION: 2;3                         ACCESS: Direct Global Write & w/Fileman
 GENERAL DESCRIPTION:   Order entry request the ability to do a direct read on
 Reminder Dialog File, file number 801.41, fields' numbers four and 51. Order
 Entry also requests the ability to do a direct set to field number 23.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EXCLUDE FROM PROGRESS NOTE
KEYWORDS: PXRM SUPPRESS CHECKBOX
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4098                            IA #: 4098
  DATE CREATED: MAY 19, 2003
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSSPOIDT                     NAME: PSSPOIDT
  ORIGINAL NUMBER: 4098                 ID: PSSPOIDT
 GENERAL DESCRIPTION:   Allow CPRS to use EN1^PSSPOIDT during the
 post-installation of patch OR*3*176.  EN1^PSSPOIDT will update CPRS files to
 be in synch with Pharmacy files for the Herbal/OTC/Non-VA Meds project.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NON-VA MEDS
KEYWORDS: PSSPOIDT
COMPONENT/ENTRY POINT: EN1
VARIABLES: PSSTEST                      TYPE: Input
 VARIABLES DESCRIPTION:   PSSTEST is the internal entry number from file 50.7
 (Pharmacy Orderable Item.) 
VARIABLES: PSSCROSS                     TYPE: Input
 VARIABLES DESCRIPTION:   PSSCROSS is s flag used in processing flow.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   One time use for patch OR*3*176.  

NUMBER: 4099                            IA #: 4099
  FILE NUMBER: 50.7                     GLOBAL ROOT: PS(50.7,
  DATE CREATED: MAY 05, 2003
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: PHARMACY ORDERABLE ITEM FILE
  ORIGINAL NUMBER: 4098                 ID: PS(50.7,
GLOBAL REFERENCE: PS(50.7,
FIELD NUMBER: 8                         FIELD NAME: NON-VA MED
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Allow CPRS to use the Pharmacy Orderable Item file
 [^PS(50.7] during the post-installation of patch OR*3*176.  OR*3*176 post-init
 routine ORY176 loops through ^PS(50.7 for each call into EN1^PSSPOIDT to synch
 CPRS files with Pharmacy files for the Herbal/OTC/Non-VA Meds project.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: NON-VA MEDS
KEYWORDS: 50.7
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   One time use for patch OR*3*176.  

NUMBER: 4100                            IA #: 4100
  DATE CREATED: MAY 19, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XQALERT1                     NAME: XQALERT1
  ID: XQALERT1                          STATUS: Active
KEYWORDS: RESTORE
KEYWORDS: ALERT
KEYWORDS: XQALERT1
COMPONENT/ENTRY POINT: RESTORE
 COMPONENT DESCRIPTION:   Restore deleted alert.  
VARIABLES: XQAID                        TYPE: Input
 VARIABLES DESCRIPTION:   XQAID is the unique alert identifier.  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   DUZ is the internal entry number from file 200 (New
 Person) of the alert recipient.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4101                            IA #: 4101
  DATE CREATED: NOV 18, 2003            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: WVSITE                       NAME: WVSITE
  ID: WVSITE                            STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETPARAM(.RESULT,IEN)
 COMPONENT DESCRIPTION:   Return WH site parameters for the facility indicated. 
  
 Output: RESULT(0)=1st piece is 1 (for Success) or -1 (Failure) 
                   2nd piece is the reason for failure 
         RESULT(1)=1st piece is 1 (for Yes) or 0 (for No or Null) to UPDATE 
                   RESULTS/DX for an entry in the WV PROCEDURE file 
                   (#790.1).  
                   2nd piece is 1 (for Yes) or 0 (for No) to UPDATE 
                   TREATMENT NEEDS for an entry in WV PATIENT file (#790).  
  
  > D GETPARAM(.RESULT,IEN) ZW RESULT 
  > RESULT(0)=1^ 
  > RESULT(1)=1^1 
VARIABLES: .RESULT                      TYPE: Both
 VARIABLES DESCRIPTION:   Array name to return data in. Passed by reference.
 (Required) 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   INSTITUTION file (#4) IEN. (Required) 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4102                            IA #: 4102
  DATE CREATED: NOV 18, 2003            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: WVALERTS                     NAME: WVALERTS
  ID: WVALERTS                          STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RESULTS(.RESULT,IEN)
 COMPONENT DESCRIPTION:   Returns an array with a limited amount of data for
 the WV PROCEDURE FILE (#790.1) entry identified.  
  
  Output: 
  
  RESULT(0)=piece1^piece2^piece3^piece4^piece5^piece6^piece7^piece8^ 
            piece9^piece10 
  
  piece1 = WV PROCEDURE file (#790.1) entry number 
  piece2 = patient DFN 
  piece3 = 'Breast Ultrasound', 'Mammogram' or 'Pap Smear' 
  piece4 = Date of procedure (FileMan internal format) 
  piece5 = Radiology procedure name 
  piece6 = Primary radiology diagnosis 
  piece7 = One or more radiology modifiers separated by tildes (~) 
  piece8 = Lab package test date (external format) 
  piece9 = Lab accession number 
  piece10 = Lab specimen text 
  
 If the entry is not found, piece1 will contain '-1' and piece3 will contain an
 error message.  
  
 If the entry is a Pap Smear, then pieces 5 through 7 are null.  
  
 If the entry is a Mammogram or Breast Ultrasound, then pieces 8 through 10 are
 not returned.  
  
  Example of a Pap Smear: 
  
  D RESULTS(.RESULT,IEN) ZW RESULT 
  
  RESULT(0)=313^94^Pap Smear^3030131^^^^01/31/2003^CY 03 6^PAP SMEAR 
  
  
  Example of a Mammogram: 
  
  D RESULTS(.RESULT,IEN) ZW RESULT 
  
  RESULT(0)=314^94^Mammogram^3030321^MAMMOGRAM SCREENING^NORMAL^LEFT~RIGHT 
VARIABLES: .RESULT                      TYPE: Both
 VARIABLES DESCRIPTION:   Array name to return data in. (Required) 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of a WV PROCEDURE file
 (#790.1) entry. (Required) 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4103                            IA #: 4103
  DATE CREATED: NOV 18, 2003            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: WVRPCNO1                     NAME: WVRPCNO1
  ID: WVRPCNO1                          STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LETTER(.RESULT,IEN)
 COMPONENT DESCRIPTION:   Returns the letter text for the purpose of
 notification identified.  
  
  Output: RESULT(0)= Blank if the entry exists  <OR> 
                     -1^error message 
          RESULT(n)= Lines of letter text where 'n' is a sequential number 
  
  > D LETTER(.RESULT,IEN) ZW RESULT 
    RESULT(0)= 
    RESULT(1)=|NOWRAP| 
    RESULT(2)= 
    RESULT(3)=|CENTER("Women's Health Clinic")| 
    RESULT(4)= 
    RESULT(5)=|CENTER(" 123 Main Street")| 
    RESULT(6)= 
    RESULT(7)=|CENTER("CHICAGO, IL 60612")| 
    RESULT(n)=...  
VARIABLES: .RESULT                      TYPE: Both
 VARIABLES DESCRIPTION:   Array name to return data in. (Required) 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   WV NOTIFICATION PURPOSE file (#790.404) IEN.
 (Required) 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4104                            IA #: 4104
  DATE CREATED: NOV 18, 2003            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: WVRPCNO                      NAME: WVRPCNO
  ID: WVRPCNO                           STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: NEW(.RESULT,.NOTIFY)
 COMPONENT DESCRIPTION:   Used to update a procedure result, create a
 notification, print a notification letter and update a patient's treatment
 needs.  
  
 A notification letter for a patient may be printed based on the input 
 parameter values. No data is passed back to the calling routine.  
VARIABLES: RESULT                       TYPE: Input
 VARIABLES DESCRIPTION:   This is an array that identifies what WV PROCEDURE
 file (#790.1) entries will be updated and the result code to use. (Optional) 
  
  RESULT(n)=FILE 790.1 IEN^"A", "N" or "U" 
  
  where: n is a number greater than zero.  
  
  The first piece is the FILE 790.1 IEN.  
  
  The second piece is a one character code that identifies the diagnosis.  
  "A" stands for Abnormal, "N" stands for Normal and "U" stands for 
  Unsatisfactory.  
  
  
 Three fields are updated in the FILE 790.1 entry. 
  
 The codes of "A", "N" and "U" are converted to entries in the WV 
 RESULTS/DIAGNOSIS file (#790.31). "A" becomes "Abnormal". "N" becomes "No 
 Evidence of Malignancy". "U" becomes "Unsatisfactory for Dx". That FILE 790.31
 value is stored in the RESULTS/DIAGNOSIS field (#.05).  
  
 The STATUS field (#.14) is set to "c" (for Closed).  
  
 The PROCESSED Y/N? field (#.16) is set to 1 (for Yes).  
VARIABLES: NOTIF                        TYPE: Input
 VARIABLES DESCRIPTION:   This is an array that identifies the notification
 purposes to use to create entries in the WV NOTIFICATION file (#790.4).
 (Optional) 
  
 NOTIF(FILE 790.404 IEN,n)=FILE 790.1 IEN^Type^FILE 3.5 NAME^DFN 
  
 The first array subscript is a FILE 790.404 internal entry number (IEN).  
  
 The second subscript is a sequential number starting with 1.  
  
 The first piece of data in the node is the FILE 790.1 IEN which identifies the
 procedure performed.  
  
 The second piece is a one character code that identifies the type of 
 notification. "I" stands for In-person, "L" stands for Letter and "P" stands
 for Phone.  
  
 The third piece identifies the print device. It consists of the FILE 3.5 IEN,
 a semi-colon and the .01 value of the entry (e.g., 5;HPLASERJET).  
  
 The fourth piece is the patient IEN (i.e., DFN) from FILE 2.  
  
 If the first subscript value is a valid FILE 790.404 IEN, then a WV 
 NOTIFICATION file (#790.4) entry is created. This new entry has the following
 field values set: 
  (.01) PATIENT - is set to the DFN of the patient.  
  (.02) DATE NOTIFICATION OPENED - is set to today's date.  
  (.03) TYPE OF NOTIFICATION - is set to a WV NOTIFICATION TYPE file 
        (#790.403) value. The one character code in the second piece is 
        converted to a FILE 790.403 value. "I" becomes "CONVERSATION WITH 
        PATIENT". "L" becomes "LETTER, FIRST". "P" becomes "CONTACT PHN".  
  (.04) PURPOSE OF NOTIFICATION - is set with the value of the first 
        subscript (i.e., FILE 790.404 value).  
  (.05) OUTCOME - is set to "Letter Sent" if the third piece contains a 
        device. If no device is identified, it is set to null. Also, if the 
        second piece is "I" (i.e., In-person) or "P" (i.e., Phone), this 
        field is set to null.  
  (.06) ACCESSION# - is set to a FILE 790.1 IEN.  
  (.07) FACILITY - is set to the user's facility value (i.e., DUZ(2)).  
  (.08) DATE NOTIFICATION CLOSED - is set to today's date.  
  (.11) PRINT DATE - is set to today's date if a device is selected.  
  (.13) COMPLETE BY (DATE) - is set to today's date.  
  (.14) STATUS - is set to "c" (for Closed).  
  
  
 The Purpose of Notification value (the first subscript) is a pointer to FILE
 790.404. The following fields in that FILE 790.404 entry are checked for a
 value: 
  (.07) BR TX NEED 
  (.08) BR TX DUE DATE 
  (.09) CX TX NEED 
  (.1)  CX TX DUE DATE 
  
 If any of these four fields in this entry have a value, those values are used
 to update the patient's entry in the WV PATIENT file (#790). 
  For example: 
  The BR TX NEED value is used in the BR TX NEED field (#.18).  
  The CX TX NEED value is used in the CX TX NEED field (#.11). 
  The day, month or year offset in the BR TX DUE DATE value is added to 
  the procedure or current date to create a future date that is used in the 
  BR TX NEED DUE DATE (#.19).  
  The day, month or year offset in the CX TX DUE DATE value is added to 
  the procedure or current date to create a future date that is used in the 
  CX TX NEED DUE DATE (#.12).  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4105                            IA #: 4105
  DATE CREATED: NOV 18, 2003            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: WVRPCPR                      NAME: WVRPCPR
  ID: WVRPCPR                           STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LATEST(.RESULT,DFN,TYPE,DATES,MAX,DX)
 COMPONENT DESCRIPTION:   Returns a list of entries for Pap Smear, Mammogram or
 Breast Ultrasound in reverse chronological order for the search criteria
 identified in the input parameters.  
  
  Output: RESULT(0)=# of matches 
  RESULT(n)=IEN^DFN^DATE^TYPE^DX CATEGORY^DX Result^RAD/LAB link^STATUS 
  
  where   n = A sequential number starting with 1 
        IEN = FILE 790.1 internal entry number 
        DFN = FILE 2 internal entry number 
        DATE = Procedure date in FileMan format 
        TYPE = Procedure name (from FILE 790.2) 
        DX Category = 'Normal', 'Abnormal' or 'Pending' 
        DX Result = FILE 790.31, Field .01 
        RAD/LAB LINK = 0 stands for no link to rad/lab package 
                       1 stands for link to rad/lab package 
        STATUS = FILE 790.1 entry status. 'OPEN' or 'CLOSED' 
  
 If no matches were found, RESULT(0)=-1^error message.  
  
  Example: 
  
  D LATEST(.RESULT,94,"M","3030101^3031231",10,"*") ZW RESULT 
  RESULT(0)=1^ 
  RESULT(1)=314^94^3030321^MAMMOGRAM SCREENING^Normal^Negative^1^OPEN 
VARIABLES: .RESULT                      TYPE: Both
 VARIABLES DESCRIPTION:   Array name for return values. (Required) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN. (Required) 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   A set of codes where "P" stands for Pap Smear, "M"
 for Mammogram or "U" for Breast Ultrasound. (Required) 
VARIABLES: DATES                        TYPE: Input
 VARIABLES DESCRIPTION:   A date range in FileMan internal format separated by
 an uparrow (e.g., 3020101^3021231). (Optional).  
  
 If this value is not defined, the API will use the past three years as the
 date range.  
VARIABLES: MAX                          TYPE: Input
 VARIABLES DESCRIPTION:   The maximum number of entries to return. (Optional) 
  
 The default value is 10.  
VARIABLES: DX                           TYPE: Input
 VARIABLES DESCRIPTION:   A set of codes that identify a category of results
 where "N" stands for Normal, "A" stands for Abnormal, "P" stands for Pending
 and "*" stands for everything. (Optional) 
  
 The default is "*". It returns entries that are marked as "Unsatisfactory for
 DX" as well as Normal, Abnormal and Pending.  
  
 "P" returns entries that are marked as Unsatisfactory for DX as well as 
 Pending.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4106                            IA #: 4106
  DATE CREATED: OCT 06, 2003            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: WVALERTF                     NAME: WVALERTF
  ID: WVALERTF                          STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RESULTS(.RESULT,IEN)
 COMPONENT DESCRIPTION:   Returns any report text for a pap smear, mammogram or
 breast ultrasound for the WV PROCEDURE file (#790.1) entry identified.  
  
  Output: 
  ^TMP("WV RPT",$J,n,0) = report text 
  where n is a sequential number starting with 1.  
  
 If the entry is not found, the first node of the global array is returned with
 a -1 in the first piece, piece 2 will be null and piece 3 will contain an
 error message: 
  
  ^TMP("WV RPT",557902502,1,0) = -1^^Entry not found.  
  
  
  Example of report text found: 
  
  S IEN=315 
  D RESULTS(.RESULT,IEN) ZW RESULT 
  RESULT=^TMP("WV RPT",557902502) 
  D ^%G 
  ^TMP("WV RPT",557902502,1,0) =          DAY-CASE #: 032103-1515 
  ^TMP("WV RPT",557902502,2,0) =      EXAM DATE/TIME: MAR 21, 2003@13:30 
  ^TMP("WV RPT",557902502,3,0) = VERIFYING PHYSICIAN: TAYLOR,FRANK 
  ^TMP("WV RPT",557902502,4,0) =           PROCEDURE: MAMMOGRAM SCREENING 
  ...
  ...
VARIABLES: RESULT                       TYPE: Both
 VARIABLES DESCRIPTION:   Array name that will identify the global reference
 containing the report text (Required).  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the FILE 790.1 entry to
 return data on (Required).  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4107                            IA #: 4107
  FILE NUMBER: 790.403                  GLOBAL ROOT: WV(790.403
  DATE CREATED: MAY 06, 2003            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            NAME: DBIA4107
  ID: WV(790.403                        STATUS: Pending
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4108                            IA #: 4108
  FILE NUMBER: 790.404                  GLOBAL ROOT: WV(790.404
  DATE CREATED: JUL 02, 2004            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4108                        ID: WV(790.404
GLOBAL REFERENCE: WV(790.404,
FIELD NUMBER: .01                       FIELD NAME: NOTIFICATION PURPOSE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is a free text field that contains the name of
 each Notification Purpose.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: WH
KEYWORDS: Direct read of file 790.404
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clinical Reminders is requesting the ability to a
 direct read on file 790.404 piece one. We are also requesting the ability to
 be able to point to this file for use in Reminder Dialog elements.  

NUMBER: 4109                            IA #: 4109
  DATE CREATED: MAY 15, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: TIULG                        NAME: ACTIVATE DOCUMENT DEFINITIONS
  ID: TIULG
 GENERAL DESCRIPTION:   In some patches, TIU exports new Document Definitions,
 and a companion USR patch exports a new User Class and new Business Rules on
 the new Document Definitions and User Class.  USR would like to be able to 
 activate these new Document Definitions AFTER the Business Rules have been 
 installed successfully.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DOCUMENT DEFINITIONS
KEYWORDS: ACTIVATE
COMPONENT/ENTRY POINT: ACTIVATE
VARIABLES: TIUARRAY                     TYPE: Input
 VARIABLES DESCRIPTION:   Array of Document Definitions to activate 
VARIABLES: SUCCESS                      TYPE: Output
 VARIABLES DESCRIPTION:   Success of attempt to activate Document Definition 
SUBSCRIBING PACKAGE: AUTHORIZATION/SUBSCRIPTION
  ISC: Salt Lake City

NUMBER: 4110                            IA #: 4110
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123,
  DATE CREATED: JUL 31, 2003
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Imaging Consults                ID: GMR(123,
GLOBAL REFERENCE: GMR(123,
FIELD NUMBER: .02                       FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Patient name, pointer to the Patient file (#2).  
FIELD NUMBER: 1                         FIELD NAME: TO SERVICE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The service responsible for completion of the
 consult/request.  
FIELD NUMBER: 3                         FIELD NAME: DATE OF REQUEST
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The date of the request for the consult.  
FIELD NUMBER: 5                         FIELD NAME: URGENCY
  LOCATION: 0;9                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The urgency for the consult or request.  
FIELD NUMBER: 8                         FIELD NAME: CPRS STATUS
  LOCATION: 0;12                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The current CPRS status of the consult or request.  
FIELD NUMBER: 4                         FIELD NAME: PROCEDURE/REQUEST TYPE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The procedure requested via CPRS.  
FIELD NUMBER: 10                        FIELD NAME: SENDING PROVIDER
  LOCATION: 0;14                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The provider who originated the order.  
GLOBAL REFERENCE: GMR(123,D0,50,
FIELD NUMBER: .01                       FIELD NAME: ASSOCIATED RESULTS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The result to be associated with a consult.  
 GLOBAL DESCRIPTION:   This global allows one or more results to be associated
 with a consult.  
GLOBAL REFERENCE: GMR(123,D0,40,
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME OF ACTION ENTRY
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Acutal date & time the activity tracking update was added
 to the consult or request.  
FIELD NUMBER: 6                         FIELD NAME: FORWARDED FROM
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The hospital service that is forwarding the consult.  
 GLOBAL DESCRIPTION:   Global node has the history of the processing actions
 for the consult.  
 GENERAL DESCRIPTION:   Imaging reads fields from the REQUEST/CONSULTATION file
 to gather information regarding the consult or procedure being performed to
 produce a patient worklist for modalities. The worklist is displayed on the 
 modality for the technician or physician to select the patient and attach 
 images to the consult\procedure.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
 SUBSCRIBING DETAILS:   CP is only allowed access to the ASSOCIATED RESULTS
 (#50) field and all associated sub-fields with read w/FileMan access.  
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  DATE ACTIVATED: MAY 14, 2008

NUMBER: 4111                            IA #: 4111
  DATE CREATED: MAY 29, 2003            CUSTODIAL PACKAGE: SURGERY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: SRSCLM                       NAME: Calls to Routine SRSCLM
  ID: SRSCLM
 GENERAL DESCRIPTION:   This DBIA documents calls to the routine SRSCLM.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MSG
 COMPONENT DESCRIPTION:   The Communication Service Library (CSL) is given
 permission to call SRSCLM to pass information about surgery cases that the
 Supply Processing and Distribution (SPD) was unable to process due to problems
 with the HL7 transaction transmitted to SPD.  
VARIABLES: CSLCASE                      TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the case in the Surgery file #130.  
VARIABLES: CSLTEXT                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the reason behind CSL/SPD rejecting the
 Surgery case information.  
SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  ISC: Washington/Silver Spring

NUMBER: 4112                            IA #: 4112
  FILE NUMBER: 78.3                     GLOBAL ROOT: RA(78.3,
  DATE CREATED: MAY 29, 2003
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Look Up Radiology Diagnostic Code Number from Name
  ID: RA(78.3,
GLOBAL REFERENCE: RA(78.3,
FIELD NUMBER: .01                       FIELD NAME: DIAGNOSTIC CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This value is referenced via the "B" index and then
 verified against the first piece of the 0 node to find the number (IEN) 
 associated with a diagnostic code name.  
 GENERAL DESCRIPTION:   This agreement allows the VistA Imaging Package to
 reference the "B" index and 0 subscript of the Radiology DIAGNOSTIC CODE File
 (#78.3) in order to obtain a Diagnostic Code number given a Diagnostic Code
 name.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   VistA Imaging uses routine MAG7RSR to look up a
 Diagnosis Code number given a Diagnosis Code name.  This enables Imaging to
 populate the required code number component of the diagnosis code triplet that
 is sent in DICOM messages.  

NUMBER: 4113                            IA #: 4113
  DATE CREATED: JUN 11, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXRMSXRM                     NAME: PXRM INDEX ERROR MESSAGE
  ID: PXRMSXRM                          STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: PXRM INDEX
KEYWORDS: PXRM INDEX ERROR MESSAGE
COMPONENT/ENTRY POINT: ADDERROR
 COMPONENT DESCRIPTION:   This API will build a list of error found in a
 particular global while the Clinical Reminder Index ^PXRMINDX is being built.  
VARIABLES: GLOBAL                       TYPE: Input
 VARIABLES DESCRIPTION:   Global is the global root for the file being indexed. 
 
VARIABLES: IDEN                         TYPE: Input
 VARIABLES DESCRIPTION:   IDEN is a string which identifies the record being
 index.  
VARIABLES: NERROR                       TYPE: Input
 VARIABLES DESCRIPTION:   NERROR is an error number counter.  
COMPONENT/ENTRY POINT: DETIME
 COMPONENT DESCRIPTION:   This API will write out the elapsed time that it took
 to index a global.  
VARIABLES: START                        TYPE: Input
 VARIABLES DESCRIPTION:   START is the time that the indexing was started.  
VARIABLES: END                          TYPE: Input
 VARIABLES DESCRIPTION:   END is the time that the indexing finished.  
COMPONENT/ENTRY POINT: COMMSG
 COMPONENT DESCRIPTION:   This API will send a MailMan message providing a
 notification that the indexing of a global is complete. 
VARIABLES: GLOBAL                       TYPE: Input
 VARIABLES DESCRIPTION:   Global is the Global root.  
VARIABLES: START                        TYPE: Input
 VARIABLES DESCRIPTION:   START is the time that the indexing was started.  
VARIABLES: END                          TYPE: Input
 VARIABLES DESCRIPTION:   END is the time that the indexing finished.  
VARIABLES: NE                           TYPE: Input
 VARIABLES DESCRIPTION:   NE is the number of entries that were created in the
 Clinical Reminder Index.  
VARIABLES: NERROR                       TYPE: Input
 VARIABLES DESCRIPTION:   NERROR is the number of errors that were found while
 indexing the global.  
COMPONENT/ENTRY POINT: ERRMSG
 COMPONENT DESCRIPTION:   This API will send a message if errors were found
 while Clinical Reminders were indexing the global.  
VARIABLES: NERROR                       TYPE: Input
 VARIABLES DESCRIPTION:   NERROR is the number of errors that were found while
 indexing the global.  
VARIABLES: Global                       TYPE: Input
 VARIABLES DESCRIPTION:   Global is the global root for the file being indexed. 
 
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany
SUBSCRIBING PACKAGE: PROBLEM LIST       ISC: Salt Lake City
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  ISC: Hines
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  ISC: Hines

NUMBER: 4114                            IA #: 4114
  GLOBAL ROOT: PXRMINDX(                DATE CREATED: JUL 31, 2003
  CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DIRECT SET AND KILL OF CLINICAL REMINDERS INDEX
  ID: PXRMINDX(
GLOBAL REFERENCE: PXRMINDX(55,
 GLOBAL DESCRIPTION:   Inpatient pharmacy has the right to do a direct set and
 a direct kill on all entries with the first subscript number 55.  
GLOBAL REFERENCE: PXRMINDX(63,
 GLOBAL DESCRIPTION:   Lab Services has the right to do a direct set and a
 direct kill on all entries with the first subscript number 63.  
GLOBAL REFERENCE: PXRMINDX(52,
 GLOBAL DESCRIPTION:   Outpatient pharmacy has the right to do a direct set and
 a direct kill on all entries with the first subscript number 52.  
GLOBAL REFERENCE: PXRMINDX(100,
 GLOBAL DESCRIPTION:   Order Entry has the right to do a direct set and a
 direct kill on all entries with the first subscript number 100.  
GLOBAL REFERENCE: PXRMINDX(601.2,
 GLOBAL DESCRIPTION:   Mental Health has the right to do a direct set and a
 direct kill on all entries with the first subscript number 601.2.  
GLOBAL REFERENCE: PXRMINDX(9000011,
 GLOBAL DESCRIPTION:   Problem List has the right to do a direct set and a
 direct kill on all entries with the first subscript number 9000011.  
GLOBAL REFERENCE: PXRMINDX(70,
 GLOBAL DESCRIPTION:   Radiology has the right to do a direct set and a direct
 kill on all entries with the first subscript number 70.  
GLOBAL REFERENCE: PXRMINDX(45,
 GLOBAL DESCRIPTION:   Registration has the right to do a direct set and a
 direct kill on all entries with the first subscript number 45.  
GLOBAL REFERENCE: PXRMINDX(120.5,
 GLOBAL DESCRIPTION:   Vitals has the right to do a direct set and a direct
 kill on all entries with the first subscript number 120.5.  
GLOBAL REFERENCE: PXRMINDX(9000010.18,
 GLOBAL DESCRIPTION:   PCE has the right to do a direct set and a direct kill
 on all entries with the first subscript number 9000010.18 
GLOBAL REFERENCE: PXRMINDX(9000010.13,
 GLOBAL DESCRIPTION:   PCE has the right to do a direct set and a direct kill
 on all entries with the first subscript number 9000010.13.  
GLOBAL REFERENCE: PXRMINDX(9000010.23,
 GLOBAL DESCRIPTION:   PCE has the right to do a direct set and a direct kill
 on all entries with the first subscript number 9000010.23.  
GLOBAL REFERENCE: PXRMINDX(9000010.11,
 GLOBAL DESCRIPTION:   PCE has the right to do a direct set and a direct kill
 on all entries with the first subscript number 9000010.11.  
GLOBAL REFERENCE: PXRMINDX(9000010.16,
 GLOBAL DESCRIPTION:   PCE has the right to do a direct set and a direct kill
 on all entries with the first subscript number 9000010.16.  
GLOBAL REFERENCE: PXRMINDX(9000010.07,
 GLOBAL DESCRIPTION:   PCE has the right to do a direct set and a direct kill
 on all entries with the first subscript number 9000010.07.  
GLOBAL REFERENCE: PXRMINDX(9000010.12,
 GLOBAL DESCRIPTION:   PCE has the right to do a direct set and a direct kill
 on all entries with the first subscript number 9000010.12.  
GLOBAL REFERENCE: PXRMINDX(601.84,
 GLOBAL DESCRIPTION:   Mental Health has the right to do a direct set and a
 direct kill on all entries with the first subscript number 601.84.  
GLOBAL REFERENCE: PXRMINDX(9000010.707,
 GLOBAL DESCRIPTION:   PCE has the right to do a direct set and a direct kill
 on all entries with the first subscript number 9000010.707.  
 GENERAL DESCRIPTION:   This DBIA will allow the subcribing packages to do a
 direct set and a direct kill to the Clinical Reminders Index.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM INDEX
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany
SUBSCRIBING PACKAGE: PROBLEM LIST       ISC: Salt Lake City
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  ISC: Hines
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  ISC: Albany
SUBSCRIBING PACKAGE: MENTAL HEALTH      ISC: Dallas
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  ISC: Hines
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
 SUBSCRIBING DETAILS:   added 2/22/2010 
  DATE ACTIVATED: SEP 19, 2016

NUMBER: 4115                            IA #: 4115
  DATE CREATED: MAY 29, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: IBCNSU3                      NAME: DBIA4115
  ID: IBCNSU3
 GENERAL DESCRIPTION:   The OUTPATIENT PHARMACY package will call the entry
 point PTCOV in the routine IBCNSU3 to allow Outpatient Pharmacy to provide a
 report of patients who had prescription insurance coverage on the fill date of 
 prescriptions which had copay charges back-billed by patch PSO*7*123.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2005
COMPONENT/ENTRY POINT: PTCOV(PSODFN,PSOFDT,"PHARMACY")
VARIABLES: PSODFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number in file #2 
VARIABLES: PSOFDT                       TYPE: Input
 VARIABLES DESCRIPTION:   Fill date or refill date from file 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 4116                            IA #: 4116
  DATE CREATED: JUN 04, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DPTNAME
  NAME: NCEDIT DPTNAME                  ID: DPTNAME
 GENERAL DESCRIPTION:   This routine was introduced with Patient Name
 Standardization.  MPI allows editing of the patient name.  To be consistent
 with Registration options they want to display and allow editing of the
 individual name component values as well.  
  STATUS: Active
COMPONENT/ENTRY POINT: NCEDIT
 COMPONENT DESCRIPTION:   This entry point allows the editing of the components
 of the patient's name. Returning the formatted name.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN - Internal entry number of patient in the Patient
 file (#2).  
VARIABLES: DGHDR                        TYPE: Input
 VARIABLES DESCRIPTION:   Set to 1 to write components header (optional).  
VARIABLES: DG20NAME                     TYPE: Both
 VARIABLES DESCRIPTION:   Input - Array to store name components (optional) 
 Output - components if the user specifies the array, otherwise null.  
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA

NUMBER: 4117                            IA #: 4117
  DATE CREATED: JUN 05, 2003            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: HLUCM                        NAME: HL7 Capacity Management $$CM2F 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.  
  
 Patch HL*1.6*103 fully documents the $$CM2F^HLUCM API covered by this 
 integration agreement.  In addition, the patch documentation discusses the
 $$CM^HLUCM (DBIA# 3484) and $$CM2^HLUCM (DBIA# 3489) APIs.  
  
 COMPARISON OF $$CM, $$CM2 & $$CM2F: 
 -----------------------------------
 $$CM^HLUCM and $$CM2^HLUCM are almost identical to each other.  Both have 
 identical parameters and both return data in the same format.  The only 
 difference is that $$CM^HLUCM returns the number of messages during the 
 user-supplied time range, and $$CM2^HLUCM returns the number of "message 
 units" within a time range.  
  
 Messages are individually transmitted messages.  The initially transmitted
 message is considered a "message" by $$CM^HLUCM, and the return
 acknowledgement is considers a separate and unique "message."  If a message is
 transmitted, and an acknowledgement message returned, $$CM^HLUCM returns a
 total of two messages.  
  
 Message "units" are collections of functionally related messages.  In the 
 above example, $$CM^HLUCM counts two messages, but since the message and it's
 acknowledgement are functionally related, $$CM2^HLUCM returns a count of one
 "unit." 
  
 $$CM2F^HLUCM counts message units in an identical manner to $$CM2.  The only
 difference between these two APIs is the $$CM2F^HLUCM counts only message
 units involving remote sites.  $$CM2^HLUCM (and $$CM^HLUCM, for that matter)
 counts both locally and remotely sent message units.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HL7
KEYWORDS: CM
KEYWORDS: CAPACITY MANAGEMENT
COMPONENT/ENTRY POINT: $$CM2F
 COMPONENT DESCRIPTION:   The syntax for the $$CM2F call point is:   
  
   $$CM2F(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.  
  
 When $$CM2F is called, only remote message units are counted.  
  
 The above information regarding the $$CM2F 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: $$CM2F                       TYPE: Output
 VARIABLES DESCRIPTION:   Calling $$CM2F^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 $$CM2F^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 $$CM2F^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 $$CM2F^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 $$CM2F call point is: 
  
   $$CM2F(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 $$CM2F^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 $$CM2F call point is: 
  
   $$CM2F(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 $$CM2F^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 $$CM2F call point is: 
  
   $$CM2F(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 $$CM2F^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 $$CM2F call point is: 
  
   $$CM2F(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 $$CM2F^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 $$CM2F call point is: 
  
   $$CM2F(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 $$CM2F^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 $$CM2F call point is: 
  
   $$CM2F(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 $$CM2F^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 $$CM2F call point is: 
  
   $$CM2F(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) 
  
 The seventh parameter, ERR, is the location for error information returned by
 the $$CM2F call.  Here is an example call: 
  
 W $$CM2F^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: 4118                            IA #: 4118
  FILE NUMBER: 399.3                    GLOBAL ROOT: DGCR(399.3,
  DATE CREATED: JUN 05, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: ALLOW A/R TO UPDATE RATE TYPE FILE
  ID: DGCR(399.3,
GLOBAL REFERENCE: DGCR(399.3,D0,
FIELD NUMBER: .11                       FIELD NAME: BILL RESULTING FROM
  LOCATION: 0;11                        ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   The EDI Third Party Lockbox module includes
 functionality where, when electronic bill status messages are received in
 Integrated Billing containing specific data, the auto-audit function of A/R is
 automatically invoked, based on the rate type of the bill.  The IB portion of
 the patch is modifying the RATE TYPE file (#399.3 - which it owns) to add
 field #.11 BILL RESULTING FROM.  From an A/R standpoint then, if this field is
 filled in for a rate type, then all bills with that rate type are eligible for 
 the auto-audit function.  
  
 As a result, a request is being made to grant A/R Fileman write access to the
 RATE TYPE file (#399.3) to allow A/R personnel to update this field in this
 file so they can control which rate types can be auto-audited.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RATE TYPE
KEYWORDS: AUDIT
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany

NUMBER: 4119                            IA #: 4119
  DATE CREATED: JUN 05, 2003
  CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: USRPS23                      NAME: CALL TO USRPS23
  ID: USRPS23
 GENERAL DESCRIPTION:   Patches TIU*1*137 and USR*1*23 create new Document
 Definitions and a new User Class and new Business Rules in support of Anat
 Path.  They are sent out as a combined build.  
  
 The actual creation is done in an option sent out with TIU*1*137 but run after
 the distribution is installed.  
  
 Being able to create both the TIU and the USR entities from one option makes
 less work for sites, and ensures that the Document Definitions do not get
 created without the Business Rules which restrict their use.  
  
 This agreement permits TIU to call MAIN^USRPS23 and to kill the temp global
 created in USRPS23: ^TMP("USR23").  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 15, 2004
COMPONENT/ENTRY POINT: MAIN
 COMPONENT DESCRIPTION:   This module creates a new User Class and new Business
 Rules in support of Anatomic Pathology.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4120                            IA #: 4120
  DATE CREATED: JUL 08, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ALPBCBU                      NAME: BCMA CONTINGENCY UPDATE
  ID: ALPBCBU
 GENERAL DESCRIPTION:   The purpose of this API is to allow for Inpatient
 Pharmacy to cause an order update to the BAR CODE MEDICATION ADMINISTRATION
 (BCMA) CONTINGENCY software.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCBU
KEYWORDS: CONTINGENCY
COMPONENT/ENTRY POINT: NURV(DFN,PHARMACY ORDER#)
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry number for the patient. (Required) 
VARIABLES: PHARMACY ORDER#              TYPE: Input
 VARIABLES DESCRIPTION:   Order number (from the PHARMACY PATIENT file (#55)).  
 The order number must have the type indicator Examples are   41U,    15V,  
 23245P 
   (Required) 
  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham

NUMBER: 4121                            IA #: 4121
  DATE CREATED: JUN 11, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBJTLA
  NAME: A/R access to TPJI for patient name OR bill number
  ID: IBJTLA
 GENERAL DESCRIPTION:   An entrypoint is needed by A/R to access the TPJI
 (Third Party Joint Inquiry) option from a PROTOCOL action.  The level of entry
 needs to be at the point where the user is prompted to enter EITHER a patient
 name OR a bill number and the appropriate TPJI list manager screen will be 
 invoked.  This entry point already exists at line OPTION^IBJTLA and A/R would
 like to have access to this call.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TPJI
COMPONENT/ENTRY POINT: OPTION
 COMPONENT DESCRIPTION:   The user is prompted for patient name or bill number
 and the appropriate TPJI screen is displayed.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4122                            IA #: 4122
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: DEC 13, 2010            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: SET AUDIT ON NEW PERSON FILE #200 FIELDS
  ID: VA(200,
GLOBAL REFERENCE: VA(200,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7                         FIELD NAME: DISUSER
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9.2                       FIELD NAME: TERMINATION DATE
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,D0,2)
FIELD NUMBER: .132                      FIELD NAME: OFFICE PHONE
  LOCATION: .13;2                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,D0,1)
FIELD NUMBER: 9                         FIELD NAME: SSN
  LOCATION: 1;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: DOB
  LOCATION: 1;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: SEX
  LOCATION: 1;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,D0,VPID)
FIELD NUMBER: 9000                      FIELD NAME: VPID
  LOCATION: VPID;1                      ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,D0,NPI)
FIELD NUMBER: 41.99                     FIELD NAME: NPI
  LOCATION: NPI;1                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,D0,51,D1,0)
FIELD NUMBER: .01                       FIELD NAME: KEY
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,D0,51)
FIELD NUMBER: 51                        FIELD NAME: KEYS
  LOCATION: 51;0                        ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   The LAB SERVICE package (LSRP project) has a
 requirement that specific fields are to be set to be audited on patch
 installation for the NEW PERSON file (#200).  We are requesting a one-time use
 ICR that allows us to set this access on specific fields in file 200 using the
 supported API for this purpose (TURNON^DIAUTL).  This would be done in our
 post installation routine for patch LR*5.2*393  The fields are: 
  
 Top level:            
  
   .01   NAME 
   .132  OFFICE PHONE 
   .137  VOICE PAGER 
   .138  DIGITAL PAGER 
   4     SEX 
   5     DOB 
   7     DISUSER 
   9     SSN 
   9.2   TERMINATION DATE 
   41.99 NPI 
   9000  VPID 
  
   51    KEYS (subfile #200.051) 
         .01 KEY 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   The Fileman Read/Write access would be for setting the
 AUDITING feature only.  
  DATE ACTIVATED: DEC 15, 2010

NUMBER: 4123                            IA #: 4123
  FILE NUMBER: 409.61                   GLOBAL ROOT: SD(409.61
  DATE CREATED: AUG 24, 2004            CUSTODIAL PACKAGE: TOOLKIT
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: 4123                            ID: SD(409.61
GLOBAL REFERENCE: SD(409.61
 GENERAL DESCRIPTION:   If a List template has been distributed to a site and
 subsequent changes are made and KIDS is used to send the updated version, IT
 DOES NOT UPDATE to the new version but the old version is left in place. This
 gives the subscriber permission to directly KILL an entry and SET the zero
 node of file 409.61 (LIST TEMPLATE). This includes the use of the "B" cross 
 reference.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4124                            IA #: 4124
  DATE CREATED: AUG 12, 2003
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: CSLFB38
  NAME: DBIA3514-F                      ID: CSLFB38
 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: Retired
COMPONENT/ENTRY POINT: $$BLDMSG(.DATA,.PatientData)
 COMPONENT DESCRIPTION:   Extrinsic function called by the Fee Basis
 application to submit a request for Travel 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^CSLFB38 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 denote the line item number 
                 ranging from 1 to n 
  DATA(2) = VistA Payment Batch ID 
  DATA(3) = Invoice Date, format: YYYYMMDD 
  DATA(4) = Invoice Received Date, format: YYYYMMDD 
  DATA(5) = Accounting Code String 
  DATA(6) = VistA Invoice Number 
  DATA(7) = Invoice Amount 
  DATA(8,seq#) = Amount Paid for line item 
  DATA(9,seq#) = Prompt Pay Type for line item 
  DATA(10) = Payment Flag 
  DATA(11,seq#) = Amount Claimed for line item 
  DATA(12) = Buyer SSN (Fee Basis user's full SSN) 
  DATA(13,seq#) = Travel Date for line item 
  DATA(14) = Total Invoice line items 
  DATA(15) = Fee Program 
  DATA(16) = Payment Type Code 
VARIABLES: .PatientData                 TYPE: Input
 VARIABLES DESCRIPTION:   Second paramater, passed by reference, contains the 
 Veteran 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 Code 
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("CSLFB38;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("CSLFB38;MSGID","PRE_VALIDATION_MSG") = 
    Pre Validation Message ^XTMP("CSLFB38;MSGID","VISTA_INVOICE_NUMBER") = 
    VistA Invoice Number ^XTMP("CSLFB38;MSGID","VISTA_PAYMENT_BATCH_ID") = 
    VistA Payment Batch ID ^XTMP("CSLFB38;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("CSLFB38;MSGID","ERR",$H) = Error 
    description, applicable for both 
    Application Error (AE) 
    and Application Reject (AR) 
SUBSCRIBING PACKAGE: FEE BASIS          ISC: Washington/Silver Spring

NUMBER: 4125                            IA #: 4125
  DATE CREATED: JUL 21, 2003            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: CPT CODE UPDATE
 GENERAL DESCRIPTION:   attached package protocols will be notified of a code
 set update.  Packages may attach protocols using KIDS' "USE AS LINK FOR MENU
 ITEMS" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ICPT CODE UPDATE EVENT
 COMPONENT DESCRIPTION:   Notify applications that CPT/HCPCS codes  and
 modifiers have been updated.  

NUMBER: 4126                            IA #: 4126
  DATE CREATED: JUL 21, 2003            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: ICD CODE UPDATE
 GENERAL DESCRIPTION:   attached package protocols will be notified of a code
 set update.  Packages may attach protocols using KIDS' "USE AS LINK FOR MENU
 ITEMS" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ICD CODE UPDATE EVENT
 COMPONENT DESCRIPTION:   Notify applications that ICD codes have been updated. 
 

NUMBER: 4127                            IA #: 4127
  DATE CREATED: JUN 11, 2003
  CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: USRPS24                      NAME: CALL TO USRPS24
  ID: USRPS24
 GENERAL DESCRIPTION:   Patches TIU*1*165 and USR*1*24 create new Document
 Definitions and a new User Class and new Business Rules in support of Patient
 Record Flags. They are sent out as a combined build.  
  
 The actual creation is done in an option sent out with TIU*1*165 but run after
 the distribution is installed.  
  
 Being able to create both the TIU and the USR entities from one option makes
 less work for sites, and ensures that the Document Definitions do not get
 created without the Business Rules which restrict their use.  
  
 This agreement permits TIU to call MAIN^USRPS24 and to kill the temp global
 created in USRPS24: ^TMP("USR24",$J).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 09, 2004
COMPONENT/ENTRY POINT: MAIN
 COMPONENT DESCRIPTION:   This module creates a new User Class and new Business
 Rules in support of Patient Record Flags.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4128                            IA #: 4128
  FILE NUMBER: 399.2                    GLOBAL ROOT: DGCR(399.2,
  DATE CREATED: JUN 20, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: REVENUE CODE                    ID: DGCR(399.2,
GLOBAL REFERENCE: DGCR(399.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: REVENUE CODE
  LOCATION: 0;1                         ACCESS: Pointed to
FIELD NUMBER: 1                         FIELD NAME: STANDARD ABBREVIATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DESCRIPTION
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA allows Fee Basis to establish a field that
 points to the REVENUE CODE (#399.2) file.  LAYGO is not allowed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS          ISC: Washington/Silver Spring

NUMBER: 4129                            IA #: 4129
  DATE CREATED: JUN 30, 2003            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUP
  NAME: INVOKE DUZ~XUP                  ID: XUP
 GENERAL DESCRIPTION:   Noted by Custodian on 11/3/23 that it has been
 mentioned in the past that this API needs to be improved. That is, Kernel
 needs to find a better solution to allow VistA Kernel direct-authentication of
 the actual user logged in to VistA.  Setting the DUZ variable should be done
 only by Kernel after verification of valid and secure credentials. If we 
 continue allowing applications to "arbitrarily search" for an IEN in the NEW
 PERSON (#200) file, and then call DUZ^XUP to set the DUZ variable, it may
 cause additional problems. 
  STATUS: Active
COMPONENT/ENTRY POINT: DUZ(DA)
VARIABLES: DUZ                          TYPE: Output
 VARIABLES DESCRIPTION:   This procedure returns variable DUZ equal to your
 input parameter.  Also, components of the DUZ array are set-up as well.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   The required input parameter to DUZ^XUP(DA) is the
 internal entry number into file 200.  This is the user IEN of the user that
 you want to set the DUZ value and DUZ array to.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   The IB package has MRA (Medicare Remittance Advice)
 functionality using a specific, non-human user in file 200 (AUTHORIZER,IB
 MRA), effective with IB*2.0*155. IB MRA would like to be able to re-set the
 DUZ to be this non-human user so all filing and database activities appear to
 have been performed by this non-human IB MRA user instead of by the
 Postmaster.  
  
 IB MRA is invoking DUZ^XUP at the beginning of a background task to set the
 DUZ value and DUZ array entries.  
  
 Routine IBAMTS also must insure DUZ is set since the HL7 multi-thread listener
 is not passing a valid DUZ.  
  
 With IB*2.0*432, in routine IBCAPP for the new IB CBW functionality, a
 specific non-human user (AUTHORIZER,IB REG) is used for all reg 835 EOB filing
 processes.  IBCAPP would like to be able to re-set the DUZ to be this
 non-human user so all filing and database activities appear to have been
 performed by this non-human IB CBW user during these background processes.  
  
 Added 3/10/25, documenting specific non-human user (AUTHORIZER,IB ACC) which
 is used for IB Automated Community Care (ACC) claims processes with 
 IB*2.0*770.  
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: IFCAP
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: VISTALINK SECURITY
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: MAILMAN
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Added 11/12/20.  
SUBSCRIBING PACKAGE: HEALTH LEVEL SEVEN
 SUBSCRIBING DETAILS:   Added 1/31/22 to document access in an existing routine
 HLCSTCP4.  Patch HL*1.6*174, will include the ICR reference in the routine.
 The DUZ^XUP access is necessary to initialize the DUZ variables as part of the 
 incoming background filer which is not tied to an actual user.  HLCSTCP4
 ;SFIRMFO/RSD - BI-DIRECTIONAL TCP ;08/03/2011 13:29 
  ;;1.6;HEALTH LEVEL SEVEN;**109,122,140,157**;Oct 13,1995;Build 8 
  ;Per VHA Directive 2004-038, this routine should not be modified.  
  ;
  Q 
  ; RDERR & ERROR moved from HLCSTCP2 on 12/2/2003 - LJA 
  ;
 HLDUZ2 ; compare DUZ and HLDUZ 
  I $G(DUZ)'=HLDUZ D 
  . S DUZ=HLDUZ 
  . D DUZ^XUP(DUZ) 
  Q 
  ;
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Added 7/11/22,effective with patch RA*5*192, to use
 POSTMASTER (DUZ=.5) to update the radiology order status and the CPRS order
 status to COMPLETE.  This update requires who made the change.  
SUBSCRIBING PACKAGE: DSS RXTRACKER
 SUBSCRIBING DETAILS:   Added 11/3/23, effective with patch DSHX 2.0 for the
 DSS RXTRACKER, also referred to as DSHX RXTRACKER. DSHX needs to alter DUZ in
 routines DSHXOMP, DSHXOMP2, and DSHXOMPX. The provider(s) who  
 prescribed/discontinued the medication in RxTracker (external to VistA) are
 returned in the HL7 message that is received and consumed by Vista. The
 processing of the inbound HL7 message is invoked by the multi-listener in the
 background so there is no user log-in for the instance. The Vista HL7
 application DUZ value is that of the user who logged into CPRS/VistA or
 Postmaster (.5) and not that of the provider/pharmacist who prescribed the
 medication order in RxTracker.  Having the accurate DUZ values will ensure the
 proper provider/pharmacist is associated with the medication order(s).  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 3/5/25, effective with patch PSO*7.0*774, to
 allow for auto release of pharmacy medications on a host site that were
 refilled or partial filled remotely via OneVA Pharmacy and dispensed remotely
 by an automated dispensing device. Since the user performing the release at 
 the dispensing site is not on file locally at the host site, the proxy user
 PSOAUTORELEASE,PROXY USER is added to the NEW PERSON file (#200) by this patch
 and the DUZ variable containing this proxy user is required to invoke required
 ECME/IB APIs. As the actual user performing the remote release of the pharmacy
 prescription is stored as free text in the REMOTE PRESCRIPTION  LOG file
 (#52.09), and the unique prescription number is stored on the remote
 dispensing site in this same file, there is a manual method by which the
 remote user may be identified if necessary. Until the long term goal of using
 SEC ID to identify remote users via an enterprise pattern that could address
 application proxy-based scenarios, this intermediate solution is necessary for
 OneVA.  
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   ADDED 6/20/25 effective with patch MECH 1.0. Medicom
 needs to alter the DUZ in routines MECHACIROREG and MECHACIRPFAR. The
 processing of the inbound HL7 message is invoked by the multi-listener in the
 background so there is no user log-in for the instance. The Vista HL7
 application DUZ value is that of the user who logged into VistA. Changing the
 DUZ to the user RADIOLOGY,USER in the NEW PERSON file (#200) will allow the
 various activity logs for an exam/order being processed via the HL7 message to
 store the appropriate user associated with that exam/order.  
  DATE ACTIVATED: DEC 16, 2010

NUMBER: 4130                            IA #: 4130
  DATE CREATED: JUN 17, 2003            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: AVJLES
  NAME: LES ORDER CHECK                 ID: AVJLES
 GENERAL DESCRIPTION:   In CPRS GUI, when user edited the lab order, the new
 generated lab order needs the validation check by the "Lab Expert
 System"(LES), the existed LES API "COM^AVJLES" need to be called by CPRS for
 this purpose.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: LES
COMPONENT/ENTRY POINT: COM(.ORY,ORDFN,ORLAB,ORLOC,ORNP,ORDT)
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   Empty string   : valid lab order Array of string:
 invalid lab order with the error message 
VARIABLES: ORDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: ORLAB                        TYPE: Input
 VARIABLES DESCRIPTION:   Lab order IEN 
VARIABLES: ORLOC                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient location 
VARIABLES: ORNP                         TYPE: Input
 VARIABLES DESCRIPTION:   Provider IEN 
VARIABLES: ORDT                         TYPE: Input
 VARIABLES DESCRIPTION:   Lab order's collection date/time 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4131                            IA #: 4131
  DATE CREATED: JUL 16, 2003            CUSTODIAL PACKAGE: EVENT CAPTURE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ECRRPC                       NAME: ECS REPORT
  ID: ECRRPC
 GENERAL DESCRIPTION:   The API "RPTEN^ECRRPC" returns the patient event
 capture report's data. CPRS need to call the API for displaying the event
 capture report. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECS
COMPONENT/ENTRY POINT: RPTEN
VARIABLES: ORECARY                      TYPE: Input
 VARIABLES DESCRIPTION:   Array of the appropriate values passed from the CPRS
 GUI ORECARY("ECHNDL") - Handle of report that's to be generated. 
 ORECARY("ECPTYP") =Display or Print to a device.  ORECARY("ECDEV")  =IEN of
 the Print device (#3.5) ORECARY("ECDFN")  =Patient IEN (#2) ORECARY("ECED")  
 =Report End Date ORECARY("ECRY")   =Display Procedure Reasons ORECARY("ECSD")  
 =Report Start Date ORECARY("ECDUZ")  =User DUZ 
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   Patient's event capture report data.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4132                            IA #: 4132
  DATE CREATED: JUN 17, 2003            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DG FIELD MONITOR
 GENERAL DESCRIPTION:   Automatically adding the following entries to the
 following files.  
  
  
 File #3.5 
  
 NAME: DG FIELD MONITOR                  $I: DG FIELD MONITOR 
     LOCATION OF TERMINAL: DG field editing protocol 
     RESOURCE SLOTS: 9                     SUBTYPE: P-OTHER 
     TYPE: RESOURCES 
  
  
 File #3.54 
  
     NAME: DG FIELD MONITOR                  AVAILABLE SLOTS: 9 
  STATUS: Active                        EXPIRATION DATE: JUN 11, 2004
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4133                            IA #: 4133
  DATE CREATED: JUN 25, 2003            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDAMA203
  NAME: IMO QUALIFIER                   ID: SDAMA203
 GENERAL DESCRIPTION:   The purpose of this DBIA is asking for permission to
 call the scheduling API from OE/RR at server side to determine if a specific
 patient at a specific clinic is qualified to receive inpatient medication.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IMO
COMPONENT/ENTRY POINT: $$SDIMO(ORLOC,ORDFN)
 COMPONENT DESCRIPTION:   This API determines if a specific patient at a
 specific clinic is qualified to receive inpatient medication.  
VARIABLES: ORDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: ORLOC                        TYPE: Input
 VARIABLES DESCRIPTION:   Location IEN 
COMPONENT/ENTRY POINT: SDAUTHCL(PSJCLIN,.PSJCLOK)
 COMPONENT DESCRIPTION:   This API determines if a specific clinic is
 authorized to dispense inpatient medications to outpatients 
VARIABLES: PSJCLIN                      TYPE: Input
 VARIABLES DESCRIPTION:   Location IEN 
VARIABLES: PSJCLOK                      TYPE: Both
 VARIABLES DESCRIPTION:   Authorized Flag. A value of 1 is passed in by
 reference.  
  
 Authorized Flag. An clinic authorized to dispense medications to inpatients
 returns 1, clinics not authorized return -1.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA needs access to entry points SDIMO and SDAUTHCL in
 routine SDAMA203.  VIA will be creating RPC VIAB IMOLOC for use with their 
 OrderMgmtSvc - isInpatientMedicationLocation.  

NUMBER: 4134                            IA #: 4134
  DATE CREATED: JUN 23, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORCHECK
  NAME: ORCHECK                         ID: ORCHECK
 GENERAL DESCRIPTION:   Allergy tracking requests the use of the BLD entry
 point in ORCHECK.  This call will put the patient's order in the correct 
 format for order checking code to process.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: BLD(ORDER)
 COMPONENT DESCRIPTION:   The following API is defined by this agreement: 
  
 BLD - The call to BLD will take the CPRS order identified by the ORDER
 parameter and reformat it into the expected format for order checking.  The
 array ORX is returned with the orders in proper format.  
VARIABLES: ORDER                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number from ORDERS (#100) file to be
 converted to order checking format.  
VARIABLES: ORX                          TYPE: Output
 VARIABLES DESCRIPTION:   This array will hold the newly formatted information
 that can then be sent to the order checking software.  Multiple calls to BLD
 will continue to build the ORX array.  
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
 SUBSCRIBING DETAILS:   Allergy tracking needs to call order checking code when
 a new allergy is entered.  Currently, order checking only occurs when new
 orders are entered.  

NUMBER: 4135                            IA #: 4135
  DATE CREATED: JUN 23, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORKCHK
  NAME: ORKCHK                          ID: ORKCHK
 GENERAL DESCRIPTION:   Adverse reaction tracking requests the ability to call
 into the order checking software.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORDER CHECK
COMPONENT/ENTRY POINT: EN(ORKY,ORKDFN,ORKA,ORKMODE,OROIL,ORDODSG)
 COMPONENT DESCRIPTION:   This entry point returns any order checks found in
 the order check array specified for the patient and orders checked.  
VARIABLES: ORKY                         TYPE: Both
 VARIABLES DESCRIPTION:   Array of returned messages (order checks found) in
 the following format: ORDER NUMBER^ORDER CHECK IEN^CLINICAL DANGER^MESSAGE 
VARIABLES: ORKDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN 
VARIABLES: ORKA                         TYPE: Input
 VARIABLES DESCRIPTION:   Array of orderable items to check.  This array is
 built using the BLD^ORCHECK API.  See DBIA #4134.  
VARIABLES: ORKMODE                      TYPE: Input
 VARIABLES DESCRIPTION:   Determines the mode of order checking.  Set this
 variable to either DISPLAY, SELECT, ACCEPT, SESSION, ALL, or NOTIF.  Adverse
 reaction tracking will set this variable to "ACCEPT" because adverse reaction 
 tracking checks are of this type.  See the order checking documentation for a
 complete description of the different modes.  
VARIABLES: OROIL                        TYPE: Input
 VARIABLES DESCRIPTION:   Array of order information to check.  For adverse
 reaction tracking, this variable is set to null as the orderable items to
 check are passed in the ORKA parameter.  
VARIABLES: ORDODSG                      TYPE: Both
 VARIABLES DESCRIPTION:   Determines whether to perform pharmacy dosage checks. 
 The caller must pass this variable in by reference.  Adverse reaction tracking
 will set this variable to 0 to disable dosage checking since adverse reaction 
 tracking checks are not concerned with medication dosages.  Since only one 
 call is made to this API per patient, the caller may safely ignore the 
 returned value.  
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
 SUBSCRIBING DETAILS:   Adverse reaction tracking has a requirement to call
 order checking software when an adverse reaction is documented or modified.  
  DATE ACTIVATED: MAR 26, 2014

NUMBER: 4136                            IA #: 4136
  FILE NUMBER: 5.12                     GLOBAL ROOT: DD(5.12,0,'PT'
  DATE CREATED: JUN 24, 2003            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Look For 'PT' Nodes in File 5.12
  ID: DD(5.12,0,'PT'
 GENERAL DESCRIPTION:   
  
 In routine XIPENV (enviroment check routine) it is necessary to look for "PT"
 nodes of files that should NOT be Pointing To this file.  The need for this
 check is because in the pre-installation routine will be deleting this file
 prior to the new DD and data being installed.  
  STATUS: Active
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

NUMBER: 4137                            IA #: 4137
  FILE NUMBER: 5.13                     GLOBAL ROOT: DD(5.13,0,'PT',
  DATE CREATED: JUN 24, 2003            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Look For 'PT' Nodes in File 5.13
  ID: DD(5.13,0,'PT',
 GENERAL DESCRIPTION:   In routine XIPENV (enviroment check routine) it is
 necessary to look for "PT" nodes of files that should NOT be Pointing To this
 file.  The need for this check is because in the pre-installation routine will
 be deleting this file prior to the new DD and data being installed.  
  STATUS: Active
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

NUMBER: 4138                            IA #: 4138
  DATE CREATED: JUN 26, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: DPTLK1
  NAME: NON-INTERACTIVE PATIENT LOOKUP LIST
  ID: DPTLK1                            STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$LIST
 COMPONENT DESCRIPTION:   This API facilitates the non-interactive return of
 patient record match lists based on a specified lookup value.  
VARIABLES: DPTX                         TYPE: Input
 VARIABLES DESCRIPTION:   Lookup value (Name, SSN, Room, Ward, DFN, or
 "space_return").  
VARIABLES: DPTLMAX                      TYPE: Input
 VARIABLES DESCRIPTION:   Maximum number of matches to return (optional).  This
 parameter has no effect if DFN or "space_return" lookup methods are used.  
VARIABLES: DPTLARR                      TYPE: Output
 VARIABLES DESCRIPTION:   Name of array to return list of matches.  This should
 be a global if DPTLMAX is a large value or unspecified.  This array is
 returned in the format: 
  
 @DPTLARR@(n)=DFN^Patient Name^xref_lookup_match_value^SSN^Date of Birth 
  
 If more matches exist than the maximum to be returned as specified by DPTLMAX,
 the @DPTLARR@(DPTLMAX+1) node will be defined = "ADDITIONAL MATCHES FOUND BUT
 NOT RETURNED".  
  
 The calling program has the responsibility to kill @DPTLARR prior to calling
 this entry point.  

NUMBER: 4139                            IA #: 4139
  FILE NUMBER: 2                        GLOBAL ROOT: DD(2
  DATE CREATED: DEC 13, 2010            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PATIENT FILE (#2) DATE OF BIRTH FIELD (.03) IDENTIFIER
  ID: DD(2
GLOBAL REFERENCE: DD(2,0,'ID'
FIELD NUMBER: .03                       FIELD NAME: DATE OF BIRTH
  LOCATION: DD(2,0,'ID',.03             ACCESS: Direct Global Write & w/Fileman
 GENERAL DESCRIPTION:   This is a one-time agreement to allow Registration to
 set the IDENTIFIER node as follows for the PATIENT (#2) file: 
  
 ^DD(2,0,"ID",.03)="D EN^DDIOL($TR($$DOB^DPTLK1(Y,1),""/"",""-""),,""?$X+2"")" 
  
 This api will add the IDENTIFIER parameter back to the PATIENT file (#2).  It
 was an unknown fact that the IDENTIFIER parameter would be removed when the
 DG*5.3*754 pre-init routine (DG53754P) initialized the field definition for
 the DATE OF BIRTH field (#.03) from the PATIENT file (#2).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: MAR 31, 2011
KEYWORDS: DOB IDENTIFIER
SUBSCRIBING PACKAGE: REGISTRATION
  DATE ACTIVATED: DEC 13, 2010
REMINDER: MAR 31, 2011

NUMBER: 4140                            IA #: 4140
  FILE NUMBER: 5.12                     GLOBAL ROOT: DD(5.12,0,'ID'
  DATE CREATED: JUN 30, 2003            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Remove ID Node From File #5.12
  ID: DD(5.12,0,'ID'
 GENERAL DESCRIPTION:   During the install of data at the target site for patch
 XU*8*292 it is necessary to have 'UNIQUE KEY (VA)' (#8) field brought in as an 
 Identifier so duplicate Zip Code entries can be resolved, then during the 
 post-install it is necessary to remove it via: 
  
 K ^DD(5.12,0,"ID",8) ; IA #4140 
  
 This would be a one time agreement.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

NUMBER: 4141                            IA #: 4141
  FILE NUMBER: 4.2                      GLOBAL ROOT: DIC(4.2,
  DATE CREATED: JUL 02, 2003            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Closing Legacy Queues           ID: DIC(4.2,
 GENERAL DESCRIPTION:   When CoreFLS is implemented at a site, the IFCAP and
 Engineering (AEMS/MERS) packages will be inactivated by the Legacy Software
 Shut Down patch and there should not be transmission of documents to the 
 domains or queues set up to support their business.  As the deployment of 
 CoreFLS nationally will be phased in over a period of a few years, it seems
 more appropriate that the software involved in the inactivation of IFCAP and
 Engineering, rather than an nationally released MailMan patch, should close
 these domains/queues. It is requested that as part of the Legacy Software Shut
 Down process, PRCL namespaced code be allowed to set the DOMAIN file (#4.2)
 entry's FLAGS field (#1) to 'C' (CLOSED) and delete the current value of the
 RELAY DOMAIN field (#2) for the following domains: 
         CONST.RD4-REGION4.DNS 
         NESC.DNS 
         Q-CRD.DNS 
         Q-EDP.DNS 
         Q-EDV.DNS 
         Q-FAM.DNS 
         Q-FMZ.DNS 
         Q-ISM.DNS 
         Q-LOG.DNS 
         Q-PRC.DNS 
  
 Before filing the changes, the current values of those domains/queues will be
 extracted and stored in the LEGACY SOFTWARE SHUT DOWN file (#449.1), so that
 they are available for restoration if necessary.  As part of this integration
 agreement, we are also requesting that the software be permitted to file the
 original values back into the DOMAIN file entries, in the remote likelihood
 that the CoreFLS implementation needs to be temporarily reversed.  
  
 The extraction of current values and the filing would be performed by calls to
 supported FileMan database server APIs.  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
KEYWORDS: COREFLS
KEYWORDS: LEGACY SOFTWARE SHUT DOWN
KEYWORDS: CLOSING QUEUES
SUBSCRIBING PACKAGE: IFCAP              ISC: Washington/Silver Spring

NUMBER: 4142                            IA #: 4142
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19,
  DATE CREATED: JUL 16, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Entry Action Setting in Option  ID: DIC(19,
 GENERAL DESCRIPTION:   As part of the Legacy Software Shut Down process,
 IFCAP, Engineering (AEMS/MERS) and Equipment/Turn-In Request options that
 change the database will be disabled.  Only read access to the database will
 be allowed once the site comes up on CoreFLS. Although putting a string in the
 OUT OF ORDER MESSAGE field (#2) can put the option offline, it seems
 preferable to also inactivate the option by putting "S XQUIT=1" in the ENTRY
 ACTION field (#20).  There currently is not a supported Kernel API
 specifically for editing the ENTRY ACTION field. Management has previously
 instructed our team not to edit the application routines in order to
 inactivate the option.  
  
 Specifically this request is to permit PRCL namespaced code to file "S 
 XQUIT=1" in the ENTRY ACTION field of selected options of these three legacy
 packages using supported FileMan (FM) database server APIs.  Before filing the
 new value, the existing value will be extracted via a FM supported API and
 stored in the LEGACY SOFTWARE SHUT DOWN file (#449.1) so that it is available
 if needed.  In the remote possibility the the site temporarily needs to resume
 business activity in the legacy systems, it is also requested that the
 software be permitted to restore the original value for each entry again using
 supported FM APIs.  [Note: The software is also filing of an Out of Order
 Message using the supported OUT^XPDMENU() API.] 
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
KEYWORDS: COREFLS
KEYWORDS: LEGACY SOFTWARE SHUT DOWN
KEYWORDS: ENTRY ACTION
SUBSCRIBING PACKAGE: IFCAP              ISC: Washington/Silver Spring

NUMBER: 4143                            IA #: 4143
  FILE NUMBER: 19.2                     GLOBAL ROOT: DIC(19.2,
  DATE CREATED: JUL 03, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Scheduled Option Removal        ID: DIC(19.2,
 GENERAL DESCRIPTION:   The Legacy Software Shut Down project will be
 converting the IFCAP, Engineering (AEMS/MERS) and Equipment/Turn-In Request
 packages to Read-Only as part of the site's coming on line with CoreFLS. 
 Scheduled options, especially those which may alter the database, must be
 removed from the OPTION SCHEDULING file (#19.2).  This request is to permit
 PRCL namespaced code to remove any entries in the namespaces of these legacy 
 packages from file 19.2.  
  
 Specifically it is requested that the Legacy Sofware Shut Down software be 
 permitted to extract via supported FileMan database server APIs, the current
 value of most fields of the entry to be removed so that they can be stored in
 the LEGACY SOFTWARE SHUT DOWN file (#449.1) in case the values are needed
 later. The TASK ID field (#12) and the computed TASK DEFIND field (#99.1),
 however, will not be backed up.  The request further asks for permission to
 remove the entry from file 19.2 via a ^DIK call.  Finally, in the highly
 unlikely event that the site must temporarily resume using these packages,
 instead of CoreFLS, for business activities, it is requested that the software
 be permitted to create a new entry in file 19.2 to reschedule each of the
 affected options.  This again would be accomplished through supported FileMan
 APIs.  TaskManager, not this software, would establish the value for the TASK
 ID field.  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
KEYWORDS: COREFLS
KEYWORDS: UNSCHEDULE OPTIONS
KEYWORDS: LEGACY SOFTWARE SHUTDOWN
SUBSCRIBING PACKAGE: IFCAP              ISC: Washington/Silver Spring

NUMBER: 4144                            IA #: 4144
  FILE NUMBER: 14.4                     GLOBAL ROOT: ZTSK(
  DATE CREATED: JUL 03, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Dequeueing Legacy Software Tasks
  ID: ZTSK(
 GENERAL DESCRIPTION:   The Legacy Software Shut Down patch will be converting
 the IFCAP, Engineering (AEMS/MERS) and Equipment/Turn-In Request packages to 
 Read-Only when the site comes up on CoreFLS.  Queued tasks for these packages,
 especially those that may alter the database, must be dequeued.  Specifically,
 this request asks that PRCL namespaced software be permitted to $Order()
 through the ^%ZTSK global and to identify tasks to be dequeued through
 examination by direct global read of the Routine Name field (#2) [node 0,
 piece 2], comparing the routine's prefix to the namespaces of the above
 packages.  (For dequeueing, the status of the task must also be verified as
 "Active: Pending" using the supported Kernel API STAT^%ZTLOAD.) Where the task
 is to be dequeued via supported Kernel API DQ^%ZTLOAD, it is requested that
 the software be permitted to file via a supported FileMan database server API
 a value of one year from the run date into the Remember Untill field (#59.8)
 so that the task is still available, in the highly unlikely case that the site
 needs to temporarily resume business processing using these legacy packages
 instead of CoreFLS and wishes to requeue the task.  Finally, for reporting
 tasks dequeued as part of the shut down, it is requested that the software be
 permitted to extract via a supported FileMan database server API, the values
 for the Entry Point field (#.01), Routine Name field (#2) and the Task
 Description field (#41), so they can be displayed in addition to the task
 number.  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
KEYWORDS: DEQUEUE
KEYWORDS: LEGACY SOFTWARE SHUT DOWN
KEYWORDS: COREFLS
SUBSCRIBING PACKAGE: IFCAP              ISC: Washington/Silver Spring

NUMBER: 4145                            IA #: 4145
  FILE NUMBER: 200.032                  GLOBAL ROOT: VA(200,DUZ,'FOF',
  DATE CREATED: JUL 03, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Kernel Part 3 - Modifying File Access Permissions
  ID: VA(200,DUZ,'FOF',
 GENERAL DESCRIPTION:   The Legacy Software Shut Down patch will convert the
 IFCAP, Engineering (AEMS/MERS), and Equipment/Turn-In Request packages to
 Read-Only.  Users must not be able to edit via FileMan, files of the above
 packages.  Although some restriction can be accomplished by the IRM removing
 Write and Delete/Purge permissions to application namespaced globals, some 
 Engineering files still store data in the ^DIC global, whose protection can
 not be changed by this patch. In addition, as a temporary workaround for
 Prosthetics during the initial deployment of CoreFLS at VAMC Bay Pines, the
 protection of the IFCAP ^PRC global can not be modified so access to files
 stored in this global has to be controlled via VA FileMan or Kernel Part 3
 setups.  This request concerns sites that have implemented the Kernel Part 3
 access controls.  
  
 Specifically, this request asks that PRCL namespaced code be permitted to 
 $Order() through the AFOF cross reference in the NEW PERSON file (#200) in
 order to identify individuals with access to the files of interest and the
 internal number of the accessible file multiple entry.  It is further
 requested that the software be permitted to extract via a supported FileMan
 API, the current access values in case they are needed later. They will be
 stored in the LEGACY SOFTWARE SHUT DOWN file (#449.1).  It is requested that
 the software be permitted to file via a supported FileMan API, '0' (NO) for
 DATA DICTIONARY ACCESS, DELETE ACCESS, LAYGO ACCESS, and WRITE ACCESS to the
 files of these packages.  Finally, in the highly unlikely situation that users
 need to temporarily resume using these legacy packages, rather than CoreFLS
 for their business activities, it is requested that the software be permitted
 to file via a supported FileMan API, the original values back into the
 ACCESSIBLE FILE multiple of the NEW PERSON entries that were modified during
 the shut down.  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.1
KEYWORDS: LEGACY SOFTWARE SHUT DOWN
KEYWORDS: FILE ACCESS PERMISSIONS
KEYWORDS: COREFLS
SUBSCRIBING PACKAGE: IFCAP              ISC: Washington/Silver Spring

NUMBER: 4146                            IA #: 4146
  DATE CREATED: FEB 22, 2007            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: BPSUTIL
  NAME: BPSUTIL                         ID: BPSUTIL
 GENERAL DESCRIPTION:   The application programming interfaces covered by this
 agreement have been designed to support ePharmacy/ECME Enhancements project
 and: 
  -  provide the Integrated Billing package with the status, date of service
 and amount paid for the claim by the third party ($$PAIDAMNT), 
  -  allow the Integrated Billing user to select and use ePharmacy divisions
 for reporting purposes ($$SELPHARM, $$MULTPHRM, $$GETPHARM), 
  -  return NDPDP # and NPI for Controlled Substance Pharmacy.  
  
 Amended 8/2022: $$CSNPI added, effective with BPS*1.0*33 and PSO*7.0*680, not
 used by IB.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
COMPONENT/ENTRY POINT: $$SELPHARM
 COMPONENT DESCRIPTION:   Prompts the user to select ePharmacy divisions from
 BPS PHARMACIES file #9002313.56 
VARIABLES: BPSPHAR                      TYPE: Both
 VARIABLES DESCRIPTION:   BPSPHAR is passed by reference to get the result of
 the user's selection.  
  
 If BPSPHAR = 1 then the BPSPHAR array will be defined where: BPSPHAR(ptr) =
 ptr ^ BPS PHARMACY NAME and ptr = Internal Pointer to BPS PHARMACIES file
 (#9002313.56).  
  
 If BPSPHAR = 0 when the user selects "ALL" divisions.  
  
 If BPSPHAR is undefined when the user enters "^" to quit.  
VARIABLES: $$SELPHARM                   TYPE: Output
 VARIABLES DESCRIPTION:   Return Value: 
  "" = Valid Entry or Entries Selected ; 
  ^  = Exit ; 
COMPONENT/ENTRY POINT: $$GETPHARM
 COMPONENT DESCRIPTION:   Function to return e-Pharmacy (BPS  PHARMACIES file
 #9002313.56 ien) by OUTPATIENT SITE file #59 ien 
VARIABLES: BPSDIV                       TYPE: Input
 VARIABLES DESCRIPTION:   Outpatient Site file #59 ien 
VARIABLES: $$GETPHARM                   TYPE: Output
 VARIABLES DESCRIPTION:   BPS Pharmacy ien (file #9002313.56) 
COMPONENT/ENTRY POINT: $$MULTPHRM
 COMPONENT DESCRIPTION:   API for IB (IA #4146) to determine whether is one or
 more BPS PHARMACIES in the system.  
VARIABLES: $$MULTPHRM                   TYPE: Output
 VARIABLES DESCRIPTION:   Returned values: 1 - if the site has more than one
 record in the file #9002313.56 0 - if there are no any divisions 0^NAME OF THE
 EPHARM - if only one division return 0 and its name to use in the header of
 the report 
COMPONENT/ENTRY POINT: $$PAIDAMNT
 COMPONENT DESCRIPTION:   This API returns: the Status of the claim, the Dollar
 amount the payer agreed to pay and the Date of service.  
VARIABLES: BPSRX                        TYPE: Input
 VARIABLES DESCRIPTION:   PRESCRIPTION file #52 ien 
VARIABLES: BPSREFNO                     TYPE: Input
 VARIABLES DESCRIPTION:   Refill number (0 for original) 
VARIABLES: $$PAIDAMNT                   TYPE: Output
 VARIABLES DESCRIPTION:   1st piece: 
   0 - status "non-payable" or there is no response 
   from the payer for whatever reason or invalid parameters 
   1- status "payable" 
  
 2nd piece: 
   Dollar amount the payer agreed to pay 
  
 3rd piece: 
   Date of Service in FileMan  format 
COMPONENT/ENTRY POINT: $$CSNPI
 COMPONENT DESCRIPTION:   This API returns: the NCPDP # and NPI for the
 Controlled Substance Pharmacy, if any.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   PRESCRIPTION file #52 ien 
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Refill number (0 for original) 
VARIABLES: $$CSNPI                      TYPE: Output
 VARIABLES DESCRIPTION:   Return Value: 
  NCPDP ^ NPI (if any) 
  -1 ^ (if none) 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: AUG 03, 2022

NUMBER: 4147                            IA #: 4147
  DATE CREATED: FEB 22, 2007
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: CALL TO THE TIU TEMPLATE REMINDER DIALOGS PARAMETER
 GENERAL DESCRIPTION:   This IA will allow Clinical Reminders to be able to
 call the TIU parameter TIU TEMPLATE REMINDER DIALOGS from a Clinical Reminder
 option.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU TEMPLATE REMINDER DIALOGS
KEYWORDS: PXRM
KEYWORDS: TIU
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: FEB 26, 2007

NUMBER: 4148                            IA #: 4148
  DATE CREATED: FEB 23, 2007            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  NAME: VistALink J2M Java APIs [vljConnector-x.x.x.xxx.jar]
 GENERAL DESCRIPTION:   
    This ICR describes the supported VistALink J2M (v1.5) Java APIs for 
    the vljConnector-x.x.x.xxx.jar file.  
  
    It is strongly recommended that you consult the javadoc for the 
    VistALink J2M software for more detail on all supported VistALink 
    J2M Java APIs.  
  
    
    Jar: 
       vljConnector-x.x.x.xxx.jar   
    
    Connector Packages: 
       gov.va.med.vistalink.adapter.cci 
       gov.va.med.vistalink.adapter.heartbeat 
       gov.va.med.vistalink.adapter.record 
       gov.va.med.vistalink.adapter.spi 
  
    RPC Package: 
       gov.va.med.vistalink.rpc 
  
    Institution Mapping Utilities Package: 
       gov.va.med.vistalink.institution   
  
  
  
    Package gov.va.med.vistalink.adapter.cci 
    ========================================
       Implements the Common Client Interface (CCI) portion of the Java 
       Connector Architecture (JCA) for VistaLink.  
     
       Interface Summary 
       =================
          VistaLinkConnection 
             This interface represents an application level connection 
             handle that is used by a component to access an EIS instance.  
     
          VistaLinkConnectionSpec 
             This interface defined the common properties needed by any 
             connection spec implementation.  
  
       Class Summary 
       =============
          VistaLinkAppProxyConnectionSpec 
             This is the connection spec class for Application Proxy 
             re-authentication.  
     
          VistaLinkConnectionFactory 
             This implementation class provides an interface for getting 
             connection to an EIS instance.  
     
          VistaLinkConnectionMetaData 
             Provides information about an EIS instance connected through a 
             Connection instance.  
     
          VistaLinkConnectionSpecImpl 
             This is the base implementation class for 
             VistaLinkConnectionSpec.  
          
          VistaLinkDuzConnectionSpec 
             This is the connection spec class for Duz re-authentication.  
     
          VistaLinkResourceAdapterMetaData 
             Implementation class provides info about the capabilities of a 
             resource adapter.  
     
          VistaLinkVpidConnectionSpec 
             This is the connection spec class for VPID re-authentication.  
  
       Exception Summary 
       =================
          VistaLinkResourceException 
             Represents a ResourceException thrown by the VistaLink 
             adapter.  
     
  
    Package gov.va.med.vistalink.adapter.heartbeat 
    ==============================================
       Implements the heartbeat keepalive timer process for VistaLink.  
  
       Exception Summary 
       =================
          HeartBeatFailedException 
             This exception class is used to notify the managed connection 
             and its event listeners that a scheduled heart beat has 
             failed.  
          
          HeartBeatInitializationFailedException 
             This exception class is thrown when the heart beat fails to 
             make its first interaction to retrieve the heartbeat rate from 
             M.  
     
  
    Package gov.va.med.vistalink.adapter.record 
    ===========================================
       Implements basic request- and response-related classes for 
       VistaLink.  
  
       Interface Summary 
       =================
          VistaLinkRequestRetryStrategy 
             Base strategy interface for determining if request should be 
             re-executed.  
  
          VistaLinkRequestVO 
             Base request interface.  
  
       Class Summary 
       =============
          VistaLinkRequestRetryStrategyAllow 
             Simple 'Allow' strategy implementation that indicates request 
             should be re-executed.  
     
          VistaLinkRequestRetryStrategyDeny 
             Simple 'Deny' strategy implementation that indicates request 
             should not be re-executed.  
     
          VistaLinkRequestVOImpl 
             Base request implementation.  
  
       Exception Summary 
       =================
          LoginsDisabledFaultException 
             This exception represents the case where the M side has logins 
             disabled; this is when the site sets the parameter to not 
             allow any logins.  
     
          NoJobSlotsAvailableFaultException 
             This exception represents the case where on the M side there 
             are no license slots available to start another process.  
  
          VistaLinkFaultException 
             Exception encapsulates Fault information coming from M side.  
  
     
    Package gov.va.med.vistalink.adapter.spi 
    ========================================
       Implements the Service Provider Interface (spi) portion of the Java 
       Connector Architecture (JCA) for VistaLink.  
     
       Class Summary 
       =============
          VistaLinkServerInfo 
             Represents M VistA connection information, like address and 
             port.  
     
       Exception Summary 
       =================
          ConnectionHandlesExceededException 
             This exception class is thrown when a 
             VistaLinkManagedConnection object has exceeded its maximum 
             allowable connection handles.  
          
          VistaLinkSocketAlreadyClosedException 
             Represents a situation where, when attempting to close a 
             socket, the socket is already closed.  
     
          VistaLinkSocketClosedException 
             This exception class is thrown when an attempt is made to 
             access the VistaLinkManagedConnection's underlying 
             VistaSocketConnection after it has been closed or invalidated.  
  
  
    Package gov.va.med.vistalink.rpc 
    ================================
       Implements RPC requests and responses over VistaLink.  
  
       Class Summary 
       =============
          RpcReferenceType 
             Represents a reference type object for an RPC parameter.  
     
          RpcRequest 
             Represents a RPC request to an M VistA server.  
     
          RpcRequestFactory 
             Factory class to creates instances of RpcRequest.  
     
             J2SE Example: //request and response objects 
             RpcRequest vReq = null; 
             RpcResponse vResp = null; //The Rpc Context 
             String rpcContext = "XOBV VISTALINK TESTER"; //The Rpc to call 
             String rpcName = "XOBV TEST PING"; //Construct the request 
             object 
             vReq = RpcRequestFactory.getRpcRequest(rpcContext, rpcName); 
             //Execute the Rpc and get the response 
             vResp = myConnection.executeRPC(vReq); //Work with the 
             response...  
     
          RpcRequestParams 
             Represents the collection of parameters associated with an 
             RPC.  
     
          RpcResponse 
             Represents a data structure which holds the response value(s).  
     
       Exception Summary 
       =================
          NoRpcContextFaultException 
             This exception represents the case where the request RPC 
             context does not exist or the current user does not have 
             access to the B-option representing the context.  
     
          RpcFaultException 
             This fault exception class is used for all Rpc-related errors 
             returned from the M system.  
     
          RpcNotInContextFaultException 
             This exception represents the case where the requested RPC is 
             not contained in the current RPC context.  
     
          RpcNotOkForProxyUseException 
             This exception represents the case where the requested RPC is 
             not marked as OK for use by an application proxy user, but has 
             been attempted to be invoked by one.  
     
          RpcResponseTypeIsNotXmlException 
             Represents an exception indicating the RpcResponse type if not 
             XML.  
     
          RpcTimeOutFaultException 
             This exception represents the case where the RPC execution 
             took too long on the server and the application gracefully 
             stopped the RPC's processing.  
  
  
    Package gov.va.med.vistalink.institution 
    ========================================
       Foundations utilities for working with VistaLink-related Institution 
       data.  
     
       Class Summary 
       =============
          InstitutionMappingDelegate 
             The in-memory mapping is initialized during connector startup.  
     
       Exception Summary 
       =================
          InstitutionMapNotInitializedException 
             Represents an attempt to access some functionality of the 
             InstitutionMappingImpl instance when that instance has not 
             been created.  
     
          InstitutionMappingNotFoundException 
             Represents a failure to retrieve an institution mapping based 
             on station number, due to requested station number not being 
             found in the list of instituion mappings maintained by the 
             InstitutionMappingImpl instance.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
KEYWORDS: VISTALINK SECURITY
  DATE ACTIVATED: MAR 06, 2007

NUMBER: 4149                            IA #: 4149
  DATE CREATED: JUL 03, 2003            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MXMLPRSE
  NAME: M XML EVENT-DRIVEN API          ID: MXMLPRSE
 GENERAL DESCRIPTION:   An event-driven interface that is modeled after the
 widely used SAX interface specification.  In this implementation, a client
 application provides a special handler for each parsing event of interest. 
 When the client invokes the parser, it conveys not only the document to be
 parsed, but also the entry points for each of its event handlers.  As the
 parser progresses through the document, it invokes the client's handlers for 
 each parsing event for which a handler has been registered.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN(DOC,CBK,OPT)
VARIABLES: DOC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is 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: CBK                          TYPE: Both
 VARIABLES DESCRIPTION:   This is a local array, passed by reference, that
 contains a list of parse events and the entry points for the handlers of those
 events.  The format for each entry is: 
  
     CBK(<event type>) = <entry point> 
  
 The entry point must reference a valid entry point in an existing M routine
 and should be of the format tag^routine.  The entry should not contain any
 formal parameter references.  The application developer is responsible for
 ensuring that the actual entry point contains the appropriate number of formal
 parameters for the event type.  For example, client application might register
 its STARTELEMENT event handler as follows: 
  
     CBK("STARTELEMENT") = "STELE^CLNT" 
  
 The actual entry point in the CLNT routine must include two formal parameters
 as in the example: 
  
     STELE(ELE,ATR)   <handler code> 
  
 See full documentation for event types.  Documentation at: 
  http://www.va.gov/vdl/VistA_Lib/Infrastructure/Kernel_Toolkit/KTK7_3p58.p df 
VARIABLES: OPT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a list of option flags that control parser
 behavior.  Recognized option flags are: 
  
  W = Do not report warnings to the client.  
  
  V = Validate the document.  If not specified, the parser only checks for
 conformance.  
  
  0 = Terminate parsing on encountering a warning.  
  
  1 = Terminate parsing on encountering a validation error.  (By default, the
 parser terminates only when a conformance error is encountered.) 

NUMBER: 4150                            IA #: 4150
  FILE NUMBER: 9002313.56               GLOBAL ROOT: BPS(9002313.56
  DATE CREATED: FEB 26, 2007            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: STORE POINTERS TO BDP PHARMACYS
  ID: BPS(9002313.56
GLOBAL REFERENCE: BPS(9002313.56
FIELD NUMBER: .01                       FIELD NAME: NAME
  ACCESS: Pointed to
 FIELD DESCRIPTION:   Pointers to BPS Pharmacies file (#9002313.56) in IB file
 #366.14 
 GENERAL DESCRIPTION:   Integrated Billing requests to be able to store
 pointers to BPS Pharmacies file (#9002313.56) in IB file #366.14.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4151                            IA #: 4151
  DATE CREATED: JUL 30, 2003            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PRCLOP4
  NAME: CoreFLS/Legacy Software Shut Down Status Check
  ID: PRCLOP4
 GENERAL DESCRIPTION:   As the legacy software packages IFCAP, Engineering
 (AEMS/MERS) and Equipment/Turn-In Request are converted to Read-Only
 functionality, data conversions are started and then CoreFLS comes on-line for
 each site, a new PRCL LSSD SHUTDOWN STATUS parameter in VistA will be updated. 
 The API described below will enable other packages to check its value, perhaps
 directing the flows their software execution on the basis of it.  For example,
 the IFCAP interface partners might continue to use APIs to IFCAP code if IFCAP
 is fully functional and switch to use APIs to the Communications Service
 Library (CSL) code if CoreFLS is on-line.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COREFLS
KEYWORDS: LEGACY SOFTWARE SHUT DOWN
COMPONENT/ENTRY POINT: SYS
 COMPONENT DESCRIPTION:   Format of call: $$SYS^PRCLOP4.  The returned value of
 the extrinsic function is one of the following codes: 
  
      0 : SYSTEM IS ENABLED   (IFCAP, Engineering, and Equipment/Turn-In 
 Request are fully enabled. Read/Write/Delete) 
  
      1 : SYSTEM IS SHUT DOWN (IFCAP, Engineering, and Equipment/Turn-In 
 Request are Read-Only.) 
  
      2 : COREFLS CONVERSION COMPLETE (IFCAP, Engineering, and 
 Equipment/Turn-In Request are Read-Only and data conversions for CoreFLS 
 implementation are completed.) 
  
      3 : COREFLS ONLINE      (IFCAP, Engineering, and Equipment/Turn-In 
 Request are Read-Only and new business must be entered into CoreFLS.) 
  
 The calling application should first check for the existence of this API 
 before referencing it.  For example: 
     S X="PRCLOP4" X ^%ZOSF("TEST") I $T,$$SYS^PRCLOP4=3  MUMPS code 
  
 This approach will enable calling applications to install changes to their
 software before the Legacy Software Shut Down patch PRC*5.1*65 is installed.  

NUMBER: 4152                            IA #: 4152
  DATE CREATED: FEB 28, 2007            CUSTODIAL PACKAGE: 759
  USAGE: Controlled Subscription        TYPE: Other
  NAME: Person Service Lookup java components
 GENERAL DESCRIPTION:   Person Service Lookup includes components necessary to
 support the search and retrieval operations for patient and provider lookups
 for both web and swing versions.  PSL components include both a web and java 
 swing-based GUI application client to be used within a consuming host 
 application.  These GUI components represent the API for consuming 
 applications that must embed the GUI Person Service Lookup Client components
 into the design of their application.  GUI PSL components internally use CAIP
 (Cross Application Integration Protocol) delegate to access PSL services
 needed to perform a lookup.  
  
 PSL provider lookup components do not include any GUI components.  The 
 provider lookup API consists of a CAIP provider lookup delegate class that is
 intended for programmatic access from a consuming application.  
  
 PSL Services will be deployed both nationally and locally.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: plu_patient_interface.do
 COMPONENT DESCRIPTION:   When consuming a web-based application service within
 a J2EE architecture, the host application needs to provide a JSP page for the 
 service to present in.  The host JSP that is the application's web page 
 instantiates the interface JSP.  It is recommended that this be done as an
 iframe.  This provides the service JSP with the ability to function 
 independently from the host application while appearing as though it were part
 of the host application.  
VARIABLES: Security Type                TYPE: Input
 VARIABLES DESCRIPTION:   VistALink supports two types of security.  This value
 determines what method of security to use when connecting to the M database
 with VistALink.  Acceptable values are DUZ and VPID.  
VARIABLES: UserCredential               TYPE: Input
 VARIABLES DESCRIPTION:   This contains the DUZ or the VPID value that is
 required by VistALink.  
VARIABLES: SiteIdentifier               TYPE: Input
 VARIABLES DESCRIPTION:   This value identifies the VistA site.  
VARIABLES: DivisionIdentifier           TYPE: Input
 VARIABLES DESCRIPTION:   Required by VistALink.  If undefined it will use the
 default Division for the facility.  If more than one division is defined for a
 user, then an error will occur.  
VARIABLES: SiteOfInterest               TYPE: Input
 VARIABLES DESCRIPTION:   This value identifies the VistALink database to be
 used.  
VARIABLES: ForwardToPage                TYPE: Input
 VARIABLES DESCRIPTION:   This is the URL address of the consuming
 application's forward to page.  This URL will be used to forward the request
 upon PS Lookup exit.  
VARIABLES: PatientLookupBean            TYPE: Output
 VARIABLES DESCRIPTION:   ICN = Integration Control Number assigned by the MPI
 or local ICN.  
    
 DFN = Internal entry number in Patient (#2) file or unique identifier of the
 patient on the local M system.  
  
 SiteName = The name of the Institution for the database where the patient was
 accessed.  
  
 SiteNumber = This is the station number including suffixes for the database
 where the patient was accessed.  
  
 ProductionDatabase = String value indicating if the database is a production
 database.  
  
 Domain = M database domain returned by Kernel.  
  
 FullName = Full name of patient from Patient (#2) file.  
  
 FirstName = First name of patient 
  
 LastName = Last name of patient 
  
 MiddleInitial = Middle initial of patient 
  
 NamePrefix = Prefix of patient 
  
 NameSuffix = Suffix of patient 
  
 NameDegree = Degree of the patient 
  
 Gender = Gender of the patient (M or F) 
  
 DOBTrueValue = Date of birth for the patient in MM/DD/YY format.  
  
 DOB = Date of Birth displayed in patient lookup prior to selection.  This 
 value may be set to "Sensitive".  
  
 SSNTrueValue = Social Security Number of patient.  Pseudo SSNs end with a "P"
 and are returned without modification.  
  
 SSN = Social Security Number of the patient that is displayed prior to patient
 selection.  This value may be changed to "Sensitive".  
  
 isSensitiveRecord = String representing the Boolean value indicating whether
 this is a sensitive patient or not.  Returned values are true or false.  
  
 isServiceConnected = String represents the Boolean value indicating whether
 this    patient is service connected or not.  Returned values are true or
 false.  
  
 SCPercent = String value of the integer data representing the service 
 connected percentage of the patient.  
  
 isVeteran = String representing the Boolean value indicating whether this 
 patient is a veteran or not.  Returned values are true or false.  
  
 PrimaryEligibility = This is the Print Name data element from the MAS 
 Eligibility Code (#8.1) file for the primary eligibility code of the patient. 
  
 RoomBed = Text of room/bed if an inpatient.  
  
 TypeOfPatient = Name of the type of patient from Type of Patient (#391) file.  
  
 Ward = Name of ward from Ward Location (#42) file if an inpatient.  
  
 PCProvider = PCP name, VPID and IEN.  
  
 List of Alerts = The PatientLookupBean also includes an ArrayList of all the
 alert notification statuses for a given patient.  This ArrayList includes an
 AlertVO for each of the alert notifications for the patient represented within
 the PatientLookupBean.  
COMPONENT/ENTRY POINT: iPLUManager
 COMPONENT DESCRIPTION:   The main vehicle employed by the swing version of PSL
 in order to communicate with the host application that needs to perform a
 lookup operation is a Java class called the PLUManager.  This class is a 
 singleton that is capable of instantiating itself through a static method 
 called getPLUManager.  The host application is responsible for populating a
 Java Bean which implements IUserBean interface and placing it within the
 PLUManager by invoking the setUserBean method.  
  
 In addition, the host application must provide the PLUManager with a parent
 JFrame object which will be used to control the modality of the dialogs that
 are used to perform a patient lookup by calling setParentFrame on PLUManager.  
VARIABLES: SecurityType                 TYPE: Input
 VARIABLES DESCRIPTION:   VistALink supports two types of security.  This value
 determines what method of security to use when connecting to the M database
 with VistALink.  Acceptable values are DUZ and VPID.  
VARIABLES: UserCredential               TYPE: Input
 VARIABLES DESCRIPTION:   This contains the DUZ or the VPID value that is
 required by VistALink.  
VARIABLES: SiteIdentifier               TYPE: Input
 VARIABLES DESCRIPTION:   This value identifies the VistA site.  
VARIABLES: DivisionIdentifier           TYPE: Input
 VARIABLES DESCRIPTION:   Required by VistALink.  If undefined it will use the
 default Division for the facility.  If more than one division is defined for a
 user, then an error will occur.  
VARIABLES: SiteOfInterest               TYPE: Input
 VARIABLES DESCRIPTION:   This value identifies the VistALink database to be
 accessed.  
VARIABLES: ForwardToPage                TYPE: Input
 VARIABLES DESCRIPTION:   This is the URL address of the consuming
 application's forward to page.  This URL will be used to forward the request
 upon PS Lookup exit.  
VARIABLES: PatientLookupBean            TYPE: Output
 VARIABLES DESCRIPTION:   ICN = Integration Control Number assigned by the MPI
 or local ICN.  
    
 DFN = Internal entry number in Patient (#2) file or unique identifier of the
 patient on the local M system.  
  
 SiteName = The name of the Institution for the database where the patient was
 accessed.  
  
 SiteNumber = This is the station number including suffixes for the database
 where the patient was accessed.  
  
 ProductionDatabase = String value indicating if the database is a production
 database.  
  
 Domain = M database domain returned by Kernel.  
  
 FullName = Full name of patient from Patient (#2) file.  
  
 FirstName = First name of patient 
  
 LastName = Last name of patient 
  
 MiddleInitial = Middle initial of patient 
  
 NamePrefix = Prefix of patient 
  
 NameSuffix = Suffix of patient 
  
 NameDegree = Degree of the patient 
  
 Gender = Gender of the patient (M or F) 
  
 DOBTrueValue = Date of birth for the patient in MM/DD/YY format.  
  
 DOB = Date of Birth displayed in patient lookup prior to selection.  This 
 value may be set to "Sensitive".  
  
 SSNTrueValue = Social Security Number of patient.  Pseudo SSNs end with a "P"
 and are returned without modification.  
  
 SSN = Social Security Number of the patient that is displayed prior to patient
 selection.  This value may be changed to "Sensitive".  
  
 isSensitiveRecord = String representing the Boolean value indicating whether
 this is a sensitive patient or not.  Returned values are true or false.  
  
 isServiceConnected = String represents the Boolean value indicating whether
 this    patient is service connected or not.  Returned values are true or
 false.  
  
 SCPercent = String value of the integer data representing the service 
 connected percentage of the patient.  
  
 isVeteran = String representing the Boolean value indicating whether this 
 patient is a veteran or not.  Returned values are true or false.  
  
 PrimaryEligibility = This is the Print Name data element from the MAS 
 Eligibility Code (#8.1) file for the primary eligibility code of the patient. 
  
 RoomBed = Text of room/bed if an inpatient.  
  
 TypeOfPatient = Name of the type of patient from Type of Patient (#391) file.  
  
 Ward = Name of ward from Ward Location (#42) file if an inpatient.  
  
 PCProvider = PCP name, VPID and IEN.  
  
 List of Alerts = The PatientLookupBean also includes an ArrayList of all the
 alert notification statuses for a given patient.  This ArrayList includes an
 AlertVO for each of the alert notifications for the patient represented within
 the PatientLookupBean.  
COMPONENT/ENTRY POINT: ICN/DFN Search (swing)
 COMPONENT DESCRIPTION:   Both the web and Java swing-based versions of PS
 Lookup include support for a programmatic ICN and DFN search capability.  When
 a programmatic search is performed, PS Lookup displays any patient alert
 status notifications before returning a PatientLookupBean to the consuming 
 application.  
  
 In both the web and the Java swing-based versions of PS Lookup it is necessary
 to furnish PS Lookup with the user credentials for accessing the patient data
 from the VistA system and the ICN or DFN of the patient to be accessed.  In
 addition, the swing version requires that the parent frame of the host
 application be provided so that all alert notification dialogs displayed to
 the user are shown modally relative to this parent frame.  
  
 Swing version:  The user credentials and the parent frame must be set using
 the methods provided by the IPLUManager interface.  The ICN/DFN search is
 performed by calling getPatient( ) method of IPLUManager.  
VARIABLES: SearchType                   TYPE: Input
 VARIABLES DESCRIPTION:   The SearchType must be "ICN" or "DFN".  
VARIABLES: searchValue                  TYPE: Input
 VARIABLES DESCRIPTION:   The searchValue contains the Integration Control
 Number (ICN) or the DFN, internal entry number in the Patient (#2) file, for
 the patient.  
COMPONENT/ENTRY POINT: ICN/DFN Search (web)
 COMPONENT DESCRIPTION:   Both the web and Java swing-based versions of PS
 Lookup include support for a programmatic ICN and DFN search capability.  When
 a programmatic search is performed, PS Lookup displays any patient alert
 status notifications before returning a PatientLookupBean to the consuming 
 application.  
  
 In both the web and the Java swing-based versions of PS Lookup it is necessary
 to furnish PS Lookup with the user credentials for accessing the patient data
 from the VistA system and the ICN or DFN of the patient to be accessed.  In
 addition, the swing version requires that the parent frame of the host
 application be provided so that all alert notification dialogs displayed to
 the user are shown modally relative to this parent frame.  
  
 Web version:  It is necessary to place the user credentials and the desired
 ICN/DFN within the user's HttpSession.  When a lookup is performed, the
 presence of an ICN/DFN search value within the HttpSession is interpreted as a
 request for a specified ICN/DFN. 
VARIABLES: ICN/DFN                      TYPE: Input
 VARIABLES DESCRIPTION:   The value of the ICN or DFN must be set in the
 HttpSession as follows: 
  
 session.setAttribute(IPLUConstants.ICN_SEARCH_VALUE_SESSION_STRING,value of
 ICN) 
  
 session.setAttribute(IPLUConstants.DFN_SEARCH_VALUE_SESSION_STRING,value of
 DFN) 
  
 It is the responsibility of the consuming application to remove this value
 from the HttpSession once the lookup is complete.  
COMPONENT/ENTRY POINT: pl_person_interface.do
 COMPONENT DESCRIPTION:   The Provider Lookup component is designed for use as
 a service that is invoked by requesting the CAIP ProviderLookupDelegate class
 to perform a lookup.  There is no GUI component provided with the Provider
 Lookup component.  The ProviderLookupDelegate method invocation can be viewed
 as a client side invocation if the calling program is on the client.  
 Alternately, this could be viewed as a middle tier service invocation if the
 calling program is a middle tier class.  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   DUZ = Internal Entry Number in New Person (#200)
 file.  
       The string value of the DUZ or User ID of the individual performing 
       the lookup.  
VARIABLES: Division                     TYPE: Input
 VARIABLES DESCRIPTION:   The string value of the Division for the VistA site
 to be accessed.  
VARIABLES: SiteOfInterest               TYPE: Input
 VARIABLES DESCRIPTION:   The string value of the name for the VistA site to be
 accessed.  
VARIABLES: VPID                         TYPE: Input
 VARIABLES DESCRIPTION:   The VPID of the provider for the provider lookup to
 be performed.  If VPID is specified, then the only other lookup criteria used
 is the effective date.  Otherwise, First Name, Last Name, SSN and Station
 Number may be provided.  
VARIABLES: Last Name                    TYPE: Input
 VARIABLES DESCRIPTION:   The last name (or part thereof) of the provider for
 the provider lookup to be performed.  
VARIABLES: First Name                   TYPE: Input
 VARIABLES DESCRIPTION:   The first name (or part thereof) of the provider for
 the provider lookup to be performed.  
VARIABLES: SSN                          TYPE: Input
 VARIABLES DESCRIPTION:   The SSN of the provider for the provider lookup to be
 performed.  
VARIABLES: Station Number               TYPE: Input
 VARIABLES DESCRIPTION:   The Station Number of the provider for the provider
 lookup to be performed.  
VARIABLES: Effective Date               TYPE: Input
 VARIABLES DESCRIPTION:   Contains the date used to determine if person class
 is active.  Defaults to current date.  
VARIABLES: IProviderVO                  TYPE: Output
 VARIABLES DESCRIPTION:   VPID = String value of the unique identifier of the
 provider in the Administrative Data Repository (ADR).  
  
 IEN = String value of the internal entry number of the provider in the local M
 database.  
  
 First Name = String value of the first name of the provider from the New 
 Person (#200) file.  
  
 Middle Name = String value of the middle name of the provider from the New 
 Person (#200) file.     
  
 Last Name = String value of the last name of the provider from the New Person
 (#200) file.  
  
 SSN = String value of the Social Security Number of the provider.  
  
 DOB = String value of the Date of Birth of provider.  
  
 Gender = String value of the gender of the provider.  
          Returned values are F or M.  
  
 Provider Type = String value of the provider type of the provider.  
  
 Classification = String value of the classification of the provider.  
  
 Specialization = String value of the specialization of the provider.  
  
 Specialty Code = String value of the specialty code of the provider.  
  
 VA Code = String value of the VA code of the provider.  
  
 X12 Code = String value of the X12 code of the provider. 
SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM
SUBSCRIBING PACKAGE: INTEGRATED PATIENT FUNDS

NUMBER: 4153                            IA #: 4153
  DATE CREATED: JUL 15, 2003            CUSTODIAL PACKAGE: TOOLKIT
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: MXMLUTL                      NAME: MXMLUTL
  ID: MXMLUTL
 GENERAL DESCRIPTION:   Utility API's to help when building XML messages.  
  STATUS: Active
COMPONENT/ENTRY POINT: $$XMLHDR
 COMPONENT DESCRIPTION:   This extrinsic function returns a standard extensible
 markup language (XML) header for encoding XML messages.  Example: 
         >S X=$$XMLHDR^MXMLUTL 
         >W X 
         <?xml version="1.0" encoding="utf-8" ?> 
COMPONENT/ENTRY POINT: $$SYMENC(str)
 COMPONENT DESCRIPTION:   This extrinsic function replaces reserved XML symbols
 in a string with their XML encoding for strings used in an extensible markup
 language (XML) message.  
  
 Output: Returns the input string with XML encoding replacing reserved XML
 symbols.  
   
 Example: 
  
  >S X=$$SYMENC^MXMLUTL("This line isn't &""<XML>"" safe as is.") 
  >W X 
  This line isn&apos;t &amp;&quot;&lt;XML&gt;&quot; safe as is.  
VARIABLES: str                          TYPE: Input
 VARIABLES DESCRIPTION:   String to be encoded for an XML message.  
  DATE ACTIVATED: MAY 13, 2011

NUMBER: 4154                            IA #: 4154
  FILE NUMBER: 61                       GLOBAL ROOT: LAB(61
  DATE CREATED: JUL 11, 2003            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: FILE 61
  ID: LAB(61
 GENERAL DESCRIPTION:   The Womens Health package requests permission to point
 to the TOPOGRAPHY FIELD (#61) file.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: WOMEN'S HEALTH     ISC: Hines
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4155                            IA #: 4155
  FILE NUMBER: 61.1                     GLOBAL ROOT: LAB(61.1
  DATE CREATED: JUL 11, 2003            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            NAME: FILE 61.1
  ID: LAB(61.1
 GENERAL DESCRIPTION:   The Womens Health package requests permission to point
 to the MORPHOLOGY FIELD (#61.1) file.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: WOMEN'S HEALTH     ISC: Hines
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4156                            IA #: 4156
  DATE CREATED: JUL 21, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGCV
  NAME: COMBAT VETERAN STATUS           ID: DGCV
 GENERAL DESCRIPTION:   As per directive 2002-049 patients who qualify as
 Combat Veterans will be treated for two years after separation even in the
 absence of supporting evidence that their condiditons are combat related. 
 This supported DBIA covers an API that will be used during patient lookups,
 Registration, Billing, Outpatient Pharmacy and treatment checkout that will
 provide whether or not the veteran being processed has been assigned combat 
 status and whether that combat status is still in effect.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$CVEDT(DFN,DGDT)
 COMPONENT DESCRIPTION:   This API will take the DFN as an input parameter.  If
 eligibility is to be determined for a date other than the current date it may
 be entered as an optional input parameter.  Output is whether or not the
 veteran has CV status and if so, the end date of the eligibility.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file IEN 
VARIABLES: DGDT                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional)  The date for which eligiblity is to be
 determined.  
VARIABLES: $$CVEDT                      TYPE: Output
 VARIABLES DESCRIPTION:   This variable is a "^" delimited.  
  
 The first piece is -1/0/1 
         -1 if the determination cannot be made due to a non-valid DFN 
          0 if never given combat veteran eligibility.  
          1 if the veteran was ever given combat veteran eligibility.  
  
 The second piece is the Combat Vet End Date (if ever given eligibility).  
  
 The third piece is 1/0 
          1 if still eligible on the specified date (either passed in to the
 API or TODAY by default), 0 if not.  This piece will be populated only if the
 1st piece is equal to 1.  

NUMBER: 4157                            IA #: 4157
  DATE CREATED: JUL 24, 2003            CUSTODIAL PACKAGE: VDEM
  USAGE: Supported                      TYPE: Routine
  ROUTINE: VDEMCUS1                     NAME: VDEMCUS1
  ID: VDEMCUS1
 GENERAL DESCRIPTION:   VDEM extraction tool utility which contains calls and
 conversion of data from dictionary.  
  STATUS: Withdrawn
KEYWORDS: VDEM
COMPONENT/ENTRY POINT: DIC
 COMPONENT DESCRIPTION:   This entry point is called to retrieve dictionary
 specific data to assist in reformating.  
VARIABLES: DICNUM                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the IENs form dictionary 44, 45.1, 757.01,
 50.6,50.7, 53,100.02 , 101.43 & 8925.1 files.  
VARIABLES: ENTRY                        TYPE: Input
 VARIABLES DESCRIPTION:   This variable is sent from a command in the VDEM
 Controller. The ENTRY defines what a specific point in where a command will
 exicute.  
VARIABLES: VALUE                        TYPE: Both
 VARIABLES DESCRIPTION:   This variable defines the data that exists in the
 called DICNUM varible and will be needed to determine what will be translated.
 When a match is found, variable VALUE will be reset and send back to the
 called routine with a new value.  
COMPONENT/ENTRY POINT: PERCONC
 COMPONENT DESCRIPTION:   This is called by VDEM routines to assist in
 extracting Person Class Data. The routine calls dictionary 8932.1.  
VARIABLES: VALUE                        TYPE: Both
 VARIABLES DESCRIPTION:   This variable is information that is sent from a VDEM
 application which contains person class information. The routine will find
 corresponding data and will add/update/modify the data and send it back in a
 variable called VALUE.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This variable is sent by a VDEM routine and is the
 Internal Entry Number for USC(8932.1,IEN...from this string we are getting the
 3rd peice. This is used to recreate the variable VALUE.  
COMPONENT/ENTRY POINT: GMRVVIT
 COMPONENT DESCRIPTION:   This tag is a custom routine that pulls data from
 Dictionary # 120.52.  
VARIABLES: IEN                          TYPE: Used
 VARIABLES DESCRIPTION:   This is the Internal Entry Number fro Global
 GMRD(120.53,IEN,0) 
VARIABLES: NAME                         TYPE: Used
 VARIABLES DESCRIPTION:   This variable is the Pce 1 from data string in Global
 GMRD(120.53,IEN,0).  
VARIABLES: VITIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   This variable is a Subscript in a global
 GMRD(120.53,IEN,1,VITIEN).  
VARIABLES: VITINDT                      TYPE: Used
 VARIABLES DESCRIPTION:   This variable is a string of data from global
 GMRD(120.53,IEN,1,VITIEN,0).  
VARIABLES: 'VITIN'                      TYPE: Used
 VARIABLES DESCRIPTION:   This varaible is the 1st pce of data from variable
 VITINDT.  
VARIABLES: VITDATA                      TYPE: Used
 VARIABLES DESCRIPTION:   This is a data string that is created from Dictionary
 global 120.51.  The string is dirived from GMRD(120.51,VITIN,0) 
VARIABLES: DEFIEN                       TYPE: Used
 VARIABLES DESCRIPTION:   This variable is a subscript that is used in getting
 data from dictionary (#120.52) 
     ie . GMRD(120.52,DEFIEN,0) 

NUMBER: 4158                            IA #: 4158
  FILE NUMBER: 405.4                    GLOBAL ROOT: DG(405.4
  DATE CREATED: JUL 25, 2003            CUSTODIAL PACKAGE: VDEM
  USAGE: Private                        TYPE: File
  ROUTINE: VDEMRMBD
  NAME: VDEMRMBD Routine Calling File 405.4.
  ID: VDEMRMBD
GLOBAL REFERENCE: DG(405.4,IEN,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DG(405.4,IEN,I,D1,0)
FIELD NUMBER: .01                       FIELD NAME: OUT-OF-SERVICE DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: RETURN TO SERVICE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DG(405.4,D0,W,0)
FIELD NUMBER: .01                       FIELD NAME: WARD(S) WHICH CAN ASSIGN
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA was created becuase of the routine dependancy
 with the Room-Bed file # 405.4. The routine will loop through the file and
 extract data elements of key fields. The data will be used to support the VDEM 
 extraction application.  
  STATUS: Withdrawn
KEYWORDS: VDEM
KEYWORDS: VDEMRMBD
KEYWORDS: ROOM-BED
COMPONENT/ENTRY POINT: START
 COMPONENT DESCRIPTION:   This is the start point of the routine..  
VARIABLES: IEN                          TYPE: Used
 VARIABLES DESCRIPTION:   Internal Entry Number that is used in global
 DG(405.4...  
VARIABLES: WARDIEN2                     TYPE: Used
 VARIABLES DESCRIPTION:   This varaible is for getting data from dictionary
 DIC(42...  
VARIABLES: DESCRIPT                     TYPE: Used
 VARIABLES DESCRIPTION:   This varaible is the IEN for DG(405.6.....  

NUMBER: 4159                            IA #: 4159
  FILE NUMBER: 10                       GLOBAL ROOT: DIC(10
  DATE CREATED: JUL 25, 2003            CUSTODIAL PACKAGE: VDEM
  USAGE: Private                        TYPE: File
  ROUTINE: VDEMRACE                     NAME: VDEMRACE Routine Calling File 10
  ID: VDEMRACE
GLOBAL REFERENCE: DIC(10,IEN,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ABBREVIATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(10,IEN,.01,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SYNONYM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA was created becuase of the routines dependancy
 with the Race file #10. The routine will loop through the file and extract 
 data elements of key fields. The data will be used to support the VDEM
 extraction application.  
  STATUS: Withdrawn
KEYWORDS: VDEM
KEYWORDS: VDEMRACE
KEYWORDS: RACE
COMPONENT/ENTRY POINT: START
VARIABLES: IEN                          TYPE: Used
 VARIABLES DESCRIPTION:   Internal Entry Number for race dictionary 10
 DIC(10.....  

NUMBER: 4160                            IA #: 4160
  FILE NUMBER: 627.9                    GLOBAL ROOT: DIC(627.9
  DATE CREATED: JUL 25, 2003            CUSTODIAL PACKAGE: VDEM
  USAGE: Private                        TYPE: File
  ROUTINE: VDEMDSMM
  NAME: VDEMDSMM Routine Calling file 627.9
  ID: VDEMDSMM
GLOBAL REFERENCE: DIC(627.9,IEN,0)
FIELD NUMBER: .01                       FIELD NAME: ENTRY NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Direct Global Read from the VDEM application 
FIELD NUMBER: 1                         FIELD NAME: PROMPT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(627.9,IEN,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DSM VERSIONS 
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA was created becuase of the routine dependancy
 with the DSM MODIFIER file 627.9. The routine will loop through the file and 
 extract data elements of key fields. The data will be used to support the VDEM
 extraction 
  STATUS: Withdrawn
KEYWORDS: VDEM
KEYWORDS: VDEMDSMM
KEYWORDS: DSM MODIFIER
COMPONENT/ENTRY POINT: START
VARIABLES: IEN                          TYPE: Used
 VARIABLES DESCRIPTION:   Internal Entry Number used as a subscript in
 Dictionary global DIC(627.9, IEN.......  

NUMBER: 4161                            IA #: 4161
  DATE CREATED: JUL 25, 2003            CUSTODIAL PACKAGE: VDEM
  USAGE: Supported                      TYPE: Routine
  ROUTINE: VDEMVITL                     NAME: VDEMVITL
  ID: VDEMVITL
 GENERAL DESCRIPTION:   This IA was created to address the dictionary
 references (#120.51), (#120.52), (#120.53), (#126.56) & (#126.8) 
  STATUS: Withdrawn
KEYWORDS: VDEM
COMPONENT/ENTRY POINT: VITAL1
VARIABLES: IEN                          TYPE: Used
 VARIABLES DESCRIPTION:   This is a Internal Entry Number for
 GMRD(120.52,IEN.....  
VARIABLES: TYPE                         TYPE: Used
 VARIABLES DESCRIPTION:   This is a Internal Entry Number for ^GMRD(120.51,TYPE 
VARIABLES: CAT                          TYPE: Used
 VARIABLES DESCRIPTION:   This is a Internal Entry Number for
 $G(^GMRD(120.53,CAT.....  
COMPONENT/ENTRY POINT: VITAL2
VARIABLES: IEN                          TYPE: Used
 VARIABLES DESCRIPTION:   This is a Internal Entry Number for
 GMRD(126.8,IEN.....  
VARIABLES: INPUT                        TYPE: Used
 VARIABLES DESCRIPTION:   This is a Internal Entry Number for
 GMRD(126.56,INPUT......  

NUMBER: 4162                            IA #: 4162
  FILE NUMBER: 120.83                   GLOBAL ROOT: GMRD(120.83
  DATE CREATED: JUL 25, 2003
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: File
  ROUTINE: VDEMSIGN
  NAME: VDEMSIGN Routine Calling File 120.83
  ID: VDEMSIGN
GLOBAL REFERENCE: GMRD(120.83,IEN,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: NATIONAL SIGN/SYMPTOM
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: GMRD(120.83,IEN,2,D1,0
FIELD NUMBER: .01                       FIELD NAME: SYNONYM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA is defined to address issues from dictionary
 (#120.83) 
  STATUS: Withdrawn
KEYWORDS: VDEM
KEYWORDS: VDEMSIGN
COMPONENT/ENTRY POINT: START
VARIABLES: IEN                          TYPE: Used
 VARIABLES DESCRIPTION:   This is a Internal Entry Number for
 GMRD(120.83,IEN......  

NUMBER: 4163                            IA #: 4163
  DATE CREATED: JUL 29, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: TIUPXPM                      NAME: DBIA4163
  ID: TIUPXPM                           STATUS: Active
KEYWORDS: PROGRESS NOTES
COMPONENT/ENTRY POINT: $$PM
 COMPONENT DESCRIPTION:   Scheduling calls this API ($$PM^TIUPXPM) in order to
 determine if a progress note has been signed/co-signed/amended, properly 
 signed/co-signed/amended, and date signed.  This is done on a visit by visit
 basis.  
  
 Based upon the VISIT IEN, the API shall match records to appropriate TIU 
 DOCUMENT entries in file # 8925 and shall return back to the Scheduling 
 package the information on whether the VISIT IEN has an associated Progress
 Note (or Addendum) signed by the appropriate provider for that encounter and
 shall return the Note Category, Signed By, Signed By Date/Time, Co-Signed By,
 Co-Signed By Date/Time data back to the PIMS package.  
  
 Sample use 
 -------------
  
 S VIEN=$P(^SCE(PTRENC,0),U,5) 
  
 S NOTEINFO=$$PM^TIUPXPM(VIEN) 
VARIABLES: VIEN                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to visit file (9000010) 
VARIABLES: $$PM                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns: 
  
      String with 6 fields ('^' delimiter) 
       1  VIEN 
       2  Note Category (A-E) 
       3  Signed By (pointer to File #200) 
       4  Signed Date.Time (FM format) 
       5  Co-signed By (pointer to File #200) - defined only if necessary 
       6  Co-signed Date.Time - defined only if necessary    
  
 Categories 
  
       Note  Status                          Cat 
  ---------------------------               -------
  No note for the Visit IEN                    A 
  Acceptable Note                              B 
  Unacceptable Note                            C 
  Scanned Image                                D 
  Purged, Deleted, or Retracted note           E 
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 4164                            IA #: 4164
  DATE CREATED: JUL 29, 2003            CUSTODIAL PACKAGE: TOOLKIT
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XPARDD                       NAME: XPARDD
  ID: XPARDD
 GENERAL DESCRIPTION:   The HealtheVet Desktop allows the setting and changing
 of parameter values that control its behavior from within the application
 itself; since this is a GUI application it must do its own presentation and
 thus needs access to some lower-level calls to manipulate those values.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$EXT(X,PAR,FLD)
 COMPONENT DESCRIPTION:   Returns the external form of either a parameter value
 or instance.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   Internal form of the value.  
VARIABLES: PAR                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN from the Parameter Definition file #8989.51 
VARIABLES: FLD                          TYPE: Input
 VARIABLES DESCRIPTION:   Flag indicating type of value passed in X, (I)nstance
 or (V)alue; if this field is left empty, "V" will be the default used.  
VARIABLES: $$EXT                        TYPE: Output
 VARIABLES DESCRIPTION:   The external form of X based on the parameter and
 field specified.  
SUBSCRIBING PACKAGE: HEALTHEVET DESKTOP
  ISC: Salt Lake City

NUMBER: 4165                            IA #: 4165
  DATE CREATED: JUL 29, 2003            CUSTODIAL PACKAGE: TOOLKIT
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XPARLIST                     NAME: XPARLIST
  ID: XPARLIST
 GENERAL DESCRIPTION:   The HealtheVet Desktop allows the setting and changing
 of parameter values that control its behavior from within the application
 itself; since this is a GUI application it must do its own presentation and
 thus needs access to some lower-level calls to manipulate those values.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$ENTNAME
 COMPONENT DESCRIPTION:   Returns the type and external name of a parameter
 entity in the form TYPE: NAME, for example "PKG: PARAMETER TOOLS" 
VARIABLES: ENT                          TYPE: Input
 VARIABLES DESCRIPTION:   Parameter entity in variable-pointer format 
VARIABLES: $$ENTNAME                    TYPE: Output
 VARIABLES DESCRIPTION:   The 'TYPE: NAME' of the requested entity.  
SUBSCRIBING PACKAGE: HEALTHEVET DESKTOP
  ISC: Salt Lake City

NUMBER: 4166                            IA #: 4166
  DATE CREATED: JUL 30, 2003
  CUSTODIAL PACKAGE: CLINICAL CASE REGISTRIES
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: RORAPI01                     NAME: RORAPI01
  ID: RORAPI01
 GENERAL DESCRIPTION:   This agreement documents the use of entry points in
 routine RORAPI01 to get lists of patients from the Clinical Case Registries.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$PATITER
 COMPONENT DESCRIPTION:   Creates an iterator of patients in the specified
 registry.  
VARIABLES: IDESC                        TYPE: Both
 VARIABLES DESCRIPTION:   A local variable, passed in by reference, where the
 iterator descriptor will be created and returned.  
VARIABLES: REGNAME                      TYPE: Input
 VARIABLES DESCRIPTION:   Registry Name.  
VARIABLES: MODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Bit flag to determine iteration mode, where 1 =
 Active patients or 2 = Inactive patients (default = both active and inactive
 if null).  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULT=$$PATITER^RORAPI01(.IDESC,REGNAME,MODE) where
 RESULT is 0 if the iterator was successfully created, or <0 if an error
 occurred.  
COMPONENT/ENTRY POINT: $$NEXTPAT
 COMPONENT DESCRIPTION:   Returns the next patient in the registry.  
VARIABLES: IDESC                        TYPE: Both
 VARIABLES DESCRIPTION:   Reference to the patient iterator descriptor created
 by $$PATITER.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULT=$$NEXTPAT^RORAPI01(.IDESC) where RESULT is
 PatientIEN^InactiveDate, or "" if there are no more patients or <0 if an error
 occurred.  
COMPONENT/ENTRY POINT: $$REGITER
 COMPONENT DESCRIPTION:   Creates an iterator of the patient registries.  
VARIABLES: IDESC                        TYPE: Both
 VARIABLES DESCRIPTION:   A local variable, passed in by reference, where the
 iterator descriptor will be created and returned.  
VARIABLES: PATIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: MODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Bit flag to determine iteration mode, where 1 =
 Active patients or 2 = Inactive patients (default = both active and inactive
 if null) 
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULT=$$REGITER^RORAPI01(.IDESC,PATIEN,MODE) where
 RESULT is 0 if the iterator was successfully created, or <0 if an error
 occurred.  
COMPONENT/ENTRY POINT: $$NEXTREG
 COMPONENT DESCRIPTION:   Returns the next registry for the patient.  
VARIABLES: IDESC                        TYPE: Both
 VARIABLES DESCRIPTION:   Reference to the patient iterator descriptor created
 by $$REGITER.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULT=$$NEXTREG^RORAPI01(.IDESC) where RESULT is
 RegistryIEN^Inactive Date, or "" if there are no more registries for the
 patient or <0 if an error occurred.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4167                            IA #: 4167
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100,
  DATE CREATED: JUL 30, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Care Mgt access to OR(100       ID: OR(100,
GLOBAL REFERENCE: OR(100,D0,0)
FIELD NUMBER: .02                       FIELD NAME: OBJECT OF ORDER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Patient IEN 
FIELD NUMBER: 21                        FIELD NAME: START DATE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Start Date.Time of order 
FIELD NUMBER: 12                        FIELD NAME: PACKAGE
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Package file IEN 
GLOBAL REFERENCE: OR(100,D0,3)
FIELD NUMBER: 5                         FIELD NAME: STATUS
  LOCATION: 3;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 30                        FIELD NAME: CURRENT ACTION
  LOCATION: 3;7                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,D0,4)
FIELD NUMBER: 33                        FIELD NAME: PACKAGE REFERENCE
  LOCATION: 4;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,D0,6)
FIELD NUMBER: 66                        FIELD NAME: COMPLETED
  LOCATION: 6;6                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,D0,7)
FIELD NUMBER: 71                        FIELD NAME: RESULTS DATE/TIME
  LOCATION: 7;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 72                        FIELD NAME: ABNORMAL RESULTS
  LOCATION: 7;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 73                        FIELD NAME: FINDINGS
  LOCATION: 7;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,D0,8,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME ORDERED
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PROVIDER
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: DATE/TIME NURSE VERIFIED
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,'ARS',
 GLOBAL DESCRIPTION:   Index to return orders with results 
GLOBAL REFERENCE: OR(100,'AS',
 GLOBAL DESCRIPTION:   Index to return unsigned orders 
 GENERAL DESCRIPTION:   This documents the Care Management application's use of
 the Orders file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   LR*5.2*504 accesses the RESULTS DATE/TIME field in File
 100 to help debug a patient safety issue where anatomic pathology alerts are
 not being sent to recipients.  

NUMBER: 4168                            IA #: 4168
  DATE CREATED: JUL 30, 2003            CUSTODIAL PACKAGE: VDEM
  USAGE: Private                        TYPE: File
  ROUTINE: VDEMORDR                     NAME: VDEMORDR Routine calling File 
  ID: VDEMORDR
 GENERAL DESCRIPTION:   This routine is used by the VDEM package that will
 reference several dictionary (#100.98), (#101.43), (#60), (#71), (#50.7),
 (#100.01), & (#101.43).  
  STATUS: Withdrawn
KEYWORDS: VDEM
COMPONENT/ENTRY POINT: ORDITEM
VARIABLES: IEN                          TYPE: Used
 VARIABLES DESCRIPTION:   Internal Entry Number that is the subscript from
 ORD(101.43,IEN...  
VARIABLES: PCKNAME                      TYPE: Used
 VARIABLES DESCRIPTION:   Created from PACK1. It is the Direct IEN global
 references ^LAB(60,PACK1..  , ^RAMIS(71,PACK1..., ^PS(50.7,PACK1... &
 ^ORD(101.43,PACK1.....  
COMPONENT/ENTRY POINT: DISGRP
VARIABLES: IEN                          TYPE: Used
 VARIABLES DESCRIPTION:   Internal Entry Number for global reference
 ^ORD(101.98,IEN....  
COMPONENT/ENTRY POINT: ORDSTAT
 COMPONENT DESCRIPTION:   Calls to dictionary reference ^ORD(100.01..  
VARIABLES: IEN                          TYPE: Used
 VARIABLES DESCRIPTION:   Internal Entry Number that is the subscript from
 ORD(100.01,IEN....  

NUMBER: 4169                            IA #: 4169
  FILE NUMBER: 50.3                     GLOBAL ROOT: PS(50.3,IEN
  DATE CREATED: JUL 30, 2003            CUSTODIAL PACKAGE: VDEM
  USAGE: Private                        TYPE: File
  ROUTINE: VDEMPDRG                     NAME: VDEMPDRG Routine Calling File 50.3
  ID: VDEMPDRG
GLOBAL REFERENCE: PS(50.3,IEN,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DEA, SPECIAL HANDLING
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: MESSAGE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(50.3,IEN,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: APPLICATION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE:  PS(50.3,IEN,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SYNONYM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA was created becuase  of the routines dependancy
 with the PRIMARY DRUG File 50.3. The routine will loop through the file and
 extract data elements of key fields. The data will be used to support the VDEM
 extraction application.  
  STATUS: Withdrawn
KEYWORDS: VDEM
KEYWORDS: VDEMPDRG
COMPONENT/ENTRY POINT: START
VARIABLES: IEN                          TYPE: Used
 VARIABLES DESCRIPTION:   Internal Entry Number for subscript in global
 ^PS(50.3,IEN...  
VARIABLES: APLET                        TYPE: Used
 VARIABLES DESCRIPTION:   Subscript in global reference ^PS(50.35,APLET.....  
VARIABLES: MEDRTNME                     TYPE: Used
 VARIABLES DESCRIPTION:   This is created from ^PS(51.2,IEN....  

NUMBER: 4170                            IA #: 4170
  DATE CREATED: JUL 30, 2003            CUSTODIAL PACKAGE: CARE MANAGEMENT
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORRCACK                      NAME: ADD~ORRCACK
  ID: ORRCACK
 GENERAL DESCRIPTION:   This agreement documents the user of ADD^ORRCACK by
 OE/RR to create stubs in the Order Acknowledgments file when order results
 come in.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ADD
 COMPONENT DESCRIPTION:   Creates a new entry in the Order Acknowledgments file
 #102.4 when results become available for an order.  
VARIABLES: ORDER                        TYPE: Input
 VARIABLES DESCRIPTION:   Orders file IEN 
VARIABLES: PROV                         TYPE: Input
 VARIABLES DESCRIPTION:   Provider IEN in #200 
VARIABLES: ACK                          TYPE: Input
 VARIABLES DESCRIPTION:   Bit flag that indicates if the order's results have
 been acknowledged; if set to 1 then an entry must be created in the file to
 hold the acknowledgment, but if null or 0 then the user's activation date for
 the dashboard will determine if an entry is created.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4171                            IA #: 4171
  FILE NUMBER: 123.5                    GLOBAL ROOT: GMR(123.5,
  DATE CREATED: JUL 31, 2003
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: IA 4171 Imaging Consults        ID: GMR(123.5,
GLOBAL REFERENCE: GMR(123.5,
FIELD NUMBER: .01                       FIELD NAME: SERVICE NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   Imaging file 2006.5831 has field named REQUESTED
 SERVICE (#.01) defined as a pointer to file 123.5 (REQUEST SERVICES).  
  
 This allows users to define the services that will be used to build modality
 worklists for that entry/service. The purpose of this file is to link groups
 of types of Request for Consults to entities that Imaging will call worklist
 classes.  
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 03/18/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires read access to File
 123.5, field SERVICE NAME(#.01).  4-Sight II uses the consult service IEN
 already obtained from the consult record TO SERVICE field to resolve the 
 consult service name for display within the 4-Sight II application.  

NUMBER: 4172                            IA #: 4172
  DATE CREATED: AUG 01, 2003
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSSSXRD                      NAME: BUILD CLINICAL REMINDERS INDEX
  ID: PSSSXRD
 GENERAL DESCRIPTION:   This integration agreement grants Clinical Reminders
 the access to call a routine in Pharmacy Data Management to build an index for
 the PHARMACY PATIENT file (#55).  
  STATUS: Active
KEYWORDS: PSSSXRD
COMPONENT/ENTRY POINT: PSPA
 COMPONENT DESCRIPTION:   This call is to build an index to the PHARMACY
 PATIENT file (#55), if a site chooses to use this information for Clinical
 Reminders.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4173                            IA #: 4173
  DATE CREATED: FEB 28, 2007            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  NAME: VistALink J2M Java APIs [vljSecurity-x.x.x.xxx.jar]
 GENERAL DESCRIPTION:   
    This ICR describes the supported VistALink J2M (v1.5) Java APIs for 
    the vljSecurity-x.x.x.xxx.jar file.  
  
    It is strongly recommended that you consult the javadoc for the 
    VistALink J2M software for more detail on all supported VistALink 
    J2M Java APIs.  
  
  
    Jar: 
       vljSecurity-x.x.x.xxx.jar 
  
    Security Packages: 
       gov.va.med.vistalink.security 
       gov.va.med.vistalink.security.m 
  
  
  
    Package gov.va.med.vistalink.security 
    =====================================
       J2SE security module for VistaLink; contains JAAS login module 
       supporting a JAAS client/server login to a Vista M system.  
  
       Class Summary 
       =============
          CallbackHandlerSwing 
             Implements the JAAS CallbackHandler interface.  
     
          CallbackHandlerSwingCCOW 
             Implements the JAAS CallbackHandler interface.  
     
          CallbackHandlerUnitTest 
             Implements the JAAS CallbackHandler interface.  
     
          DialogConfirm 
             Swing Dialog to display an error, informational message, 
             help, or post-sign-in text to user, and collect their response 
             (OK or CANCEL, depending on type of message).  
     
          VistaKernelPrincipalImpl 
             A JAAS principal representing a logged on Kernel user on an M 
             system.  
     
          VistaLoginModule 
             A JAAS-compliant LoginModule to log users on to a Vista 
             system.  
      
       Exception Summary 
       =================
          VistaLoginModuleException 
             Represents a LoginException thrown by the LoginModule.  
     
          VistaLoginModuleIPLockedException 
             If thrown, the user's IP has been locked due to too many times 
             with invalid credentials.  
     
          VistaLoginModuleLoginsDisabledException 
             If thrown, logins are disabled on the M server.  
     
          VistaLoginModuleNoJobSlotsAvailableException 
             If thrown, job slot maximum has been exceeded on M server.  
     
          VistaLoginModuleNoPathToListenerException 
             If thrown, no reachable listener was found on the path 
             represented by the specified IP address and Port.  
     
          VistaLoginModuleTooManyInvalidAttemptsException 
             If thrown, the user tried to login too many times with invalid 
             credentials.  
     
          VistaLoginModuleUserCancelledException 
             Represents a user cancellation of Login.  
     
          VistaLoginModuleUserTimedOutException 
             User timed out of a login.  
     
     
    Package gov.va.med.vistalink.security.m 
    =======================================
       Base Security implementation (J2SE and J2EE).  
     
       Interface Summary 
       =================
          VistaKernelPrincipal 
             Provides an interface to mark a principal that represents a 
             logged on Kernel user on an M system.  
     
       Class Summary 
       =============
          VistaInstitutionVO 
             Represents a Vista Institution, including IEN, Station Name 
             and Station Number.  
     
       Exception Summary 
       =================
          SecurityAccessVerifyCodePairInvalidException 
             Represents an authentication failure during an access/verify 
             code-based re-authentication attempt, where either the access 
             code, verify code (or both) authentication credentials are 
             invalid.  
     
          SecurityConnectionProxyException 
             This exception fault is returned from M, and signifies that 
             the connection proxy used to create the connection was invalid 
             in some way, and a connection could not be established to the 
             EIS.  
     
          SecurityDivisionDeterminationFaultException 
             Represents an authentication failure during a 
             re-authentication attempt, in which an invalid division has 
             been passed for the user on whose behalf re-authentication is 
             being attempted.  
     
          SecurityFaultException 
             This fault exception class is used for all security-related 
             errors returned from the M system.  
     
          SecurityIdentityDeterminationFaultException 
             Represents an authentication failure during a 
             re-authentication attempt, in which the credentials passed for 
             re-authentication (DUZ, VPID, etc.) could not be matched with 
             an actual Kernel user.  
     
          SecurityIPLockedFaultException 
             This exception fault is returned from M, and signifies that 
             the IP address has been locked due to too many invalid 
             logins.user's login credentials were invalid too many times, 
             and the M system is rejecting further login attempts as a 
             result.  
  
          SecurityPrimaryStationMismatchException 
             This exception fault is returned from M, and signifies that 
             there was a mismatch between the client primary station 
             (mapped to the connector) and the primary station of the M 
             account the connector accessed (based on the value of the 
             DEFAULT INSTITUTION field of the Kernel System Parameters 
             file).  
     
          SecurityProductionMismatchException 
             This exception fault is returned from M, and signifies that 
             there was a mismatch between the client and the server in the 
             designation of each side as production or non-production.  
  
          SecurityTooManyInvalidLoginAttemptsFaultException 
             This exception fault is returned from M, and signifies that 
             the user's login credentials were invalid too many times, and 
             the M system is rejecting further login attempts as a result.  
     
          SecurityUserAuthorizationException 
             Represents an authorization failure during a re-authentication 
             attempt, e.g., DISUSER flag is set for the re-authentication 
             user, prohibited times of day is set, etc.  
     
          SecurityUserVerifyCodeException 
             Represents a failure during a re-authentication attempt, where 
             the user's verify code is expired or requires changing.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
KEYWORDS: VISTALINK SECURITY

NUMBER: 4174                            IA #: 4174
  DATE CREATED: AUG 04, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: TIULS                        NAME: APIs in TIULS
  ID: TIULS
 GENERAL DESCRIPTION:   This DBIA documents calls to the routine TIULS that can
 be re-used by subscribing applications.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: WRAP
COMPONENT/ENTRY POINT: NAME
 COMPONENT DESCRIPTION:   This extrinsic function parses and returns person's
 names as specified in a format string.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   This is the person's name in the default format
 <last>,<first> <middle>.  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the format string that determines how the
 name will be formatted.  
  
 Allowable patterns include: 
  
 LAST  = Family (Last) Name FIRST = Given (First) Name LI    = Last Initial FI  
  = First Initial MI    = Middle Initial 
  
 in any combination. Other characters or strings will be treated as delimiters. 
  
 Annotated examples of use: 
 ==========================
  
 In all cases, the input string X will be "WINCHESTER,CHARLES EMERSON III" 
  
 a. To format the result as <first name> <middle initial>. <last name> the 
 format string may be passed as "FIRST MI. LAST" as shown below: 
  
 W $$NAME^TIULS(X,"FIRST MI LAST") 
  
 returns the result: 
  
 CHARLES E. WINCHESTER 
  
 b. To format the result as <last name>, <first initial>.<middle initial>.  the
 format string may be passed as "LAST, FI.MI." as shown below: 
  
 W $$NAME^TIULS(X,"LAST, FI.MI.") 
  
 returns the result: 
  
 WINCHESTER, C.E.  
  
 c. To format the result as <first name> the great physician <last name>! the
 format string may be passed as "FIRST the great physician LAST!" as shown
 below: 
  
 W $$NAME^TIULS(X,"FIRST the great physician LAST!") 
  
 returns the result: 
  
 CHARLES the great physician WINCHESTER! 
COMPONENT/ENTRY POINT: DATE
 COMPONENT DESCRIPTION:   This extrinsic function parses and returns dates (and
 times) as specified in a format string.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   This is a FileMan formatted date [with optional time]
 following the pattern YYYMMDD.HHMMSS (e.g., 3030801.161845 would represent AUG
 01, 2003@16:18:45).  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the format string that determines how the
 date will be formatted.  
  
 Allowable patterns include: 
   
 [Date Format String] (which has these components): 
    AMTH = Alphabetic Month 
    MM   = two-digit numeric Month 
    DD   = two-digit numeric Day of Month 
    CC   = two-digit numeric Century 
    YY   = two-digit numeric Year [Time Format String] (which has these
 components): 
    HR   = two-digit numeric hour 
    MIN  = two-digit numeric minute 
    SEC  = two-digit numeric second 
  
 in any combination. Other characters or strings will be treated as delimiters. 
  
 NOTE: The time format string currently MUST include the "HR" tag in order to
 behave appropriately (i.e., the "MIN" or "SEC" tags, alone or in combination,
 without including the "HR" tag, won't be replaced with their appropriate
 numeric values). This is a newly discovered bug that should be corrected in a
 future patch.  
  
 Annotated examples of use: 
 ==========================
  
 In all cases, the input date X will be 3030801.161845 
  
 a. To format the result as 08/01/03@16:18 the format string may be passed as
 "MM/DD/YY@HR:MIN" as shown below: 
  
 W $$DATE^TIULS(X,"MM/DD/YY@HR:MIN") 
  
 returns the result: 
  
 08/01/03@16:18 
  
 b. To format the result as 01 AUG 2003 the format string may be passed as "DD
 AMTH CCYY" as shown below: 
  
 W $$DATE^TIULS(X,"DD AMTH CCYY")                 
  
 returns the result: 
  
 01 AUG 2003 
  
 c. To format the result as 20030801161845, the format string may be passed as
 "CCYYMMDDHRMINSEC" as shown below: 
  
 W $$DATE^TIULS(X,"CCYYMMDDHRMINSEC") 
  
 returns the result: 
  
 20030801161845 
COMPONENT/ENTRY POINT: WRAP
 COMPONENT DESCRIPTION:   The purpose of this component is to break a text
 string into substrings of a specified length.  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the text string that the subroutine will
 break into substrings.  
VARIABLES: LENGTH                       TYPE: Input
 VARIABLES DESCRIPTION:   The length that should be used to create the
 substrings. In other words, what's the maximum length of each substring.  
SUBSCRIBING PACKAGE: HEALTHEVET DESKTOP
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAY 18, 2023

NUMBER: 4175                            IA #: 4175
  DATE CREATED: AUG 04, 2003
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: TIUSRVP1                     NAME: APIs in TIUSRVP1
  ID: TIUSRVP1
 GENERAL DESCRIPTION:   This IA documents MUMPS-to-MUMPS calls to the routine
 TIUSRVP1, some of which are also documented as RPC-type agreements.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DEFDOC
 COMPONENT DESCRIPTION:   This API returns the default provider as specified by
 the TIU Site Parameter DEFAULT PRIMARY PROVIDER, which has the following
 allowable values: 
   
  0      NONE, DON'T PROMT 
  In which case the call will return 0^ 
   
  1      DEFAULT, BY LOCATION 
  In this case, the call will return the default provider for a given 
  Hospital Location, as specified in the set-up for the Clinic in MAS. If a 
  default provider is specified for the location in question, that person 
  will be returned. If the Clinic set-up specifies use of the Primary 
  Provider (if defined) for the patient, then that person will be returned.  
  The return format will be DUZ^LASTNAME,FIRSTNAME.  
   
  
  2      AUTHOR (IF PROVIDER) 
  In this case, the call will return the current user (if they are a known 
  Provider). If they're not a known Provider, then the call will return 0^.  
VARIABLES: HLOC                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the Hospital Location File (#44).  
VARIABLES: USER                         TYPE: Input
 VARIABLES DESCRIPTION:   Optional Pointer to the New Person File (#200)
 identifying the Author. If nothing is passed, the current user will be
 assumed.  
VARIABLES: TIUIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the Record # (IEN) of the document in the TIU
 DOCUMENT FILE (#8925).  
VARIABLES: TIUDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter identifying the date on which the
 determination of the default provider for the location in question is to be
 made (e.g., a past visit date, etc.). Default in the event that no value is
 passed will be TODAY.  
COMPONENT/ENTRY POINT: $$CANDEL(TIUDA)
 COMPONENT DESCRIPTION:   This API is a Boolean function that evaluates a
 request to delete a document and returns 1 or 0.  
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the document in TIU DOCUMENT
 file (#8925).  [REQUIRED] 
VARIABLES: $$CANDEL                     TYPE: Output
 VARIABLES DESCRIPTION:   
  0 - Document may not be deleted 
  1 - Document may be deleted 
COMPONENT/ENTRY POINT: DOCPARM(.TIUY,TIUDA,TIUTYP)
 COMPONENT DESCRIPTION:   Returns parameters for a document type.  
VARIABLES: TIUY                         TYPE: Both
 VARIABLES DESCRIPTION:   Array passed in by reference, to return data from the
 TIU DOCUMENT PARAMETERS file (#8925.95): 
                              TIUY(0)=0-node of file entry 
                              TIUY(5)=#^#^...^# where # is each entry in 
                                      the Users Requiring Cosignature 
                                      subfile (#8995.955) 
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   The optional variable is the internal entry number of
 a record in the TIU DOCUMENT (#8925) file.  
VARIABLES: TIUTYP                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of TIU DOCUMENT DEFINITION file (#8925.1) 
COMPONENT/ENTRY POINT: SITEPARM(.TIUY)
 COMPONENT DESCRIPTION:   This entry point returns the TIU site parameters for
 a user's division.  
VARIABLES: TIUY                         TYPE: Both
 VARIABLES DESCRIPTION:   This variable is passed by reference and is returned
 as follows: 
  
 TIUY = 0 node of TIU PARAMETERS file (#8925.99) 
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City
SUBSCRIBING PACKAGE: SURGERY            ISC: Birmingham

NUMBER: 4176                            IA #: 4176
  DATE CREATED: JUN 29, 2004
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DISK CONSUMPTION ESTIMATE FOR CLINICAL REMINDERS
 GENERAL DESCRIPTION:   The following global references are made: 
  
   Global          Nodes 
   AUPNVCPT        $P(^AUPNVCPT(0),U,4) 
   AUPNVXAM        $P(^AUPNVXAM(0),U,4) 
   AUPNVHF         $P(^AUPNVXHF(0),U,4) 
   AUPNVIMM        $P(^AUPNVIMM(0),U,4) 
   AUPNVPED        $P(^AUPNVPED(0),U,4) 
   AUPNVPOV        $P(^AUPNVPOV(0),U,4) 
   AUPNVSK         $P(^AUPNVSK(0),U,4) 
   AUPNPROB        $P(^AUPNPROB(0),U,4) 
  STATUS: Active                        DURATION: Next Version
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 4177                            IA #: 4177
  GLOBAL ROOT: DGPT(                    DATE CREATED: JUN 29, 2004
  CUSTODIAL PACKAGE: REGISTRATION       USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DISK CONSUMPTION ESTIMATE FOR CLINICAL REMINDERS
  ID: DGPT(
 GENERAL DESCRIPTION:   The following global references are made: 
  
 Global  Nodes 
  
 DGPT    $O(^DGPT(DA)) 
         $P(^DGPT(DA,0),U,1) 
  
         $O(^DGPT(DA, S ,D1)) 
         $P(^DGPT(DA, S ,D1,0),U,M) 
         M=1,8,9,10,11,12 
  
         $O(^DGPT(DA, P ,D1)) 
         $P(^DGPT(DA, P ,D1,0),U,M) 
         M=1,5,6,7,8,9 
  
         $P(^DGPT(DA,70),U,M) 
         M=10,11,16,17,18,19,20,21,22,23,24 
  
         $O(^DGPT(DA, M ,D1)) 
         $P(^DGPT(DA, M ,D1,0),U,N) 
         N=5,6,7,8,9,10,11,12,13,14,15 
  STATUS: Active                        DURATION: Next Version
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 4178                            IA #: 4178
  FILE NUMBER: 120.5                    GLOBAL ROOT: GMR(120.5,
  DATE CREATED: AUG 05, 2003
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DISK CONSUMPTION ESTIMATE FOR CLINICAL REMINDERS
  ID: GMR(120.5,
GLOBAL REFERENCE: GMR(120.5,0)
FIELD NUMBER: descriptor                FIELD NAME: count of entries
  LOCATION: 4th piece                   ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Next Version
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 4179                            IA #: 4179
  FILE NUMBER: 63                       GLOBAL ROOT: LR(
  DATE CREATED: SEP 29, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DISK CONSUMPTION ESTIMATE FOR CLINICAL REMINDERS
  ID: LR(
 GENERAL DESCRIPTION:   The following global references are made: 
  
 Global  Nodes 
  
 LR (CH)     $O(^LR(LRDFN)) 
             $P(^LR(LRDFN,0),U,2) 
             $O(^LR(LRDFN,"CH",LRIDT)) 
             $P(^LR(LRDFN,"CH",LRIDT,0),U,3) 
             $O(^LR(LRDFN,"CH",LRIDT,LRDN)) 
  
 LR (AP)     $O(^LR(LRDFN)) 
             $P(^LR(LRDFN,0),U,2) 
             $O(^LR(LRDFN,APSUB,LRIDT) 
             APSUB="CY","EM","SP" 
             $P(^LR(LRDFN,APSUB,LRIDT,0),U,M) 
             M=3,6,11 
             $O(^LR(LRDFN,APSUB,LRIDT,.1,SPEC)) 
             $P(^LR(LRDFN,APSUB,LRIDT,.1,SPEC,0),U,1) 
             $O(^LR(LRDFN,APSUB,LRIDT,.1,SPEC,1,PREP)) 
             $O(^LR(LRDFN,APSUB,LRIDT,.1,SPEC,1,PREP,1,TEST)) 
             $P(^LR(LRDFN,APSUB,LRIDT,.1,SPEC,1,PREP,1,TEST,0),U,1) 
  
             $O(^LR(LRDFN,APSUB,LRIDT,3,ICD)) 
             $G(^LR(LRDFN,APSUB,LRIDT,3,ICD,0)) 
  
             $O(^LR(LRDFN,APSUB,LRIDT,2,I)) 
             $G(^LR(LRDFN,APSUB,LRIDT,2,I,0)) 
  
             $O(^LR(LRDFN,APSUB,LRIDT,2,I,SUB,II) 
             SUB=1,2,3,4 
             $G(^LR(LRDFN,APSUB,LRIDT,2,I,SUB,II,0) 
             $O(^LR(LRDFN,APSUB,LRIDT,2,I,SUB,II,1,III)) 
             $G(^LR(LRDFN,APSUB,LRIDT,2,I,SUB,II,1,III,0)) 
  
             $G(^LR(LRDFN,"AU")) 
             $O(^LR(LRDFN,33,SPEC)) 
             $G(^LR(LRDFN,33,SPEC,0)) 
             $O(^LR(LRDFN,80,ICD)) 
             $G(^LR(LRDFN,80,ICD,0)) 
             $O(^LR(LRDFN,"AY",I)) 
             $G(^LR(LRDFN,"AY",I,0)) 
             $O(^LR(LRDFN,"AY",I,SUB,II)) 
             SUB=1,2,3,4 
             $G(^LR(LRDFN,"AY",I,SUB,II,0)) 
             $O(^LR(LRDFN,"AY",I,SUB,II,1,III)) 
             $G(^LR(LRDFN,"AY",I,SUB,II,1,III,0)) 
  
 LR (Micro)  $O(^LR(LRDFN)) 
             $P(^LR(LRDFN,0),U,2) 
             $O(^LR(LRDFN,"MI",LRIDT)) 
             $G(^LR(LRDFN,"MI",LRIDT,0)) 
  
             $O(^LR(LRDFN,"MI",LRIDT,3,ORGNUM)) 
             $G(^LR(LRDFN,"MI",LRIDT,3,ORGNUM,0)) 
             $O(^LR(LRDFN,"MI",LRIDT,3,ORGNUM,ABDN)) 
             $G(^LR(LRDFN,"MI",LRIDT,3,ORGNUM,ABDN)) 
  
             $O(^LR(LRDFN,"MI",LRIDT,SUB)) 
             SUB=5,8,11,16 
             $O(^LR(LRDFN,"MI",LRIDT,SUB+1,ORGNUM)) 
             $G(^LR(LRDFN,"MI",LRIDT,SUB+1,ORGNUM,0)) 
             $O(^LR(LRDFN,"MI",LRIDT,12,ORGNUM,TBDN)) 
             $G(^LR(LRDFN,"MI",LRIDT,12,ORGNUM,TBDN)) 
  STATUS: Active                        DURATION: Next Version
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 4180                            IA #: 4180
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100,
  DATE CREATED: AUG 11, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DISK CONSUMPTION ESTIMATE FOR CLINICAL REMINDERS
  ID: OR(100,
GLOBAL REFERENCE: OR(100,0)
FIELD NUMBER: descriptor                FIELD NAME: count of entries
  LOCATION: 4th piece                   ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Next Version
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 4181                            IA #: 4181
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: JUN 29, 2004
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: File
  NAME: DISK CONSUMPTION ESTIMATE FOR CLINICAL REMINDERS
  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 EMAIL GROUP 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 following global references are made: 
  
 Global   Nodes 
  
 PS(55)   $O(^PS(55,DFN)) 
  
          $O(^PS(55,DFN,5,DA) 
          $P(^PS(55,DFN,5,DA,2),U,M) 
          M=2,4 
          $O(^PS(55,DFN,5,DA,1,DA1)) 
          $P(^PS(55,DFN,5,DA,1,DA1,0),U,1) 
  
          $O(^PS(55,DFN, IV ,DA)) 
          $P(^PS(55,DFN, IV ,DA,0),U,M) 
          M=2,3 
  
          $O(^PS(55,DFN, IV ,DA, AD ,DA1)) 
          ADD=$P(^PS(55,DFN, IV ,DA, AD ,DA1,0),U,1) 
          $P(^PS(52.6,ADD,0),U,2) 
  
          $O(^PS(55,DFN, IV ,DA, SOL ,DA1)) 
          SOL=$P(^PS(55,DFN, IV ,DA, SOL ,DA1,0),U,1) 
          $P(^PS(52.7,SOL,0),U,2) 
  STATUS: Retired                       DURATION: Next Version
  EXPIRATION DATE: DEC 31, 2006
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 4182                            IA #: 4182
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  NAME: DISK CONSUMPTION ESTIMATE FOR CLINICAL REMINDERS
  ID: PSRX(
 GENERAL DESCRIPTION:   The following global references are made: 
  
 Global  Nodes 
  
 PSRX    $O(^PSRX(DA)) 
         $P(^PSRX(DA,0),U,M) 
         M=2,6,8 
         $P(^PSRX(DA,2),U,13) 
  
         $O(^PSRX(DA,1,DA1)) 
         $P(^PSRX(DA,1,DA1,0),U,M) 
         M=10,18 
  
         $O(^PSRX(DA, P ,DA1)) 
         $P(^PSRX(DA, P ,DA1,0),U,M) 
         M=10,19 
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Next Version
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 4183                            IA #: 4183
  FILE NUMBER: 70                       GLOBAL ROOT: RADPT(
  DATE CREATED: AUG 05, 2003
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DISK CONSUMPTION ESTIMATE FOR CLINICAL REMINDERS
  ID: RADPT(
 GENERAL DESCRIPTION:   The following global references are made: 
  
 Global     Nodes 
  
 RADPT      $O(^RADPT(IEN)) 
            $P(^RADPT(IEN,"DT",0),U,4) 
  
  STATUS: Active                        DURATION: Next Version
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 4184                            IA #: 4184
  FILE NUMBER: 9.7                      GLOBAL ROOT: XPD(9.7,
  DATE CREATED: OCT 22, 2004            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: KIDS Install Start/Complete Times
  ID: XPD(9.7,
GLOBAL REFERENCE: XPD(9.7,XPDA,1)
FIELD NUMBER: 11                        FIELD NAME: INSTALL START TIME
  LOCATION: 1;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the time the install started 
FIELD NUMBER: 17                        FIELD NAME: INSTALL COMPLETE TIME
  LOCATION: 1;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the time the install finished 
 GLOBAL DESCRIPTION:   This file contains the installation information for a
 site from the Kernel Installation & Distribution System (KIDS).  This file is
 updated when a KIDS Distribution is installed at a site.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LEXICON
KEYWORDS: KIDS
SUBSCRIBING PACKAGE: LEXICON UTILITY    ISC: Salt Lake City
 SUBSCRIBING DETAILS:   The Lexicon needs to use the Kernel's KIDS variable
 XPDA to retrieve the Installation Start and Completion times from the Install
 File #9.7 to include in a post-install status message from the install sites
 to the Lexicon devleopers.  This message is used to trouble-shoot various
 problems in the field.  

NUMBER: 4185                            IA #: 4185
  FILE NUMBER: 68                       GLOBAL ROOT: LRO(68,
  DATE CREATED: AUG 06, 2003            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DISK CONSUMPTION ESTIMATE FOR CLINICAL REMINDERS
  ID: LRO(68,
 GENERAL DESCRIPTION:   The following global references are made: 
  
 Global   Nodes 
  
 LRO(68,  $O(^LRO(68,AA)) 
          $G(^LRO(68,AA,0)) 
          $O(^LRO(68,AA,1,LRAD,1,LRAN,4,TEST)) 
  STATUS: Active                        DURATION: Next Version
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 4186                            IA #: 4186
  DATE CREATED: AUG 07, 2003            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  NAME: M2M BROKER - M Client/Server Connection
 GENERAL DESCRIPTION:   $$CONNECT^XWBM2MC()- This API establishes the initial
 connection to the VISTA M server.  It is a function call that returns a
 success/fail indicator of 1 or 0, respectively.  
  STATUS: Active
KEYWORDS: M2M

NUMBER: 4187                            IA #: 4187
  DATE CREATED: AUG 07, 2003            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  NAME: M2M BROKER - Set Application Context
 GENERAL DESCRIPTION:   $$SETCONTX^XWBM2MC() - This API sets the context.  It
 sets up the necessary environment to run the RPCs.  It is a function call that
 returns a success/fail indicator of 1 or 0, respectively.  
  STATUS: Active
KEYWORDS: M2M

NUMBER: 4188                            IA #: 4188
  DATE CREATED: AUG 07, 2003            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  NAME: M2M BROKER - Build the PARAM Data Structure
 GENERAL DESCRIPTION:   $$PARAM^XWBM2MC() - This API sets up the PARAM data
 structure necessary to run the RPCs.  This is a function call that returns a
 success/fail indicator of 1 or 0, respectively.  
  STATUS: Active

NUMBER: 4189                            IA #: 4189
  DATE CREATED: AUG 07, 2003            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  NAME: M2M BROKER - Build the Remote Procedure Data Structure
 GENERAL DESCRIPTION:   $$CALLRPC^XWBM2MC() - This API builds the Remote
 Procedure Call (RPC) data structure, and then makes the call to the RPC on the
 server.  The request message is transported in XML and is parsed by using the
 VISTA Extensible Markup Language (XML) Parser, introduced in Kernel Toolkit
 Patch XT*7.3*58.  
  
 This API is a function call returning a success/fail indicator of 1 or 0, 
 respectively.  
  STATUS: Active
KEYWORDS: M2M

NUMBER: 4190                            IA #: 4190
  DATE CREATED: AUG 07, 2003            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  NAME: M2M BROKER - Close Connection
 GENERAL DESCRIPTION:   $$CLOSE^XWBM2MC() - This API closes the connection
 between that particular instance of the "requesting" VISTA M server and the
 "receiving" VISTA M server, and does any necessary cleanup.  It is a function
 call that returns a success/fail indicator of 1 or 0, respectively.  
  STATUS: Active
KEYWORDS: M2M

NUMBER: 4191                            IA #: 4191
  DATE CREATED: AUG 07, 2003            CUSTODIAL PACKAGE: RPC BROKER
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  NAME: M2M BROKER - Returns CURRENT Application Context
 GENERAL DESCRIPTION:   $$GETCONTX^XWBM2MC() - This API returns the current
 application context so that a new context may be established, thereby
 restoring the previous application context prior to switching to the new one. 
 It is a function call returning a success/fail indicator of 1 or 0,
 respectively.  
  STATUS: Active
KEYWORDS: M2M

NUMBER: 4192                            IA #: 4192
  DATE CREATED: AUG 13, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGENA4                       NAME: DBIA4192
  ID: DGENA4
 GENERAL DESCRIPTION:   As part of the Transitional Pharmacy Benefit project, a
 patient must be enrolled to become eligible for the benefit, along with other
 criteria.  One of the functions to determine enrollment is to determine the
 category of the current enrollment, which is what the $$CATEGORY^DGENA4 call 
 provides.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EXTCAT
COMPONENT/ENTRY POINT: $$CATEGORY(DFN,STATUS)
 COMPONENT DESCRIPTION:   This entry point returns the enrollment category for
 a patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number of the Patient from
 the PATIENT (#2) File.  
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   This variable is optional. If passed in, the call
 will return the enrollment category for this status rather than the veteran's
 current enrollment status.  
VARIABLES: $$CATEGORY                   TYPE: Output
 VARIABLES DESCRIPTION:   This represents the current enrollment category for
 the patient or the enrollment category of the status passed in, if available.
 Otherwise, it defaults to the "Not Enrolled" category. This will be one of
 three values: "E" for Enrolled; "N" for Not Enrolled; "P" for In Process.  
COMPONENT/ENTRY POINT: EXTCAT
 COMPONENT DESCRIPTION:   This entry point returns the external name for the
 defined ENROLLMENT CATEGORY flag.  
VARIABLES: CATEGORY                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal representation of the ENROLLMENT
 CATEGORY.  
VARIABLES: $$EXTCAT                     TYPE: Output
 VARIABLES DESCRIPTION:   This represents the external value of the ENROLLMENT
 CATEGORY.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
 SUBSCRIBING DETAILS:   The $$CATEGORY^DGENA4 call will provide the current
 enrollment category for a patient.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 08/09/19 for access to $$CATEGORY^DGENA4. Added
 access to EXTCAT^DGENA4 on 9/12/2019.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 10/29/26, effective with patch SD*5.3*963 for 
 access to $$CATEGORY 
  DATE ACTIVATED: SEP 20, 2019

NUMBER: 4193                            IA #: 4193
  DATE CREATED: AUG 20, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: SDPHARM                      NAME: DBIA4193
  ID: SDPHARM
 GENERAL DESCRIPTION:   As part of the Transitional Pharmacy Benefit project, a
 list of eligible patients must be built upon install of the patches that make
 up this project. There are various criteria used to determine eligibility, and 
 part of this process involves retrieving appointment information from the 
 PATIENT (#2) file, which is what the SDPHARM routine does.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SDPHARM
 COMPONENT DESCRIPTION:   This routine will return a list of patients eligible
 for the Transitional Pharmacy Benefit program.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
 SUBSCRIBING DETAILS:   Upon post-install of patch PSO*7.0*145, a call will be
 made to the routine SDPHARM. This routine will look through appointment
 information, and determine what patients are eligible for the Transitional
 Pharmacy Benefit program. This information will be set in an XTMP global, 
 beginning with the subscript XTMP("SDPSO145".  

NUMBER: 4194                            IA #: 4194
  DATE CREATED: AUG 13, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: SDPBE                        NAME: DBIA4194
  ID: SDPBE
 GENERAL DESCRIPTION:   As part of the Transitional Pharmacy Benefit project, a
 list of eligible patients must be built upon install of the patches that make
 up this project. There are various criteria used to determine eligibility, and 
 part of this process involves retrieving information from the SD WAIT LIST 
 (#409.3) file, and it's associated files, which is what the SDPBE routine 
 does.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SDPBE
 COMPONENT DESCRIPTION:   This routine will return a list of patients eligible
 for the Transitional Pharmacy Benefit program.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
 SUBSCRIBING DETAILS:   Upon post-install of patch PSO*7.0*145, a call will be
 made to the routine SDPBE. This routine will look through SD WAIT LIST
 information, and determine what patients are eligible for the Transitional
 Pharmacy Benefit program. This information will be set in an XTMP global,
 beginning with the subscript XTMP("SDPSO145".  

NUMBER: 4195                            IA #: 4195
  DATE CREATED: AUG 11, 2003            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSOTPCUL                     NAME: DBIA4195
  ID: PSOTPCUL
 GENERAL DESCRIPTION:   This call tells a subscribing package if a prescription
 has been designated as a Transitional Pharmacy Benefit prescription.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$EN(PSOTRXN)
 COMPONENT DESCRIPTION:   This entry point determines whether or not a
 prescription is a Transitional Pharmacy Benefit prescription.  
VARIABLES: PSOTRXN                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the
 PRESCRIPTION (#52) File.  
VARIABLES: $$EN                         TYPE: Output
 VARIABLES DESCRIPTION:   This variable will be one of two values. A '0' will
 indicate that the prescription is not a Transitional Pharmacy Benefit
 prescription, or that the prescription could not be found. A '1' indicates
 that the prescription is a Transitional Pharmacy Benefit prescription.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   This entry point will return a 1 or a 0, a 1 indicating
 that the prescription passed into the call is a Transitional Pharmacy Benefit 
 prescription, a 0 indicating that the prescription is not a Transitional 
 Pharmacy Benefit prescription.  

NUMBER: 4196                            IA #: 4196
  DATE CREATED: AUG 20, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: SDPHARM1                     NAME: DBIA4196
  ID: SDPHARM1
 GENERAL DESCRIPTION:   The Scheduling package will provide a default
 Institution and default Station Number to Outpatient Pharmacy, based on future
 appointments for patients, when someone is attempting to add a patient to the
 TPB ELIGIBILITY (#52.91) File. The Scheduling package will also provide the 
 nearest Primary Care Appointment date and Hospital Location of that 
 appointment for a patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$DEF(SDPSODFN)
 COMPONENT DESCRIPTION:   This entry point returns the default Institution and
 Station Number.  
VARIABLES: SDPSODFN                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the PATIENT
 (#2) File.  
VARIABLES: $$DEF                        TYPE: Output
 VARIABLES DESCRIPTION:   This variable contains the default Institution and
 Station Number. If a '0' is returned, that means defaults could not be found.
 If defaults can be found, this variable will be 2 pieces, with the '^' as the
 delimiter. The first piece will be the internal number from the INSTITUTION
 (#4) File, the second piece will be that Institution's Station Number.  
COMPONENT/ENTRY POINT: $$PRIAPT(SDPSOPAT)
 COMPONENT DESCRIPTION:   This entry point returns the nearest Primary Care
 Appointment for a patient. Primary Care is determined by the DSS credit pair
 codes that were exported as part of the Transitional Pharmacy Benefit project. 
 
VARIABLES: SDPSOPAT                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the PATIENT
 (#2) File.  
VARIABLES: $$PRIAPT                     TYPE: Output
 VARIABLES DESCRIPTION:   This variable contains the Primary Care Appointment
 information. It will be returned in the following format in 3 pieces of
 information: 
  
 OCT 29, 2003@12:30  OUTPATIENT LAB  (6 days) 
  
 The first piece is the date/time of the appointment, the second piece is the
 Hospital Location, the third piece is the number of days from the current date
 to the appointment. Outpatient Encounters are also evaluated.  Whichever is
 closest to the current date, either encounter or appointment, is returned. If
 it is a past encounter that is returned, then the third piece would be
 returned like this for an encounter 6 days ago: (-6 days).  The Hospital
 Location associated with the Outpatient Encounter must be for one of the DSS
 credit pair codes as determined by the Transitional Pharmacy Benefit project,
 and the status of the Outpatient Encounter must be either "CHECKED OUT" or
 "INPATIENT APPOINTMENT".  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
 SUBSCRIBING DETAILS:   When adding patients manually to the TPB ELIGIBILITY
 (#52.91) File, Institution and Station Number are required fields. This
 routine is called to possibly provide defaults for those fields when patients
 are being added to the file. The Scheduling package will also provide the
 nearest Primary Care Appointment date and Hospital Location of that
 appointment for a patient.  

NUMBER: 4197                            IA #: 4197
  FILE NUMBER: 71.2                     GLOBAL ROOT: RAMIS(71.2
  DATE CREATED: AUG 11, 2003
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Imaging - Procedure Modifier    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 DESCRIPTION:   The name of the procedure modifier.  
 GENERAL DESCRIPTION:   Imaging is granted permission to read Radiology file
 #71.2 (PROCEDURE MODIFIER). The information is being displayed on VistARad
 workstations.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring

NUMBER: 4198                            IA #: 4198
  DATE CREATED: OCT 06, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGREGAED                     NAME: PATIENT ADDRESS EDIT API
  ID: DGREGAED
 GENERAL DESCRIPTION:   The API allows the user to edit patient's mailing
 address.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ADDRESS
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This DBIA contains a Registration API call to edit
 patient's mailing address data.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   (required) - Internal Entry # of Patient File (#2) 
VARIABLES: FLG                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional) - Flags of 1 or 0; if null, 0 is assumed.  
   FLG(1) - if 1, let user edit phone numbers (field #.131 and #.132).  
   FLG(2) - if 1, display before & after address for user confirmation.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: FEE BASIS
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   ADDED 8/3/2010 
  DATE ACTIVATED: JUL 06, 2021

NUMBER: 4199                            IA #: 4199
  DATE CREATED: AUG 13, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORCACT1                      NAME: Order verification calls
  ID: ORCACT1
 GENERAL DESCRIPTION:   This documents Care Management's use of code in ORCACT1
 to ensure that order verification by nurses is done consistently with CPRS.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: REPLCD
 COMPONENT DESCRIPTION:   Checks if the current order replaced any others via
 Edit or Renewal, and then if any replaced orders are also unverified.  
VARIABLES: ORIFN                        TYPE: Used
 VARIABLES DESCRIPTION:   Order IEN in Orders file #100.  
VARIABLES: ORVER                        TYPE: Used
 VARIABLES DESCRIPTION:   Flag indicating type of verification being done,
 (N)urse or (C)lerk or Chart (R)eview.  
VARIABLES: ORES(IEN)                    TYPE: Output
 VARIABLES DESCRIPTION:   Any unverified orders found that were replaced by
 ORIFN will be returned in this array, where IEN is the order# of each in the
 Orders file #100.  
COMPONENT/ENTRY POINT: CKALERT
 COMPONENT DESCRIPTION:   Checks if the current patient has any remaining
 unverified [med] orders, and if not then any existing Unverified [Med] Orders
 notifications for the current user will be deleted.  
VARIABLES: ORVP                         TYPE: Used
 VARIABLES DESCRIPTION:   IEN from Patient file #2 in variable pointer format.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City

NUMBER: 4200                            IA #: 4200
  DATE CREATED: AUG 13, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORCD                         NAME: NMSP~ORCD
  ID: ORCD
 GENERAL DESCRIPTION:   Routine ORCD contains CPRS utilities for order dialogs;
 Care Management would like permission to call the $$NMSP function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$NMSP(PKG)
 COMPONENT DESCRIPTION:   Uses silent FileMan calls to get a package namespace
 from its IEN in the Package file #9.4.  
VARIABLES: PKG                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in the Package file #9.4 
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULT=$$NMSP^ORCD(PKG) where RESULT returns the
 package's namespace from the PREFIX field #1 via $$GET1^DIQ.  The two
 exceptions to this are meds, where all Pharmacy packages return "PS", and
 Vitals, which returns "OR" instead of "GMRV", due to the way that CPRS and
 Care Mgt handle those types of orders.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City

NUMBER: 4201                            IA #: 4201
  DATE CREATED: AUG 13, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORCSEND                      NAME: EN~ORCSEND
  ID: ORCSEND
 GENERAL DESCRIPTION:   This routine handles the release of orders from CPRS to
 the ancillary services when appropriate.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Releases [actions on] orders to the ancillary
 services 
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN in Orders file #100; may include a second ;-piece
 containing the ien of a specific action in the Order Actions subfile #100.008. 
 
VARIABLES: ACTION                       TYPE: Input
 VARIABLES DESCRIPTION:   Two character code for the action being done to order
 ORIFN: 
         NW = new 
         RW = rewritten or copied 
         XX = changed 
         RN = renewed 
         DC = discontinued 
         HD = held 
         RL = released from hold 
         ES = signed 
         VR = verified 
VARIABLES: SIGSTS                       TYPE: Input
 VARIABLES DESCRIPTION:   The signature status of the order, corresponding to
 the values allowed by the SIGNATURE STATUS field #4 of the Order Actions
 subfile #100.008.  
VARIABLES: RELSTS                       TYPE: Input
 VARIABLES DESCRIPTION:   A true or false flag, indicating if the calling
 application thinks the order may be released.  
VARIABLES: NATURE                       TYPE: Input
 VARIABLES DESCRIPTION:   Either the IEN or CODE in the Nature of Order file
 #100.02.  
VARIABLES: REASON                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN in the Order Reason file #100.03.  
VARIABLES: ORERR                        TYPE: Both
 VARIABLES DESCRIPTION:   Variable to be passed in by reference, to allow for
 the return of an error message if needed; value will be null if successful, or
 "1^message" if release failed.  
VARIABLES: ORVP                         TYPE: Used
 VARIABLES DESCRIPTION:   IEN in Patient file #2.  
VARIABLES: ORNP                         TYPE: Used
 VARIABLES DESCRIPTION:   IEN of ordering provider in New Person file #200.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City

NUMBER: 4202                            IA #: 4202
  DATE CREATED: AUG 13, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORQ12                        NAME: TEXT~ORQ12
  ID: ORQ12
 GENERAL DESCRIPTION:   Returns the text of an order for display.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: TEXT
 COMPONENT DESCRIPTION:   Returns the text of order for display.  
VARIABLES: ORTX                         TYPE: Both
 VARIABLES DESCRIPTION:   Array passed in by reference, to accept the formatted
 text on return in the format ORTX(#)=line of text.  
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN in Orders file #100; may include a second ;-piece
 containing the ien of a specific action in the Order Actions subfile #100.008,
 else the text of the Current Action (field #30 in file #100) will be returned. 
 
VARIABLES: WIDTH                        TYPE: Input
 VARIABLES DESCRIPTION:   The desired maximum length of each line of text
 returned, as a number from 1 to 244; if not specified, 244 will be used.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City
SUBSCRIBING PACKAGE: HEALTH SUMMARY
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 04/14/22, effective with DSSV 1.1 DSS Class 3
 product Document Only This is being requested in order to properly return the
 order text associated with an order.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   ADDED 10/06/22, effective with VPR*1*25 to retrieve the
 order text 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Added 8/21/23, effective with PXRM*2.0*45 to display
 order text in support of the Breast Cancer screening. 
  DATE ACTIVATED: AUG 21, 2023

NUMBER: 4203                            IA #: 4203
  DATE CREATED: AUG 13, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORQ2                         NAME: DETAIL~ORQ2
  ID: ORQ2
 GENERAL DESCRIPTION:   Returns the Detailed Display report for an order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DETAIL
 COMPONENT DESCRIPTION:   Returns the Detailed Display report for an order.  
VARIABLES: ORY                          TYPE: Both
 VARIABLES DESCRIPTION:   The name of the array, as a closed reference, where
 the report will be built via indirection.  
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN in the Orders file #100.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 ***************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ***************************************************
  
 Effective with HMP*2.0*2 

NUMBER: 4204                            IA #: 4204
  DATE CREATED: AUG 15, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORQPTQ11                     NAME: DEFLIST~ORQPTQ11
  ID: ORQPTQ11
 GENERAL DESCRIPTION:   CPRS Patient List api's.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DEFLIST
 COMPONENT DESCRIPTION:   Returns the current user's default CPRS patient list. 
 
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Variable passed in by reference to accept and return
 the list of patients: 
     Y    = source;ien;clinic start;clinic stop 
  and 
     Y(#) = DFN ^ NAME if source is a single list 
  or ^TMP("OR",$J,"PATIENTS",#,0) = DFN ^ NAME for combination lists If there
 is an error or empty list, the first entry in the list (#=1) will return
 "^message".  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 ***************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ***************************************************
  
 HMP routine HMPROS8 calls the DEFLIST^ORQPTQ11 API to retrieve the logged on
 user's patient list.  

NUMBER: 4205                            IA #: 4205
  DATE CREATED: DEC 23, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGAPI
  NAME: DBIA4205                        ID: DGAPI
 GENERAL DESCRIPTION:   API to allow access to Inpatient CPTs and Inpatient
 POVs.  
  STATUS: Active
KEYWORDS: CPT
KEYWORDS: POV
KEYWORDS: Diagnosis
COMPONENT/ENTRY POINT: $$DATA2PTF(DFN,PTFIEN,PSDATE,USER,ERR_DISPLAY,SOURCE)
 COMPONENT DESCRIPTION:   This function adds professional services to file 46. 
 The data is passed using ^TMP("PTF",$J,FILE #,SEQUENCE #)=  Professional 
 Services are in the Inpatient CPT Procedure file (46) and Inpatient Diagnoses
 in file 46.1.  At least one procedure or diagnosis is required.  This function
 returns the IEN for the PTF file entry if successful.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   (required)  The IEN for the Patient file (2).  
VARIABLES: PTFIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional)  The IEN for the PTF file (45).  
VARIABLES: PSDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   (required)  The date and time of the professional
 service.  
VARIABLES: USER                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional)  User who is responsible for
 add/edit/delete action on the encounter.  Pointer to the New Person file
 (200).  
VARIABLES: ERR_DISPLAY                  TYPE: Input
 VARIABLES DESCRIPTION:   (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 ERR_DISPLAY is not defined, errors are posted
 to the TMP file subscripted by "DIERR" at the next level to the node that
 caused the error.  
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional)  Where SOURCE is a string of text (3-30
 character) identifying the source of the data. Examples of  SOURCE are:  "LAB 
 DATA" or "RADIOLOGY DATA".  
VARIABLES: ~TMP('PTF',$J,46,0)          TYPE: Output
 VARIABLES DESCRIPTION:   REFPROV^PERFPROV^PRIMARY DIAGNOSIS^RENDERING LOCATION 
  
 1. REFPROV (optional)  The referring or ordering provider.  
  
 2. PERFPROV (required)  The performing provider.  
  
 3. PRIMARY DIAGNOSIS (required)  The first diagnosis to list in box 21 on the
 HCFA 1500.  
  
 4. RENDERING LOCATION (optional)  The location the service was rendered if it
 was different from the provider's location.  The name and address are printed
 in box 32 on the HCFA 1500.  
VARIABLES: ~TMP('PTF',$J,46,SEQ)        TYPE: Output
 VARIABLES DESCRIPTION:   Inpatient CPT data.  Each diagnosis must have a
 cooresponding entry in file 46.1 
  
 CPT IEN^CPT CODE^CPT MODIFIER 1^CPT MODIFIER 2^RELATED DIAGNOSIS 1^RELATED
 DIAGNOSIS 2^RELATED DIAGNOSIS 3^RELATED DIAGNOSIS 4^TREATED FOR SC
 CONDITION^TREATED FOR AO CONDITION^EXPOSED TO ENVIR CONTAMINANTS^TREATMENT FOR
 MST^TREATMENT FOR HEAD/N ECK CA 
  
 SEQ   Sequence number to allow for multiple entries.  
  
 CPT IEN                   0;1 IEN for CPT Record (Optional) If the IEN is
 provided and there is an existing record, this information will overlay the
 existing record.  The CPT Code must match the existing record.  This value is
 passed back by th e API if the call is successful.  
  
 HELP-PROMPT: Enter the IEN for the CPT record in the Inpatient CPT file (46).  
 DESCRIPTION:  This is the IEN for the CPT record in the Inpatient CPT file. 
 It should be stored in the orders file.  
  
 CPT CODE               0;2 POINTER TO CPT FILE (#81) (Required for
 Professional Service Entry) 
  
 HELP-PROMPT: Enter the procedure, services or supplies using CPT or HCPCS. 
 DESCRIPTION:  This is the procedure, services, or supplies used for the
 patient.  It is using the HCFA Common Procedure Coding System (HCPCS) or
 Common Procedure Terminology (CPT) code.  This value appears on the HCFA 1500
 in box 24d.  the value s in this field will be provided to the billing package
 when the record is closed.  
  
  
 CPT MODIFIER 1         0;3 POINTER TO CPT MODIFIER FILE (#81.3) 
  
 HELP-PROMPT:      Indicates that a service or procedure has been altered, but
 code unchanged. DESCRIPTION:      Used to indicate that a service or procedure
 has been altered by some specific circumstance but without changing the
 definition or code.  
  
 CPT MODIFIER 2         0;4 POINTER TO CPT MODIFIER FILE (#81.3) 
  
 HELP-PROMPT:      Indicates that a service or procedure has been altered, but
 code UNCHANGED. DESCRIPTION:      Used to indicate that a service or procedure
 has been altered by some specific circumstance but not changed definition or
 code.  
  
 RELATED DIAGNOSIS 1    0;5 POINTER TO ICD DIAGNOSIS FILE (#80) (Required) 
  
 HELP-PROMPT:      The primary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      The diagnosis code most directly
 related to the procedure code performed for this professional service.  This
 field must be entered for each CPT code entered.  It appears in box 21 on the
 HCFA-1500 and is associated with a proc edure in box 24e.  
  
 RELATED DIAGNOSIS 2    0;6 POINTER TO ICD DIAGNOSIS FILE (#80) 
  
 HELP-PROMPT:      A secondary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      A secondary diagnosis related to
 the procedure performed for this professional service.  This field is
 optional.  It appears in box 21 on the HCFA-1500 and is associated with a
 procedure in box 24e.  
  
 RELATED DIAGNOSIS 3    0;7 POINTER TO ICD DIAGNOSIS FILE (#80) 
  
 HELP-PROMPT:      A secondary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      A secondary diagnosis related to
 the procedure performed for this professional service.  This field is
 optional.  It appears in box 21 on the HCFA-1500 and is associated with a
 procedure in box 24e.  
  
 RELATED DIAGNOSIS 4    0;8 POINTER TO ICD DIAGNOSIS FILE (#80) 
  
 HELP-PROMPT:      A secondary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      A secondary diagnosis related to
 the procedure performed for this professional service.  This field is
 optional.  It appears in box 21 on the HCFA-1500 and is associated with a
 procedure in box 24e.  
  
 TREATED FOR SC CONDITION 0;9 SET (Required if YES for registration.) 
  
 '1' FOR YES; '0' FOR NO; DESCRIPTION:      Enter 'Y' if this applicant is
 service connected and the professional service is related to that service
 connection.  Otherwise enter 'N'.  This field can only be entered if the
 service connection information was entered in reg istration.  See field .301
 in file 2.  
  
 TREATED FOR AO CONDITION 0;10 SET (Required if YES for registration.) '1' FOR
 YES; '0' FOR NO; HELP-PROMPT:      The Patient must have Agent Orange exposure
 indicated! DESCRIPTION:      The Agent Orange questions must be answered yes
 in registration before this field can be entered.  Enter 'Y' if this procedure
 is related to Agent Orange exposure based on the related diagnosis.  See field
 .32102 in file 2.  
  
 TREATED FOR IR CONDITION 0;11 SET (Required if YES for registration.) '1' FOR
 YES; '0' FOR NO; HELP-PROMPT:      The Patient must have Ionizing Radiation
 exposure indicated! DESCRIPTION:      Enter 'Y' if the procedure performed is
 related to exposure to ionizing .  Enter 'N' if the procedure performed is
 unrelated to ionizing radiation.  The ionizing radiation information must be
 entered in registration before it c an be entered here.  See field .32111 in
 file 2.  
  
 EXPOSED TO ENVIR CONTAMINANTS 0;12 SET (Required if YES for registration.) '1'
 FOR YES; '0' FOR NO; HELP-PROMPT:      The Patient must have Environment
 Contaminants exposure! DESCRIPTION:      Enter 'Y' if the procedure performed
 is related to exposure to environmental contamination.  Enter 'N' if the
 procedure performed is unrelated to environmental contamination.  This
 information must be entered in Registration be fore it can be entered here. 
 See field .322013 in file 2.  
  
 TREATMENT FOR MST      0;13 SET (Required) 
  
 '1' FOR YES; '0' FOR NO; HELP-PROMPT:      Was the treatment related to
 Military Sexual Trauma. DESCRIPTION:      Enter 'Y' if the procedure performed
 is related to military sexual trauma.  Enter 'N' if the procedure performed is
 unrelated to military sexual trauma.  This information must be entered in 
 registration first.  
  
 TREATMENT FOR HEAD/NECK CA 0;14 SET (Required if YES for registration.) '1'
 FOR YES; '0' FOR NO; 
  
 HELP-PROMPT:      Was the treatment related to Head and/or Neck Cancer. 
 DESCRIPTION:      Enter 'Y' if this procedure is related to treatment for
 head/neck cancer.  Enter 'N' is the procedure is unrelated to the patient's
 head/neck cancer.  
  
  
 QUANTITY               0;15 NUMBER 
  
 INPUT TRANSFORM:  K:+X'=X!(X>99)!(X<1)!(X?.E1"."1N.N) X HELP-PROMPT:     
 Enter a number between 1 and 99 indicating how many times this procedure was
 done. DESCRIPTION: This is the number of times this procedure was done to the
 patient for one professional service.  
  
 RELATED DIAGNOSIS 5    0;16 POINTER TO ICD DIAGNOSIS FILE (#80) (Required) 
  
 HELP-PROMPT:      A secondary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      A secondary diagnosis related to
 the procedure performed for this professional service.  This field is
 optional.  It appears in box 21 on the HCFA-1500 and is associated with a
 procedure in box 24e.  
  
 RELATED DIAGNOSIS 6    0;17 POINTER TO ICD DIAGNOSIS FILE (#80) (Required) 
  
 HELP-PROMPT:      A secondary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      A secondary diagnosis related to
 the procedure performed for this professional service.  This field is
 optional.  It appears in box 21 on the HCFA-1500 and is associated with a
 procedure in box 24e.  
  
 RELATED DIAGNOSIS 7    0;18 POINTER TO ICD DIAGNOSIS FILE (#80) (Required) 
  
 HELP-PROMPT:      A secondary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      A secondary diagnosis related to
 the procedure performed for this professional service.  This field is
 optional.  It appears in box 21 on the HCFA-1500 and is associated with a
 procedure in box 24e.  
  
 RELATED DIAGNOSIS 8    0;19 POINTER TO ICD DIAGNOSIS FILE (#80) (Required) 
  
 HELP-PROMPT:      A secondary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      A secondary diagnosis related to
 the procedure performed for this professional service.  This field is
 optional.  It appears in box 21 on the HCFA-1500 and is associated with a
 procedure in box 24e.  
  
VARIABLES: ~TMP('PTF',$J,46.1,SEQ)      TYPE: Output
 VARIABLES DESCRIPTION:   INPATIENT POV Each node is the data for a single ICD9
 diagnosis.  As many codes as needed may be sent at one time.  Each Diagnosis
 is associated with a sequence number  If the patient's inpatient stay cannot
 be located using the information provided, an error is generated.  The IEN for
 the Inpatient CPT file is returned in the zero node  for file 46 in the TMP
 file.  
  
 POV IEN^DIAGNOSIS^TREATED FOR SC CONDITION^TREATED FOR AO CONDITION^EXPOSED TO
 ENVIR CONTAMINANTS^TREATMENT FOR MST^TREATMENT FOR HEAD/NECK CA 
  
 SEQ  Sequence number to allow for multiple entries.  
  
 POV IEN                   0;1 IEN for Diagnosis Record (Optional)  If the IEN
 is provided and there is an existing record, this information will overlay the
 existing record.  This value is passed back by the API if the call is
 successful.  
  
 HELP-PROMPT: Enter the IEN for the Diagnosis record in the Inpatient POV file
 (46).  DESCRIPTION:  This is the IEN for the Diagnosis record in the Inpatient
 POV file.  It should be stored in the orders file.  
  
 DIAGNOSIS    0;2 POINTER TO ICD DIAGNOSIS FILE (#80) (Required for Diagnosis
 entry) 
  
 HELP-PROMPT:      The primary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      The diagnosis code most directly
 related to the procedure code performed for this professional service.  This
 field must be entered for each CPT code entered.  It appears in box 21 on the
 HCFA-1500 and is associated with a proc edure in box 24e.  
  
 TREATED FOR SC CONDITION 0;3 SET (Required if YES for registration.) 
  
 '1' FOR YES; '0' FOR NO; DESCRIPTION:      Enter 'Y' if this applicant is
 service connected and the professional service is related to that service
 connection.  Otherwise enter 'N'.  This field can only be entered if the
 service connection information was entered in reg istration.  See field .301
 in file 2.  
  
 TREATED FOR AO CONDITION 0;4 SET (Required if YES for registration.) '1' FOR
 YES; '0' FOR NO; HELP-PROMPT:      The Patient must have Agent Orange exposure
 indicated! DESCRIPTION:      The Agent Orange questions must be answered yes
 in registration before this field can be entered.  Enter 'Y' if this procedure
 is related to Agent Orange exposure based on the related diagnosis.  See field
 .32102 in file 2.  
  
 TREATED FOR IR CONDITION 0;5 SET (Required if YES for registration.) '1' FOR
 YES; '0' FOR NO; HELP-PROMPT:      The Patient must have Ionizing Radiation
 exposure indicated! DESCRIPTION:      Enter 'Y' if the procedure performed is
 related to exposure to ionizing .  Enter 'N' if the procedure performed is
 unrelated to ionizing radiation.  The ionizing radiation information must be
 entered in registration before it c an be entered here.  See field .32111 in
 file 2.  
  
 EXPOSED TO ENVIR CONTAMINANTS 0;6 SET (Required if YES for registration.) '1'
 FOR YES; '0' FOR NO; HELP-PROMPT:      The Patient must have Environment
 Contaminants exposure! DESCRIPTION:      Enter 'Y' if the procedure performed
 is related to exposure to environmental contamination.  Enter 'N' if the
 procedure performed is unrelated to environmental contamination.  This
 information must be entered in Registration be fore it can be entered here. 
 See field .322013 in file 2.  
  
 TREATMENT FOR MST      0;7 SET (Required) 
  
 '1' FOR YES; '0' FOR NO; HELP-PROMPT:      Was the treatment related to
 Military Sexual Trauma. DESCRIPTION:      Enter 'Y' if the procedure performed
 is related to military sexual trauma.  Enter 'N' if the procedure performed is
 unrelated to military sexual trauma.  This information must be entered in 
 registration first.  
  
 TREATMENT FOR HEAD/NECK CA 0;8 SET (Required if YES for registration.) '1' FOR
 YES; '0' FOR NO; 
  
 HELP-PROMPT:      Was the treatment related to Head and/or Neck Cancer. 
 DESCRIPTION:      Enter 'Y' if this procedure is related to treatment for
 head/neck cancer.  Enter 'N' is the procedure is unrelated to the patient's
 head/neck cancer.  
VARIABLES: $$DATA2PTF                   TYPE: Output
 VARIABLES DESCRIPTION:   
 PTFIEN   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 in the TMP file 
          subscripted by "DIERR".  
 -2       Unable to identify a valid inpatient stay.  No data was processed.
 -3       API was called incorrectly.  No data was processed.
COMPONENT/ENTRY POINT: CPTINFO(DFN,PTFIEN,PSDATE)
 COMPONENT DESCRIPTION:   This entry point will return the CPT procedure data
 for a single professional service from file 46 in ^TMP("PTF",$J,46, 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   (required)  The IEN for the Patient file (2).  
VARIABLES: PTFIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional)  The IEN for the PTF file (45).  
VARIABLES: PSDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   (required)  The date and time of the professional
 service.  
VARIABLES: ~TMP('PTF',$J,46,0)          TYPE: Output
 VARIABLES DESCRIPTION:   REFPROV^PREFPROV^PRIMARY DIAGNOSIS^RENDERING LOCATION 
  
 1.REFPROV (optional)  The referring or ordering provider.  
  
 2.  PERFPROV
 (required)  The performing provider.  
  
 2.  PRIMARY DIAGNOSIS
 (required)  The first diagnosis to list in box 21 on the HCFA 1500.  
  
 3.  RENDERING LOCATION
 (optional)  The location the service was rendered if it was different from the
 provider's location.  The name and address are printed in box 32 on the HCFA
 1500.  
VARIABLES: ~TMP('PTF',$J,46,SEQ)        TYPE: Output
 VARIABLES DESCRIPTION:   CPT IEN^CPT CODE^CPT MODIFIER 1^CPT MODIFIER
 2^RELATED DIAGNOSIS 1 ^ RELATED DIAGNOSIS 2^RELATED DIAGNOSIS 3^RELATED
 DIAGNOSIS 4^TREATED FOR SC CONDITION^TREATED FOR AO CONDITION^EXPOSED TO ENVIR
 CONTAMINANTS^TREATMENT FOR MST^TREATMENT FOR HEAD/NECK CA 
  
 1.  CPT IEN                   0;1 IEN for CPT Record
  
 2.  CPT CODE               0;2 POINTER TO CPT FILE (#81) (Required)
 HELP-PROMPT: Enter the procedure, services or supplies using CPT or HCPCS 
 DESCRIPTION:  This is the procedure, services, or supplies used for the
 patient.  It is using the HCFA Common Procedure Coding System (HCPCS) or
 Common Procedure Terminology (CPT) code.  This value appears on the HCFA 1500
 in box 24d.  the value s in this field will be provided to the billing package
 when the record is closed.  
  
 3.  CPT MODIFIER 1         0;3 POINTER TO CPT MODIFIER FILE (#81.3)
 HELP-PROMPT:      Indicates that a service or procedure has been altered, but
 code unchanged. DESCRIPTION:      Used to indicate that a service or procedure
 has been altered by some specific circumstance but without changing the
 definition or code.  
  
 4.  CPT MODIFIER 2         0;4 POINTER TO CPT MODIFIER FILE (#81.3)
 HELP-PROMPT:      Indicates that a service or procedure has been altered, but
 code UNCHANGED. DESCRIPTION:      Used to indicate that a service or procedure
 has been altered by some specific circumstance but not changed definition or
 code.  
  
 5.  RELATED DIAGNOSIS 1    0;5 POINTER TO ICD DIAGNOSIS FILE (#80) (Required)
 HELP-PROMPT:      The primary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      The diagnosis code most directly
 related to the procedure code performed for this professional service.  This
 field must be entered for each CPT code entered.  It appears in box 21 on the
 HCFA-1500 and is associated with a proc edure in box 24e.  
  
 6.  RELATED DIAGNOSIS 2    0;6 POINTER TO ICD DIAGNOSIS FILE (#80)
 HELP-PROMPT:      A secondary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      A secondary diagnosis related to
 the procedure performed for this professional service.  This field is
 optional.  It appears in box 21 on the HCFA-1500 and is associated with a
 procedure in box 24e.  
  
 7.  RELATED DIAGNOSIS 3    0;7 POINTER TO ICD DIAGNOSIS FILE (#80)
 HELP-PROMPT:      A secondary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      A secondary diagnosis related to
 the procedure performed for this professional service.  This field is
 optional.  It appears in box 21 on the HCFA-1500 and is associated with a
 procedure in box 24e.  
  
 8.  RELATED DIAGNOSIS 4    0;8 POINTER TO ICD DIAGNOSIS FILE (#80)
 HELP-PROMPT:      A secondary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      A secondary diagnosis related to
 the procedure performed for this professional service.  This field is
 optional.  It appears in box 21 on the HCFA-1500 and is associated with a
 procedure in box 24e.  
  
 9.  TREATED FOR SC CONDITION 0;9 SET (Required if YES for registration.)
 '1' FOR YES; '0' FOR NO; DESCRIPTION:      Enter 'Y' if this applicant is
 service connected and the professional service is related to that service
 connection.  Otherwise enter 'N'.  This field can only be entered if the
 service connection information was entered in reg istration.  See field .301
 in file 2.  
  
 10. TREATED FOR AO CONDITION 0;10 SET (Required if YES for registration.)
 '1' FOR YES; '0' FOR NO; HELP-PROMPT:      The Patient must have Agent Orange
 exposure indicated! DESCRIPTION:      The Agent Orange questions must be
 answered yes in registration before this field can be entered.  Enter 'Y' if
 this procedure is related to Agent Orange exposure based on the related
 diagnosis.  See field .32102 in file 2.  
  
 11. TREATED FOR IR CONDITION 0;11 SET (Required if YES for registration.)
 '1' FOR YES; '0' FOR NO; HELP-PROMPT:      The Patient must have Ionizing
 Radiation exposure indicated! DESCRIPTION:      Enter 'Y' if the procedure
 performed is related to exposure to ionizing .  Enter 'N' if the procedure
 performed is unrelated to ionizing radiation.  The ionizing radiation
 information must be entered in registration before it c an be entered here. 
 See field .32111 in file 2.  
  
 12. EXPOSED TO ENVIR CONTAMINANTS 0;12 SET (Required if YES for registration.)
 '1' FOR YES; '0' FOR NO; HELP-PROMPT:      The Patient must have Environment
 Contaminants exposure! DESCRIPTION:      Enter 'Y' if the procedure performed
 is related to exposure to environmental contamination.  Enter 'N' if the
 procedure performed is unrelated to environmental contamination.  This
 information must be entered in Registration be fore it can be entered here. 
 See field .322013 in file 2.  
  
 13. TREATMENT FOR MST      0;13 SET (Required)
 '1' FOR YES; '0' FOR NO; HELP-PROMPT:      Was the treatment related to
 Military Sexual Trauma. DESCRIPTION:      Enter 'Y' if the procedure performed
 is related to military sexual trauma.  Enter 'N' if the procedure performed is
 unrelated to military sexual trauma.  This information must be entered in 
 registration first.  
  
 14. TREATMENT FOR HEAD/NECK CA 0;14 SET (Required if YES for registration.)
 '1' FOR YES; '0' FOR NO; HELP-PROMPT:      Was the treatment related to Head
 and/or Neck Cancer. DESCRIPTION:      Enter 'Y' if this procedure is related
 to treatment for head/neck cancer.  Enter 'N' is the procedure is unrelated to
 the patient's head/neck cancer.  
  
 15. QUANTITY               0;15 NUMBER
  
 INPUT TRANSFORM:  K:+X'=X!(X>99)!(X<1)!(X?.E1"."1N.N) X HELP-PROMPT:     
 Enter a number between 1 and 99 indicating how many times this procedure was
 done. DESCRIPTION: This is the number of times this procedure was done to the
 patient for one professional service.  
  
 RELATED DIAGNOSIS 5    0;16 POINTER TO ICD DIAGNOSIS FILE (#80) (Required) 
  
 HELP-PROMPT:      A secondary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      A secondary diagnosis related to
 the procedure performed for this professional service.  This field is
 optional.  It appears in box 21 on the HCFA-1500 and is associated with a
 procedure in box 24e.  
  
 RELATED DIAGNOSIS 6    0;17 POINTER TO ICD DIAGNOSIS FILE (#80) (Required) 
  
 HELP-PROMPT:      A secondary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      A secondary diagnosis related to
 the procedure performed for this professional service.  This field is
 optional.  It appears in box 21 on the HCFA-1500 and is associated with a
 procedure in box 24e.  
  
 RELATED DIAGNOSIS 7    0;18 POINTER TO ICD DIAGNOSIS FILE (#80) (Required) 
  
 HELP-PROMPT:      A secondary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      A secondary diagnosis related to
 the procedure performed for this professional service.  This field is
 optional.  It appears in box 21 on the HCFA-1500 and is associated with a
 procedure in box 24e.  
  
 RELATED DIAGNOSIS 8    0;19 POINTER TO ICD DIAGNOSIS FILE (#80) (Required) 
  
 HELP-PROMPT:      A secondary diagnosis associated with the procedure
 performed on the HCFA 1500. DESCRIPTION:      A secondary diagnosis related to
 the procedure performed for this professional service.  This field is
 optional.  It appears in box 21 on the HCFA-1500 and is associated with a
 procedure in box 24e. 
COMPONENT/ENTRY POINT: PTFINFOR(DFN,PTFIEN,DATE)
 COMPONENT DESCRIPTION:   This entry point will return an array of Professional
 Service dates and times for an inpatient visit in the PTF file (45).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   (required) The IEN in the Patient file (2) 
VARIABLES: PTFIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   (required) The IEN in the PTF file (45) 
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   (required if PTFIEN is not provided)  The date and
 time of the order.  This will be used to identify the inpatient stay if the
 PTFIEN is not provided.  
VARIABLES: ~TMP('PTF',$J,SEQUENCE #)    TYPE: Output
 VARIABLES DESCRIPTION:   PSDATE ^ REFPROV ^ PERFPROV ^ PRIMARY DIAGNOSIS ^
 RENDERING LOCATION 
  
 SEQUENCE NUMBER  A number to allow for multiple 
                   entries to be returned.  
  
 PSDATE           (required)  The date and time of the professional service.  
  
 REFPROV          (required)  The referring or ordering provider.  
  
 PERFPROV         (required)  The performing provider.  
  
 PRIMARY DIAGNOSIS (required)  The first diagnosis to list in box 21 
                   on the HCFA 1500.  
                   This diagnosis must appear at leat once associated with a 
                   CPT code for this professional service.  
  
 RENDERING LOCATION  (optional) The location the service was rendered if 
                     it was different from the provider's location.  
                     The name and address are printed in box 32 on 
                     the HCFA 1500.  
COMPONENT/ENTRY POINT: $$DELCPT(CPTIEN)
 COMPONENT DESCRIPTION:   This entry point deletes indivdual entries in the
 Inpatient CPT file (46).  If this results in a professional service with no
 CPT codes, the professional service will be deleted.  It is the responsibility 
 of the calling routine to fix any pointers to the Inpatient CPT file.  All
 deletes are logical.  
VARIABLES: CPTIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The IEN for the CPT in the Inpatient CPT
 cile (46).  
VARIABLES: $$DELCPT                     TYPE: Output
 VARIABLES DESCRIPTION:   1      No errors occurred -1     Record was locked,
 no changes made 
COMPONENT/ENTRY POINT: $$DELPOV(POVIEN)
 COMPONENT DESCRIPTION:   This entry point deletes individual entries in the
 Inpatient CPT file (46).  If this results in a professional service with no
 codes, the professional service will be deleted.  It is the responsibility of
 the calling routine to fix any pointers from the Inpatient CPT file.  All 
 deletes are logical.  
VARIABLES: POVIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   (required) The IEN for the diagnosis in the Inpatient
 POV file (46.1).  
VARIABLES: $$DELPOV                     TYPE: Output
 VARIABLES DESCRIPTION:   2   No errors occurred -1  Record was locked, no
 changes made 
COMPONENT/ENTRY POINT: ICDINFO(DFN,PTFIEN,DATE,ICDIEN)
 COMPONENT DESCRIPTION:   This function returns the ICD9 Diagnosis data for a
 single inpatient stay from ~TMP('PTF',$J,46.1, 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   (required) This is the patient DFN.  
VARIABLES: PTFIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) The IEN from the PTF file (45).  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   (required if the PTFIEN and ICDIEN are not provided) 
 The date and time of the order.  This will be used to identify the inpatient
 stay if the PTFIEN is not provided.  
VARIABLES: ICDIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional)  The IEN from the Inpatient POV file
 (46.1) 
VARIABLES: ~TMP('PTF',$J,46.1,SEQ)      TYPE: Output
 VARIABLES DESCRIPTION:   =POV IEN^DIAGNOSIS^TREATED FOR SC CONDITION^TREATED
 FOR AO CONDITION^EXPOSED TO ENVIR CONTAMINANTS^TREATMENT FOR MST^TREATMENT FOR
 HEAD/NECK CA 
  
 1.POV IEN                   0;1 IEN for Diagnosis Record (Optional)  If the
 IEN is provided and there is an existing record, this information will overlay
 the existing record.  This value is passed back by the API if the call is
 successful.  
  
 HELP-PROMPT: Enter the IEN for the Diagnosis record in the Inpatient POV file
 (46).  DESCRIPTION:  This is the IEN for the Diagnosis record in the Inpatient
 POV file.  It should be stored in the orders file.  
  
 2. DIAGNOSIS   0;2 POINTER TO ICD DIAGNOSIS FILE (#80) (Required) HELP-PROMPT: 
     The primary diagnosis associated with the procedure performed on the HCFA
 1500. DESCRIPTION:      The diagnosis code most directly related to the
 procedure code performed for this professional service.  This field must be
 entered for each CPT code entered.  It appears in box 21 on the HCFA-1500 and
 is associated with a proc edure in box 24e.  
  
 3. TREATED FOR SC CONDITION 0;3 SET (Required if YES for registration.) '1'
 FOR YES; '0' FOR NO; DESCRIPTION:      Enter 'Y' if this applicant is service
 connected and the professional service is related to that service connection. 
 Otherwise enter 'N'.  This field can only be entered if the service connection
 information was entered in reg istration.  See field .301 in file 2.  
  
 4. TREATED FOR AO CONDITION 0;4 SET (Required if YES for registration.) '1'
 FOR YES; '0' FOR NO; HELP-PROMPT:      The Patient must have Agent Orange
 exposure indicated! DESCRIPTION:      The Agent Orange questions must be
 answered yes in registration before this field can be entered.  Enter 'Y' if
 this procedure is related to Agent Orange exposure based on the related
 diagnosis.  See field .32102 in file 2.  
  
 5. TREATED FOR IR CONDITION 0;5 SET (Required if YES for registration.) '1'
 FOR YES; '0' FOR NO; HELP-PROMPT:      The Patient must have Ionizing
 Radiation exposure indicated! DESCRIPTION:      Enter 'Y' if the procedure
 performed is related to exposure to ionizing .  Enter 'N' if the procedure
 performed is unrelated to ionizing radiation.  The ionizing radiation
 information must be entered in registration before it c an be entered here. 
 See field .32111 in file 2.  
  
 6. EXPOSED TO ENVIR CONTAMINANTS 0;6 SET (Required if YES for registration.) 
 '1' FOR YES; '0' FOR NO; HELP-PROMPT:      The Patient must have Environment
 Contaminants exposure! DESCRIPTION:      Enter 'Y' if the procedure performed
 is related to exposure to environmental contamination.  Enter 'N' if the
 procedure performed is unrelated to environmental contamination.  This
 information must be entered in Registration be fore it can be entered here. 
 See field .322013 in file 2.  
  
 7. TREATMENT FOR MST      0;7 SET (Required) '1' FOR YES; '0' FOR NO; 
 HELP-PROMPT:      Was the treatment related to Military Sexual Trauma. 
 DESCRIPTION:      Enter 'Y' if the procedure performed is related to military
 sexual trauma.  Enter 'N' if the procedure performed is unrelated to military
 sexual trauma.  This information must be entered in registration first.  
  
 8. TREATMENT FOR HEAD/NECK CA 0;8 SET (Required if YES for registration.) '1'
 FOR YES; '0' FOR NO; HELP-PROMPT:      Was the treatment related to Head
 and/or Neck Cancer. DESCRIPTION:      Enter 'Y' if this procedure is related
 to treatment for head/neck cancer.  Enter 'N' is the procedure is unrelated to
 the patient's head/neck cancer. 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: PROSTHETICS
SUBSCRIBING PACKAGE: SURGERY
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES

NUMBER: 4206                            IA #: 4206
  DATE CREATED: AUG 15, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORQPTQ1                      NAME: TEAMPTS~ORQPTQ1
  ID: ORQPTQ1
 GENERAL DESCRIPTION:   CPRS Patient List api's.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: TEAMPTS
 COMPONENT DESCRIPTION:   Returns the list of patients in an OE/RR Team.  
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Variable passed in by reference to accept and return
 the list of patients: 
     Y(#) = DFN ^ NAME, 
  or Y(1) =  ^ message, if an error or empty, 
  or @Y(#) if Y contains an open global reference and TMPFLAG is true.  
VARIABLES: TEAM                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN in OE/RR List file #100.21.  
VARIABLES: TMPFLAG                      TYPE: Input
 VARIABLES DESCRIPTION:   Boolean flag, indicating if Y contains an open global
 root for returning the list.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City

NUMBER: 4207                            IA #: 4207
  DATE CREATED: AUG 15, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORQPTQ2                      NAME: PTS~ORQPTQ2
  ID: ORQPTQ2
 GENERAL DESCRIPTION:   CPRS Patient List api's.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CLINPTS
 COMPONENT DESCRIPTION:   Returns a list of patients with a clinic appt within
 a date range.  
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Variable passed in by reference to accept and return
 the list of patients: 
     Y(#) = DFN ^ NAME 
  or Y(1) =  ^ message, if an error or empty.  
VARIABLES: CLINIC                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN in the Hospital Location file #44.  
VARIABLES: START                        TYPE: Input
 VARIABLES DESCRIPTION:   Date to begin searching for appointments, in a
 FileMan compatible format.  
VARIABLES: STOP                         TYPE: Input
 VARIABLES DESCRIPTION:   Date to end searching for appointments, in a FileMan
 compatible format.  
COMPONENT/ENTRY POINT: PROVPTS
 COMPONENT DESCRIPTION:   Returns a list of patients assigned to a provider.  
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Variable passed in by reference to accept and return
 the list of patients: 
     Y(#) = DFN ^ NAME 
  or Y(1) =  ^ message, if an error or empty.  
VARIABLES: PROV                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN in the New Person file #200 of the desired
 provider.  
COMPONENT/ENTRY POINT: SPECPTS
 COMPONENT DESCRIPTION:   Returns a list of patients assigned to a treating
 specialty.  
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Variable passed in by reference to accept and return
 the list of patients: 
     Y(#) = DFN ^ NAME 
  or Y(1) =  ^ message, if an error or empty.  
VARIABLES: SPEC                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN in the Facility Treating Specialty file #45.7.  
COMPONENT/ENTRY POINT: WARDPTS
 COMPONENT DESCRIPTION:   Returns a list of patients assigned to a ward.  
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Variable passed in by reference to accept and return
 the list of patients: 
     Y(#) = DFN ^ NAME 
  or Y(1) =  ^ message, if an error or empty.  
VARIABLES: WARD                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN in the Ward Location file #42.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 ***************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ***************************************************
  
 HMP routines HMPCAC calls the WARDPTS~ORQPTQ2 API to get a list of patients
 assigned to a ward. HMPCAC and HMPPDL call the PROVPTS~ORQPTQ2 API to get a
 list of patients for a provider. HMPCAC and HMPPDL call the SPECPTS~ORQPTQ2
 API to get a list of patients for a treating specialty. HMPCAC calls the
 CLINPTS~ORQPTQ2 API to get a list of patients with appointments in the clinic
 for a date range.  

NUMBER: 4208                            IA #: 4208
  DATE CREATED: DEC 13, 2010            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Other
  NAME: MY TEST                         STATUS: Pending
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: 1

NUMBER: 4209                            IA #: 4209
  DATE CREATED: MAR 01, 2007            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  NAME: VistALink J2M Java APIs [vljFoundationsLib-x.x.x.xxx.jar]
 GENERAL DESCRIPTION:   
    This ICR describes the supported VistALink J2M (v1.5) Java APIs for 
    the vljFoundationsLib-x.x.x.xxx.jar file.  
  
    It is strongly recommended that you consult the javadoc for the 
    VistALink J2M software for more detail on all supported VistALink 
    J2M Java APIs.  
  
  
    Jar: 
       vljFoundationsLib-x.x.x.xxx.jar 
  
    Foundations Library Utilities Packages: 
       gov.va.med.crypto 
       gov.va.med.environment 
       gov.va.med.exception 
       gov.va.med.monitor.time 
       gov.va.med.net 
       gov.va.med.xml 
  
  
  
    Package gov.va.med.crypto 
    =========================
       Contains cryptology related utility classes (Kernel hash).  
     
       Class Summary 
       =============
          VistaKernelHash 
             Implements static methods to provide the encoding algorithms 
             used by the RPC Broker and Kernel to encode and decode data 
             strings.  
     
       Exception Summary 
       =================
          VistaKernelHashCountLimitExceededException 
             Represents an exception identifying that the Hash Count Limit 
             (for a call to the VistaKernelHash encrypt method) has been 
             exceeded.  
     
     
    Package gov.va.med.environment 
    ==============================
       APIs for accessing J2EE environment information.  
     
       Class Summary 
       =============
          Environment 
             Environment settings for J2EE server use.  
     
          ServerType 
             Enumerated J2EE server types.  
     
     
    Package gov.va.med.exception 
    ============================
       Contains exception handling utility classes.  
     
       Interface Summary 
       =================
          FoundationsExceptionInterface 
             Represents the interface that all Foundations exceptions 
             implement.  
      
       Class Summary 
       =============
          ExceptionUtils 
             Exposes utility methods for handling exceptions.  
     
       Exception Summary 
       =================
          FoundationsException 
             Nested exception handling code is identical to 
             VistaLinkResourceException nested exception handling code.  
     
     
    Package gov.va.med.monitor.time 
    ===============================
       Contains resource execution time monitoring utility classes.  
     
       Class Summary 
       =============
          AuditTimer 
             This class gives an easy way to capture performance statistics 
             and log them to a log file.  
     
     
    Package gov.va.med.net 
    ======================
       Foundations TCP socket functionality for communicating with IP 
       endpoints.  
     
       Class Summary 
       =============
          SocketManager 
             Represents a socket that can be used to communicate with IP 
             endpoints.  
     
       Exception Summary 
       =================
          VistaSocketException 
             Represents an exception thrown during read/write operations 
             on a socket.  
  
          VistaSocketTimeOutException 
             Represents an exception identifying a timeout has occurred 
             during read/write operations.  
     
     
    Package gov.va.med.xml 
    ======================
       General Foundations utility class for working with XML.  
  
       Class Summary 
       =============
          XmlUtilities 
             This class contains a number of static utility methods to help 
             developers work with XML documents, nodes, attributes and 
             strings.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
KEYWORDS: VISTALINK SECURITY

NUMBER: 4210                            IA #: 4210
  DATE CREATED: AUG 15, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORQQVS                       NAME: ORQQVS
  ID: ORQQVS
 GENERAL DESCRIPTION:   APIs to return the details or text of documents.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DETNOTE
 COMPONENT DESCRIPTION:   Returns the text of progress note(s) tied to a visit. 
 
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Variable passed in by reference to accept and return
 the list of patients as Y(#) = line of text.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in Patient file #2.  
VARIABLES: VISIT                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN in Visit file #9000010.  
COMPONENT/ENTRY POINT: DETSUM
 COMPONENT DESCRIPTION:   Returns the text of a discharge summary tied to an
 inpatient stay.  
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Variable passed in by reference to accept and return
 the list of patients as Y(#) = line of text.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in Patient file #2.  
VARIABLES: VISIT                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN in Visit file #9000010.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City

NUMBER: 4211                            IA #: 4211
  DATE CREATED: AUG 15, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORWCV                        NAME: VST~ORWCV
  ID: ORWCV
 GENERAL DESCRIPTION:   Returns patient visits within a timeframe.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: VST
 COMPONENT DESCRIPTION:   Returns future appointments and past visits for a
 patient in a date range.  
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Variable passed in by reference to accept and return
 the list of visits as 
   Y(#) = ID ^ Visit Date ^ Clinic Name ^ Status where ID is a 3 ;-piece string
 containing the visit type [past (V)isit, future (A)ppointment, or (I)npatient
 stay], date/time, and pointer to the Hospital Location file #44.  All dates
 are in internal FileMan format.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in Patient file #2.  
VARIABLES: START                        TYPE: Input
 VARIABLES DESCRIPTION:   Date to begin searching for visits, in FileMan
 format.  
VARIABLES: STOP                         TYPE: Input
 VARIABLES DESCRIPTION:   Date to end searching for visits, in FileMan format.  
VARIABLES: SKIP                         TYPE: Input
 VARIABLES DESCRIPTION:   Boolean value, to indicate that inpatient stays
 should be skipped if true.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City

NUMBER: 4212                            IA #: 4212
  DATE CREATED: AUG 15, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORWPCE                       NAME: ORWPCE
  ID: ORWPCE
 GENERAL DESCRIPTION:   CPRS visit utilities 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: HASVISIT
 COMPONENT DESCRIPTION:   Determines if a document is tied to a visit or not.  
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Variable passed in by reference to accept and return
 the result of this call, as true (1) or false (0) or unknown (-1).  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in the TIU Document file #8925.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in Patient file #2.  
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in Hospital Location file #44.  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   Date of the document, in FileMan format.  
COMPONENT/ENTRY POINT: SCSEL(VAL,DFN,ATM,LOC,VST)
 COMPONENT DESCRIPTION:   This component returns the service-connected
 conditions that may be selected for the purpose of a patient visit.  
VARIABLES: VAL                          TYPE: Both
 VARIABLES DESCRIPTION:   This variable is passed by reference, and is returned
 in the format: 
  
     VAL=SCallow^SCdflt;AOallow^AOdflt;IRallow^IRdflt;ECallow^ECdflt; 
         MSTallow^MSTdflt;HNCallow^HNCdflt;CVAllow^CVDflt 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PATIENT (#2) file.  
VARIABLES: ATM                          TYPE: Input
 VARIABLES DESCRIPTION:   The date and time of an encounter.  
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the HOSPITAL LOCATION (#44) file for the
 location associated with the encounter.  
VARIABLES: VST                          TYPE: Input
 VARIABLES DESCRIPTION:   This optional variable is the ien of the visit from
 the VISIT (#9000010) file.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City

NUMBER: 4213                            IA #: 4213
  DATE CREATED: AUG 15, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORWPCE2                      NAME: ORWPCE2
  ID: ORWPCE2
 GENERAL DESCRIPTION:   Returns CPRS visit parameter values.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ASKPCE
 COMPONENT DESCRIPTION:   Returns value of ORWPCE ASK ENCOUNTER UPDATE
 parameter, which determines under what conditions a user should be requested
 to enter encounter data when signing a document.  
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Variable passed in by reference to accept and return
 the result of this call; see ORWPCE ASK ENCOUNTER UPDATE parameter definition
 for possible values.  
VARIABLES: USER                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN in New Person file #200.  
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in Hospital Location file #44.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City

NUMBER: 4214                            IA #: 4214
  DATE CREATED: AUG 15, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORWPCE3                      NAME: ORWPCE3
  ID: ORWPCE3
 GENERAL DESCRIPTION:   CPRS utilities to return encounter data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PCE4NOTE
 COMPONENT DESCRIPTION:   Returns encounter data for a document.  
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Variable passed in by reference to accept and return
 the results of this call.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in TIU Document file #8925.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in Patient file #2.  
VARIABLES: VSITSTR                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional 2 ;-piece string consisting of the visit
 location _";"_ date, used if IEN is not defined.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 ***************************************************
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application. If HMP is reactivated in the
 future, the HMP project team should review the access provided by this ICR
 with the custodial application before reactivating HMP's subscription to this
 ICR.  
 ***************************************************
  
 HMP routine HMPDJ02 calls the PCE4NOTE^ORWPCE3 to retrieve encounter data for
 a document.  

NUMBER: 4215                            IA #: 4215
  DATE CREATED: AUG 15, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORWPT                        NAME: ORWPT
  ID: ORWPT
 GENERAL DESCRIPTION:   CPRS patient utilities.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$AGE
 COMPONENT DESCRIPTION:   Returns the age of a patient, as of today or date of
 death if deceased.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in Patient file #2.  
VARIABLES: DOB                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's date of birth, in FileMan format.  
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City

NUMBER: 4216                            IA #: 4216
  DATE CREATED: AUG 25, 2003            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDAMA204
  NAME: PATIENT APPOINTMENT EXISTS      ID: SDAMA204
 GENERAL DESCRIPTION:   This DBIA contains an API that checks for the existence
 of any appointment for a specific patient.  
  STATUS: Active
KEYWORDS: PATIENT
KEYWORDS: APPOINTMENT
KEYWORDS: DFN
COMPONENT/ENTRY POINT: $$PATAPPT
 COMPONENT DESCRIPTION:   The call to this entry point will return 0,1,-1
 depending on the existence of patient appointments.  In addition, if the
 returned value is -1 (error), the ^TMP($J,"SDAMA204","PATAPPT","ERROR") will
 be created with the specific error information.  
VARIABLES: SDDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN 
VARIABLES: TMP($J,SDAMA204,PATAPPT)     TYPE: Output
 VARIABLES DESCRIPTION:   If there is a return value of -1 from this extrinsic
 function, the ^TMP($J,"SDAMA204","PATAPPT","ERROR") node will be created with
 the specific error code and message.  
  
 The calling application is responsible for deleting the temporary global when
 they have finished processing the errors.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE

NUMBER: 4217                            IA #: 4217
  FILE NUMBER: 4                        GLOBAL ROOT: DIC(4,
  DATE CREATED: AUG 20, 2003            CUSTODIAL PACKAGE: VDEM
  USAGE: Private                        TYPE: File
  ROUTINE: VDEMINST                     NAME: VDEMINST Routine calling File 4
  ID: VDEMINST
GLOBAL REFERENCE: DIC(4,IEN,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA was created becuase of the routines dependancy
 with the Instatution file #4. The routine will loop through the file and
 extract data elements of key fields. The data will be used to support the VDEM 
 extraction application.  
  STATUS: Withdrawn
KEYWORDS: VDEM
KEYWORDS: VDEMINST
KEYWORDS: Institution
COMPONENT/ENTRY POINT: START
 COMPONENT DESCRIPTION:   This entry point is called be the VDEM driver
 routine. This is the starting point for the locations extraction which will
 call several globals to extract the required data.  
VARIABLES: IEN                          TYPE: Used
 VARIABLES DESCRIPTION:   This variable will is the Internal Entry Number
 subscript for DIC(4,ien..  
VARIABLES: DATAO                        TYPE: Used
 VARIABLES DESCRIPTION:   This is the data string from the zero node of
 DIC(4,ien,0). Data is extracted from the string and used to build the out put. 
 
VARIABLES: DATA99                       TYPE: Used
 VARIABLES DESCRIPTION:   This variable is a data string created from
 DIC(4,ien,99).  
VARIABLES: MULTI                        TYPE: Both
 VARIABLES DESCRIPTION:   This variable is a flag from in the global
 ^DIC(4,IEN,"DIV".....  
VARIABLES: ASTYPE                       TYPE: Used
 VARIABLES DESCRIPTION:   This Variable is created from global 
 ^DIC(4.05,ASTYPEN,0)....  

NUMBER: 4218                            IA #: 4218
  FILE NUMBER: 71                       GLOBAL ROOT: RAMIS(71
  DATE CREATED: AUG 20, 2003            CUSTODIAL PACKAGE: VDEM
  USAGE: Private                        TYPE: File
  ROUTINE: VDEMRADN                     NAME: VDEMRADN Routine Calling file #71
  ID: VDEMRADN
GLOBAL REFERENCE: RAMIS(71,IEN,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: TYPE OF PROCEDURE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: ORIGINAL PROCEDURE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: CPT CODE
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: TYPE OF IMAGING
  LOCATION: 0;12                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RAMIS(71,IEN,I)
FIELD NUMBER: 100                       FIELD NAME: INACTIVATION DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RAMIS(71,IEN,MDL,D1,0)
FIELD NUMBER: .01                       FIELD NAME: MODALITY
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA was created becuase of the routines dependancy
 with the file #71. The routine will loop through the file and extract data
 elements from key fields. The data will be used to support the VDEM extration
 application.  
  STATUS: Withdrawn
KEYWORDS: VDEM
KEYWORDS: VDEMRADN

NUMBER: 4219                            IA #: 4219
  DATE CREATED: AUG 20, 2003            CUSTODIAL PACKAGE: VDEM
  USAGE: Supported                      TYPE: Routine
  ROUTINE: VDEMLABG                     NAME: VDEMLABG
  ID: VDEMLABG
 GENERAL DESCRIPTION:   This routine is used by the VDEM to handle Lab
 information. It uses global ^LAB(60, ^LAB(61,  ^LAB(62, ^LAB(64.061, ^LAB(95.3
 and LAM(......  
  STATUS: Withdrawn
KEYWORDS: VDEM
COMPONENT/ENTRY POINT: GO
 COMPONENT DESCRIPTION:   This point is called from the VDEM routine. The
 routine gets pasted peramiters which will determine the type of data that will
 be extracted.  

NUMBER: 4220                            IA #: 4220
  FILE NUMBER: 46                       GLOBAL ROOT: DGCPT(46,
  DATE CREATED: NOV 17, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4220-A
  ORIGINAL NUMBER: 4220                 ID: DGCPT(46,
GLOBAL REFERENCE: DGCPT(46,
FIELD NUMBER: .01                       FIELD NAME: CPT CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to Inpatient CPT file 
 GLOBAL DESCRIPTION:   This file is used to capture inpatient professional
 services for billing.  Entries from this file are used on the HCFA 1500.  This
 file can be used to capture billing information for observation visits  The 
 date and time of the professional service is used as a unique identifier for
 the professional service.  
 GENERAL DESCRIPTION:   Allow the use of the .01 field in file 46 to logically
 conect the orders file to the Inpatient CPT file.  All access to the Inpatient
 CPT file will be made using the DGAPI routine.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 01, 2020
KEYWORDS: DGAPI
KEYWORDS: Billing Awareness
KEYWORDS: PTF
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
SUBSCRIBING PACKAGE: SURGERY
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4221                            IA #: 4221
  FILE NUMBER: 46.1                     GLOBAL ROOT: DGICD9(46.1,
  DATE CREATED: NOV 12, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INPATIENT POV FILE
  ID: DGICD9(46.1,
GLOBAL REFERENCE: DGICD9(46.1,
FIELD NUMBER: .01                       FIELD NAME: DIAGNOSIS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
SUBSCRIBING PACKAGE: SURGERY

NUMBER: 4222                            IA #: 4222
  FILE NUMBER: 9002313.29               GLOBAL ROOT: BPS(9002313.29
  DATE CREATED: DEC 13, 2010            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: BPS NCPDP DELAY REASON CODE
  ID: BPS(9002313.29
GLOBAL REFERENCE: BPS(9002313.29,D0
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: BRIEF DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the brief description as defined by the NCPDP
 standard.  
FIELD NUMBER: .03                       FIELD NAME: FULL DESCRIPTION
  LOCATION: 1;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the full description as defined by the NCPDP
 standard.  
FIELD NUMBER: 2                         FIELD NAME: INACTIVE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   If set to 1/INACTIVE, then this entry cannot be entered
 or selected by the user.  
 GENERAL DESCRIPTION:   Integrated Billing (IB) is using a Fileman look-up into
 the BPS NCPDP DELAY REASON CODE (#9002313.29) file in order to ask the user to
 choose a valid delay reason code during the IB back billing process.  
  
 Amendment: Effective 5/15/23, added fields .02, .03 and 2 
  STATUS: Active
KEYWORDS: BPS
KEYWORDS: DELAY REASON CODE
KEYWORDS: NCPDP
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAY 16, 2023

NUMBER: 4223                            IA #: 4223
  FILE NUMBER: 52.91                    GLOBAL ROOT: PS(52.91,
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA4223
  ID: PS(52.91,
GLOBAL REFERENCE: PS(52.91,DA,0)
 GLOBAL DESCRIPTION:   Direct read access to the 0 node.  
 GENERAL DESCRIPTION:   The Scheduling package looks at the 0 node of the TPB
 ELIGIBILITY file (#52.91) to see if an entry has already been created for a
 patient in that file. This is done so that on subsequent installs of patch
 PSO*7*145 (Phase I of the Transitional Pharmacy Benefit project), a patient is
 not flagged as potentially being automatically entered in that file by the 
 Appointment and EWL logic, if a patient is already in the file from a previous
 install. This is done to prevent automatic changes to an entry that has
 already been manually edited.  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
 SUBSCRIBING DETAILS:   A check will be done on the 0 node of the TPB
 ELIGIBILITY file (#52.91) when the post-init is run for patch PSO*7.0*145.  

NUMBER: 4224                            IA #: 4224
  DATE CREATED: SEP 04, 2003
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: CSLARBC
  NAME: Controlled subscription from AR to CSL via CSLARBC routine
  ID: CSLARBC
 GENERAL DESCRIPTION:   CoreFLS will replace three VistA applications - IFCAP,
 AEMS/MERS, and FMS which is the central accounting software used in the VA.
 Hence, VistA applications, which used to communicate with these applications,
 will now communicate with the COTS applications in CoreFLS. To be able to
 provide real-time integration between CoreFLS and VistA, HL7 messaging
 protocol was selected. This integration agreement will address the CSL
 interface application linking the VistA AR system with the Oracle based
 CoreFLS financial system.  
  STATUS: Active
KEYWORDS: CSLAR
KEYWORDS: CSL AR
COMPONENT/ENTRY POINT: DRV
 COMPONENT DESCRIPTION:   Invoked by AR routine  to create HL7 message with
 multiple line data. If the total record number is more than 100, CSL will
 create multiple HL7 messages that each contains a maximum of 100 records.
 These HL7 messages will be sent to CoreFLS by VistA HL7 package. CoreFLS will
 return the pre-validation status in the application acknowledgement.  
  
 The data from AR will be passed in global ^XTMP(RTN) where RTN is the routine
 name which invoked routine CSLARBC. The layout of global ^XTMP(RTN) is
 categorized by different events: 
  
 210 (Cash Receipt To GL)      221 (Applied Suspense to GL) 225 (CR without
 SSN)          223 (TR Document) 
 ------------------------------------------------------------
 Piece  Description                  Description            
 ------------------------------------------------------------
   1    CoreFLS Fund                CoreFLS Fund 
   2    RSC Fund                    RSC Fund 
   3    Station Number              Station Number 
   4    Receipt Number              Receipt Number 
   5    Transaction Type            Transaction Type 
   6    Bill Number                 Bill Number 
   7    Bill Category               Bill Category 
   8    Unapplied Deposit Number    Unapplied Deposit Number 
   9    Accounting period Date      Accounting period Date 
  10    Transaction Date            Transaction Date 
  11    Accomplished Date           Increase/Decrease Indicator 
  12    Principal Amount            Principal Amount 
  13    Interest Amount             Interest Amount 
  14    Admin. Amount               Admin. Amount 
  15    Court/Marshall Fee          Court/Marshall Fee 
  16    Federal Trading Partner     Federal Trading Partner 
  17    DUNS#                       DUNS# 
  18    215 Deposit#                AR Unique Identifier 
  19    VA Business Line            Transaction Code 
  20    Program Part II and III     User SSN 
  21    Field Activity              VA Business Line 
  22    AR Unique Identifier        Program Part II and III 
  23    Transaction Code            Field Activity 
  24    User SSN 
VARIABLES: RTN                          TYPE: Input
 VARIABLES DESCRIPTION:   First subscript of ^XTMP (input data) 
VARIABLES: CSLEVI                       TYPE: Input
 VARIABLES DESCRIPTION:   AR event number 
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULT = 1, HL7 message successfully generated.  
 RESULT = 0^error message, HL7 message generation failed.  
COMPONENT/ENTRY POINT: ACK
 COMPONENT DESCRIPTION:   Invoked by VistA HL7 package to process application
 acknowledgement returned by CoreFLS. The acknowledgement message will be
 passed to AR by calling routine GETACK^PRCAFLS3(RCN,ACKCODE,.CSLB) Where RCN:
 Receipt number 
   ACKCODE: Acknowledgement code 
      CSLB: Acknowledgement message array 
            Each line in the array contains 
               Error Code ^ Error Description ^ IEN (file 347.6) 
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany
 SUBSCRIBING DETAILS:   AR will invoke CSLARBC to generate HL7 messages to pass
 multiple records to CoreFLS.  
  

NUMBER: 4225                            IA #: 4225
  DATE CREATED: AUG 26, 2003            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: HLEVAPI
  NAME: Event Monitor APIs - HLEVAPI    ID: HLEVAPI
 GENERAL DESCRIPTION:   Enhancement patch HL*1.6*106 contains the VistA HL7
 Event Monitor system.  The Event Monitor system facilitates the process of
 monitoring the VistA HL7 environment for conditions and events, as well as
 notification of the VistA HL7 support and development personnel.  
  
 The Event Monitor system includes new files and options, as well as the eight
 application program interfaces (APIs) documented in this integration
 agreement.  
  
 The Event Monitor system is built around: 
  
  - Monitors 
  - Master Job 
  
 The Monitor is built around an entry in the HL7 Monitor file (#776.1) that
 "points" to an M code API.  The monitor also includes a field that specifies
 how many minutes should elapse between every "run" of the monitor. 
  
 The Master Job runs every few hours perpetually.  It checks every monitor 
 entered in the HL7 Monitor file to determine whether the monitor should be 
 run.  If it is time for a monitor "run", the master job queues a background
 job for the specific monitor.  
  
 The primary task of the master job is to start individual monitor jobs, and to
 record the result of it's evaluation of every monitor; whether it was started
 or not, and the reason for the action taken.  
  
 The APIs created by patch HL*1.6*106 and included in integration agreements
 4225, 4226 and 4227 are: 
  
  - $$START^HLEVAPI        - CHECKIN^HLEVAPI         - CHECKOUT^HLEVAPI 
  - MAILIT^HLEVAPI         - ABORT^HLEVAIP           - VARIABLE^HLEVAPI 
  - ONOFF^HLEVAPI0         - APPSTAT^HLEVAPI1        - MSGTEXT^HLEVAPI 
  - RUNDIARY^HLEVAPI1 
  
 Application developers wishing to use the Event Monitor system, including 
 these APIs, must secure permission from the VistA HL7 development team.  
  
 --------------------------------------------------------------------------
  
 Please peruse the APIs documented in this integration agreement in the 
 following order: 
  
  - START^HLEVAPI         - CHECKIN^HLEVAPI        - CHECKOUT^HLEVAPI 
  - VARIABLE^HLEVAPI 
  
 The above APIs form a conceptual unit.  
  
 The MAILIT^HLEVAPI and the ABORT^HLEVAPI APIs may be reviewed in any order,
 but they should be reviewed after the four APIs listed above.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CHECKIN
 COMPONENT DESCRIPTION:   
 ==========================================================================
 Please read the START^HLEVAPI API section before continuing, as that API 
 section contains important foundation material referred to below.  
 ==========================================================================
  
 The CHECKIN^HLEVAPI API should be called every 30 to 60 seconds during the
 running of a monitor.  This API records the time "now" in a timestamp field,
 and stores the values of any declared variables.  
  
 If the monitor's M code runs for less then 60 seconds, this API does not need
 to be called.  
  
 The syntax for this call is: 
  
      D CHECKIN^HLEVAPI 
  
 There are no API parameters.  
COMPONENT/ENTRY POINT: CHECKOUT
 COMPONENT DESCRIPTION:   
 ==========================================================================
 Please read the START^HLEVAPI API section before continuing, as that API 
 section contains important foundation material referred to below.  
 ==========================================================================
  
 The CHECKOUT^HLEVAPI API should be called after all M code execution has 
 completed.  This API stores all declared variables, refreshes the timestamp,
 and marks the status of the monitor "run" finished.  
  
 The syntax for this call is: 
  
      D CHECKOUT^HLEVAPI 
  
 There are no API parameters.  
COMPONENT/ENTRY POINT: MAILIT
 COMPONENT DESCRIPTION:   When a monitor's M code finishes, a Mailman message
 can be sent to local and remote recipients.  The MAILIT^HLEVAPI API is used to
 send the message.  
  
 The following M code illustrates the use of the MAILIT^HLEVAPI API.  
  
    LOOP   ; Looping code to count entries in file 773 
           ;
           S VAR("CT")="773-CT" ; Defines the variable to be tracked later 
           D START^HLEVAPI(.VAR) 
           ;
           S IEN=0,CT=0 
           F  S IEN=$O(^HLMA(IEN)) Q:'IEN  D 
           .  S CT=CT+1 
           .  I '(CT#100) D CHECKIN^HLEVAPI 
           ;
           D CHECKOUT^HLEVAPI 
           ;
           D MAILIT^HLEVAPI(HLEVIENE,HLEVIENJ) 
           ;
           Q 
  
  
 The MAILIT^HLEVAPI API has three possible parameters, and the third parameter
 is discussed below.  The syntax above is the simplest allowed form and
 involves two parameters.  In this example, HLEVIENE and HLEVIENJ are passed as
 the two parameters.  These variables are always defined, and so the
 application developer doesn't need to define these variables or do anything
 other than "just pass the variables." 
  
 In the above example, no recipients for the message are in any way "declared"
 or defined.  This is because the recipients for the message sent by this API
 have already been defined as part of the monitor definition in the HL7 Monitor
 file (#776.1) entry.  
  
 The following example illustrates how local and remote recipients can be 
 passed on-the-fly into the MAILIT^HLEVAPI API.  
  
    LOOP   ; Looping code to count entries in file 773 
           ;
           S VAR("CT")="773-CT" ; Defines the variable to be tracked later 
           D START^HLEVAPI(.VAR) 
           ;
           S IEN=0,CT=0 
           F  S IEN=$O(^HLMA(IEN)) Q:'IEN  D 
           .  S CT=CT+1 
           .  I '(CT#100) D CHECKIN^HLEVAPI 
           ;
           D CHECKOUT^HLEVAPI 
           ;
           S XMY("FirstLast")="" 
           S XMY("HL7SystemMonitoring@DNS")="" 
           D MAILIT^HLEVAPI(HLEVIENE,HLEVIENJ,.XMY) 
           ;
           Q 
  
 In this example, the XMY local variable array is defined and passed by 
 reference into MAILIT^HLEVAPI. Any XMY-based recipients created as shown above
 are added to the recipients defined in the monitor entry in the HL7 Monitor
 file.  
  
 -------------------------------------------------------------------------
  
 Please read the documentation included in patch HL*1.6*106 for additional 
 information about this API and the general use of the Event Monitor system.  
VARIABLES: HLEVIENE                     TYPE: Input
 VARIABLES DESCRIPTION:   The HLEVIENE variable is the internal entry number of
 the 
COMPONENT/ENTRY POINT: START
 COMPONENT DESCRIPTION:   M code that is interfaced with the Event Monitor
 system using the APIs documented in this interface agreement, and agreements
 4226 and 4227 must begin with a call to START^HLEVAPI(), and must call
 CHECKOUT^HLEVAPI after all M code execution has completed.  If the time of M
 code execution is longer than one minute, M code should call CHECKIN^HLEVAPI 
 every 30-60 seconds.  
  
 The following M code example illustrates how these APIs should be called.  
  
    LOOP   ; Looping code to count entries in file 773 
           ;
           ; Define the variable to be tracked later...  
           S VAR("CT")="773-CT" 
           ; Call START, passing in by reference the variable...  
           D START^HLEVAPI(.VAR) 
           ;
           S IEN=0,CT=0 
           F  S IEN=$O(^HLMA(IEN)) Q:'IEN  D 
           .  S CT=CT+1 
           .  ; Check in every few seconds...  
           .  I '(CT#1000) D CHECKIN^HLEVAPI ; Variable CT stored...  
           ;
           D CHECKOUT^HLEVAPI ; Variable CT stored here too...  
           ;
           Q 
  
 In the above example, the variable CT is "declared" and passed into the 
 START^HLEVAPI API.  (The "773-CT" is an explanation of the variable being 
 tracked that is included in some report views.)  Since the CT variable has
 been declared, the CHECKIN^HLEVAPI and CHECKOUT^HLEVAPI APIs know to record
 it's current value when called.  
  
 It is not required to pass variables into the START^HLEVAPI API.  If this is
 not done, the call to START^HLEVAPI will look the code below.  
  
           D START^HLEVAPI() 
  
 The VARIABLE^HLEVAPI API allows the declaration of variables on-the-fly, at
 any time after the call to START^HLEVAPI.  
  
 -------------------------------------------------------------------------
  
 Please read the documentation included in patch HL*1.6*106 for additional 
 information about this API and the general use of the Event Monitor system.  
VARIABLES: VAR                          TYPE: Input
 VARIABLES DESCRIPTION:   The START^HLEVAPI(.VAR) API contains one
 pass-by-reference parameter.  The passing of variables into this API is
 optional.  
  
 The syntax for a call to START^HLEVAPI where variables are passed by reference
 is: 
  
    S VAR("CT")="CT-773" 
    D START^HLEVAPI(.CT) 
  
 Of course, any number of entries in the VAR() local array are allowed to be
 passed into the START^HLEVAPI API.  
  
 When VAR("CT")="CT-773" was set above, the variable CT was "declared", and so
 will be stored every time CHECKIN^HLEVAPI and CHECKOUT^HLEVAPI is called
 subsequently.  And, "CT-773" is a slightly more understandable "explanation"
 for the variable being tracked that is included in some screen displays.  
  
 The explanation (what is to the right of the equals sign) for a variable must
 not exceed 10 characters.  
  
 When no variables are declared, the call to START^HLEVAPI will look like this: 
  
    D START^HLEVAPI() 
  
 -------------------------------------------------------------------------
  
 Please read the documentation included in patch HL*1.6*106 for additional 
 information about this API and the general use of the Event Monitor system.  
COMPONENT/ENTRY POINT: ABORT
 COMPONENT DESCRIPTION:   
 ==========================================================================
 Please read the START^HLEVAPI API section before continuing, as that API 
 section contains important foundation material referred to below.  
 ==========================================================================
  
 The ABORT^HLEVAPI API should be called if the execution of the M code-based
 monitor should stop prematurely.  (This usually occurs when the Taskman job
 has been externally requested to stop.) 
  
 The syntax for this call is: 
  
      D ABORT^HLEVAPI("E",REA) 
  
 The value "E" should always be passed in the first parameter position, and the
 second parameter should include the reason for the monitor termination.  (The
 termination reason must not exceed 10 characters.) 
  
 The following M code illustrates the use of the ABORT^HLEVAPI API.  
  
    LOOP   ; Looping code to count entries in file 773 
           ;
           D START^HLEVAPI() 
           ;
           S IEN=0,CT=0,ABRT=0 
           F  S IEN=$O(^HLMA(IEN)) Q:'IEN!(ABRT)  D 
           .  S CT=CT+1 
           .  I '(CT#100) D 
           .  .  D CHECKIN^HLEVAPI 
           .  .  I $$S^%ZTLOAD S ABRT=1 ; Taskman request to stop 
           ;
           I ABRT D ABORT^HLEVAPI("E","Tskmn Req") 
           I 'ABRT D CHECKOUT^HLEVAPI 
           ;
           Q 
  
 Note that the ABORT^HLEVAPI API should be called instead of CHECKOUT^HLEVAPI
 when the monitor stops prematurely.  
VARIABLES: REA                          TYPE: Input
 VARIABLES DESCRIPTION:   The second parameter of the ABORT^HLEVAPI API should
 contain the reason for premature stoppage of the monitor.  This variable must
 not exceed 10 characters.  
COMPONENT/ENTRY POINT: VARIABLE
 COMPONENT DESCRIPTION:   The START^HLEVAPI API allows the declaration of
 variables to be tracked and stored by the CHECKIN^HLEVAPI and CHECKOUT^HLEVAPI
 APIs.  The VARIABLE^HLEVAPI API is very similar to the method used by
 START^HLEVAPI API in variable declaration, but more powerful.  
  
 The following M code illustrates the use of the VARIABLE^HLEVAPI API to 
 declare variables to be tracked on-the-fly.  
  
    LOOP   ; Looping code to count entries in file 773 
           ;
           D START^HLEVAPI() ; No variables declared and pssed in...  
           ;
           S VAR("CT")="CT-773",VAR("HLEV*")="HL Array" 
           D VARIABLE^HLEVAPI(.VAR) 
           ;
           S IEN=0,CT=0 
           F  S IEN=$O(^HLMA(IEN)) Q:'IEN  D 
           .  S CT=CT+1 
           .  I '(CT#100) D CHECKIN^HLEVAPI 
           ;
           D CHECKOUT^HLEVAPI 
           ;
           Q 
  
 In the above example, two "variables" are declared: CT and HLEV*.  The 
 declaration of the CT variable will result in the storage of the CT variable
 every time CHECKIN^HLEVAPI and CHECKOUT^HLEVAPI is called.  With the second
 variable HLEV*, the asterisk following "HLEV" is a wild card and instructs the
 CHECKIN^HLEVAPI and CHECKOUT^HLEVAPI APIs to store all local variables
 beginning with HLEV.  (E.g., this would result in HLEVRSLT and HLEV(25) being
 stored.) 
VARIABLES: VAR                          TYPE: Input
 VARIABLES DESCRIPTION:   The only parameter for this API is a
 pass-by-reference variable and is documented above in the VARIABLE^HLEVAPI
 section.  

NUMBER: 4226                            IA #: 4226
  DATE CREATED: AUG 26, 2003            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: HLEVAPI0
  NAME: Event Monitor APIs - HLEVAPI0   ID: HLEVAPI0
 GENERAL DESCRIPTION:   Integration agreements 4225, 4226 and 4227 cover the
 supported APIs for the VistA HL7 Event Monitor system.  Integration agreement
 4225 covers the HLEVAPI routine APIs, and agreement 4227 covers the HLEVAPI1
 routine APIs.  This agreement covers the HLEVAPI0 routine's APPSTAT^HLEVAPI0
 API.  
  
 Please read the GENERAL DESCRIPTION of integration agreement# 4225 before 
 continuing.  
  
 -------------------------------------------------------------------------
  
 Monitors are defined in the HL7 Monitor file (#776.)  The STATUS field (#2) in
 this file can be used to turn monitors on (when set to ACTIVE) or off (when
 set to INACTIVE.)  The $$ONOFFM^HLEVAPI0 API, covered by this integration
 agreement, is discussed below.  
  
 Application developers wishing to use the Event Monitor system, including 
 these APIs, must secure permission from the VistA development team.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ONOFFM
 COMPONENT DESCRIPTION:   Monitors are defined in the HL7 Monitor file (#776.) 
 The STATUS field (#2) in this file can be used to turn monitors on (when set
 to ACTIVE) or off (when set to INACTIVE.)  If this field is INACTIVE, no jobs
 will be queued for the monitor.  And, any queued jobs will stop immediately
 when they start before the execution of the monitor's M code.  
  
 The syntax for this API is: 
  
     S X=$$ONOFFM^HLEVAPI0(HLEVIENE,STATUS) 
  
 The variable HLEVIENE is pre-defined for the application developer creating
 calls to $$ONOFFM^HLEVAPI0.  They do not need to create the variable; just
 pass it.  
  
 There are three allowable values for the second STATUS parameter, as shown in
 the following table.  
  
 STATUS Value    Results 
 ------------------------------------------------------------------------
 A        Sets the STATUS field in the HL7 Monitor file to ACTIVE.  I       
 Sets the STATUS field in the HL7 Monitor file to INACTIVE.  ""       Returns
 the current value of the STATUS field.  
VARIABLES: HLEVIENE                     TYPE: Input
 VARIABLES DESCRIPTION:   The HLEVIENE variable is the internal entry number of
 the monitor entry in the HL7 Monitor file (#776.1.)  This variable is
 pre-defined for the application developer, and just needs to be passed into
 the API as the first parameter.  
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   There are three allowable values for the second
 STATUS parameter, as shown in the following table.  
  
 STATUS Value    Results 
 ------------------------------------------------------------------------
 A        Sets the STATUS field in the HL7 Monitor file to ACTIVE.  I       
 Sets the STATUS field in the HL7 Monitor file to INACTIVE.  ""       Returns
 the current value of the STATUS field.  
  
 Passing A or I results in the STATUS field being changed to ACTIVE or INACTIVE
 respectively.  Passing null returns the current value of the STATUS field
 without making any changes to the field.  

NUMBER: 4227                            IA #: 4227
  DATE CREATED: AUG 26, 2003            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: HLEVAPI1
  NAME: Event Monitor APIs - HLEVAPI1   ID: HLEVAPI1
 GENERAL DESCRIPTION:   Integration agreements 4225, 4226 and 4227 cover the
 supported APIs for the VistA HL7 Event Monitor system.  Integration agreement
 4225 covers the HLEVAPI routine APIs, and agreement 4227 covers the HLEVAPI1
 routine APIs.  This agreement covers the HLEVAPI0 routine's APPSTAT^HLEVAPI0
 API.  
  
 Please read the GENERAL DESCRIPTION of integration agreement# 4225 before 
 continuing.  
  
 -------------------------------------------------------------------------
  
 The APIs covered in the COMPONENT sections below are: 
  
  - APPSTAT^HLEVAPI1       - MSGTEXT^HLEVAPI1       - RUNDIARY^HLEVAPI1 
  
 Application developers wishing to use the Event Monitor system, including 
 these APIs, must secure permission from the VistA development team.  
  STATUS: Withdrawn
COMPONENT/ENTRY POINT: APPSTAT
 COMPONENT DESCRIPTION:   The STATUS-APPLICATION field (#5) in the HL7 Monitor
 Job file (#776) can hold up to 10 characters of free-text data.  This field is
 under the control of the application developer.  Data is placed in this field
 using the APPSTAT^HLEVAPI0 API.  
  
 The STATUS-APPLICATION field in no way affects software processes.  It's only
 use is for display by various Event Monitor display options.  
  
 The syntax for the APPSTAT^HLEVAPI1 API is: 
  
    D APPSTAT^HLEVAPI1(STATUS) 
  
 Where the STATUS parameter may be any value up to 10 characters (that doesn
 not contain an up-arrow.) 
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   The STATUS parameter may be any free-text data,
 excluding the up-arrow, up to 10 characters in length.  
COMPONENT/ENTRY POINT: MSGTEXT
 COMPONENT DESCRIPTION:   The MSGTEXT^HLEVAPI1 API populates the MESSAGE TEXT
 word processing field in the HL7 Monitor Job file (#776.)  The syntax for this
 API is: 
  
    D MSGTEXT^HLEVAPI1(GBL) 
  
 Where GBL is a closed global reference to the location of the word-processing
 text to be appended to the MESSAGE TEXT field.  
  
 Examples of valid closed global references are included in the following 
 example calls to this API: 
  
    D MSGTEXT^HLEVAPI1("^TMP(1532135)") 
    D MSGTEXT^HLEVAPI1($NA(^TMP($J,"TXT"))) 
    D MSGTEXT^HLEVAPI1(TEXT) 
  
 If two calls to MSGTEXT^HLEVAPI1 are made, the second call appends it's text
 to the text created by the first call.  
  
 The RUNDIARY^HLEVAPI1 API, also covered by this agreement operates identically
 to this API, except it populates the RUN DIARY word processing field in the HL
 Monitor Job file.  
VARIABLES: GBL                          TYPE: Input
 VARIABLES DESCRIPTION:   The value of GBL must be a closed global reference to
 the location of the word-processing text to be appended to the MESSAGE TEXT
 field.  
COMPONENT/ENTRY POINT: RUNDIARY
 COMPONENT DESCRIPTION:   The RUNDIARY^HLEVAPI1 API populates the RUN DIARY
 word processing field in the HL7 Monitor Job file (#776.)  The syntax for this
 API is: 
  
    D RUNDIARY^HLEVAPI1(GBL) 
  
 Where GBL is a closed global reference to the location of the word-processing
 text to be appended to the RUN DIARY field.  
  
 Examples of valid closed global references are included in the following 
 example calls to this API: 
  
    D RUNDIARY^HLEVAPI1("^TMP(1532135)") 
    D RUNDIARY^HLEVAPI1($NA(^TMP($J,"TXT"))) 
    D RUNDIARY^HLEVAPI1(TEXT) 
  
 If two calls to RUNDIARY^HLEVAPI1 are made, the second call appends it's text
 to the text created by the first call.  
  
 The MSGTEXT^HLEVAPI1 API, also covered by this agreement operates identically
 to this API, except it populates the MESSAGE TEXT word processing field in the
 HL Monitor Job file.  
VARIABLES: GBL                          TYPE: Input
 VARIABLES DESCRIPTION:   The value of GBL must be a closed global reference to
 the location of the word-processing text to be appended to the RUN DIARY
 field.  

NUMBER: 4228                            IA #: 4228
  FILE NUMBER: 8935.91                  GLOBAL ROOT: XHD(8935.91,
  DATE CREATED: SEP 09, 2003            CUSTODIAL PACKAGE: HEALTHEVET DESKTOP
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DISTRIBUTION OF XHD PARAMETER CATEGORY FILE (#8935.91)
  ID: XHD(8935.91,
 GENERAL DESCRIPTION:   This agreement is provided to the CARE MANAGEMENT
 package version 1.0, to distribute both data and full data dictionary from the
 XHD PARAMETER CATEGORY file (#8935.91).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CARE MANAGEMENT    ISC: Salt Lake City

NUMBER: 4229                            IA #: 4229
  GLOBAL ROOT: DD(                      DATE CREATED: AUG 29, 2003
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA 4229
  ID: DD(
GLOBAL REFERENCE: DD(811.22102,0,IX,AC,811.22102,.01)
 GENERAL DESCRIPTION:   A dangling "IX" node needs to be cleaned up for subfile
 811.22102.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FILEMAN
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: DANGLING IX NODE
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   K ^DD(811.22102,0,"IX","AC",811.22102,.01) 

NUMBER: 4230                            IA #: 4230
  DATE CREATED: MAY 25, 2004            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: MDPS1                        NAME: DBIA4230
  ID: MDPS1
 GENERAL DESCRIPTION:   This DBIA documents the usage of the MDPS1 entry points
 for displaying the Clinical Procedures result reports.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CPA~MDPS1
 COMPONENT DESCRIPTION:   This entry point will display Clinical Procedures
 result report that have the Procedure Summary Code of ABNORMAL.  The result
 consists of the Display Result of the Consult procedure request, if it exists,
 and the TIU document text.  
  
 The following variables are inputs from the local symbol table: 
    DFN   
    GMTS1   
    GMTS2   
    GMTSNDM   
    GMTSNPG   
    GMTSQIT   
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient Internal Entry Number. (Required) 
VARIABLES: GMTS1                        TYPE: Input
 VARIABLES DESCRIPTION:   The ending date in inverse date format
 (9999999-date/time).  (Required) 
VARIABLES: GMTS2                        TYPE: Input
 VARIABLES DESCRIPTION:   The beginning date in inverse date format
 (9999999-date/time).  (Required) 
VARIABLES: GMTSNDM                      TYPE: Input
 VARIABLES DESCRIPTION:   The maximum number of entries to return. (Optional) 
VARIABLES: GMTSNPG                      TYPE: Input
 VARIABLES DESCRIPTION:   The Page Number. (Optional) 
VARIABLES: GMTSQIT                      TYPE: Input
 VARIABLES DESCRIPTION:   Quit indicator. (Optional) 
COMPONENT/ENTRY POINT: CPB~MDPS1
 COMPONENT DESCRIPTION:   This entry point will display a brief summary of the
 Clinical Procedures result Report.  It displays the Consults # (if it exists),
 Procedure Name, Date/Time Performed, and the Procedure Summary Code.  
   
 The following variables are inputs from the local symbol table: 
    DFN   
    GMTS1   
    GMTS2   
    GMTSNDM   
    GMTSNPG   
    GMTSQIT   
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient Internal Entry Number. (Required) 
VARIABLES: GMTS1                        TYPE: Input
 VARIABLES DESCRIPTION:   The ending date in inverse date format
 (9999999-date/time).  (Required) 
VARIABLES: GMTS2                        TYPE: Input
 VARIABLES DESCRIPTION:   The beginning date in inverse date format
 (9999999-date/time).  (Required) 
VARIABLES: GMTSNDM                      TYPE: Input
 VARIABLES DESCRIPTION:   The maximum number of entries to return. (Optional) 
VARIABLES: GMTSNPG                      TYPE: Input
 VARIABLES DESCRIPTION:   The Page Number. (Optional) 
VARIABLES: GMTSQIT                      TYPE: Input
 VARIABLES DESCRIPTION:   Quit indicator. (Optional) 
COMPONENT/ENTRY POINT: CPF~MDPS1
 COMPONENT DESCRIPTION:   This entry point displays the full Clinical
 Procedures result report.  The full report consists of the Display Result of
 the Consult procedure, if it exists, and the TIU document text.  
                                                     
 The following variables are inputs from the local symbol table: 
                                                        
    DFN   
    GMTS1   
    GMTS2   
    GMTSNDM   
    GMTSNPG   
    GMTSQIT   
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient Internal Entry Number. (Required) 
VARIABLES: GMTS1                        TYPE: Input
 VARIABLES DESCRIPTION:   The ending date in inverse date format
 (9999999-date/time).  (Required) 
VARIABLES: GMTS2                        TYPE: Input
 VARIABLES DESCRIPTION:   The beginning date in inverse date format
 (9999999-date/time).  (Required) 
VARIABLES: GMTSNDM                      TYPE: Input
 VARIABLES DESCRIPTION:   The maximum number of entries to return. (Optional) 
VARIABLES: GMTSNPG                      TYPE: Input
 VARIABLES DESCRIPTION:   The Page Number. (Optional) 
VARIABLES: GMTSQIT                      TYPE: Input
 VARIABLES DESCRIPTION:   Quit indicator. (Optional) 
COMPONENT/ENTRY POINT: CPS~MDPS1
 COMPONENT DESCRIPTION:   This entry point displays a one line summary of the 
 Clinical Procedures result report.  The one line summary consists of the
 Consult Number, if it exists, Procedure Name, Date/Time Performed, and the
 Procedure Summary Code.  
              
 The following variables are inputs from the local symbol table:         
               
    DFN   
    GMTS1   
    GMTS2   
    GMTSNDM   
    GMTSNPG   
    GMTSQIT   
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient Internal Entry Number. (Required) 
VARIABLES: GMTS1                        TYPE: Input
 VARIABLES DESCRIPTION:   The ending date in inverse date format
 (9999999-date/time).  (Required) 
VARIABLES: GMTS2                        TYPE: Input
 VARIABLES DESCRIPTION:   The beginning date in inverse date format
 (9999999-date/time).  (Required) 
VARIABLES: GMTSNDM                      TYPE: Input
 VARIABLES DESCRIPTION:   The maximum number of entries to return. (Optional) 
VARIABLES: GMTSNPG                      TYPE: Input
 VARIABLES DESCRIPTION:   The Page Number. (Optional) 
VARIABLES: GMTSQIT                      TYPE: Input
 VARIABLES DESCRIPTION:   Quit indicator. (Optional) 
COMPONENT/ENTRY POINT: EN1~MDPS1(MDGLO,MDDFN,MDSDT,MDEDT,MDMAX,MDPSC,MDALL)
 COMPONENT DESCRIPTION:   This entry point returns a global Array.  
  
 Returns: 
  
 ^TMP("MDHSP",557918815,1) = ECG^1200^EN2^MDPS1^^JUL 
                             24,2002@13:39^NORMAL^^^^^1200^1642 
 ^TMP("MDHSP",557918815,2) = SPIROMETRY, PRE &POST^1047^EN2^MDPS1^^ 
                             JUL 3,2002@13:45^^^^^^1047^1570 
 ^TMP("MDHSP",557918815,3) = ECHO^820^EN2^MDPS1^^MAR 4,2002@12:21^ 
                             ABNORMAL^^^^^820^1399 
  
 Piece 1: Procedure Name Piece 2: study internal entry number (MCARGDA) Piece 3
 & 4: Label and entry point routine Piece 6: Date/Time Performed Piece 7:
 Procedure Summary Code Piece 12: same as piece 2 Piece 13: Consult number 
  
 If MDALL=1, the ^TMP("MDPTXT",$J) global will return the text of the procedure
 reports. The study internal entry number (MCARGDA) will identify the location
 where the text is within the ^TMP("MDPTXT",$J) global.  
                                              
 Global ^TMP("MDPTXT",$J 
         TMP("MDPTXT",$J ^TMP("MDPTXT",557939153,820,"Procedure name",1,0) =
 Current Pat. Status:   Inpatient ^TMP("MDPTXT",557939153,820,"Procedure
 name",2,0) = Ward:                  3AS ^TMP("MDPTXT",557939153,820,"Procedure
 name",3,0) = ^TMP("MDPTXT",557939153,820,"Procedure name",4,0) = Order
 Information ^TMP("MDPTXT",557939153,820,"Procedure name",5,0) = To Service:    
        CARDIOLOGY 
VARIABLES: MDGLO                        TYPE: Both
 VARIABLES DESCRIPTION:   Return Global Array (Required) 
VARIABLES: MDDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN (Internal Entry Number)        (Required) 
VARIABLES: MDSDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Start Date in FM Internal Format (Optional) 
VARIABLES: MDEDT                        TYPE: Input
 VARIABLES DESCRIPTION:   End Date in FM Internal Format (Optional) 
VARIABLES: MDMAX                        TYPE: Input
 VARIABLES DESCRIPTION:   Number of studies to return    (Optional) 
VARIABLES: MDPSC                        TYPE: Input
 VARIABLES DESCRIPTION:   Procedure Summary Code to return.  The four Procedure
 Summary Code are NORMAL, ABNORMAL, BRODERLINE, and INCOMPLETE.  By passing 
 this parameter, the entry point will pass studies with this Procedure Summary
 Code. (Optional) 
VARIABLES: MDALL                        TYPE: Input
 VARIABLES DESCRIPTION:   MDALL is flag.  If MDALL =1, it identifies that all
 text reports with the procedures list should be returned.  
COMPONENT/ENTRY POINT: PR690~MDPS1
 COMPONENT DESCRIPTION:   Prints the free text of the Medicine report.  
  
 The following variables are inputs from the local symbol table: 
    DFN   
    MCARGDA   
    MCPRO   
    ORHFS   
VARIABLES: MCARGDA                      TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the Medicine report
 record.  
VARIABLES: MCPRO                        TYPE: Input
 VARIABLES DESCRIPTION:   The free text of the Medicine procedure name in the
 Procedure/Subspecialty file (#697.2).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
VARIABLES: ORHFS                        TYPE: Input
 VARIABLES DESCRIPTION:   Order Entry Host File.  
COMPONENT/ENTRY POINT: PR702~MDPS1
 COMPONENT DESCRIPTION:   Prints the free text of the Clinical Procedures
 result interpretation.  
  
 The following variables are inputs from the local symbol table: 
    DFN   
    MCARGDA   
    MCPRO   
    ORHFS   
VARIABLES: MCARGDA                      TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the CP Transaction
 record in file (#702).  
VARIABLES: MCPRO                        TYPE: Input
 VARIABLES DESCRIPTION:   The free text of the CP Definition name in file
 (#702.01).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
VARIABLES: ORHFS                        TYPE: Input
 VARIABLES DESCRIPTION:   The Order Entry Host File.  
COMPONENT/ENTRY POINT: CPC~MDPS1
 COMPONENT DESCRIPTION:   This entry point displays the Captioned Clinical
 Procedures result report.  The captioned report displays the Display Result of
 the Consult procedure, if it exists, and the TIU document text.  
                                                     
 The following variables are inputs from the local symbol table: 
                                                          
     DFN   
     GMTS1   
     GMTS2   
     GMTSNDM   
     GMTSNPG   
     GMTSQIT   
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient Internal Entry Number. (Required) 
VARIABLES: GMTS1                        TYPE: Input
 VARIABLES DESCRIPTION:   The ending date in inverse date format
 (9999999-date/time).  (Required) 
VARIABLES: GMTS2                        TYPE: Input
 VARIABLES DESCRIPTION:   The beginning date in inverse date format
 (9999999-date/time).  (Required) 
VARIABLES: GMTSNDM                      TYPE: Input
 VARIABLES DESCRIPTION:   The maximum number of entries to return. (Optional) 
VARIABLES: GMTSNPG                      TYPE: Input
 VARIABLES DESCRIPTION:   The Page Number. (Optional) 
VARIABLES: GMTSQIT                      TYPE: Input
 VARIABLES DESCRIPTION:   Quit indicator. (Optional) 
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR 

NUMBER: 4231                            IA #: 4231
  DATE CREATED: MAY 07, 2004            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMTSUP                       NAME: DBIA4231
  ID: GMTSUP
 GENERAL DESCRIPTION:   This IA is used to document the CKP^GMTSUP entry point
 usage.  
                                                        
 CKP^GMTSUP Checks for the end of page and issues a page break if the number of
 lines printed is equal to or greater than the page length minus the offset
 (IOSL-GMTSLO).                                             
                                                                    
 There are no input parameters, however, this entry point expects to see the
 following pre-existing variables in the environment: 
                                                                     
 IOST       Terminal Type                                                 IOF   
     Form Feed                                                     IOSL      
 Page Length                                                   GMTSLO     Lines
 Off-Set (number of lines before IOSL where you break the 
            page)                                                       GMTSLPG 
   Last Page Indicator Flag (set to 0 except on last page)      GMTSDTM    Date
 and Time (external)                                      GMTSEG(    Segment
 Array                                                GMTSEGN    Segment Number
 - GMTSEG(GMTSEGN)                         GMTSLCMP   Last Component Number     
                              GMTSTITL   Component Title                        
                 GMTSPHDR(   Header Array w/Patient Demographics                
         
                                                              
 Note: The GMTSPHDR can be set by setting DFN and calling DEM^GMTSU.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CKP
VARIABLES: GMTSQIT                      TYPE: Output
 VARIABLES DESCRIPTION:   Not returned explicitly.  Set to 1 if the user
 desired to quit during the prompt.  
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Hines
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: APR 20, 2018

NUMBER: 4232                            IA #: 4232
  DATE CREATED: SEP 22, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUSERP                       NAME: XUSERP
  ID: XUSERP
 GENERAL DESCRIPTION:   When the user file is edited a call should be made to
 CALL^XUSERP(...) so that other applications or system can be updated.  
  STATUS: Active
COMPONENT/ENTRY POINT: CALL(ien,flag)
 COMPONENT DESCRIPTION:   This call is used to queue a task to run one of the
 user update protocols.  
VARIABLES: ien                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number into the New Person
 File.  
VARIABLES: flag                         TYPE: Input
 VARIABLES DESCRIPTION:   flag can have one of three values telling what kind
 of edit was done to the New Person File.  1=Add/Create New Entry,  call the XU
 USER ADD protocol from file 19.  2=Update Existing Entry, call the XU USER
 CHANGE protocol from file 19.  3=Terminate, call the XU USER TERMINATE
 protocol from file 19.  

NUMBER: 4233                            IA #: 4233
  DATE CREATED: SEP 02, 2003
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: CSLARACS
  NAME: COST CENTER QUERY               ID: CSLARACS
 GENERAL DESCRIPTION:   Allow user to query CoreFLS for cost centers matching
 an input pattern.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: COST CENTER
COMPONENT/ENTRY POINT: CCQ
VARIABLES: CSLY                         TYPE: Output
SUBSCRIBING PACKAGE: FEE BASIS

NUMBER: 4234                            IA #: 4234
  DATE CREATED: SEP 02, 2003
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: CSLARACS
  NAME: FIELD ACTIVITY QUERY            ID: CSLARACS
 GENERAL DESCRIPTION:   allow users to query CoreFLS for field Activity values
 from the Accounting Code String (ACS) based on input key.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FIELD ACTIVITY
KEYWORDS: ACS
COMPONENT/ENTRY POINT: FAQ
VARIABLES: CSLY                         TYPE: Output
SUBSCRIBING PACKAGE: FEE BASIS

NUMBER: 4235                            IA #: 4235
  DATE CREATED: SEP 04, 2003
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: CSLARSV
  NAME: Controlled subscription from AR to CSL via CSLARSV routine
  ID: CSLARSV
 GENERAL DESCRIPTION:   CoreFLS will replace three VistA applications - IFCAP,
 AEMS/MERS, and FMS which is the central accounting software used in the VA.
 Hence, VistA applications, which used to communicate with these applications,
 will now communicate with the COTS applications in CoreFLS. To be able to
 provide real-time integration between CoreFLS and VistA, HL7 messaging
 protocol was selected. This integration agreement will address the CSL
 interface application linking the VistA AR system with the Oracle based
 CoreFLS financial system.  
  STATUS: Active
KEYWORDS: CSLAR
KEYWORDS: CSL AR
COMPONENT/ENTRY POINT: DRV
 COMPONENT DESCRIPTION:   Invoked by AR monthly processing routine to create
 HL7 message with multiple line data. If the total record number is more than
 100, CSL will create multiple HL7 messages that each contains a maximum of 100
 records. These HL7 messages will be sent to CoreFLS by VistA HL7 package.
 Since the monthly process are background jobs, no application acknowledgement 
 will be returned to AR.  
  
 The data from AR will be passed in global ^XTMP(RTN) where RTN is the routine
 name which invoked routine CSLARSV. The layout of global ^XTMP(RTN) is
 categorized by different events: 
  
 211 (CR Detail to Storage)    215 (WR Detail to Storage) 
                               220 (SV Detail to Storage) 
 ------------------------------------------------------------
 Piece  Description                  Description            
 ------------------------------------------------------------
   1    215 Deposit Number          CoreFLS Fund 
   2    CoreFLS Fund                RSC Fund 
   3    RSC Fund                    Station Number 
   4    Station Number              Accounting Period Date 
   5    Receipt Number              Transaction Date 
   6    Accounting period Date      215 Deposit Number 
   7    Transaction Date            Amount 
   8    Accomplished Date           Federal Trading Partner 
   9    Date Bill Created           DUNS# 
  10    Last Edit Date              Date Bill Created 
  11    Amount                      Last Edit Date 
  12    Bill Number                 Bill Number 
  13    Bill Category               AR Unique Identifier 
  14    Federal Trading Partner     JE Header 
  15    DUNS#                       Bill Category 
  16    AR Unique Identifier 
  17    JE Header 
VARIABLES: RTN                          TYPE: Input
 VARIABLES DESCRIPTION:   First subscript of ^XTMP (input data) 
VARIABLES: CSLEVI                       TYPE: Input
 VARIABLES DESCRIPTION:   AR event number.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULT = 1, HL7 message successfully generated.  
 RESULT = 0^error message, HL7 message generation failed.  
COMPONENT/ENTRY POINT: ACK
 COMPONENT DESCRIPTION:   Reserved for future use.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany
 SUBSCRIBING DETAILS:   AR will invoke CSLARSV to generate HL7 messages to pass
 multiple records to CoreFLS 

NUMBER: 4236                            IA #: 4236
  DATE CREATED: SEP 04, 2003
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: CSLARDR
  NAME: Controlled subscription from AR to CSL via CSLARDR routine
  ID: CSLARDR
 GENERAL DESCRIPTION:   CoreFLS will replace three VistA applications - IFCAP,
 AEMS/MERS, and FMS which is the central accounting software used in the VA.
 Hence, VistA applications, which used to communicate with these applications,
 will now communicate with the COTS applications in CoreFLS. To be able to
 provide real-time integration between CoreFLS and VistA, HL7 messaging
 protocol was selected. This integration agreement will address the CSL
 interface application linking the VistA AR system with the Oracle based
 CoreFLS financial system.  
  STATUS: Active
KEYWORDS: CSLAR
KEYWORDS: CSL AR
COMPONENT/ENTRY POINT: DRV
 COMPONENT DESCRIPTION:   Invoked by AR routine to create HL7 message
 containing single line data. The HL7 message will be send to CoreFLS by VistA
 HL7 package. CoreFLS will return the pre-validation status in the application
 acknowledgement 
VARIABLES: TMP                          TYPE: Input
 VARIABLES DESCRIPTION:   Data from AR that need converted to HL7 format and
 sent to CoreFLS. The layout by event number: 
  
 213 (Bill Document to GL)        217 (Overpayment to GL) 216 (WR on Demand)    
           222 (End of Year Process)        226 (BD without SSN) 
 ------------------------------------------------------------
 Piece  Description                  Description            
 ------------------------------------------------------------
   1    CoreFLS Fund                CoreFLS Fund 
   2    RSC Fund                    RSC Fund 
   3    Station Number              Station Number 
   4    Transaction Code            Transaction Code 
   5    Transaction Type            Transaction Type 
   6    Bill Number                 Debtor's Last Name 
   7    Initial Bill Date           Debtor's SSN 
   8    Last Edit Date              Address 1 
   9    Accounting Period Date      Address 2 
  10    Transaction Date            City 
  11    Federal Trading Partner     State 
  12    DUNS Number                 Zip 
  13    Principal Amount            Accounting Period Date 
  14    Interest Amount             Invoice Received Date 
  15    Admin. & Penalty            Invoice Number 
  16    Court/Marshall Fee          Invoice Line Number 
  17    Increase/Decrease Indicator Principal Amount 
  18    Bill Category               User's SSN 
  19    User's SSN                  Debtor's First Name 
  20                                Debtor's Middle Name 
  21                                Debtor's Initial 
  
   
 212 (SV Monthly to GL) 214 (WR Monthly to GL) 219 (Bad Debt Estimate) 224
 (Unbilled Accruals) 
 -----------------------------
 Piece  Description          
 -----------------------------
   1    CoreFLS Fund          
   2    RSC Fund              
   3    Station Number        
   4    Transaction Code     
   5    Transaction Type     
   6    Principal Amount 
   7    Accounting Period Date 
   8    Transaction Date 
   9    SV/WR/215 Number 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN is an AR unique identifier that will be passed to
 CoreFLS and returned later with application acknowledgement to identify the
 record being processed by CoreFLS.  
VARIABLES: EVC                          TYPE: Input
 VARIABLES DESCRIPTION:   EVC is the event number which will be passed to
 CoreFLS.  
COMPONENT/ENTRY POINT: ACK
 COMPONENT DESCRIPTION:   Invoked by VistA HL7 package to process application 
 acknowledgement returned by CoreFLS. The acknowledgement message will be
 passed to AR by calling routine GETACK^PRCAFLS3(RCN,ACKCODE,.CSLB) Where RCN:
 Receipt number 
   ACKCODE: Acknowledgement code 
      CSLB: Acknowledgement message array 
            Each line in the array contains 
               Error Code ^ Error Description ^ IEN (file 347.6) 
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Albany
 SUBSCRIBING DETAILS:   AR will invoke CSLARDR to generate HL7 messages to pass
 single line data to CoreFLS 

NUMBER: 4237                            IA #: 4237
  DATE CREATED: SEP 22, 2003
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSSRXACT                     NAME: DBIA4237
  ID: PSSRXACT
 GENERAL DESCRIPTION:   This supported reference is available to allow users to
 pass in a patient's internal file number (dfn) in the form of a function call
 to indicate if that patient has at least one active prescription.  
  
 S X=$$EN^PSSRXACT(DFN).  1 is returned if the patient has at least one active
 Rx, else 0 (zero) is returned indicating no active prescriptions.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Required patient's dfn.  

NUMBER: 4238                            IA #: 4238
  DATE CREATED: SEP 16, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFHLMFE
  NAME: DBIA4238-A                      ORIGINAL NUMBER: 4238
  ID: VAFHLMFE
 GENERAL DESCRIPTION:   Integrated Billing calls the HL7 function
 $$MFE^VAFHLMFE when constructing the HL7 messages that are passed on through
 Vitria for insurance confirmation.  
  STATUS: Active
KEYWORDS: IIV
KEYWORDS: HL7
KEYWORDS: INTEGRATED BILLING
COMPONENT/ENTRY POINT: $$MFE(EVENT,MFN,EDT,CODE)
 COMPONENT DESCRIPTION:   Given the record-level event code, MFN contorl ID, 
 Effective Date/Time and primary key value, generate an MFE segment or return
 an error message if a required parameter has not been passed.  
VARIABLES: EVENT                        TYPE: Input
 VARIABLES DESCRIPTION:   Record-level event code.  If none is supplied, a
 default of MAD (always add record to master file) is employed.  
VARIABLES: MFN                          TYPE: Input
 VARIABLES DESCRIPTION:   MFN contorl ID.  If none is supplied, a default of
 NULL is employed.  
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Effective Date/Time.  If none is supplied, a default
 of the current date and time is employed (FileMan format is expected) 
VARIABLES: FUNCTION RETURNS             TYPE: Output
 VARIABLES DESCRIPTION:   MFE segment string sub-delimited by HLFS, otherwise
 "-1^"_ERROR MESSAGE 
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4239                            IA #: 4239
  DATE CREATED: SEP 16, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFHLMFI
  NAME: DBIA4238-B                      ORIGINAL NUMBER: 4238
  ID: VAFHLMFI
 GENERAL DESCRIPTION:   Integrated Billing calls the HL7 function
 $$MFI^VAFHLMFI when constructing the HL7 messages that are passed on through
 Vitria for insurance confirmation.  
  STATUS: Active
KEYWORDS: IIV
KEYWORDS: HL7
KEYWORDS: INTEGRATED BILLING
COMPONENT/ENTRY POINT: $$MFI(ID,APP,EVENT,ENDT,EFFDT,RESP)
 COMPONENT DESCRIPTION:   Given the Master File Identifier, file-level event
 code, entered date/time, effective date/time and response-level code, generate
 an MFI segment or return an error message if a required parameter has not been
 passed.  
VARIABLES: ID                           TYPE: Input
 VARIABLES DESCRIPTION:   Master File Identifier.  This is a required field. 
 If it is not supplied an error is returned.  
VARIABLES: APP                          TYPE: Input
 VARIABLES DESCRIPTION:   Master File Application Identifier.  This is a
 required field.  If it is not supplied, an error is returned.  
VARIABLES: EVENT                        TYPE: Input
 VARIABLES DESCRIPTION:   File-level event code.  If none is supplied, a
 default of REP (replace the current version of this master file with the
 version contained in this message) is employed.  
VARIABLES: ENDT                         TYPE: Input
 VARIABLES DESCRIPTION:   Entered date/time.  If none is supplied, a default of
 the current date/time is employed (FileMan format is expected).  
VARIABLES: EFFDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Effective date/time.  If none is supplied, a default
 of the current date/time is employed (FileMan format expected).  
VARIABLES: RESP                         TYPE: Input
 VARIABLES DESCRIPTION:   Response level code.  If none is supplied, a default
 of NE (Never, no application level response needed) is employed.  
VARIABLES: FUNCTION RETURNS             TYPE: Output
 VARIABLES DESCRIPTION:   Function returns:  MFI segment string sub-delimited
 by HLFS, otherwise "-1^"_error message 
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4240                            IA #: 4240
  FILE NUMBER: 9000010                  GLOBAL ROOT: AUPNVSIT(
  DATE CREATED: SEP 16, 2003
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4240
  ID: AUPNVSIT(
GLOBAL REFERENCE: (9000010,.01)
FIELD NUMBER: .01                       FIELD NAME: VISIT ADMIT/DATE&TIME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The "B" cross-reference is used to loop through visits
 within a date range.  Usage by IBCNEDE3 and IBCNEDE4 are shown below: 
            From:  IBCNEDE3 
                   S AUPNDT=$O(^AUPNVSIT("B",IBD) 
                   and 
                   S IEN=$O(^AUPNVSIT("B",IBD,IEN)) 
  
            From:  IBCNEDE4 
                   S AUPNDT=$O(^AUPNVSIT("B",IBD) 
                   and 
                   S IEN=$O(^AUPNVSIT("B",IBD,IEN)) 
GLOBAL REFERENCE: 9000010,.05
FIELD NUMBER: .05                       FIELD NAME: PATIENT NAME
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The "AA" cross-reference is used to loop through visits
 for a particular patient DFN.  Usage by IBCNEDE3 and IBCNEDE4 are shown below: 
            From:  IBCNEDE3 
                   S IBD=$O(^AUPNVSIT("AA",DFN,IBD) 
  
            From:  IBCNEDE4 
                   S IBD=$O(^AUPNVSIT("AA",DFN,IBD) 
 GLOBAL DESCRIPTION:   The value for PATIENT NAME (DFN, pointer to the PATIENT
 FILE) is then read from the file as follows: 
             From:  IBCNEDE3 
                    S DFN=$P($G(^AUPNVSIT(IEN,0)),U,5) 
                    
             From:  IBCNEDE4 
                    S DFN=$P($G(^AUPNVSIT(IEN,0)),U,5) 
GLOBAL REFERENCE: 9000010,.01
FIELD NUMBER: 1                         FIELD NAME: VISIT ADMIT/DATE&TIME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The "B" cross-reference is used to loop through visits
 within a date range.  
         Usage by IBCNEDE3 and IBCNEDE4 are shown below: 
            From:  IBCNEDE3 
                   S AUPNDT=$O(^AUPNVSIT("B",IBD) 
                   and 
                   S IEN=$O(^AUPNVSIT("B",IBD,IEN)) 
  
            From:  IBCNEDE4 
                   S AUPNDT=$O(^AUPNVSIT("B",IBD) 
                   and 
                   S IEN=$O(^AUPNVSIT("B",IBD,IEN)) 
 GENERAL DESCRIPTION:   The IIV (Insurance Identification and Verification)
 enhancement patch IB*2.0*184, performs a direct file reference to the "B" and
 "AA" cross- references as it loops through visit records as part of the IIV
 data extracts.  This applies only to extract #3 (Past encounters, non-verified
 ins.) and #4 (Past encounters, No Insurance).  These           extracts reside
 in routines IBCNEDE3 and IBCNEDE4 respectively.  
  
 In addition, the extract routines also performs a direct global read of      
 the "0" node ^AUPNVSIT(IEN,0) to retrieve the patient's DFN (5th piece)     
 value from the visits as they are looped-through.  
  STATUS: Active
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4241                            IA #: 4241
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870,
  DATE CREATED: AUG 18, 2004            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4241
  ID: HLCS(870,
GLOBAL REFERENCE: HLCS(870,
FIELD NUMBER: .01                       FIELD NAME: NODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 400.01                    FIELD NAME: TCP/IP ADDRESS
  LOCATION: 400;1                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 400.02                    FIELD NAME: TCP/IP PORT
  LOCATION: 400;2                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 400.06                    FIELD NAME: STARTUP NODE
  LOCATION: 400;6                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DOMAIN
  LOCATION: 0;7                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: "B" X-REF                 ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
   The BPS 1.0 Master Build, performs Fileman references and modifications to
 the HL7 LOGICAL LINK File (#870) to retrieve and/or modify the IP address,
 port number, Domain and startup node information for the logical links that
 are installed by the BPS software. This information is needed when installing
 the above patch and subsequently when the BPS applications validate the status
 of the links.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BPS
KEYWORDS: ECME
KEYWORDS: HIPAA
KEYWORDS: NCPDP
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   ADDED 6/2/2010 

NUMBER: 4242                            IA #: 4242
  FILE NUMBER: 43                       GLOBAL ROOT: DG(43
  DATE CREATED: SEP 16, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4242
  ID: DG(43
GLOBAL REFERENCE: 43.04,.01
FIELD NUMBER: 1                         FIELD NAME: CLINIC EXCLUSION
  LOCATION: .04,1                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This cross-reference is used to check whether a
 particular clinic should be excluded from the data extracts: 
         
         Usage by IBCNEDE2 
            From:  IBCNEDE2 
                   I $D(^DG(43,1,"DGPREC","B",CLNC)) S OK=0 
                   (if this clinic is found in the exclusion list, then set 
                   a flag to exclude) 
GLOBAL REFERENCE: 43.08,.01
FIELD NUMBER: 1                         FIELD NAME: ELIGIBILITY EXCLUSION
  LOCATION: .08,.01                     ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This cross-reference is used to check whether a
 particular eligibility should be excluded from the data extracts: 
         
         Usage by IBCNEDE2 
            From:  IBCNEDE2 
                   I $D(^DG(43,1,"DGPREE","B",ELG)) S OK=0 
                   (if ELG is found in the exclusion list, then set a flag 
                   to exclude) 
 GENERAL DESCRIPTION:   The IIV (Insurance Identification and Verification)
 enhancement patch IB*2.0*184, performs a direct file references to the CLINIC
 EXCLUSION (43.04,.01) cross-reference, ^DG(43,DA(1),"DGPREC","B",CLNC) and
 also       the ELIGIBILITY EXCLUSION (43.08,.01)cross-reference, ^DG(43,DA(1), 
        "DGPREE","B",ELG) of the MAS PARAMETERS File (#43).  These references   
    are made as part of the future appointment data extract (#2 - in routine   
 IBCNEDE2),to determine whether or not future visits should be excluded      
 from the IIV extract.  
  STATUS: Active
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4243                            IA #: 4243
  FILE NUMBER: 408.13                   GLOBAL ROOT: DGPR(408.13
  DATE CREATED: SEP 16, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4243
  ID: DGPR(408.13
GLOBAL REFERENCE: DGPR(408.13,DO,0)
FIELD NUMBER: 2                         FIELD NAME: SEX
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   DIRECT GLOBAL READ This set of codes field identifies the
 relative's sex.  
FIELD NUMBER: 3                         FIELD NAME: DATE OF BIRTH
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   DIRECT GLOBAL READ This date field identifies the
 relative's date of birth.  
FIELD NUMBER: 4                         FIELD NAME: PATIENT
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   DIRECT GLOBAL READ This pointer is used to retrieve
 demographic information directly from the PATIENT file when the relative was
 at some time a patient.  
FIELD NUMBER: 9                         FIELD NAME: SOCIAL SECURITY NUMBER
  LOCATION: 0;9                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   DIRECT GLOBAL READ This is the dependent's social
 security number.  
 GENERAL DESCRIPTION:   The IIV (Insurance Identification and Verification)
 enhancement patch IB*2.0*184, performs a direct file reference to the PATIENT
 RELATION file (#408.12).  It is used to determine if the insured is the
 veteran, the spouse, or another relationship.  If it is the veteran or the
 spouse the demographic information is pulled directly from the PATIENT file
 (#2).  If the relationship is 'other', the associated entry in the insured
 INCOME PERSON file (#408.13) is examined.  If the PATIENT field (#365.13, .04)
 in the INCOME PERSON file is populated, the demographic information is pulled 
 from that relative's record in the PATIENT file.  Otherwise, the demographic
 information is directly retrieved from the INCOME PERSON file.  This call is
 used in the routine IBCNEHLQ.  
  STATUS: Active
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4244                            IA #: 4244
  FILE NUMBER: 408.12                   GLOBAL ROOT: DGPR(408.12
  DATE CREATED: SEP 16, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4244
  ID: DGPR(408.12
GLOBAL REFERENCE: DGPR(408.12,D0,0)
FIELD NUMBER: 2                         FIELD NAME: RELATIONSHIP
  LOCATION: 0;23                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Direct Global Read This pointer is needed to identify if
 the demographic information may be found in the PATIENT file (veteran or
 spouse) or if the INCOME PERSON file should be examined.  
FIELD NUMBER: 3                         FIELD NAME: PERSON
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Direct Global Read This variable pointer identifies the
 relative by referencing the specific entry in the PATIENT or the INCOME PERSON
 file.  THis is used for retrieving insurance demographics.  
GLOBAL REFERENCE: DGPR(408.12,'B',
 GLOBAL DESCRIPTION:   The "B" cross-reference is used to find all the
 relations to the patient in order that insurance demographics (Date of Birth,
 Sex and Social Security Number) may be retrieved when querying insurance
 information.  
 GENERAL DESCRIPTION:   The IIV (Insurance Identification and Verification)
 enhancement patch IB*2.0*184, performs a direct file reference to the PATIENT
 RELATION file (#408.12).  It is used to determine if the insured is the
 veteran, the spouse, or another relationship.  If it is the veteran or the
 spouse the demographic information is pulled directly from the PATIENT file
 (#2).  If the relationship is 'other', the associated entry in the insured
 INCOME PERSON file (#408.13) is examined.  If the PATIENT field (#365.13, .04)
 in the INCOME PERSON file is populated, the demographic information is pulled 
 from that relative's record in the PATIENT file.  Otherwise, the demographic
 information is directly retrieved from the INCOME PERSON file.  This call is
 used in the routine IBCNEHLQ.  
  STATUS: Active
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4245                            IA #: 4245
  DATE CREATED: NOV 06, 2003            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: LRPXAPI                      NAME: DBIA4245
  ID: LRPXAPI
 GENERAL DESCRIPTION:   APIs for retrieving Lab data.  
  
 Arguments enclosed with brackets are optional. Arguments without brackets are
 required. Arguments preceded by a period should be called by reference. 
  
  STATUS: Active
COMPONENT/ENTRY POINT: TESTS(.i,d,[t],[m],[.n],[c],[d1],[d2])
 COMPONENT DESCRIPTION:   
  
 Returns lab items on a patient. In the case of Chemistry this would be the
 tests, with Micro or AP it could be various items. Obtains only the tests a
 patient has results for; therefore, useful to screen for only those tests on 
 selection. Results are not returned, just the tests (items).  
  
 arguments 
  
  .i    local array of items returned(ien)=ien^name 
        or 
        NMSP: namespace string 
        ^TMP(NMSP,$J,ien)=ien^name 
        where ien is pointer value in file 60 or for 
        Micro and AP data will be (item)=item^item name 
  d     DFN 
  [t]   type of data [C M A] chem, micro, or AP 
        default: C 
  [m]   max number of tests returned per call 
        default: 100 
  [.n]  next: returns 0 unless more tests available 
  [c]   condition expression: use V, F, and S as variables 
        for value, flag and specimen 
  [d1]  first date of date range 
        default: any time in the future (no limits) 
  [d2]  second date of date range 
        default: any time in the past (no limits) 
  
 examples 
  
 Return tests on patient.  
  D TESTS^LRPXAPI(.TESTS,DFN) 
  returns: 
  TESTS(173)=173^CREATININE 
  TESTS(174)=174^UREA NITROGEN 
  TESTS(175)=175^GLUCOSE 
  
 Micro items collected during May 2002.  
  D TESTS^LRPXAPI(.TESTS,DFN,"M",,,30020501,30020530) 
  
 All tests having abnormal results and storing them into 
  a TMP global to avoid allocation errors.  
  F  D  Q:'MORE 
  . D TESTS^LRPXAPI(.ITEMS,DFN,"C",100,.MORE,"F]""""",FROM,TO) 
  . M ^TMP("LRPXAPP",$J)=ITEMS 
  
COMPONENT/ENTRY POINT: RESULTS(.v,d,[i],[m],[.n],[c],[d1],[d2])
 COMPONENT DESCRIPTION:   
  
 Returns lab results on a patient for either Chem, Micro, or AP. The results
 may be for an item, a type, or partial type.  Useful for obtaining all lab
 results, results for a test, all results for a date range, or the last
 results.  
  
 arguments 
  
  .v    local array of test values returned(lridt_" "_test) 
        =date^test^comment^data 
        or 
        NMSP: namespace string^TMP(NMSP,$J,lridt_" "_test) 
        =date^test^comment^data 
        where date is collection date, test is pointer value in 
        file 60, comment is 1 if it exists   else 0, data is 
        result node (value^flag^...etc...) Micro and AP data 
        return (-date_" "_item)=date^item^node^data 
  d     DFN 
  [i]   item or type [C M A] Chem, Micro, or AP 
        may also be an item or item or type [C M A] 
        may also be an item or partial type ("M;S;360", 
        "A;M;142", "M;A;", "A;D;") 
        default: C 
  [m]   max number of collection times results returned per call 
        default: 10 
  [.n]  next: returns 0 unless more results available 
  [c]   condition expression: use V, F, and S as variables for 
        value, flag and specimen; MUMPS operators are used 
  [d1]  first date of date range 
        default: any time in the future (no limits) 
  [d2]  second date of date range 
        default: any time in the past (no limits) 
  
 examples 
  
 Get results for last 10 collections of Chem tests and store in ^TMP("ZZ",$J. 
  D RESULTS^LRPXAPI("ZZ",DFN) 
  
 Return last lab results on patient. This example returns three test results
 from the last collection time. 
  D RESULTS^LRPXAPI(.ZZZ,DFN,"C",1) returns: 
  ZZZ("7019484.887 173")=2980514.113^173^0^23^H^!^5^72!.9! 
  ZZZ("7019484.887 174")=2980514.113^174^0^14^^!^5^72!11!24 
  ZZZ("7019484.887 176")=2980514.113^176^0^23^L*^!^5^72!135 
  
 This example would return all critical results on a patient 
  (assuming there are no more than 100 results available).  
  D RESULTS^LRPXAPI(.EX,17,"C",,"F[""*""") returns: 
  EX("7019484.887 1160")=2980514.113^1160^0^4^L*^!^5^72!   
  EX("7019484.887 176")=2980514.113^176^0^23^L*^!^5^72!135! 
  
COMPONENT/ENTRY POINT: PATIENTS(.p,[i],[s],[m],[.n],[c],[d1],[d2])
 COMPONENT DESCRIPTION:   
  
 Returns all patients for a specific test. Useful for finding patients to
 study.  
  
 arguments 
  
  .p    local array of patients returned(dfn)=dfn^name 
        or 
        NMSP: namespace string ^TMP(NMSP,$J,dfn)=dfn^name 
        where name is the patient's name 
  [i]   item 
        for Chemistry: test   pointer to file 60 
        for Micro and AP data - semicolon delimited string 
        item is optional, a condition can also be used 
        for identifying patients 
        a type or partial type can be used type 
        ("M", "A;M;", "M;A;", "A;D;") 
        if not item or condition, all patients are returned 
  [s]   source used as a subset of patients 
        an array or global array reference with DFNs in the 
        first subscript 
        default is all patients with lab data 
  [m]   max number of patients returned per call 
        default: 100 
  [.n]  next: returns 0 unless more patients available 
  [c]   condition expression: use V, F, and S as variables for 
        value, flag and specimen; MUMPS operators are used 
  [d1]  first date of date range 
        default: any time in the future (no limits) 
  [d2]  second date of date range 
        default: any time in the past (no limits) 
  
 examples 
  
 Return all patients (maximum of 100) who've had a glucose over 500.  
  D PATIENTS^LRPXAPI(.PATS,175,,,,"V>500") 
  
 Return all patients (maximum of 100) who've had a glucose in May 2002.  
  D PATIENTS^LRPXAPI(.PATS,175,,,,30020501,30020530) 
  
 Get all patients with autopsy results in May 2003 
  and store in ^TMP("ZZ",$J (maximum of 1000).  
  D PATIENTS^LRPXAPI("ZZ","A",,1000,,"C=""A""",3030501,3030601) 
  
 Find all patients with AP results where disease was CANDIDIASIS.  
  D PATIENTS^LRPXAPI(.ZZ,"A;D;280") returns 
  ZZ(1086)=1086^TLNAXU,IXNJH U ZZ(8210)=8210^RDJELITXY,HIZRYI 
  ZZ(8397)=8397^OYHDA,UXKHUS C 
  
 Find all patients with AP results where disease was CANDIDIASIS.  
  Use those patients as the source for another query for patients with 
  Micro results where organism was CANDIDA ALBICANS.  
  D PATIENTS^LRPXAPI(.PTS,"A;D;280") 
  D PATIENTS^LRPXAPI(.XX,"M;O;5","PTS") returns: 
  XX(8210)=8210^RDJELUITXY,HIZRYI F 
  XX(8397)=8397^OYHDA,UXKHUS C 
  
 Find a patient with Micro results from blood where organism 
  was CANDIDA ALBICANS and was sensitive to NITROFURANTOIN.  
  D PATIENTS^LRPXAPI(.ABC,"M;O;2",,1,,"S=70|A=20|I[""S""") returns 
  ABC(8999)=8999^CLUULYML,ZLUT F 
  
COMPONENT/ENTRY POINT: DATES(.dt,d,[t],[m],[.n],[d1],[d2])
 COMPONENT DESCRIPTION:   
  
 Returns all instances of patient data. This may be for Chemistry, Micro, or AP
 data. Useful for finding time occurrences when lab specimens were collected.  
  
 arguments 
  
  .dt   local array of date/times: (-date)=date 
        or 
        NMSP: namespace string ^TMP(NMSP,$J,-date)=date 
        collated by most recent 
  d     DFN 
  [t]   type of data [C M A] Chem, Micro, or AP 
        default: C 
  [m]   max number of collection times returned per call 
        default: 100 
  [.n]  next: returns 0 unless more collection times available 
  [d1]  first date of date range 
        default: any time in the future (no limits) 
  [d2]  second date of date range 
        default: any time in the past (no limits) 
  
 examples 
  
 Return all Chem collection date/times (maximum of 100).  
  D DATES^LRPXAPI(.OCC,DFN) 
  
 The following code gets all Micro occurrences, storing them 
  into a TMP global. A namespaced label is used (example 
  "ZZMICRO") and returned as ^TMP(namespace,$J,date)=date.  
  D DATES^LRPXAPI("ZZMICRO",DFN,"M") returns: 
  ^TMP("ZZMICRO",549459892,-3020811.105354) = 3020811.105354 
  ^TMP("ZZMICRO",549459892,-3020811.105353) = 3020811.105353 
  ^TMP("ZZMICRO",549459892,-3020811.093703) = 3020811.093703 
  
COMPONENT/ENTRY POINT: VALUE(.r,d,cdt,t,[c],[.e])
 COMPONENT DESCRIPTION:   
  
 Obtains the result node of a test value. For "CH" results only. This is useful
 when getting a result without knowing Lab's variables for retrieval. LRDFN,
 LRIDT, LRDN are not needed. DFN, collection date/time and test number are
 used. A condition may also be used to only return the value if the condition
 is met. If no valid value exists, the result node is returned as "" and error
 is 1, else 0.  
  
 arguments 
  
  .r    result node 
  d     DFN 
  cdt   collection date/time 
  t     test (file 60) 
  [c]   condition 
  [.e]  error (1 or 0) 
  
 example 
  
 Get the value of a lab test.  
  D VALUE^LRPXAPI(.RESULT,DFN,COL,TEST) 
  returns the entire result node 
  
 Examples showing a patient's result for creatinine   sometimes with
 conditions.  
  D VALUE^LRPXAPI(.RESULT,6,3020319.06,173) 
  returns RESULT as: 
  2.1^H^81136.0000!82565.0000!2160!3110!1^4838^72!0.7!1.5!!!!MG 
  /DL!2!50^^^^605 
  
  D VALUE^LRPXAPI(.RESULT,6,3020319.06,173,"F[""H""|S=71",.ERR) 
  returns: RESULT="" and ERR=1 
  
COMPONENT/ENTRY POINT: LRVALUE(.r,l,i,d,[c],[.e])
 COMPONENT DESCRIPTION:   
  
 Obtains the result node of a test value. For "CH" results only. LRDFN, LRIDT,
 LRDN are needed. A condition may also be used to only return the value if the
 condition is met. If no valid value exists, the result node is returned as ""
 and error is 1, else 0.  
  
 arguments 
  
  .r    result node 
  l     LRDFN 
  i     LRIDT 
  d     LRDN 
  [c]   condition 
  [.e]  error 
  
 example 
  
 Get the value of a lab test.  
  D LRVALUE^LRPXAPI(.RESULT,LRDFN,LRIDT,LRDN) returns the entire result node 
  
  D LRVALUE^LRPXAPI(.RESULT,41,6979171.877447,826) returns RESULT as: 
  10^H^89081.0000!86678.0000!8129!8691^766^70!.9!2.9!!^^^^605 
  
COMPONENT/ENTRY POINT: LRPXRM(.r,n,[i],[t])
 COMPONENT DESCRIPTION:   
  
 Obtains the result node of a test value. If no valid value exists, "" is
 returned.  
  
 arguments 
  
  .r   result node 
  n    data node in PXRMINDX index 
       examples: 
       lrdfn;CH;lridt;lrdn, 
       lrdfn;MI;lridt;3;org;0 
  [i]  item 
       default: if i is not defined, n is assumed to be a "CH" 
       node (lrdfn;CH;lridt;lrdn), 
       else .r will be returned as "" 
  [t] type of data returned where letters can include 
      V value 
      S specimen 
      C comments 
      default: "VS" 
  
 examples 
  
 Get the value of a lab test value from a data reference.  
  S DATAREF=$O(^PXRMINDX(63,"IP",TEST,DFN,COLTIME,"") 
  D LRPXRM^LRPXAPI(.RESULT,DATAREF,TEST) 
  S VALUE=$P(RESULT,U) 
  
 Examples using data node values.  
  D LRPXRM^LRPXAPI(.RESULT,"7578;CH;7089488.8858;384",,"V") returns: 
  1^WBC^9.8 
  
  
  D LRPXRM^LRPXAPI(.RESULT,"96273;CH;6979288.926197;7",,"VSC") returns 
  RESULT=178^CHLORIDE^103^^81853.0000!82435.0000! 
  RESULT("COMMENTS")=0 
  RESULT("SPECIMEN")=72^SERUM 
  
  D LRPXRM^LRPXAPI(.RESULT,"52;SP;7049373;2;1;1;2;0","A;D;266") returns: 
  266^VIRAL HEPATITIS^266 
  
  D LRPXRM^LRPXAPI(.ZZ,"6;MI;7018878.8848;3;6;2.0016","M;A;1") returns: 
  1^AMIKACN^<=2^S^ 
  
COMPONENT/ENTRY POINT: SPEC(.r,d,cdt,[s],[.e])
 COMPONENT DESCRIPTION:   
  
 Obtains the specimen and collection information. For "CH" results only. The
 STYPE parameter may be S for the specimen node, C for comments, V for all
 LRDNs, and A for S, C, and V. If no valid specimen data exists, results is
 returned undefined and error is 1 (otherwise 0).  
  
 arguments 
  
  .r    array of results, example: 
        RESULTS("C",#)=comments 
        RESULTS("S")=specimen node 
        RESULTS("V",#)=LRDN 
  d     DFN 
  cdt   collection date/time 
  [s]   STYPE (S: spec node, C: comment, V: test values, A: all) 
        default is A 
  [.e]  error (1 or 0) 
  
 example 
  
 Get values for a lab collection.  
  D SPEC^LRPXAPI(.RESULTS,DFN,COLTIME,"A") 
  returns the comments, specimen and test information.  
  
 Examples on the same sample.  
  D SPEC^LRPXAPI(.XX,6544,2900820.2245) 
  returns: 
  XX("C",1)=Hemoglobin, Methemoglobin  10.7,1.1  
  XX("C",2)=Spontaneous  
  XX("C",3)=Arterial (AR)  
  XX("S")=2900820.2245^^2900820.2253^2382^8728^BG 0820 40^^^ 
  XX("V",1)=444^21%^ 
  XX("V",2)=446^93.6^ 
  XX("V",3)=447^2.2^ 
  XX("V",4)=449^14.0^L 
  XX("V",5)=451^31.7^L 
  XX("V",6)=452^72.2^ 
  XX("V",7)=454^23.7^ 
  XX("V",8)=457^7.482^H 
  
  D SPEC^LRPXAPI(.XX,6544,2900820.2245,"C") 
  returns: 
  XX("C",1)=Hemoglobin, Methemoglobin  10.7,1.1  
  XX("C",2)=Spontaneous 
  XX("C",3)=Arterial (AR) 
  
  D SPEC^LRPXAPI(.XX,6544,2900820.2245,"S") 
  returns: 
  XX("S")=2900820.2245^^2900820.2253^2382^8728^BG 0820 40^^^ 
  
  D SPEC^LRPXAPI(.XX,6544,2900820.2245,"V") 
  returns: 
  XX("V",1)=444^21%^ 
  XX("V",2)=446^93.6^ 
  XX("V",3)=447^2.2^ 
  XX("V",4)=449^14.0^L 
  XX("V",5)=451^31.7^L 
  XX("V",6)=452^72.2^ 
  XX("V",7)=454^23.7^ 
  XX("V",8)=457^7.482^H 
  
COMPONENT/ENTRY POINT: LRSPEC(.r,l,i,[s],[.e])
 COMPONENT DESCRIPTION:   
  
 Obtains the specimen and collection information using lab variables. The STYPE
 parameter may be S for the specimen node, C for comments, V for all LRDNs, and
 A for S, C, and V. If no valid specimen data exists, results is returned
 undefined and error is 1 (otherwise 0).  
  
 arguments 
  
  .r    array of results, example: 
        RESULTS("C",#)=comments  RESULTS("S")=specimen node 
        RESULTS("V",#)=LRDN 
  l     LRDFN 
  i     LRIDT 
  [s]   STYPE (S: spec node, C: comment, V: test values, A: all) 
        default is A 
  [.e]  error 
  
 example 
  
 Examples are similar to SPEC^LRPXAPI but with LRDFN and LRIDT 
  instead of DFN and DATE.  
  D SPEC^LRPXAPI(.XX,2457,7099178.7755,"C") 
  returns: 
  XX("C",1)=Hemoglobin, Methemoglobin  10.7,1.1  
  XX("C",2)=Spontaneous 
  XX("C",3)=Arterial (AR) 
  
COMPONENT/ENTRY POINT: $$VERIFIED(l,i)
 COMPONENT DESCRIPTION:   
  
 Checks whether the tests in the lab collection have been verified and
 available for display. Returns 1 if verified, else 0. Note: Data references
 from the ^PXRMINDX indexes are always verified.  
  
 arguments 
  
  l     LRDFN 
  i     LRIDT 
  returns 1 or 0 
  
 example 
  
 Get a glucose result if verified.  
  I $$VERIFIED^LRPXAPI(4,LRIDT) D VAL^LRPXAPI(4,LRIDT,2) 
  
VARIABLES:  
COMPONENT/ENTRY POINT: $$MIVERIFY(l,i,s)
 COMPONENT DESCRIPTION:   
  
 Checks whether the Micro specimen has been verified and available for display.
 Returns 1 if verified, else 0.  
  
 arguments 
  
  l     LRDFN 
  i     LRIDT 
  s     Micro subscript 
        default "MI" 
  returns 1 or 0 
  
 example 
  
 If Micro is not verified then quit.  
  I '$$MIVERIFY^LRPXAPI(LRDFN,LRIDT) Q 
  
COMPONENT/ENTRY POINT: $$APVERIFY(l,i,s)
 COMPONENT DESCRIPTION:   
  
 Checks whether the AP specimen has been verified and available for display.
 Returns 1 if verified, else 0.  
  
 arguments 
  
  l     LRDFN 
  i     LRIDT 
  s     AP subscript [AU CY EM SP] 
  returns 1 or 0 
  
 example 
  
 If Cytology results are not verified then quit.  
  I '$$APVERIFY^LRPXAPI(LRDFN,LRIDT,"CY") Q 
  
COMPONENT/ENTRY POINT: $$VAL(l,i,d)
 COMPONENT DESCRIPTION:   
  
 Obtains the result node of a "CH" test value. If no valid value exists, "" is
 returned.  
  
 arguments 
  
  l     LRDFN lab patient id 
  i     LRIDT inverse date/time 
  d     LRDN data number 
  returns node values 
  
 examples 
  
 Get the value of a lab test.  
  S RESULT=$$VAL^LRPXAPI(15,70021211.1523,2) returns the entire result node 
  
 Get just the result of the lab test.  
  S RESULT=$P($$VAL^LRPXAPI(15,70021211.1523,2),U) gets just the result value 
  
 This is the entire node for this result.  
  W $$VAL^LRPXAPI(922,7009790.899758,4) 
  1.1^^81114.0000!!2160!!1^1499^72!0.7!1.5!!!!MG/DL!2!50^^^^605 
  
COMPONENT/ENTRY POINT: $$REFVAL(n)
 COMPONENT DESCRIPTION:   
  
 Obtains the values from the reference node. If no valid value exists, "" is
 returned. Used for any type of data (Chem, Micro, AP).  
  
 argument 
  
  n     reference node in ^LR 
  returns node values 
  
 examples 
  
 Get the reference nodes values.  
  S RESULT=$$REFVAL^LRPXAPI("6;CH;6988891.9063;605305") 
  where RESULT is the entire node: 
  3.7^L^81132.0000!!9830!!1^4838^72!4.0!6.7^^^^605 
  
 Get the result from the reference node values 
  S RESULT=$P($$REFVAL^LRPXAPI("6;CH;6988891.9063;605305"),U) 
  where RESULT is: 3.7 
  
 CH, Micro, and AP nodes can be obtained.  
  W $$REFVAL^LRPXAPI("6451;SP;7089590;2;1;2;1;1;1;0") 
  4405 
  
COMPONENT/ENTRY POINT: $$COMMENT(l,i)
 COMPONENT DESCRIPTION:   
  
 Returns 1 if any comments exist on this collection sample, else 0. Used only
 for "CH" data.  
  
 arguments 
  
  l     LRDFN 
  i     LRIDT 
  returns 1 or 0 
  
 example 
  
 Check to see if a comment was made on a sample.  
  I $$COMMENT^LRPXAPI(LRDFN,LRIDT) D FLAG 
  
COMPONENT/ENTRY POINT: ACCY(.t,a,d)
 COMPONENT DESCRIPTION:   
  
 Obtains those lab tests for a specific accession. The accession must be for a
 yearly accession area. Since the only a portion of the accession date is used
 in the accession, the year of the accession must be declared. The year would
 be in VA FileMan format or it's first number of the date to indicate the
 century.  
  
 arguments 
  
  t     array of tests returned, (ien)=ien^test name 
  a     accession, examples: CY 02 922, MI 99 3244 
  d     beginning date number (for the year 1992 this would be 2 
        or 2990000, for 2003 this would be 3 or 3030000) 
  
 examples 
  
 Get the tests from an accession where ACC="SP 02 559".  
  D ACCY^LRPXAPI(.TESTS,ACC,3) returns: 
  TESTS(1413)=1413^H & E STAIN 
  TESTS(5034)=5034^PARAFFIN BLOCK 
  
COMPONENT/ENTRY POINT: $$HASITEM(d,i)
 COMPONENT DESCRIPTION:   
  
 Checks if patient has had a test. Useful to filter from a list of lab tests
 only those the patient has actually had.  
  
 arguments 
  
  d     DFN 
  i     Item   lab test or result from ^PXRMINDX(63 indexes 
  returns 1 or 0 
  
 examples 
  
 Screens for only those tests where the patient has results.  
  S DIC("S")="I $P(^(0),U,4)=""CH"",$$HASITEM^LRPXAPI(DFN,+Y)" 
  
COMPONENT/ENTRY POINT: CHNODE(.r,n)
 COMPONENT DESCRIPTION:   
  
 Obtains the values for data stored on the CH node for lab results. These
 fields are not documented by the DD. These data store information such as
 LOINC and National Lab Test file information. The values are returned in an
 array subscripted by the type of information. The presence of values depends
 on many factors including the test's definition and proper mapping of Lab to
 LOINC and NLT files. These are the elements of the result node: 
  
  DATE-R  report status date/time 
  DATE-T   transmit status date/time 
  DEF   default value 
  DELTA-T   type of delta check 
  DELTA-V   delta value 
  FLAG   normal range flag 
  HIGH   reference high 
  HIGH-C   critical high 
  HIGH-T   therapeutic high 
  INSTITUTION   verifying institution 
  INSTRUMENT   instrument 
  LEDI   ledi transmission status 
  LOINC   loinc code for reported test 
  LOW   reference low 
  LOW-C   critical low 
  LOW-T   therapeutic low 
  MAP   historically mapped 
  METHOD   method suffix for reported test 
  NLT-O  nlt code for ordered test 
  NLT-R   nlt code for reported test 
  RESULT   test result 
  SPEC   site/specimen 61 IEN 
  TEST   lab test 60 IEN 
  TYPE   test type (output only, both, neither) 
  UNITS   units 
  VERIFIER   verifier duz 
  
 arguments 
  
  .r   array of results, example: 
       RESULTS("RESULT")=result 
       RESULTS("FLAG")=flag 
       RESULTS("UNITS")=units 
  n    reference node for ^PCRMINDX(63, indexes 
  
 example 
  
 Display the lab value and units.  
  D CHNODE^LRPXAPI(.RESULTS,NODE) 
  W !,RESULTS("RESULT")," ",RESULTS("UNITS") 
  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   VPR*1*2, released fall of 2013, uses routine LRPXAPI.
 VPR is already using the Clinical Reminders indices to pull data from other
 VistA applications, and wouldd like to use the index to pull some microbiology 
 data; LRPXAPI seems the cleanest way to resolve the values in the index and
 get the supporting data.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  

NUMBER: 4246                            IA #: 4246
  DATE CREATED: NOV 06, 2003            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: LRPXAPIU                     NAME: DBIA4246
  ID: LRPXAPIU
 GENERAL DESCRIPTION:   APIs for use with Lab data.  
  
 Arguments enclosed with brackets are optional. Arguments without brackets are
 required. Arguments preceded by a period should be called by reference.  
  
  STATUS: Active
COMPONENT/ENTRY POINT: $$LRDFN(d)
 COMPONENT DESCRIPTION:   
  
 Obtains LRDFN (Lab Patient ID) from DFN (Patient ID). If no valid DFN exists,
 0 is returned 
  
 argument 
  
  d     DFN 
  returns LRDFN 
  
 example 
  
  S LRDFN=$$LRDFN^LRPXAPIU(DFN) 
  
COMPONENT/ENTRY POINT: $$DFN(l)
 COMPONENT DESCRIPTION:   
  
 Obtains DFN (Patient ID) from LRDFN (Lab Patient ID). If no valid DFN exists,
 0 is returned.  
  
 argument 
  
  l     LRDFN 
  returns DFN 
  
 example 
  
  S DFN=$$DFN^LRPXAPIU(LRDFN) 
  
COMPONENT/ENTRY POINT: $$LRDFNM(l)
 COMPONENT DESCRIPTION:   
  
 Obtains patient name from LRDFN. If no valid name exists, "" is returned.  
  
 argument 
  
  l     LRDFN 
  returns Patient name 
  
 example 
  
 Write patient's name using LRDFN.  
  W $$LRDFNM^LRPXAPIU(LRDFN) 
  
COMPONENT/ENTRY POINT: $$DFNM(d)
 COMPONENT DESCRIPTION:   
  
 Obtains patient name from DFN. If no valid name exists, "" is returned.  
  
 argument 
  
  d     DFN 
  returns Patient name 
  
 example 
  
 Write patient's name using DFN.  
  W $$DFNM^LRPXAPIU(DFN) 
  
COMPONENT/ENTRY POINT: $$LRIDT(i)
 COMPONENT DESCRIPTION:   
  
 Lab stores patient results by time with most recent values first. To do this
 lab uses a convention of taking the date/time and subtracting 9999999. This
 collates as most recent first. This function performs the conversion of 
 date/time to inverse date/time (or an inverse date/time to a date/time).  
  
 argument 
  
  i     date/time or inverse date/time 
  returns inverse of argument 
  
 examples 
  
  S LRIDT=$$LRIDT^LRPXAPIU(3020807.1104) 
  This would set LRIDT to 6979191.8896 
  Likewise 
  S COLTIME=$$LRIDT^LRPXAPI(6979191.8896) 
  This would set COLTIME to 3020807.1104 
  
COMPONENT/ENTRY POINT: $$SPECNM(i)
 COMPONENT DESCRIPTION:   
  
 Obtains specimen name from specimen number in file 61. If no valid name
 exists, "" is returned.  
  
 argument 
  
  i     pointer to specimen in file 61 
  returns Specimen name 
  
 example 
  
 Write the specimen name using the variable LRBLOOD.  
  W $$SPECNM^LRPXAPIU(LRBLOOD) 
  
COMPONENT/ENTRY POINT: $$LRDN(t)
 COMPONENT DESCRIPTION:   
  
 Obtains lab data number (the subscript where results are stored in ^LR) from
 the test number in file 60. The lab data number is the middle piece of the
 data name (example: data name "CH;2;1" where 2 is the data number). If no
 valid data number exists, 0 is returned.  
  
 argument 
  
  t     pointer to lab test in file 60 
  returns data number 
  
 example 
  
 Get the data number for glucose.  
  S LRDN=$$LRDN^LRPXAPIU(+$O(^LAB(60,"B","GLUCOSE",0)) 
  
COMPONENT/ENTRY POINT: $$TEST(d)
 COMPONENT DESCRIPTION:   
  
 Obtains the test number in file 60 from lab data number (the subscript where
 results are stored in ^LR). If no valid test number exists, 0 is returned.  
  
 argument 
  
  d     data number 
  returns pointer to lab test in file 60 
  
 example 
  
 Get the test number for glucose 
  (in this case the data number for glucose is 2).  
  S TEST=$$TEST^LRPXAPIU(2) 
  
COMPONENT/ENTRY POINT: $$LRDNM(d)
 COMPONENT DESCRIPTION:   
  
 Obtains lab test name from data number. If no valid name exists, "" is
 returned.  
  
 argument 
  
  d     data number 
  returns Lab test name 
  
 example 
  
 Write the test name for glucose 
  (in this case the data  number for glucose is 2).  
  W $$LRDNM^LRPXAPIU(2) 
  
COMPONENT/ENTRY POINT: $$TESTNM(t)
 COMPONENT DESCRIPTION:   
  
 Obtains lab test name from test number in file 60. If no valid name exists, ""
 is returned.  
  
 argument 
  
  t     pointer to lab test in file 60 
  returns Lab test name 
  
 example 
  
 Write the test name for glucose 
  (in this case the test number for glucose is 175).  
  W $$TESTNM^LRPXAPIU(175) 
  
COMPONENT/ENTRY POINT: $$AB(d)
 COMPONENT DESCRIPTION:   
  
 Obtains antimicrobial number in file 62.06 from antimicrobial data number. If
 no valid test number exists, 0 is returned.  
  
 argument 
  
  d     data number for antimicrobial field in file 63 
  returns data number for antimicrobial 
  
 example 
  
 Get the antimicrobial number.  
  S ABN=$$AB^LRPXAPIU(ABDN) 
  
COMPONENT/ENTRY POINT: $$ABDN(i)
 COMPONENT DESCRIPTION:   
  
 Obtains antimicrobial data number from antimicrobial number in file 62.06.. If
 no valid test number exists, 0 is returned.  
  
 argument 
  
  i     pointer to antimicrobial in file 62.06 
  returns data number for antimicrobial in file 63 
  
 example 
  
 Get the antimicrobial data number.  
  S ABDN=$$AB^LRPXAPIU(ABN) 
  
COMPONENT/ENTRY POINT: $$ABNM(i)
 COMPONENT DESCRIPTION:   
  
 Obtains antimicrobial name from antimicrobial number in file 62.06. If no
 valid name exists, "" is returned.  
  
 argument 
  
  i     pointer to antimicrobial in file 62.06 
  returns antimicrobial name 
  
 example 
  
 WRITE the antimicrobial name from it's IEN.  
  W $$ABNM^LRPXAPIU(ABN) 
  
COMPONENT/ENTRY POINT: $$TB(d)
 COMPONENT DESCRIPTION:   
  
 Obtains mycobacteria field number in file 63 from the mycobacteria data
 number. TB drugs are defined as fields in file 63. If no valid field number
 exists, 0 is returned.  
  
 argument 
  
  d     TB data number 
  returns field number for TB drug 
  
 example 
  
 Get the TB field number from TBDN.  
  S TBN=$$TB^LRPXAPIU(TBDN) 
  
COMPONENT/ENTRY POINT: $$TBDN(f)
 COMPONENT DESCRIPTION:   
  
 Obtains the TB data number in file 63 from the TB field number. TB drugs are
 defined as fields in file 63. If no valid field number exists, 0 is returned.  
  
 argument 
  
  f     field number for TB drug 
  returns TB data number 
  
 example 
  
 Get the TB data number from TBN.  
  S TBDN=$$TBDN^LRPXAPIU(TBN) 
  
COMPONENT/ENTRY POINT: $$TBNM(f)
 COMPONENT DESCRIPTION:   
  
 Obtains TB drug name from TB field number. TB drugs are defined as fields in
 file 63. If no valid name exists, "" is returned.  
  
 argument 
  
  f     field number for TB drug 
  returns name of TB drug 
  
 example 
  
 Write the TB drug name from it's TB drug number. 
  W $$TBNM^LRPXAPIU(TBDN) 
  
COMPONENT/ENTRY POINT: $$BUGNM(i)
 COMPONENT DESCRIPTION:   
  
 Obtains organism name from organism number in file 61.2. If no valid name
 exists, "" is returned.  
  
 argument 
  
  i     pointer to organism in file 61.2 
  returns organism name 
  
 example 
  
 Write the name of the organism from BUG.  
  W $$BUGNM^LRPXAPIU(BUG) 
  
COMPONENT/ENTRY POINT: $$ORGNM(i)
 COMPONENT DESCRIPTION:   
  
 Obtains  the organ/tissue name from organ/tissue number in file 61. If no
 valid name exists, "" is returned.  
  
 argument 
  
  i     pointer to organ/tissue in file 61 
  returns organ/tissue name 
  
 example 
  
 Write the organ/tissue name for SPEC.  
  W $$ORGNM^LRPXAPIU(SPEC) 
  
COMPONENT/ENTRY POINT: $$DISNM(i)
 COMPONENT DESCRIPTION:   
  
 Obtains disease name from disease number in file 61.4. If no valid name
 exists, "" is returned.  
  
 argument 
  
  i     pointer to disease in file 61.4 
  returns disease name 
  
 example 
  
 Write the disease name for DISEASE.  
  W $$DISNM^LRPXAPIU(DISEASE) 
  
COMPONENT/ENTRY POINT: $$ETINM(i)
 COMPONENT DESCRIPTION:   
  
 Obtains etiology name from etiology number in file 61.2. If no valid name
 exists, "" is returned.  
  
 argument 
  
  i     pointer to etiology in file 61.2 
  returns etiology name 
  
 example 
  
 Write the etiology name for ETIOLOGY.  
  W $$ETINM^LRPXAPIU(ETIOLOGY) 
  
COMPONENT/ENTRY POINT: $$MORPHNM(i)
 COMPONENT DESCRIPTION:   
  
 Obtains morphology name from morphology number in file 61.1.  If no valid name
 exists, "" is returned.  
  
 argument 
  
  i     pointer to morphology in file 61.1 
  returns morphology name 
  
 example 
  
 Write the morphology name for MORPH.  
  W $$MORPHNM^LRPXAPIU(MORPH) 
  
COMPONENT/ENTRY POINT: $$FUNNM(i)
 COMPONENT DESCRIPTION:   
  
 Obtains function name from function number in file 61.3. If no valid name
 exists, "" is returned.  
  
 argument 
  
  i     pointer to function in file 61.3 
  returns function name 
  
 example 
  
 Write the function name for FUNC.  
  W $$FUNNM^LRPXAPIU(FUNC) 
  
COMPONENT/ENTRY POINT: $$PROCNM(i)
 COMPONENT DESCRIPTION:   
  
 Obtains procedure name from procedure number in file 61.5. If no valid name
 exists, "" is returned.  
  
 argument 
  
  i     pointer to procedure in file 61.5 
  returns procedure name 
  
 example 
  
 Write the procedure name for PROC.  
  W $$PROCNM^LRPXAPIU(PROC) 
  
COMPONENT/ENTRY POINT: $$DOD(d)
 COMPONENT DESCRIPTION:   
  
 Obtains date of death from the appropriate field in the patient file -
 ^DPT(DFN,.35). If no valid date of death exists, 0 is returned.  
  
 argument 
  
  d     DFN 
  returns date of death 
  
 example 
  
 Write the date of death for a patient using DFN. 
  W $$DOD^LRPXAPIU(DFN) 
  
COMPONENT/ENTRY POINT: $$ITEMNM(i)
 COMPONENT DESCRIPTION:   
  
 Obtains item name from item of AP or Micro type. These items are composed of a
 type [A M]; file (depends on type); file number. This function uses that
 information to display the name of the file entry.  
  
 argument 
  
  i     item 
  returns item name 
  
 example 
  
 Write the item name for ITEM where ITEM="A;O;343".  
  W $$ITEMNM^LRPXAPIU(ITEM) 
  
COMPONENT/ENTRY POINT: DATES(d1,d2)
 COMPONENT DESCRIPTION:   
  
 Using two dates for comparison, this procedure returns the same dates but with
 the first parameter being the oldest and the second parameter being the most
 recent. This is used for a date range where it is not certain which dates are
 the beginning and end. If no values are assigned to the dates or if they are
 undefined, the first argument is returned as 0 and the second argument as
 9999999. This would be a date range of all dates.  
  
 arguments 
  
  .d1     date (returns as the older of d1 and d2) 
  .d2     date (returns as the most recent of d1 and d2) 
  
 example 
  
 From the two dates, START and STOP, ensure that START is the 
  oldest date.  
  D DATES^LRPXAPIU(.START,.STOP) 
  
COMPONENT/ENTRY POINT: NORMALS(.l,.h,t,s)
 COMPONENT DESCRIPTION:   
  
 This returns the high and low reference range on a lab test. A specimen is
 required.  
  
 arguments 
  
  .l    low reference range 
  .h    high reference range 
  t     pointer to laboratory test 60 
  s     pointer to specimen 61 
  
 example 
  
 Get low and high reference range on TEST and SPECIMEN.  
  D NORMALS^LRPXAPIU(.LOW,.HIGH,TEST,SPEC) 
  
COMPONENT/ENTRY POINT: $$EXTVALUE(v,n)
 COMPONENT DESCRIPTION:   
  
 Obtains external value of a value extracted using the reference node.  
  
 arguments 
  
  v     value in internal format 
  n     reference node 
  returns external format of value 
  
 example 
  
 Returns external format of value obtained from the reference node.  
  S VALUE=$$EXTVALUE^LRPXAPIU(VALUE,NODE) 
  
COMPONENT/ENTRY POINT: $$CATEGORY(s,[t])
 COMPONENT DESCRIPTION:   Obtains AP or Micro category from the subscript
 number of Micro or AP data in file 63. Data are identified as bacteria, 
 parasite, fungus, mycobacteria, or virus. Different kinds of data are stored
 on these subscripts depending on the type of organism or AP specimen. This
 function determines the type of organism or AP specimen when knowing the
 subscript.  
  
 arguments 
  
  s     Micro subscript number [3 6 9 12 17] 
        or AP subscript [AU CY EM SP] 
  [t]   type [A M] 
        default A 
  returns Micro category [B P F M V] or AP category [A C E S] 
  
 example 
  
 Get the category from the subscript.  
  S CAT=$$CATEGORY^LRPXAPIU(SUB) 
  
COMPONENT/ENTRY POINT: $$CATSUB(c,[t])
 COMPONENT DESCRIPTION:   
  
 Obtains AP or Micro subscript number from the category letter for AP or Micro
 data in file 63. Data are identified as bacteria, parasite, fungus,
 mycobacteria, or virus and stored on specific subscript numbers depending on
 the type of organism. For AP this function determines the subscript when 
 knowing the type of AP specimen.. For Micro this function determines the
 subscript number when knowing the type of organism.  
  
 arguments 
  
  c     Micro category [B P F M V] 
        or AP category [A C E S] 
  [t]   type [A M] 
        default A 
  returns Micro subscript number [3 6 9 12 17] or AP subscript 
  [AU CY EM SP] 
  
 example 
  
 Get the subscript number of Parasitology in Micro.  
  S SUB=$$CATSUB^LRPXAPIU("P","M") 
  
COMPONENT/ENTRY POINT: $$CONDOK(c,[t])
 COMPONENT DESCRIPTION:   
  
 Checks condition to determine if it is valid. If the condition is invalid 0 is
 returned. If the condition is valid 1 is returned. The condition is used in
 filtering lab results. This function may be used to check the syntax of the
 condition before it is used. The condition is M code starting with an IF 
 statement. Specific variables are used for different types lab data. Operators
 are specific to the variables used. An operator is followed by a value to form
 a statement (example: E=283). Multiple statements can be used by separating
 with the character: "~" for occurrence match or "|" for exact match.  For
 Chemistry (type C)[F S V] where F is flag [H, L, H*, L*], S is specimen IEN,
 and V is the value of lab test (free text or numeric). For Microbiology (type
 M)[A C I M O R S T] where A is antimicrobial IEN, C is category [B F M P V], I
 is interpretation (free text   usually [R S I]), M is mycobacteria
 antimicrobial IEN (actually a # in the DD), O is organism IEN, R is result
 (free text or numeric   usually [R S I], S is specimen IEN, and T is test IEN.
 For Anatomic Pathology (type A)[C D E F I M O P S T] where C is category [A C
 E S], D is disease IEN, E is etiology IEN, F is function IEN, I is ICD9 IEN, M
 is morphology IEN, O is organ/tissue IEN, P is procedure IEN, S is specimen
 (free text), and T is test IEN. Operators for variables: V: =, '=, >, '>, <,
 '<, [, '[, [, '[ [I R F]: =, '=, [, '[, [, '[ S when type is A: =, '=, [, '[,
 [,'[ All other variables: =, '= 
  
 arguments 
  
  c      condition condition is returned as 0 if invalid 
         a valid condition is returned as 1 
  [t]    type of data [C M A] Chem, Micro, or AP 
         default: C 
  returns 1 if condition syntax is ok, else 0 
  
 examples 
  
 Check syntax of COND.  
  I $L(COND),'$$CONDOK^LRPXAPIU(COND) Q 
  
 Evaluate a string as a valid condition.  
  W $$CONDOK^LRPXAPIU("V>100") 
  W $$CONDOK^LRPXAPIU("F[""*""","C") 
  W $$CONDOK^LRPXAPIU("M=204","A") 
  W $$CONDOK^LRPXAPIU("S[""TISSUE"""~C=""C""","A") 
  W $$CONDOK^LRPXAPIU("I[""R""|A=123","M") 
  W $$CONDOK^LRPXAPIU("C=""V""","M") 
  W $$CONDOK^LRPXAPIU("A=123|O=323|S=72|I[""R"""|T=334,"M") 
  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS
 SUBSCRIBING DETAILS:   added 6/10/09 
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   VPR*1*2 needed a couple of the functions contained in
 LRXAPIU, ICR #4246 to work with PXRM indices.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 5/16/2022, effective with DSSV*1.1 DSS Class 3
 product using $$TESTNM Document Only 

NUMBER: 4247                            IA #: 4247
  DATE CREATED: NOV 20, 2004            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: LRPXSXRL                     NAME: 4247
  ID: LRPXSXRL
 GENERAL DESCRIPTION:   This routine and entry point is used fo building the
 Clinical Reminders Index for the LAB DATA file, #63.  There are no required
 variables.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LRPXSXRL
KEYWORDS: CLINICAL REMINDERS INDEX
COMPONENT/ENTRY POINT: LAB
 COMPONENT DESCRIPTION:   This entry point is called to build the Clinical
 Reminders Index fo the LAB DATA file.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clinical reminders calls this entry point to build the
 Clinical Reminders Index for the LAB DATA file.  

NUMBER: 4248                            IA #: 4248
  DATE CREATED: AUG 24, 2004
  CUSTODIAL PACKAGE: VISTA DATA EXTRACTION FRAMEWORK
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VDEFEL                       NAME: VDEF MESSAGE-BUILDING UTILITIES
  ID: VDEFEL
 GENERAL DESCRIPTION:   In the VDEF process, domain-specific routines build
 messages that are sent to the HL7 system for distribution.  This IA contains
 utilities that perform common functions often needed by these message building
 routines.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VDEF
KEYWORDS: MESSAGE BUILDING
KEYWORDS: HL7
COMPONENT/ENTRY POINT: SETDLMS
 COMPONENT DESCRIPTION:   Sets HL7 delimiters into individual variables based
 either on elements of HL() array or default HL7 delimiter values.  
VARIABLES: HL()                         TYPE: Input
 VARIABLES DESCRIPTION:   The HL() is optional.  It is passed through the
 symbol table if it exists.  HL() is set by INIT^HLFNC2(). 
  
 If the HL() array is not present, default values are output.  
VARIABLES: SEPC                         TYPE: Output
 VARIABLES DESCRIPTION:   Component separator.  Default = ~.  
VARIABLES: SEPS                         TYPE: Output
 VARIABLES DESCRIPTION:   Subcomponent separator.  Default = &.  
VARIABLES: SEPR                         TYPE: Output
 VARIABLES DESCRIPTION:   Repetition separator.  Default = |.  
VARIABLES: SEPE                         TYPE: Output
 VARIABLES DESCRIPTION:   Escape character.  Default = \.  
VARIABLES: SEPF                         TYPE: Output
 VARIABLES DESCRIPTION:   Field separator.  Default = ^.  
COMPONENT/ENTRY POINT: $$XCN200(DUZ,source)
 COMPONENT DESCRIPTION:   Given an IEN from the NEW PERSON file (#200) function
 returns an XCN data type.  
  
 Optionally, a source of the data can be passed to the API to identify in the
 HL7 segment where the person information comes from.  
  
 Prerequisite: HL7 delimiters set into variables as done by SETDLMS^VDEFEL must
 be present.  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   DUZ = IEN of a New Person file entry is required.  
VARIABLES: $$XCN200                     TYPE: Output
 VARIABLES DESCRIPTION:   Function returns a XCN HL7 data type based on the
 indicated New Person file entry.  
  
 Example: 520637377~CREAVEN~DON~~~~~VistA200 
VARIABLES: source                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional.  The string passed will be added to the HL7
 data to identify where the data originates.  Default value of 'VistA200' is
 used if nothing is passed in this parameter.  
COMPONENT/ENTRY POINT: $$TS(date_time)
 COMPONENT DESCRIPTION:   Given a date/time value, function returns an HL7 TS
 data type.  
  
 Examples: 
  
 1.      W $$TS^VDEFEL($H) 
         20040820182643-0400 
  
 2.      W $$TS^VDEFEL("3140820.154420") 
         20140820154420-0400 
  
 3.      W $$TS^VDEFEL("AUG 23, 2004@100923") 
         20040823100923-0400 
VARIABLES: date_time                    TYPE: Input
 VARIABLES DESCRIPTION:   A date/time value in either $H, FileMan internal, or
 an external format understood by FileMan's date/time utilities.  
VARIABLES: $$TS                         TYPE: Output
 VARIABLES DESCRIPTION:   Function returns a TS data type, including time zone. 
 No time zone is returned if no time is included in input.  
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Added in support of PFSS development 
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   Added in support of PFSS development 
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
 SUBSCRIBING DETAILS:   ADDED 10/7/2009 

NUMBER: 4249                            IA #: 4249
  FILE NUMBER: 61.1                     GLOBAL ROOT: LAB(61.1,
  DATE CREATED: AUG 24, 2004            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DIRECT READ OF THE MORPHOLOGY FIELD FILE
  ID: LAB(61.1,
GLOBAL REFERENCE: LAB(61.1,
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
 GENERAL DESCRIPTION:   Clinical Reminders is requesting permission to do a
 direct read on piece 1 and 2 of File #61.1 zero node. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LAB(61.1,
KEYWORDS: PXRM
KEYWORDS: LAB
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4250                            IA #: 4250
  DATE CREATED: SEP 15, 2004
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXPXRM
  NAME: PCE APIs FOR THE CLINICAL REMINDERS INDEX
  ID: PXPXRM
 GENERAL DESCRIPTION:   This ICR will provide subscribing packages the ability
 to get data from the PCE V-files 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PCE
KEYWORDS: VCPT
KEYWORDS: VHF
KEYWORDS: VIMM
KEYWORDS: VPEDU
KEYWORDS: VPOV
KEYWORDS: VSKIN
KEYWORDS: VXAM
KEYWORDS: VICR
KEYWORDS: VSCDATA
COMPONENT/ENTRY POINT: VCPT(DA,.DATA)
 COMPONENT DESCRIPTION:   This entry point is called as D
 VCPT^PXPXRM(DA,.DATA). The  data from V CPT, file #9000010.18, is returned in
 the DATA array.  
  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the Data in the V VCPT file,
 #9000010.18 
  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   The data array that is passed back to the calling
 package.  
  
  DATA("VISIT")=Pointer to the VISIT file, #9000010 
  DATA("PROVIDER NARRATIVE")=Pointer to PROVIDER NARRATIVE file, #9999999.27 
  DATA("DIAGNOSIS")=Pointer to ICD DIAGNOSIS file, #80 
  DATA("DIAGNOSIS 2")=Pointer to ICD DIAGNOSIS file, #80 
  DATA("DIAGNOSIS 3")=Pointer to ICD DIAGNOSIS file, #80 
  DATA("DIAGNOSIS 4")=Pointer to ICD DIAGNOSIS file, #80 
  DATA("DIAGNOSIS 5")=Pointer to ICD DIAGNOSIS file, #80 
  DATA("DIAGNOSIS 6")=Pointer to ICD DIAGNOSIS file, #80 
  DATA("DIAGNOSIS 7")=Pointer to ICD DIAGNOSIS file, #80 
  DATA("DIAGNOSIS 8")=Pointer to ICD DIAGNOSIS file, #80 
  DATA("PRINCIPLE PROCEDURE")=Set of codes: 
    Y=Yes, N=No 
  DATA("QUANTITY")=An integer 
  DATA("EVENT DATE AND TIME")=Date and time in FileMan internal format 
  DATA("ENCOUNTER PROVIDER")=Pointer to the NEW PERSON file, #200 
  DATA("ORDERING PROVIDER")=Pointer to the NEW PERSON file, #200 
  DATA("COMMENTS")=Free text, 1 to 245 characters 
  DATA("PACKAGE")=Pointer to the PACKAGE file, #9.4 
  DATA("DATA SOURCE")=Pointer to the PCE DATA SOURCE file, #839.7 
  
COMPONENT/ENTRY POINT: VHF(DA,.DATA)
 COMPONENT DESCRIPTION:   This entry point is called as D VHF^PXPXRM(DA,.DATA).
 The data from V HEALTH FACTORS, file #9000010.23, is returned in the DATA
 array.  
  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the data in the V HEALTH
 FACTORS file, #9000010.23 
  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   
  
  DATA("VISIT")=Pointer to the VISIT file, #9000010 
  DATA("LEVEL/SEVERITY")=Set of codes: 
    M=Minimal, MO=Moderate, H=Heavy/Severe 
  DATA("VALUE")=Set of codes: 
    M=Minimal, MO=Moderate, H=Heavy/Severe 
  DATA("EVENT DATE AND TIME")=Date and time in FileMan internal format 
  DATA("ENCOUNTER PROVIDER")=Pointer to the NEW PERSON file, #200 
  DATA("ORDERING PROVIDER")=Pointer to the NEW PERSON file, #200 
  DATA("COMMENTS")=Free text, 1 to 245 characters 
  DATA("MEASUREMENT")=MAGNITUDE^UCUM code 
    MAGNITUDE is a number and UCUM code is a pointer to the UCUM CODES 
    file, #757.5 
  DATA("PACKAGE")=Pointer to the PACKAGE file, #9.4 
  DATA("DATA SOURCE")=Pointer to the PCE DATA SOURCE file, #839.7 
  
  
COMPONENT/ENTRY POINT: VIMM(DA,.DATA)
 COMPONENT DESCRIPTION:   This entry point is called as D
 VIMM^PXPXRM(DA,.DATA). The data from V IMMUNIZATION, file #9000010.11, is
 returned in the DATA array.  
  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the entry in the V
 IMMUNIZATION file, #9000010.11 
  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   The data array that is passed back to the calling
 package.  
  
  DATA("VISIT")=Pointer to the VISIT file, #9000010 
  DATA("SERIES")=Set of codes: 
    P=Partially Complete, C=Complete, B=Booster, a number 1-8=1-8 
  DATA("VALUE")=Set of codes: 
    P=Partially Complete, C=Complete, B=Booster, a number 1-8=1-8 
  DATA("REACTION")=Set of codes: 
    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 
  DATA("CONTRAINDICATED")=Set of codes: 1=Yes 
  DATA("COMMENTS")=Free text, 1 to 245 characters 
  DATA("EVENT DATE TIME")=Date and time in FileMan internal format 
  DATA("ORDERING PROVIDER")=IEN^Name 
    IEN = Pointer to the NEW PERSON file, #200 
  DATA("ENCOUNTER PROVIDER")=IEN^Name 
    IEN = Pointer to the NEW PERSON file, #200 
  DATA("DOSE")=Number (e.g., 0.5) 
  DATA("DOSE UNITS")=UCUM Code (e.g., mL) 
  DATA("DATE RECORDED")=Date and time in FileMan internal format 
  DATA("DOCUMENTER")= IEN^Name 
    IEN = Pointer to the NEW PERSON file, #200 
  DATA("LOT NUMBER")=IEN^Lot Number 
    IEN = Pointer to the IMMUNIZATION LOT file, #9999999.41 
  DATA("MANUFACTURER")=IEN^Name 
    IEN = Pointer to the IMM MANUFACTURER file, #9999999.04 
  DATA("EXPIRATION DATE")=Date in FileMan internal format 
  DATA("INFO SOURCE")=IEN^HL7 Code^Name 
    IEN = Pointer to the IMMUNIZATION INFO SOURCE file, #920.1 
  DATA("ADMIN ROUTE")=IEN^HL7 Code^Name 
    IEN = Pointer to the IMM ADMINISTRATION ROUTE file, #920.2 
  DATA("ADMIN SITE")=IEN^HL7 Code^Name 
    IEN = Pointer to the IMM ADMINISTRATION  SITE (BODY) file, #920.3 
  DATA("VIS OFFERED",n,0)=IEN^Date Offered^Name^Edition Date^Language 
    IEN = Pointer to the VACCINE INFORMATION STATEMENT file, #920 
    Date Offered=Date in FileMan internal format 
    Edition Date=Date in FileMan internal format 
  DATA("REMARKS",n,0)=Free text, word-processing 
  DATA("IMMUNIZATION")=IEN^Name 
    IEN = Pointer to the IMMUNIZATION file, #9999999.14 
  DATA("CVX")=CVX Code 
  DATA("VISIT DATE TIME")=Date and Time in FileMan internal format 
  DATA("FACILITY")=IEN^Name^Station # 
    IEN = Pointer to the INSTITUTION file, #4 
  DATA("LOCATION")=IEN^Name 
    IEN = Pointer to the HOSPITAL LOCATION file, #44 
  DATA("CODES",Coding System Name)=Code 1^Code 2^... Code x 
  DATA("VACCINE GROUP",n,0)=Free Text 2-30 characters in length 
  DATA("WARNING ACK")=Set of codes: 1=Yes 
  DATA("OVERRIDE REASON")=Free Text 3-245 characters in length 
  DATA("PACKAGE")=Pointer to the PACKAGE file, #9.4 
  DATA("DATA SOURCE")=IEN^Name 
    IEN = Pointer to the PCE DATA SOURCE file, #839.7 
  
  
  
COMPONENT/ENTRY POINT: VPEDU(DA,.DATA)
 COMPONENT DESCRIPTION:   This entry point is called as D
 VPEDU^PXPXRM(DA,.DATA). The data from V PATIENT ED, file #9000010.16, is
 returned in the DATA array.  
  
  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the entry in the V PATIENT
 ED file, #9000010.16 
  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   The data array that is passed back to the calling
 package.  
  
  DATA("VISIT")=Pointer to the VISIT file, #9000010 
  DATA("LEVEL OF UNDERSTANDING")=Set of codes: 
    1=Poor, 2=Fair, 3=Good 
    4=Group-No Assessment, 5=Refused 
  DATA("VALUE")=Set of codes: 
    1=Poor, 2=Fair, 3=Good 
    4=Group-No Assessment, 5=Refused 
  DATA("EVENT DATE AND TIME")=Date and time in FileMan internal format 
  DATA("ENCOUNTER PROVIDER")=Pointer to the NEW PERSON file, #200 
  DATA("ORDERING PROVIDER")=Pointer to the NEW PERSON file, #200 
  DATA("COMMENTS")=Free text, 1 to 245 characters 
  DATA("MEASUREMENT")=MAGNITUDE^UCUM code 
    MAGNITUDE is a number and UCUM code is a pointer to the UCUM CODES 
    file, #757.5 
  DATA("PACKAGE")=Pointer to the PACKAGE file, #9.4 
  DATA("DATA SOURCE")=Pointer to the PCE DATA SOURCE file, #839.7 
  
COMPONENT/ENTRY POINT: VPOV(DA,.DATA)
 COMPONENT DESCRIPTION:   This entry point is called by D
 VPOV^PXPXRM(DA,.DATA). The data from V POV, file #9000010.07, is returned in
 the DATA array.  
  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the entry in the V POV file,
 #9000010.07 
  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   The data array that is passed back to the calling
 package.  
  
  DATA("VISIT")=Pointer to the VISIT file, #9000010 
  DATA("PROVIDER NARRATIVE")=Pointer to the Provider Narrative file,
 #9999999.27 
  DATA("MODIFIER")=Set of codes: 
    C=Consider, D=Doubtful, F=Follow Up 
    M=Maybe,    O=Rule Out, P=Probable 
    R=Resolved, S=Suspect,  T=Status Post 
  DATA("PRIMARY/SECONDARY")=Set of codes: 
    P=Primary, S=Secondary 
  DATA("DATE OF INJURY")=Date and time in FileMan internal format 
  DATA("CLINICAL TERM")=Pointer to the Expressions file, #757.01 
  DATA("PROBLEM LIST ENTRY")=Pointer to the Problem file, #9000011 
  DATA("EVENT DATE AND TIME")=Date and time in FileMan internal format 
  DATA("ENCOUNTER PROVIDER")=Pointer to the NEW PERSON file, #200 
  DATA("ORDERING PROVIDER")=Pointer to the NEW PERSON file, #200 
  DATA("COMMENTS")=Free text, 1 to 245 characters 
  DATA("PACKAGE")=Pointer to the PACKAGE file, #9.4 
  DATA("DATA SOURCE")=Pointer to the PCE DATA SOURCE file, #839.7 
  
  
COMPONENT/ENTRY POINT: VSKIN(DA,.DATA)
 COMPONENT DESCRIPTION:   This entry point is called by D
 VSKIN^PXPXRM(DA,.DATA). The data from V SKIN TEST, file #9000010.12, is
 returned in the DATA array.  
  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the entry in the V SKIN TEST
 file #9000010.12 
  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   The data array that is passed back to the calling
 Package.  
  
  DATA("VISIT")=Pointer to the VISIT file, #9000010 
  DATA("RESULTS")=Set of codes: 
    P=Positive, N=Negative, D=Doubtful, O=No Take 
  DATA("VALUE")=Set of codes: 
    P=Positive, N=Negative, D=Doubtful, O=No Take 
  DATA("DATE READ")=Date and time in FileMan internal format 
  DATA("READING")=Number (0-40) 
  DATA("SKIN TEST")=IEN^Name 
    IEN = Pointer to the SKIN TEST file, #9999999.28 
  DATA("VISIT DATE TIME")=Date and time in FileMan internal format 
  DATA("FACILITY")=IEN^Name^Station # 
    IEN = Pointer to the INSTITUTION file, #4 
  DATA("LOCATION")=IEN^Name 
    IEN = Pointer to the HOSPITAL LOCATION file, #44 
  DATA("READER")=IEN^Name 
    IEN = Pointer to the NEW PERSON file, #200 
  DATA("EVENT DATE TIME")=Date and time in FileMan internal format 
  DATA("ORDERING PROVIDER")=IEN^Name 
    IEN = Pointer to the NEW PERSON file, #200 
  DATA("ENCOUNTER PROVIDER")=IEN^Name 
    IEN = Pointer to the NEW PERSON file, #200 
  DATA("D/T PLACEMENT RECORDED")=Date and time in FileMan internal format 
  DATA("ANATOMIC LOC")=IEN^HL7 Code^Name 
    IEN = Pointer to the IMM ADMINISTRATION SITE (BODY) file, #920.3 
  DATA("HOURS READ")=Number 
  DATA("D/T READING RECORDED")=Date and time in FileMan internal format 
  DATA("READING COMMENTS")=Free text, 1 to 245 characters 
  DATA("PACKAGE")=Pointer to the PACKAGE file, #9.4 
  DATA("DATA SOURCE")=Pointer to the PCE DATA SOURCE file, #839.7 
  
COMPONENT/ENTRY POINT: VXAM(DA,.DATA)
 COMPONENT DESCRIPTION:   This entry point is called by D
 VXAM^PXPXRM(DA,.DATA). The data from V EXAM, file #9000010.13, is returned in
 the DATA array.  
  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the entry in the V EXAM
 file, #9000010.13 
  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   The data array that is passed back to the calling
 package.  
  
  DATA("VISIT")=Pointer to the VISIT file, #9000010 
  DATA("RESULT")=Set of Codes: 
    A=Abnormal, N=Normal 
  DATA("VALUE")=Set of Codes: 
    A=Abnormal, N=Normal 
  DATA("EVENT DATE AND TIME")=Date and time in FileMan internal format 
  DATA("ENCOUNTER PROVIDER")=Pointer to the NEW PERSON file, #200 
  DATA("ORDERING PROVIDER")=Pointer to the NEW PERSON file, #200 
  DATA("COMMENTS")=Free text, 1 to 245 characters 
  DATA("MEASUREMENT")=MAGNITUDE^UCUM code 
    MAGNITUDE is a number and UCUM code is a pointer to the UCUM CODES 
    file, #757.5 
  DATA("PACKAGE")=Pointer to the PACKAGE file, #9.4 
  DATA("DATA SOURCE")=Pointer to the PCE DATA SOURCE file, #839.7 
  
  
COMPONENT/ENTRY POINT: VICR(DA,.DATA)
 COMPONENT DESCRIPTION:   This entry point is called by D
 VICR^PXPXRM(DA,.DATA). The data from V IMM CONTRA/REFUSAL EVENTS, file
 #9000010.707, is returned in the DATA array.  
  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the entry in the V IMM
 CONTRA/REFUSAL EVENTS file #9000010.707 
  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   The data array that is passed back to the calling
 package.  
  
  DATA("VISIT")=Pointer to the VISIT file, #9000010 
  DATA("CONTRA/REFUSAL")=Variable Pointer*^Name 
    Variable Pointer to the IMM CONTRAINDICATION REASONS file, #920.4 or 
    IMM REFUSAL REASONS file, #920.5 
  DATA("IMMUN")= IEN^Name 
    IEN = Pointer to the IMMUNIZATION file, #9999999.14 
  DATA("WARN UNTIL DATE")=Date in FileMan internal format 
  DATA("D/T RECORDED")=Date and time in FileMan internal format 
  DATA("EVENT D/T")=Date and time in FileMan internal format 
  DATA("ENC PROVIDER")= IEN^Name 
    IEN = Pointer to the NEW PERSON file, #200 
  DATA("COMMENTS")=Free Text, 1 to 245 characters 
  DATA("PACKAGE")=Pointer to the PACKAGE file, #9.4 
  DATA("DATA SOURCE")=Pointer to the PCE DATA SOURCE file, #839.7 
  
COMPONENT/ENTRY POINT: VSCDATA(DA,.DATA)
 COMPONENT DESCRIPTION:   This entry point is called as D
 VSCDATA^PXPXRM(DA,.DATA). The data from the V STANDARD CODES, file
 #9000010.71, is returned in the DATA array.  Note: This entry point is added
 with patch PX*1*211.  
  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the entry in the V STANDARD
 CODES file, #9000010.71 
  
  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   The data array that is passed back to the calling
 package.  
  
  DATA("VISIT")=Pointer to the VISIT file, #9000010 
  DATA("PROVIDER NARRATIVE")=Pointer to the Provider Narrative file, 
    #99999999.27.  
  DATA("EVENT DATE AND TIME")=Date and time in FileMan internal format 
  DATA("ENCOUNTER PROVIDER")=Pointer to the NEW PERSON file, #200 
  DATA("ORDERING PROVIDER")=Pointer to the NEW PERSON file, #200 
  DATA("COMMENTS")=Free text, 1 to 245 characters 
  DATA("MEASUREMENT")=MAGNITUDE^UCUM code MAGNITUDE is a number and UCUM 
  code is a pointer to the UCUM CODES file, #757.5 
  DATA("PACKAGE")=Pointer to the PACKAGE file, #9.4 
  DATA("DATA SOURCE")=Pointer to the PCE DATA SOURCE file, #839.7 
  
  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clinical Reminders will use these calls to retrieve 
 information from a V-file after looking up the reference in the Clinical
 Reminders Index.  
  
  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Effective with VPR*1*0.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 8/2/2022, effective with DSSV*1.1 DSS Class 3
 product Document Only 
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 7/28/26. effective with patch CDSP*1.0*4, to call
 components VPEDU and VHF. 
  DATE ACTIVATED: MAR 14, 2024

NUMBER: 4251                            IA #: 4251
  DATE CREATED: SEP 29, 2003
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMVDCEXT                     NAME: GMVDCEXT
  ID: GMVDCEXT                          STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN1(RESULT,GMVDFN,GMVFMT,GMVABR,GMVALL,GMVBEG,GMVEND,GMVM
SYS,GMVEER)
 COMPONENT DESCRIPTION:   This entry point returns patient vitals data from the
 GMRV VITAL MEASUREMENT (#120.5) file based on the input parameters selected.  
VARIABLES: RESULT                       TYPE: Both
 VARIABLES DESCRIPTION:   The name of the array to return data in (Required).  
  
  The return array is: 
   Array(0)=OK or ERROR 
   Array(n)=piece1^piece2^piece3^piece4^piece5^piece6^piece7^piece8^piece9 
            ^piece10^piece11^piece12 
  
  where: 
   n and piece 1 = the internal entry number of the FILE 120.5 entry.  
   piece2 = Date/time of the reading (FileMan internal format).  
   piece3 = Patient DFN (FILE 2).  
   piece4 = Vital Type (FILE 120.51) value. Can be IEN or Abbreviation or 
            Full Name.  
   piece5 = Date/time the entry was created (FileMan internal format).  
   piece6 = Hospital Location internal entry number (FILE 44).  
   piece7 = FILE 200 value (i.e., DUZ) of the person who created the entry.  
   piece8 = Value of the reading. Can be numberic or alphanumeric.  
   piece9 = Entered-In-Error indicator. 1 (Yes) or null.  
   piece10 = FILE 200 value (i.e., DUZ) of the person who marked the record 
             as Entered-In-Error.  
   piece11 = Qualifier (FILE 120.52) values separated by a semi-colon (;).  
             Can be IEN or Abbreviation or Full Name of the qualifier.  
   piece12 = Entered-In-Error reasons separated by a semi-colon (;). Can 
             be IEN or Full Name of the reason.  
  
  
  The input parameters are in the following order: 
  
  D EN1(RESULT,GMVDFN,GMVFMT,GMVABR,GMVALL,GMVBEG,GMVEND,GMVMSYS,GMVEER) 
  
  
  Example of a successful return of data: 
  
  S RESULT="TEST" 
  D EN1^GMVDCEXT(RESULT,49,3,"^BP^PN^P^R^T^",1,3030901,"NOW","C",1) 
  
  ZW TEST 
   TEST(0)=OK 
   TEST(7317)=7317^3030918.111503^49^BLOOD PRESSURE^3030918.111653 
              ^87^547^130/70^^^L ARM;CUFF;SITTING;ADULT^^ 
   TEST(7319)=7319^3030918.111503^49^PAIN^3030918.111653^87^547^0^^^^^ 
   TEST(7320)=7320^3030918.111503^49^PULSE^3030918.111653^87^547^20^^^^^ 
   TEST(7321)=7321^3030918.111503^49^RESPIRATION^3030918.111653^87^547^50^^^ 
              ^^
   TEST(7322)=7322^3030918.111503^49^TEMPERATURE^3030918.111653^87^547^98.7^ 
              ^^^^
   TEST(7324)=7324^3030917.09^49^PAIN^3030918.111846^87^547^4^1^547^^ 
              INCORRECT READING^ 
   TEST(7325)=7325^3030915.08^49^BLOOD PRESSURE^3030918.115509 
              ^87^547^120/82^^^L ARM;CUFF;SITTING;ADULT^^ 
   TEST(7326)=7326^3030915.08^49^PAIN^3030918.115509^87^547^1^^^^^ 
   TEST(7327)=7327^3030915.08^49^PULSE^3030918.115509^87^547^25^^^SITTING; 
              LEFT^^ 
   TEST(7328)=7328^3030915.08^49^RESPIRATION^3030918.115509^87^547^35^^^ 
              SPONTANEOUS;SITTING^^ 
   TEST(7329)=7329^3030915.08^49^TEMPERATURE^3030918.115509^87^547^99^^^^^ 
  
  
  Example of failed return of data: 
  
  S RESULT="TEST" 
  D EN1^GMVDCEXT(RESULT,"FT",3,"^BP^PN^P^R^T^",1,3030901,"NOW","C",1) 
  
  ZW TEST 
   TEST(0)=ERROR 
   TEST(1)=ERROR: Missing or invalid Patient parameter 
VARIABLES: GMVDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   The patient's internal entry number (i.e., DFN) in
 FILE 2 (Required).  
VARIABLES: GMVFMT                       TYPE: Input
 VARIABLES DESCRIPTION:   A code to indicate how the data should be formatted
 for Vital Type, Qualifiers and Entered-In-Error Reasons (Optional).  
  
 1 means return internal entry number (IEN) of data (default).  
  
 2 means return abrreviation of data.  
  
 3 means return full name of data.  
VARIABLES: GMVABR                       TYPE: Input
 VARIABLES DESCRIPTION:   The abbreviations of the vital types to return
 separated by up-arrows (Optional).  
  
 For example, "^T^P^R^" will return Temperature, Pulse and Respiration.  
  
 If no value is entered, then all Vital Types are returned (i.e.,
 "^T^P^R^PO2^BP^HT^WT^CVP^CG^PN^").  
  
 Also, "~ALL~" will return all Vital Types (i.e., 
 "^T^P^R^PO2^BP^HT^WT^CVP^CG^PN^").  
VARIABLES: GMVALL                       TYPE: Input
 VARIABLES DESCRIPTION:   A code to indicate how much data is returned
 (Optional).  
  
 0 means return the most recent entry (Default).  
  
 1 means return all data in the date range specified.  
VARIABLES: GMVBEG                       TYPE: Input
 VARIABLES DESCRIPTION:   The date/time, in FileMan internal format, to begin
 the search. FileMan date/time values (e.g., NOW, T, T-7) can be used.  
  
 If GMVALL is 0, then this value is ignored.  
VARIABLES: GMVEND                       TYPE: Input
 VARIABLES DESCRIPTION:   The date/time, in FileMan internal format, to end the
 search. FileMan date/time values (e.g., NOW, T, T-7) can be used.  
  
 If GMVALL is 0, then this value is ignored.  
VARIABLES: GMVMSYS                      TYPE: Input
 VARIABLES DESCRIPTION:   A code to indicate what measurement system to use for
 the return values (Optional).  
  
 M means Metric.  
  
 C means US Customary (Default).  
VARIABLES: GMVEER                       TYPE: Input
 VARIABLES DESCRIPTION:   A code to indicate if entered-in-error values should
 be returned (Optional).  
  
 0 means No (Default).  
  
 1 means Yes.  
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
  ISC: Birmingham

NUMBER: 4252                            IA #: 4252
  FILE NUMBER: 50.416                   GLOBAL ROOT: DD(50.416
  DATE CREATED: AUG 31, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: SET LAYGO NODE IN FILE 50.416   ID: DD(50.416
 GENERAL DESCRIPTION:   National Drug File requests a one time integration
 agreement with VA FileMan to set the LAYGO node in DD(50.416) to prevent sites
 from making local additions to this national file.  Additions will only be
 made by data update patches.  
  
  STATUS: Active
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
  ISC: Birmingham

NUMBER: 4253                            IA #: 4253
  DATE CREATED: SEP 01, 2004
  CUSTODIAL PACKAGE: VISTA DATA EXTRACTION FRAMEWORK
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VDEFQM                       NAME: VDEF MESSAGE QUEUING
  ID: VDEFQM
 GENERAL DESCRIPTION:   This IA decribes the API used to request that a message
 be created and sent by the VDEF system.  It's successful use is dependent on
 entries made in the correct VDEF and HL7 files.  
  STATUS: Active
KEYWORDS: VDEF
KEYWORDS: MESSAGING
COMPONENT/ENTRY POINT: $$QUEUE(event_ID,name_value_pairs,[.text_message])
 COMPONENT DESCRIPTION:   This entry point places a request for the generation
 of an HL7 message into VDEF Request Queue (#579.3).  
VARIABLES: event_type                   TYPE: Input
 VARIABLES DESCRIPTION:   A string comprised of an HL7 message type and an HL7
 event type separated by a "^".  
  
 The value must be defined in the list of known VDEF message type/event type
 combinations in file 577.  
  
 Example:  "ADT^A28" 
VARIABLES: name_value_pairs             TYPE: Input
 VARIABLES DESCRIPTION:   A string comprised of the following format:
 SUBTYPE=<text>^IEN=nn where the Subtype text is a code based on the
 application's domain and the clinical event and the IEN is the IEN of the
 primary file associated with the event.  
  
 All Subtype names must be defined for this Message Type/Event Type in the VDEF
 EVENT DESCRIPTION file (#577). The name "SUBTYPE" is reserved for the purposes
 of uniquely identifying the request sub-type when more than one VDEF Event is
 defined for a Message Type/Event Type combination.  For example, the HL7
 message type/event ORU^R01 is used by multiple VistA domains to send
 unsolicited results.  In these cases, the Subtype is used to differentiate the
 sending domain's unique message contents within the structure of the ORU^R01.  
  
 Example: "SUBTYPE=VTLS^IEN=12345" 
VARIABLES: text_message                 TYPE: Both
 VARIABLES DESCRIPTION:   Acceptance or rejection text returned by the VDEF
 API.  
  
 Example:  "Invalid event type." 
VARIABLES: $$QUEUE                      TYPE: Output
 VARIABLES DESCRIPTION:   
  1 if the HL7 request was queued up for processing 
  0 if it was not queued up for processing 
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
 SUBSCRIBING DETAILS:   ADDED 10/9/2009 

NUMBER: 4254                            IA #: 4254
  DATE CREATED: MAR 06, 2007
  CUSTODIAL PACKAGE: VENDOR - AUDIOFAX, INC.
  USAGE: Private                        TYPE: Routine
  ROUTINE: TEST                         NAME: JULIE TESTING
  ID: TEST
 GENERAL DESCRIPTION:   TESTING 
  STATUS: Pending
COMPONENT/ENTRY POINT: TEST1(ONE,TWO,THREE)
VARIABLES: TWO                          TYPE: Input

NUMBER: 4255                            IA #: 4255
  DATE CREATED: OCT 28, 2003
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: CSL REFERENCING PARAMETERS
 GENERAL DESCRIPTION:   CSL created the following 5 parameter entries, which
 will be referenced by Event Capture usen parameter tools: 
   
      1. CSL CC UPDATE REQUEST   (store the query request date) 
      2. CSL CC UPDATE START     (store the table update start date) 
      3. CSL CC UPDATE END       (store the table update end date) 
      4. CSL CC UPDATE STATUS    (1: processing, 0: completed) 
      5. CSL CC UPDATE NOTE      (store status note) 
  STATUS: Active
KEYWORDS: CSL
SUBSCRIBING PACKAGE: EVENT CAPTURE

NUMBER: 4256                            IA #: 4256
  FILE NUMBER: 71.2                     GLOBAL ROOT: RAMIS(71.2,
  DATE CREATED: SEP 24, 2003            CUSTODIAL PACKAGE: VDEM
  USAGE: Private                        TYPE: File
  ROUTINE: VDEMPROC                     NAME: VDEMPROC Routine calling File 71.2
  ID: VDEMPROC
GLOBAL REFERENCE: RAMIS(71.2,IEN,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RAMIS(71.2,IEN,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: TYPE OF IMAGING
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA was created becuase of the routines dependancy
 with the Rad-Nuc file 71.2. The routine will loop through the file and extract
 data elements from key fields. The data will be used to support the VDEM
 extraction application.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: VDEM
KEYWORDS: VDEMPROC

NUMBER: 4257                            IA #: 4257
  DATE CREATED: MAR 08, 2007
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIULX
  NAME: Get *ALL* TIU Title IENS        ID: TIULX
 GENERAL DESCRIPTION:   The CPRS GUI Graphing Utility requires a list of ALL
 TIU TITLES.  This API facilitates Progress Note Graphing as it looks up TIU
 documents via TIU Titles.  
  
 This API does not make ANY checks on the Titles returned.                    
 Examples:                                                                 -
 They may (or may not) be active, 'NORMAL' Progress Note Titles.  
  
 - They could be of any status.  
  
 - They could be used only by a package uploading notes into TIU.  
  
 - They may or may not be in the Progess Notes Document Type Class, or even in
 the Clinical Documents Hierarchy.  
  
 - USR business rules may not permit various actions such as Entering notes on
 these Titles, Viewing them, or Printing them.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TITLES
KEYWORDS: 8925.1
KEYWORDS: TIU DOCUMENT DEFINITION FILE
COMPONENT/ENTRY POINT: TITLIENS
 COMPONENT DESCRIPTION:   This API orders through the 'AT' cross reference on
 the TIU DOCUMENT DEFINITION file and sets ALL Internal Entry Numbers for
 entries of type Title in global ^TMP("TIUTLS",$J,IEN).  The caller MUST kill 
 ^TMP("TIUTLS",$J) when finished with the data.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   The subscribing package must make all the necessary
 checks to make sure the notes it displays are appropriate.  
  DATE ACTIVATED: MAR 06, 2007

NUMBER: 4258                            IA #: 4258
  DATE CREATED: OCT 06, 2003            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXRMGECU                     NAME: PXRM CPRS CALLS FOR GEC
  ID: PXRMGECU
 GENERAL DESCRIPTION:   This DBIA will cover the GEC entry points use by CPRS
 in PXRMGECU: 
  
 API^PXRMGECU Evaluate what Visit the GEC Referral should be store with.  
  
 FINISHED^PXRMGECU Use to determine if a GEC Referral is completed.  
  
 $$STATUS^PXRMGECU Return text describing the status of a GEC Referral 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRMGECU
KEYWORDS: PXRM
KEYWORDS: GEC
KEYWORDS: ORQQPXRM
COMPONENT/ENTRY POINT: API(RESULT,IEN,DFN,VISIT,WHERE)
 COMPONENT DESCRIPTION:   This entry point will evaluate which GEC dialog is
 being evaluated in CPRS. This entry point will return data needed to associate
 a HF with a GEC Referral.  
VARIABLES: RESULT                       TYPE: Both
 VARIABLES DESCRIPTION:   Result is the returned string with several pieces: 
  
 TV^DT;GEC#^EVALUATION TEXT 
  
 TV is a truth-value, which tells CPRS if the dialog is a GEC dialog.  
  
 DT;GEC is the date and time use to associate the HF with a GEC referral and 
 the GEC is the dialog number.  
  
 EVALUATION TEXT is the text display to the users when processing the fourth 
 GEC dialog in CPRS 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN is the Reminder or the Reminder IEN.  
VARIABLES: DFN                          TYPE: Input
VARIABLES: VISIT                        TYPE: Input
 VARIABLES DESCRIPTION:   VISIT is the encounter information that is pass to
 reminder from CPRS 
VARIABLES: WHERE                        TYPE: Input
 VARIABLES DESCRIPTION:   WHERE is use to determine where this RPC is being
 called from. Currently a value of 1 mean that this API is being called from a
 Reminder Dialog and a value of 0 mean this API is not being called from a
 Reminder Dialog.  
COMPONENT/ENTRY POINT: FINISHED(DFN,ANS)
 COMPONENT DESCRIPTION:   This API is use to determine if the sever can close
 out the current GEC Referral.  
VARIABLES: DFN                          TYPE: Input
VARIABLES: ANS                          TYPE: Input
 VARIABLES DESCRIPTION:   ANS is a Boolean value.  
COMPONENT/ENTRY POINT: $$STATUS(DFN)
 COMPONENT DESCRIPTION:   This API will be used to return a status report of
 the current GEC Referral.  
VARIABLES: DFN                          TYPE: Input
VARIABLES: $$STATUS                     TYPE: Output
 VARIABLES DESCRIPTION:   Status will return a string that is evaluated by
 CPRS.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4259                            IA #: 4259
  DATE CREATED: SEP 25, 2003            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Remote Procedure                NAME: WOMEN VETERAN REPORT LOOKUP
 GENERAL DESCRIPTION:   This API will return the most recent unprocessed entry
 report text in the WV PROCEDURE FILE, file# 790.1 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: WV
KEYWORDS: PXRM
KEYWORDS: PXRM DIALOGS
KEYWORDS: WV/CPRS INTEGRATION
KEYWORDS: CPRS
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4260                            IA #: 4260
  DATE CREATED: JAN 13, 2004            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PRCAFLS3                     NAME: AR/CSL Application ACK process
  ID: PRCAFLS3
 GENERAL DESCRIPTION:   After process the acknowledgement from CoreFLS, CSL
 will pass the information to AR. 
  STATUS: Active
KEYWORDS: CSL
COMPONENT/ENTRY POINT: GETACK(TRANID,AC,.RCARY)
 COMPONENT DESCRIPTION:   Process CoreFLS acknowledgement.  
VARIABLES: TRANID                       TYPE: Input
 VARIABLES DESCRIPTION:   The receipt or bill Number (External) 
VARIABLES: AC                           TYPE: Input
 VARIABLES DESCRIPTION:   AC is the Acknowledgement Code for the receipt/bill.  
 AA = Accepted, AE or AR = Rejected.  
VARIABLES: RCARY                        TYPE: Both
 VARIABLES DESCRIPTION:   RCARY is the Error Array.  Subscripted by Line
 Number.  
    Piece 1 = Transmission IEN 
    Piece 2 = Error Code 
    Piece 3 = Error Description (Pieces 2 and 3 are repeating) 
SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   AR routine PRCAFLS3 called by CSL to pass
 acknowledgement information.  

NUMBER: 4261                            IA #: 4261
  DATE CREATED: SEP 26, 2003            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: PRCAFLS6
  NAME: AR/CSL Status Update Process    ID: PRCAFLS6
 GENERAL DESCRIPTION:   After process the Status Update from CoreFLS, CSL will
 pass the information back to AR.  
  STATUS: Withdrawn
KEYWORDS: CSL
COMPONENT/ENTRY POINT: STATUPD(RCEC,RCID,RCCODE,RCDC,RCGLID,RCJEH)
 COMPONENT DESCRIPTION:   Process CoreFLS status update.  
VARIABLES: RCEC                         TYPE: Input
 VARIABLES DESCRIPTION:   Event Code 
VARIABLES: RCID                         TYPE: Input
 VARIABLES DESCRIPTION:   ID Number (Receipt, Bill#) 
VARIABLES: RCCODE                       TYPE: Input
 VARIABLES DESCRIPTION:   CoreFLS Code 
VARIABLES: RCDC                         TYPE: Input
 VARIABLES DESCRIPTION:   CoreFLS Status Description 
VARIABLES: RCGLID                       TYPE: Input
 VARIABLES DESCRIPTION:   CoreFLS GL ID 
VARIABLES: RCJEH                        TYPE: Input
 VARIABLES DESCRIPTION:   CoreFLS JE Header 
VARIABLES: RCRESULT                     TYPE: Output
 VARIABLES DESCRIPTION:   Update Status Indicator 
   0 = Update Completed OK 
   1 = No ID Entry Found in VISTA AR 
   2 = Invalid Update Status Code 
   3 = Invalid Event Code 
SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   AR routine PRCAFLS6 called by CSL to pass status update
 information.  

NUMBER: 4262                            IA #: 4262
  DATE CREATED: SEP 29, 2003            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: HLUOPT2                      NAME: MESSAGE BODY DELETION
  ID: HLUOPT2
 GENERAL DESCRIPTION:   This integration covers the use of the DELBODY^HLUOPT2
 API.  This API deletes all segments of a VistA HL7 message except the MSH
 segment.  See patch HL*1.6*98 for additional explanation and information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DELBODY(IEN772,APP,STORE)
 COMPONENT DESCRIPTION:   All Health Level 7 (HL7) messages are composed of a
 MSH segment, and other optional segments.  The MSH segment is stored in the HL
 Message Administration file (#773), and the other segments are stored in the
 HL Message Text file (#772).  In addition to the MSH and other segments, these
 files hold other tracking and administrative data.  
  
 Some messages handled by the VistA HL7 package are extremely large, and 
 consume enough disk space as to cause storage problems. A new VistA HL7 
 application programmer interface (API) hass being released in patch HL*1.6*98
 to allow applications to selectively delete the "other optional segments" of a
 message. (The MSH segment is not deleted by this API.) 
  
 When this API is called the following actions occur: 
  
 (1) All segments other than the MSH segment are deleted.  (No data is 
     removed from the HL Message Administration file (#773).  Only data 
     stored in the ^HL(772,IEN,"IN") nodes is killed; all other 
     HL Message Text file (#772) file data is retained.) 
  
 (2) A record is created in the ^XTMP global of the deletion action.  
     The ^XTMP global data is stored for 7 days after which it is 
     deleted.  (More details are provided below.) 
  
 The API syntax is shown next: 
  
    D DELBODY^HLUOPT2(IEN772,APP,STORE) 
  
 The three parameters of the DELBODY API are explained below.  
  
 IEN772:    The internal entry number for the HL Message Text file (#772) 
            entry containing the "optional segments" to be deleted.  
  
            The passing of IEN772 is mandatory.  
  
 APP:       Free-text information passed to the DELBODY API by the 
            application identifying the calling process.  This information 
            is stored in the ^XTMP global as shown below.  
  
            APP free-text information may be passed as a null value, or 
            may be any free-text information up to 60 characters in 
            length.  (Up-arrows not allowed.) 
  
            The passing of APP is optional.  
  
 STORE:     Reference to data to be stored in the ^XTMP global.  The 
            reference must be in "closed reference" format , rather than 
            "open reference" format.  (Pass "TEXT" rather than "TEXT(", 
            and pass "^TMP($J)" instead of "^TMP($J,". Additional examples 
            are provided below.) 
  
 Example calls to the DELBODY API are provided next.  
  
    D DELBODY(51321523)                    ... APP and STORE not passed ...  
    D DELBODY(51321523,"MUSE EKG")         ... STORE not passed ...  
    D DELBODY(51321523,"","TEXT")          ... APP not passed ...  
    D DELBODY(51321523,"MUSE EKG","TEXT") 
    D DELBODY(51321523,"MUSE EKG","^TMP($J)") 
    D DELBODY(51321523,"MUSE EKG","^TMP($J,""INFO"")") 
  
 Here is an example entry in the HL Message Text file (#772) prior to calling
 the DELBODY API: 
  
 ^HL(772,5696,0) = 3020830.122552^32^^O^^9985696^^5696^D^269^^^DG^M 
 ^HL(772,5696,"IN",0) = ^^12^12^3020830^ ^HL(772,5696,"IN",1,0) =
 PID^^^100~10~M11^^JONES~JOHN~J^^ 19421112 
                          ^M^^^^^^^^^^123456789 ^HL(772,5696,"IN",2,0) = 
 ^HL(772,5696,"IN",3,0) = OBR^^^^7089898.8543-1~043091-66~L^^^19910 
                          4301200^"^"^^^^^"^^3232~HARRIS~JACK^^^^ME 
                          DICINE^^199104301010 ^HL(772,5696,"IN",4,0) = 
 ^HL(772,5696,"IN",5,0) = OBX^^TX^I~IMPRESSION~L^^HEART NORMAL SIZE 
 ^HL(772,5696,"IN",6,0) = ^HL(772,5696,"IN",7,0) = OBX^^ST^D~DIAGNOSTIC
 CODE~L^^NORMAL ^HL(772,5696,"IN",8,0) = ^HL(772,5696,"IN",9,0) =
 OBX^^TX^R~REPORT~L^^Heart appears to be o 
                          f normal size.  ^HL(772,5696,"IN",10,0) = 
 ^HL(772,5696,"IN",11,0) = OBX^^TX^R~REPORT~L^^No infiltrate or abn 
                           ormal mass noted.  ^HL(772,5696,"IN",12,0) = 
 ^HL(772,5696,"P") = 3^3020830.122553^^^^^600 ^HL(772,5696,"S") = 351^1 
  
 The data remaining in the HL Message Text file (#772) remaining after the call
 to DELBODY is shown below.  
  
 ^HL(772,5696,0) = 3020830.122552^32^^O^^9985696^^5696^D^269^^^DG^M 
 ^HL(772,5696,"P") = 3^3020830.122553^^^^^600 ^HL(772,5696,"S") = 351^1 
  
 When a call is made to the DELBODY API, the following information is stored in
 ^XTMP: 
  
  - Time when "optional segments" were deleted.  
  - Value of APP parameter.  
  - Number lines deleted.  
  - Information stored in @STORE parameter location.  
  - Value of XQY0, if it exists.  
  - Value of ZTSK, if it exists.  
  
 The ^XTMP data created when the DELBODY API is called is shown next.  The 
 initial subscript for the ^XTMP data is "HLUOPT2 "_DT.  If TODAY is 8/25/2002,
 the ^XTMP subscript is "HLUOPT2 3020825".  Here is how ^XTMP data is stored,
 using "HLUOPT2 3020825" as the subscript: 
  
   ^XTMP("HLUOPT2 3020825",0)=3020901^3020825.1238^HLUOPT2 
                              Message Body Deletion 
  
 The vaporization date for the ^XTMP data created on 8/25/2002 is "T+7" or 
 3020901 in FileMan format.  
  
 The value of "3020825.1238" is the FileMan-format date/time when the first
 deletion occurred for the data.  After creation, this date/time is never
 overwritten when subsequent deletions of "optional segments" occur.  
  
 The value of "HLUOPT2 Message Body Deletion" is always placed in piece 3 of
 the zero node above.  
  
 When the DELBODY API is called and the zero node above created, if not already
 created, additional information is stored in two additional ^XTMP global
 locations.  But, before this can be done a "storage occurrence number" must be
 calculated.  This number is just a sequential number; 1 the first time a call
 is made to DELBODY, 2 the next time, etc.  
  
 Assuming that the "storage occurrence number" calculated by the DELBODY API is
 23, the following data is created: 
  
   ^XTMP("HLUOPT2 3020825",23,0)=3020825.1532^MUSE EKG^25321^MUSE EKG 
                                 OPTION^1391341 
  
 In the above example, the pieces of data are sequentially: 
  
  - 3020825.1532 = Time when message body was deleted.  
  - MUSE EKG = Value passed in APP parameter.  
  - 25321 = Number lines of "optional segment" data removed.  
  - MUSE EKG OPTION = Value of XQY0 at time of call to DELBODY.  
  - 1391341 = Task number (i.e., ZTSK) of process calling DELBODY.  
  
 In addition to the above information stored in ^XTMP, the data stored in the
 STORE storage location is also stored as shown next.  In this example, let's
 assume that the local TEXT array exists and has the following entries: 
  
   TEXT(1)="This entry was just marked successfully completed." 
   TEXT(2)="Therefore, it's message body is no longer needed." 
   TEXT(3)="Since this message is extremely large, it's message" 
   TEXT(7)="body will be deleted." 
  
 In this case, the TEXT array data will be stored in the ^XTMP global as shown
 below.  
  
   ^XTMP("HLUOPT2 3020825",23,"S",1)="This entry was just marked 
                                     successfully completed." 
   ^XTMP("HLUOPT2 3020825",23,"S",2)="Therefore, it's message body is no 
                                     longer needed." 
   ^XTMP("HLUOPT2 3020825",23,"S",3)="Since this message is extremely 
                                     large, it's message" 
   ^XTMP("HLUOPT2 3020825",23,"S",7)="body will be deleted." 
  
 It is strongly recommended that the DELBODY API only be called after all 
 related messages (i.e., initial message and all related acknowledgement 
 messages) are successfully completed.  
VARIABLES: IEN772                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN772 is the first parameter for the
 DELBODY^HLUOPT2(IEN772,APP,STORE) API, and it is the internal entry number of
 an entry in the HL Message Text file (#772.)  Passing this parameter is
 mandatory.  Full explanation and examples is provided in this agreement's
 component description above.  
VARIABLES: APP                          TYPE: Input
 VARIABLES DESCRIPTION:   Free-text information stored with ^XTMP data at the
 time of message body deletion.  Passing this parameter (and the STORE
 parameter) is optional.  If passed, it can be null and any value up to 60
 characters.  APP may not contain any up-arrows.  Full explanation and examples
 is provided in this agreement's component description above.  
VARIABLES: STORE                        TYPE: Input
 VARIABLES DESCRIPTION:   Global reference to the data to be stored in the
 ^XTMP data.  The passing of this parameter is optional.  Full explanation and
 examples is provided in this agreement's component description above.  

NUMBER: 4263                            IA #: 4263
  DATE CREATED: AUG 23, 2004
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Other                           NAME: VDEF EVENTS AND EXTRACTION LISTS
 GENERAL DESCRIPTION:   The following VDEF events are under the custody of
 ADVERSE REACTION TRACKING: 
  ADT^A60 
  
 The folllowing VDEF extraction lists are under the custody of ADVERSE REACTION
 TRACKING: 
  
  PID-0-PTALG 
  IAM-0-PTALG 
  IAM-5-PTALG-S-REACTS 
  ROL-0-PTALG-ALORG 
  ROL-0-PTALG-ALVER 
  ROL-0-PTALG-ALERR 
  ROL-0-PTALG-S-ALCHM 
  NTE-0-PTALG-S-CMTS 
  NTE-3-PTALG-S-CMTS-S-CMTS 
  ROL-0-PTALG-S-CMTS 
  Z01-0-PTALG 
  Z01-13-PTALG-S-DI 
  Z01-14-PTALG-S-DC 
  Z03-0-PTALG-S-REACTS 
  Z03-2-PTALG-S-REACTS 
  XXX-0-PTALG-RESET-COUNTER 
  STATUS: Retired

NUMBER: 4264                            IA #: 4264
  DATE CREATED: NOV 04, 2003            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSJXRFS
  NAME: PDM ACCESS TO PSJXRFS           ID: PSJXRFS
 GENERAL DESCRIPTION:   Pharmacy Data Management has requested permission to
 store Inpatient Medications cross-reference set routine PSJXRFS in the Data
 Dictionary for a new cross-reference. The new cross reference will create an
 index to the to the PHARMACY PATIENT file (#55) at both the UNIT DOSE multiple
 (#62) and the IV multiple (#100).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PDM
KEYWORDS: PSJ
KEYWORDS: CLINICAL REMINDERS
COMPONENT/ENTRY POINT: SPSA(X,DA,NODE)
 COMPONENT DESCRIPTION:   SPSPA(X,DA,NODE) X(1)=START DATE/TIME X(2)=STOP
 DATE/TIM DA=PATIENT IEN NODE="IV" or "UD" 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X(1)=START DATE/TIME X(2)=STOP DATE/TIME 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   DA=PATIENT IEN 
VARIABLES: NODE                         TYPE: Input
 VARIABLES DESCRIPTION:   The possible values for NODE are "IV" and "UD".  
COMPONENT/ENTRY POINT: SPSA(.X,DA,NODE)
COMPONENT/ENTRY POINT: SPSPA(.X,DA,NODE)
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT

NUMBER: 4265                            IA #: 4265
  DATE CREATED: NOV 04, 2003            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSJXRFK
  NAME: PDM ACCESS TO PSJXRFK           ID: PSJXRFK
 GENERAL DESCRIPTION:   Pharmacy Data Management has requested permission to
 store Inpatient Medications cross-reference kill routine PSJXRFK in the Data
 Dictionary for a new cross-reference. The new cross reference will create an
 index to the to the PHARMACY PATIENT file (#55) at both the UNIT DOSE multiple 
 (#62) and the IV multiple (#100).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: PSJXRFK
COMPONENT/ENTRY POINT: KPSPA(.X,DA,NODE)
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X(1)=START DATE/TIME X(2)=STOP DATE/TIME 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   DA=PATIENT IEN 
VARIABLES: NODE                         TYPE: Input
 VARIABLES DESCRIPTION:   The possible values for NODE are "IV" and "UD".  
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT

NUMBER: 4266                            IA #: 4266
  DATE CREATED: SEP 07, 2004
  CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DVBCMKLK                     NAME: AMIE 2507 Request APIs
  ID: DVBCMKLK
 GENERAL DESCRIPTION:   These APIs are used to obtain 2507 Request information,
 and to create a link between an Appointment and a 2507 Request.  
  
 Refer to the Components for more information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$GET2507(DFN,ADT)
 COMPONENT DESCRIPTION:   Retrieve a 2507 request.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN (Required) 
VARIABLES: ADT                          TYPE: Input
 VARIABLES DESCRIPTION:   Appointment Date Time (Required, FM format) 
VARIABLES: $$GET2507                    TYPE: Output
 VARIABLES DESCRIPTION:   Output: 
       IEN (of 2507 request if found) 
       zero (if Not Found) 
   - or - 
       ERR_CODE^ERR_MESSAGE (ERR_CODE is negative) 
         Calling App responsible for display of ERR_MESSAGE 
  
COMPONENT/ENTRY POINT: $$LINK(DFN,PC,ADT)
 COMPONENT DESCRIPTION:   Link C&P appointment to 2507 request 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN (Required) 
VARIABLES: PC                           TYPE: Input
 VARIABLES DESCRIPTION:   Prompt Control (Default: 0, Prompt only if necessary) 
VARIABLES: ADT                          TYPE: Input
 VARIABLES DESCRIPTION:   Appointment Date Time (FM format) 
     Default: 3rd piece of SDATA if set, else NOW 
VARIABLES: $$LINK                       TYPE: Output
 VARIABLES DESCRIPTION:   Output: 
       IEN (of 2507 request) 
   - or - 
       ERR_CODE^ERR_MESSAGE (ERR_CODE is negative) 
         Calling App responsible for display of ERR_MESSAGE 
  
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 4267                            IA #: 4267
  DATE CREATED: AUG 23, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Other                           NAME: VDEF EVENTS AND EXTRACTION LISTS
 GENERAL DESCRIPTION:   The following VDEF events are under the custody of
 REGISTRATION: 
  
  ADT^A28^PAT 
  ADT^A28^PTF 
  
 The following VDEF extraction lists are under the custody REGISTRATION: 
  
  PID-0-PATIENT-APICALL 
  PV1-0-PATIENT 
  ZSP-0-PATIENT-APICALL 
  ZEL-0-PATIENT-APICALL 
  ZEM-0-PATIENT-APICALL 
  PID-0-PTF 
  PV1-0-PTF 
  PV1-6-PTF 
  PV2-0-PTF 
  Z09-0-PTF 
  Z09-3-PTF 
  ROL-0-PTF-S-CC 
  OBX-0-PTF-SVCCNCT 
  OBX-0-PTF-AGENTORA 
  OBX-0-PTF-RADEXP 
  OBX-0-PTF-ENVCONT 
  OBX-0-PTF-MST 
  OBX-0-PTF-HNCA 
  OBX-0-PTF-SSIIND 
  OBX-0-PTF-LEGDIS 
  OBX-0-PTF-SUBSTAB 
  OBX-0-PTF-PCSEV 
  OBX-0-PTF-CURRFA 
  OBX-0-PTF-HLPC 
  DG1-0-PTF-DXLS 
  DG1-0-PTF-ICD2-ICD10 
  DRG-0-PTF-DRG 
  PR1-0-PTF-S-401 
  Z07-0-PTF-S-401 
  PR1-0-PTF-S-601 
  Z07-0-PTF-S-601 
  Z08-0-PTF-S-501 
  Z08-3-PTF-S-501 
  ROL-0-PTF-S-501 
  OBX-0-PTF-S-501-SVCCNCT 
  OBX-0-PTF-S-501-AGENTORA 
  OBX-0-PTF-S-501-RADEXP 
  OBX-0-PTF-S-501-ENVCONT 
  OBX-0-PTF-S-501-MST 
  OBX-0-PTF-S-501-HNCA 
  OBX-0-PTF-S-501-SSIIND 
  OBX-0-PTF-S-501-LEGDIS 
  OBX-0-PTF-S-501-SUBSTAB 
  OBX-0-PTF-S-501-PCSEV 
  OBX-0-PTF-S-501-CURRFA 
  OBX-0-PTF-S-501-HLPC 
  DG1-0-PTF-S-501-ICD1 
  DG1-0-PTF-S-501-ICD2 
  DG1-0-PTF-S-501-ICD3 
  DG1-0-PTF-S-501-ICD4 
  DG1-0-PTF-S-501-ICD5 
  DG1-0-PTF-S-501-ICD6 
  DG1-0-PTF-S-501-ICD7 
  DG1-0-PTF-S-501-ICD8 
  DG1-0-PTF-S-501-ICD9 
  DG1-0-PTF-S-501-ICD10 
  DRG-0-PTF-S-501 
  Z10-0-PTF-S-CY 
  XXX-0-PTF-RESET-COUNTER 
  PV1-0-PTMOVE 
  PV1-3-PTMOVE-POC 
  PV1-3-PTMOVE-POC-1 
  PV1-3-PTMOVE-POC-2 
  PV1-3-PTMOVE-ROOM 
  PV1-3-PTMOVE-BED 
  PV2-0-PTMOVE 
  Z11-0-PTMOVE 
  Z11-4-PTMOVE 
  Z11-5-PTMOVE 
  Z11-7-PTMOVE 
  Z11-9-PTMOVE 
  STATUS: Retired

NUMBER: 4268                            IA #: 4268
  DATE CREATED: AUG 23, 2004
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Supported                      TYPE: Other
  NAME: VDEF EVENTS AND EXTRACTION LISTS
 GENERAL DESCRIPTION:   The following VDEF events are under the custody of PCE
 PATIENT CARE ENCOUNTER: 
  
  ADT^A28^ENC 
  VXU^V04^HFCT 
  VXU^V04^IMMU 
  VXU^V04^SKIN 
  
 The following VDEF extraction lists are under the custody of PCE PATIENT CARE
 ENCOUNTER: 
  
  PID-0-VISIT 
  PV1-0-VISIT 
  PV1-3-VISIT 
  PV1-19-VISIT-IEN 
  PV1-19-VISIT-ID 
  PV1-39-VISIT 
  PV1-50-VISIT 
  PV2-0-VISIT 
  ROL-0-VPROV 
  ROL-3-VPROV-PS 
  ROL-3-VPROV-OA 
  ROL-9-VPROV-PC-1-1 
  ROL-9-VPROV-PC-1-2 
  ROL-9-VPROV-PC-2-1 
  ROL-9-VPROV-PC-2-2 
  ROL-9-VPROV-PC-3-1 
  ROL-9-VPROV-PC-3-2 
  NTE-0-VPROV 
  OBX-0-VISIT-SVCCNCT 
  OBX-0-VISIT-AGENTORA 
  OBX-0-VISIT-RADEXP 
  OBX-0-VISIT-PGEXP 
  OBX-0-VISIT-MST 
  OBX-0-VISIT-HNCA 
  NTE-0-VISIT 
  PR1-0-VCPT 
  PR1-3-VCPT 
  PR1-15-VCPT 
  PR1-16-VCPT 
  Z12-0-VCPT 
  Z12-1-VCPT 
  Z12-2-VCPT 
  ROL-0-VCPT-OP 
  ROL-0-VCPT-EP 
  NTE-0-VCPT 
  PR1-0-VEXAM 
  ROL-0-VEXAM-OP 
  ROL-0-VEXAM-EP 
  OBX-0-VEXAM 
  NTE-0-VEXAM 
  PRB-0-VPOV 
  PRB-10-VPOV-PN 
  PRB-10-VPOV-CT 
  ROL-0-VPOV-OP 
  ROL-0-VPOV-EP 
  OBX-0-VPOV-SVCCNCT 
  OBX-0-VPOV-AGENTORA 
  OBX-0-VPOV-RADEXP 
  OBX-0-VPOV-PGEXP 
  NTE-0-VPOV 
  PID-0-HF 
  PV1-0-HF 
  ORC-0-HF 
  RXA-0-HF 
  OBX-0-HF 
  NTE-0-HF 
  PID-0-IMMU 
  PV1-0-IMMU 
  PV1-3-IMMU-VISIT-1 
  PV1-3-IMMU-VISIT-2 
  ORC-0-IMMU 
  RXA-0-IMMU 
  OBX-0-IMMU 
  NTE-0-IMMU 
  NTE-0-IMMU-S-REM 
  PID-0-SKIN 
  PV1-0-SKIN 
  PV1-3-SKIN-VISIT-1 
  PV1-3-SKIN-VISIT-2 
  ORC-0-SKIN 
  RXA-0-SKIN 
  OBX-0-SKIN 
  NTE-0-SKIN 
  STATUS: Retired

NUMBER: 4269                            IA #: 4269
  DATE CREATED: AUG 23, 2004            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Other                           NAME: VDEF  VDEF EXTRACTION LISTS
 GENERAL DESCRIPTION:   The following VDEF extraction lists are under the
 custody of HEALTH LEVEL SEVEN: 
  
  MSH-0 
  EVN-0 
  STATUS: Retired

NUMBER: 4270                            IA #: 4270
  DATE CREATED: AUG 23, 2004
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Other                           NAME: VDEF EVENTS AND EXTRACTION LISTS
 GENERAL DESCRIPTION:   The following VDEF events are under the custody of TEXT
 INTEGRATION UTILITIES: 
  
  MDM^T02 
  
 The following VDEF extraction lists are under the custody of TEXT INTEGRATION
 UTILITIES: 
  
  PID-0-TIU 
  PV1-0-TIU 
  TXA-0-TIU 
  TXA-2-TIU 
  Z41-0-TIU 
  Z41-0-TIU-EXTLINK 
  OBX-0-TIU-S-REPTXT 
  STATUS: Retired

NUMBER: 4271                            IA #: 4271
  FILE NUMBER: 771.2                    DATE CREATED: AUG 31, 2004
  CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: HL7 MESSAGE TYPE ACCESS
GLOBAL REFERENCE: HL(771.2,
FIELD NUMBER: .01                       FIELD NAME: ABBREVIATED NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   This IA allows the VDEF package to point-to and lookup
 entries in file #771.2.  This access is used to verify that VDEF Extract
 Descriptions are based on existing HL7 Message Types.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VDEF
KEYWORDS: MESSAGE TYPE
SUBSCRIBING PACKAGE: VISTA DATA EXTRACTION FRAMEWORK
  ISC: Oakland

NUMBER: 4272                            IA #: 4272
  DATE CREATED: AUG 23, 2004            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Other                           NAME: VDEF EVENTS AND EXTRACTION LISTS
 GENERAL DESCRIPTION:   The following VDEF events are under the custody of LAB
 SERVICE: 
  
  ORU^R01^CHEM 
  ORU^R01^MICB 
  ORU^R01^ELMC 
  ORU^R01^PATH 
  ORU^R01^CYTO 
  ORU^R01^AUTP 
  
 The following VDEF extraction lists are under the custody of LAB SERVICE: 
  
  PID-0-LABCH 
  XXX-0-LABCH-APICALL 
  PID-0-LABMI 
  XXX-0-LABMI-APICALL 
  PID-0-LABEM 
  XXX-0-LABEM-APICALL 
  PID-0-LABSP 
  XXX-0-LABSP-APICALL 
  PID-0-LABCY 
  XXX-0-LABCY-APICALL 
  PID-0-LABAU 
  OBR-0-LABAU 
  OBX-0-LABAU-AUTINFO 
  OBX-0-LABAU-DEATH 
  OBX-5-LABAU-DEATH-TREATSPEC 
  OBX-0-LABAU-HEIGHT 
  OBX-0-LABAU-WEIGHT 
  OBX-0-LABAU-LUNGRT 
  OBX-0-LABAU-LUNGLT 
  OBX-0-LABAU-LIVER 
  OBX-0-LABAU-SPLEEN 
  OBX-0-LABAU-KIDNEYRT 
  OBX-0-LABAU-KIDNEYLT 
  OBX-0-LABAU-HEART 
  OBX-0-LABAU-BRAIN 
  OBX-0-LABAU-PGLAND 
  OBX-0-LABAU-TGLAND 
  OBX-0-LABAU-PARATHLTUP 
  OBX-0-LABAU-PARATHLTLO 
  OBX-0-LABAU-PARATHRTUP 
  OBX-0-LABAU-PARATHRTLO 
  OBX-0-LABAU-ADRENLT 
  OBX-0-LABAU-ADRENRT 
  OBX-0-LABAU-PANCREAS 
  OBX-0-LABAU-TESTISLT 
  OBX-0-LABAU-TESTISRT 
  OBX-0-LABAU-OVARYLT 
  OBX-0-LABAU-OVARYRT 
  OBX-0-LABAU-TVALVE 
  OBX-0-LABAU-PVALVE 
  OBX-0-LABAU-MVALVE 
  OBX-0-LABAU-AVALVE 
  OBX-0-LABAU-RVENT 
  OBX-0-LABAU-LVENT 
  OBX-0-LABAU-PLEURCAVLT 
  OBX-0-LABAU-PLEURCAVRT 
  OBX-0-LABAU-PCARDCAV 
  OBX-0-LABAU-PTONECAV 
  OBX-0-LABAU-ORGAN-S-OT 
  OBX-0-LABAU-ORGAN-S-OT-S-IG 
  OBX-0-LABAU-ORGAN-S-OT-S-IM 
  OBX-0-LABAU-ORGAN-S-ICD9 
  NTE-0-LABAU-ORGAN-S-CMTS 
  NTE-0-LABAU-ORGAN-S-CLINDX 
  NTE-0-LABAU-ORGAN-S-PATHDX 
  OBX-0-LABAU-ORGAN-S-ASR 
  NTE-0-LABAU-ORGAN-S-ASR-S-DESC 
  STATUS: Retired

NUMBER: 4273                            IA #: 4273
  DATE CREATED: AUG 23, 2004
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Other                           NAME: VDEF EVENTS AND EXTRACTION LISTS
 GENERAL DESCRIPTION:   The following VDEF events are under the custoday of
 GEN. MED. REC. - VITALS: 
  
  ORU^R01^VTLS 
  
 The following VDEF extraction list are under the custoday of GEN. MED. REC. -
 VITALS: 
  
  PID-0-VITAL 
  OBR-0-VITAL 
  OBX-0-VITALNAME 
  OBX-15-VITALNAME 
  OBX-0-VITALINFO 
  OBX-15-VITALINFO 
  OBX-0-VITALERR 
  OBX-0-VITALQUAL 
  OBX-17-VITALQUAL-1 
  OBX-17-VITALQUAL-2 
  STATUS: Retired

NUMBER: 4274                            IA #: 4274
  DATE CREATED: AUG 23, 2004            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Other                           NAME: VDEF EVENTS AND EXTRACTION LISTS
 GENERAL DESCRIPTION:   The following VDEF events are under the custody of
 KERNEL: 
  
  PMU^B01 
  PMU^B02 
  
 The following VDEF extraction lists are under the custody of KERNEL: 
  
  STF-0-NP 
  STF-2-NP-PN 
  STF-2-NP-SS 
  STF-3-NP 
  PRA-0-NP 
  PRA-3-NP-S-RNMC 
  PRA-6-NP-SW 
  PRA-6-NP-DEA 
  PRA-6-NP-VA 
  ORG-0-NP-S-PC 
  ORG-6-NP-S-PC-1 
  ORG-6-NP-S-PC-2 
  ORG-7-NP-S-PC-1 
  ORG-7-NP-S-PC-2 
  ORG-8-NP-S-PC-1 
  ORG-8-NP-S-PC-2 
  STATUS: Retired

NUMBER: 4275                            IA #: 4275
  DATE CREATED: AUG 23, 2004            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Other                           NAME: VDEF EVENTS AND EXTRACTION LISTS
 GENERAL DESCRIPTION:   The following VDEF events are under the custody of
 OUTPATIENT PHARMACY: 
  
  RDE^O11^PRES 
  RDS^O13^PPAR 
  RDS^O13^PREF 
  
 The following VDEF extraction lists are under the custoday of OUTPATIENT
 PHARMACY: 
  
  PID-0-PRES 
  PV1-0-PRES 
  PV2-0-PRES 
  ORC-0-PRES 
  RXE-0-PRES 
  RXE-2-PRES-1 
  RXE-2-PRES-2 
  RXE-21-PRES-S-PI 
  RXR-0-PRES-S-MR 
  OBX-0-PRES-SVCCNCT 
  OBX-0-PRES-MST 
  OBX-0-PRES-AGENTORA 
  OBX-0-PRES-RADEXP 
  OBX-0-PRES-ENVCONT 
  OBX-0-PRES-HNCA 
  NTE-0-PRES-RE 
  NTE-0-PRES-S-SIG1 
  NTE-3-PRES-S-SIG1 
  NTE-0-PRES-S-PC 
  NTE-3-PRES-S-PC 
  NTE-0-PRES-PAT 
  NTE-0-PRES-S-PAT2 
  NTE-3-PRES-S-PAT2 
  Z14-0-PRES 
  Z14-1-PRES 
  Z14-11-PRES-S-SCHEDS 
  Z15-0-PRES-S-REFILL 
  Z16-0-PRES-S-PARTIAL 
  Z17-0-PRES-S-MEDINSTRS 
  Z18-0-PRES-S-LOTEXP 
  STATUS: Retired

NUMBER: 4276                            IA #: 4276
  DATE CREATED: AUG 23, 2004            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Other                           NAME: VDEF EVENTS AND EXTRACTION LISTS
 GENERAL DESCRIPTION:   The following VDEF events are under the custody of
 MENTAL HEALTH: 
  
  PPR^PC1^MTLH 
  
 The following VDEF extraction lists are under the custody of MENTAL HEALTH: 
  
  PID-0-MTLH 
  PRB-0-MTLH 
  PRB-3-MTLH 
  ROL-0-MTLH-DB 
  ROL-0-MTLH-TRANS 
  OBX-0-MTLH-S-MODS 
  OBX-0-MTLH-PS 
  OBX-0-MTLH-S-COMMENT 
  STATUS: Retired

NUMBER: 4277                            IA #: 4277
  DATE CREATED: AUG 23, 2004            CUSTODIAL PACKAGE: PROBLEM LIST
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Other                           NAME: VDEF EVENTS AND EXTRACTION LISTS
 GENERAL DESCRIPTION:   The following VDEF events are under the custody of
 PROBLEM LIST: 
  
  PPR^PC1^PROB 
  
 The following VDEF extraction lists are under the custody of PROBLEM LIST: 
  
  PID-0-PROB 
  PV1-0-PROB 
  PV1-3-PROB-POC 
  PV1-3-PROB-FACILITY 
  PRB-0-PROB 
  ROL-0-PROB-EB 
  ROL-0-PROB-RECPR 
  ROL-0-PROB-RESPR 
  OBX-0-PROB-SVCCNCT 
  OBX-0-PROB-AGENTORA 
  OBX-0-PROB-RADEXP 
  OBX-0-PROB-PGEXP 
  OBX-0-PROB-HNCA 
  OBX-0-PROB-MST 
  OBX-0-PROB-PN 
  OBX-0-PROB-S-NF 
  OBX-5-PROB-FACILITY 
  OBX-0-PROB-S-NF-S-NOTE-NMBR 
  OBX-0-PROB-S-NF-S-NOTE-NARR 
  XXX-0-PROB-RESET-COUNTER 
  STATUS: Retired

NUMBER: 4278                            IA #: 4278
  DATE CREATED: AUG 23, 2004
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Other                           NAME: VDEF EVENTS AND EXTRACTION LISTS
 GENERAL DESCRIPTION:   The following VDEF events are under the custody of
 RADIOLOGY/NUCLEAR MEDICINE: 
  
  ORU^R01^RAD 
  
 The following VDEF extraction lists are under the custody of RADIOLOGY/NUCLEAR
 MEDICINE: 
  
  PID-0-RAD 
  PV1-0-RAD 
  PV1-3-RAD-POC-WARD 
  PV1-3-RAD-POC-WARD-1 
  PV1-3-RAD-POC-WARD-2 
  PV1-3-RAD-POC-PC 
  PV1-3-RAD-HOSPDIV-FT 
  OBR-0-RAD-PTCASE 
  OBR-4-RAD-PTCASE 
  OBR-16-RAD-POC-REQLOC 
  OBR-33-RAD-PTCASE-PRIMINTRES 
  OBR-33-RAD-PTCASE-PRIMINTSTF 
  OBR-33-RAD-PTCASE-S-SECINTSTF 
  OBR-33-RAD-PTCASE-S-SECINTRES 
  OBR-34-RAD-PTCASE-S-TECH 
  OBR-0-RAD-RNMR 
  OBX-0-RAD-PTCASE-PDC 
  OBX-0-RAD-PTCASE-S-SDC 
  OBX-0-RAD-PTCASE-S-CH 
  OBX-0-RAD-PTCASE-CMPL 
  OBX-0-RAD-PTCASE-CT 
  OBX-0-RAD-PTCASE-S-PM 
  OBX-0-RAD-PTCASE-S-CPT 
  OBX-0-RAD-PTCASE-S-MEDS 
  OBX-5-RAD-MEDADMIN-1 
  OBX-5-RAD-MEDADMIN-2 
  OBX-5-RAD-MEDADMIN-3 
  OBX-0-RAD-RNMR-S-RT 
  OBX-0-RAD-RNMR-S-IT 
  OBX-0-RAD-RNMR-S-ER 
  OBX-0-RAD-RNMR-S-ER-S-ET 
  OBX-0-RAD-RNMR-RT-IL 
  OBX-0-RAD-RNMR-S-OC 
  OBX-0-RAD-RNMR-S-IMG 
  OBX-0-RAD-RNMR-S-ACH 
  OBX-0-RAD-PTCASE-CM 
  Z42-0-RAD-NMD-CONTRAST 
  Z42-0-RAD-NMD-S-RADIOPHARM 
  Z42-1-RAD-NMD-S-RADIOPHARM-1 
  Z42-1-RAD-NMD-S-RADIOPHARM-2 
  Z42-1-RAD-NMD-S-RADIOPHARM-3 
  STATUS: Retired

NUMBER: 4279                            IA #: 4279
  DATE CREATED: AUG 23, 2004            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Washington             USAGE: Supported
  TYPE: Other                           NAME: VDEF EVENTS AND EXTRACTION LISTS
 GENERAL DESCRIPTION:   The following VDEF events are under the custody BAR
 CODE MED ADMIN: 
  
  RDS^O13^BCMA 
  
 The following VDEF extraction lists are under the custody of BARE CODE MED
 ADMIN: 
  
  PID-0-BCMA 
  PV1-0-BCMA 
  ORC-0-BCMA 
  RXE-0-BCMA 
  RXE-2-BCMA 
  RXC-0-BCMA-BASE 
  RXC-0-BCMA-ADD 
  RXG-0-BCMA 
  RXG-2-BCMA 
  RXG-4-BCMA-EDIT 
  RXG-3-BCMA 
  OBX-0-BCMA-PRNREASON 
  OBX-2-BCMA-EFFECTIVENESS 
  OBX-3-BCMA-ENTERED 
  OBX-4-BCMA-ENTEREDAT 
  OBX-5-BCMA-MINUTES 
  OBX-6-BCMA-DIVISION 
  OBX-7-BCMA-ACTION 
  OBX-8-BCMA-VARIANCE 
  NTE-0-BCMA 
  Z25-0-BCMA 
  STATUS: Retired

NUMBER: 4280                            IA #: 4280
  FILE NUMBER: 21                       GLOBAL ROOT: DIC(21,
  DATE CREATED: MAY 27, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DIC(21                          ID: DIC(21,
GLOBAL REFERENCE: DIC(21,
FIELD NUMBER: .03                       FIELD NAME: CODE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Includes direct access to the "D" x-ref.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas

NUMBER: 4281                            IA #: 4281
  GLOBAL ROOT: DD(                      DATE CREATED: DEC 14, 2010
  CUSTODIAL PACKAGE: 1                  USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Field selection/lookup based on DD global with call to DIC
  ID: DD(
GLOBAL REFERENCE: DD(60,D0)
 GENERAL DESCRIPTION:   The LAB SERVICE package (LSRP project) has a
 requirement for the user to be able to select specific fields in the
 LABORATORY TEST (#60) file and to set auditing on and off for these fields. 
 In order for the users to select the fields available for a file, a DIC call
 would be used with the variable DIC set to "^DD(".  This ICR will allow the
 LAB SERVICE package to use ^DD in this manner.  
  
          S DIC="^DD(60," 
          S DIC(0)="AEQMZ",DIC("A")="Field: " 
          D ^DIC 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: DEC 15, 2010

NUMBER: 4282                            IA #: 4282
  FILE NUMBER: 71.2                     GLOBAL ROOT: RAMIS(71.2
  DATE CREATED: OCT 06, 2003
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  NAME: PROCEDURE CODE                  ID: RAMIS(71.2
 GENERAL DESCRIPTION:   The VDEM package requests permission to view the Name
 field and the Type of Imaging pointer of the Procedure Modifiers file (71.2)
 to extract the data from the database.  
  STATUS: Withdrawn
KEYWORDS: VDEM
SUBSCRIBING PACKAGE: VDEM

NUMBER: 4283                            IA #: 4283
  DATE CREATED: OCT 23, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB DEVICE                      REMOTE PROCEDURE: PSB DEVICE
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSB DEVICE
KEYWORDS: BCMA
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN
  ISC: Birmingham

NUMBER: 4284                            IA #: 4284
  DATE CREATED: OCT 23, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB NURS WARDLIST               REMOTE PROCEDURE: PSB NURS WARDLIST
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSB NURS WARDLIST
KEYWORDS: BCMA
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN
  ISC: Birmingham

NUMBER: 4285                            IA #: 4285
  DATE CREATED: OCT 23, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB CHECK IV                    REMOTE PROCEDURE: PSB CHECK IV
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSB CHECK IV
KEYWORDS: BCMA
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN
  ISC: Birmingham

NUMBER: 4286                            IA #: 4286
  FILE NUMBER: 64                       GLOBAL ROOT: LAM(
  DATE CREATED: OCT 09, 2003            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: VDEMWKLD Routine Calling File 64
  ID: LAM(
GLOBAL REFERENCE: LAM(IEN,0)
FIELD NUMBER: .01                       FIELD NAME: PROCEDURE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: WKLD CODE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: BILLABLE PROCEDURE 
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   Direct Global Read from the VDEM application 
GLOBAL REFERENCE: LAM(IEN,3)
FIELD NUMBER: .04                       FIELD NAME: PRINT NAME
  LOCATION: 3;1                         ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   Direct Global Read from the VDEM to extract the print
 name.  
GLOBAL REFERENCE: LAM(IEN,5,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SPECIMEN
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LAM(IEN,5,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: TIME ASPECT
  LOCATION: O;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LAM(IEN,5,D1,1,D2,1)
FIELD NUMBER: 4                         FIELD NAME: LOINC CODE
  LOCATION: 1;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA was created becuase of the routines dependancy
 with the WKLD Code file #64. The routine will loop through the file and 
 extract data elements of key fields. The data will be used to support the VDEM
 extraction application.  
  STATUS: Withdrawn
KEYWORDS: VDEM
KEYWORDS: VDEMWKLD
KEYWORDS: WKLD CODE

NUMBER: 4287                            IA #: 4287
  DATE CREATED: OCT 20, 2003
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORB3LAB                      NAME: ORB3LAB ROUTINE
  ID: ORB3LAB
 GENERAL DESCRIPTION:   CPRS requests that the Lab package will notify CPRS
 (the OR package) whenever lab test results are released for a Cytology,
 Surgical Pathology, Electron Microscopy, and Autopsy section.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CYTOLOGY RESULTS
KEYWORDS: SURGICAL PATHOLOGY RESULTS
KEYWORDS: ANATOMIC PATHOLOGY ALERT
KEYWORDS: AUTOPSY RESULTS
COMPONENT/ENTRY POINT: LAB
 COMPONENT DESCRIPTION:   The Lab package will call this entry point when the
 results for an Autopsy, Cytology, Surgical Pathology, and Electron Microscopy
 test are released.  
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, Surgical Pathology, and Electron Microscopy. For
 Autopsy, LRI will contain the Autopsy Date/Time in Fileman format.  
VARIABLES: LRA                          TYPE: Input
 VARIABLES DESCRIPTION:   The zero node of a Cytology, Surgical Pathology,or
 Electron Microscopy entry in the LAB DATA file [#63]. For Autopsy, LRA will
 contain the "AU" node.  
VARIABLES: LRSS                         TYPE: Input
 VARIABLES DESCRIPTION:   Two letter value that identifies the type of lab
 test.  For example: CY = Cytology, SP = Surgical Pathology, EM = Electron
 Microscopy, & AU = Autopsy.  
VARIABLES: XQA                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an array of alert recipients that is passed
 by reference.  It contains the DUZs of the recipients as subscripts.  
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
  DATE ACTIVATED: MAR 14, 2008

NUMBER: 4288                            IA #: 4288
  DATE CREATED: OCT 22, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: IBCNRDV                      NAME: RETRIEVE INSURANCE DATA
  ID: IBCNRDV
 GENERAL DESCRIPTION:   Register Once Messaging will initiate a %ZTLOAD call to 
 BACKGND^IBCNRDV to retrieve insurance data from sites of record each time a
 veteran is registered at a new site for the first time. 
  
 IB*2.0*763 adds a switch to enable/disable retrieval of insurance data.  
 DG*5.3*1102 checks the status of the switch. (See ICR 7429) 
  STATUS: Active
KEYWORDS: REGISTER ONCE
KEYWORDS: INSURANCE QUERY
KEYWORDS: DGREG
KEYWORDS: DGROAPI
KEYWORDS: REMOTE INSURANCE QUERY
COMPONENT/ENTRY POINT: BACKGND
VARIABLES: IBTYPE                       TYPE: Input
 VARIABLES DESCRIPTION:   = 1   Indicates a background process 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's DFN at the requesting site.  
VARIABLES: IBDUZ                        TYPE: Input
 VARIABLES DESCRIPTION:   The requesting user's DUZ.  
VARIABLES: Insurance Buffer             TYPE: Output
 VARIABLES DESCRIPTION:   Data is returned in the INSURANCE BUFFER file 355.33. 
 
SUBSCRIBING PACKAGE: REGISTRATION
  DATE ACTIVATED: JUL 17, 2023

NUMBER: 4289                            IA #: 4289
  DATE CREATED: OCT 30, 2003            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCAHV
  NAME: PRCAHV                          ID: PRCAHV
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCAHV
COMPONENT/ENTRY POINT: $$BALANCE(.RESULT,PRCAICN,PRCATY)
VARIABLES: PRCAICN                      TYPE: Input
 VARIABLES DESCRIPTION:   Patient's ICN (required) 
VARIABLES: PRCATY                       TYPE: Input
 VARIABLES DESCRIPTION:   Account Receivable Transaction Types, possible values
 (case insensitive): 
  "OPEN" (default) the same as "113,112,102,107" - open/active Trans .  
  
 Types -   "ALL", all Transaction Types ;    <list of Trans.Type numbers, comma
 delimited> 
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULT (by reference)=<balance value> or zero if
 error/no data 
VARIABLES: $$BALANCE                    TYPE: Output
 VARIABLES DESCRIPTION:   1-success, 0-no data, '-1'-error, '-2'-patient
 doesn't exist, '-3'- program error 
COMPONENT/ENTRY POINT: $$INTDTL(.RESULT,DFN,PRCATY)
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULT(1..n)=<Bill No>^<Date Bill
 Prepared(FM)>^<Description>^ <Balance>^<Status Number> 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's DFN (required) 
VARIABLES: PRCATY                       TYPE: Input
 VARIABLES DESCRIPTION:   PRCATY - Account Receivable Transaction Types,
 possible values: 
          ;    "OPEN" (default) the same as "113,112,102,107" - open/active
 Trans. Types 
          ;    "ALL", all Transaction Types 
          ;    <list of Trans.Type numbers, comma delimited> 
VARIABLES: $$INTDTL                     TYPE: Output
 VARIABLES DESCRIPTION:   1-success, 0-no data, '-1'-error '-2'-patient doesn't
 exist 
COMPONENT/ENTRY POINT: $$INTTRANS(.RESULT,RCBILL)
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   
 RESULT(i)=<Trans.No>^<Date(FM)>^<Trans.Type>^<reserved>^<Trans. amo  
          unt>^<Descr1>^<Descr2>^<Descr3>^<Descr4>^<Descr5> 
VARIABLES: RCBILL                       TYPE: Input
 VARIABLES DESCRIPTION:   Bill IEN (required) 
VARIABLES: $$INTTRANS                   TYPE: Output
 VARIABLES DESCRIPTION:   1-success, 0-no data, '-1'-no parameter '-2'-the bill
 doesn't exist, '-3'-program error 
SUBSCRIBING PACKAGE: MYHEALTHEVET
 SUBSCRIBING DETAILS:   Used to get and display copayment data 
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

NUMBER: 4290                            IA #: 4290
  GLOBAL ROOT: PXRMINDX(                DATE CREATED: DEC 08, 2005
  CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: READ OF CLINICAL REMINDER INDEX (PXRMINDX)
  ID: PXRMINDX(
GLOBAL REFERENCE: PXRMINDX(55,
 GLOBAL DESCRIPTION:   The index is on file 55, Pharmacy Patient. The structure
 is: 
  
  ^PXRMINDX(55,"IP",DRUG,DFN,START.STOP,DAS) 
  ^PXRMINDX(55,"PI",DFN,DRUG,START,STOP,DAS) where DRUG is a pointer to Drug
 file, START is the starting date, and STOP is the stop date. The API to
 retrieve the associated data is OEL^PSJPXRM1(DAS,.DATA). It is documented in
 DBIA 3836.  
GLOBAL REFERENCE: PXRMINDX(52,
 GLOBAL DESCRIPTION:   The index is on file 52, Prescription file. The
 structure is: 
  
  ^PXRMINDX(52,"IP",DRUG,DFN,START,STOP,DAS) 
  ^PXRMINDX(52,"PI",DFN,DRUG,START,STOP,DAS) 
  
 where DRUG is a pointer to Drug file, START is the starting date (RELEASE 
 DATE) and STOP is the stop date ( RELEASE DATE +  DAYS SUPPLY). The API to 
 retrieve the associated data is PSRX^PSOPXRM1(DAS,"ARRAY"). It is documented
 in DBIA 3793.  
GLOBAL REFERENCE: PXRMINDX(100,
 GLOBAL DESCRIPTION:   The index is on file 100, Order file. The structure is: 
  
  ^PXRMINDX(100,"IP",OI,DFN,START,STOP,DAS) 
  ^PXRMINDX(100,"PI",DFN,OI,START,STOP,DAS) where OI is a pointer to the
 Orderable Items file, START is the START DATE, and STOP is the STOP DATE. The
 API to retrieve the associated data is EN^ORX8(DA).  Note that DA is the first
 piece of DAS and the data is returned in the array ORUPCHK. The API is
 documented in DBIA 871.  
  
GLOBAL REFERENCE: PXRMINDX(63,
 GLOBAL DESCRIPTION:   The index is on file 63, Lab Data. The structure is: 
  
 Chemistry, Hematology, other Lab Tests 
  ^PXRMINDX(63,"IP",ITEM,DFN,DATE,DAS) 
  ^PXRMINDX(63,"PI",DFN,ITEM,DATE,DAS) 
  
 Microbiology and Anatomic Path data have an additional index 
  
 ^PXRMINDX(63,"PDI",DFN,DATE,ITEM,DAS) 
  
 where DATE is the Date/Time of collection. The structure of ITEM depends on 
 the type of lab data. 
  
 For Chemistry, Hematology, and other lab tests, ITEM is numeric and a pointer
 to the Laboratory Test file. 
  
 For Microbiology, ITEM is of the format "M;[S T O A M];#". where the middle
 section can be one of: 
  
 S is specimen (# is a pointer to the Topography [SNOMED] file) T is test (# is
 a pointer to the Laboratory Test file) O is organism (# is a pointer to the
 Etiology Field [SNOMED] file) A is antibiotic (# is a pointer to the
 Antimicrobial Susceptibility file) M is a TB drug (# is the field number of
 the TB drug - ^DD(63.39,). 
  
 For Anatomic Pathology, ITEM is of the format "A;[S T O D M E F P I];#".  
 where the middle section can be one of: 
  
 S is specimen (# is 1.free text value) T is test (# is a pointer to the
 Laboratory Test file) O is organ/tissue (# is a pointer to the Topography
 [SNOMED] file) D is disease (# is a pointer to Disease Field [SNOMED] file) M
 is morphology (# is a pointer to the Morphology Field [SNOMED] file) E is
 etiology (# is a pointer to the Etiology Field [SNOMED] file) F is function (#
 is a pointer to the Function [SNOMED] file P is procedure (# is a pointer to
 the Procedure [SNOMED] file) I is ICD9 (# is a pointer to the ICD DIAGNOSIS
 file) 
  
 Microbiology and Anatomic Pathology data are stored in a complex hierarchy. 
 The ITEM is therefore a compound expression. This allows single elements of 
 data to be easily found. The DAS also depends on the type of lab data. A 
 chemistry test result has four semicolon pieces. Microbiology and Anatomic 
 Pathology can be more complex and have a much more nested structure. The API
 to retrieve the associated data is LRPXRM^LRPXAPI(.DATA,DAS,ITEM). This 
 information should be reviewed in the context of other data associated with 
 the specimen. The API is documented in DBIA #? The Lab package has other APIs
 that use these indexes.  
GLOBAL REFERENCE: PXRMINDX(601.2,
 GLOBAL DESCRIPTION:   The index is on file 601.2, Psych Instrument Patient.
 The structure is: 
  
  ^PXRMINDX(601.2,"IP",INS,DFN,DATE,DAS) 
  ^PXRMINDX(601.2,"PI",DFN,INS,DATE,DAS) 
  
 where INS is a pointer to the MH Instrument file. The API to retrieve the 
 associated data is ENDAS^YTAPI10(.YSDATA,DAS). The API is documented in DBIA
 #4442 
GLOBAL REFERENCE: PXRMINDX(120.5,
 GLOBAL DESCRIPTION:   The index is on file 120.5, GMV Vital Measurement. The
 structure is: 
  
 ^PXRMINDX(120.5, IP ,VITAL TYPE,DFN,DATE,DAS) ^PXRMINDX(120.5, PI ,DFN,VITAL
 TYPE,DATE,DAS) 
  
 where VITAL TYPE is a pointer to the GMV Vital Type file. Entries that are
 marked as "entered-in-error  are not indexed. The API to retrieve the
 associated data is EN^GMVPXRM(.GMVDATA,DAS).  
  
 The API is documented in DBIA 3647.  
  
GLOBAL REFERENCE: PXRMINDX(9000010.13,
 GLOBAL DESCRIPTION:   The structure of the index is: 
  
     ^PXRMINDX(9000010.13,"IP",ITEM,DFN,DATE,DAS) 
     ^PXRMINDX(9000010.13,"PI",DFN,ITEM,DATE,DAS) 
  
 where item is the .01 of the Exam file, and DATE is the Visit Date.  
  
 The API to retrieve the associated date is VXAM^PXPXRM(DAS,.DATA).  The API is
 documented in DBIA 4250.  
  
GLOBAL REFERENCE: PXRMINDX(9000010.23,
 GLOBAL DESCRIPTION:   The structure of the index is: 
  
     ^PXRMINDX(9000010.23,"IP",ITEM,DFN,DATE,DAS) 
     ^PXRMINDX(9000010.23,"PI",DFN,ITEM,DATE,DAS) 
  
 where item is the .01 of the Health Factor file, and DATE is the Visit Date.  
  
 The APIs to retrieve the associated date is VHF^PXPXRM(DAS,.DATA).  The API is
 documented in DBIA 4250.  
  
GLOBAL REFERENCE: PXRMINDX(9000010.11,
 GLOBAL DESCRIPTION:   The structure of the index is: 
     ^PXRMINDX(9000010.11,"IP",ITEM,DFN,DATE,DAS) 
     ^PXRMINDX(9000010.11,"PI",DFN,ITEM,DATE,DAS) 
     ^PXRMINDX(9000010.11,"CVX","IP",CVX_CODE,DFN,DATE,DAS) 
     ^PXRMINDX(9000010.11,"CVX","PI",DFN,CVX_CODE,DATE,DAS) 
  
 where item is the .01 of the Immunization file, and DATE is the Event Date and
 Time. If Event Date and Time is not populated, the Visit Date/Time will be
 used instead.  
  
 The API to retrieve the associated date are is VIMM^PXPXRM(DAS,.DATA).  The
 API is documented in DBIA 4250.  
GLOBAL REFERENCE: PXRMINDX(9000010.16,
 GLOBAL DESCRIPTION:   The structure of the index is: 
     ^PXRMINDX(9000010.16,"IP",ITEM,DFN,DATE,DAS) 
     ^PXRMINDX(9000010.16,"PI",DFN,ITEM,DATE,DAS) 
  
 where item is the .01 of the Education Topics file, and DATE is the Visit
 Date.  
  
 The API to retrieve the associated date are is VPEDU^PXPXRM(DAS,.  DATA). The
 API is documented in DBIA 4250.  
  
GLOBAL REFERENCE: PXRMINDX(9000010.12,
 GLOBAL DESCRIPTION:   The structure of the index is: 
  
     ^PXRMINDX(9000010.12,"IP",ITEM,DFN,DATE,DAS) 
     ^PXRMINDX(9000010.12,"PI",DFN,ITEM,DATE,DAS) 
  
 where item is the .01 of the Skin Test file, and DATE is the Visit Date.  
  
 The API to retrieve the associated date are is VSKIN^PXPXRM(DAS,.  DATA). The
 API is documented in DBIA 4250.  
  
GLOBAL REFERENCE: PXRMINDX(9000010.18,
 GLOBAL DESCRIPTION:   The structure of the index is: 
     ^PXRMINDX(9000010.18,"IP "IPP",CODE,TYPE,DFN,DATE,DAS) 
     ^PXRMINDX(9000010.18,"PI" "PPI",DFN,TYPE,CODE,DATE,DAS) 
  
 where code is a pointer to the CPT code, TYPE is the primary procedure. DATE
 is the Visit Date.  
  
 The API to retrieve the associated date are is VCPT^PXPXRM(DAS,.DATA ). The
 API is documented in DBIA 4250.  
  
GLOBAL REFERENCE: PXRMINDX(9000010.07,
 GLOBAL DESCRIPTION:   The structure of the index is: 
     ^PXRMINDX(9000010.07,"IP "IPP",CODE,TYPE,DFN,DATE,DAS) 
     ^PXRMINDX(9000010.07,"PI" "PPI",DFN,TYPE,CODE,DATE,DAS) 
  
 where code is a pointer to the ICD9 code, TYPE is the primary/ secondary value
 from the V POV file entry. DATE is the Visit Date.  
  
 The API to retrieve the associated date are is VPOVT^PXPXRM(DAS,.DATA).  The
 API is documented in DBIA 4250.  
GLOBAL REFERENCE: PXRMINDX(45,
 GLOBAL DESCRIPTION:   The index is on file 45, PTF. Because PTF stores both
 ICD 0 and ICD 9 codes, the index is structured to accommodate this.  
  
 ^PXRMINDX(45, ICD0 , INP ,ICD0,DFN,DATE,NODE,DAS) ^PXRMINDX(45, ICD0 , PNI
 ,DFN,IDC0,DATE,NODE,DAS) ^PXRMINDX(45, ICD9 , INP ,ICD9,DFN,DATE,NODE,DAS) 
 ^PXRMINDX(45, ICD9 , PNI ,DFN,IDC9,DATE,NODE,DAS) 
  
 where ICD0 is a pointer to the ICD Operation/Procedure file and ICD9 is a
 pointer to the ICD Diagnosis file. Because ICD 0 codes are stored at 10
 different locations, five on the surgery node and five on the procedure node
 and ICD 9 codes are stored at 25 different locations, 10 on the discharge
 node, 5 on node 71, and 10 on the movement node, the storage node information
 is stored in the index. This allows quick retrieval from specific nodes. For
 example, one of the ICD 9 codes is stored as DXLS, so in this case the string
 "DXLS  is the node subscript. Some of the ICD 9 storage nodes have names like
 secondary diagnosis 1, secondary diagnosis 2 etc, the corresponding nodes
 would be D SD1, D SD1. Movement storage nodes have names like "M ICD2 . The
 API to retrieve the associated data is PTF^DGPXRM(DAS,.DATA).  
  
 Note that for some of the cross-references in PTF, TYPE OF RECORD is included
 in the list of fields. It is used to exclude entries whose TYPE OF RECORD is
 CENSUS from the index.  
  
 The API is documented in DBIA #3817.  
  
GLOBAL REFERENCE: PXRMINDX(601.84,
 GLOBAL DESCRIPTION:   The index is on file 601.84, MH Administrations. The
 structure is: 
  
 ^PXRMINDX(601.84,"IP",INS,DFN,DATE,DAS) 
 ^PXRMINDX(601.84,"PI",DFN,INS,DATE,DAS) 
  
 where INS is a pointer to the MH Tests and Surveys file. The API to retrieve
 the associated data is ENDAS71^YTQPXRM6(.YSDATA,DAS). The API is documented in
 DBIA 5043.  
  
GLOBAL REFERENCE: PXRMINDX(9000010.707,
 GLOBAL DESCRIPTION:   The structure of the index is: 
     ^PXRMINDX(9000010.707,"PIC",DFN,IMM,CONTRA/REFUSAL,START,STOP,DAS) 
     ^PXRMINDX(9000010.707,"PCI",DFN,CONTRA/REFUSAL,IMM,START,STOP,DAS) 
     ^PXRMINDX(9000010.707,"ICP",IMM,CONTRA/REFUSAL,DFN,START,STOP,DAS) 
     ^PXRMINDX(9000010.707,"CIP",CONTRA/REFUSAL,IMM,DFN,START,STOP,DAS) 
        
 where IMM is a pointer to the IMMUNIZATION file; CONTRA/REFUSAL is a variable
 pointer to the IMM CONTRAINDICATION REASONS (#920.4) or IMM REFUSAL REASONS
 (#920.5) files; START is the Event Date and Time, or if Event Date and Time is
 not populated, the Visit Date/Time will be used instead; STOP is the Warn
 Until Date, or if Warn Until Date is not populated, 9999999 will be used
 instead.  
        
 The API to retrieve the associated data is VICR^PXPXRM(DAS,.DATA).  The API is
 documented in DBIA 4250.  
 GENERAL DESCRIPTION:   This DBIA will allow any packages with the DBA approval
 to be able to read from 
  the Clinical Reminders index.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: CLINICAL REMINDERS INDEX
KEYWORDS: PXRM
KEYWORDS: PXRMINDX
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS
 SUBSCRIBING DETAILS:   ADDED 4/23/09 
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
 SUBSCRIBING DETAILS:   ADDED 3/3/2010 
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   added 8/24/2010 
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Effective with VPR*1*0.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application. If HMP
 is reactivated in the future, the HMP project team should review the access
 provided by this ICR with the custodial application before reactivating HMP's
 subscription to this ICR.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 8/2/2022, effective with DSSV*1.1 DSS Class 3
 product Document Only 
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Added 8/22/2025, effective with PSJ*5*461 The Methadone 
 Dispensing Tracking Project will have to make reference to the CLINICAL
 REMINDERS data { PXRMINDX(9000010.23, } in order to determine the associated
 Health Factor status on file for reporting to the state Prescription Drug
 Monitoring Program (PDMP).  
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 7/27/26. effective with patch CDSP*1.0*4, to 
 access to PXRMINDX(9000010.23) patient V Health Factors and
 PXRMINDX(9000010.16) patient V Education 
  DATE ACTIVATED: SEP 19, 2016

NUMBER: 4291                            IA #: 4291
  DATE CREATED: NOV 04, 2003
  CUSTODIAL PACKAGE: INCOME VERIFICATION MATCH
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IVMCQ
  NAME: DG10 REFERENCE                  ID: IVMCQ
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DG10
COMPONENT/ENTRY POINT: REG(DFN)
 COMPONENT DESCRIPTION:   AUTO TO HEC FOR UPDATED FINANCIAL INFORMATION.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   PATIENT'S IEN.  
  
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4292                            IA #: 4292
  DATE CREATED: NOV 06, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VAFHLZPD                     NAME: DBIA4292
  ID: VAFHLZPD
 GENERAL DESCRIPTION:   Supported calls for building of HL7 ZPD segment (VA
 Specific Patient Demographics).  
  STATUS: Active
KEYWORDS: ZPD
COMPONENT/ENTRY POINT: $$EN(DFN,VAFSTR)
 COMPONENT DESCRIPTION:   This generic extrinsic function was designed to
 return sequences 1 throught 21 of the HL7 ZPD segment.  This segment contains
 VA-specific patient information that is not contained in the HL7 PID segment. 
 This call does not accomodate a segment length greater than 245 and has been 
 superceeded by EN1^VAFHLZPD. This line tag has been left for backwards 
 compatability.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to PATIENT file (#2) 
VARIABLES: VAFSTR                       TYPE: Input
 VARIABLES DESCRIPTION:   String of fields requested seperated by commas
 (Defaults to all fields) 
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 ZPD segment 
COMPONENT/ENTRY POINT: $$EN1(DFN,VAFSTR)
 COMPONENT DESCRIPTION:   This generic extrinsic function was designed to
 return the HL7 ZPD segment.  This segment contains VA-specific patient
 information that is not contained in the HL7 PID segment.  This call
 superceeds EN^VAFHLZPD because it accomodates a segment length greater than
 245.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to PATIENT file (#2) 
VARIABLES: VAFSTR                       TYPE: Input
 VARIABLES DESCRIPTION:   String of fields requested seperated by commas
 (Defaults to all fields) 
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 ZPD segment.  If the ZPD
 segment becomes longer than 245 characters, remaining fields will be placed in
 VAFZPD(1).  

NUMBER: 4293                            IA #: 4293
  FILE NUMBER: 5                        GLOBAL ROOT: DIC(5
  DATE CREATED: NOV 06, 2003            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Update DIC(5,'%D'               ID: DIC(5
GLOBAL REFERENCE: DIC(5,"%D",
 GLOBAL DESCRIPTION:   File DESCRIPTION.  
 GENERAL DESCRIPTION:   Update the file DESCRIPTION for the STATE(#5) file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland
 SUBSCRIBING DETAILS:   To avoid the need to send out the entire DD to update
 the DESCRIPTION of the STTE(#5) file the following is a one time code used in
 routine: XU8P328 to update the DESCRIPTION: 
  
 XU8P328 ;OIFOO/SO- POST INSTALL;8:35 AM  6 Nov 2003 
         ;;8.0;KERNEL;**328**;Jul 10, 1995 
         ;
 DES     D MES^XPDUTL("Updating STATE(#5) file's Description.") 
         K ^DIC(5,"%D") 
         S ^DIC(5,"%D",0)="^^5^5^3031105^" 
         S ^DIC(5,"%D",1,0)="This file contains the name of the state (or 
 outlying area) as issued" 
         S ^DIC(5,"%D",2,0)="by the Department of Veterans Affairs and issued
 in M-1, Part I," 
         S ^DIC(5,"%D",3,0)="Appendix B.  These entries should remain as 
 distributed and should not be" 
         S ^DIC(5,"%D",4,0)="edited or updated unless done via a software 
 upgrade or under direction" 
         S ^DIC(5,"%D",5,0)="of VA Central Office." 

NUMBER: 4294                            IA #: 4294
  DATE CREATED: NOV 13, 2003
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MPIFA40
  NAME: $$A40 MPIFA40                   ID: MPIFA40
 GENERAL DESCRIPTION:   This is the entry point used to tell the MPI that two
 records at a local site hasve been merged and that they both had National ICNs
 that should know be under one ICN.  It will build an A40 Merge Patient HL7
 message.  
  STATUS: Active
COMPONENT/ENTRY POINT: A40
 COMPONENT DESCRIPTION:   This API will return the message ID returned from the
 HL7 GENERATE^HLMA call if successful OR -1^error message if unsuccessful.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN - Internal Entry Number from the Patient (#2)
 file that will remain after the merge process has completed.  
VARIABLES: DFN2                         TYPE: Input
 VARIABLES DESCRIPTION:   DFN2 - Internal Entry Number from the Patient (#2)
 file that will no longer exist (FROM record) after the merge process has
 completed.  
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
 SUBSCRIBING DETAILS:   This API is being called via the special processing
 routine during a duplicate record merge process.  

NUMBER: 4295                            IA #: 4295
  FILE NUMBER: 9999999.64               GLOBAL ROOT: AUTTHF(
  DATE CREATED: FEB 23, 2004
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: HEALTH FACTORS INFO             ID: AUTTHF(
GLOBAL REFERENCE: AUTTHF('AC',
 GLOBAL DESCRIPTION:   This is a cross-reference of Health Factors belonging to
 a specific Health Factor Category.  
GLOBAL REFERENCE: AUTTHF(D0,0)
FIELD NUMBER: .01                       FIELD NAME: FACTOR
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the name of the Health Factor (e.g., Current
 Smoker, Non-Tobacco User, etc) 
FIELD NUMBER: .03                       FIELD NAME: CATEGORY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the Health Factor that categorizes several
 factors into one group.  For instance, Non smoker and Frequent Smoker would
 have the category of Tobacco.  
FIELD NUMBER: .1                        FIELD NAME: ENTRY TYPE
  LOCATION: 0;10                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the type of health factor, (e.g.,"F" for factor 
 or "C" for category).  
FIELD NUMBER: .08                       FIELD NAME: DISPLAY ON HEALTH SUMMARY
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This agreement is to access basic information about a 
 Health Factor, and the necessary cross-references to access them by Category.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMTSPXFP
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Health Summary needs to use the AUTTF("AC"
 cross-reference to access Health Factors by category for the Selected Health
 Factors Component (SHF).  It also needs to retrieve the FACTOR (.01), CATEGORY
 (.03) and ENTRY TYPE (.1) fields using Fileman.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 10/1/19, effective with YS*5.01*135.  

NUMBER: 4296                            IA #: 4296
  DATE CREATED: NOV 18, 2003
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: CSLPRVQ
  NAME: DBIA4296                        ID: CSLPRVQ
 GENERAL DESCRIPTION:   Silently (i.e. without user interaction) receive input
 from a calling program for building a vendor query.  The input would be in a
 structured local array as in CLSIN shown below.  CSLPRVQ* would use the input
 to build an HL7 message, obtain the Message Control ID (MID), and send the 
 message to the CoreFLS database.  When the results of the query were returned
 by HL7, CSLPRVQ* would build an ^XTMP(SUB) global with that data.  SUB equals
 the string "CSLPRVQ" concatenated with the MID (ex. "CSLPRVQ516124898").  
  
 The expected structure of the input array (CSLIN) is as follows: 
  
         CSLIN(2.1) - VENDOR NAME 
         CSLIN(2.2) - TAX ID 
         CSLIN(2.3) - CITY 
         CSLIN(2.4) - STATE 
         CSLIN(2.5) - VENDOR SITE 
         CSLIN(2.6) - VENDOR ID 
         CSLIN(2.7) - AREA CODE 
         CSLIN(2.8) - PHONE NO 
         CSLIN(3.1) - ADDRESS 1 
         CSLIN(3.2) - ADDRESS 2 
         CSLIN(3.3) - ADDRESS 3 
         CSLIN(4) - ZIP 
         CSLIN(5) - CHAIN NO 
  
 Note that if any of the above nodes are not defined or are set to NULL then
 those fields will not be used in composing the query.  The data in every field
 that is defined will have the "%" wildcard appended to it.  For example, if
 CSLIN(2.1)="MED" then the value "MED%" will be used in building the query.  
  
 An example of the structure of the output array (^XTMP(SUB)) appears below,
 where SUB is as described above and N holds the information for the Nth result
 returned from CoreFLS: 
  
         ^XTMP(SUB,N,"ADDRESS1")=2010 59TH ST W   STE 4700 
         ^XTMP(SUB,N,"ATTRIBUTES",1,"CODE")=4 
         ^XTMP(SUB,N,"ATTRIBUTES",1,"DESCRIPTION")=PURCHASING SITE 
         ^XTMP(SUB,N,"ATTRIBUTES",2,"CODE")=5 
         ^XTMP(SUB,N,"ATTRIBUTES",2,"DESCRIPTION")=PAY-TO-SITE 
         ^XTMP(SUB,N,"CITY")=BRADENTON 
         ^XTMP(SUB,N,"COUNTRY")=US 
         ^XTMP(SUB,N,"COUNTY")= 
         ^XTMP(SUB,N,"INACTIVE")=3031010.24 
         ^XTMP(SUB,N,"LAST_UPDATED")=3010917.10344 
         ^XTMP(SUB,N,"NAME")=MED ARTS REHAB INC 
         ^XTMP(SUB,N,"NUMBER")= 
         ^XTMP(SUB,N,"SITE_CODE")=BRADENTON-FL-00 
         ^XTMP(SUB,N,"STATE")=FL 
         ^XTMP(SUB,N,"TAXID")=592199074 
         ^XTMP(SUB,N,"ZIP")=342094687 
  
 Note that each subscript shown above will be defined in the output array even
 if that node contains no data (as in ^XTMP(SUB,N,"COUNTY") above).  The first
 50 results of the query will be returned in the ^XTMP(SUB) global.  Because
 ^XTMP is used to hold the query results, the results would be deletable after
 7 days.  
  
 The entry point for the silent vendor query: >W $$CSVQ^CSLPRVQ(.CSLIN) where
 CSLIN is an array structured as shown above.  If the query runs successfully,
 the return value will look like "^CSLPRVQ516124898".  If the query encounters
 an error condition, the return value will look like "3^Not Found", with a
 positive number in the first "^"-peice and a short descriptive message of the
 error in the second "^"-peice.  The different possible errors along with
 comments are shown below.  
  
  
  
 CSLPRVQ* would return the ^XTMP subscript SUB as described above to the 
 calling application in the format "^SUB".  If the first "^"-piece is nonzero
 then an error occurred and the second "^"-piece will contain an error message. 
  
 The list below shows the error messages that could be returned along with 
 comments.  Note that these error messages, unless specified in the comments to
 the right, will appear as the return value for the routine call described
 above.  
  
 Invalid input parameter list            HL7 error - the input message 
                                         string sent to CoreFLS was invalid 
  
 Query aborted due to error:             HL7 error when initializing HL7 
                                         parameters 
  
 Message send failure:                   HL7 error when transmitting 
                                         message to CoreFLS 
  
 Network Timeout                         the query request to CoreFLS 
                                         timed or the check for results 
                                         in ^XTMP timed out 
  
 Not Found                               no results obtained for query in 
                                         CoreFLS 
  
 104^wrong segment name                  HL7 errors when processing 
 201^application error                   incoming response from 202^application
 reject                  CoreFLS - these will appear in 401^missing segments    
                nodes ^XTMP(SUB,"ERR"), 402^ERR segment received               
 ^XTMP(SUB,"ETEXT"), and 403^wrong segment name (expected QAK)  
 ^XTMP(SUB,"ENUMBER").  404^missing segments 407^RDT segments expected 
 408^wrong segment name (RDT expected) 500^Can't find entry in ITEM QUERY file 
 999^unknown error wrong number of columns 900                                  
   a general error occurred. this 
                                         will also be in ^XTMP(SUB) 
  STATUS: Withdrawn
KEYWORDS: CSLPRVQ
KEYWORDS: SILENT QUERY
COMPONENT/ENTRY POINT: CSVQ
 COMPONENT DESCRIPTION:   >W $$CSVQ^CSLPRVQ(.CSLIN) 
  
 see Description for explanation 
SUBSCRIBING PACKAGE: PROSTHETICS

NUMBER: 4297                            IA #: 4297
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: DEC 23, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: ELECTRONIC SIGNATURE-RELATED DATA IN THE NEW PERSON FILE
  ID: VA(200,
GLOBAL REFERENCE: VA(200,
FIELD NUMBER: .132                      FIELD NAME: OFFICE PHONE
  LOCATION: .13;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .137                      FIELD NAME: VOICE PAGER
  LOCATION: .13;7                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .138                      FIELD NAME: DIGITAL PAGER
  LOCATION: .13;8                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: INITIAL
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20.2                      FIELD NAME: SIGNATURE BLOCK PRINTED NAME
  LOCATION: 20;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20.3                      FIELD NAME: SIGNATURE BLOCK TITLE
  LOCATION: 20;3                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20.4                      FIELD NAME: ELECTRONIC SIGNATURE CODE
  LOCATION: 20;4                        ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Electronic Signature is a collection of Java APIs to
 validate, retrieve, and save electronic signature codes and related data on
 the M server, as well as APIs to encrypt and decrypt strings similar to the
 APIs provided by the existing VA Kernel 8.0 electronic signature APIs.  
  
 The Java APIs provide HSD&D developers that are rehosting their applications
 to a new Java environment a standardized method for migrating their electronic
 signature functionality. It is hoped that this will reduce duplication of
 effort, promote more efficient use of limited development resources, and
 satisfy the VistA user's business needs.  
  
 This IA permits Electronic Signature to access electronic signature-related
 data in the NEW PERSON file (#200) as listed in the GLOBAL REFERENCE section
 of this Integration Agreement. All fields are accessed via VA FileMan calls,
 such as $$GET1^DIQ and FILE^DIE, rather than direct global reads.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ELECTRONIC SIGNATURE
  ISC: Oakland
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 4/10/23, effective with patch DSSO*2.0*3, APAT
 requests access to update SIGNATURE BLOCK PRINTED NAME (#20.2) using FileMan.
 If the SIGNATURE BLOCK PRINTED NAME (#20.2) of the NEW PERSON (#200) file is 
 null, then the SIGNATURE BLOCK PRINTED NAME (#20.2) will be set to a 
 standardized value beginning with given name for display on the purchase order
 report. Kernel Name Standardization APIs will be used for this formatting.
 This is in the UP1^DSSOPN2 API.  

NUMBER: 4298                            IA #: 4298
  FILE NUMBER: 63                       GLOBAL ROOT: LR(
  DATE CREATED: DEC 10, 2003            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: SNOMED CODES FOR WH             ID: LR(
GLOBAL REFERENCE: LR(D0,'SP',D1,2,D2,0)
FIELD NUMBER: .01                       FIELD NAME: ORGAN/TISSUE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,'SP',D1,2,D2,2,D3,0)
FIELD NUMBER: .01                       FIELD NAME: MORPHOLOGY
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Women's Health (WH) package requests permission to
 look at the following FILE 63 fields: 
  
  GLOBAL REFERENCE: ^LR(D0,'SP',D1,2,D2,0) 
           SUBFILE: 63.12 
           FIELD #: .01 
        FIELD NAME: ORGAN/TISSUE 
        NODE/PIECE: 0;1    
  
  GLOBAL REFERENCE: ^LR(D0,'SP',D1,2,D2,2,D3,0) 
           SUBFILE: 63.16 
           FIELD #: .01 
        FIELD NAME: MORPHOLOGY      
        NODE/PIECE: 0;1    
  
 These fields hold pointer values to other Lab package files containing SNOMED
 codes (FILES 61 and 61.1) used to identify the kind of lab test performed.  
  
 1) In the WH package, a new option has been created to allow each site to 
 select the SNOMED codes from FILEs 61 and 61.1 that are used locally for Pap
 Smears. WH will point to these two files and store the pointer values in a WH
 file (IAs 4154 and 4155).  
  
 2) There is already an event point in the Lab package that calls WH whenever a
 Cytology or Surgical Pathology Lab test is verified. When the Lab test is
 verified, the WH package will check these fields of the Lab test to see what
 SNOMED codes, if any, are used. If any of the SNOMED codes used in the Lab
 test match the SNOMED code(s) selected in #1, the WH package will assume that
 Lab test is a Pap Smear. Direct global reads are needed because internal entry
 numbers of file entries are being checked, not external values.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SNOMED
SUBSCRIBING PACKAGE: WOMEN'S HEALTH     ISC: Hines

NUMBER: 4299                            IA #: 4299
  DATE CREATED: NOV 25, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: IBNCPDP                      NAME: EPHARMACY API
  ID: IBNCPDP
 GENERAL DESCRIPTION:   The Outpatient Pharmacy, CMOP, and ECME packages
 request the usage of the Integrated Billing functions to support ePharmacy
 billing.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NCPDP
KEYWORDS: HIPAA
KEYWORDS: ECME
KEYWORDS: BPS
COMPONENT/ENTRY POINT: $$STORESP(DFN,.ARRAY)
 COMPONENT DESCRIPTION:   The Integrated Billing function $$STORESP^IBNCPDP is
 used by Outpatient Pharmacy and ECME to pass the third party payer's billing
 response information to Integrated Billing.  
VARIABLES: .ARRAY                       TYPE: Input
 VARIABLES DESCRIPTION:   The following elements will be passed to IB: 
    ARRAY("AUTH #")= 
       Authorization number returned by Insurance 
    ARRAY("BILLED")= 
       Amount billed to the insurance 
    ARRAY("CLAIMID")= 
       Reference Number to ECME (ECME #) 
    ARRAY("CLOSE COMMENT")= 
       Optional, if the close reason is defined 
       then the Close Comment parameter may be 
       sent to IB.  
    ARRAY("CLOSE REASON")= 
       Optional, Pointer to the IB CLAIMS TRACKING 
       NON-BILLABLE REASONS file (#356.8) 
    ARRAY("COPAY")= 
       Patient Copay Amount per the Insurance 
    ARRAY("DAYS SUPPLY")= 
       Days Supply 
    ARRAY("DISP FEE PAID")= 
       Dispensing Fee Paid by the Insurance 
    ARRAY("DOS")= 
       Date of Service in FileMan format 
    ARRAY("DROP TO PAPER")= 
       Optional, this parameter may be set to 
       1 (TRUE) for certain Close Claim Reasons, 
       indicating that that the closed 
       episode still may be "dropped to paper" 
       - passed to the Autobiller.  
    ARRAY("DRUG")= 
       IEN of DRUG file (#50) 
    ARRAY("ING COST PAID")= 
       Ingredient Cost Paid by the Insurance 
    ARRAY("FILL NUMBER")= 
       Fill or refill number 
    ARRAY("NCPDP QTY")= 
       Quantity converted according to the NCPDP 
       Unit of Measure 
    ARRAY("NCPDP UNITS")= 
       Unit of Measure per the NCPCP standard 
    ARRAY("NDC")= 
       NDC 
    ARRAY("PAID")= 
       Amount paid by the Insurance 
    ARRAY("PAT RESP")= 
       Patient Responsibility per the Insurance 
    ARRAY("PLAN")= 
       IEN of the entry in the GROUP INSURANCE 
       PLAN file (#355.3), which was captured 
       from the $$RX^IBNCPDP call 
    ARRAY("POLICY")= 
        IEN of the INSURANCE TYPE multiple 
        (#.3121) of the PATIENT file (#2) 
    ARRAY("PRESCRIPTION")= 
       IEN from the Prescription file (#52) 
    ARRAY("PRIOR PAYMENT")= 
       Used for secondary claims to pass in 
       The amount paid by the primary 
       insurance.  Required for secondary 
       claims on PAID event.  
    ARRAY("PRIMARY BILL")= 
       Bill IEN from BILL/CLAIMS file (#399).  
       Used for secondary claims to pass in 
       the Primary bill #. Required for 
       secondary claims on PAID event.  
    ARRAY("QTY")= 
       Quantity Dispensed 
    ARRAY("RELEASE COPAY")= 
       Optional, if the claim is being closed, 
       setting this parameter to 1 (TRUE) 
       indicates that the patients copay should 
       be released off hold.  
    ARRAY("RELEASE DATE")= 
       Release date/time in FileMan format 
    ARRAY("RESPIEN")= 
        IEN of the BPS RESPONSE file (#9002313.03) 
    ARRAY("RTYPE")= 
        IEN of record in RATE TYPE file (#399.3).  
        Required for secondary claims on PAID 
        event.  
    ARRAY("RXCOB")= 
       The payer sequence for the claim: 
       1-Primary, 2-secondary. VA doesn't bill 
       other insurances so it can be only 
       these two values. If null then the payer 
       sequence = Primary is assumed. Required 
       for secondary claims on PAID and 
       REVERSED events.  
    ARRAY("RX NO")= 
       RX Number from PRESCRIPTION file (#52) 
    ARRAY("STATUS")= 
       Bill status which will be assigned 
       one of the following values: "PAID", 
       "REVERSED", "CLOSED", "RELEASED", 
       "ELIG", or "SUBMITTED" 
    ARRAY("UNITS")= 
       Prescription Units 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN for the prescription.  
VARIABLES: $$STORESP                    TYPE: Output
 VARIABLES DESCRIPTION:   Bill number = success, 1 = not billable, 0^reason =
 not successful 
  
COMPONENT/ENTRY POINT: $$RX(DFN,.ARRAY)
 COMPONENT DESCRIPTION:   This function returns to the subscribing application
 whether or not a prescription is third party billable.  The subscribing
 application shall pass an array of variables to IB. IB will use the array
 elements during the billing determination logic. IB will return to the
 subscribing application Payer information and a message notifying what billing
 action should be taken on the prescription.  
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN for the prescription.  
VARIABLES: .ARRAY                       TYPE: Both
 VARIABLES DESCRIPTION:   **The following elements will be passed to IB: 
  ARRAY("COST")= 
    Price per Dispense Unit 
  ARRAY("DEA")= 
    DEA special handling code 
  ARRAY("DOS")= 
    Date of Service in Fileman format 
  ARRAY("FILL NUMBER")= 
    Fill number 
  ARRAY("IEN")= 
    IEN from Prescription file (#52) 
  ARRAY("NDC")= 
    NDC (ex: 55953-0344-80) 
  ARRAY("NCPDP QTY")= 
    Quantity converted according to the 
    NCPCP Unit of Measure 
  ARRAY("NCPDP UNITS")= 
    Unit of Measure per the NCPCP standard 
  ARRAY("PLAN")= 
    IEN of the entry in the GROUP 
    INSURANCE PLAN file (#355.3). Required 
    for secondary billing.  
  ARRAY("QTY")= 
    Quantity Dispensed 
  ARRAY("RELEASE DATE")= 
    Rx release date/time in Fileman format 
  ARRAY("RXCOB")= 
    Payer sequence for the claim (1-Primary, 
    2-Secondary). If null, then  payer 
    sequence Primary (1) is assumed.  
  ARRAY("RX ACTION")= 
    RX Action making the call 
    Example: "ELIG" for eligibility 
  ARRAY("RTYPE")= 
    IEN of record in RATE TYPE file (#399.3).  
    Required for secondary claims.  
  ARRAY("SC/EI OVR")= 
    SC/EI Override (0 or 1) where: 
     0 - Do not ignore Service 
         Connection/Environmental Indicators 
         and answers to respective questions.  
  
         If the RX was connected to at least 
         one of patient's SC/EI conditions 
         then RX will be considered as 
         non-ECME billable and the API will 
         return 0 in the first piece and a 
         respective indicator in the second 
         piece. Example: 0^AGENT ORANGE.  
  
         If at least one of the questions 
         wasn't answered, the RX will be 
         considered as non-ECME billable and 
         the API will return 0 in the first 
         piece and NEEDS SC DETERMINATION in 
         the second piece 
         (0^NEEDS SC DETERMINATION).  
  
     1 - Ignore Service Connection/Environmental 
         Indicators and bill the payer. The API 
         will return 1 unless there is a 
         different reason the RX is not billable.  
  
  ARRAY("UNITS")= 
    Prescription Units 
  
  
 **The following elements will be returned from IB: 
  ARRAY("BILL")= 
    Bill Flag (0 OR 1) 
  ARRAY("INS",Sequence,1)= 
    Piece 1: IEN of record in the GROUP INSURANCE 
               PLAN file (#355.3) 
    Piece 2: BIN 
    Piece 3: PCN 
    Piece 4: Billing Payer Sheet Name (B1) 
    Piece 5: Group ID 
    Piece 6: Cardholder ID 
    Piece 7: Patient Relationship Code 
    Piece 8: Cardholder First Name 
    Piece 9: Cardholder Last Name 
    Piece 10: Home Plan State 
    Piece 11: Reversal Payer Sheet Name (B2) 
    Piece 12: Rebill Payer Sheet Name (B3) 
    Piece 13: Software/Vendor Certification ID 
    Piece 14: Insurance Co Name from Insurance 
              file (#36) 
    Piece 15: Eligibility Payer Sheet Name (E1) 
    Piece 16: Billing Payer Sheet IEN (B1) 
    Piece 17: Reversal Payer Sheet IEN (B2) 
    Piece 18: Rebill Payer Sheet IEN (B3) 
    Piece 19: Eligibility Payer Sheet IEN (E1) 
    Piece 20: Person Code 
  
    where: 
      The IEN of file 355.3 shall be recorded in 
        the subscribing application's database 
        so that it can be retrieved and passed in 
        as input to the function $$STORESP^IBNCPDP 
      Home Plan State = State IEN for State 
        file (#5) 
  
  ARRAY("INS",Sequence,2)= 
    Piece 1: Dispensing Fee Submitted 
    Piece 2: Basis of Cost Determination 
    Piece 3: Base Price 
    Piece 4: Gross Amount Due 
    Piece 5: Administrative Fee 
    Piece 6: Ingredient Cost 
    Piece 7: Usual and Customary Amount 
  
  where: 
     Basis of Cost Determination= 
         01 for AWP 
         05 for Cost 
         07 for Usual & Customary 
     Base Price= 
         AWP = Gross Amount Due less Dispensing Fee 
               and Administrative Fee 
         Cost = Ingredient Cost plus Dispensing Fee 
         U&C = Gross Amount Due 
    Gross Amount Due= 
         Ingredient Cost plus Dispense fee plus 
         Administrative fee 
  
  ARRAY("INS",Sequence,3)= 
    Piece 1: Group name 
    Piece 2: Insurance Company Phone Number 
    Piece 3: Plan ID 
    Piece 4: Plan Type 
    Piece 5: Insurance Company IEN (#36) 
    Piece 6: COB Indicator 
    Piece 7: Policy Number 
    Piece 8: Maximum Transaction Count 
  
  where: 
        Plan Type= 
            "C" for CHAMPVA 
            "T" for TRICARE 
            "V" for Veteran Insurance 
        COB Indicator= 
             COB field (#.2) of the INSURANCE 
             TYPE multiple (#.3121) of the 
             PATIENT file (#2) 
        Policy Number= 
             IEN of the INSURANCE TYPE multiple 
             (#.3121) of the PATIENT file (#2) 
             
  ARRAY("SC/EI NO ANSW")= IB returns the list of 
           SC and environmental indicators for 
           which SC/EI connected question(s) 
           has not been answered, example: 
           "AO,SWA,CV" 
  
   Set of the following Service Connection/ 
   Environmental Indicator related nodes: 
    ARRAY("AO")=null,0 or 1    Agent Orange 
    ARRAY("EC")=null,0 or 1    Environmental 
                               Contaminants 
    ARRAY("SWA")=null,0 or 1   SouthWest Asia 
    ARRAY("SC")=null,0 or 1    Service Connected 
    ARRAY("IR")=null,0 or 1    Ionizing 
                               Radiation 
    ARRAY("HNC")=null,0 or 1   Head/Neck Cancer 
    ARRAY("MST")=null,0 or 1   Military Sexual 
                               Trauma 
    ARRAY("CV")=null,0 or 1    Combat Veteran 
    ARRAY("SHAD")=null,0 or 1  Project 112/SHAD 
    ARRAY("CLV")=null,0 or 1   Camp Lejeune 
  
  
  where: 
      null - the question has not been answered 
      (and therefore requires service connection 
       determination if the patient has such a 
       condition in file 
         0 - user answered "No" (Not connected) 
         1 - user answered "Yes" (Connected) 
VARIABLES: $$RX                         TYPE: Output
 VARIABLES DESCRIPTION:   
      Result ^ Reason ^ Primary Eligibility Type 
         where 
             Result: 
                1 = the transaction is billable 
                0 = not billable 
             Reason: reason not billable text (only 
                     if Result=0) 
             Primary Eligibility Type: 
                  C - CHAMPVA 
                  T - TRICARE or Sharing 
                  V - Veteran 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: DEC 22, 2011

NUMBER: 4300                            IA #: 4300
  DATE CREATED: NOV 09, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: BPSOSRX
  NAME: DBIA4300                        ID: BPSOSRX
 GENERAL DESCRIPTION:   
  
 The Outpatient Pharmacy Package requests access to call the Electronic Claims
 Management Engine (ECME) Package to perform the following functions: 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: NCPDP
KEYWORDS: HIPAA
KEYWORDS: ECME
COMPONENT/ENTRY POINT: $$CLAIM(BRXIEN,BFILL)
 COMPONENT DESCRIPTION:   Submits a prescription to the Electronic Claims
 Management Engine (ECME) for claims generation and transmission.  
VARIABLES: BRXIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN.  
VARIABLES: BFILL                        TYPE: Input
 VARIABLES DESCRIPTION:   Fill number.  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   ECME will return: 
  
  0^reason = failure (should never happen) 
  1 = accepted for processing 
COMPONENT/ENTRY POINT: $$UNCLAIM(BRXIEN,BFILL)
 COMPONENT DESCRIPTION:   This entry point reverses a previously paid claim on
 a prescription.  
VARIABLES: BRXIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN.  
VARIABLES: BFILL                        TYPE: Input
 VARIABLES DESCRIPTION:   Fill number.  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   
  ECME will return: 
  
  0^reason = failure (should never happen) 
  1 = accepted for processing 
COMPONENT/ENTRY POINT: $$STATUS(BRXIEN,BFILL)
 COMPONENT DESCRIPTION:   This function returns the ECME billing status of a
 particular prescription.  
VARIABLES: BRXIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN 
VARIABLES: BFILL                        TYPE: Input
 VARIABLES DESCRIPTION:   Fill number.  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   Returned value from ECME: 
  
 X = result^time^description 
  
 Where: 
  
 result =  E PAYABLE, E REJECTED, E CAPTURED, E DUPLICATE, E REVERSAL ACCEPTED, 
 E REVERSAL REJECTED, E OTHER, PAPER, PAPER REVERSAL 
  
 time = fileman date and time of last recorded update in ECME 
  
 description = Waiting to start, Waiting for packet build, Waiting to transmit,
 Processing response, Payable, Rejected, Reversal Accepted, Reversal Rejected 
  
 If there's no ECME record of this prescription and fill, returns null. 
COMPONENT/ENTRY POINT: SHOWQ
 COMPONENT DESCRIPTION:   This entry point displays the number of Claims
 waiting to be submitted and the number of claims waiting to be reversed.  
  
 Example:   D SHOWQ^BPSOSRX 
  
 Returns: 
  
  CLAIM - none 
  UNCLAIM - none 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 4301                            IA #: 4301
  FILE NUMBER: 9002313.56               GLOBAL ROOT: BPS(9002313.56
  DATE CREATED: NOV 09, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            ROUTINE: IBNCPDP
  NAME: DBIA4301                        ID: IBNCPDP
GLOBAL REFERENCE: BPS(9002313.56
FIELD NUMBER: 13800                     FIELD NAME: OUTPATIENT SITE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Outpatient Pharmacy requests to use direct reads to the
 BPS Electronic Claims Management Engine's (ECME) BPS Pharmacies file
 (#9002313.56) to verify that a particular Pharmacy is defined to bill third
 party claims.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: NCPDP
KEYWORDS: HIPAA
KEYWORDS: ECME
KEYWORDS: BPS
COMPONENT/ENTRY POINT: STORESP
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 4302                            IA #: 4302
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: NOV 17, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA4302
  ID: PSRX(
GLOBAL REFERENCE: PSRX(D0
FIELD NUMBER: 521012                    FIELD NAME: ACTUAL NDC DISPENSED
  LOCATION: "NDC";0                     ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: PSRX(D0,1
FIELD NUMBER: 19                        FIELD NAME: ACTUAL NDC DISPENSED
  LOCATION: "NDC";1                     ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   The Electronic Claims Management Engine (ECME) package
 requests direct read/write access to store the billed NDC in the Prescription
 file (#52). 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: NCPDP
KEYWORDS: HIPAA
KEYWORDS: ECME
KEYWORDS: BPS
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  ISC: Birmingham

NUMBER: 4303                            IA #: 4303
  FILE NUMBER: 59                       GLOBAL ROOT: PS(59
  DATE CREATED: JAN 06, 2006            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA4303
  ID: PS(59
GLOBAL REFERENCE: PS(59
 GENERAL DESCRIPTION:   The Electronic Claims Management Engine (ECME) package
 requests read access to the Outpatient Site file (#59).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: NCPDP
KEYWORDS: HIPAA
KEYWORDS: ECME
KEYWORDS: BPS
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  ISC: Birmingham

NUMBER: 4304                            IA #: 4304
  DATE CREATED: DEC 03, 2003            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSONCPDP                     NAME: DBIA4304
  ID: PSONCPDP
 GENERAL DESCRIPTION:   CMOP requests access to call Outpatient Pharmacy's
 function $$EN^PSONCPDP.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NCPDP
KEYWORDS: HIPAA
KEYWORDS: ECME
KEYWORDS: BPS
COMPONENT/ENTRY POINT: $$EN(BRXIEN,BFILL,BFILLDAT,BWHERE,BILLNDC)
 COMPONENT DESCRIPTION:   This entry point is used to calls IB to determine
 whether a prescription is third party billable.  If so, submits the
 prescription to ECME for claims build and transmission to payer.  It then
 returns the status of the claim response to the calling routine.  
VARIABLES: BRXIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN.  
VARIABLES: BFILL                        TYPE: Input
 VARIABLES DESCRIPTION:   Fill Number.  
VARIABLES: BFILLDAT                     TYPE: Input
 VARIABLES DESCRIPTION:   Fill Date.  
VARIABLES: BWHERE                       TYPE: Input
 VARIABLES DESCRIPTION:   One of the following must be sent for the billing
 function being requested: 
  
 CRLR = CMOP release reversal = Reverse Claim; CRLB = CMOP release rebill =
 Reverse then Rebill Claim; PS   = CMOP build silent = Display no information
 for CMOP Claim 
VARIABLES: BILLNDC                      TYPE: Input
 VARIABLES DESCRIPTION:   NDC returned from the CMOP.  
VARIABLES: $$EN                         TYPE: Output
 VARIABLES DESCRIPTION:   Returned: 
  
  0 = Billed with no errors 
  3 = Prescription is suspended 
  4 = Payer returned a drug interaction 
  6 = Could not process.  IB data missing.  
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham

NUMBER: 4305                            IA #: 4305
  FILE NUMBER: 9002313.99               GLOBAL ROOT: BPS(9002313.99
  DATE CREATED: NOV 09, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA4305
  ID: BPS(9002313.99
GLOBAL REFERENCE: BPS(9002313.99,1
FIELD NUMBER: 2500                      FIELD NAME: CERTIFIER
  LOCATION: CERTIFIER;1                 ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Outpatient Pharmacy requests read access to the ECME
 BPS Setup file (#9002313.99).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: NCPDP
KEYWORDS: BPS
KEYWORDS: HIPAA
KEYWORDS: ECME
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 4306                            IA #: 4306
  DATE CREATED: DEC 03, 2003            CUSTODIAL PACKAGE: LEXICON UTILITY
  CUSTODIAL ISC: Dallas                 USAGE: Controlled Subscription
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: LEXICAL SERVICES UPDATE Protocol
 GENERAL DESCRIPTION:   This protocol is used to notify other applications and 
 processes when the Lexicon Utility or the Lexicon Change file is updated. 
  
 The Lexicon is updated using a temporary maintenance global, ^LEXM.  This
 global is processed by the routine LEXXGI.  Once processed, this protocol is
 triggered and the global ^LEXM is deleted.  
   
 Required Variable LEXSCHG Array contains a listing of those Lexicon Files
 (#757 - 757.41) that were updated as a result of a recent install.  In the
 case of the CHANGE LOG (file #757.9), new changes to SDO controlled files will
 be indicated by file number and the internal entry number to the CHANGE LOG.  
  
 The variable LEXSCHG is created while processing the Lexicon Maintenance
 global ^LEXM.  It will indicate what files were updated.  
   
    Example: 
   
          LEXSCHG(757,0)="" 
          LEXSCHG(757.001,0)="" 
          LEXSCHG(757.01,0)="" 
          LEXSCHG(757.02,0)="" 
          LEXSCHG(757.1,0)="" 
          LEXSCHG(757.11,0)="" 
          LEXSCHG(757.9,0)="" 
          LEXSCHG(757.9,2)=80 
          LEXSCHG(757.9,3)=80.1 
          LEXSCHG(757.9,4)=81 
          LEXSCHG(757.9,"B",80,2)="" 
          LEXSCHG(757.9,"B",80.1,3)="" 
          LEXSCHG(757.9,"B",81,4)="" 
   
    If ICD-9-CM and/or CPT-4 changes are included in the ^LEXM 
    global, then the following entries will be found in the 
    local array LEXSCHG: 
   
         LEXSCHG(80,0)="" 
         LEXSCHG(80.1,0)="" 
         LEXSCHG(81,0)="" 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DRG GROUPER        ISC: Albany
 SUBSCRIBING DETAILS:   The subscribing protocol is:  ICD CODE UPDATE EVENT 
SUBSCRIBING PACKAGE: CPT/HCPCS CODES    ISC: Albany
 SUBSCRIBING DETAILS:   The subscribing protocol is:  ICPT CODE UPDATE EVENT 

NUMBER: 4307                            IA #: 4307
  DATE CREATED: DEC 08, 2003            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: PSB VITAL MEAS FILE             REMOTE PROCEDURE: PSB VITAL MEAS FILE
 GENERAL DESCRIPTION:   This RPC has been built specifically to process the
 filing of BCMA Pain Score data. The processing of other VITAL type may be
 incorporated with some adjustments.  
  
  
   This routine is to service BCMA 3.0 functionality and store VITALs' 
   data into the VITAL MEASUREMENT FILE - ^GMR(120.5  using the API 
   GMRVPCE0 
  
   Parameters: 
         Input  - 
                         DFN   (r) Pointer to the PATIENT (#2) file 
                         RATE  (r)  BCMA trigger event/transaction 
                         VTYPE (o) Pointer to GMRV VITAL TYPE FILE (#120.51) 
                                   (default = Pain ["PN"]) 
                         DTTKN (o) Date/time (FileMan) measurement was taken 
                                   (default = $$NOW^XLFDT()) 
        Output -         RESULTS(0) = 1 
                         RESULTS(1) ="1^Pain Score successfully filed" 
                   or    RESULTS(1) ="-1^ERROR * Pain Score NOT filed 
                                      successfully" 
  
  Process results in the storing of VITAL Measurement rate into the VITAL 
  MEASUREMENT FILE per the given patient and vital type.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSB
KEYWORDS: BCMA
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN
  ISC: Birmingham

NUMBER: 4308                            IA #: 4308
  FILE NUMBER: 350                      GLOBAL ROOT: IB(
  DATE CREATED: DEC 02, 2003            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            NAME: NEW FILE #350 FIELD
  ID: IB(
GLOBAL REFERENCE: IB(D0,1)
FIELD NUMBER: 17                        FIELD NAME: HOLD-REVIEW DATE
  LOCATION: 1;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the date the patient charge was put on
 HOLD-REVIEW status.  
 GENERAL DESCRIPTION:   A new field called HOLD-REVIEW DATE (#17) will be added
 to the INTEGRATED BILLING ACTION (#350) file, so that when a charge is put in
 'HOLD-REVIEW' status in the file, this field will be automatically "stuffed"
 with the current date. This will be similar to the file field ON HOLD DATE
 (#16), where if a charge in the file is put in 'ON HOLD' status, it's stuffed 
 with the current date.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 4309                            IA #: 4309
  GLOBAL ROOT: DD(                      DATE CREATED: DEC 14, 2010
  CUSTODIAL PACKAGE: 1                  USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Allow looping through 'AUDIT' nodes of DD
  ID: DD(
GLOBAL REFERENCE: DD(60,AUDIT,D0)
GLOBAL REFERENCE: DD(60.01,AUDIT,D0)
GLOBAL REFERENCE: DD(60.1,AUDIT,D0)
GLOBAL REFERENCE: DD(60.11,AUDIT,D0)
GLOBAL REFERENCE: DD(60.12,AUDIT,D0)
GLOBAL REFERENCE: DD(60.13,AUDIT,D0)
 GENERAL DESCRIPTION:   The LAB SERVICE package (LSRP project) has a
 requirement that we set specific fields to be audited on patch installation
 and remove any audit indicators on any fields that are not in the predefined
 list for the LABORATORY TEST file (#60) and for a few file 60 subfiles.  In
 order to reset the existing audit indicators, it will be necessary to use hard 
 code to traverse the ^DD(60,"AUDIT", fields.  
  
    S LRFLD=0 F  S LRFLD=$O(^DD(60,"AUDIT",LRFLD)) Q:'LRFLD  D 
    . If audit on and field LRFLD is not on list, turn audit off for LRFLD 
    . If audit off and field LRFLD is on list, turn audit on for LRFLD 
  
 The subfiles that are also included for this task are: 
  
    Field #   Field Name          Subfile #    Direct reference needed 
    ==================================================================
     100      SITE/SPECIMEN        60.01       ^DD(60.01,"AUDIT" 
       2      SYNONYM              60.1        ^DD(60.1,"AUDIT"      
       6      ACCESSION AREA       60.11       ^DD(60.11,"AUDIT" 
     500      VERIFY WKLD CODE     60.12       ^DD(60.12,"AUDIT" 
     500.1    ACCESSION WKLD CODE  60.13       ^DD(60.13,"AUDIT" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: DEC 15, 2010

NUMBER: 4310                            IA #: 4310
  DATE CREATED: DEC 09, 2003
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: CSLARACS
  NAME: Sub-Organization Query          ID: CSLARACS
 GENERAL DESCRIPTION:   Allow the user to query CoreFLS for  sub-organization
 matching a given query string.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: SUB-ORG
KEYWORDS: SUB-ORGANIZATION
KEYWORDS: ACS
COMPONENT/ENTRY POINT: SOQ
VARIABLES: CSLY                         TYPE: Output
 VARIABLES DESCRIPTION:   This output variable will be equal to the numeric
 value of the selected sub-org upon success. Upon success it will always be
 true that +CSLY>0.  
                             
 Upon failure, we will alway have +CSLY<0 and the value CSLY will be: 
                             
 -1 upon network timeout -2 if the user either provided no response or exited
 with "^" when prompted for a sub-org -3 if the user either provided no
 response or exited with "^" when prompted to select a fund from several 
 matching values.  -4 if no matching value was found.  -5 if there was an 
 internal error.  

NUMBER: 4311                            IA #: 4311
  DATE CREATED: DEC 09, 2003
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: CSLARACS
  NAME: Query for Part 2 & 3 of Program String
  ID: CSLARACS                          STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
KEYWORDS: PARTS 2&3
KEYWORDS: PROGRAM
COMPONENT/ENTRY POINT: PRQ
 COMPONENT DESCRIPTION:   This output variable will be equal to the value of
 the selected program upon success. Upon success it will always be true that
 +CSLY>0.  
                             
 Upon failure, we will alway have +CSLY<0 and the value CSLY will be: 
                             
 -1 upon network timeout -2 if the user either provided no response or exited
 with "^" when prompted for a program -3 if the user either provided no
 response or exited with "^" when prompted to select a program from several
 matching values.  -4 if no matching value was found.  -5 if there was an
 internal error.  

NUMBER: 4312                            IA #: 4312
  DATE CREATED: DEC 12, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGCVEXP                      NAME: COMBAT VET STATUS EXPIRED
  ID: DGCVEXP
 GENERAL DESCRIPTION:   This API will provide a list of any veterans with
 expired CV Status.  It is being produced so that IB can check to see if any
 veterans were improperly billed due to a bug in the Combat Vet Interim
 Solution patch (DG*5.3*528).  It is not intended for any other use.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This routine is an API listing veterans with expired
 CV status.  
VARIABLES: TMP("DGCVEX",$J,             TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP("DGCVEX",$J,DFN,CV End Date)="" 
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4313                            IA #: 4313
  GLOBAL ROOT: KMPTMP('KMPDT',          DATE CREATED: DEC 16, 2003
  CUSTODIAL PACKAGE: CAPACITY MANAGEMENT TOOLS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: CAPACITY PLANNING TIMING METRIC DATA
  ID: KMPTMP('KMPDT',
GLOBAL REFERENCE: KMPTMP("KMPDT",
 GLOBAL DESCRIPTION:   Packages are given direct write and read permission of
 the ^KMPTMP("KMPDT") global in order to generate Capacity Planning (CP) timing
 metric data for capacity planning purposes.  
  
 1. The calling package will initially start the Capacity Planning (CP) 
    timing metric clock with the following code: 
  
    S ^KMPTMP("KMPDT",pkg_name,id_node)=$H_start_time_"^^"_$G(DUZ)_"^" 
    _$G(IO( "CL NM")) 
  
    Where pkg_name = Variable identifies the particular calling package 
           Id_node = identifying id that will be utilized when the timing 
                     metric clock is stopped (see Item 2 below) 
     $H_start_time = Start time in $Horolog format 
  
    NOTE: DUZ and IO("CLNM") are Kernel system variables 
  
    Where 
             DUZ = User id 
      IO("CLNM") = client name 
  
  
  
 2. The calling package will stop the Capacity Planning (CP) timing 
    metric clock with the following code: 
  
    S $P(^KMPTMP("KMPDT",pkg_name,id_node),"^",2)=$H_stop_time 
  
    Where pkg_name = Variable identifies the particular calling package 
           Id_node = identifying id that was used when the timing metric 
                     clock was started (see 1 above) 
      $H_stop_time = Stop time in $Horolog format 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIMING
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   The subscribing package will use the following
 variables: 
  
   pkg_name = "ORWCV" 
    id_node = NODE 
  
 Where NODE = "ORWCV "_IP_"-"_HWND_"-"_DFN 
  
 Where HWND and DFN are parameters passed into the calling ORWCV POLL RPC.  
SUBSCRIBING PACKAGE: RPC BROKER
 SUBSCRIBING DETAILS:   RPC ADDED 12/7/2011 

NUMBER: 4314                            IA #: 4314
  DATE CREATED: MAR 08, 2007
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  NAME: Does User Have *ANY* TIU Documents
 GENERAL DESCRIPTION:   For efficient graphing of Progress Notes, the CPRS GUI
 Graphing Utility begins by determining whether the patient has any documents
 at all in the TIU DOCUMENT File 8925.  This Boolean extrinsic function makes
 that determination.  
  
  This API does not limit in ANY way the file entries which it considers 
 documents.  Any entry at all produces a 1 (Yes) value.  
  STATUS: Pending
KEYWORDS: DOCUMENTS

NUMBER: 4315                            IA #: 4315
  DATE CREATED: MAR 12, 2007
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIULX
  NAME: Does Patient Have *ANY* TIU Documents
  ID: TIULX
 GENERAL DESCRIPTION:   This Boolean function facilitates Progress Note
 Graphing in the CPRS GUI Graphing Utility.  The Utility first checks to see if
 the patient has ANY TIU documents at all.  ANY entry at all in the TIU
 DOCUMENT file [8925] for the given patient will yield a YES (1) answer.  This
 may include non-Progress Notes including documents entered from other packages
 which are not displayed except perhaps in reports. It will also include
 documents of all statuses (some not generally viewable) including retracted
 documents.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU Documents
KEYWORDS: 8925
KEYWORDS: TIU Document File
COMPONENT/ENTRY POINT: $$HASDOCMT(DFN)
 COMPONENT DESCRIPTION:   Extrinsic function returns 1 if patient DFN has *ANY*
 entries in the TIU DOCUMENT File [8925].  Otherwise, it returns 0.  
VARIABLES: $$HASDOCMT                   TYPE: Output
 VARIABLES DESCRIPTION:   Extrinsic function returns 1 if patient DFN has *ANY*
 entries in the TIU DOCUMENT File [8925].  Otherwise, it returns 0.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number in the PATIENT File [#2] of the
 patient in question.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAR 12, 2007

NUMBER: 4316                            IA #: 4316
  FILE NUMBER: 869.3                    GLOBAL ROOT: HLCS(869.3
  DATE CREATED: AUG 24, 2004            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: VDEF access to Institution and Mail Group data
  ID: HLCS(869.3
GLOBAL REFERENCE: HLCS(869.3,D0
FIELD NUMBER: .04                       FIELD NAME: INSTITUTION
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: MAIL GROUP
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This IA exposes Institution and Mail Group (File 869.3,
 fields .04 and .05) to VDEF that builds the MSH segment for VDEF-built HL7
 messages.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MSH
SUBSCRIBING PACKAGE: VISTA DATA EXTRACTION FRAMEWORK
 SUBSCRIBING DETAILS:   This IA enables the part of VDEF that builds the MSH
 segment for HL7 messages to access the Institution field and the Mail Group
 field in file #869.3.  

NUMBER: 4317                            IA #: 4317
  DATE CREATED: DEC 23, 2003            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         NAME: ALLOW USEAGE OF DGUTQ
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany

NUMBER: 4318                            IA #: 4318
  DATE CREATED: DEC 29, 2003            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGUTQ
  NAME: ALLOW ACCESS TO ROUTINE DGUTQ   ID: DGUTQ
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DGUTQ
COMPONENT/ENTRY POINT: ZIS
 COMPONENT DESCRIPTION:   The call to this line tag is to get a device for
 printing. It also allows the print job to be queued.  
VARIABLES: POP                          TYPE: Output
 VARIABLES DESCRIPTION:   This variable is set to 0 if there a viable output
 device has been selected. It is set to 1 if the user cancels the request for
 an output device.  
VARIABLES: IO                           TYPE: Output
 VARIABLES DESCRIPTION:   This variable is the viable output device to be used
 for printing.  
COMPONENT/ENTRY POINT: CLOSE
 COMPONENT DESCRIPTION:   This line tag closes the output device being used
 with a call to ^%ZISC.  
VARIABLES: ZTQUEUED                     TYPE: Input
 VARIABLES DESCRIPTION:   If this variable has been set then the CLOSE line tag
 will quit and not execute the ^%ZISC call. 
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 4319                            IA #: 4319
  FILE NUMBER: 4.3                      GLOBAL ROOT: XMB(1
  DATE CREATED: DEC 26, 2003            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  NAME: KERNEL ACCESS TO TIME ZONE INFORMATION
  ID: XMB(1
GLOBAL REFERENCE: XMB(1,D0,0)
FIELD NUMBER: 1                         FIELD NAME: TIME ZONE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This IA is used to allow Kernel access time zone
 information that is owned by MailMan, specificaly field 1 of file 4.3.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: KERNEL

NUMBER: 4320                            IA #: 4320
  FILE NUMBER: 4.4                      GLOBAL ROOT: XMB(4.4
  DATE CREATED: DEC 26, 2003            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  NAME: KERNEL ACCESS TO MAILMAN'S TIME ZONE INFORMATION
  ID: XMB(4.4
GLOBAL REFERENCE: XMB(4.4,D0
FIELD NUMBER: 2                         FIELD NAME: DIFFERENTIAL
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TIME ZONE NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   This IA also allows direct reading of the "C"
 cross-reference index.  
 GENERAL DESCRIPTION:   This IA is used to let the part of VDEF that is in the
 custody of Kernel to access time zone information in the custody of MailMan.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: KERNEL

NUMBER: 4321                            IA #: 4321
  FILE NUMBER: 779.001                  DATE CREATED: AUG 31, 2004
  CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: HL7 EVENT TYPE ACCESS
GLOBAL REFERENCE: HL(779.001,
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   This IA allows the VDEF package to point-to and lookup
 entries in file #779.001. This access is used to verify that VDEF Extract
 Descriptions are based on existing HL7 Event Types.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VDEF
KEYWORDS: HL7 EVENT TYPE
SUBSCRIBING PACKAGE: VISTA DATA EXTRACTION FRAMEWORK
  ISC: Oakland

NUMBER: 4322                            IA #: 4322
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870,
  DATE CREATED: AUG 31, 2004            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: TASKMAN NUMBER ASSOCIATED WITH LOGICAL LINK -- RETRIEVAL
  ID: HLCS(870,
GLOBAL REFERENCE: HLCS(870,
FIELD NUMBER: 12                        LOCATION: 0;12
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: TASK NUMBER
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This integration agreement allows the VDEF package to
 retrieve the TaskMan number that is invoking a Logical Link in order to report 
 information about the link to the user.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VDEF
KEYWORDS: LOGICAL LINK
SUBSCRIBING PACKAGE: VISTA DATA EXTRACTION FRAMEWORK

NUMBER: 4323                            IA #: 4323
  FILE NUMBER: 0                        GLOBAL ROOT: DD(50,0,'IX',
  DATE CREATED: SEP 01, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA 4323                       ID: DD(50,0,'IX',
 GENERAL DESCRIPTION:   Pharmacy Data Management will have access to look at
 the ^DD(50,0,"IX" nodes to get the field number of the file based on the cross
 reference. Then by using the FIELD^DID API, the data type will be determined.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham
 SUBSCRIBING DETAILS:   Pharmacy Data Management code will loop on the
 ^DD(50,0,"IX" nodes to determine the field number of the file based on the
 name of the cross reference. The field number will then be used to determine
 the data type, by using the FIELD^DID API.  

NUMBER: 4324                            IA #: 4324
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: DEC 31, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4324                        ID: VA(200
GLOBAL REFERENCE: VA(200,DO
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 1                         FIELD NAME: INITIAL
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ACCESS CODE
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 7.2                       FIELD NAME: VERIFY CODE never expires
  LOCATION: 0;8                         ACCESS: Write w/Fileman
FIELD NUMBER: 9                         FIELD NAME: SSN
  LOCATION: 1;9                         ACCESS: Write w/Fileman
FIELD NUMBER: 11                        FIELD NAME: VERIFY CODE
  LOCATION: .1;2                        ACCESS: Write w/Fileman
FIELD NUMBER: 200.04                    FIELD NAME: MULTIPLE SIGN-ON
  LOCATION: 200;4                       ACCESS: Write w/Fileman
FIELD NUMBER: 200.05                    FIELD NAME: ASK DEVICE TYPE AT SIGN-ON
  LOCATION: 200;5                       ACCESS: Write w/Fileman
FIELD NUMBER: 201                       FIELD NAME: PRIMARY MENU OPTION
  LOCATION: 201;1                       ACCESS: Write w/Fileman
 GLOBAL DESCRIPTION:   The following X-Ref's are killed also: 
  
 VA(200,"A",(access code))  ** (see note) VA(200,"AOLD"(access code))  ** 
 VA(200,MHV User number,"VOLD") 
  
  
 ** Note: Killed after verifying that it is assigned to MHV user only) 
 GENERAL DESCRIPTION:   During Phase II patch installation of MyHealtheVet the
 following user is created, these fields can also be reset to existing values
 by IRM staff in the event of problems.  Fields are filled, via supported
 FileMan calls, for MHV project in File 200 (New Person).  Access and Verify
 codes are "pre-hashed" for security and consistency across all VAMC's to allow 
 National Patient access via a secure eVault Server.  
  
 User:  MYHEALTHEVET,SECURE SERVER 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MYHEALTHEVET       ISC: Washington/Silver Spring

NUMBER: 4325                            IA #: 4325
  DATE CREATED: JAN 06, 2004            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: AWCMCPR1
  NAME: NATIONAL TIU MONITOR            ID: AWCMCPR1
 GENERAL DESCRIPTION:   A software package to monitor CPRS GUI response time
 for data retrievals of Lab, TIU and Clinical Reminders.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: STRT1
 COMPONENT DESCRIPTION:   Entry point to time TIU data retrieval.  
COMPONENT/ENTRY POINT: END
 COMPONENT DESCRIPTION:   Exit point for all three types of data retrieval. 
 Actually records the times gathered from the CPRS GUI.  
COMPONENT/ENTRY POINT: STRT2
 COMPONENT DESCRIPTION:   Entry point for timing Lab data retrieval.  
COMPONENT/ENTRY POINT: STRT3
 COMPONENT DESCRIPTION:   Entry point for timing Clinical Reminders.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES

NUMBER: 4326                            IA #: 4326
  FILE NUMBER: 0                        GLOBAL ROOT: DD(51.5,0,'IX'
  DATE CREATED: SEP 01, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA 4326                       ID: DD(51.5,0,'IX'
 GENERAL DESCRIPTION:   Pharmacy Data Management will have access to look at
 the ^DD(51.5,0,"IX" nodes to get the field number of the file based on the
 cross reference. Then by using the FIELD^DID API, the data type will be
 determined.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham
 SUBSCRIBING DETAILS:   Pharmacy Data Management code will loop on the
 ^DD(51.5,0,"IX" nodes to determine the field number of the file based on the
 name of the cross reference. The field number will then be used to determine
 the data type, by using the FIELD^DID API.  

NUMBER: 4327                            IA #: 4327
  FILE NUMBER: 101.24                   GLOBAL ROOT: ORD(101.24
  DATE CREATED: FEB 03, 2004
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4327                        ID: ORD(101.24
GLOBAL REFERENCE: ORD(101.24,DA,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: ORD(101.24,DA,2)
FIELD NUMBER: .23                       FIELD NAME: HEADING
  LOCATION: 2;3                         ACCESS: Write w/Fileman
FIELD NUMBER: .24                       FIELD NAME: DESCRIPTIVE TEXT
  LOCATION: 2;4                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   This is a one time only integration agreement for the
 conversion of Medicine components to Medicine/Clinical Procedures components.  
 This integration agreement is used to document that patch 2 of Clinical
 Procedures, MD*1*2, can use FileMan to lookup the entry ORRPW MEDICINE in the
 OE/RR Report file (#101.24) and use FileMan to modify ORRPW MEDICINE to ORRPW
 MEDICINE/CP and add "Medicine/CP" to the Heading and Descriptive Text fields.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Hines

NUMBER: 4328                            IA #: 4328
  FILE NUMBER: 142.1                    GLOBAL ROOT: GMT(142.1
  DATE CREATED: JAN 30, 2004            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4328                        ID: GMT(142.1
GLOBAL REFERENCE: GMT(142.1,DA,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PRINT ROUTINE
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 13                        FIELD NAME: PREFIX
  LOCATION: 0;13                        ACCESS: Write w/Fileman
GLOBAL REFERENCE: GMT(142.1,DA,.1,0)
FIELD NUMBER: 1.1                       FIELD NAME: EXTERNAL/EXTRACT ROUTINE
  LOCATION: .1;0                        ACCESS: Write w/Fileman
GLOBAL REFERENCE: GMT(142.1,DA,3.5,0)
FIELD NUMBER: 3.5                       FIELD NAME: DESCRIPTION
  LOCATION: 3.5;0                       ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   This is a one time only integration agreement for the
 conversion of Medicine Components to Medicine/Clinical Procedures Components. 
 This integration agreement is to document that patch 2 of Clinical Procedures, 
 MD*1*2, can lookup with FileMan the following entries in the Health Summary
 Components file (#142.1): 
      1   MEDICINE ABNORMAL BRIEF  
      2   MEDICINE BRIEF REPORT  
      3   MEDICINE FULL CAPTIONED  
      4   MEDICINE FULL REPORT  
      5   MEDICINE SUMMARY                                              
 Clinical Procedures can write to the entries to change the print routine, 
 prefix, and description to reflect both Medicine and CP.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Hines

NUMBER: 4329                            IA #: 4329
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: JAN 22, 2004            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4329                        ID: VA(200,
GLOBAL REFERENCE: VA(200,
FIELD NUMBER: 8                         FIELD NAME: TITLE
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 29                        FIELD NAME: SERVICE/SECTION
  LOCATION: 5;1                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Active
KEYWORDS: SERVICE/SECTION
KEYWORDS: NEW PERSON
KEYWORDS: TITLE
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Added note 5/17/23, documenting OE/RR historical use of
 $D(VA,200, D0,0) 
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   ADDED 9/2/2009 
SUBSCRIBING PACKAGE: IFCAP
 SUBSCRIBING DETAILS:   IFCAP will obtain this field from the database with a
 FileMan read.  
  DATE ACTIVATED: SEP 22, 2009

NUMBER: 4330                            IA #: 4330
  FILE NUMBER: 49                       GLOBAL ROOT: DIC(49,
  DATE CREATED: JAN 22, 2004            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4330                        ID: DIC(49,
GLOBAL REFERENCE: DIC(49,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Active
KEYWORDS: SERVICE/SECTION
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4331                            IA #: 4331
  DATE CREATED: FEB 02, 2004
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: TIUSRVP1                     NAME: Document Parameters  
  ID: TIUSRVP1
 GENERAL DESCRIPTION:   This integration aggreement allows subscribing packages
 to call DOCPARM^TIUSRVP to get TIU Document Parameters for a TIU Document
 without knowing the Document's type.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: document parameters
KEYWORDS: workload
COMPONENT/ENTRY POINT: DOCPARM
 COMPONENT DESCRIPTION:   The DOCPARM entry point retrieves the TIU Document
 Parameters when passed in a TIU Document IEN 
VARIABLES: TIUY                         TYPE: Both
 VARIABLES DESCRIPTION:   TIUY returns the document parameters of the TIU
 Document Type defined by TIUDA.  
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   TIUDA is the IEN of a TIU Document(file # 8925) 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Order Entry will be using the DOCPARM^TIUSRVP1 API to
 get the Document Parameters of a TIU Document without the use of a TIU
 Document Type.  
SUBSCRIBING PACKAGE: SURGERY

NUMBER: 4332                            IA #: 4332
  DATE CREATED: FEB 02, 2004
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: TIUPXAP2                     NAME: Workload Required?
  ID: TIUPXAP2
 GENERAL DESCRIPTION:   The $$CHKWKL^TIUPXAP2 api determines if workload is
 required for a TIU Document 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: WORKLOAD REQUIRED
COMPONENT/ENTRY POINT: CHKWKL
 COMPONENT DESCRIPTION:   Checks if workload data should be entered.  
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   TIUDA is an IEN of the TIU Document file (#8925) 
VARIABLES: TIUDPRM                      TYPE: Input
 VARIABLES DESCRIPTION:   TIUDPRM is an input array that holds TIU Document
 Parameters (#8925.95) 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Order Entry will use the $$CHKWKL^TIUPXAP2 API to
 determine if workload information will be required for a particular TIU
 Document.  

NUMBER: 4333                            IA #: 4333
  DATE CREATED: JAN 30, 2004            CUSTODIAL PACKAGE: HEALTH SUMMARY
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMTSRAD                      NAME: GMTSRAD
  ID: GMTSRAD
 GENERAL DESCRIPTION:   This routine is called to extract Radiology Order Data. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GET
 COMPONENT DESCRIPTION:   Extract Radiology order data.  
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient identifier.  
VARIABLES: TMP("GMTSRAD",$J,            TYPE: Output
 VARIABLES DESCRIPTION:   Returned global format: ^TMP("GMTSRAD",$J,REVERSE
 DATE,DA,SEQ)= 
    REQ DATE^STATUS^PROCEDURE^SCH DATE^PROVIDER 
  
  ^TMP("GMTSRAD",$J) may be killed before and after the GET call.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   
  

NUMBER: 4334                            IA #: 4334
  DATE CREATED: JAN 30, 2004            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: XU USER TERMINATE
 GENERAL DESCRIPTION:   Other pachages can attach to this protocol option and
 they will be called when a USER is Terminated. The call will be just after the
 users Access and Verify codes have been removed.  DUZ will be the person that
 is running the terminate option.  XUIFN will point to the NEW PERSON file 
 entry that is being terminated.  Returns selected file 200 data to XUSR(field
 name) array for New Person components.  
   
 It is called in XUSTERM from XUSERP.  
  
 Packages may attach or de-attach their options using KIDS.  
  STATUS: Active

NUMBER: 4335                            IA #: 4335
  DATE CREATED: FEB 17, 2004
  CUSTODIAL PACKAGE: AUTOMATED LAB INSTRUMENTS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: LA7UTL1A                     NAME: Microbiology data API
  ID: LA7UTL1A
 GENERAL DESCRIPTION:   Returns Microbiology data for a patient that either has
 specimen a collection date(s) or completion date(s) that fall within the
 passed in date parameters. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: lab
KEYWORDS: Microbiology
KEYWORDS: API
COMPONENT/ENTRY POINT: GETDATA
 COMPONENT DESCRIPTION:   Input: 
        
        LRDFN - Lab DFN 
        LASDT - Search Start Date 
        LAEDT - Search End Date 
        LASEARCH - Set to CD (collection date) or RAD (completion date).  
        RESULTS - Closed root destination array reference 
        
 Output: 
  
   If an error is found with the input variables one for the strings will 
   be returned.  
         
        -1^Start date is after end date 
        -2^No return array global 
        -3^Global array only 
        -4^No Patient lab DFN 
        -5^No Start Date Range 
        -6^No End Date Range 
         
   If there are no errors with the input variables the processing will 
   return '1'.  If there is no data in the passed in global there was no 
   data available for the patient.  
         
   If there is data available for the patient the routine will pass back 
   the following data (the example assumes the passed in closed root 
   global was "^TMP($J)"): 
         
   Fields .01 (Accession date),.05 (Site Specimen),.055 (Sample Type), 
   .06 (Accession #),11.51 (Sterility Control),11.57 (Urine Screen), 
   11.58 (Sputum Screen), 22 (TB RPT Date Approved), 23 (TB RPT Status), 
   24 (ACID Fast Stain), 25 (Quantity) and .99 (Specimen Comment) from the 
   top node in the following format; 
             
   ^TMP($J,LRDFN,Record_IEN,"0",Field #,"E" or "I")=Field Data 
             
   Field .01 of sub file 63.29 - Gram Stain - in the following format; 
         
   ^TMP($J,LRDFN,Record_IEN,"2",Sub File IEN,"0",Field #,"E" or "I")=Data 
         
   Field .01 (Organism) and 1 (Quantity) of sub file 63.3 in the following 
   format; 
           
   ^TMP($J,LRDFN,Record_IEN,"3",Sub File IEN,"0",Field #,"E" or "I")=Data 
         
   Within the Organism data there is an antibiotic multiple.  The routine 
   returns the antibiotic (.01) along with the Mic (field #1) and Mbc 
   (field #2) from the sub file 63.32 in the following format; 
         
   ^TMP($J,LRDFN,Record_IEN,"3",Sub File IEN,"3",Sub-Sub File IEN,"0" 
   ,Field #,"E" or "I")=Data 
         
         
   Organisms can potentially have specific antibiotics associated with 
   them. This API pulls any of the Antibiotics (along with their 
   interpretation and screen) that have been entered in the antibiotic 
   fields that exist within the standard Lab DD.  Within this sub file 
   these fields are numbered between 5 and 160.2 and have node numbers that 
   begin with the numbers 2.00.  
   It is also possible for sites to enter their own specific named 
   antibiotics within this multiple using a lab option.  This option 
   creates a new node number for the new antibiotic entry that is comprised 
   in the following way "2.00"_site #_n (where n is an incremented number).  
   This node number also becomes the field number for this antibiotic. The 
   interpretation and screen values of these antibiotics should follow a 
   pattern where interpretation field number is comprised as follows 
   "2.00"_site #_n_1 and the screen is "2.00"_site#_n_2.  
         
   However only antibiotics have been entered in the standard Organism DD 
   will get extracted.  Any antibiotics entered into the site specified 
   fields will not get extracted.  
         
   ^TMP($J,LRDFN,Record_IEN,"3",Sub File IEN,"0",Field #,"I")=data 
   ^TMP($J,LRDFN,Record_IEN,"3",Sub File IEN,"0",Field #,"E")=field name 
   ^data 
         
   * Note the "E" node contains the field name and it's related data.  
         
         
   Within the Organism data there is a comment multiple which the routine 
   also returns.  Field .01 Comment of sub file 63.31 in the following 
   format; 
          
   ^TMP($J,LRDFN,Record_IEN,"3",Sub File IEN,"1",Sub-Sub File IEN,"0",Field 
   #,"E" or "I")=Data 
         
   Field .01 Bact RPT Remark of sub file 63.33 in the following format; 
         
   ^TMP($J,LRDFN,Record_IEN,"4",Sub File IEN,"0",Field #,"E" or "I")=Data 
        
   Field .01 Parasite of sub file 63.34 in the following format; 
         
   ^TMP($J,LRDFN,Record_IEN,"6",Sub File IEN,"0",Field #,"E" or "I")=Data 
         
   Within Parasite data there is a stage code multiple that the routine 
   also returns.  Fields .01 Stage code and 1 Quantity of sub file 63.35 in 
   the following format; 
         
   ^TMP($J,LRDFN,Record_IEN,"6",Sub File IEN,"1",Sub-Sub File IEN,"0",Field 
   #,"E" or "I")=Data 
         
   Within the Stage Code multiple there can be a Stage Code Comment 
   multiple that this routine also returns; Field .01 of the Stage Code 
   Comment Multiple 63.351 in the following format; 
         
             
   ^TMP($J,LRDFN,Record_IEN,"6",Sub File IEN,"1",Sub-Sub File IEN,"1" ,Sub 
   Sub Sub File IEN,"0",Field #,"E" or "I")=Data) 
         
   Field .01 Parasite RPT Remark 63.36 in the following format; 
          
   ^TMP($J,LRDFN,Record_IEN,"7",Sub File IEN,"0",Field #,"E" or "I")=Data 
         
   Field .01 Fungus/Yeast and field 1 Quantity of sub file 63.37 in the 
   following format; 
         
   ^TMP($J,LRDFN,Record_IEN,"9",Sub File IEN,"0",Field #,"E" or "I")=Data 
         
   Within the Fungus/Yeast data there is a comment multiple which the 
   routine also returns.  
  
   Field .01 Comment of sub file 63.372 in the following format; 
         
   ^TMP($J,LRDFN,Record_IEN,"9",Sub File IEN,"1",Sub-Sub File IEN,"0",Field 
   #,"E" or "I")=Data 
         
         
   Field .01 Mycobacterium and field 1 Quantity of sub file 63.39 in the 
   following format; 
         
   ^TMP($J,LRDFN,Record_IEN,"12",Sub File IEN,"0",Field #,"E" or "I")=Data 
        
   Mycobacterium can potentially have antibiotics associated with them.  
   This API pulls any of the Antibiotics that have been entered in the 
   antibiotic fields that exist within the standard Lab DD.  Within this 
   sub file these fields are numbered between 5 and 55).  
   It is also possible for sites to enter their own antibiotics within this 
   multiple using a lab option.  This option creates a new node number for 
   the new antibiotic entry that is comprised in the following way 
   "2.00"_site #_n (where n is an incremented number). This node number 
   also becomes the field number for this antibiotic.  
         
   However only antibiotics have been entered in the standard Mycobacterium 
   antibiotic DD will get extracted.  Any antibiotics entered into the site 
   specified fields will not get extracted.  
        
   ^TMP($J,LRDFN,Record_IEN,"12",Sub File IEN,"0",Field #,"I")=data 
   ^TMP($J,LRDFN,Record_IEN,"12",Sub File IEN,"0",Field #,"E")=field 
   name^data 
         
   *  Note the "E" node contains the field name and it's related data.  
         
         
         
   Within the Mycobacterium data there is a comment multiple which the 
   routine also returns.  
  
   Field .01 Comment of sub file 63.4 in the following format; 
         
   ^TMP($J,LRDFN,Record_IEN,"12",Sub File IEN,"1",Sub-Sub File 
   IEN,"0",Field #,"E" or "I")=Data 
         
   Field .01 BACT Smear/Prep of sub file 63.291 in the following format; 
         
   ^TMP($J,LRDFN,Record_IEN,"25",Sub File IEN,"0",Field #,"E" or "I")=Data 
         
   Field .01 PARA Smear/Prep of sub file 63.341 in the following format; 
         
   ^TMP($J,LRDFN,Record_IEN,"24",Sub File IEN,"0",Field #,"E" or "I")=Data 
         
   Field .01 VIRUS of sub file 63.43 in the following format; 
         
   ^TMP($J,LRDFN,Record_IEN,"17",Sub File IEN,"0",Field #,"E" or "I")=Data 
VARIABLES: LRDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Lab DFN of the patient.  
VARIABLES: LASDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Search start date.  
VARIABLES: LAEDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Search end date.  
VARIABLES: LASEARCH                     TYPE: Input
 VARIABLES DESCRIPTION:   Set to 'CD' to search by collection date or 'RAD' to
 search by completion date.  
VARIABLES: RESULTS                      TYPE: Both
 VARIABLES DESCRIPTION:   Closed root destination array reference.  
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
  ISC: Hines

NUMBER: 4336                            IA #: 4336
  DATE CREATED: FEB 09, 2004
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  NAME: AP Status Update (from CoreFLS to VistA Prosthetics)
 GENERAL DESCRIPTION:   AP Status Update 
  
 Purpose:  To transmit a message from CoreFLS to VistA Prosthetics when a value 
 on a Prosthetics Purchase Order has been changed, either because of an Invoice
 transaction, a price or quantity change on a PO. or a reconciliation of a line
 item or the cancellation of a PO or the completion of a PO.  
  
 Behavior:  There is no user prompting in this event.  All information is 
 transmitted by CoreFLS.  When the event occurs, a message is sent to VistA
 Prosthetics via CSL.  Upon receipt, an Application Acknowledgement ACK or NAK
 is returned to CoreFLS.  
  
 Information is transmitted from CoreFLS in an HL7 format specified as "AP 
 Status Update Event from CoreFLS".  Incoming information is read by routines
 ~CSLPRUP and ~CSLPRUPA.  If the Order Status Field is "CA", the message is
 considered a cancellation of the entire PO; otherwise, the message is a
 transmission of a change to a specific line on a specified PO.  
  
 Information that is transmitted from CoreFLS is put into an ^XTMP global for
 use by VistA Prosthetics.  
  
 The CSL routine calls a VistA routine, EN~RMPRCSL1(CSLSUB,.ERRAY), passing the
 complete node structure of "CSLAPUP" concatenated with the Message Control ID,
 for processing, plus any content or format errors that the CSL code has
 identified.  
  
 NOTE:  Quantity Invoiced and Invoice Line Amount are assumed to be transmitted
 from CoreFLS as running totals for the line item on the PO.  This means that
 if 15 units were ordered and they were invoiced as they arrived as 1, 2, 3, 4
 then 5 items, there would be 5 AP Status Update messages.  The first would
 reflect a quantity of 1, the second would be 3, the third would 6, the fourth
 would be 10, and the fifth would be 15.  
  
 If the message transmitted is a cancellation of a complete Purchase Order, the
 CSL process branches to ~CSLPRUPC to develop the ~XTMP global with less data
 in the global but with the same structure.   CSL invokes the same processing
 routine for sending information to VistA Prosthetics.  
  
 The CSL routine evaluates the data sent by CoreFLS for the following structure
 and content: 
  
 PO Number longer than 20 characters Quantity Ordered not numeric PO Line
 number not numeric ACS longer than 200 characters Quantity Invoiced not
 numeric Purchase card longer than 80 characters PO Line ID not numeric Unit
 price not numeric Vendor Number longer than 30 characters Vendor Site longer
 than 15 characters Update Date not formatted correctly Line Cancelled Quantity
 not numeric Invoice Line Amount not numeric Order Line Amount not numeric 
  
 After VistA Prosthetics processes the supplied information, if an error is
 detected, an error message is returned to CSL in sub-node 5 of the ~XTMP
 global.  This causes an Application NAK to be transmitted to CoreFLS for
 evaluation and reprocessing.  If no errors are detected, either by CSL or by
 VistA Prosthetics, then an Application Acknowledgement ACK is sent from CSL to
 CoreFLS.  This completes the activities for AP Status Update 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: PROSTHETICS
KEYWORDS: AP
KEYWORDS: UPDATE
KEYWORDS: STATUS
COMPONENT/ENTRY POINT: START
 COMPONENT DESCRIPTION:   The routine begins at START without any parameters
 passed.  
VARIABLES: None
VARIABLES: ~XTMP                        TYPE: Output
 VARIABLES DESCRIPTION:   ~XTMP - First Node Level = "CSLAPUP"+Message Control
 ID Message Control ID is created by the HL7 package 
   
 ~XTMP - Second Node Level = 0 through 6 ~XTMP(x,0) = Delete Record
 Date^Transaction date~"Transmit message to Prosthetics for AP Status" Delete
 Record Date - Date at which the ~XTMP nodes are killed.  Transaction Date -
 Date the ~XTMP nodes were built.  
  
 ~XTMP(x,1)=Update Date~CoreFLS Purchase Order Number~CoreFLS Purchase Order
 Line ID~Vendor Number~Vendor Name~Vendor Site Code Update Date - Date the
 message was created.  CoreFLS Purchase Order Number - Sequential number to
 identify the Purchase Order Purchase Order Line ID - Sequential number to
 identify the line item within the PO.  Vendor Number, Name and Site Code -
 Identifying information about the Vendor on the PO.  
  
 ~XTMP(x,2)=Pcard Number~Item Number~Item description~Unit of Measure Code~UOM
 description~Quantity Ordered~PO Unit Price Pcard Number - 16 digit number
 without spaces.  Item Description - Description of each item ordered on the
 PO.  Unit of Measure Code - Code describing the purchased item by quantity UOM
 Description - Longer description of the purchased item by quantity Quantity
 Ordered - Requested amount of each line on the PO.  PO Unit Price - Price per
 UOM for each line.  
  
 ~XTMP(x,3)=Order Line Amount~Quantity Invoiced~Ivnoce Line Amount~Closed for
 Invoice~Final Match~PO Line cancelled Quantity~PO Line Cancelled~PO Cancelled 
 Order Line Amount - Calculated value equal to Quantity Ordered times the Unit
 Price Quantiy Invoiced - Quantity actually invoiced by the vendor Invoice Line
 Amount - Calculated value equal to Quantity Invoiced times the Unit Price 
 Closed for Invoice - indicator flag equal to Y or N, to indicate that a PO has
 closed for further invoicing.  Final Match - Indicator flag equal to Y or N. 
 Y indicates that the message transmitted is the final transmission, and that
 the line can be reconciled.  PO Line Cancelled Quantity  - If a specific line
 on a PO is cancelled, this is the quantity that is cancelled.  PO Line
 Cancelled - An indicator flag equal to Y or N. A Y indicates that a specific
 line on a PO is cancelled.  PO Cancelled - an indicator flag equal to Y or N.
 A Y indicates that the entire PO is cancelled 
  
 ~XTMP(x,4)=ACS ACS - The complete Account Classification String for the PO 
  
 ~XTMP(x,5)=Error Message Error Message - any text message indicating that
 there is a problem with the message, from VistA or CSL to CoreFLS.  
  
 ~XTMP(x,6)=Line Type~PO Header ID Line type - Either a "G" for goods and/or
 services; "S" for shipping.  PO Header ID - The CoreFLS PO Header ID Code.  
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Washington/Silver Spring

NUMBER: 4337                            IA #: 4337
  FILE NUMBER: 62.06                    GLOBAL ROOT: LAB(62.06
  DATE CREATED: FEB 05, 2004            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: File 62.06                      ID: LAB(62.06
GLOBAL REFERENCE: LAB(62.06
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   A lookup is done on the file using the "AD" cross
 reference and MIX^DIC 
 GENERAL DESCRIPTION:   Access to data in the ANTIMICROBIAL SUSCEPTIBILITY FILE
 (#62.06) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4338                            IA #: 4338
  DATE CREATED: MAR 23, 2007            CUSTODIAL PACKAGE: 757
  USAGE: Private                        TYPE: Other
  NAME: Person Service Patient Construct Java APIs - used by PATS
 GENERAL DESCRIPTION:   The following lists supported Java APIs for the Patient
 Service Construct (PSC) software package that are used by PATS.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PSC
KEYWORDS: Patient Construct
KEYWORDS: Patient Demographics
KEYWORDS: PATS

NUMBER: 4339                            IA #: 4339
  DATE CREATED: FEB 25, 2004
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: CSLPRPP
  NAME: Prosthetics Purchasing Event    ID: CSLPRPP
 GENERAL DESCRIPTION:   Agreed upon format for handoff and return between VistA
 Prosthetics and CSL for the Prosthetics Purchasing interface event.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Prosthetics
KEYWORDS: Purchasing
COMPONENT/ENTRY POINT: ENT
 COMPONENT DESCRIPTION:   Entry point of Purchasing event routine, Prosthetics
 will call interactively with the variable CSLINP populated with data to be
 passed.  
  
 When the pre-verification status is received from CoreFLS, an interactive call
 to RETURN^RMPR9HOC with variables CSLOUT and CSLRI populated will occur.  
VARIABLES: CSLINP                       TYPE: Input
 VARIABLES DESCRIPTION:   Header: 
  
 CSLINP("H")=Prosthetics Batch ID#_^_Prosthetics Station #_^_Patient IEN_^_PPA
 SSN_^_Vendor Number_^_Vendor Site Code_^_Purchase Card #_^_Bulk Indicator Flag 
  
 CSLINP("H",1)=Source Code_^_Reason Code_^_Purchase Method_^_Possible 
 Competitive Status_^_Preference Program 
  
 Repeating Body: 
  
 CSLINP(line #)=VistA Line IEN_^_Item Number_^_Restricted Flag_^_UoM 
 Code_^_Quantity_^_Unit Price_^_Contract Type_^_Contract Number_^_Ship To Org
 Code_^_Need By Date_^_Direct Delivery Flag 
  
 CSLINP(line #,"ACS")=Accounting Code String 
  
 CSLINP(line #,"SH")=Shipping & Handling Cost_^_Total Cost of PO Line_^_Total
 Cost of PO 
  
 CSLINP(line #,"ID")=Item Description 
  
 CSLINP(line #,"NR")=Note to Receiver 
  
 CSLINP(line #,"NS")=Note to Supplier 
  
 CSLINP(line #,"TPA")=Third Party Address Line 1_^_Line 2_^_City_^_State_^_Zip
 Code 
VARIABLES: CSLOUT                       TYPE: Output
 VARIABLES DESCRIPTION:   (Where CSLRI is the Prosthetics Batch ID # returned
 from CoreFLS) 
  
 CSLOUT(CSLRI)=Prevalidation Result Flag CSLOUT(CSLRI,"ERR",error # 1-N)=Error
 Message #1-N 
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   Prosthetics will use this application agreement to send
 PO data to CoreFLS and receive pre-validation results on those POs.  

NUMBER: 4340                            IA #: 4340
  DATE CREATED: FEB 09, 2004
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: CSLPRIT                      NAME: DBIA4340
  ID: CSLPRIT
 GENERAL DESCRIPTION:   Item Query is a silent query which receive inputs from
 calling program for building a query.  The inputs would be in a local array as
 in OUT shown  below.  CLSPRIT* would use the input to build an HL7 message,
 obtain the message Control ID (MID), and send the message to the CoreFLS
 Oracle database.  Once the query results were returned, CSLPRIT* would build a
 ^XTMP(SUB) with that data.  
    
  STATUS: Active
KEYWORDS: ITEM
KEYWORDS: ITEM QUERY
KEYWORDS: CSLPRIT
COMPONENT/ENTRY POINT: ITEMQ(.CSLOUT)
VARIABLES: ~XTMP(SUB,N,                 TYPE: Output
 VARIABLES DESCRIPTION:   SUB equals the string "CSLPRIT" concatenated with the
 MID 
  (ex. "CSLPRIT51698874").  
    
 An example of the structure of the output array (^XTMP(SUB)) appears below,
 where SUB is as described above and N holds the information for the Nth result
 returned from CoreFLS: 
     
     ^XTMP(SUB,N,"NUMBER")=2345 
     ^XTMP(SUB,N,"DESCRIPTION")=WHEEL CHAIR 
     ^XTMP(SUB,N,"HCPCS CODE")=H1011 
     ^XTMP(SUB,N,"UOM CODE")=EA 
     ^XTMP(SUB,N,"UOM DESCRIPTION")=EACH 
     ^XTMP(SUB,N,"RESTRICTED")=N 
     ^XTMP(SUB,N,"CONTRACT UOM")=EACH 
     ^XTMP(SUB,N,"CONTRACT UNIT PRICE")=300.00 
     ^XTMP(SUB,N,"CONTRACT TYPE")=GSA 
     ^XTMP(SUB,N,"CONTRACT NUMBER")=G1234 
VARIABLES: CSLOUT                       TYPE: Output
 VARIABLES DESCRIPTION:   
  The structure of the local input array (OUT) is as follows: 
     CSLOUT("VENDOR NUMBER") - Vendor number 
     CSLOUT("HCPCS CODE")    - HCPCS Code 
     CSLOUT("ITEM DESCRIPTION") - Item description 
    
 Note that if any of the above nodes are not defined or are set to NULL then 
 those fields will not be used in composing the query.  The data in every field
 that is defined will have the "%" wildcard appended to it.  For example, if
 CSLOUT("VENDOR NUMBER")="A" then the value "A%" will be used in building the
 query.  
   
 CSLOUT("ERROR"): The list below shows the error messages that could be
 returned along with comments.  Note that these error messages, unless
 specified in the comments to the right, will appear as the return value for
 the routine call described above.  
   
 Invalid input parameter list            HL7 error - the input message 
                                         string sent to CoreFLS was invalid 
 Query aborted due to error              HL7 error when initializing HL7 
                                         parameters Message send failure:       
            HL7 error when transmitting 
                                         message to CoreFLS Network Timeout     
                    the query request to CoreFLS 
                                         timed or the check for results 
                                         in ^XTMP timed out 
  Not Found                              no results obtained for query in 
                                         CoreFLS 
  
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Washington/Silver Spring

NUMBER: 4341                            IA #: 4341
  DATE CREATED: FEB 18, 2004
  CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: CSLPRPC*
  NAME: Prosthetics Purchase Order Creation
  ID: CSLPRPC*
 GENERAL DESCRIPTION:   PO Creation is to transmit a message from CoreFLS to
 VistA Prosthetics when a Prosthetics Purchase Order has been created in
 CoreFLS.  There is no user interface in this event.  All data is transmitted
 by CoreFLS.  When the event event occurs, a message is sent to VistA
 Prosthetics via CSL.  Upon receipt,  an Application Acknowledgement ACK or NAK
 is returned to CoreFLS.  
   
 Information is transmitted from CoreFLS in an HL7 format.  Incoming info is 
 read by routine CSLPRPC.  If the Order Status is "NW", a PO is created  in
 CoreFLS successfully.  If the Order Status is "DE", a PO has an error and not
 created in CoreFLS.  
   
 Information from CoreFLS is put into a global ^XTMP for use by VistA
 Prosthetics.  
  
  STATUS: Active
KEYWORDS: PO Creation
KEYWORDS: CoreFLS
KEYWORDS: Prosthetics
COMPONENT/ENTRY POINT: CRT
 COMPONENT DESCRIPTION:   D CRT^CSLPRPC 
VARIABLES: Input                        TYPE: Input
 VARIABLES DESCRIPTION:   Message Control ID - created by the HL7 package and
 is concatenated with the "CSLPRPC" and used as part of the node subscripts and
 node value into the ^XTMP global.  Order Control - PO status as New Order (NW)
 or Data Error (DE) Prosthetics Batch ID - An identifier for Prosthetic batch 
 CoreFLS PO # - An Purchase Order number created by CoreFLS Line IEN - Line
 internal entry number from VistA Prosthetics Order Status - "VAAP", if
 approved by CoreFLS Approved Date - date and time the PO approved by CoreFLS 
 PO Header ID - An identifier for CoreFLS PO header Ship to Location Code - A
 code assigned by user CoreFLS Line Number - Line number in this PO from
 CoreFLS Item Number -  the item number ordered on a specific line of a PO.  
 Contract Number - Contract which item(s) purchase by.  Contract Type - type of
 contract Accounting Code String - the complete Account Classification String
 for the PO.  Quantity - Quantity actually ordered Unit of Measure Code -
 standard code indicating the unit of measure for item UOM Description - the
 spelled out description of the Unit of Measure CoreFLS Line ID - An identifier
 of the specific line item on the PO Purchase card Number - 16 digits,
 specifying the card used for this order  Ship to Org Code - Organization code
 where the order delivered to Vendor Number - the number that identifies a
 specific vendor Vendor Site Code - the site code for the vendor on the PO 
  
 These fields are captured by CSL and formatted into an ^XTMP global as 
  specified.  The CSL routine calls a VistA routine, EN^RMPRCSL2(CSLSUB), 
 passing the complete node structure of "CSLPRPC" concatenated with the Message 
 Control ID, for processing.  
  
VARIABLES: Output                       TYPE: Output
 VARIABLES DESCRIPTION:   ^XTMP("CSLPRPC;"_MID,"ORDER CONTROL")=Order Control
 type 
                               Date^PO Header ID 
 ^XTMP("CSLPRPC;"_MID,"VENDOR","ID")=Vendor #^^^Vendor Site Code 
 ^XTMP("CSLPRPC;"_MID,"ITEM",ITEM #,"ACCOUNTING",1)=Accounting Code String
 (ACS) ^XTMP("CSLPRPC;"_MID,"ITEM",ITEM #,"ACCOUNTING",2)= coreFLS Line
 ID^P-Card #^Line IEN^ Order Control type ^XTMP("CSLPRPC;"_MID,"ITEM",ITEM 
 #,"DELIVERY")=Ship to Org Code^ Ship to Location Code 
 ^XTMP("CSLPRPC;"_MID,"ITEM",ITEM #,"DETAIL",1)=coreFLS Line #^Item #^ Item 
 Description^Quantity^UOM Code^UOM Description^Contract #^Unit Price^Contract 
 Type ^XTMP("CSLPRPC;"_MID,"ITEM",ITEM #,"ERROR")=Error Message from 
 coreFLS^Error Message from CSL ^XTMP("CSLPRPC;"_MID,"ERROR")="DE"   if errors
 found 
  
 The CSL routine evaluates the data sent by CoreFLS for the following structure 
 and content: Vendor ID is not numeric Item Number is not numeric Quantity is 
 not numeric Unit Price is more than five digits after decimal point 
  
 After VistA Prosthetics processes the supplied information, if an error is 
 detected, an error node will be created, ^XTMP("CSLPRPC;"_MID,"ERROR").  
  
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Washington/Silver Spring

NUMBER: 4342                            IA #: 4342
  DATE CREATED: FEB 17, 2004            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUESSO1                      NAME: Visitor
  ID: XUESSO1
 GENERAL DESCRIPTION:   The routine XUESSO1 has entry points used to create a
 Visitor record in the New Person File.  Use of this routine is restricted.  
  STATUS: Active
KEYWORDS: REGISTER ONCE
COMPONENT/ENTRY POINT: $$GET(INDUZ)
 COMPONENT DESCRIPTION:   This entry point uses the current DUZ to collect a
 set of information that can be passed to a remote site to create a Visitor
 record.  The current user must have at least the following information on
 file: Name, Access & Verify codes, SSN (no pseudo), station name & number. The 
 following information is optional: Phone, SecID, & Network Username.  
VARIABLES: INDUZ                        TYPE: Input
 VARIABLES DESCRIPTION:   The requesting user's DUZ 
VARIABLES: $$GET                        TYPE: Output
 VARIABLES DESCRIPTION:   
  SSN^NAME^STATION NAME^STATION NUMBER^DUZ^PHONE^SECID^NETWORK USERNAME 
COMPONENT/ENTRY POINT: $$PUT(DATIN)
 COMPONENT DESCRIPTION:   This entry point uses the output of the $$GET^XUESSO1
 call to create a Visitor record entry in the New Person File.  
VARIABLES: DATIN                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the string from the $$GET call at the
 originating site.  
  SSN^NAME^STATION NAME^STATION NUMBER^DUZ^PHONE^SECID^NETWORK USERNAME 
VARIABLES: $$PUT                        TYPE: Output
 VARIABLES DESCRIPTION:   
  1 == SUCCESS 
  0 == FAILURE 
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: VISTA SERVICES ASSEMBLER
SUBSCRIBING PACKAGE: RPC BROKER
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
  DATE ACTIVATED: SEP 29, 2017

NUMBER: 4343                            IA #: 4343
  DATE CREATED: FEB 13, 2004
  CUSTODIAL PACKAGE: AUTOMATED LAB INSTRUMENTS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: LA7UTL03                     NAME: Surgical Pathology data API
  ID: LA7UTL03
 GENERAL DESCRIPTION:   Returns data for a given Surgical Pathology encounter.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: lab
KEYWORDS: Surgical Pathology
KEYWORDS: API
COMPONENT/ENTRY POINT: SPATH
 COMPONENT DESCRIPTION:   Input: 
         
      LRDFN - Patient Lab DFN                        (Required) 
      IEN   - IEN of SP entry                        (Required) 
      RET   - Array reference for passing back data  (Required) 
      ERR   - Error array to pass back               (Not required) 
         
 Output: 
         
      '0' - If the API encountered an Error along with @ERR array 
         
      '1' - if the API ran successfully and the following data if it exists 
            
       Specimen field .01 of file 63.812.  
       @RET("SPEC",ien of Specimen entry)=Specimen Data 
           
       Clinical History field .01 of sub file 63.813.  
       @RET("CHIS",ien of the Clinical History entry)=Clinical His.  
          
       Pre Operative Diagnosis field .01 of sub file 63.814.  
       @RET@("PREDX",ien of the Pre. Op. Diagnosis entry)=Pre Op Diag.  
         
       Operative Diagnosis field .01 of sub file 63.815.  
       @RET@("OPERDX",ien of the Op. Diagnosis entry)=Op Diag.  
         
       Post Operative Diagnosis field .01 of sub file 63.816.  
       @RET@("POSTDX,ien of the Post. Op Diagnosis entry)=Pst. Op Diag.  
         
       Gross Description field .01 of sub file 63.81.  
       @RET@("GROSSD",ien of the Gross Description entry)=Gross Desc.  
         
       Microscopic Description field .01 of sub file 63.811.  
       @RET@("MICROD",ien of the Microspc. Description entry)=Micro Desc.  
         
       Surgical Pathology field .01 of sub file 63.802.  
       @RET@("SURGP",ien of the Surgical Path. entry)=Surgical Path.  
     
       ICD field .01 of sub file 63.88.  
       @RET@("ICD9",ien of the ICD9 entry)=ICD9 
VARIABLES: LRDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Lab patient DFN.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of record in Surgical Pathiology file.  
VARIABLES: RET                          TYPE: Both
 VARIABLES DESCRIPTION:   Array reference for passing back data.  
VARIABLES: ERR                          TYPE: Both
 VARIABLES DESCRIPTION:   Array reference for passing back any errors that were
 encountered (not required).  
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
  ISC: Hines

NUMBER: 4344                            IA #: 4344
  DATE CREATED: FEB 17, 2004
  CUSTODIAL PACKAGE: AUTOMATED LAB INSTRUMENTS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: LA7UTL02                     NAME: Cytopathology data API
  ID: LA7UTL02
 GENERAL DESCRIPTION:   Returns data for a Cytopathology Encounter.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: lab
KEYWORDS: API
KEYWORDS: Cytopathology
COMPONENT/ENTRY POINT: CYPATH
 COMPONENT DESCRIPTION:   Input: 
        
     LRDFN - Patient Lab DFN                        (Required) 
     IEN   - IEN of CY entry                        (Required) 
     RET   - Array reference for passing back data  (Required) 
     ERR   - Error array to pass back               (Not required) 
         
 Output: 
         
    '0' - If the API encountered an Error along with @ERR array 
         
    '1' - if the API ran successfully and the following data if it exists 
         
   Visit Date field .01 and Accession Number field .06 of file 63.09.  
   @RET("DEMO",ien of visit)=Visit Date^Accession Number 
         
   Specimen field .01 of sub file 63.902.  
   @RET("SPEC",ien of Specimen entry)=Specimen Data 
         
   Clinical History field .01 of sub file 63.913.  
   @RET("CHIS",ien of the Clinical History entry)=Clinical His.  
         
   Pre Operative Diagnosis field .01 of sub file 63.914.  
   @RET@("PREDX",ien of the Pre. Op. Diagnosis entry)=Pre Op Diag.  
         
   Operative Diagnosis field .01 of sub file 63.905. 
   @RET@("OPERDX",ien of the Op. Diagnosis entry)=Op Diag.  
         
   Post Opertive Diagnosis field .01 of sub file 63.906.  
   @RET@("POSTDX,ien of the Post. Op Diagnosis entry)=Pst. Op Diag.  
         
   Cytopathology Diagnosis field .01 of sub file 63.903. 
   @RET@("CYTODX",ien of the Cytopathology Diagnosis entry)=Cyto Dx 
         
   Microscopic Examination field .01 of sub file 63.911.  
   @RET@("MICRO",ien of the Microscopic Examination entry)=Micro. Exam 
         
   ICD field .01 of sub file 63.901.  
   @RET@("ICD9",ien of Cyto ien entry)=ICD9 (external) 
VARIABLES: LRDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Lab DFN of patient.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of record in Cytopathology file.  
VARIABLES: RET                          TYPE: Both
 VARIABLES DESCRIPTION:   Array reference for passing back data.  
VARIABLES: ERR                          TYPE: Both
 VARIABLES DESCRIPTION:   Array reference for passing back any errors that were
 encountered (not required).  
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
  ISC: Hines

NUMBER: 4345                            IA #: 4345
  FILE NUMBER: 664                      GLOBAL ROOT: RMPR(664,
  DATE CREATED: FEB 18, 2004            CUSTODIAL PACKAGE: PROSTHETICS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PROSTHETICS 1358 FIELDS         ID: RMPR(664,
GLOBAL REFERENCE: RMPR(664,'B',
 GLOBAL DESCRIPTION:   $Order() through the "B" cross reference on the DATE
 (#.01) field.  
GLOBAL REFERENCE: RMPR(664,D0,1,
 GLOBAL DESCRIPTION:   $Order() through the internal entry numbers of the ITEM
 subfile (#664.02).  
GLOBAL REFERENCE: RMPR(664,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: VENDOR
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 18                        FIELD NAME: STATION NAME
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: EST. SHIPPING CHARGE
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: ACT. SHIPPING CHARGE
  LOCATION: 0;11                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664,D0,4)
FIELD NUMBER: 7.1                       FIELD NAME: IFCAP ORDER
  LOCATION: 4;6                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: RMPR(664,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: BILLING ITEM
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: UNIT OF ISSUE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 13                        FIELD NAME: CONTRACT #
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: BRIEF DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: UNIT COST
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: QTY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: ACT. UNIT COST
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 16                        FIELD NAME: PSAS HCPCS
  LOCATION: 0;16                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664,'G',
 GLOBAL DESCRIPTION:   $Order() through the "G" cross reference on the PURCHASE
 CARD REFERENCE (#7.5) field.  
GLOBAL REFERENCE: RMPR(664,D0,1,D1,2)
FIELD NUMBER: 15.4                      FIELD NAME: MODEL
  LOCATION: 2;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664,D0,3
FIELD NUMBER: 19                        FIELD NAME: DELIVER TO
  LOCATION: 3;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 21.1                      FIELD NAME: DELIVERY TO ATTENTION
  LOCATION: 3;4                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The purpose of the change is to enable IFCAP users to
 view IFCAP Purchase 
  Orders with Prosthetic Line Item Detail.  IFCAP patch PRC*5.1*103.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 1358
SUBSCRIBING PACKAGE: IFCAP              ISC: Washington/Silver Spring
  DATE ACTIVATED: JUL 13, 2010

NUMBER: 4346                            IA #: 4346
  DATE CREATED: FEB 17, 2004            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFHLU
  NAME: VAFHLU                          ID: VAFHLU
 GENERAL DESCRIPTION:   Valid after patches DG*5.3*508 and SD*5.3*293 are
 released.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HL7
COMPONENT/ENTRY POINT: MAKEIT(SEGNAME,.SEGARR,.FIRST245,.ADTLNODE)
 COMPONENT DESCRIPTION:   Builds an HL7 segment 
  
  Notes  : Validity & existance of input is assumed 
         : Assumes no single element contained in SEGARR is greater 
           than 245 characters 
         : Continuation nodes are added at element boundaries 
VARIABLES: SEGNAME                      TYPE: Input
 VARIABLES DESCRIPTION:   Name of segment being built 
VARIABLES: SEGARR                       TYPE: Input
 VARIABLES DESCRIPTION:   Array continue segment data (pass by value) 
  
  SEGARR(X) = Value for sequence N 
  SEGARR(X,Y) = Repetition Y of sequence X 
  SEGARR(X,Y,Z) = Component Z of repetition Y of sequence X 
  SEGARR(X,Y,Z,A) = Subcomponent A of component Z of 
                    repetition Y of sequence X 
VARIABLES: FIRST245                     TYPE: Both
 VARIABLES DESCRIPTION:   Variable to return first 245 characters of segment in
 (pass by value) 
VARIABLES: ADTLNODE                     TYPE: Both
 VARIABLES DESCRIPTION:   Array for continuation nodes (pass by value) 
  
 ADTLNODE(1..n) = Continuation of segment 
VARIABLES: Assumed Input                TYPE: Input
 VARIABLES DESCRIPTION:   HL7 encoding chars (output of INIT^HLFNC2 or
 INIT^HLTRANS) 

NUMBER: 4347                            IA #: 4347
  DATE CREATED: FEB 17, 2004            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SCMSVUT5
  NAME: SCMSVUT5                        ID: SCMSVUT5
 GENERAL DESCRIPTION:   Supported calls for parsing of an HL7 segment 
  Valid after patches DG*5.3*508 and SD*5.3*293 are released.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HL7
COMPONENT/ENTRY POINT: SEGPRSE(SEGMENT,OUTARR,FS)
 COMPONENT DESCRIPTION:   Parse HL7 segment by field separator 
  
  Notes  : OUTARR is initialized (KILLed) on entry 
         : Assumes SEGMENT and OUTARR are defined and valid 
VARIABLES: SEGMENT                      TYPE: Input
 VARIABLES DESCRIPTION:   Array containing HL7 segment to parse (full global
 ref) 
  
  SEGMENT = First 245 characters of segment 
  SEGMENT(1..n) = Continuation nodes 
       OR 
  SEGMENT(x) = First 245 characters of segment 
  SEGMENT(x,1..n) = Continuation nodes 
VARIABLES: OUTARR                       TYPE: Both
 VARIABLES DESCRIPTION:   Array to put parsed segment into (full global ref) 
  
  OUTARR(0) = Segment name 
  OUTARR(seq#) = Data (first 245 characters) 
  OUTARR(seq#,1..n) Continuation nodes 
VARIABLES: FS                           TYPE: Input
 VARIABLES DESCRIPTION:   HL7 field separator (defaults to ^) (1 character) 
COMPONENT/ENTRY POINT: SEQPRSE(SEQDATA,OUTARR,ENCODE)
 COMPONENT DESCRIPTION:   Parse HL7 sequence by component 
  
  Notes  : OUTARR is initialized (KILLed) on entry 
         : Assumes SEQDATA and OUTARR are defined and valid 
VARIABLES: SEQDATA                      TYPE: Input
 VARIABLES DESCRIPTION:   Array containing seq to parse (full global ref) 
  
  SEQDATA = First 245 characters of sequence 
  SEQDATA(1..n) = Continuation nodes 
       OR 
  SEQDATA(x) = First 245 characters of sequence 
  SEQDATA(x,1..n) = Continuation nodes 
VARIABLES: OUTARR                       TYPE: Both
 VARIABLES DESCRIPTION:   Array to put parsed sequence into (full global ref) 
  
  OUTARR(rep#,comp#) = Data (first 245 characters) 
  OUTARR(rep#,comp#,1..n) = Continuation nodes 
VARIABLES: ENCODE                       TYPE: Input
 VARIABLES DESCRIPTION:   HL7 encoding characters (defaults to ~|\&) (4 chars) 

NUMBER: 4348                            IA #: 4348
  FILE NUMBER: 424                      GLOBAL ROOT: PRC(424,
  DATE CREATED: FEB 17, 2004            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  NAME: 1358 DAILY RECORD ACCESS        ID: PRC(424,
 GENERAL DESCRIPTION:   Fee Basis will be accessing record entries (read-access
 only) contained in the 1358 DAILY RECORD (#424) for use during the conversion
 of FEE BASIS 7078 documents (file 162.4). Conversion program(s) in the Fee
 Basis namespace will be evaluating the data stored in specific record entries
 contained in file 424 to logically decide if a specific record in file 162.4
 should be converted determinant on certain criteria.  
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: FEE BASIS
 SUBSCRIBING DETAILS:   Fee Basis will need to convert specific 7078 documents
 contained in the VA FORM 10-7078 FILE during VAMC cutover to CoreFLS. The 1358
 Daily record contains data associated with the 7078 document, and therefore
 will need to be accessed by the Fee Basis package to fulfill certain
 conversion requirements.  

NUMBER: 4349                            IA #: 4349
  FILE NUMBER: 348.4                    GLOBAL ROOT: RCXV(
  DATE CREATED: FEB 18, 2004            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: AR DATA QUEUE FILE
  ID: RCXV(
GLOBAL REFERENCE: RCXV(D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: BILL NUMBER
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   The Integrated Billing Package desires an Integration
 Agreement with the Accounts Receivable package to add bill number entries in
 to the AR DATA QUEUE File (#348.4) as they are modified in the BILL/CLAIMS
 File (#399).  BILL NUMBER entries will be created with the standard FileMan
 functions; FILE^DICN, UPDATE^DIE, and FILE^DIE.  
  
 The bill number will be retrieved from the ACCOUNTS RECEIVABLE File (#430) by
 a direct global read from the BILL NO. cross-reference. 
 [PRCA(430,"D",BillNumber] 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4350                            IA #: 4350
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: GMV ALLERGY                     REMOTE PROCEDURE: GMV ALLERGY
 GENERAL DESCRIPTION:   
  NAME: GMV ALLERGY 
  TAG: ALLERGY                         
  ROUTINE: GMVUTL3 
  RETURN VALUE TYPE: ARRAY             
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE                     
  WORD WRAP ON: TRUE 
  DESCRIPTION:   
  This remote procedure call retrieves the patient's allergy information.  
   
  This remote procedure call is documented in Integration Agreement 4350.  
  INPUT PARAMETER: DFN                   
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 30              
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  DFN is a pointer to the PATIENT file (#2).  
  RETURN PARAMETER DESCRIPTION:   
  Returns the patient allergy information in the array specified.  
   
   The result array returns: 
    RESULT(n)=This patient has the following allergy(ies): 
        (n+1)=piece1 
   
    where piece1 = the allergy name 
               n = sequential number starting at 1.  
   
  If there is no data, then the following is returned: 
   RESULT(1)=No Allergy Assessment 
   
  Example: 
   > S DFN=134 
   > D ALLERGY^GMVUTL3(.RESULT,DFN) ZW RESULT 
   > RESULT(1)="This patient has the following allergy(ies): " 
   > RESULT(2)="PENICILLIN" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4351                            IA #: 4351
  DATE CREATED: FEB 20, 2004
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                NAME: GMV CHECK DEVICE
 GENERAL DESCRIPTION:   This procedure calls a KERNEL utility to return a list
 of printers the user may select to print output. Returns a maximum of twenty
 entries.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   
  RETURN VALUE TYPE: ARRAY 
  AVAILABILITY: RESTRICTED             
  INACTIVE: ACTIVE 
  WORD WRAP ON: TRUE 
  INPUT PARAMETER: GMVIEN                
    PARAMETER TYPE: LITERAL 
    REQUIRED: YES                        
    SEQUENCE NUMBER: 1 
    DESCRIPTION: The value to begin the search in the Device file (#3.5).  
    Can be null.  
  INPUT PARAMETER: GMVDIR                
    PARAMETER TYPE: LITERAL 
    MAXIMUM DATA LENGTH: 1               
    REQUIRED: YES 
    SEQUENCE NUMBER: 2 
    DESCRIPTION:   Direction of the search (1 = forward, -1 = backwards).  
    If DIR is null, then set to 1.  
  INPUT PARAMETER: GMVRMAR               
    PARAMETER TYPE: LITERAL 
    REQUIRED: YES                        
    SEQUENCE NUMBER: 3 
    DESCRIPTION: Right margin as a single number or range (e.g, 80, 132 
    or "80-132").  
  
  RETURN PARAMETER DESCRIPTION:   
  RESULT(n)=P1^P2^P3^P4^P5^P6 
   
   where n = a sequential number starting with 1 
        P1 = File 3.5  IEN 
        P2 = File 3.5 name (.01 value) 
        P3 = File 3.5 name (.01 value) or flag to indicate last entry in 
             the array 
        P4 = location of terminal 
        P5 = right margin 
        P6 = page length 

NUMBER: 4352                            IA #: 4352
  DATE CREATED: FEB 20, 2004
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                NAME: GMV CLINIC PT
 GENERAL DESCRIPTION:   This procedure lists patients who have an appointment
 for a selected clinic and a given period of time.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   
  RETURN VALUE TYPE: ARRAY 
  AVAILABILITY: RESTRICTED             
  INACTIVE: ACTIVE 
  WORD WRAP ON: TRUE 
  DESCRIPTION: This procedure lists patients who have an appointment for 
  a selected clinic and a given period of time.  
  INPUT PARAMETER: CLIN                  
    PARAMETER TYPE: LITERAL 
    MAXIMUM DATA LENGTH: 30              
    REQUIRED: YES 
    SEQUENCE NUMBER: 1 
    DESCRIPTION:   CLIN contains the name of the selected clinic from the 
    Hospital Location file (#44).  
  INPUT PARAMETER: BDATE                 
    PARAMETER TYPE: LITERAL 
    MAXIMUM DATA LENGTH: 30              
    REQUIRED: YES 
    SEQUENCE NUMBER: 2 
    DESCRIPTION:   BDATE contains TODAY, TOMORROW, YESTERDAY, PAST WEEK or 
    PAST MONTH.  
  RETURN PARAMETER DESCRIPTION:   Returns a list of patient names and DFNs 
  for the selected clinic and the given date span in the array specified.  

NUMBER: 4353                            IA #: 4353
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: GMV CONVERT DATE                REMOTE PROCEDURE: GMV CONVERT DATE
 GENERAL DESCRIPTION:   
  NAME: GMV CONVERT DATE 
  TAG: GETDT                           
  ROUTINE: GMVGETQ 
  RETURN VALUE TYPE: SINGLE VALUE      
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE                     
  WORD WRAP ON: TRUE 
  DESCRIPTION:   
  This remote procedure call converts a user-supplied date/time into VA 
  FileMan's internal and external date format.  
   
  This remote procedure call is documented in Integration Agreement 4353.  
  INPUT PARAMETER: GMRDATE               
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 30              
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  GMRDATE is the user-supplied date/time text.  
  RETURN PARAMETER DESCRIPTION:   
  RESULT=Date in internal FileMan format^Date in external FileMan format 
   
  Example: 
   > S GMRDATE="10/11/2005@10:30AM" 
   > D GETDT^GMVGETQ(.RESULT,GMRDATE) ZW RESULT 
   > RESULT="3051011.103^OCT 11, 2005@10:30:00" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4354                            IA #: 4354
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: GMV GET CATEGORY IEN            REMOTE PROCEDURE: GMV GET CATEGORY IEN
 GENERAL DESCRIPTION:   
  NAME: GMV GET CATEGORY IEN 
  TAG: CATEGORY                        
  ROUTINE: GMVUTL8 
  RETURN VALUE TYPE: SINGLE VALUE      
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE 
  DESCRIPTION:   
  Returns the IEN if the value is found in the GMRV VITAL CATEGORY 
  (#120.53) file.  
   
  This remote procedure call is documented in Integration Agreement 4354.  
  INPUT PARAMETER: GMVCAT                
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 45              
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  GMVCAT = Name of Category (from FILE 120.53) (e.g., METHOD) 
  RETURN PARAMETER DESCRIPTION:   
  Returns the IEN if GMVCAT exists in FILE 120.53 
   
  Example: 
   > S GMVCAT="METHOD" 
   > D CATEGORY^GMVUTL8(.RESULT,GMVCAT) ZW RESULT 
   > RESULT=2 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4355                            IA #: 4355
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: GMV GET CURRENT TIME            REMOTE PROCEDURE: GMV GET CURRENT TIME
 GENERAL DESCRIPTION:   
  NAME: GMV GET CURRENT TIME 
  TAG: TIME                            
  ROUTINE: GMVUTL7 
  RETURN VALUE TYPE: SINGLE VALUE      
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE                     
  WORD WRAP ON: FALSE 
  DESCRIPTION:   
  Gets the current date and time from the server.  
   
  This remote procedure call is documented in Integration Agreement 4355.  
  RETURN PARAMETER DESCRIPTION:   
  Returns current date and time in FileMan internal and external format.  
   
  Example: 
   > D TIME^GMVUTL7(.RESULT) ZW RESULT 
   > RESULT=3051011.143332 
  
 Note: There is an input parameter, P2, listed in the TIME line tag of the 
 GMVUTL7 routine. However, it is not used. It can be set to any value or 
 omitted. It remains for backwards compatibility.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is included in HMP*2.0*2 
  
 **************************************************** 
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                   
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
 ****************************************************

NUMBER: 4356                            IA #: 4356
  DATE CREATED: FEB 20, 2004
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                NAME: GMV GET DATA
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4357                            IA #: 4357
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: GMV GET VITAL TYPE IEN          REMOTE PROCEDURE: GMV GET VITAL TYPE IEN
 GENERAL DESCRIPTION:   
  NAME: GMV GET VITAL TYPE IEN 
  TAG: TYPE                            
  ROUTINE: GMVUTL8 
  RETURN VALUE TYPE: SINGLE VALUE      
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE 
  DESCRIPTION:   
  Returns the IEN if the value is found in the GMRV VITAL TYPE (#120.51) 
  file.  
   
  This remote procedure call is documented in Integration Agreement 4357.  
  INPUT PARAMETER: GMVTYPE               
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 55              
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  GMVTYPE = Name of Vital Type (from FILE 120.51) (e.g., WEIGHT) 
  RETURN PARAMETER DESCRIPTION:   
  Returns the IEN if GMVTYPE exists in FILE 120.51.  
   
  Example: 
   > S GMVTYPE="WEIGHT" 
   > D TYPE^GMVUTL8(.RESULT,GMVTYPE) ZW RESULT 
   > RESULT=9 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4358                            IA #: 4358
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: GMV LATEST VM                   REMOTE PROCEDURE: GMV LATEST VM
 GENERAL DESCRIPTION:   
  NAME: GMV LATEST VM 
  TAG: GETLAT                          
  ROUTINE: GMVGETD 
  RETURN VALUE TYPE: GLOBAL ARRAY      
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE                     
  WORD WRAP ON: TRUE 
  DESCRIPTION:   
  This remote procedure call retrieves the latest vital records for a given 
  patient.  
   
  This remote procedure call is documented in Integration Agreement 4358.  
  INPUT PARAMETER: GMRDFN                
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 10              
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  GMRDFN variable is a pointer to the Patient (#2) file (i.e., DFN).  
  RETURN PARAMETER DESCRIPTION:   
  Returns the name of the global array (i.e., ^TMP($J,"GRPC")) containing 
  the latest vitals for the selected patient.  
   
   The TMP global contains: 
    ^TMP($J,"GRPC",n)=piece1 
   
    where piece1 = is a formatted line of text.  
               n = sequential number starting at 1.  
   
  The formatted line of text includes the vital type, value and unit 
  (U.S.), value and unit (metric), qualifiers, supplemental oxygen, body 
  mass index value, and person who entered the record.  
   
  If there is no data for the patient, the following is returned: 
   ^TMP($J,"GRPC",1)=There are no results to report 
   
  Example: 
   > S GMRDFN=134 
   > D GETLAT^GMVGETD(.RESULT,GMRDFN) ZW RESULT 
   > RESULT="^TMP(539349605,"GRPC")" 
   > D ^%G 
   > Global ^TMP($J,"GRPC" 
   > ^TMP(539349605,"GRPC",1)=Temp.: (08/09/05@08:00)  102 F  (38.9 C)* 
     (ORAL) _VITPROVIDER,ONE 
   >                       2)=Pulse:       (07/14/05@16:33)  55 
     (LEFT,CAROTID,PALPATED,LYING)  _VITPROVIDER,ONE 
   >                       3)=Resp.:       (07/14/05@16:33)  31 
     (SPONTANEOUS,SITTING) _VITPROVIDER,ONE 
   >                       4)=Pulse Ox:    (08/22/05@13:48)  99% with 
     supplemental O2 1 L/min 90% NASAL CANNULA  _VITPROVIDER,ONE 
   >                       5)=B/P:         (09/26/05@11:30)  120/80* (L 
     ARM,SITTING,CAROTID,CALF)  _VITPROVIDER,TWO 
   >                       6)=Ht.: (09/14/05@17:18)  5 ft 6 in (167.64 
     cm) (ACTUAL)  _VITPROVIDER,ONE 
   >                       7)=Wt.: (09/14/05@17:18)  135 lb  (61.36 kg) 
     (ACTUAL,STANDING)  _VITPROVIDER,ONE 
   >                       8)=Body Mass Index:             22  
                           9)=CVP:         (08/22/05@17:09)  15 cmH2O 
     (11.0 mmHg)  _VITPROVIDER,ONE 
                          10)=Circ/Girth:  (07/22/05@10:22)  1 in (2.54 cm) 
     (DRY,ABDO MINAL)  _VITPROVIDER,TWO 
                          11)=Pain: (09/15/05@16:43)  5  _VITPROVIDER,ONE 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   MH added 2/22/2011 

NUMBER: 4359                            IA #: 4359
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: GMV VITALS/CAT/QUAL             REMOTE PROCEDURE: GMV VITALS/CAT/QUAL
 GENERAL DESCRIPTION:   
  NAME: GMV VITALS/CAT/QUAL 
  TAG: GETVITAL                        
  ROUTINE: GMVUTL7 
  RETURN VALUE TYPE: ARRAY             
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE                     
  WORD WRAP ON: TRUE 
  DESCRIPTION:   
  Returns all qualifier information for the vital types selected.  
   
  This remote procedure call is documented in Integration Agreement 4359.  
  INPUT PARAMETER: GMVLIST               
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 60              
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  A list of vital type abbreviations (FILE 120.51, Field 1) separated by 
  up-arrows (e.g., "HT^WT" for height and weight). When the value is null, 
  all qualifier information will be returned for all vital types.  
  RETURN PARAMETER DESCRIPTION:   
  Returns the qualifier information for the selected vital types in the 
  array specified. Includes the abnormal high and low values for the vital 
  type, if any.  
   
  The result array contains: 
  
   RESULT(n)=piece1^piece2^piece3^piece4^piece5^piece6^piece7^piece8^piece9 
   RESULT(n.nnn)=pieceA^pieceB^pieceC^pieceD 
   
    where n is a sequential number starting with 1 
          piece1 = V for vital type 
          piece2 = FILE 120.51 IEN for this vital type 
          piece3 = vital type name (FILE 120.51, Field .01) 
          piece4 = Abbreviation (FILE 120.51, Field 1) 
          piece5 = PCE Abbreviation (FILE 120.51, Field 7) 
          piece6 = If vital type is Blood Pressure this is the 
                   abnormal systolic high value (File 120.57, Field 5.7).  
                   If vital type is Temperature, this is the abnormal high 
                   value (File 120.57, Field 5.1) 
                   If vital type is Respiration, this is the abnormal high 
                   value (File 120.57, Field 5.5) 
                   If vital type is Pulse, this is the abnormal high value 
                   (File 120.57, Field 5.3) 
                   If vital type is Central Venous Pressure, this is the 
                   abnormal high value (File 120.57, Field 6.1) 
          piece7 = If vital type is Blood Pressure this is the 
                   abnormal diastolic high value (File 120.57, Field 5.71).  
                   If vital type is Temperature, this is the abnormal low 
                   value (File 120.57, Field 5.2) 
                   If vital type is Respiration, this is the abnormal low 
                   value (File 120.57, Field 5.6) 
                   If vital type is Pulse, this is the abnormal low value 
                   (File 120.57, Field 5.4) 
                   If vital type is Central Venous Pressure, this is the 
                   abnormal low value (File 120.57, Field 6.2) 
          piece8 = If vital type is Blood Pressure this is the 
                   abnormal systolic low value (File 120.57, Field 5.8).  
                   If vital type is Central Pressure, this is the abnormal 
                   O2 saturation (File 120.57, Field 6.3) 
          piece9 = If vital type is Blood Pressure this is the 
                   abnormal diastolic low value (File 120.57, Field 5.81).  
   
   RESULT(n.nnn)=pieceA^pieceB^pieceC^pieceD 
    where pieceA = C for CATEGORY or Q for QUALIFIER 
   
    if pieceA is C, then  
          pieceB = FILE 120.53 IEN for this category 
          pieceC = category name (FILE 120.53, Field .01) 
          pieceD = null 
   
    if pieceB is Q, then 
          pieceB = FILE 120.52 IEN for this qualifier 
          pieceC = qualifier name (FILE 120.52, Field .01) 
          pieceD = synonym (FILE 120.52, Field .02) 
   
  Example: 
   > S GMVLIST="HT^WT"                            
   > D GETVITAL^GMVUTL7(.RESULT,GMVLIST) ZW RESULT 
   > RESULT(1)="V^8^HEIGHT^HT^HT^" 
   > RESULT(1.001)="C^4^QUALITY" 
   > RESULT(1.002)="Q^42^ACTUAL^A" 
   > RESULT(1.003)="Q^43^ESTIMATED^E" 
   > RESULT(1.004)="Q^107^Stated^St" 
   > RESULT(2)="V^9^WEIGHT^WT^WT^" 
   > RESULT(2.001)="C^2^METHOD" 
   > RESULT(2.002)="Q^39^OTHER^Oth" 
   > RESULT(2.003)="Q^50^SITTING^Si" 
   > RESULT(2.004)="Q^51^STANDING^St" 
   > RESULT(2.005)="C^4^QUALITY" 
   > RESULT(2.006)="Q^42^ACTUAL^A" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP*2.0*2 
  
 **************************************************** 
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                   
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
 ****************************************************

NUMBER: 4360                            IA #: 4360
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: GMV MANAGER                     REMOTE PROCEDURE: GMV MANAGER
 GENERAL DESCRIPTION:   
  NAME: GMV MANAGER 
  TAG: RPC                             
  ROUTINE: GMVRPCM 
  RETURN VALUE TYPE: GLOBAL ARRAY      
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE                     
  WORD WRAP ON: TRUE 
  DESCRIPTION:   
  Performs many functions for the Manager module.  
   
  This remote procedure call is documented in Integration Agreement 4360.  
  INPUT PARAMETER: OPTION                
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 10              
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Routine tag line in GMVRPCM to call.  
  INPUT PARAMETER: DATA                  
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 100             
  REQUIRED: YES 
  SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  Other data as required for the call.  
  RETURN PARAMETER DESCRIPTION:   
  This remote procedure call performs various actions such as building 
  selection lists and modifying package parameters. The entry point is 
  RPC^GMVRPCM. It has input parameters of RESULTS, OPTION and DATA (ex: 
  RPC^GMVRPCM(.RESULTS,OPTION,DATA). 
   
  The RESULTS variable will contain the ^TMP("GMVMGR",$J) global array 
  reference. The ^TMP("GMVMGR",$J) global array contains the results.  
   
  The OPTION variable identifies a line label in the GMVRPCM routine 
  that will be invoked to process the call.  
   
  The DATA variable contains any additional values needed by the OPTION 
  variable to process the call.  
   
   
  1) When the OPTION value is ADDQUAL, this RPC will link a GMRV VITAL 
  QUALIFIER (#120.52) file entry to a GMRV VITAL TYPE (#120.51) file 
  entry. 
    
  The DATA value is a three part value separated by semi-colons(;). The 
  first value is the FILE 120.51 internal entry number (IEN). The second 
  value is the GMRV VITAL CATEGORY (#120.53) IEN. The third value is the 
  GMRV VITAL QUALIFIER (#120.52).  
    
  Example: 
   
   > S DATA="1;1;1" 
   > S OPTION="ADDQUAL" 
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=1^Qualifier Assigned 
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned. 
   
   
  2) When the OPTION value is DELQUAL, this RPC will unlink a qualifier to 
  a GMRV VITAL TYPE (#120.51) file entry. 
    
  The DATA value is a three part value separated by semi-colons. The first 
  value is the FILE 120.51 internal entry number (IEN). The second value 
  is the GMRV VITAL CATEGORY (#120.53) IEN. The third value is the GMRV 
  VITAL QUALIFIER (#120.52) IEN.  
  
  Example: 
   > S DATA="1;1;1"         
   > S OPTION="DELQUAL"                        
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=1^Qualifier removed.  
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned.  
   
    
  3) When the OPTION value is DELTEMP, this RPC will delete a data input 
  template definition.  
    
  The DATA value is a two part value separated by a caret (^). The first 
  value is the ENTITY value. See IA #2263 for a list of entity values.  
  The second value is the name of the data input template.  
    
  Example: 
   > S DATA="USR^PAIN ONLY" 
   > S OPTION="DELTEMP" 
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=1^Template Removed. 
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned.  
   
   
  4) When the OPTION value is GETCATS, this RPC will return a list of 
  qualifiers (FILE 120.52) associated with a vital type (FILE 120.51). 
    
  The DATA value is a one part value. It is a pointer value to FILE 120.51 
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=piece1^piece2 
   ^TMP("GMVMGR",$J,n)=piece3^piece4^piece5 
  
   where piece1 = number of categories (FILE 120.53) associated with this 
                  vital type 
         piece2 = vital type name 
         piece3 = category IEN (FILE 120.53) 
         piece4 = category name (FILE 120.53, Field .01) 
         piece5 = qualifier names (FILE 120.52, Field .01) separated by a 
                  comma and space 
              n = sequential number starting with 1 
   
  Example: 
   > S DATA="21" 
   > S OPTION="GETCATS" 
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=1^PULSE OXIMETRY 
                          1)=2^METHOD^AEROSOL/HUMIDIFIED MASK, CPAP, FACE 
     TENT, L ARM, MASK, NASAL CANNULA, NON RE-BREATHER, PARTIAL 
     RE-BREATHER, ROOM AIR, T-PIECE, TRACHEOSTOMY COLLAR, VENTILATOR, 
     VENTURI MASK 
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned.  
   
   
  5) When the OPTION value is GETDATA, this RPC will return the value of 
  the entry you specify.  
    
  The DATA value is a three part value. The first part is the file number. 
  The second part is the IEN number of the entry. The third part is the 
  field number.  
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=external value of the field 
   
  Example: 
   > S DATA="120.51^1^1" 
   > D RPC(.RESULT,"GETDATA",DATA) ZW RESULT             
   > RESULT="^TMP("GMVMGR",539339804)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539339804,0)=BP 
          
  If a value cannot be found, then a null value is returned.  
   
   
  6) When the OPTION value is GETDEF, this RPC will return default template 
  names. 
    
  The DATA value is a one part value. If it is null, then all default 
  templates for that user will be returned. 
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=piece1 
   ^TMP("GMVMGR",$J,n)=piece2^piece3 
   
   where piece1 = number of templates found 
         piece2 = an IEN value, a semi-colon, and a global reference 
         piece3 = template name 
              n = sequential number starting with 1 
   
  Example A: 
   > S DATA="" 
   > S OPTION="GETDEF" 
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=4 
                             1)=125;SC(^WARD 10A 
                             2)=334;DIC(4.2,^TEST 
                             3)=4601;VA(200,^Height ONLY 
                             4)=547;VA(200,^All Vital Signs 
   
  If the DATA value is an entity value (see IA 2263 for a list of entity 
  values), then the default template name for that entity will be returned.  
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=template name 
   
  Example B: 
   > S DATA="USR"                                
   > S OPTION="GETDEF"                           
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=MY DEFAULT 
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned.  
   
    
  7) When the OPTION value is GETHILO, this RPC will return the abnormal 
  high or low value for a vital type.  
   
  The DATA value is a one part value which identifies a field number in 
  the GMRV VITALS PARAMETERS (#120.57) field.  
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=field value 
   
  Example: 
   > S DATA=5.2 
   > S OPTION="GETHILO" 
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=94 
   
  A zero is returned if there is no value in the field. 
   
   
  8) When the OPTION value is GETLIST, this RPC returns a list of entries 
  for the file number specified.  
   
  The DATA value is a one part value. It is a file number.  
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=piece1^piece2 
   ^TMP("GMVMGR",$J,n)=piece3^piece4 
   
   where piece1 = number of entries returned 
         piece2 = file name [not returned in all cases] 
         piece3 = file number, a semi-colon and record IEN 
         piece4 = the .01 value of the record 
              n = sequential number starting with 1 
   
  Examples: 
   Retrieve a list of wards.  
   > S DATA=42 
   > S OPTION="GETLIST" 
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539363784)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539363784,0)=26^WARD LOCATION 
                             1)=42;14^10A 
                             n)=42;15^10B 
                             26)=42;39^10Z 
   
   Retrieve a list of clinics.  
   > S DATA=44 
   > S OPTION="GETLIST"              
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539363784)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539363784,0)=61 
                             1)=44;6^HOUSE/A 
                             n)=44;8^HOUSE/C 
                             61)=44;39^HOUSE/ZZ 
   
   Retrieve a list vital types.  
   > S DATA=120.51 
   > S OPTION="GETLIST"              
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539363784)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539363784,0)=10^GMRV VITAL TYPE 
                             1)=120.51;1^BLOOD PRESSURE 
                             N)=120.51;19^CENTRAL VENOUS PRESSURE 
                             10)=120.51;9^WEIGHT 
   
   Retrieve a list of qualifiers.  
   > S DATA=120.52 
   > S OPTION="GETLIST"              
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539363784)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539363784,0)=80^GMRV VITAL QUALIFIER 
                             1)=120.52;74^ABDOMINAL 
                             n)=120.52;42^ACTUAL 
                             80)=120.52;99^WRIST 
   
   Retrieve a list of CPRS teams.  
   > S DATA=100.21 
   > S OPTION="GETLIST"              
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539363784)" 
   > D ^%G                                       
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539363784,0)=103 
                             1)=100.21;28^1AS 
                             n)=100.21;60^1ASO 
                             103)=100.21;96^consult team 
   
   Retrieve a list of nursing units.  
   > S DATA=211.4 
   > S OPTION="GETLIST"               
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539363784)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539363784,0)=21 
                             1)=211.4;7^10E 
                             n)=211.4;17^10W 
                             21)=211.4;9^SICU 
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned.  
   
   
  9) When the OPTION value is GETQUAL, this RPC returns a list of 
  qualifiers associated with this vital type.  
   
  The DATA value is a two part value separated by a semi-colon. The first 
  part is vital type (FILE 120.51) IEN. The second part is a category (FILE 
  120.53) IEN.  
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=piece1^piece2 
   ^TMP("GMVMGR",$J,n)=piece3^piece4 
   
    where piece1 = number of entries found 
          piece2 = category name (FILE 120.53, Field .01) 
          piece3 = qualifier IEN 
          piece4 = qualifier name (FILE 120.52, Field .01) 
               n = sequential number starting with 1 
   
  Example: 
   > S DATA="1;1",OPTION="GETQUAL" 
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=6^LOCATION 
                             1)=139^Test Qualifier 
                             2)=53^FEMORAL 
                             3)=2^L ARM 
                             4)=4^L LEG 
                             5)=24^PERIPHERAL 
                             6)=1^R ARM 
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned.  
   
   
  10) When the OPTION value is GETTEMP, this RPC will return a list data 
  input templates defintions.  
   
  The DATA value is a two part value separated by a caret. The first part 
  is an entity value. See IA 2263 for a list of entities. The second part 
  is a data input template name.  
   
  When DATA is null, all data input template definitions are returned.  
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=piece1 
   ^TMP("GMVMGR",$J,n)=piece2^piece3^piece4^piece5^piece6 
   
    where piece1 = number of entries returned 
          piece2 = 1, 2, 3, or 4. (1 = Domain, 2 = Institution, 3 = 
                   Hospital location and 4 = New Person) 
          piece3 = file IEN, a semi-colon and global reference 
          piece4 = Field .01 value of the file specified in piece3 
          piece5 = template name 
          piece6 = template description text, a bar, vital type IEN (FILE 
  120.51), a colon, a metric flag (0=U.S. and 1=metric), category IEN 
  (FILE 120.53), a coma, and a qualifier IEN (FILE 120.52), a tilde 
  indicates additional category and qualifier combinations for the vital 
  type. A semi-colon indicates the start of the next vital type.  
               n = sequential number starting with 1 
   
  Example: 
   > S DATA="USR",OPTION="GETTEMP"               
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=1 
                             1)=4^547;VA(200,^VITUSER,ONE^MY DEFAULT^ALL 
                                VITALS|1:0:1,2~2,59~3,50;20:1| 
   
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned.  
   
   
  11) When the OPTION value is LOOKUP, this RPC will do a file lookup 
   
  The DATA value is a three part value separated by a caret. The first 
  part is a file number. The second part is a value to look up. The third 
  part is the field or fields to do the look up on. If the third piece is 
  not defined, the lookup is done on the .01 field of the file.  
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=piece1 
   ^TMP("GMVMGR",$J,n)=piece2^piece3 
   
    where piece1 = number of entries found 
          piece2 = file number, a semi-colon and record IEN 
          piece3 = field value 
   
  Example: 
   > S DATA="44^OUTPAT^.01",OPTION="LOOKUP"      
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539359648)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539359648,0)=3 
                             1)=44;75^OUTPATIENT NUC MED 
                             2)=44;74^OUTPATIENT RADIOLOGY 
                             3)=44;80^OUTPATIENT ULTRASOUND 
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned.  
   
   
  12) When the OPTION value is NEWQUAL, this RPC will always return an 
  error message instructing the user to use the New Term Rapid Turnaround 
  process.  
   
  The DATA value is always null.  
   
  Example: 
   > S DATA="" 
   > S OPTION="NEWQUAL" 
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=-1^Use the New Term Rapid Turnaround 
     (NTRT) process to add qualifiers 
   
    
  13) When the OPTION value is NEWTEMP, this RPC will file a new data 
  input template.  
   
  The DATA value is a three part value separated by a caret. The first 
  part is an entity. See IA 2263 for a list of entities. The second part is 
  the name of the data input template. The third part is the description 
  text. If the third part is null, the template description will default to 
  "No Description".  
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=piece1^piece2^piece3^piece4 
   
    where piece1 = 1, 2, 3, or 4 (1 = DOMAIN (#4.2), 2 = INSTITUTION (#4), 
                   3 = HOSPITAL LOCATION, and 4 = NEW PERSON) 
          piece2 = IEN, a semi-colon, and global reference (e.g., 
                   3;DIC(4.2) 
          piece3 = the .01 field value for the record in piece2 
          piece4 = data input name 
   
  Example: 
   > S DATA="USR^1 EAST^All Vital Types" 
   > S OPTION="NEWTEMP" 
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539343036)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539343036,0)=4^547;VA(200,^VITUSER,ONE^1 EAST 
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned.          
    
   
  14) When the OPTION value is RENTEMP, this RPC will rename a data input 
  template. 
   
  The DATA value is a three part value separated by a caret. The first 
  part is an entity. See IA 2263 for a list of entities. The second part is 
  the current template name. The third part is the new name of the 
  template.  
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=1^Renamed 
           
  Example: 
   > S DATA="USR^FRANK'S DEFAULT^MY DEFAULT" 
   > S OPTION="RENTEMP" 
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=1^Renamed 
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned. 
    
   
  15) When the OPTION value is SETDATA, this RPC always returns an error 
  message that instructs the user to use the New Term Rapid Turnaround 
  process.  
    
  The DATA value is null.  
    
  Example: 
   > S DATA="" 
   > S OPTION="SETDATA"                  
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=-1^Use the New Term Rapid Turnaround 
     (NTRT) process to add qualifiers 
   
    
  16) When the OPTION value is SETDEF, this RPC will set that data input 
  template as a default.  
    
  The DATA value is a two part value separated by a caret. The first part 
  is an entity. See IA 2263 for a list of entities. The second part is the 
  name of the template that will become the default template.  
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=1^Set As Default 
   
  Example: 
   > S DATA="USR^FRANK'S LIST" 
   > S OPTION="SETDEF" 
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=1^Set As Default.  
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned.  
    
   
  17) When the OPTION value is SETHILO, this RPC will set the high and low 
  abnormal values for a vital type.  
    
  The DATA value is a two part value separated by a caret. The first part 
  is a field number in the GMRV VITALS PARAMETERS (#120.57) file. The 
  second part is the value that field should be set to.  
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=1^Update Complete.  
   
  Example: 
   > S DATA="5.1^102",OPTION="SETHILO" 
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=1^Update Complete.  
  
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned.  
    
   
  18) When the OPTION value is SETTEMP, this RPC will save the input 
  template definition.  
    
  DATA is a three part value separated by a caret. The first part is 
  an entity. See IA 2263 for a list of entities. The second part is the 
  template name. The third part is the template definition.  
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=1^Template Saved.  
    
  Example: 
   > S DATA="USR^ONE VITAL TYPE ONLY^CONTAINS ONLY ONE VITAL 
     TYPE|2:0:1,102"| 
   > S OPTION="SETTEMP" 
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539356158)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539356158,0)=1^Template Saved.  
   
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned.  
   
    
  19) When the OPTION value is VALID, this RPC will validate data.  
   
  DATA is a four part value separated by a caret. The first part is the 
  a file number. The second part is a record number. The third part is a 
  field number. The fourth part is the value to validate.  
   
  The TMP global contains: 
   ^TMP("GMVMGR",$J,0)=1^Valid Data 
   
  Example: 
   > S DATA="120.5^8864^.01^3051012.1034",OPTION="VALID" 
   > D RPC^GMVRPCM(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVMGR",539343036)" 
   > D ^%G 
   > Global ^TMP("GMVMGR",$J 
   > ^TMP("GMVMGR",539343036,0)=1^Valid Data 
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES

NUMBER: 4361                            IA #: 4361
  DATE CREATED: FEB 20, 2004
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                NAME: GMV NUR UNIT PT
 GENERAL DESCRIPTION:   This procedure returns a list of active patients for a
 nursing location.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4362                            IA #: 4362
  DATE CREATED: FEB 20, 2004
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: GMV PTSELECT                    REMOTE PROCEDURE: GMV PTSELECT
 GENERAL DESCRIPTION:   Used as a method of processing a patient DFN and
 returning all warnings and notices (i.e. sensitivity or same last 4 of SSN) to
 the client application for processing.  Also includes a call to log access of 
 sensitive patients to the DG SECURITY LOG file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES

NUMBER: 4363                            IA #: 4363
  DATE CREATED: FEB 20, 2004
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                NAME: GMV ROOM/BED
 GENERAL DESCRIPTION:   This procedure extracts room/bed information from
 Room-Bed file (#405.4) for a given MAS ward.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4364                            IA #: 4364
  DATE CREATED: FEB 20, 2004
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                NAME: GMV TEAM PATIENTS
  REMOTE PROCEDURE: GMV TEAM PATIENTS
 GENERAL DESCRIPTION:   This procedure retrieves patients assigned to a given
 team.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 4365                            IA #: 4365
  DATE CREATED: FEB 20, 2004
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                NAME: GMV WARD PT
  REMOTE PROCEDURE: GMV WARD PT
 GENERAL DESCRIPTION:   This procedure lists patients registered on a
 particular MAS ward.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 4366                            IA #: 4366
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: GMV USER                        REMOTE PROCEDURE: GMV USER
 GENERAL DESCRIPTION:   
  NAME: GMV USER 
  TAG: RPC                             
  ROUTINE: GMVRPCU 
  RETURN VALUE TYPE: GLOBAL ARRAY      
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE                     
  WORD WRAP ON: TRUE 
  DESCRIPTION:   
  Retrieves data about the user (e.g., parameter settings).  
   
  This remote procedure call is documented in Integration Agreement 4366.  
  INPUT PARAMETER: OPTION                
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 10              
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Routine tag line to call in GMVRPCU.  
  INPUT PARAMETER: DATA                  
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 100             
  REQUIRED: YES 
  SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  Other data as required for the call.  
  RETURN PARAMETER DESCRIPTION:   
  This Remote Procedure Call (RPC) performs various actions focusing on 
  the user. The entry point is RPC^GMVRPCU. It has input parameters of 
  RESULTS, OPTION and DATA (e.g., RPC^GMVRPCU(RESULTS,OPTION,DATA)).  
   
  The RESULTS variable contains the results of the call or the location 
  where the results can be found.  
   
  The OPTION variable identifies another entry point in the GMVRPCU 
  routine that is invoked to process the call.  
   
  The DATA variable contains any values needed by the OPTION variable to 
  process the call.  
   
  1) When the OPTION value is SETPAR, this RPC will set and/or delete the 
  value of a GMV USER DEFAULTS setting (e.g., the user's default template).  
   
  The DATA value is a two part value separated by a caret. The first part  
  is name of a setting. The second part is the value of the setting. If 
  the second part is null, the existing value of the setting is deleted.  
   
  The TMP global contains: 
   ^TMP("GMVUSER",$J,0)=1^Parameter set.  
   or 
   ^TMP("GMVUSER",$J,0)=1^Parameter cleared 
   
  Example: 
   > S DATA="DefaultTemplate^547;VA(200,|MY DEFAULT",OPTION="SETPAR"| 
   > D RPC^GMVRPCU(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVUSER",539374023)" 
   > D ^%G 
   > Global ^TMP("GMVUSER",$J 
   > ^TMP("GMVUSER",539374023,0)=1^Parameter set.  
   
  If an error is encountered, a "-1" followed by a caret and the error 
  message text (i.e., -1^error message) is returned.  
   
   
   
  2) When the OPTION value is GETPAR, this RPC will return the value of the 
  GMV USER DEFAULTS setting specified in the DATA value.  
   
  The DATA value is a one part value. It is the name of a setting (e.g., 
  the user's default template).  
   
   The TMP global contains: 
    ^TMP("GMVUSER",$J,0)=value of setting or null 
   
  Example: 
   > S DATA="DefaultTemplate",OPTION="GETPAR"       
   > D RPC^GMVRPCU(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVUSER",539374023)" 
   > D ^%G 
   > Global ^TMP("GMVUSER",$J 
   > ^TMP("GMVUSER",539374023,0)=547;VA(200,|ONE VITAL TYPE ONLY| 
   
   
  3) When the OPTION value is SIGNON, this RPC will return information 
  about the user who is currently signed onto the system.  
   
  The DATA value is not used. The user's IEN (i.e., DUZ) to the NEW PERSON 
  (#200) file value must be defined when this call is made.  
   
  The RESULT variable will return the following array: 
    RESULT(0)=NEW PERSON (#200) file internal entry number (DUZ) 
    RESULT(1)=User's name (FILE 200, Field .01) 
    RESULT(2)=Domain (FILE 4.2) internal entry number 
    RESULT(3)=Domain name (FILE 4.2, Field .01) 
    RESULT(4)=Institution (FILE 4) internal entry number the user is signed 
               into (i.e., DUZ(2)) 
    RESULT(5)=Institution name (FILE 4, Field .01) 
    RESULT(6)="0" or "1". "1" indicates the user has the GMV MANAGER or 
               programmer key. "0" indicates the user has neither key.  
    RESULT(7)=The user's title (FILE 200, Field 8) 
    RESULT(8)=This value is always null.  
    RESULT(9)=Number of seconds the system will wait for a response from 
               the user (i.e., DTIME). The default time is 300 seconds.  
    RESULT(10)=INSTITUTION (#4) file IEN^FILE 4 external value^station 
                number (e.g., 499^SUPPORT ISC^499).  
   
  Example: 
   > S OPTION="SIGNON" 
   > D RPC(.RESULT,OPTION) ZW RESULT 
   > RESULT="^TMP("GMVUSER",539375907)" 
   > D ^%G 
   > Global ^TMP("GMVUSER",$J 
   > ^TMP("GMVUSER",539375907,0)=547 
                              1)=VITUSER,ONE 
                              2)=334 
                              3)=DEV.DEV.DNS 
                              4)=499 
                              5)=SUPPORT ISC 
                              6)=1 
                              7)=PROGRAMMER 
                              8)= 
                              9)=9999 
                             10)=499^SUPPORT ISC^499 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4367                            IA #: 4367
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: GMV PARAMETER                   REMOTE PROCEDURE: GMV PARAMETER
 GENERAL DESCRIPTION:   
  NAME: GMV PARAMETER 
  TAG: RPC                             
  ROUTINE: GMVPAR 
  RETURN VALUE TYPE: GLOBAL ARRAY      
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE 
  WORD WRAP ON: TRUE 
  DESCRIPTION:   
  Sets and retrieves parameter values used by the graphical user interface.  
   
  This remote procedure call is documented in Integration Agreement 4367.  
  INPUT PARAMETER: OPTION                
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 10              
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Routine tag line to call.  
  INPUT PARAMETER: ENT                   
  PARAMETER TYPE: LITERAL 
  SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  The entity value to use. See Integration Agreement 2263 and FILE 8989.518 
  for a list of entity values.  
  INPUT PARAMETER: PAR                   
  PARAMETER TYPE: LITERAL 
  SEQUENCE NUMBER: 3 
  DESCRIPTION:   
  The parameter value to use. See FILE 8989.51 for a list of parameter 
  values. This value must start with the letters "GMV" (no quotes).  
  INPUT PARAMETER: INST                  
  PARAMETER TYPE: LITERAL 
  SEQUENCE NUMBER: 4 
  DESCRIPTION:   
  The instance to use. 
  INPUT PARAMETER: VAL                   
  PARAMETER TYPE: LITERAL 
  SEQUENCE NUMBER: 6 
  DESCRIPTION:   
  The value assigned to a parameter. Values are stored in FILE 8989.5.  
  RETURN PARAMETER DESCRIPTION:   
  This remote procedure call sets and retrieves parameter settings that 
  are used in the graphical user interface.  
   
  The entry point is RPC^GMVPAR.. It has input parameters of RESULTS, 
  OPTION, ENT, PAR, INST and VAL (ex: 
  RPC^GMVPAR(RESULTS,OPTION,ENT,PAR,INST,VAL).  
   
  The RESULTS variable contains the results of the call or the location 
  where the results can be found.  
   
  The OPTION variable identifies the entry point in the GMVPAR routine 
  that will be invoked to process the call.  
   
  If an error occurrs, the ^TMP global contains: 
   ^TMP($J,0)=-1^error message text 
   
           
  1) When the OPTION value is DELPAR, this RPC deletes the value for the 
  instance, parameter and entity specified.  
   
  The TMP global contains: 
   ^TMP($J,0)=1^Instance deleted 
   
  Example: 
   > S OPTION="DELPAR",ENT="SYS",PAR="GMV DLL VERSION" 
   > S INST="GMV_VITALSVIEWENTER.DLL:v. 07/21/05 10:34" 
   > D RPC^GMVPAR(.RESULT,OPTION,ENT,PAR,INST) ZW RESULT                   
   > RESULT="^TMP(538999278)" 
   > D ^%G 
   > Global ^TMP($J 
   > ^TMP(538999278,0)=1^Instance deleted 
   
   
  2) When the OPTION value is ENTVAL, this RPC returns the external value 
  of the entity specified.  
   
  The TMP global contains: 
   TMP($J,0)=external value 
                           
  Example: 
   > S OPTION="ENTVAL",ENT="USR"              
   > D RPC(.RESULT,OPTION,ENT) ZW RESULT 
   > RESULT="^TMP(538993252)" 
   > D ^%G 
   > Global ^TMP($J 
   > ^TMP(538993252,0)=TRAXLER,FRANK 
   
   
  3) When the OPTION value is GETLST, this RPC returns a list of instances 
  and their values for the parameter and entity specified.  
   
  The TMP global contains: 
   ^TMP($J,0)=piece1 
   ^TMP($J,n)=piece2^piece3 
   
    where piece1 = number of entries returned 
          piece2 = instance name 
          piece3 = instance value 
               n = sequential number starting with 1 
   
   
  Example: 
   > S OPTION="GETLST",ENT="USR",PAR="GMV USER DEFAULTS" 
   > D RPC(.RESULT,OPTION,ENT,PAR) ZW RESULT 
   > RESULT="^TMP(538993252)" 
   > D ^%G 
   > Global ^TMP($J 
   > ^TMP(538993252,0)=44 
                    1)=DefaultTemplate^547;VA(200,|MY DEFAULT| 
                    n)=UNIT_INDEX^0 
                    44)=WARD_INDEX^-1 
   
          
  4) When the OPTION value is GETPAR, this RPC will get the value for the 
  instance, parameter and entity specified. 
   
  The TMP global contains: 
   ^TMP($J,0)=piece1 
   
   where piece1 = value 
   
  Example: 
   > S ENT="USR",PAR="GMV USER DEFAULTS",INST="DefaultTemplate"   
   > S OPTION="GETPAR" 
   > D RPC(.RESULT,OPTION,ENT,PAR,INST) ZW RESULT              
   > RESULT="^TMP(538993252)" 
   > D ^%G 
   > Global ^TMP($J 
   > ^TMP(538993252,0)=547;VA(200,|MY DEFAULT| 
   
   
  5) When the OPTION value is SETPAR, this RPC set the value of an 
  instance for the instance, parameter and entity specified.  
   
  The TMP global contains: 
   ^TMP($J,0)=1^Parameter updated 
   
  Example: 
   > S OPTION="SETPAR",ENT="USR",PAR="GMV USER DEFAULTS",INST="SearchDelay" 
   > S VAL=1.5 
   > D RPC^GMVPAR(.RESULT,OPTION,ENT,PAR,INST,VAL) ZW RESULT 
   > RESULT="^TMP(538999278)" 
   > D ^%G 
   > Global ^TMP($J 
   > ^TMP(538999278,0)=1^Parameter updated 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4368                            IA #: 4368
  DATE CREATED: MAR 23, 2007            CUSTODIAL PACKAGE: 759
  USAGE: Private                        TYPE: Other
  NAME: Person Service Patient Lookup Java APIs
 GENERAL DESCRIPTION:   The following lists supported Java APIs for the Patient
 Service Lookup (PSL) software package that are used by PATS.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PSL
KEYWORDS: PATS
KEYWORDS: Patient Lookup

NUMBER: 4369                            IA #: 4369
  DATE CREATED: MAR 23, 2007            CUSTODIAL PACKAGE: 763
  USAGE: Private                        TYPE: Other
  NAME: Standard Data Service Java APIs - used by PATS
 GENERAL DESCRIPTION:   The following lists supported Java APIs for the
 Standard Data Service (SDS) software package that are used by PATS.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: SDS
KEYWORDS: PATS

NUMBER: 4370                            IA #: 4370
  DATE CREATED: MAR 28, 2007            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCAAPI
  NAME: AR API to return Billing Data   ID: PRCAAPI
 GENERAL DESCRIPTION:   This API is being implemented in support of the
 Automated Service Connected Designation (ASCD) project. The ASCD project has a
 Recovered Cost Report where they want to look for bills and payments for
 encounters that have had their Service Connected status changed by the ASCD
 options. This project has requested access to the Accounts Receivable (AR)
 package data in support of this report.  
  
 It should be noted that it was recommended that this access to the AR package
 not be given because the data for this report is not accurate at the encounter
 level. This recommendation was overridden.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCAAPI
KEYWORDS: PRCA*4.5*250
COMPONENT/ENTRY POINT: $$GETDATA(BillNum)
 COMPONENT DESCRIPTION:   This API is an Extrinsic Function. The input variable
 of this API will be the Bill Number for the Accounts Receivable (#430) file.  
  
 The API will return the following data elements: 
    ORIGINAL AMOUNT (#3) - Internal Value 
    DATE ACCOUNT ACTIVATED field (#60) - Internal Value 
    TOTAL PAID PRINCIPAL (#77) - Internal Value 
    DATE ENTERED (#19) from the AR TRANSACTION (#433) FILE using the 
       existing $$DFP^RCXVUTIL API.  
  
 The output format will be: 
    Original Amount ^ Date Account Activated ^ Total Paid Principle ^ Date 
   Entered 
VARIABLES: BillNum                      TYPE: Input
 VARIABLES DESCRIPTION:   BillNum is the .01 field value for the Accounts
 Receivable (#430) file. It can be in the Site-Bill Number Format or just the
 Bill Number Format.  Depending on the value of the Bill Number the API will
 determine which cross reference to look up the bill in the Accounts Receivable
 (#430) file.  
VARIABLES:  
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: SEP 27, 2007

NUMBER: 4371                            IA #: 4371
  DATE CREATED: FEB 25, 2004            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXRMEXSI                     NAME: REMINDER EXCHANGE APIs
  ID: PXRMEXSI
 GENERAL DESCRIPTION:   This describes the Reminder Exchange Utility APIs that
 can be used to transport and install Reminder Exchange file (#811.8) entries
 as part of a KIDS build. ICR #5687 allows subscribing packages to transport 
 Reminder Exchange file entries using KIDS. 
  
 The subscribing package should create a routine, referred to as ROUTINE in the
 descriptions below, with an entry point referred to as ENTRY. The purpose of
 this routine is to build a list of Reminder Exchange file entries that are to
 be transported and installed.  
  
 The entry point should have the following arguments: 
  
 ENTRY(MODE,ARRAY) 
  
 Where MODE can be "I" for include in the build and "A" for install action. The
 APIs documented below will set MODE to the appropriate value. ARRAY is the
 name of an array that contains the list of Reminder Exchange File entries. 
 You need the following for each Reminder Exchange entry you want to include: 
  
          S LN=LN+1 
          S ARRAY(LN,1)="NAME" 
          I MODE["I" S ARRAY(LN,2)="DATE/TIME" 
          I MODE["A" S ARRAY(LN,3)=ACTION 
  
 LN is a counter, ARRAY(LN,1) is the name of the entry, ARRAY(LN,2) is the
 date/time the entry was created (these can be cut and pasted from the Exchange
 File display), ARRAY(LN,3) is the install action. These are single letter
 codes such as install ("I"), merge ("M"), and overwrite ("O"). For example, 
  
 I MODE["A" S ARRAY(LN,3)="M" 
  
 If you would like the number of Reminder Exchange file entries that are going
 to be installed to be displayed during the KIDS install, include the following
 in ENTRY^ROUTINE after the list of Reminder Exchange file entries has been
 populated: 
  
 I MODE="IA" D BMES^XPDUTL("There are "_LN_" Reminder Exchange entries to be
 installed.") 
  
  
  
  
  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: REMINDER EXCHANGE
KEYWORDS: KIDS
COMPONENT/ENTRY POINT: DELEXE
 COMPONENT DESCRIPTION:   Usage: 
  DELEXE^PXRMEXSI("ENTRY","ROUTINE") 
  
 This should be called from the pre-init to clean out all previous versions of 
 the Reminder Exchange file entries. 
  
  
VARIABLES: ENTRY                        TYPE: Input
VARIABLES: ROUTINE                      TYPE: Input
COMPONENT/ENTRY POINT: EXFINC
 COMPONENT DESCRIPTION:   Usage: $$EXFINC^PXRMEXSI(Y,"ENTRY","ROUTINE") 
  
 This is used as a data screen in the KIDS build to determine which Exchange
 File entries will be included in the build. The data screen for #811.8 should
 be 
  
 I $$EXFINC^PXRMEXSI(Y,"ENTRY","ROUTINE") 
  
VARIABLES: Y                            TYPE: Input
VARIABLES: ENTRY                        TYPE: Input
VARIABLES: ROUTINE                      TYPE: Input
COMPONENT/ENTRY POINT: SMEXINS
 COMPONENT DESCRIPTION:   Usage: D SMEXINS^PXRMEXSI("ENTRY","ROUTINE") 
  
 This should be included in the post-init and will install all the Reminder
 Exchange file entries in the list.  
  
VARIABLES: ENTRY                        TYPE: Input
VARIABLES: ROUTINE                      TYPE: Input
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Using to install reminder exchange file entries for
 exporting TIU Document Definitions.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Mental Health is using the Reminder Exchange system to
 update Reminder Dialog entries related to the PCL-5 mental health instrument.  
  DATE ACTIVATED: MAY 23, 2013

NUMBER: 4372                            IA #: 4372
  DATE CREATED: FEB 25, 2004            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXRMEXU5                     NAME: PXRM Post KIDS Install
  ID: PXRMEXU5
 GENERAL DESCRIPTION:   Use of the Reminder Exchange Utility Post-KIDS after
 the installation of a reminder exchange file entry.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU,PXRM,REMINDER EXCHANGE
COMPONENT/ENTRY POINT: POSTKIDS
VARIABLES: PXRMRIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN of the entry in the Reminder Exchange
 File (811.8).  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Use to finish the installation process of a reminder
 exchange file entry for the export and installation of TIU Document
 Definitions.  

NUMBER: 4373                            IA #: 4373
  DATE CREATED: FEB 25, 2004            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXRMEXU1
  NAME: PXRM Delete Reminder Exchange Entry
  ID: PXRMEXU1
 GENERAL DESCRIPTION:   Use of the Reminder Exchange Utility Delete action for
 removal of a reminder exchange file entry.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU,PXRM,REMINDER EXCHANGE
COMPONENT/ENTRY POINT: DELETE
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN(s) of the entries to be removed from
 the Reminder Exchange file (811.8).  
COMPONENT/ENTRY POINT: TIUSRCH
 COMPONENT DESCRIPTION:   This entry allows an application to call into the
 Clinical Reminder Package to find TIU Patient Data Objects and TIU Template
 Fields in a word processing field.  
VARIABLES: GLOB                         TYPE: Input
 VARIABLES DESCRIPTION:   The global path to the word processing field. Similar
 to doing a ^DIC lookup. Example of searching the Dialog Progress Note Text
 Word Processing field from file 801.41.  
  
 D TIUSRCH^PXRMEXU1("^PXRMD(801.41,",DIEN,25,.OLIST,.TLIST) 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The record number to search against.  
VARIABLES: NODE                         TYPE: Input
 VARIABLES DESCRIPTION:   The word processing field subscript.  
VARIABLES: OLIST                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns an array of TIU Patient Data Object name
 found in the word processing field.  
VARIABLES: TLIST                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns an array of TIU template name found in the
 word processing field.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Used during Pre-install of TIU patches to remove any
 old/prior entries by TIU patches.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAR 17, 2025

NUMBER: 4374                            IA #: 4374
  DATE CREATED: FEB 25, 2004
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMRAPES0
  NAME: Free text bulletin              ID: GMRAPES0
 GENERAL DESCRIPTION:   This documents the use of the $$SENDREQ function to
 send a bulletin to a mail group indicating a request to add a free text
 allergy for a patient.  A message is sent when a user cannot find an adequate 
 match when entering an allergy for a patient.  The message includes important
 allergy data as well as contact information for the user.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$SENDREQ(USER,PAT,TEXT,GMRAET)
 COMPONENT DESCRIPTION:   This function sends a mail message to the GMRA
 REQUEST NEW REACTANT mail group.  If successful, the function returns a 1.  If
 it fails, it sends a 0 along with a description of why it failed.  The mail
 message will contain allergy information as well as contact information so the
 allergy can be added as quickly as possible.  
VARIABLES: USER                         TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the user attempting to
 add a free text entry.  This is essentially the user's DUZ.  
VARIABLES: PAT                          TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the patient involved
 with the allergy entry.  This is essentially the variable DFN.  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   This variable holds the text of the allergy entry the
 user was trying to add.  
VARIABLES: GMRAET                       TYPE: Input
 VARIABLES DESCRIPTION:   This array, passed by reference, contains any
 additional comments the user may have added regarding the request to add the
 text entry to the allergy file.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4375                            IA #: 4375
  DATE CREATED: FEB 26, 2004            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXRMGECU                     NAME: PXRM Health Factor Delete
  ID: PXRMGECU
 GENERAL DESCRIPTION:   This DBIA documents the call to Clinical Reminders to
 delete health factors associated with a TIU document.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU,PXRM
COMPONENT/ENTRY POINT: DEL(TIUDA)
 COMPONENT DESCRIPTION:   This entry point will delete the health factors
 associated with the TIU Document.  
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN of the TIU Document number.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4376                            IA #: 4376
  FILE NUMBER: 393                      GLOBAL ROOT: DD(393,10.04
  DATE CREATED: MAR 02, 2004            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4376
  ID: DD(393,10.04
 GENERAL DESCRIPTION:   DGBT*1*1 added a variable pointer L.LOCAL VENDOR to the
 TRANSCRIBED BY (#10.04) of the INCOMPLETE RECORDS (#393) file.  Unknowingly to
 the developer, the DD entries were not cleaned up properly.  Request killing 
 off the bad DD node entries to clean up the problem.  
  
 Request is one time only.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING
 SUBSCRIBING DETAILS:   Requesting to hard kill the bad node entries in order
 to correct the vp's.  DGBT*1*1 is a CoreFLS patch sent out to all sites.  With
 only Bay Pines running CoreFLS, inpact is minimal.   Once removed bad vp
 entries, worked as advertised.  
  
 Bad global listing: 
  
 Global ^DD(393,10.04 
         DD(393,10.04 ^DD(393,10.04,0) = TRANSCRIBED BY^V^^DT;4^Q 
 ^DD(393,10.04,1,0) = ^.1 ^DD(393,10.04,1,1,0) = 393^ATB^MUMPS 
 ^DD(393,10.04,1,1,1) = S DGJFSIG=1 D PHYDEF^DGJTUTL ^DD(393,10.04,1,1,2) = S
 DGJFSIG=1 D PHYDEF^DGJTUTL ^DD(393,10.04,1,1,"%D",0) = ^^2^2^2930302^ 
 ^DD(393,10.04,1,1,"%D",1,0) = This MUMPS cross reference acts like a trigger
 tha t updates the Physician ^DD(393,10.04,1,1,"%D",2,0) = for Deficiency field
 in file 393.  ^DD(393,10.04,1,1,"DT") = 2930302 ^DD(393,10.04,3) = 
 ^DD(393,10.04,21,0) = ^.001^1^1^3021216^^^^ ^DD(393,10.04,21,1,0) = Enter the
 person or vendor that transcribed this report.  ^DD(393,10.04,23,0) =
 ^.001^1^1^3021216^^^^ ^DD(393,10.04,23,1,0) =  ^DD(393,10.04,"DT") = 2930302 
 ^DD(393,10.04,"V",0) = ^.12P^3^3 ^DD(393,10.04,"V",1,0) = 200^PERSON^1^P^n^n 
 ^DD(393,10.04,"V",2,0) = 392.31^LOCAL VENDOR^2^L^n^n ^DD(393,10.04,"V",3,0) =
 440^VENDOR^3^V^n^n ^DD(393,10.04,"V","B",200,1) = 
 ^DD(393,10.04,"V","B",392.31,2) = ^DD(393,10.04,"V","B",440,2) =         <====
 needs removed.  ^DD(393,10.04,"V","B",440,3) = ^DD(393,10.04,"V","M","LOCAL
 VENDOR",2) = ^DD(393,10.04,"V","M","PERSON",1) = 
 ^DD(393,10.04,"V","M","VENDOR",2) =     <==== needs removed.  
 ^DD(393,10.04,"V","M","VENDOR",3) = ^DD(393,10.04,"V","O",1,1) = 
 ^DD(393,10.04,"V","O",2,2) = ^DD(393,10.04,"V","O",3,3) = 
 ^DD(393,10.04,"V","P","L",2) = ^DD(393,10.04,"V","P","P",1) = 
 ^DD(393,10.04,"V","P","V",2) =      <==== needs removed.  
 ^DD(393,10.04,"V","P","V",3) = Global ^ 

NUMBER: 4377                            IA #: 4377
  GLOBAL ROOT: TMP('TIUPR',$J,          DATE CREATED: MAR 03, 2004
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: TMP('TIUPR',$J)                 ID: TMP('TIUPR',$J,
 GENERAL DESCRIPTION:   This DBIA grants permission to Surgery to reference the
 global ^TMP("TIUPR",$J) identifying the specific report to be printed when the 
 print method for surgical reports is executed.  
  
 The following is an example of a reference identifying an Anesthesia Report,
 document #2002 stored in the TIU DOCUMENT file (#8925).  
  
 ^TMP("TIUPR",559965892,"3$ANESTHESIA REPORT;769",1,2002) = Vice SF 517 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SURGERY            ISC: Birmingham

NUMBER: 4378                            IA #: 4378
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870,
  DATE CREATED: APR 29, 2004            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: SD-PAIT HL LOGICAL LINK STATUS  ID: HLCS(870,
 GENERAL DESCRIPTION:   SD*5.3*333 allows for generating HL7 batches to be sent
 to local VistA Interface Engines as the first step of that transmission. There
 are possibilities of communication problems that would be reflected in the 
 status of fields in the SD-PAIT entry of the HL LOGICAL LINK - file # 870.  
  
                        Fld #              Fld name 
  
                          4                  STATE 
                          5         IN QUEUE FRONT POINTER 
                          6         IN QUEUE BACK POINTER  
                          7         OUT QUEUE FRONT POINTER 
                          8         OUT QUEUE BACK POINTER 
                        400.01      TCP/IP ADDRESS 
  
 SD-PAIT internal entry number would be determined by accessing "B" crss
 reference (IA # 3335).  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: 2023
KEYWORDS: HL LOGICAL LINK
KEYWORDS: SD-PAIT
KEYWORDS: TCP/IP ADDRESS
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
 SUBSCRIBING DETAILS:   There are possibilities of communication problems
 between PAIT transmission and local VistA IE that would be reflected in the
 status of fields in 
  the SD-PAIT entry of the HL LOGICAL LINK - file # 870.  
  
                        Fld #              Fld name 
  
                          4                  STATE 
                          5         IN QUEUE FRONT POINTER 
                          6         IN QUEUE BACK POINTER  
                          7         OUT QUEUE FRONT POINTER 
                          8         OUT QUEUE BACK POINTER 
                        400.01      TCP/IP ADDRESS The following code will be
 used to access SD-PAIT entry and to retrieve the above listed fields: 
  
          S SD870=$O(^HLCS(870,"B","SD-PAIT",""))                            
          N ARRAY D GETS^DIQ(870,SD870_",","4;5;6;7;8;400.01","I","ARRAY") 
        

NUMBER: 4379                            IA #: 4379
  FILE NUMBER: 2                        GLOBAL ROOT: DD(
  DATE CREATED: MAY 04, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File
  NAME: Post-Selection Action in Patient (#2) file
  ID: DD(
 GENERAL DESCRIPTION:   
  
 DG*5.3*582, Registration is sending multiple ISO bulletins. A flag has been
 added to DGRPEIS1, and the post-selection action for the Patient (#2) file
 needs to be modified to check for this flag so additional bulletins will be
 suppressed.  
  
 Old value: 
  ^DD(2,0,"ACT")= I '$G(DICR),$G(DIC(0))'["I" D ^DGSEC 
  
 Changing to: 
  ^DD(2,0,"ACT")= I '$G(DICR),$G(DIC(0))'["I",'$G(DGBULSUP) D ^DGSEC 
  
 DG53P582        ;ALB/BWF; Pre-Init; ; 3/19/2004 8:36am 
         ;;5.3;Registration;**582**;Aug 13, 1993 ENV     ;Environment check
 point 
         S XPDABORT="" 
         D PROGCHK(.XPDABORT) 
         I XPDABORT="" K XPDABORT 
         Q PROGCHK(XPDABORT)       ;checks for necessary programmer variables 
         I '$G(DUZ)!($G(DUZ(0))'="@")!('$G(DT))!($G(U)'="^") D 
         . D BMES^XPDUTL("*****") 
         . D MES^XPDUTL("Your programming variables are not set up properly.") 
         . D MES^XPDUTL("Installation aborted.") 
         . D MES^XPDUTL("*****") 
         . S XPDABORT=2 
         Q PRE     ; 
         S ^DD(2,0,"ACT")="I '$G(DICR),$G(DIC(0))'["I",'$G(DGBULSUP) D ^DGSEC"  
         Q 
  STATUS: Retired
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4380                            IA #: 4380
  DATE CREATED: MAR 23, 2004
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: TIUPRF                       NAME: TIU APIs for Patient Record Flags
  ID: TIUPRF
 GENERAL DESCRIPTION:   These APIs provide functionality needed by Registration
 for associating PRF flags with TIU Titles, and for linking PRF Assignment
 History records (i.e., actions) to TIU notes.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: TIUPRF
KEYWORDS: Patient Record Flags
KEYWORDS: TIU-PRF
KEYWORDS: PRF
COMPONENT/ENTRY POINT: GETTL
 COMPONENT DESCRIPTION:   This API returns the Title Name from the TIU DOCUMENT
 DEFINITION file (#8925.1), based on an input IEN.  Works for any type of
 Document Definition, not just Titles. 
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   A TIU DOCUMENT DEFINITION IEN 
VARIABLES: $$GETTTL                     TYPE: Output
 VARIABLES DESCRIPTION:   The .01 Name corresponding to the input DOCUMENT
 DEFINITION IEN 
COMPONENT/ENTRY POINT: CHKDOC
 COMPONENT DESCRIPTION:   This API checks whether or not a Document from the
 TIU DOCUMENT file (#8925) exists, given its IEN.  
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   An IEN from the TIU DOCUMENT file 
VARIABLES: $$CHKDOC                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 if the document exists in the TIU DOCUMENT
 file, or 0 if not.  
COMPONENT/ENTRY POINT: GETLIST
 COMPONENT DESCRIPTION:   This API returns a list of PRF TITLES from the TIU
 DOCUMENT DEFINITION file (#8925.1).  The list Includes Category I or Category
 II TITLES or both, depending on the value of the input parameter PRFCAT.  
VARIABLES: PRFCAT                       TYPE: Input
 VARIABLES DESCRIPTION:   This input parameter determines what PRF category
 titles to return.  1 = Category I, 2 = Category II, and 3 = Categories I AND
 II.  
VARIABLES: TARGET                       TYPE: Both
 VARIABLES DESCRIPTION:   This array name must be passed in as a closed global
 root. The list of Titles (IEN^NAME) will be returned in this array.  
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4381                            IA #: 4381
  FILE NUMBER: 101.43                   GLOBAL ROOT: ORD(101.43,
  DATE CREATED: JUN 03, 2004
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Contrast Media seeding between OE/RR & Rad/Nuc Med
  ID: ORD(101.43,
GLOBAL REFERENCE: ORD(101.43,D0,'RA')
FIELD NUMBER: 71.1                      FIELD NAME: CONTRAST MEDIA
  LOCATION: "RA";1                      ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field prior to the installation of OR*3*211
 indicates what contrast media, if any, is used by this radiologic procedure
 where: M = unspecified contrast media C = cholecystogram B = barium 
  
 This value may consist of as many of these flags as are appropriate for this
 procedure; if empty, no contrast media is assumed.  This field is used
 primarily for Order Checking.  
FIELD NUMBER: 71.2                      FIELD NAME: PROCEDURE TYPE
  LOCATION: "RA";2                      ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field indicates whether the Orderable Item procedure
 is of type: Broad, Detailed, Parent, or Series.  
  
 These terms are part of the VistA Radiology/Nuclear Medicine lexicon.  
FIELD NUMBER: 71.3                      FIELD NAME: IMAGING TYPE
  LOCATION: "RA";3                      ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field defines the Imaging Type of the Orderable
 Item. Valid choices are: Radiology, CT Scan, Magnetic Resonance Imaging, 
 Angio/Neuro/Interventional, Cardiology Studies, Nuclear Medicine, Ultrasound,
 Vascular Lab, & Mammography 
FIELD NUMBER: 71.4                      FIELD NAME: COMMON PROCEDURE
  LOCATION: "RA";4                      ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field indicates that this procedure is commonly
 ordered from Radiology, and is an entry in the Radiology Common Procedures
 file; the number stored here is the sequence number for display.  
 GENERAL DESCRIPTION:   Radiology will release a patch, RA*5*45, that will
 shift emphasis from AMIS Codes to CPT Codes regarding contrast media
 associations. This will lead the user to associate a relevant contrast medium,
 when appropriate, to a detailed or series procedure.  
  
 The old contrast media data set consisted of the following: Barium, Oral
 Cholecystogram, & Unspecified Contrast Media 
  
 The new data set consists of the following: Iodinated ionic, Iodinated
 non-ionic, Gadolinium, Oral Cholecystographic, Gastrografin, Barium, &
 unspecified contrast media.  
  
 Patch RA*5*45 will eliminate keystrokes by mapping barium to barium and oral
 cholecystogram to oral cholecystographic. To update the new CONTRAST MEDIA
 (#125) in the RAD/NUC MED PROCEDURE (#71) file, Rad/Nuc Med will need to look
 at Radiology/Nuclear Medicine specific data located on the "RA" node of the
 ORDERABLE ITEMS (#101.43) file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 01, 2004
KEYWORDS: CONTRAST MEDIA
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  ISC: Hines

NUMBER: 4382                            IA #: 4382
  FILE NUMBER: 101.43                   GLOBAL ROOT: ORD(101.43
  DATE CREATED: MAR 25, 2004
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Synch up contrast media between files 71 & 101.43
  ID: ORD(101.43
GLOBAL REFERENCE: ORD(101.43,"S.XRAY",
 GLOBAL DESCRIPTION:   This is a 'M' type cross-reference set when the
 orderable item in the ORDERABLE ITEMS file is associated with the Rad/Nuc Med
 application.  
 GENERAL DESCRIPTION:   Requesting this IA for the purpose of efficient
 traversal of the ORDERABLE ITEMS (#101.43) file. Rad/Nuc Med needs to know
 which orderable items are linked to Rad/Nuc Med procedures. Traversing the
 'S.XRAY' cross-reference is the most efficient way to confirm this
 relationship.  
  
 This is related to IA 4381 and patches: RA*5*45 & OR*3*211.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: SEP 01, 2004
KEYWORDS: CONTRAST MEDIA
KEYWORDS: S.RAD
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  ISC: Hines

NUMBER: 4383                            IA #: 4383
  DATE CREATED: MAR 29, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGPFAPI1                     NAME: DGPF ASSIGNMENT LINK TIU PN
  ID: DGPFAPI1
 GENERAL DESCRIPTION:   The purpose of this API is to facilitate the retrieval
 of specific data for an active or inactive Patient Record Flag Assignment to
 determine whether a TIU Progress Note has been entered for each assignment
 history record.  If the request is not from the Owner Site of the Assignment,
 no data is returned.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$GETHTIU(DFN,DGTITLE,TARGET_ROOT)
 COMPONENT DESCRIPTION:   This function entry point is used to search for and
 retrieve specific data for a patients (active or inactive) Patient Record Flag
 Assignment.  The TIU Progress Note Title IEN will be used to search for the
 patient assignment that is linked by the associated Patient Record Flag to
 that TIU Progress Note Title.  If the request is not from the Owner Site of
 the Assignment, no data is returned.  All Patient Record Flag data will be
 returned in a user named closed root array (local or global) that will contain
 multiple subscripts.  This array is referred to as "TARGET_ROOT" in this text. 
 
 Note that the TARGET_ROOT will be initialized (killed) before being used.  
  
 MUMPS code example of use: 
 --------------------------
 I $$GETHTIU^DGPFAPI1(DFN,DGTITLE,"DGPFHTIU") D . W !,"DGPFHTIU array contains
 PRF Assignment History data for this patient." 
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   [Required] 
  IEN of patient in the PATIENT File (#2) 
  
VARIABLES: DGTITLE                      TYPE: Input
 VARIABLES DESCRIPTION:   [Required] 
  Pointer to the TIU DOCUMENT (#8925.1) file.  
  This pointer represents the TIU Progress Note 
  Title that could be associated with a National 
  or Local Patient Record Flag.  The IEN is 
  stored in (Field #.07) of the PRF LOCAL FLAG 
  (#26.11) or the PRF NATIONAL FLAG (#26.15) 
  file.  The patient Assignment can then be 
  found by using the Flag name pointer that is 
  setup in each (#26.13) record.  
  
VARIABLES: $$GETHTIU                    TYPE: Output
 VARIABLES DESCRIPTION:   
  "0" = Failure = "0^Error Message of what failed" 
                  (2 piece string (^)-delimited) 
  "1" = Successful 
  
VARIABLES: TARGET_ROOT                  TYPE: Both
 VARIABLES DESCRIPTION:   [Optional] 
  Input: Target array name that should be passed 
         as a closed root reference, local or 
         global.  If the parameter is not passed, 
         then the default name of the TARGET_ROOT 
         is set equal to "DGPFHTIU".  
  
  Output: A multiple subscripted array format 
          is returned.  
  
  TARGET_ROOT(subscript) = field value 
    where: 
      subscript = a subscript being derived from 
                  the following table below: 
    field value = Internal value^External value 
                  2 piece string (^)-delimited 
                  i.e. - "int^ext" 
   field#/file# = global location of data value 
  
  
  subscript    field name        field #/file # 
  -----------  -------------     ---------------
  "ASSIGNIEN"  Assignment IEN   (.001)/(#26.13) 
               The field value contains the 
               pointer to the Patient Record Flag 
               Assignment file (#26.13) record.  
         PIECE 1=IEN of (#26.13) file 
         PIECE 2=Name of Patient assigned to flag 
  
  "FLAG"       Flag Name         (.02)/(#26.13) 
               The field value contains the 
               Patient Record Flag name that is 
               assigned to the patient.  
         PIECE 1=IEN variable pointer to the 
                 (#26.11) or (#26.15) file 
         PIECE 2=Name of Flag 
  
  "HISTORY"    History Record(s)   Multiple Nodes 
               This subscript level will 
               contain a unique node for each 
               PRF Assignment History record 
               created for the Assignment.  
  
      The multiple subscript node format is as 
      follows: 
  
      TARGET_ROOT("HISTORY")=nn 
        where: 
          nn = total number of History Records 
               returned 
  
      TARGET_ROOT("HISTORY",nn,"Subscript")=int^ext 
        where: 
          nn = unique number for each History rec.  
          "Subscript" = history field name 
           Subscript names: "ACTION" 
                            "APPRVBY" 
                            "DATETIME" 
                            "HISTIEN" 
                            "ORIG FAC" 
                            "TIUIEN" 
  
      TARGET_ROOT("HISTORY",nn,"ACTION")=int^ext 
        Action of History       (.03)/(#26.14) 
          The field value contains the event 
          that occurred to create the Assignment 
          History record.  
        PIECE 1 = internal action code number 
        PIECE 2 = external action text 
                                 
      TARGET_ROOT("HISTORY",nn,"APPRVBY")=int^ext 
        Approved By of History  (.05)/(#26.14) 
          The field value contains the person who 
          approved this change to the Assignment 
          History record.  
        PIECE 1 = IEN of (#200) file 
        PIECE 2 = external person name 
  
      TARGET_ROOT("HISTORY",nn,"DATETIME")=int^ext 
        History Assignment DT  (.02)/(#26.14) 
          The field value contains a FileMan 
          internal^external create Date/Time of 
          the Assignment History record.  
        PIECE 1 = internal Fileman date 
        PIECE 2 = external Fileman date 
  
      TARGET_ROOT("HISTORY",nn,"HISTIEN")=int^ext 
        History IEN            (.001)/(#26.14) 
          The field value contains the 
          pointer to the PRF Assignment History 
          file (#26.14) record.  
        PIECE 1 = IEN of (#26.14) file 
        PIECE 2 = (same value as PIECE 1) 
  
      TARGET_ROOT("HISTORY",nn,"ORIG FAC")=int^ext 
        Originating Facility for this History record 
                                      (.03)/(#26.14) 
          The field value contains the facility 
          that created this Assignment History record.  
        PIECE 1 = IEN of (#4) file 
        PIECE 2 = external Institution name 
  
      TARGET_ROOT("HISTORY",nn,"TIUIEN")=int^ext 
        TIU PN LINK            (.06)/(#26.14) 
          The field value contains the pointer 
          of the linked TIU Progress Note of the 
          TIU DOCUMENT (#8925) file.  
        PIECE 1 = IEN of (#8925) file 
        PIECE 2 = TIU DOCUMENT name 
        (Note:  Null values returned if no IEN.) 
COMPONENT/ENTRY POINT: $$FNDTITLE(DGTITLE)
 COMPONENT DESCRIPTION:   This function entry point is used to search for and
 retrieve the IEN and External name value of either a PRF LOCAL FLAG (#26.11)
 or PRF NATIONAL FLAG (#26.15) file entry that has been linked to a TIU
 DOCUMENT DEFINITION (#8925.1) file IEN.  
  
 MUMPS code example of use: 
  
 W $$FNDTITLE^DGPFAPI1(DGTITLE) 
    1;DGPF(26.15,^BEHAVIORAL 
  
  
VARIABLES: DGTITLE                      TYPE: Input
 VARIABLES DESCRIPTION:   
  [Required] 
  IEN of a TIU DOCUMENT DEFINITION (#8925.1) file entry.  
  
VARIABLES: $$FNDTITLE                   TYPE: Output
 VARIABLES DESCRIPTION:   
  (returns 2 piece string (^)-delimited) 
  
  On Failure - 0^error text from $$EZBLD^DIALOG 
  On Success - IEN^External Flag Name 
   
  [example:  1;DGPF(26.15,^BEHAVIORAL] 
  [Note:    "1;DGPF(26.15," is a variable pointer] 
  
COMPONENT/ENTRY POINT: $$GETLINK(DGTIUIEN)
 COMPONENT DESCRIPTION:   This function entry point is used to search for and
 retrieve the IEN of the PRF ASSIGNMENT HISTORY (#26.14) record that is linked
 to the TIU DOCUMENT (#8925) record.  If no link is found, the function call
 will return a 0 value.  
  
 MUMPS code example of use: 
  
 W $$GETLINK^DGPFAPI1(DGTIUIEN) 
     2532 
  
VARIABLES: DGTIUIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   
  [Required] 
  IEN of the TIU DOCUMENT (#8925) record.  
  
VARIABLES: $$GETLINK                    TYPE: Output
 VARIABLES DESCRIPTION:   
  "0" = Failure 
  "###" = Successful - IEN of linked history record 
  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
  DATE ACTIVATED: MAY 29, 2018

NUMBER: 4384                            IA #: 4384
  DATE CREATED: MAR 29, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGPFAPI2                     NAME: DGPF FILE/DELETE TIU PN LINK
  ID: DGPFAPI2
 GENERAL DESCRIPTION:   The purpose of this API is to facilitate the Filing
 (Linking) and Deleting (Un-Linking) of the TIU PN LINK (#.06) field of the PRF
 ASSIGNMENT HISTORY file (#26.14).  The TIU PROGRESS NOTE pointer IEN to the
 TIU DOCUMENT file (#8925) will be used.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$STOTIU(DFN,DGAIEN,DGHIEN,DGTIUIEN)
 COMPONENT DESCRIPTION:   This function entry point is used to File (Link) the
 pointer IEN of a TIU Progress Note of the TIU DOCUMENT file (#8925) to the TIU
 PN LINK Field (#.06) of the PRF ASSIGNMENT HISTORY file (#26.14).  
  
 MUMPS code example of use: 
 --------------------------
 I $$STOTIU^DGPFAPI2(DFN,DGAIEN,DGHIEN,DGTIUIEN) D . W !,"The TIU Progress Note
 IEN has been Filed for this patient." 
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   [Required] 
  IEN of patient in the PATIENT (#2) file.  
  
VARIABLES: DGAIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   [Required] 
  IEN pointer to patient record flag assignment in 
  the PRF ASSIGNMENT (#26.13) file.  
  
VARIABLES: DGHIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   [Required] 
  IEN for record in PRF ASSIGNMENT HISTORY 
  (#26.14) File.  
  
VARIABLES: DGTIUIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   [Required] 
  IEN pointer of the TIU Progress Note 
  to the TIU DOCUMENT (#8925) file.  
  
VARIABLES: $$STOTIU                     TYPE: Output
 VARIABLES DESCRIPTION:   
  "0" = Failure  = "0^Error Message of what failed" 
                     (2 piece string (^)-delimited) 
  "1" = Successful = The TIU PN LINK (#.06) field 
                     of the (#26.14) file has been 
                     updated.  
  
COMPONENT/ENTRY POINT: $$DELTIU(DGTIUIEN)
 COMPONENT DESCRIPTION:   This function entry point is used to Delete (Un-Link)
 the pointer IEN of a TIU Progress Note of the TIU DOCUMENT file (#8925) from
 the TIU PN LINK Field (#.06) of the PRF ASSIGNMENT HISTORY file (#26.14).  
  
 MUMPS code example of use: 
 --------------------------
 I $$DELTIU^DGPFAPI2(DGTIUIEN) D . W !,"The TIU Progress Note IEN has been
 Deleted for this patient." 
  
VARIABLES: DGTIUIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   [Required] 
  IEN pointer of the TIU Progress Note to 
  the TIU DOCUMENT (#8925) file.  
  
VARIABLES: $$DELTIU                     TYPE: Output
 VARIABLES DESCRIPTION:   
  "0" = Failure 
  "1" = Successful = The TIU PN LINK (#.06) field 
                     of the (#26.14) file has been 
                     deleted.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4385                            IA #: 4385
  DATE CREATED: MAR 31, 2004            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCEMU2
  NAME: MRA related function Calls from AR into IB
  ID: IBCEMU2
 GENERAL DESCRIPTION:   Two MRA related function calls made from AR into the IB
 system: 
  
 1) Determine the MRA Type for a given bill. Pre-MRA bills, post-MRA Medicare
 bills or post-MRA non-Medicare bills. This function returns 1, if the bill is
 a pre-MRA bill, returns 2 if the bill is a post-MRA Medicare bill, or 3 if the
 bill is a post-MRA Medicare bill.  
  
 2) Return the date Medicare Remittance Advice (MRA) was first activated at
 site.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MRA
KEYWORDS: MEDICARE
COMPONENT/ENTRY POINT: $$MRATYPE(BILL,ARDATE)
 COMPONENT DESCRIPTION:   This function returns DATE MRA FIRST ACTIVATED at
 site.  
VARIABLES: BILL                         TYPE: Input
 VARIABLES DESCRIPTION:   The ien# of a given bill.  
VARIABLES: ARDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   The AR Activation Date of that bill.  
VARIABLES: $$MRATYPE                    TYPE: Output
COMPONENT/ENTRY POINT: $$MRADTACT
 COMPONENT DESCRIPTION:   Return Date MRA First Activated at site.  
VARIABLES: $$MRADTACT                   TYPE: Output
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   The AR system makes two MRA related function calls to
 the IB system: 
  
 1) $$MRATYPE^IBCEMU2(BILL,ARDATE) Where BILL is the ien # of a bill and ARDATE
 is the AR Activation Date of that bill.  
  
 2) $$MRADTACT^IBCEMU2 Returns the Date MRA was First Activated at site.  

NUMBER: 4386                            IA #: 4386
  FILE NUMBER: 8925.1                   GLOBAL ROOT: TIU(8925.1,
  DATE CREATED: MAR 29, 2004
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DGPF ASSOCIATED FLAG PN TITLE   ID: TIU(8925.1,
GLOBAL REFERENCE: TIU(8925.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   This IA will document the fact that in the PRF LOCAL
 FLAG file (#26.11) and the PRF NATIONAL FLAG file (#26.15), there is a field
 called TIU PN TITLE (Field #.07) which points to the TIU DOCUMENT DEFINITION
 file (#8925.1).  
  
 The Registration package request permission to store a pointer to the NAME 
 field (#.01) of the TIU DOCUMENT DEFINITION file (#8925.1).  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 4387                            IA #: 4387
  FILE NUMBER: 8925                     GLOBAL ROOT: TIU(8925,
  DATE CREATED: MAR 29, 2004
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DGPF ASSIGNMENT TIU PN LINK     ID: TIU(8925,
GLOBAL REFERENCE: TIU(8925,D0,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 PRF
 ASSIGNMENT HISTORY file (#26.14), there is a field called TIU PN LINK (Field
 #.06) which points to the TIU DOCUMENT file (#8925).  
  
 The Registration package request permission to store the pointer IEN of a TIU
 PROGRESS NOTE to the PRF ASSIGNMENT HISTORY file (#26.14) field (#.06).  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 4388                            IA #: 4388
  FILE NUMBER: 430                      GLOBAL ROOT: PRCA(430
  DATE CREATED: MAR 29, 2004            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: File
  NAME: PRCA(430                        ID: PRCA(430
GLOBAL REFERENCE: PRCA(430,D0,13)
FIELD NUMBER: 132                       FIELD NAME: Medicare Unreimbursable
  LOCATION: U;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Medicare Contract Adjustments 
FIELD NUMBER: 131
  FIELD NAME: Medicare Contract Adjustments
  LOCATION: U;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Integrated Billing system is referencing the AR global:
 ^PRCA(430,D0,13).  The two data elements checked by the IB system and stored
 at this level are: Medicare Contractual Adjustment and Medicare Unreimbursable
 Amount.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: MRA
KEYWORDS: MEDICARE
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4389                            IA #: 4389
  FILE NUMBER: 9.7                      GLOBAL ROOT: XPD(9.7
  DATE CREATED: APR 13, 2004            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Imaging - Install file #9.7     ID: XPD(9.7
GLOBAL REFERENCE: XPD(9.7,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The name and version number of the application.  
FIELD NUMBER: 2                         FIELD NAME: DATE LOADED
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The date the application was loaded 
FIELD NUMBER: 51                        FIELD NAME: DISTRIBUTION DATE
  LOCATION: 1;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The distribution date of the application build.  
 GENERAL DESCRIPTION:   
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   VistA Imaging is granted permission to read the INSTALL
 file (#9.7) to obtain a survey of all patches that have been installed
 (including any patches that a site might be testing for us). For released
 patches, the distribution is not so important, but for test patches it becomes 
 important to see that a site is running a version on the VistA server that is
 compatible with the version on the client (DICOM Gateways).  

NUMBER: 4390                            IA #: 4390
  FILE NUMBER: 9.4                      GLOBAL ROOT: DIC(9.4
  DATE CREATED: APR 13, 2004            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Imaging - PACKAGe file (#9.4)   ID: DIC(9.4
GLOBAL REFERENCE: DIC(9.4,'B'
 GLOBAL DESCRIPTION:   Cross reference on the application name.  
GLOBAL REFERENCE: DIC(9.4,D0,22,
FIELD NUMBER: .02                       FIELD NAME: DATE APPLIED
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Date the patch was installed.  
FIELD NUMBER: .03                       FIELD NAME: APPLIED BY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The person who installed the patch.  
FIELD NUMBER: .01                       FIELD NAME: PATCH APPLICATION HISTORY
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field has stores the patch number applied.  
 GLOBAL DESCRIPTION:   The PATCH APPLICATION HISTORY subfile (field
 #1105\subfile #9.4901).  
GLOBAL REFERENCE: DIC(9.4,DO,22,'B'
 GLOBAL DESCRIPTION:   The "B" cross reference on the PATCH APPLICATON HISTORY
 subfile (#9.4901).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING            ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   VistA Imaging is granted permission to read the PACKAGE
 file (9.4) to obtain the list of installed patches for VistA Imaging.   Since
 the people who often maintain the host Vista database are not the same as the 
 ones who support the networked workstations, there is sometimes a disparity
 between the KIDS installs and the Imaging workstation's InstallShield
 installs.  This functionality is an attempt to help get the two in synch.  

NUMBER: 4391                            IA #: 4391
  FILE NUMBER: 36                       GLOBAL ROOT: DIC(36,
  DATE CREATED: APR 07, 2004            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INSURANCE COMPANY FILE ACCESS
  ID: DIC(36,
GLOBAL REFERENCE: DIC(36,D0,0)
FIELD NUMBER: .01                       FIELD NAME: INSURANCE COMPANY
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: INSURANCE COMPANY
  LOCATION: 0;1                         ACCESS: Pointed to
FIELD NUMBER: .01                       FIELD NAME: INSURANCE COMPANY
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(36,D0,.11)
FIELD NUMBER: .111                      FIELD NAME: STREET ADDRESS [LINE 1]
  LOCATION: .11;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .112                      FIELD NAME: STREET ADDRESS [LINE 2]
  LOCATION: .11;2                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .113                      FIELD NAME: STREET ADDRESS [LINE 3]
  LOCATION: .11;3                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .114                      FIELD NAME: CITY
  LOCATION: .11;4                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .115                      FIELD NAME: STATE
  LOCATION: .11;5                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .116                      FIELD NAME: ZIP CODE
  LOCATION: .11;6                       ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   It has come to my attention that Accounts Receivable
 has no Integration Agreement with Integrated Billing to allow A/R to access
 the insurance file (#36), even though A/R uses this file extensively for the
 following: 
  
   INSURANCE COMPANY NAME (#.01 field), direct read 
   INSURANCE COMPANY ADDRESS (fields #.111-#.116), direct read 
   As a file lookup using ^DIC 
   As a pointer directly to ^DIC(36) in ACCOUNTS RECEIVABLE file 
    (#430 - 2 fields - SECONDARY INSURANCE CARRIER (#19) and TERTIARY 
    INSURANCE CARRIER (#19.1)) 
   As part of a variable pointer on the DEBTOR field (#.01) of the AR 
    DEBTOR file (#340) 
  
 An IA is needed to cover these usages.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4392                            IA #: 4392
  FILE NUMBER: 450                      GLOBAL ROOT: PRSPC(
  DATE CREATED: APR 07, 2004            CUSTODIAL PACKAGE: PAID
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PAID EMPLOYEE                   ID: PRSPC(
GLOBAL REFERENCE: PRSPC(D0,
FIELD NUMBER: .01                       FIELD NAME: EMPLOYEE NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: SSN
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 31                        FIELD NAME: SEX
  LOCATION: 0;32                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 32                        FIELD NAME: DATE OF BIRTH
  LOCATION: 0;33                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 700                       FIELD NAME: NEW PERSON
  LOCATION: 200;1                       ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Also included here are direct global reads of the
 ^PRSPC(D0) to loop through the entries.  
 GENERAL DESCRIPTION:   Kernel has permission to have read access to the PAID
 EMPLOYEE file fields as described in this DBIA.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

NUMBER: 4393                            IA #: 4393
  DATE CREATED: MAY 03, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         ROUTINE: DPTNAME
  NAME: DPTNAME                         ID: DPTNAME
 GENERAL DESCRIPTION:   Kernel has the permission to use FORMAT^DPTNAME to
 standardize person name as described in this DBIA.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$FORMAT(DGNAME,DGMINL,DGMAXL,DGNOP,DGCOMA,DGAUDIT,DGFAM,
DGDNC)
VARIABLES: $$FORMAT                     TYPE: Output
 VARIABLES DESCRIPTION:   DGNAME in specified format or null if length of
 transformed val ue is less than DGMINL 
VARIABLES: DGNAME                       TYPE: Input
 VARIABLES DESCRIPTION:   Text value representing person name to transform.  
VARIABLES: DGMINL                       TYPE: Input
 VARIABLES DESCRIPTION:   Minimum length (optional), default 3.  
VARIABLES: DGMAXL                       TYPE: Input
 VARIABLES DESCRIPTION:   Minimum length (optional), default 3.  
VARIABLES: DGNOP                        TYPE: Input
 VARIABLES DESCRIPTION:   1 to standardize last name for 'NOP' x-ref
 (optional).  
VARIABLES: DGCOMA                       TYPE: Input
 VARIABLES DESCRIPTION:   0 to not require a comma, 1 to require a comma in the
 input value, 2 to add a comma if none, 3 to prohibit (remove) commas, 
 (optional) default if not specified is 1.  
VARIABLES: DGAUDIT                      TYPE: Input
 VARIABLES DESCRIPTION:   Variable to return audit, pass by reference
 (optional). Returned values:  0 if no change was made, 1 if name is changed, 2
 if name could not be converted, DGAUDIT(1) defined if name contains no comma, 
 DGAUDIT(2) defined if parenthetical text is removed, DGAUDIT(3) defined if
 value is unconvertible, DGAUDIT(4) defined if characters are removed or
 changed.  
VARIABLES: DGFAM                        TYPE: Input
 VARIABLES DESCRIPTION:   1 if just the family name, 0 otherwise (optional).  
VARIABLES: DGDNC                        TYPE: Input
 VARIABLES DESCRIPTION:   1 to prevent componentization (optional) 
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

NUMBER: 4394                            IA #: 4394
  DATE CREATED: APR 07, 2004
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSSDGUPD                     NAME: Data updates
  ID: PSSDGUPD
 GENERAL DESCRIPTION:   In support of the Outpatient Pharmacy Automation
 Dispense project, Pharmacy Data Management needs to know when changes are made
 to entries in the DRUG file (#50).  National Drug File data updates make
 changes to entries in this file.  To meet this need, NDF requests permission
 to call routine PSSDGUPD at entry point PSN.  The array ^TMP($J,"^",IEN where
 IEN is the internal entry number in the DRUG file (#50) wil be sent to this
 entry point.  The matching and unmatching processes also make changes to the
 drug file that need to be sent to PDM.  To this end, NDF requests permission
 to call routine PSSHUIDG at entry point DRG with the variable PSNB (if an 
 entry is being matched) or DA (if an entry is being unmatched) representing
 the internal entry number in the drug file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PSN
VARIABLES: global TMP($J,               TYPE: Input
 VARIABLES DESCRIPTION:   
  ^TMP($J,"^",IEN) is the array of entries in file 50 that have been edited.  
COMPONENT/ENTRY POINT: DRG
VARIABLES: PSNB                         TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of an entry in file 50.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of an entry in file 50.  
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
  ISC: Birmingham
 SUBSCRIBING DETAILS:   NDF data updates will make a call to %ZTLOAD to queue
 PSN^PSSDGUPD and pass in ^TMP($J,"^" via ZTSAVE.  Matching and unmatching will
 make a call to DRG^PSSDGUPD(DA).  

NUMBER: 4395                            IA #: 4395
  DATE CREATED: MAY 04, 2004            CUSTODIAL PACKAGE: FEE BASIS
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: FBRXUTL                      NAME: FEE PHARMACY API
  ID: FBRXUTL
 GENERAL DESCRIPTION:   This routine contains APIs related to the Pharmacy
 module of Fee Basis.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$RXSUM(DATE,STATION_NUMBER)
 COMPONENT DESCRIPTION:   This extrinsic function returns the count and cost of
 prescriptions paid through the fee software for a specified date.  
  Format: 
    $$RXSUM^FBRXUTL(DATE,STATION_NUMBER) 
  Examples: 
  1. Obtain count and cost for 4/8/2004 and station 688.  
     >W $$RXSUM(3040408,688) 
     5^17.55 
  2. An exception.  
     >W $$RXSUM^FBRXUTL(3040408) 
     -1^102^Valid station number not specified.  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) A date in VA FileMan internal format. 
 This input parameter is used to select prescriptions whose DATE CERTIFIED FOR
 PAYMENT field equals this value.  
VARIABLES: STATION_NUMBER               TYPE: Input
 VARIABLES DESCRIPTION:   (Required) A 3 digit station number.  This input
 parameter is used to select prescriptions based on the VAMC that approved
 payment when querying the national Fee Replacement system.  Prescriptions will
 be included when the approving station number Starts With this 3 digit value. 
 For example, prescriptions approved by satellite station 688A1 would be
 included for an input parameter equal to 688.  This parameter will not be
 evaluated until the API is modified to obtain data from the Fee Replacement
 system.  
VARIABLES: $$RXSUM                      TYPE: Output
 VARIABLES DESCRIPTION:   This function returns a string value 
  = count ^ total_amount_paid 
     where 
      count = the number of prescriptions for the date and station 
      total_amount_paid = sum of the Amount Paid for the prescriptions in  
                          dollars and cents 
  OR if an exception occurred 
  = -1 ^ exception_number ^ exception_text 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
 SUBSCRIBING DETAILS:   Outpatient Pharmacy has subscribed to the $$RXSUM
 component.  

NUMBER: 4396                            IA #: 4396
  DATE CREATED: MAY 04, 2004            CUSTODIAL PACKAGE: FEE BASIS
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: FBUTL                        NAME: DBIA4396
  ID: FBUTL
 GENERAL DESCRIPTION:   FEE BASIS APIs.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$AUTHL(PATIENT,STATION_NUMBER,CUTOFF_DATE,ARRAY_NAME)
 COMPONENT DESCRIPTION:   This extrinsic function returns authorization data
 for a specified patient.  Authorizations that have been Austin Deleted will
 not be returned. Format: 
   $$AUTHL^FBUTL(PATIENT,STATION_NUMBER,CUTOFF_DATE,ARRAY_NAME) Examples: 
  1. Retrieve authorizations for patient with DFN = 23456 in MYARRAY().  
     >W $$AUTHL^FBUTL(23456,,,"MYARRAY") 
     2 
     >ZW MYARRAY 
     MYARRAY(0)=2 
     MYARRAY(1,"FDT")=3011021 
     MYARRAY(1,"TDT")=3011030 
     MYARRAY(2,"FDT")=3000101 
     MYARRAY(2,"TDT")=3031231 
  
  2. An exception.  
    >W $$AUTHL^FBUTL() 
    -1^101^Patient DFN not specified.  
    >ZW FBAUTH 
VARIABLES: PATIENT                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Patient identifier,  internal entry number
 of Patient (#2) file (i.e. DFN).  
VARIABLES: STATION_NUMBER               TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) If specified, the station number will be
 used to select authorizations from the national Fee Replacement system.  Only 
 authorizations whose issuing station Starts With this parameter value will be
 returned.  This parameter will not be evaluated until the API is modified to
 obtain data from the fee replacement system.  
VARIABLES: CUTOFF_DATE                  TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Date in VA FileMan internal format.  If
 specified, only authorizations whose To Date is equal to or after the cutoff
 date will be returned.  
VARIABLES: ARRAY_NAME                   TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Name of output array, closed root. If not
 specified then a default value of "FBAUTH" will be used.  The array will be
 initialized by this API.  The array name must not be the same as variables
 newed by this API (e.g. FBDFN, FBAR, FBC, FBDA, FBDT, FBICN, FBSN, FBY). 
 Examples of a valid array name: "FBAUTH", "DGAUTH(12)", "^TMP($J)", etc.  
VARIABLES: $$AUTHL                      TYPE: Output
 VARIABLES DESCRIPTION:   This function returns a string value 
  = count of authorizations in the output array 
  OR 
  = -1 ^ exception_number ^ exception_text 
VARIABLES: OUTPUT_ARRAY                 TYPE: Output
 VARIABLES DESCRIPTION:   If an exception did not occur, there will also be an
 output array of authorization data subscripted by sequential canonic numbers
 and a header node subscripted by 0.  
   array(0) = count of authorizations in the output array 
   array(#,"FDT") = authorization # From Date (internal format) 
   array(#,"TDT") = authorization # To Date (internal format) 
  
 Note that additional subscripts may be added in the future to provide more
 authorization data. The calling application should kill the entire output
 array so any added subscripts will be cleaned-up (e.g. K FBAUTH).  
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
 SUBSCRIBING DETAILS:   Scheduling has subscribed to the $$AUTHL component.  
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
 SUBSCRIBING DETAILS:   Added 11/28/2006 

NUMBER: 4397                            IA #: 4397
  DATE CREATED: APR 08, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIAUTL                       NAME: DIAUTL
  ID: DIAUTL
 GENERAL DESCRIPTION:   Auditing Utilities.  Auditing allows VA FileMan users
 and developers to look back through the dimension of time at prior values in
 any file. Auditing is not just a tool that enhances quality control and system
 security. It also allows the easy retrieval of "old" values (e.g., "address",
 "maiden name," and so on). 
  
  STATUS: Active
KEYWORDS: auditing
COMPONENT/ENTRY POINT: TURNON()
 COMPONENT DESCRIPTION:   This is a utility to enable/disable auditing.  
  
 This procedure turns on (or off) auditing for specified fields in a file 
 (except for Computed and Word-Processing fields).  These changes are recorded
 in the Data Dictionary audit, if the file has Data-Dictionary auditing turned
 on.  Also, input templates containing the changed fields are recompiled. 
  
 Usage: 
  
 D TURNON^DIAUTL(file,field,mode) 
  
 Examples: 
  
 To turn on auditing for the STOP CODE NUMBER (#8) field in the HOSPITAL
 LOCATION (#44) file: 
  
 D TURNON^DIAUTL(44,8) or D TURNON^DIAUTL(44,8,"y") 
  
 To turn off auditing for that field: 
  
 D TURNON^DIAUTL(44,8,"n") 
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File number of a file which is being
 audited. 
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Specifies which fields from the file will
 be forced on ("ALWAYS") for auditing.  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 will be audited.  
  
 - * meaning, "audit all fields." 
  
VARIABLES: MODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an optional parameter. It defaults to "y",
 which means to turn on auditing.  
  
 y - Yes, always audit (default). Turn auditing on.  e - Audit only when edited
 or deleted.  n - No, don't audit. Turn auditing off.  
  
COMPONENT/ENTRY POINT: LAST()
 COMPONENT DESCRIPTION:   This extrinsic function uses the audit trail to
 retrieve the last user who touched a particular field value, and the date/time
 when this editing occurred.  
  
 Usage: 
  
  W $$LAST^DIAUTL(file,entry,field) 
  
 Example: 
  
 Find who last changed demographics of entry number 666 in File #2.  
  
    >W $$LAST^DIAUTL(2,666,"0:1") 
     3000708.103432^78 
  
 In this example, user number 78 was the user who most recently changed any of 
 the audited fields numbered between 0 and 1 in this Entry.  This user did so 
 on 8 July, 2000 at 10:34 AM.  
  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File number of a file which is being
 audited.  
  
VARIABLES: ENTRY                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Entry number in the audited file.  
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Specifies which fields in the audited file
 are to be examined for audit history.  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.  
  
  
COMPONENT/ENTRY POINT: CHANGED()
 COMPONENT DESCRIPTION:   This procedure returns a list of IENs of entries that
 have had audit events within a specified time period. Optionally, the oldest
 value of each audited field within that time period is returned with each
 entry.  
  
 Usage: 
  
 DO CHANGED^DIAUTL(FILE,FIELD,FLAG,TARGET_ROOT,START_DATE,END_DATE) 
  
 NOTE: CHANGED^DIAUTL can only retrieve what is recorded in the VA FileMan
 AUDIT file (#1.1),  and does not look at subfiles (Multiple fields). Data
 entry events that happen before auditing is turned on for a particular field
 are not recorded.  
  
 Also, if the PURGE DATA AUDITS option [DIAUDIT PURGE DATA] is run, information 
 from the audit trail is removed.  
  
 Examples: 
  
 Example 1 
  
 Find which entries in (fictitious) File #999000 have been changed since 
 yesterday.  
  
     >S %DT="",X="T-1" D ^%DT,CHANGED^DIAUTL(999000,"*","","^TMP($J)",Y) 
  
     ^TMP($J,7)="" 
     ^TMP($J,4878)="" 
     ^TMP($J,9899)="" 
  
 Three records have had audited events since yesterday at 12:01 AM.  
  
 Example 2 
  
 Find which NAMEs in (fictitious) File #999000 have ever been changed, and 
 retrieve the original NAMEs.  
  
     >D CHANGED^DIAUTL(999000,.01,"O","ARRAY")  ZW ARRAY 
  
     ARRAY(344)="" 
     ARRAY(344,.01)="DELETED,DAVID" 
     ARRAY(477)="" 
     ARRAY(477,.01)="UNMARRIED,UNA" 
  
 Two records are found, because the audit status of the .01 field of this file 
 is "EDITED OR DELETED". Entry 344 no longer exists. Entry 477 has a  new 
 married name. It is the EXTERNAL version of the old value that is returned. If 
 the name was changed twice in the time period, the oldest value would be 
 returned. 
  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File number of a file which is being
 audited.  
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Specifies which fields in the audited file
 are to be examined for audit history.  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 number within this range are retrieved.  
                             
 - * for all fields.  
  
  
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) "O" if the "oldest" values within the
 specified time period are to be returned.  Without the "O" parameter, the API
 returns only the entry numbers.  
  
VARIABLES: TARGET_ROOT                  TYPE: Both
 VARIABLES DESCRIPTION:   Input: (Required) The name of a closed root
 reference.  
  
 Output: The output array is found in TARGET_ROOT(IEN)=""oldest values, if
 requested by the "O" parameter, are in TARGET_ROOT(IEN,field#) 
  
VARIABLES: START_DATE                   TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Beginning date/time (VA FileMan format) of
 the auditing period.  If no START_DATE is specified, the file's audit history
 is scanned from its earliest date/time.  
  
VARIABLES: END_DATE                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Ending date/time (VA FileMan format) of
 the auditing period. If no END_DATE specified, the file's audit history is
 scanned through its most recent date/time.  
  
  DATE ACTIVATED: FEB 05, 2016

NUMBER: 4398                            IA #: 4398
  DATE CREATED: APR 09, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VAUTOMA                      NAME: DBIA4398
  ID: VAUTOMA                           STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: VAUTOMA
COMPONENT/ENTRY POINT: FIRST
 COMPONENT DESCRIPTION:   Used to select entries from various files
 (INSTITUTION #4, FEE BASIS PROGRAM FILE #161.8, etc.) 
VARIABLES: VAUTVB                       TYPE: Input
 VARIABLES DESCRIPTION:   Is used to specify output local array to return back
 a list of selected items.  
VARIABLES: VAUTSTR                      TYPE: Input
 VARIABLES DESCRIPTION:   The text which will be used in the prompt 
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   Explicit global root in the form ^GLOBAL( or
 ^GLOBAL(X,Y, of the file from which the selection will be made.  
VARIABLES: VAUTNI                       TYPE: Input
 VARIABLES DESCRIPTION:   Set VAUTNI equal to 1 to have output array format of
 subscript being the internal value of the #.01 field and the string value
 being the record's IEN.  
  
 Set VAUTNI equal to 2 to have the output array format of subscript being the
 record's IEN and the string value being the internal value of the #.01 field.  
  
 Set VAUTNI equal to 3 to have the output array format of subscript being the
 external value of the #.01 field and the string value being the record's IEN.  
VARIABLES: VAUTNALL                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional)  Define this variable if you do not want
 the user to be given the ALL option.  
VARIABLES: local array                  TYPE: Output
 VARIABLES DESCRIPTION:   The local array will contain a list of selected
 items. The array's name is specified by the input variable VAUTVB. The format
 is specified by the input variable VAUTNI. The array is not built if the user
 accepted "ALL" at the Select prompt.  
VARIABLES: local variable               TYPE: Output
 VARIABLES DESCRIPTION:   The local variable whose name is specified by the
 VAUTVB input variable has the value "1" if the user accepted the "ALL" value
 at the Select prompt or the value "0" if the user either specified individual
 entries or failed to select any entries.  
SUBSCRIBING PACKAGE: FEE BASIS          ISC: Albany
  DATE ACTIVATED: SEP 08, 2015

NUMBER: 4399                            IA #: 4399
  DATE CREATED: APR 13, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: Local FileMan Array DIPA()
 GENERAL DESCRIPTION:   Allow usage of the DIPA() array for developers.  
  STATUS: Active
COMPONENT/ENTRY POINT: SETPARAM(value,"parameter")
 COMPONENT DESCRIPTION:   Allow read only usage of DIPA() array.  
VARIABLES: DIPA()                       TYPE: Output
 VARIABLES DESCRIPTION:   When the VA FileMan function
 SETPARAM(value,"parameter") is used the information is stored in the local
 array DIPA("parameter")=<value>.  This IA is to allow the read only usage of
 this array.  

NUMBER: 4400                            IA #: 4400
  DATE CREATED: APR 12, 2004            CUSTODIAL PACKAGE: IFCAP
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: PRCLOP11
  NAME: DBIA4400 MODIFY OPTIONS FOR LSSD SHUTDOWN
  ID: PRCLOP11
 GENERAL DESCRIPTION:   
  
 At the beginning of a site's conversion to CoreFLS software, the Legacy 
 Software Shut Down (LSSD) program is run to convert the IFCAP, AEMS/MERS, and
 Equipment/Turn-In Request packages to a read-only state.  These packages will
 be referred to as legacy packages.  One of the steps in the program is
 disabling any options in the legacy systems which could effect an addition,
 modification, or deletion of data to the site's VistA database. All legacy
 options are disabled except those in a pre-determined list, which is known as
 the 'Options to Leave ALone' list.  The list is in the LSSD (#449.1) file and
 will be referred to here as the List.  
  
 Before a site converts to CoreFLS, the site will continue to install patches
 as necessary to fix bugs or add functionality to the legacy packages.  When
 adding functionality, a patch may add or enhance or delete an option or group
 of options.  Later on, when the site runs the LSSD shutdown and converts to
 CoreFLS, the site may need to continue using the functionality provided by
 those new options.  In that case, it will become necessary to prevent those
 options from being disabled by the shutdown.  To do this, the options must
 have been added to the List before the shutdown was run.  Likewise, there may
 be options in the List that a future patch may remove or enhance such that
 those options should be disabled by the legacy shutdown.  Those options should
 then be removed from the List before the legacy shutdown is run.  This IA
 describes the API that patch developers should use to add or remove options
 from the List.  The API must be invoked in the post-install executable of a 
 patch.  
  
 In any patch that uses this API, the patch must also include a patch 
 dependency for the LSSD patch, PRC*5.1*65.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: CoreFLS
KEYWORDS: LSSD
COMPONENT/ENTRY POINT: MODLAO
 COMPONENT DESCRIPTION:   API TO ADD OR DELETE OPTIONS FROM THE 'OPTIONS TO
 LEAVE ALONE' FIELD (#3) OF THE CoreFLS LEGACY SOFTWARE SHUT DOWN (#449.1)
 FILE.  
VARIABLES: PRCLMOD                      TYPE: Input
 VARIABLES DESCRIPTION:   This is an array that will contain the options that
 will be added or removed from the 'Options to Leave Alone' list.  The array
 structure will be as follows: 
  
 PRCLMOD(0) - must contain either a 1 or a 0 
     1 means the other elements in the array are options to add to the List 
     0 means the other elements in the array are options to be removed from 
     the List 
  
 PRCLMOD(n) - n is from 1 to the number of options to be added or removed.  
 Each element contains the Internal Option Name (file #19, field .01) of an 
 option to be either added to or removed from the List, depending on the value
 in PRCLMOD(0).  

NUMBER: 4401                            IA #: 4401
  FILE NUMBER: 991.1                    GLOBAL ROOT: RGHL7(991.1,
  DATE CREATED: APR 23, 2004
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: EXCEPTION PURGE
  ID: RGHL7(991.1,
GLOBAL REFERENCE: RGHL7(991.1,
FIELD NUMBER: .01                       FIELD NAME: NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Internal entry number for ^RGHL7(991.1, CIRN HL7
 EXCEPTION LOG FILE.  
 GLOBAL DESCRIPTION:   Where Patient file (#2) records exist in the following
 form: 
  
 DPT(123,0)=^^^^^^^^^^^^^3 DPT(123,"MPI")=516123456^123456^500^^^^ 
  
 purge exceptions existing for the record using FileMan API ^DIK.  
 GENERAL DESCRIPTION:   The Registration package is writing a clean-up routine
 to purge patient records that exist with only the CURRENT MEANS TEST INDICATOR
 field (#.14) and the MPI node existing.  We are also checking the CIRN HL7 
 EXCEPTION LOG file (991.1) and purging exceptions if they exist for these 
 records.  Registration is requesting an integration agreement with the CIRN
 package to purge these exceptions.  
  STATUS: Active
KEYWORDS: EXCEPTION
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4402                            IA #: 4402
  FILE NUMBER: 81                       GLOBAL ROOT: DD(81
  DATE CREATED: APR 22, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: ID Nodes in CPT file (#81)      ID: DD(81
 GENERAL DESCRIPTION:   The Code Text Descriptors project modifies the
 identifier on the SHORT NAME (#2) field in the CPT file (81).  
  
 The new identifier makes a function call into $$IDCPS^ICPTID to return
 versioned data for both the SHORT NAME and the status in the INACTIVE FLAG. 
 The function has one input parameter, the Internal Entry Point for file #81. 
 Routine ICPTID will also look to see if the package namespaced variable
 ICPTVDT is in the environment.  ICPTVDT is a versioning date.  If ICPTVDT is
 not found in the environment (not supplied) then TODAY will be used and the
 SHORT NAME and INACTIVE FLAG for TODAY will be displayed.  If the variable
 ICPTVDT is found in the environment, and is a date other than TODAY, then the
 appropriate SHORT NAME and INACTIVE FLAG will be displayed for the date.  
  
 The identifiers will be changed to: 
  
 ^DD(81,0,"ID",2)= D EN^DDIOL(("  "_$$IDCPS^ICPTID(+Y)),"","?0") D:$D(SRSITE)
 ^SROCPT 
  
 This will be exported in the combined build CTD UTIL 1.0, containing
 ICPT*6.0*19, ICD*18.0*12 and LEX*2.0*30.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICPTID
SUBSCRIBING PACKAGE: CPT/HCPCS CODES    ISC: Albany

NUMBER: 4403                            IA #: 4403
  FILE NUMBER: 81.3                     GLOBAL ROOT: DD(81.3
  DATE CREATED: APR 22, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: ID Nodes in CPT Modifier file (#81.3)
  ID: DD(81.3
 GENERAL DESCRIPTION:   The Code Text Descriptors project modifies the
 identifier on the NAME (#.02) field in the CPT Modifier file (81.3).  
  
 The new identifier makes a function call into $$IDMDS^ICPTID to return
 versioned data for both the NAME and the status in the INACTIVE FLAG.  The
 function has one input parameter, the Internal Entry Point for file #81.3. 
 Routine ICPTID will also look to see if the package namespaced variable
 ICPTVDT is in the environment.  ICPTVDT is a versioning date.  If ICPTVDT is
 not found in the environment (not supplied) then TODAY will be used and the
 NAME and INACTIVE FLAG for TODAY will be displayed.  If the variable ICPTVDT
 is found in the environment, and is a date other than TODAY, then the
 appropriate NAME and INACTIVE FLAG will be displayed for the date.  
  
 The identifier will be changed to: 
  
 ^DD(81.3,0,"ID",.02)= D EN^DDIOL(("  "_$$IDMDS^ICPTID(+Y)),"","?0") 
  
 This will be exported in the combined build CTD UTIL 1.0, containing 
 ICPT*6.0*19, ICD*18.0*12 and LEX*2.0*30.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICPTID
SUBSCRIBING PACKAGE: CPT/HCPCS CODES    ISC: Albany

NUMBER: 4404                            IA #: 4404
  FILE NUMBER: 80                       GLOBAL ROOT: DD(80
  DATE CREATED: APR 22, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: ID Nodes in ICD Dx file (#80)   ID: DD(80
 GENERAL DESCRIPTION:   The Code Text Descriptors project modifies the
 identifier on the DIAGNOSIS (#3) field in the ICD DIAGNOSIS file (80).  
  
 The new identifier makes a function call into $$IDDXS^ICDID to return
 versioned data for both the DIAGNOSIS and the status in the INACTIVE FLAG. 
 The function has only one input parameter, the Internal Entry Number for file
 #80.  Routine ICDID will also look to see if the package namespaced variable 
 ICDVDT is in the environment.  ICDVDT is a versioning date. If ICDVDT is not
 found in the environment (not supplied) then TODAY will be used and the
 DIAGNOSIS and INACTIVE FLAG for TODAY will be displayed.  If the variable
 ICDVDT is found in the environment, and is a date other than TODAY, then the 
 appropriate DIAGNOSIS and INACTIVE FLAG will be displayed for the date.  
  
 The identifier will be changed to: 
  
 ^DD(80,0,"ID",3)= D EN^DDIOL((" "_$$IDDXS^ICDID(+Y)),"","?0") 
    
 This will be exported in the combined build CTD UTIL 1.0, containing
 ICPT*6.0*19, ICD*18.0*12 and LEX*2.0*30.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICDID
SUBSCRIBING PACKAGE: DRG GROUPER        ISC: Albany

NUMBER: 4405                            IA #: 4405
  FILE NUMBER: 80.1                     GLOBAL ROOT: DD(80.1
  DATE CREATED: APR 22, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: ID Nodes in ICD OP file (#80.1)
  ID: DD(80.1
 GENERAL DESCRIPTION:   The Code Text Descriptors project modifies the
 identifier on the OPERATION/PROCEDURE (#4) in the ICD OPERATION/PROCEDURE file
 (80.1).  
  
 The new identifier makes a function call into $$IDOPS^ICDID to return
 versioned data for both the OPERATION/PROCEDURE and the status in the INACTIVE
 FLAG.  The function has only one input parameter, the Internal Entry Number
 for file #80.1.  Routine ICDID will also look to see if the package namespaced 
 variable ICDVDT is in the environment.  ICDVDT is a versioning date.  If
 ICDVDT is not found in the environment (not supplied) then TODAY will be used
 and the OPERATION/PROCEDURE and INACTIVE FLAG for TODAY will be displayed.  If
 the variable ICDVDT is found in the environment, and is a date other than 
 TODAY, then the appropriate OPERATION/PROCEDURE and INACTIVE FLAG will be
 displayed for the date.  
  
 The identifiers will be changed to: 
  
 ^DD(80.1,0,"ID",4)= D EN^DDIOL((" "_$$IDOPS^ICDID(+Y)),"","?0") 
  
 This will be exported in the combined build CTD UTIL 1.0, containing
 ICPT*6.0*19, ICD*18.0*12 and LEX*2.0*30.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICDID
SUBSCRIBING PACKAGE: DRG GROUPER        ISC: Albany

NUMBER: 4406                            IA #: 4406
  FILE NUMBER: 80.2                     GLOBAL ROOT: DD(80.2
  DATE CREATED: APR 22, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: ID Nodes in DRG file (#80.2)    ID: DD(80.2
 GENERAL DESCRIPTION:   The Code Text Descriptors project modifies the
 identifier on the INACTIVE (#15) field of the DRG file (80.2).  
  
 The new identifier makes a function call into $$IDDGS^ICDID to return
 versioned data for both the DESCRIPTION and the status in the INACTIVE field. 
 The function has only one input parameter, the Internal Entry Number for file
 #80.2. Routine ICDID will also look to see if the package namespaced variable 
 ICDVDT is in the environment.  ICDVDT is a versioning date.  If ICDVDT is not
 found in the environment (not supplied) then TODAY will be used and the
 DESCRIPTION and INACTIVE fields for TODAY will be displayed.  If the variable
 ICDVDT is found in the environment, and is a date other than TODAY, then the 
 appropriate DESCRIPTION and INACTIVE fields will be displayed for the date.  
  
 The identifiers will be changed to: 
  
 ^DD(80.2,0,"ID",15)= D EN^DDIOL((" "_$$IDDGS^ICDID(+Y)),"","?0") 
    
 This will be exported in the combined build CTD UTIL 1.0, containing
 ICPT*6.0*19, ICD*18.0*12 and LEX*2.0*30.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICDID
SUBSCRIBING PACKAGE: DRG GROUPER        ISC: Albany

NUMBER: 4407                            IA #: 4407
  GLOBAL ROOT: RCCSTM                   DATE CREATED: APR 19, 2004
  CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: File
  NAME: DBIA4407                        ID: RCCSTM
 GENERAL DESCRIPTION:   In order to protect against loosing the set up for the
 customization features in the ^DISV global, patch PRCA*4.5*217 requests
 approval to create the ^RCCSTM global to store the selections within the CU 
 Customize option. This will allow the most recently selected parameters and
 printers to be recalled by a user when customizing the screen and setting up
 the printer options.  
  
 The information is stored in ^RCCSTM(DUZ,"RCDPRPLM",SCREEN/OPTION).       An
 example is in routine RCDPRPL2 at line RCDPRPL2+124:                     S
 ^RCCSTM(DUZ,"RCDPRPLM","RECEIPT")=TYPE_"^"_DEVICE 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed

NUMBER: 4408                            IA #: 4408
  DATE CREATED: JUN 24, 2004            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGIBDSP
  NAME: DBIA4408                        ID: DGIBDSP
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: INSURANCE
KEYWORDS: DISPLAY
COMPONENT/ENTRY POINT: DISP
 COMPONENT DESCRIPTION:   This tag can be called to provide a standard,
 formatted Insurance display.  The Insurance Information is retrieved through
 INSUR^IBBAPI (DBIA4419).  The variable DFN must be defined to the current
 patient.  Information from the BILLING PATIENT File (#354) and the INSURANCE
 BUFFER File (#355.33) will not be included.  This call is intended as a 
 replacement for a retired IB API, the formatted display will appear as in the
 retired API call.  
  
 Example:  S DFN=12345 D DISP^DGIBDSP 
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4409                            IA #: 4409
  DATE CREATED: APR 23, 2004            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUP                          NAME: XUP
  ID: XUP
 GENERAL DESCRIPTION:   Supported APIs or extrinsic function in routine XUP.  
  STATUS: Active
COMPONENT/ENTRY POINT: $$DTIME
 COMPONENT DESCRIPTION:   This extrinsic function will reset the DTIME variable
 for user identified by the first parameter 'DUZ' of this function.  
  
 This extrinsic function accepts two parameters.  The first is the ien or DUZ
 of the user in the NEW PERSON file (#200).  
  
 The second is the ien of the device in the DEVICE file (#3.5).  This ien
 should be the same value of IOS if present, and should reflect the current
 sign-on device of the user.  
  
 The return value should be assigned to the variable DTIME as shown in the
 USAGE example.  This DTIME variable will be used on all timed READS where
 interactive responses are required for a given user.  
  
 The return value will be based on the first available data if present, and in
 the search order listed below: 
  
  (#200.1) TIMED READ (# OF SECONDS)      of      NEW PERSON file (#200) 
  (#51.1) TIMED READ (# OF SECONDS)       of      DEVICE file (#3.5) 
  (#210) DEFAULT TIMED-READ (SECONDS)     of      KERNEL SYSTEM PARAMETERS file
 (#8989.3) 
  
 If data is not available from the above fields, then the return value will
 default to 300 seconds.  
  
         USAGE:  S DTIME=$$DTIME^XUP(DUZ) 
                         or 
                 S DTIME=$$DTIME^XUP(DUZ,IOS) 
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The ien of the user in the NEW PERSON file (#200).  
VARIABLES: IOS                          TYPE: Input
 VARIABLES DESCRIPTION:   The ien of the device in the DEVICE file (#3.5).  

NUMBER: 4410                            IA #: 4410
  DATE CREATED: NOV 10, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: BPSUTIL                      NAME: BPSUTIL
  ID: BPSUTIL
 GENERAL DESCRIPTION:   This routine contains several APIs which are used to
 retrieve some specific information from ECME.  $$ECMEON is used to verify if
 the ECME Application is turned ON or OFF.  Other applications, such as
 Outpatient Pharmacy, need to verify this switch before submitting a
 prescription to be electronically billed.  $$CMOPON is used to verify if the
 ECME CMOP switch is ON or OFF.  $$BPSPLN returns the insurance PLAN NAME field
 for a particular BPS TRANSACTION file entry.  $$BPSINSCO returns the Insurance
 Company (902.33) field from the BPS TRANSACTION file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NCPDP
KEYWORDS: HIPAA
KEYWORDS: ECME
COMPONENT/ENTRY POINT: $$ECMEON(SITE)
 COMPONENT DESCRIPTION:   Switch to check if the ECME application is ON or OFF. 
 
VARIABLES: SITE                         TYPE: Input
 VARIABLES DESCRIPTION:   Outpatient Site IEN (Pointer to OUTPATIENT SITE File
 (#59)).  
VARIABLES: $$ECMEON                     TYPE: Output
 VARIABLES DESCRIPTION:   
   0  -  ECME Application is OFF 
   1  -  ECME Application is ON 
COMPONENT/ENTRY POINT: $$CMOPON(SITE)
 COMPONENT DESCRIPTION:   Used to check if the CMOP ePharmacy switch is ON or
 OFF.  
VARIABLES: SITE                         TYPE: Input
 VARIABLES DESCRIPTION:   Outpatient Site IEN (Pointer to OUTPATIENT SITE file
 59.  
VARIABLES: $$CMOPON                     TYPE: Output
 VARIABLES DESCRIPTION:   
  0 - CMOP Switch is OFF 
  1 - CMOP Switch is ON 
COMPONENT/ENTRY POINT: $$BPSPLN(RXI,RXR)
 COMPONENT DESCRIPTION:   Returns the insurance PLAN NAME field (#902.24) value
 from the BPS TRANSACTION file (#9002313.59).  
VARIABLES: RXI                          TYPE: Input
 VARIABLES DESCRIPTION:   Prescription File IEN (Pointer to PRESCRIPTION file
 52).  
VARIABLES: RXR                          TYPE: Input
 VARIABLES DESCRIPTION:   Refill Number (0 for original fill) 
VARIABLES: $$BPSPLN                     TYPE: Output
 VARIABLES DESCRIPTION:   The insurance PLAN NAME field (#902.24) value for the
 related entry in the BPS TRANSACTION file.  
COMPONENT/ENTRY POINT: $$BPSINSCO(RXI,RXR)
 COMPONENT DESCRIPTION:   Returns the Insurance Company (902.33) field from BPS
 TRANSACTION.  
VARIABLES: RXI                          TYPE: Input
 VARIABLES DESCRIPTION:   Prescription File IEN (Pointer to PRESCRIPTION file
 52).  
VARIABLES: RXR                          TYPE: Input
 VARIABLES DESCRIPTION:   Refill Number (0 for original fill).  
VARIABLES: $$BPSINSCO                   TYPE: Output
 VARIABLES DESCRIPTION:   The Insurance Company field (902.33) from the BPS
 TRANSACTION file.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham
  DATE ACTIVATED: FEB 13, 2007

NUMBER: 4411                            IA #: 4411
  DATE CREATED: NOV 10, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: BPSECMP2                     NAME: BPSECMP2
  ID: BPSECMP2
 GENERAL DESCRIPTION:   This API is used to send billing information from ECME
 to IB.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
KEYWORDS: HIPAA
KEYWORDS: NCPDP
COMPONENT/ENTRY POINT: IBSEND(CLAIMIEN,RESPIEN,EVENT,USER)
VARIABLES: CLAIMIEN                     TYPE: Used
VARIABLES: EVENT                        TYPE: Input
 VARIABLES DESCRIPTION:   BPS CLAIMS IEN (Pointer to the BPS CLAIMS File 
                            (#9002313.02)) 
VARIABLES: RESPIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   BPS RESPONSES IEN (Pointer to the BPS RESPONSES File 
                            (#9002313.03)) 
VARIABLES: I                            TYPE: Input
 VARIABLES DESCRIPTION:   The Flag is used by PSO to create specific events.
 Can be 
                            either null or "BILL" 
VARIABLES: USER                         TYPE: Input
 VARIABLES DESCRIPTION:   NEW PERSON IEN (Pointer to the NEW PERSON File 
                            (#200)), the user who is creating the event. This 
                             is required when EVENT is sent.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 4412                            IA #: 4412
  DATE CREATED: JUN 21, 2004            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: BPSOSRX                      NAME: BPSOSRX
  ID: BPSOSRX
 GENERAL DESCRIPTION:   This API is used by external applications to inquire
 about the status of a ECME Claim.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BPS
KEYWORDS: ECME
KEYWORDS: HIPAA
KEYWORDS: NCPDP
COMPONENT/ENTRY POINT: $$STATUS(RXI,RXR,QUE,BPRQIEN,BPCOB)
 COMPONENT DESCRIPTION:   This function will return the status of the ECME
 claim 
VARIABLES: RXI                          TYPE: Input
 VARIABLES DESCRIPTION:   Presription IEN (Pointer to the PRESCRIPTION File
 (#52)) - Required 
VARIABLES: RXR                          TYPE: Input
 VARIABLES DESCRIPTION:   Fill Number (0 for Original, 1 for 1st refill, 2 for
 the 2nd refill, etc.) - Required 
VARIABLES: QUE                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an optional variable that indicates whether
 the processing queue should be checked when determining the status of the RX
 and fill.  
  
 If this parameter is not passed in, it will be defaulted to 1.  
  
 Note: Only internal functions within ECME should set this parameter to 0.  
  
 Values: 
   0 - Do not check the processing queue.  
   No value, NULL, or 1 - Check the processing queue.  
VARIABLES: $$STATUS                     TYPE: Output
 VARIABLES DESCRIPTION:   This API returns a four piece string with the 
 following information: 
  
  1: CLAIM CATEGORY: E PAYABLE      E REJECTED 
                     E DUPLICATE    E CAPTURED 
                     E STRANDED     E OTHER 
                     CORRUPT        CANCELLED 
                     E REVERSAL ACCEPTED 
                     E REVERSAL REJECTED 
                     E REVERSAL STRANDED 
                     E REVERSAL OTHER 
                     IN PROGRESS 
  
  2: DATE/TIME OF LAST UPDATE (FM Format) 
  
  3: FREETEXT STATUS Explanation 
     This will vary dependent on the claim 
     category (first piece).  
     
     If the claim category is IN PROGRESS, this 
     piece will have the currect progress status 
     (i.e., Waiting to Start, Transmitting) 
  
     If the claim category is E OTHER, this piece 
     may have an error message for why the claims 
     process stopped (i.e., Patient missing from 
     BPS Transaction).  
     
     If the claim category has one of the other 
     statuses, this piece will have a value 
     indicating the number of submission to the 
     payer (i.e., Payable[Previously: Payable] 
  
  4: COMPLETION PERCENTAGE 
     Note that 99 is considered complete.  
  
     Examples: 
     --------
     IN PROGRESS^3040608.152544^Transmitting^60 
     E OTHER^3040921.130145^Patient missing from BPS Transaction^40 
     E PAYABLE^3040527.150818^Payable[Previously: Payable]^99 
     E REVERSAL ACCEPTED^3040421.19091^Payable^99 
VARIABLES: BPRQIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   (optional) The BPS REQUESTS file (#9002313.77)
 internal entry number.  
VARIABLES: BPCOB                        TYPE: Input
 VARIABLES DESCRIPTION:   (optional) The payer sequence (1 - Primary, 2 -
 Secondary). If null then 1 (Primary) is assumed.  
COMPONENT/ENTRY POINT: $$IEN59(KEY1,KEY2,BPCOBIND)
 COMPONENT DESCRIPTION:   This function returns the IEN for BPS TRANSACTION,
 file #9002313.59.  
VARIABLES: KEY1                         TYPE: Input
 VARIABLES DESCRIPTION:   Either Prescription IEN (pointer to the PRESCRIPTION
 file #52) or Patient IEN (pointer to PATIENT file #2) 
VARIABLES: KEY2                         TYPE: Input
 VARIABLES DESCRIPTION:   Either Fill Number (0 for original, 1 for 1st refill,
 2 for 2nd refill, etc.) or Policy Number.  If Policy Number, the value should
 be 9000 plus the Policy Number.  
VARIABLES: BPCOBIND                     TYPE: Input
 VARIABLES DESCRIPTION:   COB indicator (1=primary, 2=secondary, 3=tertiary) 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: AUG 25, 2010

NUMBER: 4413                            IA #: 4413
  DATE CREATED: NOV 09, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         ROUTINE: BPSECFM
  NAME: DBIA4413                        ID: BPSECFM
 GENERAL DESCRIPTION:   This API is used to format NDC codes: NNNNN-NNNN-NN 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: BPS
KEYWORDS: ECME
KEYWORDS: HIPAA
KEYWORDS: NCPDP
COMPONENT/ENTRY POINT: $$NDCF(X)
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   NDC number to be formatted. It must be 11 numerics
 (no dashes or other punctuation).  
VARIABLES: $$NDCF                       TYPE: Output
 VARIABLES DESCRIPTION:   NDC number formatted: NNNNN-NNNN-NN Note: If an
 invalid X (input) is passed, returns X.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham

NUMBER: 4414                            IA #: 4414
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: GMV MARK ERROR
  REMOTE PROCEDURE: GMV MARK ERROR
 GENERAL DESCRIPTION:   
  NAME: GMV MARK ERROR 
  TAG: ERROR                           
  ROUTINE: GMVUTL1 
  RETURN VALUE TYPE: SINGLE VALUE      
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE 
  DESCRIPTION:   
  This remote procedure call marks a selected vitals record in the GMRV 
  Vital Measurement (#120.5) file as entered-in-error.  
   
  This remote procedure call is documented in Integration Agreement 4414.  
  INPUT PARAMETER: GMVDATA               
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 60              
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  GMVDATA contains the following information: 
   
   piece1^piece2^piece3 
   
   where piece1 = FILE 120.5 IEN 
         piece2 = FILE 200 IEN (i.e., DUZ) 
         piece3 = A single value to indicate the reason for the error.  
                  1 = INCORRECT DATE/TIME, 2 = INCORRECT READING, 3 = 
                  INCORRECT PATIENT and 4 = INVALID RECORD 
  RETURN PARAMETER DESCRIPTION:   
  If the record is marked as entered in error, RESULT is set to "OK".  
  Otherwise, RESULT is set to "Record Not Found" 
   
   Example: 
   > S GMVDATA="1560^547^1" 
   > D ERROR^GMVUTL1(.RESULT,GMVDATA) ZW RESULT 
   > RESULT="OK" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP*2.0*2 
  
 **************************************************** 
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                   
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
 ****************************************************

NUMBER: 4415                            IA #: 4415
  DATE CREATED: JUN 21, 2004            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: BPSNCPDP                     NAME: BPSNCPDP
  ID: BPSNCPDP
 GENERAL DESCRIPTION:   This API is used by external applications to generate
 claims in the Electronic Claims Management Engine.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BPS
KEYWORDS: ECME
KEYWORDS: HIPAA
KEYWORDS: NCPDP
COMPONENT/ENTRY POINT: $$EN
 COMPONENT DESCRIPTION:   This Component is called with the variables outlined
 in the following format: 
   $$EN(BRXIEN,BFILL,DOS,BWHERE,BILLNDC,REVREAS,DURREC, 
   BPOVRIEN, BPSCLARF,BPSAUTH,BPCOBIND,BPJOBFLG,BPREQIEN, 
   BPSCLOSE,BPSPLAN,BPSPRDAT,BPSRTYPE,BPSDELAY) 
  
 This API returns seven "^" pieces of information.  
   RESPONSE 
     0  Submitted through ECME 
     1  No submission through ECME 
     2  IB not billable 
     3  Claim was closed, not submitted (RTS/Deletes) 
     4  Unable to queue claim 
     5  Incorrect information supplied to ECME 
     6  Inactive ECME - Primarily used for TRICARE and 
         CHAMPVA to say OK to calling application 
         (Outpatient Pharmacy) to process the 
         prescription 
     10 Reversal but no resubmit 
   MESSAGE 
     Text message with more details regarding the reason the 
     claim was not submitted to the payer or more information 
     on the successful submission.  
   ELIGIBILITY 
     Patient eligibility: V-Veteran, T-TRICARE, C-CHAMPVA 
   CLAIM STATUS 
     The current claim status: 
     Null or IN PROGRESS/E PAYABLE/etc...  
   COB 
     Coordination Of Benefits indicator of the insurance as 
     it is stored in the PATIENT file: 
     1 - Primary, 2 - Secondary, 3 - Tertiary 
   RXCOB 
     The payer sequence indicator of the claim which was sent 
     to the payer as a result of the call: 
     1 - Primary, 2 - Secondary, 3 - Tertiary 
   INSURANCE 
     Name of the insurance company that was billed as a result 
     of the call.  
  
  
   Examples: 
  
     0^Prescription XYZ successfully submitted to ECME for 
       claim generation.^V^E PAYABLE^1^1^AETNA 
     0^Prescription XYZ successfully submitted to ECME for 
       claim generation.^V^E PAYABLE^3^2^BCBS 
     1^ECME switch is not on for the site^^E REVERSAL ACCEPTED 
     2^Null DEA Special Handling field^V^ 
     3^Claim was not payable so it has been closed.  No ECME 
       claim created. ^^E REJECTED 
     4^Error: There is a SCHEDULED request without ACTIVATED 
       requests, RXIEN=XYZ, REFILL=0^^IN PROGRESS 
     5^RX Action parameter missing^^E PAYABLE 
VARIABLES: BRXIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Internal Entry Number of PRESCRIPTION File
 (#52) 
VARIABLES: BFILL                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Fill Number (0 for Original, 1 for 1st
 refill, 2 for the 2nd refill, etc.). This will be defaulted to 0 if not passed
 in.  
VARIABLES: DOS                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Date of Service. If not passed in or has a
 future  date, it is set to the Release Date of the Prescription and Fill.  If
 the Release Date does not have a value, it is set to the current date.  
VARIABLES: BWHERE                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) 
  
 Calling Function: 
   AREV - Auto-Reversal 
   BB   - Back Billing 
   CRLB - CMOP/OPAI Release & Rebill 
   CRLR - CMOP/OPAI Release & Reverse 
          (successful release) 
   CRLR - CMOP/OPAI Release & Reverse 
          (successful release) 
   CRRL - CMOP/OPAI Release - Original claim 
          not paid, submit another claim, 
          no reversal 
   DC   - Discontinue - only reverse un-released 
          PAYABLE DC's, release date check 
          should be in calling routine 
   DE   - Delete 
   ED   - Edit (includes RX release with NDC edit) 
   ERES - Resubmit from ECME user screen 
   EREV - Reversal from ECME user screen 
   OF   - Original Fill 
   P2   - Original submission from PRO Option, no 
          reversal 
   P2S  - Resubmit from PRO Option 
   PC   - Pull CMOPs 
   PE   - Pull early from suspense 
   PL   - Pull local from suspense 
   PP   - Pull RX (PP) action from Patient 
          Prescription Processing option 
   RF   - Refill 
   RN   - Renew 
   RRL  - Release - Original claim not paid, 
          submit another claim, no reversal 
   RS   - Return-to-Stock 
VARIABLES: BILLNDC                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) NDC that pharmacist entered at release.
 Only required on release function.  
VARIABLES: REVREAS                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Reversal Reason.  This is only needed for
 reversal events.  It will be defaulted to 'Unknown' if not passed in.  
VARIABLES: DURREC                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) String of up to three sets of DUR info.
 Sets are delimited with "~". Each set consists of the following three "^"
 pieces: 
      Reason for Service Code 
      Professional Service Code 
      Result of Service Code 
VARIABLES: BPOVRIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) IEN of the BPS NCPDP OVERRIDE file.  This
 should always be NULL or not passed with the exception of the Resubmit with
 Edit action on the ECME User Screen.  
VARIABLES: BPSCLARF                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Submission Clarification Code to be
 included in the claim.  
VARIABLES: BPSAUTH                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) String of prior authorization info - Two
 "^" pieces: 
    Piece 1 - Prior Authorization Type Code 
    Piece 2 - Prior Authorization Number 
VARIABLES: BPCOBIND                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Coordination Of Benefits (COB) indicator.  
   1 - Primary Payer (default) 
   2 - Secondary Payer 
VARIABLES: BPJOBFLG                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Background Job Flag 
    B - if is called by unqueueing logic 
        in background 
    F - by other (foreground) process 
VARIABLES: BPREQIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Internal Entry Number of the BPS REQUEST
 file record that needs to be unqueued.  
VARIABLES: BPSCLOSE                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional, By Reference) Local array used for Close
 After Reversal functionality when the user had chosen to close the claim after 
 successful reversal. Used with BWHERE="EREV" only.  If claim needs to be
 closed then: 
  BPSCLOSE("CLOSE AFT REV")=1 
  BPSCLOSE("CLOSE AFT REV REASON")=IEN of the file (#356.8) 
  BPSCLOSE("CLOSE AFT REV COMMENT")=Text of the comment 
VARIABLES: BPSPLAN                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) IEN of the entry in the GROUP INSURANCE
 PLAN file(#355.3) 
VARIABLES: BPSPRDAT                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional, By Reference) Local array passed by
 reference containing data needed to submit a secondary claim.  This parameter
 should only be used internally by ECME and should not by be passed by external
 applications.  
VARIABLES: BPSRTYPE                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Internal Entry Number of RATE TYPE file
 (#399.3) 
VARIABLES: BPSDELAY                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Delay Reason Code that will be entered on
 an NCPCP claim (field 357-NV).  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: JAN 04, 2011

NUMBER: 4416                            IA #: 4416
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: GMV EXTRACT REC
  REMOTE PROCEDURE: GMV EXTRACT REC
 GENERAL DESCRIPTION:   
  NAME: GMV EXTRACT REC 
  TAG: GETVM                            
  ROUTINE: GMVGETD 
  RETURN VALUE TYPE: GLOBAL ARRAY       
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE                     
  WORD WRAP ON: TRUE 
  DESCRIPTION:   
  This remote procedure call retrieves vital records from the GMRV Vital 
  Measurement (#120.5) file for a selected patient within a given date 
  span.  
   
  This remote procedure call is documented in Integration Agreement 4416.  
  INPUT PARAMETER: GMRVDATA               
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 30               
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  GMRVDATA consists of 4 pieces of information: 
   piece1^piece2^piece3^piece4 
   
   where piece1 = Patient (#2) file pointer (i.e., DFN) 
         piece2 = End date of search (FileMan internal format) 
         piece3 = single vital type abbreviation (File 120.51, Field 1) 
                  [optional] If not defined, the default is 
                  "T;P;R;BP;HT;WT;PN;PO2;CG;CVP" 
         piece4 = Start date of search (FileMan internal format) 
  RETURN PARAMETER DESCRIPTION:   
  Returns the name of the global array (i.e., ^TMP($J,"GRPC")) containing a 
  list of vital records for the selected patient within the defined date 
  range.  
   
   The TMP global contains: 
   ^TMP($J,"GRPC",n)=piece1^piece2 
   
   where piece1 = File 120.5 IEN 
         piece2 = a string of text in the following format: 
                  Date/time taken (external)   Vital Type Abbreviation: 
                  Rate U.S. units (Metric value) (Qualifiers) 
              n = sequential number starting at 1.  
   
   
   Example: 
   > S GMRVDATA="134^3051028^BP^3051001" 
   > D GETVM^GMVGETD(.RESULT,GMRVDATA) ZW RESULT 
   > RESULT="^TMP(538999278,"GRPC")" 
   > D ^%G 
   > Global ^TMP($J,"GRPC" 
   > ^TMP(538999278,"GRPC",1)=8858^10/11/05@16:35   B/P:   120/80*  (L 
     ARM, 
     SITTING, CAROTID, CALF) _VITPROVIDER,ONE 
   >                       2)=8961^10/20/05@14:47   B/P:   128/81*  (L ARM, 
     SITTING, PALPATED) _VITPROVIDER,TWO 
   
  If there is no data, then the following is returned: 
   
  ^TMP($J,"GRPC",1)=0^NO VITALS/MEASUREMENTS ENTERED WITHIN THIS PERIOD 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI

NUMBER: 4417                            IA #: 4417
  DATE CREATED: NOV 09, 2005            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMRPCD
  NAME: REMINDER DIALOG DETAILS FOR TIU TEMPLATES IN CPRS
  ID: PXRMRPCD
 GENERAL DESCRIPTION:   This API will accept a Reminder Dialog IEN from file#
 801.41 and a patient DFN.  This API will return the format of a reminder
 dialog.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: CPRS
KEYWORDS: PXRMRPCD
KEYWORDS: REMINDER DIALOGS IN A TEMPLATE
COMPONENT/ENTRY POINT: DIALOG
 COMPONENT DESCRIPTION:   This API will accept a Reminder Dialog IEN from file#
 801.41 and a patient DFN.  This API will return the format of a reminder
 dialog.  
  
VARIABLES: ORDLG                        TYPE: Input
 VARIABLES DESCRIPTION:   ORDLG, is the Reminder Dialog IEN from file# 801.41.  
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN is the patient dfn from file# 2.  
  
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   ORY(0)=Boolean value. The zero subscript of the ORY
 tells the caller if the Dialog patient specific flag is set to true.  
  
 For the rest of the array the ORY(n) is set to either a type 1 or type 2 
 records.  
                             
 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 
                             
  
  
  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4418                            IA #: 4418
  DATE CREATED: APR 28, 2004            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: ADT HL7 MSG
 GENERAL DESCRIPTION:   The following Protocols are Supported for packages to
 hang their protocols on: 
  
  VAFC ADT-A01 SERVER 
  VAFC ADT-A02 SERVER 
  VAFC ADT-A03 SERVER 
  VAFC ADT-A04 SERVER 
  VAFC ADT-A08 SERVER 
  VAFC ADT-A08-SDAM SERVER 
  VAFC ADT-A08-TSP SERVER 
  VAFC ADT-A11 SERVER 
  VAFC ADT-A12 SERVER 
  VAFC ADT-A13 SERVER 
  VAFC ADT-A19 SERVER 
  STATUS: Active
KEYWORDS: VAFC ADT

NUMBER: 4419                            IA #: 4419
  DATE CREATED: MAY 07, 2004            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: IBBAPI                       NAME: DBIA4419
  ID: IBBAPI
 GENERAL DESCRIPTION:   IBBAPI is a new routine to return insurance data to
 calling VistA applications.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IBBAPI
KEYWORDS: insurance
COMPONENT/ENTRY POINT: $$INSUR(DFN,IBDT,IBSTAT,IBR,IBFLDS)
 COMPONENT DESCRIPTION:   Return Patient Insurance Information 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   PATIENT IEN 
VARIABLES: IBDT                         TYPE: Input
 VARIABLES DESCRIPTION:   DATE INSURED (optional - default is today's date) 
VARIABLES: IBSTAT                       TYPE: Input
 VARIABLES DESCRIPTION:   INSURANCE STATUS FILTER (combinable based on groups
 below) 
   Group 1 
     A = Inactive included (Default is active only) 
   Group 2 
     R = Not reimbursable included (Default is reimbursable only) 
     B = Indemnity included (Default is not included) 
   Group 3 
     P = Prescription coverage required (Default is all coverages) 
         (Note: "E" and "P" are mutually exclusive) 
     O = Outpatient coverage required (Default is all coverages) 
     I = Inpatient coverage only (Default is all coverages) 
     E = ePharmacy billable insurance plans only (Default is all coverages) 
         (Note: "E" and "P" are mutually exclusive) 
VARIABLES: IBR                          TYPE: Input
 VARIABLES DESCRIPTION:   Array to return insurance information - passed by
 reference 
VARIABLES: IBFLDS                       TYPE: Input
 VARIABLES DESCRIPTION:   List of fields to return (1-31) in a comma separated
 list.  To receive all fields, pass in an asterisk "*" in place of the numbers
 representing the field(s) you want.  
   1 = Insurance Company Name 
   2 = Insurance Company Street Address Line 1 
   3 = Insurance Company City 
   4 = Insurance Company State 
   5 = Insurance Company Zip 
   6 = Insurance Company Phone 
   7 = Coordination of Benefits 
   8 = Policy Name 
   9 = Policy Reimbursable? 
  10 = Policy Effective Date 
  11 = Policy Expiration Date 
  12 = Subscriber Relationship 
  13 = Subscriber Name 
  14 = Subscriber ID 
  15 = Pharmacy Coverage? 
  16 = Outpatient Coverage? 
  17 = Inpatient Coverage? 
  18 = Group Number 
  19 = Patient Relationship to Subscriber 
  20 = VA Advantage Plan Subscriber (future functionality) 
  21 = Plan Type 
  22 = Subscriber Sex 
  23 = Insurance Company Street Address Line 2 
  24 = Insurance Company Street Address Line 3 
  25 = Date Last Verified 
  26 = Insured's Street 1 
  27 = Insured's Street 2 
  28 = Insured's City 
  29 = Insured's State 
  30 = Insured's Zip 
  31 = Insured's Phone 
VARIABLES: $$INSUR                      TYPE: Output
 VARIABLES DESCRIPTION:   
   -1 = error occurred (error message passed back in IBR("IBBAPI","INSUR", 
                        "ERROR",x) where x is error number between 101 & 111 
    0 = No insurance found based on parameters 
    1 = Insurance found 
  
 If no insurance information is found, then the IBR("IBBAPI","INSUR",y) array
 will not be generated.  
  
 If no errors occur, insurance is found, and IBR is passed by reference, IBR
 will contain the insurance array requested in the following format: 
    IBR("IBBAPI","INSUR",x) = IEN for the policy in 
                              #2.312 
    IBR("IBBAPI","INSUR",x,y) = <field y data> where 'x' is an incremental
 insurance company count (starting with 1) and 'y' is the field number
 requested.  
  
 If an error occurs, the extrinsic function will return -1 and the error codes
 and messages will be returned in IBR("IBBAPI","INSUR","ERROR",error code) =
 error message if IBR is passed by reference.  
COMPONENT/ENTRY POINT: $$CIDC(DFN)
 COMPONENT DESCRIPTION:   The API will evaluate both a CIDC switch and the
 patient's insurance to determine if the CIDC questions should be asked.  
  
 The switch will have three internal values: 
         0 = Don't ask any patients 
         1 = Ask for patients only with active billable insurance 
         2 = Ask for all patients 
  
 See output for the two possible return values.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   PATIENT IEN 
VARIABLES: $$CIDC                       TYPE: Output
 VARIABLES DESCRIPTION:   Output is based on the patient's insurance and the
 switch values: 
  
   1 = Ask CIDC questions for the specified patient 
   0 = Don't ask CIDC questions for the specified patient 
  DATE ACTIVATED: JAN 25, 2023

NUMBER: 4420                            IA #: 4420
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: GMV DLL VERSION
  REMOTE PROCEDURE: GMV DLL VERSION
 GENERAL DESCRIPTION:   
  NAME: GMV DLL VERSION 
  TAG: DLL                              
  ROUTINE: GMVUTL8 
  RETURN VALUE TYPE: SINGLE VALUE       
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE 
  DESCRIPTION:   
  Returns a YES or NO response to indicate if the Dynamic Link Library 
  (DLL) file should be used.  
   
  This remote procedure call is documented in Integration Agreement 4420.  
  INPUT PARAMETER: GMVX                  
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 50              
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  This value is the name of the file and the date/time associated with it 
  (e.g., GMV_VITALSVIEWENTER.DLL:v. 07/21/05 10:34).  
  RETURN PARAMETER DESCRIPTION:   
  Returns YES if the file can be used. Returns NO, if the file cannot be 
  used. Returns null if the file was not found.  
   
  Example: 
   > S GMVX="GMV_VITALSVIEWENTER.DLL:v. 07/21/05 10:34" 
   > D DLL^GMVUTL8(.RESULT,GMVX) ZW RESULT 
   > RESULT="NO" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4421                            IA #: 4421
  DATE CREATED: NOV 14, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  ROUTINE: HLOUSR                       NAME: HLO $$RUNNING
  ID: HLOUSR
 GENERAL DESCRIPTION:   This is a private agreement that is being provided to
 Pharmacy Benefit Mangement as a special consideration due to their partnering
 with HLO to test and release HLO in conjunction with Pharmacy Benefit
 Managment Phase III.  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$RUNNING
 COMPONENT DESCRIPTION:   The function returns 1 if the HLO application is
 running, 0 if its not.  
  
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
 SUBSCRIBING DETAILS:   The Pharmacy Benefit Management application may use the
 $$RUNNING^HLOUSR() function in its KIDS instalation routines for patch PSU*4*3
 to determine if the HLO application is currently running.  
  
  

NUMBER: 4422                            IA #: 4422
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: NOV 17, 2005            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ OF AE CROSS REFERENCE
  ID: SC(
GLOBAL REFERENCE: SC("AE"
 GLOBAL DESCRIPTION:   This cross reference is in the following format.  
  
 ^SC("AE",X,DA)="" 
  
 Where X is the value assigned to the ADMINISTER INPATIENT MEDS? field, field 
 #2802, and DA is the internal entry number for the hospital location.  
  
 GENERAL DESCRIPTION:   OR request permission to do a read on file #44 "AE"
 cross reference. This cross reference allows for a quick way to find all
 hospital locations that have the same value for the "ADMINISTER INPATIENT
 MEDS?" field.    
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 44
KEYWORDS: SC('AE'
KEYWORDS: IMO
KEYWORDS: CPRS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4423                            IA #: 4423
  FILE NUMBER: 9002313.92               GLOBAL ROOT: BPSF(9002313.92
  DATE CREATED: NOV 10, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: BPS NCPDP FORMATS               ID: BPSF(9002313.92
GLOBAL REFERENCE: BPSF(9002313.92,D0
FIELD NUMBER: .01                       FIELD NAME: Record Format Name
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1.06                      FIELD NAME: Production Status
  LOCATION: 1;6                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Allowing subscribers read access to BPS NCPDP FORMATS
 file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BPS
KEYWORDS: ECME
KEYWORDS: HIPAA
KEYWORDS: NCPDP
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Birmingham
  DATE ACTIVATED: JAN 03, 2011

NUMBER: 4424                            IA #: 4424
  DATE CREATED: NOV 29, 2005
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXIMMAPI
  NAME: PCE Patient Immunization Data   ID: PXIMMAPI
 GENERAL DESCRIPTION:   The API was created to support a requirement for
 MyhealtheVet project regarding a specific patient's immunization data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PCE Immunizations
COMPONENT/ENTRY POINT: IMMLIST
 COMPONENT DESCRIPTION:   Get all or part of patient's immunization data from
 VistA's V IMMUNIZATION FILE (#9000010.11) and return all nodes containing
 data.  
  
 IMMLIST(DFN,STDATE,ENDATE) ;Get immunization data for patient 
         ;
         ; DFN     = Patient Identification entry number (required) 
         ; STDATE  = Begining date of date FM INTERNAL FORMAT (optional) 
         ; ENDATE  = Ending date of date FM INTERNAL FORMAT (optional) 
         ;
         ; OUTPUT: 
         ;   0   = No entries found_"^"_"no immunization data" 
         ;   1   = Entries found and stored in ^TMP(PXIMM",$J) global 
         ;
         ;         ^TMP(""PXIMM"",$J,DFN,NODE)=DATA 
         ;                 NODE = 0,12,801,811,812 of V IMMUNIZATION file 
         ;
         ; Important Note: Only the nodes which contain data returned.  
         ;                 External value for immunizationis inserted in 
         ;                 2nd piece of the 0th node.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of VistA's Patient file (#2) of the patient
 whose information is requested.  
VARIABLES: STDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   The begining date of date FM INTERNAL FORMAT
 (optional).  
VARIABLES: ENDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   The ending date of date FM INTERNAL FORMAT
 (optional).  

NUMBER: 4425                            IA #: 4425
  FILE NUMBER: 41.41                    GLOBAL ROOT: DGS(41.41
  DATE CREATED: MAY 07, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4425                        ID: DGS(41.41
GLOBAL REFERENCE: DGS(41.41,'ADC',
 GLOBAL DESCRIPTION:   Cross-reference by patient and date 
  DGS(41.41,"ADC",PATIENT,DATE CHANGED,DA) 
 GENERAL DESCRIPTION:   Integrated Billing needs to reference ADC cross
 reference to the PRE-REGISTRATION AUDIT (#41.41) file to determine if/when a
 patient was pre-registered prior to treatment.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Pre-Registration
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 3/18/22, effective with patch SD*5.3*809 to
 support Vista Scheduling Graphical User Interface (VSE GUI) update to the DATE
 CHANGED (#1) field stored with the PRE-REGISTRATION AUDIT PATIENT (#41.41)
 File.  

NUMBER: 4426                            IA #: 4426
  DATE CREATED: MAY 18, 2004
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: TIULF                        NAME: TIU CHECK FOR EMPTY DOCUMENT
  ID: TIULF
 GENERAL DESCRIPTION:   This M function takes as input a TIU Document IEN and
 returns 1 if there is no text in the document and 0 if there is text.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIULF
KEYWORDS: EMPTYDOC
COMPONENT/ENTRY POINT: EMPTYDOC(DA)
 COMPONENT DESCRIPTION:   Checks to see if text for Document DA is blank 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   TIU Document IEN 
VARIABLES: $$EMPTYDOC                   TYPE: Output
 VARIABLES DESCRIPTION:   Return Value 
   ; returns a 1 if empty 
   ; returns a 0 if contains data 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4427                            IA #: 4427
  DATE CREATED: MAY 13, 2004            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SROANEST
  NAME: DBIA4427                        ID: SROANEST
 GENERAL DESCRIPTION:   This function will return an array containing case
 level anesthesia times, service connector, and clinical indicators for
 surgical cases that fall within the from and through dates based on the date
 of operation.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SROANEST
COMPONENT/ENTRY POINT: ANESTIME(DFN,FROM_DATE,THROUGH_DATE)
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4428                            IA #: 4428
  DATE CREATED: MAY 19, 2004
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: ORWRP TIME/OCC LIMITS ALL
 GENERAL DESCRIPTION:   This DBIA document the usage of the CPRS parameter 
 ORWRP TIME/OCC LIMITS ALL. CP uses the 
 $$GET^XPAR("USR.`"_DUZ_"^DIV^SYS^PKG","ORWRP TIME/OCC LIMITS ALL",1,"I") call
 to get the default date/time and occurence limit for all reports.  CP will use
 this call to get the occurence limit so CP can return the accurate number of
 CP data to CPRS for display in the CPRS Reports tab.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Hines

NUMBER: 4429                            IA #: 4429
  FILE NUMBER: 101                      GLOBAL ROOT: ORD(101
  DATE CREATED: JUN 10, 2004
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: File                            ROUTINE: CSLUTPR1
  NAME: CSL UTILITY LOOKUP INTO HL7 MESSAGE
  ID: CSLUTPR1
GLOBAL REFERENCE: ORD(101,'B'
GLOBAL REFERENCE: ORD(101,'B',PROTOCOL NAME,PROTOCOL POINTER
GLOBAL REFERENCE: ORD(101,PROTOCOL POINTER,770)
FIELD NUMBER: 1                         ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: MESSAGE TYPE
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: EVENT TYPE
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: MESSAGE TYPE
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Accessing routine name ^CSLUTPR1, and can only be
 accessed from Programmer mode.  There is another related IA (4430), connected
 with this routine for accessing file 773 (^HLMA), 772 (^HL(772,)) and 779 
 (^HL(779.001,)) 
  
 This agreement will permit the direct read of ^ORD(101,"B" cross reference to
 be able to display all HL7 Protocols related to CSL.  Input will be "CSL_"
 concatenated with a package name to limit the search.  Once a complete
 protocol is selected, the software will extract the Event Message and the
 Event Type by directly accessing ^ORD(101,"B", Protocol Name, Protocol
 pointer).  The Protocol pointer looks at ^ORD(101, Protocaol Pointer, 770),
 $Piece 1.  If the $P1 is null, then the Message Type pointer is found in
 $Piece 11, and the Event Type pointer is found in $Piece 4.  If $P1 is not
 null, then Message Type pointer is found in $Piece 3, and Event Type pointer
 is found in $Piece 4.  The name of the Message Type is then found in
 ^HL(771.2,message pointer,0), $Piece 1, and the Event Type is found in
 ^HL(779.001,event pointer,0),$Piece 1.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: CSL
KEYWORDS: HL7
KEYWORDS: UTILITY
COMPONENT/ENTRY POINT: BEGIN
SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY

NUMBER: 4430                            IA #: 4430
  DATE CREATED: MAY 24, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4430
 GENERAL DESCRIPTION:   Integrated billing has attached the IB option, IBJD
 PERCENT PREREGISTERED, to the Registration menu Outputs for Preregistration
 menu, [DGPRE PRE-REGISTER OUTPUTS].  
  
  STATUS: Active
KEYWORDS: PREREGISTER
KEYWORDS: Pre-registration
KEYWORDS: OUTPUTS
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany

NUMBER: 4431                            IA #: 4431
  FILE NUMBER: 773                      GLOBAL ROOT: HLMA(
  DATE CREATED: JUN 10, 2004            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            ROUTINE: CSLUTPR1
  NAME: HL7 UTILITY TO VIEW MESSAGES BY PROTOCOL
  ID: CSLUTPR1
GLOBAL REFERENCE: HLMA(EIN,'MSH',1,0)
 GENERAL DESCRIPTION:   This agreement will permit the direct read of
 ^HLMA(EIN, and ^HL(772 to extract message text for display on a CRT.  Input is
 based on the user selecting the Interface Protocol from ^ORD(101 (see IA
 4429), which derives the Message Type and Event Type.  The routine will search
 for HL7 messages based on the Message and Event Type.  The user is also
 prompted for filters on Segments and text string within the segment.  These 
 Segments are found in ^HL(772,EIN.  The system will also report the EIN of any
 ^HLMA record that is encountered that does not have a ^HLMA(EIN,0) node or an
 ^HLMA(EIN,'MSH',1,0).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: HL7
KEYWORDS: HLMA
KEYWORDS: HL(772
COMPONENT/ENTRY POINT: NONE
SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY

NUMBER: 4432                            IA #: 4432
  DATE CREATED: APR 03, 2007            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FBAAFSR
  NAME: Return Latest Fee Basis Calendar Year 
  ID: FBAAFSR
 GENERAL DESCRIPTION:   The Radiology package has a need to determine the
 latest Calendar Year of the 162.99 FEE BASIS HCFA CONVERSION File. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LASTCY
 COMPONENT DESCRIPTION:   Returns the Last Calendar Year of current update.  
VARIABLES: none
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Radiology will utilize $$LASTCY^FBAAFSR() to return the
 last calendar year that file 162.99 FEE BASIS HCFA CONVERSION has been updated
 with Relative Value Unit (RVU) data.  This will determine how certain RVU
 reports are calculated and presented.  
  DATE ACTIVATED: MAY 16, 2007

NUMBER: 4433                            IA #: 4433
  DATE CREATED: MAY 25, 2004            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDAMA301
  NAME: DBIA4433                        ID: SDAMA301
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$SDAPI(.ARRAY)
 COMPONENT DESCRIPTION:   Name:           SDAPI ;Retrieve Filtered Appointment
 Data 
  
 Declaration:    $$SDAPI^SDAMA301(.ARRAY) 
  
 Description:    This API returns filtered appointment information and should
 be called using an EXTRINSIC call.  This will be a SUPPORTED IA.  
  
 Argument        ARRAY - An array, passed by value, that is defined and 
                 name-spaced by the calling application, containing the 
                 following parameters: 
  
 Field List      Required, ARRAY("FLDS").  List of appointment field IDs 
                 requested, each ID separated by a semicolon.  See Appendix 
                 A for a complete list of available appointment fields and 
                 their associated IDs.  
  
 Filters         Optional.  See Appendix B for a complete list of 
                 available appointment filters and their input array 
                 format.  
  
 Max Appts       Optional, ARRAY("MAX").  Maximum appointments requested.  
                 See Appendix B for a description and valid values of this 
                 array entry.  
  
 Sort            Optional, ARRAY("SORT"). Allows the output to be sorted by 
                 patient DFN, instead of by Patient and Clinic IENs. See 
                 Appendix B for a description and valid values of this 
                 array entry.  
  
  
 Return Values 
  
 From the extrinsic call, this API will return "-1" if an error occurred, "0"
 if no appointment is found that matches the filter criteria, or a count of the
 returned appointments.  
  
 If no appointment is found that matches the filter criteria, the 
 ^TMP($J,"SDAMA301") global will not be generated.  
  
 If appointments are found that match the filter criteria, the appointments 
 will be returned in ^TMP($J,"SDAMA301",SORT1,SORT2,APPT DATE/TIME) = 
 field1^field2^field3^ where SORT1 and SORT2 are driven by the patient filter
 and defined in the table below, and field1 is appointment data ID 1 (appt
 date/time) if requested, field2 is appointment data ID 2 (clinic IEN and name)
 if requested, etc. Note: Field 6 will always be null, because if field 6
 (Appointment comments) is requested, the comments will appear on the next
 subscript ("C") of the global reference. IE. ^TMP($J,"SDAMA301",SORT1,
 SORT2,APPT DATE/TIME,"C")=field 6.  
VARIABLES: ARRAY(FLDS)                  TYPE: Input
 VARIABLES DESCRIPTION:   Required, ARRAY("FLDS"). This is a list of the
 appointment field ID's requested, each ID separated by a semicolon.  
VARIABLES: ARRAY(MAX)                   TYPE: Input
 VARIABLES DESCRIPTION:   Optional, ARRAY("MAX"). mAXIMUM APPOINTMENTS
 REQUESTED.  
VARIABLES: ARRAY(SORT)                  TYPE: Input
 VARIABLES DESCRIPTION:   Optional, ARRAY("SORT"). Allows the output to be
 sorted by patient DFN, instead of by Patient and Clinic IENs.  
VARIABLES: $$SDAPI                      TYPE: Output
 VARIABLES DESCRIPTION:   From the extrinsic call, this API will return "-1" if
 an error occurred, "0" if no appointment is found that matches the filter
 criteria, or a count of the returned appointments.  

NUMBER: 4434                            IA #: 4434
  FILE NUMBER: 350                      GLOBAL ROOT: IB(
  DATE CREATED: MAY 26, 2004            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4434
  ID: IB(
GLOBAL REFERENCE: IB(
FIELD NUMBER: .05                       FIELD NAME: STATUS
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field points to the IB ACTION STATUS file (#350.21)
 and represents the current status of the entry.  
  STATUS: Active
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4435                            IA #: 4435
  DATE CREATED: MAY 27, 2004            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: IBNCPDPU                     NAME: DBIA4435
  ID: IBNCPDPU
 GENERAL DESCRIPTION:   IB functions are to serve AR in matching the ECME
 number to the respective IB bill ($$RXBIL component) and to check the status
 of a claim in Claims Tracking ($$REJECT component). 
  STATUS: Active
KEYWORDS: ECME
KEYWORDS: NCPDP
KEYWORDS: E-PHARMACY
KEYWORDS: BPS
COMPONENT/ENTRY POINT: $$RXBIL(.IBINP,.IBERR)
 COMPONENT DESCRIPTION:   The function $$RXBIL^IBNCPDPU() determines the
 respective IB/AR Bill, matching to the given ECME Number, Fill Date and the
 Patient Name (optional).  
  
 $$RXBIL^IBNCPDPU(.IBINP,.IBERR) returns IEN of the IB Bill (file #399), or 0
 if the given ECME Number has not been matched.  
  
 If the ECME Number was not matched, the parameter IBERR passed by reference is
 set to text description of the problem.  
VARIABLES: .IBINP                       TYPE: Input
 VARIABLES DESCRIPTION:   The following will be passed to Integrated Billing: 
  
 IBINP("ECME") - the 7-digit or 12-digit ECME Reference Number; IBINP("FILLDT") 
 - the Rx Fill Date, YYYYMMDD or FileMan format; IBINP("PNM") (optional) - the
 patient's last name.  
VARIABLES: .IBERR                       TYPE: Output
 VARIABLES DESCRIPTION:   Optional parameter passed by reference. If the
 matching function was successfull, the parameter IBERR will contain null
 string.  If the matching was unsuccessful, IBERR contains text description of
 the error.  
VARIABLES: $$RXBIL                      TYPE: Output
 VARIABLES DESCRIPTION:   the function returns IEN of the IB Bill (file #399)
 if matching is successful, or 0 if the given ECME Number has not been matched. 
 
COMPONENT/ENTRY POINT: $$REJECT(IBECME,IBDATE)
 COMPONENT DESCRIPTION:   The new procedure will be used by Accounts Receivable
 to check if the e-claim has been rejected by the payer. The call will only be
 made if the matching bill is not found in IB/AR. If the electronic EOB
 reference number is not "matched" in IB, and if it conforms to to the ECME
 format (?1.12N), and the PAID AMOUNT on the  electronic EOB is zero, there is
 a chance that the EEOB is related to the rejected e-Pharmacy claims. In those
 cases AR will be making the call to this function to make sure that the
 electronic EOB is related to the reject.  The function will be checking the
 Claims Tracking (CT) record to determine the status of the claim. The status
 in CT will be updated by the "SUBMITTED" event from ECME.  If the Payer's
 response never received due to any reason, the function will be returning "0". 
 
VARIABLES: IBECME                       TYPE: Input
 VARIABLES DESCRIPTION:   Required: the ECME number (the Reference Number) as
 it is shown in the electronic EOB.  
  
VARIABLES: IBDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   The date of service as it is reported in the EEOB.
 Could be in YYYYMMDD format, or the FileMan format (YYYMMDD).  The parameter
 is optional. If not passed, the function will return the latest claim
 information.  
  
VARIABLES: $$REJECT                     TYPE: Output
 VARIABLES DESCRIPTION:   "1" if the e-Pharmacy claim was rejected.  "0" - if
 the claim was not rejected, or payer response not received.  
  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  ISC: Washington/Silver Spring
 SUBSCRIBING DETAILS:   The IB function and the consumer from the subscribing
 patch (AR) were implemented by the NCPDP e-Pharmacy project, accordingly
 IB*2.0*223 and PRCA*4.5*202.  Additionally, a second component was added,
 $$REJECT, to support PRCA*4.5*230 (HIPAA NCPDP - Global).  
  
 In order to determine the IB/AR Bill matching to the given ECME Number and the
 Fill Date from the electronic 835, the AR package will call the IB function
 $$RXBIL^IBNCPDPU().  
  
 Within the AR package the matching API will be consumed by the manual matching
 functionality (RECEIPT PROCESSING, LINK PAYMENT) and by the EDI LOCKBOX
 automatic 835s matching.  
  
  
  
  DATE ACTIVATED: DEC 13, 2010

NUMBER: 4436                            IA #: 4436
  DATE CREATED: JUN 03, 2004            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPTFEE
  NAME: DBIA4436                        ID: DGPTFEE
 GENERAL DESCRIPTION:   This agreement will allow the Subscribing Packages the
 ability to create and delete a Fee PTF entry using the following Registration
 API call points.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$CREATE(DFN,DTTM,FLAG)
 COMPONENT DESCRIPTION:   Call point to create a Fee PTF entry.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient ien 
VARIABLES: DTTM                         TYPE: Input
 VARIABLES DESCRIPTION:   Date (time optional) 
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   Flag to enable creation of Fee PTF entry (value = 1) 
VARIABLES: $$CREATE                     TYPE: Output
 VARIABLES DESCRIPTION:   Successful: returns newly created PTF ien 
 Unsuccessful: returns -1, no patient ien defined 
COMPONENT/ENTRY POINT: $$DELETE(DFN,DTTM)
 COMPONENT DESCRIPTION:   Call point to delete Fee PTF entry.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient ien of valid PTF entry 
VARIABLES: DTTM                         TYPE: Input
 VARIABLES DESCRIPTION:   Date (time optional) of valid PTF entry 
VARIABLES: $$DELETE                     TYPE: Output
 VARIABLES DESCRIPTION:   returns 1 (successful), -1 (unsuccessful) 
SUBSCRIBING PACKAGE: FEE BASIS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
 SUBSCRIBING DETAILS:   added 12/11/2008 

NUMBER: 4437                            IA #: 4437
  DATE CREATED: JUN 10, 2004            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Other
  NAME: SUBSCRIBER cleanup: PROTOCOL (101) file 
 GENERAL DESCRIPTION:   Radiology/Nuclear Medicine has found the need in
 developing RA*5.0*47 to remove the 'MAGD SEND ORM' protocol from the
 SUBSCRIBER (775) multiple on the PROTOCOL (101) file. The event driver
 protocols impacted are: RA REG RA REG 2.3 RA CANCEL RA CANCEL 2.3 RA EXAMINED 
 RA EXAMINED 2.3 
  
 These event driver protocols generate v2.1 & v2.3 ORM Health Level Seven (HL7)
 messages. Imaging, through the use of 'MAGD SEND ORM', received ORM messages
 in this manner.  
  
 Imaging now needs to receive v2.4 HL7 messages. In an effort to prevent 
 needless use of disk space, I'd like to eliminate the creation of these 
 non-v2.4 HL7 Imaging related ORM messages.  
  
 A direct global read of the whole file cross-reference "AB" on the SUBSCRIBER 
  STATUS: Withdrawn

NUMBER: 4438                            IA #: 4438
  DATE CREATED: JUL 30, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: DGENEGT1
  NAME: DBIA4438                        ID: DGENEGT1
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: DGENEGT1
COMPONENT/ENTRY POINT: $$AOECDT
 COMPONENT DESCRIPTION:   To return the expiration date for considering AO
 (Agent Orange) and EC (Environment Contaminants) conditions when determining
 Copay Exemption status. 
VARIABLES: $$AOECDT                     TYPE: Output
 VARIABLES DESCRIPTION:   The return value contains the precise expiration date
 of the AO and EC directives in FileMan format.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Albany
SUBSCRIBING PACKAGE: CMOP

NUMBER: 4439                            IA #: 4439
  FILE NUMBER: 3.8                      GLOBAL ROOT: XMB(3.8
  DATE CREATED: JUN 30, 2004            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MAIL GROUP REMOTE MEMBER
  ID: XMB(3.8
 GENERAL DESCRIPTION:   Integrated Billing needs a ONE-TIME ONLY Integration
 Agreement to allow manipulation of the data in a mail group entry set up with
 a server option as a remote member. Since no utility exists to delete a remote
 member from the mail group file, the following access is requested: 
  
 1.  The ability to read the remote members from one mail group, add them to
 another mail group, and delete them from the original mail group. This would
 be done once, in the Post-install routine IBY232PO.  The following code would
 be used: 
  
 N IBMCR,IBMCH,DLAYGO,DIC,DIK,DA,D0,DD,Z,Z0 S
 IBMCR=+$O(^XMB(3.8,"B","MCR",0)),IBMCH=+$O(^XMB(3.8,"B","MCH",0)) S Z=0 F  S
 Z=$O(^XMB(3.8,IBMCR,6,Z)) Q:'Z  S Z0=$P($G(^XMB(3.8,IBMCR,6,Z,0)),U) I Z0'=""
 D 
  . I '$D(^XMB(3.8,IBMCH,6,"B",Z0)) D 
  .. S DLAYGO=3.812,DIC(0)="L",X=Z0,DA(1)=IBMCH,DIC="^XMB(3.8,"_DA(1)_",6," D
 FILE^DICN K DO,DD,DA,DLAYGO,DIC 
  .. I Y>0 S DA(1)=IBMCR,DA=Z,DIK="^XMB(3.8,"_DA(1)_",6," D ^DIK 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4440                            IA #: 4440
  DATE CREATED: JUN 17, 2004            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUPROD                       NAME: DBIA4440
  ID: XUPROD
 GENERAL DESCRIPTION:   This API is used to tell if the current account is the
 main production or a clone or test account.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRODUCTION
COMPONENT/ENTRY POINT: PROD([force])
 COMPONENT DESCRIPTION:   If the site manager has designated this as the
 production account for this facility the API will return a 1, otherwise it
 returns 0.  
  
 Because it is unknown how often this will be called or what the cost of the 
 real check is, the default check is against a field in the KERNEL SYSTEM 
 PARAMETERS file.  The real check is done when Taskman starts or the first time
 the function is called each day.  The force flag can be used to force the API
 to do a real check for this call and update the flag.  
  
VARIABLES: force                        TYPE: Input
 VARIABLES DESCRIPTION:   Any non-zero value will cause the API to do a real
 check calling the OS functions and comparing the results with the stored
 value.  

NUMBER: 4441                            IA #: 4441
  GLOBAL ROOT: DD(200,                  DATE CREATED: JUN 29, 2004
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Direct set DD node
  ID: DD(200,
 GENERAL DESCRIPTION:   Kernel requests permission to directly set
 ^DD(file,field) from a post-installation routine. The routine will modify the
 data dictionary definition of the NEW PERSON file (#200). Direct setting of
 the ^DD global will allow updating the data dictionary definition wihout
 exporting the field.  
  
 Directly set $P(^DD(200,.01,0),U,5,99), to call a differnt API to process the
 input of the Name field.  
  
 Directly set $P(^DD(200,20.2,0),U,5,99) to update the input transform.  
  
 Directly set ^DD(200,.01,21, to update the help text of the Name field.  
  STATUS: Active
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

NUMBER: 4442                            IA #: 4442
  DATE CREATED: JAN 26, 2005            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Dallas                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: YTAPI10                      NAME: DBIA4442
  ID: YTAPI10
 GENERAL DESCRIPTION:   API to return the scoring for a psychological test.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MENTAL HEALTH
KEYWORDS: CLINICAL REMINDERS
COMPONENT/ENTRY POINT: ENDAS(.YSDATA,DAS)
 COMPONENT DESCRIPTION:   This API returns the psychological test scoring for a
 specified patient and a specified test. The psychological test of interest is
 located using the Clinical Reminders Index. The last subscript in the index
 entry (DAS) give the location in the global where the results are stored.  
  
 Example of the Mental Health Clinical Reminder Index global entry: 
  
           ^PXRMINDX(601.2,"IP",INSTRUMENT,DFN,COMPLETION DATE,DAS) 
           ^PXRMINDX(601.2,"PI",DFN,INSTRUMENT,COMPLETION DATE,DAS) 
  
           ^PXRMINDX(601.2,"IP",6,30,3030213,"30;1;6;1;3030213") = 
           ^PXRMINDX(601.2,"PI",30,6,3030213,"30;1;6;1;3030213") = 
  
 To call the API use D ENDAS^YTAPI10(.YSDATA,DAS). YSDATA (output) and DAS 
 (input) are described in detail in the Output and Input variable sections.  
   
VARIABLES: YSDATA                       TYPE: Output
 VARIABLES DESCRIPTION:   The output variable YSDATA is an array in the format: 
  
   Array(1)=[DATA] 
   Array(2)=Patient Name^Test Code^Test Title^Internal Admindate^ 
            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 of the output YSDATA array: 
  
   YSDATA(0)=[ERROR] 
   YSDATA(1)=[DATA] 
   YSDATA(2)=NOSE,LIMP^ATQ^--- AUTOMATIC THOUGHTS QUESTIONNAIRE 
             ---^3030213^02/13/2003^DIBENEDETTO,PETER 
   YSDATA(3)=R1^12345X12345X2345X12345X12345X1 
   YSDATA(4)=R2^ 
   YSDATA(5)=R3^ 
   YSDATA(6)=S1^ATQ-30^75^74 
   YSDATA(7)=S2^MALADJ^14^46 
   YSDATA(8)=S3^NEG SC^18^49 
   YSDATA(9)=S4^LOW SE^1^36 
   YSDATA(10)=S5^HELPLESS^1^34 
  
     
VARIABLES: DAS                          TYPE: Input
 VARIABLES DESCRIPTION:   This input variable (DAS) is a semicolon separated
 string of values stored in the Clinical Reminder Index entry: 
  
                ^PXRMINDX(601.2,"IP",INSTRUMENT,DFN,COMPLETION DATE,DAS) 
                ^PXRMINDX(601.2,"PI",DFN,INSTRUMENT,COMPLETION DATE,DAS) 
  
 It gives the location in the global where the results are stored. The first
 piece is the first subscript, then second piece the second subscript, and so
 on. For example, if DAS="30;1;6;1;3030213" then the data location would be
 ^YTD(601.2,30,1,6,1,3030213,1).  
  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4443                            IA #: 4443
  FILE NUMBER: 101.41                   GLOBAL ROOT: ORD(101.41,
  DATE CREATED: JUL 02, 2004
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: POINTER TO THE ORDER DIALOG FILE
  ID: ORD(101.41,
GLOBAL REFERENCE: ORD(101.41,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   This DBIA allow for subscribing package to point to
 file 101.41.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORDER DIALOG FILE
KEYWORDS: PXRM
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 04/14/22, effective with DSSV 1.1 DSS Class 3
 product Document Only - Not approved by Custodial SME DSSV is using fields
 5,11,12,B from the ORDER DIALOG (#101.41) file. This is being requested in
 order to retrieve data from the Order Dialog file. 

NUMBER: 4444                            IA #: 4444
  DATE CREATED: JUL 02, 2004
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSSWRNA                      NAME: DRUG WARNING TEXT
  ID: PSSWRNA
 GENERAL DESCRIPTION:   The purpose of this call is to return the freetext
 warning label text for a given warning number. 
  STATUS: Active
KEYWORDS: DRUG WARNING
KEYWORDS: 54
KEYWORDS: 50.625
KEYWORDS: 50.626
COMPONENT/ENTRY POINT: $$WTEXT(WARN,LAN)
 COMPONENT DESCRIPTION:   This call will return the warning label text for the
 warning number. If LAN=2 the text will be returned in Spanish if a translation
 is available, otherwise the text will be returned in English.  
VARIABLES: WARN                         TYPE: Input
 VARIABLES DESCRIPTION:   A warning label number from the old RX Consult file
 (#54) - OR - A warning label number from the new WARNING LABEL-ENGLISH file
 (#50.625) followed by an "N".  
  
 Note: there is a one-to-one correspondence for entries in the WARNING 
 LABEL-ENGLISH file (#50.625) and the WARNING LABEL-SPANISH file (#50.626).  
VARIABLES: LAN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's PMI language preference. 2=Spanish.
 Anything less than 2 is English.   Optional 
VARIABLES: $$WTEXT                      TYPE: Output
 VARIABLES DESCRIPTION:   The warning label text for the warning number.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham

NUMBER: 4445                            IA #: 4445
  FILE NUMBER: 50.625                   GLOBAL ROOT: PS(50.625,
  DATE CREATED: JUL 02, 2004            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: ACCESS TO FILE 50.625           ID: PS(50.625,
 GENERAL DESCRIPTION:   PDM requests permission to use direct global reads to
 look at all fields of the WARNING LABEL-ENGLISH file (#50.625) to retrieve
 drug warning information from the new commercial data source. These warnings 
 will be used by the laser labels routines to print the warning labels in the
 patient's language preference for the patient's prescription bottle.  
  
 Note: there is a one-to-one correspondence for entries in the WARNING 
 LABEL-ENGLISH file (#50.625) and the WARNING LABEL-SPANISH file (#50.626).  
  STATUS: Active
KEYWORDS: 50.625
KEYWORDS: DRUG WARNING
KEYWORDS: 50.626
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

NUMBER: 4446                            IA #: 4446
  FILE NUMBER: 50.626                   GLOBAL ROOT: PS(50.626,
  DATE CREATED: JUL 06, 2004            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: ACCESS TO FILE 50.626           ID: PS(50.626,
 GENERAL DESCRIPTION:   PDM requests permission to use direct global reads to
 look at all fields of the WARNING LABEL-SPANISH file (#50.626) to retrieve
 drug warning information from the new commercial data source. These warnings
 will be used by the laser labels routines to print the warning labels in the 
 patient's language preference for the patient's prescription bottle.  
     
 Note: there is a one-to-one correspondence for entries in the WARNING 
 LABEL-ENGLISH file (#50.625) and the WARNING LABEL-SPANISH file (#50.626).  
  STATUS: Active
KEYWORDS: 50.625
KEYWORDS: 50.626
KEYWORDS: DRUG WARNING
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

NUMBER: 4447                            IA #: 4447
  DATE CREATED: AUG 31, 2004
  CUSTODIAL PACKAGE: VISTA DATA EXTRACTION FRAMEWORK
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VDEFVU
  NAME: ADDING ENTRIES TO VDEF FILES    ID: VDEFVU
 GENERAL DESCRIPTION:   This Integration Agreement allows the POSTKID^VDEFVU()
 API to be used in a post-init to add an entry to the VDEF Event Description
 file (#577) and, if necessary, to the VDEF Event Subtype (#577.4) and VDEF
 Custodial Package (#579.6) files.  An individual call contains information for
 a single entry in the VDEF Event Description file.  If necessary, an EVENT 
 DESCRIPTION is added for a new entry in the VDEF Event Subtype file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VDEF
KEYWORDS: VDEF EVENT
KEYWORDS: VDEF CUSTODIAL PACKAGE
KEYWORDS: VDEF EVENT SUBTYPE
KEYWORDS: 577
KEYWORDS: 577.4
KEYWORDS: 579.6
COMPONENT/ENTRY POINT: POSTKID(MSGTYP,EVNTYP,SUBTYP,PROTO,CUSTPKG,EXTROUT,DESC,S
UBDESC)
 COMPONENT DESCRIPTION:   The Calling Syntax is: 
  
 POSTKID^VDEFVU(MSGTYP,EVNTYP,SUBTYP,PROTO,CUSTPKG,EXTROUT,DESC,SUBDESC) 
  
 Only callable from a KIDS post-init.  
  
 All input is made through the parameter list.  All parameters are required
 except SUBDESC.  
  
 Other than the creation of the desired file entries, the only output of this
 call are various error messages that are passed to the KIDS system for display
 when a problem is detected with the call.  
  
 Example: D POSTKID^VDEFVU("ORU","R01","ALGY","VDEF ORU R01 ALLERGY
 VS","ADVERSE REACTION TRACKING","GMRAIAL1","ALLERGY UPDATES/INSERTS","ALLERGY 
 UPDATE/INSERT") 
VARIABLES: MSGTYP                       TYPE: Input
 VARIABLES DESCRIPTION:   External value for the MESSAGE TYPE field (.06) in
 File #577 (corresponds to the .01 of an existing entry in File #771.2).  
VARIABLES: EVTYP                        TYPE: Input
 VARIABLES DESCRIPTION:   External value for the EVENT TYPE field (.02) in File
 #577 (corresponds to the .01 of an existing entry in File #779.001).  
VARIABLES: SUBTYPE                      TYPE: Input
 VARIABLES DESCRIPTION:   External value for the EVENT SUBTYPE field (.03) in
 File #577 (corresponds to the .01 of an entry in File #577.4).  If the entry
 does not exist in File #577.4, a new entry will be added.  An application 
 should only add new VDEF Event Subtypes after the subtype has been authorized
 in writing by DaIS.  
VARIABLES: PROTO                        TYPE: Input
 VARIABLES DESCRIPTION:   External value for the VISTA HL7 PROTOCOL field (.07)
 in File #577 (corresponds to the .01 of entry in File #101).  A new entry in
 the Protocol file can be sent as part of the KIDS build.  
VARIABLES: CUSTPKG                      TYPE: Input
 VARIABLES DESCRIPTION:   External value for the CUSTODIAL PACKAGE field (.09)
 in File #577 (corresponds to the external value of the .01 of entry in File
 #579.6 that, in turn, corresponds to the .01 in File  #9.4).  If the entry
 does not exist in the VDEF Custodial Package file, a new entry will be added.  
VARIABLES: EXTROUT                      TYPE: Input
 VARIABLES DESCRIPTION:   Value of the EXTRACTION PROGRAM field (.3) in File
 #577, the routine that will be run at perform the extraction.  
VARIABLES: DESC                         TYPE: Input
 VARIABLES DESCRIPTION:   Value of the EVENT DESCRIPTION field (1) in File
 #577.  
VARIABLES: SUBDESC                      TYPE: Input
 VARIABLES DESCRIPTION:   Value of the EVENT DECRIPTION field (.02) in File
 #577.4.  The parameter is required only if a new entry is being made in the
 VDEF Event Subtype file.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
 SUBSCRIBING DETAILS:   ADDED 10/7/2009 

NUMBER: 4448                            IA #: 4448
  FILE NUMBER: 50.627                   GLOBAL ROOT: PS(50.627,
  DATE CREATED: JUL 06, 2004            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: ACCESS TO FILE 50.627           ID: PS(50.627,
 GENERAL DESCRIPTION:   PDM requests permission to use direct global reads to
 look at the cross-reference and fields of the WARNING LABEL MAP file (#50.627)
 to retrieve the entry numbers for the WARNING LABEL-ENGLISH file (#50.625) or
 the WARNING LABEL-SPANISH file (#50.626). These files contain the drug warning
 information from the new commercial data source. These warnings will be used
 by the laser labels routines to print the warning labels in the patient's
 language preference for the patient's prescription bottle.  
  STATUS: Active
KEYWORDS: 50.627
KEYWORDS: 50.625
KEYWORDS: 50.626
KEYWORDS: DRUG WARNING
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham

NUMBER: 4449                            IA #: 4449
  DATE CREATED: JUL 06, 2004
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSSWRNA                      NAME: WARNING LABEL LIST
  ID: PSSWRNA
 GENERAL DESCRIPTION:   This call will return the warning label list associated
 with a drug. The list will consist of numbers or numbers followed by the
 letter "N", separated by commas. Entries without the "N" are from the old RX
 CONSULT file (#54) and entries with the "N" are from the new commercial data 
 source's WARNING LABEL-ENGLISH file (#50.625) or WARNING LABEL-SPANISH file
 (#50.626).  
  STATUS: Active
KEYWORDS: DRUG WARNING
KEYWORDS: 54
KEYWORDS: 50.625
KEYWORDS: 50.626
COMPONENT/ENTRY POINT: $$DRUG(XX,DFN)
VARIABLES: XX                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN from the DRUG file (#50)  ** REQUIRED ** 
VARIABLES: $$DRUG                       TYPE: Output
 VARIABLES DESCRIPTION:   A list of warning numbers, separated by commas,
 associated with this drug. Warning numbers from the new data source will be
 followed by an "N".  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN from the PATIENT file (#2)  -- optional 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
SUBSCRIBING PACKAGE: CMOP               ISC: Birmingham

NUMBER: 4450                            IA #: 4450
  FILE NUMBER: 409.68                   GLOBAL ROOT: SCE(
  DATE CREATED: JUL 06, 2004            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DENTAL READ OF FILE 409.68      ID: SCE(
GLOBAL REFERENCE: SCE('AVSIT',
GLOBAL REFERENCE: SCE(D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Dental transmits its dental specific data to the AAC
 once a week.  The Decision Support staff requested that Dental include all
 data elements it needed in the HL7 extracts of VistA that are transmited to
 the AAC.  One of the VistA fields requested by the VA-DSS is the OUTPATIENT
 ENCOUNTER (#409.68) date and time as well as the internal entry number.  The
 dental encounter file (#228.1) has a pointer to the VISIT (#900010) file. PCE 
 developers have said that for each entry in file 409.68 there should be a 
 1-to-1 relationship with the VISIT file.  Thus the DENTAL package is 
 requesting to be allowed to do direct global reads of the "AVSIT" cross 
 reference on file 409.68 to get the 409.68 record number corresponding to a
 VISIT file record number.  Then using the 409.68 record number, a direct
 global read will be done for the .01 field of that record to get the encounter
 date and time.  
  STATUS: Active
SUBSCRIBING PACKAGE: DENTAL             ISC: Hines

NUMBER: 4451                            IA #: 4451
  DATE CREATED: SEP 15, 2004
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Supported
  TYPE: Routine                         ROUTINE: GMVVISN
  NAME: GMVVISN                         ID: GMVVISN
 GENERAL DESCRIPTION:   This IA supports the VISN Support Service Center's
 request to extract data for the Financial and Clinical Data Mart.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN(GMVST,GMVEND)
 COMPONENT DESCRIPTION:   This API returns a XTMP global containing FILE 120.5
 records data for the date range provided.  
  
 NOTE: Entered-in-Error records are not returned. An Entered-in-Error 
       record is one that has the ENTERED IN ERROR (#2) field set to "YES".  
  
 Input:   GMVST - Date to start search (FM internal format) (Required) 
         GMVEND - Date to end search (FM internal format) (Optional) 
                  If not defined, the current date/time is used.  
         
 Output: ^XTMP("GMV VISN"_$J,0)=purge date^create date^description 
         
         ^XTMP("GMV VISN"_$J,n)= 
         piece 1 = (#.001) FILE 120.5 Internal Entry Number (IEN) 
         piece 2 = (#.01) DATE/TIME VITALS TAKEN (internal) 
         piece 3 = (#.02) PATIENT (internal) 
         piece 4 = (#.03) VITAL TYPE (external) 
         piece 5 = (#.05) HOSPITAL LOCATION (internal) 
         piece 6 = (#1.2) RATE (external) 
         piece 7 = UNITS (value is computed by this routine) 
         piece 8 = (#.06) ENTERED BY (internal) 
  
 n is a sequential number starting with 1.  
VARIABLES: GMVST                        TYPE: Input
 VARIABLES DESCRIPTION:   A FileMan date in internal format. (Required) 
  
 This date is the start date of the record search. 
VARIABLES: GMVEND                       TYPE: Input
 VARIABLES DESCRIPTION:   A FileMan date in internal format. (Optional) 
  
 This is the end date of the search. If the DATE/TIME VITALS TAKEN (#.01) field
 is after this date, the record will be ignored. If the end date parameter is
 not defined, then today's date is used.  

NUMBER: 4452                            IA #: 4452
  DATE CREATED: JUL 13, 2004
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: OR PARAMETERS FOR CLINICAL REMINDERS
 GENERAL DESCRIPTION:   Clinical Reminders request permission to use the
 following OR parameters: 
  
 ORQQPX DEFAULT LOCATIONS ORQQPX NEW REMINDER PARAMS ORQQPX REMINDER TEXT AT
 CURSOR 
  
 All three of these parameters are used in CPRS to determine Clinical Reminder
 set-up for an user.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OR PARAMETERS
KEYWORDS: PXRM
KEYWORDS: CPRS
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4453                            IA #: 4453
  DATE CREATED: JUL 13, 2004            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XU8P328D
  NAME: Edit COUNTY(#.117) field of the PATIENT(#2) file
  ID: XU8P328D
 GENERAL DESCRIPTION:   Patch XU*8*328 is updating the COUNTY multiple of the
 STATE file.  The Read data is obtained using the following code: 
         . S FLDS=".01;.0905;.114;.115;.116;.117" 
         . ; .01=NAME 
         . ; .0905=1U4N 
         . ; .114=CITY 
         . ; .115=STATE FILE POINTER 
         . ; .116=ZIP CODE 
         . ; .117=COUNTY MULTIPLE IEN 
         . ;
         . D GETS^DIQ(2,DFN_",",FLDS,"I","PDATA","ZER") 
  
 Any County(s) who are found to be in error are having their names changed to
 "ZZ"_<current name> and VA COUNTY CODE changed to a 900 number.  As part of
 the post install a manual entry point has been created to attempt to change
 any patient who's County begins with "ZZ"_<smoething> to the proper county,
 After getting the Patient's current ZIP Code an API call is made to the POSTAL
 CODE(#5.12) file, editing of the COUNTY(.117) field will take place If And
 Only If the following three things are true: 1. The Patient's City matches the
 POSTAL CODE(#5.12) file City.  2. The Patient's State matches the POSTAL
 CODE(#5.12) State.  3. The Patient's ZIP code matches the POSTAL CODE(#5.12)
 ZIP code.  
  
 The following is the code that does the matching and the message: 
         ... I ZDATA(III,"CITY")=CITY,ZDATA(III,"STATE 
 POINTER")=SIEN,ZDATA(III," POSTAL CODE")=ZIP D  Q 
         .... S FLAG=1 
         .... N DIERR,ZERR,FDA 
         .... S FDA(2,DFN_",",.117)=ZDATA(III,"COUNTY") 
         .... D FILE^DIE("E","FDA","ZERR") 
         .... I $D(DIERR) D NAME,MES^XPDUTL("  **Unable to file Patient's 
 COUNTY.") Q 
         .... Q 
         ... Q 
         .. I 'FLAG D NAME,MES^XPDUTL("  ** City and State do not match ZIP
 code.") 
  STATUS: Active
COMPONENT/ENTRY POINT: FIX
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

NUMBER: 4454                            IA #: 4454
  GLOBAL ROOT: DD('KWIC')               DATE CREATED: JUL 12, 2004
  CUSTODIAL PACKAGE: 1                  USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Direct read of global DD('KWIC'
  ID: DD('KWIC')
GLOBAL REFERENCE: DD('KWIC')
 GLOBAL DESCRIPTION:   Read only access.  
 GENERAL DESCRIPTION:   This IA covers the ability to read the global node
 ^DD("KWIC". There is currently no other way to access the string located in
 this node other than a direct global read.  
  STATUS: Active
KEYWORDS: KWIC
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4455                            IA #: 4455
  DATE CREATED: JAN 03, 2005            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXRMHVET
  NAME: API FOR MYHEALTHEVET PATIENT WELLNESS REMINDERS
  ID: PXRMHVET
 GENERAL DESCRIPTION:   This DBIA allowed Health Summary and the MyHealtheVet
 application access the to patient Wellness Reminders.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: GMTS
KEYWORDS: HEALTH SUMMARY
KEYWORDS: PXRMHVET
COMPONENT/ENTRY POINT: HS
 COMPONENT DESCRIPTION:   This entry point allow HS to access the Clinical
 Reminders output for the Patient Wellness Reminders.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN is the patient internal entry number.  
VARIABLES: DISP                         TYPE: Input
 VARIABLES DESCRIPTION:   DISP is the type of the Clinical Maintenance output.
 A value of 10 returns the summary display and a value of 11 returns the detail
 display type.  
VARIABLES: TMP(PXRMHV,$J)               TYPE: Output
 VARIABLES DESCRIPTION:   This is the output array that is returned by this
 API. The format of the temp global is
 ^TMP("PXRMHV",$J,STATUS,NAME,REMIEN,"TXT",N)=TEXT 
  
 STATUS is the Clinical Reminders evaluation status (i.e. DUE NOW, NOT DUE) 
 NAME is the name of the Clinical Reminder definition REMIEN is the IEN of the
 Clinical Reminder definition N is a number TEXT is a text string 
  
 It is up to the calling routine to delete ^TMP("PXRMHV",$J) when it is 
 completed with it.  
COMPONENT/ENTRY POINT: START
 COMPONENT DESCRIPTION:   This entry point allowed the MyHealtheVet application
 access to the Patient Wellnesss reminders.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN is the patient IEN 
VARIABLES: DISP                         TYPE: Input
 VARIABLES DESCRIPTION:   DISP is the type of the Clinical Maintenance output.
 A value of 10 returns the summary display and a value of 11 returns the detail
 display type.  
VARIABLES: TMP(PXRMHM,$J)               TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP("PXRHM",$J,PXRMITEM,PXRMRNAM)=STATUS^DUE
 DATE^LAST D0 where PXRMRNAM is the PRINT NTAME or if it is undefined then it
 is the NAME. For this output the TXT subscript is returned in the TMP globabl. 
 
 ^TMP("PXRHM",$J,PXRMITEM,PXRMRNAM,"TXT",N)=TEXT where N is a number and TEXT 
 is a text string 
  
 The caller should kill ^TMP("PXRHM",$J) after display of the data is complete. 
 
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
SUBSCRIBING PACKAGE: MYHEALTHEVET

NUMBER: 4456                            IA #: 4456
  FILE NUMBER: 409.67                   GLOBAL ROOT: SD(409.67
  DATE CREATED: AUG 03, 2004            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: POINTER TO THE FILE# 409.67
  ID: SD(409.67
GLOBAL REFERENCE: SD(409.67,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   This DBIA will allowed Clinical Reminders to point to
 file# 409.67 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: SCHEDULING
KEYWORDS: 409.67
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4457                            IA #: 4457
  DATE CREATED: AUG 04, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGPTPXRM
  NAME: ACCESS TO PTF API FOR CLINICAL REMINDER INDEX
  ID: DGPTPXRM
 GENERAL DESCRIPTION:   This API will allowed access to the PTF^DGPTPXRM API.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: PTF
KEYWORDS: DGPTPXRM
COMPONENT/ENTRY POINT: PTF(DAS,.DATA)
VARIABLES: DAS                          TYPE: Input
 VARIABLES DESCRIPTION:   DAS stands for DA string, similar to FileMan's DA
 array. It is a semicolon-separated string that specifies the exact location in
 the global where the data is stored.  
VARIABLES: .DATA                        TYPE: Both
 VARIABLES DESCRIPTION:   DATA is an array that is pass by reference upon
 completion DATA will contain five subscripts.  
  
 DATA("DISCHARGE DATE") DATA("DISCHARGE SPECIALITY") DATA("DISCHARGE STATUS") 
 DATA("DISCHARGE PROVIDER") DATA("MOVEMENT RECORD") 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 11/19/18, effective with VPR*1.0*8.  

NUMBER: 4458                            IA #: 4458
  DATE CREATED: AUG 03, 2006            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: YTAPI10A                     NAME: YTAPI10A
  ID: YTAPI10A                          STATUS: Active
COMPONENT/ENTRY POINT: OCCUR
 COMPONENT DESCRIPTION:   This api returns the number of occurrences of a
 specific psychological test administered to a specific patient.  The input
 parameter is passed in the form of an array named YS.  Output is passed back
 in the array ^TMP($J,YSSUB.  To call the API use D OCCUR^YTAPI10A(YSSUB,.YS). 
VARIABLES: YS                           TYPE: Input
 VARIABLES DESCRIPTION:   The input parameter is passed in an array named YS. 
 Contained in the array is: 
   YS("CODE")= IEN of the instrument from the MH INSTRUMENT file (#601) 
  YS("BEGIN")= The start date to begin the search. Use an inclusive date 
               in %DT acceptable format (11/11/2011) This variable is 
               optional. 
    YS("END")= The finish date to end the search. Use an inclusive date 
               in %DT acceptable format (11/11/2011) This variable is 
               optional. 
  YS("LIMIT")= This is the number of occurences to return.  This variable 
               is optional. 
  
  Example of the YS array: 
     YS("CODE")=205 
    YS("BEGIN")="01/01/1990" 
      YS("END")="12/31/2004" 
    YS("LIMIT")=10 
VARIABLES: YSSUB                        TYPE: Output
 VARIABLES DESCRIPTION:   The output is an array in the format: 
  
     ^TMP($J,YSSUB,1)=[DATA]^NUMBER FOUND 
     ^TMP($J,YSSUB,DFN,OCCURANCE)=DAS^DFN^TEST 
  
 This is an example of the 
  
     ^TMP(545332100,1) = [DATA]^5 ^TMP(545332100,1,49,1) =
 49;1;205;1;2940428^2940428^205 ^TMP(545332100,1,66,1) =
 66;1;205;1;2940608^2940608^205 ^TMP(545332100,1,236,1) =
 236;1;205;1;3040824^3040824^205 ^TMP(545332100,1,551,1) =
 551;1;205;1;2940428^2940428^205 ^TMP(545332100,1,919,1) =
 919;1;205;1;2940608^2940608^205 
  
COMPONENT/ENTRY POINT: PTTEST
 COMPONENT DESCRIPTION:   This api returns all psychological test scoring for a
 specified patient. The input parameter is passed in the form of an array named
 YS.  Output is passed back in the array YSDATA.  To call the API use D
 PTTEST^YTAPI10A(.YSDATA,.DAS).  Where YSDATA is the output array and YS  is
 the input array parameter. 
   
VARIABLES: YS                           TYPE: Input
 VARIABLES DESCRIPTION:   The input parameter is passed in an array named YS. 
 Contained in the array is: 
   YS("CODE")= IEN of the instrument from the MH INSTRUMENT file (#601) 
    YS("DFN")= IEN of the patient from the PATIENT file (#2) 
  YS("BEGIN")= The start date to begin the search. Use an inclusive date 
               in %DT acceptable format (11/11/2011) This variable is 
               optional. 
    YS("END")= The finish date to end the search. Use an inclusive date 
               in %DT acceptable format (11/11/2011) This variable is 
               optional. 
  YS("LIMIT")= This is the number of occurences to return.  This variable 
               is optional. If this variable is not used, the default is 
               one occurance returned.  
  
  Example of the YS array: 
     YS("CODE")=205 
      YS("DFN")=236 
    YS("BEGIN")="01/01/1990" 
      YS("END")="12/31/2004" 
    YS("LIMIT")=10 
  
  
  
VARIABLES: YSDATA                       TYPE: Output
 VARIABLES DESCRIPTION:   Output is returned in the array YSDATA.  The array
 contains the patient IEN from the PATIENT file (#2), the instrument IEN from
 the MH INSTRUMENT file (#601) and the date the instrument was completed from
 the PSYCH INSTRUMENT PATIENT file (#601.2) taken from the Clinical Reminder
 Index global.  
  
 Example #1 
  
 YSDATA(1)=[DATA]^1 YSDATA(2)=236;1;205;1;3040824^3040824 
  
 Example #2 
   
 YSDATA(1)=[DATA]^3 YSDATA(2)=236;1;205;1;3040831^3040831  
 YSDATA(3)=236;1;205;1;3040826^3040826 YSDATA(4)=236;1;205;1;3040824^3040824 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4459                            IA #: 4459
  FILE NUMBER: 2                        DATE CREATED: DEC 02, 2005
  CUSTODIAL PACKAGE: REGISTRATION       USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: MyHealtheVets Demographics
GLOBAL REFERENCE: DPT(
FIELD NUMBER: .133                      FIELD NAME: E-MAIL
  LOCATION: .13;3                       ACCESS: Read w/Fileman
FIELD NUMBER: .21011                    FIELD NAME: K-WORK PHONE NUMBER
  LOCATION: .21;11                      ACCESS: Read w/Fileman
FIELD NUMBER: .33011                    FIELD NAME: E-WORK PHONE NUMBER
  LOCATION: .33;11                      ACCESS: Read w/Fileman
FIELD NUMBER: .353                      FIELD NAME: SOURCE OF NOTIFICATION
  LOCATION: .35;3                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This DBIA allows the MyHealtheVet Demographics
 application access to fields in the PATIENT file.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MYHEALTHEVETS
KEYWORDS: E-MAIL
KEYWORDS: BUSINESS PHONE
KEYWORDS: NOTIFICATION
KEYWORDS: DEATH NOTIFICATION
SUBSCRIBING PACKAGE: MYHEALTHEVET

NUMBER: 4460                            IA #: 4460
  DATE CREATED: DEC 05, 2005            CUSTODIAL PACKAGE: EVENT CAPTURE
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ECPRVMUT
  NAME: DBIA4460                        ID: ECPRVMUT
 GENERAL DESCRIPTION:   Provides a set of APIs to store and retrieve data for
 field #42 (PROVIDER MULTIPLE) in EVENT CAPTURE PATIENT file (#721).  
  
  
  
  STATUS: Active
KEYWORDS: PROVIDERS
KEYWORDS: EVENT CAPTURE
KEYWORDS: ENCOUNTER
COMPONENT/ENTRY POINT: $$GETPRV(ECIEN,OUTARR)
 COMPONENT DESCRIPTION:   Returns providers associated with an Event Capture
 encounter.  Returns 0 if there are providers, otherwise returns a 1.  
  
  
VARIABLES: ECIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN in EVENT CAPTURE PATIENT file #721.  
  
VARIABLES: OUTARR                       TYPE: Output
 VARIABLES DESCRIPTION:   The output array with providers.  Value store at
 array:- 
          ECH IEN^provider ien^provider description^Primary/Secondary code^ 
          Primary/Secondary description 
  
VARIABLES: $$GETPRV                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns:- 
  1 if successful or, 
  0 if unsuccessful 
  
COMPONENT/ENTRY POINT: $$GETPPRV(ECIEN,ECPPROV)
 COMPONENT DESCRIPTION:   Returns the primary provider associated with an Event
 Capture encounter.  Returns 0 if there is provider, otherwise returns a 1.  
  
  
VARIABLES: ECIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN in the EVENT CAPTURE PATIENT file #721.  
  
VARIABLES: ECPPROV                      TYPE: Output
 VARIABLES DESCRIPTION:   The output value is:- 
          provider ien^provider description 
  
VARIABLES: $$GETPPRV                    TYPE: Output
 VARIABLES DESCRIPTION:   Returns:- 
  1 if successful or, 
  0 if unsuccessful 
  
COMPONENT/ENTRY POINT: $$FILPRV(ECIEN,ECPRVARY,ECOUT)
 COMPONENT DESCRIPTION:   Files multiple providers for an Event Capture
 encounter in EVENT CAPTURE PATIENT, #721.  
  
VARIABLES: ECIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN in the EVENT CAPTURE PATIENT file #721.  This
 is required.  
  
VARIABLES: ECPRVARY                     TYPE: Input
 VARIABLES DESCRIPTION:   Array with encounter providers to be filed. Required. 
  
VARIABLES: ECOUT                        TYPE: Input
 VARIABLES DESCRIPTION:   Error flag.  
  
VARIABLES: $$FILPRV                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns 
   1 if successful or, 
   0^error message if unsuccessful 
  
  
COMPONENT/ENTRY POINT: $$ASKPRV(ECIEN,ECDT,ECPRVARY,ECOUT)
 COMPONENT DESCRIPTION:   API to prompt and validate primary and multiple
 secondary providers.  
  
VARIABLES: ECIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN in the EVENT CAPTURE PATIENT file #721. 
 Required.  
  
VARIABLES: ECDT                         TYPE: Input
 VARIABLES DESCRIPTION:   Date/time of encounter.  
  
VARIABLES: ECPRVARY                     TYPE: Input
 VARIABLES DESCRIPTION:   Array with encounter's providers.  
  
VARIABLES: ECOUT                        TYPE: Input
 VARIABLES DESCRIPTION:   Error flag (1/0).  
  
VARIABLES: $$ASKPRV                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns:- 
  1 if successful or, 
  0 if unsuccessful 
  
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   Used by DSS Event Capture extract.  
  

NUMBER: 4461                            IA #: 4461
  DATE CREATED: JAN 03, 2006
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: GMV LOCATION SELECT
  REMOTE PROCEDURE: GMV LOCATION SELECT
 GENERAL DESCRIPTION:   
  NAME: GMV LOCATION SELECT              
  TAG: RPC 
  ROUTINE: GMVRPCHL                    
  RETURN VALUE TYPE: GLOBAL ARRAY 
  AVAILABILITY: SUBSCRIPTION           
  INACTIVE: ACTIVE 
  WORD WRAP ON: TRUE 
  DESCRIPTION:   Select a hospital location by name, from a patient appointment
 or from a patient admission.  
  
  INPUT PARAMETER: OPTION                
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 10              
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Routine tag line in GMVRPCHL to call.  
  INPUT PARAMETER: DATA                  
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 100             
  REQUIRED: YES 
  SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  Other data as required for the call.  
  RETURN PARAMETER DESCRIPTION:   
  This remote procedure call allows the user to select a hospital 
  location. 
  
  The entry point is RPC^GMVRPCHL. It has input parameters of RESULTS, 
  OPTION and DATA (ex. RPC^GMVRPCHL(.RESULTS,OPTION,DATA).  
   
  The RESULTS variable will contain the ^TMP("GMVHLOC",$J) global array 
  reference. The ^TMP("GMVHLOC",$J) global array contains the results.  
   
  The OPTION variable identifies a line label in the GMVRPCHL routine that 
  will be invoked to process the call.  
   
  The DATA variable contains any additional values needed by the OPTION 
  variable to process the call.  
   
   1) When the OPTION value is NAME, this RPC will do a file lookup.  
   
   The DATA value is a three part value separated by carets(^). The first 
   part is a file number. The second part is a value to look up. The third 
   part is the field or fields to do the look up on. If the third piece is 
   not defined, the lookup is done on the .01 field of the file.  
   
   The TMP global contains: 
    ^TMP("GMVHLOC",$J,0)=piece1 
    ^TMP("GMVHLOC",$J,n)=piece2^piece3 
   
     where piece1 = number of entries found 
           piece2 = file number, a semi-colon and record IEN 
           piece3 = field value 
   
   Example: 
   >S OPTION="NAME",DATA="44^OUTPATIENT^.01"    
   >D RPC^GMVRPCHL(.RESULT,OPTION,DATA) ZW RESULT 
   >RESULT="^TMP("GMVHLOC",539052767)" 
   >D ^%G 
   >Global ^TMP("GMVHLOC",$J 
   >^TMP("GMVHLOC",539052767,0)=3 
                            1)=44;75^OUTPATIENT NUC MED 
                            2)=44;74^OUTPATIENT RADIOLOGY 
                            3)=44;80^OUTPATIENT ULTRASOUND 
   
   
   2) When the OPTION value is APPT, this RPC will return a list of clinic 
   appointments for the patient.  
   
   The DATA value is a four part value separated by carets(^). The first 
   piece is DFN. The second piece is the start date of the search. If 
   not defined, this value defaults to 365 days prior to today. The third 
   piece is the end date of the search. If not defined, the value defaults 
   to today. Both dates are in FileMan internal format. The fourth piece is 
   a string of numbers to indicate what types of appointments to return. If 
   not defined, the value defaults to "123456789" (i.e., all appointment 
   types) where: 
   
   1 - Active/Kept 
   2 - Inpatient appts. only 
   3 - No-shows 
   4 - No-shows, auto-rebook 
   5 - Cancelled by clinic 
   6 - Cancelled by clinic, auto rebook 
   7 - Cancelled by patient 
   8 - Cancelled by patient, auto rebook 
   9 - No action taken 
   
   The TMP global contains: 
    ^TMP("GMVHLOC",$J,0)=piece1 
    ^TMP("GMVHLOC",$J,n)=piece2^piece3^piece4^piece5^piece6^piece7 
                         ^piece8^piece9^ 
   
     where piece1 = number of entries found 
           piece2 = date/time of appt (FM internal) 
           piece3 = date/time of appt (external) 
           piece4 = hospital location IEN (FILE 44) 
           piece5 = hospital location name (FILE 44, Field .01) 
           piece6 = appt status (internal) 
           piece7 = appt status (external) 
           piece8 = appt type (internal) 
           piece9 = appt type (external) 
   
   Example: 
   > S OPTION="APPT",DATA="78^3051201^3051206^"   
   > D RPC^GMVRPCHL(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVHLOC",539052767)" 
   > D ^%G 
   > Global ^TMP("GMVHLOC",$J 
   > ^TMP("GMVHLOC",539052767,0)=1 
                              1)=3051206.1^DEC 6,2005@10:00^88^WEIGHT 
                                 CLINIC^^^9^REGULAR 
   
   3) When the OPTION value is ADMIT, this RPC will return a list of 
   hospital admissions for the patient specified.  
   
   The DATA value is the patient's DFN.  
   
   The TMP global contains: 
    ^TMP("GMVHLOC",$J,0)=piece1 
    ^TMP("GMVHLOC",$J,n)=piece2^piece3^piece4^piece5^piece6 
   
     where piece1 = number of entries found 
           piece2 = date/time of admission (external) 
           piece3 = hospital location IEN (FILE 44) 
           piece4 = hospital location name (FILE 44, Field .01) 
           piece5 = type of movement (FILE 405.1, Field .01) 
           piece6 = movement IEN (FILE 405) 
   
   Example: 
   > S OPTION="ADMIT",DATA=134 
   > D RPC^GMVRPCHL(.RESULT,OPTION,DATA) ZW RESULT 
   > RESULT="^TMP("GMVHLOC",539052767)" 
   > D ^%G 
   > Global ^TMP("GMVHLOC",$J 
   > ^TMP("GMVHLOC",539052767,0)=1 
                              1)=Apr 09, 2001 1:48:43 pm^67^ 
                                 2-ASM^DIRECT^1712 
   
   
  If an error is encountered for NAME, ADMIT or APPT, a "-1" followed by a 
  caret and the error message text (i.e., -1^error message) is returned in 
  RESULT(0).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4462                            IA #: 4462
  DATE CREATED: DEC 13, 2005            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGUTL3
  NAME: SHAD STATUS INDICATOR           ID: DGUTL3
 GENERAL DESCRIPTION:   This supported DBIA covers an API that will return a
 value that indicates whether the patient has Project 112/SHAD exposure.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$GETSHAD(DFN)
 COMPONENT DESCRIPTION:   This API will take the DFN as an input parameter and
 return the value of the PROJ 112/SHAD field (#.3215) in the PATIENT file (#2). 
 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Patient file (#2) 
VARIABLES: $$GETSHAD                    TYPE: Output
 VARIABLES DESCRIPTION:   The API will return the following values: 
   1='YES'  (SHAD exposure indicated) 
   0='NO'   (No SHAD exposure) 
  -1=error  (Input parameter missing) 

NUMBER: 4463                            IA #: 4463
  DATE CREATED: DEC 20, 2005            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: YTQPXRM4
  NAME: CHECK TO SEE IF A MH TEST IS COMPLETE
  ID: YTQPXRM4
 GENERAL DESCRIPTION:   CPRS, needs a way to determine if a Mental Health test
 is complete, when the test contains skip questions.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OR
KEYWORDS: MH
KEYWORDS: YS
KEYWORDS: CHECKCR
KEYWORDS: YTQPXRM4
KEYWORDS: CPRS
KEYWORDS: REMINDER DIALOGS
COMPONENT/ENTRY POINT: CHECKCR
 COMPONENT DESCRIPTION:   This API accepts an array and returns an array which
 identify if a MH test is complete. If a MH test is not complete the return
 array will list out the questions that still need to be answer.  
  
  
VARIABLES: YS                           TYPE: Input
 VARIABLES DESCRIPTION:   YS, is the input array. This array contains multiple
 subscripts.  
  
 YS("DFN")= the patient DFN from file #2.  
  
 YS("CODE")= the Mental Health Instrument name from file #601 
  
 YS(n)=equal the test question number and the user answer for that question. 
       n is the test question number and the subscript value is n^User
 response.  
       Example YS(1)=1^T, YS(2)=2^F 
  
VARIABLES: YSDATA                       TYPE: Output
 VARIABLES DESCRIPTION:   This output array is in the format of YSDATA(1) and
 YSDATA(2).  
  
 YSDATA(1)="[DATA]" 
  
 If the test is complete YSDATA(2) will be in this format  YSDATA(2)="OK". If 
 the test is not complete YSDATA(2) will be in this format YSDATA(2)="0^the
 question number that still need to be answer, if multiple questions need to be
 answer the question numbers will be separated by a comma.  
  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   ADDED 12/18/2007 

NUMBER: 4464                            IA #: 4464
  DATE CREATED: DEC 20, 2005
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MPIFDUP
  NAME: POT MPIFDUP                     ID: MPIFDUP
 GENERAL DESCRIPTION:   This entry point is used by the MPI/PD EXCEPTION
 HANDLING option when the POTENTIAL MATCH REVIEW action is utilized.  
  STATUS: Active
COMPONENT/ENTRY POINT: POT
 COMPONENT DESCRIPTION:   This entry point is used by the action Potential
 Match Review [PMR] action in the MPI/PD Exception Handler to communicate with
 the MPI and allow the review of the potential matches.  
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 4465                            IA #: 4465
  DATE CREATED: JUL 21, 2004            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: File
  NAME: VBECS data conversion from LR name spaced data globals
 GENERAL DESCRIPTION:   VBECS would like permission to obtain data from LR data
 files for the purpose of converting that data to the new VBECS (Blood Bank)
 application.  
  STATUS: Withdrawn
KEYWORDS: VBECS
KEYWORDS: VBECS data conversion
KEYWORDS: Blood Bank

NUMBER: 4466                            IA #: 4466
  DATE CREATED: JUL 22, 2004
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RGADTP
  NAME: INIT RGADTP                     ID: RGADTP
 GENERAL DESCRIPTION:   The protocol MPIF ADT-A31 CLIENT is utilizing
 PROCESSING ROUTINE - INIT^RGADTP to process the inbound A31 message.  
  STATUS: Active
COMPONENT/ENTRY POINT: INIT
 COMPONENT DESCRIPTION:   This entry point processes the inbound A31 message
 from the MPI.  
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA
 SUBSCRIBING DETAILS:   The protocol MPIF ADT-A31 CLIENT is utilizing
 PROCESSING ROUTINE - INIT^RGADTP to process the inbound A31 message.  

NUMBER: 4467                            IA #: 4467
  DATE CREATED: JUL 26, 2004            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUSCNT                       NAME: XUSCNT
  ID: XUSCNT
 GENERAL DESCRIPTION:   The routine XUSCNT is just for GT.M system to keep
 track of the number of active jobs.  It is called from ZU for normal users. 
 ZTMS calls it for taskman jobs.  Broker calls it as will other applications 
 that get started outside of Kernel.  Mailman HL7 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: COUNT(INC[,JOB])
 COMPONENT DESCRIPTION:   This API is used when a job first starts to add it's
 self to the list of running jobs by passing in a INC as a "1".  When it is
 about to halt it should call with INC as a "-1".  The JOB parameter defaults
 to $JOB.  
COMPONENT/ENTRY POINT: TOUCH
 COMPONENT DESCRIPTION:   This API updates the time stamp on the record so the
 clean up code will not remove the record.  It is only needed by long running
 jobs, those running more that one day.  
SUBSCRIBING PACKAGE: MAILMAN

NUMBER: 4468                            IA #: 4468
  GLOBAL ROOT: DD(62.55,                DATE CREATED: JUL 23, 2004
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VBECS set field level write access file 62.55
  ID: DD(62.55,
GLOBAL REFERENCE: DD(62.55,.01,9)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
GLOBAL REFERENCE: DD(62.55,1,9)
FIELD NUMBER: 1                         FIELD NAME: WILL STAND FOR
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
 GENERAL DESCRIPTION:   The VistA Blood Establishment Computer Software (VBECS)
 data conversion application would like to change the write access for specific
 fields in the AGGLUTINATION STRENGTH FILE (62.55). The fields in question are: 
 .01 - NAME & 1 - WILL STAND FOR.  
  
 The method to accomplish this task will be to set the write access node for
 the targeted field to the caret.  
  
 Example: 
 --------
 S ^DD(62.55,.01,9)="^" S ^DD(62.55,1,9)="^" 
  
 After the VBECS data conversion is run, these fields should not be edited or
 deleted through the use of VistA Blood Bank application. The hard set of the
 write access node ('9') will accomplish this goal.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 2005
KEYWORDS: Blood Bank
KEYWORDS: Agglutination Strength
KEYWORDS: write access
KEYWORDS: data dictionary
SUBSCRIBING PACKAGE: LAB SERVICE

NUMBER: 4469                            IA #: 4469
  GLOBAL ROOT: DD(63,                   DATE CREATED: JUL 23, 2004
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  NAME: VBECS set field level write access for file 63
  ID: DD(63,
GLOBAL REFERENCE: DD(63.01,
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME SPECIMEN TAKEN
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DATE REPORT COMPLETED
  LOCATION: 0;3                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: ENTERING PERSON
  LOCATION: 0;4                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: SPECIMEN
  LOCATION: 0;5                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .055                      FIELD NAME: COLLECTION SAMPLE
  LOCATION: 0;11                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: ACCESSION NUMBER
  LOCATION: 0;6                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: PHYSICIAN
  LOCATION: 0;7                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: WARD
  LOCATION: 0;8                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: PHLEBOTOMIST
  LOCATION: 0;9                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .1                        FIELD NAME: DATE/TIME RECEIVED
  LOCATION: 0;10                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .12                       FIELD NAME: ACCESSION LINK
  LOCATION: 0;12                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .99                       FIELD NAME: SPECIMEN COMMENT
  LOCATION: mult-63.199                 ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 2.1                       FIELD NAME: DIRECT AHG(POLYSPECIFIC)
  LOCATION: 2;1                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 2.2                       FIELD NAME: DIRECT AHG(5 min incub)
  LOCATION: 2;2                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 2.3                       FIELD NAME: DIRECT AHG CC
  LOCATION: 2;3                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 2.4                       FIELD NAME: ANTI-IgG
  LOCATION: 2;4                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 2.5                       FIELD NAME: ANTI-IgG CC
  LOCATION: 2;5                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 2.6                       FIELD NAME: ANTI-COMPLEMENT
  LOCATION: 2;6                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 2.7
  FIELD NAME: ANTI-COMPLEMENT (5 min incub)
  LOCATION: 2;7                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 2.8                       FIELD NAME: ANTI-COMPLEMENT CC
  LOCATION: 2;8                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 2.9                       FIELD NAME: DIRECT AHG INTERPRETATION
  LOCATION: 2;9                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 2.91                      FIELD NAME: DIRECT AHG TEST COMMENT
  LOCATION: 2;10                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: ELUATE ANTIBODY
  LOCATION: mult-63.012                 ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: SCREEN CELL METHOD
  LOCATION: mult-63.014                 ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 6
  FIELD NAME: ANTIBODY SCREEN INTERPRETATION
  LOCATION: 6;1                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 6.1                       FIELD NAME: RBC ANTIGEN PRESENT
  LOCATION: mult-63.011                 ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 6.2                       FIELD NAME: RBC ANTIGEN ABSENT
  LOCATION: mult-63.0112                ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 6.3                       FIELD NAME: HLA ANTIGEN PRESENT
  LOCATION: mult-63.013                 ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 6.4                       FIELD NAME: HLA ANTIGEN ABSENT
  LOCATION: mult-63.0114                ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: SERUM ANTIBODY
  LOCATION: mult-63.46                  ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: ANTIBODY SCREEN COMMENT
  LOCATION: mult-63.48                  ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: RBC TYPING METHOD
  LOCATION: mult-63.018                 ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 121                       FIELD NAME: PT CELLS+ANTI D
  LOCATION: 12;1                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 122                       FIELD NAME: PT CELLS+RH CTRL
  LOCATION: 12;2                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 123                       FIELD NAME: PT CELLS(sal)+ANTI D(hp IS)
  LOCATION: 12;3                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 124                       FIELD NAME: PT CELLS(ser)+ANTI D(hp IS)
  LOCATION: 12;4                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 125                       FIELD NAME: PT CELLS+ANTI D (hp 37)
  LOCATION: 12;5                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 126                       FIELD NAME: PT CELLS+ANTI D (hp AHG)
  LOCATION: 12;6                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 127                       FIELD NAME: PT CELLS+ANTI D SLIDE (hp)
  LOCATION: 12;7                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 128
  FIELD NAME: PT CELLS(sal)+RH CTRL (hp IS)
  LOCATION: 12;8                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 129                       FIELD NAME: PT CELLS(ser)+RH CTRL(hp IS)
  LOCATION: 12;9                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 129.1                     FIELD NAME: PT CELLS+RH CTRL (hp 37)
  LOCATION: 12;10                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 129.11                    FIELD NAME: PT CELLS+RH CTRL (hp AHG)
  LOCATION: 12;11                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 129.12                    FIELD NAME: PT CELLS+RH CTRL SLIDE (hp)
  LOCATION: 12;12                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 131                       FIELD NAME: INTERPRETATION OF RH TESTING
  LOCATION: 13;1                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 132                       FIELD NAME: RH TEST COMMENT
  LOCATION: 13;2                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 133                       FIELD NAME: PT Cells(sal)+Anti D(mod) IS
  LOCATION: 13;3                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 134                       FIELD NAME: PT Cells(ser)+Anti D(mod) IS
  LOCATION: 13;4                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 135                       FIELD NAME: PT Cells+Anti D(mod) 37
  LOCATION: 13;5                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 136                       FIELD NAME: PT Cells+Anti D(mod) AHG
  LOCATION: 13;6                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 138
  FIELD NAME: PT Cells(sal)+RH Ctrl(sal) IS
  LOCATION: 13;8                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 139
  FIELD NAME: PT Cells(ser)+RH Ctrl(sal) IS
  LOCATION: 13;9                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 139.1                     FIELD NAME: PT Cells+RH Ctrl(sal) 37
  LOCATION: 13;10                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 139.11                    FIELD NAME: PT Cells+RH Ctrl(sal) AHG
  LOCATION: 13;11                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 141                       FIELD NAME: PT CELLS(ser)+ANTI A IS
  LOCATION: 14;1                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 142                       FIELD NAME: PT CELLS(sal)+ANTI A IS
  LOCATION: 14;2                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 143                       FIELD NAME: PT CELLS+ANTI A SLIDE
  LOCATION: 14;3                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 144                       FIELD NAME: PT CELLS(ser)+ANTI B IS
  LOCATION: 14;4                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 145                       FIELD NAME: PT CELLS(sal)+ANTI B IS
  LOCATION: 14;5                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 146                       FIELD NAME: PT CELLS+ANTI B SLIDE
  LOCATION: 14;6                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 147                       FIELD NAME: PT CELLS(ser)+ANTI A,B IS
  LOCATION: 14;7                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 148                       FIELD NAME: PT CELLS(ser)+ANTI A,B (RT)
  LOCATION: 14;8                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 149                       FIELD NAME: PT CELLS(sal)+ANTI A,B (IS)
  LOCATION: 14;9                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 149.1                     FIELD NAME: PT CELLS(sal)+ANTI A,B (RT)
  LOCATION: 14;10                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 149.11                    FIELD NAME: PT CELLS+ANTI A,B SLIDE
  LOCATION: 14;11                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 149.12                    FIELD NAME: PT SERUM+A1 CELLS
  LOCATION: 14;12                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 149.13                    FIELD NAME: PT SERUM+B CELLS
  LOCATION: 14;13                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 151
  FIELD NAME: INTERPRETATION OF ABO TESTING
  LOCATION: 15;1                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 152                       FIELD NAME: ABO TESTING COMMENT
  LOCATION: 15;2                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 153
  FIELD NAME: INTERPRETATION ABO GROUP(cell)
  LOCATION: 15;3                        ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 154
  FIELD NAME: INTERPRETATION ABO GROUP(ser)
  LOCATION: 15;4                        ACCESS: Direct Global Write & w/Fileman
GLOBAL REFERENCE: DD(63.199,
FIELD NUMBER: .01                       FIELD NAME: SPECIMEN COMMENT
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
GLOBAL REFERENCE: DD(63.012,
FIELD NUMBER: .01                       FIELD NAME: ELUATE ANTIBODY
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
GLOBAL REFERENCE: DD(63.014,
FIELD NUMBER: .01                       FIELD NAME: SCREEN CELL METHOD
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: TECHNIQUE
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: SCREEN CELL
  LOCATION: mult-63.015                 ACCESS: Direct Global Write & w/Fileman
GLOBAL REFERENCE: DD(63.015,
FIELD NUMBER: .01                       FIELD NAME: SCREEN CELL
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: SOURCE
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .03                       FIELD NAME:  INTERPRETATION
  LOCATION: 0;3                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .04                       FIELD NAME:  IS
  LOCATION: 0;4                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: 37 C
  LOCATION: 0;5                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: AHG
  LOCATION: 0;6                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: CONTROL CELL
  LOCATION: 0;7                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: ROOM TEMP
  LOCATION: 0;8                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: 12-18 C
  LOCATION: 0;9                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .1                        FIELD NAME: 4 C
  LOCATION: 0;10                        ACCESS: Direct Global Write & w/Fileman
GLOBAL REFERENCE: DD(63.011,
FIELD NUMBER: .01                       FIELD NAME: RBC ANTIGEN PRESENT
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: COMMENT
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
GLOBAL REFERENCE: DD(63.0112,
FIELD NUMBER: .01                       FIELD NAME: RBC ANTIGEN ABSENT
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: COMMENT
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
GLOBAL REFERENCE: DD(63.013,
FIELD NUMBER: .01                       FIELD NAME: HLA ANTIGEN PRESENT
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: COMMENT
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
GLOBAL REFERENCE: DD(63.0114,
FIELD NUMBER: .01                       FIELD NAME: HLA ANTIGEN ABSENT
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: COMMENT
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
GLOBAL REFERENCE: DD(63.46,
FIELD NUMBER: .01                       FIELD NAME: SERUM ANTIBODY
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ANTIBODY COMMENT
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
GLOBAL REFERENCE: DD(63.48,
FIELD NUMBER: .01                       FIELD NAME: ANTIBODY SCREEN COMMENT
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
GLOBAL REFERENCE: DD(63.018,
FIELD NUMBER: .01                       FIELD NAME: RBC TYPING METHOD
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: TECHNIQUE
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ANTISERUM
  LOCATION: mult-63.019                 ACCESS: Direct Global Write & w/Fileman
GLOBAL REFERENCE: DD(63.019,
FIELD NUMBER: .01                       FIELD NAME: ANTISERUM
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: LOT #
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: INTERPRETATION
  LOCATION: 0;3                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .04                       FIELD NAME:  IS
  LOCATION: 0;4                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: 37 C
  LOCATION: 0;5                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: AHG
  LOCATION: 0;6                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: CONTROL CELL
  LOCATION: 0;7                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: ROOM TEMP
  LOCATION: 0;8                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: 12-18 C
  LOCATION: 0;9                         ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: .1                        FIELD NAME: 4 C
  LOCATION: 0;10                        ACCESS: Direct Global Write & w/Fileman
 GENERAL DESCRIPTION:   The VistA Blood Establishment Computer Software (VBECS)
 data conversion application would like to change the write access for specific
 fields in the LAB DATA file (63).  
  
 The following sub-files and fields will be targeted: 
 ----------------------------------------------------
 BLOOD BANK (Multiple-63.01), [BB;0] 
           .01  DATE/TIME SPECIMEN TAKEN (RDX), [0;1] 
           .03  DATE REPORT COMPLETED (RD), [0;3] 
           .04  ENTERING PERSON (P200'), [0;4] 
           .05  SPECIMEN (P61'), [0;5] 
           .055 COLLECTION SAMPLE (RP62'), [0;11] 
           .06  ACCESSION NUMBER (F), [0;6] 
           .07  PHYSICIAN (*P200'X), [0;7] 
           .08  WARD (F), [0;8] 
           .09  PHLEBOTOMIST (P200'), [0;9] 
           .1   DATE/TIME RECEIVED (RDX), [0;10] 
           .12  ACCESSION LINK (FI), [0;12] 
           .99  SPECIMEN COMMENT (Multiple-63.199), [99;0] 
                .01  SPECIMEN COMMENT (MF), [0;1] 
           2.1  DIRECT AHG(POLYSPECIFIC) (FX), [2;1] 
           2.2  DIRECT AHG(5 min incub) (FX), [2;2] 
           2.3  DIRECT AHG CC (FX), [2;3] 
           2.4  ANTI-IgG (FX), [2;4] 
           2.5  ANTI-IgG CC (FX), [2;5] 
           2.6  ANTI-COMPLEMENT (FX), [2;6] 
           2.7  ANTI-COMPLEMENT (5 min incub) (FX), [2;7] 
           2.8  ANTI-COMPLEMENT CC (FX), [2;8] 
           2.9  DIRECT AHG INTERPRETATION (S), [2;9] 
           2.91 DIRECT AHG TEST COMMENT (FX), [2;10] 
           3    ELUATE ANTIBODY (Multiple-63.012), [EA;0] 
                .01  ELUATE ANTIBODY (M*P61.3'X), [0;1] 
           4    SCREEN CELL METHOD (Multiple-63.014), [3;0] 
                .01  SCREEN CELL METHOD (MS), [0;1] 
                .02  TECHNIQUE (S), [0;2] 
                1    SCREEN CELL (Multiple-63.015), [1;0] 
                     .01  SCREEN CELL (MSX), [0;1] 
                     .02  SOURCE (P66'), [0;2] 
                     .03  INTERPRETATION (S), [0;3] 
                     .04  IS (FX), [0;4] 
                     .05  37 C (FX), [0;5] 
                     .06  AHG (FX), [0;6] 
                     .07  CONTROL CELL (FX), [0;7] 
                     .08  ROOM TEMP (FX), [0;8] 
                     .09  12-18 C (FX), [0;9] 
                     .1   4 C (FX), [0;10] 
           6    ANTIBODY SCREEN INTERPRETATION (S), [6;1] 
           6.1  RBC ANTIGEN PRESENT (Multiple-63.011), [1.1;0] 
                .01  RBC ANTIGEN PRESENT (M*P61.3'X), [0;1] 
                .02  COMMENT (F), [0;2] 
           6.2  RBC ANTIGEN ABSENT (Multiple-63.0112), [1.2;0] 
                .01  RBC ANTIGEN ABSENT (M*P61.3'X), [0;1] 
                .02  COMMENT (F), [0;2] 
           6.3  HLA ANTIGEN PRESENT (Multiple-63.013), [1.3;0] 
                .01  HLA ANTIGEN PRESENT (M*P61.3'X), [0;1] 
                .02  COMMENT (F), [0;2] 
           6.4  HLA ANTIGEN ABSENT (Multiple-63.0114), [1.4;0] 
                .01  HLA ANTIGEN ABSENT (M*P61.3'X), [0;1] 
                .02  COMMENT (F), [0;2] 
           7    SERUM ANTIBODY (Multiple-63.46), [5;0] 
                .01  SERUM ANTIBODY (M*P61.3'X), [0;1] 
                .02  ANTIBODY COMMENT (F), [0;2] 
           8    ANTIBODY SCREEN COMMENT (Multiple-63.48), [4;0] 
                .01  ANTIBODY SCREEN COMMENT (MFX), [0;1] 
           9    RBC TYPING METHOD (Multiple-63.018), [1;0] 
                .01  RBC TYPING METHOD (S), [0;1] 
                .02  TECHNIQUE (S), [0;2] 
                1    ANTISERUM (Multiple-63.019), [1;0] 
                     .01  ANTISERUM (M*P66'), [0;1] 
                     .02  LOT # (F), [0;2] 
                     .03  INTERPRETATION (RS), [0;3] 
                     .04  IS (FX), [0;4] 
                     .05  37 C (FX), [0;5] 
                     .06  AHG (FX), [0;6] 
                     .07  CONTROL CELL (FX), [0;7] 
                     .08  ROOM TEMP (FX), [0;8] 
                     .09  12-18 C (FX), [0;9] 
                     .1   4 C (FX), [0;10] 
           121  PT CELLS+ANTI D (sal) (FX), [12;1] 
           122  PT CELLS+RH CTRL (sal) (FX), [12;2] 
           123  PT CELLS(sal)+ANTI D(hp IS) (FX), [12;3] 
           124  PT CELLS(ser)+ANTI D(hp IS) (RFX), [12;4] 
           125  PT CELLS+ANTI D (hp 37) (FX), [12;5] 
           126  PT CELLS+ANTI D (hp AHG) (FX), [12;6] 
           127  PT CELLS+ANTI D SLIDE (hp) (S), [12;7] 
           128  PT CELLS(sal)+RH CTRL (hp IS) (FX), [12;8] 
           129  PT CELLS(ser)+RH CTRL(hp IS) (RFX), [12;9] 
           129.1PT CELLS+RH CTRL (hp 37) (FX), [12;10] 
           129.11PT CELLS+RH CTRL (hp AHG) (FX), [12;11] 
           129.12PT CELLS+RH CTRL SLIDE (hp) (S), [12;12] 
           131  INTERPRETATION OF RH TESTING (RS), [13;1] 
           132  RH TEST COMMENT (F), [13;2] 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 2005
KEYWORDS: Blood Bank
KEYWORDS: write access
KEYWORDS: data dictionary
KEYWORDS: Lab Data

NUMBER: 4470                            IA #: 4470
  DATE CREATED: DEC 29, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  ROUTINE: PSOMHV2                      NAME: DBIA4470
  ID: PSOMHV2
 GENERAL DESCRIPTION:   This DBIA will provide NON-VA Medication information
 from the NON-VA MEDS sub-file (#55.05) of the PHARMACY PATIENT File (#55) to
 the subscribing package.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ALL(PSOHDFN)
 COMPONENT DESCRIPTION:   This component returns Non-VA Medication information
 from the NON-VA MEDS sub-file (#55.05) of the PHARMACY PATIENT File (#55) to
 the subscribing package. All Active NON-VA meds will be returned. That will
 include all entries with a null DISCONTINUED DATE, or a DISCONTINUED DATE not
 less than the current date.  
VARIABLES: PSOHDFN                      TYPE: Input
 VARIABLES DESCRIPTION:   The parameter is the Internal Entry Number from the
 PATIENT file (#2). It is required.  
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP("PSONVA",$J,DFN,0)=Total entries returned, or
 -1^Error code 
  
 ^TMP("PSONVA",$J,DFN,D0,0)=2977;50^CAPTOPRIL 25MG TABS^^^^^^ACTIVE^10778 
    Where: 
    piece 1 = Internal Entry number;File Number. If the order has an 
    entry from the DRUG (#50) File, that will display. If the order does 
    not have an entry frm the DRUG (#50) File, the the entry from the 
    PHARMACY ORDERABLE ITEM (#50.7) File will display.  
    piece 2 = If the order has an entry from the DRUG (#50) File, this 
    will be the .01 field from the DRUG (#50) File. If the order does 
    not have an entry frm the DRUG (#50) File, this will be the entry from 
    the PHARMACY ORDERABLE ITEM (#50.7) File, concatenated with the .01 
    field from the DOSAGE FORM (#50.606) File.  
    piece 8 = DISCONTINUED if the entry has a date in the DISCONTINUED DATE 
    (#6) field, and the date is not a future date. Otherwise, ACTIVE will 
    be returned.  
    piece 9 = ORDER NUMBER, which is the pointer to the ORDER (#100) File.  
  
  
 ^TMP("PSONVA",$J,DFN,D0,"CLINIC",0)=# of CLINIC entries 
 ^TMP("PSONVA",$J,DFN,D0,"CLINIC",1,0)=22^OUTPATIENT LAB 
    Where if defined, data node will be: 
    piece 1 = Internal Entry Number from the HOSPITAL LOCATION (#44) File.  
    piece 2 = The NAME (.01) Field from the HOSPITAL LOCATION (#44) File. 
  
  
 ^TMP("PSONVA",$J,DFN,D0,"DTDISC",0)=# of DISCONTINUED DATE entries 
 ^TMP("PSONVA",$J,DFN,D0,"DTDISC",1,0)=3060103^JAN 3,2006 
    Where if defined, data node will be: 
    piece 1 = Internal format of DISCONTINUED DATE (#6) Field.  
    piece 2 = External format of DISCONTINUED DATE (#6) Field.  
  
  
 ^TMP("PSONVA",$J,DFN,D0,"DTDOCU",0)=# of DOCUMENTED DATE entries 
 ^TMP("PSONVA",$J,DFN,D0,"DTDOCU",1,0)=3051230.094043^DEC 30,2005@09:40:43 
    Where if defined, data node will be: 
    piece 1 = Internal format of DOCUMENTED DATE (#11) Field.  
    piece 2 = External format of DOCUMENTED DATE (#11) Field. 
  
  
 ^TMP("PSONVA",$J,DFN,D0,"DTSTRT",0)=# of START DATE entries 
 ^TMP("PSONVA",$J,DFN,D0,"DTSTRT",1,0)=3051229^DEC 29,2005 
    Where if defined, data node will be: 
    piece 1 = Internal format of START DATE (#8) Field.  
    piece 2 = External format of START DATE (#8) Field.  
  
  
 ^TMP("PSONVA",$J,DFN,D0,"ORDIEN",0)=# of ORDER NUMBER entries 
 ^TMP("PSONVA",$J,DFN,D0,"ORDIEN",1,0)=10778 
    Where if defined, data node will be: 
    piece 1 = ORDER NUMBER (#7) Field, which is the pointer to the ORDER 
    (#100) File.  
  
  
 ^TMP("PSONVA",$J,DFN,D0,"SCHED",0)=# of SCHEDULE entries 
 ^TMP("PSONVA",$J,DFN,D0,"SCHED",1,0)=Schedule 
    Where if defined, data node will be: 
    piece 1 = Entry from the SCHEDULE (#4) Field.  
  
  
 ^TMP("PSONVA",$J,DFN,D0,"SIG",0)=# of SIG entries 
 ^TMP("PSONVA",$J,DFN,D0,"SIG",1,0)=25MG BY MOUTH 
    Where if defined, data node will be: 
    piece 1 = SIG, which is comprised of a concatenation of the DOSAGE 
    (#2) Field, the  MEDICATION ROUTE (#3) Field, and the SCHEDULE (#4) 
    Field.  
  
  
 ^TMP("PSONVA",$J,DFN,D0,"STATUS",0)=# of STATUS entries 
 ^TMP("PSONVA",$J,DFN,D0,"STATUS",1,0)=DISCONTINUED 
    Where if defined, data node will be: 
    piece 1 = DISCONTINUED if the entry has data in the   
    DISCONTINUED DATE (#6) field, and the date is not a future date. 
    Otherwise, ACTIVE will be returned.  
  
  
 ^TMP("PSONVA",$J,DFN,D0,"USRDOCU",0)=# of DOCUMENTED BY entries 
 ^TMP("PSONVA",$J,DFN,D0,"USRDOCU",1,0)=12345^CPRSprovider 
    Where if defined, data node will be: 
    piece 1 = NEW PERSON (#200) File pointer from the DOCUMENTED BY (#12) 
    Field.  
    piece 2 = NAME (#.01) Field from the NEW PERSON (#200) File. 
                                                                 
  
 ^TMP("PSONVA",$J,DFN,D0,"WP-CMMNT",0)=# of COMMENTS lines 
 ^TMP("PSONVA",$J,DFN,D0,"WP-CMMNT",1,0)=Patient already taking medication.  
    Where if defined, data node will be: 
    data from the COMMENTS  (#55.514) Subfile 
  
  
 ^TMP("PSONVA",$J,DFN,D0,"WP-DSCLMR",0)=# of DISCLAIMER lines 
 ^TMP("PSONVA",$J,DFN,D0,"WP-DSCLMR",D1,0)=Patient wants to buy from Non-VA
 pharmacy.  
    Where if defined, data node will be: 
    data from the DISCLAIMER (#55.052) Subfile 
                             
  
 ^TMP("PSONVA",$J,DFN,D0,"WP-OCNAR",0)=# of ORDER CHECK NARRATIVES lines 
 ^TMP("PSONVA",$J,DFN,D0,"WP-OCNAR",D1,0)=CRITICAL drug-drug interaction:
 AMINOPHYLLINE & CIMETIDINE (AMINOPHYLLINE TAB  100MG TAKE ONE TABLET BY BY
 MOUTH EVERY MORNING THIS IS ONLY A TEST  [ACTIVE])^12345 
    Where if defined, data node will be: 
    piece 1 = The narrative of the order check for the Non-VA Medication 
    order from the ORDER CHECK NARRATIVE (#.01) Field.  
    piece 2 = NEW PERSON (#200) File pointer of the provider responsible 
    for overriding the order check, from the OVERRIDING PROVIDER (#1) 
    Field.  
                                              
  
 ^TMP("PSONVA",$J,DFN,D0,"WP-OCNAR",D1,"WP-OVRDRSN",0)=# of OVERRIDING REASON
 lines ^TMP("PSONVA",$J,DFN,D0,"WP-OCNAR",D1,"WP-OVRDRSN",D2,0)=Patient 
 understands instructions.  
   Where if defined, data node will be: 
   data from the OVERRIDING REASON  (#55.O511) Subfile 
COMPONENT/ENTRY POINT: NVA(PSOHDFN,PSOBEGDT,PSOENDT)
 COMPONENT DESCRIPTION:   This component returns Non-VA Medication information
 from the NON-VA MEDS sub-file (#55.05) of the PHARMACY PATIENT File (#55) to
 the subscribing package. All Active NON-VA meds will be returned. That will
 include all entries with a null DISCONTINUED DATE, or a DISCONTINUED DATE that
 falls between the Beginning and Ending Date, inclusively.  
VARIABLES: PSOHDFN                      TYPE: Input
 VARIABLES DESCRIPTION:   The parameter is the Internal Entry Number from the
 PATIENT file (#2). It is required.  
VARIABLES: PSOBEGDT                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the Beginning Date. For an order with a
 DISCONTINUED DATE, that order will only be returned if the DISCONTINUE DATE is
 not less than the Beginning Date.  
VARIABLES: PSOENDT                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the Ending Date. For an order with a
 DISCONTINUED DATE, that order will only be returned if the DISCONTINUE DATE is
 not greater than the Ending Date.  
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   See the ALL component of this DBIA for the
 description of the TMP global output.  
SUBSCRIBING PACKAGE: MYHEALTHEVET
 SUBSCRIBING DETAILS:   This DBIA will provide Non-VA Medication information
 from the NON-VA MEDS sub-file (#55.05) of the PHARMACY PATIENT File (#55) to
 the subscribing package. The subscribing package must pass in a required
 patient identifier.  

NUMBER: 4471                            IA #: 4471
  FILE NUMBER: 450                      DATE CREATED: JAN 10, 2006
  CUSTODIAL PACKAGE: PAID               USAGE: Private
  TYPE: Other                           NAME: CREATE NEW CROSS REFERENCE
 GENERAL DESCRIPTION:   Kernel patch XU*8*384 requests to create the new AXUSEC
 Cross-reference for field SEPARATION IND(#80) of the file PAID EMPLOYEE(#450)
 to send a bulletin message to the mail group XUSEC/PRC PAID SEPARATION when
 the field SEPARATION IND(#80) is set 'Y' for an employee.  
  
  
  
 hard codes set for the cross-ref: 
  
        S ^DD(450,80,1,160001,0)="450^AXUSEC^MUMPS" 
        S ^DD(450,80,1,160001,1)="D:$T(^XUSECBUL)'="""" ^XUSECBUL" 
        S ^DD(450,80,1,160001,2)="Q" 
        S ^DD(450,80,1,160001,"%D",0)="^^3^3^3060110^" 
        S ^DD(450,80,1,160001,"%D",1,0)="This cross reference is used to 
        send a message when an employee's:" 
        S ^DD(450,80,1,160001,"%D",2,0)="File: PAID EMPLOYEE(#450)" 
        S ^DD(450,80,1,160001,"%D",3,0)="Field: SEPARATION IND(#80) is set 
        to 'Y '" 
        S ^DD(450,80,1,160001,"DT")=3060110 
        S ^DD(450,80,"DT")=3060110 
        Q 
  
             =========================================
  
 CROSS-REFERENCE:  450^AXUSEC^MUMPS 
                                 1)= D:$T(^XUSECBUL)'="" ^XUSECBUL 
                                 2)= Q 
                                 This cross reference is used to send a 
                                 message when an employee's: File: PAID 
                                 EMPLOYEE(#450) Field: SEPARATION IND(#80) 
                                 is set to 'Y' 
  STATUS: Expired
SUBSCRIBING PACKAGE: KERNEL

NUMBER: 4472                            IA #: 4472
  FILE NUMBER: 58.86                    GLOBAL ROOT: PSD(58.86,
  DATE CREATED: JAN 11, 2006            CUSTODIAL PACKAGE: CONTROLLED SUBSTANCES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CS DESTRUCTION FILE
  ID: PSD(58.86,
 GENERAL DESCRIPTION:   This is an open agreement between Controlled Substances
 and Drug Accountability. This agreement allows Drug Accountability access to
 the CS Destruction (#58.86) file. Controlled Substances permits Drug 
 Accountability access to add/alter/delete data from this file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY

NUMBER: 4473                            IA #: 4473
  FILE NUMBER: 811.2                    GLOBAL ROOT: PXD(811.2,
  DATE CREATED: JAN 17, 2006            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: REMINDER TAXONOMIES
  ID: PXD(811.2,
GLOBAL REFERENCE: PXD(811.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the name of the Reminder Taxonomy 
FIELD NUMBER: 1.6                       FIELD NAME: INACTIVE FLAG
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This flags the Reminder Taxonomy as inactive.  
 GENERAL DESCRIPTION:   This IA allows for a global read of the .01 and 1.6
 fields of file 811.2.  
  STATUS: Active
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4474                            IA #: 4474
  FILE NUMBER: 811.3                    GLOBAL ROOT: PXD(811.3,
  DATE CREATED: JAN 17, 2006            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: EXPANDED REMINDER TAXONOMIES
  ID: PXD(811.3,
GLOBAL REFERENCE: PXD(811.3,D0,80,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ICD9 CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PXD(811.3,D0,80.1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ICD0 CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PXD(811.3,D0,81,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CPT CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This IA allows for a global read of the .01 fields of
 the 80, 80.1, 81 subnodes of file 811.3.  
  STATUS: Active
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4475                            IA #: 4475
  GLOBAL ROOT: DD(                      DATE CREATED: JAN 25, 2006
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Code Set DD Fixes               ID: DD(
 GENERAL DESCRIPTION:   During the SQA of patch LEX*2.0*39, several anomalies
 were discovered with the Lexicon, CPT and ICD data files stemming from the
 Code Set Versioning and Code Text Descriptors projects.  There were several
 identical fields identified by the cross-references, and a field that points
 to a non-existing file.  
  
 Rather than delete the DD and refresh it, potentially wiping out local mods,
 the Lexicon team is requesting a one-time permission to write and delete
 directly from the Data Dictionary.  
  
 The code is as follows: 
  
  
   1  File #757.28, Index "ACT" has duplicate Fields 
        Field .01  ACTIVATION EFFECTIVE DATE 
        Field  1   ACTIVATION STATUS 
  
            S ^DD(757.02,1,1,2,0)="757.02^ACT1^MUMPS" 
            S ^DD(757.28,.01,1,2,0)="757.02^ACT2^MUMPS" 
            S ^DD(757.28,1,1,1,0)="757.02^ACT3^MUMPS" 
            K ^DD(757.02,0,"IX","ACT",757.02,1) 
            K ^DD(757.02,0,"IX","ACT",757.28,.01) 
            K ^DD(757.02,0,"IX","ACT",757.28,1) 
            S ^DD(757.02,0,"IX","ACT1",757.02,1)="" 
            S ^DD(757.02,0,"IX","ACT2",757.28,.01)="" 
            S ^DD(757.02,0,"IX","ACT3",757.28,1)="" 
  
   2  File #757.02, Index "APCODE" has duplicate Fields 
        Field 1   EXPRESSION 
        Field 4   PREFERENCE FLAG 
  
            S ^DD(757.02,1,1,4,0)="757.02^APCODE1^MUMPS" 
            S ^DD(757.02,4,1,1,0)="757.02^APCODE2^MUMPS" 
            K ^DD(757.02,0,"IX","APCODE",757.02,1) 
            K ^DD(757.02,0,"IX","APCODE",757.02,4) 
            S ^DD(757.02,0,"IX","APCODE1",757.02,1)="" 
            S ^DD(757.02,0,"IX","APCODE2",757.02,4)="" 
  
   3  File #81.02, Index "ACT" has duplicate Fields 
        Field .01  EFFECTIVE DATE 
        Field .02  STATUS 
  
            S ^DD(81,.01,1,5,0)="81^ACT1^MUMPS" 
            S ^DD(81.02,.01,1,2,0)="81^ACT2^MUMPS" 
            S ^DD(81.02,.02,1,1,0)="81^ACT3^MUMPS" 
            K ^DD(81,0,"IX","ACT",81,.01) 
            K ^DD(81,0,"IX","ACT",81.02,.01) 
            K ^DD(81,0,"IX","ACT",81.02,.02) 
            S ^DD(81,0,"IX","ACT1",81,.01)="" 
            S ^DD(81,0,"IX","ACT2",81.02,.01)="" 
            S ^DD(81,0,"IX","ACT3",81.02,.02)="" 
  
   4  File #81.33, Index "ACT" has duplicate Fields 
        Field .01   EFFECTIVE DATE 
        Field .02   STATUS 
  
            S ^DD(81.3,.01,1,3,0)="81.3^ACT1^MUMPS" 
            S ^DD(81.33,.01,1,2,0)="81.3^ACT2^MUMPS" 
            S ^DD(81.33,.02,1,1,0)="81.3^ACT3^MUMPS" 
            K ^DD(81.3,0,"IX","ACT",81.3,.01) 
            K ^DD(81.3,0,"IX","ACT",81.33,.01) 
            K ^DD(81.3,0,"IX","ACT",81.33,.02) 
            S ^DD(81.3,0,"IX","ACT1",81.3,.01)="" 
            S ^DD(81.3,0,"IX","ACT2",81.33,.01)="" 
            S ^DD(81.3,0,"IX","ACT3",81.33,.02)="" 
  
   5  File #80.066, Index "ACT" has duplicate Fields 
        Field .01   EFFECTIVE DATE 
        Field .02   STATUS 
  
            S ^DD(80,.01,1,4,0)="80^ACT1^MUMPS" 
            S ^DD(80.066,.01,1,2,0)="80^ACT2^MUMPS" 
            S ^DD(80.066,.02,1,1,0)="80^ACT3^MUMPS" 
            K ^DD(80,0,"IX","ACT",80,.01) 
            K ^DD(80,0,"IX","ACT",80.066,.01) 
            K ^DD(80,0,"IX","ACT",80.066,.02) 
            S ^DD(80,0,"IX","ACT1",80,.01)="" 
            S ^DD(80,0,"IX","ACT2",80.066,.01)="" 
            S ^DD(80,0,"IX","ACT3",80.066,.02)="" 
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LEXICON UTILITY
 SUBSCRIBING DETAILS:   
  

NUMBER: 4476                            IA #: 4476
  FILE NUMBER: 8925.1                   GLOBAL ROOT: TIU(8925.1,
  DATE CREATED: JAN 25, 2006
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4476
  ID: TIU(8925.1,
GLOBAL REFERENCE: TIU(8925.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ABBREVIATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: STATUS
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Provides FileMan read of .01, .02, and .07 fields in
 8925.1 for CPRS 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   FM read of name, abbreviation, and status of document
 types.  
  DATE ACTIVATED: JUN 04, 2020

NUMBER: 4477                            IA #: 4477
  FILE NUMBER: 8925                     GLOBAL ROOT: TIU(8925,
  DATE CREATED: JAN 25, 2006
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4477
  ID: TIU(8925,
GLOBAL REFERENCE: TIU(8925,C,DFN,D0)
FIELD NUMBER: .01                       FIELD NAME: DOCUMENT TYPE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the C xref of file 8925 to be used as a check if
 the patient has ever had a document type. This access will be changed to a TIU
 API when available.  
 GENERAL DESCRIPTION:   Provides CPRS access to C xref of file 8925 until TIU
 provides an API.  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 26
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4478                            IA #: 4478
  FILE NUMBER: 8925.1                   GLOBAL ROOT: TIU(8925.1,
  DATE CREATED: JAN 25, 2006
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4478
  ID: TIU(8925.1,
GLOBAL REFERENCE: TIU(8925.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: TYPE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: STATUS
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Access to order through file 8925.1 and use the .04 to
 screen entries will be changed to a TIU API when made available.  
 GENERAL DESCRIPTION:   Provides CPRS access to order through 8925.1, using the
 4th piece as a screen.  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 26
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4479                            IA #: 4479
  DATE CREATED: JAN 26, 2006
  CUSTODIAL PACKAGE: ENROLLMENT APPLICATION SYSTEM
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: EASPFSS
  NAME: DBIA4479                        ID: EASPFSS
 GENERAL DESCRIPTION:   IA for PFSS to route a message from the DG package to
 the EAS package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EASPFSS
KEYWORDS: PFSS
COMPONENT/ENTRY POINT: MSG
 COMPONENT DESCRIPTION:   Entry point to hand off message processing.  
VARIABLES: HLMTIENS                     TYPE: Input
 VARIABLES DESCRIPTION:   This variable is assumed and not passed in.  This is
 the same varible that is passed into the DG package when called by the HL7
 package.  
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   The subscriber (DG package) should evaluate an inbound
 A08 message for the EVN.4 segment containing "PFSS0".  If true then the
 inbound A08 message is intended for the EAS package to process insted of the
 DG package.  No changes to the HL7 variable HLMTIENS should be made prior to
 this call.  

NUMBER: 4480                            IA #: 4480
  DATE CREATED: FEB 06, 2006
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSS781
  NAME: DBIA4480                        ID: PSS781
 GENERAL DESCRIPTION:   This DBIA is provided by PDM (Pharmacy Data Management)
 as an API to the PHARMACY PATIENT file (#55). This API is to used in the
 future by all packages accessing this file as all the Pharmacy packages are
 being re-engineered.  
  STATUS: Active
COMPONENT/ENTRY POINT: PSS(PSSDFN,PSSNUM,LIST)
 COMPONENT DESCRIPTION:   Returns Clozapine data from the Pharmacy Patient
 (#55) file.  
VARIABLES: PSSDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Patient [optional] 
VARIABLES: PSSNUM                       TYPE: Input
 VARIABLES DESCRIPTION:   Clozapine Registration Number [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript name used in ^TMP global [REQUIRED] 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=1 for successful return of data or
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST,DFN,53)=CLOZAPINE REGISTRATION NUMBER(#53) 
  
 ^TMP($J,LIST,DFN,54)=CLOZAPINE STATUS(54 - S)^External Format for the Set of
 Codes 
  
 ^TMP($J,LIST,DFN,55)=DATE OF LAST CLOZAPINE RX(55 - D/T)^External Format (ex:
 Sep. 12, 1999) 
  
 ^TMP($J,LIST,DFN,56)=DEMOGRAPHICS SENT(56)^External Format for the Set of
 Codes 
  
 ^TMP($J,LIST,DFN,57)=RESPONSIBLE PROVIDER (pointer value) (57)^NAME (200,.01) 
  
 ^TMP($J,LIST,DFN,58)=REGISTRATION DATE(58 -D/T)^External Format (ex: Sep. 12,
 1999) 
COMPONENT/ENTRY POINT: WRT(PSSDFN,PSSSTAT,LIST)
 COMPONENT DESCRIPTION:   Set Clozapine Status field for Mental Health 
VARIABLES: PSSDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of patient [REQUIRED] 
VARIABLES: PSSSTAT                      TYPE: Input
 VARIABLES DESCRIPTION:   Clozapine Status [REQUIRED] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript name used in ^TMP global [REQUIRED] 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=-1 for failure or 1 for success 

NUMBER: 4481                            IA #: 4481
  DATE CREATED: FEB 14, 2006            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLFNC3
  NAME: HLFNC3                          ID: HLFNC3
 GENERAL DESCRIPTION:   BHS segments are not stored in the ^TMP("HLS",$J)
 global when batch HL7 messages are generated. They are added by the VistA HL7
 engine when the messages are sent. As the result, the application has no
 access to the content of these segments.  
  
 This IA allows the subscribing package to generate the BHS segment in those
 cases when access to the content of the segment is required (e.g. if the
 segment should be written to a host file).  
  STATUS: Active
COMPONENT/ENTRY POINT: BHS(HL,BID,RESULT,SECURITY,MSA)
 COMPONENT DESCRIPTION:   This is a subroutine call with parameter passing that
 returns an HL7 Batch Header (BHS) segment in the variable RESULT (and possibly
 RESULT(1) if the BHS segment is longer than 245 characters).  
VARIABLES: HL                           TYPE: Input
 VARIABLES DESCRIPTION:   The array of values returned by the call to
 INIT^HLFNC2.  
VARIABLES: BID                          TYPE: Input
 VARIABLES DESCRIPTION:   The Batch Control ID to be included in the BHS
 segment. The Batch Control ID for the batch is returned by the call to
 CREATE^HLTF.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   The variable that will be returned to the calling
 application as described above. If the required input parameters HL or BID are
 missing, RESULT is returned equal to null.  
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES

NUMBER: 4482                            IA #: 4482
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: JUL 28, 2004            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: READ OF FILE 44 'AST' AND 'ACST' CROSS-REFERENCES
  ID: SC(
GLOBAL REFERENCE: SC('AST',
 GLOBAL DESCRIPTION:   Request to do a read on the "AST" cross-reference to
 find all hospital locations within a Stop Code.  
GLOBAL REFERENCE: SC('ACST',
 GLOBAL DESCRIPTION:   Request to do a read on the "ACST" cross-reference to
 find all hospital locations within a Stop Code.  
GLOBAL REFERENCE: SC(D0,0)
FIELD NUMBER: 2503                      FIELD NAME: CREDIT STOP CODE
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Appointments to this clinic will receive this stop code
 credit in addition to the 'normal' stop code credit if a stop code different
 from  the 'normal' stop code for this clinic is entered here.  
 GENERAL DESCRIPTION:   Clinical Reminders request permission to do a global
 read on file 44 "AST" and "ACST" cross-references. This gives permission to
 access the CREDIT STOP CODE information in field 2503.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 44
KEYWORDS: SC('AST'
KEYWORDS: PXRM
KEYWORDS: CREDIT STOP CODE
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clincial reminders would like to read the "AST" AND
 "ACST" crossreferences to find hospital locations within stop codes. CR also
 has a need to directly reference the CREDIT STOP CODE field #2503.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   ADDED 6/30/11 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   ADDED 11/3/2011 
SUBSCRIBING PACKAGE: MYHEALTHEVET
 SUBSCRIBING DETAILS:   Added 2/15/13 for MHV*1.0*10 

NUMBER: 4483                            IA #: 4483
  DATE CREATED: SEP 15, 2005
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: Routine                         ROUTINE: PSS50
  NAME: DBIA4483                        ID: PSS50
 GENERAL DESCRIPTION:   This DBIA is provided by PDM (Pharmacy Data Management)
 as an API to the DRUG file (#50). This API is to used in the future by all
 packages accessing this file as all the Pharmacy packages are being
 re-engineered.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DATA(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  DATA^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = GENERIC NAME field of the DRUG file (#50.01). A value of  "??" may be
 used) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSRTOI = If "1" returns only those entries matched to a Pharmacy Orderable
 Item [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = the array defined by the calling party [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,2)=VA CLASSIFICATION(50,2) 
  ^TMP($J,LIST,PSSIEN,2.1)=PHARMACY ORDERABLE ITEM(50,2.1) ^NAME(50.7,.01)^IEN
 of the Dosage Form file (#50.606)^NAME(50.606,.01) 
  ^TMP($J,LIST,PSSIEN,3)=DEA SPECIAL HDLG(50,3) 
  ^TMP($J,LIST,PSSIEN,4)=MAXIMUM DOSE PER DAY(50,4) 
  ^TMP($J,LIST,PSSIEN,5)=STANDARD SIG(50,5) 
  ^TMP($J,LIST,PSSIEN,6)=FSN(50,6) 
  ^TMP($J,LIST,PSSIEN,8)=WARNING LABEL(50,8) 
  ^TMP($J,LIST,PSSIEN,12)=ORDER UNIT(50,12)^ABBREVIATION
 (51.5,.01)^EXPANSION(51.5,.02) 
  ^TMP($J,LIST,PSSIEN,13)=PRICE PER ORDER UNIT(50,13) 
  ^TMP($J,LIST,PSSIEN,14.5)=DISPENSE UNIT(50,14.5) 
  ^TMP($J,LIST,PSSIEN,15)=DISPENSE UNITS PER ORDER UNIT(50,15) 
  ^TMP($J,LIST,PSSIEN,16)=PRICE PER DISPENSE UNIT(50,16) 
  ^TMP($J,LIST,PSSIEN,20)=NATIONAL DRUG FILE ENTRY (50,20)^NAME (50.6,.01) 
  ^TMP($J,LIST,PSSIEN,21)=VA PRODUCT NAME(50,21) 
  ^TMP($J,LIST,PSSIEN,22)=PSNDF VA PRODUCT NAME ENTRY(50,22)^ NAME(50.68,.01) 
  ^TMP($J,LIST,PSSIEN,25)=NATIONAL DRUG CLASS(50,25)^CODE
 (50.605,.01)^CLASSIFICATION(50.605,1) 
  ^TMP($J,LIST,PSSIEN,31)=NDC(50,31) 
  ^TMP($J,LIST,PSSIEN,40)=ACTION PROFILE MESSAGE(50,40) 
  ^TMP($J,LIST,PSSIEN,51)=LOCAL NON-FORMULARY(50,51)^ External format for the
 set of codes 
  ^TMP($J,LIST,PSSIEN,52)=VISN NON-FORMULARY(50,52)^External format for the set
 of codes 
  ^TMP($J,LIST,PSSIEN,63)=APPLICATION PACKAGES' USE(50,63) 
  ^TMP($J,LIST,PSSIEN,64)=PRIMARY DRUG(50,64)^NAME(50.3,.01) 
  ^TMP($J,LIST,PSSIEN,100)=INACTIVE DATE (50,100)^External format (ex: SEP
 12,1999) 
  ^TMP($J,LIST,PSSIEN,101)=MESSAGE(50,101) 
  ^TMP($J,LIST,PSSIEN,"102)=RESTRICTION(50,102) 
  ^TMP($J,LIST,PSSIEN,301)=AR/WS AMIS CATEGORY(50,301)^External format for the
 set of codes 
  ^TMP($J,LIST,PSSIEN,302)=AR/WS AMIS CONVERSION NUMBER (50,302) 
  ^TMP($J,LIST,PSSIEN,400)=SERVICE CODE(50,400) 
  ^TMP($J,LIST,PSSIEN,"FRM",0)= Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"FRM",PSS(1),2 )=FORMULARY ALTERNATIVE (50.065,2)^GENERIC
 NAME (50,.01) 
  ^TMP($J,LIST,PSSIEN,"OLD",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"OLD",PSS(1),.01)=OLD NAME(50.01,.01) 
  ^TMP($J,LIST,PSSIEN,"OLD",PSS(1),.02)=DATE CHANGED (50.01,.02) ^External
 format (ex: SEP 12,1999) 
  ^TMP($J,LIST,PSSIEN,"SYN",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),.01)=SYNONYM(50.1,.01) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),1)=INTENDED USE(50.1,1)^ External format for
 the set of codes 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),2)=NDC CODE(50.1,2) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),403)=DISPENSE UNITS PER ORDER UNIT(50.1,403) 
  ^TMP($J,LIST, "B",GENERIC NAME,PSSIEN)= "" 
  Where: 
  PSS(1) is the IEN of the multiple it referenced 
COMPONENT/ENTRY POINT: INV(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  INV^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = NAME field of the DRUG file (#50.01).  A value of  "??" may be used)
 [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSRTOI = If "1" returns only those entries matched to a Pharmacy Orderable
 Item [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = the array defined by the calling party [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,11)=REORDER LEVEL(50,11) 
  ^TMP($J,LIST,PSSIEN,12)=ORDER UNIT(50,12)^ABBREVIATION
 (51.5,.01)^EXPANSION(51.5,.02) 
  ^TMP($J,LIST,PSSIEN,13)=PRICE PER ORDER UNIT(50,13) 
  ^TMP($J,LIST,PSSIEN,14)=NORMAL AMOUNT TO ORDER (50,14) 
  ^TMP($J,LIST,PSSIEN,14.5)=DISPENSE UNIT(50,14.5) 
  ^TMP($J,LIST,PSSIEN,15)=DISPENSE UNITS PER ORDER UNIT(50,15) 
  ^TMP($J,LIST,PSSIEN,16)=PRICE PER DISPENSE UNIT(50,16) 
  ^TMP($J,LIST,PSSIEN,17)=SOURCE OF SUPPLY(50,17) 
  ^TMP($J,LIST,PSSIEN,17.1)=EXPIRATION DATE(50,17.1) 
  ^TMP($J,LIST,PSSIEN,50)=CURRENT INVENTORY (50,50) 
  ^TMP($J,LIST,PSSIEN,"IFC",0)= Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"IFC",PSS(1),.01)=ITEM NUMBER (50.0441,.01) 
  ^TMP($J,LIST,PSSIEN,"SYN",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),.01)=SYNONYM(50.1,.01) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),1)=INTENDED USE(50.1,1)^ External format for
 the set of codes 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),2)= NDC CODE (50.1,2) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),400)=VSN(50.1,400) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),401)=ORDER UNIT (50.1,401)^
 ABBREVIATION(51.5,.01)^EXPANSION(51.5,.02) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),402)=PRICE PER ORDER UNIT (50.1,402) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),403)=DISPENSE UNITS PER ORDER UNIT(50.1,403) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),404)=PRICE PER DISPENSE UNIT (50.1,404) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),405)=VENDOR(50.1,405) 
  ^TMP($J,LIST, "B",GENERIC NAME,PSSIEN)= "" 
  Where: 
  PSS(1) is the IEN of the multiple it referenced 
COMPONENT/ENTRY POINT: CMOP(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  CMOP^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = GENERIC NAME field of the DRUG file (#50.01).  A value of  "??" may
 be used) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSRTOI = If "1" returns only those entries matched to a Pharmacy Orderable
 Item [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = the array defined by the calling party [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,28)=OP EXTERNAL DISPENSE(50,28)^ External format for the
 set of codes 
  ^TMP($J,LIST,PSSIEN,213)=CMOP DISPENSE(50,213)^External format for the set of
 codes 
  ^TMP($J,LIST,PSSIEN,215)=QUANTITY DISPENSE MESSAGE (50,215) 
  ^TMP($J,LIST,PSSIEN,"AL",0)= Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"AL",PSS(1),.01)=ACTIVITY LOG(50.0214,.01)^External
 format (ex: SEP 12,1999) 
  ^TMP($J,LIST,PSSIEN,"AL",PSS(1),1)=REASON(50.0214,1)^External format for the
 set of codes 
  ^TMP($J,LIST,PSSIEN ,"AL",PSS(1),2)=INITIATOR OF ACTIVITY (50.0214,2) ^
 NAME(200,.01) 
  ^TMP($J,LIST,PSSIEN, "AL",PSS(1),3)=FIELD EDITED(50.0214,3) 
  ^TMP($J,LIST,PSSIEN ,"AL",PSS(1),4)=NEW VALUE(50.0214,4) 
  ^TMP($J,LIST,PSSIEN, "AL",PSS(1),5)=NDF UPDATE(50.0214,5) 
  ^TMP($J,LIST, "B",GENERIC NAME,PSSIEN)= "" 
  Where: 
  PSS(1) is the IEN of entry in the ACTIVITY LOG multiple 
COMPONENT/ENTRY POINT: DRG(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  DRG^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = GENERIC NAME field of the DRUG file (#50.01).  A value of  "??" may
 be used) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSRTOI - If "1" returns only those entries matched to a Pharmacy Orderable
 Item [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = the array defined by the calling party [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,62.01)=DAY (nD) or DOSE (nL) LIMIT(50,62.01) 
  ^TMP($J,LIST,PSSIEN,62.02)=UNIT DOSE MED ROUTE (50,62.02)^NAME(51.2,.01) 
  ^TMP($J,LIST,PSSIEN,62.03)=UNIT DOSE SCHEDULE TYPE(50,62.03)^External format
 for the set of codes 
  ^TMP($J,LIST,PSSIEN,62.04)=UNIT DOSE SCHEDULE(50,62.04) 
  ^TMP($J,LIST,PSSIEN,62.05)=CORRESPONDING OUTPATIENT DRUG (50,62.05)^GENERIC
 NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,905)=CORRESPONDING INPATIENT DRUG (50,905) ^GENERIC
 NAME(50,.01) 
  ^TMP($J,LIST, "B",GENERIC NAME,PSSIEN)= "" 
COMPONENT/ENTRY POINT: ATC(PSSIEN,PSSFT,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  ATC^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = NAME field of the DRUG file (#50.01).  A value of  "??" may be used)
 [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = the array defined by the calling party [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,212.2)=ATC MNEMONIC(50,212.2) 
  ^TMP($J,LIST,PSSIEN,"ATC",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"ATC",PSS(1),.01)=WARD GROUP FOR ATC CANISTER
 (50.0212,.01)^ NAME(57.5,.01) 
  ^TMP($J,LIST,PSSIEN,"ATC",PSS(1),1)=ATC CANISTER (50.0212,1) 
  ^TMP($J,LIST,"C",GENERIC NAME,PSSIEN)="" 
  Where: 
  PSS(1) is the IEN of entry in the ATC CANISTER multiple 
COMPONENT/ENTRY POINT: LAB(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  LAB^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = GENERIC NAME field of the DRUG file (#50.01).  A value of  "??" may
 be used) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSRTOI - If "1" returns only those entries matched to a Pharmacy Orderable
 Item [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = the array defined by the calling party [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,17.2 )=LAB TEST MONITOR(50,17.2) ^NAME(60,.01) 
  ^TMP($J,LIST,PSSIEN,17.3)=MONITOR MAX DAYS(50,17.3) 
  ^TMP($J,LIST,PSSIEN,17.4)=SPECIMEN TYPE(50,17.4) ^NAME(61,.01) 
  ^TMP($J,LIST,PSSIEN,17.5)=MONITOR ROUTINE(50,17.5) 
  ^TMP($J,LIST,PSSIEN,17.6)=LAB MONITOR MARK(50,17.6)^External format for the
 set of codes 
  ^TMP($J,LIST, "B",GENERIC NAME,PSSIEN)= "" 
COMPONENT/ENTRY POINT: CLOZ(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  CLOZ^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = GENERIC NAME field of the DRUG file (#50.01).  A value of  "??" may
 be used) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSRTOI - If "1" returns only those entries matched to a Pharmacy Orderable
 Item [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = the array defined by the calling party [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^DATA NOT FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,"CLOZ",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"CLOZ",PSS(1),.01)=LAB TEST MONITOR
 (50.02,.01)^NAME(60,.01) 
  ^TMP($J,LIST,PSSIEN, "CLOZ",PSS(1),1)=MONITOR MAX DAYS (50.02,1) 
  ^TMP($J,LIST,PSSIEN, "CLOZ",PSS(1),2)=SPECIMEN TYPE(50.02,2) ^NAME(61,.01) 
  ^TMP($J,LIST,PSSIEN, "CLOZ",PSS(1),3)=TYPE OF TEST(50.02,3) ^External format
 for the set of codes 
  ^TMP($J,LIST, "B",GENERIC NAME,PSSIEN)= "" 
  Where: 
  PSS(1) is the IEN of entry in the CLOZAPINE LAB TEST multiple 
COMPONENT/ENTRY POINT: DOSE(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  DOSE^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = NAME field of the DRUG file (#50.01).  A value of  "??" may be used)
 [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSRTOI - If "1" returns only those entries matched to a Pharmacy Orderable
 Item [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = the array defined by the calling party [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,901)=STRENGTH (50,901) 
  ^TMP($J,LIST,PSSIEN,902)=UNIT(50,902)^NAME(50.607,.01) 
  ^TMP($J,LIST,PSSIEN,"LOC",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"LOC",PSS(1),.01)=LOCAL POSSIBLE DOSAGE (50.0904,.01) 
  ^TMP($J,LIST,PSSIEN,"LOC",PSS(1),1)=PACKAGE(50.0904,1)^External format for
 the set of codes 
  ^TMP($J,LIST,PSSIEN,"LOC",PSS(1),2)=BCMA UNITS PER DOSE (50.0904,2) 
  ^TMP($J,LIST,PSSIEN,"LOC",PSS(1),3)=OTHER LANGUAGE DOSAGE NAME(50.0904,3) 
  ^TMP($J,LIST,PSSIEN,"POS",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"POS",PSS(1),.01)=DISPENSE UNITS PER DOSE(50.0903,.01) 
  ^TMP($J,LIST,PSSIEN,"POS",PSS(1),1)=DOSE(50.0903,1) 
  ^TMP($J,LIST,PSSIEN,"POS",PSS(1),2)=PACKAGE(50.0903,2)^External format 
  ^TMP($J,LIST,PSSIEN,"POS",PSS(1),3)=BCMA UNITS PER DOSE(50.0903,3) 
  ^TMP($J,LIST, "B",GENERIC NAME,PSSIEN)="" 
  Where: 
  PSS(1) is the IEN of the multiple it referenced 
COMPONENT/ENTRY POINT: NDF(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  NDF^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = NAME field of the DRUG file (#50.01).  A value of  "??" may be used)
 [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSRTOI - If "1" returns only those entries matched to a Pharmacy Orderable
 Item [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = the array defined by the calling party [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,20)=NATIONAL DRUG FILE ENTRY (50,20)^NAME (50.6,.01) 
  ^TMP($J,LIST,PSSIEN,21)=VA PRODUCT NAME(50,21) 
  ^TMP($J,LIST,PSSIEN,22)=PSNDF VA PRODUCT NAME ENTRY(50,22) ^NAME(50.68,.01) 
  ^TMP($J,LIST,PSSIEN,23)=PACKAGE SIZE(50,23)^NAME(50.609,.01) 
  ^TMP($J,LIST,PSSIEN,24)=PACKAGE TYPE(50,24)^NAME(50.608,.01) 
  ^TMP($J,LIST,PSSIEN,25)=NATIONAL DRUG CLASS(50,25)^CODE
 (50.605,.01)^CLASSIFICATION(50.605,1) 
  ^TMP($J,LIST,PSSIEN,27)=CMOP ID(50,27) 
  ^TMP($J,LIST,PSSIEN,29)=NATIONAL FORMULARY INDICATOR (50,29)^External format
 for the set of codes 
  ^TMP($J,LIST,"B",GENERIC NAME,PSSIEN)="" 
COMPONENT/ENTRY POINT: WS(PSSIEN,PSSFT,PSSFL,PSSPK, PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  WS^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = NAME field of the DRUG file (#50.01).  A value of  "??" may be used)
 [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSRTOI = If passed in a 1, returns only those entries matched to a Pharmacy
 Orderable Item [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = the array defined by the calling party [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,300)=INPATIENT PHARMACY LOCATION (50,300) 
  ^TMP($J,LIST,PSSIEN,301)=AR/WS AMIS CATEGORY(50,301)^External format for the
 set of codes 
  ^TMP($J,LIST,PSSIEN,302)=AR/WS AMIS CONVERSION NUMBER (50,302) 
  ^TMP($J,LIST,"B",GENERIC NAME,PSSIEN)="" 
COMPONENT/ENTRY POINT: ARWS(PSSIEN,PSSFT,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  ARWS^PSS50(PSSIEN,PSSFT,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = NAME field (#.01) of the DRUG file (#50) (a value of  "??" may be
 used) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,2)=VA CLASSIFICATION(50,2) 
  ^TMP($J,LIST,PSSIEN,3)=DEA SPECIAL HDLG(50,3) 
  ^TMP($J,LIST,PSSIEN,12)=ORDER UNIT(50,12)^ABBREVIATION
 (51.5,.01)^EXPANSION(51.5,.02) 
  ^TMP($J,LIST,PSSIEN,13)=PRICE PER ORDER UNIT(50,13) 
  ^TMP($J,LIST,PSSIEN,14.5)=DISPENSE UNIT(50,14.5) 
  ^TMP($J,LIST,PSSIEN,15)=DISPENSE UNITS PER ORDER UNIT(50,15) 
  ^TMP($J,LIST,PSSIEN,16)=PRICE PER DISPENSE UNIT(50,16) 
  ^TMP($J,LIST,PSSIEN,20)=NATIONAL DRUG FILE ENTRY (50,20)^NAME (50.6,.01) 
  ^TMP($J,LIST,PSSIEN,21)=VA PRODUCT NAME(50,21) 
  ^TMP($J,LIST,PSSIEN,22)=PSNDF VA PRODUCT NAME ENTRY(50,22)^ NAME(50.68,.01) 
  ^TMP($J,LIST,PSSIEN,23)= PACKAGE SIZE (50,23)^NAME (50.609,.01) 
  ^TMP($J,LIST,PSSIEN,25)=NATIONAL DRUG CLASS(50,25)^CODE
 (50.605,.01)^CLASSIFICATION(50.605,1) 
  ^TMP($J,LIST,PSSIEN,31)=NDC(50,31) 
  ^TMP($J,LIST,PSSIEN,51)=LOCAL NON-FORMULARY(50,51)^ External format for the
 set of codes 
  ^TMP($J,LIST,PSSIEN,52)=VISN NON-FORMULARY(50,52)^External format for the set
 of codes 
  ^TMP($J,LIST,PSSIEN,301)=AR/WS AMIS CATEGORY(50,301)^External format for the
 set of codes 
  ^TMP($J,LIST,PSSIEN,302)=AR/WS AMIS CONVERSION NUMBER (50,302) 
  ^TMP($J,LIST,"B",GENERIC NAME,PSSIEN)="" 
COMPONENT/ENTRY POINT: CSYN(PSSIEN,PSSVAL,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  CSYN^PSS50(PSSIEN,PSSVAL,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in DRUG file (#50) [required] 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSVAL = SYNONYM subfield (#.01) of the SYNONYM multiple of the DRUG file
 (#50) [required] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,"SYN",0)= Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),.01)=SYNONYM(50.1,.01) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),403)=DISPENSE UNITS PER ORDER UNIT(50.1,403) 
  ^TMP($J,LIST,"C",SYNONYM,PSSIEN)="" 
  Definition: 
  PSS(1) is the IEN of the SYNONYM multiple 
COMPONENT/ENTRY POINT: MRTN(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  MRTN^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = NAME field of the DRUG file (#50.01).  A value of  "??" may be used)
 [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSRTOI = If passed in a 1, returns only those entries matched to a Pharmacy
 Orderable Item [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = the array defined by the calling party [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,17.2)=LAB TEST MONITOR(50,17.2)^NAME (60,.01) 
  ^TMP($J,LIST,PSSIEN,17.5)=MONITOR ROUTINE(50,17.5) 
  ^TMP($J,LIST,PSSIEN,31)=NDC(50,31) 
  ^TMP($J,LIST,"B",GENERIC NAME,PSSIEN)="" 
COMPONENT/ENTRY POINT: DSPUNT(PSSIEN,PSSIEN2,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  DSPUNT^PSS50(PSSIEN,PSSIEN2,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in DRUG file (#50) [required] 
VARIABLES: PSSIEN2                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN2 = IEN of entry in SYNONYM multiple of the DRUG file (#50) [required] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = the array defined by the calling party [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,"SYN",0)= Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,PSS(1),.01)=SYNONYM(50.1,.01) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),403)=DISPENSE UNITS PER ORDER UNIT(50.1,403) 
  ^TMP($J,LIST",C",SYNONYM,PSSIEN)="" 
  Definition: 
  PSS(1) is the IEN of the SYNONYM multiple 
COMPONENT/ENTRY POINT: ZERO(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  ZERO^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = NAME field of the DRUG file (#50.01).  A value of  "??" may be used)
 [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSRTOI = If passed in a 1, return only those entries matched to a Pharmacy
 Orderable Item [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,2)=VA CLASSIFICATION(50,2) 
  ^TMP($J,LIST,PSSIEN,3)=DEA SPECIAL HDLG(50,3) 
  ^TMP($J,LIST,PSSIEN,4)=MAXIMUM DOSE PER DAY(50,4) 
  ^TMP($J,LIST,PSSIEN,5)=STANDARD SIG(50,5) 
  ^TMP($J,LIST,PSSIEN,6)=FSN(50,6) 
  ^TMP($J,LIST,PSSIEN,8)=WARNING LABEL(50,8) 
  ^TMP($J,LIST,PSSIEN,51)=LOCAL NON-FORMULARY(50,51)^ External format for the
 set of codes 
  ^TMP($J,LIST,PSSIEN,52)=VISN NON-FORMULARY(50,52)^External format for the set
 of codes 
  ^TMP($J,LIST,PSSIEN,101)=MESSAGE(50,101) 
  ^TMP($J,LIST, "B",GENERIC NAME,PSSIEN)= "" 
COMPONENT/ENTRY POINT: $$NOCMOP(PSSIEN,PSSFL)
 COMPONENT DESCRIPTION:   
  Format: 
  S X=$$NOCMOP^PSS50(PSSIEN,PSSFL) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFL = verifies if ^PSDRUG(D0,3) node existed and the CMOP DISPENSE field
 (#213) = 0 if PSSFL = 1 
  
 PSSFL=0 or null will check if ^PSDRUG(D0,3) node is not existed 
VARIABLES: $$NOCMOP                     TYPE: Output
 VARIABLES DESCRIPTION:   
  X 
  Where X is: 
  0 (zero) conditions are not met 
  1 (one) condition is met 
COMPONENT/ENTRY POINT: MSG(LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  MSG^PSS50(LIST) 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = array defined by the calling application 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,100)=INACTIVE DATE(50,100)^External format (ex: SEP
 12,1999) 
  ^TMP($J,LIST,"B",GENERIC NAME,PSSIEN)="" 
COMPONENT/ENTRY POINT: IEN(LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  IEN^PSS50(LIST) 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = array defined by the calling application 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,"AIU",GENERIC NAME,PSSIEN)="" 
  ^TMP($J,LIST,"IU",GENERIC NAME,PSSIEN)="" 
COMPONENT/ENTRY POINT: B(PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  B^PSS50(PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = NAME field of the DRUG file (#50.01) A value of  "??" may be used)
 [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSRTOI = If passed in a 1, return only those entries matched to a Pharmacy
 Orderable Item [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST, "B",GENERIC NAME,PSSIEN)= "" 
  Where: 
  PSSIEN is IEN of entry in the DRUG file (#50) 
COMPONENT/ENTRY POINT: $$SKB(PSSIEN,PSSFL)
 COMPONENT DESCRIPTION:   
  Format: 
  S X=$$SKB^PSS50(PSSIEN,PSSFL) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in DRUG file (#50) [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFL = Either "S" (set) or "K"  (kill) action [required] 
VARIABLES: $$SKB                        TYPE: Output
 VARIABLES DESCRIPTION:   
  X 
  Where X is: 
  0 (zero) action unsuccessful 
  1 (one) action is accomplished 
COMPONENT/ENTRY POINT: VAC(PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  VAC^PSS50(PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSVAL = the NATIONAL DRUG CLASS field (#25) of the DRUG file (#50)
 [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST - the array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST, "VAC",GENERIC NAME,PSSIEN)= "" 
  Where: 
  PSSIEN is IEN of entry in the DRUG file (#50) 
COMPONENT/ENTRY POINT: NDC(PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  NDC^PSS50(PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSVAL = NDC field (#31) of the DRUG file (#50) [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST= array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST, "NDC",GENERIC NAME,PSSIEN)= "" 
  Where: 
  PSSIEN is IEN of entry in the DRUG file (#50) 
COMPONENT/ENTRY POINT: ASP(PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  ASP^PSS50(PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSVAL = PHARMACY ORDERABLE ITEM field (#2.1) of the DRUG file (#50)
 [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST= array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,"ASP",GENERIC NAME,PSSIEN)="" 
  Where: 
  PSSIEN is IEN of entry in the DRUG file (#50) 
COMPONENT/ENTRY POINT: AND(PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  AND^PSS50(PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSVAL = NATIONAL DRUG FILE ENTRY field (#20) of the DRUG file (#50)
 [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST= array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,"AND",GENERIC NAME,PSSIEN)="" 
  Where: 
  PSSIEN is IEN of entry in the DRUG file (#50) 
COMPONENT/ENTRY POINT: AB(PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  AB^PSS50(PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSVAL = ITEM NUMBER sub-field (#.01) of the IFCAP ITEM NUMBER multiple in
 the DRUG file (#50) [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST= array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)= GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,"IFC",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"IFC",PSS(1),.01)=ITEM NUMBER(50.0441,.01) 
  ^TMP($J,LIST,"AB",GENERIC NAME,PSSIEN)="" 
  Where: 
  PSSIEN is IEN of entry in the DRUG file (#50) 
  PSS(1) is the IEN of entry in the IFCAP ITEM NUMBER multiple 
COMPONENT/ENTRY POINT: AP(PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  AP^PSS50(PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSVAL = PRIMARY DRUG field (#64) of the DRUG file (#50) [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,"AP",GENERIC NAME,PSSIEN)="" 
  Where: 
  PSSIEN is IEN of entry in the DRUG file (#50) 
COMPONENT/ENTRY POINT: AOC(PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  AOC^PSS50(PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSVAL = VA CLASSIFICATION field (#2) of the DRUG file (#50) [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST= array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,"AOC",GENERIC NAME,PSSIEN)="" 
  Where: 
  PSSIEN is IEN of entry in the DRUG file (#50) 
COMPONENT/ENTRY POINT: C(PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  C^PSS50(PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSVAL = SYNONYM sub-field (#.01) of the SYNONYM multiple of the DRUG file
 (#50).  The synonym needs to be enclosed in quotes otherwise the leading
 zeroes get stripped off by the system [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST= array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,PSS(1),.01)=SYNONYM(50.1,.01) 
  ^TMP($J,LIST,PSSIEN,PSS(1),1)=INTENDED USE(50.1,1) ^External format for the
 set of codes 
  ^TMP($J,LIST,PSSIEN,PSS(1),2)=NDC CODE(50.1,2) 
  ^TMP($J,LIST,PSSIEN,PSS(1),400)=VSN(50.1,400) 
  ^TMP($J,LIST,PSSIEN,PSS(1),401)=ORDER UNIT(50.1,401)^ ABBREVIATION(51.5,.01) 
  ^TMP($J,LIST,PSSIEN,PSS(1),402)=PRICE PER ORDER UNIT (50.1,402) 
  ^TMP($J,LIST,PSSIEN,PSS(1),403)=DISPENSE UNITS PER ORDER UNIT(50.1,403) 
  ^TMP($J,LIST,PSSIEN,PSS(1),404)=PRICE PER DISPENSE UNIT (50.1,404) 
  ^TMP($J,LIST,PSSIEN,PSS(1),405)=VENDOR(50.1,405) 
  ^TMP($J,LIST,"C",GENERIC NAME,PSSIEN)="" 
  Where: 
  PSSIEN is IEN of entry in the DRUG file (#50) 
  PSS(1) is the IEN of entry in the SYNONYM multiple 
COMPONENT/ENTRY POINT: AVSN(PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  AVSN^PSS50(PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSVAL = VSN sub-field (#400) of the SYNONYM multiple of the DRUG file (#50)
 [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] Dose) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST= array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,"SYN",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),.01)=SYNONYM(50.1,.01) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),1)=INTENDED USE(50.1,1)^External format for
 the set of codes 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),2)=NDC CODE(50.1,2) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),400)=VSN(50.1,400) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),,401)=ORDER UNIT (50.1,401)^
 ABBREVIATION(51.5,.01) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),402)=PRICE PER ORDER UNIT (50.1,402) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),403)=DISPENSE UNITS PER ORDER UNIT(50.1,403) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),404)=PRICE PER DISPENSE UNIT (50.1,404) 
  ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),405)=VENDOR(50.1,405) 
  ^TMP($J,LIST,"AVSN",GENERIC NAME,PSSIEN)="" 
  Where: 
  PSSIEN is IEN of entry in the DRUG file (#50) 
  PSS(1) is the IEN of entry in the SYNONYM multiple 
COMPONENT/ENTRY POINT: $$AQ(PSSIEN)
 COMPONENT DESCRIPTION:   
  Format: 
  S X=$$AQ^PSS50(PSSIEN) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of the DRUG in the DRUG file (#50) [required] 
VARIABLES: $$AQ                         TYPE: Output
 VARIABLES DESCRIPTION:   
  X 
  Where X is: 
  0 (zero) = IEN does not exist in the cross-reference 
  1 (one) = IEN exists in the cross-reference 
COMPONENT/ENTRY POINT: $$SKAQ(PSSIEN,PSSFL)
 COMPONENT DESCRIPTION:   
  Format: 
  S X=$$SKAQ^PSS50(PSSIEN,PSSFL) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in DRUG file (#50) [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFL = Either "S" (set) or "K"  (kill) action [required] 
VARIABLES: $$SKAQ                       TYPE: Output
 VARIABLES DESCRIPTION:   
  X 
  Where X is: 
  0 (zero) = action unsuccessful 
  1 (one)  = action accomplished 
COMPONENT/ENTRY POINT: $$SKAQ1(PSSIEN)
 COMPONENT DESCRIPTION:   
  Format: 
  S X=$$SKAQ1^PSS50(PSSIEN) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in DRUG file (#50) [required] 
VARIABLES: $$SKAQ1                      TYPE: Output
 VARIABLES DESCRIPTION:   
  X 
  Where X is: 
  0 (zero) = action unsuccessful 
  1 (one)  = action accomplished 
COMPONENT/ENTRY POINT: AQ1(PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  AQ1^PSS50(PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSVAL = CMOP ID field (#27) of the DRUG file (#50) [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST= array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,"AQ1",GENERIC NAME,PSSIEN)="" 
  Where: 
  PSSIEN is IEN of entry in the DRUG file (#50) 
COMPONENT/ENTRY POINT: OLDNM(PSSIEN,PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  OLDNM^PSS50(PSSIEN,PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in DRUG file (#50) [optional] 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSVAL = NAME field (#.01) of the DRUG file (#50) (a value of  "??" may be
 used) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,"OLD",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"OLD",PSS(1),.01)=OLD NAME(50.01,.01) 
  ^TMP($J,LIST,PSSIEN,"OLD",PSS(1),.02)=DATE CHANGED(50.01,.02) ^External
 format (ex: SEP 12,1999) 
  ^TMP($J,LIST,"B",GENERIC NAME,PSSIEN)="" 
  Where: 
  PSS(1) is the IEN of entry in the OLD NAME multiple 
COMPONENT/ENTRY POINT: $$ADDOLDNM(PSSIEN,PSSIEN2,PSSONM,PSSDT)
 COMPONENT DESCRIPTION:   
  Format: 
  S X=$$ADDOLDNM^PSS50(PSSIEN,PSSIEN2,PSSONM,PSSDT) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in DRUG file (#50) [optional] 
VARIABLES: PSSIEN2                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN2 = IEN of entry in OLD NAME multiple of the DRUG file (#50) [required] 
VARIABLES: PSSONM                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSONM = OLD NAME field (#.01) of the OLD NAME multiple of the DRUG file
 (#50) [optional] 
VARIABLES: PSSDT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSDT = DATE CHANGED field (#2) of the OLD NAME multiple of the DRUG file
 (#50) [optional] 
VARIABLES: $$ADDOLDNM                   TYPE: Output
 VARIABLES DESCRIPTION:   
  X 
  Where X is: 
  0 (zero) = entry was unsuccessful 
  1 (one) = entry was added 
COMPONENT/ENTRY POINT: A526(PSSIEN,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  A526^PSS50(PSSIEN,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in DRUG file (#50) [required] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST= array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN2,.01)=PRINT NAME (52.6,.01) 
  ^TMP($J,LIST,"A526",PRINT NAME,PSSIEN2)="" 
  Where: 
  PSSIEN2 is IEN of entry in IV ADDITIVE file (#52.6) 
COMPONENT/ENTRY POINT: A527(PSSIEN,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  A527^PSS50(PSSIEN,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in DRUG file (#50) [required] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN2,.01)=PRINT NAME (52.7,.01) 
  ^TMP($J,LIST,"A527",PRINT NAME,PSSIEN2)="" 
  Where: 
  PSSIEN2 is IEN of entry in IV SOLUTION file (#52.7) 
COMPONENT/ENTRY POINT: AIU(PSSFT,PSSPK,PSSFL,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  AIU^PSS50(PSSFT,PSSPK,PSSFL,LIST) 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = NAME field (#.01) of the DRUG file (#50) [required] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST= array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,"AIU",GENERIC NAME,PSSIEN)="" 
  Where: 
  PSSIEN is IEN of entry in the DRUG file (#50) 
COMPONENT/ENTRY POINT: IU(PSSFL,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  IU^PSS50(PSSFL,LIST) 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST= array defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,"IU",GENERIC NAME,PSSIEN)="" 
  Where: 
  PSSIEN is IEN of entry in the DRUG file (#50) 
COMPONENT/ENTRY POINT: $$SKAIU(PSSIEN,PSSFL)
 COMPONENT DESCRIPTION:   
  Format: 
  S X=$$SKAIU^PSS50(PSSIEN,PSSFL) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in DRUG file (#50) [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFL = Either "S" (set) or "K" (kill) action [required] Note: The
 APPLICATION PACKAGES' USE (50,63) must be updated prior to calling this API.  
VARIABLES: $$SKAIU                      TYPE: Output
 VARIABLES DESCRIPTION:   
  X 
  Where X is: 
  0 (zero) = action unsuccessful 
  1 (one)  = action accomplished 
COMPONENT/ENTRY POINT: $$SKIU(PSSIEN)
 COMPONENT DESCRIPTION:   
  Format: 
  S X=$$SKIU^PSS50(PSSIEN) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in DRUG file (#50) [required] Note: The APPLICATION
 PACKAGES' USE (50,63) must be updated prior to calling this API.  
VARIABLES: $$SKIU                       TYPE: Output
 VARIABLES DESCRIPTION:   
  X 
  Where X is: 
  0 (zero) = action unsuccessful 
  1 (one)  = action accomplished 
COMPONENT/ENTRY POINT: LOOKUP(PSSFT,PSSFL,PSSPK,PSSRTOI,PSSIFCAP,PSSCMOP,PSSD,LI
ST)
 COMPONENT DESCRIPTION:   
  Format: 
  LOOKUP^PSS50(PSSFT,PSSFL,PSSPK,PSSRTOI,PSSIFCAP,PSSCMOP,PSSD,LIST) 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = A look up value that could be the NAME field (#.01), IEN, VA PRODUCT
 NAME (#21), NATIONAL DRUG CLASS (#25), or SYNONYM (#.01) multiple of the DRUG
 file (#50) (a value of"??" may be used) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSRTOI = If "1" returns only those entries matched to a Pharmacy Orderable
 Item [optional] 
VARIABLES: PSSIFCAP                     TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIFCAP = If this flag is passed in with a 1, the API returns those drug
 entries that do not have the IFCAP ITEM NUMBER (#441) multiple existed in the
 DRUG file (#50) [optional] 
VARIABLES: PSSCMOP                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSCMOP = If this flag is passed in with a 1, the API returns those drug
 entries that do not have data in the CMOP ID (#27) of the DRUG file (#50)
 [optional] 
VARIABLES: PSSD                         TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSD = Multiple index lookup is performed if passed in (ex: "B", "C", "VAPN",
 "VAC"). Otherwise only the "B" cross-reference is used [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = array defined by the calling application 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,25)=NATIONAL DRUG CLASS(50,25)^CODE (50.605,.01)^
 CLASSIFICATION(50.605,1)) 
  ^TMP($J,LIST,PSSIEN,100)=INACTIVE DATE(50,100)^External format 
  (ex: SEP 12,1999) 
  ^TMP($J,LIST,PSSIEN,101)=MESSAGE(50,101) 
  ^TMP($J,LIST,PSSDX,GENERIC NAME,PSSIEN)="" 
  Where: 
  PSSIEN is IEN of entry in the DRUG file (#50) 
  PSSDX is value passed in the PSSD. If multiple values are passed in, or the
 back tick IEN lookup is used, "B" will be used.  
COMPONENT/ENTRY POINT: FRMALT(PSSIEN,PSSFT,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  FRMALT^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in DRUG file (#50) [required] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = NAME field (#.01) of the DRUG file (#50) (a value of  "??" may be
 used)  [optional] 
  
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = array defined by the calling application 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,25)=NATIONAL DRUG CLASS(50,25) 
  ^TMP($J,LIST,PSSIEN,100)=INACTIVE DATE (50,100)^External format (ex: SEP
 12,1999) 
  ^TMP($J,LIST,PSSIEN,101)=MESSAGE(50,101) 
  ^TMP($J,LIST,PSSIEN,"FRM",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,"FRM",PSS(1),2)=FORMULARY ALTERNATIVE (50.065,2)^GENERIC
 NAME (50,.01) 
  ^TMP($J,LIST,"B",GENERIC NAME,PSSIEN)="" 
  Where: 
  PSS(1) is the IEN of the FORMULARY ALTERNATIVE multiple 
COMPONENT/ENTRY POINT: LABEL(PSSIEN,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  LABEL^PSS50(PSSIEN,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in the DRUG file (#50) [required] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = array defined by the calling application 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,25)= NATIONAL DRUG CLASS(50,25)^CODE (50.605,.01)^
 CLASSIFICATION(50.605,1) 
  ^TMP($J,LIST,PSSIEN,51)=LOCAL NON FORMULARY(50,51)^ External format for the
 set of codes 
  ^TMP($J,LIST,PSSIEN,100)=INACTIVE DATE(50,100)^External format (ex: SEP
 12,1999) 
  ^TMP($J,LIST,PSSIEN,101)=MESSAGE(50,101) 
  ^TMP($J,LIST,PSSIEN,102)=RESTRICTION(50,102) 
  ^TMP($J,LIST, "B",GENERIC NAME,PSSIEN)= "" 
COMPONENT/ENTRY POINT: LIST(PSSFT,PSSFL,PSSD,PSSPK,LIST)
 COMPONENT DESCRIPTION:   
  Format: 
  LIST^PSS50(PSSFT,PSSFL,PSSD,PSSPK,LIST) 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFT = NAME field (#.01) of the DRUG file (#50) (a value of  "??" may be
 used)  [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date. A Null value will return all
 entries.  Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date. [optional] 
VARIABLES: PSSD                         TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSD = the index used in the lookup, (ex: "B","C"-cross reference) 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSPK = Returns the APPLICATION PACAKGES USE (ex: "IU" returns the
 APPLICATION PACKAGES' USE for IV and Unit Dose [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   
  LIST = array defined by the call application [required] Note: If PSSFT =
 "??", the "B" cross reference will be used and PSSD is ignored 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  ^TMP($J,LIST,PSSIEN,2.1)=PHARMACY ORDERABLE ITEM (50,2.1)^NAME(50.7,.01) ^IEN
 of the Dosage Form file (#50.606) 
  ^TMP($J,LIST,PSSIEN,100)=INACTIVE DATE (50,100)^External format (ex: SEP
 12,1999) 
  ^TMP($J,LIST, PSSDX,GENERIC NAME,PSSIEN)= "" 
  Where: 
  PSSDX is value passed in the PSSD.  If multiple values are passed in, "B"
 will be used.  
COMPONENT/ENTRY POINT: $$EDTIFCAP(PSSIEN,PSSVAL)
 COMPONENT DESCRIPTION:   
  Format: 
  S X=$$EDTIFCAP^PSS50(PSSIEN,PSSVAL) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSIEN = IEN of entry in the DRUG file (#50) [required] 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSVAL = the ITEM NUMBER subfield (#.01) of the IFCAP ITEM NUMBER multiple in
 the DRUG file (#50) [required] 
VARIABLES: $$EDTIFCAP                   TYPE: Output
 VARIABLES DESCRIPTION:   
  X 
  Where X is: 
  0 (zero) = action unsuccessful 
  1 (one) = action accomplished 
COMPONENT/ENTRY POINT: $$FNAME(PSSFNO,PSSFILE)
 COMPONENT DESCRIPTION:   
  Format: 
  S X=$$FNAME^PSS50(PSSFNO,PSSFILE) 
VARIABLES: PSSFNO                       TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFNO = Field number [required] 
VARIABLES: PSSFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   
  PSSFILE = File number of the sub-files [optional] 
VARIABLES: $$FNAME                      TYPE: Output
 VARIABLES DESCRIPTION:   
  X 
  Where: 
  X = the field name 
COMPONENT/ENTRY POINT: NOCMOP

NUMBER: 4484                            IA #: 4484
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: AUG 26, 2004
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Controlled Subscription
  TYPE: File
  NAME: READ OF STATUS FIELD FOR NON-VA MEDS
  ID: PS(55,
GLOBAL REFERENCE: PS(55,D0,"NVA",
FIELD NUMBER: 5                         FIELD NAME: STATUS
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 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 EMAIL GROUP 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.  
  
 Clinical Reminders is requesting permission to do a FileMan read on the Non-VA
 meds status field. This read is to allow the user to define what the Non-VA
 meds status must for Clinical Reminders to consider the Non-VA meds finding
 item as true.  
     
 Clinical Reminders will use the NVA^PSOPXRM1 API to retrieve the data related
 to a Non-VA med. This API is documented in DBIA #3793.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2006
KEYWORDS: NON-VA
KEYWORDS: PXRM
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4485                            IA #: 4485
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9(
  DATE CREATED: JUL 28, 2004            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ICD DIAGNOSIS
  ID: ICD9(
 GENERAL DESCRIPTION:   Lexicon Utility has all privileges as though it were
 the custodial package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LEXICON UTILITY

NUMBER: 4486                            IA #: 4486
  FILE NUMBER: 80.1                     GLOBAL ROOT: ICD0(
  DATE CREATED: JUL 28, 2004            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ICD OPERATION/PROCEDURE
  ID: ICD0(
 GENERAL DESCRIPTION:   Lexicon Utility has all privileges as though it were
 the custodial package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LEXICON UTILITY

NUMBER: 4487                            IA #: 4487
  FILE NUMBER: 80.2                     GLOBAL ROOT: ICD(
  DATE CREATED: JUL 28, 2004            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DRG
  ID: ICD(
 GENERAL DESCRIPTION:   Lexicon Utility has all privileges as though it were
 the custodial package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LEXICON UTILITY

NUMBER: 4488                            IA #: 4488
  FILE NUMBER: 80.3                     GLOBAL ROOT: ICM(
  DATE CREATED: JUL 28, 2004            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MAJOR DIAGNOSTIC CATEGORY
  ID: ICM(
 GENERAL DESCRIPTION:   Lexicon Utility has all privileges as though it were
 the custodial package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LEXICON UTILITY

NUMBER: 4489                            IA #: 4489
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT(
  DATE CREATED: JUL 28, 2004            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CPT
  ID: ICPT(
 GENERAL DESCRIPTION:   Lexicon Utility has all privileges as though it were
 the custodial package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LEXICON UTILITY

NUMBER: 4490                            IA #: 4490
  FILE NUMBER: 81.1                     GLOBAL ROOT: DIC(81.1,
  DATE CREATED: JUL 28, 2004            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CPT CATEGORY
  ID: DIC(81.1,
 GENERAL DESCRIPTION:   Lexicon Utility has all privileges as though it were
 the custodial package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LEXICON UTILITY

NUMBER: 4491                            IA #: 4491
  FILE NUMBER: 81.2                     GLOBAL ROOT: DIC(81.2,
  DATE CREATED: JUL 28, 2004            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CPT COPYRIGHT
  ID: DIC(81.2,
 GENERAL DESCRIPTION:   Lexicon Utility has all privileges as though it were
 the custodial package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LEXICON UTILITY

NUMBER: 4492                            IA #: 4492
  FILE NUMBER: 81.3                     GLOBAL ROOT: DIC(81.3,
  DATE CREATED: JUL 28, 2004            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CPT MODIFIER
  ID: DIC(81.3,
 GENERAL DESCRIPTION:   Lexicon Utility has all privileges as though it were
 the custodial package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LEXICON UTILITY

NUMBER: 4493                            IA #: 4493
  FILE NUMBER: 771.7                    GLOBAL ROOT: HL(771.7
  DATE CREATED: FEB 14, 2006            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HL7 ERROR MESSAGE FILE
  ID: HL(771.7
GLOBAL REFERENCE: HL(771.7,D0,0)
FIELD NUMBER: .01                       FIELD NAME: SHORT TEXT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The $$MSGSTAT^HLUTIL function returns only a code (IEN)
 of the HL7 error in the 4th component. This IA allows the subscribing package
 to get the corresponding error message.  
  STATUS: Active
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES

NUMBER: 4494                            IA #: 4494
  FILE NUMBER: 757.01                   DATE CREATED: APR 03, 2007
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MODIFY 'B' XREF OF 757.01
  ORIGINAL NUMBER: 321
 GENERAL DESCRIPTION:   The FM team grants the request of the Clinical Lexicon
 package to modify the "B" index of file 757.01 as follows: 
  
 S ^LEX(757.01,"B",$E($$UP^XLFSTR(X),1,63),DA)="" K
 ^LEX(757.01,"B",$E($$UP^XLFSTR(X),1,63),DA) 
  
 It is further agreed that the following tools will not be used with this file:
 DIFROM, COMPARE/MERGE and TRANSFER.  These tools rely on an unmodified 'B'
 index to function properly.  Using the modified 'B' index of file 757.01 along
 with any of the named tools may produce unexpected results.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LEXICON
SUBSCRIBING PACKAGE: LEXICON UTILITY    ISC: Salt Lake City
  DATE ACTIVATED: APR 03, 2007

NUMBER: 4495                            IA #: 4495
  DATE CREATED: AUG 04, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VAFHLZMH                     NAME: DBIA4141-D
  ID: VAFHLZMH
 GENERAL DESCRIPTION:   Supported call for building of HL7 ZMH segment (VA
 Specific Military History Segment).  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ZMH
KEYWORDS: VAFHLZMH
COMPONENT/ENTRY POINT: ENTER(DFN,VAFARRAY,VAFTYPE,VAFSTR,VAFHLS,VAFHLC,VAFHLQ)
 COMPONENT DESCRIPTION:   
        This call is designed to build HL7 ZMH segment. This segment 
        contains VA- specific Military History types VAFTYPE and for each 
         of them different indentifiers can be generated. "ZMH" segments 
        (up to 13) are returned in VAFARRAY array, default is 
        ^TMP("VAFHLZMH",$J) 
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN - pointer to PATIENT file  (#2) - is the only
 required parameter. Defaults 
  are used if no values are passed for the other parameters 
  
VARIABLES: VAFTYPE                      TYPE: Input
 VARIABLES DESCRIPTION:   
         ; VAFTYPE = Military History type desired (separated by commas) where 
         ;            1=Last Service branch (SL) 
         ;            2=Next to last Service branch (SNL) 
         ;            3=Next to next to last Service branch (SNNL) 
         ;            4=Prisoner of War Status indicated? (POW) 
         ;            5=Combat Service indicated? (COMB) 
         ;            6=Vietnam Service indicated? (VIET) 
         ;            7=Lebanon Service indicated? (LEBA) 
         ;            8=Grenada Service indicated? (GREN) 
         ;            9=Panama Service indicated? (PANA) 
         ;           10=Persian Gulf Service indicated? (GULF) 
         ;           11=Somalia Service indicated? (SOMA)    
         ;           12=Yugoslavia Service indicated? (YUGO) 
         ;           13=Purple Heart Receipient? (PH) 
         ;          A range of numbers separated by colons can be sent 
         ;                  (e.g. 1:4,8,10:12) 
         ;          Default is all 12 (1,2,3...) 
VARIABLES: VAFSTR                       TYPE: Input
 VARIABLES DESCRIPTION:   
         ; VAFSTR = Fields (sequence numbers) desired (separated by comma)
 where 
         ;          3=qualifier #1 (Service branch if VAFTYPE is 1,2 or 3 
         ;                         or Yes/No response if VAFTYPE is 4 thru 13) 
         ;            qualifier #2 (Service number if VAFTYPE is 1,2 or 3 
         ;                         or Location if VAFTYPE is 4 or 5) 
         ;                         or 
         ;            qualifier #3 (Service discharge type if VAFTYPE is 1,2 
         ;                          or 3) 
         ;          4=From/To Date range for each VAFTYPE 
         ;          Default is 3,4 
VARIABLES: VAFHLS                       TYPE: Input
 VARIABLES DESCRIPTION:   
         ; VAFHLS = HL7 field separator (1 character) 
         ;          Default is ^ (carrot) 
VARIABLES: VAFHLC                       TYPE: Input
 VARIABLES DESCRIPTION:   
         ; VAFHLC = HL7 encoding characters (4 characters must be supplied) 
         ;          Default is ~|\& (tilde bar backslash ampersand) 
VARIABLES: VAFHLQ                       TYPE: Input
 VARIABLES DESCRIPTION:   
         ; VAFHLQ = HL7 null designation 
         ;          Default is "" (quote quote) 
VARIABLES: VAFARRAY                     TYPE: Output
 VARIABLES DESCRIPTION:   rray name to hold the "ZMH" segments (up to 13).  
        Default is ^TMP("VAFHLZMH",$J) 
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
 SUBSCRIBING DETAILS:   We would like to build ZMH segment for the following
 Types: 
  SL 
  COMB 
  GULF 
  
 The following sequences would be transmitted: SL: Service Separation Date
 [Last] (.327) 
  
 COMB: Combat Service Indicated (.5291)  
       Combat Service Location (.5292) GULF:  Persian Gulf Service (.32201) 
  

NUMBER: 4496                            IA #: 4496
  FILE NUMBER: 53.79                    GLOBAL ROOT: PSB
  DATE CREATED: AUG 06, 2004            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: DBIA4496
  ID: PSB
GLOBAL REFERENCE: PSB(53.79,D0
FIELD NUMBER: .06                       FIELD NAME: ACTION DATE/TIME
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: .07
FIELD NUMBER: .09                       FIELD NAME: ACTION STATUS
  LOCATION: 0;9                         ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   The BCMA MEDICATION LOG file (#53.79) records
 administration actions to medications order.  
 GENERAL DESCRIPTION:   Inpatient Medications requests fileman read access to
 the BCMA MEDICATION LOG file (#53.79) in BAR CODE MEDICATION ADMINISTRATION V.
 3.0.  
  
 BCMA V. 3.0 records administration actions for medication orders that may also
 be acted upon in INPATIENT MEDICATIONS V. 5.0. There is a need for the BCMA V.
 3.0 last action to be seen by users in INPATIENT MEDICATIONS V. 5.0.  
  STATUS: Pending
KEYWORDS: PSJ
KEYWORDS: BCMA
KEYWORDS: BCMA LAST ACTION
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  ISC: Birmingham

NUMBER: 4497                            IA #: 4497
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19,
  DATE CREATED: AUG 17, 2004            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DENTAL EDIT/DELETE OF OPTIONS   ID: DIC(19,
GLOBAL REFERENCE: DIC(19,D0,0)
FIELD NUMBER: 2                         FIELD NAME: OUT OF ORDER MESSAGE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(19,D0,200.9)
FIELD NUMBER: 209                       FIELD NAME: SCHEDULING RECOMMENDED
  LOCATION: 200.9;1                     ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Dental Package would like an agreement with the owner
 of the OPTION file (#19) to Fileman edit and delete of entries in these files,
 due to the plan to retire the old Dental Activity System (DAS) in FY2005.  As
 such the first step of this phase out is to place many DENT* options by
 placing thme OUT OF ORDER.  There will be more than one dental patch to
 accomplish this.  Phase I involves disabling most of the old edit type options
 but leaving some of the reporting options available.  There may or may not be 
 a second patch to disable the remaining old Dental options.  Definitely, when
 DENT 2.0 is released, all of the old DAS options and functionality will be
 removed.  In DENT 2.0, we will include the Dental Options in the KIDS build
 definition with a status of DELETE AT SITE.  
  
 Dental is planning on a patch that would queue up Taskman job to run late in
 the evening on Oct 31, 2004.  That tasked job will place options out of order. 
 The patch will do nothing except scheduled that Taskman job to run at the
 designated time.  This is why we cannot export the OPTIONs with the OUT OF
 ORDER field set.  The local VAMCs are allowed to run those options up until
 Oct 31.  
  
 Dental is requesting: 1. Fileman read to do a lookup on file 19 given an
 option name using either $$FIND1^DIC or FIND^DIC or LIST^DIC 
  
 2. Fileman write access to the OPTION file for fields: 
    2         OUT OF ORDER MESSAGE (F), [0;3] 
    209       SCHEDULING RECOMMENDED (S), [200.9;1] 
  
    S DENT(19,IENS,2) = some appropriate text 
    S DENT(19,IENS,209)="@" 
    D FILE^DIE 
  STATUS: Active
SUBSCRIBING PACKAGE: DENTAL             ISC: Hines

NUMBER: 4498                            IA #: 4498
  DATE CREATED: NOV 09, 2004
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORPXRM                       NAME: 4498
  ID: ORPXRM
 GENERAL DESCRIPTION:   This routine allows one use obtain information on
 orders from the orders file. It also build the Clinical Reminders Index.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: ORDER
KEYWORDS: CLINICAL REMINDERS INDEX
COMPONENT/ENTRY POINT: GETDATA
 COMPONENT DESCRIPTION:   Returns data on specified order. The call in the
 routine looks like GETDATA(ORIFN,DATA).  
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The first parameter is the Internal entry number of
 the Order.  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   The data is returned by way of the second parameter
 when passed in by reference.  
COMPONENT/ENTRY POINT: INDEX
 COMPONENT DESCRIPTION:   This entry point is called to build the Clinical
 Reminders Index for the ORDER file. No variables are required.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clinical reminders will use to get Order Information
 and build the Clincial Reminders Index.  

NUMBER: 4499                            IA #: 4499
  DATE CREATED: AUG 17, 2004
  CUSTODIAL PACKAGE: ENROLLMENT APPLICATION SYSTEM
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: EASECU
  NAME: 4499                            ID: EASECU
 GENERAL DESCRIPTION:   Allow a package to call this routine to return the LTC
 copay status of a patient without requiring a means test.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LTC
COMPONENT/ENTRY POINT: $$LST(DFN,DGDT,DGMTYPT)
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file IEN 
VARIABLES: DGDT                         TYPE: Input
 VARIABLES DESCRIPTION:   DATE/TIME (Default to today) 
VARIABLES: DGMTYPT                      TYPE: Input
 VARIABLES DESCRIPTION:   Type of Test 
VARIABLES: $$LST                        TYPE: Output
 VARIABLES DESCRIPTION:   LTC Co-pay test IEN^Status Code^Date of Test 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

NUMBER: 4500                            IA #: 4500
  DATE CREATED: NOV 09, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: Routine
  ROUTINE: BPSOSL                       NAME: DBIA4500
  ID: BPSOSL
 GENERAL DESCRIPTION:   To allow pharmacy routines to log messages for ECME to
 track performance statistics.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: NCPDP
KEYWORDS: HIPAA
KEYWORDS: BPS
COMPONENT/ENTRY POINT: LOG(TEXT,ECHO,SPECIAL)
 COMPONENT DESCRIPTION:   Creates a log entry point for the calling package.  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   MESSAGE PASSED INTO THE LOG ENTRY 
VARIABLES: ECHO                         TYPE: Input
 VARIABLES DESCRIPTION:   FLAG TO DETERMINE IF THE MESSAGE WILL BE DISPLAYED ON
 SCREEN 
VARIABLES: SPECIAL                      TYPE: Input
 VARIABLES DESCRIPTION:   SWITCH TO TELL THE ROUTINE TO PREFIX THE MESSAGE WITH
 A PRINTABLE DATE OR TIME OR BOTH 
COMPONENT/ENTRY POINT: LOG59(MSG,IEN59)
 COMPONENT DESCRIPTION:   Creates a log entry point for the calling package
 using the claim ien as an identifier.  
VARIABLES: MSG                          TYPE: Input
 VARIABLES DESCRIPTION:   MESSAGE TEXT ASSOCIATED WITH THIS LOG POINT.  
VARIABLES: IEN59                        TYPE: Input
 VARIABLES DESCRIPTION:   CLAIMS ENTRY NUMBER ASSOCIATED WITH THIS MESSAGE.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 4501                            IA #: 4501
  FILE NUMBER: 790.2                    GLOBAL ROOT: WV(790.2,
  DATE CREATED: AUG 23, 2004            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: READ OF THE WV PROCEDURE TYPE FILE
  ID: WV(790.2,
GLOBAL REFERENCE: WV(790.2,'B'
GLOBAL REFERENCE: WV(790.2,D0,1,
FIELD NUMBER: .01                       FIELD NAME: MORPHOLOGY SNOMED CODE
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DIAGNOSIS
  LOCATION: 1;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: WV(790.2,D0,2,
FIELD NUMBER: .01                       FIELD NAME: TOPOGRAPHY SNOMED CODE
  LOCATION: 2;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Clinical Reminders is requesting permission to a direct
 read on the WV PROCEDURE TYPE FILE File #790.2 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: WV
KEYWORDS: WV(790.2,
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4502                            IA #: 4502
  FILE NUMBER: 130                      GLOBAL ROOT: SRF(
  DATE CREATED: SEP 10, 2004            CUSTODIAL PACKAGE: SURGERY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Find Surgical Case # for TIU    ID: SRF(
GLOBAL REFERENCE: SRF(Case#,"TIU")
 GLOBAL DESCRIPTION:   Read acces only.  
 GENERAL DESCRIPTION:   During the upload of TIU documents specific to the
 SURGICAL REPORTS document class, TIU needs to associate the newly uploaded TIU
 data to the correct TIU document stub created by the surgery package.  Surgery 
 maintains the link between the surgical case # and the TIU document in the 
 ^SRF(Case#,"TIU" global which TIU needs to read to ensure the correct linkage. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU SURGERY
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4503                            IA #: 4503
  DATE CREATED: AUG 26, 2004
  CUSTODIAL PACKAGE: ENROLLMENT APPLICATION SYSTEM
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: EASECU                       NAME: 4503
  ID: EASECU
 GENERAL DESCRIPTION:   Allow packages to get the LTC copay status without
 requiring the patient to have had a Means test.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LTC
COMPONENT/ENTRY POINT: $$LST(DFN,DGDT,DGNTYPT)
 COMPONENT DESCRIPTION:   This call is made with 3 parameters the first of
 which is the only one required. The DFN (patient ien), DATE, Test type
 (defaulted to LTC) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: DGDT                         TYPE: Input
 VARIABLES DESCRIPTION:   Date/Time (optional - default TODAY@2359) Used if a
 certain time frame is desired.  
VARIABLES: DGMTYPT                      TYPE: Input
 VARIABLES DESCRIPTION:   Type of Test (Optional) If not defined, LTC Co-pay
 will be assumed.  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   This call is a function call. X would represent the
 variable the data would be sent to as in S X=$$LST^EASECU(DFN,DGDT,DGMTYPT).  
  The variable would look like: LTC Co-pay test IEN^Date of Test^Status 
 Name^Status Code^Source of Test 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   In a Clinical Reminder Dialog Object, Clinical
 Reminders will display the LTC Copay Status for a patient.  

NUMBER: 4504                            IA #: 4504
  FILE NUMBER: 120.52                   GLOBAL ROOT: GMRD(120.52
  DATE CREATED: SEP 08, 2004
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: 4504                            ID: GMRD(120.52
GLOBAL REFERENCE: GMRD(120.52
FIELD NUMBER: .01                       FIELD NAME: QUALIFIER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field supplies a list of possible qualifiers for a
 vital measurement record.  
 GENERAL DESCRIPTION:   This IA will allow package to directly look at the .01
 field in order to get the text of the Vital Qualifier. This also gives the
 packages permission to reference all of the crossreference in the file in
 order to find the entry that is being sought after.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMRV
KEYWORDS: GRMD
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clinical Reminder will retrieve and display the text
 for the Vital Qualifier by direct golbal read.  
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT

NUMBER: 4505                            IA #: 4505
  DATE CREATED: DEC 14, 2010            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  ROUTINE: IBCNBLA1                     NAME: DSIV CALL TO IBCNBLA1
  ID: IBCNBLA1
 GENERAL DESCRIPTION:   The Insurance Capture Buffer (ICB) application uses the
 ICB API in IBCNBLA1 to update the buffer symbol when retrieving or refreshing 
 buffer entries.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ICB(IBBUFDA)
 COMPONENT DESCRIPTION:   Called by ICB to update eIV status flag (symbol) in
 the insurance buffer entry.  
VARIABLES: IBBUFDA                      TYPE: Input
 VARIABLES DESCRIPTION:   The Insurance Buffer file (#355.33) IEN 
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER

NUMBER: 4506                            IA #: 4506
  FILE NUMBER: 365.15                   GLOBAL ROOT: IBE(365.15,
  DATE CREATED: DEC 14, 2010            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IIV STATUS TABLE ACCESS
  ID: IBE(365.15,
GLOBAL REFERENCE: IBE(365.15,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ASCII VALUE FOR IIV STATUS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: EXPAND ENTRY ACTION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Error display code will quit if the entry does not allow
 expanded entry action 
GLOBAL REFERENCE: IBE(365.15,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: IBE(365.15,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CORRECTIVE ACTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   DSIV requests access to file 365.15 IIV STATUS TABLE to
 display the entire eIV error message for the Insurance Capture Buffer (ICB) 
 application. This file is only read when there is an error condition.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
 SUBSCRIBING DETAILS:   Amendment - Added 1/12/23, Fileman Read to File 365.15,
 Field .02 effective with DSIV*2.2*15 
  DATE ACTIVATED: JAN 12, 2023

NUMBER: 4507                            IA #: 4507
  FILE NUMBER: 1                        GLOBAL ROOT: DIC(
  DATE CREATED: SEP 24, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4507                        ID: DIC(
 GENERAL DESCRIPTION:   This IA documents that the CP Conversion file (#703.9)
 has a multiple field, MEDICINE FILE PARAMETERS (#703.91).  The MEDICINE FILE
 PARAMETERS field (#.01) points to the FILE file (#1).  This multiple field is
 used to store the pointer to the Medicine files so CP can store parameters for 
 each Medicine files used for the medicine report conversion.  The CP 
 Conversion file (#703.9) will be added with patch MD*1*5.  The files that will
 be used belong to the CP namespace.  CP will screen for CP namespace files and
 populate this multiple.  LAYGO will not be allowed.  The following are files
 that will be used:                                      691   ECHO             
                                               691.1 CARDIAC CATHETERIZATION    
                                      691.5 ELECTROCARDIOGRAM (EKG)             
                               691.6 HOLTER                                     
                        691.7 EXERCISE TOLERANCE TEST                           
                691.8 ELECTROPHYSIOLOGY (EP)                                    
         694   HEMATOLOGY                                                      
 694.5 CARDIAC SURGERY RISK ASSESSMENT                                      698 
  GENERATOR IMPLANT                                                   698.1 V
 LEAD IMPLANT                                                   698.2 A LEAD
 IMPLANT                                                     698.3 PACEMAKER
 SURVEILLANCE                                            699  
 ENDOSCOPY/CONSULT                                                 699.5
 GENERALIZED PROCEDURE/CONSULT                                       700  
 PULMONARY FUNCTION TESTS                                            701  
 RHEUMATOLOGY           
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FILE
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Hines

NUMBER: 4508                            IA #: 4508
  DATE CREATED: JAN 31, 2005
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: TIUSRVPT                     NAME: DBIA4508
  ID: TIUSRVPT
 GENERAL DESCRIPTION:   Set Methods/Administrative Closure for TIU documents
 (#8925).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ADMNCLOS(TIUY,TIUDA,MODE,PERSON)
 COMPONENT DESCRIPTION:   Post administrative closure on documents. The
 post-signature code is added to the Administrative Closure of TIU documents so
 that it will be executed upon closure of the document(s).  
  
  
VARIABLES: TIUY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is the return parameter, which is passed by
 reference.  
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the document internal entry number.  
VARIABLES: MODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the administrative closure mode. The
 following values for this variable can be passed in and the corresponding term
 appended: "E"-the "Electronically Filed" term is appended without the
 disclaimer; "S"-the "Electronically Filed" term is appended with the
 disclaimer; "M"-the "Administrative Closure" term is appended.  
  
VARIABLES: PERSON                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number of the person who
 will be posting the administrative closure.  
COMPONENT/ENTRY POINT: SETTEXT(TIUY,TIUDA,TIUX,SUPPRESS)
 COMPONENT DESCRIPTION:   Save Document Text using Buffered I/O. Allows
 documents of indefinite size to be filed, without risk of an allocate error in
 M.  
VARIABLES: TIUY                         TYPE: Both
 VARIABLES DESCRIPTION:   
  If successful returns: 
     <IEN in TIU DOCUMENT FILE>^<LAST_PAGE_RECEIVED>^<TOTAL_PAGES_EXPECTED> 
   
  If unsuccessful returns: 
     0^0^0^Explanatory text 
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   TIUDA = Entry IEN in TIU DOCUMENT file 8925 
VARIABLES: TIUX                         TYPE: Input
 VARIABLES DESCRIPTION:   
  This is the array in which the body of the TIU Document is being passed, 
  as: 
   
                  TIUX("HDR")=<# of Current Page>^<Total # of Pages> 
                  TIUX("TEXT",1,0)=<Line 1 of document body> 
                  TIUX("TEXT",2,0)=<Line 2 of document body> 
                  TIUX("TEXT",3,0)=<Line 3 of document body> 
                  etc.  
VARIABLES: SUPPRESS                     TYPE: Input
 VARIABLES DESCRIPTION:   
  Optional parameter.  Default is 0 (no).  
   
  Boolean flag that indicates whether to commit the data (as in the Save 
  w/o signature action in CPRS), or to simply save it in the EDIT BUFFER 
  for the document (as in the auto-save function).  
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Hines
 SUBSCRIBING DETAILS:   To administratively close the documents created by
 Clinical Procedures for the Medicine Report Conversion and high volume
 procedures.  
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
  DATE ACTIVATED: JAN 25, 2007

NUMBER: 4509                            IA #: 4509
  DATE CREATED: SEP 23, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGRPDB                       NAME: DBIA4509
  ID: DGRPDB
 GENERAL DESCRIPTION:   Insurance display.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: REGISTRATION
KEYWORDS: INSURANCE
COMPONENT/ENTRY POINT: INS
 COMPONENT DESCRIPTION:   This tag is called to display standard, formatted
 insurance data. The insurance data is retrieved through INSUR^IBBAPI
 (DBIA4419).  The variable DFN must be defined to the current patient.  Data is
 retrieved from the BILLING PATIENT File, #354.  New API DISP^DGIBDSP is called
 from INS^DGRPDB and this new API is intended as a replacement for retired IB
 API, DBIA10146.  The new API does not access the INSURANCE BUFFER File,
 #355.33.  
  
SUBSCRIBING PACKAGE: FEE BASIS          ISC: Albany

NUMBER: 4510                            IA #: 4510
  FILE NUMBER: 66                       GLOBAL ROOT: LAB(66,
  DATE CREATED: SEP 23, 2004            CUSTODIAL PACKAGE: LAB SERVICE
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4510                        ID: LAB(66,
GLOBAL REFERENCE: LAB(66,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   NAME 
FIELD NUMBER: .02                       FIELD NAME: ABBREVIATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   The DSS EXTRACTS package is granted permission from the
 Laboratory package to read from the BLOOD PRODUCT file (#66) for purposes of
 storing the #.01 field, NAME, and field #.02, ABBREVIATION, in the DSS extract
 file, #727.829.  No updates are performed on file #66.  
  
 GENERAL DESCRIPTION:   READ BLOOD PRODUCT.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BLOOD PRODUCT
KEYWORDS: ABBREVIATION
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  ISC: Albany
 SUBSCRIBING DETAILS:   Read BLOOD PRODUCT File, #66, for component name, #.01,
 and abbreviation, #.02.  

NUMBER: 4511                            IA #: 4511
  DATE CREATED: JAN 26, 2006            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSERP
  NAME: XUSERP                          ID: XUSERP
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XUSERP
KEYWORDS: DEQUE
COMPONENT/ENTRY POINT: DEQUE
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN

NUMBER: 4512                            IA #: 4512
  DATE CREATED: JAN 26, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: VAFHAPV1                     NAME: VAFHAPV1
  ID: VAFHAPV1                          STATUS: Expired
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: JAN 2007
KEYWORDS: VAFHAPV1
COMPONENT/ENTRY POINT: EN
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN

NUMBER: 4513                            IA #: 4513
  DATE CREATED: JAN 27, 2006            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: YTQAPI5
  NAME: DBIA4513                        ID: YTQAPI5
 GENERAL DESCRIPTION:   This API is called to return data associated with the
 administration of all a patient's Mental Health interviews, surveys and tests
 (instruments).  The input is an array that includes the patients DFN and a
 completion indicator ("Y" for the completed administrations or "N" for the
 non-completed administrations).  Output is returned in an array that includes
 the administration number, instrument name, date the instrument was given,
 date the instrument was saved, who ordered the instrument, who administered
 the instrument, was the administration signed, number of questions answered by
 the patient, did the user have the specified key to view the instrument's
 report, is the instrument legacy (contained in the MH INSTRUMENT file (#601)),
 the instrument IEN from the MH TESTS AND SURVEYS file (#601.71), the
 instrument IEN from the MH INSTRUMENT file (#601), is the instrument
 copyrighted and the IEN of the HOPSITAL LOCATION file (#44).  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ADMINS(YSDATA,YS)
 COMPONENT DESCRIPTION:   Use D ADMINS^YTQAPI5(.YSDATA,.YS) to call the api.  A
 successful call of the api will return YSDATA(1)=[DATA] and YSDATA(2)="# of
 administrations returned" followed by the data.  
                 
 If an error occurs during processing of the input array the api will return 
 YSDATA(1)="[ERROR]" and YSDATA(2)="error message".  
  
VARIABLES: YS                           TYPE: Input
 VARIABLES DESCRIPTION:   YS("DFN") = Patient IEN of the PATIENT file (#2) 
 YS("COMPLETE") = If "Y" returns all completed instrument administrations for 
                  the selected patient. If "N" returns all incomplete
 instrument 
                  administrations for the selected patient.  
   Example 
   -------
   YS("DFN")=28 
   YS("COMPLETE")="Y" 
  
VARIABLES: YSDATA                       TYPE: Output
 VARIABLES DESCRIPTION:   OUTPUT = ADMINISTRATION NUMBER field (#.01) of the MH
 ADMINISTRATIONS file 
          (#601.84)^INSTRUMENT NAME field (#2) of the MH ADMINISTRATIONS file 
          (#601.84)^ DATE GIVEN field (#3) of the MH ADMINISTRATIONS file 
          (#601.84)^DATE SAVED field (#4) of the MH ADMINISTRATIONS file 
          (#601.84)^ORDERED BY field (#5) of the MH ADMINISTRATIONS file 
          (#601.84)^ADMINISTERED BY field (#6) of the MH ADMINISTRATIONS file 
          (#601.84)^SIGNED field (#7) of the MH ADMINISTRATIONS file (#601.84) 
          ^NUMBER OF QUESTIONS ANSWERED field (#9) of the MH ADMINISTRATIONS 
          file (#601.84)^R PRIVILEGE field (#9) of the MH TESTS AND SURVEYS
 file 
          (#601.71) or EXEMPT TEST field (#21) of MH INSTRUMENT file (#601)^IS 
          LEGACY field (#9) of the MH TESTS AND SURVEYS file (#601.71)^ 
          INSTRUMENT IEN From the MH TESTS AND SURVEYS file (#601.71)^ 
          INSTRUMENT IEN From the MH INSTRUMENT file (#601)^REQUIRES LICENSE 
          field (#11) of the MH TESTS AND SURVEYS file (#601.71) or LICENSE 
          STATUS field (#35) of the MH INSTRUMENT file (#601)^IEN OF HOPSITAL 
          LOCATION file (#44) 
   
   Example of a patient with input variable YS("COMPLETE")="Y" 
   -----------------------------------------------------------
   YSDATA(1)="[DATA]" 
   YSDATA(2)="20 administrations returned" 
   YSDATA(3)="91^AUDC^3060126.095539^3060126.105625^232^232^N^3^^Y^5^208^N^78" 
   YSDATA(4)="88^PTSD4Q^3060125.15163^3060125.161933^232^232^N^4^^N^56^^N^48" 
  
 YSDATA(5)="66^DOM80^3060117.134325^3060117.144433^232^232^N^4^^Y^19^229^N^78" 
  
 YSDATA(6)="65^DOM80^3060117.125948^3060117.140054^232^232^N^4^^Y^19^229^N^78" 
  
 YSDATA(7)="64^DOM80^3060117.124934^3060117.135559^232^232^N^4^^Y^19^229^N^78" 
   YSDATA(8)="^DOM80^3060117^3060117^232^232^^^Y^Y^^229^N^" 
   YSDATA(9)="59^PTSD4Q^3060113.144201^3060113.154602^232^232^N^4^^N^56^^N^78" 
   YSDATA(10)="57^PTSD4Q^3060113.142601^3060113.153132^232^232^N^4^^N^56^^N^78" 
   YSDATA(11)="51^PTSD4Q^3060111.143238^3060111.155526^232^232^N^4^^N^56^^N^29" 
  
 YSDATA(12)="101268^CAGE^3051025.140555^3051025.160642^6620^6620^N^4^^Y^17^226 
               ^N^2" 
   YSDATA(13)="101267^CAGE^3051025.14002^3051025.160041^6491^6491^N^4^^Y^17^226 
               ^N^2" 
   YSDATA(14)="101144^BDI2^3050906.113933^3050906.124137^232^232^N^21^^Y^11^245 
               ^Y^29" 
   YSDATA(15)="101118^CAGE^3050902.110511^3050902.13054^6491^6491^N^4^^Y^17^226 
               ^N^2" 
   YSDATA(16)="101035^AUDIT^3050714.132436^3050714.160933^232^232^N^10^^Y^7^227 
               ^Y^29" 
   YSDATA(17)="101029^BDI2^3050714.110644^3050714.121118^232^232^N^21^^Y^11^245 
               ^Y^29" 
   YSDATA(18)="101028^AUDIT^3050714.110035^3050714.120554^232^232^N^10^^Y^7^227 
               ^Y^29" 
   YSDATA(19)="101027^AUDC^3050714.105908^3050714.120025^232^232^N^3^^Y^5^208^N 
               ^29" 
   YSDATA(20)="101026^AUDC^3050714.105805^3050714.115853^232^232^N^3^^Y^5^208^N 
               ^29" 
   YSDATA(21)="100957^AUDC^3050614.125945^3050614.140836^232^232^N^3^^Y^5^208^N 
               ^7" 
   YSDATA(22)="100958^ZDIT-2005^3050614.125945^3050614.140843^232^232^N^12^^N^ 
               100087^^N^7" 
                             
   Example of a patient with input variable YS("COMPLETE")="N" 
   -----------------------------------------------------------
   YSDATA(1)="[DATA]" 
   YSDATA(2)="2 administrations returned" 
   YSDATA(3)="^MMPI2^2940809^^176^^^500^^Y^^202^N^" 
   YSDATA(4)="^MMPI^2930219^2930219^176^^^0^^Y^^60^Y^" 
  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 9/19/23, to use the ADMINS^YTQAPI5 call for
 retrieving completed administrations by patient. 
  DATE ACTIVATED: SEP 19, 2023

NUMBER: 4514                            IA #: 4514
  DATE CREATED: JAN 31, 2006            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: YTQAPI8
  NAME: DBIA4514                        ID: YTQAPI8
 GENERAL DESCRIPTION:   This API is called to return the Mental Health scales,
 raw scores and transformed scores associated with a specified entry from the
 MH ADMINISTRATIONS file (#601.84) and the associated entry from the MH TESTS 
 AND SURVEYS file (#601.71) that was administered to the patient.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETSCORE(YSDATA,YS)
 COMPONENT DESCRIPTION:   Use D GETSCORE^YTQAPI8(.YSDATA,.YS) to call the api. 
 A successful call of the api will return a temporary global array
 (^TMP($J,"YSCOR",1)=[DATA]) followed by data that includes the Mental Health
 scale name(s), raw score(s) and transformed score(s).  
  
 If an error occurs during processing of the input data the api will return a 
 temporary global array (^TMP($J,"YSCOR",1)=[ERROR] followed by an error
 message (^TMP($J,"YSCOR",2)="Error message").  
  
VARIABLES: YS                           TYPE: Input
 VARIABLES DESCRIPTION:   YS("AD") = Internal Entry Number of the MH
 ADMINISTRATIONS file (#601.84) 
   Example 
   -------
   S YS("AD")=94 
  
VARIABLES: YSDATA                       TYPE: Output
 VARIABLES DESCRIPTION:   OUTPUT= SCALE NAME field (#3) of the MH SCALES file
 (#601.87)=the calculated 
         raw score^the calculated transformed score 
  
   Example 
   -------
   This example shows the scale names, raw scores and transformed scores for 
   the SCL9R (Symptom Checklist-90-Revised) instrument.  
   ^TMP(543644718,"YSCOR",1)=[DATA] 
                          2)=SOM;Somatization=2.83^72 
                          3)=O-C;Obsessive-Compulsive=2.90^65 
                          4)=I-S;Interpersonal-Sensitivity=2.78^64 
                          5)=DEP;Depression=3.08^65 
                          6)=ANX;Anxiety=2.80^67 
                          7)=HOS;Hostility=2.83^66 
                          8)=PHOB;Phobic Anxiety=2.71^71 
                          9)=PAR;Paranoid Ideation=3.00^68 
                         10)=PSY;Psychoticism=3.10^80 
                         11)=ADD;Additional Items=2.57^ 
                         12)=GSI;Global Severity Index=2.88^76 
                         13)=PSDI;Positive Symptom Distress Index=2.88^63 
                         14)=PST;Positive Symptom Total=90^80 
   This example shows the scale name and raw score for the AUDC (Alcohol 
   Use Disorders Identification Test Condensed) 
   ^TMP(545524790,"YSCOR",1)=[DATA] 
                          2)=Total=6^ 
  
  
  
SUBSCRIBING PACKAGE: HEALTH SUMMARY

NUMBER: 4515                            IA #: 4515
  FILE NUMBER: 53.79                    GLOBAL ROOT: PSB(53.79,
  DATE CREATED: FEB 13, 2006            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4515
  ID: PSB(53.79,
GLOBAL REFERENCE: PSB(53.79,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This includes global reads of "AADT", "AOIP", "B" cross
 references 
FIELD NUMBER: .08                       FIELD NAME: ADMINISTRATION MEDICATION
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: ACTION STATUS
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSB(53.79,DO,.5)
FIELD NUMBER: .01                       FIELD NAME: DISPENSE DRUG
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSB(53.79,D0,.6)
FIELD NUMBER: .01                       FIELD NAME: ADDITIVES
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSB(53.79,D0,.7)
FIELD NUMBER: .01                       FIELD NAME: SOLUTIONS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   CPRS read access to file 53.79.  
  STATUS: Active                        DURATION: Next Version
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4516                            IA #: 4516
  DATE CREATED: NOV 09, 2004            CUSTODIAL PACKAGE: PROBLEM LIST
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMPLPXRM                     NAME: 4516
  ID: GMPLPXRM
 GENERAL DESCRIPTION:   This entry point is called to build the Clinical
 reminders Index for the PROBLEM file, #9000011. There are no required
 variables.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMPLPXRM
KEYWORDS: CLINICAL REMINDERS INDEX
COMPONENT/ENTRY POINT: INDEX
 COMPONENT DESCRIPTION:   This entry point is called to build the Clinical
 Reminders Index for the PROBLEM file.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clinical reminders calls this entry point to build the
 Clinical Reminders Index for the PROBLEM file.  

NUMBER: 4517                            IA #: 4517
  DATE CREATED: FEB 06, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: OR PARAM COORDINATOR MENU
 GENERAL DESCRIPTION:   This DBIA is meant to allow Care Management to place a
 new option under the menu option OR PARAM COORDINATOR MENU.  
  
  STATUS: Active
KEYWORDS: OR PARAM COORDINATOR MENU
COMPONENT/ENTRY POINT: OR PARAM COORDINATOR MENU
 COMPONENT DESCRIPTION:   This is a menu option that will allow the subscribing
 package to place options under.  
  
SUBSCRIBING PACKAGE: CARE MANAGEMENT
 SUBSCRIBING DETAILS:   Care Management needs to add menu option OR CM MENU to
 the OR PARAM COORDINATOR MENU.  
  

NUMBER: 4518                            IA #: 4518
  DATE CREATED: APR 05, 2007            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDAMUTIL
  NAME: DBIA4518                        ID: SDAMUTIL
 GENERAL DESCRIPTION:   This DBIA provides an interface to retrieve the PCE
 CHECK OUT (Field #11) and the CONSULT LINK (Field #33) for a specific RSA
 appointment, which is identified by its appointment ID, from the RSA
 APPOINTMENT LIST File #44.44. This file is currently the authoritative source
 for these appointment related fields for RSA appointments.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RSA
KEYWORDS: SD
KEYWORDS: ALSTDTA
COMPONENT/ENTRY POINT: $$ALSTDTA(SDRSAID)
 COMPONENT DESCRIPTION:   This function will return the CHECK OUT DATE/TIME ^
 CONSULT LINK IEN for a specific RSA Appointment, identified by its ID. If no
 values exist then just the ^ will be returned.  
VARIABLES: SDRSAID                      TYPE: Input
 VARIABLES DESCRIPTION:   The appointment ID that uniquely identifies the RSA
 appointment. - REQUIRED 
VARIABLES: $$ALSTDTA                    TYPE: Output
 VARIABLES DESCRIPTION:   This API returns a two piece delimitted string
 containing the following information, if they exist: 
  
 1: Check Out Date/Time 2: Consult Link IEN 
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  DATE ACTIVATED: SEP 27, 2007

NUMBER: 4519                            IA #: 4519
  DATE CREATED: NOV 17, 2004
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXPXRMI1                     NAME: 4519
  ID: PXPXRMI1
 GENERAL DESCRIPTION:   Clinical Reminders calls these entry points to build
 the Clinical Reminders Index for the V CPT file, #9000010.18, V HEALTH FACTORS
 file, #9000010.23,  V IMMUNIZATION file, #9000010.11, and the V IMM 
 CONTRA/REFUSAL EVENTS file, #9000010.707. There are no required variables.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXPXRMI1
KEYWORDS: CLINICAL REMINDERS INDEX
COMPONENT/ENTRY POINT: VCPT
 COMPONENT DESCRIPTION:   This entry point is called to build the Clinical
 Reminders Index for the V CPT file.  
COMPONENT/ENTRY POINT: VHF
 COMPONENT DESCRIPTION:   This entry point is called to build the Clinical
 Reminders Index for the V HEALTH FACTOR file.  
COMPONENT/ENTRY POINT: VIMM
 COMPONENT DESCRIPTION:   This entry point is called to build the Clinical
 Reminders Index for the V IMMUNIZATION file.  
COMPONENT/ENTRY POINT: VICR
 COMPONENT DESCRIPTION:   This entry point is called to build the Clinical
 Reminders Index for the V IMM CONTRA/REFUSAL EVENTS file.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clinical reminders calls these entry points to build
 the Clinical Reminders Indexs for the V CPT, V IMMUNIZATION and the V HEALTH
 FACTOR files.  
  DATE ACTIVATED: SEP 19, 2016

NUMBER: 4520                            IA #: 4520
  DATE CREATED: NOV 20, 2004
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXPXRMI2
  NAME: BUILD PCE CLINICAL REMINDERS INDEXES
  ID: PXPXRMI2
 GENERAL DESCRIPTION:   Clinical Reminders calls these entry points to build
 the Clinical Reminders Indexes for the V PATIENT ED file, #9000010.16, V POV
 file, #9000010.07, V SKIN TEST file, #9000010.12, V EXAM file, #9000010.13, 
 and the V STANDARD CODES file, #9000010.71. There are no required variables.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXPXRMI2
KEYWORDS: CLINICAL REMINDERS INDEX
KEYWORDS: V PATIENT ED
KEYWORDS: V POV
KEYWORDS: V SKIN TEST
KEYWORDS: V EXAM
KEYWORDS: V STANDARD CODES
COMPONENT/ENTRY POINT: VPED
 COMPONENT DESCRIPTION:   This entry point is called to build the Clinical
 Reminders Index for the V PATIENT ED file.  
  
COMPONENT/ENTRY POINT: VPOV
 COMPONENT DESCRIPTION:   This entry point is called to build the Clinical
 Reminders Index for the V POV file.  
  
COMPONENT/ENTRY POINT: VSK
 COMPONENT DESCRIPTION:   This entry point is called to build the Clinical
 Reminders Index for the V SKIN TEST file.  
  
COMPONENT/ENTRY POINT: VXAM
 COMPONENT DESCRIPTION:   This entry point is called to build the Clinical
 Reminders Index for the V EXAM file.  
  
COMPONENT/ENTRY POINT: VSC
 COMPONENT DESCRIPTION:   This entry point is called to build the Clinical
 Reminders Index for the V STANDARD CODES file.  
  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clinical Reminders calls these entry points to build
 the Clinical Reminders Indexes for the V PATIENT ED, V POV, V SKIN TEST, V
 EXAM, and V STANDARD CODES files.  
  
  DATE ACTIVATED: JUL 12, 2018

NUMBER: 4521                            IA #: 4521
  DATE CREATED: OCT 29, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGPTDDCR                     NAME: 4521
  ID: DGPTDDCR
 GENERAL DESCRIPTION:   This routine and entry point is used for building the
 PXRMINDX( crossreference with data from the PTF file. There are no required 
 variables.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: INDEX
 COMPONENT DESCRIPTION:   This entry point is called to build the Clinical
 Reminders Index for the PTF file.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clinical reminders will call this entry point to build
 the PXRMINDX( entries for the PTF file.  

NUMBER: 4522                            IA #: 4522
  DATE CREATED: NOV 02, 2004            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSOPXRMI                     NAME: 4522
  ID: PSOPXRMI
 GENERAL DESCRIPTION:   This routine and entry point is used for building the
 Clinical Reminders Index for the PRESCRIPTION file, #52. There are no required
 variables.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSOPXRMI
KEYWORDS: CLINICAL REMINDERS INDEX
COMPONENT/ENTRY POINT: PSRX
 COMPONENT DESCRIPTION:   This entry point is called to build the Clinical
 Reminders Index for the PRESCRIPTION file.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clinical reminders calls this entry point to build the
 Clinical Reminders Indes for the PRESCRIPTION file.  

NUMBER: 4523                            IA #: 4523
  DATE CREATED: NOV 12, 2004            CUSTODIAL PACKAGE: MENTAL HEALTH
  CUSTODIAL ISC: Dallas                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: YTPXRM                       NAME: 4523
  ID: YTPXRM
 GENERAL DESCRIPTION:   This routine and entry point is used for building the
 Clinical Reminders Index for the PSYCH INSTRUMENT PATIENT file, #601.2. There
 are no required variables.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: YTPXRM
KEYWORDS: CLINCIAL REMINDERS INDEX
COMPONENT/ENTRY POINT: INDEX
 COMPONENT DESCRIPTION:   This entry point is call to build the Clinical
 Reminders Index for the PSYCH INSTRUMENT PATIENT file.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clinical reminders calls this entry point to build the
 Clinical Reminders Index for the PSYCH INSTRUMENT PATIENT file.  
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
 SUBSCRIBING DETAILS:   ADDED 10/7/2009 

NUMBER: 4524                            IA #: 4524
  DATE CREATED: OCT 14, 2004            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBARXEU5
  NAME: DBIA4524                        ID: IBARXEU5
 GENERAL DESCRIPTION:   The REGAUTO^IBARXEU5 API updates the Billing Patient
 file (#354) with a patient's copay status and exemption reason.  Registration
 queues this API as a background task from routine DGMTCOR.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: REGAUTO
 COMPONENT DESCRIPTION:   This API updates the Billing Patient file (#354).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Patient file (#2) 
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4525                            IA #: 4525
  DATE CREATED: OCT 26, 2004            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: WVLABCHK                     NAME: WVLABCHK
  ID: WVLABCHK
 GENERAL DESCRIPTION:   The Women's Health (WH) package requests that the Lab
 package will notify the WH package whenever SNOMED codes are changed for a
 verified cytology or surgical pathology test.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORGAN/TISSUE
KEYWORDS: SNOMED
COMPONENT/ENTRY POINT: CREATE
 COMPONENT DESCRIPTION:   The Lab package will call this entry point when
 SNOMED codes are changed for a cytology or surgical pathology test after that
 test has been verified.  
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

NUMBER: 4526                            IA #: 4526
  DATE CREATED: OCT 29, 2004            CUSTODIAL PACKAGE: IMAGING
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: MAG4 REMOTE IMPORT              REMOTE PROCEDURE: MAG4 REMOTE IMPORT
 GENERAL DESCRIPTION:   MAG4 REMOTE IMPORT This RPC is used to QUEUE an image
 for storage by the VistA Imaging Import API. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   The RPC listed in this IA will be added to the OR CPRS
 GUI CHART option beginning at v25 of the CPRS GUI.  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
 SUBSCRIBING DETAILS:   ADDED JUNE 2009 
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

NUMBER: 4527                            IA #: 4527
  DATE CREATED: OCT 26, 2004            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXRMOBJ                      NAME: 4527
  ID: PXRMOBJ
 GENERAL DESCRIPTION:   This DBIA is established to permission to call the
 routine PXRMOBJ to return information to be displayed in TIU OBJECTS.  
  STATUS: Active
KEYWORDS: PXRMOBJ
KEYWORDS: $$STAT
KEYWORDS: $$DEM
COMPONENT/ENTRY POINT: $$STAT(DFN)
 COMPONENT DESCRIPTION:   This component will return the status of the current
 GEC referral.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the patient in question. 
 
VARIABLES: TMP("PXRMOBJSTATUS",$J)      TYPE: Output
 VARIABLES DESCRIPTION:   This is the global array to which the status
 information is set.  
COMPONENT/ENTRY POINT: $$DEM(DFN)
 COMPONENT DESCRIPTION:   This component will return demographic information on
 a certain patient noted by the DFN that is passed into the component.  
VARIABLES: TMP("PXRMOBJ",$J)            TYPE: Output
 VARIABLES DESCRIPTION:   This is the TMP array to which the demographic
 information is set.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN is is equal to the internal entry number of the
 patient file of the patient being queried.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City

NUMBER: 4528                            IA #: 4528
  DATE CREATED: OCT 29, 2004            CUSTODIAL PACKAGE: IMAGING
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: MAG IMPORT CHECK STATUS
  REMOTE PROCEDURE: MAG IMPORT CHECK STATUS
 GENERAL DESCRIPTION:   MAG IMPORT CHECK STATUS This RPC is called to get a
 status record from the IMPORT STATUS file (2006.037) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   The RPC listed in this IA will be added to the OR CPRS
 GUI CHART option beginning at v25 of the CPRS GUI.  

NUMBER: 4529                            IA #: 4529
  DATE CREATED: OCT 26, 2004            CUSTODIAL PACKAGE: IMAGING
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: IMAGING RPC
 GENERAL DESCRIPTION:   MAG IMPORT CLEAR STATUS This RPC call will remove a
 status record in the IMPORT STATUS file (2006.037).  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4530                            IA #: 4530
  DATE CREATED: OCT 29, 2004            CUSTODIAL PACKAGE: IMAGING
  CUSTODIAL ISC: Washington             USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: MAG IMPORT CLEAR STATUS
  REMOTE PROCEDURE: MAG IMPORT CLEAR STATUS
 GENERAL DESCRIPTION:   MAG IMPORT CLEAR STATUS This RPC will be used to clear
 a status record from the IMPORT STATUS file (2006.037).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   The RPC listed in this IA will be added to the OR CPRS
 GUI CHART option beginning at v25 of the CPRS GUI.  

NUMBER: 4531                            IA #: 4531
  DATE CREATED: DEC 14, 2004            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSN50P41                     NAME: DBIA4531
  ID: PSN50P41
 GENERAL DESCRIPTION:   This DBIA is provided by NDF (National Drug File) as an
 API to the DRUG INGREDIENTS file (#50.416). This API is to used in the future
 by all packages accessing this file as all the Pharmacy packages are being 
 re-engineered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$B
 COMPONENT DESCRIPTION:   Returns the file root of the "B" cross-reference. The 
 $$B^PSN50P41 API will accomplish this task.  
                 
  Format: S X=$$B^PSN50P41 
VARIABLES: $$B                          TYPE: Output
 VARIABLES DESCRIPTION:   $$B = "^PS(50.416, "B")" the file root of the "B"
 cross-reference on the DRUG INGREDIENTS file (#50.416) 
COMPONENT/ENTRY POINT: ZERO(PSNIEN,PSNFT,PSNFL,LIST)
 COMPONENT DESCRIPTION:   Format: D ZERO^PSN50P41(PSNIEN,PSNFT,PSNFL,LIST) 
VARIABLES: PSNIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSNIEN = IEN of entry in DRUG INGREDIENTS file
 (#50.416) [optional] 
VARIABLES: PSNFT                        TYPE: Input
 VARIABLES DESCRIPTION:   PSNFT = the NAME field (#.01) of the DRUG INGREDIENTS
 file (#50.416) (a value of  "??" may be used) [optional] 
VARIABLES: PSNFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSNFL = Inactive date: A null value will return all
 entries (entry of a FileMan format date (ex: 3030917) will return active
 entries after this date) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSNIEN,.01)=NAME(50.416,.01) 
  
 ^TMP($J,LIST,PSNIEN,2)=PRIMARY INGREDIENT(50.416,2)^NAME(50.416,.01) (The 
 PRIMARY INGREDIENT field (#2) stores the IEN of the DRUG INGREDIENTS file 
 (#50.416) that point to other entry in this file) 
  
 ^TMP($J,LIST,PSNIEN,3)=INACTIVATION DATE(50.416,3)^External format (ex: SEP
 12,1999) 
  
 ^TMP($J,LIST,"B",NAME,PSNIEN)= "" 
COMPONENT/ENTRY POINT: NAME(PSNFT,LIST)
 COMPONENT DESCRIPTION:   Returns fields in the zero node in the DRUG
 INGREDIENTS file (#50.416) in the array defined by the calling application.
 The "P  cross-reference in the format of ^PS(50.416,"P
 ,NAME(50.416,.01),IEN(50.416)) will be used.  
VARIABLES: PSNFT                        TYPE: Input
 VARIABLES DESCRIPTION:   NAME field (#.01) of the DRUG INGREDIENTS file
 (#50.416) (a value of "??" may be used) [required] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0) = Total entries returned or -1^NO
 DATA FOUND 
  
 ^TMP($J,LIST,PSNIEN,.01) = NAME (50.416,.01) 
  
 ^TMP($J,LIST,PSNIEN,2) = PRIMARY INGREDIENT (50.416,2)^NAME (50.416,.01) (The
 PRIMARY INGREDIENT field (#2) stores the IEN of the DRUG INGREDIENTS file
 (#50.416) that point to other entry in this file) 
  
 ^TMP($J,LIST,"P",NAME,PSNIEN) = "" 
  
 Where: 
  
 PSNIEN is IEN of entry in the DRUG INGREDIENTS file (#50.416) 

NUMBER: 4532                            IA #: 4532
  DATE CREATED: MAR 22, 2006            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSNPI
  NAME: NPI UTILITIES                   ID: XUSNPI
 GENERAL DESCRIPTION:   An API to facilitate retrieval of the National Provider
 Identifier (NPI) information and related utilities.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NPI
COMPONENT/ENTRY POINT: $$NPI(XUSQI,XUSIEN,XUSDATE)
 COMPONENT DESCRIPTION:   Extrinsic function for retrieving NPI.  
VARIABLES: XUSQI                        TYPE: Input
 VARIABLES DESCRIPTION:   The Qualified Identifier for the NPI.  Required.  No
 default.  
VARIABLES: XUSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number.  Required.  No default.  
VARIABLES: XUSDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   A date of interest.  Not required.  Default to
 'Today'.  
VARIABLES: $$NPI                        TYPE: Output
 VARIABLES DESCRIPTION:   If NPI exists returns string: 
  'NPI^EffectiveDate^Status'.  
  
 If NPI does not exist returns string: 
  '0'. 
  
 Else returns string: 
  '-1^ErrorMessage'. 
COMPONENT/ENTRY POINT: $$QI(XUSNPI)
 COMPONENT DESCRIPTION:   Extrinsic function for retrieving provider entities.  
VARIABLES: XUSNPI                       TYPE: Input
 VARIABLES DESCRIPTION:   The NPI.  Required.  No default.  
VARIABLES: $$QI                         TYPE: Output
 VARIABLES DESCRIPTION:   If NPI exists returns string: 
  'QualifiedIdentifier^IEN^EffectiveDate^Status'.  
                             
 Else returns string: 
  '0'. 
COMPONENT/ENTRY POINT: $$CHKDGT(XUSNPI)
 COMPONENT DESCRIPTION:   Extrinsic function for testing NPI check digit.  
VARIABLES: XUSNPI                       TYPE: Input
 VARIABLES DESCRIPTION:   The National Provider Identifier.  Required.  No
 default.  
VARIABLES: $$CHKDGT                     TYPE: Output
 VARIABLES DESCRIPTION:   If check digit is valid: 
  '1'.  
  
 Else: 
  '0'.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: FEE BASIS
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   added AR 9/19/2007 
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   LR added 9/19/2007 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   added 10/11/2007 
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Added 6/17/20 for an HL7 adaptor to interface between
 Cerner EHRM and VistA for deployment to Spokane.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Added 6/17/20 for an HL7 adaptor to interface between
 Cerner EHRM and VistA for deployment to Spokane.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Using $$NPI to support displaying NPI# for providers in
 the user display for PPMS/PIE/CPRS/MVI project, Community Provider Update
 users. Effective with CPRS (OR*3.0*533).  
  DATE ACTIVATED: MAR 14, 2018

NUMBER: 4533                            IA #: 4533
  DATE CREATED: DEC 14, 2004
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSS50                        NAME: DBIA4533
  ID: PSS50
 GENERAL DESCRIPTION:   This DBIA is provided by PDM (Pharmacy Data Management)
 as an API to the DRUG file (#50). This API is to used in the future by all
 packages accessing this file as all the Pharmacy packages are being
 re-engineered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DATA(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   Format: D
 DATA^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFT = GENERIC NAME field (#.01) of the DRUG file
 (#50) (a value of "??" may be used) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date: A null value will return all
 entries (entry of a FileMan format date (ex: 3030917) will return active
 entries after this date) [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSPK = Returns only those entries containing at
 least one of the codes in the APPLICATION PACKAGES' USE (#63) field of the
 DRUG file (#50) (ex: PSSPK = "IU" will return all entries for either IV, Unit
 Dose, or both IV and Unit Dose) [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   PSSRTOI = If a "1" is passed in, then only those
 entries matched to a Pharmacy Orderable Item will be returned [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  
 ^TMP($J,LIST,PSSIEN,2)=VA CLASSIFICATION(50,2) 
  
 ^TMP($J,LIST,PSSIEN,2.1)=PHARMACY ORDERABLE ITEM(50,2.1)^NAME (50.7,.01)^IEN
 of the Dosage Form file (#50.606)^NAME(50.606,.01) 
  
 ^TMP($J,LIST,PSSIEN,3)=DEA SPECIAL HDLG(50,3) 
  
 ^TMP($J,LIST,PSSIEN,4)=MAXIMUM DOSE PER DAY(50,4) 
  
 ^TMP($J,LIST,PSSIEN,5)=STANDARD SIG(50,5) 
  
 ^TMP($J,LIST,PSSIEN,6)=FSN(50,6) 
  
 ^TMP($J,LIST,PSSIEN,8)=WARNING LABEL(50,8) 
  
 ^TMP($J,LIST,PSSIEN,12)=ORDER UNIT(50,12)^ABBREVIATION
 (51.5,.01)^EXPANSION(51.5,.02) 
  
 ^TMP($J,LIST,PSSIEN,13)=PRICE PER ORDER UNIT(50,13) 
  
 ^TMP($J,LIST,PSSIEN,14.5)=DISPENSE UNIT(50,14.5) 
  
 ^TMP($J,LIST,PSSIEN,15)=DISPENSE UNITS PER ORDER UNIT(50,15) 
  
 ^TMP($J,LIST,PSSIEN,16)=PRICE PER DISPENSE UNIT(50,16) 
  
 ^TMP($J,LIST,PSSIEN,20)=NATIONAL DRUG FILE ENTRY (50,20)^NAME(50.6,.01) 
  
 ^TMP($J,LIST,PSSIEN,21)=VA PRODUCT NAME(50,21) 
  
 ^TMP($J,LIST,PSSIEN,22)=PSNDF VA PRODUCT NAME ENTRY(50,22)^NAME(50.68,.01) 
  
 ^TMP($J,LIST,PSSIEN,25)=NATIONAL DRUG 
 CLASS(50,25)^CODE(50.605,.01)^CLASSIFICATION (50.605,1) 
  
 ^TMP($J,LIST,PSSIEN,27)=CMOP ID(50,27) 
  
 ^TMP($J,LIST,PSSIEN,31)=NDC(50,31) 
  
 ^TMP($J,LIST,PSSIEN,40)=ACTION PROFILE MESSAGE(50,40) 
  
 ^TMP($J,LIST,PSSIEN,51)=LOCAL NON-FORMULARY(50,51)^External format for the set
 of codes 
  
 ^TMP($J,LIST,PSSIEN,52)=VISN NON-FORMULARY(50,52)^External format for the set
 of codes 
  
 ^TMP($J,LIST,PSSIEN,63)=APPLICATION PACKAGES' USE(50,63) 
  
 ^TMP($J,LIST,PSSIEN,64)=PRIMARY DRUG(50,64)^NAME(50.3,.01) 
  
 ^TMP($J,LIST,PSSIEN,100)=INACTIVE DATE (50,100)^External format (ex: SEP
 12,1999) 
  
 ^TMP($J,LIST,PSSIEN,101)=MESSAGE(50,101) 
  
 ^TMP($J,LIST,PSSIEN,102)=RESTRICTION(50,102) 
  
 ^TMP($J,LIST,PSSIEN,301)=AR/WS AMIS CATEGORY(50,301)^External format for the
 set of codes 
  
 ^TMP($J,LIST,PSSIEN,302)=AR/WS AMIS CONVERSION NUMBER(50,302) 
  
 ^TMP($J,LIST,PSSIEN,400)=SERVICE CODE(50,400) 
  
 Note: For the SERVICE CODE field (#400)entry returned, it will be 
       retrieved in one of three ways: 
    1) If the DRUG entry from the DRUG file (#50) is matched to the 
       VA PRODUCT file (#50.68), and there is data in the SERVICE CODE 
       field (#2000) of the VA PRODUCT file (#50.68) of that match, the 
       SERVICE CODE field will be retrieved from the SERVICE CODE field 
       (#2000) of the VA PRODUCT file (#50.68).  
    2) If no SERVICE CODE data is found in the SERVICE CODE field (#2000) 
       of the VA PRODUCT file (#50.68), and there is data in the SERVICE 
       CODE field (#400) of the DRUG file (#50), the SERVICE CODE field 
       will be retrieved from the SERVICE CODE field (#400) of the DRUG 
       file (#50).  
    3) If no SERVICE CODE data is found in the SERVICE CODE field (#2000) 
       of the VA PRODUCT file (#50.68), and in the SERVICE CODE field 
       (#400) of the DRUG file (#50), the value 600000 will be returned as 
       the SERVICE CODE.  
  
  
 ^TMP($J,LIST,PSSIEN,"FRM",0)= Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST,PSSIEN,"FRM",PSS(1),2)=FORMULARY ALTERNATIVE (50.065,.01)^GENERIC
 NAME (50,.01) 
  
 ^TMP($J,LIST,PSSIEN,"OLD",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST,PSSIEN,"OLD",PSS(1),.01)=OLD NAMES(50.01,.01) 
  
 ^TMP($J,LIST,PSSIEN,"OLD",PSS(1),.02)=DATE CHANGED (50.01,.02) ^External
 format (ex: SEP 12,1999) 
  
 ^TMP($J,LIST,PSSIEN,"SYN",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),.01)=SYNONYM (50.1,.01) 
  
 ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),1)=INTENDED USE(50.1,1)^External format for
 the set of codes 
  
 ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),2)=NDC CODE(50.1,2) 
  
 ^TMP($J,LIST,PSSIEN,"SYN",PSS(1),403)=DISPENSE UNITS PER ORDER UNIT(50.1,403) 
  
 ^TMP($J,LIST,"B",GENERIC NAME,PSSIEN)= "" 
  
 Where: PSS(1) is the IEN of the multiple it referenced 
COMPONENT/ENTRY POINT: LAB(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   D LAB^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFT = GENERIC NAME field (#.01) of the DRUG file
 (#50) (a value of "??" may be used) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date: A null value will return all
 entries (entry of a FileMan format date (ex: 3030917) will return active
 entries after this date) [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSPK = Returns only those entries containing at
 least one of the codes in the APPLICATION PACKAGES' USE (#63) field of the
 DRUG file (#50) (ex: PSSPK = "IU" will return all entries for either IV, Unit
 Dose, or both IV and Unit Dose) [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   PSSRTOI = If a "1" is passed in, then only those
 entries matched to a Pharmacy Orderable Item will be returned [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returned or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  
 ^TMP($J,LIST,PSSIEN,17.2)=LAB TEST MONITOR 50,17.2)^NAME 60,.01) 
  
 ^TMP($J,LIST,PSSIEN,17.3)=MONITOR MAX DAYS(50,17.3) 
  
 ^TMP($J,LIST,PSSIEN,17.4)=SPECIMEN TYPE(50,17.4)^NAME(61,.01) 
  
 ^TMP($J,LIST,PSSIEN,17.5)=MONITOR ROUTINE(50,17.5) 
  
 ^TMP($J,LIST,PSSIEN,17.6)=LAB MONITOR MARK(50,17.6)^External format for the
 set of codes 
  
 ^TMP($J,LIST,"B",GENERIC NAME,PSSIEN)="" 
COMPONENT/ENTRY POINT: CLOZ(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   Format: D
 CLOZ^PSS50(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSIEN = IEN from the DRUG file (#50) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFT = GENERIC NAME field (#.01) of the DRUG file
 (#50) (a value of "??" may be used) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date: A null value will return all
 entries (entry of a FileMan format date (ex: 3030917) will return active
 entries after this date) [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSPK = Returns only those entries containing at
 least one of the codes in the APPLICATION PACKAGES' USE (#63) field of the
 DRUG file (#50) (ex: PSSPK = "IU" will return all entries for either IV, Unit
 Dose, or both IV and Unit Dose) [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   PSSRTOI = If a "1" is passed in, then only those
 entries matched to a Pharmacy Orderable Item will be returned [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returned or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  
 ^TMP($J,LIST,PSSIEN,"CLOZ",0)=Total entries returned for this sub-file or 
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST,PSSIEN,"CLOZ",PSS(1),.01)=LAB TEST 
 MONITOR(50.02,.01)^NAME(60,.01) 
  
 ^TMP($J,LIST,PSSIEN,"CLOZ",PSS(1),1)=MONITOR MAX DAYS(50.02,1) 
  
 ^TMP($J,LIST,PSSIEN,"CLOZ",PSS(1),2)=SPECIMEN TYPE(50.02,2)^NAME(61,.01) 
  
 ^TMP($J,LIST,PSSIEN,"CLOZ",PSS(1),3)=TYPE OF TEST(50.02,3)^External format for
 the set of codes 
  
 ^TMP($J,LIST,"B",GENERIC NAME,PSSIEN)="" 
  
 Where: PSS(1) is the IEN of entry in the CLOZAPINE LAB TEST multiple 
COMPONENT/ENTRY POINT: NDC(PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   Format: D NDC^PSS50(PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSVAL = NDC field (#31) of the DRUG file (#50) (ex:
 "053905099101" (without dashes) as being used in the "NDC" cross-reference)
 [required] 
  
 Note: Use quotes around the PSSVAL value, or use quotes around the value if
 setting a variable to this value to be used as the parameter, to prevent
 leading zeros from being truncated.  
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date: A null value will return all
 entries (entry of a FileMan format date (ex: 3030917) will return active
 entries after this date) [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSPK = Returns only those entries containing at
 least one of the codes in the APPLICATION PACKAGES' USE (#63) field of the
 DRUG file (#50) (ex: PSSPK = "IU" will return all entries for either IV, Unit
 Dose, or both IV and Unit Dose) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returned or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  
 ^TMP($J,LIST,PSSIEN,"NDC",GENERIC NAME,PSSIEN)="" 
  
 Where: PSSIEN is IEN of entry in the DRUG file (#50) 
  
 The "NDC" cross-reference in the format of ^PSDRUG("NDC",NDC(50,31), IEN(50))
 will be used for the lookup.  
COMPONENT/ENTRY POINT: ASP(PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   Format: D ASP^PSS50(PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSVAL = PHARMACY ORDERABLE ITEM field (#2.1) of the
 DRUG file (#50) [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date: A null value will return all
 entries (entry of a FileMan format date (ex: 3030917) will return active
 entries after this date) [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSPK = Returns only those entries containing at
 least one of the codes in the APPLICATION PACKAGES' USE (#63) field of the
 DRUG file (#50) (ex: PSSPK = "IU" will return all entries for either IV, Unit
 Dose, or both IV and Unit Dose) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returned or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  
 ^TMP($J,LIST,"ASP",GENERIC NAME,PSSIEN)="" 
  
 Where: PSSIEN is IEN of entry in the DRUG file(#50) 
  
 The "ASP" cross-reference in the format of ^PSDRUG("ASP",PHARMACY ORDERABLE
 ITEM(50,2.1),IEN(50)) will be used for the lookup.  
COMPONENT/ENTRY POINT: AND(PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   Format: D AND^PSS50(PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSVAL = NATIONAL DRUG FILE ENTRY field (#20) of the
 DRUG file (#50) [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date: A null value will return all
 entries (entry of a FileMan format date (ex: 3030917) will return active
 entries after this date) [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSPK = Returns only those entries containing at
 least one of the codes in the APPLICATION PACKAGES' USE (#63) field of the
 DRUG file (#50) (ex: PSSPK = "IU" will return all entries for either IV, Unit
 Dose, or both IV and Unit Dose) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returned or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  
 ^TMP($J,LIST,"AND",GENERIC NAME,PSSIEN)="" 
  
 Where: PSSIEN is IEN of entry in the DRUG file(#50) 
  
 The "AND" cross-reference in the format of ^PSDRUG("AND",NATIONAL DRUG FILE
 ENTRY(50,20),IEN(50)) will be used for the lookup.  
COMPONENT/ENTRY POINT: VAC(PSSVAL,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   Format: D VAC^PSS50(PSSVAL,PSSFL,PSSPK,LIST) 
VARIABLES: PSSVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSVAL = the NATIONAL DRUG CLASS field (#25) of the
 DRUG file (#50) [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date: A null value will return all
 entries (entry of a FileMan format date (ex: 3030917) will return active
 entries after this date) [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSPK = Returns only those entries containing at
 least one of the codes in the APPLICATION PACKAGES' USE (#63) field of the
 DRUG file (#50) (ex: PSSPK = "IU" will return all entries for either IV, Unit
 Dose, or both IV and Unit Dose) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = the array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returned or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  
 ^TMP($J,LIST,"VAC",GENERIC NAME,PSSIEN)="" 
  
 Note: The "VAC" cross-reference in the format of ^PSDRUG("VAC",NATIONAL DRUG
 CLASS(50,25),IEN(50) will be used for the lookup.  
  
 Where: PSSIEN is IEN of entry in the DRUG file(#50) 
COMPONENT/ENTRY POINT: ZERO(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   This API will return information from the DRUG file
 (#50), primarily from the zero node.  
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the DRUG file
 (#50). [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the GENERIC NAME field (#.01) from the DRUG
 file (#50). A value of "??" may be used for a complete list of entries.
 [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   This parameter represents the inactive date, in
 FileMan format.  If no date is passed in, all possible entries will be
 returned. If a date is passed in, only entries without an inactive date and
 entries with an inactive date later than this date will be returned. 
 [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   This parameter represents the APPLICATION PACKAGES'
 USE field (#63) of the DRUG file (#50), and the entries returned will be based
 on this value.  For example, if "IU" is passed in, then the call will return
 only those entries marked for Unit Dose or IV. [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   If a 1 is passed in this parameter, only those
 entries matched to a Pharmacy Orderable Item, will be returned. If a 1 is not
 passed in, all possible entries will be returned.  
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   This will be the name subscript in the return ^TMP
 global. [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)= Total entries returned. If there are
 no entries being returned, then this will be equal to "-1^NO DATA FOUND".  
  
 ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  
 ^TMP($J,LIST,PSSIEN,2)=VA CLASSIFICATION(50,2) 
  
 ^TMP($J,LIST,PSSIEN,3)=DEA, SPECIAL HDLG(50,3) 
  
 ^TMP($J,LIST,PSSIEN,4)=MAXIMUM DOSE PER DAY(50,4) 
  
 ^TMP($J,LIST,PSSIEN,5)=STANDARD SIG(50,5) 
  
 ^TMP($J,LIST,PSSIEN,6)=FSN(50,6) 
  
 ^TMP($J,LIST,PSSIEN,8)=WARNING LABEL(50,8) 
  
 ^TMP($J,LIST,PSSIEN,51)=LOCAL NON-FORMULARY(50,51)^External format for the set
 of codes 
  
 ^TMP($J,LIST,PSSIEN,52)=VISN NON-FORMULARY(50,52)^External format for the set
 of codes 
  
 ^TMP($J,LIST,PSSIEN,101)=MESSAGE(50,101) 
  
 ^TMP($J,LIST,"B",GENERIC NAME,PSSIEN)="" 
COMPONENT/ENTRY POINT: ARWS(PSSIEN,PSSFT,LIST)
 COMPONENT DESCRIPTION:   This API will return information from the DRUG file
 (#50).  
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the DRUG file
 (#50). [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the GENERIC NAME field (#.01) from the DRUG
 file (#50). A value of "??" may be used for a complete list of entries.
 [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   This will be the name subscript in the return ^TMP
 global. [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)= Total entries returned. If there are
 no entries being returned, then this will be equal to "-1^NO DATA FOUND".  
                             
 ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) 
  
 ^TMP($J,LIST,PSSIEN,2)=VA CLASSIFICATION(50,2) 
  
 ^TMP($J,LIST,PSSIEN,3)=DEA, SPECIAL HDLG(50,3) 
  
 ^TMP($J,LIST,PSSIEN,12)=ORDER 
 UNIT(50,12)^ABBREVIATION(51.5,.01)^EXPANSION(51.5,.02) 
  
 ^TMP($J,LIST,PSSIEN,13)=PRICE PER ORDER UNIT(50,13) 
  
 ^TMP($J,LIST,PSSIEN,14.5)=DISPENSE UNIT(50,14.5) 
  
 ^TMP($J,LIST,PSSIEN,15)=DISPENSE UNITS PER ORDER UNIT(50,15) 
  
 ^TMP($J,LIST,PSSIEN,16)=PRICE PER DISPENSE UNIT(50,16) 
  
 ^TMP($J,LIST,PSSIEN,20)=NATIONAL DRUG FILE ENTRY(50,20)^NAME(50.6,.01) 
  
 ^TMP($J,LIST,PSSIEN,21)=VA PRODUCT NAME(50,12) 
  
 ^TMP($J,LIST,PSSIEN,22)=PSNDF VA PRODUCT NAME ENTRY(50,22)^NAME(50.68,.01) 
  
 ^TMP($J,LIST,PSSIEN,23)=PACKAGE SIZE(50,23)^NAME(50.609,.01) 
  
 ^TMP($J,LIST,PSSIEN,25)=NATIONAL DRUG 
 CLASS(50.25)^CODE(50.605,.01)^CLASSIFICATION(50.605,1) 
  
 ^TMP($J,LIST,PSSIEN,31)=NDC(50,31) 
  
 ^TMP($J,LIST,PSSIEN,51)=LOCAL NON-FORMULARY(50,51)^External format for the set
 of codes 
  
 ^TMP($J,LIST,PSSIEN,52)=VISN NON-FORMULARY(50,52)^External format for the set
 of codes 
  
 ^TMP($J,LIST,PSSIEN,301)=AR/WS AMIS CATEGORY(50,301)^External format for the
 set of codes 
  
 ^TMP($J,LIST,PSSIEN,302)=AR/WS AMIS CONVERSION NUMBER(50,302) 
  
 ^TMP($J,LIST,"B",GENERIC NAME,PSSIEN)="" 
COMPONENT/ENTRY POINT: NDF(PSSIEN,PSSFT,PSSFL,PSSPK,PSSRTOI,LIST)
 COMPONENT DESCRIPTION:   This API returns National Drug Information from the
 DRUG file (#50).  
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the DRUG file
 (#50). [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the GENERIC NAME field (#.01) from the DRUG
 file (#50). A value of "??" may be used for a complete list of entries.
 [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   This parameter represents the inactive date, in
 FileMan format.  If no date is passed in, all possible entries will be
 returned. If a date is passed in, only entries without an inactive date and
 entries with an inactive date later than this date will be returned. 
 [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   This parameter represents the APPLICATION PACKAGES'
 USE field (#63) of the DRUG file (#50), and the entries returned will be based
 on this value.  For example, if "IU" is passed in, then the call will return
 only those entries marked for Unit Dose or IV. [optional] 
VARIABLES: PSSRTOI                      TYPE: Input
 VARIABLES DESCRIPTION:   If a 1 is passed in this parameter, only those
 entries matched to a Pharmacy Orderable Item, will be returned. If a 1 is not
 passed in, all possible entries will be returned.  
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   This will be the name subscript in the return ^TMP
 global. [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)= Total entries returned. If there are
 no entries being returned, then this will be equal to "-1^NO DATA FOUND".  
                             
 ^TMP($J,LIST,PSSIEN,.01)=GENERIC NAME(50,.01) ^TMP($J,LIST,PSSIEN,20)=NATIONAL
 DRUG FILE ENTRY(50,20)^NAME (50.6,.01) ^TMP($J,LIST,PSSIEN,21)=VA PRODUCT
 NAME(50,21) ^TMP($J,LIST,PSSIEN,22)=PSNDF VA PRODUCT NAME
 ENTRY(50,22)^NAME(50.68,.01) ^TMP($J,LIST,PSSIEN,23)=PACKAGE
 SIZE(50,23)^NAME(50.609,.01) ^TMP($J,LIST,PSSIEN,24)=PACKAGE
 TYPE(50,24)^NAME(50.608,.01) ^TMP($J,LIST,PSSIEN,25)=NATIONAL DRUG 
 CLASS(50,25)^CODE(50.605,.01)^CLASSIFICATION(50.605,1) 
 ^TMP($J,LIST,PSSIEN,27)=CMOP ID(50,27) ^TMP($J,LIST,PSSIEN,29)=NATIONAL
 FORMULARY INDICATOR (50,29)^External format for the set of codes 
 ^TMP($J,LIST,"B",GENERIC NAME,PSSIEN)="" 

NUMBER: 4534                            IA #: 4534
  FILE NUMBER: 45.84                    GLOBAL ROOT: DGP(45.84,
  DATE CREATED: FEB 13, 2006            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: ACCESS TO PTF CLOSE OUT (#45.84) FILE
  ID: DGP(45.84,
GLOBAL REFERENCE: DGP(45.84,DA,0)
FIELD NUMBER: .01                       FIELD NAME: PTF RECORD
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Dinumed pointer to PTF File (#45).  This file is
 populated when a PTF record has been closed out.  
 GLOBAL DESCRIPTION:   $D(^DGP(45.84,DA)) checks to determine if PTF record has
 been closed out prior to deletion.  
 GENERAL DESCRIPTION:   
  
 Used to check and make sure the PTF record has not been closed out.  
  
 3/26/18-The references to file 45.83 in the Global Reference and Global Root
 fields were changed to 45.84. Integrated Billing was the only subscribing
 package referencing the PTF Release (#45.83) file and ICR #2819 provides IB
 access to fields in the PTF Release file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS          ISC: Albany
 SUBSCRIBING DETAILS:   Fee Basis uses the "AFEE" cross-reference in the PTF
 file to locate a Non-VA PTF record that is created on admission to a Non-VA
 facility.  There are times when the admission is cancelled or entered in error 
 and fee locates the PTF record, assures it is not closed out by checking in
 file 45.84, and deletes the stub record.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  ISC: Albany
SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING
  DATE ACTIVATED: MAR 26, 2018

NUMBER: 4535                            IA #: 4535
  DATE CREATED: FEB 14, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFHLZRD
  NAME: VAFHLZRD                        ID: VAFHLZRD
  STATUS: Active
COMPONENT/ENTRY POINT: EN(DFN,VAFSTR,VAFHLQ,VAFHLFS,VAFARRY)
 COMPONENT DESCRIPTION:   This generic function creates HL7 VA-Specific Rated
 Disabilities (ZRD) segments for a patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the patient (DFN).  
VARIABLES: VAFSTR                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional. String of fields requested, separated by
 commas. If not passed, the API will return all data fields.  
VARIABLES: VAFHLQ                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional. HL7 null variable.  
VARIABLES: VAFHLFS                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional. HL7 field separator.  
VARIABLES: VAFARRY                      TYPE: Both
 VARIABLES DESCRIPTION:   Optional. Closed root of the destination array that
 will hold HL7 ZRD segments. If not defined or an empty string, then
 ^TMP("VAFZRD",$J) will be used.  
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
SUBSCRIBING PACKAGE: SURGERY
 SUBSCRIBING DETAILS:   8-2-13:  SQWM will be including the ZRD segment in
 their outbound HL7 message from VistA to SQWM.  

NUMBER: 4536                            IA #: 4536
  DATE CREATED: FEB 14, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFHLZSP
  NAME: VAFHLZSP                        ID: VAFHLZSP
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$EN(DFN,VAFNUM,VAFAMB)
 COMPONENT DESCRIPTION:   This generic function creates HL7 VA-Specific Service
 Period (ZSP) segment for a patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the patient (DFN).  
VARIABLES: VAFNUM                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) sequential number for SET ID (default=1) 
VARIABLES: VAFAMB                       TYPE: Input
VARIABLES: $$EN                         TYPE: Output
 VARIABLES DESCRIPTION:   The function returns the ZSP segment.  
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   LR ADDED 3/21/11 
  DATE ACTIVATED: JUN 19, 2010

NUMBER: 4537                            IA #: 4537
  DATE CREATED: SEP 21, 2006            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSJ53P1
  NAME: PSJ53P1                         ID: PSJ53P1
 GENERAL DESCRIPTION:   This API shall be provided to return the ORDER NUMBER
 field (#.01), PROVIDER field (#1), MED ROUTE field (#3), SCHEDULE TYPE field
 (#7), START DATE/TIME field (#10), STOP DATE/TIME field (#25), SCHEDULE field
 (#26), STATUS field (#28), ORDERABLE ITEM field (#108), DOSAGE ORDERED field
 (#109) and all the Dispensed Drugs from the DISPENSED DRUG field (#2), for an
 entry from the NON-VERIFIED ORDERS (#53.1) File.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PSJ(PSJIEN,LIST)
 COMPONENT DESCRIPTION:   FORMAT: D PSJ^PSJ53P1(PSJIEN,LIST) 
VARIABLES: PSJIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSJIEN = IEN of NON-VERIFIED ORDERS file (#53.1).
 [REQUIRED] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript name used in ^TMP global [REQUIRED] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)= 1 for successful return of data or
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST,ORDER NUMBER,.01)=ORDER NUMBER (53.1,.01) 
  
 ^TMP($J,LIST,ORDER NUMBER,1)=PROVIDER (53.1,1   P)^NAME (200,.01) 
  
 ^TMP($J,LIST,ORDER NUMBER,3)=MED ROUTE (53.1,3)^NAME (51.2,.01) 
  
 ^TMP($J,LIST,ORDER NUMBER,7)=SCHEDULE TYPE (53.1,7)^ External Format for the
 Set of Codes 
  
 ^TMP($J,LIST,ORDER NUMBER,10)=START DATE/TIME (53.1,10)^ External Format (ex:
 Sep. 12, 1999) 
  
 ^TMP($J,LIST,ORDER NUMBER,25)=STOP DATE/TIME (53.1,25)^ External Format (ex:
 Sep. 12, 1999) 
  
 ^TMP($J,LIST,ORDER NUMBER,26)=SCHEDULE (53.1,26) 
  
 ^TMP($J,LIST,ORDER NUMBER,28)=STATUS (53.1,28)^ External Format for the Set of
 Codes 
  
 ^TMP($J,LIST,ORDER NUMBER,108)=ORDERABLE ITEM (53.1,108)^NAME (50.7, .01) 
  
 ^TMP($J,LIST,ORDER NUMBER,109)=DOSAGE ORDERED (53.1,109) 
  
 ^TMP($J,LIST,ORDER NUMBER,"DDRUG",0)=Number of drugs returned or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,ORDER NUMBER,"DDRUG",Drug IEN,.01)=DISPENSE DRUG 
 (53.11,.01)^GENERIC NAME (50,.01) 
  
 ^TMP($J,LIST,ORDER NUMBER,"DDRUG",Drug IEN,.02)= UNITS PER DOSE (53.11,.02) 
  
 ^TMP($J,LIST,"B",ORDER NUMBER)="" 

NUMBER: 4538                            IA #: 4538
  FILE NUMBER: 350.1                    GLOBAL ROOT: IBE(350.1
  DATE CREATED: FEB 28, 2006            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: AR ACCESS TO FILE 350.1
  ID: IBE(350.1
GLOBAL REFERENCE: IBE(350.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   
  
FIELD NUMBER: .11                       FIELD NAME: BILLING GROUP
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   
  
 GLOBAL DESCRIPTION:   
  
GLOBAL REFERENCE: IBE(350.1,B,
 GLOBAL DESCRIPTION:   Cross reference to lookup entry IEN by NAME.  
 GENERAL DESCRIPTION:   As part of the Vista IB/AR Data Extract to the ARC, AR
 needs to access file 350.1 (IB ACTION TYPE). AR would like direct global
 access to the following: 
  
 Direct global read access is requested for the following fields: 
  
               .01  NAME 
               .11  BILLING GROUP 
  
 Direct global read access for record lookup by name to the following cross
 reference: 
  
               ^IBE(350.1,"B" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   
  
  DATE ACTIVATED: MAR 03, 2010

NUMBER: 4539                            IA #: 4539
  DATE CREATED: FEB 28, 2006            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSAP
  NAME: DBIA4539                        ID: XUSAP
 GENERAL DESCRIPTION:   checks whether user is active and a proxy user 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PROXY USER
COMPONENT/ENTRY POINT: $$USERTYPE(IE,CLASS)
VARIABLES: IE                           TYPE: Input
 VARIABLES DESCRIPTION:   ien of New Person file record 
VARIABLES: CLASS                        TYPE: Input
 VARIABLES DESCRIPTION:   "application proxy" or "connector proxy" class 
VARIABLES: $$USERTYPE                   TYPE: Output
 VARIABLES DESCRIPTION:   returns 1 if proxy user, else 0 
COMPONENT/ENTRY POINT: $$ACTIVE(XUDA)
VARIABLES: XUDA                         TYPE: Input
 VARIABLES DESCRIPTION:   ien of New Person file record 
VARIABLES: $$ACTIVE                     TYPE: Output
 VARIABLES DESCRIPTION:   returns 1 if active user, 0 if not 
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4540                            IA #: 4540
  DATE CREATED: DEC 14, 2004            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSN50P6                      NAME: DBIA4540
  ID: PSN50P6
 GENERAL DESCRIPTION:   This DBIA is provided by NDF (National Drug File) as an
 API to the VA GENERIC file (#50.6). This API is to used in the future by all
 packages accessing this file as all the Pharmacy packages are being
 re-engineered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ZERO(PSNIEN,PSNFT,PSNFL,PSNX,LIST)
 COMPONENT DESCRIPTION:   Format: D ZERO^PSN50P6(PSNIEN,PSNFT,PSNFL,PSNX,LIST) 
VARIABLES: PSNIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSNIEN = IEN of entry in VA GENERIC file (#50.6)
 [optional] 
VARIABLES: PSNFT                        TYPE: Input
 VARIABLES DESCRIPTION:   PSNFT = NAME field (#.01) of the VA GENERIC file
 (#50.6) (a value of  "??" may be used) [optional] 
VARIABLES: PSNX                         TYPE: Input
 VARIABLES DESCRIPTION:   PSNX = 1 for exact match flag [optional] 
VARIABLES: PSNFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSNFL = Inactive date: A null value will return all
 entries (entry of a FileMan format date (ex: 3030917) will return active
 entries after this date) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSNIEN,.01)=NAME(50.6,.01) 
  
 ^TMP($J,LIST,PSNIEN,1)=INACTIVATION DATE(50.6,1)^External format (ex: SEP 
 12,1999) 
  
 ^TMP($J,LIST,"B",NAME,PSNIEN)= "" 
COMPONENT/ENTRY POINT: $$ROOT
 COMPONENT DESCRIPTION:   $$ROOT returns the global root of VA Generic file
 (#50.6) Format: S X=$$ROOT^PSN50P6 
VARIABLES: $$ROOT                       TYPE: Output
 VARIABLES DESCRIPTION:   $$ROOT Where: $$ROOT is "^PSNDF(50.6," 

NUMBER: 4541                            IA #: 4541
  FILE NUMBER: 350                      GLOBAL ROOT: IB(
  DATE CREATED: MAR 02, 2006            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: AR access to INTEGRATED BILLING ACTION file 350
  ID: IB(
GLOBAL REFERENCE: IB(D0,0)
FIELD NUMBER: .01                       FIELD NAME: REFERENCE NUMBER
  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: ACTION TYPE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: RESULTING FROM
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: UNITS
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: TOTAL CHARGE
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .11                       FIELD NAME: AR BILL NUMBER
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .14                       FIELD NAME: DATE BILLED FROM
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .15                       FIELD NAME: DATE BILLED TO
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .16                       FIELD NAME: PARENT EVENT
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .17                       FIELD NAME: EVENT DATE
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: STATUS
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   As part of the Vista IB/AR date extract to the ARC, AR
 needs to access file 350 (INTEGRATED BILLING ACTION).  AR would like direct
 global access to the following: 
  
 Access to "ABIL" cross-reference (AR BILL NUMBER) 
  
 Access to "C" cross-reference (PATIENT) 
  
 Direct global access to ^IB(DO,0) to place data in the AR DATA QUEUE (348.4) 
  
 Fileman access to the .05 STATUS field of file 350 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   
  
  DATE ACTIVATED: NOV 17, 2020

NUMBER: 4542                            IA #: 4542
  FILE NUMBER: 2                        GLOBAL ROOT: DD(2
  DATE CREATED: APR 13, 2006            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DD Nodes in Patient (#2) file
  ID: DD(2
 GENERAL DESCRIPTION:   DG*5.3*705, FIX PATIENT FILE DATA DICTIONARY, deletes
 Fileman DD entries for fields on the PATIENT file (#2). 
  
 The pre-init routine, DG53705I, will be run only once and it will delete the
 following nodes: 
  
 D BMES^XPDUTL(">>> Deleting bad write access, help, audit, other miscel 
 laneous nodes") 
          K ^DD(2,.12113,9),^DD(2,.14112,9) 
          K ^DD(2,.108,3) 
          K ^DD(2,.391,4) 
          F Z=.01,.2924,.3111,.3192,991.07 K ^DD(2,Z,"AUDIT") 
          K ^DD(2.312,.18,"AUDIT") 
          K ^DIC(2,0,"AUDIT") 
          K ^DD(2,0,"VR") 
          K ^DD(2,0,"VRPK") 
          K ^DIC(2,"%",7,0) 
          K ^DIC(2,"%","B","QAM",7) 
  
 D PT^DDUCHK1  (">>> Deleting bad pointer nodes") (this deletes any "PT"
 reference node whose file and field either don't exist or don't point to file
 2) 
  
 D BMES^XPDUTL(">>> Deleting bad identifier nodes") 
          F Z=.2924,.302,.351,"GARB","WARD","WR","ZREW" K ^DD(2,0,"ID",Z) 
  
 D BMES^XPDUTL(">>> Deleting bad field description nodes") 
          S Z=1 F  S Z=$O(^DD(2,.107,21,Z)) Q:'Z  K ^DD(2,.107,21,Z,0) 
  
 D BMES^XPDUTL(">>> Deleting bad cross reference nodes") 
          ^DD(2,0,"IX","AHL",.01) 
          ^DD(2,0,"IX",AHL2",.02) 
          ^DD(2,0,"IX","AHL3",.03) 
          ^DD(2,0,"IX","AHL5",.06) 
          ^DD(2,0,"IX","AHL4",.09) 
          ^DD(2,0,"IX","A4EC",.102) 
          ^DD(2,0,"IX","ACP",.302) 
          ^DD(2,0,"IX","AP",.302) 
          ^DD(2,0,"IX","CHK4",.3025) 
          ^DD(2,0,"IX","AEMP",.31115) 
          ^DD(2,0,"IX","MAC",.31115) 
          ^DD (2,0,"IX","AI",.32102) 
          ^DD(2,0,"IX","AK",.32103) 
          ^DD(2,0,"IX","AEXP",.351) 
          ^DD(2,0,"IX","AHL6",.351) 
          ^DD(2,0,"IX","AT",.351) 
          ^DD(2,0,"IX","AR",.361) 
          ^DD(2,0,"IX","BEN",.36205) 
          ^DD(2,0,"IX","CHK1",.36205) 
          ^DD(2,0,"IX","CHK2,".36215) 
          ^DD(2,0,"IX","CHK3",.36235) 
          ^DD(2,0,"IX","AT",.381) 
  STATUS: Active
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4543                            IA #: 4543
  DATE CREATED: DEC 27, 2004            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSN50P65                     NAME: DBIA4543
  ID: PSN50P65
 GENERAL DESCRIPTION:   This DBIA is provided by NDF (National Drug File) as an
 API to the VA DRUG CLASS file (#50.605). This API is to used in the future by
 all packages accessing this file as all the Pharmacy packages are being
 re-engineered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: IEN(PSNIEN,PSNFT,LIST)
 COMPONENT DESCRIPTION:   Format: D IEN^PSN50P65(PSNIEN,PSNFT,LIST) 
VARIABLES: PSNIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSNIEN - IEN of entry in VA DRUG CLASS file (#50.605)
 [optional] 
VARIABLES: PSNFT                        TYPE: Input
 VARIABLES DESCRIPTION:   PSNFT - CODE field (#.01) of VA DRUG CLASS file
 (#50.605) (a value of  "??" may be used) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSNIEN,.01)=CODE(50.605,.01) 
  
 ^TMP($J,LIST,PSNIEN,1)=CLASSIFICATION(50.605,1) 
  
 ^TMP($J,LIST,"B",CODE,PSNIEN)= "" 
COMPONENT/ENTRY POINT: C(PSNIEN,PSNFT,LIST)
 COMPONENT DESCRIPTION:   Format: D C^PSN50P65(PSNIEN,PSNFT,LIST) 
VARIABLES: PSNIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSNIEN = IEN of entry in VA DRUG CLASS file (#50.605)
 [optional] 
VARIABLES: PSNFT                        TYPE: Input
 VARIABLES DESCRIPTION:   PSNFT = the CLASSIFICATION field (#1) of the VA DRUG
 CLASS file (#50.605) (a value of  "??" may be used) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSNIEN,.01)=CODE(50.605,.01) 
  
 ^TMP($J,LIST,PSNIEN,1)=CLASSIFICATION(50.605,1) 
  
 ^TMP($J,LIST,PSNIEN,2)=PARENT CLASS(50.605,2)^CODE (50.605,.01) 
  
 ^TMP($J,LIST,PSNIEN,3)=TYPE(50.605,3) 
  
 ^TMP($J,LIST,"C",CODE,PSNIEN)= "" 
  
 Note: The "C" cross-reference in the format of
 ^PS(50.605,"C",CLASSIFICATION(50.605,1),IEN(50.605)) will be used for the
 lookup 
COMPONENT/ENTRY POINT: $$ROOT(PSNC)
 COMPONENT DESCRIPTION:   Format: S X=$$ROOT^PSN50P65(PSNC) 
VARIABLES: PSNC                         TYPE: Input
 VARIABLES DESCRIPTION:   PSNC = If "1" the global root of the "C"
 cross-reference is returned otherwise, the global root of the zero node is
 returned 
VARIABLES: $$ROOT                       TYPE: Output
 VARIABLES DESCRIPTION:   $$ROOT Where: $$ROOT = "^PS(50.605, ""C"")" if PSNC
 is passed in as 1 $$ROOT = "^PS(50.605,") if PSNC is null 
COMPONENT/ENTRY POINT: SSET
 COMPONENT DESCRIPTION:   Returns a subset of active child drug classes (plus
 HA000) of the VA DRUG CLASS file (#50.605).  
  
 A drug class is considered a 'CHILD' if there is no data in the PARENT field
 (#2). In order to be considered inactive, the CODE field (#.01) must contain
 the word INACTIVE.  
VARIABLES: PSNC                         TYPE: Input
 VARIABLES DESCRIPTION:   Count (number wheel) used when populating the return
 ^TMP global.  
VARIABLES: PSNCNT                       TYPE: Input
 VARIABLES DESCRIPTION:   Number of items to return at one time.  
VARIABLES: PSNI                         TYPE: Input
 VARIABLES DESCRIPTION:   Starting location for the 'B' cross-reference.  
VARIABLES: DIR                          TYPE: Input
 VARIABLES DESCRIPTION:   
  1 - Process 'B' cross-reference backwards.  -1 - Process 'B' cross-reference
 backwards.  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   The subscript to use to return data in the ^TMP
 global.  
VARIABLES: ~TMP(SUB,$J,1,PSNC)          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP(SUB,$J,1,PSNC)=IEN of the Drug Class ^ CODE
 field (#.01) ^ CLASSIFICATION (#1) 
  DATE ACTIVATED: MAY 22, 2019

NUMBER: 4544                            IA #: 4544
  DATE CREATED: MAR 08, 2006            CUSTODIAL PACKAGE: CMOP
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSX550
  NAME: PSX550                          ID: PSX550
 GENERAL DESCRIPTION:   This DBIA is provided by CMOP as an API to the CMOP
 SYSTEM file (#550).  The API returns the STATUS field (#1) for the System name
 passed to the API.  
  
 This API is to used in the future by all packages accessing this file as all
 the Pharmacy packages are being re-engineered.  
  STATUS: Active
COMPONENT/ENTRY POINT: PSX(PSXIEN,PSXTXT,LIST)
 COMPONENT DESCRIPTION:   This component returns the STATUS field (#1) 
VARIABLES: PSXIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   CMOP system internal entry number (optional) 
VARIABLES: PSXTXT                       TYPE: Input
 VARIABLES DESCRIPTION:   Free Text CMOP system name (optional) 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript name used in ^TMP global [REQUIRED] 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=1 for successful return of data or
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST,1)=STATUS (550,1 - S)^External Format for the Set of Codes 

NUMBER: 4545                            IA #: 4545
  DATE CREATED: DEC 14, 2004            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSN50P68                     NAME: DBIA4545
  ID: PSN50P68
 GENERAL DESCRIPTION:   This DBIA is provided by NDF (National Drug File) as an
 API to the VA PRODUCT file (#50.68). This API is to used in the future by all
 packages accessing this file as all the Pharmacy packages are being
 re-engineered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DATA(PSNIEN,PSNFT,LIST)
 COMPONENT DESCRIPTION:   Format: D DATA^PSN50P68(PSNIEN,PSNFT,LIST) 
VARIABLES: PSNIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSNIEN = IEN of entry in VA PRODUCT file (#50.68)
 [optional] 
VARIABLES: PSNFT                        TYPE: Input
 VARIABLES DESCRIPTION:   PSNFT = NAME field (#.01) of the VA PRODUCT file
 (#50.68) (a value of  "??" may be used) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSNIEN,.01)=NAME(50.68,.01) 
  
 ^TMP($J,LIST,PSNIEN,.05)=VA GENERIC NAME(50.68,.05)^NAME(50.6,.01) 
  
 ^TMP($J,LIST,PSNIEN,3)=UNITS(50.68,3)^NAME (50.607,.01) 
  
 ^TMP($J,LIST,PSNIEN,4)=NATIONAL FORMULARY NAME(50.68,4) 
  
 ^TMP($J,LIST,PSNIEN,11)=GCNSEQNO(50.68,11) 
  
 ^TMP($J,LIST,PSNIEN,12)=PREVIOUS GCNSEQNO (50.68,12) 
  
 ^TMP($J,LIST,PSNIEN,13)=NDC LINK TO GCNSEQNO(50.68,13) 
  
 ^TMP($J,LIST,PSNIEN,19)=CS FEDERAL SCHEDULE(50.68,19)^External format for the
 set of codes 
  
 ^TMP(552498364,5068,2887,43,1,.01)="RxNorm^RxNorm" 
  
 ^TMP(552498364,5068,2887,43,2,.01)="SNOMED^SNOMED" 
  
  
 ^TMP($J,LIST,PSNIEN,2000)=SERVICE CODE(50.68,2000) 
  
 Note: If there is no data in the SERVICE CODE field (#2000) of the VA PRODUCT
 file (#50.68), the value 600000 will be returned for the SERVICE CODE.  
  
 ^TMP($J,LIST,"B",NAME,PSNIEN)= "" 
  DATE ACTIVATED: MAR 28, 2025

NUMBER: 4546                            IA #: 4546
  DATE CREATED: DEC 14, 2004
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSS51P1                      NAME: ADMINISTRATION SCHEDULE
  ID: PSS51P1
 GENERAL DESCRIPTION:   This DBIA is provided by PDM (Pharmacy Data Management)
 as an API to the ADMINISTRATION SCHEDULE file (#51.1). This API must be used
 by all packages accessing this file as all the Pharmacy packages are being
 re-engineered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ZERO(PSSIEN,PSSFT,PSSPP,PSSTSCH,LIST)
 COMPONENT DESCRIPTION:   Format: D
 ZERO^PSS51P1(PSSIEN,PSSFT,PSSPP,PSSTSCH,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSIEN = IEN of entry in ADMINISTRATION SCHEDULE file
 (#51.1) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFT = NAME field in ADMINISTRATION SCHEDULE file
 (#51.1) (a value of  "??" may be used) [optional] 
VARIABLES: PSSPP                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSPP = the PACKAGE PREFIX field (#4) of the
 ADMINISTRATION SCHEDULE file (#51.1) (screening for the Package Prefix if this
 field is passed in (ex: PSJ, LR )) [optional] 
VARIABLES: PSSTSCH                      TYPE: Input
 VARIABLES DESCRIPTION:   PSSTSCH = TYPE OF SCHEDULE field (#5) of
 ADMINISTRATION SCHEDULE file (#51.1) (screening for One-time "O" if PSSTSCH
 passed in) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01)=NAME (51.1,.01) 
  
 ^TMP($J,LIST,PSSIEN,1)=STANDARD ADMINISTRATION TIMES(51.1,1) 
  
 ^TMP($J,LIST,PSSIEN,2)=FREQUENCY (IN MINUTES)(51.1,2) 
  
 ^TMP($J,LIST,PSSIEN,2.5)=MAX DAYS FOR ORDERS(51.1,2.5) 
  
 ^TMP($J,LIST,PSSIEN,4)=PACKAGE PREFIX(51.1,4) 
  
 ^TMP($J,LIST,PSSIEN,5)=TYPE OF SCHEDULE(51.1,5)^External format for the set of
 code 
  
 ^TMP($J,LIST,PSSIEN,6)=STANDARD SHIFTS(51.1,6) 
  
 ^TMP($J,LIST,PSSIEN,8)=OUTPATIENT EXPANSION(51.1,8) 
  
 ^TMP($J,LIST,PSSIEN,8.1)=OTHER LANGUAGE EXPANSION(51.1,8.1) 
  
 ^TMP($J,LIST,"B",NAME,PSSIEN)= "" 
COMPONENT/ENTRY POINT: AP(PSSPP,PSSFT,PSSWDIEN,PSSSTPY,LIST,PSSFREQ)
 COMPONENT DESCRIPTION:   Format: D
 AP^PSS51P1(PSSPP,PSSFT,PSSWDIEN,PSSSTPY,LIST,PSSFREQ) 
VARIABLES: PSSPP                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSPP = PACKAGE PREFIX field (#4) of the
 ADMINISTRATION SCHEDULE file (#51.1) [required] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFT = NAME field (#.01) of the ADMINISTRATION
 SCHEDULE file (#51.1) (a value of  "??" may be used) [optional] 
VARIABLES: PSSWDIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   PSSWDIEN = IEN of entry of WARD multiple in
 ADMINISTRATION SCHEDULE file (#51.1) [optional] 
VARIABLES: PSSSTPY                      TYPE: Input
 VARIABLES DESCRIPTION:   PSSSTPY = TYPE OF SCHEDULE field (#5) OF
 ADMINISTRATION SCHEDULE file (#51.1) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01)=NAME(51.1,.01) 
  
 ^TMP($J,LIST,PSSIEN,1)=STANDARD ADMINISTRATION TIMES(51.1,1) 
  
 ^TMP($J,LIST,PSSIEN,2)=FREQUENCY (IN MINUTES) (51.1,2) 
  
 ^TMP($J,LIST,PSSIEN,2.5)=MAX DAYS FOR ORDERS(51.1,2.5) 
  
 ^TMP($J,LIST,PSSIEN,4)=PACKAGE PREFIX(51.1,4) 
  
 ^TMP($J,LIST,PSSIEN,5)=TYPE OF SCHEDULE(51.1,5)^External format for the set of
 code 
  
 ^TMP($J,LIST,PSSIEN,8)=OUTPATIENT EXPANSION(51.1,8) 
  
 ^TMP($J,LIST,PSSIEN,"WARD",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST,PSSIEN,"WARD",PSSWDIEN,.01)=WARD (51.11,.01)^NAME(42,.01) 
  
 ^TMP($J,LIST,PSSIEN,"WARD",PSSWDIEN,1)=WARD ADMINISTRATION TIMES(51.11,1) 
  
 ^TMP($J,LIST,"AP"_PACKAGE PREFIX,NAME,PSSIEN)="" 
  
 Note: If PSSSTYP is passed in the API will screening on this value: 
  
 1. If PSSPP is passed in, PSSFT = "" or PSSFT = "??", PSSWDIEN = "" and PSSTYP
 = "", then all schedules associated with the PSSPP and Ward will be returned.  
  
 2. If PSSPP is passed in, PSSFT = "" or PSSFT = "??", PSSWDIEN is passed in
 and PSSTYP = "", then all schedules associated with the PSSPP will be returned
 and only Ward matched the PSSWDIEN will be included.  
  
 3. If PSSPP = "", PSSFT = "QID", PSSWDIEN = "" and PSSTYP = "", then QID data
 and associated Wards will be returned.  
  
 4. If PSSPP = "", PSSFT = "QID", PSSWDIEN is passed in and PSSTYP = "", then
 QID data will be returned and only matched Ward will be included.  
VARIABLES: PSSFREQ                      TYPE: Input
 VARIABLES DESCRIPTION:   Filter for FREQUENCY field (#2) of the OF
 ADMINISTRATION SCHEDULE file   (#51.1).  [optional] 
  
 NOTE: If the frequency in the FREQUENCY field (#2) is greater than a value 
 passed in as PSSFREQ, then the entry will not be returned. Additionally, a 
 PSSFREQ value less than 1 or null will be ignored.  
COMPONENT/ENTRY POINT: PSSDQ
 COMPONENT DESCRIPTION:   Displays all the entries in the ADMINISTRATION
 SCHEDULE file (#51.1).  
COMPONENT/ENTRY POINT: SCHED
 COMPONENT DESCRIPTION:   Calls new routine PSSSCHED to return a new filtered
 array of Administration Schedules to CPRS for selection from the list of
 schedules presented to the user.  
VARIABLES: PSSWIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the ward location for the patient.  If this
 value is null, it will be set to 0.  
VARIABLES: PSSARRY                      TYPE: Both
 VARIABLES DESCRIPTION:   Array of schedules to be returned to CPRS.  The
 structure is: 
  
 PSSARRY(n) = IEN^NAME^OUTPATIENT EXPANSION^SCHEDULE TYPE^ADMIN TIME 
  
 IEN = Ward location (File #42) of the patient.  
  
 NAME = Schedule Name 
  
 OUTPATIENT EXPANSION = Display name of the schedule for Outpatient Pharmacy.  
  
 SCHEDULE TYPE = Schedule type of the schedule 
  
 ADMIN TIME = Either the Standard Administration Times for the schedule or the
 Ward-Specific Administration Times for the schedule, if defined.  
  
  DATE ACTIVATED: JUL 28, 2008

NUMBER: 4547                            IA #: 4547
  FILE NUMBER: 9002313.02               GLOBAL ROOT: BPSC(
  DATE CREATED: MAR 08, 2006            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: BPSC(
  ID: BPSC(
GLOBAL REFERENCE: BPSC(D0,0)
FIELD NUMBER: .07                       FIELD NAME: AUTO REVERSE FLAG
  LOCATION: 0;7                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: BPSC(D0,900)
FIELD NUMBER: 904                       FIELD NAME: CLOSED REASON
  LOCATION: 900;4                       ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   Integrated Billing needs read/write access to the
 following fields of the BPS CLAIMS file (#9002313.02).  
  
 Field    Name                Loc    Access 
  
 .07      AUTO REVERSE FLAG   0;7    Direct Read/Write 
  
 904      CLOSED REASON       900;4  Direct Read/Write 
  
  STATUS: Active
KEYWORDS: BPS
KEYWORDS: ECME
KEYWORDS: NCPDP
KEYWORDS: BPSC
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4548                            IA #: 4548
  DATE CREATED: DEC 14, 2004
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSS51P2                      NAME: MEDICATION ROUTES APIs
  ID: PSS51P2
 GENERAL DESCRIPTION:   This DBIA is provided by PDM (Pharmacy Data Management)
 as an API to the MEDICATION ROUTES file (#51.2). This API is to used in the
 future by all packages accessing this file as all the Pharmacy packages are
 being re-engineered. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ALL(PSSIEN,PSSFT,PSSFL,PSSPK,LIST)
 COMPONENT DESCRIPTION:   Format: D ALL^PSS51P2(PSSIEN,PSSFT,PSSFL,PSSPK,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSIEN = IEN of entry in MEDICATION ROUTES file
 (#51.2) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFT = NAME field (#.01) of the MEDICATION ROUTES
 file (#51.2) (a value of  "??" may be used) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date: A null value will return all
 entries (entry of a FileMan format date (ex: 3030917) will return active
 entries after this date) [optional] 
VARIABLES: PSSPK                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSPK = PACKAGE USE field (#3) of the MEDICATION
 ROUTES file (#51.2) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01)=NAME(51.2,.01) 
  
 ^TMP($J,LIST,PSSIEN,1)=ABBREVIATION(51.2,1) 
  
 ^TMP($J,LIST,PSSIEN,3)=PACKAGE USE(51.2,3)^External format for the set of
 codes 
  
 ^TMP($J,LIST,PSSIEN,4)=OUTPATIENT EXPANSION (51.2,4) 
  
 ^TMP($J,LIST,PSSIEN,4.1)=OTHER LANGUAGE EXPANSION (51.2,4.1) 
  
 ^TMP($J,LIST,PSSIEN,5)=INACTIVATION DATE (51.2,5)^External format (ex: SEP
 12,1999) 
  
 ^TMP($J,LIST,PSSIEN,6)=IV FLAG (51.2,6)^External format for the set of codes
 (ex: YES if flagged for IV) 
  
 ^TMP($J,LIST,PSSIEN,7) = PROMPT FOR INJ. SITE IN BCMA (51.2,8) ^ External
 format for the set of codes (ex: YES if BCMA should prompt for Injection Site) 
  
 ^TMP($J,LIST,PSSIEN,8) = DSPLY ON IVP/IVPB TAB IN BCMA? (51.2,9) ^ External
 format for the set of codes (ex: YES if BCMA should display this order on the
 IVP/IVPB tab) 
  
 ^TMP($J,LIST,"B",NAME,PSSIEN)="" 

NUMBER: 4549                            IA #: 4549
  DATE CREATED: DEC 14, 2004
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSS52P6                      NAME: DBIA4549
  ID: PSS52P6
 GENERAL DESCRIPTION:   This DBIA is provided by PDM (Pharmacy Data Management)
 as an API to the IV ADDITIVES file (#52.6). This API is to used in the future
 by all packages accessing this file as all the Pharmacy packages are being 
 re-engineered. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ZERO(PSSIEN,PSSFT,PSSFL,LIST)
 COMPONENT DESCRIPTION:   Format: D ZERO^PSS52P6(PSSIEN,PSSFT,PSSFL,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSIEN = IEN of entry in IV ADDITIVES file (#52.6)
 [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFT = PRINT NAME field (#.01) of IV ADDITIVES file
 (#52.6) (a value of  "??" may be used) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date: A null value will return all
 entries (entry of a FileMan format date (ex: 3030917) will return active
 entries after this date) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01)=PRINT NAME (52.6,.01) 
  
 ^TMP($J,LIST,PSSIEN,1)=GENERIC DRUG (52.6,1)^GENERIC NAME (50,.01) 
  
 ^TMP($J,LIST,PSSIEN,2)=DRUG UNIT(52.6,2)^Drug Unit external format (ex: MG,
 ML) 
  
 ^TMP($J,LIST,PSSIEN,3)=NUMBER OF DAYS FOR IV ORDER(52.6,3) 
  
 ^TMP($J,LIST,PSSIEN,4)=USUAL IV SCHEDULE(52.6,4) 
  
 ^TMP($J,LIST,PSSIEN,5)=ADMINISTRATION TIMES(52.6,5) 
  
 ^TMP($J,LIST,PSSIEN,7)=AVERAGE DRUG COST PER UNIT(52.6,7) 
  
 ^TMP($J,LIST,PSSIEN,12)=INACTIVATION DATE(52.6,12)^External format (ex: SEP
 12,1999) 
  
 ^TMP($J,LIST,PSSIEN,13)=CONCENTRATION(52.6,13) 
  
 TMP($J,LIST,PSSIEN,14)=MESSAGE(52.6,14) 
  
 ^TMP($J,LIST,PSSIEN,15)=PHARMACY ORDERABLE ITEM(52.6,15)^NAME(50.7,.01) 
  
 ^TMP($J,LIST,PSSIEN,17)=USED IN IV FLUID ORDER ENTRY (52.6,17)^External format
 (ex: "YES" for 1 otherwise it is null) 
  
 ^TMP($J,LIST,"B",PRINT NAME,PSSIEN)= "" 

NUMBER: 4550                            IA #: 4550
  DATE CREATED: DEC 14, 2004
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSS52P7                      NAME: DBIA4550
  ID: PSS52P7
 GENERAL DESCRIPTION:   This DBIA is provided by PDM (Pharmacy Data Management)
 as an API to the IV SOLUTIONS file (#52.7). This API is to use in the future
 by all packages accessing this file as all the Pharmacy packages are being 
 re-engineered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ZERO(PSSIEN,PSSFT,PSSFL,LIST)
 COMPONENT DESCRIPTION:   Format: D ZERO^PSS52P7(PSSIEN,PSSFT,PSSFL,LIST) 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSIEN = IEN of entry in IV SOLUTIONS file (#52.7)
 [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFT = PRINT NAME in IV SOLUTIONS file (#52.7) (a
 value of  "??" may be used) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date: A null value will return all
 entries (entry of a FileMan format date (ex: 3030917) will return active
 entries after this date) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01)=PRINT NAME(52.7,.01) 
  
 ^TMP($J,LIST,PSSIEN,.02)=PRINT NAME {2}(52.7,.02) 
  
 ^TMP($J,LIST,PSSIEN,1)=GENERIC DRUG(52.7,1)^GENERIC NAME (50,.01) 
  
 ^TMP($J,LIST,PSSIEN,2)=VOLUME(52.7,2) 
  
 ^TMP($J,LIST,PSSIEN,7)=AVERAGE DRUG COST (52.7,7) 
  
 ^TMP($J,LIST,PSSIEN,8)=INACTIVATION DATE(52.7,8)^External format (ex: SEP 12,
 1999) 
  
 ^TMP($J,LIST,PSSIEN,9)=PHARMACY ORDERABLE ITEM(52.7,9)^ NAME(50.7,.01) 
  
 ^TMP($J,LIST,PSSIEN,17)=USED IN IV FLUID ORDER ENTRY (52.7,17)^External format
 (ex: "YES" for 1 otherwise it is null) 
  
 ^TMP($J,LIST,PSSIEN,"ELYTES",0)=Total entries returning for this sub-file or
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST,PSSIEN,"ELYTES",PSS(1),.01)=ELECTROLYTES(52.702,.01)^NAME(50.4,.01
)
 (external format) 
  
 ^TMP($J,LIST,PSSIEN,"ELYTES",PSS(1),1)=CONCENTRATION(52.702,1) 
  
 ^TMP($J,LIST,"B",PRINT NAME,PSSIEN)= "" 
  
 Where: PSS(1) is the IEN of entry in the ELECTROLYTES multiple 
COMPONENT/ENTRY POINT: DRGIEN(PSS50,PSSFL,LIST)
 COMPONENT DESCRIPTION:   This component returns the IV Solution Print Name and
 Volume for a given entry from the Drug file (#50).  
VARIABLES: PSS50                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of entry in DRUG file (#50) [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSSFL = Inactive date: A null value will return all
 entries (entry of a FileMan format date (ex: 3030917) will return active
 entries after this date) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript name [required] 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returning or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01)=PRINT NAME(52.7,.01) 
  
 ^TMP($J,LIST,PSSIEN,2)=VOLUME(52.7,2) 
  
 ^TMP($J,LIST,"AC",PRINT NAME,PSSIEN)="" (where PSSIEN = IEN of the IV SOLUTION
 file (#52.7) 
  DATE ACTIVATED: NOV 29, 2017

NUMBER: 4551                            IA #: 4551
  DATE CREATED: DEC 14, 2004
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSSDI                        NAME: DBIA4551
  ID: PSSDI
 GENERAL DESCRIPTION:   This DBIA is provided by PDM (Pharmacy Data Management)
 as an API to do simulated VA FileMan calls. This API is to be used in the
 future by all packages needing to use FileMan to look at PDM files as all the
 Pharmacy packages are being re-engineered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DIC(PSSFILE,PSSAPP,.DIC,.X,DLAYGO,PSSSCRDT,PSSSCRUS,PSSVA
CL)
VARIABLES: PSSFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   PSSFILE = File number used for validation of access
 [required] 
VARIABLES: PSSAPP                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSAPP = Name space of the calling application (ex:
 PSJ for Inpatient Meds, PSO for Outpatient; PSSAPP is used to check if write
 access is allowed) [optional] 
VARIABLES: .DIC                         TYPE: Input
 VARIABLES DESCRIPTION:   See VA FileMan Programmer Manual for ^DIC call, for
 DIC, X, and DLAYGO input definitions 
VARIABLES: PSSSCRDT                     TYPE: Input
 VARIABLES DESCRIPTION:   PSSSCRDT = Inactivation Date. If the file has an
 Inactivation Date, then any entry with an Inactivation Date on or before
 PSNDATE will not be returned [optional] 
VARIABLES: PSSSCRUS                     TYPE: Input
 VARIABLES DESCRIPTION:   PSSSCRUS = APPLICATION PACKAGES' USE. This parameter
 only applies when the file is the DRUG File (#50). PSSSCRUS should be passed
 in the form of a String. If any of the characters in the PSSSCRUS String is
 contained in the APPLICATION PACKAGES' USE Field (#63), then the entry will be 
 returned [optional] 
VARIABLES: PSSDIY                       TYPE: Output
 VARIABLES DESCRIPTION:   PSSDIY will return null if the values for PSSFILE and
 PSSAPP are valid (it will return -1 if conditions were not met) 
                             
 See VA FileMan Programmer Manual for DIC output definition 
                             
 DLAYGO should only be passed in if the calling application has this type of
 access through another Integration Agreement 
VARIABLES: PSSVACL                      TYPE: Input
 VARIABLES DESCRIPTION:   PSSVACL = An array containing VA CLASSES that the
 user wants either included or excluded for the Drug lookup.  
  
 For example, if only drugs with a VA Class of DX201 & DX202 were to be
 available for selection, the local variable array would look like this: 
  
 PSSVACL("DX201")="" PSSVACL("DX202")="" PSSVACL("R")="" - The "R" means only
 drugs with these classes will be available for selection. If these classes
 were to be excluded, the letter "P" would be used instead.  
  
COMPONENT/ENTRY POINT: DO(PSSFILE,PSSAPP,.DIC)
 COMPONENT DESCRIPTION:   Format: D DO^PSSDI(PSSFILE,PSSAPP,.DIC) 
VARIABLES: PSSFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   PSSFILE = File number used for validation of access
 [required] 
VARIABLES: PSSAPP                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSAPP = Name space of the calling application (ex:
 PSJ for Inpatient Meds, PSO for Outpatient; PSSAPP is used to check if write
 access is allowed) [optional] 
VARIABLES: .DIC                         TYPE: Input
 VARIABLES DESCRIPTION:   See VA FileMan Programmer Manual for DIC input
 definition 
VARIABLES: PSSDIY                       TYPE: Output
 VARIABLES DESCRIPTION:   PSSDIY will return null if the values for PSSFILE and
 PSSAPP are valid (it will return -1 if conditions were not met) 
  
 See VA FileMan Programmer Manual for DO^DIC1 output definition 
COMPONENT/ENTRY POINT: MIX(PSSFILE,PSSAPP,.DIC,D,.X,DLAYGO,PSSDATE,PSSUSAGE,PSSV
ACL)
VARIABLES: PSSFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   PSSFILE = File number used for validation of access
 [required] 
VARIABLES: PSSAPP                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSAPP = Name space of the calling application (ex:
 PSJ for Inpatient Meds, PSO for Outpatient; PSSAPP is used to check if write
 access is allowed) [optional] 
VARIABLES: .DIC                         TYPE: Input
 VARIABLES DESCRIPTION:   See VA FileMan Programmer Manual for MIX^DIC1 call,
 for DIC, D, X, and DLAYGO input definitions 
VARIABLES: PSSDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   PSSDATE = Inactivation Date. If the file has an
 Inactivation Date, then any entry with an Inactivation Date on or before
 PSNDATE will not be returned [optional] 
VARIABLES: PSSUSAGE                     TYPE: Input
 VARIABLES DESCRIPTION:   PSSUSAGE = APPLICATION PACKAGES' USE. This parameter
 only applies when the file is the DRUG File (#50). PSSUSAGE should be passed
 in the form of a String. If any of the characters in the PSSUSAGE String is
 contained in the APPLICATION PACKAGES' USE Field (#63), then the entry will be 
 returned [optional] 
VARIABLES: PSSDIY                       TYPE: Output
 VARIABLES DESCRIPTION:   PSSDIY will return null if the values for PSSFILE and
 PSSAPP are valid (it will return -1 if conditions were not met) 
                             
 See VA FileMan Programmer Manual for MIX^DIC1 output definition 
                             
 DLAYGO should only be passed in if the calling application has this type of
 access through another Integration Agreement 
VARIABLES: PSSVACL                      TYPE: Input
 VARIABLES DESCRIPTION:   PSSVACL = An array containing VA CLASSES that the
 user wants either included or excluded for the Drug lookup.  
  
 For example, if only drugs with a VA Class of DX201 & DX202 were to be
 available for selection, the local variable array would look like this: 
  
 PSSVACL("DX201")="" PSSVACL("DX202")="" PSSVACL("R")="" - The "R" means only
 drugs with these classes will be available for selection. If these classes
 were to be excluded, the letter "P" would be used instead.  
  
COMPONENT/ENTRY POINT: EN(PSSFILE,PSSAPP,DIC,.DR,.DA,.DIQ)
 COMPONENT DESCRIPTION:   Format: D EN^PSSDI(PSSFILE,PSSAPP,DIC,.DR,.DA,.DIQ) 
VARIABLES: PSSFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   PSSFILE = File number used for validation of access
 [required] 
VARIABLES: PSSAPP                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSAPP = Name space of the calling application (ex:
 PSJ for Inpatient Meds, PSO for Outpatient; PSSAPP is used to check if write
 access is allowed) [optional] 
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   See VA FileMan Programmer Manual for EN^DIQ1 call,
 for DIC, DR, DA, and DIQ input definitions 
VARIABLES: PSSDIY                       TYPE: Output
 VARIABLES DESCRIPTION:   PSSDIY will return null if the values for PSSFILE and
 PSSAPP are valid (it will return -1 if conditions were not met) 
                             
 See VA FileMan Programmer Manual for EN^DIQ1 output definition 
COMPONENT/ENTRY POINT: $$FNAME(PSSFNO,PSSFILE)
 COMPONENT DESCRIPTION:   This component returns the field name of the
 specified Pharmacy file for the field number and file number passed in.  
VARIABLES: PSSFNO                       TYPE: Input
 VARIABLES DESCRIPTION:   Field number [required] 
VARIABLES: PSSFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   File number or sub-file number. This file must be a
 file that is owned by a Pharmacy application [required] 
VARIABLES: $$FNAME                      TYPE: Output
 VARIABLES DESCRIPTION:   $$FNAME = the field name. If an invalid field number
 or invalid file number is passed in, or the file number passed in is not a
 file owned by a pharmacy application, null will be returned.  

NUMBER: 4552                            IA #: 4552
  DATE CREATED: MAR 10, 2006            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBAKAT
  NAME: DBIA4552                        ID: IBAKAT
 GENERAL DESCRIPTION:   Integrated Billing is releasing the new routine IBAKAT,
 which contains an entry point that will be invoked by the patch PRCA*4.5*241
 post initialization process.  IBAKAT will identify all co-payment charges, for
 veterans affected by Hurricane Katrina, for care provided from 8/29/05 through
 2/28/06.  This routine will in turn invoke various APIs within Accounts 
 Receivable to credit veterans' accounts.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$CAN()
 COMPONENT DESCRIPTION:   This entry point invokes the process to cancel
 co-payment charges for veterans affected by Hurricane Katrina.  No input needs
 to be defined by the calling application.  This is an extrinsic function which
 returns the results of the call, in the format NUM^AMT^AMTH (to be defined
 below), to the calling application.  If the process is not conducted, because
 the cancellation reason KATRINA AFFECTED VETERAN is not defined the IB CHARGE
 REMOVE REASONS (#350.3) file, then the null string will be returned to the
 calling application.  
VARIABLES: NUM                          TYPE: Output
 VARIABLES DESCRIPTION:   This variable contains the number of veterans for
 whom co-payment charges were cancelled.  
VARIABLES: AMT                          TYPE: Output
 VARIABLES DESCRIPTION:   This variable contains the total dollar amount of all
 co-payment charges that were cancelled.  
VARIABLES: AMTH                         TYPE: Output
 VARIABLES DESCRIPTION:   Of the total dollar amount of all co-payment charges
 that were cancelled, this variable contains the portion of that amount for 
 which the co-payment charges had not yet been passed to Accounts Receivable,
 and were 'on hold' in Integrated Billing.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   Accounts Receivable should only invoke the routine
 IBAKAT during the post initialization process for patch PRCA*4.5*241.  

NUMBER: 4553                            IA #: 4553
  DATE CREATED: MAR 10, 2006            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RCKATP
  NAME: DBIA4553                        ID: RCKATP
 GENERAL DESCRIPTION:   Accounts Receivable will release the routine RCKATP
 with patch PRCA*4.5*241.  The patch post initialization process will queue a
 task that invokes this routine to make adjustments to the financial accounts
 of veterans affected by Hurricane Katrina.  DBIA4552 has been developed to
 allow this routine to invoke the Integrated Billing routine IBAKAT to identify
 co-payment charges that should be cancelled.  IBAKAT, in turn, will invoke
 several APIs in routine RCKATP to adjust the veteran's account in Accounts
 Receivable.  This DBIA defines the APIs that IBAKAT may call back into to
 credit the veteran's account.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$CHK(DFN)
 COMPONENT DESCRIPTION:   This entry point allows Integrated Billing to
 determine if it should attempt to cancel charges for a specific veteran.  This
 extrinsic function will determine if a veteran has been flagged as a veteran 
 affected by Hurricane Katrina, and if the veteran had previously been flagged
 in the AR DEBTOR (#340) file as having had co-payment charges cancelled.  This
 function will return a flag to whether co-payment charges may be cancelled for
 a specific veteran.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This input variable contains a pointer to the veteran
 in the PATIENT (#2) file.  
VARIABLES: RES                          TYPE: Output
 VARIABLES DESCRIPTION:   This return value from the $$CHK(DFN) function call
 returns a zero if charges cannot be cancelled for the veteran, or a one if
 charges can be cancelled for the veteran.  The function will return a one if
 the veteran has been flagged as affected by Hurricane Katrina, but has not yet
 been flagged in the AR DEBTOR (#340) file as having had co-payment charges
 cancelled.  
COMPONENT/ENTRY POINT: $$DEC(BILL,AMOUNT)
 COMPONENT DESCRIPTION:   This entry point allows Integrated Billing to request
 that Accounts Receivable reduce the balance of a specific bill by a specified 
 amount.  This extrinsic function will return to Integrated Billing the dollar
 amount that was NOT reduced from the bill.  
VARIABLES: BILL                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the bill number of the receivable that should
 be reduced.  The bill number is the name (.01 field value) of an entry in the 
 ACCOUNTS RECEIVABLE (#430) file.  
VARIABLES: AMOUNT                       TYPE: Input
 VARIABLES DESCRIPTION:   This is a positive dollar amount by which the balance
 of the requested receivable should be reduced.  
VARIABLES: RES                          TYPE: Output
 VARIABLES DESCRIPTION:   This variable contains the portion of the requested
 dollar amount that the receivable was NOT reduced.  For example, if the
 receivable to be reduced had a large outstanding balance, and was reduced by 
 the input dollar amount, the value returned by this extrinsic function is
 zero.  If the receivable was closed and had a zero balance (and thus could not
 be further reduced), the value returned by this extrinsic function would be
 equal to the input dollar amount.  If the balance of the receivable to be
 reduced was positive, but less than the input dollar amount, then the value
 returned by this extrinsic function would be the difference between the input
 dollar amount and the previous positive balance of the receivable.  
COMPONENT/ENTRY POINT: FLAG(DFN)
 COMPONENT DESCRIPTION:   This entry point is invoked by Integrated Billing to
 request that Accounts Receivable flag a specific veteran in the AR DEBTOR
 (#340) file as having had co-payment charges cancelled.  This call does not
 provide output to the calling application.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This input variable contains a pointer to the veteran
 in the PATIENT (#2) file.  Accounts Receivable will find this patient's 
 associated entry in the AR DEBTOR (#340) file, and set field .09 (COPAY
 CHARGES CANCELLED?) for that entry equal to one.  
COMPONENT/ENTRY POINT: ADJ(DFN,AMOUNT)
 COMPONENT DESCRIPTION:   This entry point allows Integrated Billing to request
 that Accounts Receivable reduce the total account balance of a specific
 veteran by a specific amount.  Accounts Receivable will accomplish this task
 by reducing any active bills of that veteran, or establishing a pre-payment
 for the veteran if necessary.  This call does not provide output to the
 calling application.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This input variable contains a pointer to the veteran
 in the PATIENT (#2) file.  
VARIABLES: AMOUNT                       TYPE: Input
 VARIABLES DESCRIPTION:   This is a positive dollar amount by which the
 specified veteran's account should be reduced.  
COMPONENT/ENTRY POINT: $$TPP(TRAN,ARR)
 COMPONENT DESCRIPTION:   This entry point allows Integrated Billing to request
 that Accounts Receivable calculate the total dollar amount of all decrease 
 adjustments that have been applied to a specific bill, after the application
 of a specific increase adjustment.  In this context, the decrease adjustments
 represent credits that have been applied to the veteran's account due to the
 receipt of a payment from an insurance company for the same episode of care
 for which the veteran was billed a co-payment.  This credit amount should not 
 be applied a second time to the veteran's account.  
VARIABLES: TRAN                         TYPE: Input
 VARIABLES DESCRIPTION:   This variable is a pointer to a transaction in the AR
 TRANSACTION (#433) file.  This transaction represents the increase adjustment
 used to debit the veteran's account when the veteran was billed a co-payment, 
 and the pointer to this transaction is stored with the co-payment charge in
 the INTEGRATED BILLING ACTION (#350) file.  The pointer to this transaction is
 provided to specify that AR look for decrease adjustments that were filed
 after this transaction.  
VARIABLES: ARR                          TYPE: Both
 VARIABLES DESCRIPTION:   This variable is an array that is passed to this
 extrinsic function by reference.  The array may or may not be defined when it
 is passed to AR.  The array actually has the form ARR(BILL,TRAN), where BILL
 is the pointer to the receivable in the ACCOUNTS RECEIVABLE (#430) file, and
 TRAN is the pointer to one of the receivable's transactions in the AR
 TRANSACTION (#433) file.  When AR is invoked through this API to examine the
 decrease adjustments for a specific receivable, all the transactions that are
 included in the calculation are captured in the array and passed back to 
 Integrated Billing.  Integrated Billing may encounter a subsequent transaction
 for the same receivable, in which case it would invoke this API with defined
 array elements in ARR.  In this latter case, when AR is examining decrease
 adjustments to include in its total, it would exclude those decrease
 adjustments stored in ARR since they were previously included in the
 calculation.  
VARIABLES: RES                          TYPE: Output
 VARIABLES DESCRIPTION:   This variable represents the output from the
 extrinsic function.  This value will be null if the input variable TRAN is not
 a positive value, or if this value could not be used to find a valid pointer 
 to a receivable in the ACCOUNTS RECEIVABLE (#430) file.  Otherwise, the value
 of this variable is "AMT^BILL", where: 
  
 AMT = The total transaction amount of all decrease adjustments filed 
       for the receivable after the filing of the input transaction 
       TRAN, excluding those adjustments stored in the input 
       array ARR.  
  
 BILL = The pointer to the receivable in the ACCOUNTS RECEIVABLE (#430) 
        with which the input transaction TRAN is associated.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   The Integrated Billing routine IBAKAT is invoked during
 the patch PRCA*4.5*241 post initialization process, as allowed by DBIA4552.  
 During this process only, Integrated Billing may make calls back to the
 calling Accounts Receivable routine (RCKATP) in order to credit a veteran's
 account.  

NUMBER: 4554                            IA #: 4554
  DATE CREATED: DEC 14, 2004            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSNDI                        NAME: DBIA4554
  ID: PSNDI
 GENERAL DESCRIPTION:   This DBIA is provided by NDF (National Drug File) as an
 API to do simulated VA FileMan calls. This API is to be used in the future by
 all packages needing to use FileMan to look at NDF files as all the Pharmacy 
 packages are being re-engineered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: IX(PSNFILE,PSNPACK,.DIC,D,.X,DLAYGO,PSNDATE)
VARIABLES: PSNFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   PSNFILE = File number used for validation of access
 [required] 
VARIABLES: PSNPACK                      TYPE: Input
 VARIABLES DESCRIPTION:   PSNPACK = Name space of the calling application. Ex:
 PSJ for Inpatient Meds, PSO for Outpatient.  PSNPACK is used to check if write
 access is allowed [optional] 
VARIABLES: .DIC                         TYPE: Input
 VARIABLES DESCRIPTION:   See VA FileMan Programmer Manual for IX^DIC call, for
 DIC, D, X, and DLAYGO input definitions 
VARIABLES: PSNDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   PSNDATE = Inactivation Date. If the file has an
 Inactivation Date, then any entry with an Inactivation Date on or before
 PSNDATE will not be returned [optional] 
VARIABLES: PSNDIY                       TYPE: Output
 VARIABLES DESCRIPTION:   PSNDIY will return null if the values for PSNFILE and
 PSNPACK are valid (it will return -1 if conditions were not met) 
                             
 See VA FileMan Programmer Manual for IX^DIC output definition 
                             
 DLAYGO should only be passed in if the calling application has this type of
 access through another Integration Agreement 
COMPONENT/ENTRY POINT: DIC(PSNFILE,PSNPACK,.DIC,.X,DLAYGO,PSNDATE)
VARIABLES: PSNFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   PSNFILE = File number used for validation of access
 [required] 
VARIABLES: PSNPACK                      TYPE: Input
 VARIABLES DESCRIPTION:   PSNPACK = Name space of the calling application. Ex:
 PSJ for Inpatient Meds, PSO for Outpatient.  PSNPACK is used to check if write
 access is allowed [optional] 
VARIABLES: .DIC                         TYPE: Input
 VARIABLES DESCRIPTION:   See VA FileMan Programmer Manual for ^DIC call, for
 DIC, X, AND DLAYGO input definitions 
VARIABLES: PSNDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   PSNDATE = Inactivation Date. If the file has an
 Inactivation Date, then any entry with an Inactivation Date on or before
 PSNDATE will not be returned [optional] 
VARIABLES: PSNDIY                       TYPE: Output
 VARIABLES DESCRIPTION:   PSNDIY will return null if the values for PSNFILE and
 PSNPACK are valid (it will return -1 if conditions were not met) 
                             
 See VA FileMan Programmer Manual for DIC output definition 
                             
 DLAYGO should only be passed in if the calling application has this type of
 access through another Integration Agreement 

NUMBER: 4555                            IA #: 4555
  DATE CREATED: MAR 15, 2006
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Routine
  ROUTINE: PSSORUTE                     NAME: FIND STATUS OF PHARMACY ORDERS
  ID: PSSORUTE
 GENERAL DESCRIPTION:   The purpose of this call is to provide the status of
 any Pharmacy order. The order could be Inpatient Medications, Outpatient
 Pharmacy or Non-VA Medications. Additionally, the $$DOSE API will be used to
 reformat dosages and units as described below.  
  STATUS: Other                         DURATION: Till Otherwise Agreed
KEYWORDS: PSSORUTE
COMPONENT/ENTRY POINT: STATUS
VARIABLES: PSSDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the patient.  
VARIABLES: PSSON                        TYPE: Input
 VARIABLES DESCRIPTION:   The order number of the Pharmacy order, followed by a
 ';', followed by the package.  
  
 The order number expected is the PACKAGE REFERENCE field (#33) from the ORDER
 file (#100).  
VARIABLES: status                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns the english description of the status. For
 example: PENDING, DISCONTINUED, etc.  
COMPONENT/ENTRY POINT: DOSE
 COMPONENT DESCRIPTION:   Dosage/unit formatting API.  
  
 This API performs the following rules when reformatting the dosage: 
  
 1) Adds a leading 0 (zero) to decimal number less than 1 (one) 
    if it does not have one.       
  
 2) Adds a space between the numeric part of the dosage and the 
    unit (e.g. "100MG" is converted to "100 MG") 
  
 3) Automatically converts the units "cc" or "CC" to "ML" (e.g. 
    "25cc" is converted to "25 ML")  
  
 4) Automatically converts the abbreviations "u" and "U" to 
    "UNIT" (e.g. "2000U/5ML" is converted to "2000 UNIT/5 ML") 
  
 5) Does not apply the rules above to the following terms:"M2", 
    "PO2","D5W","12H","12HR","12HRS","24H","24HR","24HRS" 
VARIABLES: DOSE                         TYPE: Input
 VARIABLES DESCRIPTION:   Dosage to be formatted (e.g. 200MG, 10CC/.5MG,
 2000U).  
VARIABLES: $$DOSE                       TYPE: Output
 VARIABLES DESCRIPTION:   Reformatted dose (e.g. 200 MG, 20 ML/0.5 MG, 2000
 UNIT).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS

NUMBER: 4556                            IA #: 4556
  DATE CREATED: MAR 17, 2006            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: YSCLTST2
  NAME: DBIA4556                        ID: YSCLTST2
 GENERAL DESCRIPTION:   This agreement provides the calling program, the WBC
 and the ANC results needed for dispensing Clozapine medications.  
  STATUS: Active
KEYWORDS: Clozapine
KEYWORDS: CLOZAPINE
COMPONENT/ENTRY POINT: $$CL(DFN)
 COMPONENT DESCRIPTION:   This API will take the DFN as an input and returns a
 data string with 7 pieces.  
  Example: "1^4300^WBC^2150^ANC^3060307.100709^B" 
  
 first piece = 1 indicates that it's ok to dispense 
               2 Not OK to dispense - The rest of the results will indicate 
                 what happened. If there are no results listed, then the 
                 denial is due to the lack of results. If the WBC is less 
                 than 3000 or the ANC is less than 1500, then the denial is 
                 due to out of range results.  
              -1 an invalid DFN or a lockout by the NCCC 
               0 NCCC has authorized the medication 
  second piece = WBC result 
  third piece  = WBC test name 
  fourth piece = ANC result 
  fifth piece  = ANC test name 
  sixth piece  = WBC and ANC test date and time 
  seventh piece = Dispense Frequency ("W", "B", "M") 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN Number (Required).  
VARIABLES: $$CL                         TYPE: Output
 VARIABLES DESCRIPTION:   This entry point returns a 7 piece data string.  
 Example: "1^4300^WBC^2150^ANC^3060307.100709^B" 
  
 first piece = 1 indicates that it's ok to dispense 
               0 Not OK to dispense - The rest of the results will indicate 
                 what happened. If there are no results listed, then the 
                 denial is due to the lack of results. If the WBC is less 
                 than 3000 or the ANC is less than 1500, then the denial is 
                 due to out of range results.  
              -1 an invalid DFN or a lockout by the NCCC second piece = WBC
 result third piece  = WBC test name fourth piece = ANC result fifth piece  =
 ANC test name sixth piece  = WBC and ANC test date and time seventh piece =
 Dispense Frequency ("W", "B", "M") 
COMPONENT/ENTRY POINT: CL1(DFN,DAYS)
 COMPONENT DESCRIPTION:   This entry point will return all the WBC and the ANC
 results for the given # of days in the descending date/time order in a TMP
 global.  
  
 Example: 
  
 ^TMP($J,"PSO",DATE.TIME)=4400^2288 where the 1st piece is the WBC result 
                                    and the 2nd piece is ANC result.  
  
 This data will repeat as many times for the given # of days.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN Number (Required).  
VARIABLES: DAYS                         TYPE: Input
 VARIABLES DESCRIPTION:   Null, zero or a number are valid entries. If null or
 zero it will return the latest WBC and ANC results in the last 6 days.  
COMPONENT/ENTRY POINT: $$OVERRIDE(DFN)
 COMPONENT DESCRIPTION:   This entry point provides the NCCC authorized
 clozapine medication.  It returns 1 for an NCCC authorized override or a 0 for
 not authorized.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN Number (Required).  
VARIABLES: $$OVERRIDE                   TYPE: Output
 VARIABLES DESCRIPTION:   It returns 1 for an NCCC authorized override or a 0
 for not authorized.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Dispensing clozapine medication requires Mental Health
 approval.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   ADDED 1/7/2010 
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Added 8/24/20 

NUMBER: 4557                            IA #: 4557
  FILE NUMBER: 123.5                    GLOBAL ROOT: GMR(123.5,
  DATE CREATED: MAR 22, 2006
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4557
  ID: GMR(123.5,
GLOBAL REFERENCE: GMR(123.5,
FIELD NUMBER: .01                       FIELD NAME: SERVICE NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   with Direct global read.  
FIELD NUMBER: 123.09                    FIELD NAME: SERVICE PRINTER
  LOCATION: 123;9                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: GMR(123.5,D0,688,
FIELD NUMBER: .01                       FIELD NAME: ASSOCIATED STOP CODE
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   with Direct global read.  
GLOBAL REFERENCE: GMR(123.5,'AB1'
 GLOBAL DESCRIPTION:   Cross reference used by ASSOCIATED STOP CODE field
 (#123.5688,.01).  Direct global read on "AB1" cross reference.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 4558                            IA #: 4558
  DATE CREATED: NOV 03, 2004            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XLFDT3
  NAME: LIBRARY FUNCTIONS               ID: XLFDT3
  STATUS: Active
COMPONENT/ENTRY POINT: $$LEAP(%)
 COMPONENT DESCRIPTION:   Check if a Leap year 
VARIABLES: %                            TYPE: Input
 VARIABLES DESCRIPTION:   Year 
VARIABLES: $$LEAP                       TYPE: Output
 VARIABLES DESCRIPTION:   
  1 == a leap year 
  0 == not a leap year 

NUMBER: 4559                            IA #: 4559
  DATE CREATED: NOV 09, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VAFHLZCL                     NAME: DBIA4141-C
  ID: VAFHLZCL
 GENERAL DESCRIPTION:   Supported call for building of HL7 ZCL repeated
 segment: ZCL - VA - Specific Outpatient Classification Segment for all
 existing Outpatient Classification Types.  
  
 HL7 ZCL repeated segment is built for all Outpatient Classification Types in
 an order of Table SD008 - Outpatient Classification Type.  
  
 ZCL - VA-Specific Outpatient Classification Segment 
  
  SEQ LEN  DT   R/O  TBL# VISTA ELEMENT NAME 
  ------------------------------------------
  1   4    SI   R            SET ID 
  2   2    ID   R    SD008   OUTPATIENT CLASSIFICATION TYPE 
  3   50   ST                VALUE 
  
  SD008 - Outpatient Classification Type 
  ----------------------------------------
  Outpatient Classification Type   Description 
  ---------------------------------------------------------
                 1               AGENT ORANGE 
                 2               IONIZING RADIATION 
                 3               SERVICE CONNECTED 
                 4               ENVIRONMENTAL CONTAMINANTS 
                 5               MILITARY SEXUAL TRAUMA 
                 6               HEAD AND/OR NECK CANCER 
                 7               COMBAT VETERAN 
                 8               PROJ 112/SHAD              
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ZCL
KEYWORDS: VAFHLZCL
KEYWORDS: HL7 CLASSIFICATION
COMPONENT/ENTRY POINT: EN(DFN,VAFENC,VAFSTR,VAFHLQ,VAFHLFS,VAFARRY)
 COMPONENT DESCRIPTION:   This call is designed to build HL7 ZCL segment. This
 segment contains VA - Specific Outpatient Classification Types with values
 representing the corresponding field values in the Visit file (#9000010) the
 Outpatient Encounter is pointing to.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number of the Patient file (#2) -
 required 
  
VARIABLES: VAFENC                       TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number of the Outpatient Encounter
 file (#409.68) - required 
  
VARIABLES: VAFSTR                       TYPE: Input
 VARIABLES DESCRIPTION:   String of requested sequences separated by commas.
 For all sequences VAFSTR="1,2,3".  
  
VARIABLES: VAFHLQ                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional HL7 null designation. Default is "" (quote
 quote) 
  
VARIABLES: VAFHLFS                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional HL7 field separator (1 character). Default
 is ^ (carrot).  
  
VARIABLES: VAFARRY                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional user-supplied array name that will hold ZCL
 segments.  
  
VARIABLES: VAFARRAY                     TYPE: Output
 VARIABLES DESCRIPTION:   Array of HL7 ZCL segments. If not defined : 
 VAFARRY="^TMP(""VAFHL"",$J,""CLASS"")".  
SUBSCRIBING PACKAGE: SCHEDULING         ISC: Albany
  DATE ACTIVATED: AUG 08, 2018

NUMBER: 4560                            IA #: 4560
  DATE CREATED: FEB 28, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: BPSNCPD3                     NAME: BPSNCPD3
  ID: BPSNCPD3
 GENERAL DESCRIPTION:   This API is used by external applications to inquire
 about DUR information for a prescription.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BPS
KEYWORDS: ECME
KEYWORDS: DUR1
KEYWORDS: DURRESP
KEYWORDS: EPHARMACY
COMPONENT/ENTRY POINT: DUR1(BRXIEN,BFILL,DUR,ERROR,BPRXCOB)
VARIABLES: BRXIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN (Pointer to the PRESCRIPTION File
 (#52)) 
VARIABLES: BFILL                        TYPE: Input
 VARIABLES DESCRIPTION:   Fill number (0 for Original, 1 for 1st refill, 2 for
 the 2nd refill, etc.) 
VARIABLES: DUR                          TYPE: Output
 VARIABLES DESCRIPTION:   Array of DUR information in the following format: 
  
   DUR(INSN,"BILLED") - 1 for processed through 
     ECME, 0 for not processed 
   DUR(INSN,"CARDHOLDER ID") - Patient's cardholder 
     ID 
   DUR(INSN,"ELIGBLT") - Eligibility indicator 
     (V for VA, T for TRICARE and C for CHAMPVA) 
     determined by Integrated Billing 
   DUR(INSN,"GROUP NAME") - Insurance group name 
   DUR(INSN,"GROUP NUMBER") - Insurance group 
     number 
   DUR(INSN,"INSURANCE NAME") - Insurance company 
     name 
   DUR(INSN,"INSURANCE POINTER") - Insurance 
     company IEN 
   DUR(INSN,"PLAN CONTACT") - Patient's Insurance 
     Plan Contact telephone number 
  
  Note: Where INSN is the Payer Sequence.  
  
  Note: Applicable DUR related data returned from 
        the DURRESP component described in this IA 
        is also returned in the DUR array. Refer 
        to the DURRESP component for details.  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   Optional. Returns error information about the call.  
VARIABLES: BPRXCOB                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The Payer Sequence: 
   1 - Primary (default) 
   2 - Secondary 
COMPONENT/ENTRY POINT: DURRESP(DURIEN,DUR,BPRXCOB)
VARIABLES: DUR                          TYPE: Output
 VARIABLES DESCRIPTION:   
  Array of DUR related information for a 
  specific claim response in the BPS RESPONSES 
  file in the following format: 
   DUR(INSN,"RESPONSE IEN") - Pointer to the 
     RESPONSE file (#9002313.03) for the claim 
     submission 
   DUR(INSN,"MESSAGE") - The Transmission level 
     specific data, or Message field 504 
   DUR(INSN,"PAYER MESSAGE") - Message returned 
     from the payer in the Transaction level 
   DUR(INSN,"STATUS") - Status of the claim 
     (i.e. REJECTED CLAIM, PAYABLE) 
   DUR(INSN,"BIN") - BIN number associated with 
     the payer.  
  
  The following four fields are redundant with 
  the fields in the DUR PPS array but are provided 
  for backwards compatibility.  
   DUR(INSN,"REASON") - Reason for Service Code 
     pointer to BPS NCPDP REASON FOR SERVICE CODE 
     file (#9002313.23) 
   DUR(INSN,"PREV FILL DATE") - Plan's Previous 
     Fill Date 
   DUR(INSN,"DUR FREE TEXT DESC") - Drug 
     Utilization Review (DUR) description 
     and/or claims rejection free text 
     information from the payer 
   DUR(INSN,"DUR ADD MSG TEXT") - Drug Utilization 
     Review (DUR) additional free text information 
     from the payer 
  
  The following fields are from the DUR PPS 
  RESPONSE multiple. 
   DUR(INSN,"DUR PPS",SEQ,"DUR PPS RESPONSE") - 
     Total number of DUR PPS responses from the 
     payer 
   DUR(INSN,"DUR PPS",SEQ,"REASON FOR SERVICE 
   CODE") - Code identifying the type of 
     utilization conflict detected or the reason 
     for the pharmacist's professional service 
   DUR(INSN,"DUR PPS",SEQ,"CLINICAL SIGNIFICANCE 
   CODE") - Code identifying the significance or 
     severity level of a clinical event as 
     contained in the originating data base 
   DUR(INSN,"DUR PPS",SEQ,"OTHER PHARMACY 
   INDICATOR") - Code for the type of pharmacy 
     dispensing the conflicting drug 
   DUR(INSN,"DUR PPS",SEQ,"PREVIOUS DATE OF FILL") 
     - Date prescription was previously filled 
   DUR(INSN,"DUR PPS",SEQ,"QUANTITY OF PREVIOUS 
   FILL") - Amount expressed in metric decimal 
     units of the conflicting agent that was 
     previously filled 
   DUR(INSN,"DUR PPS",SEQ,"DATABASE INDICATOR") 
     - Code identifying the source of drug 
     information used for DUR processing 
   DUR(INSN,"DUR PPS",SEQ,"OTHER PRESCRIBER 
   INDICATOR") - Code comparing the prescriber of 
     the current prescription to the prescriber of 
     the previously filled conflicting prescription 
   DUR(INSN,"DUR PPS",SEQ,"DUR FREE TEXT MESSAGE") 
     - Text that provides additional detail 
     regarding a DUR conflict 
   DUR(INSN,"DUR PPS",SEQ,"DUR ADDITIONAL TEXT") 
     - Descriptive information that further defines 
     the referenced DUR alert 
  
   DUR(INSN,"REJ CODE LST") - List of rejection 
     code(s) returned by the payer separated by 
     commas (i.e. 79,14).  
   DUR(INSN,"REJ CODES",SEQ,REJ CODE) - Array of 
     rejection code descriptions where REJ CODE 
     correlates to DUR(INSN,"REJ CODE LST") 
     value(s) and SEQ equals a sequential number 
                             
  Note: Where INSN is the Payer Sequence 
VARIABLES: DURIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Claim Response IEN (Pointer to the BPS RESPONSES File
 (#9002313.03)) 
VARIABLES: BPRXCOB                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The Payer Sequence: 
   1 - Primary (default) 
   2 - Secondary 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
  DATE ACTIVATED: AUG 11, 2011

NUMBER: 4561                            IA #: 4561
  FILE NUMBER: 100.21                   GLOBAL ROOT: OR(100.21'
  DATE CREATED: NOV 20, 2004
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: 4561                            ID: OR(100.21'
GLOBAL REFERENCE: OR(100.21,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Write & w/Fileman
 FIELD DESCRIPTION:   This field contains the name of the list being defined.  
  
FIELD NUMBER: .1                        FIELD NAME: UPPER CASE
  LOCATION: 0;3                         ACCESS: Direct Global Write & w/Fileman
 FIELD DESCRIPTION:   This is the name of the list in upper case.  
  
FIELD NUMBER: 1                         FIELD NAME: TYPE
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
 FIELD DESCRIPTION:   Type will be set to the value "TM".  
  
FIELD NUMBER: 1.6                       FIELD NAME: CREATOR
  LOCATION: 0;5                         ACCESS: Direct Global Write & w/Fileman
 FIELD DESCRIPTION:   Set to the user who created the list.  
  
FIELD NUMBER: 1.65                      FIELD NAME: CREATION D/T
  LOCATION: 0;7                         ACCESS: Direct Global Write & w/Fileman
 FIELD DESCRIPTION:   The date and time the list was created.  
  
GLOBAL REFERENCE: OR(100.21,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: MEMBER
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is a pointer to the PATIENT file #2 
  
 GLOBAL DESCRIPTION:   
  
GLOBAL REFERENCE: OR(100.21,D0,11)
FIELD NUMBER: 11                        FIELD NAME: VISIBILITY
  LOCATION: 100.21,11                   ACCESS: Direct Global Write & w/Fileman
 FIELD DESCRIPTION:   This is set to Owner.  
  
 GENERAL DESCRIPTION:   This agreement allows the subscribers to maintain a
 pointer to the OE/RR LIST file, #100.21, and to add and edit information in
 the listed fields.  
  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TEAM LISTS
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: OE/RR LISTS
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clinical Reminders is allowed to edit a number of
 fields based on the following  agreement. When a list is created the field
 named CREATOR will be set to the current user. Subsequently, the list can only
 be edited by the Creator. The second condition is that the field named TYPE
 can only be set to "TM" which stands for "TEAM PATIENT MANUAL".  
  
  DATE ACTIVATED: APR 12, 2012

NUMBER: 4562                            IA #: 4562
  FILE NUMBER: 120.8                    GLOBAL ROOT: GMR(120.8
  DATE CREATED: NOV 17, 2004
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Use of V cross-reference in 120.8
  ID: GMR(120.8
GLOBAL REFERENCE: GMR(120.8,'V'
 GLOBAL DESCRIPTION:   Entries on the V cross-reference are by date/time and
 internal entry number.  For example, ^GMR(120.8,"V",3041002.1302,567 
 GENERAL DESCRIPTION:   The pharmacy benefits management software needs the
 ability to have direct global access to the V cross-reference of file 120.8.  
 The project needs to be able to quickly find all verified reactions over a
 given time frame, which the V cross-reference will supply.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Verified
KEYWORDS: Allergy
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
 SUBSCRIBING DETAILS:   PBM needs to be able to identify all verified allergies
 and adverse reactions over a given time frame.  Use of the "V" cross-reference
 from file 120.8 (PATIENT ALLERGIES) will allow them to quickly identify all
 verified entries by date/time.  

NUMBER: 4563                            IA #: 4563
  DATE CREATED: NOV 20, 2004            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGPFAPI                      NAME: DGPF DISPLAY PATIENT RECORD FLAG
  ID: DGPFAPI
 GENERAL DESCRIPTION:   The purpose of this API is to perform a lookup for
 active patient record flag assignments for a given patient and format the
 output data for roll-and-scroll display.  The following Patient Record Flag
 files are used: (#26.15) PRF NATIONAL FLAG (#26.11) PRF LOCAL FLAG (#26.13)
 PRF ASSIGNMENT (#26.14) PRF ASSIGNMENT HISTORY (#26.16) PRF TYPE The primary
 mechanism is from within the Registration package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DISPPRF(DFN)
 COMPONENT DESCRIPTION:   This entry point is used to perform a lookup for
 active patient record flag assignments for a given patient and format the
 output data for roll-and-scroll display.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the patient in the PATIENT
 File (#2).  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 4564                            IA #: 4564
  FILE NUMBER: 772                      GLOBAL ROOT: HL(772
  DATE CREATED: JAN 08, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: 4564                            ID: HL(772
GLOBAL REFERENCE: HL(772,'C',D0,0)
 GLOBAL DESCRIPTION:   This is the "C" index on the 772 file that allows a user
 to look up a HL7 message by its unique message ID.  
GLOBAL REFERENCE: HL(772,D0,P)
FIELD NUMBER: 20                        FIELD NAME: STATUS
  LOCATION: P;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the current status of this message transmission.  
 GLOBAL DESCRIPTION:   This is the file node on which the STATUS field is
 located.  
 GENERAL DESCRIPTION:   This IA allows the subscribing package to search the
 "C" crossreference of file HL7 MESSAGE TEXT, #772 and then get the status of
 the message using VA FILEMAN.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Clinical reminders will search through the "C" cross
 reference for the HL7 MESSAGE TEXT (file # 772) looking for a particular
 message and then obtain the information from the STATUS field using VA
 FILEMAN.  
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4565                            IA #: 4565
  DATE CREATED: APR 05, 2007            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDAMUTIL
  NAME: DBIA4565                        ID: SDAMUTIL
 GENERAL DESCRIPTION:   This DBIA provides an interface to delete the CONSULT
 LINK (Field #33) in the RSA APPOINTMENT LIST File (#44.44) for a specific RSA
 appointment, which is identified by its appointment ID. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RSA
KEYWORDS: SD
KEYWORDS: DELCNSLT
COMPONENT/ENTRY POINT: $$DELCNSLT(SDRSAID)
 COMPONENT DESCRIPTION:   This function will return a 1 or 0 based on the
 successful completion of deleting the CONSULT LINK (Field #33) in the RSA
 APPOINTMENT LIST File (#44.44) for a specific RSA appointment, identified by
 its ID.  
VARIABLES: SDRSAID                      TYPE: Input
 VARIABLES DESCRIPTION:   The appointment ID that uniquely identifies the RSA
 appointment. - REQUIRED 
VARIABLES: $$DELCNSLT                   TYPE: Output
 VARIABLES DESCRIPTION:   This API returns one of two possible values: 
  
 1 - Consult Link successfully deleted from 
     appointment.                                   0 - RSA appointment ID
 could not be found 
     to delete Consult Link.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  DATE ACTIVATED: SEP 27, 2007

NUMBER: 4566                            IA #: 4566
  FILE NUMBER: 120.51                   GLOBAL ROOT: GMR(120.51
  DATE CREATED: NOV 30, 2004
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: GMRV VITAL QUALIFIER            ID: GMR(120.51
GLOBAL REFERENCE: GMR(120.51,D0,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: D0,0                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The pharmacy benefit management extract needs to go
 through the qualifiers for selected vital signs.  
 GENERAL DESCRIPTION:   PBM needs to be able to access VITAL QUALIFIERS for
 direct global reads.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PBM
KEYWORDS: QUALIFIER
KEYWORDS: GMRV
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham
 SUBSCRIBING DETAILS:   The pharmacy benefits management services package needs
 to be able to have direct global read privilages to extract the qualifiers for
 selected vitals for a given time frame.  

NUMBER: 4567                            IA #: 4567
  FILE NUMBER: 9000010.11               GLOBAL ROOT: AUPNVIMM(9000010.11
  DATE CREATED: DEC 07, 2004
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DIRECT GLOBAL READS OF IMMUNIZATIONS, TIMES & DATES
  ID: AUPNVIMM(9000010.11
GLOBAL REFERENCE: AUPNVIMM(9000010.11
FIELD NUMBER: .01                       FIELD NAME: IMMUNIZATION
  LOCATION: D0,0                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: AUPNVIMM(9000010.11
FIELD NUMBER: 1201                      FIELD NAME: EVENT DATE AND TIME
  LOCATION: D0,12                       ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The pharmacy benefits management extracts needs to
 perform direct global reads to extract the date, time and immunization from
 this file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PBM
KEYWORDS: IMMUNIZATION
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham
 SUBSCRIBING DETAILS:   The Pharmacy benefit management extract needs to rifle
 through each immunization and extract the data if the date criteria falls 
 within the search parameters.  

NUMBER: 4568                            IA #: 4568
  DATE CREATED: DEC 14, 2004            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XLFNAME7                     NAME: XLFNAME7
  ID: XLFNAME7
 GENERAL DESCRIPTION:   Name standardization and name processing APIs.  
  STATUS: Active
COMPONENT/ENTRY POINT: $$FORMAT(.XUNAME,XUMINL,XUMAXL,XUNOP,XUCOMA,.XUAUDIT,XUFA
M,XUDNC)
 COMPONENT DESCRIPTION:   Format name value according to a number of name 
 standardization rules and user specifications.  
VARIABLES: XUNAME                       TYPE: Both
 VARIABLES DESCRIPTION:   Text value representing person name to transform 
VARIABLES: XUMINL                       TYPE: Input
 VARIABLES DESCRIPTION:   Minimum length (optional, default 3) 
VARIABLES: XUMAXL                       TYPE: Input
 VARIABLES DESCRIPTION:   Maximum length (optional, default 30) 
VARIABLES: XUNOP                        TYPE: Input
 VARIABLES DESCRIPTION:   1 to standardize last name for 'NOP' x-ref for the
 Patient file (optional) 
VARIABLES: XUCOMA                       TYPE: Input
 VARIABLES DESCRIPTION:   0 to not require a comma, 1 to require a comma in the
 input value, 2 to add a comma if none, 3 to prohibit (remove) commas, 
 (optional, default 1) 
VARIABLES: XUAUDIT                      TYPE: Both
 VARIABLES DESCRIPTION:   Variable to return audit, pass by reference 
 (optional). Returned values:                  XUAUDIT = 0 if no change was
 made, 
         = 1 if name is changed, 
         = 2 if name could not be converted XUAUDIT(1) defined if name contains
 no comma XUAUDIT(2) defined if parenthetical text is removed                   
                 XUAUDIT(3) defined if value is unconvertible XUAUDIT(4)
 defined if characters are removed or changed 
VARIABLES: XUFAM                        TYPE: Input
 VARIABLES DESCRIPTION:   1 if just the family name, 0 otherwise (optional) 
VARIABLES: XUDNC                        TYPE: Input
 VARIABLES DESCRIPTION:   1 to prevent componentization, 2 to return components
 before standardize (optional) 
VARIABLES: $$FORMAT                     TYPE: Output
 VARIABLES DESCRIPTION:   XUNAME in specified format or null if length of
 transformed value is less than XUMINL.  
COMPONENT/ENTRY POINT: NARY(.XU20NAME)
 COMPONENT DESCRIPTION:   Set up name component array.  
VARIABLES: XU20NAME                     TYPE: Both
 VARIABLES DESCRIPTION:   Input: Name value for which the name components will
 be returened.                             Output: XU20NAME(ComponentName),
 corresponding name components.  
COMPONENT/ENTRY POINT: $$NOP(XUX)
 COMPONENT DESCRIPTION:   Produce "NOP" cross-reference.  
VARIABLES: XUX                          TYPE: Input
 VARIABLES DESCRIPTION:   Name value for which the cross-reference may be
 created.  
VARIABLES: $$NOP                        TYPE: Output
 VARIABLES DESCRIPTION:   Standardized name or null if the same as input value. 
 
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4569                            IA #: 4569
  DATE CREATED: DEC 02, 2004
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: ORWDBA1                      NAME: DBIA4569
  ID: ORWDBA1
 GENERAL DESCRIPTION:   IA to allow other applications to determine if a given
 user holds the ORES security key.  This will allow them to verify the user
 will be able to electronically sign an order in the CPRS application.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORWDBA1
KEYWORDS: ORES
COMPONENT/ENTRY POINT: $$ORESKEY
 COMPONENT DESCRIPTION:   This entry point will check if the user has the ORES
 security key.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an IEN from the New Person (#200) file to be
 evaluated.  
VARIABLES: $$ORESKEY                    TYPE: Output
 VARIABLES DESCRIPTION:   Return value: 
         1 = the New Person (#200) file entry holds the ORES key.  
         0 = the New Person (#200) file entry does not hold the ORES key.  
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 4570                            IA #: 4570
  DATE CREATED: DEC 16, 2004            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XLFNAME8                     NAME: CVALID XLFNAME8
  ID: XLFNAME8
 GENERAL DESCRIPTION:   The API validates name components.  
  STATUS: Active
COMPONENT/ENTRY POINT: CVALID(XUC,XUX,.XUM)
 COMPONENT DESCRIPTION:   Validate name components.  
VARIABLES: XUC                          TYPE: Input
 VARIABLES DESCRIPTION:   Name component (e.g. FAMILY, GIVEN, etc.) 
VARIABLES: XUX                          TYPE: Input
 VARIABLES DESCRIPTION:   Input value to validate 
VARIABLES: XUM                          TYPE: Both
 VARIABLES DESCRIPTION:   Array to return results and errors (pass by 
 reference)                                 Output:XUM array in the format    
 XUM("ERROR",n)=error text, if any           XUM("HELP",n)=help text            
         XUM("LENGTH")=field length in length, e.g. 3-30 
 XUM("RESULT")=transformed name value, null if invalid entry 
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4571                            IA #: 4571
  DATE CREATED: DEC 16, 2004
  CUSTODIAL PACKAGE: VISTA DATA EXTRACTION FRAMEWORK
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VDEFREQ                      NAME: VDEF ERROR RECORDING
  ID: VDEFREQ
 GENERAL DESCRIPTION:   This IA describes the API used to record an error
 encountered during message building being done as the result of a request
 passed to the VDEF queue.  Use this API only inside of a message building
 routine that is invoked by VDEF.  The string passed to the API will be filed
 with the queued request that encounters the error in file 579.3.  
  STATUS: Active
KEYWORDS: VDEF
KEYWORDS: MESSAGE ERROR
COMPONENT/ENTRY POINT: ERR(error_string)
 COMPONENT DESCRIPTION:   This entry point places an error message into file
 #579.3.  
VARIABLES: error_string                 TYPE: Input
 VARIABLES DESCRIPTION:   This parameter should contain the error message to be
 filed.  
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
 SUBSCRIBING DETAILS:   ADDED 10/7/2009 

NUMBER: 4572                            IA #: 4572
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: JAN 03, 2005            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: E-SIG LOOKUP                    ID: VA(200
GLOBAL REFERENCE: VA(200,
FIELD NUMBER: 20.4                      FIELD NAME: ELECTRONIC SIGNATURE CODE
  LOCATION: 20;4                        ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   This is the user's electronic signature code global
 location.  
 GENERAL DESCRIPTION:   This INTEGRATION AGREEMENT describes the ability to
 read the hash of the user's electronic signature from file #200.  
  STATUS: Active
KEYWORDS: esig
KEYWORDS: HASH
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  ISC: Salt Lake City
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  ISC: Salt Lake City

NUMBER: 4573                            IA #: 4573
  DATE CREATED: DEC 07, 2004            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: READ AND WRITE OF TMP(XM-MESS   STATUS: Active
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  ISC: Salt Lake City

NUMBER: 4574                            IA #: 4574
  DATE CREATED: APR 18, 2006            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUPS
  NAME: XUPS APIs                       ID: XUPS
 GENERAL DESCRIPTION:   Two APIs are contained in routine XUPS to identify the
 VPID (VA Person ID) for a selected user or identify the DUZ for an entry in
 the New Person (#200) file from a VPID.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$VPID(DUZ)
 COMPONENT DESCRIPTION:   VPID entry point accepts the internal entry number
 (DUZ) of an entry in the New Person (#200) file and returns the VPID (VA
 Person ID) for the selected user.  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   DUZ = Internal entry number in New Person (#200)
 file.  
VARIABLES: $$VPID                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns the VPID (VA Person ID).  
COMPONENT/ENTRY POINT: $$IEN(VPID)
 COMPONENT DESCRIPTION:   IEN entry point accepts the VPID (VA Person ID) and
 returns the internal entry number (DUZ) from the New Person (#200) file.  
VARIABLES: VPID                         TYPE: Input
 VARIABLES DESCRIPTION:   VPID = VA Person ID.  
VARIABLES: $$IEN                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns the internal entry number (DUZ) of the New
 Person (#200) file entry.  
  DATE ACTIVATED: MAY 26, 2007

NUMBER: 4575                            IA #: 4575
  DATE CREATED: APR 18, 2006            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUPSQRY
  NAME: XUPSQRY API                     ID: XUPSQRY
 GENERAL DESCRIPTION:   This API provides the functionality to query the New
 Person (#200) file.  The calling application may query the New Person (#200)
 file by using either the VPID of the requested entry or part or all of a last
 name.  Other optional parameters may be passed to the call as additional
 filters.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN1(RESULT,XUPSVPID,XUPSLNAM,...)
 COMPONENT DESCRIPTION:   Format of call is: 
  
 D EN1^XUPSQRY(RESULT,XUPSVPID,XUPSLNAM,XUPSFNAM,XUPSSSN, 
 XUPSPROV,XUPSSTN,XUPSMNM,XUPSDATE) 
VARIABLES: XUPSVPID                     TYPE: Input
 VARIABLES DESCRIPTION:   Contains the VPID (VA Person ID) for the requested
 user.  Either VPID or last name are required.  
VARIABLES: XUPSLNAM                     TYPE: Input
 VARIABLES DESCRIPTION:   Contains all or part of a last name.  A last name or
 VPID are required input variables.  
VARIABLES: XUPSFNAM                     TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter set to null or the full or partial
 first name.  
VARIABLES: XUPSSSN                      TYPE: Input
 VARIABLES DESCRIPTION:   Value set to null or contains the 9 digits of the
 Social Security Number.  
VARIABLES: XUPSPROV                     TYPE: Input
 VARIABLES DESCRIPTION:   Optional input parameter set to null or "P".  If set
 to "P", screesn for providers (person with active user class).  
VARIABLES: XUPSSTN                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter set to null or station number.  
VARIABLES: XUPSMNM                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter set to maximum number of entries
 (1-50) to be returned.  Defaults to 50.  
VARIABLES: XUPSDATE                     TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter contains the date used to
 determine if person class is active.  Defaults to current date.  
VARIABLES: TMP($J,"XUPSQRY"             TYPE: Output
 VARIABLES DESCRIPTION:   Results are returned in a global array: 
  
      ^TMP($J,"XUPSQRY",1) - 1 if found, 0 if not found 
      ^TMP($J,"XUPSQRY",n,0) - VPID^IEN^Last Name~First Name~ 
                               Middle Name^SSN^DOB^SEX^ 
      ^TMP($J,"XUPSQRY",n,1) - Provider Type^ 
      ^TMP($J,"XUPSQRY",n,2) - Provider Classification^ 
      ^TMP($J,"XUPSQRY",n,3) - Provider Area of Specialization^ 
      ^TMP($J,"XUPSQRY",n,4) - VA CODE^X12 CODE^Specialty Code^ 
                               end-of-record character "|"| 
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4576                            IA #: 4576
  DATE CREATED: DEC 22, 2004
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  CUSTODIAL ISC: Chicago                USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMRCAU
  NAME: FIM REQUESTING USER CONSULT PERMISSIONS
  ID: GMRCAU                            STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$VALID(var1)
 COMPONENT DESCRIPTION:   This component will check each one of the following
 fields to determine if a user has permission to complete a consult for a
 specific consult service: 
      
  Update users W/O notifications(123.3) 
  Administrative Update Users(123.33) 
  Update Teams W/O notifications(123.31) 
  Administrative Update Teams(123.34) 
  Update User Classes W/O Notifs(123.35) 
  Service Individual to Notify (123.08) 
  Service Teams to Notify(123.1) 
      
 within file 123.5 
VARIABLES: var1                         TYPE: Input
 VARIABLES DESCRIPTION:   Consult Service IEN for file 123.5 
VARIABLES: $$VALID                      TYPE: Output
 VARIABLES DESCRIPTION:   This function will return : 
  0 = not an update user 
  2 = update user 
  3 = administrative update user 
  4 = admin AND update user 
  5 = IFC coordinator 

NUMBER: 4577                            IA #: 4577
  DATE CREATED: DEC 14, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: DIC(0)
 GENERAL DESCRIPTION:   FileMan determines if it can "talk" to the user if the
 variable DIC(0) contains the letter "E".  
  STATUS: Active
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland
 SUBSCRIBING DETAILS:   Kernel: 
  Where: Whole File Screen on NEW PERSON(#200) file 
  Routine: XUSER 
  API: SCR200() 
  Usage: I $G(DIC(0))'["E" Q 1 

NUMBER: 4578                            IA #: 4578
  DATE CREATED: DEC 14, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Controlled Subscription
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: DINDEX
 GENERAL DESCRIPTION:   When DIC is being used to search the indexes for user
 matches, the local variable DINDEX reflects the current index that is being
 searched.  
  STATUS: Active
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland
 SUBSCRIBING DETAILS:   Kernel: 
  Where: Whole File Screen on NEW PERSON(#200) file 
  Routine: XUSER 
  API: SCR200() 
  Usage: ; Test to see if index being searched is SSN 
         I $G(DINDEX)'="SSN" Q 1 

NUMBER: 4579                            IA #: 4579
  FILE NUMBER: 200                      GLOBAL ROOT: DD(200,0,'SCR'
  DATE CREATED: DEC 15, 2004            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DD(200,0,'SCR')                 ID: DD(200,0,'SCR'
 GENERAL DESCRIPTION:   This is a one time IA for patch XU*8*373 to set the
 whole file screen code.  The patch code is as follows: 
  
 XU8P373 ;SFISC/SO- Add Whole File Screen to file 200 ;5:50 AM  13 Dec 
         2004 
        ;;8.0;KERNEL;**373**;Jul 10, 1995 
        ; IA # 4579 
        ; Test for file header node 
        I '$D(^VA(200,0))#2 D MES^XPDUTL("NEW PERSON(#200) file is mis 
         sing it's File Header node.") Q 
        ; Test header node $P#2 for proper construction 
        I +$P(^VA(200,0),U,2)'=200 D MES^XPDUTL("The second piece of N 
         EW PERSON(#200) file is not correct.") Q 
        ; Add the Whole File Screen 
        S ^DD(200,0,"SCR")="I $$SCR200^XUSER" 
        ; Add Screen flag to file header if not already there 
        I $P(^VA(200,0),U,2)'["s" S $P(^VA(200,0),U,2)=$P(^VA(200,0),U 
         ,2)_"s" 
        ;
        D MES^XPDUTL("Added Screen to NEW PERSON(#200) file.") 
        Q 
  STATUS: Active
SUBSCRIBING PACKAGE: KERNEL             ISC: Oakland

NUMBER: 4580                            IA #: 4580
  DATE CREATED: APR 13, 2007            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSIVUTL
  NAME: VALIDATE DOW SCHEDULES          ID: PSIVUTL
 GENERAL DESCRIPTION:   The purpose of this agreement is to grant access to the
 Inpatient Medications V. 5.0 day-of-week schedule validator.  
  STATUS: Active
KEYWORDS: PSIVUTL
COMPONENT/ENTRY POINT: $$DOW
VARIABLES: SCHED                        TYPE: Input
 VARIABLES DESCRIPTION:   Schedule being validated.  
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  DATE ACTIVATED: JUL 10, 2007

NUMBER: 4581                            IA #: 4581
  FILE NUMBER: 192.1                    GLOBAL ROOT: RTV(
  DATE CREATED: DEC 30, 2004            CUSTODIAL PACKAGE: RECORD TRACKING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: MAS/X-RAY RECORDS REQUEST FILE  ID: RTV(
GLOBAL REFERENCE: RTV(192.1,.06
FIELD NUMBER: .06                       FIELD NAME: APPOINTMENT CANCELLED?
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: RTV(192.1,'ARAD'
FIELD NUMBER: .05
  FIELD NAME: PRIOR X-RAY RESULTS TO CLINIC?
  ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This file holds the patient records requested for the
 scheduling appointment.  
  
 This file replaces the Record Tracking fields found in the PATIENT (#44.003) 
 sub-file of the HOSPITAL LOCATION (#44) file.  
  STATUS: Active
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Scheduling needs direct global access to the "ARAD"
 cross-reference node and the 'CANCELLED APPOINTMENT?" field.  

NUMBER: 4582                            IA #: 4582
  DATE CREATED: JAN 06, 2005
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: TIUSRVT2 GETTMPLT RPC
 GENERAL DESCRIPTION:   This RPC is invoked from the CPRS Delphi template code. 
 That CPRS templating code is being encapsulated in v25 of CPRS.  The
 encapsulated code is made available to other applications.  This RPC is
 invoked from within that templating Delphi code.  
  STATUS: Active
SUBSCRIBING PACKAGE: DENTAL             ISC: Hines
 SUBSCRIBING DETAILS:   The encapsulated Delphi code for CPRS templating
 functions is made available to Dental (and other) applications for those
 applications to incorporate that Delphi code within their own GUI application. 
  
 This integration agreement allows those applications to subscribe to this RPC. 
 

NUMBER: 4583                            IA #: 4583
  DATE CREATED: FEB 16, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Routine                         ROUTINE: GMVHDR
  NAME: GMVHDR                          ID: GMVHDR
 GENERAL DESCRIPTION:   This Integration Agreement supports the VistA Data
 Extraction Framework (VDEF) package.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$EN(GMVIEN)
VARIABLES: GMVIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   An internal entry number for a record in the GMRV
 VITAL MEASUREMENT (#120.5) file.  
VARIABLES: $$EN                         TYPE: Output
 VARIABLES DESCRIPTION:   Output: A string of data where: 
  
  piece 1 = (#.01) DATE/TIME VITALS TAKEN (internal) 
  piece 2 = (#.02) PATIENT (internal) 
  piece 3 = (#.03) VITAL TYPE (external) 
  piece 4 = (#.04) DATE/TIME VITALS ENTERED (internal) 
  piece 5 = (#.05) HOSPITAL LOCATION (internal) 
  piece 6 = (#.06) ENTERED BY (internal) 
  piece 7 = (#.03) VITAL TYPE (internal) 
  piece 8 = (#1.2) RATE 
  piece 9 = UNITS (value is computed by this routine) 
  piece 10 = (#1.4) SUPPLEMENTAL O2 (internal) 
  piece 11 = (#2) ENTERED IN ERROR (internal) 
  piece 12 = (#3) ERROR ENTERED BY (internal) 
  piece 13 = (#4) REASON ENTERED IN ERROR (multiple) (external) 
                  Values are separated by a tilde (~).  
  piece 14 = (#5) QUALIFIER (multiple) (external) 
                  Values are separated by a tilde (~).  
  
 Returns a null value if the entry does not exist.  
  
   Example: 
   > S GMVIEN=7599 
   > W $$EN^GMVHDR(GMVIEN) 
   > 3040527.1137^22^TEMPERATURE^3040527.113849^87^547^2^98.8^F^^YES^547^ 
     2-INCORRECT READING^ORAL 
SUBSCRIBING PACKAGE: VISTA DATA EXTRACTION FRAMEWORK

NUMBER: 4584                            IA #: 4584
  GLOBAL ROOT: TMP('PXRHM',$J,          DATE CREATED: DEC 28, 2004
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PXRHM used in TMP global
  ID: TMP('PXRHM',$J,
 GENERAL DESCRIPTION:   The ^TMP("PXRHM",$J, global has been historically used
 in PCE and is also used by other packages now for the same purpose.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: HEALTH SUMMARY
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 4585                            IA #: 4585
  DATE CREATED: DEC 29, 2004            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: XM-MESS
 GENERAL DESCRIPTION:   Because two jobs are being tasked off, the info in
 ^TMP("XM-MESS" is being saved so that after the first job is queued and ZTLOAD
 cleans-up ^TMP("XM-MESS",$J), it can be recreated for the second task job.  
  
 Any output from both jobs ends up as separate messages.  If the output from
 the SORT is not needed the print job could be tasked first but not scheduled
 and then the sort could be scheduled.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 4586                            IA #: 4586
  FILE NUMBER: 811.8                    GLOBAL ROOT: PXD(811.8,
  DATE CREATED: JAN 03, 2005            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: READ OF REMINDER EXCHANGE FILE  ID: PXD(811.8,
GLOBAL REFERENCE: PXD(811.8
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: ..03                      FIELD NAME: DATE PACKED
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the date and time the reminder was orginally
 packed. When a packed reminder is 
 GENERAL DESCRIPTION:   This IA will allow HS to do a FileMan read on the
 Reminder Exchange file, #811.8.  
  STATUS: Active
KEYWORDS: 811.8
KEYWORDS: PXRM
KEYWORDS: REMINDER EXCHANGE
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City

NUMBER: 4587                            IA #: 4587
  DATE CREATED: JAN 06, 2005            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  CUSTODIAL ISC: Salt Lake City         USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PXRMGECV                     NAME: 4587
  ID: PXRMGECV
 GENERAL DESCRIPTION:   This is an API call used to return Health Factor
 Information in a TMP array about a patient for a given dated range.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Health Summary
KEYWORDS: PXRMGECV
COMPONENT/ENTRY POINT: E(ARY,BDT,EDT,CHK,DFNONLY)
 COMPONENT DESCRIPTION:   This entry point allows callers to receive a group of
 Health Factors that are grouped together based on a Geriatric Extended Care
 session.  
VARIABLES: ARY                          TYPE: Input
 VARIABLES DESCRIPTION:   This is set to the letter "HS" that stand for Health
 Summary and is used as a subscript in the TMP array which will be returned.  
VARIABLES: FIN                          TYPE: Input
 VARIABLES DESCRIPTION:   0=unfinished referrals 1=finished referrals 2=both
 finished and unfinished referrals ""= finished 
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Beginning Date in FileMan format. (i.e. 3020509) 
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   End date in FileMan format (i.e. 3030609) 
VARIABLES: CHK                          TYPE: Input
 VARIABLES DESCRIPTION:   This is as check as to how to check the dates in the
 referral.  S=use the start of the referral.  F=use the finished date of the
 referral.  
  
VARIABLES: DFNONLY                      TYPE: Input
 VARIABLES DESCRIPTION:   0=find the information on all patients in the date
 range.  234=find the information on the patient with a DFN of 234.  
VARIABLES: TMP(PXMRGEC,$J,              TYPE: Output
 VARIABLES DESCRIPTION:   The Temp Array to which will house the returned data. 
 TMP("PXRMGEC",$J,"HS",CNTRF,DFN,DATE,VDT,CAT,DATEV,DA)="" CNTREF=Count or
 Numbering for the referral, DFN = Patient IEN, DATE = Starting date of the
 referral, VDT = Finished date of the referral, CAT = Health Factor Category
 IEN, DATEV = Date that each dialog referral was done, DA =Internal Entry
 Number of each Health Factor.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY     ISC: Salt Lake City
 SUBSCRIBING DETAILS:   Heath Summary calls this routine to get Health Factor
 information to be displayed in a Health Summary.  

NUMBER: 4588                            IA #: 4588
  DATE CREATED: JAN 11, 2005            CUSTODIAL PACKAGE: IMAGING
  CUSTODIAL ISC: Washington             USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: MAGMC2CP                     NAME: Imaging's API for CP
  ID: MAGMC2CP
 GENERAL DESCRIPTION:   Imaging grants Clinical Procedures permission to call
 routine MAGMC2CP.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAGMC2CP
COMPONENT/ENTRY POINT: TIU
 COMPONENT DESCRIPTION:   This module will re-point an image's existing
 Medicine report entry to a TIU report. Both the image entry and the TIU report
 entry will be updated with the correct TIU/image pointer. 
  
 Passed into this module will be the Image Internal Entry Number (IEN) to be
 updated, the Medicine Report IEN and the TIU note IEN which replaces the
 Medicine report pointer.  
VARIABLES: MODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Boolean value: 0:Test mode, 1:Real mode 
VARIABLES: VP                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to Medicine file report entry that is being
 converted.  The calling application should validate this number before
 sending.  
VARIABLES: TIUEN                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of a TIU note; calling application should
 validate this number before sending.  
VARIABLES: IP                           TYPE: Input
 VARIABLES DESCRIPTION:   The image's IEN in file 2005.  
VARIABLES: $$TIU(MODE,VP,TIU,IP)        TYPE: Output
 VARIABLES DESCRIPTION:   An extrinsic function that returns the success of the
 call and additional information on the results.  
  
 Example of call S X=$$TIU^MAGMC2CP(MODE,VP,TIUE,IP) See above documentation on
 passing variables.  
  
 Possible results: -1^description of error 
  
 0^No Action - No conversion took place for the entry.  
  
 1^Success message - The image's report pointer was re-pointed to the TIU entry
 sent. 
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  ISC: Hines
 SUBSCRIBING DETAILS:   Imaging provides an Application Programmer Interface
 (API) that will enable the Clinical Procedure conversion application to
 re-point the image records from Medicine reports to the new TIU documents
 generated by the CP conversion application. 

NUMBER: 4589                            IA #: 4589
  DATE CREATED: FEB 03, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4589-A
  ORIGINAL NUMBER: 4589
 GENERAL DESCRIPTION:   The Health Revenue Center (HRC) will be using a special
 telnet feature in CAPRI-Remote to view patient data across all Vista Systems. 
 They need access to the menu options listed in this IA in order to review
 various records for any given patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HRC
KEYWORDS: AMIE
KEYWORDS: DVB
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Usage of: 
  
  XUSESIG CLEAR 
  XQDISPLAY OPTIONS 
  XQSHOKEY 
  XUINQUIRE 
  XUSERINQ 
  

NUMBER: 4590                            IA #: 4590
  DATE CREATED: FEB 03, 2005            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4589-B
  ORIGINAL NUMBER: 4589
 GENERAL DESCRIPTION:   The Health Revenue Center (HRC) will be using a special
 telnet feature in CAPRI-Remote to view patient data across all Vista Systems. 
 They need access to the menu options listed in this IA in order to review
 various records for any given patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AMIE
KEYWORDS: HRC
KEYWORDS: DVB
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Usage of: 
  
  RCDP BILL PROFILE 
  RCDP CLAIMS MATCH 
  RCDP EXTENDED CHECK/CC SEARCH 
  PRCA PAYMENT TRANS HISTORY 
  PRCAC PROFILE 
  PRCA TRANS HISTORY 
  PRCAY FULL ACCOUNT PROFILE 
  PRCA VEN BIL 
  PRCA ACCOUNT CHECK 
  PRCAC TR SUSPENDED 
  PRCA DEBTOR COMMENT 
  PRCA BILL STATUS LISTING 
  PRCAC TR RE-ESTABLISH BILL 
  PRCA RCDMC LESSER WITHHOLDING 
  RCBD TRANSACTION STMT HISTORY 
  PRCAC COWC REFER 
  PRCAF ADJ ADMIN 
  PRCA NOTIFICATION PARAMETERS 
  RCDP RECEIPT PROCESSING 
  RCDP LIST OF RECEIPTS REPORT 
  RCDP SUMMARY 215 REPORT 
  RCDPE EDI LOCKBOX MENU 
  PRCA BIL AGENCY 
  PRCAF U ADMIN.RATE 
  
  DATE ACTIVATED: JUN 08, 2010

NUMBER: 4591                            IA #: 4591
  DATE CREATED: FEB 04, 2005
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4589-C
  ORIGINAL NUMBER: 4589
 GENERAL DESCRIPTION:   The Health Revenue Center (HRC) will be using a special
 telnet feature in CAPRI-Remote to view patient data across all Vista Systems. 
 They need access to the menu options listed in this IA in order to review
 various records for any given patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AMIE
KEYWORDS: HRC
KEYWORDS: DVB
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Usage of: 
  
 PXCE ENCOUNTER VIEWER 
  

NUMBER: 4592                            IA #: 4592
  DATE CREATED: FEB 03, 2005            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4589-D
  ORIGINAL NUMBER: 4589
 GENERAL DESCRIPTION:   The Health Revenue Center (HRC) will be using a special
 telnet feature in CAPRI-Remote to view patient data across all Vista Systems. 
 They need access to the menu options listed in this IA in order to review
 various records for any given patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AMIE
KEYWORDS: HRC
KEYWORDS: DVB
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Usage of: 
  
  DG CO-PAY TEST VIEW TEST 
  DG MEANS TEST VIEW TEST 
  DG REGISTRATION VIEW 
  DG PATIENT INQUIRY 
  DGPRE PRE-REGISTER OPTION 
  DGFFP FUGITIVE FELON PROGRAM 
  
  DATE ACTIVATED: JUN 08, 2010

NUMBER: 4593                            IA #: 4593
  DATE CREATED: JAN 25, 2005
  CUSTODIAL PACKAGE: ENROLLMENT APPLICATION SYSTEM
  USAGE: Controlled Subscription        TYPE: Other
  NAME: DBIA4589-E                      ORIGINAL NUMBER: 4589
 GENERAL DESCRIPTION:   The Health Revenue Center (HRC) will be using a special
 telnet feature in CAPRI-Remote to view patient data across all Vista Systems. 
 They need access to the menu options listed in this IA in order to review
 various records for any given patient.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: AMIE
KEYWORDS: HRC
KEYWORDS: DVB
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Usage of: 
  
 EAS GMT THRESHOLDS LOOKUP 
  

NUMBER: 4594                            IA #: 4594
  DATE CREATED: JAN 25, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4589-F
  ORIGINAL NUMBER: 4589
 GENERAL DESCRIPTION:   The Health Revenue Center (HRC) will be using a special
 telnet feature in CAPRI-Remote to view patient data across all Vista Systems. 
 They need access to the menu options listed in this IA in order to review
 various records for any given patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HRC
KEYWORDS: AMIE
KEYWORDS: DVB
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Usage of: 
  
  IBCN VIEW PATIENT INSURANCE 
  IB MT PROFILE 
  IBJ THIRD PARTY JOINT INQUIRY 
  IB RX INQUIRE 
  IB LIST ALL BILLS FOR PAT 
  IB OUTPUT FULL INQ BY BILL NO 
  IBT OUTPUT CLAIM INQUIRY 
  IB ECME BILLING EVENTS 
  IB RX HARDSHIP 
  
  DATE ACTIVATED: FEB 15, 2005

NUMBER: 4595                            IA #: 4595
  DATE CREATED: FEB 10, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4589-G
  ORIGINAL NUMBER: 4589
 GENERAL DESCRIPTION:   The Health Revenue Center (HRC) will be using a special
 telnet feature in CAPRI-Remote.  This allows a user to be automatically logged
 into the local VistA system and provides access to the site's regular VistA 
 functionality.  The HRC requires access to the menu options listed in this 
 Integration Agreement in order to access various records for a given patient. 
  
 HRC First Party Call Center contact representatives will use the HRC Pharmacy
 Menu [DVBA HRC MENU PHARMACY] option to handle calls from veterans related to
 the Consolidated Co-payment Processing Center (CCPC) billing statements.  The
 menu option will be available through the CAPRI application, which provides
 local common service to VistA for HRC CAPRI remote users.  Users of the HRC
 Pharmacy Menu [DVBA HRC MENU PHARMACY] option will typically be licensed and
 registered personnel (i.e. pharmacists and pharmacy technicians).  
  
 NOTES 
 ======================================================================
   * The Reset Copay Status/Cancel Charges [PSOCP RESET COPAY STATUS] 
     and Reset Copay Status List Manager [PSOCP RESET COPAY STATUS LM] 
     options may be used to change the patients Copay.  
  
   * Pharmacy Benefits Management endorses the addition of the Patient 
     Prescription Processing [PSO LM BACKDOOR ORDERS] to the HRC Pharmacy 
     Menu [DVBA HRC MENU PHARMACY] menu option, with the understanding 
     that HRC users will not use the option to alter existing Outpatient 
     Pharmacy records. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HRC
KEYWORDS: AMIE
KEYWORDS: DVB
KEYWORDS: CAPRI
KEYWORDS: DVBA
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Usage of the following options: 
  
     PSOCP RESET COPAY STATUS 
     PSOCP RESET COPAY STATUS LM 
     PSO P 
     PSO VIEW 
     PSO LM BACKDOOR ORDERS 
     PSO HRC PROFILE/REFILL 
  DATE ACTIVATED: JUL 27, 2010

NUMBER: 4596                            IA #: 4596
  DATE CREATED: JAN 26, 2005            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUP                          NAME: Envoke ASKDUZ - Routine XUP
  ID: XUP
 GENERAL DESCRIPTION:   Envoke ASKDUZ^XUP in routine DII if DUZ is undefined.  
  STATUS: Active
COMPONENT/ENTRY POINT: ASKDUZ
 COMPONENT DESCRIPTION:   Usage Code: Routine: DII [snip] 
         I '+$G(DUZ),$D(^VA(200,0))#2 D  I '+$G(DUZ) W 
 $C(7),!,$$EZBLD^DIALOG(7005),! Q 
         . ;If ASKDUZ^XUP avainable use it first 
         . I $L($T(ASKDUZ^XUP)) N DIR,DIRUT,DUOUT,DTOUT D  
 Q:($D(DUOUT)!$D(DTOUT)) 
         [snip] 
         .. D ASKDUZ^XUP 
         .. Q [snip] 
  
 Example usage: Failure: VCD,FMA>D P^DI 
  
  
 VA FileMan 22.0 
  
 Access Code: 
  
 Select NEW PERSON NAME: <rtn> You must have a valid DUZ! 
  
 Sucessful: VCD,FMA>D P^DI 
  
  
 VA FileMan 22.0 
  
 Access Code: 
  
  
 Select OPTION: 
SUBSCRIBING PACKAGE: 1                  ISC: Oakland
 SUBSCRIBING DETAILS:   Routine: XUP; Line Label: ASKDUZ is the section of code
 when at the programmer level that validates the user if the local variable DUZ
 is undefined.  Example: >D ^XUP 
  
 Setting up programmer environment This is a TEST account.  
  
 Access Code: 

NUMBER: 4597                            IA #: 4597
  FILE NUMBER: 42.6                     GLOBAL ROOT: DGAM(334
  DATE CREATED: FEB 04, 2005            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4597                        ID: DGAM(334
GLOBAL REFERENCE: DGAM(334,'B',
GLOBAL REFERENCE: DGAM(334,D0,'SE',D1,0
FIELD NUMBER: 42.6001                   FIELD NAME: SEGMENT
FIELD NUMBER: .01                       FIELD NAME: SEGMENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGAM(334,D0,'SE',D1,'D',D2,0
FIELD NUMBER: 42.61                     FIELD NAME: DIVISION
FIELD NUMBER: .01                       FIELD NAME: DIVISION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 12                        FIELD NAME: PATIENT DAYS OF CARE
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 21                        FIELD NAME: PATIENT DAYS OF CARE ( >45)
  LOCATION: 0;24                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham
 SUBSCRIBING DETAILS:   Pharmacy Benefits Management extracts monthly AMIS data
 from the SEGMENT and DIVISION fields within file #(42.6). PATIENT DAYS OF CARE
 and PATIENT DAYS OF CARE (>45) are sent to PBM and compiled into statistical
 records.  

NUMBER: 4598                            IA #: 4598
  FILE NUMBER: 42.7                     GLOBAL ROOT: DGAM(345
  DATE CREATED: FEB 07, 2005            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4598                        ID: DGAM(345
GLOBAL REFERENCE: DGAM(345,'B',
GLOBAL REFERENCE: DGAM(345,D0,'SE',D1,0
FIELD NUMBER: 42.701                    FIELD NAME: SEGMENT
FIELD NUMBER: .01                       FIELD NAME: SEGMENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGAM(345,D0,'SE',D1,'D',D2,0
FIELD NUMBER: 42.702                    FIELD NAME: DIVISION
FIELD NUMBER: .01                       FIELD NAME: DIVISION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: PATIENT DAYS OF CARE
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
  ISC: Birmingham
 SUBSCRIBING DETAILS:   Pharmacy Benefits Management extracts monthly AMIS data
 from the SEGMENT and DIVISION fields within file #(42.7).  PATIENT DAYS OF
 CARE are sent to PBM and compiled into statistical records.  

NUMBER: 4599                            IA #: 4599
  FILE NUMBER: 440                      GLOBAL ROOT: PRC(440,
  DATE CREATED: FEB 07, 2005            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VENDOR FILE READ
  ID: PRC(440,
GLOBAL REFERENCE: PRC(440,
FIELD NUMBER: 8.3                       FIELD NAME: BUSINESS TYPE (FPDS)
  LOCATION: 2;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 18.3                      FIELD NAME: DUN & BRADSTREET #
  LOCATION: 7;12                        ACCESS: Read w/Fileman
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
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Hines

NUMBER: 4600                            IA #: 4600
  DATE CREATED: FEB 08, 2005
  CUSTODIAL PACKAGE: ENROLLMENT APPLICATION SYSTEM
  CUSTODIAL ISC: Albany                 USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: EASEZPDG                     NAME: 1010EZ/EZR PRINT
  ID: EASEZPDG
 GENERAL DESCRIPTION:   Allow registration routines to call entry points to
 print 1010EZ or 1010EZR.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 1010EZ
KEYWORDS: 1010EZR
COMPONENT/ENTRY POINT: $$ENEZ(DFN,EASMTIEN)
 COMPONENT DESCRIPTION:   Extrinsic function for printing 1010EZ.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The Internal Entry Number of the patient.  
VARIABLES: $$ENEZ                       TYPE: Output
 VARIABLES DESCRIPTION:   The task # of the print job.  
VARIABLES: EASMTIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   Optional.  The IEN from 408.31 (Means Tests). 
 Defaults to most current test.  
COMPONENT/ENTRY POINT: $$ENEZR(DFN,EASMTIEN)
 COMPONENT DESCRIPTION:   Extrinsic function for printing 1010EZR.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The Internal Entry Number of the patient.  
VARIABLES: $$ENEZR                      TYPE: Output
 VARIABLES DESCRIPTION:   The task # of the print job.  
VARIABLES: EASMTIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   Optional.  The IEN from 408.31 (Means Tests). 
 Defaults to most current test.  
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Tag for execution as a tasked job (i.e., from
 ZTLOAD).  
VARIABLES: ZTSAVE                       TYPE: Input
 VARIABLES DESCRIPTION:   
  EASDFN   Input 
    The internal entry Number of the patient. Required.  
  ZUSR     Input 
    The internal entry number of the user.  Required.  
  EASFLAG  Input 
    'EZR' to print the 1010EZR, else prints 1010EZ.   Optional.  Defaults to
 EZ.  
  EASMTIEN Input 
    The IEN from 408.31 (Means Tests).  Optional.  Defaults to most current
 test.  
SUBSCRIBING PACKAGE: REGISTRATION       ISC: Albany

NUMBER: 4601                            IA #: 4601
  DATE CREATED: JUL 19, 2005
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  ROUTINE: PXXDPT                       NAME: PXXDPT - File 9000001
  ID: PXXDPT
 GENERAL DESCRIPTION:   My patch originated because user's were unable to
 perform the check out process on certain encounters.  We couldn't find the
 source of the problem but we found out how to fix the encounters so that the
 check out could be done. (The main problem was that you had Appt's pointing to
 an encounter that did not have a pointer to a visit. Somehow the visit entry 
 did not get created along with the encounter as it should have.) 
  
 Now, during site testing we found some that still couldn't be checked out. 
 This was because of bad pointers in the IHS/Patient file (9000001).  
  
 After fixing this file, everything checked out properly.  When we found that,
 after looking into further we found that this patient file was also causing
 the initial problem of the visit not being created when the encounter is
 created.  I then found some existing routine (PXXDPT)  that builds/re-build
 this patient file.  
  
 So, I've changed my fix utility (PXDELENC/PXDELFIX) to repair or build the
 entries in the IHS/Patient file (9000001) also.  And, here's where to
 agreement comes into play. I want to put a check in the SD routine SDCO1 to
 check this IHS/Patient file (9000001) file and if it needs repaired go ahead
 and repair just before the check out process so that the check out would then
 run with out issues.  
  
 May agreement will be between SD and PCE.  My routine is PXDELFIX and there is
 a FIXIHS line tag that does a couple calls to the PXXDPT routine.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CHECK
VARIABLES: DA                           TYPE: Input
COMPONENT/ENTRY POINT: GETSSN
VARIABLES: PX                           TYPE: Input
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 4602                            IA #: 4602
  DATE CREATED: FEB 07, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCEF2
  NAME: GET CURRENT INSURANCE           ID: IBCEF2
 GENERAL DESCRIPTION:   As part of the IB/AR data extract, AR must pull the
 current insurance IEN for a bill in order to determine the Payer.   Routine
 RCXVDC3 uses the IB function $$CURR^IBCEF2(RCXVD0), where RCXVD0 is the
 internal number of the bill to get the internal number of the insurance file. 
 This is then used to extract the payer from the insurance file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$CURR
VARIABLES: RCXVD0                       TYPE: Input
 VARIABLES DESCRIPTION:   Internal number of the bill.  
VARIABLES: RCXVINS                      TYPE: Output
 VARIABLES DESCRIPTION:   Internal number of the insurance file.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4603                            IA #: 4603
  FILE NUMBER: 361                      GLOBAL ROOT: IBM(361,
  DATE CREATED: FEB 07, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FILE 361
  ID: IBM(361,
GLOBAL REFERENCE: IBM(361,'B',
GLOBAL REFERENCE: IBM(361,D0,0
FIELD NUMBER: .03                       FIELD NAME: MESSAGE SEVERITY
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   As part of the AR/IB data extract, AR needs to
 determine whether a claim has had any MRA rejection messages.  These messages
 are stored in file 361.   Routine RCXVDC3 uses the "B" X-Ref of that file in
 order to determine all messages for a particular bill.  It then checks piece 3
 of the '0' node to determine if the message had a 'rejected' status and adds 
 one to the count if it is rejected.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4604                            IA #: 4604
  FILE NUMBER: 365.12                   GLOBAL ROOT: IBE(365.12,
  DATE CREATED: FEB 07, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FILE 365.12
  ID: IBE(365.12,
GLOBAL REFERENCE: IBE(365,D0,0
FIELD NUMBER: .01                       FIELD NAME: PAYER NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: VA NATIONAL ID
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   As part of the AR/IB data extract, the PAYER NAME and
 the VA NATIONAL ID needs to be extracted from file 365.12 for transmission to
 the ARC.  RCXVDC3 uses a direct global read to extract this information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4605                            IA #: 4605
  GLOBAL ROOT: DD(123,                  DATE CREATED: FEB 08, 2005
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: GLOBAL READ OF DD(123
  ID: DD(123,
GLOBAL REFERENCE: DD(123,1,1
GLOBAL REFERENCE: DD(123,3,1
GLOBAL REFERENCE: DD(123,8,1
 GENERAL DESCRIPTION:   GMRC*3*41 proposes to delete 3 MUMPS style
 cross-references and replace them with a NEW-STYLE compound index. This
 approach should increase the efficiency and reliability of the
 cross-reference.  
  
 To insure the deletion of the proper cross-references "AE", "AE1" and "AE2",
 Consult/Request Tracking will loop through: 
  
 ^DD(123,1,1, ^DD(123,3,1, ^DD(123,8,1, 
  
 in order to locate the number of the cross reference to delete via 
 DELIX^DDMOD.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  ISC: Salt Lake City

NUMBER: 4606                            IA #: 4606
  DATE CREATED: FEB 09, 2005
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  CUSTODIAL ISC: Salt Lake City         USAGE: Private
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  NAME: REINDEX APC CROSS REFERENCE IN FILE 120.8
 GENERAL DESCRIPTION:   During the course of data updates for the National Drug
 file, the names some VA drug classes (entries in the VA DRUG CLASS file
 (#50.605)) are changed.  This causes the APC cross reference in file 120.8 to
 be incorrect.  To remedy this problem, we request permission to reindex this
 cross reference as part of data updates.  Specifically, we ask to insert the
 following code at the end of the post-install routine 
  
        ;
 REINDEX ;Make sure APC xref is correct 
        Q:$T(EN2^GMRAUIX0)']"" 
        N SUB,DA,DIK,GMRAIEN,CLASS 
        S SUB=0 F  S SUB=$O(^GMR(120.8,SUB)) Q:'+SUB  I $D(^GMR(120.8,SUB,3)) D 
        .S GMRAIEN=+$P($G(^GMR(120.8,SUB,0)),U) Q:'GMRAIEN 
        .S CLASS="" F  S CLASS=$O(^GMR(120.8,"APC",GMRAIEN,CLASS)) Q:CLASS="" 
 K 
         ^GMR(120.8,"APC",GMRAIEN,CLASS,SUB) 
        .S DA(1)=SUB 
        .S DIK="^GMR(120.8,DA(1),3," 
        .S DIK(1)=".01^ADRG3" 
        .D ENALL^DIK ;Reset the drug class xref 
        Q 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
  ISC: Birmingham

NUMBER: 4607                            IA #: 4607
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: VBECS
  CUSTODIAL ISC: Chicago                USAGE: Private
  TYPE: Remote Procedure                DBIC APPROVAL STATUS: APPROVED
  NAME: VBECS ACCESSION AREA LOOKUP
  REMOTE PROCEDURE: VBECS ACCESSION AREA LOOKUP
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 a list of VistA Lab Blood Bank accession areas to be associated with a
 division in VBECS.  The association is used by the Lab Workload reporting
 process for VBECS.  
  
 RPC Details: 
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4608                            IA #: 4608
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VBECS BLOOD BANK USER LOOKUP
  REMOTE PROCEDURE: VBECS BLOOD BANK USER LOOKUP
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 a list of VistA Blood Bank users to the gov.va.med.vbecs rehosted Blood Bank
 application.  
  
 RPC Details: 
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4609                            IA #: 4609
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VBECS DIVISION LOOKUP
  REMOTE PROCEDURE: VBECS DIVISION LOOKUP
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 a list of all VistA Divisions (Institutions) associated with a Medical Center. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4610                            IA #: 4610
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VBECS HCPCS CODES LOOKUP
  REMOTE PROCEDURE: VBECS HCPCS CODES LOOKUP
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 a list of Healthcare Common Procedure Code System (HCPCS) codes from the VistA
 CPT file (#81) with a CPT CATEGORY of PATHOLOGY AND LABORATORY SERVICES for 
 use in the rehosted VBECS software.  
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4611                            IA #: 4611
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VBECS LABORATORY TEST LOOKUP
  REMOTE PROCEDURE: VBECS LABORATORY TEST LOOKUP
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 the rehosted VBECS application with a Laboratory Test lookup from the VistA
 Laboratory Test file (#60) for the purpose of associating Lab tests with
 components in the VBECS database.  
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4612                            IA #: 4612
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VBECS LAB TEST RESULTS LOOKUP
  REMOTE PROCEDURE: VBECS LAB TEST RESULTS LOOKUP
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 a list of Laboratory test results for a specific patient during a specific
 date range for the rehosted VBECS application.  
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4613                            IA #: 4613
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VBECS MED PROFILE LOOKUP
  REMOTE PROCEDURE: VBECS MED PROFILE LOOKUP
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 a list of all medications for a patient from the VistA Pharmacy package based
 on a beginning and ending search date.  
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4614                            IA #: 4614
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VBECS LAB ACCESSION UID LOOKUP
  REMOTE PROCEDURE: VBECS LAB ACCESSION UID LOOKUP
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 VBECS with a lookup into the Accession file (#68) for the purpose of
 identifying an existing Specimen UID and Accession number associated with a
 Lab Order Number.  This will facilitate the ability of VBECS to identify
 existing VBECS orders by scanning a barcoded specimen UID, or entering the UID 
 manually, from a specimen received in the Blood Bank.  
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4615                            IA #: 4615
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VBECS WORKLOAD CODES LOOKUP
  REMOTE PROCEDURE: VBECS WORKLOAD CODES LOOKUP
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 a list of workload codes from the WORKOAD CODE file (#64) for use in the
 rehosted VBECS application.  
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4616                            IA #: 4616
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VBECS PATIENT LOOKUP
  REMOTE PROCEDURE: VBECS PATIENT LOOKUP
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 the rehosted VBECS application with a list of specific VistA patient data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4617                            IA #: 4617
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VBECS PROVIDER LOOKUP
  REMOTE PROCEDURE: VBECS PROVIDER LOOKUP
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 the rehosted VBECS application with a list of physicians (providers) in VistA. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4618                            IA #: 4618
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VBECS HOSPITAL LOCATION LOOKUP
  REMOTE PROCEDURE: VBECS HOSPITAL LOCATION LOOKUP
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 the rehosted VBECS application with a list of Hospital Locations for the
 purpose of issuing units to specific locations.  
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4619                            IA #: 4619
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: 769
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4619
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 patient specific and common order entry data to VistA for the purpose of
 creating VBECS orders for blood products and diagnostic tests performed in the
 Blood Bank.  
  
  XML Mapping: 
  
  XML Element.Attribute    VBECS SQL Table.Column or Function 
  _____________________    __________________________________
  Patient.dfn              Patient.VistaPatientId 
  Patient.firstName        Patient.PatientFirstName 
  Patient.lastName         Patient.PatientLastName 
  Patient.abo              fnGetAbo(Patient.PatientGuid) 
  Patient.rh               fnGetRh(Patient.PatientGuid) 
  TransfusionReaction.type TransfusionReactionType.TransfusionReactionTypeText 
  TransfusionReaction.date 
 fnDateTimeConversionToHL7DateTime(PatientTransfusionReaction.NotedDateTim e 
 )
  TransfusionRequirement.modifier 
 PatientTransfusionRequirement.TransfusionRequirementText 
  Antibody.name            AntibodyType.AntibodyTypeName 
  Unit.status              UnitStatus.UnitStatusCode OR 
 DonationType.RestrictionTypeCode 
  Unit.id                  BloodUnit.EyeReadableUnitId 
  Unit.product             ProductType.ProductTypePrintName 
  Unit.location            VamcDivision.DivisionName 
  Unit.expDate             
 fnDateTimeConversionToHL7DateTime(BloodUnitMedia.UnitExpirationDate) 
  Specimen.expDate         
 fnDateTimeConversionToHL7DateTime(PatientSpecimen.SpecimenExpirationDate) 
  Specimen.uid             PatientSpecimen.SpecimenUid 
  Component.name           ComponentClass.ComponentClassShortName 
  Component.id             ComponentClass.CprsOrderableItemId 
  Component.specimen       ComponentClassParameter.SpecimenRequiredIndicator 
  LabTest.id               SpecimenTestThreshold.LabTestId 
  LabTest.name             SpecimenTestThreshold.VistALaboratoryTestName 
  Msbos.name               Msbos.SurgeryName 
  Msbos.threshold          MsbosComponentClass.MaximumSetupUnitQuantity 
  Surgery.name             Msbos.SurgeryName 
  
  Function Description: 
  
  fnGetAbo - This function returns the patient's current ABO Group.  
  fnGetRh - This function returns the patient's current Rh Type.  
  fnDateTimeConversionToHL7DateTime - This function converts a SQL DateTime
 data type to HL7 format.  
  
  
  XML Example: 
  <?xml version="1.0" encoding="utf-8" ?> 
  <BloodBank> 
      <Patient dfn="5000" firstName="One" lastName="VBECSpatient" 
 ssn="000000000" abo=A"" rh="P"> 
          <TransfusionReactions> 
              <TransfusionReaction type="Acute Hemolytic" 
 date="20010101120035-0600" /> 
          </TransfusionReactions> 
          <TransfutionRequirements> 
              <TransfusionRequirement modifier="Washed RBC products"> 
          <Antibodies> 
              <Antibody name="Anti-E" /> 
          </Antibodies> 
          <Units> 
              <Unit status="C" id="04215" product="RBC" location="4E" 
 expDate="20010103115535-0600" /> 
          </Units> 
          <Specimen expDate="20010115115535-0600" uid="1234567890" /> 
      </Patient> 
      <Components> 
          <Component name="RED BLOOD CELLS" id="2" specimen="R"> 
              <LabTests> 
                  <LabTest id="320" name="HGB" /> 
              </LabTests> 
              <MsbosList> 
                  <Msbos name="Esophogectomy" threshold="5" /> 
              </MsbosList> 
          </Component> 
      </Components> 
      <Surgeries> 
          <Surgery name="Esophogectomy" /> 
      </Surgeries> 
  </BloodBank> 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VBECS

NUMBER: 4620                            IA #: 4620
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: 769
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4620
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 VistA applications with a list of Blood Units associated with a patient. 
  
  XML Mapping: 
  
  XML Element.Attribute   VBECS SQL Table.Column or Function 
  _____________________   __________________________________
  
  Patient.dfn             Patient.VistaPatientId 
  Patient.firstName       Patient.PatientFirstName 
  Patient.lastName        Patient.PatientLastName 
  Patient.dob             
 fnPatientDobConversionToFileManDateTime(Patient.PatientGuid) 
  Patient.ssn             Patient.PatientSsn 
  Patient.abo             fnGetAbo(Patient.PatientGuid) 
  Patient.rh              fnGetRh(Patient.PatientGuid) 
  Unit.status             DonationType.RestrictionTypeCode 
  Unit.id                 BloodUnit.EyeReadableUnitId 
  Unit.product            ProductType.ProductTypeName 
  Unit.productCode        BloodProduct.ProductCode 
  Unit.abo                BloodUnitMedia.BloodTypeCode 
  Unit.rh                 BloodUnitMedia.RhFactorCode 
  Unit.volume             BloodUnit.OriginalVolume 
  Unit.dateAssigned       
 fnDateTimeConversionToFileManDateTime(OrderedUnit.SelectedDate) 
  Unit.divisionCode       VamcDivision.DivisionCode 
  Unit.location           IssuedUnit.IssueToLocation 
  Unit.expDate            
 fnDateTimeConversionToFileManDateTime(BloodUnitMedia.UnitExpirationDate) 
  
  fnPatientDobConversionToFileManDateTime - This function returns the patient's
 date of birth in FileMan format based on the patient unique identifier in the
 VBECS database.  
  fnGetAbo - This function returns the patient's current ABO Group.  
  fnGetRh - This function returns the patient's current Rh Type.  
  fnDateTimeConversionToFileManDateTime - This function converts a SQL DateTime
 data type to FileMan format.  
  
  XML Example: 
  <?xml version="1.0" encoding="utf-8" ?> 
  <BloodBank> 
    <Patient dfn="5000" firstName="One" lastName="VBECSpatient" dob="19500101"
 ssn="000000000" abo="A" rh="P" /> 
    <Units> 
      <Unit status="C" id="04215" product="RBC" productCode="E0335" abo="A" 
 rh="P" volumn="250" dateAssigned="20010430115535-0600" divisionCode="589" 
 location="4E" expDate="20010430115535-0600" /> 
    </Units> 
  </BloodBank> 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VBECS

NUMBER: 4621                            IA #: 4621
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: 769
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4621
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 VistA application with a list of Transfusions given to a patient.  
  
  
  XML Mapping: 
  
  XML Element.Attribute            VBECS SQL Table.Column or Function 
  _____________________            __________________________________
  Patient.dfn                      Patient.VistaPatientId 
  Patient.firstName                Patient.PatientFirstName 
  Patient.lastName                 Patient.PatientLastName 
  Patient.dob                      
 fnPatientDobConversionToFileManDateTime(Patient.PatientGuid) 
  Patient.ssn                      Patient.PatientSsn 
  Patient.abo                      fnGetAbo(Patient.PatientGuid) 
  Patient.rh                       fnGetRh(Patient.PatientGuid) 
  Transfusion.date                 
 fnDateTimeConversionToFileManDateTime(PatientTransfusion.TransfusinoEndDat 
 eTime) 
  Transfusion.unitsPooled          BloodUnit.PooledUnitsCount 
  Transfusion.productTypeName      ProductType.ProductTypeName 
  Transfusion.productTypePrintName ProductType.ProductTypePrintName 
  
  
  Function Description: 
  
  fnPatientDobConversionToFileManDateTime - This function returns the patient's
 date of birth in FileMan format based on the patient unique identifier in the
 VBECS database.  
  fnGetAbo - This function returns the patient's current ABO Group. 
  fnGetRh - This function returns the patient's current Rh Type.  
  fnDateTimeConversionToFileManDateTime - This function converts a SQL DateTime
 data type to FileMan format.  
  
  
  XML Example: 
  
  <Bloodbank> 
      <Patient dfn="5000" firstName="One" lastName="VBECSpatient" 
 dob="19500101" ssn="000000000" abo="A" rh="P"> 
          <Transfusions> 
              <Transfusion date="20000101115535-0600" unitsPooled="3" 
 productTypeName="RED BLOOD CELLS" productTypePrintName="RBC" /> 
          </Transfusions> 
      </Patient> 
  </Bloodbank> 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VBECS

NUMBER: 4622                            IA #: 4622
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: 769
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4622
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 VistA applications with a list of Blood Products, or Component Classes, that 
 can be ordered for a patient.  
  
  
  XML Mapping: 
  
  XML Element.Attribute      VBECS SQL Table.Column or Function 
  _____________________      __________________________________
  ComponentClass.name        ComponentClass.ComponentClassName 
  ComponentClass.shortName   ComponentClass.ComponentClassShortName 
  
  
  XML Example: 
  
  <ComponentClasses> 
      <ComponentClass name="RED BLOOD CELLS" shortName="RBC" /> 
      <ComponentClass name="FRESH FROZEN PLASMA" shortName ="FFP" /> 
      <ComponentClass name="CRYOPRECIPITATE" shortName ="CRYO" /> 
      <ComponentClass name="PLATELETS" shortName ="PLT" /> 
      <ComponentClass name="OTHER" shortName ="OTHER" /> 
      <ComponentClass name="WHOLE BLOOD" shortName ="WB" /> 
  </ComponentClasses> 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VBECS

NUMBER: 4623                            IA #: 4623
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: 769
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4623
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 VistA applications with a list of Blood Bank patient diagnostic testing
 results, blood products requested, and blood units associated with a patient.  
  
  
  XML Mapping: 
  ____________
  
  XML Element.Attribute / VBECS SQL Table.Column or Function 
   
  Patient.dfn / Patient.VistaPatientId 
  Patient.firstName / Patient.PatientFirstName 
  Patient.lastName / Patient.PatientLastName 
  Patient.dob / fnPatientDobConversionToFileManDateTime(Patient.PatientGuid) 
  Patient.ssn / Patient.PatientSsn 
  Patient.abo / fnGetAbo(Patient.PatientGuid) 
  Patient.rh / fnGetRh(Patient.PatientGuid) 
  SpecimenTest.printTestName / BloodTestType.BloodTestName 
  SpecimenTest.orderableTestName / OrderableTest.OrderableTestName 
  SpecimenTest.result / TestResult.TestResultText 
  SpecimenTest.testDate / 
 fnDateTimeConversionToFileManeDateTime(SpecimenTest.TestDate) 
  SpecimenTest.cprsOrderId / PatientOrder.OrderGroupNumber 
  SpecimenTest.divisionCode / SpecimenTest.DivisionCode 
  SpecimenTest.enteringTechId / VbecsUser.UserDuz 
  SpecimenTest.requestorId / PatientOrder.OrderingProviderId 
  SpecimenTestComments / InformationMessage.InformationMessageText 
  ComponentRequest.dateRequested / 
 fnDateTimeConversionToFileManDateTime(PatientOrder.orderPlacedDatetime) 
  ComponentRequest.dateWanted / 
 fnDateTimeConversionToFileManDateTime(OrderedComponent.RequiredDatetime) 
  ComponentRequest.unitsRequested / OrderedComponent.RequiredUnitQuantity 
  ComponentRequest.cprsOrderId / PatientOrder.OrderGroupNumber 
  ComponentRequest.componentClassName / ComponentClass.ComponentClassName 
  ComponentRequest.componentClassShortName / 
 ComponentClass.ComponentClassShortName 
  ComponentRequest.requestorId / PatientOrder.OrderingProviderId 
  ComponentRequest.enteredById / PatientOrder.OrderEnteredById 
  Unit.status / UnitStatus.UnitStatusCode 
  Unit.id / BloodUnit.EyeReadableUnitId 
  Unit.product / ProductType.ProductTypePrintName 
  Unit.abo / BloodUnitMedia.BloodTypeCode 
  Unit.rh / BloodUnitMedia.RhFactorCode 
  Unit.divisionCode / BloodUnit.DivisionCode 
  Unit.location / IssuedUnit.LocationIen 
  Unit.expDate / 
 fnDateTimeConversionToFileManDateTime(BloodUnitMedia.UnitExpirationDate) 
  
  
  Function Description: 
  _____________________
  
  fnPatientDobConversionToFileManDateTime - This function returns the patient's
 date of birth in FileMan format based on the patient unique identifier in the
 VBECS database.  
  fnGetAbo - This function returns the patient's current ABO Group. 
  fnGetRh - This function returns the patient's current Rh Type.  
  fnDateTimeConversionToFileManDateTime - This function converts a SQL DateTime
 data type to FileMan format.  
  
  
  XML Example: 
  ____________
  
  <BloodBank> 
      <Patient dfn="5000" firstName="One" lastName="VBECSpatient"
 dob="19500101" ssn="000000000" abo="A" rh="P"> 
          <SpecimenTests> 
              <SpecimenTest printTestName="ABO Interp" 
 orderableTestName="ABO/Rh" result="A" testDate="20030101115535-0600" 
 cprsOrderId="12345" divisionCode="589" enteringTechId="5335" 
 requestorId="3553"> 
                  <SpecimenTestComments></SpecimenTestComments> 
              </SpecimenTest> 
          </SpecimenTests> 
          <ComponentRequests> 
              <ComponentRequest dateRequested="20030101115535-0600" 
 dateWanted="20030102" cprsOrderId="12346" componentClassName="RED BLOOD CELLS"
 componentClassShortName="RBC" requestorId="3553" enteredById="3553" 
 />
          </ComponentRequests> 
          <Units> 
              <Unit status="C" id="04215" product="RBC" abo="A" rh="P" 
 divisionCode="589" location="4E" expDate="20030103115535-0600" /> 
          </Units> 
      </Patient> 
  </BloodBank> 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VBECS

NUMBER: 4624                            IA #: 4624
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: 769
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4624
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 VistA applications with a patient's current ABO Blood Group and Rh Type.  
  
  
  XML Mapping: 
  
  XML Element.Attribute  VBECS SQL Table.Column or Function 
  _____________________  __________________________________
  Patient.dfn            Patient.VistaPatientId 
  Patient.firstName      Patient.PatientFirstName 
  Patient.lastName       Patient.PatientLastName 
  Patient.dob            
 fnPatientDobConversionToFileManDateTime(Patient.PatientGuid) 
  Patient.ssn            Patient.PatientSsn 
  Patient.abo            fnGetAbo(Patient.PatientGuid) 
  Patient.rh             fnGetRh(Patient.PatientGuid) 
  
  
  Function Description: 
  
  fnPatientDobConversionToFileManDateTime - This function returns the patient's
 date of birth in FileMan format based on the patient unique identifier in the
 VBECS database.  
  fnGetAbo - This function returns the patient's current ABO Group. 
  fnGetRh - This function returns the patient's current Rh Type.  
  
  
  XML Example: 
  
  <BloodBank> 
      <Patient dfn="5000" firstName="One" lastName="VBECSpatient" 
 dob="19500101" ssn="000000000" abo="A" rh="P" /> 
  </BloodBank> 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VBECS

NUMBER: 4625                            IA #: 4625
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: 769
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4625
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 VistA applications with a list of antibodies identified for a patient.  
  
  
  XML Mapping: 
  
  XML Element.Attribute   VBECS SQL Table.Column or Function 
  _____________________   __________________________________
  Patient.dfn             Patient.VistaPatientId 
  Patient.firstName       Patient.PatientFirstName 
  Patient.lastName        Patient.PatientLastName 
  Patient.ssn             Patient.PatientSsn 
  Patient.abo             fnGetAbo(Patient.PatientGuid) 
  Patient.rh              fnGetRh(Patient.PatientGuid) 
  Antibody.name           AntibodyType.AntibodyTypeName 
  Antibody.comment        InformationMessage.InformationMessageText 
  
  
  Function Description: 
  
  fnGetAbo - This function returns the patient's current ABO Group. 
  fnGetRh - This function returns the patient's current Rh Type.  
  
  
  XML Example: 
  
  <BloodBank> 
      <Patient dfn="5000" firstName="One" lastName="VBECSpatient" 
 dob="19500101" ssn="000000000" abo="A" rh="P" > 
          <Antibodies> 
              <Antibody name="Anti-E" comment="Unexpected Antibody Detected:
 Preparation of red cell components for transfusion may be delayed due to the
 presence of serum red cell specific antibody(ies), which may require antigen
 negative red cell components. Contact transfusion service for information on
 potential clinical significance and availability of red cell components." /> 
          </Antibodies> 
      </Patient> 
  </BloodBank> 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VBECS

NUMBER: 4626                            IA #: 4626
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: 769
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4626
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 VistA applications with a list of Transfusion Reactions associated with a 
 patient.  
  
  
  XML Mapping: 
  ____________
  
  XML Element.Attribute / VBECS SQL Table.Column or Function 
  
  Patient.dfn / Patient.VistaPatientId 
  Patient.firstName / Patient.PatientFirstName 
  Patient.lastName / Patient.PatientLastName 
  Patient.dob / fnPatientDobConversionToFileManDateTime(Patient.PatientGuid) 
  Patient.ssn / Patient.PatientSsn 
  Patient.abo / fnGetAbo(Patient.PatientGuid) 
  Patient.rh /fnGetRh(Patient.PatientGuid) 
  TransfusionReaction.type / 
 TransfusionReactionType.TransfusionReactionTypeText 
  TransfusionReaction.date / 
 fnDateTimeConversionToFileManDateTime(PatientTransfusionReaction.NotedDate 
 Time) 
  TransfusionReaction.unitId / BloodProduct.EyeReadableUnitId 
  TransfusionReaction.productTypeName / ProductType.ProductTypeName 
  TransfusionReaction.productTypePrintName / ProductType.ProductTypePrintName 
  TransfusionReaction.comment / 
 PatientTransfusionComment.PatientTransfusionCommentText 
  
  
  Function Description: 
  _____________________
  
  fnGetAbo - This function returns the patient's current ABO Group. 
  fnGetRh - This function returns the patient's current Rh Type.  
  fnDateTimeConversionToFileManDateTime - This function converts a SQL DateTime
 data type to FileMan format.  
  
  
  XML Example: 
  ____________
   
  <BloodBank> 
      <Patient dfn="5000" firstName="One" lastName="VBECSpatient" 
 dob="19500101" ssn="000000000" abo="A" rh="P" > 
          <TransfusionReactions> 
              <TransfusionReaction type="Acute Hemolytic" 
 date="20000101113555-0600" unitId="04215" productTypeName="RED BLOOD CELLS"
 productTypePrintName="RBC" comment="The patient is also experiencing severe
 headaches."> 
          </TransfusionReactions> 
      </Patient> 
  </BloodBank> 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VBECS

NUMBER: 4627                            IA #: 4627
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: 769
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4627
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 Blood Bank related workload data to VistA for workload reporting.  
  
  
  XML Mapping: 
  
  XML Element.Attribute       VBECS SQL Table.Column or Function 
  _____________________       __________________________________
  Transaction.id              WorkloadEvent.WorkloadEventGuid 
  Transaction.type            VbecsProcess.TransactionType 
  Transaction.division        WorkloadEvent.DivisionCode 
  Transaction.accessionArea   VamcDivision.AccessionAreaId 
  Transaction.dateTime        
 fnDateTimeConversionToFileManDateTime(WorkloadEvent.WorkloadEventDate) 
  Transaction.status          WorkloadEvent.WorkloadEventStatusCode 
  Workload.code               WorkloadProcess.WorkloadCode 
  Workload.multiplyFactor     WorkloadEvent.WeightMultiplier 
  Patient.dfn                 Patient.VistaPatientId 
  VbecsUser.duz               VbecsUser.UserDuz 
  Lab.accessionNumber         OrderedTest.SpecimenWorkloadUid OR 
 OrderedComponent.SpecimenWorkloadUid 
  Lab.testPerformed           OrderedTest.LabTestId OR 
 OrderedComponent.LabTestId 
  Unit.id                     BloodUnit.UnitProductCode 
  
    Note: 
    Transaction.type is a conditional code where the values can be 
    one of the following depending on the type of workload event being 
 returned.  
       U = Unit 
       P = Patient 
       M = Miscellaneous 
    The WorkloadEventStatusCode is always P for 'Pending Processing'. 
  
  
  Function Description: 
  
  fnDateTimeConversionToFileManDateTime - This function converts a SQL DateTime
 data type to FileMan format.  
  
  
  XML Example: 
  
  <WorkloadTransactions> 
      <Transaction id="28711464-EFB3-453E-8B8A-025BA85CCD10" type="U" 
 division="589" accessionArea="29" dateTime="20030101113555-0600" status="P"> 
          <Workload code="86832.0000" multiplyFactor="1" /> 
          <VbecsUser duz="53555" /> 
          <Lab accessionNumber="2930160023" testPerformed="6478" /> 
      </Transaction> </WorkloadTransactions> 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VBECS

NUMBER: 4628                            IA #: 4628
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: 769
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4628
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 a bi-directional data exchange between the rehosted gov.va.med.vbecs Blood
 Bank software application and the VistA Laboratory VBECS application to update
 workload event data in the rehosted SQL Server database as well as the VistA
 VBECS WORKLOAD CAPTURE file (#6002.01). The VistA Laboratory VBECS application 
 will initiate the data exchange.  
  
  
  XML Mapping of input XML Message: 
  _________________________________
  
  {XML Element.Attribute / VBECS SQL Table.Column or Function / Field in file
 #6002.01} 
  
  WorkloadEvent.WorkloadEventGuid / WorkloadEvent.WorkloadEventGuid / 
 TRANSACTION ID (#.01) 
  WorkloadEvent.WorkloadEventStatusCode / WorkloadEvent.WorkloadEventStatusCode
 / STATUS (#5) 
  WorkloadEvent.ProcessedDate / 
 fnFileManDateTimeConversionToDateTime(WorkloadEvent.ProcessedDate) / PROCESSED
 DATE (#4) 
  WorkloadEvent.ErrorText / WorkloadEvent.ErrorText / ERROR TEXT (#20) 
  WorkloadEvent.PceEncounterNumber / WorkloadEvent.PceEncounterNumber / PCE
 ENCOUNTER (#99) 
   
  Function Description: 
  _____________________
  
  fnFileManDateTimeConversionToDateTime - This function converts a FileMan 
 datetime type to a SQL datetime type.  
  
  
  Input XML Example: 
  __________________
  
  This XML message is sent from the VistA Laboratory VBECS software when VBECS
 workload data has been 
  
 updated by the Lab package.  
  <WorkloadEvents> 
      <WorkloadEvent> 
          
 <WorkloadEventGuid>28711464-EFB3-453E-8B8A-025BA85CCD10 </WorkloadEventGuid> 
          <WorkloadEventStatusCode>S</WorkloadEventStatusCode> 
          <ProcessedDate>3020101</ProcessedDate> 
          <ErrorText></ErrorText> 
          <PceEncounterNumber>55566666</PceEncounterNumber> 
      </WorkloadEvent> 
  </WorkloadEvents> 
  
  
  
  XML Mapping of Output XML Message: 
  __________________________________
  
  {XML Element.Attribute / VBECS SQL Table.Column or Function / Field in file
 #6002.01} 
  
  WorkloadEvent.id / WorkloadEvent.WorkloadEventGuid / TRANSACTION ID (#.01) 
  WorkloadEvent.successfullyUpdate / 
 WorkloadEvent.WorkloadEvent.WorkloadEventStatusCode / STATUS (#5) 
  WorkloadEvent.ErrorText / WorkloadEvent.ErrorText / ERROR TEXT (#20) 
  
  
  Output XML Example: 
  ___________________
  
  This XML message is returned from the rehosted gov.va.med.vbecs software to
 update the VBECS WORKLOAD 
  
 CAPTURE file (#6002.01).  
  
  <WorkloadEvents> 
      <WorkloadEvent id="28711464-EFB3-453E-8B8A-025BA85CCD10" 
 successfullyUpdated="S" > 
          <ErrorText></ErrorText> 
      </ WorkloadEvent > 
  </WorkloadEvents> 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VBECS

NUMBER: 4629                            IA #: 4629
  DATE CREATED: AUG 10, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VBECA1B
  NAME: VBECS PATIENT AVAILABLE UNITS   ID: VBECA1B
 GENERAL DESCRIPTION:   The purpose of this integration agreement is to provide
 the Surgery package access to units that are available for a patient.  Surgery
 will use the data returned from the AVUNIT^VBECA1B API to validate units for a
 patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: AVUNIT(TMPLOC,DFN)
 COMPONENT DESCRIPTION:   Called to return a list of units for a patient 
  
 AVUNIT^VBECA1B(TMPLOC,DFN) 
  
 RETURNED: 
  ^TMP(TMPLOC,$J,0) = PTABO^PTRH^DFN^FNAME^LNAME^DOB^SSN 
  ^TMP(TMPLOC,$J,IDT)= 
  EFLG^EDT^UID^PROD^VOL^ABO^RH^DTYP^UDIV^ULOC^PCODE 
  
  TMPLOC = Name of array node passed into routine 
  $J =     Job ID 
  PTABO =  Patient ABO blood group 
  PTRH =   Patient RH Type  - Returned as POS or NEG 
  DFN =    Patient file (#2) Internal Entry Number 
  FNAME =  Patient first name 
  LNAME =  Patient last name 
  DOB =    Patient date of birth - Returned in FileMan date format 
  SSN =    Patient social security number - Returned without hyphens 
  IDT =    Inverse Date/Time unit assigned 
  EFLG =   "*" if unit expires within 48 hours 
           "**" if unit expires within 24 hours 
  EDT =    Unit expiration date - Returned in FileMan date format 
  UID =    Unit ID 
  PROD =   Blood Product name 
  VOL =    Volume of unit 
  ABO =    ABO blood group of unit 
  RH =     RH Type of unit - Returned as P or N 
  DTYP =   Donation type (Autologous or Directed 
  UDIV =   Division where the unit resides 
  ULOC =   Location to which unit of blood is being relocated 
  PCODE =  Blood Product code 
VARIABLES: TMPLOC                       TYPE: Input
 VARIABLES DESCRIPTION:   Node in ^TMP to be used for output data array.  
  Example: 
  If TMPLOC="SR" then ^TMP("SR",$J,n) Would be returned.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number of patient in the PATIENT file
 (#2).  
SUBSCRIBING PACKAGE: SURGERY

NUMBER: 4630                            IA #: 4630
  DATE CREATED: FEB 28, 2005
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMRCCP
  NAME: Medicine Report Conversion      ID: GMRCCP
 GENERAL DESCRIPTION:   This integration agreement documents the private usage
 of a Consult/Request Tracking entry point to allow the one-time replacement of 
 Medicine package results with TIU documents.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$MCCNVT(GMRCMOD,GMRCMC,GMRCTIU)
 COMPONENT DESCRIPTION:   This entry point provides a mechanism to replace a
 Medicine package variable pointer with a TIU variable pointer in the
 REQUEST/CONSULTATION (#123) file.  
VARIABLES: GMRCMOD                      TYPE: Input
 VARIABLES DESCRIPTION:   boolean 1 (convert if found) or 0 (test conversion) 
VARIABLES: GMRCMC                       TYPE: Input
 VARIABLES DESCRIPTION:   This represents the variable pointer to a Medicine
 package result 
VARIABLES: GMRCTIU                      TYPE: Input
 VARIABLES DESCRIPTION:   pointer to file 8925 
VARIABLES: $$MCCNVT                     TYPE: Output
 VARIABLES DESCRIPTION:   The output of this entry point will be in the form: 
  
     -1^Description of error 
      0^No Action needed 
      1^Success message^Consult IEN 
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES

NUMBER: 4631                            IA #: 4631
  DATE CREATED: MAY 06, 2005            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XTID
  NAME: VHA UNIQUE ID (VUID) API        ID: XTID
 GENERAL DESCRIPTION:   API to handle the storage and retrieval of
 VUID-assigned data for terms/concepts.  
  
 Please consult the VistA document library online to browse examples of its
 use.  
  STATUS: Active
KEYWORDS: VUID
COMPONENT/ENTRY POINT: $$GETVUID(TFILE,TFIELD,TIREF)
 COMPONENT DESCRIPTION:   This extrinsic function retrieves the VHA unique id
 (VUID) for a given term/concept reference.  
  
 Example: 
  
 for terms defined in fields that are SET OF CODES 
  
 >S file=2,field=.02,iref="M" 
  
 >W $$GETVUID^XTID(file,field,iref) 
  
 123456 
  
  
 for terms defined in a single file 
  
 >S file=16000009,field=.01,iref="3," 
  
 >W $$GETVUID^XTID(file,field,iref) 
  
 123457 
VARIABLES: TFILE                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) VistA file/subfile number where
 term/concept is defined.  
VARIABLES: TFIELD                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Field number, in TFILE, where term/concept
 is defined.  
  
 - When not defined, TFIELD defaults to the .01 field number, and it represents
 terms defined in the file TFILE.  
  
 - When defined, TFIELD must be of type SET OF CODES.  
VARIABLES: TIREF                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) Internal reference for term/concept.  
  
 - For file entries this will be an IENS. For example, 
     TIREF="5," 
  
 - For sets of codes this will be the internal value of the code.  For 
   example, 
     TIREF=3 or 
     TIREF="f" or 
     TIREF="M" 
VARIABLES: $$GETVUID                    TYPE: Output
 VARIABLES DESCRIPTION:   Returns:  Success of operation as 
  
 - The VHA unique id (VUID), when successful; or 
  
 - "0^<error message>", when unsuccessful 
COMPONENT/ENTRY POINT: $$SETVUID(TFILE,TFIELD,TIREF,TVUID)
 COMPONENT DESCRIPTION:   This extrinsic function populates the VHA unique id
 (VUID) for a given term/concept reference.  
  
 Example: 
  
 for terms defined in fields that are SET OF CODES 
  
 >S file=2,field=.02,iref="M",vuid=123456 
  
 >W $$SETVUID^XTID(file,field,iref,vuid) 
  
 1 
  
 for terms defined in a single file 
  
 >S file=16000009,field=.01,iref="3,",vuid=123457 
  
 >W $$SETVUID^XTID(file,field,iref,vuid) 
  
 1 
VARIABLES: TFILE                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) VistA file/subfile number where
 term/concept is defined.  
VARIABLES: TFIELD                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Field number, in TFILE, where term/concept
 is defined.  
VARIABLES: TIREF                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) Internal reference for term/concept.  
  
 - For file entries this will be an IENS. For example, 
     TIREF="5," 
  
 - For sets of codes this will be the internal value of the code.  For 
   example, 
     TIREF=3 or 
     TIREF="f" or 
     TIREF="M" 
VARIABLES: TVUID                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The VHA unique id (VUID) to assign the
 given term/concept reference.  
VARIABLES: $$SETVUID                    TYPE: Output
 VARIABLES DESCRIPTION:   Returns: Success of operation as 
  
 - 1, when successful; or 
  
 - "0^<error message>", when unsuccessful 
COMPONENT/ENTRY POINT: $$GETSTAT(TFILE,TFIELD,TIREF,TDATE)
 COMPONENT DESCRIPTION:   This extrinsic function retrieves the status
 information for a given term/concept reference and a specified date/time.  
  
 Example: 
  
 for terms defined in fields that are SET OF CODES 
  
 >S file=2,field=.02,iref="M",datetime=$$NOW^XLFDT 
  
 >W $$GETSTAT^XTID(file,field,iref,datetime) 
  
 1^3050121.154752^ACTIVE 
  
 for terms defined in a single file 
  
 >S file=16000009,field=.01,iref="3,",datetime="" 
  
 >W $$GETSTAT^XTID(file,field,iref,datetime) 
  
 0^3050122.154755^INACTIVE 
VARIABLES: TFILE                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) VistA file/subfile number where
 term/concept is defined.  
VARIABLES: TFIELD                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Field number, in TFILE, where term/concept
 is defined.  
  
 - When not defined, TFIELD defaults to the .01 field number, and it represents
 terms defined in the file TFILE.  
  
 - When defined, TFIELD must be of type SET OF CODES.  
VARIABLES: TIREF                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) Internal reference for term/concept.  
  
 - For file entries this will be an IENS. For example, 
     TIREF="5," 
  
 - For sets of codes this will be the internal value of the code.  For 
   example, 
     TIREF=3 or 
     TIREF="f" or 
     TIREF="M" 
VARIABLES: TDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   (optional) FileMan date/time (defaults to NOW).  
VARIABLES: $$GETSTAT                    TYPE: Output
 VARIABLES DESCRIPTION:   Returns:  Success of operation as 
  
 - status information, when successful, as 
  
   "<internal value>^<FileMan effective date/time>^<external value>" 
  
   for example, 
  
   "0^3050220.115720^INACTIVE" 
  
   "1^3050225.115711^ACTIVE" 
  
   ; or 
  
 - "^<error message>", when unsuccessful 
COMPONENT/ENTRY POINT: $$SETSTAT(TFILE,TFIELD,TIREF,TSTAT,TDATE)
 COMPONENT DESCRIPTION:   Extrinsic function to store the status and status
 date/time for the given term.  
  
 Example: 
  
 for terms defined in fields that are SET OF CODES 
  
 >S file=2,field=.02,iref="M",status=1,datetime=$$NOW^XLFDT 
  
 >W $$SETSTAT^XTID(file,field,iref,status,datetime) 
  
 1 
  
 for terms defined in a single file 
  
 >S file=16000009,field=.01,iref="3,",status=1,datetime=$$NOW^XLFDT 
  
 >W $$SETSTAT^XTID(file,field,iref,status,datetime) 
  
 1 
VARIABLES: TFILE                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) VistA file/subfile number where
 term/concept is defined.  
VARIABLES: TFIELD                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Field number, in TFILE, where term/concept
 is defined.  
  
 - When not defined, TFIELD defaults to the .01 field number, and it represents
 terms defined in the file TFILE.  
  
 - When defined, TFIELD must be of type SET OF CODES.  
VARIABLES: TIREF                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) Internal reference for term/concept.  
  
 - For file entries this will be an IENS. For example, 
     TIREF="5," 
  
 - For sets of codes this will be the internal value of the code.  For 
   example, 
     TIREF=3 or 
     TIREF="f" or 
     TIREF="M" 
VARIABLES: TSTAT                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The status internal value as 
  
 - 0 for INACTIVE; or 
  
 - 1 for ACTIVE 
VARIABLES: TDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   (optional) FileMan date/time (defaults to NOW).  
VARIABLES: $$SETSTAT                    TYPE: Output
 VARIABLES DESCRIPTION:   Returns: Success of operation as 
  
 - 1, when successful; or 
  
 - "0^<error message>", when unsuccessful 
COMPONENT/ENTRY POINT: $$GETMASTR(TFILE,TFIELD,TIREF)
 COMPONENT DESCRIPTION:   This extrinsic function retrieves the value of the
 flag MASTER ENTRY FOR VUID for a given term/concept reference.  
  
 Example: 
  
 for terms defined in fields that are SET OF CODES 
  
 >S file=2,field=.02,iref="M" 
  
 >W $$GETMASTR^XTID(file,field,iref) 
  
 1 
  
 for terms defined in a single file 
  
 >S file=16000009,field=.01,iref="3," 
  
 >W $$GETMASTR^XTID(file,field,iref) 
  
 0 
VARIABLES: TFILE                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) VistA file/subfile number where
 term/concept is defined.  
VARIABLES: TFIELD                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Field number, in TFILE, where term/concept
 is defined.  
  
 - When not defined, TFIELD defaults to the .01 field number, and it represents
 terms defined in the file TFILE.  
  
 - When defined, TFIELD must be of type SET OF CODES.  
VARIABLES: TIREF                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) Internal reference for term/concept.  
  
 - For file entries this will be an IENS. For example, 
     TIREF="5," 
  
 - For sets of codes this will be the internal value of the code.  For 
   example, 
     TIREF=3 or 
     TIREF="f" or 
     TIREF="M" 
VARIABLES: $$GETMASTR                   TYPE: Output
 VARIABLES DESCRIPTION:   Returns:  Success of operation as 
  
 - The internal value of the MASTER ENTRY FOR VUID field, when successful, 
   as 
  
   0 for NO 
   1 for YES 
  
   ;or 
  
 - "^<error message>", when unsuccessful 
COMPONENT/ENTRY POINT: $$SETMASTR(TFILE,TFIELD,TIREF,TMASTER)
 COMPONENT DESCRIPTION:   This extrinsic function stores the value of the flag
 MASTER ENTRY FOR VUID for a given term/concept reference.  
  
 Example: 
  
 for terms defined in fields that are SET OF CODES 
  
 >S file=2,field=.02,iref="M",mstrflag=0 
  
 >W $$SETMASTR^XTID(file,field,iref,mstrflag) 
  
 1 
  
 for terms defined in a single file 
  
 >S file=16000009,field=.01,iref="3,",mstrflag=1 
  
 >W $$SETMASTR^XTID(file,field,iref,mstrflag) 
  
 1 
VARIABLES: TFILE                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) VistA file/subfile number where
 term/concept is defined.  
VARIABLES: TFIELD                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Field number, in TFILE, where term/concept
 is defined.  
  
 - When not defined, TFIELD defaults to the .01 field number, and it represents
 terms defined in the file TFILE.  
  
 - When defined, TFIELD must be of type SET OF CODES.  
VARIABLES: TIREF                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) Internal reference for term/concept.  
  
 - For file entries this will be an IENS. For example, 
     TIREF="5," 
  
 - For sets of codes this will be the internal value of the code.  For 
   example, 
     TIREF=3 or 
     TIREF="f" or 
     TIREF="M" 
VARIABLES: TMASTER                      TYPE: Input
 VARIABLES DESCRIPTION:   (required) The internal value flag for the MASTER
 ENTRY FOR VUID field, as 
  
 - 0 for NO; or 
  
 - 1 for YES 
VARIABLES: $$SETMASTR                   TYPE: Output
 VARIABLES DESCRIPTION:   Returns: Success of operation as 
  
 - 1, when successful; or 
  
 - "0^<error message>", when unsuccessful 
COMPONENT/ENTRY POINT: $SCREEN(TFILE,TFIELD,TIREF,TDATE,TCACHE)
 COMPONENT DESCRIPTION:   This Extrinsic function retrieves the screening
 condition for a given term/concept reference and specified date/time.  
  
    Example 1 For terms defined in fields that are SET OF CODES: 
  
 >S file=2,field=.02,iref="M",datetime=$$NOW^XLFDT 
  
 >W $$SCREEN^XTID(file,field,iref,datetime) 0 
  
    Example 2 For terms defined in a single file: 
  
 >S file=16000009,field=.01,iref="3,",datetime="" 
  
 >W $$SCREEN^XTID(file,field,iref,datetime) 0 
  
    Example 3 When searching a large file: 
  
 >S file=120.52,field=.01,datetime="" >S SCREEN="I
 '$$SCREEN^XTID(file,field,Y_"","",datetime,.cached)" 
 >. . .
 >K cached >D LIST^DIC(file,,".01;99.99",,"*",,,,SCREEN,,"LIST","MSG") >K
 cached 
VARIABLES: TFILE                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) VistA file/subfile number where
 term/concept is defined.  
VARIABLES: TFIELD                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Field number, in TFILE, where term/concept
 is defined.  
  
 - When not defined, TFIELD defaults to the .01 field number, and it represents
 terms defined in the file TFILE.  
  
 - When defined, TFIELD must be of type SET OF CODES.  
VARIABLES: TIREF                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) Internal reference for term/concept.  
  
 - For file entries this will be an IENS. For example, 
     TIREF="5," 
  
 - For sets of codes this will be the internal value of the code.  For 
   example, 
     TIREF=3 or 
     TIREF="f" or 
     TIREF="M" 
VARIABLES: TDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   (optional) FileMan date/time (defaults to NOW) to
 check screening against.  
VARIABLES: $$SCREEN                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns: The screening condition as 
  
 - 0, when term/concept is selectable (i.e. don't screen it out); or 
  
 - 1, when term/concept is not selectable (i.e. screen it out) 
VARIABLES: TCACHE                       TYPE: Both
 VARIABLES DESCRIPTION:   (optional and by-reference) Flag to indicate caching.
 Used mainly when defining the "screen" parameter [e.g., DIC("S")] while
 searching large files. This will improve the speed of the search.  
  
 NOTE: It must be KILLed before initiating each search query (e.g., before 
 calling the ^DIC).  
COMPONENT/ENTRY POINT: GETIREF(TFILE,TFIELD,TVUID,TARRAY,TMASTER)
 COMPONENT DESCRIPTION:   This subroutine searches and returns a list of
 terms/concepts for a given VUID (TVUID).  Filtering of the list is applied
 when the remaining parameters are defined: TFILE, TFIELD, and TMASTER.  
  
 Example: 
  
 >N array S array="MYARRAY" 
  
 >S file=16000009,field=.01,vuid=12343,master=0 
  
 >D GETIREF^XTID(file,field,vuid,array,master) 
  
 >ZW MYARRAY 
  
 MYARRAY=2 MYARRAY(16000009,.01,"1,")=1^3050202.153242^ACTIVE^0 
 MYARRAY(16000009,.01,"3,")=0^3050215.07584^INACTIVE^1 
   
 When no entries are found, the named array is not populated 
  
 When an error occurs, the named array is populated as follows: 
  
 >ZW MYARRAY 
  
 MYARRAY("ERROR")="<error message>" 
VARIABLES: TFILE                        TYPE: Input
 VARIABLES DESCRIPTION:   (optional) VistA file/subfile number where
 term/concept is defined.  
  
 - When defined, the search is limited to those term/concepts that exist 
   in that file and have the VUID assigned to TVUID.  
  
 - When not defined, the search will include term/concepts that have the 
   VUID assigned to TVUID and may exist in both file terms and in SET OF 
   CODES terms.  
VARIABLES: TFIELD                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Field number, in TFILE, where term/concept
 is defined.  
  
 - When not defined, TFIELD defaults to the .01 field number, and it 
   represents terms defined in the file TFILE. The search is limited to 
   those term/concepts that exist in that file and have the VUID assigned 
   to TVUID 
  
 - When defined, TFIELD must be of type SET OF CODES.  The search is 
   limited to those term/concepts that exist in that file/field and have 
   the VUID assigned to TVUID.  
VARIABLES: TVUID                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The VHA unique id (VUID) value specified
 to limit the search on.  
VARIABLES: TARRAY                       TYPE: Both
 VARIABLES DESCRIPTION:   (required) The name of the array (local or global)
 where results of the search will be stored.  
  
 Returns: The given array populated as 
  
 - @TARRAY=<list count> 
   @TARRAY@(<file#>,<field#>,<internal reference>)=<status info> 
  
   where the <status info> is defined as 
  
   "<internal value>^<FileMan effective date/time>^ 
    <external value>^<master entry?>" 
  
   ; or 
  
 - when no entries are found, the array named by TARRAY is not populated 
  
   ; or 
  
 - when an error occurs, the array named by TARRAY is populated as follows: 
  
   @TARRAY("ERROR")="<error message>" 
VARIABLES: TMASTER                      TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Flag to limit the search of terms based on
 the value of the MASTER ENTRY FOR VUID field.  
  
 - 0, to include all terms; or 
  
 - 1, to include only those terms designated as MASTER ENTRY FOR VUID 
  DATE ACTIVATED: JUN 17, 2009

NUMBER: 4632                            IA #: 4632
  FILE NUMBER: 8992.1                   GLOBAL ROOT: XTV(8992.1
  DATE CREATED: MAR 31, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4632
  ID: XTV(8992.1
GLOBAL REFERENCE: XTV(8992.1,'B',
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: XTV(8992.1,'D',
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: XTV(8992.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DATE CREATED
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: GENERATED BY
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.04                      FIELD NAME: ROUTINE FOR PROCESSING
  LOCATION: 1;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DATA FOR PROCESSING
  LOCATION: 2;E1,245                    ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Registration utilizes the alert tracking file to
 obtain/update information from existing alerts.  Information updated will be
 added to the DATA FOR PROCESSING (#2) Field.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4633                            IA #: 4633
  DATE CREATED: MAY 17, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VBECS LAB ORDER LOOKUP BY UID
  REMOTE PROCEDURE: VBECS LAB ORDER LOOKUP BY UID
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to provide
 the rehosted VBECS application with a lookup into the ACCESSION file (#68) for
 the purpose of identifying an existing Lab Order based on a specimen UID.  
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4634                            IA #: 4634
  GLOBAL ROOT: DD(                      DATE CREATED: MAR 07, 2005
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Data Dictionary global access   ID: DD(
GLOBAL REFERENCE: DD(D0,
 GLOBAL DESCRIPTION:   To loop through all file/subfile numbers in VistA as
 described in the details section.  
GLOBAL REFERENCE: DD(D0,99.991
 GLOBAL DESCRIPTION:   To determine the existence of  VUID-related fields. 
 Field 99.991 is one of several fields that contain VUID-related data.  
 GENERAL DESCRIPTION:   to request the reading of the ^DD global to quickly
 search for files that are  "VUID-enhanced." 
  
 Users of the new VUID Kernel-Toolkin api have a subroutine to search for 
 terms/concepts when given the VUID # and some filter parameters.  
  
 When the "file" filter is not defined, the search must quickly look into every
 VistA file to look for the term.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DATA DICTIONARY
KEYWORDS: VUID
KEYWORDS: DD
SUBSCRIBING PACKAGE: TOOLKIT
 SUBSCRIBING DETAILS:   The new Toolkit API for managing VUID-related data has
 a subroutine to search for terms/concepts when given the VUID # and some
 filter parameters.  
  
 When the "file" filter is not defined, the search must quickly look into every
 VistA file to look for the term.  
  
 sample code: 
  
         . S FL=0 
         . F  S FL=$O(^DIC(FL)) Q:'FL  D 
         . . Q:'$D(^DD(FL,99.991)) 
         . . Q:FL=8985.1 
         . . S CTX("SOURCE FILE#")=FL 
         . . S CTX("TERM FILE#")=FL 
         . . S CTX("TERM FIELD#")=.01 
         . . D SRCHTRMS^XTIDTBL(.CTX,VUID,XTCARR,MASTER) 
         . ;

NUMBER: 4635                            IA #: 4635
  DATE CREATED: AUG 15, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBRFN4
  NAME: ROUTINE IBRFN4                  ID: IBRFN4
 GENERAL DESCRIPTION:   Accounts Receivable is seeking an integration agreement
 to call routine IBRFN4 to gather information from various integrated billing
 files.  This information is then used as data elements in the IB AR Data
 Extract, which is sent via FTP to the ARC.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$IBAREXT(IEN,.IBD)
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal number of the claim in file 399 
VARIABLES: IBD                          TYPE: Both
 VARIABLES DESCRIPTION:   Array name in which the output data is stored.  
  
 Data returned: 
  
  IBD=MEDICARE STATUS^LAST MRA REQUESTED DATE^LAST ELECTRONIC EXTRACT 
   DATE^PRINTED VIA EDI^FORCE CLAIM TO PRINT^CLAIM MRA STATUS^MRA 
   RECORDED DATE^BILL CANCELLED DATE^FORM TYPE^CURRENT PAYER^ 
   DRG (EXTERNAL FORMAT)^ECME #^NON-VA FACILITY^#Days Site Not 
   Responsible for MRA^NATIONAL VA ID NUMBER FOR INS VERIFICATION 
   ^PAYER NAME^OFFSET AMOUNT 
         
  IBD("PRD",SEQ #)=PROSTHETIC ITEM NAME^DATE^BILL IEN 
  
  IBD("IN")= TYPE OF PLAN NAME ^ GROUP NUMBER ^ RELATIONSHIP TO INSURED ^ 
   SOURCE OF INFO ^ EDI ID NUMBER - INST ^ EDI ID NUMBER - PROF ^ INSURANCE 
   REIMBURSE 
  
  IBD("IN","MMA")= MAILING STREET ADDRESS [LINE 1 ^ MAILING STREET ADDRESS 
   [LINE 2] ^ CITY ^ STATE NAME  ^  ZIP 
VARIABLES: $$IBAREXT                    TYPE: Output
 VARIABLES DESCRIPTION:   This is the variable that holds the data retuned in
 the IBD array.  
COMPONENT/ENTRY POINT: $$IBACT(IEN,.IBARRY)
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal number of the bill in file 430 
VARIABLES: IBARRY(SEQ #)                TYPE: Both
 VARIABLES DESCRIPTION:   The data returned in this array is as follows: 
  
  IBARRY(SEQ. #)=AR BILL #^REFERENCE #^EXTERNAL STATUS^IB ACTION TYPE NAME 
  ^UNITS^TOTAL CHARGE^DT BILLD FROM^DT BILLD TO^AR BILL IEN ^DT ENTRY 
  ADDED^PATIENT SSN^EVENT DATE^RESULTING FROM^INSTITUTION IEN 
VARIABLES: $$IBACT                      TYPE: Output
 VARIABLES DESCRIPTION:   This is the variable that holds the components of the
 IBARRY array returned by this entry point.  
COMPONENT/ENTRY POINT: $$PREREG(IBBDT,IBEDT)
VARIABLES: IBBDT                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the beginning date for the Pre-Registration
 data transmission.  
VARIABLES: IBEDT                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the ending date for the Pre-Registration data
 transmission.  
VARIABLES: IBDATA                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the array name in which the data is stored. 
 The data returned in this array is: 
  
 NUMBER OF UNIQUE PATIENTS TREATED ^ NUMBER OF UNIQUE PATIENTS PRE-REGISTERED
 WITHIN PRE-REGISTRATION TIME FRAME ^ PERCENT PRE-REGISTERED ^ NUMBER OF UNIQUE
 OUTPATIENTS PRE-REGISTERED PAST PRE-REGISTRATION TIME FRAME ^ NUMBER OF UNIQUE
 OUTPATIENTS NEVER PRE-REGISTERED 
VARIABLES: $$PREREG                     TYPE: Output
 VARIABLES DESCRIPTION:   This is the variable that holds the components of the
 IBDATA array returned by this entry point.  
COMPONENT/ENTRY POINT: $$BUFFER(IBBDT,IBEDT)
VARIABLES: IBBDT                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the beginning date for the buffer file
 transmission.  
VARIABLES: IBEDT                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the ending date for the buffer file
 transmission.  
VARIABLES: IBDATA                       TYPE: Output
 VARIABLES DESCRIPTION:   Variable which returns  the AVERAGE NUMBER OF DAYS IT
 TAKES TO PROCESS A POLICY IN THE BUFFER FILE as output.  
VARIABLES: $$BUFFER                     TYPE: Output
 VARIABLES DESCRIPTION:   This holds the data returned in the IBDATA variable.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4636                            IA #: 4636
  DATE CREATED: MAR 17, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LRWU4
  NAME: VALIDATE UID API                ID: LRWU4
 GENERAL DESCRIPTION:   The purpose of this Integration Agreement is to allow
 VBECS to use the Lab Services v5.2 API CHECKUID^LRWU4 for the purpose of
 validating a Laboratory accession's UID (unique identifer) and identifying the 
 accession associated with it.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LRWU4
KEYWORDS: CHECKUID
COMPONENT/ENTRY POINT: $$CHECKUID(LRX)
 COMPONENT DESCRIPTION:   Check if UID is valid and if related accession exists
 in ACCESSION file (#60).  
VARIABLES: LRX                          TYPE: Input
 VARIABLES DESCRIPTION:   UID to check.  
VARIABLES: $$CHECKUID                   TYPE: Output
 VARIABLES DESCRIPTION:   
  Function returns 
   0 if accession does not exist 
   1 (accession exists)^area^date^number if accession does exist 
      area^date^number relate to the values for a FileMan DA array to 
      access the accession in the ACCESSION file (#60) 
      DA = accession number 
      DA(1) = FileMan date 
      DA(2) = accession area 
SUBSCRIBING PACKAGE: VBECS
 SUBSCRIBING DETAILS:   VBECS will use the Lab Services v5.2 API CHECKUID^LRWU4
 for the purpose of validating a UID and identifying the accession associated
 with it.  

NUMBER: 4637                            IA #: 4637
  FILE NUMBER: 119.9                    GLOBAL ROOT: FH(119.9,
  DATE CREATED: MAR 22, 2005            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CHANGE VA CLASSIFICATION POINTERS
  ID: FH(119.9,
GLOBAL REFERENCE: FH(119.9,
FIELD NUMBER: 85                        FIELD NAME: DRUG CLASSIFICATIONS
  LOCATION: 199.985;1                   ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   
  This field is a pointer to File 50.605, VA Drug Classification and is a
 classification of interest to clinicians.  
 GENERAL DESCRIPTION:   The FH SITE PARAMETERS file (#119.9) has a multiiple
 field that points to the VA DRUG CLASS file (#50.605).  Some entries in file
 50.605 have been renamed and moved to new IENs.  To make sure that the
 dietetics pointers are correct after this change, NDF requests permission to
 do direct global reads and writes to entries in this multiple.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
 SUBSCRIBING DETAILS:   Direct global reads and writes to the DRUG
 CLASSIFICATIONS sub-file (#85) in file FH(119.9 

NUMBER: 4638                            IA #: 4638
  DATE CREATED: APR 05, 2005
  CUSTODIAL PACKAGE: HEALTH DATA & INFORMATICS
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HDISVAP
  NAME: DBIA4638-A                      ORIGINAL NUMBER: 4638
  ID: HDISVAP
 GENERAL DESCRIPTION:   The NTRTMSG^HDISVAP API is used to direct the user on
 how to enter a new term using the New Term Rapid Turnaround Process (NTRT)
 being provided by Enterprise Terminology Services (ETS).  
  STATUS: Active
KEYWORDS: DATA STANDARDIZATION
COMPONENT/ENTRY POINT: NTRTMSG(HDISARYF,.HDISARY)
 COMPONENT DESCRIPTION:   Display a message or optionally return an array that
 directs the user on how to enter a new term using the New Term Rapid
 Turnaround Process (NTRT).  This API can be placed on the Entry Action of the
 Option or Protocol being inactivated.  
  
 Example: 
  
 >D NTRTMSG()          
  
    
  In support of national standardization of the contents of this file, 
  local site addition and modification functions are no longer available.  
  If you wish to request a new term or modify an existing term, please 
  refer to the New Term Rapid Turnaround (NTRT) web site located at 
  http:// http://vista.url//ntrt/. If you have any questions regarding this new
 term request process, please contact the ERT NTRT Coordinator via e-mail at
 EMAIL GROUP.  
VARIABLES: HDISARYF                     TYPE: Input
 VARIABLES DESCRIPTION:   Return Text in an Array Flag  (Optional- Default 0) 
  
 1=Yes and 0=No 
VARIABLES: HDISARY                      TYPE: Output
 VARIABLES DESCRIPTION:   Optional.  An array containing the NTRT Message is
 returned otherwise the message is diplayed on the screen.  The Output variable
 is assumed to be Null when the API is invoked.  
  
 Array Format: 
  
 HDISARY(1..9) = Text Message 

NUMBER: 4639                            IA #: 4639
  DATE CREATED: APR 06, 2005
  CUSTODIAL PACKAGE: HEALTH DATA & INFORMATICS
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HDISVCMR
  NAME: DBIA4638-B                      ORIGINAL NUMBER: 4638
  ID: HDISVCMR
 GENERAL DESCRIPTION:   The EN^HDISVCMR API is used to invoke the VUID Seeding
 Process for a specified HDIS Domain.  
  
 Packages may invoke this API without registering another IA only if the domain
 and files being referenced are in the calling package's numberspace.  
  STATUS: Active
KEYWORDS: DATA STANDARDIZATION
COMPONENT/ENTRY POINT: EN(HDISDOM,HDISFILE)
 COMPONENT DESCRIPTION:   Invoke the VUID Seeding Process for a specified HDIS
 Domain.  
  
 Example: 
  
  N DOMPTR,TMP 
  S TMP=$$GETIEN^HDISVF09("ALLERGIES",.DOMPTR) 
  I TMP D EN^HDISVCMR(DOMPTR,"") 
VARIABLES: HDISDOM                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN to the HDIS Domain file 
VARIABLES: HDISFILE                     TYPE: Input
 VARIABLES DESCRIPTION:   Specific file # to be seeded (if not all domain
 files) (Optional) 

NUMBER: 4640                            IA #: 4640
  DATE CREATED: APR 06, 2005
  CUSTODIAL PACKAGE: HEALTH DATA & INFORMATICS
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HDISVF01
  NAME: DBIA4638-C                      ORIGINAL NUMBER: 4638
  ID: HDISVF01
 GENERAL DESCRIPTION:   API(s) for retrieval and screening of the file/field
 implementation status.  
  STATUS: Active
KEYWORDS: DATA STANDARDIZATION
COMPONENT/ENTRY POINT: $$GETSTAT(FILE,FIELD,DATE,FAC,DOMAIN,TYPE)
 COMPONENT DESCRIPTION:   Get file/field implementation status 
  
 Notes: 
  
 - Values for "not started" status and no date are returned 
   on bad input or if no entry is found 
  
 - If time is not included with the date, the last status 
   for the given day is returned 
  
 - If more than one entry for the same date/time is found, 
   the higher entry number is returned 
  
 Example(s): 
  
 1. Get current status for GMRV Vital Qualifier file 
  
    >W $$GETSTAT^HDISVF01(120.52) 
    
    6^18^3050331.135037 
  
 2. Get status of GMRV Vital Qualifier file on 10/1/2004 
  
    >W $$GETSTAT^HDISVF01(120.52,"",3041001) 
  
    0^^ 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   File number 
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   Field number (defaults to .01) 
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   FileMan date/time to return status for (Optional-
 defaults to NOW) 
VARIABLES: FAC                          TYPE: Input
 VARIABLES DESCRIPTION:   Facility number (Optional- defaults to current) 
VARIABLES: DOMAIN                       TYPE: Input
 VARIABLES DESCRIPTION:   Domain/IP address (Optional- defaults to current) 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Type of system (Optional- defaults to current) 
  
 0 = Test     1 = Production 
VARIABLES: $$GETSTAT                    TYPE: Output
 VARIABLES DESCRIPTION:   StatusCode ^ StatusPointer ^ StatusDate 
COMPONENT/ENTRY POINT: $$SCREEN(FILE,FIELD,DATE)
 COMPONENT DESCRIPTION:   Apply screening logic to file/field.  
  
 Notes: 
  
 - 0 (don't screen) is returned on bad input 
  
 - If time is not included with the date, the last status 
   for the given day is returned 
  
 Example(s): 
  
 1. Should entries in GMRV Vital Qualifier file be screened 
  
    >W $$SCREEN^HDISVF01(120.52) 
  
    1 
  
 2. Should entries in GMRV Vital Qualifier file on screened on 10/1/2004 
  
    >W $$SCREEN^HDISVF01(120.52,"",3041001) 
  
    0 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   File number 
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   Field number (defaults to .01) 
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   FileMan date/time to check against (Optional-
 defaults to NOW) 
VARIABLES: $$SCREEN                     TYPE: Output
 VARIABLES DESCRIPTION:   Flag indicating if screening logic should be applied 
  
 0 = Don't screen entries during selection 
  
 1 = Screen entries during selection 

NUMBER: 4641                            IA #: 4641
  DATE CREATED: APR 06, 2005
  CUSTODIAL PACKAGE: HEALTH DATA & INFORMATICS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HDISVCFX
  NAME: DBIA4638-D                      ORIGINAL NUMBER: 4638
  ID: HDISVCFX
 GENERAL DESCRIPTION:   The Data Standardization (DS) Domain Action Team (DAT),
 which includes the application developer, identifies which reference files
 should be standardized for the Domain.  Each entry in the file is then
 assigned a VHA Unique Identifier (VUID) by the Enterprise Reference
 Terminology (ERT) Group.  DS then assists in the seeding of the VUIDs at the
 Facilities.  There are two approaches to the VUID Seeding.  The first is
 Facility by Facility and the second is Global Distribution. Additional
 information about the approaches can be found in the VUID Implementation
 Application Patch Requirements Document for the Domain being Standardized. 
 Each Domain is given a document which identifies the changes needed in Current 
 VistA for the DS effort.  One of the requirements is to release a VistA patch
 via the National Patch Module (NPM) which contains the changes identified in
 the Patch Requirements Document.  
  
 For the Facility by Facility Approach the HDIS Domain file is used during the
 VUID Seeding Process.  It contains a list of the files being standardized for
 the Domain.  The VUID Seeding Process itself is invoked in the application
 post-initialization routine by calling EN^HDISVCMR (IA #4639).  As part of
 this process DS will look through the entries for each of the files being
 standardized for the Domain and extract the .01 field to be bundled into an
 XML message.  
  
 The subscriber agrees to give DS permission to directly access the Global in
 the routine FILE^HDISVCFX for the .01 field of the file being standardized.  
  
 GLOBAL REFERENCE: 
   ^Global(file#,D0,0)=.01 field read only 
  STATUS: Active
KEYWORDS: DATA STANDARDIZATION
KEYWORDS: HDISVCFX
COMPONENT/ENTRY POINT: FILE
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   added 04/10/2008 

NUMBER: 4642                            IA #: 4642
  FILE NUMBER: 810.3                    GLOBAL ROOT: PXRMXT(810.3
  DATE CREATED: MAR 25, 2005            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RESET VA CLASS POINTERS
  ID: PXRMXT(810.3
GLOBAL REFERENCE: PXRMXT(810.3,D0,1,
FIELD NUMBER: .04                       FIELD NAME: FINDING ITEM
  LOCATION: 0;4                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is a variable pointer that contains the possible
 findings from a reminder evaluation.  
GLOBAL REFERENCE: PXRMXT(810.3,D0,2,
FIELD NUMBER: .01                       FIELD NAME: FINDING ITEM
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is the finding item returned by reminder evaluation. 
 
 GENERAL DESCRIPTION:   Certain VA Classes have changed.  NDF requests
 permission to reset the pointers to the VA DRUG CLASS file (#50.605) in the
 REMINDER EXTRACT SUMMARY file (#810.3).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
 SUBSCRIBING DETAILS:   Certain entries in the VA CLASS file have changed.  An
 NDF patch will reset entries in the FINDING ITEM field of the EXTRACT FINDINGS
 sub-file and the FINDING ITEM field of the FINDING TOTALS sub-file in the 
 REMINDER EXTRACT SUMMARY file as necessary.  

NUMBER: 4643                            IA #: 4643
  FILE NUMBER: 811.5                    GLOBAL ROOT: PSRMD(811.5
  DATE CREATED: MAR 25, 2005            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RESET VA DRUG CLASSES
  ID: PSRMD(811.5
GLOBAL REFERENCE: PXRMD(811.5,D0,20,
FIELD NUMBER: .01                       FIELD NAME: FINDING ITEM
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   Some entries in the VA DRUG CLASS file (#50.605) have
 changed.  NDF requests premission to reset entries in the FINDING ITEM field
 of the FINDINGS sub-file in the REMINDER TERM file (#811.5) as needed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
 SUBSCRIBING DETAILS:   NDF patches will reset entries in the FINDING ITEM
 field of the FINDINGS sub-file of the REMINDER TERM file as needed.  

NUMBER: 4644                            IA #: 4644
  FILE NUMBER: 811.9                    GLOBAL ROOT: PXD(811.9
  DATE CREATED: MAR 25, 2005            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RESET VA DRUG CLASS
  ID: PXD(811.9
GLOBAL REFERENCE: PXD(811.9,D0,20,
FIELD NUMBER: .01                       FIELD NAME: FINDING ITEM
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This field identifies finding items to use in the
 reminder evaluation process.  A finding item may be used to determine the
 patient cohort, resolve the reminder, or provide information to the provider.  
 How this finding item will be used depends on the additional fields defined,
 or not defined, for this finding item: 1. To define a finding item to use in
 the patient cohort  logic, add the finding item and define its USE IN PATIENT
 COHORT LOGIC field.  2. To define a finding item to use in the resolution
 logic, add the finding item and define its USE IN RESOLUTION LOGIC field.  3.
 To define a finding item to use for information only , leave the USE IN
 PATIENT COHORT LOGIC and USE IN RESOLUTION LOGIC fields blank.  This finding
 item can be used to override the baseline frequency age.  
 GENERAL DESCRIPTION:   Certain VA drug classes have changed.  NDF requests
 permission to reset pointers in the FINDINGS sub-file of the REMINDER
 DEFINITION file (#811.9) as needed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
 SUBSCRIBING DETAILS:   NDF patches will reset pointers in the FINDINGS
 sub-file of the REMINDER DEFINITION file as needed.  

NUMBER: 4645                            IA #: 4645
  DATE CREATED: MAR 24, 2005            CUSTODIAL PACKAGE: RPC BROKER
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XWBTCP
  NAME: START/STOP XWBTCP LISTENER      ID: XWBTCP
 GENERAL DESCRIPTION:   This is a IA for KIDS new auto patch utility to start
 and stop the RPC Broker (XWBTCP) listener.  In the code KIDS will make
 reference to STOPALL^XWBTCP and RESTART^XWBTCP.  Some patches require that the
 Broker listener be stopped.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XWBTCP
COMPONENT/ENTRY POINT: STOPALL
 COMPONENT DESCRIPTION:   This entry point will stop all Broker listeners.  
COMPONENT/ENTRY POINT: RESTART
 COMPONENT DESCRIPTION:   This entry point will restart all Broker listeners.  
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   KIDS is the subcribing package.  

NUMBER: 4646                            IA #: 4646
  DATE CREATED: DEC 14, 2010            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  ROUTINE: IBCNEUT3                     NAME: DSIV CALL TO IBCNEUT3
  ID: IBCNEUT3
 GENERAL DESCRIPTION:   The Insurance Capture Buffer (ICB) application uses the
 $$INSERROR API in IBCNEUT3 to retrieve a single line, user friendly eIV error
 message.  This call is only made when there is a buffer error condition.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$INSERROR(TYPE,IEN,ERRFLG,ARRAY)
 COMPONENT DESCRIPTION:   The function returns ien from 365.15^payer ien (if
 found)^national id The array variable contains the following data: 
    Array(n)   error number^# of lines in error text 
    Array(n,n) contains error text.  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   "B" for Buffer (used by DSIV) or "I" for Insurance.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The Buffer file (#355.33) ien or the Insurance
 Company (#36) ien 
VARIABLES: ERRFLG                       TYPE: Input
 VARIABLES DESCRIPTION:   0 (zero) for no extended error message 1 (one) for
 extended error message.  ICB passes a 1.  
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   Return array variable name passed by reference.  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER

NUMBER: 4647                            IA #: 4647
  DATE CREATED: MAR 31, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLCS2
  NAME: STOP/RESTART HL7                ID: HLCS2
 GENERAL DESCRIPTION:   This is a IA for KIDS new auto patch utility to start
 and stop HL7 background processes.  In the code KIDS will make reference to
 CLEAR^HLCS2, LLP^HLCS2, STARTF^HLCS2, and STRT^HLCS2.  Some patches require
 that HL7 processes to be stopped.  
  
 Only patches that have installation instructions to stop and re-start the HL7
 processes will be set up to automatically execute (non-interactively) the
 equivalent of the current options 
  
 - Stop All Messaging Background Processes [HL STOP ALL] menu option.  and -
 Restart/Start All Links and Filers [HL TASK RESTART]' menu option.  
  
 The new functionality provided in patch HL*1.6*126 is not included in the 
 automation process.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HL7
COMPONENT/ENTRY POINT: CLEAR
 COMPONENT DESCRIPTION:   This resets the state in file 869.3.  
COMPONENT/ENTRY POINT: LLP
 COMPONENT DESCRIPTION:   This will stop the logical links.  
COMPONENT/ENTRY POINT: STARTF
 COMPONENT DESCRIPTION:   This will start filers.  
COMPONENT/ENTRY POINT: STRT
 COMPONENT DESCRIPTION:   This will start the links.  
SUBSCRIBING PACKAGE: KERNEL

NUMBER: 4648                            IA #: 4648
  DATE CREATED: DEC 15, 2010            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFCTFU2
  NAME: VAFC LOCAL GETCORRESPONDINGIDS
  REMOTE PROCEDURE: VAFC LOCAL GETCORRESPONDINGIDS
  ID: VAFCTFU2
 GENERAL DESCRIPTION:   
  Given a patient DFN, ICN, or EDIPI, this API returns a list 
  of Treating Facilities, including SOURCE ID, station number, 
  and IDENTIFIER STATUS.  This API will be called by North 
  Chicago via the VAFC LOCAL GETCORRESPONDINGIDS remote procedure.  
  TAG: TFL                 ROUTINE: VAFCTFU2 
   
  The patient identifier will either be the PATIENT file (#2) 
  IEN (aka DFN), Integration Control Number (aka ICN) or the 
  DOD Identifier (aka EDIPI).  Following this format: 
   
  ID^IDTYPE^AssigningAuthority^AssigningFacility 
   
  Examples: 
  ICN example:   1008520438V882204^NI^USVHA^200M 
  DFN example:   100000511^PI^USVHA^500 
  EDIPI example: 852043888^NI^USDOD^200DOD 
   
  This will return a list of Treating Facilities in this format: 
   
  ID^IDTYPE^AssigningAuthority^AssigningFacility^IDStatus 
   
  Examples: 
  RETURN(1)="27^PI^USVHA^500^H" 
  RETURN(2)="7169806^PI^USVHA^500^A" 
  RETURN(3)="^PI^USVHA^200PS" 
  RETURN(4)="1^NI^USDOD^200DOD^A" 
  RETURN(5)="2^NI^USDOD^200DOD^H" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: TFL
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************** 
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                   
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
 ****************************************************
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Added 03/23/21: The Consults package GMRC*3.0*173
 includes code for the Community Care Referrals and Authorization (CCRA)
 project. Community Care Referrals and Authorization (CCRA) project has been
 tasked with sending the EDIPI with consult requests transmitted to the
 HealthShare Referral Manager. These patient ids will be displayed by HSRM and
 some, including the EDIPI, will be displayed on the printed offline referral 
 form generated by HSRM. They are used by community care staff to look-up 
 veteran information on other systems.  
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   Approved to add 9/24/20. Effective with DENT*1*76 to
 support lookup patient DFN using EDIPI from Millennium SIU^S14 message.  
SUBSCRIBING PACKAGE: AUTOMATED LAB INSTRUMENTS
 SUBSCRIBING DETAILS:   Added 3/4/22, effective with patch LA*5.2*100 the Lab
 Auto-Instrument Package will use this Application Programming Interface (API)
 to retrieve the  list of treating facilities for a patient.  
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   Added 4/23/25, effective with patch RMPR*3*217,
 Prosthetics needs to retrieve the treating facility list to ensure that
 patients are properly set up after a proxy add.  
  DATE ACTIVATED: JAN 14, 2011

NUMBER: 4649                            IA #: 4649
  FILE NUMBER: 4.3                      GLOBAL ROOT: XMB
  DATE CREATED: MAR 24, 2005            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: STOP/START MAILMAIL BY FILE
  ID: XMB
GLOBAL REFERENCE: XMB(1,
FIELD NUMBER: 10.2                      FIELD NAME: BACKGROUND FILER RUN FLAG
  LOCATION: 0;16                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This Flag will be set to 1 for stopping Mailman and 0 to
 okay it to start again.  This is for the Background filer.  
FIELD NUMBER: 8.15                      FIELD NAME: TCP/IP POLLER RUN FLAG
  LOCATION: 0;18                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This Flag will be set to 1 for stopping Mailman and 0 to
 okay it to start again. This is for the TCP/IP Poller.  
 GENERAL DESCRIPTION:   This is a IA for KIDS new auto patch utility to start
 and stop MailMan.  In the code KIDS will make set the "BACKGROUND FILER RUN
 FLAG" and the "TCP/IP POLLER RUN FLAG" to 1=stop running or 0=okay to run. 
 Some patches require that MailMan be stopped.  This will work in conjunction 
 with IA #4650.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XM
SUBSCRIBING PACKAGE: KERNEL

NUMBER: 4650                            IA #: 4650
  DATE CREATED: MAR 24, 2005            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XMKPL
  NAME: START MAILMAN BY ROUTINES       ID: XMKPL
 GENERAL DESCRIPTION:   This is a IA for KIDS new auto patch utility to start
 and stop MailMan.  In the code KIDS will make reference to START^XMKPL.  Some
 patches require that MailMan be stopped.  This will work in conjunction with
 IA #4649.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XM
COMPONENT/ENTRY POINT: START
 COMPONENT DESCRIPTION:   This routnes will start MailMan.  
SUBSCRIBING PACKAGE: KERNEL

NUMBER: 4651                            IA #: 4651
  DATE CREATED: APR 11, 2005
  CUSTODIAL PACKAGE: HEALTH DATA & INFORMATICS
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HDISVF09
  NAME: DBIA4638-E                      ID: HDISVF09
 GENERAL DESCRIPTION:   The $$GETIEN^HDISVF09 API is used to get the HDIS
 Domain file IEN by the Domain.  
  
 The MFSUP^HDISVF09 API is used in the Master File Server Parameters to update
 the status of the file to Complete and send out the HDR Activation bulletin.  
  STATUS: Active
KEYWORDS: DATA STANDARDIZATION
COMPONENT/ENTRY POINT: $$GETIEN(HDISDOM,.HDISDIEN)
 COMPONENT DESCRIPTION:   Get the HDIS Domain file IEN 
  
 Example: 
  
  N TMP 
  S TMP=$$GETIEN^HDISVF09("ALLERGIES",.DOMPTR) 
VARIABLES: HDISDOM                      TYPE: Input
 VARIABLES DESCRIPTION:   Domain 
VARIABLES: HDISDIEN                     TYPE: Output
 VARIABLES DESCRIPTION:   HDIS Domain file IEN 
VARIABLES: $$GETIEN                     TYPE: Output
 VARIABLES DESCRIPTION:   1=Successful and 0=Failure 
COMPONENT/ENTRY POINT: MFSUP(HDISFILE,HDISERR,HDISFN)
 COMPONENT DESCRIPTION:   This API should be invoked in the Post-Processing
 Logic field in the Master File Parameter file (#4.001) for the file being
 standardized.  The API updates the status of the file to VUID Implementation
 Completed and sends out the HDR Activation bulletin.  
  
 Example: 
  
 This is an example of the Post-Processing Logic Field for the GMRV Vital 
 Category file (#120.53) which is part of the Vitals Domain: 
   
 POST-PROCESSING LOGIC: 
   D MFSUP^HDISVF09(120.53,$G(ERROR)),EN^GMVUID($G(ERROR)) 
VARIABLES: HDISFILE                     TYPE: Input
 VARIABLES DESCRIPTION:   File Number of file just updated 
VARIABLES: HDISERR                      TYPE: Input
 VARIABLES DESCRIPTION:   Error indicator from MFS (1 or 0) 
VARIABLES: HDISFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Field number (Optional) 

NUMBER: 4652                            IA #: 4652
  DATE CREATED: APR 01, 2005            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDUTL2
  NAME: CLNCHK - SDUTL2 (RESTRICTING STOP CODE)
  ID: SDUTL2
 GENERAL DESCRIPTION:   The purpose of API CLNCK^SDUTL2 is to determine whether
 a Clinic entry in the HOSPITAL LOCATION File #44 has conforming stop codes.
 Stop codes are stored in the CLINIC STOP File #40.7 and are used in accordance
 to their assigned restriction types.  Stops codes with restriction type 'P' 
 can only be used in the primary stop code position. Stop codes with 
 restriction type 'S' can only be used in the secondary stop code position. 
 Stop codes with restriction type 'E' can be used in either the primary or 
 secondary stop code position 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: STOP CODES
KEYWORDS: RESTRICTING STOP CODES
KEYWORDS: SDUTL2
COMPONENT/ENTRY POINT: $$CLNCK(CLN,DSP)
 COMPONENT DESCRIPTION:   Checks a clinic for valid stop code restriction. 
 Returns 1 if stop code conforms or 0 and error message.  
VARIABLES: CLN                          TYPE: Input
 VARIABLES DESCRIPTION:   Clinic IEN in HOSPITAL LOCATION File #44.  
VARIABLES: DSP                          TYPE: Input
 VARIABLES DESCRIPTION:   Interactive display of error message, 1 - Display or
 0 No Display.  
VARIABLES: $$CLNCK                      TYPE: Output
 VARIABLES DESCRIPTION:   1  if clinic has conforming stop code, or 0^error
 message (if clinic has non-conforming stop codes) 
SUBSCRIBING PACKAGE: EVENT CAPTURE
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER

NUMBER: 4653                            IA #: 4653
  DATE CREATED: APR 06, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMVUTL8
  NAME: GMVUTL8                         ID: GMVUTL8
 GENERAL DESCRIPTION:   This agreement supports the GMVUTL8 routine entry
 points listed below.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$QUALIFRS(IEN)
 COMPONENT DESCRIPTION:   This function returns the external values of the
 QUALIFIER (#5) multiple field for an entry in the GMRV VITAL MEASUREMENT
 (#120.5) file. The qualifier values are separated by a comma.  
  
  Example: 
  > S IEN=488 
  > W $$QUALIFRS^GMVUTL8(IEN) 
  > L ARM,SITTING,CUFF,ADULT 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN is the internal entry number of an entry in the
 GMRV VITAL MEASUREMENT (#120.5) file.  
VARIABLES: $$QUALIFRS                   TYPE: Output
 VARIABLES DESCRIPTION:   A string that contains the results of the function.  
COMPONENT/ENTRY POINT: $$SUPO2(IEN)
 COMPONENT DESCRIPTION:   This function returns the external value of the
 SUPPLEMENTAL O2 (#1.4) field for an entry in the GMRV VITAL MEASUREMENT
 (#120.5) file.  
  
  Example: 
  > S IEN=489 
  > W $$SUPO2^GMVUTL8(IEN) 
  > 2 l/min 90% 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN is the internal entry number of an entry in the
 GMRV VITAL MEASUREMENT (#120.5) file.  
VARIABLES: $$SUPO2                      TYPE: Output
 VARIABLES DESCRIPTION:   A string that contains the results of the function.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4654                            IA #: 4654
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: GMV V/M ALLDATA
  REMOTE PROCEDURE: GMV V/M ALLDATA
 GENERAL DESCRIPTION:   
  NAME: GMV V/M ALLDATA 
  TAG: VMDATA                          
  ROUTINE: GMVGGR1 
  RETURN VALUE TYPE: GLOBAL ARRAY      
  AVAILABILITY: SUBSCRIPTION 
  INACTIVE: ACTIVE                     
  WORD WRAP ON: TRUE 
  DESCRIPTION:   
  This remote procedure call lists all vitals/measurements data for a given 
  date/time span.  
   
  This remote procedure call is documented in Integration Agreement 4654.  
  INPUT PARAMETER: GMVDATA               
  PARAMETER TYPE: LITERAL 
  MAXIMUM DATA LENGTH: 60              
  REQUIRED: YES 
  SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  GMVDATA consists of 4 pieces of data: 
   
   piece1^piece2^piece3^piece4 
   
   where piece1 = File 2 IEN (i.e., DFN) 
         piece2 = Start date/time for search (FileMan internal format) 
         piece3 = End date/time for search (FileMan internal format) 
         piece4 = 0 (zero) 
  
  RETURN PARAMETER DESCRIPTION:   
  RESULT array returns the data or a "NO DATA" message.  
   
  Case A: The NO DATA message is returned.  
   
  The TMP global returns: 
   ^TMP($J,1)=lastname,first  social security number  date of birth  age 
              "(Yrs)" gender 
   ^TMP($J,2)="Unit:" unit  "Room:" room 
   ^TMP($J,3)="Division:" division 
   ^TMP($J,4)= search date range 
   ^TMP($J,5)="NO DATA" 
   
  Example: 
   > S GMVDATA="90^3051012^3051012^0" 
   > D VMDATA^GMVGGR1(.RESULT,GMVDATA) ZW RESULT 
   > RESULT="^TMP(539349605)" 
   > D ^%G 
   > Global ^TMP($J 
   > ^TMP(539349605,1)=VITPATIENT,ONE 000-11-1234  JAN 2,1934  71 (Yrs)  
                       MALE 
                    2)=Unit:    Room: 
                    3)=Division: 
                    4)=OCT 11,2005 - OCT 11,2005 
                    5)=NO DATA 
   
   
  Casee B: Fourth piece of GMVDATA (Flag) is 0 
   
  The TMP global returns: 
   ^TMP($J,1)=lastname,first social security number  date of birth  age 
              "(Yrs)" sex 
   ^TMP($J,2)="Unit:" unit  "Room:" room 
   ^TMP($J,3)="Division:" division 
   ^TMP($J,4)= search date range 
   ^TMP($J,n)=piece1 through piece23 
   
   where piece1 = date of reading in mm-dd-yy format 
         piece2 = time of reading in hh:mm:ss format 
         piece3 = Temperature value and qualifier abbreviations 
         piece4 = Pulse value and qualifier abbreviations 
         piece5 = Respiration and qualifier abbreviations 
         piece6 = Pulse Oximetry value, qualifier abbreviations, flow rate 
                  and percentage value 
         piece7 = Blood Pressure value and qualifier abbreviations 
         piece8 = Weight value (pounds) and qualifier abbreviations 
         piece9 = Weight value (kilos) 
         piece10 = Body Mass Index calculation 
         piece11 = Height value (inches) and qualifier abbreviations 
         piece12 = Height value (centimeters) 
         piece13 = Circumference Girth value (inches) and qualifier 
                   abbreviations 
         piece14 = Circumference Girth value (centimeters) 
         piece15 = Central Venous Pressure value (cmH2O) 
         piece16 = Central Venous Pressure value (mmHg) 
         piece17 = Input value (from Intake & Output package) 
         piece18 = Output value (from Intake & Output package) 
         piece19 = Pain value 
         piece20 = always null 
         piece21 = always null 
         piece22 = hospital location (FILE 44, Field .01) 
         piece23 = name of person who entered the data (FILE 200, Field 
                   .01) 
   
  Example: 
   > S GMVDATA="134^3050901^3050930^0"          
   > D VMDATA^GMVGGR1(.RESULT,GMVDATA) ZW RESULT 
   > RESULT="^TMP(539349605)" 
   > D ^%G 
   > Global ^TMP($J 
   > ^TMP(539349605,1)=VITPATIENT,TWO 000-11-1234  JUN 1,1957  48 (Yrs)  
                       FEMALE 
                    2)=Unit: 2-ASM   Room: 
                    3)=Division: TEST HINES 
                    4)=SEP 1,2005 - SEP 30,2005 
                    5)=09-14-05^17:18:00^^^^^^135- A St^61.36^22^66- 
                       A^167.64^^^^^^^^ ^^2-ASM^VITPROVIDER,ONE 
                    6)=09-26-05^11:30:57^^^^^120/80*- La Si Car 
                       Clf^^^^^^^^^^^^^^^2-A SM^VITPROVIDER,TWO 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4655                            IA #: 4655
  DATE CREATED: MAY 02, 2005            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PSB MOB DRUG LIST
  REMOTE PROCEDURE: PSB MOB DRUG LIST
 GENERAL DESCRIPTION:   Used by the BCMA/CPRS Med Order Button to return an
 array of drug.  
  
 Results[0] = the number of items passed in the array Results[1] = ^1 either
 DD, SOL, ADD 
              ^2 IEN from drug file 50 
              ^3 Drug Name 
              ^4 Pharmacy Orderable Item IEN 
              ^5 Pharmacy Orderable Item Name 
              ^6 CPRS Orderable Item IEN 
              ^7 CPRS Orderable Item Name 
  STATUS: Active
KEYWORDS: BCMA
KEYWORDS: PSB
KEYWORDS: DRUG LIST
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4656                            IA #: 4656
  DATE CREATED: MAY 02, 2005            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PSB TRANSACTION
  REMOTE PROCEDURE: PSB TRANSACTION
 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.  Results of the processed transaction is
 communicated via the RESULTS array.  The number of RESULTS subscripts used (n)
 will be presented in RESULTS[0].  RESULTS [1..n] will contain the RESULTS
 message.  
  
 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
KEYWORDS: BCMA
KEYWORDS: PSB
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4657                            IA #: 4657
  DATE CREATED: MAY 02, 2005            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PSB MED LOG LOOKUP
 GENERAL DESCRIPTION:   BCMA Medication Log Look Up Remote Procedures.  
  
 This routine is a conglomerate of  Medication Log lookup functionality per the
 BCMA Graphical User Interface software.  
  
 Input:  PSBREC (array) 
         PSBREC (0)     determine  "lookup" function 
                       "PTLKUP" (patient file (#2) lookup) 
                       "ADMLKUP" (MedLog administration lookup) 
                       "SELECTAD" (selected admin.) 
                (1)     values to use per lookup. (DFN per ADMLKUP) 
                        value of selected item. (PSB IEN per SELECTAD) 
                (2)     search date per ADMLKUP 
  
 Output: RESULTS (array) 
         RESULTS(0)    number of lookup matches 
                (1)    error message or data per match/selection 
                (n)    data per subsequent match/selection.  
  
 "PTLKUP" results data format: RPC Call: PSB MED LOG LOOKUP RESULTS(0) = 1 
 RESULTS(1) = piece 1         Patient's DFN               ("-1" if
 error/message) piece 2         Patient's Name piece 3         Sex piece 4      
   Date of Birth (FM format) piece 5         Social Security Number piece 6     
    "" piece 7         "" piece 8         "" piece 9         "" piece 10       
 Date Of Birth (displayable format) piece 11        Social Security Number
 (displayable format) 
  
  
 "ADMLKUP" results data format: RESULTS(0)=Number of lines returned.  
  
 RESULTS(1)= piece 1         DFN of Patient piece 2         DATE of Activity 
 piece 3         Orderable Item_" "_Dosage Form piece 4         IV Unique ID 
 piece 5         Action Status piece 6         Schedule Type piece 7        
 Action Date/Time (FileMan) piece 8         Action By Initials piece 9        
 PRN Reason piece 10        PRN Effectiveness 
  
  
 "SELECTAD" results data format: RESULTS(0)=Number of lines returned.  
  
 RESULTS(1)= piece 1         PSBIEN of the administration selected for edit.
 ("-1" if error/m piece 2         DFN of Patient                               
 piece 3         Patient Name piece 4         SSN piece 5         Medication 
 piece 6         BagID piece 7         AdminStat piece 8         "for possible
 later use" piece 9         AdminD/T piece 10        InjctSt piece 11       
 "IV"/"PB"/"UD" piece 12        "for possible later use" piece 13        Order
 Status piece 14        Schedul. Type piece 15        Order Number_U/V piece 16 
       Order has given patch or infusing IVbag - Flag 
  
 RESULTS(2)= piece 1         PRN Reason piece 2         PRN Effectiveness 
  
 RESULTS(3..n) [for each dd/add/sol] = piece 1         "DD"/"ADD"/"SOL" piece 2 
        drug IEN piece 3         drug Name piece 4         Units Ordered piece
 5         Units Given piece 6         Units of Administration 
  STATUS: Active
KEYWORDS: BCMA
KEYWORDS: PSB
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 4658                            IA #: 4658
  DATE CREATED: OCT 11, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LRRPU
  NAME: DBIA4658                        ID: LRRPU
 GENERAL DESCRIPTION:   Laboratory API to retrieve from LAB DATA file #63
 laboratory test results associated with the "CH" subscript. In addition to the
 actual test result, it also returns those values associated with the test
 result such as normality, units, normals, performing laboratory and associated
 order and result codes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$TSTRES
 COMPONENT DESCRIPTION:   Entry point to return a test result and associated
 information for a specific test result stored with the "CH" subscript of the
 LAB DATA file (#63).  
VARIABLES: LRDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient 's record
 in LAB DATA file #63.  
VARIABLES: LRSS                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript in file #63, currently only "CH" supported. 
 
VARIABLES: LRIDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Inverse date/time of result being requested.  
VARIABLES: LRDN                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of data name in file #63 "CH" subscript 
VARIABLES: LR60                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file 60 test related to this dataname
 (optional).  
VARIABLES: LRCODE                       TYPE: Input
 VARIABLES DESCRIPTION:   1 - return NLT/LOINC codes (optional).  
VARIABLES: LRY                          TYPE: Output
 VARIABLES DESCRIPTION:   Test result is returned as a "^" delimited string.  
  
  result^normalcy flag^reference low^reference high^units^ 
  performing lab (file #4 ien)^therapeutic normal used (0=no/1=yes)^ 
  NLT order code;NLT name!NLT result code;NLT name!LOINC result code;LOINC
 name^ 
  performing user(DUZ)^EII 
  
  PIECE | PARAMETER 
  -------------------
  1     | result 
  2     | normalcy (L=low, H=high, L*=critical low, H*=critical high) 
  3     | reference low 
  4     | reference high 
  5     | units 
  6     | performing laboratory 
          - pointer to INSTITUTION file (#4) 
  7     | therapeutic normal used (0=no/1=yes) 
  8     | National Laboratory Test order code;NLT order code name 
          !NLT result code; NLT result code name 
          !LOINC result code; LOINC result code name 
          (This piece returns multiple codes delimited by 
          "!" within each code it's further delimited by ";" 
          to indicate the code and the code text) 
  9     | User who performed the test 
          - pointer to NEW PERSON file (#200) 
  10    | Equipment Instance Identifier (EII) 
          - make/model/serial of instrument 
  
  
  An example of output: 
  S LRY=$$TSTRES^LRRPU(905,"CH",6949781.836081,5,"",1) 
  
  LRY=155^H*^135^148^MMOL/L^170^0^81116.0000;Auto Chem 9
 test!84295.0000;Sodium!2951;SODIUM:SCNC:PT:SER/PLAS:QN^235^ 
  
  Piece  | Value 
  1      | 155 
  2      | H* 
  3      | 135 
  4      | 148 
  5      | MMOL/L 
  6       | 170 
  7      | 0 
  8      | 81116.0000;Auto Chem 9
 test!84295.0000;Sodium!2951;SODIUM:SCNC:PT:SER/PLAS:QN 
  8.1    | 81116.0000;Auto Chem 9 test 
  8.2    | 84295.0000;Sodium 
  8.3    | 2951;SODIUM:SCNC:PT:SER/PLAS:QN 
  9      | 235 
  
  
  S LRY=$$TSTRES^LRRPU(61,"CH",7049475.91,452,"",1) 
  LRY=116^H^30^90^mm Hg^170^0^82884.0000;Blood Gas POC!82880.0000;PO2 Direct
 Reading!2703;OXYGEN:PPRES:PT:BLDA:QN^235^;;UJ32018960;Roche GTS/HQ/Inform 
  
  Piece  | Value 
  1      | 116 
  2      | H 
  3      | 30 
  4      | 90 
  5      | mm HG 
  6      | 170 
  7      | 0 
  8       | 82884.0000;Blood Gas POC!82880.0000;PO2 Direct
 Reading!2703;OXYGEN:PPRES:PT:BLDA:QN 
  8.1    | 82884.0000;Blood Gas POC 
  8.2    | 82880.0000;PO2 Direct Reading 
  8.3    | 2703;OXYGEN:PPRES:PT:BLDA:QN 
  9      | 235 
  10     | ;;UJ32018960;Roche GTS/HQ/Inform 
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
SUBSCRIBING PACKAGE: HEALTH SUMMARY
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   ADDED 6/6/2011 

NUMBER: 4659                            IA #: 4659
  DATE CREATED: MAY 30, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORRDI1
  NAME: RDI DOMAIN CALL                 ID: ORRDI1
 GENERAL DESCRIPTION:   This integration agreement allows packages to use the
 Remote Data Interoperability (RDI) functionality.  
  STATUS: Active
KEYWORDS: RDI
COMPONENT/ENTRY POINT: $$GET(DFN,DOMAIN)
 COMPONENT DESCRIPTION:   Return remote data from the Health Data Repository
 (HDR).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number (IEN) of the patient in the
 PATIENT file (#2).  
VARIABLES: DOMAIN                       TYPE: Input
 VARIABLES DESCRIPTION:   The type of data to return. Possible values are "ART"
 for adverse reaction tracking data and "PSOO" for outpatient pharmacy data.  
VARIABLES: $$GET                        TYPE: Output
 VARIABLES DESCRIPTION:   The number of records returned from HDR. If an error
 occurred, a caret-delimited string is returned. The first caret piece is -1
 and the second caret piece is the error message.  
VARIABLES: XTMP("ORRDI") GLOBAL         TYPE: Output
 VARIABLES DESCRIPTION:   Remote data is returned in nodes descendant from this
 node.  
  
 Data Format: 
  
 ^XTMP("ORRDI","ART",DFN,COUNT, 
   DFN - corresponds to the DFN input parameter.  
   COUNT - number that starts at one and increments 
           by one for each subsequent adverse 
           reaction 
   DESCENDANT NODE 
     CORRESPONDING               CORRESPONDING 
      LOCAL FIELD                 LOCAL FILE 
   ===================================================
   "AUTHOR",0) 
     ORIGINATOR (#5)             PATIENT ALLERGIES 
                                 (#120.8) 
     Value: Caret-delimited string 
            PIECE  VALUE 
            ============
            1      FAMILY (LAST) NAME 
            2      GIVEN (FIRST) NAME 
            3      MIDDLE NAME 
  
   "DRUG CLASSES",COUNT) 
     DRUG CLASSES (#3)           PATIENT ALLERGIES 
                                 (#120.8) 
     COUNT - number that starts at one for the 
             first drug class and increments by one 
             for each subsequent drug class 
     Value: Caret-delimited string 
            PIECE  VALUE 
            ============
            1      VUID field (#99.99) in the VA 
                   DRUG CLASS file (#50.605) 
            2      CLASSIFICATION field (#1) in the 
                   VA DRUG CLASS file (#50.605) 
            3      Coding System 
            4      CODE field (#.01) in the VA DRUG 
                   CLASS file (#50.605) 
  
   "DRUG INGREDIENTS",COUNT) 
     DRUG INGREDIENTS (#2)       PATIENT ALLERGIES 
                                 (#120.8) 
     COUNT - number that starts at one for the 
             first drug ingredient and increments 
             by one for each subsequent drug 
             ingredient 
     Value: Caret-delimited string 
            PIECE  VALUE 
            ============
            1      VUID field (#99.99) in the DRUG 
                   INGREDIENTS file (#50.416) 
            2      NAME field (#.01) in the DRUG 
                   INGREDIENTS file (#50.416) 
            3      Coding System 
   "FACILITY",0) 
     Remote site that documented this adverse 
     reaction 
     Value: Caret-delimited string 
            PIECE  VALUE 
            ============
            1      IEN in the INSTITUTION file (#4) 
            2      NAME field (#.01) in the 
                   INSTITUTION file (#4) 
            3      STATION NUMBER field (#99) in 
                   the INSTITUTION file (#4) 
   "GMRALLERGY",0) 
      GMR ALLERGY (#1)           PATIENT ALLERGIES 
                                 (#120.8) 
      Value: Caret-delimited string 
              PIECE  VALUE 
              ============
              1      VUID field (#99.99) in either 
                     the GMR ALLERGIES file 
                     (#120.82), VA GENERIC file 
                     (#50.6), VA DRUG CLASS file 
                     (#50.605) or DRUG INGREDIENTS 
                     file (#50.416) 
              2      Field #.01 in either the GMR 
                     ALLERGIES file (#120.82), VA 
                     GENERIC file (#50.6), VA DRUG 
                     CLASS file (#50.605) or DRUG 
                     INGREDIENTS file (#50.416) 
              3      Coding System 
                     First four characters are 
                     "99VA" followed by the file 
                     number from which the data 
                     value comes 
   "MECHANISM",0) 
     MECHANISM (#17)             PATIENT ALLERGIES 
                                 (#120.8) 
     Value: Caret-delimited string 
            PIECE  VALUE 
            ============
            1      VUID field (#99.99) in the XTID 
                   VUID FOR SET OF CODES file 
                   (#8985.1) 
            2      External format 
            3      Coding System 
   "OBS/HISTORICAL",0) 
     OBSERVED/HISTORICAL (#6)    PATIENT ALLERGIES 
                                 (#120.8) 
     Value: Caret-delimited string 
            PIECE  VALUE 
            ============
            1      VUID field (#99.99) in the XTID 
                   VUID FOR SET OF CODES file 
                   (#8985.1) 
            2      External format 
            3      Coding System 
   "ORIGINATION DATE/TIME",0) 
     ORIGINATION DATE/TIME (#4)  PATIENT ALLERGIES 
                                 (#120.8) 
     Value: Health Level 7 (HL7) formatted date/ 
            time string 
   "REACTANT",0) 
     REACTANT (#.02)             PATIENT ALLERGIES 
                                 (#120.8) 
     Value: Text string 
   "SEVERITY",0) 
     SEVERITY (#14.5)            ADVERSE REACTION 
                                 REPORTING 
                                 (#120.85) 
     Value: Caret-delimited string 
            PIECE  VALUE 
            ============
            1      Internal format 
            2      External format 
   "SIGNS/SYMPTOMS",COUNT) 
     REACTIONS (#10)             PATIENT ALLERGIES 
                                 (#120.8) 
     COUNT - number that starts at one for the 
             first sign or symptom and increments 
             by one for each subsequent sign or 
             symptom 
     Value: Caret-delimited string 
            PIECE  VALUE 
            ============
            1      VUID field (#99.99) in the 
                   SIGN/SYMPTOMS file (#120.83) 
            2      NAME field (#.01) in the SIGN/ 
                   SYMPTOMS file (#120.83) 
            3      Coding System 
   "SIGNS/SYMPTOMS",COUNT,"DATE_ENTERED",0) 
     DATE ENTERED (#3) sub-      PATIENT ALLERGIES 
     field in the REACTIONS      (#120.8) 
     field (#10) 
     Value: HL7 formatted date/time string 
   "TYPE",0) 
     ALLERGY TYPE (#3.1)         PATIENT ALLERGIES 
                                 (#120.8) 
     Value: Caret-delimited string 
            PIECE  VALUE 
            ============
            1      Internal Format 
            2      External Format 
            3      Coding System 
   "VERIFIED",0) 
     VERIFIED (#19)              PATIENT ALLERGIES 
                                 (#120.8) 
     Value: External Format 
   "ASSESSMENT",COUNT) 
     REACTION ASSESSMENT (#1)    ADVERSE REACTION 
                                 ASSESSMENT 
                                 (#120.86) 
     COUNT - number that starts at one for the 
             first assessment and increments by 
             one for each subsequent assessment 
     Value: Caret-delimited string 
            PIECE  VALUE 
            ============
            1      VUID field (#99.99) in the XTID 
                   VUID FOR SET OF CODES file 
                   (#8985.1) 
            2      External Format 
            3      Coding System 
   "ASSESSMENT",COUNT,"FACILITY",0) 
     Remote site that documented this assessment 
     COUNT - corresponds to the COUNT node in 
             "ASSESSMENT",COUNT) 
     Value: Caret-delimited string 
            PIECE  VALUE 
            ============
            1      IEN in the INSTITUTION file (#4) 
            2      NAME field (#.01) in the 
                   INSTITUTION file (#4) 
            3      STATION NUMBER field (#99) in 
                   the INSTITUTION file (#4) 
  
 ^XTMP("ORRDI","PSOO",DFN,COUNT, 
   DFN - corresponds to the DFN input parameter.  
   COUNT - number that starts at one and increments 
           by one for each subsequent outpatient 
           prescription 
   DESCENDANT NODE  DATA VALUE 
   ===========================
     1,0)           Facility Name 
     2,0)           DN 
     3,0)           Drug VUID 
     4,0)           RX 
     5,0)           ST 
     6,0)           QT;DS 
     7,0)           EX 
     8,0)           ID 
     9,0)           FD 
     10,0)          RF 
     11,0)          PR 
     12,0)          CF 
     14,0)          SIG 
COMPONENT/ENTRY POINT: $$HAVEHDR
 COMPONENT DESCRIPTION:   Determine if the local system has an HDR connection.  
VARIABLES: $$HAVEHDR                    TYPE: Output
 VARIABLES DESCRIPTION:   Possible values are one for yes, the local system has
 a HDR connection and zero for no, the local system does not have a HDR
 connection.  
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: HEALTH SUMMARY
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
  DATE ACTIVATED: JUN 03, 2014

NUMBER: 4660                            IA #: 4660
  GLOBAL ROOT: XTMP('ORRDI',            DATE CREATED: APR 11, 2005
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RDI DOMAIN GLOBAL
  ID: XTMP('ORRDI',
 GENERAL DESCRIPTION:   The purpose of this DBIA is to provide subscribing
 applications the ability to read the return data from API call GET^ORRDI1
 (DBIA 4659.)  This data is stored in the following temp global: 
  
 Pharmacy format: 
   ^XTMP("ORRDI","PSOO",DFN,D0,1,0)=Facility Name 
   ^XTMP("ORRDI","PSOO",DFN,D0,2,0)=DN 
   ^XTMP("ORRDI","PSOO",DFN,D0,3,0)=Drug VUID 
   ^XTMP("ORRDI","PSOO",DFN,D0,4,0)=RX 
   ^XTMP("ORRDI","PSOO",DFN,D0,5,0)=ST 
   ^XTMP("ORRDI","PSOO",DFN,D0,6,0)=QT;DS 
   ^XTMP("ORRDI","PSOO",DFN,D0,7,0)=EX 
   ^XTMP("ORRDI","PSOO",DFN,D0,8,0)=ID 
   ^XTMP("ORRDI","PSOO",DFN,D0,9,0)=FD 
   ^XTMP("ORRDI","PSOO",DFN,D0,10,0)=RF 
   ^XTMP("ORRDI","PSOO",DFN,D0,11,0)=PR 
   ^XTMP("ORRDI","PSOO",DFN,D0,12,0)=CF 
   ^XTMP("ORRDI","PSOO",DFN,D0,14,D1)=SIG Allergies format: 
   ^XTMP("ORRDI","ART",DFN,D0,"REACTANT",0)= Allergy Reactant 
   ^XTMP("ORRDI","ART",DFN,D0,"DRUG CLASSES",1)=Drug Class 1 
   ......
   ^XTMP("ORRDI","ART",DFN,D0,"DRUG CLASSES",n)=Drug Class n 
   ^XTMP("ORRDI","ART",DFN,D0,"DRUG INGREDIENTS",0)=Drug Ing. 1 
   ......  
   ^XTMP("ORRDI","ART",DFN,D0,"DRUG INGREDIENTS",n)=Drug Ing. n 
  
  
  
  STATUS: Active
KEYWORDS: RDI
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: JUL 10, 2007

NUMBER: 4661                            IA #: 4661
  DATE CREATED: APR 12, 2005            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RMPRFC3
  NAME: API FOR PROCESSING PROSTHETIC IFC
  ID: RMPRFC3
 GENERAL DESCRIPTION:   The API called at EN^RMPRFC3 is used to process
 Prosthetics Interfacility Consults' data and file the data into the
 Prosthetics package's suspense system.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This is the primary entry point for processing
 Prosthetics Interfacility Consult HL7 messages.  It is called at EN^RMPRFC3.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Consult/Request Tracking has added a call to EN^RMPRFC3
 at the request of Prosthetics to allow Prosthetics to act on Consult HL7
 messages.  
  DATE ACTIVATED: JUN 12, 2009

NUMBER: 4662                            IA #: 4662
  DATE CREATED: APR 26, 2005
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSS50P7
  NAME: DBIA4662                        ID: PSS50P7
 GENERAL DESCRIPTION:   This API will return information from the PHARMACY
 ORDERABLE ITEM file (#50.7).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DRGIEN(PSSIEN,PSSFL,LIST)
 COMPONENT DESCRIPTION:   This API will return a list of drugs from the DRUG
 file (#50) that are matched to an entry in the PHARMACY ORDERABLE ITEM file
 (#50.7).  
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the PHARMACY
 ORDERABLE ITEM file (#50.7). [required] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   This parameter represents the inactive date, in
 FileMan format.  If no date is passed in, all entries matched to the Pharmacy
 Orderable Item will be returned. If a date is passed in, only entries without
 an inactive date and entries with an inactive date later than this date will
 be returned.  [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   This will be the name subscript in the return ^TMP
 global. [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)= Total entries returned. If there are
 no entries being returned, then this will be equal to "-1^NO DATA FOUND".  
  
 ^TMP($J,LIST,PSS50)="" 
  
 Where PSS50 is the internal entry number from the DRUG file (#50).  
COMPONENT/ENTRY POINT: ZERO(PSSIEN,PSSFT,PSSFL,LIST)
 COMPONENT DESCRIPTION:   Returns the zero node of the PHARMACY ORDERABLE ITEM
 file (#50.7) in the ^TMP array.  A check for the existence of the zero node
 will be performed.  External format will be included if applicable.  
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of entry in the PHARMACY ORDERABLE ITEM file
 (#50.7) [optional] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   NAME field (#.01) of the PHARMACY ORDERABLE ITEM file
 (#50.7) (a value of "??" may be used) [optional] 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   Inactive date: A null value will return all entries
 (entry of a FileMan format date (ex: 3030917) will return active entries after
 this date) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript value in ^TMP($J,LISTvalue,  [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0) = Total entries returned or -1^NO
 DATA FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01) = NAME (50.7,.01) 
  
 ^TMP($J,LIST,PSSIEN,.02) = DOSAGE FORM(50.7,.02)^NAME (50.606,.01) 
  
 ^TMP($J,LIST,PSSIEN,.03) = IV FLAG (50.7,.03)^External format for the set of
 codes (ex: 1 if flagged for IV) 
  
 ^TMP($J,LIST,PSSIEN,.04) = INACTIVE DATE (50.7,.04)^External format (ex: SEP
 12,1999) 
  
 ^TMP($J,LIST,PSSIEN,.05) = DAY (nD) or DOSE (nL) LIMIT (50.7,.05) 
  
 ^TMP($J,LIST,PSSIEN,.06) = MED ROUTE (50.7,.06)^NAME (51.2,.01) 
  
 ^TMP($J,LIST,PSSIEN,.07) = SCHEDULE TYPE (50.7,.07)^External format for the
 set of codes 
  
 ^TMP($J,LIST,PSSIEN,.08) = SCHEDULE (50.7,.08) 
  
 ^TMP($J,LIST,PSSIEN,.09) = SUPPLY (50.7,.09)^External format for the set of
 codes 
  
 ^TMP($J,LIST,PSSIEN,5) = FORMULARY STATUS (50.7,5)^External format for the set
 of codes 
  
 ^TMP($J,LIST,PSSIEN,8) = NON-VA MED (50.7,8)^External format for the set of
 codes (ex: 1 flagged the med as Non-VA) 
  
 ^TMP($J,LIST,"B",NAME,PSSIEN) = "" 
COMPONENT/ENTRY POINT: SSET(PSSC,PSSCNT,PSSI,DIR,SUB)
 COMPONENT DESCRIPTION:   Returns a subset of orderable items.  
VARIABLES: PSSC                         TYPE: Input
 VARIABLES DESCRIPTION:   Count (number wheel) used when populating the return
 ^TMP global.  
VARIABLES: PSSCNT                       TYPE: Input
 VARIABLES DESCRIPTION:   Number of items to return at one time.  
VARIABLES: PSSI                         TYPE: Input
 VARIABLES DESCRIPTION:   Starting location for the 'B' cross-reference.  
VARIABLES: DIR                          TYPE: Input
 VARIABLES DESCRIPTION:   
  1 - Process 'B' cross-reference backwards.  -1 - Process 'B' cross-reference
 backwards.  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   The subscript to use to return data in the ^TMP
 global.  
VARIABLES: ~TMP(SUB,$J,1,PSSC)          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP(SUB,$J,1,PSSC)=IEN of the Orderable Item ^ NAME
 (#.01) ^ DOSAGE FORM (from 50.606) ^ External form of INACTIVE DATE (#.04) 
COMPONENT/ENTRY POINT: NAME
 COMPONENT DESCRIPTION:   Returns the NAME field (#.01) of the PHARMACY
 ORDERABLE ITEM file (#50.7).  
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN = entry in PHARMACY ORDERABLE ITEM file (#50.7) 
VARIABLES: $$NAME                       TYPE: Output
 VARIABLES DESCRIPTION:   $$NAME = NAME field (#.01) of the PHARMACY ORDERABLE
 ITEM file (#50.7) 
COMPONENT/ENTRY POINT: INDCATN
 COMPONENT DESCRIPTION:   This API will return a list of Indications for use
 for a given entry in the PHARMACY ORDERABLE ITEM file (#50.7).  
VARIABLES: Input
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the PHARMACY
 ORDERABLE ITEM file (#50.7). [required] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   This will be the name subscript in the return ^TMP
 global. [required] 
VARIABLES: ~TMP or None                 TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,Seq#) if the 'Most Common Indication For
 Use' and 'Indications For Use' are populated.  
  
 ^TMP($J,LIST,"OTH",Seq#) if there are other language,'Other Language Most 
 Common Indication' and 'Other Language Indications' are populated.  
  
 Will not return a TMP global if Indications are not populated.  
  
 The Seq# for 'Most Common Indication For Use' or 'Other Language Most Common
 Indication' is always set to '1' if populated.  
                             
 Ex: 
  
 ^TMP(547627655,"PSO",1)="FOR CHOLESTEROL^1" ^TMP(547627655,"PSO",2)="TO LOWER
 BAD CHOLESTEROL" ^TMP(547627655,"PSO",3)="TO RAISE GOOD CHOLESTEROL" 
  
 ^TMP(547627655,"PSO","OTH",1)="PARA COLESTEROL^1" 
 ^TMP(547627655,"PSO","OTH",2)="PARA BAJAR COLESTEROL MALO" 
 ^TMP(547627655,"PSO","OTH",3)="PARA AUMENTAR COLESTEROL BUENO" 
  DATE ACTIVATED: MAY 22, 2019

NUMBER: 4663                            IA #: 4663
  DATE CREATED: MAY 23, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBBAPI
  NAME: PFSS ON/OFF SWITCH              ID: IBBAPI
 GENERAL DESCRIPTION:   The function $$SWSTAT^IBBAPI provides the calling
 application with the status of the PFSS On/Off Switch.  When the switch is
 "ON", the calling application should proceed with processing required to 
 conform with PFSS functionality.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PFSS
COMPONENT/ENTRY POINT: $$SWSTAT
 COMPONENT DESCRIPTION:   The SWSTAT entry point returns the current value of
 the MASTER SWITCH field (#1.01) of the PFSS SITE PARAMETERS file (#372), and
 the Effective Date/Time of the switch setting.  
  
 Called as $$SWSTAT^IBBAPI().  
VARIABLES: $$SWSTAT                     TYPE: Output
 VARIABLES DESCRIPTION:   <switch_status>^<effective_datetime> Where: 
 <switch_status> 
    0=OFF 
    1=ON <effective_datetime> 
    FileMan internal format; date and time.  
    Date/time at which switch was set to current status.  

NUMBER: 4664                            IA #: 4664
  DATE CREATED: MAY 23, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBBAPI
  NAME: PFSS ACCOUNT                    ID: IBBAPI
 GENERAL DESCRIPTION:   This entry point is added to routine IBBAPI in order to
 accommodate Patient Financial Services System (PFSS) functionality
 requirements for establishing patient accounts in the commercial medical
 billing system.  This entry point is called by a number of VistA applications 
 involved in PFSS.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PFSS
KEYWORDS: ACCOUNT
COMPONENT/ENTRY POINT: $$GETACCT
 COMPONENT DESCRIPTION:   $$GETACCT is used by an application that requires a
 PFSS Account Reference in order to associate a patient visit, encounter, or
 occasion of service to an "account" entity within the commercial medical
 billing system used for PFSS.  
   
 Called as $$GETACCT^IBBAPI(VAR1,VAR2,VAR3,VAR4,.ARR1,.ARR2,.ARR3,.ARR4, 
 .ARR5,VAR5,VAR6,.ARR6) where IBBDFN=VAR1 (required) IBBARFN=VAR2 (required;
 may be null) IBBEVENT=VAR3 (required) IBBAPLR=VAR4 (required; may be null) 
 IBBPV1=ARR1 (required) IBBPV2=ARR2 (optional) IBBPR1=ARR3 (optional) 
 IBBDG1(n)=ARR4 (optional) IBBZCL(n)=ARR5 (optional) IBBDIV=VAR5 (optional) 
 IBBRAIEN=VAR6 (optional) IBBSURG=ARR6 (optional) 
   
 Returns PFSS Account Reference; internal entry number to PFSS ACCOUNT file 
 (#375).  0, if unsuccessful.  
   
 All data passed in is stored in the PFSS ACCOUNT file (#375).  Both the
 internal entry number and #.01 of the record are set to the value of the PFSS
 Account Reference.  This value is the normal return of $$GETACCT, and should
 be retained by the calling application.  
VARIABLES: VAR1                         TYPE: Input
 VARIABLES DESCRIPTION:   Patient Identifier; numeric; standard VistA variable
 DFN.  
  
 VAR1 is required.  
VARIABLES: VAR2                         TYPE: Input
 VARIABLES DESCRIPTION:   PFSS Account Reference; numeric; pointer to PFSS
 ACCOUNT file (#375).  Must be null if requesting a new PFSS Account Number
 Reference.  
  
 VAR2 is required.  
VARIABLES: VAR3                         TYPE: Input
 VARIABLES DESCRIPTION:   HL7 Event Code; free text; e.g.,"A04".  
   
 VAR3 is required.  
VARIABLES: VAR4                         TYPE: Input
 VARIABLES DESCRIPTION:   Application Location Reference; free text;
 tag^routine or routine; e.g.,"EN^SRCHL7A".  
   
 VAR4 is required; may be null.  
VARIABLES: ARR1                         TYPE: Input
 VARIABLES DESCRIPTION:   Array of data elements for HL7 Segment PV1 as
 follows: ARR1(2) = Patient Class; (required) 
           I(npatient) or O(utpatient) ARR1(3) = Patient Location; (required) 
           PTF only - may use "FEE BASIS 
           All others - use pointer to file #44.  ARR1(4) = Appointment Type;
 (optional) 
           Scheduling and PCE only   pointer to file #409.1 ARR1(7) = Attending
 Physician; (required) 
           Pointer to file #200.  ARR1(9) = Consulting Physician; (optional) 
           Pointer to file #200.  ARR1(10) = Purpose of Visit; (optional) 
            Scheduling only; set of codes.  ARR1(17) = Admitting Physician;
 (optional) 
            Pointer to file #200.  ARR1(18) = Primary Stop Code; (optional) 
            Pointer to file #40.7 ARR1(24) = Workload Non-Count; (optional) 
            Scheduling only; Y/N.  ARR1(25) = Check-In Date/Time; (optional) 
            Scheduling only; FileMan date/time; time required.  ARR1(41) =
 Credit Stop Code; (optional) 
            Scheduling only   pointer to file #40.7 ARR1(44) = Admit Date/Time;
 (required, if not A05 event) 
            FileMan date/time; time optional.  ARR1(45) = Discharge Date/Time;
 (optional) 
            Scheduling only; FileMan date/time; time required.  ARR1(50) =
 Alternate Visit ID; (optional) 
            OP Pharmacy only   pointer to file #52.  ARR1(52) = Other Provider;
 (optional) 
            Pointer to file #200.  
   
 Array ARR1 is required, although many elements in the array are optional.  
VARIABLES: ARR2                         TYPE: Input
 VARIABLES DESCRIPTION:   Array of data elements for HL7 Segment PV2 as
 follows: ARR2(7) = Eligibility of Visit; (optional) 
           Scheduling and PCE only - pointer to file #8.1 ARR2(8) = Expected
 Admit Date/Time; (required for A05) 
           FileMan date/time; time optional.  ARR2(24) = Appointment Status;
 (optional) 
            Scheduling only; set of codes.  ARR2(46) = Pt. Status Effective
 Date; (optional) 
            Scheduling - Date appointment made.  
            Prosthetics - Date of order.  
            FileMan date/time; date only.  
   
 If variable VAR3 is "A05", then array ARR2 is required; otherwise, it is
 optional.  
VARIABLES: ARR3                         TYPE: Input
 VARIABLES DESCRIPTION:   Array of data elements for HL7 Segment PR1 as
 follows: ARR3(3) = Procedure Code (required, if PR1(4) is null) 
           Pointer to file #81.  ARR3(4) = Procedure Description (required, if
 PR1(3) is null) 
           Free text; max. 200 characters ARR3(5) = Procedure Date/Time
 (optional) 
           FileMan date/time; time optional.  ARR3(6) = Procedure Functional
 Type (optional) 
           Prosthetics - "O" (Home Oxygen), "P" (Purchasing), 
           "I" (Stock Issue).  
           Radiology - Imaging Type (file #79.2) abbreviation.  ARR3(11) =
 Surgeon (optional) 
            Surgery only; pointer to file #200.  ARR3(16) = Procedure Code
 Modifier(s) (optional) 
            Free text; one or more pointers to file #81.3 
            delimited by ";".  
   
 Array ARR3 is optional.  
VARIABLES: ARR4                         TYPE: Input
 VARIABLES DESCRIPTION:   Array of data elements for HL7 Segment DG1 as
 follows: ARR4(n,3) = Diagnosis Code (required, if ARR4(1,4) is null) 
             Pointer to file #80.  ARR4(1,4) = Diagnosis Description (required,
 if ARR4(1,3) is null) 
             Free text; max. 200 characters.  ARR4(n,6) = Diagnosis Type
 (required) 
             "A" (admitting), "W" (working), "D" (discharging), 
             "F" (final).  
   
 Since there may be more than one diagnosis, ARR4 will have two subscripts. 
 The first subscript is a sequential integer that pertains to a given diagnosis 
  The second subscript refers to the corresponding Sequence number within the
 DG1 Segment.  Diagnoses must be placed in the array in priority order; i.e.,
 primary diagnosis must be first, followed in descending priority order by
 additional diagnoses (if any).  
   
 If diagnosis is sent as free text rather than a pointer to file #80, then only
 one diagnosis may be used and the text must appear in array element ARR4(1,4). 
   
 Array ARR4 is optional.  
VARIABLES: ARR5                         TYPE: Input
 VARIABLES DESCRIPTION:   Array of data elements for HL7 Segment ZCL as
 follows: ARR5(n,2) = Type (required) 
             1 - AO (Agent Orange) 
             2 - IR (Ionizing Radiation) 
             3 - SC (Service Connected) 
             4 - EC (Environmental Contaminants) 
             5 - MST (Military Sexual Trauma) 
             6 - HNC (Head and/or Neck Cancer) 
             7 - CV (Combat Veteran) ARR5(n,3) = Value (required) 
             1 - Yes 
             2 - No 
   
 Each ARR5(n) represents one of the possible SC/EI classifications.  Array ARR5
 is optional.  
VARIABLES: VAR5                         TYPE: Input
 VARIABLES DESCRIPTION:   The calling application may, if necessary, pass a
 pointer to the MEDICAL CENTER DIVISION file (#40.8).  If passed, then the 
 facility identifier is derived from the pointed-to file #40.8 record, which in
 turn points to the INSTITUTION file (#4).  If variable VAR5 is null, then
 facility identifier is derived from the HOSPITAL LOCATION file (#44), pointed
 to by input variable ARR1(3).  The file #44 record also has a pointer to file
 #4.  
   
 VAR5 is optional.  
VARIABLES: VAR6                         TYPE: Input
 VARIABLES DESCRIPTION:   Input variable VAR6 is used only by the Radiology
 application. It contains the pointer to the exam request in the RAD/NUC MED
 ORDERS file (#75.1) for which the account is being created.  
   
 VAR6 is required for Radiology only.  
VARIABLES: ARR6                         TYPE: Input
 VARIABLES DESCRIPTION:   Array ARR6 is used only by the Surgery application.  
 ARR6(1) = Surgery Case # (optional) 
           Pointer to SURGERY file (#130).  ARR6(2) = Surgical Specialty
 (required) 
           Pointer to SURGICAL SPECIALTY file (#45.3).  
   
 ARR6 is required for Surgery only.  
VARIABLES: $$GETACCT                    TYPE: Output
 VARIABLES DESCRIPTION:   If successful, the return value is a pointer to the
 PFSS ACCOUNT file (#375) record, which holds the data provided by the input
 parameters.  Returns 0, if filing to the PFSS ACCOUNT file (#375) is
 unsuccessful.  
COMPONENT/ENTRY POINT: $$SETACCT
 COMPONENT DESCRIPTION:   When account create messages (resulting from
 $$GETACCT) are received by the commercial medical billing system, the account
 is created and assigned an Account Number.  This number is sent back to VistA 
 via HL7 messaging.  
  
 In VistA, the routine that processes the inbound message will call $$SETACCT. 
 This IBB function parses relevant data from the HL7 message using the standard
 VistA HL7 API, locates the correct record in the PFSS ACCOUNT file (#375)
 based on that data, and stores the returned Account Number in the EXTERNAL
 ACCOUNT NUMBER field (#.02).  
  
 Called as $$SETACCT^IBBAPI(VAR1,VAR2) where IBBDFN=VAR1 (required) 
 HLMTIENS=VAR2 (required) 
   
 Returns PFSS Account Reference; internal entry number to PFSS ACCOUNT file 
 (#375).  0, if unsuccessful.  
VARIABLES: VAR1                         TYPE: Input
 VARIABLES DESCRIPTION:   Patient Identifier; numeric; standard VistA variable
 DFN.  
VARIABLES: VAR2                         TYPE: Input
 VARIABLES DESCRIPTION:   Standard VistA HL7 variable; IEN for HL7 MESSAGE
 ADMINISTRATION file (#773).  
VARIABLES: $$SETACCT                    TYPE: Output
 VARIABLES DESCRIPTION:   If successful, the return value is a pointer to the
 PFSS ACCOUNT file (#375) record, which holds the data provided by the input
 parameters.  Otherwise, returns 0.  
COMPONENT/ENTRY POINT: $$EXTNUM
 COMPONENT DESCRIPTION:   It may be necessary for applications to retrieve the
 Account Number assigned by the commercial medical billing system for a given 
 patient admission/visit/encounter.  This simple function returns the Account
 Number when the PFSS Account Reference is provided as input.  
   
 Called as $$EXTNUM^IBBAPI(VAR1,VAR2) where IBBDFN=VAR1 (required) IBBARFN=VAR2
 (required) 
   
 Returns Account Number assigned by the commercial billing system; i.e., the 
 value of the EXTERNAL ACCOUNT NUMBER field (#.02) in the PFSS ACCOUNT (file
 #375) record.  0, if no record matches the IEN value in VAR2.  
VARIABLES: VAR1                         TYPE: Input
 VARIABLES DESCRIPTION:   Patient Identifier; numeric; standard VistA variable
 DFN.  
VARIABLES: VAR2                         TYPE: Input
 VARIABLES DESCRIPTION:   PFSS Account Reference; numeric; pointer to PFSS
 ACCOUNT file (#375).  
VARIABLES: $$EXTNUM                     TYPE: Output
 VARIABLES DESCRIPTION:   Account Number assigned by the commercial billing
 system; i.e., the value of the EXTERNAL ACCOUNT NUMBER field (#.02) in the
 PFSS ACCOUNT (file #375) record.  0, if no record matches the IEN value in
 VAR2.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
SUBSCRIBING PACKAGE: PROSTHETICS
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   For use by PTF module; setup of Fee Basis hospital
 admissions.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: SURGERY

NUMBER: 4665                            IA #: 4665
  DATE CREATED: MAY 23, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBBAPI
  NAME: PFSS CHARGE                     ID: IBBAPI
 GENERAL DESCRIPTION:   Two entry points are added to routine IBBAPI in order
 to accommodate Patient Financial Services System (PFSS) functionality
 requirements to provide charge data to the commercial medical billing system. 
 These entry points are called by several VistA applications involved in PFSS.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PFSS
KEYWORDS: CHARGE
COMPONENT/ENTRY POINT: $$GETCHGID
 COMPONENT DESCRIPTION:   $$GETCHGID returns to the calling application the
 value of the CURRENT CHARGE ID field (#2) of the PFSS SITE PARAMETERS file
 #372).  Those applications that are responsible for providing charge data to
 IBB use $$GETCHGID to obtain a Unique Charge ID.  The Unique Charge ID is then 
 retained in the application database in association with the charge data set.  
VARIABLES: $$GETCHGID                   TYPE: Output
 VARIABLES DESCRIPTION:   The return value is equivalent to contents of the
 CURRENT CHARGE ID field (#2) of the PFSS SITE PARAMETERS file (#372) at the
 time the call was made.  $$GETCHGID increments the value of field #2 before 
 exiting.  
  
 Upon installation of PFSS, field #2 is initialized to a value of 90000001. 
 Once this counter reaches 99999999 it will be re-initialized.  
COMPONENT/ENTRY POINT: $$CHARGE
 COMPONENT DESCRIPTION:   $$CHARGE is used by those applications responsible
 for relaying charge data to the commercial medical billing system used by
 PFSS.  
   
 Called as $$CHARGE^IBBAPI(VAR1,VAR2,VAR3,VAR4,.ARR1,.ARR2,.ARR3,.ARR4,.ARR5, 
 VAR5,.ARR6) where IBBDFN=VAR1 (required) IBBARFN=VAR2 (required) IBBCTYPE=VAR3
 (required) IBBUCID=VAR4 (required) IBBFT1=ARR1 (required) IBBPR1=ARR2
 (required, except Pharmacy) IBBDG1(n)=ARR3(n) (optional) IBBZCL(n)=ARR4(n)
 (optional) IBBRXE=ARR5 (required, Pharmacy only) IBBORIEN=VAR5 (optional) 
 IBBPROS=ARR6 (required, Prosthetics only) 
   
 All data passed in is stored in the PFSS CHARGE CACHE file (#373).  Both the
 internal entry number and #.01 of the record are set to the same value.  
VARIABLES: VAR1                         TYPE: Input
 VARIABLES DESCRIPTION:   Patient Identifier; numeric; standard VistA variable
 DFN.  
   
 VAR1 is required.  
VARIABLES: VAR2                         TYPE: Input
 VARIABLES DESCRIPTION:   PFSS Account Reference; numeric; pointer to PFSS
 ACCOUNT file (#375).  
   
 VAR2 is required.  
VARIABLES: VAR3                         TYPE: Input
 VARIABLES DESCRIPTION:   Charge Type; identifies the charge as being either a
 debit (i.e., charge) ("CG") or a credit ("CD") to the account.  
   
 VAR3 is required.  
VARIABLES: VAR4                         TYPE: Input
 VARIABLES DESCRIPTION:   The Unique Charge ID associated with the service
 event.  The IBB function $$GETCHGID^IBBAPI should be used to obtain the Unique
 Charge ID prior to the initial $$CHARGE^IBBAPI.  The Unique Charge ID is then
 stored in the application s database in association with the CPT code, HCPCS
 code, or prescription fill/refill. 
   
 VAR4 is required.  
VARIABLES: ARR1                         TYPE: Input
 VARIABLES DESCRIPTION:   Array of data elements for HL7 Segment FT1 as
 follows: ARR1(4) = Transaction Date (required) ARR1(7) = Transaction Code
 (optional) 
           Pharmacy only; required; 6-digit Service Code 
           for prescribed product.  ARR1(10) = Transaction Quantity (required) 
            Integer.  
            PCE - number of occurrences for the CPT code in ARR2(3).  
            Prosthetics - number of occurrences for the HCPCS code in 
            ARR2(3).  
            OP Pharmacy - number of dispense units prescribed.  ARR1(13) =
 Department Code (required) 
            Prosthetics - 423 
            OP Pharmacy - 160 
            PCE - as provided to PCE; otherwise, Primary Stop Code 
            associated with visit.  ARR1(16) = Assigned Patient Location
 (optional) 
            Pointer to file #44.  ARR1(18) = Patient Copay Status(optional) 
            1 - Rx Copay Exempt 
            0 - Not Exempt 
            Pharmacy only.  ARR1(20) = Performed By Code (optional) 
            Pointer to file #200.  ARR1(21) = Ordered By Code (optional) 
            Pointer to file #200.  ARR1(22) = Unit Cost (optional) 
            Pharmacy and Prosthetics only; numeric; 2 decimal digits 
            allowed.  ARR1(29) = NDC_"; _Generic Name (optional) 
            Pharmacy only; free text.  ARR1(31) = Copay Transaction Type
 (optional) 
            1 - PSO NSC RX COPAY 
            2 - PSO SC RX COPAY 
            Pharmacy only.  
   
 Array ARR1 is required, although some elements are optional.  
VARIABLES: ARR2                         TYPE: Input
 VARIABLES DESCRIPTION:   Array of data elements for HL7 Segment PR1 as
 follows: ARR2(3) = Procedure Code (required) 
           Pointer to file #81.  
           Note:  The number of times the CPT procedure was performed, 
           or the number of HCPCS items that were delivered, must be 
           specified in ARR1(10).  ARR2(4) = Procedure Description (optional) 
           Free text upto 200 characters; may be used to modify or 
           enhance the data provided in ARR2(3).  ARR2(5) = Procedure Date/Time
 (optional) 
           FileMan date/time; time optional.  ARR2(6) = Procedure Functional
 Type (optional) 
           Prosthetics - "O" (Home Oxygen), "P" (Purchasing), 
           "I" (Stock Issue).  
           Radiology - Imaging Type (file #79.2) abbreviation.  ARR2(11,1) =
 Surgeon (optional) 
              For Surgery procedures only; pointer to file #200.  ARR2(11,2) =
 Attending Surgeon (optional) 
              For Surgery procedures only; pointer to file #200.  ARR2(16) =
 Procedure Code Modifier(s) (optional) 
            Free text; one or more pointers to file #81.3 
            delimited by ";".  
   
 Array ARR2 is required from all applications except Pharmacy.  
VARIABLES: ARR3                         TYPE: Input
 VARIABLES DESCRIPTION:   Array of data elements for HL7 Segment DG1 as
 follows: ARR3(n,3) = Diagnosis Code (required) 
             Pointer to file #80.  ARR3(n,6) = Diagnosis Type (required) 
             "A" (admitting), "W" (working), "D" (discharging), 
             "F" (final).  
   
 Since there may be more than one diagnosis, ARR3 will have two subscripts. 
 The first subscript is a sequential integer that pertains to a given diagnosis 
  The second subscript refers to the corresponding Sequence number within the
 DG1 Segment.  Diagnoses must be placed in the array in priority order; i.e.,
 primary diagnosis must be first, followed in descending priority order by
 additional diagnoses (if any).  
   
 Array ARR3 is optional.  
VARIABLES: ARR4                         TYPE: Input
 VARIABLES DESCRIPTION:   Array of data elements for HL7 Segment ZCL as
 follows: ARR4(n,2) = Type (required) 
             1 - AO (Agent Orange) 
             2 - IR (Ionizing Radiation) 
             3 - SC (Service Connected) 
             4 - EC (Environmental Contaminants) 
             5 - MST (Military Sexual Trauma) 
             6 - HNC (Head and/or Neck Cancer) 
             7 - CV (Combat Veteran) ARR4(n,3) = Value (required) 
             1 - Yes 
             2 - No 
   
 Each ARR4(n) represents one of the possible SC/EI classifications.  
   
 Array ARR4 is optional.  
VARIABLES: ARR5                         TYPE: Input
 VARIABLES DESCRIPTION:   The input array is used only by Pharmacy.  Array of
 data elements for HL7 Segment RXE as follows: ARR5(1) = Quantity_";; _Days
 Supply (required) 
           Free text; numerics separated by ";;" ARR5(17) = Refills Dispensed
 (required) 
            Integer.  ARR5(18) = Date of Most Recent Fill (required) 
            FileMan date/time; date only.  ARR5(31) = DEA, Special Handling
 (required) 
            Free text; max. 5 characters.  
   
 Array ARR5 is required for Pharmacy only.  
VARIABLES: VAR5                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the ORDER file (#100) in OE/RR.  Provider
 orders entered in CPRS are maintained in file #100 and forwarded to the
 service applications such as Radiology and Laboratory.  These applications 
 retain the ORDER pointer in their files and it is passed to PCE as service
 requests are completed/resulted.  PCE will always pass the ORDER file pointer
 to IBB, if it exists.  
   
 VAR5 is optional.  
VARIABLES: ARR6                         TYPE: Input
 VARIABLES DESCRIPTION:   Array of data elements for Prosthetics only as
 follows: ARR6(1) = Vendor (required) 
           Pointer to file #440.  ARR6(2) = OBL# (required) 
           Free text; max. 30 characters.  
   
 Array ARR6 is required for Prosthetics only.  
VARIABLES: $$CHARGE                     TYPE: Output
 VARIABLES DESCRIPTION:   1, if a new record in file #373 is successfully
 created; 0, if unsucessful.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
SUBSCRIBING PACKAGE: PROSTHETICS

NUMBER: 4666                            IA #: 4666
  DATE CREATED: MAY 05, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOHLNE3
  NAME: DBIA4666                        ID: PSOHLNE3
 GENERAL DESCRIPTION:   CPRS requests permission to use the EN^PSOHLNE3 API to
 pass updated SC, EI, and ICD-9 Diagnosis information to Outpatient Pharmacy. 
 When a verbal or telephone order is place and it requires electronic
 signature, the provider may update the SC, EI's, or ICD Diagnosis information.
 This API updates this information in Prescription file (#52).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSOHLNE3
KEYWORDS: CIDC
COMPONENT/ENTRY POINT: EN(DFN,ORITEM,ORIEN,ORDX,ORSCEI)
 COMPONENT DESCRIPTION:   
    Format: 
    $$EN^PSOHLNE3(DFN,ORITEM,ORIEN,ORDX,ORSCEI) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN.  
VARIABLES: ORITEM                       TYPE: Input
 VARIABLES DESCRIPTION:   Package reference number from ORDER file (#100).  
VARIABLES: ORIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN From Order file (#100) 
VARIABLES: ORDX                         TYPE: Input
 VARIABLES DESCRIPTION:   Array of pointers to Diagnosis file (#80).  Up to 8
 pointers are accepted and the first is always the primary diagnosis.  ICD. 
 Example: ORDX(1)=80 
VARIABLES: ORSCEI                       TYPE: Input
 VARIABLES DESCRIPTION:   Contains:  AO^IR^SC^EC^MST^HNC^CV^SHAD 
VARIABLES: $$EN                         TYPE: Output
 VARIABLES DESCRIPTION:   1 = success, package information has been updated.  
 0^error message = indicates function call did not succeed.  
   Where error message can contain: 
     1 = Prescription IEN cannot be found.  
     2 = ORSCEI contains "?".  
     3 = Patient IEN is different than the entry 
         in Prescription file (#52).  
     4 = Orderable item is different than the entry 
         in Prescription file (#52).  
     5 = ORIEN does not equal PLACER ORDER # in 
         Prescription file (#52).  
     6 = Discontinued order;NO COPAY RESETS  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 19, 2019

NUMBER: 4667                            IA #: 4667
  DATE CREATED: MAY 10, 2005
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMRAUTL2
  NAME: Update to entries in file 120.8
  ID: GMRAUTL2
 GENERAL DESCRIPTION:   Automatically updates entries in the PATIENT ALLERGIES
 file (120.8) when changes to the ingredients and/or drug classes of reactants
 found in file 120.82 or in pharmacy related files are made.  Changes to 
 ingredients and/or drug classes for those reactants will then be made to
 existing entries in file 120.8 so that existing allergies have the updated
 information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: UPDATE
COMPONENT/ENTRY POINT: UPDATE(ENTRY,ING,CLASS)
 COMPONENT DESCRIPTION:   This entry point will identify reactants in the
 PATIENT ALLERGIES file (120.8) that are associated with the reactant
 identified in ENTRY.  It will then make the necessary changes to the entry in
 file 120.8 based on information passed in ING and CLASS.  
VARIABLES: ENTRY                        TYPE: Input
 VARIABLES DESCRIPTION:   Describes the reactant entry that is to be found and
 updated.  It is in the format of IEN;FILE REFERENCE^TEXT.  For example, if 
 entry number 32 in the GMR ALLERGIES file was DAVETONIN then ENTRY would be
 32;GMRD(120.8,^DAVETONIN.  
VARIABLES: ING                          TYPE: Input
 VARIABLES DESCRIPTION:   Array listing ingredients that are being changed for
 the reactant identified in the ENTRY variable.  This array will list both 
 ingredients being added and those being deleted.  The format of the ING array
 will be ING("A",IEN) where "A" indicates that the ingredient is being added. 
 The IEN will be the IEN in the DRUG INGREDIENTS file (50.416).  ING("D",IEN)
 is used to indicate ingredients that will be deleted.  
VARIABLES: CLASS                        TYPE: Input
 VARIABLES DESCRIPTION:   Array listing drug classes that are being changed for
 the reactant identified in the ENTRY variable.  This array will list both 
 classes being added and those being delted.  The format of the CLASS array
 will be CLASS("A",IEN) where "A" indicates that the class is being added.  The
 IEN will be the IEN in the drug class in the VA DRUG CLASS file (50.605). 
 CLASS("D",IEN) is used to indicate drug classes that will be deleted.  
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   ADDED 4/27/2007 
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
 SUBSCRIBING DETAILS:   ADDED 8/20/2007 

NUMBER: 4668                            IA #: 4668
  DATE CREATED: SEP 20, 2006            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDPFSS2
  NAME: PFSS ACCOUNT NUMBER REFERENCE   ID: SDPFSS2
 GENERAL DESCRIPTION:   This API will return the PFSS Account Number Reference
 stored in the Scheduling APPOINTMENT ACCOUNT NUMBER REFERENCE File (#409.55). 
 This reference number is provided by the IBB PFSS ACCOUNT API when a new 
 appointment is made. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PFSS
KEYWORDS: IBB
KEYWORDS: ANR
KEYWORDS: ACCOUNT NUMBER REFERENCE
COMPONENT/ENTRY POINT: $$GETARN(SDT,DFN,SDCL)
 COMPONENT DESCRIPTION:   Returns the PFSS Account Number Reference when
 provided the Appointment Date/Time, patient DFN, and Clinic IEN.  The account
 number reference is the IEN to the PFSS ACCOUNT File (#375) which stores the
 Account Number provided by the external Medical Billing System.  
VARIABLES: SDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Appointment Date/Time in internal FileMan format 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number to the PATIENT File (#2) 
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number for the appointment clinic in
 the HOSPITAL LOCATION File (#44) 
VARIABLES: $$GETARN                     TYPE: Output
 VARIABLES DESCRIPTION:   This will be the PFSS Account Number Reference (if
 one is found) or 0 if one is not.  If an error occurred when calling the API,
 an error will be returned in the following format: "-1^error description" 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4669                            IA #: 4669
  FILE NUMBER: 773                      GLOBAL ROOT: HLMA(
  DATE CREATED: MAY 16, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HL7 MESSAGE ID ACCESS
  ID: HLMA(
GLOBAL REFERENCE: HLMA('B',
 GLOBAL DESCRIPTION:   This is the "B" index on the HL7 MESSAGE ADMINISTRATION
 (#773) file that allows a user to lookup a record by it's corresponding entry
 in the HL7 MESSAGE TEXT (#772) file.  
GLOBAL REFERENCE: HLMA(D0,0)
FIELD NUMBER: 2                         FIELD NAME: MESSAGE ID
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA allows the subscribing package to search the
 "B" index of the HL7 MESSAGE ADMINISTRATION (#773) file and get the message ID
 of the message using VA FileMan.  
  STATUS: Active
KEYWORDS: PRF
KEYWORDS: HLMA
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4670                            IA #: 4670
  FILE NUMBER: 65                       GLOBAL ROOT: LRD(
  DATE CREATED: MAY 16, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: BLOOD BANK
  ID: LRD(
GLOBAL REFERENCE: LRD(65,D0,6)
FIELD NUMBER: 6.2                       FIELD NAME: PHYSICIAN
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Physician of patient transfused 
 GENERAL DESCRIPTION:   The DSS Extracts BLOOD BANK EXTRACT file (#727.829)
 does direct reads to the 0 node to LAB DATA file (#63). File (#63) has a
 multiple field (#1) 'UNITS SELECTED FOR XMATCH' which has field (#.01) 'UNIT
 SELECTED FOR XMATCH'. This field is a pointer to the BLOOD INVENTORY file
 (#65). DSS Extracts needs permission to execute direct global read to retrieve 
 'PHYSICIAN' field (#6.2) from BLOOD INVENTORY file (#65).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BLOOD BANK
KEYWORDS: DSS EXTRACTS
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   The DSS Extracts BLOOD BANK EXTRACT file (#727.829)
 does direct reads to the 0 node to LAB DATA file (#63). File (#63) has a
 multiple field (#1) 'UNITS SELECTED FOR XMATCH' which has field (#.01) 'UNIT
 SELECTED FOR XMATCH'. This field is a pointer to the BLOOD INVENTORY file
 (#65). DSS Extracts needs permission to execute direct global read to retrieve 
 'PHYSICIAN' field (#6.2) from BLOOD INVENTORY file (#65).  
      
         Global: ^LRD(65,D0,6)),U,2) 
    GLOBAL REFERENCE: 
      ^LRD(65,D0,6) 

NUMBER: 4671                            IA #: 4671
  FILE NUMBER: 409.1                    GLOBAL ROOT: SD(409.1,
  DATE CREATED: MAY 31, 2005            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4671
  ID: SD(409.1,
GLOBAL REFERENCE: SD(409.1,
FIELD NUMBER: 4                         FIELD NAME: SYNONYM
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   A free text field of 1 to 5 characters.  
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   For Patient Financial Services System (PFSS), the IBB
 module of INTEGRATED BILLING requires direct global read of the SYNONYM field
 (#4) in the APPOINTMENT TYPE file (#409.1).  
  STATUS: Active
KEYWORDS: PFSS
KEYWORDS: APPOINTMENT TYPE
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   In the PFSS Project, a new module has been developed
 within INTEGRATED BILLING in namespace IBB.  Its purpose is to provide a
 common interface for applications, which must send data to an external billing
 system.  All data is sent via HL7 messaging.  The routines for data extraction 
 and message assembly are located in the IBB namespace.  
   
 Certain applications (e.g., Scheduling) will provide to IBB the Appointment
 Type of a patient visit as a pointer to the APPOINTMENT TYPE file (#409.1).  
   
 The message builder code will obtain data from the SYNONYM field (#4) by
 direct global read of the zero-node; i.e., 4th piece of ^SD(409.1,D0,0).  

NUMBER: 4672                            IA #: 4672
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: MAY 31, 2005            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4672
  ID: SC(
GLOBAL REFERENCE: SC(D0,0)
FIELD NUMBER: 3.5                       FIELD NAME: DIVISION
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Pointer to the MEDICAL CENTER DIVISION file (#40.8).  
 GENERAL DESCRIPTION:   For Patient Financial Services System (PFSS), the IBB
 module of INTEGRATED BILLING requires direct global read of the DIVISION field
 (#3.5) in the HOSPITAL LOCATION file (#44).  
  STATUS: Active
KEYWORDS: PFSS
KEYWORDS: HOSPITAL LOCATION
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   In the PFSS Project, a new module has been developed
 within INTEGRATED BILLING in namespace IBB.  Its purpose is to provide a
 common interface for applications, which must send data to an external billing
 system.  All data is sent via HL7 messaging.  The routines for data extraction 
 and message assembly are located in the IBB namespace.  
   
 Certain applications (e.g., Scheduling) will provide to IBB the Location of a
 patient visit as a pointer to the HOSPITAL LOCATION file (#44).  Each message
 to the external billing system must also identify the Medical Center Division
 of the sender.  
   
 The message builder code will obtain data from the DIVISION field (#15) by
 direct global read of the zero-node; i.e., 15th piece of ^SC(D0,0).  

NUMBER: 4673                            IA #: 4673
  FILE NUMBER: 100                      GLOBAL ROOT: OR(
  DATE CREATED: AUG 09, 2005
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWPFSS
  NAME: RETURN PFSS ACCOUNT REFERENCE   ID: ORWPFSS
 GENERAL DESCRIPTION:   Via functionality and constraints subsumed within the
 PFSS project, the PFSS Account Reference Number pointer is stored for
 specified orders in the Order file (#100) as field 97. This IA covers the
 return of a previously stored PFSS Account Reference Number pointer from the
 Order file (#100).  
         
 The OE/RR API is accessed as D ORACTREF^ORWPFSS(.ORACTREF,ORIEN).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PFSS
KEYWORDS: PFSS ACCOUNT REFERENCE
KEYWORDS: ORACTREF
COMPONENT/ENTRY POINT: ORACTREF(.ORACTREF,ORIEN)
 COMPONENT DESCRIPTION:   
    The OE/RR API is accessed as D ORACTREF^ORWPFSS(.ORACTREF,ORIEN).  
     
    If a PFSS Account Reference Number exists in the Order file (#100) for 
    that Order IEN, then the pointer for same will be returned.  
     
    If a PFSS Account Reference Number does not exist in the Order file 
    (#100) for that Order IEN, then a null value is returned.  
VARIABLES: ORIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Order IEN 
VARIABLES: ORACTREF                     TYPE: Output
 VARIABLES DESCRIPTION:   PFSS Account Reference number as a pointer to file
 #375.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER

NUMBER: 4674                            IA #: 4674
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: JUN 02, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ACCESS TO AK.PROVIDER CROSS REFERENCE
  ID: VA(200
GLOBAL REFERENCE: VA(200,AK.PROVIDER
 GENERAL DESCRIPTION:   This integration agreement allows access to the
 AK.PROVIDER cross reference in the New Person file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   Person Service Lookup is referencing the AK.PROVIDER
 cross reference to obtain the beginning value for a call to LIST^DIC.  

NUMBER: 4675                            IA #: 4675
  FILE NUMBER: 75.1                     GLOBAL ROOT: RAO(75.1
  DATE CREATED: JUN 03, 2005
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4675
  ID: RAO(75.1
GLOBAL REFERENCE: RAO(75.1,D0,'H',
FIELD NUMBER: 400                       FIELD NAME: CLINICAL HISTORY FOR EXAM
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field may contain a written clinical history
 pertinent to the procedure requested, as well as instructions to the
 interpreting physician.  The entire field data is included in the outbound HL7 
 ADT message sent by PFSS to the external medical billing system for purposes
 of pre-certification of Radiologic exams.  
 GLOBAL DESCRIPTION:   This is a word-processing field that may be composed of
 many global nodes.  
 GENERAL DESCRIPTION:   A private agreement with INTEGRATED BILLING to allow
 direct global read of the CLINICAL HISTORY FOR EXAM field (#400) of the
 RAD/NUC MED ORDERS file (#75.1) in the context of the Patient Financial
 Services System (PFSS) project.  
  STATUS: Active
KEYWORDS: PFSS
KEYWORDS: CLINICAL HISTORY
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   The code for the message builders for many of the
 outbound HL7 ADT messages is located within the IBB namespace of INTEGRATED 
 BILLING.  For efficiency the message builder will access the data in field
 #400 of file #75.1 by direct global read.  The data from field #400 is sent to
 the external medical billing system as required for pre-certification of
 Radiologic exams.  

NUMBER: 4676                            IA #: 4676
  FILE NUMBER: 440                      GLOBAL ROOT: PRC(440
  DATE CREATED: JUN 08, 2005            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4676
  ID: PRC(440
GLOBAL REFERENCE: PRC(440,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The free text Vendor name; maximum 36 characters.  
 GENERAL DESCRIPTION:   Allow FileMan read of the VENDOR file (#440), NAME
 field (#.01).  
  STATUS: Active
KEYWORDS: VENDOR
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   In the Patient Financial Services System project,
 Prosthetics passes a pointer to the VENDOR file (#440) to identify the vendor
 associated with a HCPCS item.  When billing data is sent to the external
 medical billing system, the vendor must be identified by name.  
  
 The vendor name is placed in the HL7 message to the external medical billing
 system at location RQ1.4 of the DFT-P03 message.  

NUMBER: 4677                            IA #: 4677
  DATE CREATED: JUN 08, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSAP
  NAME: Application Proxy               ID: XUSAP
 GENERAL DESCRIPTION:   To support the J2EE middle tier the concept of a
 APPLICATION PROXY user was created. This is a user name that an application
 sets that has an user class of Application Proxy. It will not have Access or
 Verify codes, no Primary Menu. It will have one or more Secondary Menu items.
 The RPC's that the menu items point to must have the APP PROXY ALLOWED field
 set to Yes.  
  
 APPLICATION PROXY names used by Class I software must be approved by the DBA.  
  STATUS: Active
COMPONENT/ENTRY POINT: $$CREATE(proxyname,fmac,options)
 COMPONENT DESCRIPTION:   proxyname is the name of the Application proxy.  FMAC
 is the FM access code. (Can not be "@") option can be the name of an option
 like "XMUSER" or 
  it can be an array of options XUOPT("XMUSER")=1,XUOPT("XWB RPC TEST")=1 
  that are passed by reference.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   The Application Proxy called RADIOLOGY, OUTSIDE SERVICE
 was created to receive reports from COTS products and vendors interfacing with
 VistA's RADIOLOGY/NUCLEAR MEDICINE package.  
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   Added 10/23/2007 
  
 7/6/15-LR*5.2*458, Autoverification, will add two new application proxy users. 
 LRLAB AUTO RELEASE is used to indicate that the results in VistA Lab were
 released by an automated Lab process without human interventions.  LRLAB, AUTO
 VERIFY is used to indicate that the results were "approved" by an automated
 process using a rules based system.  
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
 SUBSCRIBING DETAILS:   NAME: CLINICAL,DEVICE PROXY SERVICE SECONDARY MENU
 OPTIONS: MD GUI MANAGER SECONDARY MENU OPTIONS: MD GUI USER Added 03/16/2009.  
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   Added 4/6/09 
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 11/13/2007 
  
 9/4/14-PCMMR will be adding a new application proxy user (SD*5.3*603): 
  
 NAME: SCMC,APPLICATION PROXY 
   DATE ENTERED: JAN 28, 2014     SECONDARY MENU OPTIONS: SCMC PCMMR APP PROXY
 MENU User Class: APPLICATION PROXY           ISPRIMARY: Yes 
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   Added 12/22/09 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Added IB 12/10/2010 Added 5/21/2021 Username
 INTERFACE,IB IIU for use effective with IB*2.0*687.  There is a background
 Integrated Billing job as part of the IIU effort that files entries into the
 INSURANCE VERIFICATION PROCESSOR (#355.33) file for user processing. This
 proxy will be recorded as the user who created the entry in file #355.33.  
  
 Added 3/10/25 to document Application Proxy historical entries created by IB: 
   AUTHORIZER,IB ACC added automatically in IB*2.0*770 
   INTERFACE,IB RFI added automatically in IB*2.0*547 
   IBTAS,APPLICATION PROXY added automatically in IB*2.0*623 
   AUTHORIZER,IB REG added automatically in IB*2.0*432 
  
   Application Proxies manually installed before ICR 4677 created: 
     TAS,CONNECTOR PROXY added with IB*2.0*623 
     AUTHORIZER,IB MRA added prior to 2007.  
  
 Added 5/20/25: 
  Effective with IB*2.0*702. Added proxy user 'ICB,IB NOINS'. This special user
 will be used to automatically process No Insurance buffer entries in ICBWeb.  
  Effective with IB*2.0*806. Added proxy user 'IB, BUFFER CLEANUP'. This 
 special user will be used to do simple routine work in the buffer file so that
 the IB Verifier can focus on more complex entries that require editing and
 need manual review.  
  
 Added 8/26/25: Effective with IB*2.0*822. Added proxy user 'IB,AUTOINS 
 FILEUPDATE'. This proxy is for an application.  It does not have any menus or
 keys assigned to it. In the background on a nightly basis, this special user
 will be used to automatically re-verify existing active policies for patients
 associated with specific insurances.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   eHMP has been added as a subscriber to ICR #4677 for
 HMP v.2.0. HMP will be creating a single proxy user called HMP,APPLICATION
 PROXY.  This user is assigned two Broker (Client/Server) type options, HMP UI
 CONTEXT and HMP SYNCHRONIZATION CONTEXT, as secondary menu options. 
  
 HMP SYNCHRONIZATION CONTEXT option manages access to RPCs responsible for 
 synchronization of eHMP data with VistA.  HMP UI CONTEXT option allows the HMP
 UI access to the VistA system.  
  
 **************************************************** 
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                   
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
 ****************************************************
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM
 SUBSCRIBING DETAILS:   RTLS will be creating VIAASERVICE,RTLS APPLICATION
 PROXY and VIAASERVICE,RTLS CONNECTOR PROXY in VIAA*1.0*1.  
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   Effective with DG*5.3*951.  
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 6/3/19. Effective with YS*5.01*130.  
SUBSCRIBING PACKAGE: LIGHTHOUSE
 SUBSCRIBING DETAILS:   Added 5/21/21 for the purpose of creating a new
 Application Proxy named [LHS,APPLICATION PROXY] to be installed through the
 new LHS Package Release patch (LHS*1.0*0). This patch is being released in
 support of the COVID Patient Manager (CPM) SMART ON FHIR application. This
 Application Proxy user is assigned one Broker (Client\Server) Type option [LHS
 RPC CONTEXT] that includes approved RPCs through ICRs #4746 and #6022.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 12/12/22, effective with PSO*7*642 and PSO*7*675
 released 3/23/22.  Outpatient Pharmacy needs the PSO,VCC CONNECTOR PROXY for
 the VA Health Connect (VAHC) Customer Relationship Management (CRM)
 application. This application needs the ability to refill prescriptions when a
 patient calls into the contact center. 
  
 Added 5/28/24, to reflect historical update for PSO*7*707 to add a new 
 SECONDARY MENU OPTION called PSO WEB CHART to the PSOVCC,APPLICATION PROXY 
  
 Added 11/25/24, effective with patch effective with PSO*7*774, Outpatient
 Pharmacy needs the PSOAUTORELEASE, PROXY USER for OneVA Pharmacy functionality
 to automatically release a prescription at the host site when a request for
 fill, refill or partial fill is made at a dispensing site.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   Added 2/18/26, effective with patch PRCA*4.5*455
 Request new application proxy user "RCDPETAS,APPLICATION PROXY" This proxy
 user is called by ePayments for processing of external interfaces via VistA
 Link.  
  DATE ACTIVATED: MAR 16, 2009

NUMBER: 4678                            IA #: 4678
  DATE CREATED: JUN 08, 2005            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VAFCTFU GET TREATING LIST
  REMOTE PROCEDURE: VAFCTFU GET TREATING LIST
  STATUS: Active

NUMBER: 4679                            IA #: 4679
  DATE CREATED: DEC 20, 2005            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VAFCTFU CONVERT ICN TO DFN
  REMOTE PROCEDURE: VAFCTFU CONVERT ICN TO DFN
  STATUS: Active

NUMBER: 4680                            IA #: 4680
  DATE CREATED: DEC 20, 2005            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VAFCTFU CONVERT DFN TO ICN
  REMOTE PROCEDURE: VAFCTFU CONVERT DFN TO ICN
  STATUS: Active

NUMBER: 4681                            IA #: 4681
  FILE NUMBER: 100                      GLOBAL ROOT: OR(
  DATE CREATED: JUN 09, 2005
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Direct read of order check multiple
  ID: OR(
GLOBAL REFERENCE: OR(100,D0,9
FIELD NUMBER: .9                        FIELD NAME: ORDER CHECKS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Stores existing order checks for the given order.  Th
 "B" cross-reference allows quick access to specific types of order checks.  
 GENERAL DESCRIPTION:   Package may directly access the ^OR(100,DA,9 node to
 determine what, if any, order checks currently exist for an order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORDER CHECK
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
 SUBSCRIBING DETAILS:   The allergy package would like to check existing order
 checks to determine whether or not an order check exists for an order when 
 existing allergy data is modified.  The new allergy data is compared against
 existing orders to determine if an order check should be given.  The ability
 to view the ORDER CHECK multiple in the ORDER file will reduce false positive
 checks.  

NUMBER: 4682                            IA #: 4682
  DATE CREATED: JUN 13, 2005
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMRAGUI1
  NAME: Allergy CPRS GUI interaction    ID: GMRAGUI1
 GENERAL DESCRIPTION:   A change was made so that allergies were no longer
 handled as orders.  As a result, direct interaction between CPRS GUI and the
 Allergy package is required in order to save allergy information entered from
 within CPRS GUI.  This agreement gives access to existing APIs within the
 allergy package so that CPRS GUI can send allergy data directly to the allergy 
 system.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: allergy
COMPONENT/ENTRY POINT: EIE
 COMPONENT DESCRIPTION:   This API is called when an allergy has been marked
 'entered in error' 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the entry to be marked as
 entered in error from file 120.8.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient identifier.  
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   Array that contains specific data related to the
 action of marking the allergy as entered in error.  Includes date/time of
 action, who invoked the action and any comments related to the action.  
COMPONENT/ENTRY POINT: NKA
 COMPONENT DESCRIPTION:   API that changes the patient's assessment to 'no
 known allergies' from an un-assessed state.  
COMPONENT/ENTRY POINT: UPDATE
 COMPONENT DESCRIPTION:   This API is called when there is updated (typically
 new) allergy information to be stored.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This variable may be left blank if the allergy is a
 new allergy.  If the update call is for an existing allergy (being edited)
 then this will be the internal entry number from file 120.8.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient identifier.  
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   This array holds all of the allergy data to be stored
 for the patient.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   CPRS is allowed to make direct calls to allergy package
 APIs in order to interact directly with the allergy package for adding and
 editing allergy information.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************** 
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                   
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
 ****************************************************
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 7/8/25 effective with Class HS.Local.VA 
 .HC.ServiceBroker.VistA.AdverseReactionTracking for access to line tag NKA.  

NUMBER: 4683                            IA #: 4683
  DATE CREATED: JUN 13, 2005
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMRAGUI
  NAME: Retrieve allergy data           ID: GMRAGUI
 GENERAL DESCRIPTION:   Now that allergies are no longer orders CPRS GUI needs
 to have direct access to the allergy package in order to display and save the
 allergy data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: allergy
COMPONENT/ENTRY POINT: GETREC
 COMPONENT DESCRIPTION:   This API will return detailed information about an
 existing allergy.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number from file 120.8.  
VARIABLES: ARRAY                        TYPE: Output
 VARIABLES DESCRIPTION:   The allergy data will be returned in this array.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   This agreement allows CPRS to directly access the
 allergy package to exchange allergy based data.  

NUMBER: 4684                            IA #: 4684
  DATE CREATED: JUN 13, 2005
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMRAUTL
  NAME: Obtain site parameter entry     ID: GMRAUTL
 GENERAL DESCRIPTION:   This call will determine which allergy parameter entry
 is the correct one for the user.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: allergy
COMPONENT/ENTRY POINT: SITE
 COMPONENT DESCRIPTION:   When called, this API will determine which site
 parameter should be used for the specific user.  
VARIABLES: GMRASITE                     TYPE: Output
 VARIABLES DESCRIPTION:   After the call is made to SITE, the package variable
 GMRASITE will be defined as the IEN of the parameter settings appropriate for 
 the user.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   CPRS displays the "top ten" signs/symptoms during
 allergy entry.  There may be multiple site parameters defined at any given
 site for the allergies package and this call will allow CPRS to display the
 correct list based on the user's division, etc.  

NUMBER: 4685                            IA #: 4685
  FILE NUMBER: 101                      GLOBAL ROOT: ORD(
  DATE CREATED: JUN 20, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROTOCOL
  ID: ORD(
GLOBAL REFERENCE: DISABLE  0;3
FIELD NUMBER: 2                         FIELD NAME: DISABLE
  LOCATION: 0;3                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field disables use of the protocol when there is
 text in it.  The text will be a short message explaining why the protocol is
 disabled.  
 GENERAL DESCRIPTION:   Direct access to the Protocol file (#101) to mark
 protocols out of order and remove the out of order message.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORD
KEYWORDS: OUT OF ORDER

NUMBER: 4686                            IA #: 4686
  DATE CREATED: SEP 09, 2005            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PATIENT SERVICE B-TYPE OPTIONS
 GENERAL DESCRIPTION:   Person Services owns Broker Type Options in the DGRR
 namespace. In order to make use of the services such as Patient Service Lookup
 (PSL) and Patient Service Construct (PSC), the Broker Type Options must be
 assigned to users of any application that uses the Person Services.  
  
 In order to make things easier for the sites, Person Service developers have
 suggested that their DGRR broker type options be attached as items in the MENU
 multiple of the broker type options belonging to the application that will use
 the service. This will make the Person Service RPCs available to the
 application, and will reduce work for IRM because they will not have to assign
 the DGRR options to each user of the application, in addition to the
 application's own options.  
  
 The Interation Agreement allows an application to attach the Person Service
 Broker Type options as MENU items in the applications own Broker type option.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSC
KEYWORDS: Patient Services
KEYWORDS: Person Services
KEYWORDS: Demographics
KEYWORDS: Person Services Demographics
KEYWORDS: Person Service Construct
SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM

NUMBER: 4687                            IA #: 4687
  DATE CREATED: JUN 22, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOMHV1
  NAME: DBIA4687                        ID: PSOMHV1
 GENERAL DESCRIPTION:   This agreement provides the calling program, details of
 all (active, verified, on hold, suspended, discontinued, pending and expired), 
 prescriptions within a given date for a patient.  
  
 It provides complete details of Rx(s) in a sorted order in a TMP global 
 depending on the entry point being called EN, EN2 or EN3.  
  
  The EN call sorts data by the Rx Status (TR) and the dispensed drug (TD).  
  The EN2 call returns data for a specified Rx or list of Rxs sorted by the 
      Rx Status (TR) and the dispensed drug (TD).  
  The EN3 call sorts data by the Rx Status (TR) and the Rx IEN# (TD).  
  
  Please see at the component level for more details.  
  
  For all Rx except PENDING orders, the following details are included in 
  the TMP global: 
  
  ^TMP("PSO",$J,TR,TD,0)=DISPENSED DRUG^^RX EXPIRATION DATE^REFILLS 
  REMAINING^ISSUE DATE^RX STATUS^DAYS SUPPLY^QUANTITY^^^PLACER ORDER #^LAST 
  FILLED DATE^^ 
   
  ^TMP("PSO",$J,TR,TD,"RXN",0)=EXTERNAL Rx NUMBER^LAST RELEASE 
  DATE^ORIGINAL FILL ROUTING (W or M)^Remarks^FINISHED BY^ORIGINAL FILL 
  DATE^ORIGINAL RELEASE DATE^^RX IEN# 
  ^TMP("PSO",$J,TR,TD,"DIV",0)=DIVISION^OP DIVISION DETAILS 
  ^TMP("PSO",$J,TR,TD,"P",0)=PROVIDER IEN^PROVIDER NAME 
  ^TMP("PSO",$J,TR,TD,"REF",0)=# of refill dispensed 
  ^TMP("PSO",$J,TR,TD,"REF",REF IEN#,0)=REFILL DATE^DAYS 
   SUPPLY^QUANTITY^RELEASED DATE^ROUTING (M/W)^REMARKS 
  ^TMP("PSO",$J,TR,TD,"PAR",0)=# of partials dispensed 
  ^TMP("PSO",$J,TR,TD,"PAR",PAR IEN#,0)=PARTIAL DATE^DAYS 
   SUPPLY^QUANTITY^RELEASED DATE^ROUTING (M/W)^REMARKS 
  ^TMP("PSO",$J,TR,TD,"MDR",0)=# of MEDICATION ROUTES 
  ^TMP("PSO",$J,TR,TD,"MDR",D1,0)=MEDICATION ROUTES ABBR.  
  ^TMP("PSO",$J,TR,TD,"SCH",0)=# of schedule entries 
  ^TMP("PSO",$J,TR,TD,"SCH",D1,0)=SCHEDULES 
  ^TMP("PSO",$J,TR,TD,"SIG",0)=# of Sig entries 
  ^TMP("PSO",$J,TR,TD,"SIG",D1,0)=SIG 
  ^TMP("PSO",$J,TR,TD,"PC",0)=# of provider comment entries 
  ^TMP("PSO",$J,TR,TD,"PC",D1,0)=PROVIDER COMMENTS 
  ^TMP("PSO",$J,TR,TD,"DD",0)=1 
  ^TMP("PSO",$J,TR,TD,"DD",1,0)=DISPENSED DRUG IEN#^^ 
  
 For Pending orders, the data is sorted by the DISPENSED DRUG (name)/PHARMACY
 ORDERABLE ITEM (name) (TD) and returns the following: 
  
  ^TMP("PSO",$J,"PND",TD,0)=DISPENSED DRUG (if entered in CPRS)/NAME of 
  the PHARMACY ORDERABLE ITEM concatenated with the NAME OF THE DOSAGE 
  FORM^^MEDICATION ROUTE ABBR.^^# OF REFILLS^EFFECTIVE DATE^ORDER TYPE 
  (PENDING/ONHOLD)^^QUANTITY^^PLACER NUMBER 
  
  
  ^TMP("PSO",$J,"PND",TD,"SCH",0)= # of SCHEDULE 
  ^TMP("PSO",$J,"PND",TD,"SCH",D1,0)=SCHEDULE 
  ^TMP("PSO",$J,"PND",TD,"SIG",0)= # of SIG 
  ^TMP("PSO",$J,"PND",TD,"SIG",D1,0)=SIG 
  ^TMP("PSO",$J,"PND",TD,"SIO",0)= # of Lines 
  ^TMP("PSO",$J,"PND",TD,"SIO",D1,0)=PROVIDER COMMENTS (packed to 80 
   characaters) 
  ^TMP("PSO",$J,"PND",TD,"DD",0)   = 1 
  ^TMP("PSO",$J,"PND",TD,"DD",1,0)=DISPENSED DRUG IEN# (if entered in 
   CPRS)^^ 
  STATUS: Active
KEYWORDS: MHV
KEYWORDS: INTERNET
KEYWORDS: PRESCRIPTION
COMPONENT/ENTRY POINT: EN(DFN,BDT,EDT)
 COMPONENT DESCRIPTION:   This entry point returns prescription information of
 the most recent occurrence of drug(s) that was dispensed for a given date
 range in a TMP global. The data is sorted by the Rx Status (TR) and the
 dispensed drug (TD).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN Number (Required).  
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the start date to search (default is DT-120,
 prescriptions expired in the last 120 days).  
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the end date (default is null, prescriptions
 expiring in the future).  
VARIABLES: TMP('PSO',$J                 TYPE: Output
 VARIABLES DESCRIPTION:   Global location of returned list of Rxs. Please see
 the IA description section for the TMP global layout.  
COMPONENT/ENTRY POINT: EN2(DFN,RXLIST)
 COMPONENT DESCRIPTION:   This entry point returns prescription information for
 a given Rx/list of Rxs.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN Number (Required).  
VARIABLES: RXLIST                       TYPE: Input
 VARIABLES DESCRIPTION:   List of prescription IEN's delimited with "^".  
VARIABLES: TMP('PSO',$J                 TYPE: Output
 VARIABLES DESCRIPTION:   Global location of returned list of Rx(s). Please see
 the IA description section for the TMP global layout.  
COMPONENT/ENTRY POINT: EN3(DFN,BDT,EDT)
 COMPONENT DESCRIPTION:   This entry point returns every prescription
 information (Rx history) that was dispensed for a given date range in a TMP
 global. The data is sorted by the Rx Status (TR) and the Rx IEN# (TD).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN Number (Required).  
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the start date to search (default is DT-120,
 prescriptions expired in the last 120 days).  
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the end date (default is null, prescriptions
 expiring in the future).  
VARIABLES: TMP('PSO',$J                 TYPE: Output
 VARIABLES DESCRIPTION:   Global location of returned list of Rxs. Please see
 the IA description section for the TMP global layout.  
SUBSCRIBING PACKAGE: MYHEALTHEVET

NUMBER: 4688                            IA #: 4688
  DATE CREATED: JUN 28, 2005            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGMTR
  NAME: STANDARD RULES FOR REQUIRING A MEANS TEST
  ID: DGMTR
 GENERAL DESCRIPTION:   The Means Test Expiration by Appointment Date report
 (EASMTRP3) currently lists some patients who do not require a means test. 
 This is because the rules for determining if a patient requires a means test
 are periodically updated.  In order to correct the situation without having to
 recode the report every time the rules change, the report now calls a central 
 routine to determine if a means test is required.  The central routine (DGMTR)
 is the definitive routine that standardizes and compartmentalizes the rules
 for requiring a means test with entry point (EN).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MEANS TEST
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   The entry point EN is the entry point that determines
 whether a means test is required.  It accepts the input variables DFN, DGADDF,
 DGMSGF, and returns the output variable DGREQF as described below.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The DFN is the internal entry number to the Patient
 File (#2).  
VARIABLES: DGADDF                       TYPE: Input
 VARIABLES DESCRIPTION:   The "add flag" (DGADDF) is set to "1".  This is
 counterintuitive.  The value of "1" instructs the routine to NOT add a means
 test.  
VARIABLES: DGMSGF                       TYPE: Input
 VARIABLES DESCRIPTION:   The "message flag" (DGMSGF) is set to "1".  This is
 counterintuitive.  The value of "1" instructs the routine to NOT list
 messages.  
VARIABLES: DGREQF                       TYPE: Output
 VARIABLES DESCRIPTION:   The variable DGREQF is returned as a zero "0" if a
 means test is not required, and as a one "1" if a means test is required.  
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM

NUMBER: 4689                            IA #: 4689
  FILE NUMBER: 59                       GLOBAL ROOT: DIC(59
  DATE CREATED: APR 20, 2007            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DIC(59
  ID: DIC(59
GLOBAL REFERENCE: DIC(59,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the name of the site.  
 GENERAL DESCRIPTION:   This DBIA allows the DSS EXTRACTS PACKAGE to do a
 direct read to a old global location to retrieve Outpatient Sites. This read
 is exempt from the Pharmacy encapsulation effort, since the current global
 location is different, and we are not encapsulating pre-V7.0 Outpatient
 Pharmacy direct reads.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   The DSS EXTRACTS package can do a direct read to
 DIC(59, to retrieve Outpatient Sites. Data has since been moved to the PS(59
 location, but since some non-VA sites still may use old versions of Outpatient 
 Pharmacy, for that reason we will continue to allow this direct read.  
  DATE ACTIVATED: APR 22, 2007

NUMBER: 4690                            IA #: 4690
  DATE CREATED: JUN 21, 2005            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: XDRDVALF variable
 GENERAL DESCRIPTION:   The XDRDVALF variable is defined during the MERGE
 process, and can be used to determine whether changes which are being seen are
 the result of a merge process.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MERGE

NUMBER: 4691                            IA #: 4691
  FILE NUMBER: 9.4                      GLOBAL ROOT: DIC(9.4,
  DATE CREATED: JUN 17, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DELETE AFFECTS RECORD MERGE
  ID: DIC(9.4,
GLOBAL REFERENCE: DIC(9.4,D0,20,
FIELD NUMBER: .01                       FIELD NAME: FILE AFFECTED
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Remove all entries in the AFFECTS RECORD MERGE field in
 the Package file for Prosthetics.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS

NUMBER: 4692                            IA #: 4692
  DATE CREATED: JUN 22, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPDPI
  NAME: DBIA4692                        ID: IBNCPDPI
 GENERAL DESCRIPTION:   This call is needed to allow ECME 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
KEYWORDS: ECME
KEYWORDS: BPS
COMPONENT/ENTRY POINT: TPJI
 COMPONENT DESCRIPTION:   This call is the main entry for ECME point into the
 Third Party Joint Inquiry List Template option.  
  
 The API will check if the PFSS system is active. If so then the functionality
 provided by this API will not be available and the user will be notified by
 the message "This functionality is not supported on PFSS sites." 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) parameter to run the TPJI for pre-selected
 patient. If DFN is defined then the TPJI will use the patient with specified
 DFN.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 4693                            IA #: 4693
  DATE CREATED: JUN 22, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPDPC
  NAME: DBIA4693                        ID: IBNCPDPC
 GENERAL DESCRIPTION:   This call is needed to allow ECME to call the IB CLAIM
 TRACKING / VIEW /EDIT EPISODE functionality. This is needed to prevent users
 from having to exit one menu option and access another option.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
COMPONENT/ENTRY POINT: CT
 COMPONENT DESCRIPTION:   This call is the main entry point into the IBNCPDP
 LSTMN CT List Template option.  
VARIABLES: IBRXIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   Internal Prescription IEN - Pointer to file# 52 
VARIABLES: IBRXFIL                      TYPE: Input
 VARIABLES DESCRIPTION:   Fill# 
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: DEC 10, 2010

NUMBER: 4694                            IA #: 4694
  DATE CREATED: JUN 22, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPDPI
  NAME: DBIA4694                        ID: IBNCPDPI
 GENERAL DESCRIPTION:   This call is needed to allow ECME to call the IB
 Patient Insurance Info View/Edit functionality. This is needed to prevent
 users from having to exit one menu option and access another option.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   This call is the main entry point into the [IBNCPDP
 INSURANCE MANAGEMENT] List Template option.  
  
 The API will check if the PFSS system is active. If so then the functionality
 provided by this API will not be available and the user will be notified by
 the message "This functionality is not supported on PFSS sites." 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's IEN (file #2) 
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 4695                            IA #: 4695
  DATE CREATED: JUN 22, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPDPL
  NAME: DBIA4695                        ID: IBNCPDPL
 GENERAL DESCRIPTION:   This call is needed to allow ECME to call the IB
 Patient Eligibility functionality. This is needed to prevent users from having
 to exit one menu option and access another option.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   Patient's IEN (file #2) 
  
 The API will check if the PFSS system is active. If so then the functionality
 provided by this API will not be available and the user will be notified by
 the message "This functionality is not supported on PFSS sites." 
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 4696                            IA #: 4696
  DATE CREATED: JUN 22, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPDPH
  NAME: DBIA4696                        ID: IBNCPDPH
 GENERAL DESCRIPTION:   This call is needed to allow ECME to call the IB List
 Current/Past Held Charges by Pt functionality. This is needed to prevent users
 from having to exit one menu option and access another option.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
COMPONENT/ENTRY POINT: ONHOLD
 COMPONENT DESCRIPTION:   List Current/Past Held Charges by Patient 
  
 The API will check if the PFSS system is active. If so then the functionality
 provided by this API will not be available and the user will be notified by
 the message "This functionality is not supported on PFSS sites." 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's IEN (file #2) 
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 4697                            IA #: 4697
  DATE CREATED: JUN 22, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPDPR
  NAME: DBIA4697                        ID: IBNCPDPR
 GENERAL DESCRIPTION:   This call is needed to allow ECME to release Held
 Charges. This is needed to prevent users from having to exit one menu option
 and access another option.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
COMPONENT/ENTRY POINT: RELH
 COMPONENT DESCRIPTION:   The API will check if the PFSS system is active. If
 so then the functionality provided by this API will not be available and the
 user will be notified by the message "This functionality is not supported on
 PFSS sites." 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's IEN (file #2) 
VARIABLES: IBRXIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Pharmacy file #52 
VARIABLES: IBREFL                       TYPE: Input
 VARIABLES DESCRIPTION:   Refill # (0 - for the original RX) 
VARIABLES: IBMODE                       TYPE: Input
 VARIABLES DESCRIPTION:   Mode: C - for separate claim - defaults the specific
 RX/refill combination P - for the patient 
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 4698                            IA #: 4698
  DATE CREATED: JUN 22, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPDPE
  NAME: DBIA4698                        ID: IBNCPDPE
 GENERAL DESCRIPTION:   This call is needed to allow ECME to invoke ECME
 Billing Events Report.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
COMPONENT/ENTRY POINT: USRSCREN
 COMPONENT DESCRIPTION:   User Screen Entry point (to call from ECME User
 Screen) 
  
 The API will check if the PFSS system is active. If so then the functionality
 provided by this API will not be available and the user will be notified by
 the message "This functionality is not supported on PFSS sites." 
VARIABLES: IBMODE                       TYPE: Input
 VARIABLES DESCRIPTION:   Mode: 
  P-patient 
  R-Rx 
VARIABLES: IBVAL                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient's DFN (mode "P") or RX ien #52 (mode "R").  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 4699                            IA #: 4699
  FILE NUMBER: 363.21                   GLOBAL ROOT: IBA(363.21,
  DATE CREATED: JUL 14, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: DBIA4699                        ID: IBA(363.21,
GLOBAL REFERENCE: IBA(363.21,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   ECME is storing the pointer to #363.21 BILLING ITEMS
 file in its #9002313.57 BPS LOG OF TRANSACTIONS file.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 4700                            IA #: 4700
  FILE NUMBER: 363.2                    GLOBAL ROOT: IBA(363.2,
  DATE CREATED: JUL 14, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: DBIA4700                        ID: IBA(363.2,
GLOBAL REFERENCE: IBA(363.2,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   ECME is storing the pointer to #363.2 -- CHARGE ITEM
 FILE in its #9002313.51 -- BPS DATA INPUT FILE, field (#1.08) CPTIEN
 [8P:363.2] 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 4701                            IA #: 4701
  DATE CREATED: JUN 27, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOBPSUT
  NAME: PSOBPSUT                        ID: PSOBPSUT
 GENERAL DESCRIPTION:   This routine contains apis used mainly by ePharmacy
 (Electronic Third Party Billing).  
  STATUS: Active
KEYWORDS: ECME
KEYWORDS: BPS
KEYWORDS: PSOBPSUT
KEYWORDS: EPHARMACY
KEYWORDS: RXFLDT
KEYWORDS: RXRLDT
KEYWORDS: STATUS
KEYWORDS: SUBMIT
KEYWORDS: RXSITE
KEYWORDS: MANREL
KEYWORDS: AUTOREL
COMPONENT/ENTRY POINT: $$STATUS(RX,RFL)
 COMPONENT DESCRIPTION:   Returns the Rx's ECME Status (calls STATUS^BPSOSRX).
 Examples: E PAYABLE, E REJECTED, etc.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTION file (#52).  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the REFILL multiple (#52.1) in the
 PRESCRIPTION file (#52).  
VARIABLES: $$STATUS                     TYPE: Output
 VARIABLES DESCRIPTION:   Prescription claim status in the following format: E
 PAYABLE, E REJECTED, E STRANDED, etc.  
COMPONENT/ENTRY POINT: $$RXSITE(RX,RFL)
 COMPONENT DESCRIPTION:   Returns the DIVISION (Pointer to the OUTPATIENT SITE
 file (#59)) for the prescription/fill.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTION file (#52).  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the REFILL multiple (#52.1) in the
 PRESCRIPTION file (#52).  
VARIABLES: $$RXSITE                     TYPE: Output
 VARIABLES DESCRIPTION:   Prescription/fill DIVISION.  
COMPONENT/ENTRY POINT: $$RXFLDT(RX,RFL)
 COMPONENT DESCRIPTION:   Returns the FILL DATE for the prescription/fill.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTION file (#52).  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the REFILL multiple (#52.1) in the
 PRESCRIPTION file (#52).  
VARIABLES: $$RXFLDT                     TYPE: Output
 VARIABLES DESCRIPTION:   Prescription/fill FILL DATE.  
COMPONENT/ENTRY POINT: AUTOREL(RX,RFL,RLDT,NDC,SRC,STS,HNG)
 COMPONENT DESCRIPTION:   This procedure performs the ePharmacy checks and
 subsequent submission of ePharmacy prescription that are automatically
 released (e.g., CMOP prescriptions).  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTION file (#52).  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the REFILL multiple (#52.1) in the
 PRESCRIPTION file (#52).  
VARIABLES: RLDT                         TYPE: Input
 VARIABLES DESCRIPTION:   Prescription/fill RELEASE DATE.  
VARIABLES: NDC                          TYPE: Input
 VARIABLES DESCRIPTION:   Prescription/fill NDC (National Drug Code).  
VARIABLES: SRC                          TYPE: Input
 VARIABLES DESCRIPTION:   Source of Call. There are currently two possible
 sources: 
  
   C - CMOP 
   A - AUTOMATED DISPENSING MACHINE 
  
VARIABLES: STS                          TYPE: Input
 VARIABLES DESCRIPTION:   Release status: "S" - Successful or "U" -
 Unsuccessful 
VARIABLES: HNG                          TYPE: Input
 VARIABLES DESCRIPTION:   Hang time. This time is used in case the NDC passed
 in is different than the NDC currently on file for the prescription/fill.
 After re-submitting the prescription/fill to the third party payer, the
 process will wait this hang time. If the prescr 
  iption returned from the payer as PAYABLE, the NDC is then saved on the DRUG
 file (#50) as the LAST USED NDC for the Division who entered the
 prescription/fill.  
COMPONENT/ENTRY POINT: $$RETRX(RX,FL)
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTON file 52.  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the REFILL multiple (52.1) in the
 PRESCRIPTION file 52.  
  (Default: most recent fill) 
VARIABLES: $$RETRX                      TYPE: Output
 VARIABLES DESCRIPTION:   
  in the next CMOP transmission or Print Local From Suspense run 
  
  0 - Prescription should NOT be re-transmitted to ECME 
  1 - Prescription should be re-transmitted to ECME 
COMPONENT/ENTRY POINT: $$RXRLDT(RX,RFL)
VARIABLES: $$RXRLDT                     TYPE: Output
 VARIABLES DESCRIPTION:   RELEASE DATE for the prescription/fill.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRITION file 52.  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the REFILL multiple (52.1) in the
 PRESCRIPTION file 52.  To indicate the Original fill, pass in 0 (zero).  
SUBSCRIBING PACKAGE: CMOP
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   06-11-14 DT: Added Accounts Receivable as subscriber,
 effectively with ePayments patch PRCA*4.5*298.  

NUMBER: 4702                            IA #: 4702
  DATE CREATED: JUN 27, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOBPSU1
  NAME: PSOBPSU1                        ID: PSOBPSU1
 GENERAL DESCRIPTION:   This routine contains apis used mainly by ePharmacy
 (Electronic Third Party Billing).  
  STATUS: Active
KEYWORDS: ECME
KEYWORDS: EPHARMACY
KEYWORDS: PSOBPSU1
KEYWORDS: BPS
KEYWORDS: ECMESND
KEYWORDS: REVERSE
COMPONENT/ENTRY POINT: ECMESND(RX,RFL,DATE,FROM,NDC,CMOP,RVTX,OVRC)
 COMPONENT DESCRIPTION:   This procedure is used to submit a specific
 prescription/fill to third party payer through ECME (Electronic Claim
 Management Engine).  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTION file (#52).  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the REFILL multiple (#52.1) in the
 PRESCRIPTION file (#52).  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   Date of service. Ideally, this should be the RELEASE
 DATE, but in most cases the FILL DATE is passed in. In case of a future date
 is passed, the api replaces it with today's date.  
VARIABLES: FROM                         TYPE: Input
 VARIABLES DESCRIPTION:   This parameter is mostly used by EMCE to indicate the
 function that triggered the claim submission. Here is the current list of
 possible values: 
  
 PP   - From choosing PP from Patient Prescription Processing 
        option.  PL   - Pull local from suspense PE   - Pull early from
 suspense PC   - Pull CMOPs RN   - Renew OF   - Original Fill BB   - Back
 Billing RF   - Refill RL   - Release Rx NDC check - Rebill if billed NDC
 doesnt match 
        release NDC.  CRLB - CMOP Release & Rebill CRLR - CMOP Release &
 Reverse (successful release) ERES - Resubmit from ECME user screen CRLX - CMOP
 unsuccessful release & reverse RRL  - Original claim rejected, submit another
 claim, no reversal DE   - Delete ED   - Edit DDED - Delete in edit DC   -
 Discontinue - only reverse un-released PAYABLE DC's, release 
        date check should be in calling routine.  RS   - Return-to-Stock 
VARIABLES: NDC                          TYPE: Input
 VARIABLES DESCRIPTION:   Prescription/fill NDC.  
VARIABLES: CMOP                         TYPE: Input
 VARIABLES DESCRIPTION:   Flag indicating if the prescription/fill is being
 transmitted to CMOP (=1) or not (=0).  
VARIABLES: RVTX                         TYPE: Input
 VARIABLES DESCRIPTION:   Reverse text. This parameter is used by ECME for
 submissions that also require a claim to be reversed before it can be
 re-submitted (e.g.,"RX RELEASE - NDC CHANGED").  
VARIABLES: OVRC                         TYPE: Input
 VARIABLES DESCRIPTION:   Set of 3 NCPDP override codes used to override DUR
 rejects. They should be separted by "^" (up-arrow), being COD1^COD2^COD3,
 where: 
  
    COD1 - PROFESSIONAL SERVICE CODE 
    COD2 - REASON FOR SERVICE CODE 
    COD3 - RESULT OF SERVICE CODE 
  
COMPONENT/ENTRY POINT: $$LSTRFL(RX)
 COMPONENT DESCRIPTION:   Returns the latest fill for a specific prescription.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTION file (#52).  
VARIABLES: $$LSTRFL                     TYPE: Output
 VARIABLES DESCRIPTION:   
  Returns 0 (zero) for the ORIGINAL FILL, 
  1 for REFILL 1, 2 for REFILL 2, ... 
COMPONENT/ENTRY POINT: ECMEACT(RX,RFL,COMM,USR)
 COMPONENT DESCRIPTION:   Allows other applications to log ECME activities to
 the ACTIVITY LOG (#52.3) sub-file in the PRESCRIPTION file (#52).  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTION file (#52).  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the REFILL multiple (#52.1) in the
 PRESCRIPTION file (#52). (Default: latest refill) 
VARIABLES: COMM                         TYPE: Input
 VARIABLES DESCRIPTION:   Comments to be logged as an activity for the 
 prescription ECME Activity Log. Up to 75 characters.  
VARIABLES: USR                          TYPE: Input
 VARIABLES DESCRIPTION:   User responsible for setting the activity. Pointer to
 NEW PERSON file (#200). (Default: DUZ) 
SUBSCRIBING PACKAGE: CMOP
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4703                            IA #: 4703
  FILE NUMBER: 52.5                     GLOBAL ROOT: PS(52.5,
  DATE CREATED: DEC 02, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  NAME: DBIA4703                        ID: PS(52.5,
GLOBAL REFERENCE: PS(52.5,
FIELD NUMBER: 3                         FIELD NAME: CMOP INDICATOR
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This value is used in order to determine CMOP status of
 the RX.  
GLOBAL REFERENCE: PS(52.5,'B',
 GLOBAL DESCRIPTION:   This cross reference is used by the ECME package to
 lookup prescription entries in the Rx Suspense file #52.5.  
 GENERAL DESCRIPTION:   The ECME routines are accessing "B" x-ref and reading
 (#3) CMOP INDICATOR field to determine the Window/Mail/CMOP status of the RX.  
  
 This agreement will be retired on 12/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 PSO*7*213. 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 EMAIL GROUP 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
 December 1, 2006.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 01, 2006
KEYWORDS: ECME
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 4704                            IA #: 4704
  FILE NUMBER: 442.6                    GLOBAL ROOT: PRC(442.6,
  DATE CREATED: JUN 27, 2005            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4704
  ID: PRC(442.6,
GLOBAL REFERENCE: PRC(442.6,
FIELD NUMBER: .01                       FIELD NAME: COMMON NUMBERING SERIES
  LOCATION: 0;1                         ACCESS: Pointed to
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS

NUMBER: 4705                            IA #: 4705
  DATE CREATED: JUN 27, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSONDCUT
  NAME: PSONDCUT                        ID: PSONDCUT
 GENERAL DESCRIPTION:   This routine contains apis for retrieving, editing and
 saving NDC in the PRESCRIPTION file (#52).  
  STATUS: Active
KEYWORDS: ECME
KEYWORDS: BPS
KEYWORDS: EPHARMACY
KEYWORDS: GETNDC
KEYWORDS: PSONDCUT
COMPONENT/ENTRY POINT: $$GETNDC(RX,RFL)
 COMPONENT DESCRIPTION:   This routine returns the NDC for a specific
 prescription/fill. In case, the NDC is not found for a refill, the NDC for the
 original fill is returned.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTION file (#52).  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the REFILL multiple (#52.1) in the
 PRESCRIPTION file (#52).  
VARIABLES: $$GETNDC                     TYPE: Output
 VARIABLES DESCRIPTION:   Validated/formatted (5-4-2) NDC for the specific
 prescription/fill requested.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: CMOP
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4706                            IA #: 4706
  DATE CREATED: JUN 27, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOREJUT
  NAME: PSOREJUT                        ID: PSOREJUT
 GENERAL DESCRIPTION:   This routine contains APIs used for handling rejects
 from Third Party Payers that have clinical significance, such as DUR and
 REFILL TOO SOON rejects. These rejects are part of the ePharmacy project.  
  
 Amendment: Effective 5/15/23, added Component CLSALL 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: EPHARMACY
KEYWORDS: BPS
KEYWORDS: PSOREJUT
KEYWORDS: FIND
KEYWORDS: DUR
KEYWORDS: REJECT
KEYWORDS: DUR REJECT
COMPONENT/ENTRY POINT: $$FIND(RX,RFL,REJDATA,CODE,BESC,RRRFLAG)
 COMPONENT DESCRIPTION:   This API returns whether a specific prescription/fill
 has any OPEN/UNRESOLVED rejects. If so, it can also return the information
 about the reject.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTION file (#52).  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the REFILL multiple (#52.1) in the
 PRESCRIPTION file (#52).  
VARIABLES: REJDATA                      TYPE: Output
 VARIABLES DESCRIPTION:   Array contains the Reject(s) data:
 REJDATA("FIELD")=VALUE 
  
   "CODE" - Reject Code (79 or 88) 
   "DATE/TIME" - DATE/TIME Reject was detected 
   "PAYER MESSAGE" - Message returned by the payer 
   "REASON" - Reject Reason description (from payer) 
   "INSURANCE NAME" - Patient's Insurance Company Name 
   "GROUP NAME" - Patient's Insurance Group Name 
   "GROUP NUMBER" - Patient's Insurance Group Number 
   "CARDHOLDER ID" - Patient's Insurance Cardholder ID 
   "PLAN CONTACT" - Plan's Contact (eg., "1-800-...") 
   "PLAN PREVIOUS FILL DATE" - Last time Rx was paid by payer 
   "STATUS" - REJECTS status ("OPEN/UNRESOLVED" or "CLOSED/RESOLVED") 
   "DUR TEXT" - Payer's DUR description 
   "OTHER REJECTS" - Other Rejects on the same response 
    
 If REJECT is closed, the following fields will be returned: 
  
   "CLOSED DATE/TIME" - DATE/TIME Reject was closed 
   "CLOSED BY" - Name of the user responsible for closing Reject 
   "CLOSE REASON" - Reason for closing Reject (text) 
   "CLOSE COMMENTS" - User entered comments 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This specify which reject code should be looked for
 (e.g., 79, 88).  
  
VARIABLES: $$FIND                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 if a DUR/REFILL TOO SOON reject was found
 for the prescription/fill passed in. Otherwise, returns 0 (zero).  
VARIABLES: BESC                         TYPE: Input
 VARIABLES DESCRIPTION:   This specifies that RX is TRICARE/CHAMPVA and ECME
 status check for refills is not performed. 
  
VARIABLES: RRRFLAG                      TYPE: Input
 VARIABLES DESCRIPTION:   Pass a 1 in this parameter to also look for any
 unresolved Reject Resolution Required (RRR) rejects when CODE is also passed. 
  
 If CODE is not passed in, then pass a 1 to ONLY look for unresolved RRR
 rejects.  
  
 The default is 0 if not passed.  
  
COMPONENT/ENTRY POINT: SYNC(RX,RFL,USR,RXCOB)
 COMPONENT DESCRIPTION:   This API is used to synchronize the information about
 DUR and REFILL TOO SOON rejects from third party payers between Outpatient
 Pharmacy and ECME.  It should be called by ECME every time it receives a
 response from a third party payer.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTION file (#52).  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Pointer to the REFILL multiple (#52.1) in
 the PRESCRIPTION file (#52). If this information is not passed, the latest
 fill for the prescription is assumed.  
VARIABLES: USR                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) User using the system when this API is
 called.  
VARIABLES: RXCOB                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Coordination of benefits indicator may
 contain a value of 1 (one) for primary, 2 (two) for secondary, or 3 (three)
 for tertiary.  
COMPONENT/ENTRY POINT: CLSALL(RX,RFL,USR,REA,COM,COD1,COD2,COD3,CLA,PA)
 COMPONENT DESCRIPTION:   This procedure closes any open/unresolved rejects on
 the REJECT INFO sub-file (52.25) of the PRESCRIPTION file (52).  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Prescription, pointer to file 52.  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Refill #, 0 if original fill.  If not passed, the
 most recent fill will be used.  
VARIABLES: USR                          TYPE: Input
 VARIABLES DESCRIPTION:   The DUZ of the user to be cited as closing the
 rejects.  
VARIABLES: REA                          TYPE: Input
 VARIABLES DESCRIPTION:   Close reason code.  
VARIABLES: COM                          TYPE: Input
 VARIABLES DESCRIPTION:   Close comments.  
VARIABLES: COD1                         TYPE: Input
 VARIABLES DESCRIPTION:   First set of DUR overrides, in the format of Reason
 Code ^ Professional Service Code ^ Result Code 
VARIABLES: COD2                         TYPE: Input
 VARIABLES DESCRIPTION:   Second set of DUR overrides, in the format of Reason
 Code ^ Professional Service Code ^ Result Code 
VARIABLES: COD3                         TYPE: Input
 VARIABLES DESCRIPTION:   Third set of DUR overrides, in the format of Reason
 Code ^ Professional Service Code ^ Result Code 
VARIABLES: CLA                          TYPE: Input
 VARIABLES DESCRIPTION:   NCPDP Submission Clarification Code.  
VARIABLES: PA                           TYPE: Input
 VARIABLES DESCRIPTION:   NCPDP Prior Authorization code.  
SUBSCRIBING PACKAGE: CMOP
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: MAY 15, 2023

NUMBER: 4707                            IA #: 4707
  DATE CREATED: JUN 27, 2005
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSNDCUT
  NAME: PSSNDCUT                        ID: PSSNDCUT
 GENERAL DESCRIPTION:   This routine contains apis for retrieving and saving
 NDC in the DRUG file (#50).  
  STATUS: Active
KEYWORDS: ECME
KEYWORDS: BPS
KEYWORDS: PSSNDCUT
KEYWORDS: GETNDC
KEYWORDS: SAVNDC
KEYWORDS: EPHARMACY
COMPONENT/ENTRY POINT: $$GETNDC(DRG,SITE,CMOP)
 COMPONENT DESCRIPTION:   This api returns the CMOP/LOCAL NDC for a specific
 drug and division.  
VARIABLES: DRG                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the DRUG file (#50).  
VARIABLES: SITE                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the OUTPATIENT SITE file (#59).  
VARIABLES: CMOP                         TYPE: Input
 VARIABLES DESCRIPTION:   Indicates wheter the CMOP or the LOCAL NDC should be
 returned. 
  
    1 - CMOP NDC 
    0 - LOCAL NDC 
  
VARIABLES: $$GETNDC                     TYPE: Output
 VARIABLES DESCRIPTION:   Validated/formatted (5-4-2) NDC for the specific drug
 passed in.  
COMPONENT/ENTRY POINT: SAVNDC(DRG,SITE,NDC,CMP)
 COMPONENT DESCRIPTION:   This api is used to save an NDC in the DRUG file.  
VARIABLES: DRG                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the DRUG file (#50).  
VARIABLES: SITE                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the OUTPATIENT SITE file (#59).  
VARIABLES: NDC                          TYPE: Input
 VARIABLES DESCRIPTION:   NDC to be saved in the NDC BY OUTPATIENT SITE
 multiple (#50.032) in the DRUG file (#50).  
VARIABLES: CMP                          TYPE: Input
 VARIABLES DESCRIPTION:   Indicates whether the NDC is from CMOP (CMP=1) or not
 (CMP=0).  
COMPONENT/ENTRY POINT: $$NDCFMT(NDC)
 COMPONENT DESCRIPTION:   Used to format/validate NDC codes.  
VARIABLES: NDC                          TYPE: Input
 VARIABLES DESCRIPTION:   NDC to be formatted/validated.  
VARIABLES: $$NDCFMT                     TYPE: Output
 VARIABLES DESCRIPTION:   Validated/formatted (5-4-2) NDC or "" (null) if NDC
 is not valid.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 4708                            IA #: 4708
  DATE CREATED: JUN 27, 2005
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSDAWUT
  NAME: PSSDAWUT                        ID: PSSDAWUT
 GENERAL DESCRIPTION:   This routine contains apis related to DAW (Dispensed As
 Written) code for ePharmacy.  
  STATUS: Active
KEYWORDS: PSSDAWUT
KEYWORDS: ECME
KEYWORDS: DAWEXT
KEYWORDS: BPS
KEYWORDS: EPHARMACY
COMPONENT/ENTRY POINT: $$DAWEXT(CODE)
 COMPONENT DESCRIPTION:   Returns description for DAW code.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   DAW code. Below are all the existing values: 
  
   0 - NO PRODUCT SELECTION INDICATED 
   1 - SUBSTITUTION NOT ALLOWED BY PRESCRIBER 
   2 - SUBSTITUTION ALLOWED-PATIENT REQUESTED PRODUCT DISPENSED 
   3 - SUBSTITUTION ALLOWED-PHARMACIST SELECTED PRODUCT DISPENSED 
   4 - SUBSTITUTION ALLOWED-GENERIC DRUG NOT IN STOCK 
   5 - SUBSTITUTION ALLOWED-BRAND DRUG DISPENSED AS A GENERIC 
   6 - OVERRIDE 
   7 - SUBSTITUTION NOT ALLOWED-BRAND DRUG MANDATED BY LAW 
   8 - SUBSTITUTION ALLOWED-GENERIC DRUG NOT AVAILABLE IN MARKETPLACE 
   9 - OTHER 
  
VARIABLES: $$DAWEXT                     TYPE: Output
 VARIABLES DESCRIPTION:   Corresponding description for the NCPDP DAW CODE
 passed in.  
COMPONENT/ENTRY POINT: HLP
 COMPONENT DESCRIPTION:   This entry point is used for Data Dictionary
 Executable Help for DAW CODE fields in the PRESCRIPTION (#52) and DRUG (#50)
 files.  
COMPONENT/ENTRY POINT: INPUT
 COMPONENT DESCRIPTION:   This entry point is used for Data Dictionary Input
 Transform for DAW CODE fields in the PRESCRIPTION (#52) and DRUG (#50) files.  
VARIABLES: X                            TYPE: Both
 VARIABLES DESCRIPTION:   DAW CODE value to be validated by the Input
 Transform.  If the original value of X is invalid, X is killed off.  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   If the original value of X is valid, two fields
 separated by "^" (up-arrow) are returned in this variable: Internal Entry
 Number (IEN) from the BPS NCPDP DAW CODE file (#9002313.24), followed by the
 field .01 content. In case the original value of X is invalid, Y is set to -1. 
 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 4709                            IA #: 4709
  DATE CREATED: JUN 27, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBBFINA
  NAME: PFSS PROCESS INSURANCE FROM DG REGISTRATION
  ID: IBBFINA
 GENERAL DESCRIPTION:   The Registration application (DG) will receive messages
 sent from the COTS Billing package and then pass these messages off to the
 Integrated Billing (IB) package for insurance processing.  This IA will insure
 that Registration accesses the API used to pass the HL7 message off to IB for
 processing in the correct way.  The routine IBBFINA will be called at the
 entry point EN, passing the parameter for the internal entry number of the HL7
 message from file 772.  The API will parse the HL7 message and store insurance
 data values pertinent to the patient inside the new file structures defined
 for PFSS Insurance.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: INSURANCE
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Entry point to accept HL7 message to be used for
 extraction of PFSS insurance values.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the HL7 MESSAGE TEXT (#772) file
 containing the message to be processed.  
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   Registration (DG) will call EN^IBBFINA in order to
 process insurance segments of an HL7 message it has already processed for
 demographic changes.  DG will call EN^IBBFINA(IEN) using the HL7 IEN from file
 #772 in order to process the IN1, IN2, and IN3 segments of the message.  Upon
 completion, Registration will receive back either a positive integer to
 indicate successful addition of insurance message elements, or a negative
 integer concatenated with a message indicating an error of some sort with
 insurance processing.  The Registration package will then either send an
 application ACKnowledgement or Non-ACKnowledgement back to the HL7 messaging
 package indicating success or failure to process the message.  

NUMBER: 4710                            IA #: 4710
  FILE NUMBER: 356.8                    GLOBAL ROOT: IBE(356.8
  DATE CREATED: JUN 28, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4710
  ID: IBE(356.8
GLOBAL REFERENCE: IBE(356.8,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: ECME PAPER FLAG
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ECME FLAG
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: IBE(356.8,'B'
 GLOBAL DESCRIPTION:   direct read 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
 SUBSCRIBING DETAILS:   ECME is storing the pointer to the file #356.8 --
 CLAIMS TRACKING NON-BILLABLE REASONS file in its #9002313.02 BPS CLAIMS file,
 the field (#904) CLOSED REASON [4P:356.8] 

NUMBER: 4711                            IA #: 4711
  DATE CREATED: JUN 27, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSORXVW
  NAME: DBIA4711                        ID: PSORXVW
 GENERAL DESCRIPTION:   This call is needed to allow ECME to invoke View
 Prescription functionality provided by Outpatient Pharmacy package.  This is
 needed  to prevent users from having to exit one menu option and access
 another option.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
COMPONENT/ENTRY POINT: DP
 COMPONENT DESCRIPTION:   Entry point for View Prescription option.  
VARIABLES: PSOVDA                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of file #52 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN of file #52 
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 4712                            IA #: 4712
  FILE NUMBER: 9002313.21               GLOBAL ROOT: BPS(9002313.21,
  DATE CREATED: JUL 05, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: LOOKUP/READ ACCESS TO FILE #9002313.21
  ID: BPS(9002313.21,
GLOBAL REFERENCE: BPS(9002313.21,
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   NCPDP PROFESSIONAL SERVICE CODE identifying pharmacist
 intervention when a conflict code has been identified or service has been
 rendered. 
FIELD NUMBER: 1                         FIELD NAME: DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Description of the NCPDP PROFESSIONAL SERVICE CODE.  
FIELD NUMBER: 2                         FIELD NAME: INACTIVE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   If set to 1/INACTIVE, then this entry cannot be entered
 or selected by the user.  
 GENERAL DESCRIPTION:   Permission to subscriber packages to make reference to
 this file to perform lookups or read its fields. No write access.  
  
 Amendment: Effective 5/15/23, added field 2 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: EPHARMACY
KEYWORDS: BPS
KEYWORDS: PROFESSIONAL
KEYWORDS: SERVICE CODE
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   BPS is responsible to check +$$SWSTAT^IBBAPI for a
 return value of 0, if 1 is returned this call is not supported.  
  DATE ACTIVATED: MAY 15, 2023

NUMBER: 4713                            IA #: 4713
  FILE NUMBER: 9002313.22               GLOBAL ROOT: BPS(9002313.22,
  DATE CREATED: JUL 05, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: LOOKUP/READ ACCESS TO FILE #9002313.22
  ID: BPS(9002313.22,
GLOBAL REFERENCE: BPS(9002313.22,
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   NCPDP RESULT OF SERVICE CODE identifying the action taken
 by a pharmacist in response to a conflict or the result of a pharmacist's
 professional service.  
FIELD NUMBER: 1                         FIELD NAME: DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Description of the NCPDP RESULT OF SERVICE CODE.  
FIELD NUMBER: 2                         FIELD NAME: INACTIVE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   If set to 1/INACTIVE, then this entry cannot be entered
 or selected by the user.  
 GENERAL DESCRIPTION:   Permission to subscriber packages to make reference to
 this file to perform lookups or read its fields. No write access.  
  
 Amendment: Effective 5/15/23, added field 2 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: EPHARMACY
KEYWORDS: BPS
KEYWORDS: RESULT OF SERVICE
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   BPS is responsible to check +$$SWSTAT^IBBAPI for a
 return value of 0, if 1 is returned this call is not supported.  
  DATE ACTIVATED: MAY 16, 2023

NUMBER: 4714                            IA #: 4714
  FILE NUMBER: 9002313.23               GLOBAL ROOT: BPS(9002313.23,
  DATE CREATED: JUL 05, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: LOOKUP/READ ACCESS TO FILE #9002313.23
  ID: BPS(9002313.23,
GLOBAL REFERENCE: BPS(9002313.23,
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   REASON FOR SERVICE CODE identifying the type of
 utilization conflict detected or the reason for the pharmacist's professional
 service.  
FIELD NUMBER: 1                         FIELD NAME: DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Description of the REASON FOR SERVICE CODE.  
FIELD NUMBER: 2                         FIELD NAME: INACTIVE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   If set to 1/INACTIVE, then this entry cannot be entered
 or selected by the user.  
 GENERAL DESCRIPTION:   Permission to subscriber packages to make reference to
 this file to perform lookups or read its fields. No write access.  
  
 Amendment: Effective 5/15/23, added field 2 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: EPHARMACY
KEYWORDS: BPS
KEYWORDS: REASON FOR SERVICE CODE
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   BPS is responsible to check +$$SWSTAT^IBBAPI for a
 return value of 0, if 1 is returned this call is not supported.  
  DATE ACTIVATED: MAY 16, 2023

NUMBER: 4715                            IA #: 4715
  FILE NUMBER: 9002313.24               GLOBAL ROOT: BPS(9002313.24,
  DATE CREATED: JUL 05, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: LOOKUP/READ ACCESS TO FILE #9002313.24
  ID: BPS(9002313.24,
GLOBAL REFERENCE: BPS(9002313.24,
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Code indicating whether or not the prescriber's
 instructions regarding generic substitution were followed.  
FIELD NUMBER: 1                         FIELD NAME: DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Description of the DAW CODE.  
FIELD NUMBER: 2                         FIELD NAME: INACTIVE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   If set to 1/INACTIVE, then this entry cannot be entered
 or selected by the user.  
 GENERAL DESCRIPTION:   Permission to subscriber packages to make reference to
 this file to perform lookups or read its fields. No write access.  
  
 Amendment: Effective 5/15/23, added field 2 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
KEYWORDS: EPHARMACY
KEYWORDS: DAW
KEYWORDS: DAW CODE
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   BPS is responsible to check +$$SWSTAT^IBBAPI for a
 return value of 0, if 1 is returned this call is not supported.  
  DATE ACTIVATED: MAY 15, 2023

NUMBER: 4716                            IA #: 4716
  DATE CREATED: AUG 19, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOAPI
  NAME: HLO BUILD MESSAGE APIS          ID: HLOAPI
 GENERAL DESCRIPTION:   These APIs are used to build HLO messages.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$NEWMSG(.PARMS,.HLMSTATE,.ERROR)
 COMPONENT DESCRIPTION:   This API is to be used by applications that need to
 send an HL7 message via HLO.  It starts the message building process.  
VARIABLES: PARMS                        TYPE: Input
 VARIABLES DESCRIPTION:   PARMS ("COUNTRY") - A three-character country code
 (optional).  ("CONTINUATION POINTER")  - Indicates a fragmented message.  
 ("EVENT") - A three-character event type (required).  ("FIELD SEPARATOR") -
 Field separator (optional, defaults to "|").  ("ENCODING CHARACTERS") - Four
 HL7 encoding characters (optional, defaults to "(^~\&").  ("MESSAGE
 STRUCTURE") - MSH 9, component 3 - a code from the standard HL7table
 ((optional).  ("MESSAGE TYPE")- A three-character message type (required).  
 ("PROCESSING MODE") - MSH 11, component 2 - A one character code (optional).  
 ("VERSION") - The HL7 Version ID, for example, "2.4" (optional, defaults to
 2.4).  
VARIABLES: HLMSTATE                     TYPE: Output
 VARIABLES DESCRIPTION:   Used by the HL7 package to track the progress of the
 message.  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   Optional. Returns an error message on failure.  
VARIABLES: $$NEWMSG                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 on success, 0 on failure.  
COMPONENT/ENTRY POINT: $$NEWBATCH(.PARMS,.HLMSTATE,.ERROR) 
 COMPONENT DESCRIPTION:   This API is to be used by applications that need to
 send a batch of HL7 message via HLO.  It starts the batch building process.  
VARIABLES: PARMS                        TYPE: Input
 VARIABLES DESCRIPTION:   ("COUNTRY") - A three-character country code
 (optional).  ("FIELD SEPARATOR") - Field separator (optional, defaults to "
 |").  ("ENCODING CHARACTERS") - Four HL7 encoding characters (optional,
 defaults to "^~\&").  ("VERSION") - HL7 Version ID, for example, "2.4"
 (optional, defaults to 2.4).  
VARIABLES: HLMSTATE                     TYPE: Output
 VARIABLES DESCRIPTION:   Used by the HL7 package to track the progress of the
 message.  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns an error message on failure.  
VARIABLES: $$NEWBATCH                   TYPE: Output
 VARIABLES DESCRIPTION:   Function returns 1 on success, 0 on failure.  
COMPONENT/ENTRY POINT: $$ADDMSG(.HLMSTATE,.PARMS,.ERROR) 
 COMPONENT DESCRIPTION:   Used by applications to add a message to a batch that
 is in the process of being built.  
VARIABLES: $$ADDMSG                     TYPE: Output
 VARIABLES DESCRIPTION:   The function returns 1 on success, 0 on failure.  
VARIABLES: HLMSTATE                     TYPE: Both
 VARIABLES DESCRIPTION:   An array used by the HL7 package to track the
 progress of the message as it is being built.  
VARIABLES: PARMS                        TYPE: Input
 VARIABLES DESCRIPTION:   ("EVENT") - A three-character event type (required).  
 ("MESSAGE TYPE") - A three-character message type (required).  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   Optional - returns an error message on failure.  
COMPONENT/ENTRY POINT: SET(.SEG,VALUE,FIELD,COMP,SUBCOMP,REP)
 COMPONENT DESCRIPTION:   Used to set a value into a segment that is in the
 process of being built.  
VARIABLES: SEG                          TYPE: Both
 VARIABLES DESCRIPTION:   The array where the segment is being built.  
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   The individual value to be set into the segment.  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   The sequence # of the field (optional, defaults to 0) 
 Note: FIELD=0 is used to denote the segment type.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   The # of the component (optional, defaults to 1).  
VARIABLES: SUBCOMP                      TYPE: Input
 VARIABLES DESCRIPTION:   The # of the subcomponent (optional, defaults to 1).  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   The occurrence# (optional, defaults to 1)  For a
 non-repeating field, the occurrence # need not be provided, because it would
 be 1.  
COMPONENT/ENTRY POINT: $$ADDSEG(.HLMSTATE,.SEG,.ERROR)
 COMPONENT DESCRIPTION:   Used to add a segment that has just been built to a
 message that is still in the process of being built.  
VARIABLES: $$ADDSEG                     TYPE: Output
 VARIABLES DESCRIPTION:   Function returns 1 on success, 0 on failure.  
VARIABLES: HLMSTATE                     TYPE: Both
 VARIABLES DESCRIPTION:   Used by the HL7 package to track the progress of the
 message as it is being built.  
VARIABLES: SEG                          TYPE: Input
 VARIABLES DESCRIPTION:   Required. Contains the segment built by calls to SET
 prior to calling $$ADDSEG.  
   
 Note#1:  The message control segments, including the MSH and BHS segments, are
 added automatically.  Note#2:  The 0th field must be a 3 character segment
 type.  Note#3:  SEG is killed upon successfully adding the segment.  
  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns an error message on failure.  
COMPONENT/ENTRY POINT: MOVEMSG(.HLMSTATE,.ARY) 
 COMPONENT DESCRIPTION:   If a message was built using any other method than
 the HLO APIs and resides in an array, it will be moved into HLO. This API
 allows segment builders that were created prior to HLO to be used within HLO.  
VARIABLES: HLMSTATE                     TYPE: Both
 VARIABLES DESCRIPTION:   Created by calling $$NEWMSG^HLOAPI or
 $$NEWBATCH^HLOAPI. It tracks the progress of the message as its is being
 built.  
VARIABLES: ARY                          TYPE: Input
 VARIABLES DESCRIPTION:   The name of the local or global variable where the
 message was built.  It is accessed via indirection to move the message into
 HLO.  
COMPONENT/ENTRY POINT: $$MOVESEG(.HLMSTATE,.SEG,.ERROR)
 COMPONENT DESCRIPTION:   Adds a segment built in the 'traditional' way as an
 array of lines into the HLO message under construction.  
  
VARIABLES: HLMSTATE                     TYPE: Both
 VARIABLES DESCRIPTION:   This variable contains the message that is being
 built.  
  
VARIABLES: SEG                          TYPE: Input
 VARIABLES DESCRIPTION:   This variable contains the segment that is to be
 appended to the message. 
  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   If the segment is not appended to the message, an
 error message is returned. 
  
  DATE ACTIVATED: DEC 26, 2012

NUMBER: 4717                            IA #: 4717
  DATE CREATED: AUG 19, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOAPI1
  NAME: HLO SEND MESSAGE APIS           ID: HLOAPI1
 GENERAL DESCRIPTION:   These APIs provide the ability to address a message
 that has already been built and put it on an out-going queue for transmission. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$SENDONE(.HLMSTATE,.PARMS,.WHOTO,.ERROR)
 COMPONENT DESCRIPTION:   Sends the message to a single recipient.  The
 recipient is identified in the message header by the Receiving Facility and
 the Receiving Application.  The message may optionally be routed through an
 interface engine.  
VARIABLES: $$SENDONE                    TYPE: Output
 VARIABLES DESCRIPTION:   Function call returns the IEN of the message in file
 778 on success, 0 on failure.  
VARIABLES: HLMSTATE                     TYPE: Both
 VARIABLES DESCRIPTION:   Used by the HL7 package to track the progress of the
 message. 
  
VARIABLES: PARMS                        TYPE: Input
 VARIABLES DESCRIPTION:   ( "APP ACK RESPONSE")=<tag^routine> to call in
 response to app ack (i.e., not received). (Optional.  This parameter is
 ignored if the ACK TO parameter is present.) ( "APP ACK TYPE") = <AL,NE>
 (Optional, defaults to NE).  ( "ACCEPT ACK RESPONSE")=<tag^routine> to call in
 response to a commit ack(optional).  ( "ACCEPT ACK TYPE") = <AL,NE> (Optional,
 defaults to AL).  ("FAILURE RESPONSE") - <tag>^<routine> (Optional) The
 sending application routine to execute when the transmission of the message
 fails, i.e., the message can not be sent or no commit ack is received.  
 ("QUEUE") - Optional. An application can name its own private queue -  just a
 string under 20 characters, it should be namespaced.  ("SECURITY")=Security
 information to include in the header segment, SEQ 8 (Optional).  ("SENDING
 APPLICATION")=name of sending application (required, 60 max-length).  
VARIABLES: WHOTO                        TYPE: Input
 VARIABLES DESCRIPTION:   Required. Specifies a single recipient.  ("RECEIVING
 APPLICATION") - String, 60 char max, required.  
  
        One of the following four parameters is required to identify the 
 Receiving Facility: 
  
 ("FACILITY LINK IEN") - IEN of the logical link.  ("FACILITY LINK NAME") -
 Name of the logical link.  ("INSTITUTION IEN") - Pointer to the INSTITUTION
 file.  ("STATION NUMBER") -  Station # with suffix.  
    
 One of the following two parameters MAY be provided, optionally,  to identify
 the interface engine to route the message through: 
  
 ("IE LINK IEN")  -  Pointer to a logical link for the interface engine.  ("IE
 LINK NAME") - Name of the logical link for the interface engine.  
  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns an message on error.  
COMPONENT/ENTRY POINT: $$SENDMANY(.HLMSTATE,.PARMS,.WHOTO)
 COMPONENT DESCRIPTION:   Sends the message that has already been built to a
 list of recipients.  
VARIABLES: $$SENDMANY                   TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 on success, 0 on failure.  
VARIABLES: HLMSTATE                     TYPE: Both
 VARIABLES DESCRIPTION:   This array is used to track the progress of the
 message.  
VARIABLES: PARMS                        TYPE: Input
 VARIABLES DESCRIPTION:   ( "APP ACK RESPONSE")=<tag^routine> to call in
 response to app ack (i.e., not received). (Optional.  This parameter is
 ignored if the ACK TO parameter is present.) ( "APP ACK TYPE") = <AL,NE>
 (Optional, defaults to NE).  ( "ACCEPT ACK RESPONSE")=<tag^routine> to call in
 response to a commit  ack (optional).  ( "ACCEPT ACK TYPE") = <AL,NE>
 (Optional, defaults to AL).  ("FAILURE RESPONSE") - <tag>^<routine> (Optional)
 The sending application routine to execute when the transmission of the
 message fails, i.e., the message can not be sent or no commit ack is received. 
 ("QUEUE") - Optional. An application can name its own private queue -  just a
 string under 20 characters, it should be namespaced.  ("SECURITY")=Security
 information to include in the header segment, SEQ 8 (Optional).  ("SENDING
 APPLICATION")=name of sending application (required, 60 max-length).  
  
VARIABLES: WHOTO                        TYPE: Both
 VARIABLES DESCRIPTION:   For Input: Specifies a list of recipients.  Each
 recipient should be listed individually in array WHOTO(i), where i=a
 recipient. For each recipient the same subscripts may be defined as in the
 $$SENDONE API.  For example: 
   
 WHOTO(1,"LINK NAME")="VAALB" WHOTO(1,"RECEIVING APPLICATION")="MPI" 
 WHOTO(2,"STATION NUMBER")=500 WHOTO(2,"RECEIVING APPLICATION")="MPI" 
  
  
 For Output: Returns the status of each message to be sent in the format: 
 (<i>,"QUEUED") - 1 if queued to be sent, 0 otherwise.  (<i>,"IEN") - IEN, file
 778.  (<i>,"ERROR") - Error message if an error was encountered (status=0),not
 defined otherwise.  
  
COMPONENT/ENTRY POINT: $$SENDSUB(.HLMSTATE,.PARMS,.MESSAGES)
 COMPONENT DESCRIPTION:   Send Messages to Subscription Registry Subscribers 
VARIABLES: $$SENDSUB                    TYPE: Output
 VARIABLES DESCRIPTION:   Function call returns 1 if a message is queued to be
 sent to each intended recipient, 0 otherwise.  
  
VARIABLES: HLMSTATE                     TYPE: Both
 VARIABLES DESCRIPTION:   Used by HLO internally to track the progress of the
 message.  
VARIABLES: PARMS                        TYPE: Input
 VARIABLES DESCRIPTION:   Required. Same as $$SENDMANY^HLOAPI1, with one
 additional subscript: 
  
 ( "SUBSCRIPTION IEN") -The IEN of an entry in the HLO SUBSCRIPTION REGISTRY
 file (#779.4), defining the intended recipients of this message 
  
VARIABLES: MESSAGES                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns the status of each message to be sent in this
 format, where the sub-IEN is the IEN of the recipient in the RECIPIENTS
 sub-file of the HLO SUBSCRIPTION REGISTRY file (#779.4).  
  
 (<subien>,"QUEUED") - 1 if queued to be sent, 0 otherwise.  (<subien>,"IEN") -
 IEN, HLO MESSAGES file (#778).  (<subien>,"ERROR") - Error message if an error
 was encountered (status=0),;not defined otherwise.  
  

NUMBER: 4718                            IA #: 4718
  DATE CREATED: AUG 19, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOPRS
  NAME: HLO PARSING APIS                ID: HLOPRS
 GENERAL DESCRIPTION:   These APIs are to be used by applications that receive
 HL7 messages via HLO.  They provide the means of stepping through batches of
 messages, the message segments, and fetching data values from within segments. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$STARTMSG(.HLMSTATE,IEN,.HDR)
 COMPONENT DESCRIPTION:   This function begins the parsing of the message,
 parsing the header and returning the individual values in the array HDR().  
VARIABLES: $$STARTMSG                   TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 on success, 0 on failure.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the message in file 778. 
 
VARIABLES: HLMSTATE                     TYPE: Output
 VARIABLES DESCRIPTION:   Required. This array is used by the HL7 package to
 track the progress of parsing the message.  The application MUST NOT touch it. 
 
VARIABLES: HDR                          TYPE: Output
 VARIABLES DESCRIPTION:   Optional.   This array contains the results of
 parsing the message header.  
COMPONENT/ENTRY POINT: $$NEXTSEG(.HLMSTATE,.SEG)
 COMPONENT DESCRIPTION:   Advances parsing to the next segment within the
 message.  
VARIABLES: $$NEXTSEG                    TYPE: Output
 VARIABLES DESCRIPTION:   Function  returns 1 on success, 0 if there are no
 more segments in this message.  For batch messages, a return value of 0 does
 not preclude the possibility that there are additional individual messages
 within the batch.  
VARIABLES: HLMSTATE                     TYPE: Both
 VARIABLES DESCRIPTION:   HLMSTATE is an array used internally by HLO to track
 the progress of parsing.  
VARIABLES: SEG                          TYPE: Output
 VARIABLES DESCRIPTION:   The segment is returned in this array.  
COMPONENT/ENTRY POINT: $$NEXTMSG(.HLMSTATE,.MSH)
 COMPONENT DESCRIPTION:   Advances to the next message within the batch, with
 the MSH segment returned.  
VARIABLES: $$NEXTMSG                    TYPE: Output
 VARIABLES DESCRIPTION:   Function returns 1 on success, 0 if there are no more
 messages.  
VARIABLES: HLMSTATE                     TYPE: Both
 VARIABLES DESCRIPTION:   This array is used by HLO to track the current
 position in the message.  
VARIABLES: MSH                          TYPE: Output
 VARIABLES DESCRIPTION:   Returns the MSH segment, parsed into its individual
 values.  
COMPONENT/ENTRY POINT: $$GET(.SEG,FIELD,COMP,SUBCOMP,REP)
 COMPONENT DESCRIPTION:   This function gets a specified value from a segment
 that was parsed by $$NEXTSEG^HLOPRS. The FIELD,COMP,SUBCOMP,REP parameters are
 optional - if not specified, they default to 1.  
  
 Example: $$GET^HLOPRS(.SEG,1) will return the value of the first field, first 
 component, first subcomponent, in the first occurrence of field #1.  
VARIABLES: $$GET                        TYPE: Output
 VARIABLES DESCRIPTION:   This function returns a specified value from a
 segment.  
VARIABLES: SEG                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the array where the parsed segment was placed
 by $$NEXTSEG^HLOPRS.  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   The sequence # of the field (optional, defaults to
 1). If 0 (zero) is specified, then the function returns the segment type.  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   The number of the component (optional, defaults to
 1).  
VARIABLES: SUBCOMP                      TYPE: Input
 VARIABLES DESCRIPTION:   The number of the subcomponent (optional, defaults to
 1).  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   The occurrence number (optional, defaults to 1)  For
 a non-repeating field, the occurrence number need not be provided, because it
 would be 1.  

NUMBER: 4719                            IA #: 4719
  DATE CREATED: AUG 16, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: BPSBUTL
  NAME: BPSBUTL                         ID: BPSBUTL
 GENERAL DESCRIPTION:   This routine contains apis that are being used by
 outside applications to retrieve/file information relevant to 3rd Party
 Electronic Billing (ePharmacy).  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NABP
KEYWORDS: EPHARMACY
KEYWORDS: ECME
KEYWORDS: BPSBUTL
KEYWORDS: CLAIM
KEYWORDS: ADDCOMM
KEYWORDS: DIVNCPDP
KEYWORDS: GETDAT
KEYWORDS: AMT
KEYWORDS: NFLDT
KEYWORDS: BBILL
KEYWORDS: ELIG
KEYWORDS: GETBAMT
KEYWORDS: GETCOB
KEYWORDS: RESUBMIT
COMPONENT/ENTRY POINT: $$NABP(RXP,BFILL)
 COMPONENT DESCRIPTION:   Returns the value in the Service Provider ID (201-B1)
 field of the last NCPDP claim submitted for the passed in RX and fill.  Note
 that as of the NPI release (BPS*1.0*2), this API may return either NPI or
 NABP/NCPDP, depending on what was sent in the claim.  
VARIABLES: RXP                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTION file (#52).  This is a
 required parameter.  
VARIABLES: BFILL                        TYPE: Input
 VARIABLES DESCRIPTION:   Fill/refill number.  If this is not passed in, it
 will be defaulted to 0.  
VARIABLES: $$NABP                       TYPE: Output
 VARIABLES DESCRIPTION:   NPI number or NABP/NCPDP, depending on what was sent
 in the NCPDP claim.  Note that if the Prescription IEN is not passed in, this
 function will return NULL.  
COMPONENT/ENTRY POINT: $$CLAIM(RXI,RXR,COB)
 COMPONENT DESCRIPTION:   This API is used to retrieve information about a
 claim for an specific prescription, fill, and coordination of benefit value.  
VARIABLES: RXI                          TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN (Pointer to the PRESCRIPTION File
 (#52).  This parameter is required.  
VARIABLES: RXR                          TYPE: Input
 VARIABLES DESCRIPTION:   Fill Number (0 for Original, 1 for 1st refill, 2 for
 the 2nd refill, etc.).  If this parameter is missing, it will default to zero. 
 
VARIABLES: COB                          TYPE: Input
 VARIABLES DESCRIPTION:   Coordination of Benefit value (1-Primary,
 2-Secondary, 3-Tertiary).  If not passed in, primary is assumed.  
VARIABLES: $$CLAIM                      TYPE: Output
 VARIABLES DESCRIPTION:   The following information is returned ("^" pieces): 
  
    1 - BPS TRANSACTION file (#9002313.59) pointer 
    2 - BPS CLAIMS file (#9002313.02) pointer 
    3 - BPS RESPONSES file (#9002313.03) pointer 
    4 - BPS CLAIMS file (#9002313.02) pointer for REVERSAL Claim 
    5 - BPS RESPONSES file (#9002313.03) pointer for REVERSAL Claim 
    6 - The ECME Number sent in the last ECME Claim 
COMPONENT/ENTRY POINT: $$DIVNCPDP(BPSDIV)
 COMPONENT DESCRIPTION:   This API returns the NPI and NABP/NCPDP numbers for a
 specific outpatient site 
VARIABLES: BPSDIV                       TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the Outpatient Site file -
 Required 
VARIABLES: $$DIVNCPDP                   TYPE: Output
 VARIABLES DESCRIPTION:   The function returns the NCPDP and NPI numbers
 associated with the Outpatient Site in the format NCPDP Number^NPI Number.  If
 the Outpatient Site is not passed in or if the identifiers could not be
 determined, the function will return just a caret ("^").  
COMPONENT/ENTRY POINT: $$ADDCOMM(BPRX,BPREF,BPRCMNT,BPBKG)
 COMPONENT DESCRIPTION:   This api is used to pass user entered comments about
 Rejects back to ECME.  
VARIABLES: BPRX                         TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN (Pointer to the PRESCRIPTION File
 (#52)).  This parameter is required.  If it not passed in, the API will return
 -1 indicating the comment was not filed.  
VARIABLES: BPREF                        TYPE: Input
 VARIABLES DESCRIPTION:   Fill Number (0 for Original, 1 for 1st refill, 2 for
 the 2nd refill, etc.).  If not passed in, it will be defaulted to zero.  
VARIABLES: $$ADDCOMM                    TYPE: Output
 VARIABLES DESCRIPTION:   
   1 - Comments added successfully 
  -1 - Comments not added 
VARIABLES: BPRCMNT                      TYPE: Input
 VARIABLES DESCRIPTION:   Comments to be added to the BPS TRANSACTION file
 (#9002313.59).  Note that this value will be truncated to 63 characters prior
 to filing.  This parameter is required.  If missing, the API will return -1
 indicating no comment was filed.  
VARIABLES: BPBKG                        TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter to indicate if the API was called
 by a background process.  
  
 If this parameter value is 1 then the comment is stored in BPS TRANSACTION 
 (#9002313.59) file with POSTMASTER as the user entering the comment.  
  
COMPONENT/ENTRY POINT: GETDAT(RX,FIL,COB,LDOS,LDSUP)
 COMPONENT DESCRIPTION:   This API is used to get the LAST DATE OF SERVICE and
 LAST DAYS SUPPLY from the most recent claim submitted for a prescription and
 fill.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   The RX IEN from the PRESCRIPTION file (#52).  This
 parameter is required.  If not passed in, the API will not continue.  
VARIABLES: FIL                          TYPE: Input
 VARIABLES DESCRIPTION:   The prescription fill number. This parameter is
 required. If not passed in, the API will not continue.  
VARIABLES: COB                          TYPE: Input
 VARIABLES DESCRIPTION:   Coordination of Benefits indicator.  This parameter
 is optional.  If not passed in, the API will default it to 1, meaning PRIMARY. 
 
VARIABLES: LDOS                         TYPE: Both
 VARIABLES DESCRIPTION:   Last Date of Service from the most recent claim
 submitted for the prescription and fill.  This parameter is required to be
 passed by reference.  If not passed then GETDAT will not return the expected
 value.  
VARIABLES: LDSUP                        TYPE: Both
 VARIABLES DESCRIPTION:   Last Days Supply from the most recent claim submitted
 for the prescription and fill.  This parameter is required to be passed by 
 reference.  If not passed then GETDAT will not return the expected value.  
COMPONENT/ENTRY POINT: $$AMT(RX,RFILL,COB)
 COMPONENT DESCRIPTION:   This API returns the Gross Amount Due for the given
 Rx, Fill and COB from the BPS TRANSACTION FILE (9002313.59), (Field #902.15).
 The value is in internal numeric format (i.e. 188.2 or 65.0895).  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the Prescription file #52
 (Required).  
  
  
  
VARIABLES: RFILL                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the fill number of the prescription
 (Optional). Defaults to original fill if not passed. 
  
VARIABLES: COB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the COB payer sequence number of the ECME
 bill (Optional). Defaults to 1 (Primary) if not passed.  
  
VARIABLES: $$AMT                        TYPE: Output
 VARIABLES DESCRIPTION:   The function value is the value of the Gross Amount
 Due field (#902.15) from the #9002313.59902 subfile of the BPS Transaction
 file.  
COMPONENT/ENTRY POINT: $$NFLDT(RX,RFILL,COB)
 COMPONENT DESCRIPTION:   This API returns the Next Available Fill Date from
 BPS RESPONSES File #9002313.03.  
  
  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the Prescription file #52 (Required).  
  
  
VARIABLES: RFILL                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the fill number of the prescription
 (Required).  
  
VARIABLES: COB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the COB payer sequence number of the original
 bill (optional). Defaults to 1 (primary) if not passed.  
  
VARIABLES: $$NFLDT                      TYPE: Output
 VARIABLES DESCRIPTION:   Next Available Fill Date.  
  
COMPONENT/ENTRY POINT: $$BBILL(RX,RFILL,COB)
 COMPONENT DESCRIPTION:   Back Bill indicator from BPS CLAIMS file #9002313.02. 
 
 Returns 1 if RX ACTION code of "BB", "P2" or "P2S" is found.  Otherwise
 returns 0.  
  
  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the Prescription file #52
 (Required).  
  
  
VARIABLES: RFILL                        TYPE: Input
 VARIABLES DESCRIPTION:   Fill/refill number (Optional). Defaults to 0
 (original fill) if not passed.  
  
VARIABLES: COB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the COB payer sequence number of the original
 bill (optional). Defaults to 1 (primary) if not passed.  
  
VARIABLES: $$BBILL                      TYPE: Output
 VARIABLES DESCRIPTION:   Back Bill Indicator 
  
 1 - Back Bill 0 - Not a Back Bill 
  
COMPONENT/ENTRY POINT: $$ELIG(RX,RFILL,COB)
 COMPONENT DESCRIPTION:   This API returns the Eligibility for the given Rx,
 Fill and COB. 
  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   This is the pointer to the Prescription file #52
 (Required).  
  
  
  
VARIABLES: RFILL                        TYPE: Input
 VARIABLES DESCRIPTION:   Fill/Refill number (Optional). Defaults to 0
 (origianl fill) if not passed.  
  
VARIABLES: COB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the COB payer sequence number of the ECME
 bill (Optional). Defaults to 1 (primary) if not passed.  
  
VARIABLES: $$ELIG                       TYPE: Output
 VARIABLES DESCRIPTION:   The function value is the value of the Gross Amount
 Due field (#901.04) from the BPS Transaction file #9002313.59.  
  
COMPONENT/ENTRY POINT: $$GETBAMT(RXIEN,FILL,COB)
 COMPONENT DESCRIPTION:   Retrieves the Billed Gross Amount Due (Field #430)
 from the BPS CLAIMS FILE (#9002313.02). This function retrieves the external
 dollar.cents format.  
VARIABLES: RXIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN pointer to the PRESCRIPTION File
 (#52). This parameter is required.  
VARIABLES: FILL                         TYPE: Input
 VARIABLES DESCRIPTION:   Fill Number (0 for Original, 1 for 1st refill, 2 for
 the 2nd refill, etc.). If this parameter is missing, it will default to the
 latest fill.  
VARIABLES: COB                          TYPE: Input
 VARIABLES DESCRIPTION:   Coordination of Benefits value (1-Primary,
 2-Secondary). If not passed in, it defaults to Primary.  
VARIABLES: $$GETBAMT                    TYPE: Output
 VARIABLES DESCRIPTION:   Return value of the Gross Amount Due from the BPS
 CLAIMS FILE #9002313.02 (Field #430).  
COMPONENT/ENTRY POINT: $$GETCOB(RXIEN,FILL)
 COMPONENT DESCRIPTION:   This API returns the Coordination of Benefits (COB)
 Payer sequence for usage by Outpatient Pharmacy.  
VARIABLES: RXIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the Prescription file #52 (Required).  
VARIABLES: FILL                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the fill number of the prescription
 (Required).  
VARIABLES: $$GETCOB                     TYPE: Output
 VARIABLES DESCRIPTION:   "" (the null string) - If the Prescription/Fill is
 not found in the BPS Transaction file.  
                             
 -1 - If there are multiple COB payer sequences found in the BPS Transaction
 file (#9002313.59) for this prescription.  
                             
 Otherwise, the function value is a pieced string: COB^BPS Transaction IEN
 (pointer to file #9002313.59) 
COMPONENT/ENTRY POINT: $$RESUBMIT(RX,REFILL,COB)
 COMPONENT DESCRIPTION:   This API returns whether or not the ECME prescription
 is an ECME resubmitted prescription. The return value is either 0 or 1.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the Prescription file #52 (Required).  
VARIABLES: REFILL                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the fill number of the prescription
 (Optional). Defaults to the most recent fill number.  
VARIABLES: COB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Coordination of Benefits (COB) payer
 sequence number (Optional). Defaults to 1 (Primary payer).  
VARIABLES: $$RESUBMIT                   TYPE: Output
 VARIABLES DESCRIPTION:   Either 0 or 1. 1 if the ECME prescription is
 classified as an ECME resubmission. 0 otherwise.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: JUL 23, 2013

NUMBER: 4720                            IA #: 4720
  FILE NUMBER: 9002313.93               GLOBAL ROOT: BPSF(9002313.93,
  DATE CREATED: JUL 07, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: LOOKUP/READ ACCESS TO FILE #9002313.93
  ID: BPSF(9002313.93,
GLOBAL REFERENCE: BPSF(9002313.93,
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Code identifying the reason for the claim rejection by
 the third party payer.  
FIELD NUMBER: 1                         FIELD NAME: EXPLANATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Description of the reason for the claim rejection by the
 third party payer.  
 GENERAL DESCRIPTION:   Permission to subscriber packages to make reference to
 this file to perform lookups or read its fields. No write access.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: EPHARMACY
KEYWORDS: REJECT
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: AUG 25, 2010

NUMBER: 4721                            IA #: 4721
  DATE CREATED: JUL 07, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  ROUTINE: IBNCPDPI                     NAME: DBIA4721
  ID: IBNCPDPI
 GENERAL DESCRIPTION:   This agreement includes various INTEGRATED BILLING APIs
 for use by the E CLAIMS MGMT ENGINE to provide data necessary for processing 
 electronic claims.  
  STATUS: Other                         DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
COMPONENT/ENTRY POINT: $$SELINSUR(PRMTMSG,DFLTVAL)
 COMPONENT DESCRIPTION:   Insurance Company lookup API.  
VARIABLES: PRMTMSG                      TYPE: Input
 VARIABLES DESCRIPTION:   Prompt message.  
VARIABLES: DFLTVAL                      TYPE: Input
 VARIABLES DESCRIPTION:   INSURANCE NAME as a default value for the prompt
 (optional).  
VARIABLES: $$SELINSUR                   TYPE: Output
 VARIABLES DESCRIPTION:   returned value (one of the following): 
  
  IEN^INSURANCE_NAME 
   0^  means ALL selected 
  -1^  nothing was selected, timeout expired or uparrow entered 
  
 where: 
  IEN is record number in file #36.  
COMPONENT/ENTRY POINT: $$INSNM(IBINSIEN)
 COMPONENT DESCRIPTION:   INSURANCE COMPANY NAME lookup API.  
VARIABLES: IBINSIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN of entry in INSURANCE COMPANY file #36.  
VARIABLES: $$INSNM                      TYPE: Output
 VARIABLES DESCRIPTION:   returned value: NAME field #.01 of INSURANCE COMPANY
 file #36.  
COMPONENT/ENTRY POINT: $$ACPHONE()
 COMPONENT DESCRIPTION:   AGENT CASHIER PHONE NUMBER lookup API.  
VARIABLES: $$ACPHONE                    TYPE: Output
 VARIABLES DESCRIPTION:   return value: AGENT CASHIER PHONE NUMBER field #2.06
 from the IB SITE PARAMETERS file #350.9 
COMPONENT/ENTRY POINT: $$INSPL(IBPL)
 COMPONENT DESCRIPTION:   INSURANCE COMPANY lookup API from GROUP INSURANCE
 PLAN file #355.3.  
VARIABLES: IBPL                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of entry in the GROUP INSURANCE PLAN file #355.3. 
 
VARIABLES: $$INSPL                      TYPE: Output
 VARIABLES DESCRIPTION:   returned value: INSURANCE COMPANY field #.01 of the
 GROUP INSURANCE PLAN file #355.3.  
COMPONENT/ENTRY POINT: $$MXTRNS(IBPLID)
 COMPONENT DESCRIPTION:   MAXIMUM NCPDP TRANSACTIONS lookup API.  
VARIABLES: IBPLID                       TYPE: Input
 VARIABLES DESCRIPTION:   ID field #.01 from the PLAN file.  
VARIABLES: $$MXTRNS                     TYPE: Output
 VARIABLES DESCRIPTION:   returned value: Numeric value from MAXIMUM NCPDP
 TRANSACTIONS field #10.1 of the PLAN file #366.03.  Default is 1 if undefined. 
 
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 4722                            IA #: 4722
  DATE CREATED: AUG 19, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOAPI2
  NAME: HLO APPLICATION ACKNOWLEDGEMENT APIS
  ID: HLOAPI2
 GENERAL DESCRIPTION:   These APIs are used by applications to return
 application acknowledgments to messages received via HLO.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$ACK(.HLMSTATE,.PARMS,.ACK,.ERROR)
 COMPONENT DESCRIPTION:   This API initiates (but doesn't complete) an
 application acknowledgment. This API should NOT be called for batch messages,
 use $$BATCHACK^HLOAPI3 instead.  
VARIABLES: $$ACK                        TYPE: Output
 VARIABLES DESCRIPTION:   Function call returns 1 on success, 0 on failure.  
VARIABLES: HLMSTATE                     TYPE: Both
 VARIABLES DESCRIPTION:   Obtained by calling $$STARTMSG^HLOPRS when parsing
 the original message. It is used internally by HLO.  
VARIABLES: PARMS                        TYPE: Input
 VARIABLES DESCRIPTION:   Optional. These subscripts may be defined: 
  
 ("ACK CODE") - MSA1 contains AA, AE, or AR.  ("ERROR MESSAGE") - MSA3, should
 be used only if AE or AR.  ("ACCEPT ACK RESPONSE") - Optional. The
 <tag^routine> to call in response to a commit ack.    ("ACCEPT ACK TYPE") -
 {AL,NE} (Optional, defaults to AL).  ("CONTINUATION POINTER") -Indicates a
 fragmented messages.  ("COUNTRY") - The three-character country code
 (optional).  ("EVENT") - The three-character event type (optional, defaults to
 the event code of the original message).  ("ENCODING CHARACTERS") - The four
 HL7 encoding characters (optional, defaults to "^~\&".  ("FAILURE RESPONSE") -
 Optional. The <tag>^<routine> that the sending application routine should
 execute if the transmission of the message fails, i.e., the message can not be
 sent or a requested commit ack is not received.  ("FIELD SEPARATOR") - Field
 separator (optional, defaults to "|").  ("MESSAGE TYPE") - If not defined, ACK
 is used.  ("MESSAGE STRUCTURE CODE") - Optional.  ("QUEUE")- Optional. An
 application can name its own private queue (a string under 20 characters, it
 should be namespaced). The default is the name of the queue of the original
 message ("SECURITY") - Optional. Security information to include in the header
 segment, SEQ 8. ("VERSION") - The HL7 Version ID (optional, defaults to 2.4).  
  
VARIABLES: ACK                          TYPE: Output
 VARIABLES DESCRIPTION:   The acknowledgement message being built.  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   On failure, an error message is returned.  
COMPONENT/ENTRY POINT: $$SENDACK(.ACK,.ERROR)
 COMPONENT DESCRIPTION:   Sends the acknowledgment message that was begun by a
 call to $$ACK^HLAPI2 or a batch of acknowledgement messages that was begun by
 a call to $$$$BATCHACK^HLOAPI3.  
VARIABLES: $$SENDACK                    TYPE: Output
 VARIABLES DESCRIPTION:   Function call returns 1 on success, 0 on failure.  
VARIABLES: ACK                          TYPE: Input
 VARIABLES DESCRIPTION:   An array that contains the acknowledgment message
 that was built by calling the other APIs.  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   If the function fails, an error message is returned.  

NUMBER: 4723                            IA #: 4723
  DATE CREATED: AUG 19, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOAPI3
  NAME: HLO APPLICATION ACKNOWLEDGEMENT APIS (CONTINUED)
  ID: HLOAPI3
 GENERAL DESCRIPTION:   These APIs are part of the set of tools that an
 application uses to return an application acknowledgement to a message that
 was received via HLO. See integration agreement # 4722 for the related APIs.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$BATCHACK(.HLMSTATE,PARMS,.ACK,.ERROR)
 COMPONENT DESCRIPTION:   This routine is used to  initiate a batch message
 containing inidividual application acknowledgments to a batch of messages that
 was received via HLO.  Individual acks are placed in this batch by calling
 $$ADDACK^HLOAPI3, then the batch of acks is actually sent by calling
 $$SENDACK^HLOAPI2.  
VARIABLES: $$BATCHACK                   TYPE: Output
 VARIABLES DESCRIPTION:   The function returns 1 on success, 0 on failure.  
VARIABLES: HLMSTATE                     TYPE: Both
 VARIABLES DESCRIPTION:   The HLMSTATE array is used internally by HLO to track
 the processing of the message.  It is created by the application's earlier
 call to $$STARTMSG^HLOPRS when parsing the original message.  
  
VARIABLES: PARMS                        TYPE: Input
 VARIABLES DESCRIPTION:   These subscripts may be defined: 
  
 ("ACCEPT ACK RESPONSE") - <tag^routine> to call in response to a commit ack
 (optional).  ("ACCEPT ACK TYPE")  - <AL,NE> (Optional, defaults to AL).  
 ("COUNTRY")  - A three-character country code from the HL7 standard table
 (optional).  ("ENCODING CHARACTERS") - The four HL7 encoding characters;
 optional, defaults to "^~\&".  ("FAILURE RESPONSE") - Optional. The
 <tag>^<routine> that the sending application routine should execute if the
 transmission of the message fails, i.e., the message can not be sent or a
 requested commit ack is not received.  ("FIELD SEPARATOR") - Field separator;
 optional, defaults to "|".  ("QUEUE") - Optional. An application can name a
 private queue (a string under 20 characters, it should be namespaced). The
 default is the name of the queue of the original message.  ("SECURITY") -
 Security information to include in the header segment, SEQ 8 (optional).  
 ("VERSION") - The HL7 Version ID (optional, defaults to 2.4) 
  
VARIABLES: ACK                          TYPE: Output
 VARIABLES DESCRIPTION:   The acknowledgement being built.  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   On failure, the function returns an error message.  
COMPONENT/ENTRY POINT: $$ADDACK(.ACK,.PARMS,.ERROR)
 COMPONENT DESCRIPTION:   This API adds an application acknowledgement to a
 batch acknowledgement message that was started by calling $$BATCHACK^HLOAPI3.  
VARIABLES: $$ADDACK                     TYPE: Output
 VARIABLES DESCRIPTION:   The function returns 1 on success, 0 on failure.  
VARIABLES: ACK                          TYPE: Both
 VARIABLES DESCRIPTION:   The batch of acknowledgements that is being built.  
VARIABLES: PARMS                        TYPE: Input
 VARIABLES DESCRIPTION:   These subscripts may be defined: 
  
 ("ACK CODE" ) - Required. MSA1 contains AA, AE, or AR.  ("ERROR MESSAGE" ) -
 Optional.  MSA3 should be used only if AE or AR.  ("EVENT")  - A
 three-character event type (optional, defaults to the event code of the
 original message).  ("MESSAGE CONTROL ID") - Required. The message control ID
 of the original individual message within the batch that is being
 acknowledged.  ("MESSAGE STRUCTURE CODE") - Optional.  ("MESSAGE TYPE") -
 Optional, defaults to ACK.  ("SECURITY") - Optional. Security information to
 include in the header segment SEQ.  
  
VARIABLES:  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   On failure, the function also returns an error
 message.  

NUMBER: 4724                            IA #: 4724
  DATE CREATED: AUG 19, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOAPI3
  NAME: HLO MISCELANEOUS APIS           ID: HLOAPI3
 GENERAL DESCRIPTION:   These are APIs provided by HLO that don't fit into any
 of the other categories.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$RESEND(MSGIEN,.ERROR)
 COMPONENT DESCRIPTION:   This routine re-transmits a message.  It does this by
 making a copy of the message, reusing all the original parameters. Then the
 message is placed in the same outgoing queue.  
VARIABLES: $$RESEND                     TYPE: Output
 VARIABLES DESCRIPTION:   The function returns 1 on success, 0 on failure.  
VARIABLES: MSGIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the message that is to be sent from HLO
 MESSAGES file( #778).  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   On failure, the function also returns an error
 message.  
COMPONENT/ENTRY POINT: $$REPROC(MSGIEN,.ERROR)
 COMPONENT DESCRIPTION:   This routine reprocesses a message by placing it on
 the appropriate incoming queue.  
VARIABLES: $$REPROC                     TYPE: Output
 VARIABLES DESCRIPTION:   This function returns 1 on success, 0 on failure.  
VARIABLES: MSGIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the message that is to be sent from HLO
 MESSAGES file( #778).  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   On failure, this function also returns an error
 message.  
COMPONENT/ENTRY POINT: $$SETPURGE(MSGIEN,TIME)
 COMPONENT DESCRIPTION:   This API can be used to reset the scheduled purge
 date/time.  
VARIABLES: $$SETPURGE                   TYPE: Output
 VARIABLES DESCRIPTION:   This function returns 1 on success, 0 on failure.  
VARIABLES: MSGIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the message that is to be reprocessed from 
 HLO MESSAGES file (#778).  
VARIABLES: TIME                         TYPE: Input
 VARIABLES DESCRIPTION:   Optional, date/time to which to set the purge time.
 If not defined, defaults to NOW.  

NUMBER: 4725                            IA #: 4725
  DATE CREATED: AUG 19, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOASUB
  NAME: HLO SUBSCRIPTION REGISTRY APIS  ID: HLOASUB
 GENERAL DESCRIPTION:   These APIs allow applications to create and manage
 entries in the HLO Subscription Registry.  Each entry is basically a list of
 recipients that can be used and reused to address HL7 messages.  Its similar
 to a mailing list. See also IA# 4726.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$CREATE(OWNER,DESCRIPTION,.ERROR)
 COMPONENT DESCRIPTION:   This API is used to create a new entry in the HLO
 Subscription Registry.  
VARIABLES: $$CREATE                     TYPE: Output
 VARIABLES DESCRIPTION:   Function call returns the new IEN in the HLO
 SUBSCRIPTION REGISTRY file (#779.4)  if successful, 0 if error.  
VARIABLES: OWNER                        TYPE: Input
 VARIABLES DESCRIPTION:   The name of the owning application. It should be
 pre-fixed with the owning application's namespace.  
VARIABLES: DESCRIPTION                  TYPE: Input
 VARIABLES DESCRIPTION:   Optional.  A short description of the subscription
 registry entry.  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   The function also returns an error message if it
 fails.  
COMPONENT/ENTRY POINT: $$ADD(IEN,.WHO,.ERROR) 
 COMPONENT DESCRIPTION:   Add a new recipient to an existing subscription list. 
 
VARIABLES: $$ADD                        TYPE: Output
 VARIABLES DESCRIPTION:   The function returns the subien of the recipient from
 the RECIPIENTS multiple, 0 on failure.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the entry in the HLO SUBSCRIPTION REGISTRY
 file (#779.4).  
VARIABLES: WHO                          TYPE: Input
 VARIABLES DESCRIPTION:   An array containing the information for a single new
 recipient to be added to the list. These subscripts are allowed: 
  
 ("RECEIVING APPLICATION") - String, 60 char max, required.  
  
 One of the following four parameters must be provided to identify the 
 Receiving Facility: 
  
 ("FACILITY LINK IEN") - IEN of the logical link.  ("FACILITY LINK NAME") -
 Name of the logical link.  ("INSTITUTION IEN") - Pointer to the INSTITUTION
 file.  ("STATION NUMBER") - Station # with suffix.  
  
 ONE of the following two parameters MAY be provided - optionally - to identify
 the interface engine to route the message through: 
  
 ("IE LINK IEN") -  Pointer to a logical link for the interface engine.  ("IE
 LINK NAME") - Name of the logical link for the interface engine.  
  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   On failure, one of these messages will be returned: 
  
 "SUBSCRIPITON REGISTRY ENTRY NOT FOUND" "RECEIVING FACILTY LOGICAL LINK NOT
 FOUND" "RECEIVING APPLICATION NOT FOUND" "INTERFACE ENGINE LOGICAL LINK
 PROVIDED BUT NOT FOUND" "FAILED TO ACTIVATE SUBSCRIBER" 
COMPONENT/ENTRY POINT: $$END(IEN,.WHO)
 COMPONENT DESCRIPTION:   to terminate a recipient from the subscriber list. 
 The recipient isn't deleted, but the DATE/TIME TERMINATED field is entered
 with the current date/time.  
VARIABLES: $$END                        TYPE: Output
 VARIABLES DESCRIPTION:   The function returns 1 on success, 0 on failure.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the HLO SUBSCRIPTION REGISTRY file
 (#779.4) entry.  
VARIABLES: WHO                          TYPE: Input
 VARIABLES DESCRIPTION:   If WHO("SUBIEN") is defined, then it should be the
 IEN of the sub-record to be terminated.  Otherwise, set the set the parameter
 as per $$ADD^HLOASUB 
COMPONENT/ENTRY POINT: $$ONLIST(IEN,LINKIEN,APPNAME,FAC1,FAC2,FAC3)
 COMPONENT DESCRIPTION:   This function is used to check whether or not a
 potential recipient is already on a particular subscription list.  
VARIABLES: $$ONLIST                     TYPE: Output
 VARIABLES DESCRIPTION:   Function call returns the IEN of the recipient from
 the RECIPIENTS multiple, 0 on failure.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the HLO SUBSCRIPTION REGISTRY file
 (#779.4) entry.  
VARIABLES: LINKIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the logical link.  
VARIABLES: APPNAME                      TYPE: Input
 VARIABLES DESCRIPTION:   The name of the receiving application.  
VARIABLES: FAC1                         TYPE: Input
 VARIABLES DESCRIPTION:   Component 1 of the receiving facility.  
VARIABLES: FAC2                         TYPE: Input
 VARIABLES DESCRIPTION:   Component 2 of the Receiving Facility.  
VARIABLES: FAC3                         TYPE: Input
 VARIABLES DESCRIPTION:   Component 3 of the Receiving Facility.  
COMPONENT/ENTRY POINT: $$NEXT(IEN,.RECIP) 
 COMPONENT DESCRIPTION:   This API is used to loop through a subscription list. 
 It ignores recipients that have been terminated from the list.  
VARIABLES: $$NEXT                       TYPE: Output
 VARIABLES DESCRIPTION:   Function call returns the IEN of the recipient from
 the RECIPIENTS multiple, 0 on failure. 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the HLO SUBSCRIPTION REGISTRY file
 (#779.4) entry.  
VARIABLES: RECIP                        TYPE: Both
 VARIABLES DESCRIPTION:   Input: If NULL, it gets the first recipient on the
 list, else it uses the value of RECIP("SUBIEN") to find the next recipient.  
  
 Output: RECIP - Required. Returns the next recipient on the list. These
 subscripts are returned: 
  
 ("LINK IEN") ("LINK NAME") ("RECEIVING APPLICATION") ("RECEIVING FACILITY",1) 
 - Component 1 ("RECEIVING FACILITY",2)  - Component 2 ("RECEIVING FACILITY",3) 
 - Component 3 ("SUBIEN") - The IEN in the multiple, used to find the next on
 the list.  
  

NUMBER: 4726                            IA #: 4726
  DATE CREATED: AUG 19, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOASUB1
  NAME: HLO SUBSCRIPTION REGISTRY APIS (CONTINUED)
  ID: HLOASUB1
 GENERAL DESCRIPTION:   This continues the APIs for HLO subscription lists. 
 See IA# 4725.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$INDEX(IEN,.PARMARY)
 COMPONENT DESCRIPTION:   This function call allows an application to build an
 index of its subscriptions.  This is optional, but using this function allows
 the application to easily find subscriptions without storing the IEN.  
VARIABLES: $$INDEX                      TYPE: Output
 VARIABLES DESCRIPTION:   The function returns 1 on success, 0 on failure.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the HLO SUBSCRIPTION REGISTRY file (#779.4)
 entry. 
VARIABLES: PARMARY                      TYPE: Input
 VARIABLES DESCRIPTION:   Array of parameters with which to build the index. 
 The format is: PARMARY(1)=<first parameter>, PARMARY(2)=<second parameter>  If 
 PARMARY(i)=null, the parameter will be translated to a single space.  
COMPONENT/ENTRY POINT: $$FIND(OWNER,.PARMARY)
 COMPONENT DESCRIPTION:   This function call allows an application to find a
 subscription registry entry.  The application must maintain a private index in
 order to utilize this function, via $$INDEX^HLOASUB1.  
VARIABLES: $$FIND                       TYPE: Output
 VARIABLES DESCRIPTION:   This function returns the IEN of the subscription
 list if found, 0 otherwise.  
VARIABLES: OWNER                        TYPE: Input
 VARIABLES DESCRIPTION:   The name of the owning application, as specified when
 the subscription list was created.  
VARIABLES: PARMARY                      TYPE: Input
 VARIABLES DESCRIPTION:   The array of parameters with which the  index was
 built.  The format is: PARMARY(1)=<first parameter>, PARMARY(2)=<second
 parameter>  If PARMARY(i)=null, the parameter will be translated to a single
 space.  

NUMBER: 4727                            IA #: 4727
  DATE CREATED: AUG 19, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOCNRT
  NAME: HLO CONVERSION APIS             ID: HLOCNRT
 GENERAL DESCRIPTION:   These utilities provide help to applications that were
 developed before HLO convert to HLO. See also IA# 4728 and IA#4731.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$EN(HLOPRTCL,ARYTYP,.HLP)
 COMPONENT DESCRIPTION:   Takes a current HL 1.6 message that follows the
 standard HL 1.6 methodology, converts it to use the HLO engine, and places the
 message into the HLO message queue. A function call to EN^HLOCNRT replaces the
 HL 1.6 call to GENERATE^HLMA.  
VARIABLES: $$EN                         TYPE: Output
 VARIABLES DESCRIPTION:   The function returns a string that is one to three
 piece variable consisting of message id^error code^error description. Only the
 message id will be returned if there is no error.  
VARIABLES: HLOPRTCL                     TYPE: Input
 VARIABLES DESCRIPTION:   Event Protocol IEN 
VARIABLES: ARYTYP                       TYPE: Input
 VARIABLES DESCRIPTION:   Array Type ("GM" is the standard usage, used for a
 global array containing a single message.  
VARIABLES: HLP                          TYPE: Input
 VARIABLES DESCRIPTION:   Additional MSH parameters. For example: -     
 HLP("SECURITY") -      HLP( "CONTPTR") -      HLP("QUEUE") 
  

NUMBER: 4728                            IA #: 4728
  DATE CREATED: AUG 19, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOCVU
  NAME: HLO CONVERSION APIS (2)         ID: HLOCVU
 GENERAL DESCRIPTION:   These utilities provide help to applications that were
 developed before HLO convert to HLO. See also IA# 4727 and IA#4731.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: APAR(HLOEID,.APPARMS,.WHO,.WHOTO)
 COMPONENT DESCRIPTION:   Designed to retrieve pre-HLO HL 1.6 parameters from
 the existing HL 1.6 protocol and translate to HLO format. 
VARIABLES: HLOEID                       TYPE: Input
 VARIABLES DESCRIPTION:   Event Protocol IEN.  
VARIABLES: APPARMS                      TYPE: Output
 VARIABLES DESCRIPTION:   Array containing HLO message parameters.  
  
  
 Specific translation from HL 1.6 parameters to HLO is as follows:      
  
 HL 1.6 APPLICATION PROTOCOL            =>      HLO APPARMS ARRAY PARAMETERS 
 COUNTRY CODE                           =>      APPARMS("COUNTRY") APPLICATION
 ACK TYPE                   =>      APPARMS("APP ACK TYPE") EVENT TYPE          
                   =>      APPARMS("EVENT") SENDING APPLICATION                 
   =>      APPARMS("SENDING APPLICATION") TRANSACTION MESSAGE TYPE              
 =>      APPARMS("MESSAGE TYPE") VERSION ID                             =>     
 APPARMS("VERSION") HL7 FIELD SEPARATOR                    =>     
 APPARMS("FIELD SEPARATOR")      HL7 ENCODING CHARACTERS                       
 =>      APPARMS("ENCODING CHARACTERS")  
  
 HL 1.6 Passed Parameters               =>      HLO APPARMS ARRAY PARAMETERS 
 HLP("SECURITY")                                =>      APPARMS("SECURITY") 
 HLP("CONTPTR")                         =>      APPARMS("CONTINUATION POINTER") 
 HLP("QUEUE")*                          =>      APPARMS("QUEUE") 
  
 *NOTE: HLP("QUEUE") is not actually a current HL 1.6 parameter but can be 
 added to the HLP array to allow a converted application to define HLO private
 queues.  
  
 For Sending Messages To One Application                                     
                                                         _
 RECEIVING APPLICATION                  =>      WHO("RECEIVING APPLICATION")    
      LOGICAL LINK                           =>      WHO("FACILITY LINK NAME") 
  
 For Sending Messages To Multiple Applications (where "n" is a numeric index 
 (0,1,2, ))              _ RECEIVING APPLICATION                  =>     
 WHOTO(n,"RECEIVING APPLICATION")  LOGICAL LINK                           =>    
  WHOTO(n,"FACILITY LINK NAME") 
  
VARIABLES: WHO                          TYPE: Output
 VARIABLES DESCRIPTION:   For single HLO message recipients, receiving
 application parameters.  
VARIABLES: WHOTO                        TYPE: Output
 VARIABLES DESCRIPTION:   For multiple HLO message recipients, receiving
 application parameters.  

NUMBER: 4729                            IA #: 4729
  DATE CREATED: JUL 11, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPDPI
  NAME: API FOR RX BILLING INFO         ID: IBNCPDPI
 GENERAL DESCRIPTION:   The API returns billing information for specified
 prescription/refill.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
COMPONENT/ENTRY POINT: $$BILLINFO(IBRX,IBREF,IBPSEQ)
 COMPONENT DESCRIPTION:   Return Bill# and Account Receivable information about
 the bill. If IBPSEQ=1, then return the bill# from the Claims Tracking file. If 
 IBPSEQ=2, then return the active bill, if there is no active bill then return
 the latest bill with any status. If IBPSEQ is passed in as null, then 1 is
 assumed.  
VARIABLES: IBRX                         TYPE: Input
 VARIABLES DESCRIPTION:   Prescription's IEN in file #52 
VARIABLES: IBREF                        TYPE: Input
 VARIABLES DESCRIPTION:   Re-fill number.  
VARIABLES: $$BILLINFO                   TYPE: Output
 VARIABLES DESCRIPTION:   Returns a string of information about the bill
 requested: 
  piece #1:  Bill number 
  piece #2:  Original Amount of bill 
  piece #3:  Current Status 
  piece #4:  Current Balance 
  piece #5:  Total Collected 
  piece #6:  % Collected Returns null if no data or bill found.  
  piece #7:  PFSS switch status: 0-OFF, 1-ON 
  
 The PFSS sites do not provide this information and thus the API will return
 "^^^^^^1".  
VARIABLES: IBPSEQ                       TYPE: Input
 VARIABLES DESCRIPTION:   Payer sequence (optional parameter).  1-primary,
 2-secondary. If null then 1 (primary) is assumed.  
COMPONENT/ENTRY POINT: $$RNB(IBRX,IBFL)
 COMPONENT DESCRIPTION:   Returns the Claims Tracking Reason Not Billable
 information for a given prescription and fill. If the Claims Tracking entry is
 billable or if the Claims Tracking entry doesn't exist for the
 prescription/fill, then this function returns 0.  
VARIABLES: IBRX                         TYPE: Input
 VARIABLES DESCRIPTION:   Prescription ien (file# 52) 
VARIABLES: IBFL                         TYPE: Input
 VARIABLES DESCRIPTION:   Prescription fill/refill number. 0 for original fill. 
 
VARIABLES: $$RNB                        TYPE: Output
 VARIABLES DESCRIPTION:   The function value is 0 if no Claims Tracking entry
 is found or if the CT entry is billable. If the CT entry is non-billable, then
 the following pieced string will be returned about the Reason Not Billable
 (RNB). [1]- RNB ien (pointer to file# 356.8). [2]-RNB description [3]-RNB ECME
 flag [4]-RNB ECME paper flag [5]-RNB code [6]-RNB active/inactive flag. These 
 pieces are taken from the data fields in file# 356.8.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: AUG 25, 2010

NUMBER: 4730                            IA #: 4730
  DATE CREATED: AUG 19, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOQUE
  NAME: HLO QUEUE MANAGEMENT APIS       ID: HLOQUE
 GENERAL DESCRIPTION:   These APIs are for applications to use in KIDS
 distributions of messaging applications.  They allow the application to turn
 on and off individual queues during the instalation of a patch. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: STOPQUE(DIR,QUEUE)
 COMPONENT DESCRIPTION:   Routine designed to set a "Stop" flag on a named
 queue. Flag to set is ^HLTMP("STOPPED QUEUES",DIR,QUEUE).  
  
VARIABLES: DIR                          TYPE: Input
 VARIABLES DESCRIPTION:   Direction of queue. Values are "IN" or "OUT".  
VARIABLES: QUEUE                        TYPE: Input
 VARIABLES DESCRIPTION:   The name of the queue to be stopped.  
COMPONENT/ENTRY POINT: STARTQUE(DIR,QUEUE)
 COMPONENT DESCRIPTION:   Routine designed to remove a "Stop" flag on a named
 queue. Flag to remove is ^HLTMP("STOPPED QUEUES",DIR,QUEUE).  
VARIABLES: DIR                          TYPE: Input
 VARIABLES DESCRIPTION:   Direction of queue. Values are "IN" or "OUT".  
VARIABLES: QUEUE                        TYPE: Input
 VARIABLES DESCRIPTION:   The name of the queue to be started.  
COMPONENT/ENTRY POINT: $$STOPPED(DIR,QUEUE)
 COMPONENT DESCRIPTION:   Function designed to check the status of a queue by
 determining if a "Stop" flag has been set on a named queue. Flag to check is
 ^HLTMP("STOPPED QUEUES",DIR,QUEUE).  
VARIABLES: DIR                          TYPE: Input
 VARIABLES DESCRIPTION:   Direction of queue. Values are "IN" or "OUT".  
VARIABLES: QUEUE                        TYPE: Input
 VARIABLES DESCRIPTION:   The name of the queue to be checked.  
VARIABLES: $$STOPPED                    TYPE: Output
 VARIABLES DESCRIPTION:   The function returns 1 if the named queue is stopped,
 0 otherwise.  

NUMBER: 4731                            IA #: 4731
  DATE CREATED: AUG 19, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOMSG
  NAME: HLO CONVERSOIN APIS (3)         ID: HLOMSG
 GENERAL DESCRIPTION:   These utilities provide help to applications that were
 developed before HLO convert to HLO. See also IA# 4727 and IA#4728.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$HLNEXT(.HLMSTATE,.SEG)
 COMPONENT DESCRIPTION:   This API is NOT to be used in the development of a
 new messaging application.  It is provided for messaging applications that
 were developed prior to HLO where stepping through a message was accomplished
 by executing HLNEXT.  
  
 The new function $$HLNEXT is used to step through the segments of a message 
 stored in the new HLO data structures.  However, for batch messages, it does
 not tranverse from one message to the next as executing HLNEXT does.  
VARIABLES: HLMSTATE                     TYPE: Both
 VARIABLES DESCRIPTION:   This array is used by the HL7 package to track the
 current position in the message.  The application MUST NOT touch it.  
VARIABLES: SEG                          TYPE: Output
 VARIABLES DESCRIPTION:   The segment is returned in this array.  
VARIABLES: $$HLNEXT                     TYPE: Output
 VARIABLES DESCRIPTION:   The function returns 1 on success, 0 if there are no
 more segments in this message.  For batch messages, a return value of 0 does
 not preclude the possibility that there are additional individual messages
 within the batch.  

NUMBER: 4732                            IA #: 4732
  DATE CREATED: JUL 15, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOPFSU0
  NAME: DBIA4732                        ID: PSOPFSU0
 GENERAL DESCRIPTION:   This agreement provides the Integration Billing (IB)
 package the following IENs for a given Prescription and Refill number that was
 released: 
  
   1. Pharmacist who released the prescription.  
  
   2. Initiator of Activity - last entry in the activity log with an INITIATOR
 OF ACTIVITY field (#.03) value defined.  If none are found, default to the
 releasing pharmacist. Null values are not to be passed.  
  
   3. IB Service Section of the dispensing division from the OUTPATIENT SITE
 file (#59).  
  
 The format is Pharmacist IEN^Last Activity Initiator IEN^IB Service Section
 IEN.  
  
 If this API is called for unreleased prescriptions, null values will be 
 returned for all fields.  
  STATUS: Active
KEYWORDS: PFSS
COMPONENT/ENTRY POINT: $$RPH(PSORXN,PSOREF)
VARIABLES: PSORXN                       TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN (Required) 
VARIABLES: PSOREF                       TYPE: Input
 VARIABLES DESCRIPTION:   Refill Number (Required) 
VARIABLES: $$RPH                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns Pharmacist IEN^Last Activity Initiator IEN^IB
 Service Section IEN. If the input variables are invalid it returns "^^".  
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4733                            IA #: 4733
  DATE CREATED: JUL 19, 2005
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUPXAPI
  NAME: Calls to TIUPXAPI               ID: TIUPXAPI
 GENERAL DESCRIPTION:   This agreement documents calls from Care Management to
 TIUPXAPI.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$DFLTDOC(HLOC)
 COMPONENT DESCRIPTION:   This entry point is used to determine the default
 provider for a clinic location as determined by PCE.  
VARIABLES: HLOC                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the HOSPITAL LOCATION (#44) file 
VARIABLES: $$DFLTDOC                    TYPE: Output
 VARIABLES DESCRIPTION:   The return value is in the form: 
  
         provider_NEW PERSON_ien^provider_NEW PERSON_name 
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 9/26/25, effective with patch OR*3.0*508.  CPRS
 needs to find the default provider 

NUMBER: 4734                            IA #: 4734
  DATE CREATED: JUL 18, 2005
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORPRF HASFLG
  REMOTE PROCEDURE: ORPRF HASFLG
 GENERAL DESCRIPTION:   This agreement documents use of the ORPRF HASFLG remote
 procedure call.  
  
 TAG^ROUTINE: HASFLG^ORPRF 
  
 This RPC returns an array of Patient Record Flags on file for the patient in
 the format: 
  
 ARR=number of flags ARR(1)=flag number^text of flag narrative ARR(2)=flag
 number^text of flag narrative etc.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 4735                            IA #: 4735
  DATE CREATED: JUL 18, 2005
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORPRF GETFLG
 GENERAL DESCRIPTION:   This agreement documents calls to the ORPRF GETFLG
 remote procedure call.  
  
 TAG^ROUTINE:  GETFLG^ORPRF 
  
 This RPC is used to return the detailed text of a patient record flag in an
 array.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CARE MANAGEMENT

NUMBER: 4736                            IA #: 4736
  DATE CREATED: JUL 20, 2005            CUSTODIAL PACKAGE: LIST MANAGER
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VALM0
  NAME: TERM SETUP                      ID: VALM0
 GENERAL DESCRIPTION:   HIPAA Electronic Claims requests an integration
 agreement with List Manger to call TERM^VALM0.  Call will set up variables
 needed by the Claims Data Entry Screen.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: TERM
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 4737                            IA #: 4737
  DATE CREATED: JUL 20, 2005            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFPFSPD
  NAME: PFSS PID SEGEMENT BUILDER       ID: VAFPFSPD
 GENERAL DESCRIPTION:   The PFSS 1B Prototype project requires HL7 messages to
 be sent from VistA to a commercial Billing System.  The HL7 messages contain a
 PID segment.  Some elements are needed in that segment that are not supported
 by existing PID segment builders.  The EN^VAFPFSPD API builds a PID segment 
 for PFSS use.  To the extent possible, EN^VAFPFSPD uses existing, supported
 PID utilities to build the customized segment.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PFSS
KEYWORDS: PID
COMPONENT/ENTRY POINT: EN(DFN,PID,ERR)
 COMPONENT DESCRIPTION:   EN^VAFPFSPD builds a PID segment based on the DFN
 passed in the first parameter. Contents are based on the requirements of PFSS
 messages and an error message is returned if the segment cannot be built
 successfully.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Patient File entry for which the PID
 segment is built.  
VARIABLES: PID                          TYPE: Output
 VARIABLES DESCRIPTION:   Array, passed by reference, that contains the built
 PID segment if no errors are encountered.  
VARIABLES: ERR                          TYPE: Output
 VARIABLES DESCRIPTION:   Passed by reference.  ERR contains a string
 describing an error if one occurs during the building of the PID segment.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   DBIA to be used to build PID segment for PFSS messages. 
 
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM

NUMBER: 4738                            IA #: 4738
  FILE NUMBER: 773                      GLOBAL ROOT: HLMA(
  DATE CREATED: JUL 20, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: OBTAINING FILE 772 POINTER VALUEFROM FILE 773
  ID: HLMA(
GLOBAL REFERENCE: HLMA('C',
 GLOBAL DESCRIPTION:   "C" cross-reference on File 773 allows lookup of file
 773 IEN using the Message Id.  
GLOBAL REFERENCE: HLMA(
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME ENTERED
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The .01 field of File 773 is a pointer to File 772. 
 Direct Access to this value returns the IEN of File 772 entry associated with
 the Message Id.  
 GENERAL DESCRIPTION:   The PFSS project needs to store the pointer to the File
 #772 (HL7 Message Text) record that contains the body of the HL7 message
 triggered by an entry in File #375 (PFSS Account).  This pointer will be used
 for troubleshooting and ad hoc auditing.  
  
 In order to obtain the pointer value from the Message Id returned by the HL7
 GENERATE^HLMA() API, a lookup is done on the "C" cross-reference of File #773. 
 The "C" cross-reference is built on Field #2, the Message Id.  Using the IEN
 obtained, the .01 value of the File #773 entry is retrieved.  That value is
 the desired pointer to the File #772 entry containing the Message Text.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 772
KEYWORDS: MESSAGE ID
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   As part of the PADE project, Inpatient Medications
 patch PSJ*5*317, will store the HL7 MESSAGE ADMINISTRATION file (#773), .01
 field in our log file for troubleshooting purposes. 

NUMBER: 4739                            IA #: 4739
  FILE NUMBER: 772                      GLOBAL ROOT: HL(772
  DATE CREATED: JUL 21, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: POINTING TO FILE 772
  ID: HL(772
GLOBAL REFERENCE: HL(772,
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME ENTERED
  LOCATION: 0;1                         ACCESS: Pointed to
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PFSS
KEYWORDS: HL7 MESSAGE TEXT
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4740                            IA #: 4740
  DATE CREATED: NOV 04, 2005
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Routine
  ROUTINE: RAO7PC5
  NAME: My HealtheVet Radiology View extract
  ID: RAO7PC5
 GENERAL DESCRIPTION:   The 'My HealtheVet' team in preparation for the My
 HealtheVet V. 1.0 package requested an additional Radiology/Nuclear Medicine
 V5.0 Application Program Interface to provide details of patient records 
 provided that the patient exam is currently associated with a verified report
 or had ever been associated with an verified report (report subsequently was
 backed out of the verified status): 
  
 Format: field #, field name, piece_datatype;file (if pointer) Internal code:
 no=external FileMan format, yes=internal FileMan format 
  
 EXAMINATIONS SUB-FILE #70.03 field  field name                   
 node;piece_datatype;file  internal 
 -----------------------------------------------------------------------
 2      PROCEDURE                     0;2P;71                    no 
  
  
 RAD/NUC MED REPORTS #74 field  field name                   
 node;piece_datatype;file   internal 
 ------------------------------------------------------------------------
 .01    DAY-CASE#                     0;1F                       yes 2     
 PATIENT NAME                  0;2P;2                     yes 3      EXAM
 DATE/TIME                0;3D                       yes 4      CASE NUMBER     
              0;4N                       yes 5      REPORT STATUS               
  0;5S                       no 6      DATE REPORT ENTERED           0;6N       
                yes 7      VERIFIED DATE                 0;7D                   
    yes 8      REPORTED DATE                 0;8D                       yes 9   
   VERIFYING PHYSICIAN           0;9P;200                   yes 14    
 PRE-VERIFICATION DATE/TIME    0;12D                      yes 15    
 PRE-VERIFICATION USER         0;13P;200                  yes 17     STATUS
 CHANGED TO VERIFIED BY 0;17P;200                  yes 
  
  
 ERROR REPORTS SUB-FILE #74.06 field  field name                   
 node;piece_datatype;file   internal 
 ------------------------------------------------------------------------
 .01    DATE/TIME OF RPT SAVE         0;1D                       yes 
  
  
 ADDITIONAL CLINICAL HISTORY SUB-FILE #74.04 field  field name                  
  node;piece_datatype;file   internal 
 ------------------------------------------------------------------------
 .01    ADDITIONAL CLINICAL HISTORY   0;1W                       yes 
  
  
 IMPRESSION TEXT SUB-FILE #74.03 field  field name                   
 node;piece_datatype;file   internal 
 ------------------------------------------------------------------------
 .01    IMPRESSION TEXT               0;1W                       yes 
  
  
 REPORT TEXT SUB-FILE #74.02 field  field name                   
 node;piece_datatype;file   internal 
 ------------------------------------------------------------------------
 .01    REPORT TEXT                   0;1W                       yes 
  
  
 RAD/NUC MED ORDERS FILE #75.1 field  field name                   
 node;piece_datatype;file   internal 
 ------------------------------------------------------------------------
 1.1    REASON FOR STUDY              .1;1F                      yes 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: MHV
KEYWORDS: My HealtheVet
KEYWORDS: Radiology View
COMPONENT/ENTRY POINT: MHVRV
 COMPONENT DESCRIPTION:   ** Please note that REASON FOR STUDY data will not be
 captured until the release of RA*5.0*61 ** 
  
 This entry point build the following data into globals where the delimiter is
 the caret (spaces between caret used to enhance readability): 
 ----------------------------------------------------------------
 ^TMP($J,"RA HLTHEVET",DFN,exam d/t,case_IEN)=PROCEDURE ^ DAY-CASE# ^ PATIENT
 NAME ^ EXAM DATE/TIME ^ CASE NUMBER ^ REPORT STATUS (internal format) ~ REPORT
 STATUS (external format) ^ DATE REPORT ENTERED ^ VERIFIED DATE ^ REPORTED DATE
 ^ VERIFYING PHYSICIAN ^ PRE-VERIFICATION DATE/TIME ^ PRE-VERIFICATION USER ^
 STATUS CHANGED TO VERIFIED BY 
  
 ^TMP($J,"RA HLTHEVET",DFN,exam d/t,case_IEN,"rpt saved",line)=DATE/TIME RPT
 SAVED (a report may be verified, un-verified, and re-verified more than once) 
  
 ^TMP($J,"RA HLTHEVET",DFN,exam d/t,case_IEN,"rpt txt",line)=REPORT TEXT (if
 REPORT TEXT exists) 
  
 ^TMP($J,"RA HLTHEVET",DFN,exam d/t,case_IEN,"imp txt",line)=IMPRESSION TEXT
 (if IMPRESSION TEXT exists) 
  
 ^TMP($J,"RA HLTHEVET",DFN,exam d/t,case_IEN,"clin hist",line)=ADDITIONAL 
 CLINICAL HISTORY (if ADDITIONAL CLINICAL HISTORY text exists) 
  
 ^TMP($J,"RA HLTHEVET",DFN,exam d/t,case_IEN,"reason")=REASON FOR STUDY 
  
 Where 'line' is a line counter 
  
 Notes: 
 ------
 The DFN, exam date/time, and case number IEN subscripts ensure uniqueness 
 within a facility.  
  
 Please note that a "many exam to one report" ('printset') relationship may
 exist. To determine whether a printset situation presents itself, please check
 the OTHER CASE# #74.05 sub-file.  
VARIABLES: RADFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The DFN of the patient. This variable cannot be
 passed in as null.  
SUBSCRIBING PACKAGE: MYHEALTHEVET
 SUBSCRIBING DETAILS:   MHV will provide input values for the Radiology/Nuclear
 Medicine function. The input value is: 
 -------------------
 RADFN: must be defined to a patient's DFN 

NUMBER: 4741                            IA #: 4741
  FILE NUMBER: 375                      GLOBAL ROOT: IBBAA(375,
  DATE CREATED: JUL 27, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PFSS ACCOUNT REFERENCE
  ID: IBBAA(375,
GLOBAL REFERENCE: IBBAA(375,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   Allows VistA applications participating in Patient
 Financial Services System (PFSS) to store the PFSS Account Reference within
 their respective file structures.  The PFSS Account Reference is a pointer to
 the PFSS ACCOUNT file (#375).  
  STATUS: Active
KEYWORDS: PFSS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
SUBSCRIBING PACKAGE: PROSTHETICS
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: SURGERY
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4742                            IA #: 4742
  DATE CREATED: AUG 29, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLPRS
  NAME: HL7 MESSAGE PARSING APIs (PRE-HLO)
  ID: HLPRS
 GENERAL DESCRIPTION:   These API's are to be used by applications that were
 developed with the HL7 messaging engine that preceded the newer HL7 Optimized
 messaging engine that was released in patch HL*1.6*126.  
  
 The API's provide support for applications in parsing messages. HL7 escape 
 sequences are decoded. 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$STARTMSG(.HLMSG,IEN,.HEADER)
 COMPONENT DESCRIPTION:   This function begins the parsing of the message,
 parsing the header and returning the individual values in the array HEADER().  
  
VARIABLES: HLMSG                        TYPE: Output
 VARIABLES DESCRIPTION:   (pass by reference, required) This array is used by
 the HL7 package to track the progress of parsing the message.  The application
 MUST NOT touch it! 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   (REQUIRED) 
  
 Internal Entry Number (IEN) of the message in the HL7 MESSAGE ADMINISTRATION 
 file (#773) 
  
VARIABLES: HEADER                       TYPE: Output
 VARIABLES DESCRIPTION:   (pass by reference, optional) 
  
 This array will return the results of parsing the message header. The array 
 subscripts are: 
  
 ** Message Header, MSH Segment ** Sequence       Description/Comment 
  
        HEADER("SEGMENT TYPE )= "MSH    SEQ1   HEADER("FIELD SEPARATOR )      
 The field separator.  SEQ2                                   The four other
 encoding characters.  
        HEADER("COMPONENT SEPARATOR ) 
        HEADER("SUBCOMPONENT SEPARATOR ) 
        HEADER("REPETITION SEPARATOR ) 
        HEADER("ESCAPE CHARACTER )      SEQ3   HEADER("SENDING APPLICATION )   
 SEQ4   HEADER("SENDING FACILITY ,1)    First Component 
        HEADER("SENDING FACILITY ,2)    Second Component 
        HEADER("SENDING FACILITY ,3)    Third Component SEQ5  
 HEADER("RECEIVING APPLICATION ) SEQ6   HEADER("RECEIVING FACILITY ,1)  First
 Component 
        HEADER("RECEIVING FACILITY ,2)  Second Component 
        HEADER("RECEIVING FACILITY ,3)  Third Component SEQ7   HEADER("DT/TM OF
 MESSAGE )      Converted to FileMan format.  SEQ8   HEADER("SECURITY )      
 SEQ9   HEADER ("MESSAGE TYPE )         First Component 
        HEADER("EVENT )                 Second Component 
        HEADER("MESSAGE STRUCTURE )     Third Component SEQ10  HEADER("MESSAGE
 CONTROL ID )    Message control ID.  SEQ11  HEADER("PROCESSING ID )        
 First Component 
        HEADER("PROCESSING MODE )       Second Component SEQ12  HEADER("VERSION
 )       SEQ14  HEADER("CONTINUATION POINTER )  MESSAGE CONTROL ID of the
 message that this one continues.  SEQ15  HEADER("ACCEPT ACK TYPE )      
 ACCEPT ACKNOWLEDGMENT TYPE, <AL or NE> SEQ16  HEADER("APP ACK TYPE )         
 APPLICATION ACKNOWLEDGMENT TYPE, <AL or NE> SEQ17  HEADER("COUNTRY )           
    COUNTRY CODE 
  
  
  ** Message Header, BHS Segment ** Sequence       Description/Comment 
  
        HEADER("SEGMENT TYPE )= "BHS    SEQ1   HEADER("FIELD SEPARATOR )      
 The field separator.  SEQ2                                   The four other
 encoding characters.  
        HEADER("COMPONENT SEPARATOR ) 
        HEADER("SUBCOMPONENT SEPARATOR ) 
        HEADER("REPETITION SEPARATOR ) 
        HEADER("ESCAPE CHARACTER )      SEQ3   HEADER("SENDING APPLICATION )   
 SEQ4                                    Sending Facility 
        HEADER("SENDING FACILITY ,1)    First Component 
        HEADER("SENDING FACILITY ,2)    Second Component 
        HEADER("SENDING FACILITY ,3)    Third Component SEQ5  
 HEADER("RECEIVING APPLICATION ) SEQ6                                   
 Receiving Facility 
        HEADER("RECEIVING FACILITY ,1)  First Component 
        HEADER("RECEIVING FACILITY ,2)  Second Component 
        HEADER("RECEIVING FACILITY ,3)  Third Component SEQ7   HEADER("DT/TM OF
 MESSAGE )      Converted to FileMan Format.  SEQ8   HEADER("SECURITY ) SEQ9  
 HEADER("BATCH NAME/ID/TYPE ) These fields are not defined by the standard
 within the BHS segment, but they are needed and are encoded in SEQ 9 by the
 VistA HL7 package: 
        HEADER("PROCESSING ID ) 
        HEADER("ACCEPT ACK TYPE ) 
        HEADER("APP ACK TYPE ) SEQ10  HEADER("BATCH COMMENT ) The VistA HL7
 package, Version 1.6, Pre-HLO, currently requires that an application
 designate a batch message as being of a particular message type, event type,
 and version, and this information is encoded as components of SEQ10 
        HEADER("MESSAGE TYPE ) 
        HEADER("EVENT ) 
        HEADER("VERSION ) SEQ11  HEADER("BATCH CONTROL ID )      SEQ12 
 HEADER("REFERENCE BATCH CONTROL ID )      
  
VARIABLES: $$STARTMSG                   TYPE: Output
 VARIABLES DESCRIPTION:   Function returns 1 on success, 0 on failure. Failure
 would indicate that the message was not found.  
  
COMPONENT/ENTRY POINT: $$NEXTSEG(.HLMSG,.SEGMENT)
 COMPONENT DESCRIPTION:   This function advances parsing to the next segment.  
  
VARIABLES: $$NEXTSEG                    TYPE: Output
 VARIABLES DESCRIPTION:   Function returns 1 on success, 0 if there are no more
 segments in this message.  For batch messages, a return value of 0 does not
 preclude the possibility that there are additional individual messages within
 the batch.  
  
VARIABLES: HLMSG                        TYPE: Both
 VARIABLES DESCRIPTION:   (pass by reference, required) 
  
 This array is used by the HL7 package to track the current position in the
 message.  The application MUST NOT touch it! 
  
VARIABLES: SEGMENT                      TYPE: Output
 VARIABLES DESCRIPTION:   (pass by reference, required) 
  
 The segment is returned in this array. SEGMENT("SEGMENT TYPE") is returned
 with the 3 letter HL7 segment type that always begins a segment.  
  
 The structure is not further described here because it should not be accessed
 directly by the application developer. Use $$GET to obtain individual segment
 values.  As a shortcut, $$GET^HLOPRS(0) may be used to return the segment
 type.  
  
COMPONENT/ENTRY POINT: $$NEXTMSG(.HLMSG,.MSH)
 COMPONENT DESCRIPTION:   Advances to the next message within the batch, with
 the MSH segment returned.  
  
VARIABLES: $$NEXTMSG                    TYPE: Output
 VARIABLES DESCRIPTION:   Function returns 1 on success, 0 if there are no more
 messages.  
  
VARIABLES: HLMSG                        TYPE: Both
 VARIABLES DESCRIPTION:   (pass by reference, required) 
  
 This array is used by the HL7 package to track the current position in the
 message.  The application MUST NOT touch it! 
  
VARIABLES: MSH                          TYPE: Output
 VARIABLES DESCRIPTION:   (pass by reference, required) 
  
 This array returns the MSH segement of the next message in the batch  in the 
 same format as the $$STARTMSG API. 
  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   The IB package is granted authority to use these new
 APIs for the PFSS project.  
  
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   The DG package is granted authority to use these new
 APIs for the PFSS project.  
  
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
SUBSCRIBING PACKAGE: IFCAP
 SUBSCRIBING DETAILS:   added 6/1/2010 
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   3/2/16-Inpatient Meds added as a subscriber for
 Pharmacy Interface (PIA) Automation project.  

NUMBER: 4743                            IA #: 4743
  DATE CREATED: AUG 01, 2005            CUSTODIAL PACKAGE: PROBLEM LIST
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMPLWP
  NAME: Problem Comment calls in GMPLWP
  ID: GMPLWP
 GENERAL DESCRIPTION:   This documents available calls to enter or return
 Problem Comments.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GET(TEXT,IEN,WIDTH)
 COMPONENT DESCRIPTION:   Returns the text of a problem comment, optionally
 wrapped to a given width; unless otherwise specified, only plain text stripped
 of all XHTML tags will be returned.  
VARIABLES: TEXT                         TYPE: Both
 VARIABLES DESCRIPTION:   Array name (closed root reference) in which to return
 comment content as @TEXT@(n)=line of text 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Problem Comment (#125.5) 
VARIABLES: WIDTH                        TYPE: Input
 VARIABLES DESCRIPTION:   Optional, maximum number of characters to return in
 each line of text; 240 is used if not defined.  May also be set to "X" to
 return the text with all XHTML tags as saved in the global, for use by GUI
 clients.  
COMPONENT/ENTRY POINT: EN(PROBLEM,AUTHOR,COMMENT)
 COMPONENT DESCRIPTION:   Main entry point to save or update a problem comment. 
 
VARIABLES: PROBLEM                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Problem (#9000011) 
VARIABLES: AUTHOR                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of New Person (#200), the user responsible for
 the content of the comment 
VARIABLES: COMMENT                      TYPE: Input
 VARIABLES DESCRIPTION:   Closed array reference to the location of the comment
 text, in standard FileMan word-processing format, to be accessed by
 indirection 
COMPONENT/ENTRY POINT: EDIT(PROBLEM,RETURN)
 COMPONENT DESCRIPTION:   Interactive entry point to create or change comments 
VARIABLES: PROBLEM                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Problem (#9000011) 
VARIABLES: RETURN                       TYPE: Both
 VARIABLES DESCRIPTION:   Indicator, passed by reference, of whether new text
 was successfully entered (1) or if the action was aborted (^) 
VARIABLES: GMPROV                       TYPE: Used
 VARIABLES DESCRIPTION:   IEN of New Person (#200), the user responsible for
 the content of the comment 
VARIABLES: GMPROB                       TYPE: Used
 VARIABLES DESCRIPTION:   Text of problem description, optionally displayed in
 header of screen editor if defined 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES

NUMBER: 4744                            IA #: 4744
  DATE CREATED: AUG 29, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOPRS
  NAME: HL7 MESSAGE PARSING APIs (PRE-HLO) (continued)
  ID: HLOPRS
 GENERAL DESCRIPTION:   This integration agreement completes the description of
 the HL7 message parsing APIs that begins with DBIA #4742.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$GET(.SEGMENT,SEQ,COMP,SUBCOMP,REP)
 COMPONENT DESCRIPTION:   This function gets a value from a segment that was
 obtained by calling $$NEXTSEG.  The SEQ, COMP, SUBCOMP, and REP parameters are
 optional. If not specified, they default to the value1. For example,
 $$GET^HLPRS(.SEGMENT,1) will return the value of the first field, first
 component, first subcomponent, in the first occurrence.  Since many fields
 consist of a single simple value, this is a useful feature.  $$GET^HLOPRS(0)
 may be used to return the segment type.  
  
VARIABLES: $$GET                        TYPE: Output
 VARIABLES DESCRIPTION:   Function returns the value on success, "" on failure
 or if the specified part is not valued.  
  
VARIABLES: SEGMENT                      TYPE: Input
 VARIABLES DESCRIPTION:   (required, pass by reference) 
  
 The segment was placed in this array by $$NEXTSEG.  
  
VARIABLES: SEQ                          TYPE: Input
 VARIABLES DESCRIPTION:   The sequence number of the field, defaults to 1.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   The number of the component, defaults to 1.  
  
VARIABLES: SUBCOMP                      TYPE: Input
 VARIABLES DESCRIPTION:   The number of the subcomponent, defaults to 1.  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   The occurrence number.  For a non-repeating field,
 the occurrence number need not be provided, because it is always 1.  
  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   The IB package is granted authority to use these new
 APIs for the PFSS project.  
  
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   The DG package is granted authority to use these new
 APIs for the PFSS project.  
  

NUMBER: 4745                            IA #: 4745
  DATE CREATED: APR 30, 2015
  CUSTODIAL PACKAGE: FUNCTIONAL INDEPENDENCE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RMIMRP
  NAME: RMIMRP calls                    ID: RMIMRP
 GENERAL DESCRIPTION:   This documents the calls used by the Virtual Patient
 Record (VPR) to extract Functional Independence Measurement data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PRM(.PARAM)
 COMPONENT DESCRIPTION:   Returns site parameters from the FIM Parameter file
 #783.9 
VARIABLES: PARAM                        TYPE: Both
 VARIABLES DESCRIPTION:   Array name, passed by reference, in which results
 will be returned as: 
  PARAM(1) = InstitutionName ^ Station# ^ Mail 
   Group (#.03) ^ FSOD Note Title (#.04) ^ FSOD 
   Note Title name ^ NonFSOD Note Title (#.05) ^ 
   NonFSOD Note Title name ^ Consult Title (#.06) ^ 
   Consult Title name ^ # of Facility Codes (#10) ^ 
   DTIME 
  PARAM(n) = Facility Code (#783.9001/.01) ^ Type 
   of Care (#.02) 
COMPONENT/ENTRY POINT: LC(.LIST,PATIENT)
 COMPONENT DESCRIPTION:   Returns a list of cases from the FIM file #783 for a
 patient, at a given facility 
VARIABLES: PATIENT                      TYPE: Input
 VARIABLES DESCRIPTION:   String consisting of DFN^FAC where 
   DFN=Patient file #2 IEN 
   FAC=Facility Code, from FIM Parameters #783.9 
VARIABLES: LIST                         TYPE: Both
 VARIABLES DESCRIPTION:   Array name, passed by reference, in which results
 will be returned as: 
  LIST(1) = # of cases returned 
  LIST(n) = Case (#.02) ^ Patient (#.03) ^ 
   Facility Code (#.06) ^ Admit Date (#.1) ^ 
   Discharge Date (#.11) 
COMPONENT/ENTRY POINT: GC(.RES,CASE)
 COMPONENT DESCRIPTION:   Returns the details of a case from the FIM file #783 
VARIABLES: CASE                         TYPE: Input
 VARIABLES DESCRIPTION:   Site Case Number (#.02) 
VARIABLES: RES                          TYPE: Both
 VARIABLES DESCRIPTION:   Array name, passed by reference, in which results
 will be returned as: 
  RES(1) = IEN (#.01) ^ Case Number (#.02) ^ 
   Patient (#.03) ^ Pt ID (#.04) ^ Pt DOB (#.05) ^ 
   Facility Code (#.06) ^ Type of Care (#.07) ^ 
   Impairment Group (#.08) ^ Onset Date (#.09) ^ 
   Admit Date (#.1) ^ Discharge (#.11) ^ 
   Prog Note IEN (#.16) ^ Email ID (#.17) 
  RES(2) = ^RMIM(783,D0,1) 
  RES(3) = ^RMIM(783,D0,2) 
  RES(4) = ^RMIM(783,D0,3) 
  RES(5) = ^RMIM(783,D0,4) 
  RES(6) = ^RMIM(783,D0,5) 
  RES(7) = ^RMIM(783,D0,6) 
  RES(8) = ^RMIM(783,D0,7) 
  RES(9) = ^RMIM(783,D0,8) 
  RES(10)= Note (#100), first line of text 
  RES(n) = Note (#100), additional lines of text 
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: JUL 21, 2015

NUMBER: 4746                            IA #: 4746
  DATE CREATED: MAY 21, 2015
  CUSTODIAL PACKAGE: VIRTUAL PATIENT RECORD
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VPR GET PATIENT DATA JSON
 GENERAL DESCRIPTION:   VPR GET PATIENT DATA JSON is an rpc that pulls patient
 data from VistA and returns it in an array formatted as JSON. Please see the
 VPR Technical Manual for details about input parameters and output data
 elements.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JSON
SUBSCRIBING PACKAGE: HEALTH DATA REPOSITORY
 SUBSCRIBING DETAILS:   Increment 14, HDR v3.9 
SUBSCRIBING PACKAGE: LIGHTHOUSE
 SUBSCRIBING DETAILS:   Added 1/22/21 to collect patient data directly from
 VistA to support the Covid Patient Manager (CPM) SMART ON FHIR app that VA is
 currently building.  
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 7/8/24 effective with CDSP*1.0*1, to include VPR
 GET PATIENT DATA JSON in the CDSP RPC CONTEXT option. CDSP needs to collect
 patient data directly from VistA to support APPs such as Lung Cancer Screening
 and Precision Oncology.  
  DATE ACTIVATED: JUL 06, 2015

NUMBER: 4747                            IA #: 4747
  DATE CREATED: AUG 01, 2005
  CUSTODIAL PACKAGE: VIRTUAL PATIENT RECORD
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VPROR
  NAME: VPR updates from OR             ID: VPROR
 GENERAL DESCRIPTION:   This documents the calls used by Order Entry/Results
 Reporting to update a patient data cache in the Virtual Patient Record (VPR).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4748                            IA #: 4748
  DATE CREATED: AUG 01, 2005
  CUSTODIAL PACKAGE: VIRTUAL PATIENT RECORD
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VPROR1
  NAME: VPR updates from OR             ID: VPROR1
 GENERAL DESCRIPTION:   This documents the calls used by Order Entry/Results
 Reporting to update a patient data cache in the Virtual Patient Record (VPR).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4749                            IA #: 4749
  DATE CREATED: AUG 01, 2005
  CUSTODIAL PACKAGE: VIRTUAL PATIENT RECORD
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VPRPROC
  NAME: VPR updates from MCAR/MD        ID: VPRPROC
 GENERAL DESCRIPTION:   This documents the calls used by Clinical Procedures to
 update a patient data cache in the Virtual Patient Record (VPR).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES

NUMBER: 4750                            IA #: 4750
  DATE CREATED: AUG 02, 2005
  CUSTODIAL PACKAGE: VIRTUAL PATIENT RECORD
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VPRSR
  NAME: VPR updates from SR             ID: VPRSR
 GENERAL DESCRIPTION:   This documents the calls used by Surgery to update a
 patient data cache in the Virtual Patient Record (VPR).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: NEW(IEN,DFN,STATUS)
 COMPONENT DESCRIPTION:   Creates a new surgical request in the VPR.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Surgery file #130 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Patient file #2 
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   Text of current status name 
COMPONENT/ENTRY POINT: UPD(IEN,DFN,STATUS)
 COMPONENT DESCRIPTION:   Updates an existing surgical request in the VPR.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Surgery file #130 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Patient file #2 
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   Text of current status name 
COMPONENT/ENTRY POINT: DEL(IEN,DFN)
 COMPONENT DESCRIPTION:   Removes an existing surgical request from the VPR.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Surgery file #130 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Patient file #2 
SUBSCRIBING PACKAGE: SURGERY

NUMBER: 4751                            IA #: 4751
  DATE CREATED: OCT 31, 2014
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUSRVLO
  NAME: Calls to TIUSRVLO               ID: TIUSRVLO
 GENERAL DESCRIPTION:   The Virtual Patient Record (VPR) would like to call
 $$IMGCNT^TIUSRVLO to retrieve the number of images tied to a given document.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IMGCNT
COMPONENT/ENTRY POINT: $$IMGCNT(IEN)
 COMPONENT DESCRIPTION:   Returns the number of images linked to a document via
 the TIU EXTERNAL DATA LINK file #8925.91.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of TIU DOCUMENT file #8925 
VARIABLES: $$IMGCNT                     TYPE: Output
 VARIABLES DESCRIPTION:   Number 
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 04/26/21, effective with patch OR*3.0*498 

NUMBER: 4752                            IA #: 4752
  DATE CREATED: AUG 01, 2005
  CUSTODIAL PACKAGE: VIRTUAL PATIENT RECORD
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VPRXHTML
  NAME: VPR utilities for XHTML         ID: VPRXHTML
 GENERAL DESCRIPTION:   This documents the calls available to manage
 XHTML-formatted text in M.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
SUBSCRIBING PACKAGE: PROBLEM LIST

NUMBER: 4753                            IA #: 4753
  FILE NUMBER: 120.5                    GLOBAL ROOT: GMR(120.5,
  DATE CREATED: DEC 12, 2014
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: AVPR index
  ID: GMR(120.5,
GLOBAL REFERENCE: GMR(120.5,D0,0)
FIELD NUMBER: .02                       FIELD NAME: PATIENT
  LOCATION: 0;2                         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
 GENERAL DESCRIPTION:   The Virtual Patient Record (VPR) would like to create
 an action index on the GMRV Vital Measurement file #120.5, that would call a
 VPR API in routine VPREVNT when data in the file is entered or modified. The
 FileMan utility CREIXN^DDMOD would be used in a post-init for patch VPR*1*3 to 
 create the AVPR index, instead of exporting the data dictionary. The three 
 fields listed here are the ones included in the index.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AVPR
KEYWORDS: VPREVNT
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: FEB 23, 2015

NUMBER: 4754                            IA #: 4754
  FILE NUMBER: 8925                     GLOBAL ROOT: DD('IX',
  DATE CREATED: OCT 02, 2014            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VPRVIT
  NAME: SETTING DD('IX')                ID: VPRVIT
GLOBAL REFERENCE: DD('IX',D0,'NOREINDEX')
 GLOBAL DESCRIPTION:   Post-init for patch TIU*1*106 will directly set this
 node to 1, immediately after calling CREIXN^DDMOD to create the new index.  
 GENERAL DESCRIPTION:   Text Integration Utilities (TIU) requests permission to
 directly set the ^DD("IX",DA,"NOREINDEX") node in a post-init. DIKCBLD is used
 to create the post-init routine that will install the new index, but the new 
 NOREINDEX flag is not being picked up yet by this utility, and CREIXN^DDMOD 
 does not currently accept the NOREINDEX designator as part of its input array.
 This is a one-time request for patch TIU*1*106.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  DATE ACTIVATED: NOV 04, 2014

NUMBER: 4755                            IA #: 4755
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19,
  DATE CREATED: SEP 09, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: ADD B-OPTIONS TO MENU OF B-OPTION
  ID: DIC(19,
GLOBAL REFERENCE: DIC(19,D0,10,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 GLOBAL DESCRIPTION:   MENU multiple of OPTION file.  
 GENERAL DESCRIPTION:   Kernel's KIDS package currently supports adding an
 option from another package to the MENU multiple of either a MENU type option,
 or an EXTENDED ACTION type option as part of a packages KIDS installation.
 However it doesn't support adding an option to the MENU multiple of a BROKER
 type option.  
  
 Request is to use FileMan call UPDATE^DIE to add BROKER type options to the
 MENU multiple of an existing BROKER type option.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
  EXPIRATION DATE: FEB 16, 2007
KEYWORDS: BROKER
KEYWORDS: BROKER TYPE OPTION
KEYWORDS: OPTION
KEYWORDS: MENU
KEYWORDS: REMOTE PROCEDURE
SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE
 SUBSCRIBING DETAILS:   Patient Advocate Tracking System (PATS) is a new
 application that will replace the old Patient Representative system. PATS uses
 the services Patient Service Lookup (PSL) and Patient Service Construct (PSC).
 These services each have a Broker Type option containing one or more RPCs that
 need to be assigned to any user of their services.  
  
 PATS plans to add the PSL and PSC Broker Type options as Menu Items to an 
 existing PATS Broker Type option in a POST-INIT routine in the the PATS KIDS
 build. This will allow the sites to assign just one B-type option to the PATS
 users rather than three. (See also IA #4686).  

NUMBER: 4756                            IA #: 4756
  DATE CREATED: OCT 06, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUS1
  NAME: DBIA4756                        ID: XUS1
 GENERAL DESCRIPTION:   This agreement allows the VistaLink package to use
 routine XUS1 to perform user validation during the VistaLink reauthentication
 process, which includes support for the login capabilities of FatKAAT and
 KAAJEE.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK SECURITY
COMPONENT/ENTRY POINT: SAVE
 COMPONENT DESCRIPTION:   Will preserve user sign-on variables in ^XUTL("XQ")
 and HOME device variables during the reauthentication process.  
SUBSCRIBING PACKAGE: VISTALINK SECURITY

NUMBER: 4757                            IA #: 4757
  DATE CREATED: OCT 06, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUS1A
  NAME: DBIA4757                        ID: XUS1A
 GENERAL DESCRIPTION:   This agreement allows the VistaLink package to use
 routine XUS1A to perform user validation during the VistaLink reauthentication
 process, which includes support for the login capabilities of FatKAAT and
 KAAJEE.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK SECURITY
COMPONENT/ENTRY POINT: $$PROHIBIT(TIME,RANGE)
 COMPONENT DESCRIPTION:   User sign-on during prohibited times validation
 checks.  
VARIABLES: TIME                         TYPE: Input
 VARIABLES DESCRIPTION:   Current time (i.e., 2nd piece of $HOROLOG).  
VARIABLES: RANGE                        TYPE: Input
 VARIABLES DESCRIPTION:   Time range that represents when the user may not sign
 on.  Obtained from the PROHIBITED TIMES FOR SIGN-ON field (#15) in the NEW
 PERSON file (#200).  
VARIABLES: $$PROHIBIT                   TYPE: Output
 VARIABLES DESCRIPTION:   If prohibited time(s) exist, result returns: 
   "1^<prohibited times message>" 
   Example:  1^1:00 pm thru 3:00 pm 
  
 Otherwise, result returns: 
   "0^ thru " 
SUBSCRIBING PACKAGE: VISTALINK SECURITY

NUMBER: 4758                            IA #: 4758
  DATE CREATED: OCT 06, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSHSH
  NAME: DBIA4758                        ID: XUSHSH
 GENERAL DESCRIPTION:   This agreement allows the VistaLink package to use
 routine XUSHSH to encrypt Kernel access and verify codes to their hashed
 versions during the VistaLink reauthentication process, to support the login
 capabilities of FatKAAT and KAAJEE.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK SECURITY
COMPONENT/ENTRY POINT: $$EN(X)
 COMPONENT DESCRIPTION:   Convert access or verify code to hashed version.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   Decrypted access or verify code.  
VARIABLES: $$EN                         TYPE: Output
 VARIABLES DESCRIPTION:   Result returned is the hashed access or verify code.  
SUBSCRIBING PACKAGE: VISTALINK SECURITY
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   ADDED 9/29/2009 

NUMBER: 4759                            IA #: 4759
  DATE CREATED: OCT 06, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSRB4
  NAME: DBIA4759                        ID: XUSRB4
 GENERAL DESCRIPTION:   This agreement allows the VistaLink package to use
 routine XUSRB4 to perform validation checks on the Kernel CCOW user sign-on
 token during the VistaLink reauthentication process.  This is used for the
 purpose of integrating with the Single Sign-On/User Context (SSO/UC) project
 (part of Infrastructure & Security Services).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK SECURITY
COMPONENT/ENTRY POINT: $$CHECK(HL,TOUT)
 COMPONENT DESCRIPTION:   Perform validation checks for a Kernel CCOW auto
 sign-on token handle.  
VARIABLES: HL                           TYPE: Input
 VARIABLES DESCRIPTION:   Kernel CCOW token handle.  
VARIABLES: TOUT                         TYPE: Input
 VARIABLES DESCRIPTION:   Kernel CCOW token timeout value in seconds.  Value
 will default to 20 seconds if not passed in.  
VARIABLES: $$CHECK                      TYPE: Output
 VARIABLES DESCRIPTION:   Result returns: 
   On failure: "0^Short error message of failure" 
       Examples: "0^Bad Token" 
                 "0^Bad User" 
  
   On success: DUZ 
SUBSCRIBING PACKAGE: VISTALINK SECURITY

NUMBER: 4760                            IA #: 4760
  DATE CREATED: OCT 06, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSTZ
  NAME: DBIA4760                        ID: XUSTZ
 GENERAL DESCRIPTION:   This agreement allows the VistaLink package to use
 routine XUSTZ to perform Kernel IP address locking during the VistaLink
 reauthentication process, which includes support for the login capabilities of
 FatKAAT and KAAJEE.  
  
 For more information on IP address locking, please see patch XU*8*265, 
 Subject: 3 Strikes and You Are Out.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK SECURITY
COMPONENT/ENTRY POINT: $$RA(IP)
 COMPONENT DESCRIPTION:   Used to lock the user or IP address, file data in the
 FAILED ACCESS ATTEMPTS LOG file (#3.05), and provide error text.  Used by
 VistaLink when constructing the 'IP Address Locked' error (#182306 in the
 DIALOG file (#.84)).  
VARIABLES: IP                           TYPE: Input
 VARIABLES DESCRIPTION:   IP address.  
VARIABLES: $$RA                         TYPE: Output
 VARIABLES DESCRIPTION:   Result returns: 
   On failure, TXT variable will contain a text message related to user or 
   IP address failure, i.e. "Your access has been locked-out for xx 
   seconds." or "This IP address has been locked." 
  
   On success, TXT="".  
SUBSCRIBING PACKAGE: VISTALINK SECURITY

NUMBER: 4761                            IA #: 4761
  DATE CREATED: OCT 06, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSTZIP
  NAME: DBIA4761                        ID: XUSTZIP
 GENERAL DESCRIPTION:   This agreement allows the VistaLink package to use
 routine XUSTZIP to perform checks on Kernel IP/device locking during the
 VistaLink reauthentication process, which includes support for the login 
 capabilities of FatKAAT and KAAJEE.  
  
 For related information on IP address locking, see integration agreement 
 #4760.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK SECURITY
COMPONENT/ENTRY POINT: $$LKCHECK(IP)
 COMPONENT DESCRIPTION:   Kernel check to determine whether the IP address is
 locked.  Used by VistaLink when constructing the 'Too many invalid signon
 attempts' error for this condition.  
VARIABLES: IP                           TYPE: Input
 VARIABLES DESCRIPTION:   IP address.  
VARIABLES: $$LKCHECK                    TYPE: Output
 VARIABLES DESCRIPTION:   Result on failure returns the FileMan date/time that
 the IP address should be locked until.  
  
 Result on success returns 0.  
SUBSCRIBING PACKAGE: VISTALINK SECURITY

NUMBER: 4762                            IA #: 4762
  DATE CREATED: OCT 06, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUS
  NAME: DBIA4762                        ID: XUS
 GENERAL DESCRIPTION:   This agreement allows the VistaLink package to use
 routine XUS to check initial sign-on parameters and environment/volume set
 information in the KERNEL SYSTEM PARAMETERS file (#8989.3) during the
 VistaLink reauthentication process, which includes support for the login 
 capabilities of FatKAAT and KAAJEE.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK SECURITY
COMPONENT/ENTRY POINT: XOPT
 COMPONENT DESCRIPTION:   Get sign-on parameters from "XUS" node of
 ^XTV(8989.3).  
VARIABLES: XOPT                         TYPE: Output
 VARIABLES DESCRIPTION:   User sign-on parameters contained in variable XOPT
 (piece-delimited by 
 "^").
COMPONENT/ENTRY POINT: XUVOL
 COMPONENT DESCRIPTION:   Get environment/volume set parameters from VOLUME SET
 multiple (#8989.304).  
VARIABLES: XUENV                        TYPE: Output
 VARIABLES DESCRIPTION:   Full environment variable in form
 UCI^VOL^NODE^BOX:VOLUME.  
VARIABLES: XUCI                         TYPE: Output
 VARIABLES DESCRIPTION:   UCI variable.  
VARIABLES: XQVOL                        TYPE: Output
 VARIABLES DESCRIPTION:   Volume Set variable.  
VARIABLES: XUVOL                        TYPE: Output
 VARIABLES DESCRIPTION:   Volume Set record from VOLUME SET multiple
 (#8989.304).  
SUBSCRIBING PACKAGE: VISTALINK SECURITY

NUMBER: 4763                            IA #: 4763
  DATE CREATED: AUG 16, 2005            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FHOMAPI
  NAME: OUTPATIENT MEALS DATA           ID: FHOMAPI
 GENERAL DESCRIPTION:   This IA allows OE/RR to call functions that will return
 3 pieces of data for Outpatient Meals.  
  
 $$AUTH^FHOMAPI(DUZ) - The user's DUZ is passed into this function and the 
 function returns a '1' (user holds the FHAUTH key) or a '0' (user does not 
 hold the FHAUTH key).  
  
 DIETLST^FHOMAPI - No variables are passed into this API, which simply returns 
 the array FHDIET containing the list of allowable outpatient diets from the FH
 Site Parameters (#119.9) file.  
  
 $$MAXDAYS^FHOMAPI(FHLOC) - A hospital location pointer is passed into this 
 function and the function returns the numeric "Max Number of Days" for which 
 recurring meals can be ordered for this location.  
  
 $$NFSLOC^FHOMAPI(FHLOC) - A hospital location pointer is passed into this 
 function and the function returns the NFS location name corresponding to that 
 hospital location.  
  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$AUTH(DUZ)
 COMPONENT DESCRIPTION:   Returns whether or not user holds FHAUTH key.  
  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the New Person (#200) file.  
  
VARIABLES: $$AUTH                       TYPE: Output
 VARIABLES DESCRIPTION:   This will be a numeric field returning whether or not
 the person holds the FHAUTH key, 1 for "Yes", 0 for "No".  
  
COMPONENT/ENTRY POINT: $$MAXDAYS(FHLOC)
 COMPONENT DESCRIPTION:   Returns Max Number of Days recurring meals can be
 ordered for at this location.  
  
VARIABLES: FHLOC                        TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the Hospital Location (#44)
 file.  
  
VARIABLES: $$MAXDAYS                    TYPE: Output
 VARIABLES DESCRIPTION:   This will be a numeric field containing the maximum
 number of days in advance a recurring meal can be ordered for this NFS
 location.  
  
COMPONENT/ENTRY POINT: $$NFSLOC(FHLOC)
 COMPONENT DESCRIPTION:   Returns NFS location name corresponding to the
 hospital location passed in.  
  
VARIABLES: FHLOC                        TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the Hospital Location (#44)
 file.  
  
VARIABLES: $$NFSLOC                     TYPE: Output
 VARIABLES DESCRIPTION:   This will be a free-text field displaying the NFS
 location name.  
  
COMPONENT/ENTRY POINT: DIETLST
 COMPONENT DESCRIPTION:   Returns array FHDIET containing list of allowable
 outpatient meals diets from the FH Site Parameters (#119.9) file.  
  
VARIABLES: FHDIET                       TYPE: Output
 VARIABLES DESCRIPTION:   This output variable is an array containing the
 allowable outpatient diets from the FH Site Parameters (#119.9) file, in the
 format FHDIET(N)="IEN^NAME".  The IEN is the pointer to the entry in the Diets
 (#111) file and the NAME is the displayable name of the Diet.  For example: 
  
 FHDIET(1)="25^OUTPATIENT REGULAR" FHDIET(2)="33^LOW CHOLESTEROL" etc...  
  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4764                            IA #: 4764
  DATE CREATED: OCT 06, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUS3
  NAME: DBIA4764                        ID: XUS3
 GENERAL DESCRIPTION:   This agreement allows the VistaLink package to use
 routine XUS3 to check, clear, and set the failed access count in the FAILED
 SIGNON ATTEMPTS file (#3.084).  This will track the count of sign-on attempts
 from an IP address or domain.  It is used during the VistaLink
 reauthentication process, which includes support for the login capabilities of
 FatKAAT and KAAJEE.  
  
 See patch XU*8*265 for more information on the FAILED SIGNON ATTEMPTS file 
 (#3.084).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK SECURITY
COMPONENT/ENTRY POINT: CLRFAC
 COMPONENT DESCRIPTION:   Perform a lookup using the IP address and clear the
 failed access count (fac) from the FAILED SIGNON ATTEMPTS file (#3.084). 
 VistaLink will call this to reinitialize the fac after successful
 reauthentication.  
VARIABLES: IP                           TYPE: Input
 VARIABLES DESCRIPTION:   IP address.  
COMPONENT/ENTRY POINT: $$FAIL(IP)
 COMPONENT DESCRIPTION:   Used by VistaLink to set the failed access count in
 the FAILED SIGNON ATTEMPTS file (#3.084).  
VARIABLES: IP                           TYPE: Input
 VARIABLES DESCRIPTION:   IP address.  
VARIABLES: $$FAIL                       TYPE: Output
 VARIABLES DESCRIPTION:   On failure, return result is 1 (Failed Access Count
 is not less than the value in the DEFAULT # OF ATTEMPTS field (#202) of the
 Kernel System Parameters file (#8989.3)).  VistaLink will use this result to
 indicate the 'IP Address Locked' error (#182306 in the DIALOG file (#.84)).  
  
 On success, return result is 0.  
SUBSCRIBING PACKAGE: VISTALINK SECURITY

NUMBER: 4765                            IA #: 4765
  DATE CREATED: OCT 06, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSAP
  NAME: DBIA4765                        ID: XUSAP
 GENERAL DESCRIPTION:   This agreement allows the VistaLink package to use
 routine XUSAP to implement the Kernel Connector Proxy/Application Proxy APIs. 
 These APIs are used in both VistaLink initial authentication and
 reauthentication processes.  These methods have been approved by the Single
 Sign-On/User Context (SSO/UC) project (part of Infrastructure & Security
 Services).  
  
 See Kernel supported reference #4677 for more information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK SECURITY
COMPONENT/ENTRY POINT: $$APFIND(NAME)
 COMPONENT DESCRIPTION:   Application proxy user lookup by name.  
VARIABLES: NAME                         TYPE: Input
 VARIABLES DESCRIPTION:   NAME field (#.01) in the NEW PERSON file (#200).  
VARIABLES: $$APFIND                     TYPE: Output
 VARIABLES DESCRIPTION:   Result returns: 
   On failure, result returns 0.  
  
   On success, result returns "IEN^VPID" of the application proxy user.  
   (VPID = VA Person ID Number) 
COMPONENT/ENTRY POINT: CONT
 COMPONENT DESCRIPTION:   Interactively create (or edit if record already
 exists) Connector Proxy user in the NEW PERSON file (#200).  
VARIABLES: Record                       TYPE: Output
 VARIABLES DESCRIPTION:   To create a Connector Proxy user using this option,
 user must hold the XUMGR key.  
  
 Code will automatically set the following fields in the NEW PERSON file 
 (#200): 
   o  FILE MANAGER ACCESS CODE (#3) = "#" 
   o  VERIFY CODE never expires (#7.2) = "Yes" 
   o  MULTIPLE SIGN-ON (#200.04) = "ALLOWED" 
   o  In the USER CLASS multiple (#200.07): 
        o  User Class (#.01) = "CONNECTOR PROXY" 
        o  ISPRIMARY (#2)    = "Yes" 
VARIABLES: NAME                         TYPE: Input
 VARIABLES DESCRIPTION:   Enter Connector Proxy name.  
VARIABLES: ACCESS CODE                  TYPE: Input
 VARIABLES DESCRIPTION:   Can edit Access Code of Connector Proxy user.  
VARIABLES: VERIFY CODE                  TYPE: Input
 VARIABLES DESCRIPTION:   Can edit Verify Code of Connector Proxy user.  
VARIABLES: PRIMARY MENU                 TYPE: Input
 VARIABLES DESCRIPTION:   Can edit Primary Menu of Connector Proxy user.  
COMPONENT/ENTRY POINT: $$CPCHK(IEN)
 COMPONENT DESCRIPTION:   VistaLink uses this to perform Connector Proxy user
 validation checks such as: 
   o  Check that the zero node record for the user in the NEW PERSON file 
      (#200) is defined.  
   o  Check that User Class = "CONNECTOR PROXY" 
      User Class value can be found by navigating to the User Class field 
      (#.01) of the USER CLASS sub-field (#9.5) of the NEW PERSON file 
      (#200)).  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Connector Proxy user in NEW PERSON file
 (#200).  
VARIABLES: $$CPCHK                      TYPE: Output
 VARIABLES DESCRIPTION:   Used in VistaLink to validate the connector proxy
 user.  
  
 If failure, result returned as "0^Error Message".  
      Examples:  "0^IEN not valid" 
                 "0^Not a CONNECTOR PROXY User" 
  
 If success, result = 1.  
COMPONENT/ENTRY POINT: $$RPC(RPC)
 COMPONENT DESCRIPTION:   Validate that the Application Proxy user is allowed
 to run a specific RPC.  
VARIABLES: $$RPC                        TYPE: Output
 VARIABLES DESCRIPTION:   Result returns: 
   If failure (not allowed to run RPC), result = 0.  
  
   If success, result = 1 (the value of the APP PROXY ALLOWED field (#.11) 
   of the RPC BROKER file (#8994)).  
VARIABLES: RPC                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN from the RPC BROKER file (#8994).  
SUBSCRIBING PACKAGE: VISTALINK
SUBSCRIBING PACKAGE: VISTALINK SECURITY

NUMBER: 4766                            IA #: 4766
  DATE CREATED: AUG 04, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VBECA3
  NAME: BLOOD BANK ORDER ENTRY API      ID: VBECA3
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VBECA3
KEYWORDS: OEAPI
COMPONENT/ENTRY POINT: OEAPI
 COMPONENT DESCRIPTION:   This API provides Blood Bank patient specific and
 order entry data for the purpose of creating Blood Bank orders in CPRS.  
VARIABLES: ARR                          TYPE: Input
 VARIABLES DESCRIPTION:   Name of local array used to return data.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of patient in the PATIENT file (#2).  
VARIABLES: DIV                          TYPE: Input
 VARIABLES DESCRIPTION:   Station number of division associated with the
 patient's location.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4767                            IA #: 4767
  DATE CREATED: AUG 22, 2005            CUSTODIAL PACKAGE: VBECS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VBECA7
  NAME: VBECS WORKLOAD CAPTURE          ID: VBECA7
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VBECA7
COMPONENT/ENTRY POINT: WKLDCAP
 COMPONENT DESCRIPTION:   This API will initiate a request to the re-engineered
 Blood Bank medical device for pending workload events.  
COMPONENT/ENTRY POINT: UPDTWKLD
 COMPONENT DESCRIPTION:   This API is used to indicate that Lab has completed
 processing workload data. The API will initiate an update to the re-engineered
 Blood Bank medical device for all completed workload data.  
SUBSCRIBING PACKAGE: LAB SERVICE

NUMBER: 4768                            IA #: 4768
  GLOBAL ROOT: DD(                      DATE CREATED: DEC 15, 2010
  CUSTODIAL PACKAGE: 1                  USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DIRECT DD ACCESS TO SUBFILE 'NM' node
  ID: DD(
GLOBAL REFERENCE: DD(D0,0,'NM',
 GLOBAL DESCRIPTION:   Access to the 'NM' node of a subfile is requested to get
 the name of the corresponding field at the previous level.  
 GENERAL DESCRIPTION:   The LAB SERVICE package (LSRP project) needs to access
 the name of the sub-file, given its subfile number.  We would like to access
 this via direct ^DD global read of the 'NM' node: 
  
     S NAME=$O(^DD(subfile#,0,"NM","")) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 5/28/24 to document historical use of S 
 PXQNAME=$O(@DD@(PXQFILE,0,"NM","")) in the PCE DEBUGGING UTILITIES.  
 Documenting ICR effective with PX*1.0*214.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Added 5/28/24 to document historical use of S
 NAME=$O(^DD(subfile#,0,"NM","") in the PXRMSINQ routine, a generic inquiry
 utility. Documenting ICR effective with PXRM*2.0*67.   
  DATE ACTIVATED: DEC 15, 2010

NUMBER: 4769                            IA #: 4769
  DATE CREATED: AUG 05, 2005
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUMHEV
  NAME: TIU MyHealthEVet APIs           ID: TIUMHEV
 GENERAL DESCRIPTION:   APIs to TIU calls to support Dischare Summary and
 Progress Notes lookup for MyHealthEVet.  
  
  
  STATUS: Active
KEYWORDS: MHEV
KEYWORDS: TIUMHEV
COMPONENT/ENTRY POINT: LISTDS
 COMPONENT DESCRIPTION:   The API should return a list of all Discharge
 documents that fall within the date range and have a STATUS of either
 completed, amended or retracted. The list should include identifying
 information about the document, IEN and STATUS.  The list would be returned in
 a TMP global sorted by STATUS. The first date in the date range can be null or
 0, which indicates to start from the oldest date.  The second date in the date
 range can be null or 0 indicating today.  The results of the call are stored
 in the following STATUS sorted temp global: 
  
        ^TMP("TIUMHEVLIST",$J,STATUS,TIUIEN) 
  
 Where STATUS is the status of the Discharge Summary TIUIEN 
  
VARIABLES: DFN                          TYPE: Input
VARIABLES: START                        TYPE: Input
VARIABLES: END                          TYPE: Input
COMPONENT/ENTRY POINT: GETTEXT
 COMPONENT DESCRIPTION:   This component/entry point returns the text of the
 Discharge Summary TIUDA into the temp global: 
        
        ^TMP("TIUMHEVTEXT",$J,DA)="TEXT" 
  
 Where DA is the line number of the text.  
  
VARIABLES: TIUDA                        TYPE: Input
COMPONENT/ENTRY POINT: GETDATA
 COMPONENT DESCRIPTION:   This component/entry point returns the Data fields of
 the Discharge Summary TIUDA into the following temp global: 
  
        ^TMP("TIUMHEVDATA",$J,TIUDA,FIELD)=Field value 
  
 for each FIELD in the TIU DOCUMENTS file from the following list: 
  
        .01 to 1 
        1200 to 70201 
  
COMPONENT/ENTRY POINT: LISTPN
 COMPONENT DESCRIPTION:   The list would be returned in a TMP global sorted by
 STATUS. The first date in the date range can be null or 0, which indicates to
 start from the oldest date.  The second date in the date range can be null or
 0 indicating today.  The results of the call are stored in the following
 STATUS sorted temp global: 
  
        ^TMP("TIUMHEVLIST",$J,STATUS,TIUIEN) 
  
 Where STATUS is the status of the PROGRESS NOTE TIUIEN 
  
VARIABLES: DFN                          TYPE: Input
VARIABLES: START                        TYPE: Input
VARIABLES: END                          TYPE: Input
SUBSCRIBING PACKAGE: MYHEALTHEVET

NUMBER: 4770                            IA #: 4770
  DATE CREATED: AUG 08, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSRB4
  NAME: unique handle into XTMP global.
  ID: XUSRB4
 GENERAL DESCRIPTION:   Create and return a unique handle (subscript) for the
 ^XTMP global and create the required zero node.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$HANDLE(<namespace>[,<timetolive>])
 COMPONENT DESCRIPTION:   This call creates and returns a unique handle
 (subscript) for the ^XTMP global and create the required zero node.  
VARIABLES: namespace                    TYPE: Input
 VARIABLES DESCRIPTION:   This is the application namespace that will be used
 as a prefix to the handle.  If this input is empty the call will return a null
 value.  
VARIABLES: timetolive                   TYPE: Input
 VARIABLES DESCRIPTION:   This is the number of days that the record should not
 be removed by the cleanup process.  

NUMBER: 4771                            IA #: 4771
  DATE CREATED: AUG 09, 2005
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RABWORD1
  NAME: DBIA4771                        ID: RABWORD1
 GENERAL DESCRIPTION:   This extrinsic function will be used by CPRS to
 transmit changes made to certain Radiology orders that were originally placed
 via the Radiology application, not via the CPRS application.  These "backdoor"
 orders, if they are telephoned or verbal orders, require an electronic
 signature in CPRS.  Before the e-sig is entered, the provider may add/edit
 certain data:  ICD Diagnoses and their associated clinical indicators.  
  
 This API will be used to store the updated data in the RAD/NUC MED ORDERS file
 (#75.1).  Previous data for ordering ICD diagnoses and their associated
 clinical indicators will be removed from the order before storing the updated
 data.  If the order had already been completed in Radiology and sent to PCE,
 then Radiology will re-complete the order and re-send it to PCE.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$CPRSUPD(RADFN,RAITEM,RAORIEN,RADX,RASCEI)
VARIABLES: RADFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: RAITEM                       TYPE: Input
 VARIABLES DESCRIPTION:   PACKAGE REFERENCE from the ORDER file (#100) 
VARIABLES: RAORIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN from the ORDER file (#100) 
VARIABLES: RADX                         TYPE: Input
 VARIABLES DESCRIPTION:   This must be passed by reference.  It is an array of
 pointers to the ICD DIAGNOSIS file (#80).  The first array element is the
 primary ordering ICD diagnosis, the others are secondary ordering ICD
 diagnoses.  
VARIABLES: RASCEI                       TYPE: Input
 VARIABLES DESCRIPTION:   A string of 7 pieces for the clinical indicators,
 separated by "^". A value of "1" means "Yes", "0" means "No", and null means
 "Not Asked".  The 7 pieces are in this order: AO, IR, SC, EC, MST, HNC, and
 CV.  "AO" is Agent Orange, "IR" is Ionizing Radiation, "SC" is Service
 Connected, "EC" is Environmental Contaminants, "MST" is Military Sexual
 Trauma, "HNC" is Head/Neck Cancer, and "CV" is Combat Vet. 
VARIABLES: $$CPRSUPD                    TYPE: Output
 VARIABLES DESCRIPTION:   A string of either 1 or 2 pieces, depending on
 success.  
  
 If the call was successful, the returned value is 1.  
  
 If the call was unsuccessful, the returned value is in 2 pieces: 
     0^error message.  The error message indicates the reason for failure. 
 Eg., "Order #nn does not match Radiology Order # ppp", "Order #nn's DFN=qwqw,
 but Radiology Order #ppp 's DFN=tgtg".  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4772                            IA #: 4772
  DATE CREATED: AUG 22, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  ROUTINE: IBBFINS                      NAME: INSURANCE PROCESSING
  ID: IBBFINS
 GENERAL DESCRIPTION:   This integration agrement between Integrated Billing
 and Registration is to allow the processing of Insurance Buffer entries before
 subsequent send to the COTS Billing package.  Regsitration will call the IB
 routine IBBFINS in order to assign Financial Status Classifications (FSC) to
 insurance buffers entries that currently do not have a FSC assigned in order
 to interface them to the COTS Billing package along with
 Registration/Demographic changes.  
  
 The call will be constructed as EN^IBBFINS(DFN) where DFN is the Internal 
 Entry Number of the patient in the PATIENT (#2) file.  IB will process the 
 Insurance Buffer (#355.33) file entries and pass operations back to DG
 Registration for sending the message to COTS Billing.  There is currently NO
 value passed back from IBBFINS to indicate completion.  Once completed,
 Registration is able to send the message on to the COTS Billing package.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: INSURANCE
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Entry point to process a patient's Insurance Buffer
 (#355.33) file entries.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient's Internal Entry Number from the PATIENT
 (#2) file.  
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   This API will be used by DG Registration to correct
 Insurance Buffer (#355.33) file entries for subsequent updates to the COTS
 Billing package.  DG will call this routine by supplying the Patient's DFN so
 that IB can process the correct buffer file entries and pass back processing
 to Registration for the generation of HL7 messages to update/add a patient.  

NUMBER: 4773                            IA #: 4773
  FILE NUMBER: 68                       GLOBAL ROOT: LRO(68
  DATE CREATED: AUG 10, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4773
  ID: LRO(68
GLOBAL REFERENCE: LRO(68,D0,1,D1,1,
FIELD NUMBER: 14                        FIELD NAME: ORDER #
  LOCATION: .1;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: LRDFN
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: ACCESSION
  LOCATION: .2;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: DRAW TIME
  LOCATION: 3;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: FILE #
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: UID
  LOCATION: .3;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LRO(68,D0,1,D1,1,D2,4,D3,
FIELD NUMBER: .01                       FIELD NAME: TEST
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LRO(68,D0,1,D1,1,"C",
 GLOBAL DESCRIPTION:   Direct global access permitted 
 GENERAL DESCRIPTION:   The purpose of this request is to provide the VBECS
 package access to read the Laboratory Accession file for the purpose of
 validating Blood Bank accession related information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VBECS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4774                            IA #: 4774
  FILE NUMBER: 69                       GLOBAL ROOT: LRO(69
  DATE CREATED: AUG 10, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4774
  ID: LRO(69
GLOBAL REFERENCE: LRO(69,D0,1,D1,1,
FIELD NUMBER: 22                        FIELD NAME: MERGE ORDER #
  LOCATION: 1;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: LRDFN
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LRO(69,D0,1,D1,2,
FIELD NUMBER: .01                       FIELD NAME: TEST/PROCEDURE
  LOCATION: 0;1                         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
FIELD NUMBER: 13                        FIELD NAME: UID
  LOCATION: .3;1                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The purpose of this request is to provide the VBECS
 package access to read the Lab Order Entry file to obtain Blood Bank related
 Lab order information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VBECS

NUMBER: 4775                            IA #: 4775
  DATE CREATED: AUG 10, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LRBEBA4
  NAME: DBIA4775                        ID: LRBEBA4
 GENERAL DESCRIPTION:   This DBIA has been initiated to authorize the CPRS
 application to call API UPDOR^LRBEBA4.  This API is used to store data as a
 part of the Clinical Indicator Data Capture (CIDC) project.  The laboratory
 portion of this project is being released with patch LR*5.2*291.  This API
 call stores data received from the order process in CPRS.  The data includes
 service connection indicators, environmental indicators and ICD-9 diagnosis
 codes entered by the provider in CPRS for ordered lab tests.  The data is
 stored in the LAB ORDER ENTRY (#69) file and is transmitted to PCE at the time
 the ordered test is resulted.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LRBEBA4
KEYWORDS: CIDC
COMPONENT/ENTRY POINT: UPDOR
 COMPONENT DESCRIPTION:   This API is used to update the LAB ORDER ENTRY (#69)
 file with service connection indicators, environmental indicators and ICD-9
 diagnosis codes entered by a provider in CPRS for ordered laboratory tests.  
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN.  
  
VARIABLES: ORITEM                       TYPE: Input
 VARIABLES DESCRIPTION:   PACKAGE REFERENCE (#33) field from the ORDER (#100)
 file.  
  
VARIABLES: ORIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   ORDER IEN from the ORDER(#100) file.  
  
VARIABLES: ORSCEI                       TYPE: Input
 VARIABLES DESCRIPTION:   Contains service connection and environmental
 indicators in the following string: 
  
 AO^IR^SC^EC^MST^HNC^CV 
  
  Where: 
  
       AO = Agent Orange 
       IR = Ionizing Radiation 
       SC = Service Connected 
       EC = Environmental Contaminants 
      MST = Military Sexual Trauma 
      HNC = Head and Neck Cancer 
       CV = Combat Veteran 
  
VARIABLES: ORDX                         TYPE: Input
 VARIABLES DESCRIPTION:   Array of pointers to the ICD DIAGNOSIS (#80) file. 
 The first in the array is considered the primary diagnosis.  
  
VARIABLES: LRBERMS                      TYPE: Output
 VARIABLES DESCRIPTION:   1 = Success - LAB ORDER ENTRY (#69) file has been
 updated.  
   
 0^error message = Update did not succeed.  
  
  Where error message contains: 
  
       No Diagnosis Entered 
       Possible reasons for failure is the Order Number did not match.  
       Possible reasons for failure is the DFN did not match.  
       Possible reasons for failure is the Orderable Item did not match.  
  
  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4776                            IA #: 4776
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT(
  DATE CREATED: AUG 15, 2005            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  USAGE: Controlled Subscription        TYPE: File
  NAME: DBIA4776                        ID: ICPT(
GLOBAL REFERENCE: ICPT(D0,0)
FIELD NUMBER: .01                       FIELD NAME: CPT CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: SHORT NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2008
SUBSCRIBING PACKAGE: VBECS
 SUBSCRIBING DETAILS:   VBECS requests permission to read with FileMan the CPT
 file (#81) using the "D" index to identify entries associated with the
 "PATHOLOGY AND LABORATORY SERVICES" CPT CATEGORY.  
  
 A screen will be used to only identify entries with a matching CPT CATEGORY,
 SOURCE of "H" for HCPCS, and active STATUS. The screen will use the function
 $$CPT^ICPTCOD, supported by IA #1995, to validate the entries in the CPT file. 
 

NUMBER: 4777                            IA #: 4777
  FILE NUMBER: 354.7                    GLOBAL ROOT: IBAM(354.7,
  DATE CREATED: AUG 17, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: AR access to IB Patient Copay account data
  ID: IBAM(354.7,
GLOBAL REFERENCE: IBAM(354.7,D0,1,
FIELD NUMBER: .01                       FIELD NAME: MONTH/YEAR
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: TOTAL AMOUNT BILLED
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: CAP REACHED
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: TOTAL AMOUNT NON-BILLABLE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 'AC' - XREF               FIELD NAME: MONTH/YEAR & CAP REACHED
  LOCATION: RCXV('AC',                  ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 4778                            IA #: 4778
  DATE CREATED: AUG 16, 2005            CUSTODIAL PACKAGE: 1
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DICRW
  NAME: DICRW                           ID: DICRW
 GENERAL DESCRIPTION:   Make sure DT and other VA FileMan variables are set
 without the need to set DIQUIET.  
  STATUS: Active
COMPONENT/ENTRY POINT: DTNOLF
 COMPONENT DESCRIPTION:   Set up the necessary VA FileMan variables without
 writting a line feed.  
VARIABLES: %                            TYPE: Output
 VARIABLES DESCRIPTION:   Current VA FileMan Date/Time Example:
 %="3050816.082745" 
VARIABLES: %H                           TYPE: Output
 VARIABLES DESCRIPTION:   Current $H Example: %H="60128,30465" 
VARIABLES: DISYS                        TYPE: Output
 VARIABLES DESCRIPTION:   Pointer value to the MUMPS OPERATING SYSTEM(#.7) file 
 Example: DISYS=18 
VARIABLES: DT                           TYPE: Output
 VARIABLES DESCRIPTION:   The current VA FileMan Date Example: DT=3050816 
VARIABLES: DTIME                        TYPE: Output
 VARIABLES DESCRIPTION:   Default value to be used on timed READs Example:
 DTIME=300 
VARIABLES: DUZ                          TYPE: Output
 VARIABLES DESCRIPTION:   Standard DUZ array Example: DUZ=0 
          DUZ(0)="" 
VARIABLES: IO(0)                        TYPE: Output
 VARIABLES DESCRIPTION:   Current IO device: Example: IO(0)="TNA1249:" 
VARIABLES: U                            TYPE: Output
 VARIABLES DESCRIPTION:   The Usual suspect Example: U="^" 
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   The current VA FileMan date Example: X=3050816 
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4779                            IA #: 4779
  FILE NUMBER: 64                       GLOBAL ROOT: LAM(
  DATE CREATED: AUG 16, 2005            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4779
  ID: LAM(
GLOBAL REFERENCE: LAM(
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
FIELD NUMBER: 2                         FIELD NAME: WKLD UNIT WEIGHT
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: COST
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 13                        FIELD NAME: WKLD CODE LAB SECTION
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAM(D0,4,
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAM("C",
 GLOBAL DESCRIPTION:   Global read access permitted 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VBECS
 SUBSCRIBING DETAILS:   VBECS requests permission to read data in the WKLD CODE
 file (#64) for the purpose of identifying Blood Bank related workload data.  
 The software will perform a direct global read on file 64 identifying all 
 entries where the WKLD CODE LAB SECTION field (#13) is "Blood Bank". The 
 software will identify all CPT codes associated with an entry by referencing
 the LAM("AD",D0,"CPT") index.  

NUMBER: 4780                            IA #: 4780
  DATE CREATED: AUG 16, 2005            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGPFSS1                      NAME: DBIA4780
  ID: DGPFSS1
 GENERAL DESCRIPTION:   This API will be used by DG Registration to generate
 ADT^A28 (Add Person) and ADT^A31 (Update Person) messages to a Commercial
 Off-the-Shelf Billing system for Registration/Demographic Add/Edits to patient
 information.  This API will be provided with the patient's DFN and a flag
 value to indicate whether this is a new person or a person update event.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PFSS
COMPONENT/ENTRY POINT: SEND
 COMPONENT DESCRIPTION:   This entry point initiates the process to send either
 an A28 or A31 message.  This entry point checks the PFSS Master Switch to
 determine it's status.  If the switch is "On", the appropriate person message
 will be queued to the VDEF application for processing.  If the switch is
 "Off", the message will not be queued.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry number in the PATIENT File (#2) for
 the patient.  
VARIABLES: DGNEW                        TYPE: Input
 VARIABLES DESCRIPTION:   Flag variable to indicate whether this is a new
 patient or an update to an existing patient.  DGNEW = 1: New Patient entry
 (A28) 
         0: Update Patient entry (A31) 
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH

NUMBER: 4781                            IA #: 4781
  DATE CREATED: AUG 17, 2005            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFPFSM1
  NAME: BUILD A28/A31 MESSAGE FOR PFSS  ID: VAFPFSM1
 GENERAL DESCRIPTION:   The PFSS 1B Prototype project requires messages to be
 sent from VistA to a Commercial Billing System.  An ADT,A31 (Update Person
 Information) message that is triggered in the Integrated Billing package must
 be sent.  The $$BUILD^VAFPFSM1 function builds that message based on
 information in the VDEF environment.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: A31
KEYWORDS: PFSS
COMPONENT/ENTRY POINT: $$BUILD(EVTIEN,KEY,FLAG,.OUT,MSGID,MSGEVT)
VARIABLES: EVTIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of entry in VDEF Event Description File (#577)
 describing this message.  
VARIABLES: KEY                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Patient File (DFN).  
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   Flag passed by VDEF, default to "V".  
VARIABLES: OUT                          TYPE: Output
 VARIABLES DESCRIPTION:   Output array containing the HL7 message if built in a
 local variable.  
VARIABLES: MSGID                        TYPE: Input
 VARIABLES DESCRIPTION:   Message identifying information as passed by VDEF. 
 Subtype is in the fourth ^-piece.  
VARIABLES: MSGEVT                       TYPE: Input
 VARIABLES DESCRIPTION:   HL7 event = "A31" for Update Person Information.  
VARIABLES: $$BUILD                      TYPE: Output
 VARIABLES DESCRIPTION:   "LM" if the message is in the OUT() array.  "GM" if
 message is in ^TMP("HLS",$J).  
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4782                            IA #: 4782
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: AUG 31, 2005            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CLINIC PHONE
  ID: SC(
GLOBAL REFERENCE: SC(D0,99)
FIELD NUMBER: 99                        FIELD NAME: TELEPHONE
  LOCATION: 99;1                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Telephone number for specific location.  FREE TEXT 
 GENERAL DESCRIPTION:   
    The purpose of this agreement is to allow access to TELEPHONE field #99, of
 the HOSPITAL LOCATION file #44.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TELEPHONE
KEYWORDS: CLINIC PHONE
KEYWORDS: HOSPITAL LOCATION
SUBSCRIBING PACKAGE: MYHEALTHEVET
 SUBSCRIBING DETAILS:   The My HealtheVet project would like access to the
 TELEPHONE field #99, in the HOSPITAL LOCATION file #44.  This field is not
 provided by the SDAMA301 API, but the location IEN is provided.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   ICR 4782 replaces the previous subscription of
 Radiology/Nuclear Medicine to the Clinic Phone number in ICR 1335, where ICR
 1335 is retired.  

NUMBER: 4783                            IA #: 4783
  DATE CREATED: AUG 18, 2005
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMRAFX
  NAME: ADD COMMENT                     ID: GMRAFX
 GENERAL DESCRIPTION:   The NDF application is forced to clean up some entries
 in ART files because of a problem with locally added entries to the DRUG
 INGREDIENTS file (#50.416).  ART developers asked that we call and entry in
 their package to make a note that changes werew made by an NDF patch.  To that 
 end we request permission to call ADCOM^GMRAFX.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ADCOM
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
 SUBSCRIBING DETAILS:   
  

NUMBER: 4784                            IA #: 4784
  DATE CREATED: AUG 18, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMVMHV
  NAME: GMVMHV                          ID: GMVMHV
 GENERAL DESCRIPTION:   The MyHealtheVet package requests permission to
 retrieve patient vitals/measurements data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MyHealtheVet
COMPONENT/ENTRY POINT: EN(GMVDFN,GMVSTART,GMVEND,GMVVT,GMVERR)
 COMPONENT DESCRIPTION:   This entry point returns patient vitals/measurements
 data (FILE 120.5). 
VARIABLES: GMVDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   The patient identification number (aka DFN) from the
 PATIENT (#2) file. (Required) 
VARIABLES: GMVSTART                     TYPE: Input
 VARIABLES DESCRIPTION:   The date to begin the search. It must be in FileMan
 internal format (e.g., 3050818). The date is optional. Time may be entered,
 but is optional. If time is entered, it must be in FileMan internal format
 (e.g., 3050818.08), too. If no date/time is entered, the date/time of the very
 first record for the patient is used.  
VARIABLES: GMVEND                       TYPE: Input
 VARIABLES DESCRIPTION:   The date to end the search. It must be in FileMan
 internal format (e.g., 3050818). This value is optional. Time may be entered,
 but is optional. If time is entered, it must be in FileMan internal format
 (e.g., 3050818.08), too. If a date is entered, but not a time, then '235959'
 is used for the time. The default is the current date/time.  
VARIABLES: TMP($J,'GMVMHV')             TYPE: Output
 VARIABLES DESCRIPTION:   Returns patient record data from the GMRV VITAL
 MEASUREMENT (#120.5) file.  
  
 Output: ^TMP($J,"GMVMHV",0)=piece1^piece2 
   where piece 1 = the number of records returned or "-1" if an error was 
                   found 
         piece 2 = an error message if piece 1 is "-1" 
  
          
   ^TMP($J,"GMVMHV",n)=piece1^piece2^piece3^piece4^piece5^piece6^ 
                       piece7^piece8^piece9 
    where n = is the internal entry number of the FILE 120.5 entry 
  
    piece 1 = DATE/TIME VITALS TAKEN (.01) 
          2 = VITAL TYPE (.03) 
          3 = DATE/TIME VITALS ENTERED (.04) 
          4 = HOSPITAL LOCATION (.05) 
          5 = RATE (1.2) 
          6 = SUPPLEMENTAL O2 (1.4) 
          7 = ENTERED IN ERROR (2) 
          8 = REASON ENTERED IN ERROR (4) (multiple values separated by 
              tilde) 
          9 = QUALIFIER (5) (multiple values separated by tilde) 
  
     pieces 1 and 3 are internal values. pieces 2,4-9 are external values 
  
 Example: 
  
  > S GMVDFN=134,GMVSTART=3051201,GMVEND=3060101,GMVVT="WT^HT",GMVERR=1 
  > D EN^GMVMHV(GMVDFN,GMVSTART,GMVEND,GMVVT,GMVERR) 
  > D ^%G 
  > Global ^TMP($J,"GMVMHV" 
  > ^TMP(539290429,"GMVMHV",0)=2 
                            9538)=3051219.1709^WEIGHT^3051219.170941^ 
                                  2-ASM^135^^^^ACTUAL~STANDING 
                            9539)=3051219.1709^HEIGHT^3051219.170941^ 
                                  2-ASM^67.5^^^^ACTUAL 
VARIABLES: GMVVT                        TYPE: Input
 VARIABLES DESCRIPTION:   This is a list of vital type abbreviations from FILE
 120.51, Field 1) separated by an uparrow (e.g., HT^WT). 
  
 The default is "P^T^R^P^HT^WT^CVP^CG^PO2^PN".  
VARIABLES: GMVERR                       TYPE: Input
 VARIABLES DESCRIPTION:   This value indicates if the user wants records that
 were marked as entered-in-error. (Optional). '1' means "Yes" and '0' (zero)
 means "No" (i.e., don't return entered-in-error records). '0' is the default.  
SUBSCRIBING PACKAGE: MYHEALTHEVET

NUMBER: 4785                            IA #: 4785
  FILE NUMBER: 355.33                   GLOBAL ROOT: IBA(355.33,
  DATE CREATED: AUG 25, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INSURANCE BUFFER FILE ACCESS
  ID: IBA(355.33,
GLOBAL REFERENCE: IBA(355.33,
FIELD NUMBER: ALL                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Many fields across most the global nodes are accessed.  
  
GLOBAL REFERENCE: IBA(355.33,D0,90)
FIELD NUMBER: 90.01                     FIELD NAME: GROUP NAME
  LOCATION: 90;1                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   IB*2*497 replaced GROUP NAME field at 355.33, 40.02
 location.  
FIELD NUMBER: 90.02                     FIELD NAME: GROUP NUMBER
  LOCATION: 90;2                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   IB*2*497 replaced GROUP NUMBER field at 355.33,40.03
 location.  
FIELD NUMBER: 90.03                     FIELD NAME: SUBSCRIBER ID
  LOCATION: 90;3                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   IB*2*497 replaced SUBSCRIBER ID field at 355.33,60.04
 location.  
GLOBAL REFERENCE: IBA(355.33,D0,91)
FIELD NUMBER: 91.01                     FIELD NAME: NAME OF INSURED
  LOCATION: 91;1                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   IB*2*497 replaced NAME OF INSURED field at 355.33,60.07
 location.  
 GENERAL DESCRIPTION:   Access to the Insurance Buffer file (#355.33) is
 granted solely for the purpose of creating HL7 messages for the PFSS project.  
  
 Update: IB*2*497 increased the length of the SUBSCRIBER ID field, NAME OF 
 INSURED field, GROUP NAME, 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 4 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
KEYWORDS: IN1
KEYWORDS: IN2
KEYWORDS: IN3
KEYWORDS: PFSS
SUBSCRIBING PACKAGE: REGISTRATION
  DATE ACTIVATED: FEB 21, 2014

NUMBER: 4786                            IA #: 4786
  FILE NUMBER: 370                      GLOBAL ROOT: IBBFP(370,
  DATE CREATED: AUG 25, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PATIENT FSC FILE ACCESS
  ID: IBBFP(370,
GLOBAL REFERENCE: IBBFP(370,
FIELD NUMBER: ALL                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Many fields from throughout the file are available for
 direct access.  
 GENERAL DESCRIPTION:   Access to the Patient FSC File (#370) is granted solely
 for the purpose of creating an HL7 message for the PFSS project.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: INSURANCE
KEYWORDS: IN1
KEYWORDS: IN2
KEYWORDS: IN3
KEYWORDS: PFSS
KEYWORDS: FSC
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4787                            IA #: 4787
  FILE NUMBER: 370.1                    GLOBAL ROOT: IBBFM(370.1
  DATE CREATED: AUG 25, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VISTA FSC FILE ACCESS
  ID: IBBFM(370.1
GLOBAL REFERENCE: IBBFM(370.1,
FIELD NUMBER: ALL                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Access to all fields on the 0-node.  
 GENERAL DESCRIPTION:   Access to the VISTA FSC File (#370.1) is granted solely
 for the purpose of building HL7 messages for the PFSS project.  
  STATUS: Active
KEYWORDS: IN1
KEYWORDS: PFSS
KEYWORDS: INSURANCE
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4788                            IA #: 4788
  FILE NUMBER: 370.2                    GLOBAL ROOT: IBBFM(370.2,
  DATE CREATED: AUG 25, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: COMMERCIAL INSURANCE FILE ACCESS
  ID: IBBFM(370.2,
GLOBAL REFERENCE: IBBFM(370.2,
FIELD NUMBER: ALL                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Access to all fields.  
 GENERAL DESCRIPTION:   Access to the Commercial Insurance File (#370.2) is
 granted for the sole purpose of building HL7 messages for the PFSS project.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IN3
KEYWORDS: IN1
KEYWORDS: IN2
KEYWORDS: PFSS
KEYWORDS: INSURANCE
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4789                            IA #: 4789
  FILE NUMBER: 370.3                    GLOBAL ROOT: IBBFM(370.3,
  DATE CREATED: AUG 25, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PFSS PLAN FILE ACCESS
  ID: IBBFM(370.3,
GLOBAL REFERENCE: IBBFM(370.3,
FIELD NUMBER: ALL                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Access is granted to all fields.  
 GENERAL DESCRIPTION:   Access is granted to the PFSS Plan File (#370.3) for
 the sole purpose of building HL7 messages for the PFSS project.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IN1
KEYWORDS: PFSS
KEYWORDS: INSURANCE
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4790                            IA #: 4790
  FILE NUMBER: 370.4                    GLOBAL ROOT: IBBFM(370.4,
  DATE CREATED: AUG 25, 2005            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBBFINS
  NAME: PFSS INSURANCE STATUS UPDATE    ID: IBBFINS
GLOBAL REFERENCE: IBBFM(370.4,D0,0
FIELD NUMBER: ALL                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Access to all fields is granted.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PFSS
KEYWORDS: INSURANCE
KEYWORDS: 355.33
KEYWORDS: INSURANCE BUFFER
COMPONENT/ENTRY POINT: PREP(IEN)
 COMPONENT DESCRIPTION:   The STATUS Field (#.04) of the Insurance Buffer File
 (#355.33) tracks the processing progress of the entry.  As an HL7 message is
 being created, the status is updated and time-stamped by the PREP^IBBFINS API. 
 The API updates the status to "P".  This call is made from the message
 creation code.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the File #355.33 entry to be updated.  
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4791                            IA #: 4791
  DATE CREATED: DEC 20, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMVHS
  NAME: GMVHS                           ID: GMVHS
 GENERAL DESCRIPTION:   This routine will return vital/measurement data for a
 patient over a given date/time range.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   Returns data for the patient and date range
 specified.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient (#2) file internal entry number. (Required) 
VARIABLES: GMRVSTR                      TYPE: Input
 VARIABLES DESCRIPTION:   The types of vital/measurments desired. Use the
 abbreviation found in the Vital Type (#120.51) file. For multiple vitals, use
 the semi-colon (;) as a delimiter (e.g., "T;P;R;BP"). (Required) 
VARIABLES: GMRVSTR(0)                   TYPE: Input
 VARIABLES DESCRIPTION:   GMRVSTR(0) = is a 4 part value. (REQUIRED) 
   GMRVSTDT^GMRVENDT^GMRVOCC^GMRVSORD 
      
  where GMRVSTDT = The start date/time that the utility will use in 
                   obtaining patient data. (Required) 
        GMRVENDT = The end date/time that the utility will use to stop the 
                   search.  (Required) 
        GMRVOCC = The number of occurrences of the data that is desired by 
                  the search.  (Required) 
        GMRVSORD = The sort order desired in the output. O will sort the 
                   data by vital type, then by date/time entered. 1 will 
                   sort the data by date/time entered, then vital type.  
                   (Required) 
VARIABLES: GMRVSTR('LT')                TYPE: Input
 VARIABLES DESCRIPTION:   
  GMRVSTR("LT") = ^TYP1^[TYP2^...]  (OPTIONAL) 
  
 This variable is a caret (^) delimited list of hospital location types to 
 extract measurement data for. For example, "^C^" will extract data for only
 those measurements taken in clinics.  
VARIABLES: UTILITY($J,'GMRVD',          TYPE: Output
 VARIABLES DESCRIPTION:   This is a global array.  
  
 The array structure will be as follows if '$P(GMRVSTR,"^",4): 
 ^UTILITY($J,"GMRVD",GMRVTYP,GMRVRDT,GMRVIEN)=GMRVDATA or if $P(GMRVSTR,"^",4)
 then the following will be returned: 
 ^UTILITY($J,"GMRVD",GMRVRDT,GMRVTYP,GMRVIEN)=GMRVDATA 
  
  where GMRVRDT  = Reverse FileMan date/time.  
                   9999999-Date/time vital/measurement was taken.  
        GMRVTYP  = The abbreviation used in the GMRVSTR string for the type 
                   of vital/measurment taken.  
        GMRVIEN  = Entry number in file Vital/Measurement (#120.5) file.  
        $P(GMRVDATA,"^",1) = date/time of the reading (FileMan internal) 
        $P(GMRVDATA,"^",2) = Patient (#2) number (i.e., DFN) 
        $P(GMRVDATA,"^",3) = vital type ien (File 120.51) 
        $P(GMRVDATA,"^",4) = date/time of data entry (FileMan internal) 
        $P(GMRVDATA,"^",5) = hospital location ien (File 44) 
        $P(GMRVDATA,"^",6) = user ien (File 200) 
        $P(GMRVDATA,"^",7) = always null 
        $P(GMRVDATA,"^",8) = reading (e.g., 98.6, Unavailable) 
        $P(GMRVDATA,"^",9) = always null 
        $P(GMRVDATA,"^",10) = first qualifier 
        $P(GMRVDATA,"^",11) = second qualifier 
        $P(GMRVDATA,"^",12)= "*" for abnormal measurement, otherwise = 
                             "" (i.e., null) 
        $P(GMRVDATA,"^",13)= values in centigrade for T; kilos for WT; 
                             centimeters for HT and Circumference/Girth; 
                             and mmHg for CVP 
        $P(GMRVDATA,"^",14)= Body Mass Index value 
        $P(GMRVDATA,"^",15)= L/Min of supplemental O2 
        $P(GMRVDATA,"^",16)= % of supplemental O2 
        $P(GMRVDATA,"^",17)= all qualifiers delimited by semi-colons 
  
 Example: 
  
  > S DFN=134,GMRVSTR="T;P;R;BP;PN"       
  > S GMRVSTR(0)="3051001^3051031^10^0" 
  > D EN1^GMVHS  
  > D ^%G 
  > Global ^UTILITY($J,"GMRVD" 
 ^UTILITY(539013315,"GMRVD","BP",6948978.855248,8961)=3051020.144752^134^1 
 ^3051020.145023^87^547^^128/81^^L ARM^SITTING^*^^^^^L ARM;SITTING 
 ^UTILITY(539013315,"GMRVD","P",6948978.855248,8965)=3051020.144752^134^5^ 
 3051020.145023^87^547^^44^^CAROTID^SITTING^^^^^^CAROTID;SITTING;PALPATED 
 ^UTILITY(539013315,"GMRVD","PN",6948978.855248,8964)=3051020.144752^134^22 
 ^3051020.145023^87^547^^0^^^^^^^^^ 
 ^UTILITY(539013315,"GMRVD","R",6948978.855248,8967)=3051020.144752^134^3^ 
 3051020.145023^87^547^^60^^SPONTANEOUS^SITTING^*^^^^^SPONTANEOUS;SITTING 
 ^UTILITY(539013315,"GMRVD","T",6948978.855248,8968)=3051020.144752^134^2^ 
 3051020.145023^87^547^^98.6^^ORAL^^^37.0^^^^ORAL 
SUBSCRIBING PACKAGE: HEALTH SUMMARY
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4792                            IA #: 4792
  DATE CREATED: AUG 31, 2005
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUSRVA
  NAME: DBIA4792                        ID: TIUSRVA
 GENERAL DESCRIPTION:   This IA is used to document the usage of entry point 
 CANDO^TIUSRVA by Clinical Procedures.  Clinical Procedures uses this entry
 point to evaluate the prilvilege of a user before allowing the text of the CP
 document be viewed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CANDO(Y,TIUDA,TIUACT)
 COMPONENT DESCRIPTION:   This entry point evaluates the user prilvilege for a
 TIU document.  
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   This variable will return a 1:yes,0:no_"^"_why not
 message.  
  
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   The TIU document internal entry number.  
VARIABLES: TIUACT                       TYPE: Input
 VARIABLES DESCRIPTION:   The action that needs evaluation.  
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES

NUMBER: 4793                            IA #: 4793
  DATE CREATED: SEP 12, 2005            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: WVRALINK
  NAME: WVRALINK                        ID: WVRALINK
 GENERAL DESCRIPTION:   The Radiology/NM package will call the Women's Health
 package whenever a Radiology report is verified or deleted.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CREATE(DFN,DATE,CASE)
 COMPONENT DESCRIPTION:   This entry point is for the Radiology/NM package
 which will provide the Women's Health package with the subscript values needed
 to look up a record in the RAD/NUC MED PATIENT (#70) file. The Radiology/NM
 package will call this entry point when a radiology report is verfied.  
  
 CREATE(DFN,DATE,CASE) will use the parameter values to look up 
 ^RADPT(DFN,"DT",DATE,"P",CASE,0) 
  
 Example: CREATE(134,6998995.8948,1) will be used to look up 
 ^RADPT(134,"DT",6998995.8948,"P",1,0) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the NAME (#.01) value of the RAD/NUC MED
 PATIENT (#70) file. It is the patient's internal entry number (FILE #2, #.01
 Field). (Required).  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the EXAM DATE (#.01) value of the REGISTERED
 EXAMS (#2) multiple field of the RAD/NUC MED PATIENT (#70) file. The value is
 in FileMan internal format and in inverse form (e.g.,
 9999999.9999-3050912.1051).  (Required) 
VARIABLES: CASE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the CASE NUMBER (#.01) pointer value of the
 EXAMINATIONS (#3) multiple field of the RAD/NUC MED PATIENT (#70) file.
 (Required).  
COMPONENT/ENTRY POINT: DELETE(DFN,DATE,CASE)
 COMPONENT DESCRIPTION:   This entry point is for the Radiology/NM package
 which will provide the Women's Health package with the subscript values needed
 to look up a record in the RAD/NUC MED PATIENT (#70) file. The Radiology/NM
 package will call this entry point when a radiology report is deleted.  
  
 CREATE(DFN,DATE,CASE) will use the parameter values to look up  
 ^RADPT(DFN,"DT",DATE,"P",CASE,0) 
  
 Example: CREATE(134,6998995.8948,1) will be used to look up 
 ^RADPT(134,"DT",6998995.8948,"P",1,0) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the NAME (#.01) value of the RAD/NUC MED
 PATIENT (#70) file. It is the patient's internal entry number (FILE #2, #.01
 Field). (Required).  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the EXAM DATE (#.01) value of the REGISTERED
 EXAMS (#2) multiple field of the RAD/NUC MED PATIENT (#70) file. The value is
 in FileMan internal format and in inverse form (e.g.,
 9999999.9999-3050912.1051).  (Required) 
VARIABLES: CASE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the CASE NUMBER (#.01) pointer value of the
 EXAMINATIONS (#3) multiple field of the RAD/NUC MED PATIENT (#70) file.
 (Required).  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 4794                            IA #: 4794
  FILE NUMBER: 71                       GLOBAL ROOT: RAMIS(71,
  DATE CREATED: OCT 12, 2005
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RA PROCEDURES FILE TEMPORARY READ
  ID: RAMIS(71,
GLOBAL REFERENCE: RAMIS(71,D0,4,
FIELD NUMBER: .01                       FIELD NAME: DESCENDENTS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: RAMIS(71,D0,"CM",
FIELD NUMBER: .01                       FIELD NAME: CONTRAST MEDIA
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This integration agreement is meant to allow the post
 install of OR*3.0*240 to read the RAD/NUC MED PROCEDURES File in order to
 update the ORDERABLE ITEMS File with the correct CONTRAST MEDIA codes.  
  
  STATUS: Active                        EXPIRATION DATE: NOV 14, 2005
KEYWORDS: ORDERABLE ITEMS
KEYWORDS: CONTRAST MEDIA
KEYWORDS: RAD/NUC MED PROCEDURES
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4795                            IA #: 4795
  DATE CREATED: SEP 22, 2005
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUSRVP2
  NAME: DBIA4795                        ID: TIUSRVP2
 GENERAL DESCRIPTION:   Entry points in this routine (TIUSRVP2) are used for
 signing and addending TIU documents.  This agreement overlaps with IA 3535,
 for routine TIUSRVP. Routine TIUSRVP was split in patch TIU*1*184, with
 components MAKEADD and SIGN moved to TIUSRVP2. Variables and code have not
 changed, just the routine. As of TIU*1*184, MAKEADD^TIUSRVP and SIGN^TIUSRVP
 call their counterparts in TIUSRVP2. This means it will be more efficient to
 call MAKEADD and SIGN directly from TIUSRVP2 when TIU*1*184 is released.  This
 agreement grants that permission.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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 of MAKEADD^TIUSRVP when editing existing code or writing new code. It
 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 of SIGN^TIUSRVP when editing or writing new code.  Only the routine is 
 changed.  
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN in 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.  
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.  
SUBSCRIBING PACKAGE: SURGERY
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
SUBSCRIBING PACKAGE: CARE MANAGEMENT
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 4/25/24 effective with patch PSO*7*746. The
 Outpatient Pharmacy Meds By Mail team is working on an enhancement to create
 an addendum to the existing TIU document.  

NUMBER: 4796                            IA #: 4796
  FILE NUMBER: 8925                     GLOBAL ROOT: TIU(8925,DA,0)
  DATE CREATED: SEP 21, 2005
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4796
  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 integration agreement documents the fact that
 Clinical Procedures has a field called NEW TIU DOCUMENT IEN (#.03) in
 sub-file, CONVERSION LOG (#703.92), in the CP CONVERSION file (#703.9) stores
 the internal entry nuumber of the Medicine Report converted note in the TIU
 DOCUMENT file (#8925).  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES

NUMBER: 4797                            IA #: 4797
  FILE NUMBER: 8984.4                   GLOBAL ROOT: XT(8984.4,
  DATE CREATED: SEP 21, 2005            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Controlled Subscription        TYPE: File
  NAME: MTLU Setup for Code Sets        ID: XT(8984.4,
GLOBAL REFERENCE: XT(8984.4,<file>,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,<file>,1)
FIELD NUMBER: .02                       FIELD NAME: DISPLAY PROTOCOL
  LOCATION: 1;E1,20                     ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   The Lexicon Utility needs to write to the Kernel
 Toolkit Multi-Term Look-up Utility's (MTLU) files during a KIDS
 install/post-init.  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: MTLU
KEYWORDS: LEXICON
KEYWORDS: CODE SETS
SUBSCRIBING PACKAGE: LEXICON UTILITY
 SUBSCRIBING DETAILS:   This IA supersedes previous IA #346, #856 and 887,
 originally written to support the Clinical Lexicon Utility v 1.0 (in the GMPT
 namespace).  The updated agreement will support Code Sets as implemented in
 the Lexicon Utility v 2.0 (in the LEX namespace). The Lexicon Utility is 
 responsible for the ICD Code Sets and the CPT Code Sets in files 757.01, 80,
 80.1, and 81.  
  

NUMBER: 4798                            IA #: 4798
  DATE CREATED: DEC 15, 2010            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VAFC NEW NC TREATING FACILITY
 GENERAL DESCRIPTION:   
  This Remote Procedure Call will be used by the North Chicago 
  Common Registration User Interface (UI).  Given a patient DFN 
  and DOD EDIPI, the RPC adds an active Department of Defense 
  correlation to the VistA TREATING FACILITY LIST (#391.91) 
  file if it does not exist.  
   
  It returns a list of Treating Facilities, including Source 
  Identifier, Identifier Type, Assigning Authority, Assigning 
  Facility, Identifier Status, and an indicator if the entry 
  was entered into File 391.91.  
  TAG: NEWTF                 ROUTINE: VAFCTFU2 
   
  INPUT PARAMETER: Vista Patient Identifier 
  Vista Patient Identifier will be the PATIENT (#2) file 
  IEN (aka DFN).  Example: DFN="7168937" 
   
  INPUT PARAMETER: DOD Identifier 
  The DOD Identifier will be EDIPI data in this format: 
   
  Id^IdType^AssigningAuthority^AssigningFacility 
   
  Example: EDIPI="852043888^NI^USDOD^200DOD" 
    
    
  This API returns a list of Treating Facilities in this 
  format: 
    
  Id^IdType^AssigningAuthority^AssigningFacility^IdStatus[^NEW] 
    
  Examples: 
  RESULT(1)="7168937^PI^USVHA^500^A" 
  RESULT(2)="1^NI^USDOD^200DOD^A^NEW" 
   
  Note: If there is data in the 6th piece of the RESULT(<number>), 
        with data value as "NEW", then it means that the entry 
        was newly created in the TREATING FACILITY LIST (#391.91) 
        file by this RPC call.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
  DATE ACTIVATED: JAN 14, 2011

NUMBER: 4799                            IA #: 4799
  DATE CREATED: SEP 23, 2005            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FBRVU
  NAME: IA4799                          ID: FBRVU
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RVU
COMPONENT/ENTRY POINT: $$RVU(FBCPT,FBMOD,FBDATE)
VARIABLES: FBCPT                        TYPE: Input
 VARIABLES DESCRIPTION:   (Requred) CPT code, external value 
VARIABLES: FBMOD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) CPT modifier. Can be a string of CPT code
 specific modifiers delimited by commas.  
VARIABLES: FBDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Exam date/time in FileMan format. If null
 then today's date becomes the assumed date.  
VARIABLES: $$RVU                        TYPE: Output
 VARIABLES DESCRIPTION:   Output: 
  returns a string RETSTATUS^VALUE^MESSAGE 
  where: 
  
  If the CPT/CPT+CPT modifier was found for the date or date/time specified
 then: 
  RETSTATUS = 1, 
  VALUE = (#.03) WORK RELATIVE VALUE UNIT of file #162.97, 
  MESSAGE = null.  
  
  If the CPT/CPT+CPT modifier was NOT found for the date or date/time specified
 then: 
  RETSTATUS = 0, 
  VALUE = null, 
  MESSAGE = "CPT/MOD not found" 
  
  If the date specified in FBDATE is invalid then: 
  RETSTATUS = 0, 
  VALUE = null, 
  MESSAGE = "Valid date not specified" 
  
  If the CPT modifiers listed in FBMOD cannot be used together 
  to determine correct RVU value then: 
  RETSTATUS = 0, 
  VALUE = null, 
  MESSAGE = "Wrong CPT modifiers combination" 
  
  If the database is not available at the time of the request then: 
  RETSTATUS = -1, 
  VALUE = null, 
  MESSAGE = "Database Unavailable" 
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  DATE ACTIVATED: MAY 16, 2007

NUMBER: 4800                            IA #: 4800
  DATE CREATED: SEP 23, 2005            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGUTL
  NAME: EMERGENCY RESPONSE INDICATOR    ID: DGUTL
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$EMGRES(DFN)
 COMPONENT DESCRIPTION:   Returns the value of the Emergency Response Indicator 
 (Patient file 2, field .181), or null if blank.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the Patient file 2.  
VARIABLES: $$EMGRES                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns value from the EMERGENCY RESPONSE INDICATOR
 field or null if blank.  
  
 Current possible values: 
  'P' for Pandemic 
  DATE ACTIVATED: APR 08, 2020

NUMBER: 4801                            IA #: 4801
  DATE CREATED: OCT 05, 2005
  CUSTODIAL PACKAGE: HEALTH DATA & INFORMATICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HDISVAP
  NAME: DBIA4801                        ID: HDISVAP
 GENERAL DESCRIPTION:   Within the Lab Data file (#63), is the Microbiology
 multiple (field #5, subfile #63.05), and within that is the Organism multiple
 (field #12, subfile #63.3) for microbiology organisms.  This in turn contains
 site specific fields (created by the option LRWU7 - Add a new internal name
 for an antibiotic) for antibiotics associated with the organism.  There are 
 values associated with the antibiotic that meet the criteria for being 
 described as a set of codes: 
              
 Value             Description 
 ----------------  -------------------------------------------------------
 ALWAYS DISPLAY    Always display the result.  
  
 NEVER DISPLAY     Never display the result unless the user has the LRLAB 
                   key that indicates user is laboratory personnel.  
  
 RESTRICT DISPLAY  Result is only displayed if the interpretation of 
                   all antibiotics that are always displayed is resistant.  
  
 Although the set of codes has been assigned VHA Unique Identifier (VUID), new
 antibiotics can be entered into VistA by a facility.  The new antibiotics are
 dynamically assigned field numbers and would not automatically find
 translation to a VUID.  
  
 Since this is a rare exception and one not felt to jeopardize the integrity of
 the VUID model, DS proposes to handle the translation of these site specific
 fields and provide APIs for the Lab application to use when converting to/from
 a VUID.  This will allow for more expediency if changes are needed and ensure
 that new entries are assigned VUIDs that are interpretable by the HDR.  This
 DBIA contains the APIs.  
  STATUS: Active
KEYWORDS: DATA STANDARDIZATION
COMPONENT/ENTRY POINT: $$LOSVUID(CODE)
 COMPONENT DESCRIPTION:   Convert Lab's Organism Screen set of codes to VUID 
   
 Example: 
  
 >W $$LOSVUID^HDISVAP("A") 
  
 4500665 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Code representing organism screen 
VARIABLES: $$LOSVUID                    TYPE: Output
 VARIABLES DESCRIPTION:   VUID for input code 
  
 NULL returned on bad input 
COMPONENT/ENTRY POINT: $$LOSCODE(VUID)
 COMPONENT DESCRIPTION:   Convert Lab's Organism Screen VUID to set of codes 
  
 Example: 
  
 >W $$LOSCODE^HDISVAP(4500665) 
  
 A 
VARIABLES: VUID                         TYPE: Input
 VARIABLES DESCRIPTION:   VUID representing organism screen 
VARIABLES: $$LOSCODE                    TYPE: Output
 VARIABLES DESCRIPTION:   Code for input VUID 
  
 NULL returned on bad input 
SUBSCRIBING PACKAGE: LAB SERVICE

NUMBER: 4802                            IA #: 4802
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870,
  DATE CREATED: MAR 31, 2006            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HL7 LOGICAL LINK UPDATE
  ID: HLCS(870,
GLOBAL REFERENCE: HLCS(870,D0,
FIELD NUMBER: 200.02                    FIELD NAME: RE-TRANSMISSION ATTEMPTS
  LOCATION: 200;2                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 200.04                    FIELD NAME: READ TIMEOUT
  LOCATION: 200;4                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 200.05                    FIELD NAME: ACK TIMEOUT
  LOCATION: 200;5                       ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 200.021                   FIELD NAME: EXCEED RE-TRANSMIT ACTION
  LOCATION: 200;10                      ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 400.01                    FIELD NAME: TCP/IP ADDRESS
  LOCATION: 400;1                       ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This DBIA is used to authorize the Order Entry Package
 to directly set the fields of a HL7 Logical Link in file 870.  The need for
 this arrises from the finding that KIDS does not update these fields when a
 Logical Link is sent as a component.  
  
  STATUS: Active
KEYWORDS: logical
KEYWORDS: LINK
KEYWORDS: HL7
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   ADDED 6/2/2010 

NUMBER: 4803                            IA #: 4803
  DATE CREATED: SEP 29, 2005
  CUSTODIAL PACKAGE: PHARMACY BENEFITS MANAGEMENT
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSUHL
  NAME: PSUHL USAGE                     ID: PSUHL
 GENERAL DESCRIPTION:   The purpose of this integration agreement is to record
 usage of the routine PSUHL. PSUHL is used to make entries in a retransmission
 queue to allow Pharmacy Benefits Management (PBM) extracts to retransmit only 
 those patient demographics for patients who have had data updated.  
  STATUS: Active
KEYWORDS: PSUHL
COMPONENT/ENTRY POINT: LOGDFN
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the patient for which
 demographics have been updated.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS

NUMBER: 4804                            IA #: 4804
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870,
  DATE CREATED: OCT 05, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PSU SEND
  ID: HLCS(870,
 GENERAL DESCRIPTION:   Pharmacy Benefit Management is permitted to distribute
 via KIDS the PSU SEND entry in the HL Logical Link file (#870). To do so, it
 may: 
  
  1) Use the "B" cross-reference to find the "PSU SEND" entry's ien.  
  2) Read existing entries in the file, all fields.  
  3) Create a new entry whose .01 field is "PSU SEND", on condition that it 
    does not already exist.  
  4) Overwrite an existing entry whose .01 field is "PSU SEND".  
  5) The record must be updated or created via Fileman. 
  
  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 30, 2006
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT

NUMBER: 4805                            IA #: 4805
  FILE NUMBER: 779.2                    GLOBAL ROOT: HLD(779.2,
  DATE CREATED: OCT 05, 2005            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HLO APPLICATION REGISTRY
  ID: HLD(779.2,
 GENERAL DESCRIPTION:   Permission is given for any application to create new
 entries in the HLO Application Registry file and distribute those entries via
 KIDS, under these conditions: 
  
  1) The .01 field must be namespaced by the application. It is the
 application's responsibility to insure that their entry is uniquely named.  
  
  2) The entry must be distributed via KIDS by selecting HLO APPLICATION
 REGISTRY from the Build Components screen of the Edit a Build option.  
  
  3) Select the entry you want to distribute and select an action: SEND TO SITE
 or DELETE AT SITE.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HL7
  DATE ACTIVATED: OCT 05, 2005

NUMBER: 4806                            IA #: 4806
  FILE NUMBER: 1.1                      GLOBAL ROOT: DIA(
  DATE CREATED: DEC 20, 2010            CUSTODIAL PACKAGE: 1
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ADD TEMPLATES TO AUDIT FILE
  ID: DIA(
 GENERAL DESCRIPTION:   LAB SERVICE has been approved to add a sort and two
 print templates to the AUDIT file (#1.1) to print/display audited entries.  
  
 The templates are: 
   Sort template: LRJ SYS DISPLAY FILE 60 CHANGE 
  Print template: LRJ SYS DISPLAY FILE 60 CHANGE 
  Print Template: LRJ SYS GET INDIRECT AUDIT 
  
 They both run off the LABORATORY TEST file (#60) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LAB
KEYWORDS: AUDIT
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: JUN 04, 2013

NUMBER: 4807                            IA #: 4807
  DATE CREATED: OCT 05, 2005            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGRPDB
  NAME: API FOR RATED DISABILITIES      ID: DGRPDB
 GENERAL DESCRIPTION:   This agreement covers an API which will return, in an
 array, the six fields of the Rated Disabilities multiple from the Patient
 file.  The multiple is 2.04, field number .372.  The array will also return
 the disabilities in descending Service Connected percent.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RATED DISABILITIES
COMPONENT/ENTRY POINT: RDIS(DGDFN,.DGARR)
VARIABLES: DGDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Patient file.  
VARIABLES: DGARR                        TYPE: Both
 VARIABLES DESCRIPTION:   Array name in which the disabilities information will
 be returned.  

NUMBER: 4808                            IA #: 4808
  FILE NUMBER: 38.1                     GLOBAL ROOT: DGSL(38.1
  DATE CREATED: DEC 28, 2010            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DG SECURITY LOG SECURITY LEVEL
  ID: DGSL(38.1
GLOBAL REFERENCE: DGSL(38.1,DA,0)
FIELD NUMBER: 2                         FIELD NAME: SECURITY LEVEL
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Alias Comparison Tool (ACT) in the Laboratory
 System Re-Engineering Project (LSRP) uses FileMan Database Server (DBS) API
 calls to read the Security Level field (#2) in the DG Security Log (#38.1)
 file.  
  
 1) The following FileMan DBS API is used to determine if the value, LRCVAL,
 being passed in from a COTS Lab Information Management System (LIMS) is a
 valid value for the Security Level Field (#2): 
  
     D CHK^DIE(38.1,2,"E",LRCVAL,.LRVAL) where LRCVAL is 0 or 1 
  
     Example: 
  
     >S LRCVAL=1                          
  
     > D CHK^DIE(38.1,2,"E",LRCVAL,.LRVAL) 
  
     >W LRVAL 
      1 
  
 2) The following FileMan DBS API is used to get the Security Level Field (#2)
 definition: 
  
    $$GET1^DID(38.1,2,"","POINTER") 
  
    Example: 
  
    >S LRFLDEF=$$GET1^DID(38.1,2,"","POINTER") 
  
    >W LRFLDEF                                
     0:NON-SENSITIVE;1:SENSITIVE; 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LSRP
KEYWORDS: ACT
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: JAN 05, 2011

NUMBER: 4809                            IA #: 4809
  FILE NUMBER: 8985.1                   GLOBAL ROOT: XTID(8985.1,
  DATE CREATED: OCT 12, 2005            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4809
  ID: XTID(8985.1,
GLOBAL REFERENCE: XTID(8985.1,'A')
 GLOBAL DESCRIPTION:   Direct Global Read - Primary Key 
GLOBAL REFERENCE: XTID(8985.1,D1,'TERMSTATUS','B',Date,D0)
 GLOBAL DESCRIPTION:   Direct Global Read - IEN of Multiple 
 GENERAL DESCRIPTION:   This DBIA is a one time request to permit the HDI
 application to scan the EFFECTIVE DATE/TIME Multiple (subfile #8985.11) of the
 XTID VUID FOR SET OF CODES file (#8985.1) for consecutive storage of the same
 status using a Direct Global Read.  The M code is in the routine HDI1002A
 which is being invoked in the post-installation of patch HDI*1.0*2.  If a
 duplicate status entry is found, the FileMan M routine ^DIK is used to delete
 the EFFECTIVE DATE/TIME multiple entry. The HDI1002A routine can be deleted 
 after the patch is successfully installed.  This is a one time request since
 future updates to the file will not result in redundant status entries being
 created.  
  STATUS: Active
KEYWORDS: DATA STANDARDIZATION
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS

NUMBER: 4810                            IA #: 4810
  DATE CREATED: OCT 11, 2005
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: MPIF OPTIONS/MENUS ON CIRN MENUS
 GENERAL DESCRIPTION:   
  MPI is requesting to place some options/menus on CIRN namespaced Menus.  
  This request replaces IA #2717 which is out-of-date.  
       
  MPIF CMOR MGR on the RG ADMIN USER MENU 
  MPIF SITE PARAMETER on the RG ADMIN COORD MENU 
  MPIF DISPLAY ONLY QUERY TO MPI on the RG EXCEPTION MENU 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA

NUMBER: 4811                            IA #: 4811
  DATE CREATED: OCT 26, 2005            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMMHV
  NAME: DBIA 4811                       ID: PXRMMHV
 GENERAL DESCRIPTION:   This integration agreement describes the Clinical
 Reminders APIs developed for use by My HealtheVet.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Clinical Reminders
KEYWORDS: My HealtheVet
COMPONENT/ENTRY POINT: MHVC(DFN)
 COMPONENT DESCRIPTION:   This entry point returns the combined MHV summary and
 MHV detailed output for an individual patient.  
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient DFN.  
  
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   Output is returned in ^TMP("PXRMMHVC",$J,RIEN) where
 RIEN is the internal entry number of the reminder definition (file #811.9).  
 The evaluation status is returned in 
  ^TMP("PXRMMHVC",$J,RIEN,"STATUS")=STATUS^DUE DATE^LAST DONE DATE 
  
 The detailed output is returned in 
  ^TMP("PXRMMHVC",$J,RIEN,"DETAIL",L)=TEXT line L 
  
 where L is the line number.  
  
 The summary text is returned in ^TMP("PXRMMHVC",$J,RIEN,"SUMMARY",L)=TEXT line
 L 
  
 The caller should kill ^TMP("PXRMMHVC",$J) once it has finished processing it. 
  
  
  
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   Output is returned in ^TMP("PXRMMHVC",$J,RIEN)        
                where RIEN is the internal entry number of the reminder 
 definition (file #811.9).  
  
 The evaluation status is returned in 
  ^TMP("PXRMMHVC",$J,RIEN,"STATUS")=STATUS^DUE DATE^LAST DONE DATE 
                             
 The detailed output is returned in         
  ^TMP("PXRMMHVC",$J,RIEN,"DETAIL",L)=TEXT line L 
                             
  where L is the line number. 
                             
 The summary text is returned in            
  ^TMP("PXRMMHVC",$J,RIEN,"SUMMARY",L)=TEXT line L 
                             
 The caller should kill ^TMP("PXRMMHVC",$J) once they have finished processing
 it. 
  
  
COMPONENT/ENTRY POINT: PREMLIST
 COMPONENT DESCRIPTION:   This entry point returns a list of all the active
 clinical reminders that have been written for use by patients. A reminder is
 marked as a patient reminder when it contains a "P" is the USAGE field. 
  
  
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   Output is returned in 
  ^TMP("PXRMMHVL",$J,RIEN)=NAME^PRINT NAME^CLASS 
  
 where RIEN is the internal entry number of the reminder definition, (file
 #811.9), NAME is the reminder name (field 811.9, .01),  PRINT NAME is the
 print name (field 811.9, 1.2), and CLASS is the reminder class (field 811.9,
 100). 
  
 The caller should kill ^TMP("PXRMMHVL",$J) once they have finished processing
 it. 
  
  
  
COMPONENT/ENTRY POINT: WEBALL
 COMPONENT DESCRIPTION:   This entry point returns the web site information for
 all active patient reminders.  
  
  
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   Output is returned in ^TMP("PXRMMHVW",$J,RIEN,"WEB");
 the format is: 
  ^TMP("PXRMMHVW",$J,RIEN,"WEB",N,"URL")=URL 
  ^TMP("PXRMMHVW",$J,RIEN,"WEB",N,"TITLE")=TITLE 
  ^TMP("PXRMMHVW",$J,RIEN,"WEB",N,"DESCRIPTION",1)=TEXT line L 
  
 where RIEN is the internal entry number of the reminder definition (file
 #811.9), N is the nth web site defined for this reminder, URL is the web site
 URL, TITLE is the web site title, L is the lth line of the description. 
  
 The caller should kill ^TMP("PXRMMHVW",$J) once they have finished processing
 it.  
  
  
COMPONENT/ENTRY POINT: WEBI(RIEN,NODE)
 COMPONENT DESCRIPTION:   This API returns the web site information for an
 individual reminder.  
  
VARIABLES: RIEN                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number of the reminder
 definition (file #811.9).  
  
  
VARIABLES: NODE                         TYPE: Input
 VARIABLES DESCRIPTION:   NODE is the subscript of ^TMP where the output will
 be returned, i.e., ^TMP(NODE,$J).  
  
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   The output is returned in ^TMP(NODE,$J,RIEN,WEB); the
 format is; 
  ^TMP(NODE,$J,RIEN,"WEB",N,"URL")=URL 
  ^TMP(NODE,$J,RIEN,"WEB",N,"TITLE")=TITLE 
  ^TMP(NODE,$J,RIEN,"WEB",N,"DESCRIPTION",L)=TEXT line L 
  
 where RIEN is the internal entry number of the reminder definition (file
 #811.9), N is the nth web site defined for this reminder, URL is the web site
 URL, TITLE is the web site title, L is the lth line of the description. 
  
 The caller should kill ^TMP(NODE,$J) once they have finished processing it.  
  
  
  
SUBSCRIBING PACKAGE: MYHEALTHEVET
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD

NUMBER: 4812                            IA #: 4812
  FILE NUMBER: 9002313.02               GLOBAL ROOT: BPSC(
  DATE CREATED: OCT 12, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4812
  ID: BPSC(
GLOBAL REFERENCE: BPSC(D0,1)
FIELD NUMBER: 1.04                      FIELD NAME: VA PLAN IEN
  LOCATION: 1;4                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
    The IB package required direct Read access to the following fields 
    of the BPS CLAIMS file (#9002313.02) 
    
   Field      Name                           Loc   Access 
    1.04      VA PLAN IEN                    1;4   Direct Global Read 
  STATUS: Active
KEYWORDS: BPS
KEYWORDS: ECME
KEYWORDS: NCPDP
KEYWORDS: HIPAA
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4813                            IA #: 4813
  FILE NUMBER: 9002313.03               GLOBAL ROOT: BPSR(
  DATE CREATED: OCT 12, 2005            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4813
  ID: BPSR(
 GENERAL DESCRIPTION:   The IB package requires Read-only access (both direct
 global reads and through FileMan) to all fields, nodes, and pieces of the BPS
 RESPONSES file (#9002313.03) and to all subfiles.  
  STATUS: Active
KEYWORDS: BPS
KEYWORDS: ECME
KEYWORDS: HIPAA
KEYWORDS: NCPDP
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: NOV 12, 2010

NUMBER: 4814                            IA #: 4814
  FILE NUMBER: 9000001                  GLOBAL ROOT: AUPNPAT(
  DATE CREATED: OCT 12, 2005
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HEALTH RECORD NUMBER LOOKUP
  ID: AUPNPAT(
GLOBAL REFERENCE: AUPNPAT("D",
 GLOBAL DESCRIPTION:   Direct global access permitted to the Health Record
 Number x-ref.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE

NUMBER: 4815                            IA #: 4815
  DATE CREATED: OCT 19, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMVDCSAV
  NAME: GMVDCSAV                        ID: GMVDCSAV
 GENERAL DESCRIPTION:   Allows the subscriber to file patient vitals data in
 the GMRV VITAL MEASUREMENT (#120.5) file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN1(.RESULT,GMVDATA)
 COMPONENT DESCRIPTION:   This entry point allows the subscriber to add a new
 record to the GMRV VITALS MEASUREMENT (#120.5) file.  
VARIABLES: GMVDATA                      TYPE: Input
 VARIABLES DESCRIPTION:   This variable contains the data needed to build a
 Vital/Measurement record in the GMRV Vital Measurement (#120.5) file. The
 values are parsed out of the GMRVDATA variable and filed.  
   
  GMRVDATA has the following data: 
   piece1^piece2^piece3^piece4^piece5 
   
  where: 
   piece1 = the FileMan internal date/time 
   piece2 = patient number from FILE 2 (i.e., DFN) 
   piece3 = vital type, a semi-colon, the reading, a semi-colon, and 
            supplemental oxygen value (e.g., 21;99;1 l/min 90%) 
   piece4 = hospital location (FILE 44) pointer value 
   piece5 = user number from FILE 200 (i.e., DUZ), an asterisk, and the 
            qualifier internal entry numbers (FILE 120.52) separated by 
            colons (e.g., 547*50:65) 
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************** 
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                   
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
 ****************************************************

NUMBER: 4816                            IA #: 4816
  GLOBAL ROOT: DD(                      DATE CREATED: OCT 24, 2005
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DD Nodes for files 5, SUB-FILE 5.01, 5.12, & 5.13
  ID: DD(
 GENERAL DESCRIPTION:   This will be a one time agrement for patch XU*8*378 to
 se the following nodes: 
  
 Routine: XU8P378 
         ; Set current C xrefs in 5 to Q 
         S ^DD(5,1,1,1,1)="Q" 
         S ^DD(5,1,1,1,2)="Q" 
         S ^DD(5,1,1,1,3)="Used in conjunction with the 'ADUALC' xref." 
         S ^DD(5,1,"DT")=$G(DT) 
         S ^DD(5,2,1,1,1)="Q" 
         S ^DD(5,2,1,1,2)="Q" 
         S ^DD(5,2,1,1,3)="Used in conjunction with the 'ADUALC' xref." 
         S ^DD(5,2,"DT")=$G(DT) 
  
 Routine: XU8P378C 
          ; Set DEL & LAYGO nodes for file 5 
          S ^DD(5,.01,"DEL",1,0)="D EN^DDIOL(""Deletions are not 
 allowed."","""", ""!?5,$C(7)"") I 1" 
          S ^DD(5,.01,"LAYGO",1,0)="D EN^DDIOL(""New State additions are not
 allowed."","""",""!?5,$C(7)"") I 0" 
          S ^DD(5,.01,"DT")=$G(DT) 
          ;
          ; Set DEL & LAYGO nodes for sub-file 5.01 
          S ^DD(5.01,.01,"DEL",1,0)="D EN^DDIOL(""Entries can only be 
 Inactivated."","""",""!?5,$C(7)"") I 1" 
          S ^DD(5.01,.01,"LAYGO",1,0)="D EN^DDIOL(""New County additions are
 not allowed."","""",""!?5,$C(7)"") I 0" 
          S ^DD(5,.01,"DT")=$G(DT) 
          ;
          ; Set DEL node for file 5.12 
          S ^DD(5.12,.01,"DEL",1,0)="D EN^DDIOL(""Entries can only be 
 Inactivated."","""",""!?5,$C(7)"") I 1" 
          S ^DD(5.12,.01,"DT")=$G(DT) 
          ;
          ; Set Del & LAYGO nodes for file 5.13 
          S ^DD(5.13,.01,"DEL",1,0)="D EN^DDIOL(""Entries can only be 
 Inactivated."","""",""!?5,$C(7)"") I 1" 
          S ^DD(5.13,.01,"LAYGO",1,0)="D EN^DDIOL(""New County Code additions
 are not allowed."","""",""!?5,$C(7)"") I 0" 
          S ^DD(5.13,.01,"DT")=$G(DT) 
  STATUS: Active
SUBSCRIBING PACKAGE: KERNEL

NUMBER: 4817                            IA #: 4817
  DATE CREATED: OCT 24, 2005            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFPFSEV
  NAME: PFSS EVN SEGMENT BUILDER        ID: VAFPFSEV
 GENERAL DESCRIPTION:   The PFSS 1B Prototype requries HL7 messages to be sent
 from VistA to a Commercial Billing System.  The messages contain an EVN
 segment with contents not supported by existing EVN-building utilities.  The 
 EN^VAFPFSEV API returns a complete EVN segment.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EVN
COMPONENT/ENTRY POINT: EN(EVENT,EVN,ERR)
 COMPONENT DESCRIPTION:   EN^VAFPFSEV builds an EVN segment.  It inserts the
 HL7 EVENT passed in the EVENT parameter into the segment.  The segment is
 returned in the EVN parameter.  An error message is returned if the segment
 cannot be built.  
VARIABLES: EVENT                        TYPE: Input
 VARIABLES DESCRIPTION:   HL7 Event (e.g., A08).  
VARIABLES: EVN                          TYPE: Output
 VARIABLES DESCRIPTION:   Returned EVN segment.  
VARIABLES: ERR                          TYPE: Output
 VARIABLES DESCRIPTION:   An error message if the segment cannot be built.  
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM

NUMBER: 4818                            IA #: 4818
  DATE CREATED: OCT 25, 2005
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORQQPL3
  NAME: MHV use of ORQQPL3              ID: ORQQPL3
 GENERAL DESCRIPTION:   This documents usage of calls in ORQQPL3 to obtain a
 patient's problems.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LIST(.RESULT,DFN,STATUS)
 COMPONENT DESCRIPTION:   Returns a list of patient problems (no hidden
 problems).  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   List of problems and key attributes in the format: 
 RESULT(0)=number of problems returned 
 RESULT(n)=IFN^Status^Description^ICD^Onset^LastMod^ 
           SC^Exposures^Condition^Loc^LocType^Prov^ 
           Service^Priority^HasComment^Recorded^ 
           SCconditions^InactiveICDcode 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file #2 IEN 
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   The type of problems to be returned, by status; may
 be A=active, I=inactive, or "" to get all problems.  
COMPONENT/ENTRY POINT: DELLIST(.RESULT,DFN)
 COMPONENT DESCRIPTION:   Returns a list of hidden problems for a patient.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   List of problems and key attributes in the format: 
 RESULT(n)=IFN^Status^Description^ICD^Onset^LastMod^ 
           SC^Exposures^Condition^Loc^LocType^Prov^ 
           Service^Priority^HasComment^Recorded^ 
           SCconditions^InactiveICDcode 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file #2 IEN 
SUBSCRIBING PACKAGE: MYHEALTHEVET

NUMBER: 4819                            IA #: 4819
  FILE NUMBER: 59.5                     GLOBAL ROOT: 59.5
  DATE CREATED: OCT 31, 2005            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSJ59P5
  NAME: PSJ59P5                         ID: PSJ59P5
 GENERAL DESCRIPTION:   This API shall be provided to return the NAME field
 (#.01), DIVISION field (#.02) and INACTIVATION DATE field (#19) from the IV
 ROOM file (#59.5) for the IEN or free text entry received.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ALL(PSJIEN,PSJTXT,LIST)
VARIABLES: PSJIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSJIEN = Internal Entry Number in IV ROOM file 59.5
 [optional] 
VARIABLES: PSJTXT                       TYPE: Input
 VARIABLES DESCRIPTION:   PSJTXT = Free text entry (a value of "??" may be
 used) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript name used in ^TMP global [REQUIRED] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returned or -1^NO DATA
 FOUND 
  
 ^TMP($J,LIST,PSJIEN,.01)=NAME (59.5,.01) 
  
 ^TMP($J,LIST,PSJIEN,.02)= DIVISION (59.5,.02)^NAME(40.8,.01) 
  
 ^TMP($J,LIST, PSJIEN,19)= INACTIVATION DATE (59.5,19)^External Format 
  (ex: Sep. 12, 1999) 
  
 ^TMP($J,LIST,"B",NAME,PSJIEN)="" 
COMPONENT/ENTRY POINT: WRT(PSJIEN,PSJVAL,LIST)
VARIABLES: PSJIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the IV ROOM file (59.5)[REQUIRED] 
VARIABLES: PSJVAL                       TYPE: Input
 VARIABLES DESCRIPTION:   Division value [REQUIRED AND MUST BE THE POINTER
 VALUE] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   defined by the calling application [REQUIRED] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,PSJIEN,0)=0 for failure or 1 for success 

NUMBER: 4820                            IA #: 4820
  DATE CREATED: DEC 07, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSO52API
  NAME: PRESCRIPTION FILE (#52) DATA ELEMENTS
  ID: PSO52API
 GENERAL DESCRIPTION:   The PSO52API routine shall be used to return requested
 data elements for the PRESCRIPTION file (#52).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RX(DFN,LIST,IEN,RX#,NODE,SDATE,EDATE)
 COMPONENT DESCRIPTION:   
  
 RX^PSO52API(DFN,LIST,IEN,RX#,NODE,SDATE,EDATE) 
  
 Input: 
   DFN 
   LIST 
   IEN 
   RX# 
   NODE 
   SDATE 
   EDATE 
  
 Where: 
   DFN = IEN from the PATIENT file (#2) [required] 
   LIST = Subscript name used in the ^TMP global [required] 
   IEN = Internal prescription number in PRESCRIPTION file (#52) [optional] 
   RX# = RX # field (#.01) from the PRESCRIPTION file (#52) [optional] 
   NODE = will be passed "null" or as a string of data separated by commas 
 containing some or all of the following: 
 0,2,3,R,I,P,O,T,L,S,M,C,A,ICD,CPRS,ST,IND 
  
   SDATE = Start Date [optional] 
   EDATE = End Date [optional] 
  
 Note: This API has defined one entry point by parameter passing, to return 
 data from available data nodes from the PRESCRIPTION file (#52). The variable
 "NODE" shall be passed null or as a string of data separated by commas. Every
 field from the PRESCRIPTION file (#52) shall not be returned, though the
 string must be defined to contain some or all of the following: 0, 2, 3, R, I,
 P, O, T, L, S, M, C, A, ICD, CPRS, ST, IND.  Each section describes what is
 returned by each string variable. TRADE NAME field (#6.5) (piece 1 of the "TN"
 node), from the PRESCRIPTION file (#52) that is associated with DRUG NAME
 field (#6) will be returned as part of the 0 node data, if populated. The
 status and "B" cross-reference of valid prescriptions is always returned.  
  
   0 - returns the Zero node 
   2 - returns the Zero and Two nodes 
   3 - returns the Two and Three nodes 
   R - returns all refills for a prescription (If a specific refill is wanted,
 this variable must be passed in the following format: "R^^n" (indicating which
 refill is wanted)) 
   I - returns Integrated Billing (IB) data ([^null, O or R^n] if 2nd piece is
 defined as null IB data for both original and all refills are returned. If 2nd
 piece is defined as 'O' only IB data for the original fill is returned.  If
 2nd piece is  defined as 'R' refill data is returned and the 3rd piece is
 null, all refill IB data are returned, or if the 3rd piece has a number it
 shall return the IB node for that refill only.) 
   P - returns all partial fills for a prescription 
   O - returns the Orderable Item for a prescription 
   T - returns the TPB node 
   L - returns the Label multiple 
   S - returns the SAND node 
   M - returns the medication instructions (SIG) 
   C - returns CMOP data 
   A - returns the Activity Logs for a prescription 
   CPRS - returns the corresponding ORDER File (#100) internal entry number 
   ICD - returns the ICD multiple 
   ST - returns the status of the prescription 
   IND - returns the Indication if populated 
  
 Note: If NODE is passed in null, all possible nodes are returned.  
  
 Note: If an invalid parameter is passed into the NODE variable the following 
 node shall be returned: 
  ^TMP($J,LIST,DFN,IEN,"INVALID REQUEST",NODE)=Invalid Data Requested 
  
 Output: (If node = 0 (zero)) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,.01)=RX #(52,.01) 
   ^TMP($J,LIST,DFN,IEN,1)=ISSUE DATE (52,1)^External Format (ex: Sep. 12, 
 1999) 
   ^TMP($J,LIST,DFN,IEN,2)=PATIENT (52,2)^NAME (2,.01) 
   ^TMP($J,LIST,DFN,IEN,3)=PATIENT STATUS (52,3) 
   ^TMP($J,LIST,DFN,IEN,4)=PROVIDER (52,4)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN,5)=CLINIC (52,5)^NAME(44,.01) 
   ^TMP($J,LIST,DFN,IEN,6)=DRUG (52,6)^GENERIC NAME(50,.01) 
   ^TMP($J,LIST,DFN,IEN,6.5)=TRADE NAME (52,6.5) 
   ^TMP($J,LIST,DFN,IEN,7)=QTY (52,7) 
   ^TMP($J,LIST,DFN,IEN,8)=DAYS SUPPLY (52,8) 
   ^TMP($J,LIST,DFN,IEN,9)=# OF REFILLS (52,9) 
   ^TMP($J,LIST,DFN,IEN,10.3)=ORDER CONVERTED (52,10.3)^External Format for the
 Set of Codes 
   ^TMP($J,LIST,DFN,IEN,10.6)=COPIES (52,10.6) 
   ^TMP($J,LIST,DFN,IEN,11)=MAIL/WINDOW (52,11)^External Format for the Set of
 Codes 
   ^TMP($J,LIST,DFN,IEN,14)=ADMINISTERED IN CLINIC (52,14)^External Format fof
 the Set of Codes 
   ^TMP($J,LIST,DFN,IEN,16)=ENTERED BY (52,16)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN,17)=UNIT PRICE OF DRUG (52,17) 
  
 Output: (If node = 2) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,.01)=RX #(52,.01) 
   ^TMP($J,LIST,DFN,IEN,1)=ISSUE DATE (52,1)^External Format (ex: Sep. 12,
 1999) 
   ^TMP($J,LIST,DFN,IEN,2)=PATIENT (52,2)^NAME (2,.01) 
   ^TMP($J,LIST,DFN,IEN,3)=PATIENT STATUS (52,3) 
   ^TMP($J,LIST,DFN,IEN,4)=PROVIDER (52,4)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN,5)=CLINIC (52,5)^NAME(44,.01) 
   ^TMP($J,LIST,DFN,IEN,6)=DRUG (52,6)^GENERIC NAME(50,.01) 
   ^TMP($J,LIST,DFN,IEN,6.5)=TRADE NAME (52,6.5) 
   ^TMP($J,LIST,DFN,IEN,7)=QTY (52,7) 
   ^TMP($J,LIST,DFN,IEN,8)=DAYS SUPPLY (52,8) 
   ^TMP($J,LIST,DFN,IEN,9)=# OF REFILLS (52,9) 
   ^TMP($J,LIST,DFN,IEN,10.3)=ORDER CONVERTED (52,10.3)^External Format for the
 Set of Codes 
   ^TMP($J,LIST,DFN,IEN,10.6)=COPIES (52,10.6) 
   ^TMP($J,LIST,DFN,IEN,11)=MAIL/WINDOW (52,11)^External Format for the Set of
 Codes 
   ^TMP($J,LIST,DFN,IEN,16)=ENTERED BY (52,16)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN,17)=UNIT PRICE OF DRUG (52,17) 
   ^TMP($J,LIST,DFN,IEN,20)=DIVISION (52,20)^NAME(59,.01) 
   ^TMP($J,LIST,DFN,IEN,21)=LOGIN DATE (52,21)^External Format (ex: Sep. 12, 
 1999) 
   ^TMP($J,LIST,DFN,IEN,22)=FILL DATE (52,22)^External Format (ex: Sep. 12, 
 1999) 
   ^TMP($J,LIST,DFN,IEN,23)=PHARMACIST (52,23)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN 24)=LOT # (52,24) 
   ^TMP($J,LIST,DFN,IEN 25)=DISPENSED DATE (52,25)^External Format (ex: Sep.  
 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,26)=EXPIRATION DATE (52,26)^External Format (ex: Sep.
 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,27)=NDC (52,27) 
   ^TMP($J,LIST,DFN,IEN,28)=MANUFACTURER (52,28) 
   ^TMP($J,LIST,DFN,IEN,29)=DRUG EXPIRATION DATE (52,29)^External Format (ex: 
 Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,30)=GENERIC PROVIDER (52,30) 
   ^TMP($J,LIST,DFN,IEN,31)=RELEASE DATE/TIME (52,31)^External Format (ex: Sep.
 12, 1999) 
   ^TMP($J,LIST,DFN,IEN 32.1)=RETURNED TO STOCK (52,32.1)^External Format (ex:
 Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,32.2)=REPRINT (52,32.2)^External Format for the Set of
 Codes 
   ^TMP($J,LIST,DFN,IEN,32.3)=BINGO WAIT TIME (52,32.3) 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100)^External Format for the Set of
 Codes 
   ^TMP($J,LIST,DFN,IEN,104)=VERIFYING PHARMACIST (52,104)^NAME (200,.01) 
   ^TMP($J,LIST,"B",RX#,IEN)="" 
  
 Output: (If node = 3) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,12)=REMARKS (52,12) 
   ^TMP($J,LIST,DFN,IEN,20)=DIVISION (52,20)^NAME (59,.01) 
   ^TMP($J,LIST,DFN,IEN,21)=LOGIN DATE (52,21)^External Format (ex: Sep. 12, 
 1999) 
   ^TMP($J,LIST,DFN,IEN,22)=FILL DATE (52,22)^External Format (ex: Sep. 12,
 1999) 
   ^TMP($J,LIST,DFN,IEN,23)=PHARMACIST (52,23)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN 24)=LOT # (52,24) 
   ^TMP($J,LIST,DFN,IEN 25)=DISPENSED DATE (52,25)^External Format (ex: Sep.  
 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,26)=EXPIRATION DATE (52,26)^External Format (ex: Sep.  
 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,26.1)=CANCEL DATE (52,26.1)^External Format (ex: Sep.  
 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,27)=NDC (52,27) 
   ^TMP($J,LIST,DFN,IEN,28)=MANUFACTURER (52,28) 
   ^TMP($J,LIST,DFN,IEN,29)=DRUG EXPIRATION DATE (52,29)^External Format (ex: 
 Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,30)=GENERIC PROVIDER (52,30) 
   ^TMP($J,LIST,DFN,IEN,31)=RELEASE DATE/TIME (52,31)^External Format (ex: Sep.
 12, 1999) 
   ^TMP($J,LIST,DFN,IEN 32.1)=RETURNED TO STOCK (52,32.1)^External  (ex: Sep.  
 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,32.2)=REPRINT (52,32.2)^External Format for the Set of
 Codes 
   ^TMP($J,LIST,DFN,IEN,32.3)=BINGO WAIT TIME (52,32.3) 
   ^TMP($J,LIST,DFN,IEN,34.1)=DRUG ALLERGY INDICATION (52,34.1)^External Format
 for the Set of Codes 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100)^External Format for the Set of 
 Codes 
   ^TMP($J,LIST,DFN,IEN,101)=LAST DISPENSED DATE (52,101)^External Format (ex:
 Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,102)=NEXT POSSIBLE FILL (52,102)^External Format (ex: 
 Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,102.1)=PRIOR FILL DATE (52,102.1)^External Format (ex:
 Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,102.2)=PENDING NEXT POSSIBLE FILLDATE (52,102.2) 
 ^External Format (ex: Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,104)=VERIFYING PHARMACIST (52,104)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN,109)=COSIGNING PHYSICIAN (52,109)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN,112)=ORIGINAL QTY (52,112) 
   ^TMP($J,LIST,"B",RX#,IEN)="" 
  
 Output: (If node = R(r)[^^n(o)]) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100)^External Format for the Set of 
 Codes 
   ^TMP($J,LIST,DFN,IEN,"RF",0)=Total entries returned by patient or -1^NO DATA
 FOUND 
   ^TMP($J,LIST,DFN,IEN,"RF",n,.01)=REFILL DATE (52.1,.01)^External Format (ex:
 Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,1)=QTY (52.1,1) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,1.1)=DAYS SUPPLY (52.1,1.1) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,1.2)=CURRENT UNIT PRICE OF DRUG (52.1,1.2) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,2)=MAIL/WINDOW (52.1,2)^External Format for the
 Set of Codes 
   ^TMP($J,LIST,DFN,IEN,"RF",n,3)=REMARKS (52.1,3) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,4)=PHARMACIST NAME (52.1,4)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,5)=LOT # (52.1,5) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,6)=CLERK CODE (52.1,6)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,7)=LOGIN DATE (52.1,7)^External Format (ex: Sep.
 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,8)=DIVISION (52.1,8)^NAME (59,.01) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,10.1)=DISPENSE DATE (52.1,10.1)^External Format
 (ex: Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,11)=NDC (52.1,11) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,12)=MANUFACTURER (52.1,12) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,13)=DRUG EXPIRATION DATE (52.1,13)^External 
 Format (ex: Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,14)=RETURNED TO STOCK (52.1,14)External Format
 (ex: Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,15)=PROVIDER (52.1,15)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,17)=RELEASED DATE/TIME (52.1,17)^External Format
 (ex: Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,"RF",n,23)=ADMINISTERED IN CLINIC (52.1,23)^External
 Format for the set of Codes 
   ^TMP($J,LIST,"B",RX#,IEN)="" 
  
 Where: 
   n = the IEN of entry in the Refill multiple 
  
 Output: (If node = I(r)[^null,O or R^n]) 
  
 [ORIGINAL FILLS] 
   ^TMP($J,LIST,DFN,IEN,105)=COPAY TRANSACTION TYPE (52,105) 
   ^TMP($J,LIST,DFN,IEN,106)=IB NUMBER (52,106)^REFERENCE NUMBER(350,.01) 
   ^TMP($J,LIST,DFN,IEN,106.5)=COPAY TYPE AUDIT (52,106.5) 
   ^TMP($J,LIST,DFN,IEN,106.6)=COPAY EXCEEDING CAP (52,106.6)^TRANSACTION 
 NUMBER(354.71,.01) 
  
  
 [REFILLS] 
   ^TMP($J,LIST,DFN,IEN,"IB",0)=Total entries returned by patient or -1^NO DATA
 FOUND 
   ^TMP($J,LIST,DFN,IEN,"IB",n,9)= IB NUMBER (52.1,9)^REFERENCE NUMBER(350,.01) 
   ^TMP($J,LIST,DFN,IEN,"IB",n,9.1)=COPAY EXCEEDING CAP (52.1,9.1)^ TRANSACTION
 NUMBER(354.71,.01) 
  
 Where: 
   n = the IEN of entry in the Refill multiple for IB 
  
 Output: (If node = P) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100)^External Format for the Set of
 Codes 
   ^TMP($J,LIST,DFN,IEN,"P",0)= Total entries returned or -1^NO DATA FOUND 
  ^TMP($J,LIST,DFN,IEN,"P",n,.01)=PARTIAL DATE (52.2,.01)^External Format (ex:
 Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,"P",n,.02)=MAIL/WINDOW (52.2,.02)^External Format for
 the Set of Codes 
   ^TMP($J,LIST,DFN,IEN,"P",n,.03)=REMARKS (52.2,.03) 
   ^TMP($J,LIST,DFN,IEN,"P",n,.04)=QTY (52.2,.04) 
   ^TMP($J,LIST,DFN,IEN,"P",n,.041)=DAYS SUPPLY (52.2,.041) 
   ^TMP($J,LIST,DFN,IEN,"P",n,.042)=CURRENT UNIT PRICE OF DRUG (52.2,.042) 
   ^TMP($J,LIST,DFN,IEN,"P",n,.05)=PHARMACIST NAME (52.2,.05)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN,"P",n,.06)=LOT # (52.2,.06) 
   ^TMP($J,LIST,DFN,IEN,"P",n,.08)=LOGIN DATE (52.2,.08)^External Format (ex: 
 Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,"P",n,.09)=DIVISION (52.2,.09)^NAME (59,.01) 
   ^TMP($J,LIST,DFN,IEN,"P",n,1)=NDC (52.2,1) 
   ^TMP($J,LIST,DFN,IEN,"P",n,5)=RETURNED TO STOCK (52.2,5)^External Format 
 (ex: Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,"P",n,6)=PROVIDER (52.2,6)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN,"P",n,7.5)=DISPENSED DATE (52.2,7.5)^External Format
 (ex: Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,"P",n,8)=RELEASE DATE/TIME (52.2,8)^External Format 
 (ex: Sep. 12, 1999) 
   ^TMP($J,LIST,"B",RX#,IEN)="" 
  
 Where: 
   n = the IEN of entry in the Partial multiple 
  
 Output: (If node = O) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100)^External Format for the Set of 
 Codes 
   ^TMP($J,LIST,DFN,IEN,"OI")=IEN(52,39.2)^NAME(50.7,.01)^DOSAGE
 FORM(50.7,.02)^NAME (50.606,.01) 
   ^TMP($J,LIST,"B",RX#,IEN)="" 
  
 Output: (If node = T) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND" 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100)^External Format for the Set of 
 Codes 
   ^TMP($J,LIST,DFN,IEN,201)=TPB RX (52,201)^External Format for the Set of
 Codes 
   ^TMP($J,LIST,"B",RX#,IEN)="" 
  
 Output: (If node = L) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100)^External Format for the Set of
 Codes 
   ^TMP($J,LIST,DFN,IEN,"L",0)=Total entries returned or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,"L",n,.01)=LABEL DATE/TIME (52.032,.01)^External Format
 (ex: Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,"L",n,1)=RX REFERENCE (52.032,1) 
   ^TMP($J,LIST,DFN,IEN,"L",n,2)=LABEL COMMENT (52.032,1) 
   ^TMP($J,LIST,DFN,IEN,"L",n,3)=PRINTED BY (52.032,3)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN,"L",n,4)=WARNING LABEL TYPE (52.032,4)^External Format
 for the Set of Codes 
   ^TMP($J,LIST,"B",RX#,IEN)="" 
  
 Where: 
   n = the IEN of entry in the Label multiple 
  
 Output: (If node = S) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100)^External Format for the Set of 
 Codes 
   ^TMP($J,LIST,DFN,IEN,301)=CLOZAPINE DOSAGE (MG/DAY) (52,301) 
   ^TMP($J,LIST,DFN,IEN,302)=WBC RESULTS (52,302) 
   ^TMP($J,LIST,DFN,IEN,303)=DATE OF WBC TEST (52,303)^External Format (ex: 
 Sep. 12, 1999) 
   ^TMP($J,LIST,"B",RX#,IEN)="" 
  
 Output: (If node = M) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100)^External Format for the Set of
 Codes 
   ^TMP($J,LIST,DFN,IEN,"M",0)=Total entries returned or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,"M",n,0)=MEDICATION INSTRUCTIONS(52.04,.01) 
   ^TMP($J,LIST,"B",RX#,IEN)="" 
  
 Where: 
   n = the IEN of entry in the Medication Instruction (SIG) multiple 
  
 Output: (If node = C) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100)^External Format for the Set of
 Codes 
   ^TMP($J,LIST,DFN,IEN,"C",0)=Total entries returned or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,"C",n,.01)=TRANSMISSION NUMBER (52.01,.01)^TRANSMISSION
 (550.2,.01) 
   ^TMP($J,LIST,DFN,IEN,"C",n,2)=RX INDICATOR (52.01,2) 
   ^TMP($J,LIST,DFN,IEN,"C",n,3)=STATUS (52.01,3)^External Format for the Set
 of Codes 
   ^TMP($J,LIST,DFN,IEN,"C",n,4)=NDC (52.01,4) 
   ^TMP($J,LIST,DFN,IEN,"C",n,9)=DATE SHIPPED (52.01,9)^ External Format (ex:
 Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,"C",n,10)=CARRIER (52.01,10) 
   ^TMP($J,LIST,DFN,IEN,"C",n,11)=PACKAGE ID (52.01,11) 
   ^TMP($J,LIST,DFN,IEN,"C",n,12)=NDC SENT (52.01,12) 
   ^TMP($J,LIST,"B",RX#,IEN)="" 
  
 Where: 
   n = the IEN of entry in the CMOP Event multiple 
  
 Output: (If node = A) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100)^External Format for the Set of 
 Codes 
   ^TMP($J,LIST,DFN,IEN,"A",0)=Total entries returned or -1^NO DATA FOUND 
 ^TMP($J,LIST,DFN,IEN,"A",n,.01)=ACTIVITY LOG (52.03,.01)^External Format (ex:
 Sep. 12, 1999) 
   ^TMP($J,LIST,DFN,IEN,"A",n,.02)=REASON (52.03,.02)^External Format for the
 Set of Codes 
   ^TMP($J,LIST,DFN,IEN,"A",n,.03)=INITIATOR OF ACTIVITY (52.03,.03)^NAME 
 (200,.01) 
   ^TMP($J,LIST,DFN,IEN,"A",n,.04)=RX REFERENCE (52.03,.04) 
   ^TMP($J,LIST,DFN,IEN,"A",n,.05)=COMMENTS (52.30,.05) 
   ^TMP($J,LIST,DFN,IEN,"A",n,"OC",n,.01)=OTHER COMMENTS (52.34,.01) 
   ^TMP($J,LIST,"B",RX#,IEN)="" 
  
 Output:( If node = CPRS) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100) ^External Format for the Set of
 Codes 
   ^TMP($J,LIST,DFN,IEN,39.3)=PLACER ORDER # (52,39.3) 
  
 Where: 
   n = the IEN of entry in the Activity Log multiple 
  
 Output: (If node = ICD) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100) ^External Format for the Set of
 Codes 
   ^TMP($J,LIST,DFN,IEN,"ICD",0)=Total entries returned or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,"ICD",n,.01)=ICD DIAGNOSIS (52.052311,.01)^CODE NUMBER
 (80,.01) 
   ^TMP($J,LIST,DFN,IEN,"ICD",n,1)=AGENT ORANGE (52.052311,1)^External Format
 for the Set of Codes 
   ^TMP($J,LIST,DFN,IEN,"ICD",n,2)=IONIZING RADIATION (52.052311,2)^External
 Format for the Set of Codes 
   ^TMP($J,LIST,DFN,IEN,"ICD",n,3)=SERVICE CONNECTION (52.052311,3)^External
 Format for the Set of Codes 
   ^TMP($J,LIST,DFN,IEN,"ICD",n,4)=ENVIRONMENTAL CONTAMINANTS 
 (52.052311,4)^External Format for the Set of Codes 
   ^TMP($J,LIST,DFN,IEN,"ICD",n,5)=MILITARY SEXUAL TRAUMA 
 (52.052311,5)^External Format for the Set of Codes 
   ^TMP($J,LIST,DFN,IEN,"ICD",n,6)=HEAD AND/OR NECK CANCER 
 (52.052311,6)^External Format for the Set of Codes 
   ^TMP($J,LIST,DFN,IEN,"ICD",n,7)=COMBAT VETERAN (52.052311,7)^External Format
 for the Set of Codes 
  
 Where: 
   n = the IEN of entry in the ICD multiple 
  
 Output: (If node = ST) 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100)^External Format for the Set of 
 Codes 
  
 Output: (If node = IND) ^TMP($J,LIST,DFN,IEN,"IND")=Indication^Indication flag
 (1-Indication is included in the Sig, 0 or null-Indication is not included in
 the Sig) 
  
   ^TMP($J,LIST,"B",RX#,IEN)="" 
VARIABLES: DFN                          TYPE: Both
 VARIABLES DESCRIPTION:   Internal entry number from the PATIENT file (#2)
 [required] 
VARIABLES: LIST                         TYPE: Both
 VARIABLES DESCRIPTION:   Subscript name used in the ^TMP global [required] 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number from the PRESCRIPTION file
 (#52) [optional].  
VARIABLES: RX#                          TYPE: Input
 VARIABLES DESCRIPTION:   RX # field (#.01) from the PRESCRIPTION file (#52)
 [optional].  
VARIABLES: NODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This string variable is used to determine what data
 elements from the PRESCRIPTION file (#52) are returned.  
  
 If NODE is passed in null, all possible pre-defined data elements are 
 returned. [optional] 
VARIABLES: EDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   EXPIRATION DATE field (#26) from the PRESCRIPTION
 file (#52) using the ^PS(55,Patient,"P","A",Expiration Date,DA)
 cross-reference from PHARMACY PATIENT file (#55) when prescriptions are
 requested within a date range.  [optional] 
VARIABLES: SDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   EXPIRATION DATE field (#26) from the PRESCRIPTION
 file (#52) using the ^PS(55,Patient,"P","A",Expiration Date,DA)
 cross-reference from PHARMACY PATIENT file (#55) when prescriptions are
 requested within a date range.  [optional] 
COMPONENT/ENTRY POINT: PROF(DFN,LIST,SDATE,EDATE)
 COMPONENT DESCRIPTION:   
   PROF^PSO52API(DFN,LIST,SDATE,EDATE) 
  
 Input: 
   DFN 
   LIST 
   SDATE 
   EDATE 
  
 Where: 
   DFN = IEN from the PATIENT file (#2) [required] 
   LIST = Subscript name used in the ^TMP global [required] 
   SDATE = Starting Expiration Date [optional] 
   EDATE = Ending Expiration Date [optional] 
  
 Note: If patient does not have any prescriptions, but has archived 
 prescriptions, a ^TMP($J,LIST,DFN,"ARC")="PATIENT HAS ARCHIVED PRESCRIPTION" 
 shall be defined. If SDATE is passed in, suspended RXs starting with this date
 shall be returned (^PS(55,DFN,"P","A")). If EDATE is passed in, RXs up to and
 including this date shall be returned (^PS(55,DFN,"P","A")).  
  
 Output: 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO PRESCRIPTION
 DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,.01)=RX #(52,.01)^IEN 
   ^TMP($J,LIST,DFN,IEN,1)=ISSUE DATE (52,1)^External Format (ex: Sep. 12, 
 1999) 
   ^TMP($J,LIST,DFN,IEN,2)=PATIENT (52,2)^NAME (2,.01) 
   ^TMP($J,LIST,DFN,IEN,3)=PATIENT STATUS (52,3)^NAME (53,.01) 
   ^TMP($J,LIST,DFN,IEN,4)=PROVIDER (52,4)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN,5)=CLINIC (52,5)^NAME (44,.01) 
   ^TMP($J,LIST,DFN,IEN,6)=DRUG (52,6)^GENERIC NAME (50,.01) 
   ^TMP($J,LIST,DFN,IEN,6.5)=TRADE NAME (52,6.5) 
   ^TMP($J,LIST,DFN,IEN,7)=QTY (52,7) 
   ^TMP($J,LIST,DFN,IEN,8)=DAYS SUPPLY (52,8) 
   ^TMP($J,LIST,DFN,IEN,9)=# OF REFILLS (52,9) 
   ^TMP($J,LIST,DFN,IEN,10.3)=ORDER CONVERTED (52,10.3) ^External Format for 
 the Set of Codes 
   ^TMP($J,LIST,DFN,IEN,10.6)=COPIES (52,10.6) 
   ^TMP($J,LIST,DFN,IEN,11)=MAIL/WINDOW (52,11)^External Format for the Set of
 Codes 
   ^TMP($J,LIST,DFN,IEN,16)=ENTERED BY (52,16)^NAME (200,.01) 
   ^TMP($J,LIST,DFN,IEN,17)=UNIT PRICE OF DRUG (52,17) 
   ^TMP($J,LIST,DFN,IEN,100)=STATUS (52,100)^External Format for the Set of 
 Codes 
   ^TMP($J,LIST,DFN,"ARC")="PATIENT HAS ARCHIVED PRESCRIPTION" 
   ^TMP($J,LIST,"B",RX #,IEN)="" 
VARIABLES: DFN                          TYPE: Both
 VARIABLES DESCRIPTION:   Internal entry number from the PATIENT file (#2)
 [required].  
VARIABLES: LIST                         TYPE: Both
 VARIABLES DESCRIPTION:   Subscript name used in the ^TMP global [required] 
VARIABLES: SDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   EXPIRATION DATE field (#26) from the PRESCRIPTION
 file (#52) using the ^PS(55,Patient,"P","A",Expiration Date,DA)
 cross-reference from PHARMACY PATIENT file (#55) when prescriptions are
 requested within a date range.  [optional] 
VARIABLES: EDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   EXPIRATION DATE field (#26) from the PRESCRIPTION
 file (#52) using the ^PS(55,Patient,"P","A",Expiration Date,DA)
 cross-reference from PHARMACY PATIENT file (#55) when prescriptions are
 requested within a date range.  [optional] 
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4821                            IA #: 4821
  DATE CREATED: DEC 07, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSO5241
  NAME: DBIA4821                        ID: PSO5241
 GENERAL DESCRIPTION:   The 'PEN' component returns data from the PENDING
 OUTPATIENT ORDERS (#52.41) File. The 'NONVA' component returns data from the
 NON-VA MEDS (#55.05) Subfile of the PHARMACY PATIENT (#55) File.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PEN(DFN,LIST,IEN,PLACER NUMBER)
 COMPONENT DESCRIPTION:   
  
 PEN^PSO5241(DFN,LIST,IEN,PLACER NUMBER) 
  
 Input: 
   DFN 
   LIST 
   IEN 
   PLACER NUMBER 
  
 Where: 
   DFN = Internal entry number of the PATIENT (#2) File [required] 
   LIST = Subscript name used in the ^TMP global [required] 
   IEN = Internal entry number in the PENDING 
         OUTPATIENT ORDERS (#52.41) File [optional] 
   PLACER NUMBER = Internal Entry Number of the ORDER (#100) File [optional] 
  
 Note: If IEN is passed in, PLACER NUMBER is ignored. If PLACER NUMBER is 
 passed in without IEN, a lookup is done on the ^PS(52.41,"B" cross-reference
 to find the order. If no IEN and no PLACER NUMBER are passed, the
 ^PS(52.41,"P" cross-reference is used to return all pending orders for the
 patient for only orders with one of these values in the ORDER TYPE (#2) Field: 
 NW:NEW ORDER, HD:HOLD, RNW:RENEW, RF:REFILL REQUEST 
VARIABLES: DFN                          TYPE: Both
 VARIABLES DESCRIPTION:   Internal entry number from the PATIENT (#2) File.
 [required] 
VARIABLES: LIST                         TYPE: Both
 VARIABLES DESCRIPTION:   Subscript name used in the ^TMP global. [required] 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number from the PENDING OUTPATIENT
 ORDERS (#52.41) File.  [optional] 
VARIABLES: PLACER NUMBER                TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number from the ORDERS (#100) File.
 [optional] 
VARIABLES: TMP($J,LIST)                 TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,DFN,0)=Total entries returned by patient
 or -1^NO DATA FOUND ^TMP($J,LIST,DFN,IEN,.01)=PLACER NUMBER (52.41,.01) 
 ^TMP($J,LIST,DFN,IEN,1)=PATIENT (52.41,1)^NAME (2,.01) 
 ^TMP($J,LIST,DFN,IEN,1.1)=PATIENT LOCATION (52.41,1.1)^NAME (44,.01) 
 ^TMP($J,LIST,DFN,IEN,2)=ORDER TYPE (52.41,2)^External Format for the Code 
 ^TMP($J,LIST,DFN,IEN,5)=PROVIDER (52.41,5)^NAME (200,.01) 
 ^TMP($J,LIST,DFN,IEN,6)=EFFECTIVE DATE (52.41,6)^External Format (ex: Sep. 12,
 1999) ^TMP($J,LIST,DFN,IEN,8)=PHARMACY ORDERABLE ITEM (52.41,8)^NAME
 (50.7,.01) ^DOSAGE FORM (50.7,.02) ^NAME (50.606,.01) 
 ^TMP($J,LIST,DFN,IEN,11)=DRUG (52.41,11) ^GENERIC NAME (50,.01) 
 ^TMP($J,LIST,DFN,IEN,12)=QTY (52.41,12) ^TMP($J,LIST,DFN,IEN,13)=# OF REFILLS
 (52.41,13) ^TMP($J,LIST,DFN,IEN,15)=LOGIN DATE (52.41,15)^External Format (ex: 
 Sep. 12, 1999) ^TMP($J,LIST,DFN,IEN,19)=PICKUP ROUTING (52.41,19)^External
 Format for the Code ^TMP($J,LIST,DFN,IEN,21)=Rx REFILL REQUEST (52.41,21) 
 ^TMP($J,LIST,DFN,IEN,22.1)=PREVIOUS ORDER # (52.41,22.1)^RX # (52,.01) 
 ^TMP($J,LIST,DFN,IEN,24,n)=DISPENSING INSTRUCTIONS (52.4124,.01) 
 ^TMP($J,LIST,DFN,IEN,26)=POSSIBLE FILLDATE (52.41,26)^External Format (ex:
 Sep. 12, 1999) ^TMP($J,LIST,DFN,IEN,100)=RELATED INSTITUTION (52.41,100)^NAME
 (4,.01) ^TMP($J,LIST,DFN,IEN,101)=DAY SUPPLY (52.41,101) 
 ^TMP($J,LIST,DFN,"B",PLACER NUMBER,IEN)="" 
COMPONENT/ENTRY POINT: NONVA(PSODFN,PSOLST,PSOSIEN,PSOPL)
 COMPONENT DESCRIPTION:   
  
 NONVA^PSO5241(PSODFN,PSOLST,PSOSIEN,PSOPL) 
  
 Input: 
   PSODFN 
   PSOLST 
   PSOSIEN 
   PSOPL 
  
 Where: 
   PSODFN = Internal entry number from the PATIENT (#2) File. [required] 
   PSOLST = Subscript name used in the ^TMP global. [required] 
   PSOSIEN = Internal entry number from the NON-VA MEDS (#55.05) Subfile 
             of the PHARMACY PATIENT (#55) File. [optional] 
   PSOPL = Internal entry number of the ORDER (#100) File. [optional] 
  
 Note: If PSOSIEN is passed in, PSOPL is ignored, and the NON-VA entry of that
 internal entry number (PSOSIEN) is returned. If PSOPL is passed in without
 PSOSIEN, the NON-VA entry with PSOPL in the ORDER NUMBER (#7) Field is
 returned. If no PSOSIEN and no PSOPL are passed, all NON-VA entries will be
 returned.  
VARIABLES: PSODFN                       TYPE: Both
 VARIABLES DESCRIPTION:   Internal entry number from the PATIENT (#2) File.
 [required] 
VARIABLES: PSOLST                       TYPE: Both
 VARIABLES DESCRIPTION:   Subscript name used in the ^TMP global.  [required] 
VARIABLES: PSOSIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number from the NON-VA MEDS (#55.05)
 Subfile of the PHARMACY PATIENT (#55) File. [optional] 
VARIABLES: PSOPL                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number from the ORDER (#100) File.
 [optional] 
VARIABLES: TMP($J,PSOLST)               TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,PSOLST,PSODFN,IEN,0)=Total entries returned
 or -1^NO DATA FOUND ^TMP($J,PSOLST,PSODFN,IEN,.01)=ORDERABLE ITEM
 (55.05,.01)^NAME (50.7,.01)^DOSAGE FORM (50.7,.02)^NAME(50.606,.01) 
 ^TMP($J,PSOLST,PSODFN,IEN,1)=DISPENSE DRUG (55.05,1) ^GENERIC NAME (50,.01) 
 ^TMP($J,PSOLST,PSODFN,IEN,2)=DOSAGE (55.05,2) 
 ^TMP($J,PSOLST,PSODFN,IEN,3)=MEDICATION ROUTE (55.05,3) 
 ^TMP($J,PSOLST,PSODFN,IEN,4)=SCHEDULE (55.05,4) 
 ^TMP($J,PSOLST,PSODFN,IEN,5)=STATUS (55.05,5)^External Format of the code.  
 ^TMP($J,PSOLST,PSODFN,IEN,6)=DISCONTINUED DATE (55.05,6)^External Format (ex:
 Sep. 12, 1999@11:10:36) ^TMP($J,PSOLST,PSODFN,IEN,7)=ORDER NUMBER (55.05,7) 
 ^TMP($J,PSOLST,PSODFN,IEN,8)=START DATE (55.05,8)^External Format (ex: Sep.
 12, 1999) ^TMP($J,PSOLST,PSODFN,IEN,10,n)=DISCLAIMER (55.052,.01) 
 ^TMP($J,PSOLST,PSODFN,IEN,11)=DOCUMENTED DATE (55.05,11)^External Format (ex:
 Sep. 12, 1999@11:10:36) ^TMP($J,PSOLST,PSODFN,IEN,12)=DOCUMENTED BY
 (55.05,12)^NAME(200,.01) ^TMP($J,PSOLST,PSODFN,IEN,13)=CLINIC (55.05,13)^NAME
 (44,.01) ^TMP($J,PSOLST,PSODFN,IEN,14,n)=COMMENTS (55.514,.01) 
 ^TMP($J,PSOLST,PSODFN,"B",ORDERABLE ITEM,IEN)="" 
  DATE ACTIVATED: JUN 01, 2020

NUMBER: 4822                            IA #: 4822
  DATE CREATED: DEC 07, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSO525AP
  NAME: DBIA4822                        ID: PSO525AP
 GENERAL DESCRIPTION:   The routine PSO525AP shall be used to return requested
 data elements for the RX SUSPENSE file (#52.5). Various data elements shall be
 returned by parameter passing. The following requirements shall describe what
 is passed in and what is returned.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SUS(LIST,DFN,IEN,RX#,SDATE,EDATE)
 COMPONENT DESCRIPTION:   SUS^PSO525AP(LIST,DFN,IEN,RX#,SDATE,EDATE) 
  
 Input: 
   LIST 
   DFN 
   IEN 
   RX# 
   SDATE 
   EDATE 
  
 Where: 
   LIST = Subscript name used in the ^TMP global [required] 
   DFN = IEN from the PATIENT file (#2) [optional] 
   IEN = Internal record number in RX SUSPENSE file (#52.5) [optional] 
   RX# = Pointer to PRESCRIPTION file (#52) [optional] 
   SDATE = Starting Suspense Date [optional] 
   EDATE = Ending Suspense Date [optional] 
  
 Note: If IEN is passed in, RX # is ignored. If RX # is passed in without IEN
 lookup is done on ^PS(52.5,"B" cross-reference. If no IEN and no RX # is
 passed, "AF" cross-reference shall be used to return suspended RXs. If SDATE
 is passed in, suspended RXs starting with this date shall be returned.  If
 EDATE is passed in, suspended RXs up to and including this date shall be 
 returned.  
  
 Output: 
   ^TMP($J,LIST,DFN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,DFN,IEN,.01)=RX # (52.5,01) 
   ^TMP($J,LIST,DFN,IEN,.02)=Suspense Date (52.5,.02)^External Format (ex: Sep.
 12, 1999) 
   ^TMP($J,LIST,DFN,IEN.05)=Partial (52.5,.05) 
   ^TMP($J,LIST,DFN,IEN,5)=Printed (52.5,2)^External Format for the Set of
 codes 
   ^TMP($J,LIST,DFN,IEN,3)=CMOP INDICATOR (52.5,3)^External Format for the Set
 of Codes 
   ^TMP($J,LIST,DFN,IEN,9)=Fill (52.5,9) 
   ^TMP($J,LIST,"B",RX#,IEN)="" 
VARIABLES: LIST                         TYPE: Both
 VARIABLES DESCRIPTION:   Subscript name used in the ^TMP global [required] 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number from the PATIENT file (#2)
 [optional] 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number from RX SUSPENSE file (#52.5)
 [optional] 
VARIABLES: RX#                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to PRESCRIPTION file (#52) [optional] 
VARIABLES: SDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   Starting suspense date if data is to be returned
 within date range using the SUSPENSE DATE field (#.02) C cross-reference from
 RX SUSPENSE file (#52.5). [optional] 
VARIABLES: EDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   Ending suspense date if data is to be returned within
 date range using the SUSPENSE DATE field (#.02) C cross-reference from RX
 SUSPENSE file (#52.5). [optional] 

NUMBER: 4823                            IA #: 4823
  DATE CREATED: DEC 07, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSO5252
  NAME: DBIA4823                        ID: PSO5252
 GENERAL DESCRIPTION:   This API shall return the following fields from the
 CLOZAPINE PRESCRIPTION OVERRIDES file (#52.52) for the IEN or free text entry
 received: DATE/TIME, PRESCRIPTION NUMBER, USER ENTERING, APPROVING TEAM
 MEMBER, REASON FOR LOCKOUT, and COMMENTS.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN(LIST,IEN,RX#,SDATE,EDATE)
 COMPONENT DESCRIPTION:   EN^PSO5252(LIST,IEN,RX#,SDATE,EDATE) 
  
 Input: 
   LIST 
   IEN 
   RX# 
   SDATE 
   EDATE 
  
 Where: 
   LIST = Subscript name used in the ^TMP global [required] 
   IEN = Internal record number in CLOZAPINE PRESCRIPTION OVERRIDES file 
 (#52.52) [optional] 
   RX# = Pointer to PRESCRIPTION file (#52) [optional] 
   SDATE = Starting Date [optional] 
   EDATE = Ending Date [optional] 
  
 Note: If RX # is passed in without IEN, lookup is done on ^PS(52.52,"A". If no
 IEN and no RX # is passed, "B" cross-reference shall be used to return 
 Override RXs.  
  
 Output: 
   ^TMP($J,LIST,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,IEN,.01)= DATE TIME (52.52,.01) 
   ^TMP($J,LIST,IEN,1)=PRESCRIPTION NUMBER (52.52,1)^RX # (52,.01) 
   ^TMP($J,LIST,IEN,2)=USER ENTERING (52.52,2)^NAME (200,.01) 
   ^TMP($J,LIST,IEN,3)=APPROVING TEAM MEMBER (52.52,3)^NAME (200,.01) 
  ^TMP($J,LIST,IEN,4)=REASON FOR LOCKOUT (52.52,4)^External Format for the Set
 of Codes 
   ^TMP($J,LIST,IEN,5)=COMMENTS (52.52,5) 
   ^TMP($J,LIST,"B",DATE TIME,IEN)="" 
VARIABLES: LIST                         TYPE: Both
 VARIABLES DESCRIPTION:   Subscript name used in the ^TMP global [required] 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number from CLOZAPINE PRESCRIPTION
 OVERRIDES file (#52.52) [optional] 
VARIABLES: RX#                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to PRESCRIPTION file (#52) [optional] 
VARIABLES: SDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   Starting date/time if data is to be returned within
 date range using the DATE TIME field (#.01) B cross-reference from CLOZAPINE
 PRESCRIPTION OVERRIDES file (#52.52). [optional] 
VARIABLES: EDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   Ending date/time if data is to be returned within
 date range using the DATE TIME field (#.01) B cross-reference from CLOZAPINE
 PRESCRIPTION OVERRIDES file (#52.52). [optional] 

NUMBER: 4824                            IA #: 4824
  DATE CREATED: DEC 07, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSO5291
  NAME: DBIA4824                        ID: PSO5291
 GENERAL DESCRIPTION:   This API shall return the following fields from the TPB
 ELIGIBILITY file (#52.91) for the IEN or free text entry received: PATIENT,
 DATE PHARMACY BENEFITS BEGAN, INACTIVATION OF BENEFITS DATE, INACTIVATION
 REASON CODE, DESIRED APPOINTMENT DATE, WAIT TYPE, STATION NUMBER, INSTITUTION,
 EXCLUSION REASON, PRIMARY CARE SCHEDULED APPT DATE, RX#, and DATE LETTER
 PRINTED.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PSO(PSOIEN,PSOTXT,LIST)
 COMPONENT DESCRIPTION:   PSO^PSO5291(PSOIEN,PSOTXT,LIST) 
  
 Input: 
   PSOIEN 
   PSOTXT 
   LIST 
  
 Where: 
   PSOIEN = Internal Entry Number in TPB ELIGIBILITY file (#52.91) [optional] 
   PSOTXT = Free text entry [optional] 
   LIST = Subscript name used in the ^TMP global [required] 
  
 Note: Either the IEN or free text entry must be present.  
  
 Output: 
   ^TMP($J,LIST,PSOIEN,0)=TOTAL entries returning or -1^NO DATA FOUND 
   ^TMP($J,LIST,PSOIEN,.01)=PATIENT (IEN) (52.91,.01)^NAME (2,.01) 
   ^TMP($J,LIST,PSOIEN,1)=DATE PHARMACY BENEFIT BEGAN(52.91,1)^External Format
 (ex: Sep. 12, 1999) 
   ^TMP($J,LIST,PSOIEN,2)=INACTIVATION OF BENEFIT DATE(52.91,2)^External Format
 (ex: Sep. 12, 1999) 
   ^TMP($J,LIST,PSOIEN,3)=INACTIVATION REASON CODE (52.91,3)^External Format 
 for the Set of Codes 
   ^TMP($J,LIST,PSOIEN,4)=DESIRED APPOINTMENT DATE(52.91,4)^External Format 
 (ex: Sep. 12, 1999) 
   ^TMP($J,LIST,PSOIEN,5)=WAIT TYPE (52.91,5)^External Format for the Set of 
 Codes 
   ^TMP($J,LIST,PSOIEN,6)=STATION NUMBER(52.91,6) 
   ^TMP($J,LIST,PSOIEN,7)=INSTITUTION (52.91,7)^NAME (4,.01) 
   ^TMP($J,LIST,PSOIEN,8)=EXCLUSION REASON (52.91,8)^External Format for the 
 Set of Codes 
   ^TMP($J,LIST,PSOIEN,9)=PRIMARY CARE SCHEDULE APT DATE(52.91,9)^External 
 Format (ex: Sep. 12, 1999) 
   ^TMP($J,LIST,PSOIEN,10)=RX #(52.91,10) 
   ^TMP($J,LIST,PSOIEN,11)=DATE LETTER PRINTED(52.91,11)^External Format (ex:
 Sep. 12, 1999) 
   ^TMP($J,LIST,"B",PATIENT,PSOIEN)="" 
VARIABLES: PSOIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number [optional] 
VARIABLES: PSOTXT                       TYPE: Input
 VARIABLES DESCRIPTION:   Free text entry of .01 field from TPB ELIGIBILITY
 file (#52.91) [optional] 
VARIABLES: LIST                         TYPE: Both
 VARIABLES DESCRIPTION:   Subscript name used in the ^TMP global [required] 

NUMBER: 4825                            IA #: 4825
  DATE CREATED: DEC 07, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSO53
  NAME: DBIA4825                        ID: PSO53
 GENERAL DESCRIPTION:   This API shall be provided to scan the NAME field
 (#.01) of RX PATIENT STATUS file (#53) utilizing the "B" cross-reference and
 return a listing of records for a specific value based on logical criteria
 received for the patient status. The following fields shall be included: NAME,
 ABBR, DAYS SUPPLY, REFILLS, RENEWABLE, SC/A&A/OTHER/INPATIENT/NVA, EXEMPT FROM 
 COPAYMENT, and EXEMPT FROM CHAMPUS BILLING.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PSO(PSOIEN,PSOTXT,LIST)
 COMPONENT DESCRIPTION:   PSO^PSO53(PSOIEN,PSOTXT,LIST) 
  
 Input: 
  PSOIEN 
  PSOTXT 
  LIST 
  
 Where: 
  PSOIEN = Internal Entry Number [optional] 
  PSOTXT = Free text entry [optional] 
  LIST = Subscript name used in the ^TMP global [required] 
  
 Output: 
  ^TMP($J,LIST,PSOIEN,0)=TOTAL entries returning or -1^NO DATA FOUND 
  ^TMP($J,LIST,PSOIEN,.001)=NUMBER(53,.001) 
  ^TMP($J,LIST,PSOIEN,.01)=NAME(53,.01) 
  ^TMP($J,LIST,PSOIEN,2)=ABBR(53,2) 
  ^TMP($J,LIST,PSOIEN,3)=DAYS SUPPLY(53,3) 
  ^TMP($J,LIST,PSOIEN,4)=REFILLS(53,4) 
  ^TMP($J,LIST,PSOIEN,5)=RENEWABLE (53,5)^External Format for the Set of Codes 
  ^TMP($J,LIST,PSOIEN,6)=SC/A&A/OTHER/INPATIENT/NVA (53,6)^External Format for
 the Set of Codes 
  ^TMP($J,LIST,PSOIEN,15)=EXEMPT FROM COPAYMENT (53,15)^External Format for the
 Set of Codes 
  ^TMP($J,LIST,PSOIEN,16)=EXEMPT FROM CHAMPUS BILLING (53,16)^External Format 
 for the Set of Codes 
  ^TMP($J,LIST,"B",NAME,PSOIEN)="" 
VARIABLES: PSOIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number [optional] 
VARIABLES: PSOTXT                       TYPE: Input
 VARIABLES DESCRIPTION:   Free text entry of .01 field from RX PATIENT STATUS
 file (#53) [optional] 
VARIABLES: LIST                         TYPE: Both
 VARIABLES DESCRIPTION:   Subscript name used in the ^TMP global [required] 

NUMBER: 4826                            IA #: 4826
  DATE CREATED: NOV 15, 2005
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSS55
  NAME: DBIA4826                        ID: PSS55
 GENERAL DESCRIPTION:   This DBIA is provided by PDM (Pharmacy Data Management)
 as an API to the PHARMACY PATIENT file (#55). This API is to used in the
 future by all packages accessing this file as all the Pharmacy packages are
 being re-engineered.  
  STATUS: Active
COMPONENT/ENTRY POINT: PSS431(DFN,PO,PSDATE,PODATE,LIST)
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Patient [REQUIRED] 
VARIABLES: PO                           TYPE: Input
 VARIABLES DESCRIPTION:   Order # [optional] 
VARIABLES: PSDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   Start Date [optional] 
VARIABLES: PEDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   End Date [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript name used in ^TMP global [REQUIRED] 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returned by patient or
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST ,PO,.01)=ORDER NUMBER(55.06,.01) 
  
 ^TMP($J,LIST,PO,.5)=PATIENT NAME (DFN) (55.06,.5)^NAME (2,.01) 
  
 ^TMP($J,LIST,PO,1)=PROVIDER (pointer value) (55.06,1)^NAME (200,.01) 
  
 ^TMP($J,LIST,PO,3)=MED ROUTE (pointer value) (55.06,3) ^NAME (51.2,.01) 
  
 ^TMP($J,LIST,PO,4)=TYPE (55.06,4)^External Format for the Set of Codes 
  
 ^TMP($J,LIST,PO,5)=SELF MED (55.06,5)^External Format for the Set of Codes 
  
 ^TMP($J,LIST,PO,6)=HOSPITAL SUPPLIED SELF MED (55.06,6)^External Format for
 the Set of Codes 
  
 ^TMP($J,LIST,PO,7)=SCHEDULE TYPE (55.06,7)^External Format for the Set of
 Codes 
  
 ^TMP($J,LIST,PO,11)=DAY LIMIT(55.06,11) 
  
 ^TMP($J,LIST,PO,12)=DOSE LIMIT(55.06,12) 
  
 ^TMP($J,LIST,PO,27)=ORDER DATE(55.06,27)^External Format (ex: Sep. 12, 1999) 
  
 ^TMP($J,LIST,PO,27.1)=LOG-IN DATE(55.06,27.1)^External Format (ex: Sep. 12,
 1999) 
  
 ^TMP($J,LIST,PO,28)=STATUS (55.06,28)^External Format for the Set of Codes 
  
 ^TMP($J,LIST,PO,"DDRUG",0)= Total entries returned or -1 ^NO DATA FOUND 
  
 ^TMP($J,LIST,PO,"DDRUG",n,.01)=DISPENSE DRUG (55.07,.01)^GENERIC NAME (50,.01) 
  
 ^TMP($J,LIST,PO,"DDRUG",n,.02)=UNITS PER DOSE(55.07,.02) 
  
  
 ^TMP($J,LIST,PO,"DDRUG",n,.03)=INACTIVE DATE(55.07,.03)^External Format (ex:
 Sep. 12, 1999) 
  
 ^TMP($J,LIST,PO,"DDRUG",n,.04)=TOTALS UNITS DISPENSED(55.07,.04) 
  
 ^TMP($J,LIST,PO,"DDRUG",n,.05)=UNITS CALLED FOR(55.07,.05) 
  
 ^TMP($J,LIST,PO,"DDRUG",n,.06)=UNITS ACTUALLY DISPENSED(55.07,.06) 
  
 ^TMP($J,LIST,PO,"DDRUG",n,.07)=TOTAL RETURNS(55.07,.07) 
  
 ^TMP($J,LIST,PO,"DDRUG",n,.08)=RETURNS(55.07,.08) 
  
 ^TMP($J,LIST,PO,"DDRUG",n,.09)=PRE-EXCHANGE UNITS(55.07,.09) 
  
 ^TMP($J,LIST,PO,"DDRUG",n,.1)=TOTALS EXTRA UNITS DISPENSED(55.07,.1) 
  
 ^TMP($J,LIST,PO,"DDRUG",n,.11)=EXTRA UNITS DISPENSED(55.07,.11) 
  
 ^TMP($J,LIST,PO,"DDRUG",n,.12)=TOTAL PRE-EXCHANGE UNITS(55.07,.12) 
  
 ^TMP($J,LIST,"B",ORDER NUMBER)="" 
COMPONENT/ENTRY POINT: PSS432(DFN,PO,LIST)
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Patient [REQUIRED] 
VARIABLES: PO                           TYPE: Input
 VARIABLES DESCRIPTION:   Order # [optional] If left blank, all active orders
 will be returned 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript name used in ^TMP global [REQUIRED] 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returned by patient or
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST,PO,.01)=ORDER NUMBER(55.06,.01) 
  
 ^TMP($J,LIST,PO,.5)=PATIENT NAME (DFN) (55.06,.5)^NAME (2,.01) 
  
 ^TMP($J,LIST,PO,1)=PROVIDER (55.06,1) ^NAME (200,.01) 
  
 ^TMP($J,LIST,PO,3)=MED ROUTE (55.06,3) ^NAME (51.2,.01) 
  
 ^TMP($J,LIST,PO,4)=TYPE (55.06,4)^External Format for the Set of Codes 
   
 ^TMP($J,LIST,PO,5)=SELF MED (55.06,5)^External Format for the Set of Codes 
  
 ^TMP($J,LIST,PO,6)=HOSPITAL SUPPLIED SELF MED (55.06,6)^External Format for
 the Set of Codes 
  
 ^TMP($J,LIST,PO,7)=SCHEDULE TYPE  (55.06,7)^External Format for the Set of
 Codes 
  
 ^TMP($J,LIST,PO,11)=DAY LIMIT(55.06,11) 
  
 ^TMP($J,LIST,PO,12)=DOSE LIMIT(55.06,12) 
  
 ^TMP($J,LIST,PO,26)=SCHEDULE (55.06,26) 
  
 ^TMP($J,LIST,PO,27)=ORDER DATE(55.06,27)^External Format (ex: Sep. 12, 1999) 
  
 ^TMP($J,LIST,PO,27.1)=LOG-IN DATE(55.06,27.1)^External Format (ex: Sep. 12,
 1999) 
  
 ^TMP($J,LIST,PO,28)=STATUS (55.06,28)^External Format for the Set of Codes 
  
 ^TMP($J,LIST,"B",ORDER NUMBER)="" 
COMPONENT/ENTRY POINT: PSS433(DFN,LIST)
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Patient [REQUIRED] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript name used in ^TMP global [REQUIRED] 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returned by patient or
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST,PO,.5)=PATIENT NAME (DFN) (55.06,.5)^NAME (2,.01) 
  
 ^TMP($J,LIST,PO,9)=ORIGINAL WARD (55.06,9) ^NAME (42,.01) 
  
 ^TMP($J,LIST,PO,25)=PREVIOUS STOP DATE/TIME(55.06,25)^External Format (ex:
 Sep. 12, 1999) 
  
 ^TMP($J,LIST,PO,26)=SCHEDULE(55.06,26) 
  
 ^TMP($J,LIST,PO,34)=STOP DATE/TIME(55.06,34)^External Format (ex: Sep. 12,
 1999) 
  
 ^TMP($J,LIST,PO,41)=ADMIN TIMES(55.06,41) 
  
 ^TMP($J,LIST,PO,42)=FREQUENCY (in minutes)(55.06,42) 
  
 ^TMP($J,LIST,PO,70)=ORIGINAL START DATE/TIME(55.06,70)^External Format (ex:
 Sep. 12, 1999) 
  
 ^TMP($J,LIST,"B",ORDER NUMBER)="" 
COMPONENT/ENTRY POINT: PSS435(DFN,PO,LIST)
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Patient [REQUIRED] 
VARIABLES: PO                           TYPE: Input
 VARIABLES DESCRIPTION:   Order # [optional] If left blank, all active orders
 will be returned. 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript name used in ^TMP global [REQUIRED] 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returned by patient or
 -1^NO DATA FOUND 
   
 ^TMP($J,LIST,PO,.01)=ORDER NUMBER(55.01,.01) 
  
 ^TMP($J,LIST,PO,.02)=START DATE/TIME(55.01,.02)^External Format (ex: Sep. 12,
 1999) 
  
 ^TMP($J,LIST,PO,.03)=STOP DATE/TIME(55.01,.03)^External Format (ex: Sep. 12,
 1999) 
  
 ^TMP($J,LIST,PO,.04)=TYPE (55.01,.04)^External Format for the Set of Codes 
  
 ^TMP($J,LIST,PO,.06)=PROVIDER (55.01,.06)^NAME (200,.01) 
  
 ^TMP($J,LIST,PO,.08)=INFUSION RATE(55.01,.08) 
  
 ^TMP($J,LIST,PO,.09)=SCHEDULE(55.01,.09) 
  
 ^TMP($J,LIST,PO,.12)=ADMINISTRATION TIMES(55.01,.12) 
  
 ^TMP($J,LIST,PO,.17)=SCHEDULE INTERVAL(55.01,.17) 
  
 ^TMP($J,LIST,PO,.24)=CUMULATIVE DOSES(55.01,.24) 
  
 ^TMP($J,LIST,PO,9)=ORIGINAL WARD (55.01,9)^NAME (42,.01) 
  
 ^TMP($J,LIST,PO,31)=OTHER PRINT INFO (55.01,31) 
  
 ^TMP($J,LIST,PO,100)=STATUS (55.01,100)^External Format for the Set of Codes 
  
 ^TMP($J,LIST,PO,104)=WARD(55.01,104) 
  
 ^TMP($J,LIST,PO,106)=CHEMOTHERAPY TYPE (55.01,106)^External Format for the Set
 of Codes 
  
 ^TMP($J,LIST,PO,108)=INTERMITTENT SYRINGE(55.01,108) 
  
 ^TMP($J,LIST,PO,110)=ORDERS FILE ENTRY(55.01,110) 
  
 ^TMP($J,LIST,PO,112)=ATZERO (55.01,112)^External Format for the Set of Codes 
  
 ^TMP($J,LIST,PO,120)=OERR HOLD FLAG  (55.01,120)^External Format for the Set
 of Codes 
  
 ^TMP($J,LIST,PO,121)=AUTO DC (55.01,121)^External Format for the Set of Codes 
  
 ^TMP($J,LIST,PO,132)=MED ROUTE (55.01,132)^NAME (51.2,.01) 
  
 ^TMP($J,LIST,"B",ORDER NUMBER)="" 
COMPONENT/ENTRY POINT: PSS436(DFN,ORDER,LIST)
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number of patient in PHARMACY PATIENT
 file [REQUIRED] 
VARIABLES:  
VARIABLES: ORDER                        TYPE: Input
 VARIABLES DESCRIPTION:   ORDER NUMBER [REQUIRED] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript name used in ^TMP global [REQUIRED] 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returned by patient or
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST,ORDER,.01)=ORDER NUMBER(55.01,.01) 
  
 ^TMP($J,LIST,ORDER,.02)=START DATE/TIME(55.01,.02)^External Format (ex: Sep.
 12, 1999) 
  
 ^TMP($J,LIST,ORDER,.03)=STOP DATE/TIME (55.01,.03)^External Format (ex: Sep.
 12, 1999) 
  
 ^TMP($J,LIST,ORDER,.04)=TYPE (55.01,.04)^External Format for the Set of Codes 
  
 ^TMP($J,LIST,ORDER,.06)=PROVIDER(55.01,.06)^NAME (200,.01) 
  
 ^TMP($J,LIST,ORDER,.08)=INFUSION RATE(55.01,.08) 
  
 ^TMP($J,LIST,ORDER,.09)=SCHEDULE(55.01,.09) 
  
 ^TMP($J,LIST,ORDER,.12)=ADMINISTRATION TIMES(55.01,.12) 
  
 ^TMP($J,LIST,ORDER,.17)=SCHEDULE INTERVAL(55.01,.17) 
  
 ^TMP($J,LIST,ORDER,.24)=CUMULATIVE DOSES(55.01,.24) 
  
 ^TMP($J,LIST,ORDER,9)=ORIGINAL WARD (55.01,9)^NAME (42,.01) 
  
 ^TMP($J,LIST,ORDER,31)=OTHER PRINT INFO (55.01,31) 
  
 ^TMP($J,LIST,ORDER,100)=STATUS (55.01,100)^External Format for the Set of
 Codes 
  
 ^TMP($J,LIST,ORDER,104)=WARD(55.01,104) 
  
  
 ^TMP($J,LIST,ORDER,106)=CHEMOTHERAPY TYPE (55.01,106)^External Format for the
 Set of Codes 
  
 ^TMP($J,LIST,ORDER,108)=INTERMITTENT SYRINGE (55.01,108)^External Format for
 the Set of Codes 
  
 ^TMP($J,LIST,ORDER,110)=ORDERS FILE ENTRY(55.01,110) 
  
 ^TMP($J,LIST,ORDER,112)=ATZERO  (55.01,112)^External Format for the Set of
 Codes ^TMP($J,LIST,ORDER,120)=OERR HOLD FLAG  (55.01,120)^External Format for
 the Set of Codes 
  
 ^TMP($J,LIST,ORDER,121)=AUTO DC  (55.01,121)^External Format for the Set of
 Codes 
  
 ^TMP($J,LIST,ORDER,132)=MED ROUTE (55.01,132)^NAME (51.2,.01) 
  
 ^TMP($J,LIST,ORDER,147)=BCMA EXPIRED FLAG  (55.01,147)^External Format for the
 Set of Codes 
  
 ^TMP($J,LIST,IEN,"ADD",0)=Total entries returned or -1^NO DATA FOUND 
  
 ^TMP($J,LIST,ORDER,"ADD",n1,.01)=ADDITIVE (55.02,.01)^PRINT NAME (52.6,.01) 
  
 ^TMP($J,LIST,ORDER,"ADD",n1,.02)=STRENGTH(55.02,.02) 
  
 ^TMP($J,LIST,ORDER,"ADD",n1,.03)=BOTTLE(55.02,.03) 
  
 ^TMP($J,LIST,IEN,"SOL",0)=Total entries returned or -1^NO DATA FOUND 
  
 ^TMP($J,LIST,ORDER,"SOL",n2,.01)=SOLUTION (55.11,.01)^PRINT NAME (52.7,.01) 
  
 ^TMP($J,LIST,ORDER,"SOL",n2,1)=VOLUME(55.11,1) 
  
 ^TMP($J,LIST,"B",ORDER NUMBER)="" 

NUMBER: 4827                            IA #: 4827
  DATE CREATED: DEC 07, 2005            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSO59
  NAME: OUTPATIENT SITE FILE            ID: PSO59
 GENERAL DESCRIPTION:   This API shall return the following fields from the
 OUTPATIENT SITE file (#59) for the IEN or free text entry received: NAME,
 MAILING FRANK STREET ADDRESS, AREA CODE, PHONE NUMBER, MAILING FRANK ZIP+4
 CODE, SITE NUMBER, MAILING FRANK CITY, MAILING FRANK STATE, SITE DEA NUMBER,
 RELATED INSTITUTION, NPI INSTITUTION, IB SERVICE/SECTION and NCPDP NUMBER.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PSS(PSOIEN,PSOTXT,LIST)
 COMPONENT DESCRIPTION:   PSS^PSO59(PSOIEN,PSOTXT,LIST) 
  
 Input: 
   PSOIEN 
   PSOTXT 
   LIST 
  
 Where: 
   PSOIEN = Internal Entry Number in OUTPATIENT SITE file (#59) [optional] 
   PSOTXT = Free text entry (a value of "??" may be used)  [optional] 
   LIST = Subscript name used in the ^TMP global [required] 
  
 Note: Either the IEN or free text entry must be present.  
  
 Output: 
   ^TMP($J,LIST,PSOIEN,0)=Total entries returned by patient or -1^NO DATA FOUND 
   ^TMP($J,LIST,PSOIEN,.01)=NAME(59,.01) 
   ^TMP($J,LIST,PSOIEN,.02)=MAILING FRANK STREET ADDRESS(59,.02) 
   ^TMP($J,LIST,PSOIEN,.03)=AREA CODE (59,.03) 
   ^TMP($J,LIST,PSOIEN,.04)=PHONE NUMBER (59,.04) 
   ^TMP($J,LIST,PSOIEN,.05)=MAILING FRANK ZIP+4 CODE(59,.05) 
   ^TMP($J,LIST,PSOIEN,.06)=SITE NUMBER(59,.06) 
   ^TMP($J,LIST,PSOIEN,.07)=MAILING FRANK CITY(59,.07) 
   ^TMP($J,LIST,PSOIEN,.08)=MAILING FRANK STATE (59,.08)^NAME (5,.01) 
   ^TMP($J,LIST,PSOIEN,1)=SITE DEA NUMBER (59,1) 
   ^TMP($J,LIST,PSOIEN,2)=SITE (NATIONAL NAME)(59,2)^NAME (736,.01) <***See 
 note below***> 
   ^TMP($J,LIST,PSOIEN,100)=RELATED INSTITUTION (59,100)^NAME (4,.01) 
   ^TMP($J,LIST,PSOIEN,101)=NPI INSTITUTION (59,101)^NAME (4,.01) 
   ^TMP($J,LIST,PSOIEN,1003)=IB SERVICE/SECTION (59,1003)^NAME (49,.01) 
   ^TMP($J,LIST,PSOIEN,1008)=NCPDP NUMBER (59,1008) 
   ^TMP($J,LIST,"B",NAME,PSOIEN)="" 
  
 Note: The SITE (NATIONAL NAME) field (#2) of the OUTPATIENT SITE file (#59)
 points to the QUIC SORT DATA file (#736), which no longer exists.  Therefore,
 the PSO59 routine will no longer return the ^TMP($J,LIST,PSOIEN,2) node.  
                                                             .
VARIABLES: PSOIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number [optional] 
VARIABLES: PSOTXT                       TYPE: Input
 VARIABLES DESCRIPTION:   Free text entry of .01 field from OUTPATIENT SITE
 file (#59) or a value of "??" may be used [optional] 
VARIABLES: LIST                         TYPE: Both
 VARIABLES DESCRIPTION:   Subscript name used in the ^TMP global [required] 
  DATE ACTIVATED: FEB 16, 2011

NUMBER: 4828                            IA #: 4828
  DATE CREATED: NOV 15, 2005
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSS59P7
  NAME: DBIA4828                        ID: PSS59P7
 GENERAL DESCRIPTION:   This DBIA is provided by PDM (Pharmacy Data Management)
 as an API to the PHARMACY SYSTEM file (#59.7). This API is to used in the
 future by all packages accessing this file as all the Pharmacy packages are
 being re-engineered.  
  STATUS: Active
COMPONENT/ENTRY POINT: PSS(PSSIEN,PSSTXT,LIST)
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number from PHARMACY SYSTEM file
 [optional] 
VARIABLES: PSSTXT                       TYPE: Input
 VARIABLES DESCRIPTION:   Free text entry [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript name used in ^TMP global [REQUIRED] 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,PSOIEN,40.1)=ADMISSION CANCEL OF RXS
 (59.7,40.1 - S)^External Format for the Set of Codes 
  
 ^TMP($J,LIST,PSOIEN,49.99)=OUTPATIENT VERSION(59.7,49.99) 
  
 ^TMP($J,LIST,PSSIEN,81)=ORDERABLE ITEM STATUS TRACKER (59.7,81)^External
 Format for the Set of Codes 
  
 ^TMP($J,LIST,"B",SITE NAME,PSOIEN)="" 

NUMBER: 4829                            IA #: 4829
  DATE CREATED: FEB 14, 2006            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSN5067
  NAME: DBIA4829                        ID: PSN5067
 GENERAL DESCRIPTION:   This DBIA is provided by NDF (National Drug File) as an
 API to the NDC/UPN file (#50.67). This API is to used in the future by all
 packages accessing this file as all the Pharmacy packages are being
 re-engineered.  
  STATUS: Active
COMPONENT/ENTRY POINT: ALL(PSNIEN,PSNFT,PSNFL,LIST)
 COMPONENT DESCRIPTION:   This component will return data from the NDC/UPN file
 (#50.67).  
VARIABLES: PSNIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSNIEN = Internal Entry Number from the NDC/UPN file
 (#50.67). If a value is passed in for PSNIEN, then any value passed in for the
 PSNFT parameter will be ignored. [optional] 
VARIABLES: PSNFT                        TYPE: Input
 VARIABLES DESCRIPTION:   PSNFT = TRADE NAME field (#4) of the NDC/UPN file
 (#50.67) (a value of "??" may be used). This value will be ignored if a value
 for PSNIEN is passed in.[optional] 
VARIABLES: PSNFL                        TYPE: Input
 VARIABLES DESCRIPTION:   PSNFL = Inactivation date: A null value will return
 all entries (entry of a FileMan format date (ex: 3030917) will return active
 entries after this date) [optional] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = array name defined by the calling application
 [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries returned or -1^NO DATA
 FOUND 
                             
 ^TMP($J,LIST,PSNIEN,.01)=SEQUENCE NUMBER(50.67,.01) 
                             
 ^TMP($J,LIST,PSNIEN,1)=NDC(50.67,1) 
  
 ^TMP($J,LIST,PSNIEN,2)=UPN(50.67,2) 
  
 ^TMP($J,LIST,PSNIEN,3)=MANUFACTURER(50.67,3)^NAME(55.95,.01) 
  
 ^TMP($J,LIST,PSNIEN,4)=TRADE NAME(50.67,4) 
  
 ^TMP($J,LIST,PSNIEN,5)=VA PRODUCT NAME(50.67,5)^NAME(50.68,.01) 
  
 ^TMP($J,LIST,PSNIEN,7)=INACTIVATION DATE(50.67,7)^External format (ex: SEP
 12,1999) 
  
 ^TMP($J,LIST,PSNIEN,8)=PACKAGE SIZE(50.67,8)^NAME(50.609,.01) 
  
 ^TMP($J,LIST,PSNIEN,9)=PACKAGE TYPE(50.67,9)^NAME(50.608,.01) 
  
 ^TMP($J,LIST,PSNIEN,10)=OTX/RX INDICATOR(50.67,10)^External format for the set
 of codes 
  
 ^TMP($J,LIST,"B",TRADE NAME,PSNIEN)= "" 
  
 Note: The "B" cross-reference uses the TRADE NAME field (#4) as the data 
 value. The TRADE NAME field (#4) is not a required field.  

NUMBER: 4830                            IA #: 4830
  GLOBAL ROOT: A7RCP(                   DATE CREATED: NOV 03, 2005
  CUSTODIAL PACKAGE: NDBI               USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: MPI HEC Enumeration Project/NDBI Global
  ID: A7RCP(
GLOBAL REFERENCE: A7RCP('B',<station#>,IEN)
 GLOBAL DESCRIPTION:   
  The 'B' cross reference is used to get the site IEN.  
GLOBAL REFERENCE: A7RCP(IEN,1,2,1,DFN,1)
 GLOBAL DESCRIPTION:   
  Given a specific site IEN and DFN from the legacy site, this 
  node contains the DFN for the patient at the primary site in 
  piece 1, which is a pointer to the PATIENT file (#2).  
 GENERAL DESCRIPTION:   
  This IA is for the Master Patient Index (MPI) Health Eligibility 
  Center (HEC) Enumeration project.  
   
  There are approximately 29,000 patient entries, identified at the HEC 
  from legacy systems, for which the primary site is not known on the HEC.  
  These patients need to be identified on the primary VistA system so 
  they can be added to the 1.6 million HEC patients to be assigned ICNs.  
  This needs to be done prior to the beginning of the HEC enumeration.  
  Information for these patients may be available in the NDBI POINTER 
  CONVERSION file (#17002.2) on the primary VistA system.  
   
  From the Master Patient Index (MPI), a remote request can be sent to 
  an integrated facility for the identified HEC legacy patient entries.  
  A Remote Procedure Call (RPC) on the local VistA system will search 
  the NDBI POINTER CONVERSION file (#17002.2) and return to the MPI the 
  DFN for that entry in the primary site if it is available.  This RPC 
  will only be used at selected integrated sites.  
   
  The Master Patient Index VistA package references a National Database 
  Integration global: ^A7RCP.  
   
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: A7RCP
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA

NUMBER: 4831                            IA #: 4831
  DATE CREATED: NOV 30, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: GMV_VitalsViewEnter.dll
 GENERAL DESCRIPTION:   This integration agreement allows the subscribing
 package to call the Dynamic Link Library (DLL) file named
 GMV_VitalsViewEnter.dll. This DLL is a Graphical User Interface (GUI) for
 entering and displaying patient vitals information.  
  
 This DLL is written in Delphi. It is called from another Delphi application.
 The entry points and input variables are Delphi, not M.  
  
 The following GMV-namespaced Remote Procedure Calls must be in the RPC (#320)
 field of the OPTION (#19) file entry used to create the Broker context. They
 are: 
  
  GMV ADD VM 
  GMV CONVERT DATE 
  GMV GET CATEGORY IEN 
  GMV GET CURRENT TIME 
  GMV GET VITAL TYPE IEN 
  GMV LATEST VM 
  GMV MANAGER 
  GMV PARAMETER 
  GMV USER 
  GMV VITALS/CAT/QUAL 
  GMV V/M ALLDATA 
  GMV EXTRACT REC 
  GMV MARK ERROR 
  GMV ALLERGY 
  GMV DLL VERSION 
  GMV LOCATION SELECT 
  GMV CLOSEST READING  [added to the list on 6/23/09] 
  
 These additional Remote Procedure Calls must be in the RPC (#320) field of the
 OPTION (#19) file entry used to create the Broker context. They are: 
  
  ORWPT PTINQ 
  VAFCTFU CONVERT DFN TO ICN 
  VAFCTFU CONVERT ICN TO DFN 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VitalsLite
COMPONENT/ENTRY POINT: GMV_VitalsViewDLG(
 COMPONENT DESCRIPTION:   This entry point opens up a data display containing a
 graph and grid containing the patient's data.  
  
 All of the input variables for this entry point are required. 
  
 The input variables are in the following order: 
  aBroker 
  aDFN 
  aLocation 
  DateStart 
  DateStop 
  aSignature 
  aContextIn 
  aContextOut 
  aName 
  anInfo 
  aHospitalName 
VARIABLES: aDFN                         TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This is a Patient (#2)
 file IEN. (Required) 
VARIABLES: aLocation                    TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. Hospital Location (#44)
 file IEN. (Required).  
VARIABLES: DateStart                    TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This is the start of a
 date range in mm/dd/yy format. (Required).  
VARIABLES: DateStop                     TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This is the end of a
 date range in mm/dd/yy format. (Required) 
VARIABLES: aSignature                   TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This is a string of
 characters identifying the calling package (e.g., CPRS). (Required) 
VARIABLES: aContextIn                   TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This is the name of an
 option in the Option (#19) file that identifies the Broker context being used
 when entering the DLL (e.g., OR CPRS GUI CHART). (Required) 
VARIABLES: aContextOut                  TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This is the name of an
 option in the Option (#19) file that identifies the Broker context value being
 used when exiting the DLL (e.g., OR CPRS GUI CHART). (Required) 
VARIABLES: aName                        TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This is the patient's
 name (File 2, Field .01). (Required).  
VARIABLES: anInfo                       TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This is the patient's
 social security number (e.g., 000-00-0000) (Required) 
VARIABLES: aHospitalName                TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This is a two part
 variable. The first part contains the name of a hospital location (File 44,
 Field .01). The second part is an abbreviation for a vital type (File 120.51,
 Field 1). The DLL will use the hospital location and vital abbreviation as
 default values.  (Required).  
  
 Example: MICU^P 
VARIABLES: aBroker                      TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is const. This is the Broker
 instance value of TRPCBroker. (Required) 
COMPONENT/ENTRY POINT: GMV_VitalsEnterDLG(
 COMPONENT DESCRIPTION:   This entry point opens up a data input template for
 the user to begin entering patient vitals data.  
  
 All of the input variables for this entry point are required. 
  
 The input variables are in the following order: 
   aBroker 
   aPatient                                       
   aLocation  
   aTemplate  
   aSignature  
   aDateTime 
   aPatientName      
   aPatientInfo 
VARIABLES: aBroker                      TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is const. This is the Broker
 instance value of TRPCBroker. (Required) 
VARIABLES: aPatient                     TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This is a Patient (#2)
 file IEN (Required).  
VARIABLES: aLocation                    TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This is a hospital
 location (File 44) IEN.  (Required) 
VARIABLES: aTemplate                    TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This is a null value
 (Required).  
VARIABLES: aSignature                   TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This is a string of
 characters identifying the calling package (e.g., CPRS). (Required).  
VARIABLES: aDateTime                    TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is TDateTime. This is a date/time
 in Microsoft date/time format. (Required).  
  
 Example: 38656.59678 
VARIABLES: aPatientName                 TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This is the patient's
 name (File 2, Field .01). (Required).  
VARIABLES: aPatientInfo                 TYPE: Input
 VARIABLES DESCRIPTION:   The variable type is String. This variable contains a
 string of characters that identify the following three pieces of patient
 information; social security number, date of birth and age (e.g., 000-00-0000
 MAY 20, 1966 (39)). (Required) 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JUN 23, 2009

NUMBER: 4832                            IA #: 4832
  DATE CREATED: JAN 05, 2006            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: COMMON FILES
 GENERAL DESCRIPTION:   Packages may place their common files under 
  Program Files\VistA\Common Files\ 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DLL
KEYWORDS: COMMON FILES
KEYWORDS: GMV_VitalsViewEnter.dll
KEYWORDS: GMV_VitalsViewEnter.hlp
KEYWORDS: GMV_VitalsViewEnter.cnt
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
 SUBSCRIBING DETAILS:   GMV_VitalsViewEnter.dll and GMV_VitalsViewEnter.hlp and
 GMV_VitalsViewEnter.cnt 

NUMBER: 4833                            IA #: 4833
  DATE CREATED: NOV 02, 2005
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMV3PST
  NAME: ADDRPCS FOR GUI 26              ID: GMV3PST
 GENERAL DESCRIPTION:   This Integration Agreement is for the sole purpose of
 allowing the CPRS GUI 26 post-install routine to add the GMRV RPCs to the CPRS
 option.  
  
  STATUS: Active                        EXPIRATION DATE: OCT 27, 2006
KEYWORDS: ADDRPCS
KEYWORDS: GMV3PST
COMPONENT/ENTRY POINT: ADDRPCS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4834                            IA #: 4834
  DATE CREATED: NOV 03, 2005            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XQALDATA
  NAME: USER ALERTS                     ID: XQALDATA
 GENERAL DESCRIPTION:   This Integration Agreement is to document the calls
 GETUSER1^XQALDATA and GETUSER2^XQALDATA.  The Order Entry package uses these
 calls to retrieve the alerts that a user needs to see.  
  
 Amendments: 10/20/22 Component GETPAT2 was added in XU*8.0*653, as a part of
 the CPRS v31b release which included an enhancement to show all the alerts
 related to a patient, rather than only those alerts specific to the provider. 
  
 10/20/22 Component GETUSER2 was added in XU*8.0*662 as part of the 
 enhancements for the display of processed alerts in CPRS v32b.  
  
 08/18/23 Components DEFALERT and GETPAT3 were added in XU*8*653 and used by
 CPRS v31b release, in addition to the GETPAT2 documented on 10/20/22.  
  STATUS: Active
KEYWORDS: XQALDATA
KEYWORDS: GETUSER1
KEYWORDS: ALERTS
KEYWORDS: GETUSER2
KEYWORDS: GETPAT2
KEYWORDS: GETPAT3
KEYWORDS: DEFALERT
COMPONENT/ENTRY POINT: GETUSER1
 COMPONENT DESCRIPTION:   The GETUSER1 entry point retrieves unprocessed alerts
 for a user.  
VARIABLES: ROOT                         TYPE: Output
 VARIABLES DESCRIPTION:   Upon return this variable holds the global reference
 of the resulting alert data. The output consists of the following: 
  
 ROOT=TOTAL COUNT 
  
 ROOT(1)=KEY  MSG TXT^ALERT ID 
  
 If Alert Forwarded:  ROOT(+1)=KEY  -----Forwarded by: PROVIDER NAME  
 Generated: DATE/TIME FORWARDED^ALERT ID 
  
 If Alert Forwarded contains comment text:  ROOT(+1)=KEY  -----FORWARD
 COMMENT^ALERT ID 
  
 ROOT(+1)=KEY  MSG TXT^ALERT ID 
  
 ROOT(+1)...  
  
 KEY = Value is determined in order of occurance as listed below.  
  
      G = GUID FOR GUI 
      L = LONG INFO TEXT 
      I = INFORMATION ONLY 
      R = (Everything Else) 
  
 MESSAGE TEXT = The text of the message to be presented to the user at the time
 when he cycles through the menu system the first time after the alert has been
 filed for the user, and when the user selects the VIEW ALERTS option.  
  
 ALERT ID = This id may simply be a package namespace, or it may be a namespace
 followed by additional data to more accurately identify the type or purpose of
 the alert.  
  
 PROVIDER NAME = This is the name of the provider who forwarded the alert.  
  
 DATE/TIME FORWARDED = This is the date/time that the forward alert action
 occurred.  
  
  
 Example Output: 
 ---------------
 ROOT=3 
  
 ROOT(1)="R  PATIENTLNAME,PATIENTFNAME (P6666): [LOCATION] Order placed:
 ACETAMINOPHEN TAB  MM/YY HH:MM^ALERT ID" 
  
 ROOT(2)="R  -----Forwarded by: PROVIDERLNAME,PROVIDERFNAME   Generated:
 MM/DD/YY HH:MM:SS^ALERT ID" 
  
 ROOT(3)="R  -----TESTING ALERT FORWARD ACTION^ALERT ID" 
VARIABLES: XQAUSER                      TYPE: Input
 VARIABLES DESCRIPTION:   The DUZ of the user for whom to retrieve the alerts.  
  
VARIABLES: FRSTDATE                     TYPE: Input
 VARIABLES DESCRIPTION:   This variable is not used.  
VARIABLES: LASTDATE                     TYPE: Input
 VARIABLES DESCRIPTION:   This variable is not used.  
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   Add FLAG to filter deferred alerts.  
COMPONENT/ENTRY POINT: GETUSER2
 COMPONENT DESCRIPTION:   The GETUSER2 entry point retrieves processed alerts
 for a user.  
VARIABLES: ROOT                         TYPE: Output
 VARIABLES DESCRIPTION:   Upon return this variable holds the global reference
 of the resulting alert data. The output consists of the following: 
  
 ROOT=TOTAL COUNT 
  
 ROOT(1)="KEY  DISPLAY TEXT^NAME" 
  
 ROOT(1,"PROCESSED")="ALERT FIRST DISPLAYED^FIRST SELECTED ALERT^ PROCESSED
 ALERT^DELETED ON^RECIPIENT TYPE^PROCESS BY^SURROGATE FOR^ FORWARDED BY OR FOR  
 FORWARDED DATE/TIME" 
  
 ROOT(2)=KEY  DISPLAY TEXT^NAME 
  
 ROOT(2,"PROCESSED")...  
  
 KEY = Value is determined in order of occurance as listed below.  
  
      G = GUID FOR GUI 
      L = LONG INFO TEXT 
      I = INFORMATION ONLY 
      R = (Everything Else) 
  
 DISPLAY TEXT = The information that will be displayed on an alert.  
  
 NAME = This id may simply be a package namespace, or it may be a namespace
 followed by additional data to more accurately identify the type or purpose of
 the alert.  
  
 PROVIDER NAME = This is the name of the provider who forwarded the alert.  
  
 DATE/TIME FORWARDED = This is the date/time that the forward alert action
 occurred.  
  
  
 Example Output: 
 ---------------
 ROOT=1 
  
 ROOT(1)="R  PATIENTLNAME,PATIENTFNAME (P6666): [LOCATION] Order placed:
 ACETAMINOPHEN TAB  MM/YY HH:MM^NAME (ie ALERT ID)" 
  
 ROOT(1,"PROCESSED")="YYYMMDD.HHMMSS^YYYMMDD.HHMMSS^ 
 YYYMMDD.HHMMSS^YYYMMDD.HHMMSS^INITIAL RECIPIENT^ CPRSPROVIDER,SEVENTEEN^^" 
VARIABLES: XQAUSER                      TYPE: Input
 VARIABLES DESCRIPTION:   The DUZ of the user for whom to retrieve the
 processed alerts.  
VARIABLES: FRSTDATE                     TYPE: Input
 VARIABLES DESCRIPTION:   The start date in which to begin retrieving alerts.  
VARIABLES: LASTDATE                     TYPE: Input
 VARIABLES DESCRIPTION:   The end date in which to stop retrieving alerts.  
VARIABLES: MAXRET                       TYPE: Input
 VARIABLES DESCRIPTION:   The maximum number of alerts to retrieve.  
VARIABLES: PROONLY                      TYPE: Input
 VARIABLES DESCRIPTION:   This variable is not used.  
COMPONENT/ENTRY POINT: GETPAT2
 COMPONENT DESCRIPTION:   The GETPAT2 component returns all the alerts for a
 specific patient.  
VARIABLES: ROOT                         TYPE: Output
 VARIABLES DESCRIPTION:   This variable contains the name of the local array
 used to store the alerts returned.  
  
 Example usage: D GETPAT2("ROOT",PATIENT,PAGE,LIMIT) 
  
 Returns: ROOT=Total number of alerts in the page.  ROOT(0)=Page^Total number
 of pages ROOT(1)="   CPRSPATIENT,EIGH (C0008): Lapsed Unsigned 
 Order(s)^OR,100022,78;10000000200; 3221009.105002^14534305" ROOT(2)="  
 CPRSPATIENT,EIGH (C0008): Order requires electronic signature.^OR,100022,12;
 10000000200;3221008.052" 
VARIABLES: PATIENT                      TYPE: Input
 VARIABLES DESCRIPTION:   DFN of the patient for which to retrieve alerts.  
VARIABLES: PAGE                         TYPE: Input
 VARIABLES DESCRIPTION:   The 'page' of the alerts to retrieve, assuming there
 is more than one page available. For example, if the limit is to retrieve 25
 alerts at one time, and the patient has 75 alerts, there would be three pages. 
 
VARIABLES: LIMIT                        TYPE: Input
 VARIABLES DESCRIPTION:   The limit of the number of alerts to retrieve per
 page.  
COMPONENT/ENTRY POINT: DEFALERT
 COMPONENT DESCRIPTION:   The DEFALERT component adds the date and time to an
 alert.  
VARIABLES: ROOT                         TYPE: Output
 VARIABLES DESCRIPTION:   This variable contains an error message if the
 attempt to defer the alert fails.  
VARIABLES: XQAUSER1                     TYPE: Input
 VARIABLES DESCRIPTION:   The user responsible for the alert.  
VARIABLES: DEFDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   The date/time the alert is deferred til...user
 responsible sets the date...maximum of 14 days from the date/time deferred.  
VARIABLES: ALERTID                      TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the alert in file 8992 2nd piece of the
 alert date/time multiple. DG,IEN of file;original recipient;date/time of
 alert.  
COMPONENT/ENTRY POINT: GETPAT3
 COMPONENT DESCRIPTION:   Returns the list of unprocessed alerts by patient.  
VARIABLES: ROOT                         TYPE: Output
 VARIABLES DESCRIPTION:   ROOT(0)=The count of entries following in the ROOT
 array.  ROOT(#)=Alert details.  
VARIABLES: PATIENT                      TYPE: Input
 VARIABLES DESCRIPTION:   DFN of the patient for which to retrieve alerts.  
VARIABLES: XFROM                        TYPE: Input
 VARIABLES DESCRIPTION:   From Date.  
VARIABLES: XTO                          TYPE: Input
 VARIABLES DESCRIPTION:   To Date.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Revised 8/22/23: DEFALERT and GETPAT3 were historically
 used since the release of CPRS v31b without ICR compliance. Effective with
 patch OR*3.0*603 the usage meets the SAC standards.  
SUBSCRIBING PACKAGE: HEALTH DATA REPOSITORY
 SUBSCRIBING DETAILS:   Added 4/17/23, effective with informational patch
 HDS*1*66.  Vets-Home software needs to display VistA Alerts across all VistA
 systems for the remote veterans they are caring for. HDR will provide a
 service to pull Alerts as shown in CPRS for a given provider/caregiver. This 
 service will ensure the integrity of care as it will provide Alert across all
 VistA systems.  Patch information: HDR does not deploy software via VistA
 patches. HDR services use IRIS SQL objects that live in its own Cache/IRIS
 database on the VistA system (HDRDAT database). Even though HDRDAT resides on
 the VistA system is has its separate configuration from VistA. Therefore, HDR 
 does not deploy updates via FORUM, rather, it deploys using HIDU (HDR Inplace
 Database Update) process to install objects directly to the HDRDAT. 
  DATE ACTIVATED: AUG 22, 2023

NUMBER: 4835                            IA #: 4835
  DATE CREATED: DEC 01, 2005
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: ADD GMV RPCS TO OR CPRS GUI CHART
 GENERAL DESCRIPTION:   CPRS grants permission to the GMRV  GEN. MED. REC. -
 VITALS package to add GMV-namespaced Remote Procedure Calls (RPCs) to the RPC
 (Field #320) multiple of the OR CPRS GUI CHART option (File #19).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VitalsLite
KEYWORDS: DLL
KEYWORDS: GMV_VitalsViewEnter.dll
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS

NUMBER: 4836                            IA #: 4836
  FILE NUMBER: 40.7                     GLOBAL ROOT: DIC(40.7,
  DATE CREATED: MAR 22, 2006            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4836
  ID: DIC(40.7,
GLOBAL REFERENCE: DIC(40.7,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING

NUMBER: 4837                            IA #: 4837
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123,
  DATE CREATED: MAR 24, 2006
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: LOOK UP REQUEST/CONSULTATION ENTRY
  ID: GMR(123,
GLOBAL REFERENCE: GMR(123,
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: 1                         FIELD NAME: TO SERVICE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: CPRS STATUS
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: LAST ACTION TAKEN
  LOCATION: 0;13                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   with Direct Global read.  
FIELD NUMBER: 10                        FIELD NAME: SENDING PROVIDER
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Zero node read into variable.  
GLOBAL REFERENCE: GMR(123,D0,1.11,
FIELD NUMBER: 1                         FIELD NAME: DISPLAY TEXT OF ITEM ORDERED
  LOCATION: 1.11,1                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: GMR(123,D0,40,D1,
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME OF ACTION ENTRY
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ACTIVITY
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DATE/TIME OF ACTUAL ACTIVITY
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 3
  FIELD NAME: WHO'S RESPONSIBLE FOR ACTIVITY
  LOCATION: 0;4                         ACCESS: Write w/Fileman
FIELD NUMBER: 4                         FIELD NAME: WHO ENTERED ACTIVITY
  LOCATION: 0;5                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: GMR(123,'F'
 GLOBAL DESCRIPTION:   Used to search by patient to get REQUEST/CONSULTATION
 ien.  
  
 This cross-reference will be cleaned by a post-init routine in SD*5.3*496 
 through verification that each cross-reference entry has its corresponding 
 REQUEST/CONSULTATION entry, pointed to.  
GLOBAL REFERENCE: GMR(123,'E'
 GLOBAL DESCRIPTION:   Used to search by date to get REQUEST/CONSULTATION ien.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4838                            IA #: 4838
  DATE CREATED: MAR 31, 2006            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGDTR01
  NAME: 4838 MAGDTR01                   ID: MAGDTR01
 GENERAL DESCRIPTION:   Imaging has requested Consults to add a call,
 ORRIN^MAGDTR01 to the routine GMRCIMSG for use with patch MAG*3.0*46.  This
 will allow Imaging to process Consult HL7 messages.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Consult HL7 message
KEYWORDS: MAGDTR01
KEYWORDS: IMAGING
COMPONENT/ENTRY POINT: ORRIN
VARIABLES: HLNEXT                       TYPE: Input
 VARIABLES DESCRIPTION:   M code that is executed by the application to $O
 through the nodes of the Message Text global.  
VARIABLES: HLNODE                       TYPE: Input
 VARIABLES DESCRIPTION:   The HLNODE() array contains the segment text.  If the
 total segment length is not greater than 245, the full segment text is
 contained in the scalar HLNODE.  If the total segment length is greater than
 245, the segment text past the 245th character is contained in successive
 integer subscripts of the HLNODE() array in 245-character increments. 
VARIABLES: HLQUIT                       TYPE: Output
 VARIABLES DESCRIPTION:   A variable that indicates when there are one more
 nodes to process.  If HLQUIT is not greater than zero, all message text has
 been processed.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   A call to ORRIN^MAGDTR01 is made by GMRCIMSG this
 allows Imaging the ability to process Consult HL7 messages.  

NUMBER: 4839                            IA #: 4839
  DATE CREATED: APR 07, 2006
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUPRFL
  NAME: Is This a PRF Title             ID: TIUPRFL
 GENERAL DESCRIPTION:   This agreement permits subscribers to call
 ISPFTTL^TIUPRFL to determine whether a given TIU Title (file 8925.1) is a
 Patient Record Flag Title.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: flag
KEYWORDS: PRF
KEYWORDS: PATIENT RECORD FLAG
COMPONENT/ENTRY POINT: ISPFTTL
 COMPONENT DESCRIPTION:   FUNCTION returns 1 if Title is PRF Title, otherwise
 returns 0.  A title is a PRF Title if it belongs to either of the two exported
 PRF document classes.  
  
 Note ISPFTTL is spelled with PF, NOT PRF ; Cf RPC ISPRFTTL^TIUPRF2  - spelled
 with PRF 
VARIABLES: TITLEDA                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN in file 8925.1 of given Title 
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   MAG*3*59 screens out PRF titles when creating new TIU
 notes to which images are then attached. This avoids creating PRF notes which
 are not linked to flag assignments, which are not permitted in Phase II of
 Patient Record Flags. Imaging uses ISPFTTL to determine if a given Title is a
 PRF Title.  

NUMBER: 4840                            IA #: 4840
  DATE CREATED: APR 11, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPFSS2
  NAME: PROCESS INBOUND BATCH HEC ORU MESSAGES TO A31
  ID: DGPFSS2
 GENERAL DESCRIPTION:   This call is to process an inbound batch ORU message
 from the HEC to extract information to generate outbound A31 messages to
 external PFSS system.  
  STATUS: Active
KEYWORDS: PFSS
KEYWORDS: ORU
KEYWORDS: HEC
COMPONENT/ENTRY POINT: BATCH
 COMPONENT DESCRIPTION:   Entry point processes the ^TMP Global generated by
 the inbound HL7 (ORU) message processing routine.  The ^TMP global is built in
 the IVM Incoming HL7 (ORU) message processing routine and is referenced
 globally from DGPFSS2. The ^TMP global contains a "copy" of the incoming HL7
 batch message and is used by the various "Z" segment processors to extract the 
 pieces of data that particular "Z" segment uses.  This ^TMP global is in 
 exsistance until the message processing routine exits.  The format for the 
 ^TMP global follows: 
  
   ^TMP($J,Calling Routine Name,Line Count,0)=HL7 Message Segment 
  
 i.e.  ^TMP($J,"IVMPREC2",1,0)=BHS^~|\&^HEC 500^724^VAMC
 500^500^20060405015234-0500^^~T~ORU|Z05~2.1~NE~NE^^742729064258^ 
VARIABLES: DGRTN                        TYPE: Input
 VARIABLES DESCRIPTION:   This variable contains the "name" of the routine
 which built the ^TMP global.  For example, in the inbound HL7 (ORU) message
 processing routine, this value is contained in the IVMRTN variable.  
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM

NUMBER: 4841                            IA #: 4841
  FILE NUMBER: 44                       GLOBAL ROOT: SC(44,
  DATE CREATED: APR 10, 2006            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CONSULT LINK
  ID: SC(44,
GLOBAL REFERENCE: SC(D0,'S',D1,1,
FIELD NUMBER: 688                       FIELD NAME: CONSULT LINK
  LOCATION: "CONS";1                    ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Also, direct read on "AWAS1" and "AHST1" xrefs.  Direct
 Kill of records in the AWAS1 x-ref [^SC("AWAS1",] is allowed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Consult/Request Tracking requests, for reporting,
 access to the CONSULT LINK field (#688) and its xrefs "AWAS1" and "AHST1" of
 the HOSPITAL LOCATION file (#44).  
  DATE ACTIVATED: JUL 14, 2009

NUMBER: 4842                            IA #: 4842
  FILE NUMBER: 409.3                    GLOBAL ROOT: SDWL(409.3,
  DATE CREATED: APR 10, 2006            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4842
  ID: SDWL(409.3,
GLOBAL REFERENCE: SDWL(409.3,
FIELD NUMBER: 1                         FIELD NAME: ORIGINATING DATE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: WL SERVICE/SPECIALTY
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: WL SPECIFIC CLINIC
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 23                        FIELD NAME: CURRENT STATUS
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Also, direct read on "B" xref.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Consult/Request Tracking requests access to read from
 the SD WAIT LIST file (#409.3).  

NUMBER: 4843                            IA #: 4843
  FILE NUMBER: 409.31                   GLOBAL ROOT: SDWL(409.31,
  DATE CREATED: APR 10, 2006            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4843
  ID: SDWL(409.31,
GLOBAL REFERENCE: SDWL(409.31,
FIELD NUMBER: .01                       FIELD NAME: SERVICE/SPECIALTY
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Consult/Request Tracking requests access to read from
 the SD WL SERVICE/SPECIALTY file (#409.31).  

NUMBER: 4844                            IA #: 4844
  FILE NUMBER: 409.32                   GLOBAL ROOT: SDWL(409.32,
  DATE CREATED: APR 10, 2006            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4844
  ID: SDWL(409.32,
GLOBAL REFERENCE: SDWL(409.32,
FIELD NUMBER: .01                       FIELD NAME: CLINIC
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Consult/Request Tracking requests access to read from
 the SD WL CLINIC LOCATION file (#409.32).  

NUMBER: 4845                            IA #: 4845
  DATE CREATED: APR 12, 2006            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAG7UFO
  NAME: Return NEW PERSON file phone number(s)
  ID: MAG7UFO
 GENERAL DESCRIPTION:   The Vista Radiology/Nuclear Medicine application would
 like to utilize the existing VistA Imaging utility (NPFON^MAG7UFO) to return
 all phone number related information for a specific record in the NEW PERSON
 (#200) file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OBR-17
KEYWORDS: ORC-14
KEYWORDS: NEW PERSON phone number(s)
KEYWORDS: Imaging/Radiology IA
COMPONENT/ENTRY POINT: NPFON
 COMPONENT DESCRIPTION:   NPFON is the entry point for this utility. There are
 two inputs to this function XFLD & XIEN; both inputs are required.  
VARIABLES: XFLD                         TYPE: Input
 VARIABLES DESCRIPTION:   The name of the array where the phone information is
 to be populated.  
VARIABLES: XIEN                         TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number (IEN) of a NEW PERSON file
 record returning phone contact information. 
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 4846                            IA #: 4846
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG(
  DATE CREATED: APR 13, 2006
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4846
  ID: PSDRUG(
GLOBAL REFERENCE: PSDRUG(
FIELD NUMBER: .O1                       FIELD NAME: GENERIC NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   This DBIA allows for subscribing packages to store a
 pointer to the Vista DRUG (#50) file. This number can be used as an
 Identification Number to retrieve data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4847                            IA #: 4847
  DATE CREATED: APR 18, 2006
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMRAOR
  NAME: GET ALLERGY DATA INCLUDING REMOTE
  ID: GMRAOR
 GENERAL DESCRIPTION:   This DBIA is to allow subscribing packages to get the
 aggregate sum of a patients allergy information reduced into the drug classes
 and drug ingredients that the patient has allergies to.  
  
  STATUS: Active                        EXPIRATION DATE: MAY 31, 2017
KEYWORDS: GMRAOR
KEYWORDS: GETDATA
COMPONENT/ENTRY POINT: GETDATA
 COMPONENT DESCRIPTION:   Obtain local and HDR related allergy data for use in
 order checking. 
        Section added in patch 26 Output from call will be stored in ^TMP as
 follows: ^TMP("GMRAOC",$J,"API",J)="" where J is the ingredient IEN 
 ^TMP("GMRAOC",$J,"APC",K)="" where K is the drug class 
        classification (e.g. MS105) 
  
VARIABLES: DFN                          TYPE: Input
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
 SUBSCRIBING DETAILS:   OPT PS needs to access drug class information and get
 loca/remote site designations.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: JUL 28, 2016

NUMBER: 4848                            IA #: 4848
  GLOBAL ROOT: TMP('GMRAOC',            DATE CREATED: APR 18, 2006
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: GMRAOC TMP GLOBAL READ
  ID: TMP('GMRAOC',
GLOBAL REFERENCE: TMP('GMRAOC',$J,'APC',D0
 GLOBAL DESCRIPTION:   This is the global that is used to return the data from
 a call to GETDATA^GMRAOC.  It contains the patient's allergy information
 including remote data split into drug ingredients and drug classes.  
  
 GENERAL DESCRIPTION:   This dbia is a followup to DBIA #4847.  This allows the
 calling package of GETDATA^GMRAOR to read the results of the call from the
 ^TMP("GMRAOR",$J global.  
  
  STATUS: Active                        EXPIRATION DATE: MAY 31, 2017
KEYWORDS: GMRAOR
KEYWORDS: GETDATA
KEYWORDS: GMRAOC
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  ISC: Birmingham
 SUBSCRIBING DETAILS:   To be able to read the ^TMP("GMRAOC",$J global created
 by GETDATA^GMRAOR (DBIA 4847) for accessing drug class information and for
 getting the LOCAL or REMOTE SITE(S) designations.  
  DATE ACTIVATED: MAY 30, 2014

NUMBER: 4849                            IA #: 4849
  FILE NUMBER: 771                      DATE CREATED: APR 20, 2006
  CUSTODIAL PACKAGE: REGISTRATION       USAGE: Private
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA #4849
 GENERAL DESCRIPTION:   For the PFSS project, which includes a number of VistA
 application packages, structures are setup for HL7 communication between VistA 
 and an external COTS system for patient billing.  
   
 Most inbound HL7 messages are being received for processing by the
 REGISTRATION package (DG), but two specific messages (ADT-A05 and ADT-A04)
 must be processed only by the INTEGRATED BILLING package within the new IBB
 module for PFSS.  
   
 The IBB receivers use four PROTOCOLS (file #101) in order to route the ADT-A05
 and ADT-A04 to the processing routine.  Since the COTS system will only use
 the HL7 APPLICATION PARAMETER (file #771) names setup for the DG application
 in their MSH segments, the IBB Protocols must be pointed to these file #771
 entries.  
   
 This IA allows the four IBB Protocols to utilize the DG Application Parameters
 DGPFSS ADT RECV and DGPFSS ADT SENDING as follows: 
  
 NAME: IBB PFSS ADT-A04 CLIENT           TYPE: subscriber 
   RECEIVING APPLICATION: DGPFSS ADT RECV 
   EVENT TYPE: A04                       RESPONSE MESSAGE TYPE: ADT 
   PROCESSING ROUTINE: D A04^IBBAADTI    SENDING FACILITY REQUIRED?: NO 
   RECEIVING FACILITY REQUIRED?: NO 
   
 NAME: IBB PFSS ADT-A04 SERVER           ITEM TEXT: PFSS/IBB ADT-A04 Receiver 
   TYPE: event driver                    
   SENDING APPLICATION: DGPFSS ADT SENDING 
   TRANSACTION MESSAGE TYPE: ADT         EVENT TYPE: A04 
   MESSAGE STRUCTURE: ACK                ACCEPT ACK CODE: AL 
   APPLICATION ACK TYPE: AL              VERSION ID: 2.4 SUBSCRIBERS: IBB PFSS
 ADT-A04 CLIENT 
   
 NAME: IBB PFSS ADT-A05 CLIENT           TYPE: subscriber 
   RECEIVING APPLICATION: DGPFSS ADT RECV 
   EVENT TYPE: A05                       RESPONSE MESSAGE TYPE: ADT 
   PROCESSING ROUTINE: D A05^IBBAADTI    SENDING FACILITY REQUIRED?: NO 
   RECEIVING FACILITY REQUIRED?: NO 
   
 NAME: IBB PFSS ADT-A05 SERVER           ITEM TEXT: PFSS/IBB ADT-A05 Receiver 
   TYPE: event driver                    
   SENDING APPLICATION: DGPFSS ADT SENDING 
   TRANSACTION MESSAGE TYPE: ADT         EVENT TYPE: A05 
   ACCEPT ACK CODE: AL                   APPLICATION ACK TYPE: AL 
   VERSION ID: 2.4 
   
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PFSS
KEYWORDS: HL7
KEYWORDS: PROTOCOLS
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Four PROTOCOL file (#101) entries setup by IBB for PFSS
 processing of inbound ADT-A05 and ADT-A04 messages will utilize HL7
 APPLICATION PARAMETER file (#771) entries in the DG namespace that are
 intended for use exclusively by the PFSS project.  
   
 The PROTOCOL file entries for IB are: 
  
 NAME: IBB PFSS ADT-A04 CLIENT           TYPE: subscriber 
   RECEIVING APPLICATION: DGPFSS ADT RECV 
   EVENT TYPE: A04                       RESPONSE MESSAGE TYPE: ADT 
   PROCESSING ROUTINE: D A04^IBBAADTI    SENDING FACILITY REQUIRED?: NO 
   RECEIVING FACILITY REQUIRED?: NO 
   
 NAME: IBB PFSS ADT-A04 SERVER           ITEM TEXT: PFSS/IBB ADT-A04 Receiver 
   TYPE: event driver                    
   SENDING APPLICATION: DGPFSS ADT SENDING 
   TRANSACTION MESSAGE TYPE: ADT         EVENT TYPE: A04 
   MESSAGE STRUCTURE: ACK                ACCEPT ACK CODE: AL 
   APPLICATION ACK TYPE: AL              VERSION ID: 2.4 SUBSCRIBERS: IBB PFSS
 ADT-A04 CLIENT 
   
 NAME: IBB PFSS ADT-A05 CLIENT           TYPE: subscriber 
   RECEIVING APPLICATION: DGPFSS ADT RECV 
   EVENT TYPE: A05                       RESPONSE MESSAGE TYPE: ADT 
   PROCESSING ROUTINE: D A05^IBBAADTI    SENDING FACILITY REQUIRED?: NO 
   RECEIVING FACILITY REQUIRED?: NO 
   
 NAME: IBB PFSS ADT-A05 SERVER           ITEM TEXT: PFSS/IBB ADT-A05 Receiver 
   TYPE: event driver                    
   SENDING APPLICATION: DGPFSS ADT SENDING 
   TRANSACTION MESSAGE TYPE: ADT         EVENT TYPE: A05 
   ACCEPT ACK CODE: AL                   APPLICATION ACK TYPE: AL 
   VERSION ID: 2.4 
  

NUMBER: 4850                            IA #: 4850
  DATE CREATED: APR 27, 2006            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDPCE
  NAME: CALL TO GET ENCOUNTER STATUS    ID: SDPCE
 GENERAL DESCRIPTION:   This DBIA will permit Clinical Reminders to use an
 existing Scheduling function call to get the Status of an encounter.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SDPCE
KEYWORDS: PXRM
KEYWORDS: STATUS
COMPONENT/ENTRY POINT: $$STATUS(SDVISIT)
 COMPONENT DESCRIPTION:   This returns the status of an encounter.  
  
 Usage: S OUTPUT=$$STATUS^SDPCE(SDVISIT) 
  
VARIABLES: SDVISIT                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN from the VISIT File, File #9000010.  
  
VARIABLES: $$STATUS                     TYPE: Output
 VARIABLES DESCRIPTION:   Status of the encounter Internal IEN^External Value.  
  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 4851                            IA #: 4851
  DATE CREATED: APR 21, 2006            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: KAAJEE
 GENERAL DESCRIPTION:   
  
  KAAJEE addresses the Authentication and Authorization (AA) needs of 
  HealtheVet-VistA Web-based applications in the J2EE environment.  
  
 Most major J2EE application servers (e.g., BEA WebLogic V. 8.1 [SP4 or higher]
 and Oracle's 9iAS) allow enterprises to override the default source of AA and
 replace it with custom, enterprise-specific sources for AA.  In order to
 rapidly develop an AA solution for HealtheVet-VistA web-based applications
 without creating a new enterprise user store, KAAJEE takes full advantage of
 this feature of creating a custom solution.  This enables KAAJEE to provide a
 solution that has a similar look-and-feel of what VistA users are currently
 accustomed to.  
  
 KAAJEE authenticates against a VistA M Server first with Access and Verify
 codes via VistALink's AV connection spec (i.e., 
 KaajeeVistaLinkConnectionSpec). After the user has been properly authenticated
 against a VistA M Server, KAAJEE dynamically creates a temporary username and
 password and populates this into a Structured Query Language (SQL) database
 via custom Security Service Provider Interfaces (SSPIs). This username and
 password is needed for the second level/phase/pass authentication for the J2EE
 container.  
  
 Currently, Kernel maintains the primary HealtheVet-VistA user store (i.e., NEW
 PERSON file [#200]), and provides both Authentication and Authorization (AA)
 services for all HealtheVet-VistA applications. By leveraging Kernel, KAAJEE
 aims to authenticate and authorize J2EE Web users to their applications using
 Kernel's AA capabilities.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: KAAJEE
COMPONENT/ENTRY POINT: login.jsp
 COMPONENT DESCRIPTION:   
  
  Login Web page for authentication. This is the Login Web page where users 
  enter their Access and Verify codes and choose an Institution from a 
  drop-down list.  
  
 For read-only access.  
  
 The consuming application needs to place this file in their deployable 
 artifact in the following directory/folder under the web context root: 
  
         Directory               File Name 
         =========               =========
         ..login\                login.jsp 
  
 In addition, this login.jsp must configured in the application's web.xml file
 as a form-login-page.  
  
 The following XML tags shows an example of how this may be configured in the
 application's web.xml file: 
  
    <login-config> 
    <auth-method>FORM</auth-method> 
     <form-login-config> 
       <form-login-page>login/login.jsp</form-login-page> 
       <form-error-page>login/loginerror.jsp</form-error-page> 
     </form-login-config> 
    </login-config>  
  
COMPONENT/ENTRY POINT: loginerror.jsp
 COMPONENT DESCRIPTION:   
  
  This is the error page to be used with KAAJEE for Form-based 
  authentication.  
  
 When this page is presented to the user, the most likely cause is that the 
 user is lacking the proper Security Keys required for the consuming 
 application.  
  
 For read-only access.  
  
 The consuming application needs to place this file in their deployable 
 artifact in the following directory/folder under the web context root: 
  
         Directory               File Name 
         =========               =========
         ..login\                loginerror.jsp 
  
 In addition, this loginerror.jsp must be configured in the application's 
 web.xml file as a form-error-page.  
  
 The following XML tags shows an example of how this may be configured in the
 application's web.xml file: 
  
    <login-config> 
    <auth-method>FORM</auth-method> 
     <form-login-config> 
       <form-login-page>login/login.jsp</form-login-page> 
       <form-error-page>login/loginerror.jsp</form-error-page> 
     </form-login-config> 
    </login-config> 
  
COMPONENT/ENTRY POINT: loginerrordisplay.jsp
 COMPONENT DESCRIPTION:   
  
  This is the error page that KAAJEE redirects to when authentication fails 
  against a VistA M server after providing the access & verify codes plus 
  the target institution.  
  
 For read-only access.  
  
 The consuming application needs to place this file in their deployable 
 artifact in the following directory/folder under the web context root: 
  
         Directory               File Name 
         =========               =========
         ..login\                loginerrordisplay.jsp 
  
COMPONENT/ENTRY POINT: SessionTimeout.jsp
 COMPONENT DESCRIPTION:   
  
  Login session timeout Web page.  
  
 This web page informs the user that his/her session has expired during login.  
  
 For read-only access.  
  
 The consuming application needs to place this file in their deployable 
 artifact in the following directory/folder under the web context root: 
  
         Directory               File Name 
         =========               =========
         ..login\                SessionTimeout.jsp 
  
COMPONENT/ENTRY POINT: loginCookieInfo.htm
 COMPONENT DESCRIPTION:   
  
  Login persistent cookie information.  
  
 This web page informs the user how the persistent cookie information is used.  
  
 For read-only access.  
  
 The consuming application needs to place this file in their deployable 
 artifact in the following directory/folder under the web context root: 
  
         Directory               File Name 
         =========               =========
         ..login\                loginCookieInfo.htm 
  
COMPONENT/ENTRY POINT: kaajeeConfig.xml
 COMPONENT DESCRIPTION:   
  
  KAAJEE configuration file.  
  
 Access to this file is restricted to read/write/modify as described in the
 KAAJEE documentation.  For more detail regarding the parameters that may be
 modified, refer to the KAAJEE documentation.  
  
 KAAJEE relies on a configuration file (i.e., kaajeeConfig.xml file) to read in
 all administrator-configurable settings. You can use the kaajeeConfig.xml file
 that is distributed with the KAAJEE software or you can create a KAAJEE
 configuration file in your J2EE Web-based application and export it along with
 your Web-based application.  
  
 The consuming application may use 'kaajeeConfig.xml' as the name of the KAAJEE
 configuration file or any filename with an 'xml' extension.  This name is
 identified by configuring web.xml to include a startup servlet (see also
 component gov.va.med.authentication.kernel.InitKaajeeServlet) similar to the
 following entry: 
  
   <servlet> 
     <servlet-name>KaajeeInit</servlet-name> 
 <servlet-class>gov.va.med.authentication.kernel.InitKaajeeServlet</servlet 
 -class> 
     <init-param> 
       <param-name>kaajee-config-file-location</param-name> 
       <param-value>/WEB-INF/kaajeeConfig.xml</param-value> 
     </init-param> 
     <load-on-startup>3</load-on-startup> 
   </servlet>  
  
 The param-value of '/WEB-INF/kaajeeConfig.xml' associated with the param-name
 of 'kaajee-config-file-location' identifies the filename and location of the
 KAAJEE configuration file.  
  
COMPONENT/ENTRY POINT: kaajee-x.x.x.xxx.jar
 COMPONENT DESCRIPTION:   
  
  The kaajee-x.x.x.xxx.jar contains the KAAJEE java classes.  
  Access to this file is limited to read-only.  No modification are 
  permitted.  
  
  Note:  The 'x.x.x.xxx' in the name 'kaajee-x.x.x.xxx.jar' is used 
         as a placeholder and when referenced here in this Integration 
         Agreement represents the current version.  When actually using 
         this file, replace 'x.x.x.xxx' with the current version of the 
         KAAJEE JAR file.  
  
  The kaajee-x.x.x.xxx.jar file must be distributed in your application's 
  Enterprise Archive (.ear) file with an application-level classloader.  
  When you are ready to deploy/distribute your application, 
  perform the following steps: 
  
    a. (required) Package the kaajee-x.x.x.xxx.jar file 
       in your application's ear file (e.g., in a "../APP-INF/lib" folder 
       descendent from the root level of your application's ear file).  
  
    b. (required) Ensure that kaajee-x.x.x.xxx.jar is not located 
       in a deeper level of the classloader hierarchy 
       than that of an application, anywhere on the application server.  
       Otherwise, the singletons will be instantiated with settings 
       inappropriate for your application, and the KAAJEE security system 
       will function inappropriately for your application.  
  
COMPONENT/ENTRY POINT: gov.va.med.authentication.kernel.KaajeeSessionAttributeLi
stener
 COMPONENT DESCRIPTION:   
  
  This class is included in the kaajee-x.x.x.xxx.jar file and 
  is not a separate component.  It is listed here only to describe 
  how it is referenced in the consuming application's web.xml file.  
  
  Configure KAAJEE Listeners (web.xml file) 
  
  KAAJEE has two similar listeners, both of which perform logout actions 
  for a user. Both of these listeners are available in case one listener 
  does not work with a specific container/platform (e.g., WebLogic, Oracle 
  9iAS, etc.): 
  
         Listener                        Description 
         ========                        ===========
         KaajeeSessionAttributeListener  The KaajeeSessionAttributeListener 
                                         listens for specific (individual) 
                                         session attributes that are 
                                         targeted for removal, which 
                                         signals a user session ending, 
                                         and performs user logout actions.  
                                        
 (see also component
 gov.va.med.authentication.kernel.KaajeeHttpSessionListener) 
  
  Configure these listeners in your application's web.xml file as follows: 
  
         <listener> 
             <listener-class> 
                
 gov.va.med.authentication.kernel.KaajeeSessionAttributeListener 
             </listener-class> 
         </listener> 
  
 (see also component
 gov.va.med.authentication.kernel.KaajeeHttpSessionListener) 
  
COMPONENT/ENTRY POINT: HealtheVetVistaSmallBlue.jpg
 COMPONENT DESCRIPTION:   
  
  HealtheVet-VistA small blue logo image file.  
  
 For read-only access.  
  
 This jpeg file is referenced by the KAAJEE login page to provide an image.  
  
 The consuming application needs to place this file in their deployable 
 artifact in the following directory/folder under the web context root: 
  
         Directory               File Name 
         =========               =========
         ..login\images\         HealtheVetVistaSmallBlue.jpg 
  
COMPONENT/ENTRY POINT: HealtheVetVistaSmallWhite.jpg
 COMPONENT DESCRIPTION:   
  
  HealtheVet-VistA small white logo image file.  
  
 For read-only access.  
  
 This jpeg file is referenced by the KAAJEE login page to provide an image.  
  
 The consuming application needs to place this file in their deployable 
 artifact in the following directory/folder under the web context root: 
  
         Directory               File Name 
         =========               =========
         ..login\images\         HealtheVetVistaSmallWhite.jpg 
  
COMPONENT/ENTRY POINT: gov.va.med.authentication.kernel.KaajeeHttpSessionListene
r
 COMPONENT DESCRIPTION:   
  
  This class is included in the kaajee-x.x.x.xxx.jar file and 
  is not a separate component.  It is listed here only to describe 
  how it is referenced in the consuming application's web.xml file.  
  
  Configure KAAJEE Listeners (web.xml file) 
  
  KAAJEE has two similar listeners, both of which perform logout actions 
  for a user. Both of these listeners are available in case one listener 
  does not work with a specific container/platform (e.g., WebLogic, Oracle 
  9iAS, etc.): 
  
         Listener                        Description 
         ========                        ===========
         KaajeeHttpSessionListener       The KaajeeHttpSessionListener 
                                         listens for session destruction.  
                                         It is looking for the whole 
                                         session being destroyed 
                                         and performs user logout actions.  
  
 (see also component
 gov.va.med.authentication.kernel.KaajeeSessionAttributeListener) 
  
  Configure these listeners in your application's web.xml file as follows: 
  
 (see also component
 gov.va.med.authentication.kernel.KaajeeSessionAttributeListener) 
  
         <listener> 
             <listener-class> 
                 gov.va.med.authentication.kernel.KaajeeHttpSessionListener 
             </listener-class> 
         </listener> 
  
COMPONENT/ENTRY POINT: gov.va.med.authentication.kernel.LoginUserInfoVO
 COMPONENT DESCRIPTION:   
  
  This class is included in the kaajee-x.x.x.xxx.jar file and 
  is not a separate component.  It is listed here only to describe 
  how it may be referenced as a JavaBean by the consuming application.  
  
 The session key, properties and getter methods listed below are for read-only
 access.  
  
 Session key used to obtain userInfo JavaBean: 
  
 SESSION_KEY 
  
          The key under which this value is placed in the session object 
          during login, and from which this object 
          can be retrieved by the enclosing web application post-login.  
  
 This SESSION_KEY is a public static final method that returns a string.  
  
 Applications may use the userInfo JavaBean to obtain user demographic 
 information.  
  
 This can be achieved by using the JSP action <jsp:getProperty...> 
  
 This JavaBean contains the following properties: 
  
        UserDuz 
        UserName01 
        UserNameDisplay 
        UserLastName 
        UserFirstName 
        UserMiddleName 
        UserPrefix 
        UserSuffix 
        UserDegree 
        LoginStationNumber 
        UserParentAdministrativeFacilityStationNumber 
        UserParentComputerSystemStationNumber 
  
 Alternatively, applications may access the getter methods directly.  
  
 Methods with a return type of java.util.TreeMap: 
  
 getPermittedNewPersonFileDivisions() Returns a list of the user's permitted
 divisions returned as a TreeMap. The key value in the TreeMap is the Station
 Number, which is a String. The object value stored under each key is a
 VistaDivisionVO object.  
  
 (see also component gov.va.med.authentication.kernel.VistaDivisionVO) 
  
 This list represents all of the divisions on the VistA M Server that the user
 could have logged into. Applications can display a list of other divisions
 that the user could switch to within the application, allowing the user to
 select a different division. It is then the application's responsibility to
 use the proper division for its own internal business rules, and also to pass
 the proper Division Station Number with each VistALink RPC call it makes to M. 
  
 getLoginDivisionVistaProviderDivisions() returns a list of divisions (based on
 information in the SDS Institution table) whose Vista Provider is the same as
 the Vista Provider computer system of the login division.  This list is
 returned as a TreeMap.  The key value in the TreeMap is the Station Number,
 which is a String. The object value stored under each key is a VistaDivisionVO
 object.  
  
 (see also component gov.va.med.authentication.kernel.VistaDivisionVO) 
  
 This method is provided to applications to support division switching for all
 divisions supported at the same computing facility as the login division,
 regardless of whether explicit access has been granted to the user for any
 particular division.  Applications can display a list of other divisions that
 the user could switch to within the application, allowing the user to select a
 different division.  It is then the application's responsibility to use the
 proper division for its own internal business rules.  The application
 developer should be aware that this method may not be appropriate when using
 VistALink RPC calls as the login user may not be permitted access to a
 specific division.  
  
 Methods with a return type of java.lang.String: 
  
 getLoginStationNumber() Returns the Station Number of the Division the user
 selected at login. This can be used as a key to retrieve additional
 information (e.g., name about the login division from the TreeMap of permitted
 divisions returned by the getPermittedDivisions method).  
  
 getUserDegree() Returns the user's Degree value from the NAME COMPONENTS file
 (#20).  
  
 getUserDuz() Return the user's DUZ from the NEW PERSON file (#200).  
  
 getUserFirstName() Returns the users' First Name value from the NAME
 COMPONENTS file (#20) 
  
 getUserLastName() Returns the user's Last Name value from the NAME COMPONENTS
 file (#20).  
  
 getUserMiddleName() Returns the user's Middle Name value from the NAME
 COMPONENTS file (#20).  
  
 getUserName01() Returns the user's name as it's stored in the NAME field (#
 .01) in the NEW PERSON file (#200). For example: KRNUSER,ONE E 
  
 getUserNameDisplay() Returns the Display Name of the user, as put together by
 the Name Standardization APIs on M. For example: One E. Krnuser 
  
 getUserParentAdministrativeFacilityStationNumber() Returns the parent facility
 of the Division used for login, as resolved on the login computer system based
 on that system's INSTITUTION file (#4) from the SDS V. 3.0 (or higher) tables. 
  
 getUserParentComputerSystemStationNumber() Returns the computer system's
 default Institution/Computer System Institution, as identified in the system's
 KERNEL SYSTEM PARAMETERS file (#8989.3) 
  
 getUserPrefix() Returns the user's Prefix value from the NAME COMPONENTS file
 (#20).  
  
 getUserSuffix() Returns the user's Suffix value from the NAME COMPONENTS file
 (#20).  
  
 toString() Returns a string representation of the values in the object.  
  
COMPONENT/ENTRY POINT: gov.va.med.authentication.kernel.InitKaajeeServlet
 COMPONENT DESCRIPTION:   
  
  This class is included in the kaajee-x.x.x.xxx.jar file and 
  is not a separate component.  It is listed here only to describe 
  how it is referenced in the consuming application's web.xml file.  
  
  Configure KAAJEE Startup Servlet (web.xml file) 
  
  This Startup Servlet is needed by KAAJEE to read configuration parameters.  
  For further information regarding these configuration parameters, 
  refer to the current KAAJEE documentation.  
  
  Configure this startup servlet in your application's web.xml file.  
  The following XML tags shown below are an example of how to configure this
 startup servlet in the application's web.xml file: 
  
    <servlet> 
     <servlet-name>KaajeeInit</servlet-name> 
 <servlet-class>gov.va.med.authentication.kernel.InitKaajeeServlet</servlet 
 -class> 
     <init-param> 
       <param-name>kaajee-config-file-location</param-name> 
       <param-value>/WEB-INF/kaajeeConfig.xml</param-value> 
     </init-param> 
     <load-on-startup>3</load-on-startup> 
   </servlet>  
  
 In the above example, the <param-value> contains the folder/path location and
 KAAJEE configuration filename relative to the applications's webroot context.  
  
 Also, the <load-on-startup> value contains an integer value of the order in
 which you wish this servlet to start among other configured startup servlets.  
  
COMPONENT/ENTRY POINT: gov.va.med.authentication.kernel.LoginController
 COMPONENT DESCRIPTION:   
  
  This class is included in the kaajee-x.x.x.xxx.jar file and 
  is not a separate component.  It is listed here only to describe 
  how it is referenced in the consuming application's web.xml file.  
  
  This servlet is the main controller servlet that processes the login request. 
 It must be configured in the application's web.xml file.  For further details
 refer to the current KAAJEE documentation.  
  
COMPONENT/ENTRY POINT: gov.va.med.authentication.kernel.VistaDivisionVO
 COMPONENT DESCRIPTION:   
  
  This class is included in the kaajee-x.x.x.xxx.jar file and 
  is not a separate component.  It is listed here only to describe 
  how it is referenced and associated with other component(s).  
  
  VistaDivisionVO Object 
  
 The VistaDivisionVO object is used to store an individual division, when
 division TreeMaps (i.e., tree structure, keyed on Division Station Number
 strings) are returned by the LoginUserInfoVO methods.  
  
 Listed below are the Class Definition, Constructor Summary and Method Summary: 
  
  public class VistaDivisionVO 
  extends java.lang.Object 
  implements java.io.Serializable 
  
  
 Represents a VistA Division, including Station Name and Station Number.  
  
  
 Constructor Summary 
  
         VistaDivisionVO() 
  
         Instantiates a VistaDivision with all fields set to a null string.  
  
  
 The methods listed below are for read-only access: 
  
 Method Summary 
  
           boolean       getIsDefault() 
  
                         Returns whether or not this is set to the default 
                         Login Division.  
  
  java.lang.String       getName() 
  
                         Returns the Station Name of the Division, 
                         presumably from the VistA M Server 
                         INSTITUTION file (#4) entry (depending 
                         on the source of the information 
                         the instance contains) 
  
  java.lang.String       getNumber() 
  
                         Returns the Station Number of the Division, 
                         presumably from the VistA M Server 
                         INSTITUTION file (#4) entry (depending 
                         on the source of the information 
                         the instance contains) 
  
  java.lang.String       toString() 
  
                         Returns a string representation of the Division 
                         information 
  
  
  (See also component gov.va.med.authentication.kernel.LoginUserInfoVO 
  regarding division TreeMaps returned) 
  
 In order to retrieve this VistaDivisionVO object from these division TreeMaps,
 the following collection, iterator and methods may be used: 
  
  java.util.Set 
  Set java.util.TreeMap.keySet() 
  java.util.Iterator 
  Iterator java.util.Set.iterator() 
  

NUMBER: 4852                            IA #: 4852
  DATE CREATED: JUN 05, 2006            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOPRS2
  NAME: HLO DATA TYPE PARSERS           ID: HLOPRS2
 GENERAL DESCRIPTION:   This provides specialized APIs for parsing HL7 data
 types from a segment.  It applies only to HL7 messages received via the HLO
 software that was released in patch HL*1.6*126.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETTS(.SEG,.VALUE,FIELD,COMP,REP)
 COMPONENT DESCRIPTION:   Gets a segment value that is a time stamp in HL7
 format and converts it to FileMan format. IF the data type value includes the 
 time zone then the time is converted to local time. The degree of precision is
 optionally returned.  IF the component is specified, then the component is
 parsed for data type rather than at the higher field level.  
  
VARIABLES: SEG                          TYPE: Input
 VARIABLES DESCRIPTION:   (required, pass by reference) The array returned by a
 call to $$NEXTSEG^HLOPRS.  
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The sequence # of the field.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If specified, the data type is parsed as a
 component value.  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   The occurrence # (optional, defaults to 1).  For a
 non-repeating field, this parameter is not necessary.  
  
VARIABLES: VALUE                        TYPE: Output
 VARIABLES DESCRIPTION:   (required, pass-by-reference IF subscripts are used)
 The date/time in FileMan format. The PRECISION subscript is optional, if
 provided the time stamp's precision will be determined.  
              "PRECISION" -  (optional)  Expected values are: 
                   "S" - second 
                   "M" - minute 
                   "H" - hour 
                   "D" - day 
                   "L" - month 
                   "Y" - year 
                   "" - precision not specified 
   Note:  FM does not allow greater precision than seconds, so greater 
          precision will be rounded down to the second.  
  
  
COMPONENT/ENTRY POINT: GETDT(.SEG,.VALUE,FIELD,COMP,REP)
 COMPONENT DESCRIPTION:   Gets a segment value that is a date in HL7 format and
 converts it to FileMan format. The degree of precision is optionally returned. 
 
 IF the component is specified, then the component is parsed for data type 
 rather than at the higher field level.  
  
VARIABLES: SEG                          TYPE: Input
 VARIABLES DESCRIPTION:   (required, pass by reference) The array returned by a
 call to $$NEXTSEG^HLOPRS.  
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The sequence # of the field.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If specified, the data type is parsed as a
 component value.  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional, defaults to 1) The occurrence#. For a
 non-repeating fields, this parameter is not necessary.  
  
VARIABLES: VALUE                        TYPE: Output
 VARIABLES DESCRIPTION:   (required, pass-by-reference if the precisoin is
 needed) The date/time in FileMan format. The "PRECISION" subscript is also
 returned: 
         "PRECISION" Expected values are: 
                "S" - second (not valid for DT) 
                "M" - minute (not valid for DT) 
                "H" - hour (not valid for DT) 
                "D" - day 
                "L" - month 
                "Y" - year 
                ""  - precision not specified 
  
COMPONENT/ENTRY POINT: GETCE(.SEG,.VALUE,FIELD,COMP,REP)
 COMPONENT DESCRIPTION:   
        Gets an CE data type(Coded Element, HL7 Section Reference 2.9.8)from
 the 
        specified field.  IF the component is specified, then the component is 
        parsed for data type rather than at the higher field level.  
  
VARIABLES: SEG                          TYPE: Input
 VARIABLES DESCRIPTION:   (required, pass-by-reference) The array returned by a
 call to NEXTSEG^HLOPRS.  
  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If specified, the data type is parsed as a
 component value.  
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The sequence # of the field.  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   The occurrence # (optional, defaults to 1).  For a
 non-repeating fields, this parameter is not necessary.  
  
VARIABLES: VALUE                        TYPE: Output
 VARIABLES DESCRIPTION:   (required, pass-by-reference) These subscripts are
 returned: 
            "ID" - the identifier 
            "TEXT" - 
            "SYSTEM" - name of the code system 
            "ALTERNATE ID" - alternate identifier 
            "ALTERNATE TEXT" 
            "ALTERNATE SYSTEM" - name of the alternate coding system 
  
COMPONENT/ENTRY POINT: GETHD(.SEG,.VALUE,FIELD,COMP,REP)
 COMPONENT DESCRIPTION:   
        Gets an HD data type (Hierarchic Designator, HL7 Section Reference 
        2.9.21) from the specified field.  IF the component is specified, then 
        the component is parsed for data type rather than at the higher field 
        level.  
  
  
VARIABLES: SEG                          TYPE: Input
 VARIABLES DESCRIPTION:   (required, pass-by-reference) The array returned by a
 call to NEXTSEG^HLOPRS.  
  
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The sequence # of the field.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If specified, the data type is parsed as a
 component value.  
  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional, defaults to 1) The occurrence #.  For a
 non-repeating fields, this parameter is not necessary.  
  
  
VARIABLES: VALUE                        TYPE: Output
 VARIABLES DESCRIPTION:   (required, pass-by-reference) These subscripts are
 returned: 
          "NAMESPACE ID" 
          "UNIVERSAL ID" 
          "UNIVERSAL ID TYPE" 
  
  
COMPONENT/ENTRY POINT: GETCNE(.SEG,.VALUE,FIELD,COMP,REP)
 COMPONENT DESCRIPTION:   
        Gets an CNE data type (Coded With No Exceptions, HL7 Section 
        Reference 2.9.8) from the specified field.  IF the component is 
        specified, then the component is parsed for data type rather than at
 the 
        higher field level.  
  
  
VARIABLES: SEG                          TYPE: Input
 VARIABLES DESCRIPTION:   (required, pass-by-reference) The array returned by a
 call to NEXTSEG^HLOPRS.  
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The sequence # of the field.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If specified, the data type is parsed as a
 component value.  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional, defaults to 1) The occurrence #.  For a
 non-repeating fields, this parameter is not necessary.  
  
VARIABLES: VALUE                        TYPE: Output
 VARIABLES DESCRIPTION:   (required, pass-by-reference) These subscripts are
 returned: 
           "ID" - the identifier 
           "TEXT" - 
           "SYSTEM" - name of the code system 
           "ALTERNATE ID" - alternate identifier 
           "ALTERNATE TEXT" 
           "ALTERNATE SYSTEM" - name of the alternate coding system 
           "SYSTEM VERSION" - version ID of the coding system 
           "ALTERNATE SYSTEM VERSION" - version ID of the alternate 
                coding system 
           "ORIGINAL TEXT" 
  
  
COMPONENT/ENTRY POINT: GETCWE(.SEG,.VALUE,FIELD,COMP,REP)
 COMPONENT DESCRIPTION:   
        Gets an CWE data type (Coded With Exceptions, HL7 Section 
        Reference 2.9.11) from the specified field.  .  IF the component is 
        specified, then the component is parsed for data type rather than at
 the 
        higher field level.  
  
  
VARIABLES: SEG                          TYPE: Input
 VARIABLES DESCRIPTION:   (required, pass-by-reference) The array returned by a
 call to NEXTSEG^HLOPRS.  
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The sequence # of the field.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If specified, the data type is parsed as a
 component value.  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional, defaults to 1) The occurrence #.  For a
 non-repeating fields, this parameter is not necessary.  
  
VARIABLES: VALUE                        TYPE: Output
 VARIABLES DESCRIPTION:   VALUE  (required, pass-by-reference) These subscripts
 are returned: 
           "ID" - the identifier 
           "TEXT" - 
           "SYSTEM" - name of the code system 
           "ALTERNATE ID" - alternate identifier 
           "ALTERNATE TEXT" 
           "ALTERNATE SYSTEM" - name of the alternate coding system 
           "SYSTEM VERSION" - version ID of the coding system 
           "ALTERNATE SYSTEM VERSION" - version ID of the alternate 
                coding system 
           "ORIGINAL TEXT" 
  
COMPONENT/ENTRY POINT: GETAD(.SEG,.VALUE,FIELD,COMP,REP)
 COMPONENT DESCRIPTION:   
        Gets an AD data type (Address, HL7 Section Reference 2.9.1) from the 
        specified field. It can also be used to get the 1st 8 components of the 
        XAD (Extended Address) data type.  IF the component is specified, then 
        the component is parsed for the address rather than at the higher field 
        level.  
  
VARIABLES: SEG                          TYPE: Input
 VARIABLES DESCRIPTION:   (required, pass-by-reference) The array returned by a
 call to NEXTSEG^HLOPRS.  
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The sequence # of the field.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If specified, the data type is parsed as a
 component value.  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional, defaults to 1) The occurrence #.  For a
 non-repeating fields, this parameter is not necessary.  
  
VARIABLES: VALUE                        TYPE: Output
 VARIABLES DESCRIPTION:   (required, pass-by-reference) These subscripts are
 returned: 
          "STREET1" -street address 
          "STREET2" - other designation 
          "CITY" 
          "STATE" - state or province 
          "ZIP" - zip or postal code 
          "COUNTRY" 
          "TYPE"  - address type 
          "OTHER" - other geographic designation 
  
  

NUMBER: 4853                            IA #: 4853
  DATE CREATED: JUN 05, 2006            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOAPI4
  NAME: HLO BUILDING MESSAGES WITH DATA TYPES
  ID: HLOAPI4
 GENERAL DESCRIPTION:   This provides specialized APIs for buiding messages
 with HL7 data types.  It applies only to HL7 messages received via the HLO
 software that was released in patch HL*1.6*126.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HLOAPI4
KEYWORDS: MAG HLOAPI4
COMPONENT/ENTRY POINT: SETTS(.SEG,.VALUE,FIELD,COMP,REP)
 COMPONENT DESCRIPTION:   
        Sets a value that is a time stamp in FM format into the segment in HL7 
        format. The degree of precision may be optionally specified. The 
        inserted value will include the timezone if the input included the
 time.  
        IF the component is specified, then the data type is 'demoted' to a 
        component, and its components are 'demoted' to subcomponents.  
  
  
VARIABLES: SEG                          TYPE: Both
 VARIABLES DESCRIPTION:   (required, pass by reference) The segment that is
 being built.  
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The sequence # of the field.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If specified, the data type is 'demoted'
 to a component value.  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional, defaults to 1) The occurrence #.  For a
 non-repeating fields, this parameter is not necessary.  
  
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   (required, pass-by-reference to also pass the the
 "PRECISION" subscript) The date/time in FileMan format.  You can optionally
 specify that the value is to be rounded down to a particular precision by
 specifying this subscript: 
            "PRECISION" -  Allowed values are: 
                   "S" - second 
                   "M" - minute 
                   "H" - hour 
                   "D" - day 
                   "L" - month 
                   "Y" - year 
                   "" - precision not specified 
  
  
COMPONENT/ENTRY POINT: SETDT(.SEG,.VALUE,FIELD,COMP,REP)
 COMPONENT DESCRIPTION:   
        Sets a value that is a date in FM format into the segment in HL7
 format.  
        The degree of precision may be optionally specified.  IF the component 
        is specified, then the data type is 'demoted' to a component, and its 
        components are 'demoted' to subcomponents.  
  
VARIABLES: SEG                          TYPE: Both
 VARIABLES DESCRIPTION:   (required, pass by reference) The segment that is
 being built.  
  
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The date to be set into the segment. 
 Optionally, you may specify that the value should be rounded down to a 
 particular precision by specifying this subscript: 
           "PRECISION" (If needed, VALUE must be passed by reference.) 
                        Allowed values are: 
       
                        "D" - day (default value) 
                        "L" - month 
                        "Y" - year 
  
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The sequence # of the field.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If specified, the data type is 'demoted'
 to a component value.  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional, defaults to 1) The occurrence #.  For a
 non-repeating fields, this parameter is not necessary.  
  
COMPONENT/ENTRY POINT: SETCE(.SEG,.VALUE,FIELD,COMP,REP)
 COMPONENT DESCRIPTION:   
       Sets a value that is an HL7 Coded Element data type (HL7 Section 
       Reference 2.9.3) into the segment in the specified field.  IF the 
       component is specified, then the data type is 'demoted' to a component, 
       and its components are 'demoted' to subcomponents.  
  
VARIABLES: SEG                          TYPE: Both
 VARIABLES DESCRIPTION:   (required, pass-by-reference) The segment that is
 being built.  
  
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   (required, pass-by-reference) These subscripts may be
 passed: 
            "ID" - the identifier 
            "TEXT" - 
            "SYSTEM" - name of the code system 
            "ALTERNATE ID" - alternate identifier 
            "ALTERNATE TEXT" 
            "ALTERNATE SYSTEM" - name of the alternate coding system 
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The sequence # of the field.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If specified, the data type is 'demoted'
 to a component value.  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional, defaults to 1) The occurrence #.  For a
 non-repeating fields, this parameter is not necessary.  
  
COMPONENT/ENTRY POINT: SETHD(.SEG,.VALUE,FIELD,COMP,REP)
 COMPONENT DESCRIPTION:   
        Sets a value that is an HL7 Hierarchic Designator data type (HL7
 Section 
        Reference 2.9.21) into the segment in the specified field.  IF the 
        component is specified, then the data type is 'demoted' to a component, 
        and its components are 'demoted' to subcomponents.  
  
VARIABLES: SEG                          TYPE: Both
 VARIABLES DESCRIPTION:   (required, pass-by-reference) The array where the
 segment is being built.  
  
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   (required, pass-by-reference) These subscripts may be
 passed: 
           "NAMESPACE ID" 
           "UNIVERSAL ID" 
           "UNIVERSAL ID TYPE" 
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The sequence # of the field.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If specified, the data type is 'demoted'
 to a component value.  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional, defaults to 1) The occurrence #.  For a
 non-repeating fields, this parameter is not necessary.  
  
COMPONENT/ENTRY POINT: SETCNE(.SEG,.VALUE,FIELD,COMP,REP)
 COMPONENT DESCRIPTION:   
       Sets a value that is an HL7 Coded With No Exceptions  data type (HL7 
       Section Reference 2.9.8) into the segment in the specified field.  IF
 the 
       component is specified, then the data type is 'demoted' to a component, 
       and its components are 'demoted' to subcomponents.  
  
  
VARIABLES: SEG                          TYPE: Both
 VARIABLES DESCRIPTION:   (required, pass-by-reference) The array where the
 segment is being built.  
  
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   (required, pass-by-reference) These subscripts may be
 passed: 
           "ID" - the identifier 
           "TEXT" - 
           "SYSTEM" - name of the code system 
           "ALTERNATE ID" - alternate identifier 
           "ALTERNATE TEXT" 
           "ALTERNATE SYSTEM" - name of the alternate coding system 
           "SYSTEM VERSION" - version ID of the coding system 
           "ALTERNATE SYSTEM VERSION" - version ID of the alternate coding 
                                        system 
           "ORIGINAL TEXT" 
  
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The sequence # of the field.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If specified, the data type is 'demoted'
 to a component value.  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional, defaults to 1) The occurrence #.  For a
 non-repeating fields, this parameter is not necessary.  
  
COMPONENT/ENTRY POINT: SETCWE(.SEG,.VALUE,FIELD,COMP,REP) 
 COMPONENT DESCRIPTION:   
       Sets a value that is an HL7 Coded With Exceptions  data type (HL7
 Section 
       Reference 2.9.11) into the segment in the specified field.  IF the 
       component is specified, then the data type is 'demoted' to a component, 
       and its components are 'demoted' to subcomponents.  
  
  
VARIABLES: SEG                          TYPE: Both
 VARIABLES DESCRIPTION:   (required, pass-by-reference) The array where the
 segment is being built.  
  
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   (required, pass-by-reference) These subscripts may be
 passed: 
           "ID" - the identifier 
           "TEXT" - 
           "SYSTEM" - name of the code system 
           "ALTERNATE ID" - alternate identifier 
           "ALTERNATE TEXT" 
           "ALTERNATE SYSTEM" - name of the alternate coding system 
           "SYSTEM VERSION" - version ID of the coding system 
           "ALTERNATE SYSTEM VERSION" - version ID of the alternate coding 
                                        system 
           "ORIGINAL TEXT" 
  
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) The sequence # of the field.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If specified, the data type is 'demoted'
 to a component value.  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional, defaults to 1) The occurrence #.  For a
 non-repeating fields, this parameter is not necessary.  
  
COMPONENT/ENTRY POINT: SETAD(.SEG,.VALUE,FIELD,COMP,REP)
 COMPONENT DESCRIPTION:   
       Sets an AD data type (Address, HL7 Section Reference 2.9.1) into the 
       segment in the specified field. It can also be used to set the 1st 8 
       components of the XAD (Extended Address) data type.  IF the component is 
       specified, then the data type is 'demoted' to a component, and its 
       components are 'demoted' to subcomponents.  
  
VARIABLES: SEG                          TYPE: Both
 VARIABLES DESCRIPTION:   (required, pass-by-reference) The array where the
 segment is being built.  
  
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   (required, pass-by-reference) These subscripts may be
 passed: 
           "STREET1" -street address 
           "STREET2" - other designation 
           "CITY" 
           "STATE" - state or province 
           "ZIP" - zip or postal code 
           "COUNTRY" 
           "TYPE"  - address type 
           "OTHER" - other geographic designation 
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) the sequence # of the field.  
  
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If specified, the data type is 'demoted'
 to a component value.  
  
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional, defaults to 1) The occurrence #.  For a
 non-repeating fields, this parameter is not necessary.  
  
COMPONENT/ENTRY POINT: SETXPN(.SEG,.VALUE,FIELD,COMP,REP)
 COMPONENT DESCRIPTION:   Sets an XPN data type (extended person name) into the
 segment in the specified field. If the component is specified, then the data
 type is 'demoted' to a component, and its components are 'demoted' to 
 subcomponents.  
VARIABLES: SEG                          TYPE: Both
 VARIABLES DESCRIPTION:   The array of the segment being built and returned.  
  
 (required, pass by reference) 
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   VALUE is a subscripted array. The following
 subscripts can be passed: 
    "FAMILY" 
    "GIVEN" first name 
    "SECOND" second and further names or initials 
    "SUFFIX" (e.g., JR) 
    "PREFIX" (e.g., DR) 
    "DEGREE" (e.g., MD) 
  
 (required, pass-by-reference) 
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   The sequence number of the field.  
  
 (required) 
VARIABLES: COMP                         TYPE: Input
 VARIABLES DESCRIPTION:   If specified, the data type is 'demoted' to a
 component value.  
  
 (optional) 
VARIABLES: REP                          TYPE: Input
 VARIABLES DESCRIPTION:   The occurrence number. For non-repeating fields, this
 parameter is not necessary.  
  
 (optional, defaults to 1) 
  DATE ACTIVATED: JAN 22, 2015

NUMBER: 4854                            IA #: 4854
  DATE CREATED: MAY 08, 2006
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMRCGUIS
  NAME: DBIA4854                        ID: GMRCGUIS
 GENERAL DESCRIPTION:   This DBIA documents call made to routine GMRCGUIS.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: STATUS(IEN,STATUS,LSTACT,PROVIDER,DATE,.WHOGETS,.COMMENTS
)
 COMPONENT DESCRIPTION:   This entry point was written for Scheduling Consult
 Link for the purpose of updating the CPRS GUI Order Status.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN or REQUEST/CONSULTATION file (#123).  
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of ORDER STATUS file (#100.01) that represents
 the status of the consult.  
VARIABLES: LSTACT                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of REQUEST ACTION TYPES file (#123.1) that
 represents the last action to be added to the consult.  
VARIABLES: PROVIDER                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN  of NEW PERSON file (#200) denoting provider
 resonsible for the action.  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   Date/time the activity took place (DEFAULT = NOW) 
VARIABLES: WHOGETS                      TYPE: Input
 VARIABLES DESCRIPTION:   Array (passed by reference) of alert recipients who
 should be alerted of comment addition. ARRAY(IEN of #200 file)="".  
VARIABLES: COMMENTS                     TYPE: Input
 VARIABLES DESCRIPTION:   Array (passed by reference) of comments describing
 the action format COMMENTS(1)="xxxx", COMMENTS(2)="xxxx" 
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Scheduling Consult Link makes call to update Order CPRS
 Status.  
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   When an appointment is canceled in MBAA, MBAA makes a
 call to the STATUS^GMRCGUIS API to update the consult to show the appointment
 is canceled. 

NUMBER: 4855                            IA #: 4855
  FILE NUMBER: 200                      DATE CREATED: MAY 09, 2006
  CUSTODIAL PACKAGE: KERNEL             USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: NPI field for #200
 GENERAL DESCRIPTION:   Set ^DD for NPI fields in files #200 and #4: 
  
 ; Set un-editable for STATUS field (#.02) in EFFECTIVE DATE/TIME subfile
 (#200.042) I $P(^DD(200.042,.02,0),"^",2)'["I" D . S
 $P(^DD(200.042,.02,0),"^",2)=$P(^DD(200.042,.02,0),"^",2)_"I" ; Set
 un-editable for STATUS field (#.02) in EFFECTIVE DATE/TIEM subfile (#4.042) I
 $P(^DD(4.042,.02,0),"^",2)'["I" D . S
 $P(^DD(4.042,.02,0),"^",2)=$P(^DD(4.042,.02,0),"^",2)_"I" ; Set DEL-LAYGO for
 NPI field (#41.99) in INSTITUTION file (#4) S
 ^DD(4,41.99,"DEL",11,0)="D:'$D(XUMF) EN^DDIOL(""Entries must be inactivated
 via the Master File Server(MFS)."","""",""!?5,$C(7)"") I $D(XUMF 
  STATUS: Active
SUBSCRIBING PACKAGE: 1

NUMBER: 4856                            IA #: 4856
  DATE CREATED: SEP 08, 2006
  CUSTODIAL PACKAGE: HEALTH DATA & INFORMATICS
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HDISVCUT
  NAME: DBIA4856                        ID: HDISVCUT
 GENERAL DESCRIPTION:   API will be used by HSITES as part of their software to
 insure that mirrored test accounts are setup properly.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: TESTACT
 COMPONENT DESCRIPTION:   This API will be used by HSITES.  HSITES has a
 software tool which sites use to insure a test account has been setup
 properly.  This API will change the mirrored production account data to
 function properly in the test site environment.  It will update the Domain/IP
 Address and the System Type (Production or Test) in the HDIS System file
 (#7118.21).  

NUMBER: 4857                            IA #: 4857
  DATE CREATED: MAY 11, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DBIA4857
 GENERAL DESCRIPTION:   General Description goes here 
  STATUS: Pending
KEYWORDS: keywords
KEYWORDS: goes
KEYWORDS: here
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Subscribing Details 

NUMBER: 4858                            IA #: 4858
  DATE CREATED: MAY 15, 2006            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSODI
  NAME: DBIA 4858                       ID: PSODI
 GENERAL DESCRIPTION:   This DBIA is provided by PSO (Outpatient Pharmacy) as
 an API to do simulated VA FileMan calls. This API is to be used in the future
 by all packages needing to use FileMan to look at the PRESCRIPTION file (#52)
 and the OUTPATIENT SITE file (#59) as all the Pharmacy packages are being 
 re-engineered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DIQ(PSOFILE,DIC,.DR,.DA,.DIQ)
 COMPONENT DESCRIPTION:   FORMAT: D DIQ^PSODI(PSOFILE,DIC,.DR,.DA,.DIQ) 
VARIABLES: PSOFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   File number used for validation of access [REQUIRED] 
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   See VA FileMan Programmer Manual for EN^DIQ1 call for
 DIC, DR, DA, and DIQ input definitions 
VARIABLES: PSODIY                       TYPE: Output
 VARIABLES DESCRIPTION:   PSODIY will return null if the value for PSOFILE is
 valid (it will return -1 if conditions were not met)  
  
 See VA FileMan Programmer Manual for EN^DIQ1 output definition 
COMPONENT/ENTRY POINT: STATUS(PSOFILE,PSOFIELD,LIST)
 COMPONENT DESCRIPTION:   FORMAT: D STATUS^PSODI(PSOFILE,PSOFIELD,LIST)  NOTE:
 Make sure LIST("POINTER") is not defined when making this call.  
VARIABLES: PSOFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   File number used for validation of access [REQUIRED] 
VARIABLES: PSOFIELD                     TYPE: Input
 VARIABLES DESCRIPTION:   Field number from the specified file associated with
 the value in PSOFILE [REQUIRED] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Array name defined by the calling application
 [REQUIRED] 
VARIABLES: PSODIY                       TYPE: Output
 VARIABLES DESCRIPTION:   PSODIY will return null if the value for PSOFILE is
 valid (it will return -1 if conditions were not met) 
COMPONENT/ENTRY POINT: DIC(PSOFILE,.DIC,.X)
 COMPONENT DESCRIPTION:   FORMAT: D DIC^PSODI(PSOFILE,.DIC,.X) 
VARIABLES: PSOFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   File number used for validation of access [REQUIRED] 
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   See VA FileMan Programmer Manual for ^DIC call for
 DIC and X input definitions 
VARIABLES: PSODIY                       TYPE: Output
 VARIABLES DESCRIPTION:   PSODIY will return null if the value for PSOFILE is
 valid (it will return -1 if conditions were not met) 
COMPONENT/ENTRY POINT: GET1(PSOFILE,PSOIEN,PSOFIELD,PSOFLAGS,PSOWORD)
 COMPONENT DESCRIPTION:   FORMAT: 
    S X=$$GET1^PSODI(PSOFILE,PSOIEN,PSOFIELD,PSOFLAGS,PSOWORD) 
VARIABLES: PSOFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   File or sub-file number [REQUIRED] 
VARIABLES: PSOIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN for data return [REQUIRED] 
VARIABLES: PSOFIELD                     TYPE: Input
 VARIABLES DESCRIPTION:   Field for data return [REQUIRED] 
VARIABLES: FLAGS                        TYPE: Input
 VARIABLES DESCRIPTION:   Controls the processing of data returned [REQUIRED] 
VARIABLES: PSOWORD                      TYPE: Input
 VARIABLES DESCRIPTION:   Return of word processing fields [REQUIRED only with
 word processing fields] 
VARIABLES: $$GET1                       TYPE: Output
 VARIABLES DESCRIPTION:   Returned field will be in the format "1^(field)". 
 See VA FileMan Programmer Manual V 22.0 for $$GET1^DIQ output definition.  
  DATE ACTIVATED: JUL 10, 2007

NUMBER: 4859                            IA #: 4859
  DATE CREATED: MAY 22, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORCHECK
  NAME: ORDER CHECK API                 ID: ORCHECK
 GENERAL DESCRIPTION:   This Integration Aggreement will permit ancilliary
 packages to obtain the order check information for a specific order.  
  
  STATUS: Active
KEYWORDS: ORDER CHECK
KEYWORDS: ORDERCHECK
KEYWORDS: ORCHECK
COMPONENT/ENTRY POINT: OCAPI
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the order number to gather the order checking
 info on.  
  
VARIABLES: ORPLACE                      TYPE: Both
 VARIABLES DESCRIPTION:   This variable is the subscript that will be used to
 store the information in the return data.  i.e.  
   ^TMP($J,ORPLACE,D0,"OC LEVEL")="order check level" 
                    ,"OC TEXT")="order check text" 
                    ,"OR REASON")="over ride reason text" 
                    ,"OR PROVIDER")="provider DUZ who entered over ride reason" 
                    ,"OR DT")="date/time over ride reason was entered" 
  
  DATE ACTIVATED: MAY 30, 2006

NUMBER: 4860                            IA #: 4860
  DATE CREATED: MAY 23, 2006
  CUSTODIAL PACKAGE: HEALTH DATA & INFORMATICS
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HDISVF01
  NAME: HDI                             ORIGINAL NUMBER: 4638
  ID: HDISVF01
 GENERAL DESCRIPTION:   API for storage of the file/field implementation
 status.  
  
 Packages may invoke this API without registering another IA only if the domain
 and files being referenced are in the calling package's numberspace.  
  STATUS: Active
KEYWORDS: DATA STANDARDIZATION
COMPONENT/ENTRY POINT: SETSTAT
 COMPONENT DESCRIPTION:   Set file/field implementation status 
  
 Notes: 
  
 - If time is not included with the date, 1 second past 
   midnight will be used as the time 
  
 - If an entry for the given file/field and date/time 
   already exists, a new entry will still be added 
  
 Example: 
  
  D SETSTAT^HDISVF01(95.3,"",6,"") 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   File number 
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   Field number (defaults to .01) 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Status code to set (defaults to "not started") 
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   FileMan date/time to return status for (Optional-
 defaults to NOW) 
VARIABLES: STTYPE                       TYPE: Input
 VARIABLES DESCRIPTION:   Type of status code being used (Optional- defaults to
 Client) 
  
 1 = Client      2 = Server 
VARIABLES: FAC                          TYPE: Input
 VARIABLES DESCRIPTION:   Facility number (Optional- defaults to current) 
VARIABLES: DOMAIN                       TYPE: Input
 VARIABLES DESCRIPTION:   Domain/IP address (Optional- defaults to current) 
VARIABLES: SYTYPE                       TYPE: Input
 VARIABLES DESCRIPTION:   Type of system (Optional- defaults to current) 
  
 0 = Test     1 = Production 

NUMBER: 4861                            IA #: 4861
  FILE NUMBER: 771                      GLOBAL ROOT: HL(771,
  DATE CREATED: MAY 31, 2006            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4861
  ID: HL(771,
GLOBAL REFERENCE: HL(771,"B"
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
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 during post install.  
  STATUS: Active
KEYWORDS: HL7
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 4862                            IA #: 4862
  DATE CREATED: JUN 14, 2006            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4862
 GENERAL DESCRIPTION:   The HL LOGICAL LINK file entry IBBPFSS1 may be
 referenced from the LOGICAL LINK field as packages export PROTOCOL file
 entries using that link.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 4863                            IA #: 4863
  DATE CREATED: JUN 05, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: USING OR RDI CACHE TIME AS PARAMETER
 GENERAL DESCRIPTION:   This IA is to allow the ART package to use the
 parameter "OR RDI CACHE TIME" parameter in a call to GET^XPAR.  
  STATUS: Active
KEYWORDS: OR RDI CACHE TIME
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING

NUMBER: 4864                            IA #: 4864
  DATE CREATED: JUN 13, 2006            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LR7OR4
  NAME: LR7OR4                          ID: LR7OR4
 GENERAL DESCRIPTION:   This DBIA formalizes the documentation for calls to
 OR7OR4 as documented in the OE/RR Interface Specification document.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ONE(.Y,TEST)
 COMPONENT DESCRIPTION:   This API gets Laboratory test description information
 for a single test.  
  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   This is the name of the array to return test
 information in.  
VARIABLES: TEST                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal file number of the test in the
 LABORATORY TEST (#60) file for which information is being requested.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4865                            IA #: 4865
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: JUN 14, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4865
  ID: DPT(
GLOBAL REFERENCE: DPT(
FIELD NUMBER: .19                       FIELD NAME: DIVISION
  LOCATION:  ;                          ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Division of inpatient location 
  
 GENERAL DESCRIPTION:   Clinical Reminders will use VA FileMan to get the
 Division that a patient belongs to by getting the data from field .19 DIVISION
 in the PATIENT file #2.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DIVISION
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Clinical Reminders and Geriatric Extended Care will be
 obtaining the Division that a patient belongs to, by using VA FileMan to get
 the information from field .19 DIVISION in the PATIENT file #2.  
  
  

NUMBER: 4866                            IA #: 4866
  FILE NUMBER: 120.51                   GLOBAL ROOT: GMRD(120.51
  DATE CREATED: JUL 10, 2006
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4866
  ID: GMRD(120.51
GLOBAL REFERENCE: GMRD(120.51,
 GENERAL DESCRIPTION:   Clinical Procedures is using a Fileman call $$FIND1^DIC
 to find the internal entry number of the Vital type in GMRV Vital Type file
 (#120.51).  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VITAL TYPE
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES

NUMBER: 4867                            IA #: 4867
  FILE NUMBER: 120.5                    GLOBAL ROOT: GMR(120.5
  DATE CREATED: JUL 26, 2006
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4867
  ID: GMR(120.5
GLOBAL REFERENCE: GMR(120.5,D0)
 GENERAL DESCRIPTION:   This IA will be used in conjunction with IA 4815.  IA
 4815 allows Clinical Procedures (CP) to add vital measuements.  IA 4867 gives
 CP the permission to lock the ^GMR(120.5,0) global root before adding the 
 vital measurements and let CP use a reverse $O command ^GMR(120.5,"A") to get
 the internal entry number of the last entry of vital measurement that was
 added.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VITALS MEASUREMENT
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES

NUMBER: 4868                            IA #: 4868
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: JUL 31, 2006            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4868
  ID: VA(200
GLOBAL REFERENCE: VA(200,'AUSER',[.01 value],IEN)
 GENERAL DESCRIPTION:   Subscribers have permission to $O through the "AUSER"
 index of the NEW PERSON file (#200) to get a list of available provider names. 
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NEW PERSON
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 9/25/19, effective with Mental Health patch
 YS*5.01*130 which adds support for a web-based version of MHA (Mental Health
 Assistant). ICR 4868 supports the lookup of active users in the web-based
 application.  

NUMBER: 4869                            IA #: 4869
  FILE NUMBER: 45.7                     GLOBAL ROOT: DIC(45.7
  DATE CREATED: AUG 03, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4869
  ID: DIC(45.7
GLOBAL REFERENCE: DIC(45.7,
 GENERAL DESCRIPTION:   The CP Definition file (#702.01) points to the Facility
 Treating Specialty file (#45.7).  In order to print/display a CP Studies List 
 by Treating Specialty, Clinical Procedures will use the following DIC call to
 query for a Facility Treating Specialty: 
  
 S DIC="^DIC(45.7,",DIC(0)="EMQ" D ^DIC 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TREATING SPECIALTY
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES

NUMBER: 4870                            IA #: 4870
  FILE NUMBER: 443.6                    GLOBAL ROOT: DD(443.61,8
  DATE CREATED: JAN 04, 2011            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: FILE 442 AND 443.6 FCPFIELD FIX FILE DD
  ID: DD(443.61,8
GLOBAL REFERENCE: FCP
FIELD NUMBER: 8                         FIELD NAME: FCP
  LOCATION: 8;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   FEDERAL SUPPLY CLASSIFICATION 
GLOBAL REFERENCE: 442
FIELD NUMBER: 8                         FIELD NAME: FCP
  LOCATION: 8;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   FEDERAL SUPPLY CLASSIFICATION 
 GENERAL DESCRIPTION:   This is a one time aggreement via patch PRC*5.1*128.  
  
 Kill node 9 from following field DD definition: 
  
 ^DD(443.61,8,0)=FEDERAL SUPPLY CLASSIFICATION^RP441.2'X^PRC(441.2,^2;3^D 
 EN100^PRCHNPO7 
             .1)=FSC/PSC ^DD(443.61,8,1,0)=^.1 
 ^DD(443.61,8,1,1,0)=443.61^AU^MUMPS 
                  1)=I $G(PRCHNORE)=1 D:PRCHAMDA=21 EN1^PRCHAMXG Q:PRCHAMDA=21 
 D FLAG^PRCHMA Q:$T  I PRCHAMDA=23 S PRCHX=X,X=0 D EN1^PRCHAMXD S X=PRCHX K 
 PRCHX 
                  2)=I $G(PRCHNORE)=1,PRCHAMDA=23 S FLAG=1 D EN1^PRCHAMXD 
 ^DD(443.61,8,1,1,"%D",0)=^^5^5^2970416^^^^ ^DD(443.61,8,1,1,"%D",1,0)=This
 x-ref will update the CHANGES multiple whenever a 'Line Item Add' or a 
 ^DD(443.61,8,1,1,"%D",2,0)='Line Item Edit' amendment changes this field.  
 ^DD(443.61,8,1,1,"%D",3,0)=                 
 ^DD(443.61,8,1,1,"%D",4,0)=****NOTE-See routine PRCHAMXA for information on
 variable PRCHNORE and ^DD(443.61,8,1,1,"%D",5,0)=incidence of undefined DIK
 variable errors.  ^DD(443.61,8,1,1,"DT")=2950321 ^DD(443.61,8,3)= 
              9)=^        <<<=========== kill this field 
 ^DD(443.61,8,21,0)=^.001^2^2^3050909^^^^ ^DD(443.61,8,21,1,0)=This is the
 Federal Supply Classification for an item, or the Product 
 ^DD(443.61,8,21,2,0)=Service Code for a service.  ^DD(443.61,8,"DT")=3050909 
  
  
 Global ^DD(442.01,8 -- NOTE: translation in effect ^DD(442.01,8,0)=FEDERAL
 SUPPLY CLASSIFICATION^RP441.2'X^PRC(441.2,^2;3^D EN10^PRCHNPO7 
             .1)=FSC/PSC 
              3)=ANSWER MUST BE 1-24 CHARACTERS IN LENGTH 
              9)=^         <<<=========== kill this field 
 ^DD(442.01,8,21,0)=^^2^2^3050809^ ^DD(442.01,8,21,1,0)=This is the Federal
 Supply Classification for an item, or the Product ^DD(442.01,8,21,2,0)=Service
 Code for a service.  ^DD(442.01,8,"DT")=3050809 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FCP
SUBSCRIBING PACKAGE: IFCAP
 SUBSCRIBING DETAILS:   This is a one time agreement via patch PRC*5.1*128.  
  
 Must kill the 9 node in the subfiles 443.61 and 442.01 in ^DD attributes for
 field 8 to allow delivery schedule editing to echo and prevent infinite loop
 problem for user. 
  DATE ACTIVATED: JAN 10, 2011

NUMBER: 4871                            IA #: 4871
  DATE CREATED: JUL 26, 2006            CUSTODIAL PACKAGE: 804
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: REMOTE DATA HL7 REQUEST/RESPONSE
 GENERAL DESCRIPTION:   This DBIA is intended to document the transmission of
 data from CDS (Clinical Data Service) located on a server in the AAC (Austin
 Automation Center) to the OE/RR package running on servers located at each VA 
 Medical Center.  
  
 The OE/RR package uses the direct connect API of the MESSAGING package to send
 a request HL7 message to CDS.  This message sends as parameters the patient
 ICN, a domain specific "What Code", a date range that specifies what dates are
 acceptable for the data that will be returned by CDS.  The request HL7 SPR
 segment is in the following format: (variables surrounded in _"VARIABLE"_) 
  
 SPR^XWBDRPC845-569716_0^T^ZREMOTE RPC^@SPR.4.2~003RPC017ORWRP REPORT
 TEXT&006RPCVER0010&007XWBPCNT0017&007XWBESSO066321214321\F\ 
 \F\\F\657\F\48102&007XWBDVER0011&006XWBSEC0043.14&002P10187369543; 
 _"ICN"_&002P2055_"WHAT CODE"_;1\S\RXOP;ORDV06;28;200&002P3000&002P4 
 000&002P5000&002P6007_"START DATE"_&002P7000_"END DATE"_ 
  
  
 CDS then returns the requested data by sending a response HL7 message that is
 handed to OE/RR by the MESSAGING package API.  The definition of how the
 return data is formated is specified by the following RDF segment for each
 domain: 
  
 ALLERGIES 
 =========
 RDF^12^Standardized~ST~1|Facility Name~ST~30|Entered in Error~ST~2 |Allergy
 Type~CE~45|GMR Allergy~CE~450|Agent~ST~30|Reaction~CE~430 |Drug
 Classes~CE~190|Drug Ingredients~CE~190|Verification Date~TS~ 26
 |Observed/Historical Flag~CE~150|Comments~ST~255 
  
 OUTPATIENT PHARMACY 
 ===================
 RDF^17^Standardized~ST~1|Pharmacy Division~ST~30|Drug~CE~370|NDC Drug~CE~65|Rx
 Number~ST~20|Order Status Modifiers~CWE~180|Quantity in Rx~NM~10|Days
 Supply~NM~10|Expire/Cancel Date~TS~26|Issue Date~ TS~26|Last Fill Date~TS~26|
 Refills Remaining~NM~10|Provider~ST~80| Cost to Fill Rx~MO~10|SIG~ST~250|
 Station Number~IS~3|Primary Facility~ST~30 
  STATUS: Active
KEYWORDS: RDI
KEYWORDS: CDS
KEYWORDS: REMOTE DATA
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4872                            IA #: 4872
  FILE NUMBER: 136                      GLOBAL ROOT: SRO(136,
  DATE CREATED: AUG 02, 2006            CUSTODIAL PACKAGE: SURGERY
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SURGERY PROCEDURE/DIAGNOSIS CODES
  ID: SRO(136,
GLOBAL REFERENCE: SRO(136,D0,0)
FIELD NUMBER: .02                       FIELD NAME: PRINCIPAL PROCEDURE CODE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: PRIN POSTOP DIAGNOSIS CODE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRO(136,D0,3,D1,0)
FIELD NUMBER: .01                       FIELD NAME: OTHER PROCEDURE CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRO(136,D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: OTHER POSTOP DIAGNOSIS CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRO(136,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PRIN PROCEDURE CPT MODIFIER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRO(136,D0,3,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: OTHER PROCEDURE CPT MODIFIER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This integration agreement grants read access to
 Surgery case coding information from the SURGERY PROCEDURE/DIAGNOSIS CODES
 file (#136).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   Health Summary will be using a FileMan call to retrieve
 data.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA added as the subcriber for VIAB SRGY RPTLIST RPC
 for get surgery  report. 
  DATE ACTIVATED: MAY 24, 2012

NUMBER: 4873                            IA #: 4873
  FILE NUMBER: 63                       GLOBAL ROOT: LR(63,
  DATE CREATED: AUG 22, 2006            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Blood Bank
  ID: LR(63,
GLOBAL REFERENCE: LR(D0,"BB",
FIELD NUMBER: 6                         FIELD NAME: ACCESSION NUMBER
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the blood bank accession.  
 GLOBAL DESCRIPTION:   Blood Bank node in Lab Data file (#63).  
 GENERAL DESCRIPTION:   Accessing the "BB" node of the Lab Data file (#63).  
  STATUS: Active
KEYWORDS: Blood Bank Data
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 4874                            IA #: 4874
  FILE NUMBER: 66                       GLOBAL ROOT: LAB(66,
  DATE CREATED: AUG 22, 2006            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: BLOOD PRODUCT
  ID: LAB(66,
GLOBAL REFERENCE: LAB(66,
FIELD NUMBER: .06                       FIELD NAME: MODIFICATION CRITERIA
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   If this product can be made from another product present
 in inventory enter appropriate response. If selection is D (DIVIDED) a single
 letter suffix will be appended (from A-E) to the unit ID depending upon the 
 number of aliquots up to 5.  This field is used to trigger the appropriate 
 prompts if the new product(s) will be divided units or a pool.  
FIELD NUMBER: 14                        FIELD NAME: MODIFIED BEFORE RELEASE
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   If component must be further modified before release (ex.
 frozen RBC must  be deglycerolized before transfusion) a 'YES' is entered.  
  STATUS: Active
KEYWORDS: BLOOD PRODUCT FILE (#66)
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 4875                            IA #: 4875
  DATE CREATED: AUG 16, 2006
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RAO7UTL1
  NAME: Return exam date/time for interpreted non-cancelled case.
  ID: RAO7UTL1
 GENERAL DESCRIPTION:   This patient specific VistA Radiology/Nuclear Medicine
 function will return to VistA MPI the exam date/time (in FileMan internal
 format) of the most recent non-cancelled and interpreted case.  
  
 Please note that an interpreted case usually implies that a provider has 
 transcribed the report. This IA will also consider a "stub" report to be 
 interpreted for the purposes of this IA.  
  
 A "stub" report has the following characteristics: 
 --------------------------------------------------
 1) The ACTIVITY LOG (#100) indicates that images were collected via VistA 
    Imaging 2) The REPORT STATUS (#5) field of the report record is 
    null                     3) The report record points to an image record in
 the IMAGE (#2005) 
    file        4) No IMPRESSION TEXT (#300) exists for the report 
    record                        5) No PROBLEM STATEMENT (#25) exists for the
 report 
    record                       6) No REPORT TEXT (#200) exists for the report
 record 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MPI & RADIOLOGY
KEYWORDS: MPI & RAD/NUC MED
KEYWORDS: MPI & RADIOLOGY EXAM DATE/TIME
COMPONENT/ENTRY POINT: XAMDT
 COMPONENT DESCRIPTION:   The XAMDT entry point will be called by the VistA MPI
 application. VistA MPI will provide as input, the DFN of the patient. The
 VistA Radiology/Nuclear Medicine application will return, in internal VA 
 FileMan format, the exam date/time of the most recent non-cancelled 
 interpreted case.  
  
 In the case where the VistA Radiology/Nuclear Medicine is unable to return the
 exam date/time of the most recent non-cancelled interpreted case the following
 data string will be returned: "0^an active exam with interpretation was not
 found for this patient".  
VARIABLES: RADFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The DFN of the patient.  
VARIABLES: RAXAMDT                      TYPE: Output
 VARIABLES DESCRIPTION:   The exam date/time (in internal VA FileMan format) of
 the most recent non-cancelled interpreted case.  
  
 In the case where the VistA Radiology/Nuclear Medicine is unable to return the
 exam date/time of the most recent non-cancelled interpreted case the following
 data string will be returned: "0^an active exam with interpretation was not
 found for this patient".  
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   VistA Radiology/Nuclear Medicine will provide a
 function that will return to VistA MPI the exam date/time (in FileMan internal
 format) of the most recent non-cancelled interpreted case for a specific
 patient.  

NUMBER: 4876                            IA #: 4876
  FILE NUMBER: 116.2                    GLOBAL ROOT: FH(116.2,
  DATE CREATED: AUG 22, 2006            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PRODUCTION DIET file (#116.2)
  ID: FH(116.2,
GLOBAL REFERENCE: FH(116.2,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 FIELD DESCRIPTION:   This field contains the name of the production diet.  
 GENERAL DESCRIPTION:   Production Diet File (#116.2) is pointed to via a
 variable pointer field from DSS file (#728.45).  
  STATUS: Active
KEYWORDS: PRODUCTION DIET
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 4877                            IA #: 4877
  FILE NUMBER: 118                      GLOBAL ROOT: FH(118,
  DATE CREATED: AUG 22, 2006            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SUPPLEMENTAL FEEDINGS FILE (#118)
  ID: FH(118,
GLOBAL REFERENCE: FH(118,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 FIELD DESCRIPTION:   This field contains the name of the Supplemental Feeding. 
 
 GENERAL DESCRIPTION:   Supplemental Feedings file (#118) is pointed to via a
 variiable pointer field in DSS file (#728.45).  
  STATUS: Active
KEYWORDS: SUPPLMENTAL FEEDINGS
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 4878                            IA #: 4878
  FILE NUMBER: 118.2                    GLOBAL ROOT: FH(118.2,
  DATE CREATED: AUG 22, 2006            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TUBEFEEDING FILE (#118.2)
  ID: FH(118.2,
GLOBAL REFERENCE: FH(118.2,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 FIELD DESCRIPTION:   This is the name of the tubefeeding product as it will
 appear on all lists and displays.  
 GENERAL DESCRIPTION:   Tuebefeeding file (#118.2) is pointed via a variable
 pointer field in DSS file (#728.45).  
  STATUS: Active
KEYWORDS: TUBEFEEDING
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 4879                            IA #: 4879
  DATE CREATED: AUG 09, 2006            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHL6
  NAME: IA for IFCAP patch PRC*5.1*103 to read Prosthetic File 664
  ID: PRCHL6
 GENERAL DESCRIPTION:   This integration agreement will allow IFCAP to read
 Prosthetics File 664 as part of IFCAP patch PRC*5.1*103.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IFCAP
 SUBSCRIBING DETAILS:   A Delphi component will be created as part of IFCAP
 5.1*103. During the lookup of file 442, if the purchase order is a prosthetics
 order, the new option will provide "line item detail" out of file 664. At
 present, line item detail of Prosthetics purchase order resides in file 664.  

NUMBER: 4880                            IA #: 4880
  FILE NUMBER: 118.3                    GLOBAL ROOT: FH(118.3,
  DATE CREATED: AUG 22, 2006            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: STANDING ORDERS FILE (#118.3)
  ID: FH(118.3,
GLOBAL REFERENCE: FH(118.3,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 FIELD DESCRIPTION:   This field contains the name of a standing order. It may
 be such things as 'double portions', 'extra coffee', or even preferences such
 as 'no fish'.  
 GENERAL DESCRIPTION:   Standing Orders file (#118.3) is pointed via a variable
 pointer field in DSS file (#728.45).  
  STATUS: Active
KEYWORDS: STANDING ORDERS
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 4881                            IA #: 4881
  FILE NUMBER: 119.71                   GLOBAL ROOT: FH(119.71,
  DATE CREATED: AUG 22, 2006            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PRODUCTION FACILITY FILE (#119.71)
  ID: FH(119.71,
GLOBAL REFERENCE: FH(119.71,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 FIELD DESCRIPTION:   This is the name of the Production Facility. It is
 generally a main kitchen used for the preparation of bulk food to be served by
 a  Service Point.  
 GENERAL DESCRIPTION:   Production Facility file (#119.71) is pointd via a
 variable pointer field in DSS file (#728.46).  
  STATUS: Active
KEYWORDS: PRODUCTION FACILITY
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 4882                            IA #: 4882
  FILE NUMBER: 119.72                   GLOBAL ROOT: FH(119.72,
  DATE CREATED: AUG 09, 2006            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SERVICE POINT FILE (#119.72)
  ID: FH(119.72,
GLOBAL REFERENCE: FH(119.72,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 FIELD DESCRIPTION:   This is the name of the Service Point. It is either a
 tray assembly line or a cafeteria. It provides food to a group of wards.  
 GENERAL DESCRIPTION:   Service Point file (#119.72) ia pointed to via a
 variable pointer field in DSS file (#728.46).  
  STATUS: Active
KEYWORDS: SERVICE POINT
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 4883                            IA #: 4883
  DATE CREATED: SEP 06, 2006            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FHDSSAPI
  NAME: FHDSSAPI                        ID: FHDSSAPI
 GENERAL DESCRIPTION:   DATA^FHDSSAPI was created to extract N&FS data.  
  STATUS: Active
KEYWORDS: FHDSSAPI
COMPONENT/ENTRY POINT: DATA(START_DATE,END_DATE) 
 COMPONENT DESCRIPTION:   N&FS created the DATA^FHDSSAPI API at the request of
 Management Systems so that extracts could be done from the NUTRITION PATIENT
 file (#115).  
VARIABLES: START_DATE                   TYPE: Input
 VARIABLES DESCRIPTION:   Start date for data to be extracted.  
VARIABLES: END_DATE                     TYPE: Input
 VARIABLES DESCRIPTION:   End date for data to be extracted.  
VARIABLES: TMP($J,'FH',                 TYPE: Output
 VARIABLES DESCRIPTION:   Sample Call: D DATA^FHDSSAPI(3020101,302031) 
  
 INPATIENT DATA 
 ==============
  
 Diets: 
 -----
 Return Array: ^TMP($J,"FH",DATE/TIME,DFN,ADMISSION,"INP") 
  
 Node 0 returned 
  
 Supplemental Feedings: 
 ---------------------
 Return Array: ^TMP($J,"FH",DATE/TIME,DFN,ADMISSION,"SF") 
  
 Node 0 returned 
  
 Standing Orders: 
 ---------------
 Return Array: ^TMP($J,"FH",DATE/TIME,DFN,ADMISSION,"SO") 
  
 Node 0 returned 
  
 Tube Feedings: 
 -------------
 Return Array: ^TMP($J,"FH",DATE/TIME,DFN,ADMISSION,"TF") 
  
 Node 0 returned 
  
  
 OUTPATIENT MEALS 
 ================
  
 Recurring Meals: 
 ---------------
 Return Array: ^TMP($J,"FH",DATE/TIME,DFN,NUMBER,"RM") 
  
 Node 0 returned 
  
 Tube Feedings: 
 -------------
 Return Array: ^TMP($J,"FH",DATE/TIME,DFN,ADMISSION,"TF") 
               ^TMP($J,"FH",DATE/TIME,DFN,ADMISSION,"TF",NUMBER,"P") 
  
 Node 0 returned and "P" multiple 
  
 Special Meals: 
 -------------
 Return Array: ^TMP($J,"FH",DATE/TIME,DFN,"SM") 
  
 Node 0 returned 
  
 Guest Meals: 
 -----------
 Return Array: ^TMP($J,"FH",DATE/TIME,DFN,"GM") 
  
 Node 0 returned 
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 4884                            IA #: 4884
  FILE NUMBER: 119.6                    GLOBAL ROOT: FH(119.6,
  DATE CREATED: AUG 09, 2006            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: NUTRITION LOCATION FILE (#119.6)
  ID: FH(119.6,
GLOBAL REFERENCE: FH(119.6,D0,0)
FIELD NUMBER: 3                         FIELD NAME: TRAY SERVICE POINT
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field, if used, indicates that tray service is
 available to this ward and is provided by the indicated Service Point. Note:
 if a Dining Room is also available, then a Tray Service Point must be
 specified as Dining Room trays are prepared there. For outpatient nutrition
 locations this field indicates the tray Service Point available for the
 location.  
FIELD NUMBER: 101                       FIELD NAME: SERVICES
  LOCATION: 0;10                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains one or more of the characters T, C or
 D indicating tray service, cafeteria service, and/or dining room service is
 available.  
 GENERAL DESCRIPTION:   Nutrition Location file (#119.6) is referenced via DSS
 routine ECXUTL6.  
  STATUS: Active
KEYWORDS: NUTRITION LOCATION
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 4885                            IA #: 4885
  FILE NUMBER: 119.72                   GLOBAL ROOT: FH(119.72,
  DATE CREATED: AUG 22, 2006            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SERVICE POINT
  ID: FH(119.72,
GLOBAL REFERENCE: FH(119.72,
FIELD NUMBER: 2                         FIELD NAME: PRODUCTION FACILITY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field indicates the Production Facility responsible
 for preparing the food served by this Service Point.  
 GENERAL DESCRIPTION:   Serivce Point file  (#119.72) is referenced via
 Filemadn GET1^DIQ calls in ECXUTL6 DSS routine.  
  STATUS: Active
KEYWORDS: SERVICE POINT
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 4886                            IA #: 4886
  DATE CREATED: AUG 28, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGADDUTL
  NAME: UPDATE PATIENT ADDRESSES        ID: DGADDUTL
 GENERAL DESCRIPTION:   This API allows the user to update a patient's mailing
 or temporary address.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: UPDATE(DFN,TYPE)
 COMPONENT DESCRIPTION:   This API enables the user to update a patient's
 mailing or temporary address depending on the value of the TYPE variable. To
 maintain legacy compatibility this API will continue to accept the legacy
 variable "PERM" to update the patient's mailing address. If the TYPE variable
 equals "PERM" the user will be able to edit the fields for the patient's
 mailing address. If the TYPE variable equals "TEMP" the user will be able to
 edit the fields for the patient's temporary address.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN of the Patient file #2.  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   The value of TYPE determines which address the user
 will edit.  "PERM" for mailing address, "TEMP" for temporary address.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 4887                            IA #: 4887
  DATE CREATED: AUG 21, 2006            CUSTODIAL PACKAGE: 807
  USAGE: Private                        TYPE: SQL Table
  DBIC APPROVAL STATUS: APPROVED
  NAME: Use of STD_INSTITUTION table in PATS application
 GENERAL DESCRIPTION:   This integration agreement describes the use of the
 std_institution table and fields within the PATS application's Oracle
 database. 
  
 When the first test site goes to production with PATS, the EMC will be using
 version 11 of the SDS database.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PATS
KEYWORDS: SDS
KEYWORDS: INSTITUTION
KEYWORDS: STD_INSTITUTION
  SQL TABLE: STD_INSTITUTION
SQL COLUMN: STATIONNUMBER
 COLUMN DETAILS:   PATS does a join between the PATS report_of_contact table
 and the std_institution table, to select this field into the rollup table and
 the report tables.  
SQL COLUMN: VISN_ID
 COLUMN DETAILS:   PATS uses this field when building data for the rollup and
 for one PATS report provided for the National Program Office. PATS first does
 a JOIN between the PATS report_of_contact table and the std_institution table
 to select the institution at which a patient complaint was made. It then uses 
 the results of the first join to do a second join on the std_institution table
 to select an entry with an ID matching the visn_id field of the first entry,
 in order to get the name of the VISN.  
SQL COLUMN: VISTANAME
 COLUMN DETAILS:   PATS does a join between the PATS report_of_contact table
 and the std_institution table, to select this field into the rollup table and
 the report tables.  
SQL COLUMN: ID
 COLUMN DETAILS:   PATS has several foreign key references to the ID field on
 the std_institution table. This field is used both to do joins between the 
 PATS tables and the std_institution table to build tables used for reporting,
 and to screen data so that users see only the data for their own division.  
  DATE ACTIVATED: SEP 23, 2006

NUMBER: 4888                            IA #: 4888
  DATE CREATED: AUG 22, 2006            CUSTODIAL PACKAGE: 807
  USAGE: Private                        TYPE: SQL Table
  DBIC APPROVAL STATUS: APPROVED
  NAME: Use of STD_INSTITUTION table in PATS Data Migration
 GENERAL DESCRIPTION:   This integration agreement describes the use of the
 Standard Data Services std_institution table and fields within the PATS data
 migration application. This agreement is in force only until the PATS
 application has been rolled out nationally to all sites.  
  
 When the first test site goes to production with PATS, the EMC will be using
 version 11 of the SDS database.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PATS
KEYWORDS: SDS
KEYWORDS: INSTITUTION
KEYWORDS: STD_INSTITUTION
KEYWORDS: DATA MIGRATION
KEYWORDS: MIGRATION
  SQL TABLE: STD_INSTITUTION
SQL COLUMN: STATIONNUMBER
 COLUMN DETAILS:   The contingency option to delete all PATS data for an
 institution and the divisions within that insitution, takes the ID value for
 the computing institution as an input parameter. It does a SELECT statement on
 the STD_INSTITUTION table to get the STATIONNUMBER field for the computing 
 institution. It then selects all ID values from the STD_INSTITUTION table, 
 whose STATIONNUMBER field begins with the same 3 digit station number. The 
 procedure then deletes all records from the report_of_contact table, and all
 PATS reference tables that reference either the computing institution, or
 divisions within the computing institution.  
  
 When data is migrated from the VistA Patient Representative system into PATS,
 both parent and child station numbers from VistA data are used to look up
 entries on the std_institution table, in order to populate foreign key values
 in the PATS tables.  
SQL COLUMN: VISTANAME
 COLUMN DETAILS:   When data is migrated from the VistA Patient Representative
 system into PATS, the VISN name is passed from VistA, and is used to look up
 an entry on the std_institution table matching to the vistaname. The resulting
 ID field is used as a foreign key value on entries in the PATS 
 facility_service_or_section table.  
SQL COLUMN: ID
 COLUMN DETAILS:   PATS has several foreign key references to the ID field on
 the std_institution table. This field must be populated when the data is 
 migrated from VistA Patient Representative into the PATS tables. This field is
 also used by the contingency data deletion option, to identify which entries
 must be deleted from the PATS tables.  
  DATE ACTIVATED: SEP 23, 2006

NUMBER: 4889                            IA #: 4889
  DATE CREATED: AUG 22, 2006            CUSTODIAL PACKAGE: 807
  USAGE: Private                        TYPE: SQL Table
  DBIC APPROVAL STATUS: APPROVED
  NAME: Use of STD_RACE table in PATS Application
 GENERAL DESCRIPTION:   This integration agreement describes the use of the
 Patient Services std_race table and fields within the PATS application's
 Oracle database (distributed by Standard Data Services) 
  
 When the first test site goes to production with PATS, the EMC will be using
 version 11 of the SDS database.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PATS
KEYWORDS: SDS
KEYWORDS: RACE
KEYWORDS: STD_RACE
  SQL TABLE: STD_RACE
SQL COLUMN: ID
 COLUMN DETAILS:   A join is made between the PATS patient_race table and the
 SDS std_race table using the institution foreign key on the PATS table and the
 ID field on the std_race table. This join is made while building the data for
 rollup to Austin.  
SQL COLUMN: NAME
 COLUMN DETAILS:   PATS selects this field for inclusion in the rollup data for
 Austin VSSC reports.  
  DATE ACTIVATED: SEP 23, 2006

NUMBER: 4890                            IA #: 4890
  DATE CREATED: AUG 22, 2006            CUSTODIAL PACKAGE: 807
  USAGE: Private                        TYPE: SQL Table
  DBIC APPROVAL STATUS: APPROVED
  NAME: Use of STD_ETHNICITY table in PATS Application
 GENERAL DESCRIPTION:   This integration agreement describes the use of the
 Patient Services std_ethnicity table and fields within the PATS application's
 Oracle database. (distributed by Standard Data Services) 
  
 When the first test site goes to production with PATS, the EMC will be using
 version 11 of the SDS database.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PATS
KEYWORDS: SDS
KEYWORDS: ETHNICITY
KEYWORDS: STD_ETHNICITY
  SQL TABLE: STD_ETHNICITY
SQL COLUMN: ID
 COLUMN DETAILS:   A join is made between the PATS_patient table and the SDS
 std_ethnicity table using the institution foreign key on the PATS table and
 the ID field on the std_ethnicity table. This join is made while building the
 data for rollup to Austin.  
SQL COLUMN: NAME
 COLUMN DETAILS:   PATS selects this field for inclusion in the rollup data for
 Austin VSSC reports.  
  DATE ACTIVATED: SEP 23, 2006

NUMBER: 4891                            IA #: 4891
  DATE CREATED: AUG 22, 2006            CUSTODIAL PACKAGE: 807
  USAGE: Private                        TYPE: SQL Table
  DBIC APPROVAL STATUS: APPROVED
  NAME: Use of STD_RACE table in PATS Data Migration
 GENERAL DESCRIPTION:   This integration agreement describes the use of the
 Patient Services std_race table and fields within the PATS data migration
 application. This agreement is in force only until the PATS application has
 been rolled out nationally to all sites. (distributed by Standard Data
 Services) 
  
 When the first test site goes to production with PATS, the EMC will be using
 version 11 of the SDS database.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PATS
KEYWORDS: SDS
KEYWORDS: RACE
KEYWORDS: STD_RACE
  SQL TABLE: STD_RACE
SQL COLUMN: ID
 COLUMN DETAILS:   PATS has a foreign key reference to the ID field on the
 std_race table.  This field must be populated when the data is migrated from
 VistA Patient Representative into the PATS tables 
SQL COLUMN: HL7CODE
 COLUMN DETAILS:   When data is migrated from the VistA Patient Representative
 system into PATS, the HL7 VALUE field from the VistA RACE file (file #10) is
 used to look up entries on the std_race table, in order to populate the
 foreign key value in the PATS_patient_race.  
  DATE ACTIVATED: SEP 26, 2006

NUMBER: 4892                            IA #: 4892
  DATE CREATED: AUG 22, 2006            CUSTODIAL PACKAGE: 807
  USAGE: Private                        TYPE: SQL Table
  DBIC APPROVAL STATUS: APPROVED
  NAME: Use of STD_ETHNICITY table in PATS Data Migration
 GENERAL DESCRIPTION:   This integration agreement describes the use of the
 Patient Services std_ethnicity table and fields within the PATS data migration
 application.  This agreement is in force only until the PATS application has
 been rolled out nationally to all sites. (distributed by Standard Data
 Services) 
  
 When the first test site goes to production with PATS, the EMC will be using
 version 11 of the SDS database.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PATS
KEYWORDS: SDS
KEYWORDS: ETHNICITY
KEYWORDS: STD_ETHNICITY
  SQL TABLE: STD_ETHNICITY
SQL COLUMN: ID
 COLUMN DETAILS:   PATS has a foreign key reference to the ID field on the
 std_ethnicity table.  This field must be populated when the data is migrated
 from VistA Patient Representative into the PATS tables 
SQL COLUMN: ABBREVIATION
 COLUMN DETAILS:   When data is migrated from the VistA Patient Representative
 system into PATS, the ABBREVIATION field from the VistA ETHNICITY file (10.2)
 is used to look up entries on the std_ethnicity table, in order to populate
 the foreign key value in the PATS_patient.  
  DATE ACTIVATED: SEP 25, 2006

NUMBER: 4893                            IA #: 4893
  DATE CREATED: SEP 07, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQVI1 GRID
  REMOTE PROCEDURE: ORQQVI1 GRID
 GENERAL DESCRIPTION:   Returns vitals data for a patient to the cover sheet.  
  STATUS: Active
SUBSCRIBING PACKAGE: BAR CODE EXPANSION

NUMBER: 4894                            IA #: 4894
  DATE CREATED: AUG 25, 2006            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: FATKAAT TEST ENTRY
 GENERAL DESCRIPTION:   Integration agreement to list the components in FATKAAT
 that will be exposed for integration.  
  STATUS: Active
KEYWORDS: java
COMPONENT/ENTRY POINT: fatkaat_X.X.X.X.jar
COMPONENT/ENTRY POINT: fatkaatServer_X.X.X.X.jar
 COMPONENT DESCRIPTION:   scope: 
   servlet context in a web application that will be secured by FATKAAT 
 exposes: 
  
 1. itself as a java classpath library in the servlet context for a web 
 application.  
  
 2. 

NUMBER: 4895                            IA #: 4895
  FILE NUMBER: 408.12                   GLOBAL ROOT: DGPR(408.12
  DATE CREATED: AUG 29, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ADD PATIENT RELATION INFO FROM HEC
  ID: DGPR(408.12
 GENERAL DESCRIPTION:   
  
 The following Integration Agreement is granted to allow the Write access IVM
 makes into the Patient Relation file (408.12).  
  
 FIELD    FIELD NUMBER   NAME 
  
 .01      PATIENT (RP2'X), [0;1]                        Fileman and Direct 
                                                            global Writes 
  
 .02      RELATIONSHIP (R*P408.11'), [0;2]              Fileman and Direct 
                                                            global Writes 
  
 .03      PERSON (RVX), [0;3]                           Direct global Write 
  
 75       EFFECTIVE DATE (Multiple-408.1275), [E;0] 
           .01  EFFECTIVE DATE (RDX), [0;1]             Fileman and Direct 
                                                            global Writes 
           .02  ACTIVE (RS), [0;2]                      Direct global Write 
           .03  FILED BY IVM (S), [0;3]                 Direct global Write 
           .04  IVM TEST (P408.31'), [0;4]              Direct global Write 
  
  
  
  
 IVM is granted the following Read access into the Patient Relation file 
 (408.12): 
  
 Read access to the "B" cross reference.  
  
  
 FIELD    FIELD NUMBER   NAME 
  
 75       EFFECTIVE DATE (Multiple-408.1275), [E;0] 
           .03  FILED BY IVM (S), [0;3]                 Direct global Read 
           .04  IVM TEST (P408.31'), [0;4]              Direct global Read 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IVM
KEYWORDS: PATIENT RELATION FILE
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
 SUBSCRIBING DETAILS:   IVM is granted this access to facilitate addition of
 Patient Relation information received from HEC.  
  DATE ACTIVATED: NOV 29, 2006

NUMBER: 4896                            IA #: 4896
  FILE NUMBER: 81.1                     GLOBAL ROOT: DIC(81.1,
  DATE CREATED: APR 04, 2007            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: CPT CATEGORY FILE 81.1 'B' CROSS REFERENCE
  ID: DIC(81.1,
 GENERAL DESCRIPTION:   The "B" cross-reference for the CPT Modifier file 81.1
 needs to be extended to the maximum 63 characters to ensure uniqueness in the
 index.  This file is pointed to only by the CPT file 81 and itself.  
  
 New Set/Kill logic: 
  
    S ^DIC(81.1,"B",$E(X,1,63),DA)="" 
    K ^DIC(81.1,"B",$E(X,1,63),DA) 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CPT
KEYWORDS: CATEGORY
SUBSCRIBING PACKAGE: CPT/HCPCS CODES
  DATE ACTIVATED: APR 04, 2007

NUMBER: 4897                            IA #: 4897
  FILE NUMBER: 9.6                      GLOBAL ROOT: XPD(9.6
  DATE CREATED: SEP 05, 2006            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: MAG access top-level and BUILD COMPONENTS data
  ID: XPD(9.6
GLOBAL REFERENCE: XPD(9.6,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Contains package name or patch name.  
FIELD NUMBER: 20                        FIELD NAME: ALPHA/BETA TESTING
  LOCATION: ABPKG;1                     ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Set of codes: yes - alpha/beta testing or no alpha/beta
 testing.  
 GLOBAL DESCRIPTION:   This access is restricted to the specific fields at the
 top level of the BUILD (#9.6) file.  
GLOBAL REFERENCE: XPD(9.6,D0,'KRN',
FIELD NUMBER: 10                        FIELD NAME: ENTRIES
  LOCATION: 10;0                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   ENTRIES is a multiple of each BUILD COMPONENT being
 exported in a VI build.  
 GLOBAL DESCRIPTION:   ENTRIES is a multiple for each BUILD COMPONENT being
 exported in a VI build. There are fields under the ENTRIES multiple that will
 be returned by the software approved to use this IA.  
GLOBAL REFERENCE: XPD(9.6,D0,'KRN',D1,
FIELD NUMBER: .01                       FIELD NAME: ENTRIES
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The name of the build component being sent.  
FIELD NUMBER: .02                       FIELD NAME: FILE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The build component must exist in a specific pointed-to
 file. This field contains the VA FileMan file for this build component entry.  
FIELD NUMBER: .03                       FIELD NAME: ACTION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the action you want performed at the installing
 site on the entry of the build component you are sending for this package.  
FIELD NUMBER: .04                       FIELD NAME: CHECKSUM
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the checksum for this build
 component.  
 GLOBAL DESCRIPTION:   This ENTRIES (#9.68) multiple is a list of each record
 that is being sent for a build component. This particular IA focuses on the
 routine build component. The VI software using this IA will assume a static D1
 value of 9.8 (ROUTINE file number) to return routine specific data to the VI 
 application.  
GLOBAL REFERENCE: XPD(9.6,D0,'KRN',D1,'NM','B',
FIELD NUMBER: .01                       FIELD NAME: ENTRIES
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This global reference will allow the return of the
 specific build component entry (routines) collated.  
 GLOBAL DESCRIPTION:   This is a list of the routine(s) being sent as a build
 component.  
 GENERAL DESCRIPTION:   Imaging is reading the ALPHA/BETA TESTING field #20 to
 utilize a Version Control function that will not allow versions of Imaging
 client software to connect to the DataBase if they are no longer supported.  
  
 - If the Server Version (that will not support Client X) is in Alpha/Beta 
 status, Client X will be shown a warning message.  - If the Server Version
 (that will not support Client X) is Released, Client X will be forced to
 abort.  
  
 Update June 23rd 2022: 
 ----------------------
 This Integration Agreement (IA) has been updated to access the BUILD 
 COMPONENTS sub-file for routine components. The VistA Imaging (VI) application
 will use the $$FIND1^DIC to lookup the VI build.  
  
 VI will use the GETS^DIQ VA FileMan utility to return data specific to the
 routine BUILD COMPONENTS (#9.67).  
  STATUS: Active
KEYWORDS: alpha/beta testing
KEYWORDS: MAG BUILD COMPONENTS (KIDS)
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   VI is granted permission to read the BUILD (#9.6) and
 specific sub-files within the BUILD file for the purposes of version control.  
  DATE ACTIVATED: JUL 06, 2022

NUMBER: 4898                            IA #: 4898
  DATE CREATED: SEP 07, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQPX REMINDERS LIST
  REMOTE PROCEDURE: ORQQPX REMINDERS LIST
 GENERAL DESCRIPTION:   In support of the BCE project, Care Fusion's wCareView
 software is using ORQQPX REMINDERS LIST to obtain a list of reminders for a
 patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
SUBSCRIBING PACKAGE: RPC BROKER
 SUBSCRIBING DETAILS:   RPC ADDED 12/7/2011 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************** 
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                   
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
 ****************************************************

NUMBER: 4899                            IA #: 4899
  DATE CREATED: SEP 07, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQPXRM REMINDER DETAIL
  REMOTE PROCEDURE: ORQQPXRM REMINDER DETAIL
 GENERAL DESCRIPTION:   In support of the BCE project, CareFusion's wCareView
 software (MJCF) will be using the ORQQPXRM REMINDER DETAIL rpc to obtain
 details about clinical reminders.  This integration agreement with OR
 represents an interim solution to meet MJCF's need for reminder detail.  At
 some point in the future, Clinical Reminders will create a dedicated RPC for
 this purpose.  At that time, this agreement will be replaced with a new
 agreement for the deciated RPC.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************** 
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                   
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
 ****************************************************

NUMBER: 4900                            IA #: 4900
  DATE CREATED: SEP 11, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWCV DTLVST
  REMOTE PROCEDURE: ORWCV DTLVST
 GENERAL DESCRIPTION:   MJCF will dislpay progress note and discharge summary
 data returned by this RPC call.  
  STATUS: Active
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 4901                            IA #: 4901
  DATE CREATED: SEP 11, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWLRR GRID
  REMOTE PROCEDURE: ORWLRR GRID
 GENERAL DESCRIPTION:   Returns data for display of labs on grid controls 
  STATUS: Active
SUBSCRIBING PACKAGE: BAR CODE EXPANSION

NUMBER: 4902                            IA #: 4902
  DATE CREATED: SEP 13, 2006            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSO52EX
  NAME: OBTAIN FILLS, REFILLS, PARTIAL FILLS FROM PRESCRIPTION FILE
  ID: PSO52EX
 GENERAL DESCRIPTION:   This ICR is provided by Outpatient Pharmacy as an API
 to extract information related to original prescription fills, refills, and
 partial fills.  This API is to be used by all packages needing to retrieve
 data from the "AD", "AL", and "AM" cross references and the "STA" and "PARK" 
 nodes in the PRESCRIPTION file (#52).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EXTRACT(SDATE,EDATE,LIST)
 COMPONENT DESCRIPTION:   FORMAT: D EXTRACT^PSO52EX(SDATE,EDATE,LIST) 
VARIABLES: SDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   Start date of record retrieval [REQUIRED] 
VARIABLES: EDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   End date of record retrieval [OPTIONAL] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript name used in the ^TMP Global [REQUIRED] 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0)=Total entries found in X-refs or
 -1^NO DATA FOUND 
  
 Original Fill:  (Returned Every Time) ^TMP($J,LIST,IEN,.01) = RX # (52,.01) 
 ^TMP($J,LIST,IEN,2) = PATIENT (52,2)^NAME (2,.01) ^TMP($J,LIST,IEN,6) = DRUG
 (52,6)^GENERIC NAME (50,.01) 
  
 ^TMP($J,LIST,IEN,7) = QTY (52,7) ^TMP($J,LIST,IEN,8) = DAYS SUPPLY (52,8) 
 ^TMP($J,LIST,IEN,17) = UNIT PRICE OF DRUG (52,17) 
  
 Refills: (n = instance of a refill) ^TMP($J,LIST,IEN,"RF",0) = # OF ENTRIES 
 ^TMP($J,LIST,IEN,"RF",n,.01) = REFILL DATE (52.1,.01)^External format 
 ^TMP($J,LIST,IEN,"RF",n,1) = QTY (52.1,1) ^TMP($J,LIST,IEN,"RF",n,1.1)  = DAYS
 SUPPLY (52.1,1.1) 
  
 ^TMP($J,LIST,IEN,"RF",n,1.2) = CURRENT UNIT PRICE OF DRUG (52.1,1.2) 
  
 Partial Fills: (n = instance of a partial fill) ^TMP($J,LIST,IEN,"P",0)=# OF
 ENTRIES ^TMP($J,LIST,IEN,"P",n,.01) = PARTIAL DATE (52.2,.01)^External format 
 ^TMP($J,LIST,IEN,"P",n,.04) = QTY (52.2,.04) ^TMP($J,LIST,IEN,"P",n,.041) = 
 DAYS SUPPLY (52.2,.041) 
  
 ^TMP($J,LIST,IEN,"P",n,.042) = CURRENT UNIT PRICE OF DRUG (52.2,.042) 
  
  
 ^TMP($J,LIST,"AL",Date/Time,IEN,Fill)="" 
 ^TMP($J,LIST,"AM",Date/Time,IEN,Fill)="" 
COMPONENT/ENTRY POINT: REF(SDATE,EDATE,LIST)
 COMPONENT DESCRIPTION:   FORMAT: D REF^PSO52EX(SDATE,EDATE,LIST) 
VARIABLES: SDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   Start date of "AD" cross reference retrieval
 [REQUIRED] 
VARIABLES: EDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   End date of "AD" cross reference retrieval [OPTIONAL] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Subscript name used in the ^TMP Global [REQUIRED] 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,"AD",Date,RX,Fill)="" 
COMPONENT/ENTRY POINT: ARXREF(PSODATE,PSOIEN,PSOFILL)
 COMPONENT DESCRIPTION:   FORMAT: S X=$$ARXREF^PSO52EX(PSODATE,PSOIEN,PSOFILL) 
VARIABLES: PSODATE                      TYPE: Input
 VARIABLES DESCRIPTION:   Release date/time of prescription [REQUIRED] 
VARIABLES: PSOIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number from the PRESCRIPTION file
 (#52) [REQUIRED] 
VARIABLES: PSOFILL                      TYPE: Input
 VARIABLES DESCRIPTION:   Fill number of prescription (0 for Original Fill, 1
 for Refill #1, 2 for Refill #2, etc.) [REQUIRED] 
VARIABLES: $$ARXREF                     TYPE: Output
 VARIABLES DESCRIPTION:   0 (zero) = Data does not exist in the "AR" cross
 reference, indicating the fill was not dispensed from the Consolidated Mail
 Outpatient Pharmacy (CMOP).  
  
 1 (one) = Data does exist in the "AR" cross reference, indicating the fill was
 dispensed from the CMOP.  
COMPONENT/ENTRY POINT: PARK(ORIEN)
 COMPONENT DESCRIPTION:   FORMAT: S X=$$PARK^PSO52EX(ORIEN) 
VARIABLES: ORIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   ORIEN Internal entry number from the ORDER FILE
 (#100) [REQUIRED] 
VARIABLES: PARK                         TYPE: Output
 VARIABLES DESCRIPTION:   0 (zero) = Data in the first piece of the "STA" node
 is not equal to 0 (zero) or there isn't data in the first piece of the "PARK"
 node. This indicates that the prescription does not have the emulated status
 of "PARK".  
  
 1 (one) = Data in the first piece "STA" node is equal to 0 (zero) and there is
 data in the first piece of the "PARK" node. This indicates that the
 prescription has the emulated status of "PARK".  
COMPONENT/ENTRY POINT: SUSP(ORIEN)
 COMPONENT DESCRIPTION:   FORMAT: S X=$$SUSP^PSO52EX(ORIEN) 
VARIABLES: ORIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   ORIEN Internal entry number from the ORDER FILE
 (#100) [REQUIRED] 
VARIABLES: SUSP                         TYPE: Output
 VARIABLES DESCRIPTION:   0 (zero) = Data in the first piece of the "STA" node
 is not equal to 5 (Suspended). This indicates that the prescription is not
 suspended.  
  
 1 (one) = Data in the first piece of the "STA" node is equal to 5 (Suspended).
 This indicates that the prescription is suspended.  
  DATE ACTIVATED: NOV 15, 2021

NUMBER: 4903                            IA #: 4903
  DATE CREATED: JAN 06, 2011            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPFAPIH
  NAME: PATIENT RECORD FLAG DATA RETRIEVAL
  ID: DGPFAPIH
 GENERAL DESCRIPTION:   These API's provide a means to retrieve detailed
 Patient Record Flag information by patient and patient record flag, and, to
 retrieve a list of patients with a specific assigned patient record flag
 during a specified date range.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PATIENT RECORD FLAGS
COMPONENT/ENTRY POINT: GETINF
 COMPONENT DESCRIPTION:   This function will return detailed information from
 the Patient Record Flag files for the specified patient and PRF flag.  A date
 range for active PR Flags is optional.  Data array output example: 
  
 DGARR("ASSIGNDT") - Date of initial assignment. 
        i.e. 3110131.093248^Jan 31, 2011@09:32:48) DGARR("CATEGORY") - National
 or Local flag category. 
        i.e. II (LOCAL)^II (LOCAL) DGARR("FLAG") - Variable pointer to
 Local/National flag files and flag name. 
        i.e. 1;DGPF(26.11,^HIGH RISK FOR SUICIDE DGARR("FLAGTYPE") - Type of
 flag usage.  
        i.e. 1^BEHAVIORAL DGARR("HIST",n,"ACTION") - Type of action for history
 entry 
        i.e. 1^NEW ASSIGNMENT DGARR("HIST",n,"APPRVBY") - Person approving the
 flag assignment 
        i.e. 112345^PERSON,STEVE DGARR("HIST",1,"COMMENT",1,0) - Comment for
 record assignment action 
        i.e "New record flag assignment." DGARR("HIST",n,"DATETIME") -
 Date/Time of Action 
        i.e. 3110131.093248^JAN 31, 2011@09:32:48 DGARR("HIST",n,"TIULINK") -
 Pointer to the TIU Document file (#8925) 
        i.e. "^" DGARR("NARR",n,0) - Describes the purpose and instructions for
 the application of the flag. 
        i.e. "TEST ENTRY" DGARR("ORIGSITE") - Site that initially assigned this
 flag (Relevant to National flags only) 
        i.e. 500^DNS DGARR("OWNER") - Site which currently "Owns" this flag
 (Relevant to National flags only) 
         i.e. 500^DNS DGARR("REVIEWDT") - Date for next review of record flag
 assignment 
        i.e. 3110501^MAY 01, 2011 DGARR("TIUTITLE") - Pointer to the TIU
 Document Definition file (#8925.1) 
        i.e. 1309^PATIENT RECORD FLAG CATEGORY II - RESEARCH STUDY 
VARIABLES: DGDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the DFN (IEN) for the patient in the PATIENT
 File (#2).  This is a required variable.  
VARIABLES: DGPRF                        TYPE: Input
 VARIABLES DESCRIPTION:   Variable pointer to either the PRF LOCAL FLAG File
 (#26.11) or to the PRF NATIONAL FLAG file (#26.15).  This is a required
 variable.  
  
 For National Flags:  IEN;DGPF(26.15, 
    For Local Flags:  IEN;DGPF(26.11, 
VARIABLES: DGSTART                      TYPE: Input
 VARIABLES DESCRIPTION:   Start date for when to begin search for active PRF
 flags.  This date must be in FM format, i.e. 3110106.  This variable is
 optional, if null, searches will begin with the earliest assigned entry in the
 PRF ASSIGNMENT HISTORY file (#26.14) 
VARIABLES: DGEND                        TYPE: Input
 VARIABLES DESCRIPTION:   End date for the search for active PRF entries.  This
 date must be in FM format, i.e. 3110107.  This variable is optional, if null
 or not passed in, all entries to the end of the PRF ASSIGNMENT HISTORY file
 (#26.14) will be searched.  
VARIABLES: DGARR                        TYPE: Both
 VARIABLES DESCRIPTION:   This variable contains the array name for the return
 data.  This is optional.  If an array name is not specified, the return data
 is returned in local array "DGPFAPI1".  
VARIABLES: DGRSLT                       TYPE: Output
 VARIABLES DESCRIPTION:   Return value from the API call.  Returns "1" if the
 API was successful in returning PRF data, returns "0" if the API was
 unsuccessful in returning PRF data.  
COMPONENT/ENTRY POINT: GETLST
 COMPONENT DESCRIPTION:   This function call returns a list of patients with a
 specified Patient Record Flag assigned for a specified date range.  
  
   DGARR(DFN,n) - Patient Name^VPID^Date of initial assignment^National or 
 Local flag category^flag name 
  
 Example: 
    DGARR(9999955648,0)="EASPATIENT,ONE A^5000000295V790537^3100201.103713^II
 (LOCAL)^HIGH RISK FOR SUICIDE" 
VARIABLES: DGPRF                        TYPE: Input
 VARIABLES DESCRIPTION:   Variable pointer to either the PRF LOCAL FLAG File
 (#26.11) or the PRF NATIONAL FLAG File (#26.15). This variable is required.  
  
    National:  IEN;DGPF(26.15, 
       Local:  IEN;DGPF(26.11, 
VARIABLES: DGSTART                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the start date to begin searching for
 patients with the assigned Patient Record Flag.  This date must be in FM
 format, i.e. 3100110. This variable is optional.  
VARIABLES: DGEND                        TYPE: Input
 VARIABLES DESCRIPTION:   This is end date for the search range for patients
 with the assigned Patient Record Flag.  This date must be in FM format, i.e.
 3100112. This variable is optional.  
VARIABLES: DGARR                        TYPE: Both
 VARIABLES DESCRIPTION:   This variable contains the array name where the
 returned patient information will be placed.  This is optional, if an array
 name is not specified, the data will be returned in a TMP Global,
 ^TMP("PRFLST").  
VARIABLES: DGRSLT                       TYPE: Output
 VARIABLES DESCRIPTION:   This variable returns a count of the patients placed
 in the return list.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Scheduling requires Patient Record Flag information as
 part of a new missed appointment report supporting the High Risk Mental Health 
 Initiative.  This report needs to be able to determine which patients  missing
 a recent appointment have a specified Patient Record Flag assigned.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Retrieval of High Risk Mental Health Patient Flag
 information.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   ADDED 7/19/2011 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 3/11/20 to access $$GETINF^DGPFAPIH and
 $$GETLST^DGPFAPIH from DBIA #4903.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   Added 2/18/21 to support Suicide High Risk Patient
 Enhancements Project Phase 2 (SHRPE 2.0), PRCA*4.5*373.  
  DATE ACTIVATED: JUN 07, 2011

NUMBER: 4904                            IA #: 4904
  DATE CREATED: SEP 27, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWPT BYWARD
  REMOTE PROCEDURE: ORWPT BYWARD
 GENERAL DESCRIPTION:   MJCF will use this RPC in the wCareView application in
 support of the BCE project.  
  STATUS: Active
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
 SUBSCRIBING DETAILS:   MJCF is using the patient DFN and name values and
 ignoring the room-bed value.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************** 
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                   
 ICR #4904 provides access to the ORWPT BYWARD RPC and the RPC is currently
 found in the HMP UI CONTEXT option.  ICR #6272 provides access to the API. 
 However ICR #4904 is referenced in HMP routines HMPCAC and HMPDDL.  The API is
 also called in routine HMPROS8 but ICR #4904 is not noted in the routine. 
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
 ****************************************************

NUMBER: 4905                            IA #: 4905
  DATE CREATED: SEP 27, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWPT DIEDON
  REMOTE PROCEDURE: ORWPT DIEDON
 GENERAL DESCRIPTION:   MJCF will use this RPC in the wCareView application in
 support of the BCE project.  
  STATUS: Active
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
 SUBSCRIBING DETAILS:   MJCF will use the date of death for a patient as
 returned by ORWPT DIEDON.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 4906                            IA #: 4906
  DATE CREATED: SEP 27, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWPT FULLSSN
  REMOTE PROCEDURE: ORWPT FULLSSN
 GENERAL DESCRIPTION:   MJCF will use this RPC in the wCareView application in
 support of the BCE project.  
  STATUS: Active
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
 SUBSCRIBING DETAILS:   MJCF will use the list of patients as returned by this
 RPC, ignoring the values of DOB and full SSN.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   The ORWPT FULLSSN 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: 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.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 11/14/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace.
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes 
 required RPCs. ORWPT FULLSSN is one of the Remote Procedures included in the
 CRMS VAHC Option.  The Remote Application uses Data Access Services/National
 Health Information Network (DAS/NHIN) as the middleware to interface with
 VistA.  
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   Added 08/19/2025, effective with NHIN*1*26, this RPC is
 defined in the NHIN/DAS context option "NHIN DAS CC", which is defined in the
 REMOTE APPLICATION file entry name "NHIN DAS CC". The RPC is called to provide 
 read only data to the calling system. NHIN will call this RPC to facilitate
 the CTO office processing of additional community provider data using the
 existing DAS account, remote application and context option. This is specific
 to the DAS VistA service account which processes Community Care data to VistA.
 The use case is a community provider completes an exam and faxes the results
 into a VAMC. These results are stored in a file share and a process that the
 CTO office is building picks up these results need to be written back to VistA
 and the originating Consult closed out.  

NUMBER: 4907                            IA #: 4907
  DATE CREATED: SEP 27, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWPT SELECT
  REMOTE PROCEDURE: ORWPT SELECT
 GENERAL DESCRIPTION:   MJCF will use this RPC in the wCareView application in
 support of the BCE project.  
  
 The following is the current production return array for this RPC 
  
  SELECT(REC,DFN) ; Selects patient & returns key information 
   1    2   3   4    5      6    7    8       9       10      11  12 
   NAME^SEX^DOB^SSN^LOCIEN^LOCNM^RMBD^CWAD^SENSITIVE^ADMITTED^CONV^SC^ 
  
   13  14  15  16  17 
   SC%^ICN^AGE^TS^TSSVC 
  
 The RPC will be updated when CPRS GUI v33SWD, OR*3.0*608 is released in early
 2024.  
  
   1    2   3   4    5      6    7    8       9       10      11   12 
   NAME^SEX^DOB^SSN^LOCIEN^LOCNM^RMBD^CWAD^SENSITIVE^ADMITTED^CONV^SC^ 
  
   13  14  15  16  17    18    19 
   SC%^ ICN^AGE^TS^TSSVC^SIGI^PRONOUN 
  STATUS: Active
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
 SUBSCRIBING DETAILS:   MJCF will use the following fields returned by ORWPT
 SELECT - ?? represents field that will not be used.  
  
 NAME^SEX^DOB^SSN ^LOCIEN^LOCNM^RMBD ^??^SENSITIVE^ADMITTED ^??^??^SC%^??
 ^AGE^?? 
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
 SUBSCRIBING DETAILS:   Added as a subscriber for JLV 2.6 release 
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 10/02/23, effective with patch CDSP*1*0 CDSP is
 developing a Precision Oncology workflow to automatically ingest genetic test
 results into VistA and VistA imaging. The workflow needs to identify patients 
 based on demographic data present in test results. This RPC is used to fetch
 patient information to validate that the correct patient has been selected.  
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/31/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS
 namespace.The CRMS VAHC Remote Application includes the CRMS VAHC Option,
 which includes required RPCs.  ORWPT SELECT is one of the Remote Procedures
 included in the CRMS VAHC Option.  The Remote Application uses Data Access 
 Services/National Health Information Network (DAS/NHIN) as the middleware to
 interface with VistA.  
SUBSCRIBING PACKAGE: VETEXT
 SUBSCRIBING DETAILS:   Added 2/14/25, effective with VTEX *1*0 patch. This RPC
 will be defined in the VTEXRPCS context option, to select the patient to
 support the After Visit Summary (AVS), a minor of VEText.  

NUMBER: 4908                            IA #: 4908
  DATE CREATED: SEP 27, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWU PATCH
  REMOTE PROCEDURE: ORWU PATCH
 GENERAL DESCRIPTION:   MJCF will use this RPC in the wCareView application in
 support of the BCE project.  
  STATUS: Active
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
 SUBSCRIBING DETAILS:   MJCF will use this RPC to determine if a given patch
 has been installed.  

NUMBER: 4909                            IA #: 4909
  DATE CREATED: SEP 27, 2006            CUSTODIAL PACKAGE: 1
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DILOCKTM
 GENERAL DESCRIPTION:   Access to the ^DD("DILOCKTM") global and the setting of
 the DILOCKTM variable.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   Kernel wants to be sure that the variable DILOCKTM is
 set for all application to use for Lock timeouts.  Kernel need access to the
 ^DD("DILOCKTM") global to set the DILOCKTM variable.  

NUMBER: 4910                            IA #: 4910
  DATE CREATED: SEP 29, 2006            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOBAI
  NAME: DBIA4910                        ID: PSOBAI
 GENERAL DESCRIPTION:   This agreement provides CMOP an entry point to
 determine if the patient has a known bad address and no active temporary
 address.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BAD ADDRESS
KEYWORDS: PSOBAI
COMPONENT/ENTRY POINT: $$CHKRX(PSORX)
 COMPONENT DESCRIPTION:   This entry point will be used by CMOP to determine
 whether a prescription fill should be sent to CMOP or rejected because of a
 known bad address and no active temporary address.  
VARIABLES: PSORX                        TYPE: Input
 VARIABLES DESCRIPTION:   PRESCRIPTION file (#52) IEN 
VARIABLES: $$CHKRX                      TYPE: Output
 VARIABLES DESCRIPTION:   Return is a string in the format N^N where the first
 N is a numeric BAD ADDRESS indicator for the patient's permanent address
 (could be null if no bad address). The second N, if present, is a 1 if the
 temporary address is active.  
SUBSCRIBING PACKAGE: CMOP

NUMBER: 4911                            IA #: 4911
  DATE CREATED: SEP 29, 2006            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSTAX
  NAME: TAXONOMY UTILITIES              ID: XUSTAX
 GENERAL DESCRIPTION:   APIs to facilitate retrieval of Taxonomy Code
 information from VistA NEW PERSON file (#200) and the INSTITUTION file (#4).  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Taxonomy
KEYWORDS: XUSTAX
KEYWORDS: $$TAXIND
KEYWORDS: $$TAXORG
COMPONENT/ENTRY POINT: $$TAXIND(XUIEN)
 COMPONENT DESCRIPTION:   Extrinsic function to retrieve the taxonomy code for
 a given record in the 
  NEW PERSON file (#200).  
  
VARIABLES: XUIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the record in file #200. 
 Required.  No default.  
  
VARIABLES: $$TAXIND                     TYPE: Output
 VARIABLES DESCRIPTION:   If taxonomy exists returns string:
 'TaxonomyX12Code^TaxonomyIEN'.  Else returns string: '^'.  
  
COMPONENT/ENTRY POINT: $$TAXORG(XUIEN)
 COMPONENT DESCRIPTION:   Extrinsic function to retrieve the taxonomy code for
 a given record in the INSTITUTION file (#4).  
  
VARIABLES: XUIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the record in file #4. 
 Required.  No default.  
  
VARIABLES: $$TAXORG                     TYPE: Output
 VARIABLES DESCRIPTION:   If taxonomy exists returns string:
 'TaxonomyX12Code^TaxonomyIEN'.  Else returns string: '^'.  
  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   The Virtual Patient Record (VPR) application is working
 on patch VPR*1*4 in support of two of its client app's, JLV and VLER. They
 have requested that VPR add information about a provider's specialty area to
 the VPR data extract rpc, so the purpose of this ICR is to request permission
 to subscribe to two Kernel-owned ICR's: 
  
 4911       $$TAXIND^XUSTAX 4984       Person Class (#8932.1) 
  
 VPR will first call $$TAXIND^XUSTAX to get the provider's current Person Class
 ien and the corresponding X12 code; using the ien, VPR will read the Provider
 Type (.01), Classification (1), and Area of Specialization (2) fields from the
 Person Class file #8932.  

NUMBER: 4912                            IA #: 4912
  DATE CREATED: OCT 05, 2006            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEXTRAN
  NAME: LEXICON CONCEPT DATA FOR CODE   ID: LEXTRAN
 GENERAL DESCRIPTION:   This API will return an array of data for a given code,
 code source, optional date, and optional return array name.  The data returned
 will include: 
       code 
       hierarchy or subset (if available) 
       version (if available) 
       legacy code (if available) 
       code status 
       fully specified name (if available) 
       preferred term 
       any applicable synonyms 
  
 If any of the data in the passed parameters data is incorrect or 
 unrecognizable, the API will return an error message indicating the nature of 
 the error. If no date is specified, then the date will default to the current 
 system date.  This API was developed specifically for the SNOMED CT code
 system in support of the LDSI project, but is applicable to any code system.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: $$CODE
KEYWORDS: LEXTRAN
COMPONENT/ENTRY POINT: $$CODE(CODE,SRC,VDT,ARRAY,IENS,ID,INC)
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a code of a classification system that is
 stored in the Lexicon.  Classification systems include SNOMED CT, ICD, CPT,
 HCPCS, etc.  
  
VARIABLES: SRC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the mnemonic for a code system (mandatory).
 The allowable code system mnemonics are those that exist in the "B" index of
 the coding systems file (757.03) This is code system source abbreviation
 Lexicon. 
VARIABLES: VDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the effective date; the default if no date is
 specified is the current system date (optional).  
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of the output array. The default, if
 no array name is specified, is 'LEX' (optional) The format of the output is as
 follows: 
         Output 
         
           if call finds an active code for the source 
             "1^LEXCODE" 
             LEX     -   an array containing information about the code 
             LEX(0)  -   a five piece string: 
                         1. code 
                         2. hierarchy 
                         3. version 
                         4. legacy code 
                         5. code status 
             LEX("F")    fully specified name 
             LEX("P")    preferred term 
             LEX("S",n)  synonyms (n is the nth synonym) 
             
           if call cannot find specified code on file 
             "-2^"_LEXSCNM_" code "_LEXCODE_" not on file" 
             where LEXSCNM is the source name 
                   LEXCODE is the code 
                         
           if call finds an inactive code for the source 
             "-4^"_LEXSCNM_" code "_LEXCODE_" not active for "_LEXVDT 
             LEX    - an array containing information about the code 
             LEX(0) -  a five piece string: 
                       1. code 
                       2. hierarchy 
                       3. version 
                       4. legacy code 
                       5. code status 
             
           otherwise 
             "-1^error text" 
         
           example of LEX array: 
             LEX(0)="67922002^Substance^20050701^T-C2500^1" 
             LEX("F")="Serum (Substance)" 
             LEX("P")="Serum" 
  
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   Include expression IENs in output array (optional) 
     1 return IENS (2nd piece) 
     0 do not return IENS (default) 
  
VARIABLES: ID                           TYPE: Input
 VARIABLES DESCRIPTION:   Designation Identifiers (optional) 
     1 return Designation IDs (3rd piece) 
     0 do not return Designation IDs (default) 
  
VARIABLES: INC                          TYPE: Input
 VARIABLES DESCRIPTION:   Include Deactivated Terms (optional) 
     1 return Deactivated Terms 
     0 do not return Deactivated Terms (default) 
  

NUMBER: 4913                            IA #: 4913
  DATE CREATED: OCT 05, 2006            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEXTRAN
  NAME: LEXICON CONCEPT DATA FOR TEXT   ID: LEXTRAN
 GENERAL DESCRIPTION:   This API will return an array of data for a given text,
 optional code source, optional date, optional subset, and optional return
 array name.  The API will display a pick list based on the parameters passed
 and allow a user to select an item from the list. The API will then return the
 array for the item selected.  The data returned will include: 
       code 
       hierarchy or subset (if available) 
       version (if available) 
       legacy code (if available) 
       code status 
       fully specified name (if available) 
       preferred term 
       any applicable synonyms 
  
 If any of the data in the passed parameters data is incorrect or 
 unrecognizable, the API will return an error message indicating the nature of 
 the error. If no date is specified, then the date will default to the current 
 system date.  This API was developed specifically for the SNOMED CT code
 system in support of the LDSI project, but is applicable to any code system.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$TEXT(TEXT,DATE,SUBSET,SOURCE,ARRAY)
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the search text string (mandatory).  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the effective date (optional); the default,
 if no date is specified, is the current system date.  
VARIABLES: SUBSET                       TYPE: Input
 VARIABLES DESCRIPTION:   This is any code system subset mnemonic (optional).
 The allowable subset mnemonics are those that exist in the "AA" index of the
 subset definitions file (757.2).  
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the mnemonic for a code system (mandatory).
 The allowable code system mnemonics are those that exist in the "B" index of
 the coding systems file (757. 03).  
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of the output array. The default if
 no array name is specified is 'LEX' (optional) The format of the output is as
 follows: 
         Output 
  
           if call is finds an active code for the source 
             "1^LEXCODE" 
             LEX     -   an array containing information about the code 
             LEX(0)  -   a five piece string: 
                         1. code 
                         2. hierarchy 
                         3. version 
                         4. legacy code 
                         5. code status 
             LEX("F")    fully specified name 
             LEX("P")    preferred term 
             LEX("S",n)  synonyms (n is the nth synonym) 
  
           if call cannot find specified code on file 
             "-2^"_LEXSCNM_" code "_LEXCODE_" not on file" 
             "-2^"_LEXSCNM_" code "_LEXCODE_" not on file" 
             where LEXSCNM is the source name 
                   LEXCODE is the code 
  
           if call finds an inactive code for the source 
             "-4^"_LEXSCNM_" code "_LEXCODE_" not active for "_LEXVDT 
             LEX    - an array containing information about the code 
             LEX(0) -  a five piece string: 
                       1. code 
                       2. hierarchy 
                       3. version 
                       4. legacy code 
                       5. code status 
  
           otherwise 
             "-1^error text" 
  
           example of LEX array: 
             LEX(0)="67922002^Substance^20050701^T-C2500^1" 
             LEX("F")="Serum (Substance)" 
             LEX("P")="Serum" 
  

NUMBER: 4914                            IA #: 4914
  DATE CREATED: OCT 05, 2006            CUSTODIAL PACKAGE: LEXICON UTILITY
  CUSTODIAL ISC: Salt Lake City         USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: LEXTRAN                      NAME: LEXICON VALIDATE CODE FOR SOURCE
  ID: LEXTRAN
 GENERAL DESCRIPTION:   This API will return an array for a given text and code
 system indicating whether the text is valid for the specified code system. The
 data array returned will include the following: 
     An indicator of whether the text is valid for the code system 
     The code in the code system to which the text,if valid for code system, 
       belongs.  If any of the passed parameters are incorrect or
 unrecognizable, the API will return an error message indicating the nature of
 the error.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$TXT4CS(TEXT,SOURCE)
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the search text string (mandatory).  
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the mnemonic for a code system (mandatory).
 The allowable code system mnemonics are those that exist in the "B" index of
 the coding systems file (757. 03). 
VARIABLES:                              TYPE: Output
 VARIABLES DESCRIPTION:   This API returns the following output: 
  
        1^code 
           or 
        -1^error message 

NUMBER: 4915                            IA #: 4915
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870
  DATE CREATED: OCT 11, 2006            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Access to HL Logical Link (#870) file
  ID: HLCS(870
GLOBAL REFERENCE: HLCS(870,'B'
FIELD NUMBER: .01                       FIELD NAME: NODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: HLCS(870,IEN,0
FIELD NUMBER: 14                        FIELD NAME: SHUTDOWN LLP ?
  LOCATION: 0;15                        ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Person Services accesses the 0th node for the value in
 the Shutdown LLP (#14) field.  Fileman used to update the value in this field. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4916                            IA #: 4916
  FILE NUMBER: 773                      GLOBAL ROOT: HLMA(
  DATE CREATED: OCT 11, 2006            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: HL7 Message Administration (#773) file access
  ID: HLMA(
GLOBAL REFERENCE: HLMA(773,
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME ENTERED
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: MESSAGE ID
  LOCATION: 0;2                         ACCESS: Read w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4917                            IA #: 4917
  FILE NUMBER: 772                      GLOBAL ROOT: HL(772
  DATE CREATED: OCT 11, 2006            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HL MESSAGE TEXT (#772) file access
  ID: HL(772
GLOBAL REFERENCE: HL(772,IEN,'IN'
FIELD NUMBER: 200                       FIELD NAME: MESSAGE TEXT
  LOCATION: IN;0                        ACCESS: Read w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4918                            IA #: 4918
  FILE NUMBER: 771                      GLOBAL ROOT: HL(771
  DATE CREATED: OCT 11, 2006            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: HL7 Application Parameter (#771) file access
  ID: HL(771
GLOBAL REFERENCE: HL(771
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: FACILITY NAME
  LOCATION: 0;3                         ACCESS: Write w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SURGERY
 SUBSCRIBING DETAILS:   SQWM would like to update the HL7 Application
 Parameters associated with the SQWM HL7 interfaces. We need to make sure that
 the Facility Name field is populated with the correct Station ID of the VistA
 system to support accurate routing of SQWM HL7 messages through the SQWM
 Information Gateway in Austin.  The post install routine will identify the
 sites Station Number using $$SITE^VASITE and will populate the FACILITY NAME
 field #3 with the Station Number. 

NUMBER: 4919                            IA #: 4919
  FILE NUMBER: 869.3                    GLOBAL ROOT: HLCS(869.3
  DATE CREATED: OCT 11, 2006            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Communication Server Parameter (#869.3) file access
  ID: HLCS(869.3
GLOBAL REFERENCE: HLCS(869.3,IEN,0
FIELD NUMBER: .03                       FIELD NAME: DEFAULT PROCESSING ID
  LOCATION: 0;3                         ACCESS: Read w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4920                            IA #: 4920
  FILE NUMBER: 115.01                   GLOBAL ROOT: FHPT(
  DATE CREATED: OCT 11, 2006            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Controlled Subscription        TYPE: File
  NAME: NUTRITION PERSON file           ID: FHPT(
GLOBAL REFERENCE: FHPT(D0,A
FIELD NUMBER: 9                         FIELD NAME: ISOLATION/PRECAUTION
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: OE/RR ISOLATION ORDER
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: FHPT(D0,A,D1,TF
FIELD NUMBER: .01                       FIELD NAME: TUBEFEEDING
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: FHPT(D0,A,D1,TF,D2,P
FIELD NUMBER: .01                       FIELD NAME: TF PRODUCT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: FHPT(D0,S
FIELD NUMBER: 1                         FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: FHPT('AIS'
GLOBAL REFERENCE: FHPT('B'
 GENERAL DESCRIPTION:   The Spinal Cord package would like to request direct
 access to the following fields of the NUTRITION PERSON file (#115) for
 reporting purposes: 
  
 ^FHPT(D0,"A",D1,0) 
  
 9     ISOLATION/PRECAUTION        0;10      Direct Global Read       
  
 10    OE/RR ISOLATION ORDER       0;13      Direct Global Read 
  
 ^FHPT(D0,"A",D1,"TF",D2,0) 
  
 .01   TUBEFEEDING                 0;1       Direct Global Read & w/Fileman 
  
 ^FHPT(D0,"A",D1,"TF",D2,"P",D3,0) 
  
 .01   TF PRODUCT                  0;1       Direct Global Read & w/Fileman 
  
 ^FHPT(D0,"S",D1,0) 
  
 1     STATUS                      0;2       Direct Global Read & w/Fileman 
  
 11/23/21 - VO ICR Team modified to AIS and B x-ref, and COMPREHENSIVE CARE 
 COORDINATION (C3) as a subscriber 
  STATUS: Other                         DURATION: Till Otherwise Agreed
KEYWORDS: NUTRITION PERSON
KEYWORDS: NUTRITION AND FOOD SERVICE
KEYWORDS: FHPT
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   Added 11/23/21, effective with DSSV*1.1 DSS Class 3
 product Document Only. Added B and AIS cross-reference look-up to ICR.  

NUMBER: 4921                            IA #: 4921
  DATE CREATED: OCT 11, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFCSB
  NAME: VAFCSB APIS                     ID: VAFCSB
 GENERAL DESCRIPTION:   These APIs are used to include the Primary View
 Criteria to the MPI for use in scoring the validity of the update.  
  STATUS: Active
COMPONENT/ENTRY POINT: PV2
 COMPONENT DESCRIPTION:   S PV2=$$PV2^VAFCSB This entry point will pass back
 the PV2 Health Level Seven segment containing the date the next scheduled
 appointment for the patient, the last admission date for the patient and the
 last registration date for the patient.   DFN is assumed to exist as the
 internal entry number of the patient in the PATIENT file (#2).  If the patient
 doesn't have any of this data, null is returned.  
COMPONENT/ENTRY POINT: PHARA
 COMPONENT DESCRIPTION:   $$PHARA^VAFCSB() This entry point will pass back the
 OBX Health Level Seven segment indicating if this patient has any active
 prescriptions. DFN is assumed to exist as the internal entry number of the
 patient in the PATIENT file (#2).  If the patient does not have an active
 prescriptions null is returned.  
COMPONENT/ENTRY POINT: LABE
 COMPONENT DESCRIPTION:   $$LABE^VAFCSB() This entry point will pass back the
 OBX Health Level Seven segment with the last lab test date for this patient. 
 DFN is assumed to exist as the internal entry number of the patient in the
 PATIENT file (#2).  If the patient does not have a last lab test, null is
 returned.  
COMPONENT/ENTRY POINT: RADE
 COMPONENT DESCRIPTION:   $$RADE^VAFCSB() This entry point will pass back the
 OBX Health Level Seven segment with the last radiology test date for this
 patient.  DFN is assumed to exist as the internal entry number of the patient
 in the PATIENT file (#2).  If the patient does not have a last radiology test,
 null is returned.  
COMPONENT/ENTRY POINT: PV1
 COMPONENT DESCRIPTION:   S PV1=$$PV1^VAFCSB() This entry point will pass back
 the PV1 Health Level Seven segment containing the date the patient was
 admitted if they are currently admitted at this facility. DFN is assumed to
 exist as the internal entry number of the patient in the PATIENT file (#2). 
 If the patient is not currently admitted null is returned.  
COMPONENT/ENTRY POINT: PD1
 COMPONENT DESCRIPTION:   $$PD1^VAFCSB This entry point will pass back the PD1
 Health Level Seven segment containing no data.  Originally the PD1 segment
 would have contained the Coordinating Master of Record.  This is being
 removed.  
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK

NUMBER: 4922                            IA #: 4922
  DATE CREATED: OCT 23, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORHLESC
  NAME: ORDER HL7 MESSAGE ESCAPE API    ID: ORHLESC
 GENERAL DESCRIPTION:   This DBIA describes the API that OE/RR has created to
 escape and unescape HL7 messages that are sent back and forth between CPRS and
 it's ancillary packages.  
  STATUS: Active
KEYWORDS: HL7
KEYWORDS: ESCAPE
KEYWORDS: ORHLESC
COMPONENT/ENTRY POINT: ESC
 COMPONENT DESCRIPTION:   This entry point removes characters defined in DELIM
 from the string STRING and replaces them with an escape sequence.  
  
 If DELIM is not passed to $$ESC, it will default to the standard HL7 encoding
 characters "~|\&^".  
                 
         ~  Component separator converted to \S\ 
         |  Repetition separator converted to \R\ 
         \  Escape character converted to \E\ 
         &  Sub-Component converted to \T\ 
         ^  Field separator converted to  \F\ 
VARIABLES: STRING                       TYPE: Input
VARIABLES: DELIM                        TYPE: Input
VARIABLES: $$ESC                        TYPE: Output
COMPONENT/ENTRY POINT: UNESC
 COMPONENT DESCRIPTION:   This entry point replaces the escape sequences in
 STRING with the proper escaped charater from DELIM.  See entry point ESC of
 ORHLESC for details on defaults for DELIM and mapping of escaped characters to
 escape sequenses.  
VARIABLES: STRING                       TYPE: Input
VARIABLES: DELIM                        TYPE: Input
VARIABLES: $$UNESC                      TYPE: Output

NUMBER: 4923                            IA #: 4923
  FILE NUMBER: 200                      GLOBAL ROOT: DD(200
  DATE CREATED: OCT 23, 2006            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Global DD sets to New Person (#200) file
  ID: DD(200
GLOBAL REFERENCE: DD(200
FIELD NUMBER: 0th node                  ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 3 node                    ACCESS: Direct Global Write & w/Fileman
FIELD NUMBER: 'DT' node                 ACCESS: Direct Global Write & w/Fileman
 GENERAL DESCRIPTION:   Person Services is setting the following DD nodes for
 the VPID (#9000) field in the New Person (#200) file in a post init routine: 
  
 ^DD(200,9000,0)="VPID^F^^VPID;1^K:$L(X)>29!($L(X)<23) X" 
 ^DD(200,9000,3)="Answer must be 23-29 characters in length." 
 ^DD(200,9000,"DT")=DT 
  STATUS: Active                        DURATION: Till Otherwise Agreed

NUMBER: 4924                            IA #: 4924
  DATE CREATED: OCT 24, 2006
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIULC1
  NAME: Calls to routine TIULC1         ID: TIULC1
 GENERAL DESCRIPTION:   Administratively closure of a consult 
  STATUS: Active
COMPONENT/ENTRY POINT: $$POSTSIGN
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the TIU note created.  
VARIABLES: TIUTYPE                      TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the CONSULT object in
 the TIU DOCUMENT DEFINITION file (8925.1).  
VARIABLES: XECUTE                       TYPE: Input
 VARIABLES DESCRIPTION:   This has the post signature method for the CONSULT
 object.  
COMPONENT/ENTRY POINT: $$DOCCLASS
VARIABLES: TIUTYP                       TYPE: Input
 VARIABLES DESCRIPTION:   The type of TIU document.  
VARIABLES: $$DOCCLASS                   TYPE: Output
 VARIABLES DESCRIPTION:   The patient document class for the given document.  
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   Updated 2/5/26, effective with patch MAG*3.0*362 Added
 Component: DOCCLASS 

NUMBER: 4925                            IA #: 4925
  GLOBAL ROOT: KMPTMP                   DATE CREATED: NOV 28, 2006
  CUSTODIAL PACKAGE: CAPACITY MANAGEMENT TOOLS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DIRECT READ TO KMPTMP(
  ID: KMPTMP
GLOBAL REFERENCE: KMPTMP("KMPD-CPRS"
 GLOBAL DESCRIPTION:   ^KMPTMP("KMPD-CPRS") 
 GENERAL DESCRIPTION:   The value of ^KMPTMP("KMPD-CPRS") indicates whether the
 coversheet collection is currently running (value=1) or stopped (value=0).  
  
 The value of ^KMPTMP("KMPD-CPRS") is set in SST+11^KMPDSS. 
  
 The subscribing package is allowed a direct read of the global 
 ^KMPTMP("KMPD-CPRS") in order to determine the state of coversheet collection. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CAPACITY PLANNING
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: RPC BROKER
 SUBSCRIBING DETAILS:   added 12/7/2011 

NUMBER: 4926                            IA #: 4926
  DATE CREATED: DEC 04, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWPS COVER
  REMOTE PROCEDURE: ORWPS COVER         STATUS: Active
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
 SUBSCRIBING DETAILS:   The wCareView app will use the following fields
 returned from the RPC call: ID;Med Type^Name^??^Status 
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   The medication reconciliation tool uses this API to
 retrieve all medications for a patient.  
  DATE ACTIVATED: APR 30, 2015

NUMBER: 4927                            IA #: 4927
  DATE CREATED: DEC 04, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWPS DETAIL
  REMOTE PROCEDURE: ORWPS DETAIL
 GENERAL DESCRIPTION:   MJCF will use this RPC in the wCareView application in
 support of the BCE project.  
  STATUS: Active
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
 SUBSCRIBING DETAILS:   The wCareView app is expecting to use all data returned
 from this RPC call.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   CPRS approved adding Dental as a subscriber for Dental
 Record Manager to this ICR on 8/11/2009 to document existing references. 
 However the update was not made to the ICR until 2/9/18.  

NUMBER: 4928                            IA #: 4928
  DATE CREATED: NOV 24, 2006
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSS55MIS
  NAME: DATA RETRIEVAL FROM FILE 55     ID: PSS55MIS
 GENERAL DESCRIPTION:   This DBIA is provided by Pharmacy Data Management (PSS)
 as an API to do data retrieval from File 55 using various methods.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: STATUS(PSSFILE,PSSFIELD,LIST)
 COMPONENT DESCRIPTION:   This API simulates fileman DIC calls and is to be
 used by packages seeking access to the STATUS (#28) field of the UNIT DOSE
 (55.06) subfile, STATUS (#100) field of the IV (55.01) subfile, or STATUS (#5)
 field of the NON-VA MEDS (55.05) subfile from the PHARMACY PATIENT (#55) file. 
  
 FORMAT: D STATUS^PSS55MIS(PSSFILE,PSSFIELD,LIST) 
VARIABLES: PSSFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   Subfile number from the PHARMACY PATIENT file (#55)
 [required] 
VARIABLES: PSSFIELD                     TYPE: Input
 VARIABLES DESCRIPTION:   Field number from the specified file associated with
 the value in PSSFILE 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Array name defined by the calling application
 [required] 
VARIABLES: PSSDIY                       TYPE: Output
 VARIABLES DESCRIPTION:   PSODIY will return null if the value for PSOFILE is
 valid (it will return -1 if conditions were not met) 
  
 See VA FileMan Programmer Manual for DIC output definition 
COMPONENT/ENTRY POINT: CLINIC(PSSORD,PSSDFN,PSSMED)
 COMPONENT DESCRIPTION:   Returns a clinic from the HOSPITAL LOCATION file
 (#44) based on a provided order number and patient DFN.  
VARIABLES: PSSORD                       TYPE: Input
 VARIABLES DESCRIPTION:   Order Number from either the IV sub-file (#55.01) or
 UNIT DOSE sub-file (#55.06) of the PHARMACY PATIENT file (#55) [required] 
VARIABLES: PSSDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN from the PATIENT file (#2) [required] 
VARIABLES: PSSMED                       TYPE: Input
 VARIABLES DESCRIPTION:   "I" to return entries from the IV sub-file (#55.01)
 or "U" for entries from the UNIT DOSE sub-file (#55.06) [required] 
VARIABLES: $$CLINIC                     TYPE: Output
 VARIABLES DESCRIPTION:   $$CLINIC = clinic number^clinic name WHERE: clinic
 number = IEN from the HOSPITAL LOCATION file (#44) clinic name = NAME  field
 (# .01) from the HOSPTIAL LOCATION file (#44) 

NUMBER: 4929                            IA #: 4929
  FILE NUMBER: 40.7                     GLOBAL ROOT: DIC
  DATE CREATED: NOV 07, 2006            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CLINIC STOP file
  ID: DIC
GLOBAL REFERENCE: DIC(40.7
FIELD NUMBER: B                         FIELD NAME: B cross-reference
  LOCATION: n/a                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Spinal Cord package would like to request direct
 global access to the B cross-reference of the CLINIC STOP file (#40.7) for
 reporting purposes 
  STATUS: Active
KEYWORDS: Clinic Stop
KEYWORDS: DIC(40.7
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION

NUMBER: 4930                            IA #: 4930
  FILE NUMBER: 409.43                   GLOBAL ROOT: SDD
  DATE CREATED: NOV 28, 2006            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: OUTPATIENT DIAGNOSIS file
  ID: SDD
GLOBAL REFERENCE: SDD(409.43,AO
FIELD NUMBER: .01                       FIELD NAME: DIAGNOSIS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Spinal Cord package would like to request direct
 global access to the following field of the OUTPATIENT DIAGNOSIS file
 (#409.43) for reporting purposes: 
  
 ^SDD(409.43,"AO",D0,D1) 
  
 .01   DIAGNOSIS     0;1      direct global read 
  STATUS: Active
KEYWORDS: OUTPATIENT DIAGNOSIS
KEYWORDS: SCHEDULING
KEYWORDS: SDD(409.43
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION

NUMBER: 4931                            IA #: 4931
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100,
  DATE CREATED: NOV 28, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: NATURE OF ORDER
  ID: OR(100,
GLOBAL REFERENCE: OR(100,DA(1),8,DA,0)
FIELD NUMBER: 12                        FIELD NAME: NATURE OF ORDER
  LOCATION: 0;12                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This specifies the nature of the order or how it
 originated.  
 GENERAL DESCRIPTION:   Subscribing package has a permission to access the
 (#100) file as described in this DBIA.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORDER
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 4932                            IA #: 4932
  FILE NUMBER: 408.31                   GLOBAL ROOT: DGMT(408.31
  DATE CREATED: NOV 29, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ANNUAL MEANS TEST FILE
  ID: DGMT(408.31
 GENERAL DESCRIPTION:   
  
 The following Integration Agreement is granted to allow the access IVM makes
 into the Annual Means Test file (408.31).  
  
  
 FIELD    FIELD NUMBER   NAME 
  
 .23      SOURCE OF INCOME TEST (RP408.34'), [0;23]     Direct global Read 
  
  
  
 IVM is granted the following access to the Annual Means Test file (408.31): 
  
  
 FIELD    FIELD NUMBER   NAME 
  
 .01      DATE OF TEST (RDX), [0;1]                     Direct global Read 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IVM
KEYWORDS: ANNUAL MEANS TEST FILE
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
 SUBSCRIBING DETAILS:   IVM is granted this access to support additions to the
 Patient Relation file as received from HEC.  
  DATE ACTIVATED: NOV 29, 2006

NUMBER: 4933                            IA #: 4933
  DATE CREATED: NOV 29, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGMTAUD
  NAME: ACCESS REGISTRATION MEANS TEST CODE
  ID: DGMTAUD
 GENERAL DESCRIPTION:   
  
 The following Integration Agreement is granted to allow the access IVM makes
 to Registration Means Test code.  
  
 SET^DGMTAUD is invoked by IVM when a relationship entry is made in the Patient
 Relation file (408.12).  SET^DGMTAUD makes an entry in the Means Test Changes
 file (408.41) to record the change to the Patient Relation file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IVM
KEYWORDS: DGMTAUD
COMPONENT/ENTRY POINT: SET
 COMPONENT DESCRIPTION:   SET updates the Means Test Changes file (#408.41).  
VARIABLES: DGMTYPT                      TYPE: Input
 VARIABLES DESCRIPTION:   Type of Test entered (Means Test) 
VARIABLES: DGMTACT                      TYPE: Input
 VARIABLES DESCRIPTION:   Type of Action from Means Test.  
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
 SUBSCRIBING DETAILS:   IVM is granted this access to support additions to the
 Patient Relation file as received from HEC.  
  DATE ACTIVATED: NOV 29, 2006

NUMBER: 4934                            IA #: 4934
  FILE NUMBER: 408.34                   GLOBAL ROOT: DG(408.34
  DATE CREATED: NOV 29, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SOURCE OF INCOME TEST FILE
  ID: DG(408.34
 GENERAL DESCRIPTION:   
  
 IVM is granted the following access to the Source Of Income Test file 
 (408.34): 
  
  
 FIELD   FIELD NUMBER  NAME 
  
 .01     NAME (RF), [0;1]                              Direct global Read 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IVM
KEYWORDS: SOURCE OF INCOME TEST FILE
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
 SUBSCRIBING DETAILS:   IVM is granted this access to support additions to the
 Patient Relation as received from HEC.  This access will be used to provide
 better explanations of the changes HEC additions make.  
  DATE ACTIVATED: NOV 29, 2006

NUMBER: 4935                            IA #: 4935
  FILE NUMBER: 8930                     GLOBAL ROOT: USR(8930
  DATE CREATED: DEC 04, 2006
  CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION
  USAGE: Private                        TYPE: File
  NAME: Use of AD xref in file 8930     ID: USR(8930
GLOBAL REFERENCE: USR(8930,'AD',
 GLOBAL DESCRIPTION:   The AD cross-reference stores the parent class of the
 class identified in the subscript.  
 GENERAL DESCRIPTION:   CPRS requests the ability to do a direct global read of
 the AD cross-reference of file 8930.  The OR ALLERGY ENTERED IN ERROR
 parameter has identified CLASS as one of the entity levels that can be set for
 this parameter.  
  
 Because a user can belong to multiple classes and multiple classes can have
 values in this parameter, the AD cross-reference is used to determine the
 "parent" class of the class that is set in the parameter.  The child class is
 used to identify whether a user can or cannot mark an allergy as entered in
 error.  As a result, all higher level (parent) classes are removed from
 consideration when determining if the user can take the action.  If more than
 one child class has a value then those will be compared against each other and
 any "yes" value will allow the user to mark an allergy as entered in error.  
  
 This is a temporary agreement until The Authorization/Subsciption utility is
 able to write an API to provide the above funtionality in a standardized way.  
  STATUS: Expired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 2008
KEYWORDS: USER CLASS
KEYWORDS: PARENT
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 4936                            IA #: 4936
  FILE NUMBER: 101.43                   GLOBAL ROOT: ORD(101.43,D0
  DATE CREATED: DEC 14, 2006
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: UPDATE ORDERABLE ITEM FILE
  ID: ORD(101.43,D0
GLOBAL REFERENCE: ORD(101.43,DO,PS)
FIELD NUMBER: 50.8                      FIELD NAME: ROUTE
  LOCATION: piece 8                     ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   This is a one-time usage only to enable Pharmacy Data
 Management to update the CPRS Orderable Item file with the default medication
 route information.  
  STATUS: Active                        DURATION: Next Version
  EXPIRATION DATE: DEC 31, 2007
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS

NUMBER: 4937                            IA #: 4937
  FILE NUMBER: 10                       GLOBAL ROOT: DIC
  DATE CREATED: JAN 10, 2011            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4937
  ID: DIC
GLOBAL REFERENCE: DIC(10,B
 GENERAL DESCRIPTION:   Read access of the Race file using the 'B'
 cross-reference.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
  DATE ACTIVATED: AUG 02, 2011

NUMBER: 4938                            IA #: 4938
  FILE NUMBER: 2                        GLOBAL ROOT: DPT
  CUSTODIAL PACKAGE: REGISTRATION       USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PATIENT file                    ID: DPT
GLOBAL REFERENCE: DPT
FIELD NUMBER: 57.4                      FIELD NAME: SPINAL CORD INJURY
  LOCATION: 57.4;4                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 991.01                    FIELD NAME: INTEGRATION CONTROL NUMBER
  LOCATION: MPI;1                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: AICN
 GLOBAL DESCRIPTION:   Direct global access to the "AICN" cross-reference to
 identify DFN based on a given ICN.  
 GENERAL DESCRIPTION:   The Spinal Cord package would like to request direct
 global access to the following fields of the PATIENT file (#2) for reporting
 purposes: 
  
 ^DPT(D0,57) 
  
    57.4     SPINAL CORD INJURY     57;4 
  
 ^DPT(D0,"MPI") 
  
    991.01   INTEGRATION CONTROL NUMBER     MPI;1 
  
 ^DPT("AICN",D0,D1)  -  Cross-reference to lookup DFN based on ICN 
  STATUS: Active
KEYWORDS: PATIENT
KEYWORDS: SPINAL CORD INJURY
KEYWORDS: ICN
KEYWORDS: INTEGRATION CONTROL NUMBER
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  DATE ACTIVATED: FEB 01, 2007

NUMBER: 4939                            IA #: 4939
  FILE NUMBER: 355.93                   GLOBAL ROOT: IBA(355.93
  DATE CREATED: MAR 18, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: AVOID NPI DUPLICATES            ID: IBA(355.93
GLOBAL REFERENCE: IBA(355.93,'NPI42',NPI NUMBER, D0,
 GLOBAL DESCRIPTION:   Uses "NPI42" x-ref to get IEN (D0) for a given NPI
 NUMBER.  
  
GLOBAL REFERENCE: IBA(355.93,D0,'NPISTATUS',D1,
FIELD NUMBER: .02                       FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Check status for a given NPI NUMBER. If status is '0'
 (inactive) or '1' (active) then NPI is a duplicate. Any other status is OK.  
  
 GLOBAL DESCRIPTION:   
  
GLOBAL REFERENCE: IBA(355.93,D0,'NPISTATUS','C',NPI NUMBER,D1,
 GLOBAL DESCRIPTION:   Uses "C" x-ref in NPISTATUS node to get IEN (D1) for a
 given NPI NUMBER within the 'NPISTATUS' multiple for this IEN (D0).  
  
GLOBAL REFERENCE: IBA(355.93,D0,0
FIELD NUMBER: .02                       FIELD NAME: PROVIDER TYPE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   If an NPI is currently used by an entry in file 355.93,
 Kernel calls $$GET1^DIQ to return the value of the PROVIDER TYPE field (#.02)
 for that entry. This information is presented as part of the error or warning 
 message when a user attempts to enter the same NPI to an entry in the 
 INSTITUTION file (#4) or the NEW PERSON file (#200).  
 GENERAL DESCRIPTION:   When entering/editing an NPI to an entry in the NEW
 PERSON file (#200), the INSTITUTION file (#4) or the IB NON/OTHER VA BILLING
 PROVIDER file (#355.93), Kernel needs to check if the NPI is already used by
 an entry in any of the three files. If the NPI is already used, Kernel will
 issue either an error or a warning message, depending on which file is
 currently being edited.  
  
 An NPI used by an entry in file 4 cannot be used in an entry in either of the
 other files regardless of whether the NPI is 'active' or 'inactive'.  An NPI
 can be used in a single entry in both file 200 and file 355.93 at the same
 time, but a warning is issued in that case.  
  STATUS: Other                         DURATION: Till Otherwise Agreed
KEYWORDS: NPI
KEYWORDS: DUPLICATE
KEYWORDS: KERNEL PARAMETERS
SUBSCRIBING PACKAGE: KERNEL
  DATE ACTIVATED: FEB 01, 2007
REMINDER: MAR 20, 2008

NUMBER: 4940                            IA #: 4940
  FILE NUMBER: 10.2                     GLOBAL ROOT: DIC
  DATE CREATED: JAN 10, 2011            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4940
  ID: DIC
GLOBAL REFERENCE: DIC(10.2,B
 GENERAL DESCRIPTION:   Read access of the Ethnicity file using the "B"
 cross-reference.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
  DATE ACTIVATED: AUG 02, 2011

NUMBER: 4941                            IA #: 4941
  FILE NUMBER: 408.32                   GLOBAL ROOT: DG(408.32
  DATE CREATED: DEC 11, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MEANS TEST STATUS file
  ID: DG(408.32
GLOBAL REFERENCE: DG(408.32,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Spinal Cord package would like to request direct
 global access to the following field of the MEANS TEST STATUS File for
 reporting purposes: 
  
 ^DG(408.32,D0,0) 
  
 .01   NAME         0;1       Direct global read 
  STATUS: Active
KEYWORDS: MEANS TEST STATUS
KEYWORDS: DG(408.32
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  DATE ACTIVATED: MAR 05, 2007

NUMBER: 4942                            IA #: 4942
  FILE NUMBER: 405                      GLOBAL ROOT: DGPM
  DATE CREATED: DEC 11, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PATIENT MOVEMENT file
  ID: DGPM
GLOBAL REFERENCE: DGPM(APRD,D0,D1,D2
FIELD NUMBER: n/a                       ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   APRD Cross-reference 
GLOBAL REFERENCE: DGPM(B,D0,D1
FIELD NUMBER: n/a                       ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   B Cross-reference 
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: .05                       FIELD NAME: TRANSFER FACILITY
  LOCATION: 0;5                         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: .08                       FIELD NAME: PRIMARY PHYSICIAN
  LOCATION: 0;8                         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: .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
 GENERAL DESCRIPTION:   The Spinal Cord package would like to request Direct
 Global access to the following fields of the Patient Movement file (#405) for
 reporting purposes: 
  
 ^DGPM("APRD",D0)  -  APRD Cross-reference 
  
 ^DGPM("B",D0,D1)  -  B Cross-reference 
  
 ^DGPM(D0,0) 
  
 .01   DATE/TIME                    0;1    Direct global read .02   TRANSACTION 
                 0;2    Direct global read .03   PATIENT                     
 0;3    Direct global read .05   TRANSFER FACILITY            0;5    Direct
 global read .06   WARD LOCATION                0;6    Direct global read .07  
 ROOM-BED                     0;7    Direct global read .08   PRIMARY PHYSICIAN 
           0;8    Direct global read .09   FACILITY TREATING SPECIALTY  0;9   
 Direct global read .14   ADMISSION/CHECK-IN MOVEMENT  0;14   Direct global
 read .19   ATTENDING PHYSICIAN          0;19   Direct global read .24  
 RELATED PHYSICAL MOVEMENT    0;24   Direct global read 
  STATUS: Active
KEYWORDS: PATIENT MOVEMENT
KEYWORDS: DGPM
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4943                            IA #: 4943
  FILE NUMBER: 391.91                   GLOBAL ROOT: DGCN(391.91
  DATE CREATED: DEC 11, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TREATING FACILITY LIST
  ID: DGCN(391.91
GLOBAL REFERENCE: DGCN(391.91,B,D0,D1
FIELD NUMBER: n/a                       ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   B Cross-reference 
GLOBAL REFERENCE: DGCN(391.91,D0,0
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
 GENERAL DESCRIPTION:   The Spinal Cord Package would like to request direct
 global access to the following fields of the Treating Facility List file
 (#391.91) for reporting purposes: 
  
 ^DGCN(391.91,"B",D0,D1)  -  B Cross-reference 
  
 ^DGCN(391.91,D0,0) 
  
 .02   INSTITUTION            0;2     Direct global read .03   DATE LAST
 TREATED      0;3     Direct global read 
  STATUS: Active
KEYWORDS: TREATING FACILITY LIST
KEYWORDS: DGCN(391.91
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4944                            IA #: 4944
  FILE NUMBER: 45.1                     GLOBAL ROOT: DIC(45.1
  DATE CREATED: DEC 11, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SOURCE OF ADMISSION
  ID: DIC(45.1
GLOBAL REFERENCE: DIC(45.1,D0,0
FIELD NUMBER: .01                       FIELD NAME: PTF CODE
  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:   The Spinal Cord package would like to request direct
 global access to the following fields of the Source Of Admission file (#45.1)
 for reporting purposes: 
  
 ^DIC(45.1,D0,0) 
  
 .01    PTF CODE        0;1    Direct global read 2      NAME            0;2   
 Direct global read 
  STATUS: Active
KEYWORDS: SOURCE OF ADMISSION
KEYWORDS: DIC(45.1
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4945                            IA #: 4945
  FILE NUMBER: 45                       GLOBAL ROOT: DGPT
  DATE CREATED: DEC 11, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PTF file
  ID: DGPT
GLOBAL REFERENCE: DGPT(AF,D0,D1
FIELD NUMBER: n/a                       ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   AF Cross-reference 
GLOBAL REFERENCE: DGPT(D0,0
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: FACILITY
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: FEE BASIS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPT(D0,70
FIELD NUMBER: 75                        FIELD NAME: PLACE OF DISPOSITION
  LOCATION: 70;6                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 76.1                      FIELD NAME: RECEIVING FACILITY
  LOCATION: 70;12                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPT(D0,101
FIELD NUMBER: 20                        FIELD NAME: SOURCE OF ADMISSION
  LOCATION: 101;1                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGPT(D0,AP,D1
FIELD NUMBER: .01                       FIELD NAME: PROCEDURE 1
  LOCATION: 401P;1                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PROCEDURE 2
  LOCATION: 401P;2                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: PROCEDURE 3
  LOCATION: 401P;3                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: PROCEDURE 4
  LOCATION: 401P;4                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: PROCEDURE 5
  LOCATION: 401P;5                      ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Spinal Cord package would like to request direct
 global access to the following fields of the PTF file (#45) for reporting
 purposes: 
  
 ^DGPT("AF",D0,D1)  -  AF Cross-reference 
  
 ^DGPT(D0,0) 
  
 .01   PATIENT              0;1    Direct global access 3     FACILITY          
   0;3    Direct global access 4     FEE BASIS            0;4    Direct global
 access 
  
 ^DGPT(D0,70) 
  
 75    PLACE OF DISPOSITION 70;6   Direct global access 76.1  RECEIVING
 FACILITY   70;12  Direct global access 
  
 ^DGPT(D0,101) 
  
 20    SOURCE OF ADMISSION  101;1  Direct global access 
  
 ^DGPT(D0,"AP",D1) 
  
 .01   PROCEDURE 1          401P;1 Direct global access .02   PROCEDURE 2       
   401P;2 Direct global access .03   PROCEDURE 3          401P;3 Direct global
 access .04   PROCEDURE 4          401P;4 Direct global access .05   PROCEDURE
 5          401P;5 Direct global access 
  STATUS: Active
KEYWORDS: PTF
KEYWORDS: DGPT
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4946                            IA #: 4946
  FILE NUMBER: 42.4                     GLOBAL ROOT: DIC(42.4
  DATE CREATED: DEC 12, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SPECIALTY file
  ID: DIC(42.4
GLOBAL REFERENCE: DIC(42.4,B,D0
FIELD NUMBER: n/a                       ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   B Cross-reference 
 GENERAL DESCRIPTION:   The Spinal Cord package would like to request direct
 access to the B cross-reference of the Specialty file (#42.4) for reporting
 purposes.  
  
 ^DIC(42.4,"B",D0)  -  B Cross-reference 
  STATUS: Active
KEYWORDS: SPECIALTY
KEYWORDS: DIC(42.4
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4947                            IA #: 4947
  FILE NUMBER: 27.11                    GLOBAL ROOT: DGEN(27.11
  DATE CREATED: DEC 12, 2006            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PATIENT ENROLLMENT
  ID: DGEN(27.11
GLOBAL REFERENCE: DGEN(27.11,C,D0,D1
FIELD NUMBER: n/a                       ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   C Cross-reference 
GLOBAL REFERENCE: DGEN(27.11,D0,0
FIELD NUMBER: .07                       FIELD NAME: ENROLLMENT PRIORITY
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .12                       FIELD NAME: ENROLLMENT SUBGROUP
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGEN(27.11,D0,E
FIELD NUMBER: 50.14                     FIELD NAME: MEANS TEST STATUS
  LOCATION: E;14                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Spinal Cord package would like to request direct
 global access to the following fields of the Patient Enrollment file (#27.11)
 for reporting purposes: 
  
 ^DGEN(27.11,"C",D0,D1)  -  C Cross-reference 
  
 ^DGEN(27.11,D0,0) 
  
 .07    ENROLLMENT PRIORITY          0;7   Direct global read .12    ENROLLMENT
 SUBGROUP          0;12  Direct global read 
  
 ^DGEN(27.11,D0,"E") 
  
 50.14  MEANS TEST STATUS            E;14  Direct global read 
  STATUS: Active
KEYWORDS: PATIENT ENROLLMENT
KEYWORDS: DGEN(27.11
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  DATE ACTIVATED: MAR 05, 2007

NUMBER: 4948                            IA #: 4948
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: APR 23, 2007            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Person Service enumeration
  ID: VA(200
GLOBAL REFERENCE: VA(200,IEN,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ACCESS CODE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9.2                       FIELD NAME: TERMINATION DATE
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: VA(200,IEN,.1)
FIELD NUMBER: 11                        FIELD NAME: VERIFY CODE
  LOCATION: .1;2                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: VA(200,IEN,1,0)
FIELD NUMBER: 4                         FIELD NAME: SEX
  LOCATION: 1;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: DOB
  LOCATION: 1;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: SSN
  LOCATION: 1;9                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   VA(200,"SSN" cross reference used to identify person on
 local VistA system.  
GLOBAL REFERENCE: VA(200,IEN,201)
FIELD NUMBER: 201                       FIELD NAME: PRIMARY MENU OPTION
  LOCATION: 201;1                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: VA(200,IEN,450)
FIELD NUMBER: 450                       FIELD NAME: PAID EMPLOYEE
  LOCATION: 450;1                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: VA(200,IEN,'VER')
FIELD NUMBER: 9001                      FIELD NAME: ADR Sequence Number
  LOCATION: VER;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9002                      FIELD NAME: PSIM UPDATE USER
  LOCATION: VER;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9003                      FIELD NAME: PSIM UPDATE DT
  LOCATION: VER;3                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,IEN,'VPID')
FIELD NUMBER: 9000                      FIELD NAME: VPID
  LOCATION: VPID;1                      ACCESS: Direct Global R/W & w/Fileman
 GLOBAL DESCRIPTION:   VA(200,"AVPID" cross reference used to identify record
 on the local VistA system by VPID.  
GLOBAL REFERENCE: VA(200,IEN,'USC1')
FIELD NUMBER: .01                       FIELD NAME: PERSON CLASS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: Effective Date
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: Expiration Date
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   If Person Class (#200.05) multiple is defined for
 record, include Practitioner category in HL7 message.  
GLOBAL REFERENCE: VA(200,IEN,8910)
FIELD NUMBER: .01                       FIELD NAME: VISITED FROM
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: SITE NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DUZ AT HOME SITE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   If Visited From (#200.06) multiple is defined for a
 record, include Visitor category in HL7 message.  
GLOBAL REFERENCE: VA(200,'AXUPS',IEN)
 GLOBAL DESCRIPTION:   New style index to build the "AXUPS" cross reference
 when a record is added to the New Person file or fields are edited.  
  
 Process Pending Index option loops through cross reference to identify those
 records that have been added or updated.  Cross reference is killed after HL7
 message is generated.  
  
 Enumeration options will kill this cross reference for a record after a B01 or
 B02 message is generated.  If New Person file record does not meet enumeration
 requirements, cross reference is killed.  
  
 Index is built when the following fields are updated: 
  
 Name (#.01) Access Code (#2) Sex (#4) DOB (#5) SSN (#9) Termination Date
 (#9.2) Verify Code (#11) Primary Menu Option (#201) PAID Employee (#450) 
 Person Class (#8932.1) 
GLOBAL REFERENCE: VA(200,0)
 GLOBAL DESCRIPTION:   Reference to the 4th piece of VA(200,0) to capture
 number of entries in New Person (#200) file.  
 GENERAL DESCRIPTION:   
  XU*8.0*331 is being deployed in conjunction with the ongoing transition 
  to HealtheVet VistA. Interdependencies include current and future 
  HealtheVet applications and services.  
   
  Health Systems Design & Development Common Services Person Service 
  has been tasked with standing up an Administrative Data Repository 
  (ADR) that will store identification data.  Each person will be 
  enumerated with a unique identifier called a VPID (VA Person ID).  The 
  first person data to be enumerated - prior to migrating the data to 
  the ADR will be entries in the NEW PERSON file (#200).  
  STATUS: Withdrawn

NUMBER: 4949                            IA #: 4949
  DATE CREATED: JAN 25, 2007            CUSTODIAL PACKAGE: 807
  USAGE: Private                        TYPE: SQL Table
  NAME: ACCESS TO STANDARDIZED INSTITUTION FILE
 GENERAL DESCRIPTION:   The VPFS package accesses the SDS tables in a View.  
  STATUS: Pending
KEYWORDS: SDS
KEYWORDS: INSTITUTION
  SQL TABLE: STD_INSTITUTION
SQL COLUMN: ID
SQL COLUMN: NAME
SQL COLUMN: STATIONNUMBER
SQL COLUMN: VISTANAME
SQL COLUMN: STREETCOUNTRY_ID
SQL COLUMN: STREETADDRESSLINE1
SQL COLUMN: STREETADDRESSLINE2
SQL COLUMN: STREETADDRESSLINE3
SQL COLUMN: STREETCITY
SQL COLUMN: STREETPOSTALCODE
SUBSCRIBING PACKAGE: INTEGRATED PATIENT FUNDS
 SUBSCRIBING DETAILS:   The VPFS package will create the INSTITUTION view that
 references the following SDS tables / fields: 
  
 1) STD_INSTITUTION Table: Fields: id, name, stationnumber, vistaname, 
    streetcountry_id, streetaddressline1, streetaddressline2, 
    streetaddressline3, streetcity, streetpostalcode 2) STD_STATE Table:
 Fields: postalname 3) STD_COUNTRY Table: Fields: shortname 4) STD_FACILITYTYPE
 Table: Fields: code 
  
 This view is used to provide a consolidated view of institution data from the
 SDS tables (as detailed above) and the VPFS_INSTITUTION table, which contains
 institution-specific data used by VPFS.  
  
 The SELECT privilege is granted to the VPFS user for the STD_INSTITUTION, 
 STD_STATE, STD_COUNTRY, and STD_FACILITYTYPE tables.  

NUMBER: 4950                            IA #: 4950
  CUSTODIAL PACKAGE: 807                USAGE: Private
  TYPE: SQL Table                       NAME: DBIA4950
  STATUS: Pending

NUMBER: 4951                            IA #: 4951
  DATE CREATED: DEC 14, 2006
  CUSTODIAL PACKAGE: INTEGRATED PATIENT FUNDS
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: VPFS consumption of PSL API
 GENERAL DESCRIPTION:   The VPFS package consumes the Common Service PSL.  
  STATUS: Active
KEYWORDS: PSL
KEYWORDS: API
SUBSCRIBING PACKAGE: INTEGRATED PATIENT FUNDS
 SUBSCRIBING DETAILS:   The VPFS package consumes the PSL Common Service. The
 objects and methods used by VPFS, are detailed below: 
  
 IUserBean: 
         setSecurityType(String) 
         setForwardToPage(String) 
         setUserCredential(String) 
         setSiteIdentifier(String) 
         setDivisionIdentifier(String) 
         setSiteOfInterest(String) 
  
 UserBean: 
         UserBean() 
  
 PLSessionMgr: 
         getPatientLookupBean() 
  
 PatientLookupBean: 
         getICN() 
  
  
 The following files are included in the project: 
  
 plu\calendar.js plu\datePopup.js plu\help plu\images plu\jsp plu\plumaster.js 
 plu\xbDebug.js plu\xbDOM.js plu\xbLibrary.js plu\xbStyle-css.js 
 plu\xbStyle-nn4.js plu\xbStyle-not-supported.js plu\xbStyle.js 
 plu\help\acknowledging_status_notifications.htm 
 plu\help\appendix_a_patient_identifiers_list.htm 
 plu\help\appendix_b_status_notification_alert_icons.htm 
 plu\help\cshdat_robohelp.htm plu\help\cshdat_webhelp.htm plu\help\ehelp.xml 
 plu\help\ehlpdhtm.js plu\help\field_types.htm plu\help\image1.gif 
 plu\help\ms_help.css plu\help\online_help_tutorial.htm 
 plu\help\patient_lookup_filters.htm plu\help\patient_lookup_filters_text0.htm 
 plu\help\pluhelp.html plu\help\pspl (web-based) online help.log 
 plu\help\pspl_(web-based)_online_help_123004.htm 
 plu\help\pspl_(web-based)_online_help_123004_csh.htm 
 plu\help\pspl_(web-based)_online_help_123004_rhc.htm 
 plu\help\pspl_user_manual_(web-based)_files plu\help\purpose.htm 
 plu\help\robohhre.lng plu\help\search_by_clinic.htm 
 plu\help\search_by_inpatient_provider.htm plu\help\search_by_specialty.htm 
 plu\help\search_by_ward.htm plu\help\search_for_a_patient_record.htm 
 plu\help\search_for_a_user_record.htm 
 plu\help\shortcut_keys_quick_reference_table.htm plu\help\webhelp.cab 
 plu\help\webhelp.jar plu\help\what_s_new.htm plu\help\whcshdata.htm 
 plu\help\whcsh_home.htm plu\help\whdata plu\help\whd_dpns.htm 
 plu\help\whd_hide0.gif plu\help\whd_hide1.gif plu\help\whd_hide2.gif 
 plu\help\whd_home.htm plu\help\whd_next0.gif plu\help\whd_next1.gif 
 plu\help\whd_next2.gif plu\help\whd_nvp10.htm plu\help\whd_nvp20.htm 
 plu\help\whd_prev0.gif plu\help\whd_prev1.gif plu\help\whd_prev2.gif 
 plu\help\whd_show0.gif plu\help\whd_show1.gif plu\help\whd_show2.gif 
 plu\help\whd_sync0.gif plu\help\whd_sync1.gif plu\help\whd_sync2.gif 
 plu\help\whd_tab0.gif plu\help\whd_tab1.gif plu\help\whd_tab2.gif 
 plu\help\whd_tab3.gif plu\help\whd_tab4.gif plu\help\whd_tab5.gif 
 plu\help\whd_tab6.gif plu\help\whd_tab7.gif plu\help\whd_tab8.gif 
 plu\help\whd_tabs.htm plu\help\whd_toc1.gif plu\help\whd_toc2.gif 
 plu\help\whd_toc3.gif plu\help\whd_toc4.gif plu\help\whd_topic.xml 
 plu\help\whd_wbsh0.gif plu\help\whd_wbsh1.gif plu\help\whd_wbsh2.gif 
 plu\help\whfbody.htm plu\help\whfdhtml.htm plu\help\whfform.htm 
 plu\help\whfhost.js plu\help\whform.js plu\help\whframes.js 
 plu\help\whgbody.htm plu\help\whgdata plu\help\whgdef.htm 
 plu\help\whgdhtml.htm plu\help\whghost.js plu\help\whhost.js 
 plu\help\whibody.htm plu\help\whidhtml.htm plu\help\whiform.htm 
 plu\help\whihost.js plu\help\whlang.js plu\help\whmozemu.js plu\help\whmsg.js 
 plu\help\whnjs.htm plu\help\whphost.js plu\help\whproj.htm plu\help\whproj.js 
 plu\help\whproj.xml plu\help\whproxy.js plu\help\whres.xml 
 plu\help\whskin_blank.htm plu\help\whskin_homepage.htm 
 plu\help\whskin_info.htm plu\help\whskin_pickup.htm plu\help\whskin_tw.htm 
 plu\help\whstart.js plu\help\whstub.js plu\help\whtdhtml.htm 
 plu\help\whthost.js plu\help\whtopic.js plu\help\whutils.js plu\help\whver.js 
 plu\help\whxdata plu\help\window_navigation_and_commands.htm 
 plu\help\pspl_user_manual_(web-based)_files\image005.gif 
 plu\help\pspl_user_manual_(web-based)_files\image011.jpg 
 plu\help\pspl_user_manual_(web-based)_files\image013.jpg 
 plu\help\pspl_user_manual_(web-based)_files\image015.jpg 
 plu\help\pspl_user_manual_(web-based)_files\image017.jpg 
 plu\help\pspl_user_manual_(web-based)_files\image019.gif 
 plu\help\pspl_user_manual_(web-based)_files\image021.gif 
 plu\help\pspl_user_manual_(web-based)_files\image025.jpg 
 plu\help\pspl_user_manual_(web-based)_files\image027.jpg 
 plu\help\pspl_user_manual_(web-based)_files\image032.gif 
 plu\help\pspl_user_manual_(web-based)_files\image033.gif 
 plu\help\pspl_user_manual_(web-based)_files\image035.jpg 
 plu\help\pspl_user_manual_(web-based)_files\image054.gif 
 plu\help\pspl_user_manual_(web-based)_files\image056.gif 
 plu\help\pspl_user_manual_(web-based)_files\image058.gif 
 plu\help\pspl_user_manual_(web-based)_files\image060.gif 
 plu\help\pspl_user_manual_(web-based)_files\image062.gif 
 plu\help\pspl_user_manual_(web-based)_files\image065.jpg 
 plu\help\pspl_user_manual_(web-based)_files\image066.gif 
 plu\help\pspl_user_manual_(web-based)_files\image067.gif 
 plu\help\pspl_user_manual_(web-based)_files\image068.gif 
 plu\help\pspl_user_manual_(web-based)_files\image069.gif 
 plu\help\pspl_user_manual_(web-based)_files\image070.gif 
 plu\help\pspl_user_manual_(web-based)_files\image1.gif 
 plu\help\pspl_user_manual_(web-based)_files\image10.gif 
 plu\help\pspl_user_manual_(web-based)_files\image7.gif 
 plu\help\pspl_user_manual_(web-based)_files\image8.gif 
 plu\help\pspl_user_manual_(web-based)_files\image9.gif 
 plu\help\whdata\whftdata.js plu\help\whdata\whftdata0.htm 
 plu\help\whdata\whfts.htm plu\help\whdata\whfts.js plu\help\whdata\whfwdata.js 
 plu\help\whdata\whgdata.js plu\help\whdata\whgdata0.htm 
 plu\help\whdata\whglo.htm plu\help\whdata\whglo.js plu\help\whdata\whidata.js 
 plu\help\whdata\whidata0.htm plu\help\whdata\whidata1.htm 
 plu\help\whdata\whidx.htm plu\help\whdata\whidx.js plu\help\whdata\whtdata.js 
 plu\help\whdata\whtdata0.htm plu\help\whdata\whtoc.htm 
 plu\help\whdata\whtoc.js plu\help\whgdata\whexpbar.gif 
 plu\help\whgdata\whlstg0.htm plu\help\whgdata\whlstg1.htm 
 plu\help\whgdata\whlstg10.htm plu\help\whgdata\whlstg11.htm 
 plu\help\whgdata\whlstg12.htm plu\help\whgdata\whlstg2.htm 
 plu\help\whgdata\whlstg3.htm plu\help\whgdata\whlstg4.htm 
 plu\help\whgdata\whlstg5.htm plu\help\whgdata\whlstg6.htm 
 plu\help\whgdata\whlstg7.htm plu\help\whgdata\whlstg8.htm 
 plu\help\whgdata\whlstg9.htm plu\help\whgdata\whlsti0.htm 
 plu\help\whgdata\whlsti1.htm plu\help\whgdata\whlsti10.htm 
 plu\help\whgdata\whlsti11.htm plu\help\whgdata\whlsti12.htm 
 plu\help\whgdata\whlsti13.htm plu\help\whgdata\whlsti14.htm 
 plu\help\whgdata\whlsti15.htm plu\help\whgdata\whlsti16.htm 
 plu\help\whgdata\whlsti17.htm plu\help\whgdata\whlsti18.htm 
 plu\help\whgdata\whlsti19.htm plu\help\whgdata\whlsti2.htm 
 plu\help\whgdata\whlsti3.htm plu\help\whgdata\whlsti4.htm 
 plu\help\whgdata\whlsti5.htm plu\help\whgdata\whlsti6.htm 
 plu\help\whgdata\whlsti7.htm plu\help\whgdata\whlsti8.htm 
 plu\help\whgdata\whlsti9.htm plu\help\whgdata\whlstt0.htm 
 plu\help\whgdata\whnvf30.htm plu\help\whgdata\whnvf31.htm 
 plu\help\whgdata\whnvf32.htm plu\help\whgdata\whnvf33.htm 
 plu\help\whgdata\whnvl31.htm plu\help\whgdata\whnvl32.htm 
 plu\help\whgdata\whnvl33.htm plu\help\whgdata\whnvp30.htm 
 plu\help\whgdata\whnvp31.htm plu\help\whgdata\whnvp32.htm 
 plu\help\whgdata\whnvp33.htm plu\help\whgdata\whnvt30.htm 
 plu\help\whgdata\whnvt31.htm plu\help\whgdata\whnvt32.htm 
 plu\help\whgdata\whnvt33.htm plu\help\whxdata\whftdata0.xml 
 plu\help\whxdata\whfts.xml plu\help\whxdata\whgdata0.xml 
 plu\help\whxdata\whglo.xml plu\help\whxdata\whidata0.xml 
 plu\help\whxdata\whidata1.xml plu\help\whxdata\whidx.xml 
 plu\help\whxdata\whtdata0.xml plu\help\whxdata\whtoc.xml 
 plu\images\1x1transparent.gif plu\images\access_ownRecord.gif 
 plu\images\bad_address.gif plu\images\button_date.gif 
 plu\images\button_date_over.gif plu\images\calendar.gif 
 plu\images\camera16x11.gif plu\images\cancel.gif plu\images\clearscarch.gif 
 plu\images\clearscarch_over.gif plu\images\clinic-down.gif 
 plu\images\clinic-over.gif plu\images\clinic-sel.gif plu\images\clinic.gif 
 plu\images\closeBox.gif plu\images\closeEnter.gif plu\images\combat.gif 
 plu\images\continue.gif plu\images\Csearch.bmp plu\images\CWADwarning.gif 
 plu\images\deceased.gif plu\images\detail.gif plu\images\duplicate.gif 
 plu\images\employee.gif plu\images\enrollment.gif 
 plu\images\filterbybutton_02-provider_down.gif 
 plu\images\filterbybutton_02.gif plu\images\filterbybutton_06-clinic_down.gif 
 plu\images\filterbybutton_06.gif plu\images\filterbybutton_07-clinic_down.gif 
 plu\images\filterbybutton_07-provider_down.gif 
 plu\images\filterbybutton_07-ward_down.gif plu\images\filterbybutton_07.gif 
 plu\images\flag.gif plu\images\fugitive.gif plu\images\help_calendar.gif 
 plu\images\help_dblListbox.gif plu\images\help_hyper.gif 
 plu\images\help_scrollbar.gif plu\images\help_textbox.gif 
 plu\images\legacy_data.gif plu\images\means.gif 
 plu\images\miniselect_paging_next.gif 
 plu\images\miniselect_paging_previous.gif plu\images\missing.gif 
 plu\images\No.bmp plu\images\no.gif plu\images\no_over.gif 
 plu\images\patient_lookup.gif plu\images\patient_lookup16.gif 
 plu\images\provider-down.gif plu\images\provider-over.gif 
 plu\images\provider.gif plu\images\recent.bmp plu\images\required.gif 
 plu\images\rest.gif plu\images\return.gif plu\images\ReturnBtn.bmp 
 plu\images\return_over.gif plu\images\Rsearch.gif plu\images\search.gif 
 plu\images\search_over.gif plu\images\sensitive.gif 
 plu\images\sensitive_ssn.gif plu\images\shim.gif plu\images\similar.gif 
 plu\images\specialty-down.gif plu\images\specialty.gif plu\images\test.gif 
 plu\images\TestAppTitle.jpg plu\images\ward-clinic_down.gif 
 plu\images\ward-clinic_downwardsel.gif plu\images\ward-down.gif 
 plu\images\ward-over.gif plu\images\ward.gif plu\images\Yes.bmp 
 plu\images\yes.gif plu\images\yes_over.gif plu\jsp\alert.jsp 
 plu\jsp\alertdetails.jsp plu\jsp\longlist plu\jsp\patientdetails.jsp 
 plu\jsp\persondetails.jsp plu\jsp\person_search.jsp plu\jsp\plInterface.jsp 
 plu\jsp\plu_header.jsp plu\jsp\Portrait.html plu\jsp\ptlkError.jsp 
 plu\jsp\ptlkJSPError.jsp plu\jsp\search.jsp plu\jsp\longlist\black.html 
 plu\jsp\longlist\error.jsp plu\jsp\longlist\ErrorHelper.jsp 
 plu\jsp\longlist\images plu\jsp\longlist\javascripts 
 plu\jsp\longlist\ListComponent.jsp plu\jsp\longlist\LongList.jsp 
 plu\jsp\longlist\PageScopeHelper.jsp plu\jsp\longlist\ScrollBar.html 
 plu\jsp\longlist\StartsWithTextField.jsp 
 plu\jsp\longlist\images\1x1transparent.gif 
 plu\jsp\longlist\javascripts\ListComponent.js 
 plu\jsp\longlist\javascripts\LongList.js stylesheets\master.css 
 stylesheets\plu_style.css WEB-INF\longlist.tld WEB-INF\struts-config-plu.xml 
 caipConfig.xml PatientLookup.properties PersonLookupResources.properties 
 LongList.jar pslWeb_4.0.4.3.jar 

NUMBER: 4952                            IA #: 4952
  DATE CREATED: DEC 14, 2006
  CUSTODIAL PACKAGE: INTEGRATED PATIENT FUNDS
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: VPFS consumption of PSC API
 GENERAL DESCRIPTION:   The VPFS package consumes the Common Service PSC.  
  STATUS: Active
KEYWORDS: PSD
KEYWORDS: API
SUBSCRIBING PACKAGE: INTEGRATED PATIENT FUNDS
 SUBSCRIBING DETAILS:   The VPFS package consumes the PSC Common Service. The
 objects and methods used by VPFS, packaged in PatientServiceR2.jar, are
 detailed below: 
  
 IPatientID: 
  
 PatientID: 
         PatientID(String icn) 
         PatientID(String dfn, String stationnumber) 
  
 IPatientServiceRequest: 
         setSecurityMethod(String) 
         setUserCredential(String) 
         setUserDivision(String) 
         addRequestedService(RequestedServices) 
         setPatientIdentifier(IPatientID) 
         setRequestType(RequestType) 
  
 RequestedServices: 
         ADDRESS_DEMOGRAPHICS 
         PRIMARY_DEMOGRAPHICS 
         ADT 
         ENROLLMENT_ELIGIBILITY 
         INCOMPETENCE_INFORMATION 
  
 RequestType: 
         RETRIEVE_PATIENT_DATA 
  
 IPatientServiceDelegate: 
         retrievePatientData(IPatientServiceRequest) 
         retrieveMultiplePatients(IPatientServiceRequest, String[]) 
  
 IPatientServiceTO: 
         getErrorMessage() 
         getIdentifier() 
         getAddressDemographicsTO() 
         getPrimaryDemographicsTO() 
         getADTTO() 
         getEnrollmentEligibilityTO() 
         getIncompetenceInformationTO() 
  
 IIdentifier: 
         getFullName() 
         getDFN() 
         getICN() 
         getSSN() 
         getDateOfBirth() 
  
 IAddressDemographicsTO: 
  
 IPrimaryDemographicsTO: 
         getGender() 
         getDateOfDeath() 
  
 IADTTO: 
         getCurrentAdmission() 
         getDischargeDate() 
         getRoomBed() 
         getWardLocation() 
  
 IEnrollmentEligibilityTO: 
         isServiceConnected() 
         getServiceConnectedPercentage() 
         getPrimaryEligibilityCode() 
         getClaimNumber() 
         getTypeOfPatient() 
         isVeteran() 
  
 IIncompetenceInformationTO: 
         getDateRuledIncompetentCivil() 
         getDateRuledIncompetentVA() 
         getAddressCivil() 
         getAddressVA() 
  
 IAddress: 
         getContactName() 
         getRelationshipToPatient() 
         getAddressType() 
         getAddrLine1() 
         getAddrLine2() 
         getAddrLine3() 
         getCity() 
         getState() 
         getZipCode() 
         getResidencePhoneNumber() 
         getPhoneNumber() 
         getWorkPhoneNumber() 
  
 AddressType: 
         MAIN 
         INCOMPETENT_VA 
         INCOMPETENT_CIVIL 
         TEMPORARY 
  
 IVistaDate: 
         getDate() 
  
 PatientServiceException: 
         printStackTrace() 
         toString() 

NUMBER: 4953                            IA #: 4953
  FILE NUMBER: 6002.03                  GLOBAL ROOT: VBEC(6002.03,
  CUSTODIAL PACKAGE: VBECS              USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA4953                        ID: VBEC(6002.03,
 GENERAL DESCRIPTION:   This integration agreement allows the DSS EXTRACTS
 package access to the VBECS DSS EXTRACT file (#6002.03).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DSS EXTRACT
KEYWORDS: BLOOD BANK
KEYWORDS: VBECS
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   DSS EXTRACTS is allowed access to the VBECS DSS EXTRACT
 file (#6002.03) for the purpose of creating the Blood Bank DSS Extract. DSS
 EXTRACTS can read with FileMan or direct global reads on any field or cross
 reference in the file. DSS EXTRACTS also has permission to delete entries from
 this file. DSS EXTRACTS cannot add new entries to this file.  
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4954                            IA #: 4954
  DATE CREATED: MAR 12, 2008
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWPS
  NAME: ORWPS ACTIVE                    REMOTE PROCEDURE: ORWPS ACTIVE
  ID: ORWPS
 GENERAL DESCRIPTION:   IA to allow usage of the ORWPS ACTIVE rpc by Care
 Fusion's wCareView COTS product.  wCareView is part of the Bar Code
 Enhancements project...more info available at:  http://vista.url/ 
  STATUS: Active
COMPONENT/ENTRY POINT: ACTIVE
SUBSCRIBING PACKAGE: BAR CODE EXPANSION
 SUBSCRIBING DETAILS:   This ICR shall cover Care Fusion's use of the RPC call
 for ORWPS ACTIVE as written in CPRS GUI v27. The v27 version of this RPC
 includes three new, arguments: User, View, and Update.  
  
 ACTIVE^ORWPS(DFN,User,View,Update) 
  
 DFN = Patient DFN, User = user DUZ 
  
 View = Sort 
  
 0 - use last value stored for view 
  
 1 - CPRS v26 view, sort by Status/Exp. Date (IMO first on Inpt) 
  
 2 - sort by Status Group/Status/Location/Drug Name 
  
 3 - sort by Drug (alphabetical), status active, status recent expired 
  
 Update - update OR MEDS TAB SORT for User 
  
 1 - update parameter file 
  
 0 - will not update the parameter file 
  
 Below is Care Fusion's representation of the data wCareView is expecting to
 receive/use from this RPC call.  The "??"  indicates a field that will not be
 used.  - Med Type^ID;Med Type^??^??^??^??^??^??^??^Status^??^??^??^??^?? 
  
 Sample Data from calling RPC: Line 1 has Medication and order details; Line 2
 & 3: Sig/display text.  Refer to ICR 2400, OE/RR CALLS TO PSOORRL, to view
 details for each piece of the returned array.  
  
 ~OP^4321P;O^METAPROTERNOL AEROSOL^^^^^^54321^PENDING^^^1^^0 
  METAPROTERNOL AEROSOL  Qty: 1 \ Sig: 123A INHL THREE TIMES A DAY 
 ~OP^1234P;O^ALLOPURINOL 300MG TAB^^^^^^12345^PENDING^^^^^0 
  ALLOPURINOL 300MG TAB \ Sig: TAKE ONE TABLET BY MOUTH EVERY MORNING tPatient
 refuses laboratory-created meds  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH SUMMARY
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   CPRS approved adding Dental as a subscriber for Dental
 Record Manager to this ICR on 8/11/2009 to document existing references. 
 However the update was not made to the ICR until 2/9/18.  
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL
 SUBSCRIBING DETAILS:   Added 11/13/23, effective with patch CRHD*1*11,
 documenting the legacy use of ACTIVE^ORWPS Shift Change Handoff Tool which was
 initially released in 2008.  
  DATE ACTIVATED: MAR 25, 2008

NUMBER: 4955                            IA #: 4955
  CUSTODIAL PACKAGE: ELECTRONIC SIGNATURE
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: ELECTRONIC SIGNATURE
 GENERAL DESCRIPTION:   As HealtheVet-VistA developers migrate VistA
 applications to modern technologies, interim solutions may be required until
 enterprise solutions are mature and stable. The Electronic Signature (ESig)
 service provides an interim solution for the use of electronic codes in place
 of wet signatures while HealtheVet-VistA s security infrastructure and 
 architecture are being defined. The service duplicates for Java applications
 (J2EE or J2SE) the Kernel 8.0 electronic signature functionality currently
 used by VistA/M applications.  
  
 ESig furnishes a standard, consistent set of APIs that HealtheVet-VistA 
 developers can implement to provide users access to electronic signature data
 stored on VistA/M systems. ESig APIs make calls from Java applications to
 VistA/M systems to retrieve, validate, and store office phone, etc.).
 Additional Java APIs provide encoding/decoding, hash, and checksum calculation
 utilities, but do not interact with the VistA/M system.  
  
 This integration agreement describes the supported ESig Java APIs that are
 contained in the esig-x.x.x.xxx.jar file. This JAR file can be included in a
 HealtheVet package distribution.  
  
 SUMMARY 
  
        JAR: esig-x.x.x.xxx.jar 
    Package: gov.va.med.esig.utilities 
  
      Class: ESigDataAccess 
    Methods: isDefined 
             getESigCode 
             saveESigCode 
             getESigData 
             saveESigData 
  
      Class: ESigEncryption 
    Methods: checksum 
             encrypt 
             decrypt 
             hash 
             
      Class: ESigValidation 
    Methods: isValid 
             isValidFormat 
  STATUS: Active
COMPONENT/ENTRY POINT: isDefined(VistaLinkConnection)
 COMPONENT DESCRIPTION:   The isDefined method returns true if the user has an
 electronic signature code defined on the M server.  
  
 Class: 
  
   gov.va.med.esig.utilities.ESigDataAccess 
  
 Method: 
  
   public static final boolean isDefined 
     (gov.va.med.vistalink.adapter.cci.VistaLinkConnection connection) 
       throws ESigConnectionException, ESigNotAValidUserException 
  
 Parameters: 
  
   connection - The VistaLinkConnection handle.  
  
 Returns: 
  
   true if the user has an Electronic Signature Code defined on the M 
   server.  
   
 Throws: 
  
   ESigConnectionException - if the RPC request fails.  
   ESigNotAValidUserException - if the DUZ of the user does not correspond 
     to a valid entry in the New Person file.  
  
 Example: 
  
   try { 
     if (ESigDataAccess.isDefined(myConnection)) { 
       System.out.println("Your electronic signature code is defined on the 
         M server."); 
     } else { 
       System.out.println("You currently have no electronic signature code 
         defined."); 
     }
   } catch (FoundationsException e) { 
     System.out.println(e.getMessage()); 
   }
COMPONENT/ENTRY POINT: getESigCode(VistaLinkConnection)
 COMPONENT DESCRIPTION:   The getESigCode method retrieves the encrypted
 electronic signature code from the M server.  
  
 Class: 
  
   gov.va.med.esig.utilities.ESigDataAccess 
  
 Method: 
  
   public static final java.lang.String getESigCode 
     (gov.va.med.vistalink.adapter.cci.VistaLinkConnection connection) 
     throws ESigConnectionException, ESigNotAValidUserException 
  
 Parameters: 
  
   connection - The VistaLinkConnection handle.  
  
 Returns: 
   
   A String that contains the user's encrypted Electronic Signature Code.  
  
 Throws: 
  
   ESigConnectionException - if the RPC request fails.  
   ESigNotAValidUserException - if the DUZ of the user does not correspond 
     to a valid entry in the New Person file.  
  
 Example: 
  
   try { 
     String eSig = ESigDataAccess.getESigCode(myConnection); 
     System.out.println(" ESig obtained from VistA: " + eSig); 
   } catch (Exception e) { 
     System.out.println(e.getMessage()); 
   }
COMPONENT/ENTRY POINT: saveESigCode(char[] or String, VistaLinkConnection)
 COMPONENT DESCRIPTION:   The overloaded saveESigCode method take the
 unencrypted electronic signature code either in a character array or a String,
 and saves the encrypted form of the electronic signature code in the New
 Person file on the M server.  
  
 Class: 
  
   gov.va.med.esig.utilities.ESigDataAccess 
  
 Method: 
  
   public static final void saveESigCode(char[] eSigCode, 
     gov.va.med.vistalink.adapter.cci.VistaLinkConnection connection) 
       throws ESigConnectionException, 
         ESigNotAValidUserException, 
         ESigUnchangedElectronicSignatureException, 
         ESigInvalidFormatException 
  
   public static final void saveESigCode(java.lang.String eSigCode, 
     gov.va.med.vistalink.adapter.cci.VistaLinkConnection connection) 
     throws ESigConnectionException, 
       ESigNotAValidUserException, 
       ESigUnchangedElectronicSignatureException, 
       ESigInvalidFormatException 
  
 Parameters: 
     
   eSigCode   - An array of characters or a String that contains the 
                user-supplied (unencrypted) electronic signature code.  
   connection - The VistaLinkConnection handle.  
  
 Throws: 
     
   ESigConnectionException - if the RPC request fails.  
   ESigNotAValidUserException - if the DUZ of the user does not correspond 
     to a valid entry in the New Person file.  
   ESigUnchangedElectronicSignatureException - if the electronic signature 
     on the M server is the same as the electronic signature code passed 
     in.  
   ESigInvalidFormatException - if the format of the electronic signature 
     code passed in is not valid. VistA electronic signatures codes must 
     be between 6 and 20 characters in length, and cannot contain control 
     characters. That is, they must contain only the printable characters 
     in the 7-bit ASCII character set, decimal ASCII values 32 through 126 
  
 Example: 
  
   try { 
     String esig = "NEW ESIG VALUE"; 
     System.out.println("Value attempting to save: " + esig); 
     ESigDataAccess.saveESigCode(esig, myConnection); 
     System.out.println("Value " + esig + " saved successfully."); 
   } catch (Exception e) { 
     System.out.println(e.getMessage()); 
   }
COMPONENT/ENTRY POINT: getESigData(VistaLinkConnection)
 COMPONENT DESCRIPTION:   The getESigData method obtains other electronic
 signature related data from the M server and returns it in a HashMap. The key
 values in the HashMap are: 
  
  - initial 
  - signature block printed name 
  - signature block title 
  - office phone 
  - voice pager 
  - digital pager 
  
 Class: 
  
   gov.va.med.esig.utilities.ESigDataAccess 
  
 Method: 
  
   public static final java.util.HashMap getESigData 
     (gov.va.med.vistalink.adapter.cci.VistaLinkConnection connection) 
       throws ESigConnectionException, ESigNotAValidUserException 
  
 Parameters: 
  
   connection - The VistaLinkConnection handle.  
  
 Returns: 
  
   A HashMap that contains the user's data.  
  
 Throws: 
  
   ESigConnectionException - if the RPC request fails.  
   ESigNotAValidUserException - if the DUZ of the user does not correspond 
     to a valid entry in the New Person file.  
  
 Example: 
  
   Map oldValues = null 
   try { 
     oldValues = ESigDataAccess.getESigData(myConnection); 
     System.out.println("Values of Map returned:"); 
     System.out.println(" INITIAL: " + oldValues.get("initial")); 
     System.out.println("SIGNATURE BLOCK PRINTED NAME: " + 
     oldValues.get("signature block printed name")); 
     System.out.println(" SIGNATURE BLOCK TITLE: " + 
       oldValues.get("signature block title")); 
     System.out.println(" OFFICE PHONE: " + oldValues.get("office 
       phone")); 
     System.out.println(" VOICE PAGER: " + oldValues.get("voice pager")); 
     System.out.println(" DIGITAL PAGER: " + oldValues.get("digital 
       pager")); 
   } catch (Exception e) { 
     System.out.println(e.getMessage()); 
   }
COMPONENT/ENTRY POINT: saveESigData(Map, VistaLinkConnection)
 COMPONENT DESCRIPTION:   The saveESigData method accepts the following values
 in a Map, and saves the values in the New Person file on the M server: 
  
   - initial 
   - signature block printed name 
   - signature block title 
   - office phone 
   - voice pager 
   - digital pager 
  
 Class: 
  
   gov.va.med.esig.utilities.ESigDataAccess 
  
 Method: 
  
   public static final void saveESigData(java.util.Map values, 
     gov.va.med.vistalink.adapter.cci.VistaLinkConnection connection) 
       throws ESigConnectionException, ESigNotAValidUserException, 
         ESigInvalidFormatException 
  
 Parameters: 
  
   values     - The values passed in a HashMap 
   connection - The VistaLinkConnection handle.  
  
 Throws: 
  
   ESigConnectionException - if the RPC request fails.  
   ESigNotAValidUserException - if the DUZ of the user does not correspond 
     to a valid entry in the New Person file.  
   ESigInvalidFormatException - if the format of any of the data passed in 
     is not valid. In this case, none of the data is filed.  
  
 Example: 
  
   HashMap newValues = new HashMap(); 
   newValues.put("initial", "TAS"); 
   newValues.put("signature block printed name", "Test A. Smith"); 
   newValues.put("signature block title", "Dietician"); 
   newValues.put("office phone", "(123) 123-4567"); 
   newValues.put("voice pager", "(234) 234-5678"); 
   newValues.put("digital pager", "(345) 345-6789"); 
   try { 
     ESigDataAccess.saveESigData(newValues, myConnection); 
     LOGGER.info("New values saved successfully."); 
   } catch (Exception e) { 
     System.out.println(e.getMessage()); 
   }
COMPONENT/ENTRY POINT: checksum(String)
 COMPONENT DESCRIPTION:   The checksum method calculates a checksum number for
 a String using the same algorithm as the Kernel $$CHKSUM^XUSESIG1 function.  
  
 Class: 
  
   gov.va.med.esig.utilities.ESigEncryption 
  
 Method: 
  
   public static final java.lang.String checksum 
    (java.lang.String document) 
  
 Parameters: 
  
   document - A String containing the document for which to calculate a 
              checksum value.  
  
 Returns: 
  
   The checksum value.  
  
 Example: 
  
   String aDocument = "This is a sample document.\nA second line.\n"; 
   String checksum = ESigEncryption.checksum(aDocument); 
   System.out.println(" Java checksum: " + checksum); 
   System.out.println(" aDocument:\n" + aDocument); 
COMPONENT/ENTRY POINT: encrypt(String, double, double)
 COMPONENT DESCRIPTION:   This method encrypts a String using the same
 algorithm as the Kernel EN^XUSHSHP entry point.  
  
 Class: 
  
   gov.va.med.esig.utilities.ESigEncryption 
  
 Method: 
  
   public static final java.lang.String encrypt(java.lang.String text, 
     double idNumber, double docNumber) 
  
 Parameters: 
  
   text      - The String to be encrypted.  
   idNumber  - An identification number, such as DUZ.  
   docNumber - A document number (or the number one).  
  
 Returns: 
  
   The encrypted version of the input String.  
  
 Example: 
  
   String aStringToEncrypt = "John A. Smith, MD"; 
   double id = 101.0; 
   double doc = 53684791; 
   String 
   encryptedText = ESigEncryption.encrypt(aStringToEncrypt, id, doc); 
   System.out.println(" aString: " + aStringToEncrypt); 
   System.out.println(" Java encrypted value: " + encryptedText); 
COMPONENT/ENTRY POINT: decrypt(String, double, double)
 COMPONENT DESCRIPTION:   This method decrypts a String using the same
 algorithm as the Kernel DE^XUSHSHP entry point.  
  
 Class: 
  
   gov.va.med.esig.utilities.ESigEncryption 
  
 Method: 
  
   public static final java.lang.String decrypt(java.lang.String text, 
     double idNumber, double docNumber) 
  
 Parameters: 
  
   text      - The String to be decrypted.  
   idNumber  - The identification number used as the idNumber input 
               parameter to the encrypt call.  
   docNumber - The document numbers used as the docNumber input parameter 
               to the encrypt call.  
  
 Returns: 
  
   The decrypted version of the input String.  
  
 Example: 
  
   String decryptedText = ESigEncryption.decrypt(encryptedText, id, doc); 
   System.out.println(" aString: " + encryptedText); 
   System.out.println(" Java decrypted value: " + decryptedText); 
COMPONENT/ENTRY POINT: hash(String or char[])
 COMPONENT DESCRIPTION:   This overloaded method hashes a String or characters
 in a character array using the same algorithm as the Kernel HASH^XUSHSHP entry
 point. This method is used to hash an electronic signature code entered by the
 user.  
  
 Class: 
  
   gov.va.med.esig.utilities.ESigEncryption 
  
 Method: 
  
   public static final java.lang.String hash(java.lang.String text) 
  
   public static final java.lang.String hash(char[] text) 
  
 Parameters: 
  
   text - The text to hash, contained in a String or character array.  
  
 Returns: 
  
   A String that is the hashed form of the text in the input array.  
  
 Example: 
  
   String aString = "AnESigForTesting"; 
   String hashedText = ESigEncryption.hash(aString); 
   System.out.println(" aString: " + aString); 
   System.out.println(" Java hashed string: " + hashedText); 
COMPONENT/ENTRY POINT: isValid(char[] or String, VistaLinkConnection)
 COMPONENT DESCRIPTION:   The overloaded isValid method validates a
 user-supplied electronic signature code against the electronic signature code
 stored in the New Person file (#200) on the M server. It returns true if the
 electronic signature code passed matches the code stored on the M server.  
  
 A VistALink connection is assumed, and the VistaLinkConnection object must be
 passed to the method along with the electronic signature code being validated. 
  
 Class: 
  
   gov.va.med.esig.utilities.ESigValidation 
  
 Method: 
  
   public static final boolean isValid(char[] code, 
     gov.va.med.vistalink.adapter.cci.VistaLinkConnection connection) 
       throws ESigConnectionException, 
         ESigNotAValidUserException, 
          ESigNoElectronicSignatureDefinedException 
  
   public static final boolean isValid(java.lang.String code, 
     gov.va.med.vistalink.adapter.cci.VistaLinkConnection connection) 
       throws ESigConnectionException, 
         ESigNotAValidUserException, 
         ESigNoElectronicSignatureDefinedException 
  
 Parameters: 
  
   code       - A character array or String containing the unencrypted 
                user-supplied electronic signature code.  
   connection - The VistaLinkConnection handle.  
  
 Returns: 
  
   true if the electronic signature code matches the code store on the M 
   server.  
  
 Throws: 
  
   ESigConnectionException - if an error occurred while attempting to make 
     an RPC call on the M server.  
   ESigNotAValidUserException - if the user identified by DUZ on the M 
     server does not correspond to an entry in the New Person file.  
   ESigNoElectronicSignatureDefinedException - if the user has no 
     electronic signature defined on the M server.  
  
 Example: 
  
   try { 
     boolean valid = ESigValidation.isValid(userESig.toCharArray(), 
       myConnection); 
     if (valid) { 
       System.out.println("Electronic signature code is valid."); 
     } else { 
       System.out.pritnln("Electronic signature is not valid."); 
     }
   } catch (ESigConnectionException e) { 
     System.out.println(e.getMessage()); 
   } catch (ESigNotAValidUserException e) { 
     System.out.println(e.getMessage()); 
   } catch (ESigNoElectronicSignatureDefinedException e) { 
     System.out.println(e.getMessage()); 
   }
COMPONENT/ENTRY POINT: isValidFormat(char[] or String)
 COMPONENT DESCRIPTION:   The overloaded isValidFormat method checks whether
 the format of the user-supplied electronic signature code is valid. Electronic
 signatures codes must be between 6 and 20 characters in length, and cannot
 contain control characters; that is, they must contain only the printable 
 characters in the 7-bit ASCII character set, decimal ASCII values 32 through
 126.  
  
 Class: 
  
   gov.va.med.esig.utilities.ESigValidation 
  
 Method: 
  
   public static final boolean isValidFormat(char[] code) 
  
   public static final boolean isValidFormat(java.lang.String code) 
  
 Parameters: 
  
   code - A character array containing the unencrypted user-supplied 
          electronic signature code.  
  
 Returns: 
  
   true if the format of the electronic signature code is valid.  
  
 Example: 
  
   String[] validESigCodes = { "6CHARS", 
     "LENGTH 20 CHARACTERS", 
     "`~!@#$%^&*()-_=+",
     "[]\\{}|;:'\",./<>?",
     "VALID_INCL.PUNC" }; 
   String[] invalidESigCodes = { "SHORT", 
     "",
     "THIS ELECTRONIC SIGNATURE IS TOO LONG", 
     "Invalid mixed case", }; 
  
   System.out.println(" Valid e-sig codes:"); 
  
   for (int i = 0; i < validESigCodes.length; i++) { 
     System.out.println(" " + validESigCodes[i]); 
     System.out.println(" --> " + 
       (ESigValidation.isValidFormat(validESigCodes[i]) 
       ? "valid" : "invalid")); 
   }
  
   System.out.println(""); 
   System.out.println(" Invalid e-sig codes:"); 
   
   for (int i = 0; i < invalidESigCodes.length; i++) { 
     if (invalidESigCodes[i].equals("")) { 
       System.out.println(" <null> string"); 
     } else { 
       System.out.println(" " + invalidESigCodes[i]); 
     }
     System.out.println(" --> " + 
       (ESigValidation.isValidFormat(invalidESigCodes[i]) ? "valid" : 
       "invalid")); 
   }
  DATE ACTIVATED: JAN 22, 2007

NUMBER: 4956                            IA #: 4956
  DATE CREATED: JAN 09, 2007            CUSTODIAL PACKAGE: VBECS
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VBECS DSS EXTRACT
  REMOTE PROCEDURE: VBECS DSS EXTRACT
 GENERAL DESCRIPTION:   This RPC inserts or updates post transfusion related
 data in the VBECS DSS EXTRACT file (#6002.03). The data is passed into the
 VBECDSS routine through the input parameters and a success indicator is
 returned to the Blood Bank medical device.  
  
 INPUT PARAMETER DESCRIPTION: 
  PARAMS("TRANSACTION ID") = Unique record identifier 
  PARAMS("DFN") = Patient identifier 
  PARAMS("FACILITY") = Institution identifier 
  PARAMS("PHYSICIAN") = Provider requesting blood product for transfusion 
  PARAMS("ORDERING PROVIDER") = Provider who ordered Type and Crossmatch 
  PARAMS("PRODUCT NAME") = Short blood product name 
  PARAMS("COMPONENT ABBREVIATION") = Abbreviation of blood component 
  PARAMS("NUMBER OF UNITS") = Number of pooled units transfused 
  PARAMS("TRANSFUSION DATE") = Date/time of transfusion 
  PARAMS("VOLUME") = Total volume of units transfused 
  PARAMS("REACTION TYPE") = Type of reaction indicated 
  PARAMS("UNIT MODIFICATION") = String of codes representing modifications 
     done on units transfused. String cannot exceed 6 character.  
     D = Deglycerolize 
     F = Freeze 
     I = Irradiate 
     L = Leukoreduce 
     P = Pool 
     R = Rejuvenate 
     S = Split/Divide 
     T = Thaw 
     U = Thaw/Pool Cryo 
     V = Volume Reduce 
     W = Wash 
  PARAMS("REACTION") = Yes or No value if a reaction was indicated.  
  
 RETURN PARAMETER DESCRIPTION: This RPC returns and XML document containing a
 SuccessIndicator element represented by either a 1 for a successful insert or
 update or a 0 for an unsuccessful insert or update in the VBECS DSS EXTRACT
 file (#6002.03).  
  
 Example of successful transaction: 
  <ReturnValue><SuccessIndicator>1</SuccessIndicator></ReturnValue> 
  
 Example of unsuccessful transaction: 
  <ReturnValue><SuccessIndicator>0</SuccessIndicator></ReturnValue> 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VBECS

NUMBER: 4957                            IA #: 4957
  FILE NUMBER: 355.93                   GLOBAL ROOT: IBA(355.93
  CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4957
  ID: IBA(355.93
GLOBAL REFERENCE: IBA(355.93,D0,
FIELD NUMBER: 41.01                     FIELD NAME: NPI
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   National Provider Identifier, a 10-digit numeric field
 with the CMS-assigned identifier for a provider.  
 GLOBAL DESCRIPTION:   The IBA(355.93 global holds the demographic data for a
 non-VA provider, both individual and organizational.  
 GENERAL DESCRIPTION:   The CBO Extract needs to extract the National Provider
 Identifier (NPI) from the NON/OTHER VA BILLING PROVIDER file (#355.93) for
 both individual and organizational providers.  This is a read-only action and
 does not modify any fields in the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CBO
KEYWORDS: Extract
KEYWORDS: NPI
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   The CBO Extract already extracts provider data during
 its nightly run.  The National Provider Identfier (NPI) was added to the
 NON/OTHER VA BILLING PROVIDER file (#355.93) as part of the HIPAA NPI project. 
 The NPI needs to be extracted and included as part of the nightly CBO Extract 
 process.  
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4958                            IA #: 4958
  FILE NUMBER: 4                        GLOBAL ROOT: DIC(4,D0
  CUSTODIAL PACKAGE: KERNEL             USAGE: Private
  TYPE: File                            NAME: DIRECT FILE READ OF FILE 4
  ORIGINAL NUMBER: 4958                 ID: DIC(4,D0
GLOBAL REFERENCE: DIC(4,D0,NPI
FIELD NUMBER: 41.99                     FIELD NAME: NPI
  LOCATION: NPI;1                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The National Provider Identifier is a 10-digit numeric
 field with the CMS-assigned identifier for the facility.  
 GENERAL DESCRIPTION:   The CBO Extract needs to extract the National Provider
 Identifier (NPI) from the INSTITUTION file (#4) for the organizational
 providers found in the extract under the data stream fields named DEFAULT
 FACILITY and FACILITY WHERE CARE RENDERED.  This is a read-only action and
 does not modify any data in any fields in the file.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: NPI
KEYWORDS: INSTITUTION
KEYWORDS: FACILITY
KEYWORDS: CBO
KEYWORDS: EXTRACT
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   The CBO Extract already extracts facility data during
 its nightly run.  The National Provider Identifier (NPI) was added to the
 INSTITUTION file (#4) as part of the HIPAA NPI project.  The NPI needs to be 
 extracted and included as part of the nightly CBO Extract process.  This 
 extraction is a read-only type action and no data is modified.  
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4959                            IA #: 4959
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,D0,NPI
  DATE CREATED: FEB 18, 2007            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: DIRECT READ OF FILE 200         ORIGINAL NUMBER: 4958
  ID: VA(200,D0,NPI
GLOBAL REFERENCE: VA(200,D0,NPI
FIELD NUMBER: 41.99                     FIELD NAME: NPI
  LOCATION: NPI;1                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The National Provider Identifier is a 10-digit numeric
 field with the CMS-assigned identifier for the provider.  
 GENERAL DESCRIPTION:   The CBO Extract needs to extract the National Provider
 Identifier (NPI) from the NEW PERSON file (#200) for the individual providers
 found in the extract under the data stream field named PROVIDER. This is a 
 read-only action and does not modify any data in any fields in the file.  
  STATUS: Retired                       DURATION: Next Version
KEYWORDS: NPI
KEYWORDS: PROVIDER
KEYWORDS: PERSON
KEYWORDS: CBO
KEYWORDS: EXTRACT
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   The CBO Extract already extracts facility data during 
 its nightly run.  The National Provider Identifier (NPI) was added to the NEW
 PERSON file (#200) as part of the HIPAA NPI project.  The NPI needs to be 
 extracted and included as part of the nightly CBO Extract process.  This
 extraction is a read-only type action and no data is modified.  
  DATE ACTIVATED: MAR 04, 2007
REMINDER: APR 01, 2007

NUMBER: 4960                            IA #: 4960
  FILE NUMBER: 355.9                    GLOBAL ROOT: IBA(355.9
  CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INSURANCE CO AND PROVIDER ID
  ID: IBA(355.9
GLOBAL REFERENCE: IBA(355.9,D0
FIELD NUMBER: .02                       FIELD NAME: INSURANCE CO
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Pointer to the INSURANCE COMPANY file(#36). This is the
 insurance company that has assigned a specific ID to the provider. If this
 data is not entered, the ID number will be assumed to apply to all insurance
 companies for the provider.  
FIELD NUMBER: .07                       FIELD NAME: PROVIDER ID
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The provider ID that will be used for a claim when all
 criteria defined on the record have been met.  
 GLOBAL DESCRIPTION:   The IBA(355.9 global contains one record for each unique
 billing provider ID number that an individual provider (practitioner) is
 assigned by an insurance company or by a licensing or government entity.  
GLOBAL REFERENCE: IBA(355.9,B,PRACTITIONER,IEN)
 GLOBAL DESCRIPTION:   Uses B x-ref to get IEN for given practitioner 
 GENERAL DESCRIPTION:   The NPI Extract needs to extract the INSURANCE CO and
 PROVIDER ID from the IB BILLING PRACTITIONER ID file (#355.9). This is a
 read-only action and does not modify any fields in the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NPI
KEYWORDS: Extract
KEYWORDS: practitioner
KEYWORDS: ID
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   The NPI Extract extracts IB billing practitioner data
 during its run. The extract was developed as part of the HIPAA NPI project.
 The INSURANCE CO and PROVIDER ID need to be extracted and included as part of
 the NPI Extract process.  
  DATE ACTIVATED: FEB 01, 2007

NUMBER: 4961                            IA #: 4961
  FILE NUMBER: 355.91                   GLOBAL ROOT: IBA(355.91
  CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: GET PROVIDER ID FROM INSURANCE DATA
  ID: IBA(355.91
GLOBAL REFERENCE: IBA(355.91,D0
FIELD NUMBER: .07                       FIELD NAME: PROVIDER ID
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The provider ID that will be reported for the provider ID
 type for the insurance company.  
 GLOBAL DESCRIPTION:   The IBA(355.91 global contains one record for each
 provider ID that an Insurance company assigns to a facility for ALL billing
 providers at the facility.  
GLOBAL REFERENCE: IBA(355.91,B,INSURANCE CO,IEN)
 GLOBAL DESCRIPTION:   Uses B x-ref to get IEN for given insurance company 
 GENERAL DESCRIPTION:   The NPI Extract needs to extract the PROVIDER ID from
 the IB INSURANCE CO LEVEL BILLING PROV ID file (#355.91). This is a read-only
 action and does not modify any fields in the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NPI
KEYWORDS: Extract
KEYWORDS: ID
KEYWORDS: Provider
KEYWORDS: Insurance
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   The NPI Extract extracts IB insurance company level
 billing data during its run. The extract was developed as part of the HIPAA
 NPI project. The PROVIDER ID needs to be extracted and included as part of the
 NPI Extract process.  
  DATE ACTIVATED: FEB 01, 2007

NUMBER: 4962                            IA #: 4962
  FILE NUMBER: 355.92                   GLOBAL ROOT: IBA(355.92
  CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: GET PROVIDER ID FROM FACILITY BILLING ID
  ID: IBA(355.92
GLOBAL REFERENCE: IBA(355.92,D0
FIELD NUMBER: .07                       FIELD NAME: PROVIDER ID
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The Provider ID is the facility ID that will be reported
 for the provider ID type for the insurance company.  
 GLOBAL DESCRIPTION:   The IBA(355.92 global contains one record for each
 facility ID that an Insurance company assigns to a facility.  
GLOBAL REFERENCE: IBA(355.92,B,INSURANCE COMPANY,IEN)
 GLOBAL DESCRIPTION:   Uses B x-ref to get IEN for given insurance company 
 GENERAL DESCRIPTION:   The NPI Extract needs to extract the PROVIDER ID from
 the FACILITY BILLING ID file (#355.92). This is a read-only action and does
 not modify any fields in the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NPI
KEYWORDS: Extract
KEYWORDS: FACILITY
KEYWORDS: Provider
KEYWORDS: Insurance
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   The NPI Extract extracts facility billing data during
 its run. The extract was developed as part of the HIPAA NPI project. The
 PROVIDER ID needs to be extracted and included as part of the NPI Extract
 process.  
  DATE ACTIVATED: FEB 01, 2007

NUMBER: 4963                            IA #: 4963
  FILE NUMBER: 59                       GLOBAL ROOT: PS(59
  CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4963
  ID: PS(59
GLOBAL REFERENCE: PS(59,D0
FIELD NUMBER: 1008                      FIELD NAME: NCPDP #
  LOCATION: SAND;3                      ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is the site-specific National Council for
 Prescription Drug Programs (NCPDP) number.  
FIELD NUMBER: 101                       FIELD NAME: NPI INSTITUTION
  LOCATION: INI;2                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is the pointer to the entry in the INSTITUTION
 file (#4) which contains the NPI number associated with the OUTPATIENT SITE.  
 GLOBAL DESCRIPTION:   The PS(59 global contains one record for each outpatient
 pharmacy site.  
 GENERAL DESCRIPTION:   The NPI Extract needs to extract the NCPDP number from
 the OUTPATIENT SITE file (#59).  This is a read-only action and does not
 modify any fields in the file.  The NPI Extract also needs to use the NPI
 INSTITUTION field to get the correct NPI entry from file #4.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NPI
KEYWORDS: Extract
KEYWORDS: NCPDP
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   The NPI Extract extracts outpatient site data during
 its run. The extract was developed as part of the HIPAA NPI project. The NCPDP
 # needs to be extracted and included as part of the NPI Extract process.  The
 extract process also needs to examine the NPI INSTITUTION field to match the
 OUTPATIENT SITE to the correct entry in the INSTITUTION file.  
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4964                            IA #: 4964
  FILE NUMBER: 350.9                    GLOBAL ROOT: IBE(350.9
  DATE CREATED: AUG 26, 2010            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: GET FACILITY NAME & FED TAX NUMBER FROM IB SITE PARAMS
  ID: IBE(350.9
GLOBAL REFERENCE: IBE(350.9,D0
FIELD NUMBER: .02                       FIELD NAME: FACILITY NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The name of your facility from the Institution file.  
FIELD NUMBER: 1.05                      FIELD NAME: FEDERAL TAX NUMBER
  LOCATION: 1;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The facility federal tax ID number.  
FIELD NUMBER: 19;.02                    FIELD NAME: PAY-TO PROVIDER NAME
  LOCATION: 19;0-0;2                    ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The Pay- To Provider name.  
FIELD NUMBER: 19;1.01                   FIELD NAME: Street Address 1.
  LOCATION: 19;0-1;1                    ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Pay-to Provider Street Address 1 
FIELD NUMBER: 19;1.02                   FIELD NAME: Street Address 2
  LOCATION: 19;0-1;2                    ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Pay-To Provider Street Address 2 
FIELD NUMBER: 19;1.03                   FIELD NAME: City
  LOCATION: 19;0-1;3                    ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Pay-To Provider City.  
FIELD NUMBER: 19;1.04                   FIELD NAME: State
  LOCATION: 19;0-1;4                    ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Pay-To Provider State.  
FIELD NUMBER: 11.03                     FIELD NAME: Default Pay-To Provider
  LOCATION: 11;3                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The default Pay-To Provider 
FIELD NUMBER: 19;1.05                   FIELD NAME: Pay-To Provider Zip Code
  LOCATION: 19;0-1;5                    ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The Pay-To Provider zip code.  
 GLOBAL DESCRIPTION:   The IBE(350.9 global contains the data necessary to run
 the IB package and to manage the IB background filer.  
 GENERAL DESCRIPTION:   The NPI Extract needs to extract the FACILITY NAME, the 
 FEDERAL TAX NUMBER and the PAY-TO PROVIDER data from the IB SITE PARAMETER
 FILE (#350.9).  This is a read-only action and does not modify any fields in
 the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NPI
KEYWORDS: Extract
KEYWORDS: FEDERAL
KEYWORDS: TAX
KEYWORDS: FACILITY
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   The NPI Extract extracts IB site parameter data during
 its run.  The extract was developed as part of a HIPAA NPI project.  The
 FACILITY NAME, the FEDERAL TAX NUMBER, and the PAY-TO PROVIDER need to be
 extracted and included as part of the NPI Extract process.  
  DATE ACTIVATED: AUG 26, 2010

NUMBER: 4965                            IA #: 4965
  FILE NUMBER: 355.93                   GLOBAL ROOT: IBA(355.93
  CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: GET ZERO NODE INFO FROM IB NON/OTHER VA BILLING PROVIDER
  ID: IBA(355.93
GLOBAL REFERENCE: IBA(355.93,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PROVIDER TYPE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: STREET ADDRESS
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1                        FIELD NAME: STREET ADDRESS LINE 2
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: CITY
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: STATE
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: ZIP CODE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: FACILITY DEFAULT ID NUMBER
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .12                       FIELD NAME: STATE LICENSE #
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   The IBA(355.93 global holds the demographic data for a
 non-VA provider, both individual and organizational.  
GLOBAL REFERENCE: IBA(355.93,NPI,NPI NUMBER,IEN)
 GLOBAL DESCRIPTION:   Uses NPI x-ref to get IEN for a given NPI number 
GLOBAL REFERENCE: IBA(355.93,D0,NPISTATUS,B,DATE)
 GLOBAL DESCRIPTION:   Uses B x-ref in NPISTATUS node to check active date for
 a given NPI number 
GLOBAL REFERENCE: IBA(355.93,D0,TAXONOMY,B,IEN)
 GLOBAL DESCRIPTION:   Uses B x-ref in TAXONOMY node to loop through and get
 data for all IENs pointing to file 8932.1 
 GENERAL DESCRIPTION:   The NPI Extract needs to extract several fields from
 the IB NON/OTHER VA BILLING PROVIDER file (#355.93). This is a read-only
 action and does not modify any fields in the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NPI
KEYWORDS: Extract
KEYWORDS: NON-VA
KEYWORDS: PROVIDER
KEYWORDS: FACILITY
KEYWORDS: TAXONOMY
KEYWORDS: ID
KEYWORDS: LICENSE
KEYWORDS: ADDRESS
KEYWORDS: TYPE
KEYWORDS: NON/OTHER
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   The NPI Extract extracts IB Non/Other VA Billing
 Provider data during its run. The extract was developed as part of the HIPAA 
 NPI project. Several fields need to be extracted and included as part of the
 NPI Extract process.  
  DATE ACTIVATED: FEB 01, 2007

NUMBER: 4966                            IA #: 4966
  FILE NUMBER: 773                      GLOBAL ROOT: HLMA(D0
  DATE CREATED: MAY 26, 2017            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DETERMINE MESSAGE ID AND DATE/TIME
  ID: HLMA(D0
GLOBAL REFERENCE: HLMA('C',
FIELD NUMBER: 2                         FIELD NAME: MESSAGE ID
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   MESSAGE ID x-ref 
  
GLOBAL REFERENCE: HLMA(D0,
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME ENTERED
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The date/time the message was received/created.  
  
 GENERAL DESCRIPTION:   This integration agreement will be used for references
 to the HL7 MESSAGE ADMINISTRATION (#773) file.  Each reference by package is
 included in the SUBSCRIBING DETAILS for each subscribing package.  
     
 As new requests to this file are received and approved, this integration 
 agreement will be updated.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
 SUBSCRIBING DETAILS:   The ECME package needs to read the incoming ACK to
 determine which Pharmacy Registration transmission message was accepted or
 rejected by the other side of the interface.  Once determining which message
 the ACK refers to, the ECME can look up the original transmitted message for 
 further processing.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   GMRC has an HL7 interface with a Referral &
 Authorization System (RAS) database in the Austin FSC. Certain types of
 consults are sent to RAS in support of Veterans being approved for community
 (non-VA) care. Occasionally, there may be an issue in parsing the data sent
 from GMRC to RAS. When this occurs, a mail message is generated from the data
 in the ACK message. The mail message contains the Message ID of the offending 
 HL7 message. GMRC would like to extend the information in the mail message by
 adding the consult record number. To do that, GMRC will take the Message ID
 from the ACK, look up the associated HL7 Message Text, and then parse the
 Message Text (772;200) in order to retrieve the consult record number.  
  DATE ACTIVATED: FEB 01, 2007

NUMBER: 4967                            IA #: 4967
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,D0
  DATE CREATED: FEB 15, 2007            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: File
  NAME: DBIA4967                        ID: VA(200,D0
GLOBAL REFERENCE: VA(200,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: TITLE
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .151                      FIELD NAME: EMAIL ADDRESS
  LOCATION: .15;1                       ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The ECME package needs to pull contact information for
 specific users so that information regarding the ePharmacy interface may be
 reported to the appropriate individual.  
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 4968                            IA #: 4968
  CUSTODIAL PACKAGE: CMOP               USAGE: Controlled Subscription
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: PSXBPSRP                     NAME: PSXBPSRP
  ID: PSXBPSRP
 GENERAL DESCRIPTION:   This Integration Agreement grants permission for the
 ECME application to call the routine PSXBPSRP that provides the CMOP/ECME
 Activity Report. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSXBPSRP
KEYWORDS: CMOP/ECME
KEYWORDS: ECME ACTIVITY
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   It generates the CMOP/ECME Activity Report.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4969                            IA #: 4969
  DATE CREATED: JAN 22, 2007            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGENCDA
  NAME: DGENCDA - Catastrophic Disability API
  ID: DGENCDA                           STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$GET
 COMPONENT DESCRIPTION:   Returns catastrophic disability information for a
 patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN = Patient (#2) file internal entry number 
VARIABLES: DGCDIS                       TYPE: Output
 VARIABLES DESCRIPTION:   The catastrophic disability array name passed by
 reference: 
  
  DGCDIS("VCD")=Catastrophic Disability indicator 
  DGCDIS("BY")=Decided By 
  DGCDIS("DATE")=Date of Decision 
  DGCDIS("FACDET")=Facility making the determination 
  DGCDIS("REVDTE")=Review Date 
  DGCDIS("METDET")=Method of Determination 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   In support of the Catastrophically Disabled Copay
 Report 
  DATE ACTIVATED: MAR 22, 2011

NUMBER: 4970                            IA #: 4970
  DATE CREATED: JAN 22, 2007            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOBPSU2
  NAME: PSOBPSU2                        ID: PSOBPSU2
 GENERAL DESCRIPTION:   This routine contains Outpatient Pharmacy APIs related
 to the electronic billing of prescription claims (ePharmacy).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MWC
KEYWORDS: PSOBPSU2
KEYWORDS: RXNUM
COMPONENT/ENTRY POINT: $$MWC(RX,RFL)
 COMPONENT DESCRIPTION:   Returns the prescription dispensing route: (W)indow,
 (M)ail or (C)MOP.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTION file (#52).  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the REFILL multiple (#52.1) in the
 PRESCRIPTION file (#52). (Default: latest refill) 
VARIABLES: $$MWC                        TYPE: Output
 VARIABLES DESCRIPTION:   Prescription dispensing route:   W - WINDOW 
                                  M - MAIL (LOCAL) 
                                  C - CMOP 
  
COMPONENT/ENTRY POINT: $$DUR(RX,RFL)
 COMPONENT DESCRIPTION:   This function is used to determine if a prescription
 was previously placed on hold due to a host reject error.  
  
 A 0 (zero) is returned when reject codes M6, M8, NN, or 99 are present OR if
 on suspense hold which means the prescription should not be sent to CMOP.  A 1
 (one) is returned if the prescription is not on suspense hold and can be sent
 to CMOP.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   PRESCRIPTION file #52 IEN.  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Refill number.  
COMPONENT/ENTRY POINT: $$RXNUM(ECME)
 COMPONENT DESCRIPTION:   The purpose of this function is to return the
 internal Prescription IEN given the ECME#.  This function may perform user
 interface on the screen so it should never be called in the background or
 where screen messages are not desired.  
VARIABLES: ECME                         TYPE: Input
 VARIABLES DESCRIPTION:   The ECME number is generated in ePharmacy.  It is
 either 7 digits or 12 digits depending upon the NCPDP version number being
 used by the payer.  This number passed in may or may not contain leading
 zeros.  A "+" is performed on the ECME# first thing within this API.  
VARIABLES: $$RXNUM                      TYPE: Output
 VARIABLES DESCRIPTION:   The value of the extrinsic function call is the
 internal RX ien (pointer to file# 52).  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: MAR 15, 2007

NUMBER: 4971                            IA #: 4971
  FILE NUMBER: 36                       GLOBAL ROOT: DIC(36
  CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4971
  ID: DIC(36
GLOBAL REFERENCE: DIC(36,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Name of the INSURANCE COMPANY. This name will be sent
 with the extract depending on the TYPE OF COVERAGE.  
FIELD NUMBER: .13                       FIELD NAME: TYPE OF COVERAGE
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Pointer to the TYPE OF COVERAGE file (#355.2). This is
 the type of insurance coverage. NPI extract is interested in all entries of
 type BLUE CROSS or BLUE SHIELD.  
 GENERAL DESCRIPTION:   The NPI Extract extracts IB insurance company data
 during its run.  The extract was developed as part of the HIPAA NPI project.
 The NAME and TYPE OF COVERAGE need to be extracted as part of the NPI Extract 
 process.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NPI
KEYWORDS: Extract
KEYWORDS: practitioner
KEYWORDS: ID
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   The NPI Extract needs to extract the NAME and TYPE OF
 COVERAGE from the INSURANCE COMPANY file (#36). This is a read-only action and
 does not modify any fields in the file.  
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4972                            IA #: 4972
  FILE NUMBER: 355.2                    GLOBAL ROOT: IBE(355.2
  CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA4972
  ID: IBE(355.2
GLOBAL REFERENCE: IBE(355.2,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Name of the TYPE OF COVERAGE. The NPI extract is
 interested in all INSURANCE COMPANY entries that are of type BLUE CROSS or
 BLUE SHIELD.  
 GENERAL DESCRIPTION:   The NPI Extract extracts IB insurance coverage data
 during its run.  The extract was developed as part of the HIPAA NPI project.
 The NAME needs to be examined as part of the NPI Extract process.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NPI
KEYWORDS: Extract
KEYWORDS: practitioner
KEYWORDS: ID
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   The NPI Extract needs to examine the NAME from the TYPE
 OF INSURANCE COVERAGE file (#355.2). This is a read-only action and does not
 modify any fields in the file.  
  DATE ACTIVATED: MAR 04, 2007

NUMBER: 4973                            IA #: 4973
  DATE CREATED: APR 23, 2007            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  ROUTINE: MAGDHLS
  NAME: Creation of a HL7 PID & PV1 segments (V2.4)
  ID: MAGDHLS
 GENERAL DESCRIPTION:   The VistA Imaging development team will provide a
 function that creates both PID & PV1 segments that are backwards compatible to
 version 2.4 of Health Level Seven (HL7). The PID & PV1 segments are fixed
 segments; the Imaging development team will determine the fields to be defined
 for these segments in accordance with the 'Integrating the Healthcare
 Enterprise Radiology Technical Framework' specifications for order (ORM) 
 transactions.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: HL7
KEYWORDS: Health Level Seven
KEYWORDS: HL7 Imaging
KEYWORDS: HL7 Radiology
KEYWORDS: HL7 functions
KEYWORDS: HL7 segment generators
KEYWORDS: HL7 PV1
KEYWORDS: HL7 PID
COMPONENT/ENTRY POINT: $$PV1
 COMPONENT DESCRIPTION:   The VistA Imaging development team will provide a
 function that creates the PV1 segment in accordance with the 'Integrating the
 Healthcare Enterprise Radiology Technical Framework' specifications for HL7
 order (ORM) transactions.  
  
 The input variables are: 
 ------------------------
 XDFN   - The Internal Entry Number (IEN) of the patient.  XEVN   - The HL7
 event type of this message.  XEVNDT - The radiology order event date/time.
 (FileMan format) XYMSG  - The name of the array defining the HL7 segment.  
  
 The output variable is: 
 -----------------------
 @XYMSG - The input array specified by the radiology developer. This array will
 assume the value of the PID segment. 
VARIABLES: XDFN                         TYPE: Input
 VARIABLES DESCRIPTION:   The Internal Entry Number (IEN) of the patient.  
VARIABLES: XEVN                         TYPE: Input
 VARIABLES DESCRIPTION:   This variable identifies the event type of this
 message.  
VARIABLES: XEVNDT                       TYPE: Input
 VARIABLES DESCRIPTION:   This variable identifies the exam date/time of when
 the case was examined, registered, or cancelled.  (internal FileMan format) 
VARIABLES: XYMSG                        TYPE: Both
 VARIABLES DESCRIPTION:   As an input variable XYMSG is set to the name of the
 array in which to set to the value of the PV1 segment. As an output variable
 the variable passed in the XYMSG parameter is set to the value of the PV1
 segment.  
COMPONENT/ENTRY POINT: $$PID
 COMPONENT DESCRIPTION:   The VistA Imaging development team will provide a
 function that creates the PID segment in accordance with the 'Integrating the
 Healthcare Enterprise Radiology Technical Framework' specifications for HL7
 order (ORM) transactions.  
  
 The input variables are: 
 ------------------------
 XDFN   - The Internal Entry Number (IEN) of the patient.  XYMSG  - The name of
 the array defining the HL7 segment.  
  
 The output variable is: 
 -----------------------
 @XYMSG - The input array specified by the radiology developer. This array will
 assume the value of the PID segment.  
VARIABLES: XDFN                         TYPE: Input
 VARIABLES DESCRIPTION:   XDFN   - The Internal Entry Number (IEN) of the
 patient.  
VARIABLES: XYMSG                        TYPE: Both
 VARIABLES DESCRIPTION:   As an input variable XYMSG is set to the name of the
 array to which to add the value of the PID segment. As an output variable, the
 array represented by the variable passed in the XYMSG parameter has a subtree
 added to it containing the elements of the PID segment.  
  
 (the array may be multiply subscripted because the segment can exceed two 
 hundred forty-five characters in length) 
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 4974                            IA #: 4974
  DATE CREATED: FEB 06, 2007            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Private                        TYPE: Other
  NAME: PRIVATE VPFS consumption of VistALink API
 GENERAL DESCRIPTION:   The VPFS package consumes the VistALink Service. The
 objects and methods used by VPFS, are detailed below: 
  
  
  
 Package gov.va.med.exception: 
  
 -----------------------------
  
 FoundationsException: 
  
     (catch only) 
  
  
  
 Package gov.va.med.vistalink.adapter.cci: 
  
 -----------------------------------------
  
 VistaLinkConnection: 
  
     setTimeout(int) 
  
     executeRPC(RpcRequest) 
  
     close() 
  
  
  
 VistaLinkConnectionFactory: 
  
     getConnection(VistaLinkDuzConnectionSpec) 
  
  
  
 VistaLinkDuzConnectionSpec: 
  
     VistaLinkDuzConnectionSpec(String, String) 
  
  
  
 Package gov.va.med.vistalink.institution: 
  
 -----------------------------------------
  
 InstitutionMapNotInitializedException: 
  
     (catch only) 
  
  
  
 InstitutionMappingDelegate: 
  
     getJndiConnectorNameForInstitution(String) 
  
  
  
 InstitutionMappingNotFoundException: 
  
     (catch only) 
  
  
  
 Package gov.va.med.vistalink.rpc: 
  
 ---------------------------------
  
 RpcFaultException: 
  
     (catch only) 
  
  
  
 RpcResponse: 
  
     getResults() 
  
  
  
 RpcRequest: 
     setUseProprietaryMessageFormat(boolean) 
  
     setRpcContext(String) 
  
     setRpcClientTimeOut(int) 
  
     setRpcName(String) 
  
     getParams() 
  
  
  
 RpcRequestFactory: 
  
     getRpcRequest() 
  
  
  
 RpcRequestParams: 
  
     setParam(int, String, Object) 
  STATUS: Expired
KEYWORDS: VISTALINK
KEYWORDS: PRIVATE
KEYWORDS: API
KEYWORDS: J2EE
SUBSCRIBING PACKAGE: INTEGRATED PATIENT FUNDS
  DATE ACTIVATED: MAR 06, 2007

NUMBER: 4975                            IA #: 4975
  FILE NUMBER: 660                      GLOBAL ROOT: RMPR(660
  CUSTODIAL PACKAGE: PROSTHETICS        USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PROSTHETICS FILE 660            ID: RMPR(660
GLOBAL REFERENCE: RMPR(660,C
FIELD NUMBER: n/a                       FIELD NAME: n/a
  LOCATION: n/a                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the 'C' cross-reference for file 660, which
 indexes based on patient's DFN.  
 GLOBAL DESCRIPTION:   This is the 'C' cross-reference for file 660, which
 indexes based on patient's DFN.  
GLOBAL REFERENCE: RMPR(660,D0,0
FIELD NUMBER: .01                       FIELD NAME: ENTRY DATE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TYPE OF TRANSACTION
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: QTY
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: STATION
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: DELIVERY DATE
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: TOTAL COST
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: FORM REQUESTED ON
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,1
FIELD NUMBER: 4.5                       FIELD NAME: PSAS HCPCS
  LOCATION: 1;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,10
FIELD NUMBER: 8.5                       FIELD NAME: TYPE OF REQUEST
  LOCATION: 10;5                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   THE SPINAL CORD PACKAGE NEEDS ACCESS TO DATA FIELDS
 FROM THE PROSTHETICS FILE #660 (RECORD OF PROS APPLIANCE/REPAIR) AS WELL AS
 USE OF PROSTHETICS API PSASHCPC^RMPOPF.  ACCESS WILL BE READ-ONLY FOR
 REPORTING PURPOSES.  
  STATUS: Active
KEYWORDS: PROSTHETICS
KEYWORDS: RECORD OF PROS APPLIANCE
KEYWORDS: RMPR(660
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
 SUBSCRIBING DETAILS:   ASIDE FROM THE FIELDS FROM 660 THAT ARE LISTED WITHIN
 THIS DBIA, SPINAL CORD REQUIRES ACCESS TO THE PROSTHETICS API PSASHCPC^RMPOPF
 TO RETRIEVE THE TEXT FOR THE PROSTHETICS HCPCS.  
  DATE ACTIVATED: MAR 06, 2007

NUMBER: 4976                            IA #: 4976
  DATE CREATED: FEB 23, 2007            CUSTODIAL PACKAGE: 757
  USAGE: Controlled Subscription        TYPE: Other
  NAME: Patient Service Construct java components
 GENERAL DESCRIPTION:   Patient Service Construct is a Veterans Health
 Information Systems and Technology Architecture (VistA) re-engineering project
 based on the Java technologies.  Patient Service is a composite business
 service that provides a broad range of high-level patient administrative data. 
 The data is based on access to the individual business services such as 
 Patient Demographics, Eligibility/Enrollment, and Patient Identification, 
 which serve as authoritative sources for that data.  For those applications
 that have been re-engineered, all needs to retrieve patient administrative
 data through a common business service will be met.  The Patient Service
 Construct functionality is invisible to existing M VistA applications.  
  
 PSC provides a CAIP compliant delegate (IPatientServiceDelegate) for 
 applications to use that has two main API s, retrievePatientData 
 (IPatientServiceRequest) and retrieveMultiplePatients(IPatientService Request,
 String[]) where the array of strings is an array of ICN values.  The delegate
 accesses the patient data through a session fagade EJB.  It is the
 responsibility of the calling application to instantiate the EJB in an
 application server for its use. The data is retrieved at the specified VistA
 location through the session fagade utilizing VistaLink.  The 
 IPatientServiceRequest must contain the necessary information to complete the
 task.  
  
 This integration agreement documents the APIs provided by Patient Service 
 Construct.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: retrievePatientData
 COMPONENT DESCRIPTION:   When retrieving data for one patient, either of the
 two business delegate interface methods may be used.  
  
 If using retrievePatientData(IPatientServiceRequestpsReq), the interface to
 the PatientId class should be used to instantiate a PatientId object with an
 ICN.  The PatientId object should then be set in the PatientServiceRequest.  
  
 The delegate interface method retrieveMultiplePatients(IPatientService 
 RequestpsReq,String[],icnArray) may also be used to retrieve an individual 
 patient by declaring an icnArray with only one element.  
VARIABLES: IPatientServiceRequest       TYPE: Input
 VARIABLES DESCRIPTION:   IPatientServiceRequest: 
  
 IPatientId pid = new PatientId(ICN) or IPatientId pid = new
 PatientId(ICN_V_ICN checksum) 
      When instantiating with an ICN, the checksum is optional.  
VARIABLES: services java.util.List      TYPE: Input
 VARIABLES DESCRIPTION:   services java.util.List of RequestedServices: 
  
 Patient Service Construct permits the retrieval of as many of the datasets as
 are required by the client in one call to the business delegate. This is true
 for batch identifier processing as well as single ICN processing.  
 PatientServiceRequest contains a java.util.List of gov.va.med.patient 
 admin.common.RequestedServices. RequestedServices is an extension of an 
 integer Enumeration class.  
  
 Valid values are: 
                                         
 RequestedServices.PRIMARY_DEMOGRAPHICS   
 RequestedServices.SECONDARY_DEMOGRAPHICS 
 RequestedServices.TERTIARY_DEMOGRAPHICS RequestedServices.ADDRESS_DEMOGRAPHICS 
 RequestedServices.CONTACT_DEMOGRAPHICS RequestedServices.ADT 
 RequestedServices.ENROLLMENT_ELIGIBILITY 
 RequestedServices.INCOMPETENCE_INFORMATION 
VARIABLES: IPatientServiceTO            TYPE: Output
 VARIABLES DESCRIPTION:   IPatientServiceTO: 
  
 The single identifier Patient Service Construct delegate method returns to 
 consuming applications, gov.va.med.patientadmin.transfer.  
 IpatientServiceTO.java, an interface to a J2EE transfer object. 
 IPatientServiceTO is the interface to a container object that contains 
 dataset-specific transfer objects for each of the eight datasets that may be
 retrieved as well as an error message attribute.  
  
 In addition to the expected elements contained within the individual transfer
 objects, IPatientServiceTO will always return an IIdentifier and IInstitution,
 which are interfaces to corresponding classes.  
  
         IIdentifier 
         IInstitution 
         IPrimaryDemographicsTO 
         ISecondaryDemographicsTO 
         ITertiaryDemographicsTO 
         IAddressDemographicsTO 
         IContactDemographicsTO 
         IADTTO 
         IEnrollmentEligibilityTO 
         IIncompetenceInformationTO 
COMPONENT/ENTRY POINT: retrieveMultiplePatients
 COMPONENT DESCRIPTION:   The delegate interface method 
 retrieveMultiplePatients(IPatientServiceRequestpsReq,String[],icnArray) may
 also be used to retrieve an individual patient by declaring an icnArray with
 only one element.  
VARIABLES: IPatientServiceRequest       TYPE: Input
 VARIABLES DESCRIPTION:   IPatientServiceRequest: 
  
 IPatientId pid = new PatientId(ICN) or IPatientId pid = new
 PatientId(ICN_V_ICN checksum) 
      When instantiating with an ICN, the checksum is optional.  
VARIABLES: services.java.util.List      TYPE: Input
 VARIABLES DESCRIPTION:   services java.util.List of RequestedServices: 
  
 Patient Service Construct permits the retrieval of as many of the datasets as
 are required by the client in one call to the business delegate. This is true
 for batch identifier processing as well as single ICN processing.  
 PatientServiceRequest contains a java.util.List of 
 gov.va.med.patientadmin.common.RequestedServices. RequestedServices is an 
 extension of an integer Enumeration class.  
  
 Valid values are: 
  
 RequestedServices.PRIMARY_DEMOGRAPHICS 
 RequestedServices.SECONDARY_DEMOGRAPHICS 
 RequestedServices.TERTIARY_DEMOGRAPHICS RequestedServices.ADDRESS_DEMOGRAPHICS 
 RequestedServices.CONTACT_DEMOGRAPHICS RequestedServices.ADT 
 RequestedServices.ENROLLMENT_ELIGIBILITY 
 RequestedServices.INCOMPETENCE_INFORMATION 
VARIABLES: IPatientServiceTO[]          TYPE: Output
 VARIABLES DESCRIPTION:   IPatientServiceTO[]:  
  
 The single identifier Patient Service Construct delegate method returns to 
 consuming applications, gov.va.med.patientadmin.transfer.  
 IpatientServiceTO.java, an interface to a J2EE transfer object.  An array of
 Patient Service Transfer objects is returned to consumers when using batch ICN
 processing.  IPatientServiceTO is the interface to a container object that
 contains dataset-specific transfer objects for each of the eight datasets that
 may be retrieved as well as an error message attribute.  
  
 In addition to the expected elements contained within the individual transfer
 objects, IPatientServiceTO will always return an IIdentifier and IInstitution,
 which are interfaces to corresponding classes.  
  
      IIdentifier 
      IInstitution 
      IPrimaryDemographicsTO        
      ISecondaryDemographicsTO 
      ITertiaryDemographicsTO 
      IAddressDemographicsTO 
      IContactDemographicsTO 
      IADTTO 
      IEnrollmentEligibility 
      IIncompetenceInformationTO 
SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM
SUBSCRIBING PACKAGE: INTEGRATED PATIENT FUNDS

NUMBER: 4977                            IA #: 4977
  DATE CREATED: FEB 15, 2007            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  ROUTINE: MAGDHLS
  NAME: Creation of a HL7 PID segment (V2.4)
  ID: MAGDHLS
 GENERAL DESCRIPTION:   The VistA Imaging development team will provide a
 function that creates a PID segment that is backwards compatible to version
 2.4 of Health Level Seven (HL7). The PID segment is a fixed segment; the
 Imaging development team will determine the fields to be defined for this
 segment in accordance with the 'Integrating the Healthcare Enterprise
 Radiology Technical Framework' specifications for order (ORM) transactions.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
  EXPIRATION DATE: FEB 15, 2007
KEYWORDS: Health Level Seven
KEYWORDS: HL7 Imaging
KEYWORDS: HL7 Radiology
KEYWORDS: HL7 functions
KEYWORDS: HL7 segment generation
KEYWORDS: HL7 PID
COMPONENT/ENTRY POINT: $$PID
 COMPONENT DESCRIPTION:   The input variables are: 
 ------------------------
 XDFN - The Internal Entry Number (IEN) of the patient.  XYMSG - name of array
 to which to add message elements 
  
 The output variable is: 
 -----------------------
 XYMSG - The input array specified by the radiology developer set to the PID
 segment elements.  
VARIABLES: XDFN                         TYPE: Input
 VARIABLES DESCRIPTION:   The Internal Entry Number (IEN) of the patient.  
VARIABLES: XYMSG                        TYPE: Both
 VARIABLES DESCRIPTION:   As an input variable XYMSG is set to the name of the
 array set to the PID segment elements. As an output variable XYMSG is set to
 the value of the PID segment elements (may be multiply subscripted because the
 segment may exceed two hundred forty-five characters in length).  

NUMBER: 4978                            IA #: 4978
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19
  DATE CREATED: MAY 01, 2007            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: Add option to XUKERNEL          ID: DIC(19
GLOBAL REFERENCE: DIC(19,IEN,10)
FIELD NUMBER: 10                        FIELD NAME: MENU
  LOCATION: 10;0                        ACCESS: Write w/Fileman
FIELD NUMBER: 25                        FIELD NAME: ROUTINE
  LOCATION: 25;E1,245                   ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   This agreement allows the subscribing package access to
 the specified fields in the Option (#19) file.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 4979                            IA #: 4979
  FILE NUMBER: 8989.3                   GLOBAL ROOT: XTV(8989.3
  DATE CREATED: MAY 01, 2007            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: Default Directory for HFS       ID: XTV(8989.3
GLOBAL REFERENCE: XTV(8989.3,IEN)
FIELD NUMBER: 320                       FIELD NAME: DEFAULT DIRECTORY FOR HFS
  LOCATION: DEV;1                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA allows the subscriber(s) to reference the
 Default Directory for HFS (#320) field in the Kernel Systems Parameter
 (#8989.3) file.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 4980                            IA #: 4980
  FILE NUMBER: 3.8                      GLOBAL ROOT: XMB(3.8
  DATE CREATED: MAY 01, 2007            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  NAME: Remote Member (#3.812) multiple
  ID: XMB(3.8
GLOBAL REFERENCE: XMB(3.8,IEN,6)
FIELD NUMBER: 12                        FIELD NAME: MEMBERS - REMOTE
  LOCATION: 6;0                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA allows the subscribing package to reference the
 Remote Member (#3.812) multiple in the Mail Group (#3.8) file.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 4981                            IA #: 4981
  DATE CREATED: MAY 01, 2007            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  ROUTINE: XUMFXHL7                     NAME: Access to XUMFXHL7 parsing routine
  ID: XUMFXHL7
 GENERAL DESCRIPTION:   This agreement allows the subscribing package access to
 routine XUMFXHL7 used to parse HL7 segments.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SEGPRSE
 COMPONENT DESCRIPTION:   This entry point parses a HL7 segment by field
 separator.  
  
 Notes  : OUTARR is initialized (KILLed) on entry 
        : Assumes SEGMENT and OUTARR are defined and valid 
VARIABLES: SEGMENT                      TYPE: Input
 VARIABLES DESCRIPTION:   Input  : SEGMENT - Array containing HL7 segment to
 parse 
                    (full global ref)                 
                    SEGMENT = First 245 characters of segment 
                    SEGMENT(1..n) = Continuation nodes 
                         OR 
                    SEGMENT(x) = First 245 characters of segment 
                    SEGMENT(x,1..n) = Continuation nodes 
VARIABLES: OUTARR                       TYPE: Both
 VARIABLES DESCRIPTION:   OUTARR - Array to put parsed segment into (full
 global ref) 
  
 Output:  OUTARR(0) = Segment name 
          OUTARR(seq#) = Data (first 245 characters) 
          OUTARR(seq#,1..n) Continuation nodes 
VARIABLES: FS                           TYPE: Input
 VARIABLES DESCRIPTION:   FS - HL7 field separator (defaults to ^) (1
 character) 
COMPONENT/ENTRY POINT: SEQPRSE
 COMPONENT DESCRIPTION:   Parses HL7 component by sequence.  
  
 Notes  : OUTARR is initialized (KILLed) on entry 
        : Assumes SEQDATA and OUTARR are defined and valid 
VARIABLES: SEQDATA                      TYPE: Input
 VARIABLES DESCRIPTION:   Input  : SEQDATA - Array containing seq to parse
 (full global ref) 
                    SEQDATA = First 245 characters of sequence 
                    SEQDATA(1..n) = Continuation nodes 
                         OR 
                    SEQDATA(x) = First 245 characters of sequence 
                    SEQDATA(x,1..n) = Continuation nodes 
VARIABLES: OUTARR                       TYPE: Both
 VARIABLES DESCRIPTION:   OUTARR - Array to put parsed sequence into (full
 global ref) 
  
 Output : None 
          OUTARR(rep#,comp#) = Data (first 245 characters) 
          OUTARR(rep#,comp#,1..n) = Continuation nodes 
VARIABLES: ENCODE                       TYPE: Input
 VARIABLES DESCRIPTION:   ENCODE - HL7 encoding characters (defaults to ~|\&)
 (4 chars) 

NUMBER: 4982                            IA #: 4982
  DATE CREATED: MAY 01, 2007
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORMVBEC
  NAME: Lab access to ORMVBEC           ID: ORMVBEC
 GENERAL DESCRIPTION:   The purpose of this integration agreement is to allow
 the Lab package to use the EN entry point in the ORMVBEC routine.  This would
 be called by the LR7OVB routine during the VBECS order completion process.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CPRS
KEYWORDS: LAB
KEYWORDS: VBEC
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This entry point allows the VistA Blood Establishment
 Computer System (VBECS) to use HL7 order update messages to complete orders
 created through the Blood Bank Accession Area.  
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: FEB 26, 2014

NUMBER: 4983                            IA #: 4983
  FILE NUMBER: 9.69                     GLOBAL ROOT: XPD(9.69
  DATE CREATED: MAY 01, 2007            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: Kernel Hash file (#9.69)        ID: XPD(9.69
GLOBAL REFERENCE: XPD(9.69,IEN,1)
FIELD NUMBER: .01                       FIELD NAME: SITE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: HASH
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 4984                            IA #: 4984
  FILE NUMBER: 8932.1                   GLOBAL ROOT: USC(8932.1
  DATE CREATED: MAY 01, 2007            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: Person Class (#8932.1)          ID: USC(8932.1
GLOBAL REFERENCE: USC(8932.1,IEN,0)
FIELD NUMBER: .01                       FIELD NAME: PROVIDER TYPE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: CLASSIFICATION
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: AREA OF SPECIALIZATION
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: VA CODE
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: SPECIALTY CODE
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: USC(8932.1,IEN,90002)
FIELD NUMBER: 90002                     FIELD NAME: INDIVIDUAL/NON
  LOCATION: 90002;2                     ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This agreement provides access to the specified fields
 in the Person Class (#8932.1) file.  
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   The Virtual Patient Record (VPR) application is working
 on patch VPR*1*4 in support of two of its client app's, JLV and VLER. They
 have requested that VPR add information about a provider's specialty area to
 our data extract rpc.  
  
 Kernel developers have granted VPR access to the following two Kernel-owned
 ICR's: 
   4911   $$TAXIND^XUSTAX 
   4984   Person Class (#8932.1) 
  
 VPR will first call $$TAXIND^XUSTAX to get the provider's current Person Class
 ien and the corresponding X12 code; using the ien, VPR will read the Provider
 Type (.01), Classification (1), and Area of Specialization (2) fields from the
 Person Class file #8932.1. 
                    
 VPR added as a subscriber on 1/30/15.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   As part of patch OR*3*519, CPRS will add the capability
 of querying the PDMP. As part of the query, we need to send the user's person
 class information. However, we need to filter out non-individual entries that 
 have an INDIVIDUAL/NON (#90002) value of "N". We therefore need FileMan read
 access to that field.  
  DATE ACTIVATED: JUN 17, 2015

NUMBER: 4985                            IA #: 4985
  DATE CREATED: MAY 02, 2007            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  ROUTINE: XUSEREVN                     NAME: XUSEREVN
  ID: XUSEREVN
 GENERAL DESCRIPTION:   XUSEREVN creates PMU/B04, B05 and B06 HL7 messages
 based on the event that has occurred in the New Person (#200) file record.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ACT
 COMPONENT DESCRIPTION:   ACT^XUSEREVN creates a B04 HL7 message.  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   DUZ = New Person (#200) file internal entry number 

NUMBER: 4986                            IA #: 4986
  DATE CREATED: MAY 04, 2007            CUSTODIAL PACKAGE: 1
  USAGE: Supported                      TYPE: Routine
  ROUTINE: %DTC
  NAME: Temporary DBIA for use of TT in %DTC by VistA Imaging
  ID: %DTC
 GENERAL DESCRIPTION:   The purpose of this DBIA is to allow VistA Imaging to
 continue using the entry point TT^%DTC (convert $H-date into FileMan date) 
 until a patch is released that replaces all subroutine calls in Imaging 
 software that are currently to entry points in ^%DTC to be references to
 function-calls to entry points in XLFDT.  
  
 It is expected that this patch will be released before the end of 2007.  
  
  STATUS: Pending                       DURATION: Next Version
  EXPIRATION DATE: DEC 31, 2007         GOOD ONLY FOR VERSION: 3.0
COMPONENT/ENTRY POINT: TT
 COMPONENT DESCRIPTION:   Converts a $H format date to a VA FileMan date.  
  
VARIABLES: %                            TYPE: Output
 VARIABLES DESCRIPTION:   Number of days in current year.  
  
VARIABLES: %H                           TYPE: Both
 VARIABLES DESCRIPTION:   A $H format date/time.  Required and returned.  
  
VARIABLES: $I(1)                        TYPE: Output
 VARIABLES DESCRIPTION:   Month number.  
  
VARIABLES: %I(2)                        TYPE: Output
 VARIABLES DESCRIPTION:   Day of month.  
  
VARIABLES: %I(3)                        TYPE: Output
 VARIABLES DESCRIPTION:   Years since 1700.  
  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   The date (only) in VA FileMan format.  
  

NUMBER: 4987                            IA #: 4987
  DATE CREATED: MAY 04, 2007            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBRSUTL
  NAME: IB BILLING DATA API             ID: IBRSUTL
 GENERAL DESCRIPTION:   This set of API's provide billing data related to
 Outpatient Encounters and allows the update of an encounters billable status. 
 These are implemented to support the Automated Service Connected Designation
 (ASCD) project.  This project may potentially update an encounters Service 
 Connected designation after the encounter's check-out.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OUTPATIENT
KEYWORDS: ASCD
KEYWORDS: ENCOUNTER
COMPONENT/ENTRY POINT: RNBU(encounter,change)
 COMPONENT DESCRIPTION:   Update an Outpatient Encounters Claims Tracking
 Reason Not Billable.  When an encounters Service Connected designation is
 changed after check-out this function may be used to update the encounters
 Claims Tracking Reason Not Billable.  
                 
 When the encounter is changed from NSC to SC the Claims Tracking record is
 updated to non-billable only if it was identified as billable.  When the
 encounter is changed from SC to NSC the Claims Tracking record is update to
 billable only if it was identified as non-billable due to SC Treatment.  
VARIABLES: encounter                    TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Outpatient Encounter (#409.68) 
VARIABLES: change                       TYPE: Input
 VARIABLES DESCRIPTION:   1 - Encounter changed from NSC to SC              2 -
 Encounter changed from SC to NSC 
VARIABLES: $$RNBU                       TYPE: Output
 VARIABLES DESCRIPTION:   Value returned by the function representing:      1 -
 Claims Tracking record updated to non-billable If no Reason Not Billable then
 SC TREATMENT added 2 - Claims Tracking record updated to billable      If
 Reason Not Billable SC TREATMENT then deleted  0 - No change 
COMPONENT/ENTRY POINT: CT(encounter)
 COMPONENT DESCRIPTION:   Retrieve an Outpatient Encounters Claims Tracking
 record.  
VARIABLES: encounter                    TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Outpatient Encounter (#409.68) 
VARIABLES: $$CT                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns IEN of encounter in Claims Tracking (#356) or
 returns null if no record found 
COMPONENT/ENTRY POINT: FIRST(encounter)
 COMPONENT DESCRIPTION:   Check if an Outpatient Encounter is billable for
 First Party.  This function checks various elements related to the patient and
 encounter.  Not all billable elements are checked, for example encounter
 Classifications (SC/NSC) are not checked.  
VARIABLES: encounter                    TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Outpatient Encounter (#409.68) 
VARIABLES: $$FIRST                      TYPE: Output
 VARIABLES DESCRIPTION:   Returns encounter First Party billable status:    1 -
 if encounter is billable to patient           0 ^ reason encounter not
 billable 
COMPONENT/ENTRY POINT: THIRD(encounter)
 COMPONENT DESCRIPTION:   Check if an Outpatient Encounter is billable for
 Third Party.  This function checks various elements related to the patient and
 encounter.  Not all billable elements are checked, for example encounter
 Classifications (SC/NSC) and patient insurance are not checked.  
VARIABLES: encounter                    TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Outpatient Encounter (#409.68) 
VARIABLES: $$THIRD                      TYPE: Output
 VARIABLES DESCRIPTION:   Returns encounter Third Party billable status:    1 -
 if encounter is billable to insurance         0 ^ reason encounter not
 billable 
COMPONENT/ENTRY POINT: FPBILL(encounter)
 COMPONENT DESCRIPTION:   Retrieve an Outpatient Encounters First Party bill
 and charge.  The AR Bill number/transaction are only defined once charge is 
 passed to AR so a valid returned charge may only have a Total Charge defined.  
VARIABLES: encounter                    TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Outpatient Encounter (#409.68) 
VARIABLES: $$FPBILL                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns encounters patient charge data if found: AR
 BILL NUMBER (#350,.11) ^ AR TRANSACTION NUMBER (#350,.12) ^ TOTAL CHARGE
 (#350,.07)             or returns null if no non-cancelled charge found 
COMPONENT/ENTRY POINT: TPBILL(encounter)
 COMPONENT DESCRIPTION:   Retrieve an Outpatient Encounters Third Party bills.  
 Encounters may have multiple Third Party bills.  This function returns a
 string of all Third Party bills that have not been cancelled and have one of
 the encounters procedures assigned.  
VARIABLES: encounter                    TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Outpatient Encounter (#409.68) 
VARIABLES: $$TPBILL                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns encounters third party bill numbers:    BILL
 NUMBER (#399,.01)^BILL NUMBER (#399,.01)^...  or returns null if no
 non-cancelled bills found 
COMPONENT/ENTRY POINT: TPCHG(encounter)
 COMPONENT DESCRIPTION:   Calculate encounter's potential Third Party charges. 
 Based on encounters procedures and Reimbursable Insurance charges.  
VARIABLES: encounter                    TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Outpatient Encounter (#409.68) 
VARIABLES: $$TPCHG                      TYPE: Output
 VARIABLES DESCRIPTION:   Returns potential Third Party charges for the 
 procedures assigned to an encounter:            Total Institutional ^ Total
 Professional charges or returns 0 if not billable or no charges found 
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: SEP 19, 2007

NUMBER: 4988                            IA #: 4988
  FILE NUMBER: 19                       GLOBAL ROOT: DIC
  DATE CREATED: MAY 08, 2007            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: EDIT LOCK IN PCMM OPTIONS.      ID: DIC
GLOBAL REFERENCE: DIC(19
FIELD NUMBER: 3                         FIELD NAME: LOCK
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The EWL/PCMM enhancement team requests permission to
 remove and/or delete locks on the following PCMM Options. This requires that
 access to the OPTION file (#19), field #3 (LOCK). In addition, the team
 request permission to replace the SCMC PCMM EWL MENU option with the standard
 scheduling SD WAIT LIST MENU option on the SCMC PCMM MAIN MENU option. These
 changes will be executed with standard VA Fileman calls (DIE,DICN and DIK).
 The routine will be a post init on patch SD*5.3*498 and will be deleted
 following the completion of the installation. 
  
 The following OPTIONS will have the locks removed.  
            
      SCMC EXTENDED REPORT 
      SCMC FLAGGED 
      SCMC INACTIVATED REPORT 
      SC PCMM DIRECT PC FTEE 
      SCMC PRACTITIONER FLAGGED 
      SCMC PC STAFF AUTO INACTIVATE 
      SCMC PCMM MAIN MENU     
  
 The following OPTIONS will have the lock SC PCMM SETUP.  
  
      SCMC PCMM NIGHTLY TASK 
      SCMC RETRANSMIT 
      SCMC PCMM ERR CODE REPORT 
      SCMC PCMM TRANS ERROR REPORT 
      SCMC EXTEND A PATIENT 
      
 The following OPTION will have the lock SCMC PCMM RETRANSMIT.    
      
      SCMC PCMM TRANS ERROR PROC 
      
 The following OPTION will be deleted from the SCMC PCMM MAIN MENU.  
  
      SCMC PCMM EWL MENU 
      
 The following OPTION will be added the SCMC PCMM MAIN MENU.          
  
      SD WAIT LIST MENU     
  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: MAY 07, 2008
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 4989                            IA #: 4989
  DATE CREATED: MAY 10, 2007            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LR7OSAP4
  NAME: LR7OSAP4- GET AP RESULTS        ID: LR7OSAP4
 GENERAL DESCRIPTION:   Routine LR7OSAP4 to get Anatomic Path results from
 either TIU or lab files.  
          ;
 EN(LRX,LRDFN,LRSS,LRI)        ;Get Anatomic Path results from either TIU or
 Lab files 
          ; LRX is the global where the output is placed. Calling package is
 resp onsible for cleaning this up 
          ; LRDFN = Lab Patient ID 
          ; LRSS = Lab Subscript 
          ; LRI = Inverse Date/Time from ^LR(LRDFN,LRSS,LRIDT) 
  
  STATUS: Active
KEYWORDS: LR7OSAP4
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   LR7OSAP4 
          ;
 EN(LRX,LRDFN,LRSS,LRI)        ;Get Anatomic Path results from either TIU or
 Lab files 
          ; LRX is the global where the output is placed. Calling package is
 resp onsible for cleaning this up 
          ; LRDFN = Lab Patient ID 
          ; LRSS = Lab Subscript 
          ; LRI = Inverse Date/Time from ^LR(LRDFN,LRSS,LRIDT) 
  
VARIABLES: LRX                          TYPE: Both
 VARIABLES DESCRIPTION:   LRX is the global where the output is placed.  
  
VARIABLES: LRDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Lab Patient ID (File 63 IEN) 
  
VARIABLES: LRSS                         TYPE: Input
 VARIABLES DESCRIPTION:   Lab Subscript- ie. SP for Surgical Pathology 
                    EM for Electron Microscopy 
                    CY for Cytology 
  
VARIABLES: LRI                          TYPE: Input
 VARIABLES DESCRIPTION:   Inverse Date/Time from ^LR(LRDFN,LRSS,LRIDT) 
  
  DATE ACTIVATED: MAR 14, 2008

NUMBER: 4990                            IA #: 4990
  DATE CREATED: MAY 10, 2007            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDSCAPI
  NAME: SERVICE CONNECTED AUTOMATION    ID: SDSCAPI
 GENERAL DESCRIPTION:   This routine supports the Automated Service Connected
 Designation (ASCD) project. It automates the service connected (SC) value for
 outpatient encounters.  It also determines whether an encounter should be sent
 to the ASCD file #409.48 for additional review.  The evaluation of the SC
 value is based on the mapping of the patient rated disability codes and ICD
 codes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ASCD
KEYWORDS: SERVICE
KEYWORDS: CONNECT
KEYWORDS: SDSCAPI
KEYWORDS: OUTPATIENT
KEYWORDS: ENCOUNTER
COMPONENT/ENTRY POINT: $$SC(SDFN,SDXS,SDENC,SDVST)
 COMPONENT DESCRIPTION:   This entry point determines whether a specific
 diagnosis code or codes is service connected (SC) or non-service connected
 (NSC). This determination is based on the mapping of the patient's rated
 disability and ICD codes.  
VARIABLES: SDFN                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of PATIENT file (#2). [Required, if SDENC or
 SDVST undefined].  
  
VARIABLES: SDXS                         TYPE: Input
 VARIABLES DESCRIPTION:   Diagnosis code array (passed by reference) - array
 format:  SDXS(ICD ien) = "" [Optional, if SDENC defined] 
VARIABLES: SDENC                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of OUTPATIENT ENCOUNTER file (#409.68) [Optional] 
  
VARIABLES: SDVST                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of VISIT file (#9000010 [Optional] 
  
VARIABLES: $$SDFILEOK                   TYPE: Output
 VARIABLES DESCRIPTION:   SC flag^SC description^VBA/ICD match^Review 
   SC flag:         1 = Service Connected (SC) 
                    0 = Non-Service Connected (NSC) 
                   "" = (null) - could not be determined 
   SC description: SC = Service Connected 
                  NSC = Non-Service Connected 
   VBA/ICD match:   1 = yes 
                    0 = no 
   Review:          1 = send to review 
                    0 = don't send to review 
COMPONENT/ENTRY POINT: $$ST(SDENC,SDXS)
 COMPONENT DESCRIPTION:   This entry point screens each diagnosis code for an
 outpatient encounter to determine if additional review for the service
 connected (SC) value is needed.  The SDSC SERVICE CONNECTED CHANGES (#409.48)
 file is used to queue encounters needing further review.  
  
VARIABLES: SDENC                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of OUTPATIENT ENCOUNTER (#409.68) file [Required] 
  
VARIABLES: SDXS                         TYPE: Input
 VARIABLES DESCRIPTION:   Diagnosis code array (passed by reference) 
  - array format:  SDXS(ICD ien) = "" (null) [Optional] 
VARIABLES: $$ST                         TYPE: Output
 VARIABLES DESCRIPTION:   
  0 = not filed for additional review 
  1 = filed for additional review 
  2 = deleted from SDSC SERVICE CONNECTED CHANGES (#409.48) file 
  
  DATE ACTIVATED: APR 10, 2012

NUMBER: 4991                            IA #: 4991
  DATE CREATED: MAY 11, 2007
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXUTL1
  NAME: PCE PRIMARY PROVIDER            ID: PXUTL1
 GENERAL DESCRIPTION:   Returns the primary provider for a visit, if there is
 one.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRIMARY
KEYWORDS: PROVIDER
KEYWORDS: ENCOUNTER
COMPONENT/ENTRY POINT: $$PRIMVPRV(PXUTVST)
 COMPONENT DESCRIPTION:   This entry point returns the primary provider for a
 visit; if there is one otherwise it returns 0.  
  
VARIABLES: PXUTVST                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the VISIT file #9000010.  [Required] 
  
VARIABLES: $$PRIMVPRV                   TYPE: Output
 VARIABLES DESCRIPTION:   Provider IEN from NEW PERSON file #200; or 0 = no
 provider 
  
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: SEP 27, 2007

NUMBER: 4992                            IA #: 4992
  DATE CREATED: MAY 14, 2007
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSBPSUT
  NAME: PSSBPSUT                        ID: PSSBPSUT
 GENERAL DESCRIPTION:   This routine contains APIs used mainly by ePharmacy
 (Electronic Third Party Billing).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NCPDP
KEYWORDS: NCPDPQTY
KEYWORDS: EPHARMACY
KEYWORDS: ECME
COMPONENT/ENTRY POINT: $$NCPDPQTY(DRUG,RXQTY)
 COMPONENT DESCRIPTION:   Returns the NCPDP BILLING QUANTITY and NCPDP DISPENSE
 UNIT for a specified DRUG and DISPENSE QUANTITY. This information is obtained
 by Multiplying the DISPENSE QUANTITY by the NCPDP QUANTITY MULTIPLIER field
 (#83) in the DRUG file (#50).  
VARIABLES: DRUG                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the DRUG file (#50).  
VARIABLES: RXQTY                        TYPE: Input
 VARIABLES DESCRIPTION:   Dispensed quantity. For most cases, this information
 will be retrieved from the PRESCRIPTION file (#52). For the original fill it
 will be the content of the QTY field (#7) and for the refills, field QTY (#1)
 in the REFILL sub-file (#52.1).  
VARIABLES: $$NCPDPQTY                   TYPE: Output
 VARIABLES DESCRIPTION:   This API returns two fields separated by up-arrow
 ("^") to be used when submitting electronic claims to 3rd party insurance
 companies for the DRUG and DISPENSE QUANTITY passed in: 
  
 Piece 1: NCPDP BILLING QUANTITY = DISPENSE QUANTITY (passed in) X NCPDP
 QUANTITY MULTIPLIER (field #83 in the DRUG file (#50)) with 3 decimal places.  
   
 Piece 2: NCPDP DISPENSE UNIT (field #82 in the DRUG file) 
  
 Notes: 1) This API can also return the following error "-1^INVALID DRUG" 
        2) The NCPDP DISPENSE UNIT is only returned if available.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   added 9/2007 
  DATE ACTIVATED: SEP 05, 2007          DEFERRED UNTIL: SEP 01, 2007

NUMBER: 4993                            IA #: 4993
  GLOBAL ROOT: TIU(8925.1,              DATE CREATED: MAY 23, 2007
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: TIU DOCUMENT DEFINITION FILE 8925.1 'B' CROSS-REFERENCE
  ID: TIU(8925.1,
GLOBAL REFERENCE: TIU(8925.1,'B',
 GENERAL DESCRIPTION:   The "B" cross-reference for the TIU Document Definition
 file (#8925.1) needs to be extended to 60 characters to ensure uniqueness in
 the index.  This file is pointed to by the TIU Document file (#8925), the
 HEALTH SUMMARY Type file (#142), and the FUNCTIONAL INDEPENDENCE Measurement 
 Parameter file (#783.9).  
  
 Revised Set/Kill Logic: 
  
   S ^TIU(8925.1,"B",$E(X,1,60),DA)="" 
   K ^TIU(8925.1,"B",$E(X,1,60),DA) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU
KEYWORDS: DOCUMENT DEFINITION
KEYWORDS: EXTENDED 'B' CROSS-REFERENCE
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Authorized in 1997 
  DATE ACTIVATED: SEP 19, 2007

NUMBER: 4994                            IA #: 4994
  FILE NUMBER: 8926.1                   GLOBAL ROOT: TIU(8926.1,
  DATE CREATED: MAY 23, 2007            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: TIU VHA ENTERPRISE STANDARD TITLE file 'B' CROSS REFERENCE
  ID: TIU(8926.1,
GLOBAL REFERENCE: TIU(8926.1,'B',
 GENERAL DESCRIPTION:   The "B" cross-reference for the TIU VHA Enterprise
 Standard Title file (#8926.1) needs to be extended to 90 characters to ensure
 uniqueness in the index.  This file is pointed to by the TIU Document
 Definition file (#8925.1) only.  
  
 Revised Set/Kill Logic: 
  
   S ^TIU(8926.1,"B",$E(X,1,90),DA)="" 
   K ^TIU(8926.1,"B",$E(X,1,90),DA) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU
KEYWORDS: ENTERPRISE STANDARD TITLE
KEYWORDS: 'B' CROSS-REFERENCE
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  DATE ACTIVATED: SEP 19, 2007

NUMBER: 4995                            IA #: 4995
  DATE CREATED: MAY 24, 2007
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: OR EVSEND GMRC
 GENERAL DESCRIPTION:   The protocol name OR EVSEND GMRC is exported as USE AS
 LINK FOR MENU ITEMS. This linkage will allow Clinical Procedures to link to
 the protocol and monitor order activity messages.  This IA is used in
 conjunction with IA 3135.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OR EVSEND GMRC
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  DATE ACTIVATED: JUL 09, 2007

NUMBER: 4996                            IA #: 4996
  FILE NUMBER: 399                      GLOBAL ROOT: DGCR(399,PRV
  DATE CREATED: MAY 25, 2007            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: EEOB Worklist NPI inclusion
  ID: DGCR(399,PRV
 GENERAL DESCRIPTION:   This DBIA is for allowing the Accounts Receivable
 package to utilize Fileman APIs to retrieve NPIs, provider types and provider
 names from the Bill/Claims file (#399).  The fileman APIS to be used are 
 GET1^DIQ and GETS^DIQ.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EEOB
KEYWORDS: WORKLIST
KEYWORDS: NPI
KEYWORDS: PROVIDER
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   The Accounts Recievable package needs to include the
 provider type, provider name and provider NPI on the EEOB Worklist.  This data
 is found in the Bill/ Claims  file (# 399).  
  DATE ACTIVATED: SEP 19, 2007

NUMBER: 4997                            IA #: 4997
  FILE NUMBER: 50.605                   GLOBAL ROOT: PS(50.605
  DATE CREATED: JUN 05, 2007            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Pointing to the VA DRUG CLASS (#50.605) File
  ID: PS(50.605
GLOBAL REFERENCE: PS(50.605
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   This agreement allows for other applications to store a
 pointer to the Vista VA DRUG CLASS (#50.605) file. This number can be used as
 an Identification Number to retrieve data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  DATE ACTIVATED: JUN 20, 2007

NUMBER: 4998                            IA #: 4998
  FILE NUMBER: 50.416                   GLOBAL ROOT: PS(50.416
  DATE CREATED: JUN 05, 2007            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Pointing to the DRUG INGREDIENTS (#50.416) File
  ID: PS(50.416
GLOBAL REFERENCE: PS(50.416
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   This agreement allows for other applications to store a
 pointer to the Vista DRUG INGREDIENTS (#50.416) file. This number can be used
 as an Identification Number to retrieve data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  DATE ACTIVATED: JUN 20, 2007

NUMBER: 4999                            IA #: 4999
  FILE NUMBER: 50.6                     GLOBAL ROOT: PSNDF(50.6
  DATE CREATED: JUN 05, 2007            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Pointing to the VA GENERIC (#50.6) File
  ID: PSNDF(50.6
GLOBAL REFERENCE: PSNDF(50.6
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   This agreement allows for other applications to store a
 pointer to the Vista VA GENERIC (#50.6) file. This number can be used as an
 Identification Number to retrieve data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  DATE ACTIVATED: JUN 20, 2007

NUMBER: 5000                            IA #: 5000
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: JUN 05, 2007            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Pointing to the PRESCRIPTION (#52) File
  ID: PSRX(
GLOBAL REFERENCE: PSRX(
FIELD NUMBER: .01                       FIELD NAME: RX#
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   This agreement allows for other applications to store a
 pointer to the Vista PRESCRIPTION (#52) file. This number can be used as an
 Identification Number  to retrieve data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  DATE ACTIVATED: JUN 20, 2007

NUMBER: 5001                            IA #: 5001
  FILE NUMBER: 57.1                     GLOBAL ROOT: PS(57.1
  DATE CREATED: JUN 05, 2007            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Pointing to the PHARMACY QUICK ORDER (#57.1) File
  ID: PS(57.1
GLOBAL REFERENCE: PS(57.1
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   This agreement allows for other applications to store a
 pointer to the Vista 
  PHARMACY QUICK ORDER (#57.1) file. This number can be used as an
 Identification Number to retrieve data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  DATE ACTIVATED: JUN 20, 2007

NUMBER: 5002                            IA #: 5002
  FILE NUMBER: .402                     GLOBAL ROOT: DIE(D0,'DR',
  DATE CREATED: JUN 13, 2007            CUSTODIAL PACKAGE: 1
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INPUT TEMPLATE FOR A MULTIPLE
  ID: DIE(D0,'DR',
GLOBAL REFERENCE: DIE(D0,'DR',
 GENERAL DESCRIPTION:   VA FileMan does not allow you to use an Input Template
 exclusively for fields within a multiple.  For example, if you know the file
 top level IEN and you know the sub-file IEN and you want to only present for 
 editing to the user the fields within the sub-file, you cannot do this with a
 VA FileMan Input Template.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: INPUT TEMPLATE
KEYWORDS: DR STRING
KEYWORDS: DR ARRAY
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   This agreement allows the subscribing package to
 directly access the global node where the Input Template DR-array is located. 
 This is located at: 
  
    ^DIE(D0,"DR", 
  
 The data in this file is used to construct the DR-string and also the DR-array
 structure when the DR-string is greater than 245 characters long.  
  
 This ICR also includes the setting of the DATE LAST USED field (#7) in the
 INPUT TEMPLATE file (#.402) whenever the input template is being invoked in
 the manner specified in this ICR.  It is the responsibility of the subscribing
 package developer to set this field since FileMan will not set it.  
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   Lab added 20090713 
  DATE ACTIVATED: JUL 13, 2009

NUMBER: 5003                            IA #: 5003
  DATE CREATED: JUN 14, 2007
  CUSTODIAL PACKAGE: CAPACITY MANAGEMENT TOOLS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: KMPDTU11                     NAME: CAPACITY PLANNING TIMING API
  ID: KMPDTU11
 GENERAL DESCRIPTION:   API to Start and Stop gathering Timing stats for
 Capacity Planning.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: TIMING
KEYWORDS: CAPACITY PLANNING
KEYWORDS: CP
COMPONENT/ENTRY POINT: TIMING
VARIABLES: KMPDSS                       TYPE: Input
 VARIABLES DESCRIPTION:   Subscript (free text) used to identify timing data.  
VARIABLES: KMPDNODE                     TYPE: Input
 VARIABLES DESCRIPTION:   Node name (free text).  
VARIABLES: KMPDST                       TYPE: Input
 VARIABLES DESCRIPTION:   Start/Stop - 1 = start timing 
              2 = stop timing 
VARIABLES: KMPDHTM                      TYPE: Input
 VARIABLES DESCRIPTION:   Current time in $H format (optional).  
VARIABLES: KMPDUZ                       TYPE: Input
 VARIABLES DESCRIPTION:   Current DUZ of user (optional).  
VARIABLES: KMPDCL                       TYPE: Input
 VARIABLES DESCRIPTION:   Client name (free text). If not defined the current
 IO("CLNM")) will be used (optional).  

NUMBER: 5004                            IA #: 5004
  DATE CREATED: JUN 19, 2007            CUSTODIAL PACKAGE: HEALTHEVET DESKTOP
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: DISTRIBUTION OF XHDXC DESKTOP OPTION
 GENERAL DESCRIPTION:   This agreement is provided to the CARE MANAGEMENT
 package version 1.0 to distribute the XHDXC DESKTOP option.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XHDXC DESKTOP
SUBSCRIBING PACKAGE: CARE MANAGEMENT
  DATE ACTIVATED: JUN 20, 2007

NUMBER: 5005                            IA #: 5005
  DATE CREATED: JUN 19, 2007            CUSTODIAL PACKAGE: HEALTHEVET DESKTOP
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: DISTRIBUTION OF XHD PRISM DESKTOP THEME
 GENERAL DESCRIPTION:   This agreement is provided to the CARE MANAGEMENT
 package version 1.0 to distribute the XHD PRISM DESKTOP THEME parameter.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XHD PRISM
KEYWORDS: HEALTHEVET DESKTOP
SUBSCRIBING PACKAGE: CARE MANAGEMENT
  DATE ACTIVATED: JUN 20, 2007

NUMBER: 5006                            IA #: 5006
  DATE CREATED: JUN 28, 2007            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEXTRAN1
  NAME: Lexicon Obtain Synonyms for Code
  ID: LEXTRAN1
 GENERAL DESCRIPTION:   This API will return an array for a given code and
 coding system. The array will contain all synonyms for the concept including
 the preferred term and the fully specified name.  If any of the passed
 parameters are incorrect or unrecognizable, the API will return an error
 message indicating the nature of the error. 
  STATUS: Active
KEYWORDS: SYNONYM
KEYWORDS: LEXICON
KEYWORDS: $$GETSYN
KEYWORDS: GETSYN
KEYWORDS: LEXTRAN1
COMPONENT/ENTRY POINT: $$GETSYN(SRC,CODE,VDT,ARRAY,IENS,ID,INC)
VARIABLES: SRC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the mnemonic for a code system (mandatory).
 The allowable code system mnemonics are those that exist in the "B" index of
 the coding systems file (757.03) This is code system source abbreviation
 Lexicon.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a code of a classification system that is
 stored in the Lexicon.  Classification systems include SNOMED CT, ICD, CPT,
 HCPCS, etc.  
VARIABLES: VDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the effective date; the default if no date is
 specified is the current system date (optional). 
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of the output array. The default, if
 no array name is specified, is 'LEX' (optional) 
  
 The format of the output is as follows: 
    If valid code and source are passed 
    "1^no of synonyms" 
    LEX("P") = preferred term or major concept name^IEN 
    LEX("F") = fully specified name^IEN (if one exists) 
    LEX("S",n) = the nth synonym found^IEN (if they exist) 
    The presence of IEN in the return array is determined by the 
    LEXIENS parameter.  If the call does not find the code for the specified
 source it will return 
    "-2^"_LEXSCNM_" code "_LEXCODE_" not on file" 
    where LEXCSNM is the source name 
          LEXCODE is the code If an invalid source is passed the call will
 return 
    "-1^source not recognized" 
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   If this parameter is set to 1 the expression IEN will
 be included in the return array. Default is 0 - exclude IENS from return
 array.  
VARIABLES: ID                           TYPE: Input
 VARIABLES DESCRIPTION:   Designation Identifiers (optional) 
     1 return Designation IDs (3rd piece) 
     0 do not return Designation IDs (default) 
  
VARIABLES: INC                          TYPE: Input
 VARIABLES DESCRIPTION:   Include Deactivated Terms (optional) 
     1 return Deactivated Terms 
     0 do not return Deactivated Terms (default) 
  
  DATE ACTIVATED: DEC 28, 2007

NUMBER: 5007                            IA #: 5007
  DATE CREATED: JUN 28, 2007            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEXTRAN1
  NAME: Lexicon Obtain Fully Specified Name
  ID: LEXTRAN1
 GENERAL DESCRIPTION:   This API returns the fully specified name for a given
 coding system and code.  If any of the passed parameters are incorrect or
 unrecognizable, the API will return an error message indicating the nature of
 the error.  
  STATUS: Active
KEYWORDS: fully
KEYWORDS: specified
KEYWORDS: lexicon
COMPONENT/ENTRY POINT: GETFSN(LEXSRC,LEXCODE,LEXVDT)
VARIABLES: LEXSRC                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the mnemonic for a coding system (mandatory).
 The allowable code system mnemonics are those that exist in the "B" index of
 the coding systems file (757.03) This is code system source abbreviation
 Lexicon. 
VARIABLES: LEXCODE                      TYPE: Input
 VARIABLES DESCRIPTION:   This is a code that belongs to a coding system that
 is stored in the Lexicon.  Coding systems include SNOMED CT, ICD, CPT, HCPCS,
 etc. 
VARIABLES: LEXVDT                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the effective date; the default if no date is
 specified is the current system date (optional).  
  DATE ACTIVATED: DEC 28, 2007

NUMBER: 5008                            IA #: 5008
  DATE CREATED: JUN 28, 2007            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEXTRAN1
  NAME: Lexicon Obtain Preferred Term   ID: LEXTRAN1
 GENERAL DESCRIPTION:   This API returns the preferred term for a given coding
 system and code.  If any of the passed parameters are incorrect or
 unrecognizable, the API will return an error message indicating the nature of
 the error.  
  STATUS: Active
KEYWORDS: preferred
KEYWORDS: lexicon
COMPONENT/ENTRY POINT: $$GETPREF
VARIABLES: LEXSRC                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the mnemonic for a code system (mandatory).
 The allowable code system mnemonics are those that exist in the "B" index of
 the coding systems file (757.03). This is the Lexicon code system source
 abbreviation. 
VARIABLES: LEXCODE                      TYPE: Input
 VARIABLES DESCRIPTION:   This is a code belonging to a coding system that is
 stored in the Lexicon.  Coding systems include SNOMED CT, ICD-9-CM, CPT,
 HCPCS, etc. 
VARIABLES: LEXVDT                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the effective date; the default if no date is
 specified is the current system date (optional). 
  DATE ACTIVATED: DEC 28, 2007

NUMBER: 5009                            IA #: 5009
  DATE CREATED: JUN 28, 2007            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEXTRAN1
  NAME: Lexicon Obtain Designation Code
  ID: LEXTRAN1
 GENERAL DESCRIPTION:   This API returns the designation code for a given
 coding system and text.  If any of the passed parameters are incorrect or
 unrecognizable, the API will return an error message indicating the nature of
 the error.  
  STATUS: Active
KEYWORDS: designation
KEYWORDS: lexicon
COMPONENT/ENTRY POINT: $$GETDES(LEXSRC)
VARIABLES: LEXSRC                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the mnemonic for a code system (mandatory).
 The allowable code system mnemonics are those that exist in the "B" index of
 the coding systems file (757.03). This is the Lexicon code system source
 abbreviation.  
VARIABLES: LEXTEXT                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the displayable text of the expression for
 which the designation code is being sought (mandatory).  
VARIABLES: LEXVDT                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the effective date; the default if no date if
 no date is specified is the current system date (optional).  
COMPONENT/ENTRY POINT: $$GETDES(LEXSRC,LEXCODE,LEXVDT)
  DATE ACTIVATED: DEC 28, 2007

NUMBER: 5010                            IA #: 5010
  DATE CREATED: JUN 28, 2007            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEXTRAN1
  NAME: Lexicon Obtain Mapped Codes     ID: LEXTRAN1
 GENERAL DESCRIPTION:   This API returns an array containing the mappings for a
 specified code for a specified mapping identifier.  If any of the passed
 parameters are incorrect or unrecognizable, the API will return an error
 message indicating the nature of the error.  
  
  STATUS: Active
KEYWORDS: mapped
KEYWORDS: lexicon
KEYWORDS: mapping
COMPONENT/ENTRY POINT: GETASSN(LEXCODE,LEXMAP,LEXVDT,LEXRAY)
VARIABLES: LEXCODE                      TYPE: Input
 VARIABLES DESCRIPTION:   This is a code belonging to a coding system that is
 stored in the Lexicon.  Coding systems include SNOMED CT, ICD, CPT, HCPCS,
 etc.  
  
VARIABLES: LEXMAP                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the mapping identifier (mandatory). This
 allows the system to determine which map is to be used for translation. The
 map must be defined in the mapping definition file (757.32).  
  
VARIABLES: LEXVDT                       TYPE: Input
 VARIABLES DESCRIPTION:   This is a versioning date to used to distinguish 
 between active and inactive mappings (optional, default is TODAY) 
  
VARIABLES: LEXRAY                       TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of the output array. The default, if
 no array name is specified, is 'LEX' (optional) 
  
 The output array will have the following formats: 
  
 Format #1: 
  
    LEX(n,CODE)="" 
    where n is the nth mapped code 
    code is the code which is mapped to 
  
    e.g. >S X=$$GETASSN(15250008,"SCT2ICD") 
  
         >ZW LEX 
  
         LEX=2 
         LEX(1,"371.30")="" 
         LEX(2,"371.40")="" 
  
 Format #2: 
  
    LEX(n,CODE)=1 
    LEX(n,CODE)=0 
    where n is the nth mapped code 
    code is the code which is mapped to 
  
    If set to 1, then source code is a full 
    match to the target code.  If set to 0, 
    then the source code is a partial match 
    to the target code.  This feature was 
    designed for the Automated Service 
    Connected Designation (ASCD) project.  
    Full and partial match designations 
    are used in determining service 
    connection.  
  
    e.g. >S X=$$GETASSN^LEXTRAN1(300.4,"ASCD") 
  
         >ZW LEX 
      
         LEX=1 
         LEX(1,9405)=1 
  
  DATE ACTIVATED: DEC 28, 2007

NUMBER: 5011                            IA #: 5011
  DATE CREATED: JUN 28, 2007            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEXTRAN
  NAME: Lexicon Obtain Version Identifier
  ID: LEXTRAN
 GENERAL DESCRIPTION:   This API returns the SDO version identifier for a given
 coding system, code, and date. If any of the passed parameters are incorrect
 or unrecognizable, the API will return an error message indicating the nature
 of the error.  
  STATUS: Active
KEYWORDS: version
KEYWORDS: lexicon
COMPONENT/ENTRY POINT: $$VERSION(LEXSRC,LEXCODE,LEXVDT)
VARIABLES: LEXSRC                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the mnemonic for a coding system (mandatory).
 The allowable coding system mnemonics are those that exist in the "B" index of
 the coding systems file (757.03). This is the Lexicon coding system source
 abbreviation.  
VARIABLES: LEXCODE                      TYPE: Input
 VARIABLES DESCRIPTION:   This is a code belonging to a coding system that is
 stored in the Lexicon.  Coding systems include SNOMED CT ICD-9-CM, CPT, HCPCS,
 etc.  
VARIABLES: LEXVDT                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the effective date; the default if no date is
 specified is the current system date (optional).  
  DATE ACTIVATED: DEC 28, 2007

NUMBER: 5012                            IA #: 5012
  FILE NUMBER: 38.5                     GLOBAL ROOT: DGIN(38.5,
  DATE CREATED: JUL 05, 2007            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: DBIA5012                        ID: DGIN(38.5,
 GENERAL DESCRIPTION:   The Income Verification Match (IVM) package has a need
 to read, write and delete data in the INCONSISTENT DATA file (#38.5) during
 the process to build Z07 HL7 messages.  
  
  
 .01      NAME                   0;1 POINTER TO PATIENT FILE (#2) 
  
 2        INITIALLY IDENTIFIED   0;2 DATE 
  
 3        IDENTIFIED BY          0;3 POINTER TO NEW PERSON FILE (#200) 
  
 4        LAST UPDATED           0;4 DATE 
  
 5        LAST UPDATED BY        0;5 POINTER TO NEW PERSON FILE (#200) 
  
 6        BULLETIN SENT          0;6 DATE 
  
 10       INCONSISTENCY          I;0 POINTER Multiple #38.51 
  
  .01       INCONSISTENCY          0;1 POINTER TO INCONSISTENT DATA ELEMENT 
                                   S FILE (#38.6) (Multiply asked) 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH

NUMBER: 5013                            IA #: 5013
  GLOBAL ROOT: DD(9002313.58            DATE CREATED: JUL 10, 2007
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS TO DD FOR FILE 9002313.58
  ID: DD(9002313.58
GLOBAL REFERENCE: DD(9002313.58
FIELD NUMBER: ALL FIELDS                FIELD NAME: ALL FIELDS
  ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The ECME application is granted read access to the
 DD(9002313.58 global in order to $ORDER through the FIELD subscript of the
 ^DD(9002313.58,FIELD). 
  STATUS: Active
KEYWORDS: ECME
KEYWORDS: BPS
KEYWORDS: DD
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: JUL 12, 2007

NUMBER: 5014                            IA #: 5014
  FILE NUMBER: 59                       GLOBAL ROOT: PS(59
  DATE CREATED: JUL 11, 2007            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Pointing to the OUTPATIENT SITE (#59) File
  ID: PS(59
GLOBAL REFERENCE: PS(59
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Pointed to
 GENERAL DESCRIPTION:   This agreement allows for other applications to store a
 pointer to the Vista OUTPATIENT SITE (#59) file. This number can be used as an 
 Identification Number to retrieve data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  DATE ACTIVATED: JUL 12, 2007

NUMBER: 5015                            IA #: 5015
  FILE NUMBER: 9002313.59               GLOBAL ROOT: DD(9002313.59
  DATE CREATED: JUL 12, 2007            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS TO DD FOR FILE 9002313.59
  ID: DD(9002313.59
GLOBAL REFERENCE: DD(9002313.59
FIELD NUMBER: ALL FIELDS                FIELD NAME: ALL FIELDS
  ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The ECME application is granted read access to the DD
 global in order to $ORDER through the FIELD subscript of the
 ^DD(9002313.59,FIELD) global. 
  STATUS: Active
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: JUL 12, 2007

NUMBER: 5016                            IA #: 5016
  DATE CREATED: JUL 13, 2007            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPMDD
  NAME: SCREEN FOR ACTIVE PROVIDER      ID: DGPMDD
 GENERAL DESCRIPTION:   Screen for active provider in NEW PERSON (#200) file.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PROVIDER
COMPONENT/ENTRY POINT: $$SCREEN(Y,DA,DGDT)
 COMPONENT DESCRIPTION:   This entry point screens a record of the NEW PERSON
 (#200) file to determine if that record is a valid Provider selection.  
  The screening logic checks that the record: 
  1. Has the PROVIDER Security Key.  
  2. Is active on the system (no Termination Date) on a given 
     date.  
  3. Has an active Person Class on a given date.  
  
 This screening logic uses the DBIA #2349 - ACTIVE PROVIDER to call routine
 $$ACTIVPRV^PXAPI for validating the Termination Date (#9.2) and Person Class
 (#8932.1) fields of the New Person (#200) file.  
  
  
  
  
  
VARIABLES: Y [Required]                 TYPE: Input
 VARIABLES DESCRIPTION:   IEN of NEW PERSON (#200) file 
  
VARIABLES: DA [Optional]                TYPE: Input
 VARIABLES DESCRIPTION:   IEN of NEW PERSON (#200) file 
  
VARIABLES: DGDT  [Optional]             TYPE: Input
 VARIABLES DESCRIPTION:   Date/Time (internal FM format) (Defaults to Kernel DT
 value if not passed) 
  
VARIABLES: $$SCREEN                     TYPE: Output
 VARIABLES DESCRIPTION:   
  1 = success 
  0 = failure 
  
  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: JUL 13, 2007

NUMBER: 5017                            IA #: 5017
  FILE NUMBER: 42.4                     GLOBAL ROOT: DIC(42.4
  DATE CREATED: JUL 25, 2007            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Change notification for file 42.4
  ID: DIC(42.4
 GENERAL DESCRIPTION:   The VBECS (Veterans Blood Establishment Computer
 System) TreatingSpecialty table replicates the data in the VistA SPECIALTY
 file (#42.4). The VBECS team requests notification of any changes to the data 
 or data definitions in file 42.4 to ensure that VBECS and VistA are in synch. 
 We also request a copy of any test patches affecting the data or data
 definitions in file 42.4 so we can prepare any necessary VBECS patches.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VBECS
  DATE ACTIVATED: MAR 04, 2008

NUMBER: 5018                            IA #: 5018
  DATE CREATED: JAN 10, 2011            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGRPDD1                      NAME: DBIA5018
  ID: DGRPDD1
 GENERAL DESCRIPTION:   Create pseudo SSN for John Doe patients or for a
 patient that can't provide their SSN at Registration.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SSN
 COMPONENT DESCRIPTION:   Routine DGRPDD1 has a subroutine SSN that generates
 psuedo SSNs. 
VARIABLES: X                            TYPE: Both
 VARIABLES DESCRIPTION:   The variable X is set to "P" before calling the
 component. The pseudo SSN is returned in the same X variable.  
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   FILEPSSN (a subroutine of JVDGF) is used whenever the
 Single Patient Registration needs to generate a pseudoSSN.  
  
 FILEPSSN ; create pseudo SSN 
  N DPTIDS,DPTX,ZTQUEUED 
  N X,Y S X=TMPFDA(2,.03) D ^%DT 
  S ZTQUEUED=1,DPTIDS(.03)=Y,DPTX=TMPFDA(2,.01) 
  S X=XSN D SSN^DGRPDD1 ; call to legacy code.  
  I X?9N1"P" S XSN=X 
  I X'?9N1"P" D 
  . S XSN="" 
  . S DGOUT(1)="ERR^Patient Record NOT CREATED" 
  . S DGOUT(2)="pseudoSSN could not be generated" 
  ;
  Q 
  
  The line of code calls the component: 
     S X=XSN D SSN^DGRPDD1 ; call to legacy code.  

NUMBER: 5019                            IA #: 5019
  FILE NUMBER: 9002313.56               GLOBAL ROOT: BPS(9002313.56
  DATE CREATED: JUL 31, 2007            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME:  PHARMACY DATA FROM BPS PHARMACIES file
  ID: BPS(9002313.56
GLOBAL REFERENCE: BPS(9002313.56,D0,
FIELD NUMBER: .02                       FIELD NAME: NCPDP #
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: BPS(9002313.56,D0,'OPSITE',D1,
FIELD NUMBER: .01                       FIELD NAME: OUTPATIENT SITE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Kernel Package requests read access using FileMan
 to the following fields of the BPS PHARMACIES file (#9002313.56).  
  
  
  STATUS: Active
KEYWORDS: NPI
KEYWORDS: NCPDP
SUBSCRIBING PACKAGE: KERNEL
  DATE ACTIVATED: SEP 19, 2007

NUMBER: 5020                            IA #: 5020
  DATE CREATED: AUG 01, 2007
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RAAPI
  NAME: Rad/Nuc Med accession number/SIUID utilities
  ID: RAAPI
 GENERAL DESCRIPTION:   $$ACCNUM 
 --------
 The $$ACCNUM function creates and returns a site specific accession number 
 based on the input of the following case specific identifiers: RADFN (patient
 DFN), RADTI (inv. date/time of the exam), & RACNI (the exam record IEN).  
  
 $$ACCFIND 
 ---------
 Based on the input of an accession number or a site specific accession number
 and if successful the $$ACCFIND function returns case specific identifiers:
 RADFN (patient DFN), RADTI (inv. date/time of the exam), & RACNI (the exam
 record IEN) in array 'RAA(Z)'. The variable 'Z' is also returned to indicate
 the number of 'RAA' array elements created.  
  
 If unsuccessful, 'Z' is returned as a string: the first piece is a negative
 number indicating the error type and the second piece is the error type text.  
  
 $$ACCRPT 
 --------
 Based on the input of a pointer to a record in the RAD/NUC MED REPORTS (#74) 
 file, the $$ACCRPT function returns the accession number(s) in the 'RAA(n)' 
 array, if successful.  If n=1 the single accession number is returned in 
 RAA(1).  If n>1 the 'lead' accession number (for printsets) is returned in 
 RAA(1) and subsequent ones are returned in RAA(2) thru RAA(n).  Accession 
 numbers are returned in either standard "mmddyy-case#" format or in the site 
 specific "sss-mmddyy-case#" format.  
  
 If unsuccessful, a "-1" (invalid file #74 pointer value) is returned.  
  
 $$GETSIUID 
 ----------
 Based on the input of exam data, the RADFN (patient DFN), RADTI (inverse 
 date/time of registered exam) and RACNI (exam record), the $$GETSIUID function
 returns the Study Instance UID field value [^DD(70.03,81)].  
  
 $$SIUIDFND 
 ----------
 Based on the input of a Study Instance UID, if successful the $$SIUIDFND 
 function returns a '1' and also returns the case specific identifiers: RADFN
 (patient DFN), RADTI (inv. date/time of the exam), & RACNI (the exam record
 IEN) in array 'RAA(1)'.  
  
 If unsuccessful, '-1^"no data associated with this study instance UID"^siuid' 
 is returned as a string: the first piece is a '-1' indicating the lookup was 
 not successful, the second piece is the error text and the third piece is the 
 SIUID which was the original input.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: accession number
KEYWORDS: site specific accession number
KEYWORDS: day-case number
KEYWORDS: imaging radiology
KEYWORDS: radiology imaging
COMPONENT/ENTRY POINT: ACCNUM
 COMPONENT DESCRIPTION:   Given the following input into the function: RADFN,
 RADTI, & RACNI a site specific accession number in the following format
 'sss-ddmmyy-case#' is returned.  
VARIABLES: RADFN                        TYPE: Input
 VARIABLES DESCRIPTION:   RADFN is the DFN of the patient record in the PATIENT
 (#2) file.  
VARIABLES: RADTI                        TYPE: Input
 VARIABLES DESCRIPTION:   RADTI is the inverse date/time of the exam.  
  
 Example: an inverse date/time of: 6929488.8676 is equivalent to a FileMan 
 internal date/time value of: 3070511.1323 when the FileMan internal date/time
 is subtracted from the constant: 9999999.9999.  
VARIABLES: RACNI                        TYPE: Input
 VARIABLES DESCRIPTION:   RACNI is the IEN of the case level record.  
VARIABLES:                              TYPE: Output
 VARIABLES DESCRIPTION:   This extrinsic function returns a site specific
 accession number in the following format: 'sss-ddmmyy-case#'.  
COMPONENT/ENTRY POINT: ACCFIND
 COMPONENT DESCRIPTION:   When an accession number in either a
 'sss-mmddyy-xxxxx' or 'mmddyy-xxxxx' format is entered the function returns
 (if successful): 
  
 An array (RAA(Z)) defined to be a string in the following format: 
 RADFN_^_RADTI_^_RACNI. The value 'Z' is returned to indicate, if set to a 
 positive value, the number of array elements return.  
  
 An error string if the lookup failed. These error strings are: -1^"invalid
 site accession number format"^accession # -2^"invalid accession number
 format"^accession # -3^"no data associated with this accession
 number"^accession # 
  
  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   'Y' is the accession number in either a
 'sss-mmddyy-xxxxx' or 'mmddyy-xxxxx' format.  
VARIABLES: RAA (conditional)            TYPE: Output
 VARIABLES DESCRIPTION:   If the accession number lookup is successful, the
 array 'RAA(Z)' will return data in the following format:
 RADFN_^_RADTI_^_RACNI.  
VARIABLES: Z                            TYPE: Output
 VARIABLES DESCRIPTION:   'Z' is the number of array elements when successful.
 When unsuccessful (Z<0) 'Z' is a specific error dialog which is returned along
 with the invalid accession number.  
  
 Examples: 
 ---------
 -1^"invalid site accession number format"^accession # -2^"invalid accession
 number format"^accession # -3^"no data associated with this accession
 number"^accession # 
COMPONENT/ENTRY POINT: ACCRPT
 COMPONENT DESCRIPTION:   When a pointer to a record in the RAD/NUC MED REPORTS
 (#74) file is entered, the function returns: 
    
 If successful, an array (RAA(Z)) containing the accession number(s).  The 
 variable 'Z' is returned to indicate the number of array elements.  If Z=1, 
 the single accession number is returned in RAA(1).  If Z>1 the 'lead' 
 accession number (for printsets) is returned in RAA(1) and subsequent ones are
 returned in RAA(2) thru RAA(Z).  Accession numbers are returned in either 
 standard "mmddyy-case#" format or in site specific "sss-mmddyy-case#" format. 
     
 If unsuccessful, a "-1" (indicating an invalid file #74 pointer value) is 
 returned. 
  
VARIABLES: Z                            TYPE: Output
 VARIABLES DESCRIPTION:   'Z' is the number of array elements when successful. 
 If unsuccessful, indicating an invalid pointer value to file #74, 'Z' is -1.  
  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   'Y' is a pointer to the RAD/NUC MED REPORTS (#74)
 file.  
  
VARIABLES: RAA                          TYPE: Output
 VARIABLES DESCRIPTION:   If the lookup is successful, the array 'RAA(Z)' will
 return the accession number(s) in the standard "mmddyy-case#" or site specific
 "sss-mmddyy-case#" format.  
  
COMPONENT/ENTRY POINT: GETSIUID
 COMPONENT DESCRIPTION:   When the exam data (RADFN-patient DFN, RADTI-inverse
 date/time of registered exam and RACNI-exam record), is entered the function
 returns the Study Instance UID field value [^DD(70.03,81)].  
  
VARIABLES: RADFN                        TYPE: Input
 VARIABLES DESCRIPTION:   RADFN is the DFN of the patient record in the PATIENT
 (#2) file.  
  
VARIABLES: RADTI                        TYPE: Input
 VARIABLES DESCRIPTION:   RADTI is the inverse date/time of the exam.  
  
 Example: an inverse date/time of: 6929488.8676 is equivalent to a FileMan 
 internal date/time value of: 3070511.1323 when the FileMan internal date/time
 is subtracted from the constant: 9999999.9999.  
  
VARIABLES: RACNI                        TYPE: Input
 VARIABLES DESCRIPTION:   RACNI is the IEN of the case level record.  
  
COMPONENT/ENTRY POINT: SIUIDFND
 COMPONENT DESCRIPTION:   Based on the input of a Study Instance UID, if
 successful the $$SIUIDFND function returns a '1' and also returns the case
 specific identifiers: RADFN (patient DFN), RADTI (inv. date/time of the exam),
 & RACNI (the exam record IEN) in array 'RAA(1)'.  
  
 If unsuccessful, '-1^"no data associated with this study instance UID"^siuid' 
 is returned as a string: the first piece is a '-1' indicating the lookup was 
 not successful, the second piece is the error text and the third piece is the 
 SIUID which was the original input.  
  
VARIABLES: Z                            TYPE: Output
 VARIABLES DESCRIPTION:   'Z' is equal to '1' when successful.  When
 unsuccessful, 'Z' is equal to '-1' concatenated with a specific error dialog
 which is returned along with the invalid study instance UID.  
  
 Examples: 
 ---------
 -1^"no data associated with this study instance UID"^siuid 
  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   'Y' is the Study Instance UID to be looked up.  
  
VARIABLES: RAA (Conditional)            TYPE: Output
 VARIABLES DESCRIPTION:   If the Study Instance UID lookup is successful, the
 array 'RAA(1)' will return data in the following format:
 RADFN_^_RADTI_^_RACNI.  
  
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Patch MECH*1.0*1 processes HL7 new-order messages about
 imaging studies performed in the community but not entered through VistA.  In
 order to do this, it needs to invoke Radiology routines and make FileMan calls
 to add entries to the RAD/NUC MED PATIENT File (#70) (for existing VA
 patients), the ORDER File (#100), and the RAD/NUC MED ORDERS File (#75.1). The
 patch then creates an HL7 order-update message that transmits the study's 
 accession number to the sender. ADDED 3/2/2022, effective with MECH*1.0*1 
 Medicom Class 3 product Document Only 
  DATE ACTIVATED: MAY 22, 2009

NUMBER: 5021                            IA #: 5021
  DATE CREATED: AUG 01, 2007            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  ROUTINE: MAG7UFO
  NAME: Populate NEW PERSON phone(s) into a local array
  ID: MAG7UFO
 GENERAL DESCRIPTION:   This function return the following NEW PERSON (#200)
 file fields into a local array: PHONE (HOME) (#.131), OFFICE PHONE (#.132),
 PHONE #3 (#.133), PHONE #4 (#.134), COMMERCIAL PHONE (#.135), FAX NUMBER
 (#.136), VOICE PAGER (#.137), and DIGITAL PAGER (#.138). 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: new person phone number api 
COMPONENT/ENTRY POINT: NPFON
VARIABLES: XFLD                         TYPE: Input
 VARIABLES DESCRIPTION:   The name of the array into which to populate phone
 data.  
VARIABLES: XIEN                         TYPE: Input
 VARIABLES DESCRIPTION:   The Internal Entry Number (IEN) of the NEW PERSON
 file record.  
VARIABLES: @XFLD                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the local array, defined by the variable
 XFLD, that is defined to carry phone contact information for an specific
 individual in the NEW PERSON file.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 5022                            IA #: 5022
  DATE CREATED: AUG 01, 2007            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  ROUTINE: MAGDRAHL
  NAME: Build the HL7 ZDS segment for Study Instance UID
  ID: MAGDRAHL
 GENERAL DESCRIPTION:   This function creates a DICOM Study Instance UID from
 three Radiology/Nuclear Medicine package variables: RADTI, RACNI, and RADTE.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Study Instance UID
KEYWORDS: imaging HL7 ZDS segment
COMPONENT/ENTRY POINT: ZDS
VARIABLES: RADFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The record number (DFN) of the patient in the PATIENT
 (#2) file.  
VARIABLES: RADTI                        TYPE: Input
 VARIABLES DESCRIPTION:   The inverse date/time value of when the exam was
 registered.  
VARIABLES: RACNI                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the exam level record in the RAD/NUC MED
 PATIENT (#70) file.  
VARIABLES:                              TYPE: Output
 VARIABLES DESCRIPTION:   Returns the SIUID value as part of the ZDS HL7
 segment.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 5023                            IA #: 5023
  DATE CREATED: AUG 01, 2007            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  ROUTINE: MAGDHLS                      NAME: Build the HL7 PID and PV1 segments
  ID: MAGDHLS                           STATUS: Active
KEYWORDS: imaging HL7 utilities
KEYWORDS: PV1 segment
KEYWORDS: PID segment
KEYWORDS: imaging HL7 segment utility
COMPONENT/ENTRY POINT: PID
 COMPONENT DESCRIPTION:   This function builds the PID HL7 segment for HL7
 versions of 2.4 and greater.  
VARIABLES: XDFN                         TYPE: Input
 VARIABLES DESCRIPTION:   The Internal Entry Number (IEN) of the record in the
 PATIENT file.  
VARIABLES: XYMSG                        TYPE: Input
 VARIABLES DESCRIPTION:   The name of the array defining where the data is to
 be stored.  
VARIABLES: @XYMSG                       TYPE: Output
 VARIABLES DESCRIPTION:   The user defined array containing Patient Identifier
 (PID) data elements.  
COMPONENT/ENTRY POINT: PV1
 COMPONENT DESCRIPTION:   This function builds the PV1 HL7 segment for HL7
 versions of 2.4 and greater.  
VARIABLES: XDFN                         TYPE: Input
 VARIABLES DESCRIPTION:   The Internal Entry Number (IEN) of the record in the
 PATIENT file.  
VARIABLES: XEVN                         TYPE: Input
 VARIABLES DESCRIPTION:   The trigger event of the message being built.  
VARIABLES:  
VARIABLES: @XYMSG                       TYPE: Output
 VARIABLES DESCRIPTION:   The user defined array containing Patient Visit (PV1)
 data elements.  
VARIABLES: XEVNDT                       TYPE: Input
 VARIABLES DESCRIPTION:   The date/time of the event in FileMan format.  
VARIABLES: XYMSG                        TYPE: Input
 VARIABLES DESCRIPTION:   The name of the array to which to add the PV1 message
 elements.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 5024                            IA #: 5024
  DATE CREATED: AUG 06, 2007            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SRONRPT
  NAME: SURGERY FILE 130 DATA - NURSE INTRAOPERATIVE REPORT
  ORIGINAL NUMBER: 5024                 ID: SRONRPT
 GENERAL DESCRIPTION:   TIU will call this tag from a utiity routine for
 comparison of the NURSE INTRAOPERATVIE REPORT in TIU (8925) with the Surgery
 file (130) NIR data.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RPT
 COMPONENT DESCRIPTION:   Allow TIU to call RPT^SRONRPT(SRTN). Calling routine
 supplies SRTN.  
  
 Data returned in ^TMP("SRNIR",$J,SRTN 
VARIABLES: SRTN                         TYPE: Input
 VARIABLES DESCRIPTION:   The variable SRTN (which identifies the surgical
 case) must be defined before making the call.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES

NUMBER: 5025                            IA #: 5025
  DATE CREATED: AUG 06, 2007            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SROANR
  NAME: SURGERY FILE 130 DATA - ANESTHESIA REPORT
  ORIGINAL NUMBER: 5024                 ID: SROANR
 GENERAL DESCRIPTION:   TIU will call this tag from a utiity routine for
 comparison of the Anesthesia report in TIU (8925) with the Surgery file (130)
 Anesthesia data.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RPT
 COMPONENT DESCRIPTION:   Allow TIU to call RPT^SROAR(SRTN). Calling routine
 supplies SRTN.  
     
    Data returned in ^TMP("SRANE",$J,SRTN 
VARIABLES: SRTN                         TYPE: Input
 VARIABLES DESCRIPTION:   The variable SRTN (which identifies the surgical
 case) must be defined before making the call.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES

NUMBER: 5026                            IA #: 5026
  DATE CREATED: AUG 07, 2007
  CUSTODIAL PACKAGE: HEALTH DATA & INFORMATICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HDISVAP1
  NAME: TRANSMIT LAB SNOMED CT EXCEPTIONS
  ID: HDISVAP1
 GENERAL DESCRIPTION:   
  This Integration Agreement permits the Lab package to utilize a Health 
  Data and Informatics (HDI) application programmer interface (API) to 
  report SNOMED CT (SCT) exceptions to the Enterprise Reference Terminology 
  (ERT) team for resolution.  There are three exceptions/events that result 
  in the Lab package using the API.  They are: 
  
    1) Error encountered while loading ERT mapped SCT code into 
       the target database 
    2) Loading new/additional terms received from another system 
       via HL7 messaging 
    3) New terms are entered locally 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SNOMED CT
KEYWORDS: EXCEPTION
COMPONENT/ENTRY POINT: LABXCPT(ARRAY,TASKIT)
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   
  As Input 
  --------
  Name of array containing information about 
  the exception (FULL GLOBAL REFERENCE) 
  
    @ARRAY@(ETC, n) = 
        Transaction number ^ Time stamp 
    @ARRAY@(ETC, n, [x, y, ...]) = 
        Exception specific nodes 
        (defined below) 
  
      ETC is a code denoting the type of 
      exception to report 
        1 = Load Exception 
        2 = Reference Lab 
        3 = Add/Edit by Site 
  
      Time Stamp is in FileMan format 
  
  As Output 
  ---------
  * The node @ARRAY@("XMZ") will be set 
    equal to the message number of the 
    generated message.  A value of zero (0) 
    will be used when the message could not be 
    generated.  
  
  * The node @ARRAY@("ZTSK") will be set equal 
    to the task number assigned if the TASKIT 
    variable is set to one (1).  A value of 
    zero (0) will be used if queuing of this 
    API's work was not requested.  
  
  * The node @ARRAY@("ERROR", ETC) will be set 
    equal to NULL for input exception type 
    codes that are not supported.  
  
  * The node @ARRAY@("ERROR", ETC, n) will be 
    set equal to NULL if the exception could 
    not be handled.  This is typically set 
    because of a missing input node.  This 
    node will not be set for unsupported 
    exception type codes.  
  
  
  Notes 
  -----
  * If this is not a production system the 
    generated message will be sent to the 
    currently defined user (i.e. DUZ) 
  
  * The node @ARRAY@("ERROR") will be KILLed 
    on input 
  
  * It is assumed that the last field of any 
    given input node is not terminated by the 
    delimiter used for the node 
  
  * A pipe (|) is used as the delimiter for 
    the "SA" and "SB" nodes.  This is because 
    they mirror the layout of the SNOMED CT 
    extract report already implemented by the 
    Lab package's LR LAB SERVER option.  
  
  * A pipe (|) is used as the delimiter for 
    the "RD" node.  This is because it mirrors 
    the layout of the resolution data being 
    transmitted by STS to the Lab package for 
    loading.  
  
  
  Format of exception nodes 
  -------------------------
  
  Exception Type Code 1: Load Exception 
  =====================================
  @ARRAY@(1, n) = 
    Transaction number ^ Time stamp 
  @ARRAY@(1, n, "TXT") = 
    Text to describe why the exception was 
    generated.  Contents is up to the 
    discretion of the Lab package.  
  @ARRAY@(1, n, "SA") = 
    The pipe delimited row of data for the 
    entry that would be generated by the LR LAB 
    SERVER when fulfilling a SNOMED extract 
    report 
  @ARRAY@(1, n, "RD") = 
    The pipe delimited row of data received from 
    STS that the Lab package attempted to load 
  
  
  Exception Type Code 2: Reference Lab 
  ====================================
  @ARRAY@(2, n) = 
    Transaction number ^ Time stamp 
  @ARRAY@(2, n, "TXT") = 
    Text to describe why the exception was 
    generated.  Contents is up to the 
    discretion of the Lab package.  
  @ARRAY@(2, n, "SA") = 
    The pipe delimited row of data for the 
    entry that would be generated by the LR LAB 
    SERVER when fulfilling a SNOMED extract 
    report 
  @ARRAY@(2, n, "RL") = 
    Location type code ^ Location number ^ 
    Location name 
  @ARRAY@(2, n, "EC") = 
    Encoding characters from HL-7 message 
  @ARRAY@(2, n, "OBX", 3) = 
    Sequence 3 of received OBX segment 
  @ARRAY@(2, n, "OBX", 5) = 
    Sequence 5 of received OBX segment 
  
      Location Type Code: 
        1 = DoD              4 = IHS 
        2 = VA               5 = Other 
        3 = Non-government   6 = Unknown 
  
  
  Exception Type Code 3: Add/Edit by Site 
  =======================================
  @ARRAY@(3, n) = 
    Transaction number ^ Time stamp 
  @ARRAY@(3, n, "TXT") = 
    Text to describe why the exception was 
    generated.  Contents is up to the 
    discretion of the Lab package.  
  @ARRAY@(3, n, "SA") = 
    The pipe delimited row of data for the 
    entry that would be generated by the LR LAB 
    SERVER when fulfilling a SNOMED extract 
    report 
  @ARRAY@(3, n, "SB") = 
    Same definition as the SA node except the 
    values prior to the add/edit are used. Node 
    not present for additions.  
  
  
  Alternate ARRAY Format 
  ======================
  Array nodes that are delimited pieces of 
  data can also be broken out into their 
  individual pieces of data.  The only node 
  that CAN NOT be broken out in this manner is 
  the main node for the exception.  
     
  Using exception type code 1 (Load Exception) 
  as an example, the alternate array format 
  would be: 
  
  @ARRAY@(1, n) = 
      Transaction number ^ Time stamp 
  @ARRAY@(1, n, "TXT") = 
      Some kind of text 
  @ARRAY@(1, n, "SA", 1..N) = 
      Piece N of the SA node 
  @ARRAY@(1, n, "RD", 1..N) = 
      Piece N of the RD node 
  
  Note that the primary and alternate formats 
  can not be used at the same time for the 
  same node.  If this is done, the data will 
  be ignored and the error node for the 
  exception will be set.  
VARIABLES: TASKIT                       TYPE: Input
 VARIABLES DESCRIPTION:   Flag denoting if the work this API does should be
 queued to run 
  
   1 = Queue to run 
   0 = Run now (DEFAULT) 
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: SEP 12, 2012

NUMBER: 5027                            IA #: 5027
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: AUG 07, 2007            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA5027
  ID: VA(200,
 GENERAL DESCRIPTION:   The Scheduling Replacement Project (SRP) requires a
 DBIA with Kernel for the NEW PERSON file (#200).  
   
 When a site switches over to the new Replacement Scheduling Application (RSA)
 from legacy Scheduling, system users in file #200 who are active and have a
 VPID will be loaded into the Oracle Internet Directory associated with the
 RSAdb.  This load is accomplished by means of an RSA utility that uses a flat
 text file containing the Name and VPID for each user.  SRP must produce the
 text file via a routine that loops through the entire NEW PERSON file (#200)
 global to obtain the IEN for each record.  
   
 Note: Data needed from the NEW PERSON record is obtained via supported
 functions $$ACTIVE^XUSER, $$VPID^XUPS, and $$NAME^XUSER.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NEW PERSON
KEYWORDS: SRP
KEYWORDS: KERNEL
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   SRP must produce a text file via a routine that loops
 through the entire NEW PERSON file (#200) global to obtain the IEN for each
 record.  Once an IEN is obtained, it will be used in calls to functions
 $$ACTIVE^XUSER, $$VPID^XUPS, and $$NAME^XUSER, in order to retrieve the needed
 data.  
   
 Access to ^VA(200, is made at JOB+9^SDAMOID -- 
   
    F  S SDIEN=$O(^VA(200,SDIEN)) Q:'SDIEN  
       I (+SDIEN>.9),$D(^VA(200,SDIEN,0)) D 
   
 Routine SDAMOID is being distributed in SD*5.3*362.  
  
  DATE ACTIVATED: SEP 24, 2007

NUMBER: 5028                            IA #: 5028
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9('AST'
  DATE CREATED: AUG 21, 2007            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Controlled Subscription        TYPE: File
  NAME: 5028                            ID: ICD9('AST'
GLOBAL REFERENCE: ICD9(D0,67,D1,0)
FIELD NUMBER: .01                       FIELD NAME: VERSION DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   
   
 This is the date the diagnosis text was first used.  
 GLOBAL DESCRIPTION:   This agreement will use the "AST" cross reference from
 file #80 - 
  
 ^ ICD9("AST",(CODE_" "),EFF,IEN1,IEN2) 
 GENERAL DESCRIPTION:   
   
 This agreement will allow Problem List to determine if a particular ICD9 code
 has a new description change.  This agreement is to view the cross reference
 "AST" to determine if a new description exits.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: AST
SUBSCRIBING PACKAGE: PROBLEM LIST

NUMBER: 5029                            IA #: 5029
  FILE NUMBER: 352.1                    GLOBAL ROOT: IBE(352.1,
  DATE CREATED: AUG 23, 2007            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VERIFY SC APPOINTMENT TYPE
  ID: IBE(352.1,
GLOBAL REFERENCE: IBE(352.1,11,0)
 GLOBAL DESCRIPTION:   => '11^11^2880101^0^1^1'  Entire node accessed to
 determine validity.  
 GENERAL DESCRIPTION:   Scheduling requires one time access to the Billable
 Appointment Type file to verify that the Service Connected entry is correctly
 defined.  This entry was created to correspond to the new Service Connected
 Appointment Type but may have been incompletely added if there were local
 changes to the Billable Appointment Type file.  
   
 The Scheduling patch SD*5.3*491 post-init will access the SERVICE CONNECTED
 (#11) node of the BILLABLE APPOINTMENT TYPE (#352.1) file to verify that it
 was correctly created and points to the SERVICE CONNECTED (#11) entry of the
 APPOINTMENT TYPE (#409.1) file.  
   
 This agreement will expire at the end of the SD*5.3*491 compliance date.  
   
  STATUS: Active                        DURATION: Next Version
  EXPIRATION DATE: APR 28, 2009         GOOD ONLY FOR VERSION: SD*5.3*491
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: JUL 28, 2008
REMINDER: APR 28, 2009

NUMBER: 5030                            IA #: 5030
  DATE CREATED: SEP 05, 2007            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: Routine
  ROUTINE: BPS01P5C                     NAME: GETEPHRM
  ID: BPS01P5C
 GENERAL DESCRIPTION:   This API was designed exclusively to serve IB*2.0*363
 post-installation process. Thus usage of this API is limited to the IB*2.0*363
 post-install routine IB20P363.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2007
KEYWORDS: ECME
KEYWORDS: EPHARMACY
COMPONENT/ENTRY POINT: GETEPHRM
 COMPONENT DESCRIPTION:   Get ePharmacy ien by RX# ien, refill number and date
 of service.  
VARIABLES: BPSDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Date of Service 
VARIABLES: BPSRXIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   PRESCRIPTION file #52 ien 
VARIABLES: BPSREF                       TYPE: Input
 VARIABLES DESCRIPTION:   Refill number (0 - for original) 
VARIABLES: $$GETEPHRM                   TYPE: Output
 VARIABLES DESCRIPTION:   Returns ien of #9002313.56 BPS PHARMACIES or zero (0)
 if not found.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 5031                            IA #: 5031
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: SEP 18, 2007            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: DBIA5031                        ID: DPT(
 GENERAL DESCRIPTION:   Outpatient Pharmacy has a need to add the PHONE NUMBER
 [CELLULAR] field #.134 from the PATIENT file #2 to their patient information
 screen.  They have permission to display, modify and delete this field using 
 FileMan.  
  
 2,.134        PHONE NUMBER [CELLULAR] .13;4 FREE TEXT 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 5032                            IA #: 5032
  FILE NUMBER: 8994.5                   GLOBAL ROOT: XWB
  DATE CREATED: SEP 24, 2007            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: REMOTE APPLICATION REGISTRATION
  ID: XWB
 GENERAL DESCRIPTION:   This Integration Control Registration was created to
 add an entry in the file 8994.5.  
  
 The entry in this file will allow the RPC Broker code in the host VistA system
 to validate authentication requests for remote user access, and is done in
 accordance with instructions on the use of the Broker Security Enhancement as
 provided by the VistA Kernel team.  
  
 The file entry contains the name of the application, the application code 
 (encrypted), method of authentication, and authentication server IP, port, and
 entry point.  
  
 Revision History: 
  - 3/5/25: VISS team notes that this ICR will be replaced by a future solution
 currently defined in patch XU*8*759 REMOTE APPLICATION ENHANCEMENT. BSE
 bypasses and not enhances VistA Kernel Security, as VistA is site-centric,
 where sites control security of users and their applications.  BSE bypasses
 many of the components of VistA Kernel Security and site-level security.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTAWEB
KEYWORDS: REMOTE APPLICATION
KEYWORDS: SCHEDULING
KEYWORDS: CAPRI
KEYWORDS: IMAGING
KEYWORDS: NUMI
KEYWORDS: BMS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   VistaWeb operates under the auspices of Order Entry
 (OR) and CPRS, and uses the menu option OR CPRS GUI CHART (the same that CPRS
 uses).  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI uses the SDECRPC menu option.  
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   VistA Imaging uses the MAG WINDOWS menu option.  
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   CAPRI operates under the auspices of AUTOMATED MED INFO
 EXCHANGE (DVBA) and uses the menu option DVBA CAPRI GUI.  
SUBSCRIBING PACKAGE: BED MANAGEMENT SOLUTION
 SUBSCRIBING DETAILS:   BMS uses the WEBB BED MGMT SOLUTION menu option.  
SUBSCRIBING PACKAGE: NAT'L UTILIZATION MGMT INTEG
 SUBSCRIBING DETAILS:   NUMI uses the WEBN NATL UTIL MGMT INTEG menu option.  
SUBSCRIBING PACKAGE: INFORMED CONSENT WEB
 SUBSCRIBING DETAILS:   Informed Consent Web adds "INFORMED CONSENT WEB (ICW)
 VDIF ACCESS" to the REMOTE APPLICATION file with patch ICW*1.0*0. The
 "INFORMED CONSENT WEB (ICW) VDIF ACCESS" entry in the REMOTE APPLICATION file
 will use the "INFORMED CONSENT WEB (ICW) OPEN CONTEXT" entry in the OPTION
 file (#19) when setting broker context for visitors added to the New Person
 file.  
SUBSCRIBING PACKAGE: ADVANCED MEDICATION PLATFORM
 SUBSCRIBING DETAILS:   Added 8/5/20 to support the Advanced Medication
 Platform (AMPL) project. 
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 3/5/25 effective with patch YS*5.01*236 post
 install, to create a new Remote Application (#8994.5) entry, for "MENTAL
 HEALTH ASSISTANT" using context option YTQREST PATIENT ENTRY for the entry.  
  DATE ACTIVATED: OCT 24, 2007

NUMBER: 5033                            IA #: 5033
  FILE NUMBER: 8925.1                   GLOBAL ROOT: TIU(8925.1
  DATE CREATED: OCT 02, 2007
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Allow lookup with FileMan on file #8925.1
  ID: TIU(8925.1
GLOBAL REFERENCE: TIU(8925.1
 GENERAL DESCRIPTION:   
  Allow lookup with FileMan on the TIU DOCUMENT DEFINITION file (#8925.1) 
  to get Title IFN in file 8925.1 to create a TIU document- 
  Lab Anatomic Pathology Report.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: MAR 24, 2008

NUMBER: 5034                            IA #: 5034
  DATE CREATED: OCT 04, 2007            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: YTQPXRM1
  NAME: OCCUR-YTQPXRM1                  ID: YTQPXRM1
 GENERAL DESCRIPTION:   Report ocuurances of selected Mental Health instrument
 for a specific time frame.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MHA3
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: OCCUR
COMPONENT/ENTRY POINT: OCCUR
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   test code NUMBER from 601.71 including ASI and GAF 
VARIABLES: BEGIN                        TYPE: Input
 VARIABLES DESCRIPTION:   inclusive date in %DT acceptable format[optional] 
VARIABLES: END                          TYPE: Input
 VARIABLES DESCRIPTION:   inclusive date in %DT acceptable format[optional] 
VARIABLES: LIMIT                        TYPE: Input
 VARIABLES DESCRIPTION:   last N administrtations [defaults to 1] 
COMPONENT/ENTRY POINT: OCCUR(YSDATA,YS)
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: DEC 18, 2007

NUMBER: 5035                            IA #: 5035
  DATE CREATED: OCT 04, 2007            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: YTQPXRM2
  NAME: MHA3-CR data for a specified Patient
  ID: YTQPXRM2
 GENERAL DESCRIPTION:   All MHA3/mha data for a selected patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PTTEST
KEYWORDS: MHA3
KEYWORDS: CLINICAL REMINDERS
COMPONENT/ENTRY POINT: PTTEST(YSDATA,YS)
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IFN 
VARIABLES:  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Test code NUMBER from 601.71 including ASI and GAF 
VARIABLES: BEGIN                        TYPE: Input
 VARIABLES DESCRIPTION:   DATE in %DT format [optional] 
VARIABLES: END                          TYPE: Input
 VARIABLES DESCRIPTION:   DATE in %DT format [optional] 
VARIABLES: LIMIT                        TYPE: Input
 VARIABLES DESCRIPTION:   Number of entries to return 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************** 
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                   
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
 ****************************************************
  DATE ACTIVATED: DEC 18, 2007

NUMBER: 5036                            IA #: 5036
  DATE CREATED: OCT 23, 2007            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGENRDUA
  NAME: ENROLLMENT RATED DISABILITY UPLOAD AUDIT REPORTING
  ID: DGENRDUA
 GENERAL DESCRIPTION:   This API will provide Rated Disability changes from the
 ENROLLMENT RATED DISABILITY UPLOAD AUDIT file (#390) for a single or multiple
 Veterans.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RDCHG(DFN,FDT,TDT)
 COMPONENT DESCRIPTION:   
 ****************************************************************
 NOTE:  It is the responsibility of the calling application to 
        kill the ^TMP($J,"RDCHG") global reference prior to 
        calling this api and also after the calling routine is 
        done with the global reference.  
 ****************************************************************
 Input 
    DFN    - Patients DFN (Optional, If not passed return all vets) 
    FDT    - Beginning Date Range (Optional) 
    TDT    - Ending Date Range (Optional) 
  
 Output 
    DFN = Pointer to PATIENT file (#2) 
    OCC = Single occurrence of a Rated Disability change for Veteran 
  
    ^TMP($J,"RDCHG",DFN,OCC)=P1^P2^P3^...etc 
         Where:  P1 = DATE/TIME OF CHANGE (fileman format) 
                 P2 = RATED DISABILITIES CODE (external value) 
                 P3 = RATED DISABILITIES NAME (external value) 
                 P4 = DISABILITY % (numeric value) 
                 P5 = EXTREMITY AFFECTED (internal code) 
                 P6 = EXTREMITY AFFECTED (external code) 
                 P7 = ORIGINAL EFFECTIVE DATE (fileman format) 
                 P8 = CURRENT EFFECTIVE DATE (fileman format) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patients DFN (Optional, If not passed return all
 vets) 
VARIABLES: FDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Beginning Date Range (Optional) 
VARIABLES: TDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Ending Date Range (Optional) 
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: FEB 06, 2008

NUMBER: 5037                            IA #: 5037
  GLOBAL ROOT: DD(130,.04               DATE CREATED: OCT 24, 2007
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File
  NAME: VISTAWEB/CPRS SURGERY DETAIL ACCESS
  ID: DD(130,.04
 GENERAL DESCRIPTION:   VISTAWEB/CPRS report routines need access to
 ^DD(130,.04,0 for a formatted surgery report detail, retrieved using classic
 Fileman API Y^DIQ.  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: VISTAWEB
KEYWORDS: DD
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 5038                            IA #: 5038
  GLOBAL ROOT: DD(                      DATE CREATED: NOV 06, 2007
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: LEXICON READ OF DD(D0,0,'IX')   ID: DD(
GLOBAL REFERENCE: DD(D0,0,'IX')
 GLOBAL DESCRIPTION:   DD(D0,0,'IX') - Where D0 is the number of a Lexicon
 file, and the 'IX' subscript contains a listing of Lexicon fields that are
 cross-referenced.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LEXICON
KEYWORDS: IX
KEYWORDS: DD
KEYWORDS: DATA
KEYWORDS: DICTIONARY
SUBSCRIBING PACKAGE: LEXICON UTILITY
 SUBSCRIBING DETAILS:   
  Lexicon needs to be able to obtain the field number 
  that contains a classic Fileman cross-reference by 
  a direct global read of the Lexicon's Data Dictionary 
  (DD) 0 node, 'IX' subscripts.  
  
    ^DD(<file>,0,'IX',<file/sub-file>,<field>) 
  
  The Lexicon has become so large that conventional 
  Re-indexing by Kill/Set logic needs to be replaced 
  with Index Repair logic, avoiding the killing of a 
  cross-reference and allowing users to stay on the 
  system without loss of access to the Lexicon package.  
  
  DATE ACTIVATED: NOV 07, 2007

NUMBER: 5039                            IA #: 5039
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: NOV 07, 2007            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: AR Access to Patient File
  ID: DPT(
GLOBAL REFERENCE: DPT(D0,.3)
FIELD NUMBER: .3014                     FIELD NAME: EFF. DATE COMBINED SC% EVAL.
  LOCATION: .3;14                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the date that the combined Service Connected
 Disability % was awarded.  
GLOBAL REFERENCE: DPT(D0,.31)
FIELD NUMBER: .314                      FIELD NAME: CLAIM FOLDER LOCATION
  LOCATION: .31;4                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the location of the patient's claim folder.  It
 must be an entry in the INSTITUTION File.  
 GENERAL DESCRIPTION:   For the Hold Debt to DMC project the Accounts
 Receivable (AR) software package is providing some new reports for the AR
 clerks to use when evaluating bills for veterans who are Service Connected 50%
 to 100% or receiving a VA Pension. For these new reports the Business Office 
 requested that AR include 2 fields from the Patient (#2) file for which there
 currently isn't a Public DBIA and the data elements are not included with the
 VADPT API.  
  
 AR would like direct global access using Fileman to the following fields in
 the Patient (#2) file: 
      CLAIM FOLDER LOCATION (#.314) 
      EFF. DATE COMBINED SC% EVAL. (#.3014) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CLAIM FOLDER LOCATION
KEYWORDS: EFF. DATE COMBINED SC% EVAL.
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: NOV 13, 2007

NUMBER: 5040                            IA #: 5040
  FILE NUMBER: 409.68                   GLOBAL ROOT: SCE(
  DATE CREATED: NOV 07, 2007            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: AR Access to the Outpatient Encounter File
  ID: SCE(
GLOBAL REFERENCE: SCE(D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the date and time when outpatient
 encounter occurred.  
 GENERAL DESCRIPTION:   For the Hold Debt to DMC project the Accounts
 Receivable (AR) software package is providing some new reports for the AR
 clerks to use. For these new reports the Business Office requested that AR
 include bills that have an episode of care within the previous 365 days and if
 appropriate display the date of the most recent Outpatient Encounter. This is
 to be done using the RESULTING FROM (#.04) field in the INTEGRATED BILLING
 ACTION (#350) file which contains a soft-link back to the entry in any file
 that caused this billing transaction to be set. One of these soft-links is to
 the OUTPATIENT ENCOUNTER (#409.68) file which relates to DBIA 402 subscribed 
 to by the Integrated Billing package.  
  
 The AR package requires access to the DATE (#.01) field of the OUTPATIENT 
 ENCOUNTER (#409.68) based on its interface with the IB package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: DEC 13, 2007

NUMBER: 5041                            IA #: 5041
  DATE CREATED: JAN 11, 2011
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MPIFA28
  NAME: GET NEW ICN FROM MPI            ID: MPIFA28
 GENERAL DESCRIPTION:   This is used by  Single Patient Registration, whenever
 a new patient is created. If an ICN is not passed in, a request is made to to
 the National MPI for a new ICN.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: A28
 COMPONENT DESCRIPTION:   This API creates and sends an ADT-A28 HL7 message to
 the national MPI.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN    the patient record ien in File#2.  
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   FILEICN (a subroutine of JVDGF) is used to add an ICN
 to a patient record.  The following line in FILEICN makes the call: 
  
 D A28^MPIFA28(+NWDFN 
  
 This request a new ICN from the National MPI.  
  DATE ACTIVATED: MAR 01, 2011

NUMBER: 5042                            IA #: 5042
  DATE CREATED: NOV 08, 2007            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: YTQPXRM3
  NAME: YTQPXRM3                        ID: YTQPXRM3
  STATUS: Active
KEYWORDS: SHOW ALL
KEYWORDS: TEST DESCRIPTION
COMPONENT/ENTRY POINT: QUESTALL(YSDATA,YS)
 COMPONENT DESCRIPTION:   DESCRIPTION:   
  Retuns Item text, Intro, Choicetypes and Display information for all 
  Questions in a Specified Instrument.  
   
  Input: YS("CODE"):As test name 
   
  Output: YSDATA(1)=[DATA] or [ERROR] 
          YSDATA(2)="NUMBER OF QUESTIONS="_N3 
          YSDATA(3)=QUESTION NUMBER1=ien for MH Question^QUESTION 
                    SEQUENCE^DESIGNATOR 
          YSDATA(4)=QUESTION TEXT1=fIRST line of text 
          YSDATA(5)=additional text lines as needed 
          YSDATA(6)=INTRO TEXT1=IEN FOR MH INTRO^First intro line 
          YSDATA(7)=additional intro lines as needed 
          YSDATA(8)=DESC1=Respone Type^CHOICETYPE^MIN^MAX^IS REQUIRED 
                  ^HINT^CHOICEIDENTIFIER 
          YSDATA(9)=QDISPLAY1=DisplayId^FontName^FontBold^FontItalic 
                    ^FontUnderlined ^ Fontsize^FontColor ^Alignment 
                    ^left^Mask^Colums^Component (for question text) 
          YSDATA(10)=IDISPLAY1=DisplayId^FontName^FontBold^FontItalic 
                    ^FontUnderlined ^Fontsize^FontColor^Alignment 
                    ^left^Mask^Colums^Component (for intro text) 
          YSDATA(11)=CDISPLAY1=DisplayId^FontName^FontBold^FontItalic 
                     ^FontUnderlined ^Fontsize^FontColor^Alignment 
                     ^left^Mask^Colums^Component (for choice) 
          :
          Repeat for each item in test 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Name of Instrumnet IN 601.71 
VARIABLES: YSDATA                       TYPE: Output
 VARIABLES DESCRIPTION:   DESCRIPTION:   
  Output: YSDATA(1)=[DATA] or [ERROR] 
          YSDATA(2)="NUMBER OF QUESTIONS="_N3 
          YSDATA(3)=QUESTION NUMBER1=ien for MH Question^QUESTION 
                    SEQUENCE^DESIGNATOR 
          YSDATA(4)=QUESTION TEXT1=fIRST line of text 
          YSDATA(5)=additional text lines as needed 
          YSDATA(6)=INTRO TEXT1=IEN FOR MH INTRO^First intro line 
          YSDATA(7)=additional intro lines as needed 
          YSDATA(8)=DESC1=Respone Type^CHOICETYPE^MIN^MAX^IS REQUIRED 
                  ^HINT^CHOICEIDENTIFIER 
          YSDATA(9)=QDISPLAY1=DisplayId^FontName^FontBold^FontItalic 
                    ^FontUnderlined ^ Fontsize^FontColor ^Alignment 
                    ^left^Mask^Colums^Component (for question text) 
          YSDATA(10)=IDISPLAY1=DisplayId^FontName^FontBold^FontItalic 
                    ^FontUnderlined ^Fontsize^FontColor^Alignment 
                    ^left^Mask^Colums^Component (for intro text) 
          YSDATA(11)=CDISPLAY1=DisplayId^FontName^FontBold^FontItalic 
                     ^FontUnderlined ^Fontsize^FontColor^Alignment 
                     ^left^Mask^Colums^Component (for choice) 
          :
          Repeat for each item in test 
COMPONENT/ENTRY POINT: OLDNEW(YSCODEN,YSOLDNUM)
 COMPONENT DESCRIPTION:   returns new scale ien for older intruments 
  
          input YSCODEN ien OF 601.71 
                YSOLDNUM as ien of "S" MULT of 601 (1= DEFAULT) 
          output ien OF 601.87, 0=ERROR 
VARIABLES: YCODEN                       TYPE: Input
 VARIABLES DESCRIPTION:   
          input YSCODEN ien OF 601.71 
VARIABLES: YSOLDNUM                     TYPE: Input
 VARIABLES DESCRIPTION:   
              YSOLDNUM as ien of "S" MULT of 601 (1= DEFAULT) 
COMPONENT/ENTRY POINT: RL(YSCODEN)
 COMPONENT DESCRIPTION:   RL(YSCODEN) ;requires license 
          ;input YSCODEN ien OF 601.71 
          ;output  Y/N/0 
VARIABLES: YSCODEN                      TYPE: Input
 VARIABLES DESCRIPTION:   
          input YSCODEN as ien OF 601.71 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 9/19/23, to use the QUESTALL^YTQPXRM3 and
 RL^YTQPXRM3 calls to retrieve information about a specific test. 
  DATE ACTIVATED: DEC 18, 2007

NUMBER: 5043                            IA #: 5043
  DATE CREATED: NOV 08, 2007            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: YTQPXRM6
  NAME: YTQPXRM6                        ID: YTQPXRM6
  STATUS: Active
KEYWORDS: SCORING
KEYWORDS: DAS
KEYWORDS: MHA2
KEYWORDS: MHA3
COMPONENT/ENTRY POINT: ENDAS71(YSDATA,DAS)
 COMPONENT DESCRIPTION:   ENDAS71(YSDATA,DAS) ;single administration output 
          ;Input 
          ;DAS from ^PXRMINDX( 
          ;Output: 
          ;Array(1)=[DATA] 
          ;Array(2)= Patient Name^Test Code^Test Title^Internal Admin 
            date^External Admin Date ^Ordered by 
          ;Array("R",running number)=MH Administration IEN^MH Answer 
           IEN^MH Question IEN^MH Choice IEN [if avail]^MH Legacy answer 
           [single character answer is available^text of answer [first 200 
           chars] 
          ;Array("SI",601.87 IEN)=S_running number1^Scale Name^Raw 
           Score^Transformed Score 
VARIABLES: DAS                          TYPE: Input
 VARIABLES DESCRIPTION:   DAS from ^PXRMINDX( 
COMPONENT/ENTRY POINT: CONVERT(YSDATA,YS)
 COMPONENT DESCRIPTION:   CONVERT(YSDATA,YS) ;convet 601 ien into 601.71 iens 
          ;input YS601 AS 601 IEN 
          ;output 601.71 ien 
VARIABLES: YS601                        TYPE: Input
 VARIABLES DESCRIPTION:   INPUT ien OF 601 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
 **************************************************** 
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                   
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
 ****************************************************
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 9/19/23, to use the ENDAS71^YTQPXRM6 call to get
 the details about an individual test administration for a patient. 
  DATE ACTIVATED: DEC 18, 2007

NUMBER: 5044                            IA #: 5044
  FILE NUMBER: 601.71                   GLOBAL ROOT: YTT(601.71
  DATE CREATED: NOV 08, 2007            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MH TESTS AND SURVEYS ZERO
  ID: YTT(601.71
GLOBAL REFERENCE: YTT(601.71,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
 FIELD DESCRIPTION:   Name of the mental health instrument.  
FIELD NUMBER: 2                         FIELD NAME: PRINT TITLE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Full name of the mental health instrument.  
 GENERAL DESCRIPTION:   Read only ^YTT(601.71,IFN,0) and point to ^YTT(601.71) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TOP NODE
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: NOV 20, 2017

NUMBER: 5045                            IA #: 5045
  FILE NUMBER: 79.2                     GLOBAL ROOT: RA(79.2
  DATE CREATED: NOV 09, 2007
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ ACCESS TO IMAGING TYPE FILE
  ID: RA(79.2
GLOBAL REFERENCE: RA(79.2,S1,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 1                           ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   In preparation for releasing OR*3*243 (GUI v27), a
 routine is needed to assist the sites in making corrections to existing
 Radiology and Imaging quick orders.  
  
 In order to do this, access to the IMAGING TYPE file (79.2) is needed in a
 slightly different way than currently allowed.  
  
 The search routine needs access to the B cross-reference and then to the NAME
 field (.01).  
  
 This would be a one-time IA for the installation of OR*3*281.  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: CPRS v26
KEYWORDS: 79.2
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   This IA must be retired upon the release of CPRS v27.  
  DATE ACTIVATED: NOV 20, 2007
REMINDER: JAN 20, 2008

NUMBER: 5046                            IA #: 5046
  DATE CREATED: NOV 14, 2007
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMVUTL
  NAME: GMVUTL                          ID: GMVUTL
 GENERAL DESCRIPTION:   The CLIO, F1250 and GETREC entry points return a
 patient vitals record in an array. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CLIO(ARRAY,GUID)
 COMPONENT DESCRIPTION:   This entry point looks for the patient record in the
 Clinical Observations package.  
  
  Output format: 
  ARRAY(0)=A^B^C^D^E^F^G^H^I^J 
  ARRAY(2)=K^L^M 
  ARRAY(5)=N1^N2^N3^N4 
   where: 
   A=Date/time of the reading, internal FileMan format (Field .01) 
   B=DFN, pointer to FILE 2 (Field .02) 
   C=Vital type pointer to FILE 120.51 (Field .03) 
   D=Date/time the record was created, internal FileMan format (Field .04) 
   E=Hospital location pointer to File 44 (Field .05) 
   F=DUZ of person who created the record, pointer to FILE 200 (Field .06) 
   G=always null 
   H=reading (number or text) (Field 1.2) 
   I=always null 
   J=Supplemental Oxygen (text) (Field 1.4) 
   K=1 means record is marked as an error and null means not an error 
     (Field 2) 
   L=DUZ of person who marked the record as an error, pointer to FILE 200 
     (Field 3) 
   M=Set of codes to indicate reason for error. If more than one reason, 
     the values are delimited by a tilde (~). (Field 4) 
   N1-N4=Qualifier pointer values delimited by up-arrow (^), pointer to 
         FILE 120.52. (Field 5) 
  
  Example: 
  >D CLIO^GMVUTL(.ARRAY,"{A0E99B2C-9FF6-47DA-8CD2-DDB0E8756DC5}") 
  >ZW ARRAY 
  >ARRAY(0)="3071101.14^1^22^3071101.155936^125^222222311^^1" 
  >ARRAY(2)="^^" 
  >ARRAY(5)="" 
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of the array to return the record
 in. It is passed by reference. (Required) 
VARIABLES: GUID                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the Global Unique ID (aka GUID) that
 identifies a record in the Clinical Observations package. (Required) 
COMPONENT/ENTRY POINT: F1205(ARRAY,IEN,ERRORS)
 COMPONENT DESCRIPTION:   This entry point looks for the patient record in the
 Vitals package (FILE 120.5).  
  
  Output format: 
  ARRAY(0)=A^B^C^D^E^F^G^H^I^J 
  ARRAY(2)=K^L^M 
  ARRAY(5)=N1^N2^N3^N4 
   where: 
   A=Date/time of the reading, internal FileMan format (Field .01) 
   B=DFN, pointer to FILE 2 (Field .02) 
   C=Vital type pointer to FILE 120.51 (Field .03) 
   D=Date/time the record was created, internal FileMan format (Field .04) 
   E=Hospital location pointer to File 44 (Field .05) 
   F=DUZ of person who created the record, pointer to FILE 200 (Field .06) 
   G=always null 
   H=reading (number or text) (Field 1.2) 
   I=always null 
   J=Supplemental Oxygen (text) (Field 1.4) 
   K=1 means record is marked as an error and null means not an error 
     (Field 2) 
   L=DUZ of person who marked the record as an error, pointer to FILE 200 
     (Field 3) 
   M=Set of codes to indicate reason for error. If more than one reason, 
     the values are delimited by a tilde (~). (Field 4) 
   N1-N4=Qualifier pointer values delimited by up-arrow (^), pointer to 
         FILE 120.52. (Field 5) 
  
  
  Example: 
   >D F1205^GMVUTL(.ARRAY,12089,0) 
   >ZW ARRAY 
   >ARRAY(0)="3071108.162622^398^3^3071108.162708^4^547^^6^^" 
   >ARRAY(2)="^^" 
   >ARRAY(5)="47^50" 
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of the array to return the record
 in. It is passed by reference. (Required) 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the FILE 120.5 internal entry number for the
 desired record. (Required) 
VARIABLES: ERRORS                       TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag to specify whether records that are
 marked as errors should be returned. If this value is 0 (zero), the record
 will not be returned if it is marked as an error. If this value is 1 (one) the
 record will be returned even if it is marked as an error. The default is 0. 
 (Optional) 
COMPONENT/ENTRY POINT: GETREC(GMVARRAY,GMVID,GMVERR)
 COMPONENT DESCRIPTION:   This entry point checks the Vitals (File 120.5) and
 Clinical Observation databases for the specified record ID. The internal
 values of the record are returned.  
  
 Output format: 
  GMVARRAY(0)=A^B^C^D^E^F^G^H^I^J 
  GMVARRAY(2)=K^L^M 
  GMVARRAY(5)=N1^N2^N3^N4 
  
  where: 
  A=Date/time of the reading, internal FileMan format (Field .01) 
  B=DFN, pointer to FILE 2 (Field .02) 
  C=Vital type pointer to FILE 120.51 (Field .03) 
  D=Date/time the record was created, internal FileMan format (Field .04) 
  E=Hospital location pointer to File 44 (Field .05) 
  F=DUZ of person who created the record, pointer to FILE 200 (Field .06) 
  G=always null 
  H=reading (number or text) (Field 1.2) 
  I=always null 
  J=Supplemental Oxygen (text) (Field 1.4) 
  K=1 means record is marked as an error and null means not an error 
    (Field 2) 
  L=DUZ of person who marked the record as an error, pointer to FILE 200 
    (Field 3) 
  M=Set of codes to indicate reason for error. If more than one reason, 
    the values are delimited by a tilde (~). (Field 4) 
  N1-N4=Qualifier pointer values delimited by up-arrow (^), pointer to 
        FILE 120.52. (Field 5) 
                                 
  Example: 
  >D GETREC^GMVUTL(.GMVARRAY,12089,0) 
  >ZW GMVARRAY 
  >GMVARRAY(0)="3071108.162622^398^3^3071108.162708^4^547^^6^^" 
  >GMVARRAY(2)="^^" 
  >GMVARRAY(5)="47^50" 
VARIABLES: GMVARRAY                     TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of the array to return the values
 in. Passed by reference. (required) 
VARIABLES: GMVID                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the ID of the record to lookup. It is either
 a File 120.5 internal entry number (.001) or a Global Unique ID (aka GUID) for
 the Clinical Observations database (File 704.117, Field .01). (required) 
VARIABLES: GMVERR                       TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag to determine if records marked as
 errors should be returned. 0 means ignore the record and 1 means get the
 record data. The default is 0. (optional) 
  DATE ACTIVATED: MAR 19, 2008

NUMBER: 5047                            IA #: 5047
  DATE CREATED: NOV 14, 2007
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMVGETVT
  NAME: GMVGETVT                        ID: GMVGETVT
 GENERAL DESCRIPTION:   APIs that return values for vital types (FILE 120.51).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: FIELD(IEN,FIELD,FORMAT)
 COMPONENT DESCRIPTION:   Returns the value for the record and field in the
 format specified. Returns -1 if there is an error.  
  
  Example: 
   >W $$FIELD^GMVGETVT(1,1,"E")  
   >BLOOD PRESSURE 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The FILE 120.51 internal entry number. (Required) 
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   A set of codes to indicate which field value to
 return. (Required) 
  Where: 
   1=Name (.01) 
   2=Abbreviation (1) 
   3=PCE Abbreviation (7) 
   4=VUID (99.99) 
   5=Master Entry For VUID (99.98)  
VARIABLES: FORMAT                       TYPE: Input
 VARIABLES DESCRIPTION:   A set of codes to indicate if the internal or
 external value of the field should be returned. (Optional) 
  Where: 
   I=Internal 
   E=External 
   Default is E.  
COMPONENT/ENTRY POINT: GETIEN(VALUE,TYPE)
 COMPONENT DESCRIPTION:   Returns the vital type (FILE 120.51) pointer value.
 Returns null if not found and -1 if there is an error.  
  
  Example: 
   >W $$GETIEN^GMVGETVT("TEMPERATURE",1)   
   >2 
VARIABLES: Value                        TYPE: Input
 VARIABLES DESCRIPTION:   The value to use to do the lookup. (Required) 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   A set of codes to indicate the type of value it is.
 (Required) 
  Where: 
   1=Name (.01) 
   2=Abbreviation (1) 
   3=PCE Abbreviation (7) 
   4=VUID (99.99) 
COMPONENT/ENTRY POINT: LIST(ARRAY,FORMAT)
 COMPONENT DESCRIPTION:   Returns an array with the vital types currently
 tracked.  
  
  Output format: 
   GMVARRAY(0)=piece1 
   GMVARRAY(n)=piece2^piece3^piece4^piece5^piece6^piece7 
    where: 
         n=a sequential number starting with 1 
    piece1=number of entries found 
    piece2=FILE 120.51 internal entry number (.001) 
    piece3=Name (.01) 
    piece4=Abbreviation (1) 
    piece5=PCE Abbreviation (7) 
    piece6=VUID (99.99) 
    piece7=Master Entry for VUID (99.98) 
  
  Example: 
   >D LIST^GMVGETVT(.ARRAY,"E") 
   >ZW ARRAY 
   >ARRAY(0)=10 
   >ARRAY(1)="1^BLOOD PRESSURE^BP^BP^4500634^YES" 
   >ARRAY(2)="19^CENTRAL VENOUS PRESSURE^CVP^^4688719^YES" 
   >ARRAY(3)="20^CIRCUMFERENCE/GIRTH^CG^^4688720^YES" 
   >ARRAY(4)="8^HEIGHT^HT^HT^4688724^YES" 
   >ARRAY(5)="22^PAIN^PN^PN^4500635^YES" 
   >ARRAY(6)="5^PULSE^P^PU^4500636^YES" 
   >ARRAY(7)="21^PULSE OXIMETRY^PO2^PO2^4500637^YES" 
   >ARRAY(8)="3^RESPIRATION^R^RS^4688725^YES" 
   >ARRAY(9)="2^TEMPERATURE^T^TMP^4500638^YES" 
   >ARRAY(10)="9^WEIGHT^WT^WT^4500639^YES" 
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   The name of the array to return the values in.
 (Required) 
VARIABLES: FORMAT                       TYPE: Input
 VARIABLES DESCRIPTION:   A set of codes to indicate if the internal or
 external values should be returned. (Optional) 
  Where: 
   I=Internal (the default) 
   E=External 
COMPONENT/ENTRY POINT: TYPES()
 COMPONENT DESCRIPTION:   Returns a list of abbreviations as a string delimited
 by up-arrows for the vitals types currently tracked in the package. There are
 no input parameters.  
  
  Example: 
  >W $$TYPES^GMVGETVT() 
  >BP^CG^CVP^HT^P^PN^PO2^R^T^WT 
  DATE ACTIVATED: MAR 19, 2008

NUMBER: 5048                            IA #: 5048
  DATE CREATED: NOV 14, 2007
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMVGETQL
  NAME: GMVGETQL                        ID: GMVGETQL
 GENERAL DESCRIPTION:   APIs that return values for qualifiers (FILE 120.52).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: FIELD(IEN,FIELD,FORMAT)
 COMPONENT DESCRIPTION:   Returns the value for the record and field in the
 format specified.  
  
  Example: 
  >W $$FIELD^GMVGETQL(1,1,"E") 
  >R ARM 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The FILE 120.52 internal entry number. (Required) 
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   A set of codes to indicate which field value to
 return. (Required) 
  Where: 
   1=name(.01) 
   2=Synonym (.02) 
   3=VUID (99.99) 
   4=Master Entry For VUID 
VARIABLES: FORMAT                       TYPE: Input
 VARIABLES DESCRIPTION:   A set of codes to indicate if the internal or
 external value of the field should be returned. (Optional) 
  Where: 
   I=Internal 
   E=External (the default) 
COMPONENT/ENTRY POINT: GETIEN(VALUE,TYPE)
 COMPONENT DESCRIPTION:   Returns the qualifier (FILE 120.52) pointer value.
 Returns null if not found. Returns -1 if there is an error.  
  
  Example: 
   >W $$GETIEN^GMVGETQL("L ARM",1) 
   >2 
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   The value to use to do the lookup. (Required) 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   A set of codes to indicate the type of value it
 returns. (Required) 
  Where: 
   1=name (.01) 
   2=VUID (99.99) 
COMPONENT/ENTRY POINT: VT(ARRAY,IEN)
 COMPONENT DESCRIPTION:   Returns the vital types and category values for the
 specified qualifier.  
  
  Output format: 
   ARRAY(0)=piece1 
   ARRAY(n)=piece2^piece3^piece4^piece5 
   where: 
          n=sequential number starting with 1 
     piece1=number of entries found or -1 if an error 
     piece2=File 120.51 entry number 
     piece3=File 120.51 .01  field value 
     piece4=File 120.53 entry number 
     piece5=File 120.53 .01 field value 
  
  Example: 
   >D VT^GMVGETQL(.ARRAY,1)          
   >ZW ARRAY 
   >ARRAY(0)=1 
   >ARRAY(1)="1^BLOOD PRESSURE^1^LOCATION" 
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   The name of the array to return the values in.
 (Required) 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The FILE 120.52 internal entry number. (Required) 
  DATE ACTIVATED: MAR 19, 2008

NUMBER: 5049                            IA #: 5049
  DATE CREATED: JAN 11, 2011
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MPIFA24B
  NAME: ADT-A24 message                 ID: MPIFA24B
 GENERAL DESCRIPTION:   This call is used by  Single Patient Registration,
 whenever a new patient is created. After setting an ICN into the Patient File,
 we make this call to create and send an ADT-A24 message to the National MPI.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: A24
 COMPONENT DESCRIPTION:   A24^MPIFA24B is used to create and send a ADT-A24 HL7 
 message to National MPI.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN   the patient ien in file #2 
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   FILEICN (a subroutine of JVDGF) is used to add an ICN
 to a patient record.  The following line in FILEICN makes the call: 
  
      IF SUCCESS=1 S A24S=$$A24^MPIFA24B(+NWDFN) ; 
  DATE ACTIVATED: MAR 01, 2011

NUMBER: 5050                            IA #: 5050
  DATE CREATED: NOV 14, 2007
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMVGETC
  NAME: GMVGETC                         ID: GMVGETC
 GENERAL DESCRIPTION:   APIs that return values for categories (FILE 120.53).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: FIELD(IEN,FIELD,FORMAT)
 COMPONENT DESCRIPTION:   Returns the value for the record and field in the
 format specified. Returns -1 if there is an error.  
  
  Example: 
  >W $$FIELD^GMVGETC(1,1,"E") 
  >LOCATION 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The FILE 120.53 internal entry number. (Required) 
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   A set of codes to indicate which field value to
 return. (Required) 
  
  Where: 
   1=Name (.01) 
   2=VUID (99.99) 
   3=Master Entry For VUID (99.98) 
VARIABLES: FORMAT                       TYPE: Input
 VARIABLES DESCRIPTION:   A set of codes to indicate if the internal or
 external value of the field should be returned. (Optional) 
  Where: 
   I=Internal 
   E=External (the default) 
COMPONENT/ENTRY POINT: GETIEN(VALUE,TYPE)
 COMPONENT DESCRIPTION:   Returns the category (FILE 120.53) pointer value.
 Returns null if not found. Returns -1 if there is an error.  
  
  Example: 
   >W $$GETIEN^GMVGETC("METHOD",1)  
   >2 
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   The FILE 120.53 value to lookup. (Required) 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   A set of codes to indicate what kind of value is
 being used for the lookup. (Required) 
  Where: 
   1=Name (.01) 
   2=VUID (99.99) 
COMPONENT/ENTRY POINT: VT(ARRAY,IEN)
 COMPONENT DESCRIPTION:   Returns the vital types associated with the category. 
  
  Output format: 
  ARRAY(0)=piece1 
  ARRAY(n)=piece2^piece3 
   where: 
         n=a sequential number starting with 1 
    piece1=number of entries found or -1 if an error 
    piece2=FILE 120.51 entry number 
    piece3=FILE 120.51, Field .01 external value 
  
  Example: 
  >D VT^GMVGETC(.ARRAY,1) 
  >ZW ARRAY 
  >ARRAY(0)=4 
  >ARRAY(1)="1^BLOOD PRESSURE" 
  >ARRAY(2)="2^TEMPERATURE" 
  >ARRAY(3)="5^PULSE" 
  >ARRAY(4)="20^CIRCUMFERENCE/GIRTH" 
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   The name of the array to return the values in.
 (Required) 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The FILE 120.53 internal entry number. (Required) 
  DATE ACTIVATED: MAR 19, 2008

NUMBER: 5051                            IA #: 5051
  DATE CREATED: NOV 15, 2007            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: YTQPXRM3                     NAME: RL-YTQPXRM3
  ID: YTQPXRM3
 GENERAL DESCRIPTION:   RL(YSCODEN) ;requires license 
          ;input YSCODEN ien OF 601.71 
          ;output  Y/N/0 
  STATUS: Withdrawn
KEYWORDS: LICENSE
COMPONENT/ENTRY POINT: RL(YSCODEN)
 COMPONENT DESCRIPTION:   RL(YSCODEN) ;requires license 
          ;input YSCODEN as IEN of 601.71 
VARIABLES: YSCODEN                      TYPE: Input
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 5052                            IA #: 5052
  DATE CREATED: NOV 15, 2007            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: YTQPXRM3                     NAME: OLDNEW-YTQPXRM3
  ID: YTQPXRM3
 GENERAL DESCRIPTION:   OLDNEW(YSCODEN,YSOLDNUM) ; 
          ;input YSCODEN ien OF 601.71 
          ;      YSOLDNUM as ien of "S" MULT of 601 (1= DEFAULT) 
          ;output ien OF 601.87, 0=ERROR 
  STATUS: Withdrawn
KEYWORDS: SCALES
KEYWORDS: CONVERT
COMPONENT/ENTRY POINT: OLDNEW(YSCODEN,YSOLDNUM)
VARIABLES: YSCODEN                      TYPE: Input
 VARIABLES DESCRIPTION:   
          input YSCODEN ien OF 601.71, TEST Number 
VARIABLES: YSOLDNUM                     TYPE: Input
 VARIABLES DESCRIPTION:   
          YSOLDNUM as ien of "S" MULT of 601 (1= DEFAULT). tHIS IS THE OLD 
 MULTIPLE NUMBER 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 5053                            IA #: 5053
  DATE CREATED: NOV 15, 2007            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: YTQPXRM4
  NAME: SAVECR-YTQPXRM4                 ID: YTQPXRM4
 GENERAL DESCRIPTION:   SAVECR(YSDATA,YS) ;save cr entered instruments 
          ; input: CODE,DFN,^TMP($J,AARAY,sequential)=ITEM#^RESPONSE 
          ;output [DATA] VS [ERROR] 
  STATUS: Active
KEYWORDS: SAVE
KEYWORDS: REMINDERS
COMPONENT/ENTRY POINT: SAVECR(YSDATA,YS)
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   ien of patient file 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Name of mh instrument from 601.71 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: DEC 18, 2007

NUMBER: 5054                            IA #: 5054
  DATE CREATED: NOV 15, 2007            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: YTQPXRM6                     NAME: CONVERT-YTQPXRM6
  ID: YTQPXRM6
 GENERAL DESCRIPTION:   CONVERT(YSDATA,YS) ;convet 601 ien into 601.71 iens 
          ;input YS601 AS 601 IEN 
          ;output 601.71 ien 
  STATUS: Withdrawn
KEYWORDS: MHA2
KEYWORDS: CONVERT
COMPONENT/ENTRY POINT: CONVERT(YSDATA,YS)
VARIABLES: YS601                        TYPE: Input
 VARIABLES DESCRIPTION:   ien of old instrument file 601 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 5055                            IA #: 5055
  DATE CREATED: NOV 20, 2007            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  NAME: INDEX-YTQPXRM
 GENERAL DESCRIPTION:   builds index ^PXRMINDX(601.84,""PI" and
 ^PXRMINDX(601.84,"IP" as described in the clinical reminders documentation.
 DAS is last node.  
  
 No input or output variables, just a complete re-build of the indexes.  
  STATUS: Retired
KEYWORDS: REMINDERS
KEYWORDS: INDEX
COMPONENT/ENTRY POINT: INDEX
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: DEC 18, 2007

NUMBER: 5056                            IA #: 5056
  DATE CREATED: NOV 20, 2007            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: YTQPXRM5
  NAME: YTQPXRM5                        ID: YTQPXRM5
  STATUS: Active
KEYWORDS: SCALES
KEYWORDS: SHOWALL
KEYWORDS: INSTRUMENT
COMPONENT/ENTRY POINT: SCALES
 COMPONENT DESCRIPTION:   SCALES(YSDATA,YSCODEN) ;output all scales for a test 
          ;input :YSCODEN AS 601.71 IEN 
          ;output scalename^601.82 ENTRY 
VARIABLES: YSCODEN                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of file 601.71, to indicate the instrument 
VARIABLES: YSDATA                       TYPE: Output
 VARIABLES DESCRIPTION:   
          output scalename^601.82 ENTRY in an array 
COMPONENT/ENTRY POINT: SHOWALL
 COMPONENT DESCRIPTION:   Returns the text, introductions and repsonses for all
 questions in an instrument.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Name of TEST infile 601.71 
VARIABLES: YSDATA                       TYPE: Output
 VARIABLES DESCRIPTION:   Array of data first node question sequence, second:
 "I" for intro, "T" for text or "R" for responses. Third node is running count. 
 
COMPONENT/ENTRY POINT: ONECR(YSCODEN,YSLIMIT)
 COMPONENT DESCRIPTION:   ONECR(YSCODEN,YSLIMIT) ;FUNCTION check one test for
 CR 
          ;input YSCODEN ien OF 601.71 
          ;      YSLIMIT # OF QUESTIONS (25 DEFAULT) 
          ;output 1: OK for CR 
VARIABLES: YSCODEN                      TYPE: Input
 VARIABLES DESCRIPTION:   
          input YSCODEN ien OF 601.71 
VARIABLES: YSLIMIT                      TYPE: Input
 VARIABLES DESCRIPTION:   
           YSLIMIT # OF QUESTIONS (25 DEFAULT) 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: DEC 18, 2007

NUMBER: 5057                            IA #: 5057
  DATE CREATED: DEC 05, 2007            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSJUTL2
  NAME: BCMA LAST ACTION                ID: PSJUTL2
 GENERAL DESCRIPTION:   As part of the medication reconciliation portion of the
 outpatient pharmacy application, we have need for the BCMA Last Action
 information as returned by the call to BCMALG^PSJUTL2.  To accomplish this,
 outpatient pharmacy requests permission to make this call.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: BCMALG
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: FEB 11, 2008

NUMBER: 5058                            IA #: 5058
  DATE CREATED: DEC 05, 2007            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSJMUTL
  NAME: ALLERGIES ARRAY                 ID: PSJMUTL
 GENERAL DESCRIPTION:   As part of the medication reconcilication portion of
 the outpatient pharmacy application, we need the arrays of allergies and
 adverse reactions returned by a call to ATS^PSJMUTL.  To accomplish this, 
 outpatient pharmacy requests permission to make this call.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ATS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: FEB 11, 2008

NUMBER: 5059                            IA #: 5059
  DATE CREATED: DEC 06, 2007
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIULMED1
  NAME: ADD MEDS AND ADD TITLE          ID: TIULMED1
 GENERAL DESCRIPTION:   As part of the medication reconciliation component of
 the outpatient pharmacy application, we need the information provided by
 ADDMED^TIULMED1 and ADDTITLE^TIULMED1.  To that end, we request permission to
 call those entry points.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ADDMED
COMPONENT/ENTRY POINT: ADDTITLE
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: FEB 11, 2008

NUMBER: 5060                            IA #: 5060
  DATE CREATED: DEC 06, 2007
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIULMED2
  NAME: CALLS TO TIULMED2               ID: TIULMED2
 GENERAL DESCRIPTION:   The medication reconciliation portion of the outpatient
 pharmacy application has need of the information returned by call to entry
 points DEA, DRGCLASS, DRGIEN, and IENNAME in routine TIULMED2.  We request 
 permission to make those calls.  
  STATUS: Active
COMPONENT/ENTRY POINT: DEA
COMPONENT/ENTRY POINT: DRGCLASS
COMPONENT/ENTRY POINT: DRGIEN
COMPONENT/ENTRY POINT: IENNAME
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: FEB 11, 2008

NUMBER: 5061                            IA #: 5061
  DATE CREATED: DEC 06, 2007
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIULMED3
  NAME: CALLS TO TIUMED3                ID: TIULMED3
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PATCHSOK
COMPONENT/ENTRY POINT: GETCLASS
COMPONENT/ENTRY POINT: SORTSAVE
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   The medication reconciliation portion of the outpatient
 pharmacy application has need of the informatio returned by calls to entry
 points PATCHSOK, GETCLASS, and SORTSAVE in routine TIULMED3.  We request 
 permission to make those calls.  
  DATE ACTIVATED: FEB 11, 2008

NUMBER: 5062                            IA #: 5062
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123
  DATE CREATED: DEC 12, 2007
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA5062
  ID: GMR(123
GLOBAL REFERENCE: GMR(123,'ACP'
 GLOBAL DESCRIPTION:   The 'ACP' index is by CLINICAL PROCEDURE and PATIENT.  
GLOBAL REFERENCE: GMR(123,'AE'
FIELD NUMBER: 1                         FIELD NAME: TO SERVICE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This integration agreement documents the usage of the
 ACP and AE index in the REQUEST/CONSULTATION file (#123).  CLINICAL PROCEDURES
 package will be $ORDER through the ^GMR(123,"ACP" by the CP Definition to get
 a list of consult requests by CP definition.  
  
 CLINICAL PROCEDURES package will $ORDER through the ^GMR(123,"AE" by the TO
 SERVICE to get a list of consult requests for a service.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMR(123
KEYWORDS: MD*1*65
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  DATE ACTIVATED: MAR 19, 2008

NUMBER: 5063                            IA #: 5063
  DATE CREATED: DEC 14, 2007            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOREJU4
  NAME: PSOREJU4                        ID: PSOREJU4
 GENERAL DESCRIPTION:   This routine contains APIs to be used by ECME package
 to pass Third Party Reject information to the Pharmacy Reject Worklist.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: WRKLST
KEYWORDS: PSOREJU4
COMPONENT/ENTRY POINT: $$WRKLST(RX,RFL,COMMTXT,USERID,DTTIME,OPECC,RXCOB)
 COMPONENT DESCRIPTION:   External API to store reject codes other that
 79/88/Tricare on the OP Reject Worklist.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN.  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Fill number being processed.  
VARIABLES: COMMTXT                      TYPE: Input
 VARIABLES DESCRIPTION:   Array with the comments where: 
  
       Name:  COMMTXT 
       Description:  The number of comments lines 
  
       Name:  COMMTXT(1) 
       Description:   Comment line 1.  
  
       Name:   COMMTXT(2) 
       Description:  Comment line 2.  
VARIABLES: USERID                       TYPE: Input
 VARIABLES DESCRIPTION:   User's IEN.  
VARIABLES: DTTIME                       TYPE: Input
 VARIABLES DESCRIPTION:   Date/time the OPECC sent the fill to the Pharmacy
 Reject Worklist.  
VARIABLES: OPECC                        TYPE: Input
 VARIABLES DESCRIPTION:   A value of 1 for OPECC flagged for Pharmacy to
 resolve or 0 (zero) not OPECC flagged.  
VARIABLES: STATUS                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns: 1 - success 2 - already in the Pharmacy work
 list 0^error text - error flag with the error text message for the User Screen 
 user.  
      Example 0 returned values: 
              0^1-fill not on file.  
VARIABLES: RXCOB                        TYPE: Input
 VARIABLES DESCRIPTION:   Coordination of benefits indicator may contain a
 value of 1 (one) for primary, 2 (two) for secondary, or 3 (three) for
 tertiary.  
COMPONENT/ENTRY POINT: $$INLIST(RXIEN,FILL,RXCOB)
 COMPONENT DESCRIPTION:   This API returns whether the prescription fill has
 unresolved third party rejects.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN 
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Prescription fill number 
VARIABLES: REJ                          TYPE: Output
 VARIABLES DESCRIPTION:   Contains either 1 (one) meaning the prescription has
 third party rejects or 0 (zero) meaning the prescription does not have
 unresolved third party rejects.  
VARIABLES: RXCOB                        TYPE: Input
 VARIABLES DESCRIPTION:   Coordination of benefits indicator may contain a
 value of 1 (one) for primary, 2 (two) for secondary, or 3 (three) for
 tertiary.  
COMPONENT/ENTRY POINT: AUTOREJ(CODES,PSODIV)
 COMPONENT DESCRIPTION:   API to evaluate an array of reject codes to see if
 they are allowed to be passed to OP reject Worklist.  
VARIABLES: CODES                        TYPE: Both
 VARIABLES DESCRIPTION:   Array of reject codes to be evaluated to see if there
 are overrides defined for them in EPHARMACY SITE PARAMETERS file (#52.86). 
 Reject codes defined in this file are allowed to be passed onto the OP Third 
 Party Reject Worklist. These reject codes are other than 79/88/Tricare third
 party reject codes which automatically are stored on the OP Third Party Reject
 Worklist.  
  
  
 The following values are returned: 
  
 CODES(SEQ,REJECT)= Array of reject codes.  Individual reject codes may be 
 defined in EPHARMACY SITE PARAMETERS file (#52.86) as override codes meaning
 they can pass to the OP Third Party Reject Worklist automatically.  A retuned
 value of 1 (one) for a reject code means the code may be automatically passed
 to the OP Third Party Reject Worklist.  A value of 0 (zero) means the code may
 not be sent.  
  
VARIABLES: DIV                          TYPE: Input
 VARIABLES DESCRIPTION:   Division for the prescription fill, and this
 parameter is optional.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: JUL 23, 2013

NUMBER: 5064                            IA #: 5064
  FILE NUMBER: 9002313.25               GLOBAL ROOT: BPS(9002313.25
  DATE CREATED: DEC 14, 2007            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: 9002313.25
  ID: BPS(9002313.25                    STATUS: Active
KEYWORDS: CLARIFICATION CODE
KEYWORDS: ECME
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   THE SUBSCRIBING PACKAGE IS ALLOWED READ ACCESS.  
  DATE ACTIVATED: DEC 14, 2007

NUMBER: 5065                            IA #: 5065
  DATE CREATED: DEC 27, 2007            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  NAME: IA 5065
 GENERAL DESCRIPTION:   API to allow ECME to call the INLIST API to check for
 allowable reject codes that are allowed to be passed to the Pharmacy Reject
 Worklist manually by the OPECC.  
  STATUS: Pending
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 5066                            IA #: 5066
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870
  DATE CREATED: JAN 08, 2008            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  NAME: LOOKUP IP ADDRESS FOR PACKAGE IN 870
  ID: HLCS(870
 GENERAL DESCRIPTION:   The Enrollment Application System package (EAS) would
 like to lookup an entry in file #870 using a direct read on the "B cross
 reference and read data from the entry using Fileman.  Here is the code being
 used (in routine EAS1071A): 
  
 IPLIVE() ;Get IP address for production system 
          ;
          ;Search for DENTVHLAAC logical link 
          S IENS=$$FIND1^DIC(870,"","X","DENTVHLAAC","","","ERR") 
          ;If not found return null IP address 
          I 'IENS Q "" 
          ;Otherwise return TCP/IP ADDRESS 
          Q $$GET1^DIQ(870,IENS_",",400.01) 
  
 LL16(LLNAME,TCPADDR,TCPPORT,SHUTDOWN) ;Update Logical Link Port and Address 
          ;
          N FILE,DATA,RETURN,DEFINED,ERROR,DA,DGENDA 
          S FILE=870 
          S IEN870=$O(^HLCS(870,"B",LLNAME,0)) 
          I 'IEN870 D  Q RETURN 
          . S ERROR="IEN OF RECORD TO BE UPDATED NOT FOUND" 
          . S RETURN=-1_"^"_ERROR 
          ;
          S DATA(400.01)=TCPADDR                    ;TCP/IP ADDRESS 
          S DATA(400.02)=TCPPORT                    ;TCP/IP PORT 
          S DATA(4.5)=1                             ;AUTOSTART 
          S DATA(14)=SHUTDOWN                       ;SHUTDOWN LLP 
          ;
          S RETURN=$$UPD^DGENDBS(FILE,IEN870,.DATA,.ERROR) 
          S:ERROR'=""!(+RETURN=0) RETURN=-1_"^"_ERROR 
          ;
          Q RETURN 
  
 This is in support of the ESR v3.0 rollout in patch EAS*1*71.  
  
  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: IP ADDRESS
KEYWORDS: 870
KEYWORDS: EAS
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM

NUMBER: 5067                            IA #: 5067
  GLOBAL ROOT: DD(                      DATE CREATED: JAN 10, 2008
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DD CHECKING AND TRAVERSING      ID: DD(
GLOBAL REFERENCE: DD(D0,0,'PT',D1,99.97,
GLOBAL REFERENCE: DD(D0,0,'PT',D1,
 GENERAL DESCRIPTION:   In support of APIs for Data Standardization, Kernel
 ToolKit is authorized to check a file's DD as follows: 
  
 I ('$D(^DD(FILE,0,"PT",NEXTFILE,99.97))) Q 
  
 and $O through a file's DD as follows: 
  
 S NEXTFILE=+$O(^DD(FILE,0,"PT",NEXTFILE)) 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TOOLKIT
  DATE ACTIVATED: FEB 06, 2008

NUMBER: 5068                            IA #: 5068
  DATE CREATED: JAN 16, 2008
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: RAMAG EXAM ORDER
 GENERAL DESCRIPTION:   The RAMAG EXAM ORDER remote procedure requests a
 Radiology exam for the patient and returns the IEN of the new order in the
 RAD/NUC MED ORDERS file (#75.1). It also sends all required notifications.  
  
 Input Parameters 
 ================
  
   RADFN         Patient IEN (DFN).  
  
   RAMLC         IEN of the imaging location in the IMAGING LOCATIONS 
                 file (#79.1).  
  
   RAPROC        Radiology procedure and optional modifiers 
                   ^01: Procedure IEN in the RAD/NUC MED PROCEDURES 
                        file (#71) 
                   ^02: Optional procedure modifiers (IENs in 
                   ...  the PROCEDURE MODIFIERS file (#71.2)) 
                   ^nn: 
  
   REQDTE        Desired date for the exam in HL7 format (TS): YYYYMMDD.  
                 If a time part is provided, it is ignored. The date 
                 must be exact.  
  
   RACAT         Exam category: internal value of the CATEGORY OF EXAM 
                 field (4) of the RAD/NUC MED ORDERS file (#75.1).  
  
   REQLOC        IEN of the requesting location in the HOSPITAL 
                 LOCATION file (#44).  
  
   REQPHYS       IEN of the requesting physician in the NEW PERSON 
                 file (#200).  
  
   REASON        Reason for study. See the REASON FOR STUDY field (1.1) 
                 of the RAD/NUC MED ORDERS file (#75.1) for details.  
  
   [RAMSC]       Items of this list define miscellaneous/optional 
                 order parameters. Each record has 3 or more pieces 
                 separated by '^': 
  
                   ^01: Parameter name 
                   ^02: Index (for multiples and word-processing values) 
                   ^03: Value1 
                   ^04: Value2 
                   ...
  
                 The following parameters are supported by this remote 
                 procedure: 
   
                   CLINHIST^{Seq#}^{Line of clinical history} 
                     Text for the CLINICAL HISTORY FOR EXAM field (400) 
                     of the file #75.1 
  
                   ISOLPROC^^{n|y} 
                     Value for the ISOLATION PROCEDURES field (24) 
                     of the file #75.1 
  
                   PREGNANT^^{n|u|y} 
                     Value for the PREGNANT field (13) of the file #75.1 
  
                   PREOPDT^^{Internal date value} 
                     Date and time for the PRE-OP SCHEDULED DATE/TIME 
                     field (12) of the file #75.1 in HL7 format (TS): 
                     YYYYMMDD[HHMM[+/-ZZZZ]]. If seconds are provided, 
                     they are ignored. The date must be exact.  
  
                   REQNATURE^^{e|i|p|s|v|w} 
                     Value for the NATURE OF (NEW) ORDER ACTIVITY 
                     field (26) of the file #75.1 
  
                   REQURG^^{1|2|9} 
                     Value for the REQUEST URGENCY field (6) 
                     of the file #75.1 
  
                   TRANSPMODE^^{a|p|s|w} 
                     Value for the MODE OF TRANSPORT field (19) 
                     of the file #75.1 
  
                 Records can be added to the list in any order.  
  
     Example: 
  
       with RPCBroker.Param[8] do 
         begin 
           PType := list; 
           Mult[1] := 'PREGNANT^^y'; 
           Mult[2] := 'PREOPDT^^200001041400'; 
           Mult[3] := 'CLINHIST^1^Clinical history line #1'; 
           Mult[4] := 'CLINHIST^2^Clinical history line #2'; 
           Mult[5] := 'CLINHIST^3^Clinical history line #3'; 
         end; 
  
 Results 
 =======
  
 A negative value of the first '^'-piece of the Results[0] indicates that an
 error occurred during the execution of the remote procedure. In this case, the
 second piece of the Results[0] will contain number of the error descriptors
 returned in the subsequent nodes of the Results array.  
  
   Results[0]    Result descriptor 
                   ^01: The last error code 
                   ^02: Number of error descriptors 
   
   Results[i]    Error descriptor 
                   ^01: Error code 
                   ^02: Message 
                   ^03: Error location (TAG~ROUTINE) 
                   ^04: Error type 
   
   Results[j]    Line of the additional info 
                   ^01: "" (empty) 
                   ^02: Text 
  
 Error descriptors are returned in reverse chronological order (most recent 
 first).  
  
 Otherwise, the Results[0] contains IEN of the new order in the RAD/NUC MED 
 ORDERS file (#75.1).  
  
 Notes 
 =====
  
 See comments in the source code of the RAMAG02 routine and description of the
 RAMAG EXAM ORDER remote procedure for additional and/or most recent details.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING
  DATE ACTIVATED: OCT 06, 2008

NUMBER: 5069                            IA #: 5069
  DATE CREATED: JAN 16, 2008
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: RAMAG EXAM REGISTER
 GENERAL DESCRIPTION:   The RAMAG EXAM REGISTER remote procedure registers the
 Radiology exam and returns identifiers of the new case(s) in the RAD/NUC MED
 PATIENT file (#70). It also sends all required notifications.  
  
 Input Parameters 
 ================
  
   RAOIFN        IEN of the order in the RAD/NUC MED ORDERS file (#75.1).  
  
   EXMDTE        Date and time of the exam in HL7 format (TS): 
                 YYYYMMDDHHMM[+/-ZZZZ]. If seconds are provided, 
                 they are ignored. The date must be exact and the 
                 time is required.  
  
   [RAMSC]       Items of this list define miscellaneous/optional 
                 order parameters. Each record has 3 or more pieces 
                 separated by '^': 
     
                   ^01: Parameter name 
                   ^02: Index (for multiples and word-processing) 
                   ^03: Value1 
                   ^04: Value2 
                   ...
     
                 The following parameters are supported by this remote 
                 procedure: 
  
                   BEDSECT^^{IEN #42.4} 
                     Internal value for the BEDSECTION field (19) of 
                     the EXAMINATIONS multiple (sub-file #70.03).  
  
                   EXAMCAT^^{C|E|I|O|R|S} 
                     Value for the CATEGORY OF EXAM field (4) of the 
                     EXAMINATIONS multiple (sub-file #70.03).  
  
                   FLAGS^^{flags} 
                     Flags that control the execution (can be combined): 
  
                     A  If this flag is provided, then the registration 
                        entry point adds the new case to the existing 
                        ones with the same date/time instead of 
                        returning the error code -28.  
  
                        If the existing date/time record stores an exam 
                        set and the "D" flag is not provided, then the 
                        error code -54 is returned.  
  
                     D  If there is an existing case with the same 
                        date/time, then the time of the new case is 
                        incremented by 1 minute until an unused date/time 
                        is found.  
  
                        If the "A" flag is also provided, then time 
                        increments also stop when a non-examset 
                        date/time record is found.  
  
                        If the date is also changed during the time 
                        modification, then the case is not registered and 
                        the error code -29 is returned.  
  
                   PRINCLIN^^{IEN #44} 
                     Internal value for the PRINCIPAL CLINIC field (8) of 
                     the EXAMINATIONS multiple (sub-file #70.03).  
  
                   RAPROC^{Seq#}^{IEN #71}^{IEN #71.2}^{IEN #71.2}^...  
                     Radiology procedure and optional modifiers.  
  
                   SERVICE^^{IEN #49} 
                     Internal value for the SERVICE field (7) of 
                     the EXAMINATIONS multiple (sub-file #70.03).  
  
                   SINGLERPT^^{0|1} 
                     If this parameter is defined and not 0, then all 
                     cases should be associated with the same order 
                     and they will share the same report. See the 
                     MEMBER OF SET (25) and IMAGING ORDER (11) fields 
                     of the sub-file #70.03 for more details.  
  
                   TECHCOMM^^{text} 
                     Value for the TECHNOLOGIST COMMENT field (4) of 
                     the ACTIVITY LOG multiple (sub-file #70.07). 
  
                   WARD^^{IEN #42} 
                     Internal value for the WARD field (6) of 
                     the EXAMINATIONS multiple (sub-file #70.03).  
  
                 Records can be added to the list in any order.  
  
     Example: 
  
       with RPCBroker.Param[2] do 
         begin 
           PType := list; 
           Mult[1] := 'BEDSECT^^12'; 
           Mult[2] := 'SERVICE^^43'; 
           Mult[3] := 'WARD^^456'; 
           Mult[4] := 'EXAMCAT^^I'; 
         end; 
  
 Results 
 =======
  
 A negative value of the first '^'-piece of the Results[0] indicates that an
 error occurred during the execution of the remote procedure. In this case, the
 second piece of the Results[0] will contain number of the error descriptors
 returned in the subsequent nodes of the Results array.  
  
   Results[0]            Result descriptor 
                           ^01: The last error code 
                           ^02: Number of error descriptors 
   
   Results[i]            Error descriptor 
                           ^01: Error code 
                           ^02: Message 
                           ^03: Error location 
                           ^04: Error type 
   
   Results[j]            Line of the additional info 
                           ^01: "" (empty) 
                           ^02: Text 
  
 Error descriptors are returned in reverse chronological order (most recent 
 first).  
  
 Otherwise, number of registered examinations is returned in the Results[0] and
 identifiers of the examinations are returned in the subsequent elements of the
 array. 
  
   Results[0]            Number of registered examinations 
  
   Results[i]            Exam/case identifiers 
                           ^01: IEN of the patient in the file #70 
                           ^02: IEN in the REGISTERED EXAMS multiple 
                           ^03: IEN in the EXAMINATIONS multiple 
                           ^04: Case number 
                           ^05: Accession number 
                                 SSS-MMDDYY-NNNNN  if RA*5*47 is installed; 
                                     MMDDYY-NNNNN  otherwise.  
                           ^06: Actual date and time of the case in 
                                HL7 format (TS): YYYYMMDD[HHMM[+/-ZZZZ]] 
  
 Notes 
 =====
  
 See comments in the source code of the RAMAG03 routine and description of the
 RAMAG EXAM REGISTER remote procedure for additional and/or most recent 
 details.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING
  DATE ACTIVATED: OCT 06, 2008

NUMBER: 5070                            IA #: 5070
  DATE CREATED: JAN 16, 2008            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSNPI
  NAME: Utility to return AUTHORIZE RELEASE OF NPI field
  ID: XUSNPI
 GENERAL DESCRIPTION:   An API that returns the value of the field AUTHORIZE
 RELEASE OF NPI (#41.97) from an entry in the NEW PERSON file (#200).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NPI
KEYWORDS: RELEASE NPI
KEYWORDS: BLANKET RELEASE NPI
COMPONENT/ENTRY POINT: GETRLNPI(XUSIEN)
 COMPONENT DESCRIPTION:   Returns the value of the field AUTHORIZE RELEASE OF
 NPI (#41.97) from entry with IEN equal to the input parameter XUSIEN, from the
 NEW PERSON file (#200).  
VARIABLES: XUSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of an entry in the NEW PERSON file (#200).  
VARIABLES: $$GETRLNPI                   TYPE: Output
 VARIABLES DESCRIPTION:   Returns null (if field is set to null), 0 (No), 1
 (Yes) or -1^ErrorMessage 
VARIABLES:  
SUBSCRIBING PACKAGE: FEE BASIS
  DATE ACTIVATED: JAN 29, 2008

NUMBER: 5071                            IA #: 5071
  DATE CREATED: JAN 16, 2008
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: RAMAG EXAMINED
 GENERAL DESCRIPTION:   The RAMAG EXAMINED remote procedure upodates the status
 of the case (the procedure has been performed) and creates the stub report. It
 also sends required HL7 messages, sends changed order control "XX" to CPRS,
 but does not send VistA alerts regarding the exam status change.  
  
 Input Parameters 
 ================
  
   RAEXAM        String of exam/case identifiers separated by '^' 
                   ^01: IEN of the patient in the RAD/NUC MED 
                        PATIENT file (#70) 
                   ^02: IEN in the REGISTERED EXAMS multiple 
                        (sub-file #70.02) 
                   ^03: IEN in the EXAMINATIONS multiple 
                        (sub-file #70.03) 
  
   [RAMSC]       Items of this list define miscellaneous/optional 
                 order parameters. Each record has 3 or more pieces 
                 separated by '^': 
        
                   ^01: Parameter name 
                   ^02: Index (for multiples and word-processing) 
                   ^03: Value1 
                   ^04: Value2 
                   ...
        
                 The following parameters are supported by this remote 
                 procedure: 
  
                   CMUSED^^{Y|N} 
                     Internal value for the CONTRAST MEDIA USED 
                     field (10) of the sub-file #70.03.  
  
                   COMPLICAT^^{IEN #78.1}^{text} 
                     Internal values for the COMPLICATION (16) 
                     and COMPLICATION TEXT (16.5) fields of the 
                     sub-file #70.03.  
  
                   CONTMEDIA^{Seq#}^{I|N|L|C|G|B|M} 
                     Internal value for the CONTRAST MEDIA field (.01) 
                     of the sub-file #70.3225.  
  
                   CPTMODS^{Seq#}^{IEN #81.3} 
                     Internal value for the CPT MODIFIERS field (.01) 
                     of the sub-file #70.3135: IEN in the CPT MODIFIER 
                     file (#81.3).  
  
                   FILMSIZE^{Seq#}^{IEN #78.4}^{amount} 
                     Internal values for the record of the FILM SIZE 
                     multiple (70) of the sub-file #70.03.  
  
                   FLAGS^^{flags} 
                     Flags that control the execution (can be combined): 
  
                     F  Try to enforce the new status even if some 
                        required fields are not populated.  
  
                     S  Do not send HL7 message to speech recognition 
                        (dictation) systems 
  
                   PRIMCAM^^{IEN #78.6} 
                     Internal value for the PRIMARY CAMERA/EQUIP/RM 
                     field (18) of the sub-file #70.03: IEN in the 
                     CAMERA/EQUIP/RM file (#78.6).  
  
                   PRIMDXCODE^^{IEN #78.3} 
                     Internal value for the PRIMARY DIAGNOSTIC 
                     CODE field (13) of the sub-file #70.03: 
                     IEN in the DIAGNOSTIC CODES file (#78.3).  
  
                   PRIMINTRES^^{IEN #200} 
                     Internal value for the PRIMARY INTERPRETING 
                     RESIDENT field (12) of the sub-file #70.03: 
                     IEN in the NEW PERSON file (#200).  
  
                   PRIMINTSTF^^{IEN #200} 
                     Internal value for the PRIMARY INTERPRETING 
                     STAFF field (15) of the sub-file #70.03: 
                     IEN in the NEW PERSON file (#200).  
  
                   RAPROC^1^{IEN #71}^{IEN #71.2}^{IEN #71.2}^...  
                     Radiology procedure and optional modifiers.  
  
                   RDPHARMS^{Seq#} 
                     Opening/closing tag of the record of internal 
                     values for the 'RADIOPHARMACEUTICALS' multiple 
                     (100) of the 'NUC MED EXAM DATA' file (#70.2).  
  
                     RDPH-ACDR^^{value} 
                       Internal value for the ACTIVITY DRAWN 
                       field (4).  
  
                     RDPH-DOSE^^{value} 
                       Internal value for the DOSE ADMINISTERED 
                       field (7).  
  
                     RDPH-DRUG^^{IEN #50} 
                       Internal value for the RADIOPHARMACEUTICAL 
                       field (.01).  
  
                     RDPH-DTADM^^{date/time} 
                       Internal value for the DATE/TIME DOSE 
                       ADMINISTERED field (8).  
  
                     RDPH-DTDRW^^{date/time} 
                       Internal value for the DATE/TIME DRAWN 
                       field (5).  
  
                     RDPH-FORM^^{A|G|L|P|S} 
                       Internal value for the FORM field (15).  
  
                     RDPH-LOTN^^{IEN #71.9} 
                       Internal value for the LOT NO field (13).  
  
                     RDPH-PWADM^^{IEN #200} 
                       Internal value for the PERSON WHO ADMINISTERED 
                       DOSE field (9).  
  
                     RDPH-PWMSD^^{IEN #200} 
                       Internal value for the PERSON WHO MEASURED DOSE 
                       field (6).  
  
                     RDPH-ROUTE^^{IEN #71.6} 
                       Internal value for the ROUTE OF ADMINISTRATION 
                       field (11).  
  
                     RDPH-SITE^^{IEN #71.7} 
                       Internal value for the SITE OF ADMINISTRATION 
                       field (12).  
  
                     RDPH-VOL^^{value} 
                       Internal value for the VOLUME field (14).  
  
                   TECH^{Seq#}^{IEN #200} 
                     Internal value for the TECHNOLOGIST field (.01) 
                     of the subfile #70.12: IEN in the NEW PERSON 
                     file (#200).  
  
                   TECHCOMM^^{text} 
                     Value for the TECHNOLOGIST COMMENT field (4) of the 
                     ACTIVITY LOG multiple (sub-file #70.07). 
  
                 The following optional parameters are also supported: 
                 BEDSECT, EXAMCAT, PRINCLIN, SERVICE, and WARD. If any 
                 of them are defined, their values replace the existing 
                 ones assigned by the RAMAG EXAM REGISTER remote 
                 procedure.  
  
                 Records can be added to the list in any order.  
  
                 If you want to clear a multiple that already has a 
                 value, assign "@" or empty string to the parameter 
                 itself and do not set any subscripts. For example, 
                 the following construction will clear the CONTRAST 
                 MEDIA multiple: Mult[i] := 'CONTMEDIA^^@'.  
  
     Example: 
  
       with RPCBroker.Param[1] do 
         begin 
           PType := list; 
           Mult[1] := 'CMUSED^^N'; 
           Mult[2] := 'FILMSIZE^1^7^2'; 
           Mult[3] := 'FILMSIZE^2^3^1'; 
           Mult[4] := 'PRIMCAM^^3'; 
           Mult[5] := 'TECH^1^2344'; 
           Mult[6] := 'FLAGS^^F'; 
  
           Mult[7]  := 'RDPHARMS^1'; 
           Mult[8]  := 'RDPH-DRUG^^23'; 
           Mult[9]  := 'RDPH-DOSE^^.002'; 
           Mult[10] := 'RDPH-FORM^^A'; 
  
           Mult[11] := 'RDPHARMS^2'; 
           Mult[12] := 'RDPH-DRUG^^23'; 
           Mult[13] := 'RDPH-DOSE^^.002'; 
           Mult[14] := 'RDPHARMS^2';    // Record closing tag is required 
                                        // if something else than another 
                                        // record of the same kind follows.  
           Mult[15] := 'COMPLICAT^^13'; 
         end; 
  
 Results 
 =======
  
 A negative value of the first '^'-piece of the Results[0] indicates that an
 error occurred during the execution of the remote procedure. In this case, the
 second piece of the Results[0] will contain number of the error descriptors
 returned in the subsequent nodes of the Results array.  
  
   Results[0]            Result descriptor 
                           ^01: The last error code 
                           ^02: Number of error descriptors 
   
   Results[i]            Error descriptor 
                           ^01: Error code 
                           ^02: Message 
                           ^03: Error location 
                           ^04: Error type 
   
   Results[j]            Line of the additional info 
                           ^01: "" (empty) 
                           ^02: Text 
  
 Error descriptors are returned in reverse chronological order (most recent 
 first).  
  
 Otherwise, 0 is returned in the Results[0].  
  
 Notes 
 =====
  
 See comments in the source code of the RAMAG07 routine and description of the
 RAMAG EXAMINED remote procedure for additional and/or most recent details.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING
  DATE ACTIVATED: OCT 06, 2008

NUMBER: 5072                            IA #: 5072
  DATE CREATED: JAN 16, 2008
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: RAMAG EXAM COMPLETE
 GENERAL DESCRIPTION:   The RAMAG EXAM COMPLETE remote procedure completes the
 exam. It also sends required HL7 messages, sends changed order control "XX" to
 CPRS, but does not send VistA alerts regarding the exam status change.  
  
 Input Parameters 
 ================
  
   RAEXAM        String of exam/case identifiers separated by '^' 
                   ^01: IEN of the patient in the RAD/NUC MED 
                        PATIENT file (#70) 
                   ^02: IEN in the REGISTERED EXAMS multiple 
                        (sub-file #70.02) 
                   ^03: IEN in the EXAMINATIONS multiple 
                        (sub-file #70.03) 
  
   [RAMSC]       Items of this list define miscellaneous/optional 
                 order parameters. Each record has 3 or more pieces 
                 separated by '^': 
  
                   ^01: Parameter name 
                   ^02: Index (for multiples and word-processing) 
                   ^03: Value1 
                   ^04: Value2 
                   ...
  
                 The following parameters are supported by this remote 
                 procedure: 
  
                   ACLHIST^{Seq#}^{Line of clinical history} 
                     Text for the ADDITIONAL CLINICAL HISTORY field 
                     (400) of the RAD/NUC MED REPORTS file (#74).  
  
                   FLAGS^^{flags} 
                     Flags that control the execution (can be combined): 
  
                     F  Try to enforce the new status even if some 
                        required fields are not populated.  
  
                     S  Do not send HL7 message to speech recognition 
                        (dictation) systems 
  
                   IMPRESSION^{Seq#}^{Line of impression text} 
                     Text for the IMPRESSION TEXT field (300) 
                     of the file #74.  
  
                   PROBSTAT^^{text} 
                     Value for the PROBLEM STATEMENT field (25) 
                     of the file #74.  
  
                   REPORT^{Seq#}^{Line of report text} 
                     Text for the REPORT TEXT field (200) 
                     of the file #74.  
  
                   RPTDTE^^{date} 
                     Date in HL7 format (TS) for the REPORTED DATE 
                     field (8) of the file #74: YYYYMMDD. The date 
                     must be exact. If a time part is provided, it 
                     is ignored.  
  
                   RPTSTATUS^^{status} 
                     Internal value for the REPORT STATUS field (5) 
                     of the file #74.  
  
                   TRANSCRST^^{IEN #200} 
                     Internal value for the TRANSCRIPTIONIST 
                     field (11) of the file #74: IEN in the NEW 
                     PERSON file (#200).  
  
                   VERDTE^^{date} 
                     Date/time in HL7 format (TS) for the 
                     VERIFIED DATE field (7) of the file #74: 
                     YYYYMMDD[HHMM[+/-ZZZZ]]. The date must be 
                     exact.  
  
                   VERPHYS^^{IEN #200} 
                     Internal value for the VERIFYING PHYSICIAN 
                     field (9) of the file #74: IEN in the NEW 
                     PERSON file (#200).  
  
                 The following optional parameters are also supported: 
                 BEDSECT, CMUSED, COMPLICAT, CONTMEDIA, CPTMODS, EXAMCAT, 
                 FILMSIZE, PRIMCAM, PRIMDXCODE, PRIMINTRES, PRIMINTSTF, 
                 PRINCLIN, RDPHARMS, RDPH-*, SERVICE, TECH, TECHCOMM, and 
                 WARD. If any of them are defined, their values replace the 
                 existing ones assigned by the RAMAG EXAM REGISTER and 
                 RAMAG EXAMINED remote procedures.  
  
                 Records can be added to the list in any order.  
  
                 If you want to clear a multiple that already has a 
                 value, assign "@" or empty string to the parameter 
                 itself and do not set any subscripts. For example, 
                 the following construction will clear the CONTRAST 
                 MEDIA multiple: Mult[i] := 'CONTMEDIA^^@'.  
  
     Example: 
  
       with RPCBroker.Param[4] do 
         begin 
           PType := list; 
           Mult[1] := 'PRIMDXCODE^^1'; 
           Mult[2] := 'CONTMEDIA^^N'; 
           Mult[3] := 'REPORT^1^Report line #1'; 
           Mult[4] := 'REPORT^2^Report line #2'; 
           Mult[5] := 'IMPRESSION^1^Impression line #1'; 
           Mult[6] := 'FLAGS^^FS'; 
           Mult[7] := 'RPTDTE^^20071215'; 
         end; 
  
 Results 
 =======
  
 A negative value of the first '^'-piece of the Results[0] indicates that an
 error occurred during the execution of the remote procedure. In this case, the
 second piece of the Results[0] will contain number of the error descriptors
 returned in the subsequent nodes of the Results array.  
  
   Results[0]            Result descriptor 
                           ^01: The last error code 
                           ^02: Number of error descriptors 
   
   Results[i]            Error descriptor 
                           ^01: Error code 
                           ^02: Message 
                           ^03: Error location 
                           ^04: Error type 
   
   Results[j]            Line of the additional info 
                           ^01: "" (empty) 
                           ^02: Text 
  
 Error descriptors are returned in reverse chronological order (most recent 
 first).  
  
 Otherwise, 0 is returned in the Results[0].  
  
 Notes 
 =====
  
 See comments in the source code of the RAMAG06 routine and description of the
 RAMAG EXAM COMPLETE remote procedure for additional and/or most recent 
 details.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING
  DATE ACTIVATED: OCT 06, 2008

NUMBER: 5073                            IA #: 5073
  DATE CREATED: JAN 16, 2008
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: RAMAG EXAM STATUS REQUIREMENTS
 GENERAL DESCRIPTION:   The RAMAG EXAM STATUS REQUIREMENTS remote procedure
 returns a descriptor that indicates conditions that should be met in order to
 successfully perform an action on a Radiology exam/case record.  
  
 These conditions are defined by the sites and stored in the EXAMINATION STATUS
 file (#72). See the .1 and .5 nodes of the data dictionary of the file #74 for
 more details.  
  
 Input Parameters 
 ================
  
   RACTION       The RACTION parameter defines the action that is going 
                 to be performed on an exam/case record: 
  
                   E  Examined (procedure has been performed, 
                      images have been acquired) 
  
                   C  Complete 
  
   RAIMGTYI      IEN of the imaging type in the IMAGING TYPE file (#79.2).  
  
   RAPROC        Radiology procedure IEN (file #71). This parameter is 
                 required to determine exact nuclear medicine requirements 
                 (pieces of the Results[0] from 17 to 25).  
  
                 By default (+$G(RAPROC)=0), this remote procedure cannot 
                 examine the SUPPRESS RADIOPHARM PROMPT field (2) of the 
                 RAD/NUC MED PROCEDURES file (#71) and might indicate that 
                 some nuclear medicine data is required even if it is not.  
  
 Results 
 =======
  
 A negative value of the first '^'-piece of the Results[0] indicates that an
 error occurred during the execution of the remote procedure. In this case, the
 second piece of the Results[0] will contain number of the error descriptors
 returned in the subsequent nodes of the Results array.  
  
   Results[0]            Result descriptor 
                           ^01: The last error code 
                           ^02: Number of error descriptors 
   
   Results[i]            Error descriptor 
                           ^01: Error code 
                           ^02: Message 
                           ^03: Error location 
                           ^04: Error type 
   
   Results[j]            Line of the additional info 
                           ^01: "" (empty) 
                           ^02: Text 
  
 Error descriptors are returned in reverse chronological order (most recent 
 first).  
  
 Otherwise, exam status requirements are returned in the Results[0].  
 Descriptor of the exam status is returned in the Results[1].  
  
   Results[0]            Exam status requirements 
                           ^01: TECHNOLOGIST REQUIRED?         {0|1} 
                           ^02: RESIDENT OR STAFF REQUIRED?    {0|1} 
                           ^03: DETAILED PROCEDURE REQUIRED?   {0|1} 
                           ^04: FILM ENTRY REQUIRED?           {0|1} 
                           ^05: DIAGNOSTIC CODE REQUIRED?      {0|1} 
                           ^06: CAMERA/EQUIP/RM REQUIRED?      {0|1} 
                           ^07: reserved 
                           ^08: reserved 
                           ^09: reserved 
                           ^10: reserved 
                           ^11: REPORT ENTERED REQUIRED?       {0|1} 
                           ^12: VERIFIED REPORT REQUIRED?      {0|1} 
                           ^13: PROCEDURE MODIFIERS REQUIRED?  {0|1} 
                           ^14: CPT MODIFIERS REQUIRED?        {0|1} 
                           ^15: reserved 
                           ^16: IMPRESSION REQUIRED?           {0|1} 
                           ^17: RADIOPHARMS/DOSAGES REQUIRED?  {0|1} 
                           ^18: reserved 
                           ^19: ACTIVITY DRAWN REQUIRED?       {0|1} 
                           ^20: DRAWN DT/TIME/PERSON REQUIRED? {0|1} 
                           ^21: ADM DT/TIME/PERSON REQUIRED?   {0|1} 
                           ^22: reserved 
                           ^23: ROUTE/SITE REQUIRED?           {0|1} 
                           ^24: LOT NO. REQUIRED?              {0|1} 
                           ^25: VOLUME/FORM REQUIRED?          {0|1} 
  
   Results[1]            Status descriptor 
                           ^01: Status IEN 
                           ^02: Status name 
                           ^03: Status code (order) 
                           ^04: VistARAD category 
                           ^05: Generic exam status characteristics 
  
 Notes 
 =====
  
 See comments in the source code of the RAMAGU06 routine and description of the
 RAMAG EXAM STATUS REQUIREMENTS remote procedure for additional and/or most
 recent details.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING
  DATE ACTIVATED: OCT 06, 2008

NUMBER: 5074                            IA #: 5074
  DATE CREATED: JAN 16, 2008
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: RAMAG ORDER CANCEL
 GENERAL DESCRIPTION:   The RAMAG ORDER CANCEL remote procedure cancels/holds
 the Radiology order and sends all required notifications.  
  
 Input Parameters 
 ================
  
   RAOIFN        IEN of the order in the RAD/NUC MED ORDERS file (#75.1).  
  
   RAREASON      Cancel/hold reason: either IEN of a record of the 
                 RAD/NUC MED REASON file (#75.2) or a valid synonym 
                 (see SYNONYM field (3) of that file).  
  
                 The referenced record must have the appropriate type 
                 (see TYPE OF REASON field (2) of the file #75.2): 
  
                   * If the reason record has the CANCEL REQUEST (1) 
                     type, then the 'HOLDESC' (see the RAMSC parameter) 
                     is ignored and the order is canceled.  
  
                   * If the reason record is of the HOLD REQUEST (3) 
                     type, then the order is put on hold. If the 
                     'HOLDESC' parameter is defined, the text is stored 
                     into the HOLD DESCRIPTION field.  
  
                   * If the record is of the GENERAL REQUEST type (9), 
                     then the new order status is determined by the 
                     'HOLDESC' parameter. If it is defined, then the 
                     order is put on hold; otherwise, the order is 
                     canceled.  
  
   [RAMSC]       Items of this list define miscellaneous/optional 
                 order parameters. Each record has 3 or more pieces 
                 separated by '^': 
  
                   ^01: Parameter name 
                   ^02: Index (for multiples and word-processing) 
                   ^03: Value1 
                   ^04: Value2 
                   ...
  
                 The following records are supported by this remote 
                 procedure: 
  
                   HOLDESC^{Seq#}^{Line of hold description} 
                     Text for the HOLD DESCRIPTION field (25) 
                     of the file #75.1.  
  
                 Records can be added to the list in any order.  
  
     Examples: 
  
       with RPCBroker.Param[2] do 
         begin 
           PType := list; 
           Mult[1] := 'HOLDESC^1^Hold description line #1'; 
           Mult[2] := 'HOLDESC^2^Hold description line #2'; 
         end; 
  
 Results 
 =======
  
 A negative value of the first '^'-piece of the Results[0] indicates that an
 error occurred during the execution of the remote procedure. In this case, the
 second piece of the Results[0] will contain number of the error descriptors
 returned in the subsequent nodes of the Results array.  
  
   Results[0]            Result descriptor 
                           ^01: The last error code 
                           ^02: Number of error descriptors 
   
   Results[i]            Error descriptor 
                           ^01: Error code 
                           ^02: Message 
                           ^03: Error location 
                           ^04: Error type 
   
   Results[j]            Line of the additional info 
                           ^01: "" (empty) 
                           ^02: Text 
  
 Error descriptors are returned in reverse chronological order (most recent 
 first).  
  
 Otherwise, 0 is returned in the Results[0].  
  
 Notes 
 =====
  
 If there are active cases in the RAD/NUC MED PATIENT file (#70) associated 
 with an order, this remote procedure neither cancels nor holds the order and
 returns the error code -42.  
  
 See comments in the source code of the RAMAG04 routine and description of the
 RAMAG ORDER CANCEL remote procedure for additional and/or most recent details. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING
  DATE ACTIVATED: OCT 06, 2008

NUMBER: 5075                            IA #: 5075
  DATE CREATED: JAN 16, 2008
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: RAMAG EXAM CANCEL
 GENERAL DESCRIPTION:   The RAMAG EXAM CANCEL remote procedure cancels the
 Radiology exam(s) and sends all required notifications.  
  
 If all exams that reference the same order/request are canceled, this  
 function can also cancel/hold the order (if the appropriate parameters are 
 provided).  
  
 Input Parameters 
 ================
  
   RAEXAM        String of exam/case identifiers separated by '^' 
                   ^01: IEN of the patient in the RAD/NUC MED 
                        PATIENT file (#70) 
                   ^02: IEN in the REGISTERED EXAMS multiple 
                        (sub-file #70.02) 
                   ^03: IEN in the EXAMINATIONS multiple 
                        (sub-file #70.03) 
  
   RAREASON      Reason for cancelation: either IEN of a record of 
                 the RAD/NUC MED REASON file (#75.2) or a valid 
                 synonym (see SYNONYM field (3) of the file #75.2).  
                 The referenced record must have the 'CANCEL REQUEST' 
                 or 'GENERAL REQUEST' type (see TYPE OF REASON field 
                 (2) of the file #75.2).  
  
   [RAFLAGS]     Flags that control execution (can be combined): 
  
                 A  Cancel all related exams/cases (those that 
                    reference the same order).  
  
                 O  Cancel/hold the related order after successful 
                    exam cancelation.  
  
                    The order will be canceled or put on hold only 
                    if there are no more active cases associated 
                    with it.  
  
                    Otherwise, the error code -42 will be returned.  
                    Use the "A" flag to cancel all related exams 
                    and guarantee the order cancelation.  
  
   [RAMSC]       Items of this list define miscellaneous/optional 
                 order parameters. Each record has 3 or more pieces 
                 separated by '^': 
  
                   ^01: Parameter name 
                   ^02: Index (for multiples and word-processing) 
                   ^03: Value1 
                   ^04: Value2 
                   ...
  
                 The following records are supported by this remote 
                 procedure: 
  
                   HOLDESC^{Seq#}^{Line of hold description} 
                     Text for the HOLD DESCRIPTION field (25) 
                     of the file #75.1.  
  
                   ORDRSN^^{Cancel/hold reason for related order} 
                     Either IEN of a record of the RAD/NUC MED 
                     REASON file (#75.2) or a valid synonym 
                     (see SYNONYM field (3) of that file).  
  
                     If this parameter is not defined or empty, 
                     the value of the RAREASON parameter is 
                     assumed.  
  
                 Records can be added to the list in any order.  
  
                 If the RAFLAGS parameter contains the 'O' flag, 
                 the 'ORDRSN' and 'HOLDESC' parameters determine 
                 whether the related order is canceled or put on 
                 hold. Otherwise, they are ignored.  
  
                   * If the reason record referenced by the 'ORDRSN' 
                     has the CANCEL REQUEST (1) type, then the 'HOLDESC' 
                     is ignored and the order is canceled.  
  
                   * If the record referenced by the 'ORDRSN' is of 
                     the HOLD REQUEST (3) type, then the order is put 
                     on hold. If the 'HOLDESC' is defined, the text is 
                     stored into the HOLD DESCRIPTION field.  
  
                   * If the record referenced by the 'ORDRSN' is of 
                     the GENERAL REQUEST type (9), then the action 
                     performed on the order is determined by the 
                     'HOLDESC'. If it is defined, then the order is 
                     put hold; otherwise, the order is canceled.  
  
     Examples: 
  
       with RPCBroker.Param[2] do 
         begin 
           PType := list; 
           Mult[1] := 'ORDRSN^^OHR'; 
           Mult[2] := 'HOLDESC^1^Hold description line #1'; 
           Mult[3] := 'HOLDESC^2^Hold description line #2'; 
         end; 
  
 Results 
 =======
  
 A negative value of the first '^'-piece of the Results[0] indicates that an
 error occurred during the execution of the remote procedure. In this case, the
 second piece of the Results[0] will contain number of the error descriptors
 returned in the subsequent nodes of the Results array.  
  
   Results[0]            Result descriptor 
                           ^01: The last error code 
                           ^02: Number of error descriptors 
   
   Results[i]            Error descriptor 
                           ^01: Error code 
                           ^02: Message 
                           ^03: Error location 
                           ^04: Error type 
   
   Results[j]            Line of the additional info 
                           ^01: "" (empty) 
                           ^02: Text 
  
 Error descriptors are returned in reverse chronological order (most recent 
 first).  
  
 Otherwise, 0 is returned in the Results[0].  
  
 Notes 
 =====
  
 See comments in the source code of the RAMAG05 routine and description of the
 RAMAG EXAM CANCEL remote procedure for additional and/or most recent details.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING
  DATE ACTIVATED: OCT 06, 2008

NUMBER: 5076                            IA #: 5076
  DATE CREATED: JAN 17, 2008            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: Routine
  ROUTINE: MDCLIO1                      NAME: MDCLIO1
  ID: MDCLIO1
 GENERAL DESCRIPTION:   The MDCLIO1 routine provides Clinical Observations
 data.  
  
 Note: This API is only for the Vitals package and will not be approved for 
       other packages.  
  STATUS: Other                         DURATION: Till Otherwise Agreed
KEYWORDS: CLINICAL OBSERVATIONS
COMPONENT/ENTRY POINT: QRYDATE(ARRAY,START,END)
 COMPONENT DESCRIPTION:   This entry point provides a list of OBS record IDs
 (FILE 704.117, Field .01) for the date range specified.  
  
 Output format: 
  ARRAY(0)=number of records returned 
  ARRAY(n)=record ID (FILE 704.117, Field .01) 
  
 n = sequential number starting with 1 
  
 Example: 
  
  >K RESULT 
  >D QRYDATE^MDCLIO1("RESULT",3070301,3070401) 
  >ZW RESULT 
  RESULT(0)=3 
  RESULT(1)="{FD0FEBBC-8EC1-42E4-9483-4BDBE6370728}" 
  RESULT(2)="{A7C7FFEB-0CD5-4D55-BB34-35B9620F4ECC}" 
  RESULT(3)="{D0CEA9D2-A519-41C2-A4AE-9C24C7498E56}" 
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of the array to return the data in.
 It is a closed array and surrounded in quotes (e.g., "RESULT" or "^TMP($J)").
 (required) 
VARIABLES: START                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the date/time to begin the search. It is in
 FileMan internal date/time format. If it is not defined, all records before
 the END date/time are returned.  
VARIABLES: END                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the end date of the search. It is in FileMan
 internal date/time format. If it is not defined, no records will be returned.  
COMPONENT/ENTRY POINT: QRYOBS(ARRAY,GUID)
 COMPONENT DESCRIPTION:   This entry point returns the OBS (704.117) file data
 for the specified record.  
  
 Output format: 
  ARRAY("AUDIT_EXISTS","E")=Field .911 (external) 
  ARRAY("AUDIT_EXISTS","I")=Field .911 (internal) 
  ARRAY("CHILD_ORDER","E")=Field .27 (external) 
  ARRAY("CHILD_ORDER","I")=Field .27 (internal) 
  ARRAY("COMMENT","E")=Field .4 (external) 
  ARRAY("COMMENT","I")=Field .4 (internal) 
  ARRAY("CONTEXT",0)=Number of "CONTEXT" records (in this example: 2) 
  ARRAY("CONTEXT",1,"METHOD_ID","E")="CONTEXT" nodes are returned when the 
  ARRAY("CONTEXT",1,"METHOD_ID","I")=node 'ARRAY("TERM_ID","E")="SpO2%"'.  
  ARRAY("CONTEXT",1,"OBS_ID","E")=These "CONTEXT" nodes will contain any 
  ARRAY("CONTEXT",1,"OBS_ID","I")=records about SUPPLEMENTATL OXYGEN 
  ARRAY("CONTEXT",1,"SVALUE","E")=FLOW RATE and SUPPLEMENTAL OXYGEN 
  ARRAY("CONTEXT",1,"SVALUE","I")=CONCENTRATION which are related to the 
  ARRAY("CONTEXT",1,"TERM_ID","E")=SpO2% reading.  
  ARRAY("CONTEXT",1,"TERM_ID","I")= 
  ARRAY("CONTEXT",1,"UNIT_ID","E")= 
  ARRAY("CONTEXT",1,"UNIT_ID","I")= 
  ARRAY("CONTEXT",2,"OBS_ID","E")= 
  ARRAY("CONTEXT",2,"OBS_ID","I")= 
  ARRAY("CONTEXT",2,"SVALUE","E")= 
  ARRAY("CONTEXT",2,"SVALUE","I")= 
  ARRAY("CONTEXT",2,"TERM_ID","E")= 
  ARRAY("CONTEXT",2,"TERM_ID","I")= 
  ARRAY("CONTEXT",2,"UNIT_ID","E")= 
  ARRAY("CONTEXT",2,"UNIT_ID","I")= 
  ARRAY("CORRECTION_FOR_ID","E")=Field .912 (external) 
  ARRAY("CORRECTION_FOR_ID","I")=Field .912 (internal) 
  ARRAY("ENTERED_BY_ID","E")=Field .26 (external) 
  ARRAY("ENTERED_BY_ID","I")=Field .26 (internal) 
  ARRAY("ENTERED_DATE_TIME","E")=Field .25 (external) 
  ARRAY("ENTERED_DATE_TIME","I")=Field .25 (internal) 
  ARRAY("FACILITY_ID","E")=Field .03 (external) 
  ARRAY("FACILITY_ID","I")=Field .03 (internal) 
  ARRAY("HOSPITAL_LOCATION_ID","E")=Field .04 (external) 
  ARRAY("HOSPITAL_LOCATION_ID","I")=Field .04 (internal) 
  ARRAY("LOCATION_ID","E")=FILE 704.118, Field .02 (external) 
  ARRAY("LOCATION_ID","I")=FILE 704.118, Field .02 (internal) 
  ARRAY("METHOD_ID","E")=FILE 704.118, Field .02 (external) 
  ARRAY("METHOD_ID","I")=FILE 704.118, Field .02 (internal) 
  ARRAY("OBSERVED_BY_ID","E")=Field .06 (external) 
  ARRAY("OBSERVED_BY_ID","I")=Field .06 (internal) 
  ARRAY("OBSERVED_DATE_TIME","E")=Field .05 (external) 
  ARRAY("OBSERVED_DATE_TIME","I")=Field .05 (internal) 
  ARRAY("OBS_ID","E")=Field .01 (external) 
  ARRAY("OBS_ID","I")=Field .01 (internal) 
  ARRAY("PARENT_ID","E")=Field .02 (external) 
  ARRAY("PARENT_ID","I")=Field .02 (internal) 
  ARRAY("PATIENT_ID","E")=Field .08 (external) 
  ARRAY("PATIENT_ID","I")=Field .08 (internal) 
  ARRAY("POSITION_ID","E")=FILE 704.118, Field .02 (external) 
  ARRAY("POSITION_ID","I")=FILE 704.118, Field .02 (internal) 
  ARRAY("RANGE","E")=Field .28 (external) 
  ARRAY("RANGE","I")=Field .28 (internal) 
  ARRAY("SOURCE","E")=Field .21 (external) 
  ARRAY("SOURCE","I")=Field .21 (internal) 
  ARRAY("SOURCE_COMMENTS","E")=Field .22 (external) 
  ARRAY("SOURCE_COMMENTS","I")=Field .22 (internal) 
  ARRAY("SOURCE_DATA_ITEM_ID","E")=Field .23 (external) 
  ARRAY("SOURCE_DATA_ITEM_ID","I")=Field .23 (internal) 
  ARRAY("SOURCE_VERSION","E")=Field .24 (external) 
  ARRAY("SOURCE_VERSION","I")=Field .24 (internal) 
  ARRAY("STATUS","E")=Field .09 (external) 
  ARRAY("STATUS","I")=Field .09 (internal) 
  ARRAY("SVALUE","E")=Field .1 (external) 
  ARRAY("SVALUE","I")=Field .1 (internal) 
  ARRAY("TERM_ID","E")=Field .07 (external) 
  ARRAY("TERM_ID","I")=Field .07 (internal) 
  ARRAY("UNIT_ID","E")=FILE 704.118, Field .02 (external) 
  ARRAY("UNIT_ID","I")=FILE 704.118, Field .02 (internal) 
   
 Example: 
  >D QRYOBS^MDCLIO1("ARRAY","{E24715DE-3DCC-4A04-9F8B-0A7C6E8E64F4}") 
  >ZW ARRAY 
  ARRAY("AUDIT_EXISTS","E")=0 
  ARRAY("AUDIT_EXISTS","I")=0 
  ARRAY("CHILD_ORDER","E")="" 
  ARRAY("CHILD_ORDER","I")="" 
  ARRAY("COMMENT","E")="" 
  ARRAY("COMMENT","I")="" 
  ARRAY("CONTEXT",0)=2 
  ARRAY("CONTEXT",1,"METHOD_ID","E")="NASAL CANNULA" 
  ARRAY("CONTEXT",1,"METHOD_ID","I")=4688666 
  ARRAY("CONTEXT",1,"OBS_ID","E")="{792FD976-2C7B-4BC0-8B6F-E62A520ED9AA}" 
  ARRAY("CONTEXT",1,"OBS_ID","I")="{792FD976-2C7B-4BC0-8B6F-E62A520ED9AA}" 
  ARRAY("CONTEXT",1,"SVALUE","E")=1 
  ARRAY("CONTEXT",1,"SVALUE","I")=1 
  ARRAY("CONTEXT",1,"TERM_ID","E")="SUPPLEMENTAL OXYGEN FLOW RATE" 
  ARRAY("CONTEXT",1,"TERM_ID","I")="" 
  ARRAY("CONTEXT",1,"UNIT_ID","E")="LITERS PER MINUTE" 
  ARRAY("CONTEXT",1,"UNIT_ID","I")="" 
  ARRAY("CONTEXT",2,"OBS_ID","E")="{BED624B4-A519-4928-B6EB-65C92653938E}" 
  ARRAY("CONTEXT",2,"OBS_ID","I")="{BED624B4-A519-4928-B6EB-65C92653938E}" 
  ARRAY("CONTEXT",2,"SVALUE","E")=100 
  ARRAY("CONTEXT",2,"SVALUE","I")=100 
  ARRAY("CONTEXT",2,"TERM_ID","E")="SUPPLEMENTAL OXYGEN CONCENTRATION" 
  ARRAY("CONTEXT",2,"TERM_ID","I")="" 
  ARRAY("CONTEXT",2,"UNIT_ID","E")="PERCENTAGE" 
  ARRAY("CONTEXT",2,"UNIT_ID","I")="" 
  ARRAY("CORRECTION_FOR_ID","E")="" 
  ARRAY("CORRECTION_FOR_ID","I")="" 
  ARRAY("ENTERED_BY_ID","E")="CPPROVIDER,ONE" 
  ARRAY("ENTERED_BY_ID","I")=547 
  ARRAY("ENTERED_DATE_TIME","E")="AUG 13, 2009@10:23:50" 
  ARRAY("ENTERED_DATE_TIME","I")=3090813.10235 
  ARRAY("FACILITY_ID","E")="" 
  ARRAY("FACILITY_ID","I")="" 
  ARRAY("HOSPITAL_LOCATION_ID","E")="2-AS" 
  ARRAY("HOSPITAL_LOCATION_ID","I")=1 
  ARRAY("METHOD_ID","E")="MONITOR" 
  ARRAY("METHOD_ID","I")=4688665 
  ARRAY("OBSERVED_BY_ID","E")="CPPROVIDER,ONE" 
  ARRAY("OBSERVED_BY_ID","I")=547 
  ARRAY("OBSERVED_DATE_TIME","E")="AUG 13, 2009@10:20" 
  ARRAY("OBSERVED_DATE_TIME","I")=3090813.102 
  ARRAY("OBS_ID","E")="{E24715DE-3DCC-4A04-9F8B-0A7C6E8E64F4}" 
  ARRAY("OBS_ID","I")="{E24715DE-3DCC-4A04-9F8B-0A7C6E8E64F4}" 
  ARRAY("PARENT_ID","E")="" 
  ARRAY("PARENT_ID","I")="" 
  ARRAY("PATIENT_ID","E")="CPPATIENT,ONE" 
  ARRAY("PATIENT_ID","I")=136 
  ARRAY("RANGE","E")="Normal" 
  ARRAY("RANGE","I")=1 
  ARRAY("SOURCE","E")="CP Flowsheets" 
  ARRAY("SOURCE","I")="CP Flowsheets" 
  ARRAY("SOURCE_COMMENTS","E")="" 
  ARRAY("SOURCE_COMMENTS","I")="" 
  ARRAY("SOURCE_DATA_ITEM_ID","E")="CPFLOWSHEETS.EXE:6C6B9A01" 
  ARRAY("SOURCE_DATA_ITEM_ID","I")="CPFLOWSHEETS.EXE:6C6B9A01" 
  ARRAY("SOURCE_VERSION","E")="1.0.16.276" 
  ARRAY("SOURCE_VERSION","I")="1.0.16.276" 
  ARRAY("STATUS","E")="Verified" 
  ARRAY("STATUS","I")=1 
  ARRAY("SVALUE","E")=100 
  ARRAY("SVALUE","I")=100 
  ARRAY("TERM_ID","E")="SpO2%" 
  ARRAY("TERM_ID","I")=4500637 
  ARRAY("UNIT_ID","E")="PERCENTAGE" 
  ARRAY("UNIT_ID","I")="" 
   
 Example of record not found: 
  >D QRYOBS^MDCLIO1("ARRAY","") 
  >ZW ARRAY 
  ARRAY(0)="-1^No such observation ''" 
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of the array to return the data in.
 It is a closed array and surronded in quotes (e.g., "RESULT" or "^TMP($J)").
 (required) 
VARIABLES: GUID                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the Global Unique ID (aka GUID - FILE
 704.117, Field .01) value that identifies a record. (required) 
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  DATE ACTIVATED: MAR 19, 2008

NUMBER: 5077                            IA #: 5077
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: JAN 18, 2008            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME:  Radiology write with FM privilege to the NEW PERSON file
  ID: VA(200,
GLOBAL REFERENCE: VA(200,IEN,'RAC'
FIELD NUMBER: .01                       FIELD NAME: RAD/NUC MED CLASSIFICATION
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   From the RAD/NUC MED CLASSIFICATION data dictionary
 description: 
          
 "This multiple field contains information about the classification assigned to
 Rad/Nuc Med personnel.  Possible classifications are Techn ologist,
 Interpreting Resident, Interpreting Staff, and Clerk." 
         
 Note: Changes to the data dictionary description are not automatically 
 uploaded to this IA field description.  
GLOBAL REFERENCE: VA(200,IEN,'USC1'
FIELD NUMBER: .01                       FIELD NAME: Person Class
  LOCATION: 0;1 of 'USC1'               ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   From the PERSON CLASS (#8932.1) file description: 
  
 "This file holds the CMS (HCFA) provider type data. In 2001, ANSI ASC X12N 
 asked the National Uniform Claim Committee (NUCC) to become the official 
 maintainer of the Health Care Provider Taxonomy List (provider type).  PERSON
 CLASS is to be used for identifying provider types for roll-ups." 
FIELD NUMBER: 2                         FIELD NAME: Effective Date
  LOCATION: 0;2 of 'USC1'               ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   From the data dictionary description of Effective Date: 
  
 "This field is the date after which this class becomes inactive." 
 GENERAL DESCRIPTION:   VistA Radiology requests the privilege to write to the
 NEW PERSON file using approved FileMan utilities. Radiology requests this
 privilege because the package specific Application Proxy User (APU)
 'RADIOLOGY, OUTSIDE SERVICE' requires two additional data attributes in order
 to normalize radiology workflow.  
  
 VistA Radiology requests that we be able to use FileMan to write to the 
 following fields in the NEW PERSON file: 
  
 * RAD/NUC MED CLASSIFICATION (#72) sub-file: 200.072 * PERSON CLASS (#8932.1)
 sub-file: 200.05 * Effective Date (case sensitive) sub-file: 200.05, field: 2 
  
 RAD/NUC MED CLASSIFICATION is required to move a radiology exam through to the
 COMPLETE status.  
  
 PERSON CLASS is required to credit workload. Without a PERSON CLASS attribute
 a PERSON CLASS exception for this patient care encounter event.  
  
 Effective Date is the date that this Person Class became effective for this
 individual.  
  
 Please note that the lifespan of this Integration Agreement is to be short.
 Once the patch is released, and the grace period for mandatory patch
 installations period has passed, it is my intention that this IA be purged.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ephemeral
KEYWORDS: NEW PERSON
KEYWORDS: write with FileMan
KEYWORDS: Kernel
KEYWORDS: Radiology
KEYWORDS: short term
KEYWORDS: PERSON CLASS
KEYWORDS: RAD/NUC MED CLASSIFICATION
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   VistA Radiology will use approved DBS FileMan utilities
 to populate the following fields in the NEW PERSON file: 
  
 * RAD/NUC MED CLASSIFICATION (#72) sub-file: 200.072 * PERSON CLASS (#8932.1)
 sub-file: 200.05 
  DATE ACTIVATED: JAN 18, 2008

NUMBER: 5078                            IA #: 5078
  DATE CREATED: JAN 23, 2008            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XTIDTRM
  NAME: API Set for Data Standardization
  ID: XTIDTRM
 GENERAL DESCRIPTION:   High Level Examples 
  
 Assume the following replacement relationships: 
  
  
   A --> B --> C --> D      A is replaced by B     G is replaced by C 
  ^ ^         ^ ^           B is replaced by C     H is replaced by C 
  |  \        |  \          C is replaced by D     I is replaced by F 
  |   \       |   \         D has no replacement   J is replaced by F 
  |    \      |    \        E is replaced by A     K is replaced by H 
  |     F     |     H       F is replaced by A     L is replaced by H 
  |    ^ ^    |    ^ ^
  |   /   \   |   /   \
  E  I     J  G  K     L 
  
 $$GETRPLC(B) would return C 
  
 $$RPLCMNT(B) would return D 
  
 $$RPLCVALS(J) would return the requested field values from entry D 
  
 $$RPLCTRL(G) in both directions would return D and the output array would be
 set as follows: 
  
  OutArr("BY",A) = B                  OutArr("FOR",A,E) = "" 
  OutArr("BY",B) = C                  OutArr("FOR",A,F) = "" 
  OutArr("BY",C) = D                  OutArr("FOR",B,A) = "" 
  OutArr("BY",D) = ""                 OutArr("FOR",C,B) = "" 
  OutArr("BY",E) = A                  OutArr("FOR",C,G) = "" 
  OutArr("BY",F) = A                  OutArr("FOR",C,H) = "" 
  OutArr("BY",G) = C                  OutArr("FOR",D,C) = "" 
  OutArr("BY",H) = C                  OutArr("FOR",F,I) = "" 
  OutArr("BY",I) = F                  OutArr("FOR",F,J) = "" 
  OutArr("BY",J) = F                  OutArr("FOR",H,K) = "" 
  OutArr("BY",K) = H                  OutArr("FOR",H,L) = "" 
  OutArr("BY",L) = H 
  
 $$RPLCTRL(L) in the forward direction would return D and the output array
 would be set as follows: 
  
  OutArr("BY",C) = D                  OutArr("FOR",C,H) = "" 
  OutArr("BY",D) = ""                 OutArr("FOR",D,C) = "" 
  OutArr("BY",H) = C                  OutArr("FOR",H,L) = "" 
  OutArr("BY",L) = H 
  
 $$RPLCTRL(B) in the backward direction would return D and the output array
 would be set as follows: 
  
  OutArr("BY",A) = B                  OutArr("FOR",A,E) = "" 
  OutArr("BY",E) = A                  OutArr("FOR",A,F) = "" 
  OutArr("BY",F) = A                  OutArr("FOR",B,A) = "" 
  OutArr("BY",I) = F                  OutArr("FOR",F,I) = "" 
  OutArr("BY",J) = F                  OutArr("FOR",F,J) = "" 
  
 $$RPLCLST(G) in both directions would return D and the output array would be
 set as follows: 
  
  OutArr(1) = G ^ 0                   OutArr("INDEX",A) = 8 
  OutArr(2) = C ^ 0                   OutArr("INDEX",B) = 7 
  OutArr(3) = D ^ 1                   OutArr("INDEX",C) = 2 
  OutArr(4) = H ^ 0                   OutArr("INDEX",D) = 3 
  OutArr(5) = K ^ 0                   OutArr("INDEX",E) = 9 
  OutArr(6) = L ^ 0                   OutArr("INDEX",F) = 10 
  OutArr(7) = B ^ 0                   OutArr("INDEX",G) = 1 
  OutArr(8) = A ^ 0                   OutArr("INDEX",H) = 4 
  OutArr(9) = E ^ 0                   OutArr("INDEX",I) = 11 
  OutArr(10) = F ^ 0                  OutArr("INDEX",J) = 12 
  OutArr(11) = I ^ 0                  OutArr("INDEX",K) = 5 
  OutArr(12) = J ^ 0                  OutArr("INDEX",L) = 6 
  
 $$RPLCLST(L) in the forward direction would return D and the output array 
 would be set as follows if the status history was also included: 
  
  OutArr(1) = L ^ 0                   OutArr("INDEX",C) = 3 
  OutArr(1,3080101.0954) = 0          OutArr("INDEX",D) = 4 
  OutArr(2) = H ^ 0                   OutArr("INDEX",H) = 2 
  OutArr(2,3080101.1308) = 1          OutArr("INDEX",L) = 1 
  OutArr(2,3080105.09) = 0 
  OutArr(3) = C ^ 0 
  OutArr(3,3080105.0859) = 1 
  OutArr(3,3080112.1722) = 0 
  OutArr(4) = D ^ 1 
  OutArr(4,3080112.1723) = 1 
  
 $$RPLCLST(B) in the backward direction would return D and the output array
 would be set as follows: 
  
  OutArr(1) = A ^ 0                   OutArr("INDEX",A) = 1 
  OutArr(2) = E ^ 0                   OutArr("INDEX",E) = 2 
  OutArr(3) = F ^ 0                   OutArr("INDEX",F) = 3 
  OutArr(4) = I ^ 0                   OutArr("INDEX",I) = 4 
  OutArr(5) = J ^ 0                   OutArr("INDEX",J) = 5 
  
  STATUS: Active
KEYWORDS: VUID
KEYWORDS: DATA STANDARDIZATION
KEYWORDS: TERM
KEYWORDS: REPLACEMENT TERM
COMPONENT/ENTRY POINT: $$RPLCMNT
 COMPONENT DESCRIPTION:   $$RPLCMNT^XTIDTRM recursively traverses the REPLACED
 BY VHA STANDARD TERM field (#99.97) until the final replacement term is
 reached.  
  
 Usage: 
  
 S X=$$RPLCMNT^XTIDTRM(FILE,IEN) 
  
 Sets X to IEN_";"_FileNumber of the entry that ultimately replaces the input 
 entry.  
  
 Notes: 
  
 Null is returned on error. This typically will occur when the input entry does 
 not exist.  
  
 If the input entry is not replaced by another term then a reference to the 
 input term will be returned.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   File number 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Entry number 
  
COMPONENT/ENTRY POINT: $$RPLCVALS
 COMPONENT DESCRIPTION:   $$RPLCVALS^XTIDTRM retrieves one or more fields of
 data from an entry's replacement term.  The REPLACED BY VHA STANDARD TERM
 field (#99.97) is recursively traversed until the final replacement term is
 reached.  The requested field(s) of the final replace replacement term are
 returned.  
  
 This effectively bundles $$RPLCMNT^XTIDTRM and GETS^DIQ into a single call.  
  
 Usage: 
  
 S X=$$RPLCVALS^XTIDTRM(File,IEN,Fields,Flags,OutArr) 
  
 Sets X to IEN_";"_FileNumber of the entry that ultimately replaces the input
 entry.  
  
 Notes: 
  
 Null is returned on error.  This typically will occur when the input entry 
 does not exist.  
  
 If an error occurs when extracting the requested fields from the final 
 replacement term then a reference to the final replacement term will still be 
 returned and OUTARR will be KILLed.  
  
 If the input entry is not replaced by another term then a reference to the 
 input term will be returned and OutArr( ) will contain the field values for 
 the input entry.  
  
  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   File Number 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Entry number 
  
VARIABLES: FIELDS                       TYPE: Input
 VARIABLES DESCRIPTION:   Field(s) to get values for.  See definition of FIELD
 parameter in GETS^DIQ for detailed description.  
  
VARIABLES: FLAGS                        TYPE: Input
 VARIABLES DESCRIPTION:   Flag(s) that control output format.  See definition
 of FLAGS parameter in GETS^DIQ for detailed description.  
  
VARIABLES: OUTARR                       TYPE: Both
 VARIABLES DESCRIPTION:   I: Array to put output field values into (closed
 root) 
  
 O: The output array is in FDA format.  See GETS^DIQ for example output.  
  
COMPONENT/ENTRY POINT: $$RPLCTRL
 COMPONENT DESCRIPTION:   $$RPLCTRL^XTIDTRM traverses the REPLACED BY VHA
 STANDARD TERM field (#99.97) forwards and backwards to find all terms that are
 replacement terms for the input entry and all terms that the input entry is a
 replacement for.  This is recursively done so that each potential branch of
 replacement terms forwards and backwards is traversed.  
  
 Usage: 
  
 S X=$$RPLCTRL^XTIDTRM(File,IEN,Drctn,OutArr) 
  
 Sets X to IEN_";"_FileNumber of the entry that ultimately replaces the input 
 entry.  
  
 Notes: 
  
 Null is returned on error.  This typically will occur when the input entry 
 does not exist.  
  
 If the input entry is not replaced by another term then a reference to the 
 input term will be returned.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   File number 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Entry number 
  
VARIABLES: DRCTN                        TYPE: Input
 VARIABLES DESCRIPTION:   Flags denoting which direction(s) to follow the trail
 of replacement terms.  Possible flag values are: 
  
  F = Follow the trail forwards 
  B = Follow the trail backwards 
  * = Follow the trail in both directions (same as FB/BF) 
  
 (optional - defaults to 'F') 
  
VARIABLES: OUTARR                       TYPE: Both
 VARIABLES DESCRIPTION:   I: Array to put trail of replacement terms into
 (closed root).  
  
 O: The output array will contain the trail of replacement terms.  
  
  OutArr("BY",Term) =  Replacement Term 
       means: Entry 'Term' is replaced BY entry 'Replacement Term' 
  
  OutArr("FOR",Replacement Term, Term) = "" 
       means: Entry 'Replacement Term' is a replacement FOR entry 'Term' 
  
 Term and Replacement Term will be in the format IEN;FileNumber 
  
COMPONENT/ENTRY POINT: $$RPLCLST
 COMPONENT DESCRIPTION:   $$RPLCLST^XTIDTRM traverses the REPLACED BY VHA
 STANDARD TERM field (#99.97) forwards and backwards to find all terms that are
 replacement terms for the input entry and all terms that the input entry is a
 replacement for.  This is recursively done so that each potential branch of
 replacement terms forwards and backwards is traversed.  
  
 Usage: 
  
 S X=$$RPLCLST^XTIDTRM(File,IEN,Drctn,StatDate,StatHst,OutArr) 
  
 Sets X=IEN_";"_FileNumber of the entry that ultimately replaces the input
 entry.  
  
 Notes: 
  
 Null is returned on error.  This typically will occur when the input entry 
 does not exist.  
  
 If the input entry is not replaced by another term then a reference to the 
 input term will be returned.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   File number 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Entry number 
  
VARIABLES: DRCTN                        TYPE: Input
 VARIABLES DESCRIPTION:   Flags denoting which direction(s) to follow the trail
 of replacement terms.  Possible flag values are: 
  
  F = Follow the trail forwards 
  B = Follow the trail backwards 
  * = Follow the trail in both directions (same as FB/BF) 
  
 (optional - defaults to 'F') 
  
VARIABLES: STATDATE                     TYPE: Input
 VARIABLES DESCRIPTION:   FileMan date/time to return term's status on 
  
 (optional - defaults to current date/time) 
  
VARIABLES: STATHST                      TYPE: Input
 VARIABLES DESCRIPTION:   Flag denoting if a term's full status history should
 be included in the output 
  
 0 = No 1 = Yes 
  
 (optional - defaults to 0) 
  
VARIABLES: OUTARR                       TYPE: Both
 VARIABLES DESCRIPTION:   I: Array to put trail of replacement terms into
 (closed root) 
  
 O: The output array will contain the list terms that the input entry is 
 somehow related to.  
  
  OutArr(1..n) = Term ^ StatusCode [based on input StatDate] 
  OutArr(1..n,StatusDateTime) = StatusCode on this date/time 
    The above node is only returned if StatHst is set to '1' (yes) 
  OutArr("INDEX",Term) = 1..n 
  
 Term will be in the format IEN;FileNumber 
  
 StatusCode: 
  1 = Active 
  0 = Inactive 
  
 StatusDateTime will be in FileMan format 
  
COMPONENT/ENTRY POINT: $$GETRPLC
 COMPONENT DESCRIPTION:   $$GETRPLC^XTIDTRM gets the REPLACED BY VHA STANDARD
 TERM field (#99.97) for a given entry.  
  
 Usage: 
  
 S X=$$GETRPLC^XTIDTRM(File,IEN) 
  
 Sets X to IEN_";"_FileNumber of entry that replaces the input entry.  
  
 Notes: 
  
 Null is returned on error.  This typically will occur when the input entry 
 does not exist.  
  
 If the input entry is not replaced by another term then a reference to the 
 input term will be returned.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   File Number 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Entry number 
  
COMPONENT/ENTRY POINT: $$SETRPLC
 COMPONENT DESCRIPTION:   $$SETRPLC^XTIDTRM sets the REPLACED BY VHA STANDARD
 TERM field (#99.97).  
  
 Usage: 
  
 S X=$$SETRPLC^XTIDTRM(File,IEN,Rplcmnt) 
  
 Sets X to 1 if Pointer to replacement term stored (ie success) 
        or 0 if Unable to store pointer to replacement term (ie failure) 
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   File number 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Entry number 
  
VARIABLES: RPLCMNT                      TYPE: Input
 VARIABLES DESCRIPTION:   Entry number of replacement term 
  
  DATE ACTIVATED: JUN 08, 2015

NUMBER: 5079                            IA #: 5079
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAA79                       NAME: 5079 - FBAA79 for FBCS (DSS)
  ORIGINAL NUMBER: 5079                 ID: FBAA79
 GENERAL DESCRIPTION:   Request access to GOT^FBAA79 for FBCS (Fee Basis
 Compliance Suite).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: GOT
 COMPONENT DESCRIPTION:   Used to print an existing 7079.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN from file 161.  
VARIABLES: FBJ                          TYPE: Input
 VARIABLES DESCRIPTION:   Today's Date (Fileman format) 
VARIABLES: FBK                          TYPE: Input
 VARIABLES DESCRIPTION:   Authorization from date IEN, subfile 161.01 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5080                            IA #: 5080
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAACCB0                     NAME: 5080 - FBAACCB0 for FBCS (DSS)
  ORIGINAL NUMBER: 5079                 ID: FBAACCB0
 GENERAL DESCRIPTION:   Access to FBCKT and ENV^FBAACCB0 for FBCS.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: ENV
VARIABLES: K                            TYPE: Input
 VARIABLES DESCRIPTION:   Fee Basis Vendor IEN (File #161.2) 
VARIABLES: V                            TYPE: Output
 VARIABLES DESCRIPTION:   Vendor name if present otherwise returns "" 
VARIABLES: VID                          TYPE: Output
 VARIABLES DESCRIPTION:   Fee Basis Vendor ID Number 
COMPONENT/ENTRY POINT: FBCKT
 COMPONENT DESCRIPTION:   Returns check information for travel payment 
VARIABLES: J                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Patient in Fee Basis Payment file (#162) 
VARIABLES: K                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of TRAVEL PAYMENT DATE multiple (#162.04
 sub-file) 
VARIABLES: V                            TYPE: Output
 VARIABLES DESCRIPTION:   The value of the NAME (#.01) field.  
VARIABLES: FBCKDT                       TYPE: Output
 VARIABLES DESCRIPTION:   The internal value of the DATE PAID (#8) field.  
VARIABLES: FBCK                         TYPE: Output
 VARIABLES DESCRIPTION:   The value of the CHECK NUMBER (field #9) 
VARIABLES: FBCANDT                      TYPE: Output
 VARIABLES DESCRIPTION:   The internal value of the CANCELLATION DATE (#10)
 field.  
VARIABLES: FBCANR                       TYPE: Output
 VARIABLES DESCRIPTION:   The internal value of the REASON CODE (#11) field.  
VARIABLES: FBCAN                        TYPE: Output
 VARIABLES DESCRIPTION:   The internal value of the CANCELLATION ACTIVITY (#12)
 field.  
VARIABLES: FBDIS                        TYPE: Output
 VARIABLES DESCRIPTION:   The value of the DISBURSED AMOUNT (#13) field.  
VARIABLES: FBCKINT                      TYPE: Output
 VARIABLES DESCRIPTION:   The value of the INTEREST AMOUNT (#14) field.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5081                            IA #: 5081
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAACCB2                     NAME: 5081 - FBAACCB2 for FBCS (DSS)
  ORIGINAL NUMBER: 5079                 ID: FBAACCB2
 GENERAL DESCRIPTION:   Access to FBAACCB2 requested for support of FBCS 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: FBCKO
 COMPONENT DESCRIPTION:   returns check information for an outpatient/ancillary
 payment.  
VARIABLES: J                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) IEN of PATIENT in FEE BASIS PAYMENT  (File
 162) 
VARIABLES: K                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) IEN of Vendor subfile (File 162.01) 
VARIABLES: L                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) IEN of date of service (sub-file 162.02) 
VARIABLES: M                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) IEN of Service Provided (sub-file 162.03) 
VARIABLES: FBCKIN                       TYPE: Output
 VARIABLES DESCRIPTION:   Equal to global node: $G(^FBAAC(J,1,K,1,L,1,M,2)) -
 File 162.06 (CPT Modifiers) 
VARIABLES: FBCAN                        TYPE: Output
 VARIABLES DESCRIPTION:   The internal value of the CANCELLATION ACTIVITY (#38)
 field.  
VARIABLES: FBCKDT                       TYPE: Output
 VARIABLES DESCRIPTION:   The internal value of the DATE PAID (#12) field.  
VARIABLES: FBCK                         TYPE: Output
 VARIABLES DESCRIPTION:   Check Number 
VARIABLES: FBCANDT                      TYPE: Output
 VARIABLES DESCRIPTION:   The internal value of the CANCELLATION DATE (#36)
 field.  
VARIABLES: FBCANR                       TYPE: Output
 VARIABLES DESCRIPTION:   The internal value of the REASON CODE (#37) field.  
VARIABLES: FBDIS                        TYPE: Output
 VARIABLES DESCRIPTION:   The value of the DISBURSED AMOUNT (#40) field.    
VARIABLES: FBCKINT                      TYPE: Output
 VARIABLES DESCRIPTION:   The value of the INTEREST AMOUNT (#41) field.  
COMPONENT/ENTRY POINT: PMNT
 COMPONENT DESCRIPTION:   displays check and cancellation information 
VARIABLES: FBCK                         TYPE: Input
 VARIABLES DESCRIPTION:   Check Number 
VARIABLES: FBCKDT                       TYPE: Input
 VARIABLES DESCRIPTION:   Date Paid (internal FileMan) 
VARIABLES: FBCKINT                      TYPE: Input
 VARIABLES DESCRIPTION:   Field #14, file #162.04 - Interest amount 
VARIABLES: FBDIS                        TYPE: Input
 VARIABLES DESCRIPTION:   Field #13, file 162.04 - Disbursed amount 
VARIABLES: A2                           TYPE: Both
 VARIABLES DESCRIPTION:   +A2 is Amount paid.  
VARIABLES: FBCANDT                      TYPE: Input
 VARIABLES DESCRIPTION:   Cancellation date (internal Fileman( 
VARIABLES: FBCANR                       TYPE: Input
 VARIABLES DESCRIPTION:   pointer to 162.95) Reason code.  
VARIABLES: FBCAN                        TYPE: Output
 VARIABLES DESCRIPTION:   Cancellation Activity Code 
COMPONENT/ENTRY POINT: PMTCLN
 COMPONENT DESCRIPTION:   Used by DSS routines: DSIFRPT4,DSIFRPT5 to kill
 variables used when closing a batch.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5082                            IA #: 5082
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FBAACO
  NAME: 5082 - FBAACO For FBCS (DSS)    ORIGINAL NUMBER: 5079
  ID: FBAACO
 GENERAL DESCRIPTION:   Access to FBAACO for FBCS.  
   
   SITE^FBAACO (set up site variables) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: SITE
 COMPONENT DESCRIPTION:   set up site variables 
VARIABLES: FBSITE(0)                    TYPE: Both
 VARIABLES DESCRIPTION:   Equal to $G(^FBAA(161.4,1,0)) [FEE BASIS SITE
 PARAMETERS FILE] 
VARIABLES: FBPOP                        TYPE: Output
 VARIABLES DESCRIPTION:   Error condition exists flag 
VARIABLES: FBSITE(1)                    TYPE: Output
 VARIABLES DESCRIPTION:   Equals $G(^FBAA(161.4,1,1)) 
COMPONENT/ENTRY POINT: Q
 COMPONENT DESCRIPTION:   Kills payment variables cleanly 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5083                            IA #: 5083
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAADD                       NAME: 5083 - FBAADD for FBCS (DSS)
  ORIGINAL NUMBER: 5079                 ID: FBAADD
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: ALLC
 COMPONENT DESCRIPTION:   (not used at this time by FBCS) 
COMPONENT/ENTRY POINT: ALLM
 COMPONENT DESCRIPTION:   rejects all line items in a B3 type batch.  File
 161.7 and file 162 are updated. 
VARIABLES: B                            TYPE: Input
 VARIABLES DESCRIPTION:   (required) IEN from Batch File (#161.7) 
VARIABLES: J                            TYPE: Output
 VARIABLES DESCRIPTION:   Pt IEN from file #162 (field #.01) 
VARIABLES: K                            TYPE: Output
 VARIABLES DESCRIPTION:   Vendor IEN from File #162 (field #6) 
VARIABLES: L                            TYPE: Output
 VARIABLES DESCRIPTION:   IEN of Initial Treatment Date, file 162 (field #1) 
VARIABLES: M                            TYPE: Output
 VARIABLES DESCRIPTION:   IEN of Service Provided of file #162 (field #2) 
VARIABLES: FBIN                         TYPE: Output
 VARIABLES DESCRIPTION:   IEN of Invoice Number (field #14) 
VARIABLES: FBRR                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required, "" if not used) IEN of reject reason  used
 to update field #20 in sub-file 162.03.  
COMPONENT/ENTRY POINT: ALLP
 COMPONENT DESCRIPTION:   (Not used by FBCS at this time) 
COMPONENT/ENTRY POINT: ALLT
 COMPONENT DESCRIPTION:   (Not used by FBCS at this time) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5084                            IA #: 5084
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAADV                       NAME: 5084 - FBAADV for FBCS (DSS)
  ORIGINAL NUMBER: 5079                 ID: FBAADV
 GENERAL DESCRIPTION:   Access to CHVEN^FBAADV for FBCS.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$CHKVEN
 COMPONENT DESCRIPTION:   checks to see if a change or add is pending for a
 vendor 
VARIABLES: FBVIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Required) IEN of Fee Basis Vendor (file 161.2) 
VARIABLES: FBVC                         TYPE: Output
 VARIABLES DESCRIPTION:   Pieces 2 and 3 from file 161.25 (Piece 2 is filed #1
 - Pharmacy type action; Peice 3 is field #2 - Non-pharmacy type correction) 
  
 Pieces are then stripped of the "^" delimiter.  
VARIABLES: FBCS                         TYPE: Output
 VARIABLES DESCRIPTION:   value 0, 1, or 2 where 0 = nothing pending, 1 =
 change or add awaiting Austin approval, 2 = change or add on linked vendor
 awaiting Austin approval.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5085                            IA #: 5085
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAFA                       NAME: 5085 - FBAAFA for FBCS (DSS)
  ORIGINAL NUMBER: 5079                 ID: FBAAFA
 GENERAL DESCRIPTION:   FBCS Access to Subs:  
    LOADADJ^FBAAFA (Load Adjustments FROM FILE 162.03) 
     ADJLRA^FBAAFA (Adjustment Reason^Amount List Extrinsic Function) 
    FILEADJ^FBAAFA (File Adjustments FOR 162.03) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: LOADADJ(FBIENS,.FBADJ)
 COMPONENT DESCRIPTION:   Load existing Adjustments from file 162.  
VARIABLES: FBIENS                       TYPE: Input
 VARIABLES DESCRIPTION:   required, internal entry numbers for subfile 162.03
 in standard format as specified for FileMan DBS calls 
VARIABLES: FBADJ                        TYPE: Both
 VARIABLES DESCRIPTION:   required, array passed by reference used to load
 adjustments into.  
  
 Output: ;               FBADJ(#)=FBADJR^FBADJG^FBADJA 
  ;             where 
  ;               # = sequentially assigned number starting with 1 
  ;               FBADJR = adjustment reason (internal value file 162.91) 
  ;               FBADJG = adjustment group (internal value file 162.92) 
  ;               FBADJA = adjustment amount (dollar value) 
  ;             if no adjustments are on file then the array will be 
  ;               undefined 
VARIABLES: FBADJR                       TYPE: Output
 VARIABLES DESCRIPTION:   adjustment reason (internal value file 162.91) 
VARIABLES: FBADJG                       TYPE: Output
 VARIABLES DESCRIPTION:   adjustment group (internal value file 162.92) 
VARIABLES: FBADJA                       TYPE: Output
 VARIABLES DESCRIPTION:   adjustment amount (dollar value) 
COMPONENT/ENTRY POINT: $$ADJLRA(M_","_L_","_K_","_J_",")
 COMPONENT DESCRIPTION:   Adjustment Reason^Amount List Extrinsic Function 
VARIABLES: M                            TYPE: Input
 VARIABLES DESCRIPTION:   Service Provided IEN, subfile 162.03 
VARIABLES: L                            TYPE: Input
 VARIABLES DESCRIPTION:   Initial treatment date IEN, subfile 162.02 
VARIABLES: K                            TYPE: Input
 VARIABLES DESCRIPTION:   Vendor IEN, subfile 162.02 
VARIABLES: J                            TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN, field .01 of file 162 
COMPONENT/ENTRY POINT: FILEADJ(FBAACPI,FBSDI,FBV,DFN,.FBADJ)
 COMPONENT DESCRIPTION:   File the adjustment in file 162.03 function 
VARIABLES: FBIENS                       TYPE: Input
 VARIABLES DESCRIPTION:   Variable set with: FBAACPI_,_FBSDI_,_FBV_,_DFN Where:
 DFN=Patient IEN 
        FBV=Vendor IEN 
       FBSDI=Date os service multiple IEN 
     FBAACPI=Service provided multiple IEN 
VARIABLES: FBADJ                        TYPE: Input
 VARIABLES DESCRIPTION:   
  ;   FBADJ   - required, array passed by reference 
  ;             array of adjustments to file 
  ;             array does not have to contain any data or be defined 
  ;             format 
  ;               FBADJ(#)=FBADJR^FBADJG^FBADJA 
  ;             where 
  ;               # = sequentially assigned number starting with 1 
  ;               FBADJR = adjustment reason (internal value file 161.91) 
  ;               FBADJG = adjustment group (internal value file 161.92) 
  ;               FBADJA = adjustment amount (dollar value) 
  
 NOTE: in FILEADJ^FBAAFA the above internal file entries are wrong, they show
 the files as (internal value file 162.91 and 162.92) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5086                            IA #: 5086
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAFR                       NAME: 5086 - FBAAFR for FBCS (DSS)
  ORIGINAL NUMBER: 5079                 ID: FBAAFR
 GENERAL DESCRIPTION:   Access to FILERR^FBAAFR and RRL^FBAAFR for FBCS.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$RRL
 COMPONENT DESCRIPTION:   $$RRL(K_","_B_","_DA_","_DFN_",") 
VARIABLES: K                            TYPE: Input
 VARIABLES DESCRIPTION:   Service Provided IEN 
VARIABLES: B                            TYPE: Input
 VARIABLES DESCRIPTION:   Service provided date IEN 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Vendor IEN 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pt IEN 
COMPONENT/ENTRY POINT: FILERR(FBIENS,.FBRRMK)
 COMPONENT DESCRIPTION:   
  File Remittance Remarks 
VARIABLES: FBIENS                       TYPE: Input
 VARIABLES DESCRIPTION:   required, internal entry numbers for subfile 162.03 A
 string of IENs: "Pt IEN,Vendor IEN,Service provided date IEN,Service provided
 IEN" 
VARIABLES: FBRRMK                       TYPE: Input
 VARIABLES DESCRIPTION:   An array of remittance remarks 
  
 Format: 
  ;               FBRRMK(#)=FBRRMKC 
  ;             where 
  ;               # = sequentially assigned number starting with 1 
  ;               FBRRMKC = remittance remark (internal value file 162.93) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5087                            IA #: 5087
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAFS                       NAME: 5087 - FBAAFS for FBCS (DSS)
  ORIGINAL NUMBER: 5079                 ID: FBAAFS
 GENERAL DESCRIPTION:   Access to FAC^FBAAFS and GET^FBAAFS for FBCS.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$FAC(FBHCFA(30))
 COMPONENT DESCRIPTION:   call to determine if the place of service is a
 facility 
VARIABLES: FBHCFA(30)                   TYPE: Both
 VARIABLES DESCRIPTION:   POS - place of service, internal, pointer to #353.1 
COMPONENT/ENTRY POINT: $$GET(FBCPT,FBMODL,FBDOS,FBZIP,FBFAC)
 COMPONENT DESCRIPTION:   call to calculate Fee Schedule amount 
VARIABLES: FBCPT                        TYPE: Input
 VARIABLES DESCRIPTION:   CPT/HCPCS code, external value, required 
VARIABLES: FBMODL                       TYPE: Input
 VARIABLES DESCRIPTION:   list of optional CPT/HCPCS modifiers, external values
 "," delimited 
VARIABLES: FBDOS                        TYPE: Input
 VARIABLES DESCRIPTION:   Date of service (FM format) 
VARIABLES: FBZIP                        TYPE: Input
 VARIABLES DESCRIPTION:   Zip code, 5 digit, required 
VARIABLES: FBFAC                        TYPE: Input
 VARIABLES DESCRIPTION:   facility flag, 0 or 1, required,  indicates if
 procedure was performed in facility (1) or non-facility (0) 
COMPONENT/ENTRY POINT: $$ANES(CPT)
 COMPONENT DESCRIPTION:   returns 1 if CPT is an anesthesia code else return 0. 
 
VARIABLES: CPT                          TYPE: Input
 VARIABLES DESCRIPTION:   5 digit CPT code (external) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5088                            IA #: 5088
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAARB                       NAME: 5088 - FBAARB for FBCS (DSS)
  ORIGINAL NUMBER: 5079                 ID: FBAARB
 GENERAL DESCRIPTION:   Access to CNTTOT^FBAARB for FBCS.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: CNTTOT(IEN)
 COMPONENT DESCRIPTION:   called to determine line count and total dollars for
 a batch 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of batch in 161.7 
VARIABLES: FBLCNT                       TYPE: Output
 VARIABLES DESCRIPTION:   total line items in batch 
VARIABLES: FBTOTAL                      TYPE: Output
 VARIABLES DESCRIPTION:   
  total dollars in batch 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5089                            IA #: 5089
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAARR                       NAME: 5089- FBAARR for FBCS (DSS)
  ORIGINAL NUMBER: 5089                 ID: FBAARR
 GENERAL DESCRIPTION:   Access to CKSPLIT^FBAARR for FBCS.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$CKSPLIT(B,.FBILM)
 COMPONENT DESCRIPTION:   Check for/Update split invoice 
VARIABLES: B                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of original batch (File 161.7) before item moved 
VARIABLES: FBILM                        TYPE: Input
 VARIABLES DESCRIPTION:   FBILM(FBIN,M_","_L_","_K_","_J_",")=""  (FBIN= Batch
 IEN, J=Pt IEN,K=Vendor IEN,L=Date of Service IEN,M=Service provided IEN) 
  
  FBILM( - array of invoice lines that were moved to a new batch 
  ;     passed by reference 
  ;     format FBILM(invoice number,iens)="" 
  ;     where 
  ;       invoice number = invoice number 
  ;       iens           = iens of subfile 162.03 (a line item) 
VARIABLES: #
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5090                            IA #: 5090
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAUTL                      NAME: 5090 - FBAAUTL for FBCS (DSS)
  ORIGINAL NUMBER: 5089                 ID: FBAAUTL
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: PDF
 COMPONENT DESCRIPTION:   Date converter (FM to external) 
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   FM date passed in, external date returned 
COMPONENT/ENTRY POINT: SITEP
 COMPONENT DESCRIPTION:   SET FBSITE(0),FBSITE(1) VARIABLE TO FEE SITE
 PARAMETERS (File 161.4) 
VARIABLES: FBSITE(0)                    TYPE: Output
 VARIABLES DESCRIPTION:   FBSITE(0)=$G(^FBAA(161.4,1,0)) 
VARIABLES: FBSITE(1)                    TYPE: Output
 VARIABLES DESCRIPTION:   FBSITE(1)=$G(^FBAA(161.4,1,1)) 
VARIABLES: FBPOP                        TYPE: Output
 VARIABLES DESCRIPTION:   ERROR flag = "Fee Basis Site Parameters must be
 entered to proceed" 
COMPONENT/ENTRY POINT: $$SSN(DFN)
 COMPONENT DESCRIPTION:   
  ;PID = DFN of Patient. If this is all that is past, 
  ;full Pt.ID (000-00-0000) will be returned.  
  ;If BID = 1 the call will return last 4 of Pt.ID only.  
  ;If DOD is defined to internal entry # of eligibility the appropriate 
  ;Pt.ID will be returned 
VARIABLES: PID                          TYPE: Input
 VARIABLES DESCRIPTION:   Pt IEN 
VARIABLES: BID                          TYPE: Input
 VARIABLES DESCRIPTION:   If BID = 1 the call will return last 4 of Pt.ID only 
VARIABLES: DOD                          TYPE: Input
 VARIABLES DESCRIPTION:   If DOD is defined to internal entry # of eligibility
 the appropriate Pt.ID will be returned 
VARIABLES: FBSSN                        TYPE: Output
 VARIABLES DESCRIPTION:   SSN, terminal digits, or error message 
COMPONENT/ENTRY POINT: $$DATX(FBVCHDT)
 COMPONENT DESCRIPTION:   external output function for date format 
VARIABLES: FBVCHDT                      TYPE: Both
 VARIABLES DESCRIPTION:   INPUT = FM internal date format (time optional) 
  
 OUTPUT = date/time with slashes 
COMPONENT/ENTRY POINT: $$GETNXI
 COMPONENT DESCRIPTION:   GET NEXT AVAILABLE INVOICE NUMBER 
VARIABLES: FBAAIN                       TYPE: Output
 VARIABLES DESCRIPTION:   Invoice number File 161.4, field #11 
COMPONENT/ENTRY POINT: GETNXB
 COMPONENT DESCRIPTION:   GET NEXT AVAILABLE BATCH NUMBER 
VARIABLES: FBBN                         TYPE: Output
 VARIABLES DESCRIPTION:   Batch IEN 
COMPONENT/ENTRY POINT: STATION
 COMPONENT DESCRIPTION:   Get Station Number from INSTITUTION (#4) file 
VARIABLES: FBSN                         TYPE: Output
 VARIABLES DESCRIPTION:   Station Number 
VARIABLES: FBAASN                       TYPE: Output
 VARIABLES DESCRIPTION:   Station Number 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5091                            IA #: 5091
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAUTL4                     NAME: 5091 - FBAAUTL4 for FBCS (DSS)
  ORIGINAL NUMBER: 5089                 ID: FBAAUTL4
 GENERAL DESCRIPTION:   Access requested for several access points to support
 FBCS.  Access points:  $$APS,$$CPT,$$MODL,$$CHKBI,REPMOD and MODDATA 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$MODL(FBAN,FBFLAG)
 COMPONENT DESCRIPTION:   return sorted list given array of modifiers 
VARIABLES: FBAN                         TYPE: Input
 VARIABLES DESCRIPTION:   closed root of array containing modifiers 
  ;          the data must be in nodes descendent from this root.  
  ;          The subscripts of the nodes below FBAN must be 
  ;          positive numbers. The CPT MODIFIER internal value 
  ;          must be the first piece in these nodes or in the 
  ;          0-node descendent from these nodes.  
  ;          i.e.  
  ;            ARRAY(number)=CPT MODIFIER (internal value) 
  ;                  OR 
  ;            ARRAY(number,0)=CPT MODIFIER (internal value) 
VARIABLES: FBFLAG                       TYPE: Input
 VARIABLES DESCRIPTION:   I to return internal values of modifiers, E to return
 external values of modifiers 
  
 (optional) flag, E or I, default I 
COMPONENT/ENTRY POINT: REPMOD(FBJ,FBK,FBL,FBM)
 COMPONENT DESCRIPTION:   Replace CPT Modifier(s) in payment 
VARIABLES: FBK                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of VENDOR multiple in file 162 (Subfile 162.01) 
VARIABLES: FBL                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of INITIAL TREATMENT DATE multiple in file 162
 (Subfile 162.02) 
VARIABLES: FBM                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of SERVICE PROVIDED multiple in file 162 (Subfile
 162.03) 
VARIABLES: FBJ                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of PATIENT in file 162 
VARIABLES: FBMODA                       TYPE: Input
 VARIABLES DESCRIPTION:   FBMODA( array of modifiers where FBMODA(number)=CPT
 Modifier (internal) 
COMPONENT/ENTRY POINT: MODDATA(W,X,Y,Z)
 COMPONENT DESCRIPTION:   get internal values of CPT Modifier 
VARIABLES: W                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of PATIENT in file 162 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of VENDOR multiple in file 162 (Subfile 162.01) 
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of INITIAL TREATMENT DATE multiple in file 162
 (Subfile 162.02) 
VARIABLES: Z                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of SERVICE PROVIDED multiple in file 162 (Subfile
 162.03) 
COMPONENT/ENTRY POINT: $$APS(FBJ,FBK,FBL,FBM)
 COMPONENT DESCRIPTION:   amount paid symbol 
VARIABLES: FBJ                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of PATIENT in file 162 
VARIABLES: FBK                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of VENDOR multiple in file 162 
VARIABLES: FBL                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of INITIAL TREATMENT DATE multiple in file 162 
VARIABLES: FBM                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of SERVICE PROVIDED multiple in file 162 
VARIABLES: FBRET                        TYPE: Output
 VARIABLES DESCRIPTION:   M (Mill Bill emergency care - 38 U.S.C. 1725) R
 (RBRVS fee schedule amount) F (VA fee schedule amount) C (contracted service
 amount) U (usual & customary - claimed) 
                null if no amount paid 
COMPONENT/ENTRY POINT: $$CPT(X,Y,DT)
 COMPONENT DESCRIPTION:   return external format of CPT code 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of CPT Code 
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   Optional: I Y=1 return description, if null return
 external format of CPT 
VARIABLES: DT                           TYPE: Input
 VARIABLES DESCRIPTION:   Date of service (FM format) 
COMPONENT/ENTRY POINT: $$CHKBI(X,Y)
 COMPONENT DESCRIPTION:   called to determine if batch number or invoice number
 already exists 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X= next batch/invoice number 
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   Y=1 if Batch, undefined if invoice number passed 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5092                            IA #: 5092
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAUTL5                     NAME: 5092 - FBAAUTL5 for FBCS (DSS)
  ORIGINAL NUMBER: 5089                 ID: FBAAUTL5
 GENERAL DESCRIPTION:   Access to PSA^FBAAUTL5 needed for FBCS.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$PSA(X)
 COMPONENT DESCRIPTION:   get psa from institution (File #4) 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X = ien of psa (Get PSA from institution) 
COMPONENT/ENTRY POINT: $$SUB(X)
 COMPONENT DESCRIPTION:   used to get station number and substation if one
 exists from the IFCAP software. This call is used during transmission of
 payment batches to Austin.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   
  X = "STATION NUMBER-OBLIGATION NUMBER" 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5093                            IA #: 5093
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAV01                      NAME: 5093 - FBAAV01 for FBCS(DSS)
  ORIGINAL NUMBER: 5089                 ID: FBAAV01
 GENERAL DESCRIPTION:   Access to several access points needed to support FBCS. 
 Access points: ADDRESS,NEWMSG,STORE,XMIT,PADZ,STRING 
  
 FBCS needs to be able to fire off formatted email messages to Austin.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: ADDRESS
 COMPONENT DESCRIPTION:   set up recipient array, FBXMFEE( for FEE router,
 FBXMNVP( for NVP router 
VARIABLES: VATNAME                      TYPE: Input
 VARIABLES DESCRIPTION:   "FEE" OR "NVP" VATNAME=name (.01 field) as in File
 407.7 
VARIABLES: VATERR                       TYPE: Output
 VARIABLES DESCRIPTION:   null if no error 
VARIABLES: VAT                          TYPE: Output
 VARIABLES DESCRIPTION:   VAT(1),VAT(2),...=Receiving User(s),format:
 'receiving user"@"domain mail router' 
         VAT("F")=MailMan Message Length - Fixed record 
         VAT("V")=MailMan Message Length - Variable record 
COMPONENT/ENTRY POINT: NEWMSG
 COMPONENT DESCRIPTION:   get new message number, reset line counter 
VARIABLES: FBLN                         TYPE: Both
 VARIABLES DESCRIPTION:   line counter 
VARIABLES: FBFEE                        TYPE: Both
 VARIABLES DESCRIPTION:   FEE message counter 
VARIABLES: FBNVP                        TYPE: Both
 VARIABLES DESCRIPTION:   NVP message counter 
COMPONENT/ENTRY POINT: STORE
 COMPONENT DESCRIPTION:   set message string 
VARIABLES: FBLN                         TYPE: Both
 VARIABLES DESCRIPTION:   Line number counter 
VARIABLES: FBXMZ                        TYPE: Both
 VARIABLES DESCRIPTION:   MailMan message number (IEN) 
VARIABLES: FBSTR                        TYPE: Both
 VARIABLES DESCRIPTION:   Message string 
COMPONENT/ENTRY POINT: XMIT
 COMPONENT DESCRIPTION:   send message, increment message counter 
VARIABLES: FBLN                         TYPE: Both
 VARIABLES DESCRIPTION:   Line counter 
VARIABLES: FBFEE                        TYPE: Both
 VARIABLES DESCRIPTION:   Fee message counter 
VARIABLES: FBNVP                        TYPE: Both
 VARIABLES DESCRIPTION:   NVP Message counter 
VARIABLES: FBXMFEE                      TYPE: Both
 VARIABLES DESCRIPTION:   Fee recipient array 
VARIABLES: FBXMNVP                      TYPE: Both
 VARIABLES DESCRIPTION:   NVP recipient array 
COMPONENT/ENTRY POINT: $$PADZ(X,Y)
 COMPONENT DESCRIPTION:   call to pad 'X' with leading zeros' to a field length
 of 'Y' 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   Variable to be padded with leading zeros 
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   Field length to pad 
COMPONENT/ENTRY POINT: STRING
 COMPONENT DESCRIPTION:   This call expects all variables necessary to build a
 'B3' payment record.  It calls the STORE component.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5094                            IA #: 5094
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  ROUTINE: FBAAV6                       NAME: 5094 - FBAAV6 for FBCS (DSS)
  ORIGINAL NUMBER: 5089                 ID: FBAAV6
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$AUTH(X)
 COMPONENT DESCRIPTION:   Function call to provide the Admitting Regulation.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X is equal to the internal entry number of the VA
 Admitting Reg file 
VARIABLES: FBFCR                        TYPE: Output
 VARIABLES DESCRIPTION:   an alpha dependent on the Admitting Reg chosen 
COMPONENT/ENTRY POINT: FBAAV6
 COMPONENT DESCRIPTION:   CREATE TRANSACTIONS TO SEND TO PRICER SYSTEM 
VARIABLES: J                            TYPE: Input
 VARIABLES DESCRIPTION:   Batch IEN (File 161.7) 
VARIABLES: FBAACP                       TYPE: Input
 VARIABLES DESCRIPTION:   First two characters of OBLIGATION NUMBER (#1) field
 from file 161.7 
VARIABLES: FBAAON                       TYPE: Input
 VARIABLES DESCRIPTION:   Last four characters of OBLIGATION NUMBER (#1) field
 from file 161.7 
VARIABLES: FBAASN                       TYPE: Input
 VARIABLES DESCRIPTION:   Station number, 6 characters, left justified, space
 padded The station number is obtained from IFCAP and is based on the
 obligation number of the batch 
VARIABLES: PAD                          TYPE: Input
 VARIABLES DESCRIPTION:   200 long string of spaces 
VARIABLES: FBXMNVP(                     TYPE: Input
 VARIABLES DESCRIPTION:   array of recipients for Pricer messages 
VARIABLES: FBNVP                        TYPE: Both
 VARIABLES DESCRIPTION:   counter of Pricer messages created during session 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5095                            IA #: 5095
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAVR0                      NAME: 5095 - FBAAVR0 for FBCS (DSS)
  ORIGINAL NUMBER: 5089                 ID: FBAAVR0
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: VCHNH
 COMPONENT DESCRIPTION:   Used for rejected line items 
VARIABLES: FBTYPE                       TYPE: Input
COMPONENT/ENTRY POINT: FBAAVR0
 COMPONENT DESCRIPTION:   Reject items from a batch 
VARIABLES: J                            TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN, File 162 
VARIABLES: K                            TYPE: Input
 VARIABLES DESCRIPTION:   Vendor IEN, multiple, file 162, subfile 162.01 
VARIABLES: L                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Initial Treatment date, File 162, subfile
 162.02 
VARIABLES: M                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Service Provided, file 162, subfile 162.03 
VARIABLES: FZ                           TYPE: Input
 VARIABLES DESCRIPTION:   FZ=$G(^FBAA(161.7,FBN,0)), file 161.7, zero node 
 [FBN=Batch number] 
VARIABLES: FBRR                         TYPE: Input
 VARIABLES DESCRIPTION:   Filed #5, File 162, Reject Reason 
VARIABLES: FBAARA                       TYPE: Both
 VARIABLES DESCRIPTION:   Adjustment amount (rejected item) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5096                            IA #: 5096
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBCHFA                       NAME: 5096 - FBCHFA for FBCS (DSS)
  ORIGINAL NUMBER: 5089                 ID: FBCHFA
 GENERAL DESCRIPTION:   Access to ADJLRA^FBCHFA needed to support FBCS.  and    
   FILEADJ^FBCHFA 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$ADJLRA(FBIENS)
 COMPONENT DESCRIPTION:   Adjustment Reason^Amount List Extrinsic Function 
VARIABLES: FBIENS                       TYPE: Input
 VARIABLES DESCRIPTION:   FBIENS -  required, internal entry number for file
 162.5 
COMPONENT/ENTRY POINT: FILEADJ
 COMPONENT DESCRIPTION:   
  File Adjustments for CH payment.  
VARIABLES: FBIEN                        TYPE: Both
 VARIABLES DESCRIPTION:   internal entry numbers for file 162.5 
VARIABLES: FBADJ                        TYPE: Both
 VARIABLES DESCRIPTION:   FBADJ   - required, array passed by reference 
  ;             array of adjustments to file 
  ;             array does not have to contain any data or be defined 
  ;             format 
  ;               FBADJ(#)=FBADJR^FBADJG^FBADJA 
  ;             where 
  ;               # = sequentially assigned number starting with 1 
  ;               FBADJR = adjustment reason (internal value file 162.91) 
  ;               FBADJG = adjustment group (internal value file 162.92) 
  ;               FBADJA = adjustment amount (dollar value) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5097                            IA #: 5097
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBCHREQ2                     NAME: 5097 - FBCHREQ2 for FBCS (DSS)
  ORIGINAL NUMBER: 5089                 ID: FBCHREQ2
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$NAME(DFN)
 COMPONENT DESCRIPTION:   returns patient name from file #2 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pt IEN 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5098                            IA #: 5098
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBCSV1                       NAME: 5098 - FBCSV1 for FBCS (DSS)
  ORIGINAL NUMBER: 5089                 ID: FBCSV1
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$CHKICD0(FBIEN,FBDATE)
 COMPONENT DESCRIPTION:   to use in prompts (and input templates)of file #162.5
 to screen out inactive/invalid codes 
VARIABLES: FBIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   ICD IEN 
VARIABLES: FBDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) date of service 
VARIABLES: FBICD0                       TYPE: Input
 VARIABLES DESCRIPTION:   ien of #80.1 
VARIABLES: FBINV                        TYPE: Input
 VARIABLES DESCRIPTION:   
  ien of the current #162.5 record 
VARIABLES: FBRET                        TYPE: Output
 VARIABLES DESCRIPTION:   0 if code is active, otherwise - nonzero value 
COMPONENT/ENTRY POINT: $$CHKICD9(FBIEN,FBDATE)
 COMPONENT DESCRIPTION:   checks if code is inactive on the date of service and
 if active returns CODE NUMBER 
VARIABLES: FBIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of ICD Dx 
VARIABLES: FBDATE                       TYPE: Input
COMPONENT/ENTRY POINT: $$ICD(FBIEN,FBDATE)
 COMPONENT DESCRIPTION:   wrapper for DRG^ICDGTDRG to use instead of direct
 read of ^ICD( 
VARIABLES: FBIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   FBIEN - ien of #80.1 
VARIABLES: FBDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   FBDATE - date of service (optional) 
COMPONENT/ENTRY POINT: $$ICD0(FBIEN,FBDATE)
 COMPONENT DESCRIPTION:   wrapper for ICDOP^ICDCODE to use instead of direct
 read of ^ICD0( 
VARIABLES: FBIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   FBIEN - ien of #80 
VARIABLES: FBDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   FBDATE (optional) - date of service 
COMPONENT/ENTRY POINT: $$ICD9(FBIEN,FBDATE)
 COMPONENT DESCRIPTION:   wrapper for ICDDX^ICDCODE to use instead of direct
 read of ^ICD9( 
VARIABLES: FBIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   FBIEN - ien of #80 
VARIABLES: FBDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   FBDATE (optional) - date of service 
COMPONENT/ENTRY POINT: $$ICD9EX(FBIEN,FBPC,FBEXTR,FBDATE)
 COMPONENT DESCRIPTION:   extended wrapper for ICDDX^ICDCODE to use instead of
 direct read of ^ICD9( 
VARIABLES: FBIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   FBIEN - ien of #80 
VARIABLES: FBPC                         TYPE: Input
 VARIABLES DESCRIPTION:   FBPC - piece # 
VARIABLES: FBEXTR                       TYPE: Input
 VARIABLES DESCRIPTION:   $E Parameter 
VARIABLES: FBDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   Date of service (optional) 
COMPONENT/ENTRY POINT: $$STR2FBDT(FBDTSTR)
 COMPONENT DESCRIPTION:   convert date as a string like "MMDDYYYY" into FM date
 like "YYYMMDD" 
VARIABLES: FBDTSTR                      TYPE: Both
 VARIABLES DESCRIPTION:   convert date as a string like "MMDDYYYY" into FM date
 like "YYYMMDD" 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   fm date format 
COMPONENT/ENTRY POINT: $$FRDTINV(FBDA)
 COMPONENT DESCRIPTION:   
  Returns first date found in the following order: 
    Discharge date, (from 162.3 after lookup) 
    Treatment To date, (from 162.5) 
    Treatment From date (from 162.5) 
VARIABLES: FBDA                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN to 162.5, used to find date 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5099                            IA #: 5099
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBUCUTL                      NAME: 5099 - FBUCUTL for FBCS(DSS)
  ORIGINAL NUMBER: 5099                 ID: FBUCUTL
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: LOCK(FBGL,FBDA,GO)
 COMPONENT DESCRIPTION:   lock entry before editing 
VARIABLES: FBDA                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of file (Batch) 
VARIABLES: FBGL                         TYPE: Input
 VARIABLES DESCRIPTION:   Global root 
VARIABLES: GO                           TYPE: Input
 VARIABLES DESCRIPTION:   1 to continue to try (optional) 
VARIABLES: FBLOCK                       TYPE: Output
 VARIABLES DESCRIPTION:   
  1 if successful; 0 if failed 
  incremental lock may be issued 
COMPONENT/ENTRY POINT: $$ORDER(X)
 COMPONENT DESCRIPTION:   get order number of status 
VARIABLES: X                            TYPE: Both
 VARIABLES DESCRIPTION:   X = ien of status in file 162.92, status file 
COMPONENT/ENTRY POINT: $$PAYST(FBDA,FBUCP)
 COMPONENT DESCRIPTION:   unauthorized claim payment status (released+) 
VARIABLES: FBDA                         TYPE: Input
 VARIABLES DESCRIPTION:   
  ien of unauthorized claim in 162.7 
VARIABLES: FBUPC                        TYPE: Input
 VARIABLES DESCRIPTION:   Name of array (optional) 
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   1 (true) if at least one payment and all have been
 released 0 (false) if no payments or if some have not been released if FBCUP
 contains the name of an array then that array will 
  be populated with payment information in the following format 
  array (claim ien) = result ^ number of payments 
  array (claim ien, payment file #, payment iens) = batch status 
COMPONENT/ENTRY POINT: $$PAY(X,FBGL)
 COMPONENT DESCRIPTION:   determine if any payments have been made 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of file 
VARIABLES: FBGL                         TYPE: Input
 VARIABLES DESCRIPTION:   Global root 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5100                            IA #: 5100
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBUCUTL2                     NAME: 5100 - FBUCUTL2 for FBCS (DSS)
  ORIGINAL NUMBER: 5099                 ID: FBUCUTL2
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$FBUC(X)
 COMPONENT DESCRIPTION:   unauthorized claim parameters 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of parameter 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5101                            IA #: 5101
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAUTL1                     NAME: 5101 - FBAAUTL1 for FBCS (DSS)
  ORIGINAL NUMBER: 5099                 ID: FBAAUTL1
 GENERAL DESCRIPTION:   Request access to PLUSOB^FBAAUTL1 for FBCS (DSS) 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: PLUSOB
 COMPONENT DESCRIPTION:   ENTRY POINT TO INCREASE OBLIGATION ADJUSTMENT 
VARIABLES: FBAAMT                       TYPE: Both
 VARIABLES DESCRIPTION:   Amount paid from file 162.03 - (#2) AMOUNT PAID [3N] 
VARIABLES: FBAARA                       TYPE: Input
 VARIABLES DESCRIPTION:   Amount of adjustment (if any) to the 1358.  
VARIABLES: FBAAOB                       TYPE: Input
 VARIABLES DESCRIPTION:   Obligation number (format: sta#-obligation) 
VARIABLES: FBERR                        TYPE: Output
 VARIABLES DESCRIPTION:   Error message 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5102                            IA #: 5102
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBUTL4                       NAME: 5102 - FBUTL4 for FBCS (DSS)
  ORIGINAL NUMBER: 5099                 ID: FBUTL4
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$RRL(FBRRMK)
VARIABLES: FBRRMK                       TYPE: Input
 VARIABLES DESCRIPTION:   FBRRMK(#)=FBRRMKC where # = integer number greater
 than 0 FBRRMKC = remittance remark (internal value file 162.93) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5103                            IA #: 5103
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: IBBFAPI                      NAME: 5103 - IBBFAPI for FBCS (DSS)
  ORIGINAL NUMBER: 5103                 ID: IBBFAPI
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$INSUR(DFN,IBDT,IBSTAT,IBR,IBFLDS)
 COMPONENT DESCRIPTION:   Return Patient Insurance Information 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of file #2 (Patient) 
VARIABLES: IBDT                         TYPE: Input
 VARIABLES DESCRIPTION:   Date 
VARIABLES: IBSTAT                       TYPE: Input
VARIABLES: IBR                          TYPE: Input
VARIABLES: IBFLDS                       TYPE: Input
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5104                            IA #: 5104
  FILE NUMBER: 162.4                    GLOBAL ROOT: FB7078
  DATE CREATED: JAN 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FBCS File #162.4 R/W/D
  ORIGINAL NUMBER: 5103                 ID: FB7078
 GENERAL DESCRIPTION:   FBCS performs the following accesses against the VA
 FORM 10-7078 (#162.4) file.  
      
      ^FB7078(D0,0)                     Global r ($D) 
        .01   REFERENCE NUMBER     0;1  Fileman r/w,Global r 
        1     VENDOR               0;2  Fileman r/w,Global r  
        2     VETERAN              0;3  Fileman r/w,Global r 
        3     AUTHORIZATION FROM D 0;4  Fileman r/w,Global r  
        4     AUTHORIZATION TO DAT 0;5  Fileman r/w,Global r   
        5     AUTHORITY            0;6  Fileman r/w   
        6     ESTIMATED AMOUNT     0;7  Fileman r/w  
        8     USER ENTERING        0;8  Fileman r/w,Global r   
        9     STATUS               0;9  Fileman r/w,Global r  
        10    DATE OF ISSUE        0;10 Fileman r/w  
        .5    FEE PROGRAM          0;11 Fileman r/w,Global r   
        12    REASON FOR PENDING D 0;12 Fileman r/w   
        .013  USER WHO CANCELLED   0;13 Fileman r/w   
        .014  DATE CANCELLED       0;14 Fileman r/w   
        3.5   DATE OF ADMISSION    0;15 Fileman r/w,Global r 
        4.5   DATE OF DISCHARGE    0;16 Fileman r/w   
        15    REFERRING PROVIDER   0;17 Fileman r,Global r   
      ^FB7078(D0,1,0) 
        7     AUTHORIZED SERVICES 
      ^FB7078(D0,1,D1,0) 
        .01   AUTHORIZED SERVICES  0;1  Fileman r    
      ^FB7078(D0,LOG1,D1,0) 
        .01   DATE/TIME EDITED     0;1  Fileman r 
        1     EDITED BY            0;2  Fileman r 
        2     COMMENTS             0;3  Fileman r 
  
      ^FB7078("AA")  Lookup by Program and Auth From Date 
      ^FB7078("AC")  Lookup by Status and Vendor 
      ^FB7078("AD")  Lookup by Program and Auth To Date 
      ^FB7078("D")   Lookup by patient 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
 SUBSCRIBING DETAILS:   ADDED 4/27/11 
  DATE ACTIVATED: APR 29, 2016

NUMBER: 5105                            IA #: 5105
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAACCB1                     NAME: 5105 - FBAACCB1 for FBCS (DSS)
  ORIGINAL NUMBER: 5105                 ID: FBAACCB1
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: FBCKP(J,K)
 COMPONENT DESCRIPTION:   set pharmacy check variables 
VARIABLES: K                            TYPE: Input
 VARIABLES DESCRIPTION:   DA of file 162.1 
VARIABLES: J                            TYPE: Input
 VARIABLES DESCRIPTION:   DA(1) of file 162.1 
VARIABLES: FBCKIN                       TYPE: Output
 VARIABLES DESCRIPTION:   $G(^FBAA(162.1,J,"RX",K,2)) 
VARIABLES: FBCK                         TYPE: Output
 VARIABLES DESCRIPTION:   (#30) CHECK NUMBER 
VARIABLES: FBCKDT                       TYPE: Output
 VARIABLES DESCRIPTION:   (#28) DATE PAID 
VARIABLES: FBCANDT                      TYPE: Output
 VARIABLES DESCRIPTION:   (#31) CANCELLATION DATE 
VARIABLES: FBCANR                       TYPE: Output
 VARIABLES DESCRIPTION:   (#32) REASON CODE 
VARIABLES: FBCAN                        TYPE: Output
 VARIABLES DESCRIPTION:   (#33) CANCELLATION ACTIVITY 
VARIABLES: FBDIS                        TYPE: Output
 VARIABLES DESCRIPTION:   (#34) DISBURSED AMOUNT 
VARIABLES: FBCKINT                      TYPE: Output
 VARIABLES DESCRIPTION:   (#35) INTEREST AMOUNT 
COMPONENT/ENTRY POINT: FBCKI(FBI)
 COMPONENT DESCRIPTION:   set inpatient check variables 
VARIABLES: FBI                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN (DA) 
VARIABLES: FBCKDT                       TYPE: Output
 VARIABLES DESCRIPTION:   (#.01) NUMBER, file 162.5 
VARIABLES: FBCK                         TYPE: Output
 VARIABLES DESCRIPTION:   (#3) VETERAN 
VARIABLES: FBCANDT                      TYPE: Output
 VARIABLES DESCRIPTION:   Associated 7078/583 
VARIABLES: FBCANR                       TYPE: Output
 VARIABLES DESCRIPTION:   (#5) TREATMENT FROM DATE 
VARIABLES: FBCAN                        TYPE: Output
 VARIABLES DESCRIPTION:   (#6) TREATMENT TO DATE 
VARIABLES: FBDIS                        TYPE: Output
 VARIABLES DESCRIPTION:   (#7) AMOUNT CLAIMED 
VARIABLES: FBCKINT                      TYPE: Output
 VARIABLES DESCRIPTION:   (#8) AMOUNT PAID 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5106                            IA #: 5106
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAUTL2                     NAME: 5106 - FBAAUTL2 for FBCS (DSS)
  ORIGINAL NUMBER: 5105                 ID: FBAAUTL2
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: PAT
 COMPONENT DESCRIPTION:   Get patient demographics 
VARIABLES: FBSSN                        TYPE: Output
 VARIABLES DESCRIPTION:   Social security number 
VARIABLES: Y(0)                         TYPE: Input
 VARIABLES DESCRIPTION:   ^DPT(DFN,0) node 
VARIABLES: FBSEX                        TYPE: Output
 VARIABLES DESCRIPTION:   (#.02) SEX, shortened to "M" or "F" 
VARIABLES: FBDOB                        TYPE: Output
 VARIABLES DESCRIPTION:   (#.03) DATE OF BIRTH 
VARIABLES: FBNAME                       TYPE: Output
 VARIABLES DESCRIPTION:   (#.01) NAME 
VARIABLES: FBNAM                        TYPE: Output
 VARIABLES DESCRIPTION:   CHARACTERS 1-5 of FBNAME 
VARIABLES: FBFLNAM                      TYPE: Output
 VARIABLES DESCRIPTION:   Patient's last name 
VARIABLES: FBFI                         TYPE: Output
 VARIABLES DESCRIPTION:   Patient's first name 
VARIABLES: FBMI                         TYPE: Output
 VARIABLES DESCRIPTION:   Patient's middle name 
COMPONENT/ENTRY POINT: POV
 COMPONENT DESCRIPTION:   GET POV/TREATMENT TYPE FROM 161 FOR TRANSMISSION OF
 PAYMENTS 
VARIABLES: POV(0)                       TYPE: Output
 VARIABLES DESCRIPTION:   (#3) AMOUNT SUSPENDED 
VARIABLES: J                            TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN, file 162 
VARIABLES: K                            TYPE: Input
 VARIABLES DESCRIPTION:   (#6) VENDOR, file 162, subfile 162.01 
VARIABLES: L                            TYPE: Input
 VARIABLES DESCRIPTION:   (#1) INITIAL TREATMENT DATE, file 162, subfile 162.02 
VARIABLES: M                            TYPE: Input
 VARIABLES DESCRIPTION:   (#2) SERVICE PROVIDED, file 162, subfile 162.03 
VARIABLES: POV                          TYPE: Output
 VARIABLES DESCRIPTION:   (#6) CLERK 
VARIABLES: FBTT                         TYPE: Output
 VARIABLES DESCRIPTION:   (#27) ASSOCIATED 7078/583 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5107                            IA #: 5107
  FILE NUMBER: 162                      GLOBAL ROOT: FBAAC
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS FILE 162 R/W/D             ORIGINAL NUMBER: 5105
  ID: FBAAC
 GENERAL DESCRIPTION:   The Fee Basis Claims system accesses the FEE BASIS
 PAYMENT (#162) file in order to look up and display entries and add/edit
 payments. 
  
    ^FBAAC(D0,0)                             
      .01      PATIENT              0;1      Global r,Fileman w (laygo) 
    ^FBAAC(D0,1,0)                           Global r ($D) 
      6        VENDOR 
    ^FBAAC(D0,1,D1,0) 
      .01      VENDOR               0;1      Fileman w     
    ^FBAAC(D0,1,D1,1,0)                      Global r ($D) 
      1        INITIAL TREATMENT DA 
    ^FBAAC(D0,1,D1,1,D2,0) 
      .01      INITIAL TREATMENT DA 0;1      Global r, Fileman w 
      1.5      FEE PROGRAM          0;3      Global r, Fileman w 
      3        AUTHORIZATION POINTE 0;4      Global r, Fileman w 
    ^FBAAC(D0,1,D1,1,D2,1,D3,0) 
      .01      SERVICE PROVIDED     0;1      Global r, Fileman w 
      1        AMOUNT CLAIMED       0;2      Global r, Fileman w 
      2        AMOUNT PAID          0;3      Global r, Fileman w 
      3        AMT SUSPENDED        0;4      Global r, Fileman w 
      4        SUSPEND CODE         0;5      Global r, Fileman w 
      5        DATE FINALIZED       0;6      Global r,Fileman r/w 
      6        CLERK                0;7      Global r, Fileman w 
      7        BATCH NUMBER         0;8      Global r/w, Fileman w 
      23       FEE PROGRAM          0;9      Global r, Fileman w 
      8        OBLIGATION NUMBER    0;10     Global r, Fileman w 
      3.5      DATE SUSPENDED       0;11     Fileman w 
      26       PRIMARY SERVICE FACI 0;12     Global r, Fileman w 
      27       ASSOCIATED 7078/583  0;13     Global r, Fileman w 
      13       DATE CORRECT INVLOIC 0;15     Global r, Fileman w 
      14       INVOICE NUMBER       0;16     Global r, Fileman w 
      15       patient type code    0;17     Global r, Fileman w 
      16       Purpose of visit     0;18     Global r, Fileman w 
      17       Treatment type code  0;19     Fileman w 
      18       Payment type code    0;20     Global r, Fileman w 
      24       Void payment         0;21     Global r 
      28       Primary diagnosis    0;23     Global r, Fileman w 
      29       VA type of service   0;24     Global r 
      30       PLACE OF SERVICE     0;25     Global r, Fileman w 
      31       HCFA type of service 0;26     Global r, Fileman w 
      32       Service connected co 0;27     Global r, Fileman w 
    ^FBAAC(D0,1,D1,1,D2,1,D3,1,D4,0) 
      .01      DESCRIPTION OF SUSPE 0;1      Fileman w 
    ^FBAAC(D0,1,D1,1,D2,1,D3,2) 
      33       VENDOR INVOICE DATE  2;1      Global r, Fileman w 
      34       Prompt pay type      2;2      Fileman w 
      42       SITE OF SERVICE ZIP  2;10     Fileman w 
      44       Fee schedule amount  2;13     Fileman w 
      45       Fee Schedule         2;13     Fileman w 
      47       units paid           2;14     Global r, Fileman w 
      48       Revenue Code         2;15     Fileman w 
      49       Patient account numb 2;16     Global r, Fileman w 
    ^FBAAC(D0,1,D1,1,D2,1,D3,3) 
      50       FPPS claim ID        3;1      Global r, Fileman w 
      51       FPPS line item       3;2      Global r, Fileman w 
      15.5     Authorization Ptr    3;9      Globsl r, Fileman w 
    ^FBAAC(D0,1,D1,1,D2,1,D3,7,0)            Global r ($D) 
      52       Adjustment 
    ^FBAAC(D0,1,D1,1,D2,1,D3,7,D4,0) 
      .01      Adjustment reason    0;1      Fileman r/w 
      1        Adjustment group     0;2      Fileman r/w 
      2        Adjustment Amount    0;3      Fileman r/w 
    ^FBAAC(D0,1,D1,1,D2,1,D3,8,0)            Global r 
      53       Remittance remark 
    ^FBAAC(D0,1,D1,1,D2,1,D3,8,D4,0) 
      .01      Remittance remark    0;1      Fileman r 
    ^FBAAC(D0,1,D1,1,D2,1,D3,FBREJ)          Global kill of node 
      20       Reject reason        FBREJ;2  Global r 
    ^FBAAC(D0,1,D1,1,D2,1,D3,M,0)            Global r 
      46       CPT modifier 
    ^FBAAC(D0,1,D1,1,D2,1,D3,M,D4,0) 
      .01      CPT Modifier         0;1      Fileman r 
    ^FBAAC(D0,3,D1,0) 
      2    TRAVEL AMOUNT            0;3      Global r 
      8    DATE PAID                0;6      Global r 
      9    CHECK NUMBER             0;7      Global r 
      10   CANCELLATION DATE        0;8      Global r 
      11   REASON CODE              0;9      Global r 
      12   CANCELLATION ACTIVITY    0;10     Global r 
      13   DISBURSED AMOUNT         0;11     Global r 
      14   INTEREST AMOUNT          0;12     Global r 
   
    ^FBAAC("AB")  Check for existence of record by Vendor 
                  Used to lookup by vendor IEN 
    ^FBAAC("AC")  Check for existence of record by Batch, 
                  Used for lookup by Batch, global set xref 
    ^FBAAC("AD")  Check for existence of record by Travel Batch, 
                  Used for lookup by Travel Batch 
    ^FBAAC("AE")  Used to existence of record by CPT modifier 
    ^FBAAC("AJ")  Used for lookup by original Batch, global set xref 
    ^FBAAC("AF")  Check for existence of Authorization 
    ^FBAAC("AH")  Check for existence of Batch, lookup by Batch 
                  global kill of xref for Batch 
    ^FBAAC("AM")  Check for existence of FB7078 (anc services) 
    ^FBAAC("AN")  Check for existence by Fee Program 
    ^FBAAC("C")   Check for existence by Invoice Number 
    ^FBAAC(D2,D1,"AD")  Check for existence of prior claims 
    ^FBAAC(D2,"AB")     Used to lookup by Treatment date 
    ^FBAAC(D1,3,"AB")   Check existence of data, 
                        loop to get entries by Travel Payment Dt 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: APR 29, 2016

NUMBER: 5108                            IA #: 5108
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAV1                       NAME: FBAAV1 for FBCS (DSS)
  ORIGINAL NUMBER: 5105                 ID: FBAAV1
 GENERAL DESCRIPTION:   Access need to ^FBAAV1 needed for FBCS 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: KILL
 COMPONENT DESCRIPTION:   Used to kill existing local variables used in Fee
 Basis 
COMPONENT/ENTRY POINT: FBAAV1
 COMPONENT DESCRIPTION:   ELECTRONICALLY TRANSMIT FEE (VENDOR MRA'S) PART 2 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5109                            IA #: 5109
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAV3                       NAME: FBAAV3 for FBCS (DSS)
  ORIGINAL NUMBER: 5105                 ID: FBAAV3
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$AUSDT(FBDT)
 COMPONENT DESCRIPTION:   called to format date from VA FileMan internal to
 YYYYMMDD 
VARIABLES: FBDT                         TYPE: Input
 VARIABLES DESCRIPTION:   FM Date 
VARIABLES: FBRET                        TYPE: Output
 VARIABLES DESCRIPTION:   HL7 formatted date 
COMPONENT/ENTRY POINT: $$AUSAMT(FBAMT,FBL,FBS) 
 COMPONENT DESCRIPTION:   
  called to format signed dollar amount for Austin 
VARIABLES: FBAMT                        TYPE: Input
 VARIABLES DESCRIPTION:   Dollar amount 
VARIABLES: FBL                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional) length of return sting 
VARIABLES: FBS                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional) =true(1) if return value could be negative
 (-) default is false (0) 
COMPONENT/ENTRY POINT: DETT
 COMPONENT DESCRIPTION:   Process a Travel Batch 
VARIABLES: J                            TYPE: Input
 VARIABLES DESCRIPTION:   Travel Batch IEN# 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5110                            IA #: 5110
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAV4                       NAME: FBAAV4 for FBCS (DSS)
  ORIGINAL NUMBER: 5105                 ID: FBAAV4
 GENERAL DESCRIPTION:   Access to HL7NAME^FBAAV4 and ^FBAAV4 needed for FBCS 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$HL7NAME(FBDFN) 
 COMPONENT DESCRIPTION:   parse name components HL7 format 
VARIABLES: FBDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: FBNM                         TYPE: Output
 VARIABLES DESCRIPTION:   lastname|firstname 
COMPONENT/ENTRY POINT: FBAAV4
 COMPONENT DESCRIPTION:   Electronically transmit Patient MRAs Loops through
 Pending entries in the FEE BASIS PATIENT MRA (#161.26) file, prepares and
 transmits data.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5111                            IA #: 5111
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FBAAV5
  NAME: FBAAV5 for FBCS (DSS)           ORIGINAL NUMBER: 5105
  ID: FBAAV5                            STATUS: Retired
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$PSA(X,Y)
 COMPONENT DESCRIPTION:   call to set default Primary Service Area (PSA) for
 Austin transmissions call returns the 3 digit station number only 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   pointer to the institution file 
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   default if unable to determine station number in file
 4 
COMPONENT/ENTRY POINT: DETCH
 COMPONENT DESCRIPTION:   Transmit B9 payment batch message to Central Fee 
VARIABLES: J                            TYPE: Input
 VARIABLES DESCRIPTION:   Batch IEN, (file 161.7) 
VARIABLES: FBSTR                        TYPE: Input
 VARIABLES DESCRIPTION:   string containing the payment batch header line 
VARIABLES: FBAAON                       TYPE: Input
 VARIABLES DESCRIPTION:   Last four characters of OBLIGATION NUMBER (#1) field
 from file 161.7 
VARIABLES: FBAASN                       TYPE: Input
 VARIABLES DESCRIPTION:   Station number, 6 characters, left justified, space
 padded The station number is obtained from IFCAP and is based on the
 obligation number of the batch 
VARIABLES: PAD                          TYPE: Input
 VARIABLES DESCRIPTION:   200 long string of spaces 
VARIABLES: FBXMFEE(                     TYPE: Input
 VARIABLES DESCRIPTION:   array of recipients for Central Fee messages 
VARIABLES: FBFEE                        TYPE: Both
 VARIABLES DESCRIPTION:   counter of Central Fee messages created during
 session 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5112                            IA #: 5112
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAASCB                      NAME: FBAASCB for FBCS (DSS)
  ORIGINAL NUMBER: 5105                 ID: FBAASCB
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: POST
 COMPONENT DESCRIPTION:   Post a transaction to the 1358 
VARIABLES: FBAAOB                       TYPE: Input
 VARIABLES DESCRIPTION:   FFULL OBLIGATION NUMBER(STA-CXXXXX) 
VARIABLES: FBCOMM                       TYPE: Input
 VARIABLES DESCRIPTION:   COMMENT FOR 1358 
VARIABLES: FBAAMT                       TYPE: Input
 VARIABLES DESCRIPTION:   TOTAL AMOUNT OF BATCH 
VARIABLES: FBAAB                        TYPE: Input
 VARIABLES DESCRIPTION:   BATCH NUMBER 
VARIABLES: FBERR                        TYPE: Output
 VARIABLES DESCRIPTION:   IF CALL FAILS FBERR RETURNED=1 
VARIABLES: FBN                          TYPE: Output
 VARIABLES DESCRIPTION:   FBN added as 7th piece of 'X'. It is the interface ID 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5113                            IA #: 5113
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBNHEXP                      NAME: FBNHEXP for FBCS (DSS)
  ORIGINAL NUMBER: 5105                 ID: FBNHEXP
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$VNAME(X)
 COMPONENT DESCRIPTION:   Vendor Lookup 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   Vendor IEN 
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   Vendor Name or "Unknown" 
COMPONENT/ENTRY POINT: $$VID(X)
 COMPONENT DESCRIPTION:   Returns Vendor ID 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   Vendor IEN 
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   Vendor ID or "Unknown" 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5114                            IA #: 5114
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBMRASVR                     NAME: FBMRASVR for FBCS (DSS)
  ORIGINAL NUMBER: 5105                 ID: FBMRASVR
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$EXTRL(V,T)
 COMPONENT DESCRIPTION:   Calls to remove leading/trailing spaces and zeros 
VARIABLES: V                            TYPE: Input
 VARIABLES DESCRIPTION:   variable to be parsed 
VARIABLES: T                            TYPE: Input
 VARIABLES DESCRIPTION:   1 remove leading zeros, T="" remove leading spaces 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5115                            IA #: 5115
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBPAY2                       NAME: FBPAY2 for FBCS (DSS)
  ORIGINAL NUMBER: 5115                 ID: FBPAY2
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   entry point to set variables, called by fbpay67, oth
 & anc 
VARIABLES: J                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of patient from file 162 
VARIABLES: K                            TYPE: Input
 VARIABLES DESCRIPTION:   (#6) VENDOR, FILE 162, SUBFILE 162.01 
VARIABLES: L                            TYPE: Input
 VARIABLES DESCRIPTION:   (#1) INITIAL TREATMENT DATE, file 162, subfile 162.02 
VARIABLES: M                            TYPE: Input
 VARIABLES DESCRIPTION:   (#2) SERVICE PROVIDED, file 162, subfile 162.03 
VARIABLES: FBDT                         TYPE: Output
 VARIABLES DESCRIPTION:   DATE CONVERTER,FM date to "10/11/08" format 
VARIABLES: D                            TYPE: Output
 VARIABLES DESCRIPTION:   Date of service 
COMPONENT/ENTRY POINT: KILL
 COMPONENT DESCRIPTION:   kill variables, due to the large number available not
 all are listed here.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5116                            IA #: 5116
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBPAY21                      NAME: FBPAY21 for FBCS (DSS)
  ORIGINAL NUMBER: 5115                 ID: FBPAY21
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   entry from fbpay67 to set '*' if ancillary payment is
 a reimbursement.  returns FBRP=to '*' or " " 'Y' passed in equal to zero node
 of 162.03 look at $P(Y,U,20) 
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   equal to zero node of 162.03 look at $P(Y,U,20) 
VARIABLES: FBR                          TYPE: Output
 VARIABLES DESCRIPTION:   
  '*' or " " or (#18) PAYMENT TYPE CODE 
COMPONENT/ENTRY POINT: EFBCK(FBCKIN)
 COMPONENT DESCRIPTION:   extract check information from ^TMP 
  
 Not currently used by FBCS 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5117                            IA #: 5117
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBPAY67                      NAME: FBPAY67 for FBCS (DSS)
  ORIGINAL NUMBER: 5115                 ID: FBPAY67
 GENERAL DESCRIPTION:   These components are part of the fee basis payment
 listing reports and were not designed to be called by other applications. 
 They may leak many variables.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: AN
 COMPONENT DESCRIPTION:   Get ancillary payment data for a specific veteran or
 vendor for either the civil hospital or community nursing home fee program
 using the "AN  x-ref in File 162 
VARIABLES: FBVNAME                      TYPE: Input
 VARIABLES DESCRIPTION:   Vendor Name (only needed when FBSORT = 0) 
VARIABLES: FBVID                        TYPE: Input
 VARIABLES DESCRIPTION:   Vendor ID (only needed when FBSORT = 1) 
VARIABLES: FBVCHAIN                     TYPE: Input
 VARIABLES DESCRIPTION:   (#10) CLINIC AFFILIATION, from file 161.2 
VARIABLES: FBDOB                        TYPE: Input
 VARIABLES DESCRIPTION:   Patients date of birth 
VARIABLES: DFN                          TYPE: Both
 VARIABLES DESCRIPTION:   Veteran IEN (only needed when FBSORT = 1) 
VARIABLES: FBPAT                        TYPE: Output
 VARIABLES DESCRIPTION:   PATIENT NAME 
VARIABLES: FBPNAME                      TYPE: Input
 VARIABLES DESCRIPTION:   Veteran Name (only needed when FBSORT = 1) 
VARIABLES: FBPID                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient SSN (example XXX-XX-1234, only needed when
 FBSORT = 1) 
VARIABLES: FBPI                         TYPE: Input
 VARIABLES DESCRIPTION:   Fee Program, value = 6 for civil hospital or 7 for
 community nursing home 
VARIABLES: FBBDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   Beginning date in FileMan internal format 
VARIABLES: FBEDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   Ending date in FileMan internal format 
VARIABLES: FBSORT                       TYPE: Input
 VARIABLES DESCRIPTION:   Value is 0 or 1, payment listing for vendor (=0) or
 veteran (=1) 
VARIABLES: FBVI                         TYPE: Input
 VARIABLES DESCRIPTION:   Vendor IEN (only needed when FBSORT = 0) 
VARIABLES: TMP($J,FB,                   TYPE: Output
 VARIABLES DESCRIPTION:   Global of ancillary payment data that meets the input
 criterion 
  
                            Format 
                            
 ^TMP($J,"FB",FBPI_"O",FBVEN,FBPAT,(9999999.9999-FBDT1),L,M) = 
 $G(FBR)_$$DATX^FBAAUTL(FBDT1)_U_FBAACPTC_FBCP_$S($G(FBMODLE)]"":"-"_FBMODL 
 E,1:"")_U_ A1_U_A2_U_T_U_FBBN_U_FBIN_U_D2_U_FBSC_U_FBPDX_U_FBOB 
  
                            
 ^TMP($J,"FB",FBPI_"O",FBVEN,FBPAT,(9999999.9999-FBDT1),L,M,"FBCK") = 
 "^"_FBCK_"^"_FBCKDT_"^"_FBCANDT_"^"_FBCANR_"^"_FBCAN_"^"_FBDIS_"^"_FBCKINT 
  
                            
 ^TMP($J,"FB",FBPI_"O",FBVEN,FBPAT,(9999999.9999-FBDT1),L,M,"FBADJ") = 
 TAMT_U_FBUNITS_U_FBADJLR_U_FBADJLA_U_FBRRMKL_U_FBCSID_U_FBFPPSC_U_FBFPPSL_ 
 U_FBAARCE 
COMPONENT/ENTRY POINT: OTH
 COMPONENT DESCRIPTION:   Get ancillary payment data for a specific vendor and
 veteran during a specified period and fee program 
VARIABLES: FBPI                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Fee Program 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: FBVI                         TYPE: Input
 VARIABLES DESCRIPTION:   Vendor IEN 
VARIABLES: FBDT1                        TYPE: Output
 VARIABLES DESCRIPTION:   Date of service 
VARIABLES: FBBDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   Beginning Date in FileMan internal format 
VARIABLES: FBEDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   Ending Date in FileMan internal format 
VARIABLES: FBPAT                        TYPE: Input
 VARIABLES DESCRIPTION:   Veteran Name : Veteran ID (used for sorting) 
VARIABLES: FBVEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Vendor Name ; Vendor ID (used for sorting) 
VARIABLES: TMP($J,FB                    TYPE: Output
 VARIABLES DESCRIPTION:   Global of ancillary payment data that meets the input
 criterion. Same output as AN component 
COMPONENT/ENTRY POINT: ANC
 COMPONENT DESCRIPTION:   Get ancillary payment data for a specific vendor and
 veteran during a specified period and fee program 
VARIABLES: FBM                          TYPE: Input
 VARIABLES DESCRIPTION:   Date 
VARIABLES: FBI                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN to file 162.5 
VARIABLES: FBIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Either a pointer to the VETERAN or the VENDOR 
VARIABLES: FBIN(5)                      TYPE: Input
 VARIABLES DESCRIPTION:   ASSOCIATED 7078/583 
VARIABLES: TMP($J,FB                    TYPE: Output
 VARIABLES DESCRIPTION:   Global of ancillary payment data 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5118                            IA #: 5118
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBRXFA                       NAME: FBRXFA for FBCS (DSS)
  ORIGINAL NUMBER: 5115                 ID: FBRXFA
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$ADJLRA(FBIENS)
 COMPONENT DESCRIPTION:   Adjustment Reason^Amount List Extrinsic Function 
VARIABLES: FBIENS                       TYPE: Input
 VARIABLES DESCRIPTION:   required, internal entry numbers for subfile 162.11 
VARIABLES: FBRET                        TYPE: Output
 VARIABLES DESCRIPTION:   string containing sorted list (by external code) of
 reason^amounts 
  format 
        FBADJE 1, FBADJE 2^FBADJA 1,FBADJA2 
     where 
        FBADJE = adjustment reason code (external value) 
        FBADJA = adjustment amount 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5119                            IA #: 5119
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBRXFR                       NAME: FBRXFR for FBCS (DSS)
  ORIGINAL NUMBER: 5115                 ID: FBRXFR
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$RRL(FBIENS)
 COMPONENT DESCRIPTION:   Remittance Remarks List Extrinsic Function 
VARIABLES: L                            TYPE: Input
VARIABLES: FBIENS                       TYPE: Input
 VARIABLES DESCRIPTION:   required, internal entry numbers for subfile 162.11 
VARIABLES: FBRET                        TYPE: Output
 VARIABLES DESCRIPTION:   string containing sorted list (by external code) of
 remarks 
   format 
        FBRRMKCE 1, FBRRMKCE 2 
     where 
        FBRRMKCE = remittance remark code (external value) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5120                            IA #: 5120
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBUTL2                       NAME: FBUTL2 for FBCS (DSS)
  ORIGINAL NUMBER: 5115                 ID: FBUTL2
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$ADJL(FBADJ)
 COMPONENT DESCRIPTION:   build list of adjustments extrinsic function 
VARIABLES: FBADJ                        TYPE: Input
 VARIABLES DESCRIPTION:   required, array passed by reference 
  
 FBADJ(#)=FBADJR^FBADJG^FBADJA 
  ;              FBADJR = adjustment reason (internal value file 162.91) 
  ;              FBADJG = adjustment group (inernal value file 162.92) 
  ;              FBADJA = adjustment amount (dollar value) 
VARIABLES: FBRET                        TYPE: Output
 VARIABLES DESCRIPTION:   string containing sorted list (by external reason) of
 adjustments 
     format 
        FBADJRE 1^FBADJGE 1^FBADJAE 1^FBADJRE 2^FBADJGE 2^FBADJAE 2 
     where 
       FBADJRE = adjustment reason (external value) 
       FBADJGE = adjustment group (external value) 
       FBADJAE = adjustment amount (with cents) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5121                            IA #: 5121
  DATE CREATED: JAN 13, 2011
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MPIF001
  NAME: $$SETICN MPIF001                ID: MPIF001
 GENERAL DESCRIPTION:   This function updates the Integration Control Number
 (#991.01) and the ICN Checksum (#991.02) fields in the Patient (#2) file on
 the MPI node.  This is being provided for use by the North Chicago FEDERAL
 HEALTH CARE CENTER developers.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
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).    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: ICN                          TYPE: Input
 VARIABLES DESCRIPTION:   ICN - ICN (without checksum) to be updated.  
VARIABLES: CHKSUM                       TYPE: Input
 VARIABLES DESCRIPTION:   CHKSUM - ICN checksum to be updated.  
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
  DATE ACTIVATED: JAN 14, 2011

NUMBER: 5122                            IA #: 5122
  FILE NUMBER: 70                       GLOBAL ROOT: DD(70.15
  DATE CREATED: FEB 07, 2008            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: Remove Rad/Nuc Med dd Screen of Sub field #70.15
  ID: DD(70.15
 GENERAL DESCRIPTION:   The Radiology/Nuclear Medicine intends to remove the
 following Data Dictionary: 
  
   K ^DD(70.15,.01,12) 
   K ^DD(70.15,.01,12.1) 
   
 This correction will eliminate the a DIC("S") screen for a drug.  Instead of a
 direct global read to the Pharmacy file #50, an API provided by Pharmacy will
 be used to check or access a drug.  
  
 This will be a one-time IA with the installation of patch RA*5.0*65.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 5123                            IA #: 5123
  FILE NUMBER: 70                       GLOBAL ROOT: DD(70.21
  DATE CREATED: FEB 08, 2008            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: Remove Rad/Nuc Med dd Screen of Sub field #70.21
  ID: DD(70.21
 GENERAL DESCRIPTION:   The Radiology/Nuclear Medicine intends to remove the
 following Data Dictionary: 
  
   K ^DD(70.21,.01,12) 
   K ^DD(70.21,.01,12.1) 
  
 This correction will eliminate the a DIC("S") screen for a drug.  Instead of a
 direct global read to the Pharmacy file #50, an API provided by Pharmacy will
 be used to check or access a drug.  
  
 This will be a one-time IA with the installation of patch RA*5.0*65.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 5124                            IA #: 5124
  FILE NUMBER: 71                       GLOBAL ROOT: DD(71.055
  DATE CREATED: FEB 08, 2008            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: Remove Rad/Nuc Med dd Screen of Sub field #71.055
  ID: DD(71.055
 GENERAL DESCRIPTION:   The Radiology/Nuclear Medicine intends to remove the
 following Data Dictionary:            
  
  
   K ^DD(71.055,.01,12) 
   K ^DD(71.055,.01,12.1) 
  
 This correction will eliminate the a DIC("S") screen for a drug.  Instead of a
 direct global read to the Pharmacy file #50, an API provided by Pharmacy will
 be used to check or access a drug.  
  
 This will be a one-time IA with the installation of patch RA*5.0*65.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 5125                            IA #: 5125
  FILE NUMBER: 71                       GLOBAL ROOT: DD(71.08
  DATE CREATED: FEB 08, 2008            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: Remove Rad/Nuc Med dd Screen of Sub field #71.08
  ID: DD(71.08
 GENERAL DESCRIPTION:   The Radiology/Nuclear Medicine intends to remove the
 following Data Dictionary:            
  
  K ^DD(71.08,.01,12) 
  K ^DD(71.08,.01,12.1) 
  
 This correction will eliminate the a DIC("S") screen for a drug.  Instead of a
 direct global read to the Pharmacy file #50, an API provided by Pharmacy will
 be used to check or access a drug.  
  
 This will be a one-time IA with the installation of patch RA*5.0*65.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 5126                            IA #: 5126
  FILE NUMBER: 71.9                     GLOBAL ROOT: DD(71.9
  DATE CREATED: FEB 08, 2008            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: Remove Rad/Nuc Med dd Screen of File 71.9 field #5
  ID: DD(71.9
 GENERAL DESCRIPTION:   The Radiology/Nuclear Medicine intends to remove the
 following Data Dictionary: 
                                                        
  K ^DD(71.9,5,12) 
  K ^DD(71.9,5,12.1) 
  
 This correction will eliminate the a DIC("S") screen for a drug.  Instead of a
 direct global read to the Pharmacy file #50, an API provided by Pharmacy will
 be used to check or access a drug.  
  
 This will be a one-time IA with the installation of patch RA*5.0*65.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 5127                            IA #: 5127
  FILE NUMBER: 71.9                     GLOBAL ROOT: DD(71.9
  DATE CREATED: FEB 08, 2008            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: Set Rad/Nuc Med data dictionary 'ID','WRIT
  ID: DD(71.9
 GENERAL DESCRIPTION:   Radiology/Nuclear Medicine intends to modify the
 following data dictionary attribute: 
   
  K ^DD(71.9,0,"ID",5) 
  S ^DD(71.9,0,"ID","WRITE")="D EN^DDIOL($$EN5^RAPSAPI,"""",""?30"")" 
  
 Instead of a direct global read to the Pharmacy file #50, an API provided by
 Pharmacy will be used to check or access a drug.  
  
  
 This will be a one-time IA with the installation of patch RA*5.0*65.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 5128                            IA #: 5128
  FILE NUMBER: 70.15                    GLOBAL ROOT: DD(70.15
  DATE CREATED: FEB 08, 2008            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: MY PRIVATE                      ID: DD(70.15
  STATUS: Pending
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 5129                            IA #: 5129
  DATE CREATED: FEB 11, 2008
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIULMED
  NAME: CALL TO ROUTINE TIULMED         ID: TIULMED
 GENERAL DESCRIPTION:   Medicaion reconciliation has need for the data returned
 by the entry LIST^TIULMED.  Outpatiient pharmact requests permission to make
 thatcall.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LIST
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: FEB 11, 2008

NUMBER: 5130                            IA #: 5130
  DATE CREATED: JAN 19, 2011            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGROHLS                      NAME: DBIA-5130
  ID: DGROHLS
 GENERAL DESCRIPTION:   An API is needed that sends a request for Patient Data
 from the Last Site Treated.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SNDQRY
 COMPONENT DESCRIPTION:   SNDQRY^DGROHLS is passed a DFN from the local Patient
 File. The Patient record must have a National ICN and the Last Site Treated
 (LST) must not be the local site. An HL7 message, QRY-R02, is sent to the Last
 Site Treated and data is passed back and filed into the Patient Record.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN: the ien of the Patient File for the patient.  
VARIABLES: DGRSLT                       TYPE: Output
 VARIABLES DESCRIPTION:   DGRSLT: 1 on success ; 0 on failure 
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   A DFN from the local site is sent to the API:
 SNDQRY^DGROHLS(DFN). The query returns a value: 1 on success ; 0 on failure.  

NUMBER: 5131                            IA #: 5131
  FILE NUMBER: 355.93                   GLOBAL ROOT: DD(355.93,0,'ID'
  DATE CREATED: FEB 12, 2008            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IB REMOVE IDENTIFIER DESIGNATION
  ID: DD(355.93,0,'ID'
GLOBAL REFERENCE: DD(355.93,0,'ID',.09)
FIELD NUMBER: .09                       FIELD NAME: FACILITY DEFAULT ID NUMBER
  LOCATION: 0;9                         ACCESS: Direct Global Write & w/Fileman
 GENERAL DESCRIPTION:   Integrating Billing (IB) needs to remove the IDENTIFIER
 label from the .09 field (FACILITY DEFAULT ID NUMBER) in file 355.93 (IB
 NON/OTHER VA BILLING PROVIDER).  This field is not an identifier for this file
 because this field is only valid for non-VA facilities.  The .09 field is not 
 available for non-VA individual providers.  
  
 This integration agreement exists so we can KILL ^DD(355.93,0,"ID",.09) with
 IB patch IB*2.0*377.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IDENTIFIER
KEYWORDS: 355.93
KEYWORDS: ID
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAR 06, 2008

NUMBER: 5132                            IA #: 5132
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: FEB 12, 2008            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PATIENT FILE-GUARDIAN DATA
  ID: DPT(
GLOBAL REFERENCE: DPT(IEN,.29
FIELD NUMBER: .291                      FIELD NAME: DATE RULED INCOMPETENT
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE DATE THE PATIENT WAS RULED TO BE INCOMPETANT TO
 HANDLE HIS VA FUNDS 
FIELD NUMBER: .2912                     FIELD NAME: GUARDIAN (VA)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE NAME OF THE VA REPRESENTATIVE RESPONSIBLE FOR THIS
 PATIENT'S FUNDS 
FIELD NUMBER: .2914                     FIELD NAME: STREET ADDRESS 1 (VA)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE FIRST LINE OF THE STREET ADDRESS FO THE VA
 REPRESENTATIVE RESPONSIBLE FOR HANDLING THIS PATIENT'S FUNDS 
FIELD NUMBER: .2915                     FIELD NAME: STREET ADDRESS 2 (VA)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE SECOND LINE OF THE STREET ADDRESS OF THE VA
 REPRESENTATIVE RESPONSIBL FOR HANDLING THIS PATIENT'S FUNDS 
FIELD NUMBER: .2916                     FIELD NAME: CITY (VA)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE CITY IN WHICH THE PERSON RESPONSIBLE FOR HANDLING
 THIS PATIENT'S FUNDS RESIDES 
FIELD NUMBER: .2917                     FIELD NAME: STATE (VA)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE STATE IN WHICH THE PERSON RESPONSIBLE FOR HANDLING
 THIS PATIENT'S FUNDS RESIDES 
FIELD NUMBER: .2918                     FIELD NAME: ZIP (VA)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE ZIP CODE AT WHICH THE PERSON RESPONSIBLE FOR HANDLING
 THIS PATIENT'S FUNDS RESIDES 
FIELD NUMBER: .2919                     FIELD NAME: PHONE (VA)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE PHONE NUMBER OF THE PERSON RESPONSIBLE FOR HANDLING
 THIS PATIENT'S FUNDS 
FIELD NUMBER: .292
  FIELD NAME: DATE RULED INCOMPETENT (CIVIL)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE DATE THAT THE PATIENT WAS RULED INCOMPETENT TO HANDLE
 HIS FUNDS 
GLOBAL REFERENCE: DPT(IEN,.291
FIELD NUMBER: .2922                     FIELD NAME: GUARDIAN (CIVIL)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   IF THE PATIENT HAS BEEN RULED INCOMPETENT TO HANDLE HIS
 FINANCIAL MATTERS, THIS INDIVIDUAL IS RESPONSIBLE FOR HANDLING THE FUNDS ON
 THE PATIENT'S BEHALF 
FIELD NUMBER: .2923                     FIELD NAME: RELATIONSHIP (CIVIL)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   IF THE PATIENT HAS BEEN RULED INCOMPETENT, THIS IS THE
 RELAITONSHIP TO THE PATIENT OF THE PERSON THAT IS RESPONSIBLE FOR HANDLING THE
 PATIENT'S FUNDS 
FIELD NUMBER: .2924                     FIELD NAME: STREET ADDRESS 1 (CIVIL)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE FIRST LINE OF THE STREET ADDRESS OF THE PERSON
 RESPONSIBLE FOR HANDLING THIS PATIENT'S FUNDS 
FIELD NUMBER: .2925                     FIELD NAME: STREET ADDRESS 2 (CIVIL)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE SECOND LINE OF THE STREET ADDRESS OF THE PERSON
 RESPONSIBLE FOR HANDLING THIS PATIENT'S FUNDS 
FIELD NUMBER: .2926                     FIELD NAME: CITY (CIVIL)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE CITY IN WHICH THE PERSON RESPONSIBLE FOR THIS
 PATIENT'S FUNDS RESIDES.  
FIELD NUMBER: .2927                     FIELD NAME: STATE (CIVIL)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE STATE IN WHICH THE PERSON RESPONSIBLE FOR HANDLING
 THIS PATIENT'S FUNDS RESIDES 
FIELD NUMBER: .2928                     FIELD NAME: ZIP (CIVIL)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE ZIP CODE OF THE ADDRESS WHERE THE PERSON RESPONSIBLE
 FOR HANDLING THIS PATIENT'S FUNDS RESIDES.  
FIELD NUMBER: .2929                     FIELD NAME: PHONE (CIVIL)
  ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   THE PHONE NUMBER OF THE PERSON RESPONSIBLE FOR HANDLING
 THIS PATIENT'S FUNDS 
 GENERAL DESCRIPTION:   THE PATIENT FUNDS PACKAGE (PRPF) CONTAINS AN OPTION
 THAT ALLOWS EDITING OF GUARDIAN INFORMATION IN THE PATIENT FILE. THESE FIELDS
 ARE NOT AVAILABLE FOR EDITING IN ANY REGISTRATION OPTION.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GUARDIAN
SUBSCRIBING PACKAGE: INTEGRATED PATIENT FUNDS
 SUBSCRIBING DETAILS:   PATIENT FUNDS HAS AN OPTION [PRPF GUARDIAN EDIT] THAT
 ALLOWS EDITING OF GUARDIAN INFORMATION IN THE PATIENT FILE.  
  DATE ACTIVATED: MAR 07, 2008

NUMBER: 5133                            IA #: 5133
  FILE NUMBER: 801.41                   GLOBAL ROOT: PXRMD(801.41,
  DATE CREATED: FEB 14, 2008            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ OF THE FINDING ITEM AND ADDITIONAL FINDINGS FIELDS
  ID: PXRMD(801.41,
GLOBAL REFERENCE: PXRMD(801.41,D0,1)
FIELD NUMBER: 15                        FIELD NAME: FINDING ITEM
  LOCATION: 1;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field store a variable pointer to store the item
 that should be created in CPRS.  
  
GLOBAL REFERENCE: PXRMD(801.41,D0,3,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ADDITIONAL FINDINGS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field stored additional items that should be process
 in CPRS when the item is checked.  
  
GLOBAL REFERENCE: PXRMD(801.41,TYPE,X,D0)
 GLOBAL DESCRIPTION:   This is a cross-reference on the TYPE field. This allows
 the package to quickly finding dialog entries that may have the finding item
 and the additional findings fields populated.  
  
 GENERAL DESCRIPTION:   This IA allows a package to do a direct read on the
 Finding Items field and the Additional Finding Items multiple in file 801.41.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: REMINDER DIALOGS
KEYWORDS: PXRMD(801.41,
KEYWORDS: ORDER DIALOGS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: FEB 14, 2008

NUMBER: 5134                            IA #: 5134
  DATE CREATED: FEB 19, 2008
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORQ12                        NAME: ORQ12
  ID: ORQ12                             STATUS: Pending
KEYWORDS: ORQ12
COMPONENT/ENTRY POINT: ACTION
 COMPONENT DESCRIPTION:   Returns text of action X 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   The action to find the text for 
VARIABLES: $$ACTION                     TYPE: Output
 VARIABLES DESCRIPTION:   The text of the action X 
COMPONENT/ENTRY POINT: DATETIME
 COMPONENT DESCRIPTION:   Returns date/time in format 00/00/00@00:00am 
VARIABLES: $$DATETIME                   TYPE: Output
 VARIABLES DESCRIPTION:   The date/time in format 00/00/00@00:00am 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   The input time in Fileman DT 
COMPONENT/ENTRY POINT: LASTTXT
 COMPONENT DESCRIPTION:   Returns action with latest text for order IFN 
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   file 100 IEN 
VARIABLES: $$LASTTXT                    TYPE: Output
 VARIABLES DESCRIPTION:   The text of the latest action for order IFN 
COMPONENT/ENTRY POINT: NAME
 COMPONENT DESCRIPTION:   Returns name as Lname,F 
VARIABLES: $$NAME                       TYPE: Output
 VARIABLES DESCRIPTION:   return variable as a text output in format
 "Lname,Finitial" 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   File 200 IEN 
COMPONENT/ENTRY POINT: ADD
 COMPONENT DESCRIPTION:   Add text X to ORTX() 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   String containing the text to add to the output
 ORTX() array 
VARIABLES: ORTX                         TYPE: Output
 VARIABLES DESCRIPTION:   The array that the string X gets added to for return. 
 
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL

NUMBER: 5135                            IA #: 5135
  DATE CREATED: FEB 19, 2008
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORQOR2                       NAME: ORQOR2
  ID: ORQOR2                            STATUS: Pending
KEYWORDS: ORQOR2
COMPONENT/ENTRY POINT: OI
 COMPONENT DESCRIPTION:   ext. funct. gets Orderable Item ien from ORDER File
 (#100) 
VARIABLES: $$OI                         TYPE: Output
 VARIABLES DESCRIPTION:   Return variable that contains the Orderable Item IEN
 (file 101.43) 
VARIABLES: ORNUM                        TYPE: Input
 VARIABLES DESCRIPTION:   File 100 IEN 
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL

NUMBER: 5136                            IA #: 5136
  DATE CREATED: FEB 19, 2008
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORQPTQ1                      NAME: ORQPTQ1
  ID: ORQPTQ1                           STATUS: Pending
KEYWORDS: ORQPTQ1
COMPONENT/ENTRY POINT: DEFTM
 COMPONENT DESCRIPTION:   return current user's default team list 
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   Return variable containing a OE/RR List IEN (file
 100.21) 
COMPONENT/ENTRY POINT: PERSPR
 COMPONENT DESCRIPTION:   return list of personal lists linked to current user 
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   A return array that contains a list of personal lists
 for the current user in the form: 
         IEN^List Name 
  
 Where IEN is the file 100.21 IEN 
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL

NUMBER: 5137                            IA #: 5137
  DATE CREATED: FEB 19, 2008
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORQPTQ11
  NAME: ORQPTQ11                        ID: ORQPTQ11
  STATUS: Active
KEYWORDS: ORQPTQ11
COMPONENT/ENTRY POINT: DEFSRC
 COMPONENT DESCRIPTION:   return current user's default list source 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   returns the current user's default list source in the
 following form: 
         IEN^List Name^List Type 
  
 Where List Type is the place that the list comes from (Team, Ward, Primary
 Provider, Specialty, Combination) IEN is the pointer to the list List Name is
 the name for the list 
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
  DATE ACTIVATED: MAR 23, 2016

NUMBER: 5138                            IA #: 5138
  DATE CREATED: FEB 19, 2008
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORWLRR                       NAME: ORWLRR
  ID: ORWLRR                            STATUS: Pending
KEYWORDS: ORWLRR
COMPONENT/ENTRY POINT: INTERIMG
 COMPONENT DESCRIPTION:   get patient info, and expand LAB tests 
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   Return variable containing lab tests 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   PATIENT IEN from file 2 
VARIABLES: DATE1                        TYPE: Input
 VARIABLES DESCRIPTION:   Start date to look for tests 
VARIABLES: DIR                          TYPE: Input
 VARIABLES DESCRIPTION:   Direction to go from DATE1 in looking for tests 
VARIABLES: FORMAT                       TYPE: Input
 VARIABLES DESCRIPTION:   Specifies what Format to put the result array into.  
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL

NUMBER: 5139                            IA #: 5139
  DATE CREATED: FEB 19, 2008            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  ROUTINE: XUSER                        NAME: XUSER
  ID: XUSER                             STATUS: Pending
KEYWORDS: XUSER
COMPONENT/ENTRY POINT: DIV4
 COMPONENT DESCRIPTION:   Return the Divisions that this user is assigned to.  
 Returns 0 - no institution for user, 1 - institution for user 
VARIABLES: XUROOT                       TYPE: Output
 VARIABLES DESCRIPTION:   Contains the return values of the call in the
 following array format: 
  
 XUSER(DIV IEN)=# 
  
 where DIV IEN is a Division IEN and # is 1 if this division is the user's 
 default and 0 if not 
VARIABLES: XUDUZ                        TYPE: Input
 VARIABLES DESCRIPTION:   This is a NEW PERSON file IEN (file 200) 
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL
 SUBSCRIBING DETAILS:   The Shift Change Handoff Tool is a new package that is
 related to the CPRS suite of applications.  The was originally Class III
 software that is being transitioned to Class I.  

NUMBER: 5140                            IA #: 5140
  DATE CREATED: FEB 19, 2008
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORB31
  NAME: ORB31                           ID: ORB31
  STATUS: Active
KEYWORDS: ORB31
COMPONENT/ENTRY POINT: TERMLKUP
 COMPONENT DESCRIPTION:   extrinsic function returns the local terms linked to
 the nat'l OCX term in an array and the file where those array terms can be
 found. The value of the extrinsic function is the file pointed to for the
 local terms.  
VARIABLES: $$TERMLKUP                   TYPE: Output
 VARIABLES DESCRIPTION:   Return array that contains the local terms linked to
 the nat'l OCX term 
VARIABLES: OCXARR                       TYPE: Input
 VARIABLES DESCRIPTION:   Array of local terms 
VARIABLES: OCXTERM                      TYPE: Input
 VARIABLES DESCRIPTION:   OCX nat'l term from file ^OCXS(860.9 
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: APR 11, 2012

NUMBER: 5141                            IA #: 5141
  DATE CREATED: FEB 19, 2008
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORQ20                        NAME: ORQ20
  ID: ORQ20                             STATUS: Pending
KEYWORDS: ORQ20
COMPONENT/ENTRY POINT: DATE
 COMPONENT DESCRIPTION:   Return date formatted as 00/00/0000 00:00 
VARIABLES: $$DATE                       TYPE: Output
 VARIABLES DESCRIPTION:   Date formatted as 00/00/0000 00:00 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   Input date formatted as a Fileman DT 
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL

NUMBER: 5142                            IA #: 5142
  DATE CREATED: FEB 19, 2008
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORWTPT                       NAME: ORWTPT
  ID: ORWTPT                            STATUS: Pending
KEYWORDS: ORWTPT
COMPONENT/ENTRY POINT: TEAMS
 COMPONENT DESCRIPTION:   returns all teams a user is a member of (exculdes
 personal lists) 
VARIABLES: TEAMS                        TYPE: Output
 VARIABLES DESCRIPTION:   return array containing all of the teams a user is a
 member of excluding personal lists.  
VARIABLES: USER                         TYPE: Input
 VARIABLES DESCRIPTION:   Input variable specifying the user to lookup for team
 info.  A file 200 IEN 
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL

NUMBER: 5143                            IA #: 5143
  DATE CREATED: FEB 19, 2008            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: VADPT3                       NAME: VADPT3
  ID: VADPT3                            STATUS: Pending
KEYWORDS: VADPT3
COMPONENT/ENTRY POINT: LAST
 COMPONENT DESCRIPTION:   returns last movement for patient 
VARIABLES: VAX                          TYPE: Output
 VARIABLES DESCRIPTION:   Return array containing the information about the
 last patient movement for patient DFN 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN (file 2) to lookup last movement info
 for.  
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL
 SUBSCRIBING DETAILS:   The Shift Change Handoff Tool is a new package thatis
 related to the CPRS suite of applications.  Thewas originally Class III
 software that is beingtransitioned to Class I.  

NUMBER: 5144                            IA #: 5144
  FILE NUMBER: 45.7                     GLOBAL ROOT: DIC(45.7,
  DATE CREATED: FEB 19, 2008            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: DIC(45.7,                       ID: DIC(45.7,
GLOBAL REFERENCE: DPT(45_7,D0,'PRO')
FIELD NUMBER: 10                        FIELD NAME: PROVIDERS
  LOCATION: 'PRO',0                     ACCESS: Read w/Fileman
  STATUS: Pending
KEYWORDS: DIC(45.7
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL
 SUBSCRIBING DETAILS:   The Shift Change Handoff Tool is a new package thatis
 related to the CPRS suite of applications.  Thewas originally Class III
 software that is beingtransitioned to Class I.  

NUMBER: 5145                            IA #: 5145
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100
  DATE CREATED: FEB 19, 2008
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: OR(100                          ID: OR(100
GLOBAL REFERENCE: OR(100,'AC'
 GLOBAL DESCRIPTION:   "AC" index lookup 
GLOBAL REFERENCE: OR(100,D0,0
 GLOBAL DESCRIPTION:   read access on node 0 
GLOBAL REFERENCE: OR(100,D0,1)
 GLOBAL DESCRIPTION:   Read access on node 1 
GLOBAL REFERENCE: OR(100,D0,3)
 GLOBAL DESCRIPTION:   Read access on node 3 
GLOBAL REFERENCE: OR(100,D0,6)
 GLOBAL DESCRIPTION:   Read access on node 6 
GLOBAL REFERENCE: OR(100,D0,8)
 GLOBAL DESCRIPTION:   Read access on node 8 
  STATUS: Pending
KEYWORDS: OR(100
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 04/14/22, effective with DSSV 1.1 DSS Class 3
 product Document Only - Not approved by Custodial SME 

NUMBER: 5146                            IA #: 5146
  FILE NUMBER: 100.24                   GLOBAL ROOT: OR(100.24,
  DATE CREATED: FEB 19, 2008
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: OR(100.24                       ID: OR(100.24,
GLOBAL REFERENCE: OR(100_24,D0,.01
 GLOBAL DESCRIPTION:   Read access for node .01 
  STATUS: Pending
KEYWORDS: OR(100.24
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL

NUMBER: 5147                            IA #: 5147
  FILE NUMBER: 101.41                   GLOBAL ROOT: ORD(101.41,
  DATE CREATED: FEB 19, 2008
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: ORD(101.41,                     ID: ORD(101.41,
GLOBAL REFERENCE: ORD(101.41,D0,9
 GLOBAL DESCRIPTION:   Read access on node 9 
  STATUS: Pending
KEYWORDS: ORD(101.41
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL

NUMBER: 5148                            IA #: 5148
  FILE NUMBER: 8925                     GLOBAL ROOT: TIU(8925,
  DATE CREATED: FEB 19, 2008
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  NAME: TIU(8925,                       ID: TIU(8925,
GLOBAL REFERENCE: TIU(8925,D0,15 PIECE 2
FIELD NUMBER: 1502                      FIELD NAME: SIGNED BY
  LOCATION: 15;2                        ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   Read access for field 1502 
  STATUS: Pending
KEYWORDS: TIU(8925
SUBSCRIBING PACKAGE: SHIFT CHANGE HANDOFF TOOL
 SUBSCRIBING DETAILS:   The Shift Change Handoff Tool is a new package that is
 related to the CPRS suite of applications.  Thewas originally Class III
 software that is beingtransitioned to Class I.  

NUMBER: 5149                            IA #: 5149
  GLOBAL ROOT: DD(File#,Field#,'V'      DATE CREATED: FEB 20, 2008
  CUSTODIAL PACKAGE: 1                  USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: V Nodes in the DD               ID: DD(File#,Field#,'V'
 GENERAL DESCRIPTION:   This grants direct read access to the "V" nodes of a
 field's DD.  Descendent from the "V" node is information regarding variable
 pointers including pointed-to file, message, order, prefix, screen, and LAYGO
 status.  
  
 ^DD(File#, Field#, "V", n, 0) 
  
 Where 'n' is a sequential number representing a different pointed-to file.  
 The pieces within this 0 node are: 
  
 ^-Piece   Contents 
  
  1        File number of the pointed-to file 
  2        Message defined for the pointed-to file 
  3        Order defined for the pointed-to file 
  4        Prefix defined for the pointed-to file 
  5        y/n indicating whether a screen is set up for the pointed-to 
           file 
  6        y/n indicating whether the user may add new entries to the 
           pointed-to file 
  
 ^DD(File#, Field#, "V", n, 1) contains the M code defined as a screen on the 
 pointer to the file defined in the 0 node above. ^DD(File#, Field#, "V", n, 2) 
 contains a description of the screen.  
  
 Additionally, the following xrefs exist and may be read and traversed by 
 direct means, too: 
  
 ^DD(File#, Field#, "V", "B" - xref on ^-Piece 1 of the 0 node.  
                         "M" -                 2 
                         "O" -                 3 
                         "P" -                 4 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   All variable pointer fields in all Clinical Reminder
 files.  
  
  DATE ACTIVATED: MAR 14, 2024

NUMBER: 5150                            IA #: 5150
  DATE CREATED: FEB 20, 2008            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMDRSG
  NAME: API TO GET RESULT GROUP TEXT    ID: PXRMDRSG
 GENERAL DESCRIPTION:   This API returns an array of text that is used by the
 calling package to display result text and informational text that is
 associated with a score(s) for a MH Test.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRMDRSG
KEYWORDS: PXRM
COMPONENT/ENTRY POINT: MHDLL
VARIABLES: RESULTS                      TYPE: Input
 VARIABLES DESCRIPTION:   RESULTS is an array containing the IEN for a Result
 Group entry from file 801.41.  
  
 RESULTS(n)=IEN 
  
  
VARIABLES: SCORES                       TYPE: Input
 VARIABLES DESCRIPTION:   SCORES is an array containing the MH Scale number and
 the Score for the MH Test.  
  
 SCORES(n)=MH SCALE NUMBER~Score 
  
  
VARIABLES: DFN                          TYPE: Input
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   ORY is an array that returns a formatted output text
 from a Result Group determine from the score for a MH Scale.  
  
 ORY(n)=TEXT 
  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: APR 22, 2025

NUMBER: 5151                            IA #: 5151
  DATE CREATED: FEB 25, 2008            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: Exit Action for XUMF MFS EVENTS
 GENERAL DESCRIPTION:   This agreement permits Kernel to export an Exit Action
 for the XUMF MFS EVENTS (MFS event driver) Protocol that invokes the following
 Health Data & Informatics (HDI) API: 
  
 EXIT ACTION: I $T(MFSEXIT^HDISVAP)'="" D MFSEXIT^HDISVAP 
  
 HDI has requested to be invoked in the Exit Action of the XUMF MFS EVENTS 
 protocol to update the implementation status for standardization of a file in
 a domain.  This action was previously invoked in the Master File Parameters
 Post-Processing Logic field by the applications.  We are requesting it be
 added to the Exit Action to make sure we are invoked last.  
  STATUS: Active
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS
  DATE ACTIVATED: MAY 01, 2008

NUMBER: 5152                            IA #: 5152
  DATE CREATED: FEB 26, 2008
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: CHECK FOR ORES KEY
 GENERAL DESCRIPTION:   This will allow Lab to do a check for the ORES key
 using the ^XUSEC global. Even though access to check for security keys is
 granted with a Kernel Integration Control Registration, this was produced to
 record that Lab would need to know if CPRS needed to modify the key that
 indicates a user is a provider. Lab Re-engineering needs this information for
 sending user updates to the Cerner lab system.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORES
KEYWORDS: LAB
KEYWORDS: XUSEC
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: MAR 22, 2011

NUMBER: 5153                            IA #: 5153
  DATE CREATED: JAN 21, 2011            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: DBIA-5153 - County Code         STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: AUG 03, 2011
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5154                            IA #: 5154
  DATE CREATED: MAR 04, 2008            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFCPID2
  NAME: NAME VAFCPID2                   ID: VAFCPID2
 GENERAL DESCRIPTION:   Lab application has permission to use the NAME^VAFCPID2
 API for standardization of the New Person file (#200) Name (.01) that is 
 transmitted to the Cerner Lab system from Legacy Vista Lab in the Master File
 Notification messages.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: NAME
 COMPONENT DESCRIPTION:   NAME receives three paramaters.  Two of the
 parameters are not used by the NAME API (DFN and FLG).  NAME also receives
 MPISTR which is the text data of the name to be formated.  NAME standardizes
 the format of the name received and returns it (by reference) in MPISTR.  
  
  NAME(DFN,MPISTR,FLG) 
    DFN - ien from Patient file  (received but not referenced) 
    MPISTR - Name as stored in New Person file (#200) 
    FLG -  Set to 0 in code and not referenced elsewhere 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Not referenced (Lab will pass in 0) 
VARIABLES: MPISTR                       TYPE: Both
 VARIABLES DESCRIPTION:   Initially this variable is passed (by reference) into
 the API as the New Person's Name to be standardized.  When the API completes
 execution, this variable contains the standardized version of the name and is 
 returned to the calling point (via reference).  
VARIABLES: FLG                          TYPE: Input
 VARIABLES DESCRIPTION:   The API sets this variable to 0 and it is not used. 
 (Lab will not pass this parameter.) 
SUBSCRIBING PACKAGE: AUTOMATED LAB INSTRUMENTS
 SUBSCRIBING DETAILS:   LA*5.2 will be passing the New Person Name to the
 Cerner COTS Lab system as part of the Lab System Re-Engineering Project.  Lab
 has permission to use NAME^VAFCPID2 to standardize the New Person Name data in
 the same format as MPI uses to standardize Patient Name.  
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   LR*5.2 has permission to use NAME^VAFCPID2 to
 standarize the format of the New Person Name field data prior to sharing it
 with the Cerner COTS system.  
  DATE ACTIVATED: MAR 04, 2008

NUMBER: 5155                            IA #: 5155
  FILE NUMBER: 70                       GLOBAL ROOT: DD(70.03
  DATE CREATED: MAR 07, 2008            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: Remove Rad/Nuc Med dd Screen from Subfield #70.03
  ID: DD(70.03
 GENERAL DESCRIPTION:   The Radiology/Nuclear Medicine application intends to
 remove the following Data Dictionary node 
  
      K ^DD(70.03,26,9.2) 
  
 This correction will eliminate the display warning message for a data screen
 that no longer exists.  
  
 This will be a one-time IA with the installation of patch RA*5.0*56.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 5156                            IA #: 5156
  FILE NUMBER: 79.1                     GLOBAL ROOT: DD(79.1
  DATE CREATED: MAR 07, 2008            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: Remove Rad/Nuc Med dd Screen from File #79.1
  ID: DD(79.1
 GENERAL DESCRIPTION:   The Radiology/Nuclear Medicine application intends to
 remove the following Data Dictionary node 
  
      K ^DD(79.1,21,9.2) 
  
 This correction will eliminate the display warning message for a data screen
 that no longer exists.  
  
 This will be a one-time IA with the installation of patch RA*5.0*56.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 5157                            IA #: 5157
  FILE NUMBER: 63                       GLOBAL ROOT: LR(
  DATE CREATED: MAR 14, 2008            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Access to AP SUPPLEMENTARY REPORT globals
  ID: LR(
GLOBAL REFERENCE: LR(D0,84,0)
FIELD NUMBER: 32.4                      FIELD NAME: AUTOPSY SUPPLEMENTARY REPORT
  LOCATION: 0                           ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,CY,D1,1.2,0)
FIELD NUMBER: 1.2                       FIELD NAME: SUPPLEMENTARY REPORT
  LOCATION: 0                           ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,EM,D1,1.2,0)
FIELD NUMBER: 1.2                       FIELD NAME: SUPPLEMENTARY REPORT
  LOCATION: 0                           ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,SP,D1,1.2,0)
FIELD NUMBER: 1.2                       FIELD NAME: SUPPLEMENTARY REPORT
  LOCATION: 0                           ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   OE/RR needs to access the AUTOPSY, CYTOPATHOLOGY,
 SURGICAL PATHOLOGY, & ELECTRON MICROSCOPY SUPPLEMENTARY REPORT globals to
 check for the existence of any Anatomic Pathology supplementary reports on a
 patient.  
  
 ^LR(D0,84,0)=^63.324DA^^  (#32.4) AUTOPSY SUPPLEMENTARY REPORT 
 ^LR(D0,CY,D1,1.2,0)=^63.907DA^^  (#1.2) SUPPLEMENTARY REPORT 
 ^LR(D0,EM,D1,1.2,0)=^63.207DA^^  (#1.2) SUPPLEMENTARY REPORT 
 ^LR(D0,SP,D1,1.2,0)=^63.817DA^^  (#1.2) SUPPLEMENTARY REPORT 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AUTOPSY SUPPLEMENTARY REPORT
KEYWORDS: CY SUPPLEMENTARY REPORT
KEYWORDS: EM SUPPLEMENTARY REPORT
KEYWORDS: SP SUPPLEMENTARY REPORT
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAR 17, 2008

NUMBER: 5158                            IA #: 5158
  FILE NUMBER: 27.11                    GLOBAL ROOT: DGEN(27.11
  DATE CREATED: MAR 17, 2008            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PATIENT ENROLLMENT
  ID: DGEN(27.11
GLOBAL REFERENCE: DGEN(27.11,'C',D0,D1)
FIELD NUMBER: n/a                       FIELD NAME: C Cross-reference
  ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGEN(27.11,D0,0
FIELD NUMBER: .08                       FIELD NAME: EFFECTIVE DATE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: ENROLLMENT PRIORITY
  LOCATION: 0;7                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DGEN(27.11,D0,'E')
FIELD NUMBER: 50.02                     FIELD NAME: SERVICE CONNECTED
  LOCATION: E;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 50.01                     FIELD NAME: ELIGIBILITY CODE
  LOCATION: E;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 50.03                     FIELD NAME: SERVICE CONNECTED PERCENTAGE
  LOCATION: E;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Integrated Billing package would like to request
 direct global and Fileman access to read the following fields of the Patient
 Enrollment file (#27.11) for reporting purposes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SERVICE CONNECTED
KEYWORDS: PATIENT ENROLLMENT
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: APR 24, 2008

NUMBER: 5159                            IA #: 5159
  FILE NUMBER: 441                      GLOBAL ROOT: PRC(441,
  DATE CREATED: MAR 18, 2008            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  NAME: DBIA5159                        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
 FIELD DESCRIPTION:   Current Item Description.  
FIELD NUMBER: 14                        FIELD NAME: DATE ITEM CREATED
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the date of the last update to the short
 description.  If the prosthetic item was billed before this date then the
 PRE-NIF Short description will be used, otherwise the Short Description will
 be used.  
GLOBAL REFERENCE: PRC(441,D0,9)
FIELD NUMBER: 52                        FIELD NAME: PRE_NIF SHORT DESCRIPTION
  LOCATION: 9;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Old Item Description.  
 GENERAL DESCRIPTION:   Integrated Billing requires one time access to the
 IFCAP Item Master file (#441).  Prosthetics changed from using the Item Master
 file as the source of the Prosthetics Item description to using the
 Prosthetics HCPCS.  Integrated Billing is now being updated to correspond to
 this change in Prosthetics.  However for already billed items the bill must
 not change, therefore for historical purposes, the Item Master description
 will be pulled and saved with the old/existing billed Prosthetics Items.  
                
 The Integrated Billing patch IB*2*389 post-init will access the Item Master
 file to get then store (#362.5,.05) the Item description for every prosthetic
 item billed at the time of the installation, not directly related to a Patient
 Item (#660).  
               
 This agreement will expire at the end of the IB*2*389 compliance date.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 5160                            IA #: 5160
  FILE NUMBER: 661.1                    GLOBAL ROOT: RMPR(661.1,
  DATE CREATED: MAR 18, 2008            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  NAME: DBIA5160                        ID: RMPR(661.1,
GLOBAL REFERENCE: RMPR(661.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: HCPCS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: SHORT NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: STATUS
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Standardized Prosthetic HCPCS file that contains HCPCS
 code used in Prosthetics 
 GENERAL DESCRIPTION:   Integrated Billing requires access to the PROSTHETIC
 HCPCS file (#661.1) to select and identify Prosthetics Items to be billed.  A
 Fileman lookup to file #661.1 will be used for selection and several fields
 for identification.  
   
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 5161                            IA #: 5161
  DATE CREATED: MAR 25, 2008            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LRLRVRF
  NAME: Laboratory Reference Range Uniform Formatting
  ID: LRLRVRF
 GENERAL DESCRIPTION:   In order to insure the uniform formatting of the
 display of laboratory results reference ranges a new API has been created.
 This new API is EN^LRLRRVF.  
  
 It is to be used as part of a set statement. For example: 
  
 S LRDV=$$EN^LRLRRVF(RLV,RHV) 
  
 It has two input values.  RLV - Reference Low Value, RHV - Reference High
 value 
  
 Both input values are required, but either or both can be set to null.  
  
 It will return the laboratory result refference ranges formatting using the
 following guidelines: 
  
 1.  If neither low or high reference value is defined, nothing prints.  2.  If
 the low only is defined and it is equal to 0 it prints: Ref: >=0 3.  If the
 low only is defined and the first character is "<" or ">" 
     it prints: Ref: low_value 4.  If the low only is defined and it is numeric
 it prints: Ref: >=10 5.  If the low only is defined and it is alphanumeric it
 prints: 
     Ref: RVLow 6.  If the high only is defined and it is equal to 0 it prints:
 Ref: 0 7.  If the high only is defined and the first character is "<" or ">" 
     it prints: Ref: high_value 8.  If the high only is defined and it is
 numeric it prints: Ref: <=20 9.  If the high only is defined and it is
 alphanumeric it prints: 
     Ref: RVHIGH 10. If both low and high are defined it prints: RVLOW - RVHIGH
 or 10 - 20.  
  
 This is a example display. The example results and the ranges are in the same
 order as the guidelines.  
  
                         ---- MISCELLANEOUS TESTS ---- 
                                                                                
    DATE    TIME   SPECIMEN          TEST         VALUE         Ref ranges 
 --------------------------------------------------------------------------
 -----
 10/25/2007 15:49  BLOOD             CML-F:       10               10/25/2007
 16:06  BLOOD             CML-F:       10            Ref: >=0 10/25/2007 16:06 
 BLOOD             CML-F:       10            Ref: >10 10/25/2007 16:10  BLOOD  
           CML-F:       9 L           Ref: >=10 10/25/2007 16:24  BLOOD         
    CML-F:       10            Ref: RVLOW 10/25/2007 16:29  BLOOD            
 CML-F:       10 H          Ref: 0 10/25/2007 16:29  BLOOD             CML-F:   
    10 H          Ref: <20 10/25/2007 16:32  BLOOD             CML-F:       22
 H          Ref: <=20 10/25/2007 17:35  BLOOD             CML-F:       10       
     Ref: RVHIGH 10/25/2007 17:38  BLOOD             CML-F:       15           
 10 - 20 
     ***numeric ranges*** 10/25/2007 17:45  BLOOD             CML-F:       17   
         RVLOW - RVHIGH 
     ***alphanumeric ranges*** 
  STATUS: Active
KEYWORDS: LR
  DATE ACTIVATED: MAR 25, 2008

NUMBER: 5162                            IA #: 5162
  DATE CREATED: MAR 25, 2008
  CUSTODIAL PACKAGE: HEALTH DATA & INFORMATICS
  USAGE: Supported                      TYPE: Other
  NAME: HDIS STATUS UPDATE EVENTS
 GENERAL DESCRIPTION:   This event point is used to post before/after status
 values whenever the implementation status of a file is changed.  The values
 posted are what would be output by $$GETSTAT^HDISVFO1() before and after the
 change is made.  The following nodes will be posted: 
  
  ^TMP("HDIS",$J,"STATUS",FileNumber,"BEFORE") = 
       StatusCode ^ StatusPointer ^ StatusDate 
  
  ^TMP("HDIS",$J,"STATUS",FileNumber,"AFTER") = 
       StatusCode ^ StatusPointer ^ StatusDate 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: EVENT
KEYWORDS: STATUS

NUMBER: 5163                            IA #: 5163
  GLOBAL ROOT: DD(                      DATE CREATED: MAR 25, 2008
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            NAME: USE OF FILEMAN IN ROUTINE DGMTDD
  ID: DD(
 GENERAL DESCRIPTION:   Routine ^DGMTDD uses a direct global read with ^DD to
 get the cross-references for the Current Means Test Status field - file #2,
 field #.14.  
  
 The code follows: CUR+15      .F  S DGIX=$O(^DD(2,.14,1,DGIX)) Q:'DGIX  X
 ^(DGIX,2) S X=DGCS CUR+19      .F  S DGIX=$O(^DD(2,.14,1,DGIX)) Q:'DGIX  X
 ^(DGIX,1) S X=DGMTS 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 5164                            IA #: 5164
  GLOBAL ROOT: DD(                      DATE CREATED: MAR 25, 2008
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            NAME: USE OF FILEMAN IN ROUTINE DGPMDDCN
  ID: DD(
 GENERAL DESCRIPTION:   Routine ^DGPMDDCN uses a direct global read with ^DD to
 set and kill cross-references for Patient file (#2) fields.  
  
 The code follows SET+3       F DGIX=0:0 S DGIX=$O(^DD(2,DGFLD,1,DGIX)) Q:'DGIX 
 X ^(DGIX,1) S X=DGPMX KILL+3      F DGIX=0:0 S DGIX=$O(^DD(2,DGFLD,1,DGIX))
 Q:'DGIX  X ^(DGIX,2) S X=DGPMX 
  
 Fields included are: 
   .1      Ward Location 
   .102    Current Movement 
   .013    Treating Specialty 
   .104    Provider 
   .1041   Attending Physician 
   .105    Current Admission 
   .108    Current Room 
   .109    Exclude From Facility 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 5165                            IA #: 5165
  FILE NUMBER: 59.72                    GLOBAL ROOT: PS(59.72,
  DATE CREATED: APR 02, 2008
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Controlled Subscription        TYPE: File
  NAME: WDDE DISPENSING CABINET         ID: PS(59.72,
GLOBAL REFERENCE: PS(59.72
FIELD NUMBER: .01                       FIELD NAME: CABINET ID
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: NAOU OR SATELLITE VAULT
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   This ICR allows access to the automated dispensing
 cabinets defined in the AUTOMATED DISPENSING CABINET file.  
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: WDDE
KEYWORDS: 59.72
KEYWORDS: AUTOMATED
KEYWORDS: DISPENSING
KEYWORDS: CABINET
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
  DATE ACTIVATED: FEB 02, 2009

NUMBER: 5166                            IA #: 5166
  FILE NUMBER: 59.71                    GLOBAL ROOT: PS(59.71,
  DATE CREATED: APR 02, 2008
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Controlled Subscription        TYPE: File
  NAME: WDDE DISPENSING SYSTEM          ID: PS(59.71,
GLOBAL REFERENCE: PS(59.71,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DIVISION
  LOCATION: 0;4                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: RECEIVING PROTOCOL
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2
  FIELD NAME: ENABLE DRUG FILE TRANSMISSION?
  LOCATION: 0;3                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: CABINET ID
  LOCATION: 1;0                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: WARD
  LOCATION: 2;0                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: WDDE STATUS
  LOCATION: 0;5                         ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   This ICR allows access to the automated dispensing
 systems defined in the AUTOMATED DISPENSING SYSTEM file.  
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: WDDE
KEYWORDS: DISPENSING
KEYWORDS: AUTOMATED
KEYWORDS: 59.71
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   INPT MEDS added 3/24/09.  Triggered change to
 Controlled from Private./jsh 
  DATE ACTIVATED: FEB 02, 2009

NUMBER: 5167                            IA #: 5167
  DATE CREATED: APR 04, 2008            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Private                        TYPE: Routine
  ROUTINE: PSBUTL1                      NAME: BCMA ORDER ACTIVITY
  ID: PSBUTL1
 GENERAL DESCRIPTION:   This API returns a patient's order activity information
 from the Bar Code Med Admin (BCMA) package for a specified time period.        
              
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: ORDER
KEYWORDS: 53.79
COMPONENT/ENTRY POINT: RETRO
VARIABLES: PSBDFNX                      TYPE: Input
 VARIABLES DESCRIPTION:   Patient's DFN [Required] 
  
VARIABLES: PSBORDX                      TYPE: Input
 VARIABLES DESCRIPTION:   BCMA Order Number [Required] 
  
VARIABLES: PSBFDTX                      TYPE: Input
 VARIABLES DESCRIPTION:   Fileman date & time to begin inquiry (inclusive.)
 [Required] 
  
VARIABLES: PSBRNG                       TYPE: Input
 VARIABLES DESCRIPTION:   Time range (hours default=8).  
  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   RESULTS (0) = RESULT data node count 
         (1) = -1^ERROR MESSAGE 
                 [or] 
               BCMA file IEN ^ BCMA action status ^ 
                 fileman action date/time ^ 
                 mm/dd/yyyy hh:mm (action date 
                 time) ^ fileman scheduled admin 
                 date time ^ mm/dd/yyyy hh:mm 
                 (scheduled admin date time) ^ 
                 associated users IEN (file #200) ^ 
                 associated users name 
         [n] =  - REPEAT -  output data per order 
                  (n) activity 
       [n+1] =  "END" 
  
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
  DATE ACTIVATED: FEB 02, 2009

NUMBER: 5168                            IA #: 5168
  DATE CREATED: JAN 21, 2011            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: DBIA-5168 - Postal Code         STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: APR 25, 2011
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5169                            IA #: 5169
  DATE CREATED: APR 07, 2008            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: YTAPI5
  NAME: MENTAL HEALTH YTAPI5 TOOLS      ID: YTAPI5
 GENERAL DESCRIPTION:   Tools to produce horizontal GAF reference and to check
 the Privleging of legacy instruments.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GAF HORIZONTAL
KEYWORDS: MHA2 PRIVLEGES
COMPONENT/ENTRY POINT: GAFURL
 COMPONENT DESCRIPTION:   No input required. Returns: 
 http://vaww.mentalhealth.DNS/gafsheet.htm 
COMPONENT/ENTRY POINT: PRIVL
 COMPONENT DESCRIPTION:   Returns Privielging by test as set in MHA2.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   .01 Name in file 601 for a "test". GAF and ASI are
 accepted.  
VARIABLES: YSDATA(2)                    TYPE: Output
 VARIABLES DESCRIPTION:   First piece is boolean 1 for privieleged , 0 for not
 priveleged. Second piece is free text describing how decison was made.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 05/27/21 to document GAF use as a screening tool.
 OE/RR uses GAFURL^YTAPI5 and PRIVL^YTAPI5 in routine ORWPCE2. The usage of the
 API was covered historically under ICR 4041, but 4041 was withdrawn in the 
 past. Note: GAF is no longer a diagnostic tool in Mental Health but OK for
 screening.  
  DATE ACTIVATED: MAY 27, 2021

NUMBER: 5170                            IA #: 5170
  DATE CREATED: APR 11, 2008            CUSTODIAL PACKAGE: FOUNDATIONS
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: gov.va.med.monitor.time.AuditTimer
 GENERAL DESCRIPTION:   public class AuditTimer extends java.lang.Object: 
  
 The AuditTimer class gives an easy way to capture performance statistics and
 log them to a log file. Internally System.currentTimeMillis() is used.  
 Typical steps for using this class: 
  
 1. Create an instance: auditTimer = new AutitTimer() 2. auditTimer.start() 3.
 auditTimer.stop() 4. auditTimer.getTimeElapsedMillis() 
  
 autitTimer.start() should be called before auditTimer.stop() is called.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AuditTimer
KEYWORDS: Foundations
KEYWORDS: FoundationsLib
COMPONENT/ENTRY POINT: constructor
 COMPONENT DESCRIPTION:   public AuditTimer(): Default constructor. Default
 logger gov.va.med.foundations.utilities.AuditTimer will be used. 
  
 public AuditTimer(org.apache.log4j.Logger logger): Constructor that accepts
 logger to be used for output. Application can pass in their own loggers to
 have granual control over logging.  
VARIABLES: logger                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) org.apache.log4j.Logger: logger to use to
 write AuditTimer output to.  
COMPONENT/ENTRY POINT: start
 COMPONENT DESCRIPTION:   public void start(): Starts the timer.  
COMPONENT/ENTRY POINT: stop
 COMPONENT DESCRIPTION:   public long stop(): Stops the timer. If start() was
 not called at least once before stop() is called timeElapsedMillis is set to
 -1. This method does not throw Exceptions, to keep client code simple.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns long: elapsed time since timer start in
 milliseconds (or -1 if timer not started.) 
COMPONENT/ENTRY POINT: getTimeElapsedMillis()
 COMPONENT DESCRIPTION:   public long getTimeElapsedMillis(): returns the
 elapsed milliseconds between the last start()/stop() cycle.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns long: # of elapsed milliseconds between last
 start()/stop() cycle.  
COMPONENT/ENTRY POINT: log
 COMPONENT DESCRIPTION:   public void log(): Logs a message to the log4j logger
 in a following format: elapsed_time_milliseconds 
  
 public void log(java.lang.String message): Logs a message to the log4j logger
 in a following format: your_message elapsed_time_milliseconds 
VARIABLES: message                      TYPE: Input
 VARIABLES DESCRIPTION:   (optional) java.lang.String message: message to
 prepend to output.  
COMPONENT/ENTRY POINT: isAuditTimerEnabled()
 COMPONENT DESCRIPTION:   public static boolean isAuditTimerEnabled(): returns
 whether info-level is currently enabled on the default logger.  
  
 public static boolean isAuditTimerEnabled(org.apache.log4j.Logger logger): 
 returns whether info-level logging is currently enabled for the specified
 logger (AuditTimer log writes use info-level loggers).  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns boolean: true if info-level logging is on,
 false if not.  
VARIABLES: logger                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) org.apache.log4j.Logger: the logger to
 check. If not passed, the default logger is checked.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5171                            IA #: 5171
  DATE CREATED: APR 11, 2008            CUSTODIAL PACKAGE: FOUNDATIONS
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: gov.va.med.crypto.VistaKernelHash
 GENERAL DESCRIPTION:   public class VistaKernelHash extends java.lang.Object: 
  
 Implements static methods to provide the encoding algorithms used by the RPC
 Broker and Kernel to encode and decode data strings. Using these algorithms
 makes it harder to sniff the contents of text sent over the network. This is
 not, however, encryption-class encoding, nor does it protect against replay
 attacks of un-decoded strings, and therefore use of this algorithm should not
 be considered to imply or achieve any particular level of security. 
  
 For example: 
  
 String encodedString = VistaKernelHash.encrypt("some text to encode", true); 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Foundations
KEYWORDS: FoundationsLib
KEYWORDS: VistaKernelHash
COMPONENT/ENTRY POINT: decrypt()
 COMPONENT DESCRIPTION:   public static java.lang.String
 decrypt(java.lang.String encryptedText): 
  
 Decrypts a string using the same encoding algorithm as the RPC Broker uses.  
VARIABLES: encryptedText                TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String: The text to decode. Must be
 characters between ASCII 32 and 128.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: a decrypted (decoded)
 version of the input string.  
COMPONENT/ENTRY POINT: encrypt()
 COMPONENT DESCRIPTION:   public static java.lang.String
 encrypt(java.lang.String normalText, boolean
 preventEncryptionsContainingCDataSectionBoundaries) throws 
 VistaKernelHashCountLimitExceededException: 
  
 Encrypts a string using the same encoding algorithm as the RPC Broker uses.  
VARIABLES: normalText                   TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String normalText: the text to encode. Must
 be characters between ASCII 32 and 128.  
VARIABLES: preventEncryptionsCont       TYPE: Input
 VARIABLES DESCRIPTION:   boolean
 preventEncryptionsContainingCDataSectionBoundaries: if true, the returned
 encrypted strings are guaranteed not to contain either "]]>" or "<![CDATA[".
 Otherwise, it is possible a returned encryption may conta in those character
 sequences. 
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: an encrypted (encoded)
 version of the input string.  
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   throws
 gov.va.med.crypto.VistaKernelHashCountLimitExceededException: if requested
 that the method not return a result with CData section boundaries, and if the
 algorithm runs up to a count limit (presently 2000 tries) without generating a
 result without such boundaries, an exception is thrown.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5172                            IA #: 5172
  DATE CREATED: APR 11, 2008            CUSTODIAL PACKAGE: FOUNDATIONS
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: gov.va.med.environment.Environment
 GENERAL DESCRIPTION:   public class Environment extends java.lang.Object:
 Environment settings for J2EE server use.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Foundations
KEYWORDS: FoundationsLib
KEYWORDS: Environment
COMPONENT/ENTRY POINT: getServerType()
 COMPONENT DESCRIPTION:   public static ServerType getServerType(): Returns the
 J2EE server type.  The source of the setting is the
 gov.va.med.environment.servertype JVM argument passed to the J2EE server upon
 startup. If JVM arg missing, looks for WebLogic-specific classloader classes
 to determine if server type is WebLogic. Defaults to return UNKNOWN if the JVM
 argument is not present.  
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   gov.va.med.environment.ServerType: an enumerated J2EE
 server type (weblogic, tomcat, websphere, etc.) 
COMPONENT/ENTRY POINT: isProduction()
 COMPONENT DESCRIPTION:   public static boolean isProduction(): Returns whether
 the administrator has configured the J2EE server to be "production" in a
 VA-medical-center sense, i.e., is this system operating on production VA data.
 The source of the setting is the gov.va.med.environment.production JVM
 argument passed to the J2EE server upon startup. A setting of true desginates
 the server as a production server; any other value (including not passing the
 JVM argument at all) marks the server as not a VA production server.  
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   boolean: true if the server is a VA production
 server, false if not.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5173                            IA #: 5173
  DATE CREATED: APR 11, 2008            CUSTODIAL PACKAGE: FOUNDATIONS
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: gov.va.med.environment.ServerType
 GENERAL DESCRIPTION:   public class ServerType extends java.lang.Object:
 Enumerated J2EE server types.  
  
 Example Use: 
  
   if (Environment.getServerType().equals(ServerType.WEBLOGIC)) { 
     // weblogic-specific code 
   }
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Foundations
KEYWORDS: FoundationsLib
KEYWORDS: servertype
COMPONENT/ENTRY POINT: static ServerType JAVA_SE 
 COMPONENT DESCRIPTION:   represents J2SE mode, non-J2EE "server" type 
COMPONENT/ENTRY POINT: static ServerType JBOSS 
COMPONENT/ENTRY POINT: static ServerType ORACLE 
COMPONENT/ENTRY POINT: static ServerType SUN_RI_13  
COMPONENT/ENTRY POINT: static ServerType TOMCAT 
COMPONENT/ENTRY POINT: static ServerType UNKNOWN 
COMPONENT/ENTRY POINT: static ServerType WEBLOGIC
COMPONENT/ENTRY POINT: static ServerType WEBSPHERE  
COMPONENT/ENTRY POINT: toString()
 COMPONENT DESCRIPTION:   public java.lang.String toString(): returns the
 server type as a string value.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: the server type as a string
 value.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5174                            IA #: 5174
  DATE CREATED: APR 11, 2008            CUSTODIAL PACKAGE: FOUNDATIONS
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.exception.ExceptionUtils
 GENERAL DESCRIPTION:   public class ExceptionUtils extends java.lang.Object:
 Exposes utility methods for handling exceptions. Note: DEPRECATED CLASS.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Foundations
KEYWORDS: FoundationsLib
KEYWORDS: Exception
COMPONENT/ENTRY POINT: getFullStackTrace()
 COMPONENT DESCRIPTION:   public static java.lang.String
 getFullStackTrace(java.lang.Throwable e): Deprecated. Superceded by JDK 1.4+
 exception functionality.  
  
 Gets the full stack trace, including nested exceptions, as a string.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   java.lang.String: full stack trace including nested
 exceptions as a string.  
VARIABLES: e                            TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.Throwable e: Throwable exception to get
 stack trace from.  
COMPONENT/ENTRY POINT: getNestedExceptionByClass()
 COMPONENT DESCRIPTION:   public static java.lang.Throwable 
 getNestedExceptionByClass(java.lang.Throwable e, java.lang.Class 
 exceptionClass): Deprecated. Superceded by JDK 1.4+ exception functionality.  
  
 Gets the nested exception if exception is an instance of the exceptionClass or
 if any nested exception is an instance of the type exceptionClass. 
  
 If desired instance of exceptionClass is not found in the nested exception
 stack then null is returned. 
  
 Can be used to unwind nested exception stack. 
VARIABLES: e                            TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.Throwable e: Exception to check for nested
 exceptions within.  
VARIABLES: exceptionClass               TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.Class exceptionClass: class of the type of
 nested exception to look for.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.Throwable: nested exception
 matching requested class, if found.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5175                            IA #: 5175
  DATE CREATED: APR 11, 2008            CUSTODIAL PACKAGE: FOUNDATIONS
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.exception.FoundationsExceptionInterface
 GENERAL DESCRIPTION:   public interface FoundationsExceptionInterface:
 Represents the interface that all Foundations exceptions implement.
 Implementing this interface allows ExceptionUtils to work with the exception.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Foundations
KEYWORDS: FoundationsLib
KEYWORDS: Exception
COMPONENT/ENTRY POINT: getFullStackTrace()
 COMPONENT DESCRIPTION:   java.lang.String getFullStackTrace(): Deprecated. Use 
 Throwable.getStackTrace() instead.  
  
 Return full stack trace. Full stack trace will include all nested exception
 messages and the full stack trace for the root exception. 
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: full stack trace
 representation.  
COMPONENT/ENTRY POINT: getNestedException()
 COMPONENT DESCRIPTION:   java.lang.Throwable getNestedException(): Deprecated.
 Use Throwable.getCause() instead.  
  
 Return nested exception that is wrapped within this exception.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.Throwable: nested exception if any. 
 
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5176                            IA #: 5176
  DATE CREATED: APR 11, 2008            CUSTODIAL PACKAGE: FOUNDATIONS
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: gov.va.med.net.SocketManager
 GENERAL DESCRIPTION:   public class SocketManager extends java.lang.Object
 implements java.io.Serializable: Represents a socket that can be used to
 communicate with IP end points.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Foundations
KEYWORDS: FoundationsLib
KEYWORDS: socket
COMPONENT/ENTRY POINT: getBufferSize()
 COMPONENT DESCRIPTION:   public int getBufferSize(): Returns the buffer size
 (int).  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns int: buffer size.  
COMPONENT/ENTRY POINT: setBufferSize()
 COMPONENT DESCRIPTION:   void setBufferSize(int value): Sets the buffer size.  
VARIABLES: value                        TYPE: Input
 VARIABLES DESCRIPTION:   int: size to set buffer to.  
COMPONENT/ENTRY POINT: getSoc()
 COMPONENT DESCRIPTION:   public java.net.Socket getSoc(): Gets the socket
 associated with this SocketManager.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.net.Socket: socket associated with this
 socket manager.  
COMPONENT/ENTRY POINT: constructor
 COMPONENT DESCRIPTION:   public SocketManager(): constructs a Socket Manager
 instance.  
  
 public SocketManager(java.net.Socket soc): constructs a Socket Manager 
 instance.  
VARIABLES: socket                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) java.net.Socket: construct the Socket
 Manager and set its socket to the specified socket.  
COMPONENT/ENTRY POINT: setSoc()
 COMPONENT DESCRIPTION:   void setSoc(java.net.Socket value): Sets the socket
 associated with this SocketManager.  
VARIABLES: value                        TYPE: Input
 VARIABLES DESCRIPTION:   java.net.Socket: the socket to associate with this
 SocketManager.  
COMPONENT/ENTRY POINT: sendData()
 COMPONENT DESCRIPTION:   public void sendData(java.lang.String xmlRequest)
 throws VistaSocketException: 
  
 Writes data to the open socket.  
VARIABLES: data                         TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String: data to write to the open socket.  
COMPONENT/ENTRY POINT: receiveData()
 COMPONENT DESCRIPTION:   public java.lang.String receiveData() throws
 VistaSocketException, VistaSocketTimeOutException: 
  
 Reads the socket for a response and writes to String.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: return value.  
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   throws: gov.va.med.net.VistaSocketException, 
 gov.va.med.net.VistaSocketTimeOutException.  
COMPONENT/ENTRY POINT: getMatchingIdentifier()
 COMPONENT DESCRIPTION:   public java.lang.String getMatchingIdentifier(): Gets
 the socket's identifier (if any).  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: socket's identifier.  
COMPONENT/ENTRY POINT: setMatchingIdentifier()
 COMPONENT DESCRIPTION:   void setMatchingIdentifier(java.lang.String string):
 Sets an identifier to identify the socket.  
VARIABLES: string                       TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String: identifier for socket.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5177                            IA #: 5177
  DATE CREATED: APR 11, 2008            CUSTODIAL PACKAGE: FOUNDATIONS
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: gov.va.med.xml.XmlUtilities
 GENERAL DESCRIPTION:   public class XmlUtilities extends java.lang.Object:
 Deprecated. Need for XML utilities has been superceded by the many
 JRE-built-in and external XML frameworks.  
  
 This class contains a number of static utility methods to help developers work
 with XML documents, nodes, attributes and strings.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Foundations
KEYWORDS: FoundationsLib
KEYWORDS: xml
COMPONENT/ENTRY POINT: XML_HEADER 
 COMPONENT DESCRIPTION:   Deprecated. public static final java.lang.String
 XML_HEADER: Represents the default header used for all xml documents that
 communicate with an M server via VistALink. It is important to use this header
 as keeps the client and M server in sync. Note that that as a String constant,
 this value is compiled into the calling class at compile time; it is not
 dynamically linked at runtime. 
COMPONENT/ENTRY POINT: convertXmlToStr()
 COMPONENT DESCRIPTION:   public static java.lang.String
 convertXmlToStr(org.w3c.dom.Document doc) throws FoundationsException: 
  
 Deprecated. Need for XML utilities has been superceded by the many 
 JRE-built-in and external XML frameworks.  
  
 Converts a DOM document to a string.  
VARIABLES: doc                          TYPE: Input
 VARIABLES DESCRIPTION:   org.w3c.dom.Document doc: document to convert.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: string conversion of DOM
 document.  
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   Throws: FoundationsException 
COMPONENT/ENTRY POINT: getNode()
 COMPONENT DESCRIPTION:   public static org.w3c.dom.Node
 getNode(java.lang.String xpathStr, org.w3c.dom.Node node): Deprecated. Need
 for XML utilities has been superceded by the many JRE-built-in and external
 XML frameworks 
  
 Returns the first node at the specified XPath location. Example: 
  
 This example returns the Customer/Address node in the specified document 
 object. 
  
 Node address = XmlUtilities.getNode("/Customer/Address", custDoc); 
VARIABLES: xpathStr                     TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String xpathStr: xpath location
 specification 
VARIABLES: node                         TYPE: Input
 VARIABLES DESCRIPTION:   org.w3c.dom.Node node: Node to search.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns org.w3c.dom.Node: first node found.  
COMPONENT/ENTRY POINT: getAttr()
 COMPONENT DESCRIPTION:   public static org.w3c.dom.Attr
 getAttr(org.w3c.dom.Node node, java.lang.String attrName): Deprecated. Need
 for XML utilities has been superceded by the many JRE-built-in and external
 XML frameworks.  
  
 Returns the Attribute with the given attrName at node. Example: 
  
 This example returns the 'state' attribute from the address node. 
  
 Attr state = getAttr(address,"state") 
VARIABLES: node                         TYPE: Input
 VARIABLES DESCRIPTION:   org.w3c.dom.Node node: Node to search.  
VARIABLES: attrName                     TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String attrName: Name of the attribute to
 find.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns org.w3c.dom.Attr: attribute found.  
COMPONENT/ENTRY POINT: getDocumentForXmlString()
 COMPONENT DESCRIPTION:   public static org.w3c.dom.Document 
 getDocumentForXmlString(java.lang.String xml) throws FoundationsException: 
  
 Deprecated. Need for XML utilities has been superceded by the many 
 JRE-built-in and external XML frameworks.  
  
 Returns an XML DOM Document for the specified String. Example: 
  
 This example creates a customer XML document for a serialized customer: 
  
 Document cust = XmlUtilities.getDocumentForXmlString(custXmlString); 
VARIABLES: xml                          TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String xml: serialized XML document.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns org.w3c.dom.Document: XML document 
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   Throws: gov.va.med.exception.FoundationsException 
COMPONENT/ENTRY POINT: getDocumentForXmlInputStream()
 COMPONENT DESCRIPTION:   public static org.w3c.dom.Document 
 getDocumentForXmlInputStream(java.io.InputStream xml) throws 
 FoundationsException: 
  
 Deprecated. Need for XML utilities has been superceded by the many 
 JRE-built-in and external XML frameworks.  
  
 Returns an XML DOM Document for the specified InputStream Example: 
  
 This example creates a customer XML document from an input stream. 
  
 Document cust = XmlUtilities.getDocumentForXmlInputStream(custStream); 
VARIABLES: xmlInput                     TYPE: Input
 VARIABLES DESCRIPTION:   java.io.InputStream xmlInput: input stream to be
 processed.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns org.w3c.dom.Document: XML document.  
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   Throws: gov.va.med.exception.FoundationsException 
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5178                            IA #: 5178
  DATE CREATED: APR 11, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.adapter.cci.VistaLinkConnectionFactory
 GENERAL DESCRIPTION:   public class VistaLinkConnectionFactory extends
 java.lang.Object implements javax.resource.cci.ConnectionFactory,
 java.io.Serializable, javax.resource.Referenceable.  
  
 This implementation class provides an interface for getting connection to an
 EIS instance. It should be retrieved via JNDI lookup from the J2EE container.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: getConnection()
 COMPONENT DESCRIPTION:   public javax.resource.cci.Connection getConnection()
 throws javax.resource.ResourceException 
  
 Gets a VistaLinkConnection handle for J2SE mode (no argument) 
  
 public javax.resource.cci.Connection 
 getConnection(javax.resource.cci.ConnectionSpec connectionSpec) throws 
 javax.resource.ResourceException 
  
 Gets a VistaLink connection in J2EE mode (connection spec argument).  
VARIABLES: connectionSpec               TYPE: Input
 VARIABLES DESCRIPTION:   javax.resource.cci.ConnectionSpec: For J2EE only.
 Pass in a VistALink connectionSpec implementation to identify the end-user
 under whose identity to execute RPCs. For J2SE, use the no-arg version of this
 method.  
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   javax.resource.cci.Connection: returns a handle to a
 connection from the connection pool.  
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   throws javax.resource.ResourceException.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5179                            IA #: 5179
  DATE CREATED: APR 11, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.adapter.cci.VistaLinkConnection
 GENERAL DESCRIPTION:   public interface VistaLinkConnection extends 
 javax.resource.cci.Connection: This interface represents an application level
 connection handle that is used by a component to access an EIS instance. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: executeRpc()
 COMPONENT DESCRIPTION:   gov.va.med.vistalink.rpc.RpcResponse 
 executeRPC(gov.va.med.vistalink.rpc.RpcRequest request) throws 
 gov.va.med.vistalink.adapter.record.VistaLinkFaultException, 
 gov.va.med.exception.FoundationsException: 
  
 Executes an interaction with M using the RpcResponseFactory to construct a 
 response.  
VARIABLES: request                      TYPE: Input
 VARIABLES DESCRIPTION:   gov.va.med.vistalink.rpc.RpcRequest: The request
 being made.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns gov.va.med.vistalink.rpc.RpcResponse: the
 response that is returned 
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   throws: VistaLinkFaultException - thrown if an error
 occurred on M while processing the request.  FoundationsException - thrown if
 an internal adapter exception has occurred.  
COMPONENT/ENTRY POINT: getConnectionInfo()
 COMPONENT DESCRIPTION:   gov.va.med.vistalink.adapter.spi.VistaLinkServerInfo
 getConnectionInfo(): 
  
 Returns connection information about the host. The return value represents M
 VistA information for the connection, like address and port. For developer
 debugging. 
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   gov.va.med.vistalink.adapter.spi.VistaLinkServerInfo:
 value object containing information about the Vista Server connection.  
COMPONENT/ENTRY POINT: getTimeOut()
 COMPONENT DESCRIPTION:   int getTimeOut(): Returns current connection time out
 value.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns int: time out value in milliseconds.  
COMPONENT/ENTRY POINT: setTimeOut()
 COMPONENT DESCRIPTION:   void setTimeOut(int timeOut): Enables application to
 set time out for read operations on connections.  
VARIABLES: timeOut                      TYPE: Input
 VARIABLES DESCRIPTION:   int: time out value to set in milliseconds. This
 timeout value is compared to the default value usually used for the
 connection. The greater of the two values will be used. 
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5180                            IA #: 5180
  DATE CREATED: APR 11, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.adapter.cci.VistaLinkConnectionSpec
 GENERAL DESCRIPTION:   public interface VistaLinkConnectionSpec extends 
 javax.resource.cci.ConnectionSpec 
  
 This interface defined the common properties needed by any VistALink 
 connection spec implementation.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: getDivision
 COMPONENT DESCRIPTION:   java.lang.String getDivision(): Returns the division
 of this ConnectionSpec. 
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   java.lang.String: Returns the division (station#) of
 this ConnectionSpec.  
COMPONENT/ENTRY POINT: setDivision
 COMPONENT DESCRIPTION:   void setDivision(java.lang.String division): sets the
 division (station #) of the connection spec.  
VARIABLES: division                     TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String division: the division number to be
 set.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5181                            IA #: 5181
  DATE CREATED: APR 15, 2008            CUSTODIAL PACKAGE: CONTROLLED SUBSTANCES
  USAGE: Private                        TYPE: Routine
  ROUTINE: PSDHLRFD                     NAME: DRUG WASTAGE
  ID: PSDHLRFD
 GENERAL DESCRIPTION:   This API returns wastage base on the amount of
 medication ordered through the Inpatient Medications V. 5.0 application vs.
 the amount processed from the automated dispensing cabinet of the Ward Drug
 Dispensing Equipment (WDDE) software.  
  
  STATUS: Withdrawn
KEYWORDS: WASTAGE
KEYWORDS: WDDE
KEYWORDS: 58.81
COMPONENT/ENTRY POINT: WASTAGE
VARIABLES: TRNS                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of file #58.81.  
  
VARIABLES: $$WASTAGE                    TYPE: Output
 VARIABLES DESCRIPTION:   Returns 
   0 - no wastage 
   1^Drug IEN (file #50)^ordered dosage^dispensed dosage 
  
  
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
  DATE ACTIVATED: FEB 02, 2009

NUMBER: 5182                            IA #: 5182
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: APR 17, 2008            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ECME WRITE ACCESS TO NEW PERSON FILE
  ID: VA(200
 GENERAL DESCRIPTION:   ECME (BPS) Requests write access to the New Person
 (#200) file for the following fields via Fileman Input Template: 
  
     OFFICE PHONE (#.132) 
     EMAIL ADDRESS (#.151) 
     TITLE (#8) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NEW PERSON
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE

NUMBER: 5183                            IA #: 5183
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: APR 18, 2008
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: File
  NAME: PHARMACY DATA MANAGEMENT        ID: PS(55,
GLOBAL REFERENCE: PS(55,D0,5,D1,0)
FIELD NUMBER: 68                        FIELD NAME: LAST WARD
  LOCATION: 0;23                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,D0,5,D1,.2)
FIELD NUMBER: 109                       FIELD NAME: DOSAGE ORDERED
  LOCATION: .2;2                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,'AUDS',X,D0,D1)
 GLOBAL DESCRIPTION:   This cross reference is used to identify active unit
 dose orders for a patient during a specified reporting period.  
  
 GENERAL DESCRIPTION:   The Ward Drug Dispensing Equipment (WDDE) project is
 requesting access to two fields and a cross-reference of the PHARMACY PATIENT
 file 55 that are not provided by current APIs.  
  
  STATUS: Withdrawn
KEYWORDS: 55
KEYWORDS: WDDE
SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
 SUBSCRIBING DETAILS:   ADDED 12/11/2009 
  DATE ACTIVATED: FEB 02, 2009

NUMBER: 5184                            IA #: 5184
  FILE NUMBER: 58.2                     GLOBAL ROOT: PSI(58.2
  DATE CREATED: APR 21, 2008
  CUSTODIAL PACKAGE: AUTO REPLENISHMENT/WARD STOCK
  USAGE: Private                        TYPE: File
  NAME: INPATIENT PHARMACY              ID: PSI(58.2
GLOBAL REFERENCE: PSI(58.2,D0,3,D1)
FIELD NUMBER: ALL FIELDS IN 58.29 MULTIPLE
  ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This ICR was not activated as of 9/1/20, but the ICR
 and Pharmacy team determined that if it gets activated, the custodial package
 needed to change to Auto Replenishment/Ward Stock, instead of Inpatient
 Medications.  
  
 This was the only text before 9/1/20: Controlled substance requires access to
 the AOU INVENTORY GROUP file #58.2, the Areas of Use information for reporting
 purposes.  
  STATUS: Pending
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES

NUMBER: 5185                            IA #: 5185
  DATE CREATED: APR 21, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  ROUTINE: IBNCDNC
  NAME: Update IB NDC NON COVERED BY PLAN FILE #366.16
  ID: IBNCDNC
 GENERAL DESCRIPTION:   The IB API to add/update a record in the file IB NDC
 NON COVERED BY PLAN FILE #366.16 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: NCPDP
COMPONENT/ENTRY POINT: UPDLST
VARIABLES: IBRXN                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry NUmber of PRESCRIPTION FILE (#52)
 record.  
VARIABLES: IBNDC                        TYPE: Input
 VARIABLES DESCRIPTION:   NDC 
VARIABLES: IBPLAN                       TYPE: Input
 VARIABLES DESCRIPTION:   INternal Entry Number of GROUP INSURANCE PLAN FILE
 #355.3 record 
VARIABLES: IBRJCODE                     TYPE: Input
 VARIABLES DESCRIPTION:   Reject code.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: APR 21, 2008

NUMBER: 5186                            IA #: 5186
  DATE CREATED: APR 22, 2008            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOREJU3
  NAME: PSOREJU3                        ID: PSOREJU3
 GENERAL DESCRIPTION:   This routine contains an API used by CMOP to validate
 ePharmacy third party Tricare insurance response information.  
  STATUS: Active
KEYWORDS: PSOREJP4
KEYWORDS: EPHARMACY
COMPONENT/ENTRY POINT: $$TRISTA(RX,RFL,.RESP,FROM)
 COMPONENT DESCRIPTION:   This API is used to validate whether the prescription
 should be pulled from suspense.  It verifies that the response message from
 ECME does not indicate that the claim is still in progress or it is not
 non-billable.  If either of these are the case, a 1 (one) is returned. The
 default is 0 (zero).  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN.  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Prescription fill number.  
VARIABLES: RESP                         TYPE: Input
 VARIABLES DESCRIPTION:   Response information from ECME for the Rx and fill. 
 See IA #4415 for detailed information of what is returned from ECME.  
VARIABLES: FROM                         TYPE: Input
 VARIABLES DESCRIPTION:   Code for the calling routine (i.e. PL or PC for
 suspense).  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 (one) for hold Rx in suspense or 0 (zero)
 to not hold in suspense.  
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: APR 25, 2008

NUMBER: 5187                            IA #: 5187
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG
  DATE CREATED: APR 24, 2008
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSCLINR
  NAME: CLINICAL REMINDERS API          ID: PSSCLINR
GLOBAL REFERENCE: IX(PSSCRIX,PSSCRIV)
FIELD NUMBER: 20                        FIELD NAME: NATIONAL DRUG FILE ENTRY
  LOCATION: PSDRUG(D0,"ND")             ACCESS: Read w/Fileman
FIELD NUMBER: 25                        FIELD NAME: NATIONAL DRUG CLASS
  LOCATION: PSDRUG(D0,"ND")             ACCESS: Read w/Fileman
  STATUS: Active
COMPONENT/ENTRY POINT: IX(PSSCRIX,PSSCRIV)
VARIABLES: PSSCRIX                      TYPE: Input
 VARIABLES DESCRIPTION:   This field can be either the "VAC" cross -reference
 for the NATIONAL DRUG F FILE ENTRY (#20) field or the "AND" cross-reference
 for the NATIONAL DRUG CLASS (#25) field within the DRUG (#50) file.  
VARIABLES: PSSCRIV                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the data value for the index 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,PSSCRIX,PSSCRIV) = ^PSDRUG(PSSCRIX,PSSCRIV) 
COMPONENT/ENTRY POINT: DRUG(PSSCLID)
 COMPONENT DESCRIPTION:   Returns the Drug name from file 50 
VARIABLES: PSSCLID                      TYPE: Input
 VARIABLES DESCRIPTION:   File 50 IEN 
COMPONENT/ENTRY POINT: ITEM(PSSCLII)
 COMPONENT DESCRIPTION:   Returns the Pharmacy Orderable Item pointer from file
 50.  
VARIABLES: PSSCLII                      TYPE: Input
 VARIABLES DESCRIPTION:   File 50 IEN 
COMPONENT/ENTRY POINT: ING(PSSING)
 COMPONENT DESCRIPTION:   Return Drug ingredient name 
VARIABLES: PSSING                       TYPE: Input
 VARIABLES DESCRIPTION:   File 50.416 IEN 
COMPONENT/ENTRY POINT: IEN(PSSING)
 COMPONENT DESCRIPTION:   Return Drug Ingredient IEN from file 50.416 
VARIABLES: PSSING                       TYPE: Input
 VARIABLES DESCRIPTION:   Drug Ingredient Name 
COMPONENT/ENTRY POINT: NEPS()
 COMPONENT DESCRIPTION:   Return Number of entries in file 55 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: MAR 23, 2011

NUMBER: 5188                            IA #: 5188
  DATE CREATED: APR 24, 2008            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  ROUTINE: PSO52CLR                     NAME: CLINICAL REMINDERS API
  ID: PSO52CLR
 GENERAL DESCRIPTION:   This agreement gives the Clinical Reminders package
 APIs for extracting data from the Prescription (#52) file.  
  STATUS: Pending
COMPONENT/ENTRY POINT: STAT(PSO)
 COMPONENT DESCRIPTION:   Return Status (#100) external format from
 Prescription (#52) file 
VARIABLES: PSO                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal value of the STATUS (#100) field 
COMPONENT/ENTRY POINT: NEPSRX()
 COMPONENT DESCRIPTION:   Return total count of fills, refills and partials of
 Released Rxs.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 5189                            IA #: 5189
  FILE NUMBER: 58.81                    GLOBAL ROOT: PSD(58.81,
  DATE CREATED: APR 24, 2008            CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY
  USAGE: Private                        TYPE: File
  NAME: READ 58.81 FOR SELECTING PATN TRANS FOR WDDE
  ID: PSD(58.81,
 GENERAL DESCRIPTION:   Inpatient Pharmacy requests read access to the DRUG
 ACCOUNTABILITY file #58.81 for selecting records by Patient by Date for
 inclusion in WDDE reporting.  
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: FEB 03, 2009

NUMBER: 5190                            IA #: 5190
  FILE NUMBER: 120.85                   GLOBAL ROOT: GMR(120.85,
  DATE CREATED: APR 24, 2008
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: File
  NAME: READ 120.85 FOR WDDE TO GET HL7 INFO
  ID: GMR(120.85,
 GENERAL DESCRIPTION:   WDDE requests read access to the ADVERSE REACTION
 REPORTING file #120.85 for the purpose of collecting key allergy information
 to populate the Inpatient Medication Order Request, AL1 HL7 segment, for
 transmission to the Ward dispensing equipment.  
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: FEB 03, 2009

NUMBER: 5191                            IA #: 5191
  FILE NUMBER: 9999999.14               GLOBAL ROOT: AUTTIMM(
  DATE CREATED: APR 28, 2008
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Mapping Validation for Immunization Standardization
  ID: AUTTIMM(
GLOBAL REFERENCE: AUTTIMM(IEN,0)
FIELD NUMBER: ALL                       FIELD NAME: ALL FIELDS
  ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   Loop through each entry and use FileMan to query the
 fields needed for Mapping Validation.  
 GENERAL DESCRIPTION:   This agreement permits Health Data & Informatics (HDI)
 read access, using FileMan, to the Immunization file (#9999999.14).  
  
 With the standardization of the Immunization file it is necessary for HDI to
 monitor the local mapping of the term/concepts in this file.  
  STATUS: Active
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS
  DATE ACTIVATED: MAY 01, 2008

NUMBER: 5192                            IA #: 5192
  FILE NUMBER: 9999999.28               GLOBAL ROOT: AUTTSK(
  DATE CREATED: APR 28, 2008
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Mapping Validation for Skin Test Standardization
  ID: AUTTSK(
GLOBAL REFERENCE: AUTTSK(IEN,0)
FIELD NUMBER: ALL                       FIELD NAME: ALL FIELDS
  ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   Loop through each entry and use FileMan to query the
 fields needed for Mapping Validation.  
 GENERAL DESCRIPTION:   This agreement permits Health Data & Informatics (HDI)
 read access, using FileMan, to the Skin Test file (#9999999.28).  
  
 With the standardization of the Skin Test file it is necessary for HDI to
 monitor the local mapping of the term/concepts in this file.  
  STATUS: Active
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS
  DATE ACTIVATED: MAY 01, 2008

NUMBER: 5193                            IA #: 5193
  FILE NUMBER: 811.1                    GLOBAL ROOT: PXD(811.1
  DATE CREATED: APR 28, 2008
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Mapping Validation for PCE Code Mapping
  ID: PXD(811.1
GLOBAL REFERENCE: PXD(811.1,IEN,0)
FIELD NUMBER: ALL                       FIELD NAME: ALL FIELDS
  ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   Loop through each entry and use FileMan to query the
 fields needed for Mapping Validation.  
 GENERAL DESCRIPTION:   This agreement permits Health Data & Informatics (HDI)
 read access, using FileMan, to the PCE Code Mapping file (#811.1).  
  
 With the standardization of the Immunization and Skin Test files it is 
 necessary for HDI to monitor the local mapping of the term/concepts in this
 file.  
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS
  DATE ACTIVATED: MAY 01, 2008

NUMBER: 5194                            IA #: 5194
  DATE CREATED: MAY 07, 2008            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGRPD                        NAME: Recall Reminder Change to DGRPD
  ORIGINAL NUMBER: 5194                 ID: DGRPD
 GENERAL DESCRIPTION:   I have been asked to rewrite Visn 20 clinic recall
 class III application to move to class I application called Recall Reminder
 with an namespace of SDRR. One of the changes is a call from routine DGRPD at
 RMK+2 - the call is: 
  
 D ^SDRRSEG3 ;Display Recall Reminder data for patient 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: RECALL
COMPONENT/ENTRY POINT: RMK+2
 COMPONENT DESCRIPTION:   line added at RMK+2 to call SDRRSEG3 - this will show
 Recall information for patient inquiry.  
VARIABLES: DFN                          TYPE: Output
 VARIABLES DESCRIPTION:   DFN is needed for displaying current active Recall
 Reminder entries within global SD(403.5.  

NUMBER: 5195                            IA #: 5195
  DATE CREATED: MAY 07, 2008            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDRROR
  NAME: Recall Reminder Display         ORIGINAL NUMBER: 5194
  ID: SDRROR
 GENERAL DESCRIPTION:   These changes are required to show Recall Reminder
 information on the Cover sheet for all CPRS users. This is a view only NO
 input done.  
  
 ORWCV.INT VST+22          ;***ADD CHANGES TO CALL COVER^SDRROR VST+23         
 D COVER^SDRROR DTLVST+14   I $P(APPTINFO,";")="R" D RCDTL^SDRROR 
  
 making two calls to SDRROR 
  
 SDRR is a new namespace being used to move a Class III application (Clinic
 Recall) to a National Class I application called Reminder Recall (SDRR
 NAMESPACE).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RECALL
COMPONENT/ENTRY POINT: COVER
VARIABLES: BEG                          TYPE: Used
VARIABLES: END                          TYPE: Used
VARIABLES: DFN                          TYPE: Used
COMPONENT/ENTRY POINT: RCDTL
 COMPONENT DESCRIPTION:   The RCDTL subroutine returns details of the Recall
 Reminder. Things such as when a letter will be sent, fasting, and comments. As
 an example, CPRS uses this for display purposes.  
VARIABLES: APPTINFO                     TYPE: Input
 VARIABLES DESCRIPTION:   While the APPTINFO variable isn't expressly passed as
 a parameter into the call, it is assumed to be defined. RCDTL uses this
 variable to access the RECALL REMINDERS file (#403.5).  
VARIABLES: RPT                          TYPE: Output
 VARIABLES DESCRIPTION:   The RPT array is used to returned the recall reminder
 details.  
  
 RPT(1) = "The patient will be sent a letter prior to this date reminding them
 to make an" RPT(2) = "appointment with the listed clinic." RPT(3) = "  " 
 RPT(4) = If the FASTING/NON-FASTING field (#2.6) has a value, then this entry
 will be: "Patient should be "_FASTING/NON-FASTING field (#2.6) contents.  
 RPT(4) = If the FASTING/NON-FASTING field (#2.6) has no value, then this entry
 will be "Comment: "_COMMENT field (#2.5) RPT(5) = If the FASTING/NON-FASTING
 field (#2.6) has no value, then this entry will be undefined.  RPT(5) = If the
 FASTING/NON-FASTING field (#2.6) has a value, then this entry will be:
 "Comment: "_COMMENT field (#2.5) 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   RECALL REMINDER MODULE 
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VPS is using COVER^SDRROR for VPS 1*15 AVS integration
 to display recall reminder appointments to the patient.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   Project EPIP is using the COVER^SDERROR while reading
 through the ^TMP global created and extract a recall date for future patient
 appointments. This is for EPIP project's patch GMTS*2.7*124.  
  DATE ACTIVATED: OCT 02, 2019

NUMBER: 5196                            IA #: 5196
  FILE NUMBER: 100                      GLOBAL ROOT: OR 
  DATE CREATED: JAN 21, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: DBIA-5196                       ID: OR 
GLOBAL REFERENCE: OR(100,D0,0
FIELD NUMBER: 12                        FIELD NAME: PACKAGE
  LOCATION: 0;14                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the package creating the order.  
FIELD NUMBER: 22                        FIELD NAME: STOP DATE
  LOCATION: 0;9                         ACCESS: Write w/Fileman
FIELD NUMBER: .01                       FIELD NAME: ORDER #
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the internal order number of the file.  
GLOBAL REFERENCE: OR(100,D0,3
FIELD NUMBER: 31                        FIELD NAME: DATE OF LAST ACTIVITY
  LOCATION: 3;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the date/time the order was last updated.  
FIELD NUMBER: 5                         FIELD NAME: STATUS
  LOCATION: 3;3                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the status of the order.  
GLOBAL REFERENCE: OR(100,D0,4
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.  
GLOBAL REFERENCE: OR(100,D0,4.5,D1
FIELD NUMBER: .02                       FIELD NAME: DIALOG
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is a pointer to the dialog prompt, which is in the
 Order Dialog file as type prompt.  
FIELD NUMBER: .01                       FIELD NAME: ITEM ENTRY
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the internal entry number of the prompt in the
 Item multiple by which this response was obtained.  
FIELD NUMBER: .03                       FIELD NAME: INSTANCE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   In the case of multiple answers for the same item, this
 identifies the individual instance.  
FIELD NUMBER: .04                       FIELD NAME: ID 
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field assigns a free text identifier to this
 response value, for quick access to certain values in this order.  
FIELD NUMBER: 1                         FIELD NAME: VALUE
  LOCATION: 1                           ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This contains the actual response, unless the value is a
 word processing type.  
GLOBAL REFERENCE: OR(100,D0,6
FIELD NUMBER: 65                        FIELD NAME: DC REASON TEXT
  LOCATION: 6;5                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the text of the DC reason.  
GLOBAL REFERENCE: OR(100,D0,8,0
FIELD NUMBER: .8                        FIELD NAME: ORDER ACTIONS
  LOCATION: 8;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   These are the actions taken on this order, including the
 signature and verification required to release to the service.  
 GENERAL DESCRIPTION:   This is the file of orders/requisitions made for any
 package through the Order Entry Option (OR).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   Software that handles incoming Lab and Radiology
 messages from DoD needs to access the Order file (100) to store DoD
 originating orders and accessions into the VistA database as if they had been
 issued on the VA side.  

NUMBER: 5197                            IA #: 5197
  DATE CREATED: MAY 08, 2008            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOQ0496
  NAME: TIU CALLS TO PSOQ0496           ID: PSOQ0496
 GENERAL DESCRIPTION:   TIU requests approval to make the following call to
 PSOQ0496.  
  
  STATUS: Active
KEYWORDS: PSOQ0496
KEYWORDS: TIU
COMPONENT/ENTRY POINT: OCL
 COMPONENT DESCRIPTION:   Called to return a list of meds.  
                 
                OCL^PSOQ0496(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.  
  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  DATE ACTIVATED: MAY 08, 2008

NUMBER: 5198                            IA #: 5198
  DATE CREATED: MAY 13, 2008            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS DIVISION GET
  REMOTE PROCEDURE: XUS DIVISION GET
 GENERAL DESCRIPTION:   This DBIA authorizes Imaging to access the remote
 procedure call XUS DIVISION GET.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   Added 9/27/19 
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 5/13/25 effective with YS*5.01*236 patch. Cloud
 application MHA is migrating from VistALink to Cocytus, to communicate with
 VistA. In order to continue to have login functionality with Cocytus, MHA 
 requires use of this RPC.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 3/23/26, effective with DSIY*1.4*0 released
 2/8/19 APAR granted approval based on the historic usage.  
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 3/23/26, effective with DSSO*2.0 released 4/16/20 
 APAT granted approval based on the historic usage.  
  DATE ACTIVATED: MAY 20, 2008

NUMBER: 5199                            IA #: 5199
  DATE CREATED: MAY 13, 2008            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS DIVISION SET
  REMOTE PROCEDURE: XUS DIVISION SET
 GENERAL DESCRIPTION:   This DBIA authorizes Imaging to access the remote
 procedure call XUS DIVISION SET.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   Added 9/27/19 
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   Added 12/17/20 as a temporary resolution until VIA is
 able to deploy the permanent, long term fix.  
SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM
 SUBSCRIBING DETAILS:   In order for the Blind Rehabilitation application to
 continue to have login functionality once the Vista Integration Adapter (VIA)
 is retired, ANRV requires use of this remote procedure call (RPC). Patch
 ANRV*5.1*1 will allow Blind Rehabilitation to communicate with this RPC.  
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 5/13/25 effective with YS*5.01*236 patch. Cloud
 application MHA is migrating from VistALink to Cocytus, to communicate with
 VistA. In order to continue to have login functionality with Cocytus, MHA 
 requires use of this RPC.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 3/23/26, effective with DSIY*1.4*0 released
 2/8/19 APAR granted approval based on the historic usage.  
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 3/23/26, effective with DSSO*2.0 released 4/16/20 
 APAT granted approval based on the historic usage.  
  DATE ACTIVATED: MAY 20, 2008

NUMBER: 5200                            IA #: 5200
  FILE NUMBER: 702                      GLOBAL ROOT: DD(
  DATE CREATED: MAY 14, 2008            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: REMOVE 'CREATED BY' IDENTIFIER IN FILE 702
  ID: DD(
GLOBAL REFERENCE: DD(702,0,ID,.03)
 GENERAL DESCRIPTION:   This DBIA documents the removal of an identifier in the 
 CP Transaction file (#702) for the CREATED BY field (#.03) with a "K
 ^DD(702,0,ID,.03)" command in a post-init routine.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  DATE ACTIVATED: JUL 22, 2008

NUMBER: 5201                            IA #: 5201
  DATE CREATED: MAY 19, 2008            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Private                        TYPE: Routine
  ROUTINE: PSJDSS                       NAME: REBUILD IV EXTRACT FOR DSS
  ID: PSJDSS
 GENERAL DESCRIPTION:   This routine will recreate the IV extract for DSS.  DSS
 wil call this PSJ routine as needed.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This is the entry point to recreate the IV extract
 for DSS.  
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 5202                            IA #: 5202
  DATE CREATED: MAY 19, 2008
  CUSTODIAL PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  USAGE: Private                        TYPE: Routine
  ROUTINE: ECXUTL6                      NAME: DBIA5202
  ID: ECXUTL6
 GENERAL DESCRIPTION:   This API returns the value fields from the DSS LOINC
 CODES (#727.29) file. The DSS LOINC CODES (#727.29) file holds the list of
 reportable LOINC Codes desired by the Decision Support System.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LOINC
 COMPONENT DESCRIPTION:   Entry point to return desired DSS LOINC code and
 associated values from DSS LOINC CODES (#727.29) file.  
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   ARRAY is an array containing the requesting codes of
 the DSS LOINC CODES (#727.29) file.  
VARIABLES: TMP($J,"ECXUTL6",loinc-ck    TYPE: Output
 VARIABLES DESCRIPTION:   
      Output 
         ^TMP($J,"EXCUTL6",LOINC-CK)  = 
                    zero node of file 727.29 pieces 1 thru 4 
                    piece 1 := LOINC-CK (LOINC-check digit) 
                    piece 2 := DSS lar test number 
                    piece 3 := DSS test name 
                    piece 4 := DSS Reporting units 
                    piece 5 := LOINC name 
                    piece 6 := pointer to LAB LOINC (#95.3) code entry 
                   (delimited by "^") 
                -1 := not a valid loinc entry from file 727.29 
                -2 := no dss lar test number associated with loinc 
  
 Examples: >S ARRAY("718-7")="" >S ARRAY("719-8")="" 
  
 >D LOINC^ECXUTL6(.ARRAY) 
  
 >D ^%G 
  
 Device:      Right margin: 80=> 
  
 Global ^TMP($J -- NOTE: translation in effect 
 ^TMP(545452483,"ECXUTL6","718-7")=718-7^1^Hemoglobin^G/DL^Hgb Bld-mCnc^718 
                          "719-8")=-1^no entry in DSS LOINC CODE (#727.29).  
  
 >S ARRAY("ALL")="" >D LOINC^ECXUTL6(.ARRAY) 
  
 >D ^%G 
  
 Global ^TMP($J -- NOTE: translation in effect 
 ^TMP(545452483,"ECXUTL6","10535-3")=10535-3^7^Digoxin^NG/ML^Digoxin 
                   SerPl-mCnc^10535 
                          "10839-9")=10839-9^59^Troponin I^NG/ML^Troponin 
                   I SerPl-mCnc^10839 
                          "10900-9")=10900-9^33^Hepatitis B Surface 
                   Antibody^NEG- POS NON-REACTIVE-REACTIVE ^HBV surface 
                   Ab Ser Ql EIA^10900 
                          "11011-4")=11011-4^37^HCV Quantitative by 
                    PCR^IU/ML^HCV RNA SerPl PCR-a-Cnc^11011 
                          "11218-5")=11218-5^32^Microalbumin (Random 
                    Point)^MG/DL^Microalbumin Ur Qn Test Str^11218 
                          "11259-9")=11259-9^39^HCV Qualitative by 
                    PCR^NEG-POS^HCV RNA SerPl Ql PCR^11259 
                          "11556-8")=11556-8^69^PO2^MM HG^pO2 Bld Qn^11556 
                          "11557-6")=11557-6^70^PCO2^MM HG^pCO2 Bld 
                    Qn^11557 
                          "11579-0")=11579-0^24^Thyroid Stimulating 
                    Hormone (TSH) ^MCU/ML^TSH SerPl DL=0.01 mU/L-aCnc^11579 
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   This API will be used by the DSS LAR RESULTS EXTRACT to
 filter out the the Laboratory results for the DSS desired LOINC Codes. 

NUMBER: 5203                            IA #: 5203
  DATE CREATED: MAY 22, 2008
  CUSTODIAL PACKAGE: HEALTH DATA & INFORMATICS
  USAGE: Supported                      TYPE: Routine
  ROUTINE: HDISVF06                     NAME: Get HDIS Status Text
  ID: HDISVF06
 GENERAL DESCRIPTION:   The $$GETCTXT^HDISVF06 API is used to get the Status
 Text for the Status by Status Type and Status Code.  
  
 The $$GETTEXT^HDISVF06 API is used to get the Status Text for the Status by
 IEN.  
  STATUS: Pending
KEYWORDS: DATA STANDARDIZATION
COMPONENT/ENTRY POINT: $$GETCTXT(HDISCODE,HDISTYPE,.HDISTEXT)
 COMPONENT DESCRIPTION:   Get Status Text for the Status by Status Type and
 Status Code 
  
 Example: 
  
  N HDISTEXT 
  W $$GETCTXT^HDISVF06(6,,.HDISTEXT) W !,$G(HDISTEXT) 
  
  1 
  VUID IMPLEMENTATION COMPLETED 
VARIABLES: HDISCODE                     TYPE: Input
 VARIABLES DESCRIPTION:   Status Code 
VARIABLES: HDISTYPE                     TYPE: Input
 VARIABLES DESCRIPTION:   Status Type (Optional- Default 1=Client) 
VARIABLES: HDISTEXT                     TYPE: Output
 VARIABLES DESCRIPTION:   Status Text 
VARIABLES: $$GETCTXT                    TYPE: Output
 VARIABLES DESCRIPTION:   1=Successful and 0=Failure 
COMPONENT/ENTRY POINT: $$GETTEXT(HDISSIEN,.HDISTEXT)
 COMPONENT DESCRIPTION:   Get the Status Text for the Status by IEN 
  
  
 Example: 
  
  N HDISTEXT 
  W $$GETTEXT^HDISVF06(5,.HDISTEXT) W !,$G(HDISTEXT) 
  
  1 
  AWAITING ERT UPDATE 
VARIABLES: HDISSIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   HDIS Status file IEN 
VARIABLES: HDISTEXT                     TYPE: Output
 VARIABLES DESCRIPTION:   Status Text 
VARIABLES: $$GETTEXT                    TYPE: Output
 VARIABLES DESCRIPTION:   1=Successful and 0=Failure 

NUMBER: 5204                            IA #: 5204
  DATE CREATED: MAY 28, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  ROUTINE: IBCNRE4                      NAME: DBIA5204
  ID: IBCNRE4
 GENERAL DESCRIPTION:   IB grants permission to ECME to call the routine
 IBCNRE4 to provide access to the Edit PLAN APPLICATION Sub-file option through
 the ECME User Screen. This option is locked with the IBCNR E-PHARMACY
 SUPERVISOR security key.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: IBCNRE4
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
 SUBSCRIBING DETAILS:   The BPS PRTCL IBCNR EDIT PLAN action Protocol will call
 IBCNRE4 to provide a jump menu option to the Edit PLAN APPLICATION Sub-file
 option in IB from the ECME User Screen.  

NUMBER: 5205                            IA #: 5205
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: MAY 29, 2008            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  CUSTODIAL ISC: Birmingham             USAGE: Private
  TYPE: File                            NAME: PLACER ORDER # FOR CPRS
  ID: PSRX(
GLOBAL REFERENCE: PSRX(
FIELD NUMBER: 39.3                      FIELD NAME: PLACER ORDER #
  LOCATION: OR1;2                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the corresponding internal entry number from the
 ORDER (#100) File for this prescription.  
 GENERAL DESCRIPTION:   This agreement gives the Computerized Patient Record
 System (CPRS) package access in patch OR*3*281 to directly read the PLACER
 ORDER # (#39.3) Field of the PRESCRIPTION (#52) File for a one-time clean-up.
 After the patch is released, this Integration Agreement will be retired.  
  STATUS: Expired                       DURATION: Next Version
  GOOD ONLY FOR VERSION: OR 3 P31
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JUN 16, 2008
REMINDER: AUG 16, 2008

NUMBER: 5206                            IA #: 5206
  FILE NUMBER: 778                      GLOBAL ROOT: HLB
  DATE CREATED: JUN 03, 2008            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HLO MESSAGES (#778) file access
  ID: HLB
GLOBAL REFERENCE: HLB(
FIELD NUMBER: .04                       FIELD NAME: DIRECTION
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   
  Is the message INCOMING or OUTGOING? 
FIELD NUMBER: .07
  FIELD NAME: APPLICATION ACKNOWLEDGMENT BY
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   
  If this message has received an application response then 
  enter the responses Message Control ID.  
FIELD NUMBER: .16                       FIELD NAME: TRANSMISSION DATE/TIME
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   
  This is the date and time that the message was either 
  received or sent.  
FIELD NUMBER: .2                        FIELD NAME: COMPLETION STATUS
  LOCATION: 0;20                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   
  This field indicates the final status of the message.  
GLOBAL REFERENCE: HLB("B"
FIELD NUMBER: .01                       FIELD NAME: MESSAGE ID
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   
  We are looking at the "B" cross-reference to get the IEN 
  for ACK messages.  
 GENERAL DESCRIPTION:   
  Master Patient Index Austin is providing a PSIM messaging rate 
  monitor for the MPI development team on the MPI Austin production 
  account.  We are looping on ^HLB(, the HLO MESSAGES (#778) file, 
  and getting the following 4 pieces of information: 
    .04       DIRECTION (RS), [0;4] 
    .07       APPLICATION ACKNOWLEDGMENT BY (F), [0;7] 
    .16       TRANSMISSION DATE/TIME (D), [0;16] 
    .2        COMPLETION STATUS (S), [0;20] 
    
  We are also looking at the "B" cross-reference to get the IEN 
  for ACK messages.  
   
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HLO
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
  DATE ACTIVATED: JUL 25, 2008

NUMBER: 5207                            IA #: 5207
  DATE CREATED: JUN 05, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  ROUTINE: IBCNRPMT                     NAME: DBIA5207
  ID: IBCNRPMT
 GENERAL DESCRIPTION:   IB grants permission to ECME to call the routine
 EN^IBCNRPMT to provide access to the Match Group Plan to a Pharmacy Plan
 option through the ECME User Screen. This option is locked with the IBCNR
 E-PHARMACY SUPERVISOR security key.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: IBCNRPMT
COMPONENT/ENTRY POINT: EN
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
 SUBSCRIBING DETAILS:   The BPS PRTCL IBCNR PLAN MATCH action Protocol will
 call EN^IBCNRPMT to provide a jump menu option to the Match Group Plan to a
 Pharmacy Plan option in IB from the ECME User Screen.  

NUMBER: 5208                            IA #: 5208
  DATE CREATED: JUN 05, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  ROUTINE: IBCNRPM1                     NAME: DBIA5208
  ID: IBCNRPM1
 GENERAL DESCRIPTION:   IB grants permission to ECME to call the routine
 EN^IBCNRPM1 to provide access to the Match Multiple Group Plans to a Pharmacy
 Plan option through the ECME User Screen. This option is locked with the IBCNR
 E-PHARMACY SUPERVISOR security key.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: IBCNRPM1
COMPONENT/ENTRY POINT: EN
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
 SUBSCRIBING DETAILS:   The BPS PRTCL IBCNR GROUP PLAN MATCH action Protocol
 will call EN^IBCNRPM1 to provide a jump menu option to the Match Multiple
 Group Plans to a Pharmacy Plan option in IB from the ECME User Screen.  

NUMBER: 5209                            IA #: 5209
  DATE CREATED: JUN 05, 2008
  CUSTODIAL PACKAGE: HEALTH DATA & INFORMATICS
  USAGE: Supported                      TYPE: Other
  NAME: HDISVLM MAPPING TOOL
 GENERAL DESCRIPTION:   This event point is used to post before/after record
 mapping values whenever the STS Generic Mapping Tool changes the mapping of a
 record during the release process when implementing a new standardized domain. 
  
 The following nodes will be posted: 
  
 ^TMP("HDISVLM MAPPING TOOL",$J,<file#>,"BEFORE",<record ien>,"REPLACED 
 BY")=<value of field 99.97> 
  
 ^TMP("HDISVLM MAPPING TOOL",$J,<file#>,"BEFORE",<record ien>,"INHERITS 
 FROM")=$$RPLCMNT^XTIDTRM(<file#>,<record ien>) 
  
  
 ^TMP("HDISVLM MAPPING TOOL",$J,<file#>,"AFTER",<record ien>,"REPLACED 
 BY")=<value of field 99.97> 
  
 ^TMP("HDISVLM MAPPING TOOL",$J,<file#>,"AFTER",<record ien>,"INHERITS 
 FROM")=$$RPLCMNT^XTIDTRM(<file#>,<record ien>) 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: EVENT

NUMBER: 5210                            IA #: 5210
  DATE CREATED: JUN 06, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: IB DRUGS NON COVERED REPORT
 GENERAL DESCRIPTION:   Allows the E CLAIMS MGMT ENGINE package to use IB DRUGS
 NON COVERED REPORT menu option (Drugs non covered report) in its menu.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IB
KEYWORDS: ECME
COMPONENT/ENTRY POINT: IB DRUGS NON COVERED REPORT
 COMPONENT DESCRIPTION:   IB menu option IB DRUGS NON COVERED REPORT 
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: JUN 10, 2008

NUMBER: 5211                            IA #: 5211
  DATE CREATED: JUN 10, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBUCLET                      NAME: FBUCLET for FBCS (DSS)
  ID: FBUCLET                           STATUS: Retired
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$PARAM(FBUC)
 COMPONENT DESCRIPTION:   check if letter should be printed, check if parameter
 is set to print automatically, if so, check if printer is defined, if so ok to
 print 
VARIABLES: FBUC                         TYPE: Input
 VARIABLES DESCRIPTION:   FBUC = UC node (unauthorized claim node) of parameter
 file 
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   1 if ok to print letter, 0 if not ok 
COMPONENT/ENTRY POINT: AUTO(FBDA,FBORDER,FBUCA,FBUC)
 COMPONENT DESCRIPTION:   auto print - called by update routine, tasked job 
VARIABLES: FBDA                         TYPE: Input
 VARIABLES DESCRIPTION:   ien of unauthorized claim, file 162.7 
VARIABLES: FBORDER                      TYPE: Input
 VARIABLES DESCRIPTION:   (optional) order number of status 
VARIABLES: FBUCA                        TYPE: Input
 VARIABLES DESCRIPTION:   current (after) zero node of unauthorized claim
 (162.7) 
VARIABLES: FBUC                         TYPE: Input
 VARIABLES DESCRIPTION:   unauthorized claim node in parameter file 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5212                            IA #: 5212
  DATE CREATED: JUN 10, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBCHFR                       NAME: FBCHFR for FBCS (DSS)
  ID: FBCHFR                            STATUS: Retired
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$RRL(FBIENS)
 COMPONENT DESCRIPTION:   Remittance Remarks List Extrinsic Function 
VARIABLES: FBIENS                       TYPE: Input
 VARIABLES DESCRIPTION:   required, internal entry number for file 162.5 
VARIABLES: FBRET                        TYPE: Output
 VARIABLES DESCRIPTION:   Result 
    string containing sorted list (by external code) of remarks 
     format 
        FBRRMKCE 1, FBRRMKCE 2 
     where 
        FBRRMKCE = remittance remark code (external value) 
COMPONENT/ENTRY POINT: FILERR
 COMPONENT DESCRIPTION:   Used to file remittance remarks 
VARIABLES: FBIENS                       TYPE: Both
 VARIABLES DESCRIPTION:   IEN of file #162.5 (Invoice) 
VARIABLES: FBRRMK                       TYPE: Both
 VARIABLES DESCRIPTION:   FBRRMK -  required, array passed by reference 
             array of remittance remarks to file 
             array does not have to contain any data or be defined 
             format 
                 FBRRMK(#)=FBRRMKC 
               where 
                 # = sequentially assigned number starting with 1 
                 FBRRMKC = remittance remark (internal value file 162.93) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5213                            IA #: 5213
  DATE CREATED: JUN 10, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBFHLL                       NAME: FBFHLL for FBCS (DSS)
  ID: FBFHLL                            STATUS: Retired
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: LOG(FBN,FBTYPE)
 COMPONENT DESCRIPTION:   processes batch and logs 0.00 invoices to FILE #163.5 
VARIABLES: FBN                          TYPE: Input
 VARIABLES DESCRIPTION:   pointer to FEE BASIS BATCH file 
VARIABLES: FBTYPE                       TYPE: Input
 VARIABLES DESCRIPTION:   batch type (B3,B5,B9,BT) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5214                            IA #: 5214
  DATE CREATED: JUN 10, 2008            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PRCS58                       NAME: PRCS58 For FBCS (DSS)
  ID: PRCS58                            STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: EN2
 COMPONENT DESCRIPTION:   POST A TRANSACTION Y=1 IF SUCCESSFUL, +Y=0 WHEN
 FAILED AND Y CONTAINS ERROR MESSAGE 
  
 requires PRCSX=Sta-obl#^int. Date/time^est amt^act amt^reference^comments(up
 to 78 characters)^interface id^complete payment flag PRCS("TYPE")= "FB" or
 "COUNTER" 
VARIABLES: PRCSX                        TYPE: Input
 VARIABLES DESCRIPTION:   Sta-obl#^int. Date/time^est amt^act
 amt^reference^comments(up to 78 characters)^interface id^complete payment flag 
VARIABLES: PRCS                         TYPE: Input
 VARIABLES DESCRIPTION:   PRCS("TYPE") = "FB" or "COUNTER" 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   
 X=FBAAOB_"^"_%_"^^"_FBAAMT_"^"_$S($L(FBAAB)<3:$$PADZ^FBAAV01(FBAAB,4),1:FB 
 AAB)_"^"_FBCOMM_"^"_FBN_"^"_1 
VARIABLES: FBAAOB                       TYPE: Input
 VARIABLES DESCRIPTION:   FULL OBLIGATION NUMBER(STA-CXXXXX) 
VARIABLES: FBAAMT                       TYPE: Input
 VARIABLES DESCRIPTION:   TOTAL AMOUNT OF BATCH 
VARIABLES: FBCOMM                       TYPE: Input
 VARIABLES DESCRIPTION:   COMMENT FOR 1358 
VARIABLES: FBAAB                        TYPE: Input
 VARIABLES DESCRIPTION:   BATCH NUMBER 
VARIABLES: FBN                          TYPE: Input
 VARIABLES DESCRIPTION:   FBN added as 7th peice of 'X'. It is the interface ID 
COMPONENT/ENTRY POINT: EN3
 COMPONENT DESCRIPTION:   TAKE OBLIGATION#, CHECK IF AN OPEN 1358. IF OK Y=1 
VARIABLES: PRCS                         TYPE: Input
 VARIABLES DESCRIPTION:   PRCS("X")=FULL OBLIGATION NUMBER(STA-CXXXXX) 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   IF OK Y=1 (or Y=-1 ;NOT OK) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5215                            IA #: 5215
  DATE CREATED: JUN 11, 2008            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PRCS58CC                     NAME: PRCS58CC for FBCS (DSS)
  ID: PRCS58CC                          STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: PRCS58CC
 COMPONENT DESCRIPTION:   Post payment and close out 1358 when close out flag
 set 
VARIABLES: PRCSX                        TYPE: Input
 VARIABLES DESCRIPTION:   PRCSX=INT DAILY REF #^INTERNAL DATE/TIME^AMT OF 
 PAYMENT^COMMENTS^COMPLETED FLAG^REFERENCE 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Y=1 (OK) OR Y=0^error display 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5216                            IA #: 5216
  DATE CREATED: JUN 11, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAACO4                      NAME: FBAAC04 for FBCS (DSS)
  ID: FBAACO4                           STATUS: Retired
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: FBAACO4
 COMPONENT DESCRIPTION:   ENTER PAYMENT CONTINUED, FEE BASIS VENDOR CORRECTION
 LOOKUP 
VARIABLES: FBDA                         TYPE: Output
 VARIABLES DESCRIPTION:   FBDA=DA 
         **Special note, this variable is leaked from the routine and should be
 carefully checked after calling 
VARIABLES: FBAR                         TYPE: Output
 VARIABLES DESCRIPTION:   FBAR(IEN)=""  SETS AN ARRAY OF VENFORS THAT HAVE
 CORRECTIONS 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   VENDOR IEN 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5217                            IA #: 5217
  DATE CREATED: JUN 11, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAV2                       NAME: FBAAV2 for FBCS (DSS)
  ID: FBAAV2                            STATUS: Retired
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: DETP
 COMPONENT DESCRIPTION:   NOT USED BY FBCS AT THIS TIME, FUTURE ENHANCEMENT 
VARIABLES: FBTYPE                       TYPE: Input
COMPONENT/ENTRY POINT: $$HL7NAME(DFN)
 COMPONENT DESCRIPTION:   RETURNS PATIENT NAME IN HL7 FORMAT 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   PATIENT INTERNAL ENTRY NUMBER IN FILE 2 
VARIABLES: value                        TYPE: Output
 VARIABLES DESCRIPTION:   35 character fixed length string, left justified.  
 Contains formatted patient name using delimiter "|" (e.g., "lastname|firstname
 |m                     ") 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5218                            IA #: 5218
  DATE CREATED: JUN 11, 2008            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCAUTL
  NAME: ACCESS REQUEST TO CALL AR ROUTINE
  ID: PRCAUTL
 GENERAL DESCRIPTION:   The subscriber of this ICR is a Class 3 product in the
 "KPA" package namespace for the Consolidated Patient Account Center (CPAC). 
 The original development effort is an interface between the Stockamp TRAC 
 application and VistA AR.  The TRAC application is a COTS product used for AR
 follow-up and management.  This interface will file AR comments entered into
 the TRAC tool and automatically create AR comment transactions in the AR
 transaction file (File# 433).  
  
 This is a request to be able to call 2 procedures in AR in order to create a
 stub AR transaction entry in file 433.  These 2 procedure calls are very
 common throughout AR and is the normal method to create new entries in file
 433.  
  STATUS: Active
COMPONENT/ENTRY POINT: PATTR
 COMPONENT DESCRIPTION:   This entry point moves data from the FISCAL YEAR
 subfile in file 430 to the FISCAL YEAR subfile in file 433.  
COMPONENT/ENTRY POINT: SETTR
 COMPONENT DESCRIPTION:   This entry point adds a new entry in file 433.  
  DATE ACTIVATED: JUN 30, 2008

NUMBER: 5219                            IA #: 5219
  FILE NUMBER: 430                      GLOBAL ROOT: PRCA(430
  DATE CREATED: JUN 26, 2008            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: KPA ACCESS TO AR FILE 430
  ID: PRCA(430
GLOBAL REFERENCE: PRCA(430,'B',BILL NO.,D0
FIELD NUMBER: .01                       FIELD NAME: BILL NO.
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Using the "B" x-ref to be able to look up the internal
 entry number in file 430 given the external claim# and the station#.  
GLOBAL REFERENCE: PRCA(430,D0,2,0
FIELD NUMBER: 1                         FIELD NAME: FISCAL YEAR
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Performing a $D(^PRCA(430,PRCABN,2,0)) to ensure Fiscal
 Year subfile information exists before being able to process this claim.  
GLOBAL REFERENCE: PRCA(430,D0,0
FIELD NUMBER: 8                         FIELD NAME: CURRENT STATUS
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Checking the CURRENT STATUS field (field# 8) in file 430
 to make sure the claim has not been ARCHIVED before proceeding.  
 GENERAL DESCRIPTION:   The subscriber of this ICR is a Class 3 product in the
 "KPA" package namespace for the Consolidated Patient Account Center (CPAC). 
 The original development effort is an interface between the Stockamp TRAC 
 application and VistA AR.  The TRAC application is a COTS product used for AR
 follow-up and management.  This interface will file AR comments entered into
 the TRAC tool and automatically create AR comment transactions in the AR
 transaction file (File# 433).  
  
 This is a request to be able to reference several fields in file 430 in 
 preparation for being able to file new AR comment transactions in file 433.  
  STATUS: Active                        DATE ACTIVATED: JUN 30, 2008

NUMBER: 5220                            IA #: 5220
  FILE NUMBER: 433                      GLOBAL ROOT: PRCA(433
  DATE CREATED: JUN 26, 2008            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: KPA ACCESS TO AR FILE 433
  ID: PRCA(433
GLOBAL REFERENCE: PRCA(433,D0,0
FIELD NUMBER: .03                       FIELD NAME: BILL NUMBER
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 3                         FIELD NAME: CALM CODE DONE
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 4                         FIELD NAME: TRANSACTION STATUS
  LOCATION: 0;4                         ACCESS: Write w/Fileman
FIELD NUMBER: 42                        FIELD NAME: PROCESSED BY
  LOCATION: 0;9                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: PRCA(433,D0,1
FIELD NUMBER: 11                        FIELD NAME: TRANSACTION DATE
  LOCATION: 1;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 12                        FIELD NAME: TRANSACTION TYPE
  LOCATION: 1;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: TRANS. AMOUNT
  LOCATION: 1;5                         ACCESS: Write w/Fileman
FIELD NUMBER: 19                        FIELD NAME: DATE ENTERED
  LOCATION: 1;9                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PRCA(433,D0,5
FIELD NUMBER: 5.02                      FIELD NAME: BRIEF COMMENT
  LOCATION: 5;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The BRIEF COMMENT field is being hard-coded to be 
    "Acct Management - Interface".  
FIELD NUMBER: 5.03                      FIELD NAME: FOLLOW-UP DATE
  LOCATION: 5;3                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: PRCA(433,D0,7
FIELD NUMBER: 41                        FIELD NAME: COMMENTS
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   (#41) COMMENTS is a WP field.  Data is stored here: 
  
 ^PRCA(433,D0,7,0)=^433.041^^  (#41) COMMENTS ^PRCA(433,D0,7,D1,0)= (#.01)
 COMMENTS [1W] ^ 
GLOBAL REFERENCE: PRCA(433,'C',BILL NUMBER,D0
FIELD NUMBER: .03                       FIELD NAME: BILL NUMBER
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Looping through the "C" x-ref to find all AR transactions
 for a given claim.  
 GENERAL DESCRIPTION:   The subscriber of this ICR is a Class 3 product in the
 "KPA" package namespace for the Consolidated Patient Account Center (CPAC). 
 The original development effort is an interface between the Stockamp TRAC 
 application and VistA AR.  The TRAC application is a COTS product used for AR
 follow-up and management.  This interface will file AR comments entered into
 the TRAC tool and automatically create AR comment transactions in the AR
 transaction file (File# 433).  
  
 This is a request to be able to reference several fields in file 433 and also
 to edit (write) several fields in file 433 to be able to add a new AR comment
 transaction in file 433 using the FILE^DIE FileMan API.  
  STATUS: Active                        DATE ACTIVATED: JUN 30, 2008

NUMBER: 5221                            IA #: 5221
  DATE CREATED: JUL 01, 2008            CUSTODIAL PACKAGE: VISTALINK SECURITY
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.security.CallbackHandlerSwing
 GENERAL DESCRIPTION:   public class CallbackHandlerSwing extends
 java.lang.Object implements javax.security.auth.callback.CallbackHandler.  
  
 Implements the JAAS CallbackHandler interface. Use with the VistaLoginModule
 to invoke a Swing-based interactive logon. Input values (access code, verify
 code, division selection, and other "user input") are collected via a set of
 GUI dialogs when this callback handler is used. To use: 
  
 1. Create an instance of CallbackHandlerSwing. No parameters are needed. 2.
 Create the JAAS LoginContext instance, passing the instance of the callback
 handler as one of the parameters. 3. Invoke the JAAS login context's login
 method. The callback handler will invoke Swing dialogs to collect user input
 wherever required for login.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: constructor
 COMPONENT DESCRIPTION:   CallbackHandlerSwing(java.awt.Frame windowParent):
 Instantiates a JAAS callback handler for Swing applications.  
VARIABLES: windowParent                 TYPE: Input
 VARIABLES DESCRIPTION:   java.awt.Frame windowParent: Allows login dialogs to
 be centered over a parent frame (a top-level window with a title and border)
 and linked for display purposes with the parent application. If null is
 passed, login dialogs are centered based on the screen itself.  
COMPONENT/ENTRY POINT: handle
 COMPONENT DESCRIPTION:   public void
 handle(javax.security.auth.callback.Callback[] arg0) throws 
 javax.security.auth.callback.UnsupportedCallbackException: 
  
 Implementation of handle() method required in JAAS CallbackHandler interface,
 used by JAAS to perform callbacks to retrieve or display information.  
VARIABLES: callbacks                    TYPE: Input
 VARIABLES DESCRIPTION:   javax.security.auth.callback.Callback[] array as
 defined in the javax.security.auth.callback.CallbackHandler interface.  
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   Throws:
 javax.security.auth.callback.UnsupportedCallbackException 
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5222                            IA #: 5222
  DATE CREATED: JUL 01, 2008            CUSTODIAL PACKAGE: VISTALINK SECURITY
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.security.CallbackHandlerSwingCCOW
 GENERAL DESCRIPTION:   public class CallbackHandlerSwingCCOW extends 
 gov.va.med.vistalink.security.CallbackHandlerSwing implements 
 javax.security.auth.callback.CallbackHandler.  
  
 Implements the CallbackHandler JAAS CallbackHandler interface. Use with the
 VistaLoginModule to invoke a Swing-based interactive logon, using the 
 CCOW-enabled features of the VistaLink login module. If user authentication is
 required (if a valid user context does not exist that can be leveraged for
 single signon), input values (access code, verify code, division selection,
 and other "user input") are collected via a set of Swing GUI dialogs by this
 callback handler.  
  
 To login: 
  
 1. Create a CCOW context module and broker. Must be securely bound to the 
 context with a secure application passcode. 2. Create an instance of
 CallbackHandlerSwing, passing the Frame window parent, the context module and
 broker. 3. Create the JAAS LoginContext instance, passing the instance of the 
 callback handler as one of the parameters. 4. Invoke the JAAS login context's
 login method. The callback handler will invoke Swing dialogs to collect user
 input wherever required for login. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: constructor
 COMPONENT DESCRIPTION:   CallbackHandlerSwingCCOW(java.awt.Frame windowParent, 
 gov.va.med.hds.cd.ccow.IContextModule applicationCcowContextModule, 
 gov.va.med.hds.cd.ccow.IClinicalContextBroker applicationCcowContextBroker): 
  
 Creates a callback handler for VistaLink logins, using a SWING interface, and
 using the CCOW-enabled features of VistaLink to provide a CCOW-enabled login.  
VARIABLES: windowParent                 TYPE: Input
 VARIABLES DESCRIPTION:   java.awt.Frame windowParent: Allows login dialogs to
 be centered over a parent frame (a top-level window with a title and border)
 and associated with the parent application for display purposes. If null is
 passed, login dialogs are centered based on the screen itself.  
VARIABLES: appCcowContextModule         TYPE: Input
 VARIABLES DESCRIPTION:   gov.va.med.hds.cd.ccow.IContextModule
 applicationCcowContextModule appCcowContextModule: NOT USED, pass null for
 now. PREVIOUSLY WAS: the application's CCOW context module the login module
 should use to read the CCOW context. Second parameter in method signature.  
VARIABLES: appCcowContextBroker         TYPE: Input
 VARIABLES DESCRIPTION:   gov.va.med.hds.cd.ccow.IClinicalContextBroker
 appCcowContextBroker: the application's CCOW context broker the login module
 should use to read the CCOW context.  
COMPONENT/ENTRY POINT: hasNonNullUserContext
 COMPONENT DESCRIPTION:   public static boolean
 hasNonNullUserContext(java.util.Map contextItems): 
  
 Returns whether the context contains at least one user context item.  
VARIABLES: contextItems                 TYPE: Input
 VARIABLES DESCRIPTION:   java.util.Map contextItems - Map of context items
 representing a context.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   boolean return value: true if the context has at
 least one non-null user context key/value pair.  
COMPONENT/ENTRY POINT: handle
 COMPONENT DESCRIPTION:   public void
 handle(javax.security.auth.callback.Callback[] arg0) throws 
 javax.security.auth.callback.UnsupportedCallbackException: 
  
 Implementation of handle() method required in JAAS CallbackHandler interface,
 used by JAAS to perform callbacks to retrieve or display information.  
VARIABLES: callbacks                    TYPE: Input
 VARIABLES DESCRIPTION:   javax.security.auth.callback.Callback[] array as
 defined in the avax.security.auth.callback.CallbackHandler interface.  
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   Throws: 
 javax.security.auth.callback.UnsupportedCallbackException 
COMPONENT/ENTRY POINT: VHA_CCOW_LOGON_DOMAIN
 COMPONENT DESCRIPTION:   public static java.lang.String: CCOW user context key
 holding the VistA domain name.  
COMPONENT/ENTRY POINT: VHA_CCOW_LOGON_NAME 
 COMPONENT DESCRIPTION:   public static java.lang.String: CCOW user context key
 under which the user name is stored.  
COMPONENT/ENTRY POINT: VHA_CCOW_LOGON_NAME_GENERIC 
 COMPONENT DESCRIPTION:   public static java.lang.String: The non-VA-specific
 generic CCOW user context key under which the user name is stored.  
COMPONENT/ENTRY POINT: VHA_CCOW_LOGON_TOKEN
 COMPONENT DESCRIPTION:   public static java.lang.String: The CCOW user context
 key under which the Kernel token is stored.  
COMPONENT/ENTRY POINT: VHA_CCOW_LOGON_VPID
 COMPONENT DESCRIPTION:   public static java.lang.String: The CCOW user context
 key under which the VPID is stored.  
COMPONENT/ENTRY POINT: VHA_CCOW_USER_CONTEXT_KEYS 
 COMPONENT DESCRIPTION:   public static java.lang.String[]: Array containing
 the complete set of VHA CCOW user context keys.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5223                            IA #: 5223
  DATE CREATED: JUL 01, 2008            CUSTODIAL PACKAGE: VISTALINK SECURITY
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.security.CallbackHandlerUnitTest
 GENERAL DESCRIPTION:   public final class CallbackHandlerUnitTest extends 
 java.lang.Object implements javax.security.auth.callback.CallbackHandler.  
  
 Implements the JAAS CallbackHandler interface. Use with the VistaLoginModule
 to invoke a silent signon. Intended for use in unit testing environments where
 logins must be called repetitively without user interaction. Not for use in
 production environments, where users should be interactively prompted for
 signon credentials.  
  
 To use: 
  
 1. Pass access code, verify code and division as parameters when you create an
 instance of this callback handler.  
  
 2. Pass the instance of the callback handler to the login context when you 
 create the login context. 
  
 3. Then, when VistaLoginModule'slogin method (via the indirection of the 
 LoginContext) invokes this callback handler to collect user input for (access
 code, verify code, select division), these values are already present and are
 handed back to the login module without any user interation. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VistaLink
COMPONENT/ENTRY POINT: constructor 3-arg
 COMPONENT DESCRIPTION:   CallbackHandlerUnitTest(java.lang.String accessCode,
 java.lang.String verifyCode, java.lang.String divisionIen): Creates a simple
 callback handler that handles the callbacks for logon.  
VARIABLES: accessCode                   TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String accessCode: Access Code to use for
 logon.  
VARIABLES: verifyCode                   TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String verifyCode: Verify Code to use for
 logon.  
VARIABLES: divisionIen                  TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String divisionIen: IEN of division to
 select for multidivisional logins. If not needed, pass an empty string.  
COMPONENT/ENTRY POINT: constructor 5-arg
 COMPONENT DESCRIPTION:   CallbackHandlerUnitTest(java.lang.String accessCode,
 java.lang.String oldVerifyCode, java.lang.String divisionIen, java.lang.String 
 newVerifyCode, java.lang.String newVerifyCodeCheck): 
  
 Creates a simple callback handler that handles the callbacks for logon.  Will
 change verify code as part of login.  
VARIABLES: accessCode                   TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String accessCode: Access Code to use for
 logon.  
VARIABLES: oldVerifyCode                TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String oldVerifyCode: Verify Code to use
 for logon.  
VARIABLES: divisionIen                  TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String divisionIen: IEN of division to
 select for multidivisional logins. If not needed, pass an empty string.  
VARIABLES: newVerifyCode                TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String newVerifyCode: new verify code to
 change.  
VARIABLES: newVerifyCodeCheck           TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String newVerifyCodeCheck: should be the
 same as newVerifyCode, to be successful. Used as a check.  
COMPONENT/ENTRY POINT: handle
 COMPONENT DESCRIPTION:   public void
 handle(javax.security.auth.callback.Callback[] arg0) throws 
 javax.security.auth.callback.UnsupportedCallbackException: 
  
 Implementation of handle() method required in JAAS CallbackHandler interface,
 used by JAAS to perform callbacks to retrieve or display information.  
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   Throws:
 javax.security.auth.callback.UnsupportedCallbackException 
VARIABLES: callbacks                    TYPE: Input
 VARIABLES DESCRIPTION:   javax.security.auth.callback.Callback[] array as
 defined in the javax.security.auth.callback.CallbackHandler interface.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5224                            IA #: 5224
  DATE CREATED: JUL 01, 2008            CUSTODIAL PACKAGE: VISTALINK SECURITY
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.security.VistaKernelPrincipalImpl
 GENERAL DESCRIPTION:   public final class VistaKernelPrincipalImpl extends 
 java.lang.Object implements java.io.Serializable, VistaKernelPrincipal 
  
 Implements the gov.va.med.vistalink.security.m.VistaKernelPrincipal interface.
 Represents a JAAS principal representing a logged on Kernel user on an M
 system.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VistaLink
COMPONENT/ENTRY POINT: getAuthenticatedConnection
 COMPONENT DESCRIPTION:   public
 gov.va.med.vistalink.adapter.cci.VistaLinkConnection 
 getAuthenticatedConnection(): Retrieve the authenticated connection from this
 principal after logon.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   return value
 gov.va.med.vistalink.adapter.cci.VistaLinkConnection: the authenticated Vista
 connection, post-successful logon.  
COMPONENT/ENTRY POINT: getKernelPrincipal
 COMPONENT DESCRIPTION:   public static
 gov.va.med.vistalink.security.VistaKernelPrincipalImpl 
 getKernelPrincipal(javax.security.auth.Subject jaasSubject) throws 
 FoundationsException: 
  
 returns the single Kernel principal contained in a JAAS subject returned by a
 JAAS LoginContext after a successful VistaLink logon to Vista.  
VARIABLES: jaasSubject                  TYPE: Input
 VARIABLES DESCRIPTION:   javax.security.auth.Subject jaasSubject:  JAAS
 subject returned by a JAAS LoginContext after a successful VistaLink logon to
 Vista. 
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   return value
 gov.va.med.vistalink.security.VistaKernelPrincipalImpl: 
 VistaKernelPrincipalImpl Kernel principal contained in the JAAS subject.  
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   throws gov.va.med.exception.FoundationsException: If
 no Kernel principal, or more than one, are found, an exception is thrown.  
COMPONENT/ENTRY POINT: getName
 COMPONENT DESCRIPTION:   public java.lang.String getName(): 
  
 get the Principal's full name from the New Person .01 field.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: the user name (from the New
 Person .01 field) of the Principal.  
COMPONENT/ENTRY POINT: getUserDemographicValue
 COMPONENT DESCRIPTION:   public java.lang.String
 getUserDemographicValue(java.lang.String key): returns a given user
 demographic value.  
VARIABLES: key                          TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String key: The key under which the
 demographic value is stored.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: the value of the
 demographic value requested.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5225                            IA #: 5225
  DATE CREATED: JUL 01, 2008            CUSTODIAL PACKAGE: VISTALINK SECURITY
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.security.VistaLoginModule
 GENERAL DESCRIPTION:   public final class VistaLoginModule extends
 java.lang.Object implements javax.security.auth.spi.LoginModule: 
  
 VistaLoginModule is a JAAS-compliant LoginModule to log users on to a Vista
 system. An application never needs to access the VistaLoginModule class
 directly. Rather, as a JAAS login module, its methods are invoked indirectly
 by an application through the JAAS login context class 
 (javax.security.auth.login.LoginContext). 
  
 Client/server applications using VistALink for logins/connections make use of
 VistaLoginModule thru JAAS configuration, by specifying 
 gov.va.med.vistalink.security.VistaLoginModule as the LoginModule class in a
 jaas.config login configuration, and then invoking a JAAS login in application
 code.  
  
 The key classes for invoking a login with this login module are: 
  
 - a callback handler, either CallbackHandlerSwing, CallbackHandlerSwingCCOW,
 or CallbackHandlerUnitTest 
  
 - the login context (javax.security.auth.login.LoginContext) 
  
 - the Kernel principal returned after a successful login 
 (VistaKernelPrincipalImpl) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VistaLink
COMPONENT/ENTRY POINT: SERVER_ADDRESS_KEY
 COMPONENT DESCRIPTION:   public static java.lang.String SERVER_ADDRESS_KEY:
 returns the JAAS configuration key to store/retrieve server IP address.  
COMPONENT/ENTRY POINT: SERVER_ADDRESS_KEY_V1
 COMPONENT DESCRIPTION:   public static java.lang.String SERVER_ADDRESS_KEY_V1:
 returns the JAAS configuration key to store/retrieve server IP address, that
 was used in VistALink v1.0 only.  
COMPONENT/ENTRY POINT: SERVER_PORT_KEY
 COMPONENT DESCRIPTION:   public static java.lang.String SERVER_PORT_KEY:
 returns the JAAS configuration key to store/retrieve server port.  
COMPONENT/ENTRY POINT: SERVER_PORT_KEY_V1
 COMPONENT DESCRIPTION:   public static java.lang.String SERVER_PORT_KEY_V1:
 returns the JAAS configuration key to store/retrieve server port, that was
 used in VistALink v1.0 only.  
COMPONENT/ENTRY POINT: SERVER_SPI_KEY
 COMPONENT DESCRIPTION:   public static java.lang.String SERVER_SPI_KEY:
 returns the JAAS configuration key to select the VistaLoginModuleSPI
 implementation used for providing back-end Kernel login services.  
COMPONENT/ENTRY POINT: login
 COMPONENT DESCRIPTION:   public boolean login() throws
 VistaLoginModuleException, VistaLoginModuleLoginsDisabledException, 
 VistaLoginModuleNoJobSlotsAvailableException, 
 VistaLoginModuleNoPathToListenerException, 
 VistaLoginModuleTooManyInvalidAttemptsException, 
 VistaLoginModuleUserCancelledException, VistaLoginModuleUserTimedOutException: 
  
 Should never be called by an application directly. Instead, this method is
 invoked behind the scenes by the proxy of the JAAS LoginContext. 
  
 However, exceptions thrown by this method can be caught when invoking the 
 login() method of a JAAS login context.  
  
 When an application invokes login() on the LoginContext, the LoginContext 
 calls this method to initiate a login to a VistaLink M server. Once a 
 successful login has occurred, the authenticated connection will be stored in
 the JAAS subject, in a VistaKernelPrincipal. 
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   Throws: 
  
 gov.va.med.vistalink.security.VistaLoginModuleException - a 
 VistaLoginModuleException is thrown if the login for this module fails.  
  
 gov.va.med.vistalink.security.VistaLoginModuleLoginsDisabledException - thrown
 if logins are disabled 
  
 gov.va.med.vistalink.security.VistaLoginModuleNoJobSlotsAvailableException -
 thrown if no job slots are available 
  
 gov.va.med.vistalink.security.VistaLoginModuleNoPathToListenerException - 
 thrown if the specified listener can't be reached 
  
 gov.va.med.vistalink.security.  
 VistaLoginModuleTooManyInvalidAttemptsException - thrown if too many bad login
 attempts are made 
  
 gov.va.med.vistalink.security.VistaLoginModuleUserCancelledException - thrown
 if user cancels the login 
  
 gov.va.med.vistalink.security.VistaLoginModuleUserTimedOutException - thrown
 if user times out of the login 
COMPONENT/ENTRY POINT: logout
 COMPONENT DESCRIPTION:   public boolean logout() throws
 VistaLoginModuleException: 
  
 Should never be called by an application directly. Instead, this method is 
 invoked behind the scenes by the proxy of the JAAS LoginContext. 
  
 However, exceptions thrown by this method can be caught when invoking the 
 logout() method of a JAAS login context.  
  
 For applications to call, to logout a user from an open connection/session to
 a VistaLink M server. Doing this drops the connection, freeing up resources on
 the M server. 
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   Throws: 
  
 gov.va.med.vistalink.security.VistaLoginModuleException - thrown if the logout
 fails on the M side.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5226                            IA #: 5226
  DATE CREATED: JUL 01, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.security.m.VistaKernelPrincipal 
 GENERAL DESCRIPTION:   public interface VistaKernelPrincipal extends
 java.security.Principal 
  
 Provides an interface to marks a principal that represents a logged on Kernel
 user on an M system. Upon a successful JAAS login, one or more principals may
 be contained in the JAAS subject that is returned from a successful JAAS login
 (only one *Kernel* principal should be returned, however. The situation in
 which multiple principals could be returned is if some kind of compound logon
 has been set up that requires several logons to complete, for example one to
 Kernel, and one to a separate health data repository). The
 VistaKernelPrincipal interface is a marker you can use to identify a
 "VistaKernelPrincipal" as one of those principals. However, an easier approach
 is to use the helper method getKernelPrincipal in 
 gov.va.med.vistalink.security.VistaKernelPrincipalImpl to directly retrieve
 the single VistaKernelPrincipal.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VistaLink
COMPONENT/ENTRY POINT: getUserDemographicValue
 COMPONENT DESCRIPTION:   java.lang.String
 getUserDemographicValue(java.lang.String key): Returns a given user
 demographic value. Use the various KEY* field strings defined by this class to
 retrieve various values.  
VARIABLES: key                          TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String key: The key under which the
 demographic value is stored.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   return java.lang.String: String the value of the
 demographic value requested.  
COMPONENT/ENTRY POINT: getName
 COMPONENT DESCRIPTION:   java.lang.String getName(): get the Principal's full
 name from the New Person .01 field.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns value java.lang.String: the user name (from
 the New Person .01 field) of the Principal.  
COMPONENT/ENTRY POINT: KEY_DIVISION_IEN
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_DIVISION_IEN: map
 key to store/retrieve division station IEN from userDemographicsHashTable.  
COMPONENT/ENTRY POINT: KEY_DIVISION_STATION_NAME
 COMPONENT DESCRIPTION:   static final java.lang.String
 KEY_DIVISION_STATION_NAME: map key to store/retrieve division station name
 from userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_DIVISION_STATION_NUMBER
 COMPONENT DESCRIPTION:   static final java.lang.String
 KEY_DIVISION_STATION_NUMBER: map key to store/retrieve division station number
 from userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_DOMAIN_NAME
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_DOMAIN_NAME: map
 key to store/retrieve domain name from userDemographicHashTable 
COMPONENT/ENTRY POINT: KEY_DTIME
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_DTIME: map key to
 store/retrieve user timeout value from userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_DUZ
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_DUZ: map key to
 store/retrieve DUZ from userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_LANGUAGE
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_LANGUAGE: map key
 to store/retrieve user language from userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_NAME_DEGREE
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_NAME_DEGREE: map
 key to store/retrieve degree from userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_NAME_DISPLAY
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_NAME_DISPLAY: map
 key to store/retrieve the display name from userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_NAME_FAMILYLAST
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_NAME_FAMILYLAST:
 map key to store/retrieve name component family-last from
 userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_NAME_GIVENFIRST
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_NAME_GIVENFIRST:
 map key to store/retrieve name component given-first from
 userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_NAME_MIDDLE
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_NAME_MIDDLE: map
 key to store/retrieve name component middle from userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_NAME_NEWPERSON01
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_NAME_NEWPERSON01
 map key to store/retrieve New Person .01 Field name from
 userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_NAME_PREFIX
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_NAME_PREFIX: map
 key to store/retrieve name component prefix from userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_NAME_SUFFIX
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_NAME_SUFFIX map key
 to store/retrieve name component suffix from userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_SERVICE_SECTION
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_SERVICE_SECTION:
 map key to store/retrieve user service/section from userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_TITLE
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_TITLE: map key to
 store/retrieve user title from userDemographicsHashTable 
COMPONENT/ENTRY POINT: KEY_VPID
 COMPONENT DESCRIPTION:   static final java.lang.String KEY_VPID: map key to
 store/retrieve user VPID from userDemographicHashTable 
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5227                            IA #: 5227
  DATE CREATED: JUL 02, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: VistaLinkAppProxyConnectionSpec
 GENERAL DESCRIPTION:   public class 
 gov.va.med.vistalink.adapter.cci.VistaLinkAppProxyConnectionSpec extends 
 gov.va.med.vistalink.adapter.cci.VistaLinkConnectionSpecImpl implements 
 gov.va.med.vistalink.adapter.cci.VistaLinkConnectionSpec, 
 javax.resource.cci.ConnectionSpec.  
  
 This is the connection spec class for Application Proxy re-authentication.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: constructor
 COMPONENT DESCRIPTION:   public
 VistaLinkAppProxyConnectionSpec(java.lang.String division, java.lang.String
 appProxyName) 
VARIABLES: division                     TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String division: The station number (e.g.,
 "523", "523BZ", etc.) requested as the division under which logon/actions
 should be conducted for this user on the target Kernel/M system.  
VARIABLES: appProxyName                 TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String appProxyName: The Application Proxy
 Name identifier for the proxy user.  
COMPONENT/ENTRY POINT: getAppProxyName
 COMPONENT DESCRIPTION:   java.lang.String getAppProxyName() 
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String Application Proxy Name.  
COMPONENT/ENTRY POINT: setAppProxyName
 COMPONENT DESCRIPTION:   public void setAppProxyName(java.lang.String string) 
VARIABLES: name                         TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String name to set the Application Proxy
 Name to.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5228                            IA #: 5228
  DATE CREATED: JUL 02, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.adapter.cci.VistaLinkDuzConnectionSpec
 GENERAL DESCRIPTION:   public class
 gov.va.med.vistalink.adapter.cci.VistaLinkDuzConnectionSpec extends
 gov.va.med.vistalink.adapter.cci.VistaLinkConnectionSpecImpl implements
 gov.va.med.vistalink.adapter.cci.VistaLinkConnectionSpec, 
 javax.resource.cci.ConnectionSpec.  
  
 This is the connection spec class for Duz re-authentication.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: getDuz
 COMPONENT DESCRIPTION:   java.lang.String getDuz() 
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String DUZ.  
COMPONENT/ENTRY POINT: setDuz
 COMPONENT DESCRIPTION:   void setDuz(java.lang.String duz): Sets the DUZ.  
VARIABLES: duz                          TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String duz: DUZ to set the DUZ to for the
 connection spec.  
COMPONENT/ENTRY POINT: constructor
 COMPONENT DESCRIPTION:   public VistaLinkDuzConnectionSpec(java.lang.String
 division, java.lang.String duz): constructor.  
VARIABLES: division                     TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String division: The station number (e.g.,
 "523", "523BZ", etc.) requested as the division under which logon/actions
 should be conducted for this user on the target Kernel/M system.  
VARIABLES: duz                          TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String duz: The DUZ identifier for the end
 user.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5229                            IA #: 5229
  DATE CREATED: JUL 02, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: VistaLinkVpidConnectionSpec
 GENERAL DESCRIPTION:   public class gov.va.med.vistalink.adapter.cci
 VistaLinkVpidConnectionSpec extends
 gov.va.med.vistalink.adapter.cci.VistaLinkConnectionSpecImpl implements
 gov.va.med.vistalink.adapter.cci.VistaLinkConnectionSpec, 
 javax.resource.cci.ConnectionSpec.  
  
 This is the connection spec class for VPID re-authentication. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: constructor
 COMPONENT DESCRIPTION:   public VistaLinkVpidConnectionSpec(java.lang.String
 division, java.lang.String vpid): constructor.  
VARIABLES: division                     TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String division: The station number (e.g.,
 "523", "523BZ", etc.) requested as the division under which logon/actions
 should be conducted for this user on the target Kernel/M system.  
VARIABLES: vpid                         TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String vpid: the VPID identifier for the
 end-user.  
COMPONENT/ENTRY POINT: getVpid
 COMPONENT DESCRIPTION:   public java.lang.String getVpid() 
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: VPID set in the connection
 spec.  
COMPONENT/ENTRY POINT: setVpid
 COMPONENT DESCRIPTION:   public void setVpid(java.lang.String vpid) 
VARIABLES: vpid                         TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String vpid: the VPID to set for this
 connection spec.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5230                            IA #: 5230
  DATE CREATED: JUL 02, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: VistaLinkRequestRetryStrategy
 GENERAL DESCRIPTION:   public interface 
 gov.va.med.vistalink.adapter.record.VistaLinkRequestRetryStrategy 
  
 Base strategy interface for determining if request should be re-executed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: execute
 COMPONENT DESCRIPTION:   boolean execute(VistaLinkRequestVO request):
 Determines if it is ok to retry executing the request after it the failed to
 complete because of a socket error or other system type problem.  
VARIABLES: request                      TYPE: Input
 VARIABLES DESCRIPTION:   
 gov.va.med.vistalink.adapter.record.VistaLinkRequestVO request: 
 VistaLinkRequestVO instance reference for the request.  
COMPONENT/ENTRY POINT: return
 COMPONENT DESCRIPTION:   returns boolean that indicates 1) true == attempt
 retry or 2) false == do not attempt retry.  

NUMBER: 5231                            IA #: 5231
  DATE CREATED: JUL 02, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: VistaLinkRequestRetryStrategyAllow
 GENERAL DESCRIPTION:   public class 
 gov.va.med.vistalink.adapter.record.VistaLinkRequestRetryStrategyAllow 
 implements gov.va.med.vistalink.adapter.record.VistaLinkRequestRetryStrategy.  
  
 Simple 'Allow' strategy implementation that indicates request should be 
 re-executed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: constructor
 COMPONENT DESCRIPTION:   public VistaLinkRequestRetryStrategyAllow():
 constructs an instance; no arguments.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5232                            IA #: 5232
  DATE CREATED: JUL 02, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: VistaLinkRequestRetryStrategyDeny
 GENERAL DESCRIPTION:   public class 
 gov.va.med.vistalink.adapter.record.VistaLinkRequestRetryStrategyDeny 
 implements gov.va.med.vistalink.adapter.record.VistaLinkRequestRetryStrategy.  
  
 Simple 'Deny' strategy implementation that indicates request should not be
 re-executed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: constructor
 COMPONENT DESCRIPTION:   public VistaLinkRequestRetryStrategyDeny(): no-arg
 constructor constructs an instance.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5233                            IA #: 5233
  DATE CREATED: JUL 02, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.adapter.record.VistaLinkRequestVO
 GENERAL DESCRIPTION:   public interface VistaLinkRequestVO: Base request
 interface.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: getTimeOut
 COMPONENT DESCRIPTION:   int getTimeOut(): Returns time out value used for
 communications to M RPC server.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns int: int time out value in milli-seconds.  
COMPONENT/ENTRY POINT: setTimeOut
 COMPONENT DESCRIPTION:   void setTimeOut(int timeOut): Enables application to
 set a request-specific time out for read operations on the connection, for the 
 request. 
VARIABLES: timeout                      TYPE: Input
 VARIABLES DESCRIPTION:   int timeout: Time out value to set in milli-seconds.
 This timeout value is compared to the default value usually used for the
 connection. The greater of the two values will be used.  
  
 A timeout value of 0 (zero) indicates that no specific time out for the 
 request is specified, and that the time out value associated with the socket
 should be used during socket read operations.  
COMPONENT/ENTRY POINT: getRetryStrategy
 COMPONENT DESCRIPTION:   
 gov.va.med.vistalink.adapter.record.VistaLinkRequestRetryStrategy 
 getRetryStrategy(): Returns current retry strategy reference.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   
 gov.va.med.vistalink.adapter.record.VistaLinkRequestRetryStrategy: returns
 retry strategy instance reference.  
COMPONENT/ENTRY POINT: setRetryStrategy
 COMPONENT DESCRIPTION:   void setRetryStrategy( 
 gov.va.med.vistalink.adapter.record.VistaLinkRequestRetryStrategy strategy):
 Enables application to set retry strategy for request, to be used if request
 execution failed because of socket failure or other system type problems. The
 strategy determines if the retry should be attempted. 
VARIABLES: strategy                     TYPE: Input
 VARIABLES DESCRIPTION:   
 gov.va.med.vistalink.adapter.record.VistaLinkRequestRetryStrategy strategy:
 the VistaLinkRequestRetryStrategy instance representing the strategy the
 application wants implemented.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5234                            IA #: 5234
  DATE CREATED: JUL 02, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.adapter.spi.VistaLinkServerInfo
 GENERAL DESCRIPTION:   public class
 gov.va.med.vistalink.adapter.spi.VistaLinkServerInfo extends java.lang.Object: 
  
 Represents M VistA connection information, like address and port.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: getAddress
 COMPONENT DESCRIPTION:   public java.net.InetAddress getAddress(): Gets the
 current IP address associated with an instance.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   java.net.InetAddress getAddress(): Gets the current
 address associated with an instance.  
COMPONENT/ENTRY POINT: getPort
 COMPONENT DESCRIPTION:   public int getPort(): Gets the current port
 associated with an instance.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns int: the current port associated with an
 instance.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5235                            IA #: 5235
  DATE CREATED: JUL 02, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.institution.IPrimaryStationRules
 GENERAL DESCRIPTION:   public interface IPrimaryStationRules: Interface for
 PrimaryStationRules implementations. All implementations must be threadsafe. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: getPrimaryStationLookupString
 COMPONENT DESCRIPTION:   java.lang.String
 getPrimaryStationLookupString(java.lang.String division) throws 
 gov.va.med.vistalink.institution.InstitutionMappingBadStationNumberExcepti on: 
  
 Implement a method that, given a particular 'division' string (i.e., primary
 station plus optional division suffix), returns the primary Station derived
 from that division string. 
  
 The primary station is used for looking up connectors, and would be the 
 'computing facility' for the division in question. 
VARIABLES: division                     TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String division: division (in station #
 format) to derive primary station from.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: the primaryStation value
 derived from the division parameter, to use for connector lookups.  
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   Throws: gov.va.med.vistalink.institution.  
 InstitutionMappingBadStationNumberException: thrown if the division passed in
 is considered invalid.  
COMPONENT/ENTRY POINT: validatePrimaryStation
 COMPONENT DESCRIPTION:   void validatePrimaryStation(java.lang.String
 primaryStation) throws 
 gov.va.med.vistalink.institution.InstitutionMappingBadStationNumberExcepti on: 
  
 Implement a method that validates a particular 'primary station' identifier
 string as valid. Primary stations are used in VistALink to look up a
 connector. Therefore, the format of a valid 'primary station' identifier
 should be such that the entity or system it identifies would have one and only
 one connector associated with it.  
VARIABLES: primaryStation               TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String primaryStation: identifier for a
 'primary station', i.e., 'computing facility' 
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   throws gov.va.med.vistalink.institution.  
 InstitutionMappingBadStationNumberException: thrown if primaryStation param is
 considered an invalid identifier.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5236                            IA #: 5236
  DATE CREATED: JUL 02, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.institution.InstitutionMappingDelegate
 GENERAL DESCRIPTION:   public class 
 gov.va.med.vistalink.institution.InstitutionMappingDelegate extends 
 java.lang.Object: 
  
 Provides methods used by applications to query the institution mapping.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: getJndiConnectorNameForInstitution
 COMPONENT DESCRIPTION:   public static java.lang.String 
 getJndiConnectorNameForInstitution(java.lang.String stationNumber) throws 
 InstitutionMapNotInitializedException, InstitutionMappingNotFoundException: 
  
 Returns the JNDI connector name (if found) for a division matching the station
 number passed in. 
VARIABLES: stationNumber                TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String stationNumber: institution station
 number for Vista Institution to retrieve connector for.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: Jndi Connector name, if a
 connector is found that is mapped to input station number. Use for a JNDI
 lookup of actual VistaLink connector.  
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   Throws: 
  
 gov.va.med.vistalink.institution.InstitutionMapNotInitializedException - 
 thrown if the institution mapping has not been initialized 
  
 gov.va.med.vistalink.institution.InstitutionMappingNotFoundException - thrown
 if no connector JNDI name has been mapped to input station number 
COMPONENT/ENTRY POINT: getVistaLinkMappedStationNumberSet
 COMPONENT DESCRIPTION:   public static java.util.Set
 getVistaLinkMappedStationNumberSet() throws 
 InstitutionMapNotInitializedException: 
  
 Returns the set of station# strings for which adapters have been deployed on
 the current JVM, and for which institution mappings currently exist.  The
 source of the station#s in the mapping is the primaryStation configuration
 attribute, for successfully deployed adapters.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.util.Set: a Set containing station#
 strings contained in current mapping.  
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   throws: 
  
 gov.va.med.vistalink.institution.InstitutionMapNotInitializedException: thrown
 if the institution mapping has not been initialized.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5237                            IA #: 5237
  FILE NUMBER: 8985.1                   GLOBAL ROOT: XTID(8985.1,
  DATE CREATED: JUL 03, 2008            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Deletion of entries in XTID VUID FOR SET OF CODES file
  ID: XTID(8985.1,
 GENERAL DESCRIPTION:   This ICR permits the HDI application to delete entries
 from the XTID VUID FOR SET OF CODES file (#8985.1).  Entries are found using
 the FileMan call FIND^DIC with a screen set to find those entries that match
 the file and field numbers being removed.  Entries are then deleted using the 
 FileMan call ^DIK.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS
  DATE ACTIVATED: SEP 13, 2012

NUMBER: 5238                            IA #: 5238
  DATE CREATED: JUL 03, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.rpc.RpcReferenceType
 GENERAL DESCRIPTION:   public class RpcReferenceType extends java.lang.Object:
 Represents a reference type object for an RPC parameter. Used mainly for 
 RpcRequest.setParams() call to represent a 'reference' type parameter. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: constructor
 COMPONENT DESCRIPTION:   public RpcReferenceType(): default constructor.  
  
 public RpcReferenceType(java.lang.String value): Constructs this instance with
 the specified value.  
VARIABLES: value                        TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String value: Name of variable to be
 referenced, like DUZ (for 1-arg constructor).  
COMPONENT/ENTRY POINT: getValue
 COMPONENT DESCRIPTION:   public java.lang.String getValue(): Returns name of
 the variable desired in the M server partition.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: the name of the variable to
 be referenced in the M server partition.  
COMPONENT/ENTRY POINT: setValue
 COMPONENT DESCRIPTION:   public void setValue(java.lang.String value): Sets
 the value to the name of the variable desired to be referenced in the M server
 partition.  
VARIABLES: value                        TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String value: The value to set.  
COMPONENT/ENTRY POINT: toString
 COMPONENT DESCRIPTION:   public java.lang.String toString(): override of
 default toString method.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: name of the variable
 desired to be referenced in the M server partition.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5239                            IA #: 5239
  DATE CREATED: JUL 03, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.rpc.RpcRequestFactory
 GENERAL DESCRIPTION:   public class RpcRequestFactory extends java.lang.Object
 implements gov.va.med.vistalink.adapter.record.VistaLinkRequestFactory: 
  
 Factory class to creates instances of RpcRequest.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: getRpcRequest
 COMPONENT DESCRIPTION:   public static RpcRequest getRpcRequest() throws
 FoundationsException: Creates a RpcRequest with a null RpcContext and RpcName. 
  
 public static RpcRequest getRpcRequest(java.lang.String rpcContext) throws 
 FoundationsException: Creates a RpcRequest with the specified RpcContext and a
 null RpcName.  
  
 public static RpcRequest getRpcRequest(java.lang.String rpcContext, 
 java.lang.String rpcName) throws FoundationsException: Creates appropriate rpc
 request object to be passed into the connection.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns gov.va.med.vistalink.rpc.RpcRequest: an
 RpcRequest with a null RpcContext and RpcName.  
VARIABLES: rpcContext                   TYPE: Input
 VARIABLES DESCRIPTION:   (optional 1st parameter) java.lang.String rpcContext:
 name of RPC context to execute RPC(s) under with this request.  
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   Throws gov.va.med.exception.FoundationsException:
 currently in method signature to maintain backwards compatibility, but the
 exception is not actually thrown.  
VARIABLES: rpcName                      TYPE: Input
 VARIABLES DESCRIPTION:   (optional second parameter) java.lang.String rpcName:
 name of the RPC to execute with this request.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5240                            IA #: 5240
  DATE CREATED: JUL 03, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.rpc.RpcRequestParams
 GENERAL DESCRIPTION:   public class RpcRequestParams extends java.lang.Object:
 Represents the collection of parameters associated with an RPC.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: clear
 COMPONENT DESCRIPTION:   public void clear(): Clears the parameters. 
COMPONENT/ENTRY POINT: getParam
 COMPONENT DESCRIPTION:   public java.lang.Object getParam(int position): Gets
 the value for a parameter associated with a specified position in the
 parameters collection. Normally, this method is not used by the client. 
VARIABLES: position                     TYPE: Input
 VARIABLES DESCRIPTION:   int position: parameter position the M RPC expects
 this parameter.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.Object: Object String or Map. A
 return value of null indicates that there is no parameter for the position.  
COMPONENT/ENTRY POINT: setParam
 COMPONENT DESCRIPTION:   public void setParam(int position, java.lang.String
 type, java.lang.Object value): Sets a parameter needed by for a M RPC call.  
VARIABLES: position                     TYPE: Input
 VARIABLES DESCRIPTION:   int position: parameter position the M RPC expects
 this parameter.  
VARIABLES: type                         TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String type: type of parameter
 corresponding to valid M RPC types 
VARIABLES: value                        TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.Object value: value of the parameter.
 Possible values are the following: 
  
 string (corresponds to 'Literal' in VA RPC Broker) array (corresponds to
 'List' in VA RPC Broker) ref (corresponds to 'Reference' in VA RPC Broker) 
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5241                            IA #: 5241
  DATE CREATED: JUL 03, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.rpc.RpcResponse
 GENERAL DESCRIPTION:   public class RpcResponse extends 
 gov.va.med.vistalink.adapter.record.VistaLinkResponseVOImpl.  
  
 Represents a data structure which holds the response value(s).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: getResultsDocument
 COMPONENT DESCRIPTION:   public org.w3c.dom.Document getResultsDocument()
 throws RpcResponseTypeIsNotXmlException, FoundationsException: 
  
 Gets an XML Document format based on the contains of the results returned by
 the RPC. Note: This XML document is created during the call to this method and
 not as part of the creation of the RpcResponse object.  
  
 If calling application wants to use this method, it should use generic xml DOM
 interfaces from org.w3c.dom.* package. 
  
 Alternatively if application wants to use this document in a specific XML 
 parser implementation, parser should be able to create a specific Document
 implementation from org.w3c.dom.Document interface. In this case it might be
 better from performance standpiont to use getResults() and parse xml string
 directly.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns org.w3c.dom.Document 
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   Throws 
  
 gov.va.med.vistalink.rpc.RpcResponseTypeIsNotXmlException: results type must
 be 'xml' 
  
 gov.va.med.exception.FoundationsException: thrown if problem generating xml
 DOM document from results string.  
COMPONENT/ENTRY POINT: getResults
 COMPONENT DESCRIPTION:   public java.lang.String getResults(): Gets the
 results string for the returned data in this response.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: results string for the
 returned data in this response.  
COMPONENT/ENTRY POINT: getResultsType
 COMPONENT DESCRIPTION:   public java.lang.String getResultsType(): gets the
 return type of the results sent back from the M VistAServer. The possible
 types are 'string' or 'array'. 
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: return type of the results
 sent back from the M VistAServer, either 'string' or 'array'.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5242                            IA #: 5242
  DATE CREATED: JUL 03, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: gov.va.med.vistalink.rpc.RpcRequest
 GENERAL DESCRIPTION:   public class gov.va.med.vistalink.rpc.RpcRequest
 extends gov.va.med.vistalink.adapter.record.VistaLinkRequestVOImpl.  
  
 Represents a RPC request to an M VistA server. 
  
 This is the principal class for use by developers to create and setup requests
 to the host M server. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: buildMultipleMSubscriptKey
 COMPONENT DESCRIPTION:   public static java.lang.String
 buildMultipleMSubscriptKey(java.lang.String keyValue): Builds and returns
 string that contains the following: an indicator that the value represents a
 multiple M subscript structure the actual multiple M subscript structure
 string value.  
VARIABLES: keyValue                     TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String keyValue: Value representing the
 multiple M subscript structure.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: flagged key value to be
 used as HashMap key.  
COMPONENT/ENTRY POINT: getParams
 COMPONENT DESCRIPTION:   public gov.va.med.vistalink.rpc.RpcRequestParams
 getParams(): Gets the reference to the RpcRequestParamsobject associated with
 this request. This object contains the parameters sent with the call to the
 RPC during the getResponse() call. Use this object to set these parameters
 before calling getResponse().  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns gov.va.med.vistalink.rpc.RpcRequestParams
 containing the parameters to send with the request.  
COMPONENT/ENTRY POINT: setParams
 COMPONENT DESCRIPTION:   public void setParams(java.util.List list): Sets all
 the parameters for a RPC call at once using a List. 
VARIABLES: list                         TYPE: Input
 VARIABLES DESCRIPTION:   java.util.List list: list of parameters for the RPC
 call.  
COMPONENT/ENTRY POINT: clearParams
 COMPONENT DESCRIPTION:   public void clearParams(): Clears the params
 associated with this instance of RpcRequest 
COMPONENT/ENTRY POINT: getRpcName
 COMPONENT DESCRIPTION:   public java.lang.String getRpcName(): Gets the name
 of the RPC. 
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: name of the RPC associated
 with the request.  
COMPONENT/ENTRY POINT: setRpcName
 COMPONENT DESCRIPTION:   public void setRpcName(java.lang.String value): Sets
 the name of the RPC to be called on the M server. The name must be a valid RPC
 name as it appears in the REMOTE PROCEDURE (#8994) file in M VistA. 
VARIABLES: value                        TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String value: name of the RPC to be called
 on the M server. The name must be a valid RPC name as it appears in the REMOTE
 PROCEDURE (#8994) file in M VistA. 
COMPONENT/ENTRY POINT: getRpcContext
 COMPONENT DESCRIPTION:   public java.lang.String getRpcContext(): Gets the
 name of the RPC Context.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String name of the RPC context
 associated with the request.  
COMPONENT/ENTRY POINT: setRpcContext
 COMPONENT DESCRIPTION:   public void setRpcContext(java.lang.String value):
 Sets the name of the RPC Context to be used. The name must be a valid B- type
 OPTION name as it appears in the OPTION (#19) file in M VistA. 
VARIABLES: value                        TYPE: Input
 VARIABLES DESCRIPTION:   java.lang.String value: the name of the RPC Context
 to be used. The name must be a valid B- type OPTION name as it appears in the
 OPTION (#19) file in M VistA.  
COMPONENT/ENTRY POINT: getRpcClientTimeOut
 COMPONENT DESCRIPTION:   public int getRpcClientTimeOut(): Gets the current
 client time out value. (Value is returned in the number of seconds). 
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns int: the current client time out value.
 (Value is returned in the number of seconds). 
COMPONENT/ENTRY POINT: setRpcClientTimeOut
 COMPONENT DESCRIPTION:   public void setRpcClientTimeOut(int value): Sets the
 client time out value. (Value is expected in seconds.) 
VARIABLES: value                        TYPE: Input
 VARIABLES DESCRIPTION:   int value: client time out value. (Value is expected
 in seconds.) 
COMPONENT/ENTRY POINT: getRpcVersion
 COMPONENT DESCRIPTION:   public double getRpcVersion(): Gets the current RPC
 version specified by application.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns double: the rpcVersion specified in the
 request.  
COMPONENT/ENTRY POINT: setRpcVersion
 COMPONENT DESCRIPTION:   public void setRpcVersion(double value): Sets the RPC
 version number Note: Like parameters, it is up to the application code to set
 this property appropriately for each RPC request made using the RpcRequest
 instance. To unset to default, set property to 0 (zero). 
VARIABLES: value                        TYPE: Input
 VARIABLES DESCRIPTION:   double value: the RPC version number. Note: Like
 parameters, it is up to the application code to set this property
 appropriately for each RPC request made using the RpcRequest instance. To
 unset to default, set property to 0 (zero). 
COMPONENT/ENTRY POINT: getRequestString
 COMPONENT DESCRIPTION:   public java.lang.String getRequestString() throws
 FoundationsException: Gets the proprietary request string 
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String: returns the proprietary or
 xml (depending on setting) request string to be sent to the M server.  
VARIABLES: throws                       TYPE: Output
 VARIABLES DESCRIPTION:   throws 
  
 gov.va.med.exception.FoundationsException: thrown if a failure is encountered
 creating request string from the request.  
COMPONENT/ENTRY POINT: isXmlResponse
 COMPONENT DESCRIPTION:   public boolean isXmlResponse(): Indicates whether the
 returned value from the RPC call is expected in XML format or not. 
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   returns boolean: true or false depending on whether
 request has been set with indicator that result is expected in XML format.  
COMPONENT/ENTRY POINT: setXmlResponse
 COMPONENT DESCRIPTION:   public void setXmlResponse(boolean value): Sets
 request indicator that the returned value from the RPC call is expected in XML
 format or not.  
VARIABLES: value                        TYPE: Input
 VARIABLES DESCRIPTION:   boolean value: Whether XML is the expected type of
 result to be returned.  
COMPONENT/ENTRY POINT: setUseProprietaryMessageFormat
 COMPONENT DESCRIPTION:   public void setUseProprietaryMessageFormat(boolean
 useSink): Set the indicator that the RPC request should be sent to the M
 server in a proprietary format (true) or in XML format (false). 
VARIABLES: useSink                      TYPE: Input
 VARIABLES DESCRIPTION:   boolean useSink: the RPC request should be sent to
 the M server in a proprietary format (true) or in XML format (false). 
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5243                            IA #: 5243
  DATE CREATED: JUL 09, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: vljConnector Exceptions
 GENERAL DESCRIPTION:   Exceptions that can be thrown from public methods of
 classes distributed in vljConnector jar.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: gov.va.med.vistalink.adapter.cci.VistaLinkResourceExcepti
on
 COMPONENT DESCRIPTION:   public class VistaLinkResourceException extends 
 javax.resource.ResourceException implements 
 gov.va.med.exception.FoundationsExceptionInterface.  
  
 Represents a ResourceException thrown by the VistaLink adapter.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.adapter.record.LoginsDisabledFaultEx
ception
 COMPONENT DESCRIPTION:   public class LoginsDisabledFaultException extends 
 gov.va.med.vistalink.adapter.record.VistaLinkFaultException.  
  
 This exception represents the case where the M side has logins disabled; this
 is when the site sets the parameter to not allow any logins.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.adapter.record.NoJobSlotsAvailableFa
ultException
 COMPONENT DESCRIPTION:   public class NoJobSlotsAvailableFaultException
 extends gov.va.med.vistalink.adapter.record.VistaLinkFaultException.  
  
 This exception represents the case where on the M side there are no license
 slots available to start another process.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.adapter.record.VistaLinkFaultExcepti
on
 COMPONENT DESCRIPTION:   public class VistaLinkFaultException extends 
 gov.va.med.exception.FoundationsException.  
  
 Exception encapsulates Fault information coming from M side. M side can pass
 bak to Java error condition in the system Fault message. If this condition
 happens, VLJ creates VistaLinkFaultException and populates it's properties
 with data from the Fault message.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.adapter.spi.ConnectionHandlesExceede
dException
 COMPONENT DESCRIPTION:   public class ConnectionHandlesExceededException
 extends gov.va.med.vistalink.adapter.cci.VistaLinkResourceException.  
  
 This exception class is thrown when a VistaLinkManagedConnection object has
 exceeded its maximum allowable connection handles.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.adapter.spi.VistaLinkSocketAlreadyCl
osedException
 COMPONENT DESCRIPTION:   public class VistaLinkSocketAlreadyClosedException
 extends gov.va.med.net.VistaSocketException.  
  
 Represents a situation where, when attempting to close a socket, the socket is
 already closed.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.adapter.spi.VistaLinkSocketClosedExc
eption
 COMPONENT DESCRIPTION:   public class VistaLinkSocketClosedException extends 
 gov.va.med.vistalink.adapter.cci.VistaLinkResourceException.  
  
 This exception class is thrown when an attempt is made to access the 
 VistaLinkManagedConnection's underlying VistaSocketConnection after its has
 been closed or invalidated.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.institution.InstitutionMapNotInitial
izedException
 COMPONENT DESCRIPTION:   public class InstitutionMapNotInitializedException
 extends gov.va.med.exception.FoundationsException.  
  
 Represents an attempt to access some functionality of the InstitutionMapping
 instance when that instance has not been created.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.institution.InstitutionMappingBadSta
tionNumberException
 COMPONENT DESCRIPTION:   public class
 InstitutionMappingBadStationNumberException extends java.lang.Exception.  
  
 Represents a failure to create one or more institution mappings because of one
 or more bad station#s on which the mapping was to be based.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.rpc.NoRpcContextFaultException
 COMPONENT DESCRIPTION:   public class NoRpcContextFaultException extends 
 gov.va.med.vistalink.rpcRpcFaultException.  
  
 This exception represents the case where the request RPC context does not 
 exist or the current user does not have access to the B-option representing
 the context.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.rpc.RpcFaultException
 COMPONENT DESCRIPTION:   public class RpcFaultException extends 
 gov.va.med.vistalink.adapter.record.VistaLinkFaultException.  
  
 This fault exception class is used for all rpc-related errors returned from
 the M system.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.rpc.RpcNotInContextFaultException
 COMPONENT DESCRIPTION:   public class RpcNotInContextFaultException extends 
 gov.va.med.vistalink.rpc.RpcFaultException.  
  
 This exception represents the case where the requested RPC is not contained in
 the current RPC context.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.rpc.RpcNotOkForProxyUseException
 COMPONENT DESCRIPTION:   public class RpcNotOkForProxyUseException extends 
 gov.va.med.vistalink.rpcRpcFaultException.  
  
 This exception represents the case where the requested RPC is not marked as OK
 for use by an application proxy user, but has been attempted to be invoked by
 one.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.rpc.RpcResponseTypeIsNotXmlException
 COMPONENT DESCRIPTION:   public class RpcResponseTypeIsNotXmlException extends 
 gov.va.med.exception.FoundationsException.  
  
 Represents an exception indicating the RpcResponse type if not XML.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.rpc.RpcTimeOutFaultException
 COMPONENT DESCRIPTION:   public class RpcTimeOutFaultException extends 
 gov.va.med.vistalink.rpc.RpcFaultException.  
  
 This exception represents the case where the RPC execution took too long on
 the server and the application gracefully stopped the RPC's processing.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.m.SecurityAccessVerifyCodeP
airInvalidException
 COMPONENT DESCRIPTION:   public class
 SecurityAccessVerifyCodePairInvalidException extends 
 gov.va.med.vistalink.security.m.SecurityFaultException.  
  
 Represents an authentication failure during an access/verify code-based 
 re-authentication attempt, where either the access code, verify code (or both)
 authentication credentials are invalid.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.m.SecurityConnectionProxyEx
ception
 COMPONENT DESCRIPTION:   public final class SecurityConnectionProxyException
 extends gov.va.med.vistalink.security.m.SecurityFaultException.  
  
 This exception fault is returned from M, and signifies that the connection 
 proxy used to create the connection was invalid in some way, and a connection
 could not be established to the EIS.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.m.SecurityDivisionDetermina
tionFaultException
 COMPONENT DESCRIPTION:   public class
 SecurityDivisionDeterminationFaultException extends 
 gov.va.med.vistalink.security.m.SecurityFaultException.  
  
 Represents an authentication failure during a re-authentication attempt, in
 which an invalid division has been passed for the user on whose behalf 
 re-authentication is being attempted. The user does not have access to the 
 requested division.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.m.SecurityFaultException
 COMPONENT DESCRIPTION:   public class SecurityFaultException extends 
 gov.va.med.vistalink.adapter.record.VistaLinkFaultException.  
  
 This fault exception class is used for all security-related errors returned
 from the M system. It represents an error that happened on the M system, that
 VistaLink does not provide a specific java exception for.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.m.SecurityIdentityDetermina
tionFaultException
 COMPONENT DESCRIPTION:   public class
 SecurityIdentityDeterminationFaultException extends 
 gov.va.med.vistalink.security.m.SecurityFaultException.  
  
 Represents an authentication failure during a re-authentication attempt, in
 which the credentials passed for re-authentication (DUZ, VPID, etc.) could not
 be matched with an actual Kernel user.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.m.SecurityIPLockedFaultExce
ption
 COMPONENT DESCRIPTION:   public final class SecurityIPLockedFaultException
 extends gov.va.med.vistalink.security.m.SecurityFaultException.  
  
 This exception fault is returned from M, and signifies that the IP address has
 been locked due to too many invalid logins.user's login credentials were
 invalid too many times, and the M system is rejecting further login attempts
 as a result.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.m.SecurityPrimaryStationMis
matchException
 COMPONENT DESCRIPTION:   public final class
 SecurityPrimaryStationMismatchException extends 
 gov.va.med.vistalink.security.m.SecurityFaultException.  
  
 This exception fault is returned from M, and signifies that there was a 
 mismatch between the client primary station (mapped to the connector) and the
 primary station of the M account the connector accessed (based on the value of
 the DEFAULT INSTITUTION field of the Kernel System Parameters file).  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.m.SecurityProductionMismatc
hException
 COMPONENT DESCRIPTION:   public final class
 SecurityProductionMismatchException extends 
 gov.va.med.vistalink.security.m.SecurityFaultException.  
  
 This exception fault is returned from M, and signifies that there was a 
 mismatch between the client and the server in the designation of each side as
 production or non-production.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.m.SecurityTooManyInvalidLog
inAttemptsFaultException
 COMPONENT DESCRIPTION:   public final class
 SecurityTooManyInvalidLoginAttemptsFaultException extends
 gov.va.med.vistalink.security.m.SecurityFaultException.  
  
 This exception fault is returned from M, and signifies that the user's login
 credentials were invalid too many times, and the M system is rejecting further
 login attempts as a result. 
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.m.SecurityUserAuthorization
Exception
 COMPONENT DESCRIPTION:   public class SecurityUserAuthorizationException
 extends gov.va.med.vistalink.security.m.SecurityFaultException.  
  
 Represents an authorization failure during a re-authentication attempt, e.g.,
 DISUSER flag is set for the re-authentication user, prohibited times of day is
 set, etc.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.m.SecurityUserVerifyCodeExc
eption
 COMPONENT DESCRIPTION:   public class SecurityUserVerifyCodeException extends 
 gov.va.med.vistalink.security.m.SecurityFaultException.  
  
 Represents a failure during a re-authentication attempt, where the user's 
 verify code is expired or requires changing.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.institution.InstitutionMappingNotFou
ndException
 COMPONENT DESCRIPTION:   public class InstitutionMappingNotFoundException
 extends gov.va.med.exception.FoundationsException.  
  
 Represents a failure to retrieve an institution mapping based on station 
 number, due to requested station number not being found in the list of 
 instituion mappings maintained by the InstitutionMapping instance. 
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5244                            IA #: 5244
  DATE CREATED: JUL 09, 2008            CUSTODIAL PACKAGE: VISTALINK SECURITY
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: vljSecurity  Exceptions
 GENERAL DESCRIPTION:   Exceptions that can be thrown from public methods of
 classes distributed in vljSecurity jar.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.VistaLoginModuleException
 COMPONENT DESCRIPTION:   public class VistaLoginModuleException extends 
 javax.security.auth.login.LoginException implements 
 gov.va.med.exception.FoundationsExceptionInterface.  
  
 Represents a LoginException thrown by the VistaLoginModule. 
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.VistaLoginModuleIPLockedExc
eption
 COMPONENT DESCRIPTION:   If thrown, the user's IP has been locked due to too
 many times with invalid credentials. When attempting a logon, you can trap for
 this specific exception, in addition to the more general 
 VistaLoginModuleException and LoginException exceptions.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.VistaLoginModuleLoginsDisab
ledException
 COMPONENT DESCRIPTION:   public final class
 VistaLoginModuleLoginsDisabledException extends VistaLoginModuleException.  
  
 If thrown, logins are disabled on the M server. When attempting a logon, you
 can trap for this specific exception, in addition to the more general 
 VistaLoginModuleException and LoginException exceptions.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.VistaLoginModuleNoJobSlotsA
vailableException
 COMPONENT DESCRIPTION:   public final class
 VistaLoginModuleNoJobSlotsAvailableException extends 
 VistaLoginModuleException.  
  
 If thrown, job slot maximum has been exceeded on M server. When attempting a
 logon, you can trap for this specific exception, in addition to the more 
 general VistaLoginModuleException and LoginExceptionexceptions.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.VistaLoginModuleNoPathToLis
tenerException
 COMPONENT DESCRIPTION:   public final class
 VistaLoginModuleNoPathToListenerException extends VistaLoginModuleException.  
  
 If thrown, no reachable listener was found on the path represented by the 
 specified IP address and Port. When attempting a logon, you can trap for this
 specific exception, in addition to the more general VistaLoginModuleException
 and LoginException exceptions.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.VistaLoginModuleTooManyInva
lidAttemptsException
 COMPONENT DESCRIPTION:   public final class
 VistaLoginModuleTooManyInvalidAttemptsException extends
 VistaLoginModuleException.  
  
 If thrown, the user tried to login too many times with invalid credentials.
 When attempting a logon, you can trap for this specific exception, in addition
 to the more general VistaLoginModuleException and LoginException exceptions.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.VistaLoginModuleUserCancell
edException
 COMPONENT DESCRIPTION:   public final class
 VistaLoginModuleUserCancelledException extends VistaLoginModuleException.  
  
 Represents a user cancellation of Login. When attempting a logon, you can trap
 for this specific exception, in to the more general VistaLoginModuleException
 and LoginException exceptions.  
COMPONENT/ENTRY POINT: gov.va.med.vistalink.security.VistaLoginModuleUserTimedOu
tException
 COMPONENT DESCRIPTION:   User timed out of a login. When attempting a logon,
 you can trap for this specific exception, in addition to the more general 
 VistaLoginModuleException and LoginException exceptions.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5245                            IA #: 5245
  DATE CREATED: JUL 09, 2008            CUSTODIAL PACKAGE: FOUNDATIONS
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: vljFoundationsLib Exceptions
 GENERAL DESCRIPTION:   Exceptions that can be thrown from public methods of
 classes distributed in vljFoundationsLib jar.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: gov.va.med.crypto.VistaKernelHashCountLimitExceededExcept
ion
 COMPONENT DESCRIPTION:   public class
 VistaKernelHashCountLimitExceededException extends 
 gov.va.med.exception.FoundationsException.  
  
 Represents an exception identifying that the Hash Count Limit (for a call to
 the VistaKernelHash encrypt method) has been exceeded. In this case, the hash
 algorithm could not return an encrypted hash within a certain number of tries,
 that was free of CDATA boundary character strings ("&lt;![CDATA[" and
 "]]&gt;").  
COMPONENT/ENTRY POINT: gov.va.med.exception.FoundationsException
 COMPONENT DESCRIPTION:   public class FoundationsException extends Exception
 implements FoundationsExceptionInterface.  
  
 FoundationsException provides adds nested exception functionality to standard
 exceptions. This functionality is no longer necessary starting in Java 1.4,
 whose java.lang.Throwable class introduces built-in support for nested
 exceptions. However, for backwards compatibility, VistALink exceptions still
 inherit from this class.  
COMPONENT/ENTRY POINT: gov.va.med.net.VistaSocketException
 COMPONENT DESCRIPTION:   public class VistaSocketException extends
 FoundationsException.  
  
 Represents an exception thrown during read/write operations on a socket.  
COMPONENT/ENTRY POINT: gov.va.med.net.VistaSocketTimeOutException
 COMPONENT DESCRIPTION:   public class VistaSocketTimeOutException extends
 VistaSocketException.  
  
 Represents an exception identifying a timeout has occurred during read/write
 operations.  
  DATE ACTIVATED: JUL 11, 2008

NUMBER: 5246                            IA #: 5246
  FILE NUMBER: 142.5                    GLOBAL ROOT: GMT(142.5,
  DATE CREATED: JUL 29, 2008            CUSTODIAL PACKAGE: HEALTH SUMMARY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ AND WRITE OF FILE 142.5
  ID: GMT(142.5,
GLOBAL REFERENCE: GMT(142.5,DA,
FIELD NUMBER: .03                       FIELD NAME: Health Summary Type
  LOCATION: 0;3                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This field stored a pointer to the Health Summary Type
 entry in file# 142.  
  
 GENERAL DESCRIPTION:   This ICR will allow the Clinical Reminder Package to
 read and write from file # 142.5. This is needed to support the functionality
 to transport Health Summary Objects in the Reminder Exchange tool.  
  
 This ICR will allow the Clinical Reminders package to do direct reads on the 
 fields listed below and to do a write using FileMan to the entire global for 
 file 142.5.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMTS
KEYWORDS: 142.5
KEYWORDS: PXRM
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: OCT 02, 2013

NUMBER: 5247                            IA #: 5247
  FILE NUMBER: 142                      GLOBAL ROOT: GMT(142,
  DATE CREATED: JUL 29, 2008            CUSTODIAL PACKAGE: HEALTH SUMMARY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ AND WRITE OF FILE 142
  ID: GMT(142,
GLOBAL REFERENCE: GMT(142,DA(1),1,DA,
FIELD NUMBER: 1                         FIELD NAME: COMPONENT NAME
  LOCATION: 1;2                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This field store a pointer to the Health Summary
 Component associated with the Health Summary Type.  
  
GLOBAL REFERENCE: GMT(142,DA
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: GMT(142,DA(2),1,DA(1),DA,
FIELD NUMBER: .01                       FIELD NAME: SELECTION ITEM
  LOCATION: 4;1                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This field stores a variable pointer to the entry for a
 list of specific files that the Health Summary Type will use to search for
 patient data.  
  
 GENERAL DESCRIPTION:   This ICR will allow the Clinical Reminder Package to
 read and write from file # 142. This is needed to support the functionality to
 transport Health Summary Types in the Reminder Exchange tool.  
  
 This ICR will allow the Clinical Reminders package to do direct reads on the 
 fields listed below and to do a write using FileMan to the entire global for 
 file 142.  
  
  STATUS: Active
KEYWORDS: GMTS
KEYWORDS: 142
KEYWORDS: PXRM
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: OCT 02, 2013
INTEGRATION REFERENCES Redacted List as of 20261106
                                                     NOV 09, 2026@17:23   PAGE 4
--------------------------------------------------------------------------------


NUMBER: 5248                            IA #: 5248
  FILE NUMBER: 142.1                    GLOBAL ROOT: GMT(142.1,
  DATE CREATED: JUL 29, 2008            CUSTODIAL PACKAGE: HEALTH SUMMARY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: FILEMAN READ FROM THE HEALTH SUMMARY COMPONENT FILE
  ID: GMT(142.1,
GLOBAL REFERENCE: GMT(142.1,DA,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This ICR will allow the subscribing packages to do a
 FileMan read on file# 142.1.  
  
  STATUS: Active
KEYWORDS: GMT
KEYWORDS: 142.1
KEYWORDS: PXRM
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 5249                            IA #: 5249
  DATE CREATED: JUL 29, 2008
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ AND WRITE TO FILE 8925.1
 GENERAL DESCRIPTION:   This ICR will allow the Clinical Reminder Package to
 read and write from file # 8925.1. This is needed to support the functionality
 to transport TIU Objects in the Reminder Exchange tool.  
  
 This ICR will allow the Clinical Reminders package to do direct reads on the 
 fields listed below and to do a write using.  
  
  STATUS: Active
KEYWORDS: TIU
KEYWORDS: 8925.1
KEYWORDS: PXRM
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: OCT 30, 2013

NUMBER: 5250                            IA #: 5250
  DATE CREATED: AUG 01, 2008            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SCAPMC
  NAME: PCMM CALLS FOR MYHEALTHEVET - SCAPMC
  ID: SCAPMC
 GENERAL DESCRIPTION:   Allows MyHealthEVet to call exisiting API's that are
 not supported references.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SCAPMC
KEYWORDS: MYHEALTHEVET
KEYWORDS: SCHEDULING
COMPONENT/ENTRY POINT: CLPT
 COMPONENT DESCRIPTION:   Returns Clinics for a patient 
COMPONENT/ENTRY POINT: PTCL
 COMPONENT DESCRIPTION:   Returns patients for a Clinic 
COMPONENT/ENTRY POINT: TPPR
 COMPONENT DESCRIPTION:   Returns roles for teams 
SUBSCRIBING PACKAGE: MYHEALTHEVET
  DATE ACTIVATED: SEP 15, 2008

NUMBER: 5251                            IA #: 5251
  DATE CREATED: AUG 05, 2008            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MPIHLO2
  NAME: Use of Routine MPIHLO2          ID: MPIHLO2
 GENERAL DESCRIPTION:   
  Master Patient Index (Austin) is requesting permission from the 
  HL7 developers to establish a private, temporary IA to use routine 
  MPIHLO2.  This HL7 routine was provided by the HL7 developers, to 
  be installed as MPIHLO2 on the Master Patient Index (Austin).  
  The routine will be directly removing entries from an existing 
  sequence queue (^HLB("QUEUE","SEQUEUNCE","MPI LKMV") global and 
  placing them on an existing out queue (^HLB("QUEUE","OUT") with 
  the use of the OUTQUE^HLOQUE API (for more details see the routine 
  below).  The code also resets the ^HLC status global as well.  
   
  The need for this request came from the System-of-System (SoS) 
  group to help address the critical backlog of messages on the 
  MPI HLO MPI LKMV sequence queue to PSIM.  The ESR project is 
  scheduled to go live on 8/15/08.  In order to accomplish this, 
  it would require that the MPI HLO queues not have a backlog of 
  messages.  However the current backlog of messages on the MPI 
  will not be finished at the current rate with the current 
  software until 9/20/08.  
   
  The use of routine MPIHLO2 is a temporary measure that will take 
  all of the ADD events that are currently stacked up on one outbound 
  queue (Adds/Links/Moves queue) to PSIM and move them directly to the 
  outbound queue which will allow them to be processed simultaneously 
  in PSIM rather than one at a time.  The implementation will guarantee 
  that the two databases (MPI and ADR) will stay synchronized by 
  shutting down the EVENT sequence queue (Add/Link/Move) until all of 
  the ADD events are sent and successfully processed by PSIM.  Then 
  and only then will we resume normal processing.  
   
  This routine will only be used a few times (at most for only a few 
  months).  After that we plan to retire it for a more permanent 
  solution to address the MPI to PSIM synchronization throughput issue.  
   
  NOTE:  Although routine MPIHLO2 was provided/reviewed by the HL7 
  developers, testing and SQA is the sole responsibility of the 
  Master Patient Index development team.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MPIHLO2
 COMPONENT DESCRIPTION:   
  MPIHLO2 ;IRMFO-ALB/CJM -one time conversion of MPI's sequence 
      queues; 03/24/2004 14:43 ;07/29/2008 
      ;;1.0;MASTER PATIENT INDEX AUSTIN;**73**;30 Apr 99 
      ;
      ;pull record off of MPI LKMV out queue first 
      ;example ^HLB("QUEUE","OUT","VAPSIM:5027","MPI 
      LKMV",586)="" 
      ;example ^HLB("QUEUE","SEQUENCE","MPI LKMV")=586 
      <-- msg=586 has already been moved to the outque, 
      it is the msg that the sequence queue is waiting on 
      ;example ^HLB("QUEUE","SEQUENCE","MPI LKMV",587)="" 
      <-- msg=588 is the next message ont he sequence queue 
      that needs to be moved to the out queue whenthe app 
      ack for msg 587 is received 
      ;
      ;
      N CNT,MPIQ,IEN 
      S CNT=0 
      S MPIQ="MPI LKMV" 
      S IEN="" 
      ;
      F  S IEN=$O(^HLB("QUEUE","SEQUENCE",MPIQ,IEN)) Q:'IEN  D 
      .I $$MOVE(IEN) S CNT=CNT+1 
      ;
      ;decrement the counter for the sequence queues 
      I $$INC^HLOSITE($NA(^HLC("QUEUECOUNT","SEQUENCE")),-CNT) 
      W !,"MOVE COMPLETED. Count of records moved:",CNT 
      Q 
      ;
  MOVE(IEN) ;returns 1 if the msg was moved, 0 if it was not 
      N MOVED,BODY,ICN1,ICN2 
      S MOVED=0 
      ;
      S BODY=$P(^HLB(IEN,0),"^",2) 
      Q:'BODY 0 
      ;
      S ICN1=+$P($G(^HLA(BODY,1,3,0)),"^",4) 
      S ICN2=+$P($G(^HLA(BODY,1,6,0)),"^",4) 
      S:ICN2=0 ICN2=+$P($G(^HLA(BODY,1,7,0)),"^",4) 
      ;add event 
      I ICN1=ICN2 D 
      .N MSG,OLDSEQ,OLDOUT,LINK,PORT,NEWQUE,FS,CS,EVENT 
      .Q:'$$GETMSG^HLOMSG(IEN,.MSG) 
      .S FS=$E(MSG("HDR",1),4) 
      .S CS=$E(MSG("HDR",1),5) 
      .S EVENT=$P($P(MSG("HDR",2),FS,4),CS,2) 
      .S OLDSEQ=$G(MSG("STATUS","SEQUENCE QUEUE")) 
      .;
      .Q:EVENT'="A24" 
      .;
      .S OLDOUT=$G(MSG("STATUS","QUEUE")) 
      .S LINK=$G(MSG("STATUS","LINK NAME")) 
      .S PORT=$G(MSG("STATUS","PORT")) 
      .S NEWQUE="MPI UPD"_$E(+ICN1,$L(+ICN1)-2,$L(+ICN1)) 
      .Q:'$L(NEWQUE) 
      .I NEWQUE'=OLDOUT D 
      ..;update the message to show the new outgoing queue 
      ..S $P(^HLB(IEN,0),"^",6)=NEWQUE 
      .;
      .;remove the msg from the sequence queue 
      .K ^HLB("QUEUE","SEQUENCE",OLDSEQ,IEN) 
      .;
      .;put the msg on the outgoing queue 
      .D OUTQUE^HLOQUE(LINK,PORT,NEWQUE,IEN) 
      .;
      .;node 5 can be killed - it makes it as if a sequence 
      queue was never involved 
      .K ^HLB(IEN,5) 
      .S MOVED=1 
      Q MOVED 
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
  DATE ACTIVATED: MAR 16, 2009
REMINDER: APR 01, 2009

NUMBER: 5252                            IA #: 5252
  DATE CREATED: AUG 08, 2008            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  ROUTINE: LEXASCD                      NAME: Lexicon/VBA APIs
  ID: LEXASCD
 GENERAL DESCRIPTION:   LEXASCD contains APIs for supporting the Automated
 Service Connected Designation (ASCD) project.  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: LEXASCD
KEYWORDS: VBA
KEYWORDS: TITLE 38
KEYWORDS: ASCD
COMPONENT/ENTRY POINT: $$SC(ICD,VBA,EFF,.ARY)
 COMPONENT DESCRIPTION:   This function determines if there is a partial or
 full service connection for an ICD code based on the ICD codes and disability
 codes in the Lexicon.  
  
VARIABLES: ICD                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) ICD-9-CM Diagnosis Code 
  
  
VARIABLES: VBA                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) VA Disability code (Title 38) 
  
  
VARIABLES: EFF                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Effective Date - This is the date that
 service was provided to the patient (aka, encounter date) and is used to check
 to see if the ICD code was mapped to the Disability code on that date.  
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This is a local array, passed by
 reference.  When passed it will return information about the ICD code and 
 Disability codes.  
  
VARIABLES: $$SC                         TYPE: Output
 VARIABLES DESCRIPTION:   If the ICD code is mapped to a VA disability, then
 the return value is a 5 piece "^" delimited string as follows: 
  
  #  Content             Value 
  1  Service Connected   1=Yes 
  2  Connection (Match)  1=Full  0=Partial 
  3  Mapping Status      1=Active 0=Inactive 
  4  ICD Code Status     1=Active 0=Inactive 
  5  Code Status         1=Active 0=Inactive 
  
 If the ICD Code is not mapped to a VA disability, then the return value is a
 negative 2 piece "^" delimited string as follows: 
  
    -1 ^ Not Found or Error Message 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   (Optional) This is a local array passed by reference. 
 If passed it will contain detailed information about the ICD code and
 Disability code.  The local array will contain the following 2 subscripts: 
  
  ARY(1)=<ICD status>^<Date>^<Code>^<Term> 
  ARY(2)=<Disability status>^<Date>^<Code>^<Term> 
  
 Where status is either a 1 (active) or 0 (inactive) and date is the effective
 date the code became either active or inactive.  
  
COMPONENT/ENTRY POINT: $$DI(ICD,EFF,ARY)
 COMPONENT DESCRIPTION:   Return the number of Disability codes an ICD code is
 mapped to.  Optionally return an array of Disability codes an ICD code is
 mapped to in a local array passed by reference.  
  
VARIABLES: ICD                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) ICD-9-CM Code 
  
VARIABLES: EFF                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Effective Date (default TODAY) 
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Local array passed by reference, returns a
 list of Disability codes mapped to the ICD code.  
  
VARIABLES: $$DI                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns the number of Disability codes mapped to an
 ICD code.  
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   (Optional) Local Array of Disability Codes passed by
 reference 
  
  ARY(0) = 5 Piece String detailing input 
           Diagnosis code 
    
   1   Number of Disability Codes found 
   2   ICD Code 
   3   Status of ICD Code  1 = Active 0 = Inactive 
   4   Effective Date of ICD Code Status 
   5   Versioned Text of ICD Code 
  
  ARY(#) = 6 Piece String detailing output 
           Disability codes 
      
   1   Mapping 1 = Full 0 = Partial 
   2   Effective Date of Mapping 
   3   Disability Code 
   4   Status of Disability Code 
   5   Effective Date of Disability Code Status 
   6   Versioned Text of Disability Code 
         
  ARY("B",MAP,#)=""  Index of Local Array 
    
   MAP Mapping 1 = Full 0 = Partial 
   #   Entry Number in Array 
  
  
COMPONENT/ENTRY POINT: $$DX(VBA,EFF,ARY)
 COMPONENT DESCRIPTION:   Return the number of ICD Diagnosis codes a Disability
 code is mapped to.  Optionally return an array of ICD codes a Disability code
 is mapped to in a local array passed by reference.  
  
VARIABLES: VBA                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Disability Code (Title 38) 
  
VARIABLES: EFF                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Effective Date (default TODAY) 
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Local array passed by reference, return a
 list of ICD codes mapped to a Disability code.  
  
VARIABLES: $$DX                         TYPE: Output
 VARIABLES DESCRIPTION:   The number of Diagnosis codes mapped to a Disability
 code.  
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   (Optional) Local Array of Diagnosis Codes passed by
 reference 
  
  ARY(0) = 5 Piece String detailing input 
           Disability code 
    
    1   Number of Diagnosis Codes found 
    2   Disability Code 
    3   Status of Code  1 = Active 0 = Inactive 
    4   Effective Date of Disability Code Status 
    5   Versioned Text of Disability Code 
          
  ARY(#) = 6 Piece String detailing output 
           Diagnosis codes 
    
    1   Mapping 1 = Full 0 = Partial 
    2   Effective Date of Mapping 
    3   ICD-9-CM  Code 
    4   Status of ICD-9-CM Code 
    5   Effective Date of ICD-9-CM Code Status 
    6   Versioned Text of ICD-9-CM Code 
          
  ARY("B",MAP,#)=""  Index of Local Array 
         
    MAP Mapping 1 = Full 0 = Partial 
    #   Entry Number in Array 
  

NUMBER: 5253                            IA #: 5253
  FILE NUMBER: 44                       DATE CREATED: AUG 20, 2008
  CUSTODIAL PACKAGE: SCHEDULING         USAGE: Private
  TYPE: File                            NAME: DBIA5253
 GENERAL DESCRIPTION:   First Draft Request - Need to post developer as to
 request questions and variables to determine correctness - LEC 8/20/08 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING

NUMBER: 5254                            IA #: 5254
  DATE CREATED: AUG 25, 2008            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: FILE 4 ACCESS                   STATUS: Pending
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 5255                            IA #: 5255
  DATE CREATED: AUG 27, 2008            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: PRIVATE ICR FOR CISS TO ACCESS KAAJEE
 GENERAL DESCRIPTION:   
  
  1. Logins are only to be performed by the CISS framework code.  This 
  IA and supporting IAs are granted to CISS only, not to the application 
  portlets/plug-ins running in CISS.  
  
  2. To run user checks and establish user identity for a specific M/VistA 
  system, CISS should do the following: 
  
    a. Instantiate a KaajeeVistaLinkConnectionSpec instance, using 
    user-entered access/verify code and division, and also obtaining the 
    end-user's IP address, e.g., request.getRemoteAddr().  
  
    b. Obtain a VistALink connection to the desired M/VistA system from the 
    appropriate VistaLink connection factory object, using the 
    KaajeeVistaLinkConnectionSpec instance.  
  
    c. Using the connection, run the RPC "XUS KAAJEE GET USER INFO" in the 
    RPC context "XUS SIGNON" to, if successful, get a DUZ back.  
    This also creates the sign-on log entry on the M/VistA system; the DA 
    of that entry is also returned. If an exception is thrown, the user 
    is not authorized to run RPCs on the target VistA system. The exception 
    will contain the reason for denial.  
  
    d. If the end-user is authorized to run RPCs by the preceding step, 
    use the same connection and immediately run the RPC "XUS KAAJEE LOGOUT" 
    under the RPC context "XUS SIGNON", passing the DA of the sign-on log 
    entry created.  Running the RPC marks the sign-on log entry as closed.  
  
    e. Close the connection.  
  
    f. To run application RPCs for the end user, obtain a new connection 
    from the same VistALink connection factory, but using 
    VistaLinkDuzConnectionSpec (or, when supported, 
    VistaLinkVpidConnectionSpec.) 
   
  3. For the duration of the user session, the DUZ may be used with 
  DuzConnectionSpec to run RPCs.  
   
  4. Whether or not CISS caches a user's DUZ, for any new CISS user 
  sessions requiring access to a VistA system, all steps 2a-2f should be 
  performed again, as the user's authorization to log onto the VistA system 
  may have been revoked or otherwise may have changed since the previous 
  session. 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: KAAJEE
COMPONENT/ENTRY POINT: gov.va.med.authentication.kernel.KaajeeVistaLinkConnectio
nSpec
 COMPONENT DESCRIPTION:   
  
  The no-argument constructor should not be used.  Only use this 
  constructor that contains the following four arguments: 
  String division, String accessCode, String verifyCode, String clientIp 
  
VARIABLES: division                     TYPE: Input
 VARIABLES DESCRIPTION:   
  This is the first parameter for this constructor.  
  Pass in the station # (external format) of the division 
  to log the user in against.  
VARIABLES: accessCode                   TYPE: Input
 VARIABLES DESCRIPTION:   
  This is the second parameter for this constructor.  
  Pass in the user access code.  
VARIABLES: verifyCode                   TYPE: Input
 VARIABLES DESCRIPTION:   
  This is the third parameter for this constructor.  
  Pass in the user verify code.  
VARIABLES: clientIp                     TYPE: Input
 VARIABLES DESCRIPTION:   
  This is the fourth parameter for this constructor.  
  Pass in the client IP address.  
  To obtain the client IP address, 'request.getRemoteAddr()' may be used.  
SUBSCRIBING PACKAGE: CLINICAL INFO SUPPORT SYSTEM
  ISC: Washington/Silver Spring
  DATE ACTIVATED: SEP 12, 2008

NUMBER: 5256                            IA #: 5256
  DATE CREATED: AUG 28, 2008            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS KAAJEE GET USER INFO
  REMOTE PROCEDURE: XUS KAAJEE GET USER INFO
 GENERAL DESCRIPTION:   
  
  This is a private ICR/IA for CISS and is in support of ICR/IA # 5255.  
  Also, this RPC adds a new entry in Kernel's SIGN-ON LOG (File #3.081).  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: KAAJEE
SUBSCRIBING PACKAGE: CLINICAL INFO SUPPORT SYSTEM
  ISC: Washington/Silver Spring
  DATE ACTIVATED: SEP 12, 2008

NUMBER: 5257                            IA #: 5257
  DATE CREATED: AUG 28, 2008            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS KAAJEE LOGOUT
  REMOTE PROCEDURE: XUS KAAJEE LOGOUT
 GENERAL DESCRIPTION:   
  
  This is a private ICR/IA for CISS and is in support of ICR/IA # 5255.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: KAAJEE
SUBSCRIBING PACKAGE: CLINICAL INFO SUPPORT SYSTEM
  ISC: Washington/Silver Spring
  DATE ACTIVATED: SEP 12, 2008

NUMBER: 5258                            IA #: 5258
  DATE CREATED: AUG 29, 2008
  CUSTODIAL PACKAGE: VOLUNTARY SERVICE SYSTEM
  USAGE: Private                        TYPE: SQL Table
  DBIC APPROVAL STATUS: APPROVED        NAME: ICR FOR CISS TO ACCESS VSS
 GENERAL DESCRIPTION:   
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  SQL TABLE: vol_profile
SQL COLUMN: id
SQL COLUMN: entrydate
SQL COLUMN: terminationdate
SQL COLUMN: nameofinstitution/stationnumber
SQL COLUMN: firstname
SQL COLUMN: lastname
SQL COLUMN: middlename
SUBSCRIBING PACKAGE: OCCUPAT HEALTH RECORD-KEEPING
  DATE ACTIVATED: SEP 22, 2008

NUMBER: 5259                            IA #: 5259
  DATE CREATED: SEP 04, 2008
  CUSTODIAL PACKAGE: AUTOMATED LAB INSTRUMENTS
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: LAB HL7 ORU MESSAGE
 GENERAL DESCRIPTION:   The following event protocol is supported for packages
 to add their subscriber protocol to subscribe to Laboratory results.  
  
  NAME: LA7 LAB RESULTS AVAILABLE (EVN) 
  ITEM TEXT: Lab Results Available Event 
  
  DESCRIPTION: A VistA Laboratory package HL7 ORU result message is created 
  and sent by the HL package for transmission to any subscribers of event 
  protocol LA7 LAB RESULTS AVAILABLE (EVN).  
  
  It provides the capability for the generation of a Laboratory HL7 ORU 
  message containing patient laboratory results to subscribers of the HL7 
  event protocol LA7 LAB RESULTS AVAILABLE (EVN) as these results are made 
  available within the Laboratory package.  
  
  The following subscripts are supported by the event: 
    "CH", "MI", "SP", "CY", "EM".  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORU
KEYWORDS: LAB RESULTS
  DATE ACTIVATED: JUL 14, 2010

NUMBER: 5260                            IA #: 5260
  DATE CREATED: SEP 09, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: Private IA for CISS to use VistaLinkSystemInfoVO
 GENERAL DESCRIPTION:   This agreement pertains to subscriber use of VistALink
 v1.5 only.  
  
 Permission is granted to use the getIntroText() and getErrorMessage() methods
 of the gov.va.med.vistalink.adapter.spi.VistaLinkSystemInfoVO class. These
 methods return values populated earlier by a query to an M system.  
  
 Note: VistaLinkSystemInfoVO objects are the return value of the 
 getMSystemInfo() method of gov.va.med.vistalink.adapter.spi.ConnectorInfoVO.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: getIntroText()
 COMPONENT DESCRIPTION:   java.lang.String getIntroText(): returns a single
 string, with lines demarcated by the substring <BR>.  
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   returns java.lang.String.  
COMPONENT/ENTRY POINT: getErrorMessage()
 COMPONENT DESCRIPTION:   java.lang.String: returns any error messages stored
 by the instantiator of the VistaLinkSystemInfoVO object. Used to convey any
 errors encountered while attempting to populate the VistaLinkSystemInfoVO
 object with information from the target M/VistA system.  
VARIABLES: return val                   TYPE: Output
 VARIABLES DESCRIPTION:   java.lang.String.  
SUBSCRIBING PACKAGE: CLINICAL INFO SUPPORT SYSTEM
  DATE ACTIVATED: AUG 17, 2009

NUMBER: 5261                            IA #: 5261
  DATE CREATED: SEP 09, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: Private IA for CISS to use getMCFInfo()
 GENERAL DESCRIPTION:   This agreement pertains to subscriber use of VistALink
 v1.5 only.  
  
 Permission is granted to use the getMCFInfo() method of 
 gov.va.med.vistalink.adapter.cci.VistaLinkConnectionFactory, under the 
 following conditions: 
  
 1. It is to be used by the CISS application only, not by portlets or other 
 plug-ins to the CISS framework. 
  
 2. It is to be used prior to obtaining connection(s) from a given 
 VistaLinkConnectionFactory instance.  
  
 3. It is to be used only to retrieve the introductory text from the target
 M/VistA system for the purposes of supporting login functionality to the
 target M/VistA system.  
  
 4. If an error is encountered, the getErrorMessage() method of one of the 
 returned objects (gov.va.med.vistalink.adapter.spi.VistaLinkSystemInfoVO) will
 return a non-null, non-zero-length string.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: getMCFInfo()
 COMPONENT DESCRIPTION:   Method to query the M/VistA system associated with a
 particular VistaLinkConnectionFactory object. Creates a temporary connection, 
 queries the M system, and returns data in a ConnectorInfoVO object.  
VARIABLES: connectorInfoVO              TYPE: Both
 VARIABLES DESCRIPTION:   First method parameter is an instantiated 
 gov.va.med.vistalink.adapter.spi.ConnectorInfoVO object. Upon return, among
 the values returned in the object instance is a VistaLinkSystemInfoVO object,
 containing the introductory text from the associated M/VistA system, and any
 error encountered.  
VARIABLES: getDetailInfo                TYPE: Input
 VARIABLES DESCRIPTION:   second method parameter is a boolean. Pass true to
 get more information (including M system information), or false to get less
 (in particular, excluding M system information). 
SUBSCRIBING PACKAGE: CLINICAL INFO SUPPORT SYSTEM
  DATE ACTIVATED: AUG 17, 2009

NUMBER: 5262                            IA #: 5262
  DATE CREATED: SEP 12, 2008            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: Private IA for CISS to use ConnectorInfoVO
 GENERAL DESCRIPTION:   This agreement pertains to subscriber use of VistALink
 v1.5 only.  
  
 Permission is granted to use the getMSystemInfo() method of the 
 gov.va.med.vistalink.adapter.spi.ConnectorInfoVO class. This method returns a
 VistaLinkSystemInfoVO object instance, populated earlier by a query to an M
 system.  
     
 Note: ConnectorInfoVO objects are the return value of the getMCFInfo() method
 of gov.va.med.vistalink.adapter.cci.VistaLinkConnectionFactory.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: vistalink
COMPONENT/ENTRY POINT: getMSystemInfo()
 COMPONENT DESCRIPTION:   public VistaLinkSystemInfoVO getMSystemInfo():
 returns a populated gov.va.med.vistalink.adapter.spi.VistaLinkSystemInfoVO
 object. Among the values returned in the object instance is the introductory
 text from the associated M/VistA system, and any error encountered.  
SUBSCRIBING PACKAGE: CLINICAL INFO SUPPORT SYSTEM
  DATE ACTIVATED: AUG 17, 2009

NUMBER: 5263                            IA #: 5263
  DATE CREATED: SEP 23, 2008            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOEXDT
  NAME: Call to API UPDEXDT in routine PSOEXDT
  ID: PSOEXDT
 GENERAL DESCRIPTION:   Call to API UPDEXDT^PSOEXDT.  This API updates the
 Expiration Date for the following scenarios: normal release of an Rx, return
 to stock or reinstate.  Release update only occurs if the last refill is being
 released.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: UPDEXDT
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN of PRESCRIPTION file #52 
VARIABLES: XTYP                         TYPE: Input
 VARIABLES DESCRIPTION:   0=original; 1=refill 
VARIABLES: RELDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Release Date=release scenario; 0=return to stock or
 reinstate 
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: OCT 01, 2008

NUMBER: 5264                            IA #: 5264
  FILE NUMBER: 2                        GLOBAL ROOT: DPT
  DATE CREATED: SEP 23, 2008
  CUSTODIAL PACKAGE: ENROLLMENT APPLICATION SYSTEM
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SERVICE INFORMATION
  ID: DPT
GLOBAL REFERENCE: DPT(D0,.32)
FIELD NUMBER: All fields                ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.3291)
FIELD NUMBER: All fields                ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   SVC^VADPT will not return the service related
 information on nodes 6, 7, and 8 unless the SERVICE BRANCH field, which is not
 a required field, has a value. This means that required fields such as SERVICE 
 SEPARATION DATE LAST will not be returned unless SERVICE BRANCH LAST has a
 value. Therefore using SVC^VADPT can lead to the erroneous conclusion that a
 patient does not have a SERVICE SEPARATION DATE LAST and this data is key to
 determining if a patient needs OEF/OIF and TBI screening. To overcome this
 deficiency Clinical Reminders is requesting direct read access to the data
 returned on the 6, 7, and 8 nodes by SVC^VADPT.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PATIENT FILE
KEYWORDS: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   
  
  
  DATE ACTIVATED: SEP 30, 2008

NUMBER: 5265                            IA #: 5265
  FILE NUMBER: 40.9                     GLOBAL ROOT: DIC(40.9,DA,0
  DATE CREATED: SEP 25, 2008            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: MyHealtheVet read access to File 40.9 Location Type
  ID: DIC(40.9,DA,0
GLOBAL REFERENCE: DIC(40.9,DA,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Name of the Location Type 
 GENERAL DESCRIPTION:   Read access to file 40.9 by the MyHealtheVet package
 using FILEMAN 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 40.9
KEYWORDS: LOCATION TYPE
KEYWORDS: MYHEALTHEVET
SUBSCRIBING PACKAGE: MYHEALTHEVET
  DATE ACTIVATED: SEP 30, 2008

NUMBER: 5266                            IA #: 5266
  FILE NUMBER: 44                       GLOBAL ROOT: SC(D0
  DATE CREATED: SEP 25, 2008            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: MyHealtheVet access to file 44 Hospital Location
  ID: SC(D0
GLOBAL REFERENCE: SC
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Location Name 
FIELD NUMBER: 1                         FIELD NAME: ABBREVIATION
  LOCATION: 0;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Abbreviation 
FIELD NUMBER: 2                         FIELD NAME: TYPE
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 2.1                       FIELD NAME: TYPE EXTENSION
  LOCATION: 0;22                        ACCESS: Write w/Fileman
FIELD NUMBER: 3                         FIELD NAME: INSTITUTION
  LOCATION: 0;4                         ACCESS: Write w/Fileman
FIELD NUMBER: 10                        FIELD NAME: PHYSICAL LOCATION
  LOCATION: 0;11                        ACCESS: Write w/Fileman
FIELD NUMBER: 2502                      FIELD NAME: NON-COUNT CLINIC?
  LOCATION: 0;17                        ACCESS: Write w/Fileman
FIELD NUMBER: 2504
  FIELD NAME: CLINIC MEETS AT THIS FACILITY
  LOCATION: 0;19                        ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   Myhealthevet access to file 44 Hospital Location to add
 "Secure Messaging" as a location.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 44
KEYWORDS: HOSPITAL LOCATION
KEYWORDS: MYHEALTHEVET
SUBSCRIBING PACKAGE: MYHEALTHEVET
  DATE ACTIVATED: SEP 30, 2008

NUMBER: 5267                            IA #: 5267
  FILE NUMBER: 210                      GLOBAL ROOT: NURSF(210
  DATE CREATED: SEP 25, 2008            CUSTODIAL PACKAGE: NURSING SERVICE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Use of NURSF(210
  ID: NURSF(210
GLOBAL REFERENCE: NURSF(210,D0,0)
FIELD NUMBER: .01                       FIELD NAME: EMPLOYEE NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: NURSF(210,'B'
 GENERAL DESCRIPTION:   This agreement allows read access to the Nursing Staff
 file #210.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
  DATE ACTIVATED: SEP 30, 2008

NUMBER: 5268                            IA #: 5268
  FILE NUMBER: 130                      GLOBAL ROOT: SRF(
  DATE CREATED: SEP 30, 2008            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: File
  NAME: ATTENDING SURGEON/PROVIDER      ID: SRF(
GLOBAL REFERENCE: SRF(D0,.1)
FIELD NUMBER: .14                       FIELD NAME: SURGEON
  LOCATION: .1;4                        ACCESS: Read w/Fileman
FIELD NUMBER: .164                      FIELD NAME: ATTEND SURG
  LOCATION: .1;13                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: SRF(D0,NON)
FIELD NUMBER: 118                       FIELD NAME: NON-OR PROCEDURE
  LOCATION: NON;1                       ACCESS: Read w/Fileman
FIELD NUMBER: 123                       FIELD NAME: PROVIDER
  LOCATION: NON;6                       ACCESS: Read w/Fileman
FIELD NUMBER: 124                       FIELD NAME: ATTEND PROVIDER
  LOCATION: NON;7                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This ICR grants permission to read specific fields in
 the SURGERY file (#130) using VA FileMan.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE

NUMBER: 5269                            IA #: 5269
  DATE CREATED: OCT 02, 2008            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MDTERM
  NAME: MDTERM                          ID: MDTERM
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CVTVAL
COMPONENT/ENTRY POINT: CVTVAL(MDVAL,MDFR,MDTO,MDROUND)
 COMPONENT DESCRIPTION:   This function converts a value from one unit of
 measurement to another.  
  
  Example: 
  >S MDVAL=99,MDFR="DEGREES F",MDTO="DEGREES C",MDROUND=1 
  >W $$CVTVAL^MDTERM(MDVAL,MDFR,MDTO,MDROUND) 
  >37.2 
VARIABLES: MDVAL                        TYPE: Input
 VARIABLES DESCRIPTION:   Value to convert (Required) 
VARIABLES: MDFR                         TYPE: Input
 VARIABLES DESCRIPTION:   VUID or Name of unit to convert from (Must be exact
 match). (Required) 
VARIABLES: MDTO                         TYPE: Input
 VARIABLES DESCRIPTION:   VUID or Name of unit to convert to (Must be exact
 match) (Required) 
VARIABLES: MDROUND                      TYPE: Input
 VARIABLES DESCRIPTION:   Decimal precision (optional to override conversion
 logic) 
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  DATE ACTIVATED: MAR 04, 2010

NUMBER: 5270                            IA #: 5270
  DATE CREATED: OCT 09, 2008
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MPIFDNL
  NAME: CALLRPC MPIFDNL                 ID: MPIFDNL
 GENERAL DESCRIPTION:   CALLRPC^MPIFDNL calls Remote Procedure MPIF DNL ADD UPD
 to add a record with a pair of patient DFNs to the MPI DO NOT LINK file on the
 MPI Server.  This file is used to prevent users from attempting to LINK
 patients who have been determined to not be duplicates.  
  
 DNLCHK^MPIFDNL calls Remote Procedure MPI EVENT LIST, which returns (among 
 other things) a list of DFNs for those patients that are marked as "Do Not 
 Link" with the passed in DFN. From this list, DNLCHK^MPIFDNL determines 
 whether to allow the selected pair of patients to be added to the DUPLICATE
 RESOLUTION file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MPIFDNL
KEYWORDS: DUPLICATE
KEYWORDS: RESOLUTION
KEYWORDS: MPI DO NOT LINK
KEYWORDS: DO NOT LINK
KEYWORDS: XDRDEDT
KEYWORDS: XDRDPICK
KEYWORDS: MPIF DNL ADD UPD
COMPONENT/ENTRY POINT: CALLRPC
 COMPONENT DESCRIPTION:   D
 CALLRPC^MPIFDNL(DUZ,DUZ(2),DFN1,DFN2,INACTIVATION_FLAG) 
  
 If an error occurs, it is logged to the CIRN HL7 EXCEPTION LOG file (#991.1) 
VARIABLES: MPIFDUZ                      TYPE: Input
 VARIABLES DESCRIPTION:   1) DUZ of current user (REQUIRED) 
VARIABLES: MPIFSITE                     TYPE: Input
 VARIABLES DESCRIPTION:   2) Station IEN (from file #4 INSTITUTION) of the
 current users institution (from DUZ(2)) - REQUIRED.  
VARIABLES: MPIFFR                       TYPE: Input
 VARIABLES DESCRIPTION:   3) IEN (DFN) of first patient from file #2 PATIENT at
 the VistA site (REQUIRED).  
VARIABLES: MPIFTO                       TYPE: Input
 VARIABLES DESCRIPTION:   4) IEN (DFN) of second patient from file #2 PATIENT
 at the VistA site (REQUIRED).  
VARIABLES: MPIFINAC                     TYPE: Input
 VARIABLES DESCRIPTION:   5) If set to 1, entry in MPI DO NOT LINK file will be
 inactivated (OPTIONAL).  
COMPONENT/ENTRY POINT: DNLCHK
 COMPONENT DESCRIPTION:   Checks whether patient records with DFNs MPIFREC1 and
 MPIFREC2 are verified as not duplicates in the MPI DO NOT LINK file. Returns 0
 if the there were no problems making the Remote Procedure call and the pair is 
 not in the MPI DO NOT LINK file; otherwise, returns -1^error message. 
VARIABLES: MPIFREC1                     TYPE: Input
 VARIABLES DESCRIPTION:   1) DFN of a record in the Patient file.  
VARIABLES: MPIFREC2                     TYPE: Input
 VARIABLES DESCRIPTION:   2) DFN of another record in the Patient file.  
SUBSCRIBING PACKAGE: TOOLKIT
 SUBSCRIBING DETAILS:   When a user sets the status of a pair of patients in
 the DUPLICATE RECORD file to VERIFIED, NOT A DUPLICATE, CALLRPC^MPIRPC is
 called to add the patient pair record to the MPI DO NOT LINK file. (routine
 ^XDRDPICK) 
  
 When a user resets the status of a pair of patients in the DUPLICATE RECORD
 file from VERIFIED, NOT A DUPLICATE back to POTENTIAL DUPLICATE, UNVERIFIED,
 CALLRPC^MPIRPC is called to set the status on the record in the MPI DO NOT
 LINK file to INACTIVE. (routine ^XDRDEDT) 
  
 When a user attempts to add a pair of patients to the DUPLICATE RECORD file
 via the "Add Verified Duplicate Pair" option [XDR ADD VERIFIED DUPS], routine
 ^XDRMADD calls DNLCHK^MPIFDNL, which makes a direct RPC call to check that the
 selected pair does not exist on the MPI DO NO LINK file (#985.28). (routine
 ^XDRMADD) 
  DATE ACTIVATED: AUG 04, 2010

NUMBER: 5271                            IA #: 5271
  DATE CREATED: OCT 09, 2008            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XDRDADDS
  NAME: ADD XDRDADDS                    ID: XDRDADDS
 GENERAL DESCRIPTION:   ADD^XDRDADDS adds a patient pair record to the
 DUPLICATE RECORD file (#15) at a VistA site. It can be called directly, but
 can also be invoked using the Remote Procedure call XDR ADD POTENTIAL PATIENT
 DUP.  
  
 With patch MPI*1.0*62, and accompanying patches MPIF*1.0*52 and XT*7.3*113,
 most entries will be made to a local VistA DUPLICATE RECORD file because of an
 action taken by the Person Service Identity Management package (PSIM). Either
 a pair of patients is determined to be above the Auto Match Threshold by the
 commercial search engine Initiate, or a pair of patients has been determined
 to be a potential match and verified by the Identity Management Data Quality
 group (IMDQ).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XDRDADDS
KEYWORDS: MPIF002
KEYWORDS: MPIFQ0
KEYWORDS: DUPLICATE
KEYWORDS: RESOLUTION
KEYWORDS: XDR ADD POTENTIAL PATIENT DUP
COMPONENT/ENTRY POINT: ADD
 COMPONENT DESCRIPTION:   ADD(XDRSLT,XDRFL,XDRFR,XDRTO)  Add a record to the
 DUPLICATE RECORD file (#15) 
VARIABLES: XDRSLT                       TYPE: Output
 VARIABLES DESCRIPTION:   1) Set to DFN in file 15 if add was successful,
 -1^ERRMSG if error 
VARIABLES: XDRFL                        TYPE: Input
 VARIABLES DESCRIPTION:   2) File number where duplicate records reside. If not
 passed, defaults to PATIENT file.  
VARIABLES: XDRFR                        TYPE: Input
 VARIABLES DESCRIPTION:   3) From entry IEN (DFN if PATIENT file entry) 
VARIABLES: XDRTO                        TYPE: Input
 VARIABLES DESCRIPTION:   4) To entry IEN (DFN if PATIENT file entry) 
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA
 SUBSCRIBING DETAILS:   Routine MPIFQ0: When a user registers a patient in
 VistA, a query is sent to MPI. Previously, if that patient was a potential
 match to an existing patient on that VistA system, MPIFQ0 logged a Potential
 Match Exception.  After patch MPI*1.0*62 and accompanying patches XT*7.3*113
 and MPIF*1.0*52 are installed, MPIFQ0 will instead call ADD^XDRDADDS to add
 the patient pair to the DUPLICATE RECORD file (#15).  
  
 If the INITIATE search engine in PSIM determines that two patients are above
 the auto match threshold and they are both known at the same VistA site, an
 MPI routine calls the Remote Procedure Call XDR ADD POTENTIAL PATIENT DUP,
 which calls ADD^XDRDADDS to add the patient pair to the DUPLICATE RECORD file. 
  
 Routine MPIF002: If the INITIATE search engine in PSIM determines that two 
 patients are a potential match, IMDQ will use the PSIM IMDQ Toolkit to review
 the patients. If they are determined to be a match and are both known at the
 same VistA site, MPI will send an A24 message to the site.  This calls
 ^MPIF002 which calls new routine ADD^XDRDADDS to add a new entry to the sites
 DUPLICATE RECORD file 
  DATE ACTIVATED: MAR 12, 2009

NUMBER: 5272                            IA #: 5272
  FILE NUMBER: 161                      GLOBAL ROOT: FBAAA(
  DATE CREATED: OCT 12, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS FILE 161 R/W/D             ID: FBAAA(
 GENERAL DESCRIPTION:   FBCS accesses the FEE BASIS PATIENT (#161) file to
 read/write. Some deletions will be done on the AUTHORIZATION multiple
 (#161.01) after data integrity checks.  Applicable Authorized Services (FIELD
 7 from file #162.4) are copied to field .021 Authorization Remark.  
  
      ^FBAAA(DA,0)                         Global r ($D) 
        .01    NAME                   0;1  Fileman r 
      ^FBAAA(D0,1,0)                       Global r (get count) 
        1      AUTHORIZATION          0;4 
      ^FBAAA(D0,1,D1,0)                    Global r ($D) 
        .01    FROM DATE              0;1  Fileman r/w,Laygo,Global r 
        .02    TO DATE                0;2  Fileman r/w,Global r 
        .03    FEE PROGRAM            0;3  Fileman r/w,Global r 
        .04    VENDOR                 0;4  Fileman r/w,Global r/w 
        101    PRIMARY SERVICE AREA   0;5  Fileman r/w,Global r 
        .07    PURPOSE OF VISIT CODE  0;7  Fileman r/w,Global r 
        .08    DX LINE 1              0;8  Fileman r/w 
        .055   ASSOCIATED 7078/583    0;9  Fileman r,Global r 
        .095   TREATMENT TYPE CODE    0;13 Fileman r/w,Global r 
        2      TYPE OF CARE           0;14 Fileman r/w 
        .06    DISCHARGE TYPE         0;15 Fileman r/w 
        .065   PATIENT TYPE CODE      0;18 Fileman r/w,Global r 
        .096   ACCIDENT RELATED (Y/N) 0;19 Fileman r/w 
        .097   POTENTIAL COST RECOV   0;20 Fileman r/w 
        104    REFERRING PROVIDER     0;21 Fileman r/w,Global r 
      ^FBAAA(D0,1,D1,1) 
        3      DATE PRINTED           1;2  Fileman r 
      ^FBAAA(D0,1,D1,2,0) 
        .021   AUTHORIZATION REMARKS 
      ^FBAAA(D0,1,D1,2,D2,0) 
        .01    AUTHORIZATION REMARK   0;1  Fileman r/w,Global r/w 
      ^FBAAA(D0,1,D1,3) 
        .085   DX LINE 2              3;1  Fileman r/w,Global r 
        .086   DX LINE 3              3;2  Fileman r/w,Global r 
      ^FBAAA(D0,1,D1,100) 
        100    CLERK                100;1  Fileman r/w 
      ^FBAAA(D0,1,D1,ADEL) 
        103    DATE DELETE MRA TRAN ADEL;2 Global r 
      ^FBAAA(D0,1,D1,C) 
        1      PRINT AUTHORIZATION    C;1  Fileman r/w 
      ^FBAAA(D0,1,D1,LOG1,D2,0) 
        .01 DATA/TIME EDITED          0;1  Fileman r 
        1   EDITED BY                 0;2  Fileman r 
        2 COMMENTS                    0;3  Fileman r 
      ^FBAAA(DO,1,D1,LOG2,D2,0) 
        .01 CHANGED DATE/TIME         0;1  Fileman r 
        1   FIELD                     0;2  Fileman r 
        2   OLD VALUE                 0;3  Fileman r 
        3   NEW VALUE                 0;4  Fileman r 
        4   CHANGED BY                0;5  Fileman r 
      ^FBAAA(D0,4) 
        .5     FEE ID CARD NUMBER     4;1  Fileman r,Global r 
        .6     FEE ID CARD ISSUE DATE 4;2  Fileman r,Global r 
      ^FBAA("AG")       Lookup by ASSOCIATED 7078/583 
      ^FBAA("ATST")     Lookup by From Date 
      ^FBAAA(DFN,1,"B") Lookup by Authorization From Date 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: APR 29, 2016

NUMBER: 5273                            IA #: 5273
  FILE NUMBER: 161.7                    GLOBAL ROOT: FBAA(161.7
  DATE CREATED: OCT 15, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS FILE #161.7 R/W/D          ID: FBAA(161.7
 GENERAL DESCRIPTION:   FBCS accesses the FEE BASIS BATCH (#161.7) file to
 read/write. Entries can be deleted using ^DIK if it passes criteria (no
 rejects pending, etc).  
  
      ^FBAA(161.7,D0,0)            
        .01  NUMBER               0;1   Fileman r/w,Global r   
        1    OBLIGATION NUMBER    0;2   Fileman r/w,Global r        
        2    TYPE                 0;3   Fileman r/w,Global r        
        3    DATE OPENED          0;4   Fileman r/w,Global r        
        4    CLERK WHO OPENED     0;5   Fileman r/w,Global r        
        5    DATE SUPERVISOR CLOS 0;6   Fileman r,Global r/w      
        6    SUPERVISOR WHO CERTI 0;7   Fileman r,Global w 
        16   STATION NUMBER       0;8   Fileman r/w,Global r        
        8    TOTAL DOLLARS        0;9   Fileman r/w,Global r/w 
        9    INVOICE COUNT        0;10  Fileman r/w,Global r/w   
        10   PAYMENT LINE COUNT   0;11  Fileman r/w,Global r/w   
        13   DATE FINALIZED       0;12  Fileman r/w,Global r/w      
        4.5  DATE CLERK CLOSED    0;13  Fileman r/w,Global r/w 
        12   DATE TRANSMITTED     0;14  Fileman r/w,Global r      
        17   CONTRACT HOSPITAL BA 0;15  Fileman r/w,Global r     
        14   PERSON WHO COMPLETED 0;16  Fileman r/w      
        15   REJECTS PENDING      0;17  Global r/w 
        18   BATCH EXEMPT         0;18  Fileman r,Global r/w      
        19   STATISTICAL BATCH    0;19  Global r 
      ^FBAA(161.7,D0,ST) 
        11       STATUS          ST;1   Fileman r/w,Global r/w 
      
      ^FBAA(161.7,"AB") by status without field 5 (date closed) 
                        manually kill xref 
      ^FBAA(161.7,"AC") Lookup by status, check is status exists 
                        manually sets/kills xref 
      ^FBAA(161.7,"B")  Lookup by batch 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5274                            IA #: 5274
  FILE NUMBER: 442                      GLOBAL ROOT: PRC(442
  DATE CREATED: OCT 15, 2008            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS FILE 442                   ID: PRC(442
 GENERAL DESCRIPTION:   The Fee Basis Claims system accesses the PROCUREMENT &
 ACCOUNTING TRANSACTIONS (#442) file in order to return a list of obligations
 based upon Control point and number of years past for reports, as well as 
 lookup obligations by control point.  
  
   ^PRC(442,D0,0) 
      .01      PURCHASE ORDER NUMBE 0;1      Read w/Fileman 
      1        FCP                  0;3      Fileman r/global r 
      1.4      APPROPRIATION        0;4      Global r 
      2        COST CENTER          0;5      Global r 
      3        SUBACCOUNT1          0;6      Global r 
      3.4      SUBAMOUNT1           0;7      Global r 
      4        SUBACCOUNT2          0;8      Global r 
      4.4      SUBAMOUNT2           0;9      Global r 
      91       TOTAL AMOUNT         0;15     Read w/Fileman 
      .07      PRIMARY 2237         0;12     Fileman r/global r 
    ^PRC(442,D0,1) 
      .1       P.O. DATE            1;15     Read w/Fileman 
    ^PRC(442,D0,7) 
      .5       SUPPLY STATUS        7;1      Fileman r/global r 
    ^PRC(442,D0,8) 
      94       ACTUAL 1358 BALANCE  8;1      Fileman r/global r 
      96       EST 1358 BALANCE     8;3      Fileman r/global r 
    ^PRC(442,D0,23) 
      31       SUBSTATION           23;7     Global r 
        
   ^PRC(442,"B")  Used for IEN lookup 
   ^PRC(442,"C")  Used for IEN lookup 
   ^PRC(442,"E")  Used for FCP lookups 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JAN 06, 2009

NUMBER: 5275                            IA #: 5275
  FILE NUMBER: 161.4                    GLOBAL ROOT: FBAA(161.4
  DATE CREATED: OCT 16, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS ACCESS TO FILE #161.4 R/O  ID: FBAA(161.4
 GENERAL DESCRIPTION:   FBCS accesses the FEE BASIS SITE PARAMETERS (#161.4)
 file as part of the lookup of existing Fee Basis Site parameters to ensure
 parameters are defined and to get batch numbers.  
     
      ^FBAA(161.4,D0,0)                          Global r ($G),($D) 
      ^FBAA(161.4,D0,1)                          Global r ($G) 
        27  PSA DEFAULT INSTITUTION         1;3  Global r 
      ^FBAA(161.4,D0,FBNUM)                      Lock 
        10  NEXT BATCH NUMBER           FBNUM;1  Global r/w 
        11  NEXT INVOICE NUMBER         FBNUM;2  Global r/w 
        17  MAX # PAYMENT LINE ITEMS    FBNUM;3  Global r 
      ^FBAA(161.4,D0,PURGE) 
        29  DATE BATCH PURGE LAST RUN   PURGE;1  Global r 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5276                            IA #: 5276
  FILE NUMBER: 161.6                    GLOBAL ROOT: FBAA(161.6
  DATE CREATED: OCT 16, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #161.6 Read only      ID: FBAA(161.6
 GENERAL DESCRIPTION:   The FBCS application accesses the FEE BASIS SPECIALTY
 CODE (#161.6) file to get the name field for display.  
  
      ^FBAA(161.6,D0,0) 
        .01      NAME                 0;1   Global r 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5277                            IA #: 5277
  FILE NUMBER: 162.5                    GLOBAL ROOT: FBAAI(
  DATE CREATED: OCT 16, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  NAME: FBCS ACCESS TO FILE #162.5      ID: FBAAI(
 GENERAL DESCRIPTION:   The Fee Basis Claims system accesses the FEE BASIS
 INVOICE (#162.5) file to view invoices and perform other claim functions.  
  
   ^FBAAI(D0,0) 
      .01  NUMBER                   0;1   Fileman r/w 
      1    INVOICE DATE RECEIVE     0;2   Fileman r/w,global r 
      2    VENDOR                   0;3   Fileman r/w,global r 
      3    VETERAN                  0;4   Fileman r,global r 
      4    ASSOCIATED 7078/583      0;5   Fileman r/w,global r 
      5    TREATMENT FROM DATE      0;6   Fileman r/w,global r 
      6    TREATMENT TO DATE        0;7   Fileman r/w,global r 
      7    AMOUNT CLAIMED           0;8   Fileman r/w,global r 
      8    AMOUNT PAID              0;9   Fileman r/w,global r 
      9    AMOUNT SUSPENDED         0;10  Fileman r,global r 
      10   SUSPEND CODE             0;11  Fileman r,global r 
      11   FEE PROGRAM              0;12  Fileman r/w,global r 
      12   PAYMENT TYPE CODE        0;13  Fileman r,global r 
      16   VOID PAYMENT             0;14  Fileman r,global r 
      17   SUPERVISOR WHO VOIDE     0;15  Read w/Fileman 
      19   DATE FINALIZED           0;16  Read w/Fileman 
      20   BATCH NUMBER             0;17  Fileman r/w, global r 
      21   PURPOSE OF VISIT         0;18  Read w/Fileman 
      22   PT TYPE CODE             0;19  Fileman r,global r 
      23   PRIMARY SERVICE FACI     0;20  Read w/Fileman 
      6.5  DISCHARGE TYPE CODE      0;21  Fileman r/w 
      6.6  BILLED CHARGES           0;22  Fileman r/w 
      6.7  PAYMENT BY MEDICARE/FED  0;23  Fileman r/w 
      24   DISCHARGE DRG            0;24  Fileman r/w,global r 
      25   RESUBMISSION             0;25  Fileman r/w 
      26   NVH PRICER AMOUNT        0;26  Fileman r/w 
   ^FBAAI(D0,1,D1,0) 
      .01  DESCRIPTION OF SUSPENSE  0;1   Read w/Fileman ok 
   ^FBAAI(D0,2) 
      45   DATE PAID                2;1   Fileman r,global r 
      46   VENDOR INVOICE DATE      2;2   Fileman r/w 
      47   PROMPT PAY TYPE          2;3   Fileman r/w 
      48   CHECK NUMBER             2;4   Fileman r,global r 
      49   CANCELLATION DATE        2;5   Fileman r,global r 
      50   REASON CODE              2;6   Fileman r,global r 
      51   CANCELLATION ACTIVIT     2;7   Fileman r,global r 
      52   DISBURSED AMOUNT         2;8   Fileman r,global r 
      53   INTEREST AMOUNT          2;9   Fileman r/global r 
      54   COVERED DAYS             2;10  Fileman r/w,global r 
      55   PATIENT CONTROL NUMB     2;11  Fileman r/w,global r 
      24.5 DRG WEIGHT               2;12  Fileman r/w 
   ^FBAAI(D0,3) 
      56   FPPS CLAIM ID            3;1   Fileman r,global r 
      57   FPPS LINE ITEM           3;2   Fileman r,global r 
   ^FBAAI(D0,8,0) 
      58   ADJUSTMENT                     Fileman r 
   ^FBAAI(D0,8,D1,0) 
      .01  ADJSUTMENT REASON        0;1   Fileman r/w 
       1   ADJUSTMENT GROU          0;2   Fileman r/w 
       2   ADJUSTMENT AMOUNT        0;3   Fileman r/w 
   ^FBAAI(D0,9,D1,0) 
      .01  REMITTANCE REMARK        0;1   Fileman r/w 
   ^FBAAI(D0,DX) 
      30   ICD1                    DX;1   Fileman r/w,global r 
      31   ICD2                    DX;2   Fileman r/w,global r 
      32   ICD3                    DX,3   Fileman r/w,global r 
      33   ICD4                    DX;4   Fileman r/w,global r 
      34   ICD5                    DX;5   Fileman r/w,global r 
   ^FBAAI(D0,FBREJ) 
      13   REJECT STATUS        FBREJ;1   Fileman r/w 
      14   REJECT REASON        FBREJ;2   Fileman r/w 
      15   OLD BATCH NUMBER     FBREJ;3   Fileman r/w 
   ^FBAAI(D0,PROC) 
      40   PROC1                 PROC;1   Fileman r/w,global r 
      41   PROC2                 PROC;2   Fileman r/w,global r 
      42   PROC3                 PROC;3   Fileman r/w,global r 
      43   PROC4                 PROC;4   Fileman r/w,global r 
      44   PROC5                 PROC;5   Fileman r/w,global r 
   ^FBAAI(D0,R) 
      16.5 REASON FOR VOIDED PA     R;1   Read w/Fileman 
   
   ^FBAAI("AC")  Used to lookup by Batch Number 
   ^FBAAI("AD")  Used to lookup by Date Finalized 
   ^FBAAI("AE")  Used to lookup by Batch and Veteran 
   ^FBAAI("AH")  Used to lookup by Old Batch number 
   ^FBAAI("E")   Used to lookup by Associated 7078/583 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5278                            IA #: 5278
  FILE NUMBER: 161.2                    GLOBAL ROOT: FBAAV
  DATE CREATED: OCT 16, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  NAME: FBCS File #161.2 Read only      ID: FBAAV
 GENERAL DESCRIPTION:   The Fee Basis Claims system accesses the FEE BASIS
 VENDOR (#161.2) file to get vendor details and to get the vendor for fee
 batches.  
     
   ^FBAAV(D0,0) 
      .01      NAME                 0;1    Fileman r/global r 
      1        ID NUMBER            0;2    Fileman r/global r 
      2        STREET ADDRESS       0;3    Fileman r/global r 
      3        CITY                 0;4    Fileman r/global r 
      4        STATE                0;5    Fileman r/global r 
      5        ZIP CODE             0;6    Fileman r/global r 
      6        TYPE OF VENDOR       0;7    Fileman r/global r 
                                            global r of DD for codeset 
      .05      SPECIALTY CODE       0;8    Fileman r/global r 
      7        PART CODE            0;9    Fileman r/global r 
      8        CHAIN                0;10   Fileman r/global r 
      5.5      COUNTY               0;13   Fileman r/global r 
      2.5      STREET ADDRESS 2     0;14   Fileman r/global r 
      22       MEDICARE ID NUMBER   0;17   Fileman r/global r 
   ^FBAAV(D0,1) 
      14       PHONE NUMBER                    1;1  Fileman r/global r 
      19       CERTIFIED MEDICARE/MEDICAID     1;5  Read w/Fileman 
      23       FAX NUMBER                      1;9  Fileman r/global r 
      24       BUSINESS TYPE                   1;10 Fileman r/global r 
   ^FBAAV(D0,2,D1,0) 
      .01      SOCIOECONOMIC GROUP             0;1  Global r 
   ^FBAAV(D0,ADEL) 
      9        AUSTIN DELETED                 ADEL;1 Fileman r/global r 
      12       DATE LAST CORRECTION TO AUSTIN ADEL;2 Fileman r/global r 
      12.1     DATE LAST UPDATE FROM AUSTIN   ADEL;4 Fileman r/global r 
      13.1     STATION AFFECTING LAST CHANGE  ADEL;5 Global r 
   ^FBAAV(D0,AMS) 
      30.01    AUSTIN NAME FIELD              AMS;1  Fileman r/global r 
      30.02    PRICER EXEMPT                  AMS;2  Global r 
      
    ^FBAAV("C")    Used for lookup by ID Number 
    ^FBAAV("ADEL") Used to see if marked for deletion 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5279                            IA #: 5279
  FILE NUMBER: 162.2                    GLOBAL ROOT: FBAA(162.2)
  DATE CREATED: OCT 22, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #162.2 R/W            ID: FBAA(162.2)
GLOBAL REFERENCE: FBAA(162.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#.01) DATE/TIME [1D] 
FIELD NUMBER: 1                         FIELD NAME: VENDOR
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#1) VENDOR [2P:161.2] 
FIELD NUMBER: 2                         FIELD NAME: PERSON WHO CALLED
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#2) PERSON WHO CALLED [3F] 
FIELD NUMBER: 3                         FIELD NAME: VETERAN
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#3) VETERAN [4P:2] 
FIELD NUMBER: 4                         FIELD NAME: AUTHORIZED FROM DATE/TIME
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#4) AUTHORIZED FROM DATE/TIME [5D] 
FIELD NUMBER: 5                         FIELD NAME: ADMITTING DIAGNOSIS
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#5) ADMITTING DIAGNOSIS [6F] 
FIELD NUMBER: 6                         FIELD NAME: ATTENDING PHYSICIAN
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#6) ATTENDING PHYSICIAN [7F] 
FIELD NUMBER: 7                         FIELD NAME: USER ENTERING NOTIFICATION
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#7) USER ENTERING NOTIFICATION [8P:200] 
FIELD NUMBER: 8                         FIELD NAME: LEGAL ENTITLEMENT
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#8) LEGAL ENTITLEMENT [9F] 
FIELD NUMBER: 10                        FIELD NAME: USER ENTERING LEGAL DETERM.
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#10) USER ENTERING LEGAL DETERM. [11P:200] 
FIELD NUMBER: 9                         FIELD NAME: DATE OF LEGAL DETERMINATION
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#9) DATE OF LEGAL DETERMINATION [10D] 
FIELD NUMBER: 11                        FIELD NAME: MEDICAL ENTITLEMENT
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#11) MEDICAL ENTITLEMENT [12F] 
FIELD NUMBER: 12
  FIELD NAME: DATE OF MEDICAL DETERMINATION
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#12) DATE OF MEDICAL DETERMINATION [13D] 
FIELD NUMBER: 13                        FIELD NAME: USER ENTERING MEDICAL DETERM
  LOCATION: 0;14                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#13) USER ENTERING MEDICAL DETERM. [14P:200] 
FIELD NUMBER: 100                       FIELD NAME: REQUEST STATUS
  LOCATION: 0;15                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#100) REQUEST STATUS [15S] 
FIELD NUMBER: 14                        FIELD NAME: SUSPENSE CODE
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#14) SUSPENSE CODE [16P:161.27] 
FIELD NUMBER: 16                        FIELD NAME: ASSOCIATED 7078
  LOCATION: 0;17                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#16) ASSOCIATED 7078 [17P:162.4] 
FIELD NUMBER: 6.5                       FIELD NAME: ATTEN.PHYSICIAN PHONE NUMBER
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#6.5) ATTEN.PHYSICIAN PHONE NUMBER [18F] 
FIELD NUMBER: 3.5                       FIELD NAME: DATE/TIME OF ADMISSION
  LOCATION: 0;19                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#3.5) DATE/TIME OF ADMISSION [19D] 
GLOBAL REFERENCE: FBAA(162.2,D0,1,0)
FIELD NUMBER: 15                        FIELD NAME: DESCRIPTION OF SUSPENSION
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   SUBFILE 162.215 (#15) DESCRIPTION OF SUSPENSION 
GLOBAL REFERENCE: FBAA(162.2,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION OF SUSPENSION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#.01) DESCRIPTION OF SUSPENSION [1W] 
GLOBAL REFERENCE: FBAA(162.2,D0,2)
FIELD NUMBER: 17                        FIELD NAME: referring provider
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   (#17) REFERRING PROVIDER [1P:200] 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5280                            IA #: 5280
  FILE NUMBER: 162.6                    GLOBAL ROOT: FBAA(162.6)
  DATE CREATED: OCT 23, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #162.6 Read only      ID: FBAA(162.6)
GLOBAL REFERENCE: FBAA(162.6,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   (#.01) NAME [1F] 
FIELD NUMBER: 1                         FIELD NAME: CODE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   (#1) CODE [2N] 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5281                            IA #: 5281
  FILE NUMBER: 353.1                    GLOBAL ROOT: IBE(353.1)
  DATE CREATED: OCT 23, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #353.1 Read only      ID: IBE(353.1)
GLOBAL REFERENCE: IBE(353.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Using cross references:  ^IBE(353.1,"B"  to verify .01
 field (external entries conversion to IEN) 
  
 Also using fileman to get values for a pull down list (palce of service): D
 LIST^DIC(353.1,"",".01;.02","","","","","","","","ARRAY","MSG") 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: DEC 03, 2008

NUMBER: 5282                            IA #: 5282
  FILE NUMBER: 353.2                    GLOBAL ROOT: IBE(353.2
  DATE CREATED: OCT 23, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #353.2 Read only      ID: IBE(353.2
GLOBAL REFERENCE: IBE(353.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Verifying data at node: $D(^IBE(353.2,IEN,0) 
  
  
 Also using FM to retrieve a list for the GUI of HCFA type of Service: D
 LIST^DIC(353.2,"",".01;.02","","","","","","","","ARRAY","MSG") 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: DEC 03, 2008

NUMBER: 5283                            IA #: 5283
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200)
  DATE CREATED: OCT 23, 2008            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #200 Read only        ID: VA(200)
GLOBAL REFERENCE: VA(200,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   (#.01) NAME [1F] 
GLOBAL REFERENCE: VA(200,D0,51,0)
FIELD NUMBER: 51                        FIELD NAME: KEYS
  LOCATION: 51;0                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   SUBFILE 200.051 
GLOBAL REFERENCE: VA(200,D0,51,D1,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   (#.01) KEY [1P:19.1] Specifically looking for
 "FBAASUPERVISOR" 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5284                            IA #: 5284
  FILE NUMBER: 161.5                    GLOBAL ROOT: FBAA(161.5
  DATE CREATED: OCT 24, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #161.5 R/W            ID: FBAA(161.5
 GENERAL DESCRIPTION:   The Fee Basis Claims system accesses the FEE CH REPORT
 OF CONTACT (#161.5) file in order to add/edit contact information.  Entries
 may be deleted using ^DIK if the associated notification entry in file #162.2
 is deleted.  
    
      ^FBAA(161.5,D0,0)                       Global r ($D) 
        .01      ASSOCIATED REQUEST   0;1      Fileman r/w 
        1        VENDOR               0;2      Fileman r/w 
        2        VETERAN              0;3      Fileman r/w 
        3        INITIAL DATE OF CONT 0;4      Fileman r/w 
        4        AUTHORIZATION FROM D 0;5      Fileman r/w 
        5        TYPE OF CONTACT      0;6      Fileman r/w,Global r 
        7        STREET ADDRESS[1] OF 0;8      Fileman r/w 
        8        STREET ADDRESS[2] OF 0;9      Fileman r/w 
        9        CITY OF CONTACT      0;10     Fileman r/w 
        10       STATE OF CONTACT     0;11     Fileman r/w 
        11       ZIP CODE OF CONTACT  0;12     Fileman r/w 
        12       ATTENDING PHYSICIAN  0;13     Fileman r/w 
        13       ATTEND.PHYSICIAN TEL 0;14     Fileman r/w 
      ^FBAA(161.5,D0,1) 
        14       TENTATIVE DIAGNOSIS  1;1      Fileman r/w 
        15       INSURANCE TYPE       1;2      Fileman r/w 
        16       MODE OF TRANSPORTATI 1;3      Fileman r/w 
        6.5      PHONE # OF PERSON CO 1;4      Fileman r/w 
        16.5     VETERAN HAVE OTHER I 1;5      Fileman r/w 
        18       APPROVING OFFICIAL   1;6      Fileman r/w 
        19       DATE OF ADMISSION    1;7      Fileman r/w 
      ^FBAA(161.5,D0,2,D1,0) 
        .01      DATE/TIME OF CONTACT 0;1      Fileman r/w 
        2        USER                 0;2      Fileman r/w 
      ^FBAA(161.5,D0,2,D1,1,D2,0) 
        .01      NARRATIVE            0;1      Fileman r/w 
  
      ^FBAA(161.5,"B")   Lookup by request 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5285                            IA #: 5285
  DATE CREATED: NOV 03, 2008            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  ROUTINE: HLOCNRT1                     NAME: DBIA5285
  ID: HLOCNRT1
 GENERAL DESCRIPTION:   PROVIDES A TOOL TO CONVERT MESSAGES GENERATED FOR HL7
 TO MESSAGES THAT CAN BE SENT BY HLO.  ALSO PROVIDES THE ABILITY TO OVERIDE 
 PARAMETERS DEFINED IN THE EVENT AND SUBSCRIBER PROTOCOLS.  
  STATUS: Withdrawn
KEYWORDS: HAIISS
KEYWORDS: HLO
KEYWORDS: HL7
COMPONENT/ENTRY POINT: HLO(PARAMETERS,TRANSFORM)
 COMPONENT DESCRIPTION:   PARAMETERS - USED TO OVERIDE EVENT AND SUBSCRIBER
 PROTOCOL PARAMETERS.  TRANSFORM  - A ROUTINE THAT WILL TRANSFORM THE MESSAGE
 IN SOME WAY 
              BEFORE THE MESSAGE IS SENT.  
SUBSCRIBING PACKAGE: HEALTHCARE ASSOC INFECTION

NUMBER: 5286                            IA #: 5286
  DATE CREATED: NOV 06, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBJPS3
  NAME: PAY-TO PROVIDER PHONE NUMBER API
  ID: IBJPS3
 GENERAL DESCRIPTION:   This is a replacement IA for IA# 4049.  The purpose of
 the IA is the same.  
  
 When an electronic EOB is received in error at a site, EDI Lockbox has 
 functionality to transfer that EOB electronically to another site.  The IB 
 Site Parameters file (#350.9) contains the Pay-to Provider phone#.  This 
 phone# is the contact information for the receiving site to use to contact the
 sending site if there are questions regarding the EOB.  Accounts Receivable
 needs to be able to retrieve this phone# from the IB Site Parameters file in
 order for it to be included in the transferred EOB.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PAY-TO PROVIDER
KEYWORDS: AGENT CASHIER
KEYWORDS: 350.9
COMPONENT/ENTRY POINT: PRVPHONE
VARIABLES: IBIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   This parameter is optional.  If IBIFN is not passed
 in, then the default pay-to provider phone# will be returned.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: NOV 21, 2008

NUMBER: 5287                            IA #: 5287
  DATE CREATED: MAY 16, 2011            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  NAME: E CLAIMS MGMT ENGINE Option Access
  STATUS: Withdrawn

NUMBER: 5288                            IA #: 5288
  DATE CREATED: NOV 10, 2008            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: %ZOSVKR
  NAME: ZOSVKR                          ID: %ZOSVKR
 GENERAL DESCRIPTION:   The pharmacy re-engineering team needs a way to record
 the time it takes to make a call for an order check. Order checks usually take
 less than a second or two (possibly more if an RDI call is necessary). The
 Kernel API $$STATS^%ZOSVKR breaks down the time frame into hundredths of a
 second.  This information is vital for Pharmacy Re-Engineering.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: STATS
 COMPONENT DESCRIPTION:   This entry point retrieves the exact time in
 micro-seconds of when the API is called.  
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   added 4/22/2011 (removed PSO at same time) 
  DATE ACTIVATED: APR 22, 2011

NUMBER: 5289                            IA #: 5289
  CUSTODIAL PACKAGE: 1                  NAME: VA Fileman Option Access
  STATUS: Withdrawn

NUMBER: 5290                            IA #: 5290
  DATE CREATED: NOV 20, 2008            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOAPI6
  NAME: HLO VDEF API                    ID: HLOAPI6
 GENERAL DESCRIPTION:   
     The routine HLOAPI6 is provided as an API to allow VDEF to verify that 
     HLO is installed, running and has all the required parameters for a 
     specific HL7 message type and HL7 event type.  These parameters must 
     be defined prior to use by VDEF users before VDEF can use HLO.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HLO
KEYWORDS: VDEF
COMPONENT/ENTRY POINT: VDEFPCK(LINK,APP,TYPE,EVENT)
 COMPONENT DESCRIPTION:   Inputs : 
        The input parameters are all required if used. 
           1 LINK : Name of HL7 logical link.  
           2 APP  : Name of HLO application.  
           3 TYPE : HL7 Message Type.  
           4 EVENT: HL7 Event type.  
  
 Outputs: Returns 
        With input parameters: 
           1         VDEF Event 'xxxxx' parameters exists HLO Engine.  
           0         HLO running but parameters for VDEF Event 'xxxx'don't
 exist.  
          -1         HLO installed but not running on target system.  
          -2         HLO not installed on target system.  
                
        If input parameters are null: 
           1         HLO installed and running.  
          -1         HLO installed but not running on target system.  
          -2         HLO not installed on target system.  
  
 Variables used: 
         PARM1   - IEN of link in HL7 Logical Link file (#870) 
         PARM2   - IEN of application in HLO APPLICATION registry file (#779.2) 
         PARM3   - IEN of message type in MESSAGE TYPE ACTION subfile (#779.21) 
         RESULT  - Return value.  
SUBSCRIBING PACKAGE: VISTA DATA EXTRACTION FRAMEWORK
  DATE ACTIVATED: JUL 01, 2009

NUMBER: 5291                            IA #: 5291
  FILE NUMBER: 2005                     GLOBAL ROOT: MAG(2005
  DATE CREATED: NOV 23, 2008            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DSIV IMAGING ACCESS
  ID: MAG(2005
GLOBAL REFERENCE: MAG(2005,ATRKID
 GLOBAL DESCRIPTION:   Cross reference of images imported using the Import API 
 GENERAL DESCRIPTION:   The DSIV package is requsting use of the "ATRKID" cross
 reference to get the image IEN in the Image file (#2005) of an image that is
 has imported using the Import API.  The IEN is stored in an SQL database and 
 also verifies that the scanned document, or other image, was successfully 
 uploaded to imaging.  The DocManager piece of DSIV has been tested by VistA
 Imaging.  
  
 Note: DSIV also uses ICR 4526 (MAG4 REMOTE IMPORT) RPC from Imaging. The use
 of the MAG4 REMOTE IMPORT RPC and access to the "ATRKID" cross reference is
 limited to the DSS DocManager application only.  Any other DSIV application
 will need approval before using the RPC or cross reference.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5292                            IA #: 5292
  FILE NUMBER: 36                       GLOBAL ROOT: DIC(36
  DATE CREATED: NOV 23, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INSURANCE CO FILE ACCESS
  ID: DIC(36
 GENERAL DESCRIPTION:   DSIV requests access to the Insurance Company file
 (#36) to do the following for its Insurance Capture Buffer (ICB) application: 
     
 Using file #36 as a file lookup using ^DIC, and as a pointer directly to
 ^DIC(36) in DSI ICB AUDIT file (#19625 - INSURANCE DFN POINTER (#4.12)) 
     
  Also these usages: 
    ^DIC(36,D0,0) 
      .01   NAME                           0;1  Read w/FileMan  
      1     REIMBURSE?                     0;2  Read w/FileMan 
      2     SIGNATURE REQUIRED ON BILL?    0;3  Read/Write w/FileMan 
      .05   INACTIVE                       0;5  Read w/FileMan 
      .12   FILING TIME FRAME              0;12 Read/Write w/FileMan 
      .13   TYPE OF COVERAGE               0;13 Read/Write w/FileMan and 
                                                with pointer to the 
                                                TYPE OF COVERAGE file 
                                                (#355.2). This is the type 
                                                of insurance coverage.  
      .18   STANDARD FTF                   0;18 Read/Write w/FileMan and 
                                                with pointer to the 
                                                INSURANCE FILING TIME FRAME 
                                                file (#355.13).  This is 
                                                the standard filing time 
                                                frame that applies to the 
                                                insurance.  
      .19   STANDARD FTF VALUE             0;19 Read/Write w/FileMan 
    ^DIC(36,D0,.11) 
      .111  STREET ADDRESS [LINE 1]       .11;1 Read w/FileMan 
      .112  STREET ADDRESS [LINE 2]       .11;2 Read w/FileMan 
      .113  STREET ADDRESS [LINE 3]       .11;3 Read w/FileMan 
      .114  CITY                          .11;4 Read w/FileMan 
      .115  STATE                         .11;5 Read w/FileMan 
      .116  ZIP CODE                      .11;6 Read w/FileMan 
      .119  FAX NUMBER                    .11;9 Read/Write w/FileMan 
     ^DIC(36,D0,.13) 
      .131  PHONE NUMBER                  .13;1 Read w/FileMan 
      .132  BILLING PHONE NUMBER          .13;2 Read w/FileMan 
      .133  PRECERTIFICATION PHONE NUMBER .13;3 Read w/FileMan 
     ^DIC(36,D0,3) 
      3.01  TRANSMIT ELECTRONICALLY         3;1 Read/Write w/FileMan 
      3.09  ELECTRONIC INSURANCE TYPE       3;9 Read/Write w/FileMan 
     ^DIC(36,D0,10,0)  (#10) SYNOMYM Multiple (subfile #36.06) 
       .01  SYNONYM                         0;1 Read/Write w/FileMan 
     ^DIC(36,D0,11,0)  (#11) REMARKS Word-processing (subfile #36.011) 
       .01  REMARKS                         0;1 Read/Write w/FileMan 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/24/2025, effective with patch DSSO*2*6, to
 provide read-only access to the Insurance Company file (#36). It will retrieve
 insurance data and return it to APAT.  
  DATE ACTIVATED: SEP 13, 2012

NUMBER: 5293                            IA #: 5293
  FILE NUMBER: 355.3                    GLOBAL ROOT: IBA(355.3
  DATE CREATED: NOV 23, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: GROUP INSURANCE PLAN ACCESS
  ID: IBA(355.3
 GENERAL DESCRIPTION:   Update: IB*2*497 increased the length of the GROUP NAME
 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 2 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. New 
 fields are noted in the field list detail of this ICR.  
  
 DSIV requests access to file 355.3 GROUP INSURANCE PLAN to do the following
 for its Insurance Capture Buffer (ICB) application: 
  
 As a pointer directly to ^DIC(355.3 in ICB AUDIT FILE file (#19625) - GROUP
 PLAN IEN POINTER field (#4.14) 
  
  Also these usages: 
  ^IBA(355.3,D0,0) 
    .01  INSURANCE COMPANY              0;1  Read w/FileMan 
    .02  IS THIS A GROUP POLICY?        0;2  Read w/FileMan 
    .03  *GROUP NAME                    0;3  Read w/FileMan 
    Note: IB*2*497 - replaced by GROUP NAME field (2.01) 
    .04  *GROUP NUMBER                  0;4  Read w/FileMan 
    Note: IB*2*497 - replaced by GROUP NUMBER field (2.02) 
    .05  IS UTILIZATION REVIEW REQUIRED 0;5  Read w/FileMan 
    .06  IS PRE-CERTIFICATION REQUIRED? 0;6  Read w/FileMan 
    .07  EXCLUDE PRE-EXISTING CONDITION 0;7  Read w/FileMan 
    .08  BENEFITS ASSIGNABLE?           0;8  Read w/FileMan 
    .09  TYPE OF PLAN                   0;9  Read w/FileMan 
    .1   INDIVIDUAL POLICY PATIENT      0;10 Read w/FileMan 
    .11  INACTIVE                       0;11 Read w/FileMan 
    .12  AMBULATORY CARE CERTIFICATION  0;12 Read w/FileMan 
    .13  PLAN FILING TIME FRAME         0;13 Read w/FileMan 
    .15  ELECTRONIC PLAN TYPE           0;15 Read w/FileMan 
  
 ^IBA(355.3,D0,2) 
    2.01 GROUP NAME                     2;1  Read w/FileMan 
    2.02 GROUP NUMBER                   2;2  Read w/FileMan 
  
  ^IBA(355.3,D0,6) 
    6.02 BANKING IDENTIFICATION NUMBER  6;2  Read w/FileMan 
    6.03 PROCESSOR CONTROL NUMBER       6;3  Read w/FileMan 
  
  ^IBA(355.3,D0,11,D1,0) 
    .01  COMMENTS      (WP)             0;1  FileMan read/write 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/24/2025, with the release of DSSO*2.0*6
 Advanced Prosthetics Acquisition Tool is documenting its need to retrieve
 patient insurance data. The request is strictly for read only access. No
 fields with read/write access will be used by patch DSSO*2.0*6. No fields with
 * will be used by patch DSSO*2.0*6.  
  DATE ACTIVATED: FEB 21, 2014

NUMBER: 5294                            IA #: 5294
  FILE NUMBER: 355.33                   GLOBAL ROOT: IBA(355.33
  DATE CREATED: NOV 23, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INSURANCE BUFFER FILE ACCESS
  ID: IBA(355.33
 GENERAL DESCRIPTION:   Update: IB*2*497 increased the length of the SUBSCRIBER
 ID field, NAME OF INSURED field, GROUP NAME 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 4
 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 patch. New fields are noted in the 
 field list detail of this ICR.  
  
 DSIV requests access to file 355.33 INSURANCE BUFFER to do the following for
 its Insurance Capture Buffer (ICB) application to add/edit entries.  
  
   ^IBA(355.33,D0,0) 
      .01  DATE ENTERED                    0;1   FileMan read/write 
      .01  DATE ENTERED                    0;1   Laygo new entry into file 
      .02  ENTERED BY                      0;2   FileMan read/write 
      .03  SOURCE OF INFORMATION           0;3   FileMan read/write 
      .04  STATUS                          0;4   FileMan read 
      .05  DATE PROCESSED                  0;5   FileMan r,Direct Global r 
      .06  PROCESSED BY                    0;6   FileMan read 
      .07  NEW COMPANY                     0;7   FileMan read/write 
      .08  NEW GROUP/PLAN                  0;8   FileMan read/write 
      .09  NEW POLICY                      0;9   FileMan read/write 
      .1   DATE VERIFIED                   0;10  FileMan read/write 
      .11  VERIFIED BY                     0;11  FileMan read/write 
      .12  IIV STATUS                      0;12  FileMan read/write 
      .13  OVERRIDE FRESHNESS FLAG         0;13  FileMan read 
      .14  REMOTE LOCATION                 0;14  FileMan read 
      .15  IIV PROCESSED DATE              0;15  FileMan read 
      .17  BPS RESPONSE                    0;17  FileMan read 
   ^IBA(355.33,D0,20) 
      20.01  INSURANCE COMPANY NAME        20;1  FileMan read/write 
      20.02  PHONE NUMBER                  20;2  FileMan read/write 
      20.03  BILLING PHONE NUMBER          20;3  FileMan read/write 
      20.04  PRECERTIFICATION PHONE NUMBER 20;4  FileMan read/write 
      20.05  REIMBURSE?                    20;5  FileMan read/write 
   ^IBA(355.33,D0,21) 
      21.01  STREET ADDRESS [LINE 1]       21;1  FileMan read/write 
      21.02  STREET ADDRESS [LINE 2]       21;2  FileMan read/write 
      21.03  STREET ADDRESS [LINE 3]       21;3  FileMan read/write 
      21.04  CITY                          21;4  FileMan read/write 
      21.05  STATE                         21;5  FileMan read/write 
      21.06  ZIP CODE                      21;6  FileMan read/write 
   ^IBA(355.33,D0,40) 
     40.01  IS THIS A GROUP POLICY?        40;1  FileMan read/write 
     40.02  *GROUP NAME                    40;2  FileMan read/write 
     Note: IB*2*497 - replaced by field 90.01 
     40.03  *GROUP NUMBER                  40;3  FileMan read/write 
     Note: IB*2*497 - replaced by field 90.02 
     40.04  UTILITZATION REVIEW REQUIRED   40;4  FileMan read/write 
     40.05  PRECERTIFICATION REQUIRED      40;5  FileMan read/write 
     40.06  AMBULATORY CARE CERTIFICATION  40;6  FileMan read/write 
     40.07  EXCLUDE PREEXISTING CONDITION  40;7  FileMan read/write 
     40.08  BENEFITS ASSIGNABLE            40;8  FileMan read/write 
     40.09  TYPE OF PLAN                   40;9  FileMan read/write 
     40.1   BANKING IDENTIFICATION NUMBER  40;10 FileMan read/write 
     40.11  PROCESSOR CONTROL NUMBER (PCN) 40;11 FileMan read/write 
   ^IBA(355.33,D0,60) 
     60.01  PATIENT NAME                   60;1  FileMan read/write 
     60.02  EFFECTIVE DATE                 60;2  FileMan read/write 
     60.03  EXPIRATION DATE                60;3  FileMan read/write 
     60.04  *SUBSCRIBER ID                 60;4  FileMan read/write 
     Note: IB*2*497 - replaced by field 90.03 
     60.05  WHOSE INSURANCE                60;5  FileMan read/write 
     60.06  PT. RELATIONSHIP TO INSURED    60;6  FileMan read/write 
     60.07  *NAME OF INSURED               60;7  FileMan read/write 
     Note: IB*2*497 - replaced by field 91.01 
     60.08  INSURED'S DOB                  60;8  FileMan read/write 
     60.09  INSURED'S SSN                  60;9  FileMan read/write 
     60.1   PRIMARY CARE PROVIDER          60;10 FileMan read/write 
     60.11  PRIMARY PROVIDER PHONE         60;11 FileMan read/write 
     60.12  COORDINATION OF BENEFITS       60;12 FileMan read/write 
     60.13  INSURED'S SEX                  60;13 FileMan read/write 
     60.14  PT. RELATIONSHIP - HIPAA       60;14 FileMan read/write 
   ^IBA(355.33,D0,61) 
     61.01  ESGHP?                         61;1  FileMan read/write 
     61.02  SPONSORING EMPLOYER NAME       61;2  FileMan read/write 
     61.03  EMPLOYMENT STATUS              61;3  FileMan read/write 
     61.04  RETIREMENT DATE                61;4  FileMan read/write 
     61.05  SEND BILL TO EMPLOYER          61;5  FileMan read/write 
     61.06  EMPLOYER CLAIMS STREET LINE 1  61;6  FileMan read/write 
     61.07  EMPLOYER CLAIMS STREET LINE 2  61;7  FileMan read/write 
     61.08  EMPLOYER CLAIMS STREET LINE 3  61;8  FileMan read/write 
     61.09  EMPLOYER CLAIMS CITY           61;9  FileMan read/write 
     61.1   EMPLOYER CLAIMS STATE          61;10 FileMan read/write 
     61.11  EMPLOYER CLAIMS ZIP CODE       61;11 FileMan read/write 
     61.12  EMPLOYER CLAIMS PHONE NUMBER   61;12 FileMan read/write 
   ^IBA(355.33,D0,62) 
     62.01  PATIENT ID                     62;1  FileMan read/write 
   ^IBA(355.33,D0,90) 
     90.01    GROUP NAME                   90;1     FileMan read/write 
     90.02    GROUP NUMBER                 90;2     FileMan read/write 
     90.03    SUBSCRIBER ID                90;3     FileMan read/write 
   ^IBA(355.33,D0,91) 
     91.01    NAME OF INSURED              91;1     FileMan read/write 
  
  
       "C" cross reference (Patient)      Direct Global read  
    "AEST" cross reference (Status)       Direct Global read by 
                                          Date Entered "E" entries 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: FEB 21, 2014

NUMBER: 5295                            IA #: 5295
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: NOV 23, 2008            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: DSIV PATIENT ACCESS             ID: DPT(
 GENERAL DESCRIPTION:   DSIV requests access to file 2 PATIENT file to do the
 following for its Insurance Capture Buffer (ICB) application: 
  
   ^DPT(D0,ENR) 
       27.02  PREFERRED FACILITY           ENR;2  Fileman read 
                                                  returned to gui with 
                                                  buffer data 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER

NUMBER: 5296                            IA #: 5296
  FILE NUMBER: 354                      GLOBAL ROOT: IBA(354
  DATE CREATED: NOV 23, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: BILLING PATIENT ACCESS
  ID: IBA(354
 GENERAL DESCRIPTION:   DSIV requests access to file 354 BILLING PATIENT to do
 the following for its Insurance Capture Buffer (ICB) application: 
   
   ^IBA(354,DO)                   Direct global read ($D), lock/unlock 
   ^IBA(354,D0,0) 
      .01       PATIENT NAME                    0;1  Filman read/write 
      .01       PATIENT NAME                    0;1  Laygo new entry 
   ^IBA(354,D0,60) 
       60       NO COVERAGE VERIFICATION DATE   60;1 Fileman read/write 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5297                            IA #: 5297
  FILE NUMBER: 365                      GLOBAL ROOT: IBCN(365
  DATE CREATED: NOV 24, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IIV RESPONSE ACCESS
  ID: IBCN(365
GLOBAL REFERENCE: IBCN(365,D0,0)
FIELD NUMBER: .01                       FIELD NAME: MESSAGE CONTROL ID
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: PAYER
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: BUFFER ENTRY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: TRANSMISSION QUEUE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: TRANSMISSION STATUS
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: DATE/TIME RECEIVED
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DATE/TIME CREATED
  LOCATION: 0;8                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: IBCN(365,"AF")
 GLOBAL DESCRIPTION:   Direct Global read of the Buffer Entry cross reference.  
 GENERAL DESCRIPTION:   DSIV requests access to all fields in file #365 IIV
 RESPONSE to run an EIV Report for its Insurance Capture Buffer (ICB)
 application.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5298                            IA #: 5298
  FILE NUMBER: 356.11                   GLOBAL ROOT: IBE(356.11
  DATE CREATED: NOV 24, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CLAIMS TRK REVIEW TYPE ACCESS
  ID: IBE(356.11
 GENERAL DESCRIPTION:   The DSIV package is requesting FileMan read access to
 file #356.11 CLAIMS TRACKING REVIEW TYPE for the Insurance Capture Buffer
 application in order to list the review types for user selection in the
 insurance review add/edit.  
    
   ^IBE(356.11,D0,0) 
     .01  NAME                0;1    Read w/FileMan 
     .02  CODE                0;2    Read w/FileMan 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5299                            IA #: 5299
  FILE NUMBER: 356.7                    GLOBAL ROOT: IBE(356.7
  DATE CREATED: NOV 24, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CLAIMS TRACKING ACTION ACCESS
  ID: IBE(356.7
 GENERAL DESCRIPTION:   The DSIV package is requesting FileMan read access to
 file #356.7 CLAIMS TRACKING ACTION for the Insurance Capture Buffer
 application in order to list the actions for user selection in the insurance
 review add/edit.  
   
   ^IBE(356.7,D0,0) 
     .01  NAME                0;1    Read w/FileMan 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5300                            IA #: 5300
  FILE NUMBER: 424                      GLOBAL ROOT: PRC(424
  DATE CREATED: MAR 12, 2009            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS FILE 424                   ID: PRC(424
 GENERAL DESCRIPTION:   The Fee Basis Claims system accesses the 1358 DAILY
 RECORD (#424) file in order to look up entries using either the Interface ID
 cross-reference or the B cross reference.  
  
    ^PRC(424,"B")  Used for IEN lookups 
    ^PRC(424,"E")  Used for Interface ID lookups 
    ^PRC(424,"AD") Used to check for existence of the Authorization IEN 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5301                            IA #: 5301
  FILE NUMBER: 420                      GLOBAL ROOT: PRC(420
  DATE CREATED: MAR 12, 2009            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS FILE 420                   ID: PRC(420
GLOBAL REFERENCE: PRC(420,FBSTA,1,+FBFCP,1,DUZ)
FIELD NUMBER: .01                       FIELD NAME: CONTROL POINT USER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   (#.01) CONTROL POINT USER [1P:200] Checking for existance
 of the node only 
FIELD NUMBER: 1                         FIELD NAME: LEVEL OF ACCESS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   (#1) LEVEL OF ACCESS [2S], used to pass into EN1^PRCSUT31 
 GENERAL DESCRIPTION:   The Fee Basis Claims system accesses the FUND CONTROL
 POINT.  It uses this access to validate FCP/Site combinations for users.  
   $D(^PRC(420,FBSTA,1,+FBFCP,1,DUZ,0)) 
   ^PRC(420,SITE,1,"B",FBFCP) 
   $D(^PRC(420,"A",DUZ,SITE,+FBFCP)) 
   $P(^PRC(420,FBSTA,1,+FBFCP,1,DUZ,0),U,2) 
   $O(^PRC(420,"B") added with DSIF*3.2*1 (to obtain all station 
             numbers for a user) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5302                            IA #: 5302
  FILE NUMBER: 43.4                     GLOBAL ROOT: DIC(43.4
  DATE CREATED: MAR 12, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS FILE 43.4                  ID: DIC(43.4
 GENERAL DESCRIPTION:   The Fee Basis Claims system accesses the VA ADMITTING
 REGULATION (#43.4) file as part of validity checks in the application.  
  
   ^DIC(43.4,D0,0) 
     .01     NAME             0;1    Fileman r,Global r ($D check) 
     2       CFR #            0;3    Fileman r 
     4       ACTIVE           0;4    Fileman r 
     5       NURSING HOME     0;5    Fileman r 
     6       EDR CODE         0;6    Fileman r 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5303                            IA #: 5303
  FILE NUMBER: 350                      GLOBAL ROOT: IB(
  DATE CREATED: NOV 24, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: DSIV INTEGRATED BILLING ACTION  ID: IB(
 GENERAL DESCRIPTION:   The DSIV package is requesting access to file #350
 INTEGRATED BILLING ACTION for its Insurance Capture Buffer (ICB) application
 to search for all charges on hold due to insurance for a specific patient then
 update the On Hold Date to the current date, or send to the billing software
 to release the charges depending on the incoming flag.  
  
   ^IB("AH" patient charges hold x-ref   Direct Global read 
  
   ^IB(D0,0) 
     .05          STATUS         0;5     Direct Global read 
   ^IB(D0,1) 
     16           ON HOLD DATE   1;6     Direct Global read, Fileman w 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed

NUMBER: 5304                            IA #: 5304
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: NOV 24, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PATIENT INSURANCE ACCESS
  ID: DPT(
 GENERAL DESCRIPTION:   The DSIV package is requesting FileMan read access to
 the Insurance Type data in file #2 PATIENT for the Insurance Capture Buffer
 application in order to display insurance information to the user.  
  
 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.  
  
 Update:  IB*2*528 increased the length of the COMMENT-PATIENT POLICY field 
 (2.312, 1.08) from 80 characters to 250 characters; and therefore it was 
 necessary to move this field to a new subscript in the INSURANCE TYPE sub-file 
 (2.312). All subscribers to this ICR will need to make the necessary changes
 in their applications to reference the new field.  Old and new fields are
 noted in the INSURANCE TYPE multiple details below.  
  
  
   ^DPT(D0,.31) 
    .3192  COVERED BY HEALTH INSURANCE?  .31;11  Fileman read/write 
                                                 insurance verification  
   INSURANCE TYPE MULTIPLE access: 
    ^DPT(D0,.312,D1,0)                       
      .01   INSURANCE TYPE                 0;1  Read w/FileMan 
       1    *SUBSCRIBER ID                 0;2  Read w/FileMan 
       Note: IB*2*497 - Replaced by field 7.02 
       2    *GROUP NUMBER                  0;3  Read w/FileMan 
       3    INSURANCE EXPIRATION DATE      0;4  Read w/FileMan 
       6    WHOSE INSURANCE                0;6  Read w/FileMan 
       8    EFFECTIVE DATE OF POLICY       0;8  Read w/FileMan 
       15   *GROUP NAME                    0;15 Read w/FileMan 
       16   PT. RELATIONSHIP TO INSURED    0;16 Read w/FileMan 
       17   *NAME OF INSURED               0;17 Read w/FileMan 
       Note: IB*2*497 - Replaced by field 7.01 
      .18   GROUP PLAN                     0;18 Read w/FileMan 
      .2    COORDINATION OF BENEFITS       0;20 Read w/FileMan 
    ^DPT(D0,.312,D1,1)                       
      1.01  DATE ENTERED                   1;1  Read w/FileMan 
      1.02  ENTERED BY                     1;2  Read w/FileMan 
      1.03  DATE LAST VERIFIED             1;3  Read w/FileMan 
      1.04  VERIFIED BY                    1;4  Read w/FileMan 
      1.05  DATE LAST EDITED               1;5  Read w/FileMan 
      1.06  LAST EDITED BY                 1;6  Read w/FileMan 
      1.08  *COMMENT - PATIENT POLICY      1;8  Read w/FileMan 
      Note:  IB*2*528 - 1.08 replaced by COMMENT-SUBSCRIBER POLICY multiple 
      1.09  SOURCE OF INFORMATION          1;9  Read w/FileMan 
      1.1   DATE OF SOURCE OF INFORMATION  1;10 Read w/FileMan 
    ^DPT(D0,.312,D1,2) 
      2.01  SEND BILL TO EMPLOYER          2;1  Read w/FileMan 
      2.02  EMPLOYER CLAIMS STREET ADDRESS 2;2  Read w/FileMan 
      2.03  EMPLOY CLAIM ST ADDRESS LINE 2 2;3  Read w/FileMan 
      2.04  EMPLOY CLAIM ST ADDRESS LINE 3 2;4  Read w/FileMan 
      2.05  EMPLOYER CLAIMS CITY           2;5  Read w/FileMan 
      2.06  EMPLOYER CLAIMS STATE          2;6  Read w/FileMan 
      2.07  EMPLOYER CLAIMS ZIP CODE       2;7  Read w/FileMan 
      2.08  EMPLOYER CLAIMS PHONE          2;8  Read w/FileMan 
      2.015 SUBSCRIBER'S EMPLOYER NAME     2;9  Read w/FileMan 
      2.1   ESGHP                          2;10 Read w/FileMan 
      2.11  EMPLOYMENT STATUS              2;11 Read w/FileMan 
      2.12  RETIREMENT DATE                2;12 Read w/FileMan 
    ^DPT(D0,.312,D1,3)   
      3.01  INSURED'S DOB                  3;1  Read w/FileMan 
      3.02  INSURED'S BRANCH               3;2  Read w/FileMan 
      3.03  INSURED'S RANK                 3;3  Read w/FileMan 
      3.04  POLICY NOT BILLABLE            3;4  Read w/FileMan 
      3.05  INSURED'S SSN                  3;5  Read w/FileMan 
      3.06  INSURED'S STREET 1             3;6  Read w/FileMan 
      3.07  INSURED'S STREET 2             3;7  Read w/FileMan 
      3.08  INSURED'S CITY                 3;8  Read w/FileMan 
      3.09  INSURED'S STATE                3;9  Read w/FileMan 
      3.1   INSURED'S ZIP                  3;10 Read w/FileMan 
      3.11  INSURED'S PHONE                3;11 Read w/FileMan 
      3.12  INSURED'S SEX                  3;12 Read w/FileMan 
    ^DPT(D0,.312,D1,4)    
      4.01  PRIMARY CARE PROVIDER          4;1  Read w/FileMan 
      4.02  PRIMARY PROVIDER PHONE         4;2  Read w/FileMan 
      4.03  PT. RELATIONSHIP - HIPAA       4;3  Read w/FileMan 
    ^DPT(D0,.312,D1,5)    
      5.01  PATIENT ID                     5;1  Read w/FileMan 
      5.02  SUBSCRIBER'S SEC QUALIFIER(1)  5;2  Read w/FileMan 
      5.03  SUBSCRIBER'S SEC ID(1)         5;3  Read w/FileMan 
      5.04  SUBSCRIBER'S SEC QUALIFIER(2)  5;4  Read w/FileMan 
      5.05  SUBSCRIBER'S SEC ID(2)         5;5  Read w/FileMan 
      5.06  SUBSCRIBER'S SEC QUALIFIER(3)  5;6  Read w/FileMan 
      5.07  SUBSCRIBER'S SEC ID(3)         5;7  Read w/FileMan 
      5.08  PATIENT'S SEC QUALIFIER(1)     5;8  Read w/FileMan 
      5.09  PATIENT'S SECONDARY ID(1)      5;9  Read w/FileMan 
      5.1   PATIENT'S SEC QUALIFIER(2)     5;10 Read w/FileMan 
      5.11  PATIENT'S SECONDARY ID(2)      5;11 Read w/FileMan 
      5.12  PATIENT'S SEC QUALIFIER(3)     5;12 Read w/FileMan 
      5.13  PATIENT'S SECONDARY ID(3)      5;13 Read w/FileMan 
    ^DPT(D0,.312,D1,7)    
      7.01  NAME OF INSURED                7;1  Read w/FileMan 
      7.02  SUBSCRIBER ID                  7;2  Read w/FileMan 
    ^DPT(D0,.312,D1,13,D2,0) 
       .01 COMMENT DATE                   0;1  Read w/FileMan 
       .02 LAST EDITED                    0;2  Read w/FileMan 
 ^DPT(D0,.312,D1,13,D2,1) 
       .03 COMMENT                        1;1  Read w/FileMan 
     
  
  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/24/2025, with the release of DSSO*2.0*6
 Advanced Prosthetics Acquisition Tool is documenting its need to retrieve
 patient insurance data. The request is strictly for read only access. No
 fields with read/write access will be used by patch DSSO*2.0*6. No fields with
 * will be used by patch DSSO*2.0*6.  
  DATE ACTIVATED: JUL 24, 2017

NUMBER: 5305                            IA #: 5305
  FILE NUMBER: 355.12                   GLOBAL ROOT: IBE(355.12
  DATE CREATED: NOV 24, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SOURCE OF INFORMATION ACCESS
  ID: IBE(355.12
 GENERAL DESCRIPTION:   The DSIV package is requesting FileMan read access to
 file #355.12 SOURCE OF INFORMATION for the Insurance Capture Buffer
 application in order to list the sources for user selection when creating a
 buffer entry.  
  
   ^IBE(355.12,D0,0) 
     .01  CODE               0;1    Read w/FileMan 
     .02  DESCRIPTION        0;2    Read w/FileMan 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5306                            IA #: 5306
  DATE CREATED: DEC 08, 2008            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSJBLDOC
  NAME: PSJBLDOC                        ID: PSJBLDOC
 GENERAL DESCRIPTION:   This entry point builds the drug information for
 patient's orders entered in the Inpatient Medications package.  The data
 returned is used in First Data Bank order checks.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: IN
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   The parameter reference used as a subscript to
 identify the order checks data in the ^TMP global.  
VARIABLES: PDRG                         TYPE: Input
 VARIABLES DESCRIPTION:   The drug array contained the prospective drugs.  Drug
 array is in the format of PDRG(n)=IEN (#50) ^ Drug name;    Where n is a
 sequential number.  Drug name can be Orderable Item name, or the Generic name. 
 
VARIABLES: PTYP                         TYPE: Input
 VARIABLES DESCRIPTION:   Package information in the format of: P1;P2 where
 P1="I" for Inpatient & "O" for Outpatient, P2= PSJ order#.  
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,"IN","PROFILE",PSJPON)=GCN ^ VUID ^ IEN
 (File#50) ^ Drug Name ^ CPRS Order Number ^ Package 
  
 Where: 
  
 PSJPON = Pharmacy order number in the format of P1;P2;P3;P4 P1 - Order type.
 It can be Z=Outpatient Prospective Drug, I=Inpatient, O=Outpatient, R=RDI; P2
 - Order number; P3 - Drug type (PROFILE/PROSPECTIVE); P4 - Counter 
  
 GCN = GCN sequence number (#50.68) 
  
 VUID = VA PRODUCT (#50.68) 
  
 IEN = Dispense drug internal entry number (#50) 
  
 Drug Name = Drug name of either the  Orderable Item name (#50.7) or the 
 Generic Drug name (#50) 
  
 CPRS Order Number = Internal entry number for order in ^OR(100 if available 
  
 Package = Package indication -  "O" for Outpatient; "I" for Inpatient 
  
 PSJCLCOD = Clinic Order Code (1-5) 
  
 PSJCLINF = Clinic Order Flag 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: JUL 15, 2014

NUMBER: 5307                            IA #: 5307
  DATE CREATED: DEC 10, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCNBLL
  NAME: DSIV CALLS TO IBCNBLL           ID: IBCNBLL
 GENERAL DESCRIPTION:   The Insurance Capture Buffer (ICB) application uses the
 following APIs in IBCNBLL to determine if there are bills on hold for a
 patient and to get the Symbol for the buffer entry.  The symbol is displayed
 in the application and will also denote if the buffer entry has been manually
 verified.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$HOLD
 COMPONENT DESCRIPTION:   This tag is called to find out if there are bills on
 hold for a patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient pointer from file #2 PATIENT.  
COMPONENT/ENTRY POINT: $$SYMBOL(IBBUFDA)
 COMPONENT DESCRIPTION:   This tag returns the Symbol for the buffer entry.  
VARIABLES: IBBUFDA                      TYPE: Input
 VARIABLES DESCRIPTION:   The Buffer ien from file #355.33 INSURANCE BUFFER 
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5308                            IA #: 5308
  DATE CREATED: DEC 10, 2008            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Other
  NAME:  LAB SERVICES TO #2817          STATUS: Pending

NUMBER: 5309                            IA #: 5309
  DATE CREATED: DEC 10, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCNERP2
  NAME: DSIV CALL TO IBCNERP2           ID: IBCNERP2
 GENERAL DESCRIPTION:   The Insurance Capture Buffer (ICB) application uses the
 X12 API in IBCNERP2 to convert the X12 code to a readable format for a report. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$X12(FILE,CODE,FLD)
 COMPONENT DESCRIPTION:   Converts an X12 element to readable text.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   The X12 file#, for example: 365.011.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   The X12 code, for example: 1 
VARIABLES: FLD                          TYPE: Input
 VARIABLES DESCRIPTION:   The field definition number if you want the field
 title with the return (not required), for example: .02 
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5310                            IA #: 5310
  DATE CREATED: MAR 12, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: DGRPU                        NAME: FBCS ACCESS TO DGRPU
  ID: DGRPU
 GENERAL DESCRIPTION:   These components are used by the FBCS application to
 format the patient address data.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: AL(DGLEN)
 COMPONENT DESCRIPTION:   called if output should be kept within line length
 limits.  This component falls through to the AL component.  
VARIABLES: DGLEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Available line length 
COMPONENT/ENTRY POINT: AL
 COMPONENT DESCRIPTION:   Format address(s) 
VARIABLES: DGRP(                        TYPE: Input
 VARIABLES DESCRIPTION:   Address NODE from PATIENT (#2) file to be formatted
 (e.g. .11,.121) 
VARIABLES: DGA(                         TYPE: Output
 VARIABLES DESCRIPTION:   Formatted array of address information 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5311                            IA #: 5311
  DATE CREATED: MAR 12, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGSDUTL                      NAME: FBCS ACCESS TO DGSDUTL
  ID: DGSDUTL
 GENERAL DESCRIPTION:   These components are used by the FBCS application for
 patient demographic inquiries.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$PCTEAM(DFN,DATE,ASSTYPE)
 COMPONENT DESCRIPTION:   Get Primary Care team Returns the pointer to file
 404.51 if there is a team or 0 if no team found.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN (file #2) 
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   Date of interest (default=DT) 
VARIABLES: ASSTYPE                      TYPE: Input
 VARIABLES DESCRIPTION:   Assignment Type (default=1) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5312                            IA #: 5312
  FILE NUMBER: 355.31                   GLOBAL ROOT: IBE(355.31
  DATE CREATED: DEC 10, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PLAN LIMITATION CATEGORY ACCESS
  ID: IBE(355.31
 GENERAL DESCRIPTION:   The DSIV package is requesting FileMan read access to
 file #355.31 PLAN LIMITATION CATEGORY for the Insurance Capture Buffer
 application in order to perform coverage limitation add/edits.  
   
   ^IBE(355.31,D0,0) 
     .01  NAME              0;1    Read w/FileMan 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5313                            IA #: 5313
  FILE NUMBER: 356                      GLOBAL ROOT: IBT(356
  DATE CREATED: DEC 10, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CLAIMS TRACKING ACCESS
  ID: IBT(356
 GENERAL DESCRIPTION:   The DSIV package is requesting FileMan read access to
 file #356 CLAIMS TRACKING for the Insurance Capture Buffer application in
 order to look up and display a Claims Tracking record to be associated with an
 Insurance Review.  
   
   ^IBT(356,D0,0) 
     .01  ENTRY ID                0;1   Read w/FileMan 
     .03  VISIT                   0;3   Read w/FileMan 
     .04  OUTPATIENT ENCOUNTER    0;4   Read w/FileMan 
     .05  ADMISSION               0;5   Read w/FileMan 
     .06  EPISODE DATE            0;6   Read w/FileMan 
     .07  ADMISSION TYPE          0;7   Read w/FileMan 
     .18  EVENT TYPE              0;18  Read w/FileMan 
     .2   INACTIVE                0;20  Read w/FileMan 
     .31  SPECIAL CONSENT ROI     0;31  Read w/FileMan 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5314                            IA #: 5314
  FILE NUMBER: 356.1                    GLOBAL ROOT: IBT(356.1
  DATE CREATED: DEC 10, 2008            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HOSPITAL TRACKING ACCESS
  ID: IBT(356.1
 GENERAL DESCRIPTION:   The DSIV package is requesting FileMan read access to
 file #356.1 HOSPITAL TRACKING for the Insurance Capture Buffer application in
 order to look up and display a Hospital Tracking record to be associated with 
 an Insurance Review as a Related Review.  
  
  ^IBT(356.1,D0,0) 
    .01  REVIEW DATE            0;1   Read w/FileMan 
    .02  TRACKING ID            0;2   Read w/FileMan 
    .07  SPECIALTY FOR REVIEW   0;7   Read w/FileMan 
    .19  ACTIVE                 0;19  Read w/FileMan 
    .2   NEXT REVIEW DATE       0;20  Read w/FileMan 
    .21  REVIEW STATUS          0;21  Read w/FileMan 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5315                            IA #: 5315
  DATE CREATED: DEC 12, 2008
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GETCSLT ORQQCN1
  NAME: ORQQCN GET CONSULT              REMOTE PROCEDURE: ORQQCN GET CONSULT
  ID: GETCSLT ORQQCN1
 GENERAL DESCRIPTION:   This rpc is used to get consult and associated TIU
 records using a Consult ID from File 123 as input.  
  
 Output results are: RESULTS[0] = ^GMR(123 zero node 
                     RESULTS[i..j] = TIU records 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORQQCN
KEYWORDS: GETCSLT
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   CPRS approved adding Dental as a subscriber for Dental
 Record Manager to this ICR on 8/11/2009 to document existing references. 
 However the update was not made to the ICR until 2/9/18.  
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5316                            IA #: 5316
  DATE CREATED: DEC 12, 2008
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ADMNCLO TIUSRVPT
  NAME: TIU SET ADMINISTRATIVE CLOSURE
  REMOTE PROCEDURE: TIU SET ADMINISTRATIVE CLOSURE
  ID: ADMNCLO TIUSRVPT
 GENERAL DESCRIPTION:   This remote procedure sets the file attributes
 necessary to close a document by administrative action (either manually or by
 scanning a paper document that doesn't require the signature of an author as a
 typical TIU Document would).  
    
 Input params:  TIUDA    IEN of document in 8925 
                MODE     alphabetic code for manner closed: 
                           "S" for Scanned (default) 
                           "M" for Manual. 
                PERSON   User who closed the document (default=DUZ) 
  
 Output: Success = IEN of document or 0^message 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIUSRVPT
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   Caregiver Tool supporting the Caregivers Title 1,
 Sections 101-104 (CareT) application will be using the TIU SET ADMINISTRATIVE
 CLOSURE RPC.  
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/18/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce  product sharing the CRMS
 namespace. The CRMS VAHC Remote Application includes the CRMS VAHC Option,
 which includes required RPCs. TIU SET ADMINISTRATIVE CLOSURE is one of the
 Remote Procedures included in the CRMS VAHC Option. The Remote Application
 uses Data Access Services/National Health Information Network (DAS/NHIN) as
 the middleware to interface with VistA.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 9/15/25, This RPC usage is not new with
 OR*3.0*508, but rather found during ICR review of the OR CPRS GUI CHART
 context option. In all likelihood the ICR was created specifically for the
 usage within CPRS GUI, but OE/RR was never added as a subscriber.  
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5317                            IA #: 5317
  DATE CREATED: DEC 23, 2008
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICDUZ
  NAME: DSICDUZ                         ORIGINAL NUMBER: 5317
  ID: DSICDUZ
 GENERAL DESCRIPTION:   
    This ICR records API's in the DSICDUZ routine.  This routine is used by DSS
 applications for NEW PERSON (#200) file accesses.  The routine is a wrapper
 around Standard FILEMAN calls to derive results.  
  
    Associated RPCs: DSIC ACTIVE USER, DSIC USER DEF DIV, 
                     DSIC USER ID, DSIC ACTIVE USER LIST, 
                     DSIC ACTIVE PERSON CLASS, DSIC ACTIVE CPRS PROVIDER 
    
  
  
      ROUTINE: DSICDUZ 
    COMPONENT:  ACT 
    VARIABLES:  DSIC   Type: Output 
                                     A subscripted array with a value of 1 
                                     or 0 to indicated if user is active.  
  
 XDUZ   Type: Input   (Required) 
                                     A single value or a subscripted array 
                                     of security keys to be evaluated.  
                DSISCR Type: Input   (Optional) 
                                     DSISCR(n) = string 
                                                where n = 0,1,2,3,4,...  
                                     Allowable formats of DSISCR(n) = 
                                           flag^val1^val2^val3^..  
  
                                      security key ck = KEY^security key 
                                      name 
                                      kernel param ck = PARM^parameter 
                                      name^ parameter instance 
                                      M code = M^<return message>^ 
                                                 <executable M code which 
                                                  sets $T> 
  
                FUN    Type: Input (Optional)  Default is zero (0).  
                                     I $G(FUN) then extrinsic function, 
                                     else RPC.  
                                       
                   This API is used by the "DSIC USER ACTIVE USER" rpc. 
                   This API can be used to verify if a user is an active 
                   VistA user.  
                   The calling routine will send the DUZ to check and the 
                   API will return a subscripted array with a value of 1 
                   (user owns key) or 0 (key not found).  
  
    COMPONENT:  CK 
    VARIABLES:  XDUZ   Type: Input   (Required) 
                                      A single DUZ value to check.  
     
  
  
    This API does a basic check on a DUZ to see if user is active. 
                
    COMPONENT:  DIV 
    VARIABLES:  DSIC   Type: Output 
                                      return p1^p2^p3: 
  
                                      p1=pointer to file 4 
                                      p2=institution name 
                                      p3=station number 
   
                XDUZ   Type: Input   (Required) default is currect user 
                                     DUZ.  
                                     A single value or a subscripted array 
                                     of security keys to be evaluated.  
                SITE   Type: Input   (Optional) 
                                     if SITE=1 and user has no divisions, 
                                     then return facility's  default 
                                     division 
                                    
                FUN    Type: Input (Optional)  Default is zero (0).  
                                     I $G(FUN) then extrinsic function, 
                                     else RPC.  
                                       
                   Return default division for user.  If that user has 
                   only one division in the file 200 DIVISION multiple, 
                   then that entry is assumed to be the default division 
                   unless it is explicitly marked as NO.  This component is 
                   used for the "DSIC USER DEF DIV" rpc.  
  
    COMPONENT:  ID 
    VARIABLES:  DSIC   Type: Output 
                                     return p1^p2^p3^p4 for n=1,2,3,... 
                                     where 
                                     If error, return -1^message 
                                     If RPC or M API, 
                                     return List[n] = p1^p2^p3^p4 
                                       for n=1,2,3,4,...  
                                     If Ext. Function, 
                                     return 
                                       p1^p2^p3^p4;p1^p2^p3^p4;p1^p2^p3^p4;...  
                                        where p1 - ID mnemonic 
                                              p2 - ID value 
                                              p3 - location 
                                                (valid for OAI mnemonics 
                                                 only) 
                                              p4 = 1 (valid for OAI only.) 
                                                     (If 1, then default 
                                                      Alt ID) 
   
                XDUZ   Type: Input   pointer to NEW PERSON file, 
                                         if optional default to DUZ 
  
                FLAGS  Type: Input   (Optional) 
                                     default to "AaDNSTVv" 
                                     FLAGS["A" - return alternate IDS in 
                                                 field 21600 only 
                                           "a" - return default alternate 
                                                 ID only 
                                                 - either one must be 
                                                   flagged as default or if 
                                                   there is only one entry 
                                                   in alt id.  
                                           "D" - return DEA# 
                                           "N" - return NPI# 
                                           "S" - return SSN 
                                           "T" - TAX ID 
                                           "v" - VA# 
                                           "V" - VPID 
                                    
                FUN    Type: Input (Optional)  Default is zero (0).  
                                     I $G(FUN) then extrinsic function, 
                                     else RPC.  
                                       
                   Return all user IDs for a given user.  This component 
                   is used for the "DSIC USER ID" rpc.  
  
    COMPONENT:  LIST 
    VARIABLES:  DSIC   Type: Output 
                   Return ^TMP("DSIC",$J,"DILIST",#,0) = p1^p2^p3^...^p8  
                       where: 
                          p1 = ien                      p6 = initials 
                          p2 = name (.01 field)         p7 = title 
                          p3 = sig block printed name   p8 = service 
                          p4 = sig block title          p9 = division 
                          p5 = first m last 
   
                VAL   Type: Input   (Required) 
                                     lookup value for NEW PERSON file.  
                                    
                SCR   Type: Input   (Optional) 
                                     array of additional screens to 
                                     perform: 
  
                                     string   where n = 0,1,2,3,4,...  
                                     Allowable formats of SCR(n) = 
                                                    flag^val1^val2^val3^..  
                                       security key ck = KEY^security key 
                                       name 
                                       kernel param ck = PARM^parameter 
                                       name^ parameter instance 
                                       M code = M^<return message>^ 
                                       <executable M code which sets $T> 
                                      
                   Return list of active users for a lookup value.  This 
                   component is used for the "DSIC ACTIVE USER LIST" rpc.  
  
  
  
    COMPONENT:  PER 
    VARIABLES:  DSIC   Type: Output 
  
                   Return user's current active person classification for 
                   PCE.  
                           Return p1^p2^p3^...^p8  where 
                           p1 = IEN to file 8932.1     p5 = Effective date 
                           p2 = Occupation             p6 = expiration date 
                           p3 = specialty              p7 = VA Code 
                           p4 = sub-specialty          p8 = specialty code 
  
                USER   Type: Input   pointer to NEW PERSON file, 
                                         if optional default to DUZ.  
                                    
                DATE    Type: Input   ;  DATE - default=today 
                                         Fileman date to check for 
                                             active person class.  
                                    
                FUN    Type: Input (Optional)  Default is zero (0).  
                                     I $G(FUN) then extrinsic function, 
                                     else RPC.  
                                       
                   Return user's current active person classification for 
                   PCE. This component is used for the "DSIC ACTIVE PERSON 
                   CLASS" rpc.  
  
  
    COMPONENT:  PROV 
    VARIABLES:  DSIC   Type: Output 
  
                   Return: 3 if active user 
                           2 if user is active via the XUORES security key 
                           1 if user is a RDV visitor and you passed RDV=1 
                           0 if user is a RDV visitor and you passed RDV=0 
                           -1^message if problems or not a provider 
  
                XDUZ   Type: Input  (Required) default is current user DUZ.  
  
                          A single value of the DUZ to return values for.  
  
  
                RDV    Type: Input   (Optional) default = today 
                           Boolean flag to indicate whether or not to 
                           include remote data view visitors - default to 0 
                           to not include.  
                                    
                FUN    Type: Input (Optional)  Default is zero (0).  
                          I $G(FUN) then extrinsic function, else RPC.  
                                       
                   Return all user IDs for a given user.  This component 
                   is used for the "DSIC ACTIVE CPRS PROVIDER" rpc.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ACT
 COMPONENT DESCRIPTION:   
    VARIABLES:  DSIC   Type: Output 
                                     A subscripted array with a value of 1 
                                     or 0 to indicated if user is active.  
                XDUZ   Type: Input  (Required) 
                                     A single value or a subscripted array 
                                     of security keys to be evaluated.  
                DSISCR Type: Input  (Optional) 
                     DSISCR(n) = string where n = 0,1,2,3,4,... Allowable 
                                 formats of DSISCR(n) = 
                                   flag^val1^val2^val3^..  
  
                                   security key ck = KEY^security key name 
                                   kernel param ck = PARM^parameter name^ 
                                                     parameter instance 
                                      M code = M^<return message>^ 
                                         <executable M code which sets $T> 
  
                FUN    Type: Input (Optional)  Default is zero (0).  
                                     I $G(FUN) then extrinsic function, 
                                     else RPC.  
                                       
                   This API is used by the "DSIC USER ACTIVE USER" rpc. 
                   This API can be used to verify if a user is an active 
                   VistA user.  The calling routine will send the DUZ to 
                   check and the api will return a subscripted array with a 
                   value of 1 (user owns key) or 0 (key not found).  
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   A subscripted array with a value of 1 or 0 to
 indicate if user is active. 1 = Active, 0 = Inactive.  
VARIABLES: XDUZ                         TYPE: Input
 VARIABLES DESCRIPTION:   A single value or a subscripted array of security
 keys to be evaluated.  
VARIABLES: DSISCR                       TYPE: Input
 VARIABLES DESCRIPTION:   DSISCR(n) = string where n = 0,1,2,3,4,...  
  
 Allowable formats of DSISCR(n) = flag^val1^val2^val3^.. where: 
  
             security key ck = KEY^security key name 
  
             kernel param ck = PARM^parameter name^ parameter instance 
  
             M code = M^<return message>^ <executable M code which sets $T> 
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   If $G(FUN) then extrinsic function, else RPC.  
COMPONENT/ENTRY POINT: CK
 COMPONENT DESCRIPTION:   This API does a basic check on a DUZ to see if user
 is active.  
VARIABLES: XDUZ                         TYPE: Input
 VARIABLES DESCRIPTION:   A single DUZ value to check.  
COMPONENT/ENTRY POINT: DIV
 COMPONENT DESCRIPTION:   Return default division for user.  If that user has
 only one division in the file 200 DIVISION multiple, then that entry is
 assumed to be the default division unless it is explicitly marked as NO.  This
 component is used for the "DSIC USER DEF DIV" rpc.  
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   return p1^p2^p3: 
  
   p1=pointer to file 4 
   p2=institution name 
   p3=station number 
VARIABLES: XDUZ                         TYPE: Input
 VARIABLES DESCRIPTION:   A single value or a subscripted array of security
 keys to be evaluated.  
VARIABLES: SITE                         TYPE: Input
 VARIABLES DESCRIPTION:   if SITE=1 and user has no divisions, then return
 facility's  default division.  
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   Default is zero (0). I $G(FUN) then extrinsic
 function, else RPC 
COMPONENT/ENTRY POINT: ID
 COMPONENT DESCRIPTION:   Return all user IDs for a given user.  This component
 is used for the "DSIC USER ID" rpc.  
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   return p1^p2^p3^p4 for n=1,2,3,... where 
                                     If error, return -1^message 
                                     If RPC or M API, 
                                     return List[n] = p1^p2^p3^p4 
                                       for n=1,2,3,4,...  
                                     If Ext. Function, 
                                     return 
                                       p1^p2^p3^p4;p1^p2^p3^p4;p1^p2^p3^p4;...  
                                        where p1 - ID mnemonic 
                                              p2 - ID value 
                                              p3 - location 
                                             (valid for OAI mnemonics only) 
                                              p4 = 1 (valid for OAI only.) 
                                              (If 1, then default Alt ID) 
VARIABLES: XDUZ                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to NEW PERSON (#200) file, if optional
 default to DUZ.  
VARIABLES: FLAGS                        TYPE: Input
 VARIABLES DESCRIPTION:   default to "AaDNSTVv".  
  
  FLAGS["A" - return alternate IDS in field 21600 only 
        "a" - return default alternate ID only - either one must be flagged 
              as default or if there is only one entry in alt id.  
        "D" - return DEA# 
        "N" - return NPI# 
        "S" - return SSN 
        "T" - TAX ID 
        "v" - VA# 
        "V" - VPID 
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   Default is zero (0). I $G(FUN) then extrinsic
 function, else RPC.  
COMPONENT/ENTRY POINT: LIST
 COMPONENT DESCRIPTION:   Return list of active users for a lookup value.  This
 component is used for the "DSIC ACTIVE USER LIST" rpc.  
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   Return ^TMP("DSIC",$J,"DILIST",#,0) = p1^p2^p3^...^p8 
 where: 
  
                          p1 = ien                      p6 = initials 
                          p2 = name (.01 field)         p7 = title 
                          p3 = sig block printed name   p8 = service 
                          p4 = sig block title          p9 = division 
                          p5 = first m last 
VARIABLES: VAL                          TYPE: Input
 VARIABLES DESCRIPTION:   lookup value for NEW PERSON file.  
VARIABLES: SCR                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Array of additional screens to perform: 
  
           string   where n = 0,1,2,3,4,...  
    Allowable formats of SCR(n) = flag^val1^val2^val3^..  
  
                                  security key ck = KEY^security key name 
                                  kernel param ck = PARM^parameter name^ 
                                                         parameter instance 
                                  M code = M^<return message>^ 
                                           <executable M code which sets $T 
COMPONENT/ENTRY POINT: PER
 COMPONENT DESCRIPTION:   Return user's current active person classification
 for PCE. This component is used for the "DSIC ACTIVE PERSON CLASS" rpc.  
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   Return user's current active person classification
 for PCE.  
                           
 Return p1^p2^p3^...^p8  where 
             p1 = IEN to file 8932.1     p5 = Effective date 
             p2 = Occupation             p6 = expiration date 
             p3 = specialty              p7 = VA Code 
             p4 = sub-specialty          p8 = specialty code 
VARIABLES: USER                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to NEW PERSON (#200) file.  If optional,
 default to DUZ.  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   Default=today.  Fileman date to check for active
 person class.  
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   Default is zero (0). I $G(FUN) then extrinsic
 function, else RPC.  
COMPONENT/ENTRY POINT: PROV
 COMPONENT DESCRIPTION:   Return all user IDs for a given user.  This component
 is used for the "DSIC ACTIVE CPRS PROVIDER" rpc.  
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   Return: 3 if active user 
         2 if user is active via the XUORES security key 
         1 if user is a RDV visitor and you passed RDV=1 
         0 if user is a RDV visitor and you passed RDV=0 
         -1^message if problems or not a provider 
VARIABLES: XDUZ                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Default is current user DUZ. A single
 value of the DUZ to return values for.  
VARIABLES: RDV                          TYPE: Input
 VARIABLES DESCRIPTION:   Boolean flag to indicate whether or not to include
 remote data view visitors - default to 0 to not include.  
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional)  Default is zero (0). I $G(FUN) then
 extrinsic function, else RPC.  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 5/29/25 effective with APAR 1.5P6 patch to return
 information on New Person using component LIST.  
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5318                            IA #: 5318
  DATE CREATED: DEC 23, 2008
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICDDR0
  NAME: DSICDDR0                        ORIGINAL NUMBER: 5317
  ID: DSICDDR0
 GENERAL DESCRIPTION:   This ICR records APIs in the DSICDDR0 routine.  This
 routine is used by DSS applications for FILEMAN type file accesses.  The
 routine is a wrapper around Standard FILEMAN calls to derive results.  
  STATUS: Active
COMPONENT/ENTRY POINT: FIND
 COMPONENT DESCRIPTION:   This API will use the FILEMAN lookup to search for
 entries in a given file. This API is used by the RPC "DSIC DDR FINDER".  
VARIABLES: DSICP                        TYPE: Output
 VARIABLES DESCRIPTION:   A subscripted array with a value of 1 for success, or
 -1^Error Message to indicate errors occurred.  Error messages will be on
 subsequent levels of the array.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File number.  
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This is the standard FILEMAN DBS IENS;
 which is the record# to be updated.  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) "^" delimited (or ";" delimited) list of
 field numbers to retrieve.  
VARIABLES: NUMBER                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Defaults to "ALL". Number of entries to
 retrieve.  
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Value to Find.  
VARIABLES: INDEX                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Indeces to search on.  
VARIABLES: SCREEN                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) M Screening code.  
VARIABLES: FLAGS                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Defaults to "AM". FILEMAN flags.  
COMPONENT/ENTRY POINT: FILE
 COMPONENT DESCRIPTION:   This API will use the FILEMAN updater to file entries
 in VistA files. This API is used by the RPC "DSIC DDR FILER".  
VARIABLES: DSICP                        TYPE: Output
 VARIABLES DESCRIPTION:   A subscripted array with a value of 1 for success, or
 -1^Error Message to indicate errors occurred.  Error messages will be on
 subsequent levels of the array.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File number or sub-file number.  
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) this is the standard FILEMAN DBS IENS;
 which is the record# to be updated.  
VARIABLES: FLAGS                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) only acceptable value is: 
  
                           "T" - transaction processing, that is, all the 
                                 fields must be successfully updated or 
                                 none of them are.  
VARIABLES: INPUT                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) list where: 
                        LIST[#] = p1^p2^p3 where 
                                  p1 - required - field # 
                                  p2 - optional - default value I 
                                       if p2="" then field value in 
                                       internal format.  
                                            ="E" then field value in 
                                             external format.  
                                            ="I" then field value in 
                                             internal format.  
                                            ="W" then field is a word 
                                              processing field.  
  
                                               see notes below 
  
                                   p3 - value for field# if value is <null> 
                                        or "@", then that field will be 
                                        deleted.  
  
  
 NOTES on word processing fields 
 ===============================
 if LIST[#]=field#^W^@    - delete any existing text for that record if
 LIST[#]=field#^W^text - this will first remove any existing text 
                             for this field in this record and then add 
                             the new text if LIST[#]=field#^WA^text - this will
 append the new text to any 
                             existing text which may be there 
  
    You cannot mix W and WA for any one field.  p2 must be the same for all the
 LIST[#] elements.  
  
 Deletion of text, i.e. the "@" takes precedence over anything else.  
  
                                                           .
COMPONENT/ENTRY POINT: GET
 COMPONENT DESCRIPTION:   This API will allow retrieval of Field Input
 specifications. This API is used by the RPC "DSIC DDR GETS ENTRY DATA".  
  
 Restriction: At this point, this routine will NOT return multiple levels of a
 file simultaneously.  
VARIABLES: DSICP                        TYPE: Output
 VARIABLES DESCRIPTION:   Return: Array with the following format: 
                     @DSICP@(n) = FileNumber^IENS^FieldNumber^Data^I or E 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File number.  
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This is the standard FILEMAN DBS IENS;
 which is the record# to be updated.  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Field numbers, delimited by "^" or ";".  
VARIABLES: FLAGS                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Flags to control processing: 
                              [ E = External format - default 
                              [ I = Internal format 
                              [ N = Do NOT return null field values 
                              [ R = Resolves field numbers to field names.  
                                                
 If FLAGS="W" then expecting a single word-processing field.  
COMPONENT/ENTRY POINT: KILL
 COMPONENT DESCRIPTION:   This API can be used to delete an entire entry from a
 file. This API is used by the "DSIC DDR DELETE ENTRY" RPC.  
VARIABLES: DSICP                        TYPE: Output
 VARIABLES DESCRIPTION:   A subscripted array with a value of 1 or 0^Error
 message to indicate if delete succeeds.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File or sub-file number.  
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) IENS of file if subfile list is requested.
 where 
                                                         n = 0,1,2,3,4,...  
COMPONENT/ENTRY POINT: LIST
 COMPONENT DESCRIPTION:   This API will use the FILEMAN lookup to list entries
 for a given file. This API is used by the RPC "DSIC DDR LISTER".  
VARIABLES: DSICP                        TYPE: Output
 VARIABLES DESCRIPTION:   A subscripted array with a value of 1 for success, or
 -1^Error Message to indicate errors occurred.  Error messages will be on
 subsequent levels of the array.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File number.  
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) this is the standard FILEMAN DBS IENS;
 which is the record# to be updated.  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) ";" delimited list of field numbers to
 retrieve.  
VARIABLES: FLAGS                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) "B" for Traversing Backwards, or "I" for
 internal formats.  
VARIABLES: NUMBER                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Defaults to "ALL". Number of entries to
 retrieve.  
VARIABLES: FROM                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Entry to start listing from.  
VARIABLES: PARTIAL                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Partial entry to match.  
VARIABLES: INDEX                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Indeces to search on.  
VARIABLES: SCREEN                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) M Screening code.  
VARIABLES: IDENTIFY                     TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Identifiers.  
COMPONENT/ENTRY POINT: UPDATE
 COMPONENT DESCRIPTION:   This API can be used to update a VistA file entry
 using the standard FILEMAN database updater. This API is used by the "DSIC DDR
 UPDATE FILE" RPC.  
VARIABLES: DSICP                        TYPE: Output
 VARIABLES DESCRIPTION:   A subscripted array with a value of 1 or 0^Error
 message to indicate if delete succeeds.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File or sub-file number.  
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) DATA : Array of ("Field number")=Data.  
COMPONENT/ENTRY POINT: UPDATE1
 COMPONENT DESCRIPTION:   This API can be used to update a VistA subfile entry
 using the standard FILEMAN database updater. This API is used by the "DSIC DDR
 UPDATE SUBFILE" RPC.  
VARIABLES: DSICP                        TYPE: Output
 VARIABLES DESCRIPTION:   A subscripted array with a value of 1 or 0^Error
 message to indicate if delete succeeds.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File or sub-file number.  
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This is the standard FILEMAN DBS IENS;
 which is the record# to be updated.  
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) DATA : Array of ("Field number")=Data.  
COMPONENT/ENTRY POINT: WP
 COMPONENT DESCRIPTION:   This API can be used to update a VistA
 word-processing file or sub-file entry using the standard FILEMAN database
 updater. This API is used by the "DSIC DDR WP FILER" rpc.  
VARIABLES: DSICP                        TYPE: Output
 VARIABLES DESCRIPTION:   A subscripted array with a value of 1 or 0^Error
 message to indicate if delete succeeds.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File or sub-file number.  
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This is the standard FILEMAN DBS IENS;
 which is the record# to be updated.  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) ";" delimited list of field numbers to
 retrieve.  
VARIABLES: FLAGS                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) "A" to append new text to existing text in
 field.  
  
            "K" to Lock the entry or sub-entry before updating.  
VARIABLES: DSICD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Array of lines to store in field. If array
 contains "@", then delete the word-processing field.  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5319                            IA #: 5319
  DATE CREATED: DEC 23, 2008
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICFM05
  NAME: DSICFM05                        ORIGINAL NUMBER: 5317
  ID: DSICFM05
 GENERAL DESCRIPTION:   This ICR records API's in the DSICFM05 routine.  This
 routine is used by DSS applications for FILEMAN type file accesses using the
 LIST^DIC DBS call.  
  
    Associated RPCs:  DSIC FM FIND, DSIC FM LIST.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: FIND
 COMPONENT DESCRIPTION:   This API provides a wrapper around most of the
 functionality found in LIST^DIC.  This component is used for the "DSIC FM
 FIND" RPC.  
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   Return DSIC=$NA(^TMP("DSIC",$J,"DILIST")) 
                        ^TMP("DSIC",$J,"DILIST",n,0)=p1^p2^p3^...  
                                                     for n=1,2,3,...  
                             where p1 = record ien 
                                   p2 = .01 field internal value 
                                   p3 = value of field specified in 1st 
                                          ^-piece of FIELDS 
                                   p4 = value of field specified in 
                                        2nd ^-piece of FIELDS 
                                        etc. for p4,p5,p6,...  
  
                       If no matches found, @DSIC@(1,0) = -1^No matches 
                                                                   found 
                       If errors, one or more lines may be returned: 
                               @DSIC@(1,0) = -1^Problems encountered 
                               @DSIC@(n,0) = detailed text of problem, if 
                                             available 
                                      where n = 2,3,4,5,...  
VARIABLES: INPUT                        TYPE: Input
 VARIABLES DESCRIPTION:   
                            Description of the INPUT array 
                            ==============================
                 INPUT(sub) = variable name ^ value  where sub can be 
                              anything 
                              [Example: INPUT(1) = "FILE^200"] 
  
                          variable name   REQ   DEFAULT 
                          -------------   ---   -------
                          FILE            YES 
             This is the number of the file (or subfile) for which the 
             lookup is to be done.  
  
                          IENS            Y/N 
             This is the standard Fileman IENS for LIST^DIC. It is only 
             required when doing a lookup on a subfile.  
  
                          FIELDS          NO    .01 
               1. A string of fields (#s) to be returned 
               2. Field #s are separated by a ';' 
               3. For external values, use only the field # 
               4. For internal values, use the field # followed by 'I' 
               5. Example: .01;.09;.03i;.03 from PATIENT file.  
                  This will return 
                  dfn^patient name^SSN^DOB (FM format)^DOB external format 
  
                          FLAGS           NO    MP 
               1. A string of codes that affects how the lookup is done.  
               2. This RPC always packs output (P flag) 
               3. 'I' - internal values returned is obsolete but still 
                  honored.  
                  Use 'I' if you want all field values returned as 
                  internal values.  
  
                          NUMBER          NO    100 
               The maximum number of entries to be returned.  
  
                          INDEX           NO     "B" 
               The name of the index from which to build the list 
               Default value is 'B' index unless the K flag is passed 
               If INDEX="#" then loop through file by internal record 
               number.  
  
  
                          SCREEN          NO 
               The screen to apply to each potential entry in the returned 
               list to decide whether or not to include it. This may be set 
               to any valid M code that sets $TEST to 1 if the entry should 
               be included, to 0 if not. This is exactly equivalent to the 
               DIC("S") input variable to Classic FileMan lookup ^DIC. The 
               Lister will execute this screen in addition to any SCR node 
               (whole-file screen) defined for the file.  
  
               Optionally, the screen can be defined in an array entry 
               subscripted by "S" (for example, SCR("S")), allowing 
               additional screen entries to be defined for variable pointer 
               fields as described below.  
  
                           VAL            YES     
               The lookup value for FIND.  It can be an array.  
COMPONENT/ENTRY POINT: LIST
 COMPONENT DESCRIPTION:   This API provides a wrapper around most of the
 functionality found in LIST^DIC.  This component is used for the "DSIC FM
 LIST" RPC.  
VARIABLES: DSIC                         TYPE: Input
 VARIABLES DESCRIPTION:   Return DSIC=$NA(^TMP("DSIC",$J,"DILIST")) 
        ^TMP("DSIC",$J,"DILIST",n,0)=p1^p2^p3^... for n=1,2,3,...  
                             where p1 = record ien 
                                   p2 = .01 field internal value 
                                   p3 = value of field specified in 1st 
                                          ^-piece of FIELDS 
                                   p4 = value of field specified in 
                                        2nd ^-piece of FIELDS 
                                        etc. for p4,p5,p6,...  
  
                  If no matches found, @DSIC@(1,0) = -1^No matches found 
                  If errors, one or more lines may be returned: 
                          @DSIC@(1,0) = -1^Problems encountered 
                          @DSIC@(n,0) = detailed text of problem if 
                                        available where n = 
                                        2,3,4,5,...  
VARIABLES: INPUT                        TYPE: Input
 VARIABLES DESCRIPTION:   INPUT(sub) = variable name ^ value 
              where sub can be anything 
              [Example: INPUT(1) = "FILE^200"] 
  
                            Description of the INPUT array 
                            ==============================
                 INPUT(sub) = variable name ^ value  where sub can be 
                              anything [Example: INPUT(1) = "FILE^200"] 
  
                          variable name   REQ   DEFAULT 
                          -------------   ---   -------
                          FILE            YES 
               This is the number of the file (or subfile) for which the 
               lookup is to be done.  
  
                          IENS            Y/N 
               this is the standard Fileman IENS for LIST^DIC. It is only 
               required when doing a lookup on a subfile.  
  
                          FIELDS          NO    .01 
               1. A string of fields (#s) to be returned 
               2. Field #s are separated by a ';' 
               3. For external values, use only the field # 
               4. For internal values, use the field # followed by 'I' 
               5. Example: .01;.09;.03i;.03 from PATIENT file.  This will 
                  return dfn^patient name^SSN^DOB (FM format)^DOB external 
                       format.  
  
                          FLAGS           NO    MP 
               1. a string of codes that affects how the lookup is done.  
               2. This RPC always packs output (P flag) 
               3. 'I' - internal values returned is obsolete but still 
                  honored.  Use 'I' if you want all field values returned 
                  as internal values.  
  
                          NUMBER          NO    100 
               the maximum number of entries to be returned.  
  
                          INDEX           NO     "B" 
               The name of the index from which to build the list 
               Default value is 'B' index unless the K flag is passed 
               If INDEX="#" then loop through file by internal record 
               number.  
  
  
                          SCREEN          NO 
               The screen to apply to each potential entry in the returned 
               list to decide whether or not to include it. This may be set 
               to any valid M code that sets $TEST to 1 if the entry should 
               be included, to 0 if not. This is exactly equivalent to the 
               DIC("S") input variable to Classic FileMan lookup ^DIC. The 
               Lister will execute this screen in addition to any SCR node 
               (whole-file screen) defined for the file.  
               Optionally, the screen can be defined in an array entry 
               subscripted by "S" (for example, SCR("S")), allowing 
               additional screen entries to be defined for variable pointer 
               fields as described below.  
  
  
                         FROM            NO 
               1. The index entry from which to begin the list (e.g., a 
                  FROM value of "XQ" would list entries following XQ).  
               2. The FROM values must be passed as they appear in the 
                  index, not in external value.  
               3. The index entry for the FROM value itself is not 
                  included in the returned list.  
               4. If the INDEX parameter specifies a compound index (i.e., 
                  one with more than one data-valued subscript), then the 
                  FROM parameter should be passed by reference as an array 
                  where 
               FROM(n) represents the "nth" subscript on the compound 
               index.  
  
  
                         PART            NO 
               The partial match restriction. For example, a PART value of 
               "DI" would restrict the list to those entries starting with 
               the letters "DI".  Again, this value must be a partial match 
               to an index value, not the external value of a field.  This 
               can be passed by reference.  
  
               PART(n) and subscripted the same as the FROM parameter so 
               that PART values can be specified for any subscript in a 
               compound index.  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5320                            IA #: 5320
  DATE CREATED: DEC 23, 2008
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICXQA
  NAME: DSICXQA                         ORIGINAL NUMBER: 5317
  ID: DSICXQA
 GENERAL DESCRIPTION:   This ICR records API's in the DSICXQA routine.  This
 routine is used by DSS applications for NEW PERSON (#200) file accesses.  The
 routine is a wrapper around Standard FILEMAN calls to Send Alerts to VistA
 packages.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SEND
 COMPONENT DESCRIPTION:   This API will send an alert using Supported KERNEL
 calls. This API is used by the "DSIC SEND ALERT" RPC.  
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   Return 1 if alert successfully sent, else return
 -1^msg.  
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) DATA is a list which is expecting data in
 the following format: 
   
                        DATA(sub) = value 
                  subscript  required  value 
                  ---------  --------  ------------------------------
                  XQAMSG        Y      message displayed to the user 
                                                 (80 char) 
  
                  XQAROU        N      tag^routine to be invoked 
                                       if from RPC this must be silent 
  
                  XQAID         N      package identifier for alert 
  
                  XQADATA       N      an application specific data string 
                                       [the alert processor will set 
                                        XQADATA equal to this and will 
                                        be available to M routine specified 
                                        in XQAROU] 
  
                  XQAARCH       N      # days to keep in alert tracking 
                                       file.  
  
                  XQASURO       N      # days to wait before forwarding 
                                       alert.  
                                      [forwarded to recipient's MAILMAN's 
                                       surrogates if unprocessed 
                                       by recipient] 
  
                  XQASUPV       N      Supervisor forwarding 
                                       [# days to wait before forwarding 
                                       to recipient's supervisor if 
                                       unprocessed by recipient.  
                                       SUPERVIOR = CHIEF field from file 
                                       #49 corresponding to recipient's 
                                       SERVICE/SECTION] 
  
                  DFN           N      pointer to PATIENT file 
                                       [used to construct XQAID so that it 
                                        works properly in CPRS] 
  
                  PKG           N      namespace of calling app - 
                                       default=VEJD 
  
                  Rn            Y      at least one must be defined - 
                                       recipients of R1,R2,R3,...         
                                       alert - can be pointer to NEW PERSON 
                                       file or G.<name of mail group> 
  
      Example of setup in the GUI: 
        Param.List['"XQAMSG"'] := text 
        Param.list['"R1"']     := duz of recipient 
        Param.List['"DFN"']    := pointer to PATIENT file 
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5321                            IA #: 5321
  DATE CREATED: DEC 23, 2008
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICXM
  NAME: DSICXM                          ORIGINAL NUMBER: 5317
  ID: DSICXM
 GENERAL DESCRIPTION:   This ICR records API's in the DSICXM routine.  This
 routine is used by DSS applications for SENDING MAILMAN mail messages.  The
 routine is a wrapper around Standard kernel calls to send messages to VistA
 packages.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SEND
 COMPONENT DESCRIPTION:   This API will send a MAILMAN mail message to VistA
 recipients. This API is associated with the "DSIC SEND MAIL MSG" RPC.  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   Returns MAILMAN message number on success, else
 return -1^Error message.  
VARIABLES: ARR                          TYPE: Input
 VARIABLES DESCRIPTION:   ARR(sub) - required input array where 'sub' can be
 any value 
                     Format: ARR(sub) - parameter name ^ value 
                         Acceptable parameters: 
  
                     FLAGS - optional - string of uppercase characters 
                                        representing special instructions 
                                        [.XMINSTR] 
                              P = priority 
                              I = info only 
                              X = closed 
                              C = confidential 
                              R = confirm receipt 
                     FROM - optional - default to user DUZ 
                     SELF BSKT - optional - if FROM=user DUZ then name 
                                                    of user's basket to 
                                                    deliver message.  
                     VAPOR - optional - Fileman date.time for which this 
                                        message should be deleted from 
                                        recipient's baskets.  
                     SUBJ - required  - subject of mail message 3-65 
                                        characters 
                     NOTME - optional - if ARR(sub) = "NOTME^1" then 
                                        DO NOT include user DUZ as a 
                                        recipient.  Otherwise user DUZ 
                                        will always be a recipient, even 
                                        if they are not included in the 
                                        recipient list.  
                     REC - optional   - recipient to receive mail message 
                                        each recipient will be a separate 
                                        ARR(sub) entry acceptable formats 
                                        for recipient values: 
                                             DUZ number 
                                             G.mail group name 
                                             D.device name 
                                             S.server name 
                                            For DUZ and mail groups 
                                            there are additional params: 
                                               I: to indicate this one for 
                                                  INFO only 
                                               C: to indicate this one for 
                                                  cc (copy) only 
                                               L@fileman_datetime: 
                                                  deliver to this user at 
                                                  the later specified 
                                                  date/time.  
                                                  Example: I:1301 for user 
                                                           1301 
                                              CL@3021224.23:G.IRM STAFF 
                      TEXT - required - text of mail message - each line 
                                        of text in the message will be a 
                                        separate ARR(sub) entry.  No line 
                                        should exceed 80 characters.  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5322                            IA #: 5322
  DATE CREATED: DEC 23, 2008
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICXPR
  NAME: DSICXPR                         ORIGINAL NUMBER: 5317
  ID: DSICXPR
 GENERAL DESCRIPTION:   This ICR records API's in the DSICXPR routine.  This
 routine is used by DSS applications for modifications to KERNEL System
 Parameters. The routine uses standard FILEMAN and KERNEL calls to derive
 results. KERNEL XPAR APIs (Supported ICR #2263) are wrapped by this routine.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ADD
 COMPONENT DESCRIPTION:   This API is used by the "DSIC XPAR ADD" rpc. This API
 can be used to add a new instance of a parameter.  For this API, the instance
 value (p3) is NOT optional.  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   A subscripted array with a value of 1 or 0 to
 indicate success (1 = Success). Some return values will indicate -1^Error
 Message.  
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   Required - p1~p2~p3~p4~p5~p6 
                                  p1 - opt     - Entity 
                                  p2 - req     - Parameter 
                                  p3 - opt/req - Instance 
                                  p4 - opt/req - Value 
                                    1. required for most calls 
                                    2. optional for get type calls 
                                    3. not used in delete call 
                                  p5 - opt/req - New Instance Value - 
                                  p6 - opt     - GET1 format 
                                    1. Only used in GET1 call 
                                    2. Default to Q 
                                    3. For GET and GETALL - ignore, 
                                       always default to B 
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional)  Default is zero (0). I $G(FUN) then
 extrinsic function, else RPC.  
COMPONENT/ENTRY POINT: ADDWP
 COMPONENT DESCRIPTION:   This API will allow the addition of a new instance of
 a word- processing parameter.  It used by the "DSIC XPAR ADD WP" RPC.  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   if successful, return 1 if unsuccessful return
 -1^error message Some XPAR calls return 0 if the there were no problems but
 the lookup failed.  
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) 
                            DATA - required - p1~p2~p3~p4~p5~p6 
                                  p1 - opt     - Entity 
                                  p2 - req     - Parameter 
                                  p3 - opt/req - Instance 
                                       Optional for all single value 
                                       parameters - default to 1 
                                  p4 - req - Value 
VARIABLES: DSICLT                       TYPE: Input
 VARIABLES DESCRIPTION:   An array of text lines to be added to the
 word-processing field.  Array is in format: 
  
                  ARRAY(1)=line text 1 
                  ARRAY(2)=line text 2 
                  ARRAY(n)=line text n 
COMPONENT/ENTRY POINT: CHG
 COMPONENT DESCRIPTION:   This API will allow the modification of a new
 instance of a word-processing parameter.  It used by the "DSIC XPAR EDIT" RPC. 
 
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   If successful, return 1 if unsuccessful return
 -1^error message Some XPAR calls return 0 if there were no problems but the
 lookup failed.  
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   required - p1~p2~p3~p4~p5~p6 
                                  p1 - opt     - Entity 
                                  p2 - req     - Parameter 
                                  p3 - opt/req - Instance 
                                       Optional for all single value 
                                       parameters - default to 1 
                                  p4 - req - Value 
                                  p5 - req - New Instance Value - 
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional)  Default is zero (0). I $G(FUN) then
 extrinsic function, else RPC.  
COMPONENT/ENTRY POINT: DEL
 COMPONENT DESCRIPTION:   This API will allow the deletion of an instance of a
 system parameter.  It used by the "DSIC XPAR DEL" RPC.  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   if successful,  return 1 if unsuccessful return
 -1^error message 
  
 Some XPAR calls return 0 if the there were no problems, but the lookup failed. 
 
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Required - p1~p2~p3~p4 
                       p1 - opt     - Entity 
                       p2 - req     - Parameter 
                       p3 - req - Instance 
                       p4 - opt/req - Value 
                       Optional, but if passed, 
                       it must be equal to "@".  
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional)  Default is zero (0). I $G(FUN) then
 extrinsic function, else RPC.  
COMPONENT/ENTRY POINT: GET
 COMPONENT DESCRIPTION:   This API will return all instances of an
 entity/parameter.  
VARIABLES: ARR(1-6)                     TYPE: Input
 VARIABLES DESCRIPTION:   
  
   ARR(1) - ENTITY 
   ARR(2) - PARAM NAME 
   ARR(3) - INSTANCE 
   ARR(4) - VALUE 
   ARR(5) - NEW INSTANCE VALUE 
   ARR(6) - FORMAT <NOT REQUIRED> 
VARIABLES: ARR(6)                       TYPE: Output
 VARIABLES DESCRIPTION:   
               ARR(6) = Q - return list(#)=iI^iV 
                        E - return list(#)=eI^eV 
                        B - return list(#,"N")=iI^eI 
                                   list(#,"V")=iV^eV 
                        N - return list(#,"N")=iV^eI 
        Return RET(#) = iI^eI^iV^eV 
                        some of those pieces may be <null> depends upon ARR(6) 
          On error, return RET(1)=-1^error message 
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 10/3/24 effective with patch DSIY*1.5*6 to
 support finding all instances of a specified entity/parameter.  
  
 Added GET module on 5/6/25 effective with patch DSIY*1.5*6 to return all 
 instances of an entity/parameter.  
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/3/24 effective with patch DSSO*2.0*8 to
 support finding all instances of a specified entity/parameter.  
  DATE ACTIVATED: MAY 13, 2025

NUMBER: 5323                            IA #: 5323
  DATE CREATED: DEC 23, 2008
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICXPDU
  NAME: DSICXPDU                        ORIGINAL NUMBER: 5317
  ID: DSICXPDU
 GENERAL DESCRIPTION:   This ICR records API's in the DSICXPDU routine.  This
 routine is used by DSS applications for retrieving data from the INSTALL
 (#9.7) file. The routine is a wrapper around Standard FILEMAN and KERNEL calls
 to get dates and other information concerning KIDS installs.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: INSLIST
 COMPONENT DESCRIPTION:   This API will return a list of INSTALL (#9.70 file
 entries sorted by BUILD Package name (#1) and Installed Completed Date #17) in
 reverse chronological order.  
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   DSIC(n)=<INSTALL file ifn>^<Build name>^ <date
 installed completed> 
         for n=1,2,3,4,...  
         Note: date installed completed should only have a value for those 
 entries whose status is 3 [Install Completed].  
  
 If no matches found, or problems, return -1^message.  
VARIABLES: DSIKID                       TYPE: Input
 VARIABLES DESCRIPTION:   
  (Required) Lookup will be done on the name portion of the Build name.  For
 new version Build names, always use name portion only.  
  
 For patch Build names, use the entire Build name with "*" unless DSIALL=1, 
 then only use the first "*"-piece of the Build name.  
VARIABLES: DSIALL                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Boolean flag - default=0, see DSIKID.  
VARIABLES: DSISTAT                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Numbers indicating which statuses to
 return: 
        Defaults to '23'. 
        0:loaded  1:Queued  2:Started  3:Completed 4:De-installed 
COMPONENT/ENTRY POINT: LAST
 COMPONENT DESCRIPTION:   This API will return the latest installed version of
 a DSS package.  Since there is no PACKAGE file entry, this API gets
 information from the INSTALL file.  
VARIABLES: DSIKID                       TYPE: Both
 VARIABLES DESCRIPTION:   (Required) 
              INPUT:  Name of kids package to get last install.  
  
              OUTPUT: 
  
              On error, return -1^error message.  
  
              If successful, return version ^ date.time installed.  
              where version is taken from .01 field value of INSTALL 
              (#9.7) file entry of the most recent INSTALL DATE.TIME 
              (field 17).  
  
              If no matches found to DSIKID, return 0^message.  
COMPONENT/ENTRY POINT: MES
 COMPONENT DESCRIPTION:   API to send message to KIDS install to display.  This
 one call combines both MES^XPDUTL and BMES^XPDUTL.  
VARIABLES: XMES                         TYPE: Input
 VARIABLES DESCRIPTION:   required - string (or array) to pass to KIDS.  
            XMES array must be in form XMES(#)=text 
            and # = 1,2,3,4,....  
VARIABLES: BLANK                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Boolean (0/1) to indicate if text is to be
 preceeded by a blank line.  
COMPONENT/ENTRY POINT: PATCH
 COMPONENT DESCRIPTION:   This calls the KIDS API which will check the patch
 application history multiple in the version multiple in the Package (#9.4)
 file.  
  
 This API is used by the "DSIC XPD PATCH" RPC.  
VARIABLES: XRET                         TYPE: Output
 VARIABLES DESCRIPTION:   (Required) 1 if patch installed, otherwise 0.  
VARIABLES: PKG                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Patch designation to check (e.g.,
 LR*5.2*200).  
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) I FUN>0 then extrinsic API, else RPC.  
COMPONENT/ENTRY POINT: PKG
 COMPONENT DESCRIPTION:   This API will return the pointer to the PACKAGE
 (#9.4) file.  
VARIABLES: X                            TYPE: Both
 VARIABLES DESCRIPTION:   (Required) INPUT:  Name of kids package to get last
 install.  
  
            OUTPUT: 
  
                    On error, return -1^error message 
  
                    If successful, return version ^ date.time installed.  
                    where version is taken from .01 field value of INSTALL 
                    (#9.7) file entry of the most recent INSTALL DATE.TIME 
                    (field 17).  
COMPONENT/ENTRY POINT: RLAST
 COMPONENT DESCRIPTION:   API to return the latest installed version of a DSS
 package.  Since there is no PACKAGE file entry, get from INSTALL file.  
VARIABLES: PKG                          TYPE: Both
 VARIABLES DESCRIPTION:   (Required)  INPUT:  Name of kids package to get last
 install.  
  
             OUTPUT: 
  
             On error, return -1^error message 
  
             If successful, return version ^ date.time installed.  
             where version is taken from .01 field value of INSTALL 
             (#9.7) file entry of the most recent INSTALL DATE.TIME 
             (field 17).  
  
             If no matches found to DSIKID, return 0^message 
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) I FUN>0 then extrinsic API, else RPC.  
COMPONENT/ENTRY POINT: UPDSTAT
 COMPONENT DESCRIPTION:   This API is used to update the percentages on the
 KIDS installation status bar.  
VARIABLES: TOT                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Total number of items.  
VARIABLES: NUM                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Current item number.  
VARIABLES: INIT                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) if INIT=1 then initialize status bar.  
  
 OT,NUM not needed to initialize.  
COMPONENT/ENTRY POINT: VERSION
 COMPONENT DESCRIPTION:   This API is used to get the current version number of
 package. This API is used by the "DSIC XPD VERSION" RPC.  
VARIABLES: XRET                         TYPE: Output
 VARIABLES DESCRIPTION:   (Required) Package version number or -1 if not found. 
 
VARIABLES: PKG                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Namespace or full package name.  
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) I FUN>0 then extrinsic API, else RPC.  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5324                            IA #: 5324
  DATE CREATED: DEC 24, 2008
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICFM04
  NAME: DSICFM04                        ID: DSICFM04
 GENERAL DESCRIPTION:   This ICR records API's in the DSICFM04 routine.  This
 invokes the Fileman filer to update fields for an existing entry.  This will
 allow you to update any field at the level of the FILE including word
 processing fields.  It does not allow for updating different levels of the
 file.  If you wish to update a subfile, then you will have to make multiple
 calls to this RPC for each file or subfile.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: FILE
 COMPONENT DESCRIPTION:   This will allow you to update any field at the level
 of the FILE including word processing fields.  It does not allow for updating
 different levels of the file.  If you wish to update a subfile, then you will
 have to make multiple calls to this API for each file or subfile.  
  
 This API is used by the "DSIC FM FILER" RPC.  
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   (Required) Return array where 
         DSIC(1) = 1^  if everything was successfully filed 
                 = -1^error message if any problems encountered 
         DSIC(2...n) = additional error messages 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This is the file (or subfile#) which is to
 be updated.  
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This is the standard Fileman DBS IENS
 which is the record# to be updated: 
                    IENS="27," - update record# 27 in the file 
                    IENS="3,27," - update the 3rd record in the 
                         multiple indicated by the subfile# for the 
                         27th record in the file 
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Only acceptable value is "T" - transaction
 processing, that is, all the fields must be successfully updated or none of
 them are.  
VARIABLES: INPUT                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) List where: 
         LIST[#] = p1^p2^p3 where 
                   p1 - required - field # 
                   p2 - optional - default value I 
                        if p2="" then field value in internal format 
                             ="E" then field value in external format 
                             ="I" then field value in internal format 
                             ="W" then field is a word processing 
                                  see notes below 
                   p3 - value for field# - if value is <null> or "@" 
                        then that field will be deleted 
  
  NOTES on word processing fields 
  ===============================
  if LIST[#]=field#^W^@ - delete any existing text for that record 
  if LIST[#]=field#^W^text - this will first remove any existing text 
                             for this field in this record and then add 
                             the new text.  
  if LIST[#]=field#^WA^text - this will append the new text to any 
                              existing text which may be there.  
  
 You cannot mix W and WA for any one field.  p2 must be the same for all the
 LIST[#] elements. Deletion of text, i.e. the "@" takes precedence over 
 anything else.  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 3/11/20 for access to DSICFM04 to update fields
 using DSS core component DSIC FM FILER.  
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5325                            IA #: 5325
  DATE CREATED: DEC 24, 2008
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICFM01
  NAME: DSICFM01                        ID: DSICFM01
 GENERAL DESCRIPTION:   This contains common Fileman utilities.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MSG
 COMPONENT DESCRIPTION:   This api will format text using the MSG^DIALOG api.  
VARIABLES: FLGS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) default = "AE" 
      FLGS [ A - return results in OUT - passed by ref 
             W - write to current device 
             S - save ^TMP or INPUT (don't kill) 
             E - process error array 
             H - process help array 
             M - process message array 
             B - blank lines suppressed between error msgs 
             T - Return Total number of lines in the top level of OUT 
             V - don't return OUT, return extrinsic function value 
VARIABLES: OUT                          TYPE: Both
 VARIABLES DESCRIPTION:   (Optional/Required) local array passed by reference
 to return messages.  See FLGS parameter.  
VARIABLES: WIDTH                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) default= 72  max length of each line to
 return.  
VARIABLES: LEFT                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Default=0   pad LEFT spaces to return
 array.  
VARIABLES: INPUT                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Default assumes ^TMP("DIxxx",$J) Closed
 root name of local input array where text resides.  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5326                            IA #: 5326
  DATE CREATED: DEC 24, 2008
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICHFS
  NAME: DSICHFS                         ID: DSICHFS
 GENERAL DESCRIPTION:   This routine contains various entry points for handling
 HFS files. It can accomodate calling a VistA option that expects to write to a
 printer or device.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ASKFILE
 COMPONENT DESCRIPTION:   Interactive entry to prompt for file name file not
 verified as to whether it exists or not.  
  
 Return user input or <null> 
COMPONENT/ENTRY POINT: ASKPATH
 COMPONENT DESCRIPTION:   Interactive entry to prompt for path name syntax of
 path is not verified return user input or <null>.  
COMPONENT/ENTRY POINT: CLOSE
 COMPONENT DESCRIPTION:   Assumes you opened a HFS file using OPEN subroutine
 for backward compatibility, the variable HANDLE can be set prior to calling
 this line tag CLOSE.  
COMPONENT/ENTRY POINT: DEL
 COMPONENT DESCRIPTION:   Delete file(s).  
VARIABLES: PATH                         TYPE: Input
 VARIABLES DESCRIPTION:   Directory where file resides or is to be placed
 default to $$PWD^%ZISH.  
VARIABLES: DSIDEL                       TYPE: Input
 VARIABLES DESCRIPTION:   
  [.]DSIDEL - file or list of files to be deleted 
  DSIDEL=file_name or DSIDEL(file_name)="" or 
       DSIDEL(file_name_stub_"*")="" 
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   Boolean - if allowed & equal to 1 then TAG was called
 as an extrinsic function, else it was called a DO (w/params).  
COMPONENT/ENTRY POINT: DELALL
 COMPONENT DESCRIPTION:   Delete all files starting with DSIC.  
VARIABLES: PATH                         TYPE: Input
 VARIABLES DESCRIPTION:   Directory where file resides or is to be placed
 default to $$PWD^%ZISH.  
COMPONENT/ENTRY POINT: FTG
 COMPONENT DESCRIPTION:   Get HFS file.  
VARIABLES: DSICHFS                      TYPE: Output
 VARIABLES DESCRIPTION:   Return variable for global or array.  
   DSICHFS(1)=Data Line #1 
   DSICHFS(2)=Data Line #2 
   DSICHFS(n)=Data Line #n 
VARIABLES: INPUT                        TYPE: Input
 VARIABLES DESCRIPTION:   Expects ARR(varname)=value or ARR=var1^var2^var3,
 where varname defined as follows: 
  
     CTRL - Boolean, if 1 strip ctrl chars from data, default=0 
      DEL - Default to 2 
             0: do not delete file created 
              1: delete file if transferred to global 
              2: delete file always 
     FILE - name of file to open or create.  If temp file is required 
            and FILE not passed then FILE will be generated 
      FUN - Boolean - if allowed & equal to 1 then TAG was called as 
            an extrinsic function, else it was called a DO (w/params) 
   HANDLE - string to be used when opening and closing files if the 
            %ZISUTL utility is called 
     MODE - default value is W [W:write  R:read  A:append] 
     PATH - directory where file resides or is to be placed 
            default to $$PWD^%ZISH 
      RTN - required only for GET call.  Indirect argument of DO 
            command.  Entry invoked must have no user interactions 
      VPG - page length, default to 66 
      VRM - right margin, default to 80 
COMPONENT/ENTRY POINT: GET
 COMPONENT DESCRIPTION:   multifunction API: 
  
   OPEN file, run a M routine, CLOSE file, MOVE file to @DSICHFS 
   Return file_name if process successful, else return -1^msg 
   Note: if RTN="EN1^DIP" then ^DIP will do its own OPEN command.  So 
     set up %ZIS(),IOP.  It is the calling program's responsibility 
     to set up all the Fileman input local variables except for IOP 
VARIABLES: DSICHFS                      TYPE: Output
 VARIABLES DESCRIPTION:   Return variable for global or array.  
   DSICHFS(1)=Data Line #1 
   DSICHFS(2)=Data Line #2 
   DSICHFS(n)=Data Line #n 
VARIABLES: INPUT                        TYPE: Input
 VARIABLES DESCRIPTION:   Expects ARR(varname)=value or ARR=var1^var2^var3,
 where varname defined as follows: 
  
     CTRL - Boolean, if 1 strip ctrl chars from data, default=0 
      DEL - Default to 2 
             0: do not delete file created 
              1: delete file if transferred to global 
              2: delete file always 
     FILE - name of file to open or create.  If temp file is required 
            and FILE not passed then FILE will be generated 
      FUN - Boolean - if allowed & equal to 1 then TAG was called as 
            an extrinsic function, else it was called a DO (w/params) 
   HANDLE - string to be used when opening and closing files if the 
            %ZISUTL utility is called 
     MODE - default value is W [W:write  R:read  A:append] 
     PATH - directory where file resides or is to be placed 
            default to $$PWD^%ZISH 
      RTN - required only for GET call.  Indirect argument of DO 
            command.  Entry invoked must have no user interactions 
      VPG - page length, default to 66 
      VRM - right margin, default to 80 
COMPONENT/ENTRY POINT: LIST
 COMPONENT DESCRIPTION:   Return file names or verify file exists.  
VARIABLES: PATH                         TYPE: Input
 VARIABLES DESCRIPTION:   Directory where file resides or is to be placed
 default to $$PWD^%ZISH.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   Name of file to open or create.  If temp file is
 required and FILE not passed then FILE will be generated.  
VARIABLES: DSICIN                       TYPE: Input
 VARIABLES DESCRIPTION:   If FILE is <null> then DSICIN or .DSICIN() must be
 passed If $D(DSICIN)=0 then FILE must be defined FILE or DSICIN or subscripts
 of DSICIN() must be full file names or file_name_stub_"*".  
VARIABLES: DSICOUT                      TYPE: Output
 VARIABLES DESCRIPTION:   .DSICOUT() (Optional) passed by reference: 
                       Return array of file names found in directory 
                       defined in PATH.  
COMPONENT/ENTRY POINT: OPEN
 COMPONENT DESCRIPTION:   Open a HFS file and USE it.  
VARIABLES: PATH                         TYPE: Input
 VARIABLES DESCRIPTION:   Directory where file resides or is to be placed
 default to $$PWD^%ZISH.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   Name of file to open or create.  If temp file is
 required and FILE not passed then FILE will be generated.  
VARIABLES: MODE                         TYPE: Input
 VARIABLES DESCRIPTION:   default value is W [W:write  R:read  A:append].  
VARIABLES: VRM                          TYPE: Input
 VARIABLES DESCRIPTION:   Right margin, default to 80.  
VARIABLES: VPG                          TYPE: Input
 VARIABLES DESCRIPTION:   Page length, default to 66.  
COMPONENT/ENTRY POINT: STRIP
 COMPONENT DESCRIPTION:   Strip control characters from data in ROOT.  
VARIABLES: ROOT                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) $NAME of array where data is stored If
 data contains <TAB>, replace with 1-8 spaces.  
  
 Not an extrinsic function call.  
COMPONENT/ENTRY POINT: VER
 COMPONENT DESCRIPTION:   Verify that file exists in path.  
VARIABLES: PATH                         TYPE: Input
 VARIABLES DESCRIPTION:   Directory where file resides or is to be placed;
 default to $$PWD^%ZISH.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   Name of file to open or create.  If temp file is
 required and FILE not passed then FILE will be generated.  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5327                            IA #: 5327
  DATE CREATED: DEC 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  ROUTINE: FBAAUTL1                     NAME: FBCS call to FBAAUTL1
  ID: FBAAUTL1                          STATUS: Retired
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: 2
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   Authorization IEN (file 161) 
VARIABLES: FBASSOC                      TYPE: Output
 VARIABLES DESCRIPTION:   Authorization IEN 
VARIABLES: FB7078                       TYPE: Output
 VARIABLES DESCRIPTION:   IEN of the 7078 (file #162.4) if field #.055 of file
 161.01 contains FB7078.  Output= IEN_";FB7078" 
VARIABLES: FB583                        TYPE: Output
 VARIABLES DESCRIPTION:   IEN of the FB583 (file #162.4) if field #.055 of file
 161.01 contains FB583.  Output= IEN_";FB583" 
VARIABLES: FBVEN                        TYPE: Output
 VARIABLES DESCRIPTION:   Vendor IEN (file 161.2) from file 161.01, unless it
 is a FB7078, then the vendor IEN is from file 162.4.  
VARIABLES: FBAABDT                      TYPE: Output
 VARIABLES DESCRIPTION:   Beginning date (FM) of the Authorization (161.01).  
VARIABLES: FBAAEDT                      TYPE: Output
 VARIABLES DESCRIPTION:   Ending date (FM) from the authorization (161.01,
 field .02) 
VARIABLES: FBTYPE                       TYPE: Output
 VARIABLES DESCRIPTION:   Fee program of Authorization from file 161.01, field
 .03 
VARIABLES: FB                           TYPE: Output
 VARIABLES DESCRIPTION:   Global node ^FBAAA(DFN,1,X,0) (Authorization data,
 file 161.01) 
VARIABLES: FBTT                         TYPE: Output
 VARIABLES DESCRIPTION:   Treatment type from file 161.01, field .095 
VARIABLES: FBPOV                        TYPE: Output
 VARIABLES DESCRIPTION:   Purpose of Visit IEN from file 161.01, field .07 
VARIABLES: FBPSA                        TYPE: Output
 VARIABLES DESCRIPTION:   Primary Service Area from file 161.01, field 101 
VARIABLES: FBDMRA                       TYPE: Output
 VARIABLES DESCRIPTION:   Austin deletion flag, if one exists, from
 ^FBAAA(DFN,1,X,"ADEL"), the austin deletion cross reference in file 161.01,
 field 102 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5328                            IA #: 5328
  DATE CREATED: DEC 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBCH78                       NAME: FBCS Access to FBCH78
  ID: FBCH78                            STATUS: Retired
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: REFNPI
 COMPONENT DESCRIPTION:   a new function that returns the REFERRING PROVIDER
 NPI if it is Active and the provider has authorized use of the NPI 
VARIABLES: IEN200                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN OF FILE 200 IF KNOWN 
VARIABLES: IEN162P4                     TYPE: Input
 VARIABLES DESCRIPTION:   (optional) - IEN to File 162.4 (if ref prov is not
 known) 
VARIABLES: CHKAUTH                      TYPE: Input
 VARIABLES DESCRIPTION:   (optional) - Flag on whether to Check Authorization
 in file 200 
VARIABLES: NPI                          TYPE: Output
 VARIABLES DESCRIPTION:   A valid/active NPI if one can be determined. 
 Otherwise, NULL 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5329                            IA #: 5329
  DATE CREATED: DEC 31, 2008            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBCHACT0                     NAME: FBCS Access to FBCHACT0
  ID: FBCHACT0                          STATUS: Retired
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DAYS
VARIABLES: FBDAYS                       TYPE: Output
 VARIABLES DESCRIPTION:   Number of days between dates, if less than 1 pass
 back 1, other wise number of days 
VARIABLES: FBTODT                       TYPE: Both
 VARIABLES DESCRIPTION:   To date of authorization passed in 
VARIABLES: FBFRDT                       TYPE: Both
 VARIABLES DESCRIPTION:   From date of Authorization 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5330                            IA #: 5330
  DATE CREATED: DEC 31, 2008            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PRCSUT                       NAME: FBCS ACCESS TO PRCSUT
  ID: PRCSUT                            STATUS: Retired
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: STA
VARIABLES: PRCSK                        TYPE: Input
 VARIABLES DESCRIPTION:   Always passed as NULL, don't ask for user input 
VARIABLES: PRC(SITE)                    TYPE: Output
 VARIABLES DESCRIPTION:   Station number of user 
VARIABLES: PRC(SST)                     TYPE: Output
 VARIABLES DESCRIPTION:   Substation if one exists 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5331                            IA #: 5331
  DATE CREATED: DEC 31, 2008
  CUSTODIAL PACKAGE: ENROLLMENT APPLICATION SYSTEM
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: EASECU                       NAME: FBCS ACCESS TO EASECU
  ID: EASECU
 GENERAL DESCRIPTION:   We will need to clone this code into FBCS routine
 DSIFNOT5 to send output to an array instead of a screen display.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: DIS
 COMPONENT DESCRIPTION:   Display patient's current LTC Copay Test status and
 test date 
  
 We have cloned this code into DSIFNOT5, this ICR is for reference only! 
VARIABLES: DFN                          TYPE: Both
 VARIABLES DESCRIPTION:   IEN of Patient file 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5332                            IA #: 5332
  FILE NUMBER: 100.05                   GLOBAL ROOT: ORD(100.05,
  DATE CREATED: JAN 07, 2009
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ORDER CHECK INSTANCES FILE - PHARMACY FIELDS
  ID: ORD(100.05,
GLOBAL REFERENCE: ORD(100.05,D0
FIELD NUMBER: 13                        FIELD NAME: PHARMACIST OVERRIDE COMMENTS
  LOCATION: 11;1                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field represents the reason that the pharmacist is
 overriding the order check and continuing with placing the order.  
FIELD NUMBER: 14                        FIELD NAME: PHARMACIST
  LOCATION: 11;2                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the pharmacist who entered the pharmacist
 override comments.  
FIELD NUMBER: 14.1
  FIELD NAME: PHARMACIST COMMENTS DATE/TIME
  LOCATION: 11;3                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field represents the date and time that the
 Pharmacist Override Comments were entered.  
FIELD NUMBER: 50                        FIELD NAME: DISPENSE DRUGS
  LOCATION: 5;0                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The dispense drug(s) associated with the order check.  
FIELD NUMBER: 60                        FIELD NAME: GROUP ONE PHARMACY ORDERS
  LOCATION: 6;0                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Contains the interacting pharmacy pending inpatient
 orders, pending outpatient orders and outpatient prescriptions for duplicate
 drugs, drug-drug interactions, Clozapine and duplicate therapy order checks.  
FIELD NUMBER: 70                        FIELD NAME: GROUP TWO PHARMACY ORDERS
  LOCATION: 7;0                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Contains the interacting pharmacy non-VA medication, unit
 dose, and IV order numbers, as well as remote outpatient prescriptions, for
 the duplicate drugs, drug-drug interactions, Clozapine and duplicate therapy 
 order checks.  
FIELD NUMBER: 81                        FIELD NAME: INTERVENTION
  LOCATION: 8;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the pharmacy intervention that was taken for this
 order check.  
FIELD NUMBER: 82
  FIELD NAME: CLOZAPINE DISPENSING FREQUENCY
  LOCATION: 8;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is how often the patient is authorized to receive a
 Clozapine dosage at the time this order check was generated.  
FIELD NUMBER: 83                        FIELD NAME: DRUG INTERACTION SEVERITY
  LOCATION: 8;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field indicates the severity of the drug-drug
 interaction.  
FIELD NUMBER: 84                        FIELD NAME: DATABASE
  LOCATION: 8;4                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is the type of system that generated this order
 check instance.  
FIELD NUMBER: 90                        FIELD NAME: CLOZAPINE LAB RESULTS
  LOCATION: 9;0                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Contains the lab result(s) for Clozapine order checks.  
FIELD NUMBER: 100                       FIELD NAME: CLINICAL EFFECTS
  LOCATION: 10;0                        ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Contains the clinical effects for drug-drug interaction
 order checks.  
GLOBAL REFERENCE: ORD(100.05,D0,5,D1
FIELD NUMBER: .01                       FIELD NAME: DISPENSE DRUG
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The dispense drug associated with the order check.  
GLOBAL REFERENCE: ORD(100.05,D0,6,D1
FIELD NUMBER: .01                       FIELD NAME: GROUP ONE PHARMACY ORDER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Contains the interacting pharmacy pending inpatient
 order, pending outpatient order or outpatient prescription.  
FIELD NUMBER: 1                         FIELD NAME: ADDITIVE
  LOCATION: 1;0                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Contains the interacting IV additive(s).  
FIELD NUMBER: 2                         FIELD NAME: SOLUTION
  LOCATION: 2;0                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Contains the interacting IV solution(s).  
GLOBAL REFERENCE: ORD(100.05,D0,7,D1
FIELD NUMBER: .01                       FIELD NAME: GROUP TWO PHARMACY ORDER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Contains the interacting pharmacy non-VA medication, unit
 dose, and IV order number, as well as the remote outpatient prescription, for
 the duplicate drugs, drug-drug interactions, Clozapine and duplicate therapy 
 order check.  
FIELD NUMBER: 3                         FIELD NAME: ADDITIVE
  LOCATION: 1;0                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Contains the interacting IV additive(s).  
FIELD NUMBER: 4                         FIELD NAME: SOLUTION
  LOCATION: 2;0                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Contains the interacting IV solution(s).  
GLOBAL REFERENCE: ORD(100.05,D0,9,D1
FIELD NUMBER: .01                       FIELD NAME: CLOZAPINE LAB RESULT
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Contains the current lab results for a Clozapine order
 check.  
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to read and write to those fields specific to medication orders.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORDER CHECKS
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: JAN 12, 2009

NUMBER: 5333                            IA #: 5333
  DATE CREATED: JAN 08, 2009            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSGSICH1
  NAME: PROVIDER AND PHARMACIST OVER RIDE COMMENTS UTILITY
  ID: PSGSICH1
 GENERAL DESCRIPTION:   Utilities for printing Provider and Pharmacist Over
 Ride Comments and updating Pharmacist Over Ride Comments.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OVERRIDE
KEYWORDS: COMMENTS
KEYWORDS: CPRS
KEYWORDS: IMR
KEYWORDS: BCMA
COMPONENT/ENTRY POINT: DISP
 COMPONENT DESCRIPTION:   Display Provider and Pharmacist Over Ride Comments.  
 D DISP^PSGSICH1(ORPLACE,FLAG) ORPLACE is the place to find the information
 i.e. ^TMP($J,ORPLACE, FLAG is 1 to print both comments, 0 to print only
 Provider Over Ride Comments.  
VARIABLES: ORPLACE                      TYPE: Input
 VARIABLES DESCRIPTION:   Where to find the information.  See OCAPI^ORCHECK.  
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   1 to print both comments, 0 to print only Provider
 Over Ride Comments.  
COMPONENT/ENTRY POINT: UPD
 COMPONENT DESCRIPTION:   Add/Edit Pharmacist Comments.  
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   CPRS Order Number in ^ORD(100,IFN...  
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
 SUBSCRIBING DETAILS:   Called to print Provider and Pharmacist Over Ride
 Comments on reports.  
  DATE ACTIVATED: FEB 06, 2009

NUMBER: 5334                            IA #: 5334
  FILE NUMBER: 405                      GLOBAL ROOT: DGPM(
  DATE CREATED: JAN 11, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS ACCESS TO DGPM GLOBAL      ID: DGPM(
 GENERAL DESCRIPTION:   Access to Global nodes to check patient status and get
 type of movement 
    
    I '$D(^DGPM("C",DFN))          Check if inpatient/lodger 
    I $D(^DGPM(+DGPMVI(17),0))     Check if Discharge movement exists 
  
    Also the following access:   
     ^DGPM(D0,0) 
       .04   TYPE OF MOVEMENT            0;1   Global r 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5335                            IA #: 5335
  FILE NUMBER: 408.31                   GLOBAL ROOT: DGMT(408.31
  DATE CREATED: JAN 12, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  NAME: ANNUAL MEANS TEST ACCESS        ID: DGMT(408.31
 GENERAL DESCRIPTION:   The FBCS application accesses the ANNUAL MEANS TEST
 (#408.31) file to get the current means test status information.  
    
      ^DGMT(408.31,DGMTI,0) 
        .01   DATE OF TEST            0:1  Global r 
        .07   DATE/TIME COMPLETED     0:7  Global r 
        .11   AGREED TO PAY DEDUCT    0:11 Global r 
        .17   NO LONGER REQUIRED DATE 0:17 Global r 
        29    MEANS TEST SIGNED?      0:29 Global r 
      ^DGMT(408.31,D0,2) 
        2.07  REASON FOR EXEMPTION    2;7  Global r 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5336                            IA #: 5336
  FILE NUMBER: 411                      GLOBAL ROOT: PRC(411
  DATE CREATED: JAN 12, 2009            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS ACCESS TO GLOBAL PRC(411   ID: PRC(411
 GENERAL DESCRIPTION:   The Fee Basis Claims System accesses the .01 field of
 the ADMIN. ACTIVITY SITE PARAMETER (#411) file in order to setup a new
 obligation sequence number for a 7078.  
     
    ^PRC(411,D0,0) 
       .01      STATION/SUBSTATION CODE   0;1      Global Read 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5337                            IA #: 5337
  FILE NUMBER: 408.32                   DATE CREATED: JAN 12, 2009
  CUSTODIAL PACKAGE: REGISTRATION       USAGE: Controlled Subscription
  TYPE: File                            NAME: MEANS TEST STATUS ACCESS
 GENERAL DESCRIPTION:   The FBCS application accesses the ANNUAL MEANS STATUS
 (#408.32) file to get the message associated with the test status.  
  
     ^DG(408.32,D0,MSG) 
       100      MESSAGE              MSG:1   Global read 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5338                            IA #: 5338
  FILE NUMBER: 43                       GLOBAL ROOT: DG(43
  DATE CREATED: JAN 12, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  NAME: MAS PARAMETERS ACCESS           ID: DG(43
 GENERAL DESCRIPTION:   The FBCS application accesses the MAS PARAMETERS (#43)
 file to determine whether to display the abbreviated or detailed patient
 inquiry.  
  
      ^DG(43,D0,0) 
        38    ABBREVIATED PATIENT INQUIRY    0:38    Global read 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5339                            IA #: 5339
  FILE NUMBER: 355.4                    GLOBAL ROOT: IBA(355.4
  DATE CREATED: JAN 12, 2009            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ANNUAL BENEFITS ACCESS
  ID: IBA(355.4
 GENERAL DESCRIPTION:   
  The DSIV package is requesting FileMan read/write access to file #355.4 
 ANNUAL BENEFITS for the Insurance Capture Buffer application in order to add
 and edit entries.  
  
   ^IBA(355.4,D0,0) 
     .01  BENEFIT YEAR BEGINNING ON     0;1  FileMan read/write 
     .01  BENEFIT YEAR BEGINNING ON     0;1  Laygo new entry into file 
     .02  HEALTH INSURANCE POLICY       0;2  FileMan read/write 
     .05  MAX. OUT OF POCKET            0;5  FileMan read/write 
     .06  AMBULANCE COVERAGE (%)        0;6  FileMan read/write 
   ^IBA(355.4,D0,1) 
     1.01 DATE ENTERED                   1;1  FileMan read/write 
     1.02 ENTERED BY                     1;2  FileMan read/write 
     1.03 DATE LAST VERIFIED             1;3  FileMan read 
     1.04 VERIFIED BY                    1;4  FileMan read 
     1.05 DATE LAST EDITED               1;5  FileMan read 
     1.06 LAST EDIT BY                   1;6  FileMan read 
     1.07 PERSON CONTACTED               1;7  FileMan read/write 
     1.08 COMMENTS                       1;8  FileMan read/write 
     1.09 CONTACT'S PHONE NUMBER         1;9  FileMan read/write 
   ^IBA(355.4,D0,2) 
     2.01 ANNUAL DEDUCTIBLE (OPT)        2;1  FileMan read/write 
     2.02 PER VISIT DEDUCTIBLE           2;2  FileMan read/write 
     2.03 OUTPATIENT LIFETIME MAXIMUM    2;3  FileMan read/write 
     2.04 OUTPATIENT ANNUAL MAXIMUM      2;4  FileMan read/write 
     2.05 MH LIFETIME OUTPATIENT MAX.    2;5  FileMan read/write 
     2.06 MH ANNUAL OUTPATIENT MAX.      2;6  FileMan read/write 
     2.07 DENTAL COVERAGE TYPE           2;7  FileMan read/write 
     2.08 DENTAL COVERAGE $ OR %         2;8  FileMan read/write 
     2.09 OUTPATIENT VISIT (%)           2;9  FileMan read/write 
     2.1  EMERGENCY OUTPATIENT (%)       2;10 FileMan read/write 
     2.11 MENTAL HEALTH OUTPATIENT (%)   2;11 FileMan read/write 
     2.12 PRESCRIPTION (%)               2;12 FileMan read/write 
     2.13 OUTPATIENT SURGERY (%)         2;13 FileMan read/write 
     2.14 MH OPT. MAX DAYS PER YEAR      2;14 FileMan read/write 
     2.15 OUTPATIENT VISITS PER YEAR     2;15 FileMan read/write 
     2.17 ADULT DAY HEALTH CARE          2;17 FileMan read/write 
   ^IBA(355.4,D0,3) 
     3.01 HOME HEALTH CARE LEVEL         3;1  FileMan read/write 
     3.02 HOME HEALTH VISITS PER YEAR    3;2  FileMan read/write 
     3.03 HOME HEALTH MAX DAYS PER YEAR  3;3  FileMan read/write 
     3.04 HOME HEALTH MED. EQUIPMENT (%) 3;4  FileMan read/write 
     3.05 HOME HEALTH VISIT DEFINITION   3;5  FileMan read/write 
     3.06 OCCUPATIONAL THERAPY # VISITS  3;6  FileMan read/write 
     3.07 PHYSICAL THERAPY # VISITS      3;7  FileMan read/write 
     3.08 SPEECH THERAPY # VISITS        3;8  FileMan read/write 
     3.09 MEDICATION COUNSELING # VISITS 3;9  FileMan read/write 
   ^IBA(355.4,D0,4) 
     4.01 HOSPICE ANNUAL DEDUCTIBLE      4;1  FileMan read/write 
     4.02 HOSPICE INPATIENT ANNUAL MAX   4;2  FileMan read/write 
     4.03 HOSPICE INPT. LIFETIME MAX     4;3  FileMan read/write 
     4.04 ROOM AND BOARD (%)             4;4  FileMan read/write 
     4.05 OTHER INPATIENT CHARGES (%)    4;5  FileMan read/write 
     4.06 IV INFUSION OPT.               4;6  FileMan read/write 
     4.07 IV INFUSION INPT.              4;7  FileMan read/write 
     4.08 IV ANTIBIOTICS OPT.            4;8  FileMan read/write 
     4.09 IV ANTIBIOTICS INPT.           4;9  FileMan read/write 
   ^IBA(355.4,D0,5) 
     5.01 ANNUAL DEDUCTIBLE (INPATIENT)  5;1  FileMan read/write 
     5.02 PER ADMISSION DEDUCTIBLE       5;2  FileMan read/write 
     5.03 INPATIENT LIFETIME MAXIMUM     5;3  FileMan read/write 
     5.04 INPATIENT ANNUAL MAXIMUM       5;4  FileMan read/write 
     5.05 MH LIFETIME INPATIENT MAXIMUM  5;5  FileMan read/write 
     5.06 MH ANNUAL INPATIENT MAXIMUM    5;6  FileMan read/write 
     5.07 DRUG & ALCOHOL LIFETIME MAX    5;7  FileMan read/write 
     5.08 DRUG & ALCOHOL ANNUAL MAX      5;8  FileMan read/write 
     5.09 ROOM AND BOARD (%) (NJ3,0),    5;9  FileMan read/write 
     5.1  NURSING HOME (%) (NJ3,0),      5;10 FileMan read/write 
     5.11 MENTAL HEALTH INPATIENT (%)    5;11 FileMan read/write 
     5.12 OTHER INPATIENT CHARGES (%))   5;12 FileMan read/write 
     5.14 MH INPT. MAX DAYS PER YEAR     5;14 FileMan read/write 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5340                            IA #: 5340
  FILE NUMBER: 356.2                    GLOBAL ROOT: IBT(356.2
  DATE CREATED: JAN 12, 2009            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INSURANCE REVIEW ACCESS
  ID: IBT(356.2
 GENERAL DESCRIPTION:   The DSIV package is requesting FileMan read/write
 access to file #356.2 INSURANCE REVIEW for the Insurance Capture Buffer
 application in order to add and edit entries.  
   
  ^IBT(356.2,D0,0) 
    .01  REVIEW DATE                    0;1  FileMan read/write 
    .01  REVIEW DATE                    0;1  Laygo new entry into file 
    .02  TRACKING ID                    0;2  FileMan read/write 
    .03  RELATED REVIEW                 0;3  FileMan read/write 
    .04  TYPE OF CONTACT                0;4  FileMan read/write 
    .05  PATIENT                        0;5  FileMan read/write 
    .06  PERSON CONTACTED               0;6  FileMan read/write 
    .07  CONTACT PHONE #                0;7  FileMan read/write 
    .08  INSURANCE COMPANY CONTACTED    0;8  FileMan read/write 
    .1   APPEAL STATUS                  0;10 FileMan read/write 
    .11  ACTION                         0;11 FileMan read/write 
    .12  CARE AUTHORIZED FROM           0;12 FileMan read/write 
    .13  CARE AUTHORIZED TO             0;13 FileMan read/write 
    .14  DIAGNOSIS AUTHORIZED           0;14 FileMan read/write 
    .15  DATES OF DENIAL FROM           0;15 FileMan read/write 
    .16  DATES OF DENIAL TO             0;16 FileMan read/write 
    .17  METHOD OF CONTACT              0;17 FileMan read/write 
    .18  PARENT REVIEW                  0;18 FileMan read/write 
    .19  REVIEW STATUS                  0;19 FileMan read/write 
    .2   CASE PENDING                   0;20 FileMan read/write 
    .21  NO COVERAGE                    0;21 FileMan read/write 
    .22  FOLLOW-UP WITH APPEAL          0;22 FileMan read/write 
    .23  TYPE OF APPEAL                 0;23 FileMan read/write 
    .24  NEXT REVIEW DATE               0;24 FileMan read/write 
    .25  NUMBER OF DAYS PENDING APPEAL  0;25 FileMan read/write 
    .26  OUTPATIENT TREATMENT           0;26 FileMan read/write 
    .27  TREATMENT AUTHORIZED           0;27 FileMan read/write 
    .29  FINAL OUTCOME OF APPEAL        0;29 FileMan read/write 
  ^IBT(356.2,D0,1) 
    1.01 DATE ENTERED                   1;1  FileMan read/write 
    1.02 ENTERED BY                     1;2  FileMan read/write 
    1.03 DATE LAST EDITED               1;3  FileMan read/write 
    1.04 LAST EDITED BY                 1;4  FileMan read/write 
    1.05 HEALTH INSURANCE POLICY        1;5  FileMan read/write 
    1.07 DENY ENTIRE ADMISSION          1;7  FileMan read/write 
    1.08 AUTHORIZE ENTIRE ADMISSION     1;8  FileMan read/write 
  ^IBT(356.2,D0,2) 
    2.01 CALL REFERENCE NUMBER          2;1  FileMan read/write 
    2.02 AUTHORIZATION NUMBER           2;2  FileMan read/write 
  ^IBT(356.2,D0,11,D1,0) 
    .01  COMMENTS                       0;1  FileMan read/write 
  ^IBT(356.2,D0,12,D1,0)               
    .01  REASONS FOR DENIAL             0;1  FileMan read/write 
  ^IBT(356.2,D0,13,D1,0) 
    .01  PENALTY                        0;1  FileMan read/write 
    .02  AMOUNT OF PENALTY              0;2  FileMan read/write 
  ^IBT(356.2,D0,14,D1,0) 
    .01  APPROVE ON APPEAL FROM         0;1  FileMan read/write 
    .02  APPROVE ON APPEAL TO           0;2  FileMan read/write 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: MAR 22, 2013

NUMBER: 5341                            IA #: 5341
  FILE NUMBER: 355.32                   GLOBAL ROOT: IBA(355.32
  DATE CREATED: JAN 12, 2009            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PLAN COVERAGE LIMITATION
  ID: IBA(355.32
 GENERAL DESCRIPTION:   The DSIV package is requesting FileMan read/write
 access to file #355.32 PLAN COVERAGE LIMITATION for the Insurance Capture
 Buffer application in order to add and edit entries.  
   
  ^IBA(355.32,D0,0) 
     .01   PLAN               0;1    FileMan read/write 
     .01   PLAN               0;1    Laygo new entry into file 
     .02   COVERAGE CATEGORY  0;2    FileMan read/write 
     .03   EFFECTIVE DATE     0;3    FileMan read/write 
     .04   COVERAGE STATUS    0;4    FileMan read/write 
  ^IBA(355.32,D0,1) 
     1.03  DATE LAST EDITED   1;3    FileMan write 
     1.04  LAST EDITED BY     1;4    FileMan write 
  ^IBA(355.32,D0,2,D1,0) 
     .01   LIMITATION COMMENT 0;1    FileMan read/write 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5342                            IA #: 5342
  FILE NUMBER: 301.91                   GLOBAL ROOT: IVM(301.91
  DATE CREATED: JAN 12, 2009
  CUSTODIAL PACKAGE: INCOME VERIFICATION MATCH
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DSIV IVM FILE 301.91 ACCESS
  ID: IVM(301.91
 GENERAL DESCRIPTION:   The DSIV package is requesting FileMan read access to
 file #301.91 IVM REASONS FOR NOT UPLOADING INSURANCE for the Insurance Capture
 Buffer application in order to get the reasons for not uploading when
 rejecting buffer entries that were initiated by IVM.  
   
   ^IVM(301.91,D0,0) 
     .01  REASON CODE          0;1    FileMan read 
     .02  REASON DESCRIPTION   0;2    FileMan read 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 09, 2009

NUMBER: 5343                            IA #: 5343
  FILE NUMBER: 68                       GLOBAL ROOT: LRO(68,
  DATE CREATED: JAN 14, 2009            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: File
  NAME: ACCESSION DIV                   ID: LRO(68,
GLOBAL REFERENCE: LRO(68,D0,1,D1,1,D2,.4)
FIELD NUMBER: 26                        FIELD NAME: DIV
  LOCATION: .4;1                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the division of the person ordering
 the test for this accession number. The DUZ(2) is used to determine the
 division pointer. In some cases this field may be blank, example auto
 accession controls.  
  
 GENERAL DESCRIPTION:   The ONCOLOGY package needs to directly access (read
 only) the following field: 
  
 DIV sub-field (#26) within the ACCESSION NUMBER multiple (#1) within the DATE
 multiple (#2) of the ACCESSION file (#68) 
  
 This will allow ONCOLOGY casefinding to determine the division value of a LAB 
 DATA (#63) record.  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ACCESSION
KEYWORDS: ACCESSION NUMBER
KEYWORDS: DIV
SUBSCRIBING PACKAGE: ONCOLOGY

NUMBER: 5344                            IA #: 5344
  DATE CREATED: DEC 15, 2010
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA5344
  STATUS: Pending

NUMBER: 5345                            IA #: 5345
  FILE NUMBER: 41.41                    GLOBAL ROOT: DGS(41.41
  DATE CREATED: JAN 14, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS ACCESS TO GLOBAL DGS(41.41
  ID: DGS(41.41
GLOBAL REFERENCE: DGS(41.41,ADC,DFN,DGPDT)
 GLOBAL DESCRIPTION:   Checking the validity of a pre-registration date using: 
 S DGPDT="",DGPDT=$O(^DGS(41.41,"ADC",DFN,DGPDT),-1) 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5346                            IA #: 5346
  FILE NUMBER: 21                       GLOBAL ROOT: DIC(21
  DATE CREATED: JAN 14, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS ACCESS TO GLOBAL DIC(21    ID: DIC(21
GLOBAL REFERENCE: DIC(21,SVD)
FIELD NUMBER: .03                       FIELD NAME: CODE
  LOCATION: 0:3                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5347                            IA #: 5347
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: JAN 14, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS ACCESS TO PATIENT          ID: DPT(
 GENERAL DESCRIPTION:   FBCS needs access to the Eligibility Status date for
 demographic display.  
       
    ^DPT(D0,.361) 
       .3612  ELIGIBILITY STATUS DATE         .361;2  Fileman read 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5348                            IA #: 5348
  FILE NUMBER: 81.2                     GLOBAL ROOT: DIC(81.2
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  USAGE: Controlled Subscription        TYPE: File
  NAME: CPT COPYRIGHT                   ID: DIC(81.2
 GENERAL DESCRIPTION:   Read access to file 81.2 get the CPT Copyright
 information for a broker application.  The following data is read: 
    ^DIC(81.2,D0,1,0) 
     .01     SIGNON COPYRIGHT MESSAGE     0;1 
  
 This ICR will be retired upon release of patch ICPT*6.0*46.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5349                            IA #: 5349
  FILE NUMBER: 404.51                   GLOBAL ROOT: SCTM(404.51
  DATE CREATED: JAN 15, 2009            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS ACCESS TO GLOBAL SCTM(404.51
  ID: SCTM(404.51
GLOBAL REFERENCE: SCTM(404.51,D0,0)
FIELD NUMBER: .02                       FIELD NAME: TEAM PHONE NUMBER
  LOCATION: 0:2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   (#.02) TEAM PHONE NUMBER [2F] 
 GENERAL DESCRIPTION:   Use cloned logic from existing routine "SDPPTEM" to
 print Primary care team information to an array for the GUI interface.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5350                            IA #: 5350
  DATE CREATED: JAN 15, 2009            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: File
  NAME: MEDICAL PATIENT IEN
 GENERAL DESCRIPTION:   In CPRS v27, incorrect patient information could be
 displayed to the user.  In Consults, when the incorrect patient information
 was displayed, the user could attach a result note to the wrong patient's
 record.  
  
 Therefore, an agreement with Clinical Procedures is needed to allow the
 MEDICAL PATIENT IEN to be pulled from the Medicine files using $$GET1^DIQ
 based upon the Medicine Results stored in REQUEST/CONSULTATION file #123.  The
 IEN value will be reported on a Consults report which finds all ASSOCIATED
 RESULTS that are attached to the wrong patient.  
  
 This IA will be used one time for patch GMRC*3.0*70.  
     
 FILE#                           FIELD#                NODE   
 ------                          -------               -----
 690    MEDICAL PATIENT          .01 NAME              0;1 Read w/Fileman 
  
 691    ECHO                     1 MEDICAL PATIENT     0;2 Read w/Fileman 
  
 691.1  CARDIAC CATHETERIZATION  1 MEDICAL PATIENT     0;2 Read w/Fileman 
  
 691.5  ELECTROCARDIOGRAM (EKG)  1 MEDICAL PATIENT     0;2 Read w/Fileman 
                                                      
 691.6  HOLTER                   1 MEDICAL PATIENT     0;2 Read w/Fileman 
  
 691.7  EXERCISE TOLERANCE TEST  1 MEDICAL PATIENT     0;2 Read w/Fileman 
  
 691.8  ELECTROPHYSIOLOGY (EP)   1 MEDICAL PATIENT     0;2 Read w/Fileman 
  
 694    HEMATOLOGY               1 MEDICAL PATIENT     0;2 Read w/Fileman 
  
 698    GENERATOR IMPLANT        1 MEDICAL PATIENT     0;2 Read w/Fileman 
  
 698.1  V LEAD IMPLANT           1 MEDICAL PATIENT     0;2 Read w/Fileman 
  
 698.2  A LEAD IMPLANT           1 MEDICAL PATIENT     0;2 Read w/Fileman 
  
 698.3  PACEMAKER SURVEILLANCE   1 MEDICAL PATIENT     0;2 Read w/Fileman 
  
 699    ENDOSCOPY/CONSULT        .02 MEDICAL PATIENT   0;2 Read w/Fileman 
  
 699.5  GENERALIZED PROCEDURE/CONSULT 
                                 .02 MEDICAL PATIENT   0;2 Read w/Fileman 
  
 700    PULMONARY FUNCTION TESTS 1 MEDICAL PATIENT     0;2 Read w/Fileman 
  
 701    RHEUMATOLOGY             1 MEDICAL PATIENT     0;2 Read w/Fileman 
  STATUS: Pending
KEYWORDS: CONSULTS
KEYWORDS: MEDICAL PATIENT
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING

NUMBER: 5351                            IA #: 5351
  FILE NUMBER: 8925                     GLOBAL ROOT: TIU(8925
  DATE CREATED: JAN 16, 2009
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU STORE POINTER TO 8925
  ID: TIU(8925
 GENERAL DESCRIPTION:   This ICR documents the fact that DSIV has a field
 called TIU DOCUMENT (field #.08) in the DSI VISTA IMAGING QUEUE TRACKING file
 (#19621) that points to the TIU DOCUMENT file (#8925).  
  
     ^TIU(8925,DA,0) 
        .01      DOCUMENT TYPE        0;1      Pointed to 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5352                            IA #: 5352
  DATE CREATED: JAN 26, 2009
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUFLF7
  NAME: TIU GET TITLE IFN               ID: TIUFLF7
 GENERAL DESCRIPTION:   
  Lab use $$DDEFIEN^TIUFLF7 to find the Title IFN in 
  file 8925.1.  
  
 S LRTITLE=$$DDEFIEN^TIUFLF7("LR "_LRO68_" REPORT","TL") I 'LRTITLE  D .W $C(7) 
 .S LRMSG="No TIU title for this lab report.  Cannot release."      .D
 EN^DDIOL(LRMSG,"","!!") K LRMSG 
  
  
  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU
COMPONENT/ENTRY POINT: $$DEFIEN
 COMPONENT DESCRIPTION:   Get IFN for Title in TIU DOCUMENT file (#8925.1).  
  
  
VARIABLES: TIUDEFNM                     TYPE: Input
 VARIABLES DESCRIPTION:   .01 name of Title, Docmt Class or Class in the
 Document Definition file #8925.1 
  
VARIABLES: TIUTYPE                      TYPE: Input
 VARIABLES DESCRIPTION:   Expected type of DDEF: TL or DC or CL 
  
VARIABLES: IEN                          TYPE: Output
 VARIABLES DESCRIPTION:   Returns IEN^STATUS^NATL if exactly one DDEF of type
 TIUTYPE 
          ;        is found 
          ;     or 0^ErrMsg 
  
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   MH ADDED 2.15.2011 
  DATE ACTIVATED: FEB 13, 2009

NUMBER: 5353                            IA #: 5353
  DATE CREATED: JAN 27, 2009            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: UPDTICB
  NAME: Accept/Reject Insurance Buffer data APIs
  ID: UPDTICB
 GENERAL DESCRIPTION:   This ICR provides APIs for the IB Insurance Application
 which will suppress the Write Statements and Interactive Fileman calls for the 
 existing ACCEPT^IBCNBAR and REJECT^IBCNBAR logic. It includes logic to update
 the Patient Insurance Type (2.312) sub file with a new Group Insurance Plan
 and Insurance Company.  
  
 There is also an API (UPDTICB) which will allow for fields that are not stored
 in the insurance buffer to be updated into the IB Insurance Files.  
  
 Update:  IB*2*528 increased the data length of the COMMENT-PATIENT POLICY
 field (2.312, 1.08) from 80 characters to 250 characters; and therefore a new
 DD definition COMMENT-SUSCRIBER POLICY (2.342) subfile was created to store
 the increased length and the history of comments entered.   The UPDTICB
 component (API) will be affected by this change.  All subscribers to this ICR
 will need to make the necessary changes in their applications to reference the
 new field. When all subscribers have implemented the use of the new fields,
 the old fields will need to be deleted with a subsequent IB patch. Old and new 
 fields are noted at the UPDTICB component details.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ACCEPAPI
KEYWORDS: IBCNICB
KEYWORDS: REJECAPI
KEYWORDS: UPDTICB
COMPONENT/ENTRY POINT: ACCEPAPI()
 COMPONENT DESCRIPTION:   API to be called by the Insurance Capture Buffer
 (ICB) application to move buffer data to Insurance Files then cleanup. Usage
 of this entry will suppress write statements and interactive fileman calls. In
 addition to this, the follow are some difference that will only occur when
 this API is used: 
  
    1. Allows a new insurance group to be updated into 
       an existing patient policy entry. If this is 
       done there is cleanup logic that will delete 
       obsolete Individual Plans, Repoint Insurance 
       Reviews if Insurance Company changes, and 
       Remove any Old Benefits Used.  
  
    2. The PAT^IBCNBMI will not be called 
  
 Entry point with parameters - 
  
 ACCEPAPI(RESULT,IBBUFDA,DFN,IBINSDA,IBGRPDA,IBPOLDA,IBMVINS, 
 IBMVGRP,IBMVPOL,IBNEWINS,IBNEWGRP,IBNEWPOL,IVMREPTR) 
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Returned Parameter Array with IENS of new entries
 and/or errors/warnings.  
  
      RESULT(0) = -1 ^ error message 
      RESULT(0) =  0          -Move worked 
      RESULT(0) =  0 ^ warning message ^ warning message ^ warning message 
                   ^ warning message    
                              - Move worked but there may be zero to 4 
                                warning messages 
      RESULT(1) = "IBINSDA^" IEN of new Insurance Company (#36) 
      RESULT(1,"ERR",#) - Array with any FM errors when data updated from 
                          file 355.33 to 36.  
  
      RESULT(2) = "IBGRPDA^" IEN of new GROUP INSURANCE PLAN (#355.3) File 
      RESULT(2,"ERR",#) - Array with any FM errors when data updated from 
                          file 355.33 to 355.3.  
      RESULT(3) = "IBPOLDA^" IEN of new INSURANCE TYPE (#2.312) sub-file 
                  of PATIENT (#2) IEN 
      RESULT(3,"ERR",#) - Array with any FM errors when data updated from 
                          file 355.33 to 2.312. 
      RESULT(4) Contains the results of the call to UPDPOL^IBCNICB which is 
                used to update a new group into an existing patient policy 
                entry when applicable.  
         RESULT(4) =-1^error message 
         RESULT(4) =0 ^ message that process was successful or not required 
VARIABLES: IBBUFDA                      TYPE: Input
 VARIABLES DESCRIPTION:   INSURANCE BUFFER (#355.33) file internal entry number
 (IEN). (Required) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   PATIENT (#2) file IEN. (Required) 
VARIABLES: IBINSDA                      TYPE: Input
 VARIABLES DESCRIPTION:   INSURANCE COMPANY (#36) File IEN if not adding new
 entry. (Optional) 
VARIABLES: IBGRPDA                      TYPE: Input
 VARIABLES DESCRIPTION:   GROUP INSURANCE PLAN (#355.3) File IEN if not adding
 new entry. (Optional) 
VARIABLES: IBPOLDA                      TYPE: Input
 VARIABLES DESCRIPTION:   INSURANCE TYPE (#2.312) sub-file of PATIENT (#2) IEN
 if not adding new entry. (Optional) 
VARIABLES: IBMVINS                      TYPE: Input
 VARIABLES DESCRIPTION:   Move Type for INSURANCE. (Required) 
         1=Merge, 2=Overwrite, 3=Replace 
VARIABLES: IBMVGRP                      TYPE: Input
 VARIABLES DESCRIPTION:   Move Type for GROUP. (Optional) 
         1=Merge, 2=Overwrite, 3=Replace 
VARIABLES: IBMVPOL                      TYPE: Input
 VARIABLES DESCRIPTION:   Move Type for POLICY. (Optional)            
         1=Merge, 2=Overwrite, 3=Replace 
VARIABLES: IBNEWINS                     TYPE: Input
 VARIABLES DESCRIPTION:   Add new INSURANCE COMPANY flag (non-zero means add).  
VARIABLES: IBNEWGRP                     TYPE: Input
 VARIABLES DESCRIPTION:   Add new GROUP INSURANCE PLAN flag (non-zero means
 add).  
VARIABLES: IBNEWPOL                     TYPE: Input
 VARIABLES DESCRIPTION:   Add new patient insurance policy (non-zero means
 add).  
VARIABLES: IVMREPTR                     TYPE: Input
 VARIABLES DESCRIPTION:   IVM REASONS FOR NOT UPLOADING (#301.91) File internal
 entry number.  (Optional) 
COMPONENT/ENTRY POINT: REJECAPI(RESULT,IBBUFDA,IVMREPTR)
 COMPONENT DESCRIPTION:   API to be called by the Insurance Capture Buffer
 (ICB) application to reject buffer entry. Usage of this entry will suppress
 write statements and interactive fileman calls.  
VARIABLES: IBBUFDA                      TYPE: Input
 VARIABLES DESCRIPTION:   INSURANCE BUFFER (#355.33) file internal entry
 number. (required) 
VARIABLES: IVMREPTR                     TYPE: Input
 VARIABLES DESCRIPTION:   IVM REASONS FOR NOT UPLOADING (#301.91) File internal
 entry number. (Optional) 
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Returned parameter variable with errors messages if
 problems with the reject processing. Format for array.  
  
    REJECT = -1 ^ error message 
    REJECT =  0                     - Reject worked 
    REJECT =  0 ^ warning message   - Reject process worked but there is a 
                                      warning message 
COMPONENT/ENTRY POINT: UPDTICB()
 COMPONENT DESCRIPTION:   The UPDTICB^IBCNICB API provides functionality to
 update the following data elements: 
  
    Patient INSURANCE TYPE (#2.312) SUBFILE: 
       *COMMENT - PATIENT POLICY (#1.08) field 
       POLICY NOT BILLABLE (#3.04) field 
       Note:  IB*2*528 - COMMENT - PATIENT POLICY (1.08) replaced by 
       COMMENT-SUBSCRIBER POLICY (2.342).   
    
    COMMENT - SUBSCRIBER POLICY (#2.342) SUB-FILE: 
       COMMENT DATE/TIME (2.342,.01) 
       LAST EDITED BY (2.342,.02) 
       COMMENT (2.342,.03) 
  
  
    GROUP INSURANCE PLAN (#355.3) file: 
       PLAN FILING TIME FRAME (#.13) field 
       ELECTRONIC PLAN TYPE  (#.15) field 
       PLAN STANDARD FTF (#.16) field 
       PLAN STANDARD FTF VALUE (#.17) field 
       COMMENTS (#11) word-processing field 
  
 Entry point with parameters - 
                
 UPDTICB(RESULT,DFN,IBPOLDA,IBGRPDA,IBPOLCOM,IBPOLBIL, 
 IBPLAN,IBELEC,IBGPCOM,IBFTF,IBFTFVAL) 
  
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   PATIENT (#2) file Internal Entry Number.  (Required
 if IBPOLCOM or IBPOLBIL variables passed) 
VARIABLES: IBPOLDA                      TYPE: Input
 VARIABLES DESCRIPTION:   INSURANCE TYPE (#2.312) sub-file of PATIENT (#2)
 internal entry number.  (Required if IBPOLCOM or IBPOLBIL variables passed) 
VARIABLES: IBGRPDA                      TYPE: Input
 VARIABLES DESCRIPTION:   GROUP INSURANCE PLAN (#355.3) File internal entry
 number (Required if IBPLAN, IBELEC, IBGPCOM, IBFTF, or IBFTFVAL variables
 passed) 
VARIABLES: IBPOLCOM                     TYPE: Input
 VARIABLES DESCRIPTION:   Data to be filed into the *COMMENT - PATIENT POLICY
 (#1.08) file of the 2.312 sub-file.  (Optional) Note:  IB*2*528 -patch will
 implement the filing of the patient policy comment data and related fields
 into the fields defined to the COMMENT-SUBSCRIBER POLICY multiple (2.342): 
        COMMENT DATE/TIME (2.342,.01) 
        LAST EDITED BY (2.342,.02) 
        COMMENT (2.342,.03) 
  
  
VARIABLES: IBPOLBIL                     TYPE: Input
 VARIABLES DESCRIPTION:   Data to be filed into the POLICY NOT BILLABLE (#3.04)
 field of the 2.312 sub-file. (Optional) 
  
 Corresponds to the Internal codes in 3.04 field of 2.312 sub-file: 
     '0' FOR NO 
     '1' FOR YES 
VARIABLES: IBPLAN                       TYPE: Input
 VARIABLES DESCRIPTION:   Data to be filed in PLAN FILING TIME FRAME (#.13)
 field of 355.3 file.  (Optional) 
VARIABLES: IBELEC                       TYPE: Input
 VARIABLES DESCRIPTION:   Data to be file in ELECTRONIC PLAN TYPE (#.15) field
 of 355.3 file.  (Optional) 
  
 Corresponds to the Internal Codes in .15 field of 355.3 file: 
  
    '16' FOR HMO MEDICARE; 
    'MX' FOR MEDICARE A or B; 
    'TV' FOR TITLE V; 
    'MC' FOR MEDICAID; 
    'BL' FOR BC/BS; 
    'CH' FOR TRICARE; 
    '15' FOR INDEMNITY; 
    'CI' FOR COMMERCIAL; 
    'HM' FOR HMO; 
    'DS' FOR DISABILITY; 
    '12' FOR PPO; 
    '13' FOR POS; 
    'ZZ' FOR OTHER; 
VARIABLES: IBGPCOM                      TYPE: Input
 VARIABLES DESCRIPTION:   Group Plan Comment array that contains the word
 processing data to be filed the COMMENTS (#11) word-processing field of  355.3
 file. (Optional) 
  
 Example:  
     IBGPCOM(1)="This is line 1" 
     IBGPCOM(2)="This is line 2" 
VARIABLES: IBFTF                        TYPE: Input
 VARIABLES DESCRIPTION:   Data to be filed in the PLAN STANDARD FTF (#.16)
 field of 355.3 file.  (Optional) 
  
 Corresponds to the Internal Entry Number of the entry in the INSURANCE FILING
 TIME FRAME (#355.13) File.  
  
    1 - DAYS (Requires Plan Standard FTF Value) 
    2 - MONTH(S) (Requires FTF Value) 
    3 - YEAR(S) (Requires FTF Value) 
    4 - DAYS PLUS ONE YEAR (Requires FTF Value) 
    5 - DAYS OF FOLLOWING YEAR (Requires FTF Value) 
    6 - MONTHS OF FOLLOWING YEAR (Requires FTF Value) 
    7 - END OF FOLLOWING YEAR 
    8 - NO FILING TIME FRAME LIMIT 
VARIABLES: IBFTFVAL                     TYPE: Input
 VARIABLES DESCRIPTION:   Data to be filed in the PLAN STANDARD FTF VALUE
 (#.17) field of 355.3 file (Optional - Calling application responsible to pass
 value if required for Plan Standard FTF) 
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULT   - Returned Parameter Array with results of
 call 
     RESULT = 0 ^ No data to update 
     RESULT(1) = -1 ^ error with Insurance Type (#2.312) file update 
     RESULT(1) = 0                 - Insurance Type update worked 
     RESULT(2) = -1 ^ error with GROUP INSURANCE PLAN (#355.3) file update 
     RESULT(2) = 0                 - Group Insurance Plan update worked 
  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5354                            IA #: 5354
  DATE CREATED: JAN 29, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGMSE
  NAME: MILITARY SERVICE INFORMATION    ID: DGMSE
 GENERAL DESCRIPTION:   Patch DG*5.3*797 modifies the PATIENT file (#2) to
 support the entry of an unlimited number of military service episodes for the 
 patient. The storage of the service episodes is in the new MILITARY SERVICE
 EPISODE sub-file (#2.3216). The following APIs will return service episode
 data from the appropriate location in the PATIENT file.  
  
  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PATIENT FILE
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: MILITARY SERVICE
COMPONENT/ENTRY POINT: OEIF
 COMPONENT DESCRIPTION:   This returns a list of patients with OEF/OIF/UNK
 service in the specified date range. The data is returned in: 
  ^TMP($J,LSUB,DFN,FDATE,TDATE,SLOC,DA)="" 
  
 where 
  LSUB  - list subscript; see variable description below 
  DFN   - standard patient identifier 
  FDATE - from date of the service 
  TDATE - to date of the service 
  SLOC  - service location; it can be OEF, OIF, or UNK. UNK is used when the 
          location is unknown/cannot be disclosed 
  DA    - entry in OEF/OIF subfile 
  
 A patient will be included on the list if there is any overlap between the 
 date range defined by BDT-EDT and the date range defined by FDATE- TDATE.  
  
  
  
  
  
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the beginning date/time of the time period in
 which to search for OEF/OIF service.  
  
  
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the ending date/time of the time period in
 which to search for OEF/OIF service.  
  
VARIABLES: LSUB                         TYPE: Input
 VARIABLES DESCRIPTION:   The patient list data is returned in ^TMP($J,LSUB).  
  
COMPONENT/ENTRY POINT: MSDATA
 COMPONENT DESCRIPTION:   This entry point returns data for all episodes of
 service. The argument list is: MSDATA(DFN,NEPS,ENTRYDTA,MSDATA).  
  
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Standard patient identifier.  
  
VARIABLES: NEPS                         TYPE: Output
 VARIABLES DESCRIPTION:   The number of episodes of service that were found.  
  
VARIABLES: ENTRYDTA                     TYPE: Output
 VARIABLES DESCRIPTION:   This array has the following format: 
  ENTRYDTA(ENTRYDT)=N 
  
 Where ENTRYDT is the entry date for the Nth episode of service.  
  
VARIABLES: MSDATA                       TYPE: Output
 VARIABLES DESCRIPTION:   This array contains data for each episode of service.
 For the Nth episode of service the format is: 
  
 MSDATA(N,"ENTRY DATE") - This is the date the patient entered this episode of
 service.  
  
 MSDATA(N,"SEPARATION DATE") - This is the date the patient separated from this
 episode of service. If the patient has not yet separated this will be null.  
  
 MSDATA(N,"DATE") - This is the separation date; if there is no separation date
 then this is the entry date.  
  
 MSDATA(N,"BRANCH") - This is the branch of service in which the patient served
 for this episode of service.  
  
 MSDATA(N,"SERVICE COMPONENT") - This is the service component for this episode
 of service. The possible values are: REGULAR, ACTIVATED RESERVE, and ACTIVATED
 NG.  
  
 MSDATA(N,"DISCHARGE TYPE") - This is the discharge type for this episode of
 service. The possible values are in the Type of Discharge file #25. If the
 patient has not been discharged this will be null.  
  
  
  
VARIABLES:  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: JUL 18, 2011

NUMBER: 5355                            IA #: 5355
  DATE CREATED: FEB 02, 2009            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPUT3
  NAME: BILL INFORMATION                ID: IBNCPUT3
 GENERAL DESCRIPTION:   This APIs were created to provide detailed information
 about bills created for prescription/refills.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BILL
KEYWORDS: ECME
COMPONENT/ENTRY POINT: ISBILL
 COMPONENT DESCRIPTION:   To determine if there is a bill with a given bill #.  
VARIABLES: $$ISBILL                     TYPE: Output
 VARIABLES DESCRIPTION:   return value: 
  -file #399 ien if found 
  -zero if not found 
VARIABLES: IBBIL                        TYPE: Input
 VARIABLES DESCRIPTION:   Bill # - the value of the (#.01) BILL NUMBER field of
 the file (#399) is expected.  
COMPONENT/ENTRY POINT: BILINF
 COMPONENT DESCRIPTION:   Get bill details from file #399.  
VARIABLES: $$BILINF                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns two piece value: 
  Piece#1 : 
   -1 if an error 
   the payer sequence (P-primary, S-secondary,...) 
  Piece#2 : 
   error message if piece#1 = -1 
   otherwise - patient's DFN 
VARIABLES: IB399                        TYPE: Input
 VARIABLES DESCRIPTION:   Bill ien of the file (#399).  
VARIABLES: IBINFO                       TYPE: Both
 VARIABLES DESCRIPTION:   Output array, passed in by reference.  Format of data
 returned in the array: IBINFO("INS IEN") - insurance ien, ien of the file
 (#36) IBINFO("INS NAME") - insurance name as a text IBINFO("BILL #") - bill
 number, field (#.01) of the file (#399) IBINFO("AR STATUS") - Account
 Receivable status for the bill IBINFO("DOS") - date of service (FM format) 
 IBINFO("PLAN") - plan ien of (#355.3) IBINFO("FILL NUMBER") - refill number 
 IBINFO("PRESCRIPTION") - prescription ien of file (#52) IBINFO("IB STATUS") -
 value of STATUS field (.13) of the file (#399) 
COMPONENT/ENTRY POINT: RXBILL
 COMPONENT DESCRIPTION:   Find bill(s) for the specific RX/refill.  
VARIABLES: $$RXBILL                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns 2 pieces: 
  piece 1 - the number of bills found for the RX/refill 
  piece 2 - the latest active bill's ien 
VARIABLES: IBRXIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   IBRXIEN RX ien (#52).  
VARIABLES: IBRXREF                      TYPE: Input
 VARIABLES DESCRIPTION:   IBRXREF - refill number.  
VARIABLES: IBRXCOB                      TYPE: Input
 VARIABLES DESCRIPTION:   IBRXCOB - (optional) Payer Sequence ("P"- primary,"S"
 - secondary,"T" -tertiary.  
VARIABLES: IBDOS                        TYPE: Input
 VARIABLES DESCRIPTION:   IBDOS-(optional)Date of Service.  
VARIABLES: IBARR                        TYPE: Both
 VARIABLES DESCRIPTION:   IBARR - array, passed by reference to return the list
 of bills for the RX#.  Format: IBARR(IEN of the file #399 )=
 Bill#^status^date^insurance name^payer sequence^RX ien^Refill No^IB status 
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: AUG 25, 2010

NUMBER: 5356                            IA #: 5356
  DATE CREATED: FEB 04, 2009            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  NAME: BILL INFO                       STATUS: Pending

NUMBER: 5357                            IA #: 5357
  FILE NUMBER: 79.1                     GLOBAL ROOT: RA(79.1
  DATE CREATED: FEB 04, 2009
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Imaging-Radiology file 79.1
  ORIGINAL NUMBER: 5357                 ID: RA(79.1
GLOBAL REFERENCE: RA(79.1,D0,0
FIELD NUMBER: .01                       FIELD NAME: LOCATION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field points to the Hospital Location File, and
 contains the name of this location.  
FIELD NUMBER: 21                        FIELD NAME: CREDIT METHOD
  LOCATION: 0;21                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The type of credit this location will receive for this
 examination. 
FIELD NUMBER: 6                         FIELD NAME: TYPE OF IMAGING
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Enter an imaging type for this location.  
GLOBAL REFERENCE: RA(79.1,D0,'R',
FIELD NUMBER: 100                       FIELD NAME: CAMERAS/EQUIP/RMS
  LOCATION: (0;1)                       ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   VistA Radiology grants VistA Imaging 'read & write
 w/FileMan' privileges to the CAMERAS/EQUIP/RMS (#79.12) sub-file of which
 there exists only one field: CAMERA/EQUIP/RM (#.01) 
  
 Note: First piece of the 'R' data node; datatype: pointer to file #78.6.  
 GLOBAL DESCRIPTION:   CAMERA/EQUIP/RMS (#100) is a multiple field containing
 the cameras/equip/rms associated with a particular imaging location.  
 GENERAL DESCRIPTION:   Radiology gives Imaging permission to point to file
 IMAGING LOCATIONS (#79.1) in addition to reading and writing to the file.
 (with VA FileMan) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: No-credit location
KEYWORDS: outside camera/equip/rm
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   Imaging's file OUTSIDE IMAGING LOCATION (#2006.5759)
 points to Radiology file IMAGING LOCATIONS selecting only no-credit entries.
 This file is used by the DICOM Gateways to associate imported images to
 Radiology Outside locations.  
  DATE ACTIVATED: JAN 26, 2010

NUMBER: 5358                            IA #: 5358
  FILE NUMBER: 79.2                     GLOBAL ROOT: RA(79.2,
  DATE CREATED: FEB 04, 2009
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Imaging-Radiology file 79.2
  ORIGINAL NUMBER: 5357                 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.  
 GENERAL DESCRIPTION:   Radiology gives Imaging permission to point to file
 IMAGING TYPE (#79.2).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Outside Radiology locations
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   Imaging's file OUTSIDE IMAGING LOCATION (#2006.5759)
 points to Radiology file IMAGING TYPE (#79.2) selecting only Imaging Types
 associated to a no- credit IMAGING LOCATION.  This file is used by the DICOM
 Gateways to associate imported images to Radiology IMAGING LOCATIONS.  
  DATE ACTIVATED: MAR 17, 2009

NUMBER: 5359                            IA #: 5359
  FILE NUMBER: 78.6                     GLOBAL ROOT: RA(78.6,
  DATE CREATED: FEB 04, 2009
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Imaging- Radiology file 78.6
  ORIGINAL NUMBER: 5357                 ID: RA(78.6,
GLOBAL REFERENCE: RA(78.6,D0,0
FIELD NUMBER: .01                       FIELD NAME: CAMERA/EQUIP/RM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the name of the
 camera/equipment/room. 
FIELD NUMBER: 2                         FIELD NAME: DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field is used to describe this camera/equipment/room
 and define what types of procedures may be performed there.  
 GENERAL DESCRIPTION:   Radiology gives Imaging permission to read file
 CAMERA/EQUIP/RM (#78.6).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Outside reporting
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   Imaging reads Radiology's file CAMERA/EQUIP/RM file to
 provide a listing of entries to the DICOM Gateways when importing images from
 Outside locations.  
  DATE ACTIVATED: MAR 17, 2009

NUMBER: 5360                            IA #: 5360
  FILE NUMBER: 78.4                     GLOBAL ROOT: RA(78.4
  DATE CREATED: FEB 04, 2009
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Imaging- Radiology file 78.4
  ID: RA(78.4
GLOBAL REFERENCE: RA(78.4,DO,0
FIELD NUMBER: .01                       FIELD NAME: FILM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the names of the types of films that
 the hospital uses in performing rad/nuc med exams.  
 GENERAL DESCRIPTION:   Radiology gives Imaging permission to read file FILM
 SIZE (#78.4).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Outside Radiology reporting
  DATE ACTIVATED: MAR 17, 2009

NUMBER: 5361                            IA #: 5361
  DATE CREATED: FEB 05, 2009            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBOSRX
  NAME: IBOSRX                          ID: IBOSRX
 GENERAL DESCRIPTION:   This IA allows a subscribing package to call
 COLLECT^IBOSRX to identify and return potential secondary payer rx claims.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IBOSRX
COMPONENT/ENTRY POINT: COLLECT
 COMPONENT DESCRIPTION:   The COLLECT component returns: 
   ^TMP("BPSRPT9A",$J,n)=RX IEN^RX#^FILL#^BILL#^DFN^DATE^PRIMARY INS NAME^399
 IEN^TOTAL CHARGE 
   ^TMP("BPSRPT9A",$J,n,n,1)INSURANCE COMPANY IEN^INSURANCE COMPANY NAME 
   ^TMP("BPSRPT9A",$J,n,n,2)INURANCE COMPANY ADDRESS 
   ^TMP("BPSRPT9A",$J,n,n,7)COB INDICATOR^COB DESC 
VARIABLES: SDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Start date to begin search in FileMan format.  
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   End date in FileMan format.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
 SUBSCRIBING DETAILS:   ECME will call COLLECT^IBOSRX to collect and return an
 array of data for use in the Potential Secondary Rx Claims Report for
 Coordination of Benefits.  
  DATE ACTIVATED: AUG 25, 2010

NUMBER: 5362                            IA #: 5362
  DATE CREATED: FEB 06, 2009            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: PSB GETCOMMENTS
 GENERAL DESCRIPTION:   Gives the client VDL Provider and Pharmacy Over Ride
 information and Order Check Text.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PSB GETCOMMENTS
KEYWORDS: BCMA
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 5363                            IA #: 5363
  DATE CREATED: JAN 25, 2011            CUSTODIAL PACKAGE: HINQ
  NAME: HINQ Option Access              STATUS: Withdrawn

NUMBER: 5364                            IA #: 5364
  DATE CREATED: FEB 09, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFCPTAD
  NAME: ADD VAFCPTAD(PARAM)             ID: VAFCPTAD
 GENERAL DESCRIPTION:   
  Master Patient Index Austin (MPI) requests the ability to add a patient 
  to the PATIENT (#2) file via RPC VAFC VOA ADD PATIENT which calls 
  routine ADD^VAFCPTAD(PARAM).  
     
  A Remote Procedure Call containing the PARAM data adds a patient that 
  is new to the local PATIENT (#2) file.  This is to support the Veteran 
  On-Line Application (VOA) project within the MyHealtheVet system.  
   
  The information for the new record originates from Person Service 
  Identity Management (PSIM) and National Enrollment Service (ESR).  
  An in-person authentication vetting process is conducted by ESR 
  prior to invoking the VAFC VOA ADD PATIENT Remote Procedure.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ADD
 COMPONENT DESCRIPTION:   
  ADD^VAFCPTAD(RETURN,PARAM) allows Master Patient Index to add 
  a patient to the local VistA PATIENT (#2) file, passing the 
  data known in the PARAM array.  The data may include the 
  following fields:  (R - required; O - optional) 
   
   R     .01       NAME 
   R     .02       SEX 
   R     .03       DATE OF BIRTH 
   R     .09       SOCIAL SECURITY NUMBER 
         .0906     PSEUDO SSN REASON (if SSN is passed in as 
                   null, the .0906 value is automatically set 
                   to SSN UNKNOWN/FOLLOW-UP REQUIRED) 
   O     .092      PLACE OF BIRTH [CITY] 
   O     .093      PLACE OF BIRTH [STATE] 
   O     .2403     MOTHER'S MAIDEN NAME 
   R     .301      SERVICE CONNECTED? 
   R   27.02       PREFERRED FACILITY 
   R  391          TYPE 
   R 1901          VETERAN (Y/N)? 
   R  991.01       INTEGRATION CONTROL NUMBER 
   R  991.02       ICN CHECKSUM 
   O    1          ALIAS 
    
  The list will be passed with the following variable names 
  and values.  Some values are specified in the VHA Standard 
  Data Service tables.  Most input values are checked on VistA 
  (using CHK^DIE) to ensure that the required fields will 
  pass the input transform for that field.  The SERVICE 
  CONNECTED? (#.301) and VETERAN Y/N? (#1901) fields do not 
  call CHK^DIE, as the input transform is expecting the DFN 
  variable which is not yet defined.  If a required field 
  fails the CHK^DIE call, the entry is not created.  In that 
  case, the RPC returns an error message to the MPI indicating 
  why the call failed.  If all fields pass the CHK^DIE call, 
  then FILE^DICN is called to create the entry in the PATIENT 
  (#2) file.  
   
  Required: 
    PARAM("PRFCLTY")= Preferred Facility Station number.  
                      Station Number from the Institution List 
                      in the VHA Standard Data Service table.  
                      Facility Type must be VA MEDICAL CENTER.  
    PARAM("NAME")= Last Name^First Name^Middle Name^Suffix 
                   input is converted to: Last Name<comma> 
                   First Name<space>Middle Name<space>Suffix 
    PARAM("GENDER")= Code from the Gender List in the VHA 
                     Standard Data Service table: M for MALE 
                     OR F for FEMALE 
    PARAM("DOB")= mm/dd/yyyy 
                  2 digit MONTH followed by "/" delimiter 
                  followed by 2 digit DAY followed by "/" 
                  delimiter followed by 4 digit YEAR.  
                  Month and/or day alone, without year 
                  is not allowed.  
    PARAM("SSN")= nine numbers / no dashes, OR a NULL value.  
                  If SSN is sent with a null value, then on 
                  VistA, the patient is given a PSEUDO SSN 
                  number and the PSEUDO SSN REASON field is 
                  automatically set to SSN UNKNOWN/FOLLOW-UP 
                  REQUIRED.  
    PARAM("SRVCNCTD")= SERVICE CONNECTED? Y for YES OR N 
                       for NO.  
    PARAM("TYPE")= Patient TYPE. Code from the Patient Type 
                   List in the VHA Standard Data Service 
                   table.  
                   1 for ACTIVE DUTY, 
                   2 for ALLIED VETERAN, 
                   3 for COLLATERAL, 
                   4 for EMPLOYEE, 
                   5 for MILITARY RETIREE, 
                   6 for NON-VETERAN (OTHER), 
                   7 for NSC VETERAN, 
                   8 for SC VETERAN, OR 
                   9 for TRICARE.  
    PARAM("VET")= VETERAN YES/NO? Y for YES OR N for NO.  
    PARAM("FULLICN")= A 10 digit NUMBER, followed by V 
                      (delimiter), followed by a 6 digit 
                      CHECKSUM NUMBER.  
  Optional: 
    PARAM("POBCTY")= PLACE OF BIRTH [CITY].  
    PARAM("POBST")= 2 character STATE ABBREVIATION.  
    PARAM("MMN")= MOTHER'S MAIDEN NAME.  
    PARAM("ALIAS",#)= ALIAS NAME 
                      (last^first^middle^suffix)^ALIAS SSN 
   
  The IEN of the entry created in the PATIENT (#2) file 
  is returned.  
VARIABLES: PARAM                        TYPE: Input
 VARIABLES DESCRIPTION:   
  PARAM - is a list of the values passed in.  This 
  data is used to create the patient in the PATIENT 
  (#2) file.  
VARIABLES: DFN                          TYPE: Output
 VARIABLES DESCRIPTION:   
  DFN (if successful) 
  DFN is returned as the IEN of the PATIENT (#2) 
  file entry that was created in the session.  
  
  ERROR TEXT (if unsuccessful) 
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
  DATE ACTIVATED: APR 29, 2009

NUMBER: 5365                            IA #: 5365
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123
  DATE CREATED: FEB 11, 2009
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: REQUEST/CONSULTATION AIFC CROSS REFERENCE
  ID: GMR(123
GLOBAL REFERENCE: GMR(123,'AIFC'
 GLOBAL DESCRIPTION:   Index on ROUTING FACILITY & REMOTE CONSULT # 
 GENERAL DESCRIPTION:   Prosthetics requires access to the "AIFC" cross
 reference of file 123 in support of the Inter-Facility Consults (IFC) data
 interface for Prosthetics. Reference RMPR*3*83 and GMRC*3*44.  
  STATUS: Active
KEYWORDS: AIFC
KEYWORDS: IFC
KEYWORDS: PROSTHETICS
KEYWORDS: RMPR
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   Direct global read of the following: 
 ^GMR(123,"AIFC",routing_facility,remote_consult_ien,local_ien,0) Prevents RMPR
 from creating duplicate entries ensures GMRC has properly filed the HL7 data
 prior to being pointed to by RMPR 
  DATE ACTIVATED: JUN 12, 2009

NUMBER: 5366                            IA #: 5366
  DATE CREATED: FEB 12, 2009            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSODDPR4
  NAME: PHARMACY ENHANCED ORDER CHECKS MED PROFILE BUILDER
  ID: PSODDPR4
 GENERAL DESCRIPTION:   This API is used currently by CPRS and Inpatient Meds
 to build med profile data for both IP meds and OP meds to return enhanced
 order checks by using the new interface by First Data Bank (FDB).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: BLD(PSODFN,LIST,PDRG,PTY)
 COMPONENT DESCRIPTION:   This entry point returns any possible drug
 interactions and duplicate drug therapys.  Duplicate drug class order checks
 have been replaced with duplicate therapy checks.  
VARIABLES: PSODFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient's IEN 
VARIABLES: LIST                         TYPE: Both
 VARIABLES DESCRIPTION:   Global output base.  
VARIABLES: PDRG                         TYPE: Input
 VARIABLES DESCRIPTION:   Prospective drug(s) 
VARIABLES: PTY                          TYPE: Input
 VARIABLES DESCRIPTION:   A two piece variable (P1;P2).  P1 - package type (I
 or O). P2 Order number if available.  
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,"IN","PROFILE",PSOPON)=GCN ^ VUID ^IEN (File#50) ^ Drug Name ^ 
  CPRS Order Number ^ Package 
  Where: 
  PSOPON = Pharmacy order number in the format of P1;P2;P3;P4 P1 - Order type 
  It can be Z=Outpatient Prospective Drug, I=Inpatient, O=Outpatient, R=RDI; 
  P2 - Order number; P3 - Drug type (PROFILE/PROSPECTIVE); P4 - Counter 
  GCN = GCN sequence number (#50.68) 
  VUID = VA PRODUCT (#50.68) 
  IEN = Dispense drug internal entry number (#50) 
  Drug Name = Drug name of either the Orderable Item name (#50.7) or the 
  Generic Drug name (#50) CPRS Order Number = Internal entry number for 
  order in ^OR(100 if available 
  Package = Package indication - "O" for Outpatient; "I" for Inpatient 
COMPONENT/ENTRY POINT: CPRS(PSODFN,LIST,PDRG,PTY)
 COMPONENT DESCRIPTION:   This entry point returns any possible duplicate
 drugs, drug interactions and duplicate drug therapies.  Duplicate drug class
 order checks have been replaced with duplicate therapy checks.  
VARIABLES: PTY                          TYPE: Input
 VARIABLES DESCRIPTION:   A two piece variable (P1;P2).  P1 - package type (I
 or O). P2 Order number if available.  
VARIABLES: PSODFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient's IEN.  
VARIABLES: LIST                         TYPE: Both
 VARIABLES DESCRIPTION:   Global output base 
VARIABLES: PDRG                         TYPE: Input
 VARIABLES DESCRIPTION:   Prospective drug(s) list.  
VARIABLES: TMP($J,"DD",INDD,0)          TYPE: Output
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   
  ^TMP($J,LIST,"IN","PROFILE",PSOPON)=GCN ^ VUID ^IEN (File#50) ^ Drug Name ^ 
 CPRS Order Number ^ Package 
  Where: 
  PSOPON = Pharmacy order number in the format of P1;P2;P3;P4 P1 - Order type 
  It can be Z=Outpatient Prospective Drug, I=Inpatient, O=Outpatient, R=RDI; 
  P2 - Order number; P3 - Drug type (PROFILE/PROSPECTIVE); P4 - Counter 
  GCN = GCN sequence number (#50.68) 
  VUID = VA PRODUCT (#50.68) 
  IEN = Dispense drug internal entry number (#50) 
  Drug Name = Drug name of either the Orderable Item name (#50.7) or the 
  Generic Drug name (#50)  CPRS Order Number = Internal entry number for 
  order in ^OR(100 if available 
  Package = Package indication -  "O" for Outpatient; "I" for Inpatient 
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 14, 2023

NUMBER: 5367                            IA #: 5367
  DATE CREATED: FEB 13, 2009
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: OROCAPI
  NAME: EXPERT SYSTEM OCS               ID: OROCAPI
 GENERAL DESCRIPTION:   The purpose of this IA is to provide access to three
 order checks that are performed in the OE/RR Expert System.  
  STATUS: Active
KEYWORDS: ORDER CHECK
KEYWORDS: EXPERT SYSTEM
COMPONENT/ENTRY POINT: AOC
 COMPONENT DESCRIPTION:   This tag provides the AMINOGLYCOSIDE ORDERED ORDER
 CHECK 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   PATIENT IDENTIFIER 
VARIABLES: ORPROD                       TYPE: Input
 VARIABLES DESCRIPTION:   FILE 50.68 IEN (va product) 
VARIABLES: AOC                          TYPE: Output
 VARIABLES DESCRIPTION:   Output of function is a string with the second ^
 piece set to the file 100.8 IEN of the order check and the forth ^ piece set
 to the order check output text 
COMPONENT/ENTRY POINT: GOC
 COMPONENT DESCRIPTION:   GLUCOPHAGE LAB RESULTS ORDER CHECK 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   PATIENT IDENTIFIER 
VARIABLES: MEDTXT                       TYPE: Input
 VARIABLES DESCRIPTION:   FILE 50 LOCAL DRUG TEXT 
VARIABLES: GOC                          TYPE: Output
 VARIABLES DESCRIPTION:   Output of function is a string with the second ^
 piece set to the file 100.8 IEN of the order check and the forth ^ piece set
 to the order check output text 
COMPONENT/ENTRY POINT: DOC
 COMPONENT DESCRIPTION:   DANGEREOUS MEDS FOR PAT > 64 ORDER CHECK 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   PATIENT IDENTIFIER 
VARIABLES: OI                           TYPE: Input
 VARIABLES DESCRIPTION:   FILE 101.43 IEN - ORDERABLE ITEM 
VARIABLES: DOC                          TYPE: Output
 VARIABLES DESCRIPTION:   Output of function is a string with the second ^
 piece set to the file 100.8 IEN of the order check and the forth ^ piece set
 to the order check output text 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Pharmacy will use this IA to perform the three Expert
 System Order Checks: DANGEREOUS MEDS FOR PAT > 64 ORDER CHECK GLUCOPHAGE LAB
 RESULTS ORDER CHECK AMINOGLYCOSIDE ORDERED ORDER CHECK 
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Added for the Mocha Enhancements 2 project, patch
 PSJ*5*281 
  DATE ACTIVATED: JUL 15, 2014

NUMBER: 5368                            IA #: 5368
  DATE CREATED: JAN 26, 2011            CUSTODIAL PACKAGE: PROSTHETICS
  NAME: Prosthetics Option Access       STATUS: Withdrawn

NUMBER: 5369                            IA #: 5369
  DATE CREATED: FEB 13, 2009
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSHRQ2
  NAME: PHARMACY ENHANCED ORDER CHECKS FDB INTERFACE
  ID: PSSHRQ2
 GENERAL DESCRIPTION:   This API is used to request and get back order check
 results from a server using First DataBank's Drug Information Framework (DIF).
 This interface uses the Web Services to make the requests and get back
 results.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FDB
KEYWORDS: FIRST DATABANK
KEYWORDS: ORDER CHECKS
COMPONENT/ENTRY POINT: IN(BASE)
 COMPONENT DESCRIPTION:   This entry point returns in a ^TMP global the results
 of the First DataBank's enhanced order checks for drug-drug interactions,
 duplicate therapy and dosage checks.  
VARIABLES: BASE                         TYPE: Input
 VARIABLES DESCRIPTION:   This represents the second subscript of the submitted
 ^TMP($J) global.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: MEDICATION ORDER CHECK (MOCHA)
 SUBSCRIBING DETAILS:   Added 10/24/14 for use with Patch #'s PSO*7*411 and
 PSJ*5*281.  
  DATE ACTIVATED: OCT 28, 2014

NUMBER: 5370                            IA #: 5370
  DATE CREATED: FEB 19, 2009
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICDT
  NAME: DSICDT                          ID: DSICDT
 GENERAL DESCRIPTION:   This routine converts dates and times from one format
 into another. It can be called via a function call, or the RPC: DSIC DATE
 CONVERT.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CNVT
 COMPONENT DESCRIPTION:   Entry to convert date/times from one format to
 another. 
VARIABLES: INVAL                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the input date.time value to be converted. 
 If this parameters contains any alpha characters, this RPC will always assume
 that this input value is in external form (i.e., human readable format).  
VARIABLES: INTYPE                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional - only if INVAL contains an alpha character. 
 Else, this is required. Usually it is a single character.  If two characters,
 then it must be one of the first 6 listed below plus "I".  If INVAL="I" then 
 assume INVAL in external format.  
  
  "D" - INVAL is in Delphi internal format 
  "F" - INVAL is in internal Fileman format 
  "E" - INVAL is in external fmt (human read) 
  "M" - INVAL is in internal M format ($H) 
  "H" - INVAL is in HL7 format 
  "G" - INVAL is in UCT format 
  "I" - INVAL is in Internationalized format,i.e., 
        the day number precedes the month number 
VARIABLES: OUTYPE                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional - default value is internal Fileman format
 "F".  This is a string of characters designating output format(s) 
  
 If OUTYPE contains 
  "F" - return internal Fileman format 
  "D" - return internal Delphi format 
  "E" - return external format 
  "M" - return internal M format ($H) 
  "A" - return all formats 
  "H" - return HL7 format 
  "G" - return UCT format 
VARIABLES: OUTFMT                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional - this param controls the format of the
 returned value for external date value only.  OUTFMT can contain only a single
 digit plus optional alpha characters.  
  
 If OUTFMT = 
  "" then return mmm dd, yyyy@hh:mm:ss (default) 
  1  mmm dd, yyyy@hh:mm:ss - default 
  2  mm/dd/yy@hh:mm:ss [no leading zeros] 
  3  dd/mm/yy@hh:mm:ss [no leading zeros] 
  4  yy/mm/dd@hh:mm:ss [no leading zeros] 
  5  mm/dd/yyyy@hh:mm:ss [no leading zeros] 
  6  dd/mm/yyyy@hh:mm:ss [no leading zeros] 
  7  yyyy/mm/dd@hh:mm:ss [no leading zeros] 
  D  return date only 
  F  output with leading blanks 
  S  force seconds in outputs 
  Z  pad months and days with leading zeros 
  P  output time in ' hh:mm:ss am/pm' 
VARIABLES: TIMEFMT                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional - controls what portion of the time part of
 the date will be returned.  Default value is M 
  
  If TIMEFMT = H, then return only hours 
             = M, then return only hour:minute 
             = S, then return seconds 
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   Boolean - if allowed & equal to 1 then TAG was called
 as an extrinsic function, else it was called a DO (w/params).  
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   Passed by reference.  Return value for output date
 format.  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5371                            IA #: 5371
  DATE CREATED: FEB 19, 2009
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICDPT
  NAME: DSICDPT                         ID: DSICDPT
 GENERAL DESCRIPTION:   Contains entry points to get patient demographic data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DEM
 COMPONENT DESCRIPTION:   Returns specific patient demographic elements. RPC:
 DSIC DPT GET DEMO.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file#2 (patient DFN, or IEN).  You must
 pass either field DFN or SSN.  
VARIABLES: SSN                          TYPE: Input
 VARIABLES DESCRIPTION:   The 9 or 10 digit SSN (field .09 from file#2).  
VARIABLES: PERM                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a boolean flag (1 or 0).   The default value
 is zero. If one, then always return the patient's permanent address
 information.  
VARIABLES: DSICONF                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional field to determine whether or not to return
 the confidential address information.  If passed, then TODAY will be the
 default date to use to check to see if a confidential address is active for
 that date.  format = p1^p2 where: 
  p1=confidential address category - this is a string of 
   one or more numerics, e.g, 134, where category 
   numbers are: 
    1 for Eligibility/Enrollment 
    2 for Appointment/Scheduling 
    3 for Co-payments/Veterans Billing 
    4 for Medical Records 
    5 for All Others 
  
   p2 = fileman date to determine if confidential date 
        is effective.  Default value is TODAY 
VARIABLES: DSIFLG                       TYPE: Input
 VARIABLES DESCRIPTION:   If DSIFLG=0, return state abbreviation, a 5 or 9
 zip-code, and county name. If DSIFLG=1, return ien to file 5^state name^state
 abbreviation internal form of zip code^external zip code multiple ien
 value^county name.  
VARIABLES: DSICDAT                      TYPE: Output
 VARIABLES DESCRIPTION:   Passed by reference.  Contains the following array
 data: 
  DSICDAT()  Description 
   ---------  ----------------------
       1      patient name 
       2      ssn;dashed ssn 
       3      dob int;ext 
       4      age 
       5      sex 
       6      date of death int;ext 
       7      race 
       8      religion 
       9      marital status 
      10      employment status 
      11      1st st add 
      12      2nd st add 
      13      3rd st add 
      14      city 
      15      state  
      16      zip 
      17      county 
      18      home phone 
      19      work phone 
      20      LastName^FirstName^Middle^Suffix/Title 
   ------------------------------------------------
              see routine documentation for details 
      21      confidential address bitmap 
      22      street address 1 
      23      street address 2 
      24      street address 3 
      25      city 
      26      state abbr 
      27      zip 
      28      county 
   ----------------------------------------------
      29      primary elig^other elig^other elig^ 
      30      1 if patient is a veteran, else 0 
      31      code^name of current means test status 
COMPONENT/ENTRY POINT: ICN
 COMPONENT DESCRIPTION:   Returns ICN and a flag to denote whether ICN is local
 or national. Can be called as a function, or via RPC: DSIC DPT GET ICN.  
VARIABLES: PAT                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient lookup value, can be pointer to file#2 (DFN)
 or SSN (field .09 fr file #2 entry).  
VARIABLES: ISSSN                        TYPE: Input
 VARIABLES DESCRIPTION:   This Boolean (0, 1) flag indicates whether or not PAT
 (the patient lookup 
  value) is a SSN value.  
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   Boolean - if allowed & equal to 1 then TAG was called
 as an extrinsic function, else it was called a DO (w/params).  
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns ICN^flag where ICN is either a national or
 local ICN with checksum.  Flag is N:national; L:local.  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5372                            IA #: 5372
  DATE CREATED: FEB 19, 2009
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICLOCK
  NAME: DSICLOCK                        ID: DSICLOCK
 GENERAL DESCRIPTION:   Lock or unlock a global reference from a gui client or
 a funtion call.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LOCK
 COMPONENT DESCRIPTION:   Lock or unlock a global reference.  Can be called as
 a function or via the RPC: DSIC LOCK.  
VARIABLES: REF                          TYPE: Input
 VARIABLES DESCRIPTION:   This can be a closed form of a global or it can be a
 file number.  If it is a file number, then IFN is also required.  The file
 number can be the file number of the entire file or the subfile number of
 corresponding to the ^DD() value.  If it is a subfile, then the IFN parameter
 must be set accordingly.  
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number (record number) of
 the record that you wish to lock or unlock in the file specified in the REF
 parameter.  IFN is required if the REF parameter is a file or subfile number.  
  
 IFN is the IEN if you are locking the entire record.  If you are locking a
 subrecord in a multiple, the IFN must be a proper IENS at the appropriate
 level as documented in the Fileman DBS manuals.  
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   This flag indicates whether or not the global
 reference should be locked or unlocked.  The default value is 1 which means to
 lock the global.  If it has a value of -1 then unlock the global reference.  
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   Boolean flag to denote calling as a function (=1) vs
 calling from the rpc.  
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 if successful, else returns -1^error
 message.  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5373                            IA #: 5373
  DATE CREATED: FEB 19, 2009
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICVA
  NAME: DSICVA                          ID: DSICVA
 GENERAL DESCRIPTION:   Returns the default institution data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SITE
 COMPONENT DESCRIPTION:   Returns institution and station number.  Can be
 called as a function or via the RPC: DSIC VA DEFAULT SITE.  
VARIABLES: DIV                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the medical center division file
 (#40.8).  If it is not passed then return data for the primary division as of
 that date.  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   This optional Fileman date only will be used to
 return division data of that date.  Default value if not passed is TODAY.  
VARIABLES: FUN                          TYPE: Input
 VARIABLES DESCRIPTION:   Boolean flag to denote calling as a function (=1) vs
 calling from the rpc. 
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   Return p1^p2^p3^p4  where 
    p1 = pointer to Institution file (#4) 
    p2 = Institution file name 
    p3 = Station number 
    p4 = pointer to Medical Center Division file 
          (#40.8) for that division 
         which was the primary division as of that date.  
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5374                            IA #: 5374
  DATE CREATED: FEB 19, 2009
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DSICFM06
  NAME: DSICFM06                        ID: DSICFM06
 GENERAL DESCRIPTION:   Wrapper to FileMan utilities for accessing data
 dictionary structures.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: FIELD
 COMPONENT DESCRIPTION:   Returns the field attributes for a file.  Can be
 called via the RPC: DSIC FM GET FIELD ATTRIB.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This can be the file number or the full name of the
 file.  For subfiles, it must be the subfile number.  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the field number or the full name of the
 field.  
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag controlling what will be returned. The
 default value is <null>. If FLAG contains N then do not return attributes
 whose value is <null>. If FLAG contains Z, then for Word Processing
 attributes, include the zeroth node with the text.  
VARIABLES: ATT                          TYPE: Input
 VARIABLES DESCRIPTION:   List of attributes to return.  
  List[n] := attribute name  where n=0,1,2,3,...  
  List[0] := "*" to send all.  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Optional - default = 1. If TYPE=1, then return
 DSIC(attribute name)=value.  For wp fields, return DSIC(att name,#)=text, else
 return DSIC(#)=attribute name^value  [from RPC].  
VARIABLES: DSIC                         TYPE: Output
 VARIABLES DESCRIPTION:   Passed by reference.  Array of attributes, output is
 determined by TYPE parameter.  
COMPONENT/ENTRY POINT: MULT
 COMPONENT DESCRIPTION:   Return requested attributes for one or more fields in
 a file.  Can be accessed via RPC: DSIC FM GET FIELD ATTRIB MULT.  
VARIABLES: DSIN                         TYPE: Input
 VARIABLES DESCRIPTION:   Array containing the following label^value data: 
  
 DSIN(i) := label^value 
      i = 0,1,2,3,4,...  
  
 Label can be one of five values: FILE - req - file (or subfile) number or file
 name 
  
 FLAG - opt - N or <null> - default value is <null> 
        if FLAG["N" - do not return null attributes 
  
 ATT - req - list of field attributes to return 
             delimited by ';' 
  Examples: DSIN(i)="ATT^LABEL;TYPE;GLOBAL LOCATION;" 
            DSIN(i)="ATT^*" means get all field attrib 
  
 FIELD - req - field number or field name 
   Examples: DSIN(i)="FIELD^.01" 
             DSIN(i)="FIELD^.01;.02;.03;.09" 
VARIABLES: DSICM                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns List[i]=field #^attr name^attr value 
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5375                            IA #: 5375
  FILE NUMBER: 27.15                    GLOBAL ROOT: DGEN(27.15
  DATE CREATED: FEB 27, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ENROLLMENT STATUS
  ID: DGEN(27.15
GLOBAL REFERENCE: DGEN(27.15,D0,0
FIELD NUMBER: .001                      FIELD NAME: ENTRY NUMBER
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
  Master Patient Index Austin (MPI) will create an ENROLLMENT STATUS field 
  in our MPI FACILITY ASSOCIATION (#985.5) file.  This field will point to 
  the ENROLLMENT STATUS (#27.15) file.  Since the MPI is a central national 
  database, that environment does not currently contain this VistA file.  
  Development requests permission to place the ENROLLMENT STATUS (#27.15) 
  file on the Master Patient Index.  We will be responsible for keeping 
  the file current.  
   
  On the Master Patient Index, MPI will use direct global and FileMan 
  access to read the following fields of the ENROLLMENT STATUS (#27.15) 
  file.  
    
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
  DATE ACTIVATED: APR 20, 2009

NUMBER: 5376                            IA #: 5376
  DATE CREATED: JAN 26, 2011            CUSTODIAL PACKAGE: ENGINEERING
  NAME: Engineering Option Access       STATUS: Withdrawn

NUMBER: 5377                            IA #: 5377
  DATE CREATED: JAN 26, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  NAME: RADIOLOGY/NUCLEAR MEDICINE Option Access
  STATUS: Withdrawn

NUMBER: 5378                            IA #: 5378
  FILE NUMBER: 164.18                   GLOBAL ROOT: DD(164.18,0,'ID',
  DATE CREATED: MAR 04, 2009            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ONCOLOGY REMOVE IDENTIFIER DESIGNATION
  ID: DD(164.18,0,'ID',
GLOBAL REFERENCE: DD(164.18,0,'ID',1)
FIELD NUMBER: 1                         FIELD NAME: NSC NUMBER
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
 GENERAL DESCRIPTION:   ONCOLOGY needs to remove the IDENTIFIER label from the
 1 field (NSC NUMBER) in file 164.18 (CHEMOTHERAPEUTIC DRUGS).  This field has
 been designated a "Key field" thereby making the IDENTIFIER redundant.         
                
     
 This integration agreement exists so we can KILL ^DD(164.18,0,"ID",1) with 
 ONCOLOGY patch ONC*2.11*49.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IDENTIFIER
KEYWORDS: 164.18
SUBSCRIBING PACKAGE: ONCOLOGY
  DATE ACTIVATED: MAR 04, 2009

NUMBER: 5379                            IA #: 5379
  DATE CREATED: MAR 09, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGENA
  NAME: FBCS ACCESS TO DGENA            ID: DGENA
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$STATUS
 COMPONENT DESCRIPTION:   Returns ENROLLMENT STATUS from the patient's current
 enrollment.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN FROM FILE #2 OR FILE #161 
VARIABLES: Function Value               TYPE: Output
 VARIABLES DESCRIPTION:   
  If the patient has a current ENROLLMENT STATUS this function will return its
 value, otherwise it returns NULL.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  DATE ACTIVATED: APR 10, 2013

NUMBER: 5380                            IA #: 5380
  DATE CREATED: MAR 09, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: DGENPTA                      NAME: FBCS ACCESS TO DGENPTA
  ID: DGENPTA                           STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$VET(DFN)
 COMPONENT DESCRIPTION:   Used to determine if the patient is an eligible
 veteran 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN OF FILE #2 OR FILE #161 
VARIABLES: VET                          TYPE: Output
 VARIABLES DESCRIPTION:   returns 1 for Veteran or 0 if not a veteran or not
 eligible 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5381                            IA #: 5381
  DATE CREATED: MAR 09, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: DGNEQRY                      NAME: FBCS ACCESS TO DGENQRY
  ID: DGNEQRY                           STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$PENDING(DFN)
 COMPONENT DESCRIPTION:   Used to determine if, for a given patient, there is
 an enrollment query pending (STATUS=TRANSMITTED) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN OF FILE #2 OF FILE #161 
VARIABLES: PENDING                      TYPE: Output
 VARIABLES DESCRIPTION:   1 IF PENDING EXISTS OR 0 NONE 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5382                            IA #: 5382
  DATE CREATED: MAR 09, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: DGMTH                        NAME: FBCS ACCESS TO DGMTH
  ID: DGMTH                             STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$PENDING(STATUS)
 COMPONENT DESCRIPTION:   Gets the means test status name given the ien 
VARIABLES: STATUS                       TYPE: Both
 VARIABLES DESCRIPTION:   Gets the means test status name given the ien (Means
 test file #408.32) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5383                            IA #: 5383
  DATE CREATED: MAR 09, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: DGMTR                        NAME: FBCS ACCESS TO DGMTR
  ID: DGMTR                             STATUS: Retired
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: DOM
 COMPONENT DESCRIPTION:   Check if patient is in a DOM 
  ;  call to DOM checks if patient currently on a DOM ward 
  ;                                     (called from EN) 
  ;  call to DOM1 checks if patient on a DOM ward for a specific date 
  ;    before call to DOM1 - N VAINDT,VADMVT,DGDOM,DGDOM1 
  ;                          S VAINDT=specific date 
  ;                          S DFN=Patient IEN 
  ;                 output - DGDOM & DGDOM1 (defined and set to 1 if 
  ;                          patient on a DOM ward for specific date) 
VARIABLES: DFN                          TYPE: Both
 VARIABLES DESCRIPTION:   IEN OF FILE #2 OR FILE #161 
VARIABLES: DGDOM                        TYPE: Output
 VARIABLES DESCRIPTION:   SET TO 1 IF PT CURRENTLY ON DOM WARD 
VARIABLES: DGDOM1                       TYPE: Output
 VARIABLES DESCRIPTION:   SET TO 1 IF PATIENT IS ON DOM AT SPECIFOC DATE 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5384                            IA #: 5384
  DATE CREATED: MAR 09, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: DGPMV10                      NAME: FBCS ACCESS TO DGPMV10
  ID: DGPMV10
 GENERAL DESCRIPTION:   FBCS access to INP^DGPMV10 to set-up inpt variables
 needed (mimic VAIP array) 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: INP
 COMPONENT DESCRIPTION:   
  
 set-up inpt vbls needed (mimic VAIP array) returns last movement for patient 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Patient from file 2 or file 161 
VARIABLES: VAIP(D)                      TYPE: Input
 VARIABLES DESCRIPTION:   VAIP("D") needs to be set to "L" 
VARIABLES: VAX(DAT)                     TYPE: Output
 VARIABLES DESCRIPTION:   Date automatically set to NOW 
VARIABLES: X                            TYPE: Output
VARIABLES: DGPMCD                       TYPE: Output
 VARIABLES DESCRIPTION:   Date and time of last movement (FM) 
VARIABLES: DGPMVI                       TYPE: Output
 VARIABLES DESCRIPTION:   Array showing details of last inpatient movement.  
 DGPMVI(1)=IEN of last pt movement from file #405 DGPMVI(2)=(#.02) TRANSACTION
 [2P:405.3] DGPMVI(3)=Date of last movement in format "FM^External date@Time" 
 DGPMVI(4)=(#.18) MAS MOVEMENT TYPE [18P:405.2] DGPMVI(5)=(#.06) WARD LOCATION
 [6P:42] DGPMVI(6)=(#.07) ROOM-BED [7P:405.4] DGPMVI(13)=(#.14)
 ADMISSION/CHECK-IN MOVEMENT [14P:405] DGPMVI(13,1)=Details about the
 Admission/check-in movement DGPMVI(17)=(#.17) DISCHARGE/CHECK-OUT MOVEMENT
 [17P:405] 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5385                            IA #: 5385
  DATE CREATED: MAR 11, 2009            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSJAPIDS
  NAME: Dosing Checks for IVs           ID: PSJAPIDS
 GENERAL DESCRIPTION:   This API calls DOSE^PSSDSAPD to perform dosing checks
 for display in CPRS.  For full Output details, see the 'VistA to MOCHA
 Interface Document', located under the 'Pharm: Data Management (PDM)' section,
 under the 'Clinical' section of the VA Software Document Library (VDL).  
  
 Last Updated: June/2018 
        Patch: PSJ*5.0*538 
       Update: PSS*1.0*224 changed one of the output subscripts for the 
               Informational output message for the X(3) output.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DOSE
 COMPONENT DESCRIPTION:   This component provides CPRS with dosing checks for
 IV orders using the First DataBank (FDB) Drug Information Framework (DIF)
 interfaces and database.  
VARIABLES: P1                           TYPE: Input
 VARIABLES DESCRIPTION:   The parameter reference used as a subscript to
 identify the dosing checks data in the ^TMP global.  This is an array
 consisted of P(1)=Base, P(2)=Base1.  The output will be returned in
 ^TMP($J,Base and ^TMP($J,Base1.  
VARIABLES: P2                           TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number(DFN). This input is
 required.  
VARIABLES: P3                           TYPE: Input
 VARIABLES DESCRIPTION:   This is an array consisted of the following data: 
  P("INF_RATE") = Infusion Rate [Required for Continuous IV Type] (Ex: 125 
 ml/hr) 
  P("MR_IEN")   = Medication Route Internal Entry Number 
  P("IV_TYPE")  = 1 (Intermittent); 2 (Continuous) 
  P("SCHEDULE") = Administration Schedule (Free text) 
  P("TVOL_DUR") = Total Volume in the format of nUnit where n is a numeric 
 value and Unit of "H", "D", "L", "M", or, "DOSES". (Ex: 8H for 8 Hours, 2D for
 2 Days, 1L for 1 Liter, 100M for 100ML, 3DOSES for 3 Doses) 
  P("AD",CNT)   = P1^P2^P3^P4^P5 
  P("SOL",CNT)  = P1^P2^P3^^P5 
   Where: 
    P1 = Pharmacy Orderable Item IEN (#50.7) associates with the Additive 
         or Solution 
    P2 = Drug name (displayable name such as CPRS OI name) 
    P3 = Strength of the Additive, or Volume for the Solution 
    P4 = IV bag # for additive only.  
    P5 = 1 if the Enhanced order checks were done.  0 if not.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 24, 2024

NUMBER: 5386                            IA #: 5386
  DATE CREATED: MAR 13, 2009            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEXU
  NAME: LEXU Lookup Screens             ID: LEXU
 GENERAL DESCRIPTION:   This agreement includes common entry points for
 filtering Lexicon searches.  Similar to DIC("S") screens.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LEXU
KEYWORDS: $$SC
KEYWORDS: $$SO
COMPONENT/ENTRY POINT: $$SC(Y,STRING,DATE)
 COMPONENT DESCRIPTION:   This entry point filters Lexicon searches based on 
 Semantic Class/Types and Classification Codes.  
  
 DIC("S")/Screen Usage:  I $$SC^LEXU(Y,STRING,DATE) 
  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) of the
 Lexicon's EXPRESSION file 757.01.  
  
VARIABLES: STRING                       TYPE: Input
 VARIABLES DESCRIPTION:   This is a three piece ";" delimited string used by
 the filter/screen logic.  The first piece is called the "inclusion string" and
 list the Semantic Classes and Types to include in the search.  The second
 piece is called the "exclusion string" and list the Semantic Types to exclude
 from a search.  The third piece is called the "source string" and list
 classification sources to include in the search.  
  
 Detailed Example:  Problems and Diagnosis (including ICD, CPT and DSM) looks
 like this: 
  
 I
 $$SC^LEXU(Y,"BEH/DIS;999/64/66/73/74/77/82/169/170/171;ICD/CPT/CPC/DS4",DATE) 
  
 The full explanation: 
  
 Piece 1:  BEH/DIS Include expressions which relate to Behaviors and Diseases
 or Pathologic Processes.  
  
 Piece 2:  999/64/66/73/74/77/82/169/170/171 Exclude expressions which relate
 to Unknown or Untyped, Governmental or Regulatory Activity, Machine Activity, 
 Manufactured Object, Medical Device or Supplies, Conceptual Entity, Spatial
 Concept, Functional Concept, Intellectual Product and Language.   
  
 Piece 3:  ICD/CPT/CPC/DS4 Also include expressions which are linked to
 ICD-9-CM, CPT-4, HCPCS and coding systems.  
  
 In the filter string, Semantic Classes are identified by a 3 character
 mnemonic which can be found in the "B" cross-reference of the SEMANTIC CLASS
 file 757.11 and the Semantic Type is identified by internal entry number of
 the SEMANTIC TYPE file 757.12.  The coding systems are identified by a 3
 character mnemonic which can be found in the "ASAB" cross-reference of the
 CODING SYSTEMS file 757.03.  
  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   If applicable, this is the date service was provided 
 to the patient and passed in Fileman format.  Default is TODAY.  
  
COMPONENT/ENTRY POINT: $$SO(Y,STRING,DATE)
 COMPONENT DESCRIPTION:   This entry point filters Lexicon searches based on 
 Classification Codes.  
  
 DIC("S")/Screen Usage:  I $$SO^LEXU(Y,STRING,DATE) 
  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) of the
 Lexicon's EXPRESSION file 757.01.  
  
VARIABLES: STRING                       TYPE: Input
 VARIABLES DESCRIPTION:   This string is called the "source string" and is a
 list classification coding systems to include in the search.  The
 classification coding systems are identified by a 3 character mnemonic which
 can be found in the "ASAB" cross-reference of the CODING SYSTEMS file 757.03.  
  
 Example:   ICD/CPT/CPC/DS4 Means:     Search the Lexicon and include terms
 that are 
            linked to ICD-9-CM, CPT-4, HCPCS and DSM-4 
            coding systems.  
  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   If applicable, this is the date service was provided 
 to the patient and passed in Fileman format.  Default is TODAY.  
  
  DATE ACTIVATED: MAR 16, 2009

NUMBER: 5387                            IA #: 5387
  FILE NUMBER: 757.03                   GLOBAL ROOT: LEX(757.03
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Private                        TYPE: File
  NAME: Access to Lexicon file #757.03  ID: LEX(757.03
GLOBAL REFERENCE: LEX(757.03
 GENERAL DESCRIPTION:   Allows Radiology/Nuclear Medicine package to access
 Lexicon file #757.03, Coding System, to be used for Fileman lookup as in
 DIC("S") screen of medical terminology, diagnosis or classification.  
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 5388                            IA #: 5388
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9(
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Supported                      TYPE: File
  NAME: ICD-9 Diagnosis File 80         ID: ICD9(
GLOBAL REFERENCE: ICD9(D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ICD9('AB',
 GLOBAL DESCRIPTION:   Direct global read of the "AB" cross reference.  
  
GLOBAL REFERENCE: ICD9('BA',
 GLOBAL DESCRIPTION:   Direct global read of the "BA" cross reference.  
  
GLOBAL REFERENCE: ICD9('D',
 GLOBAL DESCRIPTION:   Direct global read of the "D" cross reference.  
  
GLOBAL REFERENCE: ICD9('AST',
 GLOBAL DESCRIPTION:   Direct global read of the "AST" cross reference.  
  
GLOBAL REFERENCE: ICD9('ACT'
 GLOBAL DESCRIPTION:   Direct global read of the "ACT" cross reference.  
  
 GENERAL DESCRIPTION:   This ICR will be retired upon ICD10 Implementation
 (retire action estimated to occur April 1,2016). New development efforts
 should use ICR 5747.  
  
 Applications may conduct Fileman lookups of ICD Diagnosis file #80 provided
 the 0 (zero) node is not returned as part of the output from the lookup. 
 Applications may also point to the ICD Diagnosis file #80.  This agreement 
 provides very limited access to file 80, primarily the .01 field and selected
 cross-references.  Additional access to file 80 is given through the use of
 APIs in routines ICDCODE and ICDAPIU.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: APR 01, 2016
KEYWORDS: ICD9
KEYWORDS: ICD-9
KEYWORDS: ICD-9-CM
KEYWORDS: CODE SET
KEYWORDS: CSV
  DATE ACTIVATED: APR 02, 2009

NUMBER: 5389                            IA #: 5389
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: IBARXEU0                     NAME: IBARXEU0
  ID: IBARXEU0                          STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$ON
 COMPONENT DESCRIPTION:   Checks if copay exemption testing is on 
    output 1 = exemption testing is active 
           0 = exemption testing is inactive (everybody non-exempt) 
          -1 = copay is off (everybody exempt) 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5390                            IA #: 5390
  DATE CREATED: MAR 16, 2009
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWORB GETDATA                  REMOTE PROCEDURE: ORWORB GETDATA
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5391                            IA #: 5391
  DATE CREATED: MAR 16, 2009
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWPT SELCHK                    REMOTE PROCEDURE: ORWPT SELCHK
 GENERAL DESCRIPTION:   Requires DFN input.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5392                            IA #: 5392
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBCHDI                       NAME: FBCS ACCESS TO FBCHDI
  ID: FBCHDI
 GENERAL DESCRIPTION:   The Fee Basis claims system calls END^FBCHDI after the
 GUI rpc DSIF INP COMPLETE PAYMENT processing which completes a CH payment in
 order to clean up all FB variables used by FB APIs.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: END
 COMPONENT DESCRIPTION:   Kill variables used by Fee.  Calls KILL^FBPAY which
 kills all variables set in the FBPAY* routines, other than FBX.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5393                            IA #: 5393
  FILE NUMBER: 161.91                   GLOBAL ROOT: FB(161.91
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #161.91 Read only     ID: FB(161.91
 GENERAL DESCRIPTION:   The FBCS GUI application reads the ADJUSTMENT REASON
 (#161.91) file using Fileman for selection by the user.  
  
    ^FB(161.91,D0,0) 
      .01  CODE                        0;1   Fileman r 
    ^FB(161.91,D0,1,D1,0) 
      .01   STATUS EFFECTIVE DATE      0;1   Fileman r 
       1   STATUS                      0;2   Fileman r 
       2   FEE USE                     0;3   Fileman r 
    ^FB(161.91,D0,2,D1,0) 
      .01  DESCRIPTION EFFECTIVE DATE  0;1   Fileman r 
    ^FB(161.91,D0,2,D1,D,D2,0) 
      .01  DESCRIPTION                 0;1   Fileman r 
    ^FB(161.91,D0,4,D1,0) 
      .01  SUSPENSION DESCRIPTION      0;1   Fileman r 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5394                            IA #: 5394
  FILE NUMBER: 161.92                   GLOBAL ROOT: FB(161.92
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #161.92 Read only     ID: FB(161.92
 GENERAL DESCRIPTION:   The FBCS GUI application reads the ADJUSTMENT GROUP
 (#161.92) file using Fileman.  
  
    ^FB(161.92,D0,0) 
      .01   CODE                       0;1   Fileman r 
    ^FB(161.92,D0,1,D1,0) 
      .01  STATUS EFFECTIVE DATE       0;1   Fileman r 
       1   STATUS                      0;2   Fileman r 
       2   FEE USE                     0;3   Fileman r 
    ^FB(161.92,D0,2,D1,0) 
      .01  DESCRIPTION EFFECTIVE DATE  0;1   Fileman r 
      .02  SHORT DESCRIPTION           0;2   Fileman r 
    ^FB(161.92,D0,2,D1,D,D2,0) 
      .01  DESCRIPTION                 0;1   Fileman r 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5395                            IA #: 5395
  FILE NUMBER: 161.93                   GLOBAL ROOT: FB(161.93
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File 161.93 Read only      ID: FB(161.93
 GENERAL DESCRIPTION:   The FBCS application reads the REMITTANCE REMARK
 (#161.93) file using Fileman and checks for existence of the node.  
  
    ^FB(161.93,D0,0) 
      .01 CODE                         0;1   Fileman r,Global r 
    ^FB(161.93,D0,1,D1,0) 
      .01 STATUS EFFECTIVE DATE        0;1   Fileman r 
      1   STATUS                       0;2   Fileman r 
      2   FEE USE                      0;3   Fileman r 
    ^FB(161.93,D0,2,D1,0) 
     .01  DESCRIPTION EFFECTIVE DATE   0;1   Fileman r 
    ^FB(161.93,D0,2,D1,D,D2,0) 
     .01  DESCRIPTION                  0;1   Fileman r 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5396                            IA #: 5396
  FILE NUMBER: 162.95                   GLOBAL ROOT: FB(162.95
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File 162.95 Read only      ID: FB(162.95
 GENERAL DESCRIPTION:   The FBCS application reads the FEE BASIS CHECK
 CANCELLATION REASON (#162.95) file to get cancellation reasons.  
  
    ^FB(162.95,D0,0) 
      .01  CANCELLATION REASON         0;1  Global r 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5397                            IA #: 5397
  FILE NUMBER: 162.7                    GLOBAL ROOT: FB583(
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  NAME: FBCS File #162.7 Read only      ID: FB583(
 GENERAL DESCRIPTION:   The FBCS application reads the FEE BASIS UNAUTHORIZED
 CLAIMS (#162.7) file.  
     
       ^FB583(D0,0)                               $D(node) 
         .01  DATE CLAIM RECEIVED           0;1   Global r 
         .5   FEE PROGRAM                   0;2   Global r 
         1    VENDOR                        0;3   Global r 
         2    VETERAN                       0;4   Global r 
         3    TREATMENT FROM DATE           0;5   Global r 
         4    TREATMENT TO DATE             0;6   Global r 
         9    PATIENT TYPE CODE             0;10  Global r 
         10   DISPOSITION                   0;11  Global r 
         12   AUTHORIZED FROM DATE          0;13  Global r 
         13   AUTHORIZED TO DATE            0;14  Global r 
         19   PRINT LETTER?                 0;16  Global r 
         23   CLAIM SUBMITTED BY            0;23  Global r 
         24   STATUS                        0;24  Global r 
         30   AUTHORIZATION                 0;27  Global r 
         31   38 U.S.C. 1725                0;28  Global r 
      ^FB583(D0,5) 
         32   FPPS CLAIM ID                 5;1   Global r 
      ^FB583(D0,LOG1,D1,0) 
         .01  DATE/TIME EDITED              0;1   Fileman r 
          1   EDITED BY                     0;2   Fileman r 
          2   COMMENTS                      0;3   Fileman r 
       ^FB583(DO,LOG2,D1,0) 
         .01  CHANGED DATE/TIME             0;1   Fileman r 
          1   FIELD                         0;2   Fileman r 
          2   OLD VALUE                     0;3   Fileman r 
          3   NEW VALUE                     0;4   Fileman r 
          4   CHANGED BY                    0;5   Fileman r 
  
       ^FB 
         
       ^FB583("AD") Used to lookup by Program and AUTHORIZED FROM DATE 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: APR 29, 2016

NUMBER: 5398                            IA #: 5398
  FILE NUMBER: 161.25                   GLOBAL ROOT: FBAA(161.25
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #161.25 R/W           ID: FBAA(161.25
 GENERAL DESCRIPTION:   The FBCS application accesses the FEE BASIS VENDOR
 CORRECTION (#161.25) file when transmitting/re-transmitting record data to
 Austin.  
    
    ^FBAA(161.25,D0,0)                    Global r ($D) 
       4   DATE TRANSMITTED        0;5    Global w (set to null) 
  
    ^FBAA(161.25,"AE")  Used to check if txns require transmission 
                        direct global set of xref 
    ^FBAA(161.25,"AD")  Used to check if MRAs were xmitted on sel dt 
                        direct global kill of xref for date 
    ^FBAA(161.25,"AF")  Used to check if the vendor is a linked vendor 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5399                            IA #: 5399
  FILE NUMBER: 161.26                   GLOBAL ROOT: FBAA(161.26
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #161.26 R/W           ID: FBAA(161.26
 GENERAL DESCRIPTION:   The FBCS application accesses the FEE BASIS PATIENT MRA
 (#161.26) file when transmitting/re-transmitting record data to Austin.  
    
    ^FBAA(161.26,D0,0) 
      .01  NAME                           0;1   Fileman w, Laygo 
       1   STATUS                         0;2   Fileman w Global w 
       2   POINTER TO AUTHORIZATION NODE  0;3   Fileman w 
       3   TYPE                           0;4   Fileman w 
       4   DATE TRANSMITTED               0;5   Global w 
       5   AUTH. FROM DATE CHANGED        0;6   Fileman w 
       6   SHORT TERM MRA                 0;7   Fileman w 
  
  
    ^FBAA(161.26,"AC")  Used to check if txns require transmission 
                        direct global set/kill of xref 
    ^FBAA(161.26,"AD")  Used to check if MRAs were xmitted on selected dt 
                        direct global kill of xref for date 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5400                            IA #: 5400
  FILE NUMBER: 161.27                   GLOBAL ROOT: FBAA(161.27
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #161.27 Read only     ID: FBAA(161.27
 GENERAL DESCRIPTION:   The FBCS application accesses the FEE BASIS SUSPENSION
 (#161.27) file to get suspense codes.  
                           
    ^FBAA(161.27,D0,0) 
      .01   CODE                  0;1   Global r 
    ^FBAA(161.27,D0,2) 
      2     SHORT DESCRIPTION     0;1   Global r 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5401                            IA #: 5401
  FILE NUMBER: 161.8                    GLOBAL ROOT: FBAA(161.8
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #161.8 Read only      ID: FBAA(161.8
 GENERAL DESCRIPTION:   The FBCS application accesses the FEE BASIS PROGRAM
 (#161.8 file to get the Program names and verify if the program is active.  
                           
    ^FBAA(161.8,D0,0)                          Global r ($D) 
      .01  NAME                           0;1  Global r,Fileman r 
      2    ACTIVE?                        0;3  Global r,Fileman r 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5402                            IA #: 5402
  FILE NUMBER: 161.81                   GLOBAL ROOT: FBAA(161.81
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #161.81 Read only     ID: FBAA(161.81
 GENERAL DESCRIPTION:   The FBCS application accesses the FEE BASIS
 PARTICIPATION CODE (#161.81) file to get participation codes.  
     
     ^FBAA(161.81,D0,0) 
       .01   NAME           0;1    Global r 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5403                            IA #: 5403
  FILE NUMBER: 161.82                   GLOBAL ROOT: FBAA(161.82
  DATE CREATED: MAR 16, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #161.82 Read only     ID: FBAA(161.82
 GENERAL DESCRIPTION:   The FBCS application accesses the FEE BASIS PURPOSE OF
 VISIT (#161.82) file to get names and codes of active purposes.  
     
    ^FBAA(161.82,D0,0)                      Global r ($D) 
      .01 NAME                         0;1  Global r, Fileman r 
      3   AUSTIN CODE                  0;3  Global r, Fileman r 
    ^FBAA(161.82,D0,I) 
      4   INACTIVATION DATE            I;1  Fileman r 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5404                            IA #: 5404
  FILE NUMBER: 80.1                     GLOBAL ROOT: ICD0(
  DATE CREATED: MAR 17, 2009            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Supported                      TYPE: File
  NAME: ICD-9 Operation/Procedure file 80.1
  ID: ICD0(
GLOBAL REFERENCE: ICD0(D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ICD0('BA',
 GLOBAL DESCRIPTION:   Direct global read of the "BA" cross reference.  
  
GLOBAL REFERENCE: ICD0('ACT'
 GLOBAL DESCRIPTION:   Direct global read of the "ACT" cross reference.  
  
 GENERAL DESCRIPTION:   This ICR will be retired upon ICD10 Implementation
 (retire action estimated to occur April 1,2016). New development efforts
 should use ICR 5747.  
  
 Applications may conduct Fileman lookups of ICD Operation Procedure file #80.1
 provided the 0 (zero) node is not returned as part of the output from the
 lookup.  Applications may also point to the ICD Operation/Procedure file
 #80.1.  This agreement provides very limited access to file 80.1, primarily
 the .01 field and selected cross-references.  Additional access to file 80.1
 is given through the use of APIs in routines ICDCODE and ICDAPIU.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: APR 01, 2016
KEYWORDS: ICD0
KEYWORDS: OPERATION
KEYWORDS: PROCEDURE
KEYWORDS: ICD-9
KEYWORDS: ICD-9-CM
KEYWORDS: CODE SET
KEYWORDS: CSV
  DATE ACTIVATED: APR 02, 2009

NUMBER: 5405                            IA #: 5405
  FILE NUMBER: 81                       GLOBAL ROOT: DD(81
  DATE CREATED: MAR 17, 2009            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CPT File 81 Surgical Identifier
  ID: DD(81
GLOBAL REFERENCE: DD(81,0,'ID',6)
 GLOBAL DESCRIPTION:   
  
 File Identifier: 
  
 ^DD(81,0,"ID",6)=D EN^DDIOL(("  "_$$IDCPF^ICPTID(+Y)),"","?0") 
      D:$D(SRSITE) ^SROCPT 
  
 Where $$IDCPF returns the Versioned Short Name from field #61, and the
 Versioned Status from field #60 (only if Inactive), and ^SROCPT returns the
 Versioned Description from field #62.  
  
  
 GENERAL DESCRIPTION:   The DD for the CPT file #81 includes the following DD
 Identifier node which causes the CPT Versioned Description field #62 to be 
 displayed when a lookup is done on the CPT file: 
  
   ^DD(81,0,"ID",6)=D EN^DDIOL(("  "_$$IDCPF^ICPTID(+Y)),"","?0") 
        D:$D(SRSITE) ^SROCPT 
  
 An agreement is established for Surgery to call ^DD(81,0,"ID",6). This DD node
 will remain in place to assist with CPT lookups from within the Surgery
 package.  Surgery will be responsible for support of the conditional call to
 ^SROCPT.  
  
 The following MUMPS code will be included with the file Identifier supporting
 the Surgery Package to display the Versioned Description field #62 using the
 Code Set Versioning API $$CPTD^ICDCODE: 
  
     D:$D(SRSITE) ^SROCPT 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICPT(
KEYWORDS: DD(81
KEYWORDS: SURGERY
KEYWORDS: CPT-4
KEYWORDS: CPT/HCPCS
KEYWORDS: HCPCS
KEYWORDS: CODE SET
KEYWORDS: CSV
SUBSCRIBING PACKAGE: SURGERY
 SUBSCRIBING DETAILS:   
  
  DATE ACTIVATED: APR 02, 2009

NUMBER: 5406                            IA #: 5406
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: MAR 17, 2009            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Proxy User in File 200
  ID: VA(200
GLOBAL REFERENCE: VA(200,D0,.13)
FIELD NUMBER: .132                      FIELD NAME: OFFICE PHONE
  LOCATION: .13;2                       ACCESS: Write w/Fileman
GLOBAL REFERENCE: VA(200,D0,1)
FIELD NUMBER: 9                         FIELD NAME: SSN
  LOCATION: 1;9                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: VA(200,D0,2,0)
FIELD NUMBER: 16                        FIELD NAME: DIVISION
  LOCATION: 2;0                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: VA(200,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DIVISION
  LOCATION: 0;1                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: VA(200,D0,5)
FIELD NUMBER: 29                        FIELD NAME: SERVICE/SECTION
  LOCATION: 5;1                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: VA(200,D0,USC3,0)
FIELD NUMBER: 9.5                       FIELD NAME: USER CLASS
  LOCATION: USC3;0                      ACCESS: Write w/Fileman
GLOBAL REFERENCE: VA(200,D0,USC3,D1,0)
FIELD NUMBER: .01                       FIELD NAME: User Class
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ISPRIMARY
  LOCATION: 0;2                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   
  The Veteran On-Line Application (VOA) project will make it easier 
  for veterans to register for medical benefits from VHA via the web.  
  National Enrollment Service (ESR), through Person Service Identity 
  Management (PSIM), uses a Remote Procedure to add a patient record 
  at the designated Preferred VistA Facility after the proper vetting 
  process.  
    
  The Remote Procedure is invoked on the Master Patient Index Austin 
  by PSIM via a proxy user in the NEW PERSON (#200) file.  This proxy 
  user is assigned the PSIM GUI VistALink Access [MPI PSIM GUI 
  INTERFACE] secondary menu option.  The user NAME and SECONDARY MENU 
  OPTION fields are created using the $$CREATE^XUSAP(proxyname,fmac, 
  options) API in IA# 4677.  The other fields populated are listed below.  
    
  Because testing takes place on multiple "MPI" environments before 
  final installation on the national Austin Master Patient Index, the 
  PSUSER,APPLICATION PROXY user will be created in a post-init routine.  
  This ensures that the fields required for the RPC to work successfully 
  are created.  
   
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
  DATE ACTIVATED: APR 20, 2009

NUMBER: 5407                            IA #: 5407
  DATE CREATED: MAR 17, 2009
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWTPN
  NAME: OE/RR GET DEFAULT COSIGNER FOR USER
  ID: ORWTPN
 GENERAL DESCRIPTION:   Clinical Procedures would like use the entry point
 GETDCOS^ORWTPN to get the default cosigner for the user.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORWTPN
COMPONENT/ENTRY POINT: GETDCOS
 COMPONENT DESCRIPTION:   Returns the default cosigner for a user.  
  
VARIABLES: VALUE                        TYPE: Output
 VARIABLES DESCRIPTION:   Return value.  
VARIABLES: USER                         TYPE: Input
 VARIABLES DESCRIPTION:   The DUZ of the user.  
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  DATE ACTIVATED: MAR 19, 2009

NUMBER: 5408                            IA #: 5408
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT(
  DATE CREATED: MAR 17, 2009            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CPT/HCPCS Procedure File 81
  ID: ICPT(
GLOBAL REFERENCE: ICPT(D0,0)
FIELD NUMBER: .01                       FIELD NAME: CPT CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ICPT('B'
 GLOBAL DESCRIPTION:   Direct global read of the "B" cross reference.  
  
GLOBAL REFERENCE: ICPT('BA',
 GLOBAL DESCRIPTION:   Direct global read of the "BA" cross reference.  
  
GLOBAL REFERENCE: ICPT('C',
 GLOBAL DESCRIPTION:   Direct global read of the "C" cross reference.  
  
GLOBAL REFERENCE: ICPT('ACT',
 GLOBAL DESCRIPTION:   Direct global read of the "ACT" cross reference.  
  
GLOBAL REFERENCE: ICPT('AN',
 GLOBAL DESCRIPTION:   Direct global read of the "AN" cross reference.  
  
GLOBAL REFERENCE: ICPT('D',
 GLOBAL DESCRIPTION:   Direct global read of the "D" cross reference.  
  
 GENERAL DESCRIPTION:   Applications may conduct Fileman lookups of CPT
 Procedure file #81 provided the 0 (zero) node is not returned as part of the
 output from the lookup.  Applications may also point to the CPT Procedure file
 #81.  This agreement provides very limited access to file 81, primarily the 
 .01 field and selected cross-references. Additional access to file 81 is given
 through the use of APIs in routines ICPTCOD and ICPTAPIU.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CPT
KEYWORDS: CPT-4
KEYWORDS: CPT/HCPCS
KEYWORDS: HCPCS
KEYWORDS: CODE SET
  DATE ACTIVATED: NOV 17, 2014

NUMBER: 5409                            IA #: 5409
  FILE NUMBER: 162.1                    GLOBAL ROOT: FBAA(162.1
  DATE CREATED: MAR 17, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #162.1 Read only      ID: FBAA(162.1
 GENERAL DESCRIPTION:   The FBCS application reads the FEE BASIS PHARMACY
 INVOICE (#162.1) file to display pharmacy payment history.  
     
     ^FBAA(162.1,D0,0) 
       .01  NUMBER                         0;1  Global r 
        3   VENDOR                         0;4  Global r 
        13  FPPS CLAIM ID                  0;13 Global r 
     ^FBAA(162.1,D0,RX,D1,0) 
       .01  PRESCRIPTION NUMBER            0;1  Global r 
        1   DRUG NAME                      0;2  Global r 
        2   DATE PRESCRIPTION FILLED       0;3  Global r 
        3   AMOUNT CLAIMED                 0;4  Global r 
        6   AMOUNT SUSPENDED               0;7  Global r 
        7   SUSPEND CODE                   0;8  Global r 
        8   LINE ITEM STATUS               0;9  Global r 
        1.5 STRENGTH                       0;12 Global r 
        1.6 QUANTITY                       0;13 Global r 
        6.5 AMOUNT PAID                    0;16 Global r 
        13  BATCH NUMBER                   0;17 Global r 
        15  DATE CERTIFIED FOR PAYMENT     0;19 Global r 
        16  PAYMENT TYPE CODE              0;20 Global r 
     ^FBAA(162.1,D0,RX,D1,2) 
        23  VOID PAYMENT                   2;3  Global r 
        26  ASSOCIATED 7078/583            2;6  Global r 
     ^FBAA(162.1,D0,RX,D1,3) 
        36  FPPS LINE ITEM                 3;1  Global r 
     ^FBAA(162.1,D0,RX,D1,FBREJ)                Global r ($D) 
     
     ^FBAA(162.1,"AD")  Used to lookup by patient 
     ^FBAA(162.1,"AE")  Used to check if batch exists, loop on batch 
     ^FBAA(162.1,"AN")  Used to lookup by Vendor 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5410                            IA #: 5410
  FILE NUMBER: 162.2                    GLOBAL ROOT: FBAA(162.2
  DATE CREATED: MAR 17, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #162.2 R/W/D          ID: FBAA(162.2
 GENERAL DESCRIPTION:   The FBCS application accesses the FEE
 NOTIFICATION/REQUEST (#162.2) file.  Entries may be deleted as long as there
 is not a 7078 set up for the request and the user must either be the user who
 entered the request or be the holder of the FBAASUPERVISOR security key.  
     
     ^FBAA(162.2,D0,0)                          Global r ($D) 
       .01  DATE/TIME                      0;1  Fileman r/w,Global r 
        1   VENDOR                         0;2  Fileman r/w,Global r 
        2   PERSON WHO CALLED              0;3  Fileman r/w 
        3   VETERAN                        0;4  Fileman w,Global r 
        4   AUTHORIZED FROM DATE/TIME      0;5  Fileman r/w,Global r 
        5   ADMITTING DIAGNOSIS            0;6  Fileman r/w,Global r 
        6   ATTENDING PHYSICIAN            0;7  Fileman r/w 
        7   USER ENTERING NOTIFICATION     0;8  Fileman r/w,Global r 
        8   LEGAL ENTITLEMENT              0;9  Fileman r/w,Global r 
        9   DATE OF LEGAL DETERMINATION    0;10 Fileman w 
       10   USER ENTERING LEGAL DETERM.    0;11 Fileman w 
       11   MEDICAL ENTITLEMENT            0;12 Fileman r/w,Global r 
       12   DATE OF MEDICAL DETERMINATION  0;13 Fileman w 
       13   USER ENTERING MEDICAL DETERM.  0;14 
       100  REQUEST STATUS                 0;15 Fileman r/w,Global r 
       14   SUSPENSE CODE                  0;16 Fileman r/w 
       16   ASSOCIATED 7078                0;17 Fileman r/w,Global r 
       6.5  ATTEN.PHYSICIAN PHONE NUMBER   0;18 Fileman r/w 
       3.5  DATE/TIME OF ADMISSION         0;19 Fileman r/w,Global r 
     ^FBAA(162.2,D0,1,D1,0)  [Field 15] 
       .01  DESCRIPTION OF SUSPENSION      0;1  Fileman r/w 
     ^FBAA(162.2,D0,2)       [Field 17] 
       17   REFERRING PROVIDER             2;1 
     ^FBAA(162.2,DO,LOG1,D1,0) 
      .01 DATE/TIME EDITED                 0;1 Fileman r 
      1   EDITED BY                        0;2 Fileman r 
      2   COMMENTS                         0;3 Fileman r 
  
     ^FBAA(162.2,"AM") Lookup entry by ASSOCIATED 7078 
     ^FBAA(162.2,"D") to check if record exists for Patient 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: APR 29, 2016

NUMBER: 5411                            IA #: 5411
  FILE NUMBER: 162.6                    GLOBAL ROOT: FBAA(162.6
  DATE CREATED: MAR 17, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #162.6 Read only      ID: FBAA(162.6
 GENERAL DESCRIPTION:   The FBCS application accesses the FEE BASIS DISPOSITION
 CODE (#162.6) file.  
     
     ^FBAA(162.6,D0,0)           Global r ($D) 
        .01    NAME         0;1  Fileman r 
         1     CODE         0;2  Fileman r 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5412                            IA #: 5412
  FILE NUMBER: 163.85                   GLOBAL ROOT: FBAA(163.85
  DATE CREATED: MAR 17, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FBCS File #163.85 Read only     ID: FBAA(163.85
 GENERAL DESCRIPTION:   The FBCS application accesses the FEE BASIS VA TYPE OF
 SERVICE (#163.85) file to get the VA Code when sending payment data to Austin. 
     
     ^FBAA(163.85,D0,0) 
       .02   VA CODE       0;2  Global r 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5413                            IA #: 5413
  FILE NUMBER: 0                        GLOBAL ROOT: DD(81,
  DATE CREATED: MAR 19, 2009            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CPT File 81 Identifier Update
  ORIGINAL NUMBER: 5413                 ID: DD(81,
GLOBAL REFERENCE: DD(81,0,'ID')
 GLOBAL DESCRIPTION:   Direct Kill of the following DD nodes in the
 Post-Install: 
  
   ^DD(81,0,"ID",2)= 
     D EN^DDIOL(("  "_$$IDCPS^ICPTID(+Y)),"","?0") D:$D(SRSITE) ^SROCPT 
  
   ^DD(81,0,"ID",5)= 
     D EN^DDIOL(("   "_$$IDCP^ICPTID(+Y,5)),"","?0") 
  
 Direct Set of the following DD node in the Post-Install: 
  
   ^DD(81,0,"ID",6)= 
     D EN^DDIOL(("  "_$$IDCPF^ICPTID(+Y)),"","?0") D:$D(SRSITE) ^SROCPT 
  
 NOTE:  Field #6 is the SOURCE field and is used to distinguish between
 national codes and VA codes.  The identifiers are being moved from the deleted
 fields to a static field.  
  
 GENERAL DESCRIPTION:   
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CPT-4
SUBSCRIBING PACKAGE: CPT/HCPCS CODES
 SUBSCRIBING DETAILS:   Patch ICPT*6.0*46 deletes SHORT NAME field #2 and
 INACTIVE FLAG #5 from the CPT file #81.  The CPT package needs permission to 
 delete the file identifiers associated with these two fields and then set a
 replacement identifier in the Data Dictionary.  
  
 This agreement is one time only and expires with the installation of
 ICPT*6.0*46.  
  
  DATE ACTIVATED: MAR 19, 2009

NUMBER: 5414                            IA #: 5414
  FILE NUMBER: 0                        GLOBAL ROOT: DD(81.3,
  DATE CREATED: MAR 19, 2009            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: CPT Modifier File 81.3 Identifier Update
  ORIGINAL NUMBER: 5413                 ID: DD(81.3,
GLOBAL REFERENCE: DD(81.3,0,'ID')
 GLOBAL DESCRIPTION:   Direct Kill of the following DD nodes in the
 Post-Install: 
  
   ^DD(81.3,0,"ID",.02)= 
     D EN^DDIOL(("  "_$$IDMDS^ICPTID(+Y)),"","?0") 
  
   ^DD(81.3,0,"ID",5)= 
     D EN^DDIOL(("   "_$$IDMD^ICPTID(+Y,5)),"","?0") 
  
 Direct Set of the following DD node in the Post-Install: 
  
   ^DD(81.3,0,"ID",.04)= 
     D EN^DDIOL(("  "_$$IDMDF^ICPTID(+Y)),"","?0") 
  
 NOTE:  Field #.04 is the SOURCE field and is used to distinguish between
 national codes and VA codes.  The identifiers are being moved from the deleted
 fields to a static field.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CPT-4
SUBSCRIBING PACKAGE: CPT/HCPCS CODES
 SUBSCRIBING DETAILS:   Patch ICPT*6.0*46 deletes the NAME field #.02 and
 INACTIVE FLAG field #5 from the CPT Modifier file #81.3.  The CPT package
 needs permission to delete the file identifiers associated with these two
 fields and then set a replacement identifier in the Data Dictionary.  
  
 This agreement is one time only and expires with the installation of
 ICPT*6.0*46.  
  
  DATE ACTIVATED: MAR 19, 2009

NUMBER: 5415                            IA #: 5415
  FILE NUMBER: 0                        GLOBAL ROOT: DD(80,
  DATE CREATED: MAR 19, 2009            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ICD Diagnosis File 80 Identifier Update
  ORIGINAL NUMBER: 5413                 ID: DD(80,
GLOBAL REFERENCE: DD(80,0,'ID')
 GLOBAL DESCRIPTION:   Direct Kill of the following DD node in the
 Post-Install: 
  
   ^DD(80,0,"ID",3)= 
     D EN^DDIOL((" "_$$IDDXS^ICDID(+Y)),"","?0") 
  
 Direct Set of the following DD node in the Post-Install: 
  
   ^DD(80,0,"ID",8)= 
     D EN^DDIOL((" "_$$IDDXF^ICDID(+Y)),"","?0") 
  
 NOTE:  Field #8 is the ICD EXPANDED field and is used to distinguish between
 national codes and VA codes.  The identifiers are being moved from the deleted
 fields to a static field.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICD-9-CM
SUBSCRIBING PACKAGE: DRG GROUPER
 SUBSCRIBING DETAILS:   Patch ICD*18.0*40 deletes the DIAGNOSIS field #3 from
 the ICD Diagnosis file #80.  The DRG Grouper package needs permission to
 delete the file identifiers associated with this field and then set a
 replacement identifier in the Data Dictionary.  
  
 This agreement is one time only and expires with the installation of
 ICD*18.0*40.  
  
  DATE ACTIVATED: APR 04, 2009

NUMBER: 5416                            IA #: 5416
  FILE NUMBER: 0                        GLOBAL ROOT: DD(80.1,
  DATE CREATED: MAR 19, 2009            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ICD Procedure File 80.1 Identifier Update
  ORIGINAL NUMBER: 5413                 ID: DD(80.1,
GLOBAL REFERENCE: DD(80.1,0,'ID')
 GLOBAL DESCRIPTION:   Direct Kill of the following DD node in the
 Post-Install: 
  
   ^DD(80.1,0,"ID",4)= 
     D EN^DDIOL((" "_$$IDOPS^ICDID(+Y)),"","?0") 
  
 Direct Set of the following DD node in the Post-Install: 
  
   ^DD(80.1,0,"ID",8)= 
     D EN^DDIOL((" "_$$IDOPF^ICDID(+Y)),"","?0") 
  
 NOTE:  Field #8 is the ICD EXPANDED field and is used to distinguish between
 national codes and VA codes.  The identifiers are being moved from the deleted
 fields to a static field.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICD-9-CM
SUBSCRIBING PACKAGE: DRG GROUPER
 SUBSCRIBING DETAILS:   Patch ICD*18.0*40 deletes the OPERATION/PROCEDURE field
 #4 from the ICD Procedure file #80.1.  The DRG Grouper package needs 
 permission to delete the file identifiers associated with this field and then
 set a replacement identifier in the Data Dictionary.  
  
 This agreement is one time only and expires with the installation of
 ICD*18.0*40.  
  
  DATE ACTIVATED: MAR 20, 2009

NUMBER: 5417                            IA #: 5417
  FILE NUMBER: 9002313.57               GLOBAL ROOT: BPSTL(
  DATE CREATED: MAR 19, 2009            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: EPHARM LOG OF TRANSACTION FILE
  ID: BPSTL(
GLOBAL REFERENCE: BPSTL(D0,0)
FIELD NUMBER: 4                         FIELD NAME: RESPONSE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to the corresponding response in the response
 file, 9002313.03.  
FIELD NUMBER: "B" index                 ACCESS: Read w/Fileman
GLOBAL REFERENCE: BPSTL(D0,10)
FIELD NUMBER: 902.24                    FIELD NAME: INSURANCE NAME
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field is the Plan Name for the insurance being
 filed.  
FIELD NUMBER: 902.25                    FIELD NAME: GROUP NAME
  LOCATION: 3;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the Group Name for the Group Insurance file 
FIELD NUMBER: 902.26                    FIELD NAME: INSURANCE CO PHONE
  LOCATION: 3;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the Claims (RX) phone number from the Insurance
 Company file.  
 GENERAL DESCRIPTION:   The Outpatient Pharmacy package required direct Read
 access to the following fields/indices of the BPS LOG OF TRANSACTIONS file 
 (#9002313.57).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
KEYWORDS: NCPDP
KEYWORDS: 9002313.57
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: MAR 21, 2009

NUMBER: 5418                            IA #: 5418
  FILE NUMBER: 78.3                     GLOBAL ROOT: DD(78.3
  DATE CREATED: MAR 20, 2009            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Set file 78.3 'ID','WRITE'
  ID: DD(78.3
 GENERAL DESCRIPTION:   Radiology/Nuclear Medicine intends to add the following
 node to file #78.3's Data Dictionary: 
  
 ^DD(78.3,0,"ID","WRITE")=D EN^DDIOL($$EN1^RABIRAD,"","?33") 
  
 This will be a one-time IA with the installation of patch RA*5.0*97.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  DATE ACTIVATED: MAR 22, 2009

NUMBER: 5419                            IA #: 5419
  FILE NUMBER: 78.3                     GLOBAL ROOT: RA(78.3
  DATE CREATED: MAR 20, 2009            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Insert 'I' in file 78.3 header node
  ID: RA(78.3
 GENERAL DESCRIPTION:   Radiology/Nuclear Medicine intends to insert an "I"
 after the file number in the second piece of File 78.3's header node.  
  
 Here are the "before" and "after" from a development account: 
  
 "before": ^RA(78.3,0)=DIAGNOSTIC CODES^78.3^77^30 
  
 "after":  ^RA(78.3,0)=DIAGNOSTIC CODES^78.3I^77^30 
  
  
 This will be a one-time IA with the installation of patch RA*5.0*97.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  DATE ACTIVATED: MAR 22, 2009

NUMBER: 5420                            IA #: 5420
  DATE CREATED: MAR 20, 2009            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XOBWLIB1
  NAME: XOBWLIB1                        ID: XOBWLIB1
 GENERAL DESCRIPTION:   $$IMPORT^XOBWLIB1 allows a package's pre-init routine
 to automatically import a Cache Object from an XML host file, without the
 package needing to resort to Cache-specific code in its pre-init routine.  
  
 Pharmacy Re-engineering was a very early adopter of HWSC whose early preview
 documentation recommended a style of XML parsing that requires the application
 to provide (and therefore export and install) Cache Objects.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: IMPORT
 COMPONENT DESCRIPTION:   Import Cache-exported XML file into Cache.  
VARIABLES: XOBDIR                       TYPE: Input
 VARIABLES DESCRIPTION:   first function parameter, the directory holding the
 file to import from.  
VARIABLES: XOBFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   second function parameter, holding the name of the
 file to import from.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   If the import was successful, the return value from
 the function is positive. If the import fails, the return value is two
 ^-pieces: 0^reason.  
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  DATE ACTIVATED: JUN 17, 2009

NUMBER: 5421                            IA #: 5421
  DATE CREATED: MAR 20, 2009            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Supported                      TYPE: Routine
  ROUTINE: XOBWLIB                      NAME: XOBWLIB
  ID: XOBWLIB
 GENERAL DESCRIPTION:   Public APIs for the HWSC package.  
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$GETPROXY
 COMPONENT DESCRIPTION:   $$GETPROXY (web service name, web server name) 
  
 Returns a Cache web service client proxy object for the specified web service,
 ready to invoke web service methods on the specified web server. Use this
 method to obtain a web service proxy if you are going to invoke web service
 methods on a single server only.  
VARIABLES: web service name             TYPE: Input
 VARIABLES DESCRIPTION:   first input parameter, name of of entry in WEB
 SERVICE (#18.02) file. 
VARIABLES: web server name              TYPE: Input
 VARIABLES DESCRIPTION:   Name of entry in WEB SERVER (#18.12) file. 
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   Web service client proxy object ready to invoke web
 service methods on the specified web server.  
COMPONENT/ENTRY POINT: $$GENPORT
 COMPONENT DESCRIPTION:   $$GENPORT (.infoarray) 
  
 Use in installation post-init routines to import a WSDL file and run the Cachi
 WSDL import wizard. This call runs the Cache SOAP client wizard to create
 proxy classes for communicating with an external web service, using the web
 service's WSDL file. Creates entry for web service in file #18.02, WEB
 SERVICE.  
VARIABLES: infoarray                    TYPE: Input
 VARIABLES DESCRIPTION:   pass by reference. set up array as follows: 
  
 infoarray("WSDL FILE")  WSDL file location on host operating system 
  
 infoarray("CACHE PACKAGE NAME") Package name to place generated Cache classes
 in.  
  
 infoarray("WEB SERVICE NAME"):  Name to store web service information in file
 #18.02 (WEB SERVICE) - used for lookups, should be namespaced for your
 application.  
  
 infoarray(""AVAILABILITY RESOURCE"")    (optional) resource for HWSC to access
 via an HTTP GET when checking if the web service is available. HWSC appends
 the resource to the IP address and context root of the web service.  
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   Success:        positive value Failure:       
 0^failure description 
COMPONENT/ENTRY POINT: REGSOAP
 COMPONENT DESCRIPTION:   REGSOAP (wsname, wsroot, class, [path], [resource]) 
  
 Use in installation post-init routines to register a web service by creating
 an entry in the WEB SERVICE file (#18.02), without calling the Cache WSDL
 compiler. Typical use cases would be: 
  
 1. Compiled classes are exported for install on the target system rather than
 just a WSDL, because classes were manually modified by development team after
 initial import. 
  
 2. A site calls the WSDL import wizard itself to create a client to a web
 service, and needs to create a Web Service entry to associate with the
 imported classes.  
VARIABLES: wsname                       TYPE: Input
 VARIABLES DESCRIPTION:   first input parameter. Web Service name.  
VARIABLES: wsroot                       TYPE: Input
 VARIABLES DESCRIPTION:   second input parameter. Web Service root (without
 trailing '/').  
VARIABLES: class                        TYPE: Input
 VARIABLES DESCRIPTION:   third input parameter: Cache package + class name of
 the main class created for the web service client proxy, as created by the
 Cache WSDL compiler. 
  
 NOTE: The WSDL compiler uses the value of the name attribute (of the port 
 element, within the service element, in the WSDL file) as the name for the 
 main class it creates.  
VARIABLES: path                         TYPE: Input
 VARIABLES DESCRIPTION:   fourth input parameter (optional). WSDL file location
 on host operating system (WSDL file is copied into Web Service file entry.) 
VARIABLES: resource                     TYPE: Input
 VARIABLES DESCRIPTION:   fifth input parameter (optional): Resource for HWSC
 to access via an HTTP GET when checking if the web service is available. HWSC
 appends the resource to the IP address and context root of the web service.  
COMPONENT/ENTRY POINT: UNREG
 COMPONENT DESCRIPTION:   UNREG (service name) 
  
 Use in installation post-init routines to un-register/delete a web service
 entry in the WEB SERVICE file (#18.02). Can be either a SOAP or REST web
 service. Also removes the service from any web servers it is authorized to.  
VARIABLES: servicename                  TYPE: Input
 VARIABLES DESCRIPTION:   SOAP or REST Web Service Name (entries in File
 #18.02).  
COMPONENT/ENTRY POINT: $$GETREST
 COMPONENT DESCRIPTION:   $$GETREST (service name, server name) 
  
 Return REST service request object. Use to make GET, POST and PUT calls to the
 specified service and server.  
VARIABLES: service name                 TYPE: Input
 VARIABLES DESCRIPTION:   REST Web Service Name (entry File #18.02).  
VARIABLES: server name                  TYPE: Input
 VARIABLES DESCRIPTION:   Web Server Name (entry in File #18.12).  
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   REST service request (xobw.RestRequest) object.  
COMPONENT/ENTRY POINT: $$GET
 COMPONENT DESCRIPTION:   $$GET (RestRequest, resource, [.error], [ForceError]) 
  
 Make HTTP GET call and (by default) force an error trap if problem 
 encountered.  
VARIABLES: RestRequest                  TYPE: Input
 VARIABLES DESCRIPTION:   xobw.RestRequest object.  
VARIABLES: Resource                     TYPE: Input
 VARIABLES DESCRIPTION:   resource string to use with GET method.  
VARIABLES: error                        TYPE: Input
 VARIABLES DESCRIPTION:   (optional) where to store any error encountered (pass
 by ref) - errors returned as an xobw.error object.  
VARIABLES: ForceError                   TYPE: Input
 VARIABLES DESCRIPTION:   (optional) force error trap (1) or not (0). Defaults
 to 1.  
VARIABLES: returnvalue                  TYPE: Output
 VARIABLES DESCRIPTION:   True if succeeded, false if an error occurred. NOTE:
 If ForceError is set to 1, a $ECODE is thrown and the return value QUIT is
 never reached.  
COMPONENT/ENTRY POINT: $$POST
 COMPONENT DESCRIPTION:   $$POST (RestRequest, Resource, [.error],
 [ForceError]) 
  
 Make HTTP POST call and (by default) force an error trap if problem 
 encountered.  
VARIABLES: RestRequest                  TYPE: Input
 VARIABLES DESCRIPTION:   xobw.RestRequest object.  
VARIABLES: Resource                     TYPE: Input
 VARIABLES DESCRIPTION:   resource string to use with POST method.  
VARIABLES: error                        TYPE: Input
 VARIABLES DESCRIPTION:   (optional) where to store any error encountered (pass
 by ref) - errors returned as an xobw.error object.  
VARIABLES: ForceError                   TYPE: Input
 VARIABLES DESCRIPTION:   (optional) force error trap (1) or not (0). Defaults
 to 1.  
VARIABLES: returnvalue                  TYPE: Output
 VARIABLES DESCRIPTION:   True if succeeded, false if an error occurred.  
  
 NOTE: If ForceError is set to 1, a $ECODE is thrown and the return value QUIT
 is never reached.  
COMPONENT/ENTRY POINT: $$HTTPCHK
 COMPONENT DESCRIPTION:   $$HTTPCHK (RestRequest, [.error], [ForceError]) 
  
 Check HTTP status after a GET, POST, or PUT operation has completed; if HTTP
 status code indicated condition other than success, create an HttpError object
 and return false.  
VARIABLES: RestRequest                  TYPE: Input
 VARIABLES DESCRIPTION:   xobw.RestRequest object.  
VARIABLES: error                        TYPE: Input
 VARIABLES DESCRIPTION:   (optional) where to store any error encountered (pass
 by ref) - errors returned as an xobw.error object.  
VARIABLES: ForceError                   TYPE: Input
 VARIABLES DESCRIPTION:   (optional) force error trap (1) or not (0). Defaults
 to 1.  
VARIABLES: returnvalue                  TYPE: Output
 VARIABLES DESCRIPTION:   True if HTTP status judged OK, false if a condition
 other than success occurred. NOTE: If ForceError is set to 1, a $ECODE is
 thrown and the return value QUIT is never reached.  
COMPONENT/ENTRY POINT: $$HTTPOK
 COMPONENT DESCRIPTION:   $$HTTPOK (http status code) 
  
 Check HTTP status after a GET, POST, or PUT operation has completed; if HTTP
 status code indicated condition other than success, return false.  
VARIABLES: http status code             TYPE: Input
 VARIABLES DESCRIPTION:   String containing HTTP status code (e.g., from 
 xobw.RestRequest.HttpResponse.StatusCode).  
VARIABLES: returnvalue                  TYPE: Output
 VARIABLES DESCRIPTION:   True if HTTP status judged OK, false if a condition
 other than success occurred.  
COMPONENT/ENTRY POINT: $$EOFAC
 COMPONENT DESCRIPTION:   $$EOFAC ([SOAP proxy object]) 
  
 For use in error trap handlers during SOAP and REST web services calls, to
 make it easy to process error conditions. Creates an error object based on the
 error condition in the partition, representing a SOAP, Cachi Object, HWSC
 dialog, or basic M error. Includes special parsing for <ZSOAP> web service
 errors.  
  
 Intended for use in an error trap handler, i.e., a known error condition is
 already present in the partition.  
VARIABLES: SOAP proxy object            TYPE: Input
 VARIABLES DESCRIPTION:   (optional) SOAP proxy object (if making a SOAP call). 
 
VARIABLES: returnvalue                  TYPE: Output
 VARIABLES DESCRIPTION:   Cachi Object representing the trapped and parsed
 error (assumes EOFAC^XOBWLIB is being called in an error trap handler) is an
 instance of one of the following classes in the "xobw.error" package: 
  
 BasicError: basic M/ Cache error DialogError: HWSC fault with corresponding
 DIALOG file (#.84) entry ObjectError: Cache Object-level error SoapError: SOAP
 fault returned from web service invocation AbstractError: base class for all
 error types 
COMPONENT/ENTRY POINT: $$EOSTAT
 COMPONENT DESCRIPTION:   $$EOSTAT (status object) 
  
 Create ObjectError from Cache status (%Library.Status) object.  
VARIABLES: status object                TYPE: Input
 VARIABLES DESCRIPTION:   Cache %Library.Status object.  
VARIABLES: returnvalue                  TYPE: Output
 VARIABLES DESCRIPTION:   xobw.error.ObjectError object.  
COMPONENT/ENTRY POINT: $$EOHTTP
 COMPONENT DESCRIPTION:   $$EOHTTP (response object) 
  
 Create HttpError object from Cache %Net.Response object.  
VARIABLES: response object              TYPE: Input
 VARIABLES DESCRIPTION:   %Net.HttpResponse object (e.g., from
 xobw.RestRequest.HttpResponse).  
VARIABLES: returnvalue                  TYPE: Output
 VARIABLES DESCRIPTION:   xobw.error.HttpError object.  
COMPONENT/ENTRY POINT: ERRDISP
 COMPONENT DESCRIPTION:   ERRDISP (error object) 
  
 Does a simple display of an error's information to the screen. "Error Object"
 should be of the type xobw.error.AbstractError or one of its descendants.  
VARIABLES: error object                 TYPE: Input
 VARIABLES DESCRIPTION:   Any HWSC error object in the xobw.error package.  
COMPONENT/ENTRY POINT: ERR2ARR
 COMPONENT DESCRIPTION:   ERR2ARR (error object, .return array) 
  
 Decomposes an error object into an M array carrying the various components of
 the error object. "Error Object" is should be of the type 
 xobw.error.AbstractError or one of its descendants.  
VARIABLES: error object                 TYPE: Input
 VARIABLES DESCRIPTION:   Any HWSC error object in the xobw.error package.  
VARIABLES: return array                 TYPE: Both
 VARIABLES DESCRIPTION:   (pass by ref) Array in which to return the decomposed
 components of the error object.  
  
 Different array nodes are returned depending on the type of xobw.error object
 passed in: 
  
 xobw.error.BasicError: 
         ARRAY("errorType") = type of error (BASIC, DIALOG) 
         ARRAY("code") = error code 
         ARRAY("text") = 
         ARRAY("text",i..n) = 
  
 xobw.error.DialogError: 
         ARRAY("errorType") = type of error (BASIC, DIALOG) 
         ARRAY("code") = error code 
         ARRAY("text") = 
         ARRAY("text",i..n) = 
  
 xobw.error.HttpError: 
         ARRAY("errorType") = type of error (HTTP) 
         ARRAY("code") = error code 
         ARRAY("statusLine") = error dcode 
         ARRAY("text") = 
         ARRAY("text",i..n) = 
  
 xobw.error.ObjectError: 
         ARRAY("errorType") = type of error (OBJECT) 
         ARRAY("code") = error code 
         ARRAY("dcode") = error dcode 
         ARRAY("domain") = error domain 
         ARRAY("text") = 
         ARRAY("text",i..n) = 
  
 xobw.error.SoapError: 
         ARRAY("errorType") = type of error (SOAP) 
         ARRAY("soapFaultType") = SOAP Fault Type 
         ARRAY("faultactor") = SOAP fault actor 
         ARRAY("faultcode") = SOAP fault code 
         ARRAY("faultstring") = SOAP fault string 
         ARRAY("detail") = SOAP fault detail 
         ARRAY("text") = 
         ARRAY("text",i..n) = 
COMPONENT/ENTRY POINT: $$STATCHK
 COMPONENT DESCRIPTION:   $$STATCHK (status object, [.error], [ForceError]) 
  
 Check Cache %Library.Status status object (returned by many Cache Object 
 calls); if not OK create ObjectError object and return false.  
VARIABLES: status object                TYPE: Input
 VARIABLES DESCRIPTION:   Cache %Library.Status object.  
VARIABLES: error                        TYPE: Input
 VARIABLES DESCRIPTION:   (optional) where to store any error encountered (pass
 by ref) - errors returned as an xobw.error object 
VARIABLES: forceerror                   TYPE: Input
 VARIABLES DESCRIPTION:   (optional) force error trap (1) or not (0). Defaults
 to 1.  
VARIABLES: returnvalue                  TYPE: Output
 VARIABLES DESCRIPTION:   True if succeeded, false if an error occurred.  
  
 NOTE: If ForceError is set to 1, a $ECODE is thrown and the return value QUIT
 is never reached.  
COMPONENT/ENTRY POINT: ZTER
 COMPONENT DESCRIPTION:   ZTER (error object) 
  
 Performs two functions: 
  
 1. Decomposes error object into an XOB-namespaced M array carrying the various
 components of the error object.  
  
 2. Calls Kernel error trap to record error.  
  
 It is useful to decompose the error into an M array before calling the Kernel
 error trap, because otherwise the Cachi Object error information is not
 captured in the error trap.  
VARIABLES: error object                 TYPE: Input
 VARIABLES DESCRIPTION:   Any HWSC error object in the xobw.error package
 (should be of the type xobw.error.AbstractError or one of its descendants).  
VARIABLES: XOB-namespaced array         TYPE: Output
 VARIABLES DESCRIPTION:   Array contains different nodes depending on
 xobw.error subclass type of input parameter: 
  
 xobw.error.BasicError: 
         ARRAY("errorType") = type of error (BASIC, DIALOG) 
         ARRAY("code") = error code 
         ARRAY("text") = 
         ARRAY("text",i..n) = 
  
 xobw.error.DialogError: 
         ARRAY("errorType") = type of error (BASIC, DIALOG) 
         ARRAY("code") = error code 
         ARRAY("text") = 
         ARRAY("text",i..n) = 
  
 xobw.error.HttpError: 
         ARRAY("errorType") = type of error (HTTP) 
         ARRAY("code") = error code 
         ARRAY("statusLine") = error dcode 
         ARRAY("text") = 
         ARRAY("text",i..n) = 
  
 xobw.error.ObjectError: 
         ARRAY("errorType") = type of error (OBJECT) 
         ARRAY("code") = error code 
         ARRAY("dcode") = error dcode 
         ARRAY("domain") = error domain 
         ARRAY("text") = 
         ARRAY("text",i..n) = 
  
 xobw.error.SoapError: 
         ARRAY("errorType") = type of error (SOAP) 
         ARRAY("soapFaultType") = SOAP Fault Type 
         ARRAY("faultactor") = SOAP fault actor 
         ARRAY("faultcode") = SOAP fault code 
         ARRAY("faultstring") = SOAP fault string 
         ARRAY("detail") = SOAP fault detail 
         ARRAY("text") = 
         ARRAY("text",i..n) = 
COMPONENT/ENTRY POINT: $$SKEYADD
 COMPONENT DESCRIPTION:   $$SKEYADD (key name, [description], [.error]) 
  
 Add a new server lookup key, or edit an existing one.  
VARIABLES: key name                     TYPE: Input
 VARIABLES DESCRIPTION:   Name of server lookup key.  
VARIABLES: description                  TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Brief description of lookup key.  
VARIABLES: error                        TYPE: Both
 VARIABLES DESCRIPTION:   (optional) location to return error description (pass
 by reference) - returned as array node(s) starting at error(1) 
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   if successful: IEN of new or existing entry (always >
 0) 
  
 if unsuccessful: 0 (Also, error description node(s) are returned in optional
 error parameter.) 
COMPONENT/ENTRY POINT: $$SNAME4KY
 COMPONENT DESCRIPTION:   $$SNAME4KY (key name, .retvalue, [.error]) 
  
 Retrieve the server name associated with a server lookup key.  
VARIABLES: key name                     TYPE: Input
 VARIABLES DESCRIPTION:   Name of server lookup key.  
VARIABLES: retvalue                     TYPE: Both
 VARIABLES DESCRIPTION:   Storage location to return server name if successful
 (pass by reference).  
VARIABLES: error                        TYPE: Both
 VARIABLES DESCRIPTION:   (optional) location to return error information in if
 failure (pass by reference).  
  
 [error format]: error code^error text. Possible errors: 186008^description
 (invalid key) 186009^description (server association missing) 
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   if successful: IEN of new or existing entry (always >
 0) (and the matching server name is returned in the "server name" parameter) 
  
 if unsuccesful: 0 Also, an error is returned in the optional error parameter.  
COMPONENT/ENTRY POINT: ATTACHDR
 COMPONENT DESCRIPTION:   ATTACHDR (proxy object) 
  
 Attach a "VistaInfoHeader" header block to outgoing web service request.  It
 can be processed by the receiving web service as a SOAP header by using a
 handler. This header block contains partition and Kernel environment variables
 as follows: 
  
 duz: the user's DUZ value mio: the partition's $IO value mjob: the partition's
 $JOB value production: "1" if the calling VistA system is a production system,
 "0" if test.  station: station # (currently the Kernel site parameter default 
 institution value) vpid: the user's VPID 
VARIABLES: proxy object                 TYPE: Input
 VARIABLES DESCRIPTION:   SOAP web service client proxy object.  
COMPONENT/ENTRY POINT: REGREST
 COMPONENT DESCRIPTION:   REGREST (service name, context root, [resource]) 
  
 Use in installation post-init routines to register a REST service by creating
 an entry in the WEB SERVICE file (#18.02).  
VARIABLES: service name                 TYPE: Input
 VARIABLES DESCRIPTION:   REST Web Service Name (entry in File #18.02).  
VARIABLES: context root                 TYPE: Input
 VARIABLES DESCRIPTION:   Context Root for the REST service (without leading or
 trailing '/' characters) 
VARIABLES: resource                     TYPE: Input
 VARIABLES DESCRIPTION:   resource for HWSC to access via an HTTP GET when
 checking if the web service is available. HWSC appends the resource to the IP
 address and context root of the web service.  
  DATE ACTIVATED: JUN 16, 2009

NUMBER: 5422                            IA #: 5422
  DATE CREATED: MAR 24, 2009
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Routine
  ROUTINE: PSSWDLL                      NAME: WDDE WARD ASSIGNMENT
  ID: PSSWDLL
 GENERAL DESCRIPTION:   This API checks if a ward is assigned to a specific
 ward drug dispensing equipment (WDDE).  
  
  STATUS: Withdrawn
KEYWORDS: WDDE
KEYWORDS: WARD
KEYWORDS: 59.71
COMPONENT/ENTRY POINT: WRDASGN
VARIABLES: WARD                         TYPE: Input
 VARIABLES DESCRIPTION:   WARD = IFN of WARD LOCATION file #42.  
  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   IFN of #59.71, if found. 0, if not found.  
  
  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: MAR 24, 2009

NUMBER: 5423                            IA #: 5423
  DATE CREATED: MAR 24, 2009            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PSJBCMA5
  NAME: RETURN OTHER PRINT & SPEC INSTRUCTIONS FOR AN ORDER
  ID: PSJBCMA5
 GENERAL DESCRIPTION:   This retrieves the Special Instructions or Other Print
 Information for an order.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: IM
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Returns the Special Instructions for Unit Dose
 Orders.  Returns Other Print Information for IV orders.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The Patient IEN.  
VARIABLES: ON                           TYPE: Input
 VARIABLES DESCRIPTION:   The pharmacy order number.  Contains V for IV or U
 for Unit Dose.  
VARIABLES: PSJTMP                       TYPE: Output
 VARIABLES DESCRIPTION:   The array variable to load the results into.  
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
 SUBSCRIBING DETAILS:   Used for Reports and to send information to the DELPHI
 GUI.  

NUMBER: 5424                            IA #: 5424
  FILE NUMBER: 355.13                   GLOBAL ROOT: IBE(355.13,
  DATE CREATED: MAR 26, 2009            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INSURANCE FILING TIME FRAME
  ID: IBE(355.13,
 GENERAL DESCRIPTION:   The Insurance Capture Buffer application reads file
 #355.13 INSURANCE FILING TIME FRAME in order to display selections to the user
 and determine if time frame Values are needed.  
      
     ^IBE(355.13,D0,0) 
       .01   NAME        0;1         Fileman read 
       .02   VALUE       0;2         Fileman read 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: JUN 11, 2009

NUMBER: 5425                            IA #: 5425
  DATE CREATED: APR 07, 2009
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSDSAPI
  NAME: DBIA 5425                       ID: PSSDSAPI
 GENERAL DESCRIPTION:   This DBIA provides various components that will be used
 for Pharmacy Re-engineering order checking functionality.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$EXMT(PSSVLIEN)
 COMPONENT DESCRIPTION:   This component tells whether or not an entry from the
 DRUG (#50) file should have Dosing checks performed against it.  
VARIABLES: PSSVLIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the Internal Entry Number from the DRUG (#50)
 File. (Required) 
VARIABLES: $$EXMT                       TYPE: Output
 VARIABLES DESCRIPTION:   A '1' indicates the entry is exempt from Dosing
 checks, a '0' indicates the entry is not exempt from Dosing checks.  
COMPONENT/ENTRY POINT: $$SUP(PSSSPLIN)
 COMPONENT DESCRIPTION:   This component tells whether or not an entry in the
 DRUG (#50) File is marked as a Supply item or not. If marked as a Supply,
 there is no need to do Drug Interaction and Duplicate Therapy order checks
 against the item.  
VARIABLES: PSSSPLIN                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the Internal Entry Number from the DRUG (#50)
 File. (Required) 
VARIABLES: $$SUP                        TYPE: Output
 VARIABLES DESCRIPTION:   A '1' indicates that the item is marked as a Supply
 item, and Drug Interaction and Duplicate Therapy order checks do not need to
 be performed against this item. A '0' indicates the item is not marked as a
 Supply item, and that Drug Interaction and Duplicate Therapy order checks
 should be performed against this item.  
COMPONENT/ENTRY POINT: $$MRT(PSSRS1)
 COMPONENT DESCRIPTION:   This component returns the Standard Medication Route
 mapping and it's associated First DataBank Medication Route for an entry in
 the MEDICATION ROUTES (#51.2) File.  
VARIABLES: PSSRS1                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the Internal Entry Number from the MEDICATION
 ROUTES (#51.2) File. (Required) 
VARIABLES: $$MRT                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a two piece result, delimited by the '^'
 character. The first piece is the NAME (#.01) Field from the STANDARD
 MEDICATION ROUTES (#51.23) File entry that the entry in the MEDICATION ROUTES
 (#51.2) File is mapped to. The second piece is the FIRST DATABANK MED ROUTE
 (#1) Field from the STANDARD MEDICATION ROUTES (#51.23) File for that same
 entry. The '^' character is always returned, regardless of whether or not
 there is data in either of the two pieces.  
COMPONENT/ENTRY POINT: $$UNIT(PSSVUTUN)
 COMPONENT DESCRIPTION:   This component returns the FIRST DATABANK DOSE UNIT
 (#1) Field from the DOSE UNITS (#51.24) File for the Drug Unit that is passed
 in.  
VARIABLES: PSSVUTUN                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the text value of the Drug Unit. This usually
 will come from the NAME (#.01) Field of the DRUG UNITS (#50.607) Field.
 (Required) 
VARIABLES: $$UNIT                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the FIRST DATABANK DOSE UNIT (#1) Field from
 the DOSE UNITS (#51.24) File. A null will be returned if no FIRST DATABANK
 DOSE UNIT value can be found.  
COMPONENT/ENTRY POINT: $$DS
 COMPONENT DESCRIPTION:   This component tells the calling application whether
 or not the Dosing Order checks should be invoked.  
VARIABLES: $$DS                         TYPE: Output
 VARIABLES DESCRIPTION:   If '1', Dosing checks are enabled and should be
 invoked. If '0^reason', Dosing checks are not enabled and should not be
 invoked. Piece 2 (reason), using '^' as the delimiter, is a reason that can be
 displayed to the end user.  
COMPONENT/ENTRY POINT: $$IV(PSSADFOI)
 COMPONENT DESCRIPTION:   This component returns a default value to
 Computerized Patient Record System (CPRS) for the Additive Frequency field,
 for continuous IV orders that are entered with additives. All active IV
 Additives that are matched to the Pharmacy Orderable Item are evaluated, and
 for any value other than null to be returned, all entries must be set to the
 same value.  
VARIABLES: PSSADFOI                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the PHARMACY
 ORDERABLE ITEM (#50.7) File.  
VARIABLES: $$IV                         TYPE: Output
 VARIABLES DESCRIPTION:   This will be equal to the internal code value from
 the ADDITIVE FREQUENCY (#18) Field of the IV ADDITIVES (#52.6) File. If a
 value from the list of codes cannot be determined, a null will be returned.  
COMPONENT/ENTRY POINT: $$BSA(PSSBSADF)
 COMPONENT DESCRIPTION:   This component returns a patients height (in
 centimeters), weight (in kilograms), and Body Surface Area. The Body Surface
 Area is calculated using the DuBois formula.  
VARIABLES: PSSBSADF                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the Internal Entry Number from the PATIENT
 (#2) File.  
VARIABLES: $$BSA                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a three-piece variable delimited by the '^'
 character. Piece 1 is the patients height, in centimeters. Piece 2 is the
 patients weight, in kilograms. Piece 3 is the patients Body Surface Area. If
 height is not entered for the patient in VistA, a 0 (zero) will be returned
 for height.  If weight is not entered for the patient in VistA, a 0 (zero)
 will be returned for weight. If weight or height is not entered for the
 patient in VistA, a 0 (zero) will be returned for Body Surface Area.  
COMPONENT/ENTRY POINT: $$UNITD(PSSDBI4)
 COMPONENT DESCRIPTION:   This component returns the FIRST DATABANK DOSE UNIT
 (#1) Field from the DOSE UNITS (#51.24) File for the Drug Unit that is passed
 in. It will only return data from an entry in the file if the DOSE FORM
 INDICATOR (#3) Field is set to NO for that entry.  
VARIABLES: PSSDBI4                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the text value of the Drug Unit. (Required) 
VARIABLES: $$UNITD                      TYPE: Output
 VARIABLES DESCRIPTION:   This is the FIRST DATABANK DOSE UNIT (#1) Field from
 the DOSE UNITS (#51.24) File. A value will only be returned for an entry the
 has the DOSE FORM INDICATOR (#3) Field set to NO. A null will be returned if
 no FIRST DATABANK DOSE UNIT value can be found.  
COMPONENT/ENTRY POINT: $$FRQ(PSSFWSCC,PSSFWFR,PSSFWPK,PSSFWDRC,PSSFWDRG)
 COMPONENT DESCRIPTION:   This component returns Frequency information to be
 used for the Daily Dose checks.  
VARIABLES: PSSFWSCC                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the free text schedule. (required) 
VARIABLES: PSSFWFR                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the numeric frequency in minutes. A 'D' may
 also be passed in to indicate that this is a Day Of Week schedule. (optional) 
VARIABLES: PSSFWPK                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the package use. 'O' for Outpatient, 'I' for
 Inpatient. (required) 
VARIABLES: PSSFWDRC                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the duration. (Optional) The following format
 is required: '120M' will represent 120 minutes.  '12H'  will represent 12
 hours '3D'  will represent 3 days.  '2W'  will represent 2 weeks.  '1L'  will
 represent 1 month.  
  
 If only a numeric is passed in with no alpha, Days will be assumed.  
VARIABLES: PSSFWDRG                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the Internal Entry Number from the DRUG (#50)
 File. (Optional) This data is used to check for the Dosing Check Frequency
 specified for this drug.  
  
 Please note that this Input Variable (PSSFWDRG) will not be valid to pass in
 until the installation of patch PSS*1.0*178.  
VARIABLES: $$FRQ                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the returned frequency, in 2 pieces,
 separated by the '^' character. Piece 1 is the adjusted daily frequency, an
 adjustment may have to be made if a duration is passed in. Piece 2 is the
 Daily Frequency solely based on the schedule. For example, if 'Q2H' is passed 
 in with no duration, the returned value will be '12^12'. If 'Q2H' is passed in
 with a duration of '8H', the returned value would be '4^12', since the '8H'
 duration limits the number of doses in the day. The return can be numeric, or
 it can be in the text format that the Vendor can use. For example, a valid
 return could be "Q2D^Q2D".  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JUN 19, 2014

NUMBER: 5426                            IA #: 5426
  DATE CREATED: APR 07, 2009
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSDSAPD
  NAME: DBIA 5426                       ID: PSSDSAPD
 GENERAL DESCRIPTION:   This DBIA is for the call to perform Dosing checks on
 Medication orders.  
  
 For full Input and Output details, see the 'VistA to MOCHA Interface 
 Document', located under the 'Pharm: Data Management (PDM)' section, under the
 'Clinical' section of the VA Software Document Library (VDL).  
  
 Last Updated: June/2018 
        Patch: PSS*1.0*224 
       Update: Changed one of the output subscripts for the Informational 
               output message for the X(3) output.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DOSE
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 28, 2024

NUMBER: 5427                            IA #: 5427
  DATE CREATED: APR 07, 2009            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOSUCH1
  NAME: PSOSUCH1                        ID: PSOSUCH1
 GENERAL DESCRIPTION:   When an Rx is placed on 3/4 days supply hold for
 ePharamcy, CMOP updates the fill/refill date with the date that the Rx may be
 filled and calls CHANGE^PSOSUCH1 to update file 52.5 and all cross references. 
 
  STATUS: Active
KEYWORDS: PSOSUCH1
COMPONENT/ENTRY POINT: CHANGE
 COMPONENT DESCRIPTION:   Files update and suspense date changes.  
VARIABLES: RXREC                        TYPE: Input
 VARIABLES DESCRIPTION:   RX IEN 
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   REFILL IEN 
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: JUN 23, 2009

NUMBER: 5428                            IA #: 5428
  FILE NUMBER: 61.2                     GLOBAL ROOT: LAB(61.2,
  DATE CREATED: APR 14, 2009            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: ETIOLOGY FIELD FILE             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
GLOBAL REFERENCE: LAB(61.2,'B',
 GLOBAL DESCRIPTION:   B Cross-reference 
 GENERAL DESCRIPTION:   The MRSA INITIATIVE REPORTS would like to request
 Direct Global access to the following fields of the Etiology Field file
 (#61.2) for reporting purposes: 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS

NUMBER: 5429                            IA #: 5429
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100,
  DATE CREATED: APR 14, 2009
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ORDER FILE
  ID: OR(100,
GLOBAL REFERENCE: OR(100,D0,0)
FIELD NUMBER: 21                        FIELD NAME: START DATE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,D0,3)
FIELD NUMBER: 5                         FIELD NAME: STATUS
  LOCATION: 3;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,'AOI',
 GLOBAL DESCRIPTION:   AOI2 Cross-reference 
 GENERAL DESCRIPTION:   The MRSA INITIATIVE REPORTS would like to request
 Direct Global access to the following fields of the Order file (#100) for
 reporting purposes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS
  DATE ACTIVATED: JUN 08, 2009

NUMBER: 5430                            IA #: 5430
  FILE NUMBER: 101.43                   GLOBAL ROOT: ORD(101.43,
  DATE CREATED: APR 14, 2009
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ORDERABLE ITEMS FILE
  ID: ORD(101.43,
GLOBAL REFERENCE: ORD(101.43,'ID',
 GLOBAL DESCRIPTION:   ID Cross-reference 
 GENERAL DESCRIPTION:   The MRSA INITIATIVE REPORTS would like to request
 Direct Global access to the following fields of the Orderable Items file
 (#101.43) for reporting purposes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added subscriber 3/31/14 for use in the MOCHA 2B
 project, PSO*7*412 patch.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Added subscriber 3/31/14 for use in the MOCHA 2B
 project, PSJ*5*293 patch.  
  DATE ACTIVATED: JUN 08, 2009

NUMBER: 5431                            IA #: 5431
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: APR 14, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PATIENT FILE
  ID: DPT(
GLOBAL REFERENCE: DPT('CN',
 GLOBAL DESCRIPTION:   CN Cross-reference 
 GENERAL DESCRIPTION:   The MRSA INITIATIVE REPORTS would like to request
 Direct Global access to the following fields of the Patient file (#2) for
 reporting purposes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS
  DATE ACTIVATED: JUN 08, 2009

NUMBER: 5432                            IA #: 5432
  FILE NUMBER: 62.06                    GLOBAL ROOT: LAB(62.06,
  DATE CREATED: APR 14, 2009            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: ANTIMICROBIAL SUSCEPTIBILITY FILE
  ID: LAB(62.06,
GLOBAL REFERENCE: LAB(62.06,D0,0)
FIELD NUMBER: 1                         FIELD NAME: DRUG NODE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The MRSA INITIATIVE REPORTS would like to request
 Direct Global access to the following fields of the Antimicrobial
 Susceptibility file (#62.06) for reporting purposes.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS

NUMBER: 5433                            IA #: 5433
  FILE NUMBER: 41.9                     GLOBAL ROOT: DG(41.9,
  DATE CREATED: APR 14, 2009            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CENSUS FILE
  ID: DG(41.9,
GLOBAL REFERENCE: DG(41.9,'B',
 GLOBAL DESCRIPTION:   B Cross-reference 
GLOBAL REFERENCE: DG(41.9,D0,'C',D1,0)
FIELD NUMBER: 2                         FIELD NAME: CUM PATIENT DAYS OF CARE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The MRSA INITIATIVE REPORTS would like to request
 Direct Global access to the following fields of the Census file (#41.9) for
 reporting purposes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS
  DATE ACTIVATED: JUN 08, 2009

NUMBER: 5434                            IA #: 5434
  DATE CREATED: APR 29, 2009            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSBPOIV
  NAME: IV Parameter Validation         ID: PSBPOIV
 GENERAL DESCRIPTION:   This utility returns the status of the IV Bags
 associated with an order.  
  STATUS: Active
KEYWORDS: IV BAG
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Returns IV Bag information for order.  
VARIABLES: PSBDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to patient.  
VARIABLES: PSBORD                       TYPE: Input
 VARIABLES DESCRIPTION:   Pharmacy order number.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: MAY 29, 2014

NUMBER: 5435                            IA #: 5435
  DATE CREATED: MAY 01, 2009            CUSTODIAL PACKAGE: LIST MANAGER
  USAGE: Private                        TYPE: Routine
  ROUTINE: VALM1                        NAME: VALM1 (PRT,PRTL)
  ID: VALM1
 GENERAL DESCRIPTION:   Outpatient Pharmacy requests an integration agreement
 to call line tags PRT and PRTL of VALM1.  
  STATUS: Withdrawn
KEYWORDS: PRT,PRTL
COMPONENT/ENTRY POINT: PRT
 COMPONENT DESCRIPTION:   Print ListMan entries on current screen to a device.  
COMPONENT/ENTRY POINT: PRTL
 COMPONENT DESCRIPTION:   Print all ListMan entries to a device.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 5436                            IA #: 5436
  DATE CREATED: MAY 01, 2009            CUSTODIAL PACKAGE: LIST MANAGER
  USAGE: Private                        TYPE: Routine
  ROUTINE: VALM2                        NAME: VALM2 (HELP,MENU)
  ID: VALM2
 GENERAL DESCRIPTION:   Outpatient Pharmacy requests an integration agreement
 to call line tags HELP and MENU of VALM2.  
  STATUS: Withdrawn
KEYWORDS: HELP,MENU
COMPONENT/ENTRY POINT: HELP
 COMPONENT DESCRIPTION:   Provides help on available ListMan actions.  
COMPONENT/ENTRY POINT: MENU
 COMPONENT DESCRIPTION:   Turns display of ListMan actions On or Off.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 5437                            IA #: 5437
  DATE CREATED: MAY 01, 2009            CUSTODIAL PACKAGE: LIST MANAGER
  USAGE: Private                        TYPE: Routine
  ROUTINE: VALM4                        NAME: VALM4 (FIRST,LAST,NEXT,PREV)
  ID: VALM4
 GENERAL DESCRIPTION:   Outpatient Pharmacy requests an integration agreement
 to call line tags FIRST, LAST, NEXT and PREV of VALM4.  
  STATUS: Withdrawn
KEYWORDS: FIRST,LAST,NEXT,PREV
COMPONENT/ENTRY POINT: FIRST
 COMPONENT DESCRIPTION:   Displays the first screen.  
COMPONENT/ENTRY POINT: LAST
 COMPONENT DESCRIPTION:   Displays the last screen.  
COMPONENT/ENTRY POINT: NEXT
 COMPONENT DESCRIPTION:   Displays the next screen.  
COMPONENT/ENTRY POINT: PREV
 COMPONENT DESCRIPTION:   Displays the previous screen.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 5438                            IA #: 5438
  DATE CREATED: MAY 01, 2009            CUSTODIAL PACKAGE: LIST MANAGER
  USAGE: Private                        TYPE: Routine
  ROUTINE: VALM40
  NAME: VALM40 (DOWN,FIND,GOTO,LEFT,RIGHT,UP)
  ID: VALM40
 GENERAL DESCRIPTION:   Outpatient Pharmacy requests an integration agreement
 to call line tags DOWN, FIND, GOTO, LEFT, RIGHT and UP of VALM40.  
  STATUS: Withdrawn
KEYWORDS: DOWN,FIND,GOTO,LEFT,RIGHT,UP
COMPONENT/ENTRY POINT: DOWN
 COMPONENT DESCRIPTION:   Moves down one line.  
COMPONENT/ENTRY POINT: UP
 COMPONENT DESCRIPTION:   Moves up one line.  
COMPONENT/ENTRY POINT: FIND
 COMPONENT DESCRIPTION:   Finds a search text in the list.  
COMPONENT/ENTRY POINT: GOTO
 COMPONENT DESCRIPTION:   Goes to a specified page number.  
COMPONENT/ENTRY POINT: LEFT
 COMPONENT DESCRIPTION:   Moves view to the left.  
COMPONENT/ENTRY POINT: RIGHT
 COMPONENT DESCRIPTION:   Moves view to the right.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 5439                            IA #: 5439
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: MAY 05, 2009            CUSTODIAL PACKAGE: POLICE & SECURITY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DELETE WRITE ACCESS IN FILE 200 FOR PATCH ES*1*46
  ID: VA(200,
 GENERAL DESCRIPTION:   This is a request to delete the delete, laygo, and
 write access that any user may have to files 910-916 for patch ES*1*46.  This
 patch retires many of the Police package options that can write, add, or
 delete to the legacy Police package files.  Read-only options are left active
 for historical data retrieval.  
  
 In file 200, field 32 (ACCESSIBLE FILE), subfields 2 (DELETE ACCESS), 3 (LAYGO
 ACCESS), and 5 (WRITE ACCESS) would be deleted for any user who has either to
 any file in the 910-916 range.  
  
 Here is the code to do so: 
  
          N DA,DIE,DR,I,II S DR="2///@;3///@;5///@" 
          F I=0:0 S I=$O(^VA(200,I)) Q:'I  D 
          .F II=909.9:0 S II=$O(^VA(200,I,"FOF",II)) Q:'II!(II>916)  D 
          ..S DIE="^VA(200,"_I_",""FOF"",",DA(1)=I,DA=II D ^DIE 
         Q 
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUL 31, 2009
SUBSCRIBING PACKAGE: POLICE & SECURITY
SUBSCRIBING PACKAGE: KERNEL
  DATE ACTIVATED: MAY 07, 2009

NUMBER: 5440                            IA #: 5440
  GLOBAL ROOT: XTMP('ORRDI',            DATE CREATED: MAY 06, 2009
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RDI OUTAGE INFO GLOBAL
  ID: XTMP('ORRDI',
GLOBAL REFERENCE: XTMP('ORRDI','OUTAGE INFO'
 GLOBAL DESCRIPTION:   The ^XTMP("ORRDI","OUTAGE INFO") global contains
 information about RDI's up or down status.  The following information is
 contained in the global: 
  
   ^XTMP("ORRDI","OUTAGE INFO","DOWN") 
         If this is set to 1 then RDI is in a down state 
   ^XTMP("ORRDI","OUTAGE INFO","DOWN","LAST PING") 
         This holds the date/time of the last ping to the HDR while RDI is down 
   ^XTMP("ORRDI","OUTAGE INFO","FAILURES") 
         This holds the current count of consecutive failures that have 
 occurred during normal (non down) calls to the HDR.  If a successful call is
 made then this is set back to 0. 
   ^XTMP("ORRDI","OUTAGE INFO","SUCCEEDS") 
                 This holds the current count of consecutive successful calls
 to the HDR during a down state.  If a failure occurs then this is set to 0.  
 GENERAL DESCRIPTION:   This IA is used to allow subscribed packages to view
 all of the ^XTMP("OUTAGE INFO") global nodes.  
  STATUS: Active
KEYWORDS: RDI
KEYWORDS: XTMP
KEYWORDS: OUTAGE INFO
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: MAY 06, 2009

NUMBER: 5441                            IA #: 5441
  DATE CREATED: MAY 06, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBUCUTL5                     NAME: FBCS Access to FBUCUTL5 routine
  ID: FBUCUTL5                          STATUS: Retired
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: DISP9
 COMPONENT DESCRIPTION:   set array for display from files 162.9* 
  
 Usage: D DISP9^FBUCUTL5(FB,IG) 
VARIABLES: FN                           TYPE: Input
 VARIABLES DESCRIPTION:   FN = file number (162.91, 162.92, 162.93, or 162.94) 
VARIABLES: IG                           TYPE: Input
 VARIABLES DESCRIPTION:   IG = ignore screen (optional) 
VARIABLES: TMP(FBAR,$J,ARRAY            TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP("FBAR",$J,"FBAR")=total count;5^ ^TMP("FBAR
 ,$J,number)=ien;.01 field value 
  
    Example for file 162.91 
  
     D DISP9^FBUCUTL5(162.91) 
  
       ^TMP("FBAR",546787498,1)=1;APPROVED 
                             2)=2;DISAPPROVED 
                             3)=3;CANCELLED/WITHDRAWN 
                             4)=4;APPROVED TO STABILIZATION 
                             5)=5;ABANDONED 
                          "FBAR")=5;5^ 
COMPONENT/ENTRY POINT: DISP7
 COMPONENT DESCRIPTION:   set array for display from file 162.7 
  
 Usage: D DISP7^FBUCUTL5(IX,IEN,FBO,FB1725R) 
VARIABLES: IX                           TYPE: Input
 VARIABLES DESCRIPTION:   X-REF to use for sort 
      "APMS    for patient (veteran) 
      "AVMS    for vendor 
      "AOMS    for other party 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Veteran or Vendor or other party IEN (depends on
 specified x-ref) 
VARIABLES: FBO                          TYPE: Input
 VARIABLES DESCRIPTION:   either 0 for all status' for a patient/vendor or a
 status list in string format, delimited by "^" EG: ("10^50^") 
VARIABLES: FB1725R                      TYPE: Input
 VARIABLES DESCRIPTION:   (optional) mill bill screening criteria with value 
    "M" for just mill bill claims 
    "N" for just non-mill bill claims 
    "A" (or null) for all claims 
VARIABLES: TMP(FBAR,$J                  TYPE: Output
 VARIABLES DESCRIPTION:   
   ^TMP("FBAR ,$J, FBAR )= display count in array;piece positions for display
 (only if count) 
  
   ^TMP("FBAR ,$J,number) = ien;name(vet or ven)^name(ven or vet)^fee 
 program^date of claim^status^may be more information and pieces in string 
                          
    Example: 
       D DISP7^FBUCUTL5("AVMS",1427,0) 
  
         Global ^TMP("FBAR" -- NOTE: translation in effect 
  
                            
 ^TMP("FBAR",546787498,1)=713;FEEHOSPITAL^FEEPATIENT,T^CIVIL 
 HOSPIT^12/18/08^DISPOSITIONED^!^TREATMENT FROM: 12/8/08^TREATMENT TO: 12/12/08 
                  
             2)=714;FEEHOSPITAL^FEEPATIENT,T^OUTPATIENT^2/12/09^DISPOSI 
               TIONED^!^TREATMENT FROM: 2/10/09^TREATMENT TO: 2/10/09 
                                                  
             3)=716;FEEHOSPITAL^FEEPATIENT,T^CIVIL HOSPIT^6/10/09^DISPO 
               SITIONED^!^TREATMENT FROM: 6/1/09^TREATMENT TO: 6/6/09 
  
                                             
        "FBAR")=3;5^20^35^52^63^6^33^57^ 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5442                            IA #: 5442
  DATE CREATED: MAY 06, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBNPILK                      NAME: FBCS Access to FBNPILK 
  ID: FBNPILK
 GENERAL DESCRIPTION:   Using $$EN^FBNPILK 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$EN
 COMPONENT DESCRIPTION:   Usage: S X=$$EN^FBNPILK(IEN) 
VARIABLES: IEN                          TYPE: Both
 VARIABLES DESCRIPTION:   
   INPUT: (optional) IEN of the FEE BASIS Vendor File (#161.2) 
  If an ien is not provided, the user will be prompted to select a vendor 
  
   Output     return value 
  NPI (#41.01) field for the specified vendor or 10 spaces if no NPI 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5443                            IA #: 5443
  DATE CREATED: MAY 06, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAACO3                      NAME: FBCS Access to FBAACO3
  ID: FBAACO3
 GENERAL DESCRIPTION:   Access to CALC^FBAACO3 (Calculate Current Invoice
 Total) 
            OUT^FBAACO3 (Update payment line count in 161.7) 
           SETO^FBAACO3 (fiscal year of date) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: CALC
 COMPONENT DESCRIPTION:   Usage: D CALC^FBAACO3 
VARIABLES: A2                           TYPE: Output
 VARIABLES DESCRIPTION:   Amount paid from file 162.03 for one line item 
VARIABLES: FBAAID                       TYPE: Output
 VARIABLES DESCRIPTION:   Date correct invoice received (FM format) 
VARIABLES: FBAAVID                      TYPE: Output
 VARIABLES DESCRIPTION:   Vendor Invoice date (FM format) 
VARIABLES: FBINTOT                      TYPE: Output
 VARIABLES DESCRIPTION:   Sum of amount paid for all line items on invoice 
COMPONENT/ENTRY POINT: OUT
 COMPONENT DESCRIPTION:   The PAYMENT LINE COUNT (#10) field of the FEE BASIS
 BATCH (#161.7) file 
  Will be incremented by 1 if input variable K is greater than 0.  
  
                Usage: D OUT^FBAACO3 
VARIABLES: Z1                           TYPE: Output
 VARIABLES DESCRIPTION:   Payment line count from the batch (file 161.7) 
VARIABLES: FBAABE                       TYPE: Input
 VARIABLES DESCRIPTION:   Batch IEN (file 161.7) selected by user 
VARIABLES: K                            TYPE: Input
 VARIABLES DESCRIPTION:   Amount paid 
VARIABLES: FBINTOT                      TYPE: Both
 VARIABLES DESCRIPTION:   Sum of amount paid.  Will be increased by K.  
COMPONENT/ENTRY POINT: SETO
 COMPONENT DESCRIPTION:   Usage: D SETO^FBAACO3 
VARIABLES: FBAADT                       TYPE: Input
 VARIABLES DESCRIPTION:   FM date of Authorization from date (161.01) 
VARIABLES: FY                           TYPE: Output
 VARIABLES DESCRIPTION:   The year in format nnnn derived for the FM date
 passed in 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5444                            IA #: 5444
  DATE CREATED: MAY 06, 2009            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAASCB0                     NAME: FBCS access to FBAASCB0
  ID: FBAASCB0
 GENERAL DESCRIPTION:   FBCS needs access to $$INTER^FBAASCB0 (get internal
 entry number from file 424) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$INTER
 COMPONENT DESCRIPTION:   Finds an entry in file 424 using the INTERFACE ID
 field 
  Usage: S X=$$INTER^FBAASCBO() 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   ien of patient (file 2 or file 161) 
VARIABLES: FBII78                       TYPE: Input
 VARIABLES DESCRIPTION:   +FBII78 must be the ien of VA FORM 10-7078 (file
 162.4) 
VARIABLES: FBAAON                       TYPE: Input
 VARIABLES DESCRIPTION:   Obligation (e.g. C95003) 
VARIABLES: FBCNH                        TYPE: Input
 VARIABLES DESCRIPTION:   (optional) $D(FBCNH) must be true when nursing home 
VARIABLES: FBMM                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) year and month (format YYMM). Required
 when nursing home 
VARIABLES: value                        TYPE: Output
 VARIABLES DESCRIPTION:   returns a value equal to the ien from file 424 or
 null 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5445                            IA #: 5445
  DATE CREATED: MAY 06, 2009            CUSTODIAL PACKAGE: HEALTH SUMMARY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMTSDESC
  NAME: HEALTH SUMMARY DESCRIPTION      ID: GMTSDESC
 GENERAL DESCRIPTION:   Clinical Reminders is requesting the ability to call
 the EN^GMTSDESC. This API returns a formatted output array containing the
 context of the entry from either file #142, 142.1, and 142.5.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMTSDESC
KEYWORDS: PXRM
KEYWORDS: 142
KEYWORDS: 142.1
KEYWORDS: 142.5
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This is the entry point that will return the output
 in a formatted output.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN is the internal entry number for the health
 summary item.  
  
VARIABLES: FILENUM                      TYPE: Input
 VARIABLES DESCRIPTION:   FILNUM is the file number to search for the entry in.
 The possible values are 142, 142.1, and 142.5.  
  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   The output of this entry point is 
 ^TMP($J,SUB,IEN,n)=text. The calling application should passed in the
 subscript that should be used in the temp global. 
  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: MAY 21, 2009

NUMBER: 5446                            IA #: 5446
  DATE CREATED: MAY 06, 2009
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORORDDSC
  NAME: ORDER DIALOG DESCRIPTION        ID: ORORDDSC
 GENERAL DESCRIPTION:   Clinical Reminders is requesting the ability to call
 EN^ORORDDSC. This API returns a formatted output array containing the context
 of the entry from file #101.41.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OR
KEYWORDS: PXRM
KEYWORDS: 101.41
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This is the entry point that will return the output
 in a formatted output. 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN is the internal entry number from the order
 dialog file, file #101.41.  
  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   The output of this entry point is
 ^TMP($J,SUB,IEN,n)=text global. The calling application should passed in the
 subscript that should be used in the temp global.  
  
  
COMPONENT/ENTRY POINT: BEG
 COMPONENT DESCRIPTION:   This entry point build the header section of the
 Order Dialog entry.  
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   Pass by reference output variable 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Order Dialog file, #101.41 entry IEN 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   The type of entry from order dialog file. This is
 piece 4 of the zero node of the entry.  
VARIABLES: CNT                          TYPE: Both
 VARIABLES DESCRIPTION:   This is the integer value for the output array. This
 variable is pass by zero and must be defined before calling the entry point.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: DEC 20, 2022

NUMBER: 5447                            IA #: 5447
  DATE CREATED: MAY 06, 2009
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUCHECK
  NAME: TIU OBJECTS AND TEMPLATE STATUS AND DESCRIPTION
  ID: TIUCHECK
 GENERAL DESCRIPTION:   Clinical Reminders is requesting the ability to call
 the different APIs in the routine TIUCHECK.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU
KEYWORDS: PXRM
KEYWORDS: 8925.1
KEYWORDS: 8927.1
COMPONENT/ENTRY POINT: GETSTAT
 COMPONENT DESCRIPTION:   This entry point returns the status of an entry in
 file 8925.1 in external format.  
  
VARIABLES: TIUIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   TIUIEN is the internal entry point from file 8925.1.  
  
VARIABLES: $$GETSTAT                    TYPE: Output
 VARIABLES DESCRIPTION:   This return the item status in external format.  
  
COMPONENT/ENTRY POINT: OBJBYIEN
 COMPONENT DESCRIPTION:   This entry point returns the TIU Object description
 in a formatted output.  
  
VARIABLES: TIUOUT                       TYPE: Both
 VARIABLES DESCRIPTION:   This is the output array. The format is
 TIUOUT(TIUIEN,fn)=text.  
  
 TIUIEN is the internal IEN number.  fn is the field number from file 8925.1.
 This API will only return field numbers .01, .07, and 9.  
  
COMPONENT/ENTRY POINT: OBJBYNAM
 COMPONENT DESCRIPTION:   This entry point checks to see if the object exist in
 file 8925.1. If the object exists it will return the object description in a
 formatted array.  
  
VARIABLES: TIUOUT                       TYPE: Both
 VARIABLES DESCRIPTION:   The is the output array. The format is.  
 TIUOUT(TIUIEN,fn)=text.  
                             
 TIUIEN is the internal IEN number.  fn is the field number from file 8925.1.  
  
 This API will only return field numbers .01, .07, and 9.  
  
VARIABLES: TIUNAME                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the external name for the TIU Object.  
  
VARIABLES: $$OBJBYNAM                   TYPE: Output
 VARIABLES DESCRIPTION:   Returns a -1 if the item does not exist in file
 8925.1 or if the item exist and it is not a TIU Object. Returns the internal
 entry number if the item exists and it is a TIU Object.  
  
COMPONENT/ENTRY POINT: OBJSTAT
 COMPONENT DESCRIPTION:   This entry will return if the TIU Object exist in
 file 8925.1 and if the object is active or inactive.  
  
VARIABLES: TIUNAME                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the external name for the TIU Object.  
  
VARIABLES: $$OBJSTAT                    TYPE: Output
 VARIABLES DESCRIPTION:   Returns a -1 if the item does not exist in file
 8925.1 or if the item exists and it is not a TIU Object. Returns a 0 if the
 object exist and the status is inactive. Returns a 1 if the object exist and
 it status is active.  
  
COMPONENT/ENTRY POINT: TEMPSTAT
 COMPONENT DESCRIPTION:   This entry point will return if a TIU Template exist
 in file 8927.1. It will also return the TIU Template status. 
  
VARIABLES: TIUNAME                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the external name for the TIU Template field. 
  
VARIABLES: $$TEMPSTAT                   TYPE: Output
 VARIABLES DESCRIPTION:   Returns a -1 if the item does not exist in file
 8925.1 or if the item exists and it is not a TIU Object. Returns a 0 if the
 object exist and the status is inactive. Returns a 1 if the object exist and
 it status is active.  
  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: MAY 21, 2009

NUMBER: 5448                            IA #: 5448
  DATE CREATED: MAY 11, 2009            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMDLG6
  NAME: PXRM REMINDER DIALOG IS ACTIVE  ID: PXRMDLG6
 GENERAL DESCRIPTION:   TIU is requesting the ability to determine if an entry
 from the REMINDER DIALOG file, file #801.41 is a dialog and if the entry is
 active.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: TIU
COMPONENT/ENTRY POINT: ISACTDLG
 COMPONENT DESCRIPTION:   This entry point determines if an entry from file
 801.41 is an active reminder dialog type.  
  
VARIABLES: DIEN                         TYPE: Input
 VARIABLES DESCRIPTION:   DIEN is the internal entry number for the item from
 file 801.41.  
  
VARIABLES: $$ISACTDLG                   TYPE: Output
 VARIABLES DESCRIPTION:   Returns a 0 is the entry is not a reminder dialog
 type or if the entry is not active. Returns a 1 is the entry is an active
 reminder dialog type.  
  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  DATE ACTIVATED: MAY 21, 2009

NUMBER: 5449                            IA #: 5449
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870,
  DATE CREATED: MAY 12, 2009            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: KERNEL BSE LOOKUP IN HL LOGICAL LINK FILE
  ID: HLCS(870,
 GENERAL DESCRIPTION:   Kernel Broker Security Enhancement (BSE) requests the
 ability to do a lookup within the HL LOGICAL LINK file (#870) using
 FileManager and the command 
    D FIND^DIC(870,,".03;.08","X",L,,"C",,,"XUSBSE") where L=station# 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: KERNEL
  DATE ACTIVATED: APR 16, 2012

NUMBER: 5450                            IA #: 5450
  FILE NUMBER: 2005.2                   GLOBAL ROOT: MAG(2005.2
  DATE CREATED: MAY 12, 2009            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: KERNEL BSE LOOKUP IN NETWORK LOCATION FILE
  ID: MAG(2005.2
 GENERAL DESCRIPTION:   Kernel Broker Security Enhancement (BSE) requests the
 ability to do a lookup within the NETWORK LOCATION file (#2005.2) using
 FileManager and the command 
       D FIND^DIC(2005.2,,"1","MO","VISTASITESERVICE",,,,,"XUSBSE") 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: KERNEL
  DATE ACTIVATED: JUN 16, 2010

NUMBER: 5451                            IA #: 5451
  DATE CREATED: MAY 13, 2009            CUSTODIAL PACKAGE: LIST MANAGER
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: VALM HIDDEN ACTIONS protocol
 GENERAL DESCRIPTION:   Supported actions entries in the VALM HIDDEN ACTIONS
 protocol.  
  STATUS: Active                        DATE ACTIVATED: JUN 11, 2009

NUMBER: 5452                            IA #: 5452
  FILE NUMBER: 604                      GLOBAL ROOT: YSTX(604
  DATE CREATED: MAY 14, 2009            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FILE 604 X-REFERENCE CLEAN UP
  ID: YSTX(604
 GENERAL DESCRIPTION:   This IA is for cleaning up the x-references from a
 faulty deletion of a field in file #604. Patch YS*5.01*100 will be used to run
 the post-init routine YS501100 which does the following: 
             K ^DD(604,"B","PROGRESS NOTE POINTER",.53) 
     and     K ^DD(604,"GL",.5,3,.53) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: 2010
SUBSCRIBING PACKAGE: MENTAL HEALTH
  DATE ACTIVATED: JUN 02, 2009

NUMBER: 5453                            IA #: 5453
  DATE CREATED: MAY 21, 2009
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWPS MEDHIST
  REMOTE PROCEDURE: ORWPS MEDHIST
 GENERAL DESCRIPTION:   Returns the medication administration history for a med
 in a report format. The input required is the DFN and Order IEN.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   CPRS approved this ICR for Dental Record Manager on
 8/11/2009 to document existing references.  However the ICR was not activated
 until 2/9/18.  
  DATE ACTIVATED: FEB 09, 2018

NUMBER: 5454                            IA #: 5454
  DATE CREATED: MAY 21, 2009
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWTIU WINPRINT NOTE
  REMOTE PROCEDURE: ORWTIU WINPRINT NOTE
 GENERAL DESCRIPTION:   Returns a TIU note formatted for output to a printer.
 The input required is the TIU IEN (pointer to #8925).  A second parameter
 contains a Chart Copy flag denoting whether the user wants to print the chart
 copy (=1). If the chart copy flag is 0 or not defined then the rpc outputs the
 work copy.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   CPRS approved this ICR for Dental Record Manager on
 8/11/2009 to document existing references.  However the ICR was not activated
 until 2/9/18.  
  DATE ACTIVATED: FEB 09, 2018

NUMBER: 5455                            IA #: 5455
  FILE NUMBER: 75.1                     GLOBAL ROOT: RAO(75.1,
  DATE CREATED: MAY 26, 2009
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: WOMEN'S HEALTH READS THE RAD/NUC MED ORDERS FILE
  ID: RAO(75.1,
GLOBAL REFERENCE: RAO(75.1,DA,.1)
FIELD NUMBER: 1.1                       FIELD NAME: REASON FOR STUDY
  LOCATION: .1;1                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RAO(75.1,DA,0)
FIELD NUMBER: 2                         FIELD NAME: PROCEDURE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: REQUEST STATUS
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: REQUESTING PHYSICIAN
  LOCATION: 0;14                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This integration agreement allows the subscribing
 package to read fields from the RAD/NUC MED ORDERS file (#75.1).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: WOMEN'S HEALTH RADIOLOGY
KEYWORDS: RADIOLOGY WOMEN'S HEALTH
KEYWORDS: RAD/NUC MED ORDERS FILE
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
 SUBSCRIBING DETAILS:   The Women's Health package needs to determine if a
 patient is about to receive an imaging procedure while pregnant or lactating.  
  DATE ACTIVATED: SEP 12, 2014

NUMBER: 5456                            IA #: 5456
  FILE NUMBER: 15.3                     GLOBAL ROOT: VA(15.3,
  DATE CREATED: JUN 04, 2009            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Merged Records
  ID: VA(15.3,
GLOBAL REFERENCE: VA(15.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: FILE NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: VA(15.3,D0,1,0)
FIELD NUMBER: 1                         FIELD NAME: MERGED ENTRY
  LOCATION: 1;0                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: VA(15.3,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: MERGED ENTRY
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: MERGED TO ENTRY
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
  The Health Data Repository (HDR) relies on the Master Patient 
  Index (MPI), and Person Service Identity Management (PSIM) to 
  provide national and correlated identifiers for patients.  The 
  MPI does not currently have data for patient records involved 
  in past merge events.  
   
  Post-init routine, MPIF51P, will order through the XDR REPOINTED ENTRY 
  (#15.3) file.  For the PATIENT (#2) file entries, data will be extracted 
  for the MERGED ENTRY (#.01) and MERGED TO ENTRY (#.02).  This data 
  will be sent in A24 HL7 messages to the MPI to update PSIM and the 
  Administrative Data Repository (ADR).  
   
  MPIF51P will be distributed in VistA patch MPIF*1.0*51.  It will be 
  run one time as part of the patch installation, and the routine can 
  then be deleted from the site's VistA system.  
   
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA
  DATE ACTIVATED: JUN 17, 2009

NUMBER: 5457                            IA #: 5457
  FILE NUMBER: 115.4                    GLOBAL ROOT: FH(115.4
  DATE CREATED: JUN 09, 2009            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Controlled Subscription        TYPE: File
  NAME: NUTRITION STATUS file           ID: FH(115.4
GLOBAL REFERENCE: FH(115.4,D0
FIELD NUMBER: .01                       FIELD NAME: CATEGORY
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains a nutrition status or risk category.  
FIELD NUMBER: 1                         FIELD NAME: STATUS TEXT (U/L CASE)
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the text name (upper/lower case) of a
 Nutrition Status or risk category. 
 GLOBAL DESCRIPTION:   This file contains the four nutrition statuses of the
 established guidelines that are used in nutrition assessment and screening.  
 GENERAL DESCRIPTION:   The Spinal Cord package would like to request direct
 access to the following fields of the NUTRITION STATUS file (115.4) for
 reporting purposes: .01 CATEGORY & 1 STATUS TEXT (U/L CASE) 
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: NUTRITION STATUS
KEYWORDS: FH(115.4
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION

NUMBER: 5458                            IA #: 5458
  DATE CREATED: JUN 10, 2009            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: xobw.RestRequest
 GENERAL DESCRIPTION:   This class is used to make REST-type requests to an
 external web service.  
  
 The class extends Cache's %Net.HttpRequest class. As such, all methods in the
 parent class are avialable in this one as well.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: Get
 COMPONENT DESCRIPTION:   method Get(resource As %String, test As %Integer = 0)
 returns %Status 
  
 Issue the Http 'get' request, this will cause the web server to return the
 page requested. If this completes correctly the response to this request will
 be in the HttpResponse. The location is the url to request, e.g. '/test.html'.
 This can contain parameters which are assumed to be already URL escaped, e.g.
 '/test.html?PARAM=%25VALUE' sets PARAM to %VALUE. If test is 1 then instead of
 connecting to a remote machine it will just output what it would have send to
 the web server to the current device, if test is 2 then it will output the
 response to the current device after the Get. This can be used to check that
 it will send what you are expecting. This calls Reset automatically after
 reading the response, except in test=1 mode or if reset=0. 
VARIABLES: resource                     TYPE: Input
 VARIABLES DESCRIPTION:   the url to request, e.g. '/test.html'.  
VARIABLES: test                         TYPE: Input
 VARIABLES DESCRIPTION:   If test is 1 then instead of connecting to a remote
 machine it will just output what it would have send to the web server to the
 current device, if test is 2 then it will output the response to the current
 device after the Get. This can be used to check that it will send what you are 
 expecting.  
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   a Cache %Library.status object. Many of the methods
 provided by the Cache Class Library return error status information using the
 %Status data type. 
COMPONENT/ENTRY POINT: Head
 COMPONENT DESCRIPTION:   method Head(resource As %String, test As %Integer =
 0) returns %Status 
  
 Issue the Http 'head' request, this will cause the web server to just return
 the header of the response and none of the body. If this completes correctly
 the response to this request will be in the HttpResponse. The location is the
 url to request, e.g. '/test.html'. This can contain parameters which are
 assumed to be already URL escaped, e.g. '/test.html?PARAM=%25VALUE' sets PARAM
 to %VALUE. If test is 1 then instead of connecting to a remote machine it will
 just output what it would have send to the web server to the current device,
 if test is 2 then it will output the response to the current device after the
 Head. This can be used to check that it will send what you are expecting. This
 calls Reset automatically after reading the response, except in test mode or
 if reset=0. 
VARIABLES: resource                     TYPE: Input
 VARIABLES DESCRIPTION:   he url to request, e.g. '/test.html'.  
VARIABLES: test                         TYPE: Input
 VARIABLES DESCRIPTION:   If test is 1 then instead of connecting to a remote
 machine it will just output what it would have send to the web server to the
 current device, if test is 2 then it will output the response to the current
 device after the Get. This can be used to check that it will send what you are
 expecting.  
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   a Cache %Library.status object. Many of the methods
 provided by the Cache Class Library return error status information using the
 %Status data type. The status represents success or failure.  
COMPONENT/ENTRY POINT: POST
 COMPONENT DESCRIPTION:   method Post(resource As %String, test As %Integer =
 0) returns %Status 
  
 Issue the Http 'post' request, this is used to send data to the web server 
 such as the results of a form, or upload a file. If this completes correctly
 the response to this request will be in the HttpResponse. The location is the
 url to request, e.g. '/test.html'. This can contain parameters which are
 assumed to be already URL escaped, e.g. '/test.html?PARAM=%25VALUE' sets PARAM
 to %VALUE. If test is 1 then instead of connecting to a remote machine it will
 just output what it would have send to the web server to the current device,
 if test is 2 then it will output the response to the current device after the
 Post. This can be used to check that it will send what you are expecting. This
 calls Reset automatically after reading the response, except in test=1 mode or 
 if reset=0. 
VARIABLES: resource                     TYPE: Input
 VARIABLES DESCRIPTION:   the url to request, e.g. '/test.html'.  
VARIABLES: test                         TYPE: Input
 VARIABLES DESCRIPTION:   If test is 1 then instead of connecting to a remote
 machine it will just output what it would have send to the web server to the
 current device, if test is 2 then it will output the response to the current
 device after the Get. This can be used to check that it will send what you are
 expecting.  
VARIABLES: return val                   TYPE: Output
 VARIABLES DESCRIPTION:   a Cache %Library.status object. Many of the methods
 provided by the Cache Class Library return error status information using the
 %Status data type.  The status represents success or failure.  
COMPONENT/ENTRY POINT: Put
 COMPONENT DESCRIPTION:   method Put(resource As %String, test As %Integer = 0)
 returns %Status 
  
 Issue the Http 'put' request, this is used to upload data to the web server,
 it is not used that often. If this completes correctly the response to this
 request will be in the HttpResponse. The location is the url to request, e.g.
 '/test.html'. This can contain parameters which are assumed to be already URL
 escaped, e.g. '/test.html?PARAM=%25VALUE' sets PARAM to %VALUE. If test is 1
 then instead of connecting to a remote machine it will just output what it
 would have send to the web server to the current device, if test is 2 then it
 will output the response to the current device after the Put. This can be used
 to check that it will send what you are expecting. This calls Reset
 automatically after reading the response, except in test=1 mode or if reset=0. 
 
COMPONENT/ENTRY POINT: put
 COMPONENT DESCRIPTION:   method Put(resource As %String, test As %Integer = 0)
 returns %Status 
  
 Issue the Http 'put' request, this is used to upload data to the web server,
 it is not used that often. If this completes correctly the response to this
 request will be in the HttpResponse. The location is the url to request, e.g.
 '/test.html'. This can contain parameters which are assumed to be already URL
 escaped, e.g. '/test.html?PARAM=%25VALUE' sets PARAM to %VALUE. If test is 1
 then instead of connecting to a remote machine it will just output what it
 would have send to the web server to the current device, if test is 2 then it
 will output the response to the current device after the Put. This can be used
 to check that it will send what you are expecting. This calls Reset
 automatically after reading the response, except in test=1 mode or if reset=0. 
 
VARIABLES: resource                     TYPE: Input
 VARIABLES DESCRIPTION:   the url to request, e.g. '/test.html'. 
VARIABLES: test                         TYPE: Input
 VARIABLES DESCRIPTION:   If test is 1 then instead of connecting to a remote
 machine it will just output what it would have send to the web server to the
 current device, if test is 2 then it will output the response to the current
 device after the Get. This can be used to check that it will send what you are
 expecting.  
VARIABLES: return val                   TYPE: Output
 VARIABLES DESCRIPTION:   a Cache %Library.status object. Many of the methods
 provided by the Cache Class Library return error status information using the
 %Status data type.  The status represents success or failure.  
  DATE ACTIVATED: JUN 17, 2009

NUMBER: 5459                            IA #: 5459
  DATE CREATED: JUN 10, 2009            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: xobw.error.BasicError
 GENERAL DESCRIPTION:   class xobw.error.BasicError extends
 xobw.error.AbstractError 
  
 Error class used by the HWSC error processing sub-system when a basic M/Cache
 error occurs. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: code
 COMPONENT DESCRIPTION:   property code As %String (TRUNCATE = 1) 
  
 Code associated with the error.  
COMPONENT/ENTRY POINT: errorType
 COMPONENT DESCRIPTION:   property errorType As %String (TRUNCATE = 1) 
  
 Human readable name for the type of error.  
COMPONENT/ENTRY POINT: text
 COMPONENT DESCRIPTION:   list property text As %String (TRUNCATE = 1) 
  
 Human readable text that provides information about the error.  
COMPONENT/ENTRY POINT: decompose
 COMPONENT DESCRIPTION:   method decompose(ByRef error) returns nothing. 
  
 This method converts the error object properties into a traditional M array. 
VARIABLES: error                        TYPE: Both
 VARIABLES DESCRIPTION:   pass by reference. Structure of ARRAY returned in
 this parameters: 
  
 ARRAY("errorType") = type of error (BASIC, DIALOG) ARRAY("code") = error code 
 ARRAY("text") = ARRAY("text",i..n) = 
COMPONENT/ENTRY POINT: display
 COMPONENT DESCRIPTION:   method display() returns nothing. 
  
 This method provides a simple display of the error using MUMPS WRITE commands. 
  
 Information displayed: Class name Properties: code text 
  DATE ACTIVATED: JUN 17, 2009

NUMBER: 5460                            IA #: 5460
  DATE CREATED: JUN 10, 2009            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: xobw.error.DialogError
 GENERAL DESCRIPTION:   class xobw.error.DialogError extends
 xobw.error.AbstractError 
  
 Class for errors associated with DIALOG file (#.84) entries and used by the
 HWSC error processing sub-system 
  
 The Kernel API EZBLD^DIALOG should be used to produce the 'text' property 
 value and the ien of the DIALOG file entry should be the 'code' property 
 value. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: code
 COMPONENT DESCRIPTION:   property code As %String (TRUNCATE = 1) 
  
 Code associated with the error.  
COMPONENT/ENTRY POINT: errorType
 COMPONENT DESCRIPTION:   property errorType As %String (TRUNCATE = 1) 
  
 Human readable name for the type of error. 
COMPONENT/ENTRY POINT: text
 COMPONENT DESCRIPTION:   list property text As %String (TRUNCATE = 1) 
  
 Human readable text that provides information about the error.  
COMPONENT/ENTRY POINT: decompose
 COMPONENT DESCRIPTION:   method decompose(ByRef error) returns nothing. 
  
 This method converts the error object properties into a traditional M array. 
VARIABLES: error                        TYPE: Both
 VARIABLES DESCRIPTION:   pass by reference. Structure of ARRAY returned in
 this parameters: 
  
 ARRAY("errorType") = type of error (BASIC, DIALOG) ARRAY("code") = error code
 ARRAY("text") = ARRAY("text",i..n) = 
COMPONENT/ENTRY POINT: display
 COMPONENT DESCRIPTION:   method display() returns nothing. 
  
 This method provides a simple display of the error using MUMPS WRITE commands. 
  
 Information displayed: - Class name - Properties: 
   - code 
   - text 
  DATE ACTIVATED: JUN 17, 2009

NUMBER: 5461                            IA #: 5461
  DATE CREATED: JUN 10, 2009            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: xobw.error.HttpError
 GENERAL DESCRIPTION:   class xobw.error.HttpError extends
 xobw.error.AbstractError 
  
 Error class used by the HWSC error processing sub-system when an HTTP error
 occurs.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: code
 COMPONENT DESCRIPTION:   property code As %String (TRUNCATE = 1) 
  
 Code associated with the error.  
COMPONENT/ENTRY POINT: errorType
 COMPONENT DESCRIPTION:   property errorType As %String (TRUNCATE = 1) 
  
 Human readable name for the type of error.  
COMPONENT/ENTRY POINT: text
 COMPONENT DESCRIPTION:   list property text As %String (TRUNCATE = 1) 
  
 Human readable text that provides information about the error.  
COMPONENT/ENTRY POINT: statusLine
 COMPONENT DESCRIPTION:   property statusLine As %String (TRUNCATE = 1) 
  
 The HTTP status line. This is the first line of the response and signals if
 the request was sucessful or if there was a problem. 
COMPONENT/ENTRY POINT: decompose
 COMPONENT DESCRIPTION:   method decompose(ByRef error) returns nothing. 
  
 This method converts the HTTP error object properties into a traditional M
 array. 
VARIABLES: error                        TYPE: Both
 VARIABLES DESCRIPTION:   pass by reference. 
  
 Structure of ARRAY returned in reference parameter: 
  
         ARRAY("errorType") = type of error (HTTP) 
         ARRAY("code") = error code 
         ARRAY("statusLine") = error dcode 
         ARRAY("text") = 
         ARRAY("text",i..n) = 
COMPONENT/ENTRY POINT: display
 COMPONENT DESCRIPTION:   method display() returns nothing. 
  
 This method provides a simple display of the error using MUMPS WRITE commands. 
  
 Information displayed: - Class name - Properties: 
   - code 
   - statusLine 
   - text 
  DATE ACTIVATED: JUN 17, 2009

NUMBER: 5462                            IA #: 5462
  DATE CREATED: JUN 10, 2009            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: xobw.error.ObjectError
 GENERAL DESCRIPTION:   class xobw.error.ObjectError extends
 xobw.error.AbstractError 
  
 Error class used by the HWSC error processing sub-system when a CacheObject
 error occurs. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: code
 COMPONENT DESCRIPTION:   property code As %String (TRUNCATE = 1) 
  
 Code associated with the error.  
COMPONENT/ENTRY POINT: errorType
 COMPONENT DESCRIPTION:   property errorType As %String (TRUNCATE = 1) 
  
 Human readable name for the type of error. 
COMPONENT/ENTRY POINT: text
 COMPONENT DESCRIPTION:   list property text As %String (TRUNCATE = 1) 
  
 Human readable text that provides information about the error.  
COMPONENT/ENTRY POINT: dcode
 COMPONENT DESCRIPTION:   property dcode As %String (TRUNCATE = 1) 
  
 Cache Objects error code.  
COMPONENT/ENTRY POINT: domain
 COMPONENT DESCRIPTION:   property domain As %String (TRUNCATE = 1) 
  
 Cache Objects error domain.  
COMPONENT/ENTRY POINT: decompose
 COMPONENT DESCRIPTION:   method decompose(ByRef error) returns nothing. 
  
 This method converts the error object properties into a traditional M array. 
VARIABLES: error                        TYPE: Both
 VARIABLES DESCRIPTION:   pass by reference, error elements are returned as
 array nodes.  
  
 Structure of ARRAY returned ByRef: 
  
         ARRAY("errorType") = type of error (OBJECT) 
         ARRAY("code") = error code 
         ARRAY("dcode") = error dcode 
         ARRAY("domain") = error domain 
         ARRAY("text") = 
         ARRAY("text",i..n) = 
COMPONENT/ENTRY POINT: display
 COMPONENT DESCRIPTION:   This method provides a simple display of the error
 using MUMPS WRITE commands. 
  
 Information displayed: - Class name - Properties: 
   - code 
   - dcode 
   - domain 
   - text 
  DATE ACTIVATED: JUN 17, 2009

NUMBER: 5463                            IA #: 5463
  DATE CREATED: JUN 10, 2009            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: xobw.error.SoapError
 GENERAL DESCRIPTION:   class xobw.error.SoapError extends
 xobw.error.AbstractError 
  
 Error class used by the HWSC error processing sub-system when a SOAP fault is
 returned. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: code
 COMPONENT DESCRIPTION:   property code As %String (TRUNCATE = 1) 
  
 Code associated with the error.  
COMPONENT/ENTRY POINT: errorType
 COMPONENT DESCRIPTION:   property errorType As %String (TRUNCATE = 1) 
  
 Human readable name for the type of error.  
COMPONENT/ENTRY POINT: text
 COMPONENT DESCRIPTION:   list property text As %String (TRUNCATE = 1) 
  
 Human readable text that provides information about the error.  
COMPONENT/ENTRY POINT: soapFault
 COMPONENT DESCRIPTION:   property soapFault As %SOAP.Fault 
  
 SOAP fault object instance returned by a web method call.  
COMPONENT/ENTRY POINT: soapFaultType
 COMPONENT DESCRIPTION:   property soapFaultType As %String (TRUNCATE = 1) 
 [Calculated;] 
  
 Type of SOAP fault returned by web method call. Possible types: - Server -
 Client - Must Understand - Version Mismatch - Unknown 
COMPONENT/ENTRY POINT: decompose
 COMPONENT DESCRIPTION:   method decompose(ByRef error) returns nothing. 
  
 This method converts the error object properties into a traditional M array.  
VARIABLES: error                        TYPE: Both
 VARIABLES DESCRIPTION:   pass by reference. error information is returned in
 array nodes.  
  
 Structure of ARRAY returned ByRef: 
  
         ARRAY("errorType") = type of error (SOAP) 
         ARRAY("soapFaultType") = SOAP Fault Type 
         ARRAY("faultactor") = SOAP fault actor 
         ARRAY("faultcode") = SOAP fault code 
         ARRAY("faultstring") = SOAP fault string 
         ARRAY("detail") = SOAP fault detail 
         ARRAY("text") = 
         ARRAY("text",i..n) = 
COMPONENT/ENTRY POINT: display
 COMPONENT DESCRIPTION:   method display() returns nothing. 
  
 This method provides a simple display of the error using MUMPS WRITE commands. 
  
 Information displayed: - Class name - Properties: 
   - soapFaultType 
   - soapFault.faultactor 
   - soapFault.faultcode 
   - soapFault.faultstring 
   - soapFault.detail 
COMPONENT/ENTRY POINT: isFaultClient
 COMPONENT DESCRIPTION:   method isFaultClient() returns %String 
  
 Indicates if fault was produced when the client made an incorrect/incomplete
 request. 
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   evaluates to true if a client request fault, false if
 not.  
COMPONENT/ENTRY POINT: isFaultMustUnderstand
 COMPONENT DESCRIPTION:   method isFaultMustUnderstand() returns %String 
  
 Indicates if fault was produced when a header was not handled by server when
 the 'MustUnderstand' attribute was set to 'true'.  
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   evaluates to true if fault was due to a header that
 was not handled by the server with the MustUnderstand attribute set to true.
 Otherwise evaluates to false.  
COMPONENT/ENTRY POINT: isFaultServer
 COMPONENT DESCRIPTION:   method isFaultServer() returns %String 
  
 Indicates if fault was produced when server side error occurred.  
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   evaluates to true if fault was caused on server side,
 otherwise evaluates to false.  
COMPONENT/ENTRY POINT: isFaultVersionMismatch
 COMPONENT DESCRIPTION:   method isFaultVersionMismatch() returns %String 
  
 Indicates if fault was produced when the SOAP versions between client and 
 server were incompatible.  
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   evaluates to true if fault was due to SOAP version
 incompatibility between server and client, otherwise evaluates to false.  
COMPONENT/ENTRY POINT: soapFaultGet
 COMPONENT DESCRIPTION:   method soapFaultGet() returns %SOAP.Fault 
  
 returns the SOAP fault object.  
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   returns the SOAP fault object.  
COMPONENT/ENTRY POINT: soapFaultTypeGet
 COMPONENT DESCRIPTION:   method soapFaultTypeGet() returns %String 
  
 Returns text string describing type of fault.  
VARIABLES: return value                 TYPE: Output
 VARIABLES DESCRIPTION:   Text description of the type of SOAP fault.  
  
 Server, Client, Version Mismatch, Must Understand, Unknown. 
  DATE ACTIVATED: JUN 17, 2009

NUMBER: 5464                            IA #: 5464
  DATE CREATED: JAN 26, 2011
  CUSTODIAL PACKAGE: INCOME VERIFICATION MATCH
  NAME: INCOME VERIFICATION MATCH Option Access
  STATUS: Withdrawn

NUMBER: 5465                            IA #: 5465
  DATE CREATED: JAN 26, 2011            CUSTODIAL PACKAGE: IFCAP
  NAME: IFCAP Option Access             STATUS: Withdrawn

NUMBER: 5466                            IA #: 5466
  DATE CREATED: JUN 19, 2009            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: LRJWLST                      NAME: RETRIEVE COTS ACCESSION NUMBER
  ID: LRJWLST
 GENERAL DESCRIPTION:   With the new integration to the Cerner Lab System,
 there is a need to display the accession number from the Commercial Off the
 Shelf (COTS) product in places outside the lab package.  
  
 This call allows the subscribing package to retrieve the COTS accession 
 nummber.  
  STATUS: Pending
KEYWORDS: LRJWLST
KEYWORDS: COTS
COMPONENT/ENTRY POINT: GETACC
VARIABLES: LRDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal fle number of the 'patient' in the Laboratoy
 package.  
VARIABLES: LRSS                         TYPE: Input
 VARIABLES DESCRIPTION:   Type of lab work - AU for Autopsy, for example.  
VARIABLES: LRIDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Inverted date of lab work.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: HEALTH SUMMARY

NUMBER: 5467                            IA #: 5467
  DATE CREATED: JAN 26, 2011            CUSTODIAL PACKAGE: PAID
  NAME: PAID Option Access              STATUS: Withdrawn

NUMBER: 5468                            IA #: 5468
  DATE CREATED: JUN 23, 2009
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: ONE TIME RELEASE OF GMV CLOSEST READING
 GENERAL DESCRIPTION:   This is a one time ICR to allow OE/RR to release the
 GMV CLOSEST READING RPC in patch OR*3.0*296.  
  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 3.0
KEYWORDS: RPC
KEYWORDS: OR
KEYWORDS: VITAL
KEYWORDS: GMV CLOSEST READING
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JUN 23, 2009

NUMBER: 5469                            IA #: 5469
  DATE CREATED: JUN 26, 2009
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORX8
  NAME: ORDERABLE ITEM LOOKUP           ID: ORX8
 GENERAL DESCRIPTION:   This API is used to lookup an orderable item IEN from
 file 101.43 to match it to a package reference.  For instance Pharmacy can use
 it to lookup one of their Pharmacy Orderable Items to a 101.43 Orderable Item. 
 
  STATUS: Active
KEYWORDS: ORDERABLE ITEM
KEYWORDS: ORDERABLE
COMPONENT/ENTRY POINT: OITM
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN of the package reference 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the file of the package reference 
VARIABLES: OITM                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the return variable of the extrinsic function
 that is the 101.43 IEN.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   MOCHA Enhancements 2 project, patch PSO*7*411-
 Outpatient Pharmacy is using this API to lookup one of their Pharmacy
 Orderable Items to a 101.43 Orderable Item.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Added for the Mocha Enhancements 2 project, patch
 PSJ*5*281 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   Added 1/23/2023, effective with DSSV 1.2 Class 2
 product. Document Only 
  DATE ACTIVATED: SEP 04, 2014

NUMBER: 5470                            IA #: 5470
  DATE CREATED: JUL 16, 2009            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: XUMF MFS EVENTS
 GENERAL DESCRIPTION:   This is the event invoked by the Master File Server
 (MFS) mechanism.  Actions from any application area that are dependent on this
 event may be added to this event upon approval of the DBIC.  
  
 MFS provides an event point that protocols of domain developers may subscribe. 
 The following data is provided by MFS that documents changes to records of the
 files related to the domain updated: 
  
 UPDATE 
  
 ^TMP("XUMF EVENT",$J,IFN,"NEW",IEN) -- this is a new record ^TMP("XUMF
 EVENT",$J,IFN,"AFTER",IEN) -- updated record (internal format) ^TMP("XUMF
 EVENT",$J,IFN,"BEFORE",IEN) -- before image (internal format) 
  
 STATUS 
  
 ^TMP("XUMF EVENT",$J,IFN,"STATUS",IEN) = Term Status Before ^ Effective
 Date/Time Before ^ Term Status After ^ Effective Date/Time After 
  
 REPLACED BY VHA STANDARD TERM (#99.97) 
  
 ^TMP("XUMF EVENT",$J,IFN,"BEFORE",IEN,"REPLACED BY")=internal value ^TMP("XUMF
 EVENT",$J,IFN,"BEFORE",IEN,"INHERITS FROM")=$$RPLCMNT^XTIDTRM ^TMP("XUMF
 EVENT",$J,IFN,"AFTER",IEN,"REPLACED BY")=internal value ^TMP("XUMF
 EVENT",$J,IFN,"AFTER",IEN,"INHERITS FROM")=$$RPLCMNT^XTIDTRM 
  
 ERROR 
  
 ^TMP("XUMF EVENT",$J,"ERROR") = Error message ^TMP("XUMF EVENT",$J,"ERROR",1)
 = IFN ^ IEN 
  
 Note: 
  
 A record updated with same values (overwrite existing values with identical 
 values) does not create a TMP record. 
  
 New Record 
  
 ^TMP("XUMF EVENT",$J,"NEW",IFN,IEN) is set equal to NULL The BEFORE and AFTER
 nodes are not set.  
  
 Update 
  
 The pre-update state of the record is merged into ^TMP("XUMF
 EVENT",$J,"BEFORE",IFN,IEN) 
  
 The post-update state of the record is merged into ^TMP("XUMF
 EVENT",$J,"AFTER",IFN,IEN) 
  
 The NEW node is not set.  
  
 Examples: 
  
 GMRV VITAL TYPE (#120.51) 
  
 NAME: WEIGHT                            ABBREVIATION: WT 
   RATE: YES                             RATE HELP: GMRV-WEIGHT RATE HELP 
   PCE ABBREVIATION: WT 
   RATE INPUT TRANSFORM: I '("UNAVAILABLEPASSREFUSED"...  
  
 Internal 
  
 ^GMRD(120.51,9,0)=WEIGHT^WT^^1^^GMRV-WEIGHT RATE HELP^WT ^GMRD(120.51,9,1)=I
 '("UNAVAILABLEPASSREFUSED"...  
  
 NEW RECORD 
  
 ^TMP("XUMF EVENT",$J,120.51,"NEW",9)=  
  
 UPDATED RECORD 
  
 NAME: WEIGHT                            ABBREVIATION: WT 
   RATE: YES                             RATE HELP: GMRV-WEIGHT RATE HELP 
   PCE ABBREVIATION: WT 
   RATE INPUT TRANSFORM: I '("UNAVAILABLEPASSREFUSED"...  EFFECTIVE DATE/TIME:
 JUN 07, 2007@12:01:23 
   STATUS: ACTIVE 
   VUID: 4500639                         MASTER ENTRY FOR VUID: YES 
  
 ^TMP("XUMF EVENT",$J,120.51,"AFTER ,9,0)=WEIGHT^WT^^1^^GMRV-WEIGHT RATE
 HELP^WT^ ^TMP("XUMF EVENT",$J,120.51,"AFTER ,9,1)=I
 '("UNAVAILABLEPASSREFUSED"...  ^TMP("XUMF EVENT",$J,120.51,"AFTER
 ,9,"TERMSTATUS",0)=^120.5199DA^1^1 ^TMP("XUMF EVENT",$J,120.51,"AFTER E
 ,9,"TERMSTATUS",1,0)=3070607.120123^1 ^TMP("XUMF EVENT",$J,120.51,"AFTER
 ,9,"TERMSTATUS","B",3070607.120123,1)= ^TMP("XUMF EVENT",$J,120.51,"AFTER
 ,9,"VUID")=4500639^1 ^TMP("XUMF EVENT",$J,120.51,"BEFORE
 ,9,0)=WEIGHT^WT^^1^^GMRV-WEIGHT RATE HELP^WT ^TMP("XUMF
 EVENT",$J,120.51,"BEFORE ,9,1)=I '("UNAVAILABLEPASSREFUSED"...  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MFS
KEYWORDS: XUMF
  DATE ACTIVATED: OCT 31, 2011

NUMBER: 5471                            IA #: 5471
  DATE CREATED: JAN 26, 2011            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Private                        NAME: BAR CODE MED ADMIN Option Access
  STATUS: Withdrawn

NUMBER: 5472                            IA #: 5472
  DATE CREATED: JAN 26, 2011            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  NAME: NATIONAL DRUG FILE Option Access
  STATUS: Withdrawn

NUMBER: 5473                            IA #: 5473
  DATE CREATED: JAN 26, 2011
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  NAME: PCE PATIENT CARE ENCOUNTER Option Access
  STATUS: Withdrawn

NUMBER: 5474                            IA #: 5474
  DATE CREATED: JAN 26, 2011            CUSTODIAL PACKAGE: SCHEDULING
  NAME: SCHEDULING Option Access        STATUS: Withdrawn

NUMBER: 5475                            IA #: 5475
  DATE CREATED: JAN 26, 2011            CUSTODIAL PACKAGE: MAILMAN
  NAME: MAILMAN Option Access
 GENERAL DESCRIPTION:   The Consolidated Patient Accounts Center (CPAC) has
 requested the ability to access data across all VA Medical Center VistA System
 by using the telnet feature in CAPRI-Remote. CPAC needs access to the MAILMAN
 XMEDITMG option in order to perform its business office functions.  
  STATUS: Withdrawn                     EXPIRATION DATE: MAR 01, 2011
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE

NUMBER: 5476                            IA #: 5476
  DATE CREATED: JAN 26, 2011
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  NAME: Withdrawn                       STATUS: Withdrawn

NUMBER: 5477                            IA #: 5477
  DATE CREATED: JAN 28, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RAORDU
  NAME: DBIA-5477                       ID: RAORDU
 GENERAL DESCRIPTION:   RAORDU routine is used as a utility to update a request
 status.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RAORDU
 COMPONENT DESCRIPTION:   JVORD routine invokes RAORDU when DoD sends us a
 request to Cancel (Discontinue) a Radiology order.  The entry point we invoke
 is ^RAORDU (no defined label).  
VARIABLES: RAOIFN                       TYPE: Input
VARIABLES: RAOSTS                       TYPE: Input
 VARIABLES DESCRIPTION:   RAOSTS = request status of exam 
VARIABLES: RAOREA                       TYPE: Input
 VARIABLES DESCRIPTION:   RAOREA = set when Canceling and Holding a request.  
VARIABLES: RADFN                        TYPE: Input
VARIABLES: RADTI                        TYPE: Input
VARIABLES: RACNI                        TYPE: Input
VARIABLES: RAREA                        TYPE: Input
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   In accordance with the interface project, it is
 necessary to accept status changes from the external partner. It is necessary
 to call this routine to successfully update the status of Radiological exams
 for which the interface has received a status change.  
  DATE ACTIVATED: APR 27, 2011

NUMBER: 5478                            IA #: 5478
  DATE CREATED: JAN 28, 2011
  CUSTODIAL PACKAGE: AUTOMATED LAB INSTRUMENTS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LA7VHLU6
  NAME: LAB CODE MAPPING                ID: LA7VHLU6
 GENERAL DESCRIPTION:   The routine LA7VHLU6 is used to resolve standardized
 codes such as LOINC, SNOMED CT and other code sets when processing HL7
 messages to internal data structures within the LAB DATA file (#63) for data
 related to Microbiology, Surgical Pathology, Cytology, and Electron
 Microscopsy.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SNOMED CT
KEYWORDS: LOINC
KEYWORDS: CODE MAPPING
KEYWORDS: LAB HL7
COMPONENT/ENTRY POINT: HL2LAH
 COMPONENT DESCRIPTION:   The entry point HL2LAH^LA7VHLU6 takes a LOINC code as
 input and returns a pointer into the Organism subfile (63.3) of the Lab Data
 file (63).  This pointer identifies where the antibiotic sensitivity record is
 to be stored in VistA.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Represent the code identifier from the code system to
 be resolved.  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   Code text related to the code being resolved.  
VARIABLES: NCS                          TYPE: Input
 VARIABLES DESCRIPTION:   Name of code system referenced in the CODE variable.  
VARIABLES: VERSION                      TYPE: Input
 VARIABLES DESCRIPTION:   The version of the code system being resolved.  
VARIABLES: LA76248                      TYPE: Input
 VARIABLES DESCRIPTION:   Related Lab Messaging configuration entry in LA7
 MESSAGE PARAMETER File (#62.48) for non-standard code lookup when code is only
 for a specific interface (optional). Usually used when code/code system is a
 local code and only applicable to a specific interface.  
  
VARIABLES: LA7SS                        TYPE: Input
 VARIABLES DESCRIPTION:   Specific lab subscript to screen standard codes -
 used when same code used in multiple areas (optional). Subscripts supported
 are "CH", "MI", "SP", "CY" and "EM".  
  
VARIABLES: LA7Y                         TYPE: Output
 VARIABLES DESCRIPTION:   CONCEPT^SUBSCRIPT^FILE/SUBFILE^FIELD NUMBER^SCT
 HIERARCHY ^OVERRIDE CONCEPT(optional)^OVERRIDE FILE/SUBFILE (optional) 
  
 Where: 
  CONCEPT = pointer to related concept in LAB MAPPING FILE (#62.47) 
  SUBSCRIPT = subscript of LAB DATA file (#63) "CH", "MI", "SP", "CY", "EM" 
  FILE/SUBFILE = file or subfile number of related entry 
  FIELD NUMBER = field number of related file/subfile to store value.  
  SCT HIERARCHY = SNOMED CT hierarchy of related concept 
  
 <optional return values> 
  OVERRDIE CONCEPT = pointer to related concept in LAB MAPPING FILE (#62.47) 
                     that can be used when the regular related concept is 
                     unable to accommodate the value.  
  OVERRIDE FILE/SUBFILE = file or subfile number of related entry of 
                          override concept 
  
  
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   In its Lab Order Portability feature, the Federal
 Health Care Center provides a capability to receive Lab orders, accessions and
 clinical data from DoD and enter the information into the legacy VistA
 database.  For antibiotic susceptibility information in Lab Micro results, we
 need to determine the mapping of a LOINC code encoded in an HL7 message to the
 local VistA Lab antiobiotic storage field in the LAB DATA file (#63).  The
 entry point HL2LAH will resolve the LOINC code to the internal storage 
 location.  
  
  DATE ACTIVATED: MAR 28, 2011

NUMBER: 5479                            IA #: 5479
  DATE CREATED: JAN 28, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RAREG1
  NAME: REGISTRATION OF NEW RAD EXAMS   ID: RAREG1
 GENERAL DESCRIPTION:   The routine RAREG1 is used in the registration of new
 radiology exams.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: JV RA
COMPONENT/ENTRY POINT: CN
VARIABLES: RATYPE                       TYPE: Input
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   In accordance with the interface project, it is
 necessary to be able to accept registration for new exams into VistA that were
 registered in the partner system. This routine is the primary pathway to do
 this within the Radiology system.  
  DATE ACTIVATED: APR 25, 2011

NUMBER: 5480                            IA #: 5480
  DATE CREATED: JAN 28, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  ROUTINE: LR7OB1                       NAME: HL7 MESSAGE FOR LAB
  ID: LR7OB1
 GENERAL DESCRIPTION:   Request a subscription to Lab routine LR7OB1 that
 constructs HL7 messages for Lab orders.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: LAB
KEYWORDS: FHCC
COMPONENT/ENTRY POINT: NEW
 COMPONENT DESCRIPTION:   Entry point NEW^LR7OB1 constructs a response to a Lab
 order message.  
VARIABLES: LRODT                        TYPE: Input
 VARIABLES DESCRIPTION:   LRODT = Date lab test ordered 
VARIABLES: LRSN                         TYPE: Input
 VARIABLES DESCRIPTION:   LRSN = Specimen number 
VARIABLES: SN                           TYPE: Input
 VARIABLES DESCRIPTION:   "SN" = Hard coded to this value which flags it as a
 new order 
VARIABLES: NAT                          TYPE: Input
 VARIABLES DESCRIPTION:   NAT = Nature of order 
VARIABLES: 6                            TYPE: Input
 VARIABLES DESCRIPTION:   6 = Pointer to Order Status file (100.01); this will
 always be set to ACTIVE.  
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   Invocation of NEW^LR7OB1 to set up a response to a Lab
 order message from DoD.  

NUMBER: 5481                            IA #: 5481
  DATE CREATED: JAN 28, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  NAME: DBIA-5481                       STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: JUN 08, 2011
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5482                            IA #: 5482
  DATE CREATED: JAN 28, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  NAME: DBIA-5482                       STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: JUN 08, 2011
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5483                            IA #: 5483
  DATE CREATED: JAN 28, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  ROUTINE: LRMIEDZ                      NAME: DBIA-5483
  ID: LRMIEDZ                           STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: APR 08, 2011
COMPONENT/ENTRY POINT: END
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5484                            IA #: 5484
  DATE CREATED: JAN 28, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  NAME: DBIA-5484                       STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: JUN 08, 2011
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5485                            IA #: 5485
  DATE CREATED: JAN 28, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LRCENDE1
  NAME: DISCONTINUE LAB ORDER           ID: LRCENDE1
 GENERAL DESCRIPTION:   Routine LRCENDE1 supports discontinuation of a Lab
 order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
COMPONENT/ENTRY POINT: CEN1
 COMPONENT DESCRIPTION:   Entry point CEN1^LRCENDE1 records discontinuation of
 a Lab order in the VistA database.  
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   Lab Mumps code invokes CEN1^LRCENDE1 to discontinue Lab
 Orders as requested by DoD.  
  DATE ACTIVATED: APR 27, 2011

NUMBER: 5486                            IA #: 5486
  DATE CREATED: JAN 28, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  NAME: DBIA-5486                       STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: JUN 08, 2011
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5487                            IA #: 5487
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  NAME: DBIA-5487                       STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: JUN 21, 2011
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5488                            IA #: 5488
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  ROUTINE: LRMIEDZ3                     NAME: DBIA-5488
  ID: LRMIEDZ3                          STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: MAR 10, 2011
COMPONENT/ENTRY POINT: TIME
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5489                            IA #: 5489
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  ROUTINE: LRMIUT                       NAME: DBIA-5489
  ID: LRMIUT                            STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: MAR 10, 2011
COMPONENT/ENTRY POINT: STF
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5490                            IA #: 5490
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  ROUTINE: LRCAPV2                      NAME: DBIA-5490
  ID: LRCAPV2                           STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: MAR 10, 2011
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5491                            IA #: 5491
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPFAPIU
  NAME: PATIENT RECORD FLAG VARIABLE POINTER
  ID: DGPFAPIU
 GENERAL DESCRIPTION:   Builds and returns a variable pointer to the Patient
 Record Flag National or Local files based on the textual flag name.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETFLAG
 COMPONENT DESCRIPTION:   Get the variable pointer value for the flag text
 passed in.  
VARIABLES: DGPRF                        TYPE: Input
 VARIABLES DESCRIPTION:   Name of the Patient Record Flag in the PRF NATIONAL
 FLAG file, #26.15, or in the PRF LOCAL FLAG file, #26.11.  The value passed in
 must match the NAME field, #.01, and is a free text value.  
VARIABLES: DGCAT                        TYPE: Input
 VARIABLES DESCRIPTION:   Optinal File category value.  This value is either
 "N" to lookup the pointer value in the National file, or "L" to lookup the
 pointer value in the PRF Local file.  If null, both the National and Local
 files will be checked for the pointer value.  
VARIABLES: DGRSLT                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns one of the following values: 
    IEN;DGPF(National or Local File number,  i.e.  1;DGPF(26.11, 
  
 Will return "-1;NOT FOUND"  If no flag is found matching the test 
             "-1;NOT ACTIVE" If the flag is not currently active.  
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   ADDED 7/19/2011 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   Added 2/18/21 to support Suicide High Risk Patient
 Enhancements Project Phase 2 (SHRPE 2.0), PRCA*4.5*373 
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   
  
     COMPREHENSIVE CARE COORDINATION 
     ADDED 3/25/2022, effective with DSSV*1.0 
     DSS Class 3 product 
     Document Only - Not approved by Custodial SME 
  DATE ACTIVATED: JUN 07, 2011

NUMBER: 5492                            IA #: 5492
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  ROUTINE: LRVER5                       NAME: DBIA-5492
  ID: LRVER5                            STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: MAR 10, 2011
COMPONENT/ENTRY POINT: V25
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5493                            IA #: 5493
  DATE CREATED: JUL 23, 2009
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORCD
  NAME: INPATIENT MEDICATIONS           ID: ORCD
 GENERAL DESCRIPTION:   Routine ORCD contains CPRS utilities for order dialogs. 
 Inpatient Medications would like permission to use the PTR, GETDLG, GETDLG1, 
 and GETORDER utilities.  
  
  STATUS: Active
KEYWORDS: ORCD
KEYWORDS: ORDER DIALOG
KEYWORDS: PTR
KEYWORDS: GETDLG
KEYWORDS: GETDLG1
KEYWORDS: GETORDER
COMPONENT/ENTRY POINT: $$PTR(NAME)
 COMPONENT DESCRIPTION:   Returns the pointer to the dialog NAME in ^ORD(101.41 
VARIABLES: NAME                         TYPE: Input
 VARIABLES DESCRIPTION:   Name of dialog.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULT=$$PTR^ORCD(NAME) where RESULT is the pointer 
 to the ORDER DIALOG file (#101.41) for the dialog name.  
  
COMPONENT/ENTRY POINT: GETDLG(IFN)
 COMPONENT DESCRIPTION:   Returns an array with the setup of the CPRS dialog.  
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the dialog in ^ORD(101.41 
VARIABLES: ORDIALOG                     TYPE: Output
 VARIABLES DESCRIPTION:   ORDIALOG is an array with the information contained
 in the dialog setup from CPRS.  
  
COMPONENT/ENTRY POINT: GETDLG1(IFN)
 COMPONENT DESCRIPTION:   Returns an array with further information about the
 dialog setup from ^ORD(101.41.  
  
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the dialog in ^ORD(101.41 
VARIABLES: ORDIALOG                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns additional prompt information in the ORDIALOG
 array.  
  
COMPONENT/ENTRY POINT: GETORDER(ORIFN,ARRAY)
 COMPONENT DESCRIPTION:   Returns an array with specific information about an
 order from ^OR(100 
  
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Order number from ^OR(100 
  
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   Name of array for returned values.  If an array name
 is not given, the default array name is "ORDIALOG".  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP calls the GETDLG^ORCD API in order to retrieve the
 set up information for an order dialog from the Order Dialog file (#101.41).
 HMP calls the GETORDER^ORCD API to get specific information about an order
 from the Order file (#100).  
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Added 11/6/19 for access to GETDLG(IFN) component or
 ORCD routine, effective with RA*5*161.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 1/20/23, effective with DSSV*1.2 DSS Class 2
 Product Document only.  
  DATE ACTIVATED: MAY 09, 2013

NUMBER: 5494                            IA #: 5494
  DATE CREATED: AUG 03, 2009            CUSTODIAL PACKAGE: QUASAR
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ACKQUTL4
  NAME: ACKQ A&SP STAFF CONVERSION      ID: ACKQUTL4
 GENERAL DESCRIPTION:   These API's facilitate retrieving A&SP Staff file
 (#509850.3) information that corelates to the NEW PERSON file (#200).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ACKQ
KEYWORDS: QUASAR
KEYWORDS: CONVERSION
KEYWORDS: A&SP Staff
KEYWORDS: 509850.3
KEYWORDS: CONVERT
KEYWORDS: CONVERT1
KEYWORDS: CONVERT2
KEYWORDS: ACKQUTL4
COMPONENT/ENTRY POINT: $$CONVERT(ACKQPRV)
 COMPONENT DESCRIPTION:   Converts IEN from file 509850.3 to Name String from
 file 200.  
VARIABLES: ACKQPRV                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the A&SP Staff file (#509850.3).  
VARIABLES: $$CONVERT                    TYPE: Output
 VARIABLES DESCRIPTION:   The function returns the corresponding IEN from file
 200.  Returns 0 if IEN not found.  
COMPONENT/ENTRY POINT: $$CONVERT1(ACKQPRV)
 COMPONENT DESCRIPTION:   Converts IEN from file 509850.3 to file 200 IEN.  
VARIABLES: ACKQPRV                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the A&SP Staff file (#509850.3).  
VARIABLES: $$CONVERT1                   TYPE: Output
 VARIABLES DESCRIPTION:   The function returns the corresponding IEN from file
 200.  Returns 0 if IEN not found.  
COMPONENT/ENTRY POINT: $$CONVERT2(ACKQPRV)
 COMPONENT DESCRIPTION:   Converts IEN from file 509850.3 to file 200 IEN 
VARIABLES: ACKQPRV                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the A&SP Staff file (#509850.3).  
VARIABLES: $$CONVERT2                   TYPE: Output
 VARIABLES DESCRIPTION:   The function returns the corresponding IEN from file
 200.  Returns 0 if IEN not found.  
  DATE ACTIVATED: AUG 27, 2009

NUMBER: 5495                            IA #: 5495
  DATE CREATED: AUG 06, 2009
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  ROUTINE: TIUSCFI                      NAME: TIUSCFI API CALLS
  ID: TIUSCFI
 GENERAL DESCRIPTION:   This ICR documents the API calls in the routine
 TIUSCFI.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SET(SRDA,TIUDA)
 COMPONENT DESCRIPTION:   This API will create the link between a TIU document
 and a surgical case.  
  
   SET^TIUSCFI(<surgical case#^patient DFN>,<document IEN>) 
   Example: D SET^TIUSCFI("10108^33654",4479) 
VARIABLES: SRDA (required)              TYPE: Input
 VARIABLES DESCRIPTION:   Input value of the surgery case number and patient
 DFN delimited by "^".  
VARIABLES: TIUDA (required)             TYPE: Input
 VARIABLES DESCRIPTION:   Input value of the TIU document internal entry
 number.  
COMPONENT/ENTRY POINT: LIST(TIUY,TIUDFN,TIUDATE)
 COMPONENT DESCRIPTION:   This API returns a list of all the TIU documents for
 a patient within 30 days of a given date. The documents must fall within 30
 days of the given date and have a local title mapped to the desired standard
 titles. The current standard titles that will be included are CONSENT,
 PROCEDURE CONSENT and RESEARCH CONSENT.  
  
  Example: D LIST^TIUSCFI(.RETURN,100832,3090709) 
  
  Also returns the STANDARD TITLE as: 
  <return value>("STDTITL",TIUDA,SEQ)=STANDARD TITLE NAME 
  Example: ^TMP("TIULIST",5455333,4479,1)="CONSENT" 
VARIABLES: TIUY (optional)              TYPE: Output
 VARIABLES DESCRIPTION:   Return array. This may be a global or local value. If
 TIUY is not provided, the default value is ^TMP("TIULIST",$J).  
  
 Node            Piece 
 -----------     ----------------------
 @TIUY@(NUM)     1. IEN of TIU Document 
                 2. Document Title (local) 
                 3. Entry Date 
                 4. Patient Data (Name and L1234) 
                 5. Author Data (IEN, Name, 
                    Signature Name) 
                 6. Location 
                 7. Document Status 
                 8. Admission Date 
                 9. Discharge Date 
                 10. Requesting Package Reference 
                 11. # of Images Attached @TIUY@("INDX",<Document IEN>,NUM)="" 
 @TIUY@("STDTITL",<Document IEN>,NUM)=Standard Title Name 
VARIABLES: TIUDFN (required)            TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the patient.  
VARIABLES: TIUDATE (optional)           TYPE: Input
 VARIABLES DESCRIPTION:   Date in FM format. If TIUDATE is not provided, the
 default value of NOW will be used.  
COMPONENT/ENTRY POINT: GETDOCS(TIUY,SRDA,SEQ)
 COMPONENT DESCRIPTION:   This API returns a list of all the TIU documents
 associated with a given surgical case. Documents with a STATUS of RETRACTED
 are not included.  
  
  Example: D GETDOCS^TIUSCFI(.RETURN,"10108;SRF(") 
  
  Also returns the STANDARD TITLE as: 
  <return value>("STDTITL",TIUDA,SEQ)=STANDARD TITLE NAME 
  Example: ^TMP("TIULIST",5455333,4479,1)="CONSENT" 
VARIABLES: TIUY (optional)              TYPE: Output
 VARIABLES DESCRIPTION:   Return array. This may be a global or local value. If
 TIUY is not provided, the default value is ^TMP("TIULIST",$J).  
  
 Node            Piece 
 -----------     ----------------------
 @TIUY@(NUM)     1. IEN of TIU Document 
                 2. Document Title (local) 
                 3. Entry Date 
                 4. Patient Data (Name and L1234) 
                 5. Author Data (IEN, Name, 
                    Signature Name) 
                 6. Location 
                 7. Document Status 
                 8. Admission Date 
                 9. Discharge Date 
                 10. Requesting Package Reference 
                 11. # of Images Attached @TIUY@("INDX",<Document IEN>,NUM)="" 
 @TIUY@("STDTITL",<Document IEN>,NUM)=Standard Title Name 
VARIABLES: SRDA (required)              TYPE: Input
 VARIABLES DESCRIPTION:   Input value of the surgery case number and global
 root delimited by ";". Example:  "12567;^SRF(" 
VARIABLES: SEQ (optional)               TYPE: Input
 VARIABLES DESCRIPTION:   Input variable that determines the order of the
 return data. Null or 1 (default) value returns documents newest to oldest. -1
 returns documents in reverse sort order, oldest to newest.  
COMPONENT/ENTRY POINT: $$SIGNDT(TIUDA)
 COMPONENT DESCRIPTION:   This extrinsic function returns the SIGNATURE DATE
 for a given TIU document in FM format.  
  
  Example: W $$SIGNDT^TIUSCFI(4486) 
  Returns: 3090626.120144 
VARIABLES: TIUDA (required)             TYPE: Input
 VARIABLES DESCRIPTION:   Input value of the TIU document internal entry
 number.  
COMPONENT/ENTRY POINT: DEL(TIUDA,SRDA)
 COMPONENT DESCRIPTION:   This API will delete the link between a TIU document
 and a surgical case. The optional parameter (SRDA) will also allow automatic
 linking to a new surgical case if desired so that one surgical case may be
 changed to another with one call.  
  
 Example: D DEL^TIUSCFI(4486) 
VARIABLES: TIUDA (required)             TYPE: Input
 VARIABLES DESCRIPTION:   Input value of the TIU document internal entry
 number.  
VARIABLES: SRDA (optional)              TYPE: Input
 VARIABLES DESCRIPTION:   Input value of the surgery case number and the DFN of
 the Patient delimited by "^".  
COMPONENT/ENTRY POINT: IMAGES(TIUY,TIUDFN,TIUSDT,TIUEDT)
 COMPONENT DESCRIPTION:   This API returns a list of all the TIU documents for
 a patient that have a linked IMAGE associated with them. The documents must
 fall within the desired date range and have a local title mapped to the
 desired standard titles. The current standard titles that will be included are
 CONSENT, PROCEDURE CONSENT and RESEARCH CONSENT.  
  
  Also returns the STANDARD TITLE as: 
  <return value>("STDTITL",TIUDA,SEQ)=STANDARD TITLE NAME 
  Example: ^TMP("TIULIST",5455333,4479,1)="CONSENT" 
VARIABLES: TIUY (optional)              TYPE: Output
 VARIABLES DESCRIPTION:   Return array. This may be a global or local value. If
 TIUY is not provided, the default value is ^TMP("TIULIST",$J).  
  
 Node            Piece 
 -----------     ----------------------
 @TIUY@(NUM)     1  IEN of TIU Document 
                 2  Document Title (local) 
                 3. Entry Date 
                 4. Patient Data (Name and L1234) 
                 5. Author Data (IEN, Name, 
                    Signature Name) 
                 6. Location 
                 7. Document Status 
                 8. Admission Date 
                 9. Discharge Date 
                10. Requesting Package Reference 
                11. # of Images Attached @TIUY@("INDX",<Document IEN>,NUM)="" 
 @TIUY@("STDTITL",<Document IEN>,NUM)=Standard Title Name 
VARIABLES: TIUDFN (required)            TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the patient.  
VARIABLES: TIUSDT (required)            TYPE: Input
 VARIABLES DESCRIPTION:   Starting date of the desired date range in FM format. 
 
VARIABLES: TIUEDT (required)            TYPE: Input
 VARIABLES DESCRIPTION:   Ending date of the desired date range in FM format.  
SUBSCRIBING PACKAGE: SURGERY

NUMBER: 5496                            IA #: 5496
  DATE CREATED: SEP 03, 2009
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSFDBRT
  NAME: PSSFDBRT                        ID: PSSFDBRT
 GENERAL DESCRIPTION:   This DBIA is provided by PDM (Pharmacy Data Management)
 as an API to return a list of possible Medication Routes from First DataBank
 (FDB) for a dispense drug.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GROUTE
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSSIEN = IEN from the DRUG file (#50) [required] 
VARIABLES: LIST                         TYPE: Both
 VARIABLES DESCRIPTION:   Input: LIST = the array passed by reference defined
 by the calling party [required] 
  
 Output: LIST(0) ="1" if the call was successful, though this does not
 necessarily mean that Medication Routes have been returned.  LIST(0) =
 "-1^reason" if there was an error of some kind, with "reason" being the text
 describing the error.  
  
 LIST(X) = "" will be returned if Medication Routes are returned, where X is
 the First DataBank Medication Route name.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: JUN 20, 2014

NUMBER: 5497                            IA #: 5497
  DATE CREATED: SEP 04, 2009
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSDSAPK
  NAME: DBIA 5497                       ID: PSSDSAPK
 GENERAL DESCRIPTION:   This DBIA provides various components that will be used
 for Pharmacy Re-engineering order checking functionality.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$PRE(PSSLGTOI,PSSDIAG)
 COMPONENT DESCRIPTION:   This component uses the selected Pharmacy Orderable
 Item from Computerized Patient Record System (CPRS) and the dialogue being
 used (Unit Dose, IV, Outpatient or Non-VA Med), and determines whether order
 checks should be done on the order. This call should not be used if the
 Orderable Item is marked as an Additive when entering the order from the IV
 Fluids dialogue.  
VARIABLES: PSSLGTOI                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the Pharmacy
 Orderable Item (#50.7) File.  
VARIABLES: $$PRE                        TYPE: Output
 VARIABLES DESCRIPTION:   This value is a '1' or a '0'. A '1' indicates order
 checks should be done on the order that is being entered with this Orderable
 Item.  
VARIABLES: PSSDIAG                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the CPRS order dailogue (U:Inpatient;I:IV 
 Fluids;O:Outpatient;N:Non VA Meds).  
COMPONENT/ENTRY POINT: $$CONV(PSSCVTVL)
 COMPONENT DESCRIPTION:   This component converts a number that represents
 'hours' into a valid Schedule or Frequency.  
VARIABLES: PSSCVTVL                     TYPE: Input
 VARIABLES DESCRIPTION:   This is numeric value representing the number of
 hours.  
VARIABLES: $$CONV                       TYPE: Output
 VARIABLES DESCRIPTION:   This output represents a Schedule in the form of Q#H
 for an input of 1 or greater, using standard rounding logic to a whole number,
 or it represents Frequency per day for an input of less than 1, also using
 standard rounding logic to a whole number. For example, if 10.5 is passed in,
 the result would be Q11H. If .5 is passed in, the result would be 48.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   ORDER ENTRY/RESULTS REPORTING has access to call the
 $$PRE component of this DBIA.  
  
 10/30/23: effective with patch OR*3*535, identified call to $$PRE^PSSDSAPK
 from routine ORKPS implemented at some time in the past, to verify ICR use is
 properly documented.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Inpatient Medications has access to call the $$CONV
 component of this DBIA.  
  DATE ACTIVATED: OCT 30, 2023

NUMBER: 5498                            IA #: 5498
  DATE CREATED: SEP 18, 2009
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORAREN
  NAME: ORAREN AUTORENEWAL              ID: ORAREN
 GENERAL DESCRIPTION:   The purpose of this Application Programming Interface
 (API) is to provide a mechanism for requesting a renewal of an Outpatient
 prescription order from the Computerized Patient Record System (CPRS).  
  STATUS: Active
KEYWORDS: ORAREN
KEYWORDS: AUTORENEWAL
KEYWORDS: PHARMACY
COMPONENT/ENTRY POINT: RENEW(RESULT,DFN,RX,PROVP)
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's DFN (internal entry number) 
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Outpatient prescription number (internal format) 
VARIABLES: PROVP                        TYPE: Input
 VARIABLES DESCRIPTION:   Flag indicating the requirements for the ordering
 physician: A - any physician P - Primary Care provider only 
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Flag indicating the success/failure of the renewal. 0
 indicates the renew failed, 1 indicates it was successful.  
SUBSCRIBING PACKAGE: VENDOR - AUDIOFAX, INC.
 SUBSCRIBING DETAILS:   The AudioCare package requests the ability to renew an
 Outpatient prescription order where the requests originates from the AudioCare 
 system.  10/5/21-The Audiofax subscriber will be replaced by the Outpatient 
 Pharmacy subscriber.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   10/4/21-Effective with the Pharmacy Safety Updates
 (PSU) project, class 1 software PSO*7*653, which takes over processing the
 AudioCARE refill requests and the overall processing should be transparent to
 the end-user.  
  DATE ACTIVATED: APR 27, 2023

NUMBER: 5499                            IA #: 5499
  DATE CREATED: SEP 25, 2009
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU GET PERSONAL PREFERENCES
  REMOTE PROCEDURE: TIU GET PERSONAL PREFERENCES
 GENERAL DESCRIPTION:   Add support for Mental Health 
  
       1796     NAME: TIU GET PERSONAL PREFERENCES 
  CUSTODIAL PACKAGE:  TEXT INTEGRATION UTILITIES                 Salt Lake City 
 SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE                    
                      ORDER ENTRY/RESULTS REPORTING              
               USAGE: Controlled Subscri  ENTERED: APR 30,2003 
              STATUS: Active              EXPIRES: 
            DURATION:                     VERSION: 
         DESCRIPTION:                        TYPE: Remote Procedure 
    Returns Users personal preferences for TIU in the following format: 
     
    TIUY = USER [1P] ^ DEFAULT LOCATION [2P] ^ REVIEW SCREEN SORT FIELD [3S] ^ 
        ==>REVIEW SCREEN SORT ORDER [4S] ^ DISPLAY MENUS [5S] ^ PATIENT 
        ==>SELECTION PREFERENCE [6S] ^ ASK 'Save changes?' AFTER EDIT [7S] 
 ^
        ==>ASK SUBJECT FOR PROGRESS NOTES [8S] ^ 
  
  TAG^ROUTINE: GETPREF^TIUSRVR 
            KEYWORDS: 
  STATUS: Active
KEYWORDS: GET PREF
SUBSCRIBING PACKAGE: MENTAL HEALTH
  DATE ACTIVATED: SEP 25, 2009

NUMBER: 5500                            IA #: 5500
  DATE CREATED: SEP 25, 2009
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU REQUIRES COSIGNATURE
  REMOTE PROCEDURE: TIU REQUIRES COSIGNATURE
 GENERAL DESCRIPTION:   Add Mental Health as a subscriber to REQCOS^TIUSRVA.  
  STATUS: Active
KEYWORDS: TIU
KEYWORDS: CO-SIGN
SUBSCRIBING PACKAGE: MENTAL HEALTH
  DATE ACTIVATED: DEC 14, 2009

NUMBER: 5501                            IA #: 5501
  DATE CREATED: SEP 28, 2009            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS SET VISITOR
  REMOTE PROCEDURE: XUS SET VISITOR
 GENERAL DESCRIPTION:   VistA Imaging is requesting permission to use a Kernel
 API, SETVISIT^XUSBSE1, to obtain the BSE token.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SETVISIT
KEYWORDS: BSE
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   Added 9/27/19 
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 6/22/23. CDSP is developing a CPRS COM extension
 to capture user generated events to trigger clinical decision support
 applications. CDSP is utilizing solutions based on FHIR, SMART on FHIR and CDS
 Hooks standards, and needs to obtain a BSE Token for authenticated active user 
 to secure calls from COM object to backend API.  
  
 Temporary approval provided with the following contingencies: 1) Once an
 appropriate solution is available in production, the CDSP application agrees
 to transition to the appropriate solution within four months. Once CDSP has
 transitioned, this approval will be removed.  2) When using BSE, CDSP agrees
 to not create or provision VistA accounts.  3) When using BSE, CDSP agrees to
 not create duplicate VistA accounts.  4) When using BSE, CDSP agrees to only
 access VistA systems where a known user has a known VistA account.  5) This
 temporary approval does not authorize CDSP to bypass any VA directive,
 handbook or Identity Access Management policies.  
  
 If CDSP fails to comply with the contingencies then VA security officers will
 be notified and CDSP's authority to operate could be suspended.  
  DATE ACTIVATED: JUN 16, 2010

NUMBER: 5502                            IA #: 5502
  FILE NUMBER: 8994.5                   GLOBAL ROOT: XWB(8994.5,
  DATE CREATED: SEP 28, 2009            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IMAGING BSE
  ID: XWB(8994.5,
GLOBAL REFERENCE: XWB(8994.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the NAME of the REMOTE GUI APPLICATION 
FIELD NUMBER: .03                       FIELD NAME: APPLICATIONCODE
  LOCATION: 0;3                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the hashed value for a security phrase for the
 application 
GLOBAL REFERENCE: XWB(8994.5,D0,1,
FIELD NUMBER: .01                       FIELD NAME: CALLBACKTYPE
  LOCATION: 1;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   
  This field indicates the mechanism(s) by which the server should contact the 
 authenticating server to obtain information necessary to sign the current user 
 on to the current server.  
FIELD NUMBER: .02                       FIELD NAME: CALLBACKPORT
  LOCATION: 1;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the port to be used for the callback to the
 authenticating server 
 GENERAL DESCRIPTION:   Imaging is requesting permission to add four entries
 into file 8994.5 to be used by our Imaging applications. The entries will
 contain the name of the application, the application code (encrypted,) method
 of authentication, and authentication server IP, port, and entry point.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 8994.5
KEYWORDS: BSE
SUBSCRIBING PACKAGE: IMAGING
  DATE ACTIVATED: JUN 16, 2010

NUMBER: 5503                            IA #: 5503
  DATE CREATED: OCT 20, 2009            CUSTODIAL PACKAGE: EMERGENCY DEPARTMENT
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: EDPFMON
  NAME: EDPFMON                         ID: EDPFMON
 GENERAL DESCRIPTION:   This agreement documents usage of various entry points
 in routine EDPFMON.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: VER
 COMPONENT DESCRIPTION:   This tag informs EDIS that an order has been
 verified.  
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to Orders file #100 
COMPONENT/ENTRY POINT: COMP
 COMPONENT DESCRIPTION:   This tag informs EDIS that an order has been
 completed.  
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to Orders file #100 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 20, 2009

NUMBER: 5504                            IA #: 5504
  DATE CREATED: OCT 27, 2009
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Routine
  ROUTINE: PSSDSAPA                     NAME: DBIA 5504
  ID: PSSDSAPA
 GENERAL DESCRIPTION:   This DBIA provides a component that will be used for
 Pharmacy Re-engineering order checking functionality.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$IV(PSSADFOI)
 COMPONENT DESCRIPTION:   This component returns a default value to
 Computerized Patient Record System (CPRS) for the Additive Frequency field,
 for continuous IV orders that are entered with additives. All active IV
 Additives that are matched to the Pharmacy Orderable Item are evaluated, and
 for any value other than null to be returned, all entries must be set to the
 same value.  
VARIABLES: PSSADFOI                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the PHARMACY
 ORDERABLE ITEM (#50.7) File.  
VARIABLES: $$IV                         TYPE: Output
 VARIABLES DESCRIPTION:   This will be equal to the internal code value from
 the ADDITIVE FREQUENCY (#18) Field of the IV ADDITIVES (#52.6) File. If a
 value from the list of codes cannot be determined, a null will be returned.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 5505                            IA #: 5505
  DATE CREATED: NOV 02, 2009            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: OUTPATIENT PHARMACY VDEF EVENTS
 GENERAL DESCRIPTION:   Outpatient Pharmacy provides access to the subscribing
 package to use the following protocols: 
  
          PSO VDEF RDE O11 OP PHARM PRES VS 
          PSO VDEF RDS O13 OP PHARM PPAR VS 
          PSO VDEF RDS O13 OP PHARM PREF VS 
  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HAIS
KEYWORDS: PSO RDE-O11
KEYWORDS: PSO RDS-013
SUBSCRIBING PACKAGE: HEALTHCARE ASSOC INFECTION
 SUBSCRIBING DETAILS:   
  The following HAIS protocols are subscribers: 
  
    HAIS RDE SUBSCRIBER 
    HAIS RDS SUBSCRIBER 
  
  
  DATE ACTIVATED: OCT 30, 2009

NUMBER: 5506                            IA #: 5506
  DATE CREATED: NOV 10, 2009            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  ROUTINE: XUMF1H
  NAME: HDIS TEXT FILE DEPLOYMENT MFS INTERFACE
  ID: XUMF1H
 GENERAL DESCRIPTION:   The text file deployment tool will replace the normal
 VistA HL7 message processing (on development and test systems only) with a new
 front end to feed MFS with HL7 message segments read from a text file.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MAIN
VARIABLES: HL(                          TYPE: Input
VARIABLES: HLQUIT                       TYPE: Input
VARIABLES: HLNODE                       TYPE: Input
VARIABLES: HLNEXT                       TYPE: Input
 VARIABLES DESCRIPTION:   
  = D GETNEXT^HDISTFDB 

NUMBER: 5507                            IA #: 5507
  FILE NUMBER: 75.1                     GLOBAL ROOT: RAO(75.1,
  DATE CREATED: NOV 19, 2009
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  NAME: VI Imaging Outside ordering     ID: RAO(75.1,
GLOBAL REFERENCE: RA0(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: 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: 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: 16                        FIELD NAME: REQUEST ENTERED DATE/TIME
  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 exam.  
GLOBAL REFERENCE: RA0(75.1,DO,.1
FIELD NUMBER: 1.1                       FIELD NAME: REASON FOR STUDY
  LOCATION: .1;1                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The reason for the study.  
GLOBAL REFERENCE: RAO(75.1,D0,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:   VistA Imaging is requesting read and write access to
 Radiology file RAD/NUC MED ORDERS (#75.1).  The information will be used for
 importing images from outside facilities. 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: outside orders
KEYWORDS: MAGDRPCB
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   Imaging is reading Radiology file RAD/NUC MED ORDERS 
 (#75.1) to obtain a list of requested orders for a specific patient.  In
 addition, Imaging will update the IMAGING LOCATION (#20) field for an outside 
 Radiology order.  

NUMBER: 5508                            IA #: 5508
  FILE NUMBER: 70                       GLOBAL ROOT: RADPT('AO'
  DATE CREATED: NOV 20, 2009
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  NAME: Imaging Outside/import images   ID: RADPT('AO'
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 (#75.1)
 to the exam.  
GLOBAL REFERENCE: RADPT(D0,'DT',D1,0
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(D0,'DT',D1,'P',D2,0
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.  
 GENERAL DESCRIPTION:   VistA Imaging's importing of outside Radiology exams
 requires reading Radiology file RAD/NUC MED PATIENT (#70) to obtain an exam
 record for attaching the image to the exam.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: MAGDRPCB
KEYWORDS: outside orders
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   Imaging will do FileMan reads on Radiology file RAD/NUC
 MED PATIENT (#70) to get the radiology exam number as well as pertinent fields
 for the exam.  Reading global ^RADPT("AO" is required to obtain the sublevel
 IENs for an entry in EXAMINATION subfile (#70.03).  

NUMBER: 5509                            IA #: 5509
  DATE CREATED: DEC 03, 2009            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  ROUTINE: XUMF5I
  NAME: HDIS TEXT FILE DEPLOYMENT MD5 CHECKSUM QUERY
  ID: XUMF5I
 GENERAL DESCRIPTION:   The text file deployment tool will call EN^XUMF5I to
 calculate the checksum for a STS deployment.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Main entry point to calculate MD5 checksums.  
VARIABLES: X0                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN or name of entry from 4.005 file 
VARIABLES: MODE                         TYPE: Input
 VARIABLES DESCRIPTION:   0 for regular mode.  

NUMBER: 5510                            IA #: 5510
  DATE CREATED: DEC 09, 2009            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  ROUTINE: XUS
  NAME: HDIS TEXT FILE DEPLOYMENT - ENTER PASSWORD
  ID: XUS
 GENERAL DESCRIPTION:   HDIS Text File Deployment Tool needs to enter a
 password for an ftp session.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$ACCEPT
 COMPONENT DESCRIPTION:   Enter text with *'s displayed on screen.  

NUMBER: 5511                            IA #: 5511
  FILE NUMBER: 8925.1                   GLOBAL ROOT: TIU
  DATE CREATED: DEC 09, 2009
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Supported                      TYPE: File
  NAME: HDIS - TIU MAPPING EXTRACT 1    ID: TIU
 GENERAL DESCRIPTION:   The HDIS Mapping Validation Server Option needs to
 query data in TIU Document Definition file (#8925.1) to use in the Mapping 
 Validation Logic Field in the HDIS File/Field file (#7115.6).  
  STATUS: Pending

NUMBER: 5512                            IA #: 5512
  FILE NUMBER: 8926.1                   GLOBAL ROOT: TIU
  DATE CREATED: DEC 09, 2009
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Supported                      TYPE: File
  NAME: HDIS - TIU MAPPING EXTRACT 2    ID: TIU
 GENERAL DESCRIPTION:   The HDIS Mapping Validation Server Option needs to
 query data in the TIU VHA ENTERPRISE STANDARD TITLE File (#8926.1) to use in
 the Mapping Validation Logic Field in the HDIS File/Field file (#7115.6).  
  STATUS: Pending

NUMBER: 5513                            IA #: 5513
  FILE NUMBER: 409.61                   GLOBAL ROOT: SD(
  DATE CREATED: DEC 10, 2009            CUSTODIAL PACKAGE: LIST MANAGER
  USAGE: Supported                      TYPE: File
  NAME: HDI PATCH 10 PREINSTALL CLEANUP
  ID: SD(
 GENERAL DESCRIPTION:   The pre-install routine (HDI1010I) deletes all but the
 zero node of the List Manager (LM) Templates for the Generic Mapping Tool and
 Text File Deployment Tool.  This is to overcome a problem in KIDS where LM
 templates are not updated when re-installed.  
  STATUS: Pending

NUMBER: 5514                            IA #: 5514
  DATE CREATED: DEC 10, 2009
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU GET TEMPLATE DATA
 GENERAL DESCRIPTION:   RPC TIU TEMPLATE GET TEMPLATE returns data on a
 specific TIU TEMPLATE.  12/10/09: This RPC will be released in TIU*1*252.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: TEMPLATE
SUBSCRIBING PACKAGE: DENTAL

NUMBER: 5515                            IA #: 5515
  DATE CREATED: DEC 29, 2009            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XTHC10
  NAME: HTTP Client                     ID: XTHC10
 GENERAL DESCRIPTION:   This API provides access to a HTTP client to retrieve
 WEB pages.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: HTTP
COMPONENT/ENTRY POINT: $$GETURL(URL,XT8FLG,XT8RDAT,XT8RHDR,XT8SDAT,XT8SHDR)
 COMPONENT DESCRIPTION:   GETS THE DATA FROM THE PROVIDED URL USING HTTP 1.0 
  
 Return values: 
  
         <0  Error Descriptor (see the $$ERROR^XTERROR) 
         >0  HTTP Status Code^Description 
  
 See the http://www.faqs.org/rfcs/rfc1945.html for more details of HTTP status
 codes.  
VARIABLES: URL                          TYPE: Input
 VARIABLES DESCRIPTION:   URL (http://host:port/path) 
VARIABLES: XT8FLG                       TYPE: Input
 VARIABLES DESCRIPTION:   Timeout and flags to control processing.  If a value
 of  this parameter starts from a number then this number is used as a value of
 the timeout (in seconds). Otherwise, the default value of 5 seconds is used.  
  
VARIABLES: XT8RDAT                      TYPE: Output
 VARIABLES DESCRIPTION:   Closed root of the variable where the message body is
 returned. Data is stored in consecutive nodes (numbers starting from 1). If a
 line is longer than 245 characters, only 245 characters are stored in the
 corresponding node. After that, overflow sub-nodes are created. For example: 
 ;
 @XT8DATA@(1)="<html>" @XT8DATA@(2)="<head><title>VistA</title></head>" 
 @XT8DATA@(3)="<body>" @XT8DATA@(4)="<p>" @XT8DATA@(5)="Beginning of a very
 long line" @XT8DATA@(5,1)="Continuation #1 of the long line" 
 @XT8DATA@(5,2)="Continuation #2 of the long line" @XT8DATA@(5,...)=...  
 @XT8DATA@(6)="</p>" 
VARIABLES: XT8RHDR                      TYPE: Output
 VARIABLES DESCRIPTION:   Reference to a local variable where the parsed
 headers are returned.  Header names are converted to upper case; the values
 are left "as is". The root node contains the status line. For example: 
 ;
 XT8HDR="HTTP/1.0 200 OK" XT8HDR("CACHE-CONTROL")="private" 
 XT8HDR("CONNECTION")="Keep-Alive" XT8HDR("CONTENT-LENGTH")="2690" 
 XT8HDR("CONTENT-TYPE")="text/html" XT8HDR("DATE")="Fri, 26 Sep 2003 16:04:10
 GMT" XT8HDR("SERVER")="GWS/2.1" 
VARIABLES: XT8SDAT                      TYPE: Input
 VARIABLES DESCRIPTION:   Closed root of a variable containing body of the
 request message. Data should be formatted as described earlier (see the
 XT8RDAT parameter).  
  
 NOTE: If this parameter is defined, not empty, and the referenced array 
 contains data then the POST request is generated. Otherwise, the GET request
 is sent.  
VARIABLES: XT8SHDR                      TYPE: Input
 VARIABLES DESCRIPTION:   Reference to a local variable containing header
 values, which will be added to the request.  
  DATE ACTIVATED: DEC 29, 2009

NUMBER: 5516                            IA #: 5516
  DATE CREATED: DEC 29, 2009            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Supported                      TYPE: Routine
  ROUTINE: XTHCUTL                      NAME: HTTP client utilities
  ID: XTHCUTL
 GENERAL DESCRIPTION:   ***** Replaced with DBIA $5555.  
  
 Utility API to help with HTML.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$DECODE(STR)
 COMPONENT DESCRIPTION:   DeCode a string &#32=" ", &lt;=<, &gt;=>, &nbsp;=" " 
 Returns a string with the escaped characters replaced.  
VARIABLES: STR                          TYPE: Input
 VARIABLES DESCRIPTION:   A string of HTML.  
  DATE ACTIVATED: DEC 29, 2009

NUMBER: 5517                            IA #: 5517
  DATE CREATED: JAN 22, 2010            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSNFDAMG
  NAME: GET FDA MEDICATION GUIDE        ID: PSNFDAMG
 GENERAL DESCRIPTION:   This allows the Outpatient Pharmacy application to
 request an FDA Medication Guide to be printed via the JAVA Client.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Display FDA Medication Guide on a browser via HTTL
 Toolkit call. A Java application must be pre-installed on the user's PC for
 the functionality to work.  
VARIABLES: VAPRDIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the VA PRODUCT file (#50.68).  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: JAN 22, 2010

NUMBER: 5518                            IA #: 5518
  DATE CREATED: FEB 10, 2010
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIULC
  NAME: TIULC EXTRINSIC FUNCTIONS       ID: TIULC
 GENERAL DESCRIPTION:   This ICR describes the extrinsic functions found in the
 routine TIULC, which support a variety of useful functions for determining a
 document's state, size, checksum, etc.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU
KEYWORDS: TIULC
KEYWORDS: EXTRINSIC FUNCTIONS
COMPONENT/ENTRY POINT: STATUS
 COMPONENT DESCRIPTION:   This extrinsic function accepts the Internal Entry
 Number of a TIU Document as its only argument, and returns the processing
 status (as defined in the TIU STATUS file (#8925.6), as its result. Allowable 
 results are: 
  
 amended completed deleted purged retracted uncosigned undictated unreleased 
 unsigned untranscribed unverified 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Required - This is the Internal Entry Number of the
 document in the TIU 
            DOCUMENT file (#8925).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: FEB 12, 2010

NUMBER: 5519                            IA #: 5519
  DATE CREATED: FEB 18, 2010
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RAMAGU04
  NAME: Return a RAD/NUC MED PATIENT file IEN
  ID: RAMAGU04
 GENERAL DESCRIPTION:   This is a private integration agreement between VistA
 Radiology/Nuclear Medicine and VistA Imaging. Vista Imaging is looking for a
 Rad/Nuc Med patient. If that patient exists, return the DFN of the patient.  
  
 If the patient record does not exist, add (automate the radiology registration
 process) the patient record to the RAD/NUC MED PATIENT (#70) file and return
 the DFN of the patient.  
  
 If an error occurs, an error descriptor with a negative value is returned.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: auto register rad patient
KEYWORDS: RA*5.0*90 DFN
KEYWORDS: MAG*3.0*53 DFN
KEYWORDS: ISI
KEYWORDS: ISI*1.1*110 DFN
KEYWORDS: VistARad COTS
KEYWORDS: MEDICOM
COMPONENT/ENTRY POINT: RAPTREG
 COMPONENT DESCRIPTION:   This function silently registers a patient in the
 RAD/NUC MED PATIENT (#70) file if and only if the patient has not been
 registered in the past.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN as an input variable: 
 -------------------------
 DFN is the Patient IEN (in file #2).  
VARIABLES: USLCAT (optional)            TYPE: Input
 VARIABLES DESCRIPTION:   Usual category (value of the USUAL CATEGORY (#.04)
 field of the RAD/NUC MED PATIENT file #70). By default ($G(USLCAT)=""), "O"
 (outpatient) is assumed.  
VARIABLES: DFN (Return)                 TYPE: Output
 VARIABLES DESCRIPTION:   DFN is one of two values:                           
 <0 Error Descriptor                                 >0 IEN in the file #70
 (same value as DFN) 
VARIABLES:  
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   This integration agreement was created as a result of
 the MAG*3.0*53 & RA*5.0*90 software development initiative.  
SUBSCRIBING PACKAGE: ISI IMAGING
 SUBSCRIBING DETAILS:   Added 12/28/22 effective with ISI*1.1*110 
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Added 10/17/24: Effective with Patch MECH 1.0 Called to
 line tag RAPTREG to ensure a patient is registered in the RAD/NUC MED PATIENT
 file (#70).  
  DATE ACTIVATED: FEB 23, 2010

NUMBER: 5520                            IA #: 5520
  FILE NUMBER: 9000010.12               GLOBAL ROOT: AUPNVSK(
  DATE CREATED: FEB 18, 2010
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ ACCESS TO V SKIN TEST FILE
  ID: AUPNVSK(
 GENERAL DESCRIPTION:   Clinical Case Registries requests access to the V SKIN
 TEST file (#9000010.12): Direct global read access to the "C" cross-reference
 (PATIENT NAME .02) and FileMan read access to the following fields: SKIN TEST
 (.01) VISIT (.03) RESULTS (.04) READING (.05) DATE READ (.06) EVENT DATE AND
 TIME (1201) ORDERING PROVIDER (1202) COMMENTS (81101) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: V SKIN
KEYWORDS: AUPNVSK
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
  DATE ACTIVATED: FEB 20, 2010

NUMBER: 5521                            IA #: 5521
  FILE NUMBER: 9000010.11               GLOBAL ROOT: AUPNVIMM(
  DATE CREATED: FEB 18, 2010
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ ACCESS TO V IMMUNIZATION FILE
  ID: AUPNVIMM(
 GENERAL DESCRIPTION:   Clinical Case Registries requests access to the V
 IMMUNIZATION file (#9000010.11): Direct global read access to the "C"
 cross-reference (PATIENT NAME .02) and FileMan read access to the following
 fields: IMMUNIZATION (.01) VISIT (.03) REACTION (.06) CONTRAINDICATED (.07) 
 EVENT DATE AND TIME (1201) ORDERING PROVIDER (1202) COMMENTS (81101) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: V IMMUNIZATION
KEYWORDS: AUPNVIMM
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
  DATE ACTIVATED: FEB 20, 2010

NUMBER: 5522                            IA #: 5522
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: FEB 23, 2010            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: ECAR                            ID: VA(200
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 5523                            IA #: 5523
  FILE NUMBER: 200                      GLOBAL ROOT: VA(
  DATE CREATED: FEB 23, 2010            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: kjlh                            ID: VA(
  STATUS: Pending
SUBSCRIBING PACKAGE: MAILMAN

NUMBER: 5524                            IA #: 5524
  FILE NUMBER: 9.4                      GLOBAL ROOT: DIC(9.4
  DATE CREATED: FEB 23, 2010            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: File
  NAME: CHANGE PACKAGE NAME AND DESCRIPTIONS
  ID: DIC(9.4
 GENERAL DESCRIPTION:   ICB (DSIV namespace) and FBCS (DSIF namespace) changed
 their package names during the Class I process.  The installation of the full
 build at existing ICB and FBCS sites (the Class III sites) did not update the
 package name.  The VA Business office for these products would like the
 package name and description fields to more accurately reflect the Class I
 information.  
    
 A pre-install for patch 1 for both of these applications will do a look-up on
 the 'C' cross-reference of the PACKAGE file (#9.4) to find the appropriate
 entry and change the following fields using Fileman: 
    
    ^DIC(9.4,D0,0) 
     .01       NAME                   0;1       Fileman write 
      2        SHORT DESCRIPTION      0;3       Fileman write 
    ^DIC(9.4,D0,1,D1,0) 
     .01       DESCRIPTION            WP field  Fileman write 
  STATUS: Pending                       DURATION: Next Version
  GOOD ONLY FOR VERSION: Patch 1
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5525                            IA #: 5525
  DATE CREATED: MAR 02, 2010            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBAUTL
  NAME: DETERMINE COST OF COPAYMENT     ID: IBAUTL
 GENERAL DESCRIPTION:   AR package needs to determine the potential cost of a
 copayment bill.  This DBIA will allow for lookup of the potential cost/charge. 
 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 01, 2012
KEYWORDS: IBAUTL
KEYWORDS: COST
COMPONENT/ENTRY POINT: COST
 COMPONENT DESCRIPTION:   Based on the information passed the potential per
 unit cost will be returned.  All variables are assumed to be present.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN = patient's IEN from the PATIENT (#2) file. 
 Assumed to be present, not passed in as a parameter.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   DA should be the IEN for a record in the IB ACTION
 TYPE (#350.1) file.  This variable is assumed to be present by the DBIA, not
 passed in as a parameter.  
VARIABLES: X1                           TYPE: Output
 VARIABLES DESCRIPTION:   This represents the per unit cost of an item.  It is
 the subscribing package's responsibility to clean up this variable.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: MAR 03, 2010

NUMBER: 5526                            IA #: 5526
  FILE NUMBER: 3.9                      GLOBAL ROOT: XMB(3.9,
  DATE CREATED: APR 06, 2010            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SPN ACCESS TO MESSAGE FILE (#3.9)
  ID: XMB(3.9,
GLOBAL REFERENCE: XMB(3.9,'B',$E(X,1,30),DA)
 GLOBAL DESCRIPTION:   "B" cross-reference on the SUBJECT field.  
  
  
GLOBAL REFERENCE: XMB(3.9,D0,2,1,0)
 GLOBAL DESCRIPTION:   First line of the TEXT multiple.  
  
GLOBAL REFERENCE: XMB(3.9,DA(1),1,'C',$E(X,1,30),DA)
 GLOBAL DESCRIPTION:   "C" cross-reference of the RECIPIENT sub-file.  
  
  
GLOBAL REFERENCE: XMB(3.9,D0,1,D1,0)
FIELD NUMBER: 5                         LOCATION: 0;6
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Status field.  
  
 GENERAL DESCRIPTION:   The Spinal Cord Dysfunction package (SPN), requests
 permission to directly access the global for the Message file (#3.9). This is
 for a one-time emergency patch, SPN*2.0*27.  
  
 The SPN package needs to resend Mailman messages that failed to be delivered 
 during a several day period in March 2010. Delivery failed because the Austin
 Automation Center inadvertently deactivated the domain of the server.  
  
 The post-install routine SPNP27 will locate the messages by referencing the
 Message file at these locations: 
  
 1) "B" cross-reference 2) first line of the TEXT sub-file (#3.92) 3) "C"
 cross-reference ont he RECIPIENT sub-file (#3.91) 4) 0 node of the RECIPIENT
 subfile (#3.91) 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 03, 2010
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
  DATE ACTIVATED: APR 07, 2010

NUMBER: 5527                            IA #: 5527
  FILE NUMBER: 723                      GLOBAL ROOT: ECC(723,
  DATE CREATED: MAY 04, 2010            CUSTODIAL PACKAGE: EVENT CAPTURE
  USAGE: Private                        TYPE: File
  NAME: MEDICAL SPECIALTY file 723      ID: ECC(723,
GLOBAL REFERENCE: ECC(723,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Lab needs to access the MEDICAL SPECIALTY file (#723)
 from print and sort templates for extracts to Cerner Lab system.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE

NUMBER: 5528                            IA #: 5528
  FILE NUMBER: 10.2                     GLOBAL ROOT: DIC(10.2,D0,0)
  DATE CREATED: MAY 05, 2010            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ETHNICITY FILE ACCESS
  ID: DIC(10.2,D0,0)
GLOBAL REFERENCE: DIC(10.2,
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
FIELD NUMBER: 200                       FIELD NAME: INACTIVE
  LOCATION: .02;1                       ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   LAB SERVICE package will use the NAME (#.01), HL7 VALUE
 (#3) and INACTIVE (#200) fields in Fileman sort and print templates.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: NOV 02, 2010

NUMBER: 5529                            IA #: 5529
  FILE NUMBER: 3.8                      GLOBAL ROOT: XMB(3.8,
  DATE CREATED: MAY 10, 2010            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SPN EDITS MAIL GROUP
  ID: XMB(3.8,
GLOBAL REFERENCE: XMB(3.8,'B',
FIELD NUMBER: XMB(3.8,<IEN>,6,'B',
 GLOBAL DESCRIPTION:   The "B" cross-reference to do a lookup by name for the
 mail group.  
  
GLOBAL REFERENCE: XMB(3.8,<IEN>,6,'B',
 GLOBAL DESCRIPTION:   The "B" cross-reference on the MEMBERS - REMOTE multiple
 to find the old remote member by name.  
  
 GENERAL DESCRIPTION:   The Spinal Cord Dysfunction package needs to change the
 recipient of its HL7 messages that are sent via MailMan.  To accomplish that
 it needs one-time permission to delete the old Remote Member and add a new
 Remote Member of the Mail Group that is used to addres its HL7 messages.  
 This will be used in patch SPN*2.0*26.  
  
 The lookp is done via the "B" cross-reference.  The adding and deleting of the 
 remote members are done via Fileman APIs. 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2010
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
 SUBSCRIBING DETAILS:   One-time access to the Mail Group file to add a remote
 member and delete an existing remote member for patch SPN*2.0*26.  
  
  DATE ACTIVATED: MAY 10, 2010

NUMBER: 5530                            IA #: 5530
  FILE NUMBER: 779.004                  GLOBAL ROOT: HL(779.004
  DATE CREATED: MAY 12, 2010            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ ACCESS TO COUNTRY CODE FILE
  ID: HL(779.004
GLOBAL REFERENCE: HL(779.004,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   LAB SERVICE will use the CODE (#.01) and DESCRIPTION
 (#2) fields in Fileman sort and print templates.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: NOV 02, 2010

NUMBER: 5531                            IA #: 5531
  DATE CREATED: MAY 19, 2010            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMORCH
  NAME: CLINICAL REMINDER ORDER CHECKS  ID: PXRMORCH
 GENERAL DESCRIPTION:   This provides the Clinical Reminder functionality
 needed for reminder order checks.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: OR
KEYWORDS: PXRM ORDER CHECKS
COMPONENT/ENTRY POINT: ORDERCHK
 COMPONENT DESCRIPTION:   This is the entry point to call the reminder order
 checks.  
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN is the patient DFN.  
  
VARIABLES: OI                           TYPE: Input
 VARIABLES DESCRIPTION:   OI is the IEN of the Orderable Item entry from the
 Orderable Item file, file #101.43.  
  
VARIABLES: TEST                         TYPE: Input
 VARIABLES DESCRIPTION:   This corresponds to the STATUS field in file #801.1.
 It should be set to TEST when the reminder order check is under development
 and being tested. When the reminder order check is ready for production it is 
 set to PRODUCTION.  
  
  
VARIABLES: TESTER                       TYPE: Input
 VARIABLES DESCRIPTION:   This should be set to 1 only ifthe API is being
 called from the reminder order check tester otherwise it should be 0. All
 external application should set this to 0.  
  
  
VARIABLES: TMP($J,SUB                   TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,SUB, is the output of the API. Where SUB is
 either the OI value or the DRUG value.  
  
VARIABLES: DRUG                         TYPE: Input
 VARIABLES DESCRIPTION:   DRUG is the IEN from the DRUG, file #50. The API will
 only accept an OI or the DRUG entry.  
  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: MEDICATION ORDER CHECK (MOCHA)
 SUBSCRIBING DETAILS:   02/27/14 DT: The Mocha package is a suscriber because
 Mocha Enhancements 2B is the patch group, which includes the following
 patches, PSO*7*412 and PSJ*5*282, that include code to support Mocha.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   02/27/14 DT: Mocha Enhancements 2B is the patch group. 
 The PSO*7*412 patch is included in the Mocha patch group to support 
 enhancement logic.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   2/27/14 DT: Mocha Enhancements 2B is the patch group.
 The PSJ*5*282 patch is included in the Mocha patch group to support
 enhancement logic.  
  DATE ACTIVATED: FEB 27, 2014

NUMBER: 5532                            IA #: 5532
  DATE CREATED: JUN 04, 2010            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS GET VISITOR
  REMOTE PROCEDURE: XUS GET VISITOR
 GENERAL DESCRIPTION:   VistA Imaging is requesting permission to use a Kernel
 API, GETVISIT^XUSBSE1 to verify if a BSE token is still valid.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GETVISIT
KEYWORDS: MAG
KEYWORDS: BSE
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   Added 9/27/19 
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 6/21/23. CDSP is developing a CPRS COM extension
 to capture user generated events to trigger clinical decision support
 applications. CDSP is utilizing solutions based on FHIR, SMART on FHIR and CDS
 Hooks standards. CDSP needs to validate BSE Token passed by COM object to 
 secure communication between COM object and backend API.  
  
 Temporary approval provided with the following contingencies: 1) Once an
 appropriate solution is available in production, the CDSP application agrees
 to transition to the appropriate solution within four months. Once CDSP has
 transitioned, this approval will be removed.  2) When using BSE, CDSP agrees
 to not create or provision VistA accounts.  3) When using BSE, CDSP agrees to
 not create duplicate VistA accounts.  4) When using BSE, CDSP agrees to only
 access VistA systems where a known user has a known VistA account.  5) This
 temporary approval does not authorize CDSP to bypass any VA directive,
 handbook or Identity Access Management policies.  
  
 If CDSP fails to comply with the contingencies then VA security officers will
 be notified and CDSP's authority to operate could be suspended.  
  DATE ACTIVATED: JUN 16, 2010

NUMBER: 5533                            IA #: 5533
  DATE CREATED: JUN 11, 2010            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Other
  NAME: ACCESS TO READ FILE #200 ANPI INDEX
 GENERAL DESCRIPTION:   Permission to access the file #200 ANPI index to find
 records with NPIs.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: NPI ANPI
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 5534                            IA #: 5534
  DATE CREATED: JUN 16, 2010            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: VAFHLDG1                     NAME: DBIA5534
  ID: VAFHLDG1
 GENERAL DESCRIPTION:   DG1 - Diagnosis Information Segment 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DG1
KEYWORDS: VAFHLDG1
COMPONENT/ENTRY POINT: $$EN(VAFENC,VAFSTR,VAFHLQ,VAFHLFS,VAFARRY)
 COMPONENT DESCRIPTION:   This function will create VA-specific DG1 segment(s)
 for a given outpatient encounter.  The DG1 segment is designed to transfer
 generic information about an outpatient diagnosis or diagnoses.  
VARIABLES: VAFENC                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Outpatient Encounter (#409.68) file 
VARIABLES: VAFSTR                       TYPE: Input
 VARIABLES DESCRIPTION:   String of fields requested separated by commas 
VARIABLES: VAFHLQ                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional HL7 null variable. If not there, use default
 HL7 variable.  
VARIABLES: VAFHLFS                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional HL7 field separator. If not there, use
 default HL7 variable.  
VARIABLES: VAFARRY                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional user-supplied array name to hold the HL7 DG1
 segments.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Scheduling request calling $$EN^VAFHLDG1 for use by the
 Ambulatory Care Database Project.  

NUMBER: 5535                            IA #: 5535
  DATE CREATED: JUN 16, 2010            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: VAFHLPR1                     NAME: DBIA5535
  ID: VAFHLPR1
 GENERAL DESCRIPTION:   PR1 - Procedure Information Segment 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PR1
KEYWORDS: VAFHLPR1
COMPONENT/ENTRY POINT: $$EN(VAFENC,VAFSTR,VAFHLQ,VAFHLFS,VAFHLECH,VAFARRY)
 COMPONENT DESCRIPTION:   This function will create VA-specific PR1 segment(s)
 for a given outpatient encounter.  The PR1 segment is designed to transfer
 generic information about an outpatient procedure or procedures.  
VARIABLES: VAFENC                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Outpatient Encounter (#409.68) file 
VARIABLES: VAFSTR                       TYPE: Input
 VARIABLES DESCRIPTION:   String of fields requested separated by commas 
VARIABLES: VAFHLQ                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional HL7 null variable. If not there, use default
 HL7 variable 
VARIABLES: VAFHLFS                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional HL7 field separator. If not there, use
 default HL7 variable 
VARIABLES: VAFHLECH                     TYPE: Input
 VARIABLES DESCRIPTION:   HL7 variable containing encoding characters 
VARIABLES: VAFARRY                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional user-supplied array name which will hold PR1
 segments 
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Scheduling request calling $$EN^VAFHLPR1 for use by the
 Ambulatory Care Database Project.  

NUMBER: 5536                            IA #: 5536
  DATE CREATED: JUN 17, 2010            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: VAFHLZSC                     NAME: DBIA5536
  ID: VAFHLZSC
 GENERAL DESCRIPTION:   ZSC - VA-Specific Stop Code Segment 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ZSC
KEYWORDS: VAFHLZSC
COMPONENT/ENTRY POINT: $$EN(VAFENC,VAFSTR,VAFHLQ,VAFHLFS,VAFARRY)
 COMPONENT DESCRIPTION:   This function will create VA-specific ZSC segment(s)
 for a given outpatient encounter.  The ZSC segment is designed to transfer
 service indicator (stop code) information pertaining to a patient visit.  
VARIABLES: VAFENC                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Outpatient Encounter (#409.68) file.  
VARIABLES: VAFSTR                       TYPE: Input
 VARIABLES DESCRIPTION:   String of fields requested separated by commas.  
VARIABLES: VAFHLQ                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional HL7 null variable. If not there, use default
 HL7 variable.  
VARIABLES: VAFHLFS                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional HL7 field separator. If not there, use
 default HL7 variable.  
VARIABLES: VAFARRY                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional user-supplied array name which will hold HL7
 ZSC segments.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Scheduling request calling $$EN^VAFHLZSC for use by the
 Ambulatory Care Database Project.  

NUMBER: 5537                            IA #: 5537
  DATE CREATED: JUN 17, 2010            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: VAFHLZEN                     NAME: DBIA5537
  ID: VAFHLZEN
 GENERAL DESCRIPTION:   ZEN - VA-Specific Enrollment Segment 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ZEN
KEYWORDS: VAFHLZEN
COMPONENT/ENTRY POINT: $$EN(DFN,VAFSTR,VAFNUM,VAFHLQ,VAFHLFS)
 COMPONENT DESCRIPTION:   This generic extrinsic function is designed to return
 the HL7 Enrollment (ZEN) segment. This segment contains VA-specific current
 enrollment information for a patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   internal entry number of Patient (#2) file 
VARIABLES: VAFSTR                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) string of fields requested, separated by
 commas.  If not passed, return all data fields.  
VARIABLES: VAFNUM                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) sequential number for SET ID (default=1) 
VARIABLES: VAFHLQ                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) HL7 null variable.  
VARIABLES: VAFHLFS                      TYPE: Input
 VARIABLES DESCRIPTION:   (optional) HL7 field separator.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Scheduling request calling $$EN^VAFHLZEN for use by the
 Ambulatory Care Database Project.  

NUMBER: 5538                            IA #: 5538
  DATE CREATED: JUN 17, 2010            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: VAFHLROL                     NAME: DBIA5538
  ID: VAFHLROL
 GENERAL DESCRIPTION:   ROL - Role Segment 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ROL
KEYWORDS: VAFHLROL
COMPONENT/ENTRY POINT: $$OUTPAT(PARAM,OUTARR,FIELDS,FLDSEP,ENCODE,NULL,MAXLEN)
VARIABLES: PARAM                        TYPE: Input
 VARIABLES DESCRIPTION:   Array, subscripted by paramter name, that contains
 information specific to building of segment (full global reference) 
VARIABLES: OUTARR                       TYPE: Input
 VARIABLES DESCRIPTION:   Output array (full global reference).  Defaults to
 ^TMP("VAFHLROL",$J) 
VARIABLES: FIELDS                       TYPE: Input
 VARIABLES DESCRIPTION:   List of fields (sequence numbers) to include
 seperated by commas. Defaults to all required fields (1-4).  
VARIABLES: FLDSEP                       TYPE: Input
 VARIABLES DESCRIPTION:   HL7 field seperator (1 character). Defaults to ^
 (carrot).  
VARIABLES: ENCODE                       TYPE: Input
 VARIABLES DESCRIPTION:   HL7 encoding characters (4 characters). Defaults to ~
 |\& (tilde bar backslash ampersand).  
VARIABLES: NULL                         TYPE: Input
 VARIABLES DESCRIPTION:   HL7 null designation. Defaults to "" (quote quote).  
VARIABLES: MAXLEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Maximum length of a single line in the segment array
 (i.e. when to wrap to next node in output). Defaults to 245.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Scheduling request calling $$OUTPAT^VAFHLROL for use by
 the Ambulatory Care Database Project.  

NUMBER: 5539                            IA #: 5539
  DATE CREATED: JUN 22, 2010            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCMCM
  NAME: COTS INV LOG                    ID: PRCMCM
 GENERAL DESCRIPTION:   IFCAP API to log messaging transactions between VistA
 and remote COTS Inventory System.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCMCM
COMPONENT/ENTRY POINT: GENERATE
 COMPONENT DESCRIPTION:   To be called right after the HL7 API call 
               D GENERATE^HLMA(PRCVPRO,"LM",1,.PRCVDP) 
  
 Should be called as: 
  
               D GENERATE^PRCMCM(PRCVDP,"VENDOR UPDATE") 
VARIABLES: PRCVDP                       TYPE: Input
 VARIABLES DESCRIPTION:   This should be the same variable that was used as the
 4th parameter to GENERATE^HLMA(PRCVPRO,"LM",1,.PRCVDP).  Should not be passed
 by reference as in the HLMA call.  
VARIABLES: PRCPROC                      TYPE: Input
 VARIABLES DESCRIPTION:   This is free text that describes the business process
 that occurred such as "VENDOR UPDATE".  The free text is open to developer
 design.  
SUBSCRIBING PACKAGE: PROSTHETICS
SUBSCRIBING PACKAGE: SURGERY
  DATE ACTIVATED: JUN 22, 2010

NUMBER: 5540                            IA #: 5540
  FILE NUMBER: 8925.1                   GLOBAL ROOT: TIU(8925.1,
  DATE CREATED: JUN 28, 2010
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Point to TIU file 8925.1
  ID: TIU(8925.1,
 GENERAL DESCRIPTION:   This agreement permits MENTAL HEALTH file MH TESTS AND
 SURVEYS (#601.71) to point to TIU DOCUMENT DEFINITION file 8925.1.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: POINT
SUBSCRIBING PACKAGE: MENTAL HEALTH
  DATE ACTIVATED: FEB 15, 2011

NUMBER: 5541                            IA #: 5541
  DATE CREATED: JUN 28, 2010
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUSRVA
  NAME:  User Requires Cosignature      ID: TIUSRVA
 GENERAL DESCRIPTION:   This agreement permits packages to determine whether
 the author requires a cosignature for a document of a given title.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: require
KEYWORDS: cosignature
COMPONENT/ENTRY POINT: GETTITLE(TIUY,TIUDA)
 COMPONENT DESCRIPTION:   Given the IEN TIUDA in the TIU DOCUMENT FILE (8925)
 of a document, this component gets the .01 field in 8925.  This corresponds to
 the IEN in the TIU DOCUMENT DEFINITION file (8925.1) of the Title of the
 document.  
VARIABLES: TIUY                         TYPE: Output
 VARIABLES DESCRIPTION:   This variable is passed by reference. Upon exit, it
 contains the .01 field in the TIU DOCUMENT FILE (8925) of the document.  This
 corresponds to the IEN in file 8925.1 of the Title of the document.  
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN in the TIU DOCUMENT FILE (8925) of a
 document.  
VARIABLES:  
COMPONENT/ENTRY POINT: REQCOS(TIUY,TIUTYP,TIUDA,TIUSER,TIUDT)
 COMPONENT DESCRIPTION:   This component evaluates whether or not a user
 (generally the author) requires the cosignature of a supervisor/attending
 physician.  The requirement is evaluated with respect to a given TIU document
 or document Title.  
VARIABLES: TIUY                         TYPE: Output
 VARIABLES DESCRIPTION:   This variable is passed by reference. Upon exit it
 contains 0 indicating that the author (or user) does NOT require cosignature
 for this document or 1 indicating that the author DOES require cosignature.  
VARIABLES: TIUTYP                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the type, that is, Title IEN, in the TIU
 DOCUMENT DEFINITION file (8925.1) of the document of interest.  It corresponds
 to the NAME field (.01) in the TIU DOCUMENT FILE (8925) of the document.
 Either TIUTYP or TIUDA is required.  
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN in the TIU DOCUMENT FILE (8925) of
 the document. Either TIUTYP OR TIUDA is required.  
VARIABLES: TIUSER                       TYPE: Input
 VARIABLES DESCRIPTION:   This is optional, containing the IEN in the NEW
 PERSON file of the person being queried. If not sent, the current user (DUZ)
 is assumed.  
VARIABLES: TIUDT                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the (optional) date for which it is to be
 determined whether or not TIUSER requires cosignature.  If TIUDT is not sent
 and TIUDA is sent, TIUDT is assumed to be the REFERENCE DATE (field 1301) of
 the document. Otherwise, it is assumed to be today.  The variable must be in 
 internal FILEMAN format and must include only the date, not the date/time.  
SUBSCRIBING PACKAGE: MENTAL HEALTH
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 6/11/20, effective with OR*3*519 
  DATE ACTIVATED: FEB 15, 2011

NUMBER: 5542                            IA #: 5542
  DATE CREATED: JUN 29, 2010
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: Ward Clerk Menu Access
 GENERAL DESCRIPTION:   The Ward Clerk Menu [OR MAIN MENU WARD CLERK] will be
 added to the HRC Pharmacy Menu [DVBA HRC MENU PHARMACY] option and the new
 menu, HRC Pharmacy Customer Care Menu [DVBA HRC MENU PHARMACY CC]. The Ward
 Clerk Menu option will be used by the HRC contact representatives and 
 distributed in patch DVBA*2.7*148. The HRC has provided the following 
 justification for access to the Ward Clerk Menu option: 
  
 The request for the VistA option Ward Clerk Menu [OR MAIN MENU WARD CLERK]
 will provide additional functionality to flag renewal requests for provider
 action. Renewal of prescriptions that have expired or have no refills
 remaining constitute 26.1% of the call fielded by the HRC Pharmacy Customer
 Care Center (PCCC). This type of call cannot be easily resolved by the
 facility pharmacies, because action on the part of the provider is required.
 With access to the option, the HRC agent can send a "View Alert" directly to
 the provider through VistA.  The provider will receive the "View Alert"
 immediately upon being flagged by the HRC agent to ensure prompt attention and
 resolution of the required prescription renewal. Safeguards are built into the 
 Ward Clerk version of the VistA option not allowing the HRC PCCC agent to
 discontinue, copy, change or renew a prescription without verification by a
 facility clinician. CAPRI does recognize credentials so the renewals flagged
 by HRC agents would not be processed until signed off by the provider.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AMIE
KEYWORDS: HRC
KEYWORDS: DVBA
KEYWORDS: Health Revenue Center
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   The Health Revenue Center (HRC) is using the telnet
 functionality in the CAPRI application to view patient data across all VistA
 systems. CAPRI provides local common service to VistA for HRC CAPRI remote
 users and the HRC needs usage of the following menu option listed in this
 Integration Control Registration: 
  
    Ward Clerk Menu [OR MAIN MENU WARD CLERK] 
  DATE ACTIVATED: JUL 08, 2010

NUMBER: 5543                            IA #: 5543
  DATE CREATED: JUN 30, 2010
  CUSTODIAL PACKAGE: PATIENT ASSESSMENT DOCUM
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: RPC's for NUPA in rtn: NUPABCL
 GENERAL DESCRIPTION:   Contains 11 RPC's which may reference any number of
 files in VistA - thus the request for IA's.  
  STATUS: Pending
KEYWORDS: NUPA

NUMBER: 5544                            IA #: 5544
  DATE CREATED: JUN 30, 2010
  CUSTODIAL PACKAGE: PATIENT ASSESSMENT DOCUM
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: RPC's for NUPA in rtn: NUPABCL1
 GENERAL DESCRIPTION:   Contains 5 RPC's which may reference any number of
 files in VistA - thus the request for IA's.  
  STATUS: Pending
KEYWORDS: NUPA

NUMBER: 5545                            IA #: 5545
  DATE CREATED: JUN 30, 2010
  CUSTODIAL PACKAGE: PATIENT ASSESSMENT DOCUM
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: RPC's for NUPA in rtn: NUPABCL2
 GENERAL DESCRIPTION:   Contains 6 RPC's which may reference any number of
 files in VistA - thus the request for IA's.  
  STATUS: Pending
KEYWORDS: NUPA

NUMBER: 5546                            IA #: 5546
  DATE CREATED: JUL 07, 2010
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUCNSLT
  NAME: TIUCNSLT                        ID: TIUCNSLT
 GENERAL DESCRIPTION:   This agreement documents and supports the TIUCNSLT
 routine entry points listed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ISCNSLT
KEYWORDS: CLASS
COMPONENT/ENTRY POINT: ISCNSLT(TIUY,TITLE)
 COMPONENT DESCRIPTION:   Evaluates whether TITLE is a CONSULT and returns a
 Boolean value of 0 (not a CONSULT) or 1 (is a CONSULT).  
  
 Example: 
  S TITLE=1365 D ISCNSLT^TIUCNSLT(.TEST,TITLE) ZW TEST 
  TEST=1 
VARIABLES: TIUY                         TYPE: Both
 VARIABLES DESCRIPTION:   The variable that will hold the boolean value. Passed
 by reference.  
VARIABLES: TITLE                        TYPE: Input
 VARIABLES DESCRIPTION:   An entry number for the TIU DOCUMENT DEFINITION file
 (#8925.1).  
COMPONENT/ENTRY POINT: $$CLASS()
 COMPONENT DESCRIPTION:   This function returns the 8925.1 ien of the Consults
 Document Class.  
VARIABLES: $$CLASS                      TYPE: Output
 VARIABLES DESCRIPTION:   Function result, the 8925.1 ien of the Consults
 Document Class.  
COMPONENT/ENTRY POINT: POST
 COMPONENT DESCRIPTION:   Post status updates to Consult Tracking 
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the TIU document (file #8925) associated
 to the consult (file #123) 
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   Status for Consult with a TIU result.  Example:
 'INCOMPLETE' 
SUBSCRIBING PACKAGE: MENTAL HEALTH
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   Updated 2/23/26, effective with patch MAG*3.0*362 Added
 Component: POST 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP. HMP*2.0*12 released on 10/17/17 is an informational patch
 outlining the steps for the sites to shut down the application.  
                                                   
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
  DATE ACTIVATED: FEB 15, 2011

NUMBER: 5547                            IA #: 5547
  DATE CREATED: JUL 23, 2010            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: LEXLR                        NAME: LAB LOINC FILE (#95.3) API(S)
  ID: LEXLR
 GENERAL DESCRIPTION:   These API(s) support the custodial transition of the
 LAB LOINC file (#95.3) from Legacy LAB to Standards and Terminology Services
 (STS). These API(s) provide Read Access to the LAB LOINC file (#95.3) and
 should be used when accessing the file. The API(s) support Legacy LAB's 
 encapsulation efforts and STS's LOINC Deployment efforts.  
  STATUS: Pending
COMPONENT/ENTRY POINT: $$CHKCODE(LEXCODE)
 COMPONENT DESCRIPTION:   Check if LOINC Code exists 
  
 Example: 
  
 >W $$CHKCODE^LEXLR("38553-4") 
  
 38553 
VARIABLES: LEXCODE                      TYPE: Input
 VARIABLES DESCRIPTION:   LOINC Code 
VARIABLES: $$CHKCODE                    TYPE: Output
 VARIABLES DESCRIPTION:   LOINC File IEN or Null 
COMPONENT/ENTRY POINT: $$GETCODE(LEXCIEN)
 COMPONENT DESCRIPTION:   Get LOINC Code by IEN 
  
 Example: 
  
 >W $$GETCODE^LEXLR(38553) 
  
 38553-4 
VARIABLES: LEXCIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   LOINC file IEN 
VARIABLES: $$GETCODE                    TYPE: Output
 VARIABLES DESCRIPTION:   LOINC Code or Null 
COMPONENT/ENTRY POINT: GETNAME(LEXINPT,LEXINTY,.LEXNAME)
 COMPONENT DESCRIPTION:   Get LOINC Name Array by Code or IEN 
  
 Example: 
  
 >D GETNAME^LEXLR("38553-4",,.LEXNAME) 
  ZW LEXNAME 
  LEXNAME("FULLNAME")="NARCOLEPSY ASSOCIATED AG:ACNC:PT:SER/PLAS:ORD" 
  LEXNAME("SHORTNAME")="Narcolepsy Assoc Ag SerPl Ql" 
VARIABLES: LEXINPT                      TYPE: Input
 VARIABLES DESCRIPTION:   LOINC Code or IEN 
VARIABLES: LEXINTY                      TYPE: Input
 VARIABLES DESCRIPTION:   Input Type (Optional- Default "C") 
  "C"=LOINC Code 
  "I"=LOINC IEN 
VARIABLES: LEXNAME                      TYPE: Output
 VARIABLES DESCRIPTION:   LOINC Name Array subscripts: 
  ("FULLNAME")=Fully Specified Name field (#80) 
  ("SHORTNAME")=Short Name filed (#81) 
COMPONENT/ENTRY POINT: $$STATUS(LEXINPT,LEXINTY)
 COMPONENT DESCRIPTION:   Get LOINC Code Status by Code or IEN 
  
 Example: 
  
 >W $$STATUS^LEXLR("38340-6") 
  1^DEL 
VARIABLES: LEXINPT                      TYPE: Input
 VARIABLES DESCRIPTION:   LOINC Code or IEN 
VARIABLES: LEXINTY                      TYPE: Input
 VARIABLES DESCRIPTION:   Input Type (Optional- Default "C") 
  "C"=LOINC Code 
  "I"=LOINC IEN 
VARIABLES: $$STATUS                     TYPE: Output
 VARIABLES DESCRIPTION:   Internal^External Status or Null 
COMPONENT/ENTRY POINT: GETREC(LEXINPT,LEXINTY,.LEXREC)
 COMPONENT DESCRIPTION:   Get LOINC Record Array by Code or IEN 
  
 Example: 
  
 >D GETREC^LEXLR("38553-4",,.LEXREC) 
  ZW LEXREC 
  LEXREC("ADJUSTMENT")="" 
  LEXREC("CHALLENGE")="" 
  LEXREC("CHANGETYPE")="ADD" 
  LEXREC("CLASS")="SERO" 
  LEXREC("CLASSTYPE")="1^LABORATORY" 
  LEXREC("CODE")="38553-4" 
  LEXREC("COMPONENT")="NARCOLEPSY ASSOCIATED AG" 
  LEXREC("DATELASTCHANGED")="3041103^NOV 03, 2004" 
  LEXREC("EXAMPLEUNITS")="" 
  LEXREC("FULLNAME")="NARCOLEPSY ASSOCIATED AG:ACNC:PT:SER/PLAS:ORD" 
  LEXREC("MAPTO")="" 
  LEXREC("METHODTYPE")="" 
  LEXREC("PROPERTY")="ACNC" 
  LEXREC("SCALETYPE")="Ordinal" 
  LEXREC("SHORTNAME")="Narcolepsy Assoc Ag SerPl Ql" 
  LEXREC("STATUS")="" 
  LEXREC("SYSTEM")="SER/PLAS" 
  LEXREC("TIME")="POINT" 
  LEXREC("VACODE")="" 
  LEXREC("VUID")=4681780 
VARIABLES: LEXINPT                      TYPE: Input
 VARIABLES DESCRIPTION:   LOINC Code or IEN 
VARIABLES: LEXINTY                      TYPE: Input
 VARIABLES DESCRIPTION:   Input Type (Optional- Default "C") 
  "C"=LOINC Code 
  "I"=LOINC IEN 
VARIABLES: LEXREC                       TYPE: Output
 VARIABLES DESCRIPTION:   LOINC Record Array subscripts: 
  RECORD("ADJUSTMENT") 
  RECORD("CHALLENGE") 
  RECORD("CHANGETYPE") 
  RECORD("CLASS") 
  RECORD("CLASSTYPE") 
  RECORD("CODE") 
  RECORD("COMPONENT") 
  RECORD("DATELASTCHANGED") 
  RECORD("EXAMPLEUNITS") 
  RECORD("FULLNAME") 
  RECORD("MAPTO") 
  RECORD("METHODTYPE") 
  RECORD("PROPERTY") 
  RECORD("SCALETYPE") 
  RECORD("SHORTNAME") 
  RECORD("STATUS") 
  RECORD("SYSTEM") 
  RECORD("TIME") 
  RECORD("VACODE") 
  RECORD("VUID") 
COMPONENT/ENTRY POINT: $$VERSION()
 COMPONENT DESCRIPTION:   Get LOINC Version 
  
 Example: 
  
 >W $$VERSION^LEXLR() 
  2.14 
VARIABLES: $$VERSION                    TYPE: Output
 VARIABLES DESCRIPTION:   LOINC Version or Null 
COMPONENT/ENTRY POINT: COMLST(LEXCOM,LEXARR)
 COMPONENT DESCRIPTION:   Get List by Component 
  
 Example: 
  
 >D COMLST^LEXLR("VIRUS IDENTIFIED","LEXARRAY") 
  ZW LEXARRAY 
  LEXARRAY("10736-7")="VIRUS IDENTIFIED:PRID:PT:CSF:NOM:MICROSCOPY ELECTRON" 
  LEXARRAY("10737-5")="VIRUS IDENTIFIED:PRID:PT:STL:NOM:MICROSCOPY ELECTRON" 
  LEXARRAY("10738-3")="VIRUS IDENTIFIED:PRID:PT:TISS:NOM:MICROSCOPY ELECTRON" 
  LEXARRAY("10739-1")="VIRUS IDENTIFIED:PRID:PT:XXX:NOM:MICROSCOPY ELECTRON" 
  LEXARRAY("11484-3")="VIRUS IDENTIFIED:PRID:PT:AMN:NOM:VIRUS CULTURE" 
  LEXARRAY("12272-1")="VIRUS IDENTIFIED:PRID:PT:XXX:NOM:IF" 
  LEXARRAY("14451-9")="VIRUS IDENTIFIED:PRID:PT:EYE:NOM:VIRUS CULTURE" 
  LEXARRAY("14452-7")="VIRUS IDENTIFIED:PRID:PT:CVX:NOM:VIRUS CULTURE" 
  LEXARRAY("14453-5")="VIRUS IDENTIFIED:PRID:PT:GENV:NOM:VIRUS CULTURE" 
  LEXARRAY("14454-3")="VIRUS IDENTIFIED:PRID:PT:NOSE:NOM:VIRUS CULTURE" 
  LEXARRAY("14455-0")="VIRUS IDENTIFIED:PRID:PT:PLR:NOM:VIRUS CULTURE" 
  LEXARRAY("14456-8")="VIRUS IDENTIFIED:PRID:PT:PRT:NOM:VIRUS CULTURE" 
  LEXARRAY("14457-6")="VIRUS IDENTIFIED:PRID:PT:UR:NOM:VIRUS CULTURE" 
  LEXARRAY("14458-4")="VIRUS IDENTIFIED:PRID:PT:SPT:NOM:VIRUS CULTURE" 
VARIABLES: LEXCOM                       TYPE: Input
 VARIABLES DESCRIPTION:   Component field (#100) 
VARIABLES: LEXARR                       TYPE: Input
 VARIABLES DESCRIPTION:   Component List Array (Full Global Reference) 
  
 Note: LEXARR is not initialized (ie KILLed) on input 
       The calling application is responsible for 
       initializing the array.  
VARIABLES: @LEXARR@(LEXCODE)            TYPE: Output
 VARIABLES DESCRIPTION:   Component List Array 
  
 @LEXARRAY@(LEXCODE)=Fully Specified Name field (#80) 
COMPONENT/ENTRY POINT: DEPLST(LEXARR)
 COMPONENT DESCRIPTION:   Get Deprecated List 
  
 Example: 
  
 >D DEPLST^LEXLR("LEXARRAY") 
  ZW LEXARRAY  (Partial List Captured) 
  LEXARRAY("1009-0")="DIRECT ANTIGLOBULIN TEST.POLY SPECIFIC 
  REAGENT:ACNC:PT:RBC:ORD" 
  LEXARRAY("10356-4")="MICROSCOPIC OBSERVATION:PRID:PT:STL:NOM:TRICHROME 
  STAIN" 
  LEXARRAY("10440-6")="CD30 AG:ACNC:PT:TISS:ORD:IMMUNE STAIN" 
  LEXARRAY("1052-0")="I (INT) SUBTYPE:ACNC:PT:SER/PLAS~BPU:ORD:AGGL RBC" 
  LEXARRAY("1053-8")="I (INT) SUBTYPE:ACNC:PT:SER/PLAS~DONOR:ORD:AGGL RBC" 
  LEXARRAY("10532-0")="NORAMIODARONE:MCNC:PT:SER/PLAS:QN" 
  LEXARRAY("10537-9")="DOXEPIN+NORDOXEPIN:MCNC:PT:SER/PLAS:QN" 
  LEXARRAY("10538-7")="FLUOXETINE+NORFLUOXETINE:MCNC:PT:SER/PLAS:QN" 
  LEXARRAY("1054-6")="I (INT) SUBTYPE:ACNC:PT:SER:ORD:AGGL RBC" 
  LEXARRAY("1055-3")="I (INT) SUBTYPE:ACNC:PT:RBC~BPU:ORD:AGGL RBC" 
  LEXARRAY("10550-2")="TEMAZEPAM:MCNC:PT:SER/PLAS:QN" 
  LEXARRAY("10554-4")="ACID PHOSPHATASE.PROSTATIC:CCNC:PT:SMPLS:QN" 
  LEXARRAY("10556-9")="ADENOSINE TRIPHOSPHATASE:CCNC:PT:SMPLS:QN" 
  LEXARRAY("10559-3")="CALCIUM:SCNC:PT:SMPLS:QN" 
  LEXARRAY("1056-1")="I (INT) SUBTYPE:ACNC:PT:RBC~DONOR:ORD:AGGL RBC" 
  LEXARRAY("10566-8")="CHORIOGONADOTROPIN:SCNC:PT:SMPLS:QN" 
  LEXARRAY("1057-9")="I (INT) SUBTYPE:ACNC:PT:RBC~PATIENT:ORD:AGGL RBC" 
  LEXARRAY("10575-9")="GAMMA GLUTAMYL TRANSFERASE:CCNC:PT:SMPLS:QN" 
  LEXARRAY("10584-1")="PROTEIN:MCNC:PT:SMPLS:QN" 
  LEXARRAY("10595-7")="SPERMATOZOA:NCNC:PT:SMN:QN" 
  LEXARRAY("10682-3")="HIV 1 RNA:ACNC:PT:SER/PLAS:QN:PROBE AMP" 
  LEXARRAY("10816-7")="MICROSCOPIC OBSERVATION:PRID:PT:TISS:NOM:TOLUIDINE 
  BLUE O STAIN" 
  LEXARRAY("10820-9")="MICROSCOPIC OBSERVATION:PRID:PT:TISS:NOM:WARTHIN 
  STARRY STAIN" 
  LEXARRAY("10821-7")="MICROSCOPIC 
  OBSERVATION:PRID:PT:TISS:NOM:WRIGHT-GIEMSA" 
  LEXARRAY("10852-2")="FUNGUS IDENTIFIED:PRID:PT:BLD:NOM:ROUTINE FUNGAL 
  CULTURE" 
  LEXARRAY("10854-8")="MICROFILARIA SP 
  IDENTIFIED:PRID:PT:BLD:NOM:CONCENTRATION" 
  LEXARRAY("10890-2")="NORMETHSUXIMIDE:MCNC:PT:SER:QN" 
  LEXARRAY("10962-9")="ARTEMISIA TRIDENTATA AB.IGE:ACNC:PT:SER:QN" 
  LEXARRAY("11036-1")="ALDOLASE:CCNC:PT:RBC:QN" 
  LEXARRAY("11049-4")="HYDROXYPROLINE:MCNC:PT:UR:QN" 
  LEXARRAY("1109-8")="L LITTLE B:ACNC:PT:SER:ORD:AGGL RBC" 
  LEXARRAY("11123-7")="PROMYELOCYTES/100 
  LEUKOCYTES:NFR:PT:MAR:QN:MICROSCOPY" 
VARIABLES: LEXARR                       TYPE: Input
 VARIABLES DESCRIPTION:   Deprecated List Array (Full Global Reference) 
  
 Note: LEXARR is not initialized (ie KILLed) on input 
       The calling application is responsible for 
       initializing the array.  
VARIABLES: @LEXARR@(LEXCODE)            TYPE: Output
 VARIABLES DESCRIPTION:   Deprecated List Array 
  
 @LEXARR@(LEXCODE)=Fully Specified Name Field (#80) 
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
SUBSCRIBING PACKAGE: LAB SERVICE

NUMBER: 5548                            IA #: 5548
  DATE CREATED: JUL 28, 2010            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLCSUTL
  NAME: CALCULATE MESSAGE SIZE          ID: HLCSUTL
 GENERAL DESCRIPTION:   IFCAP requests private usage of an HL7 API to determine
 message size.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HLCSUTL
COMPONENT/ENTRY POINT: $$MSGSIZE
 COMPONENT DESCRIPTION:   Return the number of characters in a message, TCP
 type only.  
VARIABLES: HLIENS                       TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of a message in the HL7 MESSAGE
 ADMINISTRATION (#773) file.  
SUBSCRIBING PACKAGE: IFCAP
  DATE ACTIVATED: AUG 17, 2010

NUMBER: 5549                            IA #: 5549
  DATE CREATED: AUG 12, 2010            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RCDPAYER
  NAME: DBIA5549                        ID: RCDPAYER
 GENERAL DESCRIPTION:   This agreement allows by the Third Party Joint Inquiry
 to display contact information from the AR ERA files and also allows a comment
 transaction to be added to the AR bill record if payer contact information is
 available for the bill.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RCDPAYER
KEYWORDS: IBJTTC
KEYWORDS: TPJI
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   
  
 Returns contact data from IB EOB file #361.1 and AR ERA file #344.4 as RESULT
 string 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   
  
 Bill/Claim IEN for file #399 
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   
  
 found_U_website_U_phone_U_fax_U_email_U_ext                  
     
 found=0 if no contact data exists 
  
 found=1 if data is any contact data exists  
COMPONENT/ENTRY POINT: ADD
 COMPONENT DESCRIPTION:   Add a comment transaction (file #433) to the AR bill
 record with brief comment of 'ERA Payer Contact Information'.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   
  
 Bill/Claim IEN for file #399 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: SEP 09, 2010

NUMBER: 5550                            IA #: 5550
  GLOBAL ROOT: DD(                      DATE CREATED: AUG 16, 2010
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            ROUTINE: MAGVRS42
  NAME: VALIDATE FIELDS ON DD FOR REGULAR CROSS REFERENCES
  ID: MAGVRS42
 GENERAL DESCRIPTION:   Read-only access for the ^DD( Global 
  
 Read ^DD(filenum,"IX",fieldnum) to determine whether a field contains a 
 regular cross reference, to optimize ad hoc searches.  
  STATUS: Other                         DURATION: Till Otherwise Agreed
KEYWORDS: FILEMAN
KEYWORDS: DATA DICTIONARY
KEYWORDS: CROSS REFERENCE
KEYWORDS: INDEX
COMPONENT/ENTRY POINT: FINDBYAT
 COMPONENT DESCRIPTION:   The calling routine will invoke entry point 
 FINDBYAT^MAGVRS42((.OUT,FILE,.ATTSARY), whose parameters are defined as 
 follows.  Inputs:  FILE 
           A FileMan file number between 2005 and 2006.999 inclusive.  Must be
 a parent file.  
          .ATTSARY 
           An array of single-valued name-value pairs consisting of the names
 of main-level fields (not multiples) and the values to be searched for.  
 Returns: .OUT 
          The return array (^TMP("DILIST",$J,2)) from a call to FIND^DIC, or an
 appropriate error message indicating that the file is out of range, that no
 cross reference was found to search on, or that no matching entries were
 found.  
  
 FINDBYAT^MAGVRS42 will validate the file against the acceptable range. If the
 file does not fall into the acceptable range, an error will be returned in
 OUT().  
  
 Then, each field name will be validated.  If any field name provided is not
 that of a top-level field on the field, an error will be returned in OUT().  
  
 Otherwise, the field will be checked against ^DD(FILE,"IX") to determine 
 whether it is a regular cross reference.  If it is, and no regular cross 
 reference has yet been selected, this field and value will be used as the 
 cross reference field and value in the call to FIND^DIC.  
  
 If the field is not a cross reference or a cross reference has already been
 selected, FINDBYAT^MAGVRS42 will obtain the global node and piece information
 from the 0 node of the data dictionary definition for the field, validating
 that the field is a top-level field (and returning an error in OUT() if it is
 not), and will add the global node, piece and value to the MUMPS screening
 logic that will be passed to FIND^DIC.  
  
 Then FIND^DIC is called, and either an appropriate error message is returned
 in OUT() if an error was encountered, or the search results from 
 ^TMP("DILIST",$J,2) are returned in OUT().  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   A FileMan file number between 2005 and 2006.999
 inclusive.  Must be a parent file.  
VARIABLES: ATTSARY                      TYPE: Input
 VARIABLES DESCRIPTION:   An array of single-valued name-value pairs consisting
 of the names of main-level fields (not multiples) and the values to be
 searched for.  
VARIABLES: OUT                          TYPE: Output
 VARIABLES DESCRIPTION:   The return array (^TMP("DILIST",$J,2)) from a call to
 FIND^DIC, or an appropriate error message indicating that the file is out of
 range, that no cross reference was found to search on, or that no matching
 entries were found.  
SUBSCRIBING PACKAGE: IMAGING
  DATE ACTIVATED: AUG 17, 2010

NUMBER: 5551                            IA #: 5551
  GLOBAL ROOT: DD(                      DATE CREATED: AUG 19, 2010
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            NAME: RETRIEVE ALL FIELDS IN A FILE  
  ID: DD(
 GENERAL DESCRIPTION:   Read-only access for the ^DD( global 
  
 Read ^DD(FN,"B",FLDNAME,FLDN), where FN is a file number, FLDNAME is a field
 name, and FLDN is a field number.  A function will be created to loop through
 ^DD(FN,"B",FLDNAME,FLDN) to create a list with all fields in a file.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: FILEMAN
KEYWORDS: DATA DICTIONARY
KEYWORDS: FIELDS
SUBSCRIBING PACKAGE: IMAGING

NUMBER: 5552                            IA #: 5552
  DATE CREATED: AUG 24, 2010            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: IFCAP SET DD NODES DURING POST INSTALL
 GENERAL DESCRIPTION:   IFCAP needs to add ID nodes to files 410, 442, and
 443.6 in support of patch PRC*5.1*146.  As KIDS does not have a mechanism to
 transport ID nodes of a files DD without exporting the entire file definition,
 it is requested that for this patch IFCAP be permitted to set the ID node via 
 the post-init routine PRC5146P.  The proposed lines of code are as follows
 (without blank lines): 
  
 S ^DD(410,0,"ID","Z3")="D:$P($G(^(14)),U,2)]"""" EN^DDIOL(""Maximo""_$P(^( 
 14),U,3)_""-""_$P(^(14),U,2),,""?0""),EN^DDIOL("" "",,""!?2"")" 
  
 S ^DD(410.02,0,"ID","Z2")="D:$P($G(@(DIC_+Y_"",9)"")),U,2)]"""" EN^DDIOL(" 
 "Maximo PR Line# ""_$P(^(9),U,2),,""!"")" 
  
 S ^DD(442,0,"ID","Z.04")="N PRCZZ S PRCZZ=$$MAX^PRCMOUTL(+Y,442) D:PRCZZ]" """
 EN^DDIOL(""     ""_PRCZZ,,""?0"")" 
  
 S ^DD(442.01,0,"ID","Z4")="N PRCZZ S PRCZZ=$$PRLINE^PRCMOUTL(D0,+Y,442) D: 
 PRCZZ]"""" EN^DDIOL(PRCZZ,,""!,?9"")" 
  
 S ^DD(443.6,0,"ID","Z.6")="N PRCZZ S PRCZZ=$$MAX^PRCMOUTL(+Y,443.6) D:PRCZ 
 Z]"""" EN^DDIOL(""     ""_PRCZZ,,""?0"")" 
  
 S ^DD(443.61,0,"ID","Z2")="N PRCZZ S PRCZZ=$$PRLINE^PRCMOUTL(DA(1),+Y,443.  6)
 D:PRCZZ]"""" EN^DDIOL(PRCZZ,,""!,?9"")" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DD(
KEYWORDS: ID
KEYWORDS: IDENTIFIER
SUBSCRIBING PACKAGE: IFCAP
  DATE ACTIVATED: AUG 26, 2010

NUMBER: 5553                            IA #: 5553
  DATE CREATED: AUG 24, 2010            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XTHC10
  NAME: HTTP Client                     ID: XTHC10
 GENERAL DESCRIPTION:   This is a HTTP/1.1 client that can request a web page
 from another system and pass the returned data to the calling routine.  
  
 It can make both GET and POST requests.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HTTP
KEYWORDS: HTML
COMPONENT/ENTRY POINT: $$GETURL(url[,xt8flg],xt8rdat,.xt8rhdr[,xt8sdat][,.xt8shd
r])
 COMPONENT DESCRIPTION:   This is the main API. It returns in xt8rdat the
 returned data from the web site.  See full doc's on the web.  http://
 http://vista.url//kernel/apis/index.shtml 
VARIABLES: url                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This is the URL (http://host:port/path) to
 access.  It could be as simple as "www.va.gov".  
VARIABLES: xt8flg                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Request timeout. Default is 5 seconds.  
VARIABLES: xt8rdat                      TYPE: Output
 VARIABLES DESCRIPTION:   (Required) Closed root of the variable where the
 message body is returned. Data is stored in consecutive nodes (numbers
 starting from 1). If a line is longer than 245 characters, only 245 characters
 are stored in the corresponding node. After that, overflow sub-nodes are
 created. For example: 
  @XT8RDAT@(1)="<html>" 
  @XT8RDAT@(2)="<head><title>VistA</title></head>" 
  @XT8RDAT@(3)="<body>" 
  @XT8RDAT@(4)="<p>" 
  @XT8RDAT@(5)="Beginning of a very long line" 
  @XT8RDAT@(5,1)="Continuation #1 of the long line" 
  @XT8RDAT@(5,2)="Continuation #2 of the long line" 
  @XT8RDAT@(5,...)=...  
  @XT8RDAT@(6)="</p>" 
  ...
VARIABLES: xt8rhdr                      TYPE: Output
 VARIABLES DESCRIPTION:   (Required) Reference to a local variable where the
 parsed headers are returned. Header names are converted to upper case and the
 values are left "as is". The root node contains the status line. For example: 
  XT8HDR="HTTP/1.1 200 OK" 
  XT8HDR("ACCEPT-RANGES")="bytes" 
  XT8HDR("CONNECTION")="close" 
  XT8HDR("CONTENT-LENGTH")="16402" 
  XT8HDR("CONTENT-TYPE")="text/html; charset=UTF-8" 
  XT8HDR("DATE")="Thu, 25 Jun 2015 14:43:01 GMT" 
  XT8HDR("ETAG")="a93a2-4012-5180156550680" 
  XT8HDR("LAST-MODIFIED")="Mon, 08 Jun 2015 13:08:26 GMT" 
  XT8HDR("SERVER")="Apache/2.2.15 (CentOS)" 
VARIABLES: xt8sdat                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Closed root of a variable containing the
 body of the request message. Data should be formatted as in variable XT8RDAT
 above. If this parameter is defined, not empty, and the referenced array
 contains data then the POST request is generated. Otherwise, the GET request
 is sent.  
VARIABLES: xt8shdr                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Reference to a local variable containing
 header values, which will be added to the request. For example: 
  XT8SHDR("CONTENT-TYPE")="text/html" 
VARIABLES: returns                      TYPE: Output
 VARIABLES DESCRIPTION:   
   Success: HTTP_Status_Code^Description 
            Common HTTP status codes returned: 
             200  OK 
             301  Moved Permanently 
             400  Bad Request 
             401  Unauthorized 
             404  Not Found 
             407  Proxy Authentication Required 
             408  Request Time-out 
             500  Internal Server Error 
             505  HTTP Version not supported 
   Fail:   -1^Error Descriptor (additional error information may be found in
 the VistA error trap or ^XTER in programmer mode) 
  DATE ACTIVATED: JUN 26, 2015

NUMBER: 5554                            IA #: 5554
  DATE CREATED: AUG 24, 2010            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XTHCURL
  NAME: HTTP Client Helper              ID: XTHCURL
 GENERAL DESCRIPTION:   These are some helper functions for the HTTP/1.1
 Client.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HTTP
KEYWORDS: HTML
COMPONENT/ENTRY POINT: $$MAKEURL(host[,port][,path][,query])
 COMPONENT DESCRIPTION:   Creates a URL from components.  
  
   Example: 
   S host="http://www.map.com" 
   S path="api/staticmap" 
   S query("center")="clay+st.,Oakland,CA" 
   S query("sensor")="false" 
   W $$MAKEURL^XTHCURL(host,,path,.query) 
 http://www.map.com/api/staticmap?center=clay%2Bst.%2COakland%2CCA&sensor=f 
 alse 
VARIABLES: host                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The FQDN or IP address of the system to
 connect to.  
VARIABLES: port                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The port to use. Default is port xx for
 http or port xxx for https.  
VARIABLES: path                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The path to the web page on the called
 server.  
VARIABLES: query                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) An array of query parameters.  
VARIABLES: returns                      TYPE: Output
 VARIABLES DESCRIPTION:   
  Success: Normalized path (see example above) 
  Fail: -1^Host not defined (if missing host variable) 
COMPONENT/ENTRY POINT: $$ENCODE(str)
 COMPONENT DESCRIPTION:   Encodes the query string. Used by MAKEURL.  
   Example: 
   W $$ENCODE^XTHCURL("1301+clay+st.,Oakland,CA") 
   1301%2Bclay%2Bst.%2COakland%2CCA 
VARIABLES: str                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) String of data to be encoded.  
VARIABLES: returns                      TYPE: Output
 VARIABLES DESCRIPTION:   Success: Encoded query string Fail: -1^String not
 defined (if missing str variable) 
COMPONENT/ENTRY POINT: $$PARSEURL(url,.host,.port,.path)
 COMPONENT DESCRIPTION:   Parses a URL string into host, port, and path (path
 includes query string).  
   Example: 
  D PARSEURL^XTHCURL("http://url:xxxx/tpl/PKG",.ZH,.ZP,.ZA) 
  W ZH,!,ZP,!,ZA 
  DNS 
  xxxx (port) 
  /tpl/PKG 
VARIABLES: url                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) URL string to be parsed.  
VARIABLES: host                         TYPE: Output
 VARIABLES DESCRIPTION:   (Required) Reference to variable where host name is
 to be returned.  
VARIABLES: port                         TYPE: Output
 VARIABLES DESCRIPTION:   (Required) Reference to variable where port is to be
 returned.  
VARIABLES: path                         TYPE: Output
 VARIABLES DESCRIPTION:   (Required) Reference to variable where path string is
 to be returned.  
VARIABLES: returns                      TYPE: Output
 VARIABLES DESCRIPTION:   
  Success: 0 
  Fail: -1^Error Description 
  DATE ACTIVATED: JUN 26, 2015

NUMBER: 5555                            IA #: 5555
  DATE CREATED: AUG 24, 2010            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XTHCUTL
  NAME: HTTP Client Helper              ID: XTHCUTL
 GENERAL DESCRIPTION:   Helper function for the HTTP/1.1 Client.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HTTP
KEYWORDS: HTML
COMPONENT/ENTRY POINT: $$DECODE(str)
 COMPONENT DESCRIPTION:   Decodes one string replacing 
                         &lt; with < 
                         &gt; with > 
                         &amp; with & 
                         &nbsp; with " " 
                         &apos; with ' 
                         &quot; with " 
                         &#65; with A.  Example: W
 $$DECODE^XTHCUTL("1301%2Bclay%2Bst.%2COakland%2CCA") 
 1301%2Bclay%2Bst.%2COakland%2CCA 
VARIABLES: str                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) String to be decoded.  
VARIABLES: returns                      TYPE: Output
 VARIABLES DESCRIPTION:   
  Success: Decoded string.  
  Fail: -1^String not defined (if missing str variable) 
  DATE ACTIVATED: JUN 26, 2015

NUMBER: 5556                            IA #: 5556
  DATE CREATED: AUG 27, 2010            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: MAG4 DATA FROM IMPORT QUEUE
  REMOTE PROCEDURE: MAG4 DATA FROM IMPORT QUEUE
 GENERAL DESCRIPTION:   This call returns the Array of Data from the Import
 Queue, given a QUEUE Number. Can be called from Delphi and 'M'.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER

NUMBER: 5557                            IA #: 5557
  DATE CREATED: AUG 27, 2010            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: MAG4 INDEX GET EVENT
 GENERAL DESCRIPTION:   This call will return an array of entries from the
 IMAGE INDEX FOR PROCEDURE/EVENT (#2005.85) file based on the input parameters
 CLS (Class) and SPEC (Specialty/subspecialty). When images are displayed, it
 is desirable to limit the list of presented images to only those that are 
 likely to be relevant in the current context.  
      
 This procedure accepts an "image category" (either an IEN or the name of a
 category) and returns all "image events" that belong to that category.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER

NUMBER: 5558                            IA #: 5558
  DATE CREATED: AUG 27, 2010            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: MAG4 INDEX GET ORIGIN
 GENERAL DESCRIPTION:   This call will return an array of the ORIGIN INDEX
 (field #45) from the IMAGE (#2005) file.  The result array includes all ORIGIN
 codes and abbreviations.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER

NUMBER: 5559                            IA #: 5559
  DATE CREATED: AUG 27, 2010            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: MAG4 INDEX GET SPECIALTY
 GENERAL DESCRIPTION:   This call will return an array of entries from the
 IMAGE INDEX FOR  SPECIALTY/SUBSPECIALTY (#2005.84) file based on the input
 parameters CLS (Class) and EVENT (Procedure/Event). When images are displayed,
 it is desirable to limit the list of presented images to only those that are 
 likely to be relevant in the current context.  
   
 This procedure accepts an "image category" (either an IEN or the name of a
 category) and returns all "(sub)specialties" that generate images in that
 category.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER

NUMBER: 5560                            IA #: 5560
  DATE CREATED: AUG 27, 2010            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: MAG4 INDEX GET TYPE
 GENERAL DESCRIPTION:   Used to filter out those image types that belong to a
 given image category (Class). When images are displayed, it is desirable to
 limit the list of presented images to only those that are likely to be
 relevant in the current context.  
   
 This procedure accepts an "image class" (either an IEN or the name of a class)
 and returns all "image types" that belong to that class.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER

NUMBER: 5561                            IA #: 5561
  DATE CREATED: AUG 27, 2010            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: MAGN PATIENT HAS PHOTO
 GENERAL DESCRIPTION:   Checks if photo image exists for a patient.  Returns 0
 if no photo or the date/time (Fileman format) of the most recent photo.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER

NUMBER: 5562                            IA #: 5562
  DATE CREATED: AUG 27, 2010            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: MAG4 GET SUPPORTED EXTENSIONS
  REMOTE PROCEDURE: MAG4 GET SUPPORTED EXTENSIONS
 GENERAL DESCRIPTION:   Returns a list of supported file extensions used in
 Imaging from the IMAGE FILE TYPES (#2005.021) file.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER

NUMBER: 5563                            IA #: 5563
  DATE CREATED: AUG 27, 2010            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: MAG3 CPRS TIU NOTE              REMOTE PROCEDURE: MAG3 CPRS TIU NOTE
 GENERAL DESCRIPTION:   Returns a list of all images for a TIU document.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER

NUMBER: 5564                            IA #: 5564
  DATE CREATED: AUG 27, 2010            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: MAGG CAPTURE USERS
 GENERAL DESCRIPTION:   This call will find users that have captured images in
 a date range. The list of users can be filtered by the FLAGS parameter. The
 Flags Parameter can contain 'C' for images captured on the Capture Workstation
 and/or 'I' for images captured throught the Import API. If the parameter is
 null it defaults to 'CI'.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER

NUMBER: 5565                            IA #: 5565
  DATE CREATED: AUG 27, 2010            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: MAGQBUT3                     NAME: IMAGING QUEUE STATUS
  ID: MAGQBUT3
 GENERAL DESCRIPTION:   This API will return the imaging queue status based on
 a Queue Number or Tracking ID.  
      S X=$$STATUS^MAGQBUT3(Queue Number)  
      S X=$$STATUS^MAGQBUT3(Tracking ID)  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: STATUS(PARAM)
 COMPONENT DESCRIPTION:   Returns 0^error message, 1^Success or 2^Pending 
VARIABLES: PARAM                        TYPE: Input
 VARIABLES DESCRIPTION:   Contains either a Queue Number or Tracking ID 
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER

NUMBER: 5566                            IA #: 5566
  DATE CREATED: AUG 30, 2010            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        NAME: Registration for FBCNH Reports
 GENERAL DESCRIPTION:   >The CAPRI application needs access to execute the
 following FBCNH components so they can be executed from the CAPRI GUI
 application via a DVBA namespace RPC.  This Integration Agreement covers the
 use of these components.  Fee Basis cannot modify these components without
 first notifying the CAPRI develoopment team and giving them ample time to make
 any necessary changes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AMIE
KEYWORDS: FBCNH
KEYWORDS: CAPRI
COMPONENT/ENTRY POINT: FBNHDEC
 COMPONENT DESCRIPTION:   FBCNH Display Episode of Care 
VARIABLES: DFN                          TYPE: Both
 VARIABLES DESCRIPTION:   IEN in PATIENT #2 FILE 
VARIABLES: IFN                          TYPE: Both
 VARIABLES DESCRIPTION:   IEN in FEE CNH ACTIVITY (#162.3) file 
COMPONENT/ENTRY POINT: FBNHROS/START
 COMPONENT DESCRIPTION:   FBCNH PRINT ROSTER 
COMPONENT/ENTRY POINT: FBNHAMIE/START
 COMPONENT DESCRIPTION:   FBCNH report of Admissions/Discharges 
VARIABLES: BEGDATE                      TYPE: Both
 VARIABLES DESCRIPTION:   Start date in FM format 
VARIABLES: ENDDATE                      TYPE: Both
 VARIABLES DESCRIPTION:   End date in FM format 
COMPONENT/ENTRY POINT: FBNHAMI2/START
 COMPONENT DESCRIPTION:   FBCNH Admissions > 90 Days 
VARIABLES: FBDT                         TYPE: Both
 VARIABLES DESCRIPTION:   effective date in FM format 
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   The following Fee Basis FBCNH components will be
 executed from DVBA namespace RPC's.  
  DATE ACTIVATED: OCT 12, 2010

NUMBER: 5567                            IA #: 5567
  DATE CREATED: SEP 01, 2010            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XPDPROT
  NAME: XPDPROT                         ID: XPDPROT
 GENERAL DESCRIPTION:   A set of calls and extrinsic functions that can be used
 to manage protocols in the PROTOCOL file during a KIDS install.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: KIDS
KEYWORDS: PROTOCOLS
COMPONENT/ENTRY POINT: ADD
 COMPONENT DESCRIPTION:   ADD(PARENT,CHILD,MNEMONIC,SEQUENCE) is an extrinsic
 function to add the CHILD protocol to the PARENT protocol ITEM multiple.  
   Returns 1 for success, 0 for failure.  
  
VARIABLES: PARENT                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The name of the protocol you want to add
 the CHILD protocol to.  
  
VARIABLES: CHILD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The name of the protocol you are adding to
 the PARENT protocol.  
  
VARIABLES: MNEMONIC                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The value you want added to the MNEMONIC
 field in the ITEM multiple for the CHILD in the PARENT protocol.  
  
VARIABLES: SEQUENCE                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The value you want added to the SEQUENCE
 field in the ITEM multiple for the CHILD in the PARENT protocol.  
  
COMPONENT/ENTRY POINT: DELETE
 COMPONENT DESCRIPTION:   DELETE(PARENT,CHILD) is an extrinsic function to
 delete the CHILD protocol from the ITEM multiple of the PARENT protocol.  
  Returns 1 for success, 0 for failure.  
  
VARIABLES: PARENT                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The name of the protocol you want to
 delete the CHILD protocol from.  
  
VARIABLES: CHILD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The name of the protocol you want to
 delete from the PARENT protocol.  
  
COMPONENT/ENTRY POINT: RENAME
 COMPONENT DESCRIPTION:   RENAME(OLD,NEW) is used to rename a protocol.  
  
VARIABLES: OLD                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The current name of the protocol.  
  
VARIABLES: NEW                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The new name of the protocol.  
  
COMPONENT/ENTRY POINT: LKPROT
 COMPONENT DESCRIPTION:   LKPROT(PROTOCOL) is an extrinsic function that
 returns the internal entry number of the PROTOCOL.  
  
  
VARIABLES: PROTOCOL                     TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The name of the protocol you want to
 lookup.  
  
COMPONENT/ENTRY POINT: OUT
 COMPONENT DESCRIPTION:   OUT(PROTOCOL,TEXT) is used to create or delete an Out
 of Order message for a protocol.  
  
VARIABLES: PROTOCOL                     TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The name of the protocol you want to
 assign the Out of Order TEXT.  
  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The text of message to place in the OUT OF
 ORDER MESSAGE field for the PROTOCOL.  If set to null, the field will be
 deleted.  
  
COMPONENT/ENTRY POINT: TYPE
 COMPONENT DESCRIPTION:   TYPE(PROTOCOL) is an extrinsic function that returns
 value for the PROTOCOL's TYPE field (#4) in the PROTOCOL file (#101).  
  
VARIABLES: PROTOCOL IEN                 TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The internal entry number (IEN) of the
 protocol.  
  
  
COMPONENT/ENTRY POINT: FIND
 COMPONENT DESCRIPTION:   FIND(RESULT,PROTOCOL) is used to find all parents for
 the PROTOCOL and return the list in the RESULT array.  
  RESULT(0)=number of parents found or -1^error message 
  RESULT(ien)=protocol name 
  
VARIABLES: RESULT                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The array to return the results, passed by
 reference.  
  RESULT(0)=number of parents found or -1^error message 
  RESULT(ien)=protocol name 
  
  
VARIABLES: PROTOCOL                     TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The name of the protocol you want find the
 parents of.  
  
  DATE ACTIVATED: NOV 11, 2010

NUMBER: 5568                            IA #: 5568
  FILE NUMBER: 2005.82                  GLOBAL ROOT: MAG(2005.82,
  DATE CREATED: SEP 08, 2010            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: File
  NAME: IMAGE INDEX FOR CLASS file 2005.82
  ID: MAG(2005.82,
 GENERAL DESCRIPTION:   The MAG4 INDEX GET TYPE remote procedure requires a
 Class parameter.  The IMAGE INDEX FOR CLASS file (#2005.82) contains the list
 of available class types for imaging and will be read using FileMan.  
  
  ^MAG(2005.82,D0,0) 
     .01    NAME           0;1  Read with Fileman 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER

NUMBER: 5569                            IA #: 5569
  FILE NUMBER: 9999999.64               DATE CREATED: SEP 09, 2010
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: File
  NAME: HEALTH FACTORS FOR PADP
 GENERAL DESCRIPTION:   As part of my C3-C1 Admission Assesment (PADP), I would
 like to add ONS AA* and ONS RA* health factors to the Health Factor file.  
  STATUS: Withdrawn
KEYWORDS: HEALTH FACTORS
KEYWORDS: ADMISSION ASSESSMENT
KEYWORDS: NUPA

NUMBER: 5570                            IA #: 5570
  DATE CREATED: SEP 14, 2010
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSDSAPM
  NAME: DBIA 5570                       ID: PSSDSAPM
 GENERAL DESCRIPTION:   This entry point will return the best entry from the
 DRUG (#50) File to use for order checks (Drug Interaction, Duplicate Therapy
 and Dosing), when there is only a Pharmacy Orderable Item associated with the 
 medication order. It will consider package, the match to National Drug File,
 and whether the matched entry in the VA PRODUCT (#50.68) File has a GCNSEQNO
 number.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$DRG(PSSNBOI,PSSNBPK,PSSNBOR)
 COMPONENT DESCRIPTION:   This entry point will return the best entry from the
 DRUG (#50) File for Drug Interaction and Duplicate Therapy order checks, and
 Dosing checks, when there is only a Pharmacy Orderable Item associated with
 the order.  
VARIABLES: PSSNBOI                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the PHARMACY
 ORDERABLE ITEM (#50.7) File.  
VARIABLES: PSSNBPK                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the package associated with the order. It can
 be one of four values, "O" for Outpatient, "I" for IV, "U" for Unit Dose, "X"
 for Non-VA Medications.  
VARIABLES: PSSNBOR                      TYPE: Input
 VARIABLES DESCRIPTION:   This should only be passed in from CPRS. It should be
 '1' if this call is for the Drug Interaction and Duplicate Therapy order
 checks, or '2' if this call is for the Dosing order checks.  
VARIABLES: $$DRG                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the DRUG (#50) File entry that should be used
 for the order checks. It is a five piece variable, using the ";" as the
 delimiter. If a Drug is found that is matched to National Drug File, then
 piece one will be the internal entry number from the DRUG (#50) File, piece 2
 will be the internal entry number from the VA GENERIC (#50.6) File, and piece
 3 will be the GCNSEQNO number if there is a GCNSEQNO number associated with
 the VA PRODUCT (#50.68) File entry. If the VA Product does not have a GCNSEQNO 
 number associated with it, then piece 3 will be null. Piece 4 will be returned
 as '1' if the call is being made from Computerized Patient Record System
 (CPRS) for the Drug Interaction and Duplicate Therapy checks, and no drug is
 returned, or a drug is returned and there is an Active Supply matched to the
 Orderable Item, indicating CPRS should also do the duplicate Supply check.
 Piece 5 is returned as '1' if the call is being made from CPRS for the Drug
 Interaction and Duplicate Therapy checks, and they should display the error
 message for all order checks and not do the Dosing Order check.  
                             
 If a Drug is returned that is not matched to National Drug File, piece one 
 will be the internal entry number from the DRUG (#50) File, piece 2 and piece
 3 will be null. If no Drug is found, piece 1 will be 0, piece 2 and piece 3
 will be null.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: JUN 11, 2015

NUMBER: 5571                            IA #: 5571
  FILE NUMBER: 2                        GLOBAL ROOT: DPT
  DATE CREATED: OCT 21, 2010            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: DBIA5571                        ID: DPT
GLOBAL REFERENCE: DPT(D0,0
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: .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: Both R/W w/Fileman
FIELD NUMBER: .091                      FIELD NAME: REMARKS
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .092                      FIELD NAME: PLACE OF BIRTH [CITY]
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .093                      FIELD NAME: PLACE OF BIRTH [STATE]
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(DO,.11
FIELD NUMBER: .111                      FIELD NAME: STREET ADDRESS [LINE1]
  LOCATION: .11;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .1112                     FIELD NAME: ZIP+4
  LOCATION: .11;12                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .112                      FIELD NAME: STREET ADDRESS [LINE2]
  LOCATION: .11;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .113                      FIELD NAME: STREET ADDRESS [LINE3]
  LOCATION: .11;3                       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: .117                      FIELD NAME: COUNTY
  LOCATION: .11;7                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .1173                     FIELD NAME: COUNTRY
  LOCATION: .11;10                      ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.13
FIELD NUMBER: .131                      FIELD NAME: PHONE NUMBER [RESIDENCE]
  LOCATION: .13;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .133                      FIELD NAME: EMAIL ADDRESS
  LOCATION: .13;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .134                      FIELD NAME: PHONE NUMBER [CELLULAR]
  LOCATION: .13;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .135                      FIELD NAME: PAGER NUMBER
  LOCATION: .13;5                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.21
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 [LINE1]
  LOCATION: .21;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .214                      FIELD NAME: K-STREET ADDRESS [LINE2]
  LOCATION: .21;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .215                      FIELD NAME: K-STREET ADDRESS [LINE 3]
  LOCATION: .21;5                       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: .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
GLOBAL REFERENCE: DPT(D0,.211
FIELD NUMBER: .2191                     FIELD NAME: K2-NAME OF SECONDARY NOK
  LOCATION: .211;1                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .2192                     FIELD NAME: K2-RELATIONSHIP TO PATIENT
  LOCATION: .211;2                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .2193                     FIELD NAME: K2-STREET ADDRESS [LINE 1]
  LOCATION: .211;3                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .2194                     FIELD NAME: K2-STREET ADDRESS [LINE 2]
  LOCATION: .211;4                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .2195                     FIELD NAME: K2-STREET ADDRESS [LINE 3]
  LOCATION: .211;5                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .2196                     FIELD NAME: K2-CITY
  LOCATION: .211;6                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .2197                     FIELD NAME: K2-STATE
  LOCATION: .211;7                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .2199                     FIELD NAME: K2-PHONE NUMBER
  LOCATION: .211;9                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .211011                   FIELD NAME: K2-WORK PHONE NUMBER
  LOCATION: .211;11                     ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.22
FIELD NUMBER: .2201                     FIELD NAME: E-ZIP+4
  LOCATION: .22;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .2203                     FIELD NAME: K2-ZIP+4
  LOCATION: .22;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .2204                     FIELD NAME: E2-ZIP+4
  LOCATION: .22;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .2207                     FIELD NAME: K-ZIP+4
  LOCATION: .22;7                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(DO,.24
FIELD NUMBER: .2403                     FIELD NAME: MOTHER'S MAIDEN NAME
  LOCATION: .24;3                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.29
FIELD NUMBER: .293                      FIELD NAME: RATED INCOMPETENT?
  LOCATION: .29;12                      ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.3
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: .3025                     FIELD NAME: RECEIVING VA DISABILITY?
  LOCATION: .3;11                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.31
FIELD NUMBER: .313                      FIELD NAME: CLAIM NUMBER
  LOCATION: .31;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .314                      FIELD NAME: CLAIM FOLDER LOCATION
  LOCATION: .31;4                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.32
FIELD NUMBER: .323                      FIELD NAME: PERIOD OF SERVICE
  LOCATION: .32;3                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.33
FIELD NUMBER: .33011                    FIELD NAME: E-WORK PHONE NUMBER
  LOCATION: .33;11                      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: .335                      FIELD NAME: E-STREET ADDRESS [LINE 3]
  LOCATION: .33;5                       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: .339                      FIELD NAME: E-PHONE NUMBER
  LOCATION: .33;9                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,331
FIELD NUMBER: .331011                   FIELD NAME: E2-WORK PHONE NUMBER
  LOCATION: .331;11                     ACCESS: Both R/W w/Fileman
FIELD NUMBER: .3311                     FIELD NAME: E2-NAME OF SECONDARY CONTACT
  LOCATION: .331;1                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .3312                     FIELD NAME: E2-RELATIONSHIP TO PATIENT
  LOCATION: .331;2                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .3313                     FIELD NAME: E2-STREET ADDRESS [LINE 1]
  LOCATION: .331;3                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .3314                     FIELD NAME: E2-STREET ADDRESS [LINE 2]
  LOCATION: .331;4                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .3315                     FIELD NAME: E2-STREET ADDRESS [LINE 3]
  LOCATION: .331;5                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .3316                     FIELD NAME: E2-CITY
  LOCATION: .331;6                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .3317                     FIELD NAME: E2-STATE
  LOCATION: .331;7                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .3319                     FIELD NAME: E2-PHONE NUMBER
  LOCATION: .331;9                      ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.36
FIELD NUMBER: .361                      FIELD NAME: PRIMARY ELIGIBILITY CODE
  LOCATION: .36;1                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.362
FIELD NUMBER: .3626                     FIELD NAME: AMOUNT OF GI INSURANCE
  LOCATION: .362;6                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .36205                    FIELD NAME: RECEIVING A&A BENEFITS?
  LOCATION: .362;12                     ACCESS: Both R/W w/Fileman
FIELD NUMBER: .36215
  FIELD NAME: RECEIVING HOUSEBOUND BENEFITS?
  LOCATION: .362;13                     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: .36265                    FIELD NAME: GI INSURANCE POLICY?
  LOCATION: .362;17                     ACCESS: Both R/W w/Fileman
FIELD NUMBER: .36295                    FIELD NAME: TOTAL ANNUAL VA CHECK AMOUNT
  LOCATION: .362;20                     ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,TYPE
FIELD NUMBER: 391                       FIELD NAME: TYPE
  LOCATION: TYPE;1                      ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,MPI
FIELD NUMBER: 991.01                    FIELD NAME: INTEGRATION CONTROL NUMBER
  LOCATION: MPI;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 991.02                    FIELD NAME: ICN CHECKSUM
  LOCATION: MPI;2                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,MPIMB
FIELD NUMBER: 994                       FIELD NAME: MULTIPLE BIRTH INDICATOR
  LOCATION: MPIMB;1                     ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,VET
FIELD NUMBER: 1901                      FIELD NAME: VETERAN (Y/N)?
  LOCATION: VET;1                       ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   
  
 The PATIENT file contains all the patients followed by the medical center/ 
 Outpatient clinic.  At a minimum each patient entry must have a NAME, DATE OF
 BIRTH and SOCIAL SECURITY NUMBER.  This file contains most of the demographic
 data for a patient.  Single Patient Registration will add/edit a subset of the
 fields in the Patient file.  A complete list of those fields is provided.  
  
 With the introduction of Single Patient Registration, Patient records for DOD
 personal and recruits will also be added to the VistA Patient File using the
 same Single Patient registration RPCs. In addition, VistA patients will be
 added to the CHCS Patient File #2.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   Patient Single Registration adds and updates records in
 the Patient File #2, using standard FileMan APIs.  Data to do this is passed
 via the RPC  'JVDG FILE'.  Patient Data will be retrieved by using the RPC
 'JVDG GETS'.  

NUMBER: 5572                            IA #: 5572
  DATE CREATED: OCT 25, 2010            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPDPU
  NAME: IBNCPDPU                        ID: IBNCPDPU
 GENERAL DESCRIPTION:   This ICR provides access to data located in the GROUP
 INSURANCE PLAN file #355.3 that will allow the ECME package to determine the
 NCPDP version of a Payer Sheet.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PLANEPS
KEYWORDS: IBNCPDPU
COMPONENT/ENTRY POINT: PLANEPS
 COMPONENT DESCRIPTION:   This function returns a comma separated list of Payer
 Sheets for a specific GROUP INSURANCE PLAN file #355.3 IEN.  A successful
 return will be formatted as follows: 
   1^B1,B2,B3,B4 
     Where: B1 = Billing Payer Sheet 
            B2 = Reversal Payer Sheet 
            B3 = Rebill Payer Sheet 
            B4 = Eligibility Payer Sheet 
  
 An unsuccessful call will return 0 (zero).  
VARIABLES: IBPL                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN to the GROUP INSURANCE PLAN file #355.3.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: JAN 18, 2011

NUMBER: 5573                            IA #: 5573
  DATE CREATED: OCT 28, 2010            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCEMOA
  NAME: User OK as Certifier for a 1358?
  ID: PRCEMOA
 GENERAL DESCRIPTION:   This agreement allows subscribers to call an API
 UOKCERT^PRCEMOA.  This API verifies that a person would not violate
 segregation of duty when certifying an invoice associated with a 1358
 miscellaneous obligation by ensuring that they have not previously acted as a
 requestor, approver, or obligator on that 1358.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 1358 Miscellaneous Obligation
COMPONENT/ENTRY POINT: UOKCERT(PRCOUT,PRC1358,PRCPER)
VARIABLES: PRCOUT                       TYPE: Both
 VARIABLES DESCRIPTION:   Output variable, passed by reference. PRCOUT will be
 set equal to one of the following values: 
  
 =1       if person can certify an invoice 
          associated with the 1358 
  
 =0^text  if person not OK as certifier due to 
          segregation of duties where text is of 
          the form You are the 'role' of 'an 
          event'.  
          e.g. "You are the Requestor of an 
          Adjustment to the 1358." 
  
 =E^text  if problem with inputs or the 1358 data 
          where list of possible error text is: 
            The 1358 number was not specified.  
            The Person was not specified.  
            The 1358 was not found in file 442.  
            The document is not a 1358.  
            The PRIMARY 2237 value is missing.  
VARIABLES: PRC1358                      TYPE: Input
 VARIABLES DESCRIPTION:   1358 obligation number (e.g. 688-C15001) - Purchase
 Order Number (#.01) field of the PROCUREMENT & ACCOUNTING TRANSACTIONS (#442)
 file.  
VARIABLES: PRCPER                       TYPE: Input
 VARIABLES DESCRIPTION:   Person attempting to certify an invoice associated
 with the 1358 - IEN of user in the NEW PERSON (#200) file.  
SUBSCRIBING PACKAGE: FEE BASIS
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JAN 11, 2011

NUMBER: 5574                            IA #: 5574
  DATE CREATED: OCT 28, 2010            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCEMOA
  NAME: Events (and Actors) for a 1358  ID: PRCEMOA
 GENERAL DESCRIPTION:   This agreement allows subscribers to call an API
 $$EV1358^PRCEMOA. This API provides information on the events (initial
 obligation and increase/decrease adjustments) and IFCAP actors (requestor,
 approving official, obligator) for a specified 1358 miscellaneous obligation.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 1358 Miscellaneous Obligation
COMPONENT/ENTRY POINT: EV1358(PRC1358,PRCARR)
VARIABLES: PRC1358                      TYPE: Input
 VARIABLES DESCRIPTION:   1358 obligation number (e.g. 688-C15001) - Purchase
 Order Number (#.01) field of the PROCUREMENT & ACCOUNTING TRANSACTIONS (#442)
 file.  
VARIABLES: PRCARR                       TYPE: Both
 VARIABLES DESCRIPTION:   (Optional) results array name, passed by value,
 closed root, default value is "^TMP(""PRC1358"",$J)".  The root must NOT be a
 variable name newed by this API: 
   - PRCARR 
   - PRCODI 
   - PRCLIST 
   - PRCRET 
   - PRC1358 
   - PRC410P 
   - PRC442 
  
  
 The PRCARR array is initialized and populated as 
  
 PRCARR(DATE/TIME,EVENT)=REQUESTOR^APPROVER^OBLIGATOR 
  
   DATE/TIME - is a FileMan Date/Time (internal 
               format) when the transaction 
               was obligated 
       EVENT - is O (OBLIGATE), or A (ADJUST) 
   REQUESTOR - is a NEW PERSON (#200) file IEN 
               or null value 
    APPROVER - is a NEW PERSON (#200) file IEN 
               or null value 
   OBLIGATOR - is a NEW PERSON (#200) file IEN 
               or null value 
   
     Example: 
      ^TMP("PRCS1358",$J,3101005.091223,"O")=134^5432^43 
      ^TMP("PRCS1358",$J,3101007.101501,"A")=134^9473^4677 
VARIABLES: $$EV1358                     TYPE: Output
 VARIABLES DESCRIPTION:   Return value is '1' or 'E^text' where: 
  
 = 1       if no problems 
  
 = E^text  if problem with inputs or 1358 data 
             List of possible errors: 
               The array name is invalid.  
               The 1358 number was not specified.  
               The 1358 was not found in file 442.  
               The document is not a 1358.  
               The PRIMARY 2237 value is missing.  
SUBSCRIBING PACKAGE: FEE BASIS
  DATE ACTIVATED: JAN 11, 2011

NUMBER: 5575                            IA #: 5575
  FILE NUMBER: 9002313.19               GLOBAL ROOT: BPS(9002313.19
  DATE CREATED: NOV 04, 2010            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA5575
  ID: BPS(9002313.19
 GENERAL DESCRIPTION:   Integrated Billing (IB) is using a FileMan look-up into
 the BPS NCPDP PATIENT RELATIONSHIP CODE (#9002313.19) in order to ask the user
 to choose a valid ECME Patient Relationship code to perform a NCPDP
 Eligibility inquiry.  
  STATUS: Active
KEYWORDS: BPS
KEYWORDS: NCPDP
KEYWORDS: RELATIONSHIP
KEYWORDS: ELIGIBILITY
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   IB is performing a FileMan lookup into file#
 9002313.19.  
  DATE ACTIVATED: NOV 12, 2010

NUMBER: 5576                            IA #: 5576
  DATE CREATED: NOV 08, 2010            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: BPSNCPD9
  NAME: BPSNCPD9                        ID: BPSNCPD9
  STATUS: Active
KEYWORDS: BPS
KEYWORDS: ECME
KEYWORDS: ELIGIBILITY
COMPONENT/ENTRY POINT: $$EN(DFN,BPSARRAY)
 COMPONENT DESCRIPTION:   Integrated Billing (IB) calls this function in order
 to request that an Eligibility Verification transaction be created per the
 NCPCP specifications.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: BPSARRAY                     TYPE: Input
 VARIABLES DESCRIPTION:   Array to input data with the following subscript
 values: 
     "PLAN"        - IEN to the GROUP INSURANCE 
                     PLAN (#355.3) file 
     "DOS"         - Date of Service 
     "IEN"         - Prescription IEN 
     "FILL NUMBER" - Prescription Fill Number 
     "REL CODE"    - Relationship Code 
     "PERSON CODE" - Person Code 
VARIABLES: $$EN                         TYPE: Output
 VARIABLES DESCRIPTION:   Return value with two '^' delimited pieces: 
     Piece 1 - 0: Not submitted or 1: Submitted 
     Piece 2 - Message 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: SEP 09, 2011

NUMBER: 5577                            IA #: 5577
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  ROUTINE: LRVER4                       NAME: DBIA-5577
  ID: LRVER4                            STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: MAR 10, 2011
COMPONENT/ENTRY POINT: RANGECHK
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5578                            IA #: 5578
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  ROUTINE: LRVERA                       NAME: DBIA-5578
  ID: LRVERA                            STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: MAR 10, 2011
COMPONENT/ENTRY POINT: CMTDSP
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5579                            IA #: 5579
  FILE NUMBER: 52.53                    GLOBAL ROOT: PS(52.53,
  DATE CREATED: NOV 18, 2010            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: OPAI ACCESS TO 52.53
  ID: PS(52.53,
 GENERAL DESCRIPTION:   This ICR grants access to the automated dispensing
 devices defined in the PHARMACY AUTOMATED DISPENSING DEVICES file (#52.53).  
  
  STATUS: Active
KEYWORDS: OPAI
KEYWORDS: ADD
KEYWORDS: DNS
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  DATE ACTIVATED: NOV 22, 2010

NUMBER: 5580                            IA #: 5580
  FILE NUMBER: 53.79                    GLOBAL ROOT: PSB(53.79,
  DATE CREATED: NOV 18, 2010            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Private                        TYPE: File
  NAME: DSS extract access              ID: PSB(53.79,
GLOBAL REFERENCE: PSB(53.79,
FIELD NUMBER: .01                       FIELD NAME: PATIENT NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This includes global reads of "AADT", "AOIP", "B" cross
 references 
FIELD NUMBER: .02                       FIELD NAME: PATIENT LOCATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: PATIENT DIVISION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: ENTERED DATE/TIME
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: ACTION DATE/TIME
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: .08                       FIELD NAME: ADMINISTRATION MEDICATION
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: .09                       FIELD NAME: ACTION STATUS
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: .11                       FIELD NAME: ORDER REFERENCE NUMBER
  LOCATION: .1;1                        ACCESS: Read w/Fileman
FIELD NUMBER: .12                       FIELD NAME: ORDER SCHEDULE
  LOCATION: .1;2                        ACCESS: Read w/Fileman
FIELD NUMBER: .13
  FIELD NAME: SCHEDULED ADMINISTRATION TIME
  LOCATION: .1;3                        ACCESS: Read w/Fileman
FIELD NUMBER: .26                       FIELD NAME: IV UNIQUE ID
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: .35                       FIELD NAME: INFUSION RATE
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: .5                        FIELD NAME: DISPENSE DRUG  (mult)
  LOCATION: .5;0                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Includes all fields in this multiple and cross references
 thereof.  
FIELD NUMBER: .6                        FIELD NAME: ADDITIVES  (mult)
  LOCATION: .6;0                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Includes all fields in this multiple and cross references
 thereof.  
FIELD NUMBER: .7                        FIELD NAME: SOLUTIONS  (mult)
  LOCATION: .7;0                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Includes all fields in this multiple and cross references
 thereof.  
 GENERAL DESCRIPTION:   DSS (ECX) read access to file #53.79 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSS (ECX)
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 11/25/2022, effective with DSSV*1.1 C3 is using
 the B index for lookup, as well as fields (#.06) ACTION DATE/TIME, (#.09)
 ACTION STATUS, (#.11) ORDER REFERENCE NUMBER of file 53.79.  DDS Class 2
 product - Document Only 

NUMBER: 5581                            IA #: 5581
  FILE NUMBER: 161.2                    GLOBAL ROOT: FBAAV(161.2,
  DATE CREATED: NOV 04, 2010            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: FEE BASIS VENDOR file #161.2 lookup
  ID: FBAAV(161.2,
GLOBAL REFERENCE: FBAAV(0)
FIELD NUMBER: 2                         FIELD NAME: STREET ADDRESS
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 2.5                       FIELD NAME: STREET ADDRESS 2
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: CITY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: STATE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: ZIP CODE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   ^FBAAV(161.2,"NPI") 
  
 GENERAL DESCRIPTION:   
  
 The ECME package needs to look up entries and addresses in the FEE BASIS
 VENDOR file (#161.2).  The lookup is by the "NPI" cross-reference.  The
 desired fields are all on the zero node. 
  
 The fields: 
  
 2         STREET ADDRESS (F), [0;3] 2.5       STREET ADDRESS 2 (F), [0;14] 3   
      CITY (RF), [0;4] 4         STATE (RP5'), [0;5] 5         ZIP CODE (RFX),
 [0;6] 
  
 This Integration Agreement is to be used to examine the "NPI" cross-reference
 and to read the address fields.  
  
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FEE BASIS VENDOR (#161.2)
KEYWORDS: FBAAV(161.2)
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
 SUBSCRIBING DETAILS:   This agreement is to read the data, only.  
  
 The fields can retrieved by FileMan or through direct global read of
 ^FBAAV(161.2).  
  

NUMBER: 5582                            IA #: 5582
  FILE NUMBER: 411                      GLOBAL ROOT: PRC(411,
  DATE CREATED: NOV 18, 2010            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FILE 411 ACCESS
  ID: PRC(411,
GLOBAL REFERENCE: PRC(411,DO,0)
FIELD NUMBER: .01                       FIELD NAME: STATION/SUBSTATION CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is station number or substation code.  
 GENERAL DESCRIPTION:   This IA provides read-only access to the ADMIN.
 ACTIVITY SITE PARAMETER (#411) file via FileMan for lookups.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS
  DATE ACTIVATED: JAN 11, 2011

NUMBER: 5583                            IA #: 5583
  DATE CREATED: DEC 08, 2010            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  ROUTINE: LRJMAG                       NAME: IMAGING LSRP ACCESSSION AREA
  ID: LRJMAG
 GENERAL DESCRIPTION:   Imaging is requesting to call routine CAALIST^LRJMAG
 for creating a lista of COTS accession area mappings - LRO(68,"ALRJC" TAG:
 CAALIST(OUT) INPUT: OUT <by ref> OUTPUT: OUT array.    OUT(COTS area) ROUTINE:
 LRJMAG 
   for example: OUT("AU") 
                OUT("BM") 
                . . .
                OUT("SP")="" 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: LSRP
KEYWORDS: 68
KEYWORDS: ALRJC
COMPONENT/ENTRY POINT: CAALIST
VARIABLES: OUT                          TYPE: Output
SUBSCRIBING PACKAGE: IMAGING

NUMBER: 5584                            IA #: 5584
  DATE CREATED: DEC 08, 2010            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  ROUTINE: LRJMAG                       NAME: IMAGING LSRP ACCESSION NUMBER
  ID: LRJMAG
 GENERAL DESCRIPTION:   IMAGING is requestin permission to call routine LRJMAG
 for the corresponding VistA/COTS Accession number.  TAG COTSACC(FALG,ACC) 
   Returns the corrsponding VistA/VOTS accession # for ACC # passed.  
   INPUTS:  FLAG: 1=VistA to COTS<dflt>  LR("ALRJH2" 
                  2=COTS to VistA        LR("ALRJH" 
            ACC: the accession # to lookup 
   OUTPUT:  return the corresponding Accession # For example: S
 VAACNUM=$$COTSACC^LRJMAG(2,"523-EM-09-0000001") 
 .
 Imaging team will use the VistA accession # to link the captured image file(s)
 with the selected study/patient.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: COTS
KEYWORDS: LR
KEYWORDS: ALRJH2
KEYWORDS: CERNER
COMPONENT/ENTRY POINT: COTSACC
 COMPONENT DESCRIPTION:   
  
 COTSACC(FLAG,ACC)G,ACC) 
   INPUTS:  FLAG: 1=VistA to COTS<dflt>  LR("ALRJH2" 
                  2=COTS to VistA        LR("ALRJH" 
            ACC: the accession # to lookup 
   OUTPUT:  return the corresponding Accession # 
VARIABLES: FLAG                         TYPE: Input
VARIABLES: ACC                          TYPE: Input
SUBSCRIBING PACKAGE: IMAGING

NUMBER: 5585                            IA #: 5585
  FILE NUMBER: 9002313.26               GLOBAL ROOT: BPS(9002313.26,
  DATE CREATED: DEC 09, 2010            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: LOOKUP/READ ACCESS TO FILE #9002313.26
  ID: BPS(9002313.26,
GLOBAL REFERENCE: BPS(9002313.26,
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the code that is transmitted to the payer for the
 prior authorization type.  
FIELD NUMBER: .02                       FIELD NAME: BRIEF DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the brief description of the code that is defined
 in the NCPDP standard.  
FIELD NUMBER: .03                       FIELD NAME: FULL DESCRIPTION
  LOCATION: 1;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the full description of the code as stated in the
 NCPDP standards.  
FIELD NUMBER: 2                         FIELD NAME: INACTIVE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   If set to 1/INACTIVE, then this entry cannot be entered
 or selected by the user.  
 GENERAL DESCRIPTION:   Permission to subscriber package to make reference to
 this file to perform lookups or read its fields. No write access.  
  
 Amendment: Effective 5/15/23, added field 2 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: BPS
KEYWORDS: PRIOR
KEYWORDS: AUTHORIZATION
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: MAY 15, 2023

NUMBER: 5586                            IA #: 5586
  DATE CREATED: DEC 09, 2010            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Remote Procedure
  NAME: IMAGING LAB PATIENT STUDY
 GENERAL DESCRIPTION:   Imaging is requesting an RPC or API to get a list of
 Lab data from selected VistA patient (DFN) So the image will be captured can
 be linked to the LAB study. (Anatomic Pathology only - VI Capture) 
 .
 Input: DFN (VistA patient ID) Output: OUT <array> 
              OUT(0) = total number of patient LAB study 
              OUT(no) = Patient name^ 
                   patient SSN^ 
                   Date - 1st piece of LR(lrdfn,sect,lri,0)^ 
                   Accession Number^ 
                   Pathologist Name^ 
                   Specimen^ 
                   Patient ID(DFN)^ 
                   Section^ 
                   LRDFN^ 
                   LRI^ If there is no Lab study, the OUT(0)=0 or -1 (patient
 no found) For example: (DFN=1066) 
  
 D DFN^LRJMAG(.OUT,1066) 
  
 OUT(0)="3^DATA FOUND" OUT(1)="PATIENT,ONEZEROSIXSIX^000001066^08/21/2001^CY 01 
 1^UNKNOWN^LUNG^CY^1066^51^6989178^" 
 OUT(2)="PATIENT,ONEZEROSIXSIX^000001066^08/21/2001^EM 01 
 1^IMAGPROVIDERTHREEONE,THREEONE^SKIN^EM^1066^51^6989178^" 
 OUT(3)="PATIENT,ONEZEROSIXSIX^000001066^08/21/2001^SP 01 
 1^UNKNOWN^LUNG^SP^1066^51^6989178^" 
  
 (LSRP MAG*3.0*113) 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DFN
KEYWORDS: LSRP
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   This is part of LSRP project and VistA Imaging to
 identify lab cases using the Cerner Lab accession number.  

NUMBER: 5587                            IA #: 5587
  FILE NUMBER: 2005.86                  GLOBAL ROOT: MAG(2005.86
  DATE CREATED: DEC 09, 2010            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: IMAGING ADD NEW FIELD TO ACTIONS FILE
  ID: MAG(2005.86
 GENERAL DESCRIPTION:   IMAGING is requesting permission to add one new field
 into file 2005.86 IMAGE ACTIONS FILE - DIVISION The IMAGE ACTIONS file
 (#2005.86) will be made division aware.  A new multiple filed will be added
 that referenced divisions are pointed to INSTITUTION FILE (#4). The "B" cross
 reference of the IMAGING SITE PARAMETERS file (#2006.1) will be used to
 collect possible divisions for the field value.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ACTION
KEYWORDS: DIVISION
KEYWORDS: 2005.86
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   STANDARD DATA DICTIONARY #2005.86 -- IMAGE ACTIONS FILE 
  
                                                     DEC 9,2010@15:24:58  PAGE
 1 STORED IN ^MAG(2005.86,  (3 ENTRIES)   SITE: IMGDemo   UCI: DVA,ROU (VERSION
 3.0)   
  
 DATA          NAME                  GLOBAL        DATA ELEMENT       TITLE     
            LOCATION      TYPE 
 --------------------------------------------------------------------------
 -----
  
 2005.86,6     DIVISION               3;0 POINTER Multiple #2005.866 
  
               Divisions                 
               LAST EDITED:      OCT 27, 2010 
               HELP-PROMPT:      Enter the Division for this type of image 
                                 action. 
               DESCRIPTION:      This set of Institution values will allow 
 sites 
                                 to enable the functionality 
  
               TECHNICAL DESCR:  This set of Institution values will allow 
 sites 
                                 to enable or disable the functionality for 
                                 multi-divisional action referenced 
  
  
 2005.866,.01    DIVISIONS              0;1 POINTER TO INSTITUTION FILE (#4) 
  
                 LAST EDITED:      OCT 27, 2010 
                 HELP-PROMPT:      Will allow sites to enable or disable the 
                                   functionality for any division referenced 
                 CROSS-REFERENCE:  2005.866^B 
                                 1)= S 
 ^MAG(2005.86,DA(1),3,"B",$E(X,1,30),DA)=" 
                                 "
  
                                 2)= K ^MAG(2005.86,DA(1),3,"B",$E(X,1,30),DA) 
  
  
  
       FILES POINTED TO                      FIELDS 
  
 INSTITUTION (#4)                  DIVISION:DIVISIONS (#.01) 

NUMBER: 5588                            IA #: 5588
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LRPHITEM
  NAME: LAB ACCESSIONS BY DOD           ID: LRPHITEM
 GENERAL DESCRIPTION:   The Orders Portability requirement for the Federal
 health Care Center at North Chicago requires the ability to handle Lab
 accession services.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
COMPONENT/ENTRY POINT: P15
 COMPONENT DESCRIPTION:   Entry point P15 stores information on a specimen
 collection.  
VARIABLES: LRODT                        TYPE: Input
 VARIABLES DESCRIPTION:   LRODT = Date lab test ordered 
VARIABLES: LRSN                         TYPE: Input
 VARIABLES DESCRIPTION:   LRSN = Specimen number 
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   The JV application for the Orders Portability
 requirement at the Federal Health Care Center in North Chicago requests a call
 into legacy code to store into the VistA database specific information on the
 specimen collection for a given Lab order and accession initiated by DoD.  
  DATE ACTIVATED: AUG 01, 2011

NUMBER: 5589                            IA #: 5589
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  NAME: DBIA-5589                       STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: AUG 03, 2011
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5590                            IA #: 5590
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LROE1
  NAME: LAB ORDER ENTRY FUNCTIONS       ID: LROE1
 GENERAL DESCRIPTION:   Routine LROE1 performs functions related to Order
 Entry.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
COMPONENT/ENTRY POINT: P15
 COMPONENT DESCRIPTION:   The entry point P15 call the M code to store
 accession number and associated elements.  
VARIABLES: LRODT                        TYPE: Input
 VARIABLES DESCRIPTION:   LRODT = Date lab test ordered 
VARIABLES: LRSN                         TYPE: Input
 VARIABLES DESCRIPTION:   LRSN    = Specimen number 
COMPONENT/ENTRY POINT: LRSPEC
 COMPONENT DESCRIPTION:   The entry point LRSPEC contains the M code to enter
 Lab specimen information.  
VARIABLES: LRODT                        TYPE: Input
 VARIABLES DESCRIPTION:   LRODT = Date lab test ordered 
VARIABLES: LRSN                         TYPE: Input
 VARIABLES DESCRIPTION:   LRSN    = Specimen number 
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   Entry points P15 and LRSPEC are invoked when processing
 an accession from DoD.  
  DATE ACTIVATED: AUG 01, 2011

NUMBER: 5591                            IA #: 5591
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LRFAST
  NAME: DBIA-5591                       ID: LRFAST
 GENERAL DESCRIPTION:   For the Orders Portability requirement at the Federal
 Health Care Center at North Chicago, the JV applications needs the ability to
 store an order and accession into the database. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LROE
 COMPONENT DESCRIPTION:   The entry point LROE^LRFAST stores an order and
 accession into the database.  
VARIABLES: LRODT                        TYPE: Input
 VARIABLES DESCRIPTION:   LRODT   = Date lab test ordered 
VARIABLES: LRSN                         TYPE: Input
 VARIABLES DESCRIPTION:   LRSN = Specimen number 
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   The JV application requests the ability to create a new
 order and accession in one step.  
  DATE ACTIVATED: AUG 01, 2011

NUMBER: 5592                            IA #: 5592
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  ROUTINE: LRX                          NAME: DBIA-5592
  ID: LRX                               STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PT
COMPONENT/ENTRY POINT: DUZ
COMPONENT/ENTRY POINT: DD
COMPONENT/ENTRY POINT: DOC
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5593                            IA #: 5593
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LROW2
  NAME: ROUTINE FOR UPDATING FILE 69    ID: LROW2
 GENERAL DESCRIPTION:   These entry points validate and update the contents of
 File 69 (Lab Order Entry). 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
COMPONENT/ENTRY POINT: ORDER
 COMPONENT DESCRIPTION:   ORDER entry point updates the order record in file
 69.  
VARIABLES: DT                           TYPE: Input
 VARIABLES DESCRIPTION:   DT = Current FileMan Date 
COMPONENT/ENTRY POINT: CHECK
 COMPONENT DESCRIPTION:   CHECK entry point validates contents of file 69 for
 an order.  
VARIABLES: LRORD                        TYPE: Input
 VARIABLES DESCRIPTION:   LRORD = Lab order number 
COMPONENT/ENTRY POINT: BAD
 COMPONENT DESCRIPTION:   BAD entry point prints out an error message if
 validation fails.  
VARIABLES: None
 VARIABLES DESCRIPTION:   Boolean result of CHECK^LROW2 
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   Used by Lab code (JVHLLR) to update VistA file when an
 order is accessioned by CHCS.  
  DATE ACTIVATED: AUG 01, 2011

NUMBER: 5594                            IA #: 5594
  DATE CREATED: JAN 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  ROUTINE: LRCAPV                       NAME: DBIA-5594
  ID: LRCAPV                            STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: MAR 03, 2011
COMPONENT/ENTRY POINT: STOP
COMPONENT/ENTRY POINT: STD
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5595                            IA #: 5595
  DATE CREATED: JAN 31, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORWDXA                       NAME: DBIA-5595
  ID: ORWDXA
 GENERAL DESCRIPTION:   The routine ORWDXA contains a set of utility functions
 for handling Orders.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DC
 COMPONENT DESCRIPTION:   The specific entry point DC^ORWDXA is used to
 DisContinue a given Order.  
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   In accordance with the interface project, it is
 necessary to be able to accept orders for procedures from the external partner
 into VistA. This routine contains several functions used in this process.  

NUMBER: 5596                            IA #: 5596
  DATE CREATED: JAN 31, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORWDX                        NAME: ACCESS TO ORDER DIALOG UTILITIES
  ID: ORWDX
 GENERAL DESCRIPTION:   ORWDX is a set of utilities related to Order Dialogs,
 which are used in the process of communicating and modifying Order status,
 results, and modifications to status.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SEND
 COMPONENT DESCRIPTION:   Entry point SEND^ORWDX is used to record the order
 signature in VistA.  
VARIABLES: DFN                          TYPE: Input
VARIABLES: ORNP                         TYPE: Input
VARIABLES: ORL                          TYPE: Input
VARIABLES: ES                           TYPE: Input
VARIABLES: ORWREC                       TYPE: Input
VARIABLES: ORWLST                       TYPE: Output
COMPONENT/ENTRY POINT: SAVE
 COMPONENT DESCRIPTION:   Entry point SAVE^ORWDX is used to store a new order
 in VistA.  
VARIABLES: REC                          TYPE: Output
VARIABLES: ORVP                         TYPE: Input
VARIABLES: ORNP                         TYPE: Input
VARIABLES: ORL                          TYPE: Input
VARIABLES: DLG                          TYPE: Input
VARIABLES: ORDG                         TYPE: Input
VARIABLES: ORIT                         TYPE: Input
VARIABLES: ORIFN                        TYPE: Input
VARIABLES: ORDIALOG                     TYPE: Input
VARIABLES: ORDEA                        TYPE: Input
VARIABLES: ORAPPT                       TYPE: Input
VARIABLES: ORSRC                        TYPE: Input
VARIABLES: OREVTDF                      TYPE: Input
COMPONENT/ENTRY POINT: DGNM
 COMPONENT DESCRIPTION:   DGNM(VAL,NM) ; Display group pointer for name 
          S VAL=$O(^ORD(100.98,"B",NM,0)) 
          Q 
VARIABLES: NM                           TYPE: Input
 VARIABLES DESCRIPTION:   NM=Radiology order number 
VARIABLES: VAL                          TYPE: Output
 VARIABLES DESCRIPTION:   VAL=display group 
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   When Lab or Rad orders are received from DoD, the JV
 Orders Portability calls into ORWDX to store the orders into VistA.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   
   ADDED 7/20/2022, effective with DSSV*1.1 
   DSS Class 3 product 
   Document Only - Not approved by Custodial SME 

NUMBER: 5597                            IA #: 5597
  FILE NUMBER: 2                        GLOBAL ROOT: DPT
  DATE CREATED: FEB 04, 2011            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DPT
  ID: DPT
GLOBAL REFERENCE: DPT(D0,.13)= 
FIELD NUMBER: .134                      FIELD NAME: PHONE NUMBER [CELLULAR]
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   
  
GLOBAL REFERENCE: DPT(D0,.21
FIELD NUMBER: .21011                    FIELD NAME: K-WORK PHONE NUMBER
  LOCATION: .21;11                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.211
FIELD NUMBER: .211011                   FIELD NAME: K2-WORK PHONE NUMBER
  LOCATION: .211;9                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.33
FIELD NUMBER: .33011                    FIELD NAME: E-WORK PHONE NUMBER
  LOCATION: .33;11                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.331
FIELD NUMBER: .331011                   FIELD NAME: E2-WORK PHONE NUMBER
  LOCATION: .331;11                     ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   
  
 GENERAL DESCRIPTION:   Requesting access to fields in file 2 PATIENT that are
 not retrieved with the API VADPT. They reference the cell phone number for the
 patient and the work phone numbers for the next of kin and emergency contacts. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 5598                            IA #: 5598
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: FEB 04, 2011            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: NOK WORK TELEPHONES             ID: DPT(
GLOBAL REFERENCE: DPT(D0,.13, 
FIELD NUMBER: .134                      FIELD NAME: PHONE NUMBER [CELLULAR]
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.21,
FIELD NUMBER: .21011                    FIELD NAME: K-WORK PHONE NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.211,
FIELD NUMBER: .211011                   FIELD NAME: K2-WORK PHONE NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.33
FIELD NUMBER: .33011                    FIELD NAME: E-WORK PHONE NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.331,
FIELD NUMBER: .331011                   FIELD NAME: E2-WORK PHONE NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The following phone numbers are not currently avaialble
 through VADPT or other API's.  They will need to be retrieved through fileman
 calls for usage in report displays.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: NOK E-CONTACT WORK PHONES
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Scheduling requests access to these fields through
 FileMan calls for a scheduling report.  

NUMBER: 5599                            IA #: 5599
  FILE NUMBER: 810.9                    GLOBAL ROOT: PXRMD(810.9,
  DATE CREATED: FEB 07, 2011            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: REMINDER LOCATION LIST
  ID: PXRMD(810.9,
GLOBAL REFERENCE: PXRMD(810.9,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the name of the Reminder Location List.  
  
GLOBAL REFERENCE: PXRMD(810.9,D0,40.7,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CLINIC STOP
  LOCATION: 810.9001,.01                ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Pointer to file #40.7.  
  
FIELD NUMBER: .02                       FIELD NAME: AMIS REPORTING STOP CODE
  LOCATION: 810.9001,.02                ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   AMIS reporting stop code.  
  
GLOBAL REFERENCE: PXRMD(810.9,'B',
 GLOBAL DESCRIPTION:   "B" index for looking up a Reminder Location List.  
  
GLOBAL REFERENCE: PXRMD(810.9,D0,40.7,'B',
 GLOBAL DESCRIPTION:   "B" index for looking up Clinic Stops.  
  
 GENERAL DESCRIPTION:   To make it easier for users to run reports for a set of
 Clinic Stops, the Scheduling package needs access to the Clinic Stop List 
 multiple in Reminder Location Lists. 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: REMINDER LOCATION LIST
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   added 6/7/2011 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   20111104/ TIU ADDED 
  DATE ACTIVATED: MAR 23, 2011

NUMBER: 5600                            IA #: 5600
  DATE CREATED: FEB 08, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RAHLRU1
  NAME: Site specific accession number switch
  ID: RAHLRU1
 GENERAL DESCRIPTION:   Radiology/Nuclear Medicine is a comprehensive software
 package designed to assist with the functions related to the processing of
 patients for imaging examinations.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SSAN
KEYWORDS: accession
KEYWORDS: radiology
KEYWORDS: switch
KEYWORDS: site specific
COMPONENT/ENTRY POINT: USESSAN
 COMPONENT DESCRIPTION:   The USESSAN function returns zero if the legacy
 accession number is used and one if the site specific accession number (SSAN)
 is used.  
  
 The format of the legacy accession number is: mmddyy-case number.  
  
 The value for mmddyy is derived from the EXAM DATE (sub-dd: 70.02; fld: .01).
 The case number is derived from the CASE NUMBER (sub-dd: 70.03; fld: .01).  
  
  
 The site specific accession number is the legacy accession number with a site
 specific prefix.  
  
 The site specific prefix is derived from the DEFAULT INSTITUTION (#217) field
 of the KERNEL SYSTEM PARAMETERS (#8989.3) file. Once the institution is
 identified we truncate the first three characters of the station number and
 appended those characters to the front of the legacy accession number.  
  
  
 Example (where '123' is the station number prefix & 4546 is the case number):
 123-032411-4546.  
SUBSCRIBING PACKAGE: IMAGING
  DATE ACTIVATED: FEB 10, 2011

NUMBER: 5601                            IA #: 5601
  DATE CREATED: FEB 09, 2011            CUSTODIAL PACKAGE: MASTER PATIENT INDEX
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MPIUTL11
  NAME: MPIUTL11 API FOR BHIE/FHIE      ID: MPIUTL11
 GENERAL DESCRIPTION:   The $$ISTF^MPIUTL11(ICN,STA) API returns 1 if the input
 ICN has the input facility (STA) as a Treating Facility (#985.5).  If the ICN
 does not have the facility as a Treating Facility, a zero is returned. This
 API is for the exclusive use of BHIE/FHIE only.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ISTF
 COMPONENT DESCRIPTION:   For the ICN and STA, determine if the STA is a
 Treating Facility or not.  
VARIABLES: ICN                          TYPE: Input
 VARIABLES DESCRIPTION:   The ICN for the patient for whom the call is made to
 determine if a specific facility is a Treating Facility.  
VARIABLES: STA                          TYPE: Input
 VARIABLES DESCRIPTION:   The facility for which the call is made to determine
 if that facility is a Treating Facility for the specific ICN.  
SUBSCRIBING PACKAGE: CORBA SERVICES
  DATE ACTIVATED: APR 27, 2011

NUMBER: 5602                            IA #: 5602
  FILE NUMBER: 70                       GLOBAL ROOT: RADPT
  DATE CREATED: FEB 11, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ACCESS TO RAD/NUC MED PATIENT FILE
  ID: RADPT
GLOBAL REFERENCE: RADPT(D0,0
FIELD NUMBER: .06                       FIELD NAME: USER WHO ENTERED PATIENT
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to the 'NEW PERSON' file (#200) to
 indicate the person who entered this patient into the Radiology/Nuclear
 Medicine system.  It is filled in by the system from information the user
 entered at sign-on.  
GLOBAL REFERENCE: RADPT(D0,DT,D1,0
FIELD NUMBER: .01                       FIELD NAME: EXAM DATE
  LOCATION: DT,0;1                      ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the date and also the time of this
 Imaging exam.  The system stores the exam dates in reverse chronological order
 to produce reports efficiently.  
FIELD NUMBER: 2                         FIELD NAME: TYPE OF IMAGING
  LOCATION: DT,0;2                      ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to the 'IMAGING TYPE' file (#79.2) to
 indicate the type of imaging used for this exam.  It is filled in by the
 system with the appropriate system name.  For example, when in General
 Radiology, this field is filled in with 'GENERAL RADIOLOGY'.  Examples of
 other imaging types this field may use are Nuclear Medicine, Nuclear Magnetic
 Resonance, and Ultrasound.  
FIELD NUMBER: 3                         FIELD NAME: HOSPITAL DIVISION
  LOCATION: DT,0;3                      ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to the 'RAD/NUC MED DIVISION' file
 (#79) to indicate the name of the hospital division where this imaging exam
 was performed.  Normally, a hospital has only one division however, some
 medical centers have multiple divisions.  This field allows the system to
 compile statistics by division.  This field is filled in by the system from
 the information the user enters at sign-on.  
FIELD NUMBER: 4                         FIELD NAME: IMAGING LOCATION
  LOCATION: DT,0;4                      ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to the 'IMAGING LOCATIONS' file (#79.1)
 to indicate the name of the imaging location within the hospital division
 where the exam was performed. Normally, a hospital has only one imaging
 location, however, some medical centers have multiple imaging locations within
 the division.  This field is filled in by the system from information the user 
 enters at sign-on.  
GLOBAL REFERENCE: RADPT(D0,DT,D1,P,D2,0
FIELD NUMBER: .01                       FIELD NAME: CASE NUMBER
  LOCATION: P,D2,0;1                    ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the computer generated case number of
 this Imaging exam.  The case number is used to quickly track and call up the
 exam as it is processed through the Rad/Nuc Med system.  The case numbers are 
 generated by the system in sequential order.  
                                  
 NOTE:  Case numbers are not allowed to exceed 99,999.  
FIELD NUMBER: 2                         FIELD NAME: PROCEDURE
  LOCATION: P,D2,0;2                    ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to the 'RAD/NUC MED PROCEDURES' file
 (#71) to indicate the Imaging procedure associated with this case number.  
FIELD NUMBER: 3                         FIELD NAME: EXAM STATUS
  LOCATION: P,D2,0;3                    ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to the 'EXAMINATION STATUS' file (#72)
 to indicate the current status of this Imaging exam.  The status is determined
 and updated by the system according to the information entered during the
 various data entry processes.  
FIELD NUMBER: 4                         FIELD NAME: CATEGORY OF EXAM
  LOCATION: P,D2,0;4                    ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the exam category associated with
 this case number.  It is used to compile workload statistics and various
 management reports (i.e. AMIS and RCS14-4). Available exam categories are: 'I'
 for INPATIENT, 'O' for OUTPATIENT, 'C' for CONTRACT, 'S' for SHARING, 'E' for
 EMPLOYEE, and 'R' for RESEARCH.  
                                  
 When the 'category of exam' is asked during the exam registration process, the
 default value asked is the value in the 'usual category' field.  Of course, if
 the patient is an inpatient, the default value will always be 'inpatient'.  
                                  
 An inpatient may have a 'category of exam' of 'contract', 'sharing', or 
 'research' for its associated case number if the exam procedure is not 
 directly related with their hospital stay. (i.e. An inpatient who has an 
 imaging exam performed for research purposes.) 
FIELD NUMBER: 6                         FIELD NAME: WARD
  LOCATION: P,D2,0;6                    ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to the 'WARD LOCATION' file (#42) to
 indicate the name of the hospital ward where the inpatient was admitted at the
 time the Radiology/Nuclear Med exam was performed.  
                                   
 This field is filled in by the system from information entered by the ADT 
 system and is updated at the time the exam report is first printed.  
FIELD NUMBER: 7                         FIELD NAME: SERVICE
  LOCATION: P,D2,0;7                    ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field is used for Rad/Nuc Med patients who are
 inpatients. It points to the 'HOSPITAL SERVICE' file (#49) to indicate the
 name of the service treating the patient and is filled in by the system from
 information entered by the ADT system.  
FIELD NUMBER: 10                        FIELD NAME: CONTRAST MEDIA USED
  LOCATION: P,D2,0;10                   ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   DESCRIPTION: This field contains a value to indicate if a
 contrast medium was, or if contrast media were used during this Rad/Nuc Med
 exam.  Available values are: 'Y' for YES and 'N' for NO.  
                                  
 If the Rad/Nuc Med procedure does not involve the use of a contrast, the field
 is automatically filled in with NO by the system but the user is prompted with
 this question.  
                                  
 Conversely, if the Rad/Nuc Med procedure does not involve the use of a 
 contrast, the field is automatically filled in with NO by the system but the
 user is prompted with this question.  
  
 TECHNICAL DESCR: Modified, description and help text only, with the release of
 RA*5*45.  
FIELD NUMBER: 11                        FIELD NAME: IMAGING ORDER
  LOCATION: P,D2,0;11                   ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   DESCRIPTION:  This field points to the 'RAD/NUC MED
 ORDERS' File (#75.1).  It contains the order associated with this exam. This
 field will only contain data if the exam has an 'ACTIVE' order associated with
 it.  When orders are purged, the pointer in this field is also purged.  
  
 TECHNICAL DESCR: Patch RA*5*41 will dis-allow purging of orders from the 
 Radiology/Nuclear Medicine application.  
FIELD NUMBER: 13                        FIELD NAME: PRIMARY DIAGNOSTIC CODE
  LOCATION: P,D2,0;13                   ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field is used at sites that decide to enter
 diagnostic codes for exams, as designated in the Examination Status file
 parameters. It points to a short diagnostic code in the 'DIAGNOSTIC CODES'
 file (#78.3) to indicate the primary diagnostic code associated with this
 exam. If filled in, this field can be used in the search criteria for database
 searches.  For example, the database can be searched for all 'normal' chest 
 procedures performed during a specific time period.  
                                  
 Depending on the requirements set up in the 'EXAMINATION STATUS' file (#72),
 it may be necessary for this field to be filled in before the 'exam status'
 can be considered complete.  
FIELD NUMBER: 14                        FIELD NAME: REQUESTING PHYSICIAN
  LOCATION: P,D2,0;14                   ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to the 'NEW PERSON' file (#200) to
 indicate the name of the person who requested this Rad/Nuc Med exam.  This
 person is not always a physician.  (i.e. A nurse might request the exam.) 
FIELD NUMBER: 15                        FIELD NAME: PRIMARY INTERPRETING STAFF
  LOCATION: P,D2,0;15                   ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to the 'NEW PERSON' file (#200) to
 indicate the name of the primary staff who interpreted the images.  Primary
 Staff must have Rad/Nuc Med personnel classification of 'staff', and must have
 access to at least one imaging location of the same imaging type as the exam.  
                                  
 Depending on the requirements set up in the 'EXAMINATION STATUS' file (#72),
 it may be necessary for this field to be filled in before the 'exam status'
 can be considered complete.  
FIELD NUMBER: 17                        FIELD NAME: REPORT TEXT
  LOCATION: P,D2,0;17                   ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to the 'RAD/NUC MED REPORTS' file (#74)
 to indicate the report text associated with this exam.  It is filled in by the
 system and is not seen by the user.  
FIELD NUMBER: 18                        FIELD NAME: PRIMARY CAMERA/EQUIP/RM
  LOCATION: P,D2,0;18                   ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field points to the 'CAMERA/EQUIP/RM' file (#78.6)
 for the name of the primary camera/equipment/room where the imaging exam was
 performed.  Usually there is only one camera/equipment/room per procedure.  
                                  
 Depending on the requirements set up in the 'EXAMINATION STATUS' file (#72),
 it may be necessary for this field to be filled in before the 'exam status'
 can be considered complete.  
FIELD NUMBER: 19                        FIELD NAME: BEDSECTION
  LOCATION: P,D2,0;19                   ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to the 'SPECIALTY' file (#42.4) to
 indicate the name of the bedsection of Rad/Nuc Med patients who are
 inpatients. This field is filled in by the system from information entered by
 the ADT system.  
FIELD NUMBER: 21                        FIELD NAME: REQUESTED DATE
  LOCATION: P,D2,0;21                   ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the date the Rad/Nuc Med exam was
 requested.  
                                  
 Depending on the site's specifications, this field may or may not be asked of
 the transcriptionist.  By default, it is populated automatically, at the time
 an exam is registered, with the Request date in the Rad/Nuc Med Order file.  
FIELD NUMBER: 22                        FIELD NAME: REQUESTING LOCATION
  LOCATION: P,D2,0;22                   ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   DESCRIPTION:This field points to the 'HOSPITAL LOCATION'
 file (#44) to indicate the name of the hospital location that is requesting
 the exam. By default, it is populated automatically, using data from the
 Rad/Nuc Med Orders file, at the time an exam is registered.  
  
 TECHNICAL DESCR: This field has been modified with the release of patch: 
 RA*5.0*86.  
FIELD NUMBER: 26                        FIELD NAME: CREDIT METHOD
  LOCATION: P,D2,0;26                   ACCESS: Both R/W 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 was 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.  
GLOBAL REFERENCE: RADPT(D0,DT,D1,P,D2,F,D3,0
FIELD NUMBER: .01                       FIELD NAME: FILM SIZE
  LOCATION: F,D3,0;1                    ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field points to the 'FILM SIZES' file (#78.4) to
 indicate the size of the film used during the Rad/Nuc Med exam.  Users may
 also enter film sizes that have been wasted during the exam.  
FIELD NUMBER: 2                         FIELD NAME: AMOUNT(#films or cine ft)
  LOCATION: F,D3,0;2                    ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field contains the amount of film (a number between
 0 and 999) used or wasted during the Rad/Nuc Med exam.  
                                  
 The amount represents either the number of that film size or the number of 
 cine feet of that film size.  On the 'Film Usage Report', these two amounts
 are distinguished from each other.  
GLOBAL REFERENCE: RADPT(D0,DT,D1,P,D2,TC,D3,0
FIELD NUMBER: .01                       FIELD NAME: TECHNOLOGIST
  LOCATION: TC,D3;0                     ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to the 'NEW PERSON' file (#200) to
 indicate the technologists who performed this exam.  
GLOBAL REFERENCE: RADPT('ADC'
 GLOBAL DESCRIPTION:   The "ADC" cross reference uses the Case Number to track
 the Radiology order number to the proper IEN for the radiology patient file
 entry.  
GLOBAL REFERENCE: RADPT('AO'
 GLOBAL DESCRIPTION:   The 'AO' cross-reference is used to track the Radiology
 order number to the proper IEN for the radiology patient file entry.  
GLOBAL REFERENCE: RADPT,D0,DT,D1,P,D2,M,0
FIELD NUMBER: 125                       FIELD NAME: PROCEDURE MODIFIERS
  LOCATION: M;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This multiple field is used to give the imaging modifiers
 that are associated with this exam.  
GLOBAL REFERENCE: RADPT(D0,DT,D1,P,D2,M,D3,0
FIELD NUMBER: .01                       FIELD NAME: PROCEDURE MODIFIERS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field points to the 'PROCEDURE MODIFIERS' file
 (#71.2) to give details and further describe this exam.  Modifier examples
 include, 'LEFT', 'RIGHT', 'BILATERAL', 'OPERATING ROOM',and 'PORTABLE' exams.  
 GENERAL DESCRIPTION:   RADPT file #70, is the RAD/NUC MED Patient file. In
 order to interface the VistA Radiology system with any external system, it is
 necessary to be able to read from and write to this file. When external exams
 are registered and results are filed entries in this file are made. This file 
 is one of three primary radiology reference files and is where are patient 
 related information is stored for radiological exams.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: JV RA
KEYWORDS: RA
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   It is necessary to read from this file in order to
 determine numerous elements associated with exam status, exam registration,
 and results status. It is also necessary for this project to be able to write
 to this global in order to create new orders, modify status of exams, and to
 cross reference results status.  
  DATE ACTIVATED: AUG 01, 2011

NUMBER: 5603                            IA #: 5603
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870,
  DATE CREATED: FEB 12, 2011            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: YS MHAT LOOKUP
  ID: HLCS(870,
 GENERAL DESCRIPTION:   The Mental Health package requests permission to do a
 FileMan lookup on the HL LOGICAL LINK (#870) file for the YS MHAT entry. We
 wish to then do a EN^DIQ call to display the field values for that record. We
 do not wish to edit any of the values.  
  
 Here is our code: 
  
 CKHL7    ;check hl7 status 
          N DIC,DA 
          W @IOF,!?15,"*** HL7 Check ***",! 
          S X="YS MHAT",DIC=870 D ^DIC 
          I +Y'>0 W !,"YS MHAT ERROR" Q  ;-->out 
          S DA=+Y D EN^DIQ 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MENTAL HEALTH
KEYWORDS: YS MHAT
SUBSCRIBING PACKAGE: MENTAL HEALTH
  DATE ACTIVATED: FEB 14, 2011

NUMBER: 5604                            IA #: 5604
  FILE NUMBER: 75.1                     GLOBAL ROOT: RAO
  DATE CREATED: FEB 14, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RADIOLOGY ORDER INFORMATION
  ID: RAO
GLOBAL REFERENCE: RAO(75.1,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: PROCEDURE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: TYPE OF IMAGING
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13                        FIELD NAME: PREGNANT
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 18                        FIELD NAME: LAST ACTIVITY DATE/TIME
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RAO(75.1,D0,T,D1,0
FIELD NUMBER: .01                       FIELD NAME: STATUS CHANGE DATE/TIME
  LOCATION: D0,T,D1,0;1                 ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: NEW STATUS
  LOCATION: D0,T,D1,0;2                 ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: COMPUTER USER
  LOCATION: D0,T,D1,0;3                 ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   This file contains the Radiology order information.
 This is different and contains information not found in the Order file (#100). 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: JV RA
KEYWORDS: MEDICOM
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   In accordance with the interfacing of Radiology orders
 and exchange of Radiology information, it is necessary to be able to both read
 from and place information into the Radiology Order file. This includes
 creating new Radiology entries.  
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Added 9/9/24 effective with Patch MECH*1.0*1 MEDICOM
 receives HL7 Imaging order messages about imaging studies performed in the
 community but not entered through VistA and needs to write to the RAD/NUC MED
 ORDERS File (#75.1), via FileMan to the PROCEDURE (#2) and the TYPE OF IMAGING
 (#3) fields.  
  DATE ACTIVATED: APR 25, 2011

NUMBER: 5605                            IA #: 5605
  FILE NUMBER: 74                       GLOBAL ROOT: RARPT
  DATE CREATED: FEB 14, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ACCESS TO RAD/NUC MED REPORT FILE
  ID: RARPT
GLOBAL REFERENCE: RARPT(D0,0
FIELD NUMBER: 2                         FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the name of the rad/nuc med patient
 associated with this report.  The system fills in this field with data
 obtained from the 'RAD/NUC MED PATIENT' file (#70) according to the case
 number selected by the transcriptionist.  
FIELD NUMBER: 3                         FIELD NAME: EXAM DATE/TIME
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the date and the time of the exam
 associated with this report.  The system fills in this field with data
 obtained from the 'RAD/NUC MED PATIENT' file (#70) according to the case
 number selected by the transcriptionist.  
FIELD NUMBER: 4                         FIELD NAME: CASE NUMBER
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the completed case number of the exam
 associated with this report.  The system fills in the data for this field with
 information obtained from the 'RAD/NUC MED PATIENT' file (#70).  
FIELD NUMBER: 5                         FIELD NAME: REPORT STATUS
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains a value to indicate the status of
 this report.  Valid choices are: 'V' for Verified, 'R' for Released/Not
 Verified, 'PD' for Problem Draft, 'D' for Draft, 'EF' for Electronically Filed
 and 'X' for Deleted.  
                                  
 'V' (Verified) status refers to a report that is verified by the interpreting
 physician and is available for display outside the Rad/Nuc Med Department to
 appropriate users, such as ward clerks, nurses, and physicians.  
                                  
 R' (Released/Not Verified) status refers to a report that is not verified by
 the interpreting physician and is available for display outside the Rad/Nuc
 Med Department.  The 'R' status is allowed only when the parameter that
 controls this feature, 'Allow Released/Unverified' of the 'RAD/NUC MED
 DIVISION' file (#79), is set to 'Yes'.  Use the 'Display Report' option to
 view reports with the 'R' status.  
                                  
 'D' (Draft) status or 'PD' (Problem Draft) status refers to a report that is
 available only for display in the Rad/Nuc Med Department. A statement 
 describing the problem to the interpreting physician is printed at the end of
 reports with the 'PD' status.  
                                  
 'EF' (Electronically Filed) status refers to a report that is interpreted 
 outside the Rad/Nuc Med Department.  The content is not the actual interpreted
 report, but canned text referring to the outside interpreted report.  
                                  
 'X' (Deleted) status refers to a report that is deleted from a case, but 
 remains in the database though not selectable from any Radiology options.  
FIELD NUMBER: 6                         FIELD NAME: DATE REPORT ENTERED
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the date and time that the report was
 entered into the system by the transcriptionist.  
FIELD NUMBER: 7                         FIELD NAME: VERIFIED DATE
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   As of July, 1985, this field contains the date and the
 time that it was indicated to the system that the report was verified by the
 interpreting physician.  
                                  
 An option allowing online verification lets the interpreting physician verify
 the report directly via a CRT.  As a result, there will be no discrepency
 between the date/time the physician verified the report and the date/time it
 was indicated to the system.  
FIELD NUMBER: 8                         FIELD NAME: REPORTED DATE
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the date that the interpreting
 physician dictated this report. The transcriptionist enters this date from the
 dictation tape.  If the physician is using a voice recognition system for
 dictation, this date is entered at the time the report is transmitted to DHCP. 
 
FIELD NUMBER: 9                         FIELD NAME: VERIFYING PHYSICIAN
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field is a pointer to the 'NEW PERSON file (#200).
 Only 'staff' or 'resident' interpreting physicians are allowed to be selected.
 This field contains the name of the interpreting physician who verified the
 report.  
FIELD NUMBER: 17
  FIELD NAME: STATUS CHANGED TO VERIFIED BY
  LOCATION: 0;17                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field will record the individual who is signed on
 and responsible for the changing the report status to 'verified'.  
GLOBAL REFERENCE: RARPT(D0,BA
FIELD NUMBER: 86
  FIELD NAME: INTERPRETING IMAGING LOCATION
  LOCATION: BA;1                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the imaging location where the interpretation was
 performed.  It is a pointer to the Imaging Location file (#79.1).  
GLOBAL REFERENCE: RARPT(D0,H,0
FIELD NUMBER: 400                       FIELD NAME: ADDITIONAL CLINICAL HISTORY
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: .01                       FIELD NAME: ADDITIONAL CLINICAL HISTORY
  LOCATION: D0,H,D1,0;1                 ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field may contain a patient's clinical history as
 well as instructions to the interpreting physician.  For example, the
 instructions might be for the physician to interpret the exam images to rule
 out the possibility of the patient having a certain disease.  
                                  
 The 'additional clinical history' is written by the interpreting physician and
 is entered into the system by the transcriptionist.  Voice Recognition systems
 allow the interpreting physician to directly enter this information into the
 'additional clinical history' field.  
GLOBAL REFERENCE: RARPT(D0,I,0
FIELD NUMBER: 300                       FIELD NAME: IMPRESSION TEXT
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: .01                       FIELD NAME: IMPRESSION TEXT
  LOCATION: D0,I,D1,0;1                 ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the 'impression text' of the rad/nuc
 med exam associated with this report.  The 'impression text' gives a quick
 summary of the 'report text'.  It is written by the interpreting physician and
 is entered into the system by the transcriptionist. The system will allow the 
 interpreting physician to directly enter this information into the 'impression
 text' field through a voice recognition system.  
                                  
 If the interpreting physician requests a standard report, the information in
 this field is copied from the 'impression text' field of the 'Standard 
 Reports' file.  
GLOBAL REFERENCE: RARPT(D0,L,0
FIELD NUMBER: 100                       FIELD NAME: ACTIVITY LOG
  LOCATION: L;0                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is a multiple field containing a log of actions that
 have been taken on this report record.  
FIELD NUMBER: .01                       FIELD NAME: LOG DATE
  LOCATION: D0,L,D1,0;1                 ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the date and the time that the action
 was taken on this report record.  
FIELD NUMBER: 2                         FIELD NAME: TYPE OF ACTION
  LOCATION: D0,L,D1,0;2                 ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the type of action that was taken on
 this report record.  Valid choices are:  'I' for Initial Report Transcription,
 'E' for Report Edit, 'V' for Verified, 'U' for Report Unverified, 'C' for 
 Digitized Images Collected, 'P' for Pre-Verified, 'F' for Electronically 
 Filed, 'X' for Deleted Report, and 'R' for Restored Report.  
FIELD NUMBER: 3                         FIELD NAME: COMPUTER USER
  LOCATION: D0,L,D1,0;1                 ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field points to  the 'NEW PERSON' file and is used
 to record the user who took an action on this report record.  
GLOBAL REFERENCE: RARPT(D0,R,0
FIELD NUMBER: 200                       FIELD NAME: REPORT TEXT
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: .01                       FIELD NAME: REPORT TEXT
  LOCATION: D0,R,D1,0;1                 ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the report text for the imaging exam.
 The report text is written by the interpreting physician and may be entered
 into the system by a transcriptionist.  A report may also be entered into DHCP
 when the interpreting physician uses a voice recognition system.  
                                  
 If the interpreting physician requests a standard report, the information in
 this field is copied from the 'Report Text' field of the 'Standard Reports'
 file.  
GLOBAL REFERENCE: RARPT(D0,T
FIELD NUMBER: 11                        FIELD NAME: TRANSCRIPTIONIST
  LOCATION: T;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   DESCRIPTION: Rad/nuc med personnel who entered the
 report.  
  
 TECHNICAL DESCR:  This field is populated by the system with the Rad/nuc med
 user that transcribes the report.  
GLOBAL REFERENCE: RARPT(D0,2005,0
FIELD NUMBER: 2005                      FIELD NAME: IMAGE
  LOCATION: 2005;0                      ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This multiple field holds pointer values to the Image
 file (2005).  
FIELD NUMBER: .01                       FIELD NAME: IMAGE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field holds the pointer value for an image located
 in the Image file (2005).  
 GENERAL DESCRIPTION:   Radiology Report file is the location all results,
 impressions, and reports associated with a radiology exam are stored.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV RA
KEYWORDS: RA JV
KEYWORDS: VPR RA
KEYWORDS: RA VPR
KEYWORDS: RA PCE
KEYWORDS: PX*1*211 RA
KEYWORDS: PCE RA
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   In accordance with the interface project, it is
 necessary to be able to both file new results into this global and to extract
 filed results and transmit them to the interface partner. 
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   VIRTUAL PATIENT RECORD will be using this IA to read
 from the RAD/NUC MED REPORTS file.  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   The PATIENT CARE ENCOUNTER (PCE) VistA application
 would like to read the CASE NUMBER (#4) and the IMPRESSION TEXT (#300) from a
 specific radiology report record which resides in the RAD/NUC MED REPORTS
 (#74) file.  
  
 Related PCE patch: PX*1*211 Date Added: 07/17/2020.  
  DATE ACTIVATED: AUG 16, 2011

NUMBER: 5606                            IA #: 5606
  FILE NUMBER: 72                       GLOBAL ROOT: RA 
  DATE CREATED: FEB 14, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RADIOLOGY EXAMINATION STATUS
  ID: RA 
GLOBAL REFERENCE: RA(72,D0,0
FIELD NUMBER: 7                         FIELD NAME: TYPE OF IMAGING
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Type of imaging being performed.  
 GENERAL DESCRIPTION:   Examination status for Radiology.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: JV RA
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   According to the requirements of the interface project,
 it is necessary to reference the Radiology Examination Status'. Since the
 status of a given procedure is locally defined it is necessary to search the
 72 file for the imaging being performed and then reference the proper status
 for the stage of the exam. Since all procedure have the potential to have
 different status' reference to the global and search for proper status is
 essential to properly set the exam status in the Radiology Order file, and
 several other files used to keep track of Radiology Status.  
  DATE ACTIVATED: APR 25, 2011

NUMBER: 5607                            IA #: 5607
  FILE NUMBER: 71                       GLOBAL ROOT: RAMIS
  DATE CREATED: FEB 14, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ACCESS TO RAD/NUC MED PROCEDURE FILE
  ID: RAMIS
GLOBAL REFERENCE: RAMIS(71,D0,0
FIELD NUMBER: 12                        FIELD NAME: TYPE OF IMAGING
  LOCATION: 0;12                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   DESCRIPTION: This field is used to associate a particular
 imaging type to a procedure.  
  
 TECHNICAL DESCR: Procedures may be screened by type of imaging.  
 GENERAL DESCRIPTION:   File 71 is the Rad/Nuc Med Procedure file. It is
 necessary for the interface project to be able to reference what procedures
 are being requested and the exams status path from registration to completion,
 which is referenced in this file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: JV RA
KEYWORDS: RA
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   Only read access is required. In the process of
 receiving status modifications and original orders, it is necessary to
 reference the status information contained within file 71.  
  DATE ACTIVATED: MAY 09, 2011

NUMBER: 5608                            IA #: 5608
  DATE CREATED: FEB 15, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORQQCN1
  NAME: ORQQCN1                         ID: ORQQCN1
 GENERAL DESCRIPTION:   The Mental Health package requests permission to call
 GETCSLT^ORQQCN1 to retrieve a complete consult record.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GETCSLT
COMPONENT/ENTRY POINT: GETCSLT
 COMPONENT DESCRIPTION:   This entry point has three parameters. From left to
 right they are ORY, ORIEN and SHOWADD). 
  
 D GETCSLT^ORQQCN1(.ORY,ORIEN,SHOWADD) 
  
 Output: If an error was encountered, the ORY array equals: 
  ORY(0)="-1^error message" 
  
 Otherwise, the ORY array contains: 
  ORY(0)=p1^p2^p3^p4^p5^p6^p7^p8^p9^p10^p11^p12^p13^p14^p15^p16^p17^p18^p19 
         ^p20^p21^p22^p23^p24 
  ORY(n)=p25^p26^p27^p28^p29^p30^p31^p32^p33^p34^p35^p36 
  
 ORY(0) is basically the zero node of the FILE 123 entry except that p14 
 contains the sending provider's name as well as NEW PERSON (#200) file number
 (aka DUZ).  
  
  p1 = (#.01) FILE ENTRY DATE [FileMan date/time] 
  p2 = (#.02) PATIENT NAME [pointer to PATIENT (#2) file] 
  p3 = (#.03) OE/RR FILE NUMBER [pointer to ORDER (#100) file] 
  p4 = (#.04) PATIENT LOCATION [pointer to HOSPITAL LOCATION (#44) file] 
  p5 = (#1) TO SERVICE [pointer to REQUEST SERVICES (#123.5) file] 
  p6 = (#2) FROM [pointer to HOSPITAL LOCATION (#44) file] 
  p7 = (#3) DATE OF REQUEST [FileMan date/time] 
  p8 = (#4) PROCEDURE/REQUEST TYPE [variable pointer] 
  p9 = (#5) URGENCY [pointer to PROTOCOL (#101) file) 
  p10 = (#6) PLACE OF CONSULTATION [pointer to PROTOCOL (#101) file] 
  p11 = (#7) ATTENTION [pointer to NEW PERSON (#200) file] 
  p12 = (#8) CPRS STATUS [pointer to ORDER STATUS (#100.01) file] 
  p13 = (#9) LAST ACTION TAKEN [pointer to REQUEST ACTION TYPES (#123.1) 
             file] 
  p14 = (#10) SENDING PROVIDER [pointer to NEW PERSON (#200) file;.01 
              value] 
  p15 = (#11) RESULT [variable pointer] 
  p16 = (#12) MODE OF ENTRY [set of codes: 1:SERVICE FORCED ENTRY] 
  p17 = (#13) REQUEST TYPE [set of codes: C:Consult;P:Procedure] 
  p18 = (#14) SERVICE RENDERED AS IN OR OUT [set of codes: 
              I:inpatient;O:outpatient] 
  p19 = (#15) SIGNIFICANT FINDINGS [set of codes: Y:yes;N:no;U:unknown] 
  p20 = (#16) TIU RESULT NARRATIVE [pointer to TIU DOCUMENT (#8925) file] 
  p21 = (#.05) ORDERING FACILITY [pointer to INSTITUTION (#4) file] 
  p22 = (#.06) REMOTE CONSULT FILE ENTRY [number from 1 to 999999999999] 
  p23 = (#.07) ROUTING FACILITY (pointer to INSTITUTION (#4) file] 
  p24 = ((#17) EARLIEST DATE [FileMan date/time] 
  
 ORY(n) contains the results of the RESOLVE^TIUSRVLO call.  
  p25 = Pointer to a TIU DOCUMENT (#8925) entry 
  p26 = Display name of TIU Title 
  p27 = REFERENCE DATE from TIU DOCUMENT file (internal format) 
  p28 = Patient name in format LAST, FIRST MI followed by space followed by 
        last 4 of patient SSN 
  p29 = AUTHOR/DICTATOR from TIU DOCUMENT file as IEN;SIGNATURE BLOCK TITLE 
  p30 = External format of HOSPITAL LOCATION from TIU DOCUMENT file 
  p31 = STATUS from TIU DOCUMENT file (external format in lower case) 
  p32 = 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.  
  p33 = 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.  
  p34 = REQUESTING PACKAGE REFERENCE field from TIU DOCUMENT file (internal 
        format) 
  p35 = Number of images associated with TIU DOCUMENT entry 
  p36 = SUBJECT (OPTIONAL description) field from TIU DOCUMENT file (note 
        that characters are limited to ensure returned string is not longer 
        than 255 characters).  
  
 Example: 
  
 >D GETCSLT^ORQQCN1(.TEST,4052,1) ZW TEST 
 TEST(0)="3110210.155^2361323495^22715^63^4^63^3110210.155034^13;GMR(123.3, 
 ^1305^1301^^2^10^4558;MHUSER,FIRST^6039;TIU(8925,^^P^I^^^6020^3110210.15" 
 TEST(1)="6039^ECG^3110210.155131^MHPATIENT, FIRST  (M1234)^4687;CLINICAL 
 DEVICE P ROXY SERVICE;CLINICAL,DEVICE PROXY SERVICE^CARDIAC 
 CLINIC^completed^Visit: 02/10 /11;3110210.16^;^4052;GMR(123,^0^^^1^" 
VARIABLES: ORY                          TYPE: Both
 VARIABLES DESCRIPTION:   ORY is the array name to hold the results of the
 search. This parameter is required.  
VARIABLES: ORIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   ORIEN is the internal entry number of a record in the
 REQUEST/CONSULTATION (#123) file. This parameter is required.  
VARIABLES: SHOWADD                      TYPE: Input
 VARIABLES DESCRIPTION:   SHOWADD is a boolean value to indicate if addenda
 should be returned. Set it to a positive number to return addenda. This
 parameter is optional.  There is no default value.  
SUBSCRIBING PACKAGE: MENTAL HEALTH
  DATE ACTIVATED: MAR 09, 2011

NUMBER: 5609                            IA #: 5609
  FILE NUMBER: 78.3                     GLOBAL ROOT: RA 
  DATE CREATED: FEB 15, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA-5609
  ID: RA 
GLOBAL REFERENCE: RA(78.3,D0
FIELD NUMBER: .01                       FIELD NAME: DIAGNOSTIC CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the number of this diagnostic code. 
 This provides a way to do quick look-ups of a diagnostic code by its number.
 Diagnostic code numbers are assigned by the system and are between 1 and 998. 
 Diagnostic codes above 998 are assigned by Radiology patches. 
 GLOBAL DESCRIPTION:   Fileman call (GET1^DIQ) is used to access the data.  
 GENERAL DESCRIPTION:   This file contains the diagnostic codes that can be
 associated with an exam. The code is attached to an exam at the time the
 interpreting resident and/or staff physician is entered for the exam. The
 diagnostic code represents a quick overall summary of what the interpreting 
 physician wrote in the report concerning the exam.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RA
KEYWORDS: JV
KEYWORDS: RA JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   The code for the FHCC check to see if the primary
 diagnosis code exists, using FileMan GET1^DIQ.   
  DATE ACTIVATED: JUN 16, 2011

NUMBER: 5610                            IA #: 5610
  FILE NUMBER: 79.1                     GLOBAL ROOT: RA 
  DATE CREATED: FEB 15, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA-5610
  ID: RA 
GLOBAL REFERENCE: RA(79.1,D0
FIELD NUMBER: .01                       FIELD NAME: LOCATION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field points to the Hospital Location File, and
 contains the name of this location.  
 GENERAL DESCRIPTION:   This file contains, for each imaging location 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 location by the package coordinator.  
  
 The data for the 'IMAGING LOCATIONS' file is stored in the ^RA(79.1, global.
 At the present time this file is very static.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: JV RAD
KEYWORDS: RAD
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   This is a check to see if the imaging location exists,
 using Fileman call (GET1^DIQ).  
  DATE ACTIVATED: JUN 16, 2011

NUMBER: 5611                            IA #: 5611
  DATE CREATED: FEB 17, 2011            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: HOSPITAL LOCATION DATA AUDITING
 GENERAL DESCRIPTION:   Applications that need to monitor Medical
 Administration changes made to Hospital Location, Ward Location, and Room-Bed
 data may do so with subscription to this ICR.  This Integration Control
 Registration allows the Subscribing packages to turn on Auditing for the
 following fields in the indicated file: 
  
    HOSPITAL LOCATION AUDITING: 
    FILE: 44                  
      ROOT: SC( 
      AUDIT GLOBAL REFERENCE: 
        ^SC(D0,0) 
          .01  NAME                             0;1   Fileman Audit allowed 
          2    TYPE                             0;3   Fileman Audit allowed 
          3    INSTITUTION                      0;4   Fileman Audit allowed 
          3.5  DIVISION                         0;15  Fileman Audit allowed 
  
        ^SC(DO,I) 
          2505 INACTIVATE DATE                  I;1   Fileman Audit allowed 
          2506 REACTIVATE DATE                  I;2   Fileman Audit allowed 
  
  
    WARD LOCATION AUDITING: 
    FILE: 42                  
      ROOT: ^DIC(42, 
      AUDIT GLOBAL REFERENCE: 
        ^DIC(42,D0,0) 
          .01  NAME                             0;1   Fileman Audit allowed 
          .015 DIVISION                         0;11  Fileman Audit allowed 
  
        ^DIC(42,D0,44) 
          44   HOSPITAL LOCATION FILE POINTER   44;1  Fileman Audit allowed 
  
  
    ROOM-BED AUDITING: 
    FILE: 405.4                  
      ROOT: DG(405.4, 
      AUDIT GLOBAL REFERENCE: 
        ^DG(405.4,D0,0) 
          .01  NAME                             0;1   Fileman Audit allowed 
  
      ROOT: ^DG(405.4,D0,W, 
      AUDIT GLOBAL REFERENCE: 
        ^DG(405.4,D0,W,D1,0) 
          .01  WARD(S) WHICH CAN ASSIGN         0;1   Fileman Audit allowed 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HOSPITAL LOCATION
KEYWORDS: WARD LOCATION
KEYWORDS: ROOM-BED
KEYWORDS: FILEMAN AUDIT
KEYWORDS: AUDIT
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   Lab Service may use the VA Fileman Auditing system to
 track and report changes to the indicated data as necessary.  
  DATE ACTIVATED: FEB 18, 2011

NUMBER: 5612                            IA #: 5612
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: MAR 02, 2011            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: RE-INDEX 'AD' CROSS-REFERENCE ON SECONDARY MENU OPTIONS 
  ID: VA(200,
GLOBAL REFERENCE: VA(200,DA(1),203,0)
FIELD NUMBER: 203                       FIELD NAME: SECONDARY MENU OPTIONS
  LOCATION: 203;0                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Laboratory System Re-engineering Project (LSRP)
 Rollback Tool Kit (RTK) has a onetime request to re-index the 'AD'
 cross-reference on the SECONDARY MENU OPTIONS field (#203) in the NEW PERSON
 file (#200). The re-indexing will take place in the post-init for patch
 LR*5.2*393 in routine LR393. The code is as follows: 
  
 REINDEX  ; -- index 'AD' xref on NEW PERSON file 
          D MES^XPDUTL("Re-indexing 'AD' Cross Reference on SECONDARY MENU 
 OPTIONS (#203) field") 
          D MES^XPDUTL("in the NEW PERSON (#200) file...") 
          N LRDUZ 
          S LRDUZ=0 
          F  S LRDUZ=$O(^VA(200,LRDUZ)) Q:'LRDUZ  D 
          . N DIK,DA 
          . Q:'$O(^VA(200,LRDUZ,203,0)) 
          . S DA(1)=LRDUZ,DIK="^VA(200,"_DA(1)_",203,",DIK(1)=".01^AD" D 
 ENALL^DIK 
          D MES^XPDUTL("Done re-indexing.") 
          Q 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LSRP
KEYWORDS: ROLLBACK
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: MAR 07, 2011

NUMBER: 5613                            IA #: 5613
  DATE CREATED: MAR 02, 2011            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: XOBDATA RPC CONTEXT VARIABLE
 GENERAL DESCRIPTION:   North Chicago (JV package) may access the subscripted
 variable XOBDATA("XOB RPC","RPC CONTEXT")) during VistALink RPC execution, to 
 obtain the "B"-type context option authorizing the execution of the RPC to the
 user. 
  
 This agreement will expire when VistALink is patched to properly set XQY
 during RPC execution when the VistALink client is a WebLogic/J2EE server.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTALINK
COMPONENT/ENTRY POINT: Environment During RPC Execution
VARIABLES: XOBDATA                      TYPE: Used
 VARIABLES DESCRIPTION:   During VistALink RPC execution, the variable: 
  
   XOBDATA("XOB RPC","RPC CONTEXT")) 
  
 is set to the encrypted RPC context ("B"-type option) used to authorize access
 to the user executing the RPC.  
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
  DATE ACTIVATED: APR 22, 2011

NUMBER: 5614                            IA #: 5614
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19,
  DATE CREATED: MAR 02, 2011            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ/WRITE ACCESS W/FILEMAN TO LOCK FIELD (#3)
  ID: DIC(19,
GLOBAL REFERENCE: DIC(19,DA,0)
FIELD NUMBER: 3                         FIELD NAME: LOCK
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Additional package(s) have been added to this ICR as
 subscribers.      The listed packages may use standard FileMan APIs such as
 $$GET1^DIQ to read the current value of the NAME and LOCK fields.       It may
 also be used to delete the current value of the LOCK field from an   existing
 option during a patch install since KIDS does not provide that capability. 
 The ICR supports the back-out/rollback process.  
  
 1) The following FileMan API is used to query for the NAME field (#.01) and
 the LOCK field (#3) in the OPTION file (#19): 
  
    D LIST^DIC(19,"","@;.01I;.01;3I;3","PQ","","","","",LRSCR,"",,"LRMSG") 
  
    where LRSCR="I ($E(^(0),1,2)=""LA""!($E(^(0),1,2)=""LR""))" 
  
 2) The following FileMan API is used to update the LOCK field (#3) in the
 OPTION file (#19): 
  
    S LRFDA(19,LROPT_",",3)=LRVALI 
    D FILE^DIE("","LRFDA","LRMSG") 
  
    where LROPT is the OPTION file (#19) IEN 
          LRVALI is the Name of the Key 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LSRP
KEYWORDS: ROLLBACK
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: FEE BASIS
 SUBSCRIBING DETAILS:   Fee Basis added as a subscriber on 7/6/15.  
  DATE ACTIVATED: MAR 07, 2011

NUMBER: 5615                            IA #: 5615
  FILE NUMBER: 19.2                     GLOBAL ROOT: DIC(19.2,
  DATE CREATED: MAR 07, 2011            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS W/FILEMAN TO OPTION SCHEDULING FILE (#19.2)
  ID: DIC(19.2,
GLOBAL REFERENCE: DIC(19.2,DA,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: QUEUED TO RUN AT WHAT TIME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DEVICE FOR QUEUED JOB OUTPUT
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: QUEUED TO RUN ON VOLUME SET
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: RESCHEDULING FREQUENCY
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: SPECIAL QUEUEING
  LOCATION: 0;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(19.2,DA,1.1)
FIELD NUMBER: 11                        FIELD NAME: USER TO RUN TASK
  LOCATION: 1.1;1                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(19.2,DA,3)
FIELD NUMBER: 15                        FIELD NAME: TASK PARAMETERS
  LOCATION: 3;E1,245                    ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(19.2,DA(1),2,0)
FIELD NUMBER: 10                        FIELD NAME: OTHER PARAMETERS
  LOCATION: 2;0                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Laboratory System Re-engineering project (LSRP)
 Rollback Tool Kit (RTK) uses FileMan API(s) to query information in the OPTION
 SCHEDULING file (#19.2) for the Preservation step in the RTK.  
     
 1) The following FileMan API is used to query for the NAME (#.01), QUEUED TO
 RUN AT WHAT TIME (#2), DEVICE FOR QUEUED JOB OUTPUT (#3), QUEUED TO RUN ON
 VOLUME SET (#5), RESCHEDULING FREQUENCY (#6), SPECIAL QUEUEING (#9), USER TO
 RUN TASK (#11) and TASK PARAMETERS (#15) fields in the OPTION SCHEDULING file
 (#19.2): 
     
    D LIST^DIC(19.2,"",LRFLDS,"PQ","","","","",LRSCR,"",LRQRY,"LRMSG") 
  
    where LRFLDS="@;.01;2;3;5;6;9;11;15" 
          LRSCR="N LRX S LRX=$G(^DIC(19,+^(0),0)) I ($E(LRX,1,2)=""LA""! 
                 ($E(LRX,1,2)=""LR"")),$E(LRX,1,3)'=""LRJ"",$E(LRX,1,4) 
                 '=""LA7J""" 
  
 2) The following FileMan API is used to query the OTHER PARAMETERS (#10) 
 subfile (#19.21) field in the OPTION SCHEDULING file (#19.2): 
  
    D GETS^DIQ(19.2,LRIEN_",","10*","E","LROTHER","LRMSG") 
  
    where LRIEN is the OPTION SCHEDULING file (#19.2) IEN 
  
 3) The following FileMan API(s) are used to look-up and display an entry in
 the OPTION SCHEDULING file (#19.2): 
  
    S DA=+$$FIND1^DIC(19.2,"","XQ",LROPTI,"B","","LRERR") 
    I 'DA Q 
    S DIC="^DIC(19.2," 
    S DIQ(0)="" 
    D EN^DIQ 
  
    where LROPTI is the OPTION file (#19) IEN 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LSRP
KEYWORDS: ROLLBACK
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: MAR 08, 2011

NUMBER: 5616                            IA #: 5616
  FILE NUMBER: 391.71                   GLOBAL ROOT: VAT(391.71
  DATE CREATED: MAR 21, 2011            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ADT/HL7 PIVOT FILE IEN
  ID: VAT(391.71
 GENERAL DESCRIPTION:   Lab Service is allowed Fileman Read access to return
 the ADT/HL7 Pivot IEN via the "D" cross reference.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PIVOT
KEYWORDS: IEN
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   Use of the Internal Entry Number for entries in the
 ADT/HL7 PIVOT file (#391.71) is allowed.  FIND1^DIC uses the PIVOT NUMBER
 (indexed by the "D" cross reference) to find the IEN for the desired ADT/HL7
 PIVOT file record.  
  DATE ACTIVATED: MAR 21, 2011

NUMBER: 5617                            IA #: 5617
  DATE CREATED: MAR 21, 2011
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSDSAPD
  NAME: PSSDSAPD Duration               ID: PSSDSAPD
 GENERAL DESCRIPTION:   This DBIA returns the number of minutes to the calling
 application based on the duration passed in.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$DRT(PSSDBJV)
 COMPONENT DESCRIPTION:   This component returns the number of minutes to the
 calling application based on the duration passed in.  
VARIABLES: PSSDBJV                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the duration in text format. Approved values
 are: 
  
 '60M'  represents 60 minutes.  '4H' represents 4 hours.  '3D' represents 3
 days.  '2W' represents 2 weeks.  '1L' represents 1 month.  
  
 If only a numeric is passed in, Days will be assumed.  
VARIABLES: $$DRT                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the duration converted to number of minutes.
 If the value passed in cannot be interpreted, a '-1' will be returned.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: MAY 29, 2018

NUMBER: 5618                            IA #: 5618
  DATE CREATED: MAR 24, 2011
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA5618
  STATUS: Pending

NUMBER: 5619                            IA #: 5619
  DATE CREATED: MAR 24, 2011            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FBARCH0
  NAME: PROJECT ARCH                    ID: FBARCH0
 GENERAL DESCRIPTION:   
  
 This Integration agreement provides two functions.  The output data comes from
 the ARCH ELIGIBILITY multiple from Fee Basis Patient file #161.  
  
 $$ELIG^FBARCH0  - lists the ARCH (Access Received Closer to Home) eligibility
 for a patient on a specific date range.  
  
 $$LIST^FBARCH0 - provides a list of ARCH eligible patients on a specific date
 range.  
  STATUS: Active
KEYWORDS: ARCH
COMPONENT/ENTRY POINT: ELIG
 COMPONENT DESCRIPTION:   This function returns the patient's ARCH eligibility. 
 See example below: 
  
 > S A=$$ELIG^FBARCH0(DFN,3100930,3110305,.FBDATA) ZW FBDATA A=1 
 FBDATA(1)="1^3101130" FBDATA(2)="0^3101030" FBDATA(3)="1^3100930" 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN which is DINUM to the internal entry of
 file #161.  
VARIABLES: FBBDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Starting/beginning date range of the listing.  
VARIABLES: FBEDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Ending date of the listing.  
VARIABLES: FBDATA                       TYPE: Output
 VARIABLES DESCRIPTION:   An array of patient ARCH eligibility.  
COMPONENT/ENTRY POINT: LIST
 COMPONENT DESCRIPTION:   Output of this function will be in ^TMP($J,"ARCHFEE" 
 global.  Below is the example: 
  
 >S A=$$LIST^FBARCH0(3100930,3110305) 
  
 Global ^TMP($J -- NOTE: translation in effect 
 ^TMP(540785357,"ARCHFEE",1)="12^0^3100930" 
                          2)="12^1^3100925" 
                          3)="12^0^3100920" 
                          4)="12^1^3100910" 
   Piece 1 = is the DFN 
   Piece 2 = is the ARCH Eligibility 1 = YES; 0 = NO 
   Piece 3 = date of ARCH Eligibility 
VARIABLES: FBBDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Starting/beginning date of the listing.  
VARIABLES: FBEDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Ending date of the listing.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Clinical Reminders needs two functions to list the
 patient's ARCH (Access Received Closer to Home) Eligibility of a certain date
 range and a list of all patients and their ARCH Eligibility.  
  DATE ACTIVATED: JUN 06, 2011

NUMBER: 5620                            IA #: 5620
  FILE NUMBER: 60                       GLOBAL ROOT: LAB
  DATE CREATED: MAR 29, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: JV APPLIC ACCESS TO LAB 60 FILE
  ID: LAB
GLOBAL REFERENCE: LAB(60,D0,0
FIELD NUMBER: 4                         FIELD NAME: SUBSCRIPT
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   SUBSCRIPT is the pointer to the legal subscripts in the
 LR SUBSCRIPT file.  CH for Chem, Hem, Tox, Ser, Ria, etc., MI for
 Microbiology, BB for Blood Bank, EM for Electron Microscopy, SP for Surgical
 Pathology, , AU for Autopsy.  This field is required for all orderable tests.  
FIELD NUMBER: 98                        FIELD NAME: EDIT CODE
  LOCATION: 0;14                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Points to EXECUTE CODE file.  
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the name of the Laboratory test you are defining
 in this entry.  
FIELD NUMBER: 10                        FIELD NAME: REQUIRED TEST
  LOCATION: 0;17                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field should be YES if this is a mandatory test,
 i.e., if no data is reported, the default status is "pending".  
FIELD NUMBER: 1                         FIELD NAME: TEST COST
  LOCATION: 0;11                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The cost of the test.  
GLOBAL REFERENCE: LAB(60,D0,.2
FIELD NUMBER: 400                       FIELD NAME: DATA NAME
  LOCATION: .2;1                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   If the test is a panel, skip this entry!  If it is an
 individual test, AND IS PART OF THE CHEM, HEM, TOX, SER, RIA, ETC. area, in
 order to be able to ENTER results, must have an entry! Micro, Blood Bank,
 Anatomic Path, excluded.  
GLOBAL REFERENCE: LAB(60,D0,1,0
FIELD NUMBER: 100                       FIELD NAME: SITE/SPECIMAN
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LAB(60,D0,1,D1,0
FIELD NUMBER: .01                       FIELD NAME: SITE/SPECIMEN
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Processing specimen type for each entry in the Lab
 Collection Sample field.  Example:  Sodium can be determined on serum and
 urine.  To enter a Site/specimen, a Data name must be entered.  
FIELD NUMBER: 1                         FIELD NAME: REFERENCE LOW
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the user entered reference low value for this
 test.  
  
 If both the low and high are defined it will print in this manner: 
   low : 10 
   high : 50 
  
 If only the low is defined and it is numeric it will print in this manner: 
   low: 10 
  
 If only the low is defined and it is alphanumeric it will print in this 
 manner: 
   NORMAL 
  
 If only the high is defined and it is numeric it will print in this manner: 
  high: 50 
  
 If only the high is defined and it is alphanumeric it will print in this 
 manner: 
  >1000 
FIELD NUMBER: 2                         FIELD NAME: REFERENCE HIGH
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the user entered reference high value for this
 test.  
  
 If both the low and high are defined it will print in this manner: 
   low : 10 
   high : 50 
  
 If only the low is defined and it is numeric it will print in this manner: 
   low: 10 
  
 If only the low is defined and it is alphanumeric it will print in this 
 manner: 
   NORMAL 
  
 If only the high is defined and it is numeric it will print in this manner: 
   high: 50 
  
 If only the high is defined and it is alphanumeric it will print in this 
 manner: 
   >1000 
FIELD NUMBER: 3                         FIELD NAME: CRITICAL LOW
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the user entered critical low value for this
 test.  Used to flag results.  
  
 If both the low and high are defined it will print in this manner: 
  low : 10 
  high : 50 
  
 If only the low is defined and it is numeric it will print in this manner: 
  low: 10 
  
 If only the low is defined and it is alphanumeric it will print in this 
 manner: 
  NORMAL 
  
 If only the high is defined and it is numeric it will print in this manner: 
  high: 50 
  
 If only the high is defined and it is alphanumeric it will print in this 
 manner: 
  >1000 
FIELD NUMBER: 4                         FIELD NAME: CRITICAL HIGH
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the user entered critical high value of this
 test.  Used to flag results.  
  
 If both the low and high are defined it will print in this manner: 
  low : 10 
  high : 50 
  
 If only the low is defined and it is numeric it will print in this manner: 
  low: 10 
  
 If only the low is defined and it is alphanumeric it will print in this 
 manner: 
   NORMAL 
  
 If only the high is defined and it is numeric it will print in this manner: 
   high: 50 
  
 If only the high is defined and it is alphanumeric it will print in this 
 manner: 
   >1000 
FIELD NUMBER: 6                         FIELD NAME: UNITS
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   UNITS represents such things as grams, number of items
 per cubic millimeter, or microliter.  
GLOBAL REFERENCE: LAB(60,D0,8,0
FIELD NUMBER: .01                       FIELD NAME: INSTITUTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the appropriate institution/division this test is
 performed at.  If this test is part of a panel that does not have an accession
 area defined for the panel, that panel will be expanded based on the 
 institution/division the program is operating under.  I.e., if the institution
 doesn't find a match, the panel test ordered will not include this test.  
FIELD NUMBER: 1                         FIELD NAME: ACCESSION AREA
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the appropriate accession area for this test.  If
 the test is a panel, all tests on that panel will be assigned to the entered
 accession area.  If some of the panel's tests go to other accession areas,
 leave this field blank.  This will be the default accession area for this
 test.  
GLOBAL REFERENCE: LAB(60,D0,2,0
FIELD NUMBER: 200                       FIELD NAME: LAB TEST INCLUDED IN PANEL
  LOCATION: 2;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Enter only if this is a panel of other tests, e.g. if the
 "Laboratory Test" is ELECTROLYTES, the entries here might be, NA, CL, K, CO2. 
 If it's an ADMIT PROFILE, they might be ELECTROLYTES, LIVER FUNCTION, CARDIAC 
 ENZYMES.  
GLOBAL REFERENCE: LAB(60,D0,2,D1,0
FIELD NUMBER: .01                       FIELD NAME: LAB TEST
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   If the entry is to be changed or the number sequence is
 to be changed, the entry must be first deleted to be moved to a different
 position in the panel.  
 GENERAL DESCRIPTION:   The JV application (James A Lovell Federal Health Care
 Center) requests access to file LAB(60 which holds the names and ordering and
 display of tests.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   The Laboratory Order file (60) is accessed when
 processing Lab Accessions from DoD.  Our software reads various fields from
 this file in order to store information for the Accession into VistA.  
  DATE ACTIVATED: APR 07, 2011

NUMBER: 5621                            IA #: 5621
  FILE NUMBER: 69.9                     GLOBAL ROOT: LAB(69.9
  DATE CREATED: MAR 30, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: DBIA-5621                       ID: LAB(69.9
GLOBAL REFERENCE: LAB(69.9,D0,OR
FIELD NUMBER: 150.1                     FIELD NAME: DEFAULT NATURE OF ORDER
  LOCATION: OR;1                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the default Nature of order for orders placed
 with Lab options.  This field points to OE/RR's Nature of order file.  
FIELD NUMBER: 150.2                     FIELD NAME: DEFAULT DC REASON
  LOCATION: OR;2                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the default DC Reason used when orders are
 canceled or deleted with Lab options.  This field points to OE/RR's Order
 Reason file.  
 GENERAL DESCRIPTION:   This file holds specific information which defines
 certain site parameters relating to the actual functioning of your laboratory. 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
  EXPIRATION DATE: APR 25, 2011
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   When DoD discontinues a Lab order, we access the
 Default Reason field in the Laboratory Site file.  

NUMBER: 5622                            IA #: 5622
  FILE NUMBER: 63                       GLOBAL ROOT: LR(63
  DATE CREATED: MAR 31, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: DBIA-5622                       ID: LR(63
GLOBAL REFERENCE: LR(D0,0
FIELD NUMBER: .02                       FIELD NAME: PARENT FILE
  LOCATION: O;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The file where the name of this entry may be found.  
FIELD NUMBER: .03                       FIELD NAME: NAME
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The internal file number in the parent file for this
 entry.  
FIELD NUMBER: .05                       FIELD NAME: ABO GROUP
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   ABO blood group of patient 
GLOBAL REFERENCE: LR(D0,BB,0
FIELD NUMBER: 1                         FIELD NAME: BLOOD BANK
  LOCATION: BB;0                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is blood bank data on this patient, DATE Multiple
 #63.01.  
GLOBAL REFERENCE: LR(D0,BB,D1,0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME SPECIMEN TAKEN
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the date/time the specimen was collected.  
FIELD NUMBER: .06                       FIELD NAME: ACCESSION NUMBER
  LOCATION: 0;6                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the blood bank accession. 
FIELD NUMBER: .08                       FIELD NAME: WARD
  LOCATION: 0;8                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the requesting location. 
FIELD NUMBER: .1                        FIELD NAME: DATE/TIME RECEIVED
  LOCATION: 0;10                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the date/time the sample was received at the
 blood bank.  
GLOBAL REFERENCE: LR(D0,EM,0
FIELD NUMBER: 2                         FIELD NAME: EM 
  LOCATION: EM;0                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is patient data from electron microscopy (EM).  
GLOBAL REFERENCE: LR(D0,EM,D1,0
FIELD NUMBER: .1                        FIELD NAME: DATE/TIME SPECIMEN RECEIVED
  LOCATION: 0;10                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the date/time the specimen was received.  
FIELD NUMBER: .06                       FIELD NAME: EM ACC #
  LOCATION: 0;6                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the accession number of the electron microscopy
 specimen.  
FIELD NUMBER: .08                       FIELD NAME: PATIENT LOCATION
  LOCATION: 0;8                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the requesting location.  
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME SPECIMEN TAKEN
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the date/time of collection of the EM specimen.  
GLOBAL REFERENCE: LR(D0,CH,0
FIELD NUMBER: 4
  FIELD NAME: CHEM, HEM, TOX, RIA, SER, etc
  LOCATION: CH;0                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Multiple field for Chem., Hem., Tox., RIA, Ser., etc.
 results.  
GLOBAL REFERENCE: LR(D0,CH,D1,0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME SPECIMEN TAKEN
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the date/time the specimen was taken.  
FIELD NUMBER: .03                       FIELD NAME: DATE REPORT COMPLETED
  LOCATION: 0;3                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the date the report was completed.  
FIELD NUMBER: .04                       FIELD NAME: VERIFY PERSON
  LOCATION: 0;4                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the person verifying the report.  
FIELD NUMBER: .06                       FIELD NAME: ACCESSION
  LOCATION: 0;6                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the accession for this specimen.  
FIELD NUMBER: .11                       FIELD NAME: REQUESTING LOCATION  
  LOCATION: 0;11                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the requesting location.  
GLOBAL REFERENCE: LR(D0,CH,D1,1,0
FIELD NUMBER: .99                       FIELD NAME: COMMENT
  LOCATION: 1;0                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   These are the comments on the tests.  
GLOBAL REFERENCE: LR(D0,CH,D1,1,D2,0
FIELD NUMBER: .01                       FIELD NAME: COMMENT
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is a comment reported with CHEM, HEM, TOX, etc.,
 data.  
GLOBAL REFERENCE: LR(D0,CH,D1,NPC
FIELD NUMBER: .12                       FIELD NAME: NEW PERSON CONVERSION
  LOCATION: NPC;1                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is to indicate that this entry has all of the
 pointers converted to the NEW PERSON file. The use of the NEW PERSON file
 began with Version 5.2 
GLOBAL REFERENCE: LR(D0,CH,D1,ORU
FIELD NUMBER: .31                       FIELD NAME: UID
  LOCATION: ORU;1                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the UID used by the HOST LEDI system for this
 order/accession.  This field is used by LEDI software.  
FIELD NUMBER: .32                       FIELD NAME: ORDERING SITE
  LOCATION: ORU;2                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field contains the pointer to the INSTITUTION file
 for the MailMan domain location of the computer system. All LEDI results are
 returned to the Ordering computer system. Location to send LEDI HL7 result
 messages.  
FIELD NUMBER: .33                       FIELD NAME: COLLECTING SITE
  LOCATION: ORU;3                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field contain the pointer to the INSTITUTION file
 for the actual collection site. The ordering site is the MailMan location of
 the computer system. MailMan domain location and the collecting site may be
 different.  This field is used by LEDI software.  
FIELD NUMBER: .34                       FIELD NAME: HOST UID
  LOCATION: ORU;4                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Each Order/Accession is given a HOST UID. The UID is
 stored in this location. If LEDI software is used to accession specimens,
 usually the collecting sites UID is used to track specimens. If the collecting
 UID conflict is the HOST system number sequence, the HOST UID will be used 
 instead of the collecting site's UID. This field is used by LEDI software.  
FIELD NUMBER: .342                      FIELD NAME: ORDERING SITE UID
  LOCATION: ORU;5                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field contains the collecting sites UID for this
 specimen. This field is used by LEDI software.  
GLOBAL REFERENCE: LR(D0,MI,0
FIELD NUMBER: 5                         FIELD NAME: MICROBIOLOGY
  LOCATION: MI;0                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is microbiology data associated with this patient.  
GLOBAL REFERENCE: LR(D0,MI,D1,0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME SPECIMEN TAKEN
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the date/time of collection of the microbiology
 specimen.  
FIELD NUMBER: .06                       FIELD NAME: MICROBIOLOGY ACCESSION
  LOCATION: 0;6                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the microbiology accession.  
FIELD NUMBER: .08                       FIELD NAME: WARD
  LOCATION: 0;8                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the requesting location.  
FIELD NUMBER: .1                        FIELD NAME: DATE/TIME RECEIVED
  LOCATION: 0;10                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the date/time the specimen was received.  
GLOBAL REFERENCE: LR(D0,MI,D1,99
FIELD NUMBER: .99                       FIELD NAME: COMMENT ON SPECIMEN
  LOCATION: 99;1                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is a comment on the specimen.  
GLOBAL REFERENCE: LR(D0,MI,D1,1
FIELD NUMBER: 11                        FIELD NAME: BACT RPT DATE APPROVED
  LOCATION: 1;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the approval date of bacteriology data for this
 specimen.  
FIELD NUMBER: 11.5                      FIELD NAME: BACT RPT STATUS
  LOCATION: 1;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the report status of the bacteriology data.  
FIELD NUMBER: 11.55                     FIELD NAME: BACT PERSON
  LOCATION: 1;3                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the person entering the bacteriology data.  
GLOBAL REFERENCE: LR(D0,MI,D1,3,0
FIELD NUMBER: 12                        FIELD NAME: ORGANISM
  LOCATION: 3;0                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   These are the organisms reported on this specimen.  
GLOBAL REFERENCE: LR(D0,MI,D1,5
FIELD NUMBER: 14                        FIELD NAME: PARASITE RPT DATE APPROVED
  LOCATION: 5;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the approval date of the parasitology data.  
FIELD NUMBER: 15                        FIELD NAME: PARASITE RPT STATUS
  LOCATION: 5;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the status  of the parasitology data.  
FIELD NUMBER: 15.5                      FIELD NAME: PARASITE ENTERING PERSON
  LOCATION: 5;3                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the person entering the parasitology data.  
GLOBAL REFERENCE: LR(D0,MI,D1,6,0
FIELD NUMBER: 16                        FIELD NAME: PARASITE
  LOCATION: 6;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   These are the parasites reported on this specimen.  
GLOBAL REFERENCE: LR(D0,MI,D1,8
FIELD NUMBER: 18                        FIELD NAME: MYCOLOGY RPT DATE APPROVED
  LOCATION: 8;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the date of approval of the mycology report.  
FIELD NUMBER: 19                        FIELD NAME: MYCOLOGY RPT STATUS
  LOCATION: 8;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the status of the mycology report.  
FIELD NUMBER: 19.5                      FIELD NAME: MYC PERSON
  LOCATION: 8;3                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the person entering the mycology data.  
GLOBAL REFERENCE: LR(D0,MI,D1,9,0
FIELD NUMBER: 20                        FIELD NAME: FUNGUS/YEAST
  LOCATION: 9;0                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   These are the fungus/yeast reported on this specimen.  
GLOBAL REFERENCE: LR(D0,MI,D1,11
FIELD NUMBER: 22                        FIELD NAME: TB RPT DATE APPROVED
  LOCATION: 11;1                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the approval date of mycobacterium data for this
 specimen.  
FIELD NUMBER: 23                        FIELD NAME: TB RPT STATUS
  LOCATION: 11;2                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the status of the report.  
FIELD NUMBER: 24                        FIELD NAME: ACID FAST STAIN
  LOCATION: 11;3                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the acid fast stain result.  
FIELD NUMBER: 25                        FIELD NAME: QUANTITY 
  LOCATION: 11;4                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the quantity of the mycobacterium present.  
FIELD NUMBER: 25.5                      FIELD NAME: TB ENTERING PERSON
  LOCATION: 11;5                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the person entering the mycobacterium data.  
GLOBAL REFERENCE: LR(D0,MI,D1,16
FIELD NUMBER: 33                        FIELD NAME: VIROLOGY RPT DATE
  LOCATION: 16;1                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the approval date of virology data for this
 specimen.  
FIELD NUMBER: 34                        FIELD NAME: VIROLOGY REPORT STATUS
  LOCATION: 16;2                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the report status of virology.  
FIELD NUMBER: 35                        FIELD NAME: VIROLOGY ENTERING PERSON
  LOCATION: 16;3                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the person entering the virology data.  
GLOBAL REFERENCE: LR(D0,MI,D1,NPC
FIELD NUMBER: 38                        FIELD NAME: NEW PERSON CONVERSION
  LOCATION: NPC;1                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field is to indicate that this entry has all of the
 pointers converted to the NEW PERSON file. The use of the NEW PERSON file.
 began with Version 5.2.  
  
 TECHNICAL DESCR: This field will be used to determine if archive data should
 be repointed to VA(200 before being restored the ^LR( global.  
GLOBAL REFERENCE: LR(D0,MI,D1,ORU
FIELD NUMBER: .31                       FIELD NAME: UID
  LOCATION: ORU;1                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the UID used by the HOST LEDI system for this
 order/accession.  This field is used by LEDI software.  
FIELD NUMBER: .32                       FIELD NAME: ORDERING SITE
  LOCATION: ORU;2                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field contains the pointer to the INSTITUTION file
 for the Mailman domain location of the computer system. All LEDI results are
 returned to the Ordering computer system. Location to send LEDI HL7 result
 messages.  This field is used by LEDI software.  
FIELD NUMBER: .33                       FIELD NAME: COLLECTING SITE
  LOCATION: ORU;3                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field contains the pointer to the INSTITUTION file
 for the actual collection site. The ordering site is the MailMan location for
 the computer system. MailMan domain location and the collecting site may be 
 different.  This field is used by LEDI.  
FIELD NUMBER: .34                       FIELD NAME: HOST UID
  LOCATION: ORU;4                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Each order/accession is given a HOST UID. The UID is
 stored in this location. If LEDI software is used to accession specimens,
 usually the collecting sites UID is used to track specimens. If the collecting
 UID conflicts with the HOST system number sequence, the HOST UID will be used 
 instead of the collecting site's UID. This field is used by LEDI software.  
FIELD NUMBER: .342                      FIELD NAME: ORDERING SITE UID
  LOCATION: ORU;5                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field contains the collecting sites UID for this
 specimen. This field is used by LEDI software.  
GLOBAL REFERENCE: LR(D0,MI,D1,ORUT,0
FIELD NUMBER: .35                       FIELD NAME: ORDERED TEST
  LOCATION: ORUT;0                      ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This subfile contains information about the ordered
 test(s) for this accession. The .01 field contains the ordered test NLT code
 requested by the clinical provider.  If this test is a panel, all atomic tests
 within the panel will be associated with the ordered test using this NLT code. 
 
GLOBAL REFERENCE: LR(D0,MI,D1,ORUT,D2,0
FIELD NUMBER: .01                       FIELD NAME: ORDERED TEST
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the ordered test NLT code requested
 by the clinical provider.  If this test is a panel, all atomic tests within
 the panel will be associated with the ordered test using this NLT code.  
GLOBAL REFERENCE: LR(D0,SP,0
FIELD NUMBER: 8                         FIELD NAME: SURGICAL PATHOLOGY
  LOCATION: SP;0                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the surgical pathology for this patient.  
GLOBAL REFERENCE: LR(D0,SP,D1,0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME SPECIMEN TAKEN
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the date/time the specimen was taken.  
FIELD NUMBER: .06                       FIELD NAME: SURGICAL PATH ACC #
  LOCATION: 0;6                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the accession number of the surgical pathology
 specimen.  
FIELD NUMBER: .08                       FIELD NAME: PATIENT LOCATION
  LOCATION: 0;8                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the requesting location.  
FIELD NUMBER: .1                        FIELD NAME: DATE/TIME SPECIMEN RECEIVED
  LOCATION: 0;10                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the date/time the specimen was received.  
GLOBAL REFERENCE: LR(DO,CY,0
FIELD NUMBER: 9                         FIELD NAME: CYTOPATHOLOGY
  LOCATION: CY;0                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Cytopathology data associated with this patient.  
GLOBAL REFERENCE: LR(D0,CY,D1,0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME SPECIMEN TAKEN
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the date/time of collection of the specimen.  
FIELD NUMBER: .06                       FIELD NAME: CYTOPATH ACC #
  LOCATION: 0;6                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the accession number of the cytopathology
 specimen.  
FIELD NUMBER: .08                       FIELD NAME: PATIENT LOCATION
  LOCATION: 0;8                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the requesting location.  
FIELD NUMBER: .1                        FIELD NAME: DATE/TIME SPECIMEN RECEIVED
  LOCATION: 0;10                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the date/time the specimen was received.  
GLOBAL REFERENCE: LR(D0,MI,D1,2,0
FIELD NUMBER: 11.6                      FIELD NAME: GRAM STAIN
  LOCATION: 2;0                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   These are gram stain results.  
GLOBAL REFERENCE: LR(D0,MI,D1,2,D2,0
FIELD NUMBER: .01                       FIELD NAME: GRAM STAIN
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the gram stain result.  
GLOBAL REFERENCE: LR(D0,MI,DI,3,D2,0
FIELD NUMBER: .01                       FIELD NAME: ORGANISM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is an organism identified on this specimen.  
GLOBAL REFERENCE: LR(D0,MI,D1,4,0
FIELD NUMBER: 13                        FIELD NAME: BACT RPT REMARK
  LOCATION: 4;0                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   These are report remarks on bacteriology data.  
GLOBAL REFERENCE: LR(D0,MI,D1,4,D2,0
FIELD NUMBER: .01                       FIELD NAME: BACT RPT REMARK
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is a report remark on bacteriology data.  
GLOBAL REFERENCE: LR(D0,MI,D1,6,D2,0
FIELD NUMBER: .01                       FIELD NAME: PARASITE 
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the parasite identified on this specimen 
GLOBAL REFERENCE: LR(D0,MI,D1,6,D2,1,0
FIELD NUMBER: 1                         FIELD NAME: STAGE
  LOCATION: 1;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   These are the stages identified with this parasite.  
GLOBAL REFERENCE: LR(D0,MI,D1,6,D2,1,D3,0
FIELD NUMBER: .01                       FIELD NAME: STAGE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the stage identified with this parasite.  
GLOBAL REFERENCE: LR(D0,MI,D1,7,0
FIELD NUMBER: 17                        FIELD NAME: PARASITE RPT REMARK
  LOCATION: 7;0                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   These are report remarks on the parasitology data.  
GLOBAL REFERENCE: LR(D0,MI,D1,7,D2,0
FIELD NUMBER: .01                       FIELD NAME: PARASITE RPT REMARK
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   These are report remarks on the parasitology data.  
GLOBAL REFERENCE: LR(D0,MI,D1,9,D2,0
FIELD NUMBER: .01                       FIELD NAME: FUNGUS/YEAST
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The entity indentified from the Etiology Field file
 (#61.2).  
GLOBAL REFERENCE: LR(D0,MI,D1,15,0
FIELD NUMBER: 19.6                      FIELD NAME: MYCOLOGY SMEAR/PREP
  LOCATION: 15;0                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   These are the results of the smear/prep in mycology.  
GLOBAL REFERENCE: LR(D0,MI,D1,15,D2,0
FIELD NUMBER: .01                       FIELD NAME: MYCOLOGY SMEAR/PREP
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: LR(D0,MI,D1,10,0
FIELD NUMBER: 21                        FIELD NAME: MYCOLOGY RPT REMARK
  LOCATION: 10;0                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   These are report remarks on the mycology data.  
GLOBAL REFERENCE: LR(D0,MI,D1,10,D2,0
FIELD NUMBER: .01                       FIELD NAME: MYCOLOGY RPT REMARK
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: LR(D0,MI,D1,12,0
FIELD NUMBER: 26                        FIELD NAME: MYCOBACTERIUM
  LOCATION: 12;0                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   These are the mycobacterium identified with this
 specimen.  
GLOBAL REFERENCE: LR(D0,MI,D1,12,D2,0
FIELD NUMBER: .01                       FIELD NAME: MYCOBACTERIUM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the mycobacterium identified with this specimen.  
FIELD NUMBER: 1                         FIELD NAME: QUANTITY
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the quantity of the mycobacterium present.  
GLOBAL REFERENCE: LR(D0,MI,D1,13,0
FIELD NUMBER: 27                        FIELD NAME: TB RPT REMARK
  LOCATION: 13;0                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   These are report remarks on the mycobacterium data.  
GLOBAL REFERENCE: LR(D0,MI,D1,13,D2,0
FIELD NUMBER: .01                       FIELD NAME: TB RPT REMARK
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is a report remark on the mycobacterium data.  
GLOBAL REFERENCE: LR(D0,MI,D1,17,0
FIELD NUMBER: 36                        FIELD NAME: VIRUS
  LOCATION: 17;0                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   These are the viruses reported on this specimen.  
GLOBAL REFERENCE: LR(D0,MI,D1,17,D2,0
FIELD NUMBER: .01                       FIELD NAME: VIRUS
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the virus reported on this specimen.  
GLOBAL REFERENCE: LR(D0,MI,D1,18,0
FIELD NUMBER: 37                        FIELD NAME: VIROLOGY RPT REMARK
  LOCATION: 18;0                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   These are report remarks for virology.  
GLOBAL REFERENCE: LR(D0,MI,D1,18,D2,0
FIELD NUMBER: .01                       FIELD NAME: VIROLOGY RPT REMARK
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is a report remark for virology.  
 GENERAL DESCRIPTION:   The Federal Health Care Center project requires access
 to Lab Service File LR(63 - Lab Data File - for its Orders Portability
 requirement.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   Our code accesses the Lab Data file (63) when receiving
 Lab orders, accessions and results from DoD.  This is one of several files
 into which the DoD originating data is stored. 

NUMBER: 5623                            IA #: 5623
  DATE CREATED: MAR 31, 2011
  CUSTODIAL PACKAGE: NATIONAL HEALTH INFO NETWORK
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: NHIN GET VISTA DATA
 GENERAL DESCRIPTION:   This RPC pulls data from VistA and returns it in an
 array formatted as XML.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MEDICAL DOMAN WEB SERVICE
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD

NUMBER: 5624                            IA #: 5624
  FILE NUMBER: 68                       GLOBAL ROOT: LRO
  DATE CREATED: APR 04, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: DBIA-5624                       ID: LRO
GLOBAL REFERENCE: LRO(68,D0,0
FIELD NUMBER: .01                       FIELD NAME: AREA
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The accession area of the Lab.  
FIELD NUMBER: .02                       FIELD NAME: LR SUBSCRIPT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This represents the functional area of the Lab. Must be
 chosen from a set of codes.  
FIELD NUMBER: .04
  FIELD NAME: COMMON ACCESSION #'S WITH AREA
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   If another accession area is designated here, that other
 accession area will be used to find the next "available" accession number
 which will be updated on the other accession area.  
FIELD NUMBER: .09                       FIELD NAME: ABBREVIATION
  LOCATION: 0;11                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Abbreviation for the accession area.  Must have
 programmer privileges to alter this entry.  
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.  If this field is not filled in, CP
 (Clinical Pathology ) will be assumed.  
  
 TECHNICAL DESCR:    There can only be two possible laboratory divisions.  
 Anatomical Pathology or Clinical Pathology.  This field is used to group 
 workload reports and data.  
GLOBAL REFERENCE: LR0(68,D0,.1
FIELD NUMBER: .051                      FIELD NAME: ACC CODE
  LOCATION: .1;1                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Mumps code that is triggered by the Accession Transform
 field.  
  
 NOTES: TRIGGERED by the ACCESSION TRANSFORM field of the ACCESSION File.  
GLOBAL REFERENCE: LRO(68,D0,.4
FIELD NUMBER: .4                        FIELD NAME: NUMERIC IDENTIFIER
  LOCATION: .4;1                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field is used to build the unique accession
 identifier number.  It is used as the first two characters of the number.  Use
 the numbers 1-9 and uppercase letters A-Z to designate the identifier. For
 example, if you enter 99 all accession identifiers for this accession area
 will start with 99, e.g. 9923400025.  
                                  
 If a single character is used the system will append a leading zero to the 
 unique identifier generated.  
                                  
 No two accession areas can use the same identifier.  
                                  
 Changing the identifier should only be performed when accessioning is not 
 occurring and when a situation requires it since personnel will memorize this
 identifier as representing the accesson area.  
                                  
 Do NOT switch identifiers between active accession areas since this could 
 compromise the uniqueness of the resulting unique identifier (UID). The 
 software when generating a UID checks for the existence of the UID it will 
 create for an accession. If it currently exists the UID being created will 
 have "00" as the numeric identifier.  
GLOBAL REFERENCE: LRO(68,D0,1,0
FIELD NUMBER: 2                         FIELD NAME: DATE
  LOCATION: 1;0                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The date of the accession.  
GLOBAL REFERENCE: LR0(68,D0,1,D1,0
FIELD NUMBER: .01                       FIELD NAME: DATE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The date of the accession.  
GLOBAL REFERENCE: LRO(68,D0,1,D1,1,0
FIELD NUMBER: 1                         FIELD NAME: ACCESSION NUMBER
  LOCATION: 1;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The numeric part of the accession.  
GLOBAL REFERENCE: LRO(68,D0,1,D1,1,D2,0
FIELD NUMBER: .01                       FIELD NAME: LRDFN 
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The internal pointer to file 63 is stored here.  
FIELD NUMBER: 1                         FIELD NAME: FILE #
  LOCATION: 0;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The pointer to the File of Files for the entity in field
 .01 is stored here.  
FIELD NUMBER: 2                         FIELD NAME: ORIGINAL ACCN DATE
  LOCATION: 0;3                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The date part of the original accession is stored here.  
FIELD NUMBER: 3                         FIELD NAME: DATE ORDERED
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The date the order was placed is stored here.  
FIELD NUMBER: 4                         FIELD NAME: SPECIMEN NUMBER
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The internal specimen number is stored here.  
FIELD NUMBER: 5                         FIELD NAME: IDENTITY
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The identity from e.g. reference labs etc. is stored
 here.  
FIELD NUMBER: 6                         FIELD NAME: REPORT ROUTING LOCATION
  LOCATION: 0;6                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The service/location from which the original order came. 
 The report is routed back to this location.  
FIELD NUMBER: 6.5                       FIELD NAME: PROVIDER 
  LOCATION: 0;8                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The internal number of the provider requesting the
 test(s) is stored here.  
FIELD NUMBER: 6.6                       FIELD NAME: TREATING SPECIALITY 
  LOCATION: 0;9                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The treating specialty of the location requesting the
 test.  
  
 TECHNICAL DESCR: This node may be set from the default treating specialty 
 field (#607) of the LABORATORY SITE file (#69.9). The 19th. peice of LRPARAM
 variable.  
FIELD NUMBER: 6.7                       FIELD NAME: LOG-IN PERSON
  LOCATION: 0;10                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The pointer to the person (NEW PERSON file) creating this
 accession is stored here.  
FIELD NUMBER: 92                        FIELD NAME: LOCATION TYPE
  LOCATION: 0;11                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field holds the type of hospital location. 
 $P(^SC(X,0),U,3) It is used primarily for WKLD calculations. Since the patient
 may be discharged or admitted before the WKLD calculation routines run.  This
 field holds a permanent location type.  
FIELD NUMBER: 94                        FIELD NAME: ORDERING LOCATION
  LOCATION: 0;13                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field contains the location placing the order for
 this patient.  
GLOBAL REFERENCE: LRO(68,D0,1,D1,1,D2,.1
FIELD NUMBER: 14                        FIELD NAME: ORDER #
  LOCATION: .1;1                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The original order number is stored here.  
GLOBAL REFERENCE: LRO(68,D0,1,D1,1,D2,.2
FIELD NUMBER: 15                        FIELD NAME: ACCESSION
  LOCATION: .2;1                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The printable form of the Accession is stored here.  
GLOBAL REFERENCE: LR(68,D0,1,D1,1,D2,.3
FIELD NUMBER: 16                        FIELD NAME: UID
  LOCATION: .3;1                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the UID used by the HOST LEDI system for this
 order/accession.  This field is used by the LEDI software.  
FIELD NUMBER: 16.1                      FIELD NAME: ORDERING SITE
  LOCATION: .3;2                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the pointer to the INSTITUTION file
 for the MailMan domain location of the computer system. All LEDI results are
 returned to the Ordering computer system.  
                                  
 Location to send LEDI HL7 result messages. This field is used by LEDI 
 software.  
FIELD NUMBER: 16.2                      FIELD NAME: COLLECTING SITE
  LOCATION: .3;3                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field contain the pointer to the INSTITUTION file
 for the actual collection site. The ordering site is the MailMan location of
 the computer system. MailMan domain location and the collecting site may be
 different.  This field is used by LEDI software.  
FIELD NUMBER: 16.3                      FIELD NAME: HOST UID
  LOCATION: .3;4                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Each Order/Accession is given a HOST UID. The UID is
 stored in this location. If LEDI software is used to accession specimens,
 usually the collecting sites UID is used to track specimens. If the collecting
 UID conflict is the HOST system number sequence, the HOST UID will be used 
 instead of the collecting site's UID. This field is used by LEDI software.  
FIELD NUMBER: 16.4                      FIELD NAME: ORDERING SITE UID
  LOCATION: .3;4                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field contains the collecting sites UID for this
 specimen. This field is used by LEDI software.  
GLOBAL REFERENCE: LRO(68,D0,1,D1,1,D2,.4
FIELD NUMBER: 26                        FIELD NAME: DIV
  LOCATION: .4;1                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field contains the division of the person ordering
 the test for this accession number. The DUZ(2) is used to determine the
 division pointer. In some cases this field may be blank, example auto
 accession controls.  
GLOBAL REFERENCE: LRO(68,D0,1,D1,1,D2,3
FIELD NUMBER: 9                         FIELD NAME: DRAW TIME
  LOCATION: 3;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The date/time the specimen was taken.  
FIELD NUMBER: 12                        FIELD NAME: LAB ARRIVAL TIME
  LOCATION: 3;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The date/time the specimen arrived at the lab.  
FIELD NUMBER: 13                        FIELD NAME: DATE/TIME RESULTS AVAILABLE 
  LOCATION: 3;4                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The date/time all results for the accession are
 available.  
FIELD NUMBER: 13.5                      FIELD NAME: INVERSE DATE
  LOCATION: 3;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   9999999 minus the internal entry in field 9 .  
GLOBAL REFERENCE: LRO(68,DO,1,D1,1,D2,4,D3,0
FIELD NUMBER: 11                        FIELD NAME: TESTS
  LOCATION: 4;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The pointers to the Laboratory Tests for this accession. 
FIELD NUMBER: .01                       FIELD NAME: TEST
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The pointers to the Laboratory Tests for this accession. 
FIELD NUMBER: 3                         FIELD NAME: TECHNOLOGIST
  LOCATION: 0;4                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The DUZ of the person verifying the test.  NOTE: This
 field previously contained technologist initials.  Converted with the release
 of version 5.2.  
FIELD NUMBER: 4                         FIELD NAME: COMPLETE DATE
  LOCATION: 0;5                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   If null, the test is incomplete.  Otherwise, it is the
 date/time of completion.  
GLOBAL REFERENCE: LRO(68,D0,1,D1,1,D2,5,0
FIELD NUMBER: 50                        FIELD NAME: SPECIMEN
  LOCATION: 5;0                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The site/specimen from the Topography Field file.  There
 may be more than one specimen for certain types of accessions.  
GLOBAL REFERENCE: LR0(68,D0,1,D1,1,D2,5,D3,0
FIELD NUMBER: .01                       FIELD NAME: SPECIMEN
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The site/specimen from the Topography field file.  There
 may be more than one specimen for certain types of accessions 
FIELD NUMBER: 1                         FIELD NAME: COLLECTION SAMPLE
  LOCATION: 0;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The collection sample is from file 62.  
GLOBAL REFERENCE: LRO(68,B
GLOBAL REFERENCE: LR0(68,AC
GLOBAL REFERENCE: LRO(68,AD
 GENERAL DESCRIPTION:   For its Orders Portability requirement, the JV
 application (Federal Health Care Center in North Chicago) request permission
 to access file (LRO(68.  This file contains entries which represent the
 functional subdivisions or departments of the laboratory, referred to by the 
 Laboratory package software as accession areas.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   For Lab accessions and results entered by DoD, our
 implementation needs to access the Accession file (68) in order to properly
 store the DoD transactions into the VistA database.  

NUMBER: 5625                            IA #: 5625
  FILE NUMBER: 69                       GLOBAL ROOT: LRO
  DATE CREATED: APR 05, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: DBIA-5625                       ID: LRO
GLOBAL REFERENCE: LRO(69,D0,0
FIELD NUMBER: .01                       FIELD NAME: DATE ORDERED
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Date of order.  
GLOBAL REFERENCE: LRO(69,D0,1,0
FIELD NUMBER: 1                         FIELD NAME: SPECIMEN #
  LOCATION: 1;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The sequential specimen number.  
GLOBAL REFERENCE: LRO(69,D0,1,D1,0
FIELD NUMBER: .01                       FIELD NAME: LRDFN
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The internal number in the Lab Data file 63.  
FIELD NUMBER: 1                         FIELD NAME: ENTERING PERSON
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Points to NEW PERSON file.  Automatically stored.  
FIELD NUMBER: 3                         FIELD NAME: COLLECTION SAMPLE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Points to the collection sample appropriate for the
 test(s) ordered.  
FIELD NUMBER: 4                         FIELD NAME: LAB,IMM OR WARD COLLECT
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This designates how the sample or specimen is to reach
 the lab.  
FIELD NUMBER: 5                         FIELD NAME: DATE/TIME ORDERED
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Date and time ordered.  
FIELD NUMBER: 7                         FIELD NAME: PROVIDER
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The person signing for the order.  Selection must be made
 from active PROVIDERS who hold the PROVIDER security key.  
FIELD NUMBER: 8                         FIELD NAME: REPORT ROUTING LOCATION
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The service or location from which the order is
 originating, and where the report will be returned.  
FIELD NUMBER: 23                        FIELD NAME: ORDERING LOCATION
  LOCATION: 0;9                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the location ordering the test and to
 whom completed results will be sent.  
FIELD NUMBER: .11                       FIELD NAME: OERR ORDER #
  LOCATION: 0;11                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field is used to store the OE/RR order number that
 links Lab with OE/RR.  
GLOBAL REFERENCE: LRO(69,D0,1,D1,.1
FIELD NUMBER: 9.5                       FIELD NAME: ORDER #
  LOCATION: .1;1                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The unique assigned order number for an ordering session
 for one "patient".  
GLOBAL REFERENCE: LRO(69,D0,1,D1,1
FIELD NUMBER: 10                        FIELD NAME: DATE/TIME OF COLLECTION 
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   When the specimen was collected from the "patient".  
FIELD NUMBER: 11                        FIELD NAME: DATE/TIME OBTAINED INEXACT 
  LOCATION: 1;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   If the time the specimen is obtained is not even
 approximate, this field is set to yes.  
FIELD NUMBER: 12                        FIELD NAME: COLLECTOR
  LOCATION: 1;3                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The phlebotomist who is accessioning the collected order. 
FIELD NUMBER: 13                        FIELD NAME: COLLECTION STATUS
  LOCATION: 1;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This indicates whether the order is collected or
 uncollected.  
FIELD NUMBER: 15                        FIELD NAME: COMMENT
  LOCATION: 1;6                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Single line comment about the order.  
FIELD NUMBER: 22                        FIELD NAME: MERGE ORDER #
  LOCATION: 1;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   if this order was merged with another order, the order
 number for that order is entered here. Automatically stuffed by the system.  
FIELD NUMBER: 25                        FIELD NAME: INSTITUTION
  LOCATION: 1;8                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   this field contains the institution entering the request
 for this particular test. This field becomes very important when dealing with 
 multi-divisional sites.  
GLOBAL REFERENCE: LRO(69,D0,1,D1,2,0
FIELD NUMBER: 6                         FIELD NAME: TEST
  LOCATION: 2;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The tests for the specimen.  
GLOBAL REFERENCE: LRO(69,D0,1,D1,2,D2,0
FIELD NUMBER: .01                       FIELD NAME: TEST/PROCEDURE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The tests for the specimen.  
FIELD NUMBER: 1                         FIELD NAME: URGENCY
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Routine, Stat, etc.  
FIELD NUMBER: 2                         FIELD NAME: ACCESSION DATE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The date piece of the accession.  
FIELD NUMBER: 3                         FIELD NAME: ACCESSION AREA
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The accession area where the test may be found. 
FIELD NUMBER: 4                         FIELD NAME: ACCESSION NUMBER
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The number piece of the accession where the test may be
 found.  
FIELD NUMBER: 5                         FIELD NAME: COMBINED ON ORDER
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   If the test has been combined with another order (i.e.,
 this test is a duplication of part of another order), this points to the order
 with which the test has been combined.  
FIELD NUMBER: 6                         FIELD NAME: OERR INTERNAL FILE #
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This provides the link to the correlate entry of the test
 ordered as it appears in OERR.  
FIELD NUMBER: 7                         FIELD NAME: PANEL EXPLODED
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Used to determine if panel with no accession area
 assigned has previously been exploded and accessioned.  
FIELD NUMBER: 8                         FIELD NAME: STATUS
  LOCATION: 0;9                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the internal status for this test.  It is used to
 identify an order when it is canceled, and/or when it is accepted by OE/RR.  
FIELD NUMBER: 9                         FIELD NAME: ORIGIN
  LOCATION: 0;10                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is how the test was ordered/entered into the system
 using the Lab (LR) options.  
FIELD NUMBER: 10                        FIELD NAME: CANCELED BY
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the person who canceled this test.  
FIELD NUMBER: 20                        FIELD NAME: COMBINED FROM
  LOCATION: 0;14                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is a reference to the entry that this test was
 combined from.  
GLOBAL REFERENCE: LRO(69,DO,1,D1,2,D2,.3
FIELD NUMBER: 13                        FIELD NAME: UID
  LOCATION: .3;1                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the UID used by the HOST LEDI system for this
 order/accession.  This field is used by LEDI software.  
FIELD NUMBER: 14                        FIELD NAME: ORDERING SITE
  LOCATION: .3;2                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the pointer to the INSTITUTION file
 for the MailMan domain location of the computer system. All LEDI results are
 returned to the Ordering computer system.  
                                  
 Location to send LEDI HL7 result messages. This field is used by LEDI 
 software.  
FIELD NUMBER: 15                        FIELD NAME: COLLECTING SITE
  LOCATION: .3;3                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field contain the pointer to the INSTITUTION file
 for the actual collection site. The ordering site is the MailMan location of
 the computer system. MailMan domain location and the collecting site may be
 different.  
                                  
 This field is used by LEDI software.  
FIELD NUMBER: 16                        FIELD NAME: HOST UID
  LOCATION: .3;4                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Each Order/Accession is given a HOST UID. The UID is
 stored in this location. If LEDI software is used to accession specimens,
 usually the collecting sites UID is used to track specimens. If the collecting
 UID conflict is the HOST system number sequence, the HOST UID will be used 
 instead of the collecting site's UID.  
                                  
 This field is used by LEDI software.  
FIELD NUMBER: 17                        FIELD NAME: ORDERING SITE UID
  LOCATION: .3;5                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field contains the collecting sites UID for this
 specimen.  
                                 
 This field is used by LEDI software.  
GLOBAL REFERENCE: LRO(69,D0,1,D1,2,D2,1,0
FIELD NUMBER: 99                        FIELD NAME: TEST COMMENTS
  LOCATION: 1;0                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: LRO(69,D0,1,D1,2,D2,1,D3,0
FIELD NUMBER: .01                       FIELD NAME: TEST COMMENTS 
  ACCESS: Write w/Fileman
FIELD NUMBER: 99.1                      FIELD NAME: CANCEL COMMENTS
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LRO(69,D0,1,D1,2,D2,1.1,D3,0
FIELD NUMBER: 99.1                      FIELD NAME: CANCEL REASON
  LOCATION: 1.1;0                       ACCESS: Read w/Fileman
FIELD NUMBER: .01                       FIELD NAME: CANCEL REASON
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LRO(69,D0,1,D1,3
FIELD NUMBER: 20                        FIELD NAME: LAB ARRIVAL TIME
  LOCATION: 3;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Lab arrival time.  
FIELD NUMBER: 21                        FIELD NAME: DATE/TIME RESULTS AVAILABLE
  LOCATION: 3;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the date/time ALL results for this specimen are
 complete.  The field is set by the software when the results are released and
 reported outside the laboratory system.  
GLOBAL REFERENCE: LRO(69,D0,1,D1,4,0
FIELD NUMBER: 2                         FIELD NAME: SPECIMEN
  LOCATION: 4;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Points to the specimen(s) for the given order. (Some
 areas of lab treat a collection of samples as a SINGLE collection "sample").  
GLOBAL REFERENCE: LRO(69,D0,1,D1,4,D2,0
FIELD NUMBER: .01                       FIELD NAME: SPECIMEN
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Points to the specimen for the given order.  
GLOBAL REFERENCE: LRO(69,D0,1,6,0
FIELD NUMBER: 16                        FIELD NAME: WARD COMMENTS ON SPECIMEN 
  LOCATION: 6;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Comments about the order.  
GLOBAL REFERENCE: LRO(69,D0,1,D1,6,D2,0
FIELD NUMBER: .01                       FIELD NAME: WARD COMMENTS ON SPECIMEN
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: LRO(69,B
 GLOBAL DESCRIPTION:   Lookup by Date 
GLOBAL REFERENCE: LRO(69,C
 GLOBAL DESCRIPTION:   Lookup by Order Number 
GLOBAL REFERENCE: LRO(69,D0,1,AA
 GLOBAL DESCRIPTION:   Lookup by Order Number 
GLOBAL REFERENCE: LRO(69,D0,1,D1,2,B
 GLOBAL DESCRIPTION:   Lookup by Test/Procedure 
 GENERAL DESCRIPTION:   This IA documents access by the JV application, the
 Federal Health Care Center at North Chicago for the Orders Portability
 requirement, to the Lab Order Entry file (69), which contains data pertinent
 to Lab tests ordered for VA patients.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   When a Lab order is entered on the DoD side, the JV
 Orders Portability software needs to store the relevant data into the Lab
 Order Entry file.  It does so through File Manager read and write APIs to
 relevant fields in this file.  

NUMBER: 5626                            IA #: 5626
  FILE NUMBER: 62                       GLOBAL ROOT: LAB
  DATE CREATED: APR 06, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: LAB COLLECTION SAMPLE
  ID: LAB
GLOBAL REFERENCE: LAB(62,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME 
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The name of the collection sample.  
  
 TECHNICAL DESCR: When this field is modified by non-interactive means, the 
 variable LRFMERTS should be defined. LRFMERTS is used by the AERT xref to 
 determine if the field is being edited by a user or by a process.  
FIELD NUMBER: 3                         FIELD NAME: TUBE TOP
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The tube top value for the collection sample.  
 GENERAL DESCRIPTION:   The Lab Collection Sample file (62) contains
 information about collection samples for lab tests.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   JV package code reads the Name and Tube Top values for
 a collection sample from File 62 when processing Lab Accessions from DoD.  
  DATE ACTIVATED: APR 27, 2011

NUMBER: 5627                            IA #: 5627
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(D0,.52)
  DATE CREATED: APR 15, 2011            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Patient File POW field (#.525)
  ID: DPT(D0,.52)
GLOBAL REFERENCE: POW STATUS INDICATED?
FIELD NUMBER: .525                      FIELD NAME: POW STATUS INDICATED?
  LOCATION: .52;5                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   
               WERE YOU A PRISONER OF WAR   
                                 'Y' FOR YES; 
                                 'N' FOR NO; 
                                 'U' FOR UNKNOWN; 
               HELP-PROMPT:      Was this patient a Prisoner of War? 
               DESCRIPTION:      For this veteran applicant enter 'Y' if s/he 
                                 was confined as a prisoner of war, 'N' if 
                                 was not, or 'U' if unknown.  Once the POW 
                                 Status is verified by the HEC, it is no 
                                 longer editable.  
  
  
 GLOBAL DESCRIPTION:   Node .52 contains Combat Related benefit eligibility
 information.  Piece 5 of the Patient file Node number .52 is POW STATUS
 INDICATED?.  
 GENERAL DESCRIPTION:   Lab is granted read access to the Patient File (#2) POW
 STATUS INDICATED? field (#.525).  
  
 ADT generates HL7 1.6 messages containing Patient Movement information.  LSRP
 converts the HL7 1.6 ADT messages into HLO formatted messages and forwards
 them to Pathnet.  Not all ADT A11 (Cancel Patient Admit) ZPD segments have the
 POW STATUS INDICATED? data populated.  When LSRP receives an ADT A11 message
 with a ZPD-17 (POW STATUS INDICATED?) containing a NULL value, POW STATUS
 INDICATED? is added to the HLO message during the HL7 1.6 to HLO conversion.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: POW
KEYWORDS: .525
KEYWORDS: PRISONER OF WAR
KEYWORDS: PATIENT POW
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   
  
   Patient File (#2) access: 
       FIELD NAME                FIELD #             ACCESS ALLOWED 
       ----------                -------             --------------
       POW STATUS INDICATED?     .525                Fileman Read 
  
  
  DATE ACTIVATED: MAY 03, 2011

NUMBER: 5628                            IA #: 5628
  GLOBAL ROOT: XUSEC(                   DATE CREATED: APR 15, 2011
  CUSTODIAL PACKAGE: IMAGING            USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: CHECK FOR MAGDISP CLIN KEY      ID: XUSEC(
GLOBAL REFERENCE: XUSEC('MAGDISP CLIN', DUZ
 GLOBAL DESCRIPTION:   CHECK FOR SECURITY KEY MAGDISP CLIN 
 GENERAL DESCRIPTION:   This ICR allows the subscribing package(s) to check for
 the MAGDISP CLIN key using the ^XUSEC global.  Reference ICR 10076 for more
 information on the XUSEC global.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAGDISP CLIN
KEYWORDS: XUSEC
KEYWORDS: IMAGING
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   
  
 Subscribing packages are allowed to check $D(^XUSEC("MAGDISP CLIN",DUZ)).  
  
  DATE ACTIVATED: MAY 03, 2011

NUMBER: 5629                            IA #: 5629
  DATE CREATED: APR 19, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Supported                      TYPE: Routine
  ROUTINE: ORKPS                        NAME: ORKPS
  ID: ORKPS
 GENERAL DESCRIPTION:   The agreement is for using the GLCREAT entry point in
 the ORKPS routine to return the CRCL value of a patient.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GLCREAT
 COMPONENT DESCRIPTION:   This extrinsic function returns a patient's (DFN)
 most recent serum creatinine within # of days from parameter ORK GLUCOPHAGE
 CREATININE results format: test id^result units flag ref range collect
 d/t^result 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN = IEN from the PATIENT file (#2) [required] 
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS

NUMBER: 5630                            IA #: 5630
  DATE CREATED: APR 19, 2011            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCAACC
  NAME: DETERMINE IF A CLAIN IS A NON-ACCRUED ACCOUNT
  ID: PRCAACC
 GENERAL DESCRIPTION:   Integrated Billing has permission to make the following
 call to AR to determine if a claim is a non-accrued account:  $ACCK^PRCAACC.
 When the user is attempting to use the IB option:  [IB CORRECT
 REJECTED/DENIED], if the claim is non-accrued ('$$ACCK^PRCAACC(IBIFN)), the
 user will be prevented from using the option and directed instead to IB
 option:  [IB COPY AND CANCEL].  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCAACC
KEYWORDS: IBCC
COMPONENT/ENTRY POINT: ACCK
 COMPONENT DESCRIPTION:   This function returns a 0 if the account/claim is
 non-accrued and should be sent to FMS. A 1 indicates the account/claim is an
 accrual.  
VARIABLES: IBIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Ien of BILL/CLAIM in file (#399) which is identical
 to the ien of the BILL/receivable <DINUM> in ACCOUNTS RECEIVABLE file (#430),
 that needs to be checked for accrual status before allowing correction.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   IB needs to use $$ACCK^PRCAAC to determine if a
 claim/account is non-accrued.  This function will be called at claim look-up
 when the user 1st enters the [IB CORRECT REJECTED/DENIED] option (CRD).  If it
 determines that the claim/account that the user entered is a non-accrued
 claim, the user will be told that they cannot use the new CRD  option and will
 be directed to use the old CLON option [IB COPY AND CANCEL] instead.  At
 NOPTF^IBCC: NOPTF    ; Note if IB364 is >0 it will be used as the ien to
 update in file 364 
  N DA,I 
  I '$G(IBNOASK) S IBIFN=+$G(Y) 
  I '$G(IBIFN) G ASK 
  I IBCAN>1 D NOPTF^IBCB2 I 'IBAC1 D NOPTF1^IBCB2 G ASK 
  ; New messages for CRD option IB*2.0*433 
  I $G(IBCNCRD)=1,'$$ACCK^PRCAACC(IBIFN) D  Q 
  .W !!,"This option cannot be used to correct some Billing Rate Types
 (Example: TRICARE)" 
  .W "Copy and cancel (CLON) must be used to correct this bill." 
  .S IBQUIT=1 H 3 
  ;
  DATE ACTIVATED: APR 19, 2011

NUMBER: 5631                            IA #: 5631
  DATE CREATED: APR 26, 2011
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DSICXIP ZIP CODE                STATUS: Withdrawn
  EXPIRATION DATE: AUG 03, 2011
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5632                            IA #: 5632
  FILE NUMBER: 771                      GLOBAL ROOT: HL(771,
  DATE CREATED: JAN 08, 2008            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: HL7 APPLICATION PARAMETER LOOKUP .01
  ID: HL(771,
GLOBAL REFERENCE: HL(771,,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   ALLOWS RADIOLOGY TO READ THE .01 FILED OF THE HL7
 APPLICATION PARAMETER FILE 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 5633                            IA #: 5633
  FILE NUMBER: 162.5                    GLOBAL ROOT: FBAAI(
  DATE CREATED: APR 28, 2011            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FEE BASIS INVOICE
  ID: FBAAI(
GLOBAL REFERENCE: FBAAI('D',patient_dfn,da)
 GLOBAL DESCRIPTION:   where patient_dfn is patient DFN in PATIENT file (#2)
 and da is the FEE BASIS INVOICE 
GLOBAL REFERENCE: FBAAI(D0,0)
FIELD NUMBER: 4                         FIELD NAME: ASSOCIATED 7078/583
  ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: TREATMENT FROM DATE
  ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: TREATMENT TO DATE
  ACCESS: Read w/Fileman
FIELD NUMBER: 6.5                       FIELD NAME: DISCHARGE TYPE CODE
  ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: AMOUNT PAID
  ACCESS: Read w/Fileman
FIELD NUMBER: 19                        FIELD NAME: DATE FINALIZED
  ACCESS: Read w/Fileman
FIELD NUMBER: 24                        FIELD NAME: DISCHARGE DRG
  ACCESS: Read w/Fileman
FIELD NUMBER: 6.6                       FIELD NAME: BILLED CHARGES
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAI(D0,'DX')
FIELD NUMBER: 30                        FIELD NAME: ICD1
  ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: ICD2
  ACCESS: Read w/Fileman
FIELD NUMBER: 32                        FIELD NAME: ICD3
  ACCESS: Read w/Fileman
FIELD NUMBER: 33                        FIELD NAME: ICD4
  ACCESS: Read w/Fileman
FIELD NUMBER: 34                        FIELD NAME: ICD5
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAI(D0,'PROC')
FIELD NUMBER: 40                        FIELD NAME: PROC1
  ACCESS: Read w/Fileman
FIELD NUMBER: 41                        FIELD NAME: PROC2
  ACCESS: Read w/Fileman
FIELD NUMBER: 42                        FIELD NAME: PROC3
  ACCESS: Read w/Fileman
FIELD NUMBER: 43                        FIELD NAME: PROC4
  ACCESS: Read w/Fileman
FIELD NUMBER: 44                        FIELD NAME: PROC5
  ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   CCR needs read-only access to fields in the FEE BASIS
 INVOICE file #162.5.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FEE BASIS
KEYWORDS: PURCHASED CARE
KEYWORDS: 162.5
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
  DATE ACTIVATED: MAY 03, 2011

NUMBER: 5634                            IA #: 5634
  FILE NUMBER: 162.1                    GLOBAL ROOT: FBAA(162.1
  DATE CREATED: APR 28, 2011            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FEE BASIS PHARMACY INVOICE
  ID: FBAA(162.1
GLOBAL REFERENCE: FBAA(162.1,D0,'RX',D1,0)
FIELD NUMBER: 9                         FIELD NAME: GENERIC DRUG
  ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   where D0 is the FEE BASIS PHARMACY INVOICE and D1 is the
 PRESCRIPTION NUMBER 
 GENERAL DESCRIPTION:   CCR needs read-only access to the FEE BASIS PHARMACY
 INVOICE file #162.1.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FEE BASIS PHARMACY INVOICE
KEYWORDS: 162.1
KEYWORDS: GENERIC DRUG
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
  DATE ACTIVATED: MAY 03, 2011

NUMBER: 5635                            IA #: 5635
  FILE NUMBER: 162                      GLOBAL ROOT: FBAAC(D0
  DATE CREATED: APR 28, 2011            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FEE BASIS PAYMENT 
  ID: FBAAC(D0
GLOBAL REFERENCE: FBAAC(D0)
 GLOBAL DESCRIPTION:   direct global read and FM read-only access to all fields 
 GENERAL DESCRIPTION:   CCR needs read-only access to all fields in the FEE
 BASIS PAYMENT file #162.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FEE BASIS PAYMENT
KEYWORDS: 162
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
  DATE ACTIVATED: APR 28, 2011

NUMBER: 5636                            IA #: 5636
  DATE CREATED: APR 28, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORCD                         NAME: CPRS ARRAY
  ID: ORCD
 GENERAL DESCRIPTION:   Routine ORCD contains CPRS utilities for order dialogs.
 The JV application (James A Lovell Federal Health Care Center in North
 Chicago) requests permission to use the GETDLG utility.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
COMPONENT/ENTRY POINT: GETDLG
 COMPONENT DESCRIPTION:   Returns an array with the setup of the CPRS dialog.  
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the dialog in ^ORD(101.41 
VARIABLES: ORDIALOG                     TYPE: Output
 VARIABLES DESCRIPTION:   ORDIALOG is an array with the information contained
 in the dialog setup from CPRS.  
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5637                            IA #: 5637
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: OROCAPI1
  NAME: ORDER CHECK API                 ID: OROCAPI1
 GENERAL DESCRIPTION:   The OROCAPI1 routine contains APIs that applications
 can use to add and read order checking information.  
  STATUS: Active
KEYWORDS: OROCAPI1
KEYWORDS: ORDER CHECK
COMPONENT/ENTRY POINT: OCCNT
 COMPONENT DESCRIPTION:   RETURN 1 IF THERE ARE ORDER CHECKS FOR AN ORDER AND 0
 IF NOT.  
VARIABLES: ORD                          TYPE: Input
 VARIABLES DESCRIPTION:   ORDER NUMBER (FILE 100 IEN) 
VARIABLES: $$OCCNT                      TYPE: Output
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: MAY 04, 2011

NUMBER: 5638                            IA #: 5638
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWU HAS OPTION ACCESS          REMOTE PROCEDURE: ORWU HAS OPTION ACCESS
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5639                            IA #: 5639
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWU1 NEWLOC
  REMOTE PROCEDURE: ORWU1 NEWLOC
 GENERAL DESCRIPTION:   Returns a list of Clinics, Wards, and "Other" category
 entries from the HOSPITAL LOCATION (#44) file.  
  
 Input: 
   ORFROM      [optional]  = Text to $O from or passed in an external value 
                      of the name from the HOSPITAL LOCATION FILE #44,.01 
   DIR         [required]  = $Order direction or the collating sequence, 
                      where, it must be 1 or -1 
                      1 = return the return list(s) in next order 
                     -1 = return the return list(s) in reverse order 
  
 Output: 
      Y(n)=DATA  delimited by "^"  where n=1,2,3,4,. .  
  
  Return Parameter Description 
   If successful: 
   Y(n)=p1^p2 
  
   Where: 
   p1 := IEN from Hospital Location file#44 
   p2 := Location name-the external value from file #44,.01 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   Added 03/11/2026, effective with NHIN*1*26, this RPC is 
 defined in the NHIN/DAS context option "NHIN DAS CC", which is defined in the
 REMOTE APPLICATION file entry name "NHIN DAS CC". The RPC is called to provide
 read only data to the calling system.  
  DATE ACTIVATED: APR 07, 2014

NUMBER: 5640                            IA #: 5640
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWORR GETBYIFN                 REMOTE PROCEDURE: ORWORR GETBYIFN
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5641                            IA #: 5641
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWOR RESULT HISTORY
  REMOTE PROCEDURE: ORWOR RESULT HISTORY
 GENERAL DESCRIPTION:   
   **NOTE: This ICR is for JAL and Mobile Scheduling Application 
           Suite only.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: VIA
KEYWORDS: VAR
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9. 
  DATE ACTIVATED: FEB 21, 2017

NUMBER: 5642                            IA #: 5642
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWOR RESULT
  REMOTE PROCEDURE: ORWOR RESULT        STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: VIA
KEYWORDS: VAR
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   Added 12/8/2022, effective with DSSV*1.1 DSS Class 3
 Product Document Only 
  DATE ACTIVATED: FEB 14, 2017

NUMBER: 5643                            IA #: 5643
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDXR GTORITM                  REMOTE PROCEDURE: ORWDXR GTORITM
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5644                            IA #: 5644
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDX ORDITM
  REMOTE PROCEDURE: ORWDX ORDITM
 GENERAL DESCRIPTION:   
   **NOTE: This ICR is for JAL and Mobile Scheduling Application Suite 
           only.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: VIA
KEYWORDS: VAR
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9. 
  DATE ACTIVATED: FEB 21, 2017

NUMBER: 5645                            IA #: 5645
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDX DLGDEF
  REMOTE PROCEDURE: ORWDX DLGDEF
 GENERAL DESCRIPTION:   
   **NOTE: This ICR is for JAL and Mobile Scheduling Application 
           Suite only.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: VIA
KEYWORDS: VAR
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   COMPREHENSIVE CARE COORDINATION ADDED 7/20/2022,
 effective with DSSV*1.1 DSS Class 3 product Document Only - Not approved by
 Custodial SME Patch additionally refers to "C" cross-references which are not
 added to the File references in the ICR.  
  DATE ACTIVATED: FEB 21, 2017

NUMBER: 5646                            IA #: 5646
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDXC DELORD                   REMOTE PROCEDURE: ORWDXC DELORD
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5647                            IA #: 5647
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXA VALID
  REMOTE PROCEDURE: ORWDXA VALID
 GENERAL DESCRIPTION:   Returns an error message if the selected action is not
 valid for a particular CPRS GUI order.  
    
 OUTPUT: SINGLE VALUE 
   Returns an error message if the selected action is not valid for a 
   particular CPRS GUI order.  
                 
 INPUT: 
   ORID   [REQUIRED] - INTERNAL ENTRY NUMBER FOR THE ORDER file (#100) 
  
  ACTION [REQUIRED] - CODE REPRESENTING TYPE OF ACTION TAKEN ON THE ORDER 
  WHEN IN CPRS 
     "XFR" == TRANSFER ORDER TO INPATIENT/OUTPATIENT 
     "RW"  == REWRITE/COPY ORDER 
     "RN"  == RENEW ORDER 
     "XX"  == EDIT/CHANGE ORDER 
     "VR"  == VERIFY ORDER 
     "RF"  == REFILL ORDER 
     "CP"  == COMPLETE ORDER 
     "AL"  == FLAG ORDER 
     "HD"  == HOLD ORDER 
     "NW"  == NEW ORDER 
     "DC"  == DISCONTINUE ORDER 
     "RL"  == RELEASE HOLD ON ORDER 
  
  DUZ    [REQUIRED] - NEW PERSON file (#200) IEN (user performing the 
  action) 
  
  NATURE OF ORDER [OPTIONAL] -  CODE REPRESENTING HOW THE ORDER WAS ENTERED 
       "W" ==   WRITTEN 
       "V" ==   VERBAL 
       "P" ==   TELEPHONED 
       "S" ==   SERVICE CORRECTION 
       "I" ==   POLICY 
       "D" ==   DUPLICATE 
       "X" ==   REJECTED 
       "E" ==   ELECTRONICALLY ENTERED 
       "A" ==   AUTO 
       "C" ==   CHANGED 
       "M" ==   MAINTENANCE 
       "R" ==   REJECTED BY SERVICE 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: VIA
KEYWORDS: VAR
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   As of 2/13/17, Veterans Appointment Request (VAR) is
 using this RPC through the VistA Integration Adaptor's (VIA) OrderMgmt
 Service.  
  DATE ACTIVATED: FEB 13, 2017

NUMBER: 5648                            IA #: 5648
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDXA HOLD                     REMOTE PROCEDURE: ORWDXA HOLD
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5649                            IA #: 5649
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXA DC
  REMOTE PROCEDURE: ORWDXA DC
 GENERAL DESCRIPTION:   
   **NOTE: This ICR is for JAL and Mobile Scheduling Application           
           Suite only.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: VIA
KEYWORDS: VAR
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 22, 2017

NUMBER: 5650                            IA #: 5650
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDLR32 DEF                    REMOTE PROCEDURE: ORWDLR32 DEF
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5651                            IA #: 5651
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDLR32 ALLSAMP                REMOTE PROCEDURE: ORWDLR32 ALLSAMP
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5652                            IA #: 5652
  DATE CREATED: MAY 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDAL32 SAVE ALLERGY
  REMOTE PROCEDURE: ORWDAL32 SAVE ALLERGY
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
  DATE ACTIVATED: NOV 10, 2016

NUMBER: 5653                            IA #: 5653
  DATE CREATED: MAY 02, 2011            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSGSICH1
  NAME: RETURN CPRS ORDER CHECKS AND OVERRIDES TO BCMA
  ID: PSGSICH1
 GENERAL DESCRIPTION:   The entry point GETPROVL^PSGSICH1 is provided by
 Inpatient Medications package to return CPRS order checks and provider
 override reason to Bar Code Medication Administration to be used by
 administering nurses when administering medications at patient's bedside.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSGSICH1
KEYWORDS: ORDER CHECK
KEYWORDS: PROVIDER OVERRIDES
COMPONENT/ENTRY POINT: GETPROVL
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN from Patient (#2) file. (Required) 
VARIABLES: PSGORD                       TYPE: Input
 VARIABLES DESCRIPTION:   Inpatient order number from the UNIT DOSE (#62)
 multiple or IV (#100) multiple, in the PHARMACY PATIENT (#55) file. Unit Dose
 orders must be appended with "U", and IV orders must be appended with "V".  
 (Required) 
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   Array name, passed by reference, to hold order checks
 and provider override information from Computerized Patient Record System
 (CPRS).  (Required) 
  
 Return details: ARRAY("PROV",[DFN],[ORDER],0)="Overriding Provider: "[provider
 name] ARRAY("PROV",[DFN],[ORDER],1)="Override Entered By: "[entered by name] 
 ARRAY("PROV",[DFN],[ORDER],2)="  Date/Time Entered: "[external date] 
 ARRAY("PROV",[DFN],[ORDER],3)="    Override Reason: "[reason text] 
  DFN = patient internal entry number 
  ORDER = order number 
  
 ARRAY("PROVR",[DFN],[ORDER],[CAT],[N],0)=[order check text] 
   DFN = patient interal entry number 
   ORDER = order number 
   CAT = an integer 1, 2, or 3 to represent category.  
      1 indicates a previous adverse reaction warning. 
      2 indicates a critical DRUG-DRUG warning.  
      3 indicates all other warning(s) 
   N = incrementing message number 
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
  DATE ACTIVATED: APR 02, 2018

NUMBER: 5654                            IA #: 5654
  DATE CREATED: MAY 02, 2011            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSGSICH1
  NAME: INPATIENT INTERVENTIONS TO BCMA
  ID: PSGSICH1
 GENERAL DESCRIPTION:   Return Pharmacy Intervention information, from the APSP
 INTERVENTION (#9009032.4) file, for Pharmacy Interventions associated with a
 specific Inpatient order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: INTERVENTIONS
KEYWORDS: ORDER CHECK
KEYWORDS: PSGSICH1
COMPONENT/ENTRY POINT: INTRDIC
 COMPONENT DESCRIPTION:   Return pharmacy intervention information from APSP
 INTERVENTION (#9009032.4) file for intervention(s) associated with a specific 
 Inpatient order.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN from PATIENT (#2) file (required).  
VARIABLES: PSJORDER                     TYPE: Input
 VARIABLES DESCRIPTION:   Inpatient Order from NON-VERIFIED ORDERS (#53.1) file
 or UD (#62) multiple or IV (#100) multiple of PHARMACY PATIENT (#55) file
 (required).  
VARIABLES: OUTARRAY                     TYPE: Both
 VARIABLES DESCRIPTION:   Array name, passed by reference, to hold return
 values (required).  
  
 Return detail: 
  
 OUTARRAY([DFN],[ORDER],[INTRV],[FLD])=[FLD NAME]": "[FLD VALUE] 
   DFN = patient internal entry number 
   ORDER = order number 
   INTRV = intervention IEN 
   FLD = field number 
   FLD NAME = field name 
   FLD VALUE = value stored in the field 
VARIABLES: PSJCURIN                     TYPE: Input
 VARIABLES DESCRIPTION:   Current/historical intervention flag. (Optional) 
  
 If PSJCURIN = 0, or any value that evaluates to FALSE: Return all 
 interventions associated with Inpatient order PSJORDER, regardless of 
 date/time.  
  
 If PSJCURIN = 1 : Return only interventions associated with Inpatient order
 PSJORDER that were logged on the most recent Intervention date/time.  
  
 If PSJCURIN = 2 : Return only CRITICAL DRUG-DRUG or ALLERGY/ADR interventions
 associated with order PSJORDER that were logged on the most recent
 Intervention date/time.  
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
  DATE ACTIVATED: APR 02, 2018

NUMBER: 5655                            IA #: 5655
  DATE CREATED: MAY 03, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQOR DETAIL
  REMOTE PROCEDURE: ORQOR DETAIL
 GENERAL DESCRIPTION:   
   **NOTE: This ICR is for HMP, JAL and Mobile Scheduling Application 
           Suite only.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: VIA
KEYWORDS: VAR
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9. 
  DATE ACTIVATED: NOV 10, 2016

NUMBER: 5656                            IA #: 5656
  DATE CREATED: MAY 03, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDX SEND
  REMOTE PROCEDURE: ORWDX SEND          STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This ICR was originally created for use by JAL.  VIAB
 was tasked to create a replacement interface for MDWS.  CPRS developer
 approved use of this RPC for both JAL and VIAB.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Added 11/6/19 for access to SEND^ORWDX, effective with
 RA*5*161.  
  DATE ACTIVATED: FEB 10, 2015

NUMBER: 5657                            IA #: 5657
  DATE CREATED: MAY 03, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDX SAVE                      REMOTE PROCEDURE: ORWDX SAVE
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5658                            IA #: 5658
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870,'AD'
  DATE CREATED: MAY 03, 2011            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  NAME: DETERMINE LOGICAL LINK BASED ON DNS DOMAIN STRING
  ID: HLCS(870,'AD'
 GENERAL DESCRIPTION:   The VistA Health Level Seven application grants
 permission to the VistA Radiology/Nuclear Medicine application to reference a
 cross reference tied to a specific NODE (#.01) record filed in the HL LOGICAL
 LINK (#870) file.  
  
 cross reference: ^HLCS(870,"AD",<LLP TYPE>,<DNS DOMAIN>,<NODE>)="" 
  
 LLP TYPE will always be "TCP". DNS DOMAIN is derived from the third component
 of the Sending Facility (MSH-4) field of the MSH segment.  
  
 There is one NODE record for each unique DNS DOMAIN value.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: HLO RA
KEYWORDS: RA HLO
KEYWORDS: DNS DOMAIN
KEYWORDS: LOGICAL LINK
COMPONENT/ENTRY POINT: RA
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   The VistA Radiology/Nuclear Medicine application will
 reference the following cross reference: ^HLCS(870,"AD",<LLP TYPE>,<DNS 
 DOMAIN>,<NODE>)="" 
  
 LLP TYPE will be always have a value of "TCP". 
  
 DNS DOMAIN will be derived from the third component of the Sending Facility
 (MSH-4) field of the MSH segment.  

NUMBER: 5659                            IA #: 5659
  FILE NUMBER: 162.4                    GLOBAL ROOT: FB(7078
  DATE CREATED: MAY 05, 2011            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VA FORM 10-7078 #162.4
  ID: FB(7078
GLOBAL REFERENCE: FB(7078,D0
 GENERAL DESCRIPTION:   CCR needs FileMan read-only access to fields in the VA
 FORM 10-7078 file #162.4.  
  STATUS: Active
KEYWORDS: VA FORM 10-7078
KEYWORDS: 10-7078
KEYWORDS: 162.4
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
  DATE ACTIVATED: MAY 09, 2011

NUMBER: 5660                            IA #: 5660
  DATE CREATED: MAY 06, 2011            CUSTODIAL PACKAGE: RPC BROKER
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: DSIC DDR GETS ENTRY DATA
  REMOTE PROCEDURE: DSIC DDR GETS ENTRY DATA
 GENERAL DESCRIPTION:   This is the Broker RPC that is called to request that a
 RPC be run on a remote system.  The data is passed by HL7 to the remote system
 as is the return value.  The difference between this and the XWB REMOTE RPC is
 this is a blocking call meaning the user's workstation will not process 
 anything else until the data returns from the remote system.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: RPC
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   The JV application is using the RPC for "Register
 Once". The application gets back a list of last sites treated from the MVI;
 then it takes the very last site number to make a XWB DIRECT RPC call for a
 remote DGRR GET PATIENT SERVICES DATA RPC call to that site to get the
 registration information from that remote site.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 7/29/25, effective with DSIY*1.4*0 released 
 2/8/19 requested to be added as subscribers to RPC DSIC DDR GETS ENTRY DATA 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 7/29/25, effective with DSSO*2.0 released 4/16/20
 requested to be added as subscribers to RPC DSIC DDR GETS ENTRY DATA 
  DATE ACTIVATED: JUN 02, 2011

NUMBER: 5661                            IA #: 5661
  DATE CREATED: MAY 10, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RADD3
  NAME: UPDATE RAD EXAM STATUS/ACTIVITY LOG
  ID: RADD3
 GENERAL DESCRIPTION:   The JV application, Federal Health Care Center at North
 Chicago, requires an interface to legacy Radiology for the purpose of updating
 the Radiology exam status and activity log in its Orders Portability 
 requirement.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: JV RA
KEYWORDS: RA
COMPONENT/ENTRY POINT: X7005
 COMPONENT DESCRIPTION:   This entry point updates the EXAM STATUS TIMES
 (70.05) multiple.  
VARIABLES: RADFN                        TYPE: Input
 VARIABLES DESCRIPTION:   RADFN=patient dfn 
VARIABLES: RADTI                        TYPE: Input
 VARIABLES DESCRIPTION:   RADTI=exam date/time (inverse) 
VARIABLES: RACNI                        TYPE: Input
 VARIABLES DESCRIPTION:   RACNI=exam record ien (70.03) 
VARIABLES: RAMDV                        TYPE: Input
 VARIABLES DESCRIPTION:   RAMDV=division parameters 
VARIABLES: RAQED                        TYPE: Input
 VARIABLES DESCRIPTION:   RAQED=task queued(1=yes;0=no) 
VARIABLES: RASTI                        TYPE: Input
 VARIABLES DESCRIPTION:   RASTI=exam status 
VARIABLES: RAWHO                        TYPE: Input
 VARIABLES DESCRIPTION:   RAWHO=editing person 
COMPONENT/ENTRY POINT: A7007
 COMPONENT DESCRIPTION:   This entry point updates the ACTIVITY LOG (70.07)
 multiple.  
VARIABLES: RADFN                        TYPE: Input
 VARIABLES DESCRIPTION:   RADFN=patient dfn 
VARIABLES: RACNI                        TYPE: Input
 VARIABLES DESCRIPTION:   RACNI=exam record ien (70.03) 
VARIABLES: RADTI                        TYPE: Input
 VARIABLES DESCRIPTION:   RADTI=exam date/time (inverse) 
VARIABLES: RAWHO                        TYPE: Input
 VARIABLES DESCRIPTION:   RAWHO=editing person 
VARIABLES: RATC                         TYPE: Input
 VARIABLES DESCRIPTION:   RATC=technologist comments (optional) 
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   The JV application invokes this legacy routine to help
 update the Rad exam and activity log status change history after DoD sends a
 new record for a patient being examined.  
  DATE ACTIVATED: AUG 01, 2011

NUMBER: 5662                            IA #: 5662
  FILE NUMBER: 78.4                     GLOBAL ROOT: RA 
  DATE CREATED: MAY 10, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RADIOLOGY FILM SIZES FILE
  ID: RA 
GLOBAL REFERENCE: RA(78.4,B
 GLOBAL DESCRIPTION:   The JV application, Federal Health Care Center, will use
 the "B" index to look up specific values in the file using the $$FIND1^DIC
 utility.  
 GENERAL DESCRIPTION:   This file contains the allowable film sizes that the
 technologist can choose from when entering film data for an exam.  Entries in
 this file should not be deleted.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: JV RA
KEYWORDS: RA
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   The JV application, Federal Health Care Center, will
 use the "B" index to look up specific values in the file.  The lookup will be
 performed using the $$FIND1^DIC utility.  
  DATE ACTIVATED: JUN 07, 2011

NUMBER: 5663                            IA #: 5663
  FILE NUMBER: 78.6                     GLOBAL ROOT: RA 
  DATE CREATED: MAY 10, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: REFERENCE TO CAMERA/EQUIP/RM FILE
  ID: RA 
GLOBAL REFERENCE: RA(78.6,B
 GLOBAL DESCRIPTION:   The JV application, Federal Health Care Center, will use
 the "B" index to look up specific values in the file, using the $$FIND1^DIC
 utility.  
 GENERAL DESCRIPTION:   This file contains all the camera/equip/rm that may be
 used to perform imaging examinations.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: JV RA
KEYWORDS: RA
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   The JV application, Federal Health Care Center, will
 use the "B" index to look up specific values in the file.  The lookup will be
 performed using the $$FIND1^DIC utility.  
  DATE ACTIVATED: JUN 07, 2011

NUMBER: 5664                            IA #: 5664
  FILE NUMBER: 71.2                     GLOBAL ROOT: RAMIS
  DATE CREATED: MAY 10, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: REFERENCE TO PROCEDURE MODIFIERS FILE
  ID: RAMIS
GLOBAL REFERENCE: RAMIS(71.2,B
 GLOBAL DESCRIPTION:   The JV application, Federal Health Care Center, will use
 the "B" index to look up specific values in the file using the $$FIND1^DIC
 utility.  
 GENERAL DESCRIPTION:   This file contains the modifiers that can be associated
 with an imaging exam. These modifiers are used to further describe the
 procedure associated with the exam.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: JV RA
KEYWORDS: RA
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   The JV application, Federal Health Care Center, will
 use the "B" index to look up specific values in the file.  The look-up will be
 performed using the $$FIND1^DIC utility.  
  DATE ACTIVATED: JUN 07, 2011

NUMBER: 5665                            IA #: 5665
  DATE CREATED: MAY 11, 2011
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DSIC DDR DELETE ENTRY           STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: JUL 29, 2011
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5666                            IA #: 5666
  DATE CREATED: MAY 11, 2011
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DSIC DDR GETS ENTRY DATA
 GENERAL DESCRIPTION:   This RPC calls GETS^DIQ to get a list of field values
 for a record.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   This RPC calls GETS^DIQ to get a list of field values
 for a record.  

NUMBER: 5667                            IA #: 5667
  DATE CREATED: MAY 11, 2011
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DSIC DDR UPDATE SUBFILE         STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: JUL 29, 2011
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER

NUMBER: 5668                            IA #: 5668
  DATE CREATED: MAY 11, 2011
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DSIC FM FILER
 GENERAL DESCRIPTION:   This RPC invokes the FileMan filer to update records
 for an existing entry.  This will allow you to update any field at the level
 of the FILE including word processing fields.  It does not allow for updating 
 different levels of the file.  If you wish to update a subfile, then you will
 have to make multiple calls to this RPC for each file or subfile.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   This RPC invokes the FileMan filer to update records
 for an existing entry.  This will allow you to update any field at the level
 of the FILE including word processing fields.  It does not allow for updating 
 different levels of the file.  If you wish to update a subfile, then you will
 have to make multiple calls to this RPC for each file or subfile.  

NUMBER: 5669                            IA #: 5669
  DATE CREATED: MAY 11, 2011
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DSIC FM FIND                    REMOTE PROCEDURE: DSIC FM FIND
 GENERAL DESCRIPTION:   This RPC provides a wrapper around the FIND^DIC API. 
 It exposes more of the functionality of the API to the RPC than the old DSIC
 DDR FINDER RPC.  
   
 For a lookup value, this RPC will return all matches.  It allows for input a
 multiple screening logic which would be ANDed together.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   This RPC provides a wrapper around the FIND^DIC API. 
 It exposes more of the functionality of the API to the RPC than the old DSIC
 DDR FINDER RPC.  
   
 For a lookup value, this RPC will return all matches.  It allows for input a
 multiple screening logic which would be ANDed together.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 10/31/25, effective with DSIY*1.4*0 released 
 2/8/19 requested to be added as subscribers to RPC DSIC FM FIND 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/31/25, effective with DSSO*2.0 released 
 4/16/20 requested to be added as subscribers to RPC DSIC FM FIND 

NUMBER: 5670                            IA #: 5670
  DATE CREATED: MAY 11, 2011
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DSIC FM LIST                    REMOTE PROCEDURE: DSIC FM LIST
 GENERAL DESCRIPTION:   The RPC provides a wrapper around the LIST^DIC API.  It
 exposes more of the functionality of the API than the DSIC DDR LISTER RPC.  
   
 For a lookup value, return all entries starting from that lookup value and 
 which collates after that lookup value.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   The RPC provides a wrapper around the LIST^DIC API.  It
 exposes more of the functionality of the API than the DSIC DDR LISTER RPC.  
   
 For a lookup value, return all entries starting from that lookup value and 
 which collates after that lookup value.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 10/31/25, effective with DSIY*1.4*0 released 
 2/8/19 requested to be added as subscribers to RPC DSIC FM LIST 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/31/25, effective with DSSO*2.0 released 2/8/19
 requested to be added as subscribers to RPC DSIC FM LIST 

NUMBER: 5671                            IA #: 5671
  DATE CREATED: MAY 11, 2011            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCEOB4
  NAME: COPY FUNCTIONS FOR IB EOB FILE #361.1
  ID: IBCEOB4
 GENERAL DESCRIPTION:   File 361.1 EXPLANATION OF BENEFITS is shared by
 Accounts Receivable and Integrated Billing. A/R already has full read access
 to the data in this file and options to add new entries. 
  
 The additional functions defined below are required to allow AR to MOVE COPY,
 REMOVE or RESTORE erroneous entries in File 361.1 and update audit trail
 fields.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IBM(361.1
KEYWORDS: EOB FILE
KEYWORDS: EXPLANATION OF BENEFITS
KEYWORDS: 361.1
COMPONENT/ENTRY POINT: $$MOVE(EOBIEN,IBIFN,DUZ,MDATE,JUST)
 COMPONENT DESCRIPTION:   This component is used to move a File 361.1 entry to
 a different bill and updates the following fields: 
  
  .01    BILL 
  101,.01 DATE/TIME EEOB MOVED 
  101,.02 EEOB MOVE/COPY/REMOVE BY 
  101,.03 MOVE/COPY/REMOVE REASON 
  101,.04 ORIGINAL BILL NUMBER 
  101,.05 MOVE/COPY/REMOVE EVENT 
  
VARIABLES: EOBIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   The pointer (ien) to the existing entry in file
 361.1.  
  
VARIABLES: IBIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The pointer (ien) to the new bill in file 399.  
  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The pointer (ien) to the user in file 200.  
  
  
VARIABLES: MDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   Date and time the move was performed.  
  
  
VARIABLES: JUST                         TYPE: Input
 VARIABLES DESCRIPTION:   Free text comment (up to 100 characters) entered by
 user making the change.  
  
COMPONENT/ENTRY POINT: $$COPY(EOBIEN,.IBIFN,DUZ,CDATE,JUST)
 COMPONENT DESCRIPTION:   This component is used to copy a single File 361.1
 entry. An array of bill numbers is passed and new File 361.1 entries are
 created for each valid bill.  
  
 In addition to existing data fields the following audit fields are updated on
 both the original entry and the new copied entries: 
  
  101,.01 DATE/TIME EEOB MOVED 
  101,.02 EEOB MOVE/COPY/REMOVE BY 
  101,.03 MOVE/COPY/REMOVE REASON 
  101,.04 ORIGINAL BILL NUMBER 
  101,.05 MOVE/COPY/REMOVE EVENT 
  101,.06 OTHER CLAIM NUMBERS (Multiple) 
  
  
VARIABLES: EOBIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   The pointer (ien) to the existing entry in file
 361.1.  
  
VARIABLES: .IBIFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Array of pointers (ien) to the new bills in file 399. 
  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The pointer (ien) to the user in file 200.  
  
VARIABLES: CDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   Date and time the copy was performed.  
  
VARIABLES: JUST                         TYPE: Input
 VARIABLES DESCRIPTION:   Free text comment (up to 100 characters) entered by
 the user.  
  
COMPONENT/ENTRY POINT: $$LOCK(EOBIEN)
 COMPONENT DESCRIPTION:   Lock entry in EOB file #361.1. 
  
VARIABLES: EOBIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   The pointer (ien) to the existing entry in file
 361.1.  
  
  
COMPONENT/ENTRY POINT: $$UNLOCK(EOBIEN)
 COMPONENT DESCRIPTION:   Unlock entry in EOB file #361.1.  
  
VARIABLES: EOBIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   The pointer (ien) to the existing entry in file
 361.1.  
  
COMPONENT/ENTRY POINT: $$REMOVE(EOBIEN,DUZ,JCOM)
 COMPONENT DESCRIPTION:   This component is used to mark an EEOB as removed by
 updating the following field: 
  
   102 EEOB REMOVED 
                 
 The following audit fields are also updated: 
                 
   101,.01 DATE/TIME EEOB MOVED 
   101,.02 EEOB MOVE/COPY/REMOVE BY 
   101,.03 MOVE/COPY/REMOVE REASON 
   101,.05 MOVE/COPY/REMOVE EVENT                                               
    
  
VARIABLES: EOBIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   The pointer (ien) to the existing entry in file
 #361.1.  
  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The pointer (ien) to the user in file 200.  
  
VARIABLES: JCOM                         TYPE: Input
 VARIABLES DESCRIPTION:   Free text comment (up to 100 characters) entered by
 the user.  
  
COMPONENT/ENTRY POINT: RESTORE
 COMPONENT DESCRIPTION:   This component is used to restore a removed EEOB. The
 following field  is updated in EOB file #361.1: 
                 
   102 EEOB REMOVED 
                                
 Audit fields in the 101 multiple are not updated. 
VARIABLES: EOBIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   The pointer (ien) to the existing entry in file
 #361.1.  
VARIABLES:  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: MAY 17, 2011

NUMBER: 5672                            IA #: 5672
  DATE CREATED: MAY 11, 2011
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DSIC XIP                        REMOTE PROCEDURE: DSIC XIP
 GENERAL DESCRIPTION:   This RPC returns address demographics for a 5 or 9
 digit zip code 
  
 The return value is for the primary location associated with the ZIP code.  
   if an error:  -1 ^ ERROR MESSAGE 
   if OK:   Input ZIP code ^ city ^ state ^ county ^ FIPS county code 
   the return is for the primary location associated with the ZIP code.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   This RPC returns address demographics for a 5 or 9
 digit zip code 
  
 The return value is for the primary location associated with the ZIP code.  
   if an error:  -1 ^ ERROR MESSAGE 
   if OK:   Input ZIP code ^ city ^ state ^ county ^ FIPS county code 
   the return is for the primary location associated with the ZIP code.  

NUMBER: 5673                            IA #: 5673
  DATE CREATED: MAY 11, 2011
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DSIC XUTIL NAME COMPONENT
 GENERAL DESCRIPTION:   This RPC will take a standard VistA person name in the
 format Last,First M and return the individual name components.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   This RPC will take a standard VistA person name in the
 format Last,First M and return the individual name components.  

NUMBER: 5674                            IA #: 5674
  DATE CREATED: MAY 11, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORWDCN32                     NAME: CONSULT UTILITY CALLS
  ID: ORWDCN32
 GENERAL DESCRIPTION:   The routine contains multiple entry points for consults
 utilities.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
COMPONENT/ENTRY POINT: GETOINUM
 COMPONENT DESCRIPTION:   This entry point gets Orderable Item IEN from
 Protocol IEN.  
VARIABLES: ORNUM                        TYPE: Input
 VARIABLES DESCRIPTION:   ORNUM=order number 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Y=IEN of an orderable item 
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   The component is invoked it to obtain the orderable
 item IEN from the protocol IEN.  

NUMBER: 5675                            IA #: 5675
  FILE NUMBER: 130                      GLOBAL ROOT: SRF(
  DATE CREATED: MAY 24, 2011            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SURGERY FILE DATA
  ID: SRF(
GLOBAL REFERENCE: SRF(D0,0)
FIELD NUMBER: .04                       FIELD NAME: SURGERY SPECIALTY
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 100                       FIELD NAME: ORDER NUMBER
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .015                      FIELD NAME: VISIT
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,8)
FIELD NUMBER: 50                        FIELD NAME: DIVISION
  LOCATION: 8;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,1.0)
FIELD NUMBER: 1.098                     FIELD NAME: DATE/TIME OR REQUEST MADE
  LOCATION: 1.0;11                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1.099                     FIELD NAME: SURG SCHED PERSON
  LOCATION: 1.0;10                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,.1)
FIELD NUMBER: .164                      FIELD NAME: ATTENDING SURGEON
  LOCATION: .1;13                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,.2)
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
GLOBAL REFERENCE: SRF(D0,NON)
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
FIELD NUMBER: 125                       FIELD NAME: MEDICAL SPECIALTY
  LOCATION: NON;8                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SRF(D0,31)
FIELD NUMBER: 15                        FIELD NAME: DATE/TIME OF DICTATION
  LOCATION: 31;6                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 39                        FIELD NAME: DATE OF TRANSCRIPTION
  LOCATION: 31;7                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This agreement documents additional fields read from
 the Surgery file #130 that are not returned by other SR api's.  
  
 Amended in August 2022: Added fields .04,.164,.205,.232,15, 39, 100,121-125
 effective with patch VPR*1*30.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: AUG 26, 2022

NUMBER: 5676                            IA #: 5676
  DATE CREATED: MAY 24, 2011
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUSROI
  NAME: TIUSROI                         ID: TIUSROI
 GENERAL DESCRIPTION:   This agreement documents and supports the TIUSROI
 routine entry points listed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CLASS
KEYWORDS: ISSURG
COMPONENT/ENTRY POINT: $$CLASS(CLNAME)
 COMPONENT DESCRIPTION:   This function returns the 8925.1 ien of the requested
 Surgery class.  
VARIABLES: CLNAME                       TYPE: Input
 VARIABLES DESCRIPTION:   The name of a document class, i.e. "SURGICAL REPORTS" 
VARIABLES: $$CLASS                      TYPE: Output
 VARIABLES DESCRIPTION:   Function result, the 8925.1 ien of the document class
 or 0.  
COMPONENT/ENTRY POINT: ISSURG(TIUY,TITLE)
 COMPONENT DESCRIPTION:   Evaluates whether TITLE is a Surgery Report and
 returns a Boolean value of 0 (not a Surgery Report) or 1 (is a Surgery
 Report).  
VARIABLES: TIUY                         TYPE: Both
 VARIABLES DESCRIPTION:   The variable that will hold the boolean value; passed
 by reference.  
VARIABLES: TITLE                        TYPE: Input
 VARIABLES DESCRIPTION:   An entry number for the TIU DOCUMENT DEFINITION file
 #8925.1.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
  DATE ACTIVATED: AUG 02, 2013

NUMBER: 5677                            IA #: 5677
  FILE NUMBER: 8925.1                   GLOBAL ROOT: TIU(8925.1,
  DATE CREATED: MAY 24, 2011
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU NATIONAL TITLE LINK
  ID: TIU(8925.1,
GLOBAL REFERENCE: TIU(8925.1,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
FIELD NUMBER: .03                       FIELD NAME: PRINT NAME
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: TYPE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: PERSONAL OWNER
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: CLASS OWNER
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: STATUS
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1                        FIELD NAME: SHARED
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .13                       FIELD NAME: NATIONAL STANDARD
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .14                       FIELD NAME: POSTING INDICATOR
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: TIU(8925.1,D0,10,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ITEM
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: TIU(8925.1,D0,15)
FIELD NUMBER: 1501
  FIELD NAME: VHA ENTERPRISE STANDARD TITLE
  LOCATION: 15;1                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Virtual Patient Record (VPR) needs the Document
 Definitions to accurately apply ASU business rules in the Health Management
 Platform (HMP) client, and filter documents based on their VHA ENTERPRISE
 STANDARD TITLE attributes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI
 SUBSCRIBING DETAILS:   Added 8/28/24, effective with DSIR*8.2*16 in order to
 read VHA ENTERPRISE STANDARD TITLE (#1501) in the TIU DOCUMENT DEFINITION
 (#8925.1)file. VHA ENTERPRISE STANDARD TITLE using FILEMAN.  
 $$GET1^DIQ(8925.1,DSIR892,"1501","I") 
  DATE ACTIVATED: AUG 05, 2013

NUMBER: 5678                            IA #: 5678
  FILE NUMBER: 8926.1                   GLOBAL ROOT: TIU(8926.1,
  DATE CREATED: MAY 24, 2011
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU NATIONAL TITLES
  ID: TIU(8926.1,
GLOBAL REFERENCE: TIU(8926.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: STANDARD TITLE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: SUBJECT MATTER DOMAIN
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: ROLE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: SETTING
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: SERVICE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DOCUMENT TYPE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   GETS^DIQ is used to retrieve all attributes of a
 national title.  
GLOBAL REFERENCE: TIU(8926.1,D0,'VUID')
FIELD NUMBER: 99.99                     FIELD NAME: VUID
  LOCATION: VUID;1                      ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   $$GET1^DIQ is used to retrieve the VUID.  
GLOBAL REFERENCE: TIU(8926.1,D0,'TERMSTATUS',D1,0)
FIELD NUMBER: .01                       FIELD NAME: EFFECTIVE DATE
  LOCATION: TERMSTATUS;1                ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   $$GET1^DIQ will be used to read the EFFECTIVE DATE.  
 GENERAL DESCRIPTION:   This agreement documents and supports read access via
 FileMan to the TIU VHA ENTERPRISE STANDARD TITLE file #8926.1.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI
 SUBSCRIBING DETAILS:   Added 8/31/21, effective with DSIR*8.2*15. Added 99.991
 EFFECTIVE DATE/TIME multiple and .01 field to ICR.  
  DATE ACTIVATED: AUG 05, 2013

NUMBER: 5679                            IA #: 5679
  DATE CREATED: JUN 03, 2011            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEXU
  NAME: LEXU (ICD-10 UPDATE)            ID: LEXU
 GENERAL DESCRIPTION:   This is an addendum to ICR 1573 and contains functions
 added to LEXU during the implementation of ICD-10 Coding system. The APIs in
 this ICR become effective on the date of release of patches ICD*18.0*57 and
 LEX*2.0*80.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICD-10
KEYWORDS: LEXU
KEYWORDS: D10ONE
KEYWORDS: P10ONE
KEYWORDS: D10
KEYWORDS: ONE
KEYWORDS: ALL
KEYWORDS: IMPDATE
KEYWORDS: ICD10
KEYWORDS: DX
COMPONENT/ENTRY POINT: $$D10ONE(IEN,DATE)
 COMPONENT DESCRIPTION:   Returns either a single active ICD-10 Diagnosis code
 linked to the Lexicon expression or Null if no ICD-10 Diagnosis 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. 
  
VARIABLES: $$D10ONE                     TYPE: Output
 VARIABLES DESCRIPTION:   A single active ICD-10 Diagnosis code or Null if no
 ICD-10 Diagnosis code is found.  
  
COMPONENT/ENTRY POINT: $$D10(IEN,DATE)
 COMPONENT DESCRIPTION:   Returns either a string of active ICD-10 Diagnosis
 codes linked to an expression (separated by semicolon, i.e., 
 ICD10;ICD10;ICD10) or Null If no ICD-10 Diagnosis 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.  
  
VARIABLES: $$D10                        TYPE: Output
 VARIABLES DESCRIPTION:   A string of active ICD-10 Diagnosis codes linked to 
 an expression (separated by semicolon, i.e., ICD.10;ICD.10;ICD.10) or Null if
 no ICD-10 Diagnosis codes are found. 
  
COMPONENT/ENTRY POINT: $$P10ONE(IEN,DATE)
 COMPONENT DESCRIPTION:   Returns either a single active ICD-10 Procedure code 
 linked to the Lexicon expression or Null if no icd-10 Procedure 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.  
  
VARIABLES: $$P10ONE                     TYPE: Output
 VARIABLES DESCRIPTION:   A single active ICD-10 Procedure code or Null if no
 ICD-10 Procedure code is found.  
  
COMPONENT/ENTRY POINT: $$ONE(IEN,DATE,SAB)
 COMPONENT DESCRIPTION:   Returns a single code for a given internal entry
 number (IEN) for a specified date and source.  
  
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.  
  
VARIABLES: SAB                          TYPE: Input
 VARIABLES DESCRIPTION:   Source, this is an internal entry number in file 
 757.03 or the 3 character source mnemonic (found on the ASAB cross-reference
 in file 757.03) or the SOURCE ABBREVIATION (.01 field in file 757.03) 
  
VARIABLES: $$ONE                        TYPE: Output
 VARIABLES DESCRIPTION:   Code - A single code belonging to the specified 
        coding identified by the input parameter 
        SAB and was active on the date provided 
        and linked to the expression (IEN).  or 
  
 Null   No code exist for the coding system on the 
        specified date and for the expression.  
  
COMPONENT/ENTRY POINT: $$ALL(IEN,DATE,SAB)
 COMPONENT DESCRIPTION:   Returns all classification codes for a given internal 
 entry number (IEN) for a specified date and source.  
  
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.  
  
VARIABLES: SAB                          TYPE: Input
 VARIABLES DESCRIPTION:   Source, this is an internal entry number in file 
 757.03 or the 3 character source mnemonic (found on the ASAB cross-reference
 in file 757.03) or the SOURCE ABBREVIATION (.01 field in file 757.03) 
  
VARIABLES: $$ALL                        TYPE: Output
 VARIABLES DESCRIPTION:   A string of codes for the source provided (one or 
 more) delineated by a semi-colon or null if no codes are found for the source. 
  
COMPONENT/ENTRY POINT: $$IMPDATE(SAB)
 COMPONENT DESCRIPTION:   This entry point (extrinsic function) returns the
 implementation date for a specified source.  
  
VARIABLES: SAB                          TYPE: Input
 VARIABLES DESCRIPTION:   Source, this is an internal entry number in file 
 757.03 or the 3 character source mnemonic (found on the ASAB cross-reference
 in file 757.03) or the SOURCE ABBREVIATION (.01 field in file 757.03) 
  
VARIABLES: $$IMPDATE                    TYPE: Output
 VARIABLES DESCRIPTION:   The date that a coding system was implemented in
 VistA in Fileman format.  
  
COMPONENT/ENTRY POINT: $$CSYS(SYS,VDT)
 COMPONENT DESCRIPTION:   This entry point returns information about a coding 
 system on file in the Coding System file #757.03.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   Coding system identification system and can be in any 
 of the following formats: 
  
     A nickname if one exist, i.e.  HCPCS, DSM, 
     NANDA, BIRADS 
  
     First three characters of source abbreviation 
     from file 757.03, field .01 
  
     Source Abbreviation (file 757.03, field .01), 
     i.e., ICD9, CPT4, SNM2 
  
     Nomenclature (file 757.03, field 1), i.e., 
     ICD-9-CM, ICD-10-PCS, NANDA 
  
     Type (only for ICD), i.e., "DIAG" or "PROC" 
     (requires date) 
  
VARIABLES: VDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Versioning date in Fileman format used to determine 
 coding system if only the type is known (DIAG or PROC) and to determine the
 correct SDO version if one exists.  If the date is not passed, then TODAY is
 used.  
  
VARIABLES: $$CSYS                       TYPE: Output
 VARIABLES DESCRIPTION:   A 13 piece caret (^) delimited string 
  
   1    IEN 
   2    SAB (3 character source abbreviation) 
   3    Source Abbreviation (3-7 char)  (#.01) 
   4    Nomenclature (2-11 char) (#1) 
   5    Source Title (2-52 char) (#2) 
   6    Source (2-50 char) (#3) 
   7    Entries (numeric) (#4) 
   8    Unique Entries (numeric) (#5) 
   9    Inactive Version (1-20 char) (#6) 
  10    HL7 Coding System (2-40 char) (#7) 
  11    SDO Version Date (date) (757.08 #.01) 
  12    SDO Version Id (1-40 char) (757.08 #1) 
  13    Implementation Date (date) (#11) 
  
COMPONENT/ENTRY POINT: $$HIST(CODE,SYS,.ARY)
 COMPONENT DESCRIPTION:   This entry point returns a codes activation history
 in an array passed by reference.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a classification code found in the CODES file
 757.02 (Required) 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a coding system found in the CODING SYSTEMS
 file 757.03.  It can be in the form of a pointer, a source abbreviation or the 
 name of a coding nomenclature (Required) 
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is an array of status effective dates and
 activation status passed by reference (Required) 
  
     ARY(0) = Number of Activation History 
     ARY(0,0) = Code ^ Source ^ Source Name 
     ARY(<date>,<status>) = Comment 
  
 Status 
  
   0  = Inactive 
   1  = Active 
  
 Comments include: 
   
   Activated 
   Inactivated 
   Re-activated 
   Revised 
   Reused 
  
 If the date is in the future, the comment will be appended with "(Pending)"
 indicating that the action activated, inactivated, etc., hasn't occurred yet.  
  
VARIABLES: $$HIST                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of activation history entries 
 found 
  
   or 
  
 -1 ^ error message 
  
COMPONENT/ENTRY POINT: $$PERIOD(CODE,SYS,ARY)
 COMPONENT DESCRIPTION:   This entry point returns the activation periods 
 (active from and to) of a code in an array passed by reference.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a classification code found in the CODES file
 757.02 (Required) 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a coding system found in the CODING SYSTEMS
 file 757.03.  It can be in the form of a pointer, a source abbreviation or the
 name of a coding nomenclature (Required) 
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is an array of activation periods (including 
 active on date and inactive on date when inactive) passed by reference
 (Required) 
  
 ARY(0)   6 piece "^" delimited string 
  
            1  Number of Activation Periods found 
            2  Coding System (pointer to file 775.03) 
            3  Coding System Abbreviation 
            4  Coding System Nomenclature 
            5  Coding System Full Name 
            6  Coding System Source 
  
            or 
            
           -1 ^ Message (no period or error) 
  
 ARY(Activation Date) = 4 piece "^" delimited string 
  
          1  Inactivation Date 
             (conditional) 
          
          2  Pointer to Expression file 757.01 
             for the code in piece #2 above 
             (required) 
             
          3  Variable Pointer IEN;Root of a 
             national file (see below)  Include 
             when the code exist in an national 
             file (conditional) 
              
                CPT Procedure code    IEN;ICPT( 
                ICD Diagnosis code    IEN;ICD9( 
                ICD Procedure code    IEN;ICD0( 
                
          4  Short Description from the SDO file 
             (CPT or ICD) 
  
 ARY(Activation Date,0) = Lexicon Expression 
  
VARIABLES: $$PERIOD                     TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of activation periods found: 
  
   Same as output variable ARY(0) 
  
   or 
  
   -1 ^ error message 
  
COMPONENT/ENTRY POINT: $$DX(IEN,VDT)
 COMPONENT DESCRIPTION:   This entry point is to be used as a screen Lexicon
 searches. It will screen out all terms not linked to either an ICD-9 or ICD-10
 code.  The code type (ICD-9 or ICD-10) is determined by date.  If the date
 passed in is before the ICD-10 implementation date then it will screen on
 ICD-9 codes.  If the date is on or after the ICD-10 implementation date then
 it will screen on ICD-10 codes. 
  
 Assuming the variable VDT is a valid Fileman format date: 
  
   Screen on ICD Diagnosis 
  
     S DIC("S")="I $$DX^LEXU(+Y,VDT)" 
  
       VDT is before ICD-10 implementation = ICD-9 
       VDT is on or after ICD-10 implementation = ICD-10 
  
 If the date is not passed, then TODAY is used. 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an internal entry number in the expression 
 file 757.01.  When performing Fileman lookups, set it to the variable +Y. 
 (Required) 
  
VARIABLES: VDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the versioning date against which the codes
 found by the search will be compared in order to determine whether the code is
 active or inactive.  Additionally if the date passed is earlier that the
 ICD-10 implementation date then the screen will only condider ICD-9 codes.  If 
 the date is on or after the ICD-10 implementation date then the screen will
 only consider ICD-10 codes.  If the date is not passed, then TODAY's date will
 be used.  (Optional) 
  
VARIABLES: $$DX                         TYPE: Output
 VARIABLES DESCRIPTION:   This is a Boolean value: 
   
    $$DX = 1 (true) if the Lexicon entry is linked 
    to an active ICD code of the type specified by the 
    input parameter TYPE.  
       
    $$DX = 0 (false) if the Lexicon entry is not 
    linked to an active ICD code of the type specified 
    by the input parameter TYPE. 
  
COMPONENT/ENTRY POINT: $$CSDATA(CODE,CSYS,VDT,.ARY)
 COMPONENT DESCRIPTION:   This entry point returns information about a code 
 from a specified coding system.  It is intended to be similar to
 ICDDATA^ICDXCODE except it is not limited to ICD coding systems.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a code found in file 757.02 (CODES file).  
  
VARIABLES: CSYS                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the CODING SYSTEMS file 757.03 
 that identifies the coding system that CODE belongs to.  It is important to
 specify the coding system because some codes overlap various coding systems.  
  
VARIABLES: VDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the date that will be used to determine the
 status of the code in the CODE input parameter.  The status will either be
 Inactive or Active.  
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of a local array passed by reference
 that will contain the output. 
  
 ARY() 
    
  Lexicon Data 
  
     ARY("LEX",1)         IEN ^ Preferred Term 
     ARY("LEX",2)         Status ^ Effective Date 
     ARY("LEX",3)         IEN ^ Major Concept Term 
     ARY("LEX",4)         IEN ^ Fully Specified Name 
     ARY("LEX",5)         Hierarchy (if it exists) 
     ARY("LEX",6,0)       Synonyms/Other Forms 
     ARY("LEX",6,1)         Synonym #1 
     ARY("LEX",6,n)         #n 
     ARY("LEX",7,0)       Semantic Map 
     ARY("LEX",7,1,1)       Class ^ Type (internal) 
     ARY("LEX",7,1,2)       Class ^ Type (external) 
     ARY("LEX",7,1,n)       #n 
     ARY("LEX",7,1,n)       #n 
     ARY("LEX",8)         Deactivated Concept Flag 
    
  Coding System Data 
  
     ARY("SYS",1)         IEN 
     ARY("SYS",2)         Short Name 
     ARY("SYS",3)         Age High 
     ARY("SYS",4)         Age Low 
     ARY("SYS",5)         Sex 
     ARY("SYS",6,0)       MDC/DRG Pairing 
     ARY("SYS",6,1,1)       MDC 
     ARY("SYS",6,1,2)       DRGs 
     ARY("SYS",6,n,1)       #n 
     ARY("SYS",6,n,2)       #n 
     ARY("SYS",7)         Complication/Comorbidity 
     ARY("SYS",8)         MDC13 
     ARY("SYS",9)         MDC24 
     ARY("SYS",10)        MDC24 
     ARY("SYS",11)        Unacceptable as Principal Dx 
     ARY("SYS",12)        Major O.R. Procedure 
     ARY("SYS",13)        Procedure Category 
     ARY("SYS",14,0)      Description 
     ARY("SYS",14,1)        Text 1 
     ARY("SYS",14,n)        #n 
    
  Each data element will be in the following format: 
    
     ARY(ID,SUB) = DATA 
     ARY(ID,SUB,"N") = NAME 
     
       Where 
     
         ID      Identifier, may be: 
         
                     "LEX" for Lexicon data 
                     "SYS" for Coding System data 
                   
         SUB     Numeric Subscript 
         
         DATA    This may be: 
         
                     A value if it applies and is found 
                     Null if it applies but not found 
                     N/A if it does not apply 
                   
         NAME    This is the common name given to the 
                 data element 
  
 Example: 
  
 S X=$$CSDATA^LEXU("C18.6",30,3141010,.ARY) 
  
 X=1 
  
 ARY("LEX",1)="267081^Malignant neoplasm of descending colon" 
 ARY("LEX",1,"N")="IEN ^ Preferred Term" ARY("LEX",2)="1^3131001" 
 ARY("LEX",2,"N")="Status ^ Effective Date" ARY("LEX",3)="267081^Malignant
 neoplasm of descending colon" ARY("LEX",3,"N")="IEN ^ Major Concept Term" 
 ARY("LEX",4)="" ARY("LEX",4,"N")="IEN ^ Fully Specified Name" ARY("LEX",5)="" 
 ARY("LEX",5,"N")="Hierarchy (if exists)" ARY("LEX",6,0)=0 
 ARY("LEX",6,0,"N")="Synonyms and Other Forms" ARY("LEX",7,0)=1 
 ARY("LEX",7,0,"N")="Semantic Map" ARY("LEX",7,1,1)="6^47" 
 ARY("LEX",7,1,1,"N")="Semantic Class ^ Semantic Type (internal)" 
 ARY("LEX",7,1,2)="Diseases/Pathologic Processes^Disease or Syndrome" 
 ARY("LEX",7,1,2,"N")="Semantic Class ^ Semantic Type (external)" 
 ARY("LEX",8)="" ARY("LEX",8,"N")="Deactivated Concept Flag" 
 ARY("SYS",1)=501148 ARY("SYS",1,"N")="IEN" ARY("SYS",2)="Malignant neoplasm of
 descending colon" ARY("SYS",2,"N")="Short Name" ARY("SYS",3)="" 
 ARY("SYS",3,"N")="Age High" ARY("SYS",4)="" ARY("SYS",4,"N")="Age Low" 
 ARY("SYS",5)="" ARY("SYS",5,"N")="Sex" ARY("SYS",6,0)=0 
 ARY("SYS",6,0,"N")="MDC/DRG" ARY("SYS",7)="" 
 ARY("SYS",7,"N")="Complication/Comorbidity" ARY("SYS",8)="" 
 ARY("SYS",8,"N")="MDC13" ARY("SYS",9)="" ARY("SYS",9,"N")="MDC24" 
 ARY("SYS",10)="" ARY("SYS",10,"N")="MDC24" ARY("SYS",11)="" 
 ARY("SYS",11,"N")="Unacceptable as Principal Dx" ARY("SYS",12)="N/A" 
 ARY("SYS",13)="N/A" ARY("SYS",14,0)=1 ARY("SYS",14,0,"N")="Description" 
 ARY("SYS",14,1)="MALIGNANT NEOPLASM OF DESCENDING COLON" 
  
VARIABLES: $$CSDATA                     TYPE: Output
 VARIABLES DESCRIPTION:   This is a boolean value: 
  
    1 if the API is successful (fully or partial) 
    0 if the API is unsuccessful 
  
       or 
  
    -1 ^ Error Message 
  
COMPONENT/ENTRY POINT: $$FREQ(TEXT)
 COMPONENT DESCRIPTION:   This API checks the frequency of use of keywords 
 contained in a text string in the Lexicon.  
  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a text string intended as the input for a
 Lexicon search.  
  
VARIABLES: $$FREQ                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the maximum number of records that must be
 inspected during a Lexicon search to find matching entries for the input
 search text. 
  
 If this number is too high, applications can prompt the user to either
 continue with the search or to further refine the search.  
  
COMPONENT/ENTRY POINT: $$MAX(SYS)
 COMPONENT DESCRIPTION:   This API returns the SEARCH THRESHOLD field #12 of
 the CODING SYSTEMS file #757.03.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the CODING SYSTEM file #757.03.  
  
VARIABLES: $$MAX                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the value stored in the SEARCH THRESHOLD 
 field #12 of the CODING SYSTEMS file 757.03.  This value, along with the value
 of $$FREQ^LEXU, can be used to evaluate if a search should continue or be
 further refined.  
  
 $$FREQ  The maximum number or records to inspect 
         during a search based on the input text 
         string.  
  
 $$MAX   The maximum number of records to consider 
         for a coding system before refining the 
         search.  
  
COMPONENT/ENTRY POINT: $$CAT(CODE)
 COMPONENT DESCRIPTION:   This API returns the category (i.e., header) of an
 ICD Diagnosis code.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a valid ICD Diagnosis code.  
  
VARIABLES: $$CAT                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the category (or header) to which the ICD
 Diagnosis code belongs.  
  
COMPONENT/ENTRY POINT: $$ISCAT(CODE)
 COMPONENT DESCRIPTION:   This API determines if an ICD-10 string is an ICD
 category.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a string used to determine if it is an ICD-10
 code or a category.  
  
VARIABLES: $$CODE                       TYPE: Output
 VARIABLES DESCRIPTION:   This is a 4 piece "^" delimited string containg the
 following: 
  
   1  Category flag 
         1 CODE is a Category 
         0 CODE is not a Category 
     
   2  Number of Sub-Categories belonging 
      to the Category 
   
   3  Number of Codes belonging to the 
      Category 
      
   4  Parent Category 
         Parent Category 
         Null if no Parent Category 
  
COMPONENT/ENTRY POINT: $$PFI(FRAG,CDT,.ARY)
 COMPONENT DESCRIPTION:   This API returns a local array containing information 
 about an ICD-10 procedure code fragment.  
  
VARIABLES: FRAG                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a string representing a fragment of an ICD-10
 procedure code.  An ICD-10 code is 7 characters long and a code fragment is a
 portion of the code starting at character position #1 and not to exceed 6
 characters in length.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the versioning date used to select an entry
 that was appropriate on the date passed.  If no date is passed, TODAY is used. 
 
 Busines rules apply, if the date passed is before the implementation date for
 ICD-10, then the implementation date is used.  
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is a local array passed by reference that will
 contain information about a code fragment.  
  
  ARY(0)      5 piece "^" delimited strig 
                  1  Unique Id 
                  2  Code Fragment 
                  3  Date Entered 
                  4  Source 
                  5  Details 
              
  ARY(1)      4 piece "^" delimited string 
                  1  Effective Date 
                  2  Status 
                  3  Effective Date External 
                  4  Status External 
              
  ARY(2)      Name/Title 
  ARY(3)      Description 
  ARY(4)      Explanation 
  ARY(5,0)    # of synonyms included 
  ARY(5,n)    Included synonyms 
  
VARIABLES: $$PFI                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a success flag 
  
       1 on success 
      -1 ^ error message on error 
  
COMPONENT/ENTRY POINT: $$NXSAB(SAB,REV)
 COMPONENT DESCRIPTION:   This API returns the next Source Abbreviation found
 in the CODING SYSTEMS file 757.03 using the ASAB cross-reference.  It is the
 equivalent of $O(^LEX(757.03,"ASAB",SAB)).  
  
VARIABLES: SAB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is either a Source Abbreviation (SAB) from the
 .01 field of file 757.03 or null value to find the first SAB. 
  
VARIABLES: REV                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a reverse flag (optional).  If set to 1 the
 API will find the next Source Abbreviation in the reverse order (aka, previous
 SAB) 
  
VARIABLES: $$NXSAB                      TYPE: Output
 VARIABLES DESCRIPTION:   This is either the next Source Abbreviation (SAB)
 previous SAB (when reverse flag set to 1) or null if the input parameter SAB
 has no next SAB.  
  
COMPONENT/ENTRY POINT: $$RECENT(SAB)
 COMPONENT DESCRIPTION:   This API returns a boolean valued flag to indicate if
 the coding system identified by the source abbreviation has been recently
 updated with in a 90 day window (looking forward by 30 days and to the past by
 60 days).  This is to evaluate if a coding system was updated by a quarterly
 patch, and may be used to trigger an code set update protocol.  
  
VARIABLES: SAB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is either a 3 character source abbreviation 
 taken from the .01 field of the CODING SYSTEM file 757.03 or a pointer to the
 CODING SYSTEM file 757.03.  
  
VARIABLES: $$RECENT                     TYPE: Output
 VARIABLES DESCRIPTION:   This is a Boolean valued flag.  
  
 1   indicates the Coding System has been recently 
     updated by a quarterly update by looking 30 days 
     into the future and 60 days for a change made 
     to the coding system.  
  
 0   indicate the Coding System has NOT been recently 
     updated by a quarterly update.  
  
COMPONENT/ENTRY POINT: $$RUPD(SAB)
 COMPONENT DESCRIPTION:   This API returns a date the coding system identified 
 by the source abbreviation has been updated based on a recent date (TODAY+3). 
 This is to evaluate if a coding system was updated by a quarterly patch, and
 may be used to trigger an code set update protocol.  
  
VARIABLES: SAB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is either a 3 character source abbreviation 
 taken from the .01 field of the CODING SYSTEM file 757.03 or a pointer to the
 CODING SYSTEM file 757.03.  
  
VARIABLES: $$RUPD                       TYPE: Output
 VARIABLES DESCRIPTION:   This is date found for the last update to a coding
 system based on a recent date (TODAY+30) 
  
COMPONENT/ENTRY POINT: $$LUPD(SAB,DATE)
 COMPONENT DESCRIPTION:   This API returns the last date the coding system
 identified by the source abbreviation has been updated based on the date
 supplied (optional).  If no date is supplied, the last date will be returned.  
  
VARIABLES: SAB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is either a 3 character source abbreviation
 taken from the .01 field of the CODING SYSTEM file 757.03 or a pointer to the
 CODING SYSTEM file 757.03.  
  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a date to use to retrieve the last update for
 a coding system (optional) 
  
VARIABLES: $$LUPD                       TYPE: Output
 VARIABLES DESCRIPTION:   This is date found for the last update to a coding
 system based on a recent passed or the last date updated if a date is not 
 passed.  
  
COMPONENT/ENTRY POINT: $$PAR(TXT,.ARY)
 COMPONENT DESCRIPTION:   This API takes a string of text and parses the string
 into words using the parsing logic used by the Lexicon search engine.  
  
VARIABLES: TXT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a text string intended as the input for a
 Lexicon search and will be parsed into words and placed in a local array
 (Required) 
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   Local array, passed by reference 
  
VARIABLES: $$PAR                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of words parsed from the text 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   This is a local array containing the words parsed
 from the input text.  The words are arranged in the order they are found in
 the text; in alphabetical order; and in the order they are used in the Lexicon
 search (frequency order) 
  
 Total words found 
  
    ARY(0)=# 
    
 Words listed in the order they appear in the input variable TXT 
  
    ARY(1)=WORD1 
    ARY(n)=WORDn 
    
 Words listed alphabetically with the frequency of occurrence in the Lexicon 
  
    ARY("B",WORDA)=# (Frequency of Use) 
    ARY("B",WORDB)=# 
    
 Words listed in the frequency order.  This is the order the words will be used
 by the Lexicon search engine, starting with the least frequently used word and
 ending with the most frequently used word.  
  
    ARY("L",1)=SEARCHWORD1 
    ARY("L",n)=SEARCHWORDn 
  
COMPONENT/ENTRY POINT: $$SCT(IEN,DATE)
 COMPONENT DESCRIPTION:   This entry point is a screen used during searches to
 return terms with SNOMED CT codes that are not classified as Veterinary.  
  
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. 
  
VARIABLES: $$SCT                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a Boolean value: 
   
   $$SCT = 1 (true) if the Lexicon entry is 
  
             Linked to an active SNOMED CT code 
             and the term is not a Veterinary term 
       
   $$SCT = 0 (false) if the Lexicon entry is 
  
             Not linked to an SNOMED CT code 
             or the SNOMED CT code is inactive 
             or the term is a Veterinary term 
  
 Excludes terms semantically typed as a Veterinary term.  
  
  DATE ACTIVATED: JUL 11, 2014

NUMBER: 5680                            IA #: 5680
  DATE CREATED: JUN 03, 2011            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEXCODE
  NAME: LEXCODE Expression              ID: LEXCODE
 GENERAL DESCRIPTION:   This is an addendum to ICR 1614 and contains functions
 added to LEXCODE during the implementation of ICD-10 Coding system.  The API
 in this ICR becomes effective on the date of release of patches ICD*18.0*57
 and LEX*2.0*80.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EXP
KEYWORDS: $$EXP
KEYWORDS: ICD10
KEYWORDS: ICD-10
COMPONENT/ENTRY POINT: $$EXP(<CODE>,<SAB>,<DATE>)
 COMPONENT DESCRIPTION:   This entry point allows an application to retrieve an
 active preferred term for a coding system on the date provided. 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Code taken from the Codes file 757.02. (Required) 
  
VARIABLES: SAB                          TYPE: Input
 VARIABLES DESCRIPTION:   Source, this is an internal entry number in file 
 757.03 or the 3 character source mnemonic (found on the ASAB cross-reference
 in file 757.03) or the SOURCE ABBREVIATION (.01 field in file 757.03) It is
 used to distinguish between different coding systems with the same code (i.e.,
 the code 300.01 occurs in both the ICD-9 CM and DSM IV coding systems).
 (Required) 
  
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.  
  
VARIABLES: $$EXP                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a 2 Piece "^" delimited string containing 
  
   Either: 
  
     1  Pointer to Expression file #757.01 
     2  Display Text (Expression) 
  
   or: 
  
     1  -1 
     2  Error Message 
  
  DATE ACTIVATED: JUL 11, 2014

NUMBER: 5681                            IA #: 5681
  DATE CREATED: JUN 06, 2011            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEX10CS
  NAME: LEX10CS                         ID: LEX10CS
 GENERAL DESCRIPTION:   Supported APIs for the implementation of ICD-10. The
 APIs in this ICR become effective on the date of release of patches
 ICD*18.0*57 and LEX*2.0*80.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICDSRCH
KEYWORDS: DIAGSRCH
KEYWORDS: PCSDIG
KEYWORDS: CODELIST
KEYWORDS: ICD-10
KEYWORDS: ICD10
COMPONENT/ENTRY POINT: $$ICDSRCH(TEXT,.ARRAY,DATE,LEN,FILTER)
 COMPONENT DESCRIPTION:   This entry point searches for an ICD code and returns
 active ICD codes found up to the number defined by the input parameter Length. 
 If the date is before the ICD-10 implementation date then the search will be
 conducted for ICD-9 codes.  If the date passed is on or after the ICD-10
 implementation date then the search will be conducted for ICD-10 codes.  
  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   Text or Code to search for.  (Required) 
  
VARIABLES: .ARRAY                       TYPE: Input
 VARIABLES DESCRIPTION:   This is a local output array passed by reference. 
 (Required) 
  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   The date against which the codes found by the search 
 will be compared in order to determine whether the code is active or inactive.
 If not passed, TODAY's date will be used.  (Optional, but when used must be in
 FileMan format) 
  
VARIABLES: LEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This specifies the length of the list of codes.  
 Default value is 30.  (Optional) 
  
VARIABLES: FILTER                       TYPE: Input
 VARIABLES DESCRIPTION:   This is a filter to apply to the search to screen out 
 unwanted entries.  It is MUMPS code in the form of a valid IF statement.  It
 is the same as Fileman's DIC("S").  (Optional) 
  
VARIABLES: $$ICDSRCH                    TYPE: Output
 VARIABLES DESCRIPTION:   2 Piece "^" delimited string the success/error 
 conditions 
  
 A Positive number for successful search not exceeding the Length of the list.  
  
 A Negative number for an unsuccessful search or a search condition 
  
     -1^No codes found 
  
        No codes found and local array not returned 
  
     -2^Too many items found, please refine search 
  
        The list exceeds the number indicated by LEN, 
        however, the first LEN of the Array is 
        returned and the list is marked as a pruned list 
  
VARIABLES: ARRAY                        TYPE: Output
 VARIABLES DESCRIPTION:   Output Array passed by reference containing the codes
 found 
   
     ARRAY(0)=# found ^ Pruning Indicator 
     ARRAY(1)=CODE ^status effective date 
     ARRAY(1,"IDL )=ICD Dx long description (if code) 
     ARRAY(1,"IDL ,1)=ICD Dx IEN ^ effective date 
     ARRAY(1,"IDS )=ICD Dx short description (if code) 
     ARRAY(1,"IDS ,1)=ICD Dx IEN ^ effective date 
     ARRAY(1,"LEX )=Lexicon expression 
     ARRAY(1,"LEX ,1)=Lexicon IEN ^ effective date 
     ARRAY(1,"SYN ,1)=synonym #1 
     ARRAY(1,"SYN",m)=Synonym #m 
  
 Pruning Indicator:  If the second piece of ARY(0) is greater than 0, then the
 list has been pruned, limiting the list to the length specified by the input
 parameter <Len>. 
  
COMPONENT/ENTRY POINT: $$DIAGSRCH(TEXT,.ARRAY,DATE,LEN,FILTER)
 COMPONENT DESCRIPTION:   This entry point searches for an ICD code and returns 
 active ICD-10 codes found up to the number defined by the input parameter
 Length.  This search is similar to $$ICDSRCH^LEX10CS except it only searches
 ICD-10 codes.  
  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   Text or Code to search for.  (Required) 
  
VARIABLES: .ARRAY                       TYPE: Input
 VARIABLES DESCRIPTION:   This is a local output array passed by reference. 
 (Required) 
  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   The date against which the codes found by the search 
 will be compared in order to determine whether the code is active or inactive.
 (Optional, but when used must be in FileMan format) 
  
VARIABLES: LEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This specifies the length of the list of codes.  
 Default value is 30.  (Optional) 
  
VARIABLES: FILTER                       TYPE: Input
 VARIABLES DESCRIPTION:   This is a filter to apply to the search to screen out 
 unwanted entries.  It is MUMPS code in the form of a valid IF statement.  It
 is the same as Fileman's DIC("S").  (Optional) 
  
VARIABLES: $$DIAGSRCH                   TYPE: Output
 VARIABLES DESCRIPTION:   2 Piece "^" delimited string the success/error 
 conditions 
  
 A Positive number for successful search not exceeding the Length of the list.  
  
 A Negative number for an unsuccessful search or a search condition 
  
     -1^No codes found 
  
        No codes found and local array not returned 
  
     -2^Too many items found, please refine search 
  
        The list exceeds the number indicated by LEN, 
        however, the first LEN of the Array is 
        returned and the list is marked as a pruned list 
  
VARIABLES: ARRAY                        TYPE: Output
 VARIABLES DESCRIPTION:   Output Array passed by reference containing the
 ICD-10 codes found 
   
     ARRAY(0)=# found ^ Pruning Indicator 
     ARRAY(1)=CODE or Category ^ status effective date (code only) 
     ARRAY(1,"CAT")=Category Name 
     ARRAY(1,"IDL )=ICD Dx long description (if code) 
     ARRAY(1,"IDL ,1)=ICD Dx IEN ^ effective date 
     ARRAY(1,"IDS )=ICD Dx short description (if code) 
     ARRAY(1,"IDS ,1)=ICD Dx IEN ^ effective date 
     ARRAY(1,"LEX )=Lexicon expression 
     ARRAY(1,"LEX ,1)=Lexicon IEN ^ effective date 
     ARRAY(1,"SYN ,1)=synonym #1 
     ARRAY(1,"SYN",m)=Synonym #m 
     ARRAY(1,"MENU")=Menu Text 
     ARRAY(1,"MSG")=Message (unversioned only) 
  
 Notes: 
  
        Pruning Indicator:  If the second piece of 
        ARRAY(0) is greater than 0, then the list 
        has been pruned, limiting the list to the 
        length specified by the input parameter LEN.  
  
        If there is a message, it can be either: 
  
           Inactive mm/dd/yyyy 
           Pending mm/dd/yyyy 
  
COMPONENT/ENTRY POINT: $$PCSDIG(FRAG,DATE)
 COMPONENT DESCRIPTION:   This entry point takes an ICD-10-PCS code, full or a 
 partial (code fragment), and  returns a list of all possibilities for the next
 character, with any definitions and examples available.  If a full code is 
 passed (7 characters) it will return the code's long description, and status.  
  
VARIABLES: FRAG                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD-10-PCS Code (7 characters) or a
 fragment of an ICD-10-PCS Code (less that 7 characters) (Required) 
  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   The date against which the codes found by the search 
 will be compared in order to determine whether the code is active or inactive.
 (Optional, defaults to TODAY) 
  
VARIABLES: LEXPCDAT                     TYPE: Output
 VARIABLES DESCRIPTION:   This is both a variable and an array.  If the length
 of the FRAG is less than 7, then the array will contain the next level of
 choices and associated data.  If the length of the FRAG is equal to 7, then a
 fully specified code has been passed and the array will contain the long
 description, status and effective date of the code.  
  
 If the string FRAG is a valid code fragment or null, the return value Of
 LEXPCDAT will be 1 and the following array will be returned.  
  
    LEXPCDAT("NEXLEV ,char1, DESC )=char1 description 
    LEXPCDAT("NEXLEV ,char2, DESC )=char2 description 
    LEXPCDAT("NEXLEV ,charn, DESC )=charn description 
  
 If the string FRAG is a valid code the return value Of LEXPCDAT will be 1 and
 the following array will be returned.  
  
    LEXPCDAT("PCSDESC )=long description for code 
    LEXPCDAT("STATUS )=status_ ^ _effective date 
  
 If the string FRAG is a not valid code fragment or null and it is not a valid
 code, the return value Of LEXPCDAT will be 0 and no array will be returned.  
  
COMPONENT/ENTRY POINT: $$CODELIST(SYS,SPEC,SUB,DATE,LEN,FMT)
 COMPONENT DESCRIPTION:   This entry point creates a list of active codes based 
 on an input code mask and date and places the list in a temporary global array
 with a subscript specified by the calling application.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   Coding system the Coding Systems file 757.03.  This 
 can be a pointer, the .01 field or the abbreviated 3 character mnemonic (found
 on the ASAB cross-reference (Required) 
  
VARIABLES: SPEC                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a code from the coding system or a code mask. 
 
 Any character position can be occupied by a question mark "?  to allow any
 value in that character position.  The trailing character may be an asterisk
 indicating any characters that follow are allowable.  The following are all
 valid; C71.0, C71.*, C7?.0 or 02V?0* (Required) 
  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a string, preferably in the calling 
 applications namespace, that will be used as a subscript in a temporary global
 array (optional, if not passed CODELIST will be used as a subscript).  
  
   ^TMP(SUB,$J) 
  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   The date against which the codes found by the search
 will be compared in order to determine whether the code is active or inactive. 
 
 (Optional, but when used, must be in FileMan format) 
  
VARIABLES: LEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This specifies the length of the list of codes.
 Default value is 30.  (Optional) 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   List Format (Optional) 
  
    0 - (zero) returns a brief listing in the 
        global array (codes only) (DEFAULT) 
  
    1 - returns a detailed listing in the 
        global  array, includes the code, a 
        variable pointer the code in a code 
        set file (i.e., ICD-9, CPT, etc), the 
        code's effective date, the expression 
        and the expression IEN from file 
        #757.01.  
  
VARIABLES: $$CODELIST                   TYPE: Output
 VARIABLES DESCRIPTION:   2 Piece "^" delimited string containing 
  
 Either: 
  
    Piece  Meaning 
      1    Positive value for success 
      2    Number of Codes Found 
  
 or: 
  
    Piece  Meaning 
      1    Negative number for error or condition 
      2    Error Message or Condition 
  
 Example errors/conditions 
  
     -1   Coding system not specified  (First 
          parameter is missing) 
     -2   Invalid coding system/source abbreviation 
          (First parameter not valid) 
     -3   No search specification (Second parameter 
          missing) 
     -4   Insufficient search specification" 
          (Second parameter too short) 
     -5   Invalid search specification (Second 
          parameter invalid) 
     -6   Number of matches exceeds specified 
          limit (More matches found, only the 
          number specified will be returned) 
  
VARIABLES: TMP(SUB,$J,                  TYPE: Output
 VARIABLES DESCRIPTION:   This is a global array subscripted as specified by
 the calling application, input parameter SUB.  It contains a list of codes
 found in either a brief or detailed output.  
  
 Brief output array (FMT = 0) 
  
   ^TMP(SUB,$J,0)=Total n 
   ^TMP(SUB,$J,1)=Code 1 
   ^TMP(SUB,$J,2)=Code 2 
   ^TMP(SUB,$J,n)=Code n 
  
  
 Detailed output array (FMT = 1) 
  
   ^TMP(SUB,$J,0)=Total n 
   ^TMP(SUB,$J,1)=Code 1 
   ^TMP(SUB,$J,1,1)=Variable Pointer 1 ^ Code 1 ^ date 
   ^TMP(SUB,$J,1,2)=Term 1 IEN ^ Term 1 
   ^TMP(SUB,$J,1,"MSG")=Message (unversioned only) 
   ^TMP(SUB,$J,2)=Code 2 
   ^TMP(SUB,$J,2,1)=Variable Pointer 2 ^ Code 2 ^ date 
   ^TMP(SUB,$J,2,2)=Term 2 IEN ^ Term 2 
   ^TMP(SUB,$J,2,"MSG")=Message (unversioned only) 
   ^TMP(SUB,$J,n)=Code n 
   ^TMP(SUB,$J,n,1)=Variable Pointer n ^ Code n ^ date 
   ^TMP(SUB,$J,n,2)=Term n IEN ^ Term n 
   ^TMP(SUB,$J,n,"MSG")=Message (unversioned only) 
  
 Notes: 
  
        If the code is found in one of the 
        VistA Code Set files controlled by 
        a Standards Development Organization 
        (SDO) then a variable pointer will 
        be provided for that code in that 
        file.  Example of SDO controlled 
        files include: 
  
          ICD DIAGNOSIS file #80 
          ICD OPERATION/PROCEDURE file #80.1 
          CPT file #81 
          DSM file #627.7 
  
        If there is a message, it can be either: 
  
           Inactive mm/dd/yyyy 
           Pending mm/dd/yyyy 
  
COMPONENT/ENTRY POINT: $$TAX(TEXT,SRC,CDT,SUB,VER)
 COMPONENT DESCRIPTION:   This API returns codes that qualify for building a
 taxonomy.  Originally designed for ICD-10, but modified to include any coding
 system (DSM, ICD, SNOMED CT, CPT, etc.) 
  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the text or code to search for.  
  
VARIABLES: SRC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a string of coding systems delimited by an
 "^" up arrow to limit the search to the desired coding systems.  The string
 can consist of pointers to the CODING SYSTEM file 757.03 or source
 abbreviations.  
  
    Using source abbreviations 
    "ICD^ICP^10D^10P" 
  
    Using source pointers to file 757.03 
    "1^2^30^31" 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This a date used processing versioned data.  Also,
 when a versioned list is required (input parameter VER=1) it is used to
 suppress inactive codes from the list.  
  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the name of a subscript to use in the ^TMP 
 global (optional).  This allows for applications to put the data in their own
 namespace.  It also allows for multiple search results to exist.  
  
   ^TMP(LEXSUB,$J, 
   ^TMP("LEXTAX",$J,    Default 
  
VARIABLES: VER                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a boolean flag that indicates if the search
 is to be versioned.  If set to 1, only active codes will be returned based on
 the date in the CDT input parameter.  If no date, then TODAY is used.  
  
   VER = 0  Return active and inactive codes 
   VER = 1  Version, return active codes only 
  
VARIABLES: $$TAX                        TYPE: Output
 VARIABLES DESCRIPTION:   This the number of codes found by the search or -1 ^
 with an error message.  
  
VARIABLES: TMP(SUB,$J)                  TYPE: Output
 VARIABLES DESCRIPTION:   This is the results of the search saved in the ^TMP
 global with the specified subscript: 
  
   ^TMP(SUB,$J,SRC,(CODE_" "),#) 
     
     5 piece "^" delimited string 
                              
     1   Activation Date (can be a future date) 
     2   Inactivation Date (can be a future date) 
     3   Lexicon IEN to Expression File 757.01 
     4   Variable Pointer to a National file 
     5   Short Name from a National file 
  
   ^TMP(SUB,$J,SRC,(CODE_" "),#,0) 
     
     2 piece "^" delimited string 
                              
     1   Code (no spaces) 
     2   Lexicon Expression 
  
 Example: 
  
 Search for   "DIFFICULTY IN WALKING" For sources  "ICD^10D"  (ICD-9/10
 Diagnosis) 
  
 ^TMP("TAX",$J,0)=3 ^TMP("TAX",$J,1,"719.7 ",1)=2781001^2791001^ 
        329945^4611;ICD9(^DIFFICULTY IN WALKING ^TMP("TAX",$J,1,"719.7
 ",1,0)=719.7^Difficulty 
        in Walking ^TMP("TAX",$J,1,"719.7 ",2)=3031001^3131001^ 
        329945^4611;ICD9(^DIFFICULTY IN WALKING ^TMP("TAX",$J,1,"719.7
 ",2,0)=719.7^Difficulty 
        in Walking ^TMP("TAX",$J,1,"781.2 ",1)=2781001^3131001^ 
        48820^5419;ICD9(^ABNORMALITY OF GAIT ^TMP("TAX",$J,1,"781.2
 ",1,0)=781.2^Abnormality 
        of Gait ^TMP("TAX",$J,30,"R26.2 ",1)=3131001^^5019306^ 
        521502;ICD9(^Difficulty in walking, not 
        elsewhere classified ^TMP("TAX",$J,30,"R26.2 ",1,0)=R26.2^Difficulty 
        in Walking, not elsewhere classified 
  
  DATE ACTIVATED: JUL 11, 2014

NUMBER: 5682                            IA #: 5682
  FILE NUMBER: 8010                     GLOBAL ROOT: ICD10DX(
  DATE CREATED: JUN 07, 2011            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Private                        TYPE: File
  NAME: ICD10DX                         ID: ICD10DX(
 GENERAL DESCRIPTION:   File 8010, global ^ICD10DX, was created to store ICD-10
 diagnosis under the two file solution.  The two file solution had the ICD-9
 codes and ICD-10 codes stored in two separate files.  This solution was
 abandoned in favor of the one file solution where both ICD-9 and ICD-10 are 
 stored in the same file (ICD Diagnosis file 80).  File 8010 will not be
 exported.  This ICR is not used.  
  
  STATUS: Withdrawn                     EXPIRATION DATE: SEP 09, 2013

NUMBER: 5683                            IA #: 5683
  FILE NUMBER: 8010.1                   GLOBAL ROOT: ICD10PR(
  DATE CREATED: JUN 07, 2011            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Private                        TYPE: File
  NAME: ICD10PR                         ID: ICD10PR(
 GENERAL DESCRIPTION:   File 8010.1, global ^ICD10PR, was created to store
 ICD-10 procedures under the two file solution.  The two file solution had the
 ICD-9 codes and ICD-10 codes stored in two separate files.  This solution was 
 abandoned in favor of the one file solution where both ICD-9 and ICD-10 are
 stored in the same file (ICD Diagnosis file 80).  File 8010 will not be
 exported.  This ICR is not used.  
  
  STATUS: Withdrawn                     EXPIRATION DATE: SEP 09, 2013

NUMBER: 5684                            IA #: 5684
  DATE CREATED: JUN 08, 2011            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Private                        TYPE: Routine
  ROUTINE: ICDXCD                       NAME: ICDXCD
  ID: ICDXCD
 GENERAL DESCRIPTION:   Routine ICDXCD was developed to replace ICDCODE during
 the ICD-10 project to navigate between the ICD-9 Diagnosis file 80 and the
 ICD-10 Diagnosis file 8010 under the two file solution.  The two file solution
 had the ICD-9 codes and ICD-10 codes stored in two separate files.  This 
 solution was abandoned in favor of the one file solution where both ICD-9 and
 ICD-10 are stored in the same file (ICD Diagnosis file 80).  Routine ICDXCD
 was abandoned and never exported to test sites, and will not be released to
 the field.  This ICR is not used.  
  
  STATUS: Withdrawn                     EXPIRATION DATE: SEP 09, 2013
KEYWORDS: DX
COMPONENT/ENTRY POINT: $$DX(CODE,FMT,CDT)
 COMPONENT DESCRIPTION:   Returns information about an ICD-10 Diagnosis code.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   ICD-10 Diagnosis Code or Internal Entry Number (IEN) 
 as appropriate to the format input parameter (FMT).  (Required) 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   Input Format;  "E" = Code, "I" = Internal (Optional,
 default IEN) 
  
VARIABLES: CDT                          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. (Optional, default is TODAY) 
  
VARIABLES: $$DX                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns an 19 piece "^" delimited string 
   
     1  IEN ^ICD10DX(       8010 
     2  ICD-10 Dx Code      #.01  0;1 
     3  Identifier          #2    0;2 
     4  Versioned Dx        #67   67;0  
        8010.067   #1   0;2 
     5  Unacc as Prin. Dx   #101  0;4 
     6  Major Dx Cat        #5    0;5 
     7  MDC13               #5.5  0;6 
     8  <null> 
     9  <null> 
    10  Status              #66   66:0 
        8010.066   #.02 0;2 
    11  Sex                 #9.5  0;8 
    12  Inactive Date       #66   66;0 
        8010.066   #.01 0;1 
    13  MDC24               #5.7  0;12 
    14  MDC25               #5.9  0;13 
    15  Age Low             #14   0;14 
    16  Age High            #15   0;15 
    17  Activation Date     #66   66;0 
        8010.066   #.01 0;1 
    18  <null> 
    19  Versioned C/C       #103  69;0 
        8010.0103  #1   0;2 
      
     or 
  
     -1^Error Description 
  
COMPONENT/ENTRY POINT: $$PR(CODE,FMT,CDT)
 COMPONENT DESCRIPTION:   Returns information about an ICD-10 Procedure code.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   ICD-10 Diagnosis Code or Internal Entry Number (IEN)
 as appropriate to the format input parameter (FMT).  (Required) 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   Input Format;  "E" = Code, "I" = Internal (Optional,
 default IEN) 
  
VARIABLES: CDT                          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. (Optional, default is TODAY) 
  
VARIABLES: $$LD                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns an 13 piece ^ delimited string 
     
     1  IEN ^ICD10DX(     8010.1    
     2  ICD-9 code        #.01  0;1 
     3  Id                #2    0;2 
     4  MDC24             #5    0;3 
     5  Oper/Proc         #67   67;0 
        8010.167   #1   0;2 
     6  <null> 
     7  <null> 
     8  <null> 
     9  <null> 
     10 Status            #66   66:0 
        8010.166   #.02 0;2 
     11 Use with Sex      #9.5  0;8 
     12 Inactive Date     #66   66:0 
        8010.166   #.01 0;1 
     13 Activation Date   #66   66:0 
        8010.166   #.01 0;1 
  
     or 
  
     -1^Error Description 
  
COMPONENT/ENTRY POINT: $$SD(IEN,DIC,CDT,ARY,LEN)
 COMPONENT DESCRIPTION:   ICD-10 Diagnosis/Procedure Short Description 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number of either the ICD-10 Diagnosis
 file 8010 or the ICD-10 Procedure file 8010.1.  (Required) 
  
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   Open Global Root/File Number (same as Fileman's DIC
 variable) of either the ICD-10 Diagnosis file 8010 or the ICD-10 Procedure
 file 8010.1.  (Required) 
  
VARIABLES: CDT                          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. (Optional, default is TODAY) 
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   Local array name, passed by reference.  If passed the
 short description will be parsed and stored in this array with a string length
 equal or less than that specified by the input parameter LEN.  (Optional) 
  
VARIABLES: LEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Length of the text strings in the local array passed
 in the input parameter .ARY (15-79, default 60, field length of the short 
 description) (Optional) 
  
VARIABLES: $$SD                         TYPE: Output
 VARIABLES DESCRIPTION:   Short Description OR -1 ^ Error Message 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   If passed, this is a local array containing the short
 description and parsed into string lengths equal or less than that specified
 by the input parameter LEN. The 0 node of the array will be set to a two piece
 "^" delimited string containing the number of text lines stored in the array
 and the effective date of the short description.  
  
 Example 
  
 K X,Y S X=$$SD(1672,8010,3131001,.Y,32) 
  
 .ARY Y is passed with a length of 32 
  
 Y(0)="2^3101001" Y(1)="Mix cellular class Hdgkn lymph," Y(2)="nodes of axla
 and upper limb" 
  
  
COMPONENT/ENTRY POINT: $$LD(IEN,DIC,CDT,ARY,LEN)
 COMPONENT DESCRIPTION:   ICD-10 Diagnosis/Procedure Long Description 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number of either the ICD-10 Diagnosis
 file 8010 or the ICD-10 Procedure file 8010.1.  (Required) 
  
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   Open Global Root/File Number (same as Fileman's DIC
 variable) of either the ICD-10 Diagnosis file 8010 or the ICD-10 Procedure
 file 8010.1.  (Required) 
  
VARIABLES: CDT                          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. (Optional, default is TODAY) 
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   Local array name, passed by reference.  If passed the
 long description will be parsed and stored in this array with a string length
 equal or less than that specified by the input parameter LEN.  (Optional) 
  
VARIABLES: LEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Length of the text strings in the local array passed
 in the input parameter .ARY (15-79, default 60, field length of the long 
 description) (Optional) 
  
VARIABLES: $$LD                         TYPE: Output
 VARIABLES DESCRIPTION:   Long Description OR -1 ^ Error Message 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   If passed, this is a local array containing the long
 description and parsed into string lengths equal or less than that specified
 by the input parameter LEN. The 0 node of the array will be set to a two piece
 "^" delimited string containing the number of text lines stored in the array
 and the effective date of the long description.  
  
 Example 
  
 K X,Y S X=$$LD(1672,8010,3131001,.Y,32) 
  
 .ARY Y is passed with a length of 32 
  
 Y(0)="3^3101001" Y(1)="MIXED CELLULARITY CLASSICAL" Y(2)="HODGKIN LYMPHOMA,
 LYMPH NODES" Y(3)="OF AXILLA AND UPPER LIMB" 
  
  

NUMBER: 5685                            IA #: 5685
  DATE CREATED: JUN 08, 2011            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Private                        TYPE: Routine
  ROUTINE: ICDXAU                       NAME: ICDXAU
  ID: ICDXAU
 GENERAL DESCRIPTION:   Routine ICDXAU was developed to replace ICDAPIU during
 the ICD-10 project to navigate between the ICD-9 Diagnosis file 80 and the
 ICD-10 Diagnosis file 8010 under the two file solution.  The two file solution
 had the ICD-9 codes and ICD-10 codes stored in two separate files.  This 
 solution was abandoned in favor of the one file solution where both ICD-9 and
 ICD-10 are stored in the same file (ICD Diagnosis file 80).  Routine ICDXAU
 was abandoned and never exported to test sites, and will not be released to
 the field.  This ICR is not used.  
  
  STATUS: Withdrawn                     EXPIRATION DATE: SEP 09, 2013
COMPONENT/ENTRY POINT: $$STATCHK(CODE,CDT)
 COMPONENT DESCRIPTION:   This API returns the status, IEN and effective date
 of a code.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD-10 Diagnosis Code or an ICD-10
 Procedure code (IEN not allowed) (Required) 
  
VARIABLES: CDT                          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. (Optional, default is TODAY) 
  
VARIABLES: $$STATCHK                    TYPE: Output
 VARIABLES DESCRIPTION:   3-Piece "^" delimited string, the following are 
 possible outputs: 
  
   1 ^ IEN ^ Effective Date       Active Code 
   0 ^ IEN ^ Effective Date       Inactive Code 
   0 ^ IEN ^ Message              Not Active 
   0 ^ -1  ^ Error Message        Error 
  
COMPONENT/ENTRY POINT: $$NEXT(CODE)
 COMPONENT DESCRIPTION:   Returns the Next ICD-10 Diagnosis/Procedure Code 
 (active or inactive).  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD-10 Diagnosis Code or an ICD-10
 Procedure code (IEN not allowed) (Required) 
  
VARIABLES: $$NEXT                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the Next ICD-10 Code, Null if none 
  
COMPONENT/ENTRY POINT: $$PREV(CODE)
 COMPONENT DESCRIPTION:   Returns the Previous ICD-10 Diagnosis/Procedure Code
 (active or inactive) 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD-10 Diagnosis Code or an ICD-10
 Procedure code (IEN not allowed) (Required) 
  
VARIABLES: $$PREV                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the Previous ICD-10 Code, Null if none 
  
COMPONENT/ENTRY POINT: $$HIST(CODE,.ARY)
 COMPONENT DESCRIPTION:   Returns the activation history of an ICD-10 Code.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD-10 Diagnosis Code or an ICD-10
 Procedure code (IEN not allowed) (Required) 
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   Local array name, passed by reference.  If passed the
 codes activation history will be stored in this array by status and effective 
 date.  (Optional) 
  
VARIABLES: $$HIST                       TYPE: Output
 VARIABLES DESCRIPTION:   The number of activation history entries are 
 returned, or -1 if an error occurs 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   Local array containing the activation histories for a
 given code: 
  
 ARY(0)      = # of Activation History Entries ARY(<date>) = status (1 = Active
 0 = Inactive) ARY("IEN")  = <ien> 
  
  
COMPONENT/ENTRY POINT: PERIOD(CODE,ARY)
 COMPONENT DESCRIPTION:   Returns Activation/Inactivation Periods 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD-10 Diagnosis Code or an ICD-10
 Procedure code (IEN not allowed) (Required) 
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   Local array name, passed by reference.  The 
 activation periods will be stored in this array by date. (Required) 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   Local array containing the activation periods for a
 given code: 
  
 ARY(0) IEN ^ Short Description for TODAY 
  
           NOTE:  Future activations will not 
                  have a short description 
  
        or 
  
        -1 if error 
  
 ARY(Activation Date) = 2 piece string 
  
    1  Inactivation Date 
    2  Short Name 
  
       Where the Short Name is versioned as 
       follows: 
  
         Period is active    
  
           Short Description for the date 
           the period became active 
  
         Period is inactive  
  
           Short Description for the date 
           the period became inactive 
  
       or -1^0 (no period or error) 
  

NUMBER: 5686                            IA #: 5686
  DATE CREATED: JUN 08, 2011            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Private                        TYPE: Routine
  ROUTINE: ICDXLK                       NAME: ICDXLK Special Lookup
  ID: ICDXLK
 GENERAL DESCRIPTION:   Routine ICDXLK was developed to replace as a special
 lookup routine during the ICD-10 project to navigate between the ICD-9
 Diagnosis file 80 and the ICD-10 Diagnosis file 8010 under the two file
 solution.  The two file solution had the ICD-9 codes and ICD-10 codes stored
 in two separate files.  This solution was abandoned in favor of the one file
 solution where both ICD-9 and ICD-10 are stored in the same file (ICD
 Diagnosis file 80).  A special lookup routine ICDEXLK was written to navigate
 between the two code sets in the same file.  Routine ICDXLK was abandoned and
 never exported to test sites, and will not be released to the field.  This ICR
 is not used.  
  
  STATUS: Withdrawn                     EXPIRATION DATE: SEP 09, 2013
COMPONENT/ENTRY POINT: LK
 COMPONENT DESCRIPTION:   This is the entry point for a special lookup.  
  
 Requires DIC      Global Root OR File Number 
  
 Uses     DIC(0)   Parameters 
          DIC("A") Prompt 
          DIC("B") Default 
          DIC("S") Screen 
          DIC("W") Write 
  
 Special Environment variables 
  
   ICDVDT   If this variable exist in the 
            environment and it is a valid 
            Fileman date, it will be used to 
            determine if a code is active or 
            inactive during the lookup, 
            otherwise TODAYs date is used.  
  
   ICDFMT   If this variable exist in the 
            environment it will be used to 
            determine the format of the text 
            in the selection list.  
  
            1  Fileman format 
               Code followed by Text (default) 
  
            2  Lexicon format 
               Text followed by Code 
  
 If DIC(0) contains an "I", control of the lookup is passed back to Fileman.  
  

NUMBER: 5687                            IA #: 5687
  FILE NUMBER: 811.8                    GLOBAL ROOT: PXD(811.8,
  DATE CREATED: JUN 17, 2011            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Transport of Reminder Exchange File Entries
  ID: PXD(811.8,
 GENERAL DESCRIPTION:   The subscribing packages are allowed to use a KIDS
 build to transport Reminder Exchange File entries. This works in conjunction
 with ICR #4371 which covers the Reminder Exchange APIs that are used to
 include the Reminder Exchange file entries in the KIDS build and install them 
 during the post-init. 
  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: REMINDER EXCHANGE
KEYWORDS: KIDS
SUBSCRIBING PACKAGE: HEALTH SUMMARY
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Mental Health is using the Reminder Exchange system to
 update Reminder Dialog entries related to the PCL-5 mental health instrument.  
  DATE ACTIVATED: JAN 14, 2015

NUMBER: 5688                            IA #: 5688
  DATE CREATED: JUN 22, 2011            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: USE XTMP GLOBAL DURING KIDS INSTALL PROCESS
GLOBAL REFERENCE: XTMP(XPDI,XDPA,BLD,
 GENERAL DESCRIPTION:   The AMIE package has a requirement to version control
 new CAPRI TEMPLATE DEFINITIONS (#396.18) file entries when installing a patch.
 Each test patch install has  a different version control number appended to
 the exported entries (e.g. ~###T1 for patch ### test version 1) versus the 
 released patch (e.g. ~### for released patch ###). Currently the developers
 code this in the Pre/Post Init Routine and update it for each test version
 that is done. After the final test version is signed off by test sites the
 Pre/Post Init Routine is appropriately updated to remove the "T#" text.  
  
 Using KERNEL data that is already available within the KIDS installation 
 process, the AMIE developers will be able to provide appropriate version 
 control of CAPRI TEMPLATE DEFINITION file entries without editing the Pre/Post
 Init Routine for each new test and the final released patch version.  
  
 When patch XU*8*559 is released it will define two supported variables for 
 this purpose: XPDNM("TST")=test number and XPDNM("SEQ")=sequence number.  
 Until this patch is released the AMIE team request the ability to utilize the
 following global created in the KERNEL KIDS process which is present during
 the pre and post install process: 
    ^XTMP("XPDI",XPDA,"BLD",XPDBLD,6)=test number^sequence number.  
  
 AMIE Pre/Post Init Routines will check if the above mentioned ^XTMP global 
 exists and if it does use the test number or sequence number for its version
 control requirement. Please note that once the patch is installed the Pre/Post
 Init Routine is deleted from the system.  
  
 This ICR needs to be in place until patch XU*8*559 has been nationally 
 released and installed at all Medical Centers.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: KIDS INSTALL VARIABLE
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  DATE ACTIVATED: JUN 28, 2011

NUMBER: 5689                            IA #: 5689
  DATE CREATED: JUN 22, 2011
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Other
  NAME: RADIOLOGY PROTOCOLS
 GENERAL DESCRIPTION:   The JV application (James A Lovell Federal Health Care
 Center in North Chicago) is requesting the usage of legacy Radiology event
 driver protocols in support of its Radiology Orders Portability requirement. 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: RAD
KEYWORDS: FHCC
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   The JV application needs to subscribe to these
 protocols: 
  
      RA CANCEL 
      RA REG 
      RA RPT 
      RA EXAMINED 

NUMBER: 5690                            IA #: 5690
  FILE NUMBER: 120.82                   GLOBAL ROOT: GMRD(120.82
  DATE CREATED: JUN 22, 2011
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Access to GMR ALLERGIES file (#120.82)
  ID: GMRD(120.82
GLOBAL REFERENCE: GMRD(120.82,DA(1),'CLASS',
FIELD NUMBER: 5                         FIELD NAME: VA DRUG CLASSES
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   List of VA Drug classes that comprise this reactant.  
 GENERAL DESCRIPTION:   This DBIA allows Outpatient Pharmacy package to
 directly read from the VA DRUG CLASSES (#5) multiple.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 120.82
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   ^GMRD (120.82,DO,"CLASS",D1 
  DATE ACTIVATED: JUN 23, 2011

NUMBER: 5691                            IA #: 5691
  DATE CREATED: JUN 24, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORUTL1                       NAME: IDENTIFY CLINIC ORDERS
  ID: ORUTL1
 GENERAL DESCRIPTION:   The purpose of this API call is to allow the calling
 package to identify if an order is a clinic order.  
  STATUS: Withdrawn
KEYWORDS: CLINIC
COMPONENT/ENTRY POINT: ISCLIN
 COMPONENT DESCRIPTION:   By passing in a CPRS Order Number and you will be
 returned a 0 if the order is not a clinic order and 1 if it is.  
VARIABLES: ORDER                        TYPE: Input
 VARIABLES DESCRIPTION:   CPRS Order Number 
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   The API will return a 1 if the order is a clinic
 order, 0 if it is not.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: SEP 27, 2012

NUMBER: 5692                            IA #: 5692
  FILE NUMBER: 162.03                   GLOBAL ROOT: DD(
  DATE CREATED: JUN 30, 2011            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: FIX TO OVERLENGTH NODE IN FILE 162
  ID: DD(
GLOBAL REFERENCE: DD(162.03,X,0)
FIELD NUMBER: 6                         FIELD NAME: CLERK
  LOCATION: 0;7                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Move this field from the 0 node to the 2 node in order to
 reduce the length of the 0 node.  
FIELD NUMBER: 7                         FIELD NAME: BATCH NUMBER
  LOCATION: 0;8                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Move this field from the 0 node to the 2 node in order to
 reduce the length of the 0 node 
FIELD NUMBER: 25                        FIELD NAME: SUPERVISOR
  LOCATION: 0;22                        ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Move this field from the 0 node to the 2 node in order to
 reduce the length of the 0 node.  
 GLOBAL DESCRIPTION:   Data Dictionary Global 
 GENERAL DESCRIPTION:   In 2004 a change was made to the FEE BASIS PAYMENT file
 (#162) which caused 
  the node ^FBAAC(D3,1,D2,1,D1,1,DA,0) to exceed the maximum length allowed 
  by the  SACC.  
  
 The Fee Basis patch FB*3.5*108 will also need to make changes to the Fee BASIS
 PAYMENT file (#162).  These changes cannot be made with the node in its
 current length.  
  
 During the pre-install for patch FB*3.5*108 the pre-install routine needs to 
 make changes to the DD global to move 3 fields from the 0 node to the 2 node 
 in order to make the 0 node of such a length the required changes can be made. 
 
  STATUS: Withdrawn                     DURATION: Next Version
  EXPIRATION DATE: JAN 01, 2012         GOOD ONLY FOR VERSION: 3.5
SUBSCRIBING PACKAGE: FEE BASIS
 SUBSCRIBING DETAILS:   This is a one time use only.  After the install of
 patch FB*3.5*108 this IA will no longer be needed.  

NUMBER: 5693                            IA #: 5693
  DATE CREATED: JUL 06, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORUTL2
  NAME: VEIL CPRS ORDER                 ID: ORUTL2
 GENERAL DESCRIPTION:   This API will allow Lab to veil/unveil an order in
 CPRS.  
  
 This API should ONLY be used if it is necessary to perform rollback for the
 Lab Re-engineering Project that is, as of February 15, 2013, only installed at
 the Huntington, WV, site.  
  STATUS: Active
KEYWORDS: ORUTL2
COMPONENT/ENTRY POINT: VEIL
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The order which is to be veiled or unveiled.  
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   To unveil the order, the STATUS parameter should be
 0. The '@' is left as a possible value for future use. If passed in currently,
 it will unveil the order.  
  
 To veil the order, the STATUS variable should be a 1.  
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: FEB 20, 2013

NUMBER: 5694                            IA #: 5694
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870,
  DATE CREATED: JUL 13, 2011            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Create & Maintain Links in HL LOGICAL LINK file (#870)
  ORIGINAL NUMBER: 5694                 ID: HLCS(870,
 GENERAL DESCRIPTION:   The LSRP software creates and configures 3 new outbound
 links to the Cerner PathNet LIMS system.  
  
   LA7JAPHX - Used for Anatomic Pathology History 
    LA7JMFN - Used for Master File Notifications 
   LA7JPNET - Used for Admissions, Discharge & Transfers 
  
 During this initialization process and as part of the ongoing LSRP 
 maintenance, the software will perform FileMan B cross reference lookups and
 allows for editing fields in the HL7 LOGICAL LINK File (#870).  
  
 The initial configuration of these links is addressed via FileMan calls during
 the post installation process.  All subsequent updates to any field in #870
 are handled via the use of the [HL7 LOGICAL LINK] ScreenMan form and calls to
 ^DDS which is supported by ICR #10031.  
  
 LSRP is requesting permission to update the following list of fields during
 the post installation process via FileMan and all fields in #870 via the use
 of the existing [HL7 LOGICAL LINK] form.  
  
 GLOBAL REFERENCE: 
      ^HLCS(870, 
        .01      NODE                 
        .02      INSTITUTION 
        .08      DNS DOMAIN 
        1        DESCRIPTION 
        2        LLP TYPE 
        4.5      AUTOSTART 
        21       QUEUE SIZE 
        400.01   TCP/IP ADDRESS 
        400.02   TCP/IP PORT 
        400.08   TCP/IP PORT (OPTIMIZED) 
        "B" X-REF 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HL LOGICAL LINK CREATION/EDIT
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: AUG 03, 2011

NUMBER: 5695                            IA #: 5695
  DATE CREATED: JUL 13, 2011            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOUSR1
  NAME: OPEN LINK                       ORIGINAL NUMBER: 5694
  ID: HLOUSR1
 GENERAL DESCRIPTION:   LSRP requests private usage of an HL7 API to determine
 if a link can be opened.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OPEN LINK
COMPONENT/ENTRY POINT: $$IFOPEN(LINK)
VARIABLES: $$IFOPEN                     TYPE: Input
 VARIABLES DESCRIPTION:   Extrinsic function to return whether the specified
 link can be opened.  
  
 Possible values: 
   1 - link can be opened 
   0 - link cannot be opened 
VARIABLES: LINK                         TYPE: Input
 VARIABLES DESCRIPTION:   Name of the link (required), optionally post-fixed
 with ":"_<port #>, will default to that defined for link.  
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: AUG 03, 2011

NUMBER: 5696                            IA #: 5696
  DATE CREATED: JUL 25, 2011            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCAMDA2
  NAME: Add the MDA comments into a List Manager array
  ID: PRCAMDA2
 GENERAL DESCRIPTION:   The following subroutine call is made to the routine
 PRCAMDA2. The input PRCABN is the internal entry number of an entry in the
 BILL/CLAIMS (#399) file, which is dinumed to the ACCOUNTS RECEIVABLE (#430)
 file. The input PRCALN is a line counter for the List Manager screen array.
 The subroutine will load the List Manager VALMAR array.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MCOM(PRCABN,PRCALN)
 COMPONENT DESCRIPTION:   This call is made to add the MDA comments into a List
 Manager array defined by VALMAR.  
VARIABLES: PRCABN                       TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of an entry in the
 BILL/CLAIMS(#399) file, which is dinumed to the ACCOUNTS RECEIVABLE (#430)
 file.  
VARIABLES: PRCALN                       TYPE: Input
 VARIABLES DESCRIPTION:   The line counter for the List Manager screen array.  
VARIABLES: VALMAR                       TYPE: Both
 VARIABLES DESCRIPTION:   Contains the array name of the List Manager screen
 array.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: JUL 25, 2011

NUMBER: 5697                            IA #: 5697
  DATE CREATED: JUL 26, 2011            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SCMCMHTC
  NAME: PCMM MHTC API's for CPRS        ID: SCMCMHTC
 GENERAL DESCRIPTION:   This is a API that returns the Mental Health treatment
 Coordinator from PCMM to CPRS for display in the CPRS Gui.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MHTC
KEYWORDS: PCMM
KEYWORDS: CPRS
COMPONENT/ENTRY POINT: $$START(DFN)
 COMPONENT DESCRIPTION:   Input is the required parameter, internal entry
 number of the patient from the Patient file (#2).  
  
 Function: $$START^SCMCMHTC(DFN) 
  
 Output: IEN^MHTC^Team Position^Role^Team 
  
       IEN   - MHTC internal entry number from file #200.  
       MHTC  - MHTC name from file #404.52.  
       Team Position - Team Position of MHTC from file #404.57.  
       Role - Role of MHTC from 404.57.  
       Team - PCMM Team of the MHTC from file #404.51.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number from Patient file (#2).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: HEALTH SUMMARY
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
  DATE ACTIVATED: DEC 07, 2011

NUMBER: 5698                            IA #: 5698
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870,
  DATE CREATED: JUL 26, 2011            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: HL7 Sending Facility/Logical Link relationship
  ID: HLCS(870,
GLOBAL REFERENCE: HLCS(870,DA,0)
FIELD NUMBER: .08                       FIELD NAME: DNS DOMAIN
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The VistA Radiology/Nuclear Medicine application uses
 HL7 messages to communicate with the teleradiologists associated with the
 National Teleradiology Program. The interface between these two applications 
 requires the software on the NTP side to query the VistA radiology database
 when an order is received by NTP for a new patient.  
  
 The first iteration of the NTP query/Radiology response software utilized v2.3
 HL7 messages and the destination of those responses was defined by the data
 stored in the following two fields: TCP/IP ADDRESS (#400.01) and the TCP/IP
 PORT (OPTIMIZED) (#400.08). These two fields reside within the HL LOGICAL LINK
 (#870) file.  
  
 RA*5.0*107 is the second iteration of the NTP query/Radiology response 
 interface. This iteration will upgrade the HL7 version of the message from
 V2.3 to V2.4 and the query will identify the DNS Domain (MSH-4.2) where the
 responses are to be broadcast.  
  
 DNS Domain information is passed as a component of the Sending Facility
 (MSH-4) field associated with the query.  
  
 The DNS Domain is then used to 'look up' the logical link record required to
 complete the HL7 information transfer.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HLO
KEYWORDS: VistA HL7
KEYWORDS: Radiology
KEYWORDS: HL7
KEYWORDS: Logical Link
KEYWORDS: Sending Application
KEYWORDS: DNS Domain
KEYWORDS: MSH-4
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   The VistA Radiology/Nuclear Medicine application will
 use a FileMan Database Server call ($$FIND1^DIC) to resolve the DNS Domain
 into the correct HL LOGICAL LINK record.  
  DATE ACTIVATED: AUG 01, 2011

NUMBER: 5699                            IA #: 5699
  DATE CREATED: AUG 02, 2011            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Supported                      TYPE: Routine
  ROUTINE: ICDXCODE                     NAME: ICDXCODE
  ID: ICDXCODE
 GENERAL DESCRIPTION:   Routine ICDXCODE was developed to replace ICDCODE
 during the ICD-10 project to navigate between the ICD-9 Diagnosis file 80 and
 the ICD-10 Diagnosis file 8010 under the two file solution.  The two file
 solution had the ICD-9 codes and ICD-10 codes stored in two separate files. 
 This solution was abandoned in favor of the one file solution where both ICD-9
 and ICD-10 are stored in the same file (ICD Diagnosis file 80).  A one file
 solution of these APIs can be found in the routine ICDEX (ICD Data Extraction) 
 Routine ICDXCODE will be exported to support applications through the
 transition between the one and two file solutions.  It will be retired 18
 months after the ICD-10 compliance date.  
  
  STATUS: Retired                       EXPIRATION DATE: APR 01, 2017
KEYWORDS: ICDXCODE
KEYWORDS: ICD10
KEYWORDS: ICD-10
KEYWORDS: ICD9
KEYWORDS: ICD-9
KEYWORDS: ICD10DX
KEYWORDS: ICD10PR
COMPONENT/ENTRY POINT: $$ICDDATA(CSYS,CODE,DATE,FRMT)
 COMPONENT DESCRIPTION:   Extract general data of ICD Diagnosis and/or
 Procedures.  
  
VARIABLES: CSYS                         TYPE: Input
 VARIABLES DESCRIPTION:   Coding System (Required) 
  
 Code Type 
   Diagnosis:         DIAG 
   Procedure:         PROC 
  
 Code File 
   ICD-9 Diagnosis:   ICD9 or 80 
   ICD-10 Diagnosis:  ICD10DX or 8010 
   ICD-9 Procedure    ICD0 or 80.1 
   ICD-10 Procedure   ICD10PR or 8010.1 
  
 If Code Type is used (DIAG/PROC) then the input parameter date will be used to
 determine if the out put is ICD-9 or ICD-10.  Dates before the ICD-10
 implementation will return ICD-9 data, and dates on or after the ICD-10 
 implementation will return ICD-10 data.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD code or an Internal Entry Number (IEN)
 or a Variable Pointer: 
    IEN;ICD9( 
    IEN;ICD0( 
    IEN;ICD10DX( 
    IEN;ICD10PR( 
  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   Date in Fileman format.  If not supplied it defaults
 to TODAY.  This date is normally the date that service was provided to the
 patient (i.e. visit date, movement date, or date of onset).  
  
VARIABLES: FRMT                         TYPE: Input
 VARIABLES DESCRIPTION:   Format of the input CODE (optional) 
  
   "E" = external format 
   "I" = internal format (IEN) 
  
 If supplied, it must be consistent with the CODE input parameter.  
  
 If a variable pointer is passed as CODE, then "I" internal format is assumed.  
  
VARIABLES: $$ICDXCODE                   TYPE: Output
 VARIABLES DESCRIPTION:   Diagnosis Code Passed: 
  
    A 19 piece caret (^) delimited string 
  
    1 IEN of code in file 80/8010 
    2 ICD-9/ICD-10 Diagnosis Code (#.01) 
    3 Id (#2) 
    4 Versioned Diagnosis Short Name (67 multiple) 
    5 Unacceptable as Principal Diagnosis (#101) 
    6 Major Dx Cat (#5) 
    7 MDC13 (5.5) 
    8 Compl/Comorb (#70) 
    9 ICD Expanded (#8) 1:Yes 0:No (ICD-9 only) 
   10 Status (66 multiple) 
   11 Sex (#9.5) 
   12 Inactive Date (66 multiple) 
   13 MDC24 (#5.7) 
   14 MDC25 (#5.9) 
   15 Age Low (#14) 
   16 Age High (#15) 
   17 Activation Date (.01 of 66 multiple) 
   18 Message (ICD-9 only) 
   19 Versioned Complication/Comorbidity (#103) 
  
 Procedure Code Passed: 
  
    A 14 piece caret (^) delimited string 
  
    1 IEN of code in file 80.1/8010.1 
    2 ICD-9/ICD-10 code (#.01) 
    3 Id (#2) 
    4 MDC24 (#5) 
    5 Versioned Oper/Proc (67 multiple) 
    6 <null> 
    7 <null> 
    8 <null> 
    9 ICD Expanded (#8) 1:Yes 0:No (ICD-9 only) 
   10 Status (66 multiple) 
   11 Use with Sex (#9.5) 
   12 Inactive Date (66 multipl 
   13 Activation Date (66 multiple) 
   14 Message 
   
  or 
   
  -1^Error Description 
  
  
COMPONENT/ENTRY POINT: $$ICDDESC(CSYS,CODE,DATE,OUTARR)
 COMPONENT DESCRIPTION:   This API returns the long description of either an
 ICD-9 or ICD-10 code.  
  
VARIABLES: CSYS                         TYPE: Input
 VARIABLES DESCRIPTION:   Coding System (Required) 
  
 Code Type 
   Diagnosis:         DIAG 
   Procedure:         PROC 
  
 Code File 
   ICD-9 Diagnosis:   ICD9 or 80 
   ICD-10 Diagnosis:  ICD10DX or 8010 
   ICD-9 Procedure    ICD0 or 80.1 
   ICD-10 Procedure   ICD10PR or 8010.1 
  
 Code System 
   ICD-9 Diagnosis    1 
   ICD-10 Diagnosis   30 
   ICD-9 Procedure    2 
   ICD-10 Procedure   31 
  
 If Code Type is used (DIAG/PROC) then the input parameter date will be used to
 determine if the out put is ICD-9 or ICD-10.  Dates before the ICD-10 
 implementation date will return ICD-9 data, and dates on or after the ICD-10
 implementation date will return ICD-10 data. 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD code (Required) 
  
 It can be an ICD-9 Diagnosis Code, ICD-9 Procedure code, an ICD-10 Diagnosis
 Code or an ICD-10 Procedure code.  The code should be consistent with the
 Coding System (first input parameter) 
  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   Date in Fileman format.  If not supplied it defaults
 to TODAY.  This date is normally the date that service was provided to the
 patient (i.e.  visit date, movement date, or date of onset). The date is used
 to return the appropriate description for the date service was provided.  
  
VARIABLES: OUTARR                       TYPE: Both
 VARIABLES DESCRIPTION:   Input:  Array Name 
  
   e.g. "ARY", "ABC" or "ABC("TEST")" 
   Default = ^TMP("ICDD",$J) 
  
 If ^TMP("ICDD",$J) is used, the calling application is responsible for killing
 the global variable when no longer needed.  
  
 Output 
  
    @ARY(1) = Versioned Description (68 multiple) 
    @ARY(2) = Blank (ICD-9 only) 
    @ARY(3) = Message (ICD-9 only): 
              CODE TEXT MAY BE INACCURATE 
  
VARIABLES: $$ICDDESC                    TYPE: Output
 VARIABLES DESCRIPTION:   Number of lines in output array 
  
COMPONENT/ENTRY POINT: $$HIST(SYS,CODE,.ARY)
 COMPONENT DESCRIPTION:   This API returns the effective dates and status from
 the code's status history.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the the CODING SYSTEM file 80.4 
  
    1 = ICD-9-CM 
    2 = ICD-9-PCS 
   30 = ICD-10-CM 
   31 = ICD-10-PCS 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD Code (IEN not allowed) 
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is a local array name passed by reference that 
 will contain the output.  
  
   ARY(0)      =  Number of Activation History 
                  Entries or -1 on error 
  
   ARY(<date>) =  Status    where: 1 is Active 
   ARY("IEN")  =  <ien> 
  
VARIABLES: $$HIST                       TYPE: Output
 VARIABLES DESCRIPTION:   This output variable mirrors ARY(0) if histories are
 found or, -1 on error.  
  
COMPONENT/ENTRY POINT: $$NEXT(SYS,CODE)
 COMPONENT DESCRIPTION:   This API returns the next code in a sequence.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the the CODING SYSTEM file 80.4 
  
    1 = ICD-9-CM 
    2 = ICD-9-PCS 
   30 = ICD-10-CM 
   31 = ICD-10-PCS 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD Code (IEN not allowed) 
  
VARIABLES: $$NEXT                       TYPE: Output
 VARIABLES DESCRIPTION:   The Next ICD Code, or the first ICD code if CODE is
 null or null if CODE is the last ICD code.  
  
COMPONENT/ENTRY POINT: $$PREV(SYS,CODE)
 COMPONENT DESCRIPTION:   This API returns the previous ICD code in a sequence. 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the the CODING SYSTEM file 80.4 
  
    1 = ICD-9-CM 
    2 = ICD-9-PCS 
   30 = ICD-10-CM 
   31 = ICD-10-PCS 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD Code (IEN not allowed) 
  
VARIABLES: $$PREV                       TYPE: Output
 VARIABLES DESCRIPTION:   The Previous ICD Code, or the last ICD code if CODE 
 is null or null if CODE is the first ICD code.  
  
COMPONENT/ENTRY POINT: $$STATCHK(SYS,CODE,CDT)
 COMPONENT DESCRIPTION:   This API returns the status of a code and the code's
 Internal Entry Number (IEN).  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the the CODING SYSTEM file 80.4 
  
    1 = ICD-9-CM 
    2 = ICD-9-PCS 
   30 = ICD-10-CM 
   31 = ICD-10-PCS 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD Code (IEN not allowed) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a date in Fileman format that will be used to
 determin the status of CODE.  (Optional, default = TODAY) 
  
VARIABLES: $$STATCHK                    TYPE: Output
 VARIABLES DESCRIPTION:   This is a 2-piece "^" delimited string containing the 
 code's status and the IEN if the code exists, else -1.  The following are
 possible outputs: 
    
    1^IEN    Active Code 
    0^IEN    Inactive Code 
    0^-1     Code not Found 
  
COMPONENT/ENTRY POINT: $$PERIOD(SYS,CODE,.ARY)
 COMPONENT DESCRIPTION:   This API returns activation periods (from/to dates).  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the the CODING SYSTEM file 80.4 
  
    1 = ICD-9-CM 
    2 = ICD-9-PCS 
   30 = ICD-10-CM 
   31 = ICD-10-PCS 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD Code (IEN not allowed) 
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is a local array name passed by reference that
 will contain the output.  
  
 ARY(0) = IEN ^ Selectable ^ Error Message 
             
          Where IEN = -1 if error 
          Selectable = 0 for unselectable 
          Error Message if applicable 
  
 ARY(Activation Date) = Inactivation Date^Short Name 
  
   Where the Short Name is versioned as follows: 
  
   Period is active    Short Description for the date 
                       the period became active 
     
   Period is inactive  Short Description for the date 
                       the period became inactive 
  
  DATE ACTIVATED: APR 14, 2016

NUMBER: 5700                            IA #: 5700
  FILE NUMBER: 95.3                     GLOBAL ROOT: LAB
  DATE CREATED: AUG 03, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: ACCESS TO LAB LOINC FILE        ID: LAB
GLOBAL REFERENCE: LAB(95.3,D0,0
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The unique LOINC code in numeric form.  
FIELD NUMBER: 80                        FIELD NAME: FULLY SPECIFIED NAME
  LOCATION: 80;1                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the fully specified name of the LOINC
 code.  It has five or six major parts including: the name of the component or
 analyte measured, the property observed, the timing of the measurement, the
 type of sample, the scale of measurement, and where relevant, the method of
 the measurement.  The colon character, ":", is part of the name and is used to 
 separate the main parts of the name.  
FIELD NUMBER: 81                        FIELD NAME: SHORTNAME
  LOCATION: 81;1                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field was introduced in LOINC version 2.07, the
 field is a concatenation of the fully specified LOINC name. This field maybe
 used as the test name on reports rather than the fully specified name in FULLY 
 SPECIFIED NAME (#80) field.  
 GENERAL DESCRIPTION:   This file contains information about LOINC codes and
 associated text for describing Lab tests.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: LAB
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   Lab Orders Portability accesses this file in converting
 DoD entered Lab Orders for storage into VistA.  
  
 All access by North Chicago project software to this file is read only, using
 the "DSIC FM FIND" RPC to invoke FileMan lookup from our Java code.  
  
 DSIC FM FIND is used by orders processing services in the VA ESB to obtain
 information on laboratory orders.  When the VA ESB processes a lab order, it
 is the first RPC call and is used to obtain the Orderable Item IEN, which sets
 up all subsequent calls to DSIC FM FIND and DSIC DDR GETS ENTRY DATA.  It is
 also used to obtain, among other purposes, a list of component test IENs for a
 lab panel.  

NUMBER: 5701                            IA #: 5701
  FILE NUMBER: 64                       GLOBAL ROOT: LAM
  DATE CREATED: AUG 03, 2011            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: ACCESS TO LAB WKLD FILE         ID: LAM
GLOBAL REFERENCE: LAM(D0,0
FIELD NUMBER: .01                       FIELD NAME: PROCEDURE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   DESCRIPTION:      The procedure or test name.  The names
 contained in this file are derived from a national list of laboratory
 procedures.  
  
 This file is updated as needed from VACO Pathology. THIS FILE SHOULD NOT BE
 EDITED BY FILEMAN AT THE LOCAL LEVEL.  
  
 Utilities are provided for local sites to manipulate distributed file data to
 meet their needs. If a site determines a procedure which they perform is not
 in this file, they are to contact VACO pathology for procedures to obtain new
 entries. When attempting to look up data in this file, do not use commas, dash
 hyphens or slash. AS A GENERAL RULE THE SYNONYM FIELD HAS THE FIRST WORD AND
 THE SECOND WORD OF A PROCEDURE REVERSED TO PERMIT EASIER LOOK UP. YOU MAY
 LOOKUP DATA USING EITHER UP OR LOWER CASE NAMES.  
  
 TECHNICAL DESCR:   The entries from 0-99999 are nationally distributed 
 procedures The entries above 99999 are additional procedures required by this
 site to report LMIP/Workload data. Data found between 0-99999 will be 
 periodically purged/over written during file updating with addition procedure
 codes.  
FIELD NUMBER: 1                         FIELD NAME: WKLD CODE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The code number of the AMIS report for the procedure.  
FIELD NUMBER: 25                        FIELD NAME: DEFAULT LOINC CODE     
  LOCATION: 9;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field is used to identify the default LOINC code.
 This field is usually used when the specimen is not clinically significant
 (i.e. body fluids).  
GLOBAL REFERENCE: LAM(D0,5,0
FIELD NUMBER: 20                        FIELD NAME: SPECIMEN
  LOCATION: 5;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Specimen associated with the test.  
GLOBAL REFERENCE: LAM(D0,5,D1,0
FIELD NUMBER: .01                       FIELD NAME: SPECIMEN
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Specimen associated with this procedure.  
GLOBAL REFERENCE: LAM(D0,5,D1,1,0
FIELD NUMBER: 30                        FIELD NAME: TIME ASPECT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the timing of the measurement or
 observation for this test for this specimen.  
GLOBAL REFERENCE: LAM(D0,5,D1,1,D2,1
FIELD NUMBER: 4                         FIELD NAME: LOINC CODE
  LOCATION: 1;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   All access to this file is read only, through the
 specific RPCs "DSIC DDR GETS ENTRY DATA" and "DSIC FM LIST" that allow Java
 code to access VistA data through FileMan.  
 GENERAL DESCRIPTION:   This file contains information on Laboratory
 procedures.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: JV
KEYWORDS: LAB
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
 SUBSCRIBING DETAILS:   North Chicago Order Portability software accesses this
 file when transforming Lab Orders from DoD for storage into VistA.  
  
 All access to this file is read only, through the specific RPCs "DSIC DDR GETS
 ENTRY DATA" and "DSIC FM LIST" that allow Java code to access VistA data
 through FileMan.  
  
 DSIC DDR GETS ENTRY DATA is used by orders processing services in the VA ESB
 to obtain information on laboratory orders, particularly to identify the LOINC
 and workload codes associated with a given lab test.  

NUMBER: 5702                            IA #: 5702
  DATE CREATED: AUG 03, 2011
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMVRPCM
  NAME: GMVRPCM                         ID: GMVRPCM
 GENERAL DESCRIPTION:   This routine performs various actions such as building
 selection lists and modifying package parameters; VPR requests use of it to
 pull values from the GMRV Vitals Parameters file #120.57.  Complete details
 about this call may be found in ICR #4360, RPC 'GMV MANAGER'.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RPC(.RESULTS,OPTION,DATA)
 COMPONENT DESCRIPTION:   VPR will call with OPTION='GETHILO' 
VARIABLES: RESULTS                      TYPE: Both
 VARIABLES DESCRIPTION:   The ^TMP("GMVMGR",$J) global array reference
 containing the results.  
VARIABLES: OPTION                       TYPE: Input
 VARIABLES DESCRIPTION:   Identifies the linetag in the GMVRPCM routine to be
 invoked by this call.  
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   Any additional values needed by the OPTION tag to
 process the call.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
  DATE ACTIVATED: MAY 25, 2012

NUMBER: 5703                            IA #: 5703
  FILE NUMBER: 9000011                  GLOBAL ROOT: AUPNPROB(
  DATE CREATED: AUG 03, 2011            CUSTODIAL PACKAGE: PROBLEM LIST
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROBLEM file data
  ID: AUPNPROB(
GLOBAL REFERENCE: AUPNPROB(D0,0
FIELD NUMBER: .03                       FIELD NAME: DATE LAST MODIFIED
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: FACILITY
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DATE ENTERED
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .13                       FIELD NAME: DATE OF ONSET
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: AUPNPROB(D0,1
FIELD NUMBER: 1.03                      FIELD NAME: ENTERED BY
  LOCATION: 1;3                         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.07                      FIELD NAME: DATE RESOLVED
  LOCATION: 1;7                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This private agreement allows the Virtual Patient
 Record (VPR) access to data in the Problem file #9000011 that is not available
 in internal format via the current GMPL api's.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: AUG 02, 2013

NUMBER: 5704                            IA #: 5704
  DATE CREATED: AUG 03, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORQ12
  NAME: ORQ12                           ID: ORQ12
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GET(IEN,ORLIST,DETAIL,ACTION)
 COMPONENT DESCRIPTION:   Returns details about an order in
 ^TMP("ORR",$J,ORLIST,i).  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   ORDERS file #100 ien.  
VARIABLES: ORLIST                       TYPE: Input
 VARIABLES DESCRIPTION:   A unique list ID, usually $H.  
VARIABLES: DETAIL                       TYPE: Input
 VARIABLES DESCRIPTION:   Boolean, returns order details if set to 1.  
VARIABLES: ACTION                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional ien from Order Actions sub-file to return a
 specfic order action or view; default is the current state of the order.  
VARIABLES: TMP('ORR',$J,ORLIST,i)       TYPE: Output
 VARIABLES DESCRIPTION:   Returns data about the order depending on DETAIL: 
 DETAIL=0: ^TMP("ORR",$J,ORLIST,i) = order# DETAIL=1: ^TMP("ORR",$J,ORLIST,i) =
 order# ^ group ^ entered d/t ^ start d/t ^ stop d/t ^ status ^ sts abbrev 
           ^TMP("ORR",$J,ORLIST,i,"TX",j) = order text 
VARIABLES: TMP('ORGOTIT',$J,IEN)        TYPE: Output
 VARIABLES DESCRIPTION:   Index to ^TMP("ORR",$J,ORLIST,i), listing the IEN and
 ACTIONs returned 
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP routines HMPDJ01 and HMPDOR call the GET^ORQ12 API
 in order to retrieve details about an order.  
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
  DATE ACTIVATED: AUG 02, 2013

NUMBER: 5705                            IA #: 5705
  FILE NUMBER: 410                      GLOBAL ROOT: description
  DATE CREATED: AUG 08, 2011            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FILE 410 DESCRIPTION UPDATE
  ID: description
GLOBAL REFERENCE: FILE DESCRIPTION
 GENERAL DESCRIPTION:   Add to end of file 410 description the wording: 
    *******DO NOT RE-INDEX THIS FILE******* 
  
 per instructions from national support as re-indexing has been causing site
 errors.  
  
 One time agreement in patch PRC*5.1*157. Post install routine PRC157P will add
 file description node in file global ^DIC: 
  
 ^DIC(410,"%D",7,0)="    *********DO NOT RE-INDEX THIS FILE**********" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: AUG 18, 2012
KEYWORDS: DESCRIPTION
KEYWORDS: PRC157P
SUBSCRIBING PACKAGE: IFCAP
 SUBSCRIBING DETAILS:   Adding 'DO NOT REINDEX' warning to end of file 410
 description.  
  DATE ACTIVATED: AUG 08, 2011

NUMBER: 5706                            IA #: 5706
  FILE NUMBER: 442                      GLOBAL ROOT: DESCRIPTION
  DATE CREATED: AUG 08, 2011            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FILE 442 DESCRIPTION UPDATE
  ID: DESCRIPTION
GLOBAL REFERENCE: FILE DESCRIPTION
 GENERAL DESCRIPTION:   Add to end of file 442 description the wording: 
    *******DO NOT RE-INDEX THIS FILE******* 
  
 per instructions from national support as re-indexing has been causing site
 errors.  
  
 One time agreement in patch PRC*5.1*157. Post install routine PRC157P will add
 file description node in file global ^DIC: 
  
 ^DIC(442,"%D",5,0)="    *********DO NOT RE-INDEX THIS FILE**********" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: AUG 18, 2012
KEYWORDS: DESCRIPTION
KEYWORDS: PRC157P
SUBSCRIBING PACKAGE: IFCAP
  DATE ACTIVATED: AUG 08, 2011

NUMBER: 5707                            IA #: 5707
  FILE NUMBER: 443.6                    GLOBAL ROOT: DESCRIPTION
  DATE CREATED: AUG 08, 2011            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FILE 443.6 DESCRIPTION UPDATE
  ID: DESCRIPTION
GLOBAL REFERENCE: FILE DESCRIPTION
 GENERAL DESCRIPTION:   Add to end of file 443.6 description the wording: 
    *******DO NOT RE-INDEX THIS FILE******* 
  
 per instructions from national support as re-indexing has been causing site
 errors.  
  
 One time agreement in patch PRC*5.1*157. Post install routine PRC157P will add
 file description node in file global ^DIC: 
  
 ^DIC(443.6,"%D",7,0)="    *********DO NOT RE-INDEX THIS FILE**********" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: AUG 18, 2012
KEYWORDS: DESCRIPTION
KEYWORDS: PRC157P
SUBSCRIBING PACKAGE: IFCAP
  DATE ACTIVATED: AUG 08, 2011

NUMBER: 5708                            IA #: 5708
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: AUG 08, 2011            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ALIAS SUBFILE
  ID: DPT(
GLOBAL REFERENCE: DPT(D0,.01
FIELD NUMBER: .01                       FIELD NAME: ALIAS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Virtual Patient Record (VPR) requests permission to
 read the ALIAS field #1 (subfile #2.01).  
  
 Outpatient Pharmacy (PSO) requests permission to read the ALIAS field #1 
 (subfile #2.01) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 10/17/24 effective with patch PSO*7*772 to
 support State Prescription Monitoring Program (SPMP)functionality which
 transmits controlled substance prescription data to the state PDMP for
 mandatory reporting.  
  DATE ACTIVATED: APR 24, 2013

NUMBER: 5709                            IA #: 5709
  DATE CREATED: AUG 12, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORDEA
  NAME: DEA DATA RETRIEVAL              ID: ORDEA
 GENERAL DESCRIPTION:   Provide information about controlled substance signing
 and digital signatures.  
  STATUS: Active
KEYWORDS: ORDEA
KEYWORDS: DEA
COMPONENT/ENTRY POINT: ARCHIVE
 COMPONENT DESCRIPTION:   retrieve archive for specified order number 
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   ORIFN is the CPRS order number whose archive is
 requested 
VARIABLES: RETURN                       TYPE: Output
 VARIABLES DESCRIPTION:   archive for specified order number.  RETURN is in the
 form of ^TMP($J,"ORDEA") 
COMPONENT/ENTRY POINT: SUBSCRIB
 COMPONENT DESCRIPTION:   API for Pharmacy to subscribe to an archive entry 
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   ORIFN is the CPRS order number of the archive
 Pharmacy wants to use 
VARIABLES: RXN                          TYPE: Input
 VARIABLES DESCRIPTION:   RXN is the Pharmacy prescription number that is
 subscribing to the archive 
VARIABLES: RETURN                       TYPE: Output
 VARIABLES DESCRIPTION:   returns a 0 if not successful returns a 1 if
 successful 
COMPONENT/ENTRY POINT: HASHRTN
 COMPONENT DESCRIPTION:   returns hash of a specified archive entry 
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   ORIFN is the CPRS order number for the archive 
VARIABLES: ORHASH                       TYPE: Output
 VARIABLES DESCRIPTION:   hash of a specified archive entry 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
  DATE ACTIVATED: MAR 22, 2018

NUMBER: 5710                            IA #: 5710
  DATE CREATED: AUG 15, 2011            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBAUTL
  NAME: POTENTIAL COPAYMENT CHARGE AMOUNT
  ID: IBAUTL
 GENERAL DESCRIPTION:   This Integration Agreement will allow the AR package to
 look up a potential copayment charge amount based on the rate to be charged
 TODAY.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$ARCOST
 COMPONENT DESCRIPTION:   This entry point will return a potential charge
 amount for the specified patient/medication based on rates that are charged
 with a date of TODAY.  It will return a single per 30 days supply rate value.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient File Pointer 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Pointer value to IB ACTION TYPE (#350.1) file.  
VARIABLES: IBRX                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer value to the PRESCRIPTION (#52) file.  
VARIABLES: $$ARCOST                     TYPE: Output
 VARIABLES DESCRIPTION:   This is a per 30 days supply value that would be
 charged to a medication if billed Today to the patient.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: AUG 16, 2011

NUMBER: 5711                            IA #: 5711
  FILE NUMBER: 366.14                   GLOBAL ROOT: IBCNR(366.14,
  DATE CREATED: AUG 22, 2011            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IB NCPDP EVENT LOG FILE
  ID: IBCNR(366.14,
GLOBAL REFERENCE: IBCNR(366.14,'I',
GLOBAL REFERENCE: IBCNR(366.14,'B',
GLOBAL REFERENCE: IBCNR(366.14,D0,1,D1,2)
FIELD NUMBER: .203                      FIELD NAME: FILL NUMBER
  LOCATION: 2;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The ECME package is performing direct global read-only
 access to the IB NCPDP EVENT LOG file (#366.14) for the purpose of generating
 data from the IB ECME EVENT LOG report to be included in the ECME report View 
 ePharmacy Prescription.  
  STATUS: Active
KEYWORDS: IB ECME EVENT LOG
KEYWORDS: 366.14
KEYWORDS: ECME IB
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
 SUBSCRIBING DETAILS:   ECME is performing read-only access to the following
 cross-references in the IB NCPDP EVENT LOG file (#366.14): 
  
 ^IBCNR(366.14,"I"    : index by Rx ien ^IBCNR(366.14,"B"    : index by event
 date 
  
 And also to the main global where data is stored: 
  
 ^IBCNR(366.14,D0,1,D1,2) 
  DATE ACTIVATED: SEP 14, 2011

NUMBER: 5712                            IA #: 5712
  DATE CREATED: AUG 22, 2011            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPEV
  NAME: PRINT IB ECME BILLING EVENTS REPORT
  ID: IBNCPEV
 GENERAL DESCRIPTION:   The ECME report "View ePharmacy Rx" will include data
 from the IB ECME BILLING EVENT REPORT.  The ECME report compile process will
 establish the necessary scratch global and set up the correct IB variables and
 will make a routine call to PRINT^IBNCPEV which will output the report to the 
 open device.  
  STATUS: Active
COMPONENT/ENTRY POINT: PRINT
 COMPONENT DESCRIPTION:   Entry point PRINT^IBNCPEV will be called by ECME in
 order to output the content of the IB ECME BILLING EVENT REPORT to the open
 device.  ECME has the responsibility to build the proper scratch global and to
 set-up local variables so that no changes are needed to the IB report.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: SEP 14, 2011

NUMBER: 5713                            IA #: 5713
  DATE CREATED: AUG 22, 2011            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBJTU6
  NAME: IB LIST MANAGER DISPLAY DATA    ID: IBJTU6
 GENERAL DESCRIPTION:   This is a generic billing API which allows the
 subscribers to obtain the ListManager display array data from various IB
 ListManager list templates/screens.  
  
 This IB API will return detailed billing information about TPJI third party
 bills and patient insurance policy information.  The content of the data is
 strictly owned by IB and may be changed at any time.  IB does not have to
 notify the subscribers that the content of the IB data which is to be returned
 to them may be changing.  
  STATUS: Active
COMPONENT/ENTRY POINT: IBDSP
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the type of IB screen to extract and build
 the ListManager display array and header data.  Possible values are as
 follows: 
   
   1 : TPJI Claim Information screen (default) 
   2 : TPJI AR Account Profile screen 
   3 : TPJI AR Comment History screen 
   4 : TPJI ECME Rx Response screen 
   5 : Patient Insurance policy expanded information screen 
VARIABLES: IBIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Claim ien file (#399) This is required for any of the
 TPJI data screens.  This is optional for the patient insurance screen.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient ien in file #2.  This is required for the
 patient insurance screen.  This is optional for any of the TPJI screens.  If
 the DFN is passed in it will be used for the TPJI screens.  If the DFN is not
 passed in it will be calculated from the 399,.02 field of the bill.  
VARIABLES: IBCDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the patient INSURANCE TYPE 2.312 subfile ien. 
 
 This is required for the patient insurance screen.  This is not used for the
 TPJI screens.  
VARIABLES: IBLMDISPA                    TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of scratch global name or local
 variable name in which to store the ListManager display array data.  Pass the
 global or local array variable name in closed reference format.  Data will be
 returned in @IBLMDISPA@(LN,0) where LN is a sequential line# counter.  
VARIABLES: VALMHDR                      TYPE: Output
 VARIABLES DESCRIPTION:   This is the standard ListManager VALMHDR header
 array.  It will be built by this IB API and returned to the calling
 application in this parameter.  It must be passed by reference in order to
 return the contents of the VALMHDR array.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: SEP 14, 2011

NUMBER: 5714                            IA #: 5714
  DATE CREATED: AUG 22, 2011            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPDPU
  NAME: IB PHARMACY INSURANCE           ID: IBNCPDPU
 GENERAL DESCRIPTION:   This IB API identifies all active pharmacy insurance
 policy data as of a given date of service and returns an array of insurance
 policies in COB (Coordination of Benefits) sequence order (primary, secondary,
 tertiary).  
  STATUS: Active
COMPONENT/ENTRY POINT: RXINS
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient ien in file #2.  This is required.  
VARIABLES: IBADT                        TYPE: Input
 VARIABLES DESCRIPTION:   Date of Service in Fileman format.  Defaults to today
 if not passed in.  
VARIABLES: IBINS                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the name of destination or target array.  
 Pass by reference in order to return the contents of the array data.  
  
   IBINS = total number of Rx ins policies returned 
  
   IBINS("S",COB seq#,pt ins sub-file ien)="" 
  
   IBINS(pt ins sub-file ien,0) = ^DPT(DFN,.312,pt ins sub-file ien,0) 
   IBINS(pt ins sub-file ien,1) = ^DPT(DFN,.312,pt ins sub-file ien,1) 
   IBINS(pt ins sub-file ien,2) = ^DPT(DFN,.312,pt ins sub-file ien,2) 
   IBINS(pt ins sub-file ien,3) = ^DPT(DFN,.312,pt ins sub-file ien,3) 
   IBINS(pt ins sub-file ien,4) = ^DPT(DFN,.312,pt ins sub-file ien,4) 
   IBINS(pt ins sub-file ien,5) = ^DPT(DFN,.312,pt ins sub-file ien,5) 
   IBINS(pt ins sub-file ien,355.3) = ^IBA(355.3,plan ien,0) 
  
 The pt ins sub-file ien is the internal entry number of the INSURANCE TYPE
 sub-file (#2.312) of the PATIENT file (#2).  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: SEP 14, 2011

NUMBER: 5715                            IA #: 5715
  DATE CREATED: AUG 22, 2011            CUSTODIAL PACKAGE: INTEGRATED BILLING
  NAME: WITHDRAWN                       STATUS: Withdrawn

NUMBER: 5716                            IA #: 5716
  DATE CREATED: AUG 22, 2011            CUSTODIAL PACKAGE: INTEGRATED BILLING
  NAME: WITHDRAWN                       STATUS: Withdrawn

NUMBER: 5717                            IA #: 5717
  DATE CREATED: AUG 22, 2011            CUSTODIAL PACKAGE: INTEGRATED BILLING
  NAME: WITHDRAWN                       STATUS: Withdrawn

NUMBER: 5718                            IA #: 5718
  FILE NUMBER: 3.5                      GLOBAL ROOT: %ZIS(1,
  DATE CREATED: AUG 24, 2011            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: OP ACCESS WINDOWS NETWORK PRINTER NAME IN THE DEVICE FILE
  ID: %ZIS(1,
GLOBAL REFERENCE: %ZIS(1,IOS,WIN
FIELD NUMBER: 75                        FIELD NAME: WINDOWS NETWORK PRINTER NAME
  LOCATION: WIN;1                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the Windows network name for the printer (e.g.,
 '\\DNS\PRINTERID'). It is used by Windows applications that  interact with
 VistA and need a printer identified for output purposes. Permission is granted
 to read the new field via 
  Fileman only, however a direct global reference might be used in a data
 dictionary field screen.  
 GENERAL DESCRIPTION:   Outpatient Pharmacy requests permission to access the
 WINDOWS NETWORK PRINTER NAME field (#75) in the Kernel DEVICE (#3.5) file.
 This field is used to identify the printer location in the Windows network.
 Outpatient Pharmacy will pass the printer location to a Java application so it
 can print documentation in a .pdf format related to a specific prescription.  
  STATUS: Active
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: AUG 24, 2011

NUMBER: 5719                            IA #: 5719
  DATE CREATED: SEP 06, 2011            CUSTODIAL PACKAGE: INTEGRATED BILLING
  NAME: WITHDRAWN                       STATUS: Withdrawn

NUMBER: 5720                            IA #: 5720
  DATE CREATED: SEP 01, 2011            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  NAME: WITHDRAWN                       STATUS: Withdrawn

NUMBER: 5721                            IA #: 5721
  DATE CREATED: AUG 29, 2011            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  ROUTINE: IBJTTC                       NAME: TPJI Comment Array
  ID: IBJTTC
 GENERAL DESCRIPTION:   The following subroutine call is made to the routine
 IBJTTC.  The input IBIFN is the internal entry number of an entry in the
 BILL/CLAIMS (#399) file, which is dinumed to the ACCOUNTS RECEIVABLE (#430)
 file. The subroutine will load the List Manager VALMAR array. 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: TPJI COMMENT
COMPONENT/ENTRY POINT: BLD
 COMPONENT DESCRIPTION:   This call is made to load the TPJI comments into a
 List Manager array defined by VALMAR.  
VARIABLES: IBIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of an entry in the 
 BILL/CLAIMS(#399) file, which is dinumed to the ACCOUNTS RECEIVABLE (#430)
 file.  
VARIABLES: VALMAR                       TYPE: Both
 VARIABLES DESCRIPTION:   Contains the array name of the List Manager screen
 array.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   The IB System shall display the following comments
 types, when present, from the Enter/View Comments action within AR option
 Medicare Deductible Alert Worklist: 
  Accounts Receivable Comments 
  MRA Worklist Comments 
  COB Management Worklist Comments 
  Medicare Deductible Alert Worklist Comments 

NUMBER: 5722                            IA #: 5722
  CUSTODIAL PACKAGE: INTEGRATED BILLING
  NAME: WITHDRAWN                       STATUS: Withdrawn

NUMBER: 5723                            IA #: 5723
  DATE CREATED: SEP 15, 2011            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: BPSVRX
  NAME: VIEW ECME PRESCRIPTION          ID: BPSVRX
 GENERAL DESCRIPTION:   Allows subscribing packages to call ECME routine BPSVRX
 in order to build the View ECME Prescription List Manager screen.  
  STATUS: Active
KEYWORDS: BPSVRX
KEYWORDS: ECME
KEYWORDS: RFL
COMPONENT/ENTRY POINT: BPSVRX
 COMPONENT DESCRIPTION:   Call it from the top:  D ^BPSVRX 
VARIABLES: BPSVRX('RXIEN')              TYPE: Input
 VARIABLES DESCRIPTION:   Calling application may define the internal Rx ien
 (ien to file# 52) into local array entry BPSVRX("RXIEN").  This is optional. 
 If not defined, then the ECME application will prompt for the Rx#.  
VARIABLES: BPSVRX('FILL#')              TYPE: Input
 VARIABLES DESCRIPTION:   Calling application may define the fill number into
 local array entry BPSVRX("FILL#").  This is optional.  If not defined, then
 the ECME application will prompt for the fill#.  
COMPONENT/ENTRY POINT: RFL
 COMPONENT DESCRIPTION:   Returns a list of all ECME fill numbers for a
 prescription from the BPS TRANSACTION file #9002313.59.  
VARIABLES: RXIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN from the PRESCRIPTION File (#52).  
VARIABLES: FILLIST                      TYPE: Output
 VARIABLES DESCRIPTION:   An array that is returned with a list of the Fill
 Numbers from the BPS TRANSACTION File (#9002313.59). The output parameter MUST
 be passed in by reference.  Array output format: 
    FILLIST(fill#)=BPS Transaction file ien (pointer to file #9002313.95).  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: SEP 15, 2011

NUMBER: 5724                            IA #: 5724
  DATE CREATED: SEP 15, 2011            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: BPS RPT VIEW ECME RX
 GENERAL DESCRIPTION:   This agreement allows the ECME option "View ePharmacy
 Rx" [BPS RPT VIEW ECME RX] to be included on the Outpatient Pharmacy parent
 menu option "ePharmacy Menu" [PSO EPHARMACY MENU].  
  STATUS: Active
KEYWORDS: BPSVRX
KEYWORDS: ECME
KEYWORDS: VIEW ECME
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: SEP 15, 2011

NUMBER: 5725                            IA #: 5725
  FILE NUMBER: 3.2                      GLOBAL ROOT: %ZIS(2
  DATE CREATED: SEP 15, 2011            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TERMINAL TYPE
  ID: %ZIS(2
GLOBAL REFERENCE: %ZIS(2,IEN,6)
FIELD NUMBER: 23                        FIELD NAME: UNDERLINE ON
  LOCATION: 6;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 24                        FIELD NAME: UNDERLINE OFF
  LOCATION: 6;5                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Mental Health package requests permission to read
 some fields in the TERMINAL TYPE (#3.2) file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: UNDERLINE ON
KEYWORDS: UNDERLINE OFF
KEYWORDS: %ZIS(2,
SUBSCRIBING PACKAGE: MENTAL HEALTH
  DATE ACTIVATED: MAR 05, 2012

NUMBER: 5726                            IA #: 5726
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: SEP 16, 2011            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: LSRP ADD X-REF TO NEW PERSON FILE
  ID: VA(200
GLOBAL REFERENCE: ALSRP
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Part of New Style M Cross Reference.  
FIELD NUMBER: .132                      FIELD NAME: OFFICE PHONE
  LOCATION: .13;2                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Part of New Style M Cross Reference.  
FIELD NUMBER: .137                      FIELD NAME: VOICE PAGER
  LOCATION: .13;7                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Part of New Style M Cross Reference.  
FIELD NUMBER: .138                      FIELD NAME: DIGITAL PAGER
  LOCATION: .13;8                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Part of New Style M Cross Reference.  
FIELD NUMBER: 4                         FIELD NAME: SEX
  LOCATION: 1;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Part of New Style M Cross Reference.  
FIELD NUMBER: 5                         FIELD NAME: DOB
  LOCATION: 1;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Part of New Style M Cross Reference.  
FIELD NUMBER: 9                         FIELD NAME: SSN
  LOCATION: 1;9                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Part of New Style M Cross Reference.  
FIELD NUMBER: 41.99                     FIELD NAME: NPI
  LOCATION: NPI;1                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Part of New Style M Cross Reference.  
 GLOBAL DESCRIPTION:   Defines VistA User information.  New Style Cross
 Reference tracking changes to indicated fields.  
GLOBAL REFERENCE: AKLSRP
FIELD NUMBER: 52                        FIELD NAME: DELEGATED KEYS
  LOCATION: 52;0                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Part of Whole-File Cross Reference that monitors KEY
 field (#.01) changes on the DELEGATED KEYS (#52) Multiple.  
 GLOBAL DESCRIPTION:   References Security Keys held by the user associated
 with the respective DUZ record.  New Style Cross Reference tracking changes to
 Security Keys held by user.  
 GENERAL DESCRIPTION:   The Lab System Re-Engineering Project (LSRP) has
 permission to define 2 New Style Cross references on the New Person File
 (#200) with patch LR*5.2*393.  These cross references are added to the New
 Person file as part of the KIDS Post-Installation process of the LR*5.2*393 
 distribution.  These Cross References are installed using the CREIXN^DDMOD
 Fileman API.  
  
 Kernel development grants this "one-time" ICR allowing LSRPs' addition of
 "ALSRP" and "AKLSRP" cross-references to the New Person file (#200) by the
 LR*5.2*393 patch.  
  
  
 New Style Cross references "ALSRP" and "AKLSRP" are described as follows: 
  
 "ALSRP" 
 -------
 "ALSRP" checks for changes to specific fields in the New Person File (#200). 
 When data in a relative field is changed, "ALSRP" SET logic invokes OPKG^XUHUI
 (allowed via ICR #3589) referencing the "LA7J MFN NEW PERSON MOD PRTCL" entry
 in the Protocol file (#101).  
  
  "ALSRP" is defined for the following New Person fields: 
   NAME (#.01) 
   OFFICE PHONE (#.132) 
   VOICE PAGER (#.137) 
   DIGITAL PAGER (#.138) 
   SEX (#4) 
   DOB (#5) 
   SSN (#9) 
   NPI (#41.99) 
  
  
 Data Dictionary Description: 
  
 ALSRP       RECORD    MUMPS        ACTION 
  Short Descr:  LSRP monitoring of New Person Field changes 
  Description:  This M New Style Cross reference will monitor changes to 
                New Person fields that are relevant to the Lab System 
                Re-Engineering Project.  
                      
                User contact and other information on the Cerner Pathnet 
                system must be synchronized with changes made (for Lab 
                users) on VistA.  This cross- reference will invoke code 
                that sends a Master File Notification to Cerner when a 
                change to pertinent data is made.  
                      
                Only users holding either the LRJ CERNER PRA or LRJ CERNER 
                STF security keys will be sent via MFN to Cerner.  
   Set Logic:  D OPKG^XUHUI("101","LA7J MFN NEW PERSON MOD PRTCL","","ALSRP") 
   Kill Logic:  Q 
   Whole Kill:  Q 
  
         X(1):  NAME  (200,.01)  (forwards) 
         X(2):  OFFICE PHONE  (200,.132)  (forwards) 
         X(3):  VOICE PAGER  (200,.137)  (forwards) 
         X(4):  DIGITAL PAGER  (200,.138)  (forwards) 
         X(5):  SEX  (200,4)  (forwards) 
         X(6):  DOB  (200,5)  (forwards) 
         X(7):  SSN  (200,9)  (forwards) 
         X(8):  NPI  (200,41.99)  (forwards) 
  
  
 "AKLSRP" 
 --------
 "AKLSRP" checks changes to the set of New Persons holding specific Security
 Keys and is defined on the New Person file KEYS subfile (#200.051), KEY field
 (#.01).  When KEY allocations and de-allocations occur, "AKLSRP" SET and KILL
 logic invoke OPKG^XUHUI (see ICR #3589) referencing the "LA7J MFN NEW PERSON
 KEY MOD PRTCL" entry in the Protocol file (#101).  
  
  
 Data Dictionary Description: 
  
 Subfile #200.051 
  
 AKLSRP       FIELD    MUMPS        ACTION    WHOLE FILE (#200) 
  Short Descr:  
        This cross reference creates LSRP MFNs when a lab key is added.  
  Description:  The AKLSRP New Style Cross reference will invoke a protocol 
                that checks when a key is added or deleted.  If the 
                affected key is LRJ CERNER PRA or LRJ CERNER STF, then an 
                MFN will be sent to Cerner Pathnet, as necessary.  
   Set Logic:  
        D OPKG^XUHUI("101","LA7J MFN NEW PERSON KEY MOD PRTCL","","AKLSRP") 
  
   Kill Logic: 
        D OPKG^XUHUI("101","LA7J MFN NEW PERSON KEY MOD PRTCL","K","AKLSRP") 
  
         X(1):  KEY  (200.051,.01)  (forwards) 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LSRP
KEYWORDS: NEW PERSON FILE
KEYWORDS: LAB
KEYWORDS: ONE TIME
KEYWORDS: NEW STYLE X-REF
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   The Laboratory System Re-Engineering Project is granted
 this one time ICR by Kernel to add 2 Cross-References to the New Person File
 (#200).  
  DATE ACTIVATED: OCT 27, 2011

NUMBER: 5727                            IA #: 5727
  DATE CREATED: SEP 28, 2011            CUSTODIAL PACKAGE: HEALTH SUMMARY
  USAGE: Private                        TYPE: Routine
  ROUTINE: GMTSMHPE                     NAME: GMTSMHPE
  ID: GMTSMHPE
 GENERAL DESCRIPTION:   The Mental Health package is removing the MEDICAL
 RECORD (#90) file with YS*5.01*60.  
  
 The Health Summary package's MENTAL HEALTH PHYSICAL EXAM component calls 
 MAIN^GMTSMHPE which checks for data in the MEDICAL RECORD (#90) file.  
  
 The Mental Health package requests permission to alter the GMTSMHPE routine
 with YS*5.01*60. We would export a routine named YSTSMHPE that is a copy of
 GMTSMHPE, but with a QUIT at the start of the MAIN entry point.  In our patch
 installation, we will save YSTSMHPE as GMTSMHPE. This would result in the
 MENTAL HEALTH PHYSICAL EXAM component not returning anything. 
  
 In a future Health Summary patch, we request the component be removed.  
  STATUS: Pending                       DURATION: Next Version
  GOOD ONLY FOR VERSION: 5.01
KEYWORDS: YSTSMHPE
KEYWORDS: MENTAL HEALTH PHYSICAL EXAM
COMPONENT/ENTRY POINT: MAIN
SUBSCRIBING PACKAGE: MENTAL HEALTH

NUMBER: 5728                            IA #: 5728
  DATE CREATED: SEP 29, 2011            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSNNGR
  NAME: PSNNGR ROUTINE                  ID: PSNNGR
 GENERAL DESCRIPTION:   This IA provides another entry point (component) for
 Outpatient Pharmacy & Inpatient Medications to use in to store Drug-Allery
 Order Checks. The line tag currently already exists but is not documented as
 an IA. The component requires the developer to pass in PSNDA and PSNID. The
 utility will return all of the primary drug ingredients to an entry in the VA
 Product file (#50.68).  
  
  *******************************************************
  The calling package(s) assumes the responsibily to kill variables 
  (PSNDA,PSNID,J,K,X) and ^TMP("PSN",$J, going in, and when exiting, do the 
  same. 
  *******************************************************
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: INGR
 COMPONENT DESCRIPTION:   Subscribing package(s) will pass in variables PSNDA
 (entry number in VA GENERIC file (#50.6) and PSNID (entry number in VA PRODUCT
 file (#50.68).  The component will return ^TMP("PSN",$J,K)=Primary Drug
 Ingredient (#.01) NAME field. Variable K is the entry number of the Primary
 DRUG INGREDIENT 
  file (#50.416).  
VARIABLES: PSNDA                        TYPE: Input
 VARIABLES DESCRIPTION:   Input = Internal entry number in VA GENERIC file
 (#50.6).  
VARIABLES: PSNID                        TYPE: Input
 VARIABLES DESCRIPTION:   Input = Internal entry number in VA PRODUCT file
 (#50.68).  
VARIABLES: K                            TYPE: Output
 VARIABLES DESCRIPTION:   Output = Internal entry number in DRUG INGREDIENTS
 file (#50.416).  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: OCT 03, 2011

NUMBER: 5729                            IA #: 5729
  DATE CREATED: OCT 03, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: OROCAPI1
  NAME: ORDER CHECK INSTANCES API       ID: OROCAPI1
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to save data into and retrieve data from the ORDER CHECK INSTANCES file
 (#100.05).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SAVEOC(ORL,RET)
 COMPONENT DESCRIPTION:   Create one or more new entries.  
VARIABLES: ORL                          TYPE: Input
 VARIABLES DESCRIPTION:   Array of new entries to create.  
  
 Data Format: 
   NOTE: Unless specified otherwise, pass in all 
         fields in internal format.  
  
 ORL(COUNT,1)=Caret-delimited string 
   COUNT - number that starts at one and increments 
           by one for each subsequent new entry 
   Caret-delimited string: 
    Piece   Stored in Field 
   ==================================================
    1       ORDER (#.01) 
    2       OCCURRENCE (#2) 
    3       USER (#3) 
    4       OCCURRENCE DATE/TIME (#4) 
    5       ORDER CHECK (#5) 
    6       CLINICAL DANGER LEVEL (#6) (optional) 
  
 ORL(COUNT,2) 
   Nodes descendant from this node are stored in 
   the ORDER CHECK MESSAGE field (#8).  
   COUNT - number that starts at one and increments 
           by one for each subsequent new entry 
   Descendant nodes are FileMan word-processing 
   field type compatible.  Refer to FileMan 
   documentation for WP^DIE for details on how to 
   structure the descendant nodes.  
  
 ORL(COUNT,3)=TEXT 
   COUNT - number that starts at one and increments 
           by one for each subsequent new entry 
   TEXT - stored in the OVERRIDE REASON (#7) field 
VARIABLES: RET                          TYPE: Input
 VARIABLES DESCRIPTION:   A reference to the array in which to return the new
 entries' internal entry number (IEN).  
  
 Data Format: 
  RET(COUNT,IEN)="" 
    COUNT - corresponds to the COUNT node in the 
            ORL input parameter (the IEN is for 
            the ORL(COUNT) entry).  
    IEN - IEN of the new entry 
VARIABLES: TMP GLOBAL                   TYPE: Input
 VARIABLES DESCRIPTION:   Nodes descendant from ^TMP("OROCIDATA",$J,CRC16) are
 stored (optional).  
  
 Data Format: 
  NOTE: Unless specified otherwise, pass in all 
        fields in internal format.  
  $J - ID number of the current process 
  CRC16 - Cyclic Redundancy Code (CRC) of the order 
          check message. Use integration control 
          registration #3156 XLFCRC to compute this 
          node.  
  
 ^TMP("OROCIDATA",$J,CRC16,100.05,84)=DATABASE 
                                      field (#84) 
  
 ^TMP("OROCIDATA",$J,CRC16,100.517,COUNT,FIELD)=VALUE 
   COUNT - number that starts at one and increments 
           by one for each subsequent new entry in 
           the DRUG ALLERGIES field (#17) 
   FIELD - number of the field to store data in.  
           Refer to the ^ORD(100.05,D0,4,D1 global 
           reference section in integration control 
           registration #5731 ORDER CHECK INSTANCES 
           FILE - DRUG ALLERGIES for valid field 
           numbers.  
   VALUE - the data to store 
  
 ^TMP("OROCIDATA",$J,CRC16,"CLASS",COUNT,EIEN)=DATA 
   COUNT - corresponds to the COUNT node in the 
           ^TMP("OROCIDATA",$J,CRC16,100.517,COUNT, 
           FIELD) input parameter.  
   EIEN - a plus-sign character followed by a 
          number that starts at two and increments 
          by one followed by a comma.  
          NOTE: The number must be unique across 
                the "CLASS", "INGREDIENT", and 
                "SIGN" nodes. There cannot be a 
                "+2," value for "CLASS", 
                "INGREDIENT", and "SIGN".  
   DATA - VA DRUG CLASS sub-field (#.01) in the VA 
          DRUG CLASSES sub-field (#3) 
  
 ^TMP("OROCIDATA",$J,CRC16,"INGREDIENT",COUNT,EIEN 
                                             )=DATA 
   COUNT - corresponds to the COUNT node in the 
           ^TMP("OROCIDATA",$J,CRC16,100.517,COUNT, 
           FIELD) input parameter.  
   EIEN - a plus-sign character followed by a 
          number that starts at two and 
          increments by one followed by a comma.  
          NOTE: The number must be unique across 
                the "CLASS", "INGREDIENT", and 
                "SIGN" nodes. There cannot be a 
                "+2," value for "CLASS", 
                "INGREDIENT", and "SIGN".  
   DATA - DRUG INGREDIENT sub-field (#.01) in the 
          DRUG INGREDIENTS sub-field (#4) 
  
 ^TMP("OROCIDATA",$J,CRC16,"SIGN",COUNT,EIEN)=DATA 
   COUNT - corresponds to the COUNT node in the 
           ^TMP("OROCIDATA",$J,CRC16,100.517,COUNT, 
            FIELD) input parameter.  
   EIEN - a plus-sign character followed by a 
          number that starts at two and 
          increments by one followed by a comma.  
          NOTE: The number must be unique across 
                the "CLASS", "INGREDIENT", and 
                "SIGN" nodes. There cannot be a 
                "+2," value for "CLASS", 
                "INGREDIENT", and "SIGN".         
   DATA - SIGN/SYMPTOM sub-field (#.01) in the 
          SIGNS/SYMPTOMS sub-field (#5) 
COMPONENT/ENTRY POINT: GETOC1(IEN,RET)
 COMPONENT DESCRIPTION:   Return data for a specific order check instance.  
VARIABLES:  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the entry in the ORDER CHECK INSTANCES file
 (#100.05) to return data for.  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   A reference to the array in which to return the
 entry's data.  
  
 Data Format: 
  RET(IEN,0)=Value of ^OR(100.05,IEN,0) 
  
  RET(IEN,1)=Value of ^OR(100.05,IEN,1) 
    NOTE: The first caret piece is a semi-colon 
          delimited string. The first semi-colon 
          piece is the external format of the 
          first caret piece of ^OR(100.05,IEN,1).  
          The second semi-colon piece is the 
          first caret piece of ^OR(100.05,IEN,1) 
          (internal format).  
  
  RET(IEN,"OC") 
   Nodes descendant from this node are from the 
   ORDER CHECK MESSAGE field (#8).  
  
  RET(IEN,"OR") 
   Nodes descendant from this node are from the 
   OVERRIDE REASON field (#7).  
  
  RET(IEN,"OI",OIEN,0)=Caret delimited string 
   OIEN - number that starts at one and increments 
          by one for each subsequent orderable item 
   Caret delimited string: 
    Piece   Value 
   ==================================================
    1       NAME field (#.01) in the ORDERABLE 
            ITEMS file (#101.43) 
    2       ID field (#2) in the ORDERABLE ITEMS 
            file (#101.43) 
COMPONENT/ENTRY POINT: GETOC2(ORD,RET)
 COMPONENT DESCRIPTION:   Return all ORDER CHECK INSTANCES file IENs for a
 specific entry in the ORDERS file (#100).  
VARIABLES: ORD                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in the ORDERS file (#100).  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   A reference to the array in which to return the data. 
  
 Data Format: 
  RET(ORD,IEN)="" 
    ORD - corresponds to the ORD input parameter 
    IEN - IEN of the ORDER CHECK INSTANCES file 
          entry 
COMPONENT/ENTRY POINT: GETOC3(ORD,OCC,RET)
 COMPONENT DESCRIPTION:   Return all ORDER CHECK INSTANCES file IENs for a
 specific order/occurrence pair.  
VARIABLES: ORD                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in the ORDERS file (#100).  
VARIABLES: OCC                          TYPE: Input
 VARIABLES DESCRIPTION:   OCCURRENCE field (#2) value.  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   A reference to the array in which to return the data. 
  
 Data Format: 
  RET(ORD,IEN)="" 
    ORD - corresponds to the ORD input parameter 
    IEN - IEN of the ORDER CHECK INSTANCES file 
          entry 
COMPONENT/ENTRY POINT: GETOC4(ORD,RET)
 COMPONENT DESCRIPTION:   Return data for all order check instances for a
 specific entry in the ORDERS file (#100).  
VARIABLES: ORD                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in the ORDERS file (#100).  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   A reference to the array in which to return data.  
  
 Data Format: 
  RET(ORD,IEN)="" 
    ORD - corresponds to the ORD input parameter 
    IEN - IEN of the ORDER CHECK INSTANCES file 
          entry 
  
  RET(ORD,IEN,"DATA") 
    Nodes descendant from this node are the same 
    nodes that are descendant from the RET(IEN) 
    array returned by the GETOC1(IEN,RET) 
    component.  
COMPONENT/ENTRY POINT: GETOC5(ORD,OCC,RET)
 COMPONENT DESCRIPTION:   Return data for all order check instances for a
 specific order/occurrence pair.  
VARIABLES: ORD                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in the ORDERS file (#100).  
VARIABLES: OCC                          TYPE: Input
 VARIABLES DESCRIPTION:   OCCURRENCE field (#2) value.  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   A reference to the array in which to return data.  
  
 Data Format: 
  RET(ORD,IEN)="" 
    ORD - corresponds to the ORD input parameter 
    IEN - IEN of the ORDER CHECK INSTANCES file 
          entry 
  
  RET(ORD,IEN,"DATA") 
    Nodes descendant from this node are the same 
    nodes that are descendant from the RET(IEN) 
    array returned by the GETOC1(IEN,RET) 
    component.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: JUL 28, 2016

NUMBER: 5730                            IA #: 5730
  DATE CREATED: OCT 05, 2011            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGGSIU4
  NAME: MAG RESCIND IMAGES              ID: MAGGSIU4
 GENERAL DESCRIPTION:   This ICR will allow the TIU Package to set a Queue so
 that Images attached to a Rescinded Advance Directive will be Watermarked with 
 the word 'RESCINDED'.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RESCIND
KEYWORDS: ADVANCE DIRECTIVE
COMPONENT/ENTRY POINT: RESCIND(MAGRY,TIUDA)
 COMPONENT DESCRIPTION:   This is the entry point for TIU to call.  It will
 start the process of queuing a job with the Imaging Background Processor to
 Watermark all images associated with the Advanced Directive that is being
 Rescinded.  
VARIABLES: MAGRY                        TYPE: Both
 VARIABLES DESCRIPTION:   MAGRY is the Result Array 
  
 if error found during execution 
    MAGRY(0) = 0^Error message 
    MAGRU(1..N) = messages describing the Error.  
  
 if success 
    MAGRY(0) = 1^Success 
  
 for each image queued we have 3 lines of info.  
    MAGRY(x)   = Image(1..n): Tracking ID: TRKID 
    MAGRY(x+1) = Image(1..n): Queue: QUENUMBER 
    MAGRY(x+2) = Image(1..n): Image: MAGDA 
  
 if First image success, and subsequent image 
    problem we Return 
    MAGRY(0) =  2^Warning message 
  
 for each successfully Queued image queued we 
    have 3 lines info, same as above. 
  
 For any image that was a problem deleting 
    (unlikely) we have MAGDA and error messages. 
  
 The Image is changed to status of "Needs Review", 
    so it is blocked from view. 
  
 information of the image is in the format 
    MAGRY(x) = Image(n): Image: MAGDA 
    where x is the incremental count of lines in 
    the results array and n is the nth image 
    in this session. 
  
 MAGDA is the internal entry number for the image in the File : IMAGE (#2005) 
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   TIUDA = IEN of TIU note in TIU DOCUMENT file (#8925) 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   TIU Package will call the RESCIND^MAGGSIU4 API when an
 Advance Directive is being Rescinded and has images attached.  
  DATE ACTIVATED: OCT 14, 2011

NUMBER: 5731                            IA #: 5731
  FILE NUMBER: 100.05                   GLOBAL ROOT: ORD(100.05,
  DATE CREATED: OCT 12, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ORDER CHECK INSTANCES FILE - DRUG ALLERGIES
  ID: ORD(100.05,
GLOBAL REFERENCE: ORD(100.05,D0,4,D1
FIELD NUMBER: .01                       FIELD NAME: REACTANT
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   The name of the agent that caused this drug allergy.  
FIELD NUMBER: 2                         FIELD NAME: CAUSATIVE AGENT
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   The agent that caused this drug allergy.  
FIELD NUMBER: 3                         FIELD NAME: VA DRUG CLASSES
  LOCATION: 1;0                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   These are the drug classes associated with this drug
 allergy.  
FIELD NUMBER: 4                         FIELD NAME: DRUG INGREDIENTS
  LOCATION: 2;0                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   These are the drug ingredients associated with this drug
 allergy.  
FIELD NUMBER: 5                         FIELD NAME: SIGNS/SYMPTOMS
  LOCATION: 3;0                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   These are the signs and symptoms of the drug allergy.  
FIELD NUMBER: 6                         FIELD NAME: LOCATION TYPE
  LOCATION: 0;3                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   The location type where this drug allergy was entered.  
FIELD NUMBER: 7                         FIELD NAME: REMOTE LOCATION
  LOCATION: 0;4                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   If the drug allergy was reported at a non-local
 institution, this field will identify that institution. For drug allergies
 that were reported in this system's institution, this field will be blank.  
FIELD NUMBER: 8                         FIELD NAME: ORIGINATION DATE/TIME
  LOCATION: 0;5                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Date/time the drug allergy was entered into the system.  
FIELD NUMBER: 9                         FIELD NAME: OBSERVED/HISTORICAL
  LOCATION: 0;6                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Indicates whether this drug allergy was observed by VA
 personnel, or if it is historical data gathered about the patient.  
FIELD NUMBER: 10                        FIELD NAME: SEVERITY
  LOCATION: 0;7                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This field indicates the severity of this drug allergy.  
GLOBAL REFERENCE: ORD(100.05,D0,4,D1,1,D2
FIELD NUMBER: .01                       FIELD NAME: VA DRUG CLASS
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   The VA drug class associated with the drug allergy.  
GLOBAL REFERENCE: ORD(100.05,D0,4,D1,2,D2
FIELD NUMBER: .01                       FIELD NAME: DRUG INGREDIENT
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is the drug ingredient associated with the drug
 allergy.  
GLOBAL REFERENCE: ORD(100.05,D0,4,D1,3,D2
FIELD NUMBER: .01                       FIELD NAME: SIGN/SYMPTOM
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is a sign or symptom of the drug allergy.  
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to read and write to those fields stored in the DRUG ALLERGIES multiple field
 (#17).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORDER CHECKS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: OCT 12, 2011

NUMBER: 5732                            IA #: 5732
  DATE CREATED: OCT 17, 2011            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLEMU
  NAME: HLEMEU APIs                     ID: HLEMU
 GENERAL DESCRIPTION:   The use of the HL7 API MSGIEN^HLEMU(message id) is
 allowed per the description documented with this Integration Control
 Registration.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MESSAGE ID
KEYWORDS: 773
KEYWORDS: 773 IEN
KEYWORDS: HL7 IEN
COMPONENT/ENTRY POINT: MSGIEN
 COMPONENT DESCRIPTION:   This function receives a HL7 MESSAGE ID and returns
 the respective IEN from the ^HLMA(773) file.  
VARIABLES: MSGID                        TYPE: Input
 VARIABLES DESCRIPTION:   HL7 MESSAGE ID for a HL7 message defined on the local
 instance of VistA.  
VARIABLES: IEN                          TYPE: Output
 VARIABLES DESCRIPTION:   An IEN from the ^HLMA(773) file.  
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   Lab Service is allowed to reference this API to
 retrieve the HL7 ien when the HL7 MESSAGE ID is known.  
  DATE ACTIVATED: OCT 27, 2011

NUMBER: 5733                            IA #: 5733
  DATE CREATED: OCT 17, 2011            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOMSG1
  NAME: HLOMSG1 APIs                    ID: HLOMSG1
 GENERAL DESCRIPTION:   The use of the HL7 API FINDMSG^HLOMSG1(message id,list)
 is allowed per the description documented with this Integration Control
 Registration.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HLMSG1
KEYWORDS: FNDMSG
KEYWORDS: HLO
KEYWORDS: HLB 778
KEYWORDS: 778
COMPONENT/ENTRY POINT: FINDMSG
 COMPONENT DESCRIPTION:   Given a message id, this function finds the file 778
 entries having that message ID.  The number of entries with that message id is
 returned as the function result.  The "list" variable is a reference parameter
 received from the calling application and is returned as an array with each
 node equal to an IEN in the ^HLB(778) file that has the received 'message id'. 
 
VARIABLES: MSGID                        TYPE: Input
 VARIABLES DESCRIPTION:   The HLO Message ID defined for the message on the
 local VistA HL7 system.  
VARIABLES: LIST                         TYPE: Both
 VARIABLES DESCRIPTION:   Array root received from the Calling application as a
 "reference" parameter.  It is returned with each node (1,2,3...) equal to an
 IEN with an associated entry in the ^HLB(778) file.  
VARIABLES: COUNT                        TYPE: Output
 VARIABLES DESCRIPTION:   The result returned upon completion of the function. 
 This the number of entries in the ^HLB(778) file that have the received
 'message id' (MSGID).  
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   Lab Service is allowed to reference this API to
 retrieve the HL7 ien in the HLO system when the HL7 MESSAGE ID is known.  
  DATE ACTIVATED: OCT 27, 2011

NUMBER: 5734                            IA #: 5734
  DATE CREATED: OCT 17, 2011            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ SAVE
  REMOTE PROCEDURE: YTQ SAVE
 GENERAL DESCRIPTION:   This RPC can be used to add or edit a Mental Health
 file entry. The subscripted YS array is passed to the RPC containing all of
 the values needed to create or update the entry.  
   
  Input: YS("FILEN")=File Number (e.g., the file # for administrations 
                     would be 601.84) 
           YS("IEN")=the internal number of the record you want to edit.  
                     Leave blank if creating a new record. If creating a 
                     new record you must send ".01^NEW" for those MH files 
                     using the New input transform.  
               YS(1)=FIELD #^Value^[3rd piece is 1 if you need to bypass 
                     validation (use only if approved by developer) 
               YS(n)=FIELD #^Value^[3rd piece] 
   
  Output:  YSDATA(1)=[DATA] or [ERROR] 
           YSDATA(2)=error message 
  
 Example: Adding a new entry to the MH ADMINISTRATION (#601.84) file.  
  
  S YS(1)=".01^NEW^1" 
  S YS(2)="1^`134" 
  S YS(3)="2^5" 
  S YS(4)="3^3111017.0945" 
  S YS(5)="4^NOW" 
  S YS(6)="5^`547" 
  S YS(7)="6^`547" 
  S YS(8)="7^NO" 
  S YS(9)="8^NO" 
  S YS(10)="9^0" 
  S YS(11)="13^`87" 
  S YS("FILEN")=601.84 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BHL
KEYWORDS: BEHAVIORAL HEALTH LAB
KEYWORDS: CAPITAL SOLUTION DESIGN
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   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 which explains why
 the Mental Health package is both the custodian and as well as the subscriber
 to this ICR.  
SUBSCRIBING PACKAGE: MOBILE MHPRO
  DATE ACTIVATED: MAY 16, 2013

NUMBER: 5735                            IA #: 5735
  DATE CREATED: OCT 17, 2011            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ SET ANSWER ALL
  REMOTE PROCEDURE: YTQ SET ANSWER ALL
 GENERAL DESCRIPTION:   This RPC saves all answers for an administration to the
 MH ANSWERS (#601.85) file.  
  
  Input: YS("AD")=internal entry number of the MH ADMINISTRATION (#601.84) 
                  entry 
            YS(n)=File 601.72 IEN^File 601.75 IEN 
         YS(n,n1)=text 
  where n and n1 are integers starting at 1.  
  
 The YS(n) array identifies the questions and responses for the administration.
 The first piece of every YS(n) should be a pointer to an entry in the MH
 QUESTIONS (#601.72) file. In most cases, the second piece will be a pointer to
 an entry in the MH CHOICES (#601.75) file. If the response to the question is
 not in FILE 601.75, the second piece is null and the YS(n,n1) value should be
 defined with the text of the response. 
  
  Output: YSDATA(1)=[DATA] 
          YSDATA(2)=number of answers^OK 
          or 
          YSDATA(1)=[ERROR] 
          YSDATA(2)=error message 
  
 The release of patch YS*5.01.123 changes the routine name called by the RPC. 
 The routine before patch YS*5.01*123 is  YTQAPI17, and the routine after the
 patch isYTQAPI21.  Input, output and tag name are not changed with this patch. 
 The above changes are dependent upon the release of CPRS v31A.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BHL
KEYWORDS: BEHAVIORAL HEALTH LAB
KEYWORDS: CAPITAL SOLUTION DESIGN
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   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 which explains why
 the Mental Health package is both the custodian and as well as the subscriber
 to this ICR.  
SUBSCRIBING PACKAGE: MOBILE MHPRO
  DATE ACTIVATED: MAY 16, 2013

NUMBER: 5736                            IA #: 5736
  DATE CREATED: OCT 18, 2011
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA5736
  STATUS: Pending

NUMBER: 5737                            IA #: 5737
  DATE CREATED: OCT 18, 2011
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSDIUTL
  NAME: CHECK DRUG INTERACTIONS UTILITY
  ID: PSSDIUTL
 GENERAL DESCRIPTION:   This utility routine is called to determine what Drug
 Interactions exist for Inpatient and Outpatient Pharmacy.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSSDIUTL
COMPONENT/ENTRY POINT: CHKFDB
 COMPONENT DESCRIPTION:   Inpatient Medications and Outpatient Pharmacy
 applications call PSSDIUTL at the top of the routine.  A return value of -1
 means the FDB database is down and 0 indicates it is up and running.  
COMPONENT/ENTRY POINT: PROC
 COMPONENT DESCRIPTION:   Variable PSODGCK is defined when the Pharmacy
 application is running the DX option.  PROC is not executed if application is
 not running DX option.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: OCT 24, 2014

NUMBER: 5738                            IA #: 5738
  DATE CREATED: OCT 25, 2011
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA5738
  STATUS: Pending

NUMBER: 5739                            IA #: 5739
  FILE NUMBER: 161.01                   GLOBAL ROOT: FBAAA
  DATE CREATED: OCT 25, 2011
  CUSTODIAL PACKAGE: NATIONAL HEALTH INFO NETWORK
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: NHIND79C
  NAME: NwHIN DIRECT 7079 GUI TRIGGER   ID: NHIND79C
 GENERAL DESCRIPTION:   To facilitate the sending of Fee Basis and related data
 which populate the Treatment Authorization Form 7079 to VA contracted vendors, 
 triggers are created on a number of fields of the Fee Basis Patient File 
 #161.01.  When triggered by Fee Basis, the NwHIN routine PUSH^NHIND79C sends
 Fee Basis and related data in XML format to NwHIN Direct via the HeatheVet Web
 Service.  
    
    The Fee Basis fields upon which a trigger are placed include: 
    
         FROM DATE - 161.01,.01 Field 
         PRINT AUTHORIZATION (Y/N) - 161.01,1 Field 
         TO DATE - 161.01,.02 Field 
         VENDOR - 161.01,.04 Field 
         PATIENT TYPE CODE - 161.01,.065 Field 
         PURPOSE OF VISIT CODE - 161.01,.07 Field 
         DIAGNOSIS LINE 1 - 161.01,.08 Field 
         DIAGNOSIS LINE 2 - 161.01,.085 Field 
         DIAGNOSIS LINE 3 - 161.01,.086 Field 
         TREATMENT TYPE CODE - 161.01,.095 Field 
         ACCIDENT RELATED (Y/N) - 161.01,.096 Field 
         POTENTIAL COST RECOVERY CASE - 161.01,.097 Field 
         TYPE OF CARE - 161.01,2 Field 
         CLERK - 161.01,100 Field 
         PRIMARY SERVICE AREA - 161.01,101 Field 
         REFERRING PROVIDER - 161.01,104 Field 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NwHIN
KEYWORDS: PRINT AUTHORIZATION
COMPONENT/ENTRY POINT: PUSH
 COMPONENT DESCRIPTION:   Input:  DA - (required) Patient DFN (File 161 IEN) 
         DA(1) - (required) Authorization IEN (sub-file 161.01) 
         DSIFARR - (optional) $D(DSIFARR) is used to 
                   distinguish between entry by VistA 
                   (roll & scroll) and entry by the FBCS GUI.  
  
 Output: None (ZTSAVE array used prior to the quit) 
SUBSCRIBING PACKAGE: FEE BASIS
  DATE ACTIVATED: MAR 29, 2012

NUMBER: 5740                            IA #: 5740
  DATE CREATED: OCT 31, 2011            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOFDAUT
  NAME: PSOFDAUT                        ID: PSOFDAUT
 GENERAL DESCRIPTION:   This Outpatient Pharmacy utility routine contains APIs
 related to the printing of FDA Medication Guides.  
  STATUS: Active
KEYWORDS: MED GUIDE
KEYWORDS: MEDICATION GUIDE
KEYWORDS: FDA MED GUIDE
KEYWORDS: PSOFDAUT
COMPONENT/ENTRY POINT: $$MGONFILE(RXIEN)
 COMPONENT DESCRIPTION:   This API returns whether there is an FDA Medication
 Guide available for a specific prescription or not.  
VARIABLES: RXIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTION file (#52).  
VARIABLES: $$MGONFILE                   TYPE: Output
 VARIABLES DESCRIPTION:   There are two possible outputs from this API: 
  
   0 - No FDA Medication Guide on file for the prescription.  
   1^<FDA Medication Guide file name> - The first piece indicates that there is
 an FDA Medication Guide for the prescription and the second piece is the
 actual document filename (e.g., "1^Citalopram_Tab_Soln_(Celexa)_(2011).pdf").  
COMPONENT/ENTRY POINT: SELPRT(DEFAULT)
 COMPONENT DESCRIPTION:   This entry point provides a user-interface for
 selecting a valid FDA Medication Guide Printer.  
VARIABLES: DEFAULT                      TYPE: Input
 VARIABLES DESCRIPTION:   Default printer name (optional). The value in this
 parameter will be displayed as the default value for the FDA Medication Guide
 Printer. In case a value is not supplied the division's default printer will
 be given as the default value. If the division does not have a default FDA
 Medication Guide printer, the HOME device will be the default.  
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: MAR 07, 2012

NUMBER: 5741                            IA #: 5741
  FILE NUMBER: 773                      GLOBAL ROOT: HLMA(
  DATE CREATED: OCT 31, 2011            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Message Status Data Retrieval from 773
  ID: HLMA(
GLOBAL REFERENCE: NODE 0
FIELD NUMBER: 2                         FIELD NAME: MESSAGE ID
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   A unique identifier associated with the message.  
  
FIELD NUMBER: 3                         FIELD NAME: TRANSMISSION TYPE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Type of Tranmission : Incoming or Outgoing.  
  
 GLOBAL DESCRIPTION:   
  
 This node contains basic message transmission information.  
  
GLOBAL REFERENCE: NODE P
FIELD NUMBER: 20                        FIELD NAME: STATUS
  LOCATION: P;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Status currently assigned to the message.  
  
FIELD NUMBER: 22                        FIELD NAME: ERROR MESSAGE
  LOCATION: P;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains any error message that may have
 resulted from sending or receiving the HLMA message entry.  
  
FIELD NUMBER: 23                        FIELD NAME: ERROR TYPE
  LOCATION: P;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field references a description of the type of error
 that may have occured.  
  
 GLOBAL DESCRIPTION:   
  
 This node contains message transmission status information.  
  
GLOBAL REFERENCE: NODE S
FIELD NUMBER: 100                       FIELD NAME: LAST DATE/TIME UPDATED
  LOCATION: S;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Outgoing message: 
   1. Date/time of its commit ACK received.  
   2. Date/time of its application ACK message received 
       (overwriting #1 - Commit Ack).  
  
 Incoming message: 
   1. Date/time of the message received.  
   2. Date/time of the message has been processed by the application 
       (overwriting #1 - Rcpt dt/tm) 
  
 GLOBAL DESCRIPTION:   
  
 This node contains transmission date/time stamps.  
  
 GENERAL DESCRIPTION:   
  
 The HL7 MESSAGE ADMINISTRATION file (#773) defines and maintains unique 
 message IDs.  It conains information related to the respective message such as
 Statuses and date/times.  
  
 LSRP has permission to retrieve message status information from the HL7 1.6 
 data structures.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 773
KEYWORDS: HLMA(
KEYWORDS: MESSAGE STATUS
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   
  
 LSRP has permission to retrieve the following fields from the HL7 file #773 
 with supported FileMan API tools: 
  MESSAGE ID 
  TRANSMISSION TYPE 
  STATUS 
  ERROR MESSAGE 
  ERROR TYPE 
  LAST DATE/TIME UPDATED 
  
  
  DATE ACTIVATED: DEC 07, 2011

NUMBER: 5742                            IA #: 5742
  FILE NUMBER: 778                      GLOBAL ROOT: HLB(
  DATE CREATED: OCT 31, 2011            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Message Status Data Retrieval from 778
  ID: HLB(
GLOBAL REFERENCE: NODE 0
FIELD NUMBER: .01                       FIELD NAME: MESSAGE ID
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Unique message Identifier for HLO message entry.  
  
FIELD NUMBER: .04                       FIELD NAME: DIRECTION
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Indicates if the message was incoming or outgoing.  
  
FIELD NUMBER: .07
  FIELD NAME: APPLICATION ACKNOWLEDGMENT BY
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Control (message) ID for application response to this
 message.  
  
FIELD NUMBER: .16                       FIELD NAME: TRANSMISSION DATE/TIME
  LOCATION: 0;16                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Date/Time the message was either received or sent.  
  
FIELD NUMBER: .2                        FIELD NAME: COMPLETION STATUS
  LOCATION: 0;20                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field indicates the final status of the message.  
  
FIELD NUMBER: .21                       FIELD NAME: ERROR TEXT
  LOCATION: 0;21                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Used to document errors that prevent transmission.  
  
 GLOBAL DESCRIPTION:   
  
 This global records HL7 messages received or transmitted through HLO.  
  
 GENERAL DESCRIPTION:   
  
 The HLO MESSAGES file (#778) records each message sent or received via HLO. 
 It conains information related to the respective message such as Statuses and
 date/times.  
  
 LSRP has permission to retrieve message status information from the HLO data
 structures.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 778
KEYWORDS: HLB(
KEYWORDS: MESSAGE STATUS
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   
  
 LSRP has permission to retrieve the following fields from the HLO file #778 
 with supported FileMan API tools: 
  MESSAGE ID 
  COMPLETION STATUS 
  DIRECTION 
  APPLICATION ACKNOWLEDGED BY 
  TRANSMISSION DATE/TIME 
  ERROR TEXT 
  
  
  DATE ACTIVATED: DEC 07, 2011

NUMBER: 5743                            IA #: 5743
  DATE CREATED: NOV 02, 2011            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBAAV2                       NAME: FBAAV2 HL7NAME FOR FBCS (DSS)
  ID: FBAAV2
 GENERAL DESCRIPTION:   FBCS is requesting access to HL7NAME^FBAAV2 in support
 of the new 35 character requirement for the name field when transmitting data
 to Central Fee.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: HL7NAME
KEYWORDS: FBAAV2
COMPONENT/ENTRY POINT: HL7NAME
VARIABLES: FBDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of file 2 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM

NUMBER: 5744                            IA #: 5744
  DATE CREATED: NOV 02, 2011            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBUTL7
  NAME: FBCS USAGE OF CONTRACT API'S IN FBUTL7
  ID: FBUTL7
 GENERAL DESCRIPTION:   FBCS requests to be allowed to use the following two
 contract related API's in FBUTL7 
  
 1. VCNTR^FBUTL7 2. EDCNTRA^FBUTL7 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBUTL7
KEYWORDS: CONTRACT
KEYWORDS: FBCS
COMPONENT/ENTRY POINT: $$EDCNTRA(DFN,FBAUTH)
 COMPONENT DESCRIPTION:   Determine if contract is editable 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: FBAUTH                       TYPE: Input
 VARIABLES DESCRIPTION:   Authorization IEN 
VARIABLES: value                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns flag^message  where flag = 0 or 1. Flag will
 =1 if contract field in sub-file 161.01 can be edited Where message is
 optional text that if present should be displayed 
COMPONENT/ENTRY POINT: $$VCNTR(FBV,FBC)
 COMPONENT DESCRIPTION:   Verify that vendor is applicable for the contract.  
VARIABLES: FBV                          TYPE: Input
 VARIABLES DESCRIPTION:   Vendor IEN 
VARIABLES: FBC                          TYPE: Input
 VARIABLES DESCRIPTION:   Contract IEN 
VARIABLES: value                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 or 0 =1 if vendor is applicable for the
 contract 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: NOV 04, 2011

NUMBER: 5745                            IA #: 5745
  DATE CREATED: NOV 02, 2011            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBUTL8                       NAME: FBCS REQUEST TO USE FBUTL8
  ID: FBUTL8
 GENERAL DESCRIPTION:   FBCS request to use API FILERP^FBUTL8 to file the Line
 item provider into the invoice file.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBUTL8
KEYWORDS: FBCS
KEYWORDS: LINE ITEM PROVIDER
COMPONENT/ENTRY POINT: FILERP
 COMPONENT DESCRIPTION:   File the Line item provider into the invoice file.  
VARIABLES: FBIENS                       TYPE: Input
 VARIABLES DESCRIPTION:   IENs for the record number to add the Line Item
 provider information to.  
VARIABLES: FBPROV                       TYPE: Input
 VARIABLES DESCRIPTION:   Line item provider information to file.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: NOV 04, 2011

NUMBER: 5746                            IA #: 5746
  DATE CREATED: NOV 04, 2011            CUSTODIAL PACKAGE: 1
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: USE SCREENMAN DDS VARIABLE
 GENERAL DESCRIPTION:   The ScreenMan documentation recommends that
 applications use $D(DDS) to determine if their code is being executed from
 within a ScreenMan form. Reading the contents of ScreenMan's DDS variable
 allows application developers to determine the ScreenMan form their code is
 being invoked from. The format of DDS is formIEN^formName. This ICR allows
 reading of DDS variable.  
  
 In order for an application to integrate and simultaneously use the Browser,
 List Manager, and ScreenMan the application must be able to manipulate the DDS
 variable. If List Manager is invoked from ScreenMan List Manager prompts will
 not display correctly because ^DIR works differently when DDS is defined.
 Therefore the application must save DDS and kill it before calling List
 Manager and restore it when returning from List Manager to ScreenMan. If the
 Browser is invoked from List Manager and DDS is not defined because of the
 above situation then the Browser will kill on exit some of variables needed by
 ScreenMan. Therefore the application needs to temporarily set DDS=1 before
 invoking the Browser.  
  
 In summary, this ICR allows the application to read, kill, set, and NEW the
 DDS variable.  
  
 Note that if List Manager is being invoked from ScreenMan the following Kernel
 calls should be made to restore the terminal settings required by ScreenMan
 before calling REFRESH^DDSUTL.  
  
 N IOAWMO,X         S X=0 X ^%ZOSF("RM"),^%ZOSF("TYPE-AHEAD") S X="IOAWM0" D
 ENDR^%ZISS W IOAWM0 
  
 If this is not done the ScreenMan display will be corrupted.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SCREENMAN
KEYWORDS: DDS VARIABLE
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 5/28/24 for historical use of $D(DDS), documented
 effective with PX*1.0*214 
  DATE ACTIVATED: MAR 20, 2012

NUMBER: 5747                            IA #: 5747
  DATE CREATED: NOV 06, 2011            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ICDEX
  NAME: ICD Data Extraction             ID: ICDEX
 GENERAL DESCRIPTION:   Application Programmer Interfaces (APIs) in this
 routine were developed to remove the need for direct global access to either
 the DIAGNOSIS file 80 or OPERATIONS/PROCEDURE file 80.1.  
  
 These entry points are meant to replace the following active/retired ICRs: 
       
      48  Private       YS File 80.2        Weight (2) 
     280  Private       HBH File 80         Code (.01) 
     365  Private       QAM File 80         Code (.01) 
     368  Private       IB File 80          Retired Nov 15, 2008 
     369  Private       IB File 80.1        Retired Nov 15, 2008 
     370  Private       IB/DSS 80.2         DRG Name (.01) 
     582  Private       IMR File 80         Code (.01) 
     647  Private       IB File 80          Retired Nov 15, 2008 
    1161  Private       VAM File 80         Retired Nov 15, 2008 
    1275  Private       GMTS File 80        Retired Nov 15, 2008 
    1276  Private       GMTS File 80.1      Retired Nov 15, 2008 
    1294  Subscription  PCE/TIU/OR File 80  Retired Nov 15, 2008 
    1487  Private       ACKQ File 80        Retired Nov 15, 2008 
    1586  Subscription  AICS/PCE File 80.3  MDC Name (.01) 
    2435  Private       PXRM File 80 Hdr    ^ICD9(0) 
    2436  Private       PXRM File 80.1 Hdr  ^ICD0(0) 
    3990  Supported     Routine ICDCODE     To be retired Apr 2016 
    3991  Supported     Routine ICDAPIU     To be retired Apr 2016 
    4052  Supported     Routine ICDGTDRG 
    5028  Subscription  GMPL File 80    
    5388  Supported     File 80             Code (.01), AB/BA/D/AST/ACT 
                                            To be retired Apr 2016 
    5404  Supported     File 80.1           Code (.01), BA/ACT 
                                            To be retired Apr 2016 
    5699  Supported     Routine ICDXCODE    To be retired Apr 2016 
    5757  Supported     Routine ICDSAPI     To be retired Apr 2016 
   10082  Supported     File 80             Retired Nov 15, 2008 
   10083  Supported     File 80.1           Retired Nov 15, 2008 
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICDEX
KEYWORDS: ICD-10
KEYWORDS: ICD10
KEYWORDS: 3990
KEYWORDS: ICDCODE
KEYWORDS: 3991
KEYWORDS: ICDAPIU
KEYWORDS: 280
KEYWORDS: 365
KEYWORDS: 582
KEYWORDS: 5388
KEYWORDS: 5404
COMPONENT/ENTRY POINT: HELP
 COMPONENT DESCRIPTION:   This is an interactive help entry point for the input 
 and output variables for the APIs contained in the routine ICDEX.  
  
COMPONENT/ENTRY POINT: $$ICDDX(CODE,CDT,SYS,FMT,LOC)
 COMPONENT DESCRIPTION:   This entry point extracts data for an ICD-9 or ICD-10 
 code in the DIAGNOSIS file 80.  
     
 This entry point is intended to replace the ICD-9 Legacy API $$ICDDX^ICDCODE
 (ICR 3990) and $$ICDDATA^ICDXCODE (ICR 5699), providing a single point of
 entry for ICD diagnostic data.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD diagnosis code in either the external
 or internal format.  If the internal format is used, then the input variable
 FMT must be set to "I" (Required).  
  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to identify the code and text that was appropriate for the date passed in
 this input parameter. (Optional, if not supplied, TODAY will be used) 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD coding system identifier (taken from
 file 80.4).  The following coding systems are found in file 80: 
           
   1 = ICD-9 Diagnosis 
  30 = ICD-10 Diagnosis 
     
 (Optional, but highly encouraged) 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This variable tells the API if the CODE is in
 External or Internal format.  
         
   "E" = External (default) 
   "I" = Internal Entry Number 
     
 (Conditional, required if CODE is in internal format) 
  
VARIABLES: $$ICDDX                      TYPE: Output
 VARIABLES DESCRIPTION:   This is a 20 piece string delimited by "^" 
  
    1  IEN of code in ^ICD9( 
    2  ICD Dx Code                  (#.01) 
    3  Identifier                   (#1.2) 
    4  Versioned Dx                 (67 multiple) 
    5  Unacceptable as Principal Dx (#1.3) 
    6  Major Dx Cat                 (72 multiple) 
    7  MDC13                        (#1.4) 
    8  Compl/Comorb                 (103 multiple) 
    9  ICD Expanded                 (#1.7) 
   10  Status                       (66 multiple) 
   11  Sex                          (10 multiple) 
   12  Inactive Date                (66 multiple) 
   13  MDC24                        (#1.5) 
   14  MDC25                        (#1.6) 
   15  Age Low                      (11 multiple) 
   16  Age High                     (12 multiple) 
   17  Activation Date              (66 multiple) 
   18  Message 
   19  Complication/Comorbidity     (103 multiple) 
   20  Coding System                (#1.1) 
   21  Primary CC Flag              (103 multiple) 
   22  PDX Exclusion Code           (#1.11) 
  or 
  
   -1^Error Description 
  
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a boolean flag used to indicate if the API is
 to use local VA codes.  It only applies to ICD-9 for backwards compatibility.  
  
   1 = Use local VA codes 
   0 = Do not use local VA codes (default) 
  
COMPONENT/ENTRY POINT: $$ICDOP(CODE,CDT,SYS,FMT,LOC)
 COMPONENT DESCRIPTION:   This entry point extracts data for an ICD-9 or ICD-10 
 code in the OPERATIONS/PROCEDURE file 80.1  
     
 This entry point is intended to replace the ICD-9 Legacy API $$ICDOP^ICDCODE
 (ICR 3990) and $$ICDDATA^ICDXCODE (ICR 5699), providing a single point of
 entry for ICD procedural data.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD operation/procedure code in either the
 external or internal format.  If the internal format is used, then the input
 variable FMT must be set to "I" (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to identify the code and text that was appropriate for the date passed in
 CDT.  (Optional, if not supplied, TODAY will be used) 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD coding system identifier (taken from
 file 80.4).  The following coding systems are found in file 80.1: 
      
   2 = ICD-9 Procedures 
  31 = ICD-10 Procedures 
    
 (Optional, but highly encouraged) 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This variable tells the API if the CODE is in 
 External or Internal format.  
     
   "E" = External (default) 
   "I" = Internal Entry Number 
      
 (Conditional, required if CODE is in internal format) 
  
VARIABLES: $$ICDOP                      TYPE: Output
 VARIABLES DESCRIPTION:   This is a 15 piece string delimited by "^" 
                                 
    1   IEN of code in ^ICD0( 
    2   ICD procedure code           (#.01) 
    3   Identifier                   (#1.2) 
    4   MDC24                        (#1.5) 
    5   Versioned Oper/Proc          (67 multiple) 
    6   <null> 
    7   <null> 
    8   <null> 
    9   ICD Expanded                 (#1.7) 
   10   Status                       (66 multiple) 
   11   Use with Sex                 (10 multiple) 
   12   Inactive Date                (66 multiple) 
   13   Activation Date              (66 multiple) 
   14   Message 
   15   Coding System                (#1.1) 
  
  or 
  
   -1^Error Description 
  
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a boolean flag used to indicate if the API is
 to use local VA codes.  It only applies to ICD-9 for backwards compatibility.  
  
   1 = Use local VA codes 
   0 = Do not use local VA codes (default) 
  
COMPONENT/ENTRY POINT: $$ICDD(CODE,.ARY,CDT,SYS,LEN)
 COMPONENT DESCRIPTION:   This API returns the long description of either an
 ICD-9 or ICD-10 code. 
  
 This entry point is intended to replace the ICD-9 Legacy API $$ICDD^ICDCODE
 (ICR 3990) and $$ICDDESC^ICDXCODE (ICR 5699), providing a single point of
 entry for ICD diagnosis/procedure descriptions.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD-9 or ICD-10 code in external format 
 only  (Required). 
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the name of a local array, passed by
 reference that will contain the output of this API.  (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format) 
 used to identify the text that was appropriate for the date passed in this
 input parameter. (Optional, if not supplied, TODAY will be used) 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD coding system identifier (taken from 
 file 80.4).  The following coding systems are found in files 80 and 80.1: 
           
   1 = ICD-9 Diagnosis file 80 
   2 = ICD-9 Procedure file 80.1 
  30 = ICD-10 Diagnosis file 80 
  31 = ICD-10 Procedure file 80.1 
  
 (Optional, but highly encouraged) 
  
VARIABLES: LEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the text string length of the description
 placed in array .ARY.  (Optional, if passed it must be greater than 27 based
 on the longest word found in a diagnosis or procedure description and not
 greater than 245.  If not passed it defaults to 245 characters based in the 
 input transformation) 
  
VARIABLES: $$ICDD                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of lines in the output array .ARY 
 or if an error occurs, -1^Error Message 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   This is a local array, passed by reference,
 containing the long description of an ICD code with string lengths defined by
 LEN when passed or 245 characters.  If there is a warning message about text
 accuracy (ICD-9 only) it will be appended to the end of the message preceded 
 by a blank line. 
        
   ARY(1) - Description (length of LEN) 
   ARY(n) - Description (continued if necessary) 
    
   If there is a warning message (ICD-9 only): 
    
   ARY(n+1) - blank 
   ARY(n+2) - message: CODE TEXT MAY BE INACCURATE 
  
COMPONENT/ENTRY POINT: $$CODEN(CODE,FILE)
 COMPONENT DESCRIPTION:   This API returns the Internal Entry Number (IEN) of a 
 ICD code.  
  
 This entry point is intended to replace the ICD-9 Legacy API $$CODEN^ICDCODE
 (ICR 3990). It is also intended to replace the need for direct global access
 of the 'BA' cross-reference in ICRs 5388 and 5404.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD-9 or ICD-10 code in external format 
 only  (Required).  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the file number where the CODE is stored,
 either 80 or 80.1 (Required) 
  
VARIABLES: $$CODEN                      TYPE: Output
 VARIABLES DESCRIPTION:   This is the Internal Entry Number (IEN) of CODE in 
 file FILE appended by a tilde "~" and the global root FILE: 
        
    IEN~^ROOT 
  
 or -1^Error Message on error 
  
COMPONENT/ENTRY POINT: $$CODEC(FILE,IEN)
 COMPONENT DESCRIPTION:   This entry point returns the ICD-9 or ICD-10 code
 from a specified ICD file and Internal Entry Number (IEN).  
  
 This entry point is intended to replace the ICD-9 Legacy API $$CODEC^ICDCODE
 (ICR 3990).  It is also intended to replace the need for direct global access
 in ICRs 280, 365, 582, 5388, and 5404. 
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to retrieve the code
 (Required) 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number in FILE were the
 code to be retrieved is stored (Required) 
  
VARIABLES: $$CODEC                      TYPE: Output
 VARIABLES DESCRIPTION:   This is either the ICD code stored at the Internal
 Entry Number IEN in the file identified by the FILE input parameter, or upon
 error: 
  
     -1 ^ Error Message 
  
COMPONENT/ENTRY POINT: $$CODEBA(CODE,ROOT)
 COMPONENT DESCRIPTION:   This entry point returns the internal entry number
 (IEN) of a code found in the 'BA' cross-reference in the file specified.  
     
 This entry point is provided in lieu of ICD-9 Legacy entry point
 $$CODEN^ICDCODE (ICR 3990) which will crash with a <MAXNUMBER> error if the
 code passed has the letter 'E' in the middle of the code (example, ICD-10
 procedure code 041E499 would be interpreted as scientific notation). 
 $$CODEBA^ICDEX is much safer. 
     
 If you already know the coding system, please use $$CODEABA^ICDEX instead.  
    
 This entry point replaces the need for direct global read access of the 'BA'
 cross-reference allowed by ICRs 5388 and 5404.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD Diagnosis code or ICD Procedure 
 code (Required) 
  
VARIABLES: ROOT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the global root (or file number) where the
 code is stored (Required) 
  
VARIABLES: $$CODEBA                     TYPE: Output
 VARIABLES DESCRIPTION:   This is the internal entry number (IEN) in the
 specified file where the code is stored or -1 if not found.  
  
COMPONENT/ENTRY POINT: $$CODEABA(CODE,ROOT,SYS)
 COMPONENT DESCRIPTION:   This entry point returns the internal entry number 
 (IEN) of a code found in the system specific 'ABA' cross-reference in the file
 specified.  
  
 This entry point is provided in lieu of ICD-9 Legacy entry point
 $$CODEN^ICDCODE (ICR 3990) and new entry point $$CODEBA^ICDEX.  
  
 Entry point Comparison: 
  
     $$CODEN^ICDCODE will crash if the code 
     has the letter 'E' in the middle of the 
     code.  Do not use it.  
  
     $$CODEBA^ICDEX is safer but it will fail to 
     return the correct IEN if ICD-9 and ICD-10 
     ever have a similar code.  
  
     $$CODEABA^ICDEX will neither crash or fail 
     to return the correct IEN.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD Diagnosis code or ICD Procedure
 code (Required) 
  
VARIABLES: ROOT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the global root (or file number) where the
 code is stored (Optional if SYS is supplied) 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD coding system identifier (taken from
 file 80.4).  The following coding systems are found in files 80 and 80.1: 
               
    1 = ICD-9 Diagnosis file 80 
    2 = ICD-9 Procedure file 80.1 
   30 = ICD-10 Diagnosis file 80 
   31 = ICD-10 Procedure file 80.1 
  
 This API will look for the code on one of the system specific
 cross-references: 
  
   ^ICD9("ABA",1,CODE,IEN)    ICD-9 Diagnosis 
   ^ICD9("ABA",30,CODE,IEN)   ICD-10 Diagnosis 
   ^ICD0("ABA",2,CODE,IEN)    ICD-9 Procedure 
   ^ICD0("ABA",31,CODE,IEN)   ICD-10 Procedure 
  
 If not supplied, the API will attempt to determine the system based on code
 and file.  
               
 (Optional, but highly encouraged) 
  
VARIABLES: $$CODEABA                    TYPE: Output
 VARIABLES DESCRIPTION:   This is the internal entry number (IEN) in the 
 specified file where the code is stored or -1 if not found. 
  
COMPONENT/ENTRY POINT: $$CODEFI(CODE)
 COMPONENT DESCRIPTION:   This entry point tries to resolve which file has an
 ICD code on file.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD Diagnosis code or ICD Procedure
 code (Required) 
  
VARIABLES: $$CODEFI                     TYPE: Output
 VARIABLES DESCRIPTION:   This is the ICD file number where the specified code 
 was found: 
  
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
 or NULL if not found or could not resolve to a single file.  
  
COMPONENT/ENTRY POINT: $$CODECS(CODE,FILE,CDT)
 COMPONENT DESCRIPTION:   This entry point tries to resolve the Coding System 
 based on a code, a file and a date.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD Diagnosis code or ICD Procedure
 code (Required) 
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to resolve the 
 coding system: 
  
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
 (Optional, but encouraged)  If not supplied, an attempt to resolve the input
 variable FILE will be made using the entry point $$CODEFI(CODE).  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to resolve the coding system.  
  
 This date is ONLY used if a code is found in both ICD-9 and ICD-10 systems. 
 If that ever happens, the date passed will determine the coding system. If the 
 date passed is before the ICD-10 implementation date it will be considered an
 ICD-9 code and if it is on or after the ICD-10 implementation date then it
 will be considered ICD-10.  
  
VARIABLES: $$CODECS                     TYPE: Output
 VARIABLES DESCRIPTION:   This is a 2 piece "^" delimited string containing: 
  
    1   Coding System (pointer to file 80.4) 
    2   Coding Nomenclature (commonly used name) 
     
 Example output values: 
     
    1^ICD-9-CM 
   30^ICD-10-CM 
    2^ICD-9 Proc 
   31^ICD-10-PCS 
  
 NULL if the API cannot resolve the coding system based on code, file and date. 
  
COMPONENT/ENTRY POINT: $$CSI(FILE,IEN)
 COMPONENT DESCRIPTION:   This entry point returns the Coding System for an 
 Internal Entry Number (IEN).  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to retrieve the
 coding system (Required): 
         
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file
 specified (Required). 
  
VARIABLES: $$CSI                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a pointer to the ICD CODING SYSTEMS file
 #80.4 
  
COMPONENT/ENTRY POINT: $$VMDC(IEN,CDT,FMT)
 COMPONENT DESCRIPTION:   This entry point retrieves the versioned Major 
 Diagnostic Category (MDC) for a diagnostic code in the DIAGNOSIS file 80.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 DIAGNOSIS file 80 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to identify the Major Diagnostic Category that was appropriate for the
 date passed (Optional, if not passed TODAY is used). 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag used to determine the output format.
 Acceptable values are 0 and 1 (Optional, default value is 0). 
     
     FMT = 0    Major Diagnostic Category (MDC) 
     FMT = 1    MDC^Effective Date 
  
VARIABLES: $$VMDC                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the Major Diagnostic Category (MDC) that was
 appropriate for the date passed and the diagnosis code identified by input
 parameter IEN.  The output may also have a second "^" delimited piece
 containing the MDC Effective Date if the input parameter FMT is set to 1.  
  
COMPONENT/ENTRY POINT: $$VAGEL(IEN,CDT,FMT)
 COMPONENT DESCRIPTION:   This entry point retrieves the versioned Age Low 
 value for a diagnostic code in the DIAGNOSIS file 80.  Age Low is the minimum
 age value for an age range for which the diagnostic code can be applied. 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 DIAGNOSIS file 80 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to identify the Age Low value that was appropriate for the date passed
 (Optional, if not passed TODAY is used).  
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag used to determine the output format.
 Acceptable values are 0 and 1 (Optional, default value is 0). 
     
     FMT = 0    Age Low 
     FMT = 1    Age Low^Effective Date 
  
VARIABLES: $$VAGEL                      TYPE: Output
 VARIABLES DESCRIPTION:   This is the Age Low that was appropriate for the date
 passed and the diagnosis code identified by the input parameter IEN.  The
 output may also have a second "^" delimited piece containing the Age Low
 Effective Date if the input parameter FMT is set to 1.  Null if Age Low not
 found for date. 
  
COMPONENT/ENTRY POINT: $$VAGEH(IEN,CDT,FMT)
 COMPONENT DESCRIPTION:   This entry point retrieves the versioned Age High
 value for a diagnostic code in the DIAGNOSIS file 80.  Age High is the maximum 
 age value for an age range for which the diagnostic code can be applied.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 DIAGNOSIS file 80 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to identify the Age High value that was appropriate for the date passed
 (Optional, if not passed TODAY is used). 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag used to determine the output format.
 Acceptable values are 0 and 1 (Optional, default value is 0). 
     
     FMT = 0    Age High 
     FMT = 1    Age High^Effective Date 
  
VARIABLES: $$VAGEH                      TYPE: Output
 VARIABLES DESCRIPTION:   This is the Age High that was appropriate for the 
 date passed and the diagnosis code identified by the input parameter IEN.  The
 output may also have a second "^" delimited piece containing the Age High
 Effective Date if the input parameter FMT is set to 1.  Null if Age High is
 not found for date.  
  
COMPONENT/ENTRY POINT: $$VCC(IEN,CDT,FMT)
 COMPONENT DESCRIPTION:   This entry point retrieves the versioned Complication
 Comorbidity (CC) designation for a diagnostic code in the DIAGNOSIS file 80.  
 A diagnostic code can be designated as: 
    
   Non-Complication Comorbidity (Non-CC) 
   Complication Comorbidity (CC) 
   Major Complication Comorbidity (MCC) 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 DIAGNOSIS file 80 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to identify the CC designation value that was appropriate for the date
 passed (Optional, if not passed TODAY is used).  
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag used to determine the output format.
 Acceptable values are 0 and 1 (Optional, default value is 0). 
     
     FMT = 0    CC designation 
     FMT = 1    CC designation^Effective Date 
  
VARIABLES: $$VCC                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the CC designation that was appropriate for
 the date passed and the diagnosis code identified by the input parameter IEN. 
 The output may also have a second "^" delimited piece containing the CC
 designation Effective Date if the input parameter FMT is set to 1. 
  
   0 = Non-Complication Comorbidity (Non-CC) 
   1 = Complication Comorbidity (CC) 
   2 = Major Complication Comorbidity (MCC) 
  
 Null if not found for date 
  
COMPONENT/ENTRY POINT: $$VSEX(FILE,IEN,CDT,FMT)
 COMPONENT DESCRIPTION:   This entry point retrieves the versioned sex 
 designation for a diagnostic or procedure code in either the ICD DIAGNOSIS
 file 80 or the ICD OPERATION/PROCEDURE file 80.1. If a sex designation exist
 then the diagnosis or procedure should be applied only to that sex.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to retrieve the sex
 designation: 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in either the
 DIAGNOSIS file 80 or OPERATION/PROCEDURE file 80.1 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to identify the sex designation value that was appropriate for the date
 passed (Optional, if not passed TODAY is used).  
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag used to determine the output format.
 Acceptable values are 0 and 1 (Optional, default value is 0). 
     
     FMT = 0    Sex designation 
     FMT = 1    Sex designation^Effective Date 
  
VARIABLES: $$VSEX                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the sex designation that was appropriate for
 the date passed and the code identified by the input parameter IEN.  The
 output may also have a second "^" delimited piece containing the sex
 designation Effective Date if the input parameter FMT is set to 1. 
  
   M = Male 
   F = Female 
   Null if sex is N/A or not found for date 
  
COMPONENT/ENTRY POINT: $$SAI(FILE,IEN,CDT)
 COMPONENT DESCRIPTION:   This entry point retrieves the Status, Activation
 date and Inactivation date for a diagnosis or procedure on a specified date.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to retrieve the
 status and effective dates: 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in either the
 DIAGNOSIS file 80 or OPERATION/PROCEDURE file 80.1 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to retrieve the status and effective dates that were appropriate for the
 date passed (Optional, if not passed TODAY is used).  
  
VARIABLES: $$SAI                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a 6 piece "^" delimited string 
        
    1  Status 
    2  Activation Date 
    3  Inactivation Date 
    4  IEN 
    5  Code 
    6  Short Text 
  
       If the status is active, the short 
       text will be the most recent.  
  
       If the status is inactive, the short 
       text will be the text in use on the 
       date it was inactivated.  
  
       Null if no status for date.  
  
COMPONENT/ENTRY POINT: $$VST(FILE,IEN,CDT)
 COMPONENT DESCRIPTION:   This entry point retrieves the Versioned Short Text
 for an diagnosis or procedure on a specified date.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to retrieve the
 Versioned Short Text: 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in either the
 DIAGNOSIS file 80 or OPERATION/PROCEDURE file 80.1 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to retrieve the Versioned Short Text that was appropriate for the date
 passed (Optional, if not passed TODAY is used).  
  
VARIABLES: $$VST                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the Versioned Short Text from either file 80
 (DIAGNOSIS) or 80.1 (OPERATION/PROCEDURE) that was appropriate for the date
 passed and the code identified by the input parameter IEN.  Null if not found. 
  
COMPONENT/ENTRY POINT: $$VLT(FILE,IEN,CDT)
 COMPONENT DESCRIPTION:   This entry point retrieves the Versioned Long Text
 (description) for a diagnosis or procedure on a specified date.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to retrieve the
 Versioned Long Text (description): 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in either the
 DIAGNOSIS file 80 or OPERATION/PROCEDURE file 80.1 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to retrieve the Versioned Long Text (description) that was appropriate
 for the date passed (Optional, if not passed TODAY is used).  
  
VARIABLES: $$VLT                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the Versioned Long Text (description) from
 either file 80 or 80.1 that was appropriate for the date passed and the code
 identified by the input parameter IEN.  Null if not found.  
  
COMPONENT/ENTRY POINT: $$VSTD(IEN,CDT)
 COMPONENT DESCRIPTION:   This entry point retrieves the Versioned Short Text
 for a diagnosis on a specified date.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 DIAGNOSIS file 80 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to retrieve the Versioned Short Text that was appropriate for the date
 passed (Optional, if not passed TODAY is used).  
  
VARIABLES: $$VSTD                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the Versioned Short Text from file 80 that
 was appropriate for the date passed and the code identified by the input
 parameter IEN.  Null if not found.  
  
COMPONENT/ENTRY POINT: $$VSTP(IEN,CDT)
 COMPONENT DESCRIPTION:   This entry point retrieves the Versioned Short Text
 for a procedure on a specified date.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 OPERATION/PROCEDURE file 80.1 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to retrieve the Versioned Short Text that was appropriate for the date
 passed (Optional, if not passed TODAY is used).  
  
VARIABLES: $$VSTP                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the Versioned Short Text from file 80.1 that
 was appropriate for the date passed and the code identified by the input
 parameter IEN.  Null if not found.  
  
COMPONENT/ENTRY POINT: $$VLTD(IEN,CDT)
 COMPONENT DESCRIPTION:   This entry point retrieves the Versioned Long Text
 (description) for a diagnosis on a specified date. 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 DIAGNOSIS file 80 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to retrieve the Versioned Long Text (description) that was appropriate
 for the date passed (Optional,  If not passed TODAY is used). 
  
VARIABLES: $$VLTD                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the Versioned Long Text (description) from
 file 80 that was appropriate for the date passed and the code identified by
 the input parameter IEN.  Null if not found.  
  
COMPONENT/ENTRY POINT: $$VLTP(IEN,CDT)
 COMPONENT DESCRIPTION:   This entry point retrieves the Versioned Long Text
 (description) for a procedure on a specified date. 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 OPERATION/PROCEDURE file 80.1 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to retrieve the Versioned Long Text (description) that was appropriate
 for the date passed (Optional,  If not passed TODAY is used). 
  
VARIABLES: $$VLTP                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the Versioned Long Text (description) from
 file 80.1 that was appropriate for the date passed and the code identified by
 the input parameter IEN.  Null if not found.  
  
COMPONENT/ENTRY POINT: $$SD(FILE,IEN,CDT,.ARY,LEN)
 COMPONENT DESCRIPTION:   This entry point retrieves the Versioned Short Text
 for a procedure on a specified date.  This entry point is similar to $$VST
 except you can elect to have the Short Text returned in a local array and you
 can specify the string lengths of the text in the array.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to retrieve the
 Versioned Short Text (Required): 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an internal entry number (IEN) in either file
 80 or 80.1 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to retrieve the Versioned Short Text that was appropriate for the date
 passed (Optional,  If not passed TODAY is used).  
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a local array name passed by reference that
 will contain the Short Text output.  
  
VARIABLES: LEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a number greater than 27 and less than 246
 representing the desired text string lengths for the Short Text output.  If
 specified, the output will be parsed into strings not to exceed the length 
 specified (Optional, default 245) 
  
VARIABLES: $$SD                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the Versioned Short Text from either file 80
 or 80.1 that was appropriate for the date passed and the code identified by
 the input parameter IEN.  If not found: 
     
    -1^Error Message 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   If passed, this is a local array containing the
 number of text lines, the effective date of the Short Text and the text.  If
 the input parameter LEN (length) is specified and the length is shorter than
 the Short Text, then the Short Text will be parsed into test strings not to
 exceed LEN.  
     
   ARY(0)=# lines ^ effective date 
   ARY(1)=Short Text 
     
   LEN is defined shorter than text 
    
   ARY(0)=# lines ^ effective date 
   ARY(1)=String length not to exceed LEN 
   ARY(n)=String length not to exceed LEN 
  
 Null if not found 
  
COMPONENT/ENTRY POINT: $$LD(FILE,IEN,CDT,.ARY,LEN)
 COMPONENT DESCRIPTION:   This entry point retrieves the Versioned Long Text
 (description) for a procedure on a specified date.  This entry point is
 similar to $$VLT except you can elect to have the Long Text (description) 
 returned in a local array and you can specify the string lengths of the text
 in the array.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to retrieve the
 Versioned Long Text (description) (Required): 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an internal entry number (IEN) in either file
 80 or 80.1 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to retrieve the Versioned Long Text (description) that was appropriate
 for the date passed (Optional,  If not passed TODAY is used).  
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a local array name passed by reference that
 will contain the Long Text (description) output.  
  
VARIABLES: LEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a number greater than 27 and less than 246
 representing the desired text string lengths for the Long Text (description) 
 output.  If specified, the output will be parsed into strings not to exceed
 the length specified (Optional, default 245) 
  
VARIABLES: $$LD                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the Versioned Long Text (description) from
 either file 80 or 80.1 that was appropriate for the date passed and the code
 identified by the input parameter IEN.  If not found: 
        
     -1^Error Message 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   If passed, this is a local array containing the
 number of text lines, the effective date of the Long Text (description) and
 the text.  If the input parameter LEN (length) is specified and the length is
 shorter than the Long Text (description), then the Long Text (description) 
 will be parsed into test strings not to exceed LEN.  
     
   ARY(0)=# lines ^ effective date 
   ARY(1)=Long Text (description) 
     
   LEN defined shorter than text 
     
   ARY(0)=# lines ^ effective date 
   ARY(1)=String length not to exceed LEN 
   ARY(n)=String length not to exceed LEN 
  
COMPONENT/ENTRY POINT: PAR(.ARY,LEN)
 COMPONENT DESCRIPTION:   This entry point takes text in a local array (passed
 by reference) and parses it into string lengths not to exceed the length 
 specified.  
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a local array name passed by reference and
 contains the text to be parsed into strings not to exceed the length
 specified.  
        
   ARY(1) = Unparsed Text 
  
VARIABLES: LEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a number representing the desired text string
 lengths for the text found in ARY().  (Optional, default length 79) 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   This is a local array containing the input text 
 parsed so that each text string length does not exceed the length specified.  
     
   ARY(1)=Parsed Text length not to exceed LEN 
   ARY(n)=Parsed Text length not to exceed LEN 
  
COMPONENT/ENTRY POINT: $$STATCHK(CODE,CDT,SYS)
 COMPONENT DESCRIPTION:   This entry point is used to determine the status 
 (active or inactive) of a ICD code.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD diagnosis or procedure code 
 (external format) (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to retrieve the code's status, internal entry number (IEN) and effective
 date that was appropriate for the date passed (Optional,  If not passed TODAY
 is used) 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD coding system identifier (taken from
 file 80.4).  The following coding systems are found in files 80 and 80.1: 
    
      1 = ICD-9 Diagnosis 
     30 = ICD-10 Diagnosis 
      2 = ICD-9 Procedures 
     31 = ICD-10 Procedures 
  
 (Optional, but encouraged, if doesn't exist it will try to determine coding
 system by input parameter CODE) 
  
VARIABLES: $$STATCHK                    TYPE: Output
 VARIABLES DESCRIPTION:   This is a three piece "^" delimited string 
    
    1  Status 1 = Active, 0 = Inactive 
    2  IEN or -1 on error 
    3  Effective Date or error message 
    
    Error           0 ^ -1 ^ Error message 
    Active Code     1 ^ IEN ^ Effective Date 
    Inactive Code   0 ^ IEN ^ Effective Date 
  
COMPONENT/ENTRY POINT: $$DTBR(CDT,STD,SYS)
 COMPONENT DESCRIPTION:   This entry point returns the business rule date for a 
 coding system.  This is in earliest date possible for a coding standard and/or
 a coding system.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to resolved the business rule date.  (Optional, if not passed TODAY is
 used) 
  
VARIABLES: STD                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a coding standard from a Standards 
 Development Organization (SDO).  A standard may have one or more coding
 systems.  (Optional, default is 0) 
         
     0 = ICD (Default) 
     1 = CPT/HCPCS 
     2 = DRG 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD coding system identifier (taken from
 file 80.4).  (Optional, there is no default value for this parameter, if it
 does not exist then it is not used) 
     
 The following coding systems are found in files 80 and 80.1: 
    
      1 = ICD-9 Diagnosis 
     30 = ICD-10 Diagnosis 
      2 = ICD-9 Procedures 
     31 = ICD-10 Procedures 
  
VARIABLES: $$DTBR                       TYPE: Output
 VARIABLES DESCRIPTION:   Date adjusted by business rules: 
  
 If Standard (SDT) = 0 (ICD) 
  
    If CDT < 2781001 use 2781001 
    If CDT < 3131001 and SYS=30, use 3131001 
    If CDT < 3131001 and SYS=31, use 3131001 
  
 If Standard (SDT) = 1 (CPT/HCPCS) 
  
    If CDT < 2890101 use 2890101 
  
 If Standard (SDT) = 2 (DRG) 
  
    If CDT < 2821001 use 2821001 
  
 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: $$IMP(SYS,CDT)
 COMPONENT DESCRIPTION:   This entry point returns the date a coding system was
 implemented (taken from file 80.4).  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a coding system (taken from file 80.4) or a 
 coding system identifier that can be resolved to a coding system.  
     
    1 = ICD-9-CM 
    2 = ICD-9-PCS 
   30 = ICD-10-CM 
   31 = ICD-10-PCS 
  
   DX, DIAG, 80, ^ICD9( 
  
     1 = ICD-9-CM if CDT is before the ICD-10 implementation date 
    30 = ICD-10-CM if CDT is on or after the ICD-10 implementation date 
                             
   PR, PROC, OPER, 80.1, ^ICD0( 
                             
     2 = ICD-9-CM if CDT is before  the ICD-10 implementation date 
    31 = ICD-10-CM if CDT is on or after  the ICD-10 implementation date 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to resolve the coding system parameter SYS (Optional, if not passed TODAY
 is used) 
  
VARIABLES: $$IMP                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the date that a coding system identified by
 the input parameters SYS and CDT was implemented in Fileman format or on
 error: 
  
 -1 ^ Error message 
  
COMPONENT/ENTRY POINT: $$MSG(CDT,STD,SYS)
 COMPONENT DESCRIPTION:   This entry point returns a warning message that the
 text may be inaccurate for the date specified.  It applies only to ICD-9 
 Diagnosis and Procedures.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to determine the accuracy of the text being returned (Optional, if not
 passed TODAY is used) 
  
VARIABLES: STD                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a coding standard from a Standards 
 Development Organization (SDO).  A standard may have one or more coding
 systems.  (Optional, default is 0) 
         
     0 = ICD (Default) 
     1 = CPT/HCPCS 
     2 = DRG 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD coding system identifier (taken from
 file 80.4).  (Optional, there is no default value for this parameter, if it
 does not exist then it is not used) 
     
 The following coding systems are found in files 80 and 80.1: 
    
      1 = ICD-9 Diagnosis 
     30 = ICD-10 Diagnosis 
      2 = ICD-9 Procedures 
     31 = ICD-10 Procedures 
  
VARIABLES: $$MSG                        TYPE: Output
 VARIABLES DESCRIPTION:   If coding system is not ICD-10 and the date passed is
 before the Code Set Versioning project Oct 1, 2002, then this variable is set
 to the warning message, "CODE TEXT MAY BE INACCURATE" otherwise it is null.  
  
COMPONENT/ENTRY POINT: $$SEL(FILE,IEN)
 COMPONENT DESCRIPTION:   This entry point determines if an entry in a file is
 selectable by calling applications.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD file number: 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file
 specified.  
  
VARIABLES: $$SEL                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a Boolean value: 
  
    1  Entry IEN in file FILE is Selectable 
    0  Entry IEN in file FILE is NOT Selectable 
  
 or 
  
 -1  on error 
  
COMPONENT/ENTRY POINT: $$NEXT(CODE,SYS,CDT)
 COMPONENT DESCRIPTION:   This entry point returns the Next code in a sequence
 of codes in a coding system.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD diagnosis, an ICD procedure
 code or null to retrieve the first code in a sequence.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD coding system identifier (taken from
 file 80.4).  (Optional) 
  
 The following coding systems are found in ICD files 80 and 80.1: 
    
      1 = ICD-9 Diagnosis 
     30 = ICD-10 Diagnosis 
      2 = ICD-9 Procedures 
     31 = ICD-10 Procedures 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to determine the next code being returned (Optional, there is no default
 value for this parameter) 
  
 If CDT date is not passed then this entry point will return the next code, 
 regardless of status (active or inactive) 
  
 If CDT date is passed then this entry point will return the next active code.  
  
VARIABLES: $$NEXT                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the next code in a sequence of codes.  If the
 input code is null, then it will return the first code of the sequence of
 codes.  If a date is passed in the input parameter CDT, then it will return
 the next active code in a sequence of codes.  
  
COMPONENT/ENTRY POINT: $$PREV(CODE,SYS,CDT)
 COMPONENT DESCRIPTION:   This entry point returns the Previous code in a
 sequence of codes in a coding system.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD diagnosis, an ICD procedure
 code or null to retrieve the last code in a sequence.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD coding system identifier (taken from
 file 80.4).  (Optional) 
  
 The following coding systems are found in ICD files 80 and 80.1: 
    
      1 = ICD-9 Diagnosis 
     30 = ICD-10 Diagnosis 
      2 = ICD-9 Procedures 
     31 = ICD-10 Procedures 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to determine the Previous code being returned (Optional, there is no
 default value for this parameter) 
  
 If CDT date is not passed then this entry point will return the previous code,
 regardless of status  (active or inactive) 
  
 If CDT date is passed then this entry point will return the previous active
 code.  
  
VARIABLES: $$PREV                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the previous code in a sequence of codes.  If
 the input code is null, then it will return the last code of the sequence of
 codes.  If a date is passed in the input parameter CDT, then it will return
 the previous active code in a sequence of codes.  
  
COMPONENT/ENTRY POINT: $$HIST(CODE,.ARY,SYS)
 COMPONENT DESCRIPTION:   This entry point returns a code's activation history. 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD diagnosis or procedure code.  
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a local array name passed by reference that
 will contain the code's activation history.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD coding system identifier (taken from
 file 80.4).  (Optional) 
  
 The following coding systems are found in ICD files 80 and 80.1: 
    
      1 = ICD-9 Diagnosis 
     30 = ICD-10 Diagnosis 
      2 = ICD-9 Procedures 
     31 = ICD-10 Procedures 
  
VARIABLES: $$HIST                       TYPE: Output
 VARIABLES DESCRIPTION:   This is set equal to the number of history entries in
 the local array ARY or -1 if there is an error or the code is not found.  
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   This is a local array containing the history records 
    
    ARY(0) = Number of History Entries 
    ARY(<effective date>,<status>) = comment 
  
COMPONENT/ENTRY POINT: $$PERIOD(CODE,.ARY,SYS)
 COMPONENT DESCRIPTION:   This entry point returns all the activation periods
 for a code.  An activation period is defined as the period of time between the 
 beginning activation effective date and the ending inactivation effective
 date.  If the code is still active the period will have an activation date
 without an inactivation date.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD diagnosis or procedure code.  
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a local array name passed by reference that
 will contain the code's activation periods.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD coding system identifier (taken from
 file 80.4).  (Optional) 
  
 The following coding systems are found in ICD files 80 and 80.1: 
    
      1 = ICD-9 Diagnosis 
     30 = ICD-10 Diagnosis 
      2 = ICD-9 Procedures 
     31 = ICD-10 Procedures 
  
VARIABLES: $$PERIOD                     TYPE: Output
 VARIABLES DESCRIPTION:   This is a 2 piece "^" delimited string if successful
 and 3 piece "^" delimited string if unsuccessful or error.  
  
    1   IEN of code 
    2   Code is selectable (boolean 1/0) 
  
  or on error 
  
   -1 ^ 0 ^ Error Message 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   This is a local array containing the Periods of 
 activation for the code 
  
 ARY(0) 
  
    This is a 2 piece "^" delimited string if 
    successful and a 3 piece "^" delimited string 
    if unsuccessful or error.  
  
      1   IEN of code 
      2   Code is selectable (boolean 1/0) 
  
    or on error 
  
     -1^0^Error Message 
  
 ARY(Activation Date) = Inactivation Date^Short Name 
  
    Where the Short Name is the Versioned text, and the 
    text is versioned as follows: 
  
    Period is active   - Text for TODAY's date 
    Period is inactive - Text for inactivation date 
  
COMPONENT/ENTRY POINT: $$OBA(FILE,CODE,SYS,REV)
 COMPONENT DESCRIPTION:   This entry point is used to $ORDER through the BA or
 ABA cross-references and replaces the need to access the BA/ABA
 cross-references in a FOR loop.  This entry point is meant to replace BA
 cross-reference in ICRs 5388 and 5404.  
  
   $$OBA(<file>,<code>,<system>) replaces: 
  
     $O(^ICD9("BA",(<code>_" ")) and 
     $O(^ICD0("BA",(<code>_" ")) 
  
   Examples: 
  
   F  S CODE=$$OBA(80,CODE,1) Q:'$L(CODE)  D 
   F  S CODE=$$OBA(80,CODE,30) Q:'$L(CODE)  D 
   F  S CODE=$$OBA(80.1,CODE,2) Q:'$L(CODE)  D 
   F  S CODE=$$OBA(80.1,CODE,31) Q:'$L(CODE)  D 
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to determine the
 global root to $ORDER through (Required): 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD diagnosis or procedure code to
 $ORDER from (required): 
    
    $O(^ROOT("BA",(CODE_" "))) 
    $O(^ROOT("ABA",SYS,(CODE_" "))) 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD diagnosis or procedure 
  
 This is an ICD coding system identifier (taken from file 80.4).  (Optional) 
  
 The following coding systems are found in ICD files 80 and 80.1: 
    
      1 = ICD-9 Diagnosis 
     30 = ICD-10 Diagnosis 
      2 = ICD-9 Procedures 
     31 = ICD-10 Procedures 
  
 If the coding system can be identified then the "BA" cross-reference is
 ignored and the $ORDER will be performed on the "ABA" cross-reference: 
    
    $O(^ROOT("ABA",SYS,(CODE_" "))) 
  
 The "ABA" cross-reference is a coding system specific cross-reference.  
  
VARIABLES: REV                          TYPE: Used
 VARIABLES DESCRIPTION:   This is a Reverse $ORDER flag, if set to 1, the
 $ORDER operation will be in the reverse direction of "BA" or "ABA"
 cross-reference (Optional, default is 0, $ORDER forward) 
     
 If equal to 1 
     
    $O(^ROOT("BA",(CODE_" ")),-1) 
    $O(^ROOT("ABA",SYS,(CODE_" ")),-1) 
  
VARIABLES: $$OBA                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the Next or Previous Code in the "BA" or
 "ABA" cross-reference depending on the $ORDER direction established by the 
 input parameter REV.  
  
COMPONENT/ENTRY POINT: $$OD(FILE,WORD,SYS,REV)
 COMPONENT DESCRIPTION:   This entry point is used to $ORDER through the "D" or
 "AD" cross-reference and replaces the need to access the D/AD cross-references 
 in a FOR loop.  This entry point is meant to replace the D cross-reference in
 ICRs 5388 and 5404.  
  
   $$OD(<file>,<word>,<system>) replaces: 
  
     $O(^ICD9("D",(<word>_" ")) and 
     $O(^ICD0("D",(<word>_" ")) 
  
   Examples: 
  
   F  S WORD=$$OD(80,WORD,1) Q:'$L(WORD)  D 
   F  S WORD=$$OD(80,WORD,30) Q:'$L(WORD)  D 
   F  S WORD=$$OD(80.1,WORD,2) Q:'$L(WORD)  D 
   F  S WORD=$$OD(80.1,WORD,31) Q:'$L(WORD)  D 
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to determine the
 global root to $ORDER through (Required): 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: WORD                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a one or two piece "^" delimited string 
  
   1  WORD  This is a single word parsed from the 
            codes description.  
  
   2  IEN   This is the internal entry number where 
            the description can be found that 
            contains the parsed word 
  
   WORD and IEN can be null.  
  
 $$OD $ORDER through "WORD^IEN" on either the D or AD cross-references 
  
 Coding System unknown:  $O(^ROOT("D",WORD,IEN)) Coding System known:   
 $O(^ROOT("AD",SYS,WORD,IEN)) 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD coding system identifier (taken from
 file 80.4).  (Optional) 
  
 The following coding systems are found in ICD files 80 and 80.1: 
    
      1 = ICD-9 Diagnosis 
     30 = ICD-10 Diagnosis 
      2 = ICD-9 Procedures 
     31 = ICD-10 Procedures 
  
 If the coding system can be identified then the "D" cross-reference is ignored
 and the $ORDER will be performed on the "AD" cross-reference: 
    
    $O(^ROOT("AD",SYS,(CODE_" "))) 
  
 The "AD" cross-reference is a coding system specific cross-reference.  
  
VARIABLES: REV                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a Reverse $ORDER flag, if set to 1, the
 $ORDER operation will be in the reverse direction of "D" or "AD"
 cross-reference (Optional, default is 0, $ORDER forward) 
     
 If equal to 1 
     
    $O(^ROOT("D",WORD)),-1) 
    $O(^ROOT("AD",SYS,WORD)),-1) 
  
VARIABLES: $$OD                         TYPE: Output
 VARIABLES DESCRIPTION:   This is a 2 piece "^" delimited string containing the
 Next or Previous Word in the "D" or "AD" cross-reference and accompanying IEN
 depending on the $ORDER direction established by the input parameter REV.  
  
 WORD^IEN taken from cross-references 
  
     ^ROOT("D",WORD,IEN) or 
     ^ROOT("AD",SYS,WORD,IEN) 
  
COMPONENT/ENTRY POINT: $$DLM(FILE,IEN,FIELD,CDT)
 COMPONENT DESCRIPTION:   This entry point returns the date a record or field
 was last modified.  If the field number is passed, then the date last modified 
 (based on date) for the field is returned.  If the field is not passed, then
 the date last modified (based on date) for the record at IEN is returned.  The
 following are valid versioned fields: 
  
    File 80 
    
    10   Sex                          5;0 
    11   Age Low                      6;0 
    12   Age High                     7;0 
    66   Status                      66;0 
    67   Diagnosis                   67;0 
    68   Description                 68;0 
    71   DRG Grouper                  3;0 
    72   Major Diagnostic Category    4;0 
   103   Complication/Comorbidity    69;0 
    
    File 80.1 
    
    10   Sex                          3;0 
    66   Status                      66;0 
    67   Operation/Procedure         67;0 
    68   Description                 68;0 
    71   DRG Grouper                  2;0 
  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to determine the
 global root to $ORDER through (Required): 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file
 specified (Required) 
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the field number of a versioned data element
 in the file specified.  (Optional, with no default value)  
  
 If the field number is provided then this API will return the date that the
 field was last modified.  
  
 If the field number is not provided then this API will return the date that
 the record was last modified.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to determine the date last modified (Optional, if not provided then TODAY
 is used) 
  
VARIABLES: $$DLM                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the date last modified for the record
 identified by the input parameters FILE and IEN.  If the input parameter FIELD
 is set to a valid versioned field then this will be the date that the field 
 was last modified.  
  
 or -1 ^ message on error 
  
COMPONENT/ENTRY POINT: $$CS(FILE,FMT,CDT)
 COMPONENT DESCRIPTION:   This is an interactive entry point to select a coding
 system.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to select a coding
 system (Optional, if not provided you will be prompted for an ICD file
 Number): 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag to determine the display format for
 the prompts: 
           
    E  Display External only (default) 
    I  Display External with Internal 
  
    Prompt using External only, default: 
  
    FMT=E      1   ICD-9-CM 
               2   ICD-10-CM 
  
    Prompt using External with Internal: 
  
    FMT=I      1   ICD-9-CM       (#1) 
               2   ICD-10-CM      (#30) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an optional date to use in selecting a coding
 system.  If passed, only coding systems with an implementation date on or
 before the date passed are selectable (optional) 
  
VARIABLES: $$CS                         TYPE: Output
 VARIABLES DESCRIPTION:   This is a 2 piece "^" delimited string 
  
 1  Coding System (internal) 2  Coding System (external) 
  
 or  -1  on error or non-selection or  ^^  double up-arrows or  ^   timeout or
 single up-arrow 
  
COMPONENT/ENTRY POINT: $$EFF(FILE,IEN,CDT)
 COMPONENT DESCRIPTION:   This entry point returns a codes status, inactivation
 date and activation date (replaces EFF^ICDSUPT) 
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD file number (Required): 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file
 specified (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to determine the status and effective dates on the date specified
 (Optional, if not provided then TODAY is used) 
  
VARIABLES: $$EFF                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a 3 piece "^" delimited string 
     
     1   Status 
         1 - Active 
         0 - Inactive 
     2   Inactivation Date 
     3   Activation Date 
  
  or 
    -1^error message 
  
COMPONENT/ENTRY POINT: $$LA(FILE,IEN,CDT)
 COMPONENT DESCRIPTION:   This entry point returns the last activation 
 effective date based on a date passed.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD file number (Required): 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file
 specified (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to determine the last activation date based on the date specified
 (Optional, if not provided then TODAY is used) 
  
VARIABLES: $$LA                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the last activation date (Fileman format) or 
  
 -1^Not activated on or before date specified 
  
COMPONENT/ENTRY POINT: $$LI(FILE,IEN,CDT)
 COMPONENT DESCRIPTION:   This entry point returns the last inactivation 
 effective date based on a date passed.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD file number (Required): 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file
 specified (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to determine the last inactivation date based on the date specified
 (Optional, if not provided then TODAY is used) 
  
VARIABLES: $$LI                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the last inactivation date (Fileman format)
 or 
  
 -1^Not inactivated on or before date specified 
  
COMPONENT/ENTRY POINT: $$LS(FILE,IEN,CDT)
 COMPONENT DESCRIPTION:   This entry point returns the last code status based
 on a date passed.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD file number (Required): 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file
 specified (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to determine the last code status based on the date specified (Optional,
 if not provided then TODAY is used) 
  
VARIABLES: $$LS                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the last code status based on the date 
 passed.  
  
     1 - Active 
     0 - Inactive 
  
  or 
  
   -1^No status on or before date specified 
  
COMPONENT/ENTRY POINT: $$NUM(CODE)
 COMPONENT DESCRIPTION:   This entry point converts a code to a numeric
 representation (found on the AN cross-reference) 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD diagnosis or procedure code
 (Required)  (This is the opposite of $$COD) 
  
VARIABLES: $$NUM                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a numeric representation of a code.  
  
COMPONENT/ENTRY POINT: $$COD(NUM)
 COMPONENT DESCRIPTION:   This entry point converts a numeric representation of
 a code to a code (found on the AN cross-reference) 
  
VARIABLES: NUM                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a numeric representation of an ICD diagnosis
 or procedure code (This is the opposite of $$NUM) 
  
VARIABLES: $$COD                        TYPE: Output
 VARIABLES DESCRIPTION:   This is an ICD diagnosis or procedure code.  
  
COMPONENT/ENTRY POINT: $$IE(CODE)
 COMPONENT DESCRIPTION:   This entry point determines if a code is in an
 external or internal format without plusing (+) the code.  
  
 If you have an ICD-10 code with the letter "E in the center and plus it you 
 will receive a MAXNUMBER error.  
  
 Example:  If you plus (+) the ICD-10 procedure code "041E499" it will be 
 interpreted as a scientific notation (E499 is a really big number).  
 Applications that plus the ICD code can use this entry point to safely 
 determine a code's format.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD diagnosis or procedure code
 (Required) 
  
VARIABLES: $$IE                         TYPE: Output
 VARIABLES DESCRIPTION:   This is a set of codes as follows: 
     
    I  CODE is in an internal format (IEN) 
    E  CODE is in an external format (Code) 
  
 or 
  
    Null on error 
  
COMPONENT/ENTRY POINT: $$FILE(SYS)
 COMPONENT DESCRIPTION:   This entry point will return an ICD file number.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a coding system, a global root or a file 
 identifier.  
  
 Global roots ^ICD9( and ^ICD0( are acceptable Coding Systems can be found in
 file 80.4 File Identifier:  DX or PR 
                   DIAG or PROC or OPER 
  
VARIABLES: $$FILE                       TYPE: Output
 VARIABLES DESCRIPTION:   This is an ICD file number 80 or 80.1 
  
 or -1 on error 
  
COMPONENT/ENTRY POINT: $$ROOT(SYS)
 COMPONENT DESCRIPTION:   This entry point will return an ICD global root.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a coding system, file number, a file 
 identifier or even an ICD code, provided the code is unique to a file.  
  
 Coding Systems can be found in file 80.4 File Number 80 or 80.1 File
 Identifier:  DX or PR 
                   DIAG or PROC or OPER 
  
VARIABLES: $$ROOT                       TYPE: Output
 VARIABLES DESCRIPTION:   This is a global root ^ICD9( or ^ICD0( or Null on
 error 
  
COMPONENT/ENTRY POINT: $$SYS(SYS,CDT,FMT)
 COMPONENT DESCRIPTION:   This entry point will return a coding system.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This can be either a Coding System name, 
 Abbreviation, system identifier (uses date) or a code.  
  
 Coding System Names: ICD-9-CM, ICD-9 Proc, ICD-10-CM or ICD-10-PCS 
  
 Coding System Abbreviations: ICD, ICP, 10D or 10P 
  
 System Identifier (with date CDT) 
  
   Date is before the ICD-10 implementation date 
                             
     DIAG, ICD9, 80, DX =  1 
     PROC, OPER, ICD0, ICP9, 80.1, PR = 2 
                             
   Date is on or after the ICD-10 implementation date 
                             
     DIAG, ICD9, 80, DX =  30 
     PROC, OPER, ICD0, ICP9, 80.1, PR = 31 
  
 An ICD code 
  
    If an ICD code is unique to an ABA 
    cross-reference then the Coding System 
    can be determined from a code 
  
     ^ICD9("ABA",1,(CODE_" "))   = 1 
     ^ICD9("ABA",30,(CODE_" "))  = 30 
     ^ICD9("ABA",2,(CODE_" "))   = 2 
     ^ICD9("ABA",31,(CODE_" "))  = 31 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to determine the coding system based on a system identifier (Optional, if 
 not provided then TODAY is used) 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a single character identifying the desired
 output format (Optional, default is "I"): 
     
     I  Internal (default) 
     E  External 
     B  Both Internal ^ External 
  
VARIABLES: $$SYS                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the Coding System in the format specified by
 the input parameter FMT: 
  
   FMT=I     FMT=E        FMT=B 
   Internal  External     Both 
  
      1      ICD-9-CM     1^ICD-9-CM 
      2      ICD-9 Proc   2^ICD-9 Proc 
     30      ICD-10-CM    30^ICD-10-CM 
     31      ICD-10-PCS   31^ICD-10-PCS 
  
  or 
  
     -1   on error 
  
COMPONENT/ENTRY POINT: $$SINFO(SYS,CDT)
 COMPONENT DESCRIPTION:   This entry point returns coding system information 
 taken from file 80.4.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This can be either a Coding System name, 
 Abbreviation, system identifier, file number or a code.  (system identifier
 and code uses date).  
  
 Coding System Names: 
  
   ICD-9-CM 
   ICD-9 Proc 
   ICD-10-CM or 
   ICD-10-PCS 
  
 Coding System Abbreviations: 
  
   ICD, ICP, 10D or 10P 
  
 System Identifier/File Number (with date CDT) 
  
    Date is before the ICD-10 implementation date 
  
      DIAG, ICD9, 80, DX =  1 
      PROC, OPER, ICD0, ICP9, 80.1, PR = 2 
  
    Date is on or after the ICD-10 implementation date 
  
      DIAG, ICD9, 80, DX =  30 
      PROC, OPER, ICD0, ICP9, 80.1, PR = 31 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to determine the coding system based on a system identifier (Optional, if 
 not provided then TODAY is used) 
  
VARIABLES: $$SINFO                      TYPE: Output
 VARIABLES DESCRIPTION:   This is a 6 piece "^" delimited string 
  
     1      IEN to file 80.4 
     2      Coding System 
     3      Coding System Abbreviation 
     4      File Number 
     5      Implementation Date 
     6      Content 
  
  or 
  
    -1   on error 
  
COMPONENT/ENTRY POINT: $$SNAM(SYS)
 COMPONENT DESCRIPTION:   This entry point returns the coding system name.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the coding system file 80.4 
  
VARIABLES: $$SNAM                       TYPE: Output
 VARIABLES DESCRIPTION:   This the coding system name, file 80.4 (.01) 
  
     ICD-9-CM 
     ICD-9 Proc 
     ICD-10-CM 
     ICD-10-PCS 
  
   Or  -1   on error 
  
COMPONENT/ENTRY POINT: $$SAB(SYS,CDT)
 COMPONENT DESCRIPTION:   This entry point returns the coding system
 abbreviation.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This can be either a Coding System name, 
 Abbreviation, system identifier (uses date) or a code.  
  
 Coding System Names: ICD-9-CM, ICD-9 Proc, ICD-10-CM or ICD-10-PCS 
  
 Coding System Abbreviations: ICD, ICP, 10D or 10P 
  
 System Identifier (with date CDT) 
  
    Date is before the ICD-10 implementation date 
  
      DIAG, ICD9, 80, DX =  1 
      PROC, OPER, ICD0, ICP9, 80.1, PR = 2 
  
    Date is on or after the ICD-10 implementation date 
  
      DIAG, ICD9, 80, DX =  30 
      PROC, OPER, ICD0, ICP9, 80.1, PR = 31 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to determine the source abbreviation based on a system identifier 
 (Optional, if not provided then TODAY is used) 
  
VARIABLES: $$SAB                        TYPE: Output
 VARIABLES DESCRIPTION:   3 Character Coding System abbreviation, file 80.4
 (.02) 
  
     ICD 
     ICP 
     10D 
     10P 
  
   Or  -1   on error 
  
COMPONENT/ENTRY POINT: $$EXC(FILE,IEN)
 COMPONENT DESCRIPTION:   This entry point returns a boolean value indicating
 if an entry in the specified file is to be excluded from lookup.  If it is to
 be excluded, then the entry will not be placed on the selection list for a 
 user to select from.  Used primarily for the special lookup.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD file number: 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file
 specified.  
  
VARIABLES: $$EXC                        TYPE: Output
 VARIABLES DESCRIPTION:   Boolean value 
  
    1 = Yes, exclude from lookup 
    0 = No, include in the lookup 
  
COMPONENT/ENTRY POINT: $$ISA(IEN1,IEN2,FIELD)
 COMPONENT DESCRIPTION:   This entry point returns a boolean value indicating
 that one code is a "condition" of another.  Conditions include: 
   
    Code 1 is Not Used With Code 2 
    Code 1 is Required With Code 2 
    Code 1 is Not Considered CC With Code 2 
  
VARIABLES: IEN1                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number (IEN) of a code in
 file 80 that has a relationship with the code at IEN2  IEN1 is equivalent to 
 Fileman's DA and identifies a code stored in a multiple in field 20, 30, 40 or
 pointed to by field 1.11.  
  
VARIABLES: IEN2                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number (IEN) of a code in
 file 80 that may have other codes (IEN1) associated with it.  IEN2 is
 equivalent to Fileman's DA(1) and identifies the code in the .01 field.  
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   This is a field number in file 80 that contains one
 or more ICD codes that have a relationship to the main entry.   Acceptable
 field numbers and the type of relationships to check include: 
    
  Field       Relationship 
  20          Code 1 Not Used With Code 2 
  30          Code 1 Required With Code 2 
  40 or 1.11  Code 1 Not Considered CC With Code 2 
  
VARIABLES: $$ISA                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a Boolean value 
    
    1   Yes/The relationship is True 
    0   No/The relationship is False 
    
    Field       Answers the Question 
    -----       --------------------------------
    20          Code 1 (identified by IEN1) is 
                not used with Code 2 (identified 
                by IEN2) 
     
    30          Code 1 (identified by IEN1) is 
                required with Code 2 (identified 
                by IEN2) 
    
    40 or 1.11  Code 1 (identified by IEN1) is 
                not considered Complication 
                Comorbidity (CC) with Code 2 
                (identified by IEN2) 
  
COMPONENT/ENTRY POINT: $$EXIST(IEN,FIELD)
 COMPONENT DESCRIPTION:   This entry point determines if special condition ICD
 codes exist.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 DIAGNOSIS file 80 (Required) 
  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   This is a field number in file 80 that contains one
 or more ICD codes that have a relationship to the main entry (Required) 
 Acceptable field numbers to check include: 
  
    20   Code Not Used With 
    30   Code Required With 
    40   Code Not Considered CC With 
  
VARIABLES: $$EXIST                      TYPE: Output
 VARIABLES DESCRIPTION:   Boolean value 
  
    1   Yes/True, codes exist 
    0   No/False, codes do not exist 
  
    Field   Answers the Question 
    -----   -------------------------------
    20      Are there any codes that should 
            not be used with this code (IEN) 
    30      Are there any codes required 
            with this code (IEN) 
    40      Are there any codes that are not 
            considered CC with this code 
            (IEN) 
  
COMPONENT/ENTRY POINT: $$GETDRG(FILE,IEN,CDT,MDC)
 COMPONENT DESCRIPTION:   This entry point returns a string of DRGs for an ICD
 Diagnosis or Procedure code.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to retrieve the DRGs
 (Required): 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file
 specified (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to identify the DRGs that were appropriate on that date (Optional, if not 
 passed then TODAY is used) 
  
VARIABLES: MDC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a Major Diagnostic Category (pointer to file
 80.3) used as a screen to limit the DRGs to an MDC.  This input parameter only 
 applies to the ICD OPERATIONS/PROCEDURE file 80.1 which has multiple MDCs,
 each with a possibility of multiple DRGs  (Conditional) 
  
VARIABLES: $$GETDRG                     TYPE: Output
 VARIABLES DESCRIPTION:   3 piece semi-colon ";" delimited string 
  
    1  DRGs delimited by ^ 
    2  Fiscal Year 
    3  Status flag 
       0 inactive 
       1 active 
  
 Example output: 
  
    907^908^909^;3071001;1 
  
 On Error: 
  
    -1;No DRG level;0 
  
COMPONENT/ENTRY POINT: MD(FILE,IEN,CDT,.ARY,FLAG)
 COMPONENT DESCRIPTION:   This entry point returns an array of Major Diagnostic
 Categories (MDCs) and Diagnosis Related Groups (DRGs) 
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to retrieve the
 Major Diagnostic Categories (Required): 
     
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file
 specified (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to identify the MDCs that were appropriate on that date (Optional, if not 
 passed then TODAY is used)  NOTE:  If no Fiscal Year is found for the input
 date then the first (earliest( Fiscal Year is used.  
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a local array name passed by reference that
 will contain a list of MDCs by effective date 
  
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag that determines the output format: 
    
    I   = Internal (default) Internal values 
          are always returned 
  
    E   = Include External values with Internal 
          values 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   ICD Procedures file 80.1 (multiple MDC) 
    
    ARY(<fiscal year>,<MDC>)=DRG^;FY;STA 
    ARY(<fiscal year>,<MDC>)="DRG^DRG^;FY;STA 
  
    If Flag contains "E" 
    
    ARY(<fiscal year>,"E",<MDC>)=MDC Name 
    ARY(<fiscal year>,"E",<MDC>,<DRG>)=DRG Name 
    ARY(<fiscal year>,"E",<MDC>)=MDC Name 
    ARY(<fiscal year>,"E",<MDC>,<DRG>)=DRG Name 
    ARY(<fiscal year>,"E",<MDC>,<DRG>)=DRG Name 
    ARY(<fiscal year>,"E","FY")=External FY 
  
 ICD Diagnosis file 80 (single MDC) 
  
    ARY(<fiscal year>,<MDC>)="DRG^DRG^;FY;STA 
  
    If Flag contains "E" 
  
    ARY(<fiscal year>,"E",<MDC>)=MDC Name 
    ARY(<fiscal year>,"E",<MDC>,<DRG>)=DRG Name 
    ARY(<fiscal year>,"E",<MDC>,<DRG>)=DRG Name 
    ARY(<fiscal year>,"E","FY")=External FY 
  
 NOTE:  If no Fiscal Year found for the input date then the first (earliest)
 Fiscal Year is used.  
  
COMPONENT/ENTRY POINT: $$EFM(CDT)
 COMPONENT DESCRIPTION:   This entry point converts an external date to a
 Fileman internal date.  This entry point replaces unsupported 
 $$DGY2K^DGPTOD0(X) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   External date (Required), examples of valid dates: 
  
    JAN 20 1957 or 20 JAN 57 
    1/20/57 or 012057 
    T   (for TODAY) 
    T+1 (for TOMORROW),  T+2,  etc.  
    T-1 (for YESTERDAY) 
    T-3W (for 3 WEEKS AGO), etc.  
  
VARIABLES: $$EFM                        TYPE: Output
 VARIABLES DESCRIPTION:   Internal Fileman Date 
  
 or -1 on error 
  
COMPONENT/ENTRY POINT: $$FY(CDT)
 COMPONENT DESCRIPTION:   This entry point returns the 4 digit fiscal year for
 a specified date.  This entry point replaces unsupported $$FY^DGPTOD0(X) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an internal Fileman date.  
  
VARIABLES: $$FY                         TYPE: Output
 VARIABLES DESCRIPTION:   This is a 4 digit fiscal year (YYYY) for the date
 specified or null on error.  
  
COMPONENT/ENTRY POINT: $$VMDCDX(IEN,CDT)
 COMPONENT DESCRIPTION:   This entry point returns the versioned Major 
 Diagnostic Code for an ICD Diagnosis.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the
 DIAGNOSIS file 80 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to identify the MDCs that was appropriate on that date (Optional, if not 
 passed then TODAY is used) 
  
VARIABLES: $$VMDCDX                     TYPE: Output
 VARIABLES DESCRIPTION:   This is a single MDC (pointer to file 80.3) active on
 the date specified.  
  
COMPONENT/ENTRY POINT: $$VMDCOP(IEN,MDC,CDT)
 COMPONENT DESCRIPTION:   This entry point returns the versioned Major
 Diagnostic Codes for an ICD Procedure.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the
 OPERATION/PROCEDURE file 80.1 (Required) 
  
VARIABLES: MDC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a Major Diagnostic Category (pointer to file
 80.3) used as a screen to limit the results to a single MDC (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to identify the MDC that was appropriate on that date (Optional, if not 
 passed then TODAY is used) 
  
VARIABLES: $$VMDCOP                     TYPE: Output
 VARIABLES DESCRIPTION:   4 piece "^" delimited string 
    
    1   Fiscal Year, Fileman format 
    2   MDC, pointer to file 80.3 
    3   Fiscal Year, pointer to sub-file 
        80.171 (formerly DADRGFY) 
    4   MDC, pointer to sub-file 80.1711 
        (formerly DAMDC) 
  
COMPONENT/ENTRY POINT: MDCG(IEN,CDT,.ARY)
 COMPONENT DESCRIPTION:   This entry point sets up an array of MDCs (later used
 in $$MDCT) 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 DIAGNOSIS file 80 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to identify the MDCs that were appropriate on that date (Optional, if not 
 passed then TODAY is used) 
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a local array name passed by reference that
 will contain a list of MDCs (Required) 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   This is an array listing MDCs for all DRGs associated 
 with a diagnosis on the date specified.  
    
    ARY(MDC)="" 
    ARY(MDC)="" 
  
COMPONENT/ENTRY POINT: $$MDCT(IEN,CDT,.ARY,FMT)
 COMPONENT DESCRIPTION:   This entry point compares a single entry in the ICD
 OPERATIONS/PROCEDURE file 80.1 to an array of Major Diagnostic Categories to
 see if the ICD procedure is assigned to one or more of the MDCs in the array.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 OPERATIONS/PROCEDURE file 80.1 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to identify the MDCs that were appropriate on that date (Optional, if not 
 passed then TODAY is used) 
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a local array passed by reference containing
 a list of MDCs for comparison (Required) 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag defining the output format (optional): 
    
    0   Boolean value only (default) 
    1   2 piece "^" delimited string 
  
        1   Boolean value 
        2   String of matching MDCs 
            delimited by ";" 
  
VARIABLES: $$MDCT                       TYPE: Output
 VARIABLES DESCRIPTION:   Boolean value 
    
    0  The ICD Procedure code identified by IEN 
       does not include any of the MDCs passed 
       in .ARY(MDC) on the date specified (CDT) 
  
    1  The ICD Procedure code identified by IEN 
       includes one or more of the MDCs passed 
       in .ARY(MDC) on the date specified (CDT) 
  
 Assuming the following input parameters: 
  
    IEN=4 
    CDT=3111110 
    ARY(2)="" 
    ARY(21)="" 
  
    Output format when input parameter FMT=0 
    (default) 
  
       $$MDCT(IEN,CDT,.ARY) = "1" 
  
    Output format when input parameter FMT=1 
  
       $$MDCT(IEN,CDT,.ARY) = "1^2;21" 
  
COMPONENT/ENTRY POINT: $$MDCD(IEN,MDC,CDT)
 COMPONENT DESCRIPTION:   This entry point checks for a Major Diagnostic 
 Category MDC in the ICD OPERATION/PROCEDURE file.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 OPERATIONS/PROCEDURE file 80.1 (Required) 
  
VARIABLES: MDC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a Major Diagnostic Category (pointer to file
 80.3) (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to identify the MDCs that were appropriate on that date (Optional, if not 
 passed then the first FY is used) 
  
VARIABLES: $$MDCD                       TYPE: Output
 VARIABLES DESCRIPTION:   Boolean value 
    
    0  MDC does not exist on date specified 
    1  MDC exist on date specified 
  
COMPONENT/ENTRY POINT: $$MOR(IEN)
 COMPONENT DESCRIPTION:   This entry point returns the Major O.R. Procedure
 string 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 OPERATIONS/PROCEDURE file 80.1 (Required) 
  
VARIABLES: $$MOR                        TYPE: Output
 VARIABLES DESCRIPTION:   Major O.R. Procedure or Null if the procedure is not
 defined as a Major O.R. Procedure or is not found 
  
 Major O.R. Procedure definitions include: 
  
 1   Bowel                 2  Chest         3   Lymphoma/Leukemia     4  Joint 
 5   Pancreas/Liver        6  Pelvic 7   Shoulder/Elbow        8  Thumb/Joint 9 
  Head/Neck             A  Cardio M   Musculoskeletal       B  Spine 
  
COMPONENT/ENTRY POINT: $$UPDX(IEN)
 COMPONENT DESCRIPTION:   This entry point determines if a diagnosis is 
 unacceptable as a principle diagnosis.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 DIAGNOSIS file 80 (Required) 
  
VARIABLES: $$UPDX                       TYPE: Output
 VARIABLES DESCRIPTION:   Boolean value, answers the question: 
  
    Is the diagnosis UNACCEPTABLE as a Principle DX? 
    
    1   Yes  Code is Unacceptable as Principle DX 
    0   No   Code is Acceptable as Principle DX 
  
COMPONENT/ENTRY POINT: $$NOT(IEN,SUB,FMT)
 COMPONENT DESCRIPTION:   This entry point returns the number of ICD codes that
 cannot be used with a specified code.  It can also return a global array
 containing a list of the codes that cannot be used with the specified code.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 DIAGNOSIS file 80 (Required) 
  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a subscript name used in a ^TMP global array
 (Optional, if not provided, the subscript "ICDNOT" will be used) 
     
     ^TMP(SUB,$J) 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag defining the output format.  
   
   0 - Total number only (default) 
   1 - Total number with global array 
  
VARIABLES: $$NOT                        TYPE: Output
 VARIABLES DESCRIPTION:   The number of ICD codes that cannot be used with the
 ICD code identified by IEN (FMT=0 or 1) 
    
 TMP global array as follows (FMT=1): 
    
    ^TMP(SUB,$J,IEN)=CODE 
    ^TMP(SUB,$J,"B",(CODE_" "),IEN)="" 
  
COMPONENT/ENTRY POINT: $$REQ(IEN,SUB,FMT)
 COMPONENT DESCRIPTION:   This entry point returns the number of ICD codes that
 are required when the specified code is used.  It can also return a global
 array containing a list of the codes that are required when the specified code
 is used.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 DIAGNOSIS file 80 (Required) 
  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a subscript name used in a ^TMP global array
 (Optional, if not provided, the subscript "ICDREQ" will be used) 
     
     ^TMP(SUB,$J) 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag defining the output format.  
   
   0 - Total number only (default) 
   1 - Total number with global array 
  
VARIABLES: $$REQ                        TYPE: Output
 VARIABLES DESCRIPTION:   The number of ICD codes required when the ICD code 
 identified by IEN is used. (FMT=0 or 1) 
    
 TMP global array as follows (FMT=1): 
    
    ^TMP(SUB,$J,IEN)=CODE 
    ^TMP(SUB,$J,"B",(CODE_" "),IEN)="" 
  
COMPONENT/ENTRY POINT: $$NCC(IEN,SUB,FMT)
 COMPONENT DESCRIPTION:   This entry point returns the number of ICD codes that
 are not considered CC with a specified code.  It can also return a global
 array containing a list of the codes that are not considered CC with a
 specified code.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the 
 DIAGNOSIS file 80 (Required) 
  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a subscript name used in a ^TMP global array
 (Optional, if not provided, the subscript "ICDNCC" will be used) 
     
     ^TMP(SUB,$J) 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag defining the output format.  
   
   0 - Total number only (default) 
   1 - Total number with global array 
  
VARIABLES: $$NCC                        TYPE: Output
 VARIABLES DESCRIPTION:   The number of ICD codes not considered CC with the 
 code identified by IEN. (FMT=0 or 1) 
    
 TMP global array as follows (FMT=1): 
    
    ^TMP(SUB,$J,IEN)=CODE 
    ^TMP(SUB,$J,"B",(CODE_" "),IEN)="" 
  
COMPONENT/ENTRY POINT: LK
 COMPONENT DESCRIPTION:   Special Lookup (called by DIC) 
  
 This is the Special Lookup program for files 80 and 80.1.  Only the ^DIC call
 honors the special lookup routines.  Those calls that allow the user to
 specify the indexes (IX^DIC and MIX^DIC1), and the Data Base Server calls 
 (FIND^DIC, $$FIND1^DIC, and UPDATE^DIE) all ignore the Special Lookup Program. 
 Also, if DIC(0) contains an "I" then the Special Lookup program will be
 ignored.  
  
 This routine uses a majority of the variables used in calling Fileman ^DIC. 
 In addition to the Fileman variables, there are three special variables that
 aid in controlling the lookup that can be set and killed by the calling 
 application;  
  
   Versioning Date (Fileman format) 
  
      ICDVDT or 
      ^TMP("ICDEXLK",$J,"ICDVDT")=<versioning date> 
  
   Coding System (from file 80.4) 
  
      ICDSYS or 
      ^TMP("ICDEXLK",$J,"ICDSYS")=<coding system> 
  
   Display Format (numeric, 1-4) (new) 
  
      ICDFMT or 
      ^TMP("ICDEXLK",$J,"ICDFMT")=<display format> 
  
VARIABLES: ICDVDT                       TYPE: Input
 VARIABLES DESCRIPTION:   Versioning Date (Fileman format) 
  
   ICDVDT or 
   ^TMP("ICDEXLK",$J,"ICDVDT")=<date> 
  
 This is a Code Set Versioning Date (in Fileman format).  If set, it must also
 be killed by the calling application.  
  
 If supplied, it is assumed that the lookup is to be a versioned lookup and
 only active codes on that date will be included in the selection list.  
  
 If not supplied, the date will default to TODAY and all codes may be selected,
 active and inactive.  
  
 In both cases the display will be altered based on the date.  
  
VARIABLES: ICDSYS                       TYPE: Input
 VARIABLES DESCRIPTION:   Coding System (from file 80.4) 
  
   ICDSYS or 
   ^TMP("ICDEXLK",$J,"ICDSYS")=<coding system> 
  
 This is the Coding System taken from file 80.4.  If set, it must be killed by
 the calling application.  It may be any of the following: 
    
     1    ICD    ICD-9-CM 
     2    ICP    ICD-9 Proc 
    30    10D    ICD-10-CM 
    31    10P    ICD-10-PCS 
  
 If supplied, the lookup will only look in the cross-references specific for
 that coding system.  
  
VARIABLES: ICDFMT                       TYPE: Input
 VARIABLES DESCRIPTION:   Display Format (numeric, 1-4) 
  
   ICDFMT or 
   ^TMP("ICDEXLK",$J,"ICDFMT")=<display format> 
  
 This is a flag defining a Display Format (numeric, 1-4).  If set, it must be
 killed by the calling application.  
  
 1 = Fileman format, code and short text 
     (default) 
  
     250.00    DMII WO CMP NT ST UNCNTR 
  
 2 = Fileman format, code and description 
  
     250.00    DIABETES MELLITUS WITHOUT 
               MENTION OF COMPLICATION, 
               TYPE II OR UNSPECIFIED TYPE, 
               NOT STATED AS UNCONTROLLED 
  
 3 = Lexicon format, short text followed 
     by code 
  
     DMII WO CMP NT ST UNCNTR (250.00) 
  
 4 = Lexicon format, description followed 
     by code 
  
     DIABETES MELLITUS WITHOUT MENTION OF 
     COMPLICATION, TYPE II OR UNSPECIFIED 
     NOT STATED AS UNCONTROLLED (250.00) 
  
  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   This is the user's input, if not available the user
 will be prompted for input.  
  
VARIABLES: FILEMAN                      TYPE: Input
 VARIABLES DESCRIPTION:   FileMan Variables used 
  
    DIC, DIC(0), DIC("A"), DIC("B"), 
    DIC("S"), DIC("W"), DIC("?N",<file>) 
  
 FileMan Variables not used: 
  
    DIC("DR"),DIC("PTRIX",<fm>,<to>,<file>), 
    DIC("T"), DIC("V"), DIC("?PARAM") 
  
 DIC(0) parameters applicable to a versioned file 
  
    A   Ask the entry; if erroneous, ask again 
    B   Only the B index is used 
    E   Echo information 
    F   Forget the lookup value 
    I   Ignore the special lookup program 
    O   Only find one entry if it matches exactly 
    Q   Question Input ?? 
    S   Suppresses display of .01 
    T   Search until user selects or enters ^^ 
    X   EXact match required 
    Z   Zero node in Y(0), external form in Y(0,0) 
  
 DIC(0) parameters NOT applicable to a versioned file and not used 
  
    C   Versioned cross-references not turned off 
    K   Primary Key not established 
    L   Learning a new entry LAYGO not allowed 
    M   Multiple-index lookup allowed 
    N   Uppercase, IEN lookup allowed (not forced) 
    n   ICD has no pure numeric entries 
    U   All values are external 
    V   Verification is not optional 
  
 FileMan Variables KILLed: 
  
    DLAYGO 
    DINUM 
  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Fileman Compliant: 
  
    Y        IEN ^ Code 
  
    If DIC(0) containing "Z" 
  
    Y(0)     0 Node 
    Y(0,0)   Code 
  
 Non-Fileman Compliant, DIC(0) contains "Z" 
  
    Y(0,1)   $$ICDDX or $$ICDOP 
    Y(0,2)   Long Description 
  
COMPONENT/ENTRY POINT: $$LKTX(X,ROOT,CDT,SYS,VER,OUT)
 COMPONENT DESCRIPTION:   This entry point is a lookup for text in either file
 80 or 80.1  It is similar to the special lookup except there is no prompt for
 input or display for selection (silent) and intended for GUI applications.  
  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   This is a string of text to search for.  
  
VARIABLES: ROOT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either a global root or file number to
 indicate either the DIAGNOSIS file 80 or the OPERATIONS/PROCEDURE file 80.1 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning date (Fileman format)
 used to determine the status of a code (active or inactive) It normally
 represents the date that service was provided to the patient (HIPAA). 
 However, it may also represent the date of onset, visit date or movement date
 depending on the application calling the lookup.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a coding system identifier (pointer to file
 80.4) 
  
    1 = ICD-9-CM 
    2 = ICD-9-PCS 
   30 = ICD-10-CM 
   31 = ICD-10-PCS 
  
VARIABLES: VER                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the versioned flag (boolean) to indicate if
 the lookup is to be versioned or not: 
  
    0  No   Include all codes, active 
            and inactive 
  
    1  Yes  Include only Active codes 
            for date specified 
  
VARIABLES: OUT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag that defines the output format: 
  
   1  Fileman, Code and Short Text (default) 
  
      250.00    DMII WO CMP NT ST UNCNTR 
  
   2  Fileman, Code and Description 
  
      250.00    DIABETES MELLITUS WITHOUT 
                MENTION OF COMPLICATION TYPE 
                II OR UNSPECIFIED TYPE, NOT 
                STATED AS UNCONTROLLED 
  
   3  Lexicon, Short Text and Code 
  
      DMII WO CMP NT ST UNCNTR (250.00) 
  
   4  Lexicon, Description and Code 
  
      DIABETES MELLITUS WITHOUT MENTION OF 
      COMPLICATION, TYPE II OR UNSPECIFIED, 
      NOT STATED AS UNCONTROLLED (250.00) 
  
VARIABLES: $$LK                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of entries found 
  
 The entries will be included in a ^TMP Global Array: 
  
    ^TMP(ID,$J,"SEL") 
    ^TMP(ID,$J,"SEL",0)=# of entries 
    ^TMP(ID,$J,"SEL",#)=IEN ^ Display Text 
  
   Where ID is a package namespaced subscript: 
  
    ICD9 - for file #80 
    ICD0 - for file #80.1 
  
COMPONENT/ENTRY POINT: $$VER(SYS,REL)
 COMPONENT DESCRIPTION:   This API returns the current Coding System version, 
 the previous Coding System version or the next Coding System version based on
 input parameters.  
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer to the coding system file 80.4 
  
VARIABLES: REL                          TYPE: Input
 VARIABLES DESCRIPTION:   This input parameter indicates the relationship of 
 the output coding system to the input coding system (Optional) 
  
    0   N/A - Return the current version (default) 
    1   Return the next version 
   -1   Return the previous version 
  
VARIABLES: $$VER                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a 5 piece string containing: 
    
     1   Coding System (pointer to file 80.4) 
     2   Coding System Nomenclature 
     3   Coding System Abbreviation 
     4   File Number containing the Coding System 
     5   Date Coding System was Implemented or 
    -1   on error 
  
COMPONENT/ENTRY POINT: Y(ROOT,IEN,CDT,FMT)
 COMPONENT DESCRIPTION:   Given the global root or file number, the Internal
 Entry Number (IEN) and a date, this API will return the equivalent of
 FileMan's output variable Y without having to perform the lookup.  
  
VARIABLES: ROOT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is either an ICD global root or file number.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number in the file 
 identified by the input parameter ROOT.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a code set versioning date used to returned
 versioned (date sensitive) data from the ICD files.  
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a output format flag (optional, default 0).  
  
   0  Return standard Fileman Y - IEN ^ CODE 
   1  Return Expanded Y as if DIC(0) contained a "Z" 
  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Input parameter FMT = 0 or 1 
  
   Y = IEN ^ Code 
  
 Input parameter FMT = 1 
  
   FileMan Compliant 
  
     Y(0)    =  0 Node    (aka Code) 
     Y(0,0)  =  .01 Field (aka Code) 
  
   Non-FileMan Compliant 
  
     Y(0,1)  =  $$ICDDX or $$ICDOP 
     Y(0,2)  =  Versioned Long Description 
  
COMPONENT/ENTRY POINT: TOKEN(TEXT,ROOT,SYS,ARY)
 COMPONENT DESCRIPTION:   This API parses text into words/tokens and saves them
 in a local array for later processing.  Words and tokens not found in the file
 and coding system identified by the input parameters are not included in the
 output array.  
  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a text string to parse.  
  
VARIABLES: ROOT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a global root or file number (required) 
   
    ^ICD9(  or  80 
    ^ICD0(  or  80.1 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the coding system  (Required) 
  
     1  or  ICD  or  ICD-9-CM 
     2  or  ICP  or  ICD-9 Proc 
    30  or  10D  or  ICD-10-CM 
    31  or  10P  or  ICD-10-PCS 
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is the output array passed by reference that
 contains a list of words parsed from the input string X and arranged by
 frequency of use 
         
    ARY(0)=# of words 
    ARY(#)=word 
            
 The least frequently used word will be ARY(1) and the most frequently used
 word will be ARY($O(ARY(" "),-1)).  Words not found in the file and coding
 system will not appear in the parsed array.  
  
COMPONENT/ENTRY POINT: $$WORD(WORD,ROOT,SYS)
 COMPONENT DESCRIPTION:   This API determines if a word is found in a file or a
 coding system identified by the input parameters 
  
VARIABLES: WORD                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a single word.  
  
VARIABLES: ROOT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a global root or file number (optional) 
   
    ^ICD9(  or  80 
    ^ICD0(  or  80.1 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the coding system (Optional) 
  
     1  or  ICD  or  ICD-9-CM 
     2  or  ICP  or  ICD-9 Proc 
    30  or  10D  or  ICD-10-CM 
    31  or  10P  or  ICD-10-PCS 
  
VARIABLES: $$WORD                       TYPE: Output
 VARIABLES DESCRIPTION:   This is a Boolean value indicating if a word is
 contained in a set (file or system).  
  
   1 = Word was found 
   
       If ROOT is not supplied, the word was 
       found in either file 80 or 80.1 
  
       If SYS is not supplied, the word was 
       found in the file designated by ROOT 
       in any coding system in the file 
  
       If both ROOT and SYS are supplied, 
       the word was found in the specified 
       coding system 
  
   0 = Word was not found 
  
COMPONENT/ENTRY POINT: $$ICDIDS(FILE,CODE,ARY)
 COMPONENT DESCRIPTION:   This API returns an array of Diagnosis or Procedure
 code Identifiers used in the calculation of DRG groups.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to retrieve the
 identifier codes (Required): 
         
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file
 specified (Required). 
  
VARIABLES: ARY                          TYPE: Both
 VARIABLES DESCRIPTION:   This is a local array of identifiers found for the
 code identified input parameters FILE and CODE.  
  
        ARY(<identifier>)="" 
  
VARIABLES: $$ICDIDS                     TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of identifiers found for the code
 identified by the input parameters FILE and CODE, or upon error: 
  
     -1^error message 
  
COMPONENT/ENTRY POINT: $$ICDID(FILE,ID,CODE)
 COMPONENT DESCRIPTION:   This API checks if a specified ICD identifier exist
 for a code identified by the input parameters FILE and CODE.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the ICD file number used to retrieve the
 identifier codes (Required): 
         
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: ID                           TYPE: Input
 VARIABLES DESCRIPTION:   This is a Diagnosis or Procedure code identifier
 (required) 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file
 specified (Required).  
  
VARIABLES: $$ICDID                      TYPE: Output
 VARIABLES DESCRIPTION:   Boolean value 
  
    1 if identifier was found for code 
    0 if identifier was not found for code 
    
    or upon error -1^error message 
  
COMPONENT/ENTRY POINT: $$ISOWNCC(IEN,CDT,FMT)
 COMPONENT DESCRIPTION:   This API returns the Complication/Comorbidity (CC)
 value for an ICD Diagnosis code when the primary diagnosis is its own CC/MCC.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Internal Entry Number (IEN) of the ICD
 Diagnosis file #80.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Date to use to extract CC (default TODAY) 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a flag that controls the output format: 
  
    0 = CC only (default) 
    1 = CC ^ Effective Date 
  
VARIABLES: $$ISOWNCC                    TYPE: Output
 VARIABLES DESCRIPTION:   Complication/Comorbidity (CC) 
    
    DX is Own CC  Format  Output 
    ------------  ------  -------------------------
         Yes        0     CC Value 
         Yes        1     CC Value ^ Effective Date 
         No        N/A    0 (zero) 
    
    or upon error -1^error message 
  
COMPONENT/ENTRY POINT: $$ICDRGCC(DRG,CDT)
 COMPONENT DESCRIPTION:   This API returns the CC/MCC flag from DRG file #80.2 
  
VARIABLES: DRG                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number for the DRG file
 80.2 (required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Date to use to extract CC/MCC flag (default TODAY) 
  
VARIABLES: $$ICDRGCC                    TYPE: Output
 VARIABLES DESCRIPTION:   This is the Complication/Comorbidity/Major CC flag 
  
     0   No CC or MCC 
     1   CC present 
     2   MCC present 
     3   CC or MCC present 
  
 or upon error -1^error message 
  
COMPONENT/ENTRY POINT: $$DRG(CODE,CDT)
 COMPONENT DESCRIPTION:   This API returns basic information about a DRG.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   DRG code, internal or external format (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Date to check status for, FileMan format (default =
 TODAY) 
  
    If CDT < 10/1/1978, use 10/1/1978 
    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 
  
VARIABLES: $$DRG                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns an 22 piece string delimited by the up-arrow
 (^) the pieces are: 
    
    1  DRG name (field #.01) 
    2  Weight (field #2) 
    3  Low Trim (days) (field #3) 
    4  High Trim (days) (field #4) 
    5  MDC (field #5) 
    6  Surgery Flag (field #.06) 
    7  <null> 
    8  Avg Length of Stay (days) (field 10) 
    9  Local Low Trim Days (field #11) 
   10  Local High Trim Days (field #12) 
   11  <null> 
   12  Local Breakeven (field #13) 
   13  Activation Date (.01 field, 66 multiple) 
   14  Status (.03 field, 66 multiple) 
   15  Inactivation Date (.01 field, 66 multiple) 
   16  Effective date (.01 field, 66 multiple) 
   17  Internal Entry Number (IEN) 
   18  Effective date (.01 field, 66 multiple) 
   19  Reference (field #900) 
   20  Weight (Non Affil) (field #7) 
   21  Weight (Int Affil) (field #7.5) 
   22  Message 
    
    or 
    
   -1^Error Description 
  
COMPONENT/ENTRY POINT: $$DRGD(CODE,ARY,CDT)
 COMPONENT DESCRIPTION:   Returns an unformatted DRG Description.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   ICD Code, Internal or External Format (required) 
  
VARIABLES: ARY                          TYPE: Both
 VARIABLES DESCRIPTION:   Input:   Name of Output Array for description 
               
   e.g. "ABC" or "ABC("TEST")" 
            
   Default = ^TMP("DRGD",$J) 
  
 Output:  Description in array 
         
    @ARY(1:n) - Description (lines 1-n) 
    @ARY(n+1) - Blank 
    @ARY(n+1) - Warning Message 
    
      or 
    
    -1^Error Description 
    
 NOTE:  
  
    User must initialize ^TMP("DRGD",$J) 
    if used.  The data is place in the 
    array unformatted, exactly as it is in 
    the DESCRIPTION multiple (sub-files 
    #80.068 or #80.168) 
  
 SEE ALSO: 
  
    $$DRGDES^ICDEX(IEN,CDT,.ARY,LENGTH) to 
    retrieve the description formatted into 
    string lengths specified by input 
    parameter for length.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Date to screen against (default = TODAY) 
              
    If CDT < 10/1/1978, use 10/1/1978 
    If CDT > DT, use DT 
    If CDT = year only, use 01/01/yyyy 
    If CDT = year & month, use mm/01/yyyy 
  
VARIABLES: $$DRGD                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of lines in description output
 array.  
  
COMPONENT/ENTRY POINT: $$DRGDES(IEN,CDT,ARY,LEN)
 COMPONENT DESCRIPTION:   This API returns the DRG Description formatted into 
 string lengths specified by the calling application.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number of DRG file 80.2 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Date to screen against (default = TODAY) 
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is a local array passed by reference containing
 the DRG description.  The text is formatted into string lengths specified by
 the LEN input parameter.  
  
VARIABLES: LEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Length of line of the description in the output array 
  
    Missing        Defaults to 79 
    Less than 25   Defaults to 25 
  
VARIABLES: $$DRGDES                     TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of lines in description output
 array.  
  
COMPONENT/ENTRY POINT: $$DRGN(CODE)
 COMPONENT DESCRIPTION:   This API returns the Internal Entry Number (IEN) of
 the DRG specified by a DRG code.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a DRG code.  
  
VARIABLES: $$DRGN                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the IEN of the DRG code specified.  
  
COMPONENT/ENTRY POINT: $$EFD(X)
 COMPONENT DESCRIPTION:   This is an interactive API that will prompt the user
 for an effective date in a range of dates.  
  
VARIABLES: $$EFD                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a 3 piece "^" delimited string containing an
 effective date in both internal and external formats: 
    
    1   Date Fileman format         nnnnnnn 
    2   Date External Short Format  mm/dd/yyyy 
    3   Date External Long Format   Mmm dd, yyyy 
  
 or 
    "^^" if the user enters double up-arrows 
    "^"  if the user enters a single up-arrow 
    ""   if the user times out 
  
 The earliest possible date is Oct 1, 1978, the initial ICD implementation date
 in the VA.  
  
 If today's date is less than the implementation date of ICD-10, then the
 latest possible date is 3 years from the ICD-10 implementation date.  
  
 If today's date is greater than the implementation date of ICD-10, then the
 latest possible date is 3 years from today's date.  
  
COMPONENT/ENTRY POINT: $$GETDATE(IEN)
 COMPONENT DESCRIPTION:   This API calculates the Effective Date to use
 retrieving ICD/DRG data based on a patient's treatment.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number of the PTF file #45 
  
VARIABLES: $$GETDATE                    TYPE: Output
 VARIABLES DESCRIPTION:   This is the correct "EFFECTIVE DATE" for a patient to
 be used retrieving DRG/ICD/CPT data (default TODAY) 
    
 "EFFECTIVE DATE" Derived from: 
  
   Census Date      ^DGPT         0;13 
   Discharge Date   ^DG(45.86     0;1 
   Surgery Date     ^DGPT(D0,"S"  0;1 
   Movement Date    ^DGPT(D0,"M"  0;10 
   Default          $$NOW^XLFDT 
  
COMPONENT/ENTRY POINT: $$IA(FILE,IEN)
 COMPONENT DESCRIPTION:   This API returns an codes Initial Activation Date
 based on a file number and the codes Internal Entry Number.  The Initial
 Activation date may be different from the Last Activation date (see $$LA) if
 the code was re-used.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a Global Root or File Number for either the
 ICD Diagnosis or ICD Procedure files (Required) 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the
 specified file (Required) 
  
VARIABLES: $$IA                         TYPE: Output
 VARIABLES DESCRIPTION:   Initial Activation Date 
  
 OR 
  
 -1 ^ Error Message 
  
COMPONENT/ENTRY POINT: $$IDSTR(FILE,IEN)
 COMPONENT DESCRIPTION:   This API returns a string of ICD identifier 
 associated with either an ICD Diagnosis or ICD Procedure code (supports legacy
 APIs) 
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   File Number or root (required) 
  
     80 or ^ICD9     = File #80 
     80.1 or ^ICD0   = File #80.1 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a Diagnosis/Procedure code IEN (required) 
  
VARIABLES: $$IDSTR                      TYPE: Output
 VARIABLES DESCRIPTION:   This is a string of Identifiers delimited by a
 semi-colon 
    
    ID;ID;ID 
  
COMPONENT/ENTRY POINT: $$ISVALID(FILE,IEN,CDT)
 COMPONENT DESCRIPTION:   This API determine is an ICD code is valid.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a file number or global root for either the
 ICD Diagnosis file or the ICD Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file
 specified.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the date to use to determine if the code is
 valid for date (default TODAY) 
  
VARIABLES: $$ISVALID                    TYPE: Output
 VARIABLES DESCRIPTION:   This is a Boolean value 
  
    1 if the code is valid 
    0 if the code is not valid 
  
COMPONENT/ENTRY POINT: $$PDXE(IEN)
 COMPONENT DESCRIPTION:   This API returns the Primary Diagnosis Exclusion
 Code.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) for the ICD
 Diagnosis file #80 
  
VARIABLES: $$PDXE                       TYPE: Output
 VARIABLES DESCRIPTION:   This is a pointer to DRG CC Exclusions file #82.13 
  
COMPONENT/ENTRY POINT: $$REF(IEN,CDT)
 COMPONENT DESCRIPTION:   This API returns the name of the DRG Reference Table. 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) of the DRG
 file #80.2 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Effective date to use (default TODAY) 
  
VARIABLES: $$REF                        TYPE: Output
 VARIABLES DESCRIPTION:   Table reference associated with a DRG entry or null
 if not found 
  
COMPONENT/ENTRY POINT: $$VCCP(IEN,CDT,FMT)
 COMPONENT DESCRIPTION:   This API returns the CC Primary Flag for a diagnosis. 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the ICD
 Diagnosis file 80 (required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the date to use to Extract CC Primary Flag
 (default TODAY) 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   Is is a flag to determine the output format
 (optional): 
  
  0 = CC Primary Flag only (default) 
  1 = CC Prim Flag^Effective Date^Value 
  
VARIABLES: $$VCCP                       TYPE: Output
 VARIABLES DESCRIPTION:   This the CC Primary Flag in one of two formats: 
  
   CC Primary Flag only (FMT=0) 
   CC Primary Flag^Effective Date^Value  (FMT=1) 
  
COMPONENT/ENTRY POINT: $$DRGW(IEN)
 COMPONENT DESCRIPTION:   This API returns the DRG Weighted Work Unit (WWU) 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) of the DRG
 file 80.2 
  
VARIABLES: $$DRGW                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the Weighted Work Unit (WWU) for a DRG 
  
COMPONENT/ENTRY POINT: $$DRGC(IEN)
 COMPONENT DESCRIPTION:   This API returns the DRG code.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) of the DRG
 file 80.2 
  
VARIABLES: $$DRGC                       TYPE: Output
 VARIABLES DESCRIPTION:   This is a DRG Code (field .01) 
  
COMPONENT/ENTRY POINT: $$MDCN(IEN)
 COMPONENT DESCRIPTION:   This API returns the name of a Major Diagnostic
 Category (MDC) 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Internal Entry Number (IEN) for file 80.3 
  
VARIABLES: $$MDCN                       TYPE: Output
 VARIABLES DESCRIPTION:   This is a Major Diagnostic Category Name 
  
COMPONENT/ENTRY POINT: $$HDR(FILE)
 COMPONENT DESCRIPTION:   This API returns the header node of either file 80 or
 80.1.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a File Number or Global Root 
  
    80    or  ^ICD9( 
    80.1  or  ^ICD0( 
  
VARIABLES: $$HDR                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the header node of either the ICD Diagnosis
 file 80 or the Operation Procedure file 80.1 
  
   ^ICD9(0) 
   ^ICD0(0) 
  
COMPONENT/ENTRY POINT: $$IEN(CODE,ROOT,SYS)
 COMPONENT DESCRIPTION:   This API returns an internal entry number for a code
 based on file/global root and coding system.  
  
 This API is similar to $$CODEABA^ICDEX except it will also return IENs for
 codes excluded from lookup and VA Local Codes.  Its primary purpose to to
 support file maintenance.  Use with great caution.  
  
 DO NOT USE in any application that requires codes and text to be versioned
 (date sensitive).  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD Diagnosis or Procedure Code from
 either the ICD-9 or ICD-10 coding systems (required) 
  
VARIABLES: ROOT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a file number or global root (optional) 
  
    ^ICD9( or 80 
    ^ICD0( or 80.1 
  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a coding system (optional) 
  
   1 = ICD-9 Diagnosis 
   2 = ICD-9 Procedure 
  30 = ICD-10 Diagnosis 
  31 = ICD-10 Procedure 
  
VARIABLES: $$IEN                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns the Internal Entry Number (IEN) for a CODE or
 -1 if not found 
  
COMPONENT/ENTRY POINT: $$SDH(FILE,IEN,ARY)
 COMPONENT DESCRIPTION:   This API returns a history of Short Description 
 changes by date.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD file number: 
                                
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file 
 specified.  
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a local array name passed by reference that
 will contain the code's short description history.  
  
VARIABLES: $$SDH                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a three piece "^" delimited string
 containing: 
  
   1   The number of short descriptions found 
   2   The earliest date found 
   3   The latest date found 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   This is a local array containing a history of Short
 Descriptions by date: 
    
    ARY(0)= # ^ Earliest Date ^ Latest Date 
    ARY(DATE)=Long Description 
  
COMPONENT/ENTRY POINT: $$LDH(FILE,IEN,ARY)
 COMPONENT DESCRIPTION:   This API returns a history of Long Description 
 changes by date.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an ICD file number: 
                                
     80   = ICD Diagnosis file 
     80.1 = ICD Operation/Procedure file 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number (IEN) in the file
 specified.  
  
VARIABLES: .ARY                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a local array name passed by reference that
 will contain the code's long description history.  
  
VARIABLES: $$LDH                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a three piece "^" delimited string
 containing: 
  
   1   The number of long descriptions found 
   2   The earliest date found 
   3   The latest date found 
  
 OR -1 ^ Error Message 
  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   This is a local array containing a history of Long
 Descriptions by date: 
    
    ARY(0)= # ^ Earliest Date ^ Latest Date 
    ARY(DATE)=Long Description 
  
COMPONENT/ENTRY POINT: $$POAE(IEN)
 COMPONENT DESCRIPTION:   This API checks to see if a Diagnosis Code is exempt
 from Present on Admission (Added in ICD*18.0*67) 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number for file 80 
  
VARIABLES: $$POAE                       TYPE: Output
 VARIABLES DESCRIPTION:   Boolean value 
  
 0  No, Diagnosis Code is not exempt for POA 1  Yes, Diagnosis Code is exempt
 for POA 
  
COMPONENT/ENTRY POINT: $$HAC(IEN)
 COMPONENT DESCRIPTION:   This API checks to see if a Diagnosis Code is a 
 Hospital Acquired Condition (Added in ICD*18.0*67) 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number for file 80 
  
VARIABLES: $$HAC                        TYPE: Output
 VARIABLES DESCRIPTION:   Boolean value 
  
 0  No, Diagnosis Code is not a Hospital 
    Acquired Condition 1  Yes, Diagnosis Code is a Hospital 
    Acquired Condition 
  
COMPONENT/ENTRY POINT: $$RDX(CODE,CDT)
 COMPONENT DESCRIPTION:   This API attempts to resolve a code fragment to a
 code.  It will return -1 with an error message if it fails.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Code or Code Fragment (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Versioning Date (Optional, Default TODAY) 
  
VARIABLES: $$RDX                        TYPE: Output
 VARIABLES DESCRIPTION:   ICD Diagnosis code from fragment if it can be
 resolved.  -1 ^ error message if not resolved 
    
 Example: 
    
    Input                   Output 
    Fragment    Oct 1, 2014        Oct 1, 2015 
    --------    ------------------------------
    E8310         E831.0              E83.10 
    311           311.                311.  
    A870          A87.0               A87.0 
    A0201         -1^Could not resolve code fragment 
  
SUBSCRIBING PACKAGE: LEXICON UTILITY
 SUBSCRIBING DETAILS:   The LEXICON UTILITY has access to all APIs listed in
 this ICR as if it were the Custodial Package.  
  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   ACCOUNT RECEIVABLE (PRCA) package will use the
 following APIs: 
  
   $$CODEC^ICDEX 
   $$CODECS^ICDEX 
  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   INTEGRATED BILLING (IB) will use the following APIs: 
    
   $$SYS^ICDEX 
   $$CODEABA^ICDEX 
   $$STATCHK^ICDEX 
   $$ICDDX^ICDEX 
   $$ICDOP^ICDEX 
   $$LS^ICDEX 
   $$CODEC^ICDEX, Effective with IB*2.0*709 
SUBSCRIBING PACKAGE: FEE BASIS
 SUBSCRIBING DETAILS:   FEE BASIS (FB) package will use the following APIs: 
    
   $$GETDRG^ICDEX 
   $$STATCHK^ICDEX 
   $$CODEC^ICDEX 
   $$CODEABA^ICDEX 
   $$CODEN^ICDEX 
   $$SD^ICDEX 
  
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   PROSTHETICS (RMPR) will use the following APIs: 
    
   $$SINFO^ICDEX 
   $$CSI^ICDEX 
   $$STATCHK^ICDEX 
   $$ICDDX^ICDEX 
   $$VLT^ICDEX 
   $$LS^ICDEX 
   $$CODEC^ICDEX 
  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   SCHEDULING (SD) will use the following APIs: 
    
   $$IMP^ICDEX 
   $$CSI^ICDEX 
   $$VER^ICDEX 
   $$SYS^ICDEX 
   $$LS^ICDEX 
   $$ICDDX^ICDEX 
   $$VLTD^ICDEX 
   $$CODEC^ICDEX, effective with SD*5.3*851 
   $$STATCHK^ICDEX, effective with SD*5.3*853 
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   REGISTRATION (DG) will use the following APIs: 
    
   $$CSI^ICDEX 
   $$CODEC^ICDEX 
   $$CODEN^ICDEX 
   $$CODEABA^ICDEX 
   $$LS^ICDEX 
   $$NOT^ICDEX 
   $$REQ^ICDEX 
   $$SYS^ICDEX 
   $$VLT^ICDEX 
   $$SINFO^ICDEX 
   $$CS^ICDEX 
   $$ICDDX^ICDEX 
   $$VST^ICDEX 
  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   CLINICAL REMINDERS (PXRM) will use the following APIs: 
    
   $$CODEN^ICDEX 
   $$CODEABA^ICDEX 
   $$ICDDX^ICDEX 
   $$ICDOP^ICDEX 
   $$NEXT^ICDEX 
   $$PREV^ICDEX 
   $$IMP^ICDEX 
   $$ROOT^ICDEX 
   $$HDR^ICDEX 
   $$CODEC^ICDEX 
   $$CSI^ICDEX 
   $$SINFO^ICDEX 
  
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
 SUBSCRIBING DETAILS:   PHARMACY BENEFITS MANAGEMENT (PSU) will use the
 following APIs: 
    
   $$CSI^ICDEX 
   $$ICDDX^ICDEX 
   $$ICDOP^ICDEX 
  
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
 SUBSCRIBING DETAILS:   CLINICAL CASE REGISTRIES (ROR) will use the following
 APIs: 
    
   $$CSI^ICDEX 
   $$VSEX^ICDEX 
   $$UPDX^ICDEX 
   $$CODEC^ICDEX 
   $$CODEABA^ICDEX 
   $$VSTD^ICDEX 
   $$VLTD^ICDEX 
   $$VSTP^ICDEX 
   $$VLTP^ICDEX 
   $$FILE^ICDEX 
   $$VLT^ICDEX 
   $$VST^ICDEX 
   $$CODEN^ICDEX 
   $$ICDDX^ICDEX 
   $$ICDOP^ICDEX 
   $$SNAM^ICDEX 
   $$OBA^ICDEX 
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
 SUBSCRIBING DETAILS:   CLINICAL PROCEDURES (MD) and MEDICINE (MC) will use the
 following APIs: 
    
   $$ICDDX^ICDEX 
   $$CSI^ICDEX 
   $$IMP^ICDEX 
   $$SINFO^ICDEX 
   $$CODEN^ICDEX 
   $$CODEC^ICDEX 
   $$CODECS^ICDEX     
SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION
 SUBSCRIBING DETAILS:   SPINAL CORD DYSFUNCTION (SPN) package will use the
 following APIs: 
    
   $$OBA^ICDEX 
   $$CODEBA^ICDEX 
   $$CSI^ICDEX 
   $$CODEABA^ICDEX 
   $$VLT^ICDEX 
   $$VST^ICDEX 
  
SUBSCRIBING PACKAGE: HOME BASED PRIMARY CARE
 SUBSCRIBING DETAILS:   HOSPITAL-BASED HOME CARE (HBH) will use the following
 APIs: 
    
   $$SYS^ICDEX 
   $$CODEC^ICDEX 
   $$VSTD^ICDEX 
   $$SAI^ICDEX 
   $$CSI^ICDEX 
  
SUBSCRIBING PACKAGE: EVENT CAPTURE
 SUBSCRIBING DETAILS:   EVENT CAPTURE (EC) package will use the following APIs: 
    
   $$SINFO^ICDEX 
   $$ICDDX^ICDEX 
   $$CODEN^ICDEX 
  
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
 SUBSCRIBING DETAILS:   AUTOMATED INFO COLLECTION SYS (IBD) package will use
 the following APIs: 
    
   $$SINFO^ICDEX 
   $$STATCHK^IDEX 
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   LAB SERVICES (LR) will use the following APIs: 
    
   $$CODEC^ICDEX 
   $$ICDDX^ICDEX 
   $$ICDOP^ICDEX 
   $$IMP^ICDEX 
   $$SINFO^ICDEX 
   $$CSI^ICDEX 
   $$SD^ICDEX 
   $$SNAM^ICDEX 
   $$CODEN^ICDEX 
  
SUBSCRIBING PACKAGE: QUASAR
 SUBSCRIBING DETAILS:   QUASAR (ACKQ) will use the following APIs: 
    
   $$CODEC^ICDEX 
   $$CSI^ICDEX 
   $$CODEN^ICDEX 
  
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   EMERGENCY DEPARTMENT (EDP) package will use the
 following APIs: 
    
   $$ICDDX^ICDEX 
   $$ICDOP^ICDEX 
   $$CODEC^ICDEX 
   $$LD^ICDEX     Added 1/25/22: Effective EDP*2*16 
SUBSCRIBING PACKAGE: PROBLEM LIST
 SUBSCRIBING DETAILS:   PROBLEM LIST (GMPL) will use the following APIs: 
    
   $$CODEC^ICDEX 
   $$CSI^ICDEX 
   $$SAB^ICDEX 
  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   PATIENT CARE ENCOUNTER - PCE (PX) will use the
 following APIs: 
    
   $$CODEC^ICDEX 
   $$CODEN^ICDEX 
   $$CSI^ICDEX 
   $$SINFO^ICDEX 
   $$LD^ICDEX 
   $$IE^ICDEX 
   $$ICDDX^ICDEX 
   $$CODEABA^ICDEX 
  
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   MENTAL HEALTH (YS) will use the following APIs: 
    
   $$SINFO^ICDEX 
  
SUBSCRIBING PACKAGE: SURGERY
 SUBSCRIBING DETAILS:   SURGERY (SR) package will use the following APIs: 
  
   $$CODEN^ICDEX 
   $$LS^ICDEX 
   $$SYS^ICDEX 
   $$VST^ICDEX 
   $$CODEABA^ICDEX 
   $$OBA^ICDEX 
   $$CSI^ICDEX 
   $$CODEC^ICDEX 
  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   ORDER ENTRY/RESULTS REPORTING (OR) will use the
 following APIs: 
  
   $$CODECS^ICDEX 
   $$CSI^ICDEX 
   $$SAB^ICDEX 
   $$VLTD^ICDEX 
   $$CODEBA^ICDEX 
   $$ICDDX^ICDEX effective 7/7/25 with OR*3.0*634 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   TEXT INTEGRATION UTILITIES (TIU) will use the following
 APIs: 
  
   $$CODECS^ICDEX 
  
SUBSCRIBING PACKAGE: VBECS
 SUBSCRIBING DETAILS:   BLOOD BANK (VBEC) will use the following APIs: 
    
   $$ICDDX^ICDEX 
   $$ICDOP^ICDEX 
  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) (VPS) will use the
 following APIs: 
  
   $$SAB^ICDEX 
  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   HEALTH SUMMARY (GMTS) will use the following APIs: 
   
    $$CSI^ICDEX 
    $$CODEC^ICDEX 
    $$SNAM^ICDEX 
    $$VST^ICDEX 
  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   VIRTUAL PATIENT RECORD (VPR) will use the following
 APIs: 
     
     $$ICDDX^ICDEX 
     $$CODEC^ICDEX 
     $$VSTD^ICDEX 
     $$VLTD^ICDEX 
     $$CSI^ICDEX 
     $$SAB^ICDEX 
   
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Enterprise Health Mgmt Platform (HMP) will be using the
 following APIs: 
  
   $$ICDDX^ICDEX 
   $$CODEC^ICDEX 
   $$ICDD^ICDEX 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   GMRC will use the following API: 
  
 $$CODECS^ICDEX $$CODEN^ICDEX 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
 SUBSCRIBING DETAILS:   FEE BASIS CLAIMS SYSTEM (FBCS) will use the following
 APIs: 
   
   $$LKTX^ICDEX 
   $$SYS^ICDEX 
   $$ICDDX^ICEDX 
   $$CODEC^ICDEX 
   $$LD^ICDEX 
   $$IMP^ICDEX 
   $$ICDOP^ICDEX 
   $$CODEABA^ICDEX 
    
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   Dental Record Manager Plus has requested to add Dental
 as a subscriber.  
   
  
 Dental will utilize the following APIs: 
  
    $$ICDDX^ICDEX 
    $$CODEN^ICDEX 
    $$CODEC^ICDEX 
    $$STATCHK^ICDEX 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Advanced Prosthetics Acquisition Tool (APAT) has
 requested to be added as a subscriber.  
  
 APAT will utilize the following APIs: 
  $$CSI^ICDEX 
  $$ICDDX^ICDEX 
  $$INFO^ICDEX 
  DATE ACTIVATED: JUL 11, 2014

NUMBER: 5748                            IA #: 5748
  FILE NUMBER: 704.101                  GLOBAL ROOT: MDC(704.101,
  DATE CREATED: NOV 16, 2011            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CLIO TERM FILE
  ID: MDC(704.101,
GLOBAL REFERENCE: MDC(704.101,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ID 
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: TERM
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: ABBREVIATION
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: DISPLAY NAME
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: TERM TYPE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: DATA TYPE
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Allows access to nationally released indices on these
 fields as well.  
GLOBAL REFERENCE: MDC(704.101,D0,VUID)
FIELD NUMBER: 99.99                     FIELD NAME: VUID
  LOCATION: VUID;1                      ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CLIO
KEYWORDS: MDC
KEYWORDS: CP
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
  DATE ACTIVATED: MAR 26, 2013

NUMBER: 5749                            IA #: 5749
  GLOBAL ROOT: DD(                      DATE CREATED: NOV 30, 2011
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Updating DD 'VR' Nodes          ID: DD(
GLOBAL REFERENCE: DD(FILE,0,'VR')
GLOBAL REFERENCE: DD(FILE,0,'VRPK')
GLOBAL REFERENCE: DD(FILE,0,'VRRV')
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VR
KEYWORDS: DD
KEYWORDS: VRPK
KEYWORDS: VRRV
SUBSCRIBING PACKAGE: LEXICON UTILITY
 SUBSCRIBING DETAILS:   The Lexicon needs to be able to update the DD "VR"
 nodes during data updates.  The Lexicon exports data in the export global
 ^LEXM.  This export global is created by comparing the development account
 with a gold account and recording the changes in ^LEXM in the form of 
 executable SET and KILL statements.  Also recorded are the DD "VR  nodes.  
     
    Example of export global for patch LEX*2.0*80 for file 757.11: 
     
       ^LEXM(757.11,4)=S ^DD(757.11,0,"VR")="2.0" 
       ^LEXM(757.11,5)=S ^DD(757.11,0,"VRPK")="LEX" 
       ^LEXM(757.11,6)=S ^DD(757.11,0,"VRRV")="80^3131001" 
       
    Example of export global for patch ICD*18.0*57 for file 80: 
  
       ^LEXM(80,5391580)=S ^DD(80,0,"VR")="18.0" 
       ^LEXM(80,5391581)=S ^DD(80,0,"VRPK")="ICD" 
       ^LEXM(80,5391582)=S ^DD(80,0,"VRRV")="57^3131001" 
  
 Data installation is done by $ORDERing through the ^LEXM export global and
 executing the MUMPS code found in the global.  When the above export global is
 installed at a site, the version number for file 757.11 is updated to 80 (for
 LEX*2.0*80) and given the effective date of Oct 1, 2013.  The effective date
 is not the date released, it is the date that the data becomes effective, and
 in this case it is the date the ICD-10 data is effective.  
  
 This activity only occurs during the post-install of an ICD, CPT or Lexicon
 KIDS Installation containing data.  It is this method of exporting only the
 changes in a series of SET and KILL statements that allows for the
 distribution of large quantities of data without forcing users off the system. 
  
  DATE ACTIVATED: DEC 07, 2011

NUMBER: 5750                            IA #: 5750
  DATE CREATED: DEC 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQPXRM REMINDERS APPLICABLE
  REMOTE PROCEDURE: ORQQPXRM REMINDERS APPLICABLE
 GENERAL DESCRIPTION:   In support of Capacity Management Tools 3.0, the RPC
 Broker looks for the execution of the ORQQPXRM REMINDERS APPLICABLE remote
 procedure (by RPC name) to measure the load times for CPRS cover sheets loaded
 in the foreground.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RPC BROKER
SUBSCRIBING PACKAGE: VETEXT
 SUBSCRIBING DETAILS:   Added 3/26/25 effective with VTEX*1*0 to support
 getting clinical reminder information for the After Visit Summary (AVS), a
 minor of VEText.  
  DATE ACTIVATED: DEC 07, 2011

NUMBER: 5751                            IA #: 5751
  DATE CREATED: DEC 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQPXRM REMINDERS UNEVALUATED
  REMOTE PROCEDURE: ORQQPXRM REMINDERS UNEVALUATED
 GENERAL DESCRIPTION:   In support of Capacity Management Tools 3.0, the RPC
 Broker looks for the execution of the ORQQPXRM REMINDERS UNEVALUATED remote
 procedure (by RPC name) to measure the load times for CPRS cover sheets loaded
 in the foreground.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RPC BROKER
  DATE ACTIVATED: DEC 07, 2011

NUMBER: 5752                            IA #: 5752
  DATE CREATED: DEC 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQPXRM REMINDER CATEGORIES
  REMOTE PROCEDURE: ORQQPXRM REMINDER CATEGORIES
 GENERAL DESCRIPTION:   In support of Capacity Management Tools 3.0, the RPC
 Broker looks for the execution of the ORQQPXRM REMINDER CATEGORIES remote
 procedure (by RPC name) to measure the load times for CPRS cover sheets loaded
 in the foreground.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RPC BROKER
  DATE ACTIVATED: DEC 07, 2011

NUMBER: 5753                            IA #: 5753
  DATE CREATED: DEC 02, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWCV
  NAME: ORWCV START                     REMOTE PROCEDURE: ORWCV START
  ID: ORWCV
 GENERAL DESCRIPTION:   In support of Capacity Management Tools 3.0, the RPC
 Broker looks for the execution of the ORWCV START remote procedure by tag
 (START) and routine (ORWCV) to measure the load times for CPRS cover sheets
 loaded in the foreground.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: START
SUBSCRIBING PACKAGE: RPC BROKER
  DATE ACTIVATED: DEC 07, 2011

NUMBER: 5754                            IA #: 5754
  FILE NUMBER: 661.1                    GLOBAL ROOT: RMPR(661.1,
  DATE CREATED: DEC 05, 2011            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PROSTHETICS USE OF HCPCS (#.01) FIELD
  ID: RMPR(661.1,
GLOBAL REFERENCE: RMPR(661.1,DA)
FIELD NUMBER: .01                       FIELD NAME: HCPCS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: SHORT NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Provide DSS Extracts access to the PROSTHETIC HCPCS
 (#661.1) File in order to read the HCPCS (#.01) Field record. 
  
 Revised 04/21/23 to add #.02 Code Description field for DSS FY24 Development
 on the Prosthetics Unusual Cost Report.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   On 4/21/23, for the Decision Support System (DSS)
 Sustainment FY24 Development patch, there is a requirement to include the
 HCPCS Code Description field in the Prosthetics Pre-Extract Unusual Cost
 Report. Effective with patch ECX*3*187, DSS accesses the SHORT NAME field
 (#.02) in the PROSTHETICS HCPCS file (#661.1).  
  DATE ACTIVATED: APR 24, 2023

NUMBER: 5755                            IA #: 5755
  FILE NUMBER: 80.4                     GLOBAL ROOT: ICDS(
  DATE CREATED: DEC 24, 2011            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ICD CODING SYSTEMS
  ID: ICDS(
 GENERAL DESCRIPTION:   Lexicon Utility has all privileges as though it were
 the custodial package.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICDS
KEYWORDS: 80.4
KEYWORDS: CODING
KEYWORDS: SYSTEMS
SUBSCRIBING PACKAGE: LEXICON UTILITY
  DATE ACTIVATED: JUL 10, 2014

NUMBER: 5756                            IA #: 5756
  DATE CREATED: DEC 28, 2011
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORUQO
  NAME: CHECK QUICK ORDERS ASSOCIATED WITH ANCILLARY ORDERABLE ITEM
  ID: ORUQO
 GENERAL DESCRIPTION:   The purpose of this Integration Control Agreement is to
 give the Laboratory V5.2 (Lab) system and the Pharmay Data Management V1.0
 system permission to call an Application Programming Interface (API) that will
 check all quick orders associated with a specified orderable item.  
  
 When certain fields (determined by the Lab package) are modified, it might
 affect the way quick orders are used or defined. Lab will call the provided
 API when any of these fields are updated. The API will notify the people at
 the site who are responsible for quick orders of the changes and which quick
 orders need to be reviewed.  
  
 The same is true for Pharmacy. Whenever certain fields are modified 
 (determined by the Pharmacy package), the quick order search will be 
 performed.  
  STATUS: Pending
KEYWORDS: LAB
KEYWORDS: QUICK ORDERS
KEYWORDS: PHARMACY
KEYWORDS: PDM
COMPONENT/ENTRY POINT: CHECKLR
 COMPONENT DESCRIPTION:   This is the entry point for checking Lab changes.  
VARIABLES: OR60                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the file 60 IEN of the entry being changed.  
VARIABLES: OR60N                        TYPE: Input
 VARIABLES DESCRIPTION:   The name (for display purposes) of the item in Lab
 that was modified.  
COMPONENT/ENTRY POINT: CHECKPS
 COMPONENT DESCRIPTION:   This is the entry point for Pharmacy Data Management
 to use to check Pharmacy quick orders.  
VARIABLES: OR507                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the Pharmacy Orderable item that was
 modified.  
VARIABLES: OR507N                       TYPE: Input
 VARIABLES DESCRIPTION:   The name of the Pharmacy Orderable item (for display
 purposes) that was modified.  
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT

NUMBER: 5757                            IA #: 5757
  DATE CREATED: DEC 29, 2011            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Supported                      TYPE: Routine
  ROUTINE: ICDSAPI                      NAME: SEARCH ICD FILES
  ID: ICDSAPI
 GENERAL DESCRIPTION:   Routine ICDSAPI was developed as a wrapper routine for
 DIC lookups during the ICD-10 project to navigate between the ICD-9 Diagnosis
 file 80 and the ICD-10 Diagnosis file 8010 under the two file solution.  The
 two file solution had the ICD-9 codes and ICD-10 codes stored in two separate
 files.  This solution was abandoned in favor of the one file solution where
 both ICD-9 and ICD-10 are stored in the same file (ICD Diagnosis file 80).  A
 one file solution of these APIs can be found in the routine ICDEXLK (ICD Data
 Extraction, special lookup).  Routine ICDSAPI will be exported to support
 applications through the transition between the one and two file solutions. 
 It will be retired 18 months after the ICD-10 compliance date.  
  
  STATUS: Retired                       EXPIRATION DATE: APR 01, 2017
  GOOD ONLY FOR VERSION: 18
KEYWORDS: SEARCH
KEYWORDS: ICDSAPI
COMPONENT/ENTRY POINT: $$SEARCH(FILE,SCR,FMPAR,CDT)
 COMPONENT DESCRIPTION:   This API conducts a search of the ICD files (80 or
 80.1) for a code, a diagnosis or a procedure using Fileman.  This API was
 developed at a time when ICD-10 and ICD-9 codes were in different file (aka,
 the two file solution).  It is being maintained at the request of the calling 
 applications.  Now the ICD-10 and ICD-9 codes are in the same file (aka, the
 one file solution).  While this API still works, a much better option is
 availble using the special lookup routine in file 80 and 80.1.  
  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   This can be either a file number, a file root, a file
 identifier, a coding system or a source abbreviation that can be resolved to a
 file number.  
                         Coding    Source Number   Root     ID    System   
 Abbreviation 
  80     ^ICD9(   DIAG   1 or 30   ICD or 10D 
  80.1   ^ICD0(   PROC   2 or 31   ICP or 10P 
  
VARIABLES: SRC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a string of MUMPS code that is executed to
 screen an entry from selection.  It must contain an IF statement to set the 
 value of $T.  Those entries that the IF statement sets $T to 0 (false) will
 not be displayed or selectable.  
  
VARIABLES: FMPAR                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the Fileman Lookup parameter consisting of a
 string of alphabetic characters which that alter how the lookup responds.
 Default value is "AEMQZ".  DIC(0) will be set to the contents of this
 parameter.  
  
 Parameters applicable to a versioned file 
  
    A   Ask the entry; if erroneous, ask again 
    B   Only the B index is used 
    E   Echo information 
    F   Forget the lookup value 
    I   Ignore the special lookup program 
    M   Multiple-index lookup allowed 
    O   Only find one entry if it matches exactly 
    S   Suppresses display of .01 
    T   Search until user selects or enters ^^ 
    X   EXact match required 
    Z   Zero node in Y(0), external form in Y(0,0) 
    
 Parameters not Applicable to a versioned file and ignored by this lookup 
  
    C   Versioned cross-references not turned off 
    K   Primary Key not established 
    L   Learning a new entry LAYGO not allowed 
    N   Uppercase, IEN lookup allowed (not forced) 
    n   ICD has no pure numeric entries 
    Q   Input is pre-processed, ?? not necessary 
    U   All values are external 
    V   Verification is not optional 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Code Set Versioning Date (Fileman format) 
  
   If supplied only active codes on that date 
   will be included in the selection list.  
  
   If not supplied, the date will default to 
   TODAY and all codes may be selected, active 
   and inactive.  
  
   In both cases the display will be altered 
   based on the date.  
  
VARIABLES: $$SEARCH                     TYPE: Output
 VARIABLES DESCRIPTION:   This is the value of Fileman's Y output variable.  
  
   Y          IEN ^ Code 
               or 
              -1 iF not found 
  
  DATE ACTIVATED: APR 14, 2016

NUMBER: 5758                            IA #: 5758
  DATE CREATED: JAN 03, 2012            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Controlled Subscription        TYPE: Other
  NAME: ICD CODE UPDATE EVENT Protocol
 GENERAL DESCRIPTION:   This protocol is used to notify other applications and
 processes when the ICD-9/10 Code Set is updated.  
  
 This is an extended action protocol.  Applications may attach actions on this
 protocol that should be taken in the event of an ICD update.  
  
 NOTE:  This protocol is commonly invoked by the LEXICAL SERVICES UPDATE
 protocol when there is a change in ICD data.  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ICD
KEYWORDS: UPDATE
KEYWORDS: PROTOCOL
SUBSCRIBING PACKAGE: PROBLEM LIST
 SUBSCRIBING DETAILS:   PROBLEM LIST (GMPL) attaches protocol GMPL SELECTION
 LIST CSV EVENT that generates a mail message containing inactivated ICD codes
 on the selection list.  
  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   CONSULTS (GMRC) attaches protocol ORCM GMRC CSV EVENT
 that generates a mail message consult or procedure quick orders that have an
 inactive ICD code.  
  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   CLINICAL REMINDERS (PXRM) attaches protocol PXRM CODE
 SET UPDATE ICD that generates a mail message containing inactive code in the 
 dialogn file 801.41.  
  

NUMBER: 5759                            IA #: 5759
  DATE CREATED: JAN 04, 2012
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA5759
  STATUS: Pending

NUMBER: 5760                            IA #: 5760
  DATE CREATED: JAN 04, 2012            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PSODDPR5                     NAME: EXCEPTIONS DISPLAYED
  ID: PSODDPR5                          STATUS: Pending
COMPONENT/ENTRY POINT: EXC
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT

NUMBER: 5761                            IA #: 5761
  DATE CREATED: JAN 04, 2012            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PSODDPR2                     NAME: DISPLAY ORDER CHECKS RETURNED
  ID: PSODDPR2                          STATUS: Withdrawn
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT

NUMBER: 5762                            IA #: 5762
  DATE CREATED: JAN 10, 2012
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA5762
  STATUS: Pending

NUMBER: 5763                            IA #: 5763
  DATE CREATED: JAN 10, 2012            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PSJBCMA5                     NAME: GETSIOPI
  ID: PSJBCMA5
 GENERAL DESCRIPTION:   Inpatient Medications has expanded the Special
 Instructions and Other Print Info associated with Inpatient orders to an
 unlimited maximum length. Bar Code Medication Administration (BCMA) requests
 access to the new data via an API that will return the word processing data in
 a ^TMP global node.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PSJBCMA5
KEYWORDS: SPECIAL INSTRUCTIONS
KEYWORDS: OTHER PRINT INFO
COMPONENT/ENTRY POINT: GETSIOPI(DFN,ON,BCMA)
 COMPONENT DESCRIPTION:   This API will return an order's Special Instructions
 if a Unit Dose order is passed in, and it will return an order's Other Print
 Info if an IV order is passed in. 
  
 The unlimited length word processing text will returned in the 
 ^TMP("PSJBCMA5",$J global if the input parameter BCMA evaluates to true. If
 the BCMA input parameter evaluates to false, the text will be returned in
 ^PS(53.45,PSJSYSP, where PSJSYSP is the user's internal entry number from the
 NEW PERSON file.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the patient's internal Internal Entry Number
 (IEN).  
VARIABLES: ON                           TYPE: Input
 VARIABLES DESCRIPTION:   This is the Inpatient Order number, appended with
 appropriate suffix (P=Pending, U=Unit Dose, V=IV).  
VARIABLES: bcma                         TYPE: Input
 VARIABLES DESCRIPTION:   Flag indicating the API is being called from BCMA. If
 it evaluates to TRUE, data will be returned in ^TMP("PSJBCMA5",$J. If it
 evaluates to FALSE, data will be returned in ^PS(53.45,PSJSYSP, where PSJSYSP
 is the user's internal entry number from the NEW PERSON file.  
VARIABLES: PS(53.45,PSJSYSP             TYPE: Output
 VARIABLES DESCRIPTION:   If the BCMA flag is not passed in: 
  Special Instructions data will be returned in ^PS(45,PSJSYSP,5,LINE,0) 
  Other Print Info will be returned in ^PS(53.45,PSJSYSP,6,LINE,0) where
 PSJSYSP is the user's internal entry number from the NEW PERSON file.  
  
 If the BCMA is passed in, nothing will be returned in ^PS(53.45,PSJSYSP.  
VARIABLES: TMP(PSJBCMA5,J               TYPE: Output
 VARIABLES DESCRIPTION:   If the BCMA flag is passed in: 
  
 If a Unit Dose order was passed in, the Special Instructions will be returned
 in ^TMP("PSJBCMA5",$J,DFN,ON,LINE).  
  
 If an IV order was passed in, the Other Print Info will be returned in 
 ^TMP("PSJBCMA5",$J,DFN,ON,LINE).  
  
 DFN is the patient IEN passed in, ON is the order number passed in, LINE is
 the nth line of text.  
  
  
 If the BCMA flag is not passed in, nothing will be returned in 
 ^TMP("PSJBCMA5",$J 
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN

NUMBER: 5764                            IA #: 5764
  DATE CREATED: JAN 12, 2012            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSODGAL1
  NAME: PSODGAL1                        ID: PSODGAL1
 GENERAL DESCRIPTION:   This API displays drug allergy order checks.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PSODGAL1
 COMPONENT DESCRIPTION:   Displays allgery order checks.  
VARIABLES: PSODFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient file (#2) IEN.  
VARIABLES: PSODRUG(IEN)                 TYPE: Input
 VARIABLES DESCRIPTION:   Drug file (#50) IEN.  
VARIABLES: PSODRUG(VA CLASS)            TYPE: Input
 VARIABLES DESCRIPTION:   VA Drug Class name.  
VARIABLES: PSODRUG(NAME)                TYPE: Input
 VARIABLES DESCRIPTION:   Dispense drug name 
VARIABLES: PSODRUG(OI)                  TYPE: Input
 VARIABLES DESCRIPTION:   Dispense drug orderable item IEN 
VARIABLES: PSODRUG(OIN)                 TYPE: Input
 VARIABLES DESCRIPTION:   Dispense drug orderable item name 
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: APR 11, 2012

NUMBER: 5765                            IA #: 5765
  DATE CREATED: JAN 31, 2012            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  NAME: ENTERED IN ERROR                STATUS: Pending

NUMBER: 5766                            IA #: 5766
  DATE CREATED: FEB 13, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWCH LOADSIZ
  REMOTE PROCEDURE: ORWCH LOADSIZ       STATUS: Active
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   DRM Plus, DENT*1.2*59, was experiencing the following
 error when selecting a TIU note title that contains a boilerplate:  An error
 has occurred within the application. Reason: The remote procedure ORWCH
 LOADSIZ is not registered to the option DENTV DSS DRM GUI.   DRM Plus requests
 this new ICR to add this rpc to the dental broker option.  
  DATE ACTIVATED: JUN 12, 2014

NUMBER: 5767                            IA #: 5767
  FILE NUMBER: 120.83                   GLOBAL ROOT: GMRD(120.83,
  DATE CREATED: FEB 15, 2012
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ALLERGY SIGN/SYMPTOMS
  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.  
 D0 is obtained as the first piece from the first piece of 
 ^ORD(100.05,D0,4,D1,3,D2,0).  
 GENERAL DESCRIPTION:   Outpatient Pharmacy and Inpatient Meds packages are
 requesting permission to retrieve Name field (.01) from the SIGN/SYMPTOMS FILE
 (#120.83) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  DATE ACTIVATED: APR 11, 2012

NUMBER: 5768                            IA #: 5768
  FILE NUMBER: 779.004                  GLOBAL ROOT: HL(779.004,
  DATE CREATED: FEB 16, 2012            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: COUNTRY CODE FILE
  ID: HL(779.004,
GLOBAL REFERENCE: HL(779.004,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: HL(779.004,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: VERSION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: HL(779.004,D0,SDS)
FIELD NUMBER: 1.1                       FIELD NAME: NUMERIC CODE
  LOCATION: SDS;1                       ACCESS: Read w/Fileman
FIELD NUMBER: 1.2                       FIELD NAME: FIPS CODE
  LOCATION: SDS;2                       ACCESS: Read w/Fileman
FIELD NUMBER: 1.3                       FIELD NAME: POSTAL NAME
  LOCATION: SDS;3                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: HL(779.004,D0,TERMSTATUS,D1,0)
FIELD NUMBER: .01                       FIELD NAME: EFFECTIVE DATE/TIME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: HL(779.004,D0,VUID)
FIELD NUMBER: 99.99                     FIELD NAME: VUID
  LOCATION: VUID;1                      ACCESS: Read w/Fileman
FIELD NUMBER: 99.98                     FIELD NAME: MASTER ENTRY FOR VUID
  LOCATION: VUID;2                      ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The HL Package grants read-only public access via
 FileMan to the Country Code file (#779.004).  This applies to all fields
 defined in the file. 
  
  
 Please Note: 
  
 Per VHA Directive 2005-044, this file has been "locked down" by Data 
 Standardization (DS).  The file definition (i.e. data dictionary) shall not be 
 modified.  All additions, changes and deletions to entries in the file shall
 be done by Enterprise Reference Terminology (ERT) using the Master File Server 
 (MFS), provided by Common Services (CS).  Creating and/or editing locally 
 defined fields in the file are not permitted.  Use of locally defined fields 
 that were created prior to the VHA Directive's 2005-044 effective date shall 
 not be supported.  
  
 This file is a table of country codes that are used by the Messaging System 
 when building message header segments.  
  
 This file should not be modified locally.  
  
  
  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COUNTRY
  DATE ACTIVATED: APR 16, 2012

NUMBER: 5769                            IA #: 5769
  FILE NUMBER: 102.4                    GLOBAL ROOT: ORA(102.4
  DATE CREATED: FEB 22, 2012            CUSTODIAL PACKAGE: CARE MANAGEMENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ORDER ACKNOWLEDGEMENT FILE
  ID: ORA(102.4
GLOBAL REFERENCE: ORA(102.4,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ORDER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Includes use of the 'B' index 
FIELD NUMBER: 2                         FIELD NAME: PROVIDER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: ACKNOWLEDGED
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This ICR grants VPR permission to read the Order
 Acknowledgement file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP is reading directly from the Order Acknowledgement
 file (#102.4) in order to retrieve information about order acknowledgements. 
 Also using 'B' cross reference.  
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
  DATE ACTIVATED: MAY 09, 2013

NUMBER: 5770                            IA #: 5770
  DATE CREATED: FEB 23, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORQQVI
  NAME: PRE CRCL CALCULATIONS           ID: ORQQVI
 GENERAL DESCRIPTION:   Returns patient height and weight.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: VITAL(VITAL,ABBREV,DFN,.ORY,CNT,F1,F2)
VARIABLES: VITAL                        TYPE: Input
 VARIABLES DESCRIPTION:   Specific vital calling routine interested in.  
VARIABLES: ABBREV                       TYPE: Input
 VARIABLES DESCRIPTION:   Abbreviation of the specific vital calling routine
 interested in.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's ID number 
VARIABLES: CNT                          TYPE: Input
 VARIABLES DESCRIPTION:   Counter for return array 
VARIABLES: F1                           TYPE: Input
 VARIABLES DESCRIPTION:   Start of date range 
VARIABLES: F2                           TYPE: Input
 VARIABLES DESCRIPTION:   End of date range.  
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   The value of the vital the calling routine is
 interested in.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Called from CRCL^PSJLMHED.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Called from CRCL^PSOORUT2.  
  DATE ACTIVATED: JUL 18, 2014

NUMBER: 5771                            IA #: 5771
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100)
  DATE CREATED: FEB 23, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ORDERS FILE DATA
  ID: OR(100)
GLOBAL REFERENCE: OR(100,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ORDER #
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: OBJECT OF ORDER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: CURRENT AGENT/PROVIDER
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DIALOG
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: WHO ENTERED
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: WHEN ENTERED
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 21                        FIELD NAME: START DATE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 22                        FIELD NAME: STOP DATE
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: PATIENT LOCATION
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 23                        FIELD NAME: TO 
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: PATIENT CLASS
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: TREATING SPECIALTY
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 12                        FIELD NAME: PACKAGE
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: EVENT
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,D0,.1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ORDERABLE ITEM
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CHILDREN
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,D0,3)
FIELD NUMBER: 31                        FIELD NAME: DATE OF LAST ACTIVITY
  LOCATION: 3;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: STATUS
  LOCATION: 3;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: REPLACED ORDER
  LOCATION: 3;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9.1                       FIELD NAME: REPLACEMENT ORDER
  LOCATION: 3;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 30                        FIELD NAME: CURRENT ACTION
  LOCATION: 3;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 36                        FIELD NAME: PARENT
  LOCATION: 3;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 35                        FIELD NAME: ALERT ON RESULTS
  LOCATION: 3;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8.1                       FIELD NAME: TYPE
  LOCATION: 3;11                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,D0,4)
FIELD NUMBER: 33                        FIELD NAME: PACKAGE REFERENCE
  LOCATION: 4;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,D0,6)
FIELD NUMBER: 61                        FIELD NAME: NATURE OF DC
  LOCATION: 6;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 62                        FIELD NAME: DC'ed BY
  LOCATION: 6;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 63                        FIELD NAME: DC DATE/TIME
  LOCATION: 6;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 64                        FIELD NAME: DC REASON
  LOCATION: 6;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 68                        FIELD NAME: DC EVENT
  LOCATION: 6;8                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,D0,8,D1,0)
FIELD NUMBER: 3                         FIELD NAME: PROVIDER
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: SIGNATURE STATUS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: SIGNED BY
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: DATE/TIME SIGNED
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: VERIFYING NURSE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: DATE/TIME NURSE VERIFIED
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: VERIFYING CLERK
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: DATE/TIME CLERK VERIFIED
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 12                        FIELD NAME: NATURE OF ORDER
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 13                        FIELD NAME: ENTERED BY
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: RELEASE DATE/TIME
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 17                        FIELD NAME: RELEASING PERSON
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 18                        FIELD NAME: CHART REVIEWED BY
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 19                        FIELD NAME: DATE/TIME CHART REVIEWED
  LOCATION: 0;19                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,D0,4.5,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ITEM ENTRY
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DIALOG
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: INSTANCE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: ID 
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: OR(100,D0,4.5,D1,2,D2,0)
FIELD NUMBER: 2                         FIELD NAME: TEXT
  LOCATION: 2;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Word processing 
GLOBAL REFERENCE: OR(100,D0,8,D1,3)
FIELD NUMBER: 31                        FIELD NAME: FLAGGED
  LOCATION: 3;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This documents data that VPR is reading from the Orders
 file #100.  
  
 Amendments: 
   10/6/22 Added the following fields for VPR subscribing package, 
           effective with VPR*1*30: 
       ^OR(100,D0,0) 
          11  TREATING SPECIALTY 
          15  EVENT              
        ^OR(100,D0,3) 
          8.1 TYPE                 
        ^OR(100,D0,6) 
          61  NATURE OF DC         
          68  DC EVENT   
        ^OR(100,D0,8,D1,0) 
          12  NATURE OF ORDER      
          17  RELEASING PERSON     
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Access to ^OR(100,D0,8 
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Added 11/6/19 for access to WHO ENTERED (field 3) and
 PACKAGE REFERENCE (field 33), effective with RA*5*161.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Updated on 10/29/20 - GMRC package added RESPONSES
 (#100.045) subfile to this ICR to support the 31 Mission Act Decision Support
 Tool, effective with patch GMRC*3.0*154.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Effective with patch TIU*1*290 (CPRS31B).  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 1/11/23 for access to WHO ENTERED (field 3) and
 PACKAGE REFERENCE (field 33), effective with SD*5.3*831.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   Added 2/8/23 effective with GMTS*2.7*145 for access to
 ^OR(100,DA,4) Package Reference(Field 33) corresponding prescription order #
 to get the latest released date as part of generating the CPRS Health Summary, 
 Essential Medication List for Review report.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 2/8/23, effective with DSSV*1.2 to use Field 31.
 DSS Class 2 Product Document only.  
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   ADDED 3/27/25 effective with MECH 1.0 requires Read 
 w/Fileman access to File 100, the STATUS field (#5).  The Medicom ImageX app
 builds a list of existing order based on the STATUS and display details of the
 order, including the STATUS. 
  DATE ACTIVATED: OCT 07, 2022

NUMBER: 5772                            IA #: 5772
  FILE NUMBER: 790.05                   GLOBAL ROOT: WV(790.05)
  DATE CREATED: FEB 23, 2012            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PREGNANCY LOG
  ID: WV(790.05)
GLOBAL REFERENCE: WV(790.05,D0,0
FIELD NUMBER: .01                       FIELD NAME: DATE ENTERED
  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 DESCRIPTION:   Includes the 'C' index 
FIELD NUMBER: .03                       FIELD NAME: PREGNANCY STATUS
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: EDC
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   VPR requests permission to read the WV Pregnancy Log.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
  DATE ACTIVATED: MAY 09, 2013

NUMBER: 5773                            IA #: 5773
  DATE CREATED: FEB 24, 2012            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ICD-9/ICD-10 Lookup
 GENERAL DESCRIPTION:   Applications may conduct Fileman lookups of ICD
 Diagnosis file #80 and the ICD OPERATIONS/PROCEDURE file #80.1 using ^DIC and
 the Special Lookup routine ICDEXLK.  Applications may also point to these
 files.  
  
 A special lookup program was written for the ICD DIAGNOSIS file #80 and ICD
 OPERATION/PROCEDURE file #80.1 to navigate through the versioned (date
 sensitive) data stored in these files.  The Name of the special lookup is
 stored in the Data Dictionary for these files: 
  
      ^DD(80,0,"DIC")="ICDEXLK"                    
      ^DD(80.1,0,"DIC")="ICDEXLK"                    
                          
 Each time an application makes a ^DIC call to either file 80 or 80.1, the
 special lookup routine is invoked, provided the FileMan variable DIC(0) does
 not contain an "I" for "ignore the special lookup." 
  
 NOTE: Only the ^DIC call honors the special lookup routine. Those calls that
 allow the user to specify the indexes (IX^DIC and MIX^DIC1), and the Data Base
 Server calls (FIND^DIC, $$FIND1^DIC, and UPDATE^DIE) all ignore the Special
 Lookup Program.  As a result, the FileMan calls that ignore the Special Lookup
 Program will not be able to conduct versioned searches or return versioned
 data so use IX^DIC, MIX^DIC1 FIND^DIC, and $$FIND1^DIC with a great deal of
 care.  Never use any FileMan entry point that alters the data in these files 
 (i.e., ^DIE, EN^DIB, ^DIK FILE^DIE, UPDATE^DIE and FILE^DICN) 
  
 Package Special Lookup Variables                         
                          
    The following local variables in the ICD namespace should be NEWed 
    or KILLed by the calling application.  The global variables may 
    be used in instances where local environment variables get NEWed 
    and the special lookup values need to be retained.  The calling 
    application is responsible for KILLing the ^TMP global variables.           
         
                          
      Versioning Date (Fileman format) 
  
          ICDVDT or ^TMP("ICDEXLK",$J,"ICDVDT")=<versioning date> 
  
                 If supplied only active codes on that date will be 
                 included in the selection list.  
  
                    1.  V74.6    SCREENING FOR YAWS 
                    2.  V77.5    SCREENING FOR GOUT 
                    3.  V76.9    SCREEN-NEOPLASM NOS 
                    4.  V76.43   SCREEN MAL NEOP-SKIN 
                    5.  V78.8    SCREEN-BLOOD DIS NEC 
  
                 If not supplied, the date will default to TODAY and 
                 all codes may be selected, active and inactive.  
                 
                   1.  V74.6   SCREENING FOR YAWS 
                   2.  V77.5   SCREENING FOR GOUT 
                   3.  V76.8   SCREEN-NEOPLASM NEC (Inactive) 
                   4.  V76.9   SCREEN-NEOPLASM NOS 
                   5.  V76.43  SCREEN MAL NEOP-SKIN 
  
      Coding System (from file 80.4) 
  
          ICDSYS or ^TMP("ICDEXLK",$J,"ICDSYS")=<coding system> 
  
                   1     ICD     ICD-9-CM 
                   2     ICP     ICD-9 Proc 
                  30     10D     ICD-10-CM 
                  31     10P     ICD-10-PCS 
  
                 If supplied only codes belonging to the coding system 
                 will be included in the selection list.               
  
                    S ICDSYS=1,X="DIABETES MELLITUS KETOACIDOSIS" 
  
                    2 matches found 
  
                      1.  249.11  SEC DM KETOACD UNCNTRLD (Major CC) 
                      2.  249.10  SEC DM KETO NT ST UNCNTR (Major CC) 
  
                    S ICDSYS=30,X="DIABETES MELLITUS KETOACIDOSIS" 
  
                    8 matches found          
  
                       1.  E09.11  Drug/chem diabetes mellitus w 
                                   ketoacidosis w coma 
                       2.  E13.11  Oth diabetes mellitus with 
                                   ketoacidosis with coma 
                       3.  E09.10  Drug/chem diabetes mellitus w 
                                   ketoacidosis w/o coma 
                       4.  E10.11  Type 1 diabetes mellitus with 
                                   ketoacidosis with coma 
                       5.  E13.10  Oth diabetes mellitus with 
                                   Ketoacidosis without coma 
                          
                 If not supplied codes from any coding system will be 
                 included in the selection list.  
                          
                     S X="DIABETES MELLITUS KETOACIDOSIS" 
  
                     10 matches found 
  
                       1.  249.11   SEC DM KETOACD UNCNTRLD (Major CC) 
                       2.  249.10   SEC DM KETO NT ST UNCNT (Major CC) 
                       3.  E09.11   Drug/chem diabetes mellitus w 
                                    ketoacidosis w coma 
                       4.  E13.11   Oth diabetes mellitus with 
                                    Ketoacidosis with coma 
                       5.  E09.10   Drug/chem diabetes mellitus w 
                                    ketoacidosis w/o coma 
  
      Display Format (numeric, 1-4) 
  
          ICDFMT or ^TMP("ICDEXLK",$J,"ICDFMT")=<display format> 
  
                  Controls the format of the terms and code presented 
                  for selection on the selection list, 1-4, 
                  default = 1               
  
                  1     Fileman format, code and short text (default) 
      
                        250.00    DMII WO CMP NT ST UNCNTR 
                          
                  2   Fileman format, code and description     
                                        
                        250.00   DIABETES MELLITUS WITHOUT MENTION OF 
                                 COMPLICATION, TYPE II OR UNSPECIFIED 
                                 TYPE, NOT STATED AS UNCONTROLLED 
                       
                  3   Lexicon format, short text followed by code 
                          
                      DMII WO CMP NT ST UNCNTR (250.00) 
                          
                  4   Lexicon format, description followed by code     
                          
                      DIABETES MELLITUS WITHOUT MENTION OF 
                      COMPLICATION, TYPE II OR UNSPECIFIED TYPE, NOT 
                      STATED AS UNCONTROLLED (250.00)     
                          
 Fileman Variables used 
  
   The following are FileMan local variables used by the Special 
   Lookup and should be NEWed or KILLed by the calling application 
                          
      Input                    
                          
      X           (Optional)  User's input.  If it exists, DIC(0) 
                   should not contain "A" for "Ask"               
                      
      DIC         (Required)  The file number or an explicit global 
                   root in the form ^GLOBAL( or ^GLOBAL(X,Y, 
                          
      DIC(0)      (Optional)  A string of alphabetic characters which 
                   alter how DIC responds. At a minimum this string 
                   must be set to null.  (Required) Default value for 
                   ICD files "AEM" 
  
                   The following characters are applicable to a 
                   versioned file               
                          
                        A   Ask the entry; if erroneous, ask again 
                        B   Only the B index is used 
                        E   Echo information 
                        F   Forget the lookup value 
                        I   Ignore the special lookup program     
                        O   Only find one entry if it matches exactly 
                        Q   Question Input ?? 
                        S   Suppresses display of .01 
                        T   Search until user selects or enters ^^ 
                        X   EXact match required 
                        Z   Zero node in Y(0), external form in Y(0,0)       
                          
                   The following characters are NOT applicable to a 
                   versioned file (not used) 
                          
                        C   Versioned cross-references not turned off 
                        K   Primary Key not established 
                        L   Learning a new entry LAYGO not allowed 
                        M   Multiple-index lookup allowed 
                        N   Uppercase, IEN lookup allowed (not forced) 
                        n   ICD has no pure numeric entries 
                        U   All values are external 
                        V   Verification is not optional          
  
      DIC("A")    (Optional) A prompt that is displayed prior to the 
                  reading of the X input. If DIC("A") is not defined, 
                  a prompt will be supplied by the special lookup 
                  routine.  
  
      DIC("B")    (Optional)  The default answer which is presented to 
                  the user when the lookup prompt is issued. If a 
                  terminal user simply presses the Enter/Return key, 
                  the DIC("B") default value will be used, and 
                  returned in X. DIC("B") will only be used if it is 
                  non-null.  
  
      DIC("S")    (Optional)  DIC("S") is a string of M code that DIC 
                  executes to screen an entry from selection. DIC("S") 
                  must contain an IF statement to set the value of $T.  
                  Those entries that the IF sets as $T=0 will not be 
                  displayed or selectable. When the DIC("S") code is 
                  executed, the local variable Y is the internal 
                  number of the entry being screened and the M naked 
                  indicator is at the global level @(DIC_"Y,0)") 
                          
      DIC("W")    (Optional) An M command string which is executed 
                  when DIC displays each of the entries that match the 
                  user's input. The condition of the variable Y and of 
                  the naked indicator is the same as for DIC("S"). 
                  WARNING:  If DIC("W") is defined, it overrides the 
                  display of the versioned identifiers for the file. 
                  Thus, if DIC("W") is set it will suppress the 
                  display of versioned data and there is a risk of 
                  displaying unversioned data.  
                          
      DIC("?N",<file>)=n   (Optional)  The number "n" should be an 
                  integer set to the number of entries to be displayed 
                  on the screen at one time when using "?" help in a 
                  lookup.  
                          
 FileMan Variables not used 
  
      DIC("DR")               
      DIC("PTRIX",<from>,<to>,<file>)               
      DIC("T")               
      DIC("V")               
      DIC("?PARAM",<file>,"INDEX")               
      DIC("?PARAM",<file>,"FROM",<subscript>)               
      DIC("?PARAM",<file>,"PART",<subscript>)               
  
 FileMan Variables KILLed 
  
      DLAYGO               
      DINUM               
                          
 FileMan Variables Modified 
  
      If DIC(0) contains an "L" it will be removed     
  
 Output Variables                    
  
      Always Returned               
                          
           Y          IEN ^ Code               FileMan 
  
      If DIC(0) contains "Z"               
                          
           Y(0)       0 Node                   FileMan 
           Y(0,0)     Code                     FileMan 
           Y(0,1)     $$ICDDX or $$ICDOP       Non-FileMan 
           Y(0,2)     Long Description         Non-FileMan 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICD-9
KEYWORDS: ICD-10
KEYWORDS: ICDEXLK
KEYWORDS: 80
KEYWORDS: 80.1
SUBSCRIBING PACKAGE: 1
 SUBSCRIBING DETAILS:   Fileman calls this Special Lookup routine when the 
 variable DIC(0) does not contain the letter "I" (Ignore Special Lookup).  
  
  DATE ACTIVATED: JUL 11, 2014

NUMBER: 5774                            IA #: 5774
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  NAME: RAD/NUC MED PATIENT file data extract
  STATUS: Withdrawn

NUMBER: 5775                            IA #: 5775
  DATE CREATED: JAN 31, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWTIU GET TIU CONTEXT
  REMOTE PROCEDURE: ORWTIU GET TIU CONTEXT
 GENERAL DESCRIPTION:   Returns the current notes view context for a user.  ICB
 would like to present the same notes context view as CPRS for consistency.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: MAR 13, 2012

NUMBER: 5776                            IA #: 5776
  DATE CREATED: MAR 05, 2012            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: %ZISTCPS
  NAME: LISTEN~%ZISTCPS                 ID: %ZISTCPS
  STATUS: Active
COMPONENT/ENTRY POINT: LISTEN(SOCK,RTN,ZRULE)
VARIABLES: SOCK                         TYPE: Input
 VARIABLES DESCRIPTION:   Socket to listen on 
VARIABLES: RTN                          TYPE: Input
 VARIABLES DESCRIPTION:   Routine to start listener 
VARIABLES: ZRULE                        TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter for additional rules to determine
 when to exit/stop 
SUBSCRIBING PACKAGE: MAILMAN
 SUBSCRIBING DETAILS:   Used to make Mailman GT.M ready and allow the listener
 to be started up on a specific port.  
  DATE ACTIVATED: APR 30, 2012

NUMBER: 5777                            IA #: 5777
  FILE NUMBER: 161                      GLOBAL ROOT: FBAAA(
  DATE CREATED: MAR 05, 2012            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FEE BASIS FILE 161 R
  ID: FBAAA(
GLOBAL REFERENCE: FBAAA(DA,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAA(D0,1,0)
FIELD NUMBER: 1                         FIELD NAME: AUTHORIZATION
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAA(D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: FROM DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: TO DATE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: FEE PROGRAM
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: VENDOR
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: PURPOSE OF VISIT CODE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DX LINE 1
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: .095                      FIELD NAME: TREATMENT TYPE CODE
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: DISCHARGE TYPE
  LOCATION: 0;15                        ACCESS: Read w/Fileman
FIELD NUMBER: .065                      FIELD NAME: PATIENT TYPE CODE
  LOCATION: 0;18                        ACCESS: Read w/Fileman
FIELD NUMBER: .096                      FIELD NAME: ACCIDENT RELATED (Y/N)
  LOCATION: 0;19                        ACCESS: Read w/Fileman
FIELD NUMBER: .097                      FIELD NAME: POTENTIAL COST RECOV
  LOCATION: 0;20                        ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TYPE OF CARE
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 101                       FIELD NAME: PRIMARY SERVICE AREA
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 104                       FIELD NAME: REFERRING PROVIDER
  LOCATION: 0;21                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAA(D0,1,D1,1)
FIELD NUMBER: 3                         FIELD NAME: DATED PRINTED
  LOCATION: 1;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAA(D0,1,D1,2,0)
FIELD NUMBER: .021                      FIELD NAME: AUTHORIZATION REMARKS
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAA(D0,1,D1,2,D2,0)
FIELD NUMBER: .01                       FIELD NAME: AUTHORIZATION REMARK
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAA(D0,1,D1,3)
FIELD NUMBER: .086                      FIELD NAME: DX LINE 3
  LOCATION: 3;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .085                      FIELD NAME: DX LINE 2
  LOCATION: 3;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAA(D0,1,D1,100)
FIELD NUMBER: 100                       FIELD NAME: CLERK
  LOCATION: 100;1                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAA(D0,1,D1,'C')
FIELD NUMBER: 1                         FIELD NAME: PRINT AUTHORIZATION
  LOCATION: 'C';1                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAA(D0,4)
FIELD NUMBER: .5                        FIELD NAME: FEE ID CARD NUMBER
  LOCATION: 4;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .6                        FIELD NAME: FEE ID CARD ISSUE DATE
  LOCATION: 4;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   
    NwHIN Direct accesses the FEE BASIS PATIENT (#161) file to read. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FEE BASIS
KEYWORDS: NwHIN
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
  DATE ACTIVATED: MAR 29, 2012

NUMBER: 5778                            IA #: 5778
  FILE NUMBER: 161.2                    GLOBAL ROOT: FBAAV(
  DATE CREATED: MAR 05, 2012            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FEE BASIS FILE 161.2 R
  ID: FBAAV(
GLOBAL REFERENCE: FBAAV(D0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ID NUMBER
  LOCATION: 1;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: STREET ADDRESS
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 2.5                       FIELD NAME: STREET ADDRESS 2
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: CITY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: STATE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: ZIP CODE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   
    NwHIN Direct accesses the FEE BASIS VENDOR (#161.2) file to read.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FEE BASIS
KEYWORDS: NwHIN
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Added 9/10/26, effective with patch DBVA*2.7*258 CAPRI
 CNH reporting will need to Read W/Fileman field .01 (NAME). 
  DATE ACTIVATED: MAR 29, 2012

NUMBER: 5779                            IA #: 5779
  DATE CREATED: MAR 05, 2012
  CUSTODIAL PACKAGE: NATIONAL HEALTH INFO NETWORK
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: NHIND79C                     NAME: FEE BASIS PUSH_NHIND79C CALL
  ID: NHIND79C
 GENERAL DESCRIPTION:   
      Fee Basis call to PUSH^NHIND79C in order to push abstracted 
      data to NwHIN Direct for the creation of Form 7079.  
  STATUS: Withdrawn                     EXPIRATION DATE: MAR 12, 2012
KEYWORDS: FEE BASIS
KEYWORDS: NwHIN
COMPONENT/ENTRY POINT: PUSH
SUBSCRIBING PACKAGE: FEE BASIS

NUMBER: 5780                            IA #: 5780
  FILE NUMBER: 80.4                     GLOBAL ROOT: ICDS(
  DATE CREATED: MAR 05, 2012            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ICD CODING SYSTEM FILE
  ID: ICDS(
 GENERAL DESCRIPTION:   This is a static file containing information about ICD
 coding systems.  Applications may conduct FileMan lookups and point to this
 file.  
  
 Use the API $$SINFO^ICDEX(IEN) to retrieve the information about an ICD Coding
 System (ICR 5747) 
  
 Applications may not alter or add data to this file.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 80.4
KEYWORDS: ICD
KEYWORDS: CODING
KEYWORDS: SYSTEM
KEYWORDS: ICDS
KEYWORDS: ICDS(
  DATE ACTIVATED: JUL 11, 2014

NUMBER: 5781                            IA #: 5781
  DATE CREATED: MAR 08, 2012            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEXXM
  NAME: Mixed Case                      ID: LEXXM
 GENERAL DESCRIPTION:   This API provides mixed case terminology primarily for
 ICD-10 Lookup. 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MIX
KEYWORDS: LEXXM
KEYWORDS: ICD-10
COMPONENT/ENTRY POINT: $$MIX(TEXT)
 COMPONENT DESCRIPTION:   This API converts text from any form to a modified 
 mix text format.  Example: 
  
 Input:    arthropathy in behcet's syndrome 
           involving other specified sites 
  
 FileMan:  Arthropathy In Behcet's Syndrome 
           Involving Other Specified Sites 
  
 Lexicon:  Arthropathy in Behcet's Syndrome 
           involving other specified sites 
  
 Input:    24 hour esophageal ph study 
  
 FileMan:  24 Hour Esophageal Ph Study 
  
 Lexicon:  24 hour Esophageal pH Study 
  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a text string to be converted to mix text.  
  
VARIABLES: $$MIX                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a string of text in mixed case.  
  
SUBSCRIBING PACKAGE: DRG GROUPER
 SUBSCRIBING DETAILS:   This API is used by the special lookup ICDEXLK* to
 display entries to the user for selection.  
  
  DATE ACTIVATED: JUL 11, 2014

NUMBER: 5782                            IA #: 5782
  DATE CREATED: MAR 13, 2012            CUSTODIAL PACKAGE: PROBLEM LIST
  USAGE: Private                        TYPE: Routine
  ROUTINE: GMPLX1
  NAME: API TO UPDATE PT PROBLEMS WHEN SCT TO ICD MAPPINGS CHANGE
  ID: GMPLX1
 GENERAL DESCRIPTION:   This API supports the updating of patient problems when
 Standards & Terminology Service (STS) updates a mapping between SNOMED CT and 
 ICD-9-CM.  
  
 When a clinician creates a Problem List entry using an unmapped SNOMED CT 
 concept, the entry in the PROBLEM file (#9000011) is saved with the ICD-9-CM
 code 799.9 - OTHER UNKNOWN AND UNSPECIFIED CAUSE OF MORBIDITY OR MORTALITY,
 and a bulletin is sent to STS informing them that an unmapped SNOMED CT
 Concept has be used as a patient problem. STS will find the appropriate
 mapping issued by the National Library of Medicine (NLM) and deploy that
 mapping using NTRT. When the NTRT deployment finishes, the Clinical Lexicon
 application will call SCTMAP^GMPLX1 to update all instances in the PROBLEM
 file where the SNOMED CT concept has been filed with the ICD-9-CM code of
 799.9, replacing the non-specific Diagnosis with the newly mapped ICD-9-CM
 code.  
  
 NOTE: This API will be updated in GMPL*2*42 to accommodate either SNOMED 
 CT-to-ICD-9-CM or SNOMED CT-to-ICD-10-CM mappings.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: SNOMED CT
KEYWORDS: ICD
KEYWORDS: MAPPING
KEYWORDS: PROBLEMS
COMPONENT/ENTRY POINT: SCTMAP
 COMPONENT DESCRIPTION:   The SCTMAP subroutine implements the Application
 Programmers Interface identified by this ICR.  
VARIABLES: GMPSCT                       TYPE: Input
 VARIABLES DESCRIPTION:   SNOMED CT Concept CODE (e.g., 53974002 for Kniest
 Dysplasia).  
VARIABLES: GMPICD                       TYPE: Input
 VARIABLES DESCRIPTION:   ICD-9-CM CODE (as string literal, so that terminal
 0's aren't truncated.  e.g., "428.0" for Congestive Heart Failure).  
VARIABLES: GMPORD                       TYPE: Input
 VARIABLES DESCRIPTION:   Order or sequence (integer) number (starting from 1)
 to accommodate SNOMED CT Concepts with multiple target ICD code mappings
 (e.g., for Diabetic Neuropathy (SNOMED CT 230572002 ICD-9-CM 250.60/355.9) the
 order for 250.60 would be 1, and the order for 355.9 would be 2.  
SUBSCRIBING PACKAGE: LEXICON UTILITY

NUMBER: 5783                            IA #: 5783
  DATE CREATED: MAR 20, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGMSEUTL
  NAME: MILITARY SERVICE EPISODE API    ID: DGMSEUTL
 GENERAL DESCRIPTION:   The HINQ (DVB) application and the Enrollment
 Application System (EAS) have a need to obtain military service episode (MSE)
 data from the PATIENT (#2) file.  This can be accomplished by using the APIs
 in military service episode utility routine, DGMSETUL.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MOVMSE
 COMPONENT DESCRIPTION:   Move MSE data from .32 node to .3216 multiple in
 PATIENT (#2) file.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the PATIENT (#2) file. 
 
COMPONENT/ENTRY POINT: GETMSE
 COMPONENT DESCRIPTION:   Return all records in MSE sub-file #2.3216 in MSE
 array.  Records are sorted in reverse chronological order and the second 
 subscript is the MSE IEN in the multiple  e.g. MSE(1,4)=last 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the PATIENT (#2) file. 
 
VARIABLES: MSE(                         TYPE: Output
 VARIABLES DESCRIPTION:   An array of all MSEs sorted in reverse chronological
 order.  
COMPONENT/ENTRY POINT: LAST
 COMPONENT DESCRIPTION:   Returns the patient's last (most recent) MSE.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the PATIENT (#2) file. 
 
VARIABLES: MSE                          TYPE: Output
 VARIABLES DESCRIPTION:   The most recent MSE for the patient consisting of the 
 0 node of the MILITARY SERVICE EPISODE sub-file #2.3216.  
COMPONENT/ENTRY POINT: ESRDATA
 COMPONENT DESCRIPTION:   Checks if any of the patient's MSEs are verified
 (received from ESR).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the PATIENT (#2) file. 
 
VARIABLES: LOCKED                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns 0 if none of the MSEs are verified.  Returns
 1 if at least one of the MSEs is verified.  
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM
SUBSCRIBING PACKAGE: HINQ
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 4/4/24, documenting historical use of
 GETMSE^DGMSEUTL routine. Additionally, effective with patch VPR*1*35, VPR is
 also using GETMSE^DGMSEUTL to support SDA Patient Container code in the AMPL
 Phase 2 project.  
  DATE ACTIVATED: APR 04, 2024

NUMBER: 5784                            IA #: 5784
  DATE CREATED: MAR 27, 2012            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSODDPR8
  NAME: DBIA 5784 Duplicate Supply Check
  ID: PSODDPR8
 GENERAL DESCRIPTION:   The DBIA documents the API that CPRS can call to do a
 duplicate Supply check against a patient's profile for orders being entered
 through the Pharmacy dialogues in CPRS.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSODDPR8
KEYWORDS: CPRS
KEYWORDS: DUPLICATE SUPPLY CHECK
COMPONENT/ENTRY POINT: CPRS
 COMPONENT DESCRIPTION:   CPRS(PSODFN,PSODSULS,PSODSUOI,PSODSUTY,PSODSUAG) 
VARIABLES: PSODFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: PSODSULS                     TYPE: Input
 VARIABLES DESCRIPTION:   Literal 
VARIABLES: PSODSUOI                     TYPE: Input
 VARIABLES DESCRIPTION:   Orderable Item array in format of PSODSUOI(n)=IEN
 (#50.7) ^ Orderable item name 
VARIABLES: PSODSUTY                     TYPE: Input
 VARIABLES DESCRIPTION:   
  P1;P2 where P1 is dialogue ("I" for IV, U for Unit Dose, "O" for Outpatient,
 "N" for Non-VA Meds (required)), P2=Pharm order# (optional) 
VARIABLES: PSODSUAG                     TYPE: Input
 VARIABLES DESCRIPTION:   If 1, indicates TMP global from CPRS^PSODDPR4 call
 still exists, and add to it 
VARIABLES: TMP($J,DD,PSODSUDC,0)        TYPE: Output
 VARIABLES DESCRIPTION:   This TMP global node is set to provide duplicate drug
 entries to CPRS.  
  
    ^TMP($J,"DD",PSODSUDC,0)=PSODSUII_"^"_PSODSUNN_"^" 
         _$P(^TMP($J,"ORDERS",PS O DSUDM),"^",4) 
         _"^"_$P(^TMP($J,"ORDERS",PSODSUDM),"^",5) 
  
     Where: 
        PSODSUDC = Counter 
        Piece 1 = IEN for DRUG file (#50) 
        Piece 2 = GENERIC NAME field (#.01) 
                    from file DRUG file (#50) 
        Piece 3 = ORDER NUMBER IN OR(100   
        Piece 4 = ORDER NUMBER_";I" 
                  Where ORDER NUMBER can Inpatient 
                          Meds, Non-VA Meds, 
                          Outpatient, etc.  
VARIABLES: TMP($J,PSODSULS,A,B,ON)      TYPE: Output
 VARIABLES DESCRIPTION:   This TMP global is defined to set the prospective
 node for duplicate supply checks for CPRS.  
  
  ^TMP($J,PSODSULS,A,B,ON)=PSOSPRQN_"^"_+PSOSPRID_"^" 
         _PSODSUII_"^"_$G(PSODS U NN) 
  
   Where:  
     PSODSULS = is a literal 
     A = "IN" 
     B = "PROSPECTIVE" 
     ON = unique identifier consisting of: 
          piece 1 = where P1 is dialogue ("I" for 
                    IV, U for Unit Dose, "O" for 
                    Outpatient, "N" for Non-VA 
                    Meds (required)) 
          piece 2 = P2=Pharm order# (optional) 
          piece 3 = "PROSPECTIVE" 
          piece 4 = Counter 
  
     PSOSPRQN = GCNSEQNO field (#11) from VA 
                   PRODUCT file (#50.68) 
     PSOSPRID = VUID field (#99.99) from VA 
                   PRODUCT file (#50.68) 
     PSODSUII = IEN for DRUG file (#50) 
     PSODSUNN = GENERIC NAME field (#.01) 
                   from DRUG file (#50) 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 02, 2012

NUMBER: 5785                            IA #: 5785
  DATE CREATED: MAR 28, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORQPTQ4
  NAME: PRE CRCL VITALS                 ID: ORQPTQ4
 GENERAL DESCRIPTION:   This function returns the age of a patient for use in
 calculating Creatinine Clearance values.  
  STATUS: Active
COMPONENT/ENTRY POINT: AGE
 COMPONENT DESCRIPTION:   S AGE=$$AGE^ORQPTQ4(DFN) Output = age in years 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's internal ID number.  
VARIABLES: VADM(4)                      TYPE: Output
 VARIABLES DESCRIPTION:   Patient's age.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: JUL 23, 2014

NUMBER: 5786                            IA #: 5786
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100
  DATE CREATED: MAR 29, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: ACCESS TO STATUS INFORMATION    ID: OR(100
GLOBAL REFERENCE: OR(100,IFN,3)
FIELD NUMBER: 5                         FIELD NAME: STATUS
  LOCATION: 3;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The purpose of this ICR is to grant Lab access to the
 order status information in the CPRS ORDERS file (#100).  
  
 One usage of this status is in the pending order migration, where speed is of
 the essence, so we are granting direct global read access.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ORDER STATUS
SUBSCRIBING PACKAGE: LAB SERVICE

NUMBER: 5787                            IA #: 5787
  DATE CREATED: APR 03, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORQQLR1
  NAME: CURRENT LAB RESULTS             ID: ORQQLR1
 GENERAL DESCRIPTION:   Returns patient's current laboratory results in an
 array determined by input parameters.  
  STATUS: Active
COMPONENT/ENTRY POINT: LOCL
 COMPONENT DESCRIPTION:   LOCL(DFN,ID,SPEC) ;extrinsic function to return pt's
 most recent lab results for a lab local id in the format: 
  ; test id^abbrev test name^result^units^flag^collection d/t 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's system ID number.  
VARIABLES: LOCL                         TYPE: Output
 VARIABLES DESCRIPTION:   The return value of the extrinsic function to return
 the patient's most recent lab results for a lab local id in the format: test
 id^abbrev test name^result^units^flag^collection d/t 
VARIABLES: LID                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the lab the calling routine is interested
 in 
VARIABLES: SPEC                         TYPE: Input
 VARIABLES DESCRIPTION:   The specific specimin the calling routine is
 interested in getting the results for.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: JUL 18, 2014

NUMBER: 5788                            IA #: 5788
  DATE CREATED: APR 03, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: BT DASHBOARD
 GENERAL DESCRIPTION:   RPC VST1^ORWCV is used by the new Beneficiary Travel
 Dashboard for patient selection 
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL

NUMBER: 5789                            IA #: 5789
  FILE NUMBER: 2006.584                 GLOBAL ROOT: DD(2006.5841
  DATE CREATED: APR 13, 2012            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: Remove PROCEDURE field (#2006.5841,1) as identifier
  ID: DD(2006.5841
 GENERAL DESCRIPTION:   IMAGING to remove PROCEDURE field (#2006.5841,1) as
 identifier: 
  
 K ^DD(2006.5841,0,"ID",1) 
  
 There currently is no other way to remove a field as an identifier.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: FILEMAN
KEYWORDS: IDENTIFIER
SUBSCRIBING PACKAGE: IMAGING

NUMBER: 5790                            IA #: 5790
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: APR 24, 2012            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: LSRP Proxy User in File 200     ID: VA(200
GLOBAL REFERENCE: VA(200,D0,2,0)
FIELD NUMBER: 16                        FIELD NAME: DIVISION
  LOCATION: 2;0                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DIVISION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DEFAULT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   The Lab System Re-engineering Project (LSRP) has a
 requirement that the DIVISION and DEFAULT fields of the NEW PERSON file (#200)
 be defined for the LSRP proxy user LRLAB,AUTOACCEPT at multi-divisional
 facilities.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   The Fileman Read/Write would be for setting/displaying
 the DIVISION and DEFAULT fields for the LRLAB,AUTOACCEPT proxy user.  

NUMBER: 5791                            IA #: 5791
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 30, 2012            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA5791 - Update Field #309 in File #44
  ID: SC(
GLOBAL REFERENCE: SC(D0,S,D1,1
FIELD NUMBER: 309                       FIELD NAME: CHECKED-IN
  LOCATION: C;1                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   To support delivery of the VA Point of Service (VPS
 Kiosks), access to the HOSPITAL LOCATION file (#44) is requested in order to
 update field #309 (CHECKED-IN) via a direct FileMan edit.  This field will be
 updated when a patient executes the CHECK-IN procedure via a Remote Procedure
 call (RPC) at a VA Kiosk.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   Input: a string that represents the appointments to be
 checked in. Each appointment consists of 3 required data elements. Each data
 element for a given appointment is delimited by a "-" and for multiple
 appointments, each one is delimited by a ";".  
  
 The data for the input will be collected after the patient scans his/her VA
 card at the Kiosk. This action will trigger the execution of another RPC (Get
 Patient Demographics) that relies on available APIs to get the information.  
  
 Input Syntax: Input = DFN_"-"_Clinic IEN_"-"_DATE/TIME stamp of scheduled
 appt._";" 
  
 example of data string (represents 2 appointments): 
  "123456-1218-3120420.1215;123456-4569-3120420.1030" 
  
  
 Output Syntax: Single dimensional array that represents the results of each 
 appointment that was checked in. Each data element in the array represents the
 result of an appointment check-in transaction; and the data in the 4-piece
 string is delimited by "-".  
  
 Return value = 1 if check-in was successful or '99-error description text' if
 appointment was not checked in.  
  
 Output Syntax: 
  output(0) = DFN_"-"_Clinic IEN_"-"_DATE/TIME stamp of scheduled 
  appt._"-"_Return value 
                           
  
 Example of data output (example represents the results of 2 checked in appts): 
  
    output(0)="123456-1218-3120420.1215-1" 
    output(1)="123456-4569-3120420.1030-99-Appt not found." 
    
  
 Field #309 (CHECKED-IN) in file #44 will be updated with the current DATE/TIME
 provided the patient has one or more appointment on the current date. FileMan
 will execute the update via a direct call to ^DIE that will not interact with
 the patient (no prompts to the patient will be shown).  
  DATE ACTIVATED: SEP 26, 2012

NUMBER: 5792                            IA #: 5792
  DATE CREATED: APR 30, 2012            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDAM2
  NAME: DBIA5792 - $$FIND call in SDAM2
  ID: SDAM2
 GENERAL DESCRIPTION:   To support delivery of the VA Point of Service (VPS
 Kiosks), access to the API $$FIND^SDAM2() is requested in order to find all
 the appointments for a patient on a given date.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$FIND
VARIABLES: VPSDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   The patient's DFN.  
VARIABLES: VPSDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Date/time for appointment in FileMan internal format. 
 
VARIABLES: VPSCLIN                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the clinic.  
VARIABLES: VPSSCIEN                     TYPE: Output
 VARIABLES DESCRIPTION:   IEN for the patient's appointment (if any).  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   The input data will be 3 required data elements as
 follows: the patient's DFN, date/time of the appointment (FileMan format), and
 the clinic's internal entry number (IEN). The data of the input will be
 collected after the patient scans his/her VA card at the Kiosk. This action
 will trigger the execution of another RPC (Get Patient Demographics) that
 relies on available APIs to get the information.  
  
 Example of data input: 3 variables defined as follows: 
  
    
  VPSDFN   = Patient's IEN from file #2 
  VPSDT    = Date/Time for the appointment 
  VPSCLIN  = IEN of the clinic 
  
  
 Syntax for API call: 
  
  S VPSSCIEN=$$FIND^SDAM2(VPSDFN,VPSDT,VPSCLIN) 
  
  
 Example of data output: 
  
  VPSSCIEN = IEN of the patient's appointment.  
  
  If VPSSCIEN = 0, no appointment was found and the patient is notified.  
  
  If VPSSCIEN > 0, the applicable appointment for that day is 
  passed back, CHECK-IN is completed, and patient is notified. More than 
  one appointment can be checked-in if applicable for the date.  
  DATE ACTIVATED: SEP 26, 2012

NUMBER: 5793                            IA #: 5793
  FILE NUMBER: 53.1                     GLOBAL ROOT: PS(53.1
  DATE CREATED: APR 30, 2012            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Inpatient Medication NON-VERIFIED ORDERS (#53.1) file
  ID: PS(53.1
GLOBAL REFERENCE: PS(53.1,DA,'AD')
FIELD NUMBER: 57                        FIELD NAME: ADDITIVE
  LOCATION: AD                          ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This allows a check for data at the 'AD' Subfile level.  
GLOBAL REFERENCE: PS(53.1,DA,0)
FIELD NUMBER: 49                        FIELD NAME: ORDERS FILE ENTRY
  LOCATION: 0;21                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This allows for read access to the ORDERS FILE ENTRY
 (#49) field.  
 GLOBAL DESCRIPTION:   This also allows a check for data on the '0' node of the
 file.  
 GENERAL DESCRIPTION:   The Outpatient Pharmacy package requests read access to
 the NON-VERIFIED ORDERS (#53.1) file using VA FileMan and direct reads.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PS(53.1
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Requesting read access to specific fields and cross
 references through VA Fileman utilities and direct reads.  
  DATE ACTIVATED: JAN 22, 2018

NUMBER: 5794                            IA #: 5794
  DATE CREATED: MAY 03, 2012            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Private                        TYPE: Remote Procedure
  NAME: PSB VERSION CHECK               REMOTE PROCEDURE: PSB VERSION CHECK
 GENERAL DESCRIPTION:   
  The RPC returns the current and previous version numbers.  
  
  INPUT PARAMETER DESCRIPTION: 
  No input parameters are passed.  
  
  RETURN PARAMETER DESCRIPTION:   
  (0) = Count 
  (1) = Current Gui Version^Previous Gui Version 
  
 Note: Previous GUI version may be blank.   
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PSBRPC3
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 5795                            IA #: 5795
  DATE CREATED: MAY 04, 2012            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Private                        TYPE: Remote Procedure
  NAME: PSB UTL XSTATUS SRCH
 GENERAL DESCRIPTION:   
      Utility to check the latest order activities of a patient.  
  
  INPUT:   
  ^ piece 1 - DFN Patient's Internal Entry Number(required).  
  ^ piece 2 - OrderNumber ON_V/U/P  Inpatient Medications Package V. 
              5.0 Order Number.  
  ^ piece 3 - Action (status) to search for.  
  ^ piece 4 - A Time Frame of "X" followed by a number will indicate the 
              number of administrations to check.  
              A Time Frame set to "FREQ" will use the order's frequency. 
              A Time Frame set to "PRN", "On Call", or "One-Time" will show 
              activity over the past 72 hours by default.  
              A Time Frame value of "Continuous" uses two frequency 
              options.  
                  1. If the frequency is <24 hours use the default of 72 
                     hours.  
                  2. If the frequency is >= 24 hour, look back 3.5 times 
                     the frequency.  
              A Time Frame set to "" and not set to "FREQ" gives no 
              location found during activity error message.  
  
  Example call: D FNDACTV^PSBVDLU3(.results,"1234^1U^H^12") 
  
  RETURN PARAMETER DESCRIPTION: 
  Procedure will return the results to the GUI executable.  
  
  OUTPUT: 
  RESULTS(0)= Returned line count.  
  RESULTS(1)= Patient's location during activity. Free text room-bed and  
              ward location.  
  RESULTS(2)= Medication^ordernumber. Contains the IEN to the actual order 
              in PHARMACY PATIENT (#55) followed by a U for Unit Dose or V 
              for IV.  
  RESULTS(3)= Action fileman date&time.  
  RESULTS(4)= Scheduled administration fileman date&time. If a continuous 
              order, this field will contain the actual administration date 
              and time the medication was ordered for.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PSBVDLU3
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 5796                            IA #: 5796
  DATE CREATED: MAY 04, 2012            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Private                        TYPE: Remote Procedure
  NAME: PSB MAN SCAN FAILURE
 GENERAL DESCRIPTION:   Utility to Manage scanning failures.  Procedure will
 populate the BCMA Unable To Scan Log located in the database ^PSB(53.77) and
 send off MailMan message if necessary.  
  
  INPUT: 
  There is one input parameter with two options: 
  For Wristband scanning failures a single value array PSBPARAM(0).  
  For medication scanning failures a two value array PSBPARAM(0) and 
  PSBPARAM(1).  
  
  PSBPARAM(0): 
  ^ piece 1 - IEN (Patient's Internal Entry Number).  
  ^ piece 2 - Order number (Only used with medication entries, not with the 
              Wristband input).  
  ^ piece 3 - Reason for Unable to Scan.  
  ^ piece 4 - User's Comment. 
  ^ piece 5 - The type of scan event.  
              The value that is placed here is determined by the user's 
              actions when attempting to scan a medication/wristband during 
              an administration. Those types beginning with "M" are 
              events dealing with medications; those beginning with "W" are 
              events with wristbands. "*UAS" occur when the user actually 
              uses the "unable to scan" functionality to document 
              the activity. "*SCN" are types that occur during normal 
              scanning activities.  The "*KEY" designates a type of event 
              where the user has by-passed the BCMA scanning system by 
              "keying", via the system's keyboard device.  
              BCMA input data: 
              "W" for Wristband with a value WSCN, WKEY, or WUAS 
              "M" for Medication with a value of MSCN, MKEY,or MUAS 
  ^ piece 6 - "0" for unable to scan, "1" for keyed entry, or "2" for 
              scanned 
  
  PSBPARAM(1): 
  ^ piece 1 - "DD" Dispense Drug, "ADD" Additive, "SOL" Solution 
  ^ piece 2 - IEN (Internal Entry Number) of failed item 
  
  RETURN PARAMETER DESCRIPTION:   
  There is one parameter returned consisting of two values RESULTS(0) and 
  RESULTS(1).  
  
  OUTPUT: 
  RESULTS(0)=1 
  RESULTS(1)=1 (Successful) 
  or 
  RESULTS(1)="-1^Unable to Scan documentation NOT 
                successful!" (Unsuccessful) 
  or 
  RESULTS(1)="-1^Unable to Scan MAILGROUP NOT SETUP!" (Unsuccessful) 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PSBVDLU3
SUBSCRIBING PACKAGE: WIRELESS MEDICATION ADMIN

NUMBER: 5797                            IA #: 5797
  FILE NUMBER: 41.43                    GLOBAL ROOT: DGS
  DATE CREATED: MAY 07, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA5797 - Update File #41.41 by VPS
  ID: DGS
GLOBAL REFERENCE: DGS(41.41,
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DATE CHANGED
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 2                         FIELD NAME: USER
  LOCATION: 0;3                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   The VA Point of Service (VPS Kiosks) package needs
 access to file #41.41 (Pre-Registration Audit) to update it after a veteran
 has completed his/her pre-registration at a VA kiosk. The fields to be updated
 will be #.01 (PATIENT), #1 (DATE CHANGED), and #2 (USER) via a direct FileMan 
 call to FILE^DICN.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   The input will be individual data elements: PATIENT,
 DATE CHANGED, and USER. Once the data elements pass validation, the file
 #41.41 will be updated.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 3/18/22, effective with patch SD*5.3*809 to both
 update and display the DATE CHANGED (#1) field stored with the
 PRE-REGISTRATION AUDIT PATIENT (#41.41) File.  
  DATE ACTIVATED: NOV 09, 2012

NUMBER: 5798                            IA #: 5798
  FILE NUMBER: 41.43                    GLOBAL ROOT: DGS
  DATE CREATED: MAY 07, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA5798 - Update File #41.43 by VPS
  ID: DGS
GLOBAL REFERENCE: DGS(41.43
FIELD NUMBER: .01                       FIELD NAME: DATE CALLED
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 2                         FIELD NAME: USER
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 3                         FIELD NAME: STATUS
  LOCATION: 0;4                         ACCESS: Write w/Fileman
FIELD NUMBER: 5                         FIELD NAME: DIVISION
  LOCATION: 0;5                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   The VA Point of Service (VPS Kiosks) package needs
 access to file #41.43 (Pre-Registration Call Log) to update it after a veteran
 has completed his/her pre-registration at a VA kiosk. The fields to be updated
 will be #.01 (DATE CALLED), #1 (PATIENT NAME), #2 (USER), #3 (STATUS), and #5 
 (DIVISION) via a direct FileMan to ^DIE.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   The input will be individual data elements: DATE
 CALLED, PATIENT NAME, USER, a one-letter code to represent the status of the
 call ("C" or "X"), and the DIVISION number for the patient. Once the data
 elements have passed validation, the file #41.43 will be updated.  
  DATE ACTIVATED: NOV 09, 2012

NUMBER: 5799                            IA #: 5799
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: MAY 16, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA5799 UPDATE OF FIELDS IN FILE #2
  ID: DPT(
GLOBAL REFERENCE: DPT(DFN,
FIELD NUMBER: .05                       FIELD NAME: MARITAL STATUS
  LOCATION: 0;5                         ACCESS: Write w/Fileman
FIELD NUMBER: .08                       FIELD NAME: RELIGIOUS PREFERENCE
  LOCATION: 0;8                         ACCESS: Write w/Fileman
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: .113                      FIELD NAME: STREE ADDRESS [LINE 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: .117                      FIELD NAME: COUNTY
  LOCATION: .11;7                       ACCESS: Write w/Fileman
FIELD NUMBER: .1171                     FIELD NAME: PROVINCE
  LOCATION: .11;8                       ACCESS: Write w/Fileman
FIELD NUMBER: .1172                     FIELD NAME: POSTAL CODE
  LOCATION: .11;9                       ACCESS: Write w/Fileman
FIELD NUMBER: .1173                     FIELD NAME: COUNTRY
  LOCATION: .11;10                      ACCESS: Write w/Fileman
FIELD NUMBER: .1112                     FIELD NAME: ZIP+4
  LOCATION: .11;12                      ACCESS: Write w/Fileman
FIELD NUMBER: .121                      FIELD NAME: BAD ADDRESS INDICATOR
  LOCATION: .11;16                      ACCESS: Write w/Fileman
FIELD NUMBER: .131                      FIELD NAME: PHONE NUMBER [RESIDENCE]
  LOCATION: .13;1                       ACCESS: Write w/Fileman
FIELD NUMBER: .132                      FIELD NAME: PHONE NUMBER [WORK]
  LOCATION: .13;2                       ACCESS: Write w/Fileman
FIELD NUMBER: .134                      FIELD NAME: PHONE NUMBER [CELLULAR]
  LOCATION: .13;4                       ACCESS: Write w/Fileman
FIELD NUMBER: .133                      FIELD NAME: EMAIL ADDRESS
  LOCATION: .13;3                       ACCESS: Write w/Fileman
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: .1215                     FIELD NAME: TEMPORARY STATE
  LOCATION: .121;5                      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: .12111                    FIELD NAME: TEMPORARY ADDRESS COUNTY
  LOCATION: .121;11                     ACCESS: Write w/Fileman
FIELD NUMBER: .12112                    FIELD NAME: TEMPORARY ZIP+4
  LOCATION: .121;12                     ACCESS: Write w/Fileman
FIELD NUMBER: .1221                     FIELD NAME: TEMPORARY ADDRESS PROVINCE
  LOCATION: .122;1                      ACCESS: Write w/Fileman
FIELD NUMBER: .1222
  FIELD NAME: TEMPORARY ADDRESS POSTAL CODE
  LOCATION: .122;2                      ACCESS: Write w/Fileman
FIELD NUMBER: .1223                     FIELD NAME: TEMPORARY ADDRESS COUNTRY
  LOCATION: .122;3                      ACCESS: Write w/Fileman
FIELD NUMBER: .1219                     FIELD NAME: TEMPORARY PHONE NUMBER
  LOCATION: .121;10                     ACCESS: Write w/Fileman
FIELD NUMBER: .211                      FIELD NAME: K-NAME OF PRIMARY NOK
  LOCATION: .21;1                       ACCESS: Write w/Fileman
FIELD NUMBER: .212                      FIELD NAME: K-RELATIONSHIP TO PATIENT
  LOCATION: .21;2                       ACCESS: Write w/Fileman
FIELD NUMBER: .213                      FIELD NAME: K-STREET ADDRESS [LINE 1]
  LOCATION: .21;3                       ACCESS: Write w/Fileman
FIELD NUMBER: .214                      FIELD NAME: K-STREET ADDRESS [LINE 2]
  LOCATION: .21;4                       ACCESS: Write w/Fileman
FIELD NUMBER: .215                      FIELD NAME: K-STREET ADDRESS [LINE 3]
  LOCATION: .21;5                       ACCESS: Write w/Fileman
FIELD NUMBER: .216                      FIELD NAME: K-CITY
  LOCATION: .21;6                       ACCESS: Write w/Fileman
FIELD NUMBER: .217                      FIELD NAME: K-STATE
  LOCATION: .21;7                       ACCESS: Write w/Fileman
FIELD NUMBER: .2207                     FIELD NAME: K-ZIP+4
  LOCATION: .22;7                       ACCESS: Write w/Fileman
FIELD NUMBER: .219                      FIELD NAME: K-PHONE NUMBER
  LOCATION: .21;9                       ACCESS: Write w/Fileman
FIELD NUMBER: .21011                    FIELD NAME: K-WORK PHONE NUMBER
  LOCATION: .21;11                      ACCESS: Write w/Fileman
FIELD NUMBER: .2191                     FIELD NAME: K2-NAME OF SECONDARY NOK
  LOCATION: .211;1                      ACCESS: Write w/Fileman
FIELD NUMBER: .2192                     FIELD NAME: K2-RELATIONSHIP TO PATIENT
  LOCATION: .211;2                      ACCESS: Write w/Fileman
FIELD NUMBER: .2193                     FIELD NAME: K2-STREET ADDRESS [LINE 1]
  LOCATION: .211;3                      ACCESS: Write w/Fileman
FIELD NUMBER: .2194                     FIELD NAME: K2-STREET ADDRESS [LINE 2]
  LOCATION: .211;4                      ACCESS: Write w/Fileman
FIELD NUMBER: .2195                     FIELD NAME: K2-STREET ADDRESS [LINE 3]
  LOCATION: .211;5                      ACCESS: Write w/Fileman
FIELD NUMBER: .2196                     FIELD NAME: K2-CITY
  LOCATION: .211;6                      ACCESS: Write w/Fileman
FIELD NUMBER: .2197                     FIELD NAME: K2-STATE
  LOCATION: .211;7                      ACCESS: Write w/Fileman
FIELD NUMBER: .2203                     FIELD NAME: K2-ZIP+4
  LOCATION: .22;3                       ACCESS: Write w/Fileman
FIELD NUMBER: .2199                     FIELD NAME: K2-PHONE NUMBER
  LOCATION: .211;9                      ACCESS: Write w/Fileman
FIELD NUMBER: .211011                   FIELD NAME: K2-WORK PHONE NUMBER
  LOCATION: .211;11                     ACCESS: Write w/Fileman
FIELD NUMBER: .331                      FIELD NAME: E-NAME
  LOCATION: .33;1                       ACCESS: Write w/Fileman
FIELD NUMBER: .332                      FIELD NAME: E-RELATIONSHIP TO PATIENT
  LOCATION: .33;2                       ACCESS: Write w/Fileman
FIELD NUMBER: .333                      FIELD NAME: E-STREET ADDRESS [LINE 1]
  LOCATION: .33;3                       ACCESS: Write w/Fileman
FIELD NUMBER: .334                      FIELD NAME: E-STREET ADDRESS [LINE 2]
  LOCATION: .33;4                       ACCESS: Write w/Fileman
FIELD NUMBER: .335                      FIELD NAME: E-STREET ADDRESS [LINE 3]
  LOCATION: .33;5                       ACCESS: Write w/Fileman
FIELD NUMBER: .336                      FIELD NAME: E-CITY
  LOCATION: .33;6                       ACCESS: Write w/Fileman
FIELD NUMBER: .337                      FIELD NAME: E-STATE
  LOCATION: .33;7                       ACCESS: Write w/Fileman
FIELD NUMBER: .2201                     FIELD NAME: E-ZIP+4
  LOCATION: .22;1                       ACCESS: Write w/Fileman
FIELD NUMBER: .339                      FIELD NAME: E-PHONE NUMBER
  LOCATION: .33;9                       ACCESS: Write w/Fileman
FIELD NUMBER: .33011                    FIELD NAME: E-WORK PHONE NUMBER
  LOCATION: .33;11                      ACCESS: Write w/Fileman
FIELD NUMBER: .3311                     FIELD NAME: E2-NAME OF SECONDARY CONTACT
  LOCATION: .331;1                      ACCESS: Write w/Fileman
FIELD NUMBER: .3312                     FIELD NAME: E2-RELATIONSHIP TO PATIENT
  LOCATION: .331;2                      ACCESS: Write w/Fileman
FIELD NUMBER: .3313                     FIELD NAME: E2-STREET ADDRESS [LINE 1]
  LOCATION: .331;3                      ACCESS: Write w/Fileman
FIELD NUMBER: .3314                     FIELD NAME: E2-STREET ADDRESS [LINE 2]
  LOCATION: .331;4                      ACCESS: Write w/Fileman
FIELD NUMBER: .3315                     FIELD NAME: E2-STREET ADDRESS [LINE 3]
  LOCATION: .331;5                      ACCESS: Write w/Fileman
FIELD NUMBER: .3316                     FIELD NAME: E2-CITY
  LOCATION: .331;6                      ACCESS: Write w/Fileman
FIELD NUMBER: .3317                     FIELD NAME: E2-STATE
  LOCATION: .331;7                      ACCESS: Write w/Fileman
FIELD NUMBER: .2204                     FIELD NAME: E2-ZIP+4
  LOCATION: .22;4                       ACCESS: Write w/Fileman
FIELD NUMBER: .3319                     FIELD NAME: E2-PHONE NUMBER
  LOCATION: .331;9                      ACCESS: Write w/Fileman
FIELD NUMBER: .331011                   FIELD NAME: E2-WORK PHONE NUMBER
  LOCATION: .331;11                     ACCESS: Write w/Fileman
FIELD NUMBER: .3111                     FIELD NAME: EMPLOYER NAME
  LOCATION: .311;1                      ACCESS: Write w/Fileman
FIELD NUMBER: .3119                     FIELD NAME: EMPLOYER PHONE NUMBER
  LOCATION: .311;9                      ACCESS: Write w/Fileman
FIELD NUMBER: .31115                    FIELD NAME: EMPLOYMENT STATUS
  LOCATION: .311;15                     ACCESS: Write w/Fileman
FIELD NUMBER: .31116                    FIELD NAME: DATE OF RETIREMENT
  LOCATION: .311;16                     ACCESS: Write w/Fileman
FIELD NUMBER: .251                      FIELD NAME: SPOUSE'S EMPLOYER NAME
  LOCATION: .25;1                       ACCESS: Write w/Fileman
FIELD NUMBER: .258                      FIELD NAME: SPOUSE'S EMP PHONE NUMBER
  LOCATION: .25;8                       ACCESS: Write w/Fileman
FIELD NUMBER: .2515                     FIELD NAME: SPOUSE'S EMPLOYMENT STATUS
  LOCATION: .25;15                      ACCESS: Write w/Fileman
FIELD NUMBER: .2516                     FIELD NAME: SPOUSE'S RETIREMENT DATE
  LOCATION: .25;16                      ACCESS: Write w/Fileman
FIELD NUMBER: .12105                    FIELD NAME: TEMPORARY ADDRESS ACTIVE?
  LOCATION: .121;9                      ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(DFN,.02,
FIELD NUMBER: .01                       FIELD NAME: RACE INFORMATION
  LOCATION: 0;1                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: DPT(DFN,.06
FIELD NUMBER: .01                       FIELD NAME: ETHNICITY INFORMATION
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   To support the delivery of the VA Point of Service (VPS
 Kiosks) project, global access to the PATIENT file (#2) is being requested in
 order to update demographic information for the patient's record. The record
 to be updated will be identified by the internal entry number (DFN) in file
 #2.  New demographic information can result from the execution of the Remote 
 Procedure Call (RPC) "VPS EDIT PATIENT DEMOGRAPHIC" on a VPS kiosk at a local
 VA hospital. The updates to the patient record are performed using Fileman's
 Database Server (DBS) APIs.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
  DATE ACTIVATED: NOV 29, 2012

NUMBER: 5800                            IA #: 5800
  DATE CREATED: MAY 22, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORMLR4
  NAME: MODIFY PACKAGE REFERENCE        ID: ORMLR4
 GENERAL DESCRIPTION:   For Lab Re-engineering, there is a need to break apart
 orders which were combined, such as Sodium and Potassium, to a single lab
 order.  
  
 Therefore, there is a need to be able to update the package reference only.  
  STATUS: Active
KEYWORDS: ORMLR4
KEYWORDS: PACKAGE
KEYWORDS: REFERENCE
KEYWORDS: CPRS
KEYWORDS: LAB
COMPONENT/ENTRY POINT: PKG
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The order number for which you want to change the
 package reference.  
VARIABLES: NEW                          TYPE: Input
 VARIABLES DESCRIPTION:   The new package reference to be used for the
 specified order.  
SUBSCRIBING PACKAGE: LAB SERVICE
  DATE ACTIVATED: FEB 07, 2013

NUMBER: 5801                            IA #: 5801
  FILE NUMBER: 230                      GLOBAL ROOT: EDP
  DATE CREATED: MAY 25, 2012            CUSTODIAL PACKAGE: EMERGENCY DEPARTMENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ED LOG file data extract
  ID: EDP
GLOBAL REFERENCE: EDP('ATO'
 GLOBAL DESCRIPTION:   Cross reference by date/time patient left the emergency
 room.  
GLOBAL REFERENCE: EDP('B'
 GLOBAL DESCRIPTION:   Cross reference by log date/time.  
GLOBAL REFERENCE: EDP('V'
 GLOBAL DESCRIPTION:   Cross reference by visit date/time.  
GLOBAL REFERENCE: EDP(230,D0,0
FIELD NUMBER: .06                       FIELD NAME: PATIENT ID
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   PATIENT ID is a pointer to the PATIENT file (#2).  
GLOBAL REFERENCE: EDP(230,D0,1
FIELD NUMBER: 1.2                       FIELD NAME: DISPOSITION
  LOCATION: 1;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the disposition of the emergency room
 visit and is a pointer to the TRACKING CODE file (#233.1).  
 GENERAL DESCRIPTION:   This integration agreement will allow the DSS package
 to obtain emergency room disposition information to be used in its data
 extracts.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EDIS
KEYWORDS: EMERGENCY
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   The decision support software (DSS) has need to review
 entries in the ED LOG file to determine a patient's disposition from the
 emergency room.  This disposition will then be used when creating entries in
 the admission and clinic extracts within the DSS software.  
  DATE ACTIVATED: AUG 27, 2012

NUMBER: 5802                            IA #: 5802
  FILE NUMBER: 233.1                    GLOBAL ROOT: EDPB(233.1
  DATE CREATED: MAY 25, 2012            CUSTODIAL PACKAGE: EMERGENCY DEPARTMENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TRACKING CODE file data extract
  ID: EDPB(233.1
GLOBAL REFERENCE: EDPB(233.1,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the name of the disposition tracking
 code in an internal format.  
FIELD NUMBER: .02                       FIELD NAME: DISPLAY NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the disposition tracking code in a
 user friendly format.  
 GENERAL DESCRIPTION:   This integration agreement will allow the DSS package
 to obtain emergency room disposition information to be used in its data 
 extracts.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EDIS
KEYWORDS: EMERGENCY
KEYWORDS: DISPOSITION
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   The decision support software (DSS) has a need to
 obtain the patient's disposition from an emergency room visit to use in their
 monthly data extracts.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 12/21/2022, effective with DSSV*1.1 DSS Class 3 
 C3 is reading the .02 field from file 233.1.  
  DATE ACTIVATED: JUL 03, 2012

NUMBER: 5803                            IA #: 5803
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55
  DATE CREATED: MAY 25, 2012
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PHARMACY PATIENT file information for data extract
  ID: PS(55
GLOBAL REFERENCE: PS(55,D0,5,D1,.2
FIELD NUMBER: 120                       FIELD NAME: DOSE
  LOCATION: .2;5                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the DOSE for the UNIT DOSE ordered
 for the specific patient.  
FIELD NUMBER: 121                       FIELD NAME: UNIT
  LOCATION: .2;6                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the specific unit associated with the
 UNIT DOSE order.  
GLOBAL REFERENCE: PS(55,D0,5,D1,2
FIELD NUMBER: 26                        FIELD NAME: SCHEDULE
  LOCATION: 2;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the assigned schedule associated with
 the unit dose order.  
GLOBAL REFERENCE: PS(55,D0,5,D1,9,D2,0
FIELD NUMBER: .01                       FIELD NAME: DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the date/time the activity took place on this
 specific unit dose order.  
FIELD NUMBER: 2                         FIELD NAME: ACTION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field describes the action taken on this specific
 unit dose order.  
 GENERAL DESCRIPTION:   The decision support software (DSS) package had a need
 to obtain specific information related to UNIT DOSE orders.  This information 
 is in a multiple within the PHARMACY PATIENT file (#55).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: UNIT DOSE
KEYWORDS: PHARMACY
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   The DSS package, in support of its data extracts and
 reports, will need to obtain the DOSE, UNIT, and SCHEDULE information from
 within the UNIT DOSE multiple of the PHARMACY PATIENT file.  
  
 The DSS package will also need to obtain the DATE and ACTION fields of the
 ACTIVITY LOG multiple within the UNIT DOSE multiple of the PHARMACY PATIENT
 file (#55).  
  DATE ACTIVATED: JUL 03, 2012

NUMBER: 5804                            IA #: 5804
  DATE CREATED: MAY 25, 2012            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PSBINPT                      NAME: BCMA GUI IV PARAMETERS
  ID: PSBINPT
 GENERAL DESCRIPTION:   Bar Code Medication Administration (BCMA) contains BCMA
 IV Parameters that are used to define the fields that, when edited in
 Inpatient Medications order entry, invalidate previously printed IV labels.
 The BCMA IV Parameters are maintained using the GUI BCMA Site Parameters 
 application. The BCMA IV Parameters are available to other applications via
 this API.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: BCMA
KEYWORDS: PSBIV
KEYWORDS: IV PARAMETERS
KEYWORDS: BCMA PARAMETERS
COMPONENT/ENTRY POINT: EN(PSBWARD,PSBIVT)
 COMPONENT DESCRIPTION:   Return a caret delimited string containing the BCMA
 IV Parameters for a specific Ward Location (#42) file entry and a specific IV
 Type ("A"-Admixture, "H"-Hyperal, "P"-Piggyback, "S"-Syringe, 
 "C"-Chemotherapy).  
VARIABLES: PSBWARD                      TYPE: Input
 VARIABLES DESCRIPTION:   PSBWARD is the Internal Entry Number (IEN) from the
 Ward Location (#42) FILE.  
VARIABLES: PSBIVT                       TYPE: Input
 VARIABLES DESCRIPTION:   The specific IV Type ("A"-Admixture, "H"-Hyperal,
 "P"-Piggyback, "S"-Syringe, "C"-Chemotherapy).  
VARIABLES: PSBIVPAR                     TYPE: Output
 VARIABLES DESCRIPTION:   Delimited string of BCMA GUI IV Parameters values by
 IV Type and Ward. If parameters are not defined for Ward, parameters will be
 returned for the Division associated with the Ward.  
  
 IV parameter string will be returned in the following order: =IV
 TYPE^ADDITIVE^STRENGTH^BOTTLE^SOLUTION^VOLUME^INFUSION RATE^MED 
 ROUTE^SCHEDULE^ADMIN TIME^REMARKS^OTHER PRINT INFO^PROVIDER^START 
 DATE/TIME^STOP DATE/TIME^PROVIDER COMMENTS 
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS

NUMBER: 5805                            IA #: 5805
  FILE NUMBER: 4.2                      GLOBAL ROOT: DIC(4.2,
  DATE CREATED: MAY 30, 2012            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: One Time Exception Domain File (#4.2) Write
  ID: DIC(4.2,
GLOBAL REFERENCE: DIC(4.2,#,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This name is the exact name of the domain, as used in
 network addressing. 
FIELD NUMBER: 1                         FIELD NAME: FLAGS
  LOCATION: 0;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The flags field controls the flow of messages to this
 domain from the local node.  
FIELD NUMBER: 2                         FIELD NAME: RELAY DOMAIN
  LOCATION: 0;3                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is the name of the domain, if any, to which messages
 are to be always routed.  
FIELD NUMBER: 1.7                       FIELD NAME: DISABLE TURN COMMAND
  LOCATION: 0;16                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This field, if set to "YES", means that a remote domain
 calling this domain will not be able to execute the SMTP TURN command.  
 GLOBAL DESCRIPTION:   This file is used to name all of the domains to which
 MailMan messages may be routed.  Each name in this file corresponds to the
 right side of a MailMan address-the part following the "@".  
 GENERAL DESCRIPTION:   Integrated Billing application requesting onetime
 exception write privileges to create new domains needed by Electronic
 Insurance Identification module. The domains are being created by Integrated
 Billing patch IB*2*457 and informational patch XM*DBA*176 will be released to 
 address documentation needs for the new domains.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUL 31, 2012
KEYWORDS: Create Domain File Entries
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Creating four new domain entries needed for Electronic
 Insurance Identification. This authorization is a onetime exception due to
 knowledge of need for new domains was not realized until late in the project 
 lifecycle. Integrated Billing patch IB*2*457 is creating the new domains.  
  
  NAME: Q-IBH.DNS              FLAGS: S 
    RELAY DOMAIN: FOC-DNS       DISABLE TURN COMMAND: YES 
    
  NAME: Q-IBK.DNS                      FLAGS: S 
    RELAY DOMAIN: FOC-DNS       DISABLE TURN COMMAND: YES 
   
  NAME: Q-IBN.DNS                      FLAGS: S 
    RELAY DOMAIN: FOC-DNS       DISABLE TURN COMMAND: YES 
   
  NAME: Q-IBX.DNS                   FLAGS: S 
    RELAY DOMAIN: FOC-DNS       DISABLE TURN COMMAND: YES 
  DATE ACTIVATED: JUN 05, 2012

NUMBER: 5806                            IA #: 5806
  DATE CREATED: MAY 31, 2012            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCEP8C
  NAME: FB PROVIDER TO IB AUTOMATION    ID: IBCEP8C
 GENERAL DESCRIPTION:   This private agreement between FB and IB will allow Fee
 Basis to file Fee Vendor and 5010 Providers to the IB NON/OTHER VA BILLING
 PROVIDER (#355.93) file for paid Fee claims that are potentially billable by
 IB.  The call is made during a nightly process (option FB PAID TO IB) within 
 FB.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EPFBAPI
 COMPONENT DESCRIPTION:   Passes FB source record information from Fee claims. 
 Source information originates in FEE BASIS PAYMENT (#162) or FEE BASIS INVOICE
 (#162.5) files for outpatient payments or inpatient invoices.  Vendor
 information for these claims will be retrieved from the FEE BASIS VENDOR
 (#161.2) file.  Returns the results (add/update/error) of the IB processing to
 FB for reporting.  
VARIABLES: IBSRCREC                     TYPE: Input
 VARIABLES DESCRIPTION:   Array of information about the source record supplied
 by the FB nightly process.  NPI is required and will be validated.  Example: 
  IBSRCREC("NAME")=NAME (#.01) 
  IBSRCREC("IB TYPE")=PROVIDER TYPE (.02) 
  IBSRCREC("FBADD1")=STREET ADDRESS (.05)* 
  IBSRCREC("FBADD2")=STREET ADDRESS LINE 2 (.1)** 
  IBSRCREC("FBCITY")=CITY (.06)* 
  IBSRCREC("FBSTATE INT")=STATE (.07)* 
  IBSRCREC("FBZIP")=ZIP CODE (.08)* 
  IBSRCREC("FBFACID")=FACILITY DEFAULT ID NUMBER (.09)** 
  IBSRCREC("FBPHONE")=CONTACT PHONE NUMBER (1.02)** 
  IBSRCREC("FBNPI")=NPI (41.01) 
            and DATE/TIME OF LAST NPI CHANGE (40) 
  IBSRCREC("FBTXY")=TAXONOMY CODE (42) 
  
  *Only for Facility type providers 
  **Only for FEE BASIS VENDORs being added as Facility type providers 
VARIABLES: IBRETARY                     TYPE: Input
 VARIABLES DESCRIPTION:   Returns the results of the add/update processing
 (passed by reference).  Example: 
  IBRETARY(1)=IEN of the IB record or NULL 
  IBRETARY(2)=Code indicating NPI validation 
  IBRETARY(3)=Code indicating Taxonomy updates 
  
 The IEN and Codes returned to the FB call will be filed in the FEE BASIS PAID
 TO IB (#161.9) file, IB NON/OTHER PROVIDER (.07), NPI UPDATED (.08) and
 TAXONOMY UPDATED (.09) for reporting.  
SUBSCRIBING PACKAGE: FEE BASIS
  DATE ACTIVATED: JUL 11, 2012

NUMBER: 5807                            IA #: 5807
  DATE CREATED: JUN 11, 2012
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  ROUTINE: TIUSRVT1                     NAME: TIU GET LINKED TEMPLATE
  ID: TIUSRVT1
 GENERAL DESCRIPTION:   This private agreement between TIU and GMRC will allow
 the Consult package to retrieve the template associated with a consult
 service.  The Healthcare Claims Processing System (HCPS) interface for
 Purchased Care will use the standard templates created by the Non-VA Care
 Coordination (NVCC) project to parse the Reason For Request field when
 receiving consults from VistA.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETLINK(ORY,LINK)
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   Passed by reference.  Returns node data from the TIU
 TEMPLATE (#8927) file in the format: 
   template IEN^Type(.03)^Status(.02)^Name(.01)...  Only the IEN and Name are
 used for this ICR.  
VARIABLES: LINK                         TYPE: Input
 VARIABLES DESCRIPTION:   Variable pointer identifying the IEN and File to 
 which a template is attached, e.g. 87;GMR(123.5, 
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING

NUMBER: 5808                            IA #: 5808
  FILE NUMBER: 2.312                    GLOBAL ROOT: DPT
  DATE CREATED: JUN 11, 2012            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: INSURANCE MULTIPLE ACCESS       ID: DPT
GLOBAL REFERENCE: DPT(D0,.312,D1,1)
FIELD NUMBER: 1.03                      FIELD NAME: DATE LAST VERIFIED
  LOCATION: 1;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The VA POINT OF SERVICE (KIOSK) package needs Fileman
 read access to the INSURANCE TYPE multiple of the PATIENT file (#2).  The VPS
 GET PATIENT DEMOGRAPHIC remote procedure call will retrieve data from this
 multiple and return the data to the MDWS web service.  MDWS will then push the
 data to the Vecna Kiosk located a the local VAMC. 
  
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   
  

NUMBER: 5809                            IA #: 5809
  FILE NUMBER: 704.102                  GLOBAL ROOT: MDC(704.102,
  DATE CREATED: JUN 11, 2012            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CLIO TERM TYPE FILE
  ID: MDC(704.102,
GLOBAL REFERENCE: MDC(704.102,D0,0)
FIELD NUMBER: .01                       FIELD NAME: TYPE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: XML TAG
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Allows access to nationally released indices on these
 fields as well.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CP
KEYWORDS: CLIO
KEYWORDS: MDC
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: MAR 26, 2013

NUMBER: 5810                            IA #: 5810
  FILE NUMBER: 704.117                  GLOBAL ROOT: MDC(704.117,
  DATE CREATED: JUN 11, 2012            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CLIO OBS FILE
  ID: MDC(704.117,
GLOBAL REFERENCE: MDC(704.117,D0,0)
FIELD NUMBER: .01                       FIELD NAME: OBS ID
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PARENT ID
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: FACILITY ID
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: HOSPITAL LOCATION ID
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: OBSERVED DATE TIME
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: OBSERVED BY ID
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: TERM ID
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: PATIENT ID
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: STATUS
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Allows access to nationally released indices on these
 fields as well.  
GLOBAL REFERENCE: MDC(704.117,D0,.1)
FIELD NUMBER: .1                        FIELD NAME: SVALUE
  LOCATION: .1;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: MDC(704.117,D0,.2)
FIELD NUMBER: .21                       FIELD NAME: SOURCE
  LOCATION: .2;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .22                       FIELD NAME: SOURCE COMMENTS
  LOCATION: .2;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .23                       FIELD NAME: SOURCE DATA ITEM ID
  LOCATION: .2;3                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .24                       FIELD NAME: SOURCE VERSION
  LOCATION: .2;4                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .25                       FIELD NAME: ENTERED DATE TIME
  LOCATION: .2;5                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .26                       FIELD NAME: ENTERED BY ID
  LOCATION: .2;6                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .27                       FIELD NAME: CHILD ORDER
  LOCATION: .2;7                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .28                       FIELD NAME: RANGE
  LOCATION: .2;8                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: MDC(704.117,D0,.4)
FIELD NUMBER: .4                        FIELD NAME: COMMENT
  LOCATION: .4;1                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CP
KEYWORDS: CLIO
KEYWORDS: MDC
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Use of ICR 5810 will allow eHMP to include the clinical
 observations from the CLINICAL PROCEDURES Package. eHMP is using the national 
 cross-references to select and process data. Use of this ICR will improve 
 efficiency and aid in maintenance of the code. 
  
 HMP v.2.0 accesses the OBS_ID (#.01), PARENT_ID (#.02), FACILITY_ID (#.03),
 HOSPITAL_LOCATION_ID (#.04), OBSERVED_DATE_TIME (#.05), OBSERVED_BY_ID (#.06),
 TERM_ID (#.07), PATIENT_ID (#.08), STATUS (#.09), SVALUE (#.1), SOURCE (#.21),
 SOURCE_COMMENTS (#.22), SOURCE_DATA_ITEM_ID (#.23), SOURCE_VERSION (#.24),
 ENTERED_DATE_TIME (#.25), ENTERED_BY_ID (#.26), CHILD_ORDER (#.27), RANGE
 (#.28), and COMMENT (#.4)fields and the 'AS', 'ASTATUS', 'PK', and 'PT' cross
 references.  
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
  DATE ACTIVATED: MAR 26, 2013

NUMBER: 5811                            IA #: 5811
  FILE NUMBER: 704.118                  GLOBAL ROOT: MDC(704.118,
  DATE CREATED: JUN 11, 2012            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CLIO OBS QUALIFIER FILE
  ID: MDC(704.118,
GLOBAL REFERENCE: MDC(704.118,D0,0)
FIELD NUMBER: .01                       FIELD NAME: OBS ID
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: QUALIFIER ID
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Allows access to nationally released indices on these
 fields as well.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CP
KEYWORDS: CLIO
KEYWORDS: MDC
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   4/4/16- eHMP added as a subscriber.  Developer
 indicated eHMP is only using the PK cross reference and only FileMan reads.
 Use of ICR #5811 allows eHMP to include the clinical observations from the
 Clinical Procedures package.  Specifically the file is used to specify the 
 relationship between observations and their qualifier.  
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
  DATE ACTIVATED: MAR 26, 2013

NUMBER: 5812                            IA #: 5812
  FILE NUMBER: 4.3                      GLOBAL ROOT: XMB(1
  DATE CREATED: JUN 13, 2012            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MAX LINES SEND/RECEIVE
  ID: XMB(1
GLOBAL REFERENCE: XMB(1,1,NETWORK-LIMIT)
FIELD NUMBER: 8.3                       FIELD NAME: NETWORK - MAX LINES SEND
  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:   The Mental Health package requests permission to 'Read
 with FileMan' the following fields from the MAILMAN SITE PARAMETERS file
 (#4.3): 
   NETWORK - MAX LINES SEND (#8.3) 
   NETWORK - MAX LINES RECEIVE (#8.31) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAX LINES SEND
KEYWORDS: MAX LINES RECEIVE
SUBSCRIBING PACKAGE: MENTAL HEALTH
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS
 SUBSCRIBING DETAILS:   Added 10/29/18 
  DATE ACTIVATED: MAY 01, 2018

NUMBER: 5813                            IA #: 5813
  FILE NUMBER: 18.12                    GLOBAL ROOT: XOB(18.12
  DATE CREATED: JUN 14, 2012            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Add Availability Resource to WEB SERVER File (#18.12)
  ID: XOB(18.12
GLOBAL REFERENCE: XOB(18.12,D0,100,0)
FIELD NUMBER: 100                       FIELD NAME: AUTHORIZED WEB SERVICES
  LOCATION: 100;0                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: XOB(18.12,D0,100,D1,0)
FIELD NUMBER: .01                       FIELD NAME: WEB SERVICE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: STATUS
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: XOB(18.12,'B')
 GENERAL DESCRIPTION:   Pharmacy Data Management needs FILEMAN read/write
 access for AUTHORIZED WEB SERVICES sub-file (#100) for WEB SERVER FILE
 (#18.12).  This includes the "B" cross-reference.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 18.12
KEYWORDS: WEB SERVICE FILE
KEYWORDS: XOBW
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   For the Pharmacy Re-engineering (PRE) project, an
 additional web service is being added to the previously released PEPS web
 server.  Enabling the new web service programmatically will alleviate having
 sites perform this task manually. 
  
 This integration agreement is only needed for PSS*1*160 post installation 
 routine.  
  DATE ACTIVATED: SEP 06, 2012

NUMBER: 5814                            IA #: 5814
  FILE NUMBER: 18.02                    GLOBAL ROOT: XOB(18.02
  DATE CREATED: JUN 15, 2012            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Read access for WEB SERVICE FILE (#18.02)
  ID: XOB(18.02
GLOBAL REFERENCE: XOB(18.02,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   The entries in this file contain the connection related
 and proxy class information of remote web services.  
  
 This information is required in order for the HealtheVet Web Services Client
 (HWSC) application to call remote web services.  
GLOBAL REFERENCE: XOB(18.02,B,WEB SERVICE,IEN)
 GENERAL DESCRIPTION:   Pharmacy Data Management needs FILEMAN read access for
 WEB SERVICE FILE (#18.02).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 18.02
KEYWORDS: XOBW
KEYWORDS: WEB SERVICE FILE
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   For the Pharmacy Re-engineering (PRE) project, an
 additional web service is being added to the previously released PEPS web
 server.  Enabling the new web service programmatically will alleviate having
 sites perform this task manually. Having read access to WEB SERVICE FILE
 (#18.02) will allow retrieval of internal entry number of the new web service. 
  
 This integration agreement is only needed for PSS*1*160 post installation 
 routine. 
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA
 SUBSCRIBING DETAILS:   MPI will be accessing the "B" X-REF in the Web Service
 (#18.02) file. This will give MPI the ability to retrieve the IEN of our Web
 Service (Created in Pre/Post install routines using the supported
 GENPORT^XOBWLIB ICR #5421) so it can be added to the AUTHORIZED WEB SERVICE
 multiple when we create our web server entry (via pending ICR #6408).  
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
  DATE ACTIVATED: SEP 06, 2012

NUMBER: 5815                            IA #: 5815
  DATE CREATED: JUN 18, 2012
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA5815
  STATUS: Pending

NUMBER: 5816                            IA #: 5816
  DATE CREATED: JUN 25, 2012            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSER2
  NAME: XUS PKI GET UPN                 REMOTE PROCEDURE: XUS PKI GET UPN
  ID: XUSER2
 GENERAL DESCRIPTION:   Allows retrieval of the SUBJECT ALTERNATIVE NAME field
 (#501.2) in the NEW PERSON file (#200).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SETUPN
 COMPONENT DESCRIPTION:   Set the SUBJECT ALTERNATIVE NAME from the PIV card.  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 if the value was successfully saved, 0 if
 it was not successfully saved.  
VARIABLES: V                            TYPE: Input
 VARIABLES DESCRIPTION:   The subject alternative name value.  
VARIABLES: DUZ                          TYPE: Used
 VARIABLES DESCRIPTION:   The internal entry number of the NEW PERSON file
 (#200) entry to update.  
COMPONENT/ENTRY POINT: GETUPN
 COMPONENT DESCRIPTION:   Get SUBJECT ALTERNATIVE NAME for PIV card check.  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   The value stored in the SUBJECT ALTERNATIVE NAME
 field (#501.2) in the NEW PERSON file (#200).  
VARIABLES: DUZ                          TYPE: Used
 VARIABLES DESCRIPTION:   The internal entry number of the NEW PERSON file
 (#200) entry to retrieve the value from.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   CPRS allows providers to enter the subject alternative
 name from their PIV card once; subsequent edits are accomplished through
 software provided by KERNEL.  
  DATE ACTIVATED: SEP 10, 2012

NUMBER: 5817                            IA #: 5817
  FILE NUMBER: 41.42                    GLOBAL ROOT: DGS(41.42
  DATE CREATED: JUL 17, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Read/Update 41.42 file entries
  ID: DGS(41.42
GLOBAL REFERENCE: DGS(41.42
FIELD NUMBER: .1                        FIELD NAME: DIVISION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: LAST UPDATED
  LOCATION: 0;5                         ACCESS: Write w/Fileman
FIELD NUMBER: 4                         FIELD NAME: CALLED
  LOCATION: 0;6                         ACCESS: Write w/Fileman
FIELD NUMBER: PATIENT(B) CROSS-REFERENCE
  ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The VA Point of Service (VPS) package needs access to
 the PRE-REGISTRATION CALL LIST FILE (#41.42) to update it after a veteran has
 completed pre-registration from a Vetlink Kiosk.  
  
  STATUS: Active
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
  DATE ACTIVATED: NOV 07, 2012

NUMBER: 5818                            IA #: 5818
  DATE CREATED: JUL 18, 2012            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOTLNK
  NAME: HLO IFCAP API                   ID: HLOTLNK
 GENERAL DESCRIPTION:   The IFCAP package requests private usage of an HLO API
 (PORT2^HLOTLNK) to obtain the TCP/IP PORT (OPTIMIZED) field for a record in
 the HL LOGICAL LINK (#870) file.  
  
 The port obtained from the HL Logical Link record will be used to set the 
 PARMS("PORT") input parameter prior to calling the supported HLO API 
 $$SENDONE^HLOAPI1(.MSG,.PARMS,.WHOTO,.ERROR).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HLO
KEYWORDS: IFCAP
COMPONENT/ENTRY POINT: $$PORT2(LINKNAME)
 COMPONENT DESCRIPTION:   Used to obtain the TCP/IP PORT (OPTIMIZED) field for
 a record in the HL LOGICAL LINK (#870) file.  
VARIABLES: LINKNAME                     TYPE: Input
 VARIABLES DESCRIPTION:   Name of HL7 Logical Link.  
VARIABLES: $$PORT2                      TYPE: Output
 VARIABLES DESCRIPTION:   The function returns TCP/IP PORT (OPTIMIZED) field on
 success, null on failure.  
SUBSCRIBING PACKAGE: IFCAP
  DATE ACTIVATED: JUL 23, 2012

NUMBER: 5819                            IA #: 5819
  GLOBAL ROOT: DD(                      DATE CREATED: JUN 28, 2012
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: IFCAP SET ID NODES DURING POST INSTALL
  ID: DD(
GLOBAL REFERENCE: DD(410,0,'ID','Z3')
GLOBAL REFERENCE: DD(410.02,0,'ID','Z2')
 GENERAL DESCRIPTION:   IFCAP needs to add ID nodes to the Control Point
 Activity file (#410) at the header (#410) and at the Item subfile (#410.02)
 level in support of patch PRC*5.1*167 (eCMS Interface to IFCAP - Phase 1).  As
 KIDS does not have a mechanism to transport ID nodes of a file's Data
 Dictionary without exporting the entire file definition, it is requested that
 for this patch IFCAP be permitted to set the ID nodes via the post-int routine 
 PRC5167P.  The proposed lines of code are as follows (without blank lines): 
  
 S ^DD(410,0,"ID","Z3")="D:$P($G(^(1)),U,8)]"""" EN^DDIOL(""Sent to 
 eCMS"",,""?0""),EN^DDIOL("" "",,""!?2"")" 
  
 S ^DD(410.02,0,"ID","Z2")="D:$P($G(@(DIC_+Y_"",4)"")),U,3)]"""" 
 EN^DDIOL(""eCMS Item Line ID ""_$P(^(4),U,3),,""!?10"")" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DD(
KEYWORDS: ID
KEYWORDS: IDENTIFIER
SUBSCRIBING PACKAGE: IFCAP
  DATE ACTIVATED: JUL 02, 2012

NUMBER: 5820                            IA #: 5820
  DATE CREATED: JUN 28, 2012
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA5820
  STATUS: Pending

NUMBER: 5821                            IA #: 5821
  FILE NUMBER: 45.86                    GLOBAL ROOT: DG(45.86,
  DATE CREATED: JUL 01, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CENSUS DATE
  ID: DG(45.86,
GLOBAL REFERENCE: DG(45.86,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the census date as established by
 VACO.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DRG
KEYWORDS: GROUPER
KEYWORDS: ICD-10
KEYWORDS: CENSUS
SUBSCRIBING PACKAGE: DRG GROUPER
 SUBSCRIBING DETAILS:   The ICD DRG Grouper needs to access the Census Date to
 compute the Effective Date.  
  
  DATE ACTIVATED: JUL 10, 2013

NUMBER: 5822                            IA #: 5822
  FILE NUMBER: 45                       GLOBAL ROOT: DGPT(
  DATE CREATED: JUL 01, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: CENSUS/DISCHARGE/MOVEMENT/SURGERY DATES
  ID: DGPT(
GLOBAL REFERENCE: DGPT(D0,0)
FIELD NUMBER: 13                        FIELD NAME: CENSUS DATE
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is a pointer to the PTF CENSUS DATE file #45.86 
  
GLOBAL REFERENCE: DGPT(D0,70)
FIELD NUMBER: 70                        FIELD NAME: DISCHARGE DATE
  LOCATION: 70;1                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Need to extract the date last discharged.  
  
GLOBAL REFERENCE: DGPT(D0,'M',D1,0)
FIELD NUMBER: 10                        FIELD NAME: MOVEMENT DATE
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Need to extract the date of the last patient movement.  
  
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:   Need to extract the date of the last Surgery procedure.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CENSUS
KEYWORDS: DATE
KEYWORDS: DISCHARGE
KEYWORDS: MOVEMENT
KEYWORDS: SURGERY
KEYWORDS: ICD-10
SUBSCRIBING PACKAGE: DRG GROUPER
 SUBSCRIBING DETAILS:   The ICD DRG Grouper needs to access the Census Date, 
 the Movement Date, the Surgery Date, and the Discharge date to compute the
 Effective Date.  
  
  DATE ACTIVATED: JUL 10, 2013

NUMBER: 5823                            IA #: 5823
  DATE CREATED: JUL 11, 2012            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS PKI SET UPN
  REMOTE PROCEDURE: XUS PKI SET UPN
 GENERAL DESCRIPTION:   Allows updating of the SUBJECT ALTERNATIVE NAME field
 (#501.2) in the NEW PERSON file (#200).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   CPRS allows providers to enter the subject alternative
 name from their PIV card once; subsequent edits are accomplished through
 software provided by KERNEL.  
  DATE ACTIVATED: SEP 10, 2012

NUMBER: 5824                            IA #: 5824
  DATE CREATED: JUL 11, 2012            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XU EPCS EDIT
  REMOTE PROCEDURE: XU EPCS EDIT
 GENERAL DESCRIPTION:   Creates an entry in the XUEPCS DATA file (#8991.6) that
 serves as an audit log of changes made to data in fields in the NEW PERSON
 file (#200) that are used in the electronic Prescribing of Controlled 
 Substances (e-PCS) functionality.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   CPRS allows providers to enter the subject alternative
 name from their PIV card once; subsequent edits are accomplished through
 software provided by KERNEL.  
  DATE ACTIVATED: SEP 10, 2012

NUMBER: 5825                            IA #: 5825
  DATE CREATED: JUL 23, 2012            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  ROUTINE: FBAAVR5                      NAME: FBAAVR5 for FBCS
  ID: FBAAVR5
 GENERAL DESCRIPTION:   Access to the API FBAAVR5 API's for FBCS to generate
 voucher batch messages to Central Fee when finalizing batches. Also to
 generate the correct ICN when transmitting batches to Central Fee.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS VOUCHER BATCH FEE BASIS
COMPONENT/ENTRY POINT: $$VBMSG
 COMPONENT DESCRIPTION:   This API generates a voucher batch message to Central
 Fee for a given batch IEN 
VARIABLES: FBN                          TYPE: Input
 VARIABLES DESCRIPTION:   Batch IEN 
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns the voucher batch message number if
 successful or 0^error message if unsuccessful 
COMPONENT/ENTRY POINT: $$ORGICN
 COMPONENT DESCRIPTION:   Generates the correct ICN to send to Central Fee when
 a patient has been moved.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   Sub-File number for outpatient or travel payments. 
VARIABLES: FBICN                        TYPE: Input
 VARIABLES DESCRIPTION:   ICN value 
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns the original ICN 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: SEP 14, 2012

NUMBER: 5826                            IA #: 5826
  DATE CREATED: JUL 23, 2012            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  ROUTINE: FBAAVR4                      NAME: FBAAVR4 for FBCS
  ID: FBAAVR4
 GENERAL DESCRIPTION:   Access to use API's in routine FBAAVR4 for FBCS 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBCS FBAAVR4 SETREJ FBAAVR4
COMPONENT/ENTRY POINT: $$SETREJ
 COMPONENT DESCRIPTION:   Set reject flags for a given payment/invoice IEN 
VARIABLES: FBN                          TYPE: Input
 VARIABLES DESCRIPTION:   Batch IEN 
VARIABLES: FBTYPE                       TYPE: Input
 VARIABLES DESCRIPTION:   Batch type (B2, B3,...B9) 
VARIABLES: FBIENS                       TYPE: Input
 VARIABLES DESCRIPTION:   Record IENS for the payment or invoice file that the
 rejections are being added to.  
VARIABLES: FBIREJ                       TYPE: Input
 VARIABLES DESCRIPTION:   Indicator to show whether the rejection came from the
 Central Fee interface.  (1 for yes) 
VARIABLES: FBRR                         TYPE: Input
 VARIABLES DESCRIPTION:   Reject reason (free text when not coming from the
 interface) 
VARIABLES: FBRRC                        TYPE: Input
 VARIABLES DESCRIPTION:   passed by reference array of reject reason codes. 
 (Required when the rejection comes from the interface.) 
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   returns a value of 1^batch number^amount paid if
 successful or 0^error message if unsuccessful.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: SEP 14, 2012

NUMBER: 5827                            IA #: 5827
  DATE CREATED: JUL 23, 2012            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FB1358
  NAME: ACCESS TO FB1358 FOR FBCS       ID: FB1358
 GENERAL DESCRIPTION:   Access to API's in the routine FB1358 for FBCS.  Used
 to manipulate 1358 values.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FBCS CHK1358 FB1358
COMPONENT/ENTRY POINT: $$CHK1358
 COMPONENT DESCRIPTION:   Determine if the 1358 is available for posting.  
VARIABLES: FBAAOB                       TYPE: Input
 VARIABLES DESCRIPTION:   Full obligation number (e.g. 500-C20001) 
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   returns a value of 1 if the 1358 is available for
 posting or 0^error message if it is not.  
COMPONENT/ENTRY POINT: $$POSTINV
 COMPONENT DESCRIPTION:   Used to update an existing IFCAP authorization on a
 1358 obligation when the IFCAP authorization is posted by invoice.  
VARIABLES: FBN                          TYPE: Input
 VARIABLES DESCRIPTION:   Batch IEN 
VARIABLES: FBI                          TYPE: Input
 VARIABLES DESCRIPTION:   Invoice IEN of file 162.5 
VARIABLES: FBACT                        TYPE: Input
 VARIABLES DESCRIPTION:   action - must be "R" or "D".  "R" for when the
 payment is rejected and "D" when the reject flag is removed.  
VARIABLES: FBSKIP                       TYPE: Input
 VARIABLES DESCRIPTION:   0 OR 1.  1 to skip control point access check.  
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   returns a value of 1 if posting to the 1358 was
 successful or 0^error message if it wasn't.  
COMPONENT/ENTRY POINT: $$POSTBAT
 COMPONENT DESCRIPTION:   This API is called to update an existing IFCAP
 authorization on a 1358 obligation when the IFCAP authorization is by fee
 batch.  
VARIABLES: FBN                          TYPE: Input
 VARIABLES DESCRIPTION:   BATCH IEN 
VARIABLES: FBAAMT                       TYPE: Input
 VARIABLES DESCRIPTION:   dollar amount 
VARIABLES: FBACT                        TYPE: Input
 VARIABLES DESCRIPTION:   must be "R" or "D" "R" means payment was flagged as
 rejected.  "D" means the reject flag was removed.  
VARIABLES: FBSKIP                       TYPE: Input
 VARIABLES DESCRIPTION:   0 or 1 
  
 1 to skip the control point access check.  
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   returns a message of 1 if posting to the 1358 was
 successful or 0^error message if it wasn't.  
COMPONENT/ENTRY POINT: &
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: SEP 14, 2012

NUMBER: 5828                            IA #: 5828
  DATE CREATED: JUL 23, 2012            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  ROUTINE: FBAADD1                      NAME: ACCESS TO FBAADD1 FOR FBCS
  ID: FBAADD1                           STATUS: Retired
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS FBAADD1 CALCDT
COMPONENT/ENTRY POINT: $$CALCDT
 COMPONENT DESCRIPTION:   calculate x number of work days from a given date.  
VARIABLES: FBN                          TYPE: Input
 VARIABLES DESCRIPTION:   Optional number of days from the given date. 
 (default 3) 
VARIABLES: FBDT                         TYPE: Input
 VARIABLES DESCRIPTION:   date in Fileman format.  defaults to today.  
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   returns a date that is FBN (number of days) workdays
 before the FBDT (input date) in FILEMAN format.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: SEP 14, 2012

NUMBER: 5829                            IA #: 5829
  DATE CREATED: JUL 23, 2012            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  ROUTINE: FBAARJP                      NAME: ACCESS TO FBAARJP FOR FBCS
  ID: FBAARJP                           STATUS: Retired
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS FBAARJP
COMPONENT/ENTRY POINT: $$REJTXT
 COMPONENT DESCRIPTION:   Get the reject text from a given line item 
VARIABLES: FBFILE                       TYPE: Input
 VARIABLES DESCRIPTION:   File number that the line item is in.  
VARIABLES: FBIENS                       TYPE: Input
 VARIABLES DESCRIPTION:   IENS of the payment line item within the file.  
VARIABLES: FBTXT                        TYPE: Both
 VARIABLES DESCRIPTION:   The rejection text in human readable format.  
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   returns an array of the rejection text for a given
 payment line. (if any) the format is: 
  
 FBTXT(0)=count of lines FBTXT(#)=line of text 
  
 where # is a sequential number starting at 1.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: SEP 14, 2012

NUMBER: 5830                            IA #: 5830
  DATE CREATED: JUL 23, 2012            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  ROUTINE: FBAARR3                      NAME: ACCESS TO FBAARR3 FOR FBCS
  ID: FBAARR3                           STATUS: Retired
  DURATION: Till Otherwise Agreed
KEYWORDS: FBCS FBAARR3
COMPONENT/ENTRY POINT: $$DELREJ
 COMPONENT DESCRIPTION:   Delete the rejection flag from a given payment line
 item when reinitiating it to a new batch.  
VARIABLES: FBFILE                       TYPE: Input
 VARIABLES DESCRIPTION:   The file number where the given payment item resides. 
 
VARIABLES: FBIENS                       TYPE: Input
 VARIABLES DESCRIPTION:   IENS for the payment to delete reject flag from.  
VARIABLES: FBNB                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the new batch for reinitiation.  
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   returns a 1 when successfully processed or 0^error
 message if there was a problem removing the reject flag.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: SEP 14, 2012

NUMBER: 5831                            IA #: 5831
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: AUG 08, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PATIENT FILE FIELDS
  ID: DPT(
GLOBAL REFERENCE: DPT(DFN,.21
FIELD NUMBER: .21011                    FIELD NAME: K-WORK PHONE NUMBER
  LOCATION: .21;11                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DFN,.211
FIELD NUMBER: .211011                   FIELD NAME: K-2 WORK PHONE NUMBER
  LOCATION: .211;11                     ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DFN,.33
FIELD NUMBER: .33011                    FIELD NAME: E-WORK PHONE NUMBER
  LOCATION: .33;11                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DFN,.331
FIELD NUMBER: .331011                   FIELD NAME: E2-WORK PHONE NUMBER
  LOCATION: .331;11                     ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DFN,.25
FIELD NUMBER: .2515                     FIELD NAME: SPOUSE'S EMPLOYMENT STATUS
  LOCATION: .25;15                      ACCESS: Read w/Fileman
FIELD NUMBER: .2516                     FIELD NAME: SPOUSE'S RETIREMENT DATE
  LOCATION: .25;16                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DFN,.311
FIELD NUMBER: .31116                    FIELD NAME: DATE OF RETIREMENT
  LOCATION: .311;16                     ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DFN,.38
FIELD NUMBER: .381                      FIELD NAME: ELIGIBLE FOR MEDICAID?
  LOCATION: .38;1                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This ICR documents access to several Patient (#2) file
 fields not supported by other ICRs or APIs for the VPS Kiosk project.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
  DATE ACTIVATED: AUG 08, 2012

NUMBER: 5832                            IA #: 5832
  DATE CREATED: AUG 14, 2012            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XULMU
  NAME: LOCK MANAGER APIs               ID: XULMU
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SETCLEAN
 COMPONENT DESCRIPTION:   Description:  The purpose of this API is to register
 a cleanup 
       routine that should be executed when the process is terminated 
       by the Kernel Lock Manager.  An entry is created on a stack kept 
       for the process.  The location is ^XTMP("XULM CLEANUP_"_$J) where 
       $J uniquely identifies the process.  A process may call 
       SETCLEAN^XULMU repeatedly, and each time a new entry is placed on 
       the stack.  
       
   *Important*: Once an application calls SETCLEAN, upon exiting it must 
        either execute its housecleaning stack or delete it, using 
        the APIs CLEAN or UNCLEAN. 
      
   
    Example:  Suppose the application has a cleanup routine 
        CLEANUP^XXAPP, and it needs to be executed with DFN defined 
        with its present valued.  The application would use this API 
        as follows: 
                    N VAR,CLEANUP 
                    S VAR("DFN")=DFN 
                    S CLEANUP=$$SETCLEAN^XULMU("CLEANUP^XXAPP",.VAR) 
  
      The application's housekeeping stack would look like this: 
  
      ^XTMP("XULM CLEANUP",$J,1,"ROUTINE")="CLEANUP^XXAPP" 
      ^XTMP("XULM CLEANUP",$J,1,"VARIABLES","DFN")=1000061 
VARIABLES: RTN                          TYPE: Input
 VARIABLES DESCRIPTION:   The routine to be executed when the process is
 terminated.  
  
VARIABLES: VAR                          TYPE: Input
 VARIABLES DESCRIPTION:   A list of variables that should be defined when the
 routine is executed.  It is up to the application to insure that all the
 required variables are defined.  
  
VARIABLES: FUNCTION VALUE               TYPE: Output
 VARIABLES DESCRIPTION:   An integer is returned that identifies the entry
 created on the stack. 
  
COMPONENT/ENTRY POINT: UNCLEAN
 COMPONENT DESCRIPTION:   Description - this removes entries from the
 housecleaning stack set by 
       calling SETCLEAN^XULMU. Entries are removed in FIFO order.  If LAST is 
       not passed in, then the entire stack is deleted, otherwise just the 
       entries back to LAST are removed.  
        
     Example: This would remove the entire housecleaning stack: 
  
                     DO UNCLEAN^XULMU 
  
     Example: If an application is called by another application, then the 
              the first application may have already placed entries of its 
              own on the stack.   So the parameter LAST needs to be passed, 
              with LAST being the first entry placed on the stack.  It will 
              be the last entry deleted, since that stack is executed in 
              FIFO order.  
   
  
               DO UNCLEAN^XULMU(LAST) 
VARIABLES: LAST                         TYPE: Input
 VARIABLES DESCRIPTION:   Identifies the last entry on the housekeeping stack
 to remove.  Entries are removed in FIFO order, so the first entry removed is 
 the last entry that was added, and the last entry removed is LAST. If not
 passed in, the entire housecleaning stack is deleted. 
COMPONENT/ENTRY POINT: CLEANUP
 COMPONENT DESCRIPTION:   Description:  This API will execute the housecleaning
 stack set by the 
       process identified by DOLLARJ. Entries are executed in the FIFO order, 
       with the last entry added being the first to be executed, and LAST 
       being the last entry executed. If LAST is not passed in, 
       then the entire stack is executed.  
         
     
    Example:  An application may execute the entire housecleaning stack 
              with the following code: 
        
               DO CLEANUP^XULMU 
  
    Example:  If an application is called by another application, then the 
              the first application may have already placed entries of its 
              own on the stack.   So the parameter LAST needs to be passed, 
              with LAST being the first entry placed on the stack.  It will 
              be the last entry executed, since that stack is executed in 
              FIFO order.  
   
               DO CLEANUP^XULM(LAST) 
  
  
  
  
VARIABLES: XULAST                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) This is the last entry that will be
 executed.  If not passed in, then the entire housecleaning stack is executed.  
  
COMPONENT/ENTRY POINT: PAT
 COMPONENT DESCRIPTION:   Description: This is for use within the MUMPS code
 for a computable file reference to the PATIENT file (#2).  It returns a
 standard set of patient identifiers.  
  
  
  
 Example of Use: Assuming that DFN is a variable defined within the lock
 template, then the MUMPS code for a computable file reference to the Patient
 file (#2) would consist of the following: 
  
          DO PAT^XULMU(DFN) 
  
  
  
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   the IEN of a record in the PATIENT file (#2) 
  
VARIABLES: ID                           TYPE: Output
 VARIABLES DESCRIPTION:   Returns the following: 
         ID("IEN")=DFN 
         ID(0)=4 
         ID(1)=<patient name> 
         ID(2)=<patient sex> 
         ID(3)=<patient date of birth> 
         ID(4)=<patient Social Security Number> 
  
COMPONENT/ENTRY POINT: ADDPAT
 COMPONENT DESCRIPTION:   Description: This API is very similar to PAT^XULMU,
 except that it is used to add the patient identifiers for a computable file
 reference for a file that is not the PATIENT file (#2).  The computable file
 references may include additional identifiers.  For example, a computable file 
 reference for a billing file may contain the bill number as an identifier as
 well as the patient identifiers returned by ADDPAT^XULMU.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   the IEN of a record in the PATIENT file (#2) 
  
VARIABLES: ID                           TYPE: Output
 VARIABLES DESCRIPTION:   ID(0) - If not defined at the point ADDPAT^XULMU is
 called, it will be initially set to 0.  When ADDPAT^XULMU returns, ID(0) will
 have been incremented by 4. 
  
         ID(ID(0)+1)=<patient name> 
         ID(ID(0)+2)=<patient sex> 
         ID(ID(0)+3)=<patient date of birth> 
         ID(ID(0)+4)=<patient Social Security Number> 
  
  DATE ACTIVATED: SEP 10, 2012

NUMBER: 5833                            IA #: 5833
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: AUG 14, 2012            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CLINIC PHYSICAL LOCATION
  ID: SC(
GLOBAL REFERENCE: SC(D0,0)
FIELD NUMBER: 10                        FIELD NAME: PHYSICAL LOCATION
  LOCATION: 0;11                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The VA POINT OF SERVICE (KIOSK) package needs Fileman
 read access to the PHYSICAL LOCATION field (10) of the HOSPITAL LOCATION file
 (#44).  The VPS GET PATIENT DEMOGRAPHIC remote procedure call will retrieve
 data from this field and return the data to the Vecna Kiosk located at the
 local VAMC.  
  STATUS: Active
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
  DATE ACTIVATED: AUG 20, 2012

NUMBER: 5834                            IA #: 5834
  DATE CREATED: AUG 20, 2012
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA5834
  STATUS: Pending

NUMBER: 5835                            IA #: 5835
  DATE CREATED: AUG 27, 2012
  CUSTODIAL PACKAGE: PATIENT ASSESSMENT DOCUM
  USAGE: Private                        TYPE: File
  NAME: PADP ACCESS TO 601.84 & 601.85
 GENERAL DESCRIPTION:   The PADP package would like to be able to add Mental
 Health Instrument Administrations and responses to files 601.84 & 601.85
 respectively via Fileman calls.  There are no documented APIs.  
  STATUS: Withdrawn

NUMBER: 5836                            IA #: 5836
  FILE NUMBER: 58.81                    GLOBAL ROOT: PSD(58.81
  DATE CREATED: AUG 29, 2012            CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA5836
  ID: PSD(58.81
GLOBAL REFERENCE: PSD(58.81,'AOP',Rx#)
 GENERAL DESCRIPTION:   Outpatient Pharmacy requests read access to the DRUG
 ACCOUNTABILITY file (#58.81) via the "AOP" x-reference to determine if an
 outpatient prescription for a controlled substance has been posted.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: SEP 03, 2014

NUMBER: 5837                            IA #: 5837
  DATE CREATED: AUG 30, 2012
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA5837
  STATUS: Pending

NUMBER: 5838                            IA #: 5838
  DATE CREATED: AUG 30, 2012            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDAMEVT
  NAME: SDAMEVT                         ID: SDAMEVT
 GENERAL DESCRIPTION:   THE [VETERAN POINT OF SERVICE] CHECK-IN RPC CALLS
 BEFORE,HANDLE, AFTER, AND EVT IN SDAMEVT TO ENSURE THAT ALL OTHER PROCESSES
 REQUIRING NOTIFICATION OF THE CHECK-IN ACTIVITY ARE NOTIFIED.  
  
 Parameters in the RPC have the following mapping for VPS: 
         VPSDT   -> SDT   Patient's appt. date and time.  
         VPSCLIN -> SDCL  IEN of clinic in HOSPITAL LOCATION file #44 
         VPSCIEN -> SDDA  IFN for ^SC(CLINIC,"S",DATE,1,IFN) 
         SDCIHDL -> SDHDL Event handle 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VPS
COMPONENT/ENTRY POINT: BEFORE
 COMPONENT DESCRIPTION:   Capture ^SC( appointment data before processing the
 event.  
VARIABLES: SDATA                        TYPE: Input
 VARIABLES DESCRIPTION:   String with format 
 "ApptIEN^PatDFN^ApptDate/Time^ClinicIEN^CurEvtHandle" 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Patient in file #2.  
VARIABLES: SDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's appointment date/time.  
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of clinic in HOSPITAL LOCATION file #44.  
VARIABLES: SDDA                         TYPE: Input
 VARIABLES DESCRIPTION:   IFN for ^SC(CLINIC,"S",DATE,1,IFN).  
VARIABLES: SDHDL                        TYPE: Input
 VARIABLES DESCRIPTION:   Event handle returned by HANDLE^SDAMEVT for and
 appointment event.  
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   Routine creates 2 temporary globals: 
         ^TMP("SDAMEVT",$J,"BEFORE") 
         ^TMP("SDEVT",$J,"BEFORE") and SDATA array element SDATA("BEFORE") 
COMPONENT/ENTRY POINT: AFTER
 COMPONENT DESCRIPTION:   Capture ^SC( appointment data after processing the
 event.  
VARIABLES: SDATA                        TYPE: Input
 VARIABLES DESCRIPTION:   String with format 
  "ApptIEN^PatDFN^ApptDate/Time^ClinicIEN^CurEvtHandle 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's IEN in PATIENT file 2.  
VARIABLES: SDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's appointment date/time.  
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of clinic in HOSPITAL LOCATION file 44.  
VARIABLES: SDDA                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of clinic in HOSPITAL LOCATION file 44.  
VARIABLES: SDHDL                        TYPE: Input
 VARIABLES DESCRIPTION:   Event handle returned by HANDLE^SDAMEVT for an
 appointment event.  
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   Routine creates 2 temporary globals: 
         ^TMP("SDAMEVT",$J,"AFTER") 
         ^TMP("SDEVT",$J,"AFTER") and SDATA array element SDATA("AFTER") 
COMPONENT/ENTRY POINT: HANDLE
 COMPONENT DESCRIPTION:   Get a handle for the current event.  
VARIABLES: SDORG                        TYPE: Input
 VARIABLES DESCRIPTION:   Originating transaction: 
         1=Appointment 
         2=Add/edit stop code 
         3=Registration/disposition 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Index into array element with value of
 ^TMP("SDEVTHANDLE",$J).  
COMPONENT/ENTRY POINT: EVT
 COMPONENT DESCRIPTION:   Call the Scheduling event handlers in ^ORD(101.  
VARIABLES: SDATA                        TYPE: Input
 VARIABLES DESCRIPTION:   String in format
 "ApptIEN^PatDFN^ApptDate/Time^ClinicIEN^CurEvtHandle" 
VARIABLES: SDAMEVT                      TYPE: Input
 VARIABLES DESCRIPTION:   Literal value 4, corresponding to a check-in event.  
VARIABLES: SDMODE                       TYPE: Input
 VARIABLES DESCRIPTION:   Parameter with the conversation mode from caller 
         0=full dialogue 
         1=computer monologue 
         2=quiet 
VARIABLES: SDHDL                        TYPE: Input
 VARIABLES DESCRIPTION:   Event handle returned by HANDLE^SDAMEVT for an
 appointment event.  
COMPONENT/ENTRY POINT: HDLKILL
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   THE [VETERAN POINT OF SERVICE] CHECK-IN RPC CALLS
 BEFORE,HANDLE, AFTER, AND EVT IN SDAMEVT TO ENSURE THAT ALL OTHER PROCESSES
 REQUIRING NOTIFICATION OF THE CHECK-IN ACTIVITY ARE NOTIFIED.  
  
 Parameters in the RPC have the following mapping for VPS: 
         VPSDT   -> SDT   Patient's appt. date and time.  
         VPSCLIN -> SDCL  IEN of clinic in HOSPITAL LOCATION file #44 
         VPSCIEN -> SDDA  IFN for ^SC(CLINIC,"S",DATE,1,IFN) 
         SDCIHDL -> SDHDL Event handle 
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   MBAA CANCEL APPOINTMENT RPC and MBAA APPOINTMENT MAKE
 RPC call the HANDLE, BEFORE, AFTER and EVT entry points in routine SDAMEVT
 when an appointment is cancelled or scheduled using the Scheduling Calendar
 View application.  The Scheduling Calendar View application is a new mobile 
 application that provides scheduling functionality via mobile devices such as
 an IPad, tablet or smart phone.  
  
 Additionally, these RPCs call the CANCEL and MAKE entry points in routine 
 SDAMEVT as documented in ICR #6048.  
  DATE ACTIVATED: OCT 12, 2012

NUMBER: 5839                            IA #: 5839
  DATE CREATED: AUG 30, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: DPTLK1                       NAME: VPS PATIENT LOOKUP
  ID: DPTLK1                            STATUS: Withdrawn
COMPONENT/ENTRY POINT: DOB
COMPONENT/ENTRY POINT: $$DOB(IEN,2)
 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 dateof birth.  
VARIABLES: [D
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's DFN in file #2.  
VARIABLES: 2                            TYPE: Input
 VARIABLES DESCRIPTION:   Constant specifying that the output you provide DOB
 in yyymmdd format.  
COMPONENT/ENTRY POINT: $$SSN(IEN)
 COMPONENT DESCRIPTION:   Given a DFN, returns the patient's SSN identifier,
 unless the patient is an employee.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's dfn in file #2.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VPS is using the API to get list of patient name(s).  

NUMBER: 5840                            IA #: 5840
  DATE CREATED: SEP 06, 2012            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEX10CX
  NAME: ICD-10 Suggestions              ID: LEX10CX
 GENERAL DESCRIPTION:   Supported APIs for the implementation of ICD-10.  The 
 APIs in this ICR become effective on the date of release of patches
 ICD*18.0*57 and LEX*2.0*80.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICD-10
KEYWORDS: ICD10
KEYWORDS: LEX10CS
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This entry point is an interactive lookup where the
 input coding system and code are not known.  There is no input variables for
 this API, however, the variable LEXSAB can be preset to a coding system (.01 
 field in file 757.03), else wise the user will be prompted for a coding
 system.  This API will display a selection list of suggested ICD-10 codes that
 have a similar textual content as the user selected code and coding system. 
 If no suggestions are available or the user does not make a selection, then
 the user will be prompted for a ICD-10 code.  There are two output variables,
 X and Y.  
  
 Example Output: 
  
   ICD-9 to ICD-10 
  
     X="119899^Tobacco Use Disorder^305.1^ICD-9-CM" 
     Y="5003360^Nicotine Dependence, unspecified, 
        Uncomplicated^F17.200^ICD-10-CM" 
    
   SNOMED CT to ICD-10 
    
     X="7078519^Diabetes mellitus type 2^44054006^SNOMED CT" 
     Y="5002666^Type 2 Diabetes Mellitus without 
        Complications^E11.9^ICD-10-CM" 
  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   X is a 4 piece "^" delimited string representing the
 source code.  
     
   1  Lexicon IEN for file 757.02 
   2  Expression 
   3  Code in selected Coding System 
   4  Coding System nomenclature 
            
      or null if search fails 
  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Y is a 4 piece "^" delimited string representing the
 target ICD-10 code.  
     
   1  Lexicon IEN for file 757.02 
   2  Expression 
   3  ICD-10 Diagnostic Code 
   4  ICD-10-CM 
            
   or -1 if search fails 
  
COMPONENT/ENTRY POINT: EN2(CODE,SAB)
 COMPONENT DESCRIPTION:   This entry point is an interactive lookup where the
 input coding system and code are known and supplied as input parameters CODE
 and SAB.  This API will display a selection list of suggested ICD-10 codes 
 that have a similar textual content as the specified code (CODE) and coding
 system (SAB).  If no suggestions are available or the user does not make a
 selection, then the user will be prompted for a ICD-10 code.  The output for
 EN2 is the same as entry point EN.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a code from the specified coding system.  
  
VARIABLES: SAB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the coding system abbreviation (a three
 character representation of the coding system taken from the .01 field of the
 CODING SYSTEMS file 757.03) 
  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   X is a 4 piece "^" delimited string representing the
 source code.  
  
   1  Lexicon IEN for file 757.02 
   2  Expression 
   3  Code in selected Coding System 
   4  Coding System nomenclature 
            
      or null if search fails 
  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Y is a 4 piece "^" delimited string representing the
 target ICD-10 code.  
     
   1  Lexicon IEN for file 757.02 
   2  Expression 
   3  ICD-10 Diagnostic Code 
   4  ICD-10-CM 
            
   or -1 if search fails 
  
COMPONENT/ENTRY POINT: EN3(CODE,SAB,.ARY,MAX)
 COMPONENT DESCRIPTION:   This entry point is a silent lookup for suggested
 ICD-10 codes for a code in another coding system.  The code (CODE) and coding
 system abbreviation (SAB) are passed as input parameters.  
  
 This API will create an array of suggested ICD-10 codes that have a similar
 textual content as the specified code (CODE) and coding system (SAB).  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a code in the coding system identified by the
 input parameter SAB.  
  
VARIABLES: SAB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the coding system abbreviation (a three
 character representation of the coding system taken from the .01 field of the
 CODING SYSTEMS file 757.03) 
  
VARIABLES: ARY                          TYPE: Both
 VARIABLES DESCRIPTION:   This is a local array, passed by reference: 
     
   ARY("X")     Input 
   ARY("Y",0)   Output   Number of Suggestions 
   ARY("Y",1)   Output   First Suggestion 
   ARY("Y",n)   Output   nth Suggestion 
  
   ARY("E")     Error Message 
                         
 Both ARY("X") and ARY("Y",#) are 4 piece "^" delimited strings: 
                
   1  Internal Entry Number (IEN) file 757.01 
   2  Expression (file 757.01, field .01) 
   3  Code (file 757.02, field 1) 
   4  Nomenclature (file 757.03, field 1) 
      i.e., SNOMED CT, ICD-9-CM or ICD-10-CM 
  
VARIABLES: MAX                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the maximum number of suggestions to return
 in the array (optional, default 100) 
  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS
SUBSCRIBING PACKAGE: PROBLEM LIST
  DATE ACTIVATED: JUL 11, 2014

NUMBER: 5841                            IA #: 5841
  DATE CREATED: SEP 07, 2012
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA5841
  STATUS: Pending

NUMBER: 5842                            IA #: 5842
  FILE NUMBER: 120.8                    GLOBAL ROOT: GMR
  DATE CREATED: SEP 07, 2012
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Controlled Subscription        TYPE: File
  NAME: ADVERSE REACTION TRACKING FILE 120.8
  ID: GMR
 GENERAL DESCRIPTION:   Veterans Point of Service Kiosk requires access to
 several fields in Patient Allergies File #120.8 that are not available from
 the ^GMRADPT API or other File ICRs.  The specific fields required for read
 are: 
  
 .02       REACTANT (RFX), [0;2] 1         GMR ALLERGY (V), [0;3] 4        
 ORIGINATION DATE/TIME (RDX), [0;4] 5         ORIGINATOR (RP200'), [0;5] 10     
   REACTIONS (Multiple-120.81), [10;0] 
           .01  REACTION (MP120.83'), [0;1] 
           1    OTHER REACTION (F), [0;2] 22        ENTERED IN ERROR (S),
 [ER;1] 23        DATE/TIME ENTERED IN ERROR (DX), [ER;2] 24        USER
 ENTERING IN ERROR (P200'), [ER;3] 26        COMMENTS (Multiple-120.826),
 [26;0] 
           .01  DATE/TIME COMMENT ENTERED (MD), [0;1] 
           1    USER ENTERING (P200'), [0;2] 
           1.5  COMMENT TYPE (S), [0;3] 
           2    COMMENTS (Multiple-120.8262), [2;0] 
                .01  COMMENTS (W), [0;1] 
  STATUS: Pending
KEYWORDS: VPS
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

NUMBER: 5843                            IA #: 5843
  FILE NUMBER: 120.8                    GLOBAL ROOT: GMR(120.8
  DATE CREATED: SEP 07, 2012
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ FIELDS IN PATIENT ALLERGY FILE
  ID: GMR(120.8
GLOBAL REFERENCE: GMR(120.8,D0,0
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
GLOBAL REFERENCE: GMR(120.8,D0,10,0
FIELD NUMBER: .01                       FIELD NAME: REACTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: OTHER REACTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: GMR(120.8,D0,ER
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,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
FIELD NUMBER: 2                         FIELD NAME: COMMENTS
  LOCATION: 2;0                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: GMR(120.8,C
FIELD NUMBER: C                         FIELD NAME: C Cross-Reference
  ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   The C cross-reference allows lookup of reactions by the
 REACTANT field (#.02).  
 GENERAL DESCRIPTION:   Veterans Point of Service Kiosk requires access to
 fields in Patient Allergies File #120.8 that are not available from ^GMRADPT
 API or other file ICRs.  
  
 Read access is requested.  
  STATUS: Active
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
  DATE ACTIVATED: SEP 25, 2012

NUMBER: 5844                            IA #: 5844
  DATE CREATED: SEP 11, 2012            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XLFIPV
  NAME: XLFIPV (IP UTILITIES)           ID: XLFIPV
 GENERAL DESCRIPTION:   Use of the VistA XLFIPV IPv4 and IPv6 Utility
 Application Programming Interfaces (APIs).  
  
 These APIs support the dual-stack protocol implementation as an IPv4-to-IPv6
 transition technology per Internet Engineering Task Force (IETF) Request For
 Comments (RFC) #4213.  
  
 They support input of IPv4 or IPv6 addresses either in standard form, or in a
 hybrid form using IPV4-Mapped IPv6 addresses.  In hybrid dual-stack 
 implementations the first 96-bits are written in the standard IPv6 format, and
 the remaining 32 bits written in the dot-decimal notation of IPv4.  
  
 IP address output of the APIs will be in standardized IPv4 dot-decimal 
 notation or in expanded IPv6 notation, where the address is represented by 8
 groups of 16-bit values, each represented as 4 hexadecimal digits and 
 separated by colons.  The hexadecimal digits will be capitalized to facilitate
 storage of IP addresses in a consistent form to simplify searches and reports. 
 The exception will be the IPv6 null address returned when the input is in an
 invalid format, which is commonly represented as "::0".  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IPV4
KEYWORDS: IPV6
COMPONENT/ENTRY POINT: $$VALIDATE
 COMPONENT DESCRIPTION:   Validate the format of an IP address (either IPv4 or
 IPv6).  
  
 Usage: S Y=$$VALIDATE^XLFIPV(IP) 
VARIABLES: IP                           TYPE: Input
 VARIABLES DESCRIPTION:   (string) IPv4 or IPv6 Address to be validated.  
VARIABLES: returns:                     TYPE: Output
 VARIABLES DESCRIPTION:   1 - if the IP address is in a valid format.  0 - if
 the format is invalid or null input.  
COMPONENT/ENTRY POINT: $$FORCEIP4
 COMPONENT DESCRIPTION:   Convert an IP address (either IPv4 or IPv6) into an
 IPv4 address in a standardized format consisting of four decimal numbers, each
 in the range 0 to 255, for example: "172.16.254.1".  
  
 Usage: S Y=$$FORCEIP4^XLFIPV(IP) 
VARIABLES: IP                           TYPE: Input
 VARIABLES DESCRIPTION:   (string) IPv4 or IPv6 Address to be converted.  
VARIABLES: returns:                     TYPE: Output
 VARIABLES DESCRIPTION:   An IPv4 address in "nnn.nnn.nnn.nnn" notation if the
 input address is valid and has an IPv4 equivalent, or the null address
 "0.0.0.0" if the input address is invalid, or the null address "0.0.0.0" if an
 IPv6 address is input which does not have an IPv4 equivalent.  
COMPONENT/ENTRY POINT: $$FORCEIP6
 COMPONENT DESCRIPTION:   Convert an IP address (either IPv4 or IPv6) into an
 IPv6 address in a standardized format consisting of eight groups of
 hexadecimal numbers separated by colons, for example: 
 "2001:0DB8:85A3:0042:0000:8A2E:0370:7334". 
  
 Usage: S Y=$$FORCEIP6^XLFIPV(IP) 
VARIABLES: IP                           TYPE: Input
 VARIABLES DESCRIPTION:   (string) IPv4 or IPv6 Address to be converted.  
VARIABLES: returns:                     TYPE: Output
 VARIABLES DESCRIPTION:   An IPv6 address in
 "hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh" notation if the input address is
 valid, or the null address "::0" if the input address is invalid.  
COMPONENT/ENTRY POINT: $$CONVERT
 COMPONENT DESCRIPTION:   Convert an IP address (either IPv4 or IPv6) into an
 IP address in a standardized format, either IPv4 or IPv6 as described above
 depending upon the system settings.  
  
 Usage: S Y=$$CONVERT^XLFIPV(IP) 
VARIABLES: IP                           TYPE: Input
 VARIABLES DESCRIPTION:   (string) IPv4 or IPv6 Address to be converted.  
VARIABLES: returns:                     TYPE: Output
 VARIABLES DESCRIPTION:   - An IPv4 address if IPv6 is disabled on the system. 
  
 - An IPv6 address if IPv6 is enabled on the system. 
  
 - An IPv4 or IPv6 null address if the input cannot be converted.  
COMPONENT/ENTRY POINT: $$VERSION
 COMPONENT DESCRIPTION:   Determine the system settings for IPv6.  
  
 Usage: S Y=$$VERSION^XLFIPV() 
VARIABLES: None                         TYPE: Input
VARIABLES: returns:                     TYPE: Output
 VARIABLES DESCRIPTION:   1 - if IPv6 is enabled.  
  
 0 - if IPv6 is disabled.  
  DATE ACTIVATED: JAN 14, 2014

NUMBER: 5845                            IA #: 5845
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123,
  DATE CREATED: SEP 17, 2012
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Controlled Subscription        TYPE: File
  NAME: Consults by Service and Status  ID: GMR(123,
GLOBAL REFERENCE: GMR(123,'AE',SRV,STAT,DAT,IEN
 GLOBAL DESCRIPTION:   Used to determine a list of consults with a specified
 status for specific services (Fee Services defined in the GMRC FEE SERVICES
 parameter) to assist in the creation of Authorizations for Fee Basis care.  
GLOBAL REFERENCE: GMR(123,
FIELD NUMBER: .01                       FIELD NAME: FILE ENTRY DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Date of entry of consult.  
FIELD NUMBER: .02                       FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Patient name, pointer to the Patient file (#2).  
FIELD NUMBER: 1                         FIELD NAME: TO SERVICE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The service responsible for completion of the
 Consult/request.  
FIELD NUMBER: 3                         FIELD NAME: DATE OF REQUEST
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The date of the request for the consult.  
FIELD NUMBER: 4                         FIELD NAME: PROCEDURE/REQUEST TYPE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The procedure requested via CPRS.  
FIELD NUMBER: 5                         FIELD NAME: URGENCY
  LOCATION: 0;9                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The urgency for the consult or request.  
FIELD NUMBER: 8                         FIELD NAME: CPRS STATUS
  LOCATION: 0;12                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The current CPRS status of the consult or request.  
FIELD NUMBER: 10                        FIELD NAME: SENDING PROVIDER
  LOCATION: 0;14                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The provder who originated the order.  
FIELD NUMBER: 13                        FIELD NAME: REQUEST TYPE
  LOCATION: 0;17                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The type of consult/request, being either consult or
 procedure.  
FIELD NUMBER: 14                        FIELD NAME: SERVICE RENDERED AS
  LOCATION: 0;18                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The type of service for the request: Inpatient or
 Outpatient 
FIELD NUMBER: 9                         FIELD NAME: LAST ACTION TAKEN
  LOCATION: 0;13                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The last recorded action for the Consult or request.  
GLOBAL REFERENCE: GMR(123,D0,40,'B'
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME OF ACTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Actual date & time the activity tracking update was added
 to the consult or request.  
FIELD NUMBER: 1                         FIELD NAME: ACTIVITY
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The activity that was recorded.  
 GLOBAL DESCRIPTION:   The global node has the history of the processing
 actions for the consult.  
 GENERAL DESCRIPTION:   Fee Basis Claims System reads fields from the
 REQUEST/CONSULTATION file to gather a list of consults to display to the Fee
 Basis staff to assist in the creation of authorizations for care related to
 consults requests. The Fee Basis Claims System application will also extract
 this information in a discrete format to help pre-populate the authorization 
 with information already present in the consult to assist in accuracy and 
 workflow.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 03, 2014

NUMBER: 5846                            IA #: 5846
  DATE CREATED: SEP 28, 2012            CUSTODIAL PACKAGE: 1
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DDS
  NAME: Clear ScreenMan Help Area       ID: DDS
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CLRMSG
KEYWORDS: DDS
KEYWORDS: SCREENMAN
KEYWORDS: ICD-10
KEYWORDS: ICD10
COMPONENT/ENTRY POINT: CLRMSG
 COMPONENT DESCRIPTION:   This API clears the contents of the Help area.  
  
SUBSCRIBING PACKAGE: DRG GROUPER
 SUBSCRIBING DETAILS:   The ICD Grouper package need to call CLRMSG^DDS inside
 of its special lookup routines (ICDEXLK*) to allow the special lookup routines
 to operate inside of ScreenMan.  After displaying the selection list and
 asking for user response, the special lookup needs to clear the Help Area.  
  
  DATE ACTIVATED: NOV 05, 2012

NUMBER: 5847                            IA #: 5847
  DATE CREATED: SEP 28, 2012            CUSTODIAL PACKAGE: 1
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DDSMSG
  NAME: Write to ScreenMan Help Area    ID: DDSMSG
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HLP
KEYWORDS: DDSMSG
KEYWORDS: SCREENMAN
KEYWORDS: ICD-10
KEYWORDS: ICD10
COMPONENT/ENTRY POINT: HLP
 COMPONENT DESCRIPTION:   This API places text in ScreenMan's Help area.  
  
SUBSCRIBING PACKAGE: DRG GROUPER
 SUBSCRIBING DETAILS:   The ICD Grouper package need to call HLP^DDSMSG inside
 of its special lookup routines (ICDEXLK*) to allow the special lookup routines
 to operate inside of ScreenMan.  This API allows the display of the selection
 list and prompting for user response in the Help Area.  
  
  DATE ACTIVATED: NOV 05, 2012

NUMBER: 5848                            IA #: 5848
  FILE NUMBER: 14.7                     GLOBAL ROOT: %ZIS(14.7,
  DATE CREATED: OCT 02, 2012            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: HL7 PKG ACCESS TO TASKMAN SITE PARAMETERS FILE
  ID: %ZIS(14.7,
GLOBAL REFERENCE: %ZIS(14.7,<IEN>,0)
FIELD NUMBER: .01                       FIELD NAME: BOX-VOLUME PAIR
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Configuration files of the HL7 package need to point to
 the TASKMAN SITE PARAMETERS file (#14.7) to allow sites to configure HLO
 processes to run on specific nodes.  The node is read from the BOX-VOLUME PAIR
 field (#.01) and used as an input parameter to Taskman.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH LEVEL SEVEN
  DATE ACTIVATED: JAN 17, 2013

NUMBER: 5849                            IA #: 5849
  FILE NUMBER: 9999999.64               GLOBAL ROOT: AUTTHF
  DATE CREATED: OCT 03, 2012
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  NAME: PADP Package Adding Health Factors
  ID: AUTTHF
GLOBAL REFERENCE: AUTTHF(IEN,0
FIELD NUMBER: .01                       FIELD NAME: FACTOR
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: .03                       FIELD NAME: CATEGORY
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DISPLAY ON HEALTH SUMMARY
  LOCATION: 0;8                         ACCESS: Write w/Fileman
FIELD NUMBER: .1                        FIELD NAME: ENTRY TYPE
  LOCATION: 0;10                        ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   PADP Package version 1.1 needs to add 809 Health
 Factors to the Health Factor file.  They are in the ONS AA and ONS RA
 namespace.  They get added in the post-init for package NUPA 1.1.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: HEALTH FACTORS
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5850                            IA #: 5850
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100
  DATE CREATED: OCT 03, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: PADP READ OF ORDERS FILE TO GET ORDERS
  ID: OR(100
 GENERAL DESCRIPTION:   The PADP package pulls in Today's orders and
 Active/Pending orders via loops through ^OR(100,"AC".  I would like to request
 an ICR to allow this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP READ OF ORDERS FILE
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5851                            IA #: 5851
  FILE NUMBER: 45                       GLOBAL ROOT: DGPM(
  DATE CREATED: OCT 03, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: PADP PULL OF ADMISSION INFO     ID: DGPM(
 GENERAL DESCRIPTION:   The PADP package pulls in the patient's last admission
 info.  It uses ICR 2090 (Access to ^DPGM("APTT1") and ^DPGM("APTT3")) to get
 the  admission date, but also does a GET1^DIQ call to file 405 to pull in the 
 patient's DIAGNOSIS [SHORT]. I would like to request an ICR to allow this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5852                            IA #: 5852
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: OCT 03, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: PADP PULL OF EMERGENCY CONTACT INFO
  ID: DPT(
GLOBAL REFERENCE: .33
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: .335                      FIELD NAME: E-STREET ADDRESS [LINE 3]
  LOCATION: .33;5                       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;8                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .338                      FIELD NAME: E-ZIP
  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
 GENERAL DESCRIPTION:   The PADP package pulls in the patient's Emergency
 Contact info from the Patient file (#2) and allows the user to change this
 information.  I would like to request an ICR to allow this.  Global
 ^DPT(DFN,.33.  
  
 OAD^VADPT (IA 10061) is used to pull in most of the info except for the 
 emergency contact person's home & work phones which is obtained using 
 $$GET1^DIQ.  
  
 Any changes made to the emergency contact information in the PADP package is
 also written back to the corresponding field in file 2 using DIE.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: EMERGENCY CONTACT
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5853                            IA #: 5853
  FILE NUMBER: 9999999.64               GLOBAL ROOT: AUTTHF(
  DATE CREATED: OCT 03, 2012
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  NAME: PADP PACKAGE READING HEALTH FACTORS
  ID: AUTTHF(
GLOBAL REFERENCE: 0
FIELD NUMBER: .01                       FIELD NAME: FACTOR
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The PADP executables pull in a list of all ONS AA & ONS
 RA Health Factors. This is a FIND^DIC call to file 9999999.64 in an RPC. 
 Global ^AUTTHF.  I would like to request an ICR to allow this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5854                            IA #: 5854
  FILE NUMBER: 601.84                   GLOBAL ROOT: YTT(601.84
  DATE CREATED: OCT 03, 2012            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: File
  NAME: PADP INTERACTION WITH MH ADMINISTRATIONS FILE
  ID: YTT(601.84
GLOBAL REFERENCE: 0
FIELD NUMBER: .01                       FIELD NAME: ADMINISTRATION NUMBER
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DATE GIVEN
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: INSTRUMENT NAME
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 4                         FIELD NAME: DATE SAVED
  LOCATION: 0;5                         ACCESS: Write w/Fileman
FIELD NUMBER: 5                         FIELD NAME: ORDERED BY
  LOCATION: 0;6                         ACCESS: Write w/Fileman
FIELD NUMBER: 6                         FIELD NAME: ADMINISTERED BY
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7                         FIELD NAME: SIGNED
  LOCATION: 0;8                         ACCESS: Write w/Fileman
FIELD NUMBER: 8                         FIELD NAME: IS COMPLETE
  LOCATION: 0;9                         ACCESS: Write w/Fileman
FIELD NUMBER: 9                         FIELD NAME: NUMBER OF QUESTIONS ANSWERED
  LOCATION: 0;10                        ACCESS: Write w/Fileman
FIELD NUMBER: 13                        FIELD NAME: LOCATION
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   The PADP package sets data via Fileman into file 601.84
 (MH ADMINISTRATIONS) when a CIWA or AUDIT-C is done via the program and not by 
 using the MH DLL.  This was added in case a nurse cannot access the DLL for
 some reason.  A new record is created using FILE^DICN and then fields are
 populated using DIE.  
  
 Data is also read from this file in order to create a note in TIU.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5855                            IA #: 5855
  FILE NUMBER: 601.85                   GLOBAL ROOT: YTT(601.85
  DATE CREATED: OCT 03, 2012            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: File
  NAME: PADP INTERACTION WITH MH ANSWERS FILE
  ID: YTT(601.85
GLOBAL REFERENCE: 0
FIELD NUMBER: .01                       FIELD NAME: ANSWER ID
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ADMINISTRATION ID
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 2                         FIELD NAME: QUESTION ID
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 4                         FIELD NAME: CHOICE ID
  LOCATION: 0;4                         ACCESS: Write w/Fileman
FIELD NUMBER: 3                         FIELD NAME: ANSWERS
  LOCATION: 1;0                         ACCESS: Direct Global Write & w/Fileman
 GENERAL DESCRIPTION:   The PADP package sets data via Fileman into file 601.85
 (MH ANSWERS) when a CIWA or AUDIT-C is done via the program and not by using
 the MH DLL.  This was added in case a nurse cannot access the DLL for some 
 reason.  A new record is created using FILE^DICN and then fields are populated
 using DIE.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5856                            IA #: 5856
  DATE CREATED: OCT 04, 2012
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Remote Procedure
  NAME: TIU CREATE RECORD               REMOTE PROCEDURE: TIU CREATE RECORD
 GENERAL DESCRIPTION:   The PADP package would like permission to use RPC TIU
 CREATE RECORD.  This is necessary in order to upload notes from PADP to TIU.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: TIU CREATE RECORD
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM
SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  

NUMBER: 5857                            IA #: 5857
  DATE CREATED: OCT 04, 2012
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Remote Procedure
  NAME: TIU CREATE ADDENDUM RECORD
  REMOTE PROCEDURE: TIU CREATE ADDENDUM RECORD
 GENERAL DESCRIPTION:   The PADP package uses RPC TIU CREATE ADDENDUM RECORD in
 order to create addendums to notes that the package uploads.  I would like to
 request permission to use it.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: TIU CREATE ADDENDUM RECORD
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5858                            IA #: 5858
  DATE CREATED: OCT 04, 2012
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Remote Procedure
  NAME: TIU SIGN RECORD                 REMOTE PROCEDURE: TIU SIGN RECORD
 GENERAL DESCRIPTION:   The PADP package uses RPC TIU SIGN RECORD in order to
 sign, from the package, notes that were just uploaded. I would like to request
 permission to use it.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: TIU SIGN RECORD
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5859                            IA #: 5859
  DATE CREATED: OCT 04, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DG SENSITIVE RECORD ACCESS
  REMOTE PROCEDURE: DG SENSITIVE RECORD ACCESS
 GENERAL DESCRIPTION:   The PADP package uses RPC DG SENSITIVE RECORD ACCESS in
 order to check if the patient just accessed is sensitized. I would like to
 request permission to use it.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5860                            IA #: 5860
  DATE CREATED: OCT 04, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DG SENSITIVE RECORD BULLETIN
  REMOTE PROCEDURE: DG SENSITIVE RECORD BULLETIN
 GENERAL DESCRIPTION:   The PADP package uses RPC DG SENSITIVE RECORD ACCESS in
 order to log access to patients whose record is sensitized. I would like to
 request permission to use it.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: DG SENSITIVE RECORD BULLETIN
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5861                            IA #: 5861
  DATE CREATED: OCT 04, 2012
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: Remote Procedure
  NAME: GMV MANAGER                     REMOTE PROCEDURE: GMV MANAGER
 GENERAL DESCRIPTION:   The PADP package uses RPC GMV MANAGER in order to pull
 in qualifiers of vitals.  The package uses these when the nurse enters vitals
 for their patient. I would like to request permission to use it.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: GMV MANAGER
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5862                            IA #: 5862
  DATE CREATED: OCT 04, 2012
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: Remote Procedure
  NAME: GMV ADD VM                      REMOTE PROCEDURE: GMV ADD VM
 GENERAL DESCRIPTION:   The PADP package uses RPC GMV ADD VM in order to upload
 vitals. I would like to request permission to use it.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: GMV ADD VM
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5863                            IA #: 5863
  DATE CREATED: OCT 05, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORQQVI2 VITALS VALIDATE
  REMOTE PROCEDURE: ORQQVI2 VITALS VALIDATE
 GENERAL DESCRIPTION:   The PADP package uploads Vitals to the vitals package
 and uses RPC ORQQVI2 VITALS VALIDATE to validate the input. I would like to
 request permission to use this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: ORQQVI2 VITALS VALIDATE
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5864                            IA #: 5864
  DATE CREATED: OCT 05, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORQQVI VITALS                   REMOTE PROCEDURE: ORQQVI VITALS
 GENERAL DESCRIPTION:   The PADP package uploads Vitals to the vitals package
 and uses RPC ORQQVI VITALS to upload the input. I would like to request
 permission to use this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: RPC ORQQVI VITALS
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5865                            IA #: 5865
  DATE CREATED: OCT 05, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDX SAVE                      REMOTE PROCEDURE: ORWDX SAVE
 GENERAL DESCRIPTION:   The PADP package uploads Consults to the Consults
 package and uses RPC ORWDX SAVE to upload the input. I would like to request
 permission to use this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5866                            IA #: 5866
  DATE CREATED: OCT 05, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWTPP GETCOS                   REMOTE PROCEDURE: ORWTPP GETCOS
 GENERAL DESCRIPTION:   The PADP package requires that nursing students have a
 cosigner for their note and uses RPC ORWTPP GETCOS to upload the input. I
 would like to request permission to use this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5867                            IA #: 5867
  DATE CREATED: OCT 05, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORQQPXRM REMINDER DETAIL
  REMOTE PROCEDURE: ORQQPXRM REMINDER DETAIL
 GENERAL DESCRIPTION:   The PADP package allows users to view and resolve a
 small list of reminders that may be due on a patient.  It uses RPC ORQQPXRM
 REMINDER DETAIL to view the detail. I would like to request permission to use
 this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: ORQQPXRM REMINDER DETAIL
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5868                            IA #: 5868
  DATE CREATED: OCT 05, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORQQPXRM REMINDER INQUIRY
  REMOTE PROCEDURE: ORQQPXRM REMINDER INQUIRY
 GENERAL DESCRIPTION:   The PADP package allows users to view and resolve a
 small list of reminders that may be due on a patient.  It uses RPC ORQQPXRM
 REMINDER DETAIL to view the reminders. I would like to request permission to
 use this.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: ORQQPXRM REMINDER INQUIRY
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5869                            IA #: 5869
  DATE CREATED: OCT 05, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWPCE SAVE                     REMOTE PROCEDURE: ORWPCE SAVE
 GENERAL DESCRIPTION:   The PADP package uploads a select group of applicable
 Helath Factors and uses RPC ORWPCE SAVE to save the reminders. I would like to
 request permission to use this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: ORWPCE SAVE
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5870                            IA #: 5870
  DATE CREATED: OCT 05, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWRP GET DEFAULT PRINTER
  REMOTE PROCEDURE: ORWRP GET DEFAULT PRINTER
 GENERAL DESCRIPTION:   The PADP package gets the User's default printer by
 using RPC ORWRP GET DEFAULT PRINTER.  I would like to request permission to
 use this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: ORWRP GET DEFAULT PRINTER
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5871                            IA #: 5871
  DATE CREATED: OCT 11, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWORR AGET                     REMOTE PROCEDURE: ORWORR AGET
 GENERAL DESCRIPTION:   The PADP package uses RPC ORWORR AGET to obtain a raw
 list of orders for a patient.  I would like to request permission to use this. 
 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: ORWORR AGET
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5872                            IA #: 5872
  DATE CREATED: OCT 11, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWORR GET4LST                  REMOTE PROCEDURE: ORWORR GET4LST
 GENERAL DESCRIPTION:   The PADP package uses RPC ORWORR GET4LST in conjunction
 with RPC ORWORR AGET to obtain a list of orders for a patient.  I would like
 to request permission to use this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: ORWORR GET4LST
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5873                            IA #: 5873
  DATE CREATED: OCT 11, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDAL32 DEF                    REMOTE PROCEDURE: ORWDAL32 DEF
 GENERAL DESCRIPTION:   The PADP package uses RPC ORWDAL32 DEF to obtain the
 patient's allergies.  I would like to request permission to use this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS:  ORWDAL32 DEF
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5874                            IA #: 5874
  DATE CREATED: OCT 11, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWU CLINLOC                    REMOTE PROCEDURE: ORWU CLINLOC
 GENERAL DESCRIPTION:   The PADP package uses RPC ORWDU CLINLOC in order to
 obtain a list of clinics.  I would like to request permission to use this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: ORWU CLINLOC
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5875                            IA #: 5875
  DATE CREATED: OCT 11, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDAL32 ALLERGY MATCH          REMOTE PROCEDURE: ORWDAL32 ALLERGY MATCH
 GENERAL DESCRIPTION:   The PADP package uses RPC ORWDAL32 ALLERGY MATCH in
 order to search for potential allergies for a patient. I would like to request
 permission to use this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: ORWDAL32 ALLERGY MATCH
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5876                            IA #: 5876
  DATE CREATED: OCT 11, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWU VALIDSIG                   REMOTE PROCEDURE: ORWU VALIDSIG
 GENERAL DESCRIPTION:   The PADP package uses RPC ORWU VALIDSIG in order to
 validate a user's electronic signature.  I would like to request permission to
 use this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: ORWU VALIDSIG
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5877                            IA #: 5877
  DATE CREATED: OCT 11, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDX SEND                      REMOTE PROCEDURE: ORWDX SEND
 GENERAL DESCRIPTION:   The PADP package uses RPC ORWDX SEND in order to allow
 the user to sign their note and consults from the package.  I would like to
 request permission to use this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: ORWDX SEND
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5878                            IA #: 5878
  DATE CREATED: OCT 11, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDAL32 SAVE ALLERGY           REMOTE PROCEDURE: ORWDAL32 SAVE ALLERGY
 GENERAL DESCRIPTION:   The PADP Package uses RPC ORWDAL32 SAVE ALLERGY to save
 new allergies.  I would like to request permission to use this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: ORWDAL32 SAVE ALLERGY
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5879                            IA #: 5879
  DATE CREATED: OCT 11, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWU DT                         REMOTE PROCEDURE: ORWU DT
 GENERAL DESCRIPTION:   The PADP package uses RPC ORWU DT in order to convert
 dates.  I would like to request permission to use this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: ORWU DT
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5880                            IA #: 5880
  DATE CREATED: OCT 11, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORQQPX GET DEF LOCATIONS
  REMOTE PROCEDURE: ORQQPX GET DEF LOCATIONS
 GENERAL DESCRIPTION:   The PADP package uses RPC ORQQPX GET DEF LOCATIONS in
 order to help resolve reminders. I would like to request permission to use
 this.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PADP
KEYWORDS: ORQQPX GET DEF LOCATIONS
SUBSCRIBING PACKAGE: PATIENT ASSESSMENT DOCUM

NUMBER: 5881                            IA #: 5881
  DATE CREATED: OCT 29, 2012            CUSTODIAL PACKAGE: PROBLEM LIST
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: GMPLPXRM                     NAME: PROBLEM LIST DATA
  ID: GMPLPXRM
 GENERAL DESCRIPTION:   This API is designed to work with the Clinical
 Reminders Index, it returns data for a Problem List entry found in the Index.
 The format of the call is PROBDATA^GMPLPXRM(DAS,.DATA).  
  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: Problem List
KEYWORDS: Clinical Reminders Index
COMPONENT/ENTRY POINT: PROBDATA
VARIABLES: DAS                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Clinical Reminders Index DA string, it is
 the last subscript in the Index and identifies the exact location in the
 Problem file where the data is stored.  
  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   This the returned data, passed by reference. Each
 subscript is the name of the field in the Problem file.  
  
  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: NOV 15, 2012

NUMBER: 5882                            IA #: 5882
  DATE CREATED: NOV 09, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORUTL2                       NAME: VEIL ORDER IN CPRS
  ID: ORUTL2
 GENERAL DESCRIPTION:   The purpose of this API is to allow the Laboratory V5.2
 to veil an order to discontinue the display on the Orders Tab only.  
  STATUS: Pending
KEYWORDS: VEIL
KEYWORDS: ORUTL2
COMPONENT/ENTRY POINT: VEIL
VARIABLES: ORIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   The CPRS order number to be veiled.  
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   Pass a 1 to veil the order or a 0 to unveil the
 order.  
SUBSCRIBING PACKAGE: LAB SERVICE

NUMBER: 5883                            IA #: 5883
  DATE CREATED: NOV 19, 2012
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA5883
  STATUS: Pending

NUMBER: 5884                            IA #: 5884
  FILE NUMBER: 53.47                    GLOBAL ROOT: PS(
  DATE CREATED: NOV 19, 2012
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: INFUSION INSTRUCTIONS (#53.47) FILE
  ID: PS(
GLOBAL REFERENCE: PS(53.47
FIELD NUMBER: .01                       FIELD NAME: NAME
FIELD NUMBER: 1                         FIELD NAME: EXPANSION
 GENERAL DESCRIPTION:   Inpatient Medications requests read and write
 permission to the INFUSION INSTRUCTIONS (#53.47) file.  
  
 This file is used to expand abbreviated free text entered in the INFUSION RATE
 (#.08) field in the IV multiple (#100) in the PHARMACY PATIENT (#55) file.  
  STATUS: Active
KEYWORDS: INFUSION INSTRUCTIONS
KEYWORDS: PS(53.47
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: MAY 30, 2014

NUMBER: 5885                            IA #: 5885
  DATE CREATED: NOV 30, 2012            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  ROUTINE: HLOAPI                       NAME: MOVESEG~HLOAPI
  ID: HLOAPI
 GENERAL DESCRIPTION:   These APIs are useful for building HL7 messages.  
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MOVESEG
 COMPONENT DESCRIPTION:   Adds a segment built in the 'traditional' way as an
 array of lines into the HLO message under construction.  
  
VARIABLES: HLMSTATE                     TYPE: Both
 VARIABLES DESCRIPTION:   This variable contains the message that is being
 built.  
  
VARIABLES: SEG                          TYPE: Input
 VARIABLES DESCRIPTION:   This variable contains the segment that is to be
 appended to the message.  
  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   If the segment is not appended to the message, an
 error message is returned.  
  

NUMBER: 5886                            IA #: 5886
  DATE CREATED: NOV 30, 2012            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLOPBLD1
  NAME:    BUILDHDR~HLOPBLD1            ID: HLOPBLD1
 GENERAL DESCRIPTION:   This API is used to build an MSH or BHS segment for an
 HL7 message.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT:    BUILDHDR
 COMPONENT DESCRIPTION:   This API is used to build an MSH segment that serves
 as the HL7 message header.  
  
VARIABLES: HLMSTATE                     TYPE: Input
 VARIABLES DESCRIPTION:   Contains information about the HL7 message.  
  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Specifies the type of message header to build.  
 Should be either MSH or BHS.  
  
VARIABLES: HDR                          TYPE: Output
 VARIABLES DESCRIPTION:   The message header built by calling this API.  
  
  DATE ACTIVATED: DEC 26, 2012

NUMBER: 5887                            IA #: 5887
  DATE CREATED: DEC 06, 2012
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  ROUTINE: TIULP
  NAME: VETERANS POINT OF SERVICE KIOSK CALL TO TIULP
  ID: TIULP
 GENERAL DESCRIPTION:   Veteran's Point of Service (VPS) Kiosk needs to call 
 $$CANENTR^TIULP(TITLE) to verify that a Kiosk user has the required privileges
 to create a TIU note with the Note title selected.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: VPS
KEYWORDS: TIU
COMPONENT/ENTRY POINT: $$CANENTR
VARIABLES: TIUTYP                       TYPE: Input
 VARIABLES DESCRIPTION:   TIUTYP is the IEN in the note in the TIU DOCUMENT
 DEFINITION file (#8925.1).  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

NUMBER: 5888                            IA #: 5888
  DATE CREATED: DEC 13, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DPTLK
  NAME: VIC API                         ID: DPTLK
 GENERAL DESCRIPTION:   Allows patient lookup based on VIC card value.  The
 value can be from a legacy VIC or a newer VIC 4.0 card.  The value can be the
 data from the swipe (magnetic stripe) input or the scan (barcode) of the card. 
 Using applications should not attempt to parse the card value but pass into
 the API the whole card value and allow the API to parse the values needed.  
  
 Example of usage within M code: 
     R X:DTIME Q:'$T!(X=U) 
     X ^%ZOSF("EOFF") R X(1):1 X ^%ZOSF("EON") 
     D RPCVIC^DPTLK(.DFN,X) 
     I DFN<1 W !,"Patient not in database, use ADT options to load patient" Q 
  
 With this example the DFN is now defined to the patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DPTLK
KEYWORDS: VIC
COMPONENT/ENTRY POINT: RPCVIC
 COMPONENT DESCRIPTION:   This entry point should be used to obtain a local
 VistA system lookup based on the card data being consumed.  
VARIABLES: RETURN                       TYPE: Input
 VARIABLES DESCRIPTION:   Pass by reference where the return value should be
 returned.  The return value will either be: 
      DFN = If the patient was successfully found in the local VistA system the
 patient's DFN will be returned 
      -1 = If the patient was not successfully found (i.e. not locally 
 registered or invalid card input) 
VARIABLES: DPTX                         TYPE: Input
 VARIABLES DESCRIPTION:   This should be the entire input from either the
 card's magnetic strip or barcode.  
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  DATE ACTIVATED: NOV 20, 2013

NUMBER: 5889                            IA #: 5889
  DATE CREATED: DEC 13, 2012            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: DG VIC PATIENT LOOKUP           REMOTE PROCEDURE: DG VIC PATIENT LOOKUP
 GENERAL DESCRIPTION:   NOTE:  On 3/31/17, the status for ICR #5889 was changed
 from Pending to Deferred (re)approval until a Release Occurs.  DG*5.3*857
 distributed the DG VIC PATIENT LOOKUP RPC but no known subscribers are
 currently using the RPC.  The ICR could be activated in the future when an
 application requests to be added as a subscriber to the ICR.  
  
  
 Allows patient lookup based on VIC card value.  The value can be from a legacy
 or a newer VIC 4.0 card.  The value can be the data from the swipe (magnetic
 stripe) input or the scan (barcode) of the card.  Using applications should
 not attempt to parse the card value but pass into the RPC the whole card value
 and allow the RPC to parse the values needed.  
  
 INPUT PARAMETER: DPTX                   PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 255              REQUIRED: YES 
   SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  This should be the entire input from either the Magnetic Strip or the 
  Barcode.  
  
 RETURN PARAMETER DESCRIPTION:   
  If the patient is known locally the patient's DFN is returned.  If not 
  then a -1 is returned.  
  STATUS: Deferred (re)approval until a Release Occurs
  DURATION: Till Otherwise Agreed
KEYWORDS: DPTLK
KEYWORDS: VIC
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS

NUMBER: 5890                            IA #: 5890
  DATE CREATED: DEC 19, 2012
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORUTL3
  NAME: FIND NATURE OF ORDER            ID: ORUTL3
 GENERAL DESCRIPTION:   The purpose of this API is to provide a way for the
 Pharmacy application(s) to retrieve the nature of order from a specified CPRS 
 order number.  
  STATUS: Active
KEYWORDS: NATURE
KEYWORDS: ORDER
COMPONENT/ENTRY POINT: NATURE
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   This the CPRS order number and order action for use
 in retrieving the nature of order. The input is in the format: 
  
       CPRS order number;order action 
  
 If no order action is specified, the routine will find the most recent order
 action that contains a nature of order and return that information.  
VARIABLES: RETURN                       TYPE: Output
 VARIABLES DESCRIPTION:   If the order number or the order action is invalid,
 the call will return a 0.  
  
 If the nature of order can be determined, the return will be: 
  
    NATURE OF ORDER IEN^NATURE OF ORDER CODE^NAME^99ORN 
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Added 2/24/26, effective with patch DVBA*2.7*257.  This
 is for the BID/CAPRI project to existing outpatient history reports in AMIE
 can display the Nature of Order field.  
  DATE ACTIVATED: JUL 25, 2014

NUMBER: 5891                            IA #: 5891
  FILE NUMBER: 18.12                    GLOBAL ROOT: XOB(18.12,
  DATE CREATED: JAN 03, 2013            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: WEB SERVER File (#18.12) access
  ID: XOB(18.12,
GLOBAL REFERENCE: XOB(18.12,DA,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: SERVER
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This agreement allows read-only access to the WEB
 SERVER File (#18.12).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   Pharmacy Data Management needs read access to the
 SERVER Field (#.04) of the WEB SERVER File (#18.12) for the PEPS entry.  
  DATE ACTIVATED: MAY 30, 2014

NUMBER: 5892                            IA #: 5892
  DATE CREATED: JAN 16, 2013            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGENA4                       NAME: DBIA5892
  ID: DGENA4                            STATUS: Pending
  DURATION: Till Otherwise Agreed
KEYWORDS: DSS
COMPONENT/ENTRY POINT: $$CATEGORY(DFN,STATUS)
 COMPONENT DESCRIPTION:   This entry point returns the enrollment category for
 a patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number of the Patient from
 the PATIENT (#2) File.  
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   This variable is optional.  If passed in, the call
 will return the enrollment category for this status rather than the veteran's
 current enrollment status.  
VARIABLES: $$CATEGORY                   TYPE: Output
 VARIABLES DESCRIPTION:   This represents the current enrollment category for
 the patient or the enrollment category of the status passed in, if available.
 Otherwise, it defaults to the "Not Enrolled" category. This will be one of
 three values: "E" for Enrolled; "N" for Not Enrolled; "P" for In Process.  
COMPONENT/ENTRY POINT: $$ENRSBGRP(DFN)
 COMPONENT DESCRIPTION:   Returns the patient current ENROLLMENT SUBGROUP if
 defined, otherwise returns NULL.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number of the Patient from
 the PATIENT (#2) File. 
VARIABLES: $$ENRSBGRP                   TYPE: Output
 VARIABLES DESCRIPTION:   This represents the ENROLLMENT SUBGROUP (#.12) Field
 value from the PATIENT ENROLLMENT File (#27.11) of the patient's current
 enrollment record.  
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   DSS EXTRACTS requests patient enrollment information
 for collection into their monthly extracts.  
  DATE ACTIVATED: APR 10, 2013

NUMBER: 5893                            IA #: 5893
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870,
  DATE CREATED: JAN 17, 2013            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RETRIEVE LINK DATA FOR PSIM
  ID: HLCS(870,
GLOBAL REFERENCE: HLCS(870,0
FIELD NUMBER: .02                       FIELD NAME: INSTITUTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DNS DOMAIN
  LOCATION: 0;8                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: HLCS(870,400
FIELD NUMBER: 400.01                    FIELD NAME: TCP/IP ADDRESS
  LOCATION: 400;1                       ACCESS: Read w/Fileman
FIELD NUMBER: 400.02                    FIELD NAME: TCP/IP PORT
  LOCATION: 400;2                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: HLCS(870,'C'
 GENERAL DESCRIPTION:   The MPI will provide a new RPC for PSIM/TK to call to
 retrieve HL7 Logical Link file (#870) data, specifically the DNS DOMAIN
 (#.08), TCP/IP address (#400.01) and TCP/IP Port (#400.02) for a specified
 VistA instance or for all VistAs.  Name:  MPI HL7 LOGICAL LINK DATA Pass in
 "ALL" or Station Number Returned:  Station Number^DNS Name^TCP/IP
 Address^TCP/IP Port for each entry required.  If there isn't a link for that
 station number, return error message.  
  
 No write to the records, only retrieving data using FileMan API, $$GET1^DIQ,
 from entries of file #870 in the MPI account: 
  
    GLOBAL REFERENCE: 
         ^HLCS(870, 
           .02      INSTITUTION 
           .08      DNS DOMAIN 
           400.01   TCP/IP ADDRESS 
           400.02   TCP/IP PORT 
           "C" X-REF 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LINK FOR PSIM
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   Provide a new RPC for PSIM/TK to call to retrieve HL7
 Logical Link file (#870) data 
  DATE ACTIVATED: JAN 22, 2013

NUMBER: 5894                            IA #: 5894
  DATE CREATED: JAN 24, 2013            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGSDU
  NAME: DBIA5894                        ID: DGSDU
 GENERAL DESCRIPTION:   This routine brings back encounter information for a
 patient based on the input values defined by the calling application. 
 SCAN~DGSDU calls several supported APIs documented in ICR #2548.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DGSDU
COMPONENT/ENTRY POINT: SCAN
 COMPONENT DESCRIPTION:   This call is used to query patient encounters.  
VARIABLES: DGINDX                       TYPE: Input
 VARIABLES DESCRIPTION:   INDEX NAME PROPERTY OF THE QUERY OBJECT 
VARIABLES: DGVAL                        TYPE: Input
 VARIABLES DESCRIPTION:   Array of data elements for start/end of search.  
   DGVAL("DFN") = PATIENT DFN 
   DGVAL("BDT") = BEGIN DATE 
   DGVAL("EDT") = END DATE 
   DGVAL("VIS") = ENCOUNTER FILE IEN 
VARIABLES: DGFILTER                     TYPE: Input
 VARIABLES DESCRIPTION:   The executable code used to screen entries.  
VARIABLES: DGCBK                        TYPE: Input
 VARIABLES DESCRIPTION:   The executable scan callback code to create the
 result set.  
VARIABLES: DGCLOSE                      TYPE: Input
 VARIABLES DESCRIPTION:   Flag that says whether or not to close the query
 object.  
  1 = Perform close 
  0 or Null = Do not close object 
VARIABLES: DGQUERY                      TYPE: Input
 VARIABLES DESCRIPTION:   The number of current query, if not a new query. If
 passed by reference and query closed, this variable will be nulled.  
  
 NOTE:  When using this call, the variable passed as DGQUERY must be newed or
 killed in the calling program 
VARIABLES: DGDIR                        TYPE: Input
 VARIABLES DESCRIPTION:   The direction of the scan (optional).  
  Null, undefined or "FORWARD": Scans forwards.  
  "BACKWARD" : Scans backwards 
SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL
 SUBSCRIBING DETAILS:   SCAN~DGSDU is called from Beneficiary Travel routine
 DGBT2 to query and display Outpatient Encounter data elements for a patient on
 Beneficiary Travel Claim Information <Screen 2>.  
  DATE ACTIVATED: MAR 25, 2013

NUMBER: 5895                            IA #: 5895
  GLOBAL ROOT: DD(52.6                  DATE CREATED: JAN 25, 2013
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PSS*1*174 POST INSTALL WITH DD(52.6
  ID: DD(52.6
 GENERAL DESCRIPTION:   This is a one-time ICR valid only for the Post-Install 
 Routine for patch PSS*1.0*174.  
  
 A new field STRENGTH (#19) has been added to the IV ADDITIVES File (#52.6). 
  
 The new STRENGTH (#19) field will be displayed on any lookup performed on the
 IV ADDITIVES File (#52.6) by creating a new "W19" node by direct global set
 into ^DD(52.6,0,"ID" by Post-Install Routine PSS0174.  
  
 ^DD(52.6,0,"ID","W19") will be set to "W ""   Additive Strength:
 "",$S($P(^(0),U,15)="""":""N/A"", 1:$P(^(0),U,15)_""
 ""_$$GET1^DIQ(52.6,$P(^(0),U,3)_"","",2))" 
  
  STATUS: Active                        DURATION: Next Version
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  DATE ACTIVATED: FEB 04, 2013

NUMBER: 5896                            IA #: 5896
  DATE CREATED: JAN 31, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWRPP
  NAME: ORWRP PRINT REPORT              REMOTE PROCEDURE: ORWRP PRINT REPORT
  ID: ORWRPP                            STATUS: Active
KEYWORDS: PRINT
KEYWORDS: VPS
KEYWORDS: ORWRP
KEYWORDS: ORWRPP
COMPONENT/ENTRY POINT: PRINT
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   Veteran's Point of Service (VPS) Kiosk has the need to
 print a report using ORWRP PRINT REPORT RPC.  
  DATE ACTIVATED: OCT 02, 2013

NUMBER: 5897                            IA #: 5897
  FILE NUMBER: 8925.1                   GLOBAL ROOT: TIU(8925.1
  DATE CREATED: FEB 04, 2013
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU DOCUMENT CLASS TITLES QUERY
  ID: TIU(8925.1
GLOBAL REFERENCE: TIU(8925.1,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the technical name, 3-60 characters, not starting
 with punctuation. If OBJECT, Name must be unique among all object Names, 
 Abbreviations, and Print Names.  
FIELD NUMBER: .03                       FIELD NAME: PRINT NAME
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Print Name is used in lists of documents and as document
 Title in the Patient  Chart.  3-60 Characters.  If OBJECT, Print Name must be
 unique among object Names/Abbreviations/PrintNames, and uppercase.  
FIELD NUMBER: .04                       FIELD NAME: TYPE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   SET OF CODES: 'CL' FOR CLASS; 'DC' FOR DOCUMENT CLASS;
 'DOC' FOR TITLE; 'CO' FOR COMPONENT; 'O' FOR OBJECT 
                                         
 Types CLASS and DOCUMENT CLASS group documents.  TITLES are used to enter 
 documents.  COMPONENTS are sections of documents.  OBJECTS are M code for use
 in Boilerplate Text.  
FIELD NUMBER: .07                       FIELD NAME: STATUS
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Documents can be entered on ACTIVE Titles.  Only the
 Owner can enter a document on TEST Titles.  Only INACTIVE Document Definitions
 can be edited.  
GLOBAL REFERENCE: TIU(8925.1,10,'AC'
 GLOBAL DESCRIPTION:   This cross-reference on Subfile ITEM lists Titles by
 Sequence Number.  
GLOBAL REFERENCE: TIU(8925.1,10.'C'
 GLOBAL DESCRIPTION:   This cross-reference on subfile ITEM lists Titles in
 alphabetic order.  
GLOBAL REFERENCE: TIU(8925.1,'B'
 GENERAL DESCRIPTION:   This agreement permits Fileman reads of file 8925.1 to
 find all the Titles under a particular Document Class and some of their
 attributes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DOCUMENT CLASS
KEYWORDS: TITLES
SUBSCRIBING PACKAGE: MYHEALTHEVET
 SUBSCRIBING DETAILS:   MHV has been tasked to report all the Titles of
 document class SECURE MESSAGING DOCUMENTS.  This report is to be used by the
 MHV SM Application.  The extraction routine MHVXTIU reads the following
 information from the DOCUMENT DEFINITION (#8925.1) File.  
      ^TIU(8925.1,'B',DOCDEF, 
         The purpose of this index read is to loop through the TIU DOCUMENT
 DEFINITION file screening on SECURE MESSAGING DOCUMENTS document class.  
      ^TIU(8925.1, 
        .01      NAME                0;1          Read w/Fileman 
        .03      PRINT NAME   0;3          Read w/Fileman 
        .04      TYPE                   0;4          Read w/Fileman 
         The purpose of this read is to enable screening by document class 
 (DC).  
        .07     STATUS              0;7          Read w/Fileman 
      ^TIU(8925.1,10,'AC',SUB 
         The purpose of this index read to screen for SECURE MESSAGING DOCUMENT
 titles sequence numbers.  
        ^TIU(8925.1,10,'C',SUB 
         The purpose of this index read is to screen for SECURE MESSAGING 
 DOCUMENT titles in alphabetical order.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 10/18/22, effective with Patch SD*5.3*827 in
 which a new RPC 'SDES GET TIU DOC BY CONTEXT'  is created that needs to
 retrieve TIU data tied to the location/clinic ID. One of the input parameters
 of the RPC is the CLASS IEN. Before retrieving the TIU data, the new RPC needs
 to validate the existence of the CLASS IEN in TIU DOCUMENT DEFINITION File
 #8925.1 in order to successfully retrieve the TIU DATA.  
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 7/22/26, effective with patch CDSP*1*4, where
 CDSP performs lookups in file 8925.1 to return Consult Request Titles for the
 CDSP APP AI Scribe. AI Scribe is a commercial application that allows the
 provider to turn on at the beginning of a clinical Visit and listen to the
 visit, make a transcription and submit to AI and the result is a properly 
 formatted SOAP note for the provider to review and submit to VistA.  This is
 where CDSP comes in to take the text of the commercial product (the call a
 FHIR endpoint to send the text to us) and write an unsigned note for the
 provider to then review and sign in CPRS.  There is no AI in the VistA code in
 CDSP patches.  This ICR supports generating a properly formatted list of note
 titles, including if it is a consult note title and provide it to the Vendor
 so the provider can select the proper note title when submitting to our API.  
 CDSP has written the Routine and RPC for this. 
  DATE ACTIVATED: FEB 04, 2013

NUMBER: 5898                            IA #: 5898
  DATE CREATED: FEB 05, 2013
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU DOCUMENT IEN
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: TIU
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   Veteran's Point of Service (VPS) Kiosk has the need to
 store TIU DOCUMENT IEN. This IEN is the returned value from calling the TIU
 CREATE RECORD rpc and will be used to reference the specific note from VPS
 MRAR PDO. VPS is aware that this stored pointer may be broken caused by
 retraction or deletion of the TIU document.  
  DATE ACTIVATED: NOV 06, 2014

NUMBER: 5899                            IA #: 5899
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: FEB 05, 2013            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IFCAP
  ID: VA(200,
GLOBAL REFERENCE: VA(200,DUZ,51
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Removal of PRCFA SUPERVISOR key from file #200 (NEW
 PERSON) for terminated employees. Currently the key has a KEEP AT TERMINATE
 set to YES and the key is changing (via patch PRC*5.1*168) KEEP AT TERMINATE
 to NO.  This will satisfy fiscal audits that show the key falsely assigned to
 terminated employees.  
  
 This one-time key removal for terminated employees will be done by a post
 install routine PRC168P that will flip the KEEP AT TERMINATE setting for PRCFA
 SUPERVISOR key to NO and remove key from any terminated employee in file #200. 
 
  STATUS: Active
KEYWORDS: PRCFA SUPERVISOR KEY REMOVAL
KEYWORDS: IFCAP
SUBSCRIBING PACKAGE: IFCAP
  DATE ACTIVATED: APR 12, 2013

NUMBER: 5900                            IA #: 5900
  FILE NUMBER: 19.1                     GLOBAL ROOT: DIC(19.1
  DATE CREATED: FEB 06, 2013            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IFCAP
  ID: DIC(19.1
GLOBAL REFERENCE: DIC(19.1,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: KEEP AT TERMINATE
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Modification of PRCFA SUPERVISOR key field KEEP AT
 TERMINATE from 'YES' to 'NO'. Currently the key has KEEP AT TERMINATE set to
 YES and the key is changing (via patch PRC*5.1*168) KEEP AT TERMINATE to NO. 
 This will satisfy fiscal audits that show the key still assigned to terminated 
 employees.  
  
 This one-time field update of KEEP AT TERMINATE will be done by a post install
 routine PRC168P that will flip the KEEP AT TERMINATE setting for the PRCFA
 SUPERVISOR key to NO and remove the key from any terminated employee in file
 #200.  
  STATUS: Active
KEYWORDS: IFCAP KEY MODIFICATION
KEYWORDS: KEEP AT TERMINATE
SUBSCRIBING PACKAGE: IFCAP
  DATE ACTIVATED: APR 12, 2013

NUMBER: 5901                            IA #: 5901
  DATE CREATED: MAR 04, 2013
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIULA
  NAME: PROMPT USER FOR DIVISION        ID: TIULA
 GENERAL DESCRIPTION:   Routine TIULA calls Registration routine VAUTOMA (ICR
 #664) to prompt the user for one, many or all Medical Center (#40.8)
 divisions.  If one or many divisions are selected, routine TIULA modifies the
 array returned by DIVISION~VAUTOMA to return the IEN from the Institution (#4)
 file for the selected division(s).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DIVISION
COMPONENT/ENTRY POINT: SELDIV
VARIABLES: SELDIV                       TYPE: Output
 VARIABLES DESCRIPTION:   The return status of the call. Possible values are: 
   -1  The user entered a caret at the prompt if 
       the site is multidivisional 
    0  The INSTITUTION file (#4) pointer is missing 
       for the division(s) returned in BADDIV 
    1  Successful selection of one or more 
       divisions 
VARIABLES: BADDIV                       TYPE: Output
 VARIABLES DESCRIPTION:   Comma delimited list of MEDICAL CENTER DIVISION file
 entries selected by the user that do not have a corresponding entry in the
 INSTITUTION file.  
VARIABLES: TIUDI                        TYPE: Output
 VARIABLES DESCRIPTION:   Array containing the selected division(s). The array
 will be undefined if the user did not enter any selections at the prompt,
 which means the user wants all divisions, or the user entered a caret at the
 prompt if the site is multidivisional. The array will be defined if the user
 selects one or more (but not all) divisions or the site is not
 multidivisional. The array is formatted as follows: 
  
    TIUDI(FILE #40.8 IEN)=CORRESPONDING FILE #4 IEN 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: APR 10, 2013

NUMBER: 5902                            IA #: 5902
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: MAR 08, 2013            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: New Person Telephone and e-Mail Address
  ID: VA(200,
GLOBAL REFERENCE: VA(200,
FIELD NUMBER: .132                      FIELD NAME: OFFICE PHONE
  LOCATION: .13;2                       ACCESS: Read w/Fileman
FIELD NUMBER: .135                      FIELD NAME: COMMERCIAL PHONE
  LOCATION: .13;5                       ACCESS: Read w/Fileman
FIELD NUMBER: .151                      FIELD NAME: EMAIL ADDRESS
  LOCATION: .15;1                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   IFCAP needs to extract contact information including
 telephone numbers and e-mail address from user's record in the New Person file
 (#200) for display and transmission via HL7 messages to external system.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: COMMERCIAL PHONE
KEYWORDS: OFFICE PHONE
KEYWORDS: EMAIL ADDRESS
SUBSCRIBING PACKAGE: IFCAP

NUMBER: 5903                            IA #: 5903
  DATE CREATED: MAR 11, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORCSAVE2
  NAME: STATUS Portion of ORCSAVE2      ID: ORCSAVE2
 GENERAL DESCRIPTION:   This ICR allows the STATUS (#5) field of an order in
 the ORDERS (#100) file to be set to a predetermined value depending on the
 needs of the routine calling STATUS^ORCSAVE2.  
  STATUS: Active
KEYWORDS: ORCSAVE2
KEYWORDS: STATUS
COMPONENT/ENTRY POINT: STATUS
 COMPONENT DESCRIPTION:   Update the status of a CPRS order.  
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the CPRS order to be
 updated.  
VARIABLES: ST                           TYPE: Input
 VARIABLES DESCRIPTION:   The new status of the order.  
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   Lab orders are frequently written in advance of the
 patient's next appointment. If circumstances force the patient to miss the
 appointment, those lab orders are not considered valid after a certain period
 of time.  
  
 Having access to this update code gives the Lab package the ability to 
 'obsolete' or lapse pending orders that are no longer considered valid.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   The status of a medication in the ORDERS (#100) file
 might be erroneously active when the status in the corresponding medication
 file - PRESCRIPTION (#52) or PHARMACY PATIENT (#55) - is expired or 
 discontinued.  Sites have found that these orders are typically several years
 old, and the root cause that existed at that time is unknown.  
  
 Patch PSO*7.0*546 introduced option "Medication Status Check" which allows a
 site to search for medication order status mismatches and correct the status
 in the ORDERS (#100) file if that status is erroneously "active".  
  
 The ability to call STATUS^ORCSAVE2 is necessary so that the "Medication 
 Status Check" option can correct the ORDERS (#100) file status.  
SUBSCRIBING PACKAGE: CMOP
 SUBSCRIBING DETAILS:   The status of a medication in the ORDERS (#100) file
 might be erroneously active when the status in the corresponding medication
 file - PRESCRIPTION (#52) or PHARMACY PATIENT (#55) - is expired or 
 discontinued.  Sites have found that these orders are typically several years
 old, and the root cause that existed at that time is unknown.  
  
 Patch PSO*7.0*546 introduced option "Medication Status Check" which allows a
 site to search for medication order status mismatches and correct the status
 in the ORDERS (#100) file if that status is erroneously "active".  
  
 The ability to call STATUS^ORCSAVE2 is necessary so that the "Medication 
 Status Check" option can correct the ORDERS (#100) file status.  
  DATE ACTIVATED: MAR 27, 2013

NUMBER: 5904                            IA #: 5904
  DATE CREATED: MAR 12, 2013            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPLBL
  NAME: DG PRINT PATIENT LABEL          ID: DGPLBL
 GENERAL DESCRIPTION:   Routine DGPLBL provides a generic patient demographics
 label print that includes Patient Name, SSN, DOB and an optional inpatient
 location (ward and bed).  Support for various printer types (i.e. bar code,
 laser, etc.) is provided using the CONTROL CODES (#3.2055) subfile of the
 TERMINAL TYPE (#3.2) file.  The control code mnemonics are documented in DBIA# 
 3435.  
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: DGPLBL
KEYWORDS: LABEL
KEYWORDS: PRINT
COMPONENT/ENTRY POINT: START
 COMPONENT DESCRIPTION:   This entry point prints patients labels and requires
 that the following variables be defined prior to the call.  
  
   DGDFNS   Array subscripted by pointer to Patient (#2) file 
   DGLBCNT  Number of labels to print per patient.  
   DGLPL    Number of lines per label.  
   DGLOC    Print Ward location flag 
  
  
 START^DGPLBL is the entry point called by TaskMan when a label is queued for
 printing through the Registration application option.  If TaskMan queueing is
 not being used by the subscribing application, the subscribing application is
 responsible for setting these variables prior to calling START^DGPLBL.  
VARIABLES: DGDFNS                       TYPE: Input
 VARIABLES DESCRIPTION:   Array subscripted by pointer to Patient (#2) file 
VARIABLES: DGLBCNT                      TYPE: Input
 VARIABLES DESCRIPTION:   Number of labels to print per patient.  
VARIABLES: DGLPL                        TYPE: Input
 VARIABLES DESCRIPTION:   Number of lines per label.  
VARIABLES: DGLOC                        TYPE: Input
 VARIABLES DESCRIPTION:   Print Ward location flag 
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (KIOSKS) has a need to print
 patient labels at secure label printers stationed in staff areas. The input
 parameters (see VARIABLES below) and output device will be provided by the VPS
 KIOSK Application (VetLink).  
  DATE ACTIVATED: APR 12, 2016

NUMBER: 5905                            IA #: 5905
  DATE CREATED: MAR 18, 2013            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPWB
  NAME: DG PRINT WRISTBAND              ID: DGPWB
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: ORWRP
KEYWORDS: PRINT
KEYWORDS: WRISTBAND
COMPONENT/ENTRY POINT: SET
 COMPONENT DESCRIPTION:   This entry point prints the selected Patient's
 wristband. The following VARIABLES will be defined by VPS before calling the
 entry point (SET^DGPWB).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to patient file (#2).  
VARIABLES: WARD                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to Ward Location file (#42).  
COMPONENT/ENTRY POINT: DIVISION
 COMPONENT DESCRIPTION:   Given patient's ward location, this boolean entry
 point will return 1 if the ward's division print patient wristband, otherwise
 it will return 0 
VARIABLES: WARD                         TYPE: Input
 VARIABLES DESCRIPTION:   Patient's Ward Location - Pointer to Ward Location
 file (#42).  
VARIABLES: RETURN VALUE                 TYPE: Output
 VARIABLES DESCRIPTION:   Boolean (1/0) to indicate whether or not the given
 ward's division prints patient wristband 
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (KIOSKS) has a need to print
 patient wristbands at secure printers stationed in staff areas. The input
 parameters and output device will be provided by the VPS KIOSK application
 (VetLink).  
  DATE ACTIVATED: APR 10, 2015

NUMBER: 5906                            IA #: 5906
  FILE NUMBER: 50.7                     GLOBAL ROOT: DD(
  DATE CREATED: MAR 26, 2013            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RESTRICT IV FLAG WRITE ACCESS
  ID: DD(
 GENERAL DESCRIPTION:   This request is to allow the Pharmacy Data Management
 package to edit the IV FLAG field to restrict write access from Fileman.  
  
 This change will be used in patch PSS*1.0*150 only. 
  
  STATUS: Active                        DURATION: Next Version
KEYWORDS: IV FLAG
KEYWORDS: 50.7
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT

NUMBER: 5907                            IA #: 5907
  FILE NUMBER: 399                      GLOBAL ROOT: DD(
  DATE CREATED: MAR 26, 2013            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DELETE FIELD 64 FROM FILE 399
  ID: DD(
 GENERAL DESCRIPTION:   This agreement is to make a fileman call to delete the 
 ICD DIAGNOSIS CODE field (#64) from the BILL/CLAIMS file (#399).  
  
 This agreement is only for patch IB*2.0*481. 
  
  STATUS: Active                        DURATION: Next Version
KEYWORDS: 399
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAR 26, 2013

NUMBER: 5908                            IA #: 5908
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT(
  DATE CREATED: MAR 28, 2013            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VBECS CPT ACCESS
  ID: ICPT(
 GENERAL DESCRIPTION:   
   Now covered by supported ICR #5408,CPT/HCPS Procedure File 81.              
 ^ICPT(D0,0)       CPT CODE            0;1      Read w/Fileman 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 09, 2015
KEYWORDS: CPT
KEYWORDS: HCPCS
KEYWORDS: VBECS
SUBSCRIBING PACKAGE: VBECS
 SUBSCRIBING DETAILS:   VBECS requests permission to read with FileMan the CPT
 file (#81) using the "D" index to identify entries associated with the
 "PATHOLOGY AND LABORATORY SERVICES" CPT CATEGORY.  
  
 A screen will be used to only identify entries with a matching CPT CATEGORY,
 SOURCE of "H" for HCPCS, and active STATUS. The screen will use the function
 $$CPT^ICPTCOD (ICR 1995) to validate the entries in the CPT file.  
  
 The CPT Code and short description will be obtained using the API 
 $$CPT^ICPTCOD (ICR 1995).  
  DATE ACTIVATED: APR 15, 2013

NUMBER: 5909                            IA #: 5909
  FILE NUMBER: 53.79                    GLOBAL ROOT: PSB(53.79,
  DATE CREATED: APR 11, 2013            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VPR use of BCMA Med Log
  ID: PSB(53.79,
GLOBAL REFERENCE: PSB(53.79,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This includes global read of "AORDX" cross reference.  
FIELD NUMBER: .06                       FIELD NAME: ACTION DATE/TIME
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: ACTION STATUS
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: ACTION BY
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Field added for VPR*1*3.  
GLOBAL REFERENCE: PSB(53.79,D0,.1)
FIELD NUMBER: .16                       FIELD NAME: INJECTION SITE
  LOCATION: .1;6                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Field added for VPR*1*3.  
GLOBAL REFERENCE: PSB(53.79,D0,.5,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DISPENSE DRUG
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DOSES ORDERED
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DOSES GIVEN
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: UNIT OF ADMINISTRATION
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   All fields on this node added for VPR*1*3.  
GLOBAL REFERENCE: PSB(53.79,D0,.6,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ADDITIVES
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DOSE ORDERED
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DOSE GIVEN
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: UNIT OF ADMINISTRATION
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   All fields on this node added for VPR*1*3.  
GLOBAL REFERENCE: PSB(53.79,D0,.7,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SOLUTIONS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DOSE ORDERED
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DOSES GIVEN
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: UNIT OF ADMINISTRATION
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   All fields on this node added for VPR*1*3.  
GLOBAL REFERENCE: PSB(53.79,D0,.2)
FIELD NUMBER: .21                       FIELD NAME: PRN REASON
  LOCATION: .2;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .22                       FIELD NAME: PRN EFFECTIVENESS
  LOCATION: .2;2                        ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   All fields on this node added for VPR*1*3.  
GLOBAL REFERENCE: PSB(53.79,D0,.3,D1,0)
FIELD NUMBER: .01                       FIELD NAME: COMMENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ENTERED BY
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: ENTERED DATE/TIME
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   All fields on this node added for VPR*1*3.  
 GENERAL DESCRIPTION:   This agreement documents VPR read access to file
 #53.79.  
  
 Several fields have been added to this ICR to document their use in patch 
 VPR*1*3; this patch was not released nationally and is not installed at any VA
 site, but is available through OSEHRA.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: JAN 16, 2018

NUMBER: 5910                            IA #: 5910
  DATE CREATED: MAY 02, 2013            CUSTODIAL PACKAGE: RPC BROKER
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XWB IM HERE
  REMOTE PROCEDURE: XWB IM HERE         STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: BHL
KEYWORDS: BEHAVIORAL HEALTH LAB
KEYWORDS: CAPITAL SOLUTION DESIGN
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   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.  
  
 Added 5/13/25 effective with YS*5.01*236 patch. Cloud application MHA is
 migrating from VistALink to Cocytus, to communicate with VistA. In order to
 continue to have login functionality with Cocytus, MHA requires use of this
 RPC.  
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   Added 9/27/19 
  DATE ACTIVATED: MAY 13, 2013

NUMBER: 5911                            IA #: 5911
  DATE CREATED: MAY 02, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWU16 USERINFO
  REMOTE PROCEDURE: ORWU16 USERINFO     STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: BHL
KEYWORDS: BEHAVIORAL HEALTH LAB
KEYWORDS: CAPITAL SOLUTION DESIGN
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   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.  
  
 RPC returns DUZ^NAME^SIGNAUTH^ISPROVIDER.  BHL uses the DUZ for its 
 application.  
  DATE ACTIVATED: MAY 15, 2013

NUMBER: 5912                            IA #: 5912
  DATE CREATED: MAY 09, 2013            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOREJP2
  NAME: PSOREJP2                        ID: PSOREJP2
 GENERAL DESCRIPTION:   Retrieve the most recent last date of service and last
 days supply from the previous prescription.  
  STATUS: Active
KEYWORDS: PREVRX
KEYWORDS: LAST DATE OF SERVICE
KEYWORDS: LAST DAYS SUPPLY
KEYWORDS: PREVIOUS PRESCRIPTION
COMPONENT/ENTRY POINT: PREVRX
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN 
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Fill# 
VARIABLES: COB                          TYPE: Input
 VARIABLES DESCRIPTION:   Payer sequence#. Defaults to 1 if not passed in.  
VARIABLES: LDOS                         TYPE: Output
 VARIABLES DESCRIPTION:   Last Date of Service.  Pass by reference.  Fileman
 date format.  
VARIABLES: LDAYS                        TYPE: Output
 VARIABLES DESCRIPTION:   Last Days Supply.  Pass by reference.  
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: JUL 23, 2013

NUMBER: 5913                            IA #: 5913
  FILE NUMBER: 6914                     GLOBAL ROOT: ENG(6914
  DATE CREATED: MAY 14, 2013            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VIAAEAD
  NAME: READ/WRITE ACCESS TO FILE #6914 (EQUIPMENT INV.)
  ID: VIAAEAD
GLOBAL REFERENCE: ENG(6914,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ENTRY NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .6                        FIELD NAME: DATE ENTERED
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: PARENT SYSTEM
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: MFGR. EQUIPMENT NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: TYPE OF ENTRY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: ENG(6914,D0,1)
FIELD NUMBER: 1                         FIELD NAME: MANUFACTURER
  LOCATION: 1;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: MODEL
  LOCATION: 1;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: SERIAL #
  LOCATION: 1;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: EQUIPMENT CATEGORY
  LOCATION: 1;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: ENG(6914,D0,2)
FIELD NUMBER: 11                        FIELD NAME: PURCHASE ORDER
  LOCATION: 2;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: TOTAL ASSET VALUE
  LOCATION: 2;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: ACQUISITION DATE
  LOCATION: 2;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 18                        FIELD NAME: CATEGORY STOCK NUMBER
  LOCATION: 2;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 19                        FIELD NAME: CMR
  LOCATION: 2;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: PHYSICAL INVENTORY DATE
  LOCATION: 2;13                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: ENG(6914,D0,3)
FIELD NUMBER: 20                        FIELD NAME: USE STATUS
  LOCATION: 3;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 21                        FIELD NAME: SERVICE POINTER
  LOCATION: 3;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 22                        FIELD NAME: DISPOSITION DATE
  LOCATION: 3;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 24                        FIELD NAME: LOCATION
  LOCATION: 3;5                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: ENG(6914,D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: RESPONSIBLE SHOP
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: ENG(6914,D0,9)
FIELD NUMBER: 60                        FIELD NAME: STATION NUMBER
  LOCATION: 9;5                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Request permission for READ/WRITE access via FileMan
 calls to file #6914 in order to complete RPC queries from IntelligentInsites,
 and to update the file in VistA when requested. This is part of the RTLS
 National project to facilitate tracking equipment updates in Engineering,
 while keeping IntelligentInsites with up to date information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
COMPONENT/ENTRY POINT: RTLSDTEX
 COMPONENT DESCRIPTION:   Entry point to collect all the data from the fields
 listed above to be sent to InSites. RPC parameters list: RETSTA, REQDATA,
 DATAID. This is a read only event.  
VARIABLES: RETSTA                       TYPE: Output
 VARIABLES DESCRIPTION:   This the return status array.  The array contains all
 the fields listed from file #6914.  
VARIABLES: REQDATA                      TYPE: Input
 VARIABLES DESCRIPTION:   Identifies the type of data required: EQUIPMENT,
 CATEGORY, or LOCATION 
VARIABLES: DATAID                       TYPE: Input
 VARIABLES DESCRIPTION:   Identifies what data is to be returned for REQDATA:
 "ALL" is the data for a given REQDATA, or an AEMSID for individual item data,
 or Category ID for an individual category, or Location IEN for an individual
 location.  
COMPONENT/ENTRY POINT: EQMVUPD
 COMPONENT DESCRIPTION:   This tag will be called to update fields #23
 (Physical Inventory Date) and #24 (Location) with data received in InSites via
 the active tags in the equipment. RPC parameters list: RETSTA, AEMSID, LOCID,
 TMSTMP. This is a write event.  
VARIABLES: RETSTA                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the return status array. It will contain
 either an error message or the following string of data: "1^Update of
 EQUIPMENT INV. file, #6914, successful" 
VARIABLES: AEMSID                       TYPE: Input
 VARIABLES DESCRIPTION:   The equipment id or IEN from file 6914 
VARIABLES: LOCID                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the location at which the equipment is
 arriving.  
VARIABLES: TMSTMP                       TYPE: Input
 VARIABLES DESCRIPTION:   This the time stamp in ISO format: yyyy-mm-dd
 hh:mm:ss 
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM
  DATE ACTIVATED: JUN 27, 2014

NUMBER: 5914                            IA #: 5914
  FILE NUMBER: 6911                     GLOBAL ROOT: ENG(6911
  DATE CREATED: MAY 15, 2013            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VIAAEUT
  NAME: READ ACCESS TO FILE #6911 (EQUIPMENT CATEGORY)
  ID: VIAAEUT
GLOBAL REFERENCE: ENG(6911,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the name of the category.  
GLOBAL REFERENCE: ENG(6911,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SYNONYM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the field synonym under the synonym multiple
 (#.5).  
 GENERAL DESCRIPTION:   Request permission for READ access via FileMan calls to
 file #6911 in order to complete RPC queries from IntelligentInsites. This is
 part of the RTLS National project to facilitate tracking equipment updates in 
 Engineering, while keeping IntelligentInsites with up to date information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
COMPONENT/ENTRY POINT: GETCAT
 COMPONENT DESCRIPTION:   Collect data for the fields listed above on a given
 equipment category.  
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM
  DATE ACTIVATED: JUN 27, 2014

NUMBER: 5915                            IA #: 5915
  FILE NUMBER: 6928                     GLOBAL ROOT: ENG('SP'
  DATE CREATED: MAY 15, 2013            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VIAAEUT
  NAME: READ ACCESS TO FILE #6928 (ENG SPACE)
  ID: VIAAEUT
GLOBAL REFERENCE: ENG('SP',D0,0)
FIELD NUMBER: .01                       FIELD NAME: ROOM NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .5                        FIELD NAME: BUILDING NUMBER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .51                       FIELD NAME: BUILDING FILE POINTER
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: .6                        FIELD NAME: DIVISION
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: WING
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.5                       FIELD NAME: SERVICE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: ENG('SP',D0,9)
FIELD NUMBER: 19                        FIELD NAME: INVERSE LOCATION
  LOCATION: 9;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Request permission for READ access via FileMan calls to
 file #6928 in order to complete RPC queries from IntelligentInsites. This is
 part of the RTLS National project to facilitate tracking equipment updates in 
 Engineering, while keeping IntelligentInsites with up to date information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
COMPONENT/ENTRY POINT: GETLOC
 COMPONENT DESCRIPTION:   This tag will collect data for all the fields above
 on any given location.  
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM
  DATE ACTIVATED: JUN 27, 2014

NUMBER: 5916                            IA #: 5916
  FILE NUMBER: 6917                     GLOBAL ROOT: ENCSN(6917
  DATE CREATED: MAY 15, 2013            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VIAAEAD
  NAME: READ ACCESS TO FILE #6917 (CATEGORY STOCK NUMBER)
  ID: VIAAEAD
GLOBAL REFERENCE: ENCSN(6917,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CATEGORY STOCK NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: BRIEF DESCRIPTION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Request permission for READ access via FileMan calls to
 file #6917 in order to complete RPC queries from IntelligentInsites. This is
 part of the RTLS National project to facilitate tracking equipment updates in 
 Engineering, while keeping IntelligentInsites with up to date information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
COMPONENT/ENTRY POINT: RTLSDTEX
 COMPONENT DESCRIPTION:   Collect the Category Stock Number and brief
 description for a given asset used in Engineeng.  
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM
  DATE ACTIVATED: JUN 27, 2014

NUMBER: 5917                            IA #: 5917
  FILE NUMBER: 6914.1                   GLOBAL ROOT: ENG(6914.1
  DATE CREATED: MAY 15, 2013            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VIAAEAD
  NAME: READ ACCESS TO FILE #6914.1 (CMR)
  ID: VIAAEAD
GLOBAL REFERENCE: ENG(6914.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .6                        FIELD NAME: BRIEF DESCRIPTION
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Request permission for READ access via FileMan calls to
 file #6914.1 in order to complete RPC queries from IntelligentInsites. This is
 part of the RTLS National project to facilitate tracking equipment updates in 
 Engineering, while keeping IntelligentInsites with up to date information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
COMPONENT/ENTRY POINT: RTLSDTEX
 COMPONENT DESCRIPTION:   Collect the CMR field name and brief description for
 a given asset used in Engineering.  
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM
  DATE ACTIVATED: JUN 27, 2014

NUMBER: 5918                            IA #: 5918
  FILE NUMBER: 6912                     GLOBAL ROOT: ENG('MFG'
  DATE CREATED: MAY 15, 2013            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VIAAEAD
  NAME: READ ACCESS TO FILE #6912 (MANUFACTURER LIST FILE)
  ID: VIAAEAD
GLOBAL REFERENCE: ENG('MFG',D0,0)
FIELD NUMBER: .01                       FIELD NAME: MFG/DIV
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the original manufacturer of the equipment.  
 GENERAL DESCRIPTION:   Request permission for READ access via FileMan calls to
 file #6912 in order to complete RPC queries from IntelligentInsites. This is
 part of the RTLS National project to facilitate tracking equipment updates in 
 Engineering, while keeping IntelligentInsites with up to date information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
COMPONENT/ENTRY POINT: RTLSDTEX
 COMPONENT DESCRIPTION:   Collect the manufacturer name for any given assset in
 Engineeiring.  
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM
  DATE ACTIVATED: JUN 27, 2014

NUMBER: 5919                            IA #: 5919
  FILE NUMBER: 6922                     GLOBAL ROOT: DIC(6922
  DATE CREATED: MAY 15, 2013            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  ROUTINE: VIAAEAD
  NAME: READ ACCESS TO FILE #6922 (ENGINEERING SECTION LIST)
  ID: VIAAEAD
GLOBAL REFERENCE: DIC(6922,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ENGINEERING SECTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Request permission for READ access via FileMan calls to
 file #6922 in order to complete RPC queries from IntelligentInsites. This is
 part of the RTLS National project to facilitate tracking equipment updates in 
 Engineering, while keeping IntelligentInsites with up to date information.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
COMPONENT/ENTRY POINT: RTLSDTEX
 COMPONENT DESCRIPTION:   Collect the Engineering section number and name.  
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM

NUMBER: 5920                            IA #: 5920
  FILE NUMBER: 6910                     GLOBAL ROOT: DIC(6910
  DATE CREATED: MAY 15, 2013            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VIAAEAD
  NAME: READ ACCESS TO FILE #6910 (ENG INIT PARAMETERS)
  ID: VIAAEAD
GLOBAL REFERENCE: DIC(6910,D0,0)
FIELD NUMBER: .01                       FIELD NAME: STATION NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: STATION NUMBER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Request permission for READ access via FileMan calls to
 file #6910 in order to complete RPC queries from IntelligentInsites. This is
 part of the RTLS National project to facilitate tracking equipment updates in 
 Engineering, while keeping IntelligentInsites with up to date information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
COMPONENT/ENTRY POINT: RTLSDTEX
 COMPONENT DESCRIPTION:   Collect the station number and name.  
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM
  DATE ACTIVATED: JUN 27, 2014

NUMBER: 5921                            IA #: 5921
  FILE NUMBER: 441                      GLOBAL ROOT: PRC(441
  DATE CREATED: MAY 16, 2013            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VIAAIMUP
  NAME: READ ACCESS TO FILE #441 (ITEM MASTER)
  ID: VIAAIMUP
GLOBAL REFERENCE: PRC(441,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: SHORT DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(441,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: VENDOR
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Vendor field under the Vendor multiple field, #6.  
FIELD NUMBER: 3                         FIELD NAME: VENDOR STOCK #
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Vendor stock # under the Vendor multiple field, #6.  
 GENERAL DESCRIPTION:   Request permission for READ access via FileMan calls to
 file #441 in order to complete RPC queries from WaveMark. This is part of the
 RTLS National project to facilitate tracking clinical supplies in the Cathlab
 inventory point for GIP.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
COMPONENT/ENTRY POINT: ITEM
 COMPONENT DESCRIPTION:   Collect the fields listed above for a given Item
 Master number from IFCAP which will be passed to WaveMark.  
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM
  DATE ACTIVATED: JUN 30, 2014

NUMBER: 5922                            IA #: 5922
  FILE NUMBER: 440                      GLOBAL ROOT: PRC(440
  DATE CREATED: MAY 16, 2013            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VIAAIMUP
  NAME: READ ACCESS TO FILE #440 (VENDOR)
  ID: VIAAIMUP
GLOBAL REFERENCE: PRC(440,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Request permission for READ access via FileMan calls to
 file #440 in order to complete RPC queries from WaveMark. This is part of the
 RTLS National project to facilitate tracking clinical supplies in the Cath lab
 inventory point for GIP.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
COMPONENT/ENTRY POINT: ITEM
 COMPONENT DESCRIPTION:   Collect the Vendor number and name for a given item
 in IFCAP and pass it forward to WaveMark.  
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM
  DATE ACTIVATED: JUL 02, 2014

NUMBER: 5923                            IA #: 5923
  FILE NUMBER: 445                      GLOBAL ROOT: PRCP(445
  DATE CREATED: MAY 16, 2013            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VIAAIPDE
  NAME: READ/WRITE ACCESS TO FILE #445 (GENERIC INVENTORY)
  ID: VIAAIPDE
GLOBAL REFERENCE: PRCP(445,D0,0)
FIELD NUMBER: .01                       FIELD NAME: INVENTORY POINT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ITEM NO.
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field and all others listed under the global
 reference above are found under the multiple of node 1 (field #1, Inventory
 Item).  
FIELD NUMBER: .4
  FIELD NAME: MANDATORY OR REQUESTED SOURCE
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: .5                        FIELD NAME: GROUP CATEGORY CODE
  LOCATION: 0;21                        ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: UNIT OF ISSUE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 4.8                       FIELD NAME: AVERAGE COST (UNIT OF ISSUE)
  LOCATION: 0;22                        ACCESS: Read w/Fileman
FIELD NUMBER: 4.81                      FIELD NAME: TOTAL INVENTORY VALUE
  LOCATION: 0;27                        ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: QTY.ON HAND (UNIT OF ISSUE)
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: NORMAL STOCK LEVEL
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9.5                       FIELD NAME: TEMPORARY STOCK LEVEL
  LOCATION: 0;23                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: STANDARD REORDER POINT
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 10.3                      FIELD NAME: OPTIONAL REORDER POINT
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11                        FIELD NAME: EMERGENCY STOCK LEVEL
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,1,D1,5,D2,0)
FIELD NUMBER: .01                       FIELD NAME: PROCUREMENT SOURCE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Field procurement source under multiple (#.6) of the same
 name.  
GLOBAL REFERENCE: PRCP(445,D0,1,D1,DUE)
FIELD NUMBER: 8.1                       FIELD NAME: DUE-IN
  LOCATION: DUE;1                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Request permission for READ and WRITE access via
 FileMan calls to file #445 in order to complete RPC queries from WaveMark.
 This is part of the RTLS National project to facilitate tracking clinical
 supplies in the Cathlab inventory point for GIP.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
COMPONENT/ENTRY POINT: IPQRY
 COMPONENT DESCRIPTION:   Collect data on all the fields listed above for a
 given Item Master and Inventory Point in IFCAP/GIP.  
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM
  DATE ACTIVATED: JUL 07, 2014

NUMBER: 5924                            IA #: 5924
  FILE NUMBER: 627.8                    GLOBAL ROOT: DIC(627.8
  DATE CREATED: MAY 16, 2013            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DESCRIPTION UPDATE FOR 627.8 FILE
  ID: DIC(627.8
 GENERAL DESCRIPTION:   Important Note: This is a One-Time Agreement, just for
 Patch YS*5.01*107.  
  
 Update of DESCRIPTION for File (#627.8) which is the DIAGNOSTIC RESULTS - 
 MENTAL HEALTH File to replace occurrences of 'ICD9' to 'ICD DIAGNOSIS' to
 accommodate ICD-10 Remediation project for Patch YS*5.01*107.  DESCRIPTION
 will be updated using Post-Init routine YS107P.  
  
 Routine YS107P directly sets nodes in the File Description for File (#627.8).  
  
 End result should be as below: 
  
 ^DIC(627.8,"%D",7,0)="""AE"" Xref  -  Type (DSM or ICD DIAGNOSIS), DFN, System
 Dte, Dx, DFN." 
  
 ^DIC(627.8,"%D",13,0)="""AG"" Xref  -  Type (DSM or ICD DIAGNOSIS), DFN, Dx,
 IFN." 
  STATUS: Active
KEYWORDS: DESCRIPTION
KEYWORDS: ICD
KEYWORDS: DIAGNOSIS
SUBSCRIBING PACKAGE: MENTAL HEALTH
  DATE ACTIVATED: MAY 23, 2013

NUMBER: 5925                            IA #: 5925
  DATE CREATED: AUG 27, 2015            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: WVUTL11
  NAME: IS PATIENT PREGNANT/LACTATING   ORIGINAL NUMBER: 5925
  ID: WVUTL11
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to determine if a patient is pregnant or lactating on a specific date or on at
 least one day within a date range.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LACTATION STATUS
KEYWORDS: LACTATING IN DATE RANGE
KEYWORDS: PREGNANCY STATUS
KEYWORDS: PREGNANT IN DATE RANGE
COMPONENT/ENTRY POINT: $$ISLACT(WVDFN,WVSDATE,WVEDATE,WVCDE)
 COMPONENT DESCRIPTION:   This entry point will return whether the patient was
 lactating on a specific date or on at least one day within a date range.  
VARIABLES: WVDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient in the WV
 PATIENT FILE (#790). This value is required.  
VARIABLES: WVSDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the start date of the date range to return
 the patient's lactation status for. The value must be in FileMan internal
 date/time format and is optional. If not defined, the value in the DT system
 variable will be used.  
VARIABLES: WVEDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the end date of the date range to return the
 patient's lactation status for. The value must be in FileMan internal
 date/time format and is optional.  
VARIABLES: WVCDE                        TYPE: Input
 VARIABLES DESCRIPTION:   This is a Boolean flag that determines how this
 component handles lactation periods without a documented end date. When set to
 one, the component will set the end date to tomorrow. When set to zero, the 
 component will set the end date to the date that the next not lactating status
 was entered on. This value is optional and if not defined, will be set to
 zero.  
VARIABLES: $$ISLACT                     TYPE: Output
 VARIABLES DESCRIPTION:   The patient's lactation status. Possible return
 values are: 
   1 for LACTATING 
   0 for NOT LACTATING 
  
 If a single date or no date is passed in to this call, the patient's lactation
 status for that specific date or the current date is returned.  
                             
 If a date range is passed in to this call, the patient must have a LACTATING
 status at some point in the range for this call to return a value of 1. In
 other words, the patient does not have to have a status of LACTATING for the
 entire date range for this call to return a value of 1.  
COMPONENT/ENTRY POINT: $$ISPREG(WVDFN,WVSDATE,WVEDATE,WVCDE)
 COMPONENT DESCRIPTION:   This entry point will return whether the patient was
 pregnant on a specific date or on at least one day within a date range.  
VARIABLES: WVDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient in the WV
 PATIENT file (#790). This value is required.  
VARIABLES: WVSDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the start date of the date range to return
 the patient's pregnancy status for. The value must be in FileMan internal
 date/time format and is optional. If not defined, the value in the DT system 
 variable will be used.  
VARIABLES: WVEDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the end date of the date range to return the
 patient's pregnancy status for. The value must be in FileMan internal
 date/time format and is optional.  
VARIABLES: WVCDE                        TYPE: Input
 VARIABLES DESCRIPTION:   This is a Boolean flag that determines how this
 component handles pregnancy periods without a documented end date. When set to
 one, the component will set the end date to tomorrow. When set to zero, the 
 component will set the end date to the date that the next not pregnant status
 was entered on. This value is optional and if not defined, will be set to
 zero. Note that this component interprets a DO NOT KNOW state as a NOT
 PREGNANT state.  
VARIABLES: $$ISPREG                     TYPE: Output
 VARIABLES DESCRIPTION:   The patient's pregnancy status. Possible return
 values are: 
   1 for PREGNANT 
   0 for all other statuses 
  
 If a single date or no date is passed in to this call, the patient's pregnancy
 status for that specific date or the current date is returned.  
                             
 If a date range is passed in to this call, the patient must have a PREGNANT
 status at some point in the range for this call to return a value of 1. In
 other words, the patient does not have to have a status of PREGNANT for the
 entire date range for this call to return a value of 1.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 3/16/22 effective with VPR*1*29, to use APIs:
 $$ISPREG and $$ISLACT 
  DATE ACTIVATED: NOV 17, 2017

NUMBER: 5926                            IA #: 5926
  DATE CREATED: JUN 05, 2013            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Supported                      TYPE: Routine
  ROUTINE: WVTDLPD                      NAME: PREGNANCY AND LACTATION DATA
  ORIGINAL NUMBER: 5925                 ID: WVTDLPD
 GENERAL DESCRIPTION:   Returns current patient data from file 790.8 and 790.9. 
 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: WOMEN'S HEALTH
KEYWORDS: LACTATION
KEYWORDS: PREGNANCY
COMPONENT/ENTRY POINT: WVDATA
VARIABLES: WVRTN                        TYPE: Output
 VARIABLES DESCRIPTION:   Return values 
VARIABLES: WVIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 

NUMBER: 5927                            IA #: 5927
  FILE NUMBER: 1                        GLOBAL ROOT: DIC(
  DATE CREATED: JUN 05, 2013            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: EDIS POINTING TO FILE 1
  ID: DIC(
 GENERAL DESCRIPTION:   The Adhoc worksheets and reports portions of EDIS
 requests approval to point to the file of files (File #1). EDIS will only
 point to files that belong to EDIS. This is to be used for building calls to
 File Manager API's dynamically.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
  DATE ACTIVATED: JUL 02, 2013

NUMBER: 5928                            IA #: 5928
  DATE CREATED: JUN 18, 2013            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGSAUTL
  NAME: DBIA 5928                       ID: DGSAUTL
 GENERAL DESCRIPTION:   SUB^DGSAUTL returns the sub-categories associated with
 either an admitting regulation or an appointment type.  If none provided or
 user times out then "NULL" will be returned.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DGSAUTL
COMPONENT/ENTRY POINT: SUB
VARIABLES: ATAR                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) IEN of Admitting Regulation or Appointment
 Type 
  
  
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) (1:ADT,2:SCHEDULING) Application that is
 requesting information 
  
VARIABLES: DEFAULT                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) IEN from Sharing Agreement Sub-Category
 File (35.2) 
  
VARIABLES: IEN                          TYPE: Output
 VARIABLES DESCRIPTION:   IEN of File 35.2^Name 
  
VARIABLES: NULL                         TYPE: Output
 VARIABLES DESCRIPTION:   If user times out, user does not make selection
 and/or "^"s out of prompt 
  
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: JUN 24, 2013

NUMBER: 5929                            IA #: 5929
  DATE CREATED: JUN 20, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDX UNLOCK ORDER
  REMOTE PROCEDURE: ORWDX UNLOCK ORDER
 GENERAL DESCRIPTION:   Provides the ability to unlock an order to update
 consult information.  
  STATUS: Active
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
 SUBSCRIBING DETAILS:   Added FBCS as subscriber for consult orders - effective
 with DSIF*3.2*29. 
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  
 VIA will use this RPC in the VIAB*1*5 patch. One of the charges to the VIA
 project is exposing RPCs and creating ICRs for those RPCs that are already in
 use by the MDWS infrastructure. VIA provides a Class I product of services
 that work with VistaLink, replacing the need for developers to use MDWS
 services.  The OR*3*426 patch is associated with the VIAB*1*5 patch and turns
 on the APP PROXY ENABLED flag.  
  DATE ACTIVATED: APR 21, 2014

NUMBER: 5930                            IA #: 5930
  DATE CREATED: JUN 20, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDCN32 DEF                    REMOTE PROCEDURE: ORWDCN32 DEF
 GENERAL DESCRIPTION:   Returns a set of Urgencies and places for use in
 Consults.  
  STATUS: Retired
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 03, 2014

NUMBER: 5931                            IA #: 5931
  DATE CREATED: JUN 20, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORQQCN URGENCIES                REMOTE PROCEDURE: ORQQCN URGENCIES
 GENERAL DESCRIPTION:   Returns a list of available urgencies for a specific
 Consult.  
  
 Fee Basis Claims System utilizes this RPC to provide users the ability to 
 update Consult information from within FBCS.  
  STATUS: Retired
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: JUN 03, 2014

NUMBER: 5932                            IA #: 5932
  FILE NUMBER: 405.4                    GLOBAL ROOT: DG(405.4,D0,W,
  DATE CREATED: JUN 24, 2013            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Lab Access to Room-Bed Wards Which Can Assign Multiple
  ID: DG(405.4,D0,W,
GLOBAL REFERENCE: DG(405.4,D0,W,D1,0)
FIELD NUMBER: .01                       FIELD NAME: WARD(S) WHICH CAN ASSIGN
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   
  
 The ward (an entry in the WARD LOCATION file [#42]) which can utilize the bed
 entry.  
  
 GLOBAL DESCRIPTION:   
  
 Multiple field on the ROOM-BED file (#405.4) indicating associations the 
 ROOM-BED file entry has with Ward Locations (in the WARD LOCATION file [#42]). 
  
 GENERAL DESCRIPTION:   
  
 Lab has permission to access the ROOM-BED file (#405.4) WARD(S) WHICH CAN
 ASSIGN Multiple.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ROOM-BED
KEYWORDS: WARDS WHICH CAN ASSIGN
KEYWORDS: LAB
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   
  
 Lab Service has permission to $Order through the WARD(S) WHICH CAN ASSIGN 
 Multiple (#100) in the ROOM-BED file (#405.4).  [^DG(405.4,DA1,"W",DA)] 
  
 Lab Service has permission to get the WARD(S) WHICH CAN ASSIGN field (#.01) 
 from the WARD(S) WHICH CAN ASSIGN Multiple (#100) using a $Piece function.  
  
 The WARD(S) WHICH CAN ASSIGN field (#.01) field is used by Lab Service to
 associate a RO0M-BED record with an entry in the WARD LOCATION file (#42) for
 lab related reporting purposes.  
  
  DATE ACTIVATED: JUN 28, 2013

NUMBER: 5933                            IA #: 5933
  DATE CREATED: JUN 25, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: OREVNTX PAT                     STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5934                            IA #: 5934
  DATE CREATED: JUN 26, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORIMO IMOLOC
 GENERAL DESCRIPTION:   via 
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5935                            IA #: 5935
  DATE CREATED: JUN 26, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORPRF ISIVQO                    STATUS: Withdrawn
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VISTA INTEGRATION ADAPTER 

NUMBER: 5936                            IA #: 5936
  DATE CREATED: MAR 06, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQCN GET ORDER NUMBER
  REMOTE PROCEDURE: ORQQCN GET ORDER NUMBER
 GENERAL DESCRIPTION:   A new OR*3*392 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  
 The following information is available about the RPC: 
  
 NAME: ORQQCN GET ORDER NUMBER           TAG: GETORDER 
   ROUTINE: ORQQCN1                      RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Returns OERR order number for consult/procedure.  INPUT PARAMETER: Consult ID 
            PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 16               REQUIRED: YES 
  STATUS: Active
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/31/23, effective with CRMS*1*0, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS
 namespace.The CRMS VAHC Remote Application includes the CRMS VAHC Option,
 which includes required RPCs.  ORQQCN GET ORDER NUMBER is one of the Remote
 Procedures included in the CRMS VAHC Option.  The Remote Application uses Data 
 Access Services/National Health Information Network (DAS/NHIN) as the 
 middleware to interface with VistA.  
  
 Added 9/3/24, effective with CRMS*1*1, the Veterans Crisis Line (VCL) 
 Medoraforce application is a Salesforce product sharing the CRMS namespace.
 The CRMS VCL MDFC Remote Application includes the CRMS VCL MDFC Option, which
 includes ORQQCN GET ORDER NUMBER Remote Procedure to support the VCL
 Medoraforce application RPCs. The Remote Application uses Data Access
 Services/National Health Information Network (DAS/NHIN)as the middleware to
 interface with VistA.  This application replaces the VCL legacy application.  
  DATE ACTIVATED: MAR 06, 2014

NUMBER: 5937                            IA #: 5937
  DATE CREATED: JUN 26, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORQQCN UNRESOLVED               STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5938                            IA #: 5938
  DATE CREATED: JUN 26, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORQQVI VITALS                   REMOTE PROCEDURE: ORQQVI VITALS
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5939                            IA #: 5939
  DATE CREATED: JUN 26, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORVAA VAA
  REMOTE PROCEDURE: ORVAA VAA
 GENERAL DESCRIPTION:   This ICR was created for VIA. The RPC was used by MDWS,
 and never previously documented in an ICR.  Since MDWS already uses this RPC,
 and VIA is responsible for exposing all RPCs used by MDWS, the CPRS 
 development team agrees to the use of the RPC. 
  
 For future subscribers there first needs to be a check for an RPC created in
 the namespace that owns the data accessed by this RPC.  
  
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch. Patch
 OR*3*495 modified this ICR and changed PARAMETER TYPE of REFERENCE to LITERAL. 
 This is in concordance with the VistA Security Remediation (VSR) project.  
  
 The following is the definition of the Remote Procedure: NAME: ORVAA VAA       
                  TAG: VAA 
   ROUTINE: ORVAA                        RETURN VALUE TYPE: ARRAY 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Returns the policy name for a veteran with VA Advantage. If the veteran 
  does not have VA Advantage the return value will be 0.  INPUT PARAMETER: DFN  
                  PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 255              REQUIRED: YES 
   SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  The DFN is the veteran patient's Internal Entry Number in the PATIENT 
  file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  DATE ACTIVATED: MAR 13, 2014

NUMBER: 5940                            IA #: 5940
  DATE CREATED: JUN 26, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWCIRN FACLIST
  REMOTE PROCEDURE: ORWCIRN FACLIST
 GENERAL DESCRIPTION:   A new OR*3*392 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  
 The following information is available about the RPC: 
  
 NAME: ORWCIRN FACLIST                   TAG: FACLIST 
   ROUTINE: ORWCIRN                      RETURN VALUE TYPE: ARRAY 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Returns a list of the remote VA facilities at which the selected patient 
  has been seen.  
  
 This information is from the TREATING FACILITY LIST file which is not owned by
 CPRS. This ICR is created to satisfy the needs of the VIA project which is
 tasked to replace MDWS services.  Future subscribers should check for an RPC
 owned by the Registration package that owns this data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  DATE ACTIVATED: MAR 13, 2014

NUMBER: 5941                            IA #: 5941
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDCN32 NEWDLG                 STATUS: Withdrawn
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5942                            IA #: 5942
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDPS2 QOGRP
  REMOTE PROCEDURE: ORWDPS2 QOGRP       STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: VIA
KEYWORDS: VAR
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   As of 2/13/17, Veterans Appointment Request (VAR) is
 using this RPC through the VistA Integration Adaptor's (VIA) OrderMgmt
 Service.  
  DATE ACTIVATED: FEB 13, 2017

NUMBER: 5943                            IA #: 5943
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDX DISMSG                    STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5944                            IA #: 5944
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDX LOADRSP
  REMOTE PROCEDURE: ORWDX LOADRSP
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
   
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
   
 This RPC gets responses from Order Dialog file (#101.41) or Order file (#100). 
   
 The following information is available about the RPC: 
  
 NAME: ORWDX LOADRSP                     TAG: LOADRSP 
   ROUTINE: ORWDX                        RETURN VALUE TYPE: ARRAY INPUT
 PARAMETER: RSPID                  PARAMETER TYPE: LITERAL 
   SEQUENCE NUMBER: 1 INPUT PARAMETER: TRANS                  PARAMETER TYPE:
 LITERAL 
   SEQUENCE NUMBER: 2 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  DATE ACTIVATED: MAR 17, 2014

NUMBER: 5945                            IA #: 5945
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDX LOCK
  REMOTE PROCEDURE: ORWDX LOCK
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
      
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
      
 This RPC attempts to lock patient for ordering.  
  
 The following information is available about the RPC: 
  NAME: ORWDX LOCK                        TAG: LOCK 
   ROUTINE: ORWDX                        RETURN VALUE TYPE: SINGLE VALUE 
  DESCRIPTION:   
  RPC to attempt to lock patient for ordering (returns 1 if successful or 0 
  if unsuccessful).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  DATE ACTIVATED: MAR 17, 2014

NUMBER: 5946                            IA #: 5946
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RARTUTL
  NAME: Return displayable medication and radiopharmaceutical data
  ID: RARTUTL
 GENERAL DESCRIPTION:   This request grants permission to the VistA Imaging
 application to call supported VistA Radiology/Nuclear Medicine (VistA RIS) API
 for the purpose of exam specific medication and radiopharmaceutical data.  
  
 Medication and radiopharmaceutical data will display together with requisition
 and report data (already displayed) as needed by radiology personnel when
 viewing images through VistARad.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RA-MAG med & radiopharm APIs
COMPONENT/ENTRY POINT: PHARM
 COMPONENT DESCRIPTION:   This subroutine displays all the medications
 associated with a radiology exam.  
VARIABLES: RADA                         TYPE: Input
 VARIABLES DESCRIPTION:   RADA is the value of the Internal Entry Number String
 (IENS) for a specific exam. It is VA FileMan's way of representing the
 internal entry numbers for an entry in all of the DBS calls. RADA will be in
 the following format: DA_","_DA(1)_","_DA(2)_",".  
COMPONENT/ENTRY POINT: RDIO
 COMPONENT DESCRIPTION:   This subroutine displays all the radiopharmaceuticals
 associated with a radiology exam. 
VARIABLES: RADA                         TYPE: Input
 VARIABLES DESCRIPTION:   RADA is the pointer value filed in the NUCLEAR MED
 DATA field.  
  
 The NUCLEAR MED DATA field can be found on the EXAMINATIONS (#70.03) sub-file.
 NUCLEAR MED DATA is the twenty-eighth piece of the zero (0;28) node.  
SUBSCRIBING PACKAGE: IMAGING
  DATE ACTIVATED: JUL 25, 2013

NUMBER: 5947                            IA #: 5947
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDX LOCK ORDER
  REMOTE PROCEDURE: ORWDX LOCK ORDER
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
      
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
      
 This RPC attempts to lock a specific order, returning a single value.  
  NAME: ORWDX LOCK ORDER                  TAG: LOCKORD 
   ROUTINE: ORWDX                        RETURN VALUE TYPE: SINGLE VALUE 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  
 VIA will use this RPC in the VIAB*1*5 patch. One of the charges to the VIA
 project is exposing RPCs and creating ICRs for those RPCs that are already in
 use by the MDWS infrastructure. VIA provides a Class I product of services
 that work with VistaLink, replacing the need for developers to use MDWS
 services.  The OR*3*426 patch is associated with the VIAB*1*5 patch and turns
 on the APP PROXY ENABLED flag.  
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
 SUBSCRIBING DETAILS:   FBCS is using this RPC to lock a consult order.
 DSIF*3.2*29 contains FBCS Consult Bidirectional processing.  
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/31/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS
 namespace.The CRMS VAHC Remote Application includes the CRMS VAHC Option,
 which includes required RPCs.  ORWDX LOCK ORDER is one of the Remote
 Procedures included in the CRMS VAHC Option.  The Remote Application uses Data
 Access Services/National Health Information Network (DAS/NHIN) as the
 middleware to interface with VistA.  
  DATE ACTIVATED: MAR 17, 2014

NUMBER: 5948                            IA #: 5948
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDX UNLOCK
  REMOTE PROCEDURE: ORWDX UNLOCK
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
      
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
      
 This RPC attempts to unlock a patient for ordering, returning a single value.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  DATE ACTIVATED: MAR 17, 2014

NUMBER: 5949                            IA #: 5949
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDX UNLOCK ORDER              STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5950                            IA #: 5950
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDX UNLOCK ORDER              STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5951                            IA #: 5951
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDX WRLST
  REMOTE PROCEDURE: ORWDX WRLST         STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: VIA
KEYWORDS: VAR
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 14, 2017

NUMBER: 5952                            IA #: 5952
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDX2 DCREASON                 STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5953                            IA #: 5953
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXC DISPLAY
  REMOTE PROCEDURE: ORWDXC DISPLAY      STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: VIA
KEYWORDS: VAR
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 22, 2017

NUMBER: 5954                            IA #: 5954
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDXC ON                       STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5955                            IA #: 5955
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXC SESSION
  REMOTE PROCEDURE: ORWDXC SESSION
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
      
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
      
 This RPC returns a list of Order Checks on Release Order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  DATE ACTIVATED: MAR 17, 2014

NUMBER: 5956                            IA #: 5956
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXM DLGNAME
  REMOTE PROCEDURE: ORWDXM DLGNAME
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
      
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
      
 This RPC returns name(s) of dialog and base dialog given IEN.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  DATE ACTIVATED: MAR 17, 2014

NUMBER: 5957                            IA #: 5957
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDXM MENU                     STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5958                            IA #: 5958
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXM1 BLDQRSP
  REMOTE PROCEDURE: ORWDXM1 BLDQRSP
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
      
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  DATE ACTIVATED: MAR 17, 2014

NUMBER: 5959                            IA #: 5959
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDXM3 ISUDQO                  STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5960                            IA #: 5960
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWLRR ALLTESTS
  REMOTE PROCEDURE: ORWLRR ALLTESTS
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
      
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
      
 This RPC returns array of Lab Test names starting with the input value FROM.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  DATE ACTIVATED: MAR 17, 2014

NUMBER: 5961                            IA #: 5961
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWLRR INTERIM                  STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5962                            IA #: 5962
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWLRR INTERIMG
  REMOTE PROCEDURE: ORWLRR INTERIMG
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
      
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
      
 This RPC uses parameters to return the Lab package interim report for display. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  DATE ACTIVATED: MAR 17, 2014

NUMBER: 5963                            IA #: 5963
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWORB KILL EXPIR MED ALERT     STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5964                            IA #: 5964
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWORB KILL UNSIG ORDERS ALERT  STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5965                            IA #: 5965
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWORB KILL UNVER MEDS ALERT    STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5966                            IA #: 5966
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWORB KILL UNVER ORDERS ALERT  STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5967                            IA #: 5967
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWORDG MAPSEQ
  REMOTE PROCEDURE: ORWORDG MAPSEQ
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
      
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
      
 This RPC is for organizing a list of display groups from the Display Group
 file (#100.98).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
  DATE ACTIVATED: MAR 17, 2014

NUMBER: 5968                            IA #: 5968
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWPCE GETSVC                   STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5969                            IA #: 5969
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWPCE NOTEVSTR                 STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5970                            IA #: 5970
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWPT INPLOC                    STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5971                            IA #: 5971
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWPT1 PCDETAIL
  REMOTE PROCEDURE: ORWPT1 PCDETAIL
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
  
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
  
 This RPC gets patient information from the Primary Care Managment Module of
 the Scheduling package. This patient information is not owned by CPRS, but the
 RPC is in the OR namespace. 
  
 Future subscribers should check for an RPC owned by the Scheduling package 
 that owns this data, instead of using this RPC.  
  
 The following information is available about the RPC: 
  NAME: ORWPT1 PCDETAIL                   TAG: PCDETAIL 
   ROUTINE: ORWPT1                       RETURN VALUE TYPE: ARRAY 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Returns primary care detailed information about a patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  DATE ACTIVATED: MAR 13, 2014

NUMBER: 5972                            IA #: 5972
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWPT1 PRCARE
  REMOTE PROCEDURE: ORWPT1 PRCARE
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
  
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
  
 This RPC gets patient information from the Primary Care Management Module of
 the Scheduling package. This patient information is not owned by CPRS, but the
 RPC is in the OR namespace. 
  
 Future subscribers should check for an RPC owned by the Scheduling package 
 that owns this data, instead of using this RPC.  
  
 The following information is available about the RPC: 
  
  NAME: ORWPT1 PRCARE                     TAG: PRCARE 
   ROUTINE: ORWPT1                       RETURN VALUE TYPE: SINGLE VALUE 
  DESCRIPTION:   
  Return primary care information for a patient in the format: 
    VAL=Primary Care Team^Primary Care Provider^Attending^MH Treatment 
        Coordinator 
  INPUT PARAMETER: dfn 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  DATE ACTIVATED: MAR 13, 2014

NUMBER: 5973                            IA #: 5973
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWRA IMAGING EXAMS1            STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5974                            IA #: 5974
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWRP2 HS COMPONENTS
  REMOTE PROCEDURE: ORWRP2 HS COMPONENTS
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
  
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
  
 This RPC gets Health Summary Ad Hoc definitions from the Health Summary Type
 and Health Summary Component file, owned by the Health Summary (GMTS) package.
 The data is not owned by CPRS, but the RPC is in the OR namespace.  
  
 Future subscribers should check for an RPC owned by the Health Summary package
 and use it, instead of using this RPC, if it exists.  
  
 The following information is available about the RPC: 
  
  NAME: ORWRP2 HS COMPONENTS              TAG: COMP 
   ROUTINE: ORWRP2                       RETURN VALUE TYPE: ARRAY 
   AVAILABILITY: RESTRICTED 
  DESCRIPTION:   
   This RPC returns an array of the ADHOC Health Summary components.  
  RETURN PARAMETER DESCRIPTION:   
   Here is the format of the returned array: 
   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)Summary 
  Order 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  DATE ACTIVATED: MAR 13, 2014

NUMBER: 5975                            IA #: 5975
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWRP2 HS REPORT TEXT
  REMOTE PROCEDURE: ORWRP2 HS REPORT TEXT
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
   
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
   
 This RPC uses the Health Summary Component definitions owned by the Health
 Summary package. The data accessed is not owned by CPRS, but the RPC is in the
 OR namespace. 
   
 New subscribers must use their own Namespaced Context option to use this RPC
 (not OR CPRS GUI CHART). 
  
  The following information is available about the RPC: 
   
  NAME: ORWRP2 HS REPORT TEXT             TAG: REPORT 
   ROUTINE: ORWRP2                       RETURN VALUE TYPE: GLOBAL ARRAY 
   AVAILABILITY: RESTRICTED              WORD WRAP ON: TRUE 
  DESCRIPTION:   
   This RPC is used to build the ADHOC Health Summary from an array of 
   pre-selected health summary components.  INPUT PARAMETER: COMPS              
    PARAMETER TYPE: LIST 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 
  DESCRIPTION:   
   The input array is defined as: 
   COMPS(i)=array of subcomponents chosen, value is pointer at 
   ^GMT(142,DA(1),1,DA) 
   Additional pieces may be present for components that require additional 
   parameters such as Headers, Time and Occurrence limits, and selected 
   file entries, such as selected lab tests.  
    
 COMPS(i)=segment^OccuranceLimit^TimeLimit^Header^segment^file^ifn^zeroth 
   node of file 
  RETURN PARAMETER DESCRIPTION:   
   Text array for report section is returned.  
   Also, the first line of the text contains the following information: 
        <number of current section being passed> ^ <last section number> 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
SUBSCRIBING PACKAGE: VETEXT
 SUBSCRIBING DETAILS:   Added 3/12/25 effective with VTEX*1*0 used to provide
 after-visit health summaries to the patient. 
  DATE ACTIVATED: MAR 13, 2014

NUMBER: 5976                            IA #: 5976
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWSR RPTLIST
  REMOTE PROCEDURE: ORWSR RPTLIST
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
     
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
     
 This RPC gets the list of Surgery Reports to use in CPRS, based on data owned
 by the Surgery (SRO) package. The data is not owned by CPRS, but the RPC is in
 the OR namespace.  
     
 Future subscribers should check for an RPC owned by the Surgery package and
 use it, instead of using this RPC, if it exists.  
     
 The following information is available about the RPC: 
  
  NAME: ORWSR RPTLIST                     TAG: RPTLIST 
   ROUTINE: ORWSR                        RETURN VALUE TYPE: GLOBAL ARRAY 
   WORD WRAP ON: TRUE 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*392 patch is associated with the
 VIAB*1*1 patch.  
  DATE ACTIVATED: MAR 13, 2014

NUMBER: 5977                            IA #: 5977
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWTIU CHKTXT
  REMOTE PROCEDURE: ORWTIU CHKTXT       STATUS: Active
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
  DATE ACTIVATED: APR 07, 2014

NUMBER: 5978                            IA #: 5978
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWTPD1 GETCSRNG                STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5979                            IA #: 5979
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWTPD1 PUTCSRNG                STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5980                            IA #: 5980
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWU NPHASKEY                   STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5981                            IA #: 5981
  DATE CREATED: JUL 01, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWU1 NEWLOC                    STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5982                            IA #: 5982
  DATE CREATED: JUL 02, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: TIU GET LINKED PRF NOTES        STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5983                            IA #: 5983
  DATE CREATED: JUL 02, 2013
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU GET PRF ACTIONS
  REMOTE PROCEDURE: TIU GET PRF ACTIONS
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
  DATE ACTIVATED: MAR 14, 2014

NUMBER: 5984                            IA #: 5984
  DATE CREATED: JUL 02, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: TIU GET PRF TITLE               STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5985                            IA #: 5985
  DATE CREATED: JUL 02, 2013
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU HAS AUTHOR SIGNED?
  REMOTE PROCEDURE: TIU HAS AUTHOR SIGNED?
 GENERAL DESCRIPTION:   Boolean RPC returns a value of 0 if the author has not
 signed and the user attempting to sign is the expected co-signer.  Returns a 1
 if the author has signed or the user attempting to sign is NOT the expected 
 co-signer.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/20/25,Documenting historical usage of this RPC
 by CPRS GUI.  With OR*3.0*508, a review of the RPCs in OR CPRS GUI CHART found
 several RPCs not covered by an ICR.  
  DATE ACTIVATED: MAR 14, 2014

NUMBER: 5986                            IA #: 5986
  DATE CREATED: JUL 02, 2013
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU ISPRF
  REMOTE PROCEDURE: TIU ISPRF           STATUS: Active
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP*2.0*2 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                                                  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs.  
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/17/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace.
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes 
 required RPCs. TIU ISPRF is one of the Remote Procedures included in the CRMS
 VAHC Option.  The Remote Application uses Data Access Services/National Health
 Information Network (DAS/NHIN) as the middleware to interface with VistA.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 9/12/25, This RPC usage is not new with
 OR*3.0*508, but rather found during ICR review of the OR CPRS GUI CHART
 context option. In all likelihood the ICR was created specifically for the
 usage within CPRS GUI, but OE/RR was never added as a subscriber.  
  DATE ACTIVATED: MAR 14, 2014

NUMBER: 5987                            IA #: 5987
  DATE CREATED: JUL 02, 2013
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU ONE VISIT NOTE?
  REMOTE PROCEDURE: TIU ONE VISIT NOTE?
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/17/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace.
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes 
 required RPCs. TIU ONE VISIT NOTE? is one of the Remote Procedures included in
 the CRMS VAHC Option.  The Remote Application uses Data Access 
 Services/National Health Information Network (DAS/NHIN) as the middleware to
 interface with VistA.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 9/15/25, This RPC usage is not new with
 OR*3.0*508, but rather found during ICR review of the OR CPRS GUI CHART
 context option. In all likelihood the ICR was created specifically for the
 usage within CPRS GUI, but OE/RR was never added as a subscriber.  
  DATE ACTIVATED: MAR 14, 2014

NUMBER: 5988                            IA #: 5988
  DATE CREATED: JUL 02, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: XUS CVC                         STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 5989                            IA #: 5989
  FILE NUMBER: 63                       GLOBAL ROOT: LR(
  DATE CREATED: JUL 03, 2013            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Read Access to Laboratory Anatomic Pathology fields
  ID: LR(
GLOBAL REFERENCE: LR(D0,'EM',D1,0)
FIELD NUMBER: 'EM' FIELDS               ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   General Description contains a list of 'EM' multiple
 fields 
GLOBAL REFERENCE: LR(D0,'SP',D1,0)
FIELD NUMBER: 'SP' FIELDS               ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   General Description contains a list of 'SP' multiple
 fields 
GLOBAL REFERENCE: LR(D0,'CY',D1,0)
FIELD NUMBER: 'CY' FIELDS               ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   General Description contains a list of 'CY' multiple
 fields 
 GENERAL DESCRIPTION:   This integration agreement provides VistA Imaging (VI)
 with read-only access to LAB DATA file (#63) using VA FileMan APIs and it is
 limited to fields: 
    
 EM                                   field (#63, 2) 
   EM                              sub-file (#63.02) 
   DATE/TIME SPECIMEN TAKEN           field (#63.02, .01) 
   DATE/TIME SPECIMEN RECEIVED        field (#63.02, .1)  
   SPECIMEN SUBMITTED BY              field (#63.02, .011) 
   BRIEF CLINICAL HISTORY             field (#63.02, .013)      sub-file
 (#63.213) 
   PREOPERATIVE DIAGNOSIS             field (#63.02, .014)      sub-file
 (#63.214) 
   OPERATIVE FINDINGS                 field (#63.02, .015)      sub-file
 (#63.205) 
   POSTOPERATIVE DIAGNOSIS            field (#63.02, .016)      sub-file
 (#63.206) 
   DATE REPORT COMPLETED              field (#63.02, .03) 
   EM ACC #                           field (#63.02, .06) 
   PHYSICIAN                          field (#63.02, .07) 
   REPORT RELEASE DATE                field (#63.02, .11) 
   TIU REFERENCE DATE/TIME - EM       field (#63.02, .16) 
     TIU REFERENCE DATE/TIME - EM  sub-file (#63.49) 
     TIU ENTRY POINTER - EM           field (#63.49, 1) 
  
   ORDERED TEST                       field (#63.02, .35) 
     ORDERED TEST                  sub-file (#63.52) 
     LAB TEST ORDERED                 field (#63.52, 13) 
  
   COMMENT                            field (#63.02, .99)       sub-file
 (#63.208) 
     COMMENT                          field (#63.208, .01) 
   
   GROSS DESCRIPTION                  field (#63.02, 1)         sub-file
 (#63.201) 
   MICROSCOPIC EXAMINATION            field (#63.02, 1.1)       sub-file
 (#63.211) 
   EM DIAGNOSIS                       field (#63.02, 1.4)       sub-file
 (#63.204) 
  
   SPECIMEN                           field (#63.02, .012) 
     SPECIMEN                      sub-file (#63.202) 
     SPECIMEN                         field (#63.202, .01) 
     SPECIMEN TOPOGRAPHY              field (#63.202, .06) 
  
     EPON BLOCK                       field (#63.202, 1) 
       EPON BLOCK                  sub-file (#63.2021) 
       EPON BLOCK                     field (#63.2021, .01) 
       DATE/TIME BLOCK PREPARED       field (#63.2021, .02) 
       EM PROCEDURE                   field (#63.2021, 1)      
         EM PROCEDURE              sub-file (#63.20211) 
         EM PROCEDURE                 field (#63.20211, .01) 
         SECTION PREPARED (#)         field (#63.20211, .02) 
         DATE/TIME SECTION STAINED    field (#63.20211, .04) 
         SECTIONS COUNTED(#)          field (#63.20211, .06) 
         NEW SECTIONS                 field (#63.20211, .07) 
         SECTIONS EXAMINED(#)         field (#63.20211, .08) 
         NON-CONTROL SLIDES COUNTED   field (#63.20211, .09) 
         PRINTS MADE(#)               field (#63.20211, .1) 
         PRINTS COUNTED(#)            field (#63.20211, .12) 
         EXAMINED SECTIONS COUNTED(#) field (#63.20211, .13) 
  
  
  
  
 SURGICAL PATHOLOGY                   field (#63, 8) 
   SURGICAL PATHOLOGY              sub-file (#63.08) 
   DATE/TIME SPECIMEN TAKEN           field (#63.08, .01)  
   DATE/TIME SPECIMEN RECEIVED        field (#63.08, .1) 
   SPECIMEN SUBMITTED BY              field (#63.08, .011) 
   BRIEF CLINICAL HISTORY             field (#63.08, .013)        sub-file
 (#63.813) 
   PREOPERATIVE DIAGNOSIS             field (#63.08, .014)        sub-file
 (#63.814) 
   OPERATIVE FINDINGS                 field (#63.08, .015)        sub-file
 (#63.815) 
   POSTOPERATIVE DIAGNOSIS            field (#63.08, .016)        sub-file
 (#63.816) 
   DATE REPORT COMPLETED              field (#63.08, .03) 
   SURGICAL PATH ACC #                field (#63.08, .06) 
   SURGEON/PHYSICIAN                  field (#63.08, .07) 
   REPORT RELEASE DATE/TIME           field (#63.08, .11) 
   TIU REFERENCE DATE/TIME - SP       field (#63.08, .16) 
     TIU REFERENCE DATE/TIME - SP  sub-file (#63.19) 
     TIU ENTRY POINTER - SP           field (#63.19, 1) 
  
   ORDERED TEST                       field (#63.08, .35) 
     ORDERED TEST                  sub-file (#63.53) 
     LAB TEST ORDERED                 field (#63.53, 13) 
  
   COMMENT                            field (#63.08, .99)         sub-file
 (#63.98) 
     COMMENT                          field (#63.98, .01) 
  
   GROSS DESCRIPTION                  field (#63.08, 1)           sub-file
 (#63.81) 
   MICROSCOPIC DESCRIPTION            field (#63.08, 1.1)         sub-file
 (#63.811) 
   SURGICAL PATH DIAGNOSIS            field (#63.08, 1.4)         sub-file
 (#63.802) 
  
   SPECIMEN                           field (#63.08, .012) 
     SPECIMEN                      sub-file (#63.812) 
     SPECIMEN                         field (#63.812, .01) 
     SPECIMEN TOPOGRAPHY              field (#63.812, .06) 
  
     PARAFFIN BLOCK                   field (#63.812, 1) 
       PARAFFIN BLOCK              sub-file (#63.8121) 
       PARAFFIN BLOCK ID              field (#63.8121, .01) 
       DATE/TIME BLOCK PREPARED       field (#63.8121, .02) 
       STAIN/PROCEDURE                field (#63.8121, 1)      
         STAIN/PROCEDURE           sub-file (#63.8122) 
         STAIN/PROCEDURE              field (#63.8122, .01) 
         SLIDES PREPARED (#)          field (#63.8122, .02) 
         CONTROL SLIDES (#)           field (#63.8122, .03) 
         DATE/TIME SLIDES STAINED     field (#63.8122, .04) 
         SLIDES COUNTED (#)           field (#63.8122, .06) 
         LABELS TO PRINT              field (#63.8122, .07)  
         NON-CONTROL SLIDES COUNTED   field (#63.8122, .09) 
  
     PLASTIC BLOCK                    field (#63.812, 2) 
       PLASTIC BLOCK               sub-file (#63.822) 
       PLASTIC BLOCK ID               field (#63.822, .01) 
       DATE/TIME BLOCK PREPARED       field (#63.822, .02) 
       PLASTIC STAIN/PROCEDURE        field (#63.822, 1)      
         PLASTIC STAIN/PROCEDURE   sub-file (#63.823) 
         PLASTCI STAIN/PROCEDURE      field (#63.823, .01) 
         PLASTIC SLIDES PREPARED (#)  field (#63.823, .02) 
         CONTROL SLIDES (#)           field (#63.823, .03) 
         DATE/TIME SLIDES STAINED     field (#63.823, .04) 
         SLIDES COUNTED (#)           field (#63.823, .06) 
         LABELS TO PRINT              field (#63.823, .07) 
         NON-CONTROL SLIDES COUNTED   field (#63.823, .09) 
  
     FROZEN TISSUE BLOCK              field (#63.812, 3) 
       FROZEN TISSUE BLOCK         sub-file (#63.824) 
       FROZEN COUNTED                 field (#63.824, .01) 
       DATE/TIME FROZEN PREPARED      field (#63.824, .02) 
       STAIN/PROCEDURE                field (#63.824, 1)      
         STAIN/PROCEDURE           sub-file (#63.825) 
         STAIN/PROCEDURE              field (#63.825, .01) 
         SLIDES PREPARED (#)          field (#63.825, .02) 
         CONTROL SLIDES (#)           field (#63.825, .03) 
         DATE/TIME SLIDES STAINED     field (#63.825, .04) 
         SLIDES COUNTED (#)           field (#63.825, .06) 
         LABELS TO PRINT              field (#63.825, .07) 
         NON-CONTROL SLIDES COUNTED   field (#63.825, .09) 
  
  
  
 CYTOPATHOLOGY                        field (#63, 9) 
   CYTOPATHOLOGY                   sub-file (#63.09) 
   DATE/TIME SPECIMEN TAKEN           field (#63.09, .01)  
   DATE/TIME SPECIMEN RECEIVED        field (#63.09, .1) 
   SPECIMEN SUBMITTED BY              field (#63.09, .011) 
   BRIEF CLINICAL HISTORY             field (#63.09, .013)          sub-file
 (#63.913) 
   PREOPERATIVE DIAGNOSIS             field (#63.09, .014)          sub-file
 (#63.914) 
   OPERATIVE FINDINGS                 field (#63.09, .015)          sub-file
 (#63.905) 
   POSTOPERATIVE DIAGNOSIS            field (#63.09, .016)          sub-file
 (#63.906) 
   DATE REPORT COMPLETED              field (#63.09, .03) 
   CYTOPATH ACC #                     field (#63.09, .06) 
   PHYSICIAN                          field (#63.09, .07) 
   REPORT RELEASE DATE/TIME           field (#63.09, .11) 
   TIU REFERENCE DATE/TIME - CY       field (#63.09, .16) 
     TIU REFERENCE DATE/TIME - CY  sub-file (#63.47) 
     TIU ENTRY POINTER - CY           field (#63.47, 1) 
    
   ORDERED TEST                       field (#63.09, .35) 
     ORDERED TEST                  sub-file (#63.51)      
     LAB TEST ORDERED                 field (#63.51, 13) 
    
   COMMENT                            field (#63.09, .99)           sub-file
 (#63.908) 
     COMMENT                          field (#63.908, .01) 
  
   GROSS DESCRIPTION                  field (#63.09, 1)             sub-file
 (#63.91) 
   MICROSCOPIC EXAMINATION            field (#63.09, 1.1)           sub-file
 (#63.911) 
   CYTOPATHOLOGY DIAGNOSIS            field (#63.09, 1.4)           sub-file
 (#63.903) 
  
   SPECIMEN                           field (#63.09, .012)  
     SPECIMEN                      sub-file (#63.902) 
     SPECIMEN                         field (#63.902, .01) 
     SPECIMEN TOPOGRAPHY              field (#63.902, .06) 
     SMEAR PREP                       field (#63.902, 1) 
       SMEAR PREP                  sub-file (#63.9121) 
       SMEAR PREP                     field (#63.9121, .01) 
       STAIN/PROCEDURE                field (#63.9121, 1) 
         STAIN/PROCEDURE           sub-file (#63.9122) 
         STAIN/PROCEDURE              field (#63.9122, .01) 
         SLIDES PREPARED (#)          field (#63.9122, .02) 
         CONTROL SLIDES (#)           field (#63.9122, .03) 
         DATE/TIME SLIDES STAINED     field (#63.9122, .04) 
         SLIDES COUNTED (#)           field (#63.9122, .06) 
         LABELS TO PRINT              field (#63.9122, .07)    
         SLIDES SCREENED (#)          field (#63.9122, .08) 
         NON-CONTROL SLIDES COUNTED   field (#63.9122, .09) 
  
     CELL BLOCK                       field (#63.902, 2) 
       CELL BLOCK                  sub-file (#63.922) 
       CELL BLOCK                     field (#63.922, .01) 
       CELL BLOCK STAIN               field (#63.922, 1) 
         CELL BLOCK STAIN          sub-file (#63.923) 
         CELL BLOCK STAIN             field (#63.923, .01) 
         SLIDES PREPARED (#)          field (#63.923, .02) 
         CONTROL SLIDES (#)           field (#63.923, .03) 
         DATE/TIME SLIDES STAINED     field (#63.923, .04) 
         SLIDES COUNTED (#)           field (#63.923, .06) 
         LABELS TO PRINT              field (#63.913, .07)  
         SLIDES SCREENED (#)          field (#63.923, .08) 
         NON-CONTROL SLIDES COUNTED   field (#63.923, .09) 
  
     MEMBRANE FILTER                  field (#63.902, 3) 
       MEMBRANE FILTER             sub-file (#63.924) 
       MEMBRANE FILTER                field (#63.924, .01) 
       MEMBRANE FILTER STAIN          field (#63.924, 1) 
         MEMBRANE FILTER STAIN     sub-file (#63.9241) 
         MEMBRANE FILTER STAIN        field (#63.9241, .01) 
         SLIDES PREPARED (#)          field (#63.9241, .02) 
         CONTROL SLIDES (#)           field (#63.9241, .03) 
         DATE/TIME SLIDES STAINED     field (#63.9241, .04) 
         SLIDES COUNTED (#)           field (#63.9241, .06) 
         LABELS TO PRINT              field (#63.9241, .07)  
         SLIDES SCREENED (#)          field (#63.9241, .08) 
         NON-CONTROL SLIDES COUNTED   field (#63.9241, .09) 
  
     PREPARED SLIDES                  field (#63.902, 4) 
       PREPARED SLIDES             sub-file (#63.9024) 
       PREPARED SLIDES                field (#63.9024, .01) 
       PREPARED SLIDES STAIN          field (#63.9024, 1) 
         PREPARED SLIDES STAIN     sub-file (#63.90241)     
         PREPARED SLIDES STAIN        field (#63.90241, .01) 
         SLIDES PREPARED (#)          field (#63.90241, .02) 
         CONTROL SLIDES (#)           field (#63.90241, .03) 
         DATE/TIME SLIDES STAINED     field (#63.90241, .04) 
         LABELS TO PRINT              field (#63.90241, .07) 
         SLIDES COUNTED (#)           field (#63.90241, .06)  
         SLIDES SCREENED (#)          field (#63.90241, .08) 
         NON-CONTROL SLIDES COUNTED   field (#63.90241, .09) 
  
     CYTOSPIN                         field (#63.902, 5) 
       CYTOSPIN                    sub-file (#63.9025) 
       CYTOSPIN                       field (#63.9025, .01) 
       CYTOSPIN STAIN                 field (#63.9025, 1) 
         CYTOSPIN STAIN            sub-file (#63.90251) 
         CYTOSPIN STAIN               field (#63.90251, .01) 
         SLIDES PREPARED (#)          field (#63.90251, .02) 
         CONTROL SLIDES (#)           field (#63.90251, .03) 
         DATE/TIME SLIDES STAINED     field (#63.90251, .04) 
         SLIDES COUNTED (#)           field (#63.90251, .06) 
         LABELS TO PRINT              field (#63.90251, .07)  
         SLIDES SCREENED (#)          field (#63.90251, .08) 
         NON-CONTROL SLIDES COUNTED   field (#63.90251, .09) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   This IA supports TelePathology project. The value of
 the fields are used in VI HL7 DICOM PACS messages and TelePathology worklist.  
  DATE ACTIVATED: SEP 20, 2013

NUMBER: 5990                            IA #: 5990
  FILE NUMBER: 130.4                    GLOBAL ROOT: DIC(130.4
  DATE CREATED: JUL 10, 2013            CUSTODIAL PACKAGE: SURGERY
  USAGE: Supported                      TYPE: File
  NAME: ICD SEARCH API FILE             ID: DIC(130.4
GLOBAL REFERENCE: DIC(130.4
FIELD NUMBER: 130.4                     ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   This file contains the ICD and Procedure API
 references.  These allow applications to call the correct search API's based
 on application parameters that control the type of search.  This allows the
 search API's to be controlled by file entries rather than having to hard code
 the calls.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUL 2020
KEYWORDS: API SEARCH

NUMBER: 5991                            IA #: 5991
  FILE NUMBER: 26.15                    GLOBAL ROOT: DGPF(26.15
  DATE CREATED: JUL 17, 2013            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: READ B CROSS REFERENCE OF PRF NATIONAL FLAG FILE
  ID: DGPF(26.15
GLOBAL REFERENCE: DGPF(26.15,'B'
 GENERAL DESCRIPTION:   Health Summary (GMTS) requires read-only access to
 ^DGPF(26.15,"B" in order to retrieve the name of each National Patient Record
 Flag.  These names are used to retrieve and subsequently display flag
 assignment information for inactive PRF assignments.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DGPF
KEYWORDS: PRF NATIONAL FLAG
KEYWORDS: 26.15
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   Active PRF assignments can be retrieved via
 GETACT^DGPFAPI without needing to know the NAME associated with each PRF.  To
 retrieve assignment information on individual flags, the NAME must be known in 
 order to build a flag pointer (GETFLAG^DGPFAPIH).  The ability to read 
 ^DGPF(26.15,"B" will permit the subscribing package to retrieve the NAME of
 any National PRF and subsequently retrieve the assignment information/history. 
 
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 3/11/20 to access ^DGPF(26.15,"B".  
  DATE ACTIVATED: OCT 17, 2013

NUMBER: 5992                            IA #: 5992
  DATE CREATED: JUL 18, 2013            CUSTODIAL PACKAGE: EVENT CAPTURE
  USAGE: Private                        TYPE: Remote Procedure
  NAME: EC FILER                        REMOTE PROCEDURE: EC FILER
 GENERAL DESCRIPTION:   A general purpose Event Capture filer used when filing
 data into ECS files 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: EC FILER
SUBSCRIBING PACKAGE: MYHEALTHEVET
 SUBSCRIBING DETAILS:   FILE THE WORKLOAD CREDIT FORM FROM SM GUI 

NUMBER: 5993                            IA #: 5993
  FILE NUMBER: 1                        GLOBAL ROOT: DIC(
  DATE CREATED: JUL 23, 2013            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RTLS POINTING TO FILE 1
  ID: DIC(
 GENERAL DESCRIPTION:   The Real Time Location System (RTLS) is requesting
 approval to point to the file of files (#1), field FILE ID (#1), in the
 PENDING RTLS EVENTS file (#6930). This is to be used for building calls to
 File Manager API'S dynamically.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM
 SUBSCRIBING DETAILS:   Within Engineering files API calls are made in order to
 capture record changes and send them back to RTLS.  
  DATE ACTIVATED: JUN 30, 2014

NUMBER: 5994                            IA #: 5994
  DATE CREATED: JUL 29, 2013            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGT7MA
  NAME: DBIA5994                        ID: MAGT7MA
 GENERAL DESCRIPTION:   VistA Imaging gives permission to Laboratory Package to
 call CANCEL^MAGT7MA, EDIT^MAGT7MA, NEW^MAGT7MA, REPORT^MAGT7MA .  These calls
 create VistA Imaging HL7 DICOM PACS messages pertain to Anatomic Pathology
 order updates. The messages are stored in PACS MESSAGE file (#2006.5) and are
 processed by VistA Imaging DICOM Text gateway.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAGT7MA
COMPONENT/ENTRY POINT: CANCEL
 COMPONENT DESCRIPTION:   Creates HL7 order message for a cancelled order.  
VARIABLES: LRDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the LRDFN field (#.01) from the patient's
 record in the LAB DATA file (#63).  
VARIABLES: LRSS                         TYPE: Input
 VARIABLES DESCRIPTION:   The accession area for the record in the LAB DATA
 file (#63): "CY", "EM", or "SP".  
VARIABLES: LRI                          TYPE: Input
 VARIABLES DESCRIPTION:   The inverse DATE/TIME SPECIMEN TAKEN (sub-field #.01)
 of SURGICAL PATHOLOGY field (#8), CYTOPATHOLOGY field (#9) or EM field (#2) of
 the LAB DATA file (#63).  
COMPONENT/ENTRY POINT: EDIT
 COMPONENT DESCRIPTION:   Creates HL7 order message for accession modification. 
 
VARIABLES: LRDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the LRDFN field (#.01) from the patient's
 record in the LAB DATA file (#63).  
VARIABLES: LRI                          TYPE: Input
 VARIABLES DESCRIPTION:   The inverse DATE/TIME SPECIMEN TAKEN (sub-field #.01)
 of SURGICAL PATHOLOGY field (#8), CYTOPATHOLOGY field (#9) or EM field (#2) of
 the LAB DATA file (#63).  
VARIABLES: LRSS                         TYPE: Input
 VARIABLES DESCRIPTION:   The accession area for the record in the LAB DATA
 file (#63): "CY", "EM", or "SP". 
VARIABLES: MAGNEWCASE                   TYPE: Input
 VARIABLES DESCRIPTION:   This variable must be newed and set to 1 during
 creation of a new accession.  
COMPONENT/ENTRY POINT: NEW
 COMPONENT DESCRIPTION:   Creates HL7 order message for a new accession.  
VARIABLES: LRDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the LRDFN field (#.01) from the patient's
 record in the LAB DATA file (#63).  
VARIABLES: LRSS                         TYPE: Input
 VARIABLES DESCRIPTION:   The accession area for the record in the LAB DATA
 file (#63): "CY", "EM", or "SP". 
VARIABLES: LRI                          TYPE: Input
 VARIABLES DESCRIPTION:   The inverse DATE/TIME SPECIMEN TAKEN (sub-field #.01)
 of SURGICAL PATHOLOGY field (#8), CYTOPATHOLOGY field (#9) or EM field (#2) of
 the LAB DATA file (#63).  
COMPONENT/ENTRY POINT: REPORT
 COMPONENT DESCRIPTION:   Creates HL7 order message for an electronically
 signed report.  
VARIABLES: LRDATA(1)                    TYPE: Input
 VARIABLES DESCRIPTION:   The inverse DATE/TIME SPECIMEN TAKEN (sub-field #.01)
 of SURGICAL PATHOLOGY field (#8), CYTOPATHOLOGY field (#9) or EM field (#2) of
 the LAB DATA file (#63).  
VARIABLES: LRSS                         TYPE: Input
 VARIABLES DESCRIPTION:   The accession area for the record in the LAB DATA
 file (#63): "CY", "EM", or "SP". 
VARIABLES: LRDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the LRDFN field (#.01) from the patient's
 record in the LAB DATA file (#63).  
VARIABLES: LRSF                         TYPE: Input
 VARIABLES DESCRIPTION:   Sub-file number for the accession area: 63.09, 63.02,
 or 63.08 
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   Laboratory package will call VistA Imaging routine to
 generate HL7 DICOM PACS messages.  
  If event driver protocols, related to laboratory order updates, are available
 in the future this ICR can be retired after VistA Imaging subscribes to the
 protocols.  
  DATE ACTIVATED: SEP 27, 2013

NUMBER: 5995                            IA #: 5995
  FILE NUMBER: 704.116                  GLOBAL ROOT: MDC(704.116,
  DATE CREATED: JUL 29, 2013            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CLIO OBS SET FILE
  ID: MDC(704.116,
GLOBAL REFERENCE: MDC(704.116,D0,0)
FIELD NUMBER: .01                       FIELD NAME: SET ID
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ENTERED DATE TIME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   VPR*1*2, released fall 2013, to access MDC(704.116 Obs
 Set file, used in VPRDMDC - with guidance from CliO developers.  
  DATE ACTIVATED: JAN 14, 2014

NUMBER: 5996                            IA #: 5996
  GLOBAL ROOT: MDC(704.1161,            DATE CREATED: JUL 29, 2013
  CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CLIO OBS SET OBS PAIR FILE
  ID: MDC(704.1161,
GLOBAL REFERENCE: MDC(704.1161,0)
FIELD NUMBER: .01                       FIELD NAME: SET ID
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: OBS ID
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Includes use of the AS index on OBS_ID and SET_ID 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 704.1161
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   VPR*1*2, released fall 2013, to access MDC(704.116 Obs
 Set Obs Pair file, used in QRYSET^VPRDMDC - with guidance from CliO
 developers.  
  DATE ACTIVATED: JAN 14, 2014

NUMBER: 5997                            IA #: 5997
  DATE CREATED: JUL 30, 2013            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGTP005
  NAME: DBA5997                         ID: MAGTP005
 GENERAL DESCRIPTION:   VistA Imaging gives permission to Laboratory Package to
 call ADD^MAGTP005 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAGTP005
COMPONENT/ENTRY POINT: ADD
 COMPONENT DESCRIPTION:   Adds a new record to MAG PATH CASELIST file
 (#2005.42).  
VARIABLES: LRAC                         TYPE: Input
 VARIABLES DESCRIPTION:   Lab accession number 
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   Laboratory package will call ADD^MAGTP005 to add a new
 record to MAG PATH CASELIST file (#2005.42). If an event driver protocol 
 related to a new lab order is available in the future, this ICR can be retired
 after VistA Imaging subscribes to the protocol.  
  DATE ACTIVATED: SEP 20, 2013

NUMBER: 5998                            IA #: 5998
  DATE CREATED: JUL 30, 2013
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA5998
  STATUS: Pending

NUMBER: 5999                            IA #: 5999
  GLOBAL ROOT: MDC(704.1122,            DATE CREATED: JUL 30, 2013
  CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CLIO OBS FLOWSHEET SUPP PAGE FILE
  ID: MDC(704.1122,
GLOBAL REFERENCE: MDC(704.1122,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ID 
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: VIEW ID
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: PATIENT ID
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DISPLAY NAME
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1                        FIELD NAME: SET ID
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: MDC(704.1122,D0,.1)
FIELD NUMBER: .11                       FIELD NAME: ACTIVATED DATE TIME
  LOCATION: .1;1                        ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Includes use of the ADT index on PATIENT_ID and
 ACTIVATED_DATE_TIME 
GLOBAL REFERENCE: MDC(704.1122,D0,.2)
FIELD NUMBER: .21                       FIELD NAME: DEACTIVATED DATE TIME
  LOCATION: .2;1                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 704.1122
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   VPR*1*2, released fall 2013, to access MDC(704.1122 Obs
 Flowsheet Supp Page file, used in QRYSET^VPRDMDC - with guidance from CliO
 developers.  
  DATE ACTIVATED: JAN 14, 2014

NUMBER: 6000                            IA #: 6000
  DATE CREATED: JUL 31, 2013            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGVRD03
  NAME: MAGV GET IRRADIATION DOSE       ID: MAGVRD03
 GENERAL DESCRIPTION:   The TAG^ROUTINE documented will return the attributes
 for the irradiation instance related to the patient and the procedure.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAG*3.0*137
KEYWORDS: RA*5.0*113
KEYWORDS: RADIATION DOSE
KEYWORDS: RADUTL
KEYWORDS: RAORDU
KEYWORDS: RA*5.0*119
KEYWORDS: MAG*3.0*157
COMPONENT/ENTRY POINT: REFRESH
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of the array, passed by reference,
 in which irradiation dose data is saved. All data is returned in its external
 format. PHANTOM TYPE will not be used in this iteration. The data returned in
 the subscripted array is delimited by the vertical bar "|".  
  
 Key variable: ARRAY(1).  The first piece indicates success (0) or failure
 (-13).  The second piece is null and the third piece is the number of records 
 returned.  
  
 Note: ARRAY(1) can have a value of "0``0" in which case the VistA RIS takes no
 action.  
  
 Example: CT SCAN data returned 
 ------------------------------
  DVA>ZW ARRAY 
  ARRAY(1)="0``2" 
  ARRAY(2)="TYPE|CT" 
  ARRAY(3)="IRRADIATION INSTANCE UID 
   1.2.841.113411.2.1.2411.10311244477 
   .365.1.63874544.8.7.2013.131" 
  ARRAY(4)="TARGET REGION|T-D0010" 
  ARRAY(5)="CTDIVOL|8.12" 
  ARRAY(6)="DLP|365.25" 
  ARRAY(7)="PHANTOM TYPE|" 
  ARRAY(8)="TYPE|CT" 
  ARRAY(9)="IRRADIATION INSTANCE UID 
   1.2.841.113411.2.1.2411.10311244477 
   .365.1.63874544.8.7.2013.132" 
  ARRAY(10)="TARGET REGION|R-FAB56" 
  ARRAY(11)="CTDIVOL|7.02" 
  ARRAY(12)="DLP|500.001" 
  ARRAY(13)="PHANTOM TYPE|" 
  
 Please note that for a scout image (a preliminary image taken of a body region
 before a definitive imaging study) CTDIvol and DLP may not have values.  
  
  
 Example: Fluoroscopy data returned 
 ---------------------------------- 
  DVA>ZW ARRAY 
  ARRAY(1)="0``2" 
  ARRAY(2)="TYPE|FLUORO" 
  ARRAY(3)="ESTIMATE|" 
  ARRAY(4)="TOTAL TIME IN FLUOROSCOPY|21" 
  ARRAY(5)="DOSE AREA PRODUCT|0" 
  ARRAY(6)="DOSE (RP) TOTAL (AKE)|0" 
  ARRAY(7)="FLUORO DOSE (RP) TOTAL|0" 
  ARRAY(8)="FLUORO DOSE AREA PRODUCT TOTAL|0" 
  ARRAY(9)="CINE DOSE (RP) TOTAL|0" 
  ARRAY(10)="CINE DOSE AREA PRODUCT TOTAL|0" 
  ARRAY(11)="CINE TIME|4" 
  ARRAY(12)="TYPE|FLUORO" 
  ARRAY(13)="ESTIMATE|" 
  ARRAY(14)="TOTAL TIME IN FLUOROSCOPY|22" 
  ARRAY(15)="DOSE AREA PRODUCT|0.00000012" 
  ARRAY(16)="DOSE (RP) TOTAL (AKE)|4.2" 
  ARRAY(17)="FLUORO DOSE (RP) TOTAL|5.1" 
  ARRAY(18)="FLUORO DOSE AREA PRODUCT TOTAL|.00000023" 
  ARRAY(19)="CINE DOSE (RP) TOTAL|6200" 
  ARRAY(20)="CINE DOSE AREA PRODUCT TOTAL|3.2" 
  ARRAY(21)="CINE TIME|23" 
   
 The VistA RIS relies on the data from the following attributes: "TOTAL TIME IN
 FLUOROSCOPY", "DOSE (RP) TOTAL (AKE)" & "FLUORO DOSE AREA PRODUCT TOTAL".  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the DFN of the patient.  
VARIABLES: PROCEDURE                    TYPE: Input
 VARIABLES DESCRIPTION:   This is the accession number of the study.  
  
 The accession number can be in its legacy format: mmddyy-case_# 
  
 -or- 
  
 The accession number can be in its site specific format: 
 site_id-mmddyy-case_#.  
  
  
  
 Note 
 ----
 'site_id' is the first three digits of the station number of the institution
 where this software is installed.  Example: Institution Hines; site_id = 578 
  
 'mm' is the month represented by two digits. Example: July = 07 
  
 'dd' is the day of a month represented by two digits.  Example: the 4th day of
 July = 04 
  
 'yy' is the year represented by the last two digits of that year.  Example:
 2013 = 13 
VARIABLES: PROCTYPE                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the imaging type of the procedure. CT Scan
 imaging studies will pass "CT"; General Radiology imaging studies will pass
 "FLUORO".  
COMPONENT/ENTRY POINT: ARRAY
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   The VistA Radiology/Nuclear Medicine application will
 call REFRESH^MAGVRD03 function whenever a Radiation Dose Structured Report
 (RDSR) enabled study is advanced to an examination status of 'Complete'.  
  DATE ACTIVATED: AUG 14, 2013

NUMBER: 6001                            IA #: 6001
  DATE CREATED: AUG 01, 2013            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: LRLAB security key
 GENERAL DESCRIPTION:   This integration agreement allows use of LRLAB security
 key.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LRLAB
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   Holders of LRLAB security key will be able to access
 TelePathology Worklist and review released pathology reports and patient
 health summary reports in VistA Imaging TelePatholgy Worklist application. 
  DATE ACTIVATED: SEP 20, 2013

NUMBER: 6002                            IA #: 6002
  DATE CREATED: AUG 01, 2013            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPFMPI
  NAME: DGPFMPI                         ID: DGPFMPI
 GENERAL DESCRIPTION:   This routine contains a function call for use by MPIF
 to get the Category I flags from each VistA treatment facility that sees the 
 patient.  
  
 The following summarizes the process flow where MPIF will call this function: 
  
 First, a patient is added to the local VA system and a background job called
 VAFC BATCH UPDATE JOB runs regularly on the VA system which assigns local
 ICNs.  Second, Once the local ICN is assigned, a background job called MPIF 
 LOC/MIS ICN RES runs (scheduled to run regularly in the background on the VA
 system).  This background job gets the national ICN and populates the
 patient's treating facilities in the Treating Facility List file (#391.91). 
 After the Treating Facilities are added for the patient, the MPIF logic will
 make a function call to the EN1^DGPFMPI routine documented in this ICR.  
  STATUS: Active
KEYWORDS: MPIF
KEYWORDS: PRF
KEYWORDS: DGPFMPI
COMPONENT/ENTRY POINT: $$EN1(DFN,DGTRANS)
 COMPONENT DESCRIPTION:   This function gets the list of treating facilities
 that have seen the patient and queries each facility for their Category I
 flags on record to update the local system.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN (Pointer to the Patient File (#2)). This
 parameter is required.  
VARIABLES: DGTRANS                      TYPE: Output
 VARIABLES DESCRIPTION:   This function returns DGTRANS as a value of 0 or 1
 (unsuccessful or successful). MPIF will not do anything with the returned
 value.  
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA
 SUBSCRIBING DETAILS:   The MPIF*1.0*58 patch will use this ICR.  
  DATE ACTIVATED: AUG 21, 2013

NUMBER: 6003                            IA #: 6003
  FILE NUMBER: 68                       GLOBAL ROOT: LRO(68
  DATE CREATED: AUG 06, 2013            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA6003
  ID: LRO(68
GLOBAL REFERENCE: LRO(68,D0,1,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: LRDFN
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
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,3)
FIELD NUMBER: 13.5                      FIELD NAME: INVERSE DATE
  LOCATION: 3;5                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LRO(68,LRAA,1,LRAD)
 GLOBAL DESCRIPTION:   $D function is executed on ^LRO(68,LRAA,1,LRAD) 
GLOBAL REFERENCE: LRO(68,LRAA,1,LRAD,1,LRAN)
 GLOBAL DESCRIPTION:   $D and $O functions are executed on
 ^LRO(68,LRAA,1,LRAD,1,LRAN) 
GLOBAL REFERENCE: LRO(68,'B',LRSS,0)
 GLOBAL DESCRIPTION:   $Order function is executed on ^LRO(68,"B",LRSS,0)   
 where LRSS equals "CY":"SP":"EM" 
 GENERAL DESCRIPTION:   This agreement provides access to Laboratory patient
 ID, date and accession number. 
  STATUS: Active
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   This IA supports TelePathology project - TelePathology
 VistA Imaging Worklist.  
  DATE ACTIVATED: SEP 20, 2013

NUMBER: 6004                            IA #: 6004
  FILE NUMBER: 74.1                     GLOBAL ROOT: RA(74.1,
  DATE CREATED: AUG 06, 2013
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ STANDARD REPORTS File (#74.1)
  ID: RA(74.1,
 GENERAL DESCRIPTION:   Imaging requests read access to the STANDARD REPORTS
 File (#74.1) to allow the Hybrid DICOM Gateway Importer application to display
 the standard report data for user selection when reconciling imported studies. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HDIG IMPORTER
KEYWORDS: IMAGING
KEYWORDS: MAG*3.0*138
KEYWORDS: MEDICOM
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   The VistA Imaging Hybrid DICOM Gateway Importer
 application will call RPC: MAGV GET RAD STD RPTS to populate a GUI selection
 drop-down box during the artifact reconciliation workflow for imported
 studies.  
  
 The code implementing the RPC is GETRADSR^MAGVIMRA. It will traverse file
 entries by direct read of ^RA(74.1,D0). Fields will be extracted via FileMan
 API calls to $$GET1^DIQ(). The extracted fields will be: 
  
   NAME (#.01), REPORT TEXT (#200), IMPRESSION TEXT (#300).  
  
 The extracted data will be XML tagged and returned as an array.  
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Patch MECH*1.0*1 files information received from HL7
 new-order messages about imaging studies performed in the community but not
 entered through VistA.  In order to associate appropriate standard report text
 with the order to allow the order to be set to Complete status.  Function 
 $$REGISTER^MECHACIROREG() will invoke FileMan function $$FIND1^DIC() to locate
 the appropriate standard report, and FileMan function $$GET1^DIQ() to retrieve
 the standard report text. ADDED 4/27/2022, effective with MECH*1.0*1 Medicom
 Class 3 product Document Only 
  DATE ACTIVATED: AUG 14, 2013

NUMBER: 6005                            IA #: 6005
  FILE NUMBER: 78.3                     GLOBAL ROOT: RA(78.3,
  DATE CREATED: AUG 06, 2013
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ DIAGNOSTIC CODES File (#78.3)
  ID: RA(78.3,
GLOBAL REFERENCE: RA(78.3,D0
FIELD NUMBER: .01                       FIELD NAME: DIAGNOSTIC CODE 
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: INACTIVE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RA(78.3,D0,1
FIELD NUMBER: 100                       FIELD NAME: DISPLAY TEXT
  LOCATION: 1;E1,245                    ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Imaging requests read access to the DIAGNOSTIC CODES
 File (#78.3) to allow the Hybrid DICOM Gateway Importer application to display
 diagnostic code data for selection by users when reconciling imported studies. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IMAGING
KEYWORDS: HDIG IMPORTER
KEYWORDS: MAG*3.0*138
KEYWORDS: ISI
KEYWORDS: ISI*1.1*110 DFN
KEYWORDS: VistARad COTS
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   The VistA Imaging Hybrid DICOM Gateway Importer
 application will call RPC: MAGV GET RAD DX CODES to populate a GUI selection
 drop-down box during the artifact reconciliation workflow for imported
 studies.  
  
 The code implementing the RPC is GETRADDX^MAGVIMRA. It will traverse file
 entries by direct read of ^RA(78.3,D0). Fields will be extracted via FileMan
 API calls to $$GET1^DIQ(). The fields to be extracted are: 
  
   DIAGNOSTIC CODE (#.01), DESCRIPTION (#2), INACTIVE (#5), and 
   DISPLAY DATA (#100).  
  
 The extracted data will be XML tagged and returned as an array.  
SUBSCRIBING PACKAGE: ISI IMAGING
 SUBSCRIBING DETAILS:   Added effective with ISI*1.1*110 
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Added 9/27/24 effective with patch MECH*1.0 MEDICOM
 TECHNOLOGIES is requesting to read via the FileMan call LIST^DIC, the
 following fields: DIAGNOSTIC CODE (#.01), DESCRIPTION (#2), INACTIVE (#5), and
 DISPLAY DATA (#100).  
  DATE ACTIVATED: AUG 14, 2013

NUMBER: 6006                            IA #: 6006
  DATE CREATED: AUG 06, 2013
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RARTE7
  NAME: IMAGING ABNORMAL ALERT TRIGGER  ID: RARTE7
 GENERAL DESCRIPTION:   Imaging requests permission to call two elements of the
 RA package alert handling code for DIAGNOSTIC CODE alert generation.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IMAGING
KEYWORDS: HDIG IMPORTER
KEYWORDS: MAG*3.0*138
COMPONENT/ENTRY POINT: ANYDX
 COMPONENT DESCRIPTION:   Arrays all DIAGNOSTIC CODES for an examination.  
VARIABLES: RADFN                        TYPE: Used
 VARIABLES DESCRIPTION:   Patient index (D0) of the RAD/NUC MED PATIENT file
 (#70).  
VARIABLES: RADTI                        TYPE: Used
 VARIABLES DESCRIPTION:   Registered Exams timestamp index (D1) of the RAD/NUC
 MED PATIENT file (#70).  
VARIABLES: RACNI                        TYPE: Used
 VARIABLES DESCRIPTION:   Examination index (D2) of the RAD/NUC MED PATIENT
 file (#70).  
VARIABLES: ARRAY                        TYPE: Both
 VARIABLES DESCRIPTION:   (Passed by reference) Name of the array in which
 DIAGNOSTIC CODES for an examination are stored.  
COMPONENT/ENTRY POINT: ALERT
 COMPONENT DESCRIPTION:   Triggers alerts based on the GENERATE ABNORMAL ALERT?
 field (#4) of the DIAGNOSIC CODES file (#78.3).  
VARIABLES: RADFN                        TYPE: Used
 VARIABLES DESCRIPTION:   Patient index (D0) of the RAD/NUC MED PATIENT file
 (#70).  
VARIABLES: RADTI                        TYPE: Used
 VARIABLES DESCRIPTION:   Registered Exams timestamp index (D1) of the RAD/NUC
 MED PATIENT file (#70).  
VARIABLES: RACNI                        TYPE: Used
 VARIABLES DESCRIPTION:   Examination index (D2) of the RAD/NUC MED PATIENT
 file (#70).  
VARIABLES: RANY1                        TYPE: Used
 VARIABLES DESCRIPTION:   Number of DIAGNOSTIC CODES defined before an edit
 operation on the record. For Imported studies, this is 0.  
VARIABLES: RANY2                        TYPE: Used
 VARIABLES DESCRIPTION:   Number of DIAGNOSTIC CODES defined after an operation
 on the record. Set by prior call to $$ANYDX^RARTE7().  
VARIABLES: RAA2                         TYPE: Used
 VARIABLES DESCRIPTION:   Array of DIAGNOSTIC CODES. Set by prior call to
 $$ANYDX^RARTE7().  
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   The VistA Imaging Hybrid DICOM Gateway Importer
 application allows users to select DIAGNOSTIC CODES during the artifact
 reconciliation workflow for imported studies. After EXAMINATION STATUS is
 advanced to COMPLETE, the RPC: MAGV RAD STAT COMPLETE will generate alerts for
 applicable DIAGNOSTIC CODES by calling ALERT^MAGVIMRA. This tag will
 initialize variables expected by the called components.  
  
 A call to $$ANYDX^RARTE7() will retrieve existing DIAGNOSTIC CODE information
 for the current exam. A subsequent call to ALERT^RARTE7() will trigger the
 alerts.  
  DATE ACTIVATED: AUG 14, 2013

NUMBER: 6007                            IA #: 6007
  FILE NUMBER: 79.1                     GLOBAL ROOT: RA(79.1,
  DATE CREATED: AUG 06, 2013
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ IMAGING LOCATIONS File (#79.1)
  ID: RA(79.1,
 GENERAL DESCRIPTION:   Imaging requests read access to the IMAGING LOCATIONS
 File (#79.1) to allow the Hybrid DICOM Gateway Importer application data for
 selection by users when reconciling imported studies.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IMAGING
KEYWORDS: HDIG IMPORTER
KEYWORDS: MAG*3.0*138
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   The VistA Imaging Hybrid DICOM Gateway Importer
 application will call RPC: MAGV GET RAD IMAGING LOCATIONS to populate a GUI
 selection box during the artifact reconciliation workflow for imported
 studies.  
  
 The code implementing the RPC is GETRADLC^MAGVIMRA. It will traverse file
 entries by direct read of ^RA(79.1,D0). Fields will be extracted via FileMan
 API calls to $$GET1^DIQ(). The fields to be extracted are: 
  
   LOCATION (#.01), CREDIT METHOD (#21).  
  
 The extracted data will be XML tagged and returned as an array.  
  DATE ACTIVATED: AUG 14, 2013

NUMBER: 6008                            IA #: 6008
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: AUG 08, 2013            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: DBIA6008 READ ACCESS TO FILE 200
  ID: VA(200
GLOBAL REFERENCE: DMMS UNITS
FIELD NUMBER: 720                       FIELD NAME: DMMS UNITS
  LOCATION: EC;0                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The DMMS unit to which this person has access for
 entering data and generate reports.  
 GENERAL DESCRIPTION:   Retrieves all authorized DSS Unit IENs from NEW PERSON
 file using "EC" cross reference.  ^VA(200,D0,"EC",DSS Unit IEN) 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MYHEALTHEVET

NUMBER: 6009                            IA #: 6009
  FILE NUMBER: 720.3                    GLOBAL ROOT: ECJ(
  DATE CREATED: AUG 08, 2013            CUSTODIAL PACKAGE: EVENT CAPTURE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA6009 READ ACCESS TO FILE 720.3
  ID: ECJ(
GLOBAL REFERENCE: ECJ(D0,0)
FIELD NUMBER: 1                         FIELD NAME: INACTIVE DATE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the date that this event code screen was
 inactivated.  
GLOBAL REFERENCE: ECJ(D0,'PRO')
FIELD NUMBER: 52.1                      FIELD NAME: PROCEDURE
  LOCATION: PRO;1                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Name of the procedure.  
FIELD NUMBER: 53                        FIELD NAME: SYNONYM
  LOCATION: PRO;2                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the synonym for the procedure
 associated with this event code screen.  
 GENERAL DESCRIPTION:   MHV Secure Messaging - Work Load Credit functionality
 allows users to save the workload credit using the assigned DSS units, and
 stores the record  in Event Capture System.  The use of the DSS units is the
 same as in ECS, users have access to link their work to DSS units that send
 the record to PCE, as well as historical DSS units for historical workload 
 credit forms that do not send the information to PCE.  To implement this 
 functionality, MHV SM reads files and calls existing APIs from Event Capture
 System.  
  
 MyHealtheVet (MHV) uses the "AP" cross reference in EC EVENT CODE SCREENS File
 (#720.3) to get DSS Units, Categories, Procedures and IEN values of a location
 specified in MHV Secure Messaging front end.  Using IEN of the zero node, MHV
 references the fields Inactive Date, Procedure and Synonym from file (#720.3). 
 If data in ^ECJ(D0,0) exists, Inactive Date is retrieved to see if Procedure
 is active or not.  ^ECJ(D0,'PRO') node is used to retrieve Synonym and
 Procedure Name.  
  ^ECJ("AP",Location IEN,DSS Unit IEN,Cateogry,Procedure, IEN) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MYHEALTHEVET
 SUBSCRIBING DETAILS:   Used by Secure Messaging in MHV 
  DATE ACTIVATED: NOV 07, 2013

NUMBER: 6010                            IA #: 6010
  DATE CREATED: AUG 08, 2013            CUSTODIAL PACKAGE: EVENT CAPTURE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ECUERPC
  NAME: DBIA6010-EVENT CAPTURE API-ECUERPC
  ID: ECUERPC
 GENERAL DESCRIPTION:   MHV Secure Messaging - Work Load Credit functionality
 allows users to save the workload credit using the assigned DSS units, and
 stores the record in Event Capture System.  The use of the DSS units is the
 same as in ECS, users have access to link their work to DSS units that send
 the record to PCE, as well as historical DSS units for historical workload
 credit forms that do not send the information to PCE.  To implement this
 functionality, MHV SM reads files and calls existing APIs from Event Capture
 System.  
     
 EC routine ELIG^ECUERPC is used to retrieve Patient Eligibility details.  This
 routine is also called via RPC [EC GETPATELIG].  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ELIG
 COMPONENT DESCRIPTION:   $$ELIG^ECUERPC(RESULTS,ECARY) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   First piece of ECARY.  Patient IEN in PATIENT File
 (#2) 
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   Output array with eligibilities.  Value store at
 array is Primary/Secondary Elig Flag^Elig IEN^Elig Description 
SUBSCRIBING PACKAGE: MYHEALTHEVET
 SUBSCRIBING DETAILS:   Used by Secure Messaging in MHV 
  DATE ACTIVATED: NOV 07, 2013

NUMBER: 6011                            IA #: 6011
  DATE CREATED: AUG 08, 2013            CUSTODIAL PACKAGE: EVENT CAPTURE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ECUERPC1
  NAME: DBIA6011-EVENT CAPTURE API-ECUERPC1-PATCLAST
  ID: ECUERPC1
 GENERAL DESCRIPTION:   MHV Secure Messaging - Work Load Credit functionality
 allows users to save the workload credit using the assigned DSS units, and
 stores the record in Event Capture System.  The use of the DSS units is the
 same as in ECS, users have access to link their work to DSS units that send
 the record to PCE, as well as historical DSS units for historical workload
 credit forms that do not send the information to PCE.  To implement this
 functionality, MHV SM reads files and calls existing APIs from Event Capture
 System.  
        
 EC routine PATCLAST^ECUERPC1 is used to retrieve Patient status and 
 Classification data.  This routine is also called via RPC [EC GETPATCLASTAT].  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PATCLAST
 COMPONENT DESCRIPTION:   $$PATCLAST^ECUERPC1(RESULTS,ECARY) 
VARIABLES: ECDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient(#2) IEN.  First piece of ECARY.  
VARIABLES: ECD                          TYPE: Input
 VARIABLES DESCRIPTION:   DSS Unit(#724) IEN.  Second piece of ECARY.  
VARIABLES: ECDT                         TYPE: Input
 VARIABLES DESCRIPTION:   Procedure date and time in fileman format.  Third
 piece of ECARY.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   Patient Status and Classifications delimited by ^.  
 Patient Status: I for inpatient and O for outpatient 
  
 Classification: 2 - Agent Orange                 
                 3 - Ionizing Radiation           
                 4 - SC Condition                 
                 5 - Environmental                
                     Contaminations/SWAC          
                 6 - Military Sexual Trauma       
                 7 - Head/Neck Cancer             
                 8 - Combat Veteran               
                 9 - Project 112/SHAD             
                10 - Camp Lejeune Veteran        
  
 Data after the ~ refers to those classifications that must be asked by front
 end application when the answer to SC = No.  Data after "~" 1 - Agent Orange 2
 - Ionizing Radi. 3 - Env Cont/SWAC 
SUBSCRIBING PACKAGE: MYHEALTHEVET
 SUBSCRIBING DETAILS:   Used by Securing Messaging in MHV 
  DATE ACTIVATED: JAN 10, 2017

NUMBER: 6012                            IA #: 6012
  DATE CREATED: AUG 08, 2013            CUSTODIAL PACKAGE: EVENT CAPTURE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ECFLRPC
  NAME: DBIA6012-EVENT CAPTURE API-ECFLRPC
  ID: ECFLRPC
 GENERAL DESCRIPTION:   MHV Secure Messaging - Work Load Credit functionality
 allows users to save the workload credit using the assigned DSS units, and
 stores the record in Event Capture System.  The use of the DSS units is the
 same as in ECS, users have access to link their work to DSS units that send
 the record to PCE, as well as historical DSS units for historical workload
 credit forms that do not send the information to PCE.  To implement this
 functionality, MHV SM reads files and calls existing APIs from Event Capture
 System via VistA's HL7 interface.  Event Capture routine ECFLRPC is used to
 file data in Event Capture Patient File (#721) and it is called from the My 
 HealtheVet HL7 filer routine.  
  
              
 EC routine FILE^ECFLRPC is used to file data in Event Capture Patient File
 (#721). 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: FILE
 COMPONENT DESCRIPTION:   FILE^ECFLRPC(RESULT,ECARY) 
VARIABLES: ECARY                        TYPE: Input
 VARIABLES DESCRIPTION:   Arrary with data to be filed 
  ECARY("ECFILE") = Event Capture Patient File (#721) 
  ECARY("ECL")    = Location 
  ECARY("ECD")    = DSS Unit 
  ECARY("ECC")    = Category 
  ECARY("ECDT")   = Date and Time of Procedure 
  ECARY("ECP")    = Procedure 
  ECARY("ECDFN")  = Patient 
  ECARY("ECMN")   = Ordering Section 
  ECARY("ECDUZ")  = Entered/Edited By 
  ECARY("ECPTSTAT")=Patient Status 
  ECARY("ECU1"..."ECUN") = List of Providers 
  ECARY("ECDX")   = Primary Diagnosis 
  ECARY("ECDXS")  = Secondary diagnosis codes 
  ECARY("EC4")    = Associated Clinic 
  ECARY("ECELIG") = Patient Eligibility 
  ECARY("ECLASS") = Patient Classification data 
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Success or Failure and message 
SUBSCRIBING PACKAGE: MYHEALTHEVET
  DATE ACTIVATED: FEB 25, 2015

NUMBER: 6013                            IA #: 6013
  FILE NUMBER: 724                      GLOBAL ROOT: ECD(
  DATE CREATED: AUG 08, 2013            CUSTODIAL PACKAGE: EVENT CAPTURE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DBIA6013-READ ACCESS TO DSS UNIT FILE, #724
  ID: ECD(
GLOBAL REFERENCE: ECD(D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Name of the DSS Unit.  
FIELD NUMBER: 5                         FIELD NAME: INACTIVE(Y/N)
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Indicates if DSS Unit is inactive or not.  
FIELD NUMBER: 13                        FIELD NAME: SEND TO PCE
  LOCATION: 0;14                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Field indicating Send to PCE Yes or No.  
 GENERAL DESCRIPTION:   MHV Secure Messaging - Work Load Credit functionality
 allows users to save the workload credit using the assigned DSS units, and
 stores the record in Event Capture System.  The use of the DSS units is the
 same as in ECS, users have access to link their work to DSS units that send
 the record to PCE, as well as historical DSS units for historical workload
 credit forms that do not send the information to PCE.  To implement this
 functionality, MHV SM reads files and calls existing APIs from Event Capture
 System.  
  
 MyHealtheVet (MHV) references Event Capture data from DSS Unit File (#724).
 When provider is ready to file a workload, he/she is presented with a workload
 form.  On the form, they have "DSS Units" drop down box.  In the drop down
 box, MHV needs to present to Provider all the active DSS Units that he/she has
 access to.  To fill the drop down box, MHV calls an MHV RPC called "MHV
 GETDSSUNIT" which has logic to retrieve provider's assigned DSS Units and
 their associated fields (Name, Inactive, SEND to PCE flag).  "MHV GETDSSUNIT"
 sends DSS units back to frontend which uses them to populate drop down box. 
 Then provider can select one of those DSS Units to file workload. Three
 conditions need to be satisfied before DSS Unit can be presented to provider 
 1. DSS Unit must be active.  2. Provider should have that DSS Unit in the
 assigned (MHV) list of DSS Units.  3. DSS Unit should also be associated with
 Location (Associated clinic) selected in front-end MHV GETDSSUNIT RPC checks
 for these three conditions and sends back DSS Units that pass this criteria. 
 MHV reads DSS Unit (#724) file to get Name, Inactive flag, SEND TO PCE flag
 values.  At this time, it will result in only 2 assigned (MHV) DSS Units.  But
 in future, it may return more DSS Units.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MYHEALTHEVET
 SUBSCRIBING DETAILS:   Used by Securing Messaging in MHV.  
  DATE ACTIVATED: NOV 15, 2013

NUMBER: 6014                            IA #: 6014
  FILE NUMBER: 43                       GLOBAL ROOT: DG(43
  DATE CREATED: AUG 12, 2013            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: MEANS TEST DATA FIELDS IN MAS PARAMETERS FILE
  ID: DG(43
GLOBAL REFERENCE: DG(43,D0,'MT',0)
FIELD NUMBER: 17                        FIELD NAME: CHILD INCOME EXCLUSION 
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Access to fields in the MEANS TEST DATA (#43.03)
 multiple in the MAS PARAMETERS (#43) file.  
  
 EAS routine EASECSCU sets a local variable to the zeroth node of an entry in
 the Means Test Data (#43.03) multiple in the MAS Parameters (#43) file. Only
 the CHILD INCOME EXCLUSION (#17) field is used by the Enrollment Application
 System.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM
  DATE ACTIVATED: MAY 02, 2018

NUMBER: 6015                            IA #: 6015
  FILE NUMBER: 392.2                    GLOBAL ROOT: DGBT(392.2
  DATE CREATED: AUG 23, 2013            CUSTODIAL PACKAGE: BENEFICIARY TRAVEL
  USAGE: Private                        TYPE: File
  NAME: READ ACCESS OF BENEFICIARY TRAVEL CERTIFICATION FILE
  ID: DGBT(392.2
GLOBAL REFERENCE: DGBT(392.2,'C'
 GLOBAL DESCRIPTION:   Routine EASBTBUL does not use the 'C' cross reference. 
 It calls $$FIND1 in routine DIC to find the IFN. S
 IFN=$$FIND1~DIC(392.2,"","MXQ",DFN, "","","ERR") 
GLOBAL REFERENCE: DGBT(392.2,D0,0
FIELD NUMBER: .01                       FIELD NAME: DATE CERTIFIED
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: ELIGIBLE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Enrollment and Eligibility (VistA REE) software
 needs access to the Beneficiary Travel Certification file in order to satisfy
 the requirements of the Veterans Financial Assessment (VFA) project.  
  
 NOTE:  ICR was entered in 2013 but never activated.  The BENEFICIARY TRAVEL
 CERTIFICATION (#392.2) file is accessed from SET+16 in routine EASBTBUL to use
 FileMAN API $$FIND1~DIC to get the IFN in file 392.2.  A comment at SET+15 in
 the routine states this file data does not exist.  SET+18 is a commented out
 line calling $$GET1~DIQ to retrieve the Date Certified field and compare it to
 the current date.  Active code is referencing the file and an ICR is needed. 
 On 4/13/18, the Status was changed from Pending to Deferred because the value
 retured by the DIC call is not used. If a future patch activates the line of
 code in SET+18~EASBTBUL, the ICR can be re-evaluated and activated if
 approved.  
  STATUS: Deferred (re)approval until a Release Occurs
  DURATION: Till Otherwise Agreed
KEYWORDS: DBGT
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM
 SUBSCRIBING DETAILS:   The Enrollment Application System (EAS) package needs
 access to the BENEFICIARY TRAVEL CERTIFICATION file (#392.2).  The 'C' cross
 reference will be accessed to obtain the data needed. The DATE CERTIFIED field 
 (#.01) and ELIGIBLE field (#3) will be needed to fulfill our requirements.  

NUMBER: 6016                            IA #: 6016
  DATE CREATED: AUG 27, 2013            CUSTODIAL PACKAGE: EVENT CAPTURE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ECUMRPC1
  NAME: DBIA6016-EVENT CAPTURE API-ECUMRPC1-SRCLST
  ID: ECUMRPC1
 GENERAL DESCRIPTION:   MHV Secure Messaging - Work Load Credit functionality
 allows users to save the workload credit using the assigned DSS units, and
 stores the record in Event Capture System.  The use of the DSS units is the
 same as in ECS, users have access to link their work to DSS units that send
 the record to PCE, as well as historical DSS units for historical workload
 credit forms that do not send the information to PCE.  To implement this 
 functionality, MHV SM reads files and calls existing APIs from Event Capture
 System.  
           
 EC routine SRCLST^ECUMRPC1 is used to retrieve diagnosis codes and description
 based on search criteria. This routine is also called via RPC [EC GETLIST].  
  STATUS: Active
COMPONENT/ENTRY POINT: SRCLST
 COMPONENT DESCRIPTION:   $$SRCLST^ECUMRPC1(RESULTS,ECARY) 
VARIABLES: ECFILE                       TYPE: Input
 VARIABLES DESCRIPTION:   Expressions File (#757.01) to Search.  First piece of
 ECARY.  
VARIABLES: ECSTR                        TYPE: Input
 VARIABLES DESCRIPTION:   Diagnosis Search String.  Second piece of ECARY.  The
 Diagnosis Search String is entered by the provider in the MHV SM front-end
 application while entering workload.  
VARIABLES: ECDIR                        TYPE: Input
 VARIABLES DESCRIPTION:   Search Order.  Third piece of ECARY.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   Array of values based on the Search criteria ICD
 Code^LEX Description^IEN of File #757.01 
SUBSCRIBING PACKAGE: MYHEALTHEVET
 SUBSCRIBING DETAILS:   Used by Secure Messaging in MHV.  
  DATE ACTIVATED: NOV 07, 2013

NUMBER: 6017                            IA #: 6017
  DATE CREATED: SEP 18, 2013
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWLEX
  NAME: ORWLEX GETI10DX                 REMOTE PROCEDURE: ORWLEX GETI10DX
  ID: ORWLEX
 GENERAL DESCRIPTION:   This agreement is between CPRS and Group Notes.  
  
 Group Notes would like to utilize the new RPC, ORWLEX GETI10DX,that is 
 introduced with the ICD-10 project initiative of CPRS GUI v30.  
  
 This RPC returns a list of Lexicon expressions for a treeview of ICD-10-CM
 categories/codes. Two parameters are required to be passed in: the first is
 the array (passed by reference) in which the expressions will be returned and
 the second is the search term.  
  
 Input Parameters:  .ARRAY    This is the local output array passed by 
                              reference. (Required) 
  
                    TEXT      Text or Code to search for.  (Required) 
  
                    DATE      The date for which the search is applicable 
                              for, which usually corresponds to the 
                              encounter date. If not passed, TODAY's date 
                              will be used.  (Optional) 
  
 Output Parameters: ARRAY     Output Array passed by reference containing 
                              the ICD-10 expressions and codes found: 
                             
                              ARRAY(#)=Lexicon Expression IEN^Preferred 
                                       Text^ICD Coding System^ICD 
                                       Diagnosis Code^^^^^ICD Diagnosis 
                                       IEN 
                             
                              If ICD-10 categories are found, then the 
                              parent node is returned in the following 
                              format: 
                             
                              ARRAY(#)=+^Preferred Text^ICD Coding System 
                                       ^ICD Diagnosis Code^^^^^-1 
                             
                              where each # is a sequence number per 
                              expression to group the data elements.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORWLEX
KEYWORDS: GETI10DX
COMPONENT/ENTRY POINT: GETI10DX(.ARRAY,TEXT,DATE)
 COMPONENT DESCRIPTION:   This RPC is a wrapper to the Lexicon API
 $$DIAGSRCH^LEX10CS and returns a list of Lexicon expressions for a treeview of
 ICD-10-CM categories/codes. Two parameters are required to be passed in: the
 first is the array (passed by reference) in which the expressions will be
 returned and the second is the search term.  
VARIABLES: .ARRAY                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the local output array passed by reference.
 (Required) 
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   Text or Code to search for.  (Required) 
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   The date for which the search is applicable for,
 which usually corresponds to the encounter date. If not passed, TODAY's date
 will be used.  (Optional) 
VARIABLES: ARRAY                        TYPE: Output
 VARIABLES DESCRIPTION:   Output Array passed by reference containing the
 ICD-10 expressions and codes found: 
  
   ARRAY(#)=Lexicon Expression IEN^Preferred 
            Text^ICD Coding System^ICD 
            Diagnosis Code^^^^^ICD Diagnosis IEN 
  
 If ICD-10 categories are found, then the parent node is returned in the 
 following format: 
  
   ARRAY(#)=+^Preferred Text^ICD Coding System^ICD 
            Diagnosis Code^^^^^-1 
  
 where each # is a sequence number per expression to group the data elements.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Group Notes, a subcomponent of CPRS Notes tab, is the
 actual subscriber.This ICR is effective with release of OR*3*385 (CPRS GUI 
 v30.A).  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   10/30/17-HMP's subscription to this ICR expires on
 10/27/17 when HMP will be shutdown.  HMP*2.0*12 released on 10/17/17 is an
 informational patch outlining the steps for the sites to shut down the
 application.  
  
 CPRS disapproved access to the ORWPCE LEX RPC on 11/3/16 recommending HMP look
 at the ORWLEX GETI10DX RPC.  HMP's request for subscription to ICR #6017 was
 not finalized before HMP was shut down on 10/27/17.  Both ORWPCE LEX and
 ORWLEX GETI10DX RPCs are included in the HMP UI Context option.  It is not
 known if one or both RPCs are used by HMP.  
  
 If HMP is reactivated in the future, the HMP project team should review ICR
 #6017 and ICR #3725 with the CPRS team to determine if one or both RPCs are
 needed by HMP.  
  DATE ACTIVATED: JUN 13, 2014

NUMBER: 6018                            IA #: 6018
  FILE NUMBER: 9999999.17               GLOBAL ROOT: DIC(9999999.17
  DATE CREATED: OCT 09, 2013            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: DESCRIPTION UPDATE FOR 9999999.17 FILE
  ID: DIC(9999999.17
 GENERAL DESCRIPTION:   Important Note: This is a One-Time Agreement, just for
 Patch PX*1.0*199.  
  
 Update of DESCRIPTION for File (#9999999.17) which is the TREATMENT File to
 replace occurrences of 'ICD-9-CM' to 'ICD-CM' to accommodate ICD-10 
 Remediation project for Patch PX*1.0*199.  DESCRIPTION will be updated using
 Pre-Init routine PX10P199.  
  
 Routine PX10P199 directly sets nodes in the File Description for File 
 (#9999999.17).  
  
 End result should be as below: 
  
 ^DIC(9999999.17,"%D",2,0)="of treatments that are not covered in the ICD-CM
 Procedures or the CPT" 
  
 ^DIC(9999999.17,"%D",8,0)="the lack of a coded CPT or ICD-CM." 
  STATUS: Retired
KEYWORDS: DESCRIPTION
KEYWORDS: ICD
KEYWORDS: DIAGNOSIS
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER

NUMBER: 6019                            IA #: 6019
  FILE NUMBER: 9000010.07               GLOBAL ROOT: DIC(9000010.07
  DATE CREATED: OCT 10, 2013            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: DESCRIPTION UPDATE FOR 9000010.07 FILE
  ID: DIC(9000010.07
 GENERAL DESCRIPTION:   Important Note: This is a One-Time Agreement, just for
 Patch PX*1.0*199.  
  
 Update of DESCRIPTION for File (#9000010.07) which is the V POV File to 
 replace occurrence of 'ICD9' to 'ICD' to acommodate ICD-10 Remediation project
 for Patch PX*1.0*199.  DESCRIPTION will be updated using Pre-Init routine
 PX10P199.  
  
 Routine PX10P199 directly sets node in the File Description for File 
 (#9000010.07).  
  
 End result should be as below: 
  
 ^DIC(9000010.07,"%D",24,0)="appropriate ICD diagnosis code. Physician entered
 narrative which modifies" 
  STATUS: Retired
KEYWORDS: DESCRIPTION
KEYWORDS: ICD
KEYWORDS: DIAGNOSIS
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER

NUMBER: 6020                            IA #: 6020
  DATE CREATED: OCT 10, 2013            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: DESCRIPTION UPDATE FOR ACR INDEX OF 9000010.07 FILE
 GENERAL DESCRIPTION:   Important Note: This is a One-Time Agreement, just for
 Patch PX*1.0*199.  
  
 Update of DESCRIPTION for ACR Index of File (#9000010.07) which is the V POV
 File to replace occurrences of 'ICD9' to 'diagnosis' and 'ICD9 CODE' to 'ICD
 IEN' to accommodate ICD-10 Remediation project for Patch PX*1.0*199. 
 DESCRIPTION for ACR Index will be updated using Pre-Init routine PX*1.0*199.  
  
 Routine PX10P199 directly sets nodes in the File Description for the ACR Index
 for File (#9000010.07).  
  
 ACR Index # should be retrieved by looping through those that are under 
 ^DD("IX","IX","ACR") then looking at uparrow piece 1 of ^DD("IX",<ACR Index
 #>,0) node for each and, if it equals 9000010.07, then the end result should
 be as below: 
  STATUS: Pending
KEYWORDS: DESCRIPTION
KEYWORDS: INDEX
KEYWORDS: ACR
KEYWORDS: ICD
KEYWORDS: DIAGNOSIS

NUMBER: 6021                            IA #: 6021
  FILE NUMBER: 9000010.07               GLOBAL ROOT: DIC(9000010.07
  DATE CREATED: OCT 10, 2013            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: ACR INDEX DESCRIPTION UPDATE FOR 9000010.07 FILE
  ID: DIC(9000010.07
 GENERAL DESCRIPTION:   Important Note: This is a One-Time Agreement, just for
 Patch PX*1.0*199.  
  
 Update of DESCRIPTION for ACR Index of File (#9000010.07) which is the V POV
 File to replace occurrences of 'ICD9' to 'diagnosis' and 'ICD9 CODE' to 'ICD
 IEN' to accommodate ICD-10 Remediation project for Patch PX*1.0*199. 
 DESCRIPTION for ACR Index will be updated using Pre-Init routine PX*1.0*199.  
  
 Routine PX10P199 directly sets nodes in the File Description for the ACR Index
 for File (#9000010.07).  
  
 ACR Index # should be retrieved by looping through those that are under 
 ^DD("IX","IX","ACR") then looking at uparrow piece 1 of ^DD("IX",<ACR Index
 #>,0) node for each and, if it equals 9000010.07, then the end result should
 be as below: 
  
 ^DD("IX",<ACR Index #>,.1,2,0)="all patients with a particular diagnosis code
 and one for finding all" 
  
 ^DD("IX",<ACR Index #>,.1,3,0)="the diagnosis codes a patient has." 
  
 ^DD("IX",<ACR Index #>,.1,5,0)=" ^PXRMINDX(9000010.07,""IPP"",ICD 
 IEN,PS,DSN,VISIT DATE,DAS) and" 
  
 ^DD("IX",<ACR Index #>,.1,6,0)=" ^PXRMINDX(9000010.07,""PPI"",DFN,PS,ICD 
 IEN,VISIT DATE,DAS)" 
  STATUS: Pending
KEYWORDS: DESCRIPTION
KEYWORDS: ACR
KEYWORDS: INDEX
KEYWORDS: ICD
KEYWORDS: DIAGNOSIS
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER

NUMBER: 6022                            IA #: 6022
  DATE CREATED: JAN 15, 2014
  CUSTODIAL PACKAGE: VIRTUAL PATIENT RECORD
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VPR GET PATIENT DATA
  REMOTE PROCEDURE: VPR GET PATIENT DATA
 GENERAL DESCRIPTION:   VPR GET PATIENT DATA is an rpc that pulls patient data
 from VistA and returns it in an array formatted as XML. Please see the VPR
 Technical Manual for details about input parameters and output data elements.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   The NHIN package is a subscriber to this ICR and the
 NHIN package name is also used to represent VLER DAS/Retail Pharmacy
 Immunization Data Retention Project.  This project receives Walgreens
 immunization data, which is being passed to PCE, creating a historical Visit
 and V Immunization entry. If a VLER DAS package is created in the future, VLER 
 DAS could be added as a subscriber.  
  
 This RPC replaced the NHIN RPC, NHIN GET VISTA DATA in PX*1*200.  
SUBSCRIBING PACKAGE: MEDICAL DOMAN WEB SERVICE
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA is added as subscriber because VIA is replacing
 MDWS use of this RPC.  VIA will use VistALink to process the RPC.  
SUBSCRIBING PACKAGE: HEALTH DATA REPOSITORY
 SUBSCRIBING DETAILS:   The Health Data Repository (HDR) release will be
 Increment 14 HDR v3.9 
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
SUBSCRIBING PACKAGE: LIGHTHOUSE
 SUBSCRIBING DETAILS:   Added 1/22/21 to collect patient data directly from
 VistA to support the Covid Patient Manager (CPM) SMART ON FHIR app that VA is
 currently building.  
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 6/9/23. CDSP is developing a CPRS COM extension
 to capture user generated events to trigger clinical decision support
 applications. CDSP is utilizing solutions based on FHIR, SMART on FHIR and CDS
 Hooks standards. CDSP needs to get patient data to enrich CPRS events and send 
 them to Clinical Decision Support services.  
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/23/23, effective with CRMS*1*0, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace.
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes 
 required RPCs. VPR GET PATIENT DATA is one of the Remote Procedures included
 in the CRMS VAHC Option. The Remote Application uses Data Access 
 Services/National Health Information Network (DAS/NHIN) as the middleware to
 interface with VistA.  
  
 Added 10/9/24, effective with CRMS*1*1, the Veterans Crisis Line (VCL) 
 Medoraforce application is a Salesforce product sharing the CRMS namespace.
 The CRMS VCL MDFC Remote Application includes the CRMS VCL MDFC Option, which
 includes all required Remote Procedures to support the VCL Medoraforce
 application. RPCs. The Remote Application uses Data Access Services/National
 Health Information Network (DAS/NHIN)as the middleware to interface with
 VistA. 
  DATE ACTIVATED: MAR 21, 2014

NUMBER: 6023                            IA #: 6023
  DATE CREATED: JAN 17, 2014
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PX SAVE DATA
  REMOTE PROCEDURE: PX SAVE DATA
 GENERAL DESCRIPTION:   The purpose of this RPC is to allow the calling
 application to save data to PCE.  
  
  Revision History: 
  ----------------
 Added 8/8/24, effective with the ENHANCED PCE ENCOUNTER LOOKUP 1.0 
 multi-Package, PX*1.0*238, TIU*1.0*362 and OR*3.0*606 the sequence of calls to
 add PCE data using PX SAVE DATA, should be: 
     1) call PX SAVE DATA, then 
     2) call TIU CREATE NOTE.  This will ensure the PKGNAME and SRC fields
 populate the Visit and PCE data and this supports reporting PCE results based
 on the PKGNAME or SRC fields. ICR 7315 is preferred as it returns error
 information.  
  
 Added 8/1/24, effective with PX*1*217, note the explanation of INPUT 
 PARAMETERS for PKGNAME and SRC and RETURN PARAMETERs expanded return values.  
  
  
  
 INPUT PARAMETER: PCELIST                PARAMETER TYPE: LIST 
   MAXIMUM DATA LENGTH: 10000            REQUIRED: YES 
   SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  PCELIST (n)=HDR^Encounter Inpatient?^Note has CPT codes?^Visit 
               string [Encounter location; Encounter date/time; Encounter 
               Service category]  (REQUIRED) 
          (n)=VST^DT^Encounter date/time 
          (n)=VST^PT^Encounter patient (DFN) (n)=VST^HL^Encounter location 
          (n)=VST^VC^ Encounter Service Category 
   
          If  applicable: 
                
          (n)=VST^PR^ Parent for secondary visit 
          (n)=VST^OL^ Outside Location for Historical visits 
          (n)=VST^SC^ Service Connected related? 
          (n)=VST^AO^ Agent Orange related? 
          (n)=VST^IR^ Ionizing Radiation related? 
          (n)=VST^EC^ Environmental Contaminates related? 
          (n)=VST^MST^ Military Sexual Trauma related? 
          (n)=VST^HNC^ Head and/or Neck Cancer related? 
          (n)=VST^CV^ Combat Vet related? 
          (n)=VST^SHD^ Shipboard Hazard and Defense related? 
          (n)=PRV(+:  add, -: delete) ^ Provider IEN ^^^ Provider Name ^ 
              Primary Provider? 
          (n)=POV(+:  add, -: delete) ^ ICD diagnosis code ^ Category  ^ 
              Narrative (Diagnosis description) ^ Primary Diagnosis? ^ 
              Provider String ^ Add to Problem List? ^^^ Next comment 
              sequence # if saving comments 
          (n)=COM^COM (Comments) ^ Next comment sequence # ^ @ = no 
              comments added 
          (n)=CPT (+:  add, -: delete) ^ Procedural  CPT code ^ Category ^ 
              Narrative (Procedure description) ^ Quantity ^ Provider IEN 
              ^^^ [# of modifiers;  Modifier code/Modifier IEN ^ Next 
              comment sequence # ^ 
  
          Effective with PX*1*209, the PCELIST input parameter contains 
          modifications for IMM (Immunization) type data to include 
          additional fields:  Encounter Provider, Event Info Source, 
          Dosage, Route, Admin Site, Lot #, Manufacturer, Expiration Date.  
          The IMM PCELIST items are not required to have the new fields - 
          to support backward compatibility.  
  
          (n)=IMM (+:  add, -: delete) ^ Immunization IEN ^ Category ^ 
              Narrative (Immunization description/name) ^ Series ^ 
              Encounter Provider ^ Reaction ^ Contraindicated? ^^ Next 
              comment sequence # ^ CVX Code ^ Event Info Source HL7 
              Code;IEN ^ Dose;Units;Units IEN ^ Route Name;HL7 Code;IEN ^ 
              Admin Site Name;HL7 Code;IEN^ Lot #;IEN ^ Manufacturer ^ 
              Expiration Date ^ Event Date and Time ^ Ordering Provider ^ 
              VIS1 IEN/VIS1 Date;VISn IEN/VISn Date;...^ Remarks Start Seq 
              #;End Seq # ^ Warning Ack ^ Override Reason (Seq #) 
  
          (n)=SK (+:  add, -: delete) ^ Skin Test IEN ^ Category ^ 
              Narrative (Skin Test description/name) ^ Results ^ Enc 
              Provider ^ Reading ^ D/T Read ^ Event D/T ^ Next comment 
              sequence # ^ Reader ^ Ordering Provider ^ Anatomic Location 
              of Placement;HL7 Code;IEN ^ Reading Comment (Seq #) 
          (n)=PED (+:  add, -: delete) ^ Patient Education IEN ^ Category ^ 
              Narrative (Patient Education description/name) ^ Level of 
              understanding ^^^^^ Next comment sequence # 
          (n)=HF (+:  add, -: delete) ^ Health Factor IEN ^ Category ^ 
              Narrative (Health Factor description/name) ^ Level ^^^^^ Next 
              comment sequence # ^ Get Reminder 
          (n)=XAM(+:  add, -: delete) ^ Exam IEN ^ Category ^ Narrative 
              (Exam description/name) ^ Results ^^^^^ Next comment sequence 
              #
          (n)=ICR (+:  add, -: delete) ^ Variable Pointer IMM 
              Contraindication Reasons/IMM Refusal Reasons ^ Category ^ 
              Narrative ^ Immunization IEN ^ Warn Until Date ^ Event 
              Date/Time ^ Enc Provider IEN ^ ^ Next comment sequence # 
  
 INPUT PARAMETER: LOC                    PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 40               REQUIRED: NO 
   SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  This is the hospital location. This is not used when the information is 
  from an outside source.  
  
 INPUT PARAMETER: PKGNAME                PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 60               REQUIRED: YES 
   SEQUENCE NUMBER: 3 
  DESCRIPTION:   
  The package name that is sending the data to PCE. This should be the 
  full package name from the PACKAGE file or a pointer to the PACKAGE file 
 (#9.4). If Middleware is involved, the Middleware package name should be the
 PKGNAME. If the calling product has a PACKAGE file entry and is not 
 middleware, then the product's PACKAGE file name should be the PKGNAME. For
 CPRS PCE updates, the PKGNAME is PATIENT CARE ENCOUNTERS, but that should not
 be used generically for any product.  
  
   Note:The Package Name field will only be updated in the PCE Visit and 
 V-files when PX SAVE DATA is called before TIU CREATE NOTE by the 
 application/middleware.  
  
 INPUT PARAMETER: SRC                    PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 64               REQUIRED: YES 
   SEQUENCE NUMBER: 4 
  DESCRIPTION:   
  The source of the data being sent to PCE. If the source is an application
 using middleware, the SRC should be the name of that application.  This
 applies to COTS, Class 3, Class 2, and Class 1 applications. SRC can be text
 or a pointer to the PCE DATA SOURCE file (#839.7). The text does not need to
 be pre-defined in the PCE DATA SOURCE file because it will be added using
 LAYGO for new data sources.  
  
   Note: The Data Source will only be updated in the PCE Visit and V-files when
 PX SAVE DATA is called before TIU CREATE NOTE by the application/middleware.  
  
  
 RETURN PARAMETER DESCRIPTION:   Returned Value: 
    1  If no errors occurred and data was processed.  
   -1  If errors occurred, but data was processed as completely as 
       possible.  
   -2  Unable to identify a valid Visit. No data was processed.  
   -3  RPC was called incorrectly. No data was processed.  
   -4  If cannot get a lock on the encounter.  
   -5  If there were only warnings.  
   
  Optionally, if the argument RETVISIT was "1", than the Visit IEN will be 
  returned as the second piece (e.g., "1^65234").  
  STATUS: Active
KEYWORDS: IMMUNIZATION
SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK
 SUBSCRIBING DETAILS:   3/21/14: The NHIN package is being used as subscriber
 because there is currently no VLER DAS package.  Retail Pharmacy Immunization
 Data Retention Project, as part of VLER DAS, will be using the PX SAVE DATA
 RPC to store immunization data (historical Visit and V Immunization entry) 
 from non-VA pharmacies in PCE. Note - if VLER DAS is given a separate package,
 then the subscribing package will need to be updated.  
  
 This RPC was linked to the NHIN APPLICATION PROXY option in PX*1*200.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Effective with HMP*2.0*2 
  
 HMP's subscription to this ICR was retired as of 10/27/17 when HMP was shut
 down.  HMP*2.0*12 released on 10/17/17 is an informational patch outlining the
 steps for the sites to shut down the application.  
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before HMP
 subscription to this ICR is reactivated.  See VistA Document Library for list
 of retired HMP ICRs.  
  DATE ACTIVATED: SEP 19, 2016

NUMBER: 6024                            IA #: 6024
  DATE CREATED: JAN 31, 2014
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA6024
  STATUS: Pending

NUMBER: 6025                            IA #: 6025
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: FEB 12, 2014            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: PATIENT APPOINTMENT MULTIPLE    ID: DPT(
GLOBAL REFERENCE: DPT(DFN,'S',IEN
FIELD NUMBER: .01                       FIELD NAME: CLINIC
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 3                         FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 9                         FIELD NAME: PURPOSE OF VISIT
  LOCATION: 0;7                         ACCESS: Write w/Fileman
FIELD NUMBER: 9.5                       FIELD NAME: APPOINTMENT TYPE
  LOCATION: 0;16                        ACCESS: Write w/Fileman
FIELD NUMBER: 19                        FIELD NAME: DATA ENTRY CLERK
  LOCATION: 0;18                        ACCESS: Write w/Fileman
FIELD NUMBER: 16                        FIELD NAME: CANCELLATION REASON
  LOCATION: 0;15                        ACCESS: Write w/Fileman
FIELD NUMBER: 17                        FIELD NAME: CANCELLATION REMARKS
  LOCATION: R;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 15                        FIELD NAME: NO-SHOW/CANCEL DATE/TIME
  LOCATION: 0;14                        ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   This Integration Agreement gives the Surgery Quality
 and Workflow Manager (SQWM) module of VistA Surgery authority to add and
 modify appointments to the Patient file (#2) Appointment sub-file (#2.98).  
  
 Clinic appointments created in the SQWM COTS application transmitted are 
 transmitted to VistA through an HL7 interface. The SIU HL7 message types and
 associated events (S12, S14, and S15) contain segments that are used to pass
 the validated data elements to VistA and are added to Appointment multiple.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: SQWM
SUBSCRIBING PACKAGE: SURGERY

NUMBER: 6026                            IA #: 6026
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: FEB 12, 2014            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  NAME: HOSPITAL LOCATION CLINIC APPOINTMENTS
  ID: SC(
GLOBAL REFERENCE: SC(DA,'S',IEN
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 1                         FIELD NAME: LENGTH OF APP'T
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 7                         FIELD NAME: DATA ENTRY CLERK
  LOCATION: 0;6                         ACCESS: Write w/Fileman
FIELD NUMBER: 8                         FIELD NAME: DATE APPOINTMENT MADE
  LOCATION: 0;7                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   This agreement give the Surgery Quality and Workflow
 Manager (SQWM) module of the VistA Surgery package permission to add and
 update clinic appointments on the APPOINTMENT sub-file of the HOSPITAL
 LOCATION file (#44).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: SQWM
SUBSCRIBING PACKAGE: SURGERY

NUMBER: 6027                            IA #: 6027
  DATE CREATED: FEB 21, 2014            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SCMCWS1
  NAME: SCMC PCMM/R GET PRIMARY CARE DETAILS
  ID: SCMCWS1
 GENERAL DESCRIPTION:   This is a new API developed for PCMMR that will return
 details regarding the Patient Aligned Care Team (PACT) and other team
 assignments (Mental Health, Specialty, OEF/OIF/OND) for a patient. This
 information will be retrieved from PCMMR and displayed when a user clicks on
 the PCMM "button" on the CPRS header.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PCMM
KEYWORDS: PRIMARY CARE
KEYWORDS: PCMMR
COMPONENT/ENTRY POINT: PCDETAIL
 COMPONENT DESCRIPTION:   Retrieve PACT and other team assignments from PCMMR.  
VARIABLES: SCDISPLY                     TYPE: Both
 VARIABLES DESCRIPTION:   An array containing PACT and other team assignment
 information.  Passed by reference.  The reference is passed as an empty array,
 and populated with data retrieved from PCMMR.  
VARIABLES: SCDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   The CPRS RPC "ORWPT1 PCDETAIL" will call this API to
 retrieve PACT and other team assignments from PCMMR.  The information will be
 displayed in the Primary Care Details popup window in CPRS.  
  DATE ACTIVATED: JUN 16, 2014

NUMBER: 6028                            IA #: 6028
  DATE CREATED: FEB 24, 2014            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: BPSUTIL2
  NAME: BPSUTIL2                        ID: BPSUTIL2
 GENERAL DESCRIPTION:   Integrated Billing requires access to data and indices
 of the BPS LOG OF TRANSACTIONS file (#9002313.57). The data will be used to
 match payments to claims. The data will be gathered by calling
 CLMECME^BPSUTIL2.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TRANSACTION
KEYWORDS: LOG
KEYWORDS: ECME
KEYWORDS: BPS
KEYWORDS: 9002313.57
KEYWORDS: DOS
KEYWORDS: SUBMIT DATE
COMPONENT/ENTRY POINT: CLMECME
 COMPONENT DESCRIPTION:   Searches for specific ECME numbers in the "AEC" index
 of #9002313.57. If appropriate entries are found, the routine returns the
 latest Date of Service for the fill that is associated with the date of
 service provided with the payment data. This routine is used to find alternate
 dates of service when there is no match for the date that is provided with the 
 payment data.  
VARIABLES: ECME                         TYPE: Input
 VARIABLES DESCRIPTION:   The ECME number of the prescription for which a bill
 is sought.  
VARIABLES: RCDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   The date of service returned from the payer with the
 payment data.  
VARIABLES: CLMDOS                       TYPE: Output
 VARIABLES DESCRIPTION:   The alternate date of service returned based on claim
 data in 9002313.57. This date is the latest date of service for the fill that
 matches the payer-provided date of service.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: JUN 19, 2014

NUMBER: 6029                            IA #: 6029
  DATE CREATED: MAR 07, 2014            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMAPI
  NAME: RETURN REMINDER ORDER CHECK ITEMS
  ID: PXRMAPI
 GENERAL DESCRIPTION:   The Clinical Reminders package stores lists of items in
 the REMINDER ORDER CHECK ITEMS GROUP file (#801).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: REMINDER ORDER CHECK ITEMS
KEYWORDS: ORDER CHECK ITEMS LIST
COMPONENT/ENTRY POINT: ITEMLIST(RIEN,GNAME,LIST,SUB)
 COMPONENT DESCRIPTION:   This entry point returns the items stored in the
 specified field for the specified entry.  
VARIABLES: RIEN                         TYPE: Input
 VARIABLES DESCRIPTION:   Optional.  REMINDER ORDER CHECK RULES file (#801.1)
 internal entry number (IEN) associated with the entries that contain the
 desired list(s).  If this parameter is null, the GNAME parameter must contain
 a value.  
VARIABLES: GNAME                        TYPE: Input
 VARIABLES DESCRIPTION:   Optional.  Value of the GROUP NAME field (#.01) of
 the entry that contains the desired list(s). If this parameter is null, the
 RIEN parameter must contain a value.  
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Required.  String that specifies which item list to
 return.  Use "P" for pharmacy, "O" for orderable item, "I" for imaging, or "A"
 for all types.  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   Optional.  String specifying the name of the
 subscript in the ^TMP($J) global to return data and error messages in. 
 Defaults to "PXRMLIST".  All data is returned in internal format.        Data
 Format: ^TMP($J,SUB,"GROUP_NAME","LIST_TYPE",ITEM)="" Error Message Format:
 ^TMP($J,SUB,"ERROR")="ERROR_MESSAGE_TEXT" 
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
 SUBSCRIBING DETAILS:   Women's Health needs to know which medications are high
 risk of causing harm to either fetuses or new born infants so it can warn
 providers when they prescribe such a medication and the patient either wants
 to become pregnant, is pregnant or is lactating. It also needs to know which 
 medications are considered contraceptive or an imaging agent.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Outpatient Pharmacy needs to include the list of items
 in a REMINDER ORDER CHECK ITEMS GROUP entry when it displays the history of a
 Clinical Reminder order check.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Inpatient Medications needs to include the list of
 items in a REMINDER ORDER CHECK ITEMS GROUP entry when it displays the history
 of a Clinical Reminder order check.  
  DATE ACTIVATED: AUG 04, 2016

NUMBER: 6030                            IA #: 6030
  DATE CREATED: MAR 07, 2014            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPMUTL
  NAME: WARD AT DISCHARGE               ID: DGPMUTL
 GENERAL DESCRIPTION:   This agreement allows the AR application to get the
 ward at the time of discharge performed by PTF^DGPMUTL to determine the care
 type of VA care or Non-VA care for the bill.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PTF~DGPMUTL
VARIABLES: DGPTF                        TYPE: Input
 VARIABLES DESCRIPTION:   A PTF entry number (IFN in the PTF (#45) file) 
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   Ward name for ward at discharge 
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: APR 03, 2017

NUMBER: 6031                            IA #: 6031
  DATE CREATED: MAR 19, 2014            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: DGENA                        NAME: DBIA6031
  ID: DGENA
 GENERAL DESCRIPTION:   The Enrollment Application System (EAS) have a need to
 obtain enrollment data from Patient Enrollment File (#27.11).  This can be
 accomplished using the API in the Registration Enrollment routine DGENA.  
  
 Added piece 24, 25, 26, and 27 to variable Node New Pieces include Camp
 Lejeune Data 
        Camp Lejeune Indicator 
        CL Date/Time Stamp 
        CL Source 
        CL Site 
  
  
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: DGENA
KEYWORDS: DG*5.3*877
COMPONENT/ENTRY POINT: $$GET
 COMPONENT DESCRIPTION:   Obtains a record from file 27.11 and loads it into an
 array.  
  
VARIABLES: DGENR                        TYPE: Input
 VARIABLES DESCRIPTION:   Enrollment record array name.  
VARIABLES: DGENRIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   Returns a patient's current enrollment record
 (pointer to file 27.11) 
SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM
SUBSCRIBING PACKAGE: DENTAL
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS

NUMBER: 6032                            IA #: 6032
  FILE NUMBER: 801                      GLOBAL ROOT: PXD(801
  DATE CREATED: MAR 21, 2014            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: File
  NAME: PRE CLINICAL REMINDER ORDER CHECK
  ID: PXD(801
GLOBAL REFERENCE: PXD(801,DO,1.5,D1,0)
FIELD NUMBER: 15                        FIELD NAME: PHARMACY ITEM LIST
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This multiple stores a list of VA Generic, Va Drug Class
 and Drugs.  If the ordered orderable item belongs to one of the items in this
 multiple then the rules attached to the group will be evaluated.  
FIELD NUMBER: 20                        FIELD NAME: ORDERABLE ITEM LIST
  LOCATION: PXD(801,DO,2                ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This multiple contains a list of orderable items that
 each reminder rule should run against. As an order is placed in CPRS, the
 orderable item is passed to the order check mechanism. This orderable item
 will be checked against this list; if it is found, then the reminder
 definition or term assigned to the rule multiple will be evaluated against the
 orderable item.  
 GENERAL DESCRIPTION:   In order to display Clinical Reminders based on
 Orderable Items and Pharmacy Items, the Inpatient Meds and Outpatient Pharmacy 
 packages request read-only access to the following nodes in the REMINDER ORDER
 CHECK ITEMS GROUP FILE (^PXD(801): 
  
 ^PXD(801,D0,1.5,0)=^801.015V^^  (#15) PHARMACY ITEM LIST 
 ^PXD(801,D0,1.5,D1,0)= (#.01) PHARMACY ITEM [1V] ^ ^PXD(801,D0,2,0)=^801.02P^^ 
 (#20) ORDERABLE ITEM LIST         ^PXD(801,D0,2,D1,0)= (#.01) ORDERABLE ITEM
 [1P:101.43] ^ 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS

NUMBER: 6033                            IA #: 6033
  FILE NUMBER: 362.4                    GLOBAL ROOT: IBA(362.4,
  DATE CREATED: MAR 25, 2014            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: IB BILL/CLAIMS PRESCRIPTION REFILL FILE ACCESS
  ID: IBA(362.4,
GLOBAL REFERENCE: IBA(362.4,D0,0)
FIELD NUMBER: .01                       FIELD NAME: RX #
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: BILL NUMBER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: DRUG
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DATE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: RECORD
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: DAYS SUPPLY
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: QTY
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: NDC #
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: FORMAT OF NDC#
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1                        FIELD NAME: FILL NUMBER
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .11                       FIELD NAME: ORDER DATE
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   As part of the implementation of PRCA*4.5*298, the
 Accounts Receivable package is requesting read access to the BILL NUMBER (C)
 cross-reference and the zero node of IB BILL/CLAIMS PRESCRIPTION REFILL file
 (362.4).  
  
  STATUS: Active
KEYWORDS: EPAYMENTS
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: JUN 12, 2014

NUMBER: 6034                            IA #: 6034
  FILE NUMBER: 52                       GLOBAL ROOT: DD(52
  DATE CREATED: MAR 26, 2014            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: Editing Label Date/Time multiple HELP-PROMPT (file #52)
  ID: DD(52
 GENERAL DESCRIPTION:   This request is to allow the Outpatient Pharmacy 
 package to remove the HELP-PROMPT for multiple field Label Date/Time (#32) of
 the Prescription file (#52).  
  
 This change will be used in patch PSO*7.0*370 only.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: Label Date
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 6035                            IA #: 6035
  DATE CREATED: MAR 31, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWPT16 ID INFO
  REMOTE PROCEDURE: ORWPT16 ID INFO
 GENERAL DESCRIPTION:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
      
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
  STATUS: Active
KEYWORDS: ORWPT16
KEYWORDS: ID INFO
KEYWORDS: ORWPT16 ID INFO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*1 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink.  
  DATE ACTIVATED: MAR 31, 2014

NUMBER: 6036                            IA #: 6036
  DATE CREATED: APR 02, 2014            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  ROUTINE: PSOUT433                     NAME: National Utility Clean-up
  ID: PSOUT433
 GENERAL DESCRIPTION:   This agreement describes the call made from
 Computerized Patient Record System (CPRS) to Outpatient Pharmacy as part of a
 combined build that contains patches OR*3.0*378 and PSO*7.0*433.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN(PSOCWORD,PSOCWPFL,PSOCWDRY,PSOCWDSQ,PSOCWTXT)
 COMPONENT DESCRIPTION:   This is the entry point CPRS calls to indicate to
 Outpatient Pharmacy that the order that CPRS has cleaned up has a
 corresponding Prescription or Pending Order that needs to be checked for
 possible clean-up.  
VARIABLES: PSOCWORD                     TYPE: Input
 VARIABLES DESCRIPTION:   This is a 2 piece variable, with the ";" character as
 the separator. Piece 1 is the CPRS order number from the ORDERS (#100) File.
 Piece 2 is either a "P" to indicate the PRESCRIPTION (#52) File, or an "S" to 
 indicate PENDING OUTPATIENT ORDERS (#52.41) File.  
VARIABLES: PSOCWPFL                     TYPE: Input
 VARIABLES DESCRIPTION:   This parameter is used only for pending orders. If 0,
 that indicates that if a Drug Name was removed from the dosage to not show the
 removed drug name on the Pending screen when the Pending order is displayed
 for finishing, and if 1 show the drug name on the Pending order screen.  
VARIABLES: PSOCWDRY                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the Dry run flag. If 1, then no file changes
 are made in Pharmacy, but all the data that is returned if the data was
 changed is returned to CPRS for reporting purposes. If 0, then the Pharmacy
 file changes are to occur.  
VARIABLES: PSOCWDSQ                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the array of dosing sequences that are to be
 cleaned up. For example, if PSOCWDSQ(1) and PSOCWDSQ(3) are defined, then
 Pharmacy needs to check dosing sequence 1 and dosing sequence 3 for potential
 clean up.  
VARIABLES: PSOCWTXT                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the array name that the return data will be
 set into.  
VARIABLES: PSOCWTXT                     TYPE: Output
 VARIABLES DESCRIPTION:   This is the Output returned to CPRS.  
  
 For prescriptions: 
  
 If there is an error of some sort, the reason is returned in the "ERR" array
 node. For example: PSOCWTXT("ERR")=No Dispense Drug found. Clean-Up could not
 be performed.  
           
 If there is data to clean up, the following is returned: 
 PSOCWTXT("PHARM")=Prescription number^Issue Date (VA FileMan format)^Status
 (In external format) PSOCWTXT("PHARM","DISP")=Drug Name^Internal Entry number
 of Drug Note: For a prescription, there should always be a DRUG (#50) File
 Entry with the prescription, which is what the "DISP" values contain. Just in 
 case there is no DRUG (#50) File entry, the "DISP" values will be from the 
 PHARMACY ORDERABLE ITEM (#50.7) File.  PSOCWTXT("PHARM","DOSE",#)=Old
 Dosage^New Dosage Note" The '#' subscript in the array represents the dosing
 sequence.  PSOCWTXT("PHARM","SIG")=Old Sig^New Sig 
  
 If there are no errors and there is nothing to clean-up, then nothing is 
 returned.  
  
  
 For Pending orders: 
  
 If there is an error of some sort, the reason is returned in the "ERR" array
 node. For example: PSOCWTXT("ERR")=Pharmacy record not found 
  
 If there is data to clean up the following is returned: 
 PSOCWTXT("PHARM")=P12345^Effective Date (VA FileMan Format)^PENDING Note:
 Piece 1 is the letter P followed by the Internal Entry Number from the PENDING
 OUTPATIENT ORDERS (#52.41) File.  PSOCWTXT("PHARM","DISP")=Drug Name^Internal
 Entry number of Drug Note: If there is a DRUG (#50) File Entry with the
 Pending Order, that is what the "DISP" values contain. If there is no DRUG
 (#50) File entry, the "DISP" values are from the PHARMACY ORDERABLE ITEM
 (#50.7) File.  PSOCWTXT("PHARM","DOSE",#)=Old Dosage^New Dosage Note: The '#'
 subscript in the array represents the dosing sequence.  
 PSOCWTXT("PHARM","SIG")=Old Sig^New Sig 
  
 If there are no errors and there is nothing to clean-up, then nothing is 
 returned.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   CPRS will pass an order number to Outpatient Pharmacy.
 CPRS has determined this order to have invalid data in the Dosage Field(s),
 and the order should have the invalid data removed and the Sig rebuilt.  

NUMBER: 6037                            IA #: 6037
  FILE NUMBER: 405                      GLOBAL ROOT: DGPM(
  DATE CREATED: APR 10, 2014            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: DGPM C CROSS REFERENCE          ID: DGPM(
GLOBAL REFERENCE: DGPM(D0,0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0:1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The MBAA RPC, MBAA PATIENT ADMISSIONS uses routine
 MBAAMEXT reads the DGPM("C" cross reference to see if a patient has a
 movement. If a movement is found, the record number for the movement is used
 to access the record and get the Date/Time (.01) field. 
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE

NUMBER: 6038                            IA #: 6038
  DATE CREATED: APR 11, 2014            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSBVPR
  NAME: BCMA ADMINISTRATION DATA        ID: PSBVPR
 GENERAL DESCRIPTION:   The purpose of this Application Programming Interface
 (API) is to provide the next scheduled administration information.  
  
 The 4th  parameter passed into this API is optional, which is the date and
 time.  If not passed in, then the API defaults to date/time = NOW, and will
 return the next admin time that follows NOW.    So, if an admin time was due 1
 minute ago, then that admin will not be returned, as the Next admin dose. 
 However, that admin of 1 minute ago, is most likely the admin that nursing
 staff would actually give to the patient via BCMA.  
  STATUS: Active
KEYWORDS: PSBVPR
KEYWORDS: ADMINISTRATION
COMPONENT/ENTRY POINT: ADMIN
VARIABLES: RESULTS                      TYPE: Both
 VARIABLES DESCRIPTION:   This is the variable that will contain the return of
 the next scheduled administration. If none is available, the return will be
 null. Should be passed by reference.  
VARIABLES: PSBVDFN                      TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN. (Required) 
VARIABLES: PSBORDNO                     TYPE: Input
 VARIABLES DESCRIPTION:   Inpatient Medications order number, in the format of
 number followed by the 'type'. For example: 20U for a unit dose order number
 20. 15V for infusion order number 15. (Required) 
VARIABLES: PSBVADT                      TYPE: Input
 VARIABLES DESCRIPTION:   This parameter is optional, this is the date and time
 to start the search.  If not passed in, then the API defaults to date/time =
 NOW, and will return the next admin time that follows NOW.    So, if an admin
 time was due 1minute ago, then that admin will not be returned, as the Next
 admin dose.  However, that admin of 1 minute ago, is most likely the admin
 that nursing staff would actually give to the patient via BCMA.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP routine HMPDJ05V calls the ADMIN^PSBVPR API to
 retrieve the next scheduled administration information for a patient.  
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: MAY 10, 2016

NUMBER: 6039                            IA #: 6039
  DATE CREATED: APR 14, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXA OFCPLX
  REMOTE PROCEDURE: ORWDXA OFCPLX
 GENERAL DESCRIPTION:   This ICR was created for VIA. The RPC was used by MDWS,
 and never previously documented in an ICR.  Since MDWS already uses this RPC,
 and VIA is responsible for exposing all RPCs used by MDWS, the CPRS 
 development team agrees to the use of the RPC. 
     
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
  
 This RPC is used to evaluate a true/false value to: is ORID child of PRTORDER. 
 
  STATUS: Active
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
      
 The OR*3*392 patch is associated with the VIAB*1*1 patch.  
  DATE ACTIVATED: APR 21, 2014

NUMBER: 6040                            IA #: 6040
  DATE CREATED: APR 14, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWLRR INFO
  REMOTE PROCEDURE: ORWLRR INFO
 GENERAL DESCRIPTION:   This ICR was created for VIA. The RPC was used by MDWS,
 and never previously documented in an ICR.  Since MDWS already uses this RPC,
 and VIA is responsible for exposing all RPCs used by MDWS, the CPRS 
 development team agrees to the use of the RPC. 
     
 A new OR*3*392 patch will be distributed that turns on this RPC's flag - APP
 PROXY ENABLED. The OR*3*392 patch is associated with the VIAB*1*1 patch.  
  
 This RPC is used to return lab test description information.  
  STATUS: Active
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This ICR is created to satisfy the needs of the VIA
 project which is tasked to replace MDWS services, where MDWS was referencing
 this RPC without an approved ICR.  
      
 The OR*3*392 patch is associated with the VIAB*1*1 patch.  
  DATE ACTIVATED: APR 21, 2014

NUMBER: 6041                            IA #: 6041
  FILE NUMBER: 74                       GLOBAL ROOT: RARPT(
  DATE CREATED: APR 15, 2014
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VERIFIED DATE/TIME OF RADIOLOGY REPORTS
  ID: RARPT(
GLOBAL REFERENCE: RARPT('AA'
 GLOBAL DESCRIPTION:   The 'AA' cross reference is used to index the date
 radiology reports were verified in an inverse date format. Once the inverse
 date format is known we can find the radiology report records by using the
 last subscript in the cross reference to identify the radiology report record. 
  
 Format: ^RARPT("AA",6859584.8686,12345) 
  
 '6859584.8686' is the inverse date.  
  
 '12345' is the record number in the RAD/NUC MED REPORTS (#74) file.  
GLOBAL REFERENCE: RARPT(
FIELD NUMBER: .01                       FIELD NAME: DAY-CASE#
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the date and case number of the
 imaging exam associated with this report. The system fills in this field with 
 information obtained from the 'RAD/NUC MED PATIENT' file (#70) according to
 the case number selected by the transcriptionist. If the Site Specific 
 Accession Number is in use then the 3-digit Site ID is appended to the 
 beginning of the field. 
FIELD NUMBER: 2                         FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains a pointer to the PATIENT (#2) file.
 The record in the PATIENT file contains the name of the rad/nuc med patient
 associated with a radiology report.  
FIELD NUMBER: 4                         FIELD NAME: CASE NUMBER
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the case number of the exam.  
FIELD NUMBER: 7                         FIELD NAME: VERIFIED DATE
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the date and the time that the report
 was verified by the interpreting physician.  
 GENERAL DESCRIPTION:   This Integration Agreement will allow the VistA
 Decision Support System (DSS) to identify verified reports over a date range.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RARPT
KEYWORDS: RA 'AA' CROSS REFERENCE
KEYWORDS: RA VERIFIED DATE/TIME REPORTS
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  DATE ACTIVATED: JUN 04, 2014

NUMBER: 6042                            IA #: 6042
  DATE CREATED: APR 15, 2014            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SCMCWSUT
  NAME: SCMC PCMM/R GET PRIMARY CARE SUMMARY
  ID: SCMCWSUT
 GENERAL DESCRIPTION:   This is a new API developed for PCMMR that will return
 Patient Aligned Care Team (PACT) summary data for a patient.  This information
 will include site name, PACT name, Primary Care Provider (PCP) and Associate 
 Provider (AP) names.  PCMMR will keep this data current.  It will be stored in
 the Outpatient Profile (404.41) file in the CPRS Header Text (.06) field.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PCMM
KEYWORDS: PCMMR
KEYWORDS: PRIMARY CARE
COMPONENT/ENTRY POINT: CPRSHEAD
 COMPONENT DESCRIPTION:   This is a function call to retrieve PACT summary data
 from PCMMR.  It returns a string of data to be displayed on line 1 of the CPRS
 PCMM header.  
VARIABLES: SCDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: Function Value               TYPE: Output
 VARIABLES DESCRIPTION:   Includes site name, PACT name, Primary Care Provider
 (PCP) and Associate Provider (AP) names.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   The CPRS RPC "ORWPT1 PRCARE" will call this API to
 retrieve PACT assignment summary data.  The data will be displayed on the
 first line of the CPRS PCMM header.  VistA will continue to be the source for 
 information in lines 2 (inpatient) and 3 (mental health) of the CPRS PCMM 
 header.  
  DATE ACTIVATED: JUN 16, 2014

NUMBER: 6043                            IA #: 6043
  FILE NUMBER: 15                       GLOBAL ROOT: VA(15
  DATE CREATED: APR 15, 2014            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ DUPLICATE RECORD FILE
  ID: VA(15
GLOBAL REFERENCE: VA(15,D0)
FIELD NUMBER: .01                       FIELD NAME: RECORD1
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: RECORD2
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: STATUS
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: MERGE DIRECTION
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: MERGE STATUS
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   PCMMR would like to reference fields in the following
 file directly: 
  
 DUPLICATE RECORD (#15) FILE 
  
 IEN, .01 RECORD1, .02 RECORD2, .03 STATUS, .04 MERGE DIRECTION, .05 MERGE
 STATUS 
  
 When PCMMR receives an ADT-A24 HL7 message from MPI indicating a merge of 
 identities that is a "local merge" on a single station, PCMMR needs to query
 the Duplicate Record file to determine whether VistA has completed the
 resolution of duplicate patients. If and only if the local VistA staff
 performing the Local Merges chooses to accept and process this local data
 merge, PCMMR will complete the data merge in its own enterprise database,
 enabling it to continue data synchronization with the VistA site. If VistA
 chooses to deny the merge request, or merge the patient data in the opposite
 direction, PCMMR can use the status in this file to adjust its behavior
 accordingly.  
  
 The code queries field .05 MERGE STATUS to find the status of the merge 
 process for each pair of duplicate records. If it finds value 3 - IN PROCESS,
 it starts polling VistA. It will poll VistA at increasing time interval until
 we exceed the maximum polling limit (currently 5 days from start of polling).
 If during polling it finds a value of 2 - MERGED, in a duplicate pair, the
 code processes the patient's data for the site and sends an application ack
 (acknowledgement) to MVI.  
  
 The file is accessed using a PCMMR restricted RPC "SCMC LISTER", which employs
 a Fileman DBS API to retrieve data from File 15.  It is deployed as part of
 patch SD*5.3*603.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MPI
KEYWORDS: MVI
KEYWORDS: PCMMR
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   See details below.  
  DATE ACTIVATED: JUL 09, 2014

NUMBER: 6044                            IA #: 6044
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: APR 22, 2014            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MBAA Access to SC files
  ID: SC(
GLOBAL REFERENCE: SC(D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0:1                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: STOP CODE NUMBER
  LOCATION: 0:7                         ACCESS: Read w/Fileman
FIELD NUMBER: 2503                      FIELD NAME: CREDIT STOP CODE
  LOCATION: 0:18                        ACCESS: Read w/Fileman
FIELD NUMBER: 9.5                       FIELD NAME: TREATING SPECIALTY
  LOCATION: 0:20                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: SC(D0,'ST',D1,1
FIELD NUMBER: 1                         FIELD NAME: CURRENT AVAILABILITY
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: SC(D0,'ST',D1,0
FIELD NUMBER: .01                       FIELD NAME: PATTERN DATE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: SC(D0,'PR',D1,0
FIELD NUMBER: .01                       FIELD NAME: PROVIDER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,'T',D1,0
FIELD NUMBER: .01                       FIELD NAME: AVAILABILITY
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,'SL'
FIELD NUMBER: 1914                      FIELD NAME: HOUR CLINIC DISPLAY BEGINES
  LOCATION: SL;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 1917                      FIELD NAME: DISPLAY INCREMENTS PER HOUR
  LOCATION: SL;6                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: SC(D0,'S',D1,1,D2,'CONS'
FIELD NUMBER: 688                       FIELD NAME: CONSULT LINK
  LOCATION: CONS;1                      ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: SC(D0,'S',D1,1,D2,0
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: LENGTH OF APPT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: XRAY
  LOCATION: 0;3                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: OTHER
  LOCATION: 0;4                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: WARD LOC
  LOCATION: 0;5                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: DATA ENTRY CLERK
  LOCATION: 0;6                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: DATE APPOINTMENT MADE
  LOCATION: 0;7                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 10
  FIELD NAME: PRIOR X-RAY RESULTS TO CLINIC
  LOCATION: 0;8                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 310                       FIELD NAME: APPOINTMENT CANCELLED
  LOCATION: 0;9                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 30                        FIELD NAME: ELIGIBILITY OF VISIT
  LOCATION: 0;10                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: SC(D0,'S',D1,1,D2,'OB'
FIELD NUMBER: 9                         FIELD NAME: OVERBOOK
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: SC(D0,'S',D1,1,D2,'C'
FIELD NUMBER: 309                       FIELD NAME: CHECKED-IN
  LOCATION: C;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 302                       FIELD NAME: CHECK IN USER
  LOCATION: C;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 303                       FIELD NAME: CHECKED OUT
  LOCATION: C;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 304                       FIELD NAME: CHECKED OUT USER
  LOCATION: C;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 306                       FIELD NAME: CHECK OUT ENTERED
  LOCATION: C;6                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: SC(D0,'S',D1,0
FIELD NUMBER: .01                       FIELD NAME: APPOINTMENT DATE/TIME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: SC('ARAD',D2,D1,DO
FIELD NUMBER: 10
  FIELD NAME: PRIOR X-RAY RESULTS TO CLINIC
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER:  
 GLOBAL DESCRIPTION:   When an appointment is cancelled, the "ARAD" cross
 reference is set equal to "N".  It was discovered routine SDCNP0 is checking
 to see if this cross reference is set to 'N'.  The SCV/VAR package sets this
 cross reference when an appointment is cancelled to be consistent with
 existing legacy Scheduling functionality.  
 GENERAL DESCRIPTION:   The Scheduling Calendar View (MBAA namespace) RPCs,
 MBAA APPOINTMENT MAKE, MBAA CANCEL APPOINTMENT, MBAA PATIENT PENDING APPT,
 MBAA GET CLINIC AVAILABILITY, and MBAA PROVIDER TO CLINIC and the routines
 below make reads and writes to the Hospital Location file (#44). The Routines
 and Linetags list below describe the access: 
  
 Routine: MBAAMDA1 reads and writes from/to the Hospital Location file (#44) in
 order to make and cancel appointments.  
   
 Linetags: 
  
 1. GETCLNX makes a FileMan read of the Hospital Location file (#44) to see if
 a clinic exists.  
  
 2. GETPATT does a FileMan read of the ^SC(D0,"ST" node to get the clinic 
 availability for a specified date.  
  
 3. GETSCAP does a direct global read of the ^SC(D0,"S" node to get clinic 
 appointment information for a specific patient and date/time.  
  
 4. GETCAPT does a FileMan read to get appointment data for a patient. Fields
 read are: Patient (.01), Length of Appointment (1), Other (3), Data Entry
 Clerk (7), Date Appointment Made (8), OverBook (9), Eligibility (30),
 Checked-in (309), Check in User (302), Checked Out (303), Check Out User
 (304), Check Out Entered (306), Consult Link (688) 
  
 5. LOCKST locks the ^SC(D0,"ST" node for a specified date prior to record for
 an appointment.  
  
 6. UNLCKST unlocks the ^SC(D0,"ST" node for a specified date after updating
 the record for an appointment.  
  
 7. LOCKS locks the ^SC(D0,"S" node for a specific date/time in order to enter
 a new appointment.  
  
 8. UNLCKS unlocks the ^SC(D0,"S", node for a specific date/time after an 
 appointment record has been created.  
  
 9. SETST uses FileMan to set the ^SC(D0,"ST",Date,1 node in order to set 
 appointment availability. This call updates fields .01, Pattern Date and 1
 Current Availability.  
  
 10. MAKE uses UPDATE^DIE to make a clinic appointment in the Hospital Location
 file (#44). The Appointment multiple is updated with a new appointment. Fields
 that are updated are .01, 1, 3, 7, 8, 10, 688.  
  
 The SC("ARAD" cross reference is being hardset in existing SD namespaced 
 routines. The SDCNP0 routine is hardsetting this cross reference to be equal
 to 'N'.  
  
  
 CANCEL updates the Hospital Location file (#44) when an appointment is 
 canceled: 
   
     a. The ^SC("ARAD" cross reference is hard set to "N". 
     b. The ^SC(D0,"S" node with the appointment record is deleted using 
        a  KILL command.  
     c. A FileMan read (GETS^DIQ) is used to get the values of the Hour 
        Clinic Display Begins (#1914) and Display Increments Per Hour 
        (#1917). These fields are used to calculate the value to be used 
        to update the Current Availability field in the Pattern multiple 
        (See d and e below).  
     d. The value of the ^SC(D0,"ST",Date,1 node is read with a 
        FileMan read. (Date is the date the appointment is being canceled).  
     e. The ^SC(D0,"ST",Date/Time,1 node is set using a FileMan write to 
        the newly calculated Current Availability as calculated when 
        canceling an appointment. Steps c, d and e are making the 
        calculations to reset the current availability pattern to recover 
        the slot that was used when making the appointment.  
  
 11. COVERB checks to see if the clinic is overbooked for a specific date/time.
 If so, the first overbooking is deleted using a KILL command.  
  
 12. GETFSTA gets the first available day for an appointment by reading the
 ^SC(D0,"T", node. 
  
 13. GETDAYA loops through the ^SC(D0,"S" nodes from a beginning date to get
 the appointment status and overbooking status for each date/time where an
 appointment is booked.  
  
 14. GETDST does a direct global read of the ^SC(D0,"ST",Date/Time, 1 node and
 returns the current availability status for the date/time.  
  
 15. GETDPATT returns the day pattern for a specific date. Does a direct global
 read of the ^SC(D0,"ST",date,D1,1) read and returns the data on this node.  
  
 16. ADDPATT uses UPDATE^DIE to update the PATTERN multiple for a specific 
 date.  
     
 Routine: MBAAMDA2 makes calls to read data from the Hospital Location file
 (#44) to get information in order to make or cancel appointments. 
    
 Linetags: SLOTS does a FileMan read of the ^SC(D0,"ST" node for a clinic to
 get the .01, Pattern Date and 1, Current Availability fields. Returns all
 nodes for the clinic in the RETURN array.  
     
 Routine MBAAMDA4 makes calls to read and update the Hospital Location file
 (#44) in order to make or cancel appointments.  
  
 Linetag: 
  
 1. UPDCAPT uses UPDATE^DIE to update the APPOINTMENT multiple for a new 
 appointment.  
  
 2. GETCAPT does a direct global read of the ^SC(D0,"S",Appointment Date/Time
 to check if the appointment exists. If it exists, uses an EN^DIQ call to read
 the appointment record. Fields that are read are Patient (.01), Length of
 Appointment (1), Other (3), Data Entry Clerk (7), Date Appointment Made (8),
 OverBook (9), Eligibility (30), Checked-in (309), Check in User (302), Checked
 Out (303), Check Out User (304), Check Out Entered (306) 
     
 Routine MBAARPC1 In linetag PROVCLIN a direct global read is made to the 
 ^SC(D0,"PR" to get the pointer to the NEW PERSON file (#200) for each Provider
 that is associated with the specified clinic.  
     
 Routine MBAARPC2 makes direct global reads of the HOSPITAL LOCATION file (#44)
 to read appointment information.  
  
 Linetag: 
  
 1. CLNDATA does a FileMan read of the ^SC(D0,0 node to get fields, STOP CODE
 NUMBER (8), TREATING SPECIALTY (9.5), CREDIT STOP CODE (2503). 
  
 2. RECALL does a FileMan  read to check to see if the Clinic ID entered exists
 in the Hospital Location file (#44).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  DATE ACTIVATED: MAR 23, 2015

NUMBER: 6045                            IA #: 6045
  FILE NUMBER: 403.5                    GLOBAL ROOT: SD(
  DATE CREATED: APR 22, 2014            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MBAA Access to SD(403.5
  ID: SD(
GLOBAL REFERENCE: SD(403.5,D0,0
FIELD NUMBER: .01                       FIELD NAME: PATIENT NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 4.5                       FIELD NAME: CLINIC
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ACCESSION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: TEST/APP.
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PROVIDER
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: RECALL DATE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 2.5                       FIELD NAME: COMMENT
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 2.6                       FIELD NAME: FAST/NON-FASTING
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 4.7                       FIELD NAME: LENGTH OF APPT.
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: DATE REMINDER SENT
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: USER WHO ENTERED RECALL
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 5.5                       FIELD NAME: RECALL DATE (PER PATIENT)
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: SECOND PRINT
  LOCATION: 0;13                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Scheduling Calendar View RPCs and code accesses the
 Recall Reminders file (#403.5) to read recall data. The RPCs are the MBAA
 RECALL BY FACILITY LIST and MBAA RECALL LIST BY PATIENT.  
  
 Routine MBAARPCL reads the Recall Reminders file (#403.5) to get the data 
 necessary to provide the facility Recall Reminders List and a Recall Reminders
 List by patient. 
  
 Linetags: 
  
 RECALL does a FileMan read of the ^SD(403.5 file to get fields Patient Name
 (.01), Clinic (4.5), Accession (2), Test/App (3), Provider (4), Recall Date
 (5), Comment (2.5), Fast/Non-Fasting (2.6), Length of Appt (4.7), Date
 Reminder Sent (6), User Who Entered Recall (7), Recall Date (Per Patient)
 (5.5), Second Print (8). 
  
 RCLDFN does a FileMan read of the ^SD(403.5 file to get fields Patient Name
 (.01), Clinic (4.5), Accession (2), Test/App (3), Provider (4), Recall Date
 (5), Comment (2.5), Fast/Non-Fasting (2.6), Length of Appt (4.7), Date
 Reminder Sent (6), User Who Entered Recall (7), Recall Date (Per Patient)
 (5.5), Second Print (8).  
  STATUS: Active
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  DATE ACTIVATED: JUN 10, 2016

NUMBER: 6046                            IA #: 6046
  FILE NUMBER: 409.3                    GLOBAL ROOT: SDWL(409.3
  DATE CREATED: APR 22, 2014            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MBAA ACESS TO SDWL(409.3
  ID: SDWL(409.3
GLOBAL REFERENCE: SDWL(409.3,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 23                        FIELD NAME: CURRENT STATUS
  LOCATION: 0;17                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ORIGINATING DATE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 22                        FIELD NAME: DESIRED DATE OF APPOINTMENT
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8                         FIELD NAME: WL SPECIFIC CLINIC
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: PRIORITY
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 27                        FIELD NAME: EWL ENROLLEE STATUS
  LOCATION: 0;20                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13                        FIELD NAME: SCHEDULED DATE OF APPT
  LOCATION: 0;23                        ACCESS: Write w/Fileman
FIELD NUMBER: 2                         FIELD NAME: INSTITUTION
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: WAIT LIST TYPE
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11                        FIELD NAME: REQUEST BY
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12                        FIELD NAME: PROVIDER
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 25                        FIELD NAME: COMMENTS
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 37
  FIELD NAME: CHANGED CLINIC PARENT POINTER
  LOCATION: 0;22                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: SDWL(409.3,D0,'SDAPT'
FIELD NUMBER: 13.1                      FIELD NAME: DATE APPT MADE
  LOCATION: 'SDAPT';1                   ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13.2                      FIELD NAME: APPT CLINIC
  LOCATION: 'SDAPT';2                   ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13.3                      FIELD NAME: APPT INSTITUTION
  LOCATION: 'SDAPT';3                   ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13.4                      FIELD NAME: APPT STOP CODE
  LOCATION: 'SDAPT';4                   ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13.5                      FIELD NAME: APPT CREDIT STOP CODE
  LOCATION: 'SDAPT';5                   ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13.6                      FIELD NAME: APPT STATION NUMBER
  LOCATION: 'SDAPT';6                   ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13.7                      FIELD NAME: APPT CLERK
  LOCATION: 'SDAPT';7                   ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13.8                      FIELD NAME: APPT STATUS
  LOCATION: 'SDAPT;8                    ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: SDWL(409.3,'SC'
FIELD NUMBER: 8                         FIELD NAME: WL SPECIFIC CLINIC
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SDWL(409.3,D0,'DIS'
FIELD NUMBER: 19                        FIELD NAME: DATE DISPOSITIONED
  LOCATION: DIS;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20                        FIELD NAME: DISPOSITIONED BY
  LOCATION: DIS;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21                        FIELD NAME: DISPOSITION
  LOCATION: DIS;3                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: SDWL(409.3,'B'
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SDWL(409.3,D0,1
FIELD NUMBER: 27.1                      FIELD NAME: EWL ENROLLEE DATE USED
  LOCATION: 1;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 27.2                      FIELD NAME: EWL ENROLLEE DATABASE FILE
  LOCATION: 1;4                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: SDWL(409.3,D0,'SC'
FIELD NUMBER: 14                        FIELD NAME: SERVICE CONNECTED PERCENTAGE
  LOCATION: SC;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 15                        FIELD NAME: SERVICE CONNECTED PRIORITY
  LOCATION: SC;2                        ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   The Scheduling Calendar View accesses the SD Wait List
 file (#409.3) to read and write data in order to provide information about
 patients on the Electronic Wait List (EWL) and to update the status of
 patients on the EWL in order to remove them from the EWL. The mobile app
 verifies the user holds the VistA security key, SDWL MENU prior to allowing
 access to the mobile wait list options.  
  
 Routine MBAARPC1 reads data using direct global reads to confirm the patient
 is on the EWL and then checks the status of the patient on the EWL.  
  
 Linetag: 
  
 UPDTEWL does a direct global read the ^SDWL(409.3,"B" cross reference to check
 to see if the patient is on a EWL. If the patient is on an EWL, a FileMan read
 of field 23, Current Status, is made to get the current status of the patient
 on the EWL.  
  
 Routine MBAARPCL makes direct global reads to the ^SDWL(409.3 file to get EWL
 information for a patient or for a facility.  
  
 Linetags: 
  
 EWL does a direct global read of the ^SDWL(409.3,"B" cross reference to check
 to see if the patient is on the EWL. If the patient is on the EWL, it does a
 FileMan read of for the Current Status (23), Originating Date (1), Desired
 Date of Appointment (22), WL Specific Clinic (8), Priority (10), EWL Enrollee
 Status (27), Date Appt. Made (13.1).  
                                                             
 FACEWL does a direct global read of data on the ^SDWL(409.3,"B" cross 
 reference. A FileMan read is made of the Current Status (23) field to see if
 the patient's entry is closed. If it is open, then a FileMan read is made to
 pull the Originating Date (1), Desired Date of Appointment (22), WL Specific
 Clinic (8), Priority (10), EWL Enrollee Status (27), Date Appt. Made (13.1)
 fields.  
  
 Routine MBAAWLDA locks and unlocks records in the ^SDWL(409.3 file and 
  
 Linetags: 
  
 LOCK locks ^SDWL(409.3,D0 in order to perform and edit action.  
  
 UNLOCK unlocks ^SDWL(409.3,D0 after performing an edit action.  
  
 DISP edits Disposition (21), Date Dispositioned (19), Dispositioned By (20),
 Current Status (23), Scheduled Date of Appt (13), Date Appt. Made (13.1), Appt
 Clinic (13.2), Appt Institution (13.3), Appt Stop Code (13.4), Appt Credit
 Stop Code (13.5), Appt Station Number (13.6), Appt Status (13.8), Apt Clerk
 (13.7) using a FileMan call. 
  
 DISP also uses GET1^DIQ to get WL Specific Clinic. If there is a WL Specific
 Clinic, the ^SDWL(409.3, "SC" cross reference for the entry is KILLed.  
  STATUS: Active
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  DATE ACTIVATED: AUG 17, 2016

NUMBER: 6047                            IA #: 6047
  FILE NUMBER: 409.32                   GLOBAL ROOT: SDWL(409.32
  DATE CREATED: APR 22, 2014            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MBAA Access to SDWL(409.32
  ID: SDWL(409.32
GLOBAL REFERENCE: SDWL(409.32,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   ICR 6047 MBAA Access to SDWL(409.32.  
  
 The Scheduling Calendar View application access the SD WL Clinic Location file
 (#409.32) to get the WL Clinic. The MBAA RPCs, MBAA WAIT LIST BY DFN and MBAA
 FACILITY WAIT LIST makes this call to the file.  
  
 Routine MBAARPCL does a FileMan read of the SD WL CLINIC LOCATION File for the
 specified record to get the Clinic field (.01) in external format.  
  
 Linetag: 
  
 EWL does a FileMan read of the SD WL CLINIC LOCATION File for the specified
 record to get the Clinic field (.01) in external format. (RPC: MBAA WAIT LIST
 BY DFN) 
  
 FACEWL does a FileMan read of the SD WL CLINIC LOCATION File to get the Clinic
 field (.01) in external format. (RPC: MBAA FACILITY WAIT LIST) 
  STATUS: Active
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  DATE ACTIVATED: FEB 26, 2015

NUMBER: 6048                            IA #: 6048
  DATE CREATED: APR 23, 2014            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDAMEVT
  NAME: MBAA SDAMEVT API CALLS          ID: SDAMEVT
 GENERAL DESCRIPTION:   The Scheduling Calendar View application uses APIs in
 the SDAMEVT routine to handle scheduling events.  
  
 API: 
  
 CANCEL^SDAMEVT - This API is used to log or trigger events when an appointment
 is canceled. The API is called from routines MBAAMAP2 and MBAARPC2 and the RPC
 is MBAA CANCEL APPOINTMENT.  
  
 MAKE^SDAMEVT - This API is used to log or trigger events when an appointment
 is made. The API is called from routine MBAAMAP2 and the RPC is MBAA
 APPOINTMENT MAKE.  
  STATUS: Active
COMPONENT/ENTRY POINT: CANCEL
 COMPONENT DESCRIPTION:   The MBAAMAP2 and MBAARPC2 routines call this API to
 handle scheduling events pertaining to cancelling appointments. The RPC is
 MBAA CANCEL APPOINTMENT.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN 
VARIABLES: SDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Date and time for the appointment.  
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer for the clinic in the Hospital Location file
 (#44).  
VARIABLES: CIFN                         TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the appointment record in the Appointment
 Multiple of the Hospital Location file (#44).  
VARIABLES: SDHDL                        TYPE: Input
 VARIABLES DESCRIPTION:   The event handle type.  
VARIABLES: SDMODE                       TYPE: Input
VARIABLES: SDATA                        TYPE: Input
 VARIABLES DESCRIPTION:   This is a list of the before values of the
 appointment before it is canceled. The list of data is pulled from the
 Hospital Location File (#44) and the Patient File (#2), the appointment
 multiple in each of these files.  
COMPONENT/ENTRY POINT: MAKE
 COMPONENT DESCRIPTION:   The MBAAMAP2 routine call this API to handle
 scheduling events pertaining to making appointments. The RPC is MBAA
 APPOINTMENT MAKE.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN 
VARIABLES: SDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The date and time for the appointment.  
VARIABLES: SDDA                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the Clinic in the Hospital Location file
 (#44) 
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the Appointment record in the Appointment
 Multiple of the Hospital Location file (#44).  
VARIABLES: CLILN
VARIABLES: SDMODE                       TYPE: Input
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   MBAA CANCEL APPOINTMENT RPC and MBAA APPOINTMENT MAKE
 RPC call the MAKE and CANCEL entry points in routine SDAMEVT when an
 appointment is scheduled or cancelled using the Scheduling Calendar View
 application.  The Scheduling Calendar View application is a new mobile
 application that provides scheduling functionality via mobile devices such as
 an IPad, tablet or smart phone.  
  
 Additionally, these RPCs call the HANDLE, BEFORE, AFTER and EVT entry points
 in routine SDAMEVT as documented in ICR #5838.  
  DATE ACTIVATED: FEB 24, 2015

NUMBER: 6049                            IA #: 6049
  DATE CREATED: APR 23, 2014            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDMANA
  NAME: MBAA SDMANA API USE             ID: SDMANA
 GENERAL DESCRIPTION:   The Scheduling Calendar View application uses the
 NAVA^SDMANA API to compute the next available indicator when making an
 appointment.  
  
 Routine MBAAMAP2 calls this API when making an appointment. MBAAMAP2 is called
 by the MBAA APPOINTMENT MAKE RPC.  
  STATUS: Active
COMPONENT/ENTRY POINT: NAVA
 COMPONENT DESCRIPTION:   Computes and returns the next available indicator
 when making an appointment.  
VARIABLES: SC                           TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the Clinic in the Hospital Location file
 (#44).  
VARIABLES: SD                           TYPE: Input
 VARIABLES DESCRIPTION:   This is the date of the appointment request.  
VARIABLES: SRT                          TYPE: Input
 VARIABLES DESCRIPTION:   This the type of appointment being requested. N -
 Next Available scheduling request C - Other than next available at clinician's
 request P - Other than next available at the patient's request W - Walk in
 (unscheduled) appointment M - Multiple appointment booking A - Auto rebook 
VARIABLES: SRT0                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns: 0 - not defined or computed to be a next
 available appointment 1 - user defined next available scheduling request 2 -
 computed to be a next available appointment 3 - user defined and computed to
 be next available appointment 
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  DATE ACTIVATED: JAN 05, 2015

NUMBER: 6050                            IA #: 6050
  DATE CREATED: APR 23, 2014            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDQQCN2
  NAME: MBAA SDQQCN2 API                ID: SDQQCN2
 GENERAL DESCRIPTION:   The Scheduling Calendar View package uses the
 SCH^SDQQCN2 API to schedule and change the status of a consult when an
 appointment is made for the consult request.  
  
 Routine MBAAAPI1 calls this API when making an appointment.  
  STATUS: Active
COMPONENT/ENTRY POINT: SCH
 COMPONENT DESCRIPTION:   Schedule consult and change status.  
VARIABLES: SDERR                        TYPE: Output
 VARIABLES DESCRIPTION:   Output variable with results or errors from the call. 
 
VARIABLES: SDIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Consult in the Request/Consultation file
 (#123).  
VARIABLES: SDNP                         TYPE: Input
 VARIABLES DESCRIPTION:   Provider that scheduled the consult.  
VARIABLES: SDDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   The date/time the consult was scheduled.  
VARIABLES: SDALRT                       TYPE: Input
 VARIABLES DESCRIPTION:   Flag to indicate to send or not send alerts to users. 
 
VARIABLES: SDALTO                       TYPE: Input
 VARIABLES DESCRIPTION:   Array of alert recipients IENs that will receive
 alerts.  
VARIABLES: SDCOM                        TYPE: Input
 VARIABLES DESCRIPTION:   An array containing any comments about the consult.  
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  DATE ACTIVATED: JUN 09, 2016

NUMBER: 6051                            IA #: 6051
  DATE CREATED: APR 23, 2014            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  ROUTINE: SDWLE6                       NAME: MBAA use of SDWLE6 API
  ID: SDWLE6
 GENERAL DESCRIPTION:   The Scheduling Calendar View RPC, MBAA REMOVE FROM EWL
 uses the DIS^SDWLE6 API to disposition an EWL entry when removing a patient
 from the SD EWL. Prior to allowing a user to access the EWL options, the
 software checks to be sure the user holds the SDWL MENU security key.  
  
 Routine MBAAWLAP calls the API in order to update the disposition of the EWL
 entry. DIS^SDWLE6 updates the status of the specified entry on the Electronic
 Wait List (EWL) to remove (Status of Closed) the patient from the EWL. The API
 also checks to see if the patient is in the SDWL TRANSFER ACCEPT FILE
 (#409.36). If the patient is in the file, a message is sent to the
 S.SDWL-XFER-SERVER at the facility indicated in the SDWL TRANSFER ACCEPT FILE. 
 
  STATUS: Withdrawn
COMPONENT/ENTRY POINT: DIS
 COMPONENT DESCRIPTION:   The DIS^SDWLE6 API updates the status of the entry on
 the Electronic Wait List EWL to show the patient has been removed from the
 EWL. The update also triggers an email to be sent to the S.SDWL-XFER-SERVER
 server process if the patient is on a wait list transfer list. 
VARIABLES: SDWLDA                       TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the wait list entry in the SD Wait List
 file (#409.3) for the Wait List entry.  
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE

NUMBER: 6052                            IA #: 6052
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123,D0,0
  DATE CREATED: APR 23, 2014
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MBAA ACCESS TO GMR(123
  ID: GMR(123,D0,0
GLOBAL REFERENCE: GMR(123,D0,40,D1
FIELD NUMBER: 5                         FIELD NAME: COMMENT
  LOCATION: 1;0                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: GMR(123,D0,0
FIELD NUMBER: 8                         FIELD NAME: CPRS STATUS
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SENDING PROVIDER
  LOCATION: 0;14                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Scheduling Calendar View (SCV) app is accessing the 
 REQUEST/CONSULTATION File (#123) in order to update the consult request from
 scheduled to pending and to add a comment when an appointment for the consult
 has been cancelled.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  DATE ACTIVATED: MAY 16, 2018

NUMBER: 6053                            IA #: 6053
  FILE NUMBER: 2                        GLOBAL ROOT: DPT
  DATE CREATED: APR 23, 2014            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MBAA ACCESS TO THE PATIENT FILE
  ID: DPT
GLOBAL REFERENCE: DPT(D0,'S',D1,0
FIELD NUMBER: .01                       FIELD NAME: CLINIC
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: PURPOSE OF VISIT
  LOCATION: 0;7                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 9.5                       FIELD NAME: APPOINTMENT TYPE
  LOCATION: 0;16                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 20                        FIELD NAME: DATE APPT MADE
  LOCATION: 0;19                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: LAB DATE/TIME
  LOCATION: 0;3                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: X-RAY DATE/TIME
  LOCATION: 0;4                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: EKG DATE/TIME
  LOCATION: 0;5                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 19                        FIELD NAME: DATA ENTRY CLERK
  LOCATION: 0;18                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 24
  FIELD NAME: APPOINTMENT TYPE SUB CATEGORY
  LOCATION: 0;24                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 25                        FIELD NAME: SCHEDULING REQUEST TYPE
  LOCATION: 0;25                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 26                        FIELD NAME: NEXT AVA. APPT INDICATORY
  LOCATION: 0;26                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: NO-SHOW/CANCELLED BY
  LOCATION: 0;12                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: NO-SHOW/CANCEL DATE/TIME
  LOCATION: 0;14                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: CANCELLATION REASON
  LOCATION: 0;15                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 13                        FIELD NAME: COLLATERAL VISIT
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: ROUTING SLIP PRINTED
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SPECIAL SURVEY DISPOSITION
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: NUMBER OF COLLATERAL SEEN
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 12
  FIELD NAME: AUTO-REBOOKED APPT. DATE/TIME
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8.5                       FIELD NAME: ROUTING SLIP PRINT DATE
  LOCATION: 0;13                        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 Read & w/Fileman
FIELD NUMBER: 23                        FIELD NAME: ENCOUNTER FORMS AS ADD-ONS
  LOCATION: 0;22                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 23.1                      FIELD NAME: ENCOUNTER CONVERSION STATUS
  LOCATION: 0;23                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(DO,'S',D1,'R'
FIELD NUMBER: 17                        FIELD NAME: CANCELLATION REMARKS
  LOCATION: R;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   If this appointment was cancelled, additional remarks as
 to the reason the appointment was cancelled can be entered. This is optional.  
 GENERAL DESCRIPTION:   The Scheduling Calendar View application accesses the
 Patient file (#2) in order to lookup up appointments, to make appointments and
 to cancel appointments and to get a list of a patient's pending appointments.
 SCV RPC that are called and access the file are MBAA APPOINTMENT MAKE, MBAA
 CANCEL APPOINTMENT and MBAA PATIENT PENDING APPT 
  
 Routine MBAAMDA2: Linetags: 
  
 GETDAPTS does a direct global read of the ^DPT(D0,"S",Date/time to get the
 Clinic (.01) and Status (3) fields. 
  
 GETAPTO returns the ^DPT(D0,"S",Date/time,0) node if the patient has an 
 appointment at that date/time. The fields returned are the (#.01) CLINIC ,
 (#3) STATUS , (#5) LAB DATE/TIME , (#6) X-RAY DATE/TIME , (#7) EKG DATE/TIME ,
 (#8) ROUTING SLIP PRINTED , (#9) PURPOSE OF VISIT , (#10) SPECIAL SURVEY
 DISPOSITION  (#11) NUMBER OF COLLATERAL SEEN , (#12) AUTO-REBOOKED APPT.
 DATE/TIME , (#13) COLLATERAL VISIT , (#14) NO-SHOW/CANCELLED BY , (#8.5)
 ROUTING SLIP PRINT DATE , (#15) NO-SHOW/CANCEL DATE/TIME , (#16) CANCELLATION
 REASON , (#9.5) APPOINTMENT TYPE , (#18) APPT. CANCELLED , (#19) DATA ENTRY
 CLERK , (#20) DATE APPT. MADE ,(#21) OUTPATIENT ENCOUNTER , (#22) ENCOUNTER
 FORMS PRINTED , (#23) ENCOUNTER FORMS AS ADD-ONS , (#23.1) ENCOUNTER
 CONVERSION STATUS ,(#24) APPOINTMENT TYPE SUB-CATEGORY , (#25) SCHEDULING
 REQUEST TYPE , (#26) NEXT AVA. APPT. INDICATOR.  
  
 Routine MBAAMDA3 Linetag: 
  
 MAKE uses FILE^DIE to enter a new appointment into the Appointment multiple in
 the Patient file (#2). Fields that are edited are Clinic (.01), Status (3),
 Purpose of Visit (9), Appointment Type (9.5), Date Appt Made (20), Lab
 Date/Time (5), X-Ray Date/Time (6), EKG Date/Time (7), Data Entry Clerk (19),
 Appointment Type Sub-Category (24), Scheduling Request Type (25), Next Ava.
 Appt. Indicator (26).  
  
 CANCEL uses FILE^DIE to update the Appointment multiple in order to cancel an
 appointment for a patient. Fields that are edited are Status (3), 
 No-Show/Cancelled By (14), No-Show/Cancel Date/Time (15), Cancellation Reason
 (16),  Data Entry Clerk (19), Date Appt Made (20), Cancellation Remarks (17).  
  
 Routine: MBAAMDA4 Linetag: GETCAPT does a direct global read to get the Clinic
 field (.01) from the ^DPT(D0,"S",Date/time node for an appointment in order to
 cancel the appointment. 
  
 Routine MBAARPC2 
  
 Linetag CHKCAN does a direct global read of the ^DPT(D0,"S",Date/Time) node to
 see if the patient has an appointment on the date/time.  
  STATUS: Active
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  DATE ACTIVATED: MAR 23, 2015

NUMBER: 6054                            IA #: 6054
  DATE CREATED: APR 24, 2014            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDAM2
  NAME: MBAA USE OF SDAM2 API           ID: SDAM2
 GENERAL DESCRIPTION:   The Scheduling Calendar View application makes a call
 to the API INP^SDAM2 from MAKE^MBAAMAP2 when scheduling an appointment for a
 patient to check the inpatient status of the patient.  
  
 The SDAM2 API will be used by the MBAA APPOINTMENT MAKE RPC.  
  STATUS: Active
COMPONENT/ENTRY POINT: INP
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient DFN.  
VARIABLES: VDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   This is a date to see if the patient is an inpatient
 on that date.  
VARIABLES: SDINP                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns a flag to indicate the patient is currently
 an inpatient. Returns null if the patient is not currently an inpatient.
 Returns "I" if the patient is currently an inpatient.  
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  DATE ACTIVATED: DEC 31, 2014

NUMBER: 6055                            IA #: 6055
  DATE CREATED: APR 24, 2014            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  NAME: MBAA USE OF API IN XUMF         STATUS: Pending

NUMBER: 6056                            IA #: 6056
  DATE CREATED: MAY 09, 2014
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA6056
  STATUS: Pending

NUMBER: 6057                            IA #: 6057
  DATE CREATED: MAY 09, 2014
  CUSTODIAL PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  USAGE: Private                        TYPE: Routine
  ROUTINE: SDAM1                        NAME: MBAA ACCESS TO SDAM1 API
  ID: SDAM1
 GENERAL DESCRIPTION:   The MBAA Scheduling Calendar View (SCV) package needs
 to access the STATUS^SDAM1 API in order to get the status of an appointment.  
  STATUS: Withdrawn
COMPONENT/ENTRY POINT: STATUS
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The Patient DFN.  
VARIABLES: SD                           TYPE: Input
 VARIABLES DESCRIPTION:   The date/time of the appointment.  
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   The IFN of the clinic in the Hospital Location file
 (#44).  
VARIABLES: SDATA                        TYPE: Input
 VARIABLES DESCRIPTION:   Contains the 0th node fo the patient appointment
 entry.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   Returns a carat delimited value that contains the
 following data: 
  
 the appt status ifn ^ status name ^ print status ^ check in date/time ^ check
 out date/time ^adm mvt ifn 
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE

NUMBER: 6058                            IA #: 6058
  DATE CREATED: MAY 20, 2014
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: Routine
  ROUTINE: GMRCGUIS                     NAME: MBAA ACCESS TO GMRCGUIS API
  ID: GMRCGUIS
 GENERAL DESCRIPTION:   The Scheduling Calendar View (MBAA namespace) uses the
 STATUS^GMRCGUIS API to get the status of a consult.  
  STATUS: Withdrawn
COMPONENT/ENTRY POINT: STATUS
 COMPONENT DESCRIPTION:   Returns the status of a consult for a patient, clinic
 and date.  
VARIABLES: CLINID ID                    TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the Clinic in the Hospital Location file
 (#44).  
VARIABLES: APPOINTMENT DATE/TIME        TYPE: Input
 VARIABLES DESCRIPTION:   The date and time of the appointment or consult.  
VARIABLES: PATIENT DFN                  TYPE: Input
 VARIABLES DESCRIPTION:   The patient DFN.  
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE

NUMBER: 6059                            IA #: 6059
  DATE CREATED: MAY 20, 2014            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMDIEV
  NAME: DISABLE REMINDER EVALUATION DURING INDEX BUILD
  ID: PXRMDIEV                          STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: DISABLE REMINDER EVALUATION
COMPONENT/ENTRY POINT: INDEXD
 COMPONENT DESCRIPTION:   The entry point INDEXD^PXRMDIEV(FILE NUMBER) will
 disable reminder evaluation while a portion of the Clinical Reminders Index is
 being rebuilt. The input parameter FILE NUMBER is the file number of the file 
 that is being indexed.  
  
VARIABLES: FILE NUMBER                  TYPE: Input
 VARIABLES DESCRIPTION:   This is the file that is being indexed.  
  
SUBSCRIBING PACKAGE: PROBLEM LIST
 SUBSCRIBING DETAILS:   The file number for Problem List is 9000011.  
  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  DATE ACTIVATED: MAY 21, 2014

NUMBER: 6060                            IA #: 6060
  DATE CREATED: MAY 23, 2014            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBJTU6
  NAME: IB CLAIM REJECT FLAG            ID: IBJTU6
 GENERAL DESCRIPTION:   This function checks file #361 and returns a flag that
 indicates whether the bill that was input has a rejected status.  Input: 
  BILL - Bill number from #399 Output: 
  REJECT - Reject status (blank = not found, 0 = not a reject, 1 = rejected) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CLAIM
KEYWORDS: REJECT
KEYWORDS: BILL
COMPONENT/ENTRY POINT: BILLREJ
VARIABLES: BILL                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to an entry in #399, BILL/CLAIMS FILE.  
VARIABLES: REJECT                       TYPE: Output
 VARIABLES DESCRIPTION:   Billing reject status (blank = not found, 0 = not a
 reject, 1 = rejected) 
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: JUN 11, 2014

NUMBER: 6061                            IA #: 6061
  DATE CREATED: MAY 28, 2014            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCNHUT1
  NAME: IBCNHUT1 (HPID/OEID)            ID: IBCNHUT1
 GENERAL DESCRIPTION:   The purpose of the standardized HPID is to eliminate
 the ambiguity that presently exists in electronic standard healthcare 
 transactions, and to streamline the numerous ways in which the term "health
 plan" is interpreted based on the different ways that health plans operate.
 This ambiguity undermines the value of electronic transactions by requiring
 repeated manual intervention.  
      
 Both the IB and BPS (e-Claims Mgmt) namespaces will be displaying the HPID on
 various reports and screens, and BPS will need to be able to access the IB
 utility that was developed to find, validate and display the HPID for a 
 particular health plan.  
  
 The functions of IBCNHUT1 will return the HPID/OEID for an insurance company
 and validate that the HPID/OEID is in the correct format (10 numeric
 characters, 1st character is a 6 or 7 and the 10th character is the Luhn
 check-digit).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HPID
KEYWORDS: IBCNHUT1
COMPONENT/ENTRY POINT: HPD
 COMPONENT DESCRIPTION:   HPD(INS,V) ; this function returns the HPID/OEID for
 an insurance company.  The user must pass INS = Insurance Company ien in file
 36 (required).  Optional variable: V = 1 means run validation checks (not
 required), which  will append an '*'  to the HPID if it does NOT pass
 validation checks 
      
 Output: Null if no HPID/OEID found for this insurance company ien - or - Data
 string contained in field #36.08 (HPID/OEID) of file 36 for ien, - and - if
 V=1 and the data string fails validation, the data string with a '*' added to
 the end.  
VARIABLES: INS                          TYPE: Input
 VARIABLES DESCRIPTION:   Insurance Company internal entry number in file 36
 (required).  
VARIABLES: V                            TYPE: Input
 VARIABLES DESCRIPTION:   Validation flag (optional).  If set to 1, validation
 checks will be run on the HPID and a "*" will be appended to the end of the
 HPID if it fails the validation  checks.  If not set or V'=1, only the HPID
 for the insurance company will be  returned, no validation checks will be run. 
 To call:  W !,"HPID/OEID:  ",$$HPD^IBCNHUT1(INS,1) for validation - or - W
 !,"HPID/OEID:  ",$$HPD^IBCNHUT1(INS) if no validation is to occur.  
COMPONENT/ENTRY POINT: HOD
 COMPONENT DESCRIPTION:   HOD(ID,INS,IBHD) ; function to determine if the data
 is an HPID, an OEID, or an invalid ID ID = data string to validate (required) 
 INS = insurance co. ien (optional) IBHD = Insurance co HPID in file 36
 (optional) 
      
 HPID/OEID is a 10 character string with the 1st digit being 7 for HPID & 6 for
 OEID and the 10th digit being a LUHN Check digit. If the data passed in the ID
 variable does not meet these requirements, this function returns a -1 for
 invalid ID.  Otherwise it returns an H for HPID or an O for OEID.  
      
 If the optional INS or IBHD values are passed, an additional validation check
 will be done, comparing the ID to what is currently on file for that insurance
 company ien (INS) or the IBHD value. If they do not match, this function will
 return a -1 for invalid ID.  
      
 returns data string:    H for HPID, O for OEID, -1 for Invalid ID              
     to call:  W $$HOD^IBCNHUT1(X,INS) - or - I $$HOD^IBCNHUT1(X,INS) it is not
 a valid ID 
VARIABLES: ID                           TYPE: Input
 VARIABLES DESCRIPTION:   HPID/OEID value to be validated (required).  Returns
 an H if the ID is an HPID, an O if the ID is an OEID, and a string of
 "-1^HPID/OEID^*" if the ID failed the validation checks.  To call:  I
 $$HOD^IBCNHUT1(X) it is not a valid ID.  
VARIABLES: INS                          TYPE: Input
 VARIABLES DESCRIPTION:   The insurance ien in file 36 (not required).  If it
 exists, an additional validation check will be performed.  The ID value will
 be compared with the HPID/OEID value in field 8.01 for the insurance ien in
 file 36.  If they do not match, a string of "-1^HPID/OEID^*" will be returned 
 indicating the ID did not pass validation checks.  
VARIABLES: IBHD                         TYPE: Input
 VARIABLES DESCRIPTION:   The value of the field #8.01 in file 36 for insurance
 company ien INS, if already known (not required).  If it exists, an additional
 validation check will be performed.  The ID value will be compared with the
 IBHD value.  If they do not match, a string of "-1^HPID/OEID^*" will be
 returned indicating the ID did not pass validation checks.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
 SUBSCRIBING DETAILS:   E-claims needs to display the validated HPID from the
 insurance company file on their COB screens and reports.  E-claims needs to
 validate the HPID from the BPS response file on their ECME Claims Log and the
 Response Inquiry Report.  
  DATE ACTIVATED: JUN 19, 2014

NUMBER: 6062                            IA #: 6062
  FILE NUMBER: .85                      GLOBAL ROOT: DI(.85
  DATE CREATED: JUN 02, 2014            CUSTODIAL PACKAGE: 1
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: LANGUAGE file
  ID: DI(.85
GLOBAL REFERENCE: DI(.85,D0,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the name of the Language 
  
FIELD NUMBER: .03                       FIELD NAME: THREE LETTER CODE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the Three-letter code defined for the language.  
 GENERAL DESCRIPTION:   With VA FileMan 22.2, the LANGUAGE file (#.85) has been
 updated to contain ISO 639-1 and 639-2 compatible languages. This file can be
 used as a Pointer to file for any field that wants to reference a language.
 Any application that points to this file should set screening logic to 
 constrict the user selection. The screening logic should use the TYPE field
 (#.07), $P(^(0),U,7), which is a set of codes: 
        'L' FOR Living 
        'C' FOR Constructed 
        'A' FOR Ancient 
        'H' FOR Historical 
        'E' FOR Extinct 
        
  If you only want to allow selections of languages that are currently spoken, 
 you can use the following: 
  S DIC("S")="I $P(^(0),U,7)=""L""" 
  
 Also, read access is permitted using FileMan APIs.  
  
 Amended: 1/3/23 Added Field.03 THREE LETTER CODE for use by REGISTRATION, 
 INCOME VERIFICATION MATCH effective with patch DG*5.3*1085/IVM*2.0*208 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Language
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
 SUBSCRIBING DETAILS:   Added 1/3/23 effective with DG*5.3*1085/IVM*2.0*208 
  DATE ACTIVATED: JAN 03, 2023

NUMBER: 6063                            IA #: 6063
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19
  DATE CREATED: JUN 04, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: MBAA RPC REGISTRATION           ID: DIC(19
GLOBAL REFERENCE: DIC(19,'B'
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(19,D0,'RPC',D1,0
FIELD NUMBER: .01                       FIELD NAME: RPC
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE

NUMBER: 6064                            IA #: 6064
  FILE NUMBER: 404.57                   GLOBAL ROOT: SCTM(404.57
  DATE CREATED: JUN 04, 2014            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MBAA ACCESS TO SCTM(404.57
  ID: SCTM(404.57
GLOBAL REFERENCE: SCTM(404.57,D0,0)
FIELD NUMBER: .01                       FIELD NAME: POSITION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Scheduling Calendar View application is doing a
 FileMan read of the ^SCTM(404.57 file for the specified record to check for
 the existence of the record in the file. This check is to make sure the team
 position exists in the file. If the position doesn't exist in the file an
 error message is return to the calling application and the RPC stops
 execution.  
  
 This is a data validation check to be sure the data that will be filed when
 making a new entry for the Electronic Wait List is valid data. The record in
 the file pointed to actually exists. This insures there will not be a broken
 pointer when the new record is created.  
  STATUS: Active
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Scheduling Calendar View routine MBAARPC2 is doing a
 FileMan read of the ^SCTM(404.57, file for the specified record to see if the
 record exists. MBAARPC2 routine is called by MBAA EWL NEW RPC.  
  DATE ACTIVATED: JAN 30, 2015

NUMBER: 6065                            IA #: 6065
  DATE CREATED: JUN 13, 2014            CUSTODIAL PACKAGE: PROBLEM LIST
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: GMPL EVENT
 GENERAL DESCRIPTION:   The GMPL EVENT protocol is used to pass patient problem
 list items from the Problem List package to other packages. This protocol is
 exported by the Problem List package.  
  STATUS: Active
KEYWORDS: PROBLEM LIST
SUBSCRIBING PACKAGE: SURGERY
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   The HMP protocol is HMP GMPL EVENT 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: JUN 16, 2014

NUMBER: 6066                            IA #: 6066
  FILE NUMBER: 80.5                     GLOBAL ROOT: ICDRS(
  DATE CREATED: JUN 13, 2014            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DRG SURGICAL HIERARCHY
  ID: ICDRS(
 GENERAL DESCRIPTION:   Lexicon Utility has all privileges as though it were
 the custodial package.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LEXICON
KEYWORDS: 80.2
KEYWORDS: ICD
KEYWORDS: SURGERY
SUBSCRIBING PACKAGE: LEXICON UTILITY
  DATE ACTIVATED: JUL 10, 2014

NUMBER: 6067                            IA #: 6067
  FILE NUMBER: 445.6                    GLOBAL ROOT: PRCP(445.6
  DATE CREATED: JUN 19, 2014            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS TO FILE #445.6 (GROUP CATEGORY)
  ID: PRCP(445.6
GLOBAL REFERENCE: PRCP(445.6,D0,0)
FIELD NUMBER: .01                       FIELD NAME: GROUP CATEGORY CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Request permission for READ access via FileMan calls to
 file #445.6 in order to complete RPC queries from WaveMark. This is part of
 the RTLS National project to facilitate tracking clinical supplies in the Cath
 lab inventory point for GIP.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM
  DATE ACTIVATED: JUL 02, 2014

NUMBER: 6068                            IA #: 6068
  FILE NUMBER: 420.5                    GLOBAL ROOT: PRCD(420.5
  DATE CREATED: JUN 19, 2014            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS TO FILE #420.5 (UNIT OF ISSUE)
  ID: PRCD(420.5
GLOBAL REFERENCE: PRCD(420.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Request permission for READ access via FileMan calls to
 file #420.5 in order to complete RPC queries from WaveMark. This is part of
 the RTLS National project to facilitate tracking clinical supplies in the Cath
 lab inventory point for GIP.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
SUBSCRIBING PACKAGE: REAL TIME LOCATION SYSTEM
  DATE ACTIVATED: JUL 02, 2014

NUMBER: 6069                            IA #: 6069
  DATE CREATED: JUN 27, 2014
  CUSTODIAL PACKAGE: REAL TIME LOCATION SYSTEM
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VIAATRI
  NAME: ENGINEERING CALL TO RTLS AFTER DATA CHANGE
  ID: VIAATRI
 GENERAL DESCRIPTION:   The RTLS project has requested the Engineering files
 #6914 and #6928 to have a number of fields modified with MUMPS
 cross-references to report data changes.  
    
 Whenever an entry is changed in either file #6914 or #6928 which affects any
 of the modified fields, a call is made to the RTLS routine VIAATRI to notify
 InSites that a data change occurred in Engineering. The call is made by the
 MUMPS cross-reference as follows: D WC^VIAATRI(File,DA), where File represents
 either file 6914 or file 6928 and DA is the internal entry number of a record
 in one of the files. Upon execution of the call, a record is added in the
 PENDING RTLS EVENTS file, #6930, and later the record is sent to update
 InSites. This event keeps both InSites and VistA synchronized.  
  
 Patch EN*7.0*95 added cross-references that call WC^VIAATRI on the following
 fields: 
  
 File 6914 Fields .01, 1, 2, 3, 4, 5, 6, 7, 11, 12, 13, 18, 19, 20, 21, 22, 30,
 60.  
  
 File 6928 Fields .01, 1, 1.5 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RTLS
COMPONENT/ENTRY POINT: WC
 COMPONENT DESCRIPTION:   At the entry point WC, the parameters File and DA are
 passed in.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   Either file 6914 or 6928.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of a record in the file.  
SUBSCRIBING PACKAGE: ENGINEERING
  DATE ACTIVATED: JUL 11, 2014

NUMBER: 6070                            IA #: 6070
  FILE NUMBER: 52.41                    GLOBAL ROOT: PS(52.41,
  DATE CREATED: JUL 09, 2014            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Pending Outpatient Orders Lookup
  ID: PS(52.41,
GLOBAL REFERENCE: PS(52.41
FIELD NUMBER: 8
  FIELD NAME: PHARMACY ORDERABLE ITEM FIELD
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: DRUG FIELD
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Inpatient Pharmacy allergy order checks need to include
 all prescription ordering processes. Inpatient Medications requests direct
 global read access to the following pharmacy file: 
  
  
    ^PS(52.41, - PENDING OUTPATIENT ORDERS FILE (#52.41) 
      Node 0, piece 8 - PHARMACY ORDERABLE ITEM FIELD (#8) 
      Node 0, piece 9 - DRUG FIELD (#9) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: SEP 04, 2014

NUMBER: 6071                            IA #: 6071
  GLOBAL ROOT: TMP('PSODAOC',           DATE CREATED: JUL 09, 2014
  CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  NAME: Outpatient Pharmacy Allergy     ID: TMP('PSODAOC',
GLOBAL REFERENCE: TMP('PSODAOC',$J
 GLOBAL DESCRIPTION:   This global is used to return data from a call to
 DOAC^PSONEWOA.  It contains data split into drug classes, drug ingredients and 
 signs/symptoms.  
 GENERAL DESCRIPTION:   This global is used to return the data from a call to 
 DAOC^PSONEWOA.  It contains data split into drug classes, drug ingredients and
 pharmacy interventions. Inpatient Medications must access Outpatient Pharmacy
 namespaced ^TMP global to perform allergy order checks. This global is
 generated by an Inpatient Medications process calling an Outpatient routine.
 Inpatient Medications requests direct global Read/Write access to the
 following pharmacy ^TMP file: 
  
 ^TMP("PSODAOC",$J,"ALLERGY",)  - Outpatient Pharmacy Allergy Data 
  
 Inpatient Meds kills the TMP global before and after the call to the 
 Outpatient Pharmacy API.  
  
 VARIABLES: Input       TMP GLOBAL 
            Nodes descendant from ^TMP("PSODAOC",$J,"ALLERGY",PSOALGCT) 
            are stored.  
  
    ROUTINE: PSONEWOA 
    COMPONENT: DAOC 
    INPUT: 
     ^TMP("PSODAOC",$J,"ALLERGY",PSOALGCT)=List of allergy order checks 
     ^TMP("PSODAOC",$J,"ALLERGY",PSOALGCT,"ALLERGY DD")=DRUG File IEN 
     ^TMP("PSODAOC",$J,"ALLERGY",PSOALGCT,"ALLERGY PKG")="IP" Hard Set 
     ^TMP("PSODAOC",$J,"ALLERGY",PSOALGCT,"INTERVENTION")=APSP INTERVENTION 
                                                          File IEN 
     ^TMP("PSODAOC",$J,"ALLERGY","ALLERGY PKG") 
        $P1 = "IP" Hard Set 
        $P2 = Process ID i.e., "COPY IV","RENEW UD" 
        $P3 = Prescription Order Number 
        $P4 = ORDER File IEN 
     ^TMP("PSODAOC",$J,"ALLERGY","PROVR")= Provider Override Reason 
  STATUS: Pending
KEYWORDS: TMP PSODAOC
KEYWORDS: ALLERGY
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS

NUMBER: 6072                            IA #: 6072
  DATE CREATED: JUL 09, 2014            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSONEWOA
  NAME: Allergy Order Check Filing      ID: PSONEWOA
 GENERAL DESCRIPTION:   This DBIA provides the DAOC^PSONEWOA routine call for
 Inpatient Medications to make to Outpatient Pharmacy. It takes the ^TMP global
 input data sent in from Inpatient Medications that contains allergy order
 check data and creates an entry in the ORDER CHECK INSTANCES File (#100.05),
 by invoking SAVEOC^OROCAPI1.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Allergy
COMPONENT/ENTRY POINT: DAOC
 COMPONENT DESCRIPTION:   Input: ^TMP("PSODAOC",$J,"ALLERGY") contains allergy
 order check data as follows: 
  Note: 'ctr' represents counter, where multiple entries can exist.  
  
  
 ^TMP("PSODOAC",$J,"ALLERGY",ctr,4,ctr,0 )= p1^p2^p3^p4^p5^p6^p7 
     where  p1 = Reactant 
            p2 = Causative Agent 
            p3 = Location Type 
            p4 = Remote Location 
            p5 = Origination Date/Time 
            p6 = Observed or Historical 
            p7 = Severity   
  
 ^TMP("PSODAOC",$J,"ALLERGY",ctr,4,ctr,1,ctr,0) = VA Drug Class 
  
 ^TMP("PSODAOC",$J,"ALLERGY",ctr,4,ctr,2,ctr,0) = Drug Ingredient 
  
 ^TMP("PSODAOC",$J,"ALLERGY",ctr,4,ctr,3,ctr,0) = Sign/Sympton 
  
 ^TMP("PSODAOC",$J,"ALLERGY",ctr,"ALLERGY DD",5,ctr,0) = Dispense Drug 
  
 ^TMP("PSODAOC",$J,"ALLERGY",ctr,"INTERVENTION") = Intervention 
  
 ^TMP("PSODAOC",$J,"ALLERGY","ALLERGY PKG")=p1^p2^p3^p4 
     where p1 = "IP" 
           p2 = Action + package. For example 'RENEW UD' or 'COPY IV' 
           p3 = Pharmacy Order Number 
           p4 = Computerized Patient Record System (CPRS) Order Number 
  
 ^TMP("PSODAOC",$J,"ALLERGY","PROVR") = Override Reason 
  
  
 Output: An entry will be created in the ORDER CHECK INSTANCES File (#100.05).  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Inpatient Medications will pass allergy order check
 data to Outpatient Pharmacy and Outpatient Pharmacy will call Computerized
 Patient Record System (CPRS) to store that allergy order check data in the
 ORDER CHECK INSTANCES File (#100.05).  
  DATE ACTIVATED: NOV 14, 2017

NUMBER: 6073                            IA #: 6073
  DATE CREATED: JUL 10, 2014            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: WVTDCF                       NAME: PREGNANCY AND LACTATION DATA
  ID: WVTDCF
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to retrieve pregnancy and lactation data for a patient.  The APIs were
 designed for use by the reminder computed finding functionality of the
 Clinical Reminders package.  
  STATUS: Expired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 25, 2025
KEYWORDS: REMINDER COMPUTED FINDING
KEYWORDS: PREGNANCY
KEYWORDS: LACTATION
COMPONENT/ENTRY POINT: PREGSTAT(DFN,NGET,BDT,EDT,NFOUND,TEST,DATE,DATA,TEXT)
 COMPONENT DESCRIPTION:   This entry point returns the entries from the WV
 PREGNANCY LOG file for a single patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient in the WV
 PATIENT file.  
VARIABLES: NGET                         TYPE: Input
 VARIABLES DESCRIPTION:   Specifies the maximum number of entries to return
 (optional).  Not passing this parameter returns all entries.  A negative value
 will return the entries in reverse date order, with the oldest entry first,
 while a positive value will return the entries in date order, with the newest 
 entry first.  
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The start date for searching for entries (optional). 
 Entries created before this date are not returned.  
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The end date for searching for entries (optional). 
 Entries entered after this date are not returned.  
VARIABLES: NFOUND                       TYPE: Output
 VARIABLES DESCRIPTION:   The number of entries returned.  
VARIABLES: TEST                         TYPE: Output
 VARIABLES DESCRIPTION:   An array of logical values, one for each entry
 returned.  The first subscript number is one for the first entry found and
 subsequent subscripts are incremented by one.  For every entry found, the
 logical value will be TRUE.  
VARIABLES: DATE                         TYPE: Output
 VARIABLES DESCRIPTION:   Array of FileMan formatted dates, one for each entry
 returned.  The first subscript number is one for the first entry found and
 subsequent subscripts are incremented by one.  For every entry returned, the
 date will be the date the entry was created.  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   Array of values from each entry.  The array is
 formatted as follows: 
  
  DATA(N,"STATUS")=PREGNANCY STATUS field 
                   External format 
  DATA(N,"EDD")=EDD field (expected date of 
                delivery) 
                FileMan format 
  DATA(N,"DELIVERY DATE")=DELIVERY DATE field 
                          FileMan format 
  
 N is the entry number and starts at one and increments by one for each entry
 that is found.  
VARIABLES: TEXT                         TYPE: Output
 VARIABLES DESCRIPTION:   Array of display text values, one for each entry
 returned.  The first subscript is one for the first entry found and subsequent
 subscripts are incremented by one.  For every entry returned, the display text
 is an empty string.  
COMPONENT/ENTRY POINT: LACSTAT(DFN,NGET,BDT,EDT,NFOUND,TEST,DATE,DATA,TEXT)
 COMPONENT DESCRIPTION:   This entry point returns entries from the WV
 LACTATION LOG file for a single patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient in the WV
 PATIENT file.  
VARIABLES: NGET                         TYPE: Input
 VARIABLES DESCRIPTION:   Specifies the maximum number of entries to return
 (optional).  Not passing this parameter returns all entries.  A negative value
 will return the entries in reverse date order, with the oldest entry first,
 while a positive value will return the entries in date order, with the newest 
 entry first.  
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The start date for searching for entries (optional). 
 Entries created before this date are not returned.  
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The end date for searching for entries (optional). 
 Entries entered after this date are not returned.  
VARIABLES: NFOUND                       TYPE: Output
 VARIABLES DESCRIPTION:   The number of entries returned.  
VARIABLES: TEST                         TYPE: Output
 VARIABLES DESCRIPTION:   An array of logical values, one for each entry
 returned.  The first subscript number is one for the first entry found and
 subsequent subscripts are incremented by one.  For every entry found, the
 logical value will be TRUE.  
VARIABLES: DATE                         TYPE: Output
 VARIABLES DESCRIPTION:   Array of FileMan formatted dates, one for each entry
 returned.  The first subscript number is one for the first entry found and
 subsequent subscripts are incremented by one.  For every entry returned, the
 date will be the date the entry was created.  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   Array of values from each entry.  The array is
 formatted as follows: 
  
  DATA(N,"STATUS")=LACTATION STATUS field 
                   External format 
  DATA(N,"END DATE")=END DATE field (date patient 
                     stopped lactating) 
                     FileMan format 
  
 N is the entry number and starts at one and increments by one for each entry
 that is found.  
VARIABLES: TEXT                         TYPE: Output
 VARIABLES DESCRIPTION:   Array of display text values, one for each entry
 returned.  The first subscript is one for the first entry found and subsequent
 subscripts are incremented by one.  For every entry returned, the display text
 is an empty string.  
COMPONENT/ENTRY POINT: MUTC(DFN,TEST,DATE,DATA,TEXT)
 COMPONENT DESCRIPTION:   This entry point returns the value of the MEDICALLY
 UNABLE TO CONCEIVE field in the WV PATIENT file for a single patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient in the WV
 PATIENT file.  
VARIABLES: TEST                         TYPE: Output
 VARIABLES DESCRIPTION:   The value stored in the MEDICALLY UNABLE TO CONCEIVE
 field in the WV PATIENT file.  
VARIABLES: DATE                         TYPE: Output
 VARIABLES DESCRIPTION:   If the MEDICALLY UNABLE TO CONCEIVE field is set to
 YES, this will be the date the entry point is executed in FileMan format.  For
 all other field values, this will be an empty string.  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   A value associated with the value of TEST.  This will
 always be an empty string.  
VARIABLES: TEXT                         TYPE: Output
 VARIABLES DESCRIPTION:   The display text value.  This will always be an empty
 string.  
COMPONENT/ENTRY POINT: LOBP(DFN,TEST,DATE,DATA,TEXT)
 COMPONENT DESCRIPTION:   This entry point returns the patient's likelihood of
 becoming pregnant.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient in the WV
 PATIENT file.  
VARIABLES: TEST                         TYPE: Output
 VARIABLES DESCRIPTION:   The logical value associated with the returned
 likelihood.  The value is TRUE if a likelihood was calculated and FALSE if a
 likelihood was not calculated.  
VARIABLES: DATE                         TYPE: Output
 VARIABLES DESCRIPTION:   If a likelihood is successfully calculated, this will
 be the date the entry point is executed in FileMan format.  If a likelihood is
 not successfully calculated, this will be an empty string.  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the likelihood of the patient becoming
 pregnant in external format.  ["HIGH"|"LOW"|"UNKNOWN"] 
VARIABLES: TEXT                         TYPE: Output
 VARIABLES DESCRIPTION:   The display text value.  This will always be an empty
 string.  
COMPONENT/ENTRY POINT: CM(DFN,NGET,BDT,EDT,NFOUND,TEST,DATE,DATA,TEXT)
 COMPONENT DESCRIPTION:   This entry point returns all of the values in the
 CONTRACEPTIVE METHODS USED field in the WV PATIENT file for a single patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient in the WV
 PATIENT file.  
VARIABLES: NGET                         TYPE: Input
 VARIABLES DESCRIPTION:   Specifies the maximum number of entries to return
 (optional).   Not passing this parameter returns all entries.  
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The start date for searching for entries (ignored). 
 The time period a patient uses a contraceptive method is not tracked.  
VARIABLES: EDT                          TYPE: Output
 VARIABLES DESCRIPTION:   The end date for searching for entries (ignored). 
 The time period a patient uses a contraceptive method is not tracked.  
VARIABLES: NFOUND                       TYPE: Output
 VARIABLES DESCRIPTION:   The number of entries returned.  
VARIABLES: TEST                         TYPE: Output
 VARIABLES DESCRIPTION:   An array of logical values, one for each entry
 returned.  The first subscript number is one for the first entry found and
 subsequent subscripts are incremented by one.  For every entry returned, the
 logical value will be TRUE.  
VARIABLES: DATE                         TYPE: Output
 VARIABLES DESCRIPTION:   An array of FileMan formatted dates, one for each
 entry returned.  The first subscript number is one for the first entry found
 and subsequent subscripts are incremented by one.  For every entry returned,
 the date will be the date the entry point is executed.  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   Array of values from each entry.  The array is
 formatted as follows: 
  
  DATA(N,"METHOD")=CONTRACEPTIVE METHOD USED Field 
                   External Format 
  DATA(N,"LIKELIHOOD")=Calculated likelihood of 
                       becoming pregnant using 
                       this method alone 
                       External Format: 
                            ["HIGH"|"LOW"|"ERROR"] 
  
 N is the entry number and starts at one and increments by one for each entry
 that is returned.  
VARIABLES: TEXT                         TYPE: Output
 VARIABLES DESCRIPTION:   An array of display text values, one for each entry
 returned.  The first subscript number is one for the first entry found and
 subsequent subscripts are incremented by one.  For every entry returned, the
 display text is an empty string.  
COMPONENT/ENTRY POINT: ATDRUG(DFN,NGET,BDT,EDT,NFOUND,TEST,DATE,DATA,TEXT)
 COMPONENT DESCRIPTION:   This entry point returns all of the active
 teratogenic drug prescriptions for a single patient.  An active prescription
 is one that has had activity within the last 5,000 days.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient in the WV
 PATIENT file.  
VARIABLES: NGET                         TYPE: Input
 VARIABLES DESCRIPTION:   Specifies the maximum number of prescriptions to
 return (optional).   Not passing this parameter returns all entries.  
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The start date for searching for prescriptions
 (ignored).  Only active prescriptions are returned.  
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The end date for searching for prescriptions
 (ignored).  Only active prescriptions are returned.  
VARIABLES: NFOUND                       TYPE: Output
 VARIABLES DESCRIPTION:   The number of prescriptions returned.  
VARIABLES: TEST                         TYPE: Output
 VARIABLES DESCRIPTION:   An array of logical values, one for each prescription
 returned.  The first subscript number is one for the first entry found and
 subsequent subscripts are incremented by one.  For every prescription
 returned, the logical value will be TRUE.  
VARIABLES: DATE                         TYPE: Output
 VARIABLES DESCRIPTION:   An array of FileMan formatted dates, one for each
 prescription returned.  The first subscript number is one for the first entry
 found and subsequent subscripts are incremented by one.  For every
 prescription returned, the date value is the issue date of the prescription.  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   Array of values from each prescription.  The array is
 formatted as follows: 
  
  DATA(N,"DRUG_NAME")=GENERIC NAME Field in the 
                      DRUG File 
  
 N is the entry number and starts at one and increments by one for each 
 prescription that is returned.  
VARIABLES: TEXT                         TYPE: Output
 VARIABLES DESCRIPTION:   An array of display text values, one for each
 prescription returned.  The first subscript number is one for the first entry
 found and subsequent subscripts are incremented by one.  For every
 prescription returned, the display text is an empty string.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 6074                            IA #: 6074
  CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        NAME: Stored Order Check Display

NUMBER: 6075                            IA #: 6075
  DATE CREATED: JUL 14, 2014            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOOCKV1
  NAME: Pharmacy Order Check Display    ID: PSOOCKV1
 GENERAL DESCRIPTION:   This is an internal Pharmacy API used to display stored
 pharmacy order checks.  
  STATUS: Active
KEYWORDS: order check
COMPONENT/ENTRY POINT: UD
 COMPONENT DESCRIPTION:   Input: 
                         Patient ID - DFN 
                         IEN Pharmacy Patient File 
  
                 Output: 
                         Clinic Order 
                         Schedule 
                         Dosage 
                         Start Date 
                         Stop Date 
COMPONENT/ENTRY POINT: IV
 COMPONENT DESCRIPTION:   
                 Input: 
                         Patient ID - DFN 
                         IEN Pharmacy Patient File 
  
                 Output: 
                 If IV 
                         Clinic Order 
                         IV Start 
                         IV Stop 
                         IV Schedule 
                         Additive 
                 If Solution 
                         Solution Name 
                         Solution Schedule 
                         Solution Start Date 
                         Solution Stop Date 
                         Dosage 
                         Start Date 
                         Stop Date 
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: JUL 25, 2014

NUMBER: 6076                            IA #: 6076
  DATE CREATED: JUL 14, 2014            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSJRXI
  NAME: Pharmacy Intervention Log       ID: PSJRXI
 GENERAL DESCRIPTION:   This is an internal pharmacy API used by Inpatient
 Medications and Outpatient Pharmacy to log pharmacy interventions.  
  STATUS: Active
COMPONENT/ENTRY POINT: PSJRXI
VARIABLES: IEN DRUG FILE (50)           TYPE: Input
VARIABLES: IEN APSP INTERVENTION        TYPE: Output
 VARIABLES DESCRIPTION:   OUTPUT:  PSJRXI("DA") = IEN APSP INTERVENTION FILE 
VARIABLES: Condition Flag               TYPE: Output
 VARIABLES DESCRIPTION:   PSJRXI("QFLG") = 1  - Unable to log an intervention.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: SEP 05, 2014

NUMBER: 6077                            IA #: 6077
  DATE CREATED: JUL 16, 2014
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUVPR
  NAME: TIU APIS FOR VPR                ID: TIUVPR
 GENERAL DESCRIPTION:   TIUVPR provides generic api's to allow the Virtual
 Patient Record (VPR) to retrieve all of a patient's documents, regardless of
 status or class.  Class and authorization filters will be applied by the
 Health Management Platform (HMP) as documents are requested by the current
 user.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIUVPR
COMPONENT/ENTRY POINT: GET(.TIUY,DFN,TYPE,EARLY,LATE)
 COMPONENT DESCRIPTION:   Returns all documents for the patient in the
 requested class, subscripted by sequence number 
  
                     ***Warning on Component GET *** 
  
 For Component GET users are warned that documents whose dates are outside of
 the date range are not listed even if they have addenda within the date range. 
 
VARIABLES: TIUY                         TYPE: Output
 VARIABLES DESCRIPTION:   Name of result array, as a closed reference Returns
 @TIUY@(#)=DA and @TIUY@("COUNT")=total# 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file #2 ien 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Document Class #8925.1 ien 
VARIABLES: EARLY                        TYPE: Input
 VARIABLES DESCRIPTION:   Date.time to begin search [optional] 
VARIABLES: LATE                         TYPE: Input
 VARIABLES DESCRIPTION:   Date.time to end search [optional] 
COMPONENT/ENTRY POINT: LIST(.TIUY,DFN,TYPE,EARLY,LATE,STATUS)
 COMPONENT DESCRIPTION:   Returns all documents for the patient [in the
 requested class], subscripted by Document #8925 ien 
VARIABLES: TIUY                         TYPE: Output
 VARIABLES DESCRIPTION:   Passed by reference, to return result array name 
 Returns @TIUY@(DA)="" and @TIUY@("COUNT")=total# 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file #2 ien 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Code indicating the type of documents to return: 
   PN,CR,C,W,A,D,DS,SR,CP,LR, or ALL [default] (Document Class #8925.1 ien also
 accepted) 
VARIABLES: EARLY                        TYPE: Input
 VARIABLES DESCRIPTION:   Date.time to begin search [optional] 
VARIABLES: LATE                         TYPE: Input
 VARIABLES DESCRIPTION:   Date.time to end search [optional] 
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   TIU Status #8925.6 Name [optional, default=COMPLETED] 
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP routine HMPDJ0 calls the GET^TIUVPR API to retrieve
 all the documents for a specified patient in the requested class. 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: SEP 24, 2014

NUMBER: 6078                            IA #: 6078
  DATE CREATED: JUL 16, 2014
  CUSTODIAL PACKAGE: VIRTUAL PATIENT RECORD
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VPREVNT
  NAME: VPR EVENTS                      ID: VPREVNT
 GENERAL DESCRIPTION:   VPREVNT contains various line tags to be used by other
 VistA applications without event protocols to notify VPR of new or modified
 data.  
  
 These hooks were exported in the VPR*1*3 patch bundle which was never released
 to the field; it was, however, posted to OSEHRA as code-in-flight and as such
 are being documented here. The patches referenced with each subscriber were
 included in this bundle to install the respective indices.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VPREVNT
COMPONENT/ENTRY POINT: GMRV(DFN,IEN,ERR)
 COMPONENT DESCRIPTION:   Set Logic for AVPR index on GMRV VITAL MEASUREMENT
 file #120.5; called when a result is entered or marked in error.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file #2 ien 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   GMRV VITAL MEASUREMENT file #120.5 ien 
VARIABLES: ERR                          TYPE: Input
 VARIABLES DESCRIPTION:   Entered in Error field #2, file #120.5 
COMPONENT/ENTRY POINT: TIU(DFN,IEN)
 COMPONENT DESCRIPTION:   Set and Kill Logic for AVPR index on TIU DOCUMENT
 file #8925; called when a document is created or modified.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file #2 ien 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   TIU Document file #8925 ien 
COMPONENT/ENTRY POINT: DOCDEF(IEN)
 COMPONENT DESCRIPTION:   Set and Kill Logic for AVPR index on TIU DOCUMENT
 DEFINITION file #8925.1; called when a document definition is created or
 modified.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   TIU DOCUMENT DEFINITION file #8925.1 ien 
COMPONENT/ENTRY POINT: DOCITM(IEN)
 COMPONENT DESCRIPTION:   Set and Kill Logic for AVPR1 index on the Items
 sub-file of the TIU DOCUMENT DEFINITION file #8925.1; called when the Items of
 a document definition are created or modified.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   TIU DOCUMENT DEFINITION file #8925.1 ien 
COMPONENT/ENTRY POINT: USR(IEN)
 COMPONENT DESCRIPTION:   Set and Kill Logic for AVPR index on USR
 AUTHORIZATION/SUBSCRIPTION file #8930.1; called when a rule is created or
 modified.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   USR AUTHORIZATION/SUBSCRIPTION file #8930.1 ien 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Calls linetag TIU from the AVPR cross reference on file
 #8925 and tags DOCDEF and DOCITM from the AVPR cross references on #8925.1 
 (installed by TIU*1*106) 
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
 SUBSCRIBING DETAILS:   Calls linetag GMRV from the AVPR cross reference on
 file #120.5 (installed by VPR*1*3 post-init; see ICR #4753) 
SUBSCRIBING PACKAGE: AUTHORIZATION/SUBSCRIPTION
 SUBSCRIBING DETAILS:   Calls linetag USR from the AVPR cross reference on file
 #8930.1 (installed by USR*1*36) 
  DATE ACTIVATED: AUG 21, 2015

NUMBER: 6079                            IA #: 6079
  DATE CREATED: JUL 31, 2014            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  NAME: CLINICAL REMINDERS API
 GENERAL DESCRIPTION:   VPS Kiosk calls MAIN^PXRM to retrieve the clinical
 reminders due now for a specific patient DFN.  VPS Kiosk input parameters
 VPSDFN and VPSIEN map to PXRM parameters DFN and PXRMITEM, respectively. VPS
 Kiosk reads Clinical Reminder data returned in ^TMP("PXRHM",$J).  
  STATUS: Withdrawn
KEYWORDS: VPS KIOSK
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

NUMBER: 6080                            IA #: 6080
  DATE CREATED: AUG 04, 2014            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        NAME: CLINICAL REMINDERS API
 GENERAL DESCRIPTION:   VPS Kiosk needs the use of CATREM^PXRMAPI0 to store
 CATEGORY Clinical Reminders to an array. VPS input to the routine is the
 patient DFN and the pointer to the VPS  array to receive the Clinical Reminder
 data returned. 
  STATUS: Active
KEYWORDS: VPS KIOSK
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
  DATE ACTIVATED: OCT 21, 2014

NUMBER: 6081                            IA #: 6081
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: AUG 05, 2014            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSAP
  NAME: Proxy User for HCPS             ID: XUSAP
 GENERAL DESCRIPTION:   The Consult/Request Tracking (GMRC) package can
 establish the Application Proxy HCPS,APPLICATION PROXY user.  This user will
 be used to establish an user environment when processing HL7 messages between
 Healthcare Claims Processing System (HCPS) and VistA.  The user will not have
 Access or Verify codes and will have a User Class of APPLICATION PROXY.  
  
 The GMRC application can use the API $$CREATE^XUSAP(proxyname, fmacc, options) 
 in patch GMRC*3*75 to create the user.  
  INPUT: proxyname = HCPS,APPLICATION PROXY 
         fmacc = FileMan Access Code 
         options = should be blank, user doesn't need any options 
  
 This ICR is for 1 year.  At the end of a year it should be re-evaluated to see 
 if a non-anonymous solution exists in VistA.  
  
  
  STATUS: Active                        DURATION: Next Version
  EXPIRATION DATE: AUG 06, 2015         GOOD ONLY FOR VERSION: GMRC 3.0
KEYWORDS: PROXY USER
COMPONENT/ENTRY POINT: $$CREATE(proxyname,fmac,options)
VARIABLES: proxyname                    TYPE: Input
 VARIABLES DESCRIPTION:   The name of the application proxy 
  
VARIABLES: fmac                         TYPE: Input
 VARIABLES DESCRIPTION:   The FileMan Access code,DUZ(0), to be associate with
 the application proxy 
  
VARIABLES: options                      TYPE: Input
 VARIABLES DESCRIPTION:   blank 
  
  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  DATE ACTIVATED: AUG 21, 2015

NUMBER: 6082                            IA #: 6082
  DATE CREATED: AUG 13, 2014
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMRCAPI
  NAME: Calls to GMRCAPI                ID: GMRCAPI
 GENERAL DESCRIPTION:   GMRCAPI contains calls to return data from the
 Request/Consultation file #123.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMRCAPI
KEYWORDS: IFC
COMPONENT/ENTRY POINT: GET(GMRCAR,GMRCDA,GMRCMED)
 COMPONENT DESCRIPTION:   Returns basic consult data and a list of linked
 results 
VARIABLES: GMRCAR                       TYPE: Both
 VARIABLES DESCRIPTION:   Results array, passed by reference, returns: 
   GMRCAR(0)    = Zero node of record 
   GMRCAR(1)    = CP procedure name, if applicable 
   GMRCAR(20)   = Reason for Request (wp) 
   GMRCAR(30)   = Provisional Dx 
   GMRCAR(30.1) = Prov Dx codes 
   GMRCAR(50,n) = ien;TIU(8925, or ien;MCAR(fnum, 
VARIABLES: GMRCDA                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Request/Consult file #123 
VARIABLES: GMRCMED                      TYPE: Input
 VARIABLES DESCRIPTION:   Set to 1 to include Medicine package results, else
 TIU only 
COMPONENT/ENTRY POINT: $$IFC(GMRCDA)
 COMPONENT DESCRIPTION:   Returns Inter-Facility Consult data as a string 
VARIABLES: GMRCDA                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Request/Consult file #123 
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Result of extrinsic function, returns "" or pieces: 
   1 - IFC REMOTE SERVICE NAME (#.131) 
   2 - REMOTE REQUESTOR PHONE (#.132) 
   3 - REMOTE REQUESTOR DIG PAGER (#.133) 
   5 - IFC ROLE (#.125) 
   6 - REMOTE ORDERING PROVIDER (#.126) 
   7 - REMOTE CONSULT FILE ENTRY (#.06) 
   8 - ROUTING FACILITY (#.07) 
COMPONENT/ENTRY POINT: ACT(GMRCAR,GMRCDA)
 COMPONENT DESCRIPTION:   Returns activity for a consult 
VARIABLES: GMRCAR                       TYPE: Both
 VARIABLES DESCRIPTION:   Results array, passed by reference, returns: 
   GMRCAR(n,0) = Zero node of record 
   GMRCAR(n,1) = Comment (wp) 
   GMRCAR(n,2) = Two node of record 
   GMRCAR(n,3) = Three node of record 
VARIABLES: GMRCDA                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Request/Consult file #123 
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP routine HMPDJ03 calls the function $$IFC^GMRCAPI to
 retrieve the inter-facility consult data as a string. HMP route HMPDJ03 also
 calls the ACT^GMRCAPI API to retrieve the activity for a consult.  
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: SEP 05, 2014

NUMBER: 6083                            IA #: 6083
  DATE CREATED: AUG 13, 2014
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUPRF2
  NAME: TIU GET DOCUMENT STATUS         ID: TIUPRF2
 GENERAL DESCRIPTION:   This API is used to retrieve the Status (8925.6 IEN) of
 a TIU DOCUMENT.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DOCUMENT
KEYWORDS: STATUS
COMPONENT/ENTRY POINT: GETSTAT
 COMPONENT DESCRIPTION:   This component is used to retrieve the Status (8925.6
 IEN) of a TIU DOCUMENT.  
VARIABLES: TIUY                         TYPE: Both
 VARIABLES DESCRIPTION:   TIUY is a single-valued variable sent by reference
 and returned as TIUY=STATIEN^STATNAME,where STATIEN is the file number in the
 TIU STATUS FILE 8925.6 of the status of the document.  
VARIABLES: TIUIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   TIUIEN is the IEN in file 8925 of the document.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   GMRC*3.0*75 creates an HL7 interface between the VistA
 Consult/Request Tracking software and the Healthcare Claims Processing System.
 GMRC*3.0*75 will create addenda to existing TIU documents.  
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added July 21, 2025 effective with CDSP*1*2, This RPC
 will return TIU document status to the various CDSP apps that will take 
 advantage to TIU documents 
  DATE ACTIVATED: SEP 11, 2014

NUMBER: 6084                            IA #: 6084
  DATE CREATED: AUG 14, 2014            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: MDC OBSERVATION UPDATE
 GENERAL DESCRIPTION:   The MDC OBSERVATION UPDATE protocol is used to notify
 other packages when observation data is updated.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP v.2.0 attaches HMP MDC EVENT protocol as an item to
 the MDC OBSERVATION UPDATE protocol to trigger unsolicited updates from VistA
 to JDS when observation data is updated.  
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: SEP 05, 2014

NUMBER: 6085                            IA #: 6085
  DATE CREATED: AUG 14, 2014            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: PSB EVSEND VPR
 GENERAL DESCRIPTION:   The PSB EVSEND VPR protocol notifies subscribing
 packages when a med order is administered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP PSB EVENTS protocol has been added as an item to
 the PSB EVSEND VPR protocol to trigger unsolicited updates from VistA to JDS
 when a med order is administered. 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: MAY 04, 2016

NUMBER: 6086                            IA #: 6086
  DATE CREATED: AUG 14, 2014
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: RA EVSEND OR
 GENERAL DESCRIPTION:   The RA EVSEND OR protocol is used to pass order
 messages from the Radiology/Nuclear Medicine package to other VistA
 applications.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP XQOR EVENTS protocol 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: SEP 05, 2014

NUMBER: 6087                            IA #: 6087
  DATE CREATED: AUG 14, 2014            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: LR7O CH EVSEND OR
 GENERAL DESCRIPTION:   The LR7O CH EVSEND OR protocol is used to pass order
 messages from the Laboratory package to other VistA applications.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP XQOR EVENTS protocol 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: SEP 05, 2014

NUMBER: 6088                            IA #: 6088
  FILE NUMBER: 8930                     GLOBAL ROOT: USR(8930)
  DATE CREATED: AUG 15, 2014
  CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VPR READ OF USER CLASS
  ID: USR(8930)
GLOBAL REFERENCE: USR(8930,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
FIELD NUMBER: .03                       FIELD NAME: ACTIVE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: DISPLAY NAME
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: USR(8930,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SUBCLASS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: USR(8930,'AD'
FIELD NUMBER: .03                       FIELD NAME: ACTIVE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Virtual Patient Record (VPR) needs the User Classes
 to accurately apply ASU business rules in the Health Management Platform (HMP)
 client.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: MAY 09, 2016

NUMBER: 6089                            IA #: 6089
  FILE NUMBER: 8930.1                   GLOBAL ROOT: USR(8930.1)
  DATE CREATED: AUG 15, 2014
  CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VPR READ OF ASU RULES
  ID: USR(8930.1)
GLOBAL REFERENCE: USR(8930.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DOCUMENT DEFINITION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: ACTION
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: USER CLASS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: AND FLAG
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: USER ROLE
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: USR(8930.1,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Virtual Patient Record (VPR) needs the
 Authorization/Subscription rules to accurately apply ASU business rules in the
 Health Management Platform (HMP) client.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expired on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational 
 patch outlining the steps for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: SEP 05, 2014

NUMBER: 6090                            IA #: 6090
  DATE CREATED: AUG 20, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: OR EVSEND FH
 GENERAL DESCRIPTION:   This is the event invoked by CPRS when a new order, or
 action to an order, is placed to the Dietetics 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 Dietetics as defined in the 
 'OE/RR Version 3 Package Interface Specifications' document.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DIETETICS
 SUBSCRIBING DETAILS:   Dietetics listener protocol is FH RECEIVE.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   VPR listener protocol is VPR NA EVENTS to be
 distributed in VPR*1*3.  
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   Emergency Department listener protocol is EDP OR
 MONITOR.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   The protocol for HMP is HMP NA EVENTS 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: SEP 25, 2015

NUMBER: 6091                            IA #: 6091
  DATE CREATED: AUG 20, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: OR EVSEND LRCH
 GENERAL DESCRIPTION:   This is the event invoked by CPRS when a new order, or
 action to an order, is placed to the Laboratory 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 Lab as defined in the 'OE/RR
 Version 3 Package Interface Specifications' document.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   Listener protocol for Lab is LR70 CH RECEIVE.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Listener protocol for VPR is VPR NA EVENTS to be added
 by VPR*1*3.  
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   Listener protocol for Emergency Department is EDP OR
 MONITOR.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   The protocol for HMP is HMP NA EVENTS 
  
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: SEP 25, 2015

NUMBER: 6092                            IA #: 6092
  DATE CREATED: AUG 20, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: OR EVSEND ORG
 GENERAL DESCRIPTION:   This is the event invoked by CPRS when a new order, or
 action to an order, is placed to the OE/RR 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 OE/RR as defined in the 'OE/RR
 Version 3 Package Interface Specifications' document.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Listener protocol for VPR is VPR XQOR EVENTS to be
 added by VPR*1*3.  
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   Listener protocol for Emergency Department is EDP
 MONITOR.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   The protocol for HMP is HMP XQOR EVENTS 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: SEP 25, 2015

NUMBER: 6093                            IA #: 6093
  DATE CREATED: AUG 20, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: OR EVSEND PS
 GENERAL DESCRIPTION:   This is the event invoked by CPRS when a new order, or
 action to an order, is placed to the Pharmacy packages.  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 Pharmacy as defined in the 'OE/RR
 Version 3 Package Interface Specifications' document.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   Listener protocol for Pharmacy Data Management is PS
 RECEIVE OR.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Listener protocol for VPR is VPR NA EVENTS to be added
 by VPR*1*3.  
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   Listener protocol for Emergency Department is EDP OR
 MONITOR.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   The protocol for HMP is HMP NA EVENTS 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   The protocol is PSIVARH PHARMACY to be added by
 PSJ*5.0*325 
  DATE ACTIVATED: SEP 25, 2015

NUMBER: 6094                            IA #: 6094
  DATE CREATED: AUG 20, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: OR EVSEND RA
 GENERAL DESCRIPTION:   This is the event invoked by CPRS when a new order, or
 action to an order, is placed to the Radiology/NM 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 Radiology as defined in the 
 'OE/RR Version 3 Package Interface Specifications' document.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Listener protocol for Radiology is RA RECEIVE.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Listener protocol for VPR is VPR NA EVENTS to be added
 by VPR*1*3.  
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   Listener protocol for Emergency Department is EDP OR
 MONITOR.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Protocol for HMP is HMP NA EVENTS 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: SEP 25, 2015

NUMBER: 6095                            IA #: 6095
  DATE CREATED: AUG 20, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: OR EVSEND VPR
 GENERAL DESCRIPTION:   This is the event invoked by CPRS when an action to an
 order occurs that does not trigger any other event, to notify the Virtual
 Patient Record.  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 action as defined in the 'OE/RR
 Version 3 Package Interface Specifications' document.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Listener protocol for VPR is VPR XQOR EVENTS to be
 added by VPR*1*3.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Protocol for eHMP is HMP XQOR EVENTS 
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: SEP 25, 2015

NUMBER: 6096                            IA #: 6096
  DATE CREATED: AUG 20, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: OR EVSEND DGPM
 GENERAL DESCRIPTION:   This is the event invoked by CPRS when an order is
 placed that can update patient movements or assign providers, to notify the
 Registration 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 information as defined in the 'OE/RR 
 Version 3 Package Interface Specifications' document.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   Registration listener protocol is DGPM PROVIDER UPDATE
 EVENT.  
  DATE ACTIVATED: SEP 25, 2015

NUMBER: 6097                            IA #: 6097
  DATE CREATED: AUG 20, 2014            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: FH EVSEND OR
 GENERAL DESCRIPTION:   The FH EVSEND OR protocol is used to pass order
 messages from the Dietetics package to other VistA applications.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Listener protocols are OR RECEIVE and OCX ORDER CHECK
 HL7 RECIEVE.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Listener protocol is VPR XQOR EVENTS, added with
 VPR*1*3.  
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   Listener protocol is EDP MONITOR.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP V.2.0 attaches HMP XQOR EVENTS protocol as an item
 to the FH EVSEND OR protocol to trigger unsolicited updates from VistA to JDS
 when dietetics orders are updated.  
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
  DATE ACTIVATED: JUL 10, 2017

NUMBER: 6098                            IA #: 6098
  FILE NUMBER: 408.31                   GLOBAL ROOT: 'DGMT(408.31
  DATE CREATED: AUG 24, 2014            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MEANS TEST STATUS file
  ID: 'DGMT(408.31
GLOBAL REFERENCE: 'DGMT(408.31,D0,0) =>HARDSHIP FLAG
FIELD NUMBER: .2                        FIELD NAME: HARDSHIP?
  LOCATION: 0;20                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: 'DGMT(408.31,C, =>PATIENT CROSS-REFERENCE
 GENERAL DESCRIPTION:   VPS Kiosks has a need to provide a patient's HARDSHIP
 means test status to the VetLink application. VPS RPC, VPS ENHANCED GET
 PATIENT DEMOGRAPHICS, uses the "C" cross-reference of ^DGMT(408.31 to find a 
 patient's means test, then reads field .2 (0;20) of the patient's entry to
 obtain the patient's hardship status.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VPS
KEYWORDS: MEANS TEST STATUS
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
  DATE ACTIVATED: JUL 22, 2015

NUMBER: 6099                            IA #: 6099
  FILE NUMBER: 27.11                    GLOBAL ROOT: 'DGEN(27.11,
  DATE CREATED: AUG 24, 2014            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ PATIENT ENROLLMENT (#27.11) FILE
  ID: 'DGEN(27.11,
GLOBAL REFERENCE: 'DGEN(27.11,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ENROLLMENT DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: ENROLLMENT STATUS
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .08                       FIELD NAME: EFFECTIVE DATE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: ENROLLMENT PRIORITY
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 50.01                     FIELD NAME: ELIGIBILITY CODE
  LOCATION: E;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to MAS ELIGIBILITY CODE FILE #8.1 
FIELD NUMBER: 50.02                     FIELD NAME: SERVICE CONNECTED
  LOCATION: E;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Y/N FLAG indicating if patient has a service connected
 disability.  
FIELD NUMBER: 50.03                     FIELD NAME: SERVICE CONNECTED PERCENTAGE
  LOCATION: E;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 50.13                     FIELD NAME: SOUTHWEST ASIS CONDITIONS
  LOCATION: E;13                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   FLAG indicating if SW Asia conditions apply.  
 GENERAL DESCRIPTION:   VPS Kiosks has a need to provide patient eligibility
 information to the VetLink application.  
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: DBIA2462
KEYWORDS: 'DGEN(27.11
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
  DATE ACTIVATED: APR 27, 2015

NUMBER: 6100                            IA #: 6100
  DATE CREATED: AUG 25, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWOR DETAIL
 GENERAL DESCRIPTION:   VA Point of Service (Kiosks) has a need to provide the
 detailed information for a patient's lab orders to VetLink.  VA Point of
 Service (Kiosks) will pass the order IEN and patient DFN as parameters to 
 retrieve the order details.  
  
 Input:  ORDIEN ; order identifier 
         DFN    ; patient identifier 
  
 TAG^ROUTINE: DETAIL^ORWOR 
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: ORWOR
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
  DATE ACTIVATED: SEP 30, 2014

NUMBER: 6101                            IA #: 6101
  DATE CREATED: AUG 25, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORPR07
  NAME: ORPRO7 ORDOC                    ID: ORPR07
 GENERAL DESCRIPTION:   Returns the ordering provider for a patient order.  
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: ORPR07
KEYWORDS: ORDOC
COMPONENT/ENTRY POINT: ORDOC
VARIABLES: ORDIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Order internal entry number in file #100 
VARIABLES: ACTIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Order action internal entry number 
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service Kiosks has a need to provide the
 ordering provider of a patient's lab order to VetLink.  
  DATE ACTIVATED: OCT 29, 2014

NUMBER: 6102                            IA #: 6102
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100
  DATE CREATED: AUG 25, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ORDER FILE READ
  ID: OR(100
GLOBAL REFERENCE: OR(100,D0,0)
FIELD NUMBER: 6                         FIELD NAME: PATIENT LOCATION
  LOCATION: (0;6)                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Hospital location from which the order originated.  
GLOBAL REFERENCE: OR(100,D0,4)
FIELD NUMBER: 33                        FIELD NAME: PACKAGE REFERENCE
  LOCATION: (4;E1)                      ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to detailed order information in the order
 package.  
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: ORDER
KEYWORDS: #100
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service Kiosks, patch VPS*1*4, has a need
 to read field #6, PATIENT LOCATION,and field #33, PACKAGE REFERENCE, in ORDER
 file #100 to provide the hospital location and detailed order information for
 a patient order to VetLink.  
  DATE ACTIVATED: AUG 29, 2014

NUMBER: 6103                            IA #: 6103
  FILE NUMBER: 777                      GLOBAL ROOT: HLA(
  DATE CREATED: SEP 08, 2014            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: HLO MESSAGE BODY (#777) direct global read
  ID: HLA(
GLOBAL REFERENCE: HLA(D0,1,D1,
FIELD NUMBER: 1                         FIELD NAME: SEGMENTS (NOT BATCHED)
  LOCATION: 1;0                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The VistA Health Level Seven application will grant
 VistA Imaging the privilege to read the HLO MESSAGE BODY (#777) global
 directly.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HLO - MAG private
KEYWORDS: MAG - HLO private
KEYWORDS: Imaging - Health Level Seven
KEYWORDS: Health Level Seven - Imaging
KEYWORDS: HLA global (#777)
KEYWORDS: HLO MESSAGE BODY HLA( global
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   The Imaging software is targeting the SEGMENTS (NOT
 BATCHED) sub-file.  
  
 The segments read from the HLO MESSAGE BODY are saved into a local array for
 processing.  
  DATE ACTIVATED: JAN 12, 2015

NUMBER: 6104                            IA #: 6104
  FILE NUMBER: 69.86                    GLOBAL ROOT: LRHY(69.86
  DATE CREATED: SEP 23, 2014            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: LRHY GET SITES RPC
  ID: LRHY(69.86
GLOBAL REFERENCE: LRHY(69.86,D0,0
FIELD NUMBER: NAME
FIELD NUMBER: .01                       FIELD NAME: NAME
  ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: LRHY(69.86,D0,2,0
FIELD NUMBER: 2                         FIELD NAME: LAB TEST (TO EXCLUDE)
  ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   
                         NAME: LRHY GET SITES                    TAG: GETSITES 
                           ROUTINE: LRHYRP01                     RETURN VALUE 
                         TYPE: ARRAY 
                          DESCRIPTION:   
                          This RPC will return all Howdy Sites 
               USAGE: Controlled Subscri  ENTERED: SEP 23,2014 
              STATUS: Pending             EXPIRES: 
            DURATION:                     VERSION: 
         DESCRIPTION:                        TYPE: Remote Procedure 
  STATUS: Active
KEYWORDS: LRHY
KEYWORDS: Howdy
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service Kiosks needs to use LRHY GET SITES,
 implemented in LRHYRP01 and included in patch LR*5.2*447, to return the list
 of Howdy sites at a facility to VetLink.  
  DATE ACTIVATED: OCT 02, 2014

NUMBER: 6105                            IA #: 6105
  FILE NUMBER: 69.01                    GLOBAL ROOT: LRO(69,D0,1,D1,4
  DATE CREATED: SEP 23, 2014            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: File
  NAME: 69.01 SPECIMEN # SUB-FILE       ID: LRO(69,D0,1,D1,4
 GENERAL DESCRIPTION:   The laboratory Specimen # sub-file.  
  STATUS: Withdrawn
KEYWORDS: LRO
KEYWORDS: LRHY
KEYWORDS: Howdy
KEYWORDS: VPS
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (Kiosks) requires READ access to
 the Specimen # Sub-file #69.01 to provide Howdy Traditional and PPOC
 functionality to VetLink.  

NUMBER: 6106                            IA #: 6106
  FILE NUMBER: 391.91                   GLOBAL ROOT: DGCN(391.91
  DATE CREATED: SEP 24, 2014            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  NAME: DGCN(391.91 GET DFN FROM EDIPI  ID: DGCN(391.91
GLOBAL REFERENCE: DGCN(391.91,D0,0
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DGCN(391,91,B
GLOBAL REFERENCE: DGCN(391.91,D0,2
FIELD NUMBER: 11                        FIELD NAME: SOURCE ID
  LOCATION: 2;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DGCN(391.91,ASID,EDIPI,VICFAC,0
 GENERAL DESCRIPTION:   Treating Facility List where patients have had
 treatment.  
  STATUS: Withdrawn
KEYWORDS: VPS
KEYWORDS: DGCN
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (Kiosks) has a need to return a
 patient's DFN to VetLink for patient's identifying with EDIPI.  
 .

NUMBER: 6107                            IA #: 6107
  DATE CREATED: SEP 24, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWPT1 PCDETAIL
 GENERAL DESCRIPTION:   Following are details of the RPC: 
     
     NAME: ORWPT1 PRCARE                     TAG: PRCARE 
      ROUTINE: ORWPT1                       RETURN VALUE TYPE: SINGLE VALUE 
     DESCRIPTION:   
  
  
 Return primary care information for a patient in the format: 
       VAL=Primary Care Team^Primary Care Provider^Attending^MH Treatment 
           Coordinator 
     INPUT PARAMETER: dfn 
    Return primary care information for a patient in the format: 
      VAL=Primary Care Team^Primary Care Provider^Attending 
  
  TAG^ROUTINE: PRCARE^ORWPT1 
  STATUS: Withdrawn
KEYWORDS: ORWPT1
KEYWORDS: PCDETAIL
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service Kiosks is requesting approval of
 the new ICR xxx.   VA Point of Service Kiosks has a need to use
 PCDETAIL^ORWPT1 to return a patient's primary care detailed information to
 VetLink.  VA Point of Service Kiosks will use this ICR in VPS*1*4 patch.  

NUMBER: 6108                            IA #: 6108
  DATE CREATED: SEP 24, 2014            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: LRHY GET BINGO BOARDS
 GENERAL DESCRIPTION:   ABC 
  STATUS: Pending
KEYWORDS: Howdy
KEYWORDS: VPS
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

NUMBER: 6109                            IA #: 6109
  DATE CREATED: SEP 25, 2014            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: LRHY GET SITE PRINTERS
 GENERAL DESCRIPTION:   NAME: LRHY GET SITE PRINTERS  TAG: GETHYPRT             
            ROUTINE: LRHYRP01 
   RETURN VALUE TYPE: ARRAY 
  DESCRIPTION:   
  This RPC will return all Howdy Printers for a given Howdy Site INPUT
 PARAMETER: LRSITE                 PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 15               REQUIRED: YES 
   SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Howdy Site IEN 
  STATUS: Active
KEYWORDS: Howdy
KEYWORDS: VPS
KEYWORDS: LRHY
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service Kiosks needs to use LRHY GET SITE
 PRINTERS, implemented in LRHYRP01 and included in patch LR*5.2*447, to return
 the list of Howdy printers at a facility.  
  DATE ACTIVATED: OCT 02, 2014

NUMBER: 6110                            IA #: 6110
  DATE CREATED: SEP 25, 2014            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: LRHY GET BINGO BOARDS
 GENERAL DESCRIPTION:   NAME: LRHY GET BINGO BOARDS             TAG: GETBINGO 
   ROUTINE: LRHYRP01                     RETURN VALUE TYPE: ARRAY 
  DESCRIPTION:   
  This RPC will return Howdy Bingo Board Devices for a given Howdy Site INPUT
 PARAMETER: LRSITE                 PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 30               REQUIRED: YES 
   SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Howdy Site 
  STATUS: Pending
KEYWORDS: Howdy
KEYWORDS: VPS
KEYWORDS: LRHY
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service Kiosks needs to use LRHY GET BINGO
 BOARDS, implemented in LRHYRP01 and included in patch LR*5.2*447, to return
 the list of Howdy Bingo Boards at a facility.  

NUMBER: 6111                            IA #: 6111
  DATE CREATED: SEP 25, 2014            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: LRHY GET BINGO BOARDS
 GENERAL DESCRIPTION:   
  
 NAME: LRHY GET BINGO BOARDS             TAG: GETBINGO 
   ROUTINE: LRHYRP01                     RETURN VALUE TYPE: ARRAY 
  DESCRIPTION:   
  This RPC will return Howdy Bingo Board Devices for a given Howdy Site INPUT
 PARAMETER: LRSITE                 PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 30               REQUIRED: YES 
   SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Howdy Site 
  STATUS: Active
KEYWORDS: Howdy
KEYWORDS: VPS
KEYWORDS: LRHY
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service Kiosks needs to use LRHY GET BINGO
 BOARDS, implemented in LRHYRP01 and included in patch LR*5.2*447, to return
 the list of Howdy Bingo boards at a facility.  
  DATE ACTIVATED: OCT 02, 2014

NUMBER: 6112                            IA #: 6112
  DATE CREATED: SEP 25, 2014            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: LRHY PATIENT CHECK-IN
 GENERAL DESCRIPTION:   NAME: LRHY PATIENT CHECK-IN 
   TAG: PTCHKIN                          ROUTINE: LRHYRP02 
   RETURN VALUE TYPE: SINGLE VALUE 
  DESCRIPTION:   
  This RPC will return result of Howdy Patient Check-In.  INPUT PARAMETER:
 LRHYPTYP               PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 7                REQUIRED: YES 
   SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Patient ID Type. Valid Value: SSN, DFN, ICN, or VIC/CAC INPUT PARAMETER:
 LRHYPTID               PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 15               REQUIRED: YES 
   SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  Patient ID for the type.  INPUT PARAMETER: LRHYSITE               PARAMETER
 TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 5                REQUIRED: YES 
   SEQUENCE NUMBER: 3 
  DESCRIPTION:   
  Howdy Site IEN INPUT PARAMETER: LRHYTYPE               PARAMETER TYPE:
 LITERAL 
  STATUS: Active
KEYWORDS: Howdy
KEYWORDS: VPS
KEYWORDS: LRHY
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service Kiosks needs to use LRHY PATIENT
 CHECK-IN, implemented in LRHYRP02 and included in patch LR*5.2*447, to do a
 Howdy patient check-in laboratory at a facility.  
  DATE ACTIVATED: OCT 02, 2014

NUMBER: 6113                            IA #: 6113
  FILE NUMBER: 811.9                    GLOBAL ROOT: PXD(811.9
  DATE CREATED: SEP 25, 2014            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: File
  NAME: 811.9                           ID: PXD(811.9
GLOBAL REFERENCE: PXD(811.9,D0
FIELD NUMBER: 1.2                       FIELD NAME: PRINT NAME
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.6                       FIELD NAME: INACTIVE FLAG
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.91                      FIELD NAME: PRIORITY
  LOCATION: 0;10                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PXD(811.9,D0,100
FIELD NUMBER: 103                       FIELD NAME: USAGE
  LOCATION: 100;4                       ACCESS: Read w/Fileman
  STATUS: Withdrawn
KEYWORDS: VPS
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (Kiosks) has a need to read the
 reminder PRINT NAME, INACTIVE FLAG, PRIORITY AND USAGE from the REMINDER
 DEFINITION file #811.9. These fields are used by the VPSPTCR routine to
 provide System and (optionally) Location level clinical reminders to VetLink.  

NUMBER: 6114                            IA #: 6114
  FILE NUMBER: 9000011                  GLOBAL ROOT: AUPNPROB(
  DATE CREATED: SEP 26, 2014            CUSTODIAL PACKAGE: PROBLEM LIST
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: AUPNPROB REFERENCES
  ID: AUPNPROB(
GLOBAL REFERENCE: AUPNPROB(DA,1)
FIELD NUMBER: 1.01
  FIELD NAME: POINTER TO EXPRESSION FILE (#757.01)
  LOCATION: 1;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VA Point of Service (Kiosks) reference to PROBLEM file
 #9000011.  
  STATUS: Active
KEYWORDS: AUPNPROB
KEYWORDS: VPS
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (Kiosks) needs to provide the
 problem description text from the Expression file for a patient's problem. 
 Kiosks will use the pointer to the Expression file entry provided in the
 PROBLEM file to read and return the Expression file description information to
 the VetLink staff-facing application.  
  DATE ACTIVATED: NOV 05, 2014

NUMBER: 6115                            IA #: 6115
  FILE NUMBER: 354                      GLOBAL ROOT: IBA(354
  DATE CREATED: SEP 26, 2014            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: File
  NAME: IBA 354                         ID: IBA(354
GLOBAL REFERENCE: IBA(354,B,DFN)
FIELD NUMBER: .04                       FIELD NAME: COPAY INCOME EXEMPTION
  LOCATION: 0;4                         ACCESS: Read w/Fileman
  STATUS: Withdrawn
KEYWORDS: VPS
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (Kiosks) needs to provide a
 patient's copay exemption status to the staff-facing VetLink application.  

NUMBER: 6116                            IA #: 6116
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123
  DATE CREATED: SEP 26, 2014
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: 123 REFERENCES
  ID: GMR(123
GLOBAL REFERENCE: GMR(123,D0,0)
FIELD NUMBER: .001                      FIELD NAME: CONSULT IEN
  ACCESS: Read w/Fileman
FIELD NUMBER: .01                       FIELD NAME: FILE ENTRY DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: OE/RR FILE NUMBER
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DATE OF REQUEST
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PROCEDURE/REQUEST TYPE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: URGENCY
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: CPRS STATUS
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SENDING PROVIDER
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: REQUEST TYPE
  LOCATION: 0;17                        ACCESS: Read w/Fileman
FIELD NUMBER: 17                        FIELD NAME: CLINICALLY INDICATED DATE
  LOCATION: 0;24                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the date by which it is clinically appropriate to
 complete the consult. GMRC*3.0*81 released on 3/8/16 changed the field name
 from Earliest Date to Clinically Indicated Date.  
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: GMRC
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (Kiosks) RPC GET ENHANCED PATIENT
 DEMOGRAPHICS needs to read patient consult information from the CONSULTATION
 file #123.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Added 11/6/19 for access to CONSULT IEN (field .001 of
 GMR(123,D0,0) global reference, effective with RA*5*161.  
SUBSCRIBING PACKAGE: DENTAL
 SUBSCRIBING DETAILS:   Added 09/22/26, effective with DENT*1.2*96, Dental
 Record Manager Plus (DRM Plus) will be checking if a provided IEN is a valid 
 entry in file #123.  
  DATE ACTIVATED: OCT 02, 2014

NUMBER: 6117                            IA #: 6117
  FILE NUMBER: 123.5                    GLOBAL ROOT: GMR(123.5
  DATE CREATED: SEP 26, 2014
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Controlled Subscription        TYPE: File
  NAME: 123.5 REFERENCES                ID: GMR(123.5
GLOBAL REFERENCE: GMR(123.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: SERVICE NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Withdrawn
KEYWORDS: VPS
KEYWORDS: GMRC
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service Kiosks has a need to return the
 service name associated with an identified patient consult to VetLink.  

NUMBER: 6118                            IA #: 6118
  DATE CREATED: OCT 01, 2014
  CUSTODIAL PACKAGE: VA POINT OF SERVICE (KIOSKS)
  USAGE: Supported                      TYPE: Routine
  ROUTINE: VPSRPC1                      NAME: VPS VALIDATE PATIENT ID
  ID: VPSRPC1
 GENERAL DESCRIPTION:   The VPS Validate Patient ID is an API that accepts a
 patient identifier type-value pair and returns the DFN of the patient.  Valid
 patient identifier types are SSN, DFN, ICN, and VIC/CAC.  
  
 The API checks the format of the patient identifier value to verify that the
 identifier value conforms to the expected format for the specified identifier
 type.  If the value format does not match the identifier type format, an error
 message is returned. 
  
 The patient  identifier type is used to select a lookup routine to use to 
 obtain the DFN corresponding to the type-value pair submitted.  If the DFN is
 found in PATIENT file #2, the DFN is returned, otherwise a PATIENT NOT FOUND
 error message is returned.  
  STATUS: Withdrawn
KEYWORDS: VPS
KEYWORDS: DFN
KEYWORDS: VIC/CAC
KEYWORDS: ICN
KEYWORDS: SSN
COMPONENT/ENTRY POINT: VALIDATE
VARIABLES: VPSTYP                       TYPE: Input
 VARIABLES DESCRIPTION:   VPSTYP is the patient identifier type is required and
 must be one of the follow free text values: SSN, DFN, ICN, or VIC/CAC 
VARIABLES: VPSNUM                       TYPE: Input
 VARIABLES DESCRIPTION:   VPSNUM is required and is the patient identifier
 value of the same type as the identifier type specified.  
VARIABLES: DFN                          TYPE: Output
 VARIABLES DESCRIPTION:   DFN is the IEN of the patient's entry in PATIENT file
 #2.  

NUMBER: 6119                            IA #: 6119
  DATE CREATED: OCT 01, 2014
  CUSTODIAL PACKAGE: CLINICAL CASE REGISTRIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ROR LIST HOSPITAL LOCATION RPC  STATUS: Withdrawn
KEYWORDS: ROR
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service Kioks  has a need to return to
 VetLink a list of hospital locations and their assigned institution and
 division IENs that meet the active, inactive and type criteria parameters.  

NUMBER: 6120                            IA #: 6120
  DATE CREATED: OCT 02, 2014            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMTAXD
  NAME: REBUILD TAXONOMY AUID INDEX     ID: PXRMTAXD
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: TAXONOMY AUID INDEX
COMPONENT/ENTRY POINT: RBLDUID
 COMPONENT DESCRIPTION:   There are no input or output arguments to this
 routine. It checks all taxonomies and rebuilds the "AUID" index if necessary.  
  
SUBSCRIBING PACKAGE: LEXICON UTILITY
 SUBSCRIBING DETAILS:   When a code set is updated the Clinical Reminders
 "AUID" index needs to be rebuilt. Until the change can be made in the Clinical
 Reminders code that is invoked by the Lexicon update protocol, Lexicon will
 make sure the rebuild takes place by calling RBLDUID^PXRMTAXD from their
 post-init.  
  
  DATE ACTIVATED: OCT 03, 2014

NUMBER: 6121                            IA #: 6121
  FILE NUMBER: 19.2                     GLOBAL ROOT: DIC(19.2
  DATE CREATED: OCT 03, 2014            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: REMOVE SCHEDULED OPTIONS FROM #19.2
  ID: DIC(19.2
 GENERAL DESCRIPTION:   Scheduling (PCMM, PCMM WEB, PAIT, ACRP, and EWL)
 requests permission to lookup and delete entries in the Option Scheduling
 (19.2) File for the Options - SCMC PCMM NIGHTLY TASK, SCMC PCMM HL7 NIGHTLY
 TASK, SD-PAIT TASKED TRANSMISSION, SCDX AMCAR NIGHTLY XMIT, SD WAIT LIST TRANS
 TO AAC. Task SCMC PCMM NIGHTLY TASK will no longer be required to run on
 VistA; it will be performed by the new PCMM Web application.  SCMC PCMM HL7
 NIGHTLY TASK, SD-PAIT TASKED TRANSMISSION, SCDX AMCAR NIGHTLY XMIT, SD WAIT
 LIST TRANS TO AAC have been replaced by the Corporate Data Warehouse (CDW).
 This will be done by a post-install routine using the ^DIK Fileman API in
 patch SD*5.3*603, SD*5.3*624, SD*5.3*638, SD*5.3*639, AND SD*5.3*640.  (PCMM,
 PCMM WEB, PAIT, ACRP, and EWL functionality falls under the Scheduling
 namespace.) 
  
 AMIE and CAPRI Options - DVBA C PURGE 2507 and DVBA REGIONAL PURGING PROGRAM 
 will also use this agreement to be deleted from the Option Scheduling File. 
 This will be done by a post-install routine using the ^DIK Fileman API in
 patch DVBA*2.7*195.  
  
 This ICR is only valid for SD*5.3*603, SD*5.3*624, SD*5.3*638, SD*5.3*639, 
 SD*5.3*640 and DVBA*2.7*195.  
  
  
  
  STATUS: Active
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   This request is for patches SD*5.3*603, SD*5.3*624,
 SD*5.3*638, SD*5.3*639, SD*5.3*640 and DBVA*2.7*195.  See details below.  
  
  
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   
  
  DATE ACTIVATED: JAN 29, 2015

NUMBER: 6122                            IA #: 6122
  FILE NUMBER: 778                      GLOBAL ROOT: HLB('QUEUE','OUT')
  DATE CREATED: NOV 03, 2014            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HLB OUT POINTER X-REF
  ID: HLB('QUEUE','OUT')
GLOBAL REFERENCE: HLB('QUEUE','OUT',LINKPORT,QUEUE)
 GENERAL DESCRIPTION:   VA POINT OF SERVICE (KIOSKS) is providing patient
 appointment status using HL7 messaging, and needs to use the
 ^HLB("QUEUE","OUT",LINKPORT,QUEUE)  global reference to lock and unlock an
 active VPS message queue.  
  STATUS: Active
KEYWORDS: HLB
KEYWORDS: VPS
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   When adding a new HL7 message to a VPS outbound queue,
 VPS needs to lock and unlock access to the outbound queue using the
 ^HLB("QUEUE","OUT", LINKPORT,QUEUE) global reference.   The LINKPORT
 identifies the VPS HL Logical Link and QUEUE is the name of the VPS queue.  
  DATE ACTIVATED: MAR 20, 2015

NUMBER: 6123                            IA #: 6123
  DATE CREATED: NOV 03, 2014            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: HLOCLNT                      NAME: DOWORK HLOCLNT
  ID: HLOCLNT                           STATUS: Withdrawn
KEYWORDS: DOWORK
KEYWORDS: HLOCLNT
KEYWORDS: VPS
COMPONENT/ENTRY POINT: DOWORK
VARIABLES: WORK                         TYPE: Input
 VARIABLES DESCRIPTION:   ARRAY POPULATED AS FOLLOWS: 
  
         WORK("QUEUE") = name of the VPS message queue 
         WORK("LINK") = name of the link;link port 
  
 The WORK("LINK") array element is a composite value.  The component elements
 are separated with a semi-colon.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) is providing patient
 appointment status using HL7 messaging.  Kiosks is using DOWORK^HLOCLNT to
 send an A01 ADT message on the VPS HL7 queue to the Vetlink HL7 server.  VPS
 will pass an array populated with the queue name and link name and port to
 connect to the Vista HL7 server and send the A08 message on the queue.  

NUMBER: 6124                            IA #: 6124
  DATE CREATED: NOV 05, 2014            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: HLOT                         NAME: CLOSE HLOT
  ID: HLOT                              STATUS: Withdrawn
KEYWORDS: HL7
KEYWORDS: HLOT
KEYWORDS: VPS
COMPONENT/ENTRY POINT: CLOSE
VARIABLES: .HLCSTATE                    TYPE: Both
 VARIABLES DESCRIPTION:   HLCSTATE is a local array passed by reference.  The
 array is populated by a previous call to DOWORK^HLOCLNT.  
  
 The action of CLOSE^HLOCLNT is to set the value of HLCSTATE("CONNECTED") to 0. 
 
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) is providing patient
 appointment status using HL7 messaging.  Upon transmission of a message, VPS
 resets the state of the HL7 server connection by calling CLOSE^HLOT.  VPS
 passes by reference the array HLCSTATE populated by a call to DOWORK^HLOCLNT. 
 The value of the HLCSTATE("CONNECTED") element is set to 0 by CLOSE^HLOT.  

NUMBER: 6125                            IA #: 6125
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(D0
  DATE CREATED: NOV 06, 2014            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ PATIENT FILE FIELDS
  ID: DPT(D0
GLOBAL REFERENCE: DPT(D0
FIELD NUMBER: .3612                     FIELD NAME: ELIGIBILITY STATUS DATE
  LOCATION: .361;2                      ACCESS: Read w/Fileman
FIELD NUMBER: .1221                     FIELD NAME: TEMPORARY ADDRESS PROVINCE
  LOCATION: .122;1                      ACCESS: Read w/Fileman
FIELD NUMBER: .14105                    FIELD NAME: CONFIDENTIAL ADDRESS ACTIVE
  LOCATION: .141;9                      ACCESS: Read w/Fileman
FIELD NUMBER: .323                      FIELD NAME: PERIOD OF SERVICE
  LOCATION: .32;3                       ACCESS: Read w/Fileman
FIELD NUMBER: 1100.01                   FIELD NAME: FUGITIVE FELON FLAG
  LOCATION: FFP;1                       ACCESS: Read w/Fileman
FIELD NUMBER: .305                      FIELD NAME: UNEMPLOYABLE
  LOCATION: .3;5                        ACCESS: Read w/Fileman
FIELD NUMBER: .525                      FIELD NAME: POW STATUS INDICATED?
  LOCATION: .52;5                       ACCESS: Read w/Fileman
FIELD NUMBER: .526                      FIELD NAME: POW CONFINEMENT LOCATION
  LOCATION: .52;6                       ACCESS: Read w/Fileman
FIELD NUMBER: .527                      FIELD NAME: POW FROM DATE
  LOCATION: .52;7                       ACCESS: Read w/Fileman
FIELD NUMBER: .528                      FIELD NAME: POW THROUGH DATE
  LOCATION: .52;8                       ACCESS: Read w/Fileman
FIELD NUMBER: .529                      FIELD NAME: POW STATUS VERIFIED
  LOCATION: .52;9                       ACCESS: Read w/Fileman
FIELD NUMBER: .531                      FIELD NAME: CURRENT PH INDICATOR
  LOCATION: .53;1                       ACCESS: Read w/Fileman
FIELD NUMBER: .532                      FIELD NAME: CURRENT PH STATUS
  LOCATION: .53;2                       ACCESS: Read w/Fileman
FIELD NUMBER: .533                      FIELD NAME: CURRENT PH REMARKS
  LOCATION: .53;3                       ACCESS: Read w/Fileman
FIELD NUMBER: .153                      FIELD NAME: MISSING PERSON DATE
  LOCATION: .15;3                       ACCESS: Read w/Fileman
FIELD NUMBER: .16                       FIELD NAME: MISSING OR INELIGIBLE
  LOCATION: .16;0                       ACCESS: Read w/Fileman
FIELD NUMBER: .1657                     FIELD NAME: MISSING PERSON TWX SOURCE
  LOCATION: INE;7                       ACCESS: Read w/Fileman
FIELD NUMBER: .1658                     FIELD NAME: MISSING PERSON TWX CITY
  LOCATION: INE;8                       ACCESS: Read w/Fileman
FIELD NUMBER: .1659                     FIELD NAME: MISSING PERSON TWX STATE
  LOCATION: INE;9                       ACCESS: Read w/Fileman
FIELD NUMBER: .3012                     FIELD NAME: SC AWARD DATE
  LOCATION: .3;12                       ACCESS: Read w/Fileman
FIELD NUMBER: .3014
  FIELD NAME: EFFECTIVE DATE COMBINE SC% EVAL
  LOCATION: .3;14                       ACCESS: Read w/Fileman
FIELD NUMBER: .32102
  FIELD NAME: AGENT ORANGE EXPOSURE INDICATED
  LOCATION: .321;2                      ACCESS: Read w/Fileman
FIELD NUMBER: .32107
  FIELD NAME: AGENT ORANGE REGISTRATION DATE
  LOCATION: .321;7                      ACCESS: Read w/Fileman
FIELD NUMBER: .32109
  FIELD NAME: AGENT ORANGE EXAMINATION DATE
  LOCATION: .321;9                      ACCESS: Read w/Fileman
FIELD NUMBER: .32103                    FIELD NAME: RADIATION EXPOSURE INDICATED
  LOCATION: .321;3                      ACCESS: Read w/Fileman
FIELD NUMBER: .32111                    FIELD NAME: RADIATION REGISTRATION DATE
  LOCATION: .321;11                     ACCESS: Read w/Fileman
FIELD NUMBER: .3212                     FIELD NAME: RADIATION EXPOSURE METHOD
  LOCATION: .321;11                     ACCESS: Read w/Fileman
FIELD NUMBER: .32115                    FIELD NAME: PROJ 112/SHAD
  LOCATION: .321;15                     ACCESS: Read w/Fileman
FIELD NUMBER: .5291                     FIELD NAME: COMBAT SERVICE INDICATED
  LOCATION: .52;11                      ACCESS: Read w/Fileman
FIELD NUMBER: .5293                     FIELD NAME: COMBAT FROM DATE
  LOCATION: .52;13                      ACCESS: Read w/Fileman
FIELD NUMBER: .5294                     FIELD NAME: COMBAT TO DATE
  LOCATION: .52;14                      ACCESS: Read w/Fileman
FIELD NUMBER: .118                      FIELD NAME: ADDRESS CHANGE DT/TM 
  LOCATION: .11;13                      ACCESS: Read w/Fileman
FIELD NUMBER: .12113                    FIELD NAME: TEMP ADDRESS CHANGE DT/TM
  LOCATION: .121;13                     ACCESS: Read w/Fileman
FIELD NUMBER: .14112
  FIELD NAME: CONFIDENTIAL ADDRESS CHANGE DT/TM
  LOCATION: .141;12                     ACCESS: Read w/Fileman
FIELD NUMBER: .1312                     FIELD NAME: PAGER NUMBER CHANGE DT/TM
  LOCATION: .13;12                      ACCESS: Read w/Fileman
FIELD NUMBER: .136                      FIELD NAME: EMAIL ADDRESS CHANGE DT/TM
  LOCATION: .13;6                       ACCESS: Read w/Fileman
FIELD NUMBER: .139
  FIELD NAME: CELLULAR NUMBER CHANGE DATE/TIME
  LOCATION: .13;9                       ACCESS: Read w/Fileman
FIELD NUMBER: .33012                    FIELD NAME: E-CONTACT CHANGE DT/TM
  LOCATION: .332;1                      ACCESS: Read w/Fileman
FIELD NUMBER: .33112                    FIELD NAME: E2-CONTACT CHANGE DT/TM
  LOCATION: .332;2                      ACCESS: Read w/Fileman
FIELD NUMBER: .3412                     FIELD NAME: DESIGNEE CHANGE DT/TM
  LOCATION: .332;3                      ACCESS: Read w/Fileman
FIELD NUMBER: .21012                    FIELD NAME: PRIMARY NOK CHANGE DATE/TIME
  LOCATION: .212;1                      ACCESS: Read w/Fileman
FIELD NUMBER: .211012
  FIELD NAME: SECONDARY NOK CHANGE DATE/TIME
  LOCATION: .212;2                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT('AEL')
FIELD NUMBER: .01                       FIELD NAME: SECONTARY ELIGIBILITY CODE
  ACCESS: Read w/Fileman
FIELD NUMBER: 0.3612                    FIELD NAME: ELIGIBILITY STATUS DATE
  LOCATION: .361;2                      ACCESS: Read w/Fileman
  STATUS: Active
KEYWORDS: PATIENT FILE
KEYWORDS: FILE 2
KEYWORDS: VPS
KEYWORDS: DPT
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   To support the VA Point of Service (Kiosks) project,
 global access to the PATIENT file (#2) is requested in order to provide a
 patient's demographic, military service, environmental factors, behavior
 flags, and service connected information to VetLink.  Patient records will be 
 identified by the internal entry number (DFN) in file #2, and read using 
 FileMan's Database Server (DBS) APIs in response to remote procedure calls 
 made by the VetLink Kiosk application.  
  
 In addition to the PATIENT file (#2) field access covered by this ICR, VPS 
 Kiosk also reads the following PATIENT file (#2) fields using supported APIs,
 IAs and approved VPS IAs.  
  
  
 VPS Kiosk reads the following PATIENT file (#2) fields from VADPT: 
      .211   K-NAME OF PRIMARY NOK (Fa)        .21;1 
      .213   K-STREET ADDRESS [LINE 1] (FX)    .21;3 
      .214   K-STREET ADDRESS [LINE 2] (FX)    .21;4 
      .215   K-STREET ADDRESS [LINE 3] (FX)    .21;5 
      .216   K-CITY (FX)                       .21;6 
      .217   K-STATE (P5'X)                    .21;7 
      .218   K-ZIP CODE (FX)                   .21;8 
      .219   K-PHONE NUMBER (FXa)              .21;9 
      .2191  K2-NAME OF SECONDARY NOK (FXa)    .211;1 
      .2192  K2-RELATIONSHIP TO PATIENT (FX)   .211;2 
      .2193  K2-STREET ADDRESS [LINE 1] (FX)   .211;3 
      .2194  K2-STREET ADDRESS [LINE 2] (FX)   .211;4 
      .2195  K2-STREET ADDRESS [LINE 3] (FX)   .211;5 
      .2196  K2-CITY (FX)                      .211;6 
      .2197  K2-STATE (P5'X)                   .211;7 
      .2198  K2-ZIP CODE (FX)                  .211;8 
      .2199  K2-PHONE NUMBER (FX)              .211;9 
  
  
 VPS Kiosk reade the following PATIENT file (#2) fields from supported API 4462 
  
      0.32115  PROJ 112/SHAD  .321;15 
  
 Under supported ICR 10035, VPS reads w/Fileman the following Patient file (#2)
 fields: 
  
      0.132   PHONE NUMBER [WORK]  .13;2 
      0.133   EMAIL ADDRESS        .13;3 
      0.134   PHONE NUMBER [CELLUL .13;4 
  
 Under ICR 5799, private for VPS, VPS writes w/Fileman to the following PATIENT
 file (#2) fields: 
  
      0.1171   PROVINCE             .11;8 
      0.1172   POSTAL CODE          .11;9 
      0.121    BAD ADDRESS INDICATO .11;16 
      0.1221   TEMPORARY ADDRESS PR .122;1 
      0.1222   TEMPORARY ADDRESS PO .122;2 
      0.21011  K-WORK PHONE NUMBER  .21;11 
      0.211011 K2-WORK PHONE NUMBER .211;11 
      0.31116  DATE OF RETIREMENT   .311;16 
      0.2515   SPOUSE'S EMPLOYMENT  .25;15 
      0.2516   SPOUSE'S RETIREMENT  .25;16 
  
 Under ICR 5831, VPS reads w/Fileman the following PATIENT file (#2) fields: 
   
      0.381   ELIGIBILITY FOR MEDI 38;1 
      0.21011  K-WORK PHONE NUMBER  .21;11 
      0.211011 K2-WORK PHONE NUMBER .211;11 
      0.31116  DATE OF RETIREMENT   .311;16 
      0.2515   SPOUSE'S EMPLOYMENT  .25;15 
      0.2516   SPOUSE'S RETIREMENT  .25;16 
  DATE ACTIVATED: FEB 25, 2015

NUMBER: 6126                            IA #: 6126
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19
  DATE CREATED: NOV 07, 2014            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: IB READ/WRITE ACCESS W/FILEMAN TO LOCK FIELD (#3)
  ID: DIC(19
GLOBAL REFERENCE: 19
FIELD NUMBER: 3                         FIELD NAME: LOCK
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   IB requires the ability to delete a LOCK from an
 OPTION. This cannot be accomplished using KIDS. Permission is required to
 accomplish this task using pre- or post-install routines in KIDS.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OPTION
KEYWORDS: LOCK
KEYWORDS: IB
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: DEC 03, 2014

NUMBER: 6127                            IA #: 6127
  DATE CREATED: NOV 17, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWOR VWGET
  REMOTE PROCEDURE: ORWOR VWGET         STATUS: Active
KEYWORDS: VPS
KEYWORDS: VWGET
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VPS uses ORWOR VWGET to provide the end users default
 order view to the After Visit Summary (AVS) component.  
  DATE ACTIVATED: AUG 13, 2015

NUMBER: 6128                            IA #: 6128
  DATE CREATED: NOV 17, 2014            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ICPTCOD
  NAME: ICPTCOD Update CSV APIs         ID: ICPTCOD
 GENERAL DESCRIPTION:   $$NM and $$LD were added as part of the Code Set
 Versioning APIs in patch ICPT*6.0*46.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NM
KEYWORDS: LD
KEYWORDS: $$NM
KEYWORDS: $$LD
COMPONENT/ENTRY POINT: $$NM(CODE,CDT,.ARY,LEN)
 COMPONENT DESCRIPTION:   This API returns the CPT/HCPCS Name (short
 description) formatted in string lengths specified.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a CPT or HCPCS code.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the date that will be used to return the name 
 that was appropriate for the date.  
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is a local array passed by reference that will 
 contain the CPT/HCPCS code name in string the lengths specified.  This array
 is first killed by the API then populated with the name.  
  
VARIABLES: LEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the desired length of the text to be returned 
 (10-78, default 78).  
  
VARIABLES: $$NM                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of lines in the output array or -1
 ^ Error Message 
  
COMPONENT/ENTRY POINT: $$LD(CODE,CDT,.ARY,LEN)
 COMPONENT DESCRIPTION:   This API returns the CPT/HCPCS Description (long 
 description) formatted in string lengths specified.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a CPT or HCPCS code.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the date that will be used to return the  
 description that was appropriate for the date.  
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is a local array passed by reference that will 
 contain the description in string lengths specified.  This array is first
 killed by the API then populated with the description.  
  
VARIABLES: LEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the desired length of the text to be returned 
 (15-245, default 78).  
  
VARIABLES: $$LD                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of lines in the output array or -1
 ^ Error Message 
  
  DATE ACTIVATED: FEB 23, 2015

NUMBER: 6129                            IA #: 6129
  DATE CREATED: NOV 17, 2014            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ICPTMOD
  NAME: ICPTMOD Update CSV APIs         ID: ICPTMOD
 GENERAL DESCRIPTION:   $$NM, $$LD, $$CM and $$MODC were added as part of the
 Code Set Versioning APIs in patch ICPT*6.0*46. 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NM
KEYWORDS: LD
KEYWORDS: $$NM
KEYWORDS: $$LD
KEYWORDS: CM
KEYWORDS: $$CM
KEYWORDS: MODC
KEYWORDS: $$MODC
COMPONENT/ENTRY POINT: $$NM(CODE,CDT,.ARY,LEN)
 COMPONENT DESCRIPTION:   This API returns the CPT/HCPCS Modifier Name (short 
 description) formatted in string lengths specified.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a CPT Modifier code.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the date that will be used to return the  
 modifier name that was appropriate for the date.  
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is a local array passed by reference that will 
 contain the modifier name in string lengths specified.  This array is first
 killed by the API then populated with the modifier name.  
  
VARIABLES: LEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the desired length of the text to be returned 
 (10-78, default 78).  
  
VARIABLES: $$NM                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of lines in the output array or -1
 ^ Error Message 
  
COMPONENT/ENTRY POINT: $$LD(CODE,CDT,.ARY,LEN)
 COMPONENT DESCRIPTION:   This API returns the CPT/HCPCS Modifier Description 
 (long description) formatted in string lengths specified.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a CPT or HCPCS Modifier Code.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the date that will be used to return the  
 description that was appropriate for the date.  
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is a local array passed by reference that will 
 contain the description in string lengths specified.  This array is first
 killed by the API then populated with the modifier description.  
  
VARIABLES: LEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the desired length of the text to be returned 
 (15-245, default 78).  
  
VARIABLES: $$LD                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of lines in the output array or -1
 ^ Error Message 
  
COMPONENT/ENTRY POINT: $$CM(Y,CPT,CDT,SRC)
 COMPONENT DESCRIPTION:   This API provides logic for a DIC("S") type screen
 for a lookup in the CPT Modifier file #81.3, where the CPT/HCPCS code is known
 and the screen filters out CPT Modifiers that cannot be used with the code on 
 the specified date.  
  
 Example: 
   
 S DIC("S")="I $$CM^ICPTMOD(CPT,+Y,CDT,SRC)>0" 
  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   This is a CPT/HCPCS Modifier Internal Entry Number 
 (IEN) from the CPT Modifier file #81.3 
  
VARIABLES: CPT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a CPT/HCPCS Code or Internal Entry Number 
 (IEN) from the CPT file #81.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the date that will be used to determine if
 the CPT Modifier can be used with a code.  
  
VARIABLES: SRC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the CPT level I, II or III as follows: 
  
   If 0 or Null, use Level I and II modifiers 
   If >0, use Level I, II, and III modifiers 
  
VARIABLES: $$CM                         TYPE: Output
 VARIABLES DESCRIPTION:   This is a Boolean value: 
  
   1  Modifier Y can be used with CPT code X 
   0  Modifier Y cannot be used with CPT code X 
  
COMPONENT/ENTRY POINT: $$MODC(MOD,CPT,CDT)
 COMPONENT DESCRIPTION:   This API returns the active CPT range of a Modifier 
 that includes the CPT/HCPCS code.  
  
VARIABLES: MOD                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a Modifier Code in the external format 
 (Required) 
  
VARIABLES: CPT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a CPT/HCPCS Code in the external format 
 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the date that will be used to determine if
 the CPT Modifier can be used with a code.  
  
VARIABLES: $$MODC                       TYPE: Output
 VARIABLES DESCRIPTION:   This is a 9 piece "^" delimited string as follows: 
   
      1   Modifier IEN 
      2   Modifier                     (#.01) 
      3   Active                       (#60, .01) 
      4   Modifier Name                (#61, 1) 
      5   CPT Range IEN                (#10) 
      6   CPT Begin Range Code         (#10, .01) 
      7   CPT End Range Code           (#10, .02) 
      8   CPT Range Activation Date    (#10, .03) 
      9   CPT Range Inactivation Date  (#10, .04) 
   
   or 
   
      0 when a qualifying range is not found 
   
   or 
   
      -1 ^ error message on error 
  
  DATE ACTIVATED: FEB 23, 2015

NUMBER: 6130                            IA #: 6130
  DATE CREATED: NOV 20, 2014            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPTFUT
  NAME: DGPTFUT                         ID: DGPTFUT
 GENERAL DESCRIPTION:   This ICR supports access to PTF (#45) data fields for
 the following PTF record types.  
  
 Patient Treatment File record types: 
 ------------------------------------
 401 - Surgery                                                           501 -
 Movement                                                          601 -
 Procedure                                                          701 -
 Diagnosis                                                         801 - CPT 
  
 Data fields may be accessed using the following APIs.  
  
 PTFIEN 
 ------
 This subroutine provides information about the subscripts of the multiples of
 the different PTF record types. These subscripts are needed for the other API
 calls.  
  
 PTFICD 
 ------
 This subroutine returns an array of the ICD's (IENs, codes, & descriptions),
 along with present on admission (POA) indicators (codes & values), where
 appropriate.  
  
 STR401 
 ------
 Given a patient (PTF IEN) and operation record type multiple, return a 
 twenty-five piece string containing the operation code ICD IENs.  
  
 STR501 
 ------
 Given a patient (PTF IEN) and movement record type multiple, return a 
 twenty-five piece string containing the movement code ICD IENs.  
  
 STR501P 
 -------
 Given a patient (PTF IEN) and movement record type multiple, return a 
 twenty-five piece string containing the present on admission (POA) codes.  
  
 STR601 
 ------
 Given a patient (PTF IEN) and procedure record type multiple, return a 
 twenty-five piece string containing the procedure code ICD IENs.  
  
 STR701 
 ------
 Given a patient (PTF IEN), return a twenty-five piece string containing the
 diagnosis code ICD IENs.  
  
 STR701P 
 -------
 Given a patient (PTF IEN), return a twenty-five piece string containing the
 present on admission (POA) codes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PTF
KEYWORDS: DGPT
COMPONENT/ENTRY POINT: PTFIEN(DGA,DGB,DGC)
 COMPONENT DESCRIPTION:   Given a PTF patient (PTF IEN) and record type, this
 returns an array of the subscripts of the multiples for the different PTF
 record types.  These subscripts are needed for the other API calls.  
VARIABLES: DGA                          TYPE: Input
 VARIABLES DESCRIPTION:   The PTF record type (401, 501, 601, 701, or 801).  
VARIABLES: DGB                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the patient in the PTF (#45) file.  
VARIABLES: DGC                          TYPE: Output
 VARIABLES DESCRIPTION:   An array of return values defined as follows: 
  - For PTF file record 401, DGC(IEN) is set 
    to the surgery/procedure date; 
  - For PTF file record 501, DGC(IEN) is set 
    to the movement date; 
  - For PTF file record 601, DGC(IEN) is set 
    to the procedure date; 
  - For PTF record type 701, DGC(0) is set 
    to the discharge date and is null for 
    active inpatients; 
  - For PTF file record 801, DGC(IEN) is set 
    to the CPT record date/time.  
COMPONENT/ENTRY POINT: PTFICD(DGA,DGB,DGC,DGD,DGE)
 COMPONENT DESCRIPTION:   Given a patient (PTF IEN), record type, and multiple
 subscript, this subroutine returns a list of the ICD's (IENs, codes, and
 descriptions), along with Present on Admission (POA) indicators (codes &
 values), where appropriate.  
VARIABLES: DGA                          TYPE: Input
 VARIABLES DESCRIPTION:   The PTF record type (401, 501, 601, 701, or 801).  
VARIABLES: DGB                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the patient in the PTF (#45) file.  
VARIABLES: DGC                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the field multiple of the 401, 501, 601, or
 801 record types.  It is ignored for record type 701.  
VARIABLES: DGE                          TYPE: Input
 VARIABLES DESCRIPTION:   Controls whether or not short or long ICD     
 descriptions are returned in the DGD array.  
  DGE=nil or 0 - no short or long descriptions 
                 returned 
  DGE=1 - short description returned in 
          DGD(i,1) 
  DGE=2 - long description returned in DGD(i,2) 
  DGE=3 - both descriptions returned in 
          DGD(i,1)/DGD(i,2) 
VARIABLES: DGD                          TYPE: Output
 VARIABLES DESCRIPTION:   The variable DGD is passed by reference.  
  
 DGD = piece-1 Patient Name 
       piece-2 Patient DFN (IEN in PATIENT #2 
               file) 
       piece-3 Admission date 
       piece-4 Admitting Facility (IEN in 
               INSTITUTION file(#4)) 
       piece-5 Fee basis flag (1 = yes) 
       piece-6 PTF Status (0=open, 1=closed, 
               2=released, 3=transmitted) 
       piece-7 Type of Record (1=PTF, 2=Census) 
       piece-8 Corresponding PTF Record (PTF 
               IEN) 
       piece-9 PTF Census date pointer (file 
               #45.86 IEN) 
       piece-10 Discharge date 
       piece-11 Effective date 
       piece-12 ICD-10 Code (ICD-10-CM or 
                ICD-10-PCS) 
       piece-13 (reserved for future use) 
       piece-14 (reserved for future use) 
       piece-15 (reserved for future use) 
       piece-16 Surgery/Procedure date 
  
 For PTF record types 401 and 601: 
  DGD(i) i is the number of the ICD code in 
         the record 
  DGD(i) piece-1 ICD OPERATION/PROCEDURE file 
                 (#80.1) IEN 
         piece-2 (reserved for future use) 
         piece-3 ICD code number 
  
 For PTF record types 501 and 701: 
  DGD(i) i is the number of the ICD code in 
         the record 
  DGD(i) piece-1 ICD DIAGNOSIS file (#80) IEN 
         piece-2 POA code for ICD (Y, N, U, 
                 or W) 
         piece-3 ICD code number 
         piece-4 POA value for ICD 
  
 For PTF record type 801: 
  DGD(i) i is the number of ICD code in 
         the record 
  DGD(i) piece-1 ICD DIAGNOSIS file (#80) IEN 
         piece-2 (reserved for future use) 
         piece-3 ICD code number 
  
 If DGE=1 or 3, DGD(i,1) is the short ICD description.  
  
 If DGE=2 or 3, DGD(i,2) is the long ICD description.  
COMPONENT/ENTRY POINT: $$STR401(DGA,DGB)
 COMPONENT DESCRIPTION:   This function returns a twenty-five piece string
 containing ICD OPERATION/PROCEDURE file (#80.1) IENs.  
VARIABLES: DGA                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the patient in the PTF (#45) file.  
VARIABLES: DGB                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the field multiple of the 401 record type.  
VARIABLES: $$STR401                     TYPE: Output
 VARIABLES DESCRIPTION:   The return value is a twenty-five piece string
 containing ICD OPERATION/PROCEDURE file (#80.1) IENs.  Example:
 ien1^ien2^...^ien24^ien25 
COMPONENT/ENTRY POINT: $$STR501(DGA,DGB)
 COMPONENT DESCRIPTION:   This function returns a twenty-five piece string
 containing ICD DIAGNOSIS file (#80) IENs.  
VARIABLES: DGA                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the patient in the PTF (#45) file.  
VARIABLES: DGB                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the field multiple of the 501 record type.  
VARIABLES: $$STR501                     TYPE: Output
 VARIABLES DESCRIPTION:   The return value is a twenty-five piece string
 containing ICD DIAGNOSIS file (#80) IENs.  Example: ien1^ien2^...^ien24^ien25 
COMPONENT/ENTRY POINT: $$STR601(DGA,DGB)
 COMPONENT DESCRIPTION:   This function returns a twenty-five piece string
 containing ICD OPERATION/PROCEDURE file (#80.1) IENs.  
VARIABLES: DGA                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the patient in the PTF (#45) file.  
VARIABLES: DGB                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the field multiple of the 601 record type.  
VARIABLES: $$STR601                     TYPE: Output
 VARIABLES DESCRIPTION:   The return value is a twenty-five piece string
 containing ICD OPERATION/PROCEDURE file (#80.1) IENs.  Example:
 ien1^ien2^...^ien24^ien25  
COMPONENT/ENTRY POINT: $$STR701(DGA)
 COMPONENT DESCRIPTION:   This function returns a twenty-five piece string
 containing ICD DIAGNOSIS file (#80) IENs.  
VARIABLES: DGA                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the patient in the PTF (#45) file.  
VARIABLES: $$STR701                     TYPE: Output
 VARIABLES DESCRIPTION:   The return value is a twenty-five piece string
 containing ICD DIAGNOSIS file (#80) IENs.  Example: ien1^ien2^...^ien24^ien25 
  
 Note: ien1 is for the primary diagnosis, ien2-ien25 are for the twenty-four
 secondary diagnoses.  
COMPONENT/ENTRY POINT: $$STR501P(DGA,DGB)
 COMPONENT DESCRIPTION:   This function returns a twenty-five piece string
 containing the Present On Admission (POA) codes for the ICDs.  
VARIABLES: DGA                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the patient in the PTF (#45) file.  
VARIABLES: DGB                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the field multiple of the 501 record type.  
VARIABLES: $$STR501P                    TYPE: Output
 VARIABLES DESCRIPTION:   The return value is a twenty-five piece string
 containing the Present On Admission (POA) codes for the ICDs.  Example:
 poa1^poa2^...^poa24^poa25 
COMPONENT/ENTRY POINT: $$STR701P(DGA)
 COMPONENT DESCRIPTION:   This function returns a twenty-five piece string
 containing the Present On Admission (POA) codes for the ICDs.  
VARIABLES: DGA                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the patient in the PTF (#45) file.  
VARIABLES: $$STR701P                    TYPE: Output
 VARIABLES DESCRIPTION:   The return value is a twenty-five piece string
 containing the Present On Admission (POA) codes for the ICDs.  Example:
 poa1^poa2^...^poa24^poa25 
  
 Note: poa1 is for the primary diagnosis, poa2-poa25 are for the twenty-four
 secondary diagnoses.  
SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES
SUBSCRIBING PACKAGE: HEALTH SUMMARY
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 10/7/22, effective with patch VPR*1*30. VPR is a
 data extract utility, and has been asked to pull ICD procedure codes from the
 PTF (#45) file. VPR needs to use the PTFIEN and $$STR601 components of routine
 DGPTFUT. 
  DATE ACTIVATED: AUG 03, 2015

NUMBER: 6131                            IA #: 6131
  DATE CREATED: NOV 20, 2014            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPEV3
  NAME: IBNCPEV3                        ID: IBNCPEV3
 GENERAL DESCRIPTION:   The ECME application requires access to the IB NCPDP
 EVENT LOG to extract data needed for the ECME Non-Billable Status Report.  
  STATUS: Active
KEYWORDS: ECME
KEYWORDS: NON-BILLABLE STATUS REPORT
COMPONENT/ENTRY POINT: $$COLLECT(BEGDT,ENDDT,MWC,RELNRL,IBDRUG,DRUGCLS,ALLRCNT,I
BPHARM,IBINS,IBNBSTS,IBELIG1,IBGLTMP)
 COMPONENT DESCRIPTION:   Entry point to extract the data from the IB NCPDP
 EVENT LOG based on the incoming criteria 
VARIABLES: BEGDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Begin date for extract 
VARIABLES: ENDDT                        TYPE: Input
 VARIABLES DESCRIPTION:   End date for extract 
VARIABLES: MWC                          TYPE: Input
 VARIABLES DESCRIPTION:   Fill Type extract criteria - A:All; M:Mail; W:Window;
 C:CMOP Prescriptions 
VARIABLES: RELNRL                       TYPE: Input
 VARIABLES DESCRIPTION:   Release extract criteria - 1:All; 2:Released; 3:Not
 Released 
VARIABLES: IBDRUG                       TYPE: Input
 VARIABLES DESCRIPTION:   Drug extract criteria - 0:All; DRUG to report on (ptr
 to #50) 
VARIABLES: DRUGCLS                      TYPE: Input
 VARIABLES DESCRIPTION:   Drug Class extract criteria - 0:All; DRUG CLASS to
 extract 
VARIABLES: ALLRCNT                      TYPE: Input
 VARIABLES DESCRIPTION:   Extract all or most recent data - A:All; R:Most
 recent 
VARIABLES: IBPHARM                      TYPE: Input
 VARIABLES DESCRIPTION:   BPS Pharmacy extract criteria - 0:All pharmacies;
 1:Array of IENs of pharmacies 
VARIABLES: IBINS                        TYPE: Input
 VARIABLES DESCRIPTION:   Insurance Company extract - 0:All insurances or list
 of file 36 IENs 
VARIABLES: IBNBSTS                      TYPE: Input
 VARIABLES DESCRIPTION:   Non-Billable status reason extract criteria - 0:All;
 1:Array of Non-Billable Status 
VARIABLES: IBELIG1                      TYPE: Input
 VARIABLES DESCRIPTION:   Patient Eligibility extract criteria - 0:All; 1:Array
 of multiple eligibilities (C:CHAMPVA, T:TRICARE, V:VETERAN) 
VARIABLES: IBGLTMP                      TYPE: Both
 VARIABLES DESCRIPTION:   The name of the temporary global to store the
 extracted data 
VARIABLES: $$COLLECT                    TYPE: Output
 VARIABLES DESCRIPTION:   Return value indicating the results of the extract - 
 1:Extract was successful, -1:Extract was not successful 
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: FEB 06, 2015

NUMBER: 6132                            IA #: 6132
  DATE CREATED: NOV 21, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWPCE PCE4NOTE                 REMOTE PROCEDURE: ORWPCE PCE4NOTE
  STATUS: Pending
KEYWORDS: VPS
KEYWORDS: PCE4NOTE
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VPS uses ORWPCE PCE4NOTE to get the encounter data for
 patient for After Visit Summary (AVS).  

NUMBER: 6133                            IA #: 6133
  DATE CREATED: NOV 21, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORWGRPC                      NAME: ORWGRPC ITEMDATA
  ID: ORWGRPC                           STATUS: Withdrawn
KEYWORDS: VPS
KEYWORDS: ITEMDATA
COMPONENT/ENTRY POINT: ITEMDATA
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The DFN is the patient's internal entry number in
 Patient File 2.  
VARIABLES: TODATE                       TYPE: Input
 VARIABLES DESCRIPTION:   The desired ending date, in FileMan format, for data
 starting from the earliest date on record.  
VARIABLES: ITEM                         TYPE: Input
 VARIABLES DESCRIPTION:   Item is a delimited string with format
 "Filenumber^Vitaltype", where Vitaltype is the IEN of the desired vital
 measurement in the Vitaltype file 120.51.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Result is the location of Global Array for return
 values.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VPS uses ORWGRPC ITEMDATA to get discrete lab data (for
 graphing) on the After Visit Summary (AVS). VPS will call ITEMDATA^ORWGRPC
 with the input parameters: name of result array,VITALTYPE,TODATE,and DFN i.e., 
 ITEMDATA^ORWGRPC(RESULT,"120.5^1",TODATE,DFN).  

NUMBER: 6134                            IA #: 6134
  DATE CREATED: NOV 21, 2014
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PXRPC                        NAME: ORWPCE SAVE
  REMOTE PROCEDURE: ORWPCE SAVE         ID: PXRPC
 GENERAL DESCRIPTION:   Saves PCE information.  
  STATUS: Withdrawn
KEYWORDS: VPS
COMPONENT/ENTRY POINT: SAVE
 COMPONENT DESCRIPTION:   
  
  
VARIABLES: PCELIST                      TYPE: Input
 VARIABLES DESCRIPTION:   
  
 PCELIST (n)= HDR ^ Encounter Inpatient? ^ Note has 
              CPT codes? ^ Visit string 
              [Encounter location; Encounter 
               date/time; Encounter 
               Service category]  (REQUIRED) 
          (n)=VST^DT^Encounter date/time 
          (n)=VST^PT^Encounter patient (DFN) 
          (n)=VST^HL^Encounter location 
          (n)=VST^VC^ Encounter Service Category 
                                 
          If  applicable: 
                                              
          (n)=VST^PR^ Parent for secondary visit 
          (n)=VST^OL^ Outside Location for 
              Historical visits 
          (n)=VST^SC^ Service Connected related? 
          (n)=VST^AO^ Agent Orange related? 
          (n)=VST^IR^ Ionizing Radiation related? 
          (n)=VST^EC^ Environmental Contaminates 
              related? 
          (n)=VST^MST^ Military Sexual Trauma 
              related? 
          (n)=VST^HNC^ Head and/or Neck Cancer 
              related? 
          (n)=VST^CV^ Combat Vet related? 
          (n)=VST^SHD^ Shipboard Hazard and Defense 
              related 
          (n)=VST^CLV^ Camp Lejeune related? 
          (n)=PRV^PRV ^ Provider IEN ^^^ Provider 
              Name ^ Primary Provider? 
          (n)=POV(+:  add, -: delete) ^ ICD 
              diagnosis code ^ Category  ^ 
              Narrative (Diagnosis description) ^ 
              Primary Diagnosis? ^ 
              Provider String ^ Add to Problem 
              List? ^^^ Next comment 
              sequence # if saving comments 
          (n)=COM^COM (Comments) ^ Next 
              comment sequence # ^ @ = no comments 
              added 
          (n)=CPT (+:  add, -: delete) ^ Procedural 
              CPT code ^ Category ^ 
              Narrative (Procedure description) ^ 
              Quantity ^ Provider IEN 
              ^^^ [# of modifiers;  Modifier 
              code/Modifier IEN ^ Next 
              comment sequence # ^ 
                         
 Effective with PX*1*209, the PCELIST input parameter contains modifications
 for IMM (Immunization)type data to include additional fields:  Encounter
 Provider, Event Info Source, Dosage, Route, Admin Site, Lot #, Manufacturer,
 Expiration Date.  
                                        
 The IMM PCELIST items are not required To have the new fields - to support
 backward compatibility.  
                                
          (n)=IMM (+:  add, -: delete) ^ 
              Immunization IEN ^ Category ^ 
              Narrative (Immunization 
              description/name) ^ Series ^ 
              Encounter Provider ^ Reaction ^ 
              Contraindicated? ^^ Next 
              comment sequence # ^ CVX Code ^ Event 
              Info Source HL7 Code;IEN ^ 
              Dose;Units;Units IEN ^ Route 
              Name;HL7 Code;IEN ^ 
              Admin Site Name;HL7 Code;IEN^ 
              Lot #;IEN ^ Manufacturer ^ 
              Expiration Date ^ Event Date and 
              Time ^ Ordering Provider ^ 
              VIS1 IEN/VIS1 Date;VISn IEN/VISn 
              Date;...^ Remarks Start Seq 
              #;End Seq # 
                                
          (n)=SK (+:  add, -: delete) ^ Skin Test 
              IEN ^ Category ^ 
              Narrative (Skin Test 
              description/name) ^ Results ^^ 
              Reading ^^^ Next comment 
              sequence # 
          (n)=PED (+: add, -: delete) ^ Patient 
              Education IEN ^ Category ^ Narrative 
              (Patient Education 
              description/name) ^ Level of 
              understanding ^^^^^ ^^ Next comment 
              sequence # 
          (n)=HF (+:  add, -: delete) ^ 
              Health Factor 
              IEN ^ Category ^ Narrative 
              (Health Factor description/name) ^ 
              Level ^^^^^ Next comment sequence # ^ 
              Get Reminder 
          (n)=XAM(+:  add, -: delete) ^ Exam IEN ^ 
              Category ^ Narrative 
              (Exam description/name) ^ Results 
              ^^^^^ Next comment sequence # 
  
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the hospital location. This is not used when
 the information is from an outside source.  
VARIABLES: PKGNAME                      TYPE: Input
 VARIABLES DESCRIPTION:   The package name that is sending the data to PCE.
 This should be the full package name, such as PATIENT CARE ENCOUNTERS. 
VARIABLES: SRC                          TYPE: Input
 VARIABLES DESCRIPTION:   The source of the data - such as VLER E-HEALTH
 EXCHANGE.  
VARIABLES: OK                           TYPE: Output
 VARIABLES DESCRIPTION:   A -2 indicates that the routine PXAI found an issue
 even though the original input values appeared to be correct. 
  
 A -3 indicates that the input parameters were not properly defined. 
  
 A 1 indicate success.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VPS needs to update a patient's primary care encounter
 with the patient's clinical reminder responses to resolve a patient's DUE NOW
 behavioral clinical reminders.  
  DATE ACTIVATED: NOV 24, 2015

NUMBER: 6135                            IA #: 6135
  DATE CREATED: NOV 21, 2014
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWLRR INTERIM                  REMOTE PROCEDURE: ORWLRR INTERIM
  STATUS: Pending
KEYWORDS: VPS
KEYWORDS: INTERIM
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VPS uses ORWLRR INTERIM for lab test results for
 patient on After Visit Summary (AVS).  

NUMBER: 6136                            IA #: 6136
  FILE NUMBER: 366.17                   GLOBAL ROOT: IBCNR(366.17,
  DATE CREATED: NOV 24, 2014            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DB6136
  ID: IBCNR(366.17,
GLOBAL REFERENCE: IBCNR(366.17,D0
FIELD NUMBER: .01                       FIELD NAME: NON-BILLABLE REASON
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the name of the non-billable status reason that
 is used to populated the IB NCPDP EVENT LOG file.  
 GENERAL DESCRIPTION:   The ECME application needs to extract the NON-BILLABLE
 REASON (#.01) field from the IB NCPDP NON-BILLABLE REASONS file.  This is a
 read-only action and does not modify any fields in the file.  
  
 The ECME application also requests lookup capabilities on the file via 
 Fileman.  No modification of the data will be done.  
  STATUS: Active
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: FEB 06, 2015

NUMBER: 6137                            IA #: 6137
  FILE NUMBER: 2.98                     GLOBAL ROOT: DPT(
  DATE CREATED: NOV 26, 2014            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: APPT CANCEL REMARKS
  ID: DPT(
GLOBAL REFERENCE: DPT(D0,'S',D1,'R'
FIELD NUMBER: 17                        FIELD NAME: CANCELLATION REMARKS
  LOCATION: 'R';1                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VPS returns a patient's outpatient clinic appointment
 status to Vetlink.  The outpatient clinic appointment information returned
 includes the cancellation remarks obtained from the APPOINTMENT sub-file 2.98,
 field 17.  
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: CANCELLATION
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) uses FileMan to read the
 CANCELLATION REMARKS, field 17, from the APPOINTMENT subfile #2.98.  
  DATE ACTIVATED: JAN 06, 2015

NUMBER: 6138                            IA #: 6138
  DATE CREATED: DEC 02, 2014            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGHBPUTL
  NAME: HEALTH BENEFIT PLAN INFORMATION
  ID: DGHBPUTL
 GENERAL DESCRIPTION:   ICR for Health Benefit Plans (HBP) to be shared by
 other VistA applications.  
  
 8/21/15:  Routine DGHBPUTL will be distributed by patch DG*5.3*871. The status
 of the ICR has been set to Deferred until patch is released and Subscribing
 Packages are identified.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HBP
KEYWORDS: HEALTH BENEFIT PLAN
COMPONENT/ENTRY POINT: GETHBP(DFN)
 COMPONENT DESCRIPTION:   Provides an array, HBP. that contains all of the
 patient's assigned Health Benefit Plans and Historical data.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's Data File Number 
VARIABLES: HBP                          TYPE: Output
 VARIABLES DESCRIPTION:   HBP("CUR",HBP Plan Name) = 
               Plan IEN^Date/Time Set^Entered By^Entered Site 
 HBP("HIS",Date/Time Set,Plan IEN) = 
               Plan Name^Entered by^Entered Site 
COMPONENT/ENTRY POINT: GETDETL(HBPNUM)
 COMPONENT DESCRIPTION:   Provides an array, HBP("DETAIL"). that contains the
 Health Benefit Plans detailed information.  
VARIABLES: HBP                          TYPE: Output
 VARIABLES DESCRIPTION:   HBP("DETAIL".0)= 
               ^^Number of Lines^Last Line Number^Date Entered HBP("DETAIL",HBP
 Plan IEN,Line Number) = 
               Description Line 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 12/3/24 effective with PSO*7*770 so Meds By Mail
 (MbM) can call GETHBP and GETDETL in the DHBPUTL routine to determine whether
 a VistA patient is eligible for ChampVA Benefits or not. 
  DATE ACTIVATED: DEC 17, 2015

NUMBER: 6139                            IA #: 6139
  DATE CREATED: DEC 02, 2014            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: BPSUTIL2
  NAME: BPSUTIL2                        ID: BPSUTIL2
 GENERAL DESCRIPTION:   The Accounts Receivable (AR) and Integrated Billing
 (IB) packages need to verify whether a pharmacy electronic claim number
 returned by a third party payer is valid or not. The verification will be used
 in the process to match payments received with existing open claims.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VALECME
KEYWORDS: ECME
COMPONENT/ENTRY POINT: $$VALECME(ECMENUM)
 COMPONENT DESCRIPTION:   Validates an ECME Number.  
VARIABLES: ECMENUM                      TYPE: Input
 VARIABLES DESCRIPTION:   The ECME number to be validated.  
VARIABLES: $$VALECME                    TYPE: Output
 VARIABLES DESCRIPTION:   
  0 - Invalid ECME Number 
  1 - Valid ECME Number 
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: DEC 10, 2014

NUMBER: 6140                            IA #: 6140
  DATE CREATED: DEC 03, 2014            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Private                        TYPE: Routine
  ROUTINE: PSJDGAL2                     NAME: FINDC
  ID: PSJDGAL2
 GENERAL DESCRIPTION:   Inpatient Meds allows Outpatient Pharmacy to use
 $$FIND^PSJDGAL2 which returns the formated orderable item, dose form and units 
 as: orderable item doseform (units) ex: MORPHINE TAB,SA (100MG).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: FINDC
KEYWORDS: PSJDGAL2
COMPONENT/ENTRY POINT: FINDC
VARIABLES: PSJORD                       TYPE: Input
 VARIABLES DESCRIPTION:   CURRENT ORDER NUMBER 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 6141                            IA #: 6141
  DATE CREATED: DEC 04, 2014
  CUSTODIAL PACKAGE: VENDOR - DOCUMENT STORAGE SYS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: VEJDVEST                     NAME: RPC VEJDVEST
  ID: VEJDVEST                          STATUS: Withdrawn
KEYWORDS: VEJDVST
KEYWORDS: VEJDVEST
KEYWORDS: VPS
COMPONENT/ENTRY POINT: RPC
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN is the internal entry number of a patient record
 in file #2.  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   RET is the computed patient's vested status, 0=not
 vested or 1=vested.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   vA Point of Service Kiosks calls RPC^VEJDVEST to read a
 patient's vested status, for return to VetLink. VPS passes the patient DFN to
 VEJDVEST.  

NUMBER: 6142                            IA #: 6142
  FILE NUMBER: 36                       GLOBAL ROOT: DIC(36
  DATE CREATED: DEC 09, 2014            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INSURANCE COMPANY LOOKUP
  ID: DIC(36
GLOBAL REFERENCE: DIC(36,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Outpatient Pharmacy requires a lookup and extract on
 the NAME (#.01) field of the Insurance Company (#36) file via Fileman.  No
 changes to the file will be made.  
  STATUS: Active
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: FEB 06, 2015

NUMBER: 6143                            IA #: 6143
  FILE NUMBER: 350.9                    GLOBAL ROOT: IBE(350.9
  DATE CREATED: JAN 08, 2015            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IB SITE PARAMETERS FILE ACCESS
  ID: IBE(350.9
GLOBAL REFERENCE: IBE(350.9,D0,62)
FIELD NUMBER: 62.01
  FIELD NAME: LIMIT FIELD LENGTH OF EIV FIELDS?
  LOCATION: 62;1                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Insurance Capture Buffer application reads file
 #350.9 IB SITE PARAMETERS to determine what field lengths the site wishes to
 use.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
 SUBSCRIBING DETAILS:   Insurance Card Buffer (ICB) needs to read the LIMIT
 LENGTH OF EIV FIELDS? (#62.01) field from the IB SITE PARAMETERS (#350.9)
 file. This is a read-only action and does not modify any fields in the file.  
  DATE ACTIVATED: JAN 04, 2018

NUMBER: 6144                            IA #: 6144
  DATE CREATED: JAN 13, 2015            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFHLPI1
  NAME: PID SEGMENT BUILDING - RETURN RACE AND ETHNICITY
  ID: VAFHLPI1
 GENERAL DESCRIPTION:   VAFHLPI1 is a routine that is used to build the PID
 segment of HL7 messages. It is comprised of functions that return the race and
 the ethnicity of a patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAG VAFHLPI1
KEYWORDS: MAG RACE/ETHNICITY PID SEGMENT
COMPONENT/ENTRY POINT: SEQ10
 COMPONENT DESCRIPTION:   This function returns the race of a specific patient.
 The validity and existence of the input is assumed. Use of the 'T' & 'B'
 qualifiers assumes use of the 'N' qualifier. This function assumes no
 individual component is greater than 245 characters in length.  
VARIABLES: HOW                          TYPE: Input
 VARIABLES DESCRIPTION:   Passes in qualifiers denoting how and which (new or
 historic) race information is to be returned.  
     "N": Return new race value (2.02 multiple) 
     "T": Include text (components 2 & 5) 
     "B": Include second triplet (components 4 - 6) 
    Null: Return historical value (.06 field) 
VARIABLES: HLQ                          TYPE: Input
 VARIABLES DESCRIPTION:   HLQ is the variable used to insert null field values
 in segments.  
VARIABLES: VAFY                         TYPE: Output
 VARIABLES DESCRIPTION:   The array in which race information is returned for a
 specific patient.  
COMPONENT/ENTRY POINT: SEQ22
 COMPONENT DESCRIPTION:   This function returns the ethnicity of a specific
 patient. The validity and existence of the input variables are assumed. This
 function assumes no individual component is greater than 245 characters in
 length.  
VARIABLES: HOW                          TYPE: Input
 VARIABLES DESCRIPTION:   Passes in qualifiers denoting how and which (new or
 historic) race information is to be returned.  
     "T": Include text (components 2 & 5) 
     "B": Include second triplet (components 4 - 6) 
    Null: Only return components 1 - 3.  
VARIABLES: HLQ                          TYPE: Input
 VARIABLES DESCRIPTION:   HLQ is the variable used to insert null field values
 in segments.  
VARIABLES: VAFY                         TYPE: Output
 VARIABLES DESCRIPTION:   The array in which ethnicity information is returned
 for a specific patient.  
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   With the activation of this Integration Agreement (IA),
 VistA Imaging will build their PID segment with the race and ethnicity data 
 returned from the functions SEQ10 (race) and SEQ22 (ethnicity) provided in the
 routine: VAFHLPI1.  
  DATE ACTIVATED: AUG 04, 2015

NUMBER: 6145                            IA #: 6145
  FILE NUMBER: 40.8                     GLOBAL ROOT: DG(40.8
  DATE CREATED: JAN 20, 2015            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  NAME: VPS READ 40.8                   ID: DG(40.8
GLOBAL REFERENCE: DPT(D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: INSTITUTION FILE POINTER
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: FACILITY NUMBER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA provides for the Fileman read of the NAME,
 INSTITUTION FILE POINTER, and FACILITY NUMBER fields in the INSTITUTION FILE
 file #40.8.  
  STATUS: Withdrawn
KEYWORDS: INSTITUTION FILE
KEYWORDS: VPS
KEYWORDS: FACILITY NUMBER
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) has a need to read the
 NAME, field .01, INSTITUTION FILE, field .07, and the FACILITY NUMBER, filed 1
 from the INSTITUTION FILE #40.8.  

NUMBER: 6146                            IA #: 6146
  FILE NUMBER: 8930.3                   GLOBAL ROOT: USR(8930.3
  DATE CREATED: JAN 20, 2015
  CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION
  USAGE: Controlled Subscription        TYPE: File
  NAME: VPS READ OF 8930.3              ID: USR(8930.3
GLOBAL REFERENCE: USR(8930.3,0)
FIELD NUMBER: .02                       FIELD NAME: USER CLASS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .01                       FIELD NAME: MEMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: EFFECTIVE DATE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: EXPIRATION DATE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: USR(8930.3,'B',MEMBER)
 GENERAL DESCRIPTION:   VA Point of Service Kiosks needs to read global
 references in the USER CLASS MEMBERSHIP FILE #8930.3.  
  STATUS: Withdrawn
KEYWORDS: USER CLASS
KEYWORDS: VPS
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) needs to read with Fileman
 the global reference ^USR(8930.0,0) fields .01 MEMBER, .02 USER CLASS, .03
 EFFECTIVE DATE and .04 EXPIRATION DATE, and the ^USR(8930.3,'B',MEMBER) 
 cross-reference from the USER CLASS MEMBERSHIP file (#8930.3) 

NUMBER: 6147                            IA #: 6147
  FILE NUMBER: 3.5                      GLOBAL ROOT: %ZIS(1
  DATE CREATED: JAN 26, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VPS READ OF 3.5
  ID: %ZIS(1
GLOBAL REFERENCE: %ZIS(1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: %ZIS(1,D0,1)
FIELD NUMBER: .02                       FIELD NAME: LOCATION OF TERMINAL
  LOCATION: 1;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: %ZIS(1,D0,91)
FIELD NUMBER: 9                         FIELD NAME: MARGIN WIDTH
  LOCATION: 91;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: PAGE LENGTH
  LOCATION: 91;3                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: %ZIS(1,D0,VMS)
FIELD NUMBER: 65                        FIELD NAME: PRINT SERVER NAME OR ADDRESS
  LOCATION: VMS;5                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA provides for the Fileman read of the NAME,
 LOCATION OF TERMINAL, MARGIN WIDTH, PAGE LENGTH, and PRINT SERVER NAME OR
 ADDRESS fields in the DEVICE file #3.5.  
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: DEVICE FILE
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) has a need to read the
 NAME, field .01, LOCATION OF TERMINAL, field .02, MARGIN WIDTH, field 9, PAGE
 LENGTH, field 11, and PRINT SERVER NAME OR ADDRESS, field 65 from the DEVICE
 file (#3.5).  
  DATE ACTIVATED: MAR 03, 2015

NUMBER: 6148                            IA #: 6148
  FILE NUMBER: 52.41                    GLOBAL ROOT: PS(52.41
  DATE CREATED: JAN 26, 2015            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VPS READ OF 52.41
  ID: PS(52.41
GLOBAL REFERENCE: PS(52.41,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PLACER NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ORDER TYPE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: # OF REFILLS
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 22                        FIELD NAME: REASON ORDER CREATED
  LOCATION: 0;20                        ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.1                       FIELD NAME: PATIENT LOCATION
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: PROVIDER
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: PHARMACY ORDERABLE ITEM
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: PROVIDER COMMENTS
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: PHARMACY INSTRUCTIONS
  LOCATION: 3;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 15                        FIELD NAME: LOGIN DATE
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 19                        FIELD NAME: PICKUP ROUTING
  LOCATION: 0;17                        ACCESS: Read w/Fileman
FIELD NUMBER: 25                        FIELD NAME: PRIORITY
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 101                       FIELD NAME: DAYS SUPPLY
  LOCATION: 0;22                        ACCESS: Read w/Fileman
FIELD NUMBER: 104                       FIELD NAME: PATIENT INSTRUCTIONS
  LOCATION: INS;1                       ACCESS: Read w/Fileman
FIELD NUMBER: 105                       FIELD NAME: EXPANDED INSTRUCTIONS
  LOCATION: INS1;1                      ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: DRUG
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: INDICATION FOR USE
  LOCATION: 4;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(52.41,D0,1,D1,1)
FIELD NUMBER: 11                        FIELD NAME: UNITS
  LOCATION: 1;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: CONJUNCTION
  LOCATION: 1;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: SCHEDULE
  LOCATION: 1;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DURATION
  LOCATION: 1;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: MED ROUTE
  LOCATION: 1;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: DOSAGE ORDERED
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: DISPENSE UNITS PER DOSE
  LOCATION: 2;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: NOUN
  LOCATION: 1;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: VERB
  LOCATION: 1;10                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(52.41,D0,'SIG',D1,0)
FIELD NUMBER: .01                       FIELD NAME: DISPENSING INSTRUCTIONS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(52.41,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: QUANTITY/FORM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA provides for the Fileman read of the 
     
     PLACER NUMBER, ORDER TYPE, # OF REFILLS, REASON ORDER CREATED, PATIENT 
     of the PENDING OUTPATIENT ORDERS FILE #52.41, 
  
     CONJUNCTION, UNITS fields of the QUANTITY TIMING SUB-FILE 
     subfile #52.413 of the PENDING OUTPATIENT ORDERS file #52.41, and 
  
     the DISPENSING INSTRUCTIONS field of the DISPENSING 
     INSTRUCTIONS subfile #52.4124 in the PENDING OUTPATIENT 
     ORDERS file #52.41.  
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: PENDING OUTPATIENT ORDERS
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) has a need to read the
 PLACER NUMBER, field .01, ORDER TYPE, field 2, # OF REFILLS, field 13, REASON
 ORDER CREATED, field 22, PATIENT, field 1 from the PENDING OUTPATIENT ORDERS
 file (#52.41), and CONJUNCTION, field 6, UNITS, field 11 from the QUANTITY 
 TIMING SUB-FILE subfile (#52.413) of the PENDING OUTPATIENT ORDERS file 
 (#52.41), and DISPENSING INSTRUCTIONS, field .01, of the DISPENSING 
 INSTRUCTIONS subfile #52.4124 of the PENDING OUTPATIENT ORDERS file #52.41 
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 02/07/2022, effective with DSSV 1.1 DSS Class 3
 product Document Only DSSV is using fields
 1.1,8,9,5,10,12,15,19,25,101,104,105;.01,1,2,10 from subfile 52.413 from the
 PENDING OUTPATIENT ORDERS (#52.41) file to support the medication
 reconciliation feature.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 9/13/23, effective with patch OR*3.0*535, to
 access the PLACER NUMBER (#.01) field in the PENDING OUTPATIENT ORDERS
 (#52.41) file to allow CPRS to display the ordering provider related to
 certain notifications.  
  DATE ACTIVATED: MAR 19, 2015

NUMBER: 6149                            IA #: 6149
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX
  DATE CREATED: JAN 26, 2015            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VPS READ OF 52
  ID: PSRX
GLOBAL REFERENCE: PSRX(D0,0)
FIELD NUMBER: .01                       FIELD NAME: RX #
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: # OF REFILLS
  LOCATION: 0;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,OR1)
FIELD NUMBER: 39.3                      FIELD NAME: PLACER ORDER #
  LOCATION: OR1;2                       ACCESS: Read w/Fileman
FIELD NUMBER: 39.4                      FIELD NAME: PREVIOUS ORDER #
  LOCATION: OR1;3                       ACCESS: Read w/Fileman
FIELD NUMBER: 39.5                      FIELD NAME: FORWARD ORDER #
  LOCATION: OR1;4                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,STA)
FIELD NUMBER: 100                       FIELD NAME: STATUS
  LOCATION: STA;1                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,3)
FIELD NUMBER: 12                        FIELD NAME: REMARKS
  LOCATION: 3;7                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,2)
FIELD NUMBER: 27                        FIELD NAME: NDC
  LOCATION: 2;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: RELEASED DATE/TIME
  LOCATION: 2;13                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA provides for the Fileman read of the RX #,
 PLACER ORDER #, STATUS, NDC, # OF REFILLS, REMARKS, RELEASED DATE/TIME,
 PREVIOUS ORDER #, FORWARD ORDER # fields in the PRESCRIPTION file #52.  
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: PRESCRIPTION
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) has a need to read the RX
 #, field .01, PLACER ORDER #, field 39.3, STATUS, field 100, NDC, field 27, #
 OF REFILLS, field 9, REMARKS, field 12, RELEASED DATE/TIME, field 31, PREVIOUS
 ORDER #, field 39.4, FORWARD ORDER #, field 39.5 from the PRESCRIPTION file
 (#52).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 9/13/23, effective with patch OR*3.0*535, to
 access the PLACER ORDER # (#39.3) field in the PRESCRIPTION (#52) file to
 allow CPRS to display the ordering provider related to certain notifications.  
  DATE ACTIVATED: MAR 11, 2015

NUMBER: 6150                            IA #: 6150
  FILE NUMBER: 403.5                    GLOBAL ROOT: SD(403.5
  DATE CREATED: JAN 26, 2015            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VPS READ OF 403.5
  ID: SD(403.5
GLOBAL REFERENCE: SD(403.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: TEST/APP
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PROVIDER
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 4.5                       FIELD NAME: CLINIC
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: RECALL DATE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA provides for the Fileman read of the PATIENT
 NAME, TEST/APP, PROVIDER, CLINIC, RECALL DATE fields in the RECALL REMINDERS
 file #403.5.  
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: SCHEDULING
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) has a need to read the
 PATIENT NAME, field .01, TEST/APP, field 3, PROVIDER, field 4, CLINIC, field
 4.5, RECALL DATE, field 5 from the RECALL REMINDERS file (#403.5).  
  DATE ACTIVATED: APR 07, 2015

NUMBER: 6151                            IA #: 6151
  FILE NUMBER: 52.41                    GLOBAL ROOT: PS(52.41
  DATE CREATED: JAN 26, 2015            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VPS READ OF 52.4124
  ID: PS(52.41
GLOBAL REFERENCE: PS(52.41,D0,'SIG',D1,0)
FIELD NUMBER: .01                       FIELD NAME: DISPENSING INSTRUCTIONS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA provides for the Fileman read of the DISPENSING
 INSTRUCTIONS field in the DISPENSING INSTRUCTIONS sub-file #52.4124.  
  STATUS: Withdrawn
KEYWORDS: VPS
KEYWORDS: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) has a need to read the
 DISPENSING INSTRUCTIONS, field .01 from the DISPENSING INSTRUCTIONS sub-file 
 (#52.4124).  
  DATE ACTIVATED: MAR 06, 2015

NUMBER: 6152                            IA #: 6152
  FILE NUMBER: 120.8                    GLOBAL ROOT: GMR(120.8
  DATE CREATED: JAN 26, 2015
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VPS READ OF 120.8
  ID: GMR(120.8
GLOBAL REFERENCE: GMR(120.8,D0,0)
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: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: GMR(120.8,'B')
 GENERAL DESCRIPTION:   This IA provides for the Fileman read of the REACTANT,
 ALLERGY TYPE, VERIFICATION DATE/TIME, and PATIENT fields in the PATIENT
 ALLERGIES file #120.8.  
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: ADVERSE REACTION TRACKING
KEYWORDS: ALLERGY
KEYWORDS: ALLERGIES
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) has a need to read the
 REACTANT, field .02, ALLERGY TYPE, field 3.1, VERIFICATION DATE/TIME, field
 20, PATIENT, field 0.1 from the PATIENT ALLERGIES file (#120.8).  
  DATE ACTIVATED: MAR 26, 2015

NUMBER: 6153                            IA #: 6153
  FILE NUMBER: 9000010.23               GLOBAL ROOT: AUPNVHF
  DATE CREATED: JAN 26, 2015
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: File
  NAME: VPS WRITE TO 9000010.23         ID: AUPNVHF
GLOBAL REFERENCE: AUPNVHF(D0,0)
FIELD NUMBER: .02                       FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: .03                       FIELD NAME: VISIT
  LOCATION: 0;3                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   This IA provides for the Fileman WRITE of the PATIENT
 NAME (.02) and VISIT (.07) fields in the  V HEALTH FACTORS file #9000010.23.  
  STATUS: Withdrawn
KEYWORDS: VPS
KEYWORDS: PCE
KEYWORDS: PCE PATIENT CARE ENCOUNTERS
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) has a need to write to the
 PATIENT NAME, field .02, and the VISIT, field .03, in the V HEALTH FACTORS
 file (#9000010.23).  
  DATE ACTIVATED: NOV 09, 2015

NUMBER: 6154                            IA #: 6154
  FILE NUMBER: 8925                     GLOBAL ROOT: TIU(8925
  DATE CREATED: JAN 26, 2015
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VPS READ OF 8925
  ID: TIU(8925
GLOBAL REFERENCE: TIU(8925,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DOCUMENT TYPE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PATIENT
  LOCATION: 0;2                         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: .06                       FIELD NAME: PARENT
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: .11                       FIELD NAME: CREDIT STOP CODE ON
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: EPISODE BEGIN DATE/TODAY
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: .13                       FIELD NAME: VISIT TYPE
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 1202                      FIELD NAME: AUTHOR/DICTATOR
  LOCATION: 12;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 1204                      FIELD NAME: EXPECTED SIGNER
  LOCATION: 12;4                        ACCESS: Read w/Fileman
FIELD NUMBER: 1208                      FIELD NAME: EXPECTED COSIGNER
  LOCATION: 12;8                        ACCESS: Read w/Fileman
FIELD NUMBER: 1211                      FIELD NAME: VISIT LOCATION
  LOCATION: 12;11                       ACCESS: Read w/Fileman
FIELD NUMBER: 1506                      FIELD NAME: COSIGNER NEEDED
  LOCATION: 15;6                        ACCESS: Read w/Fileman
FIELD NUMBER: 1201                      FIELD NAME: ENTRY DATE/TIME
  LOCATION: 12;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 1301                      FIELD NAME: REFERENCE DATE
  LOCATION: 13;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 1501                      FIELD NAME: SIGNATURE DATE/TIME
  LOCATION: 15;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 1502                      FIELD NAME: SIGNED BY
  LOCATION: 15;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 1507                      FIELD NAME: COSIGNATURE DATE/TIME 
  LOCATION: 15;7                        ACCESS: Read w/Fileman
FIELD NUMBER: 1508                      FIELD NAME: COSIGNED BY
  LOCATION: 15;8                        ACCESS: 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 IA provides for the Fileman read of the DOCUMENT
 TYPE, STATUS, EPISODE BEGIN DATE/TIME, AUTHOR/DICTATOR, VISIT LOCATION,
 PATIENT fields in the TIU DOCUMENT file #8925.  
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: TEXT INTEGRATION UTILITIES
KEYWORDS: TIU
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) has a need to read the
 DOCUMENT TYPE, field .01, STATUS, field .05, EPISODE BEGIN DATE/TIME, field
 .07, AUTHOR/DICTATOR, field 1202, VISIT LOCATION, field 1211, PATIENT, field 
 .02 from the TIU DOCUMENT file (#8925).  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP reads the "AA", "ACLPT", and "C" cross-references
 in the TIU document file (#8925).  
  
 HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP. 
 HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
 for the sites to shut down the application.  
                          
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR. See VistA Document Library for list of retired
 HMP ICRs. 
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 11/29/2021, effective with DSSV*1.0*1 DSS Class 3
 product Document Only 
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   Added 12/22/2022, CPRS development team is releasing
 patch DG*5.3*1086 to clean up some pointers to notes that may have been
 deleted. This will require read access to file #8925.  
  DATE ACTIVATED: MAR 24, 2015

NUMBER: 6155                            IA #: 6155
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,D0,EC
  DATE CREATED: JAN 27, 2015            CUSTODIAL PACKAGE: EVENT CAPTURE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS TO DMMS UNITS SUB-FIELD IN NEW PERSON FILE #200
  ID: VA(200,D0,EC
GLOBAL REFERENCE: VA(200,D0,EC,0)
FIELD NUMBER: 720                       FIELD NAME: DMMS UNITS
  LOCATION: EC;0                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   DMMS Units to which this person has access 
 GENERAL DESCRIPTION:   EVENT CAPTURE owns the DMMS UNITS sub-field (#720) in
 NEW PERSON File (#200). 
  
 MHV Secure Messaging - Work Load Credit functionality allows users to save the
 workload credit using the assigned DSS units, and stores the record in Event
 Capture System.  The use of the DSS units is the same as in ECS, users have
 access to link their work to DSS units that send the record to PCE, as well as
 historical DSS units for historical workload credit forms that do not send the
 information to PCE. 
  
 Three conditions need to be satisfied before DSS Unit can be presented to 
 provider 1. DSS Unit must be active.  2. Provider should have that DSS Unit in
 the assigned (MHV) list of DSS Units.  3. DSS Unit should also be associated
 with Location (Associated clinic) selected in front-end. MHV checks for these
 three conditions and sends back DSS Units that pass this criteria. To check
 Condition #2, MHV reads DMMS Units sub-field (#720) in NEW PERSON File (#200)
 which is owned by EVENT CAPTURE.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DMMS UNITS
KEYWORDS: DSS UNITS
KEYWORDS: NEW PERSON FILE
SUBSCRIBING PACKAGE: MYHEALTHEVET
 SUBSCRIBING DETAILS:   Used by Secure Messaging in MHV.  
  DATE ACTIVATED: JAN 29, 2015

NUMBER: 6156                            IA #: 6156
  DATE CREATED: JAN 28, 2015            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOTRI
  NAME: PSOTRI                          ID: PSOTRI
 GENERAL DESCRIPTION:   The ECME application requires the ability to create
 entries in the PSO Audit Log (#52.87) file by using the AUDIT^PSOTRI entry
 point that is already used internally by the Outpatient Pharmacy package.  
  STATUS: Active
KEYWORDS: TRICARE
KEYWORDS: CHAMPVA
KEYWORDS: BYPASS REPORT
KEYWORDS: OVERRIDE REPORT
KEYWORDS: AUDIT LOG
COMPONENT/ENTRY POINT: $$AUDIT(RX,RFL,RXCOB,JST,AUD,ELIG)
 COMPONENT DESCRIPTION:   This procedure is used to create entries in the PSO
 Audit Log (#52.87) file, which is the data source for the TRICARE CHAMPVA
 Bypass/Override Report.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Presciption (#52) file (required) 
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Prescription Fill # (Optional).  If not populated,
 the default is the original fill (0).  
VARIABLES: RXCOB                        TYPE: Input
 VARIABLES DESCRIPTION:   Coordination of Benefits indicator (optional) 
   1 = Primary (Default if not populated) 
   2 = Secondary 
VARIABLES: JST                          TYPE: Input
 VARIABLES DESCRIPTION:   Justification text (optional) 
VARIABLES: AUD                          TYPE: Input
 VARIABLES DESCRIPTION:   Audit Type (required) 
   R = NCPDP REJECT 
   N = NON BILLABLE 
   I = INPATIENT 
   P = PARTIAL FILL 
VARIABLES: ELIG                         TYPE: Input
 VARIABLES DESCRIPTION:   Eligibility Type (required) 
   T = TRICARE 
   C = CHAMPVA 
VARIABLES: $$AUDIT                      TYPE: Output
 VARIABLES DESCRIPTION:   Successful audit entry will return the IEN of the new
 entry.  Unsuccessful Audit entry will return "0^Error Description".  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: FEB 02, 2015

NUMBER: 6157                            IA #: 6157
  DATE CREATED: FEB 05, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XLFSHAN
  NAME: XLFSHAN                         ID: XLFSHAN
 GENERAL DESCRIPTION:   This DBIA describes supported references in the routine
 XLFSHAN which provides Kernel APIs for Secure Hash Algorithm (SHA) hashing of
 input of various formats.  
  
 Federal Information Processing Standards Publication 180-4 (FIPS PUB 180-4)
 specifies secure hash algorithms for computing a condensed representation of
 electronic data (message). The hash algorithms specified in this Standard are
 called secure because, for a given algorithm, it is computationally infeasible
 1) to find a message that corresponds to a given message digest, or 2) to find
 two different messages that produce the same message digest. Any change to a
 message will, with a very high probability, result in a different message
 digest.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: KERNEL
KEYWORDS: LOGIC
KEYWORDS: MATH
KEYWORDS: SHA
COMPONENT/ENTRY POINT: FILE
 COMPONENT DESCRIPTION:   This extrinsic function returns the SHA hash for a
 specified file entry.  It uses the FileMan API GETS^DIQ to extract the data
 from the file. The input parameters match the input parameters for GETS^DIQ.
 For complete details see the VA FileMan Developers Guide.  
  
 Format:  $$FILE^XLFSHAN(HASHLEN,FILENUM,IENS,[FIELD],[FLAGS]) 
                 
 The value returned is the SHA hash if successful, or "0" if the file could not
 be opened/found.  
VARIABLES: FILENUM                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File or subfile number.  
VARIABLES: IENS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Standard IENS indicating internal entry
 numbers, as documented in the VA FileMan Developers Guide.  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) See the GETS^DIQ documentation for
 possible values. If this is not passed it defaults to "**" which extracts all
 fields.  
VARIABLES: FLAGS                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) See the GETS^DIQ documentation for
 possible values.  
VARIABLES: HASHLEN                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The hash length in bits: 
   160 (SHA-1) 
   224 (SHA-224) 
   256 (SHA-256) 
   384 (SHA-384) 
   512 (SHA-512) 
COMPONENT/ENTRY POINT: HOSTFILE
 COMPONENT DESCRIPTION:   This extrinsic function returns the SHA hash of the
 specified host file.  It uses $$FTG^%ZISH to load the host file for
 processing.  
  
 Format:  $$HOSTFILE^XLFSHAN(HASHLEN,PATH,FILENAME) 
  
 The value returned is the SHA hash if successful, or "0" if the hostfile could
 not be opened/found.  
VARIABLES: PATH                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Full patch, up to but not including the
 filename.  
VARIABLES: FILENAME                     TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Name of the file.  
VARIABLES: HASHLEN                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The hash length in bits: 
   160 (SHA-1) 
   224 (SHA-224) 
   256 (SHA-256) 
   384 (SHA-384) 
   512 (SHA-512) 
COMPONENT/ENTRY POINT: ROUTINE
 COMPONENT DESCRIPTION:   This extrinsic function returns the SHA hash of a
 routine.  
  
 Format:  $$ROUTINE^XLFSHAN(HASHLEN,ROUTINE) 
  
 The value returned is the SHA hash if successful, or "0" if the routine could
 not be opened/found.  
VARIABLES: ROUTINE                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The name of the routine.  
VARIABLES: HASHLEN                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The hash length in bits: 
   160 (SHA-1) 
   224 (SHA-224) 
   256 (SHA-256) 
   384 (SHA-384) 
   512 (SHA-512) 
COMPONENT/ENTRY POINT: LSHAN
 COMPONENT DESCRIPTION:   This extrinsic function returns the SHA hash of a
 message that is too long to be passed as a single string. The message is
 passed in ^TMP($J,MSUB).  The message should be broken into blocks that are
 exactly 64 bytes/characters long except for the last one. ^TMP($J,MSG,N) is
 the Nth block of the message, where N runs from 1 to NBLOCKS.  
  
 Format:  $$LSHAN^XLFSHAN(HASHLEN,MSUB,NBLOCKS) 
  
 The value returned is the SHA hash of the message.  
VARIABLES: MSUB                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The ^TMP($J,MSUB) subscript in which the
 message is passed.  
VARIABLES: NBLOCKS                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The number of blocks in the message.  
VARIABLES: HASHLEN                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The hash length in bits: 
   160 (SHA-1) 
   224 (SHA-224) 
   256 (SHA-256) 
   384 (SHA-384) 
   512 (SHA-512) 
COMPONENT/ENTRY POINT: SHAN
 COMPONENT DESCRIPTION:   This extrinsic function returns the SHA hash of a
 message that can be passed in a single string.  
  
 Format:  $$SHAN^XLFSHAN(HASHLEN,MESSAGE) 
  
 The value returned is the SHA hash of the message.  
VARIABLES: MESSAGE                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The message string.  
VARIABLES: HASHLEN                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The hash length in bits: 
   160 (SHA-1) 
   224 (SHA-224) 
   256 (SHA-256) 
   384 (SHA-384) 
   512 (SHA-512) 
COMPONENT/ENTRY POINT: AND
 COMPONENT DESCRIPTION:   Bitwise logical AND of two 32 bit integers.  
  
 Format:  $$AND^XLFSHAN(X,Y) 
  
 The value returned is the bitwise logical AND.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) An integer of 32 bits or less.  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) An integer of 32 bits or less.  
COMPONENT/ENTRY POINT: XOR
 COMPONENT DESCRIPTION:   Bitwise logical XOR of two 32 bit integers.  
  
 Format:  $$XOR^XLFSHAN(X,Y) 
  
 The value returned is the bitwise logical XOR.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) An integer of 32 bits or less.  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) An integer of 32 bits or less.  
COMPONENT/ENTRY POINT: OR
 COMPONENT DESCRIPTION:   Bitwise logical OR of two 32 bit integers.  
  
 Format:  $$OR^XLFSHAN(X,Y) 
  
 The value returned is the bitwise logical OR.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) An integer of 32 bits or less.  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) An integer of 32 bits or less.  
COMPONENT/ENTRY POINT: GLOBAL
 COMPONENT DESCRIPTION:   This extrinsic function returns the SHA-256 hash of
 the specified global, in contrast with $$FILE which returns the hash for a
 particular entry in a global.  
  
 Format:  $$GLOBAL^XLFSHAN(HASHLEN,FILENUM,DATAONLY) 
  
 Using file #5, this is what a portion of the text for which the hash is 
 computed looks like: 
  
   DATAONLY=0 
     ^DIC(5,110,0)=YUKON TERRITORY^YT^83^^1^0 
     ^DIC(5,110,1,0)=^5.01I^1^1 
     ^DIC(5,110,1,1,0)=YUKON TERRITORY^^260 
     ^DIC(5,110,1,"B","YUKON TERRITORY",1)= 
     ^DIC(5,110,1,"C",260,1)= 
  
   DATAONLY=1 
     YUKON TERRITORY^YT^83^^1^0 
     ^5.01I^1^1 
     YUKON TERRITORY^^260 
  
 The value returned is the SHA hash if successful, or "0" if the global does
 not exist.  
VARIABLES: FILENUM                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File number.  
VARIABLES: DATAONLY                     TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Scope of the hash. 
    0 - the global location of the data is to 
        be included in the hash computation.  
    1 - the hash is computed only for the data.  
VARIABLES: HASHLEN                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The hash length in bits: 
   160 (SHA-1) 
   224 (SHA-224) 
   256 (SHA-256) 
   384 (SHA-384) 
   512 (SHA-512) 
COMPONENT/ENTRY POINT: CPUTIME
 COMPONENT DESCRIPTION:   This extrinsic function returns two comma-delimited
 pieces, "system" CPU time and "user" CPU time (except of VMS where no separate
 times are available).  
  
 Format: $$CPUTIME^XLFSHAN() 
  
 The value returned is time measured as milliseconds of CPU time.  
COMPONENT/ENTRY POINT: ETIMEMS
 COMPONENT DESCRIPTION:   Calculates the elapsed time in milliseconds.  
  
 Format:  $$ETIMEMS^XLFSHAN(START,END) 
  
 Returns the elapsed time in milliseconds.  
VARIABLES: START                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The starting CPU time, set by calling
 $$CPUTIME.  
VARIABLES: END                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The ending CPU time, set by calling
 $$CPUTIME.  
COMPONENT/ENTRY POINT: GENAREF
 COMPONENT DESCRIPTION:   This extrinsic function returns the SHA hash for a
 general array or global.  
  
 Format:  $$GENAREF^XLFSHAN(HASHLEN,AREF,DATAONLY) 
  
 The value returned is the SHA hash of the array or global.  
VARIABLES: HASHLEN                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The hash length in bits: 
   160 (SHA-1) 
   224 (SHA-224) 
   256 (SHA-256) 
   384 (SHA-384) 
   512 (SHA-512) 
VARIABLES: AREF                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The starting array reference, for example
 ABC or ^TMP($J,"XX").  
VARIABLES: DATAONLY                     TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Scope of the hash.  
   0 - the array location of the data is to 
       be included in the hash computation.  
   1 - the hash is computed only for the data.  
  DATE ACTIVATED: DEC 19, 2017

NUMBER: 6158                            IA #: 6158
  FILE NUMBER: 403.54                   GLOBAL ROOT: SD(
  DATE CREATED: FEB 12, 2015            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  NAME: MBAA Read Access to Recall Reminders Providers File
  ID: SD(
GLOBAL REFERENCE: SD(403.54,D0
FIELD NUMBER: 6                         FIELD NAME: KEY
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Scheduling Calendar View Mobile App (MBAA
 namespace) needs to read the Recall Reminders Providers File (#403.54) to look
 up what security keys are required for a provider to use the recall reminders. 
  
 This is used by the MBAA RPC MBAA REMOVE FROM RECALL LIST, in routine 
 MBAARPC1, line tag REMREC. A FileMan read is made to the file to get the 
 security key (Field #6, KEY) needed for a user to enter or edit a recall 
 reminder for the specified provider.  
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE

NUMBER: 6159                            IA #: 6159
  DATE CREATED: FEB 18, 2015            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: MAG4 ADD IMAGE                  REMOTE PROCEDURE: MAG4 ADD IMAGE
  STATUS: Withdrawn
KEYWORDS: VPS
KEYWORDS: ADD
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) After Visit Summary (AVS)
 integration has a need to store AVS PDF file to Imaging Server. It requires
 the MAG4 ADD IMAGE to add the AVS Image entry to the IMAGE File ^MAG(2005 

NUMBER: 6160                            IA #: 6160
  DATE CREATED: FEB 18, 2015            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: MAG3 TIU IMAGE                  REMOTE PROCEDURE: MAG3 TIU IMAGE
  STATUS: Withdrawn
KEYWORDS: VPS
KEYWORDS: TIU
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) After Visit Summary (AVS)
 integration has a need to store AVS PDF file to Imaging Server. It requires
 the MAG3 TIU IMAGE to link the AVS Image pointer to TIU pointer in both
 Imaging and TIU note.  

NUMBER: 6161                            IA #: 6161
  DATE CREATED: FEB 18, 2015            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: MAG4 IMAGE LIST                 STATUS: Withdrawn
KEYWORDS: VPS
KEYWORDS: LIST
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) After Visit Summary (AVS)
 integration has a need to retrieve AVS PDF file from Imaging Server. It
 requires the MAG4 IMAGE LIST to return list of images' information based on
 provided criteria.  

NUMBER: 6162                            IA #: 6162
  DATE CREATED: FEB 18, 2015            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGBAPIP
  NAME: MAGBAPIP                        ID: MAGBAPIP
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: MAGBAPIP
COMPONENT/ENTRY POINT: $$DA2PLC
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) After Visit Summary (AVS)
 integration has a need to retrieve AVS PDF file from Imaging Server. Given
 Image IEN, it requires the $$DA2PLC^MAGBAPIP to get the location of the AVS
 PDF file.  
  DATE ACTIVATED: APR 03, 2015

NUMBER: 6163                            IA #: 6163
  DATE CREATED: FEB 18, 2015            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGBAPI
  NAME: MAGBAPI                         ID: MAGBAPI
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: MAGBAPI
COMPONENT/ENTRY POINT: $$GCC
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) After Visit Summary (AVS)
 integration has a need to retrieve AVS PDF files from Imaging Server. Given
 the Image IEN, location, Image file extension (optional), it requires the
 $$GCC^MAGBAPI to add an export/copy request to Background Processor Queue to
 retrieve AVS PDF file from Imaging Server and store in a shared location.  
  DATE ACTIVATED: APR 03, 2015

NUMBER: 6164                            IA #: 6164
  DATE CREATED: FEB 24, 2015            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: WVRPCPT
  NAME: RETRIEVE PATIENT'S PREGNANCY/LACTATION DATA
  ID: WVRPCPT
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to retrieve data from the Women's Health package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PREGNANCY DATA
KEYWORDS: LACTATION DATA
COMPONENT/ENTRY POINT: GETDATA(RESULT,WVDFN,WVTYPE,WVSDATE,WVEDATE,WVMAX,WVDIR,W
VDT)
 COMPONENT DESCRIPTION:   This entry point will return data of the requested
 type from the WV PATIENT file (#790).  
VARIABLES: RESULT                       TYPE: Input
 VARIABLES DESCRIPTION:   The subscript in the ^TMP global under which to
 return data or error messages. This value is required.  
VARIABLES: WVDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient in the WV
 PATIENT file (#790). This value is required.  
VARIABLES: WVTYPE                       TYPE: Input
 VARIABLES DESCRIPTION:   The type of data to return. Valid values include: 
   "P" for pregnancy data 
   "L" for lactation data 
  
 This value is required.  
VARIABLES: WVSDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   For date/time-based data, return data entered on or
 after this date. The value must be in FileMan internal date/time format and is
 optional.  
VARIABLES: WVEDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   For date/time-based data, return data entered on or
 before this date. The value must be in FileMan internal date/time format and
 is optional.  
VARIABLES: WVMAX                        TYPE: Input
 VARIABLES DESCRIPTION:   The maximum number of entries to return. This value
 is optional.  
VARIABLES: WVDIR                        TYPE: Input
 VARIABLES DESCRIPTION:   The date/time order in which to return entries. Valid
 values include: 
   1 for chronological order 
   -1 for reverse chronological order.  
  
 This value is optional and if undefined, data is returned in reverse 
 chronological order.  
VARIABLES: WVDT                         TYPE: Input
 VARIABLES DESCRIPTION:   The date to use as today's date. The value must be in
 internal FileMan date/time format and is optional. If undefined, the value
 stored in the DT system variable is used.  
VARIABLES: TMP(RESULT,$J)               TYPE: Output
 VARIABLES DESCRIPTION:   The global node in which data is returned.  
  
 Format: 
  
 ^TMP(RESULT,$J)=Caret-delimited string 
   RESULT - the value in the RESULT input variable 
   Caret-delimited string - status of the call to 
                            GETDATA 
  PIECE   VALUE 
 =======================
  1       -1 to denote an error occurred 
          >-1 to denote the number of entries 
          returned 
  2       ERROR MESSAGE if an error occurred 
          "" if no error occurred 
  
 ^TMP(RESULT,$J,N,"FIELD NAME")=Caret-delimited 
                                   string 
   RESULT - the value in the RESULT input variable 
   N - the entry number; starts at one and 
       increments by one 
   "FIELD NAME" - the name of the field from which 
                  the data comes 
   Caret-delimited string - the returned data 
  PIECE   VALUE 
 =======================
  1       Internal format 
  2       External format 
   NOTE: Two pseudo-fields are returned whose 
         value is not caret-delimited like the 
         other "FIELD NAME" subscripts. These 
         fields are: 
         "RECORD ID":  FileMan IENS for record N 
         "VISIT STRING": Semi-colon delimited 
                         string of values from 
                         the VISIT file (#9000010) 
                         in internal format: 
             "HOSPITAL LOCATION (#.22) ; 
               VISIT/ADMIT DATE&TIME (#.01) ; 
               ENCOUNTER TYPE (#15003)" 
COMPONENT/ENTRY POINT: GETSTATUS(WVDFN)
 COMPONENT DESCRIPTION:   Returns text containing a patient's pregnancy and
 lactation status in a format that is suitable for display to the user.  
VARIABLES: WVDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient in the WV
 PATIENT file (#790). This value is required.  
VARIABLES: $$GETSTATUS                  TYPE: Output
 VARIABLES DESCRIPTION:   String containing user-friendly text. Text is only
 returned if the patient is pregnant, lactating or both. An empty string is
 returned if the patient is neither pregnant nor lactating.  
COMPONENT/ENTRY POINT: GETEDD(WVDFN)
 COMPONENT DESCRIPTION:   Returns text suitable for display to the user
 containing the patient's expected due date and if applicable, the fetus'
 gestational age.  
VARIABLES: WVDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient in the WV
 PATIENT file (#790). This value is required.  
VARIABLES: $$GETEDD                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns the string "~@" followed by the global
 location where the text to display is returned. The location uses the same
 structure as the FileMan word processing type. Each line of text to display is
 returned in the 0 (zero) node descendent from the line number node. The first
 line number is one and each subsequent line number is incremented by one.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: HEALTH SUMMARY
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Patch WV*1*26 introduces a new component (GETSTATUS)
 that Outpatient Pharmacy will begin using in its medication profile.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Patch WV*1*26 introduces a new component (GETEDD) that
 Text Integration Utilities will begin using in its VA-WH EXPECTED DUE DATE
 object.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Added 7/7/25 effective with Patch PSJ*5*461 As part of 
 the Methadone Dispensing Tracking Project, will have to make a call to
 $$GETSTATUS^WVRPCPT to check the patient's pregnancy and lactation status.  
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   Added 3/27/26 effective with Patch EHM*1*20.  EHM*1*20
 produces two (2) lists: 1) patients who are currently pregnant and 2) patients
 who are post-partum within the last year.  They are used during conversion to
 the new Federal EHR.  
  DATE ACTIVATED: NOV 17, 2017

NUMBER: 6165                            IA #: 6165
  DATE CREATED: FEB 24, 2015            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: WVRPCPT
  NAME: UPDATE PATIENT DATA             ID: WVRPCPT
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to add or update data in a subset of files and fields. These files and fields
 are: 
  
   WVPATIENT (#790) 
     CX TX NEED (#.11) 
     CX TX NEED DUE DATE (#.12) 
     BR TX NEED (#.18) 
     BR TX NEED DUE DATE (#.19) 
     PREGNANCY STATUSES (#40), as file #790.05 
       All fields 
     LACTATION STATUSES (#50), as file #790.16 
       All fields 
   WV PROCEDURE (#790.1) 
     PROCEDURE (#.04) 
     RESULTS/DIAGNOSIS (#.05) 
     OUTSIDE REPORT (#.36) 
     COMMENTS (#3.01) 
     PROCEDURE ACTIONS (#10), as file #790.23 
   WV NOTIFICATION (#790.4) 
     All fields 
   WV PREGNANCY/LACTATION STATUS CONFLICT EVENTS (#790.9) 
     DATE/TIME OCCURRED (#.01) 
  
 Subscribers of this agreement should also subscribe to agreement #6166 UPDATE
 PATIENT DATA VERIFICATION. The proper calling order for these agreements is to
 first call the application programming interface (API) documented in agreement
 #6166 to verify the WVDATA array is valid and well-constructed then call the
 API in this agreement to save the data in the WVDATA array.  
  
 This API is transactional in nature. If the subscriber needs to both update
 existing data and add new data, then the subscriber needs to call this API
 twice: once for the update and once for the add.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PREGNANCY DATA
KEYWORDS: LACTATION DATA
COMPONENT/ENTRY POINT: SAVEDATA(WVRETURN,WVDATA)
 COMPONENT DESCRIPTION:   This entry point will save new or update existing
 data.  
VARIABLES: WVRETURN                     TYPE: Both
 VARIABLES DESCRIPTION:   Reference to the array in which to return the
 SAVEDATA call status.  
  
 Format: 
  
 WVRETURN(1)=Caret-delimited string 
   Caret-delimited string - status of the call to 
                            SAVEDATA 
  PIECE   VALUE 
 ==========================
  1       -1 to denote an error occurred 
          1 to denote that the call was successful 
  2       ERROR MESSAGE if an error occurred 
          "" if no error occurred 
VARIABLES: WVDATA                       TYPE: Input
 VARIABLES DESCRIPTION:   Reference to an array containing the data to save.  
  
 Format: 
  
 WVDATA("DFN")=Internal entry number (IEN) 
               in the WV PATIENT file (#790) 
               of the patient associated with 
               the data WVDATA("DATA",FILE,RECORD_ID,SUBSCRIPT)=VALUE 
   FILE - The file number in which to save the 
          data.  
   RECORD_ID - The ID of this record in FileMan 
               IENS format. When adding new 
               records, there should only be 
               one comma-delimited value for 
               the RECORD_ID. For example, 
               "+1,". When updating existing 
               records, the RECORD_ID should 
               be the full IENS string.  
   SUBSCRIPT - The number of the field within 
               the FILE in which to save the 
               data or one of the following 
               values: 
                "NAME" => This subscript 
                          indicates the name of 
                          the reminder cascade 
                          from file #809, which 
                          is stored in VALUE.  
                          When using this 
                          subscript, FILE should 
                          equal 790 and 
                          RECORD_ID should equal 
                          "+1,".  
                "PRINTER" => This subscript 
                             indicates the IEN 
                             of the entry in 
                             the DEVICE file 
                             (#3.5) of the 
                             VistA printer to 
                             print letters on, 
                             which is stored in 
                             VALUE. When using 
                             this subscript, FILE 
                             should equal 790.404 
                             and RECORD_ID should 
                             equal "+1,".  
   VALUE - The data value to either store in 
           external format (when SUBSCRIPT is 
           the number of a field within FILE) 
           or data that is used by this API in 
           performing an action (see the 
           SUBSCRIPT description above).  
   WVDATA("DATA",FILE,"MASTER ID")=ID 
     ID - partial IENS string or a colon- 
          delimited list of identifiers. For 
          partial IENS string, this value is 
          required when adding new records and 
          should include all record IENS above 
          the level of FILE. This value is 
          optional when updating existing records 
          and should include all record IENs at 
          and above the level of FILE (unless 
          FILE is a sub-file, in which case the 
          value should include all record IENs 
          above the level of FILE). When 
          specified, this IENS string is 
          concatenated to the incomplete 
          RECORD_ID value to create a complete 
          IENS string.  
   WVDATA("VISIT")=Text Integration Utilities 
                   (TIU) visit string (semi-colon 
                   delimited string of values 
                   from the VISIT file, #9000010).  
     PIECE   VALUE 
    ==========================
     1       IEN in the HOSPITAL LOCATION file 
             (#44) 
     2       VISIT/ADMIT DATE&TIME field (#.01) in 
             internal FileMan format 
     3       SERVICE CATEGORY field (#.07) value 
             in internal format 
   WVDATA("DOCUMENT")=The IEN of the document in 
                      the TIU DOCUMENT file 
                      (#8925) associated with the 
                      data to save or update.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: NOV 17, 2017

NUMBER: 6166                            IA #: 6166
  DATE CREATED: FEB 24, 2015            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: WVRPCPT2
  NAME: UPDATE PATIENT DATA VERIFICATION
  ID: WVRPCPT2
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to verify the data to send to the application programming interface (API)
 documented in agreement #6165 is valid and well-constructed.  
  
 Subscribers of this agreement should also subscribe to agreement #6165 UPDATE
 PATIENT DATA. The proper calling order for these agreements is to first call
 the API documented in this agreement to verify the data to save then call the
 API documented in agreement #6165 to save the data that was verified.  
  
 This API is transactional in nature. If the subscriber needs to both update
 existing data and add new data, then the subscriber needs to call this API
 twice: once for the update and once for the add.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PREGNANCY DATA
KEYWORDS: LACATATION DATA
KEYWORDS: DATA VERIFICATION
COMPONENT/ENTRY POINT: VERDATA(WVRETURN,WVDATA)
 COMPONENT DESCRIPTION:   This entry point will verify that the data in the
 WVDATA array is valid and well-constructed.  
VARIABLES: WVRETURN                     TYPE: Both
 VARIABLES DESCRIPTION:   Reference to the array in which to return the VERDATA
 call status.  
  
 Format: 
  
 WVRETURN(0)=Caret-delimited string 
   Caret-delimited string - status of the call to 
                            VERDATA 
  PIECE   VALUE 
 ==========================
  1       -1 to denote that the data is not valid 
          1 to denote that the data is valid 
  2       ERROR MESSAGE if there is a problem 
          with the call itself 
          "" if there is no problem with the call 
  
 WVRETURN(N)=MESSAGE 
   N - number of the validity issue; starts at one 
       and increments by one 
   MESSAGE - description of the validity issue in 
             a user-friendly format 
VARIABLES: WVDATA                       TYPE: Input
 VARIABLES DESCRIPTION:   Reference to an array containing the data to verify.
 Refer to agreement #6165 for how to structure this array.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: NOV 17, 2017

NUMBER: 6167                            IA #: 6167
  GLOBAL ROOT: DD(409.68                DATE CREATED: MAR 02, 2015
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS TO DD(409.68        ID: DD(409.68
GLOBAL REFERENCE: DD(409.68,.08,0)
 GENERAL DESCRIPTION:   Scheduling requests read access to ^DD(409.68,.08,0). 
 This reference is in legacy code that is missing an ICR.  It is retrieving the
 external value for a code in OUTPATIENT ENCOUNTER (#409.68) file, ORIGINATING 
 PROCESS TYPE (#.08) field.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   3/26/15-For PCMM Web 
  DATE ACTIVATED: MAR 27, 2015

NUMBER: 6168                            IA #: 6168
  GLOBAL ROOT: DD(404.52                DATE CREATED: MAR 02, 2015
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS TO DD(404.52        ID: DD(404.52
 GENERAL DESCRIPTION:   This is a onetime agreement via patch SD*5.3*603.  
 Scheduling requests read access to ^DD(404.52,.09,1,2,0). The post-install 
 routine, SD53P603, in SD*5.3*603 will delete the FTEXR trigger cross-reference
 on the POSITION ASSIGNMENT HISTORY (#404.52) file, FTEE EQUIVALENT (#.09)
 field. Access to the ^DD(404.52 global is required to verify the cross
 reference is present and the correct number prior to deleting it.  
  
 Entry point in SD53P603: DELTRIGR        ;Delete FTEE History trigger in
 404.52 
  ;
  NEW SDERR 
  DO BMES^XPDUTL("Delete the FTEXR Trigger in 404.52/.09") 
  ;
  IF $DATA(^DD(404.52,.09,1,2,0)),^DD(404.52,.09,1,2,0)["FTEXR" DO 
  . DO DELIX^DDMOD(404.52,.09,2,"","SDERR") 
  . IF '$DATA(SDERR) DO 
  . . DO BMES^XPDUTL("The FTEXR trigger was deleted.") 
  . ELSE  DO 
  . . DO BMES^XPDUTL("ERROR encountered deleting the trigger.") 
  ELSE  DO 
  . DO BMES^XPDUTL("The FTEXR trigger does not exist - previously deleted.") 
  QUIT 
  ;
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: MAR 27, 2015

NUMBER: 6169                            IA #: 6169
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: MAR 03, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ/WRITE ACCESS TO NEW PERSON FILE
  ID: VA(200
GLOBAL REFERENCE: VA(200,D0
GLOBAL REFERENCE: VA(200,D0,203,D1
FIELD NUMBER: 203                       FIELD NAME: SECONDARY MENU OPTIONS
  LOCATION: 203;0                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: VA(200,D0,203,D1,0
FIELD NUMBER: .01                       FIELD NAME: SECONDARY MENU OPTIONS
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   This is a onetime agreement via patch SD*5.3*603.  
  
 Post install processing looks for users that have a secondary menu option of
 SCMC PCMM GUI WORKSTATION (legacy PCMM broker menu) and changes it to SCMC
 PCMMR WEB USER MENU (PCMM Web broker menu).  
  
 Scheduling (PCMM Web) requests read access to the NEW PERSON (#200) file to
 $ORDER through the records, $ORDER through SECONDARY MENU OPTIONS (#200.03)
 multiple, then FileMan API ($$GET1^DIQ) to interrogate the value of the
 SECONDARY MENU OPTIONS (.01) field.  If it resolves to SCMC PCMM GUI
 WORKSTATION, then we request write access to change the value to SCMC PCMMR
 WEB USER MENU using FileMan API FILE^DIE.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: MAR 27, 2015

NUMBER: 6170                            IA #: 6170
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: MAR 03, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: READ ACCESS TO NEW PERSON DIVISION MULTIPLE
  ID: VA(200
GLOBAL REFERENCE: VA(200,D0,2,D1
 GENERAL DESCRIPTION:   Scheduling (PCMM Web) requests direct global read
 access to the NEW PERSON (#200) file, DIVISION (#16) multiple to $ORDER
 through a person's assigned Divisions.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 6171                            IA #: 6171
  FILE NUMBER: 18.12                    GLOBAL ROOT: XOB(18.12
  DATE CREATED: MAR 03, 2015            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ WRITE ACCESS TO WEB SERVER FILE
  ID: XOB(18.12
GLOBAL REFERENCE: XOB(18.12,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: PORT
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: .04                       FIELD NAME: SERVER
  LOCATION: 0;4                         ACCESS: Write w/Fileman
FIELD NUMBER: .06                       FIELD NAME: STATUS
  LOCATION: 0;6                         ACCESS: Write w/Fileman
FIELD NUMBER: .07                       FIELD NAME: DEFAULT HTTP TIMEOUT
  LOCATION: 0;7                         ACCESS: Write w/Fileman
FIELD NUMBER: 1.01                      FIELD NAME: LOGIN REQUIRED
  LOCATION: 1;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 3.01                      FIELD NAME: SSL ENABLED
  LOCATION: 3;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 100                       FIELD NAME: AUTHORIZED WEB SERVICES
  LOCATION: 100;0                       ACCESS: Write w/Fileman
GLOBAL REFERENCE: XOB(18.12,D0,100,D1
FIELD NUMBER: .01                       FIELD NAME: WEB SERVICE
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: .06                       FIELD NAME: STATUS
  LOCATION: 0;6                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   This request is for a one time use in patch SD*5.3*603
 post installation processing.  
  
 Scheduling (PCMM Web) requests read and write access to the WEB SERVER 
 (#18.12) file.  The post-install routine checks if the server record exists,
 then either creates or updates the record using either the UPDATE^DIE or
 FILE^DIE FileMan API calls, respectively.  In addition it adds an entry (if it
 doesn't exist) to the AUTHORIZED WEB SERVICES (#100) multiple, WEB SERVICE
 (#.01) field using the UPDATE^DIE FileMan API.  
  
 This processing is done programmatically to avoid having sites manually 
 configure HWSC using the Web Server Manager.  
  
 Revision History: 
  - 3/18/24, effective with Kernel patch XU*8*802 which was released to support
 WEB SERVER, EXPIRATION DATE of ICR reflects JAN 7,2025.  
  - 8/21/24, effective with patch SD*5.3*884 the Scheduling application is 
 requesting a one-time use in the SD*5.3*884 patch post installation processing
 to create 2 new entries in the WEB SERVER (#18.12) file.  The post-install
 routine SDES884P will add two entries to the WEB SERVER (#18.12) file using
 UPDATE^DIE: 1.      To connect SD VVS WEB SERVER TEST to the VVS system from
 VistA Test accounts.  2.      To connect SD VVS WEB SERVER to the VVS system
 from VistA Production accounts.  
   This processing is done programmatically to avoid having sites manually 
 configure the VVS interface manually using the Web Server Manager.  
    GLOBAL REFERENCE: 
      ^XOB(18.12,D0 
        .01      NAME    0;1      Write w/Fileman 
        .04      SERVER  0;4      Write w/Fileman 
        .06      STATUS  0;6      Write w/Fileman 
        .07      DEFAULT HTTP TIMEOUT           0;7      Write w/Fileman 
        3.01     SSL ENABLED                    3;1      Write w/Fileman 
        3.02     SSL CONFIGURATION              3;2      Write w/Fileman 
        3.03     SSL PORT                       3;3      Write w/Fileman 
        100      AUTHORIZED WEB SERVICES multiple   100;0 
                          .01 WEB SERVICE       0;1    Write w/Fileman 
                          .06 STATUS            0;6    Write w/Fileman 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 07, 2025
KEYWORDS: 18.12
KEYWORDS: XOBW
KEYWORDS: WEB SERVER FILE
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 8/21/24, effective with SD*5.3*884 (Added new
 file entries, see details in Revision History in Description of ICR) 
SUBSCRIBING PACKAGE: ONCOLOGY
 SUBSCRIBING DETAILS:   Added 10/12/23 to document pre-existing usage since
 Patch ONC*2.2*15, and updated SERVER (.04) in ONC*2.2*18 
  DATE ACTIVATED: MAR 13, 2015

NUMBER: 6172                            IA #: 6172
  FILE NUMBER: 18.13                    GLOBAL ROOT: XOB(18.13
  DATE CREATED: MAR 03, 2015            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: WRITE ACCESS TO WEB SERVER LOOKUP KEY FILE
  ID: XOB(18.13
GLOBAL REFERENCE: XOB(18.13,D0
FIELD NUMBER: .03                       FIELD NAME: ASSOCIATED WEB SERVER
  LOCATION: 0;3                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   This request is for a one time use in patch SD*5.3*603
 post installation processing.  
  
 Scheduling (PCMM Web) requests write access to the WEB SERVER LOOKUP KEY 
 (#18.13) file. The post-install routine creates the lookup key record using
 the supported $$SKEYADD^XOBWLIB API, and then updates the 18.13 record,
 ASSOCIATED WEB SERVER (#.03) field using the FILE^DIE FileMan API call.  
  
 This processing is done programmatically to avoid having sites manually 
 configure HWSC using the Web Server Manager.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 18.13
KEYWORDS: XOBW
KEYWORDS: WEB SERVER LOOKUP KEY
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: MAR 13, 2015

NUMBER: 6173                            IA #: 6173
  FILE NUMBER: 18.02                    GLOBAL ROOT: XOB(18.02
  DATE CREATED: MAR 03, 2015            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS TO THE WEB SERVICE FILE
  ID: XOB(18.02
GLOBAL REFERENCE: XOB(18.02,B
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This request is for a one time use in patch SD*5.3*603
 post installation processing.  
  
 Scheduling (PCMM Web) requests read access to the WEB SERVICE (#18.02) file.
 The post-install routine creates a WEB SERVICE record using the supported
 REGREST^XOBWLIB API, then reads the WEB SERVICE file with the $$FIND1^DIC
 FileMan API to get the IEN of the WEB SERVICE record. Then in further
 processing (reference ICR-6171) updates the WEB SERVER (#18.12) file,
 AUTHORIZED WEB SERVICES (#100) multiple.  
  
 This processing is done programmatically to avoid having sites manually 
 configure HWSC using the Web Server Manager.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 18.02
KEYWORDS: XOBW
KEYWORDS: WEB SERVICE FILE
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: MAR 13, 2015

NUMBER: 6174                            IA #: 6174
  DATE CREATED: MAR 05, 2015            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: WVRPCOR
  NAME: OE/RR APIS                      ID: WVRPCOR
 GENERAL DESCRIPTION:   This integration control registration allows
 subscribing packages to access pregnancy and lactation status data in a manner
 suitable for the Computerized Patient Record System (CPRS).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PREGNANCY DATA
KEYWORDS: LACTATION DATA
KEYWORDS: POSTINGS
COMPONENT/ENTRY POINT: POSTLIST(RETURN,DFN,LINE)
 COMPONENT DESCRIPTION:   Returns the list of postings for use in the Postings
 panel on the Cover Sheet tab, as well as the Patient Postings dialog.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient in the
 PATIENT file (#2).  
VARIABLES: LINE                         TYPE: Input
 VARIABLES DESCRIPTION:   Reference to a variable containing the starting
 subscript number of the postings to return.  
VARIABLES: RETURN                       TYPE: Both
 VARIABLES DESCRIPTION:   Reference to array in which to return the postings.  
COMPONENT/ENTRY POINT: $$POSTSHRT(DFN)
 COMPONENT DESCRIPTION:   Returns the letters to include in the Postings
 section in the CPRS header bar.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient in the
 PATIENT file (#2).  
VARIABLES: $$POSTSHRT                   TYPE: Output
 VARIABLES DESCRIPTION:   The letters to include in the Postings section.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Added 4/16/21 effective with TIU*1*341, part of the
 CPRS v31b follow-up bundle of patches.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 12/13/21 effective with Patch PSO*7*622, released
 on December 7, 2021, utilizes the POSTSHRT^WVRPCOR API documented in ICR #6174
 OE/RR APIS. 
  DATE ACTIVATED: NOV 17, 2017

NUMBER: 6175                            IA #: 6175
  DATE CREATED: MAR 05, 2015            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: PXRMRPCC PROMPTVL               REMOTE PROCEDURE: PXRMRPCC PROMPTVL
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call the PXRMRPCC PROMPTVL remote procedure call.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DIALOG PROMPT VALUE CALCULATOR
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 6176                            IA #: 6176
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870
  DATE CREATED: MAR 06, 2015            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HLCS 870 B CROSS REFERENCE
  ID: HLCS(870
GLOBAL REFERENCE: HLCS(870,'B',LINK,0)
GLOBAL REFERENCE: HLCS(870,IEN,400)
FIELD NUMBER: 400.02                    FIELD NAME: TCP/IP PORT
  LOCATION: 400;2                       ACCESS: Read w/Fileman
FIELD NUMBER: 400.08                    FIELD NAME: TCP/IP PORT (OPTIMIZED)
  LOCATION: 400;8                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VA POINT OF SERVICE (KIOSKS) uses the
 ^HLCS(870,"B",LINK,0) and ^HLCS(870,IEN,400) cross references to obtain the
 internal entry number of the VPS HL Logical Link and the ports for message
 transmission.  
  STATUS: Active
KEYWORDS: HLO
KEYWORDS: VPS
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA POINT OF SERVICE (KIOSKS) is providing patient
 appointment status HL7 messaging and needs to use the ^HLCS(870,"B",LINK,0)
 cross reference to read the IEN of the VPS HL Logical Link. The IEN read is
 used in global reference ^HLCS(870,IEN,400) to obtain the TCP/IP AND TCP/IP 
 (OPTIMIZED) to be used for the HL Logical Link.  
  DATE ACTIVATED: MAR 20, 2015

NUMBER: 6177                            IA #: 6177
  DATE CREATED: MAR 06, 2015            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: HLOQUE                       NAME: HLO DEQUE
  ID: HLOQUE                            STATUS: Withdrawn
KEYWORDS: HLO
KEYWORDS: DEQUE
KEYWORDS: VPS
COMPONENT/ENTRY POINT: DEQUE
VARIABLES: QNAME                        TYPE: Input
 VARIABLES DESCRIPTION:   The QNAME parameter is the name of the VPS HL7
 message queue to be purged.  
VARIABLES: DIR                          TYPE: Input
 VARIABLES DESCRIPTION:   The DIR parameter contains "IN" or "OUT" and
 specifies whether the message queue is an inbound or outbound queue.  
VARIABLES: IEN778                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN778 is the internal entry number of the message to
 be removed in file #778.  
VARIABLES: FROMORTO                     TYPE: Input
 VARIABLES DESCRIPTION:   FROMORTO is the .01 field of the VPS outgoing logical
 link.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VPS uses DEQUE^HLOQUE to purge stale messages from VPS
 HL7 outgoing message queues.  The routine is called as part of the queue
 preparation in PREPQUE^VPSSEND and removes VPS message IENs of purged message
 from file #778.  

NUMBER: 6178                            IA #: 6178
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: MAR 10, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: READ ACCESS TO NEW PERSON FILE B CROSS REFERENCE
  ID: VA(200
GLOBAL REFERENCE: VA(200,B
 GENERAL DESCRIPTION:   Scheduling (PCMM) requests read access to the B cross
 reference of the NEW PERSON (#200) file. The code in question will $ORDER
 through the cross reference looking for a name match to a passed parameter.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: NEW PERSON
KEYWORDS: VA(200,B
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 6179                            IA #: 6179
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(D0,0)
  DATE CREATED: MAR 10, 2015            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  NAME: VPS PAT PROVIDER AND ATTENDING  ID: DPT(D0,0)
GLOBAL REFERENCE: DPT(D0,.104)
FIELD NUMBER: .104                      FIELD NAME: PROVIDER
  LOCATION: .104;1                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(DP,.1041)
FIELD NUMBER: .1041                     FIELD NAME: ATTENDING PHYSICIAN
  LOCATION: .1041;1                     ACCESS: Read w/Fileman
  STATUS: Withdrawn
KEYWORDS: PATIENT
KEYWORDS: PROVIDER
KEYWORDS: ATTENDING PHYSICIAN
KEYWORDS: VPS
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (VPS) Kiosks has a need to read the
 PROVIDER, field .104, and the ATTENDING PHYSICIAN, field .1042, from PATIENT
 file #2.  VPS needs to return to the After Visit Summary (AVS) application the 
 provider and attending physician of clinic outpatient and ambulatory 
 inpatients.  

NUMBER: 6180                            IA #: 6180
  DATE CREATED: MAR 10, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWCV LAB                       REMOTE PROCEDURE: ORWCV LAB
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (VPS) Kiosks needs to provide the 
 list of patient labs as displayed on the CPRS GUI cover sheet to the After
 Visit Summary (AVS) J2EE application.  VPS needs to ensure that the data 
 provided to AVS is the same data that would be presented in the CPRS GUI.  

NUMBER: 6181                            IA #: 6181
  DATE CREATED: MAR 18, 2015            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  ROUTINE: SDAM2                        NAME: $$FIND API in SDAM2
  ID: SDAM2
 GENERAL DESCRIPTION:   To support delivery of the Insurance Verification
 Processor (IVP) project, which is part of Integrated Billing application,
 access to the API $$FIND^SDAM2() is requested in order to find all the
 appointments for a patient on a given date.  
  
 The input data will be 3 required data elements as follows: the patient's DFN,
 date/time of the appointment (FileMan format), and the clinic's internal entry
 number (IEN). The data of the input will be determined by the IVP software
 based on the IVP Daily Appointment Worklist information.  This API is called
 by IVP code to get IEN of the sub file (#44.003), which is required to call
 SDAMEVT APIs and to update the appointment entry properly.  
  
 Data input: 3 variables defined as follows: DFN - Patient's IEN from PATIENT
 file (#2) SDT - Date/Time for the appointment in the File Man format SDCL -
 clinic IEN from the HOSPITAL LOCATION FILE (#44) 
                        
 Data output ($$FIND return value): If 0, no appointment was found and the
 patient is notified.  If > 0, then applicable appointment for that day is
 passed back as IEN of the sub file (#44.003) of the sub file (#44.001) of the
 file (#44).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: IVP
COMPONENT/ENTRY POINT: $$FIND
 COMPONENT DESCRIPTION:   Returns appointment information for a patient and
 clinic on a given date.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient's DFN.  
VARIABLES: SDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Date/time for appointment in FileMan internal format. 
 
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the clinic.  
VARIABLES: $$FIND                       TYPE: Output
 VARIABLES DESCRIPTION:   IEN for the patient's appointment (if any) - IEN of
 the sub file (#44.003) of the sub file (#44.001) of the file (#44). Returns 0
 if not found.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 6182                            IA #: 6182
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: MAR 18, 2015            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  NAME: Update fields (#309) and (#302) in file #44
  ID: SC(
GLOBAL REFERENCE: SC(D0,S,D1,1
FIELD NUMBER: 302                       FIELD NAME: CHECK IN USER
  LOCATION: C;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 309                       FIELD NAME: CHECKED-IN
  LOCATION: C;1                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   To support delivery of the Insurance Verification
 Processor (IVP) project, which is part of Integrated Billing application,
 access to the fields (#309) and (#302) in the file #44 is requested in order
 to check-in the patient for a given appointment.  Both fields (#309)
 CHECKED-IN  and  (#302) CHECK IN USER of the file (#44) will be updated by the
 FileMan call, which is made by IVP RPC "IBVP CHECKIN APPOINTMENT "  at the
 time when IVP user check in the patient in IVP web application.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: IVP
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 6183                            IA #: 6183
  DATE CREATED: MAR 18, 2015            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  ROUTINE: SDAMEVT                      NAME: SDAMEVT APIs
  ID: SDAMEVT
 GENERAL DESCRIPTION:   The APIs will are used by IB to check-in the patient
 from the Insurance Verification Processor's GUI interface via IB RPC "IBVP
 CHECKIN APPOINTMENT "  call. The IB RPC will use HDLKILL^SDAMEVT,
 BEFORE^SDAMEVT, HANDLE^SDAMEVT, AFTER^SDAMEVT, and  EVT^SDAMEVT APIs to ensure
 that all other processes requiring notification of the check-in activity are 
 notified.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: IVP
COMPONENT/ENTRY POINT: BEFORE
 COMPONENT DESCRIPTION:   Capture ^SC( appointment data before processing the
 event.  
VARIABLES: SDATA                        TYPE: Input
 VARIABLES DESCRIPTION:   String with format
 "ApptIEN^PatDFN^ApptDate/Time^ClinicIEN^CurEvtHandle" 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Patient in file #2.  
VARIABLES: SDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's appointment date/time.  
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of clinic in HOSPITAL LOCATION file #44.  
VARIABLES: SDDA                         TYPE: Input
 VARIABLES DESCRIPTION:   IFN for ^SC(CLINIC,"S",DATE,1,IFN).  
VARIABLES: SDHDL                        TYPE: Input
 VARIABLES DESCRIPTION:   Event handle returned by HANDLE^SDAMEVT for and
 appointment event.  
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   Routine creates 2 temporary globals: 
         ^TMP("SDAMEVT",$J,"BEFORE") 
         ^TMP("SDEVT",$J,"BEFORE") and SDATA array element SDATA("BEFORE") 
COMPONENT/ENTRY POINT: AFTER
 COMPONENT DESCRIPTION:   Capture ^SC( appointment data after processing the
 event.  
VARIABLES: SDATA                        TYPE: Input
 VARIABLES DESCRIPTION:   String with format
 "ApptIEN^PatDFN^ApptDate/Time^ClinicIEN^CurEvtHandle" 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's IEN in PATIENT file 2.  
VARIABLES: SDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's appointment date/time.  
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of clinic in HOSPITAL LOCATION file 44.  
VARIABLES: SDDA                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of clinic in HOSPITAL LOCATION file 44.  
VARIABLES: SDHDL                        TYPE: Input
 VARIABLES DESCRIPTION:   Event handle returned by HANDLE^SDAMEVT for an
 appointment event.  
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   Routine creates 2 temporary globals: 
         ^TMP("SDAMEVT",$J,"AFTER") 
         ^TMP("SDEVT",$J,"AFTER") and SDATA array element SDATA("AFTER") 
COMPONENT/ENTRY POINT: HANDLE
 COMPONENT DESCRIPTION:   Get a handle for the current event.  
VARIABLES: SDORG                        TYPE: Input
 VARIABLES DESCRIPTION:   Originating transaction: 
         1=Appointment 
         2=Add/edit stop code 
         3=Registration/disposition 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Index into array element with value of 
 ^TMP("SDEVTHANDLE",$J).  
COMPONENT/ENTRY POINT: EVT
 COMPONENT DESCRIPTION:   Call the Scheduling event handlers in ^ORD(101.  
VARIABLES: SDATA                        TYPE: Input
 VARIABLES DESCRIPTION:   String in format
 "ApptIEN^PatDFN^ApptDate/Time^ClinicIEN^CurEvtHandle" 
VARIABLES: SDAMEVT                      TYPE: Input
 VARIABLES DESCRIPTION:   Literal value 4, corresponding to a check-in event.  
VARIABLES: SDMODE                       TYPE: Input
 VARIABLES DESCRIPTION:   Parameter with the conversation mode from caller 
         0=full dialogue 
         1=computer monologue 
         2=quiet 
VARIABLES: SDHDL                        TYPE: Input
 VARIABLES DESCRIPTION:   Event handle returned by HANDLE^SDAMEVT for an
 appointment event.  
COMPONENT/ENTRY POINT: HDLKILL
 COMPONENT DESCRIPTION:   Kill off handle data.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 6184                            IA #: 6184
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123,'AG'
  DATE CREATED: MAR 30, 2015
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: 'AG' Cross reference in Request/Consultation file
  ID: GMR(123,'AG'
GLOBAL REFERENCE: GMR(123,'AG'
 GLOBAL DESCRIPTION:   This cross reference contains entries of the
 REQUEST/CONSULTATION file sorted by DATE OF REQUEST that do not have an
 appointment scheduled.  This is determined based on the content and order of
 the entries in the REQUEST PROCESSING ACTIVITY multiple field 40.  This cross
 reference will be updated with any update to the ACTIVITY field under the
 REQUEST PROCESSING ACTIVITY multiple and that update will be determined based 
 on all REQUEST PROCESSING ACTIVITY entries. A Global read will be used to
 access the cross reference.  The "AG" cross reference is part of GMRC*3.0*83.  
 GENERAL DESCRIPTION:   This cross reference contains entries of the
 REQUEST/CONSULTATION file sorted by DATE OF REQUEST that do not have an
 appointment scheduled.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   The VistA Scheduling Enhancement (VSE) requests access
 to the 'NEW' style "AG" cross reference for REQUEST/CONSULTATION file 123.  
  DATE ACTIVATED: DEC 08, 2015

NUMBER: 6185                            IA #: 6185
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123
  DATE CREATED: MAR 30, 2015
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ACCESS DATA FROM REQUEST/CONSULTATION
  ID: GMR(123
GLOBAL REFERENCE: GMR(123,D0,0
FIELD NUMBER: .02                       FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the Patient who the consult or request was
 ordered for.  
FIELD NUMBER: 1                         FIELD NAME: TO SERVICE
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Pointer to the REQUEST SERVICES file 123.5 
FIELD NUMBER: 14
  FIELD NAME: SERVICE RENDERED AS IN OR OUT
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field allows the ordering person to indicate if the
 service is to be rendered on an outpatient or inpatient basis. This is to 
 alleviate the confusion if patient is currently an inpatient/outpatient but is
 just about to be discharged/admitted and become a outpatient/inpatient.  
FIELD NUMBER: 8                         FIELD NAME: CPRS STATUS
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the current CPRS status of the consult or request
 order.  The Action Types which may be taken from the "Select Action: " prompt 
 update the status in this file as well as in the Orders File (100).  
 GLOBAL DESCRIPTION:   This file contains consult and request orders
 originating primarily via the OE/RR ordering process.  Once the order exists
 in this file, receiving service users perform update tracking activities.  An
 audit trail of the update tracking activities is maintained in this file.  
  
 The only associating of results to a consult or request, for this version, is
 based on Medicine Package procedure results.  
GLOBAL REFERENCE: GMR(123,D0,20,D1,0
FIELD NUMBER: .01                       FIELD NAME: REASON FOR REQUEST
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Obtain REASON FOR REQUEST data to be returned to GUI.  
 GLOBAL DESCRIPTION:   Word Processing field.  
GLOBAL REFERENCE: GMR(123,D0,40,D1,0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME OF ACTION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Obtain DATE/TIME OF ACTION for this activity.  
FIELD NUMBER: 1                         FIELD NAME: ACTIVITY
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Obtain the ACTIVITY pointer.  
FIELD NUMBER: 2                         FIELD NAME: DATE/TIME OF ACTUAL ACTIVITY
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Obtain DATE/TIME OF ACTUAL ACTIVITY for this Activity.  
FIELD NUMBER: 3
  FIELD NAME: WHO'S RESPONSIBLE FOR ACTIVITY
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Obtain WHO'S RESPONSIBLE FOR ACTIVITY pointer.  
FIELD NUMBER: 4                         FIELD NAME: WHO ENTERED ACTIVITY
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Obtain WHO ENTERED ACTIVITY pointer.  
FIELD NUMBER: GMR(123,D0,40,D1,1        FIELD NAME: COMMENT
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is a word-processing comment which you may add to
 provide additional information in reference to the Action Type selected at the
 "Select Action: " prompt.  
 GLOBAL DESCRIPTION:   Obtain date for a given activity.  
GLOBAL REFERENCE: GMR(123,'AG'
 GLOBAL DESCRIPTION:   This cross reference contains entries of the
 REQUEST/CONSULTATION file 123, sorted by DATE OF REQUEST, that do not have an
 appointment scheduled.  This 'AG' cross reference is described in INTEGRATION
 REFERENCE 6184.  Direct global read on "AG" cross reference.  
GLOBAL REFERENCE: GMR(123,'E'
 GLOBAL DESCRIPTION:   Lookup Consults based on DATE OF REQUEST.  Direct global
 read on "E" cross reference.  
GLOBAL REFERENCE: GMR(123,'AD'
 GLOBAL DESCRIPTION:   The "AD" cross-reference allows look up of patient
 consults in reverse chronological "DATE OF REQUEST" order.  Direct global read
 on "AD" cross reference.  
GLOBAL REFERENCE: GMR(123,'H'
 GLOBAL DESCRIPTION:   This cross-reference allows the location that sent the 
 consult to track what happened to their consults.  Direct global read on "H"
 cross reference.  
 GENERAL DESCRIPTION:   The VistA Scheduling Enhancement (VSE) requests
 permission to access the REQUEST/CONSULTATION file 123 in order to obtain data
 to be returned to the GUI.  The "AD", "AG", "E", and "H" cross references will
 be used for lookup.  Note that the "AG" cross reference is added in
 GMRC*3.0*83.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   The VistA Scheduling Enhancement (VSE) requests
 permission to access the REQUEST/CONSULTATION file 123 in order to obtain data
 to be returned to the GUI.  The "AD", "AG", "E", and "H" cross references will
 be used for lookup.  Access to the cross references will be done with global
 reads.  Any field reads and writes will be done via FileMan.  Note that the
 "AG" cross reference is added in GMRC*3.0*83.  
  DATE ACTIVATED: DEC 08, 2015

NUMBER: 6186                            IA #: 6186
  FILE NUMBER: 123.1                    GLOBAL ROOT: GMR(123.1
  DATE CREATED: MAR 30, 2015
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Lookup REQUEST ACTION TYPES
  ID: GMR(123.1
 GENERAL DESCRIPTION:   The VistA Scheduling Enhancement (VSE) requests 
 permission to access the REQUEST ACTION TYPES file 123.1 using the ^DIC
 FileMan call in order to obtain internal IDs using a given REQUEST ACTION
 TYPES name.  These IDs will be used in searching the REQUEST/CONSULTATION file 
 for REQUEST PROCESSING ACTIVITY entries based on the ACTIVITY field (pointer
 to REQUEST ACTION TYPES file).  No field reads will be needed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   The VistA Scheduling Enhancement (VSE) requests 
 permission to access the REQUEST ACTION TYPES file 123.1 using the ^DIC
 FileMan call in order to obtain internal IDs using a given REQUEST ACTION
 TYPES name.  These IDs will be used in searching the REQUEST/CONSULTATION file 
 for REQUEST PROCESSING ACTIVITY entries based on the ACTIVITY field (pointer
 to REQUEST ACTION TYPES file).  No field reads will be needed.  
  DATE ACTIVATED: DEC 07, 2015

NUMBER: 6187                            IA #: 6187
  FILE NUMBER: 123.5                    GLOBAL ROOT: GMR(123.5
  DATE CREATED: MAR 30, 2015
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  NAME: Get ASSOCIATED STOP CODE list   ID: GMR(123.5
GLOBAL REFERENCE: GMR(123.5,D0,688,D1,0
FIELD NUMBER: .01                       FIELD NAME: ASSOCIATED STOP CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Obtain ASSOCIATED STOP CODE pointers.  
 GENERAL DESCRIPTION:   The VistA Scheduling Enhancement (VSE) requests
 permission to access the REQUEST SERVICES file 123.5 to obtain data from the 
 ASSOCIATED STOP CODE multiple field 688.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   The VistA Scheduling Enhancement (VSE) requests
 permission to access the REQUEST SERVICES file 123.5 to obtain data from the 
 ASSOCIATED STOP CODE multiple field 688.  

NUMBER: 6188                            IA #: 6188
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123
  DATE CREATED: MAR 30, 2015
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  NAME: Update/Add REQUEST PROCESSING ACTIVITY
  ID: GMR(123
GLOBAL REFERENCE: GMR(123,D0,40,D1,0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME OF ACTION ENTRY
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Add REQUEST PROCESSING ACTIVITY entry that includes the
 DATE/TIME OF ACTION ENTRY.  
FIELD NUMBER: 1                         FIELD NAME: ACTIVITY
  LOCATION: 0;2                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Add REQUEST PROCESSING ACTIVITY entry that includes the
 ACTIVITY.  
FIELD NUMBER: 2                         FIELD NAME: DATE/TIME OF ACTUAL ACTIVITY
  LOCATION: 0;3                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Add REQUEST PROCESSING ACTIVITY entry that includes the
 DATE/TIME OF ACTUAL ACTIVITY.  
FIELD NUMBER: 3
  FIELD NAME: WHO'S RESPONSIBLE FOR ACTIVITY
  LOCATION: 0;4                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Add REQUEST PROCESSING ACTIVITY entry that includes the
 WHO'S RESPONSIBLE FOR ACTIVITY.  
FIELD NUMBER: 4                         FIELD NAME: WHO ENTERED ACTIVITY
  LOCATION: 0;5                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Add REQUEST PROCESSING ACTIVITY entry that includes the
 WHO ENTERED ACTIVITY.  
 GLOBAL DESCRIPTION:   Add a REQUEST PROCESSING ACTIVITY entry.  
 GENERAL DESCRIPTION:   The VistA Scheduling Enhancement (VSE) requests
 permission to set (write implied here) data by adding an entry into the 
 REQUEST PROCESSING ACTIVITY multiple of the REQUEST/CONSULTATION file 123 
 using FileMan.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   The VistA Scheduling Enhancement (VSE) requests
 permission to set (write implied here) data by adding an entry into the 
 REQUEST PROCESSING ACTIVITY multiple of the REQUEST/CONSULTATION file 123 
 using FileMan.  

NUMBER: 6189                            IA #: 6189
  DATE CREATED: APR 02, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSHSH
  NAME: XUSHSH Hashing and Encryption APIs
  ID: XUSHSH
 GENERAL DESCRIPTION:   This DBIA describes supported references in the routine
 XUSHSH which provides Kernel APIs for hashing, encoding/decoding, or 
 encryption/decryption of input of various formats.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: KERNEL
KEYWORDS: ENCODE
KEYWORDS: DECODE
KEYWORDS: ENCRYPT
KEYWORDS: DECRYPT
KEYWORDS: SHA
COMPONENT/ENTRY POINT: SHAHASH
 COMPONENT DESCRIPTION:   This extrinsic function returns the SHA hash for a
 string entry. It uses an input variable to specify the length in bits of the
 desired hash.  
  
                Format:  $$SHAHASH^XUSHSH(N,X,FLAG) 
                                
 The value returned is the hashed value of X.  
VARIABLES: N                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Length in bits of the desired hash: 160
 (SHA-1), 224 (SHA-224), 256 (SHA-256), 384 (SHA-384), or 512 (SHA-512).  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) String to be hashed.  
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Flag to control format of hash: 
            "H" = Hexadecimal (default) 
            "B" = Base64 Encoded 
COMPONENT/ENTRY POINT: B64ENCD
 COMPONENT DESCRIPTION:   This extrinsic function returns the Base64 encoded
 value for a string entry. Base64 is a binary-to-text encoding scheme that
 represents binary data in an ASCII string format by translating it into a
 radix-64 representation. Base64 encoding is commonly used when there is a need
 to encode binary data that needs to be stored and transferred over media that 
 is designed to deal with textual data.  
                 
                Format:  $$B64ENCD^XUSHSH(X) 
                 
 The value returned is the encoded value of X. 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) String to be encoded.  
COMPONENT/ENTRY POINT: B64DECD
 COMPONENT DESCRIPTION:   This extrinsic function returns the decoded value for
 a Base64 string entry. Base64 is a binary-to-text encoding scheme that
 represents binary data in an ASCII string format by translating it into a
 radix-64 representation. Base64 encoding is commonly used when there is a need
 to encode binary data that needs to be stored and transferred over media that 
 is designed to deal with textual data.  
                 
                Format:  $$B64DECD^XUSHSH(X) 
                 
 The value returned is the encoded value of X.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) String to be decoded.  
COMPONENT/ENTRY POINT: RSAENCR
 COMPONENT DESCRIPTION:   This extrinsic function returns the RSA encrypted
 ciphertext for a string entry. RSA is a public-key encryption system that is
 widely used for secure data transmission. The encryption key is public and
 differs from the decryption key which is kept secret.  
                 
                Format:  $$RSAENCR^XUSHSH(TEXT,CERT,CAFILE,CRLFILE,ENC) 
                 
 The value returned is the RSA encrypted ciphertext value of TEXT.  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Plaintext string to be encrypted.  
VARIABLES: CERT                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) An X.509 certificate containing the RSA
 public key to be used for encryption, in PEM encoded or binary DER format.
 Note that the length of the plaintext can not be greater than the length of
 the modulus of the RSA public key contained in the certificate minus 42 bytes. 
 
VARIABLES: CAFILE                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The name of a file containing trusted
 Certificate Authority X.509 Certificates in PEM-encoded format, one of which
 was used to sign the Certificate.  
VARIABLES: CRLFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The name of a file containing X.509
 Certificate Revocation Lists in PEM-encoded format that should be checked to
 verify the status of the Certificate.  
VARIABLES: ENC                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Encoding - PKCS #1 v2.1 encoding method: 
            1 = OAEP (default) 
            2 = PKCS1-v1_5 
COMPONENT/ENTRY POINT: RSADECR
 COMPONENT DESCRIPTION:   This extrinsic function returns the plaintext string
 value for RSA encrypted ciphertext entry. RSA is a public-key encryption
 system that is widely used for secure data transmission. The encryption key is
 public and differs from the decryption key which is kept secret.  
  
                Format:  $$RSADECR^XUSHSH(TEXT,KEY,PWD,ENC) 
                 
 The value returned is the plaintext value of TEXT.  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Ciphertext string to be decrypted.  
VARIABLES: KEY                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) RSA private key corresponding to the RSA
 public key that was used for encryption, PEM encoded.  
VARIABLES: PWD                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Private key password.  
VARIABLES: ENC                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Encoding - PKCS #1 v2.1 encoding method: 
            1 = OAEP (default) 
            2 = PKCS1-v1_5 
COMPONENT/ENTRY POINT: AESENCR
 COMPONENT DESCRIPTION:   This extrinsic function returns the Advanced
 Encryption Standard (AES) encrypted ciphertext for a string entry. AES is a
 specification for the encryption of electronic data established by the U.S.
 National Institute of Standards and Technology (NIST) in 2001.  
                 
                Format:  $$AESENCR^XUSHSH(TEXT,KEY,IV) 
                 
 The value returned is the AES encrypted ciphertext value of TEXT.  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Plaintext string to be encrypted.  
VARIABLES: KEY                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Input key material 16, 24, or 32
 characters long.  
VARIABLES: IV                           TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Initialization vector. If this argument is
 present it must be 16 characters long.  
COMPONENT/ENTRY POINT: AESDECR
 COMPONENT DESCRIPTION:   This extrinsic function returns the string value of
 an Advanced Encryption Standard (AES) encrypted ciphertext entry. AES is a
 specification for the encryption of electronic data established by the U.S.
 National Institute of Standards and Technology (NIST) in 2001.  
                 
                Format:  $$AESDECR^XUSHSH(TEXT,KEY,IV) 
                 
 The value returned is the plaintext value of TEXT.  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Ciphertext string to be decrypted.  
VARIABLES: KEY                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Input key material 16, 24, or 32
 characters long.  
VARIABLES: IV                           TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Initialization vector. If this argument is
 present it must be 16 characters long.  
  DATE ACTIVATED: AUG 18, 2015

NUMBER: 6190                            IA #: 6190
  FILE NUMBER: 101.41                   GLOBAL ROOT: OR(101.41
  DATE CREATED: APR 05, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: File
  NAME: ORDER DIALOG 101.41             ID: OR(101.41
GLOBAL REFERENCE: ORD(101.41,D0,9)
FIELD NUMBER: 19                        FIELD NAME: ADDITIONAL TEXT
  LOCATION: 9;E1                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA provides for the read with Fileman of field 19,
 ADDITIONAL TEXT, in the ORDER DIALOG file # 101.41.  
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (Kiosks) had a need to read field
 19, ADDITIONAL TEXT, from the ORDER DIALOG file #101.41.  

NUMBER: 6191                            IA #: 6191
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100
  DATE CREATED: APR 05, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: File
  NAME: READ OR 100 FIELDS              ID: OR(100
GLOBAL REFERENCE: OR(100,D0)
FIELD NUMBER: .02                       FIELD NAME: OBJECT OF ORDER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DIALOG
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: PACKAGE
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 15                        FIELD NAME: EVENT
  LOCATION: 0;17                        ACCESS: Read w/Fileman
FIELD NUMBER: 21                        FIELD NAME: START DATE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 22                        FIELD NAME: STOP DATE
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: TO 
  LOCATION: 0;11                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: OR(100,D0,3)
FIELD NUMBER: 5                         FIELD NAME: STATUS
  LOCATION: 3,3                         ACCESS: Read w/Fileman
FIELD NUMBER: 8.1                       FIELD NAME: TYPE
  LOCATION: 3,11                        ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: REPLACED ORDER
  LOCATION: 3;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 30                        FIELD NAME: CURRENT ACTION
  LOCATION: 3;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: FLAGGED
  LOCATION: 3;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: OR(100,D0,6)
FIELD NUMBER: 64                        FIELD NAME: DC REASON
  LOCATION: 6;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 65                        FIELD NAME: DC REASON TEXT
  LOCATION: 6;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: OR(100,D0,8,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME ORDERED
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ACTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PROVIDER
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: SIGNATURE STATUS
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: SIGNED BY
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: VERIFYING NURSE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: VERIFYING CLERK
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: TEXT REFERENCE
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 15                        FIELD NAME: RELEASE STATUS
  LOCATION: 0;15                        ACCESS: Read w/Fileman
FIELD NUMBER: 18                        FIELD NAME: CHART VIEWED BY
  LOCATION: 0;18                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: OR(100,D0,8,D1,2
FIELD NUMBER: 21                        FIELD NAME: DC/HOLD UNTIL
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 24                        FIELD NAME: DRUG SCHEDULE
  LOCATION: 2;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 25                        FIELD NAME: DIGITAL SIGNATURE REQUIRED
  LOCATION: 2;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: OR(100,D0,8,D1,.1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: ORDER TEXT
  LOCATION: .1;0                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: OR(100,D0,8,D1,.2,D2,0)
FIELD NUMBER: .01                       FIELD NAME: EXTERNAL TEXT
  LOCATION: .2;0                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: OR(100,D0,4.5,D1,1)
FIELD NUMBER: 1                         FIELD NAME: VALUE
  LOCATION: 1;E1                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: ORD(100.7,'C',DUZ)
GLOBAL REFERENCE: ORE(100.2,'A0',ORDER,0)
GLOBAL REFERENCE: ORD(100.03,D0,0)
 GENERAL DESCRIPTION:   This IA provides for the FileMan Read of ORDER FILE
 #100 fields.  
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service Kiosks has a need to read a
 patient's order details from ORDER FILE 100.  

NUMBER: 6192                            IA #: 6192
  FILE NUMBER: 2005                     GLOBAL ROOT: MAG(2005
  DATE CREATED: APR 17, 2015            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MAG 2005 READ
  ID: MAG(2005
GLOBAL REFERENCE: MAG(2005,D0,0)
FIELD NUMBER: 5                         FIELD NAME: PATIENT
  LOCATION: 0;7                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: MAG(2005,'ATRKID'
 GENERAL DESCRIPTION:   This ICR provides for the FileMan read of the
 ^MAG(2005, "ATRKID" index in the IMAGE FILE (#2005) and the PATIENT field #5
 in the IMAGE FILE (#2005).  
  
 These fields provide the ability to associate an image to a patient when a
 callback is execued by the Imaging Background Processor which passes only the
 Tracking ID and Queue ID to the callback routine.  Once the IEN of the image
 entry in found using "ATRKID", the patient can be identified by reading fieled
 # in ^MAG(2005,D0,0).  
  STATUS: Active
KEYWORDS: VPS
KEYWORDS: IMAGING
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   vA Point of Service Kiosk has a need to use
 ^MAG(2005,"ATRKID" index in the IMAGE FILE #2005 in order to import a
 patient's after visit summary PDF image. When the Image Background Processor
 executes a callback in response to an image import request, VPS needs to reade
 the "ATRKID" index to obtain the IEN of the image in File #2005.  Using the
 IEN, VPS and reads the Patient DFN from  ^MAG(2005,D0,0).  
  DATE ACTIVATED: APR 21, 2015

NUMBER: 6193                            IA #: 6193
  FILE NUMBER: 60                       GLOBAL ROOT: LAB(60,D0,0)
  DATE CREATED: APR 17, 2015            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: File
  NAME: LAB FILE 60 B X-REF             ID: LAB(60,D0,0)
GLOBAL REFERENCE: LAB(60,'B'
 GENERAL DESCRIPTION:   This ICR provides for the use of the "B"
 cross-reference in LAB FILE (#60) to obtain the Lab information based on a Lab
 Test Name.  
  STATUS: Withdrawn
KEYWORDS: VPS
KEYWORDS: LAB 60 B CROSS REFERENCE
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (Kiosks) needs to use ^LAB(60,"B"
 to obtain a patient's Lab Test information for a specific Lab Test Name.  

NUMBER: 6194                            IA #: 6194
  DATE CREATED: MAY 07, 2015            CUSTODIAL PACKAGE: PROBLEM LIST
  USAGE: Private                        TYPE: Routine
  ROUTINE: TIUWRIIS                     NAME: GMPLUTL2
  ID: TIUWRIIS
 GENERAL DESCRIPTION:   During SQA of patch TIU*1.0*286 it was discovered that
 routine TIUWRIIS contains a call to LIST^GMPLUTL2.  There is no intergration
 agreement for its use in TIU.  This has existed in past patches and this
 integration agreement request is an attempt to complete missing ICR
 documentation 
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PROB
VARIABLES: ROOT                         TYPE: Output
VARIABLES: dfn                          TYPE: Input
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES

NUMBER: 6195                            IA #: 6195
  FILE NUMBER: 60                       GLOBAL ROOT: LAB
  DATE CREATED: MAY 07, 2015            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: 60                              ID: LAB
 GENERAL DESCRIPTION:   During SQA for patch TIU*1.0*286 it was found that TIU
 routine TIUWRIIS reads ^LAB(60 and no integration agreement exist.  This read
 has existed in past patches and this is an attempt to complete the missing ICR
 documentation.  
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES

NUMBER: 6196                            IA #: 6196
  FILE NUMBER: 1.1                      GLOBAL ROOT: DIA
  DATE CREATED: MAY 19, 2015            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DIA
  ID: DIA
GLOBAL REFERENCE: DIA(727.809
 GLOBAL DESCRIPTION:   Holds the audit log for the UNIT DOSE LOCAL EXTRACT
 file.  
GLOBAL REFERENCE: DIA(727.81
 GLOBAL DESCRIPTION:   Holds the audit log for the PRESCRIPTION EXTRACT file.  
GLOBAL REFERENCE: DIA(727.819
 GLOBAL DESCRIPTION:   Holds the audit log for the IV DETAIL EXTRACT file.  
 GENERAL DESCRIPTION:   DSS request a one-time agreement allowing a direct
 global kill of the AUDIT file (#1.1) for 3 ECX related files in the
 post-install routine in patch ECX*3.0*154. Details of this request are below.  
  
 The DSS extract software (ECX) audits certain fields in the PRESCRIPTION 
 EXTRACT file (#727.81), the UNIT DOSE LOCAL EXTRACT file (#727.809) and the IV
 DETAIL EXTRACT file (#727.819) when they are edited using the Pharmacy Volume
 Edit [ECX PHA VOL EDIT] option.  
  
 The auditing of the specified fields was to be turned on and off using this
 option.  However, a bug in the software caused the auditing to never be turned
 off so when the monthly extract files were built, an audit log entry was
 created for every entry in the extract file.  
  
 In order to make this option, and its associated information useful, DSS is
 requesting permission to delete the entire audit log for files 727.81, 
 727.809, and 727.819.  This would be done by killing the entire audit log for
 each file via a direct global kill of ^DIA(File #).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AUDIT
KEYWORDS: DSS
KEYWORDS: EXTRACT
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  DATE ACTIVATED: JUN 11, 2015

NUMBER: 6197                            IA #: 6197
  FILE NUMBER: 71                       GLOBAL ROOT: RAMIS(71,
  DATE CREATED: MAY 22, 2015            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: WVRPCPT1
  NAME: MOST RECENT PREGNANT STATE      ID: WVRPCPT1
GLOBAL REFERENCE: RAMIS(71,D0,'CM',0)
FIELD NUMBER: 125                       FIELD NAME: CONTRAST MEDIA
  LOCATION: 0;0                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: RAMIS(71,D0,'CM',D1,0)
FIELD NUMBER: .01                       FIELD NAME: CONTRAST MEDIA
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This integration agreement allows the subscribing
 package to retrieve a detailed display of a patient's most recent instance of
 a pregnant state.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PREGNANCY STATUS
COMPONENT/ENTRY POINT: $$GETMRPST(DFN)
 COMPONENT DESCRIPTION:   This line tag returns a detailed display of the
 patient's most recent instance of a pregnant state in a format suitable for
 display to an end user.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient's internal entry number (IEN) in the WV
 PATIENT file (#790).  
VARIABLES: $$GETMRPST                   TYPE: Output
 VARIABLES DESCRIPTION:   The node address where the output is stored preceded
 by the characters 
 "~@".
VARIABLES: TMP GLOBAL                   TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP("WVPTO",$J,LINE,0)=TEXT 
   LINE: line number of text; starts at one 
         and increments by one 
   TEXT: a line of text to display to the user 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Text Integration Utilities will display the text within
 an object.  
  DATE ACTIVATED: NOV 17, 2017

NUMBER: 6198                            IA #: 6198
  DATE CREATED: MAY 26, 2015            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Private                        TYPE: Routine
  ROUTINE: WVRPCPT1                     NAME: STATUS REVIEW NOTIFICATION TEXT
  ID: WVRPCPT1
 GENERAL DESCRIPTION:   This integration agreement allows the subscribing
 package to retrieve the event that generated a status review notification in a
 user friendly format. This text is displayed when the user processes the
 notification within the Computerized Patient Record System (CPRS) GUI.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PREGNANCY STATUS
KEYWORDS: LACTATION STATUS
COMPONENT/ENTRY POINT: $$GETSRND(DFN,TYPE)
 COMPONENT DESCRIPTION:   This line tag returns the event that generated a
 status review notification in a format suitable for display to an end user.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient's internal entry number (IEN) in the WV
 PATIENT file (#790).  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   The value of the STATUS TYPE field (#3) in the WV
 PREGNANCY/LACTATION STATUS CONFLICT EVENTS file (#790.9), in internal format.  
VARIABLES: $$GETSRND                    TYPE: Output
 VARIABLES DESCRIPTION:   The node address where the output is stored preceded
 by the characters 
 "~@".
VARIABLES: TMP GLOBAL                   TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP("WVPTO",$J,LINE,0)=TEXT 
   LINE: line number of text; starts at one 
         and increments by one 
   TEXT: a line of text to display to the user 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Text Integration Utilities will display the text within
 an object.  

NUMBER: 6199                            IA #: 6199
  DATE CREATED: MAY 26, 2015            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  ROUTINE: PXRMCWH1
  NAME: HIGH RISK MEDICATIONS FOR FEMALE PATIENTS
  ID: PXRMCWH1
 GENERAL DESCRIPTION:   This integration agreement will allow the subscriber to
 determine which pharmacy orders are considered teratogenic or unsafe for a
 specific female patient.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 22, 2017
KEYWORDS: TERATOGENIC DRUGS
KEYWORDS: UNSAFE DRUGS
COMPONENT/ENTRY POINT: HIRMEDS(DFN,NGET,BDT,EDT,NFOUND,TEST,DATE,DATA,TEXT)
 COMPONENT DESCRIPTION:   Returns the teratogenic and unsafe drugs ordered for
 a patient that were active or pending during a time period.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number (IEN) of the patient's
 entry in the PATIENT file (#2).  
VARIABLES: NGET                         TYPE: Input
 VARIABLES DESCRIPTION:   The maximum number of orders to return. If this
 variable is positive, the returned orders are sorted in reverse chronological
 order (most recent order is returned first). If this variable is negative, the
 returned orders are sorted in chronological order (oldest order is returned
 first).  
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The beginning date/time in internal FileMan format of
 the time range in which to search for orders.  
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The ending date/time in internal FileMan format of
 the time range in which to search for orders.  
VARIABLES: NFOUND                       TYPE: Output
 VARIABLES DESCRIPTION:   The number of orders found.  
VARIABLES: TEST                         TYPE: Both
 VARIABLES DESCRIPTION:   INPUT: The caller must specify the REMINDER ORDER
 CHECK ITEMS GROUP file entries, the pregnancy status associated with each
 entry, and the order's status the API should check for when determining
 whether to return an order. This parameter is formatted as: 
  
   TEST="PSTATUS_1:ROCG_LIST_1~PSTATUS_N:ROCG_LIST_N^ 
       OSTATUS" 
  
     PSTATUS: the patient's status, in the format 
              XN 
             X: either P for pregnancy or L for 
                lactation 
             N: either 0 for false or 1 for true 
                and is optional when X is L but 
                required when X is P 
             Examples: P1 => patient is pregnant 
                       P0 => patient is not 
                             pregnant 
                       L  => patient is or is not 
                             lactating 
     ROCG_LIST: comma-delimited list of REMINDER 
                ORDER CHECK ITEMS GROUP entry 
                internal entry numbers (IENs) 
     *Note: Multiple STATUS:ROCG_LIST pairings are 
            allowed and are delimited by the tilde 
            character ("~").  
     OSTATUS: the order's status on the evaluation 
              date 
             Valid Values: ACTIVE/CURRENT 
                           ALL 
                           RECENT ACTIVITY 
  
 OUTPUT: An array of truth values where 1 is true and 0 is false. The array has
 one subscript that starts at one and increments by one. Each subscript
 correlates to the order returned in the same numbered first level subscript in
 the DATA array.  
VARIABLES: DATE                         TYPE: Output
 VARIABLES DESCRIPTION:   An array of dates in internal FileMan date format.
 The array has one subscript that starts at one and increments by one. Each
 subscript correlates to the order returned in the same numbered first level 
 subscript in the DATA array and contains the date/time the order was entered.  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   An array of orders that are considered teratogenic or
 unsafe. The array has the following format: 
  
    DATA(X,"DRUG NAME")="drug name" 
                        GENERIC NAME field (#.01) 
                        in the DRUG file (#50) 
    DATA(X,"ORDER NUMBER")=order number 
                           Internal Entry Number 
                           (IEN) in the ORDER file 
                           (#100) 
    DATA(X,"ROC ITEM GROUP",Y)="reminder order 
                                check items group 
                                name" 
                               GROUP NAME field 
                               (#.01) in the 
                               REMINDER ORDER CHECK 
                               ITEMS GROUP file 
                               (#801) 
  
 X is a number that starts at one and increments by one. There is only one 
 number per order.  Y is a number that starts at one and increments by one.
 There is only one number per reminder order check items group name.  
VARIABLES: TEXT                         TYPE: Output
 VARIABLES DESCRIPTION:   An array of text in a human-friendly format
 describing the orders that are returned. The array has one subscript that
 starts at one and increments by one. Each subscript correlates to the order
 returned in the same numbered first level subscript in the DATA array.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 6200                            IA #: 6200
  DATE CREATED: MAY 27, 2015            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: WVRPCPT1
  NAME: PATIENT'S HEALTHCARE MANAGERS   ID: WVRPCPT1
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to determine the healthcare managers for a patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CASE MANAGER
KEYWORDS: MATERNITY CARE COORDINATOR
COMPONENT/ENTRY POINT: PATMGR(RESULTS,PAT,WHO,IDEN)
 COMPONENT DESCRIPTION:   Returns the healthcare managers responsible for the
 patient.  
VARIABLES: RESULTS                      TYPE: Both
 VARIABLES DESCRIPTION:   Reference to array in which to return the patient's
 healthcare managers. The array is formatted as follows: 
  
   RESULTS(X)=ROLE 
  
 where X is the internal entry number (IEN) of the provider's entry in the NEW
 PERSON FILE (#200) and ROLE is the provider's role in the patient's 
 healthcare. ROLE is either "ASSIGNED CASE MANAGER", "DEFAULT CASE MANAGER", or
 "MATERNITY CARE COORDINATOR". For the "DEFAULT CASE MANAGER" role, the site's
 name is prepended to the role. For example, "SAMPLE VAMC DEFAULT CASE
 MANAGER".  
  
 If an error is encountered, RESULTS(0) is defined. The first caret piece is -1
 and the second caret piece is the error message. This reference is required.  
VARIABLES: PAT                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient's entry in
 the WV PATIENT file (#790). This is a required value.  
VARIABLES: WHO                          TYPE: Input
 VARIABLES DESCRIPTION:   The healthcare manager(s) the API should return. The
 following values are accepted: 
  
  VALUE   Returned Field* 
 ===========================
    C     CASE MANAGER (#.1) 
    M     MATERNITY CARE COORDINATOR (#.29) 
    CM    CASE MANAGER (#.1) and 
          MATERNITY CARE COORDINATOR (#.29) 
  
 *Note: All fields are in the WV PATIENT file (#790).  This is a required
 value.  
VARIABLES: IDEN                         TYPE: Input
 VARIABLES DESCRIPTION:   Whether to identify the provider's role in the
 patient's healthcare. A value of 1 will return the role, a value of 0 or
 undefined will not return the role. This is an optional value and the default
 value is 1.  
COMPONENT/ENTRY POINT: GETRECIPS(RESULTS,PAT,SOURCE,TYPE,IDEN,DIV)
 COMPONENT DESCRIPTION:   Returns the recipients for the PREGNANCY STATUS
 REVIEW and LACTATION STATUS REVIEW Computerized Patient Record System (CPRS)
 notifications.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   Reference to array in which to return the patient's
 healthcare managers. The array is formatted as follows: 
  
   RESULTS(X)=ROLE 
  
 where X is the internal entry number (IEN) of the recipient's entry in the NEW
 PERSON FILE (#200) and ROLE is the recipient's role in the patient's
 healthcare. ROLE is either "ASSIGNED CASE MANAGER", "DEFAULT CASE MANAGER",
 "MATERNITY CARE COORDINATOR", or "PRIMARY CARE PROVIDER". For the "DEFAULT
 CASE MANAGER" role, the site's name is prepended to the role. For example,
 "SAMPLE VAMC DEFAULT CASE MANAGER".  
  
 If an error is encountered, RESULTS(0) is defined. The first caret piece is -1
 and the second caret piece is the error message. This reference is required.  
VARIABLES: PAT                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the patient's entry in the WV PATIENT file
 (#790). This is a required value.  
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   The type of the source of conflict. Possible values
 are "CODE" for International Classification of Diseases (ICD) or SNOMED CT
 codes and "LAB" for laboratory tests. This is a required value.  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   The type of status conflict. Possible values are "P"
 for pregnancy status and "L" for lactation status. This is a required value.  
VARIABLES: IDEN                         TYPE: Input
 VARIABLES DESCRIPTION:   Whether to identify the provider's role in the
 patient's healthcare. A value of 1 will return the role, a value of 0 or
 undefined will not return the role. This is an optional value and the default
 value is 0.  
VARIABLES: DIV                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the entry in the INSITITUTION file (#4) where
 the conflict occurred.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 17, 2017

NUMBER: 6201                            IA #: 6201
  FILE NUMBER: 9999999.14               GLOBAL ROOT: AUTTIMM(
  DATE CREATED: MAY 29, 2015
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA 6201
  ID: AUTTIMM(
 GENERAL DESCRIPTION:   The Health Summary Package desires to set up an
 integration agreement with the PCE Package to point to the Immunizations
 (#9999999.14) file. The Selection Item (.01) field in the Structure Multiple
 (field 1) of the Health Summary Type (#142) file points to the Immunizations
 file. The Selection File (.01) field in the Selection File multiple (field 7)
 of the Health Summary Component (#142.1) file points to the Immunizations
 file.  Health Summary also requires the ability to add the application group 
 "GMTS" ^DIC(9999999.14) when the Health Factors files exists. This is done 
 with a Fileman Call.  
  STATUS: Active
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: SEP 08, 2015

NUMBER: 6202                            IA #: 6202
  FILE NUMBER: 3.8                      GLOBAL ROOT: XMB(3.81)
  DATE CREATED: JUN 04, 2015            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MAIL GROUP MEMBER
  ID: XMB(3.81)
GLOBAL REFERENCE: XMB(3.81,.01)
FIELD NUMBER: .01                       FIELD NAME: MEMBER
  LOCATION: XMB(3.81,D0,0)              ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TYPE
  LOCATION: XMB(3.81,D0,0)              ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The PTF module of the REGISTRATION package requests
 permission to read the MEMBER multiple (#2) of the MAIL GROUP (#3.8) file for
 patch DG*5.3*884. This is a one-time use to populate the new PTI mail group 
 with the same MEMBERS as the existing PTT mail group. This will save the IRMS
 staff from having to manually enter the information and save possible data
 entry errors. 
  
 Also, we request permission to read the B cross-reference this one time in
 order to find the existing PTT mail group.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MEMBER
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   This is a one time usage for DG*5.3*884.  
  DATE ACTIVATED: JUN 22, 2015

NUMBER: 6203                            IA #: 6203
  DATE CREATED: JUN 15, 2015            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED
  NAME: Delete the 'RDE' cross reference and the data (70.03 ; 1.1)
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RADIATION ABSORBED DOSE
KEYWORDS: 'RDE' CROSS-REFERENCE
KEYWORDS: RAD/NUC MED PATIENT file
KEYWORDS: RA*5.0*119
KEYWORDS: ONE-TIME
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   All the events that occur as a result of this
 post-init begin at the EN entry point.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   VistA Radiology/Nuclear Medicine (VistA RIS) asks
 permission to execute a KILL command to delete the file wide ^RADPT("RDE"
 cross reference.  
  
 A VistA RIS post-init RAIPS119 will use a VA FileMan utility to delete the
 "RDE" from the data dictionary of the RADIATION ABSORBED DOSE field: 
  
 * D DELIXN^DDMOD(70,"RDE") 
  
 Immediately after the call to that utility, the VistA RIS post-init RAIPS119
 will follow with this command: 
  
 * K ^RADPT("RDE") 
  
 These two actions will remove the "RDE" cross reference definition and data
 from the RAD/NUC MED PATIENT file.  
  
  
 This software will be included in a RA*5.0*119 post-init. This post-init will
 be run only when versions of RA*5.0*119 are installed. Because of this special
 issue a one-time request for permission to proceed is required.  
  DATE ACTIVATED: JUN 22, 2015

NUMBER: 6204                            IA #: 6204
  DATE CREATED: JUN 17, 2015            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DRG FILE ENTRY COUNTS
 GENERAL DESCRIPTION:   The Registration package requests permission to loop
 through and count the number of entries in the following DRG files: 
  
  File   Name                             Global 
  ----   ----                             ------
  80.5   DRG SURGICAL HIERARCHY           ^ICDRS 
  80.6   DRG HAC                          ^ICDHAC 
  82     DRG DIAGNOSIS INDENTIFIER CODES  ^ICDID 
  82.1   DRG PROCEDURE IDENTIFIER CODES   ^ICDIP 
  82.11  DRG PROCEDURE CODE COMBINATIONS  ^ICDIDP 
  82.12  DRG DIAGNOSIS CODE COMBINATIONS  ^ICDIDD 
  82.13  DRG CC EXCLUSIONS                ^ICDCCEX 
  
 This is a one-time request for Registration patch DG*5.3*884. It is important
 that these DRG files are correctly populated so the new functionality
 introduced in DG*5.3*884 will work properly. The environment check routine
 will check these file counts and display a message to the patch installer if
 there is any discrepancy. The installer will be instructed to log a Remedy
 ticket. Also, a MailMan message will be sent to a customer support group as an
 added precaution. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DG*5.3*884
SUBSCRIBING PACKAGE: REGISTRATION
  DATE ACTIVATED: JUL 30, 2015

NUMBER: 6205                            IA #: 6205
  DATE CREATED: JUN 19, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWTPP DELLIST                  REMOTE PROCEDURE: ORWTPP DELLIST
 GENERAL DESCRIPTION:   This RPC deletes an entry in the OE/RR LIST file
 (#100.21). Its only parameter is the Internal Entry Number (IEN) of the list,
 and it returns a Boolean result (1=Yes if successful, or 0=No otherwise).  
   
 NOTE: Authorization is enforced. A user may only delete lists which they own
 (i.e., they must be identified as a USER of the list, AND the list must be of
 type PERSONAL). Users are identified by the individual DUZ.  Application
 Proxies are forbidden.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PERSONAL LIST
SUBSCRIBING PACKAGE: MOBILE CARDIAC REHAB PROVIDER-FACING

NUMBER: 6206                            IA #: 6206
  DATE CREATED: JUN 19, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWTPP SAVELIST                 REMOTE PROCEDURE: ORWTPP SAVELIST
 GENERAL DESCRIPTION:   This RPC updates an entry in the OE/RR LIST file
 (#100.21). Parameters include the patients to be included in the list (passed
 as an ARRAY of DFNs), the Internal Entry Number (IEN) of the list, and the
 Visibility of the list (i.e., 0=OWNER ONLY (private) or 1=ALL CPRS USERS
 (public)). It returns a Boolean result (1=Yes if successful, or 0=No
 otherwise).  
  
 NOTE: Authorization is enforced. A user may only delete lists which they own
 (i.e., they must be identified as a USER of the list, AND the list must be of
 type PERSONAL). Users are identified by the individual DUZ.  Application
 Proxies are forbidden.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: OE/RR PERSONAL PATIENT LIST
SUBSCRIBING PACKAGE: MOBILE CARDIAC REHAB PROVIDER-FACING

NUMBER: 6207                            IA #: 6207
  DATE CREATED: JUL 13, 2015
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMVUTL7
  NAME: ABBVAL GMVUTL                   ID: GMVUTL7
 GENERAL DESCRIPTION:   This ICR authorizes access to the ABBVAL function in
 GMVUTL7 to retrieve the high and low measurements of a vital type.  
  STATUS: Active
KEYWORDS: VITALS
KEYWORDS: VPS
KEYWORDS: GMVUTL7
COMPONENT/ENTRY POINT: ABBVAL
VARIABLES: VITALTYPE                    TYPE: Input
 VARIABLES DESCRIPTION:   This variable is the IEN of a vital type in the GMRV
 VITALS PARAMETERS file #120.57.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   This variable contains a delimited string with the
 high and low measurement values for a vital type.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point Service (VPS) Kiosks collects vital
 measurement information through its staff-facing and patient-facing
 application.  VPS needs to provide an alert when a vital measurement is
 outside the range of normal measurement values for a vital type.       
  
 VPS will call ABBVAL with a vital type IEN in GMRV VITALS PARAMETERS file
 #120.57 to obtain the high and low measurement values of a vital type.  
  DATE ACTIVATED: JUL 27, 2015

NUMBER: 6208                            IA #: 6208
  FILE NUMBER: 364                      GLOBAL ROOT: IBA(364,
  DATE CREATED: JUL 14, 2015            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DB6208
  ID: IBA(364,
GLOBAL REFERENCE: IBA(364,D0
FIELD NUMBER: .01                       FIELD NAME: BILL NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the bill number that was EDI transmitted.  
FIELD NUMBER: .02                       FIELD NAME: BATCH NUMBER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The EDI transmission batch that includes this bill entry. 
 
 GENERAL DESCRIPTION:   The Accounts Receivable (AR) application needs to
 extract EDI transmission data from the EDI TRANSMIT BILL file (#364). This is
 a read-only action and does not modify any fields in the file.  
  STATUS: Active
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: AUG 06, 2015

NUMBER: 6209                            IA #: 6209
  FILE NUMBER: 364.1                    GLOBAL ROOT: IBA(364.1,
  DATE CREATED: JUL 14, 2015            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DB6209
  ID: IBA(364.1,
GLOBAL REFERENCE: IBA(364.1,D0
FIELD NUMBER: .01                       FIELD NAME: BATCH NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The number of the batch for EDI transmissions 
FIELD NUMBER: .12                       FIELD NAME: INSURANCE COMPANY
  LOCATION: 0;12                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the insurance company associated with the EDI
 Batch 
FIELD NUMBER: 1.01                      FIELD NAME: DATE FIRST SENT
  LOCATION: 1;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the date/time this batch was first transmitted.  
 GENERAL DESCRIPTION:   The Accounts Receivable (AR) application needs to
 extract the EDI transmission batch data from the EDI TRANSMISSION BATCH file
 (#364.1).  This is a read-only action and does not modify any fields in the
 file.  
  STATUS: Active
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: AUG 06, 2015

NUMBER: 6210                            IA #: 6210
  DATE CREATED: JUL 14, 2015            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMSXRM
  NAME: CLINICAL REMINDERS INDEX REBUILD
  ID: PXRMSXRM
 GENERAL DESCRIPTION:   BLDINDEX^PXRMSXRM provides an API that subscribing
 packages can use to rebuild their portion of the Clinical Reminders Index.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM INDEX
KEYWORDS: PXRM INDEX REBUILD
KEYWORDS: CLINICAL REMINDERS
COMPONENT/ENTRY POINT: $$BLDINDEX(.FNUMLIST,START,SEQP)
 COMPONENT DESCRIPTION:   This API will task a job to rebuild the Clinical
 Reminders Index for one or more files. 
  
 During the rebuild, all evaluation, dialogs, reminder order checks, and 
 anything using reminder evaluation will be suspended.  
  
 See the Clinical Reminders Index Technical Guide's PXRM INDEX BUILD Option 
 documentation for a more detailed description on how the index build utility
 works.  
  
VARIABLES: FNUMLIST                     TYPE: Input
 VARIABLES DESCRIPTION:   (Passed By Reference) A list of file numbers whose
 index is to be rebuilt.  It is passed in as an array, where the subscripts are
 the file numbers.  
  
 The following files can be selected: 
    - 45 
    - 52 
    - 55   
    - 63   
    - 70     
    - 100  
    - 120.5 
    - 601.2 
    - 601.84 
    - 9000011 
    - 9000010.07 
    - 9000010.11 
    - 9000010.12  
    - 9000010.13 
    - 9000010.16 
    - 9000010.18 
    - 9000010.23  
  
VARIABLES: START                        TYPE: Input
 VARIABLES DESCRIPTION:   The date/time to start the tasked job.  
VARIABLES: SEQP                         TYPE: Input
 VARIABLES DESCRIPTION:   If more than one Index is to be rebuilt, this
 variable controls if the Indexes are built sequentially or concurrently. If
 SEQP is true then the Indexes will be built sequentially, if it is false they
 will be built concurrently. This variable is optional, and it defaults to
 true.  
  
VARIABLES: ZTSK                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the task number returned by ^%ZTLOAD.  
  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   PCE will use PXRM INDEX REBUILD to rebuild the Clinical
 Reminder Index for files within the PCE namespace (i.e., 9000010.xx).  
  DATE ACTIVATED: NOV 19, 2015

NUMBER: 6211                            IA #: 6211
  DATE CREATED: JUL 31, 2015
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: TIUCOP                       NAME: CALLS TO TIUCOP
  ID: TIUCOP
 GENERAL DESCRIPTION:   This DBIA documents calls to routine TIUCOP, which are
 used to implement Copy/Paste tracking functionality.  
  STATUS: Pending
COMPONENT/ENTRY POINT: $$PCT
 COMPONENT DESCRIPTION:   Returns the copy/paste verification percentage.  
  
 Output 
     - Percent pasted text matches copied text needed to be considered 
       as derived from the copied text (example ".5") 
                Or 
       Error condition "-1^Error Msg" 
VARIABLES: INST                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the institution ien (#4).  
COMPONENT/ENTRY POINT: $$EXC
 COMPONENT DESCRIPTION:   This returns whether a note is excluded from
 copy/paste tracking.  
  
 Output 
      - Boolean (1: Exclude, 0:Don't Exclude) 
                 Or 
        Error condition "-1^Error Msg" 
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the TIU note ien (#8925).  
COMPONENT/ENTRY POINT: $$WORDS
 COMPONENT DESCRIPTION:   This returns the number of words required to begin
 tracking copied text as part of the Copy/Paste Tracking functionality.  
VARIABLES: INST                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the logged in Institution (#4) of the user.  
COMPONENT/ENTRY POINT: GETCOPY
 COMPONENT DESCRIPTION:   This retrieves the copy buffer information.  
VARIABLES: INST                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the Institution (#4) of the logged in user.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the DUZ of the user.  
VARIABLES: ARY                          TYPE: Output
 VARIABLES DESCRIPTION:   This is the array which is returned with the copy
 buffer information.  
VARIABLES: STRT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an optional variable. This is the starting
 entry to find copy buffer data.  
VARIABLES:  
COMPONENT/ENTRY POINT: $$PUTCOPY
 COMPONENT DESCRIPTION:   Saves copy buffer information for copy/paste.  
VARIABLES: ARY                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the input array containing the Copied text
 information for storing.  
VARIABLES: ERR                          TYPE: Both
 VARIABLES DESCRIPTION:   This is the array name to receive error messages.  
VARIABLES: INST                         TYPE: Input
 VARIABLES DESCRIPTION:   Institution (#4) user is signed into.  
VARIABLES:  
COMPONENT/ENTRY POINT: CHKPASTE
 COMPONENT DESCRIPTION:   This checks if a note (#8925) has pasted text data
 stored.  
VARIABLES: INST                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the Institution (#4) of the logged in user.  
VARIABLES: DOC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the TIU note document ien (#8925) to search
 for pasted text.  
COMPONENT/ENTRY POINT: $$VIEW
 COMPONENT DESCRIPTION:   This component returns the copy/paste tracking
 viewing privileges of the specified user.  
VARIABLES: USER                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the DUZ of the user who's privileges to view
 copy/paste are being determined.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the TIU Note IEN (#8925) to have the user
 checked against.  This is optional and only needed if you are checking a
 specific users viewing rights for a specific Note as the Author or Cosigner of
 said note.  
VARIABLES: INST                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the Institution (#4) the user is logged into. 
 
COMPONENT/ENTRY POINT: GETPASTE
 COMPONENT DESCRIPTION:   This retrieves copy/paste tracked pasted text.  
VARIABLES: TIUIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the TIU Note IEN (#8925) in which the pasted
 text exists.  
VARIABLES: INST                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the Institution (#4) of the logged in user.  
VARIABLES: APP                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the application which is retrieving the
 pasted text.  
VARIABLES: ARY                          TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of the array to return pasted text.  
VARIABLES:  
COMPONENT/ENTRY POINT: $$PUTPASTE
 COMPONENT DESCRIPTION:   Saves pasted text for the Copy/Paste Tracking
 functionality.  
VARIABLES: INST                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the Institution (#4) of the logged in user.  
VARIABLES: ARY                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the array containing the pasted text
 information to be saved.  
VARIABLES: ERR                          TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of the error array to retrieve error
 information.  
VARIABLES: RSLT                         TYPE: Output
 VARIABLES DESCRIPTION:   This is an output array of the results of each save
 of the paste information which was sent in the ARY array.  
COMPONENT/ENTRY POINT: START
 COMPONENT DESCRIPTION:   Queues processes to build the copy/paste copy buffer
 for a specified user utilizing a GUI.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the user DUZ.  
VARIABLES: IP                           TYPE: Input
 VARIABLES DESCRIPTION:   This is the IP address of the connecting computer
 running the GUI.  
VARIABLES: HWND                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the Windows Handle passed in from the GUI.  
VARIABLES: DIV                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the division ien of the Institution (#4) file
 the user is logged in to.  
VARIABLES: VAL                          TYPE: Output
 VARIABLES DESCRIPTION:   The return provides the success of starting the
 background process.  
     1 = Success 
     0 = Failure 
COMPONENT/ENTRY POINT: POLL
 COMPONENT DESCRIPTION:   This polls the copy buffer retrieval background task
 for completion and returns data as it becomes available.  This entry should be
 called until the done indicator is received.  This call is to be used in
 conjunction with the START Component/Entry Point.  START compiles the data
 which is retrieved by the POLL.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the user DUZ.  
VARIABLES: IP                           TYPE: Input
 VARIABLES DESCRIPTION:   This is the IP address of the connecting computer
 running the GUI.  
VARIABLES: HWND                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the Windows Handle passed in from the GUI
 application.  
VARIABLES: LST                          TYPE: Output
 VARIABLES DESCRIPTION:   This RPC will return an array containing the results
 of the copy buffer background retrieval process.  If the process has not
 completed, it will return whatever entries have been completed.  When the
 process finally completes, the final return of data will contain a "~DONE=1"
 as the first array entry value, followed by any remaining entries.  Each
 return will only contain unique entries, so it will be additive.  
  
 Output Array: 
   ORY - Total number of unique entries^More Boolean (1=more data) 
   0RY(1..n,0) - 
      Piece 1: Date/Time of the copy 
      Piece 2: Date of the ^XTMP global creation 
      Piece 3: Package Prefix of application which captured the copy 
      Piece 4: Copy from location in 2 pieces (ien;package) 
      Piece 5: Number of lines of copied text 
   ORY(1..n,1..n) - Copied text 
  
   Or Error condition: 
      ORY - "-1^Error Msg" 
      ORY(-1)=Error Message 
COMPONENT/ENTRY POINT: STOP
 COMPONENT DESCRIPTION:   This entry point stops the copy buffer data retrieval
 process.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the user DUZ.  
VARIABLES: IP                           TYPE: Input
 VARIABLES DESCRIPTION:   This is the IP address of the connecting computer
 running the GUI.  
VARIABLES: HWND                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the Windows Handle passed in from the GUI
 application.  
VARIABLES: OK                           TYPE: Output
 VARIABLES DESCRIPTION:   Boolean result. 1=success 
COMPONENT/ENTRY POINT: $$CLEAN
 COMPONENT DESCRIPTION:   Starts the background job to clean-up expired
 copy/paste ^XTMP global entries. Returns the task number of the background
 job.  
VARIABLES: TASK                         TYPE: Both
 VARIABLES DESCRIPTION:   This is the name of the variable to retrieve the task
 number of the background process job started to clean up Copy/Paste Tracking
 ^XTMP entries which may have lived beyond their intended lifespan.  
COMPONENT/ENTRY POINT: EXCLST
 COMPONENT DESCRIPTION:   This returns a list of notes that are excluded from
 Copy/Paste Tracking functionality.  
VARIABLES: LST                          TYPE: Output
 VARIABLES DESCRIPTION:   This is the list array which contains the excluded
 notes from Copy/Paste Tracking. The array is returned in two pieces.  
  
 Output Array: 
    Piece 1: The ien of the TIU DOCUMENT DEFINITION (#8925.1) 
    Piece 2: The name (#.01) of the TIU DOCUMENT DEFINITION (#8925.1) 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 6212                            IA #: 6212
  DATE CREATED: AUG 12, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ZTMGRSET
  NAME: ZTMGRSET                        ID: ZTMGRSET
 GENERAL DESCRIPTION:   
  VA FileMan request use of MOVE^ZTMGRSET to rename the following routines: 
  DIDT renamed to %DT 
  DIDTC renamed to %DTC 
  DIRCR renamed to %RCR 
  
 This is needed during the install of any new version of VA FileMan. 
  It will be called in the post install routine.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ZTMGRSET
COMPONENT/ENTRY POINT: MOVE
 COMPONENT DESCRIPTION:   FileMan post install will define the variables: 
  SCR = screening logic that sets $T 
  ZTOS = ien of Mumps Operating System 
  %S = list of routines to rename 
  %D = list of the new named routines 
  B = 1 for a blank line between messages 
  
  and call MOVE^ZTMGRSET 
  
 MOVE^ZTMGRSET will call MES^XPDUTL to display install status information to
 the User and save the information in the KIDS Install file.  
  
VARIABLES: %S                           TYPE: Input
 VARIABLES DESCRIPTION:   List of routines to be rename, separated by '^' 
  
  
  
VARIABLES: %D                           TYPE: Input
 VARIABLES DESCRIPTION:   List of renamed routines separated by '^' 
  
  
VARIABLES: SCR                          TYPE: Input
 VARIABLES DESCRIPTION:   Screening logic for routines.  Must contain an If
 statement 
  
VARIABLES: ZTOS                         TYPE: Input
 VARIABLES DESCRIPTION:   Internal number of the Mumps Operating System 
  
VARIABLES: B                            TYPE: Input
 VARIABLES DESCRIPTION:   If equal to 1, then there will be a blank line
 between messages 
  
SUBSCRIBING PACKAGE: 1
 SUBSCRIBING DETAILS:   
  
  
  DATE ACTIVATED: SEP 24, 2015

NUMBER: 6213                            IA #: 6213
  DATE CREATED: AUG 17, 2015            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: VADPT30                      NAME: INPATIENT VADPT30
  ID: VADPT30
 GENERAL DESCRIPTION:   This ICR provides for the use of VADPT30 to read a
 patient's inpatient demographic variables.  The data returned by the routine 
 includes: ward, treating specialty, room/bed assignment, attending physician,
 diagnosis, IEN of the movement entry, and the patient's response to the
 facility directory question.  
  
 All input parameters are set into the input variables DFN, VAPRC, VAPRT, VATD,
 VAWD, VATS, VARM, VAPP, VAMV, VAFD prior to calling VAR^VADPT30.  No input
 parameters are passed to this routine.  
  STATUS: Withdrawn
KEYWORDS: INPATIENT
KEYWORDS: VPS
KEYWORDS: WARD
KEYWORDS: FACILITY DIR
COMPONENT/ENTRY POINT: VAPRC
 COMPONENT DESCRIPTION:   Empty, 0 or 1 (current inpatient)/ 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's IEN in PATIENT FILE #2 
VARIABLES: VAPRC                        TYPE: Input
 VARIABLES DESCRIPTION:   Empty 0 or 1 (current inpatient).  
VARIABLES: VAPRT                        TYPE: Input
 VARIABLES DESCRIPTION:   Empty, 0 or 1.  
VARIABLES: VATD                         TYPE: Input
 VARIABLES DESCRIPTION:   Inverse date 
VARIABLES: VAWD                         TYPE: Output
 VARIABLES DESCRIPTION:   Patient's assigned ward.  
VARIABLES: VATS                         TYPE: Output
 VARIABLES DESCRIPTION:   Patient's treating specialty.  
VARIABLES: VARM                         TYPE: Output
 VARIABLES DESCRIPTION:   Patient's room/bed assignment.  
VARIABLES: VAPP                         TYPE: Output
 VARIABLES DESCRIPTION:   Patient's attending physician.  
VARIABLES: VAMV                         TYPE: Output
 VARIABLES DESCRIPTION:   IEN of the admission movement record.  
VARIABLES: VAFD                         TYPE: Output
 VARIABLES DESCRIPTION:   Patient's response to the facility directory
 question.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service Kiosks requests the use of
 VAR^VADPT30 to read patient inpatient demographic data.  VPS needs the ward,
 room/bed and the patient's response to the facility directory questions.  

NUMBER: 6214                            IA #: 6214
  DATE CREATED: AUG 19, 2015            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: BPSSCRU3
  NAME: ECME COMMENTS                   ID: BPSSCRU3
 GENERAL DESCRIPTION:   This API retrieves comments from the BPS Transaction
 file in ECME and builds an array of comments for the subscribing packages.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: COM
VARIABLES: BPSRXI                       TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN 
VARIABLES: BPSRXR                       TYPE: Input
 VARIABLES DESCRIPTION:   Fill number.  If this parameter is blank, then fill
 number is assumed to be 0 (original fill).  
VARIABLES: BPSCOB                       TYPE: Input
 VARIABLES DESCRIPTION:   Coordination of Benefits value.  Optional parameter. 
 If not passed in, the default is 1 (Primary).  
VARIABLES: BPSARRAY                     TYPE: Output
 VARIABLES DESCRIPTION:   Return array of data in the format: 
  
 BPSARRAY(Transaction Date,Count Index) = 
  
             [1] Pharmacy Flag 
             [2] Comment 
             [3] User Entering comment 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: JAN 25, 2016

NUMBER: 6215                            IA #: 6215
  DATE CREATED: JUN 19, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWEBPS CLINPTS
 GENERAL DESCRIPTION:   This RPC returns a an ARRAY of patients with
 appointments scheduled for a given Clinic, identified by its internal entry
 number in the HOSPITAL LOCATION file (#44), within a specified date range. The
 0-node of the array includes the attributes of the clinic. Each subsequent
 node contains attributes of a patient, as specified below: 
   
   RESULT(0)="CLINIC IEN^CLINIC NAME^LIST TYPE^COUNT^VISIBILITY"  
   RESULT(1...n)="DFN^SSN^DOB^SEX^VET?^SC%^WARD^RMBD^NAME^AGE^ICN" 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MOBILE CARDIAC REHAB PROVIDER-FACING

NUMBER: 6216                            IA #: 6216
  DATE CREATED: AUG 21, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWEBPS GETCDRNG
 GENERAL DESCRIPTION:   This RPC returns the user's list of preferred date
 ranges for clinic appointment search, as well as their default date range.  
  
 The return array from this RPC will look like this: 
  
  RESULT(0)="T^T" 
  RESULT(1)="T;T^Today" 
  RESULT(2)="T+1;T+1^Tomorrow" 
  RESULT(3)="T-1;T-1^Yesterday" 
  RESULT(4)="T-7;T^Past Week" 
  RESULT(5)="T-31;T^Past Month" 
  RESULT(6)="S^Specify Date Range..." 
   
 Where the 0th element of the array is the user's default range, and the 
 subsequent elements are the remaining choices to be presented for list 
 retrieval.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MOBILE CARDIAC REHAB PROVIDER-FACING

NUMBER: 6217                            IA #: 6217
  DATE CREATED: AUG 21, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWEBPS GETLIST
 GENERAL DESCRIPTION:   This RPC returns a CPRS Patient List as an ARRAY,
 identified by its internal entry number in the OE/RR LIST file (#100.21), as
 described below. An optional second parameter allows the calling application
 to specify a start value for filtering the results in a manner compatible with
 CPRS (e.g., name (or partial name), SSN, Last Initial/Last 4, etc.).  
  
 The 0-node of the return array includes the attributes of the list. Each 
 subsequent node contains attributes of a patient, as specified below: 
    
   RESULT(0)="LIST IEN^LIST NAME^LIST TYPE^COUNT^VISIBILITY"  
   RESULT(1...n)="DFN^SSN^DOB^SEX^VET?^SC%^WARD^RMBD^NAME^AGE^ICN" 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MOBILE CARDIAC REHAB PROVIDER-FACING

NUMBER: 6218                            IA #: 6218
  DATE CREATED: AUG 21, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWEBPS MYLISTS
 GENERAL DESCRIPTION:   This RPC returns the user's default Patient List
 source, as well as the user's Personal Patient Lists.  
  
 The return array includes the user's default list (if specified) in the 
 zero-node, along with the user's Personal Lists. The following data elements
 are returned: 
   
 RESULT(0)=DFLT LIST IEN^DFLT LIST NAME^TYPE^COUNT^VISIBILITY"  
 RESULT(1..n)=IEN^NAME^TYPE^UPPER CASE^DEVICE^CREATOR^ SUBSCRIBE^CREATE D/T 
    
 Note: this comprises the list of OE/RR Lists that the user owns, and is 
 authorized to change or delete.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MOBILE CARDIAC REHAB PROVIDER-FACING

NUMBER: 6219                            IA #: 6219
  DATE CREATED: AUG 21, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWEBPS TEAMPERS
 GENERAL DESCRIPTION:   This RPC returns the list of all Team and Personal
 lists which are visible to the user in question.  
  
 An optional parameter allows the calling application to pass the user ID (DUZ)
 of the user in question. If no value is provided, the DUZ from the VistA
 session will be assumed.  
  
 The return array includes of all Team and Personal Lists which are visible to
 the user. The following data elements are returned: 
   
 RESULT(n)=IEN^NAME^TYPE^UPPER CASE^DEVICE^CREATOR^SUBSCRIBE^CREATION D/T 
   
 Note: this does NOT comprise the list of OE/RR Lists that the user may modify,
 but the lists that user may read.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MOBILE CARDIAC REHAB PROVIDER-FACING

NUMBER: 6220                            IA #: 6220
  DATE CREATED: AUG 21, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWEBPS WARDPTS
 GENERAL DESCRIPTION:   This RPC returns a an ARRAY of patients admitted a
 given Ward, identified by its internal entry number in the WARD LOCATION file
 (#42), within a specified date range. 
  
 The 0-node of the return array includes the attributes of the ward. Each 
 subsequent node contains attributes of a patient, as specified below: 
   
 RESULT(0)="WARD IEN^WARD NAME^LIST TYPE^COUNT^VISIBILITY" 
 RESULT(1...n)="DFN^SSN^DOB^SEX^VET?^SC%^WARD^RMBD^NAME^AGE^ICN" 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MOBILE CARDIAC REHAB PROVIDER-FACING

NUMBER: 6221                            IA #: 6221
  DATE CREATED: AUG 21, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWEBUSR USERINFO
 GENERAL DESCRIPTION:   This RPC wraps the call to ORWU USERINFO and returns
 the SITE NAME and INTEGRATION NAME for the VistA instance to which the user is
 connected, in addition to the attributes described for ORWU USERINFO.  
  
 The following '^'-delimited string is returned: 
   
 DUZ^NAME^USRCLS^CANSIGN^ISPROVIDER^ORDERROLE^NOORDER^DTIME^ 
 COUNTDOWN^ENABLEVERIFY^NOTIFYAPPS^MSGHANG^DOMAIN^SERVICE^ 
 AUTOSAVE^INITTAB^LASTTAB^WEBACCESS^ALLOWHOLD^ISRPL^RPLLIST^ 
 CORTABS^RPTTAB^STANUM^GECSTATUS^PRODACC^SITENAME^INTEGNM 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MOBILE CARDIAC REHAB PROVIDER-FACING

NUMBER: 6222                            IA #: 6222
  DATE CREATED: AUG 21, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWEBPS LISTALL
 GENERAL DESCRIPTION:   This RPC returns a list of Patients from the current
 VistA instance as an ARRAY, sorted alphabetically by name, as described below.
 An optional parameter allows the calling application to specify a start value
 for filtering the results in a manner compatible with CPRS (e.g., name (or 
 partial name), SSN, Last Initial/Last 4, etc.). Omitting this parameter will
 cause the fetch to begin with the first entry (alphabetically by name) in the
 PATIENT File (#2). A second optional parameter allows the calling application
 to specify the direction of the search from the start value (i.e., default or
 1 -> forward; -1 -> backward).  
  
 The 0-node of the return array includes the attributes of the list. Each 
 subsequent node contains attributes of a patient, as specified below: 
    
   RESULT(0)="-1^All Patients^All^COUNT^VISIBILITY"  
   RESULT(1...n)="DFN^SSN^DOB^SEX^VET?^SC%^WARD^RMBD^NAME^AGE^ICN" 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MOBILE CARDIAC REHAB PROVIDER-FACING

NUMBER: 6223                            IA #: 6223
  DATE CREATED: AUG 21, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWTPP NEWLIST                  REMOTE PROCEDURE: ORWTPP NEWLIST
 GENERAL DESCRIPTION:   This RPC creates a Personal List entry in the OE/RR
 LIST file (#100.21).  Parameters include the List Name, User ID (DUZ), and
 Visibility (1: All CPRS Users, 0: Self Only).  
  
 The return value is a string literal. 
  
 If the call fails, the result will be a two "^"-piece string, where the first
 piece is empty and the second piece is a brief explanation of the failure
 (e.g., "^invalid list name - duplicate of another name").  
  
 If the call succeeds, the result will have the format: 
  
 IEN_U_LISTNAME_"^^^^^^^"_VISIBILITY 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: MOBILE CARDIAC REHAB PROVIDER-FACING

NUMBER: 6224                            IA #: 6224
  FILE NUMBER: 757.5                    GLOBAL ROOT: LEX(757.5,
  DATE CREATED: AUG 26, 2015            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: UCUM CODES FILE
  ID: LEX(757.5,
GLOBAL REFERENCE: LEX(757.5,D0
 GLOBAL DESCRIPTION:   This ICR allows packages to point to entries in the UCUM
 CODES file, #757.5.  
  
  STATUS: Active
KEYWORDS: UCUM CODES
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/2/19, effective with CPRS v32 - OR*3.0*405.  
  DATE ACTIVATED: SEP 02, 2015

NUMBER: 6225                            IA #: 6225
  DATE CREATED: AUG 26, 2015            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEXMUCUM
  NAME: UCUM CODES APIs                 ID: LEXMUCUM
 GENERAL DESCRIPTION:   This ICR works in conjunction with ICR #6224 to allow
 packages to use UCUM Codes for storing measurements.  
  
  STATUS: Active
KEYWORDS: UCUM CODES APIs
COMPONENT/ENTRY POINT: UCUMCODES
 COMPONENT DESCRIPTION:   Given the internal entry number (IEN) of an entry
 from the UCUM CODES file, #757.5, this entry point returns the UCUM Code.
 Usage: 
  
 $$UCUMCODE^LEXMUCUM(IEN) 
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number of an entry from
 file #757.5.  
  
COMPONENT/ENTRY POINT: UCUMDATA
 COMPONENT DESCRIPTION:   Given an identifier, which can be the internal entry
 number (IEN), the Description, or the UCUM Code this API returns the
 associated data for the entry. Usage: 
  
  D UCUMDATA^LEXMUCUM(IDEN,.UCUMDATA) 
  
VARIABLES: IDEN                         TYPE: Input
 VARIABLES DESCRIPTION:   IDEN identifies the entry from the UCUM Codes file,
 #757.5, for which to return the associated data. IDEN can be an internal entry
 number, a Description, or a UCUM Code.  
  
VARIABLES: UCUMDATA                     TYPE: Output
 VARIABLES DESCRIPTION:   UCUMDATA is an array, passed by reference, that
 contains the data associated with the identified entry from the UCUM Codes
 file #757.5.  The elements of the array are: 
  
 UCUMDATA(IEN,"COMMENTS") - Comments, if there are any 
  
 UCUMDATA(IEN,"DESCRIPTION") - Description 
  
 UCUMDATA(IEN,"IEN") - The internal entry number 
  
 UCUMDATA(IEN,"ROW") - The row number, from the Table of Examples of UCUM codes 
 for  Electronic Messaging - Version 1.3, on which this entry is found. It can
 be used to identify the entry to the developers of this table.  
  
 UCUMDATA(IEN,"UCUM CODE") - The UCUM Code 
  
  
COMPONENT/ENTRY POINT: VERSION
 COMPONENT DESCRIPTION:   This API returns the version information for the UCUM
 CODES file, #757.5. Usage: 
  
   D VERSION^LEXMUCUM(.VERDATA) 
  
VARIABLES: VERDATA                      TYPE: Output
 VARIABLES DESCRIPTION:   This array, passed by reference, contains the version
 information.  
  
 VERDATA("DATE") - The release date of this version 
  
 VERDATA("NAME") - The name of this version 
  
 VERDATA("VERSION") - The version identification 
  
VARIABLES:  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   Effective with GMTS*2.7*122, to allow display of an
 enterprise standard units of measure for Education Topics, Exams, and Health
 Factors.  
  DATE ACTIVATED: SEP 02, 2015

NUMBER: 6226                            IA #: 6226
  DATE CREATED: SEP 03, 2015            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: BPSOS03
  NAME: Pull Data from BPS Response File
  ID: BPSOS03
 GENERAL DESCRIPTION:   This API pulls data from the BPS Response file in ECME. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$RESPONSE
 COMPONENT DESCRIPTION:   Return several fields from the BPS Response file.  
VARIABLES: BPSRX                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) IEN to file# 52, Prescription 
VARIABLES: BPSFILL                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) IEN to sub-file #52.1, Refill, on file#
 52, Prescription 
VARIABLES: BPSCOB                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Payer sequence (1, primary; 2, secondary;
 3, tertiary) 
VARIABLES: $$RESPONSE                   TYPE: Output
 VARIABLES DESCRIPTION:   [1] Total Amount Paid, file# 9002313.0301, field# 509 
 [2] Ingredient Cost Paid, field# 506 [3] Amount of Copay, field# 518 [4]
 Dispensing Fee Paid, field# 507 [5] Amount Applied to Periodic Deductible,
 field# 517 [6] Remaining Deductible Amount, field# 513 
COMPONENT/ENTRY POINT: $$INSPAID
 COMPONENT DESCRIPTION:   Returns Total Amount Paid by insurer.  
VARIABLES: N                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN to BPS Responses, file# 9002313.03 
VARIABLES: $$INSPAID                    TYPE: Output
 VARIABLES DESCRIPTION:   Sum of the Total Amount Paid fields (#509) from all
 entries in the Responses sub-file 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: JAN 25, 2016

NUMBER: 6227                            IA #: 6227
  DATE CREATED: SEP 11, 2015            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOREJU4
  NAME: OUTPATIENT PHARMACY REJECT COMMENTS
  ID: PSOREJU4
 GENERAL DESCRIPTION:   This is an API to allow the Pharmacist comments entered
 and stored in Outpatient Pharmacy to be shared with the subscribing package. 
 These are pharmacist comments pertaining to ePharmacy rejections received and
 the pharmacist comments about those rejections.  
  STATUS: Active
COMPONENT/ENTRY POINT: REJCOM
 COMPONENT DESCRIPTION:   REJCOM^PSOREJU4(RX,FIL,COB,.RET) is a procedure which
 exists in Outpatient Pharmacy and which is allowed to be called by ECME for
 the purpose of obtaining the pharmacist comments pertaining to all ECME 
 rejections for the given prescription, fill number, and COB payer sequence. 
 Data will be returned in a local array format.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN  (required) 
VARIABLES: FIL                          TYPE: Input
 VARIABLES DESCRIPTION:   fill number (required) 
VARIABLES: COB                          TYPE: Input
 VARIABLES DESCRIPTION:   COB - coordination of benefits insurance sequence
 indicator. This is an optional parameter.  If the COB is present, then the COB
 must match.  If the COB is not present, then no COB check is performed.  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   RET is the output array that is built. It must be
 passed by reference.  The structure is as follows: 
  
 RET(external reject code,date/time of comment,SEQ#) = 
  
   [1] date/time of comment 
   [2] user IEN (pointer to file 200) 
   [3] user comment text (up to 150 characters) 
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: FEB 12, 2016

NUMBER: 6228                            IA #: 6228
  DATE CREATED: SEP 14, 2015            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOREJU4
  NAME: MEDICATION PROFILE/PATIENT INFORMATION LIST MANAGER
  ID: PSOREJU4
 GENERAL DESCRIPTION:   This is an Integration Agreement between Outpatient
 Pharmacy and ECME.  The Chief Business Office eBusiness Solutions ePharmacy
 team requests the ability for the Outpatient Pharmacy Electronic Claims
 Coordinator (OPECC) using the ECME User Screen to be able to view both the
 Outpatient Pharmacy Medication Profile List Manager screen and the Outpatient
 Pharmacy Patient Information List Manager screen. This agreement allows ECME
 to call these PSO API entry points to display these List Manager screens.  
  STATUS: Active
COMPONENT/ENTRY POINT: MP
 COMPONENT DESCRIPTION:   Medication Profile List Manager screen display.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN (required) 
VARIABLES: FIL                          TYPE: Input
 VARIABLES DESCRIPTION:   Fill Number (required) 
COMPONENT/ENTRY POINT: PI
 COMPONENT DESCRIPTION:   Patient Information List Manager screen display.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN (required) 
VARIABLES: FIL                          TYPE: Input
 VARIABLES DESCRIPTION:   Fill Number (required) 
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: FEB 12, 2016

NUMBER: 6229                            IA #: 6229
  DATE CREATED: SEP 16, 2015
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSUTIL1
  NAME: PSSUTIL1                        ID: PSSUTIL1
 GENERAL DESCRIPTION:   This agreement allows the Outpatient Pharmacy
 application to invoke APIs in the PSSUTIL1 routine related to the dispensing
 of Outpatient Pharmacy prescriptions.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSSUTIL1
KEYWORDS: MXDAYSUP
KEYWORDS: DAY SUPPLY
COMPONENT/ENTRY POINT: $$MXDAYSUP(DRUG) 
 COMPONENT DESCRIPTION:   This API accepts a pointer to the DRUG file (#50) and
 returns the maximum number of days supply the medication can be dispensed for
 an outpatient prescription.  
VARIABLES: DRUG                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the DRUG file (#50). Required.  
VARIABLES: $$MXDAYSUP                   TYPE: Output
 VARIABLES DESCRIPTION:   Maximum number of days supply the medication can be
 dispensed for an outpatient prescription.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: OCT 26, 2015

NUMBER: 6230                            IA #: 6230
  DATE CREATED: SEP 28, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUESSO4
  NAME: VACAA BULK-LOAD NON-VA PROVIDER INFORMATION
  ID: XUESSO4
 GENERAL DESCRIPTION:   Bulk-load non-VA entities and providers to be
 identified in VistA when documenting patient care.  
  
 On August 7, 2014, the President signed into law PL 113-146, the Veterans 
 Access, Choice, and Accountability Act of 2014 (VACAA). The law offers an 
 additional authority for VHA to expand current capacity and ensure that 
 Veterans have timely access to high-quality care. The law creates a new 
 paradigm for providing health care, set forth in the Veterans Choice program
 provisions within Title I Section 101 of VACAA. VA is utilizing a Contractor
 to provide health care and third party administrative (TPA) services set forth
 through VACAA Section 101. As a result of this law, VA must upload a list of
 non-VA medical care providers into the VistA system in order to maintain an
 accurate and updated list of non-VA providers in the Choice program.  
  
 This interface is available under a private Integration Agreement for support
 of VACAA only, and should not be used under any other circumstances.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VACAA
COMPONENT/ENTRY POINT: VACAA
 COMPONENT DESCRIPTION:   This extrinsic function returns success or failure
 when adding a non-VA provider to the NEW PERSON file (#200).  
  
      Format:  $$VACAA^XUESSO4(INARRAY,AUTHCODE) 
  
 The value returned is 1 (success), 0 (not valid for this site), or -1^error if
 the provider could not be added.  
VARIABLES: INARRAY                      TYPE: Input
 VARIABLES DESCRIPTION:   (required) 
   INARRAY(0)  = VISN 
   INARRAY(1)  = NAME 
   INARRAY(2)  = DEGREE 
   INARRAY(3)  = SEX 
   INARRAY(4)  = STREET ADDRESS 1 
   INARRAY(5)  = STREET ADDRESS 2 
   INARRAY(6)  = STREET ADDRESS 3 
   INARRAY(7)  = CITY 
   INARRAY(8)  = STATE 
   INARRAY(9)  = ZIP 
   INARRAY(10) = NPI 
   INARRAY(11) = (Optional) TAX ID 
   INARRAY(12) = DEA # 
   INARRAY(13) = Subject Organization 
   INARRAY(14) = Subject Organization ID 
VARIABLES: AUTHCODE                     TYPE: Input
 VARIABLES DESCRIPTION:   Authorization code used to control access to this
 function. The phrase passed by this variable will be hashed with a SHA-256
 algorithm and compared to a stored value.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: AUG 29, 2016

NUMBER: 6231                            IA #: 6231
  DATE CREATED: SEP 29, 2015            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCNEUT7
  NAME: Date of Death Triggers Insurance Termination
  ID: IBCNEUT7
 GENERAL DESCRIPTION:   A new style MUMPS cross reference is added to DATE OF
 DEATH field (#.351) in the Patient (#2) file which is invoked when the DATE OF
 DEATH is populated and has not previously been entered.  The set code of this
 cross reference calls DEATH^IBCNEUT7.  This IB code terms all of the patient's 
 active insurance policies (without an expiration date). The term date is to be
 set to date of death.  This functionality does not trump any existing or
 future validation/rules for the actual date of death.  The patient insurance
 policies are stored in the INSURANCE TYPE (#2.312) subfile in the Patient (#2)
 file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DOD
KEYWORDS: DATE OF DEATH
KEYWORDS: IBCNEUT7
COMPONENT/ENTRY POINT: DEATH
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (ien) of the patient in the
 file PATIENT (#2) 
VARIABLES: X(1)                         TYPE: Input
 VARIABLES DESCRIPTION:   Internal Date of Death (FileMan format).  
SUBSCRIBING PACKAGE: REGISTRATION
  DATE ACTIVATED: JAN 08, 2016

NUMBER: 6232                            IA #: 6232
  FILE NUMBER: 2.98                     GLOBAL ROOT: DPT(D0
  DATE CREATED: SEP 29, 2015            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  NAME: APPT MULTIPLE 2.98 READ/WRITE   ID: DPT(D0
GLOBAL REFERENCE: DPT(D0,'S',D1,0
FIELD NUMBER: .01                       FIELD NAME: CLINIC
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: PURPOSE OF VISIT
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: NO-SHOW/CANCELLED BY
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 15                        FIELD NAME: NO-SHOW CANCEL DATE/TIME
  LOCATION: 0;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16                        FIELD NAME: CANCELLATION REASON
  LOCATION: 0;15                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9.5                       FIELD NAME: APPOINTMENT TYPE
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 19                        FIELD NAME: DATA ENTRY CLERK
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20                        FIELD NAME: DATE APPT MADE
  LOCATION: 0;19                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 24
  FIELD NAME: APPOINTMENT TYPE SUB-CATEGORY
  LOCATION: 0;24                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 25                        FIELD NAME: SCHEDULING REQUEST TYPE
  LOCATION: 0;25                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 26                        FIELD NAME: NEXT AVA. APPT. INDICATOR
  LOCATION: 0;26                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 27                        FIELD NAME: DESIRED DATE OF APPOINTMENT
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 28                        FIELD NAME: FOLLOW-UP VISIT
  LOCATION: 1;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17                        FIELD NAME: CANCELLATION REASON
  LOCATION: R;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 18                        FIELD NAME: APPT. CANCELLED
  LOCATION: 0;17                        ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   VA Point of Service (Kiosks) (VPS) allows Veterans to
 Make and Cancel clinic appointments using the VetLink Kiosk. This ICR provides
 read/write access to  the APPOINTMENT SUB-FILE #2.98 defined in the PATIENT
 file (2).  The sub-file contains patient appointment data such as clinic,
 appointment date/time and reason for the appointment to be captured.  
  
  STATUS: Withdrawn
KEYWORDS: UNSCHEDULED APPOINTMENT
KEYWORDS: VPS
KEYWORDS: APPOINTMENT 1900
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   
  

NUMBER: 6233                            IA #: 6233
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: SEP 29, 2015            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  NAME: READ/WRITE TO HOSPITAL LOCATION file (#44)
  ID: SC(
GLOBAL REFERENCE: SC(D0,S,D1,1,D2)
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: LENGTH OF APP'T
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7                         FIELD NAME: DATA ENTRY CLERK
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8                         FIELD NAME: DATE APPOINTMENT MADE
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: OVERBOOK
  LOCATION: OB;1                        ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: SC(D0,ST,D1,1)
FIELD NUMBER: 1                         FIELD NAME: CURRENT AVAILABILITY
  LOCATION: 1;E1,90                     ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: SC(D0,ST,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PATTERN DATE
  LOCATION:  0;1                        ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: SC(D0,SL)
FIELD NUMBER: 1912                      FIELD NAME: LENGTH OF APP'T
  LOCATION: SL;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1913                      FIELD NAME: VARIABLE APP'NTMENT LENGTH
  LOCATION: SL;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1914                      FIELD NAME: HOUR CLINIC DISPLAY BEGINS
  LOCATION: SL;3                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1915
  FIELD NAME: HOLD SC SLOTS UNTIL # OF DAYS
  LOCATION: SL;4                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1916                      FIELD NAME: PRINCIPAL CLINIC
  LOCATION: SL;5                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1917                      FIELD NAME: DISPLAY INCREMENTS PER HOUR
  LOCATION: SL;6                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1918                      FIELD NAME: OVERBOOKS/DAY MAXIMUM
  LOCATION: SL;7                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1918.5                    FIELD NAME: SCHEDULE ON HOLIDAYS?
  LOCATION: SL;8                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,SDP)
FIELD NUMBER: 2002
  FIELD NAME: MAX # DAYS FOR FUTURE BOOKING
  LOCATION: SDP;2                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,S,D1,1,D2,OB)
FIELD NUMBER: 9                         FIELD NAME: OVERBOOK
  LOCATION: OB;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,SDPROT)
FIELD NUMBER: 2500                      FIELD NAME: PROHIBIT ACCESS TO CLINIC?
  LOCATION: SDPROT;1                    ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,SDPRIV,D1)
 GLOBAL DESCRIPTION:   DIRECT GLOBAL READ 
  
GLOBAL REFERENCE: SC(D0,S,D1,1,D2,C)
FIELD NUMBER: 303                       FIELD NAME: CHECKED OUT
  LOCATION: C;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: SC(D0,T_0-6,D1,1)
 GLOBAL DESCRIPTION:   $ORDER and direct reads thru the "T0 - "T6" nodes 
  
GLOBAL REFERENCE: SC(ARAD)
 GLOBAL DESCRIPTION:   ^SC("ARAD",IEN OF file 44,APPOINTMENT DATE/TIME",DFN) -
 direct global write to the PRIOR X-RAY RESULTS TO CLINIC?(ARAD) index.  
  
GLOBAL REFERENCE: SC(AWASI)
 GLOBAL DESCRIPTION:   ^SC("AWASI",IEN of REQUEST/CONSULTATION file (123))  -
 direct global kill of the AWASI (CONSULT LINK) cross-reference (when
 cancellation of appt is performed).  
  
 GENERAL DESCRIPTION:   VA Point of Service (Kiosks) (VPS) allows Veterans to
 Make and Cancel clinic appointments using the VetLink Kiosk. This ICR provides
 read/write access to the subfiles 44.001, 44.003, and 44.005 of the HOSPITAL
 LOCATION file (#44).  
  
  STATUS: Withdrawn
KEYWORDS: VPS
KEYWORDS: SCHEDULING
KEYWORDS: 44.002
KEYWORDS: 44.003
KEYWORDS: 44.005
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   
  

NUMBER: 6234                            IA #: 6234
  FILE NUMBER: 161.95                   GLOBAL ROOT: FBAA(161.95
  DATE CREATED: SEP 30, 2015            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IPAC VENDOR AGREEMENT FILE
  ID: FBAA(161.95
GLOBAL REFERENCE: FBAA(161.95,D0
 GENERAL DESCRIPTION:   Fee Basis Claims System needs the ability to read the
 records found within the file to display to clerks for proper payment of
 claims identified as IPAC. All fields are displayed to the user for proper
 identifaction.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
 SUBSCRIBING DETAILS:   Fee Basis Claims System (FBCS) requires access to read
 the values found within the IPAC VENDOR file to display during the payment
 process. This is a read-only action and does not modify any fields in the
 file.  
  DATE ACTIVATED: SEP 30, 2015

NUMBER: 6235                            IA #: 6235
  FILE NUMBER: 161.96                   GLOBAL ROOT: FBAA(161.96
  DATE CREATED: SEP 30, 2015            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IPAC VENDOR AGREEMENT MRA FILE
  ID: FBAA(161.96
GLOBAL REFERENCE: FBAA(161.96,AS,P
 GENERAL DESCRIPTION:   Fee Basis Claims System needs the ability to check
 whether pending IPAC MRAs are ready for trasmission to Austin (Central Fee) by
 using the AS cross reference.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
 SUBSCRIBING DETAILS:   Fee Basis Claims System (FBCS) needs the ability to
 check the "AS" cross reference to determine if MRAs are pending transmission.  
  DATE ACTIVATED: SEP 30, 2015

NUMBER: 6236                            IA #: 6236
  DATE CREATED: SEP 30, 2015            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  ROUTINE: FBAAV8                       NAME: FBAAV8
  ID: FBAAV8
 GENERAL DESCRIPTION:   During the Transmit to Austin functionality, FBCS needs
 the ability to trigger the sending of the IPAC MRA messages along with the
 other MRAs and batches sent during this process. FBCS will call FBAAV8 to
 trigger the creation of the messages (MailMan) if there are pending MRAs in
 the IPAC VENDOR AGREEMENT IPAC FILE (#161.96) AS cross reference.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: SEP 30, 2015

NUMBER: 6237                            IA #: 6237
  FILE NUMBER: 346                      GLOBAL ROOT: RC(346,
  DATE CREATED: SEP 30, 2015            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ALLOW IB ACCESS TO AR EDI RARC DATA
  ORIGINAL NUMBER: 6237                 ID: RC(346,
GLOBAL REFERENCE: RC(346,0
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Remittance Advice Remark Code 
 GLOBAL DESCRIPTION:   This file stores the codes and descriptions of the
 Remittance Advice Remark Codes (RARC) file published by the Washington
 Publishing Company.  The RARC data is updated by the FSC that has a
 subscription to WPC for these codes.  This file was implemented in patch
 PRCA*4.5*303.  ^RC(346,D0,0)= (#.01) CODE [1F]              
GLOBAL REFERENCE: RC(346,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the long description of the code maintained by
 Washington Publishing Company.  
 GLOBAL DESCRIPTION:   This stores the long description of the CODE. 
 ^RC(346,D0,1,D1,0)= (#.01) DESCRIPTION [1W] ^              
GLOBAL REFERENCE: RC(346,D0,1,0)
FIELD NUMBER: 4                         FIELD NAME: DESCRIPTION
  LOCATION: 1;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the multiple that stores the long description of
 the code.  
 GLOBAL DESCRIPTION:   ^RC(346,D0,1,0)=^346.04^^  (#4) DESCRIPTION              
   
 GENERAL DESCRIPTION:   This integration agreement allows Integrated Billing
 (IB) to have read access to the code (.01) and description (#4) field of AR
 file #346 - AR EDI RARC DATA.  This is a read-only action and does not modify
 any fields in the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CARC
KEYWORDS: RARC
KEYWORDS: 346
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   IB needs access to AR file #346(AR EDI RARC DATA) to be
 deployed w/PRCA*4.5*303, specifically the word-processing description
 field(#4) and the .01 field(code) for EOB reports and displays being modified
 for IB*2.0*547.  
  DATE ACTIVATED: DEC 31, 2015

NUMBER: 6238                            IA #: 6238
  FILE NUMBER: 345                      GLOBAL ROOT: RC(345,
  DATE CREATED: SEP 30, 2015            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IB ACCESS TO AR EDI CARC DATA
  ORIGINAL NUMBER: 6237                 ID: RC(345,
GLOBAL REFERENCE: RC(345,0
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Claims Adjustment Reason Code 
 GLOBAL DESCRIPTION:   This file stores the codes and descriptions of the Claim
 Adjustment Remittance Codes (CARC) file published by the Washington Publishing
 Company. The CARC data is updated by the FSC, which has a subscription from
 WPC to obtain updated codes and descriptions.  File implemented for patch
 PRCA*4.5*303 ^RC(345,D0,0)= (#.01) CODE [1F]              
GLOBAL REFERENCE: RC(345,D0,1,0)
FIELD NUMBER: 4                         FIELD NAME: DESCRIPTION
  LOCATION: 1;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Mutliple that stores the long description of the code.  
 GLOBAL DESCRIPTION:   ^RC(345,D0,1,0)=^345.04^^  (#4) DESCRIPTION              
   
GLOBAL REFERENCE: RC(345,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the long description of the code maintained by
 Washington Publishing Company.  
 GLOBAL DESCRIPTION:   ^RC(345,D0,1,D1,0)= (#.01) DESCRIPTION [1W] ^            
  
 GENERAL DESCRIPTION:   This integration agreement allows Integrated Billing
 (IB) to have read access to the code (.01) and description (#4) field of AR
 file #345 - AR EDI CARC DATA.  This is a read-only action and does not modify
 any fields in the file. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 345
KEYWORDS: CARC
KEYWORDS: RARC
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   IB needs access to AR file #345 (AR EDI CARC DATA), to
 be deployed with PRCA*4.5*303, specifically the word-processing description 
 field (#4) and the .01 field (code) for EOB reports and displays being
 modified for IB*2.0*547.  
  DATE ACTIVATED: DEC 31, 2015

NUMBER: 6239                            IA #: 6239
  DATE CREATED: OCT 01, 2015            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: WVRPCPT1
  NAME: RETRIEVE PATIENT'S DATA FOR FINDINGS
  ID: WVRPCPT1
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to retrieve a sub-set of a patient's data from the Women's Health package in a
 format that is easily convertible into Clinical Reminders general findings.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PREGNANCY DATA
KEYWORDS: LACTATION DATA
KEYWORDS: FINDINGS
COMPONENT/ENTRY POINT: GETFINDS(RESULT,WVDFN,WVVISIT)
 COMPONENT DESCRIPTION:   This entry point will return the data associated with
 the specified patient and visit. Data that is marked as entered in error is
 not returned.  
VARIABLES: RESULT                       TYPE: Input
 VARIABLES DESCRIPTION:   The subscript in the ^TMP global under which to
 return data or error messages. This value is required.  
VARIABLES: WVDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient in the WV
 PATIENT file (#790). This value is required.  
VARIABLES: WVVISIT                      TYPE: Input
 VARIABLES DESCRIPTION:   The visit associated with the data to return. This is
 either the IEN of the entry in the VISIT file (#9000010) or the Text
 Integration Utilities (TIU) visit string. This value is required.  
  
 The TIU visit string is a semi-colon delimited string of data from the VISIT
 file formatted as: 
   
   H;D;E 
  
   H: internal value of the HOSPITAL LOCATION 
      field (#22) 
   D: internal value of the VISIT/ADMIT DATE&TIME 
      field (#.01) 
   E: internal value of the ENCOUNTER TYPE 
      field (#15003) 
VARIABLES: TMP(RESULT,$J)               TYPE: Output
 VARIABLES DESCRIPTION:   The global node in which data is returned.  
  
 Format: 
  
 ^TMP(RESULT,$J)=Caret-delimited string 
   RESULT - the value in the RESULT input variable 
   Caret-delimited string - status of the call to 
                            GETFINDS 
  PIECE   VALUE 
 =======================
  1       -1 to denote an error occurred 
          >-1 to denote the number of entries 
          returned 
  2       ERROR MESSAGE if an error occurred 
          "" if no error occurred 
  
 For fields that are not multiples: ^TMP(RESULT,$J,PACKAGE,"FILE NUMBER", 
      "FIELD NUMBER")=VALUE 
   RESULT - the value in the RESULT input variable 
   PACKAGE - IEN of the Women's Health entry in the 
             PACKAGE file (#9.4) 
   "FILE NUMBER" - the file number from which the 
                   data comes 
   "FIELD NUMBER" - the field number in which the 
                    data resides 
   VALUE - the data in external format 
  
 For fields that are multiples: ^TMP(RESULT,$J,PACKAGE,"FILE NUMBER", 
      "FIELD NUMBER","RECORD NUMBER")=VALUE 
   RESULT - the value in the RESULT input variable 
   PACKAGE - IEN of the Women's Health entry in the 
             PACKAGE file (#9.4) 
   "FILE NUMBER" - the file number from which the 
                   data comes 
   "FIELD NUMBER" - the field number in which the 
                    data resides 
   "RECORD NUMBER" - IEN of the entry from which 
                     the data comes 
   VALUE - the data in external format 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: NOV 17, 2017

NUMBER: 6240                            IA #: 6240
  DATE CREATED: OCT 06, 2015
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA6240
  STATUS: Pending

NUMBER: 6241                            IA #: 6241
  DATE CREATED: OCT 06, 2015
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA6241
  STATUS: Pending

NUMBER: 6242                            IA #: 6242
  DATE CREATED: OCT 06, 2015
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA6242
  STATUS: Pending

NUMBER: 6243                            IA #: 6243
  DATE CREATED: OCT 06, 2015            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPDP
  NAME: EPHARMACY BILLABLE STATUS       ID: IBNCPDP
 GENERAL DESCRIPTION:   This function returns the ePharmacy Billable status to
 subscribing packages.  The subscribing application shall pass in the
 PRESCRIPTION File #52 IEN and the BILLING ELIGIBILITY INDICATOR: TRICARE(T), 
 CHAMPVA(C), or VETERAN(V) field of PRESCRIPTION file to make this 
 determination.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$BILLABLE(DRUG,ELIG,IBRMARK,IBBDAR)
VARIABLES: DRUG                         TYPE: Input
 VARIABLES DESCRIPTION:   Prescription File IEN (required) 
VARIABLES: ELIG                         TYPE: Input
 VARIABLES DESCRIPTION:   Billing Eligibility Indicator (T,C,V), field #85 of
 the Prescription file or Refill sub-file.  If not defined, assume "V"
 (Veteran) 
VARIABLES: IBRMARK                      TYPE: Output
 VARIABLES DESCRIPTION:   Return value is in the format: 
  
 "DRUG NOT BILLABLE" - only set if drug is not billable (pass by reference) 
VARIABLES: IBBDAR                       TYPE: Output
 VARIABLES DESCRIPTION:   Return array is in the following format: 
        IBBDAR("DRUG-BILLABLE")=1 or 0 
        IBBDAR("DRUG-BILLABLE TRICARE")=1 or 0 
        IBBDAR("DRUG-BILLABLE CHAMPVA")=1 or 0 
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: FEB 01, 2016

NUMBER: 6244                            IA #: 6244
  DATE CREATED: OCT 06, 2015            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBNCPDR
  NAME: RETRIEVE SENSITIVE DIAGNOSIS DRUG FROM DRUG FILE
  ID: IBNCPDR
 GENERAL DESCRIPTION:   This function returns the SENSITIVE DIAGNOSIS DRUG
 Field #87 from the DRUG File (#50) "EPH" node to subscribing packages.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$SENS(DRUG,IBBDAR)
 COMPONENT DESCRIPTION:   
    Function value: 
        1 if the drug is a Sensitive Diagnosis Drug 
        0 if the drug is not a Sensitive Diagnosis Drug 
VARIABLES: DRUG                         TYPE: Input
 VARIABLES DESCRIPTION:   DRUG file IEN (required) 
VARIABLES: IBBDAR                       TYPE: Output
 VARIABLES DESCRIPTION:   Pass by reference.  This is an array of values for
 ECME processing.  (optional parameter) 
   
 Return array is in the following format: 
                             
     IBBDAR ("DRUG-SENSITIVE DX")=1 or 0 
VARIABLES:  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: FEB 01, 2016

NUMBER: 6245                            IA #: 6245
  DATE CREATED: OCT 06, 2015
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSS50
  NAME: RETURN EBILLABLE & SENSITIVE DIAGNOSIS DRUG FLDS
  ID: PSS50
 GENERAL DESCRIPTION:   This function returns the EPHARMACY BILLABLE, EPHARMACY
 BILLABLE (TRICARE), EPHARMACY BILLABLE (CHAMPVA) and SENSITIVE DIAGNOSIS DRUG 
 fields from the DRUG File (#50) "EPH" node to subscribing packages.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$PSSBILSD(PSSIEN,EPHBILSD)
VARIABLES: EPHBILL                      TYPE: Output
 VARIABLES DESCRIPTION:   EPHARMACY BILLABLE Field #84 of the DRUG file 
VARIABLES: EPHTRI                       TYPE: Output
 VARIABLES DESCRIPTION:   EPHARMACY BILLABLE (TRICARE) field #85 of the DRUG
 file 
VARIABLES: EPHCHAMP                     TYPE: Output
 VARIABLES DESCRIPTION:   EPHARMACY BILLABLE (CHAMPVA) field #86 of the DRUG
 file 
VARIABLES: EPHSENS                      TYPE: Output
 VARIABLES DESCRIPTION:   EPHARMACY SENSITIVE DIAGNOSIS DRUG field #87 of the
 DRUG file 
VARIABLES: EPHBILSD                     TYPE: Output
 VARIABLES DESCRIPTION:   
  
 Return array is in the following format: 
  
 EPHBILSD=EPHBILL^EPHTRI^EPHCHAMP^EPHSENS 
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN (required) 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: FEB 12, 2016

NUMBER: 6246                            IA #: 6246
  DATE CREATED: OCT 07, 2015
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM INFO SOURCE
  REMOTE PROCEDURE: PXVIMM INFO SOURCE
 GENERAL DESCRIPTION:   
 *******************************************************************
  
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library for list of retired HMP ICRs.  
  
 *******************************************************************
  
  
  Returns entries from the IMMUNIZATION INFO SOURCE file (920.1).  INPUT
 PARAMETER: PXVFLTR                PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Filter. Possible values are: 
     R:XXX - Return entry with IEN XXX.  
     H:XXX - Return entry with HL7 Code XXX.  
     N:XXX - Return entry with #.01 field equal to XXX 
     S:X   - Return all entries with a status of X.  
             Possible values of X: 
                A - Active Entries 
                I - Inactive Entries 
                B - Both active and inactive entries 
   
  Defaults to "S:B".  INPUT PARAMETER: PXVDATE                PARAMETER TYPE:
 LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 2 
  DESCRIPTION:   Used for determining status (both for filtering and for return
 value). 
  Defaults to NOW.  
  RETURN PARAMETER DESCRIPTION:   
  Returns: 
     PXVRSLT(0)=Count of elements returned (0 if nothing found) 
     PXVRSLT(n)=IEN^Name^HL7 Code^Status (1:Active, 0:Inactive) 
    
  When filtering based off IEN, HL7 Code, or #.01 field, only one entry will 
  be returned in PXVRSLT(1).  
   
  When filtering based off status, multiple entries can be returned. The 
  first entry will be returned in subscript 1, and subscripts will be 
  incremented by 1 for further entries. Entries will be sorted 
  alphabetically.  
   
  If no entries are found based off the filtering criteria, PXVRSLT(0) will 
  equal 0, and there will be no data returned in the subsequent subscripts.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: IMMUNIZATION
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: OCT 18, 2017

NUMBER: 6247                            IA #: 6247
  GLOBAL ROOT: KMPTMP('KMPV'            DATE CREATED: OCT 08, 2015
  CUSTODIAL PACKAGE: CAPACITY MANAGEMENT TOOLS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Direct KMPV read to KMPTMP
  ID: KMPTMP('KMPV'
 GENERAL DESCRIPTION:   Allows VistA System Monitor (VSM) to read and write
 data directly to temporary global ^KMPTMP("KMPV". 
  
 ^KMPTMP has no file number. This is a temporary global specific to the 
 Capacity Planning packages (RUM-KMPR, SAGG-KMPS, CM Tools-KMPD and VSM-KMPV).
 The data is gathered during the collection periods and stored in this global.
 Daily there are TaskMan jobs that put this global in FileMan files and purge
 the temporary global. 
  STATUS: Active
SUBSCRIBING PACKAGE: VISTA SYSTEM MONITOR
  DATE ACTIVATED: NOV 18, 2015

NUMBER: 6248                            IA #: 6248
  DATE CREATED: OCT 15, 2015            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: BPSPSOU1
  NAME: Validation messages to Resubmit or Reverse a claim
  ID: BPSPSOU1
 GENERAL DESCRIPTION:   This API does validation checks before resubmitting or
 reversing an ECME claim.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$VAL(RXIEN,FILL,PSOELIG,ACTION,COB,REVREAS)
 COMPONENT DESCRIPTION:   This api validates an ECME claim when Reversing or
 Resubmitting the claim.  
VARIABLES: RXIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Prescription ien number from file 52 (^PSRX).  
VARIABLES: FILL                         TYPE: Input
 VARIABLES DESCRIPTION:   Prescription number.  
VARIABLES: PSOELIG                      TYPE: Input
 VARIABLES DESCRIPTION:   Tricare or CHAMPVA.  
VARIABLES: ACTION                       TYPE: Input
 VARIABLES DESCRIPTION:   "REV" for Reverse or "RES for Resubmit.  
VARIABLES: COB                          TYPE: Output
 VARIABLES DESCRIPTION:   Coordination of Benefits.  
VARIABLES: REVREAS                      TYPE: Output
 VARIABLES DESCRIPTION:   This variable holds the text reason for reversing a
 claim.  
VARIABLES: $$VAL                        TYPE: Output
 VARIABLES DESCRIPTION:   0 = Failed validation checks.  1 = Passed validation
 checks.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: JAN 25, 2016

NUMBER: 6249                            IA #: 6249
  DATE CREATED: OCT 15, 2015
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA6249
  STATUS: Pending

NUMBER: 6250                            IA #: 6250
  DATE CREATED: OCT 15, 2015            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCNRHLU
  NAME: e-Pharmacy HL7 Processing       ID: IBCNRHLU
 GENERAL DESCRIPTION:   ECME (Electronic Claims Management Engine) is the
 initial receiving point for incoming HL7 messages from FSC (Financial Services
 Center).  When the system detects that an inbound MFN (Master File
 Notification) message is intended to update the IB (Integrated Billing) files
 of e-Pharmacy, then ECME makes the following calls into the IB processing
 routines to accomplish the task.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: HLT
 COMPONENT DESCRIPTION:   Receive e-Pharmacy MFN (Master File Notification)
 message.  Local variable SEG should be defined upon entry and contains the
 segment identifier.  Local array IBSEG should also be defined upon entry and 
 contains the parsed data from the inbound MFN message for processing.  The
 data from the HL7 message is stored into the following files/sub-files,
 depending on the particular segment groupings being processed: 
  
 Segment ID     File/Sub-file 
 ----------     -------------
 ZPT            366.01   NCPDP PROCESSOR 
  
 ZCM            366.012  NCPDP PROCESSOR (CONTACT MEANS 
  
                         sub-file) 
  
  
    
 ZPB            366.02   PHARMACY BENEFITS MANAGER (PBM) 
  
 ZCM            366.022  PHARMACY BENEFITS MANAGER (PBM) 
  
                         (CONTACT MEANS sub-file) 
  
  
    
 ZPL            366.03   PLAN 
  
 ZCM            366.032  PLAN (CONTACT MEANS sub-file) 
  
  
  
 ZPP            366.03   PLAN 
  
 ZCM            366.0312 PLAN (RX CONTACT MEANS sub-file) 
COMPONENT/ENTRY POINT: MFK
 COMPONENT DESCRIPTION:   Send e-Pharmacy MFK (Master File Application
 Acknowledgment) message.  Local array DATAMFK should be defined upon entry and
 contains the data to populate the MFI (Master File Identification) and MFA
 (Master File ACK) segments.  
COMPONENT/ENTRY POINT: ERR
 COMPONENT DESCRIPTION:   Send e-Pharmacy HL7 error messages to the local mail
 group defined in MESSAGES MAILGROUP (field #51.04) within IB SITE PARAMETERS
 (file #350.9).  Local array MSG should be defined upon entry and contains the 
 actual error text message to be sent in the MailMan message.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: FEB 01, 2016

NUMBER: 6251                            IA #: 6251
  DATE CREATED: OCT 21, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWU
  NAME: ACTLOC~ORWU                     ID: ORWU
 GENERAL DESCRIPTION:   The Enterprise Health Management Platform (HMP) uses
 the $$ACTLOC^ORWU API in order to determine if a specified hospital location
 in the Hospital Location file (#44) is an active location.  
  
 Returns 1 is the location is active, otherwise returns 0 (zero).  
  
 **NOTE: HMP is the only package that will be granted this level of access. ** 
  
  
 **************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library for list of retired HMP ICRs.  
 **************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: ACTLOC
KEYWORDS: ORWU
COMPONENT/ENTRY POINT: ACTLOC
 COMPONENT DESCRIPTION:   Returns 1 if the location in the Hospital Location
 file (#44) is an active location. Otherwise, returns 0 (zero).  
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the location entry in the Hospital
 Location file (#44).  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: MAR 10, 2016

NUMBER: 6252                            IA #: 6252
  DATE CREATED: OCT 21, 2015
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: GMRAPENC                     NAME: GMRAPENC
  ID: GMRAPENC
 GENERAL DESCRIPTION:   HMP calls the CLP2CLDA^GMRAPENC API to return the drug
 class code and drug class classification for a specific drug. 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: CLP2CLDA
KEYWORDS: GMRAPENC
COMPONENT/ENTRY POINT: CLP2CLDA
 COMPONENT DESCRIPTION:   Returns the Drug Class Code and Drug Class
 Classification for the specified drug.  
VARIABLES: GMRAIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN for the entry in the VA Drug Class file
 (#50.605).  
VARIABLES: GMRARET                      TYPE: Output
 VARIABLES DESCRIPTION:   Return variable containing the Drug Class Code ^ Drug
 Class Classification.  
COMPONENT/ENTRY POINT: INP2INNA
 COMPONENT DESCRIPTION:   HMP calls the INP2INNA^GMRAPENC API to get the Drug
 Ingredient Names.  
VARIABLES: GMRAIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the entry in the Drug Ingredients file
 (#50.416).  
VARIABLES: GMRARET                      TYPE: Output
 VARIABLES DESCRIPTION:   The Drug Ingredient Name from teh Drug Ingredients
 file (50.416).  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6253                            IA #: 6253
  DATE CREATED: OCT 21, 2015
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: PXVIMM ADMIN ROUTE
 GENERAL DESCRIPTION:   Returns entries from the IMM ADMINISTRATION ROUTE file
 (920.2).  
  STATUS: Withdrawn
KEYWORDS: IMMUNIZATION
KEYWORDS: IMM ADMINISTRATION ROUTE

NUMBER: 6254                            IA #: 6254
  DATE CREATED: OCT 26, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORQQPL4
  NAME: LEXXFRM~ORQQPL4                 ID: ORQQPL4
 GENERAL DESCRIPTION:   HMP calls LEXXFRM^ORQQPL4 from PROB^HMPEF to transform
 text for the SCT look-up.  
  
 **************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library for list of retired HMP ICRs.  
 **************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: LEXXFRM
KEYWORDS: ORQQPL4
COMPONENT/ENTRY POINT: LEXXFRM
 COMPONENT DESCRIPTION:   Transforms text for the SCT look-up.  
VARIABLES: ELEMENT                      TYPE: Both
 VARIABLES DESCRIPTION:   Where IEN is the IEN for the entry in the Expressions
 file (#757.01) and Displayable Text is the .01 field for the entry in the
 Expressions file (#757.01) 
VARIABLES: ORDT                         TYPE: Input
 VARIABLES DESCRIPTION:   The Date of Interest or date the text is transformed. 
 
VARIABLES: ORAPP                        TYPE: Input
 VARIABLES DESCRIPTION:   The application that is making inquiry. HMP utilizes
 "GMPX" to reference the Problem List Standard subset.  
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   Returns a string of parsed data elements. IEN ^
 Displayable Text ^ ICD ^ ICDIEN ^ CodeSys ^ Concept Code ^ Designation Code ^
 ICD Coding System.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP calls the LEXXFRM^ORQQPL4 to transform text for the
 SCT look-up.  
  DATE ACTIVATED: NOV 13, 2015

NUMBER: 6255                            IA #: 6255
  DATE CREATED: OCT 26, 2015
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: GMRAUTL                      NAME: $$OUTTYPE~GMRAUTL
  ID: GMRAUTL
 GENERAL DESCRIPTION:   HMP calls the $$OUTTYPE^GMRAUTL API to transform the
 internal for the   Allergy Type field (#3.1) in the Patient Allergies file
 (#120.8) or the Allergy Type field (#1) in the GMR Allergies file (#120.82) to
 the external value.  
  STATUS: Withdrawn
KEYWORDS: OUTTYPE
KEYWORDS: GMRAUTL
COMPONENT/ENTRY POINT: $$OUTTYPE
 COMPONENT DESCRIPTION:   Returns the external value for the Allergy Type field
 (#3.1) for the Patient Allergies file (#120.8) or the Allergy Type field (#1)
 for the GMR Allergies file (#120.82).  
VARIABLES: GMRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   The internal code for the allergy type.  
VARIABLES: FXN                          TYPE: Output
 VARIABLES DESCRIPTION:   Returns the external value of the allergy type field. 
 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6256                            IA #: 6256
  DATE CREATED: OCT 29, 2015            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DELETE SCREEN NODES
GLOBAL REFERENCE: DD(9000010.11,.01,12)
GLOBAL REFERENCE: DD(9000010.11,.01,12.1)
GLOBAL REFERENCE: DD(9000010.07,.04,12)
GLOBAL REFERENCE: DD(9000010.07,.04,12.1)
GLOBAL REFERENCE: DD(9000010.18,.04,12)
GLOBAL REFERENCE: DD(9000010.18,.04,12.1)
GLOBAL REFERENCE: DD(9000011,.05,12)
GLOBAL REFERENCE: DD(9000011,.05,12.1)
 GENERAL DESCRIPTION:   There is a bug in FileMan that is not deleting the
 screen nodes (12 and 12.1) out of the DD global when a DD update is sent out
 via KIDS. The PCE team is therefore requesting a one-time direct delete access
 to the following nodes: 
  
 ^DD(9000010.11,.01,12) 
  
 ^DD(9000010.11,.01,12.1) 
  
 This will be used in the PX*1*210 Post-Install Routine PXVP210.  
  STATUS: Active
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   The following nodes will be deleted in patch PX*1*211
 by the init routine PXP211I: 
  
         V CPT 
         ^DD(9000010.18,.04,12) 
         ^DD(9000010.18,.04,12.1) 
         V POV 
         ^DD(9000010.07,.04,12) 
         ^DD(9000010.07,.04,12.1) 
SUBSCRIBING PACKAGE: PROBLEM LIST
 SUBSCRIBING DETAILS:   The following nodes will be deleted by patch GMPL*2*53
 by the init routine GMPLY53: 
  
          ^DD(9000011,.05,12) 
          ^DD(9000011,.05,12.1) 
  DATE ACTIVATED: NOV 04, 2015

NUMBER: 6257                            IA #: 6257
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100
  DATE CREATED: NOV 03, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: GMRC READ OF OR(100 GLOBAL
  ID: OR(100
GLOBAL REFERENCE: OR(100
FIELD NUMBER: .01                       FIELD NAME: ORDER #
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: OBJECT OF ORDER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: WHEN ENTERED
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 23                        FIELD NAME: TO 
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 61                        FIELD NAME: NATURE OF DC
  LOCATION: 6;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 65                        FIELD NAME: DC REASON TEXT
  LOCATION: 6;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1                        FIELD NAME: ORDERABLE ITEMS
  LOCATION: .1;0                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This ICR is temporary and only applicable to
 GMRC*3.0*85.  It will be retired when the patch has been nationally released
 and the compliance window and warranty periods have elapsed.  
  
 For emergency patch GMRC*3.0*85, GMRC needs to access and read the ^OR(100
 global.  This patch has an emergent need to quickly search the ORDER file
 (#100) global in order to find consult/procedure orders that have been
 rejected with a very specific message of "Code not valid for Coding System".  
  
 This search output will assist sites with identifying and ensuring that all
 Veterans who may have had consult orders rejected by a known GMRC defect have
 had a replacement order entered into the system.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 29, 2016
KEYWORDS: GMRC
KEYWORDS: OR(100
KEYWORDS: ORDER
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Via GMRC*3.0*85, GMRC will read the following index and
 global locations from the ORDER file (#100) global ^OR(100.  
  
 ^OR(100,"AF",DA ORDER IEN OBJECT OF ORDER [0;2] ORDERABLE ITEM of the
 ORDERABLE ITEMS multiple 
         ORDERABLE ITEMS (Multiple-100.001), [.1;0] 
           .01  ORDERABLE ITEM (MP101.43'), [0;1] WHEN ENTERED [0;7] NATURE OF
 DC [6;1] DC REASON TEXT [6;5] 
  
 This is direct read-only access of the ^OR(100 global.  No data will be 
 altered in the ^OR(100 global.  
  DATE ACTIVATED: NOV 04, 2015

NUMBER: 6258                            IA #: 6258
  DATE CREATED: NOV 05, 2015            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PXRMDLL                      NAME: LOAD PXRMDLL
  ID: PXRMDLL
 GENERAL DESCRIPTION:   PXRMDLL provides the capability to load/retrieve
 clinical reminder dialog questions into an array.  
  STATUS: Withdrawn                     EXPIRATION DATE: OCT 01, 2016
KEYWORDS: PXRMDLL
KEYWORDS: LOAD
COMPONENT/ENTRY POINT: LOAD
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (Kiosks) needs to provide
 identified behavioral clinical reminders to VetLink for presentation to clinic
 staff and/or patients.  

NUMBER: 6259                            IA #: 6259
  FILE NUMBER: 811.9                    GLOBAL ROOT: PXD(811.9,D0,0
  DATE CREATED: NOV 05, 2015            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: 811.9 READ  LINKED REMINDER
  ID: PXD(811.9,D0,0
GLOBAL REFERENCE: PXD(811.9,ORREM,51
FIELD NUMBER: 51                        FIELD NAME: LINKED REMINDER DIALOG
  LOCATION: 51;1                        ACCESS: Read w/Fileman
  STATUS: Active
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (Kiosks) (VPS) needs to do a
 FileMan read of field 51 (LINKED REMINDER DIALOG) from file #811.9. VPS needs
 to provide behavioral clinical reminders to VetLink.  The LINKED REMINDER
 DIALOG field will be used to access applicable records in file #801.41.  
  DATE ACTIVATED: DEC 02, 2015

NUMBER: 6260                            IA #: 6260
  FILE NUMBER: 801.41                   GLOBAL ROOT: PXRMD(801.41,D0,0
  DATE CREATED: NOV 05, 2015            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: File
  NAME: 801.41 READ                     ID: PXRMD(801.41,D0,0
GLOBAL REFERENCE: PXRMD(801.41,D0,0
FIELD NUMBER: 3                         FIELD NAME: DISABLE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: TYPE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 112                       FIELD NAME: PATIENT SPECIFIC
  LOCATION: 0;112                       ACCESS: Read w/Fileman
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (Kiosks) needs to do a FileMan read
 of fields 3 (DISABLE), 4 (TYPE) NAME), and 112 (PATIENT SPECIFIC) from file # 
 801.41.  These fields are needed to provide data needed by VetLink to present
 behavioral clinical reminders to clinic staff and patients.  

NUMBER: 6261                            IA #: 6261
  DATE CREATED: NOV 05, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORQPTQ11
  NAME: DEFSORT~ORQPTQ11                ID: ORQPTQ11
 GENERAL DESCRIPTION:   The HMP package is using the DEFSORT^ORQPTQ11 API to
 the default patient list for the user that is logged on.  
  
 **NOTE: HMP is the only package that will be granted this level of access. ** 
  
  
 **************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library for list of retired HMP ICRs.  
 **************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: ORQPTQ11
KEYWORDS: DEFSORT
COMPONENT/ENTRY POINT: DEFSORT
 COMPONENT DESCRIPTION:   This component returns the user's default patient
 list.  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The logged on users DUZ.  
VARIABLES: HMPSORT                      TYPE: Output
 VARIABLES DESCRIPTION:   Name of the array used to return the results.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP needs to pull the user's default patient list to
 populate the user's patient selection list box.  
  DATE ACTIVATED: MAR 10, 2016

NUMBER: 6262                            IA #: 6262
  DATE CREATED: NOV 05, 2015            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: WVRPCOR CONSAVE
  REMOTE PROCEDURE: WVRPCOR CONSAVE
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call the WVRPCOR CONSAVE remote procedure.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CAN SAVE COVER SHEET DATA
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 17, 2017

NUMBER: 6263                            IA #: 6263
  DATE CREATED: NOV 06, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORUTL
  NAME: CPRS UTILITIES                  ID: ORUTL
 GENERAL DESCRIPTION:   This integration control registration allows
 subscribing packages to access internal utility functions within the Order
 Entry/Results Reporting package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: UTILITY
KEYWORDS: LINE WRAP
COMPONENT/ENTRY POINT: WRAP(LINE,OUTPUT,INDENT,TRIM,COLNUM,LINENUM,IOM,ZERO)
 COMPONENT DESCRIPTION:   Wraps a line of text so that it is a certain number
 of characters wide. If the line contains a colon, subsequent lines are
 indented to that character's column position plus two. If the line does not
 contain a colon but starts with one or more spaces, subsequent lines are 
 indented to the first non-space character's column position. Wrapped lines are
 returned in an array.  
  
 This utility is designed to be called multiple times, once for each line of
 text, wrapping those lines of text into a single array. This is useful in
 displaying formatted output to the user, in formatting reports or formatting
 the body of email messages.  
VARIABLES: LINE                         TYPE: Input
 VARIABLES DESCRIPTION:   The line of text to wrap.  
VARIABLES: OUTPUT                       TYPE: Both
 VARIABLES DESCRIPTION:   Name of the array in which to return the wrapped text
 in. Each subscript stores one line of text and is numeric. The first subscript
 is one and subsequent subscripts are incremented by one.  
  
 The array variable itself may contain the total number of lines in the array.
 The input variable LINENUM controls where the total number of lines of text is
 returned.  
  
 Example: 
   OUTPUT=2 
   OUTPUT(1)="First line of text." 
   OUTPUT(2)="Second line of text." 
VARIABLES: INDENT                       TYPE: Input
 VARIABLES DESCRIPTION:   Boolean flag denoting whether to indent lines two
 through the last (1) or not (0).  
VARIABLES: TRIM                         TYPE: Input
 VARIABLES DESCRIPTION:   Boolean flag denoting whether to remove trailing
 spaces from every returned line (1) or not (0).  
VARIABLES: COLNUM                       TYPE: Input
 VARIABLES DESCRIPTION:   The column number that wrapped lines should be
 indented to. If not specified, the utility will calculate this value based on
 the position of the colon or if there is no colon, the position of the first
 non-space character.  
VARIABLES: LINENUM                      TYPE: Input
 VARIABLES DESCRIPTION:   Reference to a variable in which the number of lines
 in the OUTPUT array is stored. If no reference is specified ($D(LINENUM)=0),
 the number of lines in the OUTPUT array is retuned in the OUTPUT array: 
 OUTPUT=number_of_lines 
VARIABLES: IOM                          TYPE: Input
 VARIABLES DESCRIPTION:   The width (number of characters) in each line. If
 this is not specified, the utility will use either the value in the IOM system
 variable or if that is not defined, 80.  
VARIABLES: ZERO                         TYPE: Input
 VARIABLES DESCRIPTION:   Boolean flag denoting whether to return text in a
 zero subscript below the line number subscript (1) or not (0). The default
 value is not (0).  
  
 Example for True: 
   OUTPUT(1,0)="Fist line of text." 
  
 Example for False: 
   OUTPUT(1)="First line of text." 
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
  DATE ACTIVATED: NOV 14, 2017

NUMBER: 6264                            IA #: 6264
  FILE NUMBER: 9000010                  GLOBAL ROOT: AUPNVSIT
  DATE CREATED: NOV 09, 2015
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: File
  NAME: VPS WRITE TO 9000010            ID: AUPNVSIT
GLOBAL REFERENCE: AUPNVSIT(D0,0
FIELD NUMBER: .03                       FIELD NAME: TYPE
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: .05                       FIELD NAME: PATIENT NAME
  LOCATION: 0;5                         ACCESS: Write w/Fileman
FIELD NUMBER: .07                       FIELD NAME: SERVICE CATEGORY
  LOCATION: 0;7                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   This IA provides for the Fileman Write of the TYPE
 (.03), PATIENT NAME (.05) and SERVICE CATEGORY (.07) fields in the VISIT FILE
 #9000010.  
  STATUS: Withdrawn
KEYWORDS: VPS
KEYWORDS: VISIT FILE
KEYWORDS: AUPNVSIT
KEYWORDS: PCE
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
 SUBSCRIBING DETAILS:   VA Point of Service (Kiosks) has a need to write to the
 TYPE (.03), PATIENT NAME (.05) and SERVICE CATEGORY (.07) fields in the VISIT
 FILE #9000010 to resolve identified behavioral clinical reminders.  

NUMBER: 6265                            IA #: 6265
  DATE CREATED: NOV 16, 2015            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LEXU
  NAME: Lexicon Expression Extracts     ID: LEXU
 GENERAL DESCRIPTION:   Effective upon release of patch LEX*2.0*103.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EXP
KEYWORDS: EXPS
KEYWORDS: LEXU
KEYWORDS: SOS
KEYWORDS: PREF
KEYWORDS: SUBSETS
COMPONENT/ENTRY POINT: $$EXP(IEN)
 COMPONENT DESCRIPTION:   This API returns Display Text (.01 field) of the
 EXPRESSIONS file #757.01.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number to the EXPRESSIONS 
 file #757.01.  
  
VARIABLES: $$EXP                        TYPE: Output
 VARIABLES DESCRIPTION:   This is the Display Text taken from the .01 field of 
 the EXPRESSIONS file 757.01.  
  
COMPONENT/ENTRY POINT: EXPS(IEN,CDT,.ARY)
 COMPONENT DESCRIPTION:   This API returns the display text of an expression
 from the EXPRESSIONS ifle #757.01 and active codes associated with the
 expression.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number to the EXPRESSIONS 
 file #757.01.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the date that will be used to determine
 whether the code is active or inactive. If not passed, TODAY's date will be
 used.  
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   Local array passed by reference with the following
 output format: 
  
    ARY(IEN)=EXP 
    ARY(IEN,SRC)=COD ^ NOM ^ VAR 
  
 Where: 
  
    IEN   Internal Entry number in the EXPRESSION 
          file 757.01 
  
    EXP   The Display Text from the EXPRESSION 
          file 757.01 
  
    SRC   A Coding System (pointer to CODING 
          SYSTEMS file 757.03) 
  
    COD   A code taken from the CODES file 757.02 
  
    NOM   Coding Nomentclature from the CODING 
          SYSTEMS file #757.03, examples: 
  
            ICD-10-CM 
            ICD-10-PCS 
            SNOMED CT 
  
    VAR  This is a varable pointer to a national 
         coding file if one exist (optional) 
  
COMPONENT/ENTRY POINT: $$PREF(COD,SAB,CDT) 
 COMPONENT DESCRIPTION:   This API returns the preferred term for a code and
 coding system based on date.  
  
VARIABLES: COD                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a code taken from the CODES file 757.02 
  
VARIABLES: SAB                          TYPE: Input
 VARIABLES DESCRIPTION:   Source Abbreviation from the .01 field of the CODING 
 SYSTEMS file #757.03.  
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the date that will be used to determine
 whether the code is active or inactive. If not passed, TODAY's date will be
 used.  
  
VARIABLES: $$PREF                       TYPE: Output
 VARIABLES DESCRIPTION:   This is a two piece "^" delimited string: 
  
   IEN ^ EXP 
  
 Where 
  
   IEN   This is the Internal Entry Number for the 
         preferred term in file 757.01.  
  
   EXP   This is the display text of the preferred 
         term in file 757.01 
  
 or 
  
   -1    if no preferred term is found for the code 
  
COMPONENT/ENTRY POINT: $$IENS(CODE,.ARY,CDT)
 COMPONENT DESCRIPTION:   This API returns IENs from the Lexicon and National 
 files for a code.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a code from one of the coding systems in the
 Lexicon.  
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is an input/output array passed by reference.  
 It will be killed and rebuilt as follows: 
  
 Output Local Array ARY 
  
   ARY(0)   3 Piece "^" delimited string 
     
      1  Number of Entries in the Lexicon for Code 
      2  Code 
      3  Date used to extract data 
           
   ARY(#,757)   2 Piece "^" delimited string 
           
      1  IEN to the MAJOR CONCEPT MAP file #757 
      2  IEN to the Major Concept Expression in File #757.01 
  
   ARY(#,757.001)   3 Piece "^" delimited string 
           
      1  IEN to the CONCEPT USAGE file #757.001 
      2  Originating Value 
      3  Frequency 
  
   ARY(#,757.01)   8 Piece "^" delimited string 
           
      1  IEN to the EXPRESSION file #757.01 
      2  Expression Type 
      3  Expression Form 
      4  Expression Deactivation Flag 
      5  External Expression Type 
      6  External Expression Form 
      7  External Deactivation Flag 
      8  Expression 
           
   ARY(#,757.01,7,CD)   5 Piece "^" delimited string 
           
      Where CD is a Designation Code 
         
      1  IEN of the DESIGNATION CODE sub-file #757.118 
      2  Pointer to the CODING SYSTEM file #757.03 
      3  Pointer to the SNOMED CT HIERARCHY file #757.018 
      4  External nomenclature for CODING SYSTEM 
      5  External name of SNOMED CT Hierarchy 
        
   ARY(#,757.02)   5 Piece "^" delimited string 
           
      1  IEN to the CODE file #757.02 
      2  Code from CODE file #757.02 
      3  Initial Activation Date in the Lexicon 
      4  Status in the Lexicon 
      5  Status Effective Date in the Lexicon 
       
   ARY(#,757.02,4,EFF)   2 Piece "^" delimited string 
           
      Where EFF is the effective date for a Status 
           
      1  IEN of the ACTIVATION STATUS subfile #757.28 
      2  STATUS (1=Active, 0=Inactive) 
         
   ARY(#,757.03)   3 Piece "^" delimited string 
           
      1  IEN to the CODING SYSTEM file #757.03 
      2  Source Abbreviation from file #757.03 
      3  Source Nomenclature from file #757.03 
  
   ARY(#,757.1,#)   6 Piece "^" delimited string (multiple) 
           
      1  IEN to the SEMANTIC MAP file #757.1 
      2  IEN to the MAJOR CONCEPT MAP file #757 
      3  IEN to the SEMANTIC CLASS file #757.11 
      4  IEN to the SEMANTIC TYPE file #757.12 
      5  Semantic Class (external) 
      6  Semantic Type (external) 
  
   ARY(#,"VA",SR)   6 Piece "^" delimited string (multiple) 
           
      Where SR is a pointer to the CODING SYSTEM file 757.03 
           
      1  Variable Pointer to a VA National File 80, 80.1 or 81 
      2  Code from VA file 
      3  Coding System Nomenclature 
      4  Initial Activation Date in the VA file 
      5  Status in the VA file 
      6  Status Effective Date in the VA file 
         
 Example 
           
   ARY(0)="2^250.01^3150101" 
   ARY(1,757)="7006^33586" 
   ARY(1,757.001)="7006^4^4" 
   ARY(1,757.01)="33586^1^1^^Major Concept^Major Concept^^ 
                 Diabetes Mellitus Type I" 
   ARY(1,757.02)="316386^250.01^2781001^0^3041001" 
   ARY(1,757.02,4,2781001)="1^1" 
   ARY(1,757.02,4,3041001)="2^0" 
   ARY(1,757.03)="1^ICD^ICD-9-CM" 
   ARY(1,757.1,1)="10167^7006^6^47^Diseases/Pathologic 
                  Processes^Disease or Syndrome" 
   ARY(1,"VA",1)="851;ICD9(^250.01^ICD-9-CM^2781001^1^2781001" 
   ARY(2,757)="182207^331780" 
   ARY(2,757.001)="182207^4^4" 
   ARY(2,757.01)="331780^1^1^^Major Concept^Major Concept^^ 
                 Diabetes Mellitus without mention of 
                 Complication, type i [Juvenile type], not 
                 stated as Uncontrolled" 
   ARY(2,757.02)="327553^250.01^3041001^1^3041001" 
   ARY(2,757.02,4,3041001)="1^1" 
   ARY(2,757.02,4,3151001)="2^0" 
   ARY(2,757.03)="1^ICD^ICD-9-CM" 
   ARY(2,757.1,1)="259374^182207^6^47^Diseases/Pathologic 
                  Processes^Disease or Syndrome" 
   ARY(2,"VA",1)="851;ICD9(^250.01^ICD-9-CM^2781001^1^2781001" 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This the Versioning Date (default TODAY) used to 
 extract data.  
  
VARIABLES: $$IENS                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of entries found in the Lexicon
 for Code.  
  
COMPONENT/ENTRY POINT: $$SOS(IEN,.ARY,SYN)
 COMPONENT DESCRIPTION:   This API returns a local array (passed by reference)
 of codes for an Expression. If the synonym flag is set to 1 then it will
 return codes for and expression and its synonyms.  These codes may be active
 or inactive.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number to the EXPRESSIONS
 file #757.01.  
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   Local array passed by reference with the following 
 output format: 
  
 ARY(IEN)    IEN is from file #757.01 (same as X) ARY(IEN,0)  Number of Codes
 Found ARY(IEN,#)  # is a sequence number 
     
   Equals an 13 Piece "^" delimited string 
               
     1   Code 
     2   Coding System Nomenclature 
     3   Coding System Source Abbreviation 
     4   Code Status 
     5   Code Active Date 
     6   Code Inactive Date 
     7   Expression Status 
     8   Expression Active Date 
     9   Expression Inactive Date 
    10   Expression Variable Pointer 
    11   Code Variable Pointer 
    12   Coding System Variable Pointer 
    13   National File Variable Pointer (if it exist) 
     
 The array has two indexes: 
  
 ARY(LEXEIEN,"B",(CODE_" "),#)=Code_"^"_Nomenclature 
 ARY(LEXEIEN,"C",SOURCE,#)=Code_"^"_Nomenclature 
  
VARIABLES: $$SOS                        TYPE: Output
 VARIABLES DESCRIPTION:   $$SOS returns the number of codes found for an 
 expression, both active and inactive.  
  
VARIABLES: SYN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a boolean flag to indicate if codes linked to 
 synonyms to the expression are to be returned.  
  
   0  Don't return Synonym codes (default) 
   1  Return Synonym codes 
  
COMPONENT/ENTRY POINT: $$EXM(TEXT,.ARY,DF,MC)
 COMPONENT DESCRIPTION:   This API returns IENs in a local array of the 
 Expressions in the EXPRESSIONS file #757.01 that match the input text exactly. 
  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the Text to Search for (required) 
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is a local array passed by reference and will 
 contain the IENs of the expressions that match the input text exactly.  
  
 LEX(0)   2 piece "^" dilimited string 
  
          1  Total Exact Matches found 
          2  Text Searched for 
             
 LEX(#)   5 piece "^" dilimited string 
  
          1  IEN of Exact Match Expression 
          2  IEN of Major Concept for Expression 
          3  Type of Exact Match Expression (internal) 
          4  Deactivation Flag (internal) 
          5  Type of Exact Match Expression (external) 
  
VARIABLES: DF                           TYPE: Input
 VARIABLES DESCRIPTION:   This is a Boolean Flag indicating whether to include 
 or exclude Deactivated Terms (optional) 
  
     1  Include deactivated terms 
     0  Do not include deactivated terms (default) 
  
VARIABLES: MC                           TYPE: Input
 VARIABLES DESCRIPTION:   This is a Boolean Flag to include Major Concepts only
 (optional) 
  
     1  Include Major Concepts ONLY in the array 
     0  Include all expressions found in the array; 
          Major Concepts, Synonyms, Lexical 
          Variants and Fully Specified Names 
          (default) 
  
COMPONENT/ENTRY POINT: PRF(LEX,LEXVDT,LEXSAB)
 COMPONENT DESCRIPTION:   This API returns a code for a preferred term of a 
 coding system.  
  
 It is Similar to $$ONE^LEXU except the expression identified by the input
 parameter LEX must be a preferred term of the coding system identified by the
 input parameter LEXSAB and the code must be active on the date identified by
 input parameter LEXVDT to return a code 
  
 It is intended to be used as a filter for screening searches.  Example screen
 using ICD-10-CM: 
    
      I $L($$PRF^LEXU(+Y,+($G(LEXVDT))),"10D") 
  or 
      I $L($$PRF^LEXU(+Y,+($G(LEXVDT))),30) 
   
 Using the above screen, terms that are not the preferred term in ICD-10-CM
 (i.e., synonyms, lexical variants or orphan terms) will not be displayed in 
 the selection list during lookup. Only the ICD-10-CM Code Set will be
 selectable.  
  
VARIABLES: LEX                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the EXPRESSION file 757.01 
  
VARIABLES: LEXVDT                       TYPE: Input
 VARIABLES DESCRIPTION:   Date to use for screening by codes, if not provided
 TODAY will be used.  
  
VARIABLES: LEXSAB                       TYPE: Input
 VARIABLES DESCRIPTION:   Source Abbreviation or a pointer to the CODES file
 #757.03 
  
VARIABLES: $$PRF                        TYPE: Output
 VARIABLES DESCRIPTION:   Null    If the IEN is NOT the preferred term of 
         an active code of the specified coding 
         system 
  
 CODE    If the IEN is the preferred term of an 
         active code of the specified coding 
         system 
  
COMPONENT/ENTRY POINT: $$SUBSETS(CODE,SRC,.ARY)
 COMPONENT DESCRIPTION:   This API returns the names of the subsets for which a
 code is assigned. 
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a valid classification code from one of the 
 coding systems in the Lexicon (see the CODING SYSTEMS file #757.03) 
  
VARIABLES: ARY                          TYPE: Both
 VARIABLES DESCRIPTION:   This is an optional local array passed by reference
 in the following format: 
  
   LEX(<sub>) = 4 Piece "^" delimited string 
      
      1  Subset Name 
      2  Subset Definition IEN file 757.2 
      3  Subset IEN file 757.21 
      4  Expression IEN file 757.01 
      
 Where <sub> is a three character identifier of a subset.  
  
 Example of the LEX array: 
  
   $$SUBSETS^LEXU(205365003,56,.ARY) 
  
   ARY("CLF")="Clinical Findings^7000039^70071537^7301845" 
   ARY("DIS")="Disorder^7000002^7150923^7301845" 
   ARY("PLS")="PL Standard^7000038^70175664^7301845" 
   ARY("SCT")="SNOMED CT^7000037^7457760^7301845" 
  
VARIABLES: SRC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is coding system for which the code belongs.  It
 can either be the Source Abbreviation (SAB) found in the .01 field of the
 CODING SYSTEMS file #757.03 or a pointer to the CODING SYSTEMS file #757.03 
  
VARIABLES: $$SUBSETS                    TYPE: Output
 VARIABLES DESCRIPTION:   This is a 2 or more (variable) Piece "^" delimited 
 string: 
  
   1  Number of Subsets found 
   2  Subset Identifier #1 
   3  Subset Identifier #2 
   4  Subset Identifier #n 
  
   Example: 
  
     $$SUBSETS^LEXU(205365003,56) 
  
     "4^CLF^DIS^PLS^SCT^" 
  
     4 Subsets found including CLF, DIS, PLS and SCT 
  
 or if not found or error: 
  
   -1 ^ Error Message 
  
COMPONENT/ENTRY POINT: CODE(CODE,SRC,CDT,.ARY,OUT)
 COMPONENT DESCRIPTION:   This API returns information about a code in a local 
 array passed by reference.  
  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a Classification Code from the CODES file
 #757.02 (Required) 
  
VARIABLES: SRC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is either a Source Abbreviation (.01) or pointer
 to file 757.03 (Required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a date in FileMan format used to determine 
 status, default TODAY 
  
VARIABLES: OUT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Output flag (Optional) 
  
   0  Do not Display array, leave local array (default) 
   1  Display array , kill local array 
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   Local Array, passed by reference 
  
 Code 
  
   ARY("CO")="Code" 
   ARY("CO",n)=<code> 
   ARY("CO","B",<code>,n)="" 
   ARY("CO",n,"I")= 6 piece "^" delimited string 
  
     1  Status 
     2  Effective Date 
     3  Initial Activation Date 
     4  Pointer to CODES file #757.02 
     5  Coding System Nomenclature 
     6  Coding System 
  
   ARY("CO",n,"VA")= 4 piece "^" delimited string 
  
     1  Status 
     2  Effective Date 
     3  VA File Number 
     4  Variable Pointer to VA File 
  
 Diagnostic Categories (ICD-10-CM only) 
  
   ARY("DC")="Diagnostic Categories" 
   ARY("DC",1)=<category> 
   ARY("DC",1,"I")= 4 piece "^" delimited string 
  
     1  Status 
     2  Effective Date 
     3  Category Name 
     4  Pointer to CHARACTER POSITIONS file #757.033 
  
 Procedure Characters Positions (ICD-10-PCS only) 
  
   Where n is a character position number 1-7 
  
   ARY("CP")="Procedure Characters" 
   ARY("CP","I")=<code> 
   ARY("CP",n)=<character position 1-n> 
   ARY("CP",n,"I")= 4 piece "^" delimited string 
  
     1  Status 
     2  Effective Date 
     3  Name 
     4  Pointer to CHARACTER POSITIONS file #757.033 
  
 Terms 
  
   Subscript SUB can be: 
  
     PF  Preferred Term 
     FS  Fully Specified Term 
     MC  Major Concept 
     SY  Synonyms 
     LV  Lexical Variants 
     OR  Orphan Text 
  
   ARY(SUB)=type 
   ARY(SUB,n)=<expression> 
   ARY(SUB,n,"I")= 4 piece "^" delimited string 
  
     1  Status 
     2  Type 
     3  Current/Retired 
     4  Pointer to EXPRESSIONS file #757.01 
  
   ARY(SUB,n,"ID")="Designation ID" 
   ARY(SUB,n,"ID",n)<designation ID> 
   ARY(SUB,n,"ID",n,"I")= 4 piece "^" delimited string 
  
     1  Status 
     2  Coding System 
     3  Hierarchy 
     4  Pointer to DESIGNATION CODE subfile #757.118 
  
   ARY(SUB,n,"SK")="Supplemental Keywords" 
   ARY(SUB,n,"SK",n)=<keyword> 
   ARY(SUB,n,"SK",n,"I")= 4 piece "^" delimited string 
  
     1  Status 
     2  Not used 
     3  Not used 
     4  Pointer to SUPPLEMENTAL subfile #757.18 
  
 Mappings 
  
   ARY("MP")="Mapping" 
   ARY("MP",n)=<map to target code> 
   ARY("MP",n,"I")= 6 piece "^" delimited string 
  
     1  Status 
     2  Effective 
     3  Coding System 
     4  Pointer to MAPPINGS file #757.33 
     5  Match (full/partial) 
     6  Source Code 
     7  Source Coding System 
  
 Subsets 
  
   ARY("SB")="Subsets" 
   ARY("SB",n)=<subset> 
   ARY("SB",n,"I")= 5 piece "^" delimited string 
  
     1  Status 
     2  Pointer to SUBSET file #757.21 
     3  Pointer to EXPRESSION file #757.01 
     4  Pointer to SUBSET DEFINITION file #757.2 
     5  Subset ID 
  
 Source 
  
   ARY("SR")="Source" 
   ARY("SR",n)=<source abbreviation> 
   ARY("SR",n,"I")= 4 piece "^" delimited string 
   ARY("SR","B",<source>,n)="" 
  
     1  Source Abbreviation 
     2  Source Nomenclature 
     3  Source Title 
     4  Pointer to CODING SYSTEMS file #757.03 
  
COMPONENT/ENTRY POINT: TERM(IEN,CDT,.ARY,OUT)
 COMPONENT DESCRIPTION:   This API will return information about a term in a
 local array passed by reference.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an internal entry number of an Expression in
 the EXPRESSIONS file #757.01 (required) 
  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a date in FileMan format used to determine 
 status, default TODAY 
  
VARIABLES: OUT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Output flag (Optional) 
  
   0  Do not Display array, leave local array (default) 
   1  Display array , kill local array 
  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   Local Array, passed by reference 
  
 Code 
  
   ARY("CO")="Code" 
   ARY("CO",n)=<code> 
   ARY("CO","B",<code>,n)="" 
   ARY("CO",n,"I")= 6 piece "^" delimited string 
  
     1  Status 
     2  Effective Date 
     3  Initial Activation Date 
     4  Pointer to CODES file #757.02 
     5  Coding System Nomenclature 
     6  Coding System 
  
   ARY("CO",n,"VA")= 4 piece "^" delimited string 
  
     1  Status 
     2  Effective Date 
     3  VA File Number 
     4  Variable Pointer to VA File 
  
 Diagnostic Categories (ICD-10-CM only) 
  
   ARY("DC")="Diagnostic Categories" 
   ARY("DC",1)=<category> 
   ARY("DC",1,"I")= 4 piece "^" delimited string 
  
     1  Status 
     2  Effective Date 
     3  Category Name 
     4  Pointer to CHARACTER POSITIONS file #757.033 
  
 Procedure Characters Positions (ICD-10-PCS only) 
  
   Where n is a character position number 1-7 
  
   ARY("CP")="Procedure Characters" 
   ARY("CP","I")=<code> 
   ARY("CP",n)=<character position 1-n> 
   ARY("CP",n,"I")= 4 piece "^" delimited string 
  
     1  Status 
     2  Effective Date 
     3  Name 
     4  Pointer to CHARACTER POSITIONS file #757.033 
  
 Terms 
  
   Subscript SUB can be: 
  
     MC  Major Concept 
     FS  Fully Specified Term 
     SY  Synonyms 
     LV  Lexical Variants 
     OR  Orphan Text 
  
   ARY(SUB)=type 
   ARY(SUB,n)=<expression> 
   ARY(SUB,n,"I")= 4 piece "^" delimited string 
  
     1  Status 
     2  Type 
     3  Current/Retired 
     4  Pointer to EXPRESSIONS file #757.01 
  
   ARY(SUB,n,"ID")="Designation ID" 
   ARY(SUB,n,"ID",n)<designation ID> 
   ARY(SUB,n,"ID",n,"I")= 4 piece "^" delimited string 
  
     1  Status 
     2  Coding System 
     3  Hierarchy 
     4  Pointer to DESIGNATION CODE subfile #757.118 
  
   ARY(SUB,n,"SK")="Supplemental Keywords" 
   ARY(SUB,n,"SK",n)=<keyword> 
   ARY(SUB,n,"SK",n,"I")= 4 piece "^" delimited string 
  
     1  Status 
     2  Not used 
     3  Not used 
     4  Pointer to SUPPLEMENTAL subfile #757.18 
  
 Mappings 
  
   ARY("MP")="Mapping" 
   ARY("MP",n)=<map to target code> 
   ARY("MP",n,"I")= 6 piece "^" delimited string 
  
     1  Status 
     2  Effective 
     3  Coding System 
     4  Pointer to MAPPINGS file #757.33 
     5  Match (full/partial) 
     6  Source Code 
     7  Source Coding System 
  
 Subsets 
  
   ARY("SB")="Subsets" 
   ARY("SB",n)=<subset> 
   ARY("SB",n,"I")= 5 piece "^" delimited string 
  
     1  Status 
     2  Pointer to SUBSET file #757.21 
     3  Pointer to EXPRESSION file #757.01 
     4  Pointer to SUBSET DEFINITION file #757.2 
     5  Subset ID 
  
 Source 
  
  ARY("SR")="Source" 
  ARY("SR",n)=<source abbreviation> 
  ARY("SR","B",<source>,n)="" 
  ARY("SR",n,"I")= 4 piece "^" delimited string 
  
     1  Source Abbreviation 
     2  Source Nomenclature 
     3  Source Title 
     4  Pointer to CODING SYSTEMS file #757.03 
  
  DATE ACTIVATED: JAN 15, 2015

NUMBER: 6266                            IA #: 6266
  DATE CREATED: NOV 17, 2015            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  ROUTINE: LEXXMC                       NAME: Convert to Mixed Case
  ID: LEXXMC
 GENERAL DESCRIPTION:   Effective upon release of patch LEX*2.0*103.  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: MIX
KEYWORDS: LEXXMC
KEYWORDS: ICD-10
COMPONENT/ENTRY POINT: $$MIX(TEXT)
 COMPONENT DESCRIPTION:   This API converts text from any form to a modified
 mix text format.  This API replaces an older API $$MIX^LEXXM (ICR 5781) which
 converted text to mix text using hard coded rules found in a series of Lexicon
 namespace routines. This API still uses rules to convert text to mixed case
 but the rules are stored in the TOKENS file #757.07 which is much easier to
 maintain.  
  
 Examples: 
  
     Input:    arthropathy in behcet's syndrome 
               involving other specified sites 
  
     Output:   Arthropathy in Behcet's Syndrome 
               involving other specified sites 
  
     Input:    24 hour esophageal ph study 
  
     Output:   24 hour Esophageal pH Study 
  
  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a text string to be converted to mix text.  
  
VARIABLES: $$MIX                        TYPE: Output
 VARIABLES DESCRIPTION:   This is a string of text in mixed case.  
  

NUMBER: 6267                            IA #: 6267
  DATE CREATED: NOV 17, 2015            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  ROUTINE: LEXA                         NAME: Lexicon Silent Lookup
  ID: LEXA
 GENERAL DESCRIPTION:   Effective upon release of patch LEX*2.0*103.  Expands
 upon LOOK^LEXA ICR 2950.  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: LEXA
KEYWORDS: LOOK
KEYWORDS: ICD-10
COMPONENT/ENTRY POINT: LOOK(X,AP,LL,SUB,CDT,SRC,CAT,FMT)
 COMPONENT 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.  
  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   Equivalent to Fileman's variable X and contains the
 text to search for. 
  
VARIABLES: AP                           TYPE: Input
 VARIABLES DESCRIPTION:   This is the aplication or vocabulary identification 
 and may be in the form of a name or a namespace a subset definition in the
 Subset Definition file (#757.2).  
                             
 Included in this application/vocabulary definition are a number of defaults
 which assist in searching the Lexicon.  Defaults may include:  
  
   Global root, index, filter, display, vocabulary, 
   user default flag, overwrite user default flag, 
   and the unresolved narrative flag.  
  
 Values for this parameter can be found in either the "AN" or "AA"
 cross-reference of the Subset Definition file (#757.2).  
  
 Examples: 
  
   Application ("AN" Index)      Namspace 
   -----------                   --------
   Lexicon                         LEX 
   Problem List                    GMPL 
   ICD Diagnosis                   ICD 
   CPT Procedures                  CPT 
   Mental Health                   DSM 
   ICD, CPT, and DSM Terminology   VAC 
   Radiology                       RA 
     
   Vocabularies ("AA" Index)     Namspace 
   ------------                  --------
   Main Word Index                 WRD 
   Clinical Findings Index         CLF 
  
VARIABLES: LL                           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: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   This parameter is a mnemonic representing the subset 
 to use during the search.  These subsets are defined in the Subset Definition
 file (#757.2) and can be found in either the AA or AB cross-reference.  The
 subset may have default values set that are different from the controlling
 application or vocabulary.  
                             
 Examples: 
  
   Vocabularies ("AA" Index)     Namspace 
   ------------                  --------
   Main Word Index                 WRD 
   Clinical Findings Index         CLF 
   SNOMED CT                       SCT 
  
   Subsets ("AB" Index)          Namspace 
   -------                       --------
   ICD-10-CM                       10D 
   CPT-4/HCPCS                     CHP 
   Encounter Forms #2              EF2 
   DSM-IV                          DSM 
   Problem List #1                 PL1 
  
VARIABLES: CDT                          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.  
  
VARIABLES: SRC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is a source of a vocabulary taken from the 
 Source file #757.14.  When present, only terms attributed to that source will
 be returned.  
  
 Examples: 
  
 Breast Imaging Reporting and Data System (BI-RADS) Atlas (ACR) Mammography
 Quality Standards Act of 1992 (MQSA) Automated Service Connected Designation
 (ASCD) 
  
VARIABLES: CAT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the category of a source of a vocabulary
 taken from the Category file 757.13.  When present, only terms attributed to
 that category will be returned.  
  
 Examples: 
  
 Breast Imaging Reporting and Data Systems MRI Ultrasound Mammography MRI
 Assessment Categories Ultrasound Assessment Categories Mammography Assessment
 Categories 
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the preferred output format.  
  
    0  Default, Display Text 
  
         LEX("LIST",1)="5019187^Mouth Breathing 
                        (ICD-10-CM R06.5)" 
  
    1  Parsed Format 
  
         LEX("LIST",1)="5019187^Mouth Breathing" 
         LEX("LIST",1,30)="R06.5^ICD-10-CM^ 
                          521361;ICD9(" 
  
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP temporary global arrays: 
  
   ^TMP("LEXFND",$J,<freq>,<ien>) 
                             
   This global array contains all of the entries 
   found during the search.  The <freq> is a 
   negative number based on the frequency of use 
   for a given term.  <ien> is the internal entry 
   number in the Lexicon Expression file (757.01).  
                             
   ^TMP("LEXHIT",$J,<seq>) 
                             
   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.  
  

NUMBER: 6268                            IA #: 6268
  DATE CREATED: NOV 18, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORQPTQ6
  NAME: COMBPTS~ORQPTQ6                 ID: ORQPTQ6
 GENERAL DESCRIPTION:   
  
 The code returns a list of patients for clinic appointments based on input 
 parameters, the results are in ^TMP("OR",$J).  
  
 ** NOTE: Access to this file for direct reads will only be granted to the HMP
 project. ** 
  
 **************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library for list of retired HMP ICRs.  
 **************************************************************
  STATUS: Retired                       EXPIRATION DATE: OCT 27, 2017
KEYWORDS: ORQPTQ6
KEYWORDS: COMBPTS
COMPONENT/ENTRY POINT: COMBPTS
 COMPONENT DESCRIPTION:   
  
  entry point with input parameters 
  results are returned in global array - ^TMP("OR",$J) 
  
    ^TMP("OR",$J,"PATIENTS") - output 
      array created for GUI (ORQLM equals 1) 
        ^TMP("OR",$J,"PATIENTS",counter,0) = 
       patient IEN (1)_U_patient name (2)_U_Source name (3) ...  
       _U_Appt. or Room/Bed (4) ...  
       _U_Patient ID (1U4N) (5)_U_Patient DOB (6)_U_IEN of source (7) ...  
       _U_Hold appt. date/time(8)_U_Inpt. or Outpt. (or C/NS) status (9) 
VARIABLES: ORQLM                        TYPE: Input
 VARIABLES DESCRIPTION:   boolean value, one or zero, indicating call from
 ListMan (1) or from a GUI (0) 
VARIABLES: ORQCPTR                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN (pointer) to ^OR(100.24) the OE/RR PT SEL COMBO
 file 
VARIABLES: ORBDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   Beginning date for clinic appointments 
VARIABLES: OREDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   Ending date for clinic appointments 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: MAR 14, 2016

NUMBER: 6269                            IA #: 6269
  DATE CREATED: NOV 18, 2015
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWDRA32
  NAME: IMTYPSEL~ORWDRA32               ID: ORWDRA32
 GENERAL DESCRIPTION:   The code returns data from Radiology, a list of active
 imaging types from the IMAGING TYPE file (#79.2). The list returned is
 passed-by-reference to the calling routine.  
  
 ** NOTE: Access to this file for direct reads will only be granted to the HMP
 project. ** 
  
  
 **************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library for list of retired HMP ICRs.  
 **************************************************************
  STATUS: Retired                       EXPIRATION DATE: OCT 27, 2017
KEYWORDS: IMTYPSEL
KEYWORDS: ORWDRA32
KEYWORDS: IMAGING TYPE
KEYWORDS: 79.2
COMPONENT/ENTRY POINT: IMTYPSEL
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Y - output 
  results are returned in Y 
  passed-by-reference, list is returned in this format: 
    Y(counter) = IEN ^ name ^ mnemonic ^ disp. group 
  
     these 3 values are from file #79.2 
        IEN = from file #79.2 
        name = (#.01) TYPE OF IMAGING 
        mnemonic = (#3) ABBREVIATION 
  
     this value comes from the "B" cross-reference of the DISPLAY GROUP file
 (#100.98) 
        disp. group = IEN in file #100.98 
VARIABLES: DUMMY                        TYPE: Input
 VARIABLES DESCRIPTION:   
  DUMMY - 
  place holder only, not used 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: MAR 14, 2016

NUMBER: 6270                            IA #: 6270
  DATE CREATED: NOV 18, 2015            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PXRMLCR                      NAME: RUN~PXRMLCR
  ID: PXRMLCR
 GENERAL DESCRIPTION:   This is used to build a Patient List for Clinical
 Reminders.  
  
 It is called internally in Clinical Reminders by the PXRM PATIENT LIST CREATE
 protocol.  
  STATUS: Withdrawn
KEYWORDS: RUN PXRMCLR
KEYWORDS: PXRMCLR
COMPONENT/ENTRY POINT: RUN
VARIABLES: PXRMRULE                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN in REMINDER LIST RULE (#810.4) 
VARIABLES: PXRMLIST                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN in REMINDER PATIENT LIST file (#810.5) 
VARIABLES: PXRMNODE                     TYPE: Input
 VARIABLES DESCRIPTION:   storage NODE for ^TMP($J,storage_node) 
VARIABLES: BEG                          TYPE: Input
 VARIABLES DESCRIPTION:   beginning date in FileMan format 
VARIABLES: END                          TYPE: Input
 VARIABLES DESCRIPTION:   ending date in FileMan format 
VARIABLES: PXRMDPAT                     TYPE: Input
 VARIABLES DESCRIPTION:   value for INCLUDE DECEASED PATIENTS field (#1) in
 REMINDER PATIENT LIST file (#810.5) 
VARIABLES: PXRMTPAT                     TYPE: Input
 VARIABLES DESCRIPTION:   value for INCLUDE TEST PATIENTS field (#2) in
 REMINDER PATIENT LIST file (#810.5) 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Used to create a Clinical Reminders list for use in
 eHMP.  

NUMBER: 6271                            IA #: 6271
  DATE CREATED: NOV 19, 2015            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PSBUTL                       NAME: BCMA UTILITIES 
  ID: PSBUTL
 GENERAL DESCRIPTION:   Integration agreement to allow Inpatient Medications to
 call BCMA Utilities.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BCMA UTILITIES
COMPONENT/ENTRY POINT: MEDHIST
 COMPONENT DESCRIPTION:   Searches Medlog for active BCMA orders. Gets the
 information controlled by BCMA. MEDHIST^PSBUTL returns an array.  
VARIABLES: OI                           TYPE: Input
 VARIABLES DESCRIPTION:   Inpatient Meds Orderable Item Internal Entry Number.  
VARIABLES: MAX                          TYPE: Input
 VARIABLES DESCRIPTION:   Max days back to search.  
VARIABLES: LIST                         TYPE: Output
 VARIABLES DESCRIPTION:   Array of actions formatted as : 
 DATE^ACTION^ORDNO^LSTSITE^LOCATION^NURSINITL 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Integration agreement to allow Inpatient Medications to
 call BCMA Utilities.  
  DATE ACTIVATED: MAR 22, 2018

NUMBER: 6272                            IA #: 6272
  DATE CREATED: NOV 19, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWPT
  NAME: HMP USE OF ORWPT                ID: ORWPT
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) makes calls
 to the BYWARD^ORWPT API to retrieve a list of patients in a specific ward. HMP
 also calls the INPLOC^ORWPT API to retrieve a patient's current location.  
  
 **NOTE: HMP is the only package that will be granted this level of access. ** 
  
 **************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library for list of retired HMP ICRs.  
 **************************************************************
  STATUS: Retired                       EXPIRATION DATE: OCT 27, 2017
KEYWORDS: ORWPT
KEYWORDS: BYWARD
KEYWORDS: INPLOC
COMPONENT/ENTRY POINT: BYWARD
 COMPONENT DESCRIPTION:   This API returns a list of patients assigned to a
 specific ward.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the Ward in the Ward Location file (#44). 
 
VARIABLES: LIST                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns a list of patients assigned to the ward in
 the format of: DFN ^ Patient Name ^ Room-Bed 
COMPONENT/ENTRY POINT: INPLOC
 COMPONENT DESCRIPTION:   This API returns the patient's current location.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient's DFN.  
VARIABLES: ARRAY                        TYPE: Output
 VARIABLES DESCRIPTION:   An array in the format of: IEN for the Ward in the
 Ward Location file (#42) ^ Ward Name ^ Service 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: MAR 14, 2016

NUMBER: 6273                            IA #: 6273
  DATE CREATED: NOV 19, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWPT1
  NAME: PCDETAIL~ORWPT1                 ID: ORWPT1
 GENERAL DESCRIPTION:   Primary Care Detail information is returned as a list.
 The list is text that can be displayed to a user or added to a patient record. 
  
 **NOTE: Only the Enterprise Health Management Platform (HMP) will be permitted
 this access.  
  
 **************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library for list of retired HMP ICRs.  
 **************************************************************
  STATUS: Retired                       EXPIRATION DATE: OCT 27, 2017
KEYWORDS: PCDETAIL
KEYWORDS: ORWPT1
KEYWORDS: PRIMARY CARE DETAIL
COMPONENT/ENTRY POINT: PCDETAIL
VARIABLES: LST                          TYPE: Output
 VARIABLES DESCRIPTION:   passed-by-reference, the list is returned in this
 variable 
VARIABLES: PATIENT                      TYPE: Input
 VARIABLES DESCRIPTION:   the IEN from the PATIENT file (#2), also called DFN 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: APR 01, 2016

NUMBER: 6274                            IA #: 6274
  DATE CREATED: NOV 19, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORQQPX
  NAME: GETLIST~ORQQPX                  ID: ORQQPX
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform calls
 GETLIST^ORQQPX API in order to retrieve the information to build the cover
 sheet for the reminders list.  
  
 **NOTE: HMP is the only package that will be granted this level of access. ** 
  
 **************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library for list of retired HMP ICRs.  
 **************************************************************
  STATUS: Retired                       EXPIRATION DATE: OCT 27, 2017
COMPONENT/ENTRY POINT: GETLIST
 COMPONENT DESCRIPTION:   This API returns the information needed to build the
 cover sheet for the reminders list.  
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the location in the Hospital Location
 file (#44).  
VARIABLES: LIST                         TYPE: Output
 VARIABLES DESCRIPTION:   A list of clinical reminders.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: MAR 10, 2016

NUMBER: 6275                            IA #: 6275
  FILE NUMBER: 230                      GLOBAL ROOT: EDP(230,
  DATE CREATED: NOV 23, 2015            CUSTODIAL PACKAGE: EMERGENCY DEPARTMENT
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: EDP(230
  ID: EDP(230,
GLOBAL REFERENCE: 'EDP(230,D0,0
FIELD NUMBER: .12                       FIELD NAME: VISIT
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the pointer to the visit in the Visit file
 (#9000010). HMO uses the V cross reference to locate the record in the ED Log
 file (#230) for the visit.  
FIELD NUMBER: .08                       FIELD NAME: TIME IN
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: TIME OUT
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .14                       FIELD NAME: CLINIC
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: INSTITUTION
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: 'EDP(230,D0,3
FIELD NUMBER: 3.5                       FIELD NAME: MD ASSIGNED
  LOCATION: 3;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 3.6                       FIELD NAME: NURSE ASSIGNED
  LOCATION: 3;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3.7                       FIELD NAME: RESIDENT ASSIGNED
  LOCATION: 3.7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3.8                       FIELD NAME: COMMENT
  LOCATION: 3.8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3.3                       FIELD NAME: ACUITY
  LOCATION: 3;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: 'EDP(230,D0,2
FIELD NUMBER: 3.33                      FIELD NAME: COMPLAINT
  LOCATION: 2;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: 'EDP(230,D0,4
FIELD NUMBER: .01                       FIELD NAME: DISCHARGE DIAGNOSIS
  LOCATION: 4;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ICD9 CODE
  LOCATION: 4;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: 'EDP(230,D0,1
FIELD NUMBER: 1.1                       FIELD NAME: COMPLAINT
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) accesses the
 data in the ED Log file (#230) to retrieve information about emergency room
 visits.  
  
  
 **************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library for list of retired HMP ICRs.  
 **************************************************************
  STATUS: Retired                       EXPIRATION DATE: OCT 27, 2017
KEYWORDS: EDP
KEYWORDS: 230
KEYWORDS: ED LOG
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: APR 26, 2016

NUMBER: 6276                            IA #: 6276
  FILE NUMBER: 4.2                      GLOBAL ROOT: DIC(4.2
  DATE CREATED: NOV 24, 2015            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Controlled Subscription        TYPE: File
  NAME: DIC(4.2                         ID: DIC(4.2
GLOBAL REFERENCE: DIC(4.2,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5.5                       FIELD NAME: STATION
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) uses site
 hashing to identify the individual sites that have treated a patient. The HMP
 code is looping thru the Domain file (#4.2) using direct global access (read 
 only) in order to read the date in the Station field (#5.5) in order compare
 the results to the Institution field (#.02) from the Treating Facility List
 file (#391.91). When a match is made, the domain name (.01) field The Name
 (#.01) from the Domain file (#4.2) for the matching entry is is used to create
 the unique hash identified for the treating site.  
  
 All access to the Domain file is via direct global reads and with FileMan.  
  STATUS: Withdrawn
KEYWORDS: DIC(4.2
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6277                            IA #: 6277
  FILE NUMBER: 601.72                   GLOBAL ROOT: YTT(601.72
  DATE CREATED: NOV 24, 2015            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HMP ACCESS TO YTT(601.72
  ID: YTT(601.72
GLOBAL REFERENCE: YTT(601.72,D0,1
FIELD NUMBER: .01                       FIELD NAME: QUESTION TEXT
  LOCATION: 1;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) is accessing
 the MH Questions file (#601.72) to retrieve the Questions field for a
 specified entry.  
  
 ICR will not be supported after the release of patch YS*5.01*123 
   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 If HMP is restarted in the future, this ICR must be reviewed with the 
 Custodial Package due to the global references and changes implemented with
 YS*5.01*123.  The Mental Health team will not allow the direct global reads
 that are associated with this ICR.  
 **********************************************************************
  STATUS: Retired                       EXPIRATION DATE: OCT 27, 2017
KEYWORDS: YTT(601.72
KEYWORDS: 601.72
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: APR 20, 2016

NUMBER: 6278                            IA #: 6278
  FILE NUMBER: 9000010.23               GLOBAL ROOT: AUPNVHF(
  DATE CREATED: NOV 24, 2015
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: File
  NAME: HMP UPDATE TO 9000010.23        ID: AUPNVHF(
GLOBAL REFERENCE: AUPNVHF(DO,0
FIELD NUMBER: .01                       FIELD NAME: HEALTH FACTOR
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: .03                       FIELD NAME: VISIT
  LOCATION: 0;3                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: AUPNHF(D0,12
FIELD NUMBER: 1201                      FIELD NAME: EVENT DATE AND TIME
  LOCATION: 12;1                        ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) is adding new
 records to the V Health Factors file (#9000010.23). HMP uses UPDATE^DIE to add
 new health factors for a patient visit.  
  
 HMP identifies the last record in the file using a reverse $O. 
  STATUS: Withdrawn
KEYWORDS: 9000010.23
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6279                            IA #: 6279
  FILE NUMBER: 8925.5                   GLOBAL ROOT: TIU(8925.5
  DATE CREATED: NOV 24, 2015
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU AUDIT TRAIL
  ID: TIU(8925.5
GLOBAL REFERENCE: TIU(8925.5,0
FIELD NUMBER: .01                       FIELD NAME: TIU DOCUMENT NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   (#.01) TIU DOCUMENT NAME [1P:8925] 
FIELD NUMBER: 3.02                      FIELD NAME: DATE/TIME OF ACTION
  LOCATION: 3;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   (#3.02) DATE/TIME OF ACTION [2D] 
 GENERAL DESCRIPTION:   Used to retrieve information about TIU audits.  
  
 Access to the "B" cross-reference is needed, also.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  STATUS: Retired                       EXPIRATION DATE: OCT 27, 2017
KEYWORDS: 8925.5
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   The data are needed for extraction from VistA for the
 eHMP.  This is read-only.  
  DATE ACTIVATED: NOV 25, 2015

NUMBER: 6280                            IA #: 6280
  FILE NUMBER: 64.5                     GLOBAL ROOT: LAB(64.5
  DATE CREATED: NOV 24, 2015            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: HMP ACCESS TO LAB(64.5          ID: LAB(64.5
GLOBAL REFERENCE: LAB(64.5,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAB(64.5,D0,1,D1
FIELD NUMBER: .01                       FIELD NAME: MAJOR HEADER
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: MEDICAL CENTER
  LOCATION: 1;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAB(64.5,D0,1,D1,1,D2
FIELD NUMBER: .01                       FIELD NAME: MINOR HEADER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PROFILE SITE/SPECIMEN
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TYPE OF DISPLAY
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: LOCALE FIELD
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAB(64.5,D0,1,D1,1,D2,1,D3
FIELD NUMBER: .01                       FIELD NAME: LAB TEST
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TEST FIELD LENGTH
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: PRINT TEST NAME
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: TEST PRINT CODE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: TEST LOCATIOIN
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: DECIMAL PLACES
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) accesses the
 Lab Reports file (#64.5) to retrieve lab report data.  
  STATUS: Retired                       EXPIRATION DATE: OCT 27, 2017
KEYWORDS: LAB(64.5
KEYWORDS: 64.5
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expires on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  
  DATE ACTIVATED: NOV 06, 2017

NUMBER: 6281                            IA #: 6281
  DATE CREATED: NOV 24, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORWU                         NAME: HMP ACCESS TO NPHASKEY~ORWU
  ID: ORWU
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) request
 permission to ue the NPHASKEY^ORWU API in order check to see if a user has a
 specified security key.  
  STATUS: Withdrawn
KEYWORDS: ORWU
KEYWORDS: NPHASKEY
COMPONENT/ENTRY POINT: NPHASKEY
 COMPONENT DESCRIPTION:   Returns true if a user holds the specified security
 key.  
VARIABLES: KEY                          TYPE: Input
 VARIABLES DESCRIPTION:   The name of the security key.  
VARIABLES: np                           TYPE: Input
 VARIABLES DESCRIPTION:   The user DUZ.  
VARIABLES: VAL                          TYPE: Output
 VARIABLES DESCRIPTION:   Returns True is the person has the security key.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6282                            IA #: 6282
  FILE NUMBER: 9999999.64               GLOBAL ROOT: AUTTFH(
  DATE CREATED: NOV 24, 2015
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: File
  NAME: HMP ACCESS TO AUTTHF            ID: AUTTFH(
GLOBAL REFERENCE: AUTTHF(D0,0
FIELD NUMBER: .01                       FIELD NAME: FACTOR
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   HMP is using the AUTTHF("B" cross reference to look up
 the IEN for the Factor.  
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) is accessing
 the Health Factors file (#9999999.64) to get the Factor (.01) field. 
  STATUS: Withdrawn
KEYWORDS: AUTTHF
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6283                            IA #: 6283
  FILE NUMBER: 100.24                   GLOBAL ROOT: OR(100.24
  DATE CREATED: NOV 24, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: OE/RR PT SEL COMBO
  ID: OR(100.24
GLOBAL REFERENCE: OR(100.24,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: COMBINATION ITEM
  LOCATION: ...,D1,0)                   ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   ^OR(100.24,D0,.01,0)=^100.241V^^  (#1) COMBINATION ITEM 
 ^OR(100.24,D0,.01,D1,0)= (#.01) COMBINATION ITEM [1V] ^ 
 GLOBAL DESCRIPTION:   
  
 The complete file: 
  
 ^OR(100.24,D0,0)= (#.01) NAME [1P:200] ^ ^OR(100.24,D0,.01,0)=^100.241V^^ 
 (#1) COMBINATION ITEM ^OR(100.24,D0,.01,D1,0)= (#.01) COMBINATION ITEM [1V] ^ 
 GENERAL DESCRIPTION:   Used to retrieve data from the OE/RR PT SEL COMBO file
 (100.24).  This is for read-only purposes.  
  
 Reading the "B" cross-reference is allowed.  
  
 NOTE: This access will only be granted to the Enterprise Health Management
 Platform (HMP).  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  STATUS: Retired                       EXPIRATION DATE: OCT 27, 2017
KEYWORDS: OE/RR PT SEL COMBO
KEYWORDS: 100.24
KEYWORDS: OR(100.24)
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: APR 19, 2016

NUMBER: 6284                            IA #: 6284
  FILE NUMBER: 391.91                   GLOBAL ROOT: DGCN(391.91
  DATE CREATED: NOV 25, 2015            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  NAME: HMP ACCESS TO DGCN(391.91       ID: DGCN(391.91
GLOBAL REFERENCE: DGCN(391.91,D0,0
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: INSTITUTION
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: SOURCE ID TYPE
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DGCN(391.91,D0,2
FIELD NUMBER: 10                        FIELD NAME: ASSIGNING AUTHORITY
  LOCATION: 2;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: SOURCE ID
  LOCATION: 2;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 12                        FIELD NAME: IDENTIFIER STATUS
  LOCATION: 2;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   HMP uses the AISS index to determine the record for the
 specified Institution that is associated with the fully qualified ID that is
 made up of the Source ID, Assigning Authority and Source ID Type. If the 
 record exists, the Patient DFN is parsed from the record.  
  
 HMP also uses the APAT cross reference to determine if there is an entry for
 the specified pateint and specified Site IEN.  
  
 HMP uses the APAT cross reference to identify the institutions for the 
 specified patient. HMP loops through the APAT cross reference to get the IEN
 for all records for the patient. Then HMP parse the Institution, Patient DFN,
 Assigning Authority, Source ID, Identifier Status and Source ID Type.  
  STATUS: Withdrawn
KEYWORDS: DGCN(391.91
KEYWORDS: 391.91
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6285                            IA #: 6285
  FILE NUMBER: 9999999.14               GLOBAL ROOT: AUTTIMM(
  DATE CREATED: NOV 30, 2015
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SELECTABLE IMMUNIZATIONS
  ID: AUTTIMM(
GLOBAL REFERENCE: AUTTIMM(D0,0)
FIELD NUMBER: .07                       FIELD NAME: INACTIVE FLAG
  LOCATION: 7th piece                   ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This fields is used to inactivate an immunization type.  
  
GLOBAL REFERENCE: AUTTIMM(D0,6)
FIELD NUMBER: 8803                      FIELD NAME: SELECTABLE FOR HISTORIC
  LOCATION: 1st piece                   ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field determine whether an inactive immunization is
 selectable when documenting a historic administration.  
  
 GENERAL DESCRIPTION:   
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 01, 2017
KEYWORDS: PXRM
KEYWORDS: IMMUNIZATIONS
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: DEC 16, 2015

NUMBER: 6286                            IA #: 6286
  DATE CREATED: DEC 09, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS KEY CHECK
  REMOTE PROCEDURE: XUS KEY CHECK
 GENERAL DESCRIPTION:   This RPC will check if the user (DUZ) holds a security
 key or an array of keys. If a single security KEY is sent the result is
 returned in R(0). If an array is sent down then the return array has the same
 order as the calling array.  
  
 Input parameter: KEY - If key is a single value it holds one key to check. If
 key is an array then the result is an array that matches the key list with
 values that match the status of the key check for each key.  The return is a 1
 if the user has the key and 0 if not.  
  
 Input parameter: IEN - (Optional) If provided, this is the IEN of the user in
 the NEW PERSON file (#200) to check if they hold the key(s) listed in KEY. If
 not provided, this parameter defaults to the DUZ (IEN) of the current user.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XUSRB
KEYWORDS: OWNSKEY
KEYWORDS: SECURITY
KEYWORDS: KEY
  DATE ACTIVATED: SEP 12, 2016

NUMBER: 6287                            IA #: 6287
  DATE CREATED: DEC 09, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS ALLKEYS
  REMOTE PROCEDURE: XUS ALLKEYS
 GENERAL DESCRIPTION:   This RPC will return all the KEYS that a user holds. If
 the FLAG is set to some value the list of KEYS will be screened to only be
 those for J2EE use. The RPC was designed for FATKAAT and KAAJEE (VistALink
 clients) but may be used by other applications.  
  
 Input parameter: IEN - This is the IEN or DUZ of the user in question. If not
 passed in, the RPC will use the current user DUZ (IEN).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XUSRB
KEYWORDS: ALLKEYS
KEYWORDS: SECURITY
KEYWORDS: KEYS
  DATE ACTIVATED: OCT 03, 2017

NUMBER: 6288                            IA #: 6288
  DATE CREATED: DEC 09, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS IAM FIND USER
  REMOTE PROCEDURE: XUS IAM FIND USER   STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: IAMFU
KEYWORDS: XUESSO3
SUBSCRIBING PACKAGE: VISTA SERVICES ASSEMBLER
 SUBSCRIBING DETAILS:   VSA is implementing a New Person Web Service to be used
 by Identity and Access Management.  
  DATE ACTIVATED: AUG 22, 2016

NUMBER: 6289                            IA #: 6289
  DATE CREATED: DEC 09, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS IAM DISPLAY USER
  REMOTE PROCEDURE: XUS IAM DISPLAY USER
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IAMDU
KEYWORDS: XUESSO3
SUBSCRIBING PACKAGE: VISTA SERVICES ASSEMBLER
 SUBSCRIBING DETAILS:   VSA is implementing a New Person Web Service to be used
 by Identity and Access Management.  
  DATE ACTIVATED: AUG 22, 2016

NUMBER: 6290                            IA #: 6290
  DATE CREATED: DEC 09, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS IAM ADD USER
  REMOTE PROCEDURE: XUS IAM ADD USER    STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: IAMAU
KEYWORDS: XUESSO3
SUBSCRIBING PACKAGE: VISTA SERVICES ASSEMBLER
 SUBSCRIBING DETAILS:   VSA is implementing a New Person Web Service to be used
 by Identity and Access Management.  
  DATE ACTIVATED: AUG 22, 2016

NUMBER: 6291                            IA #: 6291
  DATE CREATED: DEC 09, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS IAM EDIT USER
  REMOTE PROCEDURE: XUS IAM EDIT USER   STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: IAMEU
KEYWORDS: XUESSO3
SUBSCRIBING PACKAGE: VISTA SERVICES ASSEMBLER
 SUBSCRIBING DETAILS:   VSA is implementing a New Person Web Service to be used
 by Identity and Access Management.  
  DATE ACTIVATED: AUG 22, 2016

NUMBER: 6292                            IA #: 6292
  DATE CREATED: DEC 09, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS IAM TERMINATE USER
  REMOTE PROCEDURE: XUS IAM TERMINATE USER
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IAMTU
KEYWORDS: XUESSO3
SUBSCRIBING PACKAGE: VISTA SERVICES ASSEMBLER
 SUBSCRIBING DETAILS:   VSA is implementing a New Person Web Service to be used
 by Identity and Access Management.  
  DATE ACTIVATED: SEP 12, 2016

NUMBER: 6293                            IA #: 6293
  DATE CREATED: DEC 09, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS IAM REACTIVATE USER
  REMOTE PROCEDURE: XUS IAM REACTIVATE USER
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IAMRU
KEYWORDS: XUESSO3
SUBSCRIBING PACKAGE: VISTA SERVICES ASSEMBLER
 SUBSCRIBING DETAILS:   VSA is implementing a New Person Web Service to be used
 by Identity and Access Management.  
  DATE ACTIVATED: SEP 12, 2016

NUMBER: 6294                            IA #: 6294
  DATE CREATED: DEC 09, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS IAM BIND USER
  REMOTE PROCEDURE: XUS IAM BIND USER   STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: IAMBU
KEYWORDS: XUESSO4
  DATE ACTIVATED: AUG 22, 2016

NUMBER: 6295                            IA #: 6295
  DATE CREATED: DEC 09, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS ESSO VALIDATE
  REMOTE PROCEDURE: XUS ESSO VALIDATE   STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: ESSO
KEYWORDS: XUESSO4
SUBSCRIBING PACKAGE: RPC BROKER
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via XOBV VALIDATE SAML (exposed by XUS ESSO VALIDATE): 
   Blind Rehabilitation, PATS, VPFS, DTC Integration 
   Platform (DIP) (VASI: 2825), 
   Lighthouse (DVP)  (VASI: 2196) 
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL
 SUBSCRIBING DETAILS:   Functionality will be used as a part of the two factor
 authentication (2FA) conversion effort for Beneficiary Travel Dashboard.  
SUBSCRIBING PACKAGE: 1
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT
 SUBSCRIBING DETAILS:   Added 12/08/21, in order for the Emergency Department
 Integration System (EDIS) to continue to have login functionality once the
 Vista Integration Adapter (VIA) is retired, EDIS requires use of this remote
 procedure call (RPC). Patch EDP*2*16 will allow  EDIS to communicate with this
 RPC.  
SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM
 SUBSCRIBING DETAILS:   In order for the Blind Rehabilitation application to
 continue to have login functionality once the Vista Integration Adapter (VIA)
 is retired, ANRV requires use of this remote procedure call (RPC). Patch
 ANRV*5.1*1 will allow Blind Rehabilitation to communicate with this RPC.  
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 5/13/25 effective with YS*5.01*236 patch. Cloud
 application MHA is migrating from VistALink to Cocytus, to communicate with
 VistA. In order to continue to have login functionality with Cocytus, MHA 
 requires use of this RPC.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 3/23/26, effective with DSIY*1.4*0 released
 2/8/19 APAR granted approval based on the historic usage.  
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 3/23/26, effective with DSSO*2.0 released 4/16/20 
 APAT granted approval based on the historic usage.  
  DATE ACTIVATED: AUG 22, 2016

NUMBER: 6296                            IA #: 6296
  DATE CREATED: DEC 09, 2015            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS CVC
  REMOTE PROCEDURE: XUS CVC             STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: CVC
KEYWORDS: XUSRB
SUBSCRIBING PACKAGE: RPC BROKER
SUBSCRIBING PACKAGE: VISTALINK
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   Added 9/27/19 
  DATE ACTIVATED: SEP 01, 2017

NUMBER: 6297                            IA #: 6297
  DATE CREATED: DEC 10, 2015            CUSTODIAL PACKAGE: SCHEDULING
  TYPE: Routine                         ROUTINE: SDCNSLT
  NAME: USAGE OF SCHEDULING ENTRY POINT
  ID: SDCNSLT
 GENERAL DESCRIPTION:   VPS CANCEL APPOINTMENT RPC calls the CANCEL^SDCNSLT
 entry point when an appointment is cancelled with the Vetlink Kiosk
 application.  The Vetlink Kiosk application provides the veteran Scheduling
 functionality via the KIOSKS located at VA Medical Centers.  The
 CANCEL^SDCNSLT is a pre-existing procedure that is called to update the
 consult as part of the processing of the CANCEL APPOINTMENT action located on
 Appt Mgt Module screen associated with the Appointment Management [SDAM APPT
 MGT] option.   
  
 If a consult link exists, determined at ^SC(D0,S,D1,1,D2,CONS), then VPS KIOSK 
 application will need to call the CANCEL^SDCNSLT entry point to support the 
 Scheduling Consult Appointment linkage functionality.  
  
  STATUS: Withdrawn
KEYWORDS: SDCNSLT
KEYWORDS: VPS
KEYWORDS: CANCEL
COMPONENT/ENTRY POINT: CANCEL
 COMPONENT DESCRIPTION:   The CANCEL procedure updates the consult status as
 part of the Scheduling Consult Appointment Linkage.  
  
VARIABLES: SDTTM                        TYPE: Input
 VARIABLES DESCRIPTION:   Date and time for the appointment.  
  
VARIABLES: SDSC                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer for the clinic in the Hospital Location file
 (#44).  
  
VARIABLES: SDPL                         TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the appointment record in the Appointment
 Multiple of the Hospital Location file (#44).  
  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)

NUMBER: 6298                            IA #: 6298
  FILE NUMBER: 53.79                    GLOBAL ROOT: PSB(53.79
  DATE CREATED: DEC 14, 2015            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HMP ACCESS TO PSB(53.79
  ID: PSB(53.79
GLOBAL REFERENCE: PSB(53.79,DO,.2
FIELD NUMBER: .21                       FIELD NAME: PRN REASON
  LOCATION: .2;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .22                       FIELD NAME: PRN EFFECTIVENESS
  LOCATION: .2;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .23                       FIELD NAME: PRN EFFECTIVENESS ENTERED BY
  LOCATION: .2;3                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .24                       FIELD NAME: PRN EFFECTIVENESS ENTERED AT
  LOCATION: .2;4                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .25                       FIELD NAME: PRN EFFECTIVENESS MINUTES
  LOCATION: .2;5                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSB(53.79,D0,0
FIELD NUMBER: .07                       FIELD NAME: ACTION BY
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: ACTION STATUS
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSB(53.79,D0,.1
FIELD NUMBER: .16                       FIELD NAME: INJECTION SITE
  LOCATION: .1;6                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSB(53.79,D0,.5
FIELD NUMBER: .01                       FIELD NAME: DISPENSE DRUG
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DOSES ORDERED
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DOSES GIVEN
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: UNIT OF ADMINISTRATION
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: HIGH RISK/HIGH ALERT
  LOCATION: 0;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSB(53.79,D0,.6
FIELD NUMBER: .01                       FIELD NAME: ADDITIVIES
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DOSE ORDERED
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DOSE GIVEN
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: UNIT OF ADMINISTRATION
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: HIGH RISK/HIGH ALERT
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSB(53.79,D0,.7
FIELD NUMBER: .01                       FIELD NAME: SOLUTIONS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DOSE ORDERED
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DOSES GIVEN
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: UNIT OF ADMINISTRATION
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: HIGH RISK/HIGH ALERT
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) is accessing
 the BCMA Medication Log file (53.79) to retrieve information about the 
 administration of med orders.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: PSB(53.79
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   Access to BCMA Medication Log (#53.79) file is part of
 the process that collects the BCMA administration data and sends it to the
 JSON Database System (JDS).  
  DATE ACTIVATED: APR 22, 2016

NUMBER: 6299                            IA #: 6299
  DATE CREATED: DEC 15, 2015
  CUSTODIAL PACKAGE: HEALTH MANAGEMENT PLATFORM
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HMPEVNT
  NAME: TIU use of TIU~HMPEVNT          ID: HMPEVNT
 GENERAL DESCRIPTION:   Patch TIU*1*106 introduces code in the TIU package to
 trigger sync actions to update the eHMP JDS database system when new notes are
 added or existed notes are edited.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 subscribing application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
  **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMPEVNT
COMPONENT/ENTRY POINT: TIU
 COMPONENT DESCRIPTION:   Calls the HMP API to trigger the sync.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient DFN.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the note in the TIU DOCUMENT file
 (#8925).  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  DATE ACTIVATED: JAN 11, 2016

NUMBER: 6300                            IA #: 6300
  FILE NUMBER: 53.46                    DATE CREATED: DEC 15, 2015
  CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Supported                      TYPE: File
  NAME: CLINIC DEFINITION
 GENERAL DESCRIPTION:   The purpose of this Application Programming Interface
 (API) is to provide the information from the Clinic Definition (#53.46) file
 from Inpatient Medications.  
  STATUS: Pending
KEYWORDS: 53.46
KEYWORDS: CLINIC DEFINITION

NUMBER: 6301                            IA #: 6301
  DATE CREATED: DEC 15, 2015
  CUSTODIAL PACKAGE: HEALTH MANAGEMENT PLATFORM
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HMPEVNT
  NAME: USR use of POSTX~HMPEVNT        ID: HMPEVNT
 GENERAL DESCRIPTION:   Patch USR*1*37 introduces code to trigger a sync to HMP
 JDS system wheneve a new user class is created or when an existing user class
 is edited.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 subscribing application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
  **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMPEVNT
KEYWORDS: POSTX
COMPONENT/ENTRY POINT: POSTX
 COMPONENT DESCRIPTION:   Triggers the sync action to send new user classes or
 edits of existing user classes to HMP JDS system. 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Domain to be sync action to be taken.  
VARIABLES: ID                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN for the entry in the User Class file (#201).  
VARIABLES: ACT                          TYPE: Input
 VARIABLES DESCRIPTION:   Type of action to take. Optional. 
SUBSCRIBING PACKAGE: AUTHORIZATION/SUBSCRIPTION
  DATE ACTIVATED: JAN 11, 2016

NUMBER: 6302                            IA #: 6302
  DATE CREATED: DEC 16, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORALWORD ALLWORD
  REMOTE PROCEDURE: ORALWORD ALLWORD
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
  
 NAME: ORALWORD ALLWORD                  TAG: ALLWORD 
   ROUTINE: ORALWORD                     RETURN VALUE TYPE: ARRAY 
   APP PROXY ALLOWED: Yes                                        INPUT
 PARAMETER: DFN                    PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 INPUT PARAMETER:
 OROI                   PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 2 INPUT PARAMETER:
 ORX                    PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 3 INPUT PARAMETER:
 ORTYPE                 PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 4 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.                       
  DATE ACTIVATED: FEB 05, 2016

NUMBER: 6303                            IA #: 6303
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORCHECK GETXTRA
  REMOTE PROCEDURE: ORCHECK GETXTRA
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
       The following information is available about the RPC: 
     
 NAME: ORCHECK GETXTRA                   TAG: GETXTRA 
   ROUTINE: ORCHECK                      RETURN VALUE TYPE: ARRAY 
   WORD WRAP ON: TRUE                    APP PROXY ALLOWED: Yes 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 05, 2016

NUMBER: 6304                            IA #: 6304
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORDDPAPI CLOZMSG
  REMOTE PROCEDURE: ORDDPAPI CLOZMSG
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
  
 NAME: ORDDPAPI CLOZMSG                  TAG: CLOZMSG 
   ROUTINE: ORDDPAPI                     RETURN VALUE TYPE: WORD PROCESSING 
   WORD WRAP ON: TRUE                    APP PROXY ALLOWED: Yes 
  RETURN PARAMETER DESCRIPTION:   
  Returns the text of the OR CLOZ INPT MSG parameter used to display to the
 user if it is set when entering an inpatient clozapine order.  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 05, 2016

NUMBER: 6305                            IA #: 6305
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: OREVNTX1 GETSTS
  REMOTE PROCEDURE: OREVNTX1 GETSTS
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
  
 NAME: OREVNTX1 GETSTS                   TAG: GETSTS 
   ROUTINE: OREVNTX1                     RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch. 
  DATE ACTIVATED: FEB 05, 2016

NUMBER: 6306                            IA #: 6306
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQCN STATUS
  REMOTE PROCEDURE: ORQQCN STATUS
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
  
 NAME: ORQQCN STATUS                     TAG: STATUS 
   ROUTINE: ORQQCN2                      RETURN VALUE TYPE: ARRAY 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Returns a list of consult statuses currently in use, as reflected in the 
  "AC" XREF of ^GMR(123.1.  
  RETURN PARAMETER DESCRIPTION:   
  List of [Status IEN in ^ORD(100.01 concatenated with status text] 
   
  IEN^Text 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 05, 2016

NUMBER: 6307                            IA #: 6307
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQCN SVC W/SYNONYMS
  REMOTE PROCEDURE: ORQQCN SVC W/SYNONYMS
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
  
 NAME: ORQQCN SVC W/SYNONYMS             TAG: SVCSYN 
   ROUTINE: ORQQCN2                      RETURN VALUE TYPE: GLOBAL ARRAY 
   WORD WRAP ON: TRUE                    APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  This is a modified version of ORQQCN GET SERVICE TREE that also includes 
  synonyms for the services returned. It also allows passing of an optional 
  Consult IEN, for screening allowable services to forward the consult to, 
  especially in the case of interfacility consults.  INPUT PARAMETER: Start
 With             PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 32 
  DESCRIPTION:   
  Which service in the hierarchy to begin with.  INPUT PARAMETER: Purpose       
         PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 2 
  DESCRIPTION:   
  0 for display purposes, 1 to order or forward a consult.  INPUT PARAMETER:
 Include Synonyms       PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 2 
  DESCRIPTION:   
  0 to exclude synonyms, 1 to include synonyms.  INPUT PARAMETER: Consult IEN   
         PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 16               REQUIRED: NO 
  DESCRIPTION:   
  OPTIONAL - Include pointer to file 123, the Consult Request file.  Used 
  when forwarding a consult, and screening needs to be done to limit the 
  list of services.  
  RETURN PARAMETER DESCRIPTION:   
  Output: Array formatted as follows- 
   
     svc ien^svc name or syn^parent^has children^svc usage^orderable item 
  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 05, 2016

NUMBER: 6308                            IA #: 6308
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWD1 PRINTGUI
  REMOTE PROCEDURE: ORWD1 PRINTGUI
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWD1 PRINTGUI                    TAG: PRINTGUI 
   ROUTINE: ORWD1                        RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  RPC used by CPRS GUI to print orders to a designated print device.  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 05, 2016

NUMBER: 6309                            IA #: 6309
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWD1 RVPRINT
  REMOTE PROCEDURE: ORWD1 RVPRINT
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWD1 RVPRINT                     TAG: RVPRINT 
   ROUTINE: ORWD1                        RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  RPC used by CPRS GUI to print orders to a designated print device after 
  the review or sign actions were used.  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 05, 2016

NUMBER: 6310                            IA #: 6310
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWD2 DEVINFO
  REMOTE PROCEDURE: ORWD2 DEVINFO
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWD2 DEVINFO                     TAG: DEVINFO 
   ROUTINE: ORWD2                        RETURN VALUE TYPE: ARRAY 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Returns device information related to a location/nature of order when an 
  order is signed or released via CPRS GUI.  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 03, 2016

NUMBER: 6311                            IA #: 6311
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDCN32 ORDRMSG
  REMOTE PROCEDURE: ORWDCN32 ORDRMSG
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
  
 NAME: ORWDCN32 ORDRMSG                  TAG: ORDRMSG 
   ROUTINE: ORWDCN32                     RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 03, 2016

NUMBER: 6312                            IA #: 6312
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDPS1 FAILDEA
  REMOTE PROCEDURE: ORWDPS1 FAILDEA
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDPS1 FAILDEA                   TAG: FAILDEA 
   ROUTINE: ORWDPS1                      RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 03, 2016

NUMBER: 6313                            IA #: 6313
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDPS1 ODSLCT
  REMOTE PROCEDURE: ORWDPS1 ODSLCT
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDPS1 ODSLCT                    TAG: ODSLCT 
   ROUTINE: ORWDPS1                      RETURN VALUE TYPE: ARRAY 
   APP PROXY ALLOWED: Yes 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 03, 2016

NUMBER: 6314                            IA #: 6314
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDPS2 DAY2QTY
  REMOTE PROCEDURE: ORWDPS2 DAY2QTY
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDPS2 DAY2QTY                   TAG: DAY2QTY 
   ROUTINE: ORWDPS2                      RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 03, 2016

NUMBER: 6315                            IA #: 6315
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDPS2 MAXREF
  REMOTE PROCEDURE: ORWDPS2 MAXREF
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
  
 NAME: ORWDPS2 MAXREF                    TAG: MAXREF 
   ROUTINE: ORWDPS2                      RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 03, 2016

NUMBER: 6316                            IA #: 6316
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDPS2 QTY2DAY
  REMOTE PROCEDURE: ORWDPS2 QTY2DAY
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDPS2 QTY2DAY                   TAG: QTY2DAY 
   ROUTINE: ORWDPS2                      RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 03, 2016

NUMBER: 6317                            IA #: 6317
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDPS32 DRUGMSG
  REMOTE PROCEDURE: ORWDPS32 DRUGMSG
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDPS32 DRUGMSG                  TAG: DRUGMSG 
   ROUTINE: ORWDPS33                     RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Return message text that is associated with a dispense drug.  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 05, 2016

NUMBER: 6318                            IA #: 6318
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDPS32 ISSPLY
  REMOTE PROCEDURE: ORWDPS32 ISSPLY
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDPS32 ISSPLY                   TAG: ISSPLY 
   ROUTINE: ORWDPS33                     RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Return 1 if orderable item is a supply, otherwise return 0.  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 05, 2016

NUMBER: 6319                            IA #: 6319
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDPS32 VALQTY
  REMOTE PROCEDURE: ORWDPS32 VALQTY
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDPS32 VALQTY                   TAG: VALQTY 
   ROUTINE: ORWDPS33                     RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Validate a medication quantity and return a 1 if it is valid, otherwise 
  return 0.  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 05, 2016

NUMBER: 6320                            IA #: 6320
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDPS32 VALROUTE
  REMOTE PROCEDURE: ORWDPS32 VALROUTE
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDPS32 VALROUTE                 TAG: VALROUTE 
   ROUTINE: ORWDPS32                     RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Returns the IEN for a route if the name is valid.  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 02, 2016

NUMBER: 6321                            IA #: 6321
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDRA32 APPROVAL
  REMOTE PROCEDURE: ORWDRA32 APPROVAL
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDRA32 APPROVAL                 TAG: APPROVAL 
   ROUTINE: ORWDRA32                     RETURN VALUE TYPE: ARRAY 
   APP PROXY ALLOWED: Yes 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 02, 2016

NUMBER: 6322                            IA #: 6322
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDRA32 DEF
  REMOTE PROCEDURE: ORWDRA32 DEF
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDRA32 DEF                      TAG: DEF 
   ROUTINE: ORWDRA32                     RETURN VALUE TYPE: ARRAY 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Loads dialog data (lists & defaults) for a radiology order.  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 02, 2016

NUMBER: 6323                            IA #: 6323
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDX DGNM
  REMOTE PROCEDURE: ORWDX DGNM
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDX DGNM                        TAG: DGNM 
   ROUTINE: ORWDX                        RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 02, 2016

NUMBER: 6324                            IA #: 6324
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDX LOCK ORDER
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDX LOCK ORDER                  TAG: LOCKORD 
   ROUTINE: ORWDX                        RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  RPC to attempt to lock a specific order.  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  

NUMBER: 6325                            IA #: 6325
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDX UNLOCK ORDER
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDX UNLOCK ORDER                TAG: UNLKORD 
   ROUTINE: ORWDX                        RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  RPC to unlock a specific order.  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  

NUMBER: 6326                            IA #: 6326
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDX2 DCREASON
  REMOTE PROCEDURE: ORWDX2 DCREASON
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDX2 DCREASON                   TAG: DCREASON 
   ROUTINE: ORWDX2                       RETURN VALUE TYPE: ARRAY 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  RPC to return a list of valid discontinuation reasons.  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 02, 2016

NUMBER: 6327                            IA #: 6327
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXA ISACTOI
  REMOTE PROCEDURE: ORWDXA ISACTOI
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDXA ISACTOI                    TAG: ISACTOI 
   ROUTINE: ORWDXA                       RETURN VALUE TYPE: SINGLE VALUE 
   WORD WRAP ON: TRUE                    APP PROXY ALLOWED: Yes 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 02, 2016

NUMBER: 6328                            IA #: 6328
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXR RNWFLDS
  REMOTE PROCEDURE: ORWDXR RNWFLDS
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDXR RNWFLDS                    TAG: RNWFLDS 
   ROUTINE: ORWDXR                       RETURN VALUE TYPE: ARRAY 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Return fields for renew action in format: 
      LST(0)=RenewType^Start^Stop^Refills^Pickup  LST(n)=Comments 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 02, 2016

NUMBER: 6329                            IA #: 6329
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXR01 CANCHG
  REMOTE PROCEDURE: ORWDXR01 CANCHG
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWDXR01 CANCHG                   TAG: CANCHG 
   ROUTINE: ORWDXR01                     RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 02, 2016

NUMBER: 6330                            IA #: 6330
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWGRPC ITEMDATA
  REMOTE PROCEDURE: ORWGRPC ITEMDATA
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWGRPC ITEMDATA                  TAG: ITEMDATA 
   ROUTINE: ORWGRPC                      RETURN VALUE TYPE: GLOBAL ARRAY 
   WORD WRAP ON: TRUE                    APP PROXY ALLOWED: Yes 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 02, 2016

NUMBER: 6331                            IA #: 6331
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWGRPC ITEMS
  REMOTE PROCEDURE: ORWGRPC ITEMS
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWGRPC ITEMS                     TAG: ITEMS 
   ROUTINE: ORWGRPC                      RETURN VALUE TYPE: GLOBAL ARRAY 
   WORD WRAP ON: TRUE                    APP PROXY ALLOWED: Yes 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 02, 2016

NUMBER: 6332                            IA #: 6332
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWOR1 GETDSCH
  REMOTE PROCEDURE: ORWOR1 GETDSCH
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWOR1 GETDSCH                    TAG: GETDSCH 
   ROUTINE: ORWOR1                       RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Returns the schedule of the drug.  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 02, 2016

NUMBER: 6333                            IA #: 6333
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWRP GET DEFAULT PRINTER
  REMOTE PROCEDURE: ORWRP GET DEFAULT PRINTER
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
  
 NAME: ORWRP GET DEFAULT PRINTER         TAG: GETDFPRT 
   ROUTINE: ORWRP                        RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Returns default printer.  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 02, 2016

NUMBER: 6334                            IA #: 6334
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWTPD GETDFLT
  REMOTE PROCEDURE: ORWTPD GETDFLT
 GENERAL DESCRIPTION:   A new OR*3*426 patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: ORWTPD GETDFLT                    TAG: GETDFLT 
   ROUTINE: ORWTPD                       RETURN VALUE TYPE: SINGLE VALUE 
   WORD WRAP ON: TRUE                    APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  get default setting for all reports(time/occ limits) 
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The OR*3*426 patch is associated with the
 VIAB*1*5 patch.  
  DATE ACTIVATED: FEB 02, 2016

NUMBER: 6335                            IA #: 6335
  DATE CREATED: DEC 17, 2015
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Remote Procedure
  NAME: TIU DETAILED DISPLAY
 GENERAL DESCRIPTION:   A new TIU*1*??? patch will be distributed that turns on
 this RPC's flag - APP PROXY ENABLED. The TIU*1*??? patch is associated with
 the VIAB*1*5 patch.  
  
  
    The following information is available about the RPC: 
   
 NAME: TIU DETAILED DISPLAY              TAG: RPC 
   ROUTINE: TIUSRV                       RETURN VALUE TYPE: GLOBAL ARRAY 
   AVAILABILITY: SUBSCRIPTION            WORD WRAP ON: TRUE 
   APP PROXY ALLOWED: Yes 
  DESCRIPTION:   
  Gets details for display of a given record.  INPUT PARAMETER: TIUDA           
       PARAMETER TYPE: LITERAL 
   REQUIRED: YES 
  DESCRIPTION:   
  This is the record number (IEN) in the TIU Document File (#8925).  
  RETURN PARAMETER DESCRIPTION:   
  Returns all known details of the record identified by TIUDA (Source, 
  Signature, Linked Problems, Body of document, etc.).  
  
 This ICR is created to satisfy the needs of the VIA project which is tasked to
 replace MDWS services. 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will use this RPC in the VIAB*1*5 patch. One of the
 charges to the VIA project is exposing RPCs and creating ICRs for those RPCs
 that are already in use by the MDWS infrastructure. VIA provides a Class I
 product of services that work with VistaLink, replacing the need for
 developers to use MDWS services.  The TIU*1*??? patch is associated with the
 VIAB*1*5 patch.  

NUMBER: 6336                            IA #: 6336
  DATE CREATED: JUN 30, 2017            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: WVRPCPT1
  NAME: SAVE STATUS REVIEW NOTIFICATION DATA
  ID: WVRPCPT1
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to add entries to the WV PREGNANCY/LACTATION STATUS CONFLICT EVENTS file
 (#790.9). Entries in this file are created when a patient's pregnancy or
 lactation state stored in the Women's Health software package conflicts with
 data in other software packages. For example, the Women's Health pregnancy
 state is NOT PREGNANT and a pregnancy laboratory test is resulted as positive, 
 subscribers should create an entry in file #790.9 with the pertinent details.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PREGNANCY
KEYWORDS: LACTATION
COMPONENT/ENTRY POINT: $$SAVESRND(WVDATA)
 COMPONENT DESCRIPTION:   This entry point will create a new entry in the WV
 PREGNANCY/LACTATION STATUS CONFLICT EVENTS file (#790.9).  
VARIABLES: WVDATA                       TYPE: Input
 VARIABLES DESCRIPTION:   Reference to an array that contains the pertinent
 data to create a new entry. The array is formatted as follows: 
  
   WVDATA("ID")=Caret-delimited string 
     Caret-delimited string - identifying data 
  
 PIECE   VALUE 
 ==========================
  1      The patient's internal entry 
         number (IEN) in the WV PATIENT 
         file (#790) 
  2      Type of status data that is 
         conflicting; 'P' for pregnancy 
         or 'L' for lactation 
  
   WVDATA("LAB")=Pipe-delimited string 
     Pipe-delimited string - laboratory test data 
                             that is in conflict 
  
 PIECE   VALUE 
 ==========================
  1      Observation D/T 
  2      Observation ID 
  3      Observation Sub-ID 
  4      Observation Value 
  5      Units 
  6      Reference Range 
  
 Refer to the OBX portion of the HL7 Fields sub-section of the Laboratory 
 section within the OE/RR Version 3 Package Interface Specifications document
 for details and formatting of each piece.  
  
   WVDATA("CODE")=Pipe-delimited string 
     Pipe-delimited string - diagnosis code data 
                             that is in conflict 
  
 PIECE   VALUE 
 ==========================
  1      SAB 
  2      CODE 
  
 Refer to the Input variables for the $$EXP component in integration agreement
 #5680 for a description of each piece value.  
  
 When calling this component, the "ID" subscript is required. In addition, 
 either the "LAB" or the "CODE" subscript must be defined (the caller may 
 define both of these subscripts in the same call).  
VARIABLES: $$SAVESRND                   TYPE: Output
 VARIABLES DESCRIPTION:   Caret-delimited string indicating the call's status: 
  
 PIECE   VALUE 
 ==========================
  1      1 for successfully created new entry 
         -1 for an error 
  2      Error message 
         "" when the call is successful 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: NOV 17, 2017

NUMBER: 6337                            IA #: 6337
  DATE CREATED: DEC 21, 2015            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: WVRPCPT1
  NAME: POTENTIAL UNSAFE ORDERS LIST    ID: WVRPCPT1
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to retrieve a list of potentially unsafe orders in a user friendly format.
 This list is displayed when changing the patient's pregnancy status to
 pregnant or lactation status to lactating.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Potential Teratogenic Orders
KEYWORDS: Potential Unsafe Orders
KEYWORDS: TIU Object
COMPONENT/ENTRY POINT: $$GETORDRS(DFN,TYPE,CACHE)
 COMPONENT DESCRIPTION:   This line tag returns a list of potentially unsafe
 orders. Depending on the value of the TYPE parameter, it assumes the patient
 is either pregnant or lactating.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient's entry in
 the PATIENT file (#2).  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   The context in which the list of orders are displayed
 by the caller.  Possible values are: 
  
   P - Pregnant context 
   L - Lactation context 
  
 Certain orders are only considered unsafe if a patient is lactating while 
 other orders are only considered unsafe while the patient is pregnant.  
VARIABLES: CACHE                        TYPE: Input
 VARIABLES DESCRIPTION:   Boolean flag indicating whether to store a copy of
 the returned text in nodes descendant from ^TMP("WVPTOCACHE",$J,TYPE) and
 populate the TMP("WVGETORDERS",$J,TYPE) output variable; the value 1 will
 store a copy as well as populate the variable and the value 0 will not store a
 copy as well as not populate the variable. TYPE is the value of the input 
 variable TYPE.  
VARIABLES: $$GETORDRS                   TYPE: Output
 VARIABLES DESCRIPTION:   The node address where the output is stored preceded
 with the characters 
 "~@".
VARIABLES: TMP GLOBAL                   TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP("WVPTO",$J,LINE,0)=TEXT 
   LINE: line number of text; starts at one 
         and increments by one 
   TEXT: a line of text to display to the user 
  
 The following globals are only created when the CACHE input variable is set to
 a value of one: ^TMP("WVGETORDERS",$J,TYPE)=N 
   TYPE: value of the input variable TYPE.  
   N: the number of unsafe orders found 
  
 ^TMP("WVPTOCACHE",$J,TYPE,LINE,0)=TEXT 
   This is a copy of the text stored in the node 
   address returned by $$GETORDRS.  
   TYPE: value of the input variable TYPE.  
   LINE: line number of text; starts at one 
         and increments by one 
   TEXT: a line of text to display to the user 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Text Integration Utilities will display the list within
 an object.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Clinical Reminders will reference the number of unsafe
 orders returned.  
  DATE ACTIVATED: NOV 17, 2017

NUMBER: 6338                            IA #: 6338
  FILE NUMBER: 52.6                     GLOBAL ROOT: DD(52.6
  DATE CREATED: DEC 21, 2015            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PSS*1*189 POST INSTALL WITH DD(52.6 
  ORIGINAL NUMBER: 6338                 ID: DD(52.6
 GENERAL DESCRIPTION:   This is a one-time ICR valid only for the Post-Install
 Routine for patch PSS*1.0*189.  
  
 The INACTIVATION DATE field (#12) field will be displayed on any lookup 
 performed on the IV ADDITIVES File (#52.6) by creating a new "ID" node by
 direct global set into ^DD(52.6,0,"ID",12) by Post-Install Routine PSS*1*189.  
  STATUS: Active                        DURATION: Next Version
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  DATE ACTIVATED: JUL 12, 2016

NUMBER: 6339                            IA #: 6339
  FILE NUMBER: 52.7                     GLOBAL ROOT: DD(52.7
  DATE CREATED: DEC 21, 2015            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PSS*1*189 POST INSTALL WITH DD(52.7
  ORIGINAL NUMBER: 6338                 ID: DD(52.7
 GENERAL DESCRIPTION:   This is a one-time ICR valid only for the Post-Install
 Routine for patch PSS*1.0*189 
  
 The INACTIVATION DATE field (#8) field will be displayed on any lookup 
 performed on the IV SOLUTIONS File (#52.7) by creating a new "ID" node by 
 direct global set into ^DD(52.7,0,"ID",8) by Post-Install Routine PSS*1*189.  
  STATUS: Active                        DURATION: Next Version
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  DATE ACTIVATED: JUL 12, 2016

NUMBER: 6340                            IA #: 6340
  DATE CREATED: JAN 05, 2016            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMFRPT
  NAME: SEARCH FOR FINDINGS             ID: PXRMFRPT
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to search for reminder definitions, terms, list rules, dialogs, order check
 items groups and order check rules that reference an entity, such as orderable 
 items or quick orders.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FINDING USAGE
KEYWORDS: FINDING SEARCH
KEYWORDS: ORDERABLE ITEM SEARCH
KEYWORDS: QUICK ORDER SEARCH
COMPONENT/ENTRY POINT: BLDLIST(FILENUM,GBL,FIEN,SUB)
 COMPONENT DESCRIPTION:   Returns a list of the reminder components that
 reference a specific entity.  
VARIABLES: FILENUM                      TYPE: Input
 VARIABLES DESCRIPTION:   The file number which contains the entity to search
 components for.  
VARIABLES: GBL                          TYPE: Input
 VARIABLES DESCRIPTION:   The global location where the file's data is stored.
 The location should not contain the leading caret.  
VARIABLES: FIEN                         TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the entity in the
 FILENUM file. This variable is optional. If it is not set, then all components
 are returned.  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   The name of the subscript in the ^TMP($J) global
 under which found components should be returned.  
VARIABLES: TMP($J,SUB)                  TYPE: Output
 VARIABLES DESCRIPTION:   Found components are returned in the ^TMP($J,SUB)
 global. This global has the following structure: 
   ^TMP($J,SUB,FILENUM,FIEN,TYPE,IEN,NUM)="" 
  
   FILENUM: see the FILENUM input variable 
            description 
   FIEN: internal entry number of the entity in the 
         FILENUM file 
   TYPE: type of component 
         "DEF" - Reminder Definition 
         "TERM" - Reminder Term 
         "DIALOG" - Reminder Dialog 
         "ROC" - Reminder Order Check Items Group 
         "OCRULE" - Reminder Order Check Rule 
         "LRULE" - Reminder List Rule 
   IEN: internal entry number of the component in 
        its respective file 
   NUM: When TYPE is "DEF" or "TERM", this is the 
        finding number.  
        When TYPE is "DIALOG", this is the field 
        number in the REMINDER DIALOG file that 
        references the entity.  
        For all other values of TYPE, this 
        subscript does not exist.  
VARIABLES: TMP($J,'DLG FIND')           TYPE: Output
 VARIABLES DESCRIPTION:   The ^TMP($J,"DLG FIND") global subscript is a
 temporary index of dialog findings. Subscribing packages should kill this
 subscript after calling this entry point.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JAN 27, 2016

NUMBER: 6341                            IA #: 6341
  DATE CREATED: JAN 06, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORBSMART
  NAME: NOTIFICATIONS API               ID: ORBSMART
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 access to notification-related entry points.  
  
 REVISION: 10/2/23 - Added line tag EN 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NOTIFICATION IEN
COMPONENT/ENTRY POINT: $$GETNOTID(ORNOTNM)
 COMPONENT DESCRIPTION:   This entry point returns the internal entry number
 (IEN) of the selected notification in the OE/RR NOTIFICATIONS file.  
VARIABLES: ORNOTNM                      TYPE: Input
 VARIABLES DESCRIPTION:   The name of the notification.  
VARIABLES: $$GETNOTID                   TYPE: Output
 VARIABLES DESCRIPTION:   The IEN of the selected notification. If the
 notification does not exist, an empty string is returned.  
COMPONENT/ENTRY POINT: OUTSMALRT
 COMPONENT DESCRIPTION:   Clear out a SMART that is being processed and in the 
 ^TMP("ORSMART CURRENT ALERT") 
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This entry point is used to determine to clear an
 alert or to create a new entry in the SCHEDULED ALERT file, file# 100.97.  
VARIABLES: ORDATA                       TYPE: Input
 VARIABLES DESCRIPTION:   This passed by reference defines the action the entry
 point EN takes with the passed in data. The format for the ORDATA array is: 
 ORDATA("DATA",FN)="" where FN is the file number can be set to either 100.9 or
 100.97.  
  
 Structure of ORDATA where FN = 100.9 ORDATA("DFN")=DFN, where DFN is the
 patient DFN from file 2 ORDATA("DATA",100.9,"MASTER ID")=ID where ID is the
 entry ID for the alert.  ORDATA("DATA",100.9,ID,.01)=IEN is the notification
 IEN from file 100.9 ORDATA("DATA",100.9,ID,"ACTION")=ACTION where action is
 one of the following values: CLEAR PROVIDER = clear all instance of the
 notification IEN for the patient for the current user CLEAR ALL = clear all
 instance of the notification IEN for the patient for all users.  CLEAR ONE =
 only clear the single instance of the notification based off the XQAID value
 associated with the alert for all user 
  
 Structure of ORDATA where FN =100.97 ORDATA("DFN")=DFN is the patient DFN from
 file 2 ORDATA("DATA",100.97,"+1,",2)=WHEN is the FileMan date/time when the 
 scheduled alert should be fired ORDATA("DATA",100.97,"+1,",5)=TITLE is the
 free text value that should appear in the alert 
 ORDATA("DATA",100.97,"+1,",6)=BODY is the free text value that should appear
 in CPRS 
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   ORY(1)=SUCCESS where success is either a 1 or 0 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
  DATE ACTIVATED: OCT 02, 2023

NUMBER: 6342                            IA #: 6342
  DATE CREATED: JAN 06, 2016            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: %ZOSVKSD
  NAME: Kernel-Storage API              ID: %ZOSVKSD
 GENERAL DESCRIPTION:   This API documents the callable APIs in the Kernel
 routine %ZOSVKSD used for OS specific calls on behalf of VistA Capacity
 Planning software. The purpose of this routine is to gather storage metrics.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Entry point used by Statistical Analysis of Global
 Growth (SAGG) to determine volume size for all mounted databases.  
VARIABLES: SITENUM                      TYPE: Input
 VARIABLES DESCRIPTION:   Station number of site.  
VARIABLES: SESSNUM                      TYPE: Input
 VARIABLES DESCRIPTION:   SAGG session number - equals the current date in $H
 format.  
VARIABLES: os
VARIABLES: OS                           TYPE: Input
 VARIABLES DESCRIPTION:   Type of M platform (CVMS, CWINNT).  
COMPONENT/ENTRY POINT: KMPVVSTM
 COMPONENT DESCRIPTION:   This entry point provides the Maximum Size, Current
 Size, Block Size, Blocks per Map, Free Space, System DB flag and Expansion
 Size for each mounted database.  
VARIABLES: KMPVDATA                     TYPE: Both
 VARIABLES DESCRIPTION:   Name of array passed by reference and used to hold
 data provided by the API.  
COMPONENT/ENTRY POINT: os
SUBSCRIBING PACKAGE: SAGG PROJECT
SUBSCRIBING PACKAGE: VISTA SYSTEM MONITOR
  DATE ACTIVATED: JAN 13, 2016

NUMBER: 6343                            IA #: 6343
  DATE CREATED: JAN 06, 2016            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: %ZOSVKSE
  NAME: Kernel Global Size APIs         ID: %ZOSVKSE
 GENERAL DESCRIPTION:   This API documents the callable APIs in the Kernel
 routine %ZOSVKSE used for OS specific calls on behalf of VistA Capacity
 Planning software. The purpose of this routine is to gather storage metrics
 related to VistA globals.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: START
 COMPONENT DESCRIPTION:   Entry point used by SAGG routines to collect global
 metrics on a per volume basis.  
VARIABLES: KMPSTEMP                     TYPE: Input
 VARIABLES DESCRIPTION:   "^" Delimited string containing the following: piece
 1: SiteNumber piece 2: SessionNumber piece 3: XTMP Global Location piece 4:
 Current Date/Time piece 5: Production UCI piece 6: Volume Set 
SUBSCRIBING PACKAGE: SAGG PROJECT
  DATE ACTIVATED: JAN 13, 2016

NUMBER: 6344                            IA #: 6344
  CUSTODIAL PACKAGE: LAB SERVICE        USAGE: Supported
  NAME: x

NUMBER: 6345                            IA #: 6345
  DATE CREATED: JAN 06, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: YTQGMTS
  NAME: Mental Health Instrument Listbox API
  ID: YTQGMTS
 GENERAL DESCRIPTION:   API to appropriately filter Mental Health instruments.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SEL
 COMPONENT DESCRIPTION:   Returns a list of mental health instruments that are
 scorable and active.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: JAN 20, 2016

NUMBER: 6346                            IA #: 6346
  FILE NUMBER: 800                      GLOBAL ROOT: PXRM(800,
  DATE CREATED: JAN 07, 2016            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: REMINDER MANAGEMENT MAILGROUP
  ID: PXRM(800,
GLOBAL REFERENCE: PXRM(800,
FIELD NUMBER: 3
  FIELD NAME: REMINDER MANAGEMENT MAILGROUP
  LOCATION: MGFE;1                      ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   PCE PATIENT CARE ENCOUNTER would like to access the
 REMINDER MANAGEMENT MAILGROUP (#800, #3) so that we can send MailMan messages
 to the mailgroup defined in that field.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: REMINDER MANAGEMENT MAILGROUP
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  DATE ACTIVATED: MAR 29, 2016

NUMBER: 6347                            IA #: 6347
  DATE CREATED: JAN 12, 2016            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSJ53P46
  NAME: PSJ53P46                        ID: PSJ53P46
 GENERAL DESCRIPTION:   This API is provided to return the NUMBER OF DAYS field
 (#1), AUTO-DC IMO ORDERS field (#2), SEND TO BCMA? field (#3), IMO DC/EXPIRED
 DATE LIMIT field (#6), PRE-EXCHANGE REPORT DEVICE field (#5) and MISSING DOSE
 field (#4) from the CLINIC DEFINITION file (#53.46).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ALL(PSJIEN,LIST)
VARIABLES: PSJIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   PSJIEN = IEN of CLINIC from the HOSPITAL 
          LOCATION file (#44) 
          [REQUIRED] 
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   LIST = Subscript of ^TMP array in the 
        form ^TMP($J,LIST,Field Number) 
        Where Field Number is the FileMan 
        data dictionary field number 
        of the data being returned.  
        [REQUIRED] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0) =  1 for successful 
                    return of data 
                   -1^NO CLINIC SPECIFIED 
                   -1^NO DATA FOUND 
  
 ^TMP($J,LIST,1) = NUMBER OF DAYS UNTIL 
                   STOP field (#1) 
                   Internal format ^ 
                   External format 
  
 ^TMP($J,LIST,2) = AUTO-DC IMO ORDERS 
                   field (#2) 
                   Internal format ^ 
                   External format 
  
 ^TMP($J,LIST,3) = SEND TO BCMA? 
                   field (#3) 
                   Internal format ^ 
                   External format 
  
 ^TMP($J,LIST,4) = MISSING DOSE PRINTER 
                   field (#4) 
                   Internal format ^ 
                   External format 
  
 ^TMP($J,LIST,5) = PRE-EXCHANGE REPORT 
                   DEVICE field (#5) 
                   Internal format ^ 
                   External format 
  
 ^TMP($J,LIST,6) = IMO DC/EXPIRED DAY 
                   LIMIT field (#6) 
                   Internal format ^ 
                   External format 
  DATE ACTIVATED: JAN 22, 2016

NUMBER: 6348                            IA #: 6348
  DATE CREATED: JAN 26, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQPL4 LEX
  REMOTE PROCEDURE: ORQQPL4 LEX
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform UI calls the RPC
 ORQQPL4 LEX in order to retrieve an indefinite list of terms that match the
 user's search string.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: ORQQPL4 LEX
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: APR 05, 2016

NUMBER: 6349                            IA #: 6349
  FILE NUMBER: 771.5                    GLOBAL ROOT: HL(771.5
  DATE CREATED: FEB 02, 2016            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Modify HL7 Version File
  ID: HL(771.5
GLOBAL REFERENCE: HL(771.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: VERSION
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 2                         FIELD NAME: STANDARD
  LOCATION: 0;2                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   Check for existence of version 2.6 in the HL7 VERSION
 (771.5) File. If it is missing add via call to FILE^DICN during the package
 pre-installation routine. The following entries will be added: 
   .01   VERSION       2.6 
     2   STANDARD      HEALTH LEVEL SEVEN 
  
 This ICR is temporary and only applicable to IB*2.0*547. The changes will be
 overwritten by HL*1.6*164. It will be retired when the patch has been
 nationally released and the compliance window and warranty periods have
 elapsed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAR 02, 2016

NUMBER: 6350                            IA #: 6350
  FILE NUMBER: 771.2                    GLOBAL ROOT: HL(771.2
  DATE CREATED: FEB 02, 2016            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Modify HL7 Message Type File
  ID: HL(771.2
GLOBAL REFERENCE: HL(771.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ABBREVIATED NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 2                         FIELD NAME: FULL NAME
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 3                         FIELD NAME: VERSION
  LOCATION: V;0                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   Check for existence of Message Type EHC in the HL7
 MESSAGE TYPE (771.2) File. If it is missing add via call to FILE^DICN during
 the package pre-installation routine. The following entries will be added: 
        .01      ABBREVIATED NAME     EHC 
        2        FULL NAME            Health Care Invoice 
        3        VERSION              2.6 
  
 This ICR is temporary and only applicable to IB*2.0*547. The changes will be
 overwritten by HL*1.6*164. It will be retired when the patch has been 
 nationally released and the compliance window and warranty periods have 
 elapsed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAR 02, 2016

NUMBER: 6351                            IA #: 6351
  FILE NUMBER: 779.001                  GLOBAL ROOT: HL(779.001
  DATE CREATED: FEB 02, 2016            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Modify the HL7 Event Type Code File
  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
FIELD NUMBER: 100                       FIELD NAME: VERSION
  LOCATION: 1;0                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   Check for existence of Event Type Code E12 in the HL7
 EVENT TYPE CODE ( 779.001) File.  If it is missing add via call to FILE^DICN
 during the package pre-installation routine. The following entries will be
 added: 
        .01      CODE                 E12 
        2        DESCRIPTION          Request Additional Information 
        100      VERSION              2.6 
  
 This ICR is temporary and only applicable to IB*2.0*547. The changes will be
 overwritten by HL*1.6*164. It will be retired when the patch has been 
 nationally released and the compliance window and warranty periods have 
 elapsed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAR 02, 2016

NUMBER: 6352                            IA #: 6352
  FILE NUMBER: 779.005                  GLOBAL ROOT: HL(779.005
  DATE CREATED: FEB 02, 2016            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Modify the HL7 Message Structure Code File
  ID: HL(779.005
GLOBAL REFERENCE: HL(779.005,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
FIELD NUMBER: 3                         FIELD NAME: VERSION
  LOCATION: 1;0                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   Check for existence of Message Structure Code EHC_E12
 in the HL7 MESSAGE STRUCTURE CODE (779.005) File. If it is missing add via
 call to FILE^DICN during the package pre-installation routine. The following
 entries will be added: 
        .01      CODE                 EHC_E12 
        2        DESCRIPTION          E12 
        3        VERSION              2.6 
  
 This ICR is temporary and only applicable to IB*2.0*547. The changes will be
 overwritten by HL*1.6*164. It will be retired when the patch has been 
 nationally released and the compliance window and warranty periods have 
 elapsed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAR 02, 2016

NUMBER: 6353                            IA #: 6353
  FILE NUMBER: 2005.2                   GLOBAL ROOT: MAG(2005.2
  DATE CREATED: FEB 08, 2016            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: SCHEDULING BSE LOOKUP IN NETWORK LOCATION FILE
  ID: MAG(2005.2
GLOBAL REFERENCE: MAG(2005.2,D0,0)
FIELD NUMBER: 1                         FIELD NAME: PHYSICAL REFERENCE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the physical network location where the
 connection data is stored for Single Sign On.  For example: 
    http://siteserver. http://vista.url//VistaWebSvcs/ExchangeSiteService 
 GLOBAL DESCRIPTION:   
  This file will contain an entry for every network storage location, as well
 as MUSE (EKG) network location(s). This file maps logical device names to
 physical device names, allowing continued operation even when network storage
 devices are down. The Imaging site parameters has a number of fields pointing
 to this file to locate where on the network different files are written.
 Because the Imaging System operates in a distributed environment, an object
 may be stored on one or more of the network storage devices.  These include
 multiple magnetic file servers, one or more optical jukeboxes, and possibly
 additional network devices accessed through a gateway.  
 GENERAL DESCRIPTION:   VistA Scheduling GUI Enhancement (VS GUI) patch
 SD*5.3*642 requests the ability to do a lookup of the PHYSICAL REFERENCE field
 #1 within the NETWORK LOCATION file (#2005.2) using FileManager.  This value
 will be passed back to VS GUI in order to obtain values to support Single Sign
 On (SSO) using the Broker Security Enhancement (BSE) lookup.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: MAR 07, 2016

NUMBER: 6354                            IA #: 6354
  DATE CREATED: FEB 12, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DGPF ASSIGN FLAG
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) is modifying
 the DGPF ASSIGN FLAG Protocol to make it an extended action type protocol and
 adding the HMP DGPF ASSIGN FLAG protocol as an Item under the DGPF ASSIGN FLAG 
 protocol. 
  
 HMP is modifying this protocol that a sync action between VistA and the JDS
 system will occur when a patient's Patient Record Flags are added or edited. 
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: DGPF ASSIGN FLAG
KEYWORDS: HMP DGPF ASSIGN FLAG
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: MAY 12, 2016

NUMBER: 6355                            IA #: 6355
  DATE CREATED: FEB 12, 2016            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Other
  NAME: SCMC PATIENT TEAM CHANGES
 GENERAL DESCRIPTION:   The Electronic Health MGMT Platform (HMP) is modifying
 the SCMC PATIENT TEAM CHANGES Protocol to add the HMP PCMM TEAM POSTION
 Protocol as an Item to the SCMC PATIENT TEAM CHANGES Protocol. Adding the HMP
 PCMM TEAM POSITION as an Item will trigger a sync action between VistA and JDS 
 whenever the Patient Team Assignment File (#404.42) is updated. 
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 If HMP is reactivated in the future, this ICR should be discussed with PCMM
 Web team to confirm the HMP protocols attached to the SCMC PATIENT TEAM
 CHANGES and SCMC PATIENT TEAM POSITION CHANGES protocols provide the necessary
 data for HMP.  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: SCMC PATIENT TEAM CHANGES
KEYWORDS: HMP
KEYWORDS: HMP PCMM TEAM
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   ICR #6355 documents adding HMP PCMM TEAM POSITION to
 SCMC PATIENT TEAM CHANGES protocol. ICR #6356 documents adding HMP PCMM TEAM
 protocol to SCMC PATIENT TEAM POSITION CHANGES protocol. It was originally
 thought the SCMC protocols would not be used by the PCMM Web application.  On 
 9/30/16 Andy Thompson from PCMM said he can see where these protocols are used
 by VistA.  As part of syncing data back to VistA, PCCM Web calls the SC PAT
 ASGN MAILMAN RPC to create Mailman messages regarding patient team and team
 position changes. Which in turn fires the protocols referenced in the ICRs
 6355 & 6356. The HMP protocols would be fired as well.  
  
 Email discussion also asked about the frequency the SC PAT ASGN MAILMAN RPC is
 called. PCMM said Team synchronization with VistA is limited right now to once
 every 8 hour per team. It is not real-time. For each synchronization RPC may
 be invoked zero or more times - it depends on data. If there are errors,
 synchronization may be run more than once before it completes. When user
 actively manages team, especially if they perform batch operations on it, you
 may get hundreds or even thousands of invocations (if team is large) per team
 synchronization.  Unfortunately PCMM does not track frequency of invocation of
 this RPC, so better numbers  cannot be provided.  
  
 With some exceptions for secondary data sources, eHMP aims for near realtime
 (<5s) updates. If 8-hours is the maximum delay, or if we expect that delay to
 decrease over time, this might be the best short-term option to continue
 displaying team assignment data.  
  
 HMP logged US14732 user story to track this issue.  

NUMBER: 6356                            IA #: 6356
  DATE CREATED: FEB 12, 2016            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Other
  NAME: SCMC PATIENT TEAM POSITION CHANGES
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) is adding the
 HMP PCMM TEAM POSITION Protocol as an Item under the SCMC PATIENT TEAM
 POSITION CHANGES Protocol. The HMP PCMM TEAM POSITION Protocol will trigger a
 sync action between VistA and JDS whenever the Patient Team Position
 Assignment File (#404.43) is updated.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 If HMP is reactivated in the future, this ICR should be discussed with PCMM
 Web team to confirm the HMP protocols attached to the SCMC PATIENT TEAM
 CHANGES and SCMC PATIENT TEAM POSITION CHANGES protocols provide the necessary
 data for HMP.  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: SCMC PATIENT TEAM
KEYWORDS: HMP
KEYWORDS: HMP PCMM TEAM POSITION
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   ICR #6355 documents adding HMP PCMM TEAM POSITION to
 SCMC PATIENT TEAM CHANGES protocol. ICR #6356 documents adding HMP PCMM TEAM
 protocol to SCMC PATIENT TEAM POSITION CHANGES protocol. It was originally
 thought the SCMC protocols would not be used by the PCMM Web application.  On 
 9/30/16 Andy Thompson from PCMM said he can see where these protocols are used
 by VistA.  As part of syncing data back to VistA, PCCM Web calls the SC PAT
 ASGN MAILMAN RPC to create Mailman messages regarding patient team and team
 position changes. Which in turn fires the protocols referenced in the ICRs
 6355 & 6356. The HMP protocols would be fired as well.  
  
 Email discussion also asked about the frequency the SC PAT ASGN MAILMAN RPC is
 called. PCMM said Team synchronization with VistA is limited right now to once
 every 8 hour per team. It is not real-time. For each synchronization RPC may
 be invoked zero or more times - it depends on data. If there are errors,
 synchronization may be run more than once before it completes. When user
 actively manages team, especially if they perform batch operations on it, you
 may get hundreds or even thousands of invocations (if team is large) per team
 synchronization.  Unfortunately PCMM does not track frequency of invocation of
 this RPC, so better numbers  cannot be provided.  
                          
 With some exceptions for secondary data sources, eHMP aims for near realtime
 (<5s) updates. If 8-hours is the maximum delay, or if we expect that delay to
 decrease over time, this might be the best short-term option to continue
 displaying team assignment data.  
                          
 HMP logged US14732 user story to track this issue.  
  
 HMP project will be shutting down as of 10/27/17.  If HMP is reactivated in
 the future, this ICR should be discussed with PCMM Web team to confirm the HMP
 protocols attached to the SCMC PATIENT TEAM CHANGES and SCMC PATIENT TEAM
 POSITION CHANGES protocols provide the necessary data for HMP.  

NUMBER: 6357                            IA #: 6357
  FILE NUMBER: 120.83                   GLOBAL ROOT: GMRD(120.83
  DATE CREATED: FEB 17, 2016
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: GMRD(120.83
  ID: GMRD(120.83
GLOBAL REFERENCE: GMRD(120.83,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   A sign or symptom that can be associated with an allergy. 
 
FIELD NUMBER: 99.99                     FIELD NAME: VUID
  LOCATION: VUID;1                      ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   VHA Unique ID (VUID). A unique meaningless integer
 assigned to reference terms VHA wide.  
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) is accessing
 the SIGNS/SYMPTOMS File (#120.83) to retrieve a list of all the Signs/Symptoms
 in the file.  
  
 HMP is looping thru the file and pulling the IEN and the Name (.01) in order
 to use this data to update the JDS database system that stores all the patient
 data used by HMP.  
  
 NOTE:  ICR #6357 was retired on 6/16/17 with the release of HMP*2*3.  
 References to the Signs/Symptoms (#120.83) file and associated code was 
 removed from HMP with this patch.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2016
KEYWORDS: GMRD(120.83
KEYWORDS: 120.83
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: MAR 30, 2016

NUMBER: 6358                            IA #: 6358
  FILE NUMBER: 100.98                   GLOBAL ROOT: ORD(100.98
  DATE CREATED: FEB 18, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ORD(100.98
  ID: ORD(100.98
GLOBAL REFERENCE: ORD(100.98,'B'
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The name of the display group.  
GLOBAL REFERENCE: ORD(100.98,DA
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Name of the display group.  
FIELD NUMBER: 2                         FIELD NAME: MIXED NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains a mixed case name for the display
 group.  
FIELD NUMBER: 3                         FIELD NAME: SHORT NAME
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The abbreviation for the display group.  
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) accesses the
 DISPLAY GROUP File (#100.98) to retrieve a current list of Display Groups to
 update the JDS database system used by the eHMP software. 
  
 HMP does direct global reads of the ORD(100.98 "B" cross reference in order to
 lookup the Display Group for Pharmacy and Nursing Treatment orders. This data
 is then used by HMP during the initial patient sync process that uploads this
 data to the JDS database. 
  
 HMP also loops thru the file using a direct global read and $Order to retrieve
 a list of all Display Groups. As each record is read, the HMP process collects
 the record IEN, Name, Mixed Name and Short Name to send to JDS.  
  
 ** NOTE: Access to this file for direct reads will only be granted to the HMP
 project. ** 
  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: ORD(100.98
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: MAR 14, 2016

NUMBER: 6359                            IA #: 6359
  DATE CREATED: FEB 18, 2016            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDAMA308
  NAME: HMP USE OF STATUS~SDAMA308      ID: SDAMA308
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) requests to
 use the STATUS^SDAMA308 API in order to retrieve the status of a patient 
 appointment. 
  
 HMP is retrieving this information along with other information about a 
 patient's appointments and syncing this data with the HMP JDS database system. 
  
 This is a temporary agreement until the HMP application can switch from using
 STATUS~SDAMA308 to SDAPI~SDAMA301 documented in ICR #4433.  Expiration date is
 set for 1/1/17.  
  
  
 10/24/17-ICR has been retired and expiration date changed to 6/16/17 to match
 the release date for HMP*2.0*3.  The patch description references DE4469 and
 use of SDAMA308 API.  Search of HMP routines found a commented line at
 SDAM1+12 in routine HMPDJ04 noting the change from SDAMA308 API to supported
 SDAMA301 API (ICR #4433).  No other reference to routine SDAMA308 in HMP
 routines. HMP will be shutdown as of 10/27/17.  If HMP is reactivated in the
 future and this ICR is needed, the ICR should be reviewed by the custodial
 application for approval.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JUN 16, 2017
KEYWORDS: SDAMA308
COMPONENT/ENTRY POINT: STATUS
 COMPONENT DESCRIPTION:   This API returns appointment status information.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient DFN.  
VARIABLES: SDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The appointment date and time in FileMan format.  
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the location in the Hosptial Location
 File (#44).  
VARIABLES: STS                          TYPE: Output
 VARIABLES DESCRIPTION:   Array containing the data elements below: 
  
 appointment status IFN ; Status Name ; Print Status ; Check In Date/Time ;
 Check Out Date/Time ; Admission Movement IFN 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: APR 20, 2016

NUMBER: 6360                            IA #: 6360
  FILE NUMBER: 120.51                   GLOBAL ROOT: GMRD(120.51
  DATE CREATED: FEB 18, 2016
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Supported                      TYPE: File
  NAME: NDS associated fields           ID: GMRD(120.51
 GENERAL DESCRIPTION:   Implement the native standardization LOINC for file
 #120.51 Vital Signs 
  terminology domain GMRV VITAL TYPE file (#120.51) 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: NDS
KEYWORDS: VITALS
KEYWORDS: VITAL SIGNS

NUMBER: 6361                            IA #: 6361
  FILE NUMBER: 120.52                   GLOBAL ROOT: GMRD(120.52
  DATE CREATED: FEB 18, 2016
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Supported                      TYPE: File
  NAME: NDS Associated Fields           ID: GMRD(120.52
 GENERAL DESCRIPTION:   Implement the native standardization for SNOMED CT for
 file #120.52 for the 
  Vital Signs terminology domain GMRV VITAL QUALIFIER file (#120.52).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: NDS
KEYWORDS: VITALS
KEYWORDS: VITAL SIGNS

NUMBER: 6362                            IA #: 6362
  FILE NUMBER: 120.53                   GLOBAL ROOT: gmrd(120.53
  DATE CREATED: FEB 18, 2016
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Supported                      TYPE: File
  NAME: NDS associated fields           ID: gmrd(120.53
 GENERAL DESCRIPTION:   Implement the native standardization SNOMED CT for file
 #120.53 for the 
  Vital Signs terminology domain GMRV VITAL CATEGORY file (#120.53).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: NDS
KEYWORDS: VITALS
KEYWORDS: VITAL SIGNS

NUMBER: 6363                            IA #: 6363
  FILE NUMBER: 19.2                     GLOBAL ROOT: DIC(19.2
  DATE CREATED: FEB 19, 2016            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: REMOVE SCHEDULED OPTION FROM #19.2
  ID: DIC(19.2
 GENERAL DESCRIPTION:   In Prosthetics package, the Patient Notification Letter
 project was terminated, but there were options/routines already sent out via
 patch RMPR*3.0*125. One of the options 'RMPR DVN NIGHTLY JOB' was directed to 
 be set as a nightly job in Taskman.  
  
 We have been directed to remove this option from the option file as well as
 four remaining routines (RMPRDVN, RMPRDVN1, RMPRDVN2 & RMPRDVN3) be deleted.  
  
 Since the option is being removed and may have been tasked at various sites,
 we want to insure that this task is removed from Taskman in a pre-install run
 prior to deleting the option during the install.  The pre-install routine
 (RMPRTDEL) will be deleted immediately after execution as part of the build.  
  
 This ICR is only valid for RMPR*3.0*180.  
  STATUS: Pending
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   This request is for patch RMPR*3.0*180.  See details in
 General Description.  

NUMBER: 6364                            IA #: 6364
  FILE NUMBER: 120.53                   GLOBAL ROOT: GMRD(120.53,
  DATE CREATED: FEB 19, 2016
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HMP ACCESS TO GMRD(120.53
  ID: GMRD(120.53,
GLOBAL REFERENCE: GMRD(120.53,DA
FIELD NUMBER: .01                       FIELD NAME: CATEGORY
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field provides a list of qualitieds that could be
 used assigned to a given vital measurement record.  
GLOBAL REFERENCE: GMRD(120.53,D0,1,D1
FIELD NUMBER: .01                       FIELD NAME: VITAL TYPE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field screens the vital measurement quality field in
 the GMRV VITAL MEASUREMENT file (#120.5).  
FIELD NUMBER: .03                       FIELD NAME: MAXIMUM ENTRIES
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field indicates the minimum number of
 characteristics that can be selected for a patient for this category for this
 vital type.  
FIELD NUMBER: .05                       FIELD NAME: PRINT ORDER
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the order in which this category of
 characteristics will display on the reports for this category for this vital
 type.  
FIELD NUMBER: .06                       FIELD NAME: EDIT ORDER
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the order in which this category for
 this vital type will be entered/edited in the Vitals/Measurements edit
 options.  
FIELD NUMBER: .07                       FIELD NAME: DEFAULT QUALIFIER
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field will denote the default qualifier to be used
 if the user does not specify one during data entry.  
GLOBAL REFERENCE: GMRD(120.53,D0,'TERMSTATUS',D1
FIELD NUMBER: .01                       FIELD NAME: EFFECTIVE DATE/TIME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the date/teim when the Status of the reference
 term was established 
FIELD NUMBER: .02                       FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The Status of a reference term is either 'ACTIVE' or
 'INACTIVE'. If 'ACTIVE', then the term will be accessible by end-users to
 document a particular patient event. if 'INACTIVE', then the term will only be 
 accessible by the application to display legacy data.  
GLOBAL REFERENCE: GMRD(120.53,DO,VUID
FIELD NUMBER: 99.99                     FIELD NAME: VUID
  LOCATION: VUID;1                      ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the VHA Unique ID (VUID). A unique meaningless
 integer assigned to the reference terms VHA wide.  
FIELD NUMBER: 99.98                     FIELD NAME: MASTER ENTYR FOR VUID
  LOCATION: VUID;2                      ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field identifies the Master entry for a VUID
 associated with a Term/Concept.  
 GENERAL DESCRIPTION:   The Electronic Health MGMT Platform (HMP) is making
 direct global reads of the GMRV VITAL CATEGORY File (#120.53) in order to
 retrieve all the data in the file. HMP is syncing this file and the data it
 contains between the local VistA system and the JDS database system. 
  
 HMP is using a $ORDER to loop thru the file to pull all the data and send it
 to JDS.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
KEYWORDS: GMRD(120.53
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: MAR 23, 2016

NUMBER: 6365                            IA #: 6365
  FILE NUMBER: 120.52                   GLOBAL ROOT: GMRD(120.52
  DATE CREATED: FEB 19, 2016
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HMP ACCESS TO GMRD(120.52
  ID: GMRD(120.52
GLOBAL REFERENCE: GMRD(120.52,D0
FIELD NUMBER: .01                       FIELD NAME: QUALIFIER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field supplies a list of possible qualifiers for a
 vital measurement record.  
FIELD NUMBER: .02                       FIELD NAME: SYNONYM
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the synonym for the qualifier.  
GLOBAL REFERENCE: GMRD(120.52,D0,1,D1
FIELD NUMBER: .01                       FIELD NAME: VITAL TYPE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field screens the vital measurement site field in
 the GMRV VITAL MEASUREMENT (#120.5) file.  
FIELD NUMBER: .02                       FIELD NAME: CATEGORY
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field will contain the category for this
 characteristic for this vital type.  
GLOBAL REFERENCE: GMRD(120.52,D0,'TERMSTATUS',D1
FIELD NUMBER: .01                       FIELD NAME: EFFECTIVE DATE/TIME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the date/time when the Status of the reference
 term was established.  
FIELD NUMBER: .02                       FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The Status of a reference term is either 'ACTIVE' or
 'INACTIVE'. If 'ACTIVE', then the term will be accessable by end-users to
 document a particular patient event. If 'INACTIVE', then the term will only be 
 accessible by the application to display legacy data.  
GLOBAL REFERENCE: GMRD(120.52,D0,'VUID'
FIELD NUMBER: 99.99                     FIELD NAME: VUID
  LOCATION: VUID;1                      ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   VHA Unique ID (VUID). A unique meaningless integer
 assigned to reference terms VHA wide.  
FIELD NUMBER: 99.98                     FIELD NAME: MASTER ENTRY FOR VUID
  LOCATION: VUID;2                      ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field identifies the Master entery for a VUID
 associated with a Term/Concept.  
 GENERAL DESCRIPTION:   The Electronic Health MGMT Platform (HMP) is making
 direct global reads of the GMRC VITAL QUALIFIER File (#120.52) in order to
 retrieve all the data in teh file. HMP syncs a copy of the local file with the
 JDS database system used by the eHMP interface. 
  
 HMP is using a $ORDER to loop thru the file to pull all the data and send it
 to JDS.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
KEYWORDS: GMRD(120.52
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: MAR 23, 2016

NUMBER: 6366                            IA #: 6366
  FILE NUMBER: 120.51                   GLOBAL ROOT: GMRD(120.51,D0,1
  DATE CREATED: FEB 19, 2016
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HMP ACCESS TO GMRD(120.51
  ID: GMRD(120.51,D0,1
GLOBAL REFERENCE: GMRD(120.51,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field reflects a list of vital signs/physical
 measurement types.  
FIELD NUMBER: 1                         FIELD NAME: ABBREVIATION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains an abbreviation for this vital type.  
FIELD NUMBER: 3                         FIELD NAME: RATE
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field specifies whether or not the vital measurement
 record with this vital type has a rate associated with it.  
FIELD NUMBER: 7                         FIELD NAME: PCE ABBREVIATION
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field contains the PCE Abbreviation for this Vital
 Type.  
GLOBAL REFERENCE: GMRD(120.51,D0,1
FIELD NUMBER: 4                         FIELD NAME: RATE INPUT TRANSFORM
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   If a rate is specified for a vital measurement record,
 this field checks the data validity.  
GLOBAL REFERENCE: GMRD(120.51,D0,'TERMSTATUS'
FIELD NUMBER: .01                       FIELD NAME: EFFECTIVE DATE/TIME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the date/time when the Status of the reference
 term was established.  
FIELD NUMBER: .02                       FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   The Status of a reference term is either 'ACTIVE' or
 'INACTIVE'. If 'ACTIVE', then the term will be accessIble by end-users to
 document a particular patient event. If 'INACTIVE', then the term will only be 
 accessible by the application to display legacy data.  
GLOBAL REFERENCE: GMRD(120.51,D0,VUID
FIELD NUMBER: 99.99                     FIELD NAME: VUID
  LOCATION: VUID;1                      ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   VHA Unique ID (VUID). A unique meaningless integer
 assigned to reference terms VHA wide.  
FIELD NUMBER: 99.98                     FIELD NAME: MASTER ENTRY FOR VUID
  LOCATION: VUID;2                      ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field identifies the Master entry for a VUID
 associated with a Term/Concept.  
 GENERAL DESCRIPTION:   The Electronic Health MGMT Platform (HMP) is accessing
 the GMRV VIAL TYPE File (#120.51) using direct global in order to sync the
 local file with the JDS database system used the HMP user interface.  
  
 HMP is using a $ORDER to loop thru the file and pull all data and send the
 data to JDS.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
KEYWORDS: GMRD(120.51
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: MAR 23, 2016

NUMBER: 6367                            IA #: 6367
  FILE NUMBER: 101.41                   GLOBAL ROOT: ORD(101.41
  DATE CREATED: FEB 19, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HMP ACCESS TO ORD(101.41
  ID: ORD(101.41
GLOBAL REFERENCE: ORD(101.41,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the name of the dialog.  
FIELD NUMBER: 2                         FIELD NAME: DISPLAY TEST
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The text of this dialog's name as it appears on a menu or
 subheader.  
FIELD NUMBER: 3                         FIELD NAME: DISABLE
  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 the type of order dialog to be
 processed.  
 GENERAL DESCRIPTION:   The Electronic Health MGMT Platform (HMP) is accessing
 the ORDER DIALOG File (#101.41) using direct global reads to retrieve data
 related to specific order dialogs. HMP syncing this data with the HMP JDS
 database system used by the eHMP user interface.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
KEYWORDS: ORD(101.41
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: MAR 04, 2016

NUMBER: 6368                            IA #: 6368
  FILE NUMBER: 101.42                   GLOBAL ROOT: ORD(101.42
  DATE CREATED: FEB 19, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HMP ACCESS TO ORD(101.42
  ID: ORD(101.42
GLOBAL REFERENCE: ORD(101.42,'S.RA'
 GLOBAL DESCRIPTION:   This cross reference allows retrieval of urgencies
 assigned to a particular usage context.  
GLOBAL REFERENCE: ORD(101.42,'B'
 GLOBAL DESCRIPTION:   This cross reference allows look up of records by
 urgency name.  
 GENERAL DESCRIPTION:   The Electronic Health MGMT Platform (HMP) is accessing
 the ORDER URGENCY File (#101.42) using direct global reads. HMP is looping
 thru the ORD(010.42,"S.RA" cross reference to identify records for the 
 Radiology/Nuclear Medicine usage for the urgency.  
  
 This data passed to the JDS database system used by the eHMP interface. The
 data is collected when the initial sync process syncs data from VistA to JDS
 for any of the HMP data domains. 
  
 **NOTE: HMP is the only package that is allowed this level of access.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12  
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the  access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 *********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
KEYWORDS: ORD(101.42
KEYWORDS: ORDER URGENCY
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: MAR 10, 2016

NUMBER: 6369                            IA #: 6369
  FILE NUMBER: 51.2                     GLOBAL ROOT: PS(51.2
  DATE CREATED: FEB 19, 2016
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HMP ACCESS TO PS(51.2
  ID: PS(51.2
GLOBAL REFERENCE: PS(51.2,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is a route of administration for a medication.  
FIELD NUMBER: 4                         FIELD NAME: OUTPATIENT EXPANSION
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the medication route's expansion to be used in
 the Outpatient Pharmacy.  
FIELD NUMBER: 1                         FIELD NAME: ABBREVIATION
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the abbreviation for the medication route
 entered.  
FIELD NUMBER: 5                         FIELD NAME: INACTIVATION DATE
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the date that the medication route was
 inactivated.  
FIELD NUMBER: 6                         FIELD NAME: IV FLAG
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field shall designate IV medication routes.  
 GENERAL DESCRIPTION:   The Electronic Health MGMT Platform (HMP) is accessing
 the MEDICATION ROUTES File (#51.2) using direct global reads to collect data
 when syncing the HMP data domains during the intial sync for a patient. The 
 sync process syncs data from the local VistA system with the HMP JDS database
 system.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: DEC 31, 2016
KEYWORDS: HMP
KEYWORDS: PS(51.2
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: APR 20, 2016

NUMBER: 6370                            IA #: 6370
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: FEB 23, 2016            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  NAME: HMP ACCESS TO SC(               ID: SC(
GLOBAL REFERENCE: SC(
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the name of the location.  
FIELD NUMBER: 2                         FIELD NAME: TYPE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the code for the type of location.  
GLOBAL REFERENCE: SC('B'
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   HMP loops thru the B cross reference to get all entries
 in the file.  
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) is accessing
 the Hospital Location file (#44) to retrieve a list of all active clinics. HMP
 builds a list containing the IEN for the entry and the Name (.01). HMP loops 
 thru the B cross reference to get each entry, then checks the Type field (2)
 and if the location is designated as a clinic it is added to the list. This
 list is then synced with the HMP JDS database.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: HMP
KEYWORDS: SC(
KEYWORDS: SC('B'
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6371                            IA #: 6371
  DATE CREATED: FEB 24, 2016
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSREF
  NAME: ROUTINE PSSREF                  ID: PSSREF
 GENERAL DESCRIPTION:   The National Drug File makes a call to routine ^PSSREF
 from routine ^PSNPPSNW to create an Activity Log entry in the DRUG file (#50). 
 
  STATUS: Active
KEYWORDS: PSSREF
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
  DATE ACTIVATED: APR 25, 2018

NUMBER: 6372                            IA #: 6372
  DATE CREATED: FEB 24, 2016
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: Routine
  ROUTINE: GMRAUIX0                     NAME: ROUTINE GMRAUIX0
  ID: GMRAUIX0
 GENERAL DESCRIPTION:   The National Drug File makes a call to routine
 ^GMRAUIX0 at line tag EN2. This line tag will set the needed cross reference 
 in the PATIENT ALLERGIES file #120.8.  
  STATUS: Withdrawn
KEYWORDS: GMRAUIX0
COMPONENT/ENTRY POINT: EN2
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE

NUMBER: 6373                            IA #: 6373
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: FEB 24, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  NAME: LOOKUP PATIENTS IN PATIENT FILE
  ID: DPT(
GLOBAL REFERENCE: DPT(D0,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The patient's name.  
GLOBAL REFERENCE: DPT('B',
 GLOBAL DESCRIPTION:   Enables lookup of patients via the B cross-reference.  
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to look up patients in the PATIENT file (#2).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PATIENT FILE
KEYWORDS: DPT GLOBAL
KEYWORDS: PATIENT LOOKUP
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING

NUMBER: 6374                            IA #: 6374
  FILE NUMBER: 445                      GLOBAL ROOT: PRCP(445,
  DATE CREATED: FEB 26, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PROSTHETICS-POINT OF USE-GIP LOOKUP
  ID: PRCP(445,
GLOBAL REFERENCE: PRCP(445,D0,5)
FIELD NUMBER: 22                        FIELD NAME: SS PROVIDER
  LOCATION: [5;1]                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   When an automated supply station stocks items within an
 inventory point, this field contains a pointer to the machine used, allowing
 GIP to correctly build and transmit information to the automated supply 
 station by referencing file 445.5. 
  
 GENERAL DESCRIPTION:   The IFCAP Generic Inventory Package (GIP) provides the
 ability for sites to use Point of Use (POU) supply stations.  An INVENTORY
 POINT (#.01), which is stored and managed in the GENERIC INVENTORY file (#445)
 can be linked to a Point of Use supply station with a pointer from its SS
 PROVIDER field (#22). The SS PROVIDER field points to the AUTOMATED SUPPLY
 STATIONS file (#445.5). When an INVENTORY POINT in file 445 has an entry in
 field 22 that points to an AUTOMATED SUPPLY STATION entry, then the INVENTORY
 POINT is known to be linked to a POU supply cabinet.  These are special
 cabinets that automatically update GIP inventory balances, via HL7 messaging,
 when stock is removed.  
  
 This DBIA gives the Prosthetics package permission to read the SS PROVIDER 
 FIELD (#22) and determine if that field points to a valid entry in the 
 AUTOMATED SUPPLY STATIONS file (#445.5).  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 445.5
KEYWORDS: 445
KEYWORDS: POU
KEYWORDS: POINT OF USE
KEYWORDS: SUPPLY
KEYWORDS: STATION
KEYWORDS: GIP
KEYWORDS: SUPPLY STATION
KEYWORDS: GENERIC INVENTORY
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   The Prosthetics package needs to be able to determine
 if an inventory point is linked to a POU cabinet.  If so, the Prosthetics
 software should not call IFCAP's  PRCPUSA API (DBIA #10085) to update the
 inventory balance when stock is issued as that would result in double posting. 
  
 The Prosthetics package will read the SS PROVIDER field (#22) in the GENERIC
 INVENTORY file (#445) and resolve the pointer to an entry in the AUTOMATED
 SUPPLY STATIONS file (#445.5).  
  
 The PROSTHETICS package will use the following FileMan DBMS call to perform
 this read: 
  
     $$GET1^DIQ(445,inventory point IEN,22) 
  
  
  DATE ACTIVATED: MAR 16, 2016

NUMBER: 6375                            IA #: 6375
  FILE NUMBER: 66.3                     GLOBAL ROOT: LRMLTF
  DATE CREATED: FEB 29, 2016            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Supported                      TYPE: File
  NAME: NDS Laboratory Associated Fields
  ID: LRMLTF
 GENERAL DESCRIPTION:   Implement the standardized Master Laboratory Test with
 the native 
  standardization LOINC code for use in the Laboratory Services Domain.  b 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: MLTF
KEYWORDS: Laboratory

NUMBER: 6376                            IA #: 6376
  DATE CREATED: FEB 29, 2016            CUSTODIAL PACKAGE: ASISTS
  USAGE: Private                        TYPE: Other
  NAME: VA Community Care Access to ASISTS GUI SUPERVISOR
 GENERAL DESCRIPTION:   Responsibility for processing VA Community Care (VACC)
 claims has changed from the VISNs/VAMCs to the Chief Business Office for
 Purchased Care (CBOPC).  As a national program, staff members often require
 access to multiple VistA systems in order to perform their duties.  A VACC 
 Supervisor menu is being created for use as a primary menu in accessing remote
 VistA systems via CAPRI. Besides accessing roll and scroll VistA options the
 supervisors also need to access ASISTS on remote systems through the
 Supervisor GUI.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: VACC
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   VA Community Care staff will be accessing multiple
 VistA systems through telnet functionality provided by CAPRI to support
 processing of community care claims on the remote systems. Patch DVBA*2.7*199
 creates several new role-based menus that will be assigned as the primary menu
 for these users when they access a remote VistA system via CAPRI.  The
 stakeholders have requested that the ASISTS GUI Supervisor Menu (Context)
 [OOPS GUI SUPERVISOR MENU] option be attached to the new VACC supervisor's
 menu to support access to ASISTS by VA Community Care supervisors.  This 
 integration agreement allows OOPS GUI SUPERVISOR MENU to be attached to DVBA
 namespaced menus.  

NUMBER: 6377                            IA #: 6377
  DATE CREATED: FEB 29, 2016            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: VA Community Care Access to Fee Basis Options
 GENERAL DESCRIPTION:   Responsibility for processing VA Community Care (VACC)
 claims has changed from the VISNs/VAMCs to the Chief Business Office for
 Purchased Care (CBOPC).  As a national program, staff members often require
 access to multiple VistA systems in order to perform their duties. Two new, 
 role-based menus General VACC User CAPRI Menu [DVBA VACC GENERAL USER] and
 VACC Supervisor CAPRI Menu [DVBA VACC SUPERVISOR] are being created for use as
 a primary menu in accessing remote VistA systems via CAPRI.  VACC staff need
 to be able to access Fee Basis options on multiple VistA systems for
 processing claims.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VACC
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   VA Community Care staff will be accessing, sometimes as
 visitors, multiple VistA systems through telnet functionality provided by
 CAPRI. When the two new menus are installed by patch DVBA*2.7*199, the Fee
 Basis Main Menu [FBAA MAIN MENU] will be attached to each of the menus. This 
 integration agreement grants permission to make these attachments.  
  DATE ACTIVATED: MAR 14, 2016

NUMBER: 6378                            IA #: 6378
  DATE CREATED: FEB 29, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: VA Community Care Access to Registration Options
 GENERAL DESCRIPTION:   Responsibility for processing VA Community Care (VACC)
 claims has changed from the VISNs/VAMCs to the Chief Business Office for
 Purchased Care (CBOPC).  As a national program, staff members often require
 access to multiple VistA systems in order to perform their duties.  Two new, 
 role-based menus General VACC User CAPRI Menu [DVBA VACC GENERAL USER] and
 VACC Supervisor CAPRI Menu [DVBA VACC SUPERVISOR] are being created for use as
 a primary menu in accessing remote VistA systems via CAPRI.  VACC staff need
 to be able to access some Registration options.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VACC
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   VA Community Care personnel will be accessing multiple
 VistA systems through telnet functionality provided by CAPRI. When the two new
 menus are installed by patch DVBA*2.7*199, Registration options DRG
 Calculation [DG DRG CALCULATION] or View Registration Data [DG REGISTRATION
 VIEW] will be attached to one or more of these menus.  This integration
 agreement grants permission to make these attachments.  
  DATE ACTIVATED: MAR 15, 2016

NUMBER: 6379                            IA #: 6379
  DATE CREATED: MAR 01, 2016            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Other
  NAME: VA Community  Care Access to Imaging
 GENERAL DESCRIPTION:   Responsibility for processing VA Community Care (VACC)
 claims has changed from the VISNs/VAMCs to the Chief Business Office for
 Purchased Care (CBOPC).  As a national program, staff members often require
 access to multiple VistA systems in order to perform their duties.  Four new
 menus are being created for use as a primary menu in accessing remote VistA 
 systems via CAPRI.  VACC staff need to be able to access Imaging in support of
 processing claims.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: VACC
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   VA Community Care staff will be accessing multiple
 VistA systems through telnet functionality provided by CAPRI to support
 processing of community care claims on the remote systems. Patch DVBA*2.7*199
 creates several new role-based menus that will be assigned as the primary menu
 for these users when they access a remote VistA system via CAPRI.  The
 stakeholders have requested that the All MAG* RPC's [MAG WINDOWS] option be
 attached to the new menus to support access to Imaging by the VA Community
 Care staff.  This integration agreement allows All MAG* RPC's [MAG WINDOWS] to 
 be attached to DVBA namespaced menus.  

NUMBER: 6380                            IA #: 6380
  DATE CREATED: MAR 01, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Other
  NAME: VA Community Care Access to CPRSChart
 GENERAL DESCRIPTION:   Responsibility for processing VA Community Care (VACC)
 claims has changed from the VISNs/VAMCs to the Chief Business Office for
 Purchased Care (CBOPC).  As a national program, staff members often require
 access to multiple VistA systems in order to perform their duties.  Four new, 
 role-based menus are being created for use as a primary menu in accessing 
 remote VistA systems via CAPRI.  VACC staff need to be able to access CPRS 
 while processing claims.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: VACC
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   VA Community Care staff will be accessing multiple
 VistA systems through telnet functionality provided by CAPRI.  When the new
 menus are installed by DVBA*2.7*199, CPRSChart version 1.0.30.16 [OR CPRS GUI
 CHART] will be attached to each of these new menus so that they can also
 access CPRS while processing claims.  This integration agreement grants
 permission to make these attachments.  

NUMBER: 6381                            IA #: 6381
  DATE CREATED: MAR 01, 2016
  CUSTODIAL PACKAGE: INSURANCE CAPTURE BUFFER
  USAGE: Private                        TYPE: Other
  NAME: VA Community Care Access to Insurance Capture Buffer
 GENERAL DESCRIPTION:   Responsibility for processing VA Community Care (VACC)
 claims has changed from the VISNs/VAMCs to the Chief Business Office for
 Purchased Care (CBOPC).  As a national program, staff members often require
 access to multiple VistA systems in order to perform their duties.  Four new, 
 role-based menus are being created for use as a primary menu in accessing 
 remote VistA systems via CAPRI.  VACC staff need to be able to access 
 documents in Insurance Capture Buffer while processing claims.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: VACC
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   VA Community Care staff will be accessing multiple
 VistA systems through telnet functionality provided by CAPRI.  When the four
 new menus are installed by patch DVBA*2.7*199, DSS DocManager Imaging System
 [DSIV DOCMANAGER] will be attached to each of these new menus.  This 
 integration agreement grants permission to make these attachments.  

NUMBER: 6382                            IA #: 6382
  DATE CREATED: MAR 01, 2016
  CUSTODIAL PACKAGE: FEE BASIS CLAIMS SYSTEM
  USAGE: Private                        TYPE: Other
  NAME: VA Community Care Access to Fee Basis Claims System
 GENERAL DESCRIPTION:   Responsibility for processing VA Community Care (VACC)
 claims has changed from the VISNs/VAMCs to the Chief Business Office for
 Purchased Care (CBOPC).  As a national program, staff members often require
 access to multiple VistA systems in order to perform their duties.  Four new, 
 role-based menus are being created for use as a primary menu in accessing 
 remote VistA systems via CAPRI.  VACC staff need to be able to use the Fee 
 Basis Claims System (FBCS) connected to different VistA systems in order to
 process claims.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: VACC
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   VA Community Care staff will be accessing multiple
 VistA systems through telnet functionality provided by CAPRI.  They will also
 be logging onto FBCS to process claims on multiple VistA systems.  When the
 four new menus are installed by patch DVBA*2.7*199, FBCS options Fee Basis
 Broker Calls [DSIF FEEBASIS] and Fee Basis Payments [DSIF FEEBASIS PAYMENT]
 will be attached to each of these menus.  This integration agreement grants 
 permission to make these attachments.  

NUMBER: 6383                            IA #: 6383
  FILE NUMBER: 162                      GLOBAL ROOT: FBAAC
  DATE CREATED: MAR 03, 2016            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IB ACCESS TO FB #162
  ID: FBAAC
GLOBAL REFERENCE: FBAAC(D0,1,D1,1,D2,1,0)
FIELD NUMBER: 2                         FIELD NAME: SERVICE PROVIDED
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAC(D0,1,D1,1,D2,1,D3,0)
FIELD NUMBER: .01                       FIELD NAME: SERVICE PROVIDED
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: AMOUNT PAID
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: FEE PROGRAM
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 26                        FIELD NAME: PRIMARY SERVICE FACILITY
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 27                        FIELD NAME: ASSOCIATED 7078/583
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: DATE PAID
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: INVOICE NUMBER
  LOCATION: 0;16                        ACCESS: Read w/Fileman
FIELD NUMBER: 16                        FIELD NAME: PURPOSE OF VISIT
  LOCATION: 0;18                        ACCESS: Read w/Fileman
FIELD NUMBER: 28                        FIELD NAME: PRIMARY DIAGNOSIS
  LOCATION: 0;23                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAC(D0,1,D1,1,D2,1,D3,3)
FIELD NUMBER: 15.5                      FIELD NAME: AUTHORIZATION POINTER
  LOCATION: 3;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAC(D0,1,D1,1,D2,1,D3,4)
FIELD NUMBER: 63                        FIELD NAME: RENDERING PROV NAME
  LOCATION: 4;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 64                        FIELD NAME: RENDERING PROV NPI
  LOCATION: 4;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 65                        FIELD NAME: RENDERING PROV TAXONOMY CODE
  LOCATION: 4;8                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAC(D0,1,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: INITIAL TREATMENT DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Integrated Billing (IB) accesses the Fee Basis Payment
 File (#162) in order to submit claims to third party payers for reimbursement
 of Fee Basis payments. This is read only access.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IB
KEYWORDS: FB
KEYWORDS: FBAAC
KEYWORDS: 162
KEYWORDS: 162.03
KEYWORDS: FEE BASIS PAYMENT
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAY 18, 2016

NUMBER: 6384                            IA #: 6384
  FILE NUMBER: 161                      GLOBAL ROOT: FBAAA
  DATE CREATED: MAR 03, 2016            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IB ACCESS TO FB #161
  ID: FBAAA
GLOBAL REFERENCE: FBAAA(D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: FROM DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: TO DATE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: FEE PROGRAM
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: VENDOR
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 101                       FIELD NAME: PRIMARY SERVICE AREA
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: PURPOSE OF VISIT CODE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DX LINE 1
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: .055                      FIELD NAME: ASSOCIATED 7078/583
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: .095                      FIELD NAME: TREATMENT TYPE CODE
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: DISCHARGE TYPE
  LOCATION: 0;15                        ACCESS: Read w/Fileman
FIELD NUMBER: .065                      FIELD NAME: PATIENT TYPE CODE
  LOCATION: 0;18                        ACCESS: Read w/Fileman
FIELD NUMBER: .096                      FIELD NAME: ACCIDENT RELATED (Y/N)
  LOCATION: 0;19                        ACCESS: Read w/Fileman
FIELD NUMBER: .097                      FIELD NAME: POTENTIAL COST RECOVERY CASE
  LOCATION: 0;20                        ACCESS: Read w/Fileman
FIELD NUMBER: 104                       FIELD NAME: REFERRING PROVIDER
  LOCATION: 0;21                        ACCESS: Read w/Fileman
FIELD NUMBER: 105                       FIELD NAME: CONTRACT
  LOCATION: 0;22                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAA(D0,1,D1,2,0)
FIELD NUMBER: .021                      FIELD NAME: AUTHORIZATION REMARKS
  LOCATION: 2;0                         ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   Used to identify limitations or detail specifics
 regarding the authorization. The information contained here is displayed
 during the enter payment option and also on patient inquiry option.  
GLOBAL REFERENCE: FBAAA(D0,1,D1,3)
FIELD NUMBER: .085                      FIELD NAME: DX LINE 2
  LOCATION: 3;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .086                      FIELD NAME: DX LINE 3
  LOCATION: 3;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: FBAAA(D0,1,D1,C)
FIELD NUMBER: .087                      FIELD NAME: ICD DIAGNOSIS
  LOCATION: C;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Integrated Billing (IB) accesses the Fee Basis Payment
 File (#161) in order to submit claims to third party payers for reimbursement
 of Fee Basis payments. This is read only access.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 161
KEYWORDS: FBAA
KEYWORDS: FEE BASIS CONTRACT FILE
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAY 09, 2016

NUMBER: 6385                            IA #: 6385
  DATE CREATED: MAR 08, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Remote Procedure
  NAME: RPC                             STATUS: Pending

NUMBER: 6386                            IA #: 6386
  DATE CREATED: MAR 08, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRPC
  NAME: DQSAVE                          ID: PXRPC
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DQSAVE
KEYWORDS: PXRPC
COMPONENT/ENTRY POINT: DQSAVE
 COMPONENT DESCRIPTION:   Processes PCELIST input array and creates a new array
 in a format that can be passed into DATA2PCE^PXAPI.  
VARIABLES: .PCELIST                     TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Array passed by reference.  This should be
 an array in the same format as the PX SAVE DATA and ORWPCE SAVE RPCs' PCELIST
 input paramater.  
VARIABLES: PXPCEARR                     TYPE: Output
 VARIABLES DESCRIPTION:   (Required) The root of an array passed as a String
 value (e.g., "ORPXAPI") that this API will populate based off the PCELIST
 argument. This array will be in a format that can be passed into
 DATA2PCE^PXAPI.  
VARIABLES: PXPCEDARR                    TYPE: Output
 VARIABLES DESCRIPTION:   (Required) The root of an array passed as a String
 value (e.g., "ORPXDEL") that this API will populate based off the PCELIST
 argument. This array will be populated with some deletions that need to be
 filed to DATA2PCE before filing PXPCEARR. This array will be in a format that
 can be passed into DATA2PCE^PXAPI.  
VARIABLES: .PROBLEMS                    TYPE: Output
 VARIABLES DESCRIPTION:   (Required) This API will populate this array with POV
 entries that are marked to be added to the Problem List.  
VARIABLES: .SRC                         TYPE: Both
 VARIABLES DESCRIPTION:   (Required) The source of the data - such as 'TEXT
 INTEGRATION UTILITIES'.  This API can possibly change the value of SRC,
 depending on the Health Factor (HF) values contained in PCELIST.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAR 10, 2016

NUMBER: 6387                            IA #: 6387
  DATE CREATED: MAR 08, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXAPIIM
  NAME: IMMUNIZATION APIS               ID: PXAPIIM
 GENERAL DESCRIPTION:   
   
 REVISIONS: 8/22/23 - Patch PX*1*236 adds a new parameter, PXSKIPNOTLIMITED, to
 the IMMGRP component and a new parameter, PXSKIPFOUR, to the PATICR component
 of this agreement. These new parameters will not impact current subscribers,
 as the components will function as they do currently without this new
 parameter.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PCE
KEYWORDS: IMMUNIZATION
KEYWORDS: STATUS
KEYWORDS: VIMM
COMPONENT/ENTRY POINT: $$IMMSTAT
 COMPONENT DESCRIPTION:   Returns the current immunization status.  
    A: Active 
    H: Inactive, but Selectable for Historic 
    I: Inactive 
VARIABLES: PXIMM                        TYPE: Input
 VARIABLES DESCRIPTION:   (required) Pointer to IMMUNIZATION file #9999999.14.  
COMPONENT/ENTRY POINT: HIST
 COMPONENT DESCRIPTION:   Return patient's immunization or skin test history
 for a given list of immunizations or skin tests.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   Returns an array as follows.  
  
 For Immunizations: 
  
 RESULT(n)=Immunization Name ^ Date Administered ^ Series ^ Facility 
  
 For Skin Tests: 
  
 RESULTS(n)=Skin Test Name ^ Date Admin ^ Date Read ^ Reading ^ Result ^ 
 Facility    
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   "SK": for Skin Tests; "IM": For Immunizations.  
VARIABLES: IENLIST                      TYPE: Input
 VARIABLES DESCRIPTION:   Array of IENs from the Immunization/Skin Test file
 (passed by reference). Format: IENLIST(IEN)="".  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient (#2) IEN.  
VARIABLES: SORT                         TYPE: Input
 VARIABLES DESCRIPTION:   Sort order.  1: Most recent first; 0: Oldest first.  
COMPONENT/ENTRY POINT: IMMGRP
 COMPONENT DESCRIPTION:   Returns a list of immunizations that share the same
 CVX code and Vaccine Group Name(s) as IMM, as well as Contraindications that
 are limited to IMM.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns an array as follows: 
  
    RESULT("CVX",CVX_CODE,IMM_IEN) = Immunization Name 
    
    RESULT("VG",GROUP_NAME,IMM_IEN) = Immunization Name 
                             
    RESULT("ICR",CONTRA_VARIEN) = Contraindication Name 
VARIABLES: PXIMM                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Pointer to IMMUNIZATION file #9999999.14.  
VARIABLES: PXSKIPNOTLIMITED             TYPE: Input
 VARIABLES DESCRIPTION:   (Optional; defaults to 0 for FALSE) Boolean flag that
 indicates whether to skip searching for documented contraindications that are
 not limited to any immunization (1 for TRUE) or to not skip the search (0 for
 FALSE).  
COMPONENT/ENTRY POINT: READENT
 COMPONENT DESCRIPTION:   Find most recent immunization admin for vaccine that
 requires reading.  Only return if there is no reading entered previously.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns an array as follows: 
                            
 RESULT(1)=V Immunization IEN ^ Immunization Name ^ Immunization admin 
 date/time 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   (required) Pointer to the PATIENT file #2.  
COMPONENT/ENTRY POINT: READVALS
 COMPONENT DESCRIPTION:   Returns data type for reading fields.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   Returns an array. The "RANGE" subscript is the range
 for the V Immunization, Reading (#1402) field. The other subscripts are the
 set of codes values for the RESULTS (#1401) field.  
   
    RESULTS("RANGE")=Minimum:Maximum:Maximum decimals 
    RESULTS(Code)=Value 
COMPONENT/ENTRY POINT: CVXTOIEN
 COMPONENT DESCRIPTION:   Return an Immunization IEN for a given CVX code.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns a string in the following format: 
  
 Immunization IEN ^ Name ^ Status  (1: Active; 0: Inactive) ^ Selectable for
 Historic 
VARIABLES: CVX                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The CVX Code.  
COMPONENT/ENTRY POINT: PATICR
 COMPONENT DESCRIPTION:   Finds all of a patient's contraindications/refusals
 using the following criteria: 
  
 1. Any current-dated contraindication/refusal for IMM AND any immunization 
 that shares the same CVX code.  
  
 2. If vaccine group was refused (Refused Vaccine Group (#1205) is set to Yes),
 then include any current-dated* refusals for an immunization that shares the
 same vaccine group as IMM.  
  
 3. Any current-dated* contraindications where the contraindication has IMM 
 listed in the "Immunization Limited To" multiple.  
  
 4. Any current-dated* contraindications where the contraindication does not
 have anything listed in the "Immunization Limited To" multiple, excluding
 Severe Reaction Previous Dose.  
  
 * If BEGDATE and ENDDATE are null, then "current-dated" means where STOP >=
 TODAY.  
               
 * If BEGDATE and ENDDATE are defined, then "current-dated" means where START
 <= ENDDATE, and STOP is >= BEGDATE.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns an array in the following format.  
  
 RESULT(DAS) = Visit IEN ^ Contra/Refusal variable pointer | Contra/Refusal 
 Name ^ Immunization IEN | Name ^ Warn Until Date ^ D/T Recorded ^ Event D/T ^
 Encounter Provider IEN | Name ^ Refused Vaccine Group (1/0) 
  
 RESULT(DAS,"COMMENTS") = Comments 
                           
 When the entry is from IMM CONTRAINDICATION REASONS this is defined: 
                             
 RESULT(DAS,"CONTRAINDICATION/PRECAUTION")=CONTRAINDICATION/PRECAUTION 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Pointer to the Patient (#2) file.  
VARIABLES: IMM                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Pointer to #9999999.14.  
VARIABLES: BEGDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional; defaults to TODAY) Begin Search Date.  
VARIABLES: ENDDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) (optional; defaults to 9999999) End Search
 Date.  
VARIABLES: PXSKIPFOUR                   TYPE: Input
 VARIABLES DESCRIPTION:   (Optional; defaults to 0 for FALSE) Boolean flag that
 indicates whether the fourth search criteria documented above is skipped (1
 for TRUE) or not skipped (0 for FALSE).  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 2/22/23. The IZ Gateway (IZG) project, as a part
 of VDIF, will be using CVXTOIEN^PXAPIIM to retrieve the Immunization IEN for a
 given CVX code. The IEN will be used when calling DATA2PCE to store the 
 immunization data that is sent by the State IISs (Immunization Information
 Systems) via the CDC's IZ Gateway to update the patient's EHR in VistA. This
 will enable VA healthcare providers to view the patient's immunizations that
 were administered at a non-VA facility. 
  DATE ACTIVATED: OCT 10, 2023

NUMBER: 6388                            IA #: 6388
  FILE NUMBER: 162.4                    GLOBAL ROOT: FB7078(
  DATE CREATED: MAR 09, 2016            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INTEGRATED BILLING FB INTERFACE
  ID: FB7078(
GLOBAL REFERENCE: FB7078(D0,0)
FIELD NUMBER: 3.5                       FIELD NAME: DATE OF ADMISSION
  LOCATION: 0;15                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   THIS DATA WILL BE USED TO FACILITATE THIRD PARTY
 REIMBURSEMENT OF FEE BASIS SERVICES IN INTEGRATED BILLING.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FB7078(
KEYWORDS: 162.4
KEYWORDS: 10-7078
KEYWORDS: FEE BASIS
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAY 09, 2016

NUMBER: 6389                            IA #: 6389
  DATE CREATED: MAR 09, 2016            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FBPCR
  NAME: 6389 - Label CATC in FBPCR for IB
  ID: FBPCR
 GENERAL DESCRIPTION:   Integrated Billing (IB) requires use of CATC^FBPCR to
 determine if patient is liable for a copayment in the FEE BASIS system. IB
 uses this information to seek third party reimbursement for FEE BASIS charges. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FBPCR
KEYWORDS: COPAY
KEYWORDS: FEE BASIS
COMPONENT/ENTRY POINT: CATC
 COMPONENT DESCRIPTION:   Determines patient liability for a copayment.  
VARIABLES: FBARRLTC                     TYPE: Input
 VARIABLES DESCRIPTION:   This array is required to be populated for this
 routine to work properly. The array is created by MKARRLTC^FBPCR4. The output
 is array FBARRLTC() with format FBARRLTC(POV code)=value where POV code is a 
 purpose of visit code (external value) for long term care where value: 
  
 = 1 if POV code is for LTC and recoverable from 
   LTC copayment 
  
 = 2 if POV code is for LTC but it is not a 
   subject of LTC copayment 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN in Patient File 
VARIABLES: FBDT                         TYPE: Input
 VARIABLES DESCRIPTION:   Date of service 
VARIABLES: FBPOV                        TYPE: Input
 VARIABLES DESCRIPTION:   POV Code for LTC determination 
VARIABLES: $$CATC                       TYPE: Output
 VARIABLES DESCRIPTION:   Copay liability. Possible values are: 0 - the patient
 is not liable for any co-pay; 1 - if means test or pending adjudication and
 agree to pay deductible; 2 - the patient is liable for LTC co-pay; 3 - no
 1010EC on file; 4 - more analysis is needed to determine the patient liability 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: SEP 20, 2016

NUMBER: 6390                            IA #: 6390
  DATE CREATED: MAR 09, 2016            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FBPCR4
  NAME: 6390 - Label MKARRLTC in routine FBPCR4 for IB
  ID: FBPCR4
 GENERAL DESCRIPTION:   Determines if POV code is LTC, and whether it is
 subject to a copayment.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FBPCR4
KEYWORDS: MKARRLTC
KEYWORDS: FEE BASIS
KEYWORDS: LTC
KEYWORDS: POV
COMPONENT/ENTRY POINT: MKARRLTC
 COMPONENT DESCRIPTION:   Determines if POV code is LTC, and whether it is
 subject to a copayment.  
VARIABLES: FBARRLTC                     TYPE: Output
 VARIABLES DESCRIPTION:   The output is array FBARRLTC() with format
 FBARRLTC(POV code)=value where POV code is a purpose of visit code (external
 value) for long term care where value 
   = 1 if POV code is for LTC and recoverable from LTC copayment 
   = 2 if POV code is for LTC but it is not a subject of LTC copayment 
VARIABLES:  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAY 09, 2016

NUMBER: 6391                            IA #: 6391
  DATE CREATED: MAR 10, 2016            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Supported                      TYPE: Routine
  ROUTINE: IBBAPI                       NAME: 6391 - Function INSUR in IBBAPI
  ID: IBBAPI
 GENERAL DESCRIPTION:   Displays all insurance company information.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: DISPLAY
KEYWORDS: INSURANCE
KEYWORDS: COMPANY
COMPONENT/ENTRY POINT: INSUR
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to patient.  
VARIABLES: IBDT                         TYPE: Input
 VARIABLES DESCRIPTION:   Date to check for coverage and riders.  
VARIABLES: IBSTAT                       TYPE: Input
 VARIABLES DESCRIPTION:   Status/Type of insurance.  
VARIABLES: IBFLDS                       TYPE: Input
 VARIABLES DESCRIPTION:   Insurance fields.  
VARIABLES: IBR                          TYPE: Output
 VARIABLES DESCRIPTION:   Output array.  

NUMBER: 6392                            IA #: 6392
  DATE CREATED: MAR 10, 2016            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBFBUTIL
  NAME: 6392 - IBFBUTIL FOR FEE BASIS   ID: IBFBUTIL
 GENERAL DESCRIPTION:   Utility functions in Integrated Billing for use by Fee
 Basis.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FB
KEYWORDS: FEE BASIS
KEYWORDS: EVENT
KEYWORDS: CHKBILL
KEYWORDS: IBFB
KEYWORDS: 360
COMPONENT/ENTRY POINT: EVENT
 COMPONENT DESCRIPTION:   Updates #360, IB-FB INTERFACE TRACKING FILE 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to entry in #360.  
COMPONENT/ENTRY POINT: CHKBILL
 COMPONENT DESCRIPTION:   Check for prior bill in #360.  
VARIABLES: IBIN                         TYPE: Input
 VARIABLES DESCRIPTION:   Bill and invoice used to check for previous storage
 in #360.  
SUBSCRIBING PACKAGE: FEE BASIS
  DATE ACTIVATED: MAY 09, 2016

NUMBER: 6393                            IA #: 6393
  DATE CREATED: MAR 17, 2016
  CUSTODIAL PACKAGE: VIRTUAL PATIENT RECORD
  USAGE: Private                        TYPE: Routine
  ROUTINE: VPRDJ                        NAME: VPR GET PATIENT DATA JSON
  ID: VPRDJ
 GENERAL DESCRIPTION:   The VISTA SERVICES ASSEMBLER package provides a set of
 standard RESTified services. One of these services provides patient related
 data collected from the GET^VPRDJ API and adds the ndcCode value associated
 with any patient medications returned to the output.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GET
SUBSCRIBING PACKAGE: VISTA SERVICES ASSEMBLER

NUMBER: 6394                            IA #: 6394
  DATE CREATED: MAR 18, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: PROSTHETICS-DYNAMED LOOKUP
 GENERAL DESCRIPTION:   The Prosthetics package needs the ability to determine
 whether a site is using DynaMed for inventory.  Sites using DynaMed will
 continue to use Prosthetics Inventory Package (PIP) until a better solution is
 devised.  This DBIA grants the Prosthetics package the permission to read the
 system parameter "PRCV COTS INVENTORY" with the following kernel call: 
 ($$GET^XPAR("SYS","PRCV COTS INVENTORY",1,"Q")).  The "PRCV COTS INVENTORY"
 parameter identifies which COTS product is being utilized for the inventory
 management system of the site.  The current values are: 
  
 NAME: PRCV COTS INVENTORY               DISPLAY TEXT: COTS Inventory 
   MULTIPLE VALUED: No                   VALUE TERM: 0 or 1 
   VALUE DATA TYPE: set of codes         VALUE DOMAIN: 0:NONE;1:DYNAMED 
   VALUE HELP: ?/                        INSTANCE DATA TYPE: numeric 
  
 DESCRIPTION:   
  This parameter identifies which COTS product is being utilized for the 
  inventory management system of the site.  The current values are: 
   
  0       NONE - means no COTS product is being used and the inventory 
  management system in use is GIP/IFCAP 
  1       DYNAMED - means the DynaMed product is being used 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PIP
KEYWORDS: PROSTHETICS
KEYWORDS: DYNAMED
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   This DBIA grants the Prosthetics package the permission
 to read the IFCAP system parameter "PRCV COTS INVENTORY".  See details in the
 DBIA "General Description".  
  DATE ACTIVATED: MAR 23, 2016

NUMBER: 6395                            IA #: 6395
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55,
  DATE CREATED: MAR 18, 2016
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HMP READ ACCESS TO PS(55
  ID: PS(55,
GLOBAL REFERENCE: PS(55,D0,5,D1,0
FIELD NUMBER: 66                        FIELD NAME: ORDERS FILE ENTRY
  LOCATION: 0;21                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(55,D0,'IV',D1,0
FIELD NUMBER: 110                       FIELD NAME: ORDERS FILE ENTRY
  LOCATION: 0;21                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
      
   
 The Enterprise Health MGMT Platform (HMP) request permission to do a Pharmacy
 Patient to retrieve the ORDERS FILE ENTRY (#110) on the IV Multiple and the
 ORDERS FILE ENTRY (#66) on the Unit Dose Multiple. HMP request temporary
 approval to do direct global reads rather than using FileMan or the existing
 APIs because of the need to get the data quickly so the process doesn't slow
 down the data retrieval and impact the user interface.  
  
 HMP collects this data as part of the sync actions that syncs the patients
 medication data between the local VistA system and the eHMP JDS database. 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 19, 2017
KEYWORDS: PS(55
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: MAR 23, 2016

NUMBER: 6396                            IA #: 6396
  FILE NUMBER: 404.51                   GLOBAL ROOT: SCTM(404.51
  DATE CREATED: MAR 18, 2016            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HMP ACCESS TO SCTM(404.51
  ID: SCTM(404.51
GLOBAL REFERENCE: SCTM(404.51,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: TEAM PHONE NUMBER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SCTM(404.51,'B'
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) requests
 permissions to do a direct global read of the TEAM File (#404.51) to retrieve
 the Name (.01) and Team Phone Number (.02) from the file. HMP uses this data
 as part of the sync process that syncs the local VistA data with the HMP JDS
 data system. 
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12  
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the  access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 *********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: SCTM(404.51
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: APR 07, 2016

NUMBER: 6397                            IA #: 6397
  DATE CREATED: MAR 24, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWORB
  NAME: HMP CALL TO FASTUSER~ORWORB     ID: ORWORB
 GENERAL DESCRIPTION:   The Enterprise Health Management Platform (HMP) is
 making a call to FASTUSER^ORWORB to retrieve a user's current notifications
 for all patients. This data is collected and synced with the HMP JSON Data
 System (JDS) for use with the HMP user interface. 
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12  
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the  access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 *********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: FASTUSER
KEYWORDS: HMP
COMPONENT/ENTRY POINT: FASTUSER
 COMPONENT DESCRIPTION:   This call returns the current user's notifications
 across all patients.  
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   This is the name of the output temporary global that
 contains the alert information. 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: APR 12, 2016

NUMBER: 6398                            IA #: 6398
  FILE NUMBER: 161.2                    GLOBAL ROOT: FBAAV
  DATE CREATED: MAR 31, 2016            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IB ACCESS TO FB #161.2
  ID: FBAAV
GLOBAL REFERENCE: FBAAV(D0,3)
FIELD NUMBER: 41.01                     FIELD NAME: NPI
  LOCATION: 3;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 42                        FIELD NAME: TAXONOMY CODE
  LOCATION: 3;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Integrated Billing requires access to the Fee Basis
 Vendor File (#161.2) to get the (#41.01) NPI and (#42) TAXONOMY CODE.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FEE
KEYWORDS: BASIS
KEYWORDS: VENDOR
KEYWORDS: NPI
KEYWORDS: TAXONOMY
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAY 11, 2016

NUMBER: 6399                            IA #: 6399
  DATE CREATED: APR 01, 2016            CUSTODIAL PACKAGE: BAR CODE MED ADMIN
  USAGE: Private                        NAME: BCMA MEDHIST
  STATUS: Pending
KEYWORDS: MEDHIST

NUMBER: 6400                            IA #: 6400
  FILE NUMBER: 101                      GLOBAL ROOT: ORD(101,
  DATE CREATED: APR 07, 2016            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HMP ACCESS TO FILE 101
  ID: ORD(101,
GLOBAL REFERENCE: ORD(101,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: TYPE
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: ORD(101,'B'
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ORD(101,D0,10,D1,0
FIELD NUMBER: .01                       FIELD NAME: ITEM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: ORD(101,D0,775,D1,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   **NOTE: This ICR is for the Enterprise Health
 Management Platform (HMP) only! 
  
 HMP Post Install Init Routine HMP0311P does a direct read of the B cross 
 reference to see if the HMP DGPF ASSIGN FLAG, DGPF ASSIGN FLAG exists in the
 Protocol file. If the DGPF ASSIGN FLAG protocol exists, the routine edits the
 protocol using FileMan to make the protocol an extended action protocol and to
 add HMP DGPF ASSIGN FLAG protocol as an Item.  
  
 HMP Post Install Init routine HMP0311Q does a FileMan read of the Protocol
 File to lookup to check for the HMP ADT-A04 CLIENT, VAFC ADT-A04 SERVER, HMP
 ADT-A08 CLIENT and VAFC ADT-A08 SERVER protocols exist in the Protocol file.
 If the protocols exist, the routine uses FileMan to subscribe the HMP protocol
 to the VAFC protocol. HMP ADT-A04 Client is subscribed to VAFC ADT-A04 Server
 protocol and HMP ADT-A08 Client is subscribed to the VAFC ADT-A08 Server
 protocol.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12  
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the  access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 *********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
KEYWORDS: 101
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: APR 12, 2016

NUMBER: 6401                            IA #: 6401
  DATE CREATED: APR 08, 2016            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCAAPR1
  NAME: ACCOUNT PROFILE                 ID: PRCAAPR1
 GENERAL DESCRIPTION:   Users working the Copay on Hold will be able to access
 the Patient Account Profile report while still in the Copays on Hold List
 Manager.  This will aid them in determining if the copay may be released or
 not.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRCA
KEYWORDS: COPAY ON HOLD
COMPONENT/ENTRY POINT: HDR
 COMPONENT DESCRIPTION:   Header for Account Profile report 
COMPONENT/ENTRY POINT: HDR2
 COMPONENT DESCRIPTION:   Header 2 for Account Profile report 
COMPONENT/ENTRY POINT: DIS
 COMPONENT DESCRIPTION:   Display bill line items 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   This integration control agreement will print the data
 compiled for the Patient Account Profile report.  
  DATE ACTIVATED: AUG 31, 2016

NUMBER: 6402                            IA #: 6402
  FILE NUMBER: 404.42                   GLOBAL ROOT: SCPT(404.42
  DATE CREATED: APR 08, 2016            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  NAME: HMP ACCESS TO FILE 404.42       ID: SCPT(404.42
GLOBAL REFERENCE: SCPT(404.42,D0,O
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Enterprise Health Management Platform (HMP) uses a
 FileMan read to retrieve the Patient assigned to a Team from the PATIENT TEAM
 ASSIGNMENT FILE (#404.42). 
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 There are APIs available for PCMM data but HMP was not able to convert to use
 an API prior the the shut down of HMP on 10/27/17.  HMP requested temporary
 approval of this ICR to give the project team time to convert to an API and to
 work with the PCMM Web team to identify the best path for retrieving data with
 the current and web version of PCMM. 
  
 If HMP is reactivated in the future, the HMP project team will need to work
 with the PCMM/Scheduling teams to resolve this issue and decide if this ICR is
 needed.  
  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: 404.42
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6403                            IA #: 6403
  DATE CREATED: APR 08, 2016            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCAAPR
  NAME: ACCOUNT PROFILE REPORT          ID: PRCAAPR
 GENERAL DESCRIPTION:   Users working the Copay on Hold will be able to access
 the Patient Account Profile report while still in the Copays on Hold List
 Manager. This will aid them in determining if the copay may be released or
 not.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PCRA
KEYWORDS: COPAY ON HOLD
COMPONENT/ENTRY POINT: COMP
 COMPONENT DESCRIPTION:   This is called to compile the Patient Account Profile
 report.  
VARIABLES: DFN                          TYPE: Used
 VARIABLES DESCRIPTION:   Patient ID 
VARIABLES: NAME                         TYPE: Used
 VARIABLES DESCRIPTION:   Patient Name 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   This integration control registration is used to
 compile the Patient Account Profile report.  
  DATE ACTIVATED: AUG 31, 2016

NUMBER: 6404                            IA #: 6404
  DATE CREATED: APR 18, 2016            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: FBUTL9                       NAME: FBUTL9
  ID: FBUTL9
 GENERAL DESCRIPTION:   Access to ADDUA and UOKPAY API's in FBUTL9 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: FBUTL9
KEYWORDS: FEE BASIS CLAIMS SYSTEM
KEYWORDS: OK2PAY
KEYWORDS: ADDUA
KEYWORDS: UOKPAY
COMPONENT/ENTRY POINT: ADDUA
 COMPONENT DESCRIPTION:   Add record to the User Audit Multiple 
VARIABLES: FBFILE                       TYPE: Input
 VARIABLES DESCRIPTION:   File number to edit 
VARIABLES: FBIENS                       TYPE: Input
 VARIABLES DESCRIPTION:   Record number with the file to edit 
VARIABLES: FBTXT                        TYPE: Input
 VARIABLES DESCRIPTION:   Text to add to the User Audit multpile 
COMPONENT/ENTRY POINT: UOKPAY
 COMPONENT DESCRIPTION:   Determine if the current user is allowed to make
 payments for the current patient.  
VARIABLES: FBDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: FBAUTHP                      TYPE: Input
 VARIABLES DESCRIPTION:   Authorization Pointer 
VARIABLES: FBUSR                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the cureent user 
SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM
  DATE ACTIVATED: APR 27, 2016

NUMBER: 6405                            IA #: 6405
  DATE CREATED: MAY 10, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGRPE
  NAME: LANGDEL~DGPRE                   ID: DGRPE
 GENERAL DESCRIPTION:   The Scheduling routine ^SDM (expected w/SD*5.3*619) is
 using Registration routine LANGDEL^DGRPE to check if Preferred Language
 sub-field of the LANGUAGE DATE/TIME multiple (#7) in the PATIENT file (#2) is
 entered.  If not, call the LANGDEL^DGRPE to remove the sub record.  
  STATUS: Active
COMPONENT/ENTRY POINT: LANGDEL
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of patient in Patient file.  
VARIABLES: D1                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the entry in the LANGUAGE
 DATE/TIME (#7) sub-file.  
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: JUL 22, 2016

NUMBER: 6406                            IA #: 6406
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: MAY 11, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: LANGUAGE DATE/TIME
  ID: DPT(
GLOBAL REFERENCE: DPT(D0,.207,0
 GLOBAL DESCRIPTION:   
         ^DPT(D0,.207,0)                         Read Direct Global Read 
  
 This global node is checked prior to calling Fileman to update the fields in
 the multiple.  
GLOBAL REFERENCE: DPT(D0,.207,D1,0)
FIELD NUMBER: .01                       FIELD NAME: LANGUAGE DATE/TIME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PREFERRED LANGUAGE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Scheduling package requests permission to read/update
 using FileMan to all fields in the LANGUAGE DATE/TIME multiple (#7) of the
 PATIENT file (#2).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: JUL 22, 2016

NUMBER: 6407                            IA #: 6407
  FILE NUMBER: 669                      GLOBAL ROOT: RMPR(669,
  DATE CREATED: MAY 17, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Supported                      TYPE: File
  NAME: Access to file 669              ID: RMPR(669,
GLOBAL REFERENCE: RMPR(669,D0,0)
FIELD NUMBER: RMPR(669,DO,1)            ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Access to the MASTER MEDICAL DEVICE file, #669, a
 locked down file is granted as needed for display, reading functions 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: RMPR
KEYWORDS: ACCESS

NUMBER: 6408                            IA #: 6408
  FILE NUMBER: 18.12                    GLOBAL ROOT: XOB(18.12
  DATE CREATED: MAY 18, 2016            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ADD/UPDATE RESOURCE ON WEB SERVER FILE (#18.12)
  ID: XOB(18.12
GLOBAL REFERENCE: XOB(18.12,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: SERVER
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: STATUS
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .07                       FIELD NAME: DEFAULT HTTP TIMEOUT
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.01                      FIELD NAME: LOGIN REQUIRED
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.01                      FIELD NAME: SSL ENABLED
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.02                      FIELD NAME: SSL CONFIGURATION
  LOCATION: 3;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.03                      FIELD NAME: SSL PORT
  LOCATION: 3;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 200                       FIELD NAME: USERNAME
  LOCATION: 200;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 300                       FIELD NAME: PASSWORD
  LOCATION: 300;1                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: XOB(18.12,D0,100,D1
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: STATUS
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: XOB(18.12,'B'
 GLOBAL DESCRIPTION:   Used to retrieve the Internal Entry Number (IEN) of the
 MVI's Web Server entries.  
 GENERAL DESCRIPTION:   The Master Veteran Index (MVI) team requests read/write
 access to the WEB SERVER (#18.12) file to add a new entry during a
 post-install process. The post-install routine process will create the new
 server record entry using FILE^DICN and will also create a new entry to the 
 AUTHORIZED WEB SERVICES (#100) multiple, WEB SERVICE (#.01) field using the
 FILE^DICN API.  
  
 In addition, the MVI team will require read/write access to the WEB SERVER
 (#18.12) file to update the entry through the remote procedure (RPC) [MPI
 VISTA HWS CONFIG] using FILE^DIE when needed/required.  
  
 NOTE: This processing is done programmatically to avoid having sites manually
 configure HWSC using the Web Server Manager. This will ensure all sites have
 the same configuration installed correctly.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 18.12
KEYWORDS: WEB SERVICE FILE
KEYWORDS: XOBW
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA
 SUBSCRIBING DETAILS:   For the Master Veteran Index (MVI) project, an
 additional web service is being added through post-install and updated as
 needed. Creation, updating and enabling of the web service programmatically
 will alleviate sites from having to perform this task manually and will also
 ensure that the entry is created/updated correctly.  
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   To support "VistA-Like" systems (Ie. FORUM, HAC, HEC,
 and CMOP) that do NOT install the MASTER PATIENT INDEX VISTA (MPIF) patches,
 KERNEL will release the same Web-Service identified in patch MPIF*1.0*63 to 
 allow these other systems (Ie. VistA-Like) to be able to access the MVI system
 through this Web Service through the post install process and allowing for
 updates as needed. Creation, updating and enabling of the web service
 programmatically will alleviate sites from having to perform this task
 manually and will also ensure that the entry is created/updated correctly and
 timely.  
  DATE ACTIVATED: NOV 23, 2021

NUMBER: 6409                            IA #: 6409
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870
  DATE CREATED: MAY 20, 2016            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Access to HLCS(870)
  ID: HLCS(870
GLOBAL REFERENCE: HLCS(870,0
FIELD NUMBER: .01                       FIELD NAME: NODE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DNS DOMAIN
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: STATE
  LOCATION: 0;5                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: TIME STARTED
  LOCATION: 0;10                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: TIME STOPPED
  LOCATION: 0;11                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: TASK NUMBER
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: SHUTDOWN LLP ?
  LOCATION: 0;15                        ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: HLCS(870,D0,400
FIELD NUMBER: 400.01                    FIELD NAME: TCP/IP ADDRESS
  LOCATION: 400;1                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 400.02                    FIELD NAME: TCP/IP PORT
  LOCATION: 400;2                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 400.03                    FIELD NAME: TCP/IP SERVICE TYPE
  LOCATION: 400;3                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 400.04                    FIELD NAME: PERSISTENT
  LOCATION: 400;4                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 400.08                    FIELD NAME: TCP/IP PORT (OPTIMIZED)
  LOCATION: 400;8                       ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   Update all the logical links that use Vista Interface
 Engine (VIE) to transmit HL7 messages to be replaced by VA Enterprise
 Messaging Infrastructure (VA eMI).  
  
 The process to replace VIE to eMI will be to update the DNS DOMAIN field in 
 file 870, HL LOGICAL LINK, for existing logical links.  
  
 Revision History: 
  1/13/25: Added field 400.08, TCP/IP PORT (OPTIMIZED) for use by IB*2*769 
           patch - IB COPAY ACCUMULATION CONTINUE 
  STATUS: Active
KEYWORDS: 870
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   Update logical link XUMF ACK 
SUBSCRIBING PACKAGE: HEALTH DATA REPOSITORY
 SUBSCRIBING DETAILS:   Update logical link VDEFVIE1, VDEFVIE2, VDEFVIE3, and
 VDEFVIE4 
SUBSCRIBING PACKAGE: IFCAP
 SUBSCRIBING DETAILS:   Update logical link PRCHJ_ECMS 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Effective with PSO*7.0*534.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Added 12/22/22, effective with patch IB*2.0*704 Updated
 1/13/25, effective with IB*2.0*769, added field 400.08 TCP/IP PORT (OPTIMIZED) 
  DATE ACTIVATED: JUN 02, 2016

NUMBER: 6410                            IA #: 6410
  GLOBAL ROOT: DD(                      DATE CREATED: MAY 24, 2016
  CUSTODIAL PACKAGE: 1                  USAGE: Controlled Subscription
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: FORBID PURGING AUDITS           ID: DD(
GLOBAL REFERENCE: DD(FILE,0,"AUDPURGEFORBID")
 GLOBAL DESCRIPTION:   Set this node to null to prevent a user from being able
 to purge data audits for a given file. Setting this node will cause this file
 to be screened from the list of selectable files when running option Purge
 Data Audits [DIAUDIT PURGE DATA].  
  e.g. ^DD(file #,0,"AUDPURGEFORBID")="" 
  
  
GLOBAL REFERENCE: DD(FILE,0,"DDAUDPURGEFORBID")
 GLOBAL DESCRIPTION:   Set this node to null to prevent a user from being able
 to purge data dictionary (DD) audits for a given file. Setting this node will
 cause this file to be screened from the list of selectable files when running 
 option Purge DD Audits [DIAUDIT PURGE DD].  
  e.g. ^DD(file #,0,"DDAUDPURGEFORBID")="" 
  
  
 GENERAL DESCRIPTION:   The following data dictionary (DD) nodes can be set to
 restrict purging of data and/or DD audits. These nodes have to be set directly
 in programmer mode, since there is no utility to set them. These nodes can be
 transported using the KIDS utility, if you send the full file Data Dictionary. 
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AUDPURGEFORBID
KEYWORDS: AUDIT
KEYWORDS: PURGE
KEYWORDS: DDAUDPURGEFORBID
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Effective with patch PX*1*216, Patient Care Encounter
 (PCE), will restrict purging of the data audits for the V IMMUNIZATION file
 (#9000010.11).  PCE will set the global node
 ^DD(9000010.11,0,"AUDPURGEFORBID")="" in the post-install routine.  
  
  DATE ACTIVATED: JUL 08, 2016

NUMBER: 6411                            IA #: 6411
  DATE CREATED: MAY 24, 2016
  CUSTODIAL PACKAGE: VIRTUAL PATIENT RECORD
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VPRJSON
  NAME: Decode/Encode JSON              ID: VPRJSON
 GENERAL DESCRIPTION:   This is a utility for decoding and encoding JSON.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JSON
KEYWORDS: Decode
KEYWORDS: Encode
COMPONENT/ENTRY POINT: ENCODE(VVROOT,VVJSON,VVERR)
 COMPONENT DESCRIPTION:   This API is used for converting a local or global
 array (M structure) into a JSON object.  
  
 Examples: 
  
 D ENCODE^VPRJSON("^GLO(99,2)","^TMP($J)") 
  
 D ENCODE^VPRJSON("LOCALVAR","MYJSON","LOCALERR") 
VARIABLES: VVROOT                       TYPE: Input
 VARIABLES DESCRIPTION:   Closed array reference for M representation of
 object.  
VARIABLES: VVJSON                       TYPE: Both
 VARIABLES DESCRIPTION:   Destination variable for the string array formatted
 as JSON.  
VARIABLES: VVERR                        TYPE: Both
 VARIABLES DESCRIPTION:   Contains error messages, defaults to
 ^TMP("VPRJERR",$J).  
COMPONENT/ENTRY POINT: DECODE(VVJSON,VVROOT,VVERR)
 COMPONENT DESCRIPTION:   This API is used for converting a JSON object into a
 local or global array (M structure).  
  
 Examples: 
  
 D DECODE^VPRJSON("MYJSON","LOCALVAR","LOCALERR") 
  
 D DECODE^VPRJSON("^MYJSON(1)","^GLO(99)","^TMP($J)") 
VARIABLES: VVJSON                       TYPE: Input
 VARIABLES DESCRIPTION:   String/array containing serialized JSON object.  
VARIABLES: VVROOT                       TYPE: Both
 VARIABLES DESCRIPTION:   Closed array reference for M representation of
 object.  
VARIABLES: VVERR                        TYPE: Both
 VARIABLES DESCRIPTION:   Contains error messages, defaults to
 ^TMP("VPRJERR",$J).  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
SUBSCRIBING PACKAGE: MENTAL HEALTH
SUBSCRIBING PACKAGE: LIGHTHOUSE
 SUBSCRIBING DETAILS:   Added 10/4/21, effective with LHS*1.0*1 that is being
 created to support an IB initiative associated with the Advanced Medical Cost
 Management Solutions (AMCMS) and WellHive. WellHive is a commercial insurance 
 validation/verification system that will be IOC tested at VISN8 at the time of
 the subscription.  
  DATE ACTIVATED: JUL 28, 2016

NUMBER: 6412                            IA #: 6412
  DATE CREATED: MAY 25, 2016            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SCAPMC
  NAME: HMP Access to TPPR~SCAPMC       ID: SCAPMC
 GENERAL DESCRIPTION:   The Enterprise Health Management Platform (HMP) makes a
 call to the TPPR^SCAPMC API to retrieve all the positions for a practitioner.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12  
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the  access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 *********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: SCAPMC
KEYWORDS: TPPR
KEYWORDS: HMP
COMPONENT/ENTRY POINT: TPPR
 COMPONENT DESCRIPTION:   Returns the positions for a practitioner.  
VARIABLES: SC200                        TYPE: Input
 VARIABLES DESCRIPTION:   The User DUZ for the provider.  
VARIABLES: SCDATES                      TYPE: Input
 VARIABLES DESCRIPTION:   The begin date to search, the end date to search and
 a flag for what patients to search. SCDATES("BEGIN") SCDATES("END") 
 SCDATES("INCL") 
VARIABLES: SCPURPA                      TYPE: Input
 VARIABLES DESCRIPTION:   An array of pointers to the Team Purpose
 file(#403.47). If null, it will return all teams.  
VARIABLES: SCROLEA                      TYPE: Input
 VARIABLES DESCRIPTION:   An array of pointers to the Standard Position file
 (#403.46). If null, returns all positions.  
VARIABLES: SCLIST                       TYPE: Input
 VARIABLES DESCRIPTION:   The name of the array to return the results.  
VARIABLES: SCERR                        TYPE: Input
 VARIABLES DESCRIPTION:   The array name to store error messages.  
VARIABLES:  
VARIABLES: SCLIST()                     TYPE: Output
 VARIABLES DESCRIPTION:   An array of positions: Piece   Description 1      
 IEN of Team Position file (#404.57) 2       Name of Position 3       IEN of
 Team ($404.51) 4       IEN of Team Position History file (#404.59) 5      
 Current effective date 6       Current inactivate date (if any) 7      
 Pointer to Standard Position file (403.46) 8       Name of Standard Role 9     
  Pointer to the User Class file (#8930) 10      Name of User Class 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: AUG 09, 2017

NUMBER: 6413                            IA #: 6413
  DATE CREATED: MAY 25, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORQPT2                       NAME: HMP Access to EN1~ORQPT2
  ID: ORQPT2
 GENERAL DESCRIPTION:   The Enterprise Health Management Platform (HMP) calls
 the EN1^ORQPT2 API to determine if a patient's record is flag as sensitive or
 NOT sensitive.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ORQPT2
KEYWORDS: EN1
KEYWORDS: HMP
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   Returns a flag to indicate if a patient's record is
 marked as sensitive.  
VARIABLES: ORDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6414                            IA #: 6414
  DATE CREATED: MAY 25, 2016            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMBMI
  NAME: HMP ACCESS TO PXRM APIS         ID: PXRMBMI
 GENERAL DESCRIPTION:   The Enterprise Health Management Platform (HMP) calls
 the BMI^PXRMBMI and BSA^PXRMBMI APIs to retrieve the patient's BMI and BSA
 results.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12  
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the  access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 *********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: PXRMBMI
KEYWORDS: HMP
KEYWORDS: BSA
KEYWORDS: BMI
COMPONENT/ENTRY POINT: BMI
 COMPONENT DESCRIPTION:   Returns a patient's BMI.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: NGET                         TYPE: Input
 VARIABLES DESCRIPTION:   The number of results to return.  
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The starting date/time for the search.  
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The date/time to end the search.  
VARIABLES: NFOUND                       TYPE: Output
 VARIABLES DESCRIPTION:   The number of results found.  
VARIABLES: TEST                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns the true values for the found occurances.  
VARIABLES: DATE                         TYPE: Output
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   The name of the return array.  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   The name of the array to return the date/time the
 height measurement was taken.  
VARIABLES: DATA()                       TYPE: Output
 VARIABLES DESCRIPTION:   An array containing the results: Test date ^ wt ^ ht
 ^ height date 
COMPONENT/ENTRY POINT: BSA
 COMPONENT DESCRIPTION:   Returns a patient's BSA result.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient DFN.  
VARIABLES: NGET                         TYPE: Input
 VARIABLES DESCRIPTION:   The number of results to return.  
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The date to start the seach.  
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The date to stop the search.  
VARIABLES: NFOUND                       TYPE: Input
 VARIABLES DESCRIPTION:   The number of results found.  
VARIABLES: TEST                         TYPE: Both
 VARIABLES DESCRIPTION:   Input: The formula to use.  Output: returns the true
 values for the found occurences.  
VARIABLES: DATE                         TYPE: Input
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   Name of the array to return the results.  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   The name of the array to return the date the height
 was measured.  
VARIABLES: DATA()                       TYPE: Output
 VARIABLES DESCRIPTION:   Array containing the results: Test date ^ wt ^ ht ^
 height date 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: AUG 29, 2016

NUMBER: 6415                            IA #: 6415
  DATE CREATED: MAY 27, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: HMP USE OF DGPF EDIT ASSIGNMENT PROTOCOL
 GENERAL DESCRIPTION:   HMP modified the DGPF EDIT ASSIGNMENT protocol to make
 it an extended action type and to add the HMP DGPF ASSIGN FLAG protocol as an
 Item. the HMP DGPF ASSIGN FLAG will initiate a sync action when a patient's
 flags are edited.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12  
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the  access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 *********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
KEYWORDS: DGPF EDIT ASSIGNMENT
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: AUG 12, 2016

NUMBER: 6416                            IA #: 6416
  DATE CREATED: MAY 27, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: HMP USE OF DGPF CHANGE ASSIGNMENT OWNERSHIP
 GENERAL DESCRIPTION:   HMP modified the DGPF CHANGE ASSIGNMENT OWNERSHIP
 protocol to make it an extended action type and to add the HMP DGPF ASSIGN
 FLAG protocol as an Item. the HMP DGPF ASSIGN FLAG will initiate a sync action
 when a patient's flags change ownership.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12  
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the  access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 *********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: DGPF CHANGE ASSIGNMENT
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: AUG 12, 2016

NUMBER: 6417                            IA #: 6417
  DATE CREATED: JUN 01, 2016            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDWLEVAL
  NAME: SCV ACCESS TO DATP~SDWLEVAL     ID: SDWLEVAL
 GENERAL DESCRIPTION:   The Scheduling Calendar View Mobile App (MBAA) calls
 the DATP^SDWLEVAL API to retrieve specific appointment data for a patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DATP
KEYWORDS: SDWLEVAL
KEYWORDS: SCV
KEYWORDS: VAR
COMPONENT/ENTRY POINT: DATP
 COMPONENT DESCRIPTION:   Returns appointment data.  
VARIABLES: SDAP                         TYPE: Input
 VARIABLES DESCRIPTION:   The node number from the TMP($J,"APPT" global.  
VARIABLES: SDWLAPPT                     TYPE: Output
 VARIABLES DESCRIPTION:   Name of the array to return the appointment data in.  
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  DATE ACTIVATED: JUN 10, 2016

NUMBER: 6418                            IA #: 6418
  DATE CREATED: JUN 01, 2016            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDWLQSC1
  NAME: SCV ACCESS TO CHKENC~SDWLQSC1 API
  ID: SDWLQSC1
 GENERAL DESCRIPTION:   This API checks for any encounters for a patient and
 returns encounter data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CHKENC
KEYWORDS: SDWLQSC1
KEYWORDS: SCV
KEYWORDS: VAR
COMPONENT/ENTRY POINT: CHKENC
 COMPONENT DESCRIPTION:   Checks for and returns encounter data for a patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: SDORG                        TYPE: Input
 VARIABLES DESCRIPTION:   Original date of the Electronic Wait List entry.  
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the Hospital Location file (#44).  
VARIABLES: SDSP                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the CLINIC STOP File (#40.7).  
VARIABLES: PROC                         TYPE: Input
 VARIABLES DESCRIPTION:   Flag - 0 - Create the first appointment/encounter
 only 
        1 - Multiple appointment/encounter 
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  DATE ACTIVATED: JUN 10, 2016

NUMBER: 6419                            IA #: 6419
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: JUN 01, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MBAA ACCESS TO 1010EZ DATA
  ID: DPT(
GLOBAL REFERENCE: DPT(D0,1010.15
FIELD NUMBER: 1010.159
  FIELD NAME: APPOINTMENT REQUEST ON 1010EZ
  LOCATION: 1010.15;9                   ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,1010.16
FIELD NUMBER: 1010.161                  FIELD NAME: APPOINTMENT REQUEST STATUS
  LOCATION: 1010.16;1                   ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1010.163                  FIELD NAME: APPOINTMENT REQUEST COMMENT
  LOCATION: 1010.16;3                   ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT('AEAR'
FIELD NUMBER: 1010.159
  FIELD NAME: APPOINTMENT REQUEST ON 1010EZ
  LOCATION: 1010.15;9                   ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   This cross reference is used to look up patients that
 have requested an appointment.  
 GENERAL DESCRIPTION:   The Scheduling Calendar View Mobile App (MBAA) is
 access the 1010EZ data in the Patient File (#2) in order to provide
 information about patients on the NEAR list.  
  
 The Scheduling Calendar View Mobile Apps allows users to get a list of 
 patients on the NEAR list and if the user schedules an appointment for a 
 patient to the list, they can then update the NEAR list to remove the patient
 from the list. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MBAA
KEYWORDS: 1010EZ
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 9/17/26, effective with patch SD*5.3*955.  
 Scheduling is requesting to modify fields 1010.159 and 1010.163 to be Both R/W
 w/Fileman.  
  DATE ACTIVATED: JUN 13, 2016

NUMBER: 6420                            IA #: 6420
  DATE CREATED: JUN 15, 2016            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FBUTLMVI
  NAME: FEE BASIS ACTIVITY CHECKS       ID: FBUTLMVI
 GENERAL DESCRIPTION:   The Master Veteran Index (MVI) team requests access to
 the Application Programmer Interface (API) $$ACTIVITY^FBUTLMVI to determine if
 there has been any activity for a patient that has been reported as deceased.
 MVI will determine the activity for a given patient through a remote procedure
 call (RPC) to each VistA site from the MVI to determine if the patient is
 really deceased.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 162
KEYWORDS: FEE BASIS PAYMENT
KEYWORDS: FBAAC
KEYWORDS: MPIF
KEYWORDS: 162.1
KEYWORDS: 162.7
COMPONENT/ENTRY POINT: ACTIVITY
 COMPONENT DESCRIPTION:   Call $$ACTIVITY^FBUTLMVI to retrieve any activity in
 the VistA FEE BASIS package after a specified date for a specific patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PATIENT File (#2).  
VARIABLES: FBDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   Date (no time) in FM format to check for activity
 after a given date for a given DFN.  
VARIABLES: FBACT                        TYPE: Both
 VARIABLES DESCRIPTION:   Pass by reference, will return an array of activity
 that occurred after the given FBDATE for the DFN.  Ex. FBACT(n)=DATE^TYPE OF
 ACTIVITY 
VARIABLES: $$ACTIVITY                   TYPE: Output
 VARIABLES DESCRIPTION:   Returns the number of activity items found for the
 DFN from the FBDATE.  
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA
 SUBSCRIBING DETAILS:   For the Master Veteran Index (MVI) project, a means for
 determining whether a given patient is actually deceased requires looking at 
 several other files to determine if the patient has had any type of 
 interaction with sites.  
  DATE ACTIVATED: AUG 12, 2016

NUMBER: 6421                            IA #: 6421
  DATE CREATED: JUN 20, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VAFC DOD ACCEPT SET/DISPLAY
  REMOTE PROCEDURE: VAFC DOD ACCEPT SET/DISPLAY
 GENERAL DESCRIPTION:   The Master Veteran Index (MVI) team requests access to
 the REGISTRATION remote procedure call (RPC) : VAFC DOD ACCEPT SET/DISPLAY.
 This RPC will be used to set whether a site can process Date of Death (DOD)
 messages from the MVI, and also be used to query a site to determine its
 current ability to process DOD messages from the MVI.  
  
 TAG: EN           ROUTINE:VAFCDODA 
  
 Parameters: 
      TYPE (Required) - "S" - Set the PROCESS MVI DOD UPDATE? (#1401) field 
                              in the MAS PARAMETERS (#43) file.  
                        "D" - Retrieve the PROCESS MVI DOD UPDATE? (#1401) 
                              field in the MAS PARAMETERS (#43) file.  
      SET (Optional)  - "1" for "YES" 
                        "0" for "NO" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DG
KEYWORDS: DATE OF DEATH
KEYWORDS: DOD
KEYWORDS: 43
KEYWORDS: 43.1401
KEYWORDS: MVI
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   For the Master Veteran Index (MVI) project, a mechanism
 is needed to control a sites ability to process Date of Death (DOD) messages
 from the MVI. This will provide MVI with a means for turning these messages 
 on/off in case issues arise from MPI being the authoritative source for this
 information. In addition, a mechanism is needed to determine the current state
 of DOD message processing at a site.  
  DATE ACTIVATED: AUG 10, 2016

NUMBER: 6422                            IA #: 6422
  DATE CREATED: JUN 29, 2016
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: GMVUTL1                      NAME: HMP Access to ERROR~GMVUTL1
  ID: GMVUTL1
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) uses the
 ERROR^GMVUTL1 API to mark a vital as entered in error.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 HMP developer verified HMP needs an ICR for access to GMVUTL1 API.  Custodial
 package could not review this ICR prior to HMP shutdown.  It will need to be
 reviewed by the custodial package in the future if HMP is reactivated.  
    
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: GMVUTL1
KEYWORDS: HMP
COMPONENT/ENTRY POINT: ERROR
 COMPONENT DESCRIPTION:   Marks a vital measurement as entered in error.  
VARIABLES: GMVDATA                      TYPE: Input
 VARIABLES DESCRIPTION:   An array of data used to mark the vital measurement. 
  
 IEN to 120.5 ^ Incorrect date/time ^ Incorrect Reading ^ Incorrect Patient ^
 Invalid Record 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6423                            IA #: 6423
  DATE CREATED: JUL 05, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORWORR                       NAME: MBAB USE OF ORWORR APIS
  ID: ORWORR
 GENERAL DESCRIPTION:   The Warfarin Mobile App (MBAB) calls AGET^ORWORR to
 retrieve an abbreviated order list for a patient. This list is used to
 determine if the patient has a prescription for Warfarin.  
  
 ICRs #6423, 6424 and 6425 were withdrawn on 3/8/18.  ICRs were initially 
 requested on 7/5/16.  The National Patch Module does not have patches for this
 package.  It does not look like the project is active.  If these Integration
 Control Registration (ICRs) are needed, they can be resubmitted for review
 with the custodial package.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: AGET
KEYWORDS: ORWORR
KEYWORDS: MBAB
COMPONENT/ENTRY POINT: AGET
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: FILTER                       TYPE: Input
 VARIABLES DESCRIPTION:   A comma separated list of status flags to search for. 
 
VARIABLES: GROUPS                       TYPE: Input
 VARIABLES DESCRIPTION:   Display Group 
VARIABLES: DTFROM                       TYPE: Input
 VARIABLES DESCRIPTION:   Starting date for the search.  
VARIABLES: DTTHUR                       TYPE: Input
 VARIABLES DESCRIPTION:   Date to end search.  
VARIABLES: EVENT                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the Patient Event File (#100.2).  
VARIABLES: ORRECIP                      TYPE: Input
VARIABLES: REF                          TYPE: Output
 VARIABLES DESCRIPTION:   Return variable: ^TMP("ORR",$J,ORLIST,n)=IFN ^
 Display Group ^ Activity Time 
COMPONENT/ENTRY POINT: GETBYIFN
 COMPONENT DESCRIPTION:   Returns data for a single order for a patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: ORTXT                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns the fields for a single order in the format: 
           1   2    3     4      5     6   7   8   9   10     11    12 
     .LST=~IFN^Grp^ActTm^StrtTm^StopTm^Sts^Sig^Nrs^Clk^PrvID^PrvNam^ActDA 
SUBSCRIBING PACKAGE: MOBILE WARFARIN MONITORING

NUMBER: 6424                            IA #: 6424
  FILE NUMBER: 101.01                   GLOBAL ROOT: ORD(101.01
  DATE CREATED: JUL 05, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: File
  NAME: MBAB ACCESS TO THE ORDER STATUS FILE
  ID: ORD(101.01
GLOBAL REFERENCE: ORD(101.01,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Warfarin Mobile App (MBAB) extracts a list of the
 Order Status Names form the Order Status File (#101.01) using FileMan calls.  
  
 ICRs #6423, 6424 and 6425 were withdrawn on 3/8/18.  ICRs were initially 
 requested on 7/5/16.  The National Patch Module does not have patches for this
 package.  It does not look like the project is active.  If these Integration
 Control Registration (ICRs) are needed, they can be resubmitted for review
 with the custodial package.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ORDER STATUS
KEYWORDS: 101.01
KEYWORDS: MBAB
SUBSCRIBING PACKAGE: MOBILE WARFARIN MONITORING

NUMBER: 6425                            IA #: 6425
  FILE NUMBER: 100.98                   GLOBAL ROOT: ORD(100.98
  DATE CREATED: JUL 05, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: File
  NAME: MBAB ACCESS TO THE DISPLY GROUP FILE
  ID: ORD(100.98
GLOBAL REFERENCE: ORD(100.98,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: MIXED NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Warfarin Mobile App (MBAB) accesses the Display
 Group file (#100.98) to retrieve the Display Group Name and Mixed Name using
 FileMan.  
  
 ICRs #6423, 6424 and 6425 were withdrawn on 3/8/18.  ICRs were initially 
 requested on 7/5/16.  The National Patch Module does not have patches for this
 package.  It does not look like the project is active.  If these Integration
 Control Registration (ICRs) are needed, they can be resubmitted for review
 with the custodial package.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: 100.98
KEYWORDS: MBAB
KEYWORDS: DISPLAY GROUP
SUBSCRIBING PACKAGE: MOBILE WARFARIN MONITORING

NUMBER: 6426                            IA #: 6426
  DATE CREATED: JUL 06, 2016
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSUTLA2
  NAME: HMP ACCESS TO ORDRNUM~PSSUTLA2  ID: PSSUTLA2
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the PSS
 API, ORDRNUM^PSSUTLA2 in order to retrieve the order number for a specific 
 inpatient med order.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12  
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the  access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 *********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
KEYWORDS: ORDRNUM
KEYWORDS: PSSUTLA2
COMPONENT/ENTRY POINT: ORDRNUM
 COMPONENT DESCRIPTION:   Returns the corresponding order number IEN for the
 order in the Order File (#100).  
VARIABLES: PSSDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: PSSTYPE                      TYPE: Input
 VARIABLES DESCRIPTION:   Type of inpatient med order. A numeric 5 for Unit
 dose or the literal "IV" for IV.  
VARIABLES: PSSORPK                      TYPE: Input
 VARIABLES DESCRIPTION:   Inpatient Medications order number from either the
 Unit Dose or IV multiple.  
VARIABLES: PSSORIEN                     TYPE: Output
 VARIABLES DESCRIPTION:   The IEN for the corresponding order number from the
 Order File (#100).  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: OCT 13, 2017

NUMBER: 6427                            IA #: 6427
  DATE CREATED: JUL 14, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORWDAL32                     NAME: HMP USE OF EDITSAVE~ORWDAL32
  ID: ORWDAL32
 GENERAL DESCRIPTION:   The Enterprise Health Management Platform (HMP) is
 calling EDITSAVE^ORWDAL32 in order to save allergy or adverse reaction data
 for a patient.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ORWDAL32
KEYWORDS: EDITSAVE
KEYWORDS: HMP
COMPONENT/ENTRY POINT: EDITSAVE
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number for the entry to be edited.
 If a new allergy this will be zero.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   An array containing the allergy or adverse reaction
 data.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6428                            IA #: 6428
  DATE CREATED: JUL 14, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORCHECK
  NAME: HMP USE OF GETXTRA~ORCHECK      ID: ORCHECK
 GENERAL DESCRIPTION:   The Enterprise Health Management Platform (HMP) uses
 GETXTRA^ORCHECK to retrieve any extra lines used for order checks.  
   
 **NOTE: This ICR is for HMP use only! 
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12  
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the  access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 *********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: ORCHECK
KEYWORDS: GETXTRA
KEYWORDS: HMP
COMPONENT/ENTRY POINT: GETXTRA
VARIABLES: XTRA1                        TYPE: Input
 VARIABLES DESCRIPTION:   Extra order check to be made for the order.  
VARIABLES: XTRA2                        TYPE: Input
 VARIABLES DESCRIPTION:   Extra order check for the order.  
VARIABLES: OUT                          TYPE: Output
 VARIABLES DESCRIPTION:   Array of extra lines for the order checks.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP 2.0 
  DATE ACTIVATED: AUG 19, 2016

NUMBER: 6429                            IA #: 6429
  FILE NUMBER: 870                      GLOBAL ROOT: HLCS(870
  DATE CREATED: JUL 18, 2016            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  NAME: PSO use of TCP/IP, Domain, and TCP/IP Port
  ID: HLCS(870
GLOBAL REFERENCE: HLCS(870,D0,0
FIELD NUMBER: .08                       FIELD NAME: DNS DOMAIN
  LOCATION: 0;8                         ACCESS: Write w/Fileman
FIELD NUMBER: 'B'                       FIELD NAME: B INDEX
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: HLCS(870,D0,400
FIELD NUMBER: 400.01                    FIELD NAME: TCP/IP ADDRESS
  LOCATION: 400;1                       ACCESS: Write w/Fileman
FIELD NUMBER: 400.02                    FIELD NAME: TCP/IP PORT
  LOCATION: 400;2                       ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   The Outpatient Pharmacy package is in need of modifying
 the DNS DOMAIN, TCP/IP ADDRESS, and TCP/IP PORT of the HL LOGICAL LINK file
 (#870). Outpatient Pharmacy will also be looking at the 'B' index for the IEN
 of the new logical link named PSORRXSEND.  
  
 This ICR is a one-time agreement for PSO*7.0*454.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
KEYWORDS: 870
KEYWORDS: PSO*7.0*454
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 6430                            IA #: 6430
  DATE CREATED: JUL 19, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: VAFCDODA                     NAME: DATE OF DEATH UPDATE CHECK
  ID: VAFCDODA
 GENERAL DESCRIPTION:   The CLINICAL INFO RESOURCE NETWORK (RG) package
 requests access to the REGISTRATION Application Program Interface (API)
 $$CHK^VAFCDODA. This API will be used to determine whether the site should
 receive and process the Date of Death update for the patient or not.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DEATH
KEYWORDS: RG
KEYWORDS: DOD
KEYWORDS: DATE OF DEATH
COMPONENT/ENTRY POINT: $$CHK
 COMPONENT DESCRIPTION:   The API will return whether the site can update Date
 of Death Information.  
   Returns: 1 (YES) or 0 (NO) 
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
 SUBSCRIBING DETAILS:   The CLINICAL INFO RESOURCE NETWORK package needs a
 mechanism to determine whether the site can update Date of Death Information.  
  DATE ACTIVATED: OCT 12, 2016

NUMBER: 6431                            IA #: 6431
  DATE CREATED: JUL 20, 2016
  CUSTODIAL PACKAGE: HEALTH MANAGEMENT PLATFORM
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HMPOR
  NAME: OR ACCESS TO HMP SUBSCRIPTION   ID: HMPOR
 GENERAL DESCRIPTION:   The Enterprise Health Management Platform (HMP) process
 to sync the data between the VistA system and the eHMP JSON Database System
 (JSON) requires date/timestamps that include seconds in order to correctly 
 sequence different events/actions on an order that occur within the same
 minute. Routines ORCSAVE, ORCSAVE2, ORWDX and ORWDXA have been modified to
 update the HMP SUBSCRIPTION FILE (#800000) when order events occur. This
 update will store the event and event date/time including seconds in the HMP
 SUBSCRIPTION FILE. All updates are made by calling APIs in the HMPOR routine.  
  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 subscribing application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
  **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
KEYWORDS: HMP SUBSCRIPTION
KEYWORDS: 800000
COMPONENT/ENTRY POINT: ADDFLAG
 COMPONENT DESCRIPTION:   Adds a flag action to an order in the HMP
 SUBSCRIPTION FILE (#800000).  
VARIABLES: HMVALS                       TYPE: Input
 VARIABLES DESCRIPTION:   Array of values, subscripted by the field #,
 passed-by-reference.  
VARIABLES: HMORIFN                      TYPE: Input
 VARIABLES DESCRIPTION:   Order IFN from the ORDER FILE (#100).  
VARIABLES: HMDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: HMORLVL                      TYPE: Input
 VARIABLES DESCRIPTION:   ^OR(100,HMPORIFN,8,X) where HMORLVL is the value of
 X.  
VARIABLES: HMPRSLT                      TYPE: Output
 VARIABLES DESCRIPTION:   Result, passed-by-reference. 1 if successful, else
 "-1^error message".  
COMPONENT/ENTRY POINT: ADDORDR
 COMPONENT DESCRIPTION:   Adds a new order in the ORDER multiple in the HMP
 SUBSCRIPTION FILE (#800000).  
VARIABLES: HMRSLT                       TYPE: Output
 VARIABLES DESCRIPTION:   return value passed-by-reference, 1 on success else
 "-1^error message".  
VARIABLES: HMPVALS                      TYPE: Input
 VARIABLES DESCRIPTION:   Array of values, subscripted by the field #,
 passed-by-reference.  
VARIABLES: HMPORIFN                     TYPE: Input
 VARIABLES DESCRIPTION:   Order IEN from the ORDERS FILE (#100).  
VARIABLES: HMDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: HMORLVL                      TYPE: Input
 VARIABLES DESCRIPTION:   ^OR(100,HMORIFN,8,X) where X is HMORLVL. 
COMPONENT/ENTRY POINT: SRVRNO
 COMPONENT DESCRIPTION:   Returns the IEN from the HMP SUBSCRIPTION FILE
 (#800000) for the default eHMP server.  
VARIABLES: DFN4SRVR                     TYPE: Output
 VARIABLES DESCRIPTION:   The IEN for the default eHMP server.  
COMPONENT/ENTRY POINT: ORDRCHK
 COMPONENT DESCRIPTION:   Function to check for the Order to be in the HMP
 SUBSCRIPTION FILE (#800000). Returns 1 if the order exists. Otherwise returns
 0.  
VARIABLES: HMORIFN                      TYPE: Input
 VARIABLES DESCRIPTION:   The IEN from the ORDER FILE (#100) for this order.  
VARIABLES: HMDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
COMPONENT/ENTRY POINT: UPDTORDR
 COMPONENT DESCRIPTION:   Updates the order in the HMP SUBSCRIPTION FILE
 (#800000).  
VARIABLES: HMRSLT                       TYPE: Output
 VARIABLES DESCRIPTION:   Return value passed-by-reference, 1 on success else
 "-1^error message".  
VARIABLES: HMVALS                       TYPE: Input
 VARIABLES DESCRIPTION:   Array of values, subscripted by field #,
 passed-by-reference.  
VARIABLES: HMORIFN                      TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the Order in the ORDER FILE (#100).  
VARIABLES: HMDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
COMPONENT/ENTRY POINT: DELORDR
 COMPONENT DESCRIPTION:   Deletes an order from the HMP SUBSCRIPTION FILE
 (#800000). Deletions only happen if the order is also deleted from the ORDER
 FILE (#100).  
VARIABLES: HMPDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: HMIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the order in the ORDER FILE (#100).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 04, 2017

NUMBER: 6432                            IA #: 6432
  DATE CREATED: JUL 22, 2016
  CUSTODIAL PACKAGE: HEALTH MANAGEMENT PLATFORM
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HMPEVNT
  NAME: GMRV ACCESS TO GMRV~HMPEVNT     ID: HMPEVNT
 GENERAL DESCRIPTION:   The GMRV VITAL MEASUREMENT FILE (#120.5) Index, AHMP
 makes a call to the GMRV^HMPEVNT API to trigger a sync activity to sync local
 VistA data with the HMP JSON Database System (JDS) when a vital measurement is
 marked as entered in error.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 subscribing application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
  **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: GMRV
KEYWORDS: HMPEVNT
COMPONENT/ENTRY POINT: GMRV
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN for the record in the GMRV VITAL MEASUREMENT FILE
 (#120.5).  
VARIABLES: ERR                          TYPE: Input
 VARIABLES DESCRIPTION:   The error reason.  
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
  DATE ACTIVATED: AUG 22, 2016

NUMBER: 6433                            IA #: 6433
  DATE CREATED: JUL 25, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORWDX                        NAME: HMP USE OF SAVE~ORWDX
  ID: ORWDX
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the
 SAVE^ORWDX API to save a new order. 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ORWDX
KEYWORDS: SAVE
KEYWORDS: HMP
COMPONENT/ENTRY POINT: SAVE
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The DUZ for the ordering provider.  
VARIABLES: LOCIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN from the HOSPITAL LOCATION FILE (#44) for the
 ordering location.  
VARIABLES: DLG                          TYPE: Input
 VARIABLES DESCRIPTION:   The internal dialog name. 
VARIABLES: ORDG                         TYPE: Input
 VARIABLES DESCRIPTION:   Order Display Group.  
VARIABLES: ORIT                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN for the Order Dialog. 
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the order in the ORDER FILE (#100).  
VARIABLES: ORDIALOG                     TYPE: Input
 VARIABLES DESCRIPTION:   An ordered array consisting of the following: 
   A map f the input screen to the dialog question subscripts returned from the
 ORWDX DLGDEF RPC. Order checks from teh ORWDXC ACCEPT RPC. These incdule: 
   ("ORCHECK") = number of order checks 
   ("ORCHECK",Piece 1,Piece 3,increment) = Piece 2 through Piece 4 of the order
 checks delimitd by the carat character.  
   ("ORTS") = treating specialty. Will be 0 (zero) is not available. Only 
 applies to inpatient locations.  
VARIABLES: ORDEA                        TYPE: Input
 VARIABLES DESCRIPTION:   Digital Signature.  
VARIABLES: ORAPPT                       TYPE: Input
 VARIABLES DESCRIPTION:   The date/time of the visit in VA FileMan format.  
VARIABLES: ORSRC                        TYPE: Input
 VARIABLES DESCRIPTION:   Order source.  
VARIABLES: OREVTDF                      TYPE: Input
 VARIABLES DESCRIPTION:   Event Default. Only used for delayed orders.  
VARIABLES: OUT                          TYPE: Output
 VARIABLES DESCRIPTION:   Returns : ORDER IEN^GRP^ORDER TIME^START TIME^STOP 
 TIME^STS^SIG^NURSE^CLERK^PROVIDER ID^PROVIDER 
 NAME^ACT^FLAGGED^[DCTYPE]^CHARTREV^DEA#^^DIGsIG^LOC^[DC ORIGINAL]^IS PENDING
 DC ORDER^IS DELAYED ORDER 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6434                            IA #: 6434
  DATE CREATED: JUL 25, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWDXA
  NAME: HMP USE OF VALID~ORWDXA         ID: ORWDXA
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the
 VALID^ORWDXA API to determine if an action is valid for an order.  
  
 **NOTE: This ICR is approved for HMP only! 
  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: ORWDXA
KEYWORDS: VALID
KEYWORDS: HMP
COMPONENT/ENTRY POINT: VALID
VARIABLES: ORID                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN for the order in the ORDER FILE (#100).  
VARIABLES: ACTION                       TYPE: Input
 VARIABLES DESCRIPTION:   Action code.  
VARIABLES: ORNP                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN for the ordering provider.  
VARIABLES: VAL                          TYPE: Output
 VARIABLES DESCRIPTION:   Null if successful otherwise returns error message.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: AUG 08, 2016

NUMBER: 6435                            IA #: 6435
  DATE CREATED: JUL 25, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWDXC
  NAME: HMP USE OF ACCEPT~ORWDXC        ID: ORWDXC
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls
 ACCEPT^ORWDXC in order when a provider accepts an order. 
  
 **NOTE: This ICR is approved for HMP only! 
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: ORWDXC
KEYWORDS: ACCEPT
KEYWORDS: HMP
COMPONENT/ENTRY POINT: ACCEPT
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: FID                          TYPE: Input
 VARIABLES DESCRIPTION:   Filler ID. Acquired by passing the selected order
 dialog IEN from the ORWDX WRLST RPC.  
VARIABLES: STRT                         TYPE: Input
 VARIABLES DESCRIPTION:   Desired date in the format Mmm DD,YYYY@HH:SS.  
VARIABLES: ORL                          TYPE: Input
 VARIABLES DESCRIPTION:   Order location. IEN from the HOSPTIAL LOCATION FILE
 (#44).  
VARIABLES: OIL                          TYPE: Input
 VARIABLES DESCRIPTION:   An order list of orderable items for radiology or
 orderable items and package infomation for pharmacy (inpatient, outpatient and
 infusion) and lab as appropriate.  
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Order IEN from the ORDER FILE (#100).  
VARIABLES: ORREN                        TYPE: Input
 VARIABLES DESCRIPTION:   Flag to indicate a renewed order. 1 = Yes, 0 = No.  
VARIABLES: OUT                          TYPE: Output
 VARIABLES DESCRIPTION:   Order Checks: Order IEN^Order Checks IEN^CDL^Message. 
  
 CDL = Clinic Danger Level.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   
  
    COMPREHENSIVE CARE COORDINATION 
    ADDED 7/20/2022, effective with DSSV*1.1 
    DSS Class 3 product 
    Document Only - Not approved by Custodial SME 
    The Comprehensive Care Coordination (C3) calls ACCEPT^ORWDXC in order 
    when a provider accepts an order. 
  DATE ACTIVATED: AUG 08, 2016

NUMBER: 6436                            IA #: 6436
  DATE CREATED: JUL 26, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWDAL32
  NAME: HMP USE OF EDITSAVE~ORWDAL32    ID: ORWDAL32
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls
 EDITSAVE^ORWDAL32 to edit allergy information or to mark an allergy as entered
 in error.  
  
 **NOTE: This ICR is for HMP only. 
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: ORWDAL32
KEYWORDS: EDITSAVE
KEYWORDS: HMP
COMPONENT/ENTRY POINT: EDITSAVE
VARIABLES: HMPIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the Allergy.  
VARIABLES: HMPDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   DATA - array of allergy data. Subscript names are
 required. 
  ("GMRACHT",0)=1 - Chart Marked indicator 
  ("GMRACHT",1)=3150603.0905 - Date/Time Chart Marked 
  ("GMRAGNT")="DIGITOXIN^9;PSNDF(50.6," - Allergy and Pointer to Allergen File 
  ("GMRAOBHX")="o^OBSERVED" - (O)bserved or (H)istorical 
  ("GMRAORIG")=10000000224 - Pointer to VA DRUG CLASS File (50.605) 
  ("GMRAORDT")=3150603.0805 - Allergy assessmant date and time. 
  ("GMRASEVR")=2 - Severity of Allergy. 1=Mild, 2=Moderate, 3=Severe 
  ("GMRATYPE")="D^Drug" - Type of Allergen (F)ood or (D)rug 
  ("GMRANATR")="A^Allergy" - Mechanism of Allergy (A)llergy, (P)harmacologic,
 (U)nknown.  
  ("GMRASYMP",0)=2 - Number of Symptoms 
  ("GMRASYMP",1)="2^ITCHING,WATERING EYES" - IEN and Description of Symptom 1 
  ("GMRASYMP",2)="133^RASH" - IEN and Description of Symptom 2 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: AUG 22, 2016

NUMBER: 6437                            IA #: 6437
  DATE CREATED: AUG 02, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORQPTQ2
  NAME: HMP USE OF CLINPTS2~ORQPTQ2     ID: ORQPTQ2
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) makes a call
 to CLINPTS2^ORQPTQ2 to retrieve a list of up to 200 patients that have 
 appointments at a specified clinic for a specified date range.  
  
 **NOTE: This ICR is approved for HMP only.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: ORQPTQ2
KEYWORDS: CLINPTS2
KEYWORDS: HMP
COMPONENT/ENTRY POINT: CLINPTS2
 COMPONENT DESCRIPTION:   Returns a list of up to 200 patients that have
 appointments at a specified clinic for the specified date range.  
VARIABLES: CLIN                         TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the clinic from the HOSPITAL LOCATION
 FILE (#44).  
VARIABLES: ORBDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   Starting date for the search.  
VARIABLES: OREDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   The ending date for the search.  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Array containing the list of patients with the
 appointment date/time.  
  
 Y(I)=DFN ^ PATIENT NAME ^CLINIC ID ^ APPT. DATE/TIME ^^^^^INP/OUT Where
 INP/OUT indicates if the patiet is in an inpatient or outpatient status.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: AUG 08, 2016

NUMBER: 6438                            IA #: 6438
  DATE CREATED: AUG 02, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORWDX                        NAME: HMP USE OF LOCK AND UNLOCK ORWDX
  ID: ORWDX
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the
 LOCK^ORWDX and UNLOCK^ORWDX APIs to lock and unlock a patient record as a new
 order is entered for the patient.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: LOCK
KEYWORDS: UNLOCK
KEYWORDS: ORWDX
KEYWORDS: HMP
COMPONENT/ENTRY POINT: LOCK
 COMPONENT DESCRIPTION:   Locks the specified patient record.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 if lock is successful.  
COMPONENT/ENTRY POINT: UNLOCK
 COMPONENT DESCRIPTION:   Unlocks the patient record.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6439                            IA #: 6439
  DATE CREATED: AUG 02, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORWDX
  NAME: HMP USE OF LOCKORD AND UNLKORD IN ORWDX
  ID: ORWDX
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls
 LOCKORD^ORWDX and UNLKORD^ORWDX to lock and unlock an order in the ORDER FILE
 (#100) when saving or editing an order.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: LOCKORD
KEYWORDS: UNLKORD
KEYWORDS: ORWDX
KEYWORDS: HMP
COMPONENT/ENTRY POINT: LOCKORD
 COMPONENT DESCRIPTION:   Locks the Order in the ORDER FILE (#100).  
VARIABLES: ORDER                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the order in the ORDER FILE (#100).  
VARIABLES: OK                           TYPE: Output
 VARIABLES DESCRIPTION:   Returns a 1 if the lock is successful.  
COMPONENT/ENTRY POINT: UNLKORD
 COMPONENT DESCRIPTION:   Unlocks the order in the ORDER FILE (#100).  
VARIABLES: ORDER                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN for the order in the ORDER FILE (#100).  
VARIABLES: OK                           TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6440                            IA #: 6440
  DATE CREATED: AUG 02, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWDX
  NAME: HMP USE OF ORWDX APIs           ID: ORWDX
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls
 SEND^ORWDX to sign an order.  
  
 **NOTE: This ICR is for HMP use only! 
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: SEND
KEYWORDS: VALIDSIG
KEYWORDS: ORWDX
KEYWORDS: HMP
COMPONENT/ENTRY POINT: SEND
 COMPONENT DESCRIPTION:   Signs an order.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: ORNP                         TYPE: Input
 VARIABLES DESCRIPTION:   Provider siging the order. This is IEN for the
 provider in the NEW PERSON FILE (#200).  
VARIABLES: ORL                          TYPE: Input
 VARIABLES DESCRIPTION:   The Clinic where the order was written. This is the
 IEN for the clinic in the HOSPITAL LOCATION FILE (#44).  
VARIABLES: ES                           TYPE: Input
 VARIABLES DESCRIPTION:   The user's electronic signature code.  
VARIABLES: ORWREC                       TYPE: Input
 VARIABLES DESCRIPTION:   An array containing: ORIFN;ACTION ^ SIGNATURE STS ^
 RELEASE STS ^ NATURE OF ORDER 
COMPONENT/ENTRY POINT: LOCK
 COMPONENT DESCRIPTION:   Locks a specified patient record.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 is lock is successful.  
COMPONENT/ENTRY POINT: UNLOCK
 COMPONENT DESCRIPTION:   Unlocks a patient record.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1.  
COMPONENT/ENTRY POINT: LOCKORD
 COMPONENT DESCRIPTION:   Locks the Order record in the ORDER FILE (#100).  
VARIABLES: ORIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the order in the ORDER FILE (#100).  
VARIABLES: OK                           TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 is lock is successful.  
COMPONENT/ENTRY POINT: UNLKORD
 COMPONENT DESCRIPTION:   Unlocks an order record in the ORDER FILE (#100).  
VARIABLES: ORIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the order in the ORDER FILE (#100).  
VARIABLES: OK                           TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1.  
COMPONENT/ENTRY POINT: SAVE
 COMPONENT DESCRIPTION:   Saves an order in the ORDER FILE (#100).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The Patient DFN.  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The DUZ for the ordering provider.  
VARIABLES: LOCIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   The IEN from the HOSPITAL LOCATION FILE (#44) for the
 ordering location.  
VARIABLES: DLG                          TYPE: Input
 VARIABLES DESCRIPTION:   The order dialog.  
VARIABLES: ORDG                         TYPE: Input
 VARIABLES DESCRIPTION:   The Order Display Group.  
VARIABLES: ORIT                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN for the Order Dialog.  
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the order.  
VARIABLES: ORDIALOG                     TYPE: Input
 VARIABLES DESCRIPTION:   An ordered array consisting of the following: 
  
 A map of the input screen to the dialog question subscripts returned from the
 ORWDX DGLDEF RPC. Order checks from the ORWDXC ACCEPT RPC. These include: 
 ("ORCHECK") = Number of order checks ("ORCHECK",Piece 1,Piece 3,increment) =
 Piece 2 through Piece 4 of the order checks delimited by the carat character.  
 ("ORTS") = Treating speciality. Will be 0 (zero) if not available. Only 
 applies to inpatient locations.  
VARIABLES: ORDEA                        TYPE: Input
 VARIABLES DESCRIPTION:   User's digital signature.  
VARIABLES: ORAPPT                       TYPE: Input
 VARIABLES DESCRIPTION:   The date/time of the visit in VA FileMan format.  
VARIABLES: ORSRC                        TYPE: Input
 VARIABLES DESCRIPTION:   Order source.  
VARIABLES: OREVTDF                      TYPE: Input
 VARIABLES DESCRIPTION:   Event default. Only used for delayed orders.  
VARIABLES: OUT                          TYPE: Output
 VARIABLES DESCRIPTION:   Returns: ORDER IEN ^ GRP ^ ORDER TIME ^ START TIME ^
 STOP TIME ^ STS ^ SIG ^ NURSE ^ CLERK ^ PROVIDER ID ^ PROVIDER NAME ^ ACT ^
 FLAGGED ^ [DC TYPE] ^ CHARTREV ^ DEA# ^^ DIGSIG ^ LOC ^ [DC ORIGINAL] ^IS
 PENDING DC ORDER ^ IS DELAYED ORDER 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   This functionality is being released in HMP 2.0 
  DATE ACTIVATED: AUG 19, 2016

NUMBER: 6441                            IA #: 6441
  DATE CREATED: AUG 02, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWPCE4
  NAME: HMP USE OF LEX~ORWPCE4          ID: ORWPCE4
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the
 LEX^ORWPCE4 API to retrieve a list of Lexicon information.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: LEX
KEYWORDS: ORWPCE4
KEYWORDS: HMP
COMPONENT/ENTRY POINT: LEX
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   The search text entered by the user.  
VARIABLES: APP                          TYPE: Input
 VARIABLES DESCRIPTION:   The Lexicon APP parameter for the Problem List
 subset.  
VARIABLES: ORDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional date of interest.  
VARIABLES: ORXTND                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional Bolean flag specifying whether or not to use
 an extended search.  
VARIABLES: ORINCSYN                     TYPE: Input
 VARIABLES DESCRIPTION:   Optional boolean flag specifying whether or not to
 include synonyms for SNOMED CT Concepts.  
VARIABLES: LST                          TYPE: Output
 VARIABLES DESCRIPTION:   Returns: LST=Local array name passed by reference
 which contains search result set as: <lvn>(1..n)=LEXIEN ^ PREFTEXT ^ CODESYS ^
 CONCEPTID ^ ICDVER ^ DESIGID ^ PARENTSUBSCRIPT 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: AUG 05, 2016

NUMBER: 6442                            IA #: 6442
  DATE CREATED: AUG 02, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWU
  NAME: HMP USE OF VALIDSIG~ORWU        ID: ORWU
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls
 VALIDSIG^ORWU in check to be sure the electronic signature code entered by the
 user is valid.  
  
 **NOTE: This ICR is only approved for HMP. 
  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: ORWU
KEYWORDS: VALIDSIG
KEYWORDS: HMP
COMPONENT/ENTRY POINT: VALIDSIG
VARIABLES: ES                           TYPE: Input
 VARIABLES DESCRIPTION:   The electronic signature code entered by the user.  
VARIABLES: ESOK                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 is valid.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: AUG 08, 2016

NUMBER: 6443                            IA #: 6443
  DATE CREATED: AUG 03, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORWPCE1                      NAME: HMP USE OF DQSAVE~ORWPCE1
  ID: ORWPCE1
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) makes a call
 to  DQSAVE^ORWPCE1 in order to save encounter data.  
  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 The CPRS team did not approve access to the ORWPCE SAVE RPC or DQSAVE~ORWPCE1
 API.  One reason is because the code sets the source as TIU which can cause
 downstream confusion.  The API is called from the HMP WRITEBACK ENCOUNTERS
 RPC.  HMP stated the HMP WRITEBACK ENCOUNTERS RPC is not used but it is an RPC
 in the HMP UI CONTEXT option.  The call to DQSAVE~ORWPCE1 API is found in
 routine HMPWB5.  
  
 If HMP is reactivated in the future, the HMP project team should  review this
 ICR with the Custodial Package.  OR*3.0*377 will be modifying this API.  HMP
 may need to modify HMP to remove the HMP WRITEBACK ENCOUNTERS RPC from the
 context option and the call to ORWPCE1 routine.  
  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: DQSAVE
KEYWORDS: ORWPCE1
KEYWORDS: HMP
COMPONENT/ENTRY POINT: DQSAVE
 COMPONENT DESCRIPTION:   DQSAVE doesn't have parameters, however the following
 variables have to be defined: 
  
  Input 
   IEN = record to be updated 
   DFN = patient IEN 
   DATA(0) - input format - string - Main delimiter is "^"; Subdelimiter is ";" 
     Piece 1: DFN - Patient IEN 
     Piece 2: Inpatient flag - 1 = inpatient, 0 = otherwise 
     Piece 3: Hospital location IEN 
     Piece 4: Visit/episode date 
     Piece 5: Service category 
     Piece 6: Author/dictator IEN (i.e. Provider) 
     Piece 7: Encounter type - A 2- or 3-character string as follows: 
   CPT for CPT (^AUPNVCPT; #9000010.18) 
   HF Health Factor (^AUPNVHF; #9000010.23) 
   IMM Immunization (^AUPNVIMM; #9000010.11) 
   PED Patient Education (^AUPNVPED; #9000010.16) 
   POV POV - Purpose of Visit; a.k.a Diagnosis - (^AUPNVPOV; #9000010.07) 
   SK Skin (^AUPNVSK; #9000010.12) 
   XAM Exam (^AUPNVXAM; #9000010.13) 
   DATA(n) - Encounter data - Main delimiter is "^"; Subdelimeter is ";" 
     n is an integer>0. Encounter data varies with the type of encounter (piece
 7 above) as follows: 
       CPT: CPT code^Modifier1 code;Modifier2 code;...^Quantity^Provider 
            name^Comment 
       HF: Health factor name^Level/severity code^Comment 
       IMM: ***N/A*** Immunization RPC will be invoked 
       PED: Education name^Level of understanding code^Comment 
       POV: Diag. code^Search term^EXACT "problem list items" text^Add to 
            problem list^Comment 
       SK: Skin test name^Result code^Reading^Comment 
       XAM: Exam name^Result code^Comment 
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6444                            IA #: 6444
  FILE NUMBER: 4                        GLOBAL ROOT: DIC(4,
  DATE CREATED: AUG 05, 2016            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ADD THREE FIELDS TO INSTITUTION FILE#4
  ID: DIC(4,
 GENERAL DESCRIPTION:   The VA FileMan team would like to add three (3) new
 fields to the INSTITUTION file (#4).  The new fields will be used to support
 the determination of GMT and TimeZone offset based on a given Institution 
 Entry.  
  
 Descriptions: 
 -------------
  
 4,800     LOCATION TIMEZONE      8;1 POINTER TO WORLD TIMEZONES FILE (#1.71) 
           LAST EDITED:  AUG 10, 2016 
           HELP-PROMPT:  Enter the timezone or '?' to list timezones 
           DESCRIPTION:  This is the timeZone of this specific location.  
  
 4,801     COUNTRY                8;2 POINTER TO COUNTRY CODE FILE (#779.004 ) 
           LAST EDITED:  AUG 15, 2016 
           HELP-PROMPT:  Enter the country, or '?' to list countries 
           DESCRIPTION:  Country of this location.  
  
 4,802     TIMEZONE EXCEPTION     8;3 SET    '0' FOR SST Only; 
           LAST EDITED:  AUG 09, 2016 
           HELP-PROMPT:  Enter 0 if this is for Standard Time only.  
           DESCRIPTION:  This location does not follow the TimeZone and country
 timeframe changes therefore only follows STANDARD time. Example: Some
 locations in the USA do not follow the change to DAYLIGHT SAVINGS but remain
 STANDARD all year long. Those locations would need this exception defined. 
 Puerto Rico's TimeZone is Atlantic which is also used by Canada, Dominican
 Republic, and Bermuda.  Canada and Bermuda change timeframes and Puerto Rico
 and Dominican Republic do not.  A location in Puerto Rico or Dominican
 Republic would need to have the exception field set to SST only.  
  
 ----------
  
 The three fields will be sent out to the sites via the VA FILEMAN patch 
 DI*22.2*2.  We will only send the three fields (partial), not the entire 
 Institution DD in KIDS. These fields will be maintained via the FORUM process. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FILEMAN
KEYWORDS: DATA DICTIONARY
KEYWORDS: FIELDS
KEYWORDS: UTC
KEYWORDS: INSTITUTION
SUBSCRIBING PACKAGE: 1
  DATE ACTIVATED: AUG 17, 2016

NUMBER: 6445                            IA #: 6445
  DATE CREATED: AUG 05, 2016            CUSTODIAL PACKAGE: 1
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DIUTC
  NAME: DIUTC                           ID: DIUTC
 GENERAL DESCRIPTION:   This Coordinated Universal Time (UTC) API will convert
 a FileMan date/time into Greenwich Mean Time (GMT) with a time zone offset
 based on various input values entered by the user or the default institution
 in the DUZ(2) variable.  
  
 The format of the default output will be a GMT represented in standard FileMan
 date/time format and an internal three digit time zone offset appended to the
 end.  The calculation for the internal offset is the external offset converted
 to minutes, then divided by 5, and then added to 500.  So -07:00 is -420
 minutes, then divided by 5 is -84, and added to 500 is 416.  
  
 There may be other output variables based on the value of the EXT input 
 parameter.  The details for the other output values are documented in the 
 $$UTC variable below.  
  
 To determine the offset, the API needs to have a TimeZone and Country.  These
 values are determined using the following algorithm: 
  
 1.      No optional input parameters are passed in.  The user's default 
 Institution will be used based on the DUZ(2) variable.  The TimeZone and 
 Country are determined by the new fields in the Institution file.  
  
 2.      If only Institution is passed in as an input parameter, the TimeZone
 and Country are determined by the new fields in the Institution file.  
  
 3.      The TimeZone and Country parameters are both passed in as input 
 parameters.  
  
  
 The UTC API will return an error for any of the following conditions: 
  
 1.      If the TimeZone or Country cannot be determined from any of the 
 methods documented above, an error will be returned. 
  
 2.      If the TimeZone parameter is passed in without Country parameter or
 the Country parameter is passed in without a TimeZone parameter, an error will
 be returned.  
  
 3.      If the Institution parameter is passed in with either the TimeZone or
 Country parameter, an error will be returned.  
  
 4.      Once the TimeZone and Country are determined, they will be validated
 for consistency.  An error will be returned if they are inconsistent e.g. if
 user passes in TimeZone = "Australian Eastern Time" and Country="Mexico", the
 UTC API will return an error.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: UTC
KEYWORDS: API
KEYWORDS: FILEMAN
KEYWORDS: DIUTC
COMPONENT/ENTRY POINT: UTC(DTM,TMZ,INST,CNTRY,EXT)
VARIABLES: DTM                          TYPE: Input
 VARIABLES DESCRIPTION:   This required input parameter is a standard internal
 or external FileMan DateTime. The Time portion of the input is required.  The
 NOW input parameter is based on the current system time.  If NOW is passed in
 with a TimeZone and Country that is different than the system's TimeZone and 
 Country, inconsistent output may occur.  
VARIABLES: TMZ                          TYPE: Input
 VARIABLES DESCRIPTION:   This optional input parameter is Time Zone.  It can
 be either be a pointer to the WORLD TIMEZONES (#1.71) file or value from the
 NAME (#.01) field if the WORLD TIMEZONES (#1.71) file  (e.g., EASTERN).  
VARIABLES: INST                         TYPE: Input
 VARIABLES DESCRIPTION:   This optional input parameter is a pointer to the
 INSTITUTION (#4) file.  
VARIABLES: CNTRY                        TYPE: Input
 VARIABLES DESCRIPTION:   This optional input parameter is a pointer to the
 COUNTRY CODE (#779.004) file or a valid entry from the CODE (#.01) field or
 the upper-cased DESCRIPTION (#2) field of the COUNTRY CODE (#779.004) file.  
VARIABLES: EXT                          TYPE: Input
 VARIABLES DESCRIPTION:   This optional input parameter is an indicator whether
 to return the default output (GMT+offset in internal format) or to include
 extended output return values.  If the EXT parameter is null or missing, only
 the default value is outputted.  If the EXT parameter is 1, additional values 
 are returned as documented in the $$UTC parameter below.  
VARIABLES: $$UTC                        TYPE: Output
 VARIABLES DESCRIPTION:   If the EXT input parameter is null, zero, or missing,
 then the default output (GMT+offset in internal format) is returned.  
  
 If the EXT input parameter is set to 1, then the output is multiple caret '^'
 delimited pieces: 
  
 Piece 1: GMT+offset in internal format (e.g, 3160105.080715416) 
  
 Piece 2: GMT+offset in external format (e.g., JAN 5,2016@08:07:15 (UTC-7:00) 
  
 Piece 3: Offset in external format (e.g., -7:00) 
  
 Piece 4: Time zone (e.g., EASTERN STANDARD TIME, ESTONIA STANDARD TIME) 
  
 Piece 5: Country Name (e.g., UNITED STATES, FRANCE) 
  
 Piece 6: Time zone abbreviation (e.g., EST, PST) 
  
 Piece 7: Timeframe (e.g., DAYTLIGHT, STANDARD, SUMMER) 
  
 Piece 8: Institution Name 
  DATE ACTIVATED: JUN 23, 2017

NUMBER: 6446                            IA #: 6446
  FILE NUMBER: 63                       GLOBAL ROOT: LR(
  DATE CREATED: AUG 10, 2016            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: File
  NAME: HMP ACCESS TO THE LAB DATA FILE
  ID: LR(
GLOBAL REFERENCE: LR(D0,SP,D1,.05,D2,0
FIELD NUMBER: 1                         FIELD NAME: TIU ENTRY POINTER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,CY,D1,.05,D2,0
FIELD NUMBER: 1                         FIELD NAME: TIU ENTRY POINTER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,EM,D1,.05,D2,0
FIELD NUMBER: 1                         FIELD NAME: TIU ENTRY POINTER
  LOCATION: 0;2                         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,CY,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,.1,D2,0
FIELD NUMBER: .01                       FIELD NAME: SPECIMEN
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,101,D1,0
FIELD NUMBER: 1                         FIELD NAME: TIU ENTRY POINTER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform is doing direct
 global reads in the Lab Data File (#63) to get the TIU ENTRY POINTER from TIU
 REFERENCE DATE/TIME - X where X is the type of report. HMP loops thru 
 ^LR(D0,HMPSUB,D1,.05 and gets the value in the second field on the 
 ^LR(D0,HMPSUB,D1,.05,D2,0) node (HMPSUB is the type of report). The field is a
 pointer to the TIU DOCUMEMNT FILE (#8925). This value is then used to lookup
 the enter in TIU DOCUMENT FILE (#8925) to get the name of the TIU Document. 
  
 HMP also accesses the data nodes, LR(D0,HMPSUB,D1,.1,D2,0 to get the .01
 field, SPECIMENT. 
  
 This data is collected during the pateint sync processes that sync the local
 VistA patient data with the HMP JSON Database System (JDS).  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 Discussions between the Lab package resources and HMP contacts identified 
 possible concerns that eHMP may be getting Lab updates from the protocol but
 may not be getting 'AP' updates they are expecting.  It was also noted AP
 orders are not currently part of CPRS.  EHMP was also asked if they knew that
 TIU document names are nationally standardized and there is a 1:1 correlation
 between the API section and the corresponding TIU Document definition.  It was
 also noted that not all sites use electronic signature so their AP reports are
 stored in the Lab Data file.  
  
 These questions and issues were not resolved prior to HMP shutdown on 10/27/17
 and the ICR was not activated.  It will be retired as part of the HMP shutdown
 process.  If HMP is reactivated in the future, the access provided by this ICR
 should be reviewed with the custodial application to assure HMP is getting the
 Lab data the application needs.  
  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: LAB DATA
KEYWORDS: HMP
KEYWORDS: 63
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6447                            IA #: 6447
  DATE CREATED: AUG 16, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: HMP CALL TO ORCNOTE GET TOTAL RPC
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the
 ORCNOTE GET TOTAL RPC in order to retrieve the number of progress notes for a
 patient.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 Use of this RPC was disapproved by CPRS on 11/3/16.  However the RPC is an RPC
 in the HMP UI CONTEXT option.  This ICR will be retired with an expiration
 date of 10/27/17 as part of the HMP shut down process.  
  
 If HMP is reactivated in the future, the HMP project team will need to work
 with the CPRS team to resolve this issue.  
  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
KEYWORDS: GET TOTAL
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6448                            IA #: 6448
  DATE CREATED: AUG 16, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQPL ADD SAVE
  REMOTE PROCEDURE: ORQQPL ADD SAVE
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) calls the ORQQPL ADD SAVE RPC to
 save a new record in the PROBLEM FILE (#9000011).  
   
 **NOTE: This ICR is for HMP only.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: NOV 08, 2016

NUMBER: 6449                            IA #: 6449
  DATE CREATED: AUG 16, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQPL DELETE
  REMOTE PROCEDURE: ORQQPL DELETE
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) calls the ORQQPL DELETE RPC to 
 delete an entry in the PROBLEM FILE (#9000011).  
   
 **NOTE: This ICR is for HMP only.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: NOV 08, 2016

NUMBER: 6450                            IA #: 6450
  DATE CREATED: AUG 16, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQPL EDIT LOAD
  REMOTE PROCEDURE: ORQQPL EDIT LOAD
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) calls the ORQQPL EDIT LOAD RPC to
 retrieve an array of default fields and original fields from the PROBLEM FILE
 (#9000011).  
   
 **NOTE: This ICR is for HMP only.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: NOV 08, 2016

NUMBER: 6451                            IA #: 6451
  DATE CREATED: AUG 16, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQPL EDIT SAVE
  REMOTE PROCEDURE: ORQQPL EDIT SAVE
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) calls the ORQQPL EDIT SAVE RPC to
 save changes to an existing problem in the PROBLEM FILE (#9000011).  
   
 **NOTE: This ICR is for HMP only.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: NOV 08, 2016

NUMBER: 6452                            IA #: 6452
  DATE CREATED: AUG 16, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQPL USER PROB LIST
  REMOTE PROCEDURE: ORQQPL USER PROB LIST
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) calls the ORQQPL USER PROB LIST RPC
 to retrieve a list of user specific problems to select from.  
   
 **NOTE: This ICR is for HMP only.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: NOV 08, 2016

NUMBER: 6453                            IA #: 6453
  DATE CREATED: AUG 17, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORQQPX REMINDER DETAIL          REMOTE PROCEDURE: ORQQPX REMINDER DETAIL
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the
 ORQQPX REMINDER DETAILS RPC in order to retrieve the Clinical Reminder
 Identifier from the PCE REMINDER/MAINTENANCE ITEM FILE (#811.9).  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 Use of this RPC was disapproved by CPRS on 11/3/16.  However the RPC is an RPC
 in the HMP UI CONTEXT option.  This ICR will be retired with an expiration
 date of 10/27/17 as part of the HMP shut down process.  
  
 If HMP is reactivated in the future, the HMP project team will need to work
 with the CPRS team to resolve this issue.  
  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6454                            IA #: 6454
  DATE CREATED: AUG 17, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQVI NOTEVIT
  REMOTE PROCEDURE: ORQQVI NOTEVIT
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) calls the ORQQVI NOTEVIT RPC in 
 order to retrieve the patient's most recent vital measurements.  
   
 **NOTE: This ICR is for HMP only.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: NOV 08, 2016

NUMBER: 6455                            IA #: 6455
  DATE CREATED: AUG 17, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDAL32 ALLERGY MATCH
  REMOTE PROCEDURE: ORWDAL32 ALLERGY MATCH
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) calls the ORWDAL32 ALLERGY MATCH RPC
 to search for potential allergies for a patient. 
   
 **NOTE: This ICR is for HMP only.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: NOV 08, 2016

NUMBER: 6456                            IA #: 6456
  DATE CREATED: AUG 17, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDAL32 CLINUSER
  REMOTE PROCEDURE: ORWDAL32 CLINUSER
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) calls the ORWDAL32 CLINUSER RPC to
 determine if the user can perform cover sheet allergy actions.  
   
 **NOTE: This ICR is for HMP only.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: NOV 08, 2016

NUMBER: 6457                            IA #: 6457
  DATE CREATED: AUG 17, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDAL32 SYMPTOMS
  REMOTE PROCEDURE: ORWDAL32 SYMPTOMS
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) calls the ORWDAL32 SYMPTOMS RPC to
 retrieve a subset of symptoms.  
   
 **NOTE: This ICR is for HMP only.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: NOV 08, 2016

NUMBER: 6458                            IA #: 6458
  DATE CREATED: AUG 17, 2016
  CUSTODIAL PACKAGE: VISTA SERVICES ASSEMBLER
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XSAPXUTL
  NAME: XSAPXUTL APIs                   ID: XSAPXUTL
 GENERAL DESCRIPTION:   This ICR allows any VistA application that uses the
 VISTA SERVICES ASSEMBLER (VistA.js) Platform to call these APIs in order to
 create supported VistA.js REST services.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VISTA SERVICES ASSEMBLER
KEYWORDS: VSA
KEYWORDS: XSAPXUTL
COMPONENT/ENTRY POINT: INIT(.SOURCE,.TARGET)
 COMPONENT DESCRIPTION:   This function is the first function called by all VSA
 functions and other m service functions. The primary purpose is to initialize
 the VSA package-wide common variables.  
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) A closed global root, passd by reference, 
 containing source input parameters required by the calling function. The
 SOURCE input global array is set by the VistA Services Assembler JavaScript
 software through the cache.node interface. The input variable(s) for each
 function are set in the last subscript of the SOURCE global.  
VARIABLES: TARGET                       TYPE: Both
 VARIABLES DESCRIPTION:   (Required) A closed global root, passed by reference, 
 where the results of a VistA.js m function are returned. Errors are also
 returned in the TARGET global array.  All results for a successful, or failed,
 VistA.js function call are returned in the TARGET global node.  
COMPONENT/ENTRY POINT: INITPARM(.PARAM)
 COMPONENT DESCRIPTION:   This API is used to initialize input parameters to
 the empty string if passed in through VistA.js as a JavaScript null value.  A
 JavaScript null value is interpreted by cache.node as the string "null" 
 instead of the standard m empty string. This API will set any parameter passed
 in to the empty string if the value is "null".  
VARIABLES: PARAM                        TYPE: Both
 VARIABLES DESCRIPTION:   (Required) PARAM is an input parameter variable that
 is passed by reference to this API in order to initialize the variable value
 to be used in VistA.js m functions.  If the value of PARAM is the literal
 string "null" then it is set to the empty string.  
COMPONENT/ENTRY POINT: RESULT()
 COMPONENT DESCRIPTION:   This is the primary function to call to complete a
 VistA.js m service endpoint.  
  
 Example: Q $$RESULTS^XSAPXUTL() 
COMPONENT/ENTRY POINT: CONVERT(IN)
 COMPONENT DESCRIPTION:   The purpose of this function is to convert a value to
 a web-friendly camelCase format for a JSON key. This function converts all
 characters in the input string to lower case. If the input string contains
 spaces, the first character in the input string after a space is converted to
 upper case and all spaces are removed.  
  
 For instance, the input string of PATIENT ADDRESS would be converted to
 patientAddress.  
VARIABLES: IN                           TYPE: Input
 VARIABLES DESCRIPTION:   (Required) A string literal to be converted to
 camelCase.  
COMPONENT/ENTRY POINT: GETFILE(FILE)
 COMPONENT DESCRIPTION:   This function is a wrapper for the FILE^DID fileman
 API used to return the file name from a file number.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The file number used to lookup and return
 a file name.  
COMPONENT/ENTRY POINT: GETFLD(FILE,FIELD)
 COMPONENT DESCRIPTION:   This function is used to return the field name of a
 specific field in a file based on the file and field numbers.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The file, or sub-file, where the field
 exists.  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The field number of a file, or sub-file.  
COMPONENT/ENTRY POINT: BLDERROR(CODE,TEXT,ACTOR)
 COMPONENT DESCRIPTION:   This API is used by applications that have created
 VistA.js m services to return internal application errors in the proper
 VistA.js error format to be returned to an end user through the VistA.js
 platform.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This is the error code number from the
 DIALOG file associated with an error.  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This is a free text message associated
 with an internal application error.  
VARIABLES: ACTOR                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This is a free text value used to identify
 the actor that identified the internal application error. Typically this is
 the m routine and location the error was identifed from.  
SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS)
  DATE ACTIVATED: SEP 15, 2016

NUMBER: 6459                            IA #: 6459
  DATE CREATED: AUG 17, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDRA32 RAORDITM
  REMOTE PROCEDURE: ORWDRA32 RAORDITM
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the
 ORWDRA32 RAORDITM RPC to retrieve a subset of orderable items.  
   
 **NOTE: This ICR is for HMP and Mobile Scheduling Application Suite only.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HMP
KEYWORDS: VIA
KEYWORDS: VAR
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   HMP's subscription to this ICR expires on 10/27/17 with
 the shutdown of HMP.  HMP*2.0*12 released on 10/17/17 is an informational
 patch outlining the steps for the sites to shut down the application.  
  
 If HMP is reactivated in the future, the HMP project team should review the
 access provided by this ICR with the custodial application before reactivating
 HMP's subscription to this ICR.  See VistA Document Library (VDL) for list of
 retired HMP ICRs.  
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9. 
  DATE ACTIVATED: NOV 08, 2016

NUMBER: 6460                            IA #: 6460
  DATE CREATED: AUG 17, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: HMP CALL TO ORWLEX GETFREQ RPC
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the
 ORWLEX GETFREQ RPC to wrap the Lexicon API $$FREQ^LEXU to satisfy the
 requirements of the ICD-10-CM diagnostic search.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 Use of this RPC was disapproved by CPRS on 11/3/16.  However the RPC is an RPC
 in the HMP UI CONTEXT option.  This ICR will be retired with an expiration
 date of 10/27/17 as part of the HMP shut down process.  
  
 If HMP is reactivated in the future, the HMP project team will need to work
 with the CPRS team to resolve this issue.  
  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6461                            IA #: 6461
  DATE CREATED: AUG 17, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWPCE GETSVC                   REMOTE PROCEDURE: ORWPCE GETSVC
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the
 ORWPCE GETSVC RPC to to calculate the correct service category.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 Use of this RPC was disapproved by CPRS on 11/3/16.  However the RPC is an RPC
 in the HMP UI CONTEXT option.  This ICR will be retired with an expiration
 date of 10/27/17 as part of the HMP shut down process.  
  
 If HMP is reactivated in the future, the HMP project team will need to work
 with the CPRS team to resolve this issue.  
  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6462                            IA #: 6462
  DATE CREATED: AUG 18, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWPCE HASVISIT                 REMOTE PROCEDURE: ORWPCE HASVISIT
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the
 ORWPCE HASVISIT RPC to retrieve the status of a visit associated with a note. 
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 Use of this RPC was disapproved by CPRS on 11/3/16.  However the RPC is an RPC
 in the HMP UI CONTEXT option.  This ICR will be retired with an expiration
 date of 10/27/17 as part of the HMP shut down process.  
  
 If HMP is reactivated in the future, the HMP project team will need to work
 with the CPRS team to resolve this issue.  
  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6463                            IA #: 6463
  DATE CREATED: AUG 18, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWPCE LEXCODE                  REMOTE PROCEDURE: ORWPCE LEXCODE
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the
 ORWPCE LEXCODE RPC to retrieve the code associated with a lexicon entry.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 Use of this RPC was disapproved by CPRS on 11/3/16.  However the RPC is an RPC
 in the HMP UI CONTEXT option.  This ICR will be retired with an expiration
 date of 10/27/17 as part of the HMP shut down process.  
  
 If HMP is reactivated in the future, the HMP project team will need to work
 with the CPRS team to resolve this issue.  
  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6464                            IA #: 6464
  DATE CREATED: AUG 18, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWPCE NOTEVSTR
  REMOTE PROCEDURE: ORWPCE NOTEVSTR
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) calls the ORWPCE NOTEVSTR RPC to
 retrieve the visit location, episode begin date and the visit type for the TIU
 Document File (#8925).  
   
 **NOTE: This ICR is for HMP only.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: NOV 08, 2016

NUMBER: 6465                            IA #: 6465
  DATE CREATED: AUG 18, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWPCE SAVE                     REMOTE PROCEDURE: ORWPCE SAVE
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the
 ORWPCE SAVE RPC to save PCE information enter through the eHMP User Interface
 (UI).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6466                            IA #: 6466
  DATE CREATED: AUG 18, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWPCE SCSEL                    REMOTE PROCEDURE: ORWPCE SCSEL
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the
 ORWPCE SCSEL RPC to retrieve a list of service connected conditions that may
 be selected.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 Use of this RPC was disapproved by CPRS on 11/3/16.  CPRS recommended HMP go
 to PCE for the PXAPI routine.  However the RPC is an RPC in the HMP UI CONTEXT
 option.  On 10/27/17, HMP will be shutdown.  This ICR will be retired with an
 expiration date of 10/27/17.  
  
 If HMP is reactivated in the future, the HMP project team will need to work
 with the CPRS team to resolve this issue.  
  
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6467                            IA #: 6467
  DATE CREATED: AUG 18, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWRP COLUMN HEADERS
  REMOTE PROCEDURE: ORWRP COLUMN HEADERS
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) calls the ORWRP COLUMN HEADERS RPC
 to get a list of column headers for a ListView type of report from file
 101.24.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: NOV 07, 2016

NUMBER: 6468                            IA #: 6468
  DATE CREATED: AUG 18, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWRP3 EXPAND COLUMNS
  REMOTE PROCEDURE: ORWRP3 EXPAND COLUMNS
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) calls the ORWRP3 EXPAND COLUMNS RPC
 to load and expand nested reports defined in the OE/OR Reports file (#101.24)
 for use in the eHMP User Interface (UI).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: NOV 07, 2016

NUMBER: 6469                            IA #: 6469
  DATE CREATED: AUG 18, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWU EXTNAME                    REMOTE PROCEDURE: ORWU EXTNAME
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the
 ORWU EXTNAME RPC to get the external form of a pointer value given the IEN and
 file number.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
     
 HMP defect DE8431 was entered by the HMP project team to remove the ORWU 
 EXTNAME RPC from the HMP UI CONTEXT option.  This defect was not resolved 
 before HMP was shut down on 10/27/17. 
  
 If HMP is reactivated in the future, the HMP project team will need to reopen
 this defect to remove the RPC from the context option or ask CPRS for access
 to the ORWU EXTNAME RPC.  
        
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6470                            IA #: 6470
  DATE CREATED: AUG 18, 2016            CUSTODIAL PACKAGE: HEALTHEVET DESKTOP
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: HMP CALL TO XHD GET PARAMETER DEF LIST
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the XHD
 GET PARAMETER DEF LIST RPC to retrieve all the parameter definitions as a list
 with the IEN^NAME^DISPLAY NAME in each node of the return array.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6471                            IA #: 6471
  DATE CREATED: AUG 18, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: HMP CALL TO YTQ ALLKEYS RPC
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) calls the YTQ
 ALLKEYS RPC to retrieve a list of all security keys for a specified user.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6472                            IA #: 6472
  DATE CREATED: AUG 23, 2016            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Supported                      TYPE: Routine
  ROUTINE: LEXTRAN1
  NAME: Get Designation ID for an Expression
  ID: LEXTRAN1                          STATUS: Pending
  DURATION: Till Otherwise Agreed
KEYWORDS: GETDID
KEYWORDS: DESIGNATION
KEYWORDS: LEXTRAN1
KEYWORDS: ID
COMPONENT/ENTRY POINT: $$GETDID(SRC,IEN)
 COMPONENT DESCRIPTION:   This API returns a Designation ID for a source and an
 Expression in file 757.01 identified by an Internal Entry Number.  
  
VARIABLES: SRC                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the source of the Designation ID.  It can be 
 either an IEN from the Coding Systems file #757.03 or the Source Abbreviation
 field .01 of the Coding Systems File #757.03.  
  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is an Internal Entry Number of the Expressions 
 file #757.01.  
  
VARIABLES: $$GETDID                     TYPE: Output
 VARIABLES DESCRIPTION:   This is the Designation ID if found 
  
   Otherwise 
  
 -1^error message 
  

NUMBER: 6473                            IA #: 6473
  FILE NUMBER: 123.5                    GLOBAL ROOT: GMR(123.5,
  DATE CREATED: AUG 23, 2016
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ICR6473 - PROSTHETICS SERVICE
  ID: GMR(123.5,
GLOBAL REFERENCE: GMR(123.5,D0,INT)
FIELD NUMBER: 131                       FIELD NAME: PROSTHETICS SERVICE
  LOCATION: INT;1                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VIA needs permission to read File #123.5, field #131 to
 provide data to consuming applications.  
  
  STATUS: Active
KEYWORDS: prosthetics
KEYWORDS: VIAB
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be referencing Request Services (#123.5) file
 in VIAB ISPROSVC RPC.  
  DATE ACTIVATED: FEB 28, 2017

NUMBER: 6474                            IA #: 6474
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  DATE CREATED: AUG 23, 2016            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  NAME: PATIENT APPOINTMENT             ID: SC(
GLOBAL REFERENCE: SC(D0,S,D1,0)
FIELD NUMBER: .01                       FIELD NAME: APPOINTMENT DATE/TIME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: SC(D0,S,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: .01                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VIA needs to read File #44, field #1900 (sub-file
 #44.001) to provide data to consuming applications via a remote procedure call
 (RPC).  
  
  STATUS: Withdrawn
KEYWORDS: APPOINTMENTS
KEYWORDS: PATIENT
KEYWORDS: VIAB
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6475                            IA #: 6475
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100,
  DATE CREATED: AUG 23, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: LIST ORDERS
  ID: OR(100,
GLOBAL REFERENCE: OR(100,D0,0)
FIELD NUMBER: .02                       FIELD NAME: OBJECT OF ORDER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: PATIENT LOCATION
  LOCATION: 0;10                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: OR(100,D0,3)
FIELD NUMBER: 5                         FIELD NAME: STATUS
  LOCATION: 3;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 30                        FIELD NAME: CURRENT ACTION
  LOCATION: 3;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: DATE OF LAST ACTIVITY
  LOCATION: 3;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: OR(100,D0,.1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ORDERABLE ITEM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: OR(100,D0,8,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME ORDERED
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PROVIDER
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: SIGNED BY
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: DATE/TIME SIGNED
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 16                        FIELD NAME: RELEASE DATE/TIME
  LOCATION: 0;16                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: OR(100,'AF',
GLOBAL REFERENCE: OR(100,D0,8,D1,.1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: ORDER TEXT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VIA is using FileMan LIST^DIC and reading fields from
 File #100 to provide data to consuming applications via VIAB BMS RPC.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORDER ACTIONS
KEYWORDS: STATUS
KEYWORDS: ORDERABLE ITEMS
KEYWORDS: VIAB
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Added 11/6/19 for access to DATE TIME ORDERED (field
 .01 of OR(100,D0,8,D1,0) global reference) and ORDER TEXT (field .01 of 
 OR(100,D0,8,D1,.1,D2,0) global reference), effective with RA*5*161.  
  DATE ACTIVATED: NOV 14, 2016

NUMBER: 6476                            IA #: 6476
  FILE NUMBER: 67.1                     GLOBAL ROOT: LRT(67.1,
  DATE CREATED: AUG 23, 2016            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RESEARCH
  ID: LRT(67.1,
GLOBAL REFERENCE: LRT(67.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: IDENTIFIER
  LOCATION: 0;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LRT(67.1,D0,LR)
FIELD NUMBER: 63                        FIELD NAME: LABORATORY REFERENCE
  LOCATION: LR;1                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: LRT(67.1,'B'
GLOBAL REFERENCE: LRT(67.1,'C'
 GENERAL DESCRIPTION:   VIA needs to read File #67.1, fields .01, 9, 63 and the
 "B" and "C" cross references to provide data to consuming applications via a
 remote procedure call (RPC) VIAB EFR.  
  
  STATUS: Active
KEYWORDS: RESEARCH
KEYWORDS: VIAB
KEYWORDS: NAME
KEYWORDS: IDENTIFIER
KEYWORDS: LABORATORY REFERENCE
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   The VIAB EFR RPC was developed exclusively for the
 Embedded Fragment Registry and the data the registry obtains from the
 Baltimore VAMC. This RPC is limited for use by VIA for the Embedded Fragment
 Registry. No additional subscribers should be added to this ICR.  
  
 The EFR team supporting the Embedded Fragment Registry said the data from the 
 Research (#67.1) file is data they cannot obtain from the Corporate Data 
 Warehouse (CDW) and this process has been in place for 4-5 years. The support 
 team said the consuming application will send patient SSNs as an input 
 parameter to the VIAB EFR RPC. The EFR process prior to calling the VIA 
 service will verify the values are for human patients and not research
 animals. The RPC will use the 'C' cross reference on the Identifier field to
 identify the patient in the Research (#67.1) file and navigate to the Lab Data
 (#63) file to obtain the results associated with the patient.  
  
 The VIAB EFR RPC replaces functionality currently available through MDWS and 
 the DDR LISTER RPC. VIA has created a RPC limited to EFR that will be 
 distributed in VIAB*1*9. The VIA project manager and EFR developer may be 
 contacted for additional information.  
  DATE ACTIVATED: APR 14, 2017

NUMBER: 6477                            IA #: 6477
  FILE NUMBER: 9000010.11               GLOBAL ROOT: AUPNVIMM(
  DATE CREATED: AUG 24, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: File
  NAME: HMP ACCESS TO AUPNVIMM          ID: AUPNVIMM(
GLOBAL REFERENCE: AUPNVIMM(D0,0
FIELD NUMBER: .01                       FIELD NAME: IMMUNIZATION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Name of Immunization.  
FIELD NUMBER: .02                       FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Patient DFN.  
FIELD NUMBER: .03                       FIELD NAME: VISIT
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The pointer value to the Visit in the VISIT FILE
 (#9000010).  
GLOBAL REFERENCE: AUPNVIMM('AD'
FIELD NUMBER: .03                       FIELD NAME: VISIT
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The AD cross reference on the Visit field (#.03). This
 cross reference is used for searches by the visit pointer and internal entry
 number.  
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) requests
 access to do direct global reads of the V IMMUNIZATION FILE (#9000011.11). HMP
 does a direct global read of the Immunization file in order to check to see if
 the immunization for the visit has already been entered prior to entering a 
 new immunization for the visit. To do this HMP does a loop thru the 
 AUPNVIMM("AD" cross reference. If an entry is found in the AD cross reference,
 then a check is made to compare the immunization and patient against the data
 for the new entry. If a match is found, HMP doesn't add the immunization
 record, otherwise a new immunization is added to the file for the patient's
 visit.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
     
 Discussions between PCE and HMP stopped after 12/21/16 and temporary approval
 was not processed.  Access to AUPNVIMM was found in ENC+18 in routine HMPWB5
 and several places in routine HMPWBIM1 in Albany's DNS gold account. 
  
 If HMP is reactivated in the future, the HMP project team will need to work
 with PCE developers to resolve this issue.  
        
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
KEYWORDS: AUPNVIMM
KEYWORDS: 9000010.11
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6478                            IA #: 6478
  FILE NUMBER: 8925                     GLOBAL ROOT: TIU(8925,
  DATE CREATED: AUG 24, 2016
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: NOTEVSTR
  ID: TIU(8925,
GLOBAL REFERENCE: TIU(8925,D0,0)
FIELD NUMBER: .07                       FIELD NAME: EPISODE BEGIN DATE/TIME
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: .13                       FIELD NAME: VISIT TYPE
  LOCATION: 0;13                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: TIU(8925,D0,12)
FIELD NUMBER: 1207                      FIELD NAME: SECONDARY VISIT
  LOCATION: 12;7                        ACCESS: Read w/Fileman
FIELD NUMBER: 1211                      FIELD NAME: VISIT LOCATION
  LOCATION: 12;11                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VIA needs to read File fields #.07,.13,1207 and 1211 in
 the TIU Document (#8925) file to provide data to consuming applications via a
 remote procedure call (RPC) VIAB NOTEVSTR.  
  STATUS: Active
KEYWORDS: NOTEVSTR
KEYWORDS: VIAB
KEYWORDS: VISIT
KEYWORDS: LOCATION
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
  DATE ACTIVATED: NOV 15, 2016

NUMBER: 6479                            IA #: 6479
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100
  DATE CREATED: AUG 25, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: VIA USE OF THE ORDERS FILE      ID: OR(100
GLOBAL REFERENCE: OR(100,D0,0)
FIELD NUMBER: 4                         FIELD NAME: WHEN ENTERED
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: TO 
  LOCATION: 0;11                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This documents the Vista Integration Adapter
 application's use of the Orders file. The ICR will be used by VIAB MEDHIST RPC
 and OrderMgmtSvc - getMedHistory service.  
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ORDER
KEYWORDS: 100
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6480                            IA #: 6480
  FILE NUMBER: 100.02                   GLOBAL ROOT: ORD(100.02
  DATE CREATED: AUG 25, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: VIAB USE OF 100.02 'C' INDEX    ID: ORD(100.02
GLOBAL REFERENCE: ORD(100.02,C,$E(X,1,30),DA)
FIELD NUMBER: C                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This documents the Vista Integration Adapter
 application's use of the NATURE OF ORDER file.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6481                            IA #: 6481
  FILE NUMBER: 100.05                   GLOBAL ROOT: ORD(100.05,
  DATE CREATED: AUG 25, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: VIAB USE OF ORDER CHECK INSTANCES FILE (100.05)
  ID: ORD(100.05,
GLOBAL REFERENCE: ORD(100.05,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ORDER
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 1                         FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 2                         FIELD NAME: OCCURENCE
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 3                         FIELD NAME: USER
  LOCATION: 0;4                         ACCESS: Write w/Fileman
FIELD NUMBER: 4                         FIELD NAME: OCCURENCE DATE/TIME
  LOCATION: 0;5                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: ORD(100.05,D0,1)
FIELD NUMBER: 5                         FIELD NAME: ORDER CHECK
  LOCATION: 1;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 6                         FIELD NAME: CLINICAL DANGER LEVEL
  LOCATION: 1;2                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: ORD(100.05,D0,3,D1,0)
FIELD NUMBER: .01                       FIELD NAME: OVERRIDE REASON
  LOCATION: 0;1                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: ORD(100.05,D0,2,0,D1,0)
FIELD NUMBER: 8                         FIELD NAME: ORDER CHECK MESSAGE
  LOCATION: 0;1                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: ORD(100.05,D0,17)
FIELD NUMBER: 16                        FIELD NAME: MONOGRAPH ITEM
  LOCATION: 1                           ACCESS: Write w/Fileman
GLOBAL REFERENCE: ORD(100.05,C,X(1),$E(X(2),1,30),DA)
FIELD NUMBER: C                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This documents the Vista Integration Adapter
 application's use of the ORDER CHECK INSTANCES file.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6482                            IA #: 6482
  FILE NUMBER: 100.2                    GLOBAL ROOT: ORE(100.2
  DATE CREATED: AUG 25, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: VIAB USE OF OE/RR PATIENT EVENT FILE (100.2)
  ID: ORE(100.2
GLOBAL REFERENCE: ORE(100.2,D0,0)
FIELD NUMBER: 2                         FIELD NAME: EVENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This documents the Vista Integration Adapter
 application's use of the OE/RR PATIENT EVENT file.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6483                            IA #: 6483
  FILE NUMBER: 100.5                    GLOBAL ROOT: ORD(100.5
  DATE CREATED: AUG 25, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: VIAB USE OF OE/RR RELEASE EVENTS FILE (100.5)
  ID: ORD(100.5
GLOBAL REFERENCE: ORD(100.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TYPE OF EVENT
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DIVISION
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: EVENT ORDER DIALOG
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: ORDER SET/MENU
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: LAPSE IN #DAYS
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: MAS MOVEMENT TYPE
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: DISPLAY TEXT
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: ORDERING PARAMETERS LOCATION
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1                        FIELD NAME: SHORT NAME
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 13                        FIELD NAME: COPY ACTIVE ORDERS
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: PARENT
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This documents the Vista Integration Adapter
 application's use of the OE/RR RELEASE EVENTS file.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6484                            IA #: 6484
  FILE NUMBER: 100.98                   GLOBAL ROOT: ORD(100.98
  DATE CREATED: AUG 25, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: VIAB USE OF DISPLAY GROUP FILE (100.98)
  ID: ORD(100.98
GLOBAL REFERENCE: ORD(100.98,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: DEFAULT DIALOG
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This documents the Vista Integration Adapter
 application's use of the DISPLAY GROUP file. The ICR will be used by the
 following RPCs and services.  
   VIAB MEDHIST   OrderMgmtSvc - getMedHistory 
   VIAB IMTYPSEL  OrderMgmtSvc - getImagingTypes 
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   
  

NUMBER: 6485                            IA #: 6485
  FILE NUMBER: 101.41                   GLOBAL ROOT: ORD(101.41
  DATE CREATED: AUG 25, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: VIAB USE OF THE ORDER DIALOG FILE (101.41)
  ID: ORD(101.41
GLOBAL REFERENCE: ORD(101.41,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: DISPLAY GROUP
  LOCATION: 0;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: ORD(101.41,D0,6,D1,0)
FIELD NUMBER: .02                       FIELD NAME: DIALOG
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: ORD(101.41,D0,6,D1,1)
FIELD NUMBER: 1                         FIELD NAME: VALUE
  LOCATION: 1;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This documents the Vista Integration Adapter
 application's use of the ORDER DIALOG file. The ICR will be used by the
 following RPCs and services.  
    VIABDPS2 OISLCT  OrderMgmtSvc - getMedOrderableItemDefaults 
  
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: 101.41
KEYWORDS: 101.416
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6486                            IA #: 6486
  FILE NUMBER: 101.43                   GLOBAL ROOT: ORD(101.43
  DATE CREATED: AUG 25, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: VIA USE OF ORDERABLE ITEMS FILE (101.43)
  ID: ORD(101.43
GLOBAL REFERENCE: ORD(101.43,D0,0
FIELD NUMBER: 2                         FIELD NAME: ID 
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: ORD(101.43,D0,8
FIELD NUMBER: .01                       FIELD NAME: ORDER MESSAGE
  LOCATION: 8;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: ORD(101.43,'S.set'
 GLOBAL DESCRIPTION:   VIA obtains a list of imaging types from VIAB IMTYPSEL
 RPC. VIA traverses through the "C" cross reference of RADIOLOGY/NUCLEAR
 MEDICINE IMAGING TYPE File #79.2 and then checks for the existence of the
 entry in ^ORD(101.43,"S.set".  
  
 GENERAL DESCRIPTION:   This documents the Vista Integration Adapter
 application's use of the ORDERABLE ITEMS file. The ICR will be used by the
 following RPCs and services.  
      VIAB LOAD        OrderMgmtSvc - getLabTestSpecificParams 
      VIABDPS2 OISLCT  OrderMgmtSvc - getMedOrderableItemDefaults 
      VIAB IMTYPSEL    OrderMgmtSvc - getImagingTypes 
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: VIAB
KEYWORDS: ORD(101.43
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6487                            IA #: 6487
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: AUG 25, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VIAB READ DPT(D0,0) - FULL SUBSCRIPT
  ID: DPT(
GLOBAL REFERENCE: DPT(D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: SEX
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DATE OF BIRTH
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: MARITAL STATUS
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: RACE
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: OCCUPATION
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: RELIGIOUS PREFERENCE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: SOCIAL SECURITY NUMBER
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .091                      FIELD NAME: REMARKS
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .092                      FIELD NAME: PLACE OF BIRTH [CITY]
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .093                      FIELD NAME: PLACE OF BIRTH [STATE]
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .14                       FIELD NAME: CURRENT MEANS TEST STATUS
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .096                      FIELD NAME: WHO ENTERED PATIENT
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .097                      FIELD NAME: DATE ENTERED INTO FILE
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .098                      FIELD NAME: HOW WAS PATIENT ENTERED?
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .081                      FIELD NAME: DUPLICATE STATUS
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .082                      FIELD NAME: PATIENT MERGED TO
  LOCATION: 0;19                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .083                      FIELD NAME: CHECK FOR DUPLICATE
  LOCATION: 0;20                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .6                        FIELD NAME: TEST PATIENT INDICATOR
  LOCATION: 0;21                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
  
 This documents the Vista Integration Adapter application's use of the PATIENT
 file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA sets a variable to the 0th node of the Patient (#2)
 file record.  However the application is only using the Name (#.01) 1st piece
 and Social Security Number (#.09) 9th piece from the 0th node.  
  
 ICR needed for VIABD SAVE RPC.  
  DATE ACTIVATED: NOV 10, 2016

NUMBER: 6488                            IA #: 6488
  FILE NUMBER: 8925                     GLOBAL ROOT: TIU(8925,
  DATE CREATED: AUG 29, 2016
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HMP READ FOR SECONDARY VISIT
  ID: TIU(8925,
GLOBAL REFERENCE: TIU(8925,D0,12
FIELD NUMBER: 1207                      FIELD NAME: SECONDARY VISIT
  LOCATION: 12;7                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field is the pointer to the visit in VISIT FILE 
 (#9000010).  
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  
  
 Then Enterprise Health MGMT Platform (HMP) requests permission to do a FileMan
 read of the TIU DOCUMENT FILE (#8925) to retrieve the SECONDARY VISIT field
 (#1207) in order to pass the Visit Pointer into a call to ENCEVENT^PXAPI to
 retrieve the visit information. 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: SECONDDARY VISIT
KEYWORDS: HMP
KEYWORDS: 1207
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: AUG 30, 2016

NUMBER: 6489                            IA #: 6489
  DATE CREATED: SEP 12, 2016
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIULC1
  NAME: HMP ACCESS TO CLINDOC~TIUCL1    ID: TIULC1
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) is calling
 the CLINDOC^TIUCL1 API in order to retrieve the Clinical Document subclass for
 a specified document type.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: CLINDOC
KEYWORDS: TIUCL1
KEYWORDS: HMP
COMPONENT/ENTRY POINT: CLINDOC
 COMPONENT DESCRIPTION:   Returns the Clinical Document subclass for a given
 document type.  
VARIABLES: TIUTYP                       TYPE: Input
 VARIABLES DESCRIPTION:   Document Type.  
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN for the record in the TIU DOCUMENT FILE (#8925).  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: SEP 14, 2016

NUMBER: 6490                            IA #: 6490
  DATE CREATED: SEP 12, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORWLEX                       NAME: HMP CALL TO GETFREQ~ORWLEX
  ID: ORWLEX
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) requests
 temporary approval to call GETFREQ^ORWLEX to check the frequency of use of
 keywords contained in a search string. In patch HMP*2.0*2, HMP makes a call
 the call to GETFREQ^ORWLEX. After reviewing the code, HMP is changing this
 call to call the FREQ^LEXU API directly.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 06, 2017
KEYWORDS: ORWLEX
KEYWORDS: GETFREQ
KEYWORDS: HMP
COMPONENT/ENTRY POINT: GETFREQ
VARIABLES: ORSCHTX                      TYPE: Input
 VARIABLES DESCRIPTION:   The text string used for the search.  
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   Results from the search.  
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6491                            IA #: 6491
  FILE NUMBER: 8932.1                   GLOBAL ROOT: USC(8932.1,
  DATE CREATED: SEP 15, 2016            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: PERSON CLASS file (#8932.1) maint.
  ID: USC(8932.1,
GLOBAL REFERENCE: USC(8932.1,
 GLOBAL DESCRIPTION:   The USC global contains the PERSON CLASS file (#8932.1) 
 GENERAL DESCRIPTION:   As part of the VHA standardization of VistA files the
 PERSON CLASS file (#8932.1) will be passed to the Standards & Terminology
 Services Team (STS) for maintenance of data.  This will happen with the
 release of patch XU*8.0*671.  This is for file data maintenance only.  The
 PERSON CLASS file (#8932.1) will remain within the KERNEL names/number space.  
  
 Lexicon Utility has all privileges as though it were the custodial package.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PERSON CLASS

NUMBER: 6492                            IA #: 6492
  FILE NUMBER: 665.72                   GLOBAL ROOT: RMPO(665.72
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: HOME OXYGEN TRANSACTIONS FILE ACCESS
  ID: RMPO(665.72
GLOBAL REFERENCE: RMPO(665.72,'AC'
 GLOBAL DESCRIPTION:   Cross-reference 'AC'  Used to read by PROSTHETICS
 APPLIANCE REPAIR 
  
 This cross reference is checked in three instances: 
      1) to filter Home Oxygen transactions out of the list of 
         Appliance Transactions for a patient; 
      2) to filter Home Oxygen transactions out of the list of HISA 
         transactions for a patient; and 
      3) to ensure that only Home Oxygen transactions are included 
         in the list of Home Oxygen transactions for a patient.  
  
    This check is in the following format: 
        $D(^RMPO(665.72,"AC",IEN660)) or 
        '$D(^RMPO(665.72,"AC",IEN660))    
    where IEN660 is the IEN of the Record of Pros Appliance/Repair 
    (#660).  
 GENERAL DESCRIPTION:   
    The Advanced Prosthetics Acquisition Tool (APAT) requests permission to 
    check for the existence of the "AC" cross reference of the 
    ^RMPO(665.72 file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUL 30, 2020

NUMBER: 6493                            IA #: 6493
  FILE NUMBER: 6914                     GLOBAL ROOT: ENG(6914)
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: EQUIPMENT INV. FILE ACCESS
  ID: ENG(6914)
GLOBAL REFERENCE: ENG(6914,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ENTRY NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 3                         FIELD NAME: MFGR.EQUIPMENT NAME
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2                         FIELD NAME: PARENT SYSTEM
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 7                         FIELD NAME: TYPE OF ENTRY
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 9                         FIELD NAME: LOCKOUT REQUIRED?
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: .5                        FIELD NAME: ENTERED BY
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: .6                        FIELD NAME: DATE ENTERED
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,1)
FIELD NUMBER: 6                         FIELD NAME: EQUIPMENT CATEGORY
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 4                         FIELD NAME: MODEL
  LOCATION: 1;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 5                         FIELD NAME: SERIAL #
  LOCATION: 1;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: MANUFACTURER
  LOCATION: 1;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 4.1                       FIELD NAME: MODEL(C)
  LOCATION: 1;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 5.1                       FIELD NAME: SERIAL #(C)
  LOCATION: 1;6                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,2)
FIELD NUMBER: 10                        FIELD NAME: VENDOR POINTER
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 11                        FIELD NAME: PURCHASE ORDER #
  LOCATION: 2;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 12                        FIELD NAME: TOTAL ASSET VALUE
  LOCATION: 2;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 13                        FIELD NAME: ACQUISITION DATE
  LOCATION: 2;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 14                        FIELD NAME: WARRANTY EXP. DATE
  LOCATION: 2;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 15                        FIELD NAME: LIFE EXPECTANCY
  LOCATION: 2;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 17                        FIELD NAME: NXRN #
  LOCATION: 2;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 18                        FIELD NAME: CATEGORY STOCK NUMBER
  LOCATION: 2;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 19                        FIELD NAME: CMR
  LOCATION: 2;9                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 16                        FIELD NAME: REPLACEMENT DATE
  LOCATION: 2;10                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 12.5                      FIELD NAME: LEASE COST
  LOCATION: 2;12                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 23                        FIELD NAME: PHYSICAL INVENTORY DATE
  LOCATION: 2;13                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 13.5                      FIELD NAME: ACQUISITION SOURCE
  LOCATION: 2;14                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,3)
FIELD NUMBER: 20                        FIELD NAME: USE STATUS
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 21                        FIELD NAME: SERVICE POINTER
  LOCATION: 3;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 20.5                      FIELD NAME: TURN-IN DATE
  LOCATION: 3;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 20.1                      FIELD NAME: ACQUISITION METHOD
  LOCATION: 3;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 24                        FIELD NAME: LOCATION
  LOCATION: 3;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 25                        FIELD NAME: VA PM NUMBER
  LOCATION: 3;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 26                        FIELD NAME: LOCAL IDENTIFIER
  LOCATION: 3;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 24.5                      FIELD NAME: PREVIOUS LOCATION
  LOCATION: 3;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 27                        FIELD NAME: JCAHO
  LOCATION: 3;9                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 28                        FIELD NAME: BAR CODE LABEL DATE
  LOCATION: 3;10                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 22                        FIELD NAME: DISPOSITION DATE
  LOCATION: 3;11                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 31                        FIELD NAME: DISPOSITION METHOD
  LOCATION: 3;12                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 32                        FIELD NAME: DISPOSITION VALUE
  LOCATION: 3;13                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 31.5                      FIELD NAME: ORIGINAL ASSET VALUE
  LOCATION: 3;15                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 53                        FIELD NAME: CONDITION CODE
  LOCATION: 3;16                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: RESPONSIBLE SHOP
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: TECHNICIAN
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2.6                       FIELD NAME: SKIP MONTHS
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2.7                       FIELD NAME: CRITICALITY
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,4,D1,2,D2,0)
FIELD NUMBER: .01                       FIELD NAME: FREQUENCY
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: HOURS (Estimated)
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2                         FIELD NAME: MATERIAL COST (Estimated)
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 3                         FIELD NAME: LEVEL
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 4                         FIELD NAME: PROCEDURE
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 5                         FIELD NAME: STARTING YEAR (4 numerics)
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,5,D1,0)
FIELD NUMBER: .01                       FIELD NAME: COMMENTS
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,6,D1,0)
FIELD NUMBER: .01                       FIELD NAME: HISTORY REFERENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: W.O. REFERENCE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2                         FIELD NAME: PM STATUS
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 3                         FIELD NAME: HOURS SPENT
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 4                         FIELD NAME: LABOR $
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 5                         FIELD NAME: MATERIAL $
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 6                         FIELD NAME: VENDOR $
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 7                         FIELD NAME: WORKER
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 9                         FIELD NAME: WORK PERFORMED
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,7)
FIELD NUMBER: 19.5                      FIELD NAME: SERVICE CONTRACT
  LOCATION: 7;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 19.6                      FIELD NAME: SERVICE CONTRACT COST
  LOCATION: 7;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,8)
FIELD NUMBER: 33                        FIELD NAME: CONTROLLED ITEM?
  LOCATION: 8;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 34                        FIELD NAME: INVESTMENT CATEGORY
  LOCATION: 8;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 35                        FIELD NAME: FUND CONTROL POINT
  LOCATION: 8;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 38                        FIELD NAME: STANDARD GENERAL LEDGER
  LOCATION: 8;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 51                        FIELD NAME: REPLACING (ENTRY NUMBER)
  LOCATION: 8;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 52                        FIELD NAME: REPLACEMENT UPDATE CODE
  LOCATION: 8;9                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,9)
FIELD NUMBER: 29                        FIELD NAME: SECOND PREVIOUS LOCATION
  LOCATION: 9;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 29.1                      FIELD NAME: THIRD PREVIOUS LOCATION
  LOCATION: 9;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 29.2                      FIELD NAME: FOURTH PREVIOUS LOCATION
  LOCATION: 9;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 29.3                      FIELD NAME: FIFTH PREVIOUS LOCATION
  LOCATION: 9;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 60                        FIELD NAME: STATION NUMBER
  LOCATION: 9;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 61                        FIELD NAME: BUDGET OBJECT CODE
  LOCATION: 9;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 62                        FIELD NAME: FUND
  LOCATION: 9;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 63                        FIELD NAME: ADMINISTRATION/OFFICE
  LOCATION: 9;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 64                        FIELD NAME: EQUITY ACCOUNT
  LOCATION: 9;9                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 65                        FIELD NAME: DATE OF FAP CONVERSION
  LOCATION: 9;10                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 81
  FIELD NAME: Y2K FUNCTIONAL CLASSIFICATION
  LOCATION: 9;11                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 82                        FIELD NAME: Y2K UTILITY SYSTEM
  LOCATION: 9;12                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,10,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SPEX
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,11)
FIELD NUMBER: 71                        FIELD NAME: Y2K CATEGORY
  LOCATION: 11;1                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 72
  FIELD NAME: ESTIMATED Y2K COMPLIANCE DATE
  LOCATION: 11;2                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 73
  FIELD NAME: ESTIMATED Y2K COMPLIANCE COST
  LOCATION: 11;3                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 74                        FIELD NAME: ACTUAL Y2K COMPLIANCE COST 
  LOCATION: 11;4                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 75                        FIELD NAME: Y2K TECHNICIAN
  LOCATION: 11;5                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 76                        FIELD NAME: Y2K ACTION
  LOCATION: 11;6                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 77                        FIELD NAME: Y2K ASSIGNED SHOP
  LOCATION: 11;7                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 78
  FIELD NAME: Y2K COMPLIANCE WORK ORDER (POINTER)
  LOCATION: 11;8                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 79
  FIELD NAME: Y2K COMPLIANCE WORK ORDER (TEXT)
  LOCATION: 11;9                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 72.1                      FIELD NAME: ACTUAL Y2K COMPLIANCE DATE
  LOCATION: 11;10                       ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 71.5                      FIELD NAME: SOURCE OF Y2K CATEGORY
  LOCATION: 11;11                       ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 80                        FIELD NAME: Y2K NOTES
  LOCATION: 11;12                       ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 76.1
  FIELD NAME: Y2K ESTIMATED REPLACEMENT DATE
  LOCATION: 11;13                       ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,12,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ORIGINAL BAR CODE ID
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,'ITC',D1,0)
FIELD NUMBER: .01                       FIELD NAME: IT COMMENTS
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,'ITR')
FIELD NUMBER: 91                        FIELD NAME: IT REMOTE LOCATION
  LOCATION: 91;1                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,'NSP')
FIELD NUMBER: 90                        FIELD NAME: NON-SPACE FILE LOCATION
  LOCATION: 'NSP';1                     ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 90.1                      FIELD NAME: NON-SPACE FILE PERSON
  LOCATION: 'NSP';2                     ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 90.2                      FIELD NAME: NON-SPACE FILE DATE/TIME
  LOCATION: 'NSP';3                     ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,D0,'RC')
FIELD NUMBER: 99                        FIELD NAME: REMAIN CAPITALIZED SET BY
  LOCATION: 'RC';1                      ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6914,'B'
 GLOBAL DESCRIPTION:   'B' cross reference - used to look up by ENTRY NUMBER
 (#.01) 
GLOBAL REFERENCE: ENG(6914,'C'
 GLOBAL DESCRIPTION:   'C' cross reference - used to look up by VA PM NUMBER
 (#25) 
GLOBAL REFERENCE: ENG(6914,'D'
 GLOBAL DESCRIPTION:   'D' cross reference - used to look up by LOCATION (#24) 
GLOBAL REFERENCE: ENG(6914,'E'
 GLOBAL DESCRIPTION:   'E' cross reference - used to look up by MODEL (#4) 
GLOBAL REFERENCE: ENG(6914,'F'
 GLOBAL DESCRIPTION:   'F' cross reference - used to look up by SERIAL # (#5) 
GLOBAL REFERENCE: ENG(6914,'G'
 GLOBAL DESCRIPTION:   'G' cross reference - used to look up by EQUIPMENT
 CATEGORY (#6) 
GLOBAL REFERENCE: ENG(6914,'H'
 GLOBAL DESCRIPTION:   'H' cross reference - used to look up by MFGR. EQUIPMENT
 NAME (#3) 
GLOBAL REFERENCE: ENG(6914,'I'
 GLOBAL DESCRIPTION:   'I' cross reference - used to look up by NXRN# (#17) 
GLOBAL REFERENCE: ENG(6914,'J'
 GLOBAL DESCRIPTION:   'J' cross reference - used to look up by CATEGORY STOCK
 NUMBER (#18) 
GLOBAL REFERENCE: ENG(6914,'K'
 GLOBAL DESCRIPTION:   'K' cross reference - used to look up by MANUFACTURER
 (#1) 
GLOBAL REFERENCE: ENG(6914,'L'
 GLOBAL DESCRIPTION:   'L' cross reference - used to look up by LOCAL
 IDENTIFIER (#26) 
GLOBAL REFERENCE: ENG(6914,'M'
 GLOBAL DESCRIPTION:   'M' cross reference - used to look up by PURCHASE ORDER
 # (#11) 
GLOBAL REFERENCE: ENG(6914,'AR',TAXID,D0
 GLOBAL DESCRIPTION:   'AR' cross reference - used to look up by TYPE OF ENTRY
 (#7) 
GLOBAL REFERENCE: ENG(6914,'AD'
 GLOBAL DESCRIPTION:   'AD' cross reference for field CMR (#19) 
GLOBAL REFERENCE: ENG(6914,'AB',D1,RSHOP,D0)
 GLOBAL DESCRIPTION:   'AB' cross reference by field RESPONSIBLE SHOP (#.01) 
GLOBAL REFERENCE: ENG(6914,D0,4,'B',RSHOP,D1)
 GLOBAL DESCRIPTION:   'B' cross reference used to lookup within Responsible
 Shop multiple.  
GLOBAL REFERENCE: ENG(6914,'OEE',OBARCODE,D1,D0)
 GLOBAL DESCRIPTION:   'OEE' cross reference to lookup by ORIGINAL BAR CODE
 multiple field (#.01) 
 GENERAL DESCRIPTION:   Above PAR requests permission to write to the
 ENGINEERING FILE #6914 to record additions and edits of Equipment Inventory
 data.  Above PAR also reads data from this file to display Equipment Inventory
 data in both the Equipment and Work Order functions.  
  
 Above PAR Ad-Hoc Reporting includes the ENGINEERING FILE #6914.  Ad-Hoc
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 12, 2022

NUMBER: 6494                            IA #: 6494
  FILE NUMBER: 6920                     GLOBAL ROOT: ENG(6920
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: WORK ORDER # FILE ACCESS
  ID: ENG(6920
GLOBAL REFERENCE: ENG(6920,D0,0)
FIELD NUMBER: .01                       FIELD NAME: WORK ORDER #
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: .05                       FIELD NAME: ORIGINAL WORK ORDER #
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: REQUEST DATE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2                         FIELD NAME: REQUEST MODE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 3                         FIELD NAME: LOCATION
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 4                         FIELD NAME: BED #
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6920,D0,1)
FIELD NUMBER: 7.5                       FIELD NAME: ENTERED BY
  LOCATION: 1:1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 6                         FIELD NAME: TASK DESCRIPTION (60 char)
  LOCATION: 1;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 7                         FIELD NAME: CONTACT PERSON
  LOCATION: 1;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 8                         FIELD NAME: PHONE
  LOCATION: 1;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6920,D0,2)
FIELD NUMBER: 9                         FIELD NAME: SHOP
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 16                        FIELD NAME: PRIMARY TECH ASSIGNED
  LOCATION: 2;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 17                        FIELD NAME: PRIORITY
  LOCATION: 2;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6920,D0,3)
FIELD NUMBER: 20                        FIELD NAME: PMI NUMBER
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 21                        FIELD NAME: EQUIPMENT CATEGORY
  LOCATION: 3;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 23                        FIELD NAME: OWNER/DEPARTMENT
  LOCATION: 3;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 19                        FIELD NAME: LOCAL IDENTIFIER
  LOCATION: 3;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 22.3                      FIELD NAME: MODEL
  LOCATION: 3;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 22.5                      FIELD NAME: SERIAL NO.
  LOCATION: 3;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 18                        FIELD NAME: EQUIPMENT ID#
  LOCATION: 3;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 21.9                      FIELD NAME: MANUFACTURER
  LOCATION: 3;9                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6920,D0,4)
FIELD NUMBER: 10                        FIELD NAME: DATE ASSIGNED
  LOCATION: 4;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 31                        FIELD NAME: PARTS ORDERED ON ACC.#
  LOCATION: 4;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 32                        FIELD NAME: STATUS
  LOCATION: 4;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 47                        FIELD NAME: VENDOR SERVICE COST
  LOCATION: 4;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 32.1                      FIELD NAME: NOTIFICATION PREFERENCE
  LOCATION: 4;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 32.2                      FIELD NAME: NOTIFICATION MESSAGE
  LOCATION: 4;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6920,D0,5)
FIELD NUMBER: 36                        FIELD NAME: DATE COMPLETE (or closed)
  LOCATION: 5;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 37                        FIELD NAME: TOTAL HOURS
  LOCATION: 5;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 38                        FIELD NAME: TOTAL MATERIAL COST
  LOCATION: 5;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 35.5                      FIELD NAME: WORK CENTER CODE
  LOCATION: 5;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 37.5                      FIELD NAME: TOTAL LABOR COST
  LOCATION: 5;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 39                        FIELD NAME: WORK PERFORMED
  LOCATION: 5;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 35.2                      FIELD NAME: PM STATUS
  LOCATION: 5;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6920,D0,6,D1,0)
FIELD NUMBER: .01                       FIELD NAME: COMMENTS
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6920,D0,7,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ASSIGNED TECH
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: HOURS
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2                         FIELD NAME: SHOP
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6920,D0,8,D1,0)
FIELD NUMBER: .01                       FIELD NAME: WORK ACTION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: ENG(6920,'B')
 GLOBAL DESCRIPTION:   File 6920 "B" Cross reference used to look up by WORK
 ORDER # 
GLOBAL REFERENCE: ENG(6920,'C')
 GLOBAL DESCRIPTION:   File 6920 "C" Cross reference used to look up by
 LOCATION 
GLOBAL REFERENCE: ENG(6920,'D')
 GLOBAL DESCRIPTION:   File 6920 "D" Cross reference used to look up by TASK
 DESCRIPTION 
GLOBAL REFERENCE: ENG(6920,'G')
 GLOBAL DESCRIPTION:   File 6920 "G" Cross reference used to look up by
 EQUIPMENT ID# 
GLOBAL REFERENCE: ENG(6920,'H')
 GLOBAL DESCRIPTION:   File 6920 "H" Cross reference used to look up by
 ORIGINAL WORK ORDER # 
GLOBAL REFERENCE: ENG(6920,'AINC')
 GLOBAL DESCRIPTION:   File 6920 "AINC" Cross reference used to look up open
 work orders 
 GENERAL DESCRIPTION:   Above PAR requests permission to write to the WORK
 ORDER FILE #6920 to record additions, deletions and edits of Work Order data. 
 Above PAR also reads data from this file to display Work Order data in both
 the Equipment and Work Order functions.  The Advanced Prosthetics Acquisition
 Tool (APAT) reads from the Work Order (#6920) file when a detailed purchase 
 card order is being created.  
  
 Above PAR Ad-Hoc Reporting includes the WORK ORDER FILE #6920. Ad-Hoc 
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: SEP 12, 2019

NUMBER: 6495                            IA #: 6495
  FILE NUMBER: 413.1                    GLOBAL ROOT: PRCN(413.1,
  DATE CREATED: OCT 17, 2016
  CUSTODIAL PACKAGE: EQUIPMENT/TURN-IN REQUEST
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TURN-IN REQUEST FILE ACCESS
  ID: PRCN(413.1,
GLOBAL REFERENCE: PRCN(413.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: TRANSACTION CODE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: REQUESTOR
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2                         FIELD NAME: REQUESTING SERVICE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 3                         FIELD NAME: REQUEST DATE/TIME
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 4                         FIELD NAME: STATION NUMBER
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 5                         FIELD NAME: CMR RESPONSIBLE OFFICIAL
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 6                         FIELD NAME: REQUEST STATUS
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 7                         FIELD NAME: STATUS DATE
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 8                         FIELD NAME: EQUIP REQUEST
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 12                        FIELD NAME: UTILITY DISCONNECT?
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 13                        FIELD NAME: ENGINEER. WORK ORDER
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 15                        FIELD NAME: CMR
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 9                         FIELD NAME: CMR OFFICIAL APPROVAL
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: PRCN(413.1,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: REPLACEMENT ITEM NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: DISPOSAL CONDITION CODE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2                         FIELD NAME: EQUIP REQUEST LINE ITEM
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 4                         FIELD NAME: UTILITY DISCONNECT?
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 5                         FIELD NAME: VOUCHER #
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 12                        FIELD NAME: WORK ORDER NEEDED
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: .5                        FIELD NAME: JUSTIFICATION
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: .7                        FIELD NAME: OTHER JUSTIFICATION
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 3                         FIELD NAME: DESCRIPTION
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 11                        FIELD NAME: WORK ORDER #
  LOCATION: 0;14                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: PRCN(413.1,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CMR OFFICIAL EXPLANATION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: PRCN(413.1,D0,3)
FIELD NUMBER: 1.5                       FIELD NAME: REQUESTOR PHONE #
  LOCATION: 3;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 16                        FIELD NAME: WAREHOUSE OFFICIAL
  LOCATION: 3;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PRCN(413.1,'B'
 GLOBAL DESCRIPTION:   'B' cross reference - used to look up by TRANSACTION
 CODE 
GLOBAL REFERENCE: PRCN(413.1,'AB'
 GLOBAL DESCRIPTION:   'AB' cross reference - used to look up by EE# 
GLOBAL REFERENCE: PRCN(413.1,'AC'
 GLOBAL DESCRIPTION:   'AC' cross reference - used to look up by REQUEST STATUS 
GLOBAL REFERENCE: PRCN(413.1,'AD'
 GLOBAL DESCRIPTION:   'AD' cross reference - used to look up by CMR RESP
 OFFICIAL 
GLOBAL REFERENCE: PRCN(413.1,D0,1,'B'
 GLOBAL DESCRIPTION:   'B' cross reference contains the Turn-In Item's
 REPLACEMENT ITEM NUMBER (#01) and used to lookup by REPLACEMENT ITEM NUMBER.  
 GENERAL DESCRIPTION:   Above PAR requests permission to write to the TURN-IN
 REQUEST FILE #413.1 to record additions, edits and deletions of Turn-In 
 Requests.  Above PAR also reads data from this file to display Turn-In 
 information within the Equipment function.  
  
 Above PAR Ad-Hoc Reporting includes the TURN-IN REQUEST FILE #413.1.  Ad-Hoc
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUL 31, 2020

NUMBER: 6496                            IA #: 6496
  FILE NUMBER: 660                      GLOBAL ROOT: RMPR(660
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: RECORD OF PROSTHETIC APPLIANCE/REPAIR FILE ACCESS
  ID: RMPR(660
GLOBAL REFERENCE: RMPR(660,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ENTRY DATE
  LOCATION: 0;1
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PATIENT NAME
  LOCATION: 0;2
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: REQUEST DATE
  LOCATION: 0;3
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TYPE OF TRANSACTION
  LOCATION: 0;4
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 13                        FIELD NAME: ACTION
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: ITEM
  LOCATION: 0;6
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: QTY
  LOCATION: 0;7
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 78                        FIELD NAME: UNIT OF ISSUE
  LOCATION: 0;8
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 7                         FIELD NAME: VENDOR
  LOCATION: 0;9
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 8                         FIELD NAME: STATION
  LOCATION: 0;10
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: SERIAL NBR
  LOCATION: 0;11
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: DELIVERY DATE
  LOCATION: 0;12
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 11                        FIELD NAME: FORM REQUESTED ON
  LOCATION: 0;13
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 12                        FIELD NAME: SOURCE
  LOCATION: 0;14
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 15                        FIELD NAME: HISTORICAL DATA
  LOCATION: 0;15
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: TOTAL COST
  LOCATION: 0;16
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: SHIP/DEL
  LOCATION: 0;17
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 16                        FIELD NAME: REMARKS
  LOCATION: 0;18
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 17                        FIELD NAME: RETURNED STATUS
  LOCATION: 0;19                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.5                      FIELD NAME: RETURN STATUS DATE
  LOCATION: 0;20                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 18                        FIELD NAME: STATUS FLAG
  LOCATION: 0;21                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.1                       FIELD NAME: HCPCS
  LOCATION: 0;22                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21                        FIELD NAME: LOT NUMBER
  LOCATION: 0;24                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 22                        FIELD NAME: PRODUCT LINE
  LOCATION: 0;25                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6.5                       FIELD NAME: PICKUP/DEL
  LOCATION: 0;26
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 27                        FIELD NAME: INITIATOR
  LOCATION: 0;27                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,1)
FIELD NUMBER: 23                        FIELD NAME: TRANSACTION
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 24                        FIELD NAME: DESCRIPTION
  LOCATION: 1;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 29                        FIELD NAME: INVENTORY POINT
  LOCATION: 1;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.5                       FIELD NAME: PSAS HCPCS
  LOCATION: 1;4
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 4.6                       FIELD NAME: STOCK ISSUE
  LOCATION: 1;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.7                       FIELD NAME: CPT MODIFIER
  LOCATION: 1;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.8                       FIELD NAME: DATE CPT MODIFIER EXTRACTED
  LOCATION: 1;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 39                        FIELD NAME: DATE OF SERVICE
  LOCATION: 1;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 35                        FIELD NAME: USER WHO EDIT
  LOCATION: 1;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 36                        FIELD NAME: DATE EDITED
  LOCATION: 1;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.9                       FIELD NAME: HCPCS-ICD9 CODING FLAG
  LOCATION: 1;11                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 4.91                      FIELD NAME: CODING FLAG DATE
  LOCATION: 1;12
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 4.92                      FIELD NAME: HI TECH ITEM
  LOCATION: 1;13
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,2)
FIELD NUMBER: 37                        FIELD NAME: HCPCS/ITEM
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 38                        FIELD NAME: HCPCS/ITEM DESCRIPTION
  LOCATION: 2;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 38.1                      FIELD NAME: EXCLUDE/WAIVER
  LOCATION: 2;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 38.7                      FIELD NAME: CONTRACT #
  LOCATION: 2;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 38.8                      FIELD NAME: NUMBER OF BIDS
  LOCATION: 2;10                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,3)
FIELD NUMBER: 25                        FIELD NAME: DELIVER TO
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 26                        FIELD NAME: DATE REQUIRED
  LOCATION: 3;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 19                        FIELD NAME: PATIENT NOTIFICATION FLAG
  LOCATION: 3;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,4)
FIELD NUMBER: 4.2                       FIELD NAME: VENDOR TRACKING NUMBER
  LOCATION: 4;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.3                       FIELD NAME: BANK AUTHORIZATION NUMBER
  LOCATION: 4;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.61                      FIELD NAME: CONSULT REQUEST SERVICE
  LOCATION: 4;3                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,5)
FIELD NUMBER: 34                        FIELD NAME: OIF/OEF
  LOCATION: 5;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,6)
FIELD NUMBER: 20                        FIELD NAME: DELIVERY VERIFICATION DATE
  LOCATION: 6;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 20.1                      FIELD NAME: DELIVERY VERIFICATION STATUS
  LOCATION: 6;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,9)
FIELD NUMBER: 9.1                       FIELD NAME: PRODUCT DESCRIPTION
  LOCATION: 9;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9.2                       FIELD NAME: PRODUCT MODEL
  LOCATION: 9;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,10)
FIELD NUMBER: 8.1                       FIELD NAME: SUSPENSE DATE
  LOCATION: 10;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.2                       FIELD NAME: DATE RX WRITTEN
  LOCATION: 10;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.3                       FIELD NAME: INITIAL ACTION DATE
  LOCATION: 10;3                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.4                       FIELD NAME: COMPLETION DATE
  LOCATION: 10;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.5                       FIELD NAME: TYPE OF REQUEST
  LOCATION: 10;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.6                       FIELD NAME: SUSPENSE REQUESTOR
  LOCATION: 10;6                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.7                       FIELD NAME: PROVISIONAL DIAGNOSIS
  LOCATION: 10;7                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.8                       FIELD NAME: SUSPENSE ICD
  LOCATION: 10;8
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 8.9                       FIELD NAME: CONSULT
  LOCATION: 10;9                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.11                      FIELD NAME: SUSPENSE STATION
  LOCATION: 10;11                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.12                      FIELD NAME: PCE
  LOCATION: 10;12                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.13                      FIELD NAME: DATE SENT TO PCE
  LOCATION: 10;13                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.14                      FIELD NAME: SUSPENSE STATUS
  LOCATION: 10;14                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,'AM')
FIELD NUMBER: 60                        FIELD NAME: AMIS DATE
  LOCATION: AM;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 81                        FIELD NAME: NO ADMIN COUNT
  LOCATION: AM;2
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 62                        FIELD NAME: PATIENT CATEGORY
  LOCATION: AM;3
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 63                        FIELD NAME: SPECIAL CATEGORY
  LOCATION: AM;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 64                        FIELD NAME: ADMIN REPAIR AMIS CODE
  LOCATION: AM;5                        ACCESS: Read w/Fileman
FIELD NUMBER: 79                        FIELD NAME: AMIS FLAG
  LOCATION: AM;6                        ACCESS: Read w/Fileman
FIELD NUMBER: 52                        FIELD NAME: AMIS NEW CODE
  LOCATION: AM;9                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,'AMS')
FIELD NUMBER: 68                        FIELD NAME: AMIS GROUPER
  LOCATION: AMS;1
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,'BA1')
FIELD NUMBER: 30                        FIELD NAME: PRIMARY ICD DIAGNOSIS CODE
  LOCATION: BA1;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 30.1
  FIELD NAME: PRIMARY AGENT ORANGE EXPOSURE
  LOCATION: BA1;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 30.2                      FIELD NAME: PRIMARY IONIZED RADIATION
  LOCATION: BA1;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 30.3                      FIELD NAME: PRIMARY SERVICE-CONNECTED
  LOCATION: BA1;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 30.4                      FIELD NAME: PRIMARY ENVIRONMENTAL CONT.
  LOCATION: BA1;5                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 30.5                      FIELD NAME: PRIMARY MST
  LOCATION: BA1;6                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 30.6                      FIELD NAME: PRIMARY HEAD/NECK CANCER
  LOCATION: BA1;7                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 30.7                      FIELD NAME: PRIMARY COMBAT VET
  LOCATION: BA1;8                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,'BA2')
FIELD NUMBER: 31
  FIELD NAME: SECONDARY ICD DIAGNOSIS CODE 1
  LOCATION: BA2;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 31.1                      FIELD NAME: SECONDARY AGENT ORANGE 1
  LOCATION: BA2;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 31.2
  FIELD NAME: SECONDARY IONIZED RADIATION 1
  LOCATION: BA2;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 31.3
  FIELD NAME: SECONDARY SERVICE-CONNECTED 1
  LOCATION: BA2;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 31.4
  FIELD NAME: SECONDARY ENVIRONMENTAL CONT 1
  LOCATION: BA2;5                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 31.5                      FIELD NAME: SECONDARY MST 1
  LOCATION: BA2;6                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 31.6                      FIELD NAME: SECONDARY HEAD/NECK CANCER 1
  LOCATION: BA2;7                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 31.7                      FIELD NAME: SECONDARY COMBAT VET 1
  LOCATION: BA2;8                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,'BA3')
FIELD NUMBER: 32                        FIELD NAME: SECONDARY ICD DIAGNOSIS 2
  LOCATION: BA3;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 32.1                      FIELD NAME: SECONDARY AGENT ORANGE 2
  LOCATION: BA3;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 32.2
  FIELD NAME: SECONDARY IONIZED RADIATION 2
  LOCATION: BA3;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 32.3
  FIELD NAME: SECONDARY SERVICE-CONNECTED 2
  LOCATION: BA3;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 32.4                      FIELD NAME: SECONDARY ENVIR. CONT. 2
  LOCATION: BA3;5                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 32.5                      FIELD NAME: SECONDARY MST 2
  LOCATION: BA3;6                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 32.6                      FIELD NAME: SECONDARY HEAD/NECK CANCER 2
  LOCATION: BA3;7                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 32.7                      FIELD NAME: SECONDARY COMBAT VET 2
  LOCATION: BA3;8                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,'BA4')
FIELD NUMBER: 33                        FIELD NAME: SECONDARY ICD DIAGNOSIS 3
  LOCATION: BA4;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 33.1                      FIELD NAME: SECONDARY AGENT ORANGE 3
  LOCATION: BA4;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 33.2
  FIELD NAME: SECONDARY IONIZED RADIATION 3
  LOCATION: BA4;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 33.3
  FIELD NAME: SECONDARY SERVICE-CONNECTED 3
  LOCATION: BA4;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 33.4                      FIELD NAME: SECONDARY ENVIRON. CONT. 3
  LOCATION: BA4;5                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 33.5                      FIELD NAME: SECONDARY MST 3
  LOCATION: BA4;6                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 33.6                      FIELD NAME: SECONDARY HEAD/NECK CANCER 3
  LOCATION: BA4;7                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 33.7                      FIELD NAME: SECONDARY COMBAT VET 3
  LOCATION: BA4;8                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,'DES',0)
FIELD NUMBER: 28                        FIELD NAME: EXTENDED DESCRIPTION
  LOCATION: 660.028;1                   ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,'HST')
FIELD NUMBER: 89                        FIELD NAME: HISTORICAL ITEM
  LOCATION: HST;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 90                        FIELD NAME: HISTORICAL STATION
  LOCATION: HST;2                       ACCESS: Read w/Fileman
FIELD NUMBER: 91                        FIELD NAME: HISTORICAL VENDOR
  LOCATION: HST;3                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 97                        FIELD NAME: HISTORICAL RECORD
  LOCATION: HST;4                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(D0,'HSTV')
FIELD NUMBER: 92                        FIELD NAME: HISTORICAL VENDOR PHONE
  LOCATION: HSTV;1                      ACCESS: Read w/Fileman
FIELD NUMBER: 93                        FIELD NAME: HISTORICAL STREET
  LOCATION: HSTV;2                      ACCESS: Read w/Fileman
FIELD NUMBER: 94                        FIELD NAME: HISTORICAL CITY
  LOCATION: HSTV;3                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,'HSTV1')
FIELD NUMBER: 95                        FIELD NAME: HISTORICAL STATE
  LOCATION: HSTV1;1                     ACCESS: Read w/Fileman
FIELD NUMBER: 96                        FIELD NAME: HISTORICAL ZIP
  LOCATION: HSTV1;2                     ACCESS: Read w/Fileman
FIELD NUMBER: 89.1                      FIELD NAME: DALC REFERENCE NUMBER
  LOCATION: HSTV1;3                     ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 89.2                      FIELD NAME: DALC BILL DATE
  LOCATION: HSTV1;4                     ACCESS: Read w/Fileman
FIELD NUMBER: 89.3                      FIELD NAME: DALC ORDERING STATION
  LOCATION: HSTV1;5                     ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,'LB')
FIELD NUMBER: 40                        FIELD NAME: REQUESTING STATION
  LOCATION: LB;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 72.5                      FIELD NAME: FREE TEXT WO #
  LOCATION: LB;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 69                        FIELD NAME: SOURCE OF PROCUREMENT
  LOCATION: LB;3
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 70                        FIELD NAME: RECEIVING STATION
  LOCATION: LB;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 71                        FIELD NAME: WORK ORDER NUMBER
  LOCATION: LB;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 45                        FIELD NAME: TOTAL LABOR HOURS
  LOCATION: LB;6                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 46                        FIELD NAME: TOTAL LABOR COST
  LOCATION: LB;7                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 47                        FIELD NAME: TOTAL MATERIAL COST
  LOCATION: LB;8                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 48                        FIELD NAME: TOTAL LAB COST
  LOCATION: LB;9
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 72                        FIELD NAME: 2529-3
  LOCATION: LB;10                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 50                        FIELD NAME: COMPLETION DATE
  LOCATION: LB;11                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 51                        FIELD NAME: LAB REMARKS
  LOCATION: LB;12                       ACCESS: Read w/Fileman
FIELD NUMBER: 80                        FIELD NAME: WORK FOR OTHER STATION
  LOCATION: LB;13                       ACCESS: Read w/Fileman
FIELD NUMBER: 82                        FIELD NAME: NO LAB COUNT
  LOCATION: LB;14                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(660,D0,'LBA')
FIELD NUMBER: 73                        FIELD NAME: LAB AMIS DATE
  LOCATION: LBA;1                       ACCESS: Read w/Fileman
FIELD NUMBER: 74                        FIELD NAME: ORTHOTICS LAB CODE
  LOCATION: LBA;2                       ACCESS: Read w/Fileman
FIELD NUMBER: 75                        FIELD NAME: ORTHOTICS LAB REPAIR CODE
  LOCATION: LBA;3                       ACCESS: Read w/Fileman
FIELD NUMBER: 76                        FIELD NAME: RESTORATION LAB CODE
  LOCATION: LBA;4                       ACCESS: Read w/Fileman
FIELD NUMBER: 77                        FIELD NAME: RESTORATIONS LAB REPAIR CODE
  LOCATION: LBA;5                       ACCESS: Read w/Fileman
FIELD NUMBER: 83                        FIELD NAME: BACKLOG DATE
  LOCATION: LBA;6                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(D0,'PFSS')
FIELD NUMBER: 100                       FIELD NAME: PFSS ACCOUNT REFERENCE
  LOCATION: PFSS;1                      ACCESS: Read w/Fileman
FIELD NUMBER: 101                       FIELD NAME: PFSS CHARGE ID
  LOCATION: PFSS;2                      ACCESS: Read w/Fileman
FIELD NUMBER: 102                       FIELD NAME: LATEST PSAS HCPCS
  LOCATION: PFSS;3                      ACCESS: Read w/Fileman
FIELD NUMBER: 103                       FIELD NAME: LATEST QTY
  LOCATION: PFSS;4                      ACCESS: Read w/Fileman
FIELD NUMBER: 104                       FIELD NAME: LATEST TOTAL COST
  LOCATION: PFSS;5                      ACCESS: Read w/Fileman
FIELD NUMBER: 105                       FIELD NAME: LATEST ORDERING PROVIDER
  LOCATION: PFSS;6                      ACCESS: Read w/Fileman
FIELD NUMBER: 106                       FIELD NAME: PFSS ACCOUNT FLAG
  LOCATION: PFSS;7                      ACCESS: Read w/Fileman
FIELD NUMBER: 107                       FIELD NAME: PFSS CHARGE FLAG
  LOCATION: PFSS;8                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(660,'AC'
 GLOBAL DESCRIPTION:   File 660 'AC' cross-reference  Used to look up by
 REQUEST DATE 
GLOBAL REFERENCE: RMPR(660,'AG'
 GLOBAL DESCRIPTION:   File 660 'AG' cross-reference  Used to look up by AMIS
 GROUPER 
GLOBAL REFERENCE: RMPR(660,'B'
 GLOBAL DESCRIPTION:   File 660 'B' cross reference  Used to look up by ENTRY
 DATE 
GLOBAL REFERENCE: RMPR(660,'C'
 GLOBAL DESCRIPTION:   File 660 'C' cross reference  Used to look up by PATIENT
 NAME 
GLOBAL REFERENCE: RMPR(660,'CT'
 GLOBAL DESCRIPTION:   File 660 'CT' cross reference  Used to look up by
 DELIVERY DATE 
 GENERAL DESCRIPTION:   
    The Advanced Prosthetics Acquisition Tool (APAT) reads from the RECORD 
    OF PROS APPLIANCE/REPAIR (#660) when displaying appliance transactions 
    on the 2319 tab and when extracting appliance data to SQL Server to 
    determine if duplicate appliances have been purchased for a patient.  
    When creating a Prosthetic 1358, a 2529-3, a GIP or PIP Stock Issue, 
    and when adding a cancellation note to a Prosthetic Suspense, APAT 
    writes to the RECORD OF PROS APPLIANCE/REPAIR (#660) in order to record 
    the purchase/issue on the patient's 2319. APAT also allows for the 
    editing of specific fields in the RECORD OF PROS APPLIANCE/REPAIR 
    (#660).  
  
    During reconciliation and close out, APAT stores the shipment date 
    (DATE OF SERVICE (#39)) of each 2319 entry associated with a purchase 
    card order.  
  
 Amendment - Effective 4/14/23, The Advanced Prosthetics Acquisition Tool 
 (APAT) requests changes in the types of access for the following fields in the
 RECORD OF PROS APPLIANCE/REPAIR (#660) file.  Direct global reads of fields
 are requested to prevent VistA timeouts when reports are produced or grids are
 filled.  
  
 Amendment (requested 1/23/24) - The Advanced Prosthetics Acquisition Tool 
 (APAT) requests changes in the types of access for the indicated fields in the
 RECORD OF PROS APPLIANCE/REPAIR (#660) file.  Direct global reads of the
 indicated fields are requested to prevent VistA timeouts when reports and
 lists are generated.  The requested direct global reads have existed in APAT
 since it was released in 2019.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/23/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires direct global read
 and read/write w/ Fileman access to RECORD OF PROS APPLIANCE/REPAIR (#660)
 file.  
  DATE ACTIVATED: FEB 01, 2024

NUMBER: 6497                            IA #: 6497
  FILE NUMBER: 6911                     GLOBAL ROOT: ENG(6911)
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: EQUIPMENT CATEGORY FILE ACCESS
  ID: ENG(6911)
GLOBAL REFERENCE: ENG(6911,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: LOCKOUT REQUIRED?
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: JACHO
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG(6911,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SYNONYM
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG(6911,D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: RESPONSIBLE SHOP
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TECHNICIAN
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2.6                       FIELD NAME: SKIP MONTHS
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 2.7                       FIELD NAME: CRITICALITY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: ENG(6911,D0,4,D1,1)
FIELD NUMBER: 2                         FIELD NAME: STARTING MONTH
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG(6911,D0,4,D1,2,D2,0)
FIELD NUMBER: .01                       FIELD NAME: FREQUENCY
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: HOURS (Estimated)
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: MATERIAL COST (Estimated)
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: LEVEL
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PROCEDURE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: STARTING YEAR (4 numerics)
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG(6911,'B'
 GLOBAL DESCRIPTION:   "B" cross reference - used to look up by NAME 
GLOBAL REFERENCE: ENG(6911,'C'
 GLOBAL DESCRIPTION:   "C" cross reference - used to look up by SYNONYM 
 GENERAL DESCRIPTION:   Above PAR requests permission to read the EQUIPMENT
 CATEGORY FILE #6911 to display EQUIPMENT CATEGORY information within the
 Equipment function.  
  
 Above PAR Ad-Hoc Reporting includes the EQUIPMENT CATEGORY FILE #6911.  Ad-Hoc
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 12, 2019

NUMBER: 6498                            IA #: 6498
  FILE NUMBER: 6914.1                   GLOBAL ROOT: ENG(6914.1)
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CMR FILE ACCESS
  ID: ENG(6914.1)
GLOBAL REFERENCE: ENG(6914.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: RESPONSIBLE OFFICIAL
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: LAST RECONCILED
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .5                        FIELD NAME: SERVICE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: STATION NUMBER
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .6                        FIELD NAME: BRIEF DESCRIPTION
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG(6914.1,D0,20)
FIELD NUMBER: 20
  FIELD NAME: ALTERNATE RESPONSIBLE OFFICIAL
  LOCATION: 20;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG(6914.1,'B'
 GLOBAL DESCRIPTION:   "B" cross reference - used to look up by NAME 
GLOBAL REFERENCE: ENG(6914.1,'C'
 GLOBAL DESCRIPTION:   "C" cross reference - used to look up by RESPONSIBLE
 OFFICIAL 
GLOBAL REFERENCE: ENG(6914.1,'D'
 GLOBAL DESCRIPTION:   "D" cross reference - used to look up by ALTERNATE
 RESPONSIBLE OFFICIAL 
GLOBAL REFERENCE: ENG(6914.1,'B1',NM
 GLOBAL DESCRIPTION:   Cross reference by Name field NAME (#.01).  This is
 different than 'B' index as the name is truncated at 29 characters and a space
 is added so that the index is ASCII collating sequence.  
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the CMR FILE
 #6914.1 to display CMR/EIL information within the Equipment and Work Order 
 functions.  
  
 Above PAR Ad-Hoc Reporting includes the CMR FILE #6914.1. Ad-Hoc functionality
 provides the ability to select fields from the file for display on
 user-defined reports.  Ad-Hoc offers only FileMan read access and only if the
 user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 06, 2022

NUMBER: 6499                            IA #: 6499
  FILE NUMBER: 6914.2                   GLOBAL ROOT: ENG(6914.2)
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PM PROCEDURES ACCESS
  ID: ENG(6914.2)
GLOBAL REFERENCE: ENG(6914.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PM REFERENCE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG(6914.2,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: TEXT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the PM
 PROCEDURES FILE #6914.2 to display PM Procedure Information within the
 Equipment function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 12, 2019

NUMBER: 6500                            IA #: 6500
  FILE NUMBER: 660.1                    GLOBAL ROOT: RMPR(660.1,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PROS RETURNED/CONDEMNED FILE ACCESS
  ID: RMPR(660.1,
GLOBAL REFERENCE: RMPR(660.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   
                                       Global r 
FIELD NUMBER: 1                         FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ITEM
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: QUANTITY
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: COST
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: SERIAL NUMBER
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: DATE OF RETURN
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11                        FIELD NAME: INVENTORY POINT
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13                        FIELD NAME: RETURNED STATUS
  LOCATION: 0;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: STATION
  LOCATION: 0;15                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11.5                      FIELD NAME: APPLIANCE REPAIR
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20                        FIELD NAME: OBLIGATION NUMBER
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 23                        FIELD NAME: AUTO-ADAPTIVE ITEM
  LOCATION: 0;21                        ACCESS: Read w/Fileman
FIELD NUMBER: 24                        FIELD NAME: AUTO-ADAPTIVE TRANSACTION
  LOCATION: 0;22                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(660.1,D0,1,0)
FIELD NUMBER: 2.5                       FIELD NAME: COMMENTS
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(660.1,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: COMMENTS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(660.1,'AC'
 GLOBAL DESCRIPTION:   File 660.1 'AC' cross reference  Used to look up by
 APPLIANCE 
                                  REPAIR 
GLOBAL REFERENCE: RMPR(660.1,'C'
 GLOBAL DESCRIPTION:   File 660.1 'C' cross reference  Used to display/print 
                                 loan card information 
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT) reads
 the PROS RETURNED CONDEMNED File (#660.1) when displaying 2319 appliance 
 transactions including HISA and Home Oxygen.  
  
 APAT also writes to the PROS RETURNED CONDEMNED file (#660.1) when an
 appliance transaction in the RECORD OF PROS APPLIANCE/ REPAIR file (#660) is
 returned or condemned.  A PROS RETURNED CONDEMNED item may be edited or
 deleted as well.  
  
 As is done in Prosthetics, APAT accesses fields undefined in the file using
 direct reads: 
    File 660.1 node 0 ^-piece 9 
    File 660.1 node 0 ^-piece 10 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JAN 20, 2017

NUMBER: 6501                            IA #: 6501
  FILE NUMBER: 6914.3                   GLOBAL ROOT: ENG(6914.3)
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: NX SGL ACCESS
  ID: ENG(6914.3)
GLOBAL REFERENCE: ENG(6914.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ACCOUNT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the NX SGL
 File #6914.3 to display Standard General Ledger information within the
 Equipment function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 12, 2019

NUMBER: 6502                            IA #: 6502
  FILE NUMBER: 6914.4                   GLOBAL ROOT: ENG(6914.4)
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: NX BOC FILE ACCESS
  ID: ENG(6914.4)
GLOBAL REFERENCE: ENG(6914.4,D0,0)
FIELD NUMBER: .01
  FIELD NAME: CAPITALIZED BUDGET OBJECT CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: CORRESPONDING SGL
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the NX BOC
 FILE #6914.4 to display BOC information within the Equipment function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 12, 2019

NUMBER: 6503                            IA #: 6503
  FILE NUMBER: 6914.6                   GLOBAL ROOT: ENG(6914.6)
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: NX FUND ACCESS
  ID: ENG(6914.6)
GLOBAL REFERENCE: ENG(6914.6,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NX FUND CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the NX FUND
 File #6914.6 to display FUND information within the Equipment function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 12, 2019

NUMBER: 6504                            IA #: 6504
  FILE NUMBER: 661                      GLOBAL ROOT: RMPR(661,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROS ITEM MASTER FILE ACCESS
  ID: RMPR(661,
GLOBAL REFERENCE: RMPR(661,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: AMIS ADMIN NEW CODE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: AMIS ADMIN REPAIR CODE
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: AMIS ORTHOTIC NEW CODE
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: AMIS ORTHOTICS REPAIR CODE
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: AMIS RESTORATION NEW CODE
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6
  FIELD NAME: AMIS RESTORATIONS REPAIR CODE
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(661,'B'
 GLOBAL DESCRIPTION:   'B' cross reference - used to look up by NAME 
 GENERAL DESCRIPTION:   The PROS ITEM MASTER (#661) File is read when creating
 a GIP Stock Issue, a Prosthetic purchase card order, an OWL (Orthotic and Lab
 Work Order), and when displaying 2319 appliance transactions.  Also, new
 Prosthetic Item Master items may be added or revised in inventory processing
 in Above PAR.  This file is accessed as well when various reports are produced
 and grids are filled.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Effective 4/13/23, with patch DSSO*2.0*3, "Global r"
 was added as a type of access for the NAME (#.01) field to prevent VistA time
 outs when producing reports and filling grids.  
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   PROSTHETICS VISION 4 SIGHT II Added 04/22/25, effective
 with PROSTHETICS VISION 4 SIGHT II patch RMPV*1*1, the Prosthetics package
 requires information for the Prosthetic Master File Access to support eyeglass
 ordering.  
  DATE ACTIVATED: APR 14, 2023

NUMBER: 6505                            IA #: 6505
  FILE NUMBER: 6914.7                   GLOBAL ROOT: ENG(6914.7)
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: NX A/O ACCESS
  ID: ENG(6914.7)
GLOBAL REFERENCE: ENG(6914.7,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ADMIN/OFFICE CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the NX A/O
 File #6914.7 to display Accounting Office information within the Equipment
 function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 12, 2019

NUMBER: 6506                            IA #: 6506
  FILE NUMBER: 661.1                    GLOBAL ROOT: RMPR(661.1,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROSTHETIC HCPCS FILE ACCESS
  ID: RMPR(661.1,
GLOBAL REFERENCE: RMPR(661.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: HCPCS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: SHORT NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: NEW HCPC CODE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: CPT
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: STATUS
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: NPPD REPAIR CODE
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: NPPD NEW CODE
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: CALCULATION FLAG
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: INVENTORY FLAG
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: PRE-DETERMINED LAB TIME
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 1.1                       FIELD NAME: DATE/TIME LAST UPDATE
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 1.2                       FIELD NAME: LAST UPDATE
  LOCATION: 0;12                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(661.1,D0,1,D1,0)
FIELD NUMBER: 4                         FIELD NAME: SYNONYM
  LOCATION: 661.14;1                    ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(661.1,D0,2,D1,0)
FIELD NUMBER: 8                         FIELD NAME: DESCRIPTION
  LOCATION: 661.18;1                    ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(661.1,D0,3,D1,0)
FIELD NUMBER: 20                        FIELD NAME: ITEM
  LOCATION: 661.12;1                    ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(661.1,D0,4)
FIELD NUMBER: .03                       FIELD NAME: CPT MODIFIER
  LOCATION: 4;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: NON-BILLABLE FLAG
  LOCATION: 4;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(661.1,D0,5)
FIELD NUMBER: 30                        FIELD NAME: RENTAL FLAG
  LOCATION: 5;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.3                       FIELD NAME: VERSION DATE
  LOCATION: 5;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(661.1,'B'
 GLOBAL DESCRIPTION:   File 661.1 'B' cross reference  Used to look up by HCPCS 
GLOBAL REFERENCE: RMPR(661.1,'C'
 GLOBAL DESCRIPTION:   'C' cross reference - used to look up by SHORT NAME 
GLOBAL REFERENCE: RMPR(661.1,'ASHD'
 GENERAL DESCRIPTION:   The PROSTHETIC HCPCS FILE #661.1 is read when creating
 a GIP Stock Issue, creating a Prosthetics purchase card order, displaying 2319 
 appliance transactions, and producing the PFFS and NPPD lists.  It is also
 used when extracting 2319 data for determination of duplicate appliance
 transactions issued to a patient.  In inventory processing, this file is read
 and written to when an Item Master item is associated with a HCPCS via the
 Synonym field.  
  
 Above PAR Ad-Hoc Reporting includes the PROSTHETIC HCPCS FILE #661.1.  Ad-Hoc
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/16/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires information for the 
 Prosthetic HCPCS Item Master File Access.  
  DATE ACTIVATED: APR 13, 2021

NUMBER: 6507                            IA #: 6507
  FILE NUMBER: 6914.8                   GLOBAL ROOT: ENG(6914.8)
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: NX DISPOSITION METHOD ACCESS
  ID: ENG(6914.8)
GLOBAL REFERENCE: ENG(6914.8,D0,0)
FIELD NUMBER: .01                       FIELD NAME: METHOD
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: METHOD NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG(6914.8,'B'
 GLOBAL DESCRIPTION:   Cross reference Equipment field METHOD (#.01) 
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the NX
 DISPOSITION METHOD File #6914.8 to display information within the Equipment
 and Turn-In functions.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 06, 2022

NUMBER: 6508                            IA #: 6508
  FILE NUMBER: 6915.11                  GLOBAL ROOT: ENG(6915.11)
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: AV REASON ACCESS
  ID: ENG(6915.11)
GLOBAL REFERENCE: ENG(6915.11,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the AV
 REASON File #6915.11 to display information within the Equipment function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 12, 2019

NUMBER: 6509                            IA #: 6509
  FILE NUMBER: 662                      GLOBAL ROOT: RMPR(662,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROS DISABILITY CODE FILE ACCESS
  ID: RMPR(662,
GLOBAL REFERENCE: RMPR(662,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ARABIC DISABILITY NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4
  FIELD NAME: MAJOR DISABILITY CODE SYMBOLS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: GROUP EXTENT OF DISABILITY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 5.5                       FIELD NAME: DISABILITY GROUPING
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(662,'B'
 GLOBAL DESCRIPTION:   "B" CROSS REFERENCE - Used to look up by ARABIC
 DISABILITY NAME 
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT) reads
 the PROS DISABILITY CODE File (#662) when adding disability codes to a patient 
 and to display those disability codes on the 2319.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUL 30, 2020

NUMBER: 6510                            IA #: 6510
  FILE NUMBER: 664                      GLOBAL ROOT: RMPR(664,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROSTHETICS 1358 FILE ACCESS
  ID: RMPR(664,
GLOBAL REFERENCE: RMPR(664,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .5                        FIELD NAME: OBLIGATION NUMBER
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: VENDOR
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: CANCELLATION DATE
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: C.P.
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: REFERENCE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: CLOSE OUT DATE
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: INITIATOR
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11                        FIELD NAME: EST. SHIPPING CHARGE
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12                        FIELD NAME: ACT. SHIPPING CHARGE
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13                        FIELD NAME: SHIPPING ENTRY
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: PICKUP/DELIVERY REMARKS
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 18                        FIELD NAME: STATION NAME
  LOCATION: 0;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 22                        FIELD NAME: WORK ORDER NUMBER
  LOCATION: 0;15                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 23                        FIELD NAME: LAB TECHNICIAN
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 24                        FIELD NAME: 2529-3
  LOCATION: 0;17                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(664,D0,1,0)
FIELD NUMBER: .01                       FIELD NAME: BILLING ITEM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(664,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: BILLING ITEM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: BRIEF DESCRIPTION
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: UNIT COST
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: QTY
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: UNIT OF ISSUE
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: AMIS FLAG
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: ACT UNIT COST
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7                         FIELD NAME: REMARKS
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8                         FIELD NAME: TYPE OF TRANSACTION
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: PATIENT CATEGORY
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SPECIAL CATEGORY
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11                        FIELD NAME: SOURCE
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12                        FIELD NAME: APPLIANCE/REPAIR
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13                        FIELD NAME: CONTRACT #
  LOCATION: 0;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 15                        FIELD NAME: SERIAL NUMBER
  LOCATION: 0;15                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16                        FIELD NAME: PSAS HCPCS
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 19                        FIELD NAME: NUMBER OF BIDS
  LOCATION: 0;17                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(664,D0,1,D1,1,D2,0)
FIELD NUMBER: 14                        FIELD NAME: EXTENDED DESCRIPTION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(664,D0,1,D1,2)
FIELD NUMBER: 15.2                      FIELD NAME: MANUFACTURER
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 15.4                      FIELD NAME: MODEL
  LOCATION: 2;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 15.6                      FIELD NAME: LOT #
  LOCATION: 2;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 18                        FIELD NAME: EXCLUDE/WAIVER
  LOCATION: 2;4                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(664,D0,1,D1,4)
FIELD NUMBER: 17                        FIELD NAME: VENDOR TRACKING NUMBER
  LOCATION: 4;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   
                                       Global r 
FIELD NUMBER: 16.1                      FIELD NAME: CPT MODIFIER
  LOCATION: 4;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   
                                       Global r 
GLOBAL REFERENCE: RMPR(664,D0,2)
FIELD NUMBER: 3.1                       FIELD NAME: CANCELLATION REMARKS
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.2                       FIELD NAME: CANCELLED BY
  LOCATION: 2;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.1                       FIELD NAME: CLOSE-OUT-REMARKS
  LOCATION: 2;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 15                        FIELD NAME: FORM TYPE
  LOCATION: 2;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16                        FIELD NAME: PSC CATEGORY
  LOCATION: 2;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17                        FIELD NAME: PERCENT DISCOUNT
  LOCATION: 2;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.5                       FIELD NAME: CLOSED BY
  LOCATION: 2;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.6                       FIELD NAME: LAST IFCAP AMEND BY
  LOCATION: 2;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.7                       FIELD NAME: LAST AMEND TOTAL
  LOCATION: 2;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.8                       FIELD NAME: LAST AMEND REPRINT OK
  LOCATION: 2;10                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(664,D0,3)
FIELD NUMBER: 19                        FIELD NAME: DELIVER TO
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20                        FIELD NAME: DATE REQUIRED
  LOCATION: 3;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21                        FIELD NAME: DELIVERY TIME
  LOCATION: 3;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21.1                      FIELD NAME: DELIVER TO ATTENTION
  LOCATION: 3;4                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(664,D0,4)
FIELD NUMBER: 25                        FIELD NAME: PURCHASE CARD NUMBER
  LOCATION: 4;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 26                        FIELD NAME: BANK AUTHORIZATION NUMBER
  LOCATION: 4;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 27                        FIELD NAME: EST AMOUNT
  LOCATION: 4;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 28                        FIELD NAME: CLOSE-OUT AMOUNT
  LOCATION: 4;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7.5                       FIELD NAME: PURCHASE CARD REFERENCE
  LOCATION: 4;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7.1                       FIELD NAME: IFCAP ORDER
  LOCATION: 4;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 29                        FIELD NAME: NEW PURCHASE CARD NUMBER
  LOCATION: 4;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 30                        FIELD NAME: AUDIT REPAIR
  LOCATION: 4;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: AUDIT DATE
  LOCATION: 4;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664,'B'
 GLOBAL DESCRIPTION:   File 664 'B' cross reference  Used to process in DATE
 order 
                               or to look up by DATE 
GLOBAL REFERENCE: RMPR(664,'C'
 GLOBAL DESCRIPTION:   File 664 'C' cross reference  Used to look up by PATIENT 
GLOBAL REFERENCE: RMPR(664,'E'
 GLOBAL DESCRIPTION:   File 664 'E' cross reference  Used to look up by BILLING
 ITEM 
GLOBAL REFERENCE: RMPR(664,'G'
 GLOBAL DESCRIPTION:   File 664 'G' cross reference  Used to look up by
 Purchase Card 
                               Reference 
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT) writes
 to the PROSTHETIC 1358 File (#664) to record the creation of a Prosthetic 
 purchase card order, to delete a specific PROSTHETIC 1358 record, and to read
 the PROSTHETIC 1358 file to display the Prosthetic 1358.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: SEP 10, 2019

NUMBER: 6511                            IA #: 6511
  FILE NUMBER: 6915.2                   GLOBAL ROOT: ENG(6915.2)
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FA DOCUMENT LOG ACCESS
  ID: ENG(6915.2)
GLOBAL REFERENCE: ENG(6915.2,D0,0)
FIELD NUMBER: 303                       FIELD NAME: AV REASON
  LOCATION: 300;3                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG(6915.2,'B'
 GLOBAL DESCRIPTION:   Cross Refence 'B' field EQUIPMENT RECORD (#.01) 
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the FA
 DOCUMENT LOG File # 6915.2 to display information within the Equipment
 function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 07, 2022

NUMBER: 6512                            IA #: 6512
  FILE NUMBER: 6917                     GLOBAL ROOT: ENCSN(6917)
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CATEGORY STOCK NUMBER FILE ACCESS
  ID: ENCSN(6917)
GLOBAL REFERENCE: ENCSN(6917,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: LIFE EXPECTANCY
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENCSN(6917,'B'
 GLOBAL DESCRIPTION:   'B' cross reference Used to look up by Name 
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the CATEGORY
 STOCK NUMBER FILE #6917 to display information within the Equipment function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 12, 2019

NUMBER: 6513                            IA #: 6513
  FILE NUMBER: 6918.1                   GLOBAL ROOT: ENG(6918.1,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: UTILITY SYSTEMS ACCESS
  ID: ENG(6918.1,
GLOBAL REFERENCE: ENG(6918.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the UTILITY
 SYSTEMS File #6918.1  to display information within the Equipment function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 12, 2019

NUMBER: 6514                            IA #: 6514
  FILE NUMBER: 6920.1                   GLOBAL ROOT: ENG(6920.1,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: NEW WORK ACTION ACCESS
  ID: ENG(6920.1,
GLOBAL REFERENCE: ENG(6920.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: HISTORY CODE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG(6920.1,'B'
 GLOBAL DESCRIPTION:   Cross Reference field NAME (#.01) 
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the NEW WORK
 ACTION File #6920.1 to display information within the Work Order module.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 07, 2022

NUMBER: 6515                            IA #: 6515
  FILE NUMBER: 6922                     GLOBAL ROOT: DIC(6922,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ENGINEERING SECTION LIST ACCESS
  ID: DIC(6922,
GLOBAL REFERENCE: DIC(6922,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ENGINEERING SECTION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ABBREVIATION
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DIC(6922,'B',ENSEC
 GLOBAL DESCRIPTION:   Cross Reference field ENGINEERING SECTION (#.01) 
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the
 ENGINEERING SECTION LIST File #6922 to display information within the Work
 Order function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 07, 2022

NUMBER: 6516                            IA #: 6516
  FILE NUMBER: 6928                     GLOBAL ROOT: ENG('SP',
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ENG SPACE ACCESS
  ID: ENG('SP',
GLOBAL REFERENCE: ENG('SP',D0,0)
FIELD NUMBER: .01                       FIELD NAME: ROOM NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG('SP',D0,4)
FIELD NUMBER: 2.6                       FIELD NAME: FUNCTION
  LOCATION: 4;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG('SP','B',RN
 GLOBAL DESCRIPTION:   Cross reference by Room Number, field ROOM NUMBER (#.01) 
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the ENG
 SPACE File #6928 to display information within the Equipment and Work Order
 functions.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 06, 2022

NUMBER: 6517                            IA #: 6517
  FILE NUMBER: 6929                     GLOBAL ROOT: ENG('EMP',
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ENG EMPLOYEE ACCESS
  ID: ENG('EMP',
GLOBAL REFERENCE: ENG('EMP',D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: WAGE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: STATUS
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .3                        FIELD NAME: SHOP
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG('EMP',D0,.1)
FIELD NUMBER: .1                        FIELD NAME: ORGANIZATIONAL TITLE
  LOCATION: .1;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG('EMP','B',ENM
 GLOBAL DESCRIPTION:   Cross reference Employee's Name field NAME (#.01) 
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the ENG
 EMPLOYEE File #6929 to display information with in the Work Order function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 06, 2022

NUMBER: 6518                            IA #: 6518
  FILE NUMBER: 410.3                    GLOBAL ROOT: PRCS(410.3,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: REPETITIVE ITEM LIST ACCESS
  ID: PRCS(410.3,
GLOBAL REFERENCE: PRCS(410.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ENTRY NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TOTAL COST
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: INVENTORY/DISTRIBUTION POINT
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: DATE/TIME CREATED
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410.3,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ITEM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: QUANTITY
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: VENDOR
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: EST. ITEM (UNIT) COST
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: VENDOR (POINTER)
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCS(410.3,'B'
 GLOBAL DESCRIPTION:   'B' cross reference - used to look up by ENTRY NUMBER 
 GENERAL DESCRIPTION:   Above PAR requests permission to write to the
 REPETITIVE ITEM LIST File #410.3 to record additions and edits of Repetitive
 Item Requests within the Inventory function.  
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: FEB 17, 2022

NUMBER: 6519                            IA #: 6519
  FILE NUMBER: 413.7                    GLOBAL ROOT: PRCN(413.7,
  DATE CREATED: OCT 17, 2016
  CUSTODIAL PACKAGE: EQUIPMENT/TURN-IN REQUEST
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: COUNTER FILE ACCESS
  ID: PRCN(413.7,
GLOBAL REFERENCE: PRCN(413.7,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: LAST NUMBER USED
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
 GENERAL DESCRIPTION:   Above PAR requests permission to write to the COUNTER
 FILE #413.7 to create temporary transaction numbers for turn-in requests.  
  
 Above PAR Ad-Hoc Reporting includes the COUNTER FILE #413.7. Ad-Hoc 
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUL 31, 2020

NUMBER: 6520                            IA #: 6520
  FILE NUMBER: 442.3                    GLOBAL ROOT: PRCD(442.3,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  NAME: PURCHASE ORDER STATUS ACCESS    ID: PRCD(442.3,
GLOBAL REFERENCE: PRCD(442.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the PURCHASE
 ORDER STATUS File #442.3 to display information within the Inventory function. 
  
 APAT reads from the PURCHASE ORDER STATUS (#442.3) file to determine the 
 status of a purchase card order.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL

NUMBER: 6521                            IA #: 6521
  FILE NUMBER: 444.2                    GLOBAL ROOT: PRC(444.2,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  NAME: SIC CODE FILE ACCESS            ID: PRC(444.2,
GLOBAL REFERENCE: PRC(444.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the SIC CODE
 File #444.2 to display information within the Inventory function.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6522                            IA #: 6522
  FILE NUMBER: 445.3                    GLOBAL ROOT: PRCP(445.3,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: INTERNAL DISTRIBUTION ORDER/ADJ. ACCESS
  ID: PRCP(445.3,
GLOBAL REFERENCE: PRCP(445.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PRIMARY INVENTORY POINT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: SECONDARY INVENTORY PT
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DATE
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: ENTERED BY
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: ORDER STATUS
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: PICKING TICKET PRINTED
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.5                       FIELD NAME: TYPE
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: DATE POSTED
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: TRANSMISSION DATE/TIME
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445.3,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ITEM NO.
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: QTY.(PRIMARY UNIT OF ISSUE)
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2
  FIELD NAME: UNIT PRICE (PRI.UNIT OF ISSUE)
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: QTY.BACK-ORDERED(PRI.UNIT)
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: ADJUST PRIMARY INVENTORY?
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: ADJUST SECONDARY INVENTORY?
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: QTY POSTED
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445.3,D0,2)
FIELD NUMBER: 129                       FIELD NAME: PATIENT NAME
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 130                       FIELD NAME: SCHEDULED OPERATION
  LOCATION: 2;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 131                       FIELD NAME: INVENTORY PATIENT LINK
  LOCATION: 2;3                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445.3,D0,8)
FIELD NUMBER: 8                         FIELD NAME: REMARKS
  LOCATION: 8;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445.3,'B'
 GLOBAL DESCRIPTION:   'B' cross reference - used to look up by NUMBER 
 GENERAL DESCRIPTION:   Above PAR requests permission to read and write to the
 INTERNAL DISTRIBUTION ORDER/ADJ. FILE #445.3 to display and record
 Distribution Orders within the Inventory function.  
  
 Above PAR Ad-Hoc Reporting includes the INTERNAL DISTRIBUTION ORDER/ADJ FILE
 #445.3. Ad-Hoc functionality provides the ability to select fields from the
 file for display on user-defined reports.  Ad-Hoc offers only FileMan read
 access and only if the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: FEB 17, 2022

NUMBER: 6523                            IA #: 6523
  FILE NUMBER: 445.5                    GLOBAL ROOT: PRCP(445.5,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: AUTOMATED SUPPLY STATIONS ACCESS
  ID: PRCP(445.5,
GLOBAL REFERENCE: PRCP(445.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: INVENTORY UPDATES
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: LINK NAME
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the
 AUTOMATED SUPPLY STATIONS File #445.5 to validate that the Automated Supply
 Station is defined.  
  
 Permission is also requested in order to: 1. Retrieve the value of the
 INVENTORY UPDATES field for use in logic for populating the Item Name subfield
 the HL7 message's RQD segment.  
  
 2. Retrieve the value of the LINK NAME for use in specifying the link over
 which the HL7 message will be sent to the Supply Station's database.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: DEC 07, 2018

NUMBER: 6524                            IA #: 6524
  FILE NUMBER: 445.6                    GLOBAL ROOT: PRCP(445.6,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: GROUP CATEGORY FILE ACCESS
  ID: PRCP(445.6,
GLOBAL REFERENCE: PRCP(445.6,D0,0)
FIELD NUMBER: .01                       FIELD NAME: GROUP CATEGORY CODE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: INVENTORY/DISTRIBUTION POINT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2                         FIELD NAME: DESCRIPTION
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: PRCP(445.6,'B',
 GLOBAL DESCRIPTION:   "B" cross reference - Used to look up by  GROUP CATEGORY
 CODE 
 GENERAL DESCRIPTION:   Above PAR requests permission to read and write to the
 GROUP CATEGORY FILE #445.6 to display, add, edit, and delete GROUP CATEGORY
 entries.  
  
 Above PAR Ad-Hoc Reporting includes the GROUP CATEGORY FILE #445.6.  Ad-Hoc
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: MAR 04, 2022

NUMBER: 6525                            IA #: 6525
  FILE NUMBER: 446.1                    GLOBAL ROOT: PRCP(446.1,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: INVENTORY DISTRIBUTED PATIENT SUPPLIES ACCESS
  ID: PRCP(446.1,
GLOBAL REFERENCE: PRCP(446.1,D0,0)
FIELD NUMBER: 4                         FIELD NAME: FROM INVENTORY POINT
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
 GENERAL DESCRIPTION:   Above PAR requests permission to read and write to the
 INVENTORY DISTRIBUTED PATIENT SUPPLIES FILE #446.1 to display and edit the
 inventory point within the file if a Distribution Order is posted with patient 
 supplies.  
  
 Above PAR Ad-Hoc Reporting includes the INVENTORY DISTRIBUTED PATIENT SUPPLIES
 FILE #446.1. Ad-Hoc functionality provides the ability to select fields from
 the file for display on user-defined reports.  Ad-Hoc offers only FileMan read
 access and only if the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: MAR 26, 2018

NUMBER: 6526                            IA #: 6526
  FILE NUMBER: 446.4                    GLOBAL ROOT: PRCT(446.4,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: BARCODE PROGRAM FILE ACCESS
  ID: PRCT(446.4,
GLOBAL REFERENCE: PRCT(446.4,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: .02                       FIELD NAME: IDENTIFIER
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: .03                       FIELD NAME: POST UPLOAD ROUTINE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: PRCT(446.4,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME OF DATA UPLOAD
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: .02                       FIELD NAME: UPLOAD USER
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: .03                       FIELD NAME: STATUS
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: PRCT(446.4,D0,2,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: BARCODE DATA
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: PRCT(446.4,'C'
 GLOBAL DESCRIPTION:   
  "C" cross reference - used to search by IDENTIFIER 
 GENERAL DESCRIPTION:   Above PAR requests permission to read and write to the
 BARCODE PROGRAM File #446.4 to record and display uploads from the Bar Code
 Reader.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: MAR 04, 2022

NUMBER: 6527                            IA #: 6527
  FILE NUMBER: 446.5                    GLOBAL ROOT: PRCT(446.5,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CUSTOM LABEL FILE ACCESS
  ID: PRCT(446.5,
GLOBAL REFERENCE: PRCT(446.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PRCT(446.5,D0,3,D1,0)
FIELD NUMBER: .01                       FIELD NAME: FILEMAN CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the CUSTOM
 LABEL File # 446.5 to display information within the Inventory function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: MAR 26, 2018

NUMBER: 6528                            IA #: 6528
  FILE NUMBER: 447                      GLOBAL ROOT: PRCP(447,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INVENTORY LOCK MANAGEMENT
  ID: PRCP(447,
GLOBAL REFERENCE: PRCP(447,D0,0)
FIELD NUMBER: .01                       FIELD NAME: FILE-ENTRY-SUBENTRY
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: USER
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2                         FIELD NAME: DATE@TIME LOCKED
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 3                         FIELD NAME: PROCESS
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
 GENERAL DESCRIPTION:   Above PAR requests permission to read and write to the
 INVENTORY LOCK MANAGEMENT File #447 to display and update the Lock management
 information within the Inventory function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: MAR 26, 2018

NUMBER: 6529                            IA #: 6529
  FILE NUMBER: 9.7                      GLOBAL ROOT: XPD(9.7,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INSTALL FILE ACCESS
  ID: XPD(9.7,
GLOBAL REFERENCE: XPD(9.7,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: STATUS
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DATE LOADED
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: XPD(9.7,D0,1)
FIELD NUMBER: 17                        FIELD NAME: INSTALL COMPLETE TIME
  LOCATION: 1;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 51                        FIELD NAME: DISTRIBUTION DATE
  LOCATION: 1;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: XPD(9.7,D0,2)
FIELD NUMBER: 6                         FIELD NAME: FILE COMMENT
  LOCATION: 2;E1,240                    ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Above PAR and Advanced Prosthetics Acquisition Tool
 request permission to read from the INSTALL FILE (#9.7) to display information
 about the last install within the Administrator function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUL 11, 2023

NUMBER: 6530                            IA #: 6530
  FILE NUMBER: 440                      GLOBAL ROOT: PRC(440,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VENDOR FILE ACCESS
  ID: PRC(440,
GLOBAL REFERENCE: PRC(440,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ORDERING ADDRESS 1
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ORDERING ADDRESS2
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: ORDERING ADDRESS3
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: ORDERING ADDRESS4
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.2                       FIELD NAME: ORDERING CITY
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.4                       FIELD NAME: ORDERING STATE
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.6                       FIELD NAME: ORDERING ZIP CODE
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.8                       FIELD NAME: PROCUREMENT CONTACT PERSON
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: VENDOR PHONE NUMBER
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05                       FIELD NAME: SUPPLY WHSE. INDICATOR
  LOCATION: 0;11                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(440,D0,.11)
FIELD NUMBER: 22.1                      FIELD NAME: BILLING ADDRESS1
  LOCATION: .11;1                       ACCESS: Read w/Fileman
FIELD NUMBER: 22.2                      FIELD NAME: BILLING ADDRESS2
  LOCATION: .11;2                       ACCESS: Read w/Fileman
FIELD NUMBER: 22.3                      FIELD NAME: BILLING ADDRESS3
  LOCATION: .11;3                       ACCESS: Read w/Fileman
FIELD NUMBER: 22.4                      FIELD NAME: BILLING CITY
  LOCATION: .11;4                       ACCESS: Read w/Fileman
FIELD NUMBER: 22.5                      FIELD NAME: BILLING STATE
  LOCATION: .11;5                       ACCESS: Read w/Fileman
FIELD NUMBER: 22.6                      FIELD NAME: BILLING ZIP CODE
  LOCATION: .11;6                       ACCESS: Read w/Fileman
FIELD NUMBER: 22.7                      FIELD NAME: BILLING PHONE NUMBER
  LOCATION: .11;7                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(440,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: TYPE OF OWNERSHIP
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440,D0,1.1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SOCIOECONOMIC GROUP(FPDS)
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440,D0,2)
FIELD NUMBER: 5.1                       FIELD NAME: ACCOUNT NO.
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: FEDERAL SOURCE
  LOCATION: 2;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.3                       FIELD NAME: BUSINESS TYPE (FPDS)
  LOCATION: 2;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.7                       FIELD NAME: COUNTY
  LOCATION: 2;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8                         FIELD NAME: LABOR SURPLUS AREA?
  LOCATION: 2;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.2                       FIELD NAME: BUSINESS TYPE (FPDS-88)
  LOCATION: 2;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13                        FIELD NAME: IS A SF129 ON FILE?
  LOCATION: 2;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: DATE OF SF129
  LOCATION: 2;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.4                      FIELD NAME: AUSTIN DELETED?
  LOCATION: 2;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 12.5                      FIELD NAME: FEE VENDOR
  LOCATION: 2;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 5.2                       FIELD NAME: GUARANTEED DELIVERY VENDOR?
  LOCATION: 2;11                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440,D0,3)
FIELD NUMBER: 11                        FIELD NAME: SPECIAL FACTORS
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .2                        FIELD NAME: EDI VENDOR?
  LOCATION: 3;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .4                        FIELD NAME: VENDOR ID NUMBER
  LOCATION: 3;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 34                        FIELD NAME: FMS VENDOR CODE
  LOCATION: 3;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 35                        FIELD NAME: ALT-ADDR-IND
  LOCATION: 3;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 36
  FIELD NAME: NON-RECURRING/RECURRING VENDOR
  LOCATION: 3;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 34.5                      FIELD NAME: FMS VENDOR NAME
  LOCATION: 3;7                         ACCESS: Read w/Fileman
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
FIELD NUMBER: 40                        FIELD NAME: PAYMENT HOLD INDICATOR
  LOCATION: 3;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 41                        FIELD NAME: 1099 VENDOR INDICATOR
  LOCATION: 3;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 42                        FIELD NAME: PENDING FLAG
  LOCATION: 3;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 43                        FIELD NAME: CENTRAL REMIT
  LOCATION: 3;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 44                        FIELD NAME: VENDOR TYPE
  LOCATION: 3;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 45                        FIELD NAME: MTI ACTION
  LOCATION: 3;15                        ACCESS: Read w/Fileman
FIELD NUMBER: 55                        FIELD NAME: UEI
  LOCATION: 3;16                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(440,D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CONTRACT/BOA NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: EXPIRATION DATE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .5                        FIELD NAME: BEGINING DATE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PROMPT PAYMENT TERMS %
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PROMPT PAYMENT TERMS DAYS
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: CONTRACT FLAG
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440,D0,4,D1,1)
FIELD NUMBER: 2                         FIELD NAME: CONTRACT TERMS
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440,D0,5,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SYNONYM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440,D0,6)
FIELD NUMBER: 16                        FIELD NAME: SERVICE/RETURN ADDRESS1
  LOCATION: 6;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 16.1                      FIELD NAME: SERVICE/RETURN ADDRESS2
  LOCATION: 6;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 16.2                      FIELD NAME: SERVICE/RETURN ADDRESS3
  LOCATION: 6;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 16.3                      FIELD NAME: SERVICE/RETURN ADDRESS4
  LOCATION: 6;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 16.4                      FIELD NAME: SERVICE/RETURN CITY
  LOCATION: 6;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 16.5                      FIELD NAME: SERVICE/RETURN STATE
  LOCATION: 6;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 16.6                      FIELD NAME: SERVICE/RETURN ZIP CODE
  LOCATION: 6;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 16.7                      FIELD NAME: SERVICE CONTACT PERSON
  LOCATION: 6;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 16.8                      FIELD NAME: SERVICE PHONE NO.
  LOCATION: 6;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(440,D0,7)
FIELD NUMBER: 17                        FIELD NAME: PAYMENT CONTACT PERSON
  LOCATION: 7;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.2                      FIELD NAME: PAYMENT PHONE NO.
  LOCATION: 7;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.3                      FIELD NAME: PAYMENT ADDRESS1
  LOCATION: 7;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.4                      FIELD NAME: PAYMENT ADDRESS2
  LOCATION: 7;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.5                      FIELD NAME: PAYMENT ADDRESS3
  LOCATION: 7;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 17.6                      FIELD NAME: PAYMENT ADDRESS4
  LOCATION: 7;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 17.7                      FIELD NAME: PAYMENT CITY
  LOCATION: 7;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.8                      FIELD NAME: PAYMENT STATE
  LOCATION: 7;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.9                      FIELD NAME: PAYMENT ZIP CODE
  LOCATION: 7;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 18                        FIELD NAME: CALM ID NUMBER
  LOCATION: 7;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 18.2                      FIELD NAME: CALM STUB NAME
  LOCATION: 7;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 18.3                      FIELD NAME: DUN & BRADSTREET #
  LOCATION: 7;12                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440,D0,8,D1,0)
FIELD NUMBER: .01                       FIELD NAME: REMARKS
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440,D0,9)
FIELD NUMBER: 15                        FIELD NAME: REPLACEMENT VENDOR CREATED
  LOCATION: 9;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440,D0,10)
FIELD NUMBER: 30                        FIELD NAME: DATE VENDOR CREATED
  LOCATION: 10;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: CREATED BY
  LOCATION: 10;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 32                        FIELD NAME: DATE INACTIVATED
  LOCATION: 10;3                        ACCESS: Read w/Fileman
FIELD NUMBER: 33                        FIELD NAME: INACTIVATED BY
  LOCATION: 10;4                        ACCESS: Read w/Fileman
FIELD NUMBER: 31.5                      FIELD NAME: INACTIVATED VENDOR
  LOCATION: 10;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 46                        FIELD NAME: FAX #
  LOCATION: 10;6                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440,'B',
 GLOBAL DESCRIPTION:   "B" cross reference      Used to look up by NAME 
GLOBAL REFERENCE: PRC(440,'AC',
 GLOBAL DESCRIPTION:   "AC" cross reference     Used to look up by SUPPLY WHSE.
 INDICATOR 
GLOBAL REFERENCE: PRC(440,D0,4,'B',
 GLOBAL DESCRIPTION:   "B" cross reference     Used to look up by CONTRACT/BOA
 NUMBER 
GLOBAL REFERENCE: PRC(440,'D',
 GLOBAL DESCRIPTION:   "D" cross reference       Used to look up by FMS VENDOR
 CODE 
 GENERAL DESCRIPTION:   Above PAR and the Advanced Prosthetics Acquisition Tool
 (APAT) request permission to read from the VENDOR FILE #440 to display
 information within the Equipment, Work Order and Inventory functions and when 
 creating and displaying purchasing documents.  Above PAR also updates the 
 VENDOR (#440) File.                  
  
 Above PAR Ad-Hoc Reporting includes the VENDOR FILE #440.  Ad-Hoc 
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   3/29/23 Added UEI field 55, effective with DSSO*2.0*3 
  DATE ACTIVATED: MAR 30, 2023

NUMBER: 6531                            IA #: 6531
  FILE NUMBER: 441                      GLOBAL ROOT: PRC(441,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ITEM MASTER FILE ACCESS
  ID: PRC(441,
GLOBAL REFERENCE: PRC(441,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: .05                       FIELD NAME: SHORT DESCRIPTION
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2                         FIELD NAME: FSC
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 9                         FIELD NAME: LAST VENDOR ORDERED
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 5                         FIELD NAME: NSN
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: .06
  FIELD NAME: CASE CART/TRAY/INSTRUMENT KIT
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 13                        FIELD NAME: SET/PACK ASSEMBLED BY
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 10                        FIELD NAME: MANDATORY SOURCE
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 14                        FIELD NAME: DATE ITEM CREATED
  LOCATION: 0;9                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 12                        FIELD NAME: BOC
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 15                        FIELD NAME: CREATED BY
  LOCATION: 0;11                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 3                         FIELD NAME: INC
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 23                        FIELD NAME: REUSABLE ITEM
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 7                         FIELD NAME: HAZARDOUS MATERIAL
  LOCATION: 0;14                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 51                        FIELD NAME: NIF ITEM NUMBER
  LOCATION: 0;15                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(441,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: PRC(441,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: VENDOR
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: UNIT COST
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2                         FIELD NAME: CONTRACT
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 3                         FIELD NAME: VENDOR STOCK #
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 4                         FIELD NAME: NDC
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2.5                       FIELD NAME: DATE OF UNIT PRICE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1.5                       FIELD NAME: UNIT OF PURCHASE
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1.6                       FIELD NAME: PACKAGING MULTIPLE
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 8.5                       FIELD NAME: MAXIMUM ORDER QTY
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 10                        FIELD NAME: UNIT CONVERSION FACTOR
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 9                         FIELD NAME: REQUIRED ORDER MULTIPLE
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 8                         FIELD NAME: MINIMUM ORDER QTY
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: PRC(441,D0,3)
FIELD NUMBER: 16                        FIELD NAME: INACTIVATED ITEM?
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 17                        FIELD NAME: DATE INACTIVATED
  LOCATION: 3;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 18                        FIELD NAME: INACTIVATED BY
  LOCATION: 3;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 16.5                      FIELD NAME: REPLACEMENT ITEM
  LOCATION: 3;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 19                        FIELD NAME: MFG PART NO
  LOCATION: 3;5                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 5.5                       FIELD NAME: NSN VERIFIED
  LOCATION: 3;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 20                        FIELD NAME: FOOD GROUP
  LOCATION: 3;7                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 21                        FIELD NAME: SKU
  LOCATION: 3;8                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 22                        FIELD NAME: DRUG TYPE CODE
  LOCATION: 3;9                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 24                        FIELD NAME: SIC CODE
  LOCATION: 3;10                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 25                        FIELD NAME: MANUFACTURER
  LOCATION: 3;12                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(441,D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: FCP
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2                         FIELD NAME: SUBACCOUNT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 3                         FIELD NAME: PREFERRED VENDOR
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: PRC(441,D0,4,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: PURCHASE ORDER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: PRC(441,D0,5,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SYNONYM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: PRC(441,D0,8,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PRE_NIF LONG DESCRIPTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(441,D0,9)
FIELD NUMBER: 52                        FIELD NAME: PRE_NIF SHORT DESCRIPTION
  LOCATION: 9;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Above PAR and the Advanced Prosthetics Acquisition Tool
 (APAT) request permission to add, edit, and display ITEM MASTER FILE #441
 data.  
  
 Above PAR adds, edits, and displays items in the ITEM MASTER FILE #441 as part
 of its Inventory functionality.  Above PAR Ad-Hoc Reporting provides the
 ability to select fields from the file for display on user-defined reports. 
 Ad-Hoc offers only FileMan read access and only if the user has permission to
 view the file.  
  
 The Advanced Prosthetics Acquisition Tool (APAT) reads from the ITEM MASTER
 FILE #441 when creating patient-centric purchase card orders, detailed
 purchase card orders, and GIP and PIP stock issues as well as when displaying
 Prosthetic appliance transaction information on the 2319.  The detailed
 purchase card order functionality also performs FileMan writes to specified
 fields of the ITEM MASTER #441 as each item is added to the order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JAN 12, 2023

NUMBER: 6532                            IA #: 6532
  FILE NUMBER: 441.2                    GLOBAL ROOT: PRC(441.2,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: FEDERAL SUPPLY CLASSIFICATION ACCESS
  ID: PRC(441.2,
GLOBAL REFERENCE: PRC(441.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ABBREVIATED DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: COMMODITY CODE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(441.2,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(441.2,'D'
 GLOBAL DESCRIPTION:   'D' cross reference Used to look up by ABBREVIATED
 DESCRIPTION 
GLOBAL REFERENCE: PRC(441.2,'B'
 GLOBAL DESCRIPTION:   File 441.2 "B" cross-reference   Used in generating a
 list of 
                                  FSC/PSCs via a VA FileMan API call 
                                  specifying the "B" index 
 GENERAL DESCRIPTION:   Above PAR and the Advanced Prosthetics Acquisition Tool
 (APAT) request permission to read from the FEDERAL SUPPLY CLASSIFICATION File
 (#441.2) to display information within the Inventory and Create Detailed 
 Purchase Card Order functionality.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 4/28/23, the list of FSC/PSCs is generated via a
 VA FileMan API call specifying the "B" index.  
  DATE ACTIVATED: APR 28, 2023

NUMBER: 6533                            IA #: 6533
  FILE NUMBER: 663                      GLOBAL ROOT: RMPR(663,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROS AMIS CODES FILE ACCESS
  ID: RMPR(663,
GLOBAL REFERENCE: RMPR(663,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: LINE DESCRIPTION
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: ISSUE/REPAIR CODE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: RMPR(663,'B')
 GLOBAL DESCRIPTION:   File 663 "B" cross reference - used to look up by CODE 
 GENERAL DESCRIPTION:   The PROS AMIS CODES (#663) File is read during
 inventory processing in order to present valid AMIS Codes based on the
 Issue/Repair Code.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: SEP 10, 2019

NUMBER: 6534                            IA #: 6534
  FILE NUMBER: 664.1                    GLOBAL ROOT: RMPR(664.1,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROSTHETIC 2529-3 FILE ACCESS
  ID: RMPR(664.1,
GLOBAL REFERENCE: RMPR(664.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   
                                       Global r 
FIELD NUMBER: .02                       FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: STATION
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: REQUESTING STATION
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13                        FIELD NAME: REQUESTING OFFICIAL
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: ELIGIBILITY STATUS
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: APPROVING OFFICIAL
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: SUSPENSE RECORD
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .09                       FIELD NAME: DATE REQUIRED
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TRANSACTION TYPE
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: SOURCE OF PROCUREMENT
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 34                        FIELD NAME: NO COUNT WORK ORDER
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: WORK ORDER NUMBER
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   
                                       Global r 
FIELD NUMBER: 31                        FIELD NAME: AMIS GROUPER
  LOCATION: 0;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .11                       FIELD NAME: RECEIVING STATION
  LOCATION: 0;15                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 15                        FIELD NAME: TECHNICIAN
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16                        FIELD NAME: STATUS
  LOCATION: 0;17                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17                        FIELD NAME: REQUESTOR DATE
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 18                        FIELD NAME: APPROVING DATE
  LOCATION: 0;19                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 32                        FIELD NAME: NO LAB COUNT
  LOCATION: 0;20                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21                        FIELD NAME: INSPECTING OFFICIAL
  LOCATION: 0;21                        ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: SPECIAL CATEGORY
  LOCATION: 0;22                        ACCESS: Read w/Fileman
FIELD NUMBER: 28                        FIELD NAME: NO ADMIN COUNT
  LOCATION: 0;23                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 30                        FIELD NAME: JOB # COUNT
  LOCATION: 0;24                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 22                        FIELD NAME: COMPLETED BY
  LOCATION: 0;25                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   
                                       Global r 
FIELD NUMBER: 23                        FIELD NAME: CLOSE-OUT DATE
  LOCATION: 0;26                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 24                        FIELD NAME: DELIVERY STATUS
  LOCATION: 0;27                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664.1,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DISABILITY CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: SERVICE/NON-SERVICE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ELIGIBILITY CATEGORY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: SPECIAL LEGISLATION
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664.1,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ITEM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   
                                       Global r 
FIELD NUMBER: 2                         FIELD NAME: QTY
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: UNIT OF ISSUE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: UNIT COST
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: APPLIANCE/REPAIR
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: WORK ORDER NUMBER
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8                         FIELD NAME: TYPE OF TRANSACTION
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: PATIENT CATEGORY
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SPECIAL CATEGORY
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6.5                       FIELD NAME: BRIEF DESCRIPTION
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11                        FIELD NAME: TOTAL COST
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12                        FIELD NAME: SERIAL NUMBER
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 18                        FIELD NAME: INVENTORY POINT
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(664.1,D0,2,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: EXTENDED DESCRIPTION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(664.1,D0,2,D1,2)
FIELD NUMBER: 13                        FIELD NAME: PSAS HCPCS
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13.1                      FIELD NAME: CPT MODIFIER
  LOCATION: 2;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13.2                      FIELD NAME: HIGH TECH ITEM
  LOCATION: 2;3                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(664.1,D0,2,D1,3)
FIELD NUMBER: 14                        FIELD NAME: SOURCE
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 15                        FIELD NAME: VENDOR
  LOCATION: 3;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16                        FIELD NAME: PSAS ITEM
  LOCATION: 3;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17                        FIELD NAME: ITEM LOCATION
  LOCATION: 3;4                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(664.1,D0,2,'AC'
 GLOBAL DESCRIPTION:   File 664.1/664.16 'AC' cross reference  Used to look up
 by 
                                         APPLIANCE/REPAIR 
                                         related to the ITEM 
GLOBAL REFERENCE: RMPR(664.1,D0,3)
FIELD NUMBER: 7                         FIELD NAME: CANCELLED BY
  LOCATION: 3;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: CANCEL DATE
  LOCATION: 3;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: RETURNED BY
  LOCATION: 3;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: RETURN DATE
  LOCATION: 3;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664.1,D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CANCELLATION REMARKS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664.1,D0,5,D1,0)
FIELD NUMBER: .01                       FIELD NAME: OTHER DESCRIPTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664.1,D0,6,D1,0)
FIELD NUMBER: .01                       FIELD NAME: RETURN TO LAB REASON
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664.1,D0,7)
FIELD NUMBER: 19                        FIELD NAME: DATE ASSIGNED
  LOCATION: 7;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20                        FIELD NAME: DATE DELIVERED
  LOCATION: 7;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 27                        FIELD NAME: ASSIGNED BY
  LOCATION: 7;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   
                                       Global r 
FIELD NUMBER: 33                        FIELD NAME: DATE ITEM RECEIVED
  LOCATION: 7;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 25                        FIELD NAME: TOTAL MATERIALS COST
  LOCATION: 7;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 26                        FIELD NAME: TOTAL COST
  LOCATION: 7;8                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664.1,D0,8,D1,0)
FIELD NUMBER: .01                       FIELD NAME: AUDIT DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: OLD ITEM/JOB
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: NEW ITEM/JOB
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: USER
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: RE-OPENED BY
  LOCATION: 0;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664.1,D0,8,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: REMARKS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664.1,D0,'CDR')
FIELD NUMBER: 12                        FIELD NAME: WARD LOCATION
  LOCATION: CDR;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.1                      FIELD NAME: PHYSICIAN
  LOCATION: CDR;2                       ACCESS: Read w/Fileman
FIELD NUMBER: 12.2                      FIELD NAME: DIAGNOSIS
  LOCATION: CDR;3                       ACCESS: Read w/Fileman
FIELD NUMBER: 12.3                      FIELD NAME: TRAINING SPECIALTY
  LOCATION: CDR;4                       ACCESS: Read w/Fileman
FIELD NUMBER: 12.4                      FIELD NAME: PHYSICIAN EXTENSION
  LOCATION: CDR;5                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664.1,'B'
 GLOBAL DESCRIPTION:   File 664.1 'B' cross reference  Used to look up by DATE 
GLOBAL REFERENCE: RMPR(664.1,'C'
 GLOBAL DESCRIPTION:   File 664.1 'C' cross reference  Used to look up by WORK 
                                 ORDER NUMBER 
GLOBAL REFERENCE: RMPR(664.1,'SUS'
 GLOBAL DESCRIPTION:   File 664.1 'SUS' cross reference  Used to look up by
 SUSPENSE RECORD 
 GENERAL DESCRIPTION:   The PROSTHETIC 2529-3 File (#664.1) is written to and
 read during the creation, revision, and display of an Orthotics Lab Work Order
 (OWL).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: SEP 10, 2019

NUMBER: 6535                            IA #: 6535
  FILE NUMBER: 664.2                    GLOBAL ROOT: RMPR(664.2,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROSTHETIC WORK ORDER FILE ACCESS
  ID: RMPR(664.2,
GLOBAL REFERENCE: RMPR(664.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: WORK ORDER NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: APPLIANCE/REPAIR
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.5                       FIELD NAME: STATION
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.7                       FIELD NAME: JOB NUMBER
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.8                       FIELD NAME: DATE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: EST. SHIPPING CHARGE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: ACTUAL SHIPPING CHARGE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: REFERRAL STATION
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7                         FIELD NAME: WORK FOR OTHER STATION
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: DATE COMPLETED
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: COMPLETED BY
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11                        FIELD NAME: CHECKED BY
  LOCATION: 0;12                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664.2,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: MATERIALS USED
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: QTY
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: MATERIALS COST
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: VA or COMMERCIAL SOURCE
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: INVENTORY POINT
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: VENDOR
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: UNIT OF ISSUE
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7                         FIELD NAME: SERIAL NBR
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13                        FIELD NAME: PURCHASE STATUS
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: REFERENCE
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11                        FIELD NAME: PURCHASE FORM
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12                        FIELD NAME: APPLIANCE/REPAIR
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: 2529-3
  LOCATION: 0;13                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(664.2,D0,1,D1,3,D2,0)
FIELD NUMBER: .01                       FIELD NAME: REMARKS
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(664.2,'C'
 GLOBAL DESCRIPTION:   File 664.2 'C' cross reference  Used for lookup to
 update file 
                                 660 with materials costs 
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT)
 creates, updates, deletes, and displays records in the PROSTHETIC WORK ORDER
 File (#664.2) during Orthotics Lab Work Order (OWL) functionality.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: SEP 10, 2019

NUMBER: 6536                            IA #: 6536
  FILE NUMBER: 664.3                    GLOBAL ROOT: RMPR(664.3,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PROSTHETIC LAB HOURS DATE FILE ACCESS
  ID: RMPR(664.3,
GLOBAL REFERENCE: RMPR(664.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: APPLIANCE/REPAIR
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: STATION
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(664.3,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: TECHNICIAN
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: HOURS
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: RATE PER HOUR
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(664.3,D0,1,'B'
 GLOBAL DESCRIPTION:   File 664.3/664.33 'B' cross reference  Used to look up
 by TECHNICIAN 
GLOBAL REFERENCE: RMPR(664.3,'B'
 GLOBAL DESCRIPTION:   File 664.3 'B' cross reference  Used to look up by DATE 
GLOBAL REFERENCE: RMPR(664.3,'C'
 GLOBAL DESCRIPTION:   File 664.3 'C' cross reference  Used to look up by
 APPLIANCE/REPAIR 
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT)
 accesses the PROSTHETIC LAB HOURS DATE File (#664.3) during the creation,
 revision, and display of an Orthotics Lab Work Order (OWL).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: SEP 10, 2019

NUMBER: 6537                            IA #: 6537
  FILE NUMBER: 665                      GLOBAL ROOT: RMPR(665,
  DATE CREATED: OCT 17, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROSTHETICS PATIENT FILE ACCESS
  ID: RMPR(665,
GLOBAL REFERENCE: RMPR(665,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2                         FIELD NAME: STATION
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PROSTHETIC DISABILITY CODE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: DATE CODE ADDED
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: SERVICE/NON-SERVICE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: ELIGIBILITY CATEGORY
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: SPECIAL LEGISLATION
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: ADD/DELETE
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: AMIS DATE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: ENTERED BY
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: REMOVE CODE FLAG
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: DATE CODE DELETED
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,1,'B'
 GLOBAL DESCRIPTION:   File 665 / 665.01 'B' cross reference  Used to look up
 Pros 
                                        Disability Codes assigned 
                                        to the PATIENT 
GLOBAL REFERENCE: RMPR(665,D0,3,D1,0)
FIELD NUMBER: .01                       FIELD NAME: AUTOMOBILE ACQUISITION DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: VIN
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: YEAR
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DESCRIPTION
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: AMIS LINE ITEM
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.1                       FIELD NAME: MAKE AND MODEL
  LOCATION: 0;6                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: OTHER DATA
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,5,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PSC ISSUE CARD DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DETAILED DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: SERIAL NUMBER
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PSC CATEGORY
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ITEM
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: CANCELLED
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: REMARKS
  LOCATION: 0;7                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,6,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DATE OF CLOTHING ALLOWANCE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ELIGIBLE/NOT ELIGIBLE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: STATIC/NON-STATIC
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: CLOTHING ALLOWANCE EXAM
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: DATE OF EXAM
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: EXAMINER
  LOCATION: 0;6                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,6,D1,1)
FIELD NUMBER: 3                         FIELD NAME: CLOTHING ALLOWANCE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,8,D1,0)
FIELD NUMBER: 30                        FIELD NAME: CRITICAL COMMENTS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,10)
FIELD NUMBER: 20                        FIELD NAME: HEIGHT (INCHES)
  LOCATION: 10;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 21                        FIELD NAME: WEIGHT (POUNDS)
  LOCATION: 10;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 22                        FIELD NAME: EYE COLOR
  LOCATION: 10;3                        ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: HAIR COLOR
  LOCATION: 10;4                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,'RMPOA')
FIELD NUMBER: 19.1                      FIELD NAME: HOME OXYGEN ELIGIBILITY
  LOCATION: RMPOA;1                     ACCESS: Read w/Fileman
FIELD NUMBER: 19.2                      FIELD NAME: HOME OXYGEN ACTIVATION DATE
  LOCATION: RMPOA;2                     ACCESS: Read w/Fileman
FIELD NUMBER: 19.5
  FIELD NAME: HOME OXYGEN INACTIVATION DATE
  LOCATION: RMPOA;3                     ACCESS: Read w/Fileman
FIELD NUMBER: 19.6
  FIELD NAME: HOME OXYGEN INACTIVAT. REASON
  LOCATION: RMPOA;4                     ACCESS: Read w/Fileman
FIELD NUMBER: 19.11                     FIELD NAME: SPECIAL NSC/OP CATEGORY
  LOCATION: RMPOA;5                     ACCESS: Read w/Fileman
FIELD NUMBER: 19.7                      FIELD NAME: HOME OXYGEN INACTIVATED BY
  LOCATION: RMPOA;6                     ACCESS: Read w/Fileman
FIELD NUMBER: 19.12
  FIELD NAME: HOME OXYGEN CONTRACT LOCATION 
  LOCATION: RMPOA;7                     ACCESS: Read w/Fileman
FIELD NUMBER: 19.13
  FIELD NAME: HOME OXYGEN LETTER TO BE SENT
  LOCATION: RMPOA;8                     ACCESS: Read w/Fileman
FIELD NUMBER: 19.14                     FIELD NAME: HO LETTER 1 DATE
  LOCATION: RMPOA;9                     ACCESS: Read w/Fileman
FIELD NUMBER: 19.15                     FIELD NAME: HO LETTER 1 CODE
  LOCATION: RMPOA;10                    ACCESS: Read w/Fileman
FIELD NUMBER: 19.16                     FIELD NAME: HO LETTER 2 DATE
  LOCATION: RMPOA;11                    ACCESS: Read w/Fileman
FIELD NUMBER: 19.17                     FIELD NAME: HO LETTER 2 CODE
  LOCATION: RMPOA;12                    ACCESS: Read w/Fileman
FIELD NUMBER: 19.18                     FIELD NAME: HO LETTER 3 DATE
  LOCATION: RMPOA;13                    ACCESS: Read w/Fileman
FIELD NUMBER: 19.19                     FIELD NAME: HO LETTER 3 CODE
  LOCATION: RMPOA;14                    ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,'RMPOB',D1,0)
FIELD NUMBER: .01                       FIELD NAME: DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: EXPIRATION DATE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: A&B LETTERS SENT
  LOCATION: 0;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,'RMPOB',D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,'RMPOB',D1,BA1)
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
  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.4                      FIELD NAME: PRIMARY ENVIRONMENTAL CONT.
  LOCATION: BA1;5                       ACCESS: Read w/Fileman
FIELD NUMBER: 30.5                      FIELD NAME: PRIMARY MST
  LOCATION: BA1;6                       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
GLOBAL REFERENCE: RMPR(665,D0,'RMPOB',D1,BA2)
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
GLOBAL REFERENCE: RMPR(665,D0,'RMPOB',D1,BA3)
FIELD NUMBER: 32
  FIELD NAME: SECONDARY ICD DIAGNOSIS CODE 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 ENVIRONMENTAL 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: 33.7                      FIELD NAME: SECONDARY COMBAT VET 2
  LOCATION: BA3;8                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,'RMPOB',D1,BA4)
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 ENVIRONMENTAL 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(665,D0,'RMPOB',D1,PFSS)
FIELD NUMBER: 100                       FIELD NAME: PFSS NEW PRESCRIPTION FLAG
  LOCATION: PFSS;1                      ACCESS: Read w/Fileman
FIELD NUMBER: 101                       FIELD NAME: REQUESTOR
  LOCATION: PFSS;2                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,'RMPOC',D1,0)
FIELD NUMBER: .01                       FIELD NAME: ITEM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: VENDOR
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: QUANTITY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: UNIT OF ISSUE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: UNIT COST
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: FUND CONTROL POINT
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: HCPCS CODE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: ICD9 CODE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: REMARKS
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: ITEM TYPE
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: PRIMARY ITEM
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: HOME OXYGEN RENTAL FLAG
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: HOME OXYGEN CONSERVING FLAG
  LOCATION: 0;13                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(665,D0,'RMPOC',D1,PFSS)
FIELD NUMBER: 100                       FIELD NAME: PFSS ACCOUNT FLAG
  LOCATION: PFSS;1                      ACCESS: Read w/Fileman
FIELD NUMBER: 101                       FIELD NAME: PFSS ACCOUNT REFERENCE
  LOCATION: PFSS;2                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(665,'B'
 GLOBAL DESCRIPTION:   File 665 'B' cross reference  Used to determine if a
 patient 
                               is a prosthetic patient 
 GENERAL DESCRIPTION:   In the Advanced Prosthetics Acquisition Tool (APAT),
 the PROSTHETICS PATIENT File (#665) is written to during the addition of 
 Prosthetic patients and when Prosthetic disability codes are 
 added/edited/deleted/displayed.  The file is read during the location of 
 prosthetic patients, the creation of GIP Stock Issues, 2319 processing 
 (including critical comments, patient demographics, appliance transactions 
 (including HISA and Home Oxygen)), the creation of Orthotic Lab Work Orders
 (OWLs), and during suspense processing.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 05/02/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires access to the
 Prosthetics Patient file 665 for eyeglass ordering.  
  DATE ACTIVATED: JUL 30, 2020

NUMBER: 6538                            IA #: 6538
  FILE NUMBER: 665.2                    GLOBAL ROOT: RMPR(665.2,
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROS LETTER FILE ACCESS
  ID: RMPR(665.2,
GLOBAL REFERENCE: RMPR(665.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DENIAL FLAG
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: ADP FL 10-90 FLAG
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   In the Advanced Prosthetics Acquisition Tool (APAT),
 the PROS LETTER File (#665.2) is read during the Create RFQ (Request for
 Quote/10-90) process to validate and display Pros Letter Types.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   This is a retro-active ICR activation, for the ICR
 which has been in use since release of patch DSSO*2*0 in 2019. A Prosthetics
 custodian developer is not available to approve, so ICR Team activated due to 
 reasonableness given the role of APAT to interface with Prosthetics in the
 enterprise.  
  DATE ACTIVATED: APR 13, 2023

NUMBER: 6539                            IA #: 6539
  FILE NUMBER: 665.4                    GLOBAL ROOT: RMPR(665.4,
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PROS LETTER TRANSACTIONS FILE ACCESS
  ID: RMPR(665.4,
GLOBAL REFERENCE: RMPR(665.4,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: LETTER TYPE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: PRINTED DATE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: EMPLOYEE
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(665.4,D0,2)
FIELD NUMBER: 7                         FIELD NAME: VENDOR
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: RMPR(665.4,D0,3,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ITEM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
GLOBAL REFERENCE: RMPR(665.4,D0,4)
FIELD NUMBER: 9                         FIELD NAME: SIGNED BY
  LOCATION: 4;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SIGNER'S TITLE
  LOCATION: 4;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(665.4,D0,5)
FIELD NUMBER: 11                        FIELD NAME: NON-AMIS GENERATION DATE
  LOCATION: 5;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(665.4,'AH')
 GLOBAL DESCRIPTION:   'AH' cross reference - used to look up AMIS denials by
 PRINTED DATE 
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT) writes
 to the PROS LETTER TRANSACTIONS File (#665.4) when creating a Request for
 Quote (RFQ, 10-90), and it is read when displaying an RFQ/10-90 or any other
 Prosthetic Letter.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   This is a retro-active ICR activation, for the ICR
 which has been in use since release of patch DSSO*2*0 in 2019. A Prosthetics
 custodian developer is not available to approve, so ICR Team activated due to 
 reasonableness given the role of APAT to interface with Prosthetics in the
 enterprise.  
  
 Effective 4/13/23, with patch DSSO*2.0*3 APAT has access to fields SIGNED BY
 (#9), SIGNER'S TITLE (#10), NON-AMIS GENERATION DATE (#11) that are stored
 when a Prosthetic Letter is created in the PROS LETTER TRANSACTIONS (#665.4)
 file.  
  DATE ACTIVATED: APR 14, 2023

NUMBER: 6540                            IA #: 6540
  FILE NUMBER: 668                      GLOBAL ROOT: RMPR(668,
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROSTHETIC SUSPENSE FILE ACCESS
  ID: RMPR(668,
GLOBAL REFERENCE: RMPR(668,D0,0)
FIELD NUMBER: .01                       FIELD NAME: SUSPENSE DATE
  LOCATION: 0;1
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: VETERAN
  LOCATION: 0;2
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: STATION
  LOCATION: 0;7
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: COMPLETION DATE
  LOCATION: 0;5
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: COMPLETED BY
  LOCATION: 0;6                         ACCESS: Write w/Fileman
FIELD NUMBER: 8                         FIELD NAME: SUSPENDED BY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: TYPE OF REQUEST
  LOCATION: 0;8
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: INITIAL ACTION DATE
  LOCATION: 0;9
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 13                        FIELD NAME: REQUESTOR
  LOCATION: 0;11
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: STATUS
  LOCATION: 0;10
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 16                        FIELD NAME: INITIAL ACTION BY
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17                        FIELD NAME: CANCELLED BY
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20                        FIELD NAME: CONSULT
  LOCATION: 0;15
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 22                        FIELD NAME: DATE RX WRITTEN
  LOCATION: 0;16
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ACTION DATE
  LOCATION: 0;1
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,1,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: ACTION NOTE
  LOCATION: 0;1
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION OF ITEM/SERVICES
  LOCATION: 0;1
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,3,D1,0)
FIELD NUMBER: .01                       FIELD NAME: INITIAL ACTION NOTE
  LOCATION: 0;1
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: COMPLETION DATE
  LOCATION: 0;1
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,5)
FIELD NUMBER: 18                        FIELD NAME: CANCEL DATE
  LOCATION: 5;1
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,7)
FIELD NUMBER: 15                        FIELD NAME: OIF/OEF
  LOCATION: 7;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,8)
FIELD NUMBER: 2.1                       FIELD NAME: REQUESTING FACILITY
  LOCATION: 8;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.5                       FIELD NAME: PROVISIONAL DIAGNOSIS
  LOCATION: 8;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.6                       FIELD NAME: ICD9
  LOCATION: 8;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.3                       FIELD NAME: URGENCY
  LOCATION: 8;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: CONSULT REQUEST SERVICE
  LOCATION: 8;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 24                        FIELD NAME: FORWARDED BY
  LOCATION: 8;7                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,9,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CANCEL NOTE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,10,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT 2319
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,11,D1,0)
FIELD NUMBER: .01                       FIELD NAME: AMIS GROUPER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,'BA1')
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
  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.4                      FIELD NAME: PRIMARY ENVIRONMENTAL CONT.
  LOCATION: 'BA1';5                     ACCESS: Read w/Fileman
FIELD NUMBER: 30.5                      FIELD NAME: PRIMARY MST
  LOCATION: 'BA1';6                     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
GLOBAL REFERENCE: RMPR(668,D0,'BA2')
FIELD NUMBER: 31                        FIELD NAME: SECONDARY ICD DIAGNOSIS 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 RADATION 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 ENVIRON. 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
GLOBAL REFERENCE: RMPR(668,D0,'BA3')
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 ENVIRON. 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
GLOBAL REFERENCE: RMPR(668,D0,'BA4')
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.5                      FIELD NAME: SECONDARY MST 3
  LOCATION: 'BA4';6                     ACCESS: Read w/Fileman
FIELD NUMBER: 33.4                      FIELD NAME: SECONDARY ENVIRON. CONT. 3
  LOCATION: 'BA4';5                     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(668,D0,'IFC1')
FIELD NUMBER: 27                        FIELD NAME: ORDERING PROVIDER
  LOCATION: 'IFC1';3                    ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(668,'B'
 GLOBAL DESCRIPTION:   File 668 'B' cross reference  Used to look up by
 SUSPENSE DATE 
GLOBAL REFERENCE: RMPR(668,'C'
 GLOBAL DESCRIPTION:   File 668 'C' cross reference  Used to look up by VETERAN 
GLOBAL REFERENCE: RMPR(668,'CD'
 GLOBAL DESCRIPTION:   File 668 'CD' cross reference  Used to look up by
 COMPLETION DATE 
GLOBAL REFERENCE: RMPR(668,'E'
 GLOBAL DESCRIPTION:   File 668 'E' cross reference  Used to look up by STATUS 
GLOBAL REFERENCE: RMPR(668,'F'
 GLOBAL DESCRIPTION:   File 668 'F' cross reference  Used to look up by PATIENT
 2319 
GLOBAL REFERENCE: RMPR(668,'L'
 GLOBAL DESCRIPTION:   File 668 'L' cross reference  Used to look up by STATUS 
                               (last 2 of patient SSN, 
                               Create Date with no time, 
                               and STATUS) 
GLOBAL REFERENCE: RMPR(668,'L1'
 GLOBAL DESCRIPTION:   File 668 'L1' cross reference  Used to look up by STATUS 
                                (last 2 of patient SSN, 
                                STATUS, and IEN for  
                                Delayed Order Report) 
GLOBAL REFERENCE: RMPR(668,'D'
 GLOBAL DESCRIPTION:   File 668 'D' cross reference  Used to look up by CONSULT 
 GENERAL DESCRIPTION:   The PROSTHETIC SUSPENSE (#668) File is read and written
 to in order to create cloned suspense items or to add initial action, other, 
 cancellation, and completion notes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   This is a retro-active ICR activation, for the ICR
 which has been in use since release of patch DSSO*2*0 in 2019. A Prosthetics
 custodian developer is not available to approve, so ICR Team activated due to 
 reasonableness given the role of APAT to interface with Prosthetics in the
 enterprise.  
  
 Effective 4/13/23, with patch DSSO*2.0*3, type of access for the STATUS (#14)
 field was changed from "Write w/Fileman" to "Both R/W w/Fileman".  
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 5/7/25, effective with PROSTHETICS VISION 4 SIGHT
 II patch RMPV*1*1, the Prosthetics package requires direct global read access
 and Fileman read/write access to the PROSTHETIC SUSPENSE FILE (#668) and
 adding "D" cross reference, and Direct Global Read to Field 14.  
  DATE ACTIVATED: APR 14, 2023

NUMBER: 6541                            IA #: 6541
  FILE NUMBER: 669.1                    GLOBAL ROOT: RMPR(669.1,
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROSTHETIC LAB W.O. # FILE ACCESS
  ID: RMPR(669.1,
GLOBAL REFERENCE: RMPR(669.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: LAST NUMBER USED
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(669.1,'B')
 GLOBAL DESCRIPTION:   'B' cross reference - Used to look up by NAME 
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT)
 accesses the PROSTHETIC LAB W.O. # File (#669.1) to determine the last work
 order number used. When creating a work order, the LAST NUMBER USED field is
 incremented for the STATION, YEAR, and QUARTER.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   This is a retro-active ICR activation, for the ICR
 which has been in use since in 2016. A Prosthetics custodian developer is not
 available to approve, so ICR Team activated due to reasonableness given the
 role of APAT to interface with Prosthetics in the enterprise.  
  
 Effective 4/13/23, with patch DSSO*2.0*3, type of access for the NAME (#.01)
 field was changed from "Read w/Fileman" to "Both R/W w/Fileman".  
  DATE ACTIVATED: APR 14, 2023

NUMBER: 6542                            IA #: 6542
  FILE NUMBER: 669.9                    GLOBAL ROOT: RMPR(669.9,
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PROSTHETIC SITE PARAMETERS FILE ACCESS
  ID: RMPR(669.9,
GLOBAL REFERENCE: RMPR(669.9,D0,0)
FIELD NUMBER: .01                       FIELD NAME: SITE NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: STATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: AUTOMATED INVENTORY (GIP)
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PHONE NUMBER
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: PURCHASING DEVICE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: LAB
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: GROUPER COUNTER
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 32                        FIELD NAME: ORTHOTICS LAB ACTIVATED?
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 33                        FIELD NAME: RESTORATION LAB ACTIVATED?
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 34                        FIELD NAME: ROUTING NUMBER
  LOCATION: 0;13                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PROSTHETICS CLINIC
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,2)
FIELD NUMBER: 8.5                       FIELD NAME: SIGNATURE BLOCK TITLE
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: STREET ADD1
  LOCATION: 2;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: CITY
  LOCATION: 2;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: STATE
  LOCATION: 2;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: ZIP CODE
  LOCATION: 2;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: CHIEF SIG BLOCK
  LOCATION: 2;6                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,3)
FIELD NUMBER: 12                        FIELD NAME: DVN IP ADDRESS
  LOCATION: 3;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: DVN FILE DIRECTORY
  LOCATION: 3;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: DVN SFTP USERNAME
  LOCATION: 3;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,4)
FIELD NUMBER: 1.1                       FIELD NAME: IFCAP SITE
  LOCATION: 4;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: COMMON NUMBERING SERIES
  LOCATION: 4;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,5,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PURCHASING AGENT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: START RANGE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: STOP RANGE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PHONE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PRINT NAME
  LOCATION: 0;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,6)
FIELD NUMBER: 7.1                       FIELD NAME: MANAGER COMMENT
  LOCATION: 6;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,'DEV')
FIELD NUMBER: 27                        FIELD NAME: ORTHOTIC LAB DEVICE
  LOCATION: 'DEV';2                     ACCESS: Read w/Fileman
FIELD NUMBER: 28                        FIELD NAME: RESTORATION CLINIC DEVICE
  LOCATION: 'DEV';3                     ACCESS: Read w/Fileman
FIELD NUMBER: 29                        FIELD NAME: SHOE LAST CLINIC DEVICE
  LOCATION: 'DEV';4                     ACCESS: Read w/Fileman
FIELD NUMBER: 30
  FIELD NAME: WHEELCHAIR REPAIR SHOP DEVICE
  LOCATION: 'DEV';5                     ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,'INV')
FIELD NUMBER: 35                        FIELD NAME: INVENTORY DEVICE
  LOCATION: 'INV';1                     ACCESS: Read w/Fileman
FIELD NUMBER: 40                        FIELD NAME: VISN
  LOCATION: 'INV';2                     ACCESS: Read w/Fileman
FIELD NUMBER: 37                        FIELD NAME: NOTIFICATION DATE
  LOCATION: 'INV';3                     ACCESS: Read w/Fileman
FIELD NUMBER: 38                        FIELD NAME: HQ MAIL ADDRESS
  LOCATION: 'INV';4                     ACCESS: Read w/Fileman
FIELD NUMBER: 39                        FIELD NAME: HQ REPORT DATE
  LOCATION: 'INV';5                     ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,'PCE')
FIELD NUMBER: 50                        FIELD NAME: PCE START DATE
  LOCATION: 'PCE';1                     ACCESS: Read w/Fileman
FIELD NUMBER: 51                        FIELD NAME: PCE END DATE
  LOCATION: 'PCE';2                     ACCESS: Read w/Fileman
FIELD NUMBER: 52                        FIELD NAME: PCE HOSPITAL LOCATION
  LOCATION: 'PCE';3                     ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,'RMPOFCP',D1,0)
FIELD NUMBER: .01                       FIELD NAME: FUND CONTROL POINT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PSAS?
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: PURCHASE CARD NUMBER
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,'RMPOLET',D1,0)
FIELD NUMBER: .01                       FIELD NAME: HOME OXYGEN LETTER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: LETTER CODE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DAYS TO PRESCRIPTION EXPIRY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: AUTOGENERATE LETTER
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PRINT LETTER HEADER
  LOCATION: 0;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,'RMPORXN',D1,0)
FIELD NUMBER: .01                       FIELD NAME: PRESCRIPTION SEQUENCE NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DEFAULT DAYS TO EXPIRATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,'RMPOVDR',D1,0)
FIELD NUMBER: .01                       FIELD NAME: HOME OXYGEN VENDORS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,'RMPOXBAT1',D1,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,'RMPOXBAT2',D1,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,D0,'RMPOXBAT3',D1,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(669.9,'B')
 GLOBAL DESCRIPTION:   "B" cross reference - Used to look up by SITE NAME 
GLOBAL REFERENCE: RMPR(669.9,'C')
 GLOBAL DESCRIPTION:   "C" cross reference - Used to look up by STATION 
 GENERAL DESCRIPTION:   Above PAR and the Advanced Prosthetics Acquisition Tool
 (APAT) accesses the PROSTHETIC SITE PARAMETERS File (#669.9) to obtain details
 about a given Prosthetics site.  This file is written to in order to maintain
 the GROUPER COUNTER (#11).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/23/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires direct global read
 to the PROSTHETIC SITE PARAMETERS FILE 669.9 
  DATE ACTIVATED: JUL 30, 2020

NUMBER: 6543                            IA #: 6543
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: Routine
  ROUTINE: RMPR9P23                     NAME: DISPLAY PRIVACY STATEMENT
  ID: RMPR9P23
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call routine RMPR9P23 in order to
 display the current privacy statement as the last page of a Prosthetics
 purchase card order.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: PRI
 COMPONENT DESCRIPTION:   Entry point for printing Privacy Act (GUI Windows)
 for 10-2421, 10-55, and 2419 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL

NUMBER: 6544                            IA #: 6544
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RMPRP23
  NAME: RETURN PRIVACY STATEMENT        ID: RMPRP23
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call routine RMPRP23 in order to return
 the current privacy statement for display as the last page of Prosthetics
 purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: PRI
 COMPONENT DESCRIPTION:   Entry Point for printing Privacy Act for 10-2421,
 10-55, and 2419 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: FEB 05, 2018

NUMBER: 6545                            IA #: 6545
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RMPRED5
  NAME: CHECK CPT MODIFIER FOR STOCK ISSUE
  ID: RMPRED5
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call CHK^RMPRED5 to check for Source
 and Type of Transaction changes to the CPT Modifier when creating a Generic 
 Inventory Program Stock Issue.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: CHK
 COMPONENT DESCRIPTION:   Check for Source and Type of Transaction changes to
 the CPT Modifier 
VARIABLES: $P(R1(0),U,14)               TYPE: Used
 VARIABLES DESCRIPTION:   Source from the Record of Pros Appliance/Repair for
 the specified Stock Issue 
VARIABLES: $P(R1(1),U,6)                TYPE: Used
 VARIABLES DESCRIPTION:   CPT MODIFIER from the Record of Pros Appliance/Repair
 for the specified Stock Issue 
VARIABLES: RMHCPC                       TYPE: Input
 VARIABLES DESCRIPTION:   Prosthetic HCPCS IEN associated to the specified
 Stock Issue 
VARIABLES: $P(R1(0),U,4)                TYPE: Used
 VARIABLES DESCRIPTION:   New Type of Transaction 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/17/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires permission to call
 RMPRED5 via ICR 6545.  
  DATE ACTIVATED: NOV 14, 2017

NUMBER: 6546                            IA #: 6546
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRC0D
  NAME: FIRST DATE OF QUARTER           ID: PRC0D
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRC0D. This
 extrinsic function returns the first date of the specified quarter.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: $$QTRDATE(A,B)
 COMPONENT DESCRIPTION:   This extrinsic function returns the first date of the
 specified quarter in the format:  
   ^-piece 1 = Fiscal Year (4 digits) 
   ^-piece 2 = Fiscal Quarter (1 digit) 
   ^-piece 3 = Calendar Year (4 digits) 
   ^-piece 4 = Calendar Month (2 digits) 
   ^-piece 5 = Calendar Day (2 digits) 
   ^-piece 6 = Week Day # 
   ^-piece 7 = FileMan Date 
   ^-piece 8 = $Horolog Date 
   ^-piece 9 = Fiscal Month (2 digits) 
VARIABLES: A                            TYPE: Input
 VARIABLES DESCRIPTION:   The fiscal year 
VARIABLES: B                            TYPE: Input
 VARIABLES DESCRIPTION:   The quarter 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6547                            IA #: 6547
  FILE NUMBER: 445                      GLOBAL ROOT: PRCP(445,
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: GENERIC INVENTORY FILE ACCESS
  ID: PRCP(445,
GLOBAL REFERENCE: PRCP(445,D0,0)
FIELD NUMBER: .01                       FIELD NAME: INVENTORY POINT
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   
                                                   Global r 
FIELD NUMBER: .5                        FIELD NAME: KEEP PERPETUAL INVENTORY?
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .7                        FIELD NAME: TYPE OF INVENTORY POINT
  LOCATION: 0;3
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 9
  FIELD NAME: REGULAR WHSE. ISSUES SCHEDULE
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .8                        FIELD NAME: ABBREVIATED NAME
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .6                        FIELD NAME: KEEP DETAILED TRX. HISTORY?
  LOCATION: 0;6
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .9                        FIELD NAME: COST CENTER
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: DEPARTMENT NUMBER
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7
  FIELD NAME: PRINT STOCK AT CRITICAL LEVEL?
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.5                       FIELD NAME: ISSUE BOOK SORT
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 10
  FIELD NAME: REGULAR WHSE. ISSUES DUE DATE
  LOCATION: 0;12
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 12
  FIELD NAME: MOS INACTIVE BEFORE ITEM DEL.
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7.5                       FIELD NAME: LAST PURGE USAGE
  LOCATION: 0;14
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: PRIMARY UPDATED BY WAREHOUSE
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7.6                       FIELD NAME: LAST PURGE RECEIPTS
  LOCATION: 0;17
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 7.7                       FIELD NAME: LAST PURGE TRANS REGISTER
  LOCATION: 0;18
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 7.8                       FIELD NAME: LAST PURGE DISTRIBUTION
  LOCATION: 0;19
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 15                        FIELD NAME: SPECIAL INVENTORY POINT TYPE
  LOCATION: 0;20                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7.9                       FIELD NAME: AUTOMATIC PURGE
  LOCATION: 0;21                        ACCESS: Read w/Fileman
FIELD NUMBER: 7.4                       FIELD NAME: LAST OPEN BALANCES SET
  LOCATION: 0;22
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ITEM NO.
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: CANCEL/BACKORDER
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.6                       FIELD NAME: DATE LAST RECEIVED
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 10.3                      FIELD NAME: OPTIONAL REORDER POINT
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: UNIT OF ISSUE
  LOCATION: 0;5
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: MAIN STORAGE LOCATION
  LOCATION: 0;6
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 7                         FIELD NAME: QTY.ON HAND (UNIT OF ISSUE)
  LOCATION: 0;7
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: NORMAL STOCK LEVEL (U OF I)
  LOCATION: 0;9
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: STANDARD REORDER POINT
  LOCATION: 0;10
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 11                        FIELD NAME: EMERGENCY STOCK LEVEL
  LOCATION: 0;11
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .4
  FIELD NAME: MANDATORY OR REQUESTED SOURCE
  LOCATION: 0;12
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 14.3                      FIELD NAME: DO NOT BACK-ORDER INDICATOR
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.5                       FIELD NAME: UNIT OF ISSUE PACKAGE MULT.
  LOCATION: 0;14
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 4.7                       FIELD NAME: LAST COST (UNIT OF ISSUE)
  LOCATION: 0;15                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16.5                      FIELD NAME: MINIMUM ISSUE QTY.
  LOCATION: 0;17                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 14.4                      FIELD NAME: DO NOT SUBSTITUTE INDICATOR
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7.5                       FIELD NAME: QTY NON-ISSUABLE (U/I)
  LOCATION: 0;19                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .5                        FIELD NAME: GROUP CATEGORY CODE
  LOCATION: 0;21
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 4.8                       FIELD NAME: AVERAGE COST (UNIT OF ISSUE)
  LOCATION: 0;22                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9.5                       FIELD NAME: TEMPORARY STOCK LEVEL
  LOCATION: 0;23                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9.6
  FIELD NAME: DATE TO DELETE TEMPORARY LEVEL
  LOCATION: 0;24                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16
  FIELD NAME: ISSUE MULTIPLE (UNIT OF ISSUE)
  LOCATION: 0;25                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17                        FIELD NAME: DELETE ITEM WHEN INVENTORY 0
  LOCATION: 0;26                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.81                      FIELD NAME: TOTAL INVENTORY VALUE
  LOCATION: 0;27                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 50                        FIELD NAME: DISPENSING UNIT
  LOCATION: 0;28                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 51                        FIELD NAME: DISPENSING UNIT CONV FACTOR
  LOCATION: 0;29                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .8                        FIELD NAME: ON-DEMAND
  LOCATION: 0;30
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,1,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: ADDITIONAL STORAGE LOCATION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,1,D1,2,D2,0)
FIELD NUMBER: .01                       FIELD NAME: MONTH/YEAR USED/ISSUED
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: QTY.USED/ISSUED (U OF ISSUE)
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TOTAL COST USED/ISSUED
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,1,D1,3,D2,0)
FIELD NUMBER: .01                       FIELD NAME: DATE RECEIVED
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: QTY.RECEIVED (UNIT OF ISSUE)
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,1,D1,4,D2,0)
FIELD NUMBER: .01                       FIELD NAME: SUBSTITUTE ITEM(S)
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,1,D1,5,D2,0)
FIELD NUMBER: .01                       FIELD NAME: PROCUREMENT SOURCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: UNIT OF RECEIPT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2
  FIELD NAME: UNIT OF RECEIPT PACKAGE MULT.
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: UNIT CONVERSION FACTOR
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,1,D1,6)
FIELD NUMBER: .7                        FIELD NAME: ITEM DESCRIPTION
  LOCATION: 6;1
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,1,D1,7,D2,0)
FIELD NUMBER: .01                       FIELD NAME: TRANSACTION NO.
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: QTY.ORDERED UNIT OF ISSUE
  LOCATION: 0;2
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: UNIT OF RECEIPT
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3
  FIELD NAME: UNIT OF RECEIPT PACKAGE MULT.
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: UNIT CONVERSION FACTOR
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,1,D1,8,D2,0)
FIELD NUMBER: .01
  FIELD NAME: CASE CART/INSTRUMENT KIT ITEM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: QTY NEEDED FOR ONE CC/IK
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,1,D1,9)
FIELD NUMBER: .61                       FIELD NAME: SUPPLY STATION QUANTITY
  LOCATION: 9;1
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .62                       FIELD NAME: QTY FROM SS LAST UPDATED
  LOCATION: 9;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,1,D1,10,D2,0)
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME OF CHANGE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ON-DEMAND CHANGED BY
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: REASON FOR CHANGE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: NEW ON-DEMAND SETTING
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,1,D1,'DUE')
FIELD NUMBER: 8.1                       FIELD NAME: DUE-IN (IN U/I)
  LOCATION: 'DUE';1
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 8.6                       FIELD NAME: DUE-OUT (IN U/I)
  LOCATION: 'DUE';2                     ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DISTRIBUTION POINT
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,3,D1,0)
FIELD NUMBER: .01                       FIELD NAME: MIS COSTING SECTION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: % OF COSTS TO BE APPLIED
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: INVENTORY USER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,6)
FIELD NUMBER: 23                        FIELD NAME: SS QUANTITY LAST TRANSMITTED
  LOCATION: 6;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,7)
FIELD NUMBER: 24
  FIELD NAME: QUANTITY REPLACEMENT REQUESTOR
  LOCATION: 7;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 25
  FIELD NAME: QUANTITY REPLACEMENT REQUESTED
  LOCATION: 7;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,8,D1,0)
FIELD NUMBER: .01                       FIELD NAME: QUANTITY REPLACEMENT USER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,9,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ON-DEMAND USER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,'DEV')
FIELD NUMBER: 16                        FIELD NAME: PICKING TICKET PRINTER
  LOCATION: 'DEV';1                     ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,'SEC')
FIELD NUMBER: 19
  FIELD NAME: PRE-CONVERSION HEADER (NO EDITS)
  LOCATION: 'SEC';1                     ACCESS: Both R/W w/Fileman
FIELD NUMBER: 19.5                      FIELD NAME: CONVERTED BY
  LOCATION: 'SEC';2                     ACCESS: Both R/W w/Fileman
FIELD NUMBER: 19.6                      FIELD NAME: CONVERSION DATE
  LOCATION: 'SEC';3                     ACCESS: Both R/W w/Fileman
FIELD NUMBER: 19.7                      FIELD NAME: PRE-CONVERSION STOCKED BY
  LOCATION: 'SEC';4                     ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,'SECITM',D1,0)
FIELD NUMBER: .01
  FIELD NAME: PRE-CONVERSION ITEM (NO EDITS)
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,'SECITM',D1,5,D2,0)
FIELD NUMBER: .01
  FIELD NAME: PRE-CONVERSION SOURCES (NO EDITS)
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,D0,'SECMIS',D1,0)
FIELD NUMBER: .01
  FIELD NAME: PRE-CONVERSION MIS (NO EDITS)
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445,'AB'
 GLOBAL DESCRIPTION:   'AB' cross reference - used to look up by DISTRIBUTION
 POINT 
GLOBAL REFERENCE: PRCP(445,'AC'
 GLOBAL DESCRIPTION:   'AC' cross reference - used to look up by INV POINT TYPE 
GLOBAL REFERENCE: PRCP(445,'AD'
 GLOBAL DESCRIPTION:   'AD' cross reference - used to look up by INVENTORY USER 
GLOBAL REFERENCE: PRCP(445,'AE'
 GLOBAL DESCRIPTION:   'AE' cross reference - used to look up by ITEM NO 
GLOBAL REFERENCE: PRCP(445,'B'
 GLOBAL DESCRIPTION:   'B' cross reference - used to look up by INVENTORY POINT 
GLOBAL REFERENCE: PRCP(445,D0,5)
FIELD NUMBER: 22                        FIELD NAME: SS PROVIDER
  LOCATION: 5;1
  ACCESS: Direct Global Read & R/W w/Fileman
 GENERAL DESCRIPTION:   Above PAR and the Advanced Prosthetics Acquisition Tool
 (APAT) request permission to read and write to the GENERIC INVENTORY FILE #445 
 to display and edit both Distribution Points and Items within a Distribution
 Point within the Inventory function.  Inventory levels are also adjusted by
 the APAT stock issue and edit 2319 functionality.  Above PAR will address the
 conversion of a secondary to a primary in a future version.  
  
 Above PAR Ad-Hoc Reporting includes the GENERIC INVENTORY FILE #445.  Ad-Hoc
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: MAR 04, 2022

NUMBER: 6548                            IA #: 6548
  FILE NUMBER: 445.2                    GLOBAL ROOT: PRCP(445.2,
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INVENTORY TRANSACTION FILE ACCESS
  ID: PRCP(445.2,
GLOBAL REFERENCE: PRCP(445.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: INVENTORY POINT
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TRANSACTION ID
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DATE OF TRANSACTION
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: TYPE OF TRANSACTION
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: ITEM NO.
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: PACKAGING UNIT
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: QUANTITY
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7                         FIELD NAME: AVG.UNIT COST
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8                         FIELD NAME: SELLING UNIT PRICE
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: REASON CODE
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: ISSUABLE/NONISSUABLE
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: SOURCE CODE
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 10.5                      FIELD NAME: LOG TRANSACTION CODE
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: ACCOUNT CODE
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: VOUCHER NUMBER
  LOCATION: 0;15                        ACCESS: Read w/Fileman
FIELD NUMBER: 8.5                       FIELD NAME: POSTED BY
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.5                       FIELD NAME: DATE POSTED
  LOCATION: 0;17                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: OTHER INVENTORY POINT
  LOCATION: 0;18                        ACCESS: Read w/Fileman
FIELD NUMBER: 410                       FIELD NAME: TRANSACTION/P.O. NUMBER
  LOCATION: 0;19                        ACCESS: Read w/Fileman
FIELD NUMBER: 20
  FIELD NAME: ADJUSTMENT APPROVED DATE@TIME
  LOCATION: 0;20                        ACCESS: Read w/Fileman
FIELD NUMBER: 21                        FIELD NAME: ADJUSTMENT APPROVED BY
  LOCATION: 0;21                        ACCESS: Read w/Fileman
FIELD NUMBER: 6.1                       FIELD NAME: INVENTORY VALUE
  LOCATION: 0;22                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6.2                       FIELD NAME: SELL VALUE
  LOCATION: 0;23                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 411                       FIELD NAME: ISSUE BOOK LINE NUMBER
  LOCATION: 0;24                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(445.2,D0,1)
FIELD NUMBER: 9.5                       FIELD NAME: ADDITIONAL REASON TEXT
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCP(445.2,D0,2)
FIELD NUMBER: 22                        FIELD NAME: SUPPLY STATION USER
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: RECIPIENT
  LOCATION: 2;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(445.2,'B'
 GLOBAL DESCRIPTION:   "B" cross reference - used to search by Inventory Point 
GLOBAL REFERENCE: PRCP(445.2,'C'
 GLOBAL DESCRIPTION:   "C" cross reference - used to search by Transaction /
 P.O. Number.  
GLOBAL REFERENCE: PRCP(445.2,'T'
 GLOBAL DESCRIPTION:   "T" cross reference - used to search by Transaction ID. 
GLOBAL REFERENCE: PRCP(445.2,'V'
 GLOBAL DESCRIPTION:   "V" cross reference - used to search by Voucher Number.  
GLOBAL REFERENCE: PRCP(445.2,'AX'
 GLOBAL DESCRIPTION:   'AX' cross reference - used to look up by INVENTORY
 POINT, TRANSACTION DATE & TYPE 
 GENERAL DESCRIPTION:   Above PAR and the Advanced Prosthetics Acquisition Tool
 (APAT) request permission to read and write to the INVENTORY TRANSACTION FILE
 #445.2 to update Inventory Transactions within the Inventory and Stock Issue 
 functionality.  
  
 Above PAR Ad-Hoc Reporting includes the INVENTORY TRANSACTION FILE #445.2.
 Ad-Hoc functionality provides the ability to select fields from the file for
 display on user-defined reports.  Ad-Hoc offers only FileMan read access and
 only if the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   2/3/22: Added "AX" cross-reference, effective with
 DSIY*1.5*1 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6549                            IA #: 6549
  FILE NUMBER: 445.4                    GLOBAL ROOT: PRCP(445.4,
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: STORAGE LOCATION ACCESS
  ID: PRCP(445.4,
GLOBAL REFERENCE: PRCP(445.4,D0,0)
FIELD NUMBER: .01                       FIELD NAME: STORAGE LOCATION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   
                                                   Global r 
FIELD NUMBER: 1                         FIELD NAME: INVENTORY/DISTRIBUTION POINT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   
                                                   Global r 
FIELD NUMBER: 2                         FIELD NAME: EXPANDED DESCRIPTION
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   
                                                   Global r 
GLOBAL REFERENCE: PRCP(445.4,'B'
 GLOBAL DESCRIPTION:   "B" cross reference - used to look up by STORAGE
 LOCATION 
 GENERAL DESCRIPTION:   Above PAR and the Advanced Prosthetics Acquisition Tool
 (APAT) request permission to read and write to the STORAGE LOCATION FILE
 #445.4 to maintain a master list of storage locations within the Inventory
 function.  
  
 Above PAR Ad-Hoc Reporting includes the STORAGE LOCATION FILE #445.4. Ad-Hoc
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: NOV 18, 2021

NUMBER: 6550                            IA #: 6550
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCFFMO
  NAME: FMS DOCUMENTS FOR SUPPLY FUND SPECIAL CTL PT
  ID: PRCFFMO
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRCFFMO.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: SUPP
 COMPONENT DESCRIPTION:   Using the IFCAP site (PRC("SITE")) and PROCUREMENT &
 ACCOUNTING TRANSACTIONS file (#442) IEN, this component produces FMS documents
 for supply fund special control point if the Purchasing Status exists but is
 not set to "Pending Fiscal Action" and if the METHOD OF PROCESSING (#.02) is
 not "PURCHASE CARD" or "CERTIFIED INVOICE".  
VARIABLES: PRC('SITE')                  TYPE: Input
 VARIABLES DESCRIPTION:   IFCAP Site 
VARIABLES: PRCHPO                       TYPE: Input
 VARIABLES DESCRIPTION:   PROCUREMENT & ACCOUNTING TRANSACTIONS file (#442) IEN 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUL 02, 2019

NUMBER: 6551                            IA #: 6551
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCH410
  NAME: CREATE 2237 FOR NEW PURCHASE CARD ORDER
  ID: PRCH410
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRCH410 to create
 the 2237 record, record the electronic signature, and update due-ins.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: ESIG
 COMPONENT DESCRIPTION:   
                This component processes the 2237, signs the purchase 
                card order, and updates due-ins if PRCHOBL=1 (obligate 
                immediately without Fiscal).  
VARIABLES: PRC('SITE')                  TYPE: Used
 VARIABLES DESCRIPTION:   IFCAP Site 
VARIABLES: PRC('CP')                    TYPE: Used
 VARIABLES DESCRIPTION:   Control Point 
VARIABLES: PRC('FY')                    TYPE: Used
 VARIABLES DESCRIPTION:   Fiscal Year 
VARIABLES: PRC('QTR')                   TYPE: Used
 VARIABLES DESCRIPTION:   Fiscal Quarter 
VARIABLES: PODA                         TYPE: Used
 VARIABLES DESCRIPTION:   File 442 IEN 
VARIABLES: DA                           TYPE: Used
 VARIABLES DESCRIPTION:   File 410 IEN 
VARIABLES: PRCHDELV                     TYPE: Used
 VARIABLES DESCRIPTION:   Delivery Order Indicator 
VARIABLES: PRCHOBL                      TYPE: Used
 VARIABLES DESCRIPTION:   Obligation Indicator 
VARIABLES: DUZ                          TYPE: Used
 VARIABLES DESCRIPTION:   Logged-in User 
VARIABLES: CDA                          TYPE: Used
 VARIABLES DESCRIPTION:   CONTROL POINT ACTIVITY FILE (#410) IEN 
COMPONENT/ENTRY POINT: ITEM
 COMPONENT DESCRIPTION:   
  
                The items from the detailed purchase card order are 
                copied into a local array in order to store them in the 
                newly-created 2237.  
VARIABLES: BB                           TYPE: Used
 VARIABLES DESCRIPTION:   Local array that items from the detailed purchase
 card order are copied into in order to store them in the newly-created 2237.  
VARIABLES: XDA                          TYPE: Used
 VARIABLES DESCRIPTION:   PROCUREMENT & ACCOUNTING TRANSACTIONS FILE (#442) IEN 
COMPONENT/ENTRY POINT: REC
 COMPONENT DESCRIPTION:   This component creates a skeleton 2237 in the Control
 Point Activity file (#410). 
                
 When a new purchase card order is created, a 2237 is also created in the
 Control Point Activity file (#410). This component is called to create the
 skeleton 2237.  
VARIABLES: PRC('SITE')                  TYPE: Used
 VARIABLES DESCRIPTION:   IFCAP Site 
VARIABLES: PRCHPO                       TYPE: Used
 VARIABLES DESCRIPTION:   File 442 IEN 
VARIABLES: PRC('FY')                    TYPE: Used
 VARIABLES DESCRIPTION:   Fiscal Year 
VARIABLES: PRC('QTR')                   TYPE: Used
 VARIABLES DESCRIPTION:   Fiscal Quarter 
COMPONENT/ENTRY POINT: START
 COMPONENT DESCRIPTION:   
    This component is used at the beginning of the creation of a 2237.  
                
    When completing a detailed purchase card order, this component is used 
    if Type of Order is not set in the purchase card order and if the 2237 
    has not been created.  
VARIABLES: PRC('SITE')                  TYPE: Used
 VARIABLES DESCRIPTION:   IFCAP Site 
VARIABLES: PRCHPO                       TYPE: Used
 VARIABLES DESCRIPTION:   File 442 IEN 
VARIABLES: DA                           TYPE: Used
 VARIABLES DESCRIPTION:   PROCUREMENT & ACCOUNTING TRANSACTIONS FILE (#442) IEN 
COMPONENT/ENTRY POINT: SET
 COMPONENT DESCRIPTION:   This component sets item data and vendor information
 in the 2237.  
VARIABLES: PRC('SITE')                  TYPE: Used
 VARIABLES DESCRIPTION:   Numeric portion of PURCHASE ORDER NUMBER (file #442
 field #.01) before dash 
VARIABLES: PRC('SST')                   TYPE: Used
 VARIABLES DESCRIPTION:   File 442 SUBSTATION (#31), internal format 
VARIABLES: TDATE                        TYPE: Used
 VARIABLES DESCRIPTION:   Returned from $$DATE^PRC0C("T","E"),"^",7) - current
 date in FileMan format 
VARIABLES: PRC('FY')                    TYPE: Used
 VARIABLES DESCRIPTION:   The third and fourth characters of TDATE - 2-digit
 year 
VARIABLES: PRC('QTR')                   TYPE: Used
 VARIABLES DESCRIPTION:   ^-piece 2 of TDATE - FY Quarter 
VARIABLES: CDA                          TYPE: Used
 VARIABLES DESCRIPTION:   File 410 IEN 
VARIABLES: VEND                         TYPE: Used
 VARIABLES DESCRIPTION:   File 442 VENDOR (#5), internal - pointer to file 440 
VARIABLES: XDA                          TYPE: Used
 VARIABLES DESCRIPTION:   FILE 442 IEN 
VARIABLES: SDATE                        TYPE: Used
 VARIABLES DESCRIPTION:   Current date in FileMan format 
VARIABLES: CP                           TYPE: Used
 VARIABLES DESCRIPTION:   File 442 FCP (#1) 
VARIABLES: CCEN                         TYPE: Used
 VARIABLES DESCRIPTION:   File 442 COST CENTER (#2), internal, or, if null,
 first 30 characters of the file 420.1 NAME (#.01)) 
VARIABLES: VV                           TYPE: Used
 VARIABLES DESCRIPTION:   File 442 VENDOR (#5), internal 
VARIABLES: SERV                         TYPE: Used
 VARIABLES DESCRIPTION:   File 442 REQUESTING SERVICE (#5.2), internal 
VARIABLES: ST                           TYPE: Used
 VARIABLES DESCRIPTION:   Constant "ST" 
VARIABLES: LOC                          TYPE: Used
 VARIABLES DESCRIPTION:   File 442 DELIVERY LOCATION (#5.6) 
VARIABLES: ADATE                        TYPE: Used
 VARIABLES DESCRIPTION:   File 442 DELIVERY DATE (#7), internal 
VARIABLES: ESTS                         TYPE: Used
 VARIABLES DESCRIPTION:   File 442 EST. SHIPPING AND/OR HANDLING (#13) 
VARIABLES: PCREF                        TYPE: Used
 VARIABLES DESCRIPTION:   File 442 PURCHASE ORDER NUMBER (#.01), 2nd "-" piece 
VARIABLES: PRCSIP                       TYPE: Used
 VARIABLES DESCRIPTION:   File 442 ITEM subfile #442.01 subfile #442.147 LINE
 INVENTORY POINT (#.01), pointer to file 445 
VARIABLES: PC                           TYPE: Used
 VARIABLES DESCRIPTION:   File 442 PURCHASE CARD NUMBER (#46), pointer to file
 440.5 
VARIABLES: COUNT                        TYPE: Used
 VARIABLES DESCRIPTION:   Count of items from header 442.01 sub-file header
 (4th "^" piece) 
VARIABLES: BB(IT)                       TYPE: Used
 VARIABLES DESCRIPTION:   Array of Items from the file 442 ITEMS sub-file
 (#442.01) 
VARIABLES: PRCHPC                       TYPE: Used
 VARIABLES DESCRIPTION:   TYPE OF ORDER=2 => "DETAILED PURCHASE CARD" 
VARIABLES: DUZ                          TYPE: Used
 VARIABLES DESCRIPTION:   Logged-in user 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: NOV 21, 2018

NUMBER: 6552                            IA #: 6552
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCUESIG
  NAME: CHECKSUM GENERATION             ID: PRCUESIG
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT)
 requests access to IFCAP checksum generation.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: $$SUM(X)
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required)  String for which a checksum is to be
 generated 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Generated Checksum 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6553                            IA #: 6553
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCUTL
  NAME: REFORMAT WORD PROCESSING VALUE  ID: PRCUTL
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT) uses
 the IFCAP Word Processing Reformatting utility.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: DIWP(DA)
 COMPONENT DESCRIPTION:   Call DIWP^PRCUTL($G(DA)) to save DA value 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   The variable DA is being stacked to protect it from
 change by a call to ^DIWP.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   String to be stored in the ^UTILITY($J,"W") global
 and reformatted by the called VA FileMan utility ^DIWP.  
VARIABLES: DIWL                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The (integer-valued) left margin for the
 text 
VARIABLES: DIWR                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The (integer-valued) right margin for the
 text 
VARIABLES: DIWF                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) A string of format control parameters 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6554                            IA #: 6554
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Private                        TYPE: Routine
  ROUTINE: XPAR1                        NAME: VISTA PARAMETER HANDLING
  ID: XPAR1
 GENERAL DESCRIPTION:   The Logistics and Prosthetics Suite cloned certain XPAR
 functionality into its native DSIY namespace.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: LPS
KEYWORDS: APAT
COMPONENT/ENTRY POINT: INTERN
VARIABLES: ENT                          TYPE: Both
 VARIABLES DESCRIPTION:   (Optional) The parameter entity 
VARIABLES: PAR                          TYPE: Both
 VARIABLES DESCRIPTION:   (Optional) The parameter name 
VARIABLES: INST                         TYPE: Both
 VARIABLES DESCRIPTION:   (Optional) The parameter instance 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL

NUMBER: 6555                            IA #: 6555
  DATE CREATED: OCT 18, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRC0C
  NAME: IFCAP FCP ACCOUNTING INFORMATION
  ID: PRC0C
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT) and
 Above PAR use extrinsic functions in PRC0C to retrieve fund control point
 parameters and to convert calendar dates to Fiscal Year and Fiscal Quarter.
 This data is used during the creation and display of detailed purchase card 
 orders.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: $$ACC(A,B)
 COMPONENT DESCRIPTION:   The FCP/PRJ code and the year's appropriation are
 used in the creation and display of the detailed purchase card order.  The
 Fund is used in determining the Administrative Office and FUND for the
 Purchase Order display.  
VARIABLES: A                            TYPE: Input
 VARIABLES DESCRIPTION:   The 3-digit station number 
VARIABLES: B                            TYPE: Input
 VARIABLES DESCRIPTION:   Fund control point^2-digit fiscal year^beginning
 budget fiscal year 
VARIABLES: Output                       TYPE: Output
 VARIABLES DESCRIPTION:   A fund control point fund string 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 year's 
 appropriation^gross/net^"Y" if revolving fund 
COMPONENT/ENTRY POINT: $$DATE(X,A)
 COMPONENT DESCRIPTION:   The fiscal year, fiscal quarter, and the FileMan date
 are used in creating a 2237 from a purchase card order and in completing the
 detailed purchase card order in supply.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   The date to be converted 
VARIABLES: A                            TYPE: Input
 VARIABLES DESCRIPTION:   Format of input Date:  "I" if FileMan date 
                        "E" if external date 
                        "H" if $H date 
VARIABLES: Output                       TYPE: Output
 VARIABLES DESCRIPTION:   caret delimited string of 4 digit fiscal year^fiscal
 quarter^4 digit calendar year^numeric calendar month^calendar day^week day
 number^VA FileMan formatted date^$H formatted date^2 digit fiscal month 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6556                            IA #: 6556
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ENBCPM8                      NAME: POST PM HOUR TO FILE 6922
  ID: ENBCPM8
 GENERAL DESCRIPTION:   This integration agreement allows Above PAR to call
 COUNT^ENBCPM8 to update Preventive Maintenance hours within a Work Order in
 File #6922 and call UNPOST^ENBCPM8 to unpost Preventive Maintenance hours with
 a Work Order in File #6922.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: COUNT
 COMPONENT DESCRIPTION:   COUNT^ENBCPM8 called to update Preventive Maintenance
 hours within a Work Order in file # 6922.  
VARIABLES: ENPMDT                       TYPE: Input
 VARIABLES DESCRIPTION:   PM Month YYMM 
VARIABLES: PMTOT()                      TYPE: Input
 VARIABLES DESCRIPTION:   Array of PM hours by shop and tech 
COMPONENT/ENTRY POINT: UNPOST
 COMPONENT DESCRIPTION:   UNPOST^ENBCPM8 called to unpost Preventive
 Maintenance hours with a Work Order in file # 6922.  
VARIABLES: ENPMDT                       TYPE: Input
 VARIABLES DESCRIPTION:   PM Month YYMM 
VARIABLES: PMTOT()                      TYPE: Input
 VARIABLES DESCRIPTION:   Array of PM hours by shop and tech 
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6557                            IA #: 6557
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ENBCPM8
  NAME: UNPOST/REMOVE PM HOURS FROM FILE 6922
  ID: ENBCPM8                           STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
KEYWORDS: LPS
COMPONENT/ENTRY POINT: UNPOST
 COMPONENT DESCRIPTION:   This integration agreement allows the Logistics and
 Prosthetics Suite to call UNPOST^ENBCPM8 to unpost Preventive Maintenance
 hours from a Work Order within the Work Order function.  
VARIABLES: 1)                           TYPE: Input
 VARIABLES DESCRIPTION:   ENPMDT          PM Month YYMM PMTOT()         Array
 of PM hours by shop and tech 

NUMBER: 6558                            IA #: 6558
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ENEQ3
  NAME: TRANSMIT EQUIPMENT BULLETIN     ID: ENEQ3
 GENERAL DESCRIPTION:   This integration agreement allows Above PAR to call
 BULL^ENEQ3 to transmit an equipment bulletin whenever a new piece of equipment
 is added - if a mail group is established.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: BULL
 COMPONENT DESCRIPTION:   BULL^ENEQ3 called to transmit an equipment bulletin
 whenever a new piece of equipment is added - if a mail group is established.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Equipment Entry 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUL 23, 2019

NUMBER: 6559                            IA #: 6559
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ENEQPMP                      NAME: UPDATE EQUIPMENT PM PARAMETERS
  ID: ENEQPMP
 GENERAL DESCRIPTION:   This integration agreement allows Above PAR to call
 PMSE3^ENEQPMP to copy Preventive Maintenance parameters from the Equipment
 Category File to the Equipment Inventory File.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: PMSE3
 COMPONENT DESCRIPTION:   PMSE3^ENEQPMP called to copy Preventive Maintenance
 parameters from the Equipment Category (#6911) file to the Equipment Inventory
 file (#6914).  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Equipment Inventory File ^ENG(6914) 
VARIABLES: ENDTYP                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Equipment Category File ^ENG(6911) 
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6560                            IA #: 6560
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ENEQPMR4                     NAME: EXTRACT PM HOURS FROM WORK ORDER
  ID: ENEQPMR4
 GENERAL DESCRIPTION:   This integration agreement allows Above PAR to call
 PMHRS^ENEQPMR4 to extract the Preventive Maintenance Hours from a work order
 and provide a total back to the calling routine.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: PMHRS
 COMPONENT DESCRIPTION:   PMHRS^ENEQPMR4 is called to extract the Preventive
 Maintenance Hours from a work order and provide a total back to the calling
 routine.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN to the Work Order File ^ENG(6920) 
VARIABLES: PMTOT                        TYPE: Output
 VARIABLES DESCRIPTION:   Total PM hours for this work order 
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6561                            IA #: 6561
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ENFAACQ                      NAME: MAINTAIN FA DOCUMENT LOG
  ID: ENFAACQ
 GENERAL DESCRIPTION:   This integration agreement allows Above PAR to call
 ENFAACQ for FA Code Sheet processing.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: ADDFA
 COMPONENT DESCRIPTION:   ADDFA^ENFAACQ is called to create an entry in the FA
 Code Sheet file.  
VARIABLES: ENEQ('DA')                   TYPE: Input
 VARIABLES DESCRIPTION:   IEN to the Equipment Inventory File ^ENG(6914) 
COMPONENT/ENTRY POINT: SETUP
 COMPONENT DESCRIPTION:   SETUP^ENFAACQ is called to set up variables needed
 for the FA Code Sheet file.  
VARIABLES: ENEQ('DA')                   TYPE: Input
 VARIABLES DESCRIPTION:   IEN to the Equipment Inventory File ^ENG(6914) 
COMPONENT/ENTRY POINT: UPDATE
 COMPONENT DESCRIPTION:   UPDATE^ENFAACQ is called to update the Equipment file
 with FA Code Sheet information.  
VARIABLES: ENEQ('DA')                   TYPE: Input
 VARIABLES DESCRIPTION:   IEN to the Equipment Inventory File ^ENG(6914) 
COMPONENT/ENTRY POINT: VALEQ
 COMPONENT DESCRIPTION:   VALEQ^ENFAACQ is called to check the validity of the
 Equipment being added to the FA Code Sheet file.  
VARIABLES: ENEQ('DA')                   TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Equipment Inventory File ^ENG(6914) 
VARIABLES: ENBAT('SILENT')              TYPE: Input
 VARIABLES DESCRIPTION:   Turns interactive mode off 
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6562                            IA #: 6562
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ENFAUTL
  NAME: CHECK EQUIPMENT FAP STATUS      ID: ENFAUTL
 GENERAL DESCRIPTION:   This integration agreement allows Above PAR to call
 CHKFA^ENFAUTL to check the current FAP status for a piece of equipment.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: CHKFA
 COMPONENT DESCRIPTION:   CHKFA^ENFAUTL is called to check the current FAP
 status of a piece of equipment.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Equipment Inventory File ^ENG(6914) 
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   Piece 1 = 1 if FA is current, 0 if not 
  
 Piece 2 = date/time of current FA 
  
 Piece 3 = date/time of current FD 
  
 Piece 4 = IEN of most recent FA 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUL 23, 2019

NUMBER: 6563                            IA #: 6563
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  ROUTINE: PRCHDP5                      NAME: PURCHASE ORDERS:  FIND AMENDMENTS
  ID: PRCHDP5
 GENERAL DESCRIPTION:   This integration agreement allows the call
 START^PRCHDP5 to retrieve for subsequent display what changes were made by a
 specified amendment to a purchase order.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: START
 COMPONENT DESCRIPTION:   START^PRCHDP5 is called to determine which amendments
 have been made to a particular purchase order.  
VARIABLES: PRCHPO                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Purchase Order File ^PRC(442) 
VARIABLES: PRCHAM                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN to the Amendment Multiple within the Purchase
 Order File 
VARIABLES: Output                       TYPE: Output
 VARIABLES DESCRIPTION:   Temp file containing the amendment records.  
  
 ^TMP($J,"W",1,n)=amendment record; text string containing Description and the
 old and new values.  
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6564                            IA #: 6564
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHDP6
  NAME: PURCHASE ORDER:  SET UP AMENDMENT HISTORY
  ID: PRCHDP6
 GENERAL DESCRIPTION:   This integration agreement allows the call
 AMENDS^PRCHDP6 to set up a ^TMP($J,"PRCHDP6" temp file with the amendment
 history for a purchase order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: AMENDS
 COMPONENT DESCRIPTION:   AMENDS^PRCHDP6 is called to set up a ^TMP file with
 the amendment history for a purchase order.  
VARIABLES: D0                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Purchase Order File ^PRC(442) 
VARIABLES: Output                       TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,"PRCHDP6" array created with details for all
 amendments for this purchase order.  
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUL 02, 2019

NUMBER: 6565                            IA #: 6565
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHES2
  NAME: PURCHASE ORDER:  E-SIGNATURE ON RECEIVING PARTIAL
  ID: PRCHES2
 GENERAL DESCRIPTION:   This is called to encode the e-signature on the PARTIAL
 entry during receipt into inventory.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: ENCODE
 COMPONENT DESCRIPTION:   This is called to encode the e-signature on the
 PARTIAL entry created during receiving.  
VARIABLES: LEVEL0                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Purchase Order File ^PRC(442) 
VARIABLES: LEVEL1                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of PARTIAL multiple entry created when items are
 received.  
VARIABLES: USERNUM                      TYPE: Input
 VARIABLES DESCRIPTION:   User's DUZ Value 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 if e-signature complete; returns -1 through
 -4 if errors are found 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6566                            IA #: 6566
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHFPNT
  NAME: PURCHASE ORDER: RETURN FACILITY TYPE
  ID: PRCHFPNT
 GENERAL DESCRIPTION:   This integration agreement allows the call
 FTYP^PRCHFPNT to return the free-text facility type for a purchase order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: FTYP
 COMPONENT DESCRIPTION:   FTYP^PRCHFPNT is called to return the free-text
 facility type value for a purchase order.  
VARIABLES: PRC('SITE')                  TYPE: Input
 VARIABLES DESCRIPTION:   Facility Number for Purchase Order 
VARIABLES: D0                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Purchase Order File ^PRC(442) 
VARIABLES: PRCHFTP2                     TYPE: Input
 VARIABLES DESCRIPTION:   Optional If defined then process will return in
 variable PRCHFTYP the Facility Type  Abbrv.  If not defined, then the Facility
 Type Name is returned in PRCHFTYP.  
VARIABLES: PRCHFTYP                     TYPE: Output
 VARIABLES DESCRIPTION:   free-text facility type value for Purchase Order
 Verified 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUL 02, 2019

NUMBER: 6567                            IA #: 6567
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  ROUTINE: PRCHUTL                      NAME: PURCHASE ORDER:  RETURN EDI STATUS
  ID: PRCHUTL
 GENERAL DESCRIPTION:   This integration agreement allows the call
 EDISTAT^PRCHUTL to determine the EDI status of a purchase order.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: EDISTAT
 COMPONENT DESCRIPTION:   EDISTAT^PRCHUTL is called to determine the EDI status
 of a purchase order.  
VARIABLES: D0                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN to purchase order file ^PRC(442) 
VARIABLES: D1                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Item entry in the Purchase Order's ITEM
 multiple 
VARIABLES: Output                       TYPE: Output
 VARIABLES DESCRIPTION:   Line count after call 
VARIABLES: LINECNT                      TYPE: Input
 VARIABLES DESCRIPTION:   Line count before the call 
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6568                            IA #: 6568
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPAGPR
  NAME: REPETITIVE ITEM LIST - ADD OR DELETE ITEMS
  ID: PRCPAGPR
 GENERAL DESCRIPTION:   This integration agreement allows the calls to
 $$ADDITEM^PRCPAGPR which adds to REPETITIVE ITEM LIST (RIL) (#410.3), to
 $$NEWRIL^PRCPAGPR which creates new RIL items, and to DELRIL^PRCPAGPR which
 deletes RIL items.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: $$ADDITEM
 COMPONENT DESCRIPTION:   $$ADDITEM^PRCPAGPR() is called to add items to an
 existing RIL.  
VARIABLES: V1                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN for RIL entry.  
VARIABLES: V2                           TYPE: Input
 VARIABLES DESCRIPTION:   Item Master Number 
VARIABLES: V3                           TYPE: Input
 VARIABLES DESCRIPTION:   Quantity 
VARIABLES: V4                           TYPE: Input
 VARIABLES DESCRIPTION:   Vendor IEN 
VARIABLES: V5                           TYPE: Input
 VARIABLES DESCRIPTION:   Cost 
VARIABLES: Output                       TYPE: Output
 VARIABLES DESCRIPTION:   IEN of the new entry in the ITEM multiple or either
 "0" or null string if the operation fails.  
COMPONENT/ENTRY POINT: $$NEWRIL
 COMPONENT DESCRIPTION:   $$NEWRIL^PRCPAGPR() is called to add a new RIL.  
VARIABLES: V1                           TYPE: Input
 VARIABLES DESCRIPTION:   V1 is IEN to Generic Inventory File (#445) entry
 associated with the RIL.  
VARIABLES: V2                           TYPE: Input
 VARIABLES DESCRIPTION:   V2 is the name of the Transaction Number (file
 #410.1, field #.01) counter to be used to generate the RIL Entry Number (file
 #410.3, field #.01) value to use when creating the RIL entry.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   IEN of the new RIL entry or either "0" or null string
 if the operation fails.  
COMPONENT/ENTRY POINT: DELRIL
 COMPONENT DESCRIPTION:   Called to delete an RIL. 
VARIABLES: V1                           TYPE: Input
 VARIABLES DESCRIPTION:   V1 is IEN to RIL entry to be deleted.  
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6569                            IA #: 6569
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPAGU1
  NAME: DELETE TEMP STOCK LEVEL         ID: PRCPAGU1
 GENERAL DESCRIPTION:   This integration agreement allows the call
 DELTEMP^PRCPAGU1 to delete the temporary stock level in the Generic Inventory
 File ^PRCP(445).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: DELTEMP
 COMPONENT DESCRIPTION:   DELTEMP^PRCPAGU1 is called to delete the temporary
 stock level in the Generic Inventory file (#445).  
VARIABLES: V1                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Generic Inventory Point File ^PRCP(445) 
VARIABLES: V2                           TYPE: Input
 VARIABLES DESCRIPTION:   Item Master Number 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6570                            IA #: 6570
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPHLFM
  NAME: INVENTORY:  BUILD HL7 FOR ITEM DELETION
  ID: PRCPHLFM
 GENERAL DESCRIPTION:   This integration agreement allows the call
 BLDSEG^PRCPHLFM which builds an HL7 segment whenever a secondary inventory
 item is deleted.  
  
 This updates the inventory in the automated supply stations.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: BLDSEG
 COMPONENT DESCRIPTION:   BLDSEG^PRCPHLFM is called to build an HL7 segment
 whenever a secondary inventory item is deleted.  
VARIABLES: ACTION                       TYPE: Input
 VARIABLES DESCRIPTION:   For deletion, 2 is sent 
VARIABLES: ITEM                         TYPE: Input
 VARIABLES DESCRIPTION:   Item Master Number 
VARIABLES: SIP                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN for the Secondary Distribution Point 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6571                            IA #: 6571
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  ROUTINE: PRCPOPD
  NAME: DISTRIBUTION ORDER:  SEND ORDER DELETED MESSAGE
  ID: PRCPOPD
 GENERAL DESCRIPTION:   This integration agreement allows the call
 MESSAGE^PRCPOPD which sends the user a message if a Distribution Order is
 deleted.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: MESSAGE
 COMPONENT DESCRIPTION:   MESSAGE^PRCPOPD is called to send the user a message
 if a Distribution Order is deleted.  
VARIABLES: ORDER                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Distribution Order File ^PRCP(445.3) 
VARIABLES: ACTIVITY                     TYPE: Input
 VARIABLES DESCRIPTION:   1 to show order is deleted 
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6572                            IA #: 6572
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPOPER
  NAME: DISTRIBUTION ORDER:  ITEM CHECK
  ID: PRCPOPER
 GENERAL DESCRIPTION:   This integration agreement allows the call
 $$ITEMCHK^PRCPOPER to check items within a distribution order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: $$ITEMCHK
 COMPONENT DESCRIPTION:   $$ITEMCHK^PRCPOPER is checks the setups in the
 GENERIC INVENTORY file (#445) to verify that; 
  
 a.  the item is an inventory item for both the primary and the secondary 
 inventory points.  
  
 b.  that the primary inventory point is listed as the source of that item for
 the secondary inventory point.  
  
 c.  that the primary inventory's unit of issue and unit of issue package 
 multiple values are the same as the secondary inventory point's unit of 
 receipt and unit of receipt package multiple.  
VARIABLES: PRCPPRIM                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Primary Distribution Point 
VARIABLES: PRCPSECO                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Secondary Distribution Point 
VARIABLES: ITEMDA                       TYPE: Input
 VARIABLES DESCRIPTION:   Item Master Number 
VARIABLES: Return                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns errors delimited by caret for this item 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6573                            IA #: 6573
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPOPPP
  NAME: DISTRIBUTION ORDER:  POSTING    ID: PRCPOPPP
 GENERAL DESCRIPTION:   This integration agreement allows the following calls: 
   RECEIPT^PRCPOPPP to Receive Items at a Secondary Distribution Point 
   SALE^PRCPOPPP to Disburse Items from a Primary Distribution Point These
 calls are used when a Distribution Order is Posted within the Inventory
 function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: RECEIPT
 COMPONENT DESCRIPTION:   RECEIPT^PRCPOPPP is called to Receive Items at a
 Secondary Distribution Point.  
VARIABLES: PRCPSECO                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Secondary Distribution Point 
VARIABLES: ITEMDA                       TYPE: Input
 VARIABLES DESCRIPTION:   Item Master Number 
VARIABLES: TRANORDR                     TYPE: Input
 VARIABLES DESCRIPTION:   Transaction Register # 
VARIABLES: PRCPOPPP                     TYPE: Input
 VARIABLES DESCRIPTION:   PRCPOPPP("QTY") Quantity to Receive 
 PRCPOPPP("INVVAL") Inventory Value Received PRCPOPPP("OTHERPT") Inventory
 Point received from PRCPOPPP("DUEIN") Duein quantity to add (- to subtract) 
 PRCPOPPP("REASON") Reason for transaction register PRCPOPPP("PRCPPTDA")
 Pointer to file 446.1 
COMPONENT/ENTRY POINT: SALE
 COMPONENT DESCRIPTION:   SALE^PRCPOPPP is called to Disburse Items from a
 Primary Distribution Point.  
VARIABLES: PRCPPRIM                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Primary Distribution Point 
VARIABLES: ITEMDA                       TYPE: Input
 VARIABLES DESCRIPTION:   Item Master Number 
VARIABLES: TRANORDR                     TYPE: Input
 VARIABLES DESCRIPTION:   Transaction Register # 
VARIABLES: PRCPOPPP                     TYPE: Input
 VARIABLES DESCRIPTION:   PRCPOPPP("QTY") Quantity to Sale 
  
 PRCPOPPP("INVVAL") Inventory Value Sold 
  
 PRCPOPPP("ORDERDA") IEN of 445.3 (used for type) 
  
 PRCPOPPP("OTHERPT") Inventory Point sold to 
  
 PRCPOPPP("DUEOUT") Dueout quantity to add (- to subtract) 
  
 PRCPOPPP("REASON") Reason for transaction register 
  
 PRCPOPPP("NOINVPT") Set to 1 to prevent updating 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6574                            IA #: 6574
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPOPUS
  NAME: DISTRIBUTION ORDER:  CREATE NEW ORDER
  ID: PRCPOPUS
 GENERAL DESCRIPTION:   This integration agreement allows the following calls: 
    NEWORDER^PRCPOPUS to get the next Order # available 
    $$ADDNEW^PRCPOPUS to create the new order in ^PRCP(445.3) This extrinsic
 function is used when creating a new Distribution Order in the Inventory
 function.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: $$ADDNEW
 COMPONENT DESCRIPTION:   $$ADDNEW^PRCPOPUS is called to create the new order
 in file ^PRCP(445.3).  
VARIABLES: ORDER                        TYPE: Input
 VARIABLES DESCRIPTION:   Order # received when running NEWORDER^PRCPOPUS 
VARIABLES: PRCPPRIM                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Primary Distribution Point 
VARIABLES: PRCPSECO                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Secondary Distribution Point 
VARIABLES: Output                       TYPE: Output
 VARIABLES DESCRIPTION:   IEN of the new entry 
COMPONENT/ENTRY POINT: NEWORDER
 COMPONENT DESCRIPTION:   NEWORDER^PRCPOPUS is called to get the next Order #
 available.  
VARIABLES: PRCPPRIM                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Primary Distribution Point 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6575                            IA #: 6575
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  ROUTINE: PRCPSMGO
  NAME: INVENTORY:  DELETE ITEM, UPDATE CODESHEET
  ID: PRCPSMGO
 GENERAL DESCRIPTION:   This integration agreement allows Above PAR to call
 CODESHT^PRCPSMGO to update the Code Sheet if deleting the item from a
 Warehouse.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: CODESHT
 COMPONENT DESCRIPTION:   CODESHT^PRCPSMGO is called to update the Code Sheet
 if deleting the item from a Warehouse.  
VARIABLES: V1                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Station File 
VARIABLES: V2                           TYPE: Input
 VARIABLES DESCRIPTION:   Transaction Code 
VARIABLES: V3                           TYPE: Input
 VARIABLES DESCRIPTION:   Reference Number 
VARIABLES: TMP($J)                      TYPE: Output
 VARIABLES DESCRIPTION:   Sets up ^TMP file with each code sheet 
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6576                            IA #: 6576
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPSMS0
  NAME: INVENTORY:  DELETE ITEM, GET DELETE SEGMENT
  ID: PRCPSMS0
 GENERAL DESCRIPTION:   This integration agreement allows the call
 DELETE^PRCPSMS0 to get segments needed to delete an item from the Supply Fund
 Warehouse inventory point.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: DELETE
 COMPONENT DESCRIPTION:   DELETE^PRCPSMS0 is called to get segments needed to
 delete an item from the inventory point.  
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   Item Master Number 
VARIABLES: Return                       TYPE: Output
 VARIABLES DESCRIPTION:   STRING("ID") array node with value of "ID^" to which
 the NSN stripped of hyphens is appended.  
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6577                            IA #: 6577
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPUBAL
  NAME: INVENTORY:  UPDATE ITEM BALANCE
  ID: PRCPUBAL
 GENERAL DESCRIPTION:   This integration allows the following calls: 
  
 BALANCE^PRCPUBAL in order to file in the INVENTORY BALANCE file (#445.1) the
 beginning monthly balances for an item in that inventory point.  
  
 $$GETOPEN^PRCPUBAL to obtain an Inventory item's current inventory point 
 balance.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: BALANCE
VARIABLES: INVPT                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Distribution Point in file (#445) 
VARIABLES: ITEMDA                       TYPE: Input
 VARIABLES DESCRIPTION:   Item Master File Number (IMF#) 
VARIABLES: CYYMM                        TYPE: Input
 VARIABLES DESCRIPTION:   First 5 digits of an internal VA FileMan date (CYYMM)
 that is used as the month and year for that item's starting inventory balance 
COMPONENT/ENTRY POINT: $$GETOPEN
 COMPONENT DESCRIPTION:   Returns Inventory item's current inventory point
 balance in a caret delimited string representing the fields of the item's
 year/month balances in the BEGINNING MONTH-YEAR BALANCE multiple (subfile
 #445.111) entry of the INVENTORY BALANCES File (#445.1) for that inventory
 point and item.  
  String Format: 
    1 Beginning Month-Year Balance Date 
    2 Quantity On-Hand 
    3 Quantity Non-Issuable 
    4 Quantity Due-In 
    5 Quantity Due-Out 
    6 Average Unit Cost 
    7 Last Receipt Unit Cost 
    8 Total Inventory Value 
VARIABLES: INVPT                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the Distribution Point in file (#445) 
VARIABLES: ITEMDA                       TYPE: Input
 VARIABLES DESCRIPTION:   Item Master File Number (IMF#) 
VARIABLES: CYYMM                        TYPE: Input
 VARIABLES DESCRIPTION:   First 5 digits of an internal VA FileMan date (CYYMM)
 that is used as the month and year for that item's starting inventory balance. 
 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6578                            IA #: 6578
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPUCC
  NAME: DISTRIBUTION ORDER:  RECEIVE AND UPDATE COST CENTER
  ID: PRCPUCC
 GENERAL DESCRIPTION:   This integration agreement allows the call
 COSTCNTR^PRCPUCC to create the initial year_month/cost_center/inventory_point
 entry in the DISTRIBUTION /USAGE HISTORY file (#446) or update the entry's
 total cost field's value when an issue book or internal distribution order is
 received by an inventory point.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: COSTCNTR
 COMPONENT DESCRIPTION:   COSTCNTR^PRCPUCC is called to update the Cost Center
 Data when a Distribution Order is received to a Distribution Point.  
VARIABLES: TOINVPT                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of either Primary or Secondary inventory point
 receiving the items 
VARIABLES: FROMINPT                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN of either the Supply Fund Warehouse or the
 Primary Distribution Point dispensing the items 
VARIABLES: COSTCNTR                     TYPE: Input
 VARIABLES DESCRIPTION:   Cost Center of the inventory dispensing the items so
 that usage can be reported by Cost Center rather than only the dispensing
 inventory point 
VARIABLES: COST                         TYPE: Input
 VARIABLES DESCRIPTION:   Cost Center of the inventory receiving.  
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6579                            IA #: 6579
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPUITM
  NAME: DISTRIBUTION ORDER:  INVENTORY ITEM DELETION
  ID: PRCPUITM
 GENERAL DESCRIPTION:   This integration agreement allows the call
 DELITEM^PRCPUITM to delete the item from the inventory point and any supply
 station that was linked to that (secondary) inventory point during an AutoGen 
 process when the item is flagged as KILL WHEN ZERO.  The call to DELITEM is a
 sub-process of DSIYGO01 (cloned PRCPAGP1 process) and DSIYGO07 (cloning
 PRCPAGS1 process).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: DELITEM
 COMPONENT DESCRIPTION:   DELITEM^PRCPUITM is called to delete the item from
 the inventory point and any supply station that was linked to that (secondary)
 inventory point during an AutoGen process when the item is flagged as KILL
 WHEN ZERO.  
VARIABLES: PRCPINPT                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Distribution Point 
VARIABLES: ITEMDA                       TYPE: Input
 VARIABLES DESCRIPTION:   Item Master Number 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6580                            IA #: 6580
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPUMAN
  NAME: INVENTORY:  SCREEN VENDOR FOR ITEM
  ID: PRCPUMAN
 GENERAL DESCRIPTION:   This integration agreement allows the call
 SCREEN^PRCPUMAN to screen selection of source vendor when adding to an Item
 within a Distribution Point.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: SCREEN
 COMPONENT DESCRIPTION:   SCREEN^PRCPUMAN is called to screen VENDOR when 
 adding to an Item within a Distribution Point.  
VARIABLES: INVPT                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Distribution Point 
VARIABLES: ITEMDA                       TYPE: Input
 VARIABLES DESCRIPTION:   Item Master Number 
VARIABLES: SCREEN1                      TYPE: Input
 VARIABLES DESCRIPTION:   Send 1 to add to selection screen for Supply Fund
 Warehouse and Primary inventory points that the vendor is in the PROCUREMENT
 SOURCE multiple (#445.07) for that item; otherwise send 0.  
VARIABLES: $T                           TYPE: Output
 VARIABLES DESCRIPTION:   0 if failed screen; 1 if passed 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUL 02, 2019

NUMBER: 6581                            IA #: 6581
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPUPAT
  NAME: DISTRIBUTION ORDER:  CREATE PATIENT ENTRY
  ID: PRCPUPAT
 GENERAL DESCRIPTION:   This integration agreement allows the call
 $$PATIENT^PRCPUPAT() to create an entry in the INVENTORY DISTRIBUTED PATIENT
 SUPPLIES file (#446.1) during posting of the distribution order if it includes
 patient supplies.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: $$PATIENT
 COMPONENT DESCRIPTION:   $$PATIENT^PRCPUPAT() is called to create an entry in
 the file ^PRCP(446.1) if patient supplies are included in a Distribution
 Order.  
VARIABLES: PATDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Patient File (#2) entry.  
VARIABLES: SURGDA                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Surgery File (#130) entry.  
VARIABLES: Return                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns the IEN of entry created in the INVENTORY
 DISTRIBUTED PATIENT SUPPLIES file (#446.1).  
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6582                            IA #: 6582
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPUSA
  NAME: INVENTORY:  BARCODE UPDATE      ID: PRCPUSA
 GENERAL DESCRIPTION:   This integration agreement allows the call
 $$UPDATE^PRCPUSA() to update Distribution Points when reading data from a bar
 code scanner.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: $$UPDATE
 COMPONENT DESCRIPTION:   $$UPDATE^PRCPUSA() is called to update Distribution
 Points when reading data from a bar code scanner.  
VARIABLES: PRCPZ                        TYPE: Input
 VARIABLES DESCRIPTION:   PRCPZ         an array                              
 PRCPZ("I")    IEN to distribution point PRCPZ("ITEM") Item Master Number       
             PRCPZ("TYP")  Type of Distribution             PRCPZ("QTY") 
 Quantity to add to on-hand            PRCPZ("COM")  Transaction Register
 Comments 
VARIABLES: Return                       TYPE: Output
 VARIABLES DESCRIPTION:   Error message is returned if unsuccessful, null if
 successful 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: AUG 15, 2018

NUMBER: 6583                            IA #: 6583
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPUSAG
  NAME: INVENTORY - UPDATE ITEM RECEIPT HISTORY RECEIPTS
  ID: PRCPUSAG
 GENERAL DESCRIPTION:   This integration agreement allows the call
 RECEIPTS^PRCPUSAG to update the Inventory Item's Receipts History in the
 Generic Inventory file (#445) Receipts History By Item subfile (#445.06) when
 a replenishment order is received into a Distribution Point. 
  
 NOTE:  Although the order for Primary Inventory Points would be a Purchase
 Order, for Secondary Inventory Points, the order would be a Distribution
 Order.  (If sites were operating a Supply Fund Warehouse, the order for
 Primary Inventories would be either Issue Book for receipt from Warehouse or
 Purchase Order for receipt from external vendor.) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: RECEIPTS
VARIABLES: INVPT                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Distribution Point 
VARIABLES: ITEMDA                       TYPE: Input
 VARIABLES DESCRIPTION:   Item Master File Number 
VARIABLES: QTY                          TYPE: Input
 VARIABLES DESCRIPTION:   Quantity Received 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6584                            IA #: 6584
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPUTRA
  NAME: INVENTORY: UPDATE QTY ORD'D,DUE-IN,OR DEL OUTSTANDING REQST
  ID: PRCPUTRA
 GENERAL DESCRIPTION:   This integration agreement allows the following calls: 
    KILLTRAN^PRCPUTRA to kill any outstanding transactions 
    OUTST^PRCPUTRA to add Quantity to outstanding transactions 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: KILLTRAN
 COMPONENT DESCRIPTION:   KILLTRAN^PRCPUTRA is called to delete an outstanding
 request transaction for an item in a distribution point.  
VARIABLES: INVPT                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Distribution Point 
VARIABLES: ITEMDA                       TYPE: Input
 VARIABLES DESCRIPTION:   Item Master Number 
VARIABLES: TRANDA                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of transaction entry in the OUTSTANDING REQUEST
 subfile (#445.09) to Kill.  
COMPONENT/ENTRY POINT: OUTST
 COMPONENT DESCRIPTION:   OUTST^PRCPUTRA is called to adjust the quantity
 ordered on an outstanding request transaction 
VARIABLES: INVPT                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Distribution Point 
VARIABLES: ITEMDA                       TYPE: Input
 VARIABLES DESCRIPTION:   Item Master File number 
VARIABLES: TRANDA                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of transaction entry in the OUTSTANDING REQUEST
 subfile (#445.09) to update 
VARIABLES: QTY                          TYPE: Input
 VARIABLES DESCRIPTION:   Adjustment to quantity 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6585                            IA #: 6585
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPUTRX
  NAME: INVENTORY: GET INVENTORY TRANSACTION # & CREATE TRANS
  ID: PRCPUTRX
 GENERAL DESCRIPTION:   This integration agreement allows these calls: 
   ADDTRAN^PRCPUTRX to add a transaction entry to the Transaction Register 
      ^PRCP(445.2) to record a received Purchase Order, Distribution Order, or
 Issue Book 
  
   $$ORDERNO^PRCPUTRX() to receive a new transaction entry # 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: ADDTRAN
 COMPONENT DESCRIPTION:   ADDTRAN^PRCPUTRX is called to add a transaction entry
 to the Transaction Register (#445.2) when an inventory point (Supply Fund
 Warehouse or Primary Inventory point) dispenses items to its distribution
 inventory point (Primary Inventory point or Secondary Inventory Point,
 respectively) a dispensing 'R' transaction is created for the source inventory
 point and a receiving 'RC' transaction is created for the receiving inventory
 point.  
  
 Above PAR calls ADDTRAN^PRCPUTRX to create an "RC" transaction when a PO item
 is received into an inventory point.  
VARIABLES: INVPT                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN to the Distribution Point 
VARIABLES: ITEMDA                       TYPE: Input
 VARIABLES DESCRIPTION:   Item Master Number 
VARIABLES: TRANTYPE                     TYPE: Input
 VARIABLES DESCRIPTION:   Transaction Type 
VARIABLES: ORDERNO                      TYPE: Input
 VARIABLES DESCRIPTION:   Order Number 
VARIABLES: PRCPDATA an array            TYPE: Input
 VARIABLES DESCRIPTION:   PRCPDATA("DATE")       Date of Transaction 
 PRCPDATA("QTY")        Quantity of Transaction PRCPDATA("INVVAL")    
 Inventory Value PRCPDATA("SELVAL")     Sales Value             
 PRCPDATA("AVGUNIT")    Average Unit Cost PRCPDATA("SELUNIT")    Selling Unit
 Cost PRCPDATA("PKG")        Unit per Issue          PRCPDATA("REF")       
 Reference Number PRCPDATA("2237PO")     2237 or PO Number PRCPDATA("ISSUE")    
  Issue or NonIssue PRCPDATA("OTHERPT")    Other Distribution Point 
 PRCPDATA("REASON")     Reason                   PRCPDATA("REASONCODE") Reason
 code for other 
                          adjustment                 PRCPDATA("RECIPIENT")  Who
 got the supply PRCPDATA("USER")       Person who took the supply 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   IEN of Inventory Transaction file (#445.2) entry
 added or '0' if creation failed 
COMPONENT/ENTRY POINT: $$ORDERNO
 COMPONENT DESCRIPTION:   $$ORDERNO^PRCPUTRX() is called to receive a new
 transaction entry #.  
VARIABLES: INVPT                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN to Distribution Point 
VARIABLES: Return                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns the next order # for the Distribution Point 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6586                            IA #: 6586
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCTLAB
  NAME: INVENTORY:  BARCODE PRINT       ID: PRCTLAB
 GENERAL DESCRIPTION:   This integration agreement allows the call EN^PRCTLAB
 to print Bar Code labels.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   EN^PRCTLAB is called to print Bar Code labels. 
 Processing variables are verified prior to calling EN^PRCTLAB to ensure that
 prompts and responses are not necessary.  Verification is made that Custom
 Label file (#446.5) contains one or more lines of compiled code in the word
 processing field FILEMAN CODE (#3).  
VARIABLES: PRCT                         TYPE: Used
 VARIABLES DESCRIPTION:   Requires PRCT - IEN for ^PRCT(446.5, 
VARIABLES: PRCTCPY                      TYPE: Used
 VARIABLES DESCRIPTION:   Set to 1 to avoid prompt for number of copies 
VARIABLES: PRCTSR                       TYPE: Used
 VARIABLES DESCRIPTION:   Set to 0 to avoid prompt for Search before Sorting 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: NOV 21, 2018

NUMBER: 6587                            IA #: 6587
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCTREAD
  NAME: INVENTORY:  BARCODE TASKMAN REQUEST
  ID: PRCTREAD
 GENERAL DESCRIPTION:   This integration agreement allows the call
 TASK^PRCTREAD to create the TaskMan process to run entry points in routine
 PRCPBALM to update the inventory counts or calculate inventory usage based on
 the data uploaded from the barcode reader after barcode scanning inventory
 stock.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: TASK
 COMPONENT DESCRIPTION:   The TASK module is only called if field POST UPLOAD
 ROUTINE (#446.4, #.03) is not defined.  If POST UPLOAD ROUTINE is defined,
 then processing will be directed to a specified tag and routine.  
  
 Prior to calling the TASK module, the process will verify that it has the
 variables to ensure that prompts/Reads within the TASK module are not
 necessary. Writes to the screen in the TASK module will be ignored by the GUI. 
 
VARIABLES: PRCTID                       TYPE: Input
 VARIABLES DESCRIPTION:   Device ID for this printing 
VARIABLES: PRCTTI                       TYPE: Input
 VARIABLES DESCRIPTION:   Date/Time of upload 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: AUG 27, 2018

NUMBER: 6588                            IA #: 6588
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  ROUTINE: PRCUTL1
  NAME: DISTRIBUTION ORDER:  NEW DOCUMENT ID
  ID: PRCUTL1
 GENERAL DESCRIPTION:   This integration agreement allows the call
 EN1^PRCUTL1(.X) to either add a new entry in the Transaction Number file
 (#410.1) or to update the value in the COUNTER field (#1) of an existing entry
 of this file of counters.  This call gets a new Document ID.  The stub of the
 transaction number is set into a variable which is passed by reference to the
 API.  After the call, the assigned transaction number is passed back in that
 variable.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   EN1^PRCUTL1(.X) is called to either add a new entry
 in the Transaction Number file (#410.1) or to update the value in the COUNTER
 field (#1) of an existing entry of this file of counters.  This call gets a
 new Document ID.  The stub of the transaction number is set into a variable 
 which is passed by reference to the API.  After the call, the assigned 
 transaction number is passed back in that variable.  
VARIABLES: X                            TYPE: Both
 VARIABLES DESCRIPTION:   Before the call, the stub of the Transaction Number;
 after the call, the assigned Transaction Number 
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6589                            IA #: 6589
  DATE CREATED: OCT 25, 2016            CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY
  USAGE: Private                        TYPE: Routine
  ROUTINE: PSAGIP
  NAME: PURCHASE ORDER:  UPDATE DRUG ACCOUNTABILITY
  ID: PSAGIP
 GENERAL DESCRIPTION:   This integration agreement permits the following
 programming calls: 
   EN^PSAGIP to set up information to pass to Drug Accountability.  
   EX^PSAGIP to set up the TaskMan job to pass information.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   EN^PSAGIP is called to set up information to pass to
 Drug Accountability.  
VARIABLES: PSAGIP                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN to file 445 
VARIABLES: PSAITEM                      TYPE: Input
 VARIABLES DESCRIPTION:   Master Item Number 
VARIABLES: PSAQTY                       TYPE: Input
 VARIABLES DESCRIPTION:   Quantity received in dispensing units 
VARIABLES: PSAISS
 VARIABLES DESCRIPTION:   IEN to file 41 
VARIABLES: PSAEX                        TYPE: Input
 VARIABLES DESCRIPTION:   External of IEN from either 410 or 442 
VARIABLES: PSATR                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN to file 445.2 
VARIABLES: PSACOST                      TYPE: Input
 VARIABLES DESCRIPTION:   Total cost of receipt 
VARIABLES: PSANDC                       TYPE: Input
 VARIABLES DESCRIPTION:   NCD with dashes 
VARIABLES: Return                       TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP("PSA",$J) file with information for Drug
 Accountability 
COMPONENT/ENTRY POINT: EX
 COMPONENT DESCRIPTION:   EX^PSAGIP is called to set up the TaskMan job to pass
 information.  
VARIABLES: Input                        TYPE: Input
 VARIABLES DESCRIPTION:   Variables are read from ^TMP file set up in EN^PSAGIP 
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6590                            IA #: 6590
  DATE CREATED: OCT 27, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCSRIE1
  NAME: RIL: UPDATE DELIVERY ORDER ITEM FIELD
  ID: PRCSRIE1
 GENERAL DESCRIPTION:   This integration agreement allows the call
 CHECK^PRCSRIE1 to update for a given REPETITIVE ITEM LIST file (#410.3) item
 entry, the DELIVER ORDER ITEM field (#5) the based on whether that item is
 under contract for the assigned vendor.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: CHECK
VARIABLES: PRCSDA                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN for Repetitive Item List 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6591                            IA #: 6591
  DATE CREATED: OCT 28, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCH7PUC
  NAME: GUI PURCHASE CARD PROS ORDER INTERFACE
  ID: PRCH7PUC
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT) uses
 the existing IFCAP GUI interface to create Prosthetic Purchase Card Orders.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: UP1
 COMPONENT DESCRIPTION:   ENTRY FOR GUI PURCHASING 
VARIABLES: PRCA                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Prosthetics 1358 (file #664) 
VARIABLES: PRCB                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of Procurement & Accounting Transactions file
 (#442) 
VARIABLES: PRCC                         TYPE: Input
 VARIABLES DESCRIPTION:   Total Cost 
VARIABLES: PRCSITE                      TYPE: Input
 VARIABLES DESCRIPTION:   Station Number 
VARIABLES: PRCVEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Vendor IEN (file #440) 
VARIABLES: PRCRMPR                      TYPE: Input
 VARIABLES DESCRIPTION:   Variable to quit in IFCAP e-Sig routine PRCUESIG 
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   Flag indicating the results 
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   NEW PERSON file (#200) entry for user 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6592                            IA #: 6592
  DATE CREATED: OCT 28, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCH7PA1
  NAME: PURCHASE ORDER NUMBER RETRIEVAL
  ID: PRCH7PA1
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT) uses
 the existing IFCAP API to take the specified Common Numbering Series and
 update the PAT NUMBER (#442.6) File for the next number.  An entry in the 
 PROCUREMENT & ACCOUNTING TRANSACTIONS (#442) File is also created for use in
 obligation.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: AD1
 COMPONENT DESCRIPTION:   Create the next PAT number.  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   Current User IEN (file #200) 
VARIABLES: PRCSITE                      TYPE: Input
 VARIABLES DESCRIPTION:   Station Number IEN (file #411) 
VARIABLES: RMPRSITE                     TYPE: Input
 VARIABLES DESCRIPTION:   Prosthetics Site Parameters file (#669.9) IEN 
VARIABLES: PRCHXXX                      TYPE: Input
 VARIABLES DESCRIPTION:   Purchase Card Information File (#440.5) IEN 
VARIABLES: PRCHVEN                      TYPE: Input
 VARIABLES DESCRIPTION:   Vendor file IEN (#440) 
VARIABLES: PRC4426                      TYPE: Input
 VARIABLES DESCRIPTION:   PAT Number file (#442.6) IEN - common numbering
 series 
VARIABLES: RESULTS(0)                   TYPE: Output
 VARIABLES DESCRIPTION:   Procurement & Accounting Transactions file (#442) IEN
 ^ Obligation Number 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6593                            IA #: 6593
  FILE NUMBER: 49                       GLOBAL ROOT: DIC(49,
  DATE CREATED: OCT 28, 2016            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: File
  NAME: READ ACCESS FOR SERVICE/SECTION FILE
  ID: DIC(49,
GLOBAL REFERENCE: DIC(49,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.5                       FIELD NAME: MAIL SYMBOL
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.6                       FIELD NAME: PARENT SERVICE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.7                       FIELD NAME: TYPE OF SERVICE
  LOCATION: 0;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(49,'B'
 GLOBAL DESCRIPTION:   File 49 'B' cross reference  Used to look up by Service
 or 
                              Section name 
 GENERAL DESCRIPTION:   Above PAR and Advanced Prosthetics Acquisition Tool
 request read access to the SERVICE/SECTION FILE #49 for use in retrieving the
 Service Name and Mail Symbol when displaying a detailed purchase card order
 and when providing a list of services. 
  
 Above PAR Ad-Hoc Reporting includes the SERVICE/SECTION FILE #49.  Ad-Hoc
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL

NUMBER: 6594                            IA #: 6594
  FILE NUMBER: 44                       GLOBAL ROOT: SC(44,
  DATE CREATED: NOV 03, 2016            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HOSPITAL LOCATION FILE ACCESS
  ID: SC(44,
GLOBAL REFERENCE: SC(D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: STOP CODE NUMBER
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 2502                      FIELD NAME: NON-COUNT CLINIC? (Y OR N)
  LOCATION: 0;17                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT) checks
 the HOSPITAL LOCATION File (#44) to obtain the location name, to determine if
 the clinic is non-count, and to check the stop code number.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUL 26, 2018

NUMBER: 6595                            IA #: 6595
  FILE NUMBER: 411                      GLOBAL ROOT: PRC(411,
  DATE CREATED: NOV 03, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ADMIN. ACTIVITY SITE PARAMETER FILE ACCESS
  ID: PRC(411,
GLOBAL REFERENCE: PRC(411,D0,0)
FIELD NUMBER: .01                       FIELD NAME: STATION/SUBSTATION CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 21                        FIELD NAME: PRIMARY STATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 32                        FIELD NAME: ADDRESS CODE(GSA)
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 22                        FIELD NAME: FISCAL ACCOUNTING AUTOMATED
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: FMS PAYMENTS BY STATION
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 25
  FIELD NAME: RECEIVING REPORT TRANS METHOD
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: .5                        FIELD NAME: FACILITY TYPE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 33                        FIELD NAME: PRINT REC RPT IN FISCAL
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 34                        FIELD NAME: DISPLAY UNOBLIGATED BALANCE?
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: .1                        FIELD NAME: INSTITUTION NAME
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 20                        FIELD NAME: SUPPLY P.O. FORM TYPE
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 24                        FIELD NAME: SUPPLY RECEIVING LOCATION
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 35
  FIELD NAME: RECEIPT BEFORE OBLIGATION OK?
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 26                        FIELD NAME: CODE SHEET RETENTION PERIOD
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 27                        FIELD NAME: DATE/TIME STAMP IN FISCAL
  LOCATION: 0;15                        ACCESS: Read w/Fileman
FIELD NUMBER: 28                        FIELD NAME: SUPPLY ENTER BOC
  LOCATION: 0;16                        ACCESS: Read w/Fileman
FIELD NUMBER: 29                        FIELD NAME: STATUS OF FUNDS TRACKING
  LOCATION: 0;17                        ACCESS: Read w/Fileman
FIELD NUMBER: 30                        FIELD NAME: INTERMEDIATE PRODUCT CODE?
  LOCATION: 0;18                        ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: PRINT FMS VENDOR ID
  LOCATION: 0;19                        ACCESS: Read w/Fileman
FIELD NUMBER: 37                        FIELD NAME: CAN FISCAL ADD VENDORS?
  LOCATION: 0;20                        ACCESS: Read w/Fileman
FIELD NUMBER: 38                        FIELD NAME: ISSUE BOOK SORT DEFAULT
  LOCATION: 0;21                        ACCESS: Read w/Fileman
FIELD NUMBER: 39                        FIELD NAME: SCREEN FOR FISCAL USER
  LOCATION: 0;22                        ACCESS: Read w/Fileman
FIELD NUMBER: 41                        FIELD NAME: ISMS/LOG SWITCH
  LOCATION: 0;23                        ACCESS: Read w/Fileman
FIELD NUMBER: 48                        FIELD NAME: DAYS TO TRACK INVOICES
  LOCATION: 0;24                        ACCESS: Read w/Fileman
FIELD NUMBER: 49
  FIELD NAME: CARRY FORWARD 4TH QTR REQUESTS
  LOCATION: 0;25                        ACCESS: Read w/Fileman
FIELD NUMBER: 61                        FIELD NAME: PROMPT WHEN PRINTING?
  LOCATION: 0;26                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(411,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: RECEIVING LOCATION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: STREET ADDR.1
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: STREET ADDR.2
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: STREET ADDR.3
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: CITY
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: STATE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: ZIP CODE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: DELIVERY HOURS
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: SHIP TO SUFFIX
  LOCATION: 0;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(411,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PRINTER LOCATION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DEVICE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: STACK DOCUMENTS
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DAYS FOR DOCUMENTS RETENTION
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(411,D0,3)
FIELD NUMBER: 15                        FIELD NAME: HOSPITAL STREET ADDR.1
  LOCATION: 3;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 16                        FIELD NAME: HOSPITAL STREET ADDR.2
  LOCATION: 3;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 17                        FIELD NAME: HOSPITAL CITY
  LOCATION: 3;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 18                        FIELD NAME: HOSPITAL STATE
  LOCATION: 3;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 19                        FIELD NAME: HOSPITAL ZIP
  LOCATION: 3;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 19.2                      FIELD NAME: HOSPITAL PHONE
  LOCATION: 3;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 42                        FIELD NAME: ISMS MAILGROUP
  LOCATION: 3;7                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(411,D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: MAIL INVOICE LOCATION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: MAIL INVOICE ADDRESS1
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: MAIL INVOICE ADDRESS2
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: MAIL INVOICE ADDRESS3
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: MAIL INVOICE CITY
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: MAIL INVOICE STATE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: MAIL INVOICE ZIP
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: BILL TO SUFFIX
  LOCATION: 0;8                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(411,D0,5,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ACTIVITY ADDRESS CODE (DLA)
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PRIMARY ADDRESS?
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(411,D0,6,D1,0)
FIELD NUMBER: .01                       FIELD NAME: AUTHORIZED FISCAL USER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(411,D0,6,'B'
 GLOBAL DESCRIPTION:   File 411.05 "B" cross-reference   Used to check for
 AUTHORIZED FISCAL USER 
GLOBAL REFERENCE: PRC(411,D0,7)
FIELD NUMBER: 43                        FIELD NAME: ISMS TRANSACTION TIMEOUT
  LOCATION: 7;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 44                        FIELD NAME: VALIDATION VERSION
  LOCATION: 7;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(411,D0,8,D1,0)
FIELD NUMBER: .01                       FIELD NAME: IFCAP TERMINATED USER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(411,D0,9)
FIELD NUMBER: 46                        FIELD NAME: APPLICATION COORDINATOR
  LOCATION: 9;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 47                        FIELD NAME: FMS SECURITY CODE
  LOCATION: 9;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 104                       FIELD NAME: FISCAL REVIEW OF VRQ
  LOCATION: 9;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 105                       FIELD NAME: PRODUCTION/TRAINING
  LOCATION: 9;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 50                        FIELD NAME: FMS-ET VENDOR CODE
  LOCATION: 9;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 51                        FIELD NAME: FMS-ET ALTERNATE ADDRESS
  LOCATION: 9;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 52
  FIELD NAME: RANGE OF % FOR RECONCILING AMT
  LOCATION: 9;7                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(411,D0,50)
FIELD NUMBER: 101                       FIELD NAME: PARENT STATION
  LOCATION: 50;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 102                       FIELD NAME: FACILITY NAME
  LOCATION: 50;2                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(411,D0,60)
FIELD NUMBER: 60                        FIELD NAME: FMS-ET RECORD COUNTER
  LOCATION: 60;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 106                       FIELD NAME: FCP MONITOR STATUS
  LOCATION: 60;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 107                       FIELD NAME: FCP MONITOR RUNNING?
  LOCATION: 60;3                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(411,'AC'
 GLOBAL DESCRIPTION:   File 411 "AC" cross-reference  Used to look up by
 PRIMARY STATION 
GLOBAL REFERENCE: PRC(411,'AE'
 GLOBAL DESCRIPTION:   File 411 "AE" cross-reference  Used to look up by SCREEN
 FOR FISCAL USER 
GLOBAL REFERENCE: PRC(411,'B'
 GLOBAL DESCRIPTION:   File 411 "B" cross-reference  Used to check for
 AUTHORIZED FISCAL USER 
GLOBAL REFERENCE: PRC(411,'UP'
 GLOBAL DESCRIPTION:   File 411 "UP" cross-reference  Used to check for
 AUTHORIZED FISCAL USER 
 GENERAL DESCRIPTION:   Above PAR and the Advanced Prosthetics Acquisition Tool
 (APAT) request READ access to the ADMIN. ACTIVITY SITE PARAMETER FILE #411 to 
 retrieve Receiving Locations and Substation data when creating or displaying
 detailed purchase card orders and when verifying that a site is an IFCAP site. 
  
 If SCREEN FOR FISCAL USER (#39) is set, APAT may require that the user is an
 AUTHORIZED FISCAL USER (#40 (subfile 411.05)).  
  
 Above PAR Ad-Hoc Reporting includes the ADMIN. ACTIVITY SITE PARAMETER FILE
 #411. Ad-Hoc functionality provides the ability to select fields from the file
 for display on user-defined reports.  Ad-Hoc offers only FileMan read access
 and only if the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6596                            IA #: 6596
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: NOV 03, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PATIENT FILE ACCESS
  ID: DPT(
GLOBAL REFERENCE: DPT(D0,0)
FIELD NUMBER: .0905                     FIELD NAME: 1U4N
  LOCATION: ;COMPUTED                   ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT)
 retrieves the patient's computed 1U4N (#.0905) field from the PATIENT file
 (#2) via FileMan APIs for use in patient identification.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: PATIENT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 1EE/20/2022, effective with DSSV*1.0*1 DSS Class
 3 product Document Only 
  DATE ACTIVATED: JUL 26, 2018

NUMBER: 6597                            IA #: 6597
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123,
  DATE CREATED: NOV 04, 2016
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: REQUEST/CONSULTATION FILE ACCESS
  ID: GMR(123,
GLOBAL REFERENCE: GMR(123,D0,0)
FIELD NUMBER: .01                       FIELD NAME: FILE ENTRY DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: PATIENT LOCATION
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: ROUTING FACILITY
  LOCATION: 0;23                        ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: URGENCY
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SENDING PROVIDER
  LOCATION: 0;14                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: GMR(123,D0,40,D1,0)
FIELD NUMBER: 4                         FIELD NAME: WHO ENTERED ACTIVITY
  LOCATION: 0;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: GMR(123,D0,40,D1,1,0)
FIELD NUMBER: 5                         FIELD NAME: COMMENT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: GMR(123,D0,40,D1,2)
FIELD NUMBER: .21                       FIELD NAME: REMOTE ENTERING PERSON
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   
  The Advanced Prosthetics Acquisition Tool (APAT) requests read access to 
  the Request/Consultation file when determining if a Prosthetic Suspense 
  needs to be sent to PCE.  
  
  Revision History: 
  - 10/24/24: Added following to ICR, .07 ROUTING FACILITY, 4 WHO ENTERED 
 ACTIVITY, 5 COMMENT and .21 REMOTE ORDERING PERSON 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: OCT 28, 2024

NUMBER: 6598                            IA #: 6598
  FILE NUMBER: 771                      GLOBAL ROOT: HL(771,
  DATE CREATED: NOV 04, 2016            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  NAME: HL7 APPLICATION PARAMETER FILE ACCESS
  ID: HL(771,
GLOBAL REFERENCE: HL(771,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ACTIVE/INACTIVE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   
  The Advanced Prosthetics Acquisition Tool (APAT) requests read access to 
  the HL7 APPLICATION PARAMETER file. Reading this field will allow APAT to 
  determine if the HL7 application associated with the HL7 interface 
  is active or not.  If the HL7 application is not active, the call to 
  the HL7 interface will quit, thus avoiding needless processing.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL

NUMBER: 6599                            IA #: 6599
  FILE NUMBER: 101                      GLOBAL ROOT: ORD(101,
  DATE CREATED: NOV 04, 2016            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: PROTOCOL FILE ACCESS            ID: ORD(101,
 GENERAL DESCRIPTION:   
  The Advanced Prosthetics Acquisition Tool (APAT) requests access to find 
  the IEN associated with the HL7 server protocol in order to set up HL7 
  environment variables.  
      
       ^ORD(101,D0,0) 
         .01       NAME                 0;1     Fileman r 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: LPS
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL

NUMBER: 6600                            IA #: 6600
  FILE NUMBER: 411.2                    GLOBAL ROOT: PRC(411.2,
  DATE CREATED: NOV 04, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: FACILITY TYPE (TEMPORARY) FILE ACCESS
  ID: PRC(411.2,
GLOBAL REFERENCE: PRC(411.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ABBREVIATED TYPE CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: LONG FACILITY NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(411.2,'B'
 GLOBAL DESCRIPTION:   File 411.2 "B" cross reference   Used to look up the
 LONG FACILITY 
                                  NAME by ABBREVIATED TYPE CODE 
 GENERAL DESCRIPTION:   
  The Advanced Prosthetics Acquisition Tool (APAT) requests read access to 
  the Facility type/name in the Facility Type (Temporary) file in order to 
  display it on the detailed purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Effective 4/4/23, use of 'B' cross reference of the
 FACILITY TYPE (TEMPORARY) (#411.2) to look up the LONG FACILITY NAME by
 ABBREVIATED TYPE CODE added.  
  DATE ACTIVATED: APR 04, 2023

NUMBER: 6601                            IA #: 6601
  FILE NUMBER: 440.2                    GLOBAL ROOT: PRC(440.2,
  DATE CREATED: NOV 04, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DIRECT DELIVERY PATIENTS FILE ACCESS
  ID: PRC(440.2,
GLOBAL REFERENCE: PRC(440.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: STREET ADDR.1
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: STREET ADDR.2
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: STREET ADDR.3
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: CITY
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: STATE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: ZIP CODE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT)
 requests read access to the patient name and address in the DIRECT DELIVERY
 PATIENTS FILE #440.2 for display on the detailed purchase card order.  
  
 Above PAR Ad-Hoc Reporting includes the DIRECT DELIVERY PATIENTS FILE #440.2.
 Ad-Hoc functionality provides the ability to select fields from the file for
 display on user-defined reports.  Ad-Hoc offers only FileMan read access and
 only if the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: NOV 21, 2018

NUMBER: 6602                            IA #: 6602
  FILE NUMBER: 442.4                    GLOBAL ROOT: PRC(442.4,
  DATE CREATED: NOV 04, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PURCHASE AUTHORITY FILE ACCESS
  ID: PRC(442.4,
GLOBAL REFERENCE: PRC(442.4,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ABBREVIATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DESCRIPTION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   
  Permission for read access to the Purchase Authority Abbreviation in the 
  PURCHASE AUTHORITY file (#442.4) is requested for display on the detailed 
  purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6603                            IA #: 6603
  FILE NUMBER: 442.6                    GLOBAL ROOT: PRC(442.6,
  DATE CREATED: NOV 04, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PAT NUMBER FILE ACCESS
  ID: PRC(442.6,
GLOBAL REFERENCE: PRC(442.6,D0,0)
FIELD NUMBER: .01                       FIELD NAME: COMMON NUMBERING SERIES
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: LOWER BOUND
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: UPPER BOUND
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: NEXT NUMBER
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: USING SECTION
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: FISCAL YEAR
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PRC(442.6,'B'
 GLOBAL DESCRIPTION:   'B' cross reference  Used to look up by COMMON NUMBERING
 SERIES 
GLOBAL REFERENCE: PRC(442.6,'C'
 GLOBAL DESCRIPTION:   'C' cross-reference  Used to look up by COMMON NUMBERING
 SERIES without 
                      the Site Number 
 GENERAL DESCRIPTION:   
  The Advanced Prosthetics Acquisition Tool (APAT) requests read access to 
  the PAT Number file (#442.6) when presenting the available Common 
  Numbering Series to be chosen when creating a purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6604                            IA #: 6604
  FILE NUMBER: 442.7                    GLOBAL ROOT: PRC(442.7,
  DATE CREATED: NOV 04, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ADMINISTRATIVE CERTIFICATIONS FILE ACCESS
  ID: PRC(442.7,
GLOBAL REFERENCE: PRC(442.7,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TYPE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442.7,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: TEXT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   
  The Advanced Prosthetics Acquisition Tool (APAT) requests read access to 
  the ADMINISTRATIVE CERTIFICATIONS File (#442.7) when displaying the 
  Administrative Certifications on the detailed purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6605                            IA #: 6605
  FILE NUMBER: 442.8                    GLOBAL ROOT: PRC(442.8,
  DATE CREATED: NOV 04, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DELIVERY SCHEDULE (ORDER) FILE ACCESS
  ID: PRC(442.8,
GLOBAL REFERENCE: PRC(442.8,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ORDER NUMBER (PAT)
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ITEM
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DELIVERY DATE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: LOCATION FOR DELIVERY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: QUANTITY TO BE DELIVERED
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: DELETE FLAG
  LOCATION: 0;6                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442.8,'B'
 GLOBAL DESCRIPTION:   'B' cross reference  Used to look up by ORDER NUMBER 
 GENERAL DESCRIPTION:   
  The Advanced Prosthetics Acquisition Tool (APAT) requests read access to 
  the DELIVERY SCHEDULE (ORDER) file (#442.8) when displaying the delivery 
  schedule on a purchase order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUL 02, 2019

NUMBER: 6606                            IA #: 6606
  DATE CREATED: NOV 09, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: VAFHPIVT                     NAME: VAFHPIVT
  ID: VAFHPIVT
 GENERAL DESCRIPTION:   For the Pharmacy Interface Automation Project (PIA), it
 is necessary to send the Pivot number assigned to an admission in the HL7
 message. This helps vendors subscribing to these messages to uniquely identify
 patient movements that are related to admission/transfer/discharge.  
  
 Inpatient Medications is requesting to use the call $$PIVCHK^VAFHPIVT, which
 returns the Pivot number assigned to a particular admission. 
  STATUS: Pending
KEYWORDS: PIVOT
COMPONENT/ENTRY POINT: $$PIVCHK
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number of the patient.  
VARIABLES: EVDT                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the admission date & time.  
VARIABLES: EVTY                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the event type - in our case it would be 1.  
VARIABLES: PTR                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the pointer to the Patient Movement file
 (#405), concatenated with "DGPM(", the global namespace.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS

NUMBER: 6607                            IA #: 6607
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: NOV 09, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SC PERCENTAGE
  ID: DPT(
GLOBAL REFERENCE: DPT(D0,.3
FIELD NUMBER: .302                      FIELD NAME: SERVICE CONNECTED PERCENTAGE
  LOCATION: .3;2                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VIA needs to read the SERVICE CONNECTED PERCENTAGE
 (#.302) field in the PATIENT (#2) file to provide data to consuming
 applications via the remote procedure call, VIAB BMS RPC.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SERVICE CONNECTED
KEYWORDS: PERCENTAGE
KEYWORDS: VIAB
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
  DATE ACTIVATED: NOV 09, 2016

NUMBER: 6608                            IA #: 6608
  FILE NUMBER: 420                      GLOBAL ROOT: PRC(420,
  DATE CREATED: NOV 10, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FUND CONTROL POINT FILE ACCESS
  ID: PRC(420,
GLOBAL REFERENCE: PRC(420,D0,0)
FIELD NUMBER: .01                       FIELD NAME: STATION NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: STATION OVERCOMMIT SWITCH
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: SUPPLY FUND CAP
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: INVENTORY VALUE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: DUE-IN VALUE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: TOTAL CAP AVAILABLE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: PRINT IN DEMAND
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 3.1                       FIELD NAME: STATION ROLLOVER OF EOQ BAL
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: STATION OPEN QUARTER DATE
  LOCATION: 0;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(420,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CONTROL POINT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: FUND
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: APPROPRIATION SYMBOL
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PROGRAM.LIMITATION.ANALYSIS
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: STATUS OF FUNDS BALANCE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: ESTIMATED BALANCE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 12
  FIELD NAME: ALLOW ACCESS BY ALL REQUESTORS
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: .5                        FIELD NAME: CONTROLLING SERVICE
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: AUTOMATED
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: SPECIAL CONTROL POINT
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: CP OVERCOMMIT SWITCH
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: ITEM DELIVERY POINTS
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 16                        FIELD NAME: OVERCOMMIT 1358 PERMITTED
  LOCATION: 0;15                        ACCESS: Read w/Fileman
FIELD NUMBER: 18                        FIELD NAME: DIETETICS SUBS/SUPPLIES
  LOCATION: 0;17                        ACCESS: Read w/Fileman
FIELD NUMBER: 19                        FIELD NAME: LOG DEPARTMENT
  LOCATION: 0;18                        ACCESS: Read w/Fileman
FIELD NUMBER: 20                        FIELD NAME: ACTIVE/INACTIVE
  LOCATION: 0;19                        ACCESS: Read w/Fileman
FIELD NUMBER: 21                        FIELD NAME: ROLLOVER OF EOQ BALANCE
  LOCATION: 0;20                        ACCESS: Read w/Fileman
FIELD NUMBER: 22                        FIELD NAME: ROLLOVER CONTROL POINT
  LOCATION: 0;21                        ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: DEACTIVATED BY
  LOCATION: 0;23                        ACCESS: Read w/Fileman
FIELD NUMBER: 24                        FIELD NAME: DATE/TIME DEACTIVATED
  LOCATION: 0;24                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(420,D0,1,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: CONTROL POINT USER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: LEVEL OF ACCESS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: NOTIFICATION DESIGNEE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(420,D0,1,D1,1,D2,2)
FIELD NUMBER: 2                         FIELD NAME: RECEIVE FMS RECONCILIATION
  LOCATION: 2;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(420,D0,1,D1,2,D2,0)
FIELD NUMBER: .01                       FIELD NAME: COST CENTER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(420,D0,1,D1,3,D2,0)
FIELD NUMBER: .01                       FIELD NAME: CONTROL POINT DESCRIPTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(420,D0,1,D1,4,D2,0)
FIELD NUMBER: .01                       FIELD NAME: FISCAL YEAR
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: 1QTR UNCOMMITTED BALANCE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: 2QTR UNCOMMITTED BALANCE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: 3QTR UNCOMMITTED BALANCE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: 4QTR UNCOMMITTED BALANCE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: 1QTR UNOBLIGATED BALANCE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: 2QTR UNOBLIGATED BALANCE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: 3QTR UNOBLIGATED BALANCE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: 4QTR UNOBLIGATED BALANCE
  LOCATION: 0;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(420,D0,1,D1,4,D2,1)
FIELD NUMBER: 9                         FIELD NAME: 1QTR SCP UNCOMMITTED BALANCE
  LOCATION: 1;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: 2QTR SCP UNCOMMITTED BALANCE
  LOCATION: 1;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: 3QTR SCP UNCOMMITTED BALANCE
  LOCATION: 1;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: 4QTR SCP UNCOMMITTED BALANCE
  LOCATION: 1;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(420,D0,1,D1,4,D2,2)
FIELD NUMBER: 13                        FIELD NAME: FY FCP CODE
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: FY FCP NAME
  LOCATION: 2;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 15                        FIELD NAME: FY ALD/FUND CODE
  LOCATION: 2;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 16                        FIELD NAME: FY A/O
  LOCATION: 2;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 17                        FIELD NAME: FY PROGRAM
  LOCATION: 2;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 18                        FIELD NAME: FY FCP/PRJ
  LOCATION: 2;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 19                        FIELD NAME: FY OBJECT CLASS
  LOCATION: 2;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 20                        FIELD NAME: FY JOB
  LOCATION: 2;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 21                        FIELD NAME: FY APPROPRIATION SYMBOL
  LOCATION: 2;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 22                        FIELD NAME: FY FUND CODE
  LOCATION: 2;10                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(420,D0,1,D1,5)
FIELD NUMBER: 25                        FIELD NAME: FUND CODE TEXT
  LOCATION: 5;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 26                        FIELD NAME: PROGRAM
  LOCATION: 5;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 27                        FIELD NAME: FCP/PRJ
  LOCATION: 5;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 28                        FIELD NAME: OBJECT CLASS
  LOCATION: 5;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 25.5                      FIELD NAME: ADMINISTRATIVE OFFICE
  LOCATION: 5;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 29                        FIELD NAME: JOB
  LOCATION: 5;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 30                        FIELD NAME: LAST ROLLOVER QUARTER DATE
  LOCATION: 5;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 25.2                      FIELD NAME: BEGINNING BUDGET FISCAL YEAR
  LOCATION: 5;8                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(420,D0,1,D1,6)
FIELD NUMBER: 31                        FIELD NAME: EDI AUTO RELEASE
  LOCATION: 6;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 32
  FIELD NAME: FCP ALL/DELIVERY ORDER SWITCH
  LOCATION: 6;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(420,D0,1,D1,7,D2,0)
FIELD NUMBER: .01                       FIELD NAME: INVENTORY POINT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(420,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: FUND RELEASING OFFICIAL
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(420,D0,3)
FIELD NUMBER: 10                        FIELD NAME: EDI ORDER RELEASE
  LOCATION: 3;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 11
  FIELD NAME: SITE ALL/DELIVERY ORDER SWITCH
  LOCATION: 3;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(420,'AE'
 GLOBAL DESCRIPTION:   File 420 "AE" cross-reference  Used to look up
 associated Control Point based on station and inventory point 
GLOBAL REFERENCE: PRC(420,'C'
 GLOBAL DESCRIPTION:   File 420 'C' cross-reference  Used to look up user's
 entry specifying the user's role and permissions for a given control point of
 that station 
GLOBAL REFERENCE: PRC(420,D0,1,D1,7,'B'
 GLOBAL DESCRIPTION:   File 420.07 'B' cross-reference  Used to look up primary
 and warehouse inventory points associated with a given control point of the
 specified station 
 GENERAL DESCRIPTION:   Above PAR and the Advanced Prosthetics Acquisition Tool
 (APAT) request READ access to the FUND CONTROL POINT FILE #420.  
  
 Above PAR Ad-Hoc Reporting includes the FUND CONTROL POINT FILE #420.  Ad-Hoc
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6609                            IA #: 6609
  FILE NUMBER: 42                       GLOBAL ROOT: DIC(42,
  DATE CREATED: NOV 10, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: WARD
  ID: DIC(42,
GLOBAL REFERENCE: DIC(42,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 0.17                      FIELD NAME: SPECIALTY
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: .2                        FIELD NAME: CURRENTLY OUT-OF-SERVICE?
  ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VIA needs to read fields from the WARD LOCATION (#42)
 file to provide data to consuming applications via the remote procedure call,
 VIAB BMS RPC.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: WARD
KEYWORDS: VIA
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
  DATE ACTIVATED: NOV 10, 2016

NUMBER: 6610                            IA #: 6610
  FILE NUMBER: 405.1                    GLOBAL ROOT: DG(405.1,
  DATE CREATED: NOV 10, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FACILITY MOVEMENT TYPE
  ID: DG(405.1,
GLOBAL REFERENCE: DG(405.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: FACILITY MOVEMENT TYPE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VIA needs to read fields from the FACILITY MOVEMENT
 TYPE (#405.1) file to provide data to consuming applications via the remote
 procedure call, VIAB BMS RPC.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FACILITY
KEYWORDS: MOVEMENT
KEYWORDS: VIA
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
  DATE ACTIVATED: NOV 10, 2016

NUMBER: 6611                            IA #: 6611
  FILE NUMBER: 41.1                     GLOBAL ROOT: DGS(41.1,
  DATE CREATED: NOV 10, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SCHEDULED ADMISSION
  ID: DGS(41.1,
GLOBAL REFERENCE: DGS(41.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
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: 11                        FIELD NAME: PERSON SCHEDULING ADMIT
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: DIVISION
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: DATE/TIME CANCELLED
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: CANCELLED BY
  LOCATION: 0;14                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VIA needs to read fields from the SCHEDULED ADMISSION
 (#41.1) file to provide data to consuming applications via the remote
 procedure call, VIAB BMS RPC.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SCHEDULE
KEYWORDS: ADMISSION
KEYWORDS: VIA
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
  DATE ACTIVATED: NOV 10, 2016

NUMBER: 6612                            IA #: 6612
  FILE NUMBER: 405.4                    GLOBAL ROOT: DG(405.4,
  DATE CREATED: NOV 10, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ROOM-BED
  ID: DG(405.4,
GLOBAL REFERENCE: DG(405.4,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .2                        FIELD NAME: CURRENTLY OUT-OF-SERVICE?
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: DG(405.4,D0,'W',D1,0)
FIELD NUMBER: .01                       FIELD NAME: WARD(S) WHICH CAN ASSIGN
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VIA needs to read fields from the ROOM-BED (#405.4)
 file to provide data to consuming applications via the remote procedure call,
 VIAB BMS RPC.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ROOM
KEYWORDS: BED
KEYWORDS: VIA
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
  DATE ACTIVATED: NOV 10, 2016

NUMBER: 6613                            IA #: 6613
  FILE NUMBER: 405                      GLOBAL ROOT: DGPM(
  DATE CREATED: NOV 10, 2016            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PATIENT MOVEMENT
  ID: DGPM(
GLOBAL REFERENCE: DGPM(D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: TRANSACTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: PATIENT
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: TYPE OF MOVEMENT
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: WARD LOCATION
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: ROOM-BED
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: .14                       FIELD NAME: ADMISSION/CHECK-IN MOVEMENT
  LOCATION: 0;14                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: DGPM(D0,USR)
FIELD NUMBER: 100                       FIELD NAME: ENTERED BY
  LOCATION: USR;1                       ACCESS: Read w/Fileman
FIELD NUMBER: 101                       FIELD NAME: ENTERED ON
  LOCATION: USR;2                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VIA needs to read fields from the PATIENT MOVEMENT
 (#405) file to provide data to consuming applications via the remote procedure
 call, VIAB BMS RPC.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PATIENT
KEYWORDS: MOVEMENT
KEYWORDS: ADMISSION
KEYWORDS: BED
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
  DATE ACTIVATED: NOV 10, 2016

NUMBER: 6614                            IA #: 6614
  DATE CREATED: NOV 15, 2016
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWPCE PCE4NOTE
  REMOTE PROCEDURE: ORWPCE PCE4NOTE
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  
  
 HMP calls the ORWPCE PCE4NOTE RPC to retrieve encounter information for an
 associated note in the format: 
  
  LST(1)=HDR^AllowEdit^CPTRequired^VStr^Author^hasCPT 
  LST(n)=TYP+^CODE^CAT^NARR^QUAL1^QUAL2 (QUAL1=Primary!Qty, QUAL2=Prv) 
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: ORWPCE
KEYWORDS: PCE4NOTE
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: OCT 12, 2017

NUMBER: 6615                            IA #: 6615
  FILE NUMBER: 410.1                    GLOBAL ROOT: PRCS(410.1,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TRANSACTION NUMBER FILE ACCESS
  ID: PRCS(410.1,
GLOBAL REFERENCE: PRCS(410.1,D0,0)
FIELD NUMBER: 1                         FIELD NAME: COUNTER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410.1,'B'
 GLOBAL DESCRIPTION:   File 410.1 "B" cross-reference  Used to look up by
 STA-FY-FCP, 
                                 STA-PAT#, OR STA-FY-QTR-FCP-CC 
 GENERAL DESCRIPTION:   
     The Advanced Prosthetics Acquisition Tool (APAT) checks for new 
     transaction number availability for detailed purchase card orders.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6616                            IA #: 6616
  FILE NUMBER: 410.8                    GLOBAL ROOT: PRCS(410.8,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  NAME: DELIVERY POINT FILE ACCESS      ID: PRCS(410.8,
GLOBAL REFERENCE: PRCS(410.8,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   
     The Advanced Prosthetics Acquisition Tool (APAT) pulls data from 
     the DELIVERY POINT (#410.8) file for reporting on detailed purchase 
     card orders.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL

NUMBER: 6617                            IA #: 6617
  FILE NUMBER: 410.7                    GLOBAL ROOT: PRCS(410.7,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SORT GROUP FILE ACCESS
  ID: PRCS(410.7,
GLOBAL REFERENCE: PRCS(410.7,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: CONTROL POINT NUMBER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
     The Advanced Prosthetics Acquisition Tool (APAT) requests read access 
     to the SORT GROUP (#410.7) file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6618                            IA #: 6618
  FILE NUMBER: 410.4                    GLOBAL ROOT: PRCS(410.4,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  NAME: SUB-CONTROL POINT FILE ACCESS   ID: PRCS(410.4,
GLOBAL REFERENCE: PRCS(410.4,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: CONTROL POINT NUMBER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410.4,'B'
 GLOBAL DESCRIPTION:   File 410.4 'B' cross reference  Used to look up by
 Sub-control 
                                 point NAME 
 GENERAL DESCRIPTION:   
     The Advanced Prosthetics Acquisition Tool (APAT)  pulls data from 
     file SUB-CONTROL POINT (#410.4) when creating detailed purchase card 
     orders.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL

NUMBER: 6619                            IA #: 6619
  FILE NUMBER: 410.2                    GLOBAL ROOT: PRCS(410.2,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: CLASSIFICATION OF REQUEST FILE ACCESS
  ID: PRCS(410.2,
GLOBAL REFERENCE: PRCS(410.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: CONTROL POINT NUMBER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410.2,'B'
 GLOBAL DESCRIPTION:   File 410.2 'B' cross reference  Used to look up by
 CLASSIFICATION OF 
                                 REQUEST NAME 
 GENERAL DESCRIPTION:   
     The Advanced Prosthetics Acquisition Tool (APAT) requests read access 
     to the CLASSIFICATION OF REQUEST File (#410.2).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6620                            IA #: 6620
  FILE NUMBER: 445.8                    GLOBAL ROOT: PRCP(445.8,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INSTRUMENT KITS FILE ACCESS
  ID: PRCP(445.8,
GLOBAL REFERENCE: PRCP(445.8,D0,0)
FIELD NUMBER: .01                       FIELD NAME: INSTRUMENT KIT ITEM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: INVENTORY POINT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: USER CREATING INSTRUMENT KIT
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: DATE CREATED
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: USER LAST EDIT
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: DATE LAST EDIT
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: METHOD OF STERILIZATION
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: METHOD OF WRAPPING/PACKAGING
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: TOTAL ASSEMBLY CHARGE
  LOCATION: 0;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(445.8,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ITEMS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: QUANTITY NEEDED
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: PRINT SEQUENCE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(445.8,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SPECIAL INSTRUCTIONS/REMARKS
  ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(445.8,'B'
 GLOBAL DESCRIPTION:   Cross Reference 'B' used to lookup by INSTRUMENT KIT
 ITEM 
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT) and
 ABOVE PAR determine whether a given INSTRUMENT KIT exists within the
 INSTRUMENT KITS FILE #445.8.  
  
 Above PAR Ad-Hoc Reporting includes the INSTRUMENT KITS FILE #445.8.  Ad-Hoc
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUL 02, 2019

NUMBER: 6621                            IA #: 6621
  FILE NUMBER: 445.7                    GLOBAL ROOT: PRCP(445.7,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CASE CARTS FILE ACCESS
  ID: PRCP(445.7,
GLOBAL REFERENCE: PRCP(445.7,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CASE CART ITEM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: INVENTORY POINT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: USER CREATING CASE CART
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: DATE CREATED
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: USER LAST EDIT
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: DATE LAST EDIT
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: TOTAL ASSEMBLY CHARGE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(445.7,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ITEMS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: QUANTITY NEEDED
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(445.7,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SPECIAL INSTRUCTIONS/REMARKS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(445.7,D0,3,D1,0)
FIELD NUMBER: .01                       FIELD NAME: OPERATION CODES
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(445.7,'B'
 GLOBAL DESCRIPTION:   Cross reference 'B' used to lookup by CASE CART ITEM.  
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT) and
 ABOVE PAR request read access to the CASE CARTS FILE #445.7 in order to 
 determine whether a given Case Cart exists.  
  
 Above PAR Ad-Hoc Reporting includes the CASE CARTS FILE #445.7. Ad-Hoc 
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6622                            IA #: 6622
  FILE NUMBER: 420.6                    GLOBAL ROOT: PRCD(420.6,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CODE INDEX FILE ACCESS
  ID: PRCD(420.6,
GLOBAL REFERENCE: PRCD(420.6,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: CODE INDEX
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: EFFECTIVE DATE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: SHORT DESC.
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: DISPLAY
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: APPLICABLE BUS. TYPE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   
     The Advanced Prosthetics Acquisition Tool (APAT) requests read access 
     to the CODE INDEX File (#420.6).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUL 02, 2019

NUMBER: 6623                            IA #: 6623
  FILE NUMBER: 420.54                   GLOBAL ROOT: PRCD(420.54,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: EVALUATED PREFERENCE FILE ACCESS
  ID: PRCD(420.54,
GLOBAL REFERENCE: PRCD(420.54,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  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: DESCRIPTION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCD(420.54,'B'
 GLOBAL DESCRIPTION:   File 420.54 'B' cross-reference  Used to look up by
 EVALUATED PREFERENCE 
                                  CODE 
 GENERAL DESCRIPTION:   
     The Advanced Prosthetics Acquisition Tool (APAT) requests read access 
     to the EVALUATED PREFERENCE File (#420.54).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6624                            IA #: 6624
  FILE NUMBER: 420.53                   GLOBAL ROOT: PRCD(420.53,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: EXTENT COMPETED FILE ACCESS
  ID: PRCD(420.53,
GLOBAL REFERENCE: PRCD(420.53,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  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: DESCRIPTION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCD(420.53,'B'
 GLOBAL DESCRIPTION:   File 420.53 'B' cross reference  Used to look up by
 EXTENT COMPETED CODE 
 GENERAL DESCRIPTION:   
     The Advanced Prosthetics Acquisition Tool (APAT) requests read access 
     to the EXTENT COMPETED File (#420.53).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 12, 2019

NUMBER: 6625                            IA #: 6625
  FILE NUMBER: 420.52                   GLOBAL ROOT: PRCD(420.52,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SOLICITATION PROCEDURE FILE ACCESS
  ID: PRCD(420.52,
GLOBAL REFERENCE: PRCD(420.52,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  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: DESCRIPTION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCD(420.52,'B'
 GLOBAL DESCRIPTION:   File 420.52 "B" cross reference  Used to look up by
 SOLICITATION PROCEDURE 
                                  CODE 
 GENERAL DESCRIPTION:   
     The Advanced Prosthetics Acquisition Tool (APAT) requests read access 
     to the SOLICITATION PROCEDURE File (#420.52).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 12, 2019

NUMBER: 6626                            IA #: 6626
  FILE NUMBER: 420.51                   GLOBAL ROOT: PRCD(420.51,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: REASON NOT COMPETED FILE ACCESS
  ID: PRCD(420.51,
GLOBAL REFERENCE: PRCD(420.51,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  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: DESCRIPTION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCD(420.51,'B'
 GLOBAL DESCRIPTION:   File 420.51 "B" cross reference  Used to look up by
 REASON NOT COMPETED 
                                  CODE 
 GENERAL DESCRIPTION:   
     The Advanced Prosthetics Acquisition Tool (APAT) requests read access 
     to the REASON NOT COMPETED file (#420.51).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 12, 2019

NUMBER: 6627                            IA #: 6627
  FILE NUMBER: 440.5                    GLOBAL ROOT: PRC(440.5,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PURCHASE CARD INFORMATION FILE ACCESS
  ID: PRC(440.5,
GLOBAL REFERENCE: PRC(440.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PURCHASE CARD NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: FUND CONTROL POINT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: COST CENTER
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: BUDGET OBJECT CODE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4
  FIELD NAME: PC USER SINGLE PURCHASE LIMIT
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: MONTHLY PURCHASE LIMIT
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: DELIVERY LOCATION
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: CARD HOLDER
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: APPROVING OFFICIAL
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: ALTERNATE APPROVING OFFICIAL
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: PURCHASE CARD NAME
  LOCATION: 0;11                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(440.5,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SURROGATE USER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(440.5,D0,2)
FIELD NUMBER: 13                        FIELD NAME: MONTHLY PURCHASES
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: INACTIVATE CARD?
  LOCATION: 2;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 15                        FIELD NAME: STATION NUMBER
  LOCATION: 2;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 16                        FIELD NAME: EXPIRATION DATE
  LOCATION: 2;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(440.5,D0,50)
FIELD NUMBER: 51                        FIELD NAME: E REPLACED CARD NUMBER
  LOCATION: 50;1                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(440.5,'ARPC'
 GLOBAL DESCRIPTION:   File 440.5 'ARPC' index  Used to look up by E REPLACED 
                          CARD NUMBER 
GLOBAL REFERENCE: PRC(440.5,'B'
 GLOBAL DESCRIPTION:   File 440.5 'B' cross reference  Used to look up by 
                                 PURCHASE CARD NUMBER 
GLOBAL REFERENCE: PRC(440.5,'C'
 GLOBAL DESCRIPTION:   File 440.5 'C' cross reference  Used to look up by 
                                 SURROGATE USER 
GLOBAL REFERENCE: PRC(440.5,'D'
 GLOBAL DESCRIPTION:   File 440.5 'D' cross reference  Used to look up by 
                                 PURCHASE CARD NUMBER 
GLOBAL REFERENCE: PRC(440.5,'E'
 GLOBAL DESCRIPTION:   File 440.5 'E' cross reference  Used to look up by 
                                 APPROVING OFFICIAL 
GLOBAL REFERENCE: PRC(440.5,'F'
 GLOBAL DESCRIPTION:   File 440.5 'F' cross reference  Used to look up by 
                                 ALTERNATE APPROVING OFFICIAL 
GLOBAL REFERENCE: PRC(440.5,'H'
 GLOBAL DESCRIPTION:   File 440.5 'H' cross reference  Used to look up by 
                                 CARD HOLDER 
 GENERAL DESCRIPTION:   
        Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) 
        request READ access to specific fields of the Purchase Card 
        Information file (#440.5).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: NOV 21, 2018

NUMBER: 6628                            IA #: 6628
  FILE NUMBER: 442                      GLOBAL ROOT: PRC(442,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PROCUREMENT & ACCOUNTING TRANSACTIONS FILE ACCESS
  ID: PRC(442,
GLOBAL REFERENCE: PRC(442,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PURCHASE ORDER NUMBER
  LOCATION: 0;1
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: METHOD OF PROCESSING
  LOCATION: 0;2
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: FCP
  LOCATION: 0;3
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 1.4                       FIELD NAME: APPROPRIATION
  LOCATION: 0;4
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: COST CENTER
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: SUBACCOUNT1
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 3.4                       FIELD NAME: SUBAMOUNT1
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: SUBACCOUNT2
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 4.4                       FIELD NAME: SUBAMOUNT2
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: DELIVERY DATE
  LOCATION: 0;10
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 7.2                       FIELD NAME: ESTIMATED COST
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: PRIMARY 2237
  LOCATION: 0;12
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 13
  FIELD NAME: EST. SHIPPING AND/OR HANDLING
  LOCATION: 0;13
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 15                        FIELD NAME: LINE ITEM COUNT
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 91                        FIELD NAME: TOTAL AMOUNT
  LOCATION: 0;15
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 92                        FIELD NAME: NET AMOUNT
  LOCATION: 0;16                        ACCESS: Read w/Fileman
FIELD NUMBER: 93                        FIELD NAME: LIQUIDATED AMOUNT
  LOCATION: 0;17                        ACCESS: Read w/Fileman
FIELD NUMBER: 13.1                      FIELD NAME: EST. SHIPPING LINE ITEM NO.
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: SPECIAL FUND CONTROL POINT
  LOCATION: 0;19                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6.9                       FIELD NAME: ORIGINAL DELIVERY DATE
  LOCATION: 0;20                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,1)
FIELD NUMBER: 5                         FIELD NAME: VENDOR
  LOCATION: 1;1
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 5.2                       FIELD NAME: REQUESTING SERVICE
  LOCATION: 1;2
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 5.4                       FIELD NAME: SHIP TO
  LOCATION: 1;3
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: VERBAL PURCHASE ORDER (Y/N)
  LOCATION: 1;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 6.2                       FIELD NAME: CONFIRMATION COPY (Y/N)
  LOCATION: 1;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 6.4                       FIELD NAME: F.O.B. POINT
  LOCATION: 1;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8                         FIELD NAME: SOURCE CODE
  LOCATION: 1;7
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 8.2                       FIELD NAME: PROPOSAL
  LOCATION: 1;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: PRIORITY OF 2237
  LOCATION: 1;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 16                        FIELD NAME: PA/PPM/AUTHORIZED USER
  LOCATION: 1;10
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 5.6                       FIELD NAME: DELIVERY LOCATION
  LOCATION: 1;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.3                       FIELD NAME: DIRECT DELIVERY PATIENT
  LOCATION: 1;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: DEPOT VOUCHER NO.
  LOCATION: 1;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 8.1                       FIELD NAME: ASTR. FOR SOURCE CODE
  LOCATION: 1;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .1                        FIELD NAME: P.O. DATE
  LOCATION: 1;15
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 5.1                       FIELD NAME: DEBTOR
  LOCATION: 1;16                        ACCESS: Read w/Fileman
FIELD NUMBER: .2                        FIELD NAME: EMERGENCY ORDER?
  LOCATION: 1;17                        ACCESS: Read w/Fileman
FIELD NUMBER: .3                        FIELD NAME: EXPENDABLE/NONEXPENDABLE
  LOCATION: 1;18                        ACCESS: Read w/Fileman
FIELD NUMBER: .25
  FIELD NAME: LOCAL PROCUREMENT REASON CODE
  LOCATION: 1;19                        ACCESS: Read w/Fileman
FIELD NUMBER: 501                       FIELD NAME: CERTIFIED P.O.
  LOCATION: 1;20                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: LINE ITEM NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: QUANTITY
  LOCATION: 0;2
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: UNIT OF PURCHASE
  LOCATION: 0;3
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 3.5                       FIELD NAME: BOC
  LOCATION: 0;4
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 1.5                       FIELD NAME: ITEM MASTER FILE NO.
  LOCATION: 0;5
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: VENDOR STOCK NUMBER
  LOCATION: 0;6
  ACCESS: Direct Global Read & R/W 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: 5                         FIELD NAME: ACTUAL UNIT COST
  LOCATION: 0;9
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: 2237 REFERENCE #
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 3.6                       FIELD NAME: INTERMEDIATE PRODUCT CODE
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 3.1                       FIELD NAME: PACKAGING MULTIPLE
  LOCATION: 0;12
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 9.5                       FIELD NAME: NSN
  LOCATION: 0;13
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 9.6                       FIELD NAME: MAXIMUM ORDER QTY
  LOCATION: 0;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9.3                       FIELD NAME: NATIONAL DRUG CODE
  LOCATION: 0;15                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9.4                       FIELD NAME: SKU
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9.7                       FIELD NAME: UNIT CONVERSION FACTOR
  LOCATION: 0;17                        ACCESS: Both R/W 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: 15                        FIELD NAME: TOTAL COST
  LOCATION: 2;1
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: CONTRACT/BOA #
  LOCATION: 2;2
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 8
  FIELD NAME: FEDERAL SUPPLY CLASSIFICATION
  LOCATION: 2;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: DESCRIPTION LINE COUNT
  LOCATION: 2;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7                         FIELD NAME: DESCRIPT. ASTR.
  LOCATION: 2;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16                        FIELD NAME: DISCOUNTED AMOUNT
  LOCATION: 2;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17                        FIELD NAME: OBLIGATED SUBACCOUNT
  LOCATION: 2;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11                        FIELD NAME: QUANTITY PREVIOUSLY RECEIVED
  LOCATION: 2;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 12                        FIELD NAME: EDI STATUS CODE 1
  LOCATION: 2;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 12.5                      FIELD NAME: EDI STATUS QTY 1
  LOCATION: 2;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: EDI STATUS CODE 2
  LOCATION: 2;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 13.5                      FIELD NAME: EDIT STATUS QTY 2
  LOCATION: 2;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 43                        FIELD NAME: 410 ITEM NUMBER
  LOCATION: 2;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 44                        FIELD NAME: HAZARDOUS MATERIAL
  LOCATION: 2;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 48                        FIELD NAME: DM DOC ID
  LOCATION: 2;15                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,2,D1,3,D2,0)
FIELD NUMBER: .01                       FIELD NAME: DATE RECEIVED
  LOCATION: 0;1
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: QTY BEING RECEIVED
  LOCATION: 0;2
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: AMOUNT
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: DISCOUNTED AMOUNT
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: RECEIVING CODE SHEET NO.
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: ADJUSTED QUANTITY RECEIVED
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: ADJUSTED AMOUNT
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PARTIAL NUMBER
  LOCATION: 0;4
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: PRC(442,D0,2,D1,4)
FIELD NUMBER: 30                        FIELD NAME: SERIAL NO.(GSA/DLA)
  LOCATION: 4;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: CONSUMER LEVEL
  LOCATION: 4;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 32                        FIELD NAME: CONSUMER LEVEL OVERRIDE
  LOCATION: 4;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 33                        FIELD NAME: DO NOT SUB
  LOCATION: 4;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 34                        FIELD NAME: DO NOT B/O
  LOCATION: 4;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 35                        FIELD NAME: BACKORDER CONTROL
  LOCATION: 4;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 36                        FIELD NAME: SUBSTITUTE CONTROL
  LOCATION: 4;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 37                        FIELD NAME: ACQUISITIONS CODE SHEET NO.
  LOCATION: 4;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 38                        FIELD NAME: GROUP SPLIT CIV
  LOCATION: 4;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 39                        FIELD NAME: SOURCE CODE
  LOCATION: 4;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 40                        FIELD NAME: DRUG TYPE CODE
  LOCATION: 4;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 41                        FIELD NAME: FOOD GROUP
  LOCATION: 4;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 42                        FIELD NAME: DIETETIC CONVERSION FACTOR
  LOCATION: 4;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 39.5                      FIELD NAME: SOURCE DEVIATION
  LOCATION: 4;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 36.3                      FIELD NAME: BACKORDER (EDI)
  LOCATION: 4;15                        ACCESS: Read w/Fileman
FIELD NUMBER: 36.6                      FIELD NAME: SUBSTITUTE (EDI)
  LOCATION: 4;16                        ACCESS: Read w/Fileman
FIELD NUMBER: 45                        FIELD NAME: LOT NUMBER
  LOCATION: 4;17                        ACCESS: Read w/Fileman
FIELD NUMBER: 46                        FIELD NAME: SERIAL NUMBER
  LOCATION: 4;18                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,2,D1,5,D2,0)
FIELD NUMBER: .01                       FIELD NAME: LINE INVENTORY POINT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: LINE QUANTITY
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: LINE DELIVERY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: QUANTITY RECEIVED TO DATE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,3,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DISCOUNT ITEM
  LOCATION: 0;1
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PERCENT/DOLLAR AMOUNT
  LOCATION: 0;2
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DISCOUNT AMOUNT
  LOCATION: 0;3
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: ITEM COUNT
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: CONTRACT #
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: LINE ITEM
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(442,D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: COMMENTS
  LOCATION: 0;1
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: PRC(442,D0,5,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PROMPT PAYMENT PERCENT
  LOCATION: 0;1
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DAYS (TERM)
  LOCATION: 0;2
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: CONTRACT #
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: ASTR.
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(442,D0,6,D1,0)
FIELD NUMBER: .01                       FIELD NAME: AMENDMENT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: EFFECTIVE DATE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: AMOUNT CHANGED
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: AUTHORITY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: CONTRACTOR REQUIRED TO SIGN?
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5.2                       FIELD NAME: NUMBER OF COPIES
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: TYPE OF COMMENTS
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: ADJUSTMENT VOUCHER
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 7.5                       FIELD NAME: VALIDATION VERSION
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 7.7                       FIELD NAME: ESIG CODE
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 11.5                      FIELD NAME: FISCAL VALIDATION VERSION
  LOCATION: 0;11                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,6,D1,1)
FIELD NUMBER: 6                         FIELD NAME: PA/PPM/AUTHORIZED BUYER
  LOCATION: 1;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: VALIDATION CODE
  LOCATION: 1;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: DATE SIGNED
  LOCATION: 1;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: AMENDMENT/ADJUSTMENT STATUS
  LOCATION: 1;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: FISCAL APPROVED BY
  LOCATION: 1;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: FISCAL VALIDATION CODE
  LOCATION: 1;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 11.7                      FIELD NAME: FISCAL ESIG CODE
  LOCATION: 1.7                         ACCESS: Read w/Fileman
FIELD NUMBER: 11.8                      FIELD NAME: FISCAL VALIDATION DATE
  LOCATION: 1;8                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,6,D1,2,D2,0)
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,6,D1,3,D2,0)
FIELD NUMBER: .01                       FIELD NAME: CHANGES
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: AMENDMENT TYPE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: FIELD & FILE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: SUBRECORD ENTRY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: DATE & TIME ENTERED
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: USER
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: OTHER FILE NUMBER
  LOCATION: 0;7                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,6,D1,3,D2,1,D3,0)
FIELD NUMBER: .01                       FIELD NAME: OLD DATA VALUE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,6,D1,4)
FIELD NUMBER: 16                        FIELD NAME: JUSTIFICATION
  LOCATION: 4;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,7)
FIELD NUMBER: .5                        FIELD NAME: SUPPLY STATUS
  LOCATION: 7;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .7                        FIELD NAME: SUPPLY STATUS ORDER
  LOCATION: 7;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: ESTIMATED ORDER?
  LOCATION: 7;3
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: .8                        FIELD NAME: FISCAL STATUS ORDER
  LOCATION: 7;4                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(442,D0,8)
FIELD NUMBER: 94                        FIELD NAME: ACTUAL 1358 BALANCE
  LOCATION: 8;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 95                        FIELD NAME: FISCAL 1358 BALANCE
  LOCATION: 8;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 96                        FIELD NAME: ESTIMATED 1358 BALANCE
  LOCATION: 8;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 96.6                      FIELD NAME: AUTH. AMOUNT REMAINING
  LOCATION: 8;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 96.7                      FIELD NAME: BULLETIN SENT
  LOCATION: 8;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 96.5                      FIELD NAME: CONVERTED 1358
  LOCATION: 8;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,9,D1,0)
FIELD NUMBER: .01                       FIELD NAME: AMOUNT
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TYPE CODE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: CONTRACT #
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.1                       FIELD NAME: COMP. STATUS/BUSINESS
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.2                       FIELD NAME: PREF. PROGRAM
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(442,D0,9,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: BREAKOUT CODE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(442,D0,10,D1,0)
FIELD NUMBER: .01                       FIELD NAME: TT/DATE/REF
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: OBLIGATED BY
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TRANSACTION AMOUNT
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: CODE SHEET NUMBER
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: VALIDATION CODE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: DATE SIGNED
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 4.5                       FIELD NAME: VALIDATION VERSION
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 4.7                       FIELD NAME: ESIG CODE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: GECS IEN
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: AMENDMENT NUMBER
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: 1358 ADJUSTMENT
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: OBLIGATION PROCESSING DATE
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: ACCOUNTING PERIOD
  LOCATION: 0;13                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,11,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DATE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: SUBACCOUNT1
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: SUBAMOUNT1
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: SUBACCOUNT2
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: SUBAMOUNT2
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: PROCESSED BY FISCAL?
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: WAREHOUSE APPROVED BY
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: VALIDATION CODE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: FINAL
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: OVERAGE
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: WAREHOUSE DATE/TIME SIGNED
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: TOTAL AMOUNT
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: DISCOUNT PERCENT/DAYS
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: LINECOUNT
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 14
  FIELD NAME: RECEIVED BY (PPM OR DELV.PT.)
  LOCATION: 0;15                        ACCESS: Read w/Fileman
FIELD NUMBER: 15                        FIELD NAME: RECEIVED BY VALIDATION CODE
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: DATE RECEIVED (AT DELV.PT.)
  LOCATION: 0;17
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 17
  FIELD NAME: RECEIVED BY (AT DELIVERY PT.)
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 18                        FIELD NAME: RECV.REPORT TRANS.TO AUSTIN
  LOCATION: 0;19                        ACCESS: Read w/Fileman
FIELD NUMBER: 22                        FIELD NAME: FMS BATCH SEQUENCE NUMBER
  LOCATION: 0;20                        ACCESS: Read w/Fileman
FIELD NUMBER: 24                        FIELD NAME: ADJUSTMENT/AMENDMENT NUMBER
  LOCATION: 0;21                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,11,D1,1)
FIELD NUMBER: 19                        FIELD NAME: LOG BATCH NO.(RECEIVING)
  LOCATION: 1;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 20                        FIELD NAME: DIETETIC COST PERIOD
  LOCATION: 1;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 19.3                      FIELD NAME: LOG CODE SHEETS SENT BY
  LOCATION: 1;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 19.4                      FIELD NAME: LOG CODE SH. VALIDATION CODE
  LOCATION: 1;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 19.5                      FIELD NAME: DATE SIGNED
  LOCATION: 1;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 19.2                      FIELD NAME: LOG RR CODE SHEETS DONE?
  LOCATION: 1;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 19.6                      FIELD NAME: RECV.CODE SHEET NO.(DEPOT)
  LOCATION: 1;7                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: SCHEDULED DELIVERY DATE
  LOCATION: 1;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 7.5                       FIELD NAME: VALIDATION VERSION
  LOCATION: 1;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 7.7                       FIELD NAME: ESIG CODE
  LOCATION: 1;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 15.5                      FIELD NAME: RCVD BY VALIDATION VERSION
  LOCATION: 1;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 15.7                      FIELD NAME: RCVD BY ESIG CODE
  LOCATION: 1;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 19.7                      FIELD NAME: LCS VALIDATION VERSION
  LOCATION: 1;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 19.8                      FIELD NAME: LCS ESIG CODE
  LOCATION: 1;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 15.8                      FIELD NAME: RCVD BY VALIDATION DATE/TIME
  LOCATION: 1;15                        ACCESS: Read w/Fileman
FIELD NUMBER: 21                        FIELD NAME: ORIGINAL PARTIAL
  LOCATION: 1;16                        ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: ACCOUNTING PERIOD MONTH/YEAR
  LOCATION: 1;17                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,12)
FIELD NUMBER: 18                        FIELD NAME: PO PRINTED TIME
  LOCATION: 12;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 16.5                      FIELD NAME: VALIDATION CODE
  LOCATION: 12;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 17                        FIELD NAME: VALIDATION DATE/TIME
  LOCATION: 12;3                        ACCESS: Read w/Fileman
FIELD NUMBER: 19                        FIELD NAME: AGENT ASSIGNED P.O.
  LOCATION: 12;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 19.2                      FIELD NAME: DATE P.O. ASSIGNED
  LOCATION: 12;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: INVOICE ADDRESS
  LOCATION: 12;6                        ACCESS: Read w/Fileman
FIELD NUMBER: 13.2                      FIELD NAME: GOV.T B/L NO.
  LOCATION: 12;7                        ACCESS: Read w/Fileman
FIELD NUMBER: 13.3                      FIELD NAME: SHIP VIA
  LOCATION: 12;8                        ACCESS: Read w/Fileman
FIELD NUMBER: 13.4                      FIELD NAME: GBL P.O.NUMBER
  LOCATION: 12;9                        ACCESS: Read w/Fileman
FIELD NUMBER: 18.5                      FIELD NAME: EDI MESSAGE NO.
  LOCATION: 12;10                       ACCESS: Read w/Fileman
FIELD NUMBER: 16.7                      FIELD NAME: VALIDATION VERSION
  LOCATION: 12;11                       ACCESS: Read w/Fileman
FIELD NUMBER: 16.8                      FIELD NAME: ESIG CODE
  LOCATION: 12;12                       ACCESS: Read w/Fileman
FIELD NUMBER: 18.6                      FIELD NAME: NEED SPECIAL HANDLING?
  LOCATION: 12;13                       ACCESS: Read w/Fileman
FIELD NUMBER: 18.7                      FIELD NAME: TYPE OF SPECIAL HANDLING
  LOCATION: 12;14                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 97                        FIELD NAME: PROMPT PAY TYPE
  LOCATION: 12;15                       ACCESS: Read w/Fileman
FIELD NUMBER: 116
  FIELD NAME: DO YOU WANT TO SEND THIS EDI?
  LOCATION: 12;16
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: PRC(442,D0,13,D1,0)
FIELD NUMBER: .01                       FIELD NAME: 2237 REFERENCE NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ACCOUNTABLE OFFICER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: VALIDATION CODE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: DATE SIGNED
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: PURCHASING AGENT
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: DATE ASSIGNED TO PA
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.5                       FIELD NAME: CURRENT STATUS
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: CP FUND STATUS
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: TYPE OF REQUEST
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SOURCE OF REQUEST
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: INVENTORY/DISTRIBUTION POINT
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3.7                       FIELD NAME: ESIG CODE
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 3.5                       FIELD NAME: VALIDATION VERSION
  LOCATION: 0;14                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,14,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PURCHASE METHOD
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,15,D1,0)
FIELD NUMBER: .01
  FIELD NAME: ADMINISTRATIVE CERTIFICATIONS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DESCRIPTION LINE COUNT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,16,D1,0)
FIELD NUMBER: .01                       FIELD NAME: REMARKS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,17)
FIELD NUMBER: 70                        FIELD NAME: DEPARTMENT NUMBER
  LOCATION: 17;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 71                        FIELD NAME: DOCUMENT IDENTIFIER CODE
  LOCATION: 17;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 72                        FIELD NAME: ROUTING INDENTIFIER CODE
  LOCATION: 17;3                        ACCESS: Read w/Fileman
FIELD NUMBER: 73
  FIELD NAME: DEPT.DESIGNATION (DEMAND CODE)
  LOCATION: 17;4                        ACCESS: Read w/Fileman
FIELD NUMBER: 74                        FIELD NAME: SIGNAL CODE
  LOCATION: 17;5                        ACCESS: Read w/Fileman
FIELD NUMBER: 75                        FIELD NAME: FUND CODE
  LOCATION: 17;6                        ACCESS: Read w/Fileman
FIELD NUMBER: 76                        FIELD NAME: DISTRIBUTION CODE (OPTIONAL)
  LOCATION: 17;7                        ACCESS: Read w/Fileman
FIELD NUMBER: 77                        FIELD NAME: PROJECT CODE
  LOCATION: 17;8                        ACCESS: Read w/Fileman
FIELD NUMBER: 78                        FIELD NAME: PRIORITY CODE
  LOCATION: 17;9                        ACCESS: Read w/Fileman
FIELD NUMBER: 79                        FIELD NAME: ADVICE CODE
  LOCATION: 17;10                       ACCESS: Read w/Fileman
FIELD NUMBER: 80                        FIELD NAME: MEDIA & STATUS CODE
  LOCATION: 17;11                       ACCESS: Read w/Fileman
FIELD NUMBER: 83                        FIELD NAME: REASON CODE
  LOCATION: 17;14                       ACCESS: Read w/Fileman
FIELD NUMBER: 72.4                      FIELD NAME: ACTIVITY ADDRESS CODE
  LOCATION: 17;16                       ACCESS: Read w/Fileman
FIELD NUMBER: 73.4                      FIELD NAME: SPECIAL CODE
  LOCATION: 17;17                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,18)
FIELD NUMBER: 107                       FIELD NAME: RELEASING FACILITY NUMBER
  LOCATION: 18;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 101                       FIELD NAME: PAYABLE CODE
  LOCATION: 18;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 102
  FIELD NAME: DOCUMENT IDENTIFIER/COMMON NO.
  LOCATION: 18;3                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 103                       FIELD NAME: LOG BATCH NO.(ACQUISITIONS)
  LOCATION: 18;4                        ACCESS: Read w/Fileman
FIELD NUMBER: 104                       FIELD NAME: LOG CODE SHEETS SENT BY
  LOCATION: 18;5                        ACCESS: Read w/Fileman
FIELD NUMBER: 105                       FIELD NAME: LOG CODE SH. VALIDATION CODE
  LOCATION: 18;6                        ACCESS: Read w/Fileman
FIELD NUMBER: 106                       FIELD NAME: DATE SIGNED
  LOCATION: 18;7                        ACCESS: Read w/Fileman
FIELD NUMBER: 102.5                     FIELD NAME: ISSUE VOUCHER NO.(SUPPLY)
  LOCATION: 18;8                        ACCESS: Read w/Fileman
FIELD NUMBER: 102.6                     FIELD NAME: ISSUE VOUCHER NO.(FISCAL)
  LOCATION: 18;9                        ACCESS: Read w/Fileman
FIELD NUMBER: 102.4                     FIELD NAME: REQUISITION NO.(SUPPLY)
  LOCATION: 18;10                       ACCESS: Read w/Fileman
FIELD NUMBER: 103.5                     FIELD NAME: LOG ACQ.CODE SHEETS DONE?
  LOCATION: 18;11                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 106.4                     FIELD NAME: SUPPLY FUND ORDER OBLIGATED?
  LOCATION: 18;12                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 108                       FIELD NAME: CASCA PROJECT NO.
  LOCATION: 18;13                       ACCESS: Read w/Fileman
FIELD NUMBER: 109                       FIELD NAME: CASCA TRANS TYPE
  LOCATION: 18;14                       ACCESS: Read w/Fileman
FIELD NUMBER: 105.5                     FIELD NAME: LOG CS VALIDATION VERSION
  LOCATION: 18;15                       ACCESS: Read w/Fileman
FIELD NUMBER: 105.7                     FIELD NAME: LOG CS ESIG CODE
  LOCATION: 18;16                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,19,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DELIVERY LOCATIONS/DATES
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,20,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ISMS ORDER NO.
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ORDER HEADER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,21)
FIELD NUMBER: 111                       FIELD NAME: ISMS BATCH NO.
  LOCATION: 21;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 112                       FIELD NAME: ISMS CODE SHEETS DONE?
  LOCATION: 21;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 113                       FIELD NAME: ISMS CODE SHEETS SENT BY
  LOCATION: 21;3                        ACCESS: Read w/Fileman
FIELD NUMBER: 114
  FIELD NAME: ISMS CODE SH. VALIDATION CODE
  LOCATION: 21;4                        ACCESS: Read w/Fileman
FIELD NUMBER: 115                       FIELD NAME: ISMS DATE SIGNED
  LOCATION: 21;5                        ACCESS: Read w/Fileman
FIELD NUMBER: 114.5                     FIELD NAME: ISMS VALIDATION VERSION
  LOCATION: 21;6                        ACCESS: Read w/Fileman
FIELD NUMBER: 114.7                     FIELD NAME: ISMS ESIG CODE
  LOCATION: 21;7                        ACCESS: Read w/Fileman
FIELD NUMBER: 42                        FIELD NAME: RFQ NBR
  LOCATION: 21;8                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,22,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SUBACCOUNT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: SUBAMOUNT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: FMS LINE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PRC(442,D0,23)
FIELD NUMBER: 13.05                     FIELD NAME: EST. SHIPPING BOC
  LOCATION: 23;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 26                        FIELD NAME: BBFY
  LOCATION: 23;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 27                        FIELD NAME: OLD PO RECORD
  LOCATION: 23;3                        ACCESS: Read w/Fileman
FIELD NUMBER: 28                        FIELD NAME: NEW PO RECORD
  LOCATION: 23;4                        ACCESS: Read w/Fileman
FIELD NUMBER: 29                        FIELD NAME: END DATE FOR SERVICE ORDER
  LOCATION: 23;5                        ACCESS: Read w/Fileman
FIELD NUMBER: 30                        FIELD NAME: AUTO ACCRUE
  LOCATION: 23;6                        ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: SUBSTATION
  LOCATION: 23;7
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 46                        FIELD NAME: PURCHASE CARD NUMBER
  LOCATION: 23;8
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 44                        FIELD NAME: DISPUTED
  LOCATION: 23;9                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 47                        FIELD NAME: DELIVERY ORDER
  LOCATION: 23;10                       ACCESS: Read w/Fileman
FIELD NUMBER: 48                        FIELD NAME: TYPE OF ORDER
  LOCATION: 23;11
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 52                        FIELD NAME: CLASSIFICATION OF REQUEST
  LOCATION: 23;12
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 51                        FIELD NAME: SORT GROUP
  LOCATION: 23;13                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 53                        FIELD NAME: PCDO VENDOR
  LOCATION: 23;14                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 54                        FIELD NAME: RECEIVING REQUIRED?
  LOCATION: 23;15
  ACCESS: Direct Global Read & R/W w/Fileman
FIELD NUMBER: 55                        FIELD NAME: PURCHASE CARD EXT. NO.
  LOCATION: 23;16                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 56                        FIELD NAME: PURCHASE CARD USER
  LOCATION: 23;17                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 57                        FIELD NAME: APPROVE RECONCILIATION USER
  LOCATION: 23;18                       ACCESS: Read w/Fileman
FIELD NUMBER: 58                        FIELD NAME: DATE RECONCILED
  LOCATION: 23;19                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60                        FIELD NAME: PURCHASE COST
  LOCATION: 23;21                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 61                        FIELD NAME: PURCHASE CARD HOLDER
  LOCATION: 23;22                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62                        FIELD NAME: PCDO 2237
  LOCATION: 23;23
  ACCESS: Direct Global Read & R/W w/Fileman
GLOBAL REFERENCE: PRC(442,D0,24)
FIELD NUMBER: 63
  FIELD NAME: PROCESSING REQUIRED IN FISCAL
  LOCATION: 24;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 64                        FIELD NAME: FREE TEXT VENDOR
  LOCATION: 24;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 65                        FIELD NAME: INTERFACE PACKAGE PREFIX
  LOCATION: 24;3                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(442,D0,25)
FIELD NUMBER: 117                       FIELD NAME: REASON NOT COMPETED
  LOCATION: 25;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 118                       FIELD NAME: NUMBER OF OFFERS
  LOCATION: 25;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 119                       FIELD NAME: PRE AWARD SYNOPSIS
  LOCATION: 25;3                        ACCESS: Read w/Fileman
FIELD NUMBER: 120                       FIELD NAME: ALTERNATE ADVERTISING
  LOCATION: 25;4                        ACCESS: Read w/Fileman
FIELD NUMBER: 121                       FIELD NAME: SOLICITATION PROCEDURE
  LOCATION: 25;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 122                       FIELD NAME: EVALUATED PREFERENCE
  LOCATION: 25;6                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 123                       FIELD NAME: FUNDING AGENCY CODE
  LOCATION: 25;7                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 124                       FIELD NAME: FUNDING AGENCY OFFICE CODE
  LOCATION: 25;8                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 125                       FIELD NAME: MULTIYEAR
  LOCATION: 25;9                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 126                       FIELD NAME: EPA DESIGNATED PRODUCT
  LOCATION: 25;10                       ACCESS: Read w/Fileman
FIELD NUMBER: 127                       FIELD NAME: CONTRACT BUNDLING
  LOCATION: 25;11                       ACCESS: Read w/Fileman
FIELD NUMBER: 128                       FIELD NAME: EXTENT COMPETED
  LOCATION: 25;12                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 129                       FIELD NAME: PERF. BASED SERVICE
  LOCATION: 25;13                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 130                       FIELD NAME: CLINGER COHEN
  LOCATION: 25;14                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 131                       FIELD NAME: PLACE OF PERF. THIS STATION?
  LOCATION: 25;15                       ACCESS: Read w/Fileman
FIELD NUMBER: 132                       FIELD NAME: PLACE OF PERFORMANCE
  LOCATION: 25;16                       ACCESS: Read w/Fileman
FIELD NUMBER: 133                       FIELD NAME: SEND TO FPDS?
  LOCATION: 25;17                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(442,D0,'AR'
FIELD NUMBER: 500.01                    FIELD NAME: BILL #
  LOCATION: AR;1                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(442,D0,22,'B'
 GLOBAL DESCRIPTION:   File 442.041 "B" cross-reference   Knowing the Purchase
 Order 
                                    entry IEN and the BOC, the 
                                    BOC entry in the BOC multiple 
                                    can be found or a check can 
                                    be made to see if the BOC is 
                                    associated with the Purchase 
                                    Order.  
GLOBAL REFERENCE: PRC(442,D0,2,'AC'
 GLOBAL DESCRIPTION:   File 442.01 "AC" cross-reference    Knowing the IEN of
 the 
                                     Purchase Order and the 
                                     Contract/BOA #, one can 
                                     find the LINE ITEMs that 
                                     reference this Contract/ 
                                     BOA # on this Purchase 
                                     Order.  
GLOBAL REFERENCE: PRC(442,'C'
 GLOBAL DESCRIPTION:   File 442 'C' cross reference     Used to look up by the 
                                  Common Numbering Series 
                                  portion of the complete 
                                  Purchase Order Number -     
                                  the part of the PO number 
                                  following the Site Number 
GLOBAL REFERENCE: PRC(442,'E'
 GLOBAL DESCRIPTION:   File 442 'E' cross-reference     Used to look up by
 Control 
                                  Point Number - not the name 
GLOBAL REFERENCE: PRC(442,'F'
 GLOBAL DESCRIPTION:   File 442 'F' cross-reference     Used to look up by
 METHOD 
                                  OF PROCESSING 
GLOBAL REFERENCE: PRC(442,D0,2,D1,3,'AC'
 GLOBAL DESCRIPTION:   File 442.08 "AC" cross-reference     Provides a
 non-lookup 
                                      list of all PARTIAL 
                                      NUMBERS for receipts 
                                      within each ITEM of a 
                                      Purchase Order 
GLOBAL REFERENCE: PRC(442,'B'
 GLOBAL DESCRIPTION:   File 442 "B" cross-reference     Look up by PURCHASE
 ORDER NUMBER 
GLOBAL REFERENCE: PRC(442,D0,2,'AE'
 GLOBAL DESCRIPTION:   File 442.01 "AE" cross-reference     A non-lookup list
 of 
                                      ITEM MASTER file entries 
                                      within all ITEMs in a 
                                      Purchase Order 
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT)
 requests read and write access to the PROCUREMENT & ACCOUNTING TRANSACTIONS
 FILE (#442).  APAT creates and displays simplified and detailed purchase card
 orders in this file.  Simplified purchase card orders are based on those
 created by the Prosthetic VistA Suite GUI, and detailed purchase card orders
 are based on those created in option PRCH ENTER DETAILED ORDER (New Detailed 
 Purchase Card Order).  
  
 Above PAR requests read access to the PROCUREMENT & ACCOUNTING TRANSACTIONS
 FILE #442 for display and reporting purposes.  
  
 Above PAR Ad-Hoc Reporting includes the PROCUREMENT & ACCOUNTING TRANSACTIONS
 FILE #442. Ad-Hoc functionality provides the ability to select fields from the
 file for display on user-defined reports.  Ad-Hoc offers only FileMan read
 access and only if the user has permission to view the file. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Effective, 5/01/23 with patch DSSO*2.0*3, type of
 access for the PURCHASE ORDER NUMBER (#.01) field was changed to 'Direct
 Global Read & R/W w/Fileman'.  
  DATE ACTIVATED: MAY 01, 2023

NUMBER: 6629                            IA #: 6629
  FILE NUMBER: 443.4                    GLOBAL ROOT: PRC(443.4,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: TYPE OF SPECIAL HANDLING FILE ACCESS
  ID: PRC(443.4,
GLOBAL REFERENCE: PRC(443.4,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   
        Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) 
        request READ access to specific fields of the Type of Special  
        Handling file (#443.4).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: NOV 21, 2018

NUMBER: 6630                            IA #: 6630
  FILE NUMBER: 420.1                    GLOBAL ROOT: PRCD(420.1,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: COST CENTER FILE ACCESS
  ID: PRCD(420.1,
GLOBAL REFERENCE: PRCD(420.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .5                        FIELD NAME: DEACTIVATED COST CENTER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .6                        FIELD NAME: DEACTIVATED BY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .7                        FIELD NAME: DATE/TIME DEACTIVATED
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCD(420.1,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: BOC
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCD(420.1,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCD(420.1,'B'
 GLOBAL DESCRIPTION:   File 420.1 "B" cross reference  Used to look up by COST
 CENTER NAME 
GLOBAL REFERENCE: PRCD(420.1,'C'
 GLOBAL DESCRIPTION:   File 420.1 "C" cross-reference  Used to look up by Cost
 Center name. 
GLOBAL REFERENCE: PRCD(420.1,'D'
 GLOBAL DESCRIPTION:   File 420.1 "D" cross-reference  Used to look up by Cost
 Center modulus (CC#1000).  
GLOBAL REFERENCE: PRCD(420.1,D0,1,'B'
 GLOBAL DESCRIPTION:   Subfile 420.11 "B" cross-reference  Used to generate a
 list of 
                                     BOCs for a Cost Center via 
                                     a VA FileMan API call 
                                     specifying the "B" index 
 GENERAL DESCRIPTION:   Above PAR and the Advanced Prosthetics Acquisition Tool
 (APAT) request READ access to the COST CENTER FILE #420.1.  
  
 Above PAR Ad-Hoc Reporting includes the COST CENTER FILE #420.1. Ad-Hoc 
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Effective 4/28/23, with patch DSSO*2.0*3, the list of
 BOCs for a Cost Center is generated by a VA FileMan API call specifying the
 "B" index.  
  DATE ACTIVATED: APR 28, 2023

NUMBER: 6631                            IA #: 6631
  FILE NUMBER: 420.2                    GLOBAL ROOT: PRCD(420.2,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: BUDGET OBJECT CODE FILE ACCESS
  ID: PRCD(420.2,
GLOBAL REFERENCE: PRCD(420.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .5                        FIELD NAME: DEACTIVATED BOC
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .6                        FIELD NAME: DEACTIVATED BY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .7                        FIELD NAME: DATE/TIME DEACTIVATED
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCD(420.2,'B'
 GLOBAL DESCRIPTION:   File 420.2 "B" cross-reference  Used to look up by
 BUDGET OBJECT CODE 
                                 NAME 
GLOBAL REFERENCE: PRCD(420.2,'C'
 GLOBAL DESCRIPTION:   File 420.2 "C" cross-reference  Used to look up by
 BUDGET OBJECT CODE by BOC name.  
GLOBAL REFERENCE: PRCD(420.2,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Above PAR and the Advanced Prosthetics Acquisition Tool
 (APAT) request read access the BUDGET OBJECT CODE FILE #420.2.  
  
 Above PAR Ad-Hoc Reporting includes the BUDGET OBJECT CODE FILE #420.2.  
 Ad-Hoc functionality provides the ability to select fields from the file for
 display on user-defined reports.  Ad-Hoc offers only FileMan read access and
 only if the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: NOV 21, 2018

NUMBER: 6632                            IA #: 6632
  FILE NUMBER: 420.8                    GLOBAL ROOT: PRCD(420.8,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SOURCE CODE FILE ACCESS
  ID: PRCD(420.8,
GLOBAL REFERENCE: PRCD(420.8,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: FISCAL EQUIV.
  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: AGENCY CODE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCD(420.8,'B'
 GLOBAL DESCRIPTION:   File 420.8 "B" cross-reference  Used to look up by
 SOURCE CODE 
GLOBAL REFERENCE: PRCD(420.8,'C'
 GLOBAL DESCRIPTION:   File 420.8 "C" cross-reference  Used to look up by
 SOURCE CODE abbreviation.  
 GENERAL DESCRIPTION:   Above PAR and the Advanced Prosthetics Acquisition Tool
 (APAT) request read access to the SOURCE CODE FILE #420.8.  
  
 Above PAR Ad-Hoc Reporting includes the SOURCE CODE FILE #420.8. Ad-Hoc 
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: NOV 21, 2018

NUMBER: 6633                            IA #: 6633
  FILE NUMBER: 442.5                    GLOBAL ROOT: PRCD(442.5,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PAT TYPE FILE ACCESS
  ID: PRCD(442.5,
GLOBAL REFERENCE: PRCD(442.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ABBREVIATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ORDER
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: REC RPT REQUIRED
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCD(442.5,'B'
 GLOBAL DESCRIPTION:   File 442.5 "B" cross reference  Used to look up by PAT
 TYPE NAME 
GLOBAL REFERENCE: PRCD(442.5,'C'
 GLOBAL DESCRIPTION:   The 442.5 "C" cross reference is used to look up PAT
 TYPE file entries by the value stored in the ABBREVIATION field (#1).  
 GENERAL DESCRIPTION:   
        Above PAR and the Advanced Prosthetics Acquisition Tool (APAT) 
        request read access to specific fields of the PAT TYPE (#442.5) 
        File.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 13, 2019

NUMBER: 6634                            IA #: 6634
  FILE NUMBER: 410                      GLOBAL ROOT: PRCS(410,
  DATE CREATED: NOV 16, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CONTROL POINT ACTIVITY FILE ACCESS
  ID: PRCS(410,
GLOBAL REFERENCE: PRCS(410,D0,0)
FIELD NUMBER: .01                       FIELD NAME: TRANSACTION NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 1                         FIELD NAME: TRANSACTION TYPE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 2                         FIELD NAME: TEMPORARY TRANS. NUMBER
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: FORM TYPE
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .5                        FIELD NAME: STATION NUMBER
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: INVENTORY DISTRIBUTION POINT
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 3.1                       FIELD NAME: INTERVAL ISSUE?
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 3.2                       FIELD NAME: MONTH OF 1358
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 67                        FIELD NAME: CONVERTED 1358
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 448                       FIELD NAME: SUBSTATION
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 449                       FIELD NAME: RUNNING BALANCE QUARTER DATE
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 450                       FIELD NAME: RUNNING BALANCE STATUS
  LOCATION: 0;12                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,1)
FIELD NUMBER: 5                         FIELD NAME: DATE OF REQUEST
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 451                       FIELD NAME: PURCHASE CARD RECORD
  LOCATION: 1;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7.5                       FIELD NAME: PRIORITY OF REQUEST
  LOCATION: 1;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7                         FIELD NAME: DATE REQUIRED
  LOCATION: 1;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8                         FIELD NAME: CLASSIFICATION OF REQUEST
  LOCATION: 1;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: SERVICE START DATE
  LOCATION: 1;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 6.5                       FIELD NAME: SERVICE END DATE
  LOCATION: 1;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 103                       FIELD NAME: ECMS ACTIONUID
  LOCATION: 1;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 104                       FIELD NAME: CANCELLED BY
  LOCATION: 1;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 105                       FIELD NAME: CANCEL DATE/TIME
  LOCATION: 1;10                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,2)
FIELD NUMBER: 11                        FIELD NAME: VENDOR
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11.1                      FIELD NAME: VENDOR ADDRESS1
  LOCATION: 2;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11.2                      FIELD NAME: VENDOR ADDRESS2
  LOCATION: 2;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11.3                      FIELD NAME: VENDOR ADDRESS3
  LOCATION: 2;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11.4                      FIELD NAME: VENDOR ADDRESS4
  LOCATION: 2;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11.5                      FIELD NAME: VENDOR CITY
  LOCATION: 2;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11.6                      FIELD NAME: VENDOR STATE
  LOCATION: 2;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11.7                      FIELD NAME: VENDOR ZIP CODE
  LOCATION: 2;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11.8                      FIELD NAME: VENDOR CONTACT
  LOCATION: 2;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11.9                      FIELD NAME: VENDOR PHONE NO.
  LOCATION: 2;10                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,3)
FIELD NUMBER: 15                        FIELD NAME: CONTROL POINT
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 28                        FIELD NAME: ACCOUNTING DATA
  LOCATION: 3;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 15.5                      FIELD NAME: COST CENTER
  LOCATION: 3;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12                        FIELD NAME: VENDOR(POINTER)
  LOCATION: 3;4                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 6.3                       FIELD NAME: REQUESTING SERVICE
  LOCATION: 3;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17                        FIELD NAME: BOC1
  LOCATION: 3;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 17.5                      FIELD NAME: BOC1 $ AMOUNT
  LOCATION: 3;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 18                        FIELD NAME: BOC2
  LOCATION: 3;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 18.5                      FIELD NAME: BOC2 $ AMOUNT
  LOCATION: 3;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: VENDOR CONTRACT NUMBER
  LOCATION: 3;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 28.5                      FIELD NAME: BBFY
  LOCATION: 3;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 28.1                      FIELD NAME: FCP/PRJ
  LOCATION: 3;12                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,4)
FIELD NUMBER: 20                        FIELD NAME: COMMITTED (ESTIMATED) COST
  LOCATION: 4;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 21                        FIELD NAME: DATE COMMITTED
  LOCATION: 4;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 22                        FIELD NAME: OBLIGATED (ACTUAL) COST
  LOCATION: 4;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: DATE OBLIGATED
  LOCATION: 4;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 24                        FIELD NAME: PURCHASE ORDER/OBLIGATION NO
  LOCATION: 4;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 25                        FIELD NAME: ADJUSTMENT $ AMOUNT
  LOCATION: 4;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 26                        FIELD NAME: DATE OBL ADJUSTED
  LOCATION: 4;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 27                        FIELD NAME: TRANSACTION $ AMOUNT
  LOCATION: 4;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 29                        FIELD NAME: OBLIGATED BY
  LOCATION: 4;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 29.5                      FIELD NAME: OBLIGATION VALIDATION CODE
  LOCATION: 4;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 29.6
  FIELD NAME: OBLIGATION VALIDATION VERSION
  LOCATION: 4;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 29.7                      FIELD NAME: OBLIGATION SIGNATURE BLOCK
  LOCATION: 4;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 29.8
  FIELD NAME: OBLIGATION VAL CODE DATE/TIME
  LOCATION: 4;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 25.5                      FIELD NAME: ADJUST CP BALANCE ONLY
  LOCATION: 4;14                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,5)
FIELD NUMBER: 30                        FIELD NAME: FMS $ AMOUNT
  LOCATION: 5;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: FMS DATE
  LOCATION: 5;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 32                        FIELD NAME: FMS TRANSACTION TYPE
  LOCATION: 5;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 33                        FIELD NAME: END DATE FOR 1358
  LOCATION: 5;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 34                        FIELD NAME: AUTO ACCRUE
  LOCATION: 5;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,6)
FIELD NUMBER: 35                        FIELD NAME: CEILING $ AMOUNT
  LOCATION: 6;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 36                        FIELD NAME: DATE ALLOCATED
  LOCATION: 6;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 37                        FIELD NAME: FUND CONTROL POINT DIST. NO
  LOCATION: 6;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 38                        FIELD NAME: TEMP CP REF#
  LOCATION: 6;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,7)
FIELD NUMBER: 40                        FIELD NAME: REQUESTOR
  LOCATION: 7;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 41                        FIELD NAME: REQUESTOR'S TITLE
  LOCATION: 7;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 42                        FIELD NAME: APPROVING OFFICIAL
  LOCATION: 7;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 43                        FIELD NAME: APPR. OFFICIAL'S TITLE
  LOCATION: 7;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 44                        FIELD NAME: DATE SIGNED (APPROVED)
  LOCATION: 7;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 44.5                      FIELD NAME: VALIDATION CODE
  LOCATION: 7;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 44.6                      FIELD NAME: ES CODE DATE/TIME
  LOCATION: 7;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 44.7                      FIELD NAME: GPF APPROVING FISCAL OFFICER
  LOCATION: 7;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 44.8                      FIELD NAME: GPF VALIDATION CODE
  LOCATION: 7;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 44.9                      FIELD NAME: GPF ES CODE DATE/TIME
  LOCATION: 7;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 39                        FIELD NAME: ACCOUNTABLE OFFICER
  LOCATION: 7;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 69                        FIELD NAME: AO SIGNATURE DATE
  LOCATION: 7;12                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,7.1)
FIELD NUMBER: 44.85                     FIELD NAME: GPF VALIDATION VERSION
  LOCATION: 7.1;1                       ACCESS: Read w/Fileman
FIELD NUMBER: 44.87                     FIELD NAME: GPF ESIG CODE
  LOCATION: 7.1;2                       ACCESS: Read w/Fileman
FIELD NUMBER: 44.55                     FIELD NAME: VALIDATION VERSION
  LOCATION: 7.1;3                       ACCESS: Read w/Fileman
FIELD NUMBER: 44.57                     FIELD NAME: ESIG CODE
  LOCATION: 7.1;4                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,8,D1,0)
FIELD NUMBER: .01                       FIELD NAME: JUSTIFICATION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,9)
FIELD NUMBER: 46                        FIELD NAME: DELIVER TO/LOCATION
  LOCATION: 9;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 47                        FIELD NAME: EST. DELIVERY DATE
  LOCATION: 9;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 48                        FIELD NAME: DATE RECEIVED
  LOCATION: 9;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 48.1
  FIELD NAME: EST. SHIPPING AND/OR HANDLING
  LOCATION: 9;4                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,10)
FIELD NUMBER: 50                        FIELD NAME: LINE ITEM COUNT
  LOCATION: 10;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 51                        FIELD NAME: PARENT TRANSACTION NUMBER
  LOCATION: 10;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 52                        FIELD NAME: STATION NO - P.O. NO
  LOCATION: 10;3                        ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Global r 
FIELD NUMBER: 56                        FIELD NAME: REQUEST STATUS
  LOCATION: 10;4                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,11)
FIELD NUMBER: 49                        FIELD NAME: SORT GROUP
  LOCATION: 11;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 53                        FIELD NAME: ORIGINATOR OF TEMP # REQ.
  LOCATION: 11;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 55
  FIELD NAME: READY FOR APPROVAL/SIGNATURE?
  LOCATION: 11;3                        ACCESS: Read w/Fileman
FIELD NUMBER: 19                        FIELD NAME: AUTHORITY
  LOCATION: 11;4                        ACCESS: Read w/Fileman
FIELD NUMBER: 19.1                      FIELD NAME: SUB AUTHORITY
  LOCATION: 11;5                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,12,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SUB-CONTROL POINT
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: $ AMOUNT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,13,D1,0)
FIELD NUMBER: .01                       FIELD NAME: REASON FOR RETURN
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,14)
FIELD NUMBER: 68                        FIELD NAME: ORIGINATOR OF REQUEST
  LOCATION: 14;1                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,100)
FIELD NUMBER: 57                        FIELD NAME: LOG VOUCHER NUMBER (SUPPLY)
  LOCATION: 100;1                       ACCESS: Read w/Fileman
FIELD NUMBER: 58                        FIELD NAME: LOG DIETETIC PERIOD
  LOCATION: 100;2                       ACCESS: Read w/Fileman
FIELD NUMBER: 59                        FIELD NAME: FISCAL PROCESSING MONTH
  LOCATION: 100;3                       ACCESS: Read w/Fileman
FIELD NUMBER: 62                        FIELD NAME: LOG CODE SHEETS SENT BY
  LOCATION: 100;4                       ACCESS: Read w/Fileman
FIELD NUMBER: 63                        FIELD NAME: LOG CODE SHEETS VALID. CODE
  LOCATION: 100;5                       ACCESS: Read w/Fileman
FIELD NUMBER: 64                        FIELD NAME: DATE SIGNED
  LOCATION: 100;6                       ACCESS: Read w/Fileman
FIELD NUMBER: 65                        FIELD NAME: LOG VOUCHER NUMBER (FISCAL)
  LOCATION: 100;7                       ACCESS: Read w/Fileman
FIELD NUMBER: 66                        FIELD NAME: LOG DEPARTMENT
  LOCATION: 100;8                       ACCESS: Read w/Fileman
FIELD NUMBER: 63.5                      FIELD NAME: LOG CS VALIDATION VERSION
  LOCATION: 100;9                       ACCESS: Read w/Fileman
FIELD NUMBER: 63.7                      FIELD NAME: LOG CS ESIG CODE
  LOCATION: 100;10                      ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,445)
FIELD NUMBER: 445.01                    FIELD NAME: REFERENCE VOUCHER NUMBER
  LOCATION: 445;1                       ACCESS: Read w/Fileman
FIELD NUMBER: 445.02                    FIELD NAME: LAST FMSLINE USED
  LOCATION: 445;2                       ACCESS: Read w/Fileman
FIELD NUMBER: 446                       FIELD NAME: TOTAL DOLLARS POSTED
  LOCATION: 445;3                       ACCESS: Read w/Fileman
FIELD NUMBER: 447                       FIELD NAME: COUPLER
  LOCATION: 445;4                       ACCESS: Read w/Fileman
FIELD NUMBER: 455                       FIELD NAME: ISSUE BOOK BATCH ID
  LOCATION: 445;5                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,'CO',D1,0)
FIELD NUMBER: .01                       FIELD NAME: COMMENTS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,'IT',D1,0)
FIELD NUMBER: .01                       FIELD NAME: LINE ITEM NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: QUANTITY
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: UNIT OF PURCHASE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: BOC
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: ITEM MASTER FILE NO.
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: STOCK NUMBER
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7                         FIELD NAME: EST. ITEM (UNIT) COST
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8                         FIELD NAME: ITEM DELIVERY POINTS
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11                        FIELD NAME: RECEIVING CODE SHEET NO.
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: PURCHASE ORDER/OBLIGATION NO
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: INTERMEDIATE PRODUCT CODE
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: QUANTITY POSTED (WHSE)
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: QUANTITY RECEIVED (PRIMARY)
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 15                        FIELD NAME: STATUS
  LOCATION: 0;14                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,'IT',D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,'IT',D1,2,D2,0)
FIELD NUMBER: .01                       FIELD NAME: DELIVERY SCHEDULE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DELIVERY REFERENCE NUMBER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,'IT',D1,3)
FIELD NUMBER: 16                        FIELD NAME: PO EST. SHIPPING
  LOCATION: 3;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,'IT',D1,4)
FIELD NUMBER: 17                        FIELD NAME: DM DOC ID
  LOCATION: 4;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 18                        FIELD NAME: DATE NEEDED BY
  LOCATION: 4;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 100                       FIELD NAME: ECMS ITEMUID
  LOCATION: 4;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,'IT',D1,445)
FIELD NUMBER: 445.01                    FIELD NAME: ACCT-BOC
  LOCATION: 445;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 445.02                    FIELD NAME: FMSLINE
  LOCATION: 445;2                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 445.03                    FIELD NAME: TOTAL QUANTITY POSTED
  LOCATION: 445;3                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 445.04                    FIELD NAME: TOTAL INVENTORY VALUE
  LOCATION: 445;4                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 445.05                    FIELD NAME: TOTAL SELLING VALUE
  LOCATION: 445;5                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PRCS(410,D0,'RM',D1,0)
FIELD NUMBER: .01                       FIELD NAME: SPECIAL REMARKS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PRCS(410,'B'
 GLOBAL DESCRIPTION:   File 410 'B' cross-reference  Used to look up by
 TRANSACTION NUMBER 
GLOBAL REFERENCE: PRCS(410,D0,'IT','AG'
 GLOBAL DESCRIPTION:   File 410 'IT','AG' cross-reference  For looking up a
 2237's item line 
                                     based on the file #410 entry's 
                                     IEN and the Item Master File (IMF) 
                                     Number on that item line 
GLOBAL REFERENCE: PRCS(410,'AO'
 GLOBAL DESCRIPTION:   File 410 "AO" cross reference  Used to look up by
 INVENTORY DISTRIBUTION POINT for the transaction 
GLOBAL REFERENCE: PRCS(410,'AQ'
 GLOBAL DESCRIPTION:   File 410 'AQ' cross reference  Used to look up by
 TRANSACTION NUMBER only for requests that are ready for the Control Point
 Official's approval 
GLOBAL REFERENCE: PRCS(410,'E'
 GLOBAL DESCRIPTION:   File 410 "E" cross reference  Used to look up
 transactions by VENDOR NAME 
 GENERAL DESCRIPTION:   Above PAR and the Advanced Prosthetics Acquisition Tool
 (APAT) request permission to reference the CONTROL POINT ACTIVITY FILE #410 to
 create/edit 2237's during the creation of purchase card orders and 2237's and
 during purchase card reconciliation/close-out.  
  
  
 Above PAR Ad-Hoc Reporting includes the CONTROL POINT ACTIVITY FILE #410.  
 Ad-Hoc functionality provides the ability to select fields from the file for
 display on user-defined reports.  Ad-Hoc offers only FileMan read access and
 only if the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: NOV 14, 2018

NUMBER: 6635                            IA #: 6635
  DATE CREATED: NOV 18, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM ADMIN CODES
  REMOTE PROCEDURE: PXVIMM ADMIN CODES
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  
  
 Making a call to the PXVIMM ADMIN CODES RPC to retrieve immunization 
 administration CPT codes.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: PXVIMM ADMIN CODES
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: JAN 11, 2017

NUMBER: 6636                            IA #: 6636
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHAAC
  NAME: FPDS HL7 MESSAGE GENERATION FOR AAC
  ID: PRCHAAC
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics 
    Acquisition Tool (APAT) to call IFCAP routine AAC^PRCHAAC.  When a 
    detailed purchase card order is created, this functionality will gather 
    FPDS data for the report requested by the Austin Automation Center 
    (AAC), create an HL7 message, and send it to the Austin server via the 
    VistA HL7 package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: AAC
VARIABLES: PRCHPO                       TYPE: Input
 VARIABLES DESCRIPTION:   File 442 IEN 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 12, 2019

NUMBER: 6637                            IA #: 6637
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHES5
  NAME: ENCODING E-SIGNATURE ON PC ORDER
  ID: PRCHES5
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics 
    Acquisition Tool (APAT) to call IFCAP routine ENCODE^PRCHES5 to encode 
    an esignature when a detailed purchase card order is created.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: ENCODE(LEVEL0,USERNUM,Y)
VARIABLES: LEVEL0                       TYPE: Input
 VARIABLES DESCRIPTION:   File 442 IEN 
VARIABLES: USERNUM                      TYPE: Input
 VARIABLES DESCRIPTION:   File 200 IEN of user 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Processing Results 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 12, 2019

NUMBER: 6638                            IA #: 6638
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHNPO
  NAME: ENTER NEW PURCHASE CARD ORDER   ID: PRCHNPO
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call IFCAP routine PRCHNPO when creating a detailed 
    purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: ASTR
 COMPONENT DESCRIPTION:   
    This component is called when creating a detailed 
    purchase card order in order to set the DESCRIPT.  
    ASTR. (#7) field to "*" in the line items that do 
    not contain a CONTRACT/BOA # (#4) in the case that 
    some line items have CONTRACT/BOA #'s and some do 
    not.  
VARIABLES: PRCHPO                       TYPE: Input
 VARIABLES DESCRIPTION:   File 442 IEN 
VARIABLES: PRCHSC                       TYPE: Input
 VARIABLES DESCRIPTION:   SOURCE CODE (#8) of file 442 entry 
COMPONENT/ENTRY POINT: CHG
 COMPONENT DESCRIPTION:   
    This component is called when creating a detailed 
    purchase card order.  If the ITEM MASTER FILE NO.  
    (#1.5) is not present and there is no DESCRIPTION 
    (#1) in the ITEM multiple (#442.01) of the file 442 
    entry, then fields DESCRIPTION LINE COUNT (#6) and 
    DESCRIPT. ASTR. (#7) are set to null, and a message 
    that "Line item"_LINE ITEM NUMBER (#.01)_" is 
    missing its description" is sent. LINE ITEM NUMBER 
    (#.01) from the ITEM multiple (#442.01) is set to 
    the next value, and several cross-references are 
    updated.  
VARIABLES: PRCH                         TYPE: Input
 VARIABLES DESCRIPTION:   Item (#442.01) IEN 
VARIABLES: PRCHPO                       TYPE: Input
 VARIABLES DESCRIPTION:   File 442 IEN 
VARIABLES: I                            TYPE: Input
 VARIABLES DESCRIPTION:   Value of LINE ITEM NUMBER 
VARIABLES: PRCHER                       TYPE: Output
 VARIABLES DESCRIPTION:   Error Indicator 
COMPONENT/ENTRY POINT: CN
 COMPONENT DESCRIPTION:   
    This component is called when creating a detailed 
    purchase card order in order to process the 
    CONTRACT/BOA #'s (#4) in the ITEM multiple and 
    to create the "AC" cross-reference for 
    CONTRACT/BOA #'s. 
VARIABLES: PRCHCN                       TYPE: Input
 VARIABLES DESCRIPTION:   File 442 sub-file 442.01 field #4 CONTRACT/BOA # 
VARIABLES: PRCH('AM',PRCHCN)            TYPE: Output
 VARIABLES DESCRIPTION:   Array of CONTRACT/BOA # field (#4) and amount data
 from the ITEM multiple (#442.01) of file 442 
  
 For the CN subroutine, the PRCH('AM',PRCHCN) array is populated for each line
 item that has a CONTRACT/BOA # (#4) in the ITEM multiple (#442.01) of file
 442.  
VARIABLES: PRCHEC                       TYPE: Output
 VARIABLES DESCRIPTION:   Count of PRCH("AM",PRCHCN) array entries 
VARIABLES: PRCHL3                       TYPE: Output
 VARIABLES DESCRIPTION:   Contract # 
VARIABLES: PRCHPO                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of file 442 entry 
VARIABLES: PRCHAM                       TYPE: Input
 VARIABLES DESCRIPTION:   TOTAL COST field (#15) from the ITEM multiple
 (#442.01) of file 442 which is added to the running total for each 
 CONTRACT/BOA # (#4) in the second caret-piece of the PRCH("AM",PRCHCN) entry 
VARIABLES: PRCH                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the ITEM multiple (#442.01) being processed 
COMPONENT/ENTRY POINT: MISS
 COMPONENT DESCRIPTION:   
    This component checks for missing fields in each ITEM 
    multiple (#442.01) in the detailed purchase card order 
    being created.  
VARIABLES: PRCH('COUNT',PRCH)           TYPE: Input
 VARIABLES DESCRIPTION:   Array of ITEM multiple (#442.01) entries for this 
 PROCUREMENT & ACCOUNTING TRANSACTIONS file (#442) entry 
VARIABLES: J                            TYPE: Input
 VARIABLES DESCRIPTION:   Number of entries in the PRCH("COUNT") array 
VARIABLES: I                            TYPE: Input
 VARIABLES DESCRIPTION:   Number of entries in the PRCH("AM") array 
VARIABLES: PRCH('AM')                   TYPE: Input
 VARIABLES DESCRIPTION:   Array containing running balances of TOTAL AMOUNT for 
 each CONTRACT/BOA # (#4) in the ITEM multiple (#442.01) in this file 442 entry 
VARIABLES: PRCH                         TYPE: Input
 VARIABLES DESCRIPTION:   File 442 ITEM multiple (#442.01) IEN 
COMPONENT/ENTRY POINT: OM
 COMPONENT DESCRIPTION:   
    This component processes ITEM (#442.01) entries 
    in file 442 that have no CONTRACT/BOA # (#4).  
VARIABLES: PRCHLI                       TYPE: Used
 VARIABLES DESCRIPTION:   Loop Control value when processing the ITEM multiple 
 (#442.01) of the PROCUREMENT & ACCOUNTING TRANSACTIONS file (#442) in
 subroutine MISS^PRCHNPO 
  
 This value is stored in the third caret-piece of the PRCH("AM",".OM") array as
 each ITEM (#442.01) entry from file 442 is processed in subroutine OM.  
VARIABLES: PRCH                         TYPE: Output
 VARIABLES DESCRIPTION:   Array of CONTRACT/BOA # field (#4) and amount data in
 the ITEM multiple (#442.01) of file 442 
  
 For the OM subroutine, the PRCH('AM','.OM') array is populated for each line
 item that has no CONTRACT/BOA # (#4) in the ITEM multiple (#442.01) of file
 442.  
VARIABLES: PRCHEC                       TYPE: Output
 VARIABLES DESCRIPTION:   Count of PRCH("AM",".OM") array entries 
VARIABLES: PRCHL3                       TYPE: Output
 VARIABLES DESCRIPTION:   Assigned string value ".OM" 
VARIABLES: PRCHAM                       TYPE: Input
 VARIABLES DESCRIPTION:   TOTAL COST field (#15) from the ITEM multiple
 (#442.01) of file 442 which is added to the running total for the in the
 second caret-piece of the PRCH("AM",".OM") entry 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: OCT 15, 2020

NUMBER: 6639                            IA #: 6639
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHNPO2
  NAME: FPDS CODE SELECTION SCREEN      ID: PRCHNPO2
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call EN7^PRCHNPO2 when creating a detailed purchase 
    card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: EN7
 COMPONENT DESCRIPTION:   
    This component is called when screening a Type Code.  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   File 420.6 IEN 
VARIABLES: PRCH                         TYPE: Input
 VARIABLES DESCRIPTION:   Contract/BOA # 
VARIABLES: PRCHDT                       TYPE: Input
 VARIABLES DESCRIPTION:   PRCHDT holds the value '0' or '1' based on the VA
 FileMan date in the P.O. DATE field (#.1) of the PROCUREMENT & ACCOUNTING
 TRANSACTIONS file (#442).  The value indicates whether the FPDS codes
 introduced in 88 or those intro- duced in 89 are applicable.  
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 13, 2019

NUMBER: 6640                            IA #: 6640
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHNPO7
  NAME: AUDITS OF PURCHASE CARD ORDER LINE ITEMS
  ID: PRCHNPO7
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call IFCAP routine PRCHNPO7 when creating a detailed 
    purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: EN105
 COMPONENT DESCRIPTION:   
    This component is called to ensure that a line item 
    in the PROCUREMENT & ACCOUNTING TRANSACTIONS file 
    (#442) contains an FSC or PSC.  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   Error Indicator 
VARIABLES: PRCHPO                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of file 442 entry 
COMPONENT/ENTRY POINT: EN2
 COMPONENT DESCRIPTION:   
    This component is called to store "*** ESTIMATED PURCHASE 
    ORDER ***" into the detailed purchase card order COMMENTS 
    (#20) field in the PROCUREMENT & ACCOUNTING TRANSACTIONS 
    file (#442) if the ESTIMATED ORDER? field (#.08) is 
    set to 'YES'.  
VARIABLES: PRCH                         TYPE: Used
 VARIABLES DESCRIPTION:   Contains the node reference "^PRC(442,PRCHPO,4,"
 which will be used subsequently in WORD^PRCHUTL as part of a variable 
 indirection SET statement:  S $P(@(PRCH_"0)"),U,3,4)=WJ_U_WJ 
VARIABLES: PRCHPO                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of file 442 entry 
VARIABLES: WX                           TYPE: Used
 VARIABLES DESCRIPTION:   Text to be added to the COMMENTS field (#20) of the 
 PROCUREMENT AND ACCOUNTING TRANSACTIONS file (#442) if this is an estimated
 order 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 12, 2019

NUMBER: 6641                            IA #: 6641
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHNPO8
  NAME: BBFY OF PURCHASE CARD ORDER     ID: PRCHNPO8
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics 
    Acquisition Tool (APAT) to call BBFY^PRCHNPO8 when creating a 
    detailed purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: BBFY(PO)
 COMPONENT DESCRIPTION:   
    This component is called when determining the Beginning 
    Budget Fiscal Year.  
VARIABLES: PO                           TYPE: Input
 VARIABLES DESCRIPTION:   File 442 IEN 
VARIABLES: PRC('BBFY')                  TYPE: Output
 VARIABLES DESCRIPTION:   Four-digit Beginning Budget Fiscal Year 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 12, 2019

NUMBER: 6642                            IA #: 6642
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHNPOA
  NAME: PCDO TRANSACTION NUMBER VALIDATION
  ID: PRCHNPOA
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call IFCAP routine PRCHNPOA when creating a detailed 
    purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: CHECKFCP(PCODA)
 COMPONENT DESCRIPTION:   
    This component is called to check that the Transaction 
    Number of the 2237 pointed to by the PCDO 2237 field 
    (#62) of the PROCUREMENT & ACCOUNTIN TRANSACTIONS file 
    (#442) to determine if the Fund Control Point in the 
    4th hyphen piece of the TRANSACTION NUMBER field 
    (#.01) is the same as the value in the 2237'S CONTROL 
    POINT field (#15) [file #410].  It also checks if the 
    Fiscal Year and quarter (2nd thru 3rd hyphen pieces) 
    in the TRANSACTION NUMBER field's value is the same 
    as the current Fiscal Year and Fiscal Quarter.  If, 
    after the user has e-signed the Purchase Card Order, 
    a mismatch is detected, this API creates a new 2237 
    entry which it populates with the old values and then 
    cancels and it generates a new 2237 transaction number 
    which it stores in the TRANSACTION NUMBER field of the 
    original 2237 entry.  This API gets the PCDO 2237 
    reference from the Purchase Card Order entry in file 
    #442, but it is not actually looking at the FCP field 
    (#1) of the Purchase Card Order in file #442 to do the 
    comparison.  Also, the validation is not just on FCP, 
    but also includes FY and Qtr.  For documentation 
    purposes, the logic also creates a link from the entry 
    with the old Transaction Number to the entry with the 
    new Transaction Number via a "Transaction "_OTNUM_" 
    replaced by trans. "_TX1 entry in the COMMENTS field 
    (#60).  
VARIABLES: PCODA                        TYPE: Input
 VARIABLES DESCRIPTION:   File 442 IEN 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 12, 2019

NUMBER: 6643                            IA #: 6643
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  ROUTINE: PRCHNPOB                     NAME: USAGE OF PRCHNPOB
  ID: PRCHNPOB
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call IFCAP routine PRCHNPOB when creating a detailed 
    purchase card order.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: $$EN(SITE,FCP)
 COMPONENT DESCRIPTION:   
    This component is called when checking for new Control Point 
    Activity file (#410) Transaction Number availability when creating a 
    purchase card order.    
VARIABLES: SITE                         TYPE: Input
 VARIABLES DESCRIPTION:   Site Number for Transaction Number 
VARIABLES: FCP                          TYPE: Input
 VARIABLES DESCRIPTION:   Fund Control Point for Transaction Number 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL

NUMBER: 6644                            IA #: 6644
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHQQ
  NAME: ESIG PROBLEM ERROR MESSAGE      ID: PRCHQQ
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call IFCAP routine PRCHQQ when creating a detailed 
    purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: $$ERR(ROUTINE,ERROR)
 COMPONENT DESCRIPTION:   
    This component is called to process the error messages 
    related to problems identified when the user is entering 
    that person's electronic signature.  
VARIABLES: ROUTINE                      TYPE: Input
 VARIABLES DESCRIPTION:   Routine that initiated the error 
VARIABLES: ERROR                        TYPE: Input
 VARIABLES DESCRIPTION:   Error Message Value 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 13, 2019

NUMBER: 6645                            IA #: 6645
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHSTAT
  NAME: STATUS UPDATE PURCHASE CARD ORDER
  ID: PRCHSTAT
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call IFCAP routine PRCHSTAT when creating a detailed 
    purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: ENS
 COMPONENT DESCRIPTION:   
    This component consists of a $ORDER() function call 
    to resolve a Supply Status input value passed in 
    variable X to the IEN of the corresponding PURCHASE 
    ORDER STATUS file (#442.3) entry and places that 
    value into variable Y before going to UPD.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   Supply Status Order 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN of PROCUREMENT & ACCOUNTING TRANSACTIONS file
 (#442) entry 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   IEN of PURCHASE ORDER STATUS file (#442.3) entry 
COMPONENT/ENTRY POINT: UPD
 COMPONENT DESCRIPTION:   
    This component requires that a PURCHASE ORDER STATUS 
    file (#442.3) IEN value be present in variable Y.  
    The 'AG' MUMPS cross reference on the PROCUREMENT & 
    ACCOUNTING TRANSACTIONS file (#442) entry's SUPPLY 
    STATUS field (#.5) updates the SUPPLY STATUS ORDER 
    (#.7) and the FISCAL STATUS ORDER (#.8) fields when 
    in module UPD.  The SUPPLY STATUS field (#.5) is 
    updated via the ^DIE call.  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of PURCHASE ORDER STATUS file (#442.3) entry 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN of PROCUREMENT & ACCOUNTING TRANSACTIONS file
 (#442) entry 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUL 02, 2019

NUMBER: 6646                            IA #: 6646
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHSWCH
  NAME: PRCHOBL BASED ON FCP SWITCHES/MOP
  ID: PRCHSWCH
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call IFCAP routine PRCHSWCH when creating a detailed 
    purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: CHECK
 COMPONENT DESCRIPTION:   
    This component is called to check switches to determine 
    where to send the order when creating a detailed 
    purchase card order.  
VARIABLES: PRCHOBL                      TYPE: Output
 VARIABLES DESCRIPTION:   '1' if obligate without prior Fiscal review; '0'
 otherwise 
VARIABLES: PRCHPO                       TYPE: Input
 VARIABLES DESCRIPTION:   File 442 IEN 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   File from which to obtain FCP - potential values are
 '442' (PROCUREMENT & ACCOUNTING TRANSACTIONS file) and '443.6' (AMENDMENTS
 file) 
VARIABLES: PRC('SITE')                  TYPE: Input
 VARIABLES DESCRIPTION:   IFCAP Site 
VARIABLES: AUTOOBLG                     TYPE: Output
 VARIABLES DESCRIPTION:   Not returned for purchase card orders 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 13, 2019

NUMBER: 6647                            IA #: 6647
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHUTL
  NAME: PRCHLOG VARIABLE SETUP          ID: PRCHUTL
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call SWITCH^PRCHUTL when creating a detailed purchase 
    card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: SWITCH
 COMPONENT DESCRIPTION:   
    This component is called to check the ISMS switch when 
    creating a detailed purchase card order.  
VARIABLES: PRC('SITE')                  TYPE: Input
 VARIABLES DESCRIPTION:   IFCAP Site 
VARIABLES: PRCHLOG                      TYPE: Output
 VARIABLES DESCRIPTION:   '1' - code sheets transmitted to LOG, not ISMS 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUL 02, 2019

NUMBER: 6648                            IA #: 6648
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCOEDC
  NAME: PHA FIELD VALIDATION            ID: PRCOEDC
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call NEW^PRCOEDC when creating a detailed purchase 
    card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: NEW(VAR1,VAR2)
 COMPONENT DESCRIPTION:   
    This component is called to validate the fields of the 
    different segments that make up the PHA (Procurement 
    History Activity) transaction.  This validation 
    indicates whether aspects of the order have to be re- 
    edited or a supporting file like the site's ADMIN.  
    ACTIVITY SITE PARAMETER file (#411) entry needs to 
    be corrected because as the file entries are currently 
    populated a correct PHA cannot be built.  
VARIABLES: VAR1                         TYPE: Input
 VARIABLES DESCRIPTION:   File 442 IEN 
VARIABLES: VAR2                         TYPE: Output
 VARIABLES DESCRIPTION:   'ERROR' - if an error has been detected 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 13, 2019

NUMBER: 6649                            IA #: 6649
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPWIU
  NAME: INVENTORY DUE-IN RECALCULATION  ID: PRCPWIU
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call UPDATE^PRCPWIU when creating a detailed purchase 
    card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: UPDATE
 COMPONENT DESCRIPTION:   
    This component is called to update due-ins based on 
    recalculation from data in the order (file #442), 
    associated 2237's (file #410), and the inventory 
    item multiple (file #445).  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   File 442 IEN 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 13, 2019

NUMBER: 6650                            IA #: 6650
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCS0A
  NAME: FUNDS AVAILABILITY CHECK        ID: PRCS0A
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call $$OVCOM^PRCS0A when creating a detailed purchase 
    card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: $$OVCOM(PRCA,PRCB,PRCC)
 COMPONENT DESCRIPTION:   
    This component is called to check funds availability for 
    the purchase card order taking into account the station's 
    and FCP's overcommit and rollover switch settings.  If 
    available funds are sufficient, then '0' is returned; 
    otherwise, either '1' or '2' is returned to the calling 
    routine.  
VARIABLES: PRCA                         TYPE: Input
 VARIABLES DESCRIPTION:   Data:  ^1 Station 
        ^2 FCP 
        ^3 Running Balance FY (4-digit) 
        ^4 Running Balance Quarter 
VARIABLES: PRCB                         TYPE: Input
 VARIABLES DESCRIPTION:   Amount Entered 
VARIABLES: PRCC                         TYPE: Input
 VARIABLES DESCRIPTION:   1 if obligated amount; 2 if committed amount 
VARIABLES: Z                            TYPE: Output
 VARIABLES DESCRIPTION:   Results:  0 if allowed; 
           1 if ST/FCP switch fail 
           2 if Rollover fail 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 13, 2019

NUMBER: 6651                            IA #: 6651
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCSPC
  NAME: COMMITTED BALANCE DETAILED PC ORDER
  ID: PRCSPC
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call COMM^PRCSPC when creating a detailed purchase card 
    order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: COMM(DA,SDATE)
 COMPONENT DESCRIPTION:   
    This component is called to adjust the uncommitted 
    control point and sub-control point balances in the 
    FUND CONTROL POINT file (#420) based on the purchase 
    card order's net amount.  If there is a primary 2237 
    attached to the order, the committed (estimated) cost 
    and the transaction $ amount on that 2237 is populated.  
    Additionally, the estimated delivery date is populated 
    with the value on the purchase card order, which is 
    passed as an argument.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   File 442 IEN 
VARIABLES: SDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   Estimated Delivery Date 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 13, 2019

NUMBER: 6652                            IA #: 6652
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCSUT
  NAME: BBFY OF FCP                     ID: PRCSUT
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call $$BBFY^PRCSUT() when creating a detailed purchase 
    card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: $$BBFY(A,B,C,PRCA)
 COMPONENT DESCRIPTION:   
    This component is called to determine the beginning budget 
    fiscal year for the control point when creating a detailed 
    purchase card order.  
VARIABLES: A                            TYPE: Input
 VARIABLES DESCRIPTION:   Station Number 
VARIABLES: B                            TYPE: Input
 VARIABLES DESCRIPTION:   Fiscal Year 
VARIABLES: C                            TYPE: Input
 VARIABLES DESCRIPTION:   FCP Number 
VARIABLES: PRCA                         TYPE: Input
 VARIABLES DESCRIPTION:   PRCA=1 for no user interaction 
VARIABLES: PRC('BBFY')                  TYPE: Output
 VARIABLES DESCRIPTION:   Beginning Budget Fiscal Year 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 13, 2019

NUMBER: 6653                            IA #: 6653
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCV442A
  NAME: PURCHASE ORDER DATA FOR DYNAMED
  ID: PRCV442A
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call UPD^PRCV442A() when creating a detailed 
    purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: UPD
 COMPONENT DESCRIPTION:   
    This component is called to update DynaMed regarding approved 
    purchase orders containing DynaMed items when creating a 
    detailed purchase card order.  
VARIABLES: POIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   File 442 IEN 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUL 02, 2019

NUMBER: 6654                            IA #: 6654
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHSF
  NAME: PC ORDER NET, TOTAL & BOC $ UPDATES
  ID: PRCHSF
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call ^PRCHSF when creating a detailed purchase card 
    order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: PRCHSF
 COMPONENT DESCRIPTION:   Total PO $ Amount Calculations for file 442 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   File 442 IEN 
VARIABLES: PRCHPO                       TYPE: Input
 VARIABLES DESCRIPTION:   File 442 IEN 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 13, 2019

NUMBER: 6655                            IA #: 6655
  DATE CREATED: NOV 22, 2016            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCOEDI
  NAME: PHA TXN FOR EDI & PHA QUEUES    ID: PRCOEDI
 GENERAL DESCRIPTION:   
    This integration agreement allows the Advanced Prosthetics Acquisition 
    Tool (APAT) to call IFCAP routine PRCOEDI when creating or amending a 
    detailed purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: PRCOEDI
 COMPONENT DESCRIPTION:   This API generates the PHA transaction and sends it
 to the ISM and for EDI orders to the EDP queue(s) at station 200 (AITC).  
VARIABLES: PRCOPODA                     TYPE: Input
 VARIABLES DESCRIPTION:   PRCOPODA - String of up to 4 "^" pieces: 
    Piece 1 = IEN of file 442 entry 
    Piece 2 = (optional) Flag if not new order 
       Values: 
          1 = Create a PHM, do not transmit to EDI 
          2 = Create a PHA, do not transmit to EDI 
    Piece 3 = (optional) Amendment number 
    Piece 4 = (optional) IEN of replaced file 442 
              entry, if PO number change amendment 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUL 02, 2019

NUMBER: 6656                            IA #: 6656
  DATE CREATED: NOV 25, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM ADMIN ROUTE
  REMOTE PROCEDURE: PXVIMM ADMIN ROUTE
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  
  
 Calls the PXVIMM ADMIN ROUTE RPC to retrieve the entries from the IMM 
 ADMINISTRATION ROUTE File (#920.2).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: PXVIMM
KEYWORDS: HMP
KEYWORDS: PXVIMM ADMIN ROUTE
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: JAN 11, 2017

NUMBER: 6657                            IA #: 6657
  DATE CREATED: NOV 25, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM ADMIN SITE
  REMOTE PROCEDURE: PXVIMM ADMIN SITE
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  
  
 Calls the PXVIMM ADMIN SITE RPC to retrieve entries from the IMM 
 ADMINISTRATION SITE (BODY) File (#920.3).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: PXVIMM
KEYWORDS: PXVIMM ADMIN SITE
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: JAN 11, 2017

NUMBER: 6658                            IA #: 6658
  DATE CREATED: NOV 25, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM ICR LIST
  REMOTE PROCEDURE: PXVIMM ICR LIST
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  
  
 Calls the PXVIMM ICR LIST RPC to retrieve entries from the IMM 
 CONTRAINDICATION REASONS File (#920.4) and the IMM REFUSAL REASONS File 
 (#920.5).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: PXVIMM ICR LIST
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: JAN 11, 2017

NUMBER: 6659                            IA #: 6659
  DATE CREATED: NOV 25, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM IMM DETAILED
  REMOTE PROCEDURE: PXVIMM IMM DETAILED
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  
  
 Calls to the PXVIMM IMM DETAILED RPC to retrieve a detailed Immunization 
 Record.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: PXVIMM
KEYWORDS: PXVIMM IMM
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: JAN 11, 2017

NUMBER: 6660                            IA #: 6660
  DATE CREATED: NOV 25, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM IMM FORMAT
  REMOTE PROCEDURE: PXVIMM IMM FORMAT
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  
  
 Calls the PXVIMM IMM FORMAT RPC to retrieve a formatted text of an 
 immunization for use in documentation.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: PXVIMM
KEYWORDS: PXVIMM IMM
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: JAN 11, 2017

NUMBER: 6661                            IA #: 6661
  DATE CREATED: NOV 25, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM IMM LOT
  REMOTE PROCEDURE: PXVIMM IMM LOT
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  
  
 Calls the PXVIMM IMM LOT RPC to retrieve information from the IMMUNIZATION LOT
 File (#9999999.41).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: PXVIMM
KEYWORDS: PXVIMM IMM
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: JAN 11, 2017

NUMBER: 6662                            IA #: 6662
  DATE CREATED: NOV 25, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM IMM MAN
  REMOTE PROCEDURE: PXVIMM IMM MAN
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  
  
 Calls the PXVIMM IMM MAN RPC to retrieve information from the IMM MANUFACTURER
 File (#9999999.04).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: PXVIMM
KEYWORDS: PXVIMM IMM
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: JAN 11, 2017

NUMBER: 6663                            IA #: 6663
  DATE CREATED: NOV 25, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM IMM SHORT LIST
  REMOTE PROCEDURE: PXVIMM IMM SHORT LIST
 GENERAL DESCRIPTION:   
  
 Calls the PXVIMM IMM SHORT LIST RPC to retrieve a short list of immunizations. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXVIMM
KEYWORDS: PXVIMM IMM
KEYWORDS: SHORT LIST
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
 SUBSCRIBING DETAILS:   
  
 HMP's subscription to this ICR was retired as of 10/27/17 when HMP was shut
 down.  HMP*2.0*12 released on 10/17/17 is an informational patch outlining the
 steps for the sites to shut down the application.  If HMP is reactivated in
 the future, the HMP project team should review the access provided by this ICR
 with the custodial application before the subscription is reactivated.  See
 VistA Document Library (VDL) for list of retired HMP ICRs.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA will be using this RPC with their OrderMgmtSvc -
 getImmunizationTypes and VIAB GET IMMUNIZATION TYPE RPC.  
  DATE ACTIVATED: NOV 20, 2017

NUMBER: 6664                            IA #: 6664
  DATE CREATED: NOV 25, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM IMMDATA
  REMOTE PROCEDURE: PXVIMM IMMDATA
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  
  
 Calls the PXVIMM IMMDATA RPC to retrieve information from the IMMUNIZATION 
 File (#9999999.14).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: PXVIMM
KEYWORDS: PXVIMM IMMDATA
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: JAN 11, 2017

NUMBER: 6665                            IA #: 6665
  DATE CREATED: NOV 25, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM VICR EVENTS
  REMOTE PROCEDURE: PXVIMM VICR EVENTS
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  
  
 Calls the PXVIMM VICR EVENTS RPC to retrieve "active" entries from the V IMM
 CONTRA/REFUSAL EVENTS File (#9000010.707) that are related to the given
 patient and immunization. "Active" is defined as entries where the Event Date
 and Time is greater than or equal to PXDATE and the Warn Until Date is null or
 greater than PXDATE.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: PXVIMM
KEYWORDS: PXVIMM VICR
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: JAN 11, 2017

NUMBER: 6666                            IA #: 6666
  DATE CREATED: NOV 25, 2016
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM VIS
  REMOTE PROCEDURE: PXVIMM VIS
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  
  
 Calls the PXVIMM VIS RPC to retrieve information from the VACCINE INFORMATION
 STATEMENT File (#920).  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: PXVIMM
KEYWORDS: PXVIMM VIS
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: JAN 11, 2017

NUMBER: 6667                            IA #: 6667
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ USERQ
  REMOTE PROCEDURE: YTQ USERQ
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ USERQ Mental Health RPC.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This is approved as long as VIA restricts this RPC
 access to MH Checkup only, through the application proxy.  
  DATE ACTIVATED: SEP 20, 2017

NUMBER: 6668                            IA #: 6668
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ TSLIST1
  REMOTE PROCEDURE: YTQ TSLIST1
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ TSLIST1 Mental Health RPC.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This is approved as long as VIA restricts this RPC
 access to MH Checkup only, through the application proxy.  
  DATE ACTIVATED: SEP 20, 2017

NUMBER: 6669                            IA #: 6669
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ QUESTALL
  REMOTE PROCEDURE: YTQ QUESTALL
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ QUESTALL Mental Health RPC.  
  
 The release of patch YS*5.01.123 changes the routine called by the RPC.  The
 routine before patch YS*5.01*123 is  YTQAPI3, and the routine after the patch
 is YTQAPI24.  Input, output and tag name are not changed with this patch. The
 above changes are dependent upon the release of CPRS v31A.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This is approved as long as VIA restricts this RPC
 access to MH Checkup only, through the application proxy.  
  DATE ACTIVATED: SEP 14, 2017

NUMBER: 6670                            IA #: 6670
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ SECTION
  REMOTE PROCEDURE: YTQ SECTION
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ SECTION Mental Health RPC.  
  
 The release of patch YS*5.01.123 changes the routine name called by the RPC. 
 The routine before patch YS*5.01*123 is  YTQAPI, and the routine after the
 patch is YTQAPI24.  Input, output and tag name are not changed with this
 patch. The above changes are dependent upon the release of CPRS v31A.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This is approved as long as VIA restricts this RPC
 access to MH Checkup only, through the application proxy.  
  DATE ACTIVATED: SEP 18, 2017

NUMBER: 6671                            IA #: 6671
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ RULES
  REMOTE PROCEDURE: YTQ RULES
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ RULES Mental Health RPC.  
  
 The release of patch YS*5.01.123 changes the routine called by the RPC.  The
 routine before patch YS*5.01*123 is  YTQAPI1, and the routine after the patch
 is YTQAPI24.  Input, output and tag name are not changed with this patch.  The
 above changes are dependent upon the release of CPRS v31A.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This is approved as long as VIA restricts this RPC
 access to MH Checkup only, through the application proxy.  
  DATE ACTIVATED: SEP 18, 2017

NUMBER: 6672                            IA #: 6672
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ SKIP
  REMOTE PROCEDURE: YTQ SKIP
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ SKIP Mental Health RPC.  
  
 The release of patch YS*5.01.123 changes the routine name called by the RPC. 
 The routine before patch YS*5.01*123 is  YTQAPI, and the routine after the
 patch is YTQAPI24.  Input, output and tag name are not changed with this
 patch.  The above changes are dependent upon the release of CPRS v31A.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This is approved as long as VIA restricts this RPC
 access to MH Checkup only, through the application proxy.  
  DATE ACTIVATED: SEP 19, 2017

NUMBER: 6673                            IA #: 6673
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ CHOICES
  REMOTE PROCEDURE: YTQ CHOICES
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ CHOICES Mental Health RPC.  
  
 The release of patch YS*5.01.123 changes the routine called by the RPC.  The
 routine before patch YS*5.01*123 is  YTQAPI, and the routine after the patch
 is YTQAPI24.  Input, output and tag name are not changed with this patch.  The
 above changes are dependent upon the release of CPRS v31A.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This is approved as long as VIA restricts this RPC
 access to MH Checkup only, through the application proxy.  
  DATE ACTIVATED: SEP 14, 2017

NUMBER: 6674                            IA #: 6674
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ GET SCALES
  REMOTE PROCEDURE: YTQ GET SCALES
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ GET SCALES Mental Health RPC.  
  
 The release of patch YS*5.01.123 changes the routine called by the RPC.  The
 routine before patch YS*5.01*123 is  YTQAPI3, and the routine after the patch
 is YTQAPI23.  Input, output and tag name are not changed with this patch.  The
 above changes are dependent upon the release of CPRS v31A.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This is approved as long as VIA restricts this RPC
 access to MH Checkup only, through the application proxy.  
  DATE ACTIVATED: SEP 14, 2017

NUMBER: 6675                            IA #: 6675
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ GET REPORT
  REMOTE PROCEDURE: YTQ GET REPORT
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ GET REPORT Mental Health RPC.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This is approved as long as VIA restricts this RPC
 access to MH Checkup only, through the application proxy.  
  DATE ACTIVATED: SEP 14, 2017

NUMBER: 6676                            IA #: 6676
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  NAME: YTQ SAVE                        REMOTE PROCEDURE: YTQ SAVE
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ SAVE Mental Health RPC.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO

NUMBER: 6677                            IA #: 6677
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  NAME: YTQ SET ANSWER ALL              REMOTE PROCEDURE: YTQ SET ANSWER ALL
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ SET ANSWER ALL Mental Health
 RPC.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This is approved as long as VIA restricts this RPC
 access to MH Checkup only, through the application proxy.  

NUMBER: 6678                            IA #: 6678
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ ALL ANSWERS
  REMOTE PROCEDURE: YTQ ALL ANSWERS
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ ALL ANSWERS Mental Health RPC.  
  
 The release of patch YS*5.01.123 changes the routine called by the RPC.  The
 routine before patch YS*5.01*123 is YTQAPI2 and the new routine after the
 patch is YTQAPI21.  Input, output and tag name are not changed with this
 patch.  The above changes are dependent upon the release of CPRS v31A.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This is approved as long as VIA restricts this RPC
 access to MH Checkup only, through the application proxy.  
  DATE ACTIVATED: SEP 14, 2017

NUMBER: 6679                            IA #: 6679
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ SCORE ADMIN
  REMOTE PROCEDURE: YTQ SCORE ADMIN
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ SCORE ADMIN Mental Health RPC.  
  
 The release of patch YS*5.01.123 changes the routine name called by the RPC. 
 The routine before patch YS*5.01*123 is  YTQAPI8, and the routine after the
 patch is YTQAPI23.  Input, output and tag name are not changed with this
 patch. The above changes are dependent upon the release of CPRS v31A.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This is approved as long as VIA restricts this RPC
 access to MH Checkup only, through the application proxy.  
  DATE ACTIVATED: SEP 18, 2017

NUMBER: 6680                            IA #: 6680
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ SCORE SAVE
  REMOTE PROCEDURE: YTQ SCORE SAVE
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ SCORE SAVE Mental Health RPC.  
  
 The release of patch YS*5.01.123 changes the routine name called by the RPC. 
 The routine before patch YS*5.01*123 is  YTQAPI11, and the routine after the
 patch is YTQAPI23.  Input, output and tag name are not changed with this
 patch.  The above changes are dependent upon the release of CPRS v31A.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This is approved as long as VIA restricts this RPC
 access to MH Checkup only, through the application proxy.  
  DATE ACTIVATED: SEP 18, 2017

NUMBER: 6681                            IA #: 6681
  DATE CREATED: DEC 08, 2016            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  NAME: YTQ PN CREATE                   REMOTE PROCEDURE: YTQ PN CREATE
 GENERAL DESCRIPTION:   The Mental Health Patient Reported Outcome (MHPRO)
 mobile application requests access to the YTQ PN CREATE Mental Health RPC.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO

NUMBER: 6682                            IA #: 6682
  DATE CREATED: DEC 13, 2016            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XLFJSON
  NAME: Decode/Encode JSON              ID: XLFJSON
 GENERAL DESCRIPTION:   This is a utility for decoding and encoding JSON.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: JSON
KEYWORDS: Encode
KEYWORDS: Escape
KEYWORDS: Unescape
COMPONENT/ENTRY POINT: ENCODE(XUROOT,XUJSON,XUERR)
 COMPONENT DESCRIPTION:   This API is used for converting a local or global
 array (M structure) into a JSON object.  
  
 Examples: 
                 
 D ENCODE^XLFJSON("^GLO(99,2)","^TMP($J)") 
                 
 D ENCODE^XLFJSON("LOCALVAR","MYJSON","LOCALERR") 
VARIABLES: XUROOT                       TYPE: Input
 VARIABLES DESCRIPTION:   Closed array reference for M representation of
 object.  
VARIABLES: XUJSON                       TYPE: Both
 VARIABLES DESCRIPTION:   Destination variable for the string array formatted
 as JSON.  
VARIABLES: XUERR                        TYPE: Both
 VARIABLES DESCRIPTION:   Contains error messages, defaults to
 ^TMP("XLFJERR",$J).  
COMPONENT/ENTRY POINT: DECODE(XUJSON,XUROOT,XUERR)
 COMPONENT DESCRIPTION:   This API is used for converting a JSON object into a
 local or global array (M structure).  
  
 Examples: 
  
 D DECODE^XLFJSON("MYJSON","LOCALVAR","LOCALERR") 
  
 D DECODE^XLFJSON("^MYJSON(1)","^GLO(99)","^TMP($J)") 
VARIABLES: XUJSON                       TYPE: Input
 VARIABLES DESCRIPTION:   String/array containing serialized JSON object.  
VARIABLES: XUROOT                       TYPE: Both
 VARIABLES DESCRIPTION:   Closed array reference for M representation of
 object.  
VARIABLES: XUERR                        TYPE: Both
 VARIABLES DESCRIPTION:   Contains error messages, defaults to
 ^TMP("XLFJERR",$J).  
COMPONENT/ENTRY POINT: $$ESC(STRING)
 COMPONENT DESCRIPTION:   This API is used for converting a text string to a
 JSON escaped string.  
  
 Example: 
  
 W $$ESC^XLFJSON("\one\two\three\") \\one\\two\\three\\ 
VARIABLES: STRING                       TYPE: Input
 VARIABLES DESCRIPTION:   String to be escaped to JSON.  
COMPONENT/ENTRY POINT: $$UES(STRING)
 COMPONENT DESCRIPTION:   This API is used for converting a JSON escaped string
 to a unescaped string.  
  
 Example: 
  
 W $$UES^XLFJSON("\\one\\two\\three\\") \one\two\three\ 
VARIABLES: STRING                       TYPE: Input
 VARIABLES DESCRIPTION:   JSON string to be unescaped.  
  DATE ACTIVATED: JUL 06, 2017

NUMBER: 6683                            IA #: 6683
  DATE CREATED: DEC 16, 2016
  CUSTODIAL PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  USAGE: Private                        TYPE: Remote Procedure
  NAME: MBAA LIST CANCELLATION REASONS 
 GENERAL DESCRIPTION:   This remote procedure call returns the list of
 cancellation reasons from the CANCELLATION REASONS file ($409.2).  
  
  STATUS: Pending
KEYWORDS: VIA
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: CANCEL
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6684                            IA #: 6684
  DATE CREATED: DEC 16, 2016
  CUSTODIAL PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  USAGE: Private                        TYPE: Remote Procedure
  NAME: MBAA VERIFY CLINIC ACCESS
 GENERAL DESCRIPTION:   This remote procedure call checks to see if the logon
 user has access to a clinic.  
  
  STATUS: Pending
KEYWORDS: MBAA
KEYWORDS: VIA
KEYWORDS: VAR
KEYWORDS: CLINIC
KEYWORDS: ACCESS
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6685                            IA #: 6685
  DATE CREATED: DEC 16, 2016
  CUSTODIAL PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  USAGE: Private                        TYPE: Remote Procedure
  NAME: MBAA APPOINTMENT LIST BY NAME
 GENERAL DESCRIPTION:   This remote procedure call returns a list of
 appointment types based on the input parameters from the Appointment Types
 file (#409.1).  
  
  STATUS: Pending
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: APPOINTMENT
KEYWORDS: VIA
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6686                            IA #: 6686
  DATE CREATED: DEC 16, 2016
  CUSTODIAL PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  USAGE: Private                        TYPE: Remote Procedure
  NAME: MBAA APPOINTMENT MAKE
 GENERAL DESCRIPTION:   This remote procedure call makes an appointment for a
 patient.  
  
  STATUS: Pending
KEYWORDS: VIA
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: APPOINTMENT
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6687                            IA #: 6687
  DATE CREATED: DEC 16, 2016
  CUSTODIAL PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  USAGE: Private                        TYPE: Remote Procedure
  NAME: MBAA FACILITY WAIT LIST
 GENERAL DESCRIPTION:   This remote procedure call will return the full
 Facility Electronic Wait List.  
  
  STATUS: Pending
KEYWORDS: VAR
KEYWORDS: VIA
KEYWORDS: MBAA
KEYWORDS: FACILITY
KEYWORDS: WAIT LIST
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6688                            IA #: 6688
  DATE CREATED: DEC 16, 2016
  CUSTODIAL PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  USAGE: Private                        TYPE: Remote Procedure
  NAME: MBAA CANCEL APPOINTMENT
 GENERAL DESCRIPTION:   This remote procedure call will return the full
 Facility Electronic Wait List.  
  
  STATUS: Pending
KEYWORDS: VIA
KEYWORDS: VAR
KEYWORDS: CANCEL
KEYWORDS: APPOINTMENT
KEYWORDS: MBAA
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6689                            IA #: 6689
  DATE CREATED: DEC 16, 2016
  CUSTODIAL PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  USAGE: Private                        TYPE: Remote Procedure
  NAME: MBAA PATIENT PENDING APPT
 GENERAL DESCRIPTION:   This remote procedure call returns data about pending
 appointments for a patient.  
  
  STATUS: Pending
KEYWORDS: VIA
KEYWORDS: VAR
KEYWORDS: PENDING
KEYWORDS: APPOINTMENT
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6690                            IA #: 6690
  DATE CREATED: DEC 16, 2016
  CUSTODIAL PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  USAGE: Private                        TYPE: Remote Procedure
  NAME: MBAA REMOVE FROM EWL
 GENERAL DESCRIPTION:   This remote procedure call removes a patient from the
 EWL.  
  
  STATUS: Pending
KEYWORDS: VIA
KEYWORDS: VAR
KEYWORDS: REMOVE
KEYWORDS: EWL
KEYWORDS: MBAA
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6691                            IA #: 6691
  DATE CREATED: DEC 16, 2016
  CUSTODIAL PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  USAGE: Private                        TYPE: Remote Procedure
  NAME: MBAA PROVIDERS BY CLINIC
 GENERAL DESCRIPTION:   This remote procedure takes input of the clinic id, IEN
 from the Hospital Location file (#44), and returns the list of providers
 assigned to that clinic.  The return data is the provider name and IEN for the
 provider from the New Person file (#200).  
  
  STATUS: Pending
KEYWORDS: VAR
KEYWORDS: VIA
KEYWORDS: CLINIC
KEYWORDS: PROVIDERS
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6692                            IA #: 6692
  DATE CREATED: DEC 16, 2016
  CUSTODIAL PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  USAGE: Private                        TYPE: Remote Procedure
  NAME: MBAA GET CLINIC AVAILABILITY
 GENERAL DESCRIPTION:   This remote procedure call returns the available slots
 for a clinic.  
  
  STATUS: Pending
KEYWORDS: VAR
KEYWORDS: VIA
KEYWORDS: CLINIC
KEYWORDS: AVAILABILITY
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6693                            IA #: 6693
  DATE CREATED: DEC 16, 2016
  CUSTODIAL PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  USAGE: Private                        TYPE: Remote Procedure
  NAME: MBAA GET CLINIC DETAILS
 GENERAL DESCRIPTION:   This remote procedure call returns clinic details
 needed for scheduling appointments into a clinic.  
  
  STATUS: Pending
KEYWORDS: VAR
KEYWORDS: VIA
KEYWORDS: CLINIC
KEYWORDS: DETAILS
KEYWORDS: GET
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6694                            IA #: 6694
  DATE CREATED: DEC 16, 2016
  CUSTODIAL PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
  USAGE: Private                        TYPE: Remote Procedure
  NAME: MBAA WAIT LIST BY DFN
 GENERAL DESCRIPTION:   This remote procedure call returns the EWL for a
 patient.  
  
  STATUS: Pending
KEYWORDS: VAR
KEYWORDS: VIA
KEYWORDS: WAIT LIST
KEYWORDS: DFN
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6695                            IA #: 6695
  DATE CREATED: DEC 21, 2016            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS BSE TOKEN
  REMOTE PROCEDURE: XUS BSE TOKEN
 GENERAL DESCRIPTION:   Provide Broker Security Enhancement (BSE) login string
 for Station-number authentication into a remote (visited) VistA system using
 credentials from a home (authenticating) VistA system.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BSE
KEYWORDS: TOKEN
KEYWORDS: XUS
KEYWORDS: AUTHENTICATION
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
 SUBSCRIBING DETAILS:   Enable BSE for Joint Legacy Viewer.  
  DATE ACTIVATED: MAY 25, 2017

NUMBER: 6696                            IA #: 6696
  GLOBAL ROOT: DD(404.43                DATE CREATED: JAN 03, 2017
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS TO DD(404.43        ID: DD(404.43
 GENERAL DESCRIPTION:   This is a onetime agreement via patch SD*5.3*659. 
 Scheduling requests read access to the following ^DD(404.43 nodes to obtain
 the cross reference numbers that will be deleted by the patch post-install
 routine.  
    ^DD(404.43,.01,1,   ^DD(404.43,.02,1,   ^DD(404.43,.03,1, 
    ^DD(404.43,.04,1,   ^DD(404.43,.05,1, 
  
 The patch post-install routine will delete the following cross references.
 These cross references are associated with HL7 messaging that PCMM no longer
 performs.  
  PATIENT TEAM POSITION ASSIGNMENT FILE (#404.43) 
   .01    PATIENT TEAM ASSIGNMENT 
      Xref-AEVENT1 
   .02    TEAM POSITION 
      Xref-AEVENT3 
   .03    POSITION ASSIGNED DATE 
      Xref-AEVENT4 
   .04    POSITION UNASSIGNED DATE 
      Xref-AEVENT5 
   .05    PC ROLE 
      Xref-AEVENT2 
  
 Code to delete cross references.  
  
 DELXREF(SDFILE,SDFIELD,SDXREFNM) ; Delete traditional cross reference 
  ;Inputs: SDFILE - file number 
  ;        SDFIELD - field number 
  ;        SDXREFNM - xref name 
  ;
  NEW SDHIT,SDOUT,SDERR,SDXREF 
  DO BMES^XPDUTL("Delete the "_SDXREFNM_" xref in "_SDFILE_"/"_SDFIELD_".") 
  ;
  SET SDHIT=0 
  SET SDXREF=0 
  FOR  SET SDXREF=$O(^DD(SDFILE,SDFIELD,1,SDXREF)) QUIT:('+SDXREF)!(SDHIT)  DO 
  . IF $GET(^DD(SDFILE,SDFIELD,1,SDXREF,0))[SDXREFNM DO 
  . . ;W !,"SDXREF: ",SDXREF,"   Node: ",^DD(SDFILE,SDFIELD,1,SDXREF,0),! 
  . . DO DELIX^DDMOD(SDFILE,SDFIELD,SDXREF,"","SDOUT","SDERR") 
  . . IF '$DATA(SDERR) DO 
  . . . DO MES^XPDUTL("The "_SDXREFNM_" cross reference was deleted.") 
  . . . SET SDHIT=1 
  . . ELSE  DO 
  . . . DO MES^XPDUTL("ERROR encountered deleting the "_SDXREFNM_" cross 
 reference.") 
  ;
  DO:'SDHIT MES^XPDUTL("The "_SDXREFNM_" cross reference was not found.") 
  ;
  QUIT 
  ;
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 20, 2018
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: FEB 02, 2017

NUMBER: 6697                            IA #: 6697
  DATE CREATED: JAN 05, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXR ISREL
  REMOTE PROCEDURE: ORWDXR ISREL
 GENERAL DESCRIPTION:   
  
  STATUS: Active
KEYWORDS: ORWDXR
KEYWORDS: ISREL
KEYWORDS: VAR
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 17, 2017

NUMBER: 6698                            IA #: 6698
  DATE CREATED: JAN 05, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDX1 ORDMATCH
  REMOTE PROCEDURE: ORWDX1 ORDMATCH     STATUS: Active
KEYWORDS: ORWDX1
KEYWORDS: ORDMATCH
KEYWORDS: VAR
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 17, 2017

NUMBER: 6699                            IA #: 6699
  DATE CREATED: JAN 05, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWOR PKISITE
  REMOTE PROCEDURE: ORWOR PKISITE
 GENERAL DESCRIPTION:   The RPC determines if PKI is turned on at the site.  
  
  STATUS: Active
KEYWORDS: ORWOR
KEYWORDS: PKISITE
KEYWORDS: VAR
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 17, 2017

NUMBER: 6700                            IA #: 6700
  DATE CREATED: JAN 05, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXC SAVECHK
  REMOTE PROCEDURE: ORWDXC SAVECHK
 GENERAL DESCRIPTION:   
  
  STATUS: Active
KEYWORDS: ORWDXC
KEYWORDS: SAVECHK
KEYWORDS: VAR
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   As of 2/13/17, Veterans Appointment Request (VAR) is
 using this RPC through the VistA Integration Adaptor's (VIA) OrderMgmt
 Service.  
  DATE ACTIVATED: FEB 13, 2017

NUMBER: 6701                            IA #: 6701
  DATE CREATED: JAN 05, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWUL FVSUB
  REMOTE PROCEDURE: ORWUL FVSUB
 GENERAL DESCRIPTION:   The RPC returns a subset of orders in view.  
  
  STATUS: Active
KEYWORDS: ORWUL
KEYWORDS: FVSUB
KEYWORDS: VAR
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 14, 2017

NUMBER: 6702                            IA #: 6702
  DATE CREATED: JAN 05, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXR ISCPLX
  REMOTE PROCEDURE: ORWDXR ISCPLX
 GENERAL DESCRIPTION:   The RPC returns 1 is complex order or  0 is not a
 complex order.  
  
  STATUS: Active
KEYWORDS: ORWDXR
KEYWORDS: ISCPLX
KEYWORDS: VAR
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 17, 2017

NUMBER: 6703                            IA #: 6703
  DATE CREATED: JAN 05, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWORDG ALLTREE
  REMOTE PROCEDURE: ORWORDG ALLTREE
 GENERAL DESCRIPTION:   
  
  STATUS: Active
KEYWORDS: ORWORDG
KEYWORDS: ALLTREE
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 14, 2017

NUMBER: 6704                            IA #: 6704
  DATE CREATED: JAN 05, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWORDG REVSTS
  REMOTE PROCEDURE: ORWORDG REVSTS
 GENERAL DESCRIPTION:   
  
  STATUS: Active
KEYWORDS: ORWORDG
KEYWORDS: REVSTS
KEYWORDS: VAR
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 14, 2017

NUMBER: 6705                            IA #: 6705
  DATE CREATED: JAN 06, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXR GETPKG
  REMOTE PROCEDURE: ORWDXR GETPKG
 GENERAL DESCRIPTION:   RPC returns the package for an order.  
  
  STATUS: Active
KEYWORDS: ORWDXR
KEYWORDS: GETPKG
KEYWORDS: VAR
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 14, 2017

NUMBER: 6706                            IA #: 6706
  DATE CREATED: JAN 06, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: OREVNTX1 ODPTEVID
  REMOTE PROCEDURE: OREVNTX1 ODPTEVID
 GENERAL DESCRIPTION:   RPC returns the event the order was delayed for.  
  
  STATUS: Active
KEYWORDS: OREVNTX1
KEYWORDS: ODPTEVID
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 22, 2017

NUMBER: 6707                            IA #: 6707
  DATE CREATED: JAN 06, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDRA32 ISOLATN
  REMOTE PROCEDURE: ORWDRA32 ISOLATN
 GENERAL DESCRIPTION:   RPC returns a value if patient has active isolation
 order (or 0 if not).  
  
  STATUS: Active
KEYWORDS: ORWDRA32
KEYWORDS: ISOLATN
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 14, 2017

NUMBER: 6708                            IA #: 6708
  DATE CREATED: JAN 06, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDPS2 CHKPI
  REMOTE PROCEDURE: ORWDPS2 CHKPI
 GENERAL DESCRIPTION:   RPC returns pre-existing patient instructions.  
  
  STATUS: Active
KEYWORDS: ORWDPS2
KEYWORDS: CHKPI
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 14, 2017

NUMBER: 6709                            IA #: 6709
  DATE CREATED: JAN 06, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORIMO IMOOD
  REMOTE PROCEDURE: ORIMO IMOOD
 GENERAL DESCRIPTION:   RPCS returns - Is it an IMO order? 
  
  STATUS: Active
KEYWORDS: ORIMO
KEYWORDS: IMOOD
KEYWORDS: VAR
KEYWORDS: MBAA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: FEB 17, 2017

NUMBER: 6710                            IA #: 6710
  DATE CREATED: JAN 06, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWD2 MANUAL
  REMOTE PROCEDURE: ORWD2 MANUAL        STATUS: Active
KEYWORDS: ORWD2
KEYWORDS: MANUAL
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9. 
  DATE ACTIVATED: FEB 21, 2017

NUMBER: 6711                            IA #: 6711
  DATE CREATED: JAN 06, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWUL FVIDX
  REMOTE PROCEDURE: ORWUL FVIDX
 GENERAL DESCRIPTION:   RPC returns index of item beginning with FROM
 parameter.  
  
  STATUS: Active
KEYWORDS: ORWUL
KEYWORDS: FVIDX
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 21, 2017

NUMBER: 6712                            IA #: 6712
  DATE CREATED: JAN 06, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWUL FV4DG
  REMOTE PROCEDURE: ORWUL FV4DG
 GENERAL DESCRIPTION:   RPC returns the current full list and item count.  
  
  STATUS: Active
KEYWORDS: ORWUL
KEYWORDS: FV4DG
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 21, 2017

NUMBER: 6713                            IA #: 6713
  DATE CREATED: JAN 06, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDPS5 LESGRP
  REMOTE PROCEDURE: ORWDPS5 LESGRP
 GENERAL DESCRIPTION:   RPC checks and returns the orders belonging to the
 following display group 
   1.  LAB/LABORATORY  ORDERS 
   2.  BLOOD BANK      ORDERS 
   3.  CHEMISTRY       ORDERS 
  
  STATUS: Active
KEYWORDS: ORWDPS5
KEYWORDS: LESGRP
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 21, 2017

NUMBER: 6714                            IA #: 6714
  DATE CREATED: JAN 06, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDPS2 CHKGRP
  REMOTE PROCEDURE: ORWDPS2 CHKGRP
 GENERAL DESCRIPTION:   RPC will 
  - return 1: Inpatient Med Order Group or Clin Meds Group 
  - return 2: If order belong to Outpatient Med Order Group 
  - return 0: Otherwise 
  
  STATUS: Active
KEYWORDS: ORWDPS2
KEYWORDS: CHKGRP
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 21, 2017

NUMBER: 6715                            IA #: 6715
  DATE CREATED: JAN 06, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWORR GETTXT
  REMOTE PROCEDURE: ORWORR GETTXT       STATUS: Active
KEYWORDS: ORWORR
KEYWORDS: GETTXT
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 22, 2017

NUMBER: 6716                            IA #: 6716
  DATE CREATED: JAN 06, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDRA32 PROCMSG
  REMOTE PROCEDURE: ORWDRA32 PROCMSG
 GENERAL DESCRIPTION:   RPC returns order message for a procedure.  
  
  STATUS: Active
KEYWORDS: ORWDRA32
KEYWORDS: PROCMSG
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 22, 2017

NUMBER: 6717                            IA #: 6717
  DATE CREATED: JAN 06, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDXM FORMID
  REMOTE PROCEDURE: ORWDXM FORMID       STATUS: Active
KEYWORDS: ORWDXM
KEYWORDS: FORMID
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9.  
  DATE ACTIVATED: FEB 22, 2017

NUMBER: 6718                            IA #: 6718
  DATE CREATED: JAN 06, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: OREVNTX1 DLGIEN
  REMOTE PROCEDURE: OREVNTX1 DLGIEN
 GENERAL DESCRIPTION:   RPC returns Order Dialog IEN based on name.  
  
  STATUS: Active
KEYWORDS: OREVNTX1
KEYWORDS: DLGIEN
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
 SUBSCRIBING DETAILS:   Veterans Appointment Request (VAR) is using this RPC
 through the VistA Integration Adaptor's (VIA) OrderMgmt Service beginning with
 VIAB*1*9. 
  DATE ACTIVATED: FEB 21, 2017

NUMBER: 6719                            IA #: 6719
  DATE CREATED: JAN 11, 2017            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOORCPY
  NAME: OE/RR CALL TO PSOORCPY          ID: PSOORCPY
 GENERAL DESCRIPTION:   The Order Entry/Results Reporting would like approval
 to call the extrinsic function $$ORCOPY^PSOORCPY(Placer).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSOORCPY
COMPONENT/ENTRY POINT: $$ORCOPY(PLACER)
 COMPONENT DESCRIPTION:   Extrinsic function to determine whether an order can
 be copied or not.  
VARIABLES: PLACER                       TYPE: Input
 VARIABLES DESCRIPTION:   CPRS Placer, which can be a pointer to the
 PRESCRIPTION file (#52) or the OUTPATIENT PENDING ORDER file (#52.41). If the
 value is numeric only it is assumed to be a pointer to the PRESCRIPTION file
 (#52), otherwise if the value is appended with the letter "S" at the end it
 means the numeric part of the input parameter is a pointer to the PENDING
 OUTPATIENT ORDER file (#52.41).  
VARIABLES: $$ORCOPY                     TYPE: Output
 VARIABLES DESCRIPTION:   Returns "-1^Not a Valid Outpatient Medication Order."
 if the prescription record cannot be found.  
  
 Returns "0^<Reason>" if the order cannot be copied (e.g., "0^This Drug has
 been Inactivated.") 
  
 Returns "1" if the order can be copied.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JUL 10, 2017

NUMBER: 6720                            IA #: 6720
  DATE CREATED: JAN 13, 2017
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA6720
  STATUS: Pending

NUMBER: 6721                            IA #: 6721
  GLOBAL ROOT: DD(404.52                DATE CREATED: JAN 20, 2017
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS TO DD(404.52        ID: DD(404.52
 GENERAL DESCRIPTION:   This is a onetime agreement via patch SD*5.3*659. 
 Scheduling requests read access to the following ^DD(404.52 nodes to obtain
 the cross reference numbers that will be deleted by the patch post-install
 routine. 
    ^DD(404.52,.01,1, ^DD(404.52,.02,1, ^DD(404.52,.03,1, 
    ^DD(404.52,.04,1, ^DD(404.52,.09,1, 
     
 The patch post-install routine will delete the following cross references.  
 These cross references are associated with HL7 messaging that PCMM no longer
 performs.  
     POSITION ASSIGNMENT HISTORY FILE (#404.52) 
      .01    TEAM POSITION 
         Xref-AEVENT1 
      .02    EFFECTIVE DATE 
         Xref-AEVENT2 
      .03    PRACTITIONER 
         Xref-AEVENT3 
      .04    STATUS 
         Xref-ASTATUS 
      .09    FTEE EQUIVALENT 
         Xref-AFTEE 
     
    Code to delete cross references.  DELXREF(SDFILE,SDFIELD,SDXREFNM) ; Delete
 traditional cross reference 
     ;Inputs: SDFILE - file number 
     ; SDFIELD - field number 
     ; SDXREFNM - xref name 
     ;
     NEW SDOUT,SDERR,SDXREF 
     DO BMES^XPDUTL("Delete the "_SDXREFNM_" xref in "_SDFILE_"/"_SDFIELD_".") 
     ;
     SET SDXREF=0 
     FOR  SET SDXREF=$O(^DD(SDFILE,SDFIELD,1,SDXREF)) QUIT:'+SDXREF  DO 
     . IF $GET(^DD(SDFILE,SDFIELD,1,SDXREF,0))[SDXREFNM DO 
     . . ;W !,"SDXREF: ",SDXREF," Node: ",^DD(SDFILE,SDFIELD,1,SDXREF,0),! 
     . . DO DELIX^DDMOD(SDFILE,SDFIELD,SDXREF,"","SDOUT","SDERR") 
     . . IF '$DATA(SDERR) DO 
     . . . DO MES^XPDUTL("The "_SDXREFNM_" cross reference was deleted.") 
     . . ELSE  DO 
     . . . DO MES^XPDUTL("ERROR encountered deleting the "_SDXREFNM_" cross
 reference.") 
     QUIT 
     ;
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 20, 2018
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: FEB 02, 2017

NUMBER: 6722                            IA #: 6722
  GLOBAL ROOT: DD(404.53                DATE CREATED: JAN 20, 2017
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS TO DD(404.53        ID: DD(404.53
 GENERAL DESCRIPTION:   This is a onetime agreement via patch SD*5.3*659. 
 Scheduling requests read access to the following ^DD(404.53 nodes to obtain
 the cross reference numbers that will be deleted by the patch post-install
 routine.  
    ^DD(404.53,.01,1, ^DD(404.53,.02,1, ^DD(404.53,.04,1, 
    ^DD(404.53,.06,1, The patch post-install routine will delete the following
 cross references. These cross references are associated with HL7 messaging
 that PCMM no longer performs.  
  
     PRECEPTOR ASSIGNMENT HISTORY FILE (#404.53) 
      .01    TEAM POSITION 
         Xref-AEVENT1 
      .02    EFFECTIVE DATE 
         Xref-AEVENT2 
      .04    STATUS 
         Xref-AEVENT3 
      .06    PRECEPTOR TEAM POSITION 
         Xref-AEVENT4 
     
    Code to delete cross references.  DELXREF(SDFILE,SDFIELD,SDXREFNM) ; Delete
 traditional cross reference 
     ;Inputs: SDFILE - file number 
     ; SDFIELD - field number 
     ; SDXREFNM - xref name 
     ;
     NEW SDOUT,SDERR,SDXREF 
     DO BMES^XPDUTL("Delete the "_SDXREFNM_" xref in "_SDFILE_"/"_SDFIELD_".") 
     ;
     SET SDXREF=0 
     FOR  SET SDXREF=$O(^DD(SDFILE,SDFIELD,1,SDXREF)) QUIT:'+SDXREF  DO 
     . IF $GET(^DD(SDFILE,SDFIELD,1,SDXREF,0))[SDXREFNM DO 
     . . ;W !,"SDXREF: ",SDXREF," Node: ",^DD(SDFILE,SDFIELD,1,SDXREF,0),! 
     . . DO DELIX^DDMOD(SDFILE,SDFIELD,SDXREF,"","SDOUT","SDERR") 
     . . IF '$DATA(SDERR) DO 
     . . . DO MES^XPDUTL("The "_SDXREFNM_" cross reference was deleted.") 
     . . ELSE  DO 
     . . . DO MES^XPDUTL("ERROR encountered deleting the "_SDXREFNM_" cross 
    reference.") 
     QUIT 
     ;
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 20, 2018
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: FEB 02, 2017

NUMBER: 6723                            IA #: 6723
  FILE NUMBER: 4                        GLOBAL ROOT: DIC(4,
  DATE CREATED: JAN 23, 2017            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA 6723
  ID: DIC(4,
GLOBAL REFERENCE: DIC(4,'LOC'
 GLOBAL DESCRIPTION:   Cross-reference holds entries whose CURRENT LOCATION
 field is set to 'yes'.  
 GENERAL DESCRIPTION:   Event Capture requests permission to delete and rebuild
 the "LOC" cross-reference in the INSTITUTION file (#4).  
  
 Due to an issue resulting from changing the name of an entry in the 
 INSTITUTION file, the "LOC" cross-reference may no longer show the correct
 facility name in the "LOC" cross-reference.  
  
 As a result, a direct kill of the cross-reference, using K ^DIC(4,"LOC") is
 needed to completely delete the table as the KILL logic of the cross-reference
 will not correctly remove incorrectly named entries.  
  
 After manually killing the cross-reference, a call to ENALL^DIK will be made
 to rebuild the cross-reference using the most up-to-date facility names.  
  
 This request is for a one-time deletion and rebuild of the cross-reference in
 the post-install process of patch EC*2.0*134.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: EVENT CAPTURE
 SUBSCRIBING DETAILS:   This request is for a one-time deletion and rebuild of
 the "LOC" cross-reference via patch EC*2.0*134.  
  DATE ACTIVATED: AUG 14, 2017

NUMBER: 6724                            IA #: 6724
  DATE CREATED: JAN 25, 2017            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LR7OSUM2
  NAME: LR7OSUM2                        ID: LR7OSUM2
 GENERAL DESCRIPTION:   For CPRS v32 development, the OR and GMTS packages need
 access to an existing lab report API, $$PLSADDR^LR7OSUM2, which has also been
 modified for CPRS v32. The modification is to allow an optional effective date
 to be passed, so the correct current or archived facility address will be 
 pulled based on that date. These changes are all related to NSR 20081206 and
 will be part of the CPRS v32 bundled release.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: $$PLSADDR
COMPONENT/ENTRY POINT: PLSADDR
 COMPONENT DESCRIPTION:   This function returns the correct historical physical
 address information, if available, for an Institution in an up-arrow delimited
 string (name [CLIA# nnnn] ^ address of institution) for a given Internal Entry
 Number and Effective Date. If no historical physical address information is 
 available based on the ien and effective date, the current physical address
 will be returned.  
VARIABLES: LRPLS                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number of entry in file #4 
VARIABLES: LREDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Effective Date for Historical Address search 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: JUL 11, 2017

NUMBER: 6725                            IA #: 6725
  DATE CREATED: JAN 25, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORCDPS3                      NAME: VIAB CALL TO FIRST~ORCDPS3
  ID: ORCDPS3
 GENERAL DESCRIPTION:   VIAB makes a call to the FIRST^ORCDPSA3 API to get the
 expected first admin time for an order.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ORCDPS3
KEYWORDS: VIAB
COMPONENT/ENTRY POINT: FIRST
 COMPONENT DESCRIPTION:   Returns the expected first admin time for an order.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient DFN.  
VARIABLES: WARD                         TYPE: Input
 VARIABLES DESCRIPTION:   The patient's ward.  
VARIABLES: OI                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN for the record in the Orderable Items file
 (#101.43).  
VARIABLES: SCH                          TYPE: Input
 VARIABLES DESCRIPTION:   Admin Schedule 
VARIABLES: ORDER                        TYPE: Input
 VARIABLES DESCRIPTION:   The order number.  
VARIABLES: ADMIN                        TYPE: Input
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6726                            IA #: 6726
  FILE NUMBER: 101.41                   GLOBAL ROOT: ORD(101.41
  DATE CREATED: JAN 26, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: File
  NAME: VIAB FILE READS OF 101.416      ID: ORD(101.41
GLOBAL REFERENCE: ORD(101.41,'B'
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The Order Dialog Name.  
GLOBAL REFERENCE: ORD(101.41,D0,6,'D',D1
FIELD NUMBER: .02                       FIELD NAME: POINTER TO ORDER DIALOG FILE
  LOCATION: 6;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is the ponter to the Order Dialog for this
 Order Item. VIAB is using this look up to find the record in the Responses
 Multiple for the Orderable Item.  
FIELD NUMBER: .01                       FIELD NAME: ORDER ITEM
  LOCATION: 6;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   VIAB uses this field to insure the right entry is
 retrieved by comparing this field to the RPC input parameter.  
GLOBAL REFERENCE: ORD(101.41,D0,0
FIELD NUMBER: 5                         FIELD NAME: DISPLAY GROUP
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the pointer to the DISPLAY GROUP FILE (#100.98)
 that has been defined for this Order Dialog.  
 GENERAL DESCRIPTION:   The VistA Integration Adaptor (VIAB) VIABDPS2 OISLCT
 RPC is retrieving data from the ORDER DIALOG FILE (#101.41) RESPONSE MULTIPLE
 (#101.416) in order retrieve the default dialogs for pharmacy orderable items. 
 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: VIAB
KEYWORDS: 101.41
KEYWORDS: 1O1.416
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6727                            IA #: 6727
  FILE NUMBER: 101.43                   GLOBAL ROOT: ORD(101.43,
  DATE CREATED: JAN 26, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: File
  NAME: VIAB ACCESS TO FILE 101.43      ID: ORD(101.43,
GLOBAL REFERENCE: ORD(101.43,D0,0
FIELD NUMBER: 5                         FIELD NAME: DISPLAY GROUP
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the display group defined for the order dialog.  
FIELD NUMBER: 2                         FIELD NAME: ID 
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is a unique identified for this item, created from
 the primary key passed in the Orderable Items update message from each
 package; it will be in the form of 'package code;99XXX' where XXX indicates
 the package tabble originating this item (i.e. RAP, LRT, etc).  
GLOBAL REFERENCE: ORD(101.43,D0,8
FIELD NUMBER: .01                       FIELD NAME: ORDER MESSAGE
  LOCATION: 8;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains the text that is to be displayed to
 the user whenever this item is selected to order.  
 GENERAL DESCRIPTION:   The VistA Integration Adaptor (VIAB) VIABDPS2 OISLCT
 RPC is accessing the ORDERABLE ITEMS FILE (#101.43) to retrieve data for the
 default order dialog for a pharmacy orderable item.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: VIAB
KEYWORDS: ORD(101.43
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6728                            IA #: 6728
  FILE NUMBER: 60                       GLOBAL ROOT: LAB(60,
  DATE CREATED: JAN 26, 2017            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: VIAB LOAD                       ID: LAB(60,
GLOBAL REFERENCE: LAB(60,D0,0)
FIELD NUMBER: 4                         FIELD NAME: SUBSCRIPT
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LAB(60,'B'
 GLOBAL DESCRIPTION:   The 'B' cross-reference is used to determine the IEN of
 the Laboratory Test Name.  
  
 GENERAL DESCRIPTION:   VIAB needs to read Field #4 (SUBSCRIPT) and the "B"
 cross-reference of File #60 for VIAB LOAD RPC.  
  
  STATUS: Withdrawn
KEYWORDS: SUBSCRIPT
KEYWORDS: VIA
KEYWORDS: LAB
KEYWORDS: LOAD
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6729                            IA #: 6729
  DATE CREATED: JAN 26, 2017            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: MD CLIO
  REMOTE PROCEDURE: MD CLIO
 GENERAL DESCRIPTION:   
  
  STATUS: Active
KEYWORDS: MD
KEYWORDS: CLIO
KEYWORDS: VIA
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA needs to call MD CLIO RPC to use the following two
 RPC OPTIONS.  
   
 OPTION =ROLES returns a list of user roles from VistA: 
   D RPC^MDCLIO(.RESULTS,"ROLES") 
  
 OPTION=SRVRDT returns the server date and time: 
   D RPC^MDCLIO(.RESULTS,"SRVRDT") 
  
  DATE ACTIVATED: FEB 28, 2017

NUMBER: 6730                            IA #: 6730
  FILE NUMBER: 130                      GLOBAL ROOT: SRF(
  DATE CREATED: JAN 26, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VIAB SRGY RPTLIST
  ID: SRF(
GLOBAL REFERENCE: SRF(D0,0)
FIELD NUMBER: .04                       FIELD NAME: SURGERY SPECIALTY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: SRF(D0,9,0)
FIELD NUMBER: 49                        FIELD NAME: SPECIMENS
  LOCATION: 9;0                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VIA needs to read a number of fields from Surgery File
 #130 for VIAB SRGY RPTLIST RPC.  
  STATUS: Active
KEYWORDS: SURGERY
KEYWORDS: REPORT
KEYWORDS: LIST
KEYWORDS: VIA
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
  DATE ACTIVATED: MAR 09, 2017

NUMBER: 6731                            IA #: 6731
  DATE CREATED: JAN 30, 2017
  CUSTODIAL PACKAGE: ENTERPRISE TERMINOLOGY SERVICE
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ETSLNC
  NAME: ETSLNC                          ID: ETSLNC
 GENERAL DESCRIPTION:   These API(s) allow access to the LOINC data that is
 contained in the LOINC files in the Enterprise Terminology Services (ETS)
 package.  
  STATUS: Active
KEYWORDS: CSDATA
KEYWORDS: CSYS
KEYWORDS: PERIOD
KEYWORDS: HIST
KEYWORDS: TAX
KEYWORDS: CHKCODE
KEYWORDS: GETCODE
KEYWORDS: GETNAME
KEYWORDS: GETSTAT
KEYWORDS: GETREC
KEYWORDS: VERSION
KEYWORDS: COMLST
KEYWORDS: DEPLIST
KEYWORDS: LOINC
COMPONENT/ENTRY POINT: $$CHKCODE(ETSCODE)
 COMPONENT DESCRIPTION:   This API checks to see if the LOINC code is in the
 LOINC (#129.1) file.  
  
 Example: 
   W $$CHKCODE^ETSLNC(42012) 
   1 
VARIABLES: ETSCODE                      TYPE: Input
 VARIABLES DESCRIPTION:   LOINC CODE (#.01) field from the LOINC (#129.1) file 
VARIABLES: $$CHKCODE                    TYPE: Output
 VARIABLES DESCRIPTION:   Output value to the function.  Either: 
    1 - successful check 
    0 - does not exist 
       or 
   -1^<error message> - error occurred 
COMPONENT/ENTRY POINT: $$COMLST(ETSCOM,ETSSUB)
 COMPONENT DESCRIPTION:   This API retrieves a list of LOINC codes for a
 passed-in component.  It returns both the CODE (#.01) and FULLY SPECIFIED NAME
 (#80) fields from the LOINC (#129.1) file.  
  
 If $$COMLST^ETSLNC returns a 1 (valid results found), the following global is
 also returned, where <ETSSUB> is the value passed in as the second parameter
 and the fourth subscript is equal to the CODE (#.01) field from the LOINC
 (#129.1) file.  
  
 ^TMP(<ETSSUB>,$J,"COMP",<CODE>)=FULLY SPECIFIED NAME (#80) field 
  
 Example: 
  >W $$COMLST^ETSLNC(3,"OUT") 
  1 
  
  >D ^%G 
  Global ^TMP("OUT",$J 
 ^TMP("OUT",857,"COMP",2)="ALMECILLIN:SUSC:PT:ISOLATE:QN:MLC" 
                       3)="ALMECILLIN:SUSC:PT:ISOLATE:ORDQN:MIC" 
                       4)="ALMECILLIN:SUSC:PT:ISOLATE:ORDQN:AGAR DIFFUSION" 
                       5)="ALMECILLIN:TITR:PT:ISOLATE+SER:QN:SBT" 
                   18857)="ALMECILLIN:SUSC:PT:ISOLATE:ORDQN:" 
VARIABLES: ETSCOM                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN from the LOINC COMPONENT (#129.11) file.  
VARIABLES: ETSSUB                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter used to specify the subscript used
 to store the data in.  If not passed in, the default is "ETSCOMP".  
VARIABLES: $$COMLST                     TYPE: Output
 VARIABLES DESCRIPTION:   One of the following three values: 
    0 - Component not used 
    1 - Success, results returned 
        or 
   -1^<error message> - Error 
COMPONENT/ENTRY POINT: $$CSDATA(ETSCODE,ETSSYS,ETSCDT,ARY)
 COMPONENT DESCRIPTION:   This API retrieves information for a specific code in
 a database. Note that this API was modeled after a Lexicon API with a similar
 name, and the input and output value match the format of that API as much as 
 possible.  
  
 Example: 
  >W $$CSDATA^ETSLNC(1,"LNC",3160101,.ARY) 
  1 
  
  >ZW ARY 
  ARY("LEX",1)="1^ACYCLOVIR:SUSC:PT:ISOLATE:ORDQN:" 
  ARY("LEX",1,"N")="IEN ^ Fully Specified Name" 
  ARY("LEX",2)="1^3150629" 
  ARY("LEX",2,"N")="Status ^ Effective Date" 
  ARY("LEX",8)="" 
  ARY("LEX",8,"N")="Deactivated Concept" 
  ARY("SYS",1)=1 
  ARY("SYS",1,"N")="IEN" 
  ARY("SYS",2)="ACYCLOVIR [SUSCEPTIBILITY]" 
  ARY("SYS",2,"N")="Long Common Name" 
VARIABLES: ETSCODE                      TYPE: Input
 VARIABLES DESCRIPTION:   CODE (#.01) field from the LOINC (#129.1) file 
VARIABLES: ETSSYS                       TYPE: Input
 VARIABLES DESCRIPTION:   This optional parameter is the coding System to
 perform the lookup on. For LOINC, "LNC" is the only valid value to send. If
 not passed in, defaults to "LNC".  
VARIABLES: ETSCDT                       TYPE: Input
 VARIABLES DESCRIPTION:   This optional parameter is the date in Fileman Format
 used to evaluate the status. If not passed in, defaults to TODAY.  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   This is a pass-by-reference parameter used to
 indicate the array to return the output results.  
  
 The output is returned as: 
  ARY("LEX",1): Two pieces of data - IEN^FULLY SPECIFIED NAME (#80) 
  ARY("LEX",1,"N"): "IEN ^ Fully Specified Name" 
  ARY("LEX",2): Two pieces of data from the ACTIVATION STATUS subfile - 
 ACTIVATION STATUS (#1)^ACTIVATION EFFECTIVE DATE (#.01) 
  ARY("LEX",2,"N"): "Status ^ Effective Date" 
  ARY("LEX",8): Either Null (Active) or 1 (Inactive) 
  ARY("LEX",8,"N"): "Deactivated Concept" 
  ARY("SYS",1): IEN 
  ARY("SYS",1,"N"): "IEN" 
  ARY("SYS",2): LONG COMMON NAME (#83) 
  ARY("SYS",2,"N"): "Long Common Name" 
  *Note that the "N" values are the description of the output 
VARIABLES: $$CSDATA                     TYPE: Output
 VARIABLES DESCRIPTION:   One of three values: 
    1 - Successful (code exist in LOINC dictionary) 
    0 - Unsuccessful 
        or 
   -1^<message> - Error 
COMPONENT/ENTRY POINT: $$CSYS(ETSYS)
 COMPONENT DESCRIPTION:   This API returns coding system information for LOINC.
 Note that this API was modeled after a Lexicon API with a similar name, and
 the input and output value match the format of that API as much as possible.  
  
 Example: 
  >W $$CSYS^ETSLNC() 
  ^LNC^LNC^LOINC^Logical Observation Identifier Names and Codes^ Duke
 University Medical Center^^^^^^2.52^3150629^20000 
VARIABLES: ETSSYS                       TYPE: Input
 VARIABLES DESCRIPTION:   This optional parameter has the coding system to
 perform the Lookup on.  For LOINC, the only valid value is "LNC". If not
 passed in, defaults to "LNC".  
VARIABLES: $$CSYS                       TYPE: Output
 VARIABLES DESCRIPTION:   A delimited string of code system information 
    1. Not used 
    2. Three-character Source Abbreviation 
    3. Source Abbreviation 
    4. Nomenclature 
    5. Source Title 
    6. Source 
    7. Not used 
    8. Not used 
    9. Not used 
   10. Not used 
   11. Not used 
   12. Version ID 
   13. Implementation Date 
   14. Lookup Threshold 
COMPONENT/ENTRY POINT: $$DEPLST(ETSSUB)
 COMPONENT DESCRIPTION:   This API retrieves the list of deprecated LOINC
 codes.  
  
 The API returns the list of deprecated LOINC codes in a TMP global with the
 first subscript of the TMP specified as a parameter to the function and the
 fourth subscript equal to CODE (#.01) field from the LOINC (#129.1) file.  
  
 If there are deprecated codes, they are returned as: 
  
 ^TMP(<ETSSUB>,$J,"DEPRECATED",<CODE>)=FULLY SPECIFIED NAME (#80) field 
  
 Example: 
  >W $$DEPLST^ETSLNC("SAB") 
  1 
  
  >D ^%G 
  Global ^TMP("SAB",$J 
  ^TMP("SAB",127896,"DEPRECATED",1)="ACYCLOVIR:SUSC:PT:ISOLATE:ORDQN:" 
VARIABLES: ETSSUB                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter that indicates the subscript for
 the Temporary Deprecated List Array.  If not passed in, defaults to "ETSDEP".  
VARIABLES: $$DEPLST                     TYPE: Output
 VARIABLES DESCRIPTION:   One of three possible values: 
    0 - Component Not used 
    1 - Success, results returned 
        or 
   -1^<error message> - Error 
COMPONENT/ENTRY POINT: $$GETCODE(ETSIEN)
 COMPONENT DESCRIPTION:   This API retrieves the LOINC code for the IEN that is
 passed in.  
  
 Example: 
  >W $$GETCODE^ETSLNC(38553) 
  38553 
VARIABLES: ETSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN from the LOINC (#129.1) file.  
VARIABLES: $$GETCODE                    TYPE: Output
 VARIABLES DESCRIPTION:   Return one of two possible values: 
    CODE (#.01) field from LOINC (#129.1) file 
        or 
    -1^<error message> 
COMPONENT/ENTRY POINT: $$GETNAME(ETSINPT,ETSINTY,.NAME)
 COMPONENT DESCRIPTION:   This API retrieves the LOINC Name Array, which
 includes the FULLY SPECIFIED NAME (#80) and LONG COMMON NAME (#83) fields from
 the LOINC (#129.1) file.  
  
  
 Example: 
  >W $$GETNAME^ETSLNC(3,"C",.NAME) 
  1 
  
  >ZW NAME 
  NAME("FULLNAME")="ALMECILLIN:SUSC:PT:ISOLATE:ORDQN:MIC" 
  NAME("LONGNAME")="ALMECILLIN - BY TEST [SUSCEPTIBILITY] BY MINIMUM INHIBITORY
 CONCENTRATION (MIC)" 
VARIABLES: ETSINPT                      TYPE: Input
 VARIABLES DESCRIPTION:   LOINC Code or IEN 
VARIABLES: ETSINTY                      TYPE: Input
 VARIABLES DESCRIPTION:   Input Type of the first parameter.  If not passed in,
 it defaults to "C". Possible values are: 
     "C"=LOINC Code 
     "I"=LOINC IEN 
VARIABLES: .NAME                        TYPE: Both
 VARIABLES DESCRIPTION:   Pass by reference parameter that specifies the array
 to return the LOINC name values.  
  
 The return array has two subscripts: 
      NAME("FULLNAME")=FULLY SPECIFIED NAME (#80) field 
      NAME("LONGNAME")=LONG COMMON NAME (#83) field 
VARIABLES: $$GETNAME                    TYPE: Output
 VARIABLES DESCRIPTION:   This is the return value of the function.  It can
 have one of three values: 
    0 - Code or IEN not found 
    1 - Successfully retrieve Name information 
        or 
   -1^<error message> - Error 
COMPONENT/ENTRY POINT: $$GETREC(ETSINPT,ETSINTY,ETSSUB)
 COMPONENT DESCRIPTION:   This API retrieves all information about the LOINC
 CODE or IEN.  
  
 If the lookup was successful, the API will return the data in a TMP global
 with the first subscript value determined by the input of the ETSSUB
 parameter.  The TMP global will have the following format with the data on
 each node being the data for that respective field.  
  
 ^TMP(<ETSSUB>,$J,"RECORD","ACTIVATION HISTORY",#,"ACTIVATION EFFECTIVE DATE") 
                                                  "ACTIVATION 
 HISTORY",#,"ACTIVATION STATUS") ^TMP(<ETSSUB>,$J,"RECORD","ADJUSTMENT") 
                           "CHALLENGE") 
                           "CHANGE REASON") 
                           "CHANGE TYPE") 
                           "CHECK DIGIT") 
                           "CLASS") 
                           "CLASSTYPE") 
                           "CODE") 
                           "COMMENTS") or "COMMENTS",#) 
                           "DATE LAST CHANGED") 
                           "EXAMPLE UCUM UNITS") 
                           "FULLY SPECIFIED NAME") 
                           "IEN") 
                           "LONG COMMON NAME") 
                           "MASTER ENTRY FOR VUID") 
                           "METHOD TYPE") 
                           "NON-PATIENT SPECIMEN") 
                           "PROPERTY") 
                           "REPEAT OBSERVATION") 
                           "SCALE TYPE") 
                           "SHORTNAME") 
                           "SNOMED CODE") 
                           "SOURCE") 
                           "SYSTEM") 
                           "TIME ASPECT") 
                           "TIME MODIFIER") 
                           "UNITS") 
                           "VA COMMON DISPLAY NAME") 
                           "VERSION NUMBER") ^TMP(<ETSSUB>,$J,"RECORD","VUID") 
                           "VUID EFFECTIVE DATE",#,"EFFECTIVE DATE/TIME") 
                           "VUID EFFECTIVE DATE",#,"STATUS") 
  
 Example: 
  >W $$GETREC^ETSLNC(546,"C") 
  1 
  
  >D ^%G 
  Global ^TMP("ETSREC",$J 
  ^TMP("ETSREC",139688,"RECORD","ACTIVATION HISTORY",1,"ACTIVATION EFFECTIVE
 DATE")="3150629^JUN 29, 2015" 
                                                      "ACTIVATION 
 STATUS")="1^ACTIVE" 
  ^TMP("ETSREC",139688,"RECORD","ADJUSTMENT")="" 
                               "CHALLENGE")="" 
                               "CHANGE REASON")="" 
                               "CHANGE TYPE")="MIN" 
                               "CHECK DIGIT")=2 
                               "CLASS")="MICRO" 
                               "CLASSTYPE")="1^LABORATORY" 
                               "CODE")="546-2" 
                               "COMMENTS")="" 
                               "DATE LAST CHANGED")="3150508^MAY 08, 2015" 
                               "EXAMPLE UCUM UNITS")="" 
                               "FULLY SPECIFIED 
 NAME")="STREPTOCOCCUS.BETA-HEMOLYTIC:ACNC:PT:THRT:ORD:ORGANISM SPECIFIC 
 CULTURE" 
                               "IEN")=546 
                               "LONG COMMON 
 NAME")="STREPTOCOCCUS.BETA-HEMOLYTIC [PRESENCE] IN THROAT BY ORGANISM SPECIFIC
 CULTURE" 
                               "MASTER ENTRY FOR VUID")="YES" 
                               "METHOD TYPE")="ORGANISM SPECIFIC CULTURE" 
                               "NON-PATIENT SPECIMEN")="" 
                               "PROPERTY")="ARBITRARY CONCENTRATION" 
                               "REPEAT OBSERVATION")="" 
                               "SCALE TYPE")="Ordinal" 
                               "SHORTNAME")="B-HEM STREP THROAT QL CULT" 
                               "SNOMED CODE")="" 
                               "SOURCE")="SH" 
                               "SYSTEM")="Throat" 
                               "TIME ASPECT")="POINT" 
                               "TIME MODIFIER")="" 
                               "UNITS")="" 
                               "VA COMMON DISPLAY NAME")="" 
                               "VERSION NUMBER")="" 
                               "VUID")=4683779 
  ^TMP("ETSREC",139688,"RECORD","VUID EFFECTIVE DATE",1,"EFFECTIVE 
 DATE/TIME")="3050501^MAY 01, 2005" 
                                                        "STATUS")="1^ 
VARIABLES: ETSINPT                      TYPE: Input
 VARIABLES DESCRIPTION:   LOINC Code or IEN 
VARIABLES: ETSINTY                      TYPE: Input
 VARIABLES DESCRIPTION:   Input Type of the first parameter.  If not passed in,
 it defaults to "C". Possible values are: 
     "C"=LOINC Code 
     "I"=LOINC IEN 
VARIABLES: ETSSUB                       TYPE: Input
 VARIABLES DESCRIPTION:   This parameter specifies the name of the first
 subscript of the TMP global.  If this parameter is not passed in, the default
 is "ETSREC".  
VARIABLES: $$GETREC                     TYPE: Output
 VARIABLES DESCRIPTION:   This is the return value of the function.  It can
 have one of three values: 
    0 - Code or IEN not found 
    1 - Successfully retrieve LOINC record information 
        or 
   -1^<error message> - Error 
  
 If records are found, the LOINC record information is returned in a TMP global
 as defined in the description of this component.  
COMPONENT/ENTRY POINT: $$GETSTAT(ETSINPT,ETSINTY)
 COMPONENT DESCRIPTION:   This API retrieves the current status for a LOINC
 Code or IEN.  
  
 Example: 
  >W $$GETSTAT^ETSLNC(38340) 
  1^DEL 
VARIABLES: ETSINPT                      TYPE: Input
 VARIABLES DESCRIPTION:   LOINC Code or IEN 
VARIABLES: ETSINTY                      TYPE: Input
 VARIABLES DESCRIPTION:   Input Type of the first parameter.  If not passed in,
 it defaults to "C". Possible values are: 
     "C"=LOINC Code 
     "I"=LOINC IEN 
VARIABLES: $$GETSTAT                    TYPE: Output
 VARIABLES DESCRIPTION:   This is the return value of the function.  It can
 have one of two values: 
   Internal Status^External Status 
      or 
  -1^<Error Message> 
COMPONENT/ENTRY POINT: $$HIST(ETSCODE,ETSSYS,.ARY)
 COMPONENT DESCRIPTION:   The API allows a user to extract the Activation
 History for a specified LOINC CODE. Note that this API was modeled after a
 Lexicon API with a similar name, and the input and output value match the
 format of that API as much as possible.  
  
 Example: 
  >W $$HIST^ETSLNC(2,"LNC",.ARY) 
  2 
  
  >ZW ARY 
  ARY(0)=1 
  ARY(0,0)="2^LNC^LOINC" 
  ARY(3150629,1)="Activated" 
VARIABLES: ETSCODE                      TYPE: Input
 VARIABLES DESCRIPTION:   CODE (#.01) field from LOINC (#129.1) file 
VARIABLES: ETSSYS                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the coding system.  The only valid value is
 "LNC".  If not passed in, the default is "LNC".  
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   Pass by reference parameter that returns the
 Activation History information.  
  
 ARY(0) = Number of Activation Histories ARY(0,0) = LOINC Code^Source
 Abbreviation ("LNC")^Nomenclature ("LOINC") ARY(<Date>,<Status>) = Comment 
  
 Where: 
   Date is the effective date of the status change 
   Status is activation status ( 0=Inactive, 1=Active) 
   Comment provide more detail and can be "Activated", "Re-activated", or 
      "Inactivated". The comment is dependent on the current and previous 
      statuses.  
VARIABLES: $$HIST                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the return value of the function.  It can
 have one of the following values: 
    Number of activation history entries found 
        or 
    -1 ^ error message 
COMPONENT/ENTRY POINT: $$PERIOD(ETSCODE,ETSSYS,ARY)
 COMPONENT DESCRIPTION:   This API allows a user to view the activation periods
 of a given code. Note that this API was modeled after a Lexicon API with a
 similar name, and the input and output value match the format of that API as
 much as possible.  
  
 Example: 
  >W $$PERIOD^ETSLNC(6110,"LNC",.ARY) 
  1^^LNC^LOINC^Logical Observation Identifier Names and Codes 
  
  >ZW ARY 
  ARY(0)="1^^LNC^LOINC^Logical Observation Identifier Names and Codes" 
  ARY(3061026)="^^6110;^ETS(129.1,^ENGLISH PLANTAIN IGE AB [UNITS/VOLUME] IN
 SERUM" 
  ARY(3061026,0)="PLANTAGO LANCEOLATA AB.IGE:ACNC:PT:SER:QN:" 
VARIABLES: ETSCODE                      TYPE: Input
 VARIABLES DESCRIPTION:   CODE (#.01) field from LOINC (#129.1) file 
VARIABLES: ETSSYS                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the coding system.  The only valid value is
 "LNC".  If this is not passed in, the default is "LNC". 
VARIABLES: .ARY                         TYPE: Both
 VARIABLES DESCRIPTION:   Pass by reference parameter that returns the
 activation periods.  
  
 ARY(0)-Five piece "^" delimited string or -1^Message (no period or error) 
   1  # of Activation Periods Found 
   2  Not Used 
   3  Source Abbreviation ("LNC") 
   4  Nomenclature ("LOINC") 
   5  Source Title ("Logical Observation Identifier Names and Codes") 
  
 ARY(Activation Date)-Four piece "^" delimited string 
   1  Inactivation Date 
   2  NULL (not needed for LOINC) 
   3  Variable Pointer to the LOINC File (IEN;ETSLNC(129.1,) 
   4  LONG COMMON NAME (#83) field 
  
 ARY(Activation Date,0)=FULLY SPECIFIED NAME (#80) field 
VARIABLES: $$PERIOD                     TYPE: Output
 VARIABLES DESCRIPTION:   This is the same output as returned on the 0 node of
 the output array.  
  
 Five piece "^" delimited string or -1^Message (no period or error) 
   1  # of Activation Periods Found 
   2  Not Used 
   3  Source Abbreviation ("LNC") 
   4  Nomenclature ("LOINC") 
   5  Source Title ("Logical Observation Identifier Names and Codes") 
COMPONENT/ENTRY POINT: $$TAX(ETSX,ETSSRC,ETSDT,ETSSUB,ETSVER)
 COMPONENT DESCRIPTION:   This API allows a user to locate all of the valid
 codes in the LOINC database for a given string. Note that this API was modeled
 after a Lexicon API with a similar name, and the input and output value match
 the format of that API as much as possible.  
  
 If valid values are found, the results will be returned in the TMP global with
 the first subscript equal to the value passed into the ETSSUB parameter and
 the fourth subscript equal to CODE (#.01) field from the LOINC (#129.1) file
 and containing a trailing space.  
  
 ^TMP(<ETSSUB>,$J,1,(CODE_" "),#) - Five piece "^" delimited string 
    1   Activation Date (can be a future date) 
    2   Inactivation Date (can be a future date) 
    3   Not Used 
    4   Variable Pointer to the LOINC file 
    5   LONG COMMON NAME (#83) field 
  
 ^TMP(<ETSSUB>,$J,1,(CODE_" "),#,0) - Two piece "^" delimited string 
    1   LOINC Code - CODE (#.01) field 
    2   FULLY SPECIFIED NAME (#80) field 
  
 Example: 
  >W $$TAX^ETSLNC("WARFARIN","LNC") 
  16 
  
  >D ^%G 
  Global ^TMP("LEXTAX",$J 
  ^TMP("LEXTAX",9239,0)=16 
  ^TMP("LEXTAX",9239,1,"12282 ",3)="3150629^^^12282;ETSLNC(129.1,^WARFARIN 
 [PRESEN CE] IN URINE" 
  ^TMP("LEXTAX",9239,1,"12282 ",3,0)="12282^WARFARIN:THRESHOLD:PT:URINE:ORD:" 
  ^TMP("LEXTAX",9239,1,"29382 ",4)="3150629^^^29382;ETSLNC(129.1,^WARFARIN 
 [MASS/V OLUME] IN URINE" 
  ^TMP("LEXTAX",9239,1,"29382 ",4,0)="29382^WARFARIN:MCNC:PT:URINE:QN:" 
  ^TMP("LEXTAX",9239,1,"29383 ",5)="3150629^^^29383;ETSLNC(129.1,^WARFARIN 
 [MASS/V OLUME] IN GASTRIC FLUID" 
  ^TMP("LEXTAX",9239,1,"29383 ",5,0)="29383^WARFARIN:MCNC:PT:GAST FLD:QN:" 
  ^TMP("LEXTAX",9239,1,"39798 ",6)="3150629^^^39798;ETSLNC(129.1,^WARFARIN 
 [MOLES/ VOLUME] IN SERUM OR PLASMA" 
  ^TMP("LEXTAX",9239,1,"39798 ",6,0)="39798^WARFARIN:SCNC:PT:SER/PLAS:QN:" 
  ^TMP("LEXTAX",9239,1,"4098 ",1)="3150629^^^4098;ETSLNC(129.1,^WARFARIN 
 [MASS/VOL UME] IN SERUM OR PLASMA" 
  ^TMP("LEXTAX",9239,1,"4098 ",1,0)="4098^WARFARIN:MCNC:PT:SER/PLAS:QN:" 
  <Partial Listing Displayed> 
VARIABLES: ETSX                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the partial Code or Text String to look up.  
VARIABLES: ETSSRC                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the coding system.  The only valid value is
 "LNC".  If this is not passed in, the default is "LNC".  
VARIABLES: ETSDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Date in FileMan format to use to evaluate the status.
 If not passed in, defaults to TODAY.  
VARIABLES: ETSSUB                       TYPE: Input
 VARIABLES DESCRIPTION:   This parameter will be used as the first subscript of
 the TMP global that is returned when there are valid values. If not passed in,
 the default will be "LEXTAX".  
VARIABLES: ETSVER                       TYPE: Input
 VARIABLES DESCRIPTION:   Search criteria - 0 for both Active and Inactive
 codes, 1 for Active codes only. If not passed in, defaults to 0.  
VARIABLES: $$TAX                        TYPE: Output
 VARIABLES DESCRIPTION:   The number of LOINC codes found or -1^error message.  
COMPONENT/ENTRY POINT: $$VERSION()
 COMPONENT DESCRIPTION:   This API retrieves the LOINC version.  
  
 Example: 
  >W $$VERSION^ETSLNC() 
  2.52 
VARIABLES: $$VERSION                    TYPE: Output
 VARIABLES DESCRIPTION:   LOINC Version.  The possible return values are: 
    The current LOINC version 
       or 
    Null - No version found/defined 
       or 
    -1^error message 
  DATE ACTIVATED: JUN 08, 2018

NUMBER: 6732                            IA #: 6732
  FILE NUMBER: 2005.632                 GLOBAL ROOT: MAGV(2005.632,
  DATE CREATED: FEB 07, 2017            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VISTA IMAGING RAD DOSE DATABASE ACCESS
  ID: MAGV(2005.632,
GLOBAL REFERENCE: MAGV(2005.632,IEN,0)
FIELD NUMBER: .01                       FIELD NAME: ID 
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: IRRADIATION INSTANCE UID
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TARGET REGION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: CTDIVOL
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: DLP
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: SERIES INSTANCE
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: PHANTOM TYPE
  LOCATION: 0;13                        ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   This file contains CT DOSE information corresponding to
 an entry in the IMAGE SERIES file (#2005.63).  
GLOBAL REFERENCE: MAGV(2005.632,
 GLOBAL DESCRIPTION:   I intend to use the global root of the file to determine
 if there is data in this file by using a direct global read through use of a
 $ORDER intrinsic function.  
 GENERAL DESCRIPTION:   VistA Radiology/Nuclear Medicine requires VA FileMan
 (FM) read/with FM and direct global read access to the CT DOSE (#2005.632)
 file.  
  
 The direct global read will be used to determine the presence of data in file
 2005.632.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IMAGING
KEYWORDS: MAG
KEYWORDS: RAD
KEYWORDS: RA
KEYWORDS: RAD DOSE
KEYWORDS: RIS
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  DATE ACTIVATED: JUL 11, 2017

NUMBER: 6733                            IA #: 6733
  FILE NUMBER: 2005.633                 GLOBAL ROOT: MAGV(2005.633,
  DATE CREATED: FEB 07, 2017            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VISTA IMAGING RAD DOSE DATABASE ACCESS (2)
  ID: MAGV(2005.633,
GLOBAL REFERENCE: MAGV(2005.633,IEN,0)
FIELD NUMBER: .01                       FIELD NAME: ID 
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ESTIMATE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TOTAL TIME IN FLUOROSCOPY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: DOSE AREA PRODUCT
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: SERIES INSTANCE
  LOCATION: 0;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: MAGV(2005.633,IEN,1)
FIELD NUMBER: 9                         FIELD NAME: DOSE (RP) TOTAL (AKE)
  LOCATION: 1;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: FLUORO DOSE (RP) TOTAL
  LOCATION: 1;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 11
  FIELD NAME: FLUORO DOSE AREA PRODUCT TOTAL
  LOCATION: 1;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: CINE DOSE (RP) TOTAL
  LOCATION: 1;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: CINE DOSE AREA PRODUCT TOTAL
  LOCATION: 1;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: CINE TIME
  LOCATION: 1;6                         ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   This file contains PROJECTION X-RAY DOSE information
 corresponding to an entry in the IMAGE SERIES file (#2005.63).  
GLOBAL REFERENCE: MAGV(2005.633,
 GLOBAL DESCRIPTION:   I intend to use the global root of the file to determine
 if there is data in this file by using a direct global read through use of a
 $ORDER intrinsic function.  
 GENERAL DESCRIPTION:   VistA Radiology/Nuclear Medicine requires VA FileMan
 (FM) read/with FM and direct global read access to the PROJECTION X-RAY DOSE 
 (#2005.633) file.  
  
 The direct global read will be used to determine the presence of data in file
 2005.633.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAG
KEYWORDS: RA
KEYWORDS: RAD
KEYWORDS: RAD DOSE
KEYWORDS: RIS
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  DATE ACTIVATED: JUL 11, 2017

NUMBER: 6734                            IA #: 6734
  DATE CREATED: FEB 13, 2017            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCH442A
  NAME: CANCEL 2237 FROM PC ORDER       ID: PRCH442A
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call C2237^PRCH442A.  The call will
 cancel a 2237 from a purchase card order.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: C2237
 COMPONENT DESCRIPTION:   Cancel 2237 from PC order 
VARIABLES: DA                           TYPE: Used
 VARIABLES DESCRIPTION:   IEN of the purchase card order being cancelled from
 file 442 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 13, 2019

NUMBER: 6735                            IA #: 6735
  DATE CREATED: FEB 13, 2017            CUSTODIAL PACKAGE: PROBLEM LIST
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMPLBLD2
  NAME: GMPLBLD2                        ID: GMPLBLD2
 GENERAL DESCRIPTION:   This ICR documents calls made to GMPLBLD2.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMPLBLD2
KEYWORDS: VALLIST
COMPONENT/ENTRY POINT: VALLIST(GMPLLIST)
 COMPONENT DESCRIPTION:   Returns whether a selection list is valid or not. A
 selection list is valid if it contains problems with active codes. It is
 invalid if it contains one or more problems with inactive codes.  
VARIABLES: GMPLLIST                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN of PROBLEM SELECTION LIST file (#125).  
VARIABLES: RETURN VALUE                 TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 if a list has no problems with inactive
 codes. Returns 0 if a list has one or more problems with inactive codes.
 Returns 0^ERROR if a list is invalid.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   OR*3.0*429 utilizes the $$VALLIST API to determine
 whether a problem selection list contains problems with inactive SNOMED CT/ICD
 codes. This outcome will aid in the clinic selection list migration process.  
  DATE ACTIVATED: FEB 14, 2017

NUMBER: 6736                            IA #: 6736
  DATE CREATED: FEB 17, 2017            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: Other
  NAME: Executable Help Deletion
 GENERAL DESCRIPTION:   This is a temporary agreement to be used only if
 PSS*1*202, which is the RollBack patch for PSS*1*201, needs to be released or
 sent to any number of sites. The Post-Init routine (PSS202RB) will kill the 4
 node of the NAME (#.01) Field and SYNONYM (#.5) Field of the MEDICATION
 INSTRUCTION (#51) File Data Dictionary. The 4 node contains the Executable
 Help.  
  
  
 0n 8/14/17, the developer said the 90-warranty period for PSS*1*201 was 
 reached and the functionality provided by this ICR will not be needed for the
 rollback patch PSS*1*202.  ICR #6736 was retired on 11/15/17.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: NOV 15, 2017
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   The Post-Init routine of Rollback patch PSS*1*202 will
 perform a hard kill of the 4 node of the Data Dictionary for the NAME (#.01)
 Field and SYNONYM (#.5) Field of the MEDICATION INSTRUCTION (#51) File, since
 there currently is not an API to do this. Once PSS*1*201 is installed at all 
 sites, or PSS*1*202 is no longer needed this agreement will be set to expired. 
 

NUMBER: 6737                            IA #: 6737
  DATE CREATED: FEB 23, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDXC ACCEPT                   REMOTE PROCEDURE: ORWDXC ACCEPT
 GENERAL DESCRIPTION:   The ICR will be used by this service: OrderMgmtSvc -
 acceptOrder.  
  
  STATUS: Withdrawn
KEYWORDS: ORWDXC
KEYWORDS: ACCEPT
KEYWORDS: VAR
KEYWORDS: MBAA
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE

NUMBER: 6738                            IA #: 6738
  DATE CREATED: FEB 23, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWDLR32 DEF                    REMOTE PROCEDURE: ORWDLR32 DEF
 GENERAL DESCRIPTION:   The ICR will be used by this service: OrderMgmtSvc -
 getInitialLabOrderParams.  
  
  STATUS: Withdrawn
KEYWORDS: ORWDLR32
KEYWORDS: DEF
KEYWORDS: MBAA
KEYWORDS: VAR
KEYWORDS: VIA
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE

NUMBER: 6739                            IA #: 6739
  FILE NUMBER: 601.71                   GLOBAL ROOT: YTT(601.71,
  DATE CREATED: FEB 24, 2017            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: File
  NAME: HMP ACCESS TO THE MHY TESTS AND SURVEYS FILE
  ID: YTT(601.71,
GLOBAL REFERENCE: YTT(601.71,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Name of the interview, survey or test.  
FIELD NUMBER: 21                        FIELD NAME: COPYRIGHT TEXT
  LOCATION: 7;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Text to display copyright information on the screen and
 printed report.  
GLOBAL REFERENCE: YTT(601.71,D0,8
FIELD NUMBER: 25                        FIELD NAME: IS COPYRIGHTED
  LOCATION: 8;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Boolean, if set to true, actual question text is shown on
 the reports.  
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform is accessing the MH
 TESTS AND SURVEYS FILE (#601.71) to retrieve fields .01 - NAME, 21 - COPYRIGHT
 TEXT and 25 - IS COPYRIGHTED as part of the data collection for the HMP sync
 process.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  
  
 ICR #6739 was entered to replace ICR #5044.  ICR #6739 must be revisited if
 HMP is restarted in the future due to global reference and changes implemented
 with YS*5.01*123.  
     
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
KEYWORDS: 601.71
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6740                            IA #: 6740
  FILE NUMBER: 100.21                   GLOBAL ROOT: DD(100.213
  DATE CREATED: FEB 24, 2017            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DD 'AUTOLINK' MULT .01 FLD TO REMOVE REF TO 44/409.67 FILES
  ID: DD(100.213
 GENERAL DESCRIPTION:   Patch OR*3.0*399 to remove AUTOLINK Multiple from Data
 Dictionary of OE/RR LINK File in a pre-install routine that is part of the
 patch and then the patch itself will rebuild the Multiple with only those
 Variable Pointer entries that should remain (all but refs to 44 and 409.67).  
  
 Patch will rebuild 100.213,.01 AUTOLINK field of ^DD(100.213) leaving only the
 following in the VARIABLE POINTER field: 
  
               FILE  ORDER  PREFIX    LAYGO  MESSAGE 
                42     1      W         n     WARD 
               405.4   2      R         n   ROOM-BED 
                200    3      P         n   PROVIDER 
                45.7   4      S         n   SPECIALTY 
  
 Formerly it had a link to either File 44 or 409.67 (which OR*3.0*399 deletes),
 e.g.: 
  
                44     5      C         n    CLINIC 
  
 Deletion of AUTOLINK Multiple is done by OR3P399 pre-install routine with the
 use of the following FileMan call: 
  
 S DIU=100.213,DIU(0)="S" D EN^DIU2 K DIU 
  STATUS: Active
KEYWORDS: AUTOLINK
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAR 02, 2017

NUMBER: 6741                            IA #: 6741
  DATE CREATED: MAR 02, 2017            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: DGADDUT1                     NAME: RESIDENTIAL ADDRESS DISPLAY
  ID: DGADDUT1
 GENERAL DESCRIPTION:   The routine RESDISP^DGADDUT1(DFN) will display the
 current residential address in the format found on screen 1.1 of patient
 registration.  
  
 The display will be placed at the current $Y with the following format: 
  
    123 DRIVE ROAD                          County: 
    APT 8                                    Phone: UNANSWERED 
    BED 1 
    MINNEAPOLIS,MN  55114 
    UNITED STATES                          From/To: JUN 10,2014/APR 6,2017 
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: RESIDENTIAL
KEYWORDS: ADDRESS
KEYWORDS: RESIDENTIAL ADDRESS
COMPONENT/ENTRY POINT: RESDISP
 COMPONENT DESCRIPTION:   This subroutine does the display of the residential
 address.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The ien of the patient in the ^DPT global 

NUMBER: 6742                            IA #: 6742
  FILE NUMBER: 8925                     GLOBAL ROOT: TIU(8925
  DATE CREATED: MAR 03, 2017
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA6742
  ID: TIU(8925
GLOBAL REFERENCE: TIU(8925,'ADCPT'
 GENERAL DESCRIPTION:   The consult closure tool needs to find all the amended
 or completed notes that have been entered for a particular patient for a
 consult within a selected time frame.  
  
 The "ADCPT" cross-reference addresses each of these requirements.  This ICR is
 for direct global read only.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CONSULT ADCPT
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  DATE ACTIVATED: NOV 20, 2017

NUMBER: 6743                            IA #: 6743
  FILE NUMBER: 63                       GLOBAL ROOT: LR(D0,'CH')
  DATE CREATED: MAR 06, 2017            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VIAB LAB
  ID: LR(D0,'CH')
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: .03                       FIELD NAME: DATE REPORT COMPLETED
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: ACCESSION
  LOCATION: 0;6                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LR(D0,'CH',D1,n)
 GLOBAL DESCRIPTION:   n represent field number for specific lab results. VIA
 needs read access to the entire node.  
  
  STATUS: Active
KEYWORDS: VIA
KEYWORDS: EFR
KEYWORDS: LAB
KEYWORDS: RESULT
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA needs to read File #63 to provide lab data and
 results to consuming applications via a remote procedure call (RPC) VIAB EFR.
 The VIAB EFR RPC was developed exclusively for the Embedded Fragment Registry. 
 
  DATE ACTIVATED: APR 14, 2017

NUMBER: 6744                            IA #: 6744
  DATE CREATED: MAR 14, 2017            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SCAPMC25
  NAME: DBIA6744                        ID: SCAPMC25
 GENERAL DESCRIPTION:   Registration version 5.3 uses entry point $$PCMMXMY to
 build xmy array for the appropriate type of PCMM message.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SCAPMC25
COMPONENT/ENTRY POINT: PCMMXMY
VARIABLES: MSGTYPE                      TYPE: Input
 VARIABLES DESCRIPTION:   MSGTYPE: 
      1 = Death Message 
      2 = Inpatient Message 
      3 = Team Message 
      4 = Consult Message 
      5 = Inactivation Message 
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number in Patient File (#2) 
VARIABLES: SCTEAMA                      TYPE: Input
 VARIABLES DESCRIPTION:   array of pointers to team file 404.51 if none are
 defined - returns all teams if @scteama@('exclude') is defined - exclude
 listed teams 
  
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 pracitioners who were on 
                       team for entire date range 
                    0: anytime in date range 
                       [default: 1] 
  
VARIABLES: SCYESCL                      TYPE: Input
 VARIABLES DESCRIPTION:   Boolean[1-yes(default)/0-no] Include pts asc. via
 enrollment 
VARIABLES: SCOK                         TYPE: Output
 VARIABLES DESCRIPTION:   1 if success, 0 if error 
SUBSCRIBING PACKAGE: REGISTRATION
  DATE ACTIVATED: MAR 30, 2017

NUMBER: 6745                            IA #: 6745
  DATE CREATED: MAR 14, 2017            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SCMCMM
  NAME: DBIA6745                        ID: SCMCMM
 GENERAL DESCRIPTION:   Registration Version 5.3 uses API call $$PCMAIL^SCMCMM
 to load standard patient centered information into a mail message.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SCMCMM
COMPONENT/ENTRY POINT: PCMAIL
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number in the Patient File
 (#2) 
VARIABLES: SCARRAY                      TYPE: Input
 VARIABLES DESCRIPTION:   Literal value to XMTEXT array 
VARIABLES: SCDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   Date of interest - default=DT 
VARIABLES: SCLNCNT                      TYPE: Output
 VARIABLES DESCRIPTION:   Ending line count for array 
SUBSCRIBING PACKAGE: REGISTRATION
  DATE ACTIVATED: MAR 30, 2017

NUMBER: 6746                            IA #: 6746
  FILE NUMBER: 301.9                    GLOBAL ROOT: IVM(301.9
  DATE CREATED: MAR 14, 2017
  CUSTODIAL PACKAGE: INCOME VERIFICATION MATCH
  USAGE: Private                        TYPE: File
  NAME: DBIA6746                        ID: IVM(301.9
GLOBAL REFERENCE: IVM(301.9,D0
FIELD NUMBER: .09                       FIELD NAME: ENROLLMENT ALERT MAIL GROUP
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Registration Version 5.3 access the IVM Site Parameter
 file (#301.9) to get the ENROLLMENT ALERT MAIL GROUP field  (#.09) that is on
 the 9th piece of the zero node.  
  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: IVM(301.9
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   Registration gets the ENROLLMENT ALERT MAIL GROUP in
 the IVM Site Parameter file (#301.9) with global read. 
  

NUMBER: 6747                            IA #: 6747
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19
  DATE CREATED: MAR 15, 2017            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PRCA READ/WRITE ACCESS W/FILEMAN TO LOCK FIELD (#3)
  ID: DIC(19
GLOBAL REFERENCE: DIC(19,D0,0
FIELD NUMBER: 3                         FIELD NAME: LOCK
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   PRCA requires the ability to delete a LOCK from an
 OPTION for patch PRCA*4.5*318. This cannot be accomplished using KIDS.
 Permission is required to accomplish this task using pre- or post-install
 routines in KIDS.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OPTION
KEYWORDS: LOCK
KEYWORDS: PRCA
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: MAR 27, 2017

NUMBER: 6748                            IA #: 6748
  FILE NUMBER: 2                        GLOBAL ROOT: DD(2,.024,
  DATE CREATED: MAR 20, 2017            CUSTODIAL PACKAGE: MASTER PATIENT INDEX
  USAGE: Private                        TYPE: File
  NAME: DBIA6748                        ID: DD(2,.024,
GLOBAL REFERENCE: DD(2,.024
FIELD NUMBER: .024                      FIELD NAME: SELF IDENTIFIED GENDER
  LOCATION: .24;4                       ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   Master Patient Index grants Registration Version 5.3
 permission to export the data dictionary of the SELF IDENTIFIED GENDER field
 (#.024) in the PATIENT file (#2) in patch DG*5.3*907 to update the DESCRIPTION
 of the field. The reference to "sexual orientation" was replaced with "gender
 identity".  The updated DESCRIPTION now reads: 
  
                This SELF IDENTIFIED GENDER value indicates the 
                patient's view of their gender identity, if 
                they choose to provide it.  
  
  
  
  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: SIGI
KEYWORDS: SELF IDENTIFIED GENDER
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 6749                            IA #: 6749
  DATE CREATED: MAR 22, 2017            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOREJU2
  NAME: REJECT INFORMATION              ID: PSOREJU2
 GENERAL DESCRIPTION:   Pull and return reject information from subfile 52.25.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
KEYWORDS: REJECT
COMPONENT/ENTRY POINT: GET
 COMPONENT DESCRIPTION:   GET pulls and returns reject information from
 subfile# 52.25, REJECT INFO, of file# 52, PRESCRIPTION.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Rx IEN, pointer to file# 52, PRESCRIPTION.  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Refill#.  Will default to most recent fill if blank.  
VARIABLES: REJDATA                      TYPE: Output
 VARIABLES DESCRIPTION:   This array, passed by reference, will be returned
 with the following fields.  REJDATA(REJECT IEN,FIELD), where FIELD may be: 
   "BIN" - Payer BIN number 
   "CODE" - Reject Code (79 or 88) 
   "DATE/TIME" - DATE/TIME Reject was detected 
   "PAYER MESSAGE" - Message returned by the payer 
   "REASON" - Reject Reason description (from payer) 
   "INSURANCE NAME" - Patient's Insurance Company Name 
   "INSURANCE POINTER" - Patient Insurance Company Pointer 
   "COB" - Coordination of Benefits 
   "GROUP NAME" - Patient's Insurance Group Name 
   "GROUP NUMBER" - Patient's Insurance Group Number 
   "CARDHOLDER ID" - Patient's Insurance Cardholder ID 
   "PLAN CONTACT" - Plan's Contact (eg., "1-800-...") 
   "PLAN PREVIOUS FILL DATE" - Last time Rx was paid by payer 
   "STATUS" - REJECTS status ("OPEN/UNRESOLVED" or "CLOSED/RESOLVED") 
   "DUR TEXT" - Payer's DUR description 
   "DUR ADD MSG TEXT" - Payer's DUR additional description 
   "OTHER REJECTS" - Other Rejects on the same response 
   "REASON SVC CODE" - Reason for Service Code If REJECT is closed, the
 following fields will be returned: 
   "CLA CODE" - Clarification Code submitted 
   "PRIOR AUTH TYPE" - Prior Authorization Type 
   "PRIOR AUTH NUMBER" - Prior Authorization Type 
   "CLOSED DATE/TIME" - DATE/TIME Reject was closed 
   "CLOSED BY" - Name of the user responsible for closing Reject 
   "CLOSE REASON" - Reason for closing Reject (text) 
   "CLOSE COMMENTS" - User entered comments at close 
VARIABLES: REJID                        TYPE: Input
 VARIABLES DESCRIPTION:   Reject IEN in the PRESCRIPTION file.  If this value
 is passed, the procedure will return information for only this reject.  
VARIABLES: OKCL                         TYPE: Input
 VARIABLES DESCRIPTION:   If set to 1, Closed Rejects will also be returned.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   If passed, then only rejects with this CODE should be
 returned.  
VARIABLES: RRRFLG                       TYPE: Input
 VARIABLES DESCRIPTION:   If set to 1 with CODE present, also return Reject
 Resolution Required rejects.  If set to 1 and CODE is not passed, then only
 return RRR rejects.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: APR 10, 2017

NUMBER: 6750                            IA #: 6750
  DATE CREATED: MAR 28, 2017            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PRCAAPR1
  NAME: ACCOUNT PROFILE FOR OUTPATIENT PHARMACY
  ID: PRCAAPR1
 GENERAL DESCRIPTION:   Users working Patient Medication Worklist will be able
 to access the patient Account Profile report while still in the worklist. This
 will aid them in determinig if the charge needs to be canceled or not.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: OUTPATIENT PHARMACY
COMPONENT/ENTRY POINT: HDR
 COMPONENT DESCRIPTION:   Header for Account Profile report 
COMPONENT/ENTRY POINT: HDR2
 COMPONENT DESCRIPTION:   Header 2 for Account Profile report 
COMPONENT/ENTRY POINT: DIS
 COMPONENT DESCRIPTION:   Display bill line items 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   New Patient Medication List Manger action 

NUMBER: 6751                            IA #: 6751
  DATE CREATED: MAR 28, 2017            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PRCAAPR
  NAME: ACCOUNT PROFILE REPORT FOR OUTPATIENT PHARMACY
  ID: PRCAAPR
 GENERAL DESCRIPTION:   Users working Patient Medication Worklist will be able
 to access the patient Account Profile report while still in the worklist. This
 will aid them in determinig if the charge needs to be canceled or not.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: OUTPATIENT PHARMACY
COMPONENT/ENTRY POINT: COMP
 COMPONENT DESCRIPTION:   This is called to compile the Patient Account Profile
 report.  
VARIABLES: DFN                          TYPE: Used
 VARIABLES DESCRIPTION:   Patient ID 
VARIABLES: NAME                         TYPE: Used
 VARIABLES DESCRIPTION:   Patient Name 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   New Patient Medication List Manger action 

NUMBER: 6752                            IA #: 6752
  DATE CREATED: MAR 29, 2017            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: DGRPD
  NAME: OUTPATIENT PHARMACY PATIENT INQUIRY
  ID: DGRPD
 GENERAL DESCRIPTION:   This allows users of the Patient Medication LM to do
 patient inquiry without leaving the list manager 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: OUTPATIENT PAARMACY
KEYWORDS: REGISTRATION
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   PATIENT INQUIRY ENTRY 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 6753                            IA #: 6753
  DATE CREATED: MAR 29, 2017            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBOLK
  NAME: OUTPATIENT PHARMACY BILL INQUIRY
  ID: IBOLK
 GENERAL DESCRIPTION:   This allows users of the Patient Medication LM to do
 Bill Inquiry without leaving the List Manager.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BILL INQUIRY
KEYWORDS: OUTPATIENT PHARMACY
COMPONENT/ENTRY POINT: EN
VARIABLES: IBIL                         TYPE: Input
 VARIABLES DESCRIPTION:   External form of bill number, ie 500-K10001 
VARIABLES: IBFULL                       TYPE: Input
 VARIABLES DESCRIPTION:   1 for full profile logic, 0 for brief description 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: MAR 09, 2018

NUMBER: 6754                            IA #: 6754
  DATE CREATED: APR 07, 2017            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PSNACT                       NAME: DBIA6754
  ID: PSNACT
 GENERAL DESCRIPTION:   This API was released with PSN*4.0*396.  It displays
 the Formulary Indicator and Product Text.  
  
 Pharmacy Data Management requests an ICR to utilize this API.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FORMULARY DESIGNATOR
KEYWORDS: FORMULARY DESIGNATOR TEXT
KEYWORDS: VA PRODUCT FILE
COMPONENT/ENTRY POINT: FD
 COMPONENT DESCRIPTION:   Displays the Formulary Designator field (#109) from
 VA PRODUCT file (#50.68).  
VARIABLES: DRUGIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   VA PRODUCT file (#50.68) IEN.  
COMPONENT/ENTRY POINT: FDT
 COMPONENT DESCRIPTION:   Displays the Formulary Designator Text word
 processing field (#110) from VA Product file (#50.68).  
VARIABLES: DRUGIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   VA PRODUCT file (#50.68) IEN.  
COMPONENT/ENTRY POINT: FDR
 COMPONENT DESCRIPTION:   Returns the Formulary Designator value defined for
 FORMULARY DESIGNATOR field(#109) in VA PRODUCT file (#50.68).  
VARIABLES: DRUGIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   VA PRODUCT file (#50.68) IEN.  
VARIABLES: PSNFD                        TYPE: Output
 VARIABLES DESCRIPTION:   Formulary Designator value defined for FORMULARY
 DESIGNATOR field(#109) in VA PRODUCT file (#50.68).  
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT

NUMBER: 6755                            IA #: 6755
  DATE CREATED: APR 12, 2017
  CUSTODIAL PACKAGE: HEALTH MANAGEMENT PLATFORM
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HMPEVNT
  NAME: GMRC CALL TO POST~HMPEVNT       ID: HMPEVNT
 GENERAL DESCRIPTION:   The Consult package is making a call to POST^HMPEVNT
 API to sync VistA with the eHMP JSON database system when a new comment is
 added to an existing consult.  
  
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the 
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 subscribing application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs. 
 **********************************************************************
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: HMP
KEYWORDS: GMRC
COMPONENT/ENTRY POINT: POST
 COMPONENT DESCRIPTION:   This API initiates a sync activity from VistA to the
 eHMP JSON database.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient DFN.  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   The domain to be synced. In this case it is the
 Consult domain.  
VARIABLES: ID                           TYPE: Input
 VARIABLES DESCRIPTION:   The IEN for the consult in the REQUEST/CONSULTATION
 FILE (#123).  
VARIABLES: ACT                          TYPE: Input
 VARIABLES DESCRIPTION:   The type of action to take at the JSON database. 
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  DATE ACTIVATED: OCT 23, 2017

NUMBER: 6756                            IA #: 6756
  DATE CREATED: APR 14, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWDAL32
  NAME: ORWDAL32 APIS                   ID: ORWDAL32
 GENERAL DESCRIPTION:   For CPRS v32 development, the GMRA package needs access
 to new OR APIs, CHKMEDS^ORWDAL32, GETPROV^ORWDAL32, & SENDALRT^ORWDAL32, which
 have also been developed for CPRS v32. 
  
 These changes are all related to NSR 20070203 for allergy order check 
 enhancements and will be part of the CPRS v32 bundled release.  
  STATUS: Active
KEYWORDS: ORWDAL32
KEYWORDS: SENDALRT
KEYWORDS: GETPROV
KEYWORDS: CHKMEDS
COMPONENT/ENTRY POINT: CHKMEDS
 COMPONENT DESCRIPTION:   This function will check a patient's active
 medication profile against any new allergies being entered into the system for
 potential conflicts. Input parameters are the patient's DFN and the name of
 the newly-entered allergy. The return data will be in an array format.  
VARIABLES: ORDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient's DFN 
VARIABLES: GMRAGNT                      TYPE: Input
 VARIABLES DESCRIPTION:   The newly-entered patient allergy entered in the GMRA
 system.  
VARIABLES: LST                          TYPE: Output
 VARIABLES DESCRIPTION:   An array list of the patient's active medication
 orders that have potential conflicts with the newly-entered allergy in the
 GMRA system.  
COMPONENT/ENTRY POINT: GETPROV
 COMPONENT DESCRIPTION:   For a given OR order number, this function returns a
 list of providers who are associated with the order.  
VARIABLES: ORDLST                       TYPE: Input
 VARIABLES DESCRIPTION:   The OR order number needed to retrieve the list of
 providers.  
VARIABLES: LST                          TYPE: Output
 VARIABLES DESCRIPTION:   List of provider names along with each associated
 file and ien. Returned in an array format.  
COMPONENT/ENTRY POINT: SENDALRT
 COMPONENT DESCRIPTION:   This function sends a group of alerts for a new
 allergy that impacts an existing medication order based on the OR order number
 and list of providers passed in.  
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   OR order number to send the alerts for.  
VARIABLES: PROVLST                      TYPE: Input
 VARIABLES DESCRIPTION:   List of providers to send the alerts to.  
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING
  DATE ACTIVATED: JUN 06, 2017

NUMBER: 6757                            IA #: 6757
  DATE CREATED: APR 25, 2017
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA6757
  STATUS: Pending

NUMBER: 6758                            IA #: 6758
  DATE CREATED: APR 26, 2017
  CUSTODIAL PACKAGE: ENTERPRISE TERMINOLOGY SERVICE
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ETSRXN
  NAME: ETSRXN                          ID: ETSRXN
 GENERAL DESCRIPTION:   These API(s) allow access to the RxNorm data that is
 contained in the RxNorm files in the Enterprise Terminology Services (ETS)
 package.  
  STATUS: Active
COMPONENT/ENTRY POINT: $$CSDATA(CODE,SYS,CDT,RESULT)
 COMPONENT DESCRIPTION:   This API allows a user to retrieve information for a
 given RXCUI.  Note that this API was modeled after a Lexicon API with a
 similar name, and the input and output value match the format of that API as
 much as possible.  
                 
 Example: 
  
 >W $$CSDATA^ETSRXN(749151,"RXN",,.ARY) 1 
  
 >ZW ARY ARY("LEX",1)="271798^TRI-NORINYL 28 Day Pack" ARY("LEX",1,"N")="IEN ^
 Text (STR)" ARY("LEX",2)="1^3170306" ARY("LEX",2,"N")="Status ^ Effective
 Date" ARY("LEX",8)="" ARY("LEX",8,"N")="Deactivated Concept" 
 ARY("RXN",1)="PSN^N^4096" ARY("RXN",1,"N")="Term Type (TTY) ^ Suppression Flag
 (Suppress) 
                   ^ Content View Flag (CVF)" 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   RXCUI (#.01) field from the RxNorm Concept Names and
 Sources File (#129.2).  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This optional parameter is the coding System to
 perform the lookup on. For RxNorm, "RXN" is the only valid value to send. If
 not passed in, defaults to "RXN".  
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This optional parameter is the date in Fileman Format
 used to evaluate the status. If not passed in, defaults to TODAY.  
VARIABLES: .RESULT                      TYPE: Both
 VARIABLES DESCRIPTION:   This is a pass-by-reference parameter used to
 indicate the array to return the output results.  
                             
 The output is returned as: 
  
 RESULT("LEX",1)    : Two pieces of data - IEN^ STR RESULT("LEX",1,"N"): "IEN ^
 Text (STR)" RESULT("LEX",2)    : Two pieces of data - Activation Status
 (1:Active, 
                      2:Inactive)^Activation Effective Date 
 RESULT("LEX",2,"N"): "Status ^ Effective Date" RESULT("LEX",8)    : Either
 Null (Active) or 1 (Inactive) RESULT("LEX",8,"N"): "Deactivated Concept" 
 RESULT("RXN",1)    : Three pieces of data  - TTY^SUPPRESS^CVF 
 RESULT("RXN",1,"N"): "Term Type (TTY) ^ Suppression Flag (Suppress) 
                      ^ Content View Flag (CVF)" *Note that the "N" values are
 the description of the output 
VARIABLES: $$CSDATA                     TYPE: Output
 VARIABLES DESCRIPTION:   One of three values: 
    1 - Successful (code exists in LOINC dictionary) 
    0 - Unsuccessful 
        or 
   -1^<message> - Error 
COMPONENT/ENTRY POINT: $$CSYS(SYS)
 COMPONENT DESCRIPTION:   This API returns coding system information for
 RXNORM. Note that this API was modeled after a Lexicon API with a similar
 name, and the input and output value match the format of that API as much as
 possible.  
                 
 Example: >W $$CSYS^ETSRXN("RXN") ^RXN^RXN^RxNorm^RxNorm^National Library of
 Medicine^^^^^^^^ 
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This optional parameter has the coding system to
 perform the Lookup on.  For RXNORM, the only valid value is "RXN". If not
 passed in, defaults to "RXN".  
VARIABLES: $$CSYS                       TYPE: Output
 VARIABLES DESCRIPTION:   A delimited string of code system information 
    1. Not used 
    2. Three-character Source Abbreviation 
    3. Source Abbreviation 
    4. Nomenclature 
    5. Source Title 
    6. Source 
    7. Not used 
    8. Not used 
    9. Not used 
   10. Not used 
   11. Not used 
   12. Version ID 
   13. Implementation Date - Not Used 
   14. Lookup Threshold - Not Used 
COMPONENT/ENTRY POINT: $$GETDATA(RXCUI,SUB)
 COMPONENT DESCRIPTION:   This API retrieves all of the information for the
 specified RxNorm Unique ID from the RxNorm Concept Names and Sources (129.2),
 RxNorm Simple Concept and Atom Attribites (129.21), RxNorm Related Concepts
 (129.22), and RxNorm Semantic Type (129.23) files.  
   
 If the RXCUI is valid the RXCUI related data are returned as: 
  
 ^TMP(SUB,$J,RXCUI,"RXNCONSO")=Count ^TMP(SUB,$J,RXCUI,"RXNCONSO",RXNCONSO 
 count,0)=IEN^RXCUI^SAB^TTY^CODE^SUPPRESS^CVF 
 ^TMP(SUB,$J,RXCUI,"RXNCONSO",RXNCONSO count,1)=STR 
  
 ^TMP(SUB,$J,RXCUI,"RXNREL")=Count ^TMP(SUB,$J,RXCUI,"RXNREL",RXNREL 
 count,0)=IEN^RXCUI1^REL^RXCUI2^RELA^SAB^SUPPRESS^CVF 
  
 ^TMP(SUB,$J,RXCUI,"RXNSAT")=Count ^TMP(SUB,$J,RXCUI,"RXNSAT",RXNSAT
 count,0)=IEN^RXCUI^CODE^SAB^SUPPRESS^CVF ^TMP(SUB,$J,RXCUI,"RXNSAT",RXNSAT
 count,1)=ATN ^TMP(SUB,$J,RXCUI,"RXNSAT",RXNSAT count,2)=ATV 
  
 ^TMP(SUB,$J,RXCUI,"RXNSTY")=Count ^TMP(SUB,$J,RXCUI,"RXNSTY",RXNSTY
 count,0)=IEN^RXCUI^STY^CVF 
                 
 Example: >W $$GETDATA^ETSRXN(29115,"OUT") 1 
  
 ^TMP("OUT",27627,29115,"RXCONSO")=3 
 ^TMP("OUT",27627,29115,"RXCONSO",1,0)="12004^29115^RXNORM^BN^29115^N^" 
                                    1)="Maalox" 
 ^TMP("OUT",27627,29115,"RXCONSO",2,0)="12005^29115^MMSL^BN^47069^N^" 
                                    1)="Maalox" 
 ^TMP("OUT",27627,29115,"RXCONSO",3,0)="12006^29115^MMSL^BN^5604^O^" 
                                    1)="Maalox (obsolete)" 
 ^TMP("OUT",27627,29115,"RXNREL")=18 
 ^TMP("OUT",27627,29115,"RXNREL",1,0)="86149^29115^RB^612^has_tradename^RXN 
 ORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",2,0)="86150^29115^RB^6581^has_tradename^RX 
 NORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",3,0)="86151^29115^RO^210836^has_ingredient 
 ^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",4,0)="86152^29115^RO^210847^has_ingredient 
 ^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",5,0)="86153^29115^RO^210850^has_ingredient 
 ^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",6,0)="86154^29115^RO^210852^has_ingredient 
 ^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",7,0)="86155^29115^RO^366011^has_ingredient 
 ^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",8,0)="86156^29115^RO^367863^has_ingredient 
 ^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",9,0)="86157^29115^RO^571316^has_ingredient 
 ^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",10,0)="86158^29115^RO^571327^has_ingredien 
 t^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",11,0)="86159^29115^RO^571329^has_ingredien 
 t^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",12,0)="86160^29115^RO^571331^has_ingredien 
 t^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",13,0)="86161^29115^RO^1176865^has_ingredie 
 nt^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",14,0)="86162^29115^RO^1176866^has_ingredie 
 nt^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",15,0)="86163^29115^RO^1176867^has_ingredie 
 nt^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",16,0)="86164^29115^RO^1302338^has_ingredie 
 nt^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",17,0)="86165^29115^RO^1302339^has_ingredie 
 nt^RXNORM^^" 
 ^TMP("OUT",27627,29115,"RXNREL",18,0)="86166^29115^RO^1302340^has_ingredie 
 nt^RXNORM^^" ^TMP("OUT",27627,29115,"RXNSAT")=3 
 ^TMP("OUT",27627,29115,"RXNSAT",1,0)="4257^29115^29115^RXNORM^N^" 
                                   1)="RXN_ACTIVATED" 
                                   2)="01/28/2010" 
 ^TMP("OUT",27627,29115,"RXNSAT",2,0)="4258^29115^29115^RXNORM^N^" 
                                   1)="RXN_BN_CARDINALITY" 
                                   2)="multi" 
 ^TMP("OUT",27627,29115,"RXNSAT",3,0)="4259^29115^29115^RXNORM^N^" 
                                   1)="RXN_OBSOLETED" 
                                   2)="12/04/2009" 
 ^TMP("OUT",27627,29115,"RXNSTY")=2 
 ^TMP("OUT",27627,29115,"RXNSTY",1,0)="15479^29115^Inorganic Chemical^" 
 ^TMP("OUT",27627,29115,"RXNSTY",2,0)="15480^29115^Pharmacologic Substance^" 
VARIABLES: RXCUI                        TYPE: Input
 VARIABLES DESCRIPTION:   This parameter is the RxNorm Unique ID for every
 concept in the RxNorm databases.  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter that indicates the subscript for
 the Temporary Deprecated List Array.  If not passed in, defaults to "ETSDATA". 
 
VARIABLES: $$GETDATA                    TYPE: Output
 VARIABLES DESCRIPTION:   Output value to the function.  Either: 
    1 - successful check 
    0 - does not exist 
        or 
   -1^<error message> - error occurred 
COMPONENT/ENTRY POINT: $$HIST(CODE,SYS,.RESULT)
 COMPONENT DESCRIPTION:   This API allows a user to extract the Activation
 History for a given RXCUI.  
  
 Example: >W $$HIST^ETSRXN(749151,"RXN",.ARY) 1 
                 
 >ZW ARY ARY(0)=1 ARY(0,0)="271798^RXN^RXNORM^PSN" ARY(0,1)="TRI-NORINYL 28 Day
 Pack" ARY(3170306,1)="Activated" 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   RXCUI (#.01) field from the RxNorm Concept Names and
 Sources File (#129.2).  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This optional parameter is the coding System to
 perform the lookup on. For RxNorm, "RXN" is the only valid value to send. If
 not passed in, defaults to "RXN".  
VARIABLES: .RESULT                      TYPE: Both
 VARIABLES DESCRIPTION:   Pass by reference parameter that returns the
 Activation History information.  
                             
 RESULT(0)       : Number of Histories Found RESULT(0,0)     : A four-piece "^"
 delimited string 
         1. IEN from RXNCONSO 
         2. Source Abbreviation - "RXN" 
         3. Nomenclature - "RXNORM" 
         4. TTY from RXNCONSO RESULT(0,1):    STR RESULT(<date>,<status>):
 Comment 
         where: date is the date in FileMan internal date format of the 
                last Activation Status 
  
                status is 1 (Active) or 0 (Inactive) 
  
                Comment is further information ("Activated", "Inactivated", 
                "Re-activated", "Revised").  The comment is dependent on 
                the current and previous statuses.  
VARIABLES: $$HIST                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the return value of the function.  It can
 have one of the following values: 
    Number of activation history entries found 
        or 
    -1 ^ error message 
COMPONENT/ENTRY POINT: $$NDC2RXN(NDC,SUB)
 COMPONENT DESCRIPTION:   This API extracts the RxNorm Concept number if a
 valid NDC code is provided.  
                 
 If a NDC code is found in the RxNorm Simple Concept and Atom Attributes Table
 (129.21), the results are returned as: 
  
 ^TMP(SUB,$J,RXCUI Count,0)=IEN^RXCUI^SAB^SUPPRESS  
               
 Example: 
  
 W $$NDC2RXN^ETSRXN("13668004529","OUT") 1 
  
 >D ^%G Global ^TMP("OUT",$J 
  
 ^TMP("OUT",4471,1,0)="554600^751139^RXNORM^N"" 
VARIABLES: NDC                          TYPE: Input
 VARIABLES DESCRIPTION:   NDC Code (in the Code field, #.05) field from the
 RxNorm Simple Concept and Aton Attributes file (#129.21).  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter used to specify the subscript used
 to store the data in.  If not passed in, the default is "ETSNDC".  
VARIABLES: $$NDC2RXN                    TYPE: Output
 VARIABLES DESCRIPTION:   One of the following three values: 
    0 - Component not used 
    1 - Success, results returned 
        or 
   -1^<error message> - Error 
COMPONENT/ENTRY POINT: $$PERIOD(CODE,SYS,.RESULT)
 COMPONENT DESCRIPTION:   This API allows a user to view the activation periods
 of a given RXCUI.  
  
 Example: >W $$PERIOD^ETSRXN(749151,"RXN",.ARY) 1^PSN^RXN^RXNORM^RXNORM 
  
 >ZW ARY ARY(0)="1^PSN^RXN^RXNORM^RXNORM" ARY(3170306)="^^271798;ETSRXN(129.2^" 
 ARY(3170306,0)="TRI-NORINYL 28 Day Pack" 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   RXCUI (#.01) field from the RxNorm Concept Names and
 Sources File (#129.2).  
VARIABLES: SYS                          TYPE: Input
 VARIABLES DESCRIPTION:   This optional parameter is the coding System to
 perform the lookup on. For RxNorm, "RXN" is the only valid value to send. If
 not passed in, defaults to "RXN".  
VARIABLES: .RESULT                      TYPE: Both
 VARIABLES DESCRIPTION:   Pass by reference parameter that returns the
 activation periods.  
                             
 ARY(0)-Five piece "^" delimited string or -1^Message (no period or error) 
   1  # of Activation Periods Found 
   2  Not Used 
   3  Source Abbreviation ("RXN") 
   4  Nomenclature ("RXNORM") 
   5  Source Title ("RXNORM") 
                             
 RESULT(<Activation Date>): Four-piece "^" string: 
         1.      Inactivation Date 
         2.      Not used 
         3. Variable Pointer to the RXNCONSO file - "<IEN>;ETSRXN(129.2" 
         4.      Not Used RESULT(<Activation Date>,0): STR 
         Where: Activation Date is the date the RXCUI and SAB was activated 
VARIABLES: $$PERIOD                     TYPE: Output
 VARIABLES DESCRIPTION:   This is the same output as returned on the 0 node of
 the output array.  
                             
 Five piece "^" delimited string or -1^Message (no period or error) 
   1  # of Activation Periods Found 
   2  Not Used 
   3  Source Abbreviation ("RXN") 
   4  Nomenclature ("RXNORM") 
   5  Source Title ("RXNORM") 
COMPONENT/ENTRY POINT: $$RXN2OUT(RXCUI,SUB)
 COMPONENT DESCRIPTION:   This API extracts a VA Unique ID and NDC if a valid
 RXCUI is provided.  
                 
 If the RXCUI is valid the VA Unique ID and NDC are returned as: 
  
 ^TMP(SUB,$J,RXCUI,"VUID")=Count ^TMP(SUB,$J,RXCUI,"VUID",VUID
 Count,0)=IEN^RXCUI^SAB^TTY^VUID^SUPPRESS ^TMP(SUB,$J,RXCUI,"VUID",VUID
 Count,1)=STR 
  
 ^TMP(SUB,$J,RXCUI,"NDC")=Count ^TMP(SUB,$J,RXCUI,"NDC",NDC
 Count,0)=IEN^RXCUI^CODE^SAB^SUPPRESS ^TMP(SUB,$J,RXCUI,"NDC",NDC Count,1)=ATN 
 ^TMP(SUB,$J,RXCUI,"NDC",NDC Count,2)=ATV 
  
 Example: 
  
 >W $$RXN2OUT^ETSRXN(1190692,"OUT") 2^2 
  
 ^TMP("OUT",9511,1190692,"NDC")=2 
 ^TMP("OUT",9511,1190692,"NDC",1,0)="872342^1190692^4000624^VANDF^O" 
                                 1)="NDC" 
                                 2)="000002100202" 
 ^TMP("OUT",9511,1190692,"NDC",2,0)="872343^1190692^4000624^VANDF^O" 
                                 1)="NDC" 
                                 2)="060267074230" 
 ^TMP("OUT",9511,1190692,"VUID")=2 
 ^TMP("OUT",9511,1190692,"VUID",1,0)="434265^1190692^VANDF^CD^4000624^O" 
                                  1)="ATROPINE SO4 0.4MG TAB" 
 ^TMP("OUT",9511,1190692,"VUID",2,0)="434269^1190692^VANDF^AB^4000624^O" 
                                  1)="ATROPINE SULFATE 0.4MG TAB" 
VARIABLES: RXCUI                        TYPE: Input
 VARIABLES DESCRIPTION:   This parameter is the RxNorm Unique ID for every
 concept in the RxNorm databases.  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter that indicates the subscript for
 the Temporary Deprecated List Array.  If not passed in, defaults to "ETSOUT".  
VARIABLES: $$RXN2OUT                    TYPE: Output
 VARIABLES DESCRIPTION:   One of 2 possible values: 
    # VA Unique IDs found ^ # of NDC Codes found for the requested RXCUI 
         or 
   -1^<error message> - Error 
COMPONENT/ENTRY POINT: $$TAX(VUID,SUB)
 COMPONENT DESCRIPTION:   This API returns all VUIDs for the products in the
 same value set as the valid VUID passed in. If valid values are found, the
 results will be returned as described below: 
                 
 ^TMP(SUB,$J, User-Entered VUID ,"VUID")=Count ^TMP(SUB,$J, User-Entered VUID
 ,"VUID",VUID Count,0)=IEN^RXCUI^SAB^TTY^VUID^SUPPRESS ^TMP(SUB,$J,
 User-Entered VUID ,"VUID",VUID Count,1)=STR ^TMP(SUB,$J, User-Entered VUID
 ,"VUID",VUID Count,2)=ACTIVATION DATE 
  
 Example: >W $$TAX^ETSRXN(4001147,"OUT") 1 
  
 ^TMP("OUT",25599,4001147,"VUID")=1 
 ^TMP("OUT",25599,4001147,"VUID",1,0)="137076^313725^VANDF^IN^4020804^N" 
                                   1)="VITAMIN E OIL" 
                                   2)="MAR 06, 2017" 
VARIABLES: VUID                         TYPE: Input
 VARIABLES DESCRIPTION:   VA Unique ID 
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   This parameter specifies the name of the first
 subscript of the TMP global.  If this parameter is not passed in, the default
 is "ETSTAX".  
VARIABLES: $$TAX                        TYPE: Output
 VARIABLES DESCRIPTION:   The number of RXNORM codes found or -1^error message. 
 
COMPONENT/ENTRY POINT: $$VUI2RXN(CODE,TTY,SUB)
 COMPONENT DESCRIPTION:   This API allows a user to extract the RxNorm Concept
 number(s) if a valid VA Unique ID is provided.  
  
 If a valid VA Unique ID is found in the RxNorm Concept Names and Sources File
 (#129.2), the entries will be returned as: 
  
 ^TMP(SUB,$J,RXCUI Count,0)=IEN^RXCUI^SAB^TTY^CODE^SUPPRESS ^TMP(SUB,$J,RXCUI
 Count,1)=STR 
  
  
 Example: 
  
 W $$VUI2RXN^ETSRXN(4026525,"CD","OUT") 1 
  
 >D ^%G Global ^TMP("OUT",$J 
 ^TMP("OUT",4471,1,0)="273225^751139^VANDF^CD^4026525^N" 
                   1)="LAMOTRIGINE 25MG TAB,35,KIT" 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   VA Unique ID (in the Code field, #.04) field from the
 RxNorm Concept Names and Sources File (#129.2).  
VARIABLES: TTY                          TYPE: Input
 VARIABLES DESCRIPTION:   TERM_TYPE TTY (#.03) field from the RxNorm Concept
 Names and Sources File (#129.2).  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter that indicates the subscript for
 the Temporary Deprecated List Array.  If not passed in, defaults to "ETSRXN".  
VARIABLES: $$VUI2RXN                    TYPE: Output
 VARIABLES DESCRIPTION:   Output value to the function.  Either: 
    1 - successful check 
    0 - does not exist 
       or 
   -1^<error message> - error occurred 
COMPONENT/ENTRY POINT: $$VUICLASS(VUID,SUB)
 COMPONENT DESCRIPTION:   This API retrieves the VUIDs for all products sharing
 the same ATC drug class as the valid VUID passed in.  
                 
 If the lookup was successful, the API will return the data in the format 
 below.  
  
 ^TMP(SUB,$J, User-Entered VUID ,"VUID")=Count ^TMP(SUB,$J, User-Entered VUID
 ,"VUID",VUID Count,0)=IEN^RXCUI^SAB^TTY^VUID^SUPPRESS ^TMP(SUB,$J,
 User-Entered VUID ,"VUID",VUID Count,1)=STR 
  
 Example 
  
 >W $$VUICLASS^ETSRXN(4025394,"OUT") 78 
  
 ^TMP("OUT",25599,4025394,"VUID")=78 
 ^TMP("OUT",25599,4025394,"VUID",1,0)="34736^198051^VANDF^CD^4025402^N" 
                                   1)="OMEPRAZOLE 20MG CAP,EC" 
 ^TMP("OUT",25599,4025394,"VUID",2,0)="34737^198051^VANDF^CD^4025403^N" 
                                   1)="OMEPRAZOLE 20MG CAP,EC,UD" 
 ^TMP("OUT",25599,4025394,"VUID",3,0)="34738^198051^VANDF^AB^4025402^N" 
                                   1)="OMEPRAZOLE 20MG EC CAP" 
 ^TMP("OUT",25599,4025394,"VUID",4,0)="34739^198051^VANDF^AB^4025403^N" 
                                   1)="OMEPRAZOLE 20MG EC CAP UD" 
 ^TMP("OUT",25599,4025394,"VUID",5,0)="39642^199119^VANDF^CD^4025400^N" 
                                   1)="OMEPRAZOLE 10MG CAP,EC" 
  
         <Partial listing displayed> 
VARIABLES: VUID                         TYPE: Input
 VARIABLES DESCRIPTION:   VA Unique ID (in the Code field, #.04) field from the
 RxNorm Concept Names and Sources File (#129.2).  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   This parameter specifies the name of the first
 subscript of the TMP global.  If this parameter is not passed in, the default
 is "ETSCLA".  
VARIABLES: $$VUICLASS                   TYPE: Output
 VARIABLES DESCRIPTION:   # of RXCUIs found 
        or -1^<error message> - Error 
  DATE ACTIVATED: JUN 08, 2018

NUMBER: 6759                            IA #: 6759
  DATE CREATED: MAY 01, 2017            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: DGWPT BYWARD
  REMOTE PROCEDURE: DGWPT BYWARD
 GENERAL DESCRIPTION:   
 **********************************************************************
 This ICR was retired as of 10/27/17 when HMP was shut down.  HMP*2.0*12 
 released on 10/17/17 is an informational patch outlining the steps for the
 sites to shut down the application.  If HMP is reactivated in the future, the
 HMP project team should review the access provided by this ICR with the
 custodial application before the ICR is reactivated.  See VistA Document
 Library (VDL) for list of retired HMP ICRs.  
 **********************************************************************
  
  
 The Enterprise Health MGMT Platform (HMP) calls the DGWPT BYWARD RPC in order
 to retreive the current list of patients for the specified ward.  
  STATUS: Retired                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: OCT 27, 2017
KEYWORDS: DGWPT BYWARD
KEYWORDS: HMP
KEYWORDS: BYWARD
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM
  DATE ACTIVATED: OCT 18, 2017

NUMBER: 6760                            IA #: 6760
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(
  DATE CREATED: MAY 03, 2017
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  NAME: READ FILE ENTRY DATE            ID: GMR(
GLOBAL REFERENCE: GMR(123,D0,.01
FIELD NUMBER: .01                       FIELD NAME: FILE ENTRY DATE
  ACCESS: Read w/Fileman
  STATUS: Withdrawn

NUMBER: 6761                            IA #: 6761
  DATE CREATED: MAY 18, 2017            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGDHLE
  NAME: Update patient demographics via HL7 w/VI
  ID: MAGDHLE
 GENERAL DESCRIPTION:   VistA Imaging provides a routine type entry point that
 will build and broadcast HL7 ADT A08 Patient Information Update messages to
 subscribers of ADT messages.  
  
 A HL7 ADT A47 Change Patient Identifier List message will also be built and
 broadcast for each SSN change.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAG HL7 CUSTODIAN
KEYWORDS: SENDA08
KEYWORDS: MAGDHLE
KEYWORDS: RAHLRS
COMPONENT/ENTRY POINT: SENDA08
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This variable identifies the patient's record number
 in the PATIENT (#2) file.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   VistA Radiology/Nuclear Medicine (RIS) will use the
 call to SENDA08^MAGDHLE to build and broadcast ADT A08 HL7 messages to
 radiology subscribers.  
  DATE ACTIVATED: SEP 14, 2017

NUMBER: 6762                            IA #: 6762
  FILE NUMBER: 810.4                    GLOBAL ROOT: PXRM(810.4,
  DATE CREATED: MAY 18, 2017            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Reminder List Rule
  ID: PXRM(810.4,
GLOBAL REFERENCE: PXRM(810.4,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   ORDER ENTRY/RESULTS REPORTING would like to access the
 Reminder List Rule file (#810.4). This will be used to update the list of
 patients in an OE/RR List (commonly called CPRS Team List) using a reminder
 list rule. We are requesting to be able to point to this file as well as
 access the NAME field (#.01).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Reminder List Rule
KEYWORDS: List
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: SEP 26, 2017

NUMBER: 6763                            IA #: 6763
  DATE CREATED: MAY 19, 2017            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOREJP1
  NAME: ELIGIBILITY                     ID: PSOREJP1
 GENERAL DESCRIPTION:   APIs in PSOREJP1 concern third-party payer information. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$ELIGDISP
 COMPONENT DESCRIPTION:   This API returns either TRICARE, CHAMPVA, or <blank>
 according to the eligibility of the patient.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   Prescription number, pointer to file# 52,
 PRESCRIPTIONS.  
VARIABLES: RFL                          TYPE: Input
 VARIABLES DESCRIPTION:   Fill number, 0 for original fill, 1 for first refill,
 etc.  
VARIABLES: $$ELIGDISP                   TYPE: Output
 VARIABLES DESCRIPTION:   TRICARE, CHAMPVA, or <blank>.  
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: AUG 02, 2017

NUMBER: 6764                            IA #: 6764
  DATE CREATED: MAY 19, 2017            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: BPSOSL
  NAME: DEVELOPER LOG                   ID: BPSOSL
 GENERAL DESCRIPTION:   BPSOSL contains APIs for adding entries to the BPS LOG
 file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LOG
 COMPONENT DESCRIPTION:   LOG adds a single message to the BPS LOG file for the
 specified BPS TRANSACTION.  
VARIABLES: SLOT                         TYPE: Input
 VARIABLES DESCRIPTION:   SLOT is usually a BPS TRANSACTION, but it could also
 be a communication log.  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   Message text to be added to the log.  
VARIABLES: SPECIAL                      TYPE: Input
 VARIABLES DESCRIPTION:   If it contains a "D", the date will be added to the
 message.  If it contains a "T", the time will be added to the message.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: AUG 02, 2017

NUMBER: 6765                            IA #: 6765
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19,
  DATE CREATED: MAY 22, 2017            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: DELETION OF DIC(S) VALUE FROM OPTION
  ID: DIC(19,
GLOBAL REFERENCE: DIC(19,D0,34)
FIELD NUMBER: 34                        FIELD NAME: DIC(S)
  LOCATION: 34;E1,245                   ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Used in conjunction with INQUIRE and EDIT type options
 for screening entry selection.  Enter executable MUMPS code that will screen
 out entries that should NOT be selected.  An entry is only selectable when the
 executable code produces a truth value of 1.  
 GENERAL DESCRIPTION:   During installation by KIDS distribution of a patch
 which updates an option's definition to delete a DIC(S) value, although the
 value of other fields are overlaid with the incoming values, the existing
 DIC(S) value is not nulled out when the incoming value is null.  The
 post-install routine must include logic like invoking FILE^DIE() to remove the
 value from the Option (#19) file entry.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DIC(S)
KEYWORDS: OPTION FILE
SUBSCRIBING PACKAGE: IFCAP
 SUBSCRIBING DETAILS:   As the existing DIC(S) value is not nulled out when the
 incoming value is null.  The post-install routine must include logic like
 invoking FILE^DIE() to remove the value.  In a back-out patch I am proposing
 the use of logic similar to the following to null out the value of the Option 
 (#19) file's DIC(S) (#34) field for the PRCO EDI VENDOR entry: 
     
     N PRCDA S PRCDA=$$LKOPT^XPDMENU("PRCO EDI VENDOR") 
     I PRCDA>0 D 
     . D BMES^XPDUTL("Deleting edit screen from option PRCO EDI VENDOR") 
     . N PRCARR,PRCERR S PRCARR(19,PRCDA_",",34)="@" 
     . D FILE^DIE("EK","PRCARR","PRCERR") 
     D CLEAN^DILF 
     
 Hence, IFCAP is requesting permission to update the value of the DIC(S) field
 via a VA FileMan API like FILE^DIE(), as the screen deletion is not handled by
 sending the new definition for an option as set up in the KIDS Build
 definition.  

NUMBER: 6766                            IA #: 6766
  DATE CREATED: MAY 22, 2017            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  NAME: ESSO VALIDATE FOR FILEMAN INTEGRATED WEB SERVICE
 GENERAL DESCRIPTION:   This API allows ESSO^XUESSO4 to be called from the
 DIFSMAIN routine.  
  STATUS: Pending
KEYWORDS: SECURITY
KEYWORDS: VALIDATE
KEYWORDS: ESSO

NUMBER: 6767                            IA #: 6767
  FILE NUMBER: 661.3                    GLOBAL ROOT: RMPR(661.3,
  DATE CREATED: JUN 06, 2017            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROS ITEM LOCATION FILE ACCESS
  ID: RMPR(661.3,
GLOBAL REFERENCE: RMPR(661.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: LOCATION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ADDRESS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: STATION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(661.3,D0,1,0)
FIELD NUMBER: 1                         FIELD NAME: HCPCS
  LOCATION: 661.31;1                    ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(661.3,D0,1,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: ITEM
  LOCATION: 661.312;1                   ACCESS: Read w/Fileman
FIELD NUMBER: 22                        FIELD NAME: QUANTITY
  LOCATION: 661.312;2                   ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: COST
  LOCATION: 661.312;3                   ACCESS: Read w/Fileman
FIELD NUMBER: 24                        FIELD NAME: UNIT OF ISSUE
  LOCATION: 661.312;4                   ACCESS: Read w/Fileman
FIELD NUMBER: 25                        FIELD NAME: VENDOR
  LOCATION: 661.312;5                   ACCESS: Read w/Fileman
FIELD NUMBER: 26                        FIELD NAME: RE-ORDER LEVEL
  LOCATION: 661.312;6                   ACCESS: Read w/Fileman
FIELD NUMBER: 27                        FIELD NAME: DETAILED INVENTORY ID
  LOCATION: 661.312;7                   ACCESS: Read w/Fileman
FIELD NUMBER: 28                        FIELD NAME: DESCRIPTION
  LOCATION: 661.312;8                   ACCESS: Read w/Fileman
FIELD NUMBER: 30                        FIELD NAME: AVERAGE COST
  LOCATION: 661.312;10                  ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: ORDERED QUANTITY
  LOCATION: 661.312;11                  ACCESS: Read w/Fileman
FIELD NUMBER: 32                        FIELD NAME: RECEIVED QUANTITY
  LOCATION: 661.312;12                  ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(661.3,D0,1,'B'
 GLOBAL DESCRIPTION:   File 661.3 'B' cross reference  Used to look up by HCPCS 
                                 within LOCATION 
GLOBAL REFERENCE: RMPR(661.3,D0,1,D1,1,'B'
 GLOBAL DESCRIPTION:   File 661.312 'B' cross reference  Used to look up by
 ITEM 
                                   within LOCATION/HCPCS 
 GENERAL DESCRIPTION:   The Pros Item Location file is read during Orthotic and
 Lab Work Order processing and during Stock Issue processing in order to
 display the location of the selected item.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   This is a retro-active ICR activation, for the ICR
 which has been in use since release of patch DSSO*2*0 in 2019. A Prosthetics
 custodian developer is not available to approve, so ICR Team activated due to 
 reasonableness given the role of APAT to interface with Prosthetics in the
 enterprise.  
  DATE ACTIVATED: APR 13, 2023

NUMBER: 6768                            IA #: 6768
  DATE CREATED: JUN 19, 2017            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCEF75
  NAME: IBCEF75 PROVIDER ID APIS        ID: IBCEF75
 GENERAL DESCRIPTION:   APIs that return Provider ID information.  
  STATUS: Active
COMPONENT/ENTRY POINT: $$TAXID
 COMPONENT DESCRIPTION:   The returned value will contain two pieces, delimited
 by ^: The 1st piece is the Billing Provider Primary ID.  The 2nd piece is the
 Federal Tax Number.  
VARIABLES: TAXID                        TYPE: Output
 VARIABLES DESCRIPTION:   The returned value will contain two pieces, delimited
 by ^: The 1st piece is the Billing Provider Primary ID.  The 2nd piece is the
 Federal Tax Number.  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: NOV 29, 2017

NUMBER: 6769                            IA #: 6769
  DATE CREATED: JUN 20, 2017            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: SD RECEIVE OR Protocol
 GENERAL DESCRIPTION:   This agreement grants permission to Order Entry /
 Result Reporting to use the protocol in order to send appointment requests to
 Scheduling.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SD RECEIVE OR
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: AUG 23, 2017

NUMBER: 6770                            IA #: 6770
  DATE CREATED: JUN 20, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: OR RECEIVE Protocol
 GENERAL DESCRIPTION:   This agreement grants permission for the subscribing
 packages to use the protocol OR RECEIVE to transmist updates to Order
 Entry/Results reporting. The updates would be related to orders - things such
 as status changes, results completed, etc.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OR RECEIVE
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
SUBSCRIBING PACKAGE: DIETETICS
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  DATE ACTIVATED: AUG 23, 2017

NUMBER: 6771                            IA #: 6771
  DATE CREATED: JUN 20, 2017
  CUSTODIAL PACKAGE: ENROLLMENT APPLICATION SYSTEM
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: EASECU
  NAME: DBIA6771                        ID: EASECU
 GENERAL DESCRIPTION:   Registration Version 5.3 has one routine DGRPD which 
 displays the Patient Inquiry calls DIS^EASECU to display the patient's current
 LTC Copay Test status and test date.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LTC
COMPONENT/ENTRY POINT: DIS
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
SUBSCRIBING PACKAGE: REGISTRATION
  DATE ACTIVATED: AUG 09, 2017

NUMBER: 6772                            IA #: 6772
  DATE CREATED: JUN 22, 2017            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMGEV
  NAME: CLINICAL REMINDERS GENERIC EVALUATOR
  ID: PXRMGEV
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to execute various components within the Clinical Reminders package, such as
 order checks and list rules.  
  
 Revision History: 
  -3/26/25- Effective with patch PXRM*2.0*81, added Reminder Terms as an item
 that can be evaluated and made it so multiple list rules can be pass to the
 API.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GEV
KEYWORDS: REMINDER ORDER CHECKS
KEYWORDS: REMINDER LIST RULES
COMPONENT/ENTRY POINT: EN(RESULT,PARAMETERS)
 COMPONENT DESCRIPTION:   This is the main entry point.  
VARIABLES: RESULT                       TYPE: Both
 VARIABLES DESCRIPTION:   Reference to a variable that will contain the global
 node address of the result global ^TMP($J,SUB) after this component finishes
 executing. The value of SUB comes from the PARAMETERS("SUB") node. The result
 global has the following format: 
  
  ^TMP($J,SUB,0)=STATUS^MESSAGE 
    STATUS: Success or failure. Possible values are 
            -1 for an error, 0 for no data returned 
            and 1 for data was returned.  
    MESSAGE: Error message. This piece is only set 
             when the STATUS is -1.  
  
 Order Checks: 
  ^TMP($J,SUB,ORDER_IEN)=ORQ1^CAP 
    ORDER_IEN: Internal entry number (IEN) of the 
               order in the ORDER file (#100).  
    ORQ1: Data returned from EN^ORQ1 call (refer to 
          the DETAIL Input variable in integration 
          agreement #3154 for how this section is 
          formatted).  
    CAP: CURRENT AGENT/PROVIDER field (#1) in the 
         ORDER file (#100), in internal format.  
  ^TMP($J,SUB,ORDER_IEN,"RULES",RULE)="" 
    RULE: RULE NAME (#.01) field in the REMINDER 
          ORDER CHECK RULES file (#801.1).  
    Only rules that evaluate as true for this order 
    are returned.  
  ^TMP($J,SUB,ORDER_IEN,"GROUPS",GROUP)="" 
    GROUP: GROUP NAME field (#.01) in the REMINDER 
           ORDER CHECK ITEMS GROUP file (#801).  
    Only those groups that contain this order's 
    orderable item(s) are returned.  
  ^TMP($J,SUB,ORDER_IEN,"TX",LINE)=TEXT 
    LINE: Line number of text.  
    TEXT: Order text as returned by the EN^ORQ1 
          call (refer to the TMP('ORR',$J,ORLIST,i) 
          Output variable in integration agreement 
          #3154 for details).  
  ^TMP($J,SUB,ORDER_IEN,"OI",OI)=DATA 
    OI: IEN of the orderable item in the ORDERABLE 
        ITEMS file (#101.43).  
    DATA: Data returned from OIS^ORX8 call (refer 
          to the OIS component in integration 
          agreement #2467 for how this section is 
          formatted).  
  
 List Rules: 
  ^TMP($J,SUB,RULE,INSTANCE,DFN)="" 
      RULE: NAME field (#.01) in the REMINDER LIST 
            RULE file (#810.4).  
  INSTANCE: Whole number; allows running of same 
            list rule set with different 
            parameters.  
       DFN: IEN of the patient in the PATIENT file 
            (#2).  
    All of the patients that satisfy the rule's 
    criteria are returned descendant from the RULE 
    node.  
  ^TMP($J,SUB,RULE,DFN,"DATA",TYPE)=VALUE 
    TYPE: The second comma-piece of the DATA TYPE 
          field (#.01) in the DATA field (#1) in 
          the PATIENTS field (#30) in the REMINDER 
          PATIENT LIST file (#810.5).  
    VALUE: The VALUE field (#.02) in the DATA field 
           (#1) in the PATIENTS field (#30) in the 
           REMINDER PATIENT LIST file (#810.5).  
  ^TMP($J,SUB,RULE,"PATIENT LIST CREATED")=NAME 
    NAME: NAME field (#.01) in the REMINDER 
          PATIENT LIST file (#810.5) for the 
          patient list that was created.  
  
 Reminder Definitions: ^TMP($J,SUB,REMINDER)="STATUS^DUE DATE^LAST DONE" 
   REMINDER: IEN of the entry from file 811.9 or 
             the .01 value of the file entry.  
     STATUS: The reminder evaluation status as a 
             string value 
   DUE DATE: The date the reminder is due 
  LAST DONE: The date the reminder evaluation 
             determines as the last time the 
             reminder was completed.  
  
      The following subscript will only be returned 
      if pass in parameters specified if they 
      should returned.  
  
 ^TMP($J,SUB,REMINDER,"PRINT NAME")= 
      Reminder's print name (or name if print name 
      is null) ^TMP($J,SUB,REMINDER,"FIEVAL")= 
      Merged copy of the FIEVAL array.  ^TMP($J,SUB,REMINDER,"MAINTENANCE",X)= 
      Line X of the maintenance output.  
  
 ^TMP($J,SUB,REMINDER,"FINDINGS",COMPONENT REMINDER)= 
      "STATUS^DUE DATE^LAST DONE" 
   If REMINDER has the VA-REMINDER DEFINITION 
   computed finding and its SAVETEMP parameter 
   value is 1, then data for the COMPONENT 
   REMINDER that is executed is returned under 
   this node.  ^TMP($J,SUB,REMINDER,"FINDINGS",COMPONENT REMINDER,"FIEVAL")= 
  
   Merged copy of the FIEVAL array for 
   COMPONENT REMINDER that is executed as a 
   finding, where COMPONENT REMINDER is the 
   PRINT NAME of that reminder.  ^TMP($J,SUB,REMINDER,"FINDINGS",COMPONENT
 REMINDER,"MAINTENANCE",X)= 
  
   Line X of the maintenance output for COMPONENT 
   REMINDER that is executed as a finding, where 
   COMPONENT REMINDER is the PRINT NAME of that 
   reminder.  
  
 Reminder Terms ^TMP($J,SUB,"TERMS",TERM)=RESULT 
   TERM: The IEN of the entry from file 811.5, 
         or the .01 of the entry from file 811.5.  RESULT: 1 for the term
 applies to the patient 
         or 0 the term does not apply to the 
         patient.  
  
      The following subscript will only be returned 
      if pass in parameters specified if they 
      should returned.  
  
 ^TMP($J,SUB,"TERMS",TERM,"FIEVAL")=Merged copy of 
         the term FIEVAL array.  ^TMP($J,SUB,"TERMS",TERM,"DETAIL
 TEXT",X,0)=Line 
         X of the term. 
VARIABLES: PARAMETERS                   TYPE: Input
 VARIABLES DESCRIPTION:   Reference to an array that contains the input data.
 This array has the following format: 
  
 For all types: 
  PARAMETERS("SUB")=SUB 
    SUB: Name of the subscript in the global 
         ^TMP($J) under which to return data.  
  
 For reminder order checks: 
  PARAMETERS("DFN")=DFN 
    DFN: IEN of the patient in the PATIENT file 
         (#2).  
  PARAMETERS("ROC",ROC)="" 
    The "ROC" node specifies the group name(s) to 
    use during the order check. If one of the 
    orderable item(s) in the list of orders is 
    contained in one of these groups and at least 
    one of the rules associated with that group is 
    applicable, then the order check is generated. 
    ROC: GROUP NAME field (#.01) in the REMINDER 
         ORDER CHECK ITEMS GROUP file (#801) OR 
         "ALL" to specify all groups.  
  
  There are two options to identify the orders to 
  check: the caller can request the API to search 
  for orders based on criteria specified by the 
  caller or the caller can identify the orders for 
  the API.  
                                              
  To search for orders, the following is required 
  unless otherwise specified: 
  PARAMETERS("ROC DISPLAY GROUPS",DG)="" 
    The "ROC DISPLAY GROUPS" node specifies a list 
    of display group(s) used in searching for 
    orders.  
    DG: NAME field (#.01) in the DISPLAY GROUP file 
        (#100.98).  
  PARAMETERS("ROC STATUS",STATUS)="" 
    The "ROC STATUS" node specifies a list of order 
    status(es) used in searching for orders.  
    STATUS: NAME field (#.01) in the ORDER STATUS 
            file (#100.01).  
  When searching for orders, you may optionally 
  specify a date range by using one of the 
  following groups of dates (you can specify both 
  groups in the same call and both nodes in a group 
  are required): 
  GROUP 1: 
  PARAMETERS("ROC START")=START 
    START: Date, in internal FileMan format, that 
           signifies the earliest date for an 
           order's DATE/TIME ORDERED field (#.01) 
           value in the ORDER ACTIONS multiple 
           field (#.8) in the ORDER file (#100).  
           This date applies to all orders whose 
           display group parameter does not have 
           a start date.  
  PARAMETERS("ROC STOP")=STOP 
    STOP: Date, in internal FileMan format, that 
          signifies the latest date for an order's 
          DATE/TIME ORDERED field (#.01) value in 
          the ORDER ACTIONS multiple field (#.8) in 
          the ORDER file (#100). This date applies 
          to all orders whose display group 
          parameter does not have a stop date.  
  GROUP 2: 
  PARAMETERS("ROC DISPLAY GROUPS",DG,"START")=START 
    START: Date, in internal FileMan format, that 
           signifies the earliest date for an 
           order's DATE/TIME ORDERED field (#.01) 
           value in the ORDER ACTIONS multiple 
           field (#.8) in the ORDER file (#100).  
           This date overrides the value in 
           PARAMETERS("ROC START") and is only 
           applicable to orders with the display 
           group DG.  
  PARAMETERS("ROC DISPLAY GROUPS",DG,"STOP")=STOP 
    STOP: Date, in internal FileMan format, that 
          signifies the latest date for an order's 
          DATE/TIME ORDERED field (#.01) value in 
          the ORDER ACTIONS multiple field (#.8) in 
          the ORDER file (#100). This date 
          overrides the value in 
          PARAMETERS("ROC STOP") and is only 
          applicable to orders with the display 
          group DG.  
  PARAMETERS("ROC ORDERED WITHIN")="" 
    An optional flag that indicates the order's 
    WHEN ENTERED field (#4) value in the ORDER file 
    (#100) should fall within the specified date 
    range.  
  
  To identify the orders, the following is 
  required: 
  PARAMETERS("ROC ORDERS",ORDER)="" 
    The "ROC ORDERS" node specifies a list of 
    orders to execute order checks against.  
    ORDER: IEN of the order in the ORDER file 
           (#100).  
  
  PARAMETERS("ROC RETURN TYPE",TYPE)="" 
    Nodes descendant from "ROC RETURN TYPE" specify 
    the type(s) of data to return.  
    TYPE: the type of data to return and is one of 
          the following: 
          "GROUPS" for group names, which are 
                   returned descendant from 
                   ^TMP($J,SUB,ORDER_IEN,"GROUPS") 
          "RULES" for rule names, which are 
                  returned descendant from 
                  ^TMP($J,SUB,ORDER_IEN,"RULES") 
          "OI" for orderable item IENs, which are 
               returned descendant from 
               ^TMP($J,SUB,ORDER_IEN,"OI") 
  
 For reminder list rules: 
  PARAMETERS("LR",RULE,INSTANCE)=PARAMS 
     RULE: IEN of the rule in the REMINDER LIST 
           RULE file (#810.4) to evaluate.  INSTANCE: Whole number; allows
 running of same 
           list rule set with different 
           parameters.  
   PARAMS: Caret-delimited string ('^') of 
           parameters for the specified rule's 
           evaluation: 
            "PNAME ^ START ^ STOP ^ SECURE ^ 
                    OVERWRITE ^ RETURN" 
      PNAME - Name of the patient list to create in 
              the PATIENT LIST file (#810.5).  
          START - Date, in internal FileMan format, 
                  that signifies the earliest date 
                  for rule evaluation.  
          STOP - Date, in internal FileMan format, 
                 that signifies the latest date for 
                 rule evaluation.  
          SECURE - Boolean flag indicating how 
                   secure the patient list should 
                   be; 1 for secure (private) and 0 
                   for not secure (public).  
          OVERWRITE - Boolean flag indicating if an 
                      existing patient list with 
                      the same PNAME should be 
                      overwritten; 1 for overwrite 
                      and 0 for do not overwrite.  
          RETURN - Boolean flag indicating whether 
                   to return the patients' data 
                   (the DATA field, #1, in the 
                   PATIENTS field, #30, in the 
                   REMINDER PATIENT LIST file, 
                   #810.5) in nodes descendant from 
                   ^TMP($J,SUB,RULE,DFN,"DATA"); 1 
                   for return the data and 0 for do 
                   not return the data.  
  
 Reminder Definitions: 
  PARAMETERS("REMINDERS",REMINDER)=PARAMS 
   REMINDER: Reminder definition to execute; either 
             the definition's IEN, NAME or 
             PRINT NAME.  
     PARAMS: Caret-delimited string ('^') of 
             parameters for the specified 
             reminder's evaluation: 
             "SAVE_FIEVAL^MAINTENANCE_FORMAT^DATE" 
  
        SAVE_FIEVAL: 1 or 0, set to one to return 
                     the FIEVAL array MAINTENANCE_FORMAT: How to format the
 maintenance 
                     section that is copied into 
                     the return TMP global; see the 
                     description for the OUTPUT 
                     parameter in the MAIN^PXRM 
                     line tag for acceptable 
                     values.  
               DATE: The date to use for evaluation 
                     in FileMan format, if not 
                     defined set to DT.  
  
 Reminder Terms: PARAMETERS("TERMS",TERM)=PARAMS 
   TERM: The IEN of the entry from file 811.5, or 
         the .01 of the entry from file 811.5.  PARAMS: Caret-delimited string
 ('^') of parameters 
         for the specified term's evaluation: 
              "DATE^RETURN FIEVAL^RETURN TEXT" 
  
              DATE: The date to use for evaluation 
                    in FileMan format, if not 
                    defined set to DT.  
     RETURN FIEVAL: 1 or 0, set to one to return 
                    the FIEVAL array.  
       RETRUN TEXT: 1  or 0, set to one to return 
                    the term output text.  
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAR 17, 2025

NUMBER: 6773                            IA #: 6773
  DATE CREATED: JUN 22, 2017
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: DOCUMENT ACTION ANCILLARY DATA DISPLAY
 GENERAL DESCRIPTION:   This integration agreement allows subscribers to attach
 items to the TIU DOCUMENT ACTION DISPLAY protocol, which will display an
 onscreen message provided by the subscriber to TIU users when a document is
 deleted, retracted or reassigned.  
  
 The following data is available to subscribers: 
  ^TMP("TIUDOCDIS",$J,"PATIENT")=DFN 
   DFN: internal entry number of the patient in the PATIENT file (#2) 
  ^TMP("TIUDOCDIS",$J,"VISIT")=VISIT 
   VISIT: internal entry number of the visit in the VISIT file (#9000010) 
  ^TMP("TIUDOCDIS",$J,"DOCUMENT")=DOC IEN^DOC NAME 
   DOC IEN: internal entry number of the document in the TIU DOCUMENT file 
            (#8925) 
   DOC NAME: name of the document in the TIU DOCUMENT DEFINITION file 
             (#8925.1) 
  ^TMP("TIUDOCDIS",$J,"ACTION")=ACTION 
   ACTION: the action taken on the document; either "DELETE", "RETRACT" or 
           "REASSIGN" 
   
 Place the text to display in the ^TMP global with the following structure: 
   
  ^TMP("TIUDOCDIS",$J,"MESSAGES",DISPLAY)=LINE COUNT 
    DISPLAY: the display name of the package as it should appear to the 
             user; for example, "Women's Health" 
    LINE COUNT: total number of lines to display to the user 
   
  ^TMP("TIUDOCDIS",$J,"MESSAGES",DISPLAY,N)=TEXT 
    N: line number of text, starting at one and incrementing by one 
    TEXT: the line of text to display. The subscriber is responsible for 
          ensuring that the length is not more than 80 characters as TIU 
          will not wrap the text that is displayed. When the text is 
          displayed in the CPRS GUI, it will wrap depending on the screen 
          size of the user's display; subscribers should not assume that 
          how the text is displayed in a roll and scroll environment is how 
          it will appear in a GUI environment.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU DOCUMENT ACTION DISPLAY
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
 SUBSCRIBING DETAILS:   Attached the WV DISPLAY ASSOCIATED DATA protocol.  
  DATE ACTIVATED: NOV 21, 2017

NUMBER: 6774                            IA #: 6774
  DATE CREATED: JUN 26, 2017
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DOCUMENT ACTION NOTIFICATION
 GENERAL DESCRIPTION:   This protocol will notify subscribers when a document
 is deleted, retracted or reassigned.  
  
 The following data is available to subscribers: 
 ^TMP("TIUDOCAT",$J,"ACTION")=ACT 
  ACT: the action taken on the document; possible values are "DELETE", 
       "RETRACT", and "REASSIGN" 
  
 When ACT is "DELETE" or "RETRACT", 
  ^TMP("TIUDOCAT",$J,"PATIENT")=DFN 
   DFN: internal entry number of the document's patient in the PATIENT 
        file (#2) 
  ^TMP("TIUDOCAT",$J,"VISIT")=VISIT 
   VISIT: internal entry number of the document's visit in the VISIT file 
          (#9000010) 
  ^TMP("TIUDOCAT",$J,"DOCUMENT")=DOC IEN^DOC NAME 
    DOC IEN: internal entry number of the document in the TIU DOCUMENT file 
             (#8925) 
    DOC NAME: name of the document in the TIU DOCUMENT DEFINITION file 
              (#8925.1) 
  
 When ACT is "REASSIGN", 
  ^TMP("TIUDOCAT",$J,"PATIENT","OLD")=DFN 
   DFN: internal entry number of the document's patient in the PATIENT 
        file (#2) before reassignment 
  ^TMP("TIUDOCAT",$J,"PATIENT","NEW")=DFN 
   DFN: internal entry number of the document's patient in the PATIENT 
        file (#2) after reassignment 
  ^TMP("TIUDOCAT",$J,"VISIT","OLD")=VISIT 
   VISIT: internal entry number of the document's visit in the VISIT file 
          (#9000010) before reassignment 
  ^TMP("TIUDOCAT",$J,"VISIT","NEW")=VISIT 
   VISIT: internal entry number of the document's visit in the VISIT file 
          (#9000010) after reassignment 
  ^TMP("TIUDOCAT",$J,"DOCUMENT","OLD")=DOC IEN^DOC NAME 
    DOC IEN: internal entry number of the retracted document in the TIU 
             DOCUMENT file (#8925) 
    DOC NAME: name of the retracted document in the TIU DOCUMENT DEFINITION 
              file (#8925.1) 
  ^TMP("TIUDOCAT",$J,"DOCUMENT","NEW")=DOC IEN^DOC NAME 
    DOC IEN: internal entry number of the reassigned document in the TIU 
             DOCUMENT file (#8925) 
    DOC NAME: name of the reassigned document in the TIU DOCUMENT 
              DEFINITION file (#8925.1) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU DOCUMENT ACTION EVENT
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
 SUBSCRIBING DETAILS:   Attached the WV ACT ON DOCUMENT ACTION protocol.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 8/13/21. The VPR listener protocol is VPR TIU
 RETRACT and will be attached to the TIU DOCUMENT ACTION EVENT protocol with
 patch VPR*1*27.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Added 3/1/22. The PXRM ACT ON DOCUMENT ACTION listener
 protocol will be attached to the TIU DOCUMENT ACTION EVENT protocol, effective
 with PXRM*2.0*78.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Added 5/18/23. The GMRC listener protocol is GMRC ACT
 ON DOCUMENT ACTION and will be attached to the TIU DOCUMENT ACTION EVENT
 protocol with patch GMRC*3*208.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 5/18/23. The OR listener protocol is OR ACT ON
 DOCUMENT ACTION and was attached to the TIU DOCUMENT ACTION EVENT protocol
 with released patch OR*3*519, compliance date December 29, 2020.  
  DATE ACTIVATED: NOV 21, 2017

NUMBER: 6775                            IA #: 6775
  GLOBAL ROOT: %ZTSCH                   DATE CREATED: JUN 26, 2017
  CUSTODIAL PACKAGE: KERNEL             USAGE: Private
  TYPE: File                            NAME: HMP CHECK OF %ZTSCH GLOBAL
  ID: %ZTSCH
GLOBAL REFERENCE: %ZTSCH
 GENERAL DESCRIPTION:   The Enterprise Health MGMT Platform (HMP) needs to make
 a check to see if a task exists in the %ZTSCH global and if the task exist, if
 it is still active. HMP does this by checking to see if a lock can be obtained
 for the task in %ZTSCH, if the lock can be obtained then the job is not active
 and the HMP EXTRACT RESOURCE slot that is in use by that task can be cleared. 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: %ZTSCH
KEYWORDS: HMP
SUBSCRIBING PACKAGE: HEALTH MANAGEMENT PLATFORM

NUMBER: 6776                            IA #: 6776
  DATE CREATED: JUN 26, 2017            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Private                        TYPE: Routine
  ROUTINE: WVRPCGF1                     NAME: WV APIS FOR CLINICAL REMINDERS
  ID: WVRPCGF1
 GENERAL DESCRIPTION:   This provides a list of APIs used by the Clinical
 Reminder packages for procedure tracking from the Women's Veterans files in
 CPRS, effective with CPRS 31.B, patches WV*1.0*24 and PXRM*2.0*45 for SMART
 alert functionality.  
  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: WVRPCGF1
COMPONENT/ENTRY POINT: GETTEST
 COMPONENT DESCRIPTION:   This entry point returns the text of a Women's Health
 procedure in a local variable. It also returns the primary diagnosis as a pass
 by reference variable.  
  
VARIABLES: WVIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   This variable is the record IEN from WV PROCEDURE
 file, file #790.1.  
  
VARIABLES: TEXT                         TYPE: Output
 VARIABLES DESCRIPTION:   This variable returns the text of a WV PROCEDURE file
 entry in an a local array format of TEXT(n)="text".  
  
VARIABLES: DIAG                         TYPE: Output
 VARIABLES DESCRIPTION:   This variable returns the output text from
 RESULT/DIAGNOSIS field from the WV PROCEDURE file entry.  
  
COMPONENT/ENTRY POINT: $$NEXTPROC
 COMPONENT DESCRIPTION:   This entry point returns the patients next procedure
 name and date it is due based from the WV PATIENT file, file $790.  
  
 The result return is based off the procedure type pass to the entry point.  
  
 The output is returned as a string PROCEDURE NAME^PROCEDURE DATE 
  
  
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient DFN from file 2.  
  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   This value determines which fields to return from
 file #790: 
  
 BR: for Breast Treatment   (returns fields BR TX NEED^BR TX NEED DUE DATE) CX:
 for Cervical Treatment (returns fields CX TX NEED^CX TX NEED DUE DATE) 
  
  
COMPONENT/ENTRY POINT: GETWVP
 COMPONENT DESCRIPTION:   This entry report returns an array of text to the
 calling application. The array of text contains a subset of fields from file
 WV PROCEDURE file, file #790.1 and WV NOTIFICATION file, file *790.4.  
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient DFN from file #2.  
  
VARIABLES: ITEM                         TYPE: Input
 VARIABLES DESCRIPTION:   The record IEN from file 790.1.  
  
VARIABLES: TEXT                         TYPE: Output
 VARIABLES DESCRIPTION:   TEXT is a local array pass by reference it returns
 the text output in the format TEXT(n)="TEXT".  
  
  
COMPONENT/ENTRY POINT: VIEWDATA
 COMPONENT DESCRIPTION:   This entry point is used by Clinical Reminders to
 display different text reports when the user requests to view the output text
 type in a Clinical Reminder Dialog in CPRS.  
  
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   DATA is an array of strings by package file entry,
 file number, an integer value.  
  
 DATA("WOMEN"S HEALTH",790.1,n)=STRING 
  
 Where string contains the following fields 
  
 SUBSCRIPT^VALUE^PROMPT IEN^SUBSCRIPT 
  
 Based off the subscript fields and the value field, this API determines which 
 text report to send back to the calling application.  
  
  
VARIABLES: PAT                          TYPE: Input
 VARIABLES DESCRIPTION:   PAT is the patient DFN from file #2.  
  
VARIABLES: FINDVAL                      TYPE: Input
 VARIABLES DESCRIPTION:   FINDVAL is a colon delimited string of record IEN
 from the WV PROCEDURE file, file #790.1.  
  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULT is a local array that returns the different
 text reports back to the calling application in the following format
 TEXT(n)="TEXT".  
  
  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 6777                            IA #: 6777
  DATE CREATED: JUN 28, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: OR COMPLETE ORDER
 GENERAL DESCRIPTION:   The purpose of this ICR is to grant access to packages
 that need to subscribe to OR COMPLETE ORDER protocol. The purpose of the
 protocol OR COMPLETE ORDER is to notify other packages that an order has been
 marked complete in the Computerized Patient Record System.  
  
 The following information will be passed into the protocol in the array 
 ORINFO. Any subscribers will have access to it: 
  
      ORINFO("OR0")=0 node of the ORDER file (#100) 
      ORINFO("OR3")=3 node of the ORDER file (#100) 
      ORINFO("OR4")=4 node of the ORDER file (#100) 
      ORINFO("OR6")=6 node of the ORDER file (#100) 
      ORFINO("OR7")=7 node of the ORDER file (#100) 
      ORINFO("DIALOG")=Dialog IEN for the dialog used to create this order 
                       (pointer to the ORDER DIALOG file (#101.4) 
      ORFINO("RESPONSES")=Responses from the 4.5 level of the ORDER file 
                          (#100) 
                                                                
 The OR COMPLETE ORDER protocol will be distributed in OR*3*397. It's called
 when the RPC, ORWDXA COMPLETE is invoked.  
  
 Subscribing Packages will be added to the ICR as they are identified and 
 approved by CPRS.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OR COMPLETE ORDER
  DATE ACTIVATED: SEP 25, 2018

NUMBER: 6778                            IA #: 6778
  FILE NUMBER: 661.6                    GLOBAL ROOT: RMPR(661.6,
  DATE CREATED: JUL 03, 2017            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PROS INVENTORY TRANSACTION FILE ACCESS
  ID: RMPR(661.6,
GLOBAL REFERENCE: RMPR(661.6,D0,0)
FIELD NUMBER: .01                       FIELD NAME: HCPCS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: QUANTITY
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: VALUE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: HCPCS ITEM
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: VENDOR
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: STATION
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: LOCATION
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DATE&TIME STAMP
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: SEQUENCE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: TRANSACTION TYPE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: COMMENT
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: USER
  LOCATION: 0;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(661.6,'B')
 GLOBAL DESCRIPTION:   Used to look up the IEN of a HCPCS 
GLOBAL REFERENCE: RMPR(661.6,'ASHD')
 GLOBAL DESCRIPTION:   Used to look up the IEN of a STATION & HCPCS & DATE&TIME
 STAMP 
GLOBAL REFERENCE: RMPR(661.6,'C')
 GLOBAL DESCRIPTION:   Used to look up a DATE&TIME STAMP 
 GENERAL DESCRIPTION:   The Pros Inventory Transaction file is read during the
 display of a Prosthetics Inventory Program (PIP) stock issue in order to
 present inventory transaction information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/23/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires access to the PROS
 inventory transaction file 661.6 
  DATE ACTIVATED: JUL 30, 2020

NUMBER: 6779                            IA #: 6779
  FILE NUMBER: 661.11                   GLOBAL ROOT: RMPR(661.11,
  DATE CREATED: JUL 03, 2017            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PROSTHETIC HCPCS ITEM MASTER FILE ACCESS
  ID: RMPR(661.11,
GLOBAL REFERENCE: RMPR(661.11,D0,0)
FIELD NUMBER: .01                       FIELD NAME: HCPCS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: HCPCS ITEM
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DESCRIPTION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: STATION
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: SOURCE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: UNIT OF ISSUE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: PSAS ITEM
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: ITEM MASTER
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: STATUS
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: INACTIVATION DATE
  LOCATION: 0;10                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(661.11,'ASHI'
 GLOBAL DESCRIPTION:   File 661.11 'ASHI' cross reference  Used to look up the
 IEN of 
                                     a STATION, HCPCS, and 
                                     HCPCS ITEM 
GLOBAL REFERENCE: RMPR(661.11,'B'
 GLOBAL DESCRIPTION:   File 661.11 'B' cross reference  Used to look up by
 HCPCS Name 
                                  as it appears in file 661.1 
GLOBAL REFERENCE: RMPR(661.11,'ASHD'
 GLOBAL DESCRIPTION:   File 661.11 'ASHD' cross reference  Used to look up and
 sort by 
                                     STATION, HCPCS, DESCRIPTION 
GLOBAL REFERENCE: RMPR(661.11,'ASHMDI'
 GLOBAL DESCRIPTION:   File 661.11 'ASHMDI' look up index  Used to look up and
 sort by 
                                     STATION, HCPCS, ITEM MASTER, 
                                     DESCRIPTION, and HCPCS ITEM 
 GENERAL DESCRIPTION:   The Prosthetic HCPCS Item Master file is read during
 the display of a Prosthetics Inventory Program (PIP) stock issue in order to
 present Prosthetic HCPCS Item Master information.  
  
 Amended: Added 1/12/23, effective with DSSO*2.0*3, APAT requested adding
 'ASHMDI' index. This is to identify the MANUFACTURER and MFG PART NO.
 associated with items in Prosthetics Inventory that have a specified STATION
 and PSAS HCPCS.  The MANUFACTURER and MFG PART NO. are associated with the 
 ITEM MASTER (#441) item referenced in the "ASHMDI" index.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/29/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires information for the
 Prosthetic HCPCS Item Master File Access.  
  DATE ACTIVATED: JAN 17, 2023

NUMBER: 6780                            IA #: 6780
  FILE NUMBER: 420.5                    GLOBAL ROOT: PRCD(420.5,
  DATE CREATED: JUL 03, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SRHLU                        NAME: HL7 VERSION CHECK
  ID: SRHLU
 GENERAL DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call V^SRHLU, which returns boolean value that tells whether the
 HL7 messaging is compatible with 1.5 version. If the answer is yes, then no
 HL7 message will be sent.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: V
 COMPONENT DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call V^SRHLU, which returns boolean value that tells whether the
 HL7 messaging is compatible with 1.5 version. If the answer is yes, then no
 HL7 message will be sent.  
VARIABLES: SR15                         TYPE: Output
 VARIABLES DESCRIPTION:   HL7 1.5 compatibility 

NUMBER: 6781                            IA #: 6781
  DATE CREATED: JUL 03, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SRHLZIU                      NAME: SURGICAL HL7 TRANSMISSION
  ID: SRHLZIU
 GENERAL DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call MSG^SRHLZIU, which sends ZIU message for various events such
 as S12 New Appointment, S13 Reschedule, S14 Modification, S15 Cancellation,
 and S17 Deletion.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: MSG
 COMPONENT DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call MSG^SRHLZIU, which sends ZIU message for various events such
 as S12 New Appointment, S13 Reschedule, S14 Modification, S15 Cancellation,
 and S17 Deletion.  
VARIABLES: CASE                         TYPE: Input
 VARIABLES DESCRIPTION:   Surgery Case Number 
VARIABLES: SRSTATUS                     TYPE: Input
 VARIABLES DESCRIPTION:   Surgery Case Status 
VARIABLES: SREVENT                      TYPE: Input
 VARIABLES DESCRIPTION:   Surgical Event 

NUMBER: 6782                            IA #: 6782
  DATE CREATED: JUL 03, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SRHLUO
  NAME: SURGICAL OUTGOING HL7 STANDARD SEGMENT UTILITIES
  ID: SRHLUO
 GENERAL DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call SRHLUO routines which contains various utility modules to
 build outgoing surgery HL7 standard segments.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: AL1
 COMPONENT DESCRIPTION:   This component is called when AL1 segment is built
 for surgery HL7 message which contains allergy information.  
VARIABLES: SRI                          TYPE: Input
 VARIABLES DESCRIPTION:   Incremental Variable ^TMP("HLS",$J,SRI) 
VARIABLES: SRENT                        TYPE: Input
 VARIABLES DESCRIPTION:   Temporary global node ^TMP(SRENT,$J) 
COMPONENT/ENTRY POINT: DG1
 COMPONENT DESCRIPTION:   This component is called when DG1 segment is build
 for surgery HL7 message which contains diagnosis information.  
VARIABLES: SRI                          TYPE: Input
 VARIABLES DESCRIPTION:   Incremental variable ^TMP("HLS",$J,SRI) 
VARIABLES: SRENT                        TYPE: Input
 VARIABLES DESCRIPTION:   Temporary global node ^TMP(SRENT,$J) 
COMPONENT/ENTRY POINT: OBX
 COMPONENT DESCRIPTION:   This component is called when OBX segment is build
 for surgery HL7 message which contains observational information.  
VARIABLES: SRI                          TYPE: Input
 VARIABLES DESCRIPTION:   Incremental variable ^TMP("HLS",$J,SRI) 
VARIABLES: Y
VARIABLES: SRENT                        TYPE: Input
 VARIABLES DESCRIPTION:   Temporary global variable ^TMP(SRENT,$J) 
COMPONENT/ENTRY POINT: PID
 COMPONENT DESCRIPTION:   This component is called when PID segment is build
 for surgery HL7 message which contains patient information.  
VARIABLES: SRI                          TYPE: Input
 VARIABLES DESCRIPTION:   Incremental variable ^TMP("HLS",$J,SRI) 
VARIABLES: SRENT                        TYPE: Input
 VARIABLES DESCRIPTION:   Temporary global node ^TMP(SRENT,$J) 

NUMBER: 6783                            IA #: 6783
  DATE CREATED: JUL 03, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SRHLUO1
  NAME: SURGICAL OUTGOING HL7 CUSTOM SEGMENT UTILITIES 1
  ID: SRHLUO1
 GENERAL DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call SRHLUO1 routines, which contains various utility modules to
 build HL7 custom segments.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: ZCH
 COMPONENT DESCRIPTION:   This component is called when ZCH segment is built
 for surgery HL7 message which contains case information.  
VARIABLES: SRI                          TYPE: Input
 VARIABLES DESCRIPTION:   Incremental variable ^TMP("HLS",$J,SRI) 
VARIABLES: SREVENT                      TYPE: Input
 VARIABLES DESCRIPTION:   Surgery event (S12, S13, etc) 
VARIABLES: SRSTATUS                     TYPE: Input
 VARIABLES DESCRIPTION:   Surgery case status 
VARIABLES: SRENT                        TYPE: Input
 VARIABLES DESCRIPTION:   Temporary global node ^TMP(SRENT,$J) 
COMPONENT/ENTRY POINT: ZIG
 COMPONENT DESCRIPTION:   This component is called when ZIG segment is built
 for surgery HL7 message which contains appointment information.  
VARIABLES: SRI                          TYPE: Input
 VARIABLES DESCRIPTION:   Incremental variable ^TMP("HLS",$J,SRI) 
VARIABLES: SRENT                        TYPE: Input
 VARIABLES DESCRIPTION:   Temporary global node ^TMP(SRENT,$J) 
COMPONENT/ENTRY POINT: ZIL
 COMPONENT DESCRIPTION:   This component is called when ZIL segment is built
 for surgery HL7 message which contains location information.  
VARIABLES: SRI                          TYPE: Input
 VARIABLES DESCRIPTION:   Incremental variable ^TMP("HLS",$J,SRI) 
VARIABLES: SRENT                        TYPE: Input
 VARIABLES DESCRIPTION:   Temporary global node ^TMP(SRENT,$J) 
COMPONENT/ENTRY POINT: ZIP
 COMPONENT DESCRIPTION:   This component is called when ZIP segment is built
 for surgery HL7 message which contains personnel information.  
VARIABLES: SRI                          TYPE: Input
 VARIABLES DESCRIPTION:   Incremental variable ^TMP("HLS",$J,SRI) 
VARIABLES: SRENT                        TYPE: Input
 VARIABLES DESCRIPTION:   Temporary global node ^TMP(SRENT,$J) 

NUMBER: 6784                            IA #: 6784
  DATE CREATED: JUL 03, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SRHLUO2
  NAME: SURGICAL OUTGOING HL7 CUSTOM SEGMENT UTILITIES 2
  ID: SRHLUO2
 GENERAL DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call SRHLUO2 routines which contains various utility modules to
 build custom HL7 segments.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: ZIS
 COMPONENT DESCRIPTION:   This component is called when ZIS segment is built
 for surgery HL7 message which contains service information.  
VARIABLES: SRI                          TYPE: Input
 VARIABLES DESCRIPTION:   Incremental variable ^TMP("HLS",$J,SRI) 
VARIABLES: SRENT                        TYPE: Input
 VARIABLES DESCRIPTION:   Temporary global node ^TMP(SRENT,$J) 

NUMBER: 6785                            IA #: 6785
  DATE CREATED: JUL 03, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SROUTL                       NAME: SURGICAL CASE LOCK/UNLOCK
  ID: SROUTL
 GENERAL DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call SROUTL, which contains various utility modules including
 locking, and unlocking surgical cases so that cases can be modified without
 being modified by other processes.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: LOCK
 COMPONENT DESCRIPTION:   This component locks the surgery case so that data
 can be modified without being overwritten by competing processes.  
VARIABLES: SRCASE                       TYPE: Input
 VARIABLES DESCRIPTION:   Surgery Case Number to be locked 
VARIABLES: SRLCK                        TYPE: Output
 VARIABLES DESCRIPTION:   Lock Success flag 
COMPONENT/ENTRY POINT: UNLOCK
 COMPONENT DESCRIPTION:   This component unlocks the surgery case so that data
 can be modified by other processes.  
VARIABLES: SRCASE                       TYPE: Input
 VARIABLES DESCRIPTION:   Surgery Case Number to be unlocked 

NUMBER: 6786                            IA #: 6786
  DATE CREATED: JUL 03, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SROUTL0                      NAME: SURGERY CASE'S DIVISION SETUP
  ID: SROUTL0
 GENERAL DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call SROUTL0  which contains various utility modules including
 getting divisions of a given OR.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: DIV
 COMPONENT DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call SROUTL0 which contains various utility modules including
 getting divisions of a given OR.  
VARIABLES: CASE                         TYPE: Input
 VARIABLES DESCRIPTION:   Surgery Case Number 
VARIABLES: SRDIV                        TYPE: Output
 VARIABLES DESCRIPTION:   Surgery Division Number 

NUMBER: 6787                            IA #: 6787
  DATE CREATED: JUL 03, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SROERR0                      NAME: SURGICAL CASE STATUS
  ID: SROERR0
 GENERAL DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call STATUS^SROERR0 to find status about a given surgery case.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: STATUS
 COMPONENT DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call STATUS^SROERR0 to find status about a given surgery case.  

NUMBER: 6788                            IA #: 6788
  DATE CREATED: JUL 03, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SRSBUTL                      NAME: SURGICAL CASE STATUS II
  ID: SRSBUTL
 GENERAL DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call DIS1^SRSBUTL to check and set new service block for surgery
 availability graph.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: DIS1
 COMPONENT DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call DIS1^SRSBUTL to check and set new service block for surgery
 availability graph.  

NUMBER: 6789                            IA #: 6789
  DATE CREATED: JUL 03, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SRSGRPH                      NAME: SURGERY DRAW GRAPH
  ID: SRSGRPH
 GENERAL DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call ^SRSGRPH to draw surgery OR room availability graph.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL

NUMBER: 6790                            IA #: 6790
  DATE CREATED: JUL 03, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SRSCG                        NAME: SURGERY CANCEL GRAPH
  ID: SRSCG
 GENERAL DESCRIPTION:   This integration agreement allows the DSS PeriOp
 Manager to call ^SRSCG to update graph when a case is cancelled.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL

NUMBER: 6791                            IA #: 6791
  DATE CREATED: JUL 06, 2017            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  ROUTINE: PXRMCWH1                     NAME: ORDER CHECK TEXT
  ID: PXRMCWH1
 GENERAL DESCRIPTION:   This integration agreement allows the subscribing
 package to retrieve a portion of a reminder definition evaluation's clinical
 maintenance section for inclusion in a reminder order check's text that is
 displayed to an end user.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DEFINITION TEXT
COMPONENT/ENTRY POINT: $$ROCTEXT(DFN)
 COMPONENT DESCRIPTION:   This line tag returns a portion of a reminder
 definition evaluation's clinical maintenance section.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient's entry in
 the PATIENT file (#2).  
VARIABLES: $$ROCTEXT                    TYPE: Output
 VARIABLES DESCRIPTION:   The node address where the output is stored preceded
 with the characters 
 "~@".
VARIABLES: TMP GLOBAL                   TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP("PXRM ROC TEXT",$J,LINE,0)=TEXT 
   LINE: line number of text; starts at one 
         and increments by one 
   TEXT: a line of text to display to the user 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Text Integration Utilities will display the text within
 an object.  

NUMBER: 6792                            IA #: 6792
  DATE CREATED: JUL 06, 2017            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMCWH1
  NAME: NUMER OF DAYS IN EDD GRACE PERIOD
  ID: PXRMCWH1
 GENERAL DESCRIPTION:   This integration agreement allows subscribers to obtain
 the number of days in the Expected Due Date (EDD) grace period. The grace
 period is defined as a parameter to the VA-WH PATIENT DOCUMENTATION reminder 
 computed finding in the VA-WH UPDATE PREGNANCY STATUS reminder definition. If
 this parameter does not exist, a hard-coded default period is used.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$GETGRACD()
 COMPONENT DESCRIPTION:   Calculates the number of days in the EDD grace
 period.  
VARIABLES: $$GETGRACD                   TYPE: Output
 VARIABLES DESCRIPTION:   The number of days in the EDD grace period.  
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
  DATE ACTIVATED: JAN 21, 2021

NUMBER: 6793                            IA #: 6793
  GLOBAL ROOT: DD(                      DATE CREATED: JUL 06, 2017
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: LOOK FOR ENTRIES POINTING TO VISIT ENTRIES
  ID: DD(
GLOBAL REFERENCE: DD(9000010,0,'PT',
 GLOBAL DESCRIPTION:   This index lists all of the files and their fields that
 point to the VISIT file (#9000010).  
GLOBAL REFERENCE: DD(FILE,FIELD,1,XREF,0
 GLOBAL DESCRIPTION:   The third piece of this node differentiates MUMPS type
 cross-references from other types of cross-references.  
GLOBAL REFERENCE: DD(FILE,FIELD,1,XREF,1
 GLOBAL DESCRIPTION:   This node contains executable M code that will SET the
 cross-reference.  
 GENERAL DESCRIPTION:   This integration agreement allows the subscribing
 package to determine all of the entries that point to an entry in the VISIT
 file (#9000010). Read-only global access is granted to the global references
 listed below.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: POINTED TO
KEYWORDS: INDEX
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   The VISIT file (#9000010) contains the DEPENDENT ENTRY
 COUNT field (#.09) that stores the number of entries that point to the visit.
 PATIENT CARE ENCOUNTER has a maintenance routine that verifies this field's
 value.  
  DATE ACTIVATED: NOV 15, 2017

NUMBER: 6794                            IA #: 6794
  FILE NUMBER: 52.7                     GLOBAL ROOT: PS(52.7
  DATE CREATED: JUL 13, 2017
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: IV SOLUTIONS FILE (#52.7) PREMIX FIELD (#18) FROM PSO
  ID: PS(52.7
 GENERAL DESCRIPTION:   VistA code decides which orders need to go through
 enhanced order checking in PSODDPR* routines, including IV Fluids. This ICR
 will allow the IV SOLUTION File (52.7), PREMIX field (18) to be checked from
 within PSO.  GLOBAL REFERENCE: 
      ^PS(52.7,D0,0) 
        18      PREMIX        0;14    Direct Global Read & w/Fileman 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: JUL 26, 2017

NUMBER: 6795                            IA #: 6795
  DATE CREATED: JUL 13, 2017
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA6795
  STATUS: Pending

NUMBER: 6796                            IA #: 6796
  DATE CREATED: JUL 20, 2017            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMDATE
  NAME: DATE FORMATTING                 ID: PXRMDATE
 GENERAL DESCRIPTION:   Allowing Health Summary to use Clinical Reminders date
 formatting will provide for a consistent display of dates in Clinical
 Reminders output and the Health Summary Clinical Reminders components.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DDATE
KEYWORDS: PXRMDATE
COMPONENT/ENTRY POINT: DDATE
 COMPONENT DESCRIPTION:   This extrinsic function returns an externally
 formatted date.  
  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   The date in FileMan internal format.  
  
VARIABLES: FMT                          TYPE: Input
 VARIABLES DESCRIPTION:   The date formatting string as used by $$FMTE^XLFDT.  
  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: AUG 07, 2017

NUMBER: 6797                            IA #: 6797
  DATE CREATED: JUL 20, 2017            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMFMTO
  NAME: CLINICAL REMINDERS OUTPUT       ID: PXRMFMTO
 GENERAL DESCRIPTION:   Allowing Health Summary to use the Clinical Reminders
 text formatting routines provides for a consistent display of Clinical
 Reminders output in Health Summary Clinical Reminders components and Clinical
 Reminders.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FMTOUT
KEYWORDS: MHVOUT
KEYWORDS: PXRMFMTO
COMPONENT/ENTRY POINT: FMTOUT
 COMPONENT DESCRIPTION:   This entry point produces the formatted Clinical
 Reminders maintenance output.  
  
VARIABLES: TMPSUB                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the first subscript of ^TMP(TMPSUB,$J) which
 contains the unformatted output from a reminder evaluation. TMPSUB is normally
 set to the value PXHRM.  
  
VARIABLES: NL                           TYPE: Both
 VARIABLES DESCRIPTION:   Passed by reference, this is the number of lines of
 output text.  
  
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   Passed by reference, this is the local array
 containing the formatted output text.  
  
COMPONENT/ENTRY POINT: MHVOUT
 COMPONENT DESCRIPTION:   This entry point produces the formatted MyHealtheVet
 output.  
  
VARIABLES: TMPSUB                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the first subscript of ^TMP(TMPSUB,$J) which
 contains the unformatted output from a reminder evaluation. TMPSUB is normally
 set to the value PXHRM.  
  
  
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the status as returned by the reminder
 evaluation.  
  
VARIABLES: RNAME                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the name of the reminder that was evaluated.  
  
VARIABLES: RIEN                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number of the reminder
 that was evaluated.  
  
VARIABLES: NL                           TYPE: Both
 VARIABLES DESCRIPTION:   Passed by reference, this is the number of lines of
 output text.  
  
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   Passed by reference, this is the local array
 containing the formatted output text.  
  
  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: AUG 07, 2017

NUMBER: 6798                            IA #: 6798
  DATE CREATED: JUL 24, 2017            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  ROUTINE: HLTF0                        NAME: UPDATE STATUS OF HL7 MESSAGE
  ID: HLTF0
 GENERAL DESCRIPTION:   This ICR will update the status of the entry in the
 Message Text File and log an event for errors.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: STATUS
 COMPONENT DESCRIPTION:   Updates the status of the entry in the Message Text
 File and logs an event for errors.  
VARIABLES: MTIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of entry in file 772 or 773 
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of new status 
VARIABLES: ERR                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of error message 
VARIABLES: ERRTEXT                      TYPE: Input
 VARIABLES DESCRIPTION:   An error message of up to 200 characters 
VARIABLES: COMDT                        TYPE: Input
 VARIABLES DESCRIPTION:   0/1 1=update DATE/TIME PROCESSED 
VARIABLES: NOEVENT                      TYPE: Input
 VARIABLES DESCRIPTION:   1 if an event should NOT be logged 

NUMBER: 6799                            IA #: 6799
  DATE CREATED: JUL 24, 2017            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  ROUTINE: HLTP                         NAME: GENERATE OUTGOING HL7 MESSAGE
  ID: HLTP
 GENERAL DESCRIPTION:   This ICR allows the creation of an outgoing HL7 message
 and returns a value if there is an error while creating the message.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: GENERATE
 COMPONENT DESCRIPTION:   This entry point allows the creation of a new
 outgoing HL7 message and returns a value if there is an error while creating
 the message.  
VARIABLES: HLMID                        TYPE: Input
 VARIABLES DESCRIPTION:   Message ID of message being generated 
VARIABLES: HLMTIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN in Message Text file 
VARIABLES: HLEID                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of event driver protocol 
VARIABLES: HLARYTYP                     TYPE: Input
 VARIABLES DESCRIPTION:   Array type with set of codes 
VARIABLES: HLFORMAT                     TYPE: Input
 VARIABLES DESCRIPTION:   Format of array 
VARIABLES: HLRESLT                      TYPE: Input
 VARIABLES DESCRIPTION:   Return value 
VARIABLES: HLP                          TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter setting 

NUMBER: 6800                            IA #: 6800
  DATE CREATED: JUL 24, 2017            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  ROUTINE: HLTPCK2A                     NAME: HL7 DE-ESCAPE DELIMITERS
  ID: HLTPCK2A
 GENERAL DESCRIPTION:   This ICR will allow the conversion of HL7 escape
 characters to original characters including field separator, component
 separator, repetition separator, escape characters, and subcomponent
 separator.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: DEESCAPE
 COMPONENT DESCRIPTION:   This entry point will allow the conversion of HL7
 escape characters to original characters including field separator, component
 separator, repetition separator, escape character, and subcomponent separator. 
 
VARIABLES: INPUT                        TYPE: Input
 VARIABLES DESCRIPTION:   Input string 
VARIABLES: HLDATA                       TYPE: Output
 VARIABLES DESCRIPTION:   Output string 1 
VARIABLES: HLOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   Output string 2 

NUMBER: 6801                            IA #: 6801
  DATE CREATED: JUL 24, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORCXPND1                     NAME: GET ORDER RESULTS
  ID: ORCXPND1
 GENERAL DESCRIPTION:   This ICR allows the return of results information for
 orders such as lab, consult, and x-ray.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: ORDERS
 COMPONENT DESCRIPTION:   This entry point returns results information for
 orders such as lab, consult, and x-ray.  

NUMBER: 6802                            IA #: 6802
  DATE CREATED: JUL 24, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORWOR                        NAME: GET ORDER RESULTS BY ID
  ID: ORWOR
 GENERAL DESCRIPTION:   This ICR allows the return of order results when an
 input with order ID is passed in.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: RESULT
 COMPONENT DESCRIPTION:   This entry point allows the return of order results
 when an input with order ID is passed in.  
VARIABLES: REF                          TYPE: Input
 VARIABLES DESCRIPTION:   Return variable 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: ORID                         TYPE: Input
 VARIABLES DESCRIPTION:   Order number 
VARIABLES: ID                           TYPE: Input
 VARIABLES DESCRIPTION:   IEN to file #100 

NUMBER: 6803                            IA #: 6803
  DATE CREATED: JUL 24, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORWORR
  NAME: GET EVENT DELAYED ORDER LIST FOR PATIENT
  ID: ORWORR
 GENERAL DESCRIPTION:   This ICR allows the return of a list of orders that are
 event delayed.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: AGET
 COMPONENT DESCRIPTION:   This entry point returns a list of orders that are
 event delayed.  
VARIABLES: REF                          TYPE: Input
 VARIABLES DESCRIPTION:   Return variable 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: FILTER                       TYPE: Input
 VARIABLES DESCRIPTION:   Indicates which orders to return 
VARIABLES: GROUPS                       TYPE: Input
 VARIABLES DESCRIPTION:   Display group of orders to show 
VARIABLES: DTFROM                       TYPE: Input
 VARIABLES DESCRIPTION:   From date 
VARIABLES: DTTHRU                       TYPE: Input
 VARIABLES DESCRIPTION:   Through date 
VARIABLES: EVENT                        TYPE: Input
 VARIABLES DESCRIPTION:   Event 
VARIABLES: ORRECIP                      TYPE: Input
 VARIABLES DESCRIPTION:   Order received 

NUMBER: 6804                            IA #: 6804
  DATE CREATED: JUL 24, 2017
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  ROUTINE: PXKENC                       NAME: GET PATIENT ENCOUNTER DATA
  ID: PXKENC
 GENERAL DESCRIPTION:   This ICR allows the return of all information about one
 encounter in a global array.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: ENCEVENT
 COMPONENT DESCRIPTION:   This entry point allows the return of all information
 about one encounter in a global array.  
VARIABLES: VISITIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to visit 
VARIABLES: DONTKILL                     TYPE: Input
 VARIABLES DESCRIPTION:   1 if output array is not to be killed 0 otherwise 

NUMBER: 6805                            IA #: 6805
  DATE CREATED: JUL 24, 2017            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  ROUTINE: SCUTBK11                     NAME: SC PATIENT LOOKUP
  ID: SCUTBK11
 GENERAL DESCRIPTION:   This ICR allows the return of patient information using
 a lookup value.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
COMPONENT/ENTRY POINT: FINDP
 COMPONENT DESCRIPTION:   This API return patient information based on a lookup
 value.  
VARIABLES: SCOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   Location of Data 
VARIABLES: SCIN                         TYPE: Input
 VARIABLES DESCRIPTION:   Value to look up 

NUMBER: 6806                            IA #: 6806
  DATE CREATED: JUL 25, 2017            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMDLR3
  NAME: REMINDER DIALOG SEARCHER REPORT APIS
  ID: PXRMDLR3
 GENERAL DESCRIPTION:   This routine provides two APIs that receives either a
 finding item or a list of finding items. This routine will search through the
 REMINDER DIALOG file, file #801.41. It will return any reminder dialog that
 contains the finding item in a written report format.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: REMINDER DIALOG
KEYWORDS: 801.41
COMPONENT/ENTRY POINT: APIONE
 COMPONENT DESCRIPTION:   This API takes a single item and returns which
 reminder dialogs the item is used in a text report format.  
  
 Output in the following format: 
  
 ^TMP($J,SUB,FINDING ITEM,X)=TEXT 
  
 SUB = is the passed in variable 
  
 FINDING = is the variable pointer format of the passed in finding item.  
 "1;ORD(101.41," 
  
 X is incremented numeric value 
  
  
  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   SUB=this is the temp global subscript to return the
 output.  
  
VARIABLES: ITEM                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number the code should
 search for.  
  
VARIABLES: GBL                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the file global the code should search for.
 Example "ORD(101.41," 
  
COMPONENT/ENTRY POINT: APIALL
 COMPONENT DESCRIPTION:   This API takes an array of finding items for the code
 to search for in the Reminder Dialog file, file #801.41.  
  
 Output in the following format: 
  
 ^TMP($J,SUB,FINDING ITEM,X)=TEXT 
  
 SUB = is the passed in variable 
  
 FINDING = is the variable pointer format of the passed in finding item.  
 "1;ORD(101.41," 
  
 X is an incremented numeric value 
  
  
  
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the temp global subscript to return the
 output.  
  
VARIABLES: ITEMS                        TYPE: Input
 VARIABLES DESCRIPTION:   This is an array of finding to search for. The format
 is internal variable pointer format.  
  
 Example ITEMS("1;ORD(101.41,")="" ITEMS("10;ORD(101.41,")="" 
  
  
  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 22, 2022

NUMBER: 6807                            IA #: 6807
  DATE CREATED: JUL 25, 2017            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  ROUTINE: PXRMEOC                      NAME: UPDATE THE EPISODE OF CARE FILE
  ID: PXRMEOC
 GENERAL DESCRIPTION:   This ICR allows a calling application to send data to
 the cascade file to either create an open cascade or add data to the open
 cascade. This ICR also allows a calling application to request the open
 cascade be closed.  
  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: 809
COMPONENT/ENTRY POINT: ADD
 COMPONENT DESCRIPTION:   This entry point allows a calling application to send
 data to PXRM to determine if a cascade entry should be created. Once a cascade
 is open or the patient has a current open cascade the data will be added to
 the cascade entry.  
  
  
VARIABLES: PAT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the patient DFN.  
  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the date/time associated with the data event
 added to the cascade.  
  
  
  
VARIABLES: ITEM                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the data in variable pointer format to add to
 the cascade.  
  
VARIABLES: START                        TYPE: Input
 VARIABLES DESCRIPTION:   This is a boolean value passed by the calling
 application to let PXRM create a cascade if an open one is not found.  
  
  
VARIABLES: CLOSE                        TYPE: Input
 VARIABLES DESCRIPTION:   This is a boolean value used by the code to determine
 if an open cascade should be closed.  
  
VARIABLES: NAME                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the name of the type of cascade to update.  
  
VARIABLES: VISIT                        TYPE: Input
 VARIABLES DESCRIPTION:   This is a pointer value to the Visit File, file
 #9000010.  
  
  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   This will return any error message if the routine
 cannot update a cascade.  
  
VARIABLES:  
COMPONENT/ENTRY POINT: CLOSE
 COMPONENT DESCRIPTION:   This entry point is used to close an open cascade
 without updating any of the items in the cascade.  
  
  
VARIABLES: INPUT                        TYPE: Input
 VARIABLES DESCRIPTION:   This is an array that the system used to close an
 open cascade.  
  
 INPUT("NAME")=X whereas X is the name of the cascade to update INPUT("DFN")=X
 whereas X is the patient DFN.  
  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   This is a return array.  
  
 RESULT(1)=1 the cascade closed without error.  RESULT(0)=-1^Error Message 
  
  
SUBSCRIBING PACKAGE: WOMEN'S HEALTH

NUMBER: 6808                            IA #: 6808
  DATE CREATED: AUG 01, 2017            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMPRAD
  NAME: Determine if radiology procedure is for breast image
  ID: PXRMPRAD
 GENERAL DESCRIPTION:   This ICR provide a way to determine if a Radiology
 Procedure is for a Breast Image, by using Reminder Term. If the Reminder Term
 has a taxonomy assigned to it the API will check the taxonomy for CPT and
 HCPCS codes.  
  
 Amendments: 10/20/22: Added the EARLDATE and BLDTARR components. These were 
 introduced in PXRM*2.0*71, which was part of the SMART enhancements included
 in CPRS v31b.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TERM
KEYWORDS: TAXONOMY
KEYWORDS: PXRM
COMPONENT/ENTRY POINT: GETTRMCD
 COMPONENT DESCRIPTION:   This entry point returns a list of codes for both the
 CPT and HCPCS coding system assigned to the Reminder Term.  
  
  
VARIABLES: TIEN                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN of the Reminder Term from file 811.5. 
  
VARIABLES: TXARRAY                      TYPE: Output
 VARIABLES DESCRIPTION:   This passed by reference array returns a list of CPT
 or HCPCS codes assigned to the passed in reminder term.  
  
VARIABLES: ERROR                        TYPE: Output
 VARIABLES DESCRIPTION:   If this passed by reference variable is defined then
 it contains the error message the entry point returned to the calling
 application.  
  
  
COMPONENT/ENTRY POINT: CHCKPROC
 COMPONENT DESCRIPTION:   This entry point checks to see if a passed in
 CPT/HCPCS code or a radiology procedure is associated to a breast image
 procedure.  
  
VARIABLES: INPUT                        TYPE: Input
 VARIABLES DESCRIPTION:   This is a passed by reference that code and coding
 system and/or radiology procedure entry to determine if it is related to a
 breast images test.  
  
 INPUT("CODE")=the code to check for INPUT("CODESYS")=the coding system to
 check the code is against 
  
 INPUT("ITEMTYPE")= currently only support the global entry for file 71 
 RAMIS(71, INPUT("ITEM")=the IEN of the entry from file 71.  
  
COMPONENT/ENTRY POINT: EARLDATE
 COMPONENT DESCRIPTION:   This entry point returns the REMINDER TERM FINDING
 BEGINNING DATE/TIME in internal FileMan date format.  
VARIABLES: TERMARR                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the WV BREAST IMAGE TERM array created from
 the REMINDER TERM file (#811.5).  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   This returns the REMINDER TERM FINDINGS BEGINNING
 DATE/TIME in the internal FileMan date format.  
COMPONENT/ENTRY POINT: BLDTARR
 COMPONENT DESCRIPTION:   This entry point creates the WV BREAST IMAGE array
 from the REMINDER TERM file (#811.5).  
VARIABLES: TERMARR                      TYPE: Output
 VARIABLES DESCRIPTION:   This returns the WV BREAST IMAGE TERM array from the
 REMINDER TERM file (#811.5).  
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 27, 2022
INTEGRATION REFERENCES Redacted List as of 20261106
                                                     NOV 09, 2026@17:23   PAGE 5
--------------------------------------------------------------------------------


NUMBER: 6809                            IA #: 6809
  DATE CREATED: AUG 01, 2017
  CUSTODIAL PACKAGE: VENDOR - AUDIOFAX, INC.
  NAME: Erroneously entered             STATUS: Withdrawn

NUMBER: 6810                            IA #: 6810
  DATE CREATED: AUG 08, 2017            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: VAFCPTAD                     NAME: CAPRI Call to VAFCPTAD
  ID: VAFCPTAD                          STATUS: Pending
  DURATION: Till Otherwise Agreed
KEYWORDS: VAFCPTAD
COMPONENT/ENTRY POINT: ADD
 COMPONENT DESCRIPTION:   
          .; PARAM("PRFCLTY")=PREFERRED FACILITY 
          .; PARAM("NAME")=NAME (last name minimal; recommend full name) 
          .; PARAM("GENDER")=SEX 
          .; PARAM("DOB")=DATE OF BIRTH 
          .; PARAM("SSN")=SOCIAL SECURITY NUMBER OR NULL IF NONE 
          .; PARAM("SRVCNCTD")=SERVICE CONNECTED? 
          .; PARAM("TYPE")=TYPE 
          .; PARAM("VET")=VETERAN (Y/N)? 
          .; PARAM("FULLICN")=INTEGRATION CONTROL NUMBER AND CHECKSUM 
          .; .301 SERVICE CONNECTED? 
          .; .302 SERVICE CONNECTED PERCENTAGE 
          .; .314 CLAIM FOLDER LOCATION 
          .; .313 CLAIM NUMBER 
          .; .323 PERIOD OF SERVICE 
          .; .326 SERVICE ENTRY DATE [LAST] 
          .; .327 SERVICE SEPARATION DATE [LAST] 
          .; .361 PRIMARY ELIGIBILITY CODE 
          .; .3611 ELIGIBILITY STATUS 
          .; .3612 ELIGIBILITY STATUS DATE 
          .; .525 POW STATUS INDICATED? 
          .; 1901 VETERAN (Y/N)? 
          .; 391 TYPE 
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   When adding new record to other Vista sites, if the
 patient does not exist in that site, we will call ADD^VAFCPTAD to create a new
 patient.  

NUMBER: 6811                            IA #: 6811
  FILE NUMBER: 100.21                   GLOBAL ROOT: OR(100.21,
  DATE CREATED: AUG 14, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: GET TEAM, USERS, AND PRINTER FROM FILE #100.21
  ID: OR(100.21,
GLOBAL REFERENCE: OR(100.21,D0,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.5                       FIELD NAME: DEVICE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: OR(100.21,D0,1,D1,
FIELD NUMBER: 2,.01                     FIELD NAME: USER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: OR(100.21,'B',D0
FIELD NUMBER: IEN                       FIELD NAME: IEN
  LOCATION: NONE                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Text Integration Utilities (TIU) needs read access via
 Fileman to 3 fields of the OE/RR LIST file (#100.21) in order to find a team
 list name, its users, and the printer where alerts are printed. Additionally,
 access to the "B" cross reference is requested to find quickly the team's IEN. 
 
  STATUS: Active
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  DATE ACTIVATED: SEP 21, 2017

NUMBER: 6812                            IA #: 6812
  FILE NUMBER: 43                       GLOBAL ROOT: DG(43,
  DATE CREATED: AUG 21, 2017            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: REGISTRATION FILE USED BY BCMA - DG(43
  ID: DG(43,
GLOBAL REFERENCE: DG(43,D0,'GL'
FIELD NUMBER: 11                        FIELD NAME: MULTIDIVISION MED CENTER?
  LOCATION: GL;2                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The BAR CODE MED ADMIN (BCMA) needs to extract the
 MULTIDIVISION MED CENTER? data from the MAS PARAMETERS file (#43) for use in
 the routine PSBMD to determine if a facility is multidivisional.  
  STATUS: Active
KEYWORDS: BCMA
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
  DATE ACTIVATED: SEP 06, 2017

NUMBER: 6813                            IA #: 6813
  DATE CREATED: AUG 23, 2017            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS GET TOKEN
  REMOTE PROCEDURE: XUS GET TOKEN
 GENERAL DESCRIPTION:   This RPC returns a handle to a token that can be used
 instead of an Access/Verify code authentication to sign on a new process by a
 user that is currently authenticated and active.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XUSRB4
KEYWORDS: TOKEN
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
SUBSCRIBING PACKAGE: RPC BROKER
 SUBSCRIBING DETAILS:   Integrated into the RPC Broker Development Kit (BDK)
 for Delphi GUI clients.  
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   Added 09/27/19 
  DATE ACTIVATED: AUG 30, 2017

NUMBER: 6814                            IA #: 6814
  FILE NUMBER: 3.812                    GLOBAL ROOT: XMB(3.8,D0,6,D1
  DATE CREATED: SEP 12, 2017            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MAIL GROUP REMOTE MEMBER DELETION
  ID: XMB(3.8,D0,6,D1
 GENERAL DESCRIPTION:   Accounts Receivable needs a ONE-TIME ONLY Integration
 Agreement to allow deletion of remote members from a mail group. Since no
 utility exists to delete a remote member from the mail group file, the
 following access is requested: 
    
    1.  The ability to Fileman read ^XMB(3.8) using $$FIND1^DIC 
    2.  The ability to Fileman/global read the remote member subfile 3.812 
        in global ^XMB(3.8,,6) 
    3.  The ability to remove the remote members from a specific mail group 
        using the ^DIK utility.  
  
 This would be done once, in the Post-install routine RCP321, to update the
 RCDPE AUDIT mail group.  
  STATUS: Active
KEYWORDS: 3.8
KEYWORDS: REMOTE MEMBER
KEYWORDS: RCDPE AUDIT
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: SEP 26, 2017

NUMBER: 6815                            IA #: 6815
  DATE CREATED: SEP 14, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SRHLVUI2
  NAME: SURGICAL OUTBOUND HL7 GENERATION UTILITY FOR NTE
  ID: SRHLVUI2
 GENERAL DESCRIPTION:   SURGICAL OUTBOUND HL7 GENERATION UTILITY FOR NTE will
 allow DSS Integration Framework to generate an NTE segment based on OBR
 segment. NTE segment contains comments and other free texts written by care
 providers.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: NTE
VARIABLES: NTE                          TYPE: Output
 VARIABLES DESCRIPTION:   Output string that contains finished NTE 
VARIABLES: OBR                          TYPE: Input
 VARIABLES DESCRIPTION:   Input OBR needed to generate NTE segment 

NUMBER: 6816                            IA #: 6816
  FILE NUMBER: 133.2                    GLOBAL ROOT: SRO(133.2
  DATE CREATED: SEP 14, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: File
  NAME: SURGERY CONFIGURATION FILE ACCESS
  ID: SRO(133.2
GLOBAL REFERENCE: SRO(133.2,D0
 GLOBAL DESCRIPTION:   Uses $O to iterate the surgery file 
GLOBAL REFERENCE: SRO(133.2,'AC'
 GLOBAL DESCRIPTION:   Used to look up by TEXT 
 GENERAL DESCRIPTION:   This integration agreement will allow the DSS
 Integration Framework to iterate through the list in ^SRO(133.2) global as
 well as look up its internal entry number by TEXT through the use of "AC"
 cross reference. NO direct reads or writes to the globals will be done. The
 primary purpose of the ICR is to iterate this file in D0 node (1,2,3...etc),
 and "AC" cross reference.  
  
 ^SRO(133.2,D0) Uses $O to iterate the surgery file 
  
 File 133.2 "AC" cross-reference   used to look up by TEXT 
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 6817                            IA #: 6817
  FILE NUMBER: 101.43                   GLOBAL ROOT: ORD(101.43,
  DATE CREATED: SEP 14, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: ORDERABLE LOOKUP ORDERABLE ITEMS
  ID: ORD(101.43,
GLOBAL REFERENCE: ORD(101.43,D0
 GLOBAL DESCRIPTION:   Uses $D to check if given node exists 
GLOBAL REFERENCE: ORD(101.43,'B'
 GLOBAL DESCRIPTION:   Used to look up by name 
 GENERAL DESCRIPTION:   This integration agreement will allow the DSS CyberREN
 to check whether the primary node exists, as well as look up internal entry
 number with NAME field through the use of "B" cross reference. No direct reads
 or writes to the globals will be done. The primary purpose of the ICR is to 
 check whether the node exists using $D, and calculate the internal entry 
 number given its name.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 6818                            IA #: 6818
  DATE CREATED: SEP 14, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORCSAVE                      NAME: ORDER SAVE RESPONSES
  ID: ORCSAVE
 GENERAL DESCRIPTION:   ORDER SAVE RESPONSES will allow the DSS CyberREN to
 take responses in ORDIALOG() and save into ^OR(100,ORIFN,4.5) 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RESPONSE

NUMBER: 6819                            IA #: 6819
  DATE CREATED: SEP 14, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORCSAVE1                     NAME: ORDER BUILD AND SAVE ORDER TEXT
  ID: ORCSAVE1
 GENERAL DESCRIPTION:   ORDER BUILD AND SAVE ORDER TEXT will allow the DSS
 CyberREN to build and save order text from ORDIALOG() into ORDER file.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ORDTEXT
VARIABLES: ORDER                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal file entry to ORDER file.  

NUMBER: 6820                            IA #: 6820
  DATE CREATED: SEP 14, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORCSIGN
  NAME: ORDER TRIGGER UNSIGNED ORDER NOTIFICATION
  ID: ORCSIGN
 GENERAL DESCRIPTION:   ORDER TRIGGER UNSIGNED ORDER NOTIFICATION will allow
 the DSS CyberREN to send a notification for unsigned orders.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: NOTIF

NUMBER: 6821                            IA #: 6821
  DATE CREATED: SEP 14, 2017
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORWDLR32                     NAME: ORDER LOAD ORDERS FOR LAB TEST
  ID: ORWDLR32
 GENERAL DESCRIPTION:   ORDER LOAD ORDERS FOR LAB TEST will allow the DSS
 CyberREN to take lab test as an input and return all orders that have the lab
 test.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LOAD
VARIABLES: LIST                         TYPE: Output
 VARIABLES DESCRIPTION:   Array that will contain a list of orders.  
VARIABLES: TESTID                       TYPE: Input
 VARIABLES DESCRIPTION:   Lab Test internal file number 

NUMBER: 6822                            IA #: 6822
  DATE CREATED: SEP 14, 2017            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  ROUTINE: SDVSIT2                      NAME: OUTPATIENT ENCOUNTER LOOKUP
  ID: SDVSIT2
 GENERAL DESCRIPTION:   OUTPATIENT ENCOUNTER LOOKUP will allow the DSS CyberREN
 to take patient, appointment date/time, hospital location, as well as visit
 file pointer and return all outpatient encounter IENs matching the given
 criteria.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: getapt
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file IEN 
VARIABLES: SDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Appointment Date/Time 
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   Hospital Location file IEN for Appt 
VARIABLES: SDVIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Visit file pointer [optional] 

NUMBER: 6823                            IA #: 6823
  FILE NUMBER: 811.5                    DATE CREATED: SEP 14, 2017
  CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: File
  NAME: Points to PXRMD(811.5)
GLOBAL REFERENCE: PXRMD(811.5,D0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This agreements documents the package that have
 permission to point to the Reminder Term file, file #811.5 from within their
 own package files.  
  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
SUBSCRIBING PACKAGE: WOMEN'S HEALTH

NUMBER: 6824                            IA #: 6824
  FILE NUMBER: 790.1                    DATE CREATED: SEP 14, 2017
  CUSTODIAL PACKAGE: WOMEN'S HEALTH     USAGE: Private
  TYPE: File                            NAME: ACCESS TO WV(790.1
GLOBAL REFERENCE: WV(790.1,D0)
FIELD NUMBER: .01                       FIELD NAME: ACCESSION#
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This agreements documents the usages of the package
 that have permission to point to the WV PROCEDURE file, file #790.1 from
 within their own package files.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: WV
KEYWORDS: PXRM
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 6825                            IA #: 6825
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19
  DATE CREATED: OCT 18, 2017            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: CHANGE NAME OF OPTION IBCNR RELEASE OF INFORMATION
  ID: DIC(19
GLOBAL REFERENCE: DIC(19,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   eBusiness product owners wish to change the name of the
 existing option IBCNR RELEASE OF INFORMATION to IBCNR ROI SENSITIVE DRUG MGMT
 as part of patch IB*2.0*617. Permission is required to Accomplish this name
 change using a pre-install routine. This agreement is one time only and
 expires with the installation of IB*2.0*617.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OPTION
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAR 06, 2018

NUMBER: 6826                            IA #: 6826
  FILE NUMBER: 19.2                     GLOBAL ROOT: DIC(19.2,
  DATE CREATED: OCT 18, 2017            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RAIPS135
  NAME: SCHEDULE AN OPTION SILENTLY SET 'USER TO RUN TASK' FIELD
  ID: RAIPS135
GLOBAL REFERENCE: DIC(19.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: QUEUED TO RUN AT WHAT TIME
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DEVICE FOR QUEUED JOB OUTPUT
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: RESCHEDULING FREQUENCY
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(19.2,D0,1.1)
FIELD NUMBER: 11                        FIELD NAME: USER TO RUN TASK
  LOCATION: 1.1;1                       ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   The VistA Radiology/Nuclear Medicine (RIS) application
 requests permission to schedule a RIS option with the 'USER TO RUN TASK' field 
 (#11) in the OPTION SCHEDULING (#19.2) file.  
  
 The Kernel option 'RESCH^XUTMOPT()' or 'Set Up Option Schedule' option does
 not define an input parameter for the 'USER TO RUN TASK' field.  
  
 The RIS must guarantee that the user identified discontinuing orders in the
 RAD/NUC MED ORDERS (#75.1) file is the same user recorded as discontinuing
 that same order in the Computerized Patient Record System (CPRS) ORDER (#100)
 file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RA*5.0*135
KEYWORDS: OPTION SCHEDULING
KEYWORDS: XU RA
KEYWORDS: RA IAs
COMPONENT/ENTRY POINT: EN2
 COMPONENT DESCRIPTION:   This entry point will schedule a VistA RIS option to
 run at a defined date/time tying this process to a specific owner.  
VARIABLES: RAWHEN                       TYPE: Input
 VARIABLES DESCRIPTION:   RAWHEN is used to define the date and time this
 option is to run.  (required) 
VARIABLES: RAUSER                       TYPE: Input
 VARIABLES DESCRIPTION:   RAUSER is used to define who the user is that
 schedules this option to run. (required) 
VARIABLES: RADEV                        TYPE: Input
 VARIABLES DESCRIPTION:   RADEV is used to define the name of the device on
 which this option will be queued to print by TaskMan. (optional) 
VARIABLES: RAFREQ                       TYPE: Input
 VARIABLES DESCRIPTION:   RAFREQ is used to define the frequency with which
 this option will be automatically rescheduled to run.  (optional) 
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   The RIS software will create an entry in the OPTION
 SCHEDULING file based on a specific radiology option. This option will be
 scheduled and run once. The RIS software will then file the date and time the
 option is to run and the user responsible to run scheduled task.  
  
 All transactions involving the OPTION SCHEDULING file will use VA FileMan 
 supported application program interfaces.  
  DATE ACTIVATED: DEC 11, 2017

NUMBER: 6827                            IA #: 6827
  DATE CREATED: OCT 23, 2017            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ SAVE ADMIN
  REMOTE PROCEDURE: YTQ SAVE ADMIN
 GENERAL DESCRIPTION:   This RPC is used to add or edit a Mental Health
 Administration File entry.  The subscripted YS array is passed to the RPC
 containing all of the values needed to create or update the entry.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Mental Health
KEYWORDS: MHPRO
KEYWORDS: YTQ
SUBSCRIBING PACKAGE: MOBILE MHPRO
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This is approved as long as VIA restricts this RPC
 access to MH Checkup only, through the application proxy.  
  DATE ACTIVATED: NOV 08, 2017

NUMBER: 6828                            IA #: 6828
  FILE NUMBER: 691.5                    GLOBAL ROOT: MCAR(691.5
  DATE CREATED: OCT 30, 2017            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ACCESS TO READ EKG FILE
  ID: MCAR(691.5
GLOBAL REFERENCE: MCAR(691.5,D0,0) 
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: MCAR(691.5,D0,.2)
FIELD NUMBER: .03                       FIELD NAME: SUMMARY
  LOCATION: 2;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: MCAR(691.5,D0,9,D1,0)
FIELD NUMBER: 20                        FIELD NAME: AUTO-INSTRUMENT DIAGNOSIS
  LOCATION: 9;0                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Users need the ability to access the patient EKG
 Date/Time, Summary and AUTO Instrument Diagnosis using a Health Summary
 Object.  Routines will use the "C" cross reference to obtain data for a
 patient using a Fileman call.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EKG
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: APR 12, 2018

NUMBER: 6829                            IA #: 6829
  FILE NUMBER: 667.3                    GLOBAL ROOT: RMPR(667.3,
  DATE CREATED: NOV 13, 2017            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: V.O.R. TRANSACTION FILE ACCESS
  ID: RMPR(667.3,
GLOBAL REFERENCE: RMPR(667.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE PROCESSED
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: VEHICLE ID#
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ITEM
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: COST
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: AMIS CODE
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: SERIAL NUMBER
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.5                       FIELD NAME: QTY
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8                         FIELD NAME: TYPE OF TRANSACTION
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: PATIENT CATEGORY
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SPECIAL CATEGORY
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 11                        FIELD NAME: SOURCE
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: RETURN DATE
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(667.3,D0,1)
FIELD NUMBER: 5                         FIELD NAME: DESCRIPTION
  LOCATION: 1;0                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(667.3,D0,2)
FIELD NUMBER: 12                        FIELD NAME: STATION NAME
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13                        FIELD NAME: USER
  LOCATION: 2;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(667.3,D0,3)
FIELD NUMBER: 7                         FIELD NAME: AMIS
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: RMPR(667.3,'B'
 GLOBAL DESCRIPTION:   File 667.3 'B' cross reference  Used to look up by DATE
 PROCESSED 
GLOBAL REFERENCE: RMPR(667.3,'AD'
 GLOBAL DESCRIPTION:   File 667.3 'AD' cross reference  Used to look up by ITEM 
GLOBAL REFERENCE: RMPR(667.3,'C'
 GLOBAL DESCRIPTION:   File 667.3 'C' cross reference  Used to look up by
 VEHICLE ID# 
 GENERAL DESCRIPTION:   The ADVANCED PROSTHETICS ACQUISITION TOOL requests
 permission to use a FileMan API to edit a returned/condemned item in the
 V.O.R. TRANSACTION (#667.3) FILE.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: SEP 10, 2019

NUMBER: 6830                            IA #: 6830
  FILE NUMBER: 440.6                    GLOBAL ROOT: PRCH(440.6,
  DATE CREATED: NOV 13, 2017            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PURCHASE CARD RECONCILE FILE ACCESS
  ID: PRCH(440.6,
GLOBAL REFERENCE: PRCH(440.6,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ORACLE DOCUMENT ID
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: BATCH NUMBER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: LINE NUMBER
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: CREDIT CARD NUMBER
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: BANK'S VENDOR ID
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: STATEMENT DATE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: TRANSACTION DATE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: STATION NUMBER
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: PURCHASE DATE
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: TXN REFERENCE #
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: BBFY
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: EBFY
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: ACCOUNTING PERIOD
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: AMOUNT
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: FISCAL YEAR
  LOCATION: 0;15                        ACCESS: Read w/Fileman
FIELD NUMBER: 15                        FIELD NAME: STATUS
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16                        FIELD NAME: CARD HOLDER
  LOCATION: 0;17                        ACCESS: Read w/Fileman
FIELD NUMBER: 17                        FIELD NAME: ET CODE SHEET
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 18                        FIELD NAME: COMMITTED AMOUNT
  LOCATION: 0;19                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 19                        FIELD NAME: OLD PO STATUS CODE
  LOCATION: 0;20                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20                        FIELD NAME: VENDOR PURCHASE ORDER
  LOCATION: 0;21                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCH(440.6,D0,1)
FIELD NUMBER: 41                        FIELD NAME: PURCHASE ORDER
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 42                        FIELD NAME: RECEIVING REQUIRED
  LOCATION: 1;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 43                        FIELD NAME: COMPLETE ORDER RECEIVED
  LOCATION: 1;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 44                        FIELD NAME: FINAL CHARGE
  LOCATION: 1;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 45                        FIELD NAME: RECONCILE USER
  LOCATION: 1;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 46                        FIELD NAME: RECONCILE DATE
  LOCATION: 1;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 47                        FIELD NAME: CHARGE RECEIVING DATE
  LOCATION: 1;7                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCH(440.6,D0,5)
FIELD NUMBER: 21                        FIELD NAME: FUND CODE
  LOCATION: 5;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 22                        FIELD NAME: ACC CODE
  LOCATION: 5;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: COST CENTER
  LOCATION: 5;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 24                        FIELD NAME: BOC
  LOCATION: 5;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 25                        FIELD NAME: APPROVING OFFICE
  LOCATION: 5;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 26                        FIELD NAME: APPROVAL DATE
  LOCATION: 5;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 27                        FIELD NAME: APPROVING OFFICIAL
  LOCATION: 5;7                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRCH(440.6,D0,6)
FIELD NUMBER: 31                        FIELD NAME: MERCHANT NAME
  LOCATION: 6;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 32                        FIELD NAME: MERCHANT ADDRESS 1
  LOCATION: 6;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 33                        FIELD NAME: MERCHANT ADDRESS 2
  LOCATION: 6;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 34                        FIELD NAME: MERCHANT CITY
  LOCATION: 6;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 35                        FIELD NAME: MERCHANT STATE
  LOCATION: 6;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 36                        FIELD NAME: MERCHANT ZIP
  LOCATION: 6;6                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCH(440.6,'ST'
 GLOBAL DESCRIPTION:   "ST" cross reference    Used for look up by combination 
                         of status and card holder 
GLOBAL REFERENCE: PRCH(440.6,'C'
 GLOBAL DESCRIPTION:   File 440.6 'C' cross reference  Used to look up by
 VENDOR 
                                 PURCHASE ORDER 
GLOBAL REFERENCE: PRCH(440.6,'PO'
 GLOBAL DESCRIPTION:   File 440.6 'PO' cross reference  Used to look up by
 reconciled 
                                  PURCHASE ORDER 
 GENERAL DESCRIPTION:   The ADVANCED PROSTHETICS ACQUISITION TOOL requests
 permission to use FileMan APIs to read from and write to the PURCHASE ORDER
 RECONCILE file (#440.6).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 13, 2019

NUMBER: 6831                            IA #: 6831
  DATE CREATED: NOV 13, 2017            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGAPI                        NAME: CPT AND DIAGNOSIS UPDATE
  ID: DGAPI
 GENERAL DESCRIPTION:   CPT AND DIAGNOSIS UPDATE is an API that contains
 modules that update CPT codes and diagnosis codes.  ERR module allows printing
 of error message based on flag parameter for DATA2PTF.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
KEYWORDS: INTEGRATION FRAMEWORK
KEYWORDS: DATA BRIDGE
COMPONENT/ENTRY POINT: CPT
 COMPONENT DESCRIPTION:   CPT module enables filing of CPT information in
 ^DGCPT file.  
COMPONENT/ENTRY POINT: DIAG
 COMPONENT DESCRIPTION:   DIAG module enables filing of diagnosis information
 in ^DGCPT file.  
COMPONENT/ENTRY POINT: ERR
 COMPONENT DESCRIPTION:   ERR module displays or prints error messages based on
 flag parameter for DATA2PTF.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   FILE contains file number.  
VARIABLES: MESS                         TYPE: Input
 VARIABLES DESCRIPTION:   MESS contains message to be printed.  

NUMBER: 6832                            IA #: 6832
  DATE CREATED: NOV 13, 2017            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  ROUTINE: HLCSUTL2                     NAME: GET NUMBER OF FILERS
  ID: HLCSUTL2
 GENERAL DESCRIPTION:   GET NUMBER OF FILERS will return the number of filers
 that are currently running.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
KEYWORDS: INTEGRATION FRAMEWORK
KEYWORDS: DATA BRIDGE
COMPONENT/ENTRY POINT: CNTFLR
 COMPONENT DESCRIPTION:   CNTFLR will return a number of incoming/outgoing
 filers that are currently running.  This will typically be the number of
 entries in the INCOMING FILER TASK NUMBER or OUTGOING FILER TASK NUMBER
 multiples of the HL COMMUNICATION SERVER PARAMETER(#869.3) FILE.  
VARIABLES: FLRTYPE                      TYPE: Input
 VARIABLES DESCRIPTION:   IN=Incoming, OUT=Outgoing 
VARIABLES: COUNT                        TYPE: Output
 VARIABLES DESCRIPTION:   Number of incoming/outgoing filers 

NUMBER: 6833                            IA #: 6833
  DATE CREATED: NOV 13, 2017            CUSTODIAL PACKAGE: DRG GROUPER
  USAGE: Private                        TYPE: Routine
  ROUTINE: ICDSUPT
  NAME: ICD EFFECTIVE DATE AND STATUS FOR CODE/MODIFIER
  ID: ICDSUPT
 GENERAL DESCRIPTION:   ICD EFFECTIVE DATE AND STATUS FOR CODE/MODIFIER will
 return an effective date and status for code/modifier.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
KEYWORDS: INTEGRATION FRAMEWORK
KEYWORDS: DATA BRIDGE
COMPONENT/ENTRY POINT: EFF
 COMPONENT DESCRIPTION:   ICD EFFECTIVE DATE AND STATUS FOR CODE/MODIFIER will
 return an effective date and status for code/modifier.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   80 = ICD DX, 80.1 = ICD O/P 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   ICD IEN 
VARIABLES: CDT                          TYPE: Input
 VARIABLES DESCRIPTION:   DATE TO CHECK 

NUMBER: 6834                            IA #: 6834
  DATE CREATED: NOV 13, 2017
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  ROUTINE: PXKMAIN                      NAME: EXECUTE PCE'S EVENT
  ID: PXKMAIN
 GENERAL DESCRIPTION:   EXECUTE PCE'S EVENT is an integration agreement that
 lets the caller execute PCE'S event.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
KEYWORDS: INTEGRATION FRAMEWORK
KEYWORDS: DATA BRIDGE
COMPONENT/ENTRY POINT: EVENT

NUMBER: 6835                            IA #: 6835
  DATE CREATED: NOV 13, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SRHLU                        NAME: CONVERT INTERNAL NAME TO HL NAME
  ID: SRHLU
 GENERAL DESCRIPTION:   CONVERT INTERNAL NAME TO HL NAME is an integration
 agreement that allows the caller to convert internal entry number into an HL7
 CN data type.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
KEYWORDS: INTEGRATION FRAMEWORK
KEYWORDS: DATA BRIDGE
COMPONENT/ENTRY POINT: HNAME
 COMPONENT DESCRIPTION:   CONVERT INTERNAL NAME TO HL NAME is an integration
 agreement that allows the caller to convert internal entry number into an HL7
 CN data type.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN OF HL NAME 

NUMBER: 6836                            IA #: 6836
  DATE CREATED: NOV 13, 2017            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SROP1                        NAME: PRINT SURGERY CASE STATUS
  ID: SROP1
 GENERAL DESCRIPTION:   PRINT SURGERY CASE STATUS allows the caller to print
 surgery cases.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
KEYWORDS: INTEGRATION FRAMEWORK
KEYWORDS: DATA BRIDGE
COMPONENT/ENTRY POINT: STATUS
 COMPONENT DESCRIPTION:   PRINT SURGERY CASE STATUS allows the caller to print
 surgery cases.  
VARIABLES: SROP                         TYPE: Input
 VARIABLES DESCRIPTION:   SURGERY file IEN 

NUMBER: 6837                            IA #: 6837
  FILE NUMBER: 757.02                   GLOBAL ROOT: LEX(757.02,
  DATE CREATED: NOV 13, 2017            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Private                        TYPE: File
  NAME: LEXICON CODES                   ID: LEX(757.02,
GLOBAL REFERENCE: LEX(757.02,D0,0)
FIELD NUMBER: .01                       FIELD NAME: EXPRESSION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: CODE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: CLASSIFICATION SOURCE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: MAJOR CONCEPT
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PREFERENCE FLAG
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: DEACTIVATION FLAG
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: PRIMARY FLAG
  LOCATION: 0;7                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LEX(757.02,D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ACTIVATION EFFECTIVE DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ACTIVATION STATUS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LEX(757.02,D0,6)
FIELD NUMBER: 13                        FIELD NAME: LEGACY CODE
  LOCATION: 6;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   LEXICON CODES contain codes, their classification
 sources (such as ICD), and some flags.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
KEYWORDS: INTEGRATION FRAMEWORK
KEYWORDS: DATA BRIDGE

NUMBER: 6838                            IA #: 6838
  FILE NUMBER: 757.2                    GLOBAL ROOT: LEXT(757.2,
  DATE CREATED: NOV 13, 2017            CUSTODIAL PACKAGE: LEXICON UTILITY
  USAGE: Private                        TYPE: File
  NAME: SUBSET DEFINITIONS              ID: LEXT(757.2,
GLOBAL REFERENCE: LEXT(757.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: SHORT TITLE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LEXT(757.2,D0,1)
FIELD NUMBER: 2                         FIELD NAME: GLOBAL REFERENCE
  LOCATION: 1;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LEXT(757.2,D0,2)
FIELD NUMBER: 3                         FIELD NAME: HELP ROUTINE ENTRY POINT
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: HELP ROUTINE
  LOCATION: 2;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LEXT(757.2,D0,3)
FIELD NUMBER: 5                         FIELD NAME: DISPLAY ROUTINE ENTRY POINT
  LOCATION: 3;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: DISPLAY ROUTINE
  LOCATION: 3;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LEXT(757.2,D0,4)
FIELD NUMBER: 7                         FIELD NAME: DISPLAY CODES
  LOCATION: 4;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LEXT(757.2,D0,5)
FIELD NUMBER: 8                         FIELD NAME: APPLICATION MNEMONIC
  LOCATION: 5;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: APPLICATION INDEX
  LOCATION: 5;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: APPLICATION USER DEFAULTS
  LOCATION: 5;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: APPLICATION FILE NUMBER
  LOCATION: 5;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: APPLICATION NAMESPACE
  LOCATION: 5;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 15                        FIELD NAME: UNRESOLVED NARRATIVES
  LOCATION: 5;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 16                        FIELD NAME: OVERRIDE USER DEFAULTS
  LOCATION: 5;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 17                        FIELD NAME: SHORTCUT CONTEXT
  LOCATION: 5;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 18                        FIELD NAME: USER MODIFIERS
  LOCATION: 5;9                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LEXT(757.2,D0,6)
FIELD NUMBER: 10                        FIELD NAME: APPLICATION FILTER
  LOCATION: 6;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LEXT(757.2,D0,7)
FIELD NUMBER: 11                        FIELD NAME: APPLICATION DISPLAY CODES
  LOCATION: 7;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LEXT(757.2,D0,100,0)
FIELD NUMBER: 100                       FIELD NAME: DESCRIPTION
  ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   SUBSET DEFINITIONS contains various terminologies and
 codes related to certain areas defined in other LEX globals.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DSIHL
KEYWORDS: INTEGRATION FRAMEWORK
KEYWORDS: DATA BRIDGE

NUMBER: 6839                            IA #: 6839
  DATE CREATED: NOV 15, 2017            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: PXRMRPCG CANCEL REMOTE PROCEDURE
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call the PXRMRPCG CANCEL remote procedure call.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: CANCEL REMINDER DIALOG
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 6840                            IA #: 6840
  DATE CREATED: NOV 15, 2017            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: PXRMRPCG GENFUPD                REMOTE PROCEDURE: PXRMRPCG GENFUPD
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call the PXRMRPCG GENFUPD remote procedure call.  
  
 Subscribers of this agreement should also subscribe to agreement #6841 
 PXRMRPCG GENFVALD REMOTE PROCEDURE. The PXRMRPCG GENFVALD remote procedure
 should be called before calling the PXRMRPCG GENFUPD remote procedure to
 ensure that data passed in to the latter call is valid.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: REMINDER DIALOG
KEYWORDS: GENERAL FINDINGS UPDATE
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 6841                            IA #: 6841
  DATE CREATED: NOV 15, 2017            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: PXRMRPCG GENFVALD               REMOTE PROCEDURE: PXRMRPCG GENFVALD
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call the PXRMRPCG GENFVALD remote procedure call.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: VALIDATE GENERAL FINDINGS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 6842                            IA #: 6842
  DATE CREATED: NOV 15, 2017            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: PXRMRPCG VIEW REMOTE PROCEDURE
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call the PXRMRPCG VIEW remote procedure call.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: REMINDER DIALOG VIEW TEXT
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 6843                            IA #: 6843
  DATE CREATED: NOV 15, 2017            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: WVRPCOR COVER
  REMOTE PROCEDURE: WVRPCOR COVER
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call the WVRPCOR COVER remote procedure.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COVER SHEET PANEL CONTENT
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 20, 2017

NUMBER: 6844                            IA #: 6844
  DATE CREATED: NOV 15, 2017            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: WVRPCOR DETAIL
  REMOTE PROCEDURE: WVRPCOR DETAIL
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call the WVRPCOR DETAIL remote procedure.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COVER SHEET DETAIL DIALOG
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 20, 2017

NUMBER: 6845                            IA #: 6845
  DATE CREATED: NOV 15, 2017            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: WVRPCOR EIE
  REMOTE PROCEDURE: WVRPCOR EIE
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call the WVRPCOR EIE remote procedure.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MARK RECORD ENTERED IN ERROR
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 20, 2017

NUMBER: 6846                            IA #: 6846
  DATE CREATED: NOV 15, 2017            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: WVRPCOR POSTREP
  REMOTE PROCEDURE: WVRPCOR POSTREP
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call the WVRPCOR POSTREP remote procedure.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: POSTINGS POP-UP DIALOG
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 20, 2017

NUMBER: 6847                            IA #: 6847
  DATE CREATED: NOV 15, 2017            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: WVRPCOR REASONS
  REMOTE PROCEDURE: WVRPCOR REASONS
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call the WVRPCOR REASONS remote procedure.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: REASONS TO MARK RECORD EIE
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 20, 2017

NUMBER: 6848                            IA #: 6848
  DATE CREATED: NOV 15, 2017            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: WVRPCOR SAVEDATA
  REMOTE PROCEDURE: WVRPCOR SAVEDATA
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call the WVRPCOR SAVEDATA remote procedure.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COVER SHEET SAVE DATA
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 20, 2017

NUMBER: 6849                            IA #: 6849
  DATE CREATED: NOV 15, 2017            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: WVRPCOR SITES
  REMOTE PROCEDURE: WVRPCOR SITES
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call the WVRPCOR SITES remote procedure.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COVER SHEET WEB SITES
KEYWORDS: POP-UP MENU
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 20, 2017

NUMBER: 6850                            IA #: 6850
  DATE CREATED: NOV 24, 2017            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: PTF ICD DIAGNOSIS NOTIFICATION
 GENERAL DESCRIPTION:   The DG PTF ICD DIAGNOSIS NOTIFIER protocol notifies
 subscribers when an International Classification of Diseases (ICD) diagnosis
 code is added, modified or removed for entries within the PTF file (#45).  
  
 The following data is available to subscribers: 
  
 ^TMP("DG PTF ICD NOTIFIER",$J,"DFN")=DFN 
   DFN: internal entry number of the patient in the PATIENT file (#2).  
  
 ^TMP("DG PTF ICD NOTIFIER",$J,TYPE,"IENS")=IENS 
  TYPE: The activity type; possible values are "DISCHARGE", "MOVEMENT", 
        "SERVICE" and "SERVICE46". "DISCHARGE" codes are from the 
        PRINCIPAL DIAGNOSIS field and the SECONDARY DIAGNOSIS series of 
        fields in the PTF file (#45). "MOVEMENT" codes are from the ICD 
        series of fields in the 501 sub-file (#45.02) in the PTF file 
        (#45). "SERVICE" code is from the PRIMARY DIAGNOSIS field in the 
        CPT RECORD DATE/TIME sub-file (#45.06) in the PTF file (#45).  
        "SERVICE46" codes are from the PRIMARY DIAGNOSIS field and the 
        SECONDARY DIAGNOSIS series of fields in the INPATIENT CPT CODE file 
        (#46).  
   IENS: The internal entry number string identifying the record in which 
         the associated codes are stored.  
  
 ^TMP("DG PTF ICD NOTIFIER",$J,TYPE,FIELD,"OLD")=ICDP 
  This is how the field appeared in the file before the change was made.  
  FIELD: This is an abbreviation denoting which field the code came from.  
         The following table should assist in determining which field a 
         code came from: 
         TYPE      FIELD     Field Name 
         -----------------------------------------------------
         DISCHARGE PDX       PRINCIPAL DIAGNOSIS 
         DISCHARGE SDXnn     SECONDARY DIAGNOSIS nn (nn is a whole number) 
         DISCHARGE PDX-P1986 PRINCIPAL DIAGNOSIS pre 1986 
         MOVEMENT  DXnn      ICD nn (nn is a whole number) 
         SERVICE   PDX       PRIMARY DIAGNOSIS 
         SERVICE46 PDX       PRIMARY DIAGNOSIS 
         SERVICE46 SDX0n     SECONDARY DIAGNOSIS n (n is a whole number) 
  ICDP: Internal entry number of the diagnosis code in the ICD DIAGNOSIS 
        file (#80).  
  
 ^TMP("DG PTF ICD NOTIFIER",$J,TYPE,FIELD,"NEW")=ICDP 
  This is how the field appeared in the file after the change was made.  
  
 When a code is added, the "OLD" value will be blank and the "NEW" value will
 not be. When a code is deleted, the "OLD" value will not be blank and the
 "NEW" value will be. When a code is changed, both the "OLD" and "NEW" values
 will not be blank.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DG PTF ICD DIAGNOSIS EVENT
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Attached the PXRM PATIENT PTF DATA CHANGE protocol.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 9/3/21, effective with VPR*1*26. VPR added a
 listener protocol, VPR PTF EVENTS, to the DG PTF ICD DIAGNOSIS NOTIFIER
 protocol event.  
  DATE ACTIVATED: JUN 19, 2018

NUMBER: 6851                            IA #: 6851
  DATE CREATED: DEC 08, 2017            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RCDPUREC
  NAME: GET FMS DOCUMENT STATUS FOR AR BATCH PAYMENT
  ID: RCDPUREC
 GENERAL DESCRIPTION:   The subroutine FMSSTAT^RCDPUREC is used to get the
 status and FMS document given the internal entry number from the AR BATCH
 PAYMENT FILE [#344].  There is a need to access this call from within the
 INTEGRATED BILLING (IB) package to provide the FMS DOCUMENT number and STATUS
 for information on IB reports and worklists.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FMSSTATUS
KEYWORDS: FMS STATUS
KEYWORDS: RCDPUREC
KEYWORDS: 344
KEYWORDS: RCY(344
COMPONENT/ENTRY POINT: $$FMSSTAT(ARBPIEN)
 COMPONENT DESCRIPTION:   This component takes an internal entry number from
 the AR BATCH PAYMENT file [#344] and returns an '^' delimited string
 containing the FMS DOCUMENT number and STATUS.  
VARIABLES: ARBPIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of an AR BATCH PAYMENT
 [#344].  
VARIABLES: RETURN                       TYPE: Output
 VARIABLES DESCRIPTION:   FMS_DOCUMENT_NUMBER^FMS_DOCUMENT_STATUS 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: FEB 08, 2018

NUMBER: 6852                            IA #: 6852
  DATE CREATED: DEC 12, 2017            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ENEQNX3                      NAME: UPLOADED EQUIPMENT INVENTORY 
  ID: ENEQNX3
 GENERAL DESCRIPTION:   This integration agreement allows ABOVE PAR to call
 ENGINEERING routine ENEQNX3 to verify the ITEM is in the database and to
 process a PM item.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: NOLBL
 COMPONENT DESCRIPTION:   NOLBL^ENEQNX3 is called to verify the ITEM is in the
 database.  If matched, then the process will update ENGINEERING EQUIPMENT INV.
 (#6914) file fields PHYSICAL INVENTORY DATE (#23) and LOCATION (#24).  
VARIABLES: ENCTID                       TYPE: Input
 VARIABLES DESCRIPTION:   BARCODE IEN (#446.4) 
VARIABLES: ENCTTI                       TYPE: Input
 VARIABLES DESCRIPTION:   DATE/TIME (#446.42) that data was uploaded from a
 barcode reader and stored in this file 
VARIABLES: ENX                          TYPE: Input
 VARIABLES DESCRIPTION:   Barcode Data (#446.2,1) 
COMPONENT/ENTRY POINT: PMN
 COMPONENT DESCRIPTION:   PMN^ENEQNX3 is called to process a PM item.  The
 process will update BARCODE DATA (#446.4) BARCODE PROGRAM (#1) as "*" attached
 to input variable ENEQ.  
VARIABLES: ENCTID                       TYPE: Input
 VARIABLES DESCRIPTION:   BARCODE IEN (#446.4) 
VARIABLES: ENCTTI                       TYPE: Input
 VARIABLES DESCRIPTION:   DATE/TIME (446.42) - data was uploaded from a barcode
 reader and stored in this file 
VARIABLES: ENX                          TYPE: Input
 VARIABLES DESCRIPTION:   BARCODE DATA (446.421) 
VARIABLES: ENEQ                         TYPE: Input
 VARIABLES DESCRIPTION:   Barcode record identifier 
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6853                            IA #: 6853
  DATE CREATED: DEC 13, 2017            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  ROUTINE: PRCVITMU                     NAME: ITEM - VERIFY ITEM MASTER NUMBER
  ID: PRCVITMU
 GENERAL DESCRIPTION:   This integration agreement allows ABOVE PAR to call
 IFCAP routine PRCVITMU to verify the ITEM MASTER item number.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: TRANS
 COMPONENT DESCRIPTION:   The call to TRANS will verify the IEN input as a
 valid ITEM # for the ITEM MASTER (#441) file or will determine a new IEN if
 the input is passed as 'NEW'.  
VARIABLES: X                            TYPE: Both
 VARIABLES DESCRIPTION:   Input: An ITEM MASTER (#441) file IEN or 'NEW' 
 Output: The ITEM MASTER (#441) file IEN as determined or 
         UNDEFINED if no value found 
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6854                            IA #: 6854
  DATE CREATED: DEC 13, 2017            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  ROUTINE: PRCVNDR
  NAME: VENDOR - CHECK ONE VENDOR'S CHECKSUM
  ID: PRCVNDR
 GENERAL DESCRIPTION:   This integration agreement allows ABOVE PAR to call
 ONECHK routine PRCVNDR to verify the vendor record and, if necessary, send
 updated data to DynaMed.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: ONECHK
 COMPONENT DESCRIPTION:   Send vendor update information to DynaMed - checksum
 to one vendor only.  
VARIABLES: PRCVN                        TYPE: Input
 VARIABLES DESCRIPTION:   VENDOR (#440) file IEN 
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6855                            IA #: 6855
  FILE NUMBER: 6910.1                   GLOBAL ROOT: DIC(6910.1,
  DATE CREATED: DEC 13, 2017            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ENGINEERING COMPUTER PORT FILE ACCESS
  ID: DIC(6910.1,
GLOBAL REFERENCE: DIC(6910.1,D0,1)
FIELD NUMBER: 3                         FIELD NAME: BAR CODE EQUIPMENT FORMAT
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DIC(6910.1,D0,2)
FIELD NUMBER: 4                         FIELD NAME: BAR CODE LOCATION FORMAT
  LOCATION: 2;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DIC(6910.1,D0,3)
FIELD NUMBER: 5                         FIELD NAME: BAR CODE EQUIPMENT DATA
  LOCATION: 3;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DIC(6910.1,D0,4)
FIELD NUMBER: 6                         FIELD NAME: BAR CODE LOCATION DATA
  LOCATION: 4;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DIC(6910.1,'B',STNM
 GLOBAL DESCRIPTION:   Cross Reference by Station Name, field STATION NAME
 (#.01) 
 GENERAL DESCRIPTION:   The ENGINEERING COMPUTER PORT FILE #6910.1 is read
 during: 
    - Print Location label setup.  The location format and location data  
      will be used if the port has a custom setup.  
    - Print Equipment label setup.  The equipment format and equipment 
      data will be used if the port has a custom setup.  
  
 Above PAR Ad-Hoc Reporting includes the ENGINEERING COMPUTER PORT FILE
 #6910.1. Ad-Hoc functionality provides the ability to select fields from the
 file for display on user-defined reports.  Ad-Hoc offers only FileMan read
 access and only if the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 06, 2022

NUMBER: 6856                            IA #: 6856
  FILE NUMBER: 422.2                    GLOBAL ROOT: PRCF(422.2,
  DATE CREATED: DEC 13, 2017            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  NAME: COUNTER FILE ACCESS             ID: PRCF(422.2,
GLOBAL REFERENCE: PRCF(422.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: COUNTER
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRFC(422.2,'B',NAME,D0)
 GLOBAL DESCRIPTION:   'B' index used to lookup by Name.  
 GENERAL DESCRIPTION:   Above PAR requests permission to update the COUNTER
 (#422.2) file when sending a FMS VENDOR REQUEST to Austin.  
  
 Above PAR will create a COUNTER entry to support the FMS VENDOR REQUEST if the
 COUNTER NAME (.01) is not defined.  
  
 Above PAR will increment the COUNTER field COUNTER (1).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6857                            IA #: 6857
  FILE NUMBER: 447.1                    GLOBAL ROOT: PRCP(447.1,
  DATE CREATED: DEC 13, 2017            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: AUTOMATED SUPPLY STATION PROCESSING QUEUE FILE ACCESS
  ID: PRCP(447.1,
GLOBAL REFERENCE: PRCP(447.1,D0,0)
FIELD NUMBER: 1                         FIELD NAME: STATION NUMBER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: SECONDARY INVENTORY POINT
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(447.1,'C'
 GLOBAL DESCRIPTION:   "C" cross reference - used to check OUTSTANDING
 TRANSACTIONS BY AFFECTED INVENTORY POINT to determine if an Alert record has
 been produced 
 GENERAL DESCRIPTION:   ABOVE PAR requests permission to check the AUTOMATED
 SUPPLY STATION PROCESSING QUEUE (#447.1) file's STATION NUMBER (#1) and
 SECONDARY INVENTORY POINT (#2) fields.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: NOV 21, 2018

NUMBER: 6858                            IA #: 6858
  FILE NUMBER: 445.1                    GLOBAL ROOT: PRCP(445.1,
  DATE CREATED: DEC 13, 2017            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INVENTORY BALANCES FILE ACCESS
  ID: PRCP(445.1,
GLOBAL REFERENCE: PRCP(445.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: INVENTORY POINT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(445.1,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: INVENTORY ITEM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCP(445.1,D0,1,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: BEGINNING MONTH-YEAR BALANCE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: QUANTITY ON-HAND
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: QUANTITY NON-ISSUABLE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: QUANTITY DUE-IN
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: QUANTITY DUE-OUT
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: AVERAGE UNIT COST
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: LAST RECEIPT UNIT COST
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: TOTAL INVENTORY VALUE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The INVENTORY BALANCE (#445.1) file stores the
 beginning monthly balances for the items stored in the inventory points,
 GENERIC INVENTORY (#445) file.  ABOVE PAR checks determines whether the
 inventory item balance is available and will create the balance record if the
 item has no balance record.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: DEC 07, 2018

NUMBER: 6859                            IA #: 6859
  FILE NUMBER: 6915.5                   GLOBAL ROOT: ENG(6915.5,
  DATE CREATED: DEC 13, 2017            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FD DOCUMENT LOG FILE ACCESS
  ID: ENG(6915.5,
GLOBAL REFERENCE: ENG(6915.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: EQUIPMENT RECORD
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ENG(6915.5,'B'
 GLOBAL DESCRIPTION:   Cross Reference field EQUIPMENT RECORD (#.01) 
 GENERAL DESCRIPTION:   The FD DOCUMENT LOG (#6915.5) file is referenced by
 RPCs DSIYUTL4 FAPCHK CHK FOR FAP and DSIYUTL1 EQUPDT UPDATE EQUIP to determine
 if an FP document exists.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: SEP 12, 2022

NUMBER: 6860                            IA #: 6860
  FILE NUMBER: 2006.1                   GLOBAL ROOT: MAG(2006.1,
  DATE CREATED: DEC 19, 2017            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  NAME: MAG IHE SWITCH FOR HL7 ADT MESSAGES
  ID: MAG(2006.1,
GLOBAL REFERENCE: MAG(2006.1,IEN,'IHE')
FIELD NUMBER: 3.01
  FIELD NAME: IHE PACS HL7 INTERFACE ACTIVE
  LOCATION: IHE;1                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field contains a flag that indicates whether HL7 ADT
 messages should  be sent using the IHE-based interface developed in Imaging
 Patch  MAG*3.0*49.  
 GLOBAL DESCRIPTION:   The Imaging Site Parameter file contains those variables
 which are site specific, and which are necessary for the Imaging Software to
 perform properly.  
GLOBAL REFERENCE: MAG(2006.1,'B',
FIELD NUMBER: .01                       FIELD NAME: INSTITUTION NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field identifies the INSTITUTION record(s) stored in
 the IMAGING SITE PARAMETERS file.  
 GENERAL DESCRIPTION:   Radiology requests access to the IMAGING SITE
 PARAMETERS file (#2006.1), field IHE PACS HL7 INTERFACE ACTIVE (#3.01) to
 determine if the broadcast of ADT messages are permitted at a facility.  ADT
 messages can be broadcast by running the new RA ADT menu option that will be
 available with patch RA*5.0*137.  
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
KEYWORDS: RA*5.0*137
KEYWORDS: MAG*3.0*183
KEYWORDS: MAG(2006.1
KEYWORDS: HL7 ADT BROADCASTS
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Imaging patch MAG*3.0*183 is required to be installed.  
  DATE ACTIVATED: DEC 21, 2017

NUMBER: 6861                            IA #: 6861
  DATE CREATED: JAN 12, 2018
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA6861
  STATUS: Pending

NUMBER: 6862                            IA #: 6862
  DATE CREATED: JAN 12, 2018
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA6862
  STATUS: Pending

NUMBER: 6863                            IA #: 6863
  DATE CREATED: JAN 16, 2018            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOPMP0
  NAME: PSO Medication Profile          ID: PSOPMP0
 GENERAL DESCRIPTION:   Allow ECME routine to access Medication Profile
 information from Outpatient Pharmacy.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MEDPRO
 COMPONENT DESCRIPTION:   Allow ECME routine to access Medication Profile
 information from Outpatient Pharmacy. The MEDPRO procedure does not have any
 output variables, per se, but instead builds display lines in the ^TMP global 
 which are then merged by the ECME routine into another section of the ^TMP
 global to be used by ListMan.  
  
 This procedure populates the ^TMP("PSOPMP0",$J) global with the medication
 profile of a given patient. Each line is free text. There can be up to 9
 sections: REFILL TOO SOON/DUR REJECTS, OTHER REJECTS PENDING RESOLUTION,
 CURRENT ORDERS, PENDING, NON-VA MEDS, ACTIVE, DISCONTINUED, HOLD and
 NON-VERIFIED.  
  
 Each section will have one header line and one or more lines of prescriptions.
 Each prescription line will contain the following values: Prescription#, Drug
 Name, Quantity, Status, Issue Date, Fill Date, Refills Remaining and Days'
 Supply.  
VARIABLES: RXIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Prescription IEN, pointer to file# 52.  
VARIABLES: FILL                         TYPE: Input
 VARIABLES DESCRIPTION:   Fill number (0 for original fill).  
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
  DATE ACTIVATED: FEB 05, 2018

NUMBER: 6864                            IA #: 6864
  FILE NUMBER: 200                      GLOBAL ROOT: DD(200
  DATE CREATED: JAN 17, 2018            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ ACCESS TO DD(200
  ID: DD(200
 GENERAL DESCRIPTION:   This is a one-time agreement via patch XU*8.0*687 to
 clean up a cross reference on two fields, MAIL CODE (#28) and SERVICE/SECTION
 (#29) of the NEW PERSON File (#200).  This agreement will cover the removal of
 the E cross reference on Field 28.  The code to remove the cross reference is: 
  
  N XUHIT,XUOUT,XUERR,XUXREF 
  S (XUHIT,XUXREF)=0 
  F  S XUXREF=$O(^DD(200,28,1,XUXREF)) Q:('+XUXREF)!(XUHIT)  D 
  . I $P($G(^DD(200,28,1,XUXREF,0)),U,2)="E" D 
  .. S XUHIT=1 
  .. D DELIX^DDMOD(200,28,XUXREF,"K","XUOUT","XUERR") 
  .. ;
  .. ; No error, xRef deleted 
  .. I '$D(XUERR) D MES^XPDUTL("The E cross reference was deleted.")  Q 
  .. ;
  .. ; Error encountered, xRef not deleted.  
  .. D MES^XPDUTL("ERROR encountered deleting the E cross reference.") 
  ;
  D:'XUHIT MES^XPDUTL("The E cross reference was not found.") 
  ;
  Q 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: KERNEL
  DATE ACTIVATED: FEB 16, 2018

NUMBER: 6865                            IA #: 6865
  FILE NUMBER: 779.2                    GLOBAL ROOT: HLD(799.2,
  DATE CREATED: JAN 19, 2018            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  ROUTINE: HLOASUB1                     NAME: HLOASUB1
  ID: HLOASUB1
GLOBAL REFERENCE: HLD(779.2,D0,
FIELD NUMBER: .01                       FIELD NAME: APPLICATION NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Radiology needs access to clean up radiology entries
 from file HLO APPLICATION REGISTRY as KIDS does not have delete logic in place
 for the 'Delete at Site' action on this file.  A ticket [I18129151FY18] has
 been submitted for this issue.  
  
 HLO Application Registry File access is needed for patch RA*5.0*144.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: RA*5.0*144
KEYWORDS: HLO APPLICATION REGISTRY
KEYWORDS: 779.2
KEYWORDS: $$DELETE
KEYWORDS: HLOASUB1
COMPONENT/ENTRY POINT: DELETE
VARIABLES: FILE                         TYPE: Input
VARIABLES: DA                           TYPE: Input
VARIABLES: ERROR                        TYPE: Both
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE

NUMBER: 6866                            IA #: 6866
  DATE CREATED: JAN 23, 2018            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCFACB
  NAME: IFCAP API: BACKGROUND BATCH PRINT CODE SHEETS
  ID: PRCFACB
 GENERAL DESCRIPTION:   This integration agreement allows the call ^PRCFACB
 when batching code sheets for inventory transactions.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: PRCFACB
 COMPONENT DESCRIPTION:   This module batches the code sheets and prints out a
 list of batching errors.  
VARIABLES: PRCFASYS                     TYPE: Used
 VARIABLES DESCRIPTION:   System ID, value "ISM" 
VARIABLES: DUZ                          TYPE: Used
VARIABLES: PRC('SITE')                  TYPE: Used
 VARIABLES DESCRIPTION:   IFCAP Site 
VARIABLES: NO RETURN VALUE              TYPE: Output
 VARIABLES DESCRIPTION:   No return value from this API.  
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: NOV 29, 2018

NUMBER: 6867                            IA #: 6867
  DATE CREATED: JAN 23, 2018            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCFACBT
  NAME: IFCAP API: BACKGROUND RELEASE OF CODE SHEETS
  ID: PRCFACBT
 GENERAL DESCRIPTION:   This integration agreement allows the call ^PRCFACBT to
 transmit code sheets.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: PRCFACBT
 COMPONENT DESCRIPTION:   Transmits code sheets 
VARIABLES: PRCFASYS                     TYPE: Used
 VARIABLES DESCRIPTION:   System Id - passed in as 'ISM' 
VARIABLES: PRC('SITE')                  TYPE: Used
 VARIABLES DESCRIPTION:   IFCAP Site 
VARIABLES: PRC('PER')                   TYPE: Used
 VARIABLES DESCRIPTION:   Equal the DUZ variable's value.  
VARIABLES: PRCF('BTCH')                 TYPE: Used
 VARIABLES DESCRIPTION:   Batch number 
VARIABLES: DUZ                          TYPE: Used
VARIABLES: NO RETURN VALUE              TYPE: Output
 VARIABLES DESCRIPTION:   No return value from this API.  
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: NOV 29, 2018

NUMBER: 6868                            IA #: 6868
  DATE CREATED: JAN 23, 2018            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCFACX2
  NAME: IFCAP API - BUILD AND TRANSMIT CODE SHEET
  ID: PRCFACX2
 GENERAL DESCRIPTION:   This integration agreement allows the call ^PRCFACX2
 when creating ISMS code sheet - BUILD AND TRANSMIT CODE SHEET when items are
 deleted from the Supply Fund Warehouse inventory.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: PRCFACX2
 COMPONENT DESCRIPTION:   Build and transmit code sheet 
VARIABLES: PRCFASYS                     TYPE: Used
 VARIABLES DESCRIPTION:   System Id, Above PAR is passing 'ISM' for the GIP
 transaction code sheets.  
VARIABLES: PRCFA('TTF')                 TYPE: Used
 VARIABLES DESCRIPTION:   Trans Type - File 420.4 field .01 
VARIABLES: PRC('SITE')                  TYPE: Used
 VARIABLES DESCRIPTION:   IFCAP Site 
VARIABLES: PRC('PER')                   TYPE: Used
 VARIABLES DESCRIPTION:   Above PAR is passing DUZ 
VARIABLES: PRCFA('STRING')              TYPE: Used
 VARIABLES DESCRIPTION:   Code Sheet string to be transmitted 
VARIABLES: PRCFA('STRING',#)            TYPE: Used
 VARIABLES DESCRIPTION:   Array of additional code sheet lines to be
 transmitted (optional) 
VARIABLES: PRCF('TDATE')                TYPE: Used
 VARIABLES DESCRIPTION:   Transmission date (optional), use today if not
 defined 
VARIABLES: PRCFA('REF')                 TYPE: Used
 VARIABLES DESCRIPTION:   Log common number (optional) 
VARIABLES: PRCFA('PRIO')                TYPE: Used
 VARIABLES DESCRIPTION:   Batch priority, use 3 if not defined 
VARIABLES: TMP($J,'STRING',%)           TYPE: Used
 VARIABLES DESCRIPTION:   Global array of additional code sheet lines to be
 transmitted (optional) 
VARIABLES: NO RETURN VALUE              TYPE: Output
 VARIABLES DESCRIPTION:   No return value from this API 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: NOV 29, 2018

NUMBER: 6869                            IA #: 6869
  FILE NUMBER: 8992.3                   GLOBAL ROOT: XTV(8992.3
  DATE CREATED: JAN 24, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ALERT CRITICAL TEXT LOOKUP AND EDIT
  ID: XTV(8992.3
GLOBAL REFERENCE: XTV(8992.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CRITICAL TEXT
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is a string of text, which if present in the message
 text for an alert, should be identified as text identifying a critical alert 
 and the alert emphasized in whatever manner available.  
FIELD NUMBER: .02                       FIELD NAME: PACKAGE-ID
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field is used to specify, if desired, a specific
 package ID to be associated with the CRITICAL TEXT entered in field #.01.  The
 value entered should be the textual part of the value used for XQAID when
 creating the alert(s) (e.g., OR for OrdeR Entry or TIU for Text Integration
 Utility).  If a non-null value is in this field, alerts containing the
 CRITICAL TEXT string will only be indicated as critical alerts if they also
 have text matching the PACKAGE-ID as a part of the ALERTID field.  Matching of
 this value will not be case sensitive.  
FIELD NUMBER: .03                       FIELD NAME: CREATING PACKAGE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the package which is responsible for creating
 this CRITICAL TEXT entry.  
 GLOBAL DESCRIPTION:   Kernel file used to identify strings of text for
 Critical Alerts.  
 GENERAL DESCRIPTION:   
  Kernel Alerts do not have any APIs that enable a package to edit its own 
  Alert Critical text.  Therefore, for the purpose of adding/editing alert 
  critical text, permission is granted to: 
      
   1. Look up alert critical text using VA FileMan APIs, such as ^DIC or 
      $$FIND1^DIC.  
     
   2. Add/edit data in the ALERT CRITICAL TEXT (#8992.3) file using VA 
      FileMan APIs such as ^DIE, UPDATE^DIE or FILE^DIE. 
     
     
   NOTICE:  Adding an entry with Critical Text will report any Alert 
   containing that text as critical.  Careful analysis is necessary to 
   confirm changes will not cause malfunction of any VistA alerts.  When 
   creating a new entry in the ALERT CRITICAL TEXT (#8992.3) file, it is 
   recommended the associated package be indicated in the CREATING PACKAGE 
   (#.03) field.  Inquiries regarding the critical alert text can be 
   directed to the development team for the respective VistA application, 
   if a package development team exists for the application.  Finally, the 
   description included in the ALERT CRITICAL TEXT (#8992.3) file 
   PACKAGE-ID (#.02) field VA FileMan Data Dictionary should be observed 
   to determine if it must be defined.  That field's description indicates 
   that data in this field can further screen alerts from being reported 
   as critical.  Its use should be understood when adding entries to the 
   ALERT CRITICAL TEXT (#8992.3) file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ALERT
KEYWORDS: CRITICAL
SUBSCRIBING PACKAGE: IMAGING
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: FEB 27, 2018

NUMBER: 6870                            IA #: 6870
  FILE NUMBER: 228.1                    GLOBAL ROOT: DENT(228.1,
  DATE CREATED: JAN 28, 2018            CUSTODIAL PACKAGE: DENTAL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: BILLING ACCESS TO DENTAL HISTORY
  ID: DENT(228.1,
GLOBAL REFERENCE: DENT(228.1,D0,0)
FIELD NUMBER: .05                       FIELD NAME: VISIT
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Access 'AV' Cross-Reference with FileMan $$FIND1^DIC 
 GENERAL DESCRIPTION:   The automated billing routines (IBCD*) need access to
 DENTAL HISTORY (#228.1) file to get the necessary information for billing
 non-service connected dental work to third party payers via EDI X12 837D
 (Dental) transactions.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EDI
KEYWORDS: X12
KEYWORDS: DENTAL
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: FEB 21, 2018

NUMBER: 6871                            IA #: 6871
  FILE NUMBER: 228.2                    GLOBAL ROOT: DENT(228.2,
  DATE CREATED: JAN 28, 2018            CUSTODIAL PACKAGE: DENTAL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: BILLING ACCESS TO TREATMENT PLAN TRANSACTION/EXAM 
  ID: DENT(228.2,
GLOBAL REFERENCE: DENT(228.2,D0,0)
FIELD NUMBER: .04                       FIELD NAME: ADA CODE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .09                       FIELD NAME: CONDITION
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: .15                       FIELD NAME: TOOTH NUMBER
  LOCATION: 0;15                        ACCESS: Read w/Fileman
FIELD NUMBER: .16                       FIELD NAME: SURFACES/ROOTS
  LOCATION: 0;16                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: DENT(228.2,D0,1)
FIELD NUMBER: 1.15                      FIELD NAME: DENTAL ENCOUNTER
  LOCATION: 1;15                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Access 'AG' Cross-Reference with FileMan FIND^DIC 
 GENERAL DESCRIPTION:   The automated billing routines (IBCD*) need access to
 TREATMENT PLAN TRANSACTION/EXAM (#228.2) file to get the necessary information
 for billing non-service connected dental work to third party payers via EDI 
 X12 837D (Dental) transactions.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EDI
KEYWORDS: X12
KEYWORDS: DENTAL
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: FEB 21, 2018

NUMBER: 6872                            IA #: 6872
  DATE CREATED: FEB 04, 2018            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Supported                      TYPE: Routine
  ROUTINE: SDCLVMN                      NAME: CLV BYPASS PARAMETER
  ID: SDCLVMN
 GENERAL DESCRIPTION:   This supported DBIA covers an API that will return a
 value that indicates whether a patient should be asked for Camp Lejeune
 eligibility.  
  
 The master value is stored in the PARAMETER DEFINITION file (#8989.51) in the
 SD CLV BYPASS PARAMETER entry.  
  
 The business side requirements included a parameter to be installed and 
 implemented across the board for the Camp Lejeune project.  They do not want
 ANY package to display Camp Lejeune information AT ALL if this master value is
 ON.  This IA will allow packages to call this API and determine if the
 parameter is enabled.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: CAMP LEJEUNE ELIGIBILITY
COMPONENT/ENTRY POINT: $$GETCL(DFN)
 COMPONENT DESCRIPTION:   The switch indicates whether to inhibit the asking of
 Camp Lejeune eligibility questions.  
  
 The API will return one of the following values: 
     1 = 'NO' don't ask  Camp Lejeune Eligibility questions 
     0 = 'YES' ask Camp Lejeune Eligibility questions 
    -1 = error  (Input parameter missing) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN in the PATIENT file (#2).  
COMPONENT/ENTRY POINT: EN

NUMBER: 6873                            IA #: 6873
  DATE CREATED: FEB 13, 2018            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGOTHBTN
  NAME: DG OTH ELIGIBILITY PATIENT STATUS
  ID: DGOTHBTN
 GENERAL DESCRIPTION:   The purpose of this API is to return an array of text
 for CPRS to display the following information on the CPRS button at the top of
 the screen and in the pop-up window associated with this button when the user
 clicks on it: 
  
 - Other Than Honorable discharge (OTH) eligibility status for two categories
 of OTH patients - EMERGENT MH OTH and EXTENDED MH OTH in order to display it
 in CPRS header. The OTH status is calculated by Registration API based on the
 data stored in the PATIENT file (#2) and OTH ELIGIBILITY PATIENT file (#33).  
  
 - Presumptive Psychosis (PP) status based on the settings in the PATIENT file
 (#2) and in the INSURANCE VERIFICATION PROCESSOR file (#355.33) 
  
 - Inactive Patient Record Flags (PRF) assigned to the patient and a history of
 PRF changes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OTH
KEYWORDS: PRF
KEYWORDS: PP
COMPONENT/ENTRY POINT: OTHBTN(DGDFN,DGDATE,RET)
 COMPONENT DESCRIPTION:   This function entry point is to retrieve a text to
 display the following information about the patient: 
  
 a)the OTH (Other Than Honorable) eligibility data for a specific patient. The
 patient for the function call is specified by IEN in the PATIENT file (#2) in
 the first parameter.  
  
 b) the Presumptive Psychosis (PP) status based on 
  
 - settings in the following fields in the PATIENT file (#2): 
  
 (#.361)  PRIMARY ELIGIBILITY CODE 
  
 (#391)   TYPE 
  
 (#1901)  VETERAN (Y/N)? 
  
 (#.301)  SERVICE CONNECTED? 
  
 (#.302)  SERVICE CONNECTED PERCENTAGE 
  
 (#.3721) RATED DISABILITIES (VA) 
  
 (#.5601) PRESUMPTIVE PSYCHOSIS CATEGORY 
  
 - and a presence of the insurance buffer entry in the INSURANCE VERIFICATION
 PROCESSOR file (#355.33) for the patient.  
  
 c) PRF status for the patient in the PRF ASSIGNMENT file (#26.13) and entries
 in the PRF ASSIGNMENT HISTORY file (#26.14).  
  
 The date, for which the appropriate text with the status to be composed and
 returned, is specified in the 2nd parameter of the API in FileMan format.  
  
 The 3rd parameter is used to pass a local array to return the composed text to
 the calling application in the form of array elements as described in the
 description of the RET array.  
  
 MUMPS code example of use, 
  
 - results for EXTENDED MH OTH patient: 
  
 >K RET S DFN=100913,DATE=DT 
  
 >D OTHBTN^DGOTHBTN(DFN,DATE,.RET)  
  
 >ZW RET 
  
 RET(0)=6 
  
 RET(1)="OTH-EXT^Other than Honorable, click for details" 
  
 RET(2)=" " 
  
 RET(3)="Other than Honorable - Extended" 
  
 RET(4)="Eligible for Mental Health care only" 
  
 RET(5)="Not time limited - pending VBA adjudication" 
  
 RET(6)="Adjudication will determine eligibility for continuing care" 
VARIABLES: DGDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN of patient in the PATIENT File (#2).  
VARIABLES: DGDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The date to calculate status in FileMan
 format.  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   The array returns: 
  OTH (Other Than Honorable) status, 
  PP (Presumptive Psychosis) status, 
  Inactive PRF (Patient Record Flags) and history of PRF changes as a text to
 display in OTH/PP/inactive PRF history button and associated pop-up window in
 CPRS.  
  
 Return array: If RET(0)<0 : error code less than zero ^ error message - it is
 an error, and do not display anything 
  
 If RET(0)=0 : then do not display anything 
  
 If RET(0)>0 : see the description below 
  
 RET(0) = number of lines to return 
  
 RET(1) = text for the 1st line on the button ^ text to display when hover over
 the 1st line on the button 
  
 RET(2) = text for the 2nd line on the button ^ text to display when hover over
 the 2nd line on the button 
  
 RET(3) = text for the 1st line of the button-click pop-up message ^ text for
 the 1st line of the warning pop-up message (see the example for the OTH-90
 below) 
  
 RET(>3)= text lines for the rest of the text in the pop-up message when the
 user clicks on the button or for the warning pop-up message 
  
 NOTE: empty or null values in array elements greater than 3 will not be 
 displayed in the pop-up message. Enter at least a blank space in the piece to
 include a blank line in the displayed text.  
  
  
 Example for OTH-90 with zero days remaining: 
 -------------------------------------------
  
 RET(0)=10 
  
 RET(1)="OTH^Other than Honorable, click for details" 
  
 RET(2)="0D,P1^Zero days remaining in the most recent period" 
  
 RET(3)="Other Than Honorable Status" 
  
 RET(4)="   " 
  
 RET(5)="Zero days remaining in the most recent period^WARNING:  EMERGENT MH
 OTH" 
  
 RET(6)="^Zero days remaining in the most recent period." 
  
 RET(7)="^Authorization from VISN Chief Medical Officer is required for an 
 additional 90-Day period." 
  
 RET(8)="   " 
  
 RET(9)="Call Registration team for details." 
  
 RET(10)="Clinician: Determine and document in 1st line of Progress Note if MH
 treatment related to service." 
  
  
 Example for PP workaround settings only: 
 ---------------------------------------
  
 RET(0)=7 
  
 RET(1)="PP^Presumptive Psychosis Authority, click for details" 
  
 RET(2)="^" 
  
 RET(3)="Eligible for mental health care only under Presumptive Psychosis" 
  
 RET(4)="Authority." 
  
 RET(5)="PP Category: No value was selected as PP Indicator is not completed." 
  
 RET(6)="Patients who experienced MST are eligible for MST related mental" 
  
 RET(7)="health and medical care." 
  
  
 Example for inactive PRFs: 
 -------------------------
  
 RET(0)=11 
  
 RET(1)="Inactive Flag^Patient has Inactive Flag(s), click to view" 
  
 RET(2)=" " 
  
 RET(3)="Flag name: HIGH RISK FOR SUICIDE   Status: INACTIVE" 
  
 RET(4)="  Initial Assigned Date: OCT 12, 2019@16:27:10" 
  
 RET(5)="  Originating Site: CAMP MASTER" 
  
 RET(6)="  Owner Site: CAMP MASTER" 
  
 RET(7)="  CAMP MASTER changes:" 
  
 RET(8)="    DATE/TIME: NOV 25, 2020@10:45:44    ACTION: INACTIVATE" 
  
 RET(9)="  BAY PINES VAMC changes:" 
  
 RET(10)="    DATE/TIME: NOV 25, 2019@07:19:17    ACTION: REACTIVATE" 
  
 RET(11)="    DATE/TIME: NOV 24, 2019@09:26:06    ACTION: INACTIVATE" 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   This API is called is called from GET^OROTHCL to
 support the "OROTHCL GET" RPC.  
  DATE ACTIVATED: MAY 29, 2018

NUMBER: 6874                            IA #: 6874
  DATE CREATED: FEB 13, 2018            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPFDBRS
  NAME: DGPF DBRS DATA                  ID: DGPFDBRS
 GENERAL DESCRIPTION:   The purpose of this API is to facilitate the retrieval
 of the Disruptive Behavior Reporting System (DBRS)  numbers. The  DBRS numbers
 are stored in VistA in the file PRF ASSIGNMENT FILE (#26.13).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DBRS
COMPONENT/ENTRY POINT: $$GETDBRS(DGDFN,DGRETARR,DGFLAG)
 COMPONENT DESCRIPTION:   This function entry point is used to retrieve the
 Disruptive Behavior Reporting System (DBRS)  numbers for a specific patient
 and flag. The patient for the function call is specified by IEN in the PATIENT
 file (#2) in the first parameter. The second parameter is used to return the 
 array with data. The third parameter is used to specify the flag, for which
 the last DBRS entry data need to be returned as a return value of the function
 (default is "BEHAVIORAL").  MUMPS code example of use: 
  
 >S DFN=7209323 K ARR W $$GETDBRS^DGPFDBRS(DFN,.ARR),! ZW ARR 
  
 777.123456^for Hines ARR("BEHAVIORAL",1)="777.123456^for Hines" 
 ARR("BEHAVIORAL",2)="500.123456^for Albany" ARR("HIGH RISK FOR
 SUICIDE",1)="675GA.172150^the DBRS case A" ARR("HIGH RISK FOR
 SUICIDE",2)="573GI.170161^the DBRS case B" 
VARIABLES: DGDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) IEN of patient in the PATIENT File (#2).  
VARIABLES: DGRETARR                     TYPE: Output
 VARIABLES DESCRIPTION:   (Required) The array to return information in the
 following format: 
   ARR(1)="DBRS#^DBRS date^DBRS other information" 
   ARR(2)="DBRS#^DBRS date^DBRS other information" 
   ... 
   ARR(n)="DBRS#^DBRS date^DBRS other information" 
  Note: the DBRS entries are listed in the reversed order. ARR(1) contains the
 latest entry.  
VARIABLES: DGFLAG                       TYPE: Input
 VARIABLES DESCRIPTION:   The flag name, for which flag the DBRS entry data
 need to be returned as a return value of the function. Note: Default is
 "BEHAVIORAL".  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   The API is called by HASFLG^ORPRF to support the ORPRF
 GETFLG" RPC.  
  DATE ACTIVATED: MAY 29, 2018

NUMBER: 6875                            IA #: 6875
  DATE CREATED: FEB 15, 2018            CUSTODIAL PACKAGE: 1
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DITP
  NAME: Repoint or Delete Existing File Entry
  ID: DITP                              STATUS: Active
KEYWORDS: DITP
KEYWORDS: POINTER
KEYWORDS: REPOINT
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   The EN^DITP API processes all files that have fields
 or subfields pointing to a particular VA FileMan file. It looks for pointers
 to particular entries in that file and does either of the following: 
        * Repoints each entry to a different specified entry.  
        * Deletes the pointers.  
  
 Format EN^DITP(FILE,.LIST) 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (required) VA FileMan file number.  
VARIABLES: .LIST                        TYPE: Input
 VARIABLES DESCRIPTION:   
  (required) Array (passed by reference) containing list of entries to be
 repointed or deleted.  
  DATE ACTIVATED: MAR 05, 2018

NUMBER: 6876                            IA #: 6876
  DATE CREATED: FEB 15, 2018            CUSTODIAL PACKAGE: 1
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DIUTL
  NAME: Check for Existing Pointers     ID: DIUTL
 GENERAL DESCRIPTION:   The CHKPT^DIUTL API will find all entries that point to
 a record.  
  STATUS: Active
KEYWORDS: POINTER
KEYWORDS: DIUTL
COMPONENT/ENTRY POINT: CHKPT
 COMPONENT DESCRIPTION:   The CHKPT^DIUTL API checks what entries points to a
 particular record. It returns an array of records as either text or detailed.  
  
 The text array will look like: 
  ARRAY(0)=line count 
  ARRAY(line #)="Entry" record ien "in FILE (" file ") refers to it" 
  
  The detailed array will look like: 
  ARRAY(0)=record count 
  ARRAY(pointer from file #, pointer from ien, dd/subdd #, field #)="" 
  
   Format  CHKPT^DIUTL(FILE,IEN,MSG_ROOT,FLAG) 
  
 The FLAG parameter was added with patch DI*22.2*19 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (required) VA FileMan file number.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   (required) Internal Entry Number (IEN) of the record. 
 
VARIABLES: MSG_ROOT                     TYPE: Input
 VARIABLES DESCRIPTION:   (required) Closed global root or local array name
 that will hold the results.  
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Output format 
   1=detailed, 0=text (default) 
  DATE ACTIVATED: MAR 05, 2018

NUMBER: 6877                            IA #: 6877
  FILE NUMBER: 772                      GLOBAL ROOT: HL(772,
  DATE CREATED: FEB 22, 2018            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Read access to HL7 Message Text file for capacity planning.
  ID: HL(772,
GLOBAL REFERENCE: HL(772,DO,0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME ENTERED
  LOCATION: 0;1                         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: 8                         FIELD NAME: PARENT MESSAGE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: NAMESPACE
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: HL(772,'B'
 GLOBAL DESCRIPTION:   Direct global read access to "B" x-ref.  
GLOBAL REFERENCE: HL(772,D0,'S'
FIELD NUMBER: 100                       FIELD NAME: NO. OF CHARACTERS IN MESSAGE
  LOCATION: S;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 101                       FIELD NAME: NO. OF EVENTS IN MESSAGE
  LOCATION: S;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 102                       FIELD NAME: TRANSMISSION TIME
  LOCATION: S;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The purpose of this IA is to allow packages to read the
 HL7 Message Text (#772) file directly.  KMP routines will aggregate message
 metrics for analysis and capacity planning.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA SYSTEM MONITOR
  DATE ACTIVATED: MAR 08, 2018

NUMBER: 6878                            IA #: 6878
  FILE NUMBER: 773                      GLOBAL ROOT: HLMA(,
  DATE CREATED: FEB 22, 2018            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Read access to FILE 773 for capacity planning.
  ID: HLMA(,
GLOBAL REFERENCE: HLMA(D0,0
FIELD NUMBER: 3                         FIELD NAME: TRANSMISSION TYPE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PRIORITY
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: HEADER TYPE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: INITIAL MESSAGE
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: LOGICAL LINK
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: SUBSCRIBER PROTOCOL
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 13                        FIELD NAME: SENDING APPLICATION
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: RECEIVING APPLICATION
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: MESSAGE TYPE
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: EVENT TYPE
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: HLMA(D0,'MSH',D1,0
FIELD NUMBER: 200                       FIELD NAME: MSH
  LOCATION: MSH;0                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: HLMA(D0,'S'
FIELD NUMBER: 102                       FIELD NAME: TIME START TO SEND
  LOCATION: S;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 103                       FIELD NAME: TIME SENT
  LOCATION: S;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 104                       FIELD NAME: TIME OF COMMIT/APP ACK
  LOCATION: S;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 105                       FIELD NAME: TIME OF APPLICATION ACK
  LOCATION: S;5                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: HLMA(D0,'P'
FIELD NUMBER: 20                        FIELD NAME: STATUS
  LOCATION: P;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: HLMA('B',
 GLOBAL DESCRIPTION:   Direct global read access to "B" x-ref.  
 GENERAL DESCRIPTION:   The purpose of this IA is to allow packages to read the
 HL7 Message Administration (#773) file directly.  KMP routines will aggregate
 message metrics for analysis and capacity planning.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA SYSTEM MONITOR
 SUBSCRIBING DETAILS:   The purpose of this IA is to allow the KMP package to
 read the HL7 Message Administration file directly.  KMP routines will
 aggregate message metrics for analysis and capacity planning.  
  DATE ACTIVATED: MAR 08, 2018

NUMBER: 6879                            IA #: 6879
  DATE CREATED: FEB 26, 2018            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHFPDS
  NAME: CREATE BREAKOUT CODES           ID: PRCHFPDS
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition 
    Tool (APAT) to call BREAK^PRCHFPDS to create BREAKOUT CODE (#442.16) 
    sub-file entries in the AMOUNT (#442.1) sub-file of the PROCUREMENT & 
    ACCOUNTING TRANSACTIONS (#442) file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: BREAK
 COMPONENT DESCRIPTION:   This component creates BREAKOUT CODE entries in the
 AMOUNT multiple of the PROCUREMENT & ACCOUNTING TRANSACTIONS file.  
VARIABLES: PRCHPO                       TYPE: Input
 VARIABLES DESCRIPTION:   File 442 IEN 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   File 442 AMOUNT (#442.1) subfile IEN 
VARIABLES: PRCHSC                       TYPE: Input
 VARIABLES DESCRIPTION:   File 442 SOURCE CODE (#8) 
VARIABLES: PRCHB                        TYPE: Input
 VARIABLES DESCRIPTION:   BREAKOUT CODE array 
VARIABLES: I                            TYPE: Used
 VARIABLES DESCRIPTION:   Scratch variable 
VARIABLES: PRCHN('TC')                  TYPE: Output
 VARIABLES DESCRIPTION:   CODE INDEX file (#420.6) NAME (#.01) of the BREAKOUT
 CODE 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 12, 2019

NUMBER: 6880                            IA #: 6880
  DATE CREATED: FEB 26, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS MVI NEW PERSON GET
  REMOTE PROCEDURE: XUS MVI NEW PERSON GET
 GENERAL DESCRIPTION:   The Master Veteran Index (MVI) team requests permission
 to use the following KERNEL Remote Procedure Call (RPC) [XUS MVI NEW PERSON
 GET], which will search for and return an existing entry, if it exists, from
 the NEW PERSON File (#200) to the MVI system. Use of this RPC will provide MVI
 with an immediate path to move forward to view the Identity Access Management
 (IAM) data in VistA to support 2 Factor Authentication (2FA) until future
 technologies become available in the production VistA environments.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XUS MVI NEW PERSON GET
KEYWORDS: 200
KEYWORDS: VA(200
KEYWORDS: 2FA
KEYWORDS: XUMVINPU
KEYWORDS: MVI
KEYWORDS: MPI
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   The Master Veteran Index (MVI) project will use this
 Remote Procedure Call (RPC) to allow the retrieval of a NEW PERSON File (#200)
 entry beginning with patch MPI*1.0*119.  
  DATE ACTIVATED: MAR 28, 2018

NUMBER: 6881                            IA #: 6881
  DATE CREATED: FEB 26, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS MVI NEW PERSON UPDATE
  REMOTE PROCEDURE: XUS MVI NEW PERSON UPDATE
 GENERAL DESCRIPTION:   The Master Veteran Index (MVI) team requests permission
 to use the following KERNEL Remote Procedure Call (RPC) [XUS MVI NEW PERSON
 UPDATE], which will update select fields to correct issues for an existing
 entry in the NEW PERSON File (#200) from the MVI system. Use of this RPC will 
 provide MVI with an immediate path to move forward to manage the Identity
 Access Management (IAM) data in VistA to support 2 Factor Authentication (2FA)
 until future technologies become available in the production VistA
 environments.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XUS MVI NEW PERSON UPDATE
KEYWORDS: 200
KEYWORDS: VA(200
KEYWORDS: 2FA
KEYWORDS: XUMVINPU
KEYWORDS: MVI
KEYWORDS: MPI
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   The Master Veteran Index (MVI) project will use this
 Remote Procedure Call (RPC) to update an existing entry in the NEW PERSON File
 (#200) beginning with patch MPI*1.0*119.  
  DATE ACTIVATED: MAR 28, 2018

NUMBER: 6882                            IA #: 6882
  FILE NUMBER: 777                      GLOBAL ROOT: HLA(D0
  DATE CREATED: FEB 26, 2018            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Read access to HLO Message Body file for capacity planning
  ID: HLA(D0
GLOBAL REFERENCE: HLA(D0,0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME ENTERED
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: MESSAGE TYPE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: EVENT
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: HLA(D0,1,D1,0
FIELD NUMBER: 1                         FIELD NAME: SEGMENTS (NOT BATCHED)
  LOCATION: 1;0                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: HLA('B',
 GLOBAL DESCRIPTION:   "B" cross reference - used to get entries for specific
 dates.  
 GENERAL DESCRIPTION:   The purpose of this IA is to allow subscribing packages
 to read the HLO Message Body (#777) file directly.  KMP routines will
 aggregate message metrics for analysis and capacity planning.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA SYSTEM MONITOR
  DATE ACTIVATED: MAR 09, 2018

NUMBER: 6883                            IA #: 6883
  FILE NUMBER: 778                      GLOBAL ROOT: HLB(
  DATE CREATED: FEB 26, 2018            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Read access to HLO Messages file for capacity planning
  ID: HLB(
GLOBAL REFERENCE: HLB(D0,0
FIELD NUMBER: .03
  FIELD NAME: APPLICATION ACKNOWLEDGMENT TO
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: DIRECTION
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: LINK
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: QUEUE
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: HLB(D0,1
FIELD NUMBER: 1                         FIELD NAME: HDR SEGMENT,COMPONENTS 1-6
  LOCATION: 1;E1,250                    ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: HLB('C'
 GLOBAL DESCRIPTION:   Direct global read access to "C" x-ref.  
GLOBAL REFERENCE: HLB(D0,2
FIELD NUMBER: 2                         FIELD NAME: HDR SEGMENT,COMPONENTS 7-END
  LOCATION: 2;E1,250                    ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The purpose of this IA is to allow subscribing packages
 to read the HLO Messages (#778) file directly.  KMP routines will aggregate
 message metrics for analysis and capacity planning.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA SYSTEM MONITOR
  DATE ACTIVATED: MAR 09, 2018

NUMBER: 6884                            IA #: 6884
  FILE NUMBER: 771                      GLOBAL ROOT: HL(771,
  DATE CREATED: MAR 05, 2018            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  ROUTINE: GMRCPOST99
  NAME: GMRC UPDATE TO THE APPLICATION PARAMETERS FILE
  ID: GMRCPOST99
GLOBAL REFERENCE: HL(771,D0,0
FIELD NUMBER: 3                         FIELD NAME: FACILITY NAME
  LOCATION: 0;3                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   GMRC is requesting a one time update to set the site
 number in the HL7's table for the Application Parameter entry in the HL7
 APPLICATION PARAMETER FILE (#771) during the post install of patch
 GMRC*3.0*99.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: GMRC
COMPONENT/ENTRY POINT: SENDAPP
 COMPONENT DESCRIPTION:   This line tag updates the Facility Name (#3) in the
 HL7 APPLICATION PARAMETER FILE (#771) for the GMRC HCP RECEIVE entry.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING

NUMBER: 6885                            IA #: 6885
  FILE NUMBER: 870                      GLOBAL ROOT: HL(870,
  DATE CREATED: MAR 05, 2018            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  NAME: GMRC UPDATE TO THE HL LOGICAL LINK FILE
  ID: HL(870,
GLOBAL REFERENCE: HLCS(870,D0,0
FIELD NUMBER: .02                       FIELD NAME: INSTITUTION
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DNS DOMAIN
  LOCATION: 0;8                         ACCESS: Write w/Fileman
FIELD NUMBER: 4.5                       FIELD NAME: AUTOSTART
  LOCATION: 0;6                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: HLCS(870,D0,400
FIELD NUMBER: .01
FIELD NUMBER: 400.01                    FIELD NAME: TCP/IP ADDRESS
  LOCATION: 400;1                       ACCESS: Write w/Fileman
FIELD NUMBER: 400.02                    FIELD NAME: TCP/IP PORT
  LOCATION: 400;2                       ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   GMRC requests a one time update as part of the patch
 GMRC*3.0*99 post install to make an update to the HL LOGICAL LINK FILE (#870)
 to add the INSTITUTION (#.02), DNS DOMAIN (#.08), AUTO START (#4.5), TCP/IP
 ADDRESS (#400.01), TCP/IP PORT (#400.02) to the GMRCHCP Link entry.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: GMRC
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING

NUMBER: 6886                            IA #: 6886
  FILE NUMBER: 101                      GLOBAL ROOT: ORD(101,
  DATE CREATED: MAR 05, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: GMRC UPDATE TO THE PROTOCOL FILE
  ID: ORD(101,
GLOBAL REFERENCE: ORD(101,D0,10,D1,0
FIELD NUMBER: .01                       FIELD NAME: ITEM
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   GMRC requests a one time update to the PROTOCOL FILE
 (#101) to edit the GMRC EVSEND OR Protocol to add the GMRC CONSULTS TO HCP
 Protocol as an Item.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: GMRC
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING

NUMBER: 6887                            IA #: 6887
  FILE NUMBER: 420.5                    GLOBAL ROOT: PRCD(420.5,
  DATE CREATED: MAR 05, 2018            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: UNIT OF ISSUE FILE ACCESS (#420.5)
  ID: PRCD(420.5,
GLOBAL REFERENCE: PRCD(420.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Contains the 2 character name that represents the unit of
 issue.  
FIELD NUMBER: 1                         FIELD NAME: FULL NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Contains the full name of the unit of issue, used to
 clarify the 2 character name found in the NAME field.  
GLOBAL REFERENCE: PRCD(420.5,'B',
 GLOBAL DESCRIPTION:   Direct read of "B" cross-reference of the file.  
 GENERAL DESCRIPTION:   Allow direct read of file 420.5, UNIT OF ISSUE.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   Used during extract reporting of workload in the DSS
 extract software.  
  DATE ACTIVATED: MAR 07, 2018

NUMBER: 6888                            IA #: 6888
  DATE CREATED: MAR 13, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSNPI1
  NAME: NPIUSED                         ID: XUSNPI1
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NPI
COMPONENT/ENTRY POINT: $$NPIUSED(XUSNPI,XUSQID,XUSQIL,XUSRSLT,XUSIEN)
 COMPONENT DESCRIPTION:   Extrinsic function used to return an error or warning
 if an NPI is in use.  
                 
 This API is meant to be called from code where a new NPI is being added to a
 provider. It evaluates whether the NPI is currently or previously used by any
 entity on files 200 (NEW PERSON), 4 (INSTITUTION) or 355.93 (IB NON/OTHER VA
 BILLING PROVIDER). If it returns an error, the NPI should not be assigned to
 the provider. If it returns a warning, the warning should be displayed to the
 end user, but they should be allowed to add the NPI to the new provider.  
VARIABLES: XUSNPI                       TYPE: Input
 VARIABLES DESCRIPTION:   The NPI being checked. Required. No Default.  
VARIABLES: XUSQID                       TYPE: Input
 VARIABLES DESCRIPTION:   The Qualified Identifier for the NPI. Required. No
 Default. (ex.  "Individual_ID") 
VARIABLES: XUSQIL                       TYPE: Input
 VARIABLES DESCRIPTION:   The delimited list of entities already using that 
 NPI. This it the output from $$QI^XUSNPI in the format 
 Qualified_Identifier^IEN^Effective_date/time^Active/I nactive; Required. No
 Default.  
VARIABLES: XUSRSLT                      TYPE: Output
 VARIABLES DESCRIPTION:   An array containing either an error or warning
 message (if any).  
VARIABLES: XUSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Only set if this routine is being called from the 
 input transform of the NPI field on files 4, 200 or 355.93. Set to the IEN of
 the entity being edited. This input parameter should ONLY be set if the
 routine is being called from an input transform!!! It suppresses return of the
 error or warning message! No Default.  
VARIABLES: $$NPIUSED                    TYPE: Output
 VARIABLES DESCRIPTION:   No Error - If the NPI is not being used, or if the 
 API is called from the input transform and the NPI was previously used by the
 current user, the API returns:                                        '0' 
                             
 Error - If an error was found. XUSRSLT will contain the error message, and the
 API returns:   '1' 
                             
 Warning - If the current file is NEW PERSON (#200) or IB NON/OTHER VA BILLING
 PROVIDER (#355.93), and if a provider on the other file has the NPI, a warning
 message is returned in XUSRSLT. (A provider can be both a VA and a non-VA
 provider at the same time). The API returns:              '2' 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
SUBSCRIBING PACKAGE: FEE BASIS
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
SUBSCRIBING PACKAGE: LAB SERVICE
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
  DATE ACTIVATED: MAR 14, 2018

NUMBER: 6889                            IA #: 6889
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: MAR 14, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: NEW PERSON PHARMACY FIELDS
  ID: VA(200
GLOBAL REFERENCE: VA(200,D0,0)
FIELD NUMBER: 8                         FIELD NAME: TITLE
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9.2                       FIELD NAME: TERMINATION DATE
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7                         FIELD NAME: DISUSER
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,D0,PS)
FIELD NUMBER: 53.9                      FIELD NAME: REMARKS
  LOCATION: PS;9                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 53.11                     FIELD NAME: DETOX/MAINTENANCE ID NUMBER
  LOCATION: PS;11                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 53.4                      FIELD NAME: INACTIVE DATE
  LOCATION: PS;4                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,D0,PS3)
FIELD NUMBER: 55.1                      FIELD NAME: SCHEDULE II NARCOTIC
  LOCATION: PS3;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 55.2                      FIELD NAME: SCHEDULE II NON-NARCOTIC
  LOCATION: PS3;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 55.3                      FIELD NAME: SCHEDULE III NARCOTIC
  LOCATION: PS3;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 55.4                      FIELD NAME: SCHEDULE III NON-NARCOTIC
  LOCATION: PS3;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 55.5                      FIELD NAME: SCHEDULE IV
  LOCATION: PS3;5                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 55.6                      FIELD NAME: SCHEDULE V
  LOCATION: PS3;6                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,D0,QAR)
FIELD NUMBER: 747.44                    FIELD NAME: DEA EXPIRATION DATE
  LOCATION: QAR;9                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,B)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: VA(200,D0,5)
FIELD NUMBER: 29                        FIELD NAME: SERVICE/SECTION
  LOCATION: 5;1                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   In support of the Veterans Access, Choice, and
 Accountability Act of 2014 (VACAA) and to address Patient Safety concerns for
 non-VA providers whose affiliation is not currently available to CPRS,
 Outpatient Pharmacy requests permission to populate via VA FileMan APIs the
 following fields which are not currently populated by the $$VACAA^XUESSO4()
 API that created the entries.  
  
 If the NEW PERSON (#200) file entries need to be backed out, the Non-VA 
 Provider Inactivate [PSO NON-VA PROVIDER INACTIVATE] option may be used.  This
 option will populate the DISUSER (#7) field with "YES". The INACTIVE DATE
 (#53.4) and TERMINATION DATE (#9.2) fields will be populated with the previous
 day's date so that the providers will be immediately inactive.  The REMARKS
 (#53.9) field will contain a comment that the entry was inactivated by this
 option.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VACAA
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: APR 23, 2018

NUMBER: 6890                            IA #: 6890
  DATE CREATED: MAR 15, 2018
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Other
  NAME: OR EVSEND DVBA                  STATUS: Pending
KEYWORDS: DVBA
KEYWORDS: MASS

NUMBER: 6891                            IA #: 6891
  FILE NUMBER: 355.33                   GLOBAL ROOT: IBA(355.33
  DATE CREATED: MAR 21, 2018            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: File
  NAME: MVAH Insurance                  ID: IBA(355.33
GLOBAL REFERENCE: IBA(355.33,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE ENTERED
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ENTERED BY
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: SOURCE OF INFORMATION
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: STATUS
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .13                       FIELD NAME: OVERRIDE FRESHNESS FLAG
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .18                       FIELD NAME: SERVICE DATE
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBA(355.33,D0,60)
FIELD NUMBER: 60.01                     FIELD NAME: PATIENT NAME
  LOCATION: 60;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.04                     FIELD NAME: *SUBSCRIBER ID
  LOCATION: 60;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.07                     FIELD NAME: *NAME OF INSURED
  LOCATION: 60;7                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.14                     FIELD NAME: PT. RELATIONSHIP - HIPAA
  LOCATION: 60;14                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.08                     FIELD NAME: INSURED'S DOB
  LOCATION: 60;8                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.05                     FIELD NAME: WHOSE INSURANCE
  LOCATION: 60;5                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBA(355.33,D0,20)
FIELD NUMBER: 20.01                     FIELD NAME: INSURANCE COMPANY NAME
  LOCATION: 20;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20.02                     FIELD NAME: PHONE NUMBER
  LOCATION: 20;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20.04
  FIELD NAME: PRECERTIFICATION PHONE NUMBER
  LOCATION: 20;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20.03                     FIELD NAME: BILLING PHONE NUMBER
  LOCATION: 20;3                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBA(355.33,D0,21)
FIELD NUMBER: 21.01                     FIELD NAME: STREET ADDRESS [LINE 1]
  LOCATION: 21;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21.02                     FIELD NAME: STREET ADDRESS [LINE 2]
  LOCATION: 21;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21.04                     FIELD NAME: CITY
  LOCATION: 21;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21.05                     FIELD NAME: STATE
  LOCATION: 21;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21.06                     FIELD NAME: ZIP CODE
  LOCATION: 21;6                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBA(355.33,D0,80)
FIELD NUMBER: 80.01                     FIELD NAME: INQ SERVICE TYPE CODE 1
  LOCATION: 80;1                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBA(355,33,D0,40)
FIELD NUMBER: 40.09                     FIELD NAME: TYPE OF PLAN
  LOCATION: 40;9                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 40.1
  FIELD NAME: BANKING IDENTIFICATION NUMBER
  LOCATION: 40;10                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 40.11
  FIELD NAME: PROCESSOR CONTROL NUMBER (PCN)
  LOCATION: 40;11                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBA(355.33,D0,62)
FIELD NUMBER: 62.07                     FIELD NAME: SUBSCRIBER ADDRESS COUNTRY
  LOCATION: 62;7                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.02                     FIELD NAME: SUBSCRIBER ADDRESS LINE 1
  LOCATION: 62;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.03                     FIELD NAME: SUBSCRIBER ADDRESS LINE 2
  LOCATION: 62;3                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.04                     FIELD NAME: SUBSCRIBER ADDRESS CITY
  LOCATION: 62;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.05                     FIELD NAME: SUBSCRIBER ADDRESS STATE
  LOCATION: 62;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.06                     FIELD NAME: SUBSCRIBER ADDRESS ZIP
  LOCATION: 62;6                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.09                     FIELD NAME: SUBSCRIBER PHONE
  LOCATION: 62;9                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBA(355.33,D0,90)
FIELD NUMBER: 90.01                     FIELD NAME: GROUP NAME
  LOCATION: 90;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 90.02                     FIELD NAME: GROUP NUMBER
  LOCATION: 90;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 90.03                     FIELD NAME: SUBSCRIBER ID
  LOCATION: 90;3                        ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   This IA is for the mobilehealth package to be able to
 submit insurance information to the insurance buffer for processing 
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: MVAH
KEYWORDS: IB
KEYWORDS: INSURANCE
KEYWORDS: MOBILEHEALTH
KEYWORDS: REMEDIATION
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE

NUMBER: 6892                            IA #: 6892
  FILE NUMBER: 75.1                     GLOBAL ROOT: DD(
  DATE CREATED: MAR 21, 2018            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VISTA RADIOLOGY UPDATES DD (CROSS REFERENCE #)
  ID: DD(
GLOBAL REFERENCE: DD(75.1,21,1,
FIELD NUMBER: 1                         FIELD NAME: CROSS-REFERENCE
  LOCATION: 1;0                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   What follows is a VA FileMan index print for the 'DATE
 DESIRED (Not guaranteed)' (75.1,21) field of the RAD/NUC MED ORDERS file.  
  
 There are two "AP" subscripted indices with the same set/kill logic: one 
 traditional, one new-style. The traditional index was left after RA*5.0*130
 created the new-style "AP" index.  
  
 The traditional index, named "AC", should have been deleted. It was not.  
 RA*5.0*124 will correct this oversight.  
  
 Radiology is requesting a one-time Integration Agreement to walk down the 
 cross-reference number subscript to find the aforementioned cross- reference
 number identifying the "AC" index.  
  
 Once the correct cross-reference number is identified Radiology will use the
 supported Application Programmer Interface (API) DELIX^DDMOD to delete the
 "AC" cross-reference.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RA 75.1 DATE DESIRED (Not...)
KEYWORDS: 75.1 AC traditional xref
KEYWORDS: DD(75.1,21,1,
KEYWORDS: RAD/NUC MED ORDERS AC MUMPS
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  DATE ACTIVATED: MAR 22, 2018

NUMBER: 6893                            IA #: 6893
  FILE NUMBER: 200                      GLOBAL ROOT: DD(200
  DATE CREATED: MAR 22, 2018            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Updating DD 'VR' and 'VRPK' Nodes
  ID: DD(200
GLOBAL REFERENCE: DD(200,0)
FIELD NUMBER: VR                        FIELD NAME: VERSION
  LOCATION: 'VR'                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: VRPK                      FIELD NAME: PACKAGE
  LOCATION: 'VRPK'                      ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   IB*2.0*582 sent the entire data dictionary for the NEW
 PERSON (#200) file.  This caused the 'VR' node to be changed from "8.0" to
 "2.0" and the 'VRPK' node to be changed from "XU" to "IB" in the data
 dictionary.  
  
 This ICR is a onetime only request for patch XU*8.0*687 to restore the fields
 to their orignal state of "8.0" for 'VR' and "XU" for 'VRPK'.  This will be
 done via a direct set: 
  
  S ^DD(200,0,"VR")="8.0" 
  S ^DD(200,0,"VRPK")="XU" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VR
KEYWORDS: VRPK
KEYWORDS: DD
SUBSCRIBING PACKAGE: KERNEL
  DATE ACTIVATED: APR 02, 2018

NUMBER: 6894                            IA #: 6894
  DATE CREATED: MAR 27, 2018
  CUSTODIAL PACKAGE: HEALTH DATA & INFORMATICS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HDISDOC
  NAME: HDI COLLECT SDOS                ID: HDISDOC
 GENERAL DESCRIPTION:   API for collecting Standards Development Organization
 (SDO) codes from Laboratory based on items in the ORDERABLE ITEMS File
 (#101.43) 
  STATUS: Active
KEYWORDS: SDO
KEYWORDS: HDI
COMPONENT/ENTRY POINT: $$EN(AREA, TYPE,VALUE, RETURN, ERRARRAY, COUNT)
 COMPONENT DESCRIPTION:   Call point for requesting SDO information 
  
 Return Values: 
      0 (zero) or null  no errors.  
      1 - Area Not Sent.  
      2 - Lookup Value Not Sent.  
      3 - Return Value Not Sent.  
      4 - Improper Search Area.  
      5 - Single Item Not Found in ORDERABLE ITEMS File 101.43.  
      6 - Single Item Not in Area.  
      7 - Partial Lookup Error.  
      8 - Orderable Items File Does Not Have Lab Pointer for 
          Item. Can be repeating, should have an entry in 
          ERRARRY.  
      9 - Orderable Item Lab Pointer Not Found in Lab File. Can 
          be repeating, should have an entry in ERRARRY.  
     12 - Type of Lookup not Sent.  
  
 See the HDI Orderable Items SDO Listing User Manual for additional 
 information.  
VARIABLES: AREA                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This indicates which area the lookup is
 for. L for Laboratory.  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Type of lookup 'S' for Single, 'P' for
 Partial Match, 'ALL' for ALL items.  
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This is the value that will be looked up.
 For Single the value will be the IEN of the item in the ORDERABLE ITEMS File
 (#101.43). For Partial Match the value will be a name partial match to an
 orderable item name in the ORDERABLE ITEMS File (#101.43).  For ALL the value
 will be ALL.  
VARIABLES: RETURN                       TYPE: Output
 VARIABLES DESCRIPTION:   (Required) Closed Root of the variable where the
 found items are returned.  
VARIABLES: ERRARRAY                     TYPE: Output
 VARIABLES DESCRIPTION:   (Optional) Reference to a local variable where the
 error array (if one) can be returned.  
VARIABLES: COUNT                        TYPE: Output
 VARIABLES DESCRIPTION:   (Optional) Reference to a local variable where
 various counts that are collected during the lookup process are returned.  
  DATE ACTIVATED: OCT 30, 2018

NUMBER: 6895                            IA #: 6895
  FILE NUMBER: 101.43                   GLOBAL ROOT: ORD(101.43,
  DATE CREATED: MAR 27, 2018
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: HDI READ ORDERABLE ITEMS File (#101.43)
  ID: ORD(101.43,
GLOBAL REFERENCE: ORD(101.43,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ID 
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: ORD(101.43,D0,.1
FIELD NUMBER: .1                        FIELD NAME: INACTIVATED
  LOCATION: .1;1                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: ORD(101.43,D0,2,D1,0
FIELD NUMBER: .01                       FIELD NAME: SYNONYM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: ORD(101.43,D0,9,0
FIELD NUMBER: 9                         FIELD NAME: SET MEMBERSHIP
  LOCATION: 9;0                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: ORD(101.43,D0,9,D1,0
FIELD NUMBER: .01                       FIELD NAME: SET
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: ORD(101.43,D0,2,0
FIELD NUMBER: 1                         FIELD NAME: SYNONYMS
  LOCATION: 2;0                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Allows Health Data & Informatics (HDI) to read the
 following fields in the ORDERABLE ITEMS File (#101.43) in support of the HDI
 SDO API effort.  
  STATUS: Active
KEYWORDS: HDI
KEYWORDS: SDO
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS
  DATE ACTIVATED: OCT 29, 2018

NUMBER: 6896                            IA #: 6896
  FILE NUMBER: 50.7                     GLOBAL ROOT: PS(50.7,
  DATE CREATED: MAR 27, 2018
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: File
  NAME: HDI READ PHARMACY ORDERABLE ITEM FILE (#50.7)
  ID: PS(50.7,
GLOBAL REFERENCE: PS(50.7,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DOSAGE FORM
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: INACTIVE DATE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Allows Health Data & Informatics (HDI) to read the
 following fields in the PHARMACY ORDERABLE ITEM File (#50.7) in support of the
 HDI SDO API effort.  
  STATUS: Pending
KEYWORDS: HDI
KEYWORDS: SDO
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS

NUMBER: 6897                            IA #: 6897
  FILE NUMBER: 50.606                   GLOBAL ROOT: PS(50.606,
  DATE CREATED: MAR 27, 2018
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: File
  NAME: HDI READ PHARMACY DOSAGE FORM FILE (#50.606)
  ID: PS(50.606,
GLOBAL REFERENCE: PS(50.606,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: INACTIVATION DATE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(50.606,D0,MASTER
FIELD NUMBER: 90                        FIELD NAME: MASTER DOSAGE FORM
  LOCATION: MASTER;1                    ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Allows Health Data & Informatics (HDI) to read the
 following fields in the PHARMACY DOSAGE FORM File (#50.606) in support of the
 HDI SDO API effort.  
  STATUS: Pending
KEYWORDS: HDI
KEYWORDS: SDO
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS

NUMBER: 6898                            IA #: 6898
  FILE NUMBER: 50.60699                 GLOBAL ROOT: PSMDF(50.60699,
  DATE CREATED: MAR 27, 2018
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: File
  NAME: HDI READ PHARMACY MASTER DOSAGE FORM FILE (#50.60699)
  ID: PSMDF(50.60699,
GLOBAL REFERENCE: PSMDF(50.60699,D0,0
FIELD NUMBER: .01                       FIELD NAME: RXNORM NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: RXCUI CODE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSMDF(50.60699,D0,TERMSTATUS,0
FIELD NUMBER: 99.991                    FIELD NAME: EFFECTIVE DATE/TIME
  LOCATION: TERMSTATUS;0                ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSMDF(50.6069901,D0,TERMSTATUS,D1,0
FIELD NUMBER: .01                       FIELD NAME: EFFECTIVE DATE/TIME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Allows Health Data & Informatics (HDI) to read the
 following fields in the PHARMACY MASTER DOSAGE FORM File (#50.60699) in
 support of the HDI SDO API effort.  
  STATUS: Pending
KEYWORDS: HDI
KEYWORDS: SDO
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS

NUMBER: 6899                            IA #: 6899
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG(
  DATE CREATED: MAR 27, 2018
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: File
  NAME: HDI READ PHARMACY DRUG FILE (#50)
  ID: PSDRUG(
GLOBAL REFERENCE: PSDRUG(D0,0
FIELD NUMBER: .01                       FIELD NAME: GENERIC NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSDRUG(D0,2
FIELD NUMBER: 2.1                       FIELD NAME: PHARMACY ORDERABLE ITEM
  LOCATION: 2;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSDRUG(D0,I
FIELD NUMBER: 100                       FIELD NAME: INACTIVE DATE
  LOCATION: I;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSDRUG(D0,ND
FIELD NUMBER: 22                        FIELD NAME: PSNDF VA PRODUCT NAME ENTRY 
  LOCATION: ND;3                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Allows Health Data & Informatics (HDI) to read the
 following fields in the PHARMACY DRUG File (#50) in support of the HDI SDO API
 effort.  
  STATUS: Pending
KEYWORDS: HDI
KEYWORDS: SDO
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS

NUMBER: 6900                            IA #: 6900
  FILE NUMBER: 50.68                    GLOBAL ROOT: PSNDF(
  DATE CREATED: MAR 27, 2018            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  USAGE: Private                        TYPE: File
  NAME: HDI READ PHARMACY VA PRODUCT FILE (#50.68)
  ID: PSNDF(
GLOBAL REFERENCE: PSNDF(50.68,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSNDF(50.68,D0,11,0
FIELD NUMBER: 43                        FIELD NAME: CODING SYSTEM
  LOCATION: 11;0                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSNDF(50.68,D0,11,D1,1,0
FIELD NUMBER: .02                       FIELD NAME: CODE
  LOCATION: 1;0                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSNDF(50.68,D0,11,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CODING SYSTEM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSNDF(50.68,D0,11,D1,1,D2,0
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSNDF(50.68,D0,TERMSTATUS,0
FIELD NUMBER: 99.991                    FIELD NAME: EFFECTIVE DATE/TIME
  LOCATION: TERMSTATUS;0                ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSNDF(50.68,D0,TERMSTATUS,D1,0
FIELD NUMBER: .01                       FIELD NAME: EFFECTIVE DATE/TIME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Allows Health Data & Informatics (HDI) to read the
 following fields in the PHARMACY VA PRODUCT File (#50.68) in support of the
 HDI SDO API effort.  
  STATUS: Pending
KEYWORDS: HDI
KEYWORDS: SDO
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS

NUMBER: 6901                            IA #: 6901
  FILE NUMBER: 60                       GLOBAL ROOT: LAB(60,
  DATE CREATED: MAR 27, 2018            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: HDI READ LABORATORY SERVICE LABORATORY TEST FILE (#60)
  ID: LAB(60,
GLOBAL REFERENCE: LAB(60,D0,0
FIELD NUMBER: .01                       FIELD NAME:  NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: TYPE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: LOCATION (DATA NAME)
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: FIELD
  LOCATION: 0;12                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: LAB(60,D0,2,0
FIELD NUMBER: 200                       FIELD NAME: LAB TEST INCLUDED IN PANEL
  LOCATION: 2;0                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LAB(60,D0,2,D1,0
FIELD NUMBER: .01                       FIELD NAME: LAB TEST
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LAB(60,D0,14
FIELD NUMBER: 132                       FIELD NAME: TEST INACTIVE
  LOCATION: 14;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 133                       FIELD NAME: TEST INACTIVE DATE
  LOCATION: 14;3                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: LAB(60,D0,1,0
FIELD NUMBER: 100                       FIELD NAME: SITE/SPECIMEN
  LOCATION: 1;0                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LAB(60,D0,1,D1,0
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
GLOBAL REFERENCE: LAB(60,D0,1,D1,6)
FIELD NUMBER: 30                        FIELD NAME: MLTF NUMBER
  LOCATION: 6;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LAB(60,D0,1,D1,5)
FIELD NUMBER: 32                        FIELD NAME: RESULT/SPECIMEN INACTIVE
  LOCATION: 5;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 33
  FIELD NAME: RESULT/SPECIMEN INACTIVE DATE
  LOCATION: 5;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Allows Health Data & Informatics (HDI) to read the
 following fields in the LABORATORY SERVICE LABORATORY TEST File (#60) in
 support of the HDI SDO API effort.  
  STATUS: Active
KEYWORDS: HDI
KEYWORDS: SDO
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS
  DATE ACTIVATED: MAY 01, 2018

NUMBER: 6902                            IA #: 6902
  FILE NUMBER: 66.3                     GLOBAL ROOT: LRMLTF(
  DATE CREATED: MAR 27, 2018            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: HDI READ MASTER LABORATORY TEST FILE (#66.3)
  ID: LRMLTF(
GLOBAL REFERENCE: LRMLTF(D0,0
FIELD NUMBER: .01                       FIELD NAME: LAB TEST NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LRMLTF(D0,1
FIELD NUMBER: .02                       FIELD NAME: ALTERNATE TEST NAME
  LOCATION: 1;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LRMLTF(D0,2
FIELD NUMBER: .04                       FIELD NAME: LOINC CODE
  LOCATION: 2;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: COMPONENT
  LOCATION: 2;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: PROPERTY
  LOCATION: 2;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LRMLTF(D0,3
FIELD NUMBER: .07                       FIELD NAME: TIME ASPECT
  LOCATION: 3;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .08                       FIELD NAME: SPECIMEN
  LOCATION: 3;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .09                       FIELD NAME: SCALE
  LOCATION: 3;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: METHOD
  LOCATION: 3;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: LRMLTF(D0,TERMSTATUS,0
FIELD NUMBER: 99.991                    FIELD NAME: EFFECTIVE DATE/TIME
  LOCATION: TERMSTATUS;0                ACCESS: Read w/Fileman
GLOBAL REFERENCE: LRMLTF(D0,TERMSTATUS,D1,0
FIELD NUMBER: .01                       FIELD NAME: EFFECTIVE DATE/TIME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Allows Health Data & Informatics to read (HDI) the
 following fields in the LABORATORY SERVICE MASTER LABORATORY TEST File (#66.3)
 in support of the HDI SDO API effort.  
  STATUS: Active
KEYWORDS: HDI
KEYWORDS: SDO
SUBSCRIBING PACKAGE: HEALTH DATA & INFORMATICS
  DATE ACTIVATED: MAY 01, 2018

NUMBER: 6903                            IA #: 6903
  FILE NUMBER: 409.4                    DATE CREATED: MAR 29, 2018
  CUSTODIAL PACKAGE: SCHEDULING         USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: SDCLVMN
  NAME: PCE USAGE OF FILE 409.4         ID: SDCLVMN
GLOBAL REFERENCE: SD(409.4,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DT BYPASSED
  LOCATION: SD(409.4,DO,0)              ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the date and time an action required encounter
 was bypassed.  
FIELD NUMBER: .02                       FIELD NAME: PATIENT
  LOCATION: SD(409.4,D0,0)              ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This field is the patient involved in this bypass action. 
 
FIELD NUMBER: .03                       FIELD NAME: CLINIC
  LOCATION: SD(409.4,D0,0)              ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   
  This is the clinic this patient was scheduled to be seen at.  
FIELD NUMBER: .04                       FIELD NAME: APPT.DATE/TIME
  LOCATION: SD(409.4,D0,0)              ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the date and time of this clinic appointment. 
 The time is required.  
FIELD NUMBER: .05                       FIELD NAME: ACTION REQUIRED
  LOCATION: SD(409.4,D0,0)              ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the comment which will replace ACTION REQUIRED in
 the encounter STATUS FIELD.  
FIELD NUMBER: .06                       FIELD NAME: BYPASS USER
  LOCATION: SD(409.4,D0,0)              ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the name of the user initiating the bypass
 action.  
FIELD NUMBER: .07                       FIELD NAME: ENCOUNTER UNIQUE ID
  LOCATION: SD(409.4,D0,0)              ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is the unique id assigned to this visit.  
FIELD NUMBER: .09                       FIELD NAME: DATA SOURCE
  LOCATION: SD(409.4,D0,0)              ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   This is an indicator of where the data came from for a
 VISIT file entry. 
 GENERAL DESCRIPTION:   The Patient Care Encounter (PCE) has authority to use
 the BYPASS ACTION REQUIRED LOG file (# 409.4).  
  
 An API is used to call routine BYPASS^SDCLVMN(PXUPAT,PXUHLOC,PXUDT,PXUTLVST) 
 to file the data into the BYPASS ACTION REQUIRED LOG file #409.4.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PCE
KEYWORDS: CLV
KEYWORDS: BYPASS ACTION REQUIRED LOG
COMPONENT/ENTRY POINT: BYPASS
 COMPONENT DESCRIPTION:   PCE Encounter data will be filed to the BYPASS ACTION
 REQUIRED LOG FILE #409.4 when the bypass for Camp Lejeune is ON and a null is
 received as data for Camp Lejeune eligible veterans in the Camp Lejeune
 exposure response.  
VARIABLES: PXUPAT                       TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the PATIENT file (#2).  
VARIABLES: PXUHLOC                      TYPE: Input
 VARIABLES DESCRIPTION:   The hospital location of the encounter.  
VARIABLES: PXUDT                        TYPE: Input
 VARIABLES DESCRIPTION:   The date and time of the encounter.  
VARIABLES: PXUTLVST                     TYPE: Input
 VARIABLES DESCRIPTION:   The pointer to the visit that is being used.  
VARIABLES: PXASOURC                     TYPE: Input
 VARIABLES DESCRIPTION:   The data source that entered the encounter.  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   PATIENT CARE ENCOUNTER will use the BYPASS ACTION
 REQUIRED LOG file (# 409.4) to record Camp Lejeune encounters that have a
 status of ACTION REQUIRED but are bypassed and given the status of CHECKED
 OUT.  

NUMBER: 6904                            IA #: 6904
  FILE NUMBER: 9999999.64               GLOBAL ROOT: AUTTHF(
  DATE CREATED: APR 09, 2018
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  NAME: DBIA6904                        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.  
FIELD NUMBER: .3                        FIELD NAME: CATEGORY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .1                        FIELD NAME: ENTRY TYPE
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: .11                       FIELD NAME: INACTIVE FLAG
  LOCATION: 0;11                        ACCESS: 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 pieces
 1-11 and usage of the "B" cross reference.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: AUTTHF
KEYWORDS: VIA
KEYWORDS: VIAB
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6905                            IA #: 6905
  DATE CREATED: APR 10, 2018            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: Option DG G&L CHANGES VIEW used on external menus
 GENERAL DESCRIPTION:   Allow the G&L view changes option (DG G&L CHANGES VIEW)
 to be assigned to menus on namespaces outside of DG.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: DSS - DECISION SUPPORT SYSTEM EXTRACTS
 SUBSCRIBING DETAILS:   DSS would like to add the DG G&L CHANGES VIEW option to
 our existing menu, ECX MAINTENANCE.  
  
 This option will allow users in DSS to view updates to the gains and losses
 sheet in order to track movements that may affect DSS extracts.  
  DATE ACTIVATED: MAY 29, 2018

NUMBER: 6906                            IA #: 6906
  FILE NUMBER: 19625                    GLOBAL ROOT: DSI(19625,
  DATE CREATED: APR 10, 2018            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: DBIA 6906                       ID: DSI(19625,
GLOBAL REFERENCE: DSI(19625,D0,
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Updates to this file included all fields and usage of
 cross references.  
 GENERAL DESCRIPTION:   This ICR is used to file new insurance data fields from
 ICB to the DSIV ICB AUDIT (#19625) file that are not part of the INSURANCE
 BUFFER (#355.33) file so that they may be updated as part of buffer processing 
 by insurance verifiers. 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: VIAB
KEYWORDS: 19625
KEYWORDS: DSIV ICB AUDIT
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6907                            IA #: 6907
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX
  DATE CREATED: APR 10, 2018            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: File
  NAME: IB FM ACCESS TO PSRX FOR SHRPE  ID: PSRX
GLOBAL REFERENCE: PSRX(
FIELD NUMBER: 8                         FIELD NAME: DAYS SUPPLY
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: RELEASED DATE/TIME
  LOCATION: 2;13                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,1,D1,0)
FIELD NUMBER: 17                        FIELD NAME: RELEASED DATE/TIME
  LOCATION: 0;18                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Read w/Fileman 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Need access to fields 8 and 31 to prorate prescriptions
 in the patient has High Risk for Suicide Flag.  

NUMBER: 6908                            IA #: 6908
  DATE CREATED: APR 18, 2018            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: Routine
  ROUTINE: XMD                          NAME: MAILMAN SET FROM
  ID: XMD
 GENERAL DESCRIPTION:   This integration agreement allows Enterprise
 Manager/Watchdog to call SETFROM in routine XMD to verify and define the FROM
 User prior to calling to send the message.  
  Code reference D SETFROM^XMD(.DSIWFROM,.DSIWXMIN) 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ENTERPRISE MANAGER/WATCHDOG
COMPONENT/ENTRY POINT: SETFROM
 COMPONENT DESCRIPTION:   Verify the FROM before calling SENDMSG^XMXAPI(.  
VARIABLES: XMDUZ                        TYPE: Both
 VARIABLES DESCRIPTION:   Input either; user or .5 Return user ien.  Uses the
 XMINSTR flags if passed.  
VARIABLES: XMINSTR                      TYPE: Both
 VARIABLES DESCRIPTION:   Array containing optional flags R, P, & I 
 XMINSTR("FLAGS") = flags If Confirmation Requested then include "R" If
 Priority then include "P" If Information Only then include "I" 

NUMBER: 6909                            IA #: 6909
  FILE NUMBER: 869.1                    GLOBAL ROOT: HLCS(869.1
  DATE CREATED: APR 18, 2018            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  NAME: HL LOWER LEVEL PROTOCOL TYPE    ID: HLCS(869.1
 GENERAL DESCRIPTION:   This IA allows WATCHDOG to verify the HL LOWER LEVEL 
 PROTOCOL TYPE prior to submitting the Protocol to taskman. The IA will access
 the BACKGROUND ROUTINE and ENVIRONMENT CHECK ROUTINE in order to verify the 
 processing routine and run the environment check routine prior to submitted
 the task.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ENTERPRISE MANAGER/WATCHDOG

NUMBER: 6910                            IA #: 6910
  DATE CREATED: APR 30, 2018            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  ROUTINE: MAGDHOWP
  NAME: BUILD VI HL7 ORM MESSAGE FOR CP CHECK-IN OR CANCELLATION
  ID: MAGDHOWP
 GENERAL DESCRIPTION:   VistA Imaging's (MAG) CLINPROC^MAGDHOWP is called by
 MDHL7BH to build and broadcast VistA Imaging HL7 ORM (order) messages for a
 check-in or cancellation events in the Clinical Procedure (MD) application.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: MD HL7 ORM
KEYWORDS: CLINICAL PROC HL7 ORM IMAGING
COMPONENT/ENTRY POINT: CLINPROC
VARIABLES: MDD702                       TYPE: Input
 VARIABLES DESCRIPTION:   'MDD702' in the internal entry number (IEN) of the
 record in the CP TRANSACTION (#702) file.  
VARIABLES: MDORFLG                      TYPE: Input
 VARIABLES DESCRIPTION:   'MDORFLG' is an input variable that indicates the
 value of the ORDER CONTROL (ORC-1) and ORDER STATUS (ORC-5) fields used to
 build at Common Order (ORC) segment for a ORM (Order) HL7 message.  
VARIABLES:  
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES

NUMBER: 6911                            IA #: 6911
  DATE CREATED: APR 30, 2018            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  ROUTINE: MAGDFCNV
  NAME: SWAP CP INSTRUMENT ORDER # w/ IMAGING CONSULT ACCESSION #
  ID: MAGDFCNV
 GENERAL DESCRIPTION:   VistA Imaging software has been enhanced to replace the
 CP Instrument Order Number with the VistA Imaging consults Accession Number.
 This greatly improves interoperability between Clinical Procedures and VistA 
 Imaging CPRS Consult Request Tracking.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: CP INSTRUMENT ORDER # REPLACED
COMPONENT/ENTRY POINT: GMRCACN
 COMPONENT DESCRIPTION:   This component will return a site-specific accession
 number for clinical specialties. GMRCIEN, the input variable, is the CPRS
 Consult Request Tracking IEN of the record in the REQUEST/CONSULTATION (#123)
 file.  
  
 Returned is a string in the following format: <sss>-GMR-<gmrcien>, where <sss>
 is station number.  
VARIABLES: MDGMRCIEN                    TYPE: Input
 VARIABLES DESCRIPTION:   'MDGMRCIEN' is set to the consult number (IEN) from
 REQUEST/CONSULTATION file (#123) record.  
VARIABLES: MDIORD                       TYPE: Output
 VARIABLES DESCRIPTION:   'MDIORD' is set to a site-specific accession number
 for clinical procedure transaction.  
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES

NUMBER: 6912                            IA #: 6912
  FILE NUMBER: 13                       GLOBAL ROOT: DIC(13
  DATE CREATED: MAY 03, 2018            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ ACCESS TO DIC(13
  ID: DIC(13
GLOBAL REFERENCE: DIC(13,'C',
 GLOBAL DESCRIPTION:   The "C" cross reference of code of the religion.  
 GENERAL DESCRIPTION:   Income Verification Match (IVM) Version 2.0 uses the
 "C" cross reference of the RELIGION file (#13) with the following code: 
 $O(^DIC(13,"C",code,0)) to obtain the internal entry number of the religion
 code for storage.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DIC(13
KEYWORDS: RELIGION
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  DATE ACTIVATED: DEC 03, 2018

NUMBER: 6913                            IA #: 6913
  FILE NUMBER: 11                       GLOBAL ROOT: DIC(11
  DATE CREATED: MAY 03, 2018            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ ACCESS TO THE DIC(11
  ID: DIC(11
GLOBAL REFERENCE: DIC(11,'B'
 GLOBAL DESCRIPTION:   The "B" cross reference of the marital status.  
 GENERAL DESCRIPTION:   Income Verification Match (IVM) Version 2.0 uses the
 "B" cross of the MARITAL STATUS file (#11) to get the internal entry number of
 the marital status with the following code: $O(^DIC(11,"B",IVMFLD,0)) where
 variable IVMFLD is the marital status name. 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MARITAL STATUS
KEYWORDS: DIC(11
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  DATE ACTIVATED: DEC 03, 2018

NUMBER: 6914                            IA #: 6914
  FILE NUMBER: 8992.1                   GLOBAL ROOT: XTV(8992.1
  DATE CREATED: MAY 09, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Lab References to Alert Tracking File
  ID: XTV(8992.1
GLOBAL REFERENCE: XTV(8992.1,D0,2)
FIELD NUMBER: 2                         FIELD NAME: DATA FOR PROCESSING
  LOCATION: 2;E1,245                    ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   The DATA FOR PROCESSING (#2) field for each alert
 internal entry number will be compared against a specific Lab case number to
 determine if an alert was generated for the case.  
GLOBAL REFERENCE: XTV(8992.1,'C'
FIELD NUMBER: .04                       FIELD NAME: PATIENT
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   The Lab package will scan all alerts for a patient's
 identification number (variable DFN). ^XTV(8992.1,"C" is subscripted by the 
 patient's identification number and internal entry number of the alert in
 ^XTV(8992.1.  
 GENERAL DESCRIPTION:   Lab will search the Alert Tracking file to determine if
 an alert was sent for a Lab case after it was verified by a pathologist.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ALERT
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   A Lab routine will review all alerts for a patient's
 identification number (DFN) at the "C" cross reference of the Alert Tracking
 file.  Each alert will be analyzed against a known Lab case number to
 determine if an alert was generated for the Lab case.  
  DATE ACTIVATED: MAY 14, 2018

NUMBER: 6915                            IA #: 6915
  FILE NUMBER: 8989.51                  GLOBAL ROOT: XTV(8989.51,
  DATE CREATED: MAY 04, 2018            CUSTODIAL PACKAGE: TOOLKIT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Parameter Definition File Access
  ID: XTV(8989.51,
GLOBAL REFERENCE: XTV(8989.51,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   For post-installation, if NAME contains "DSIVA", then
 "DSIVA" is changed to "DSSO".  In the case of back out, if NAME contains 
 "DSSO", then "DSSO" is changed to "DSIVA".  
FIELD NUMBER: .02                       FIELD NAME: DISPLAY TEXT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   For post-installation, if DISPLAY TEXT contains "DSIVA",
 then "DSIVA" is changed to "DSSO".  In the case of back out, if DISPLAY TEXT
 contains "DSSO", then "DSSO" is changed to "DSIVA".  
GLOBAL REFERENCE: XTV(8989.51,'B'
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   "B" cross-reference             For post-installation, $O
 is used to 
                                 loop through each instance of a 
                                 DSIVA-namespaced parameter, and in 
                                 preparation for back out, $O is used 
                                 to loop through each instance of a 
                                 DSSO-namespaced parameter.  
 GENERAL DESCRIPTION:   Permission requested for initial release of DSSO 2.0 
  
 Due to namespace conversion of the Advanced Prosthetics Acquisition Tool 
 (APAT) product from DSIVA to DSSO, it is necessary to convert the existing
 DSIVA-namespaced parameter definitions to the new DSSO namespace.  
  
 For this, there will be a one-time installation routine which will utilize the
 "B" cross-reference of the PARAMETER DEFINITION FILE (#8989.51) to loop
 through each instance of a DSIVA-namespaced parameter.  In this loop, each
 parameter NAME and DISPLAY NAME will have DSIVA replaced with DSSO using
 FileMan API FILE^DIE.  
  
 To prepare for the need to back out, there is also a one-time routine which
 will utilize the "B" cross-reference of the PARAMETER DEFINITION FILE
 (#8989.51) to loop through each instance of a DSSO-namespaced parameter.  In
 this loop, each parameter NAME and DISPLAY NAME will have DSSO replaced with
 DSIVA using FileMan API FILE^DIE.  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: DSSO 2.0
KEYWORDS: APAT
KEYWORDS: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JUN 05, 2018

NUMBER: 6916                            IA #: 6916
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: MAY 15, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: APAT READ/WRITE ACCESS TO NEW PERSON FILE
  ID: VA(200,
GLOBAL REFERENCE: VA(200,D0,201)
FIELD NUMBER: 201                       FIELD NAME: PRIMARY MENU OPTION
  LOCATION: 201;1                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,D0,203,D1,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,'AD'
 GLOBAL DESCRIPTION:   File 200 "AD" cross-reference  Used to look up by
 SECONDARY MENU 
                                OPTIONS using FileMan API FIND^DIC 
                                and direct global read 
GLOBAL REFERENCE: VA(200,'AP'
 GLOBAL DESCRIPTION:   File 200 "AP" cross-reference  Used to look up by
 PRIMARY MENU OPTION 
                                using FileMan API FIND^DIC and 
                                direct global read 
 GENERAL DESCRIPTION:   This is a one-time request for the initial release of
 DSSO 2.0.  
  
 The Advanced Prosthetics Acquisition Tool (APAT) must migrate from namespace
 DSIVA to namespace DSSO.  Because of this, the Primary and Secondary menu
 options have been renamed. 
  
 The post-installation routine will search for users that have PRIMARY MENU
 OPTION set to DSIVA APAT and will change the PRIMARY MENU OPTION to DSSO APAT.
 Also, if a user has DSIVA APAT in the SECONDARY MENU OPTIONS multiple, then
 DSSO APAT will be added to that multiple.  
  
 APAT requests permission to use FileMan API FIND^DIC with index AP to identify
 those users with PRIMARY MENU OPTION set to DSIVA APAT.  FileMan API FILE^DIE
 will be used to change the PRIMARY MENU OPTION to DSSO APAT.  
  
 APAT requests permission to use FileMan API FIND^DIC with index AD to identify
 those users with DSIVA APAT in the SECONDARY MENU OPTIONS multiple.  FileMan
 API FILE^DIE will be used to add DSSO APAT to the SECONDARY MENU OPTIONS
 multiple.  
  
 In a future build, FileMan API FIND^DIC using index AD will be used to
 identify all users with secondary menu option DSIVA APAT, and this secondary
 menu option will be deleted from the SECONDARY MENU OPTIONS multiple of each
 identified user using FileMan API FILE^DIE.  
  
 If back-out is needed, APAT requests permission to change the PRIMARY MENU
 OPTION to DSIVA APAT if a user's PRIMARY MENU OPTION is DSSO APAT.  This will
 be accomplished in a similar manner using FileMan APIs FIND^DIC and FILE^DIE.  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: DSSO 2.0
KEYWORDS: APAT
KEYWORDS: ADVANCED PROSTHETICS ACQ TOOL
KEYWORDS: PERSON
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: MAY 31, 2018

NUMBER: 6917                            IA #: 6917
  DATE CREATED: JUN 04, 2018            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFHLIN1
  NAME: CCR&A USE OF VAFHLIN1           ID: VAFHLIN1
 GENERAL DESCRIPTION:   The Community Care Referral and Authorizations (CCR&A)
 calls the EN^VAFHLIN1 API in order to retrieve a patient's insurance
 information and format it in HL7 format. This data is transmitted with the
 CCR&A consult request for billing purposes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CCRA
KEYWORDS: CCR&A
KEYWORDS: VAFHLIN1
COMPONENT/ENTRY POINT: EN
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient's unique DFN.  
VARIABLES: VAFSTR                       TYPE: Input
 VARIABLES DESCRIPTION:   A string of fields requested, separated by commas. If
 null, return all fields.  
VARIABLES: VAFHLQ                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional HL7 null variable.  
VARIABLES: VAFHLFS                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional HL7 field separator.  
VARIABLES: VAFARRY                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional user-supplied array name which will hold the
 HL7 IN1 segments. Otherwise, ^TMP("VAFIN1",$J) will be used.  
VARIABLES: VAFHLECH                     TYPE: Input
 VARIABLES DESCRIPTION:   Optional HL7 encoding  characters.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
  DATE ACTIVATED: AUG 14, 2018

NUMBER: 6918                            IA #: 6918
  DATE CREATED: MAY 29, 2018
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Supported                      TYPE: Routine
  ROUTINE: PSS50P66                     NAME: PSS50P66
  ID: PSS50P66
 GENERAL DESCRIPTION:   The purpose of this ICR is to grant the ability to
 return information related to the DOSAGE FORM file (#50.606).  
  STATUS: Pending
KEYWORDS: PSS50P66
KEYWORDS: DOSAGE FORM
COMPONENT/ENTRY POINT: ALL
 COMPONENT DESCRIPTION:   This API does a look-up from the DOSAGE FORM file
 (#50.606).  
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the entry in the DOSAGE FORM file (#50.606)
 [required] 
VARIABLES: PSSFT                        TYPE: Input
 VARIABLES DESCRIPTION:   NAME field (#.01) of the DOSAGE FORM file (#50.606)
 [optional] (a value of "??" may be used) 
VARIABLES: PSSFL                        TYPE: Input
 VARIABLES DESCRIPTION:   Inactive date. [optional] A null value will return
 all entries. Entry of a FileMan format date (ex: 3030917) will return active
 entries after this date.  
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   Defined by the calling application [required] 
VARIABLES: ~TMP                         TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,LIST,0) = Total entries returned or -1^NO
 DATA FOUND 
  
 ^TMP($J,LIST,PSSIEN,.01) = NAME (50.606,.01) 
  
 ^TMP($J,LIST,PSSIEN,3) = VERB (50.606,3) 
  
 ^TMP($J,LIST,PSSIEN,5) = PREPOSITION (50.606,5) 
  
 ^TMP($J,LIST,PSSIEN,7) = INACTIVATION DATE (50.606,7)^External format (ex: SEP
 12,1999) 
  
 ^TMP($J,LIST,PSSIEN,"MRDSFRM",0) = Total entries returned for this sub-file or
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST,PSSIEN,"MRDSFRM",PSS(1),.01) = MED ROUTE FOR DOSAGE FORM 
 (50.6061,.01)^NAME (51.2,.01) 
  
 ^TMP($J,LIST,PSSIEN,"NOUN",0) = Total entries returned for this sub-file or
 -1^NO DATA FOUND 
  
 ^TMP($J,LIST,PSSIEN,"NOUN",PSS(1),.01) = NOUN (50.6066,.01) 
  
 ^TMP($J,LIST,"B",NAME,PSSIEN) ="" 
  DATE ACTIVATED: DEC 27, 2018

NUMBER: 6919                            IA #: 6919
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19,
  DATE CREATED: MAY 30, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: OPTION FILE ACCESS
  ID: DIC(19,
GLOBAL REFERENCE: DIC(19,'B'
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Direct Global Read 
 GENERAL DESCRIPTION:   This is a one-time request for the initial release of
 DSSO 2.0.  
  
 The Advanced Prosthetics Acquisition Tool (APAT) must migrate from namespace
 DSIVA to namespace DSSO.  Because of this, the post-installation routine must
 verify the existence of both options "DSIVA APAT" and "DSSO APAT" in the
 OPTION FILE (#19) when adding option "DSSO APAT" to users who currently have
 the "DSIVA APAT" option as a PRIMARY MENU OPTION or SECONDARY MENU OPTIONS in
 the NEW PERSON FILE (#200). To accomplish this, direct global reads through
 the "B" cross-reference using $ORDER are used for each Option NAME.  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: DSSO 2.0
KEYWORDS: OPTION
KEYWORDS: APAT
KEYWORDS: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: MAY 31, 2018

NUMBER: 6920                            IA #: 6920
  DATE CREATED: JUN 05, 2018            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DIFROMSR
  NAME: DBIA1052-D                      ID: DIFROMSR
 GENERAL DESCRIPTION:   KIDS needs to call the VA FileMan DIFROM Server
 routines and Compiler routines.  These calls are used to update the Data
 Dictionaries, Templates, Forums, and Functions at a site during the
 installation of a package.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: KIDS
COMPONENT/ENTRY POINT: RP
 COMPONENT DESCRIPTION:   RP(DIFRFLG,DIFRFIA,DIFRSA,DIFRMSGR) Resolves pointers
 on target system 
VARIABLES: DIFRFLG                      TYPE: Input
 VARIABLES DESCRIPTION:   Reserved for future use (optional) 
VARIABLES: DIFRFIA                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) - Close Input Array Reference See DIFROM
 SERVER documentation for FIA array structure definitions.  If undefined
 SOURCE_ARRAY will be used by appending "FIA" to the source array root
 subscript.  
VARIABLES: DIFRSA                       TYPE: Input
 VARIABLES DESCRIPTION:   SOURCE_ARRAY=CLOSED_INPUT_ARRAY_ROOT (Required) -
 Closed Input Array Reference where the file data is temporarily stored for
 distribution.  
VARIABLES: DIFRMSGR                     TYPE: Input
 VARIABLES DESCRIPTION:   MSG_ROOT=CLOSED ARRAY REFERENCE (Optional) - Closed
 array reference where messages such as errors will be returned.  If not
 passed, descendants of ^TMP will be used.  
SUBSCRIBING PACKAGE: KERNEL
  DATE ACTIVATED: JUN 05, 2018

NUMBER: 6921                            IA #: 6921
  DATE CREATED: JUN 05, 2018            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DIP1
  NAME: INQUIRE OPTION FOR MENU MAN     ID: DIP1
 GENERAL DESCRIPTION:   Allows Inquire type option for Menu Man 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DIP1
COMPONENT/ENTRY POINT: N
 COMPONENT DESCRIPTION:   Must have variables DI, FLDS, and DIQ(0) defined 
VARIABLES: DI                           TYPE: Input
 VARIABLES DESCRIPTION:   Global root of file 
VARIABLES: FLDS                         TYPE: Input
 VARIABLES DESCRIPTION:   List of fields to display, same structure as DR
 variable 
VARIABLES: DIQ(0)                       TYPE: Input
 VARIABLES DESCRIPTION:   Can contain one of the following: C,R,B C=Computed
 Fields R=Record Number B=Both Computed Fields and Record Number 
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   Options in the OPTION file #19, of TYPE INQUIRE calls
 N^DIP1 
  DATE ACTIVATED: MAR 08, 2019

NUMBER: 6922                            IA #: 6922
  DATE CREATED: JUN 08, 2018            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA6922
  STATUS: Pending

NUMBER: 6923                            IA #: 6923
  DATE CREATED: JUN 12, 2018            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Routine
  ROUTINE: DGUTL3                       NAME: CAMP LEJEUNE STATUS INDICATOR
  ID: DGUTL3
 GENERAL DESCRIPTION:   This supported DBIA covers an API that will return a
 value that indicates whether the patient has Camp Lejeune exposure.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$GETCL(DFN)
 COMPONENT DESCRIPTION:   This API will take the DFN as an input parameter and
 return the value of the Camp Lejeune file (#.3217) of the PATIENT file (#2).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the PATIENT file (#2).  
VARIABLES: $$GETCL                      TYPE: Output
 VARIABLES DESCRIPTION:   The API will return the following values: 
   1 = 'YES' (Camp Lejeune exposure indicated) 
   0 = 'NO'  (No Camp Lejeune exposure) 
  -1 = error (Input parameter missing) 

NUMBER: 6924                            IA #: 6924
  FILE NUMBER: 8925.1                   GLOBAL ROOT: TIU(8925.1,
  DATE CREATED: JUN 13, 2018
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: UPDATE TECHNICAL FIELDS FOR CLINICAL PROCEDURES
  ID: TIU(8925.1,
GLOBAL REFERENCE: TIU(8925.1,D0,0)
FIELD NUMBER: 4.1                       FIELD NAME: COMMIT ACTION
  LOCATION: 4.1;E1,245                  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.9                       FIELD NAME: POST-SIGNATURE CODE
  LOCATION: 4.9;E1,245                  ACCESS: Both R/W w/Fileman
FIELD NUMBER: .07                       FIELD NAME: STATUS
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Clinical Procedures requires TIU DOCUMENT DEFINITION
 (#8925.1) fields COMMIT ACTION (#4.1) and POST-SIGNATURE CODE (#4.9) be set
 when a clinical procedure is configured for High Volume.  Local staff do not 
 have access to edit these fields through the normal TIU Document Definitions
 menu options as programmer access is required. 
  
 Clinical Procedures will verify the title is inactive before updating the two
 fields with a value of 'Q' (or remove the 'Q'). Local staff will be required
 to INACTIVATE the title and REACTIVATE the title as needed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU DOCUMENT DEFINITION
KEYWORDS: 8925.1
KEYWORDS: MD*1*65
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  DATE ACTIVATED: JUN 13, 2018

NUMBER: 6925                            IA #: 6925
  FILE NUMBER: 779.4                    GLOBAL ROOT: HLD(779.4,
  DATE CREATED: JUN 14, 2018            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: HLO SUBSCRIPTION REGISTRY (#779.4) READ NAME (#.01) FIELD
  ID: HLD(779.4,
GLOBAL REFERENCE: HLD(779.4,DA,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the top-level .01 field on file 779.4. 
 GENERAL DESCRIPTION:   With the release of MAG*3.0*208 the VistA Imaging
 application requests the permission to read the name of the HLO SUBSCRIPTION
 REGISTRY record.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HLO SUBSCRIPTION REGISTRY
KEYWORDS: MD*1.0*60
KEYWORDS: MAG*3.0*208
KEYWORDS: IMAGING
SUBSCRIBING PACKAGE: IMAGING
  DATE ACTIVATED: JUN 14, 2018

NUMBER: 6926                            IA #: 6926
  FILE NUMBER: 123.3                    GLOBAL ROOT: GMR(123.3,
  DATE CREATED: JUN 14, 2018
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: GMRC PROCEDURE - CP UTILITY
  ID: GMR(123.3,
GLOBAL REFERENCE: GMR(123.3,D0,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: CLINICAL PROCEDURE
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Clinical Procedures package will do a lookup on the
 GMRC PROCEDURE file (#123.3) for the consult procedure to clinical procedure
 conversion utility. Clinical Procedures will set the CLINICAL PROCEDURE field
 (#.04) as part of the conversion.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMR(123.3
KEYWORDS: MD*1*65
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  DATE ACTIVATED: JUN 19, 2018

NUMBER: 6927                            IA #: 6927
  FILE NUMBER: 123.5                    GLOBAL ROOT: GMR(123.5,
  DATE CREATED: JUN 14, 2018
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: REQUEST SERVICES LOOKUP FOR CP UTILITIES
  ID: GMR(123.5,
GLOBAL REFERENCE: GMR(123.5,D0,
FIELD NUMBER: .01                       FIELD NAME: SERVICE NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   CLINICAL PROCEDURES will do a lookup on the REQUEST
 SERVICES file (#123.3) for the consult to clinical procedure conversion
 utilities.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MD*1*65
KEYWORDS: GMR(123.5
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  DATE ACTIVATED: JUN 19, 2018

NUMBER: 6928                            IA #: 6928
  FILE NUMBER: 702.09                   GLOBAL ROOT: MDS(702.09,
  DATE CREATED: JUN 15, 2018            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CP DICOM INTEROPERABILITY
  ID: MDS(702.09,
GLOBAL REFERENCE: MDS(702.09,DA,
FIELD NUMBER: .13                       FIELD NAME: BI-DIRECTIONAL
  LOCATION: .1;3                        ACCESS: Read w/Fileman
FIELD NUMBER: .17                       FIELD NAME: HL7 UNIVERSAL SERVICE ID
  LOCATION: .1;7                        ACCESS: Read w/Fileman
FIELD NUMBER: .19                       FIELD NAME:  CP - DICOM INTEROPERABILITY
  LOCATION: .1;9                        ACCESS: Read w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAG*3.0*208
KEYWORDS: MD*1.0*60
KEYWORDS: IMAGING
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   MAG*3.0*208 requires and integration agreement with
 Clinical Procedure to read with FileMan specific fields from the CP INSTRUMENT
 file.  
  DATE ACTIVATED: JUN 15, 2018

NUMBER: 6929                            IA #: 6929
  FILE NUMBER: 702                      GLOBAL ROOT: MDD(702,
  DATE CREATED: JUN 15, 2018            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: CP DICOM INTEROPERABILITY TRANSACTIONS
  ID: MDD(702,
GLOBAL REFERENCE: MDD(702,DA,
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: CP DEFINITION
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: CONSULT NUMBER
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: VSTRING
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: .11                       FIELD NAME: SUBMITTED TO INSTRUMENT
  LOCATION: 0;11                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: MDD(702,'ACON',
FIELD NUMBER: .05                       FIELD NAME: CONSULT NUMBER
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This global reference requires MAG*3.0*208 to $ORDER
 through the "ACON" cross-reference on the CONSULT NUMBER field.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAG*3.0*208
KEYWORDS: MD*1.0*60
KEYWORDS: IMAGING
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   MAG*3.0*208 requires and integration agreement with
 Clinical Procedure to read with FileMan specific fields from the CP
 TRANSACTION file.  
  DATE ACTIVATED: JUN 15, 2018

NUMBER: 6930                            IA #: 6930
  FILE NUMBER: 702.01                   GLOBAL ROOT: MDS(702.01,
  DATE CREATED: JUN 15, 2018            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: CP DICOM INTEROPERABILITY DEFINITIONS
  ID: MDS(702.01,
GLOBAL REFERENCE: MDS(702.01,DA,
FIELD NUMBER: .05                       FIELD NAME: HOSPITAL LOCATION
  LOCATION: 0;5                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: MDS(702.01,DA(1),.1,DA,
FIELD NUMBER: .01                       FIELD NAME: INSTRUMENT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   INSTRUMENT is a multiple field under the INSTRUMENT
 (#702.011) sub-file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAG*3.0*208
KEYWORDS: MD*1.0*60
KEYWORDS: IMAGING
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   MAG*3.0*208 requires and integration agreement with
 Clinical Procedure to read with FileMan specific fields from the CP DEFINITION
 file.  
  DATE ACTIVATED: JUN 15, 2018

NUMBER: 6931                            IA #: 6931
  DATE CREATED: JUN 15, 2018            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGDFCNV
  NAME: CP DICOM INTEROPERABILITY RETURN SSAN FOR CLIN SPEC
  ID: MAGDFCNV
 GENERAL DESCRIPTION:   This extrinsic function will return a site-specific
 accession number for clinical specialties. GMRCIEN is the CPRS Consult Request
 Tracking GMRC IEN from the REQUEST/CONSULTATION file (#123).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAG*3.0*208
KEYWORDS: MD*1.0*60
KEYWORDS: IMAGING
KEYWORDS: MEDICOM
COMPONENT/ENTRY POINT: GMRCACN
 COMPONENT DESCRIPTION:   This is an API that returns a site-specific accession
 number sss-GMR-nnnnnnnn for CPRS Consult Request Tracking consults and 
 procedures.  
VARIABLES: MDGMRCIEN                    TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN of the associated consult/request.  
VARIABLES: ACNUMB                       TYPE: Output
 VARIABLES DESCRIPTION:   The value returned is the clinical specialties
 site-specific accession number.  
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Added 9/27/24 effective with Patch MECH 1.0 request
 subscription to call GMRCACN for site-specific accession number for a specific
 consult request.  
  DATE ACTIVATED: JUN 15, 2018

NUMBER: 6932                            IA #: 6932
  DATE CREATED: JUN 15, 2018            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGDHOWP
  NAME: CP DICOM INTEROPERABILITY BUILD HL7 MESSAGE
  ID: MAGDHOWP
 GENERAL DESCRIPTION:   This API builds the VistA Imaging procedure HL7 ORM
 (order) message using the VistA Imaging formatted accession number.  The API
 may conditionally return the HL7 ORM message body for Clinical Procedures'
 use.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MAG*3.0*208
KEYWORDS: MD*1.0*60
KEYWORDS: IMAGING
COMPONENT/ENTRY POINT: CLINPROC
VARIABLES: FILE702P                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the pointer to the clinical procedure record
 in the CP TRANSACTION (#702) file.  
VARIABLES: ORDERFLAG                    TYPE: Input
 VARIABLES DESCRIPTION:   This variable indicates if the enhanced HL7 order
 message is new or canceled.  
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  DATE ACTIVATED: JUN 15, 2018

NUMBER: 6933                            IA #: 6933
  DATE CREATED: JUN 18, 2018
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU LINK SECONDARY VISIT
  REMOTE PROCEDURE: TIU LINK SECONDARY VISIT
  STATUS: Active
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JUN 19, 2018

NUMBER: 6934                            IA #: 6934
  FILE NUMBER: 409.68                   GLOBAL ROOT: SCE(
  DATE CREATED: JUN 19, 2018            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ENCOUNTER FILE XREF BY PATIENT/DATE
  ID: SCE(
GLOBAL REFERENCE: SCE('ADFN',DFN,
 GLOBAL DESCRIPTION:   The "ADFN" cross-reference is used to look at all
 encounters for a patient for the last two years.  
GLOBAL REFERENCE: SCE(D0,0)
FIELD NUMBER: .04                       FIELD NAME: LOCATION
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Looking for clinics with same stop codes to determine if
 this is a follow-up visit.  
FIELD NUMBER: .06                       FIELD NAME: PARENT ENCOUNTER
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Do not include child encounters.  
 GENERAL DESCRIPTION:   This integration agreement is needed to determine
 whether an appointment made using the mobile scheduling application by either
 the veteran or staff is considered a follow-up appointment.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ADFN
KEYWORDS: OUTPATIENT
KEYWORDS: ENCOUNTERS
KEYWORDS: FOLLOW-UP
SUBSCRIBING PACKAGE: MOBILE SCHEDULING APPLICATIONS SUITE
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 9/20/19 - Mental Health's Suicide Prevention
 Project will be adding new functionality in patch YS*5.01*135 that will allow
 providers to view key metrics in assessing high risk patients. One of these
 metrics is the patient's last outpatient encounter at a mental health clinic,
 using the ^SCE("ADFN" index to look through the encounters. 
  DATE ACTIVATED: JUN 20, 2018

NUMBER: 6935                            IA #: 6935
  DATE CREATED: JUN 22, 2018            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMTEXT
  NAME: CLINICAL REMINDER TEXT FORMATTING APIs
  ID: PXRMTEXT
 GENERAL DESCRIPTION:   Clinical Reminders has a set of text formatting APIs,
 this ICR allows other packages to use that functionality.  
  
 Revision History: 
  05/08/2024 Added the component FORMAT, available with PXRM*2.0*67. ORDER 
  ENTRY/RESULTS REPORTING was added as a subscriber, effective with  
  OR*3.0*508.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: List Manager
KEYWORDS: Text Formatting Utilities
COMPONENT/ENTRY POINT: COLFMT
 COMPONENT DESCRIPTION:   This entry point is a columnar text formatter.  
  
 Usage: D COLFMT^PXRMTEXT(FMTSTR,TEXTSTR,PC,.NL,.OUTPUT) 
VARIABLES: FMTSTR                       TYPE: Input
 VARIABLES DESCRIPTION:   Format string -  ^ separated string for each column
 in the output. For example, 35R2 defines a right justified column 35
 characters wide with 2 blank spaces following. Columns can be centered (C)
 left justified (L) or right justified (R).  
  
VARIABLES: TEXTSTR                      TYPE: Input
 VARIABLES DESCRIPTION:   The text string to be formatted, the text for each
 column is separated by 
 "^".
VARIABLES: PC                           TYPE: Input
 VARIABLES DESCRIPTION:   This is the character used to 'pad' the text so it
 fills the width of the column. Typically, this is the space character.  
  
  
VARIABLES: NL                           TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of lines of formatted text
 returned in OUTPUT; passed by reference.  
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   An array containing the columnar formatted output
 text; passed by reference.  
COMPONENT/ENTRY POINT: FORMATS
 COMPONENT DESCRIPTION:   This API formats a single line of text.  
                 
 Usage: D FORMATS^PXRMTEXT(LM,RM,TEXTLINE,.NOUT,.TEXTOUT) 
VARIABLES: LM                           TYPE: Input
 VARIABLES DESCRIPTION:   The left margin.  
VARIABLES: RM                           TYPE: Input
 VARIABLES DESCRIPTION:   The right margin.  
VARIABLES: TEXTLINE                     TYPE: Input
 VARIABLES DESCRIPTION:   The single line of text to be formatted.  
VARIABLES: NOUT                         TYPE: Output
 VARIABLES DESCRIPTION:   The number of lines of formatted text; passed by
 reference.  
VARIABLES: TEXTOUT                      TYPE: Output
 VARIABLES DESCRIPTION:   This array contains the formatted text; passed by
 reference.  
  
COMPONENT/ENTRY POINT: LMFMTSTR
 COMPONENT DESCRIPTION:   This entry point builds a columnar format string
 using the List Manager variable VALMDDF.  
  
 Usage: S FMTSTR=$$LMFMTSTR^PXRMTEXT(VALMDDF,JSTR) 
VARIABLES: VALMDDF                      TYPE: Input
 VARIABLES DESCRIPTION:   The List Manager variable VALMDDF contains the list
 template column formatting information. The structure is: VALMDDF(COLUMN
 NAME)=COLUMN NAME^COLUMN^WIDTH^CAPTION ^VIDEO^SCROLL LOCK. COLUMN is the
 starting column and WIDTH is the column width.  
VARIABLES: JSTR                         TYPE: Input
 VARIABLES DESCRIPTION:   A string specifying the justification for each
 column. There is one character for each column. The characters can be: L=left,
 C=center, and R=right. The default is center.  
                             
 The string "RLLLL" specifies column 1 is right justified and columns 2-5 are
 left justified.  
COMPONENT/ENTRY POINT: FORMAT
 COMPONENT DESCRIPTION:   This API formats the array of text in TEXTIN so that
 each formatted line has a left margin of LM and a right margin of RM. The
 formatted text is in TEXTOUT. "\\" is the end of line marker.  Lines ending
 with "\\" will not have anything appended to them. A blank line can be created
 with a line containing just "\\". Lines containing nothing but whitespace will
 also act like a "\\".  
  
 Usage: D FORMAT(LM,RM,NIN,.TEXTIN,.NOUT,.TEXTOUT) 
VARIABLES: LM                           TYPE: Input
 VARIABLES DESCRIPTION:   The left margin.  
VARIABLES: RM                           TYPE: Input
 VARIABLES DESCRIPTION:   The right margin.  
VARIABLES: NIN                          TYPE: Input
 VARIABLES DESCRIPTION:   The number of lines of text in TEXTIN.  
VARIABLES: TEXTIN                       TYPE: Input
 VARIABLES DESCRIPTION:   An array containing the lines of text to be
 formatted; passed by reference.  
VARIABLES: NOUT                         TYPE: Output
 VARIABLES DESCRIPTION:   The number of formatted lines in TEXTOUT; passed by
 reference.  
VARIABLES: TEXTOUT                      TYPE: Output
 VARIABLES DESCRIPTION:   An array containing the formatted text; passed by
 reference.  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Patch PX*1*211 creates integrated management utilities
 for Education Topics, Exams, and Health Factors. These are based on the model
 of the management utility that was developed for Clinical Reminders
 Taxonomies.  Because they follow the same model that was used for Taxonomies,
 they need the same text formatting utilities. This ICR allows PCE to use those
 utilities promoting code reuse.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 5/6/24, effective with OR*3.0*508. OE/RR needs
 access to the Clinical Reminders Text Formatting tools to correctly format the
 detail text in the CPRS Information Panel functionality.  
  DATE ACTIVATED: JUN 26, 2018

NUMBER: 6936                            IA #: 6936
  FILE NUMBER: 811.6                    GLOBAL ROOT: PXRMD(811.6,
  DATE CREATED: JUN 26, 2018            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: REMINDER SPONSOR
  ID: PXRMD(811.6,
GLOBAL REFERENCE: PXRMD(811.6,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Pointed to
GLOBAL REFERENCE: PXRMD(811.6,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CONTACT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PXRMD(811.6,D0,1,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: DETAILED INFORMATION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PXRMD(811.6,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ASSOCIATED SPONSORS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PXRMD(811.6,D0,100)
FIELD NUMBER: 100                       FIELD NAME: CLASS
  LOCATION: 100;1                       ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Specifying who the "owner" is of a PCE data type
 facilitates the maintenance and management of the data type. When there are
 questions about the data type's definition or usage, the owner can provide the 
 answers. The Reminder Sponsor file, #811.6, was created for this purpose and
 because it is common for the owner of Clinical Reminders content (definitions,
 terms, etc.) to also be the owner of the related PCE data types, allowing PCE
 to point to and read from file #811.6 provides a consistent mechanism for
 managing ownership.  
  
 This ICR allows PCE to point to file #811.6 and read the following fields: 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: REMINDER SPONSOR
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  DATE ACTIVATED: JUN 26, 2018

NUMBER: 6937                            IA #: 6937
  DATE CREATED: JUN 29, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  ROUTINE: XUSNPI                       NAME: VACAA NON-VA PROVIDER BULK LOAD
  ID: XUSNPI
 GENERAL DESCRIPTION:   Bulk-load non-VA entities and providers to be
 identified in VistA when documenting patient care.  
     
 On August 7, 2014, the President signed into law PL 113-146, the Veterans 
 Access, Choice, and Accountability Act of 2014 (VACAA). The law offers an 
 additional authority for VHA to expand current capacity and ensure that 
 Veterans have timely access to high-quality care. The law creates a new 
 paradigm for providing health care, set forth in the Veterans Choice program
 provisions within Title I Section 101 of VACAA. VA is utilizing a Contractor
 to provide health care and third party administrative (TPA) services set forth
 through VACAA Section 101. As a result of this law, VA must upload a list of
 non-VA medical care providers into the VistA system in order to maintain an
 accurate and updated list of non-VA providers in the Choice program.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: VACAA
COMPONENT/ENTRY POINT: ADDNPI
 COMPONENT DESCRIPTION:   Outpatient Pharmacy utilitizes this API so that the
 EFFECTIVE DATE/TIME (#42) field and associated sub-fields will be populated in
 the NEW PERSON (#200) file for providers which are filed by the Non-VA
 Provider import process.  
  
 FORMAT: $$ADDNPI^XUSNPI(XUSQI,XUSIEN,XUSNPI,XUSDATE,XUSTATUS) 
  
 Where: 
  
  XUSQI    : Qualified Identifier. Required. 
             For example: Individual_ID Or Organization_ID 
  XUSIEN   : Internal Entry Number. Required.  
  XUSNPI   : National Provider Identifier. Required.  
  XUSDATE  : Active Date. Required.  
  XUSTATUS : Active or Inactive. (Defaults to "Active" if not passed in) 
VARIABLES: XUSQI                        TYPE: Input
 VARIABLES DESCRIPTION:   Qualified Identifier, Required. For example:
 Individual_ID Or Organization_ID 
VARIABLES: XUSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number. Required.  
VARIABLES: XUSNPI                       TYPE: Input
 VARIABLES DESCRIPTION:   National Provider Identifier. Required.  
VARIABLES: XUSDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   Active Date. Required.  
VARIABLES: XUSTATUS                     TYPE: Input
 VARIABLES DESCRIPTION:   Active or Inactive. (Defaults to "Active" if not
 passed in) 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 6938                            IA #: 6938
  DATE CREATED: JUL 03, 2018            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: BPSRES1
  NAME: Add Additional NCPDP Fields to a Claim
  ID: BPSRES1
 GENERAL DESCRIPTION:   BPSRES1 allows the user to add to a claim NCPDP fields
 not already on the payer sheet.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NCPDP
COMPONENT/ENTRY POINT: $$ADDLFLDS
 COMPONENT DESCRIPTION:   This function allows the user select one or more
 NCPDP fields to be added to a claim request.  The user may select only from
 those fields which are not already on the payer sheet, which are outgoing
 fields, and which have some logic in place for pulling a value.  
VARIABLES: BPS02                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to BPS CLAIMS.  
VARIABLES: BPS59                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to BPS TRANSACTION.  
VARIABLES: BPSDOS                       TYPE: Input
 VARIABLES DESCRIPTION:   Date of Service.  If passed in, then this value will
 be displayed to the user when listing fields to be added to the claim.  
VARIABLES: BPSADDLFLDS                  TYPE: Output
 VARIABLES DESCRIPTION:   This array will list the fields being added to the
 claim.  
   BPSADDLFLDS(Field IEN) = Value to send.  
VARIABLES: $$ADDLFLDS                   TYPE: Output
 VARIABLES DESCRIPTION:   This function will return 
    1 - If user entered additional fields.  
    0 - If user added no fields.  
   -1 - If user exited out via "^".  
COMPONENT/ENTRY POINT: $$SAVE
 COMPONENT DESCRIPTION:   This function saves overrides into BPS NCPDP
 OVERRIDES.  
VARIABLES: BPSACTION                    TYPE: Input
 VARIABLES DESCRIPTION:   Action selected by the user (e.g. RED, PRO, ECS).  
VARIABLES: BPS59                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to BPS TRANSACTIONS.  
VARIABLES: BPSADDLFLDS                  TYPE: Input
 VARIABLES DESCRIPTION:   Passed by reference.  An array listing the NCPDP
 fields to be added to the claim.  
   BPSADDLFLDS(NCPDP Field) = "" 
VARIABLES: BPSOVRIEN                    TYPE: Input
 VARIABLES DESCRIPTION:   Passed by reference, IEN of the entry in the file BPS
 NCPDP OVERRIDE.  
VARIABLES: $$SAVE                       TYPE: Output
 VARIABLES DESCRIPTION:   This function returns a '1' if the values were
 successfully saved; otherwise, it returns '-1'.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: JUL 26, 2018

NUMBER: 6939                            IA #: 6939
  DATE CREATED: JUL 03, 2018            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: BPSPRRX5
  NAME: Billing Related Functions       ID: BPSPRRX5
 GENERAL DESCRIPTION:   BPSPRRX5 contains subroutines related to secondary
 billing.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$GETPL59
 COMPONENT DESCRIPTION:   The function returns the Plan from an entry in the
 BPS TRANSACTION file.  
VARIABLES: BP59                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to BPS TRANSACTION.  
VARIABLES: $$GETPL59                    TYPE: Output
 VARIABLES DESCRIPTION:   The Plan from an entry in the BPS TRANSACTION file.  
COMPONENT/ENTRY POINT: $$GETRTP59
 COMPONENT DESCRIPTION:   This function returns the Rate Type from an entry in
 the BPS TRANSACTION file.  
VARIABLES: BP59                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to BPS TRANSACTION.  
VARIABLES: $$GETRTP59                   TYPE: Output
 VARIABLES DESCRIPTION:   The Rate Type from an entry in the BPS TRANSACTION
 file.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: JUL 26, 2018

NUMBER: 6940                            IA #: 6940
  FILE NUMBER: 19610.5                  GLOBAL ROOT: VEJD(19610.5,
  DATE CREATED: JUL 10, 2018
  CUSTODIAL PACKAGE: VENDOR - DOCUMENT STORAGE SYS
  USAGE: Private                        TYPE: File
  NAME: CODING COMPLETED                ID: VEJD(19610.5,
GLOBAL REFERENCE: VEJD(19610.5,D0,13)
FIELD NUMBER: 13.01                     FIELD NAME: VISIT POINTER
  LOCATION: 13;1                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Use this field for lookup into this file.  
GLOBAL REFERENCE: VEJD(19610.5,D0,5)
FIELD NUMBER: 20                        FIELD NAME: CCM CODING STATUS
  LOCATION: 5;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Getting external value of this field.  
 GENERAL DESCRIPTION:   This agreement allows Integrated Billing (IB) to
 determine if coding has completed for an entry in the VEJD PFCS LINKAGE DATA
 (#19610.5) file.  
  
 IB will use the VISIT # to perform a look up into this file to get the CCM
 CODING STATUS (#20) field. 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: NO-TOUCH
KEYWORDS: CODING COMMENTS
KEYWORDS: EBILLING
KEYWORDS: TAS
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 6941                            IA #: 6941
  DATE CREATED: JUL 11, 2018
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Supported                      TYPE: Routine
  ROUTINE: PSSUTIL                      NAME: PSSUTIL HAZ
  ID: PSSUTIL
 GENERAL DESCRIPTION:   This IA is provided by PDM (Pharmacy Data Management)
 as an API Function to return Hazardous To Handle and Hazardous To Dispose
 indication flags per a drug in the DRUG file (#50) or Orderable Item in the
 PHARMACY ORDERABLE ITEM file (#50.7).  
  
 Note: Hazardous indications are fields stored in the PSNDF file VA PRODUCT 
       file (#50.68).  
    
       If any drug has a Hazardous to Handle or Dispose indication, then 
       the Pharmacy Orderable Item (OI) and any drugs pointing to that same 
       OI will be considered Hazardous for the same indications.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HAZ
KEYWORDS: HAZARDOUS
KEYWORDS: DISPOSE INDICATOR HAZ
KEYWORDS: HANDLE INDICATOR HAZ
COMPONENT/ENTRY POINT: $$HAZ(PSSIEN,PSSF)
VARIABLES: PSSIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   DRUG file (#50) ien or PHARMACY ORDERABLE ITEM file
 (#50.7) ien.  (required) 
VARIABLES: PSSF                         TYPE: Input
 VARIABLES DESCRIPTION:   "OI" passed, if file ien passed in param 1 is for
 file #50.7 else assumes the default.   (optional)  default = drug ien 
VARIABLES: FUNCTION VALUES              TYPE: Output
 VARIABLES DESCRIPTION:   Piece 1 = 0 or 1  (Hazardous To Handle) Piece 2 = 0
 or 1  (Hazardous To Dispose) Piece 3 = PHARMACY ORDERABLE ITEM file (#50.7)
 NAME 

NUMBER: 6942                            IA #: 6942
  DATE CREATED: JUL 11, 2018
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Supported                      TYPE: Routine
  ROUTINE: PSSUTIL                      NAME: PSSUTIL HAZWARNG
  ID: PSSUTIL
 GENERAL DESCRIPTION:   This DBIA is provided by PDM (Pharmacy Data Management)
 as an API to return the Hazardous To Handle and Hazardous To Dispose alert
 text generated for a specific drug in the DRUG file (#50) appropriate for the 
 package that is calling it.  
  
 Note: Hazardous indications are fields stored in the PSNDF file VA PRODUCT 
       file (#50.68).  
  
       If any drug has a Hazardous to Handle or Dispose indication, then 
       the Pharmacy Orderable Item (OI) and any drugs pointing to that same 
       OI will be considered Hazardous for the same indications.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HAZ
KEYWORDS: HAZARDOUS
KEYWORDS: HAZ WARNING TEXT
KEYWORDS: HAZ ALERT TEXT
COMPONENT/ENTRY POINT: $$HAZWARNG(PSSDRIEN,PSSIO,PSSHAZH,PSSHAZD,PSSHAZTX)
VARIABLES: PSSDRIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   DRUG file (#50) ien.   (required) 
VARIABLES: PSSIO                        TYPE: Input
 VARIABLES DESCRIPTION:   "I" or "O" Inpatient or Outpatient package warning.  
 (required) 
VARIABLES: PSSHAZH                      TYPE: Input
 VARIABLES DESCRIPTION:   Hazardous to Handle flag (1 or 0).   (required) 
VARIABLES: PSSHAZD                      TYPE: Input
 VARIABLES DESCRIPTION:   Hazardous to Dispose flag (1 or 0).   (required) 
VARIABLES: PSSHAZTX                     TYPE: Output
 VARIABLES DESCRIPTION:   Hazardous warning text string returned containing
 drug name and related Hazardous To Handle and/or Hazardous Dispose disposition
 appropriate for the that was passed in package.  
COMPONENT/ENTRY POINT: HAZWARNG(PSSDRIEN,PSSIO,PSSHAZH,PSSHAZD,PSSHAZTX)

NUMBER: 6943                            IA #: 6943
  FILE NUMBER: 19640.32                 GLOBAL ROOT: DSIP(19640.32,
  DATE CREATED: JUL 11, 2018
  CUSTODIAL PACKAGE: VENDOR - DOCUMENT STORAGE SYS
  USAGE: Private                        TYPE: File
  NAME: CODER COMMENTS                  ID: DSIP(19640.32,
GLOBAL REFERENCE: DSIP(19640.32,D0,0)
FIELD NUMBER: .01                       FIELD NAME: VISIT IFN
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This ICR is just to see if there are any entries in the
 file for a given VISIT #.  It will use FileMan utilities for lookup.  
 GENERAL DESCRIPTION:   This agreement allows Integrated Billing (IB) to
 determine if there are any entries in the DSIP CODER COMMENT HISTORY
 (#19640.32) file for a VISIT IFN (#.01) field which is a pointer to the VISIT
 (#9000010) file.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: TAS
KEYWORDS: EBILLING
KEYWORDS: CODING COMPLETED
KEYWORDS: NO-TOUCH
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 6944                            IA #: 6944
  FILE NUMBER: 6910                     GLOBAL ROOT: DIC(6910)
  DATE CREATED: JUL 19, 2018            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ENG SITE PARAMETERS
  ID: DIC(6910)
GLOBAL REFERENCE: DIC(6910,D0,0)
FIELD NUMBER: .01                       FIELD NAME: STATION NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: STATION NUMBER
FIELD NUMBER: 1                         FIELD NAME: STATION NUMBER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TYPE OF 2237 FORM
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: DELETE PM WORK ORDERS
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PM HOURLY LABOR COST
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: TEMPORARY WORK ORDER
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: REGION
FIELD NUMBER: 6                         FIELD NAME: REGION
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: EQPT CAT ON BAR CODE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SPACE FUNCT ON LOCATION
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: MULT-DIVISION
FIELD NUMBER: 11                        FIELD NAME: MULTI-DIVISION
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: VISN
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: NEWORK
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 5.1                       FIELD NAME: INCOMING INSPECTION SECTION
  LOCATION: 0;13                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(6910.08,D0,0)
FIELD NUMBER: EQPT LABEL PRINT FILE
FIELD NUMBER: .01                       FIELD NAME: EQPT LABEL PRINT FILE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: LABEL
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(910.09,D0,0)
FIELD NUMBER: .01                       FIELD NAME: COMP LIST PRINT FIELD
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: LABEL
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(6910.01,D0,0)
FIELD NUMBER: .01                       FIELD NAME: WORK ORDER MESSAGE TYPE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(6910.012,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ALTERNATIVE STATION NUM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(6910,D0,9)
FIELD NUMBER: 100                       FIELD NAME: PROJECT PLANNING ROLL
  LOCATION: 9;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 101                       FIELD NAME: PROJECT TRACKING ROLL
  LOCATION: 9;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(6910,D0,20)
FIELD NUMBER: 20                        FIELD NAME: EQUIPMENT TURN-IN SEC2
  LOCATION: 20;1                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Above Par requests permission to read the ENG INIT
 PARAMETERS FILE #6910 to retrieve Engineering site parameters for view and use
 in Barcode printing, determining Shop Key value, and Station Number value.  
  
 Above PAR's Adhoc Reporting module includes ENG INIT PARAMETERS FILE (#6910)
 in the list of files and fields accesible from user defined reports.  
  STATUS: Active
KEYWORDS: ENGINERRING
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: AUG 16, 2018

NUMBER: 6945                            IA #: 6945
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,'B'
  DATE CREATED: JUL 27, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: LOOKUP USING B CROSS REFERENCE  ID: VA(200,'B'
GLOBAL REFERENCE: VA(200,'B',NAME)
FIELD NUMBER: .001                      FIELD NAME: INTERNAL ENTRY NUMBER
  LOCATION:                             ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Virtual Patient Record (VPR) application needs to
 be able to return the Internal Entry Number (IEN) of a user to the consuming
 applications (such as Joint Legacy Viewer). VPR has the user name, but not the
 IEN.  This ICR will grant them access to do a lookup on the 'B' cross
 reference of the NEW PERSON (#200) file.  
  STATUS: Pending
KEYWORDS: VA(200
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD

NUMBER: 6946                            IA #: 6946
  DATE CREATED: JUL 27, 2018            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  ROUTINE: SDMXCORE                     NAME: SDMXCORE
  ID: SDMXCORE
 GENERAL DESCRIPTION:   Core tags for MASS project.  
  STATUS: Pending
KEYWORDS: MASS
KEYWORDS: SDMXCORE
KEYWORDS: FMTPHONE
KEYWORDS: HL72VATS
KEYWORDS: INSTRING
KEYWORDS: VA2HL7TS
KEYWORDS: ESCINVLD
KEYWORDS: INCINTF
COMPONENT/ENTRY POINT: FMTPHONE
 COMPONENT DESCRIPTION:   Formats a VistA telephone number into an
 HL7-compliant format.  
VARIABLES: PHONE                        TYPE: Both
 VARIABLES DESCRIPTION:   Phone number to be formatted.  
VARIABLES: EXT                          TYPE: Output
 VARIABLES DESCRIPTION:   Phone number extension (if specified).  
COMPONENT/ENTRY POINT: HL72VATS
 COMPONENT DESCRIPTION:   Converts HL7 formatted timestamps to VA format.
 Returns formatted value.  
VARIABLES: HL7TS                        TYPE: Input
 VARIABLES DESCRIPTION:   Date/time stamp in 24H HL7 format (YYYYMMDDHHMMSS).  
COMPONENT/ENTRY POINT: INSTRING
 COMPONENT DESCRIPTION:   Compare a string value to see if it is a list given a
 particular delimiter.  
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   Value to find in the list.  
VARIABLES: LIST                         TYPE: Input
 VARIABLES DESCRIPTION:   The list to check.  
VARIABLES: DELIM                        TYPE: Input
 VARIABLES DESCRIPTION:   Delimiter that separates the data in the list.
 Default is ",".  
COMPONENT/ENTRY POINT: VA2HL7TS
 COMPONENT DESCRIPTION:   Converts VA formatted timestamps to HL7 format.
 Returns formatted value.  
VARIABLES: VATS                         TYPE: Input
 VARIABLES DESCRIPTION:   Date/time stamp in VA format (YYYMMDD.HHMMSS).  
COMPONENT/ENTRY POINT: ESCINVLD
 COMPONENT DESCRIPTION:   Escapes invalid ASCII characters in a single segment. 
 
VARIABLES: SEG                          TYPE: Both
 VARIABLES DESCRIPTION:   Segment array created by the HLO package.  
VARIABLES: ESC                          TYPE: Input
 VARIABLES DESCRIPTION:   String to replace unprintable characters with.  
COMPONENT/ENTRY POINT: INCINTF
 COMPONENT DESCRIPTION:   Checks temp global that indicates whether the process
 is filing an incoming message.  
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   MASS project interfacing with SD for common utilities.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 6947                            IA #: 6947
  DATE CREATED: JUL 27, 2018            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  ROUTINE: SDMXERRO                     NAME: SDMXERRO
  ID: SDMXERRO
 GENERAL DESCRIPTION:   Outgoing Error Interface tags.  
  STATUS: Pending
KEYWORDS: MASS
KEYWORDS: SDMXERRO
KEYWORDS: ERRLOG
COMPONENT/ENTRY POINT: ERRLOG
 COMPONENT DESCRIPTION:   Log an error to ^XERROR and optionally trigger error
 interface.  
VARIABLES: ERRORID                      TYPE: Input
 VARIABLES DESCRIPTION:   Numeric identifier for the error code.  
VARIABLES: ERRORTEXT                    TYPE: Input
 VARIABLES DESCRIPTION:   Error text explaining the issue.  
VARIABLES: SENDMSG                      TYPE: Input
 VARIABLES DESCRIPTION:   Set to 1 to trigger the error interface.  
SUBSCRIBING PACKAGE: REGISTRATION
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 6948                            IA #: 6948
  DATE CREATED: AUG 01, 2018            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGMXVLD                      NAME: DGMXVLD
  ID: DGMXVLD
 GENERAL DESCRIPTION:   Incoming HL7 message PID validation tags.  
  STATUS: Pending
KEYWORDS: MASS
KEYWORDS: DGMXVLD
KEYWORDS: VLDPAT
COMPONENT/ENTRY POINT: VLDPAT
 COMPONENT DESCRIPTION:   Validates patient information from an incoming HL7
 message. Returns '1' for valid, '0' for invalid.  
VARIABLES: PID                          TYPE: Input
 VARIABLES DESCRIPTION:   Contains the PID segment from the HL7 message (in
 standard HLO array).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   VistA Internal Entry Number (IEN).  
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 6949                            IA #: 6949
  DATE CREATED: AUG 01, 2018            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGMXHL7                      NAME: DGMXHL7
  ID: DGMXHL7
 GENERAL DESCRIPTION:   Tags for building HL7 messages to send to MASS.  
  STATUS: Pending
KEYWORDS: MASS
KEYWORDS: DGMXHL7
KEYWORDS: SETXCN
KEYWORDS: PID
COMPONENT/ENTRY POINT: SETXCN
 COMPONENT DESCRIPTION:   Sets and XCN field in an HLO message.  
VARIABLES: SEG                          TYPE: Output
 VARIABLES DESCRIPTION:   HLO segment.  
VARIABLES: USERID                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN.  
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   Field Number.  
COMPONENT/ENTRY POINT: PID
 COMPONENT DESCRIPTION:   Builds and HL7 PID segment.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN.  
VARIABLES: SEQ                          TYPE: Input
 VARIABLES DESCRIPTION:   Segment Index.  
VARIABLES: SEG                          TYPE: Output
 VARIABLES DESCRIPTION:   Segment Output.  
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 6950                            IA #: 6950
  DATE CREATED: AUG 01, 2018            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  ROUTINE: SDMXLKRQ                     NAME: SDMXLKRQ
  ID: SDMXLKRQ
 GENERAL DESCRIPTION:   Locking and Resequencing Tags.  
  STATUS: Pending
KEYWORDS: MASS
KEYWORDS: SDMXLKRQ
KEYWORDS: LOCKORD
KEYWORDS: ULOCKORD
COMPONENT/ENTRY POINT: LOCKORD
 COMPONENT DESCRIPTION:   Lock order.  
VARIABLES: ORDID                        TYPE: Input
 VARIABLES DESCRIPTION:   Order ID to lock.  
COMPONENT/ENTRY POINT: ULOCKORD
 COMPONENT DESCRIPTION:   Unlock Order.  
VARIABLES: ORDID                        TYPE: Input
 VARIABLES DESCRIPTION:   Order ID to unlock.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 6951                            IA #: 6951
  DATE CREATED: AUG 01, 2018
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORMXFMT                      NAME: ORMXFMT
  ID: ORMXFMT
 GENERAL DESCRIPTION:   Order formatting.  
  STATUS: Pending
KEYWORDS: MASS
KEYWORDS: ORMXFMT
KEYWORDS: TRANORCD
COMPONENT/ENTRY POINT: TRANORCD
 COMPONENT DESCRIPTION:   Translates a file string to its HLO order type code
 and visa-versa.  
VARIABLES: DIRECT                       TYPE: Input
 VARIABLES DESCRIPTION:   Message direction (outgoing).  
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   The type of order.  
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 6952                            IA #: 6952
  DATE CREATED: AUG 01, 2018
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORMXTR                       NAME: ORMXTR
  ID: ORMXTR
 GENERAL DESCRIPTION:   HL7 order message triggering.  
  STATUS: Pending
KEYWORDS: MASS
KEYWORDS: ORMXTR
KEYWORDS: TRUPDMSG
KEYWORDS: TRGMRMSG
KEYWORDS: TRCPMSG
COMPONENT/ENTRY POINT: TRUPDMSG
 COMPONENT DESCRIPTION:   Triggers an "XO" ORM messages for consults.  
VARIABLES: GMRIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   The consult ID.  
COMPONENT/ENTRY POINT: TRGMRMSG
 COMPONENT DESCRIPTION:   Entry point for triggering any (i.e. "NW","XO","CA")
 ORM messages for consults.  
VARIABLES: CNTLLIST                     TYPE: Input
 VARIABLES DESCRIPTION:   Set to a list of specific control codes (i.e. "NW",
 "XO", "NW,CA") you want to trigger a message for.  
COMPONENT/ENTRY POINT: TRCPMSG
 COMPONENT DESCRIPTION:   Entry point for triggering any (i.e. "NW","XO","CA")
 ORM messages for C&P requests.  
VARIABLES: CNTLLIST                     TYPE: Input
 VARIABLES DESCRIPTION:   Set to a list of specific control codes (i.e. "NW",
 "XO", "NW,CA") you want to trigger a message for.  
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE

NUMBER: 6953                            IA #: 6953
  DATE CREATED: AUG 03, 2018
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXAPI
  NAME: PROVIDER NARRATIVE API          ID: PXAPI
  STATUS: Active
KEYWORDS: PROVIDER NARRATIVE API
COMPONENT/ENTRY POINT: $$PROVNARR
 COMPONENT DESCRIPTION:   $$PROVNARR^PXAPI(PXPNAR,PXFILE,PXCLEX) This API
 provides a laygo function for Provider Narrative. It returns IEN^Provider
 Narrative text.  
  
VARIABLES: PXPNAR                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the text of the Provider Narrative, the
 length is 2-245 characters. 
  
VARIABLES: PXFILE                       TYPE: Input
 VARIABLES DESCRIPTION:   This field is used to identify what file pointing to
 the Provider Narrative file created the entry in the Provider Narrative file.  
  
VARIABLES: PXCLEX                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the Clinical Expression related to the
 provider narrative. It is optional.  
  
SUBSCRIBING PACKAGE: PROBLEM LIST
 SUBSCRIBING DETAILS:   With regards to Provider Narrative, Problem List needs
 the same functionality as PCE and that is a laygo function that will return
 the internal entry number for an existing Provider Narrative or add a new one.
 The best way to do that is via the same API PCE uses.  
  
  DATE ACTIVATED: AUG 06, 2018

NUMBER: 6954                            IA #: 6954
  FILE NUMBER: 9000010                  GLOBAL ROOT: AUPNVSIT(D0,812
  DATE CREATED: AUG 10, 2018
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  NAME: DBIA 6954                       ID: AUPNVSIT(D0,812
GLOBAL REFERENCE: AUPNVSIT(D0,812
FIELD NUMBER: 81203                     FIELD NAME: DATA SOURCE
  LOCATION: 812;3                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   This is a pointer to the PCE DATA SOURCE file and is the
 source that wanted the visit created.  
 GLOBAL DESCRIPTION:   VISIT file (#9000010) 
 GENERAL DESCRIPTION:   VIA requests the ability to update the DATA SOURCE
 field (#81203) of the VISIT file (#9000010).  
  
 A CPRS RPC is used to create and sign a new note which defines the data source
 as TIU.  Then an update is sent to add note information with the actual data
 source as part of the data. PCE keeps the original data source unless there is
 a change in the patient's location.  VIA requests to update the DATA SOURCE
 field with the calling application at the time the update to the note is sent. 
 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: SOURCE
KEYWORDS: DATA SOURCE
KEYWORDS: AUPNVSIT
KEYWORDS: VISIT
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6955                            IA #: 6955
  DATE CREATED: AUG 10, 2018
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  ROUTINE: PXAPIUTL                     NAME: DBIA 6955
  ID: PXAPIUTL
 GENERAL DESCRIPTION:   VIA requests this ICR to utilize SOURCE^PXAPIUTL to add
 a new source if not previously defined.  
  
 As part of adding progress notes, a CPRS RPC is used to create and sign a new
 note which defines the data source as TIU. Then an update is sent to add note
 information with the actual data source as part of the data. PCE keeps the
 original data source unless there is a change in the patient's location.  VIA
 requests to call SOURCE^PXAPIUTL to add a new source if update to the note is
 sent.  
  
 This ICR will be utilized in conjunction with DBIA 6954.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: SOURCE
KEYWORDS: PXAPIUTL
COMPONENT/ENTRY POINT: SOURCE
VARIABLES: PXASOURC                     TYPE: Input
 VARIABLES DESCRIPTION:   New data source.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR

NUMBER: 6956                            IA #: 6956
  FILE NUMBER: 19.1                     GLOBAL ROOT: DIC(19.1
  DATE CREATED: AUG 15, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: Security Key Description        ID: DIC(19.1
GLOBAL REFERENCE: DIC(19.1,D0,1,D1,0)
FIELD NUMBER: 1                         FIELD NAME: DESCRIPTION
  LOCATION: 1;0                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The ORDER ENTRY/RESULTS REPORTING package requests read
 access to the Description field of the Security Key file. 
  STATUS: Pending
KEYWORDS: SECURITY KEY
KEYWORDS: DESCRIPTION
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 6957                            IA #: 6957
  DATE CREATED: AUG 20, 2018
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Remote Procedure
  NAME: NEED TO SIGN DOCUMENT?
 GENERAL DESCRIPTION:   This RPC checks to see if the current user needs to
 sign the passed-in document IEN.  
  STATUS: Pending
KEYWORDS: TIUSRVA
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   This RPC checks to see if the current user needs to
 sign the passed-in document IEN.  

NUMBER: 6958                            IA #: 6958
  DATE CREATED: AUG 31, 2018            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCFACP
  NAME: RETREIVE NEXT COUNTER NUMBER FILE 422.2
  ID: PRCFACP
 GENERAL DESCRIPTION:   This integration agreement allows the ABOVE  PAR
 package to call COUNTER^PRCFACP to retrieve next Counter number from file
 COUNTER (422.2).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: COUNTER
 COMPONENT DESCRIPTION:   Module COUNTER will create a COUNTER entry to support
 the FMS VENDOR REQUEST if the COUNTER NAME (.01) is not defined.  Module
 COUNTER will increment the COUNTER field COUNTER (1).  
  
 Returns Y,  the incremented counter number.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   Counter Name 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Counter value incremented by 1 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: NOV 01, 2018

NUMBER: 6959                            IA #: 6959
  FILE NUMBER: 2006.5831                GLOBAL ROOT: MAG(2006.5831,
  DATE CREATED: SEP 07, 2018            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CP CONVERSION UTILITY
  ID: MAG(2006.5831,
GLOBAL REFERENCE: MAG(2006.5831,D0,0
FIELD NUMBER: 2                         FIELD NAME: PROCEDURE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: MAG(2006.5831,'C'
GLOBAL REFERENCE: MAG(2006.5831,'B'
 GENERAL DESCRIPTION:   Clinical Procedures requires read access to the
 CLINICAL SPECIALTY DICOM & HL7 file (#2006.5831) to screen for consults or
 procedures setup in DICOM. The screen is on the interactive lookup for
 consults or procedures that are being selected to convert to Clinical
 Procedures.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MD*1.0*65
KEYWORDS: 2006.5831
SUBSCRIBING PACKAGE: CLINICAL PROCEDURES
  DATE ACTIVATED: DEC 03, 2018

NUMBER: 6960                            IA #: 6960
  FILE NUMBER: 6910.2                   GLOBAL ROOT: ENG(6910.2)
  DATE CREATED: SEP 11, 2018            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  NAME: ENG SOFTWARE OPTIONS            ID: ENG(6910.2)
GLOBAL REFERENCE: ENG(6910.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: FEATURE NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: SELECTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: REFERENCE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: ENG(6910.2,D0,1,D1)
FIELD NUMBER: .01                       FIELD NAME: CHOICES
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Above Par requests permission to read the ENG SOFTWARE
 OPTIONS (#6910.2) to retrieve information governing the performance of
 options.  
  
 Above PAR's Adhoc Reporting module includes ENG SOFTWARE OPTIONS (#6910.2) in
 the list of files and fields accessible from user defined reports.  
  STATUS: Pending
KEYWORDS: ABOVE PAR
KEYWORDS: ENGINEERING
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 6961                            IA #: 6961
  DATE CREATED: SEP 12, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: XU EPCS ADD DEA                 REMOTE PROCEDURE: XU EPCS ADD DEA
  ORIGINAL NUMBER: 6961
 GENERAL DESCRIPTION:   This RPC is designed to work with the EPCS GUI
 application for editing provider DEA information for pharmacy.  It will accept
 inputs of a IEN for the NEW PERSON FILE #200 and a "^" delimited line of text
 to be recorded.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 6962                            IA #: 6962
  DATE CREATED: SEP 12, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: XU EPCS DEADOJ                  REMOTE PROCEDURE: XU EPCS DEADOJ
  ORIGINAL NUMBER: 6961
 GENERAL DESCRIPTION:   This RPC call, accepts a DEA Number as input. It calls
 the DOJ/DEA Web Service to get the most recent information for the provider
 which is returned to the calling program in a single string with "^" delimited 
 data. The values in the string are: 
            1 - PROVIDER NAME 
            2 - ADDRESS 1 
            3 - ADDRESS 2 
            4 - ADDRESS 3 
            5 - CITY 
            6 - STATE 
            7 - STATE POINTER 
            8 - ZIP CODE 
            9 - ACTIVITY CODE 
           10 - TYPE 
           11 - DEA NUMBER 
           12 - EXPIRATION DATE 
           13 - PROCESSED DATE 
           14 - DETOX NUMBER 
           15 - SCHDEULE II NARCOTIC 
           16 - SCHEDULE II NON-NARCOTIC 
           17 - SCHEDULE III NARCOTIC 
           18 - SCHEDULE III NON-NARCOTIC 
           19 - SCHEDULE IV 
           20 - SCHEDULE V 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: EPCS GUI
KEYWORDS: DOJ/DEA
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 6963                            IA #: 6963
  DATE CREATED: SEP 12, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: XU EPCS REMOVE DEA              REMOTE PROCEDURE: XU EPCS REMOVE DEA
  ORIGINAL NUMBER: 6961
 GENERAL DESCRIPTION:   
  Functionality to remove a DEA multiple from file #200, Field 53.21 
    INPUT:  NPIEN - NEW PERSON FILE #200 INTERNAL ENTRY NUMBER 
            DEATXT - PROPERLY FORMATTED DEA NUMBER 
    OUTPUT: RET - 1 for SUCCESS, 0 for UNSUCCESSFUL 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   CPRS allows providers to enter the subject alternative
 name from their PIV card once; subsequent edits are accomplished through
 software provided by KERNEL.  

NUMBER: 6964                            IA #: 6964
  DATE CREATED: SEP 12, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: XU EPCS DEA DUP CHECK           REMOTE PROCEDURE: XU EPCS DEA DUP CHECK
  ORIGINAL NUMBER: 6961
 GENERAL DESCRIPTION:   
  This RPC will accept a DEA in text format, and an institutional suffix if
 available.  It will perform checking to determine if the DEA is being used by
 another user.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   
  CPRS allows providers to enter the subject alternative name from their PIV
 card once; subsequent edits are accomplished through software provided by
 KERNEL.  

NUMBER: 6965                            IA #: 6965
  DATE CREATED: SEP 14, 2018            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PSJHL5
  NAME: Access to ACTIVITY LOG of File 53.1
  ID: PSJHL5
 GENERAL DESCRIPTION:   When a unique IEN into File #53.1 (NON-VERIFIED ORDERS)
 is sent into this API, then it should return a local array which holds all of
 the ACTIVITY LOG information for the associated record.  
  STATUS: Withdrawn
KEYWORDS: NON-VERIFIED ORDERS
KEYWORDS: ACTIVITY LOG
COMPONENT/ENTRY POINT: AARRGET
 COMPONENT DESCRIPTION:   The AARRGET component of the PSJHL5 routine will take
 PSIFN value (which is the unique IEN into File #53.1) and pull back into local
 array PSAARR the ACTIVITY LOG multiple information that is available or not.  
VARIABLES: PSIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Unique IEN into File #53.1 (NON-VERIFIED ORDERS).  
VARIABLES: PSAARR                       TYPE: Output
 VARIABLES DESCRIPTION:   The local array returned which holds all of the
 ACTIVITY LOG multiple information for the record.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 6966                            IA #: 6966
  DATE CREATED: SEP 19, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: XU EPCS MBM                     REMOTE PROCEDURE: XU EPCS MBM
 GENERAL DESCRIPTION:   This RPC is provided to ePCS GUI to check if the site
 is setup for Meds by Mail service.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   CPRS allows providers to enter the subject alternative
 name from their PIV card once; subsequent edits are accomplished through
 software provided by KERNEL.  

NUMBER: 6967                            IA #: 6967
  DATE CREATED: SEP 19, 2018
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORDEA ZIP                       REMOTE PROCEDURE: ORDEA ZIP
 GENERAL DESCRIPTION:   This remote procedure call will confirm if the patient
 has a valid zip code entered.  This information is being verified before a
 provider is able to prescribe a controlled substance.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   
  CPRS allows providers to enter the subject alternative name from their PIV
 card once; subsequent edits are accomplished through software provided by
 KERNEL.  

NUMBER: 6968                            IA #: 6968
  DATE CREATED: SEP 19, 2018
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: XU EPCS DEALIST                 REMOTE PROCEDURE: XU EPCS DEALIST
 GENERAL DESCRIPTION:   This remote procedure call will provide a list of
 active DEA #s for a provider during Outpatient Pharmacy controlled substances
 order entry. If there is more than one then the provider will be presented
 with the list to select one, which will be associated to that order.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   
  CPRS allows providers to enter the subject alternative name from their PIV
 card once; subsequent edits are accomplished through software provided by
 KERNEL.  

NUMBER: 6969                            IA #: 6969
  DATE CREATED: SEP 19, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: XUEPCSME                     NAME: XUEPCSME
  ID: XUEPCSME
 GENERAL DESCRIPTION:   The XUEPCSME routine provides functionality to retrieve
 information from the DOJ/DEA web service and use a ListMan screen to enable
 the Pharmacy to edit the information and link it to a provider in the NEW
 PERSON FILE #200 and save the information to the DEA NUMBERS FILE #8991.9.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DEA
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   A complex application for editing the DEA information
 in the DEA NUMBERS FILE #8991.9 and associating that information with a
 provider in the NEW DEA NUMBER #53.21 multiple of the NEW PERSON FILE #200.  
VARIABLES: DEA                          TYPE: Input
 VARIABLES DESCRIPTION:   DEA NUMBER IN TEXT FORMAT.  
VARIABLES: IEN                          TYPE: Output
 VARIABLES DESCRIPTION:   The IEN of the DEA information stored in the DEA
 NUMBERS FILE #8991.9.  
COMPONENT/ENTRY POINT: WSGET
 COMPONENT DESCRIPTION:   This function makes a web service call to the DOJ/DEA
 web service and returns the response data in a MUMPS global.  
VARIABLES: DEA                          TYPE: Input
 VARIABLES DESCRIPTION:   DEA number properly formatted.  
VARIABLES: FG                           TYPE: Output
 VARIABLES DESCRIPTION:   An array listing of the web service supplied data.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 6970                            IA #: 6970
  DATE CREATED: SEP 19, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: XUEPCSUT                     NAME: XUEPCSUT 
  ID: XUEPCSUT
 GENERAL DESCRIPTION:   An algorithm to validate that the DEA number is
 formatted correctly.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DEA
COMPONENT/ENTRY POINT: DEANUM
 COMPONENT DESCRIPTION:   An algorithm to validate that the DEA number is
 formatted correctly.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   DEA number in Text format.  
VARIABLES: RETURN                       TYPE: Output
 VARIABLES DESCRIPTION:   0 = Not formatted correctly, 1 = Formatted correctly. 
 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 6971                            IA #: 6971
  DATE CREATED: SEP 19, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: XUEPCSED                     NAME: XUEPCSED
  ID: XUEPCSED
 GENERAL DESCRIPTION:   Returns a value in the RET variable indicating the
 Meds-by-Mail System setting.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: MBM
KEYWORDS: MEDS BY MAIL
KEYWORDS: EPCS
COMPONENT/ENTRY POINT: MBM
 COMPONENT DESCRIPTION:   Returns a value in the RET variable indicating the
 Meds-by-Mail System setting.  
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   Returns the value of the Meds-by-Mail system setting. 
 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 6972                            IA #: 6972
  DATE CREATED: SEP 19, 2018
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA6972
  STATUS: Pending

NUMBER: 6973                            IA #: 6973
  FILE NUMBER: 120.8                    GLOBAL ROOT: GMR(120.8)
  DATE CREATED: SEP 26, 2018
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PATIENT ALLERGIES file data
  ID: GMR(120.8)
GLOBAL REFERENCE: GMR(120.8,D0,0)
FIELD NUMBER: 5                         FIELD NAME: ORIGINATOR
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 21                        FIELD NAME: VERIFIER
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: GMR(120.8,D0,'ER')
FIELD NUMBER: 24                        FIELD NAME: USER ENTERING IN ERROR
  LOCATION: ER;3                        ACCESS: Direct Global 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: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: USER ENTERING
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1.5                       FIELD NAME: COMMENT TYPE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Includes use of the AVER index to find entered in error
 comments 
FIELD NUMBER: 2                         FIELD NAME: COMMENTS
  LOCATION: 2;0                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Word-processing text 
 GENERAL DESCRIPTION:   This documents data that VPR is reading from the
 Patient Allergies file #120.8, in addition to the use of other supported
 api's.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: SEP 28, 2018

NUMBER: 6974                            IA #: 6974
  FILE NUMBER: 120.82                   GLOBAL ROOT: GMRD(120.82)
  DATE CREATED: SEP 26, 2018
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: GMR ALLERGIES CODING SYSTEMS
  ID: GMRD(120.82)
GLOBAL REFERENCE: GMRD(120.82,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CODING SYSTEM
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: GMRD(120.82,D0,1,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This agreement allows access to the national codes
 pushed out to the GMR Allergies file #120.82 by the Native Domain
 Standardization (NDS) team.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: SEP 28, 2018

NUMBER: 6975                            IA #: 6975
  FILE NUMBER: 120.83                   GLOBAL ROOT: GMRD(120.83)
  DATE CREATED: SEP 26, 2018
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SIGNS/SYMPTOMS CODING SYSTEMS
  ID: GMRD(120.83)
GLOBAL REFERENCE: GMRD(120.83,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CODING SYSTEM
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: GMRD(120.83,D0,1,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This agreement allows access to the national codes
 pushed out to the Sign/Symptoms file #120.83 by the Native Domain
 Standardization (NDS) team.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: SEP 28, 2018

NUMBER: 6976                            IA #: 6976
  FILE NUMBER: .402                     GLOBAL ROOT: DIC
  DATE CREATED: SEP 27, 2018            CUSTODIAL PACKAGE: 1
  USAGE: Controlled Subscription        TYPE: File
  NAME: DELETION OF INPUT TEMPLATES     ID: DIC
 GENERAL DESCRIPTION:   This integration agreement covers the deletion of input
 templates used with patch DG*5.3*914 for Camp Lejeune.  The pre-init routine
 DGPR914 will loop through a list of input templates used for the project Camp 
 Lejeune and delete them.  Upon installation of patch DG*5.3*914, all input
 templates will be automatically recompiled.  
  
 Deletion of input templates will involve the following: 
  
 1. Using $$FIND1^DIC(.402,"","MX","INPUT TEMPLATE NAME") to get the Input 
 Template IEN from file #.402.  
  
 2. Using ^DIK to delete the input template from file #.402.  
  STATUS: Pending
KEYWORDS: PTF
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 6977                            IA #: 6977
  DATE CREATED: OCT 10, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS MVI NEW PERSON DATA
  REMOTE PROCEDURE: XUS MVI NEW PERSON DATA
 GENERAL DESCRIPTION:   The Master Veteran Index (MVI) team requests permission
 to use the following KERNEL Remote Procedure Call (RPC) [XUS MVI NEW PERSON
 DATA], which will allow the MVI system to retrieve the following '^' delimited
 aggregated data for Active and/or Non-Active NEW PERSON file (#200) entries
 from a 'specific' or 'all' active VistA site(s) if requested: 
  
      - Number of ALL Record types found 
      - Number of Non-Active Records 
      - Number of Active Records 
      - Number of Active Records containing a SECID 
      - Number of Active Records containing an Email 
      - Number of Active Records containing an Network Username 
      - Number of Visitor Records 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XUS MVI NEW PERSON DATA
KEYWORDS: 200
KEYWORDS: VA(200
KEYWORDS: MVI
KEYWORDS: MPI
KEYWORDS: XUMVIDTA
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   The Master Veteran Index (MVI) project will use this 
 Remote Procedure Call (RPC) to allow retrieval of aggregated user data
 statistics from the NEW PERSON file (#200) for analysis beginning with patch 
 MPI*1.0*124.  
  DATE ACTIVATED: OCT 11, 2018

NUMBER: 6978                            IA #: 6978
  FILE NUMBER: 2.98                     GLOBAL ROOT: DPT(DFN,'S'
  DATE CREATED: OCT 22, 2018            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VPR ACCESS TO APPOINTMENTS
  ID: DPT(DFN,'S'
GLOBAL REFERENCE: DPT(D0,'S',D1,0)
FIELD NUMBER: 19                        FIELD NAME: DATA ENTRY CLERK
  LOCATION: 0;18                        ACCESS: Read w/Fileman
FIELD NUMBER: 20                        FIELD NAME: DATE APPT. MADE
  LOCATION: 0;19                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This agreement allows VPR to access fields in the
 APPOINTMENT sub-file #2.98 that are not provided by the supported Scheduling
 APIs. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: OCT 26, 2018

NUMBER: 6979                            IA #: 6979
  FILE NUMBER: 440.3                    GLOBAL ROOT: PRC(440.3
  DATE CREATED: OCT 22, 2018            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VENDOR EDIT FILE ACCESS
  ID: PRC(440.3
GLOBAL REFERENCE: PRC(440,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ORDERING ADDRESS1
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ORDERING ADDRESS2
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: ORDERING ADDRESS3
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: ORDERING ADDRESS4
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.2                       FIELD NAME: ORDERING CITY
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.4                       FIELD NAME: ORDERING STATE
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.6                       FIELD NAME: ORDERING ZIP CODE
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.8                       FIELD NAME: PROCUREMENT CONTACT PERSON
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: VA P&C contact phone number
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05                       FIELD NAME: SUPPLY WHSE. INDICATOR
  LOCATION: 0;11                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,.11)
FIELD NUMBER: 22.1                      FIELD NAME: BILLING ADDRESS1
  LOCATION: .11;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 22.2                      FIELD NAME: BILLING ADDRESS2
  LOCATION: .11;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 22.3                      FIELD NAME: BILLING ADDRESS3
  LOCATION: .11;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 22.4                      FIELD NAME: BILLING CITY
  LOCATION: .11;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 22.5                      FIELD NAME: BILLING STATE
  LOCATION: .11;5                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 22.6                      FIELD NAME: BILLING ZIP CODE
  LOCATION: .11;6                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 22.7                      FIELD NAME: BILLING PHONE NUMBER
  LOCATION: .11;7                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,1,D1)
FIELD NUMBER: .01                       FIELD NAME: TYPE OF OWNERSHIP (FY88)
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,1.1,D1)
FIELD NUMBER: .01                       FIELD NAME: SOCIOECONOMIC GROUP (FPDS)
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,2)
FIELD NUMBER: 5.1                       FIELD NAME: ACCOUNT NO.
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: FEDERAL SOURCE
  LOCATION: 2;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.3                       FIELD NAME: BUSINESS TYPE (FPDS)
  LOCATION: 2;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.7                       FIELD NAME: COUNTY
  LOCATION: 2;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8                         FIELD NAME: LABOR SURPLUS AREA?
  LOCATION: 2;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.2                       FIELD NAME: BUSINESS TYPE (FPDS-88)
  LOCATION: 2;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13                        FIELD NAME: IS A SF129 ON FILE?
  LOCATION: 2;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: DATE OF SF129
  LOCATION: 2;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.4                      FIELD NAME: AUSTIN DELETED?
  LOCATION: 2;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.5                      FIELD NAME: FEE VENDOR
  LOCATION: 2;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.2                       FIELD NAME: GUARANTEED DELIVERY VENDOR?
  LOCATION: 2;11                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,3)
FIELD NUMBER: 11                        FIELD NAME: SPECIAL FACTORS
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .2                        FIELD NAME: EDI VENDOR?
  LOCATION: 3;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .4                        FIELD NAME: VENDOR ID NUMBER
  LOCATION: 3;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 34                        FIELD NAME: FMS VENDOR CODE
  LOCATION: 3;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 35                        FIELD NAME: ALT-ADDR-IND
  LOCATION: 3;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 36                        FIELD NAME: NON-RECURRING VENDOR
  LOCATION: 3;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 38                        FIELD NAME: TAX ID/SSN
  LOCATION: 3;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 39                        FIELD NAME: SSN/TAX ID INDICATOR
  LOCATION: 3;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 40                        FIELD NAME: PAYMENT HOLD INDICATOR
  LOCATION: 3;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 41                        FIELD NAME: 1099 VENDOR INDICATOR
  LOCATION: 3;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 42                        FIELD NAME: PENDING FLAG
  LOCATION: 3;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 43                        FIELD NAME: CENTRAL REMIT
  LOCATION: 3;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 44                        FIELD NAME: VENDOR TYPE
  LOCATION: 3;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 45                        FIELD NAME: MTI ACTION
  LOCATION: 3;15                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,4,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CONTRACT NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: EXPIRATION DATE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PROMPT PAYMENT TERMS %
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PROMPT PAYMENT TERM DAYS
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,4,D1,1)
FIELD NUMBER: 2                         FIELD NAME: CONTRACT TERMS
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,5,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SYNONYM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,6)
FIELD NUMBER: 16                        FIELD NAME: SERVICE/RETURN ADDRESS1
  LOCATION: 6;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16.1                      FIELD NAME: SERVICE/RETURN ADDRESS2
  LOCATION: 6;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16.2                      FIELD NAME: SERVICE/RETURN ADDRESS3
  LOCATION: 6;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16.3                      FIELD NAME: SERVICE/RETURN ADDRESS4
  LOCATION: 6;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16.4                      FIELD NAME: SERVICE/RETURN CITY
  LOCATION: 6;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16.5                      FIELD NAME: SERVICE/RETURN STATE
  LOCATION: 6;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16.6                      FIELD NAME: SERVICE/RETURN ZIP CODE
  LOCATION: 6;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16.7                      FIELD NAME: SERVICE CONTACT PERSON
  LOCATION: 6;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 16.8                      FIELD NAME: SERVICE PHONE NO.
  LOCATION: 6;9                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,7)
FIELD NUMBER: 17                        FIELD NAME: PAYMENT CONTACT PERSON
  LOCATION: 7;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.2                      FIELD NAME: PAYMENT PHONE NO.
  LOCATION: 7;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.3                      FIELD NAME: PAYMENT ADDRESS1
  LOCATION: 7;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.4                      FIELD NAME: PAYMENT ADDRESS2
  LOCATION: 7;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.5                      FIELD NAME: PAYMENT ADDRESS3
  LOCATION: 7;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.6                      FIELD NAME: PAYMENT ADDRESS4
  LOCATION: 7;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.7                      FIELD NAME: PAYMENT CITY
  LOCATION: 7;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.8                      FIELD NAME: PAYMENT STATE
  LOCATION: 7;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17.9                      FIELD NAME: PAYMENT ZIP CODE
  LOCATION: 7;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 18                        FIELD NAME: CALM ID NUMBER
  LOCATION: 7;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 18.2                      FIELD NAME: CALM STUB NAME
  LOCATION: 7;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 18.3                      FIELD NAME: DUN & BRADSTREET #
  LOCATION: 7;12                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,8,D1,0)
FIELD NUMBER: .01                       FIELD NAME: REMARKS
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,9)
FIELD NUMBER: 15                        FIELD NAME: REPLACEMENT VENDOR
  LOCATION: 9;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,10)
FIELD NUMBER: 30                        FIELD NAME: DATE VENDOR CREATED
  LOCATION: 10;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 31                        FIELD NAME: CREATED BY
  LOCATION: 10;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 32                        FIELD NAME: DATE INACTIVATED
  LOCATION: 10;3                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 33                        FIELD NAME: INACTIVATED BY
  LOCATION: 10;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 31.5                      FIELD NAME: INACTIVATED VENDOR
  LOCATION: 10;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 46                        FIELD NAME: FAX#
  LOCATION: 10;6                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,'AR')
FIELD NUMBER: 50                        FIELD NAME: FLAG AR
  LOCATION: AR;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 51                        FIELD NAME: VENDOR RECORD - AR
  LOCATION: AR;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 52                        FIELD NAME: SITE AR
  LOCATION: AR;3                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 53                        FIELD NAME: OK 
  LOCATION: AR;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 54                        FIELD NAME: SENT
  LOCATION: AR;5                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,D0,'VRQ')
FIELD NUMBER: 47                        FIELD NAME: FLAG
  LOCATION: VRQ;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 48                        FIELD NAME: VENDOR RECORD
  LOCATION: VRQ;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 49                        FIELD NAME: SITE
  LOCATION: VRQ;3                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: PRC(440.3,'B'
 GLOBAL DESCRIPTION:   "B" cross reference - used to search by Vendor Name.  
 GENERAL DESCRIPTION:   Consistent with IFCAP, Above PAR calls XY^%RCR to
 back-up the current Vendor entry in file (#440) into a corresponding entry in
 file (#440.3) so that if the user decides to cancel the update, the original
 values can be restored.  
  
 Above PAR deletes the VENDOR EDIT entry when the user confirms that a
 verification needs to be sent to Austin.  
  STATUS: Active
KEYWORDS: IFCAP
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUN 07, 2019

NUMBER: 6980                            IA #: 6980
  DATE CREATED: OCT 23, 2018            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOUTL
  NAME: TITRATION API                   ID: PSOUTL
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TITRATION
KEYWORDS: MAINTENANCE
KEYWORDS: PSOUTL
COMPONENT/ENTRY POINT: $$TITRX
 COMPONENT DESCRIPTION:   Returns a "t" if this prescription is a Titration
 Dose RX.  Returns a "m" if this prescription is a Maintenance Dose RX that was 
 copied from a titrating RX.  Returns "" otherwise.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   This is the PRESCRIPTION (#52) IEN.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   The OR*3*405 post-install will update the Order (#100)
 entry for any outpatient RX marked as titrating. The TITRX^PSOUTL API will be 
 used to determine if it is a titrating RX.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 6/6/19 so VPR provide Custom Services to the
 Pharmacy Advanced Medication Platform (AMPL) GUI project for prescription
 display information. Effective with VPR*1*14.  
  DATE ACTIVATED: FEB 11, 2019

NUMBER: 6981                            IA #: 6981
  FILE NUMBER: 100.045                  GLOBAL ROOT: OR(100,D0,4.5)
  DATE CREATED: OCT 24, 2018
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RESPONSES MULTIPLE
  ID: OR(100,D0,4.5)
GLOBAL REFERENCE: OR(100,D0,4.5,D1,0)
FIELD NUMBER: .02                       FIELD NAME: DIALOG
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: INSTANCE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: ID 
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Includes use of "ID" cross reference 
GLOBAL REFERENCE: OR(100,D0,4.5,D1,1)
FIELD NUMBER: 1                         FIELD NAME: VALUE
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: OR(100,D0,4.5,D1,2,D2,0)
FIELD NUMBER: .01                       FIELD NAME: TEXT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   lines of word-processing text 
 GENERAL DESCRIPTION:   This agreement documents VPR access to the Responses
 multiple of the Orders file #100.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Added 3/12/25, effective with PSJ*5.0*453, the Order
 file Responses global references will be captured in an HL7 order file to be
 sent to the Methadone vendor. Fields in Order File #100 listed in this ICR
 will be used. This supports the Methadone Dispensing Tracking Project to help 
 manage dispensing and monitoring of Medications for Opioid Use Disorder for
 veterans participating in an Opioid Treatment Program (OTP).  
  DATE ACTIVATED: NOV 19, 2018

NUMBER: 6982                            IA #: 6982
  FILE NUMBER: 100.98                   GLOBAL ROOT: ORD(100.98)
  DATE CREATED: OCT 24, 2018
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VPR USE OF DISPLAY GROUPS
  ID: ORD(100.98)
GLOBAL REFERENCE: ORD(100.98,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: SHORT NAME
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   Includes use of the B cross reference 
 GENERAL DESCRIPTION:   This agreements document VPR access to the Display
 Group file #100.98.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: NOV 19, 2018

NUMBER: 6983                            IA #: 6983
  DATE CREATED: OCT 24, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  NAME: TEXT XU REM
 GENERAL DESCRIPTION:   This is just for test.  
  STATUS: Pending
KEYWORDS: XU REM
SUBSCRIBING PACKAGE: RPC BROKER
 SUBSCRIBING DETAILS:   TESTING 

NUMBER: 6984                            IA #: 6984
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: OCT 25, 2018            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PATIENT FILE
  ID: DPT(
GLOBAL REFERENCE: DPT('CN', CN cross reference
 GENERAL DESCRIPTION:   BAR CODE MED ADMIN package (namespace PSB) would like
 to request Direct Global read access to cross reference 'CN' in the Patient
 file (#2) for reporting purposes. Basically the use is to $O through the 'CN'
 cross  reference to get patients and wards to be displayed via a report in the
 patch PSB*3.0*103.  
  STATUS: Active
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
  DATE ACTIVATED: NOV 13, 2018

NUMBER: 6985                            IA #: 6985
  FILE NUMBER: 702                      GLOBAL ROOT: MDD(702)
  DATE CREATED: OCT 26, 2018            CUSTODIAL PACKAGE: CLINICAL PROCEDURES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CP TRANSACTIONS DATA
  ID: MDD(702)
GLOBAL REFERENCE: MDD(702,D0,0)
FIELD NUMBER: .02                       FIELD NAME: CREATED DATE/TIME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: CREATED BY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: MDD(702,D0,.1,D1,0)
FIELD NUMBER: .09                       FIELD NAME: STATUS
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This agreement documents VPR access to fields in the CP
 Transactions file #702 that are not available via other api's.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: OCT 31, 2018

NUMBER: 6986                            IA #: 6986
  DATE CREATED: OCT 29, 2018
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: GMRA ASSESSMENT CHANGE
 GENERAL DESCRIPTION:   This extended action protocol is activated whenever
 there is a change in a patient's adverse reaction assessment. The following
 variable is defined when the protocol is activated: 
  
       GMRAL = Internal Entry Number (IEN) in the ADVERSE REACTION 
               ASSESSMENT file (#120.86) 
    GMRAL(0) = Contents of the FileMan X(order#) array in the new-style 
               AHDR cross-reference, flattened. Each caret piece number of 
               this node is populated from the corresponding subscript in 
               the X(order#) array. For example, piece 1 is populated from 
               the X(1) node and piece 4 is populated from the X(4) node.  
               Note: Reference the data dictionary for the ADVERSE 
               REACTION ASSESSMENT file (#120.86) for a listing of the 
               fields included in the AHDR cross-reference. Note that all 
               pieces are in internal format.  
  STATUS: Active
KEYWORDS: ALLERGY ASSESSMENT CHANGE
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: NOV 05, 2018

NUMBER: 6987                            IA #: 6987
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55
  DATE CREATED: NOV 08, 2018
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Controlled Subscription        TYPE: File
  NAME: PHARMACY PATIENT (#55) FILE     ID: PS(55
GLOBAL REFERENCE: PS(55
 GENERAL DESCRIPTION:   The Outpatient Pharmacy and CMOP packages request full
 access to the PHARMACY PATIENT (#55) file. 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.  
  
 This integration agreement replaces IA #2228.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: PSO
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: CMOP

NUMBER: 6988                            IA #: 6988
  DATE CREATED: NOV 14, 2018
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORCSAVE2                     NAME: STATUS Portion of ORCSAVE2
  ID: ORCSAVE2
 GENERAL DESCRIPTION:   The purpose of this ICR is to grant the Outpatient
 Pharmacy and CMOP packages access to the STATUS update code in ORCSAVE2.  
  
 Replaced by 5903.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ORCSAVE2
KEYWORDS: STATUS
COMPONENT/ENTRY POINT: STATUS
 COMPONENT DESCRIPTION:   Updates the status in the ORDERS (#100) file 
VARIABLES: IFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number (IEN) of the orders in the
 ORDERS(#100) file 
VARIABLES: ST                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number (IEN) of the status in the
 ORDER STATUS (#100.01) file 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Patch PSO*7.0*546 contains logic that allows site
 personnel to search the ORDERS (#100) file and compare the status in this file
 to the status in the associated medication file - PHARMACY PATIENT (#55) or
 PRESCRIPTION (#52).  If the status in the ORDERS (#100) file is active but the
 status in the medication file is expired or discontinued, the user can elect
 to have the logic of the search routine update the ORDERS (#100) file status 
 to "discontinued" or "expired".  
SUBSCRIBING PACKAGE: CMOP
 SUBSCRIBING DETAILS:   See details for Outpatient Pharmacy.  

NUMBER: 6989                            IA #: 6989
  FILE NUMBER: 120.82                   GLOBAL ROOT: GMRD(120.82,
  DATE CREATED: NOV 20, 2018
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS TO ALLERGY'S DRUG INGREDIENTS
  ID: GMRD(120.82,
GLOBAL REFERENCE: GMRD(120.82,DA(1),'ING',
FIELD NUMBER: 4                         FIELD NAME: DRUG INGREDIENTS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   List of drug ingredients that comprise this allergy.  
 GENERAL DESCRIPTION:   This integration agreement allows subscribers to read
 the entries in the DRUG INGREDIENTS multiple (#4) in the GMR ALLERGIES file
 (#120.82).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DRUG INGREDIENTS
KEYWORDS: ING
SUBSCRIBING PACKAGE: DIETETICS
 SUBSCRIBING DETAILS:   The Dietetics package performs food allergy order
 checking and needs read access to the DRUG INGREDIENTS field to determine
 which foods a patient may have an adverse reaction to. This checking looks at
 the ingredients in the drug and compares them to the ingredients in the
 ordered food item.  
  DATE ACTIVATED: NOV 30, 2018

NUMBER: 6990                            IA #: 6990
  DATE CREATED: NOV 20, 2018
  CUSTODIAL PACKAGE: FUNCTIONAL INDEPENDENCE
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: RMIM DRIVER
 GENERAL DESCRIPTION:   The RMIM DRIVER protocol is used to send HL7 messages
 to the Functional Status and Outcomes Database (FSOD) at the Austin Automation
 Center (AAC).  See the FIM Technical Manual for the HL7 message
 specifications.  
  
 This documents the protocols allowed to subscribe to this event. Supported HL7
 utilities may be used to read the attached message; the message itself and HL7
 application variables may not be altered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   The VPR listener is VPR RMIM EVENTS, effective with
 VPR*1*8.  
  DATE ACTIVATED: NOV 29, 2018

NUMBER: 6991                            IA #: 6991
  DATE CREATED: NOV 27, 2018            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMPDX
  NAME: PREVIOUS ENCOUNTER DIAGNOSIS API
  ID: PXRMPDX
 GENERAL DESCRIPTION:   This API searches the V POV file for previous encounter
 diagnoses for a patient using the Clinical Reminders Index.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PREVIOUS ENCOUNTER
KEYWORDS: DIAGNOSIS
KEYWORDS: API
COMPONENT/ENTRY POINT: $$PRENDIAG(DFN,BDT,ENCDATE,.DIAGLIST)
 COMPONENT DESCRIPTION:   This API searches the V POV file for previous
 encounter diagnoses for a patient using the Clinical Reminders Index. The
 arguments are: 
  
 DFN - The patient 
  
 BDT -  Each V POV entry has an associated date, this is the Event Date and 
 Time and if that does not exist it is the Visit/Admit Date&Time. This argument 
 specifies how far back to start the search. It can be any valid FileMan date 
 including symbolic dates of the form T-NX where N is an integer and X can be
 one of the following: 
  D = days 
  M = months 
  Y = years 
  T-3M would start the search three months prior to today, T-2Y would start the 
 search 2 years prior to today.  
  
 ENCDATE - The encounter date, only diagnoses that are active as of the 
 encounter date will be returned.  
  
 DIAGLIST - The list of diagnoses that were found, this is in a format that is 
 compatible with the API GETLST^IBDF18A, so that the list created by this API 
 can be passed into GETLST^IBDF18A and have the additional diagnoses defined 
 for a specified encounter form added to the list.  
   DIAGLIST(0)=The number that were found 
   DIAGLIST(1)="^PREVIOUS ENCOUNTER DIAGNOSES" 
   DIAGLIST(2) to DIAGLIST(2+number found) An "^" separated string where 
    Piece 1 is the code 
    Piece 2 is the short description of the code 
    Piece 9 is the code pointer, the internal entry number of the code in file 
 #80 
    Piece 10 is the long description of the code 
  If no diagnoses are found then DIAGLIST(2)="^None found" 
  
 The return values are: 
  -1 - The Clinical Reminders Index for V POV is missing so the search cannot
 be performed 
  N - The number of diagnoses that were found 
  
 For a diagnosis to be added to the list it must be associated with an 
 encounter that has a status of "CHECKED OUT" and not already on the patient's 
 Problem List.  
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient 
  
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Date and optional time to start the search 
  
VARIABLES: ENCDATE                      TYPE: Input
 VARIABLES DESCRIPTION:   Encounter date and optional time 
  
VARIABLES: DIAGLIST                     TYPE: Output
 VARIABLES DESCRIPTION:   The list of diagnoses 
  
SUBSCRIBING PACKAGE: PROBLEM LIST
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 12/10/20, effective with OR*3*476 
  DATE ACTIVATED: DEC 03, 2018

NUMBER: 6992                            IA #: 6992
  DATE CREATED: NOV 27, 2018
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXPXRM1
  NAME: IMMUNIZATION API FOR CLINICAL REMINDERS
  ID: PXPXRM1                           STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: IMMUNIZATION
KEYWORDS: API
KEYWORDS: CLINICAL REMINDERS
COMPONENT/ENTRY POINT: VIMMCR(DA,.DATA)
 COMPONENT DESCRIPTION:   This entry point is called as D
 VIMMCR^PXPXRM1(DA,.DATA). The data from V IMMUNIZATION, file #9000010.11, is
 returned in the DATA array.  
  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the entry in the V
 IMMUNIZATION file, #9000010.11 
  
VARIABLES: DATA                         TYPE: Output
 VARIABLES DESCRIPTION:   The data array that is passed back to the calling
 package.  
                             
  DATA("ADMIN ROUTE")=HL7 Code^Name 
  DATA("ADMIN SITE")=HL7 Code^Name 
  DATA("CODES",Coding System Name)=Code 1^Code 2^... Code x 
  DATA("COMMENTS")=Free text, 1 to 245 characters 
  DATA("CONTRAINDICATED")=Set of codes: 1=Yes 
  DATA("CVX")=CVX Code 
  DATA("DATA SOURCE")=Pointer to the PCE DATA SOURCE file, #839.7 
  DATA("DATE RECORDED")=Date and time in FileMan internal format 
  DATA("DOCUMENTER")=Pointer to the NEW PERSON file, #200 
  DATA("DOSE")=Number (e.g., 0.5) 
  DATA("DOSE UNITS")=UCUM Code (e.g., mL) 
  DATA("ENCOUNTER PROVIDER")=Pointer to the NEW PERSON file, #200 
  DATA("EVENT DATE TIME")=Date and time in FileMan internal format 
  DATA("EXPIRATION DATE")=Date in FileMan internal format 
  DATA("IMMUNIZATION")=Name 
  DATA("INFO SOURCE")=HL7 Code^Name 
  DATA("LOT NUMBER")=Lot Number 
  DATA("MANUFACTURER")=Name 
  DATA("ORDERING PROVIDER")=Pointer to the NEW PERSON file, #200 
  DATA("OVERRIDE REASON")=Free Text 3-245 characters in length 
  DATA("PACKAGE")=Pointer to the PACKAGE file, #9.4 
  DATA("REACTION")=Set of codes: 
    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 
  DATA("SERIES")=Set of codes: P=Partially Complete, C=Complete, B=Booster, 
    a number 1-8=1-8 
  DATA("REMARKS",n,0)=Free text, word-processing 
  DATA("VACCINE GROUP",n,0)=Free text 2-30 characters in length 
  DATA("VALUE")=Set of codes: P=Partially Complete, C=Complete, B=Booster, 
    a number 1-8=1-8 
  DATA("VIS OFFERED",n,0)=IEN^Date Offered^Name^Edition Date^Language 
    IEN = Pointer to the VACCINE INFORMATION STATEMENT file, #920 
    Date Offered=Date in FileMan internal format 
    Edition Date=Date in FileMan internal format 
  DATA("VISIT")=Pointer to the VISIT file, #9000010 
  DATA("WARNING ACK")=Set of codes: 1=Yes 
  
  
  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: DEC 03, 2018

NUMBER: 6993                            IA #: 6993
  DATE CREATED: NOV 30, 2018
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWDXC
  NAME: NFS CALLS REASON ORWDXC         ID: ORWDXC
 GENERAL DESCRIPTION:   NUTRITION AND FOOD SERVICES CALLS REASON^ORWDXC TO
 RETRIEVE A LIST OF REASONS TO OVERRIDE AN ORDER CHECK.  THIS IS FOR TUBE
 FEEDING ORDERS.  
  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: REASON
SUBSCRIBING PACKAGE: DIETETICS
  DATE ACTIVATED: NOV 30, 2018

NUMBER: 6994                            IA #: 6994
  DATE CREATED: NOV 30, 2018            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FHSELA1
  NAME: CHKTF FHSELA1 API               ID: FHSELA1
 GENERAL DESCRIPTION:   CPRS CALLS $$CHKTF^FHSELA1 TO PERFORM TUBE FEEDING
 ORDER CHECKS.  
  
  STATUS: Active
COMPONENT/ENTRY POINT: $$CHKTF
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 30, 2018

NUMBER: 6995                            IA #: 6995
  DATE CREATED: JAN 24, 2019            CUSTODIAL PACKAGE: MYHEALTHEVET
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: MHV52API                     NAME: MHV Pharmacy Data
  ID: MHV52API
 GENERAL DESCRIPTION:   This api is used to gather prescription information to
 display in My HealtheVet from Prescription file #52, Pharmacy Patient file #55
 and Pending Outpatient Order file #52.41.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: MHV
KEYWORDS: Pharmacy
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This entry point returns medication information for a 
 patient.  Medication are comprised of Outpatient Pharmacy (Prescription detail
 includes Partials fills, Refills, and CMOP data), Non-VA Medications, and
 Pending Medications.  
  
 Note: This API has defined one entry point by parameter passing, to return
 data from available data nodes from the PRESCRIPTION file (#52), Pharmacy
 Patient file (#55)and the Pending Outpatient Order file (#52.41).  
  
 ZE - returns the Zero node TW - returns the Two node TH -returns the  Three
 node RF - returns all refills for a prescription PF - returns all partial
 fills for a prescription CM - returns CMOP data AT - returns the Activity Logs
 for a prescription OI - returns the Orderable Item for a prescription MI -
 returns the medication instructions (SIG) NVA - returns the Non-VA Medications 
 PEND - returns the pending outpatient orders 
  
 Outpatient Pharmacy/Prescription Data -  File 52 
 -----------------------------------------------------------
 LIST="RX" to indicate a Outpatient pharmacy prescription IEN - File 52 IEN
 Pointer 
  
   ^TMP("MHV",$J,LIST,0)=Total RX entries returned by patient 
    or -1^NO DATA FOUND 
   ^TMP("MHV",$J,LIST,IEN,.01)=RX #(52,.01) 
   ^TMP("MHV",$J,LIST,IEN,1)=ISSUE DATE (52,1)^External Format 
    (ex: Sep. 12, 1999) 
   ^TMP(,IEN,2)=PATIENT (52,2)^NAME (2,.01) 
   ^TMP("MHV",$J,LIST,IEN,3)=PATIENT STATUS (52,3) 
   ^TMP("MHV",$J,LIST,IEN,4)=PROVIDER (52,4)^NAME (200,.01) 
   ^TMP("MHV",$J,LIST,IEN,5)=CLINIC (52,5)^NAME(44,.01) 
   ^TMP("MHV",$J,LIST,IEN,6)=DRUG (52,6)^GENERIC NAME(50,.01) 
   ^TMP("MHV",$J,LIST,IEN,6.5)=TRADE NAME (52,6.5) 
   ^TMP("MHV",$J,LIST,IEN,7)=QTY (52,7) 
   ^TMP("MHV",$J,LIST,IEN,8)=DAYS SUPPLY (52,8) 
   ^TMP($"MHV",$J,LIST,IEN,9)=# OF REFILLS (52,9) 
   ^TMP($"MHV",$J,LIST,IEN,10.3)=ORDER CONVERTED 
    (52,10.3)^External Format for the Set of Codes     
   ^TMP("MHV",$J,LIST,IEN,10.6)=COPIES (52,10.6) 
   ^TMP("MHV",$J,LIST,IEN,11)=MAIL/WINDOW (52,11)^External 
    Format for the Set of Codes 
   ^TMP("MHV",$J,LIST,IEN,14)=ADMINISTERED IN CLINIC 
   ^TMP("MHV",$J,LIST,IEN,16)=ENTERED BY (52,16)^NAME (200,.01) 
   ^TMP("MHV",$J,LIST,IEN,17)=UNIT PRICE OF DRUG (52,17) 
   ^TMP("MHV",$J,LIST,IEN,20)=DIVISION (52,20)^NAME(59,.01) 
   ^TMP("MHV",$J,LIST,IEN,21)=LOGIN DATE (52,21)^External 
    Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,22)=FILL DATE (52,22)^External Format 
    (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,23)=PHARMACIST (52,23)^NAME (200,.01) 
   ^TMP("MHV",$J,LIST,IEN 24)=LOT # (52,24) 
   ^TMP("MHV",$J,LIST,IEN 25)=DISPENSED DATE (52,25)^External 
    Format (ex: Sep.  12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,26)=EXPIRATION DATE (52,26)^External 
    Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,27)=NDC (52,27) 
   ^TMP("MHV",$J,LIST,IEN,28)=MANUFACTURER (52,28) 
   ^TMP("MHV",$J,LIST,IEN,29)=DRUG EXPIRATION DATE 
    (52,29)^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,30)=GENERIC PROVIDER (52,30) 
   ^TMP("MHV",$J,LIST,IEN,31)=RELEASE DATE/TIME (52,31) 
    ^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN 32.1)=RETURNED TO STOCK 
    (52,32.1)^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,32.2)=REPRINT (52,32.2)^External 
    Format for the Set of Codes 
   ^TMP("MHV",$J,LIST,IEN,32.3)=BINGO WAIT TIME (52,32.3) 
   ^TMP("MHV",$J,LIST,IEN,104)=VERIFYING PHARMACIST (52,104) 
    ^NAME (200,.01) 
   ^TMP("MHV",$J,LIST,IEN,12)=REMARKS (52,12) 
   ^TMP("MHV",$J,LIST,IEN,26.1)=CANCEL DATE (52,26.1)^External 
    Format (ex: Sep.  12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,34.1)=DRUG ALLERGY INDICATION 
    (52,34.1)^External Format for the Set of Codes 
   ^TMP("MHV",$J,LIST,IEN,39.3)=PLACER ORDER # 
   ^TMP("MHV",$J,LIST,IEN,100)=STATUS (52,100)^External Format 
    for the Set of Codes 
   ^TMP("MHV",$J,LIST,IEN,101)=LAST DISPENSED DATE 
    (52,101)^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,102)=NEXT POSSIBLE FILL 
    (52,102)^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,102.1)=PRIOR FILL DATE 
    (52,102.1)^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,102.2)=PENDING NEXT POSSIBLE FILLDATE 
    (52,102.2) ^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,109)=COSIGNING PHYSICIAN (52,109) 
    ^NAME (200,.01) 
   ^TMP("MHV",$J,LIST,IEN,112)=ORIGINAL QTY (52,112) 
  
 Prescription Refill - File 52 fld 52 (DD 52.1) 
  -------------------
 LIST="RX" to indicate a Outpatient pharmacy prescription IEN - File 52 IEN
 Pointer SUB = "RF" to indicate Refill multiple n = 52.1 mulitple pointer value 
  
   ^TMP("MHV",$J,LIST,IEN,SUB,n,.01)=REFILL DATE 
    (52.1,.01)^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,1)=QTY (52.1,1) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,1.1)=DAYS SUPPLY (52.1,1.1) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,1.2)=CURRENT UNIT PRICE 
    OF DRUG (52.1,1.2) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,2)=MAIL/WINDOW (52.1,2) 
    ^External Format for the Set of Codes 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,3)=REMARKS (52.1,3) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,4)=PHARMACIST NAME (52.1,4) 
     ^NAME(200,.01) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,5)=LOT # (52.1,5) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,6)=CLERK CODE (52.1,6)^NAME 
     (200,.01) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,7)=LOGIN DATE (52.1,7) 
    ^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,8)=DIVISION (52.1,8)^NAME 
    (59,.01) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,10.1)=DISPENSE DATE 
    (52.1,10.1)^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,11)=NDC 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,12)=MANUFACTURER (52.1,12) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,13)=DRUG EXPIRATION DATE 
    (52.1,13)^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,14)=RETURNED TO STOCK 
    (52.1,14)External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,15)=PROVIDER (52.1,15)^NAME 
    (200,.01) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,17)=RELEASED DATE/TIME 
    (52.1,17)^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,23)=ADMINISTERED IN CLINIC 
  
 Prescription Partial fill- File 52 fld 60 (DD 52.2) 
 -------------------
 LIST="RX" to indicate a Outpatient pharmacy prescription IEN - File 52 IEN
 Pointer SUB = "PF" to indicate Refill multiple n = 52.2 mulitple pointer value 
  
   ^TMP("MHV",$J,LIST,0)=Total entries returned by patient or 
    -1^NO DATA FOUND 
   ^TMP("MHV",$J,LIST,IEN,100)=STATUS (52,100)^External Format 
    for the Set of Codes 
   ^TMP("MHV",$J,LIST,IEN,SUB,0)= Total entries returned 
    or -1^NO DATA FOUND 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,.01)=PARTIAL DATE 
    (52.2,.01)^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,.02)=MAIL/WINDOW 
    (52.2,.02)^External Format for the Set of Codes 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,.03)=REMARKS (52.2,.03) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,.04)=QTY (52.2,.04) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,.041)=DAYS SUPPLY (52.2,.041) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,.042)=CURRENT UNIT PRICE 
    OF DRUG (52.2,.042) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,.05)=PHARMACIST NAME 
    (52.2,.05)^NAME (200,.01) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,.06)=LOT # (52.2,.06) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,.08)=LOGIN DATE 
    (52.2,.08)^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,.09)=DIVISION (52.2,.09)^NAME 
    (59.2,.01) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,1)=NDC (52.2,1) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,5)=RETURNED TO STOCK 
    (52.2,5)^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,6)=PROVIDER (52.2,6)^NAME 
    (200,.01) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,7.5)=DISPENSED DATE 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,8)=RELEASE DATE/TIME 
    (52.2,8)^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,12)=DRUG EXPIRATION DATE 
  
 Prescription SIG (Medication Instructions) - File 52 Fld 10 
 -------------------
 LIST="RX" to indicate a Outpatient pharmacy prescription IEN - File 52 IEN
 Pointer SUB = "M" to indicate SIG multiple n = multiple line value 
  
   ^TMP("MHV",$J,LIST,IEN,SUB,0)=Total entries returned 
    -1^NO DATA FOUND 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,0)=MEDICATION 
     INSTRUCTIONS(52.04,.01) 
                 
 Prescription CMOP - File 52,400 (DD 52.01) 
 -----------------
 LIST="RX" to indicate a Outpatient pharmacy prescription IEN - File 52 IEN
 Pointer SUB = "C" to indicate CMOP data n = multiple line value 
  
   ^TMP("MHV",$J,LIST,IEN,SUB,0)=Total entries returned or 
     -1^NO  DATA FOUND 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,2)=RX INDICATOR (52.01,2) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,3)=STATUS (52.01,3)^External 
    Format for the Set of Codes 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,4)=NDC (52.10,4) 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,9)=DATE SHIPPED 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,10)=CARRIER 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,11)=PACKAGE ID 
   ^TMP("MHV",$J,LIST,IEN,SUB,n,12)=NDC SENT 
  
 Prescription Activity Log- Pulled from File 52 fld 40 (DD 52.3) 
 -----------------
 LIST="RX" to indicate a Outpatient pharmacy prescription IEN - File 52 IEN
 Pointer SUB = "A" to indicate Activity Log data n = 52.3 mulitple pointer
 value 
   
   ^TMP("MHV",$J,LIST,IEN,"A",0)=Total entries returned 
    or -1^NO DATA FOUND 
   ^TMP("MHV",$J,LIST,IEN,"A",n,.01)=ACTIVITY LOG 
    (52.3,.01)^External Format (ex: Sep. 12, 1999) 
   ^TMP("MHV",$J,LIST,IEN,"A",n,.02)=REASON (52.3,.02) 
    ^External Format for the Set of Codes 
   ^TMP("MHV",$J,LIST,IEN,"A",n,.03)=INITIATOR OF ACTIVITY 
    (52.3,.03)^NAME (200,.01) 
   ^TMP("MHV",$J,LIST,IEN,"A",n,.04)=RX REFERENCE (52.3,.04) 
   ^TMP("MHV",$J,LIST,IEN,"A",n,.05)=COMMENTS (52.3,.05) 
   
 Pharmacy Orderable Item- Pulled from File 52 fld 39.2 (DD 50.7) 
 -----------------
 LIST="RX" to indicate a Outpatient pharmacy prescription IEN - File 52 IEN
 Pointer SUB = "OI" to indicate Activity Log data n = 52.3 mulitple pointer
 value 
    
 ^TMP("MHV",$J,LIST,IEN,SUB)=IEN(52,39.2)^NAME(50.7,.01)^DOSAGE 
    FORM(50.7,.02)^NAME (50.606,.01) 
           
 Non-VA Medications- Pulled from File 55 fld 52.2 DD(55.05) 
 -----------------
 LIST="NV" to indicate a Non-VA Meds IEN - 55.05 multiple pointer 
       
   ^TMP("MHV",$J,LIST,0)=Total entries returned by patient or 
    -1^NO DATA FOUND 
   ^TMP("MHV",$J,LIST,IEN,.01)=ORDERABLE ITEM 
   ^TMP("MHV",$J,LIST,IEN,1)=DISPENSED DRUG (PTR to #50.7) 
   ^TMP("MHV",$J,LIST,IEN,2)=DOSAGE 
   ^TMP("MHV",$J,LIST,IEN,3)=MEDICATION ROUTE 
   ^TMP("MHV",$J,LIST,IEN,4)=SCHEDULE 
   ^TMP("MHV",$J,LIST,IEN,5)=STATUS (1=Discontinue 
    2=Date of Death) 
   ^TMP("MHV",$J,LIST,IEN,6)=DISCONTINUED DATE 
   ^TMP("MHV",$J,LIST,IEN,8)=START DATE 
   ^TMP("MHV",$J,LIST,IEN,13)=CLINIC 
   ^TMP("MHV",$J,LIST,IEN,14)=COMMENTS 
   
 Pending Medications- Pulled from File 52.41  
 -----------------
 LIST="PD" to indicate a Non-VA Meds IEN - 52.41 IEN pointer 
   
   ^TMP("MHV",$J,LIST,0)=Total entries returned by patient or 
    -1^NO DATA FOUND 
   ^TMP("MHV",$J,LIST,IEN,.01)=PLACER NUMBER (52.41,.01) 
   ^TMP("MHV",$J,LIST,IEN,1)=PATIENT (52.41,1) 
   ^TMP"MHV",$J,LIST,IEN,1.1)=PATIENT LOCATION (52.41,1.1) 
   ^TMP("MHV",$J,LIST,IEN,2)=ORDER TYPE (52.41,2) 
   ^TMP("MHV",$J,LIST,IEN,5)=PROVIDER  (52.41,5) 
   ^TMP("MHV",$J,LIST,IEN,6)=EFFECTIVE DATE (52.41,6) 
   ^TMP("MHV",$J,LIST,IEN,8)=PHARMACY ORDERABLE ITEM (52.41,8) 
   ^TMP("MHV",$J,LIST,IEN,11)=DRUG (52.41,11) 
   ^TMP("MHV",$J,LIST,IEN,12)=QTY (52.41,12) 
   ^TMP("MHV",$J,LIST,IEN,13)= # OF REFILLS (52.41,13) 
   ^TMP("MHV",$J,LIST,IEN,19)=PICKUP ROUTING (52.41,19) 
   ^TMP("MHV",$J,LIST,IEN,21)=Rx REFILL REQUEST (52.41,21) 
   ^TMP("MHV",$J,LIST,IEN,23)=COMMENTS (52.41,23) 
   ^TMP("MHV",$J,LIST,IEN,26)=POSSIBLE FILLDATE (52.41,26) 
   ^TMP("MHV",$J,LIST,IEN, 100)=RELATED INSTITUTION (52.41,100) 
   ^TMP("MHV",$J,LIST,IEN,101)=DAYS SUPPLY (52.41,101) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN NUmber (Required).  
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the start date to search (default is DT-548). 
 
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the end date (default is null, prescriptions
 expiring in the future 
VARIABLES: TMP('MHV',$J                 TYPE: Output
 VARIABLES DESCRIPTION:   Global location of returned list of RXs. Please see
 the IA description section for the TMP global layout.  

NUMBER: 6996                            IA #: 6996
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: DEC 01, 2018            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  NAME: File 52                         ID: PSRX(
GLOBAL REFERENCE: PSRX(
FIELD NUMBER: .01                       FIELD NAME: RX #
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: # OF REFILLS
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 100                       FIELD NAME: STATUS
  LOCATION: STA;1                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PSRX(D0,1,D1,0
FIELD NUMBER: Sub-internal entry number
  LOCATION: Global root                 ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Permission is granted for the calling application to loop
 through the entries in the REFILL Subfile (#52.1) to count the number of
 entries within the multiple.  
 GENERAL DESCRIPTION:   This is the replacement agreement for DBIA #824. It
 gives permission to read various fields in the PRESCRIPTION File (#52).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: Prescription
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   This agreement gives permission to the Inpatient
 Medications package to read various fields in the PRESCRIPTION File (#52).  

NUMBER: 6997                            IA #: 6997
  FILE NUMBER: 53                       GLOBAL ROOT: PS(53,
  DATE CREATED: DEC 01, 2018            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: File
  NAME: File 53                         ID: PS(53,
GLOBAL REFERENCE: PS(53,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ABBR
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DAYS SUPPLY
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: REFILLS
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: RENEWABLE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: SC/A&A/OTHER/INPATIENT/NVA
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: EXEMPT FROM COPAYMENT
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: EXEMPT FROM CHAMPUS BILLING
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This is the replacement agreement for DBIA 1975. It
 gives permission to read various fields in the RX PATIENT STATUS File (#53).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: Rx Patient Status
SUBSCRIBING PACKAGE: CMOP
 SUBSCRIBING DETAILS:   This agreement gives permission to the Consolidated
 Mail Outpatient Pharmacy package to read various fields in the RX PATIENT
 STATUS File (#53).  
SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT
 SUBSCRIBING DETAILS:   This agreement gives permission to the Pharmacy
 Benefits Management package to read various fields in the RX PATIENT STATUS
 File (#53).  

NUMBER: 6998                            IA #: 6998
  FILE NUMBER: 59                       GLOBAL ROOT: PS(59
  DATE CREATED: DEC 01, 2018            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: File
  NAME: File 59                         ID: PS(59
GLOBAL REFERENCE: PS(59
FIELD NUMBER: All fields                FIELD NAME: All fields
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   All fields in the file can be read.  
 GENERAL DESCRIPTION:   This is the replacement agreement for DBIA 1976. It
 gives permission for other packages to directly read and read with FileMan all
 fields in the OUTPATIENT SITE File (#59).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: Outpatient Site
SUBSCRIBING PACKAGE: CMOP
 SUBSCRIBING DETAILS:   This agreement gives permission to the Consolidated
 Mail Outpatient Pharmacy package to directly read and read with FileMan all
 fields in the OUTPATIENT SITE File (#59).  
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   This agreement gives permission to the Pharmacy Data
 Management packege to directly read and read with FileMan all fields in the
 OUTPATIENT SITE File (#59).  
SUBSCRIBING PACKAGE: NATIONAL DRUG FILE
 SUBSCRIBING DETAILS:   This agreement gives permission to the National Drug
 File package to directly read and read with FileMan all fields in the
 OUTPATIENT SITE File (#59).  

NUMBER: 6999                            IA #: 6999
  FILE NUMBER: 59                       GLOBAL ROOT: PS(59
  DATE CREATED: DEC 01, 2018            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  NAME: File 59                         ID: PS(59
GLOBAL REFERENCE: PS(59
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Also can perform a FileMan lookup into File 59.  
FIELD NUMBER: .02                       FIELD NAME: MAILING FRANK STREET ADDRESS
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: MAILING FRANK ZIP+4 CODE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: SITE NUMBER
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: MAILING FRANK CITY
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: MAILING FRANK STATE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2004                      FIELD NAME: INACTIVE DATE
  LOCATION: I;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PS(59,D0,INI1,D1,0
FIELD NUMBER: .01                       FIELD NAME: CPRS ORDERING INSTITUTION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This is the replacement agreement for DBIA #2621. It
 gives permission to read various fields in the OUTPATIENT SITE File (#59).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: Outpatient Site
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
 SUBSCRIBING DETAILS:   This agreement gives permission to the Controlled
 Substances package to read various fields in the OUTPATIENT SITE File (#59).  

NUMBER: 7000                            IA #: 7000
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: DEC 04, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: NEW DEA MULTIPLE
  ID: VA(200,
GLOBAL REFERENCE: VA(200,D0,'PS4',
FIELD NUMBER: .01                       FIELD NAME: DEA NUMBER
  LOCATION: 0;1                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field is used to enter the providers' Drug
 Enforcement Administration (DEA) number. The DEA number is entered as two
 upper case letters followed by 7 digits. e.g., AA1234567.  
FIELD NUMBER: .02                       FIELD NAME: INDIVIDUAL DEA SUFFIX
  LOCATION: 0;2                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This is the individual DEA suffix related to an
 institutional DEA number.  This field is required if the DEA is an
 institutional DEA number.  
FIELD NUMBER: .03                       FIELD NAME: DEA POINTER
  LOCATION: 0;3                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This pointer field points to the DEA NUMBERS FILE #8991.9
 that contains the provider demographics and controlled substance schedule
 permissions.  
  
 The DEA number is entered as two upper case letters followed by 7 digits, 
 e.g., AA1234567.  
 GLOBAL DESCRIPTION:   This sub-file links providers in the NEW PERSON file
 (#200) to one or more Drug Enforcement Agency (DEA) numbers in the DEA NUMBERS
 file (#8991.9). Institutional type DEA numbers must also contain a unique 
 individual DEA suffix that, when combined with an institutional DEA number,
 form a unique DEA identifier.  
 GENERAL DESCRIPTION:   Outpatient Pharmacy is granted permission to
 enter/edit/delete the following fields.  
  
    Field #     Node;Piece          Field Name 
     53.21        PS4             NEW DEA #'S Multiple #200.5321 200.5321,.01   
  0;1             DEA NUMBER 200.5321,.02     0;2             INDIVIDUAL DEA
 SUFFIX 200.5321,.03     0;3             DEA POINTER 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DEA
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 1/25/22: effective with patch PSO*7*529 and
 XU*8.0*688 
  DATE ACTIVATED: JAN 25, 2022

NUMBER: 7001                            IA #: 7001
  FILE NUMBER: 8991.8                   GLOBAL ROOT: XTV(8991.8
  DATE CREATED: DEC 04, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DEA BUSINESS ACTIVITY CODES
  ID: XTV(8991.8
GLOBAL REFERENCE: XTV(8991.8
FIELD NUMBER: .01                       FIELD NAME: FULL BUSINESS ACTIVITY CODE
  LOCATION: 0;1                         ACCESS: LAYGO
 FIELD DESCRIPTION:   The Drug Enforcement Agency (DEA) uses an alpha character
 business activity code to identify various categories of registrants. and a 
 sub-code to identify sub-categories of registrants.  
  
 For example, business activity code "C" in combination with business activity
 sub-code "1" indicates a practitioner who has received a Drug Addiction
 Treatment Act (DATA) Waiver (DATA Waived or DW) to provide office based opioid
 treatment to 30 or 100 or 275 patients (DW/30, DW/100, DW/275). As new
 sub-categories of business activities become regulated, additional sub-code
 combinations (e.g. C-2, C-3, A-1, etc.) will be assigned. 
FIELD NUMBER: .02                       FIELD NAME: BUSINESS ACTIVITY
  LOCATION: 0;2                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field holds the Business Activity value used for a
 Drug Enforcement Agency (DEA) numbers. This value can currently be one of the
 following: A,B,C,D,E,F,G,H,J,K,L,M,N,P,R,S,T or U 
  
 This value, combined with a numeric business sub-type, categorizes a DEA 
 number.  
FIELD NUMBER: .03                       FIELD NAME: BUSINESS ACTIVITY SUB-CODE
  LOCATION: 0;3                         ACCESS: LAYGO
 FIELD DESCRIPTION:   The Drug Enforcement Agency (DEA) uses an alpha character
 business activity code to identify various categories of registrants, and a 
 sub-code to identify new sub-categories of registrants. This field contains
 the DEA sub-code.  
FIELD NUMBER: 1
  FIELD NAME: BUSINESS ACTIVITY DESCRIPTION
  LOCATION: 1;1                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This is the description given for the Business Activity
 Code and Sub-code.  
FIELD NUMBER: 2                         FIELD NAME: MANUAL ENTRY DATE/TIME
  LOCATION: 1;2                         ACCESS: LAYGO
 FIELD DESCRIPTION:   When populated, this indicates a Business Activity Code
 (BAC) was entered manually due to the failure of the PSO DOJ/DEA WEB SERVICE
 to establish a connection to the web server.  
 GLOBAL DESCRIPTION:   The DEA BUSINESS ACTIVITY CODES FILE is associated with
 the DEA numbers and provider information in the DEA NUMBERS file.  This file
 links a provider with the type of service provided.  It contains BUSINESS 
 ACTIVITY CODES that are supplied by the DOJ/DEA web service.  
 GENERAL DESCRIPTION:   
     Outpatient Pharmacy is granted permission to enter/edit the following 
    fields.  
    
    Field #     Node;Piece          Field Name 
     .01          0;1            FULL BUSINESS ACTIVITY CODE 
     .02          0;2            BUSINESS ACTIVITY 
     .03          0;3            BUSINESS ACTIVITY SUB-CODE 
     1            1;1            BUSINESS ACTIVITY DESCRIPTION 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DEA
KEYWORDS: BUSINESS ACTIVITY
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 1/25/22: effective with patch PSO*7*529 and
 XU*8.0*688 
  DATE ACTIVATED: JAN 25, 2022

NUMBER: 7002                            IA #: 7002
  FILE NUMBER: 8991.9                   GLOBAL ROOT: XTV(8991.9
  DATE CREATED: DEC 04, 2018            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DEA NUMBERS FILE
  ID: XTV(8991.9
GLOBAL REFERENCE: XTV(8991.9
FIELD NUMBER: .01                       FIELD NAME: DEA NUMBER
  LOCATION: 0;1                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field is contains the Drug Enforcement
 Administration (DEA) number that authorizes the prescribing of controlled
 substances.  
FIELD NUMBER: .02                       FIELD NAME: BUSINESS ACTIVITY CODE
  LOCATION: 0;2                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field contains the business activity code associated
 with the Drug Enforcement Agency (DEA) number.  
FIELD NUMBER: .03                       FIELD NAME: DETOX NUMBER
  LOCATION: 0;3                         ACCESS: LAYGO
 FIELD DESCRIPTION:   If the DEA provider has detox privileges, this field will
 be populated with a 'VX' or 'XA' followed by the numeric portion of the DEA
 number.  
FIELD NUMBER: .04                       FIELD NAME: EXPIRATION DATE
  LOCATION: 0;4                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field contains the date the Drug Enforcement Agency
 (DEA) number expires.  
FIELD NUMBER: .06                       FIELD NAME: USE FOR INPATIENT ORDERS
  LOCATION: 0;6                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field indicates if this DEA number can be used for
 inpatient orders.  
FIELD NUMBER: .07                       FIELD NAME: TYPE
  LOCATION: 0;7                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field  identifies whether the Drug Enforcement
 Agency (DEA) number is an individual DEA number or an Institutional DEA
 number.  
FIELD NUMBER: 1.1
  FIELD NAME: NAME (PROVIDER OR INSTITUTION)
  LOCATION: 1;1                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field contains the name of the facility or person
 associated with the Drug Enforcement Agency (DEA) number.  
FIELD NUMBER: 1.2                       FIELD NAME: STREET ADDRESS 1
  LOCATION: 1;2                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field contains the first line of the permanent
 street address of the the person or institution associated with the Drug
 Enforcement Agency (DEA) number.  
FIELD NUMBER: 1.3                       FIELD NAME: STREET ADDRESS 2
  LOCATION: 1;3                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This is the second line of the permanent street address
 of the person or institution associated with the Drug Enforcement Agency (DEA)
 number.  
FIELD NUMBER: 1.4                       FIELD NAME: STREET ADDRESS 3
  LOCATION: 1;4                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This is the third line of the permanent street address of
 the person or institution associated with this Drug Enforcement Agency (DEA)
 number.  
FIELD NUMBER: 1.5                       FIELD NAME: CITY
  LOCATION: 1;5                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field contains the city in the permanent address of
 the person or institution related to this Drug Enfocement Agency (DEA) number. 
 
FIELD NUMBER: 1.6                       FIELD NAME: STATE
  LOCATION: 1;6                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This is the state of the permanent address of the person
 or institution associated with this Drug Enforcement Agency (DEA) number.  
FIELD NUMBER: 1.7                       FIELD NAME: ZIP CODE
  LOCATION: 1;7                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This is the postal ZIP code of the person or institution
 associated with this Drug Enforcement Agency (DEA) number.  
FIELD NUMBER: 2.1                       FIELD NAME: SCHEDULE II NARCOTIC
  LOCATION: 2;1                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field is used to determine if the provider has
 privileges to prescribe Schedule II drugs.  
FIELD NUMBER: 2.2                       FIELD NAME: SCHEDULE II NON-NARCOTIC
  LOCATION: 2;2                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field is used to determine if the provider has
 privileges to prescribe Schedule II non-narcotic drugs.  
FIELD NUMBER: 2.3                       FIELD NAME: SCHEDULE III NARCOTIC
  LOCATION: 2;3                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field is used to determine if the provider has
 privileges to prescribe Schedule III narcotic drugs.  
FIELD NUMBER: 2.4                       FIELD NAME: SCHEDULE III NON-NARCOTIC
  LOCATION: 2;4                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field is used to determine if the provider has
 privileges to prescribe Schedule III non-narcotic drugs.  
FIELD NUMBER: 2.5                       FIELD NAME: SCHEDULE IV
  LOCATION: 2;5                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field is used to determine if the provider has
 privileges to prescribe Schedule IV drugs.  
FIELD NUMBER: 2.6                       FIELD NAME: SCHEDULE V
  LOCATION: 2;6                         ACCESS: LAYGO
 FIELD DESCRIPTION:   This field is used to determine if the provider has
 privileges to prescribe Schedule V drugs.  
FIELD NUMBER: 10.1                      FIELD NAME: LAST UPDATED BY
  LOCATION: 10;1                        ACCESS: LAYGO
 FIELD DESCRIPTION:   This is the person from the NEW PERSON file who last
 updated this Drug Enforcement Agency (DEA) record.  
FIELD NUMBER: 10.2                      FIELD NAME: LAST UPDATED DATE/TIME
  LOCATION: 10;2                        ACCESS: LAYGO
 FIELD DESCRIPTION:   This is the date/time of the last update to this Drug
 Enforement Agency (DEA) number record.  
FIELD NUMBER: 10.3                      FIELD NAME: LAST DOJ UPDATE DATE/TIME
  LOCATION: 10;3                        ACCESS: LAYGO
 FIELD DESCRIPTION:   This is the date/time the DOJ (Department of Justice)
 data was used to update this Drug Enforcement Agency (DEA) number record. The
 absence of this date/time indicates the record was added manually and may not 
 accurately reflect DOJ data.  
 GLOBAL DESCRIPTION:   The DEA NUMBERS FILE is designed to contain demographic
 and permission information about a provider related to the ability to order
 controlled substance prescriptions.  
 GENERAL DESCRIPTION:   
     Outpatient Pharmacy is granted permission to enter/edit/delete the 
 following fields.  
  
    Field #     Node;Piece          Field Name 
      .01          0;1           DEA NUMBER 
      .02          0;2           BUSINESS ACTIVITY CODE 
      .03          0;3           DETOX NUMBER 
      .04          0;4           EXPIRATION DATE 
      .06          0;6           USE FOR INPATIENT ORDERS? 
      .07          0;7           TYPE 
      1.1          1;1           NAME (PROVIDER OR INSTITUTION) 
      1.2          1;2           STREET ADDRESS 1 
      1.3          1;3           STREET ADDRESS 2 
      1.4          1;4           STREET ADDRESS 3 
      1.5          1;5           CITY 
      1.6          1;6           STATE 
      1.7          1;7           ZIP CODE 
      2.1          2;1           SCHEDULE II NARCOTIC? 
      2.2          2;2           SCHEDULE II NON-NARCOTIC? 
      2.3          2;3           SCHEDULE III NARCOTIC? 
      2.4          2;4           SCHEDULE III NON-NARCOTIC? 
      2.5          2;5           SCHEDULE IV? 
      2.6          2;6           SCHEDULE V? 
     10.1         10;1           LAST UPDATED BY 
     10.2         10;2           LAST UPDATED DATE/TIME 
     10.3         10;3           LAST DOJ UPDATE DATE/TIME 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DEA
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 1/25/22: effective with patch PSO*7*529 and
 XU*8.0*688 
  DATE ACTIVATED: JAN 24, 2022

NUMBER: 7003                            IA #: 7003
  FILE NUMBER: 984.8                    GLOBAL ROOT: MPIF(984.8,
  DATE CREATED: DEC 11, 2018
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Private                        TYPE: File
  NAME: MPI ICN BUILD MANAGMENT FILE - LEGAL NAME FLAG
  ID: MPIF(984.8,
GLOBAL REFERENCE: MPIF(984.8,D0,0)
FIELD NUMBER: 3                         FIELD NAME: LAST PATIENT BUILT
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The REGISTRATION package requests permission to access
 the MPI ICN BUILD MANAGEMENT (#984.8) file using a direct global read. This 
 file contains a 'Flag' that is needed to determine how to process the
 collection of an individual's legal name (or Alias) which can now exceed
 VistA's limitation of 30 characters.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: MPIF
KEYWORDS: DG
KEYWORDS: REGISTRATION
KEYWORDS: LEGAL NAME
KEYWORDS: NAME
KEYWORDS: ALIAS
KEYWORDS: 984.8
KEYWORDS: MPIF(984.8
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   The REGISTRATION package will access the MPI ICN BUILD
 MANAGEMENT (#984.8) file to retrieve the LAST PATIENT BUILT (#3) field using a
 direct global read of the 0 node. This field contains the Name Components flag
 that determines how Legal Names (or Aliases) that may exceed the 30-characater
 limitation in VistA should be processed.  

NUMBER: 7004                            IA #: 7004
  DATE CREATED: DEC 11, 2018
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MPIFNAMC
  NAME: MPIFNAMC - LEGAL NAME FLAG      ID: MPIFNAMC
 GENERAL DESCRIPTION:   The REGISTRATION and CLINICAL INFO RESOURCE NETWORK
 packages request permission to access the Application Programming Interface
 (API) to retrieve the value of the 'Name Components' flag which will be used 
 to determine how an individual's legal name (or Alias), which can now exceed
 VistA's limitation of 30 characters, is processed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MPIF
KEYWORDS: CIRN
KEYWORDS: CLINICAL INFO RESOURCE NETWORK
KEYWORDS: LEGAL NAME
KEYWORDS: NAME
KEYWORDS: ALIAS
KEYWORDS: 984.8
KEYWORDS: MPIF(984.8
KEYWORDS: DG
KEYWORDS: REGISTRATION
KEYWORDS: RG
COMPONENT/ENTRY POINT: $$GETFLAG
 COMPONENT DESCRIPTION:   This function returns a value of 1,0 or null that
 defines how Names and/or Aliases should be processed.  
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
 SUBSCRIBING DETAILS:   The CLINICAL INFO RESOURCE NETWORK package will access
 the API $$GETFLAG^MPIFNAMC to retrieve the Name Components flag that
 determines how Legal Names (or Aliases) that may exceed the 30-character
 limitation in VistA should be processed.  
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   The REGISTRATION package will access the API
 $$GETFLAG^MPIFNAMC to retrieve the Name Components flag that determines how
 Legal Names (or Aliases) that may exceed the 30-character limitation in VistA 
 should be processed.  
  DATE ACTIVATED: APR 25, 2019

NUMBER: 7005                            IA #: 7005
  DATE CREATED: DEC 17, 2018
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU ANCILLARY PACKAGE MESSAGE
  REMOTE PROCEDURE: TIU ANCILLARY PACKAGE MESSAGE
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JAN 29, 2019

NUMBER: 7006                            IA #: 7006
  DATE CREATED: DEC 26, 2018
  CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE
  USAGE: Controlled Subscription        NAME: TEST
  STATUS: Withdrawn

NUMBER: 7007                            IA #: 7007
  DATE CREATED: JAN 17, 2019            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  ROUTINE: IBR
  NAME: IBR TO RELEASE CHARGES FROM ACCOUNTS RECEIVABLE
  ID: IBR
 GENERAL DESCRIPTION:   The IB routine ^IBR can be used to release "ON HOLD"
 charges to ACCOUNTS RECEIVABLE (AR).  E-Payments nightly process needs to use
 this call as part of the first party auto-decrease logic, so that first party
 charges can be released then auto-decreased when the matching third party bill
 is received.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: IBR
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   ACCOUNTS RECIEVABLE to call ^IBR to release 'ON-HOLD'
 charges.  
  DATE ACTIVATED: MAR 17, 2020

NUMBER: 7008                            IA #: 7008
  DATE CREATED: JAN 24, 2019            CUSTODIAL PACKAGE: 1
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DDE
  NAME: Entity mapping APIs             ID: DDE
 GENERAL DESCRIPTION:   APIs that can be used with the ENTITY file (#1.5) to
 retrieve data from VA FileMan files and format them in either XML or JSON.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ENTITY
KEYWORDS: SDA
COMPONENT/ENTRY POINT: $$GET1()
 COMPONENT DESCRIPTION:   This extrinsic function retrieves a single record and
 returns a string containing the data.  
  
 $$GET1^DDE(RESOURCE, ID,, MTYPE, ERROR) 
VARIABLES: RESOURCE                     TYPE: Input
 VARIABLES DESCRIPTION:   (Required)  The ien or name of the ENTITY file (#1.5)
 record to use.  
VARIABLES: ID                           TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The record ien or name to use to retrieve
 data.  
VARIABLES: MTYPE                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional)  Format used for returned data;  0=JSON
 (default) or 1=XML 
VARIABLES: ERROR                        TYPE: Both
 VARIABLES DESCRIPTION:   (Optional)  The name of a closed root reference that
 is used to return error messages.  
COMPONENT/ENTRY POINT: GET()
 COMPONENT DESCRIPTION:   This procedure can retrieve multiple records using
 the QUERY array or a single record using the ID parameter.  It will return an
 array containing the data.  
  
 GET^DDE(RESOURCE, ID, QUERY, MTYPE, MAX, RESULT, ERROR) 
VARIABLES: RESOURCE                     TYPE: Input
 VARIABLES DESCRIPTION:   (Required)  The ien or name of the ENTITY file (#1.5)
 record to use.  
VARIABLES: ID                           TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The record ien or name to use to retrieve
 data.  
VARIABLES: QUERY                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional)  An array used to lookup multiple records 
 via the GET QUERY ROUTINE: 
  QUERY("start") start date.time for a search of records 
  QUERY("stop")  stop date.time for a search of records 
  QUERY("patient")  DFN or DFN;ICN of a patient 
  QUERY(x) where x is any developer-defined lookup value 
VARIABLES: MTYPE                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional)  Format used for returned data;  0=JSON
 (default) or 1=XML 
VARIABLES: MAX                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional)  The maximum number of items to return.  
VARIABLES: RESULT                       TYPE: Both
 VARIABLES DESCRIPTION:   (Optional)  The name of a closed root reference that
 is used to return data.  
VARIABLES: ERROR                        TYPE: Both
 VARIABLES DESCRIPTION:   (Optional)  The name of a closed root reference that
 is used to return error messages.  
  DATE ACTIVATED: MAR 08, 2019

NUMBER: 7009                            IA #: 7009
  DATE CREATED: JAN 24, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DGPF PRF EVENT
 GENERAL DESCRIPTION:   The DGPF PRF EVENT protocol is an event protocol that
 will notify subscribers when Patient Record Flags are assigned or modified.
 This agreement documents the protocols allowed to subscribe to this event.  
  
 The following data is available to subscribers: 
  
  DGIEN = PRF ASSIGNMENT (#26.13) file ien 
  DGPRF = Output array containing assignment record field values 
          Subscript          Field#   Data 
          --------------     -------  ---------------------
          "DFN"              .01      internal^external 
          "FLAG"             .02      internal^external 
          "STATUS"           .03      internal^external 
          "OWNER"            .04      internal^external 
          "ORIGSITE"         .05      internal^external 
          "REVIEWDT"         .06      internal^external 
          "NARR",line#,0     1        character string 
          "DBRS#",line#      2;.01    internal^external 
          "DBRS OTHER",line# 2;.02    internal^external 
          "DBRS DATE",line#  2;.03    internal^external 
          "DBRS SITE",line#  2;.04    internal^external 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   The VPR subscriber protocol is VPR PRF EVENTS,
 effective with VPR*1*23.  
  DATE ACTIVATED: AUG 19, 2021

NUMBER: 7010                            IA #: 7010
  DATE CREATED: JAN 24, 2019            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Other
  NAME: IBCN NEW INSURANCE
 GENERAL DESCRIPTION:   The IBCN NEW INSURANCE event driver will be invoked
 whenever a new insurance type entry is created in the patient file, so that
 necessary actions can take place when a new insurance policy is added for a
 patient.  
  
 This agreement documents the protocols allowed to subscribe to this event.  
 Supported HL7 utilities may be used to read the attached message; the message
 itself and HL7 application variables may not be altered.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   The VPR Item protocol is VPR IBCN EVENTS 

NUMBER: 7011                            IA #: 7011
  DATE CREATED: JAN 24, 2019            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: LR7O AP EVSEND OR
 GENERAL DESCRIPTION:   The LR7O AP EVSEND OR protocol is used to pass
 pathology orders and results from Lab to CPRS and other packages.  
  
 This agreement documents the protocols allowed to subscribe to this event.  
 Supported HL7 utilities may be used to read the attached message; the message
 itself and HL7 application variables may not be altered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   The VPR Item protocol is VPR LRAP EVENTS 
  DATE ACTIVATED: FEB 05, 2019

NUMBER: 7012                            IA #: 7012
  DATE CREATED: JAN 24, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: SCMC PATIENT TEAM CHANGES
 GENERAL DESCRIPTION:   The SCMC PATIENT TEAM CHANGES protocol is fired off
 whenever the Patient Team Assignment File (#404.42) is updated.  
  
 This agreement documents the protocols allowed to subscribe to this event.  
 Supported HL7 utilities may be used to read the attached message; the message
 itself and HL7 application variables may not be altered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   The VPR Item protocol is VPR PCMM TEAM 
  DATE ACTIVATED: AUG 26, 2021

NUMBER: 7013                            IA #: 7013
  DATE CREATED: JAN 24, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: SCMC PATIENT TEAM POSITION CHANGES
 GENERAL DESCRIPTION:   The SCMC PATIENT TEAM POSITION CHANGES protocol is
 fired off whenever the Patient Team Position Assignment file (#404.43) is
 updated.  
  
 This agreement documents the protocols allowed to subscribe to this event.  
 Supported HL7 utilities may be used to read the attached message; the message
 itself and HL7 application variables may not be altered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   The VPR Item protocol is VPR PCMM TEAM POSITION 
  DATE ACTIVATED: FEB 04, 2019

NUMBER: 7014                            IA #: 7014
  FILE NUMBER: 1.5                      GLOBAL ROOT: DDE(
  DATE CREATED: JAN 30, 2019            CUSTODIAL PACKAGE: 1
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Entity File Cross Reference
  ID: DDE(
 GENERAL DESCRIPTION:   The ENTITY file (#1.5) has two cross reference that
 will be available to approved applications.  These cross references allows an
 application to lookup a record by DATA MODEL field (#.06), DISPLAY NAME field
 (#.1), and DEFAULT FILE NUMBER field (#.02).  Currently, there is only two
 Data Models: FHIR and SDA. The cross reference will look like: 
  
  ^DDE("FHIR",display name, file number, ien)="" 
  ^DDE("SDA", display name, file number, ien)="" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ENTITY
KEYWORDS: SDA
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   The Virtual Patient Record (VPR) application uses the
 SDA cross reference.  
  DATE ACTIVATED: MAR 08, 2019

NUMBER: 7015                            IA #: 7015
  FILE NUMBER: 8991.6                   GLOBAL ROOT: XTV(8991.6
  DATE CREATED: FEB 01, 2019            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: XUEPCS DATA FILE                ID: XTV(8991.6
 GENERAL DESCRIPTION:   Outpatient Pharmacy is granted permission to enter the
 following fields.  
  
       Field #     Node;Piece          Field Name 
         .01          0;1           NAME 
         .02          0;2           EDITED BY 
         .03          0;3           FIELD EDITED 
         .04          0;4           ORIGINAL DATA 
         .05          0;5           EDITED DATA 
         .06          0;6           DATE/TIME EDITED 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DEA
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 7016                            IA #: 7016
  FILE NUMBER: 8991.7                   GLOBAL ROOT: XTV(8991.7
  DATE CREATED: FEB 01, 2019            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: XUEPCS PSDRPH AUDIT FILE
  ID: XTV(8991.7
 GENERAL DESCRIPTION:   Outpatient Pharmacy is granted permission to enter the
 following fields.  
  
       Field #     Node;Piece          Field Name 
         .01          0;1           NAME 
         .02          0;2           EDITED BY 
         .03          0;3           ALLOCATION STATUS 
         .04          0;4           DATE/TIME EDITED 
  
  Revision History - 
  10/16/24 The WebVRAM and Outpatient Pharmacy development teams are working
 together on the release of the RPC and the WebVRAM GUI changes to invoke the
 RPC. The Pharmacy patch is PSO*7*732 and the WEBG patch is WEBG*3*21. The ICR
 that authorizes Pharmacy's reference to file 8991.7 is #7016. This RPC
 performs the same function as the Allocate/De-Allocate of PSDRPH Key (Audited)
 [PSO EPCS PSDRPH KEY]. WebVRAM's subscription is valid only as long as ICR
 7492 is active.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DEA
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   Added 10/16/24 effective with patches PSO*7*732 and
 WEBG*3*21 
  DATE ACTIVATED: OCT 16, 2024

NUMBER: 7017                            IA #: 7017
  FILE NUMBER: 361.1                    GLOBAL ROOT: IBM(361.1,
  DATE CREATED: FEB 07, 2019            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ERA DETAIL
  ID: IBM(361.1,
GLOBAL REFERENCE: IBM(361.1,
FIELD NUMBER: 104                       FIELD NAME: ERA DETAIL
  LOCATION: 102;3                       ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This IA will allow read and write access to the ERA
 DETAIL field (#104) in the EXPLANATION OF BENEFITS file (#361.1).  This field
 is to be used to track Explanation of Benefits (EOB) data.  
  
 The field label: 
  
 ERA DETAIL                     361.1,104    FREE TEXT 
      
               Enter the ERA detail reference in the form nn,nnnnn, 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EXPLANATION OF BENEFITS
KEYWORDS: 361.1
KEYWORDS: ERA DETAIL
KEYWORDS: INPATIENT BILLING
KEYWORDS: ACCOUNTS RECEIVABLE
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   This will allow read and write access to ERA DETAIL
 field (#104).  
  DATE ACTIVATED: MAR 17, 2020

NUMBER: 7018                            IA #: 7018
  DATE CREATED: FEB 13, 2019
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7018
  STATUS: Pending

NUMBER: 7019                            IA #: 7019
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: FEB 26, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Scheduling access to address data
  ID: DPT(
GLOBAL REFERENCE: DPT(D0
FIELD NUMBER: .111                      FIELD NAME: STREET ADDRESS [LINE 1]
  LOCATION: .11;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1112                     FIELD NAME: ZIP+4
  LOCATION: .11;12                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .112                      FIELD NAME: STREET ADDRESS [LINE 2]
  LOCATION: .11;2                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .113                      FIELD NAME: STREET ADDRESS [LINE 3]
  LOCATION: .11;3                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .114                      FIELD NAME: CITY
  LOCATION: .11;4                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .115                      FIELD NAME: STATE
  LOCATION: .11;5                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .116                      FIELD NAME: ZIP CODE
  LOCATION: .11;6                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .117                      FIELD NAME: COUNTY
  LOCATION: .11;7                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1171                     FIELD NAME: PROVINCE
  LOCATION: .11;8                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1172                     FIELD NAME: POSTAL CODE
  LOCATION: .11;9                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1173                     FIELD NAME: COUNTRY
  LOCATION: .11;10                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .118                      FIELD NAME: ADDRESS CHANGE DT/TM
  LOCATION: .11;13                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .119                      FIELD NAME: ADDRESS CHANGE SOURCE
  LOCATION: .11;14                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .12                       FIELD NAME: ADDRESS CHANGE SITE
  LOCATION: .11;15                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .121                      FIELD NAME: BAD ADDRESS INDICATOR
  LOCATION: .11;16                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .12105                    FIELD NAME: TEMPORARY ADDRESS ACTIVE?
  LOCATION: .121;9                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1211                     FIELD NAME: TEMPORARY STREET [LINE 1]
  LOCATION: .121;1                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .12111                    FIELD NAME: TEMPORARY ADDRESS COUNTY
  LOCATION: .121;11                     ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .12112                    FIELD NAME: TEMPORARY ZIP+4
  LOCATION: .121;12                     ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .12113
  FIELD NAME: TEMPORARY ADDRESS CHANGE DT/TM
  LOCATION: .121;13                     ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .12114
  FIELD NAME: TEMPORARY ADDRESS CHANGE SITE
  LOCATION: .121;14                     ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1212                     FIELD NAME: TEMPORARY STREET [LINE 2]
  LOCATION: .121;2                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1213                     FIELD NAME: TEMPORARY STREET [LINE 3]
  LOCATION: .121;3                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1214                     FIELD NAME: TEMPORARY CITY
  LOCATION: .121;4                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1215                     FIELD NAME: TEMPORARY STATE
  LOCATION: .121;5                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1216                     FIELD NAME: TEMPORARY ZIP CODE
  LOCATION: .121;6                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1217                     FIELD NAME: TEMPORARY ADDRESS START DATE
  LOCATION: .121;7                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1218                     FIELD NAME: TEMPORARY ADDRESS END DATE
  LOCATION: .121;8                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1219                     FIELD NAME: TEMPORARY PHONE NUMBER
  LOCATION: .121;10                     ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .122                      FIELD NAME: ADDRESS CHANGE USER
  LOCATION: .11;17                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1221                     FIELD NAME: TEMPORARY ADDRESS PROVINCE
  LOCATION: .122;1                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1222
  FIELD NAME: TEMPORARY ADDRESS POSTAL CODE
  LOCATION: .122;2                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1223                     FIELD NAME: TEMPORARY ADDRESS COUNTRY
  LOCATION: .122;3                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .131                      FIELD NAME: PHONE NUMBER [RESIDENCE]
  LOCATION: .13;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1311
  FIELD NAME: CELLULAR NUMBER CHANGE SOURCE
  LOCATION: .13;10                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1312                     FIELD NAME: PAGER NUMBER CHANGE DT/TM
  LOCATION: .13;12                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1313                     FIELD NAME: PAGER NUMBER CHANGE SOURCE
  LOCATION: .13;13                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1314                     FIELD NAME: PAGER NUMBER CHANGE SITE
  LOCATION: .13;14                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1315                     FIELD NAME: CONFIDENTIAL PHONE NUMBER
  LOCATION: .13;15                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1316                     FIELD NAME: EMAIL ADDRESS INDICATOR
  LOCATION: .13;16                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1317
  FIELD NAME: EMAIL ADDRESS INDICATOR DT/TM
  LOCATION: .13;17                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .132                      FIELD NAME: PHONE NUMBER [WORK]
  LOCATION: .13;2                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1321
  FIELD NAME: RESIDENCE NUMBER CHANGE DT/TM
  LOCATION: .132;1                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1322
  FIELD NAME: RESIDENCE NUMBER CHANGE SOURCE
  LOCATION: .132;2                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1323                     FIELD NAME: RESIDENCE NUMBER CHANGE SITE
  LOCATION: .132;3                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .133                      FIELD NAME: EMAIL ADDRESS
  LOCATION: .13;3                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .134                      FIELD NAME: PHONE NUMBER [CELLULAR]
  LOCATION: .13;4                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .135                      FIELD NAME: PAGER NUMBER
  LOCATION: .13;5                       ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
 ************************************************************************
 *                                                                      *
 *  This is a temporary ICR for the production VistA Scheduling (VS)    * * 
 GUI software.                                                       * *  The
 need for this ICR was identified from the VS Sustainment Team   * *  reviewing
 the VistA Scheduling Enhancement (VSE) software that was  * *  released
 nationally without approved ICRs.  This temporary ICR      * *  represents the
 situation, where the Custodian package experts       * *  requested changes to
 the production software to use approved        * *  APIs, which requires a
 future VS patch. This temporary ICR will     * *  expire when the production
 code is modified to the use approved     * *  APIs                             
                                   * 
 *                                                                      *
 ************************************************************************
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   A Veteran's address information is displayed on VS GUI
 when making appointments.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 10/19/2022, effective with DSSV 1.1 DSS Class 2
 product Document Only DSSV is using field .121 from the PATIENT (#2) file with
 Read w/FM.  
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI
 SUBSCRIBING DETAILS:   Added 9/6/24, effective with DSIR*8.2*16 to read
 TEMPORARY ADDRESS Fields .12105, .1217 and .1218 with FILEMAN. 
 DGETS^DIQ(2,DSIRIFNS,".01;.02;.03;.09;.12105;.1217; 
 .1218;.132;.351","IE","DSIRGET","DSIRMSG") 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   PROSTHETICS VISION 4 SIGHT II Added 04/22/25, effective
 with PROSTHETICS VISION 4 SIGHT II patch RMPV*1*1, the Prosthetics package
 requires Read w/FM to fields .111, .112, .113, .114, .115, and .116 
  DATE ACTIVATED: MAY 21, 2019

NUMBER: 7020                            IA #: 7020
  FILE NUMBER: 26.11                    GLOBAL ROOT: DGPF(26.11
  DATE CREATED: FEB 26, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Scheduling access to patient flags (local)
  ID: DGPF(26.11
GLOBAL REFERENCE: DGPF(26.11,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VS GUI displays patient flags to schedulers.  It
 requires FileMan read access to the following fields: 
  
 .01 Name .02 Status 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: APR 17, 2019

NUMBER: 7021                            IA #: 7021
  FILE NUMBER: 26.15                    GLOBAL ROOT: DGPF(26.15
  DATE CREATED: FEB 26, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VS GUI access to Patient flags (national)
  ID: DGPF(26.15
GLOBAL REFERENCE: DGPF(26.15,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VS GUI displays patient flags to schedulers.  It
 requires FileMan read access to the following fields: 
  
 .01 Name .02 Status 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: APR 17, 2019

NUMBER: 7022                            IA #: 7022
  FILE NUMBER: 26.13                    GLOBAL ROOT: DGPF(26.13
  DATE CREATED: FEB 26, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VS GUI access to Patient Flag Assignment
  ID: DGPF(26.13
GLOBAL REFERENCE: DGPF(26.13,D0
FIELD NUMBER: .03                       FIELD NAME: STATUS
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   VS GUI displays patient flags to schedulers.  It
 requires FileMan read access to the following fields: 
  
 .03 Status 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: MAY 21, 2019

NUMBER: 7023                            IA #: 7023
  FILE NUMBER: 27.11                    GLOBAL ROOT: DGEN(27.11
  DATE CREATED: FEB 26, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VS GUI access to patient enrollment data
  ID: DGEN(27.11
GLOBAL REFERENCE: DGEN(27.11,D0
FIELD NUMBER: .07                       FIELD NAME: ENROLLMENT PRIORITY
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: .12                       FIELD NAME: ENROLLMENT SUB-GROUP
  LOCATION: 0;12                        ACCESS: Read w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI displays patient enrollment data to schedulers.  
  DATE ACTIVATED: APR 17, 2019

NUMBER: 7024                            IA #: 7024
  FILE NUMBER: 40.8                     GLOBAL ROOT: DG(40.8
  DATE CREATED: FEB 26, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VS GUI access to Medical Center Division fields
  ID: DG(40.8
GLOBAL REFERENCE: DG(40.8,D0
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
FIELD NUMBER: 1                         FIELD NAME: FACILITY NUMBER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 30.01                     FIELD NAME: ADDRESS LOCATION ON LETTERS
  LOCATION: LTR;1                       ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   VS GUI uses data from file #40.8 - Medical Center
 Division.  It requires FileMan and direct global read access to the following
 fields: 
  
   .01 Name 
   .07 Institution 
     1 Facility Number 30.01 Address Location on Letters 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
SUBSCRIBING PACKAGE: HOME BASED PRIMARY CARE
 SUBSCRIBING DETAILS:   Added 6/8/21, Effective with HBH*1.0*32. Home Based
 Primary Care (HBPC - formerly known as HOSPITAL BASED HOME CARE) contains a
 "parent site" multiple field in the HBHC SYSTEM PARAMETERS (#631.9) file. The
 parent sites must be predefined in the MEDICAL CENTER DIVISION (#40.8) file.  
 Transmission logic to AITC will determine the parent site for patients and 
 visits from the INSTITUTION FILE POINTER (#.07) field. The station number of
 that parent site is transmitted to AITC.  
SUBSCRIBING PACKAGE: AUTOMATED LAB INSTRUMENTS
 SUBSCRIBING DETAILS:   Added 11/15/23, effective with LA*5.2*104 patch (and
 LR*5.2*568), to be released in early 2024 by the HDSO Sustainment Project
 team. The AUTOMATED LAB INSTRUMENTS package will enable sites to specify a
 reporting facility for Point of Care (POC) results if the default reporting
 facility is not correct. Parameter LR POC REPORTING LAB may be defined by
 SYSTEM or DIVISION using a pointer to the MEDICAL CENTER DIVISION file (#40.8) 
 to get the value from the INSTITUTION FILE POINTER (#.07) field in file #40.8
 so that routine LRVRPOC can determine a division's institution.  
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   Added 11/15/23, effective with LR*5.2*568 patch (and
 LA*5.2*104), to be released in early 2024 by the HDSO Sustainment Project
 team. The LAB SERVICE package will enable sites to specify a reporting
 facility for Point of Care (POC) results if the default reporting facility is
 not correct. Parameter LR POC REPORTING LAB may be defined by SYSTEM or 
 DIVISION using a pointer to the MEDICAL CENTER DIVISION file (#40.8) to get
 the value from the INSTITUTION FILE POINTER (#.07)field in file #40.8 so that
 routine LRVRPOC can determine a division's institution.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 5/29/25 effective with 1.5P6 patch to retrieve
 Name, Institution File POI and Facility Number.  
  DATE ACTIVATED: NOV 15, 2023

NUMBER: 7025                            IA #: 7025
  FILE NUMBER: 43                       GLOBAL ROOT: DG(43
  DATE CREATED: FEB 27, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VS GUI access to MAS Parameters (#43) file
  ID: DG(43
GLOBAL REFERENCE: DG(43,D0
FIELD NUMBER: 16                        FIELD NAME: DOMICILIARY WARDS?
  LOCATION: 0;21                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 722                       FIELD NAME: USE TEMPORARY ADDRESS
  LOCATION: BT;3                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   The Temporary Address field is referenced when printing
 appointment letters.  
  
 The Domiciliary Wards field is used in the calculation of appointment status.  
  DATE ACTIVATED: APR 17, 2019

NUMBER: 7026                            IA #: 7026
  FILE NUMBER: 101                      GLOBAL ROOT: ORD(101
  DATE CREATED: FEB 27, 2019
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: VS GUI access to Protocol (#101) fields
  ID: ORD(101
GLOBAL REFERENCE: ORD(101,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ORD(101,D0,2,D1
FIELD NUMBER: .01                       FIELD NAME: SYNONYM
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   VS GUI uses data from file #101 - Protocol.  It
 requires FileMan and direct global read access to the following fields: 
  
   .01 Name 
  1.1  Synonym multiple 
   .01 Synonym 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Protocol fields used to determine consult urgency by
 SDECRMG2 URGENCY RPC.  

NUMBER: 7027                            IA #: 7027
  FILE NUMBER: 150.9                    GLOBAL ROOT: DIC(150.9
  DATE CREATED: FEB 27, 2019
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  NAME: VS GUI access to Visit Tracking Parameters (#150.9)
  ID: DIC(150.9
GLOBAL REFERENCE: DIC(150.9,D0
FIELD NUMBER: 402                       FIELD NAME: SITE PART OF VISIT ID
  LOCATION: 4;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
 ************************************************************************
 *                                                                      *
 *  This is a temporary ICR for the production VistA Scheduling (VS)    * * 
 GUI software.                                                       * *  The
 need for this ICR was identified from the VS Sustainment Team   * *  reviewing
 the VistA Scheduling Enhancement (VSE) software that was  * *  released
 nationally without approved ICRs.  This temporary ICR      * *  represents the
 situation, where the Custodian package experts       * *  requested changes to
 the production software to use approved        * *  APIs, which requires a
 future VS patch. This temporary ICR will     * *  expire when the production
 code is modified to the use approved     * *  APIs                             
                                   * 
 *                                                                      *
 ************************************************************************
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   File 150.9 is referenced when a visit is generated in
 file #9000010.  

NUMBER: 7028                            IA #: 7028
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: FEB 27, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VS GUI access to Patient's next of kin and employer fields
  ID: DPT(
GLOBAL REFERENCE: DPT(D0
FIELD NUMBER: .211                      FIELD NAME: K-NAME OF PRIMARY NOK
  LOCATION: .21;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .211011                   FIELD NAME: K2-WORK PHONE NUMBER
  LOCATION: .211;11                     ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .211012
  FIELD NAME: SECONDARY NOK CHANGE DATE/TIME
  LOCATION: .212;2                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .212                      FIELD NAME: K-RELATIONSHIP TO PATIENT
  LOCATION: .21;2                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2125                     FIELD NAME: K-ADDRESS SAME AS PATIENT'S?
  LOCATION: .21;10                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .213                      FIELD NAME: K-STREET ADDRESS [LINE 1]
  LOCATION: .21;3                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .214                      FIELD NAME: K-STREET ADDRESS [LINE 2]
  LOCATION: .21;4                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .215                      FIELD NAME: K-STREET ADDRESS [LINE 3]
  LOCATION: .21;5                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .216                      FIELD NAME: K-CITY
  LOCATION: .21;6                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .217                      FIELD NAME: K-STATE
  LOCATION: .21;7                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .218                      FIELD NAME: K-ZIP CODE
  LOCATION: .21;8                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .219                      FIELD NAME: K-PHONE NUMBER
  LOCATION: .21;9                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2191                     FIELD NAME: K2-NAME OF SECONDARY NOK
  LOCATION: .211;1                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2192                     FIELD NAME: K2-RELATIONSHIP TO PATIENT
  LOCATION: .211;2                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .21925
  FIELD NAME: K2-ADDRESS SAME AS PATIENT'S?
  LOCATION: .211;10                     ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2193                     FIELD NAME: K2-STREET ADDRESS [LINE 1]
  LOCATION: .211;3                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2194                     FIELD NAME: K2-STREET ADDRESS [LINE 2]
  LOCATION: .211;4                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2195                     FIELD NAME: K2-STREET ADDRESS [LINE 3]
  LOCATION: .211;5                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2196                     FIELD NAME: K2-CITY
  LOCATION: .211;6                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2197                     FIELD NAME: K2-STATE
  LOCATION: .211;7                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2198                     FIELD NAME: K2-ZIP CODE
  LOCATION: .211;8                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2199                     FIELD NAME: K2-PHONE NUMBER
  LOCATION: .211;9                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2201                     FIELD NAME: E-ZIP+4
  LOCATION: .22;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2202                     FIELD NAME: D-ZIP+4
  LOCATION: .22;2                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2203                     FIELD NAME: K2-ZIP+4
  LOCATION: .22;3                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2204                     FIELD NAME: E2-ZIP+4
  LOCATION: .22;4                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2205                     FIELD NAME: EMPLOYER ZIP+4
  LOCATION: .22;5                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2206                     FIELD NAME: SPOUSE'S EMP ZIP+4
  LOCATION: .22;6                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .2207                     FIELD NAME: K-ZIP+4
  LOCATION: .22;7                       ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
 ************************************************************************
 *                                                                      *
 *  This is a temporary ICR for the production VistA Scheduling (VS)    * * 
 GUI software.                                                       * *  The
 need for this ICR was identified from the VS Sustainment Team   * *  reviewing
 the VistA Scheduling Enhancement (VSE) software that was  * *  released
 nationally without approved ICRs.  This temporary ICR      * *  represents the
 situation, where the Custodian package experts       * *  requested changes to
 the production software to use approved        * *  APIs, which requires a
 future VS patch. This temporary ICR will     * *  expire when the production
 code is modified to the use approved     * *  APIs                             
                                   * 
 *                                                                      *
 ************************************************************************
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI gathers and displays next of kin and employer
 information to schedulers.  
  DATE ACTIVATED: MAY 28, 2019

NUMBER: 7029                            IA #: 7029
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: FEB 27, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VS GUI access to Patient's eligibility information
  ID: DPT(
GLOBAL REFERENCE: DPT(D0
FIELD NUMBER: .301                      FIELD NAME: SERVICE CONNECTED?
  LOCATION: .3;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .302                      FIELD NAME: SERVICE CONNECTED PERCENTAGE
  LOCATION: .3;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .32103
  FIELD NAME: RADIATION EXPOSURE INDICATED?
  LOCATION: .321;3                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .32115                    FIELD NAME: PROJ 112/SHAD
  LOCATION: .321;15                     ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .3213
  FIELD NAME: AGENT ORANGE EXPOSURE LOCATION
  LOCATION: .321;13                     ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .322013                   FIELD NAME: SOUTHWEST ASIA CONDITIONS?
  LOCATION: .322;13                     ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .323                      FIELD NAME: PERIOD OF SERVICE
  LOCATION: .32;3                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .351                      FIELD NAME: DATE OF DEATH
  LOCATION: .351;1                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .361                      FIELD NAME: PRIMARY ELIGIBILITY CODE
  LOCATION: .36;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .39
  FIELD NAME: VETERAN CATASTROPHICALLY DISABLED?
  LOCATION: .39;6                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .525                      FIELD NAME: POW STATUS INDICATED?
  LOCATION: .52;5                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .5291                     FIELD NAME: COMBAT SERVICE INDICATED?
  LOCATION: .52;11                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 391                       FIELD NAME: TYPE
  LOCATION: TYPE;1                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1100.01                   FIELD NAME: FUGITIVE FELON FLAG
  LOCATION: FFP;1                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.372,D1
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
FIELD NUMBER: 4                         FIELD NAME: EXTREMITY AFFECTED
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: ORIGINAL EFFECTIVE DATE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: CURRENT EFFECTIVE DATE
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.02,D1
FIELD NUMBER: .01                       FIELD NAME: RACE INFORMATION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,DE,D1
FIELD NUMBER: .01                       FIELD NAME: ENROLLMENT CLINIC
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: CURRENT STATUS
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.06,D1
FIELD NUMBER: .01                       FIELD NAME: ETHNICITY INFORMATION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,E,D1
FIELD NUMBER: .01                       FIELD NAME: ELIGIBILITY
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: LONG ID
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: SHORT ID
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
 ************************************************************************
 *                                                                      *
 *  This is a temporary ICR for the production VistA Scheduling (VS)    * * 
 GUI software.                                                       * *  The
 need for this ICR was identified from the VS Sustainment Team   * *  reviewing
 the VistA Scheduling Enhancement (VSE) software that was  * *  released
 nationally without approved ICRs.  This temporary ICR      * *  represents the
 situation, where the Custodian package experts       * *  requested changes to
 the production software to use approved        * *  APIs, which requires a
 future VS patch. This temporary ICR will     * *  expire when the production
 code is modified to the use approved     * *  APIs                             
                                   * 
 *                                                                      *
 ************************************************************************
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI displays data about the Veteran to the scheduler
 that is needed to make and manage appointments.  
  DATE ACTIVATED: MAY 28, 2019

NUMBER: 7030                            IA #: 7030
  FILE NUMBER: 2.98                     GLOBAL ROOT: DPT(DFN,'S'
  DATE CREATED: FEB 28, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VS GUI access to patient appointment data
  ID: DPT(DFN,'S'
GLOBAL REFERENCE: DPT(DFN,'S',D0
FIELD NUMBER: .01                       FIELD NAME: CLINIC
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: LAB DATE/TIME
  LOCATION: 0;3                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: X-RAY DATE/TIME
  LOCATION: 0;4                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: EKG DATE/TIME
  LOCATION: 0;5                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: ROUTING SLIP PRINTED
  LOCATION: 0;6                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 8.5                       FIELD NAME: ROUTING SLIP PRINT DATE
  LOCATION: 0;13                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: PURPOSE OF VISIT
  LOCATION: 0;7                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 9.5                       FIELD NAME: APPOINTMENT TYPE
  LOCATION: 0;16                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 12
  FIELD NAME: AUTO-REBOOKED APPT. DATE/TIME
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: COLLATERAL VISIT
  LOCATION: 0;11                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: NO-SHOW/CANCELLED BY
  LOCATION: 0;12                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: NO-SHOW/CANCEL DATE/TIME
  LOCATION: 0;14                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 16                        FIELD NAME: CANCELLATION REASON
  LOCATION: 0;15                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 17                        FIELD NAME: CANCELLATION REMARKS
  LOCATION: R;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 19                        FIELD NAME: DATA ENTRY CLERK
  LOCATION: 0;18                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 20                        FIELD NAME: DATE APPT. MADE
  LOCATION: 0;19                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 21                        FIELD NAME: OUTPATIENT ENCOUNTER
  LOCATION: 0;20                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 25                        FIELD NAME: SCHEDULING REQUEST TYPE
  LOCATION: 0;26                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 26                        FIELD NAME: NEXT AVA. APPT. INDICATOR
  LOCATION: 0;26                        ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 27                        FIELD NAME: DESIRED DATE OF APPOINTMENT
  LOCATION: 1;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 28                        FIELD NAME: FOLLOW-UP VISIT
  LOCATION: 1;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 100                       FIELD NAME: CURRENT STATUS
  LOCATION: COMPUTED                    ACCESS: Read w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI creates appointments in the patient file
 appointment multiple.  It also reads the data from the multiple for display in
 its expand entry view.  
  DATE ACTIVATED: APR 17, 2019

NUMBER: 7031                            IA #: 7031
  FILE NUMBER: 396.1                    GLOBAL ROOT: DVB(396.1
  DATE CREATED: FEB 28, 2019
  CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VS GUI access to AMIE Site Parameters (#396.1)
  ID: DVB(396.1
GLOBAL REFERENCE: DVB(396.1,D0
FIELD NUMBER: 17
  FIELD NAME: APPT LINKING ENHANCED DIALOGUE
  LOCATION: 0;18                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Field is returned by the SDEC GETFAC RPC to return data
 about the facilities accessible to the user.  
  DATE ACTIVATED: MAY 21, 2019

NUMBER: 7032                            IA #: 7032
  DATE CREATED: FEB 28, 2019
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  ROUTINE: AUPNPAT                      NAME: VS GUI access to routine AUPNPAT
  ID: AUPNPAT
 GENERAL DESCRIPTION:   
 ************************************************************************
 *                                                                      *
 *  This is a temporary ICR for the production VistA Scheduling (VS)    * * 
 GUI software.                                                       * *  The
 need for this ICR was identified from the VS Sustainment Team   * *  reviewing
 the VistA Scheduling Enhancement (VSE) software that was  * *  released
 nationally without approved ICRs.  This temporary ICR      * *  represents the
 situation, where the Custodian package experts       * *  requested changes to
 the production software to use approved        * *  APIs, which requires a
 future VS patch. This temporary ICR will     * *  expire when the production
 code is modified to the use approved     * *  APIs                             
                                   * 
 *                                                                      *
 ************************************************************************
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: START
 COMPONENT DESCRIPTION:   Extracts sex, date of birth, date of death (if
 present) and calculates age at death or today if still alive.  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to Patient (#2) file 
VARIABLES: AUPNSEX                      TYPE: Output
 VARIABLES DESCRIPTION:   Patient's sex 
VARIABLES: AUPNDOB                      TYPE: Output
 VARIABLES DESCRIPTION:   Patient's date of birth 
VARIABLES: AUPNDOD                      TYPE: Output
 VARIABLES DESCRIPTION:   Patient's date of death 
VARIABLES: AUPNDAYS                     TYPE: Output
 VARIABLES DESCRIPTION:   Patient's age at death or current if still alive 
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   AUPNPAT called to get select data about the patient. 
 The routine is called without a tag.  START is the first tag in the routine so
 a call to AUPNPAT is equivalent to calling START^AUPNPAT.  

NUMBER: 7033                            IA #: 7033
  DATE CREATED: FEB 28, 2019
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  ROUTINE: AUPNVSIT                     NAME: VS GUI access to routine AUPNVSIT
  ID: AUPNVSIT
 GENERAL DESCRIPTION:   
 ************************************************************************
 *                                                                      *
 *  This is a temporary ICR for the production VistA Scheduling (VS)    * * 
 GUI software.                                                       * *  The
 need for this ICR was identified from the VS Sustainment Team   * *  reviewing
 the VistA Scheduling Enhancement (VSE) software that was  * *  released
 nationally without approved ICRs.  This temporary ICR      * *  represents the
 situation, where the Custodian package experts       * *  requested changes to
 the production software to use approved        * *  APIs, which requires a
 future VS patch. This temporary ICR will     * *  expire when the production
 code is modified to the use approved     * *  APIs                             
                                   * 
 *                                                                      *
 ************************************************************************
  
 VSIT01 validates the date of visit so that it is not in the future, after the
 patient's death or before the patient's birth.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: VSIT01
 COMPONENT DESCRIPTION:   Validates visit date.  
VARIABLES: AUPNPAT                      TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to patient file (#2) entry 
VARIABLES: AUPNDOB                      TYPE: Input
 VARIABLES DESCRIPTION:   Patient's date of birth 
VARIABLES: AUPNDOD                      TYPE: Input
 VARIABLES DESCRIPTION:   Patient's date of death or null 
VARIABLES: X                            TYPE: Both
 VARIABLES DESCRIPTION:   Proposed date of visit.  X is killed by VSIT01 if the
 date is invalid.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Called to validate visit date.  

NUMBER: 7034                            IA #: 7034
  DATE CREATED: FEB 28, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGNFUNC
  NAME: VS GUI access to routine DGNFUNC
  ID: DGNFUNC
 GENERAL DESCRIPTION:   $$FML^DGNFUNC returns the patient's name formatted in
 'First Middle Last Suffix' format.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: FML
 COMPONENT DESCRIPTION:   Extrinsic function that returns a formatted patient
 name.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to patient file (#2) entry 
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Called $$FML^DGNFUNC to obtain formatted patient's name
 for letters.  
  DATE ACTIVATED: APR 17, 2019

NUMBER: 7035                            IA #: 7035
  DATE CREATED: MAR 11, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGPMV10                      NAME: VS GUI access to DGPMV10 routine
  ID: DGPMV10                           STATUS: Pending
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: INP
 COMPONENT DESCRIPTION:   Gathers data about patient movement for display in
 expand entry.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file (#2) pointer.  
VARIABLES: VAIP(D)                      TYPE: Input
 VARIABLES DESCRIPTION:   VAIP("D") needs to be set to "L" 
VARIABLES: VAX(DAT)                     TYPE: Output
 VARIABLES DESCRIPTION:   Date automatically set to NOW 
VARIABLES: X                            TYPE: Output
VARIABLES: DGPMCD                       TYPE: Output
 VARIABLES DESCRIPTION:   Date and time of last movement (FM) 
VARIABLES: DGPMVI                       TYPE: Output
 VARIABLES DESCRIPTION:   Array showing details of last inpatient movement.  
                       DGPMVI(1)=IEN of last pt movement from file #405 
                       DGPMVI(2)=(#.02) TRANSACTION [2P:405.3] 
                       DGPMVI(3)=Date of last movement in format 
                        "FM^External date@Time" DGPMVI(4)=(#.18) MAS 
                        MOVEMENT TYPE [18P:405.2] DGPMVI(5)=(#.06) WARD 
                        LOCATION [6P:42] DGPMVI(6)=(#.07) ROOM-BED 
                        [7P:405.4] DGPMVI(13)=(#.14) ADMISSION/CHECK-IN 
                        MOVEMENT [14P:405] DGPMVI(13,1)=Details about the 
                        Admission/check-in movement DGPMVI(17)=(#.17) 
                        DISCHARGE/CHECK-OUT MOVEMENT [17P:405] 
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Expand entry inquiry uses this routine to gather and
 display data about an appointment.  

NUMBER: 7036                            IA #: 7036
  DATE CREATED: MAR 12, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGSEC4
  NAME: VS GUI access to DGSEC4 routine
  ID: DGSEC4
 GENERAL DESCRIPTION:   
 ************************************************************************
 *                                                                      *
 *  This is a temporary ICR for the production VistA Scheduling (VS)    * * 
 GUI software.                                                       * *  The
 need for this ICR was identified from the VS Sustainment Team   * *  reviewing
 the VistA Scheduling Enhancement (VSE) software that was  * *  released
 nationally without approved ICRs.  This temporary ICR      * *  represents the
 situation, where the Custodian package experts       * *  requested changes to
 the production software to use approved        * *  APIs, which requires a
 future VS patch. This temporary ICR will     * *  expire when the production
 code is modified to the use approved     * *  APIs                             
                                   * 
 *                                                                      *
 ************************************************************************
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: OWNREC
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file pointer.  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   Scheduler's DUZ 
VARIABLES: DGMSG                        TYPE: Input
 VARIABLES DESCRIPTION:   Flag that tells the code to return a message.  
VARIABLES: DGREC                        TYPE: Output
 VARIABLES DESCRIPTION:   Array with the results.  
COMPONENT/ENTRY POINT: SENS
 COMPONENT DESCRIPTION:   Subroutine that returns sensitive information flags
 about a patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient pointer 
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   Scheduler's DUZ 
VARIABLES: DGSENS                       TYPE: Output
 VARIABLES DESCRIPTION:   Array containing sensitive information flags about
 the patient.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI uses DGSEC4 to determine if the scheduler is
 attempting to access his/her own record or if the record is for a sensitive
 patient.  The GUI prevents access to the scheduler's own record and displays
 appropriate warnings for sensitive patients.  
  DATE ACTIVATED: MAY 21, 2019

NUMBER: 7037                            IA #: 7037
  DATE CREATED: MAR 12, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGUTL3                       NAME: VS GUI access to routine DGUTL3
  ID: DGUTL3                            STATUS: Pending
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: BADADR
 COMPONENT DESCRIPTION:   Extrinsic function.  Returns set of codes from field
 .121 of file #2.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient pointer.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI uses the BADADR extrinsic function in DGUTL3
 when printing appointment letters.  

NUMBER: 7038                            IA #: 7038
  DATE CREATED: MAR 13, 2019
  CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DVBCCNNS
  NAME: VS GUI access to routine DVBCCNNS
  ID: DVBCCNNS                          STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CANCEL
VARIABLES: DVBALKDA                     TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file #396.95 
VARIABLES: DVBASTAT                     TYPE: Input
 VARIABLES DESCRIPTION:   Appointment status 
COMPONENT/ENTRY POINT: KVARS
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI uses routine DVBCCNNS to cancel a C&P
 appointment and to clean up variables created during the process.  
  DATE ACTIVATED: MAY 21, 2019

NUMBER: 7039                            IA #: 7039
  DATE CREATED: MAR 13, 2019
  CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DVBCMKLK
  NAME: VS GUI access to routine DVBCMKLK
  ID: DVBCMKLK                          STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: KVARS
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI uses DVBCMKLK to clean up variables created
 during appointment processing for C&P appointments.  
  DATE ACTIVATED: MAY 21, 2019

NUMBER: 7040                            IA #: 7040
  DATE CREATED: MAR 13, 2019
  CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DVBCUTA3
  NAME: VS GUI access to routine DVBCUTA3
  ID: DVBCUTA3                          STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LNKARY
VARIABLES: REQDA                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to 2507 request file (#396.3).  
VARIABLES: DVBADFN                      TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to patient file (#2).  
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   Array containing data from AMIE C&P Exam Tracking
 file (#396.95).  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI uses routine DVBCUTA3 to set up the link array
 for a C&P appointment 
  DATE ACTIVATED: MAY 21, 2019

NUMBER: 7041                            IA #: 7041
  DATE CREATED: MAR 13, 2019
  CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DVBCUTA4
  NAME: VS GUI access to routine DVBCUTA4
  ID: DVBCUTA4                          STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ENHNC
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI uses the ENHNC extrinsic function in DVBCUTA4 to
 return the event driver dialog mode from the AMIE Site Parameter file
 (#396.1).  
  DATE ACTIVATED: MAY 28, 2019

NUMBER: 7042                            IA #: 7042
  DATE CREATED: MAR 13, 2019
  CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DVBCUTL5
  NAME: VS GUI access to routine DVBCUTL5
  ID: DVBCUTL5                          STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SDEVTXST
COMPONENT/ENTRY POINT: SDEVTSPC
VARIABLES: DVBAPCE                      TYPE: Input
 VARIABLES DESCRIPTION:   Piece number in AFTER event array.  
VARIABLES: SDHDL                        TYPE: Input
 VARIABLES DESCRIPTION:   Event handle.  
VARIABLES: DVBASPCV                     TYPE: Output
 VARIABLES DESCRIPTION:   Value from AFTER event array.  
COMPONENT/ENTRY POINT: SDORGST
 COMPONENT DESCRIPTION:   Extrinsic function returns event originating process. 
 
COMPONENT/ENTRY POINT: REQARY
 COMPONENT DESCRIPTION:   Builds ^TMP array from file 396.3.  
VARIABLES: DVBADFN                      TYPE: Input
 VARIABLES DESCRIPTION:   Patient pointer (#2).  
VARIABLES: DVBASTAT                     TYPE: Input
 VARIABLES DESCRIPTION:   Status 
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI uses 3 extrinsic functions (SDEVTXST, SDEVTSPC
 and SDORGST) and 1 subroutine (REQARY) in routine DVBCUTL5 to maintain C&P
 appointments.  
  DATE ACTIVATED: MAY 28, 2019

NUMBER: 7043                            IA #: 7043
  DATE CREATED: MAR 13, 2019
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Private                        TYPE: Routine
  ROUTINE: MPIF001
  NAME: VS GUI access to extrinsic function in routine MPIF001
  ID: MPIF001                           STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETICN
 COMPONENT DESCRIPTION:   Returns ICN from patient file.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file pointer.  
VARIABLES: RETURN                       TYPE: Output
 VARIABLES DESCRIPTION:   ICN 
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI uses extrinsic function $$GETICN^MPIF001 to
 retrieve a patient's ICN.  

NUMBER: 7044                            IA #: 7044
  FILE NUMBER: 396.3                    GLOBAL ROOT: DVB(396.3
  DATE CREATED: MAR 14, 2019
  CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VS GUI access to 2507 Request file (#396.3)
  ID: DVB(396.3
GLOBAL REFERENCE: DVB(396.3,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Patient file (#2) pointer.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Access to .01 field used when linking appointments to
 entries in the AMIE C&P EXAM TRACKING file (#396.95).  
  DATE ACTIVATED: MAY 28, 2019

NUMBER: 7045                            IA #: 7045
  FILE NUMBER: 396.95                   GLOBAL ROOT: DVB(396.95
  DATE CREATED: MAR 14, 2019
  CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VS GUI access to AMIE C&P Exam Tracking (#396.95)
  ID: DVB(396.95
GLOBAL REFERENCE: DVB(396.95,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ORIGINAL APPOINTMENT DATE
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: CURRENT APPT DATE
  LOCATION: 0;3                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: VETERAN CANCELLATION
  LOCATION: 0;4                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: VETERAN REQ APPT DATE
  LOCATION: 0;5                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: 2507 REQUEST
  LOCATION: 0;6                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: APPOINTMENT STATUS
  LOCATION: 0;7                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DATE APPT CANCELLED
  LOCATION: 0;8                         ACCESS: Direct Global R/W & w/Fileman
 GENERAL DESCRIPTION:   This ICR request results from an ICR audit of
 production VS GUI code.  
  
 No new code was introduced into the system.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI needs access to the AMIE C&P Exam Tracking file
 (#396.95) to record scheduled appointments.  
  DATE ACTIVATED: APR 17, 2019

NUMBER: 7046                            IA #: 7046
  DATE CREATED: MAR 14, 2019
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  ROUTINE: VSITVID                      NAME: VS GUI access to routine VSITVID
  ID: VSITVID
 GENERAL DESCRIPTION:   
 ************************************************************************
 *                                                                      *
 *  This is a temporary ICR for the production VistA Scheduling (VS)    * * 
 GUI software.                                                       * *  The
 need for this ICR was identified from the VS Sustainment Team   * *  reviewing
 the VistA Scheduling Enhancement (VSE) software that was  * *  released
 nationally without approved ICRs.  This temporary ICR      * *  represents the
 situation, where the Custodian package experts       * *  requested changes to
 the production software to use approved        * *  APIs, which requires a
 future VS patch. This temporary ICR will     * *  expire when the production
 code is modified to the use approved     * *  APIs                             
                                   * 
 *                                                                      *
 ************************************************************************
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETVID
 COMPONENT DESCRIPTION:   Returns the next available visit ID.  There are no
 input parameters.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI used the extrinsic function $$GETVID^VSITVID
 when generating new visits.  

NUMBER: 7047                            IA #: 7047
  DATE CREATED: MAR 18, 2019
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWPT
  NAME: VS GUI access to routine ORWPT  ID: ORWPT
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PTINQ
 COMPONENT DESCRIPTION:   Generates formatted patient inquiry.  
VARIABLES: REF                          TYPE: Output
 VARIABLES DESCRIPTION:   Stores location (^TMP) where the formatted data is
 stored.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file (#2) pointer.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI calls ORWPT to obtain a formatted patient
 inquiry that can be displayed to the scheduler.  
  DATE ACTIVATED: APR 18, 2019

NUMBER: 7048                            IA #: 7048
  FILE NUMBER: 9000001                  GLOBAL ROOT: AUPNPAT
  DATE CREATED: MAR 18, 2019
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  NAME: VS GUI access to file #9000001  ID: AUPNPAT
GLOBAL REFERENCE: AUPNPAT(D0,41,D1
FIELD NUMBER: .02                       FIELD NAME: HEALTH RECORD NO.
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DATE INACTIVATED/DELETED
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
 ************************************************************************
 *                                                                      *
 *  This is a temporary ICR for the production VistA Scheduling (VS)    * * 
 GUI software.                                                       * *  The
 need for this ICR was identified from the VS Sustainment Team   * *  reviewing
 the VistA Scheduling Enhancement (VSE) software that was  * *  released
 nationally without approved ICRs.  This temporary ICR      * *  represents the
 situation, where the Custodian package experts       * *  requested changes to
 the production software to use approved        * *  APIs, which requires a
 future VS patch. This temporary ICR will     * *  expire when the production
 code is modified to the use approved     * *  APIs                             
                                   * 
 *                                                                      *
 ************************************************************************
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI extracts the health record number and date
 inactivated/deleted from file #9000001.  

NUMBER: 7049                            IA #: 7049
  FILE NUMBER: 405                      GLOBAL ROOT: DGPM(
  DATE CREATED: MAR 20, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VS GUI access to Patient Movement (#405) file.
  ID: DGPM(
GLOBAL REFERENCE: DGPM(D0
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: TRANSFER FACILITY
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .17                       FIELD NAME: DISCHARGE/CHECK-OUT MOVEMENT
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI uses file #405 to obtain information about
 inpatients for display to the scheduler.  
  
 Before file #405 is accessed: 
  
 * SDECEP and SDECEPT call INP^DGPMV10.  * SDECPTCX gets a pointer from
 ^DPT(dfn,.105.  * SDECUTL looks at the "AVISIT" cross-reference.  * SDEC50
 calls ADM^VADPT then uses return value to look up data in #405.  
  
 This ICR request results from an ICR audit of production VS GUI code.  
  
 No new code was introduced into the system.  
  
 Note: This ICR request revises and replaces ICR #2297.  
  DATE ACTIVATED: MAY 28, 2019

NUMBER: 7050                            IA #: 7050
  FILE NUMBER: 8                        GLOBAL ROOT: DIC(8
  DATE CREATED: MAR 22, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VS GUI access to Eligibility Code file (#8)
  ID: DIC(8
GLOBAL REFERENCE: DIC(8,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: TYPE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: MAS ELIGIBILITY CODE
  LOCATION: 0;9                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   
 ************************************************************************
 *                                                                      *
 *  This is a temporary ICR for the production VistA Scheduling (VS)    * * 
 GUI software.                                                       * *  The
 need for this ICR was identified from the VS Sustainment Team   * *  reviewing
 the VistA Scheduling Enhancement (VSE) software that was  * *  released
 nationally without approved ICRs.  This temporary ICR      * *  represents the
 situation, where the Custodian package experts       * *  requested changes to
 the production software to use approved        * *  APIs, which requires a
 future VS patch. This temporary ICR will     * *  expire when the production
 code is modified to the use approved     * *  APIs                             
                                   * 
 *                                                                      *
 ************************************************************************
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI uses the Eligibility Code file to display
 eligibility data to schedulers.  
  
 Note:  This request results from an ICR Audit of production code and not the
 introduction of new code.  
  DATE ACTIVATED: MAY 28, 2019

NUMBER: 7051                            IA #: 7051
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123
  DATE CREATED: MAR 25, 2019
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  NAME: VS GUI Access fields in file #123
  ID: GMR(123
GLOBAL REFERENCE: GMR(123,D0
FIELD NUMBER: .04                       FIELD NAME: Patient Location
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .125                      FIELD NAME: IFC Role
  LOCATION: 12;5                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: From
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: Date of Request
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: Urgency
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: Attention
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 13                        FIELD NAME: Request Type
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 17                        FIELD NAME: Clinically Indicated Date
  LOCATION: 0;24                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI uses fields in file #123 Request/Consultation to
 display to the scheduler and to calculate audit statistics.  
  
 Note:  This request is from an ICR Audit of production code.  No new code is
 being introduced.  

NUMBER: 7052                            IA #: 7052
  FILE NUMBER: 8.1                      GLOBAL ROOT: DIC(8.1
  DATE CREATED: APR 01, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: VS GUI access to MAS Eligibility Code (#8.1)
  ID: DIC(8.1
GLOBAL REFERENCE: DIC(8.1,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: TYPE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   
 ************************************************************************
 *                                                                      *
 *  This is a temporary ICR for the production VistA Scheduling (VS)    * * 
 GUI software.                                                       * *  The
 need for this ICR was identified from the VS Sustainment Team   * *  reviewing
 the VistA Scheduling Enhancement (VSE) software that was  * *  released
 nationally without approved ICRs.  This temporary ICR      * *  represents the
 situation, where the Custodian package experts       * *  requested changes to
 the production software to use approved        * *  APIs, which requires a
 future VS patch. This temporary ICR will     * *  expire when the production
 code is modified to the use approved     * *  APIs                             
                                   * 
 *                                                                      *
 ************************************************************************
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   VS GUI uses data in the MAS Eligibility Code (#8.1)
 file when displaying eligibility information to schedulers.  
  
 Note:  This request results from an ICR audit of production code.  No new code
 is being introduced.  
  DATE ACTIVATED: MAY 28, 2019

NUMBER: 7053                            IA #: 7053
  FILE NUMBER: 0                        GLOBAL ROOT: DD(63.04
  DATE CREATED: APR 04, 2019            CUSTODIAL PACKAGE: 1
  USAGE: Controlled Subscription        TYPE: File
  NAME: FIELD LABEL CHECK               ID: DD(63.04
GLOBAL REFERENCE: DD(63.04,D0,0
FIELD NUMBER: .01                       FIELD NAME: FIELD LABEL
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Field Label is in first "^" data piece:
 ^DD(63.04,IEN,0)=[field label]^...  
GLOBAL REFERENCE: DD(63.04,B
FIELD NUMBER: .01                       FIELD NAME: FIELD LABEL
  ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Field Label is in the third subscript:
 ^DD(63.04,"B",[field label],[IEN].  
 GENERAL DESCRIPTION:   
  
 VistA Laboratory requests permission to read ^DD(63.04 in order to check for
 Field Label inconsistencies which have potential for causing downstream
 issues.  
  
 Patch LR*5.2*519 will check all subscripts in the "B" cross reference of 
 ^DD(63.04 and send a MailMan message to the "LMI" MailMan group if the 
 following issues are found: 
  
 1. A Field Label subscript in the "B" cross reference does not match the 
    field label of the corresponding internal entry number (IEN) in the 
    first "^" data piece of ^DD(63.04,IEN,0).  
  
    Example - Correct: 
  
    ^DD(63.04,"B","ABC",100)="" 
    ^DD(63.04,100,0)="ABC^FJ222^^RF;2^K:$L(X)>222!($L(X)<1) X" 
  
    Example - Incorrect: 
  
    ^DD(63.04,"B","ABC",100)="" 
    ^DD(63.04,100,0)="XYZ^FJ222^^RF;2^K:$L(X)>222!($L(X)<1) X" 
  
 And/Or: 
  
 2. A Field Label subscript in the "B" cross reference points to more 
    than one IEN at ^DD(63.04,IEN,0).  
  
    Example - Correct - Only one entry at the "B" cross reference 
  
    ^DD(63.04,"B","ABC",100)="" 
    
    Example - Incorrect - More than one entry at the "B" cross reference 
  
    ^DD(63.04,"B","ABC",100)="" 
    ^DD(63.04,"B","ABC",200)="" 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DD(63.04
KEYWORDS: DATA NAME
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   VistA Lab will check ^DD(63.04,"B" subscripts for
 "Field Label" and internal entry number (IEN) issues: (1) a field label at
 ^DD(63.04,"B" is not valid for the corresponding IEN; and (2) a field label
 points to more than one IEN.  

NUMBER: 7054                            IA #: 7054
  FILE NUMBER: 200.051                  GLOBAL ROOT: VA(200,D0,51
  DATE CREATED: APR 08, 2019            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: WRITE ACCESS TO SUB-FILE 200.051
  ID: VA(200,D0,51
 GENERAL DESCRIPTION:   Outpatient Pharmacy is given permission by Kernel for
 write access with Fileman to the KEY field (#.01) of the KEYS SUB-FILE
 (#200.051).  
  STATUS: Active
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 4/25/25 effective with SD*5.3*899, for CPRS
 providers to view VSE GUI software. If user has ORES and/or ORELSE and does
 not have SDECZMenu, SECZMGR, or SD Supervisor then SCHEDULING will grant them
 SDECVIEW. 
   VISS KERNEL, ISSO, and ISO all denied approval in accordance with 
 'zero-trust'. There is no transitive trust, for example, if VA trusts A, and A
 trusts B, it doesn't mean VA automatically trusts B. B must meet or exceed
 requirements of the security account management process.  VistA identifies who
 requested the access, who approved it and who assigned the key.  
   The denial was over-ridden and the ICR subscription was approved by the 
 Office of Executive Director, Health Portfolio, accepting the associated risk.
 Risk Accepted POAM ID 1018541423476 documents the action plan.  
   This ICR allows skipping documentation about security key being assigned for
 the Scheduling package use.  
  
 ******THIS IS FOR A ONE TIME USE ONLY FOR PATCH SD*5.3*899.******** 
  
   From Scheduling's perspective, VistA Account policy is to ensure people do
 not get unauthorized access. But in this case, users already have OR key to
 view individual appointment data, and this is just giving them the read-only
 SDEC key to allow them to see aggregated view.  
  DATE ACTIVATED: JUN 03, 2025

NUMBER: 7055                            IA #: 7055
  DATE CREATED: APR 10, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VAFC MVI MGRTD FACILITIES UPDT
  REMOTE PROCEDURE: VAFC MVI MGRTD FACILITIES UPDT
 GENERAL DESCRIPTION:   The Master Patient Index (MPI) team requests permission
 for the MPI system to utilize the following REGISTRATION Remote Procedure Call 
 (RPC) [VAFC MVI MGRTD FACILITIES UPDT] to remotely maintain the EHRM MIGRATED
 FACILITIES (#391.919) file, which allows the site to know which facilities
 have migrated to/implemented the CERNER application in support of the
 Electronic Health Record Modernization (EHRM).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VAFC
KEYWORDS: DGCN(391.919
KEYWORDS: MVI
KEYWORDS: MPI
KEYWORDS: VAFC MVI MGRTD FACILITIES UPDT
KEYWORDS: EHRM MIGRATED FACILITIES
KEYWORDS: 391.919
KEYWORDS: CERNER
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   The Master Veteran Index (MVI) project will use the
 Remote Procedure Call (RPC) [VAFC MVI MGRTD FACILITIES UPDT] to maintain the
 EHRM MIGRATED FACILITIES (#391.919) file at the Veteran Affairs Medical 
 Centers (VAMCs), which will give the sites the ability to determine the
 facilities that have migrated to/implemented the CERNER application during the
 transition phase away from VistA.  
  DATE ACTIVATED: MAY 15, 2019

NUMBER: 7056                            IA #: 7056
  DATE CREATED: APR 19, 2019
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORWDX                        NAME: VIAB USE OF SAVE ORWDXA
  ID: ORWDX
 GENERAL DESCRIPTION:   VIA Requests usage of routine SAVE^ORWDX to process
 orders.  This routine will be called from remote procedure VIABDX SAVE.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: 2022
KEYWORDS: VIA
COMPONENT/ENTRY POINT: SAVE
 COMPONENT DESCRIPTION:   Routine SAVE^ORWDX will be called from SAVE^VIABDX. 
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VIA has client applications in need of initiating
 orders.  Previously VIA was using File access to process orders, but those
 ICR's are withdrawn. This process will provide needed services for
 getOrderManagment Web service calls without disruption to Order Entry files.  

NUMBER: 7057                            IA #: 7057
  DATE CREATED: APR 24, 2019
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: ORWDPS2 OISLCT                  REMOTE PROCEDURE: ORWDPS2 OISLCT
 GENERAL DESCRIPTION:   Returns defaults for pharmacy orderable item needed for
 clients currently in the field.  
  STATUS: Pending
KEYWORDS: VIA
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   Usage for web service was sent out in past efforts. 
 ICR may have been overlooked.  

NUMBER: 7058                            IA #: 7058
  DATE CREATED: APR 25, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDEC07
  NAME: Make Appointment API            ID: SDEC07
 GENERAL DESCRIPTION:   Making an appointment impacts several files in all
 cases (e.g., Patient, Location, SDEC Appointment) and others in specific cases
 (e.g., Consult).  This ICR describes the scheduling API that can be used by 
 non-scheduling applications to make appointments.  
  
 Note:  Subscribing applications that want to invoke this API using the SDEC
 APPADD RPC can subscribe to the appropriate controlled ICR (#7059).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: APPADD
 COMPONENT DESCRIPTION:   APPADD is the entry point in SDEC07 that is called to
 make an appointment and have the data updated in all required files.  
  
 Sequence of input parameters: 
  
                1.  SDECSTART 
                2.  SDECEND 
                3.  DFN 
                4.  SDRES 
                5.  SDCLEN 
                6.  SDECNOTE 
                7.  SDECATID 
                8.  SDECCR 
                9.  SDMRTC 
               10.  SDDDT 
               11.  SDREQBY 
               12.  SDLAB 
               13.  PROVIEN 
               14.  SDID 
               15.  SDAPTYP 
               16.  SDSVCP 
               17.  SDSVCPR 
               18.  SDCL 
               19.  SDEKG 
               20.  SDXRAY 
               21.  APPTYPE 
               22.  EESTAT 
               23.  OVB 
               24.  SDPARENT 
               25.  SDEL 
               26.  SOURCE (introduce in patch 715)  
VARIABLES: SDECY                        TYPE: Output
 VARIABLES DESCRIPTION:   SDECY contains the name of the global array which
 stores the results of the make appointment operation.  It is in the form of 
 ^TMP("SDEC07",$J,i).  For i=0, the header string 
 "I00020APPOINTMENTID^T00020ERRORID" is returned.  
  
 If the API call is successful, the next line will contain a pointer to the 
 SDEC Appointment file (#409.84) entry that was created.  
  
 If the API call is unsuccessful, the next line will contain a 0 in piece 1 (on
 "^") and the error reason text in piece 2.  
VARIABLES: SDECSTART                    TYPE: Input
 VARIABLES DESCRIPTION:   Contains the start date/time of the appointment in
 external format.  Both date and time must be present.  REQUIRED.  
VARIABLES: SDECEND                      TYPE: Input
 VARIABLES DESCRIPTION:   Contains the end date/time of the appointment in
 external format.  Both date and time must be present.  REQUIRED.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file (#2) pointer.  REQUIRED.  
VARIABLES: SDECRES                      TYPE: Input
 VARIABLES DESCRIPTION:   Either the pointer or the name of the SDEC Resource
 (#409.831) being scheduled.  If the name is specified, it must be an exact
 match with the .01 field.  REQUIRED.  
VARIABLES: SDECLEN                      TYPE: Input
 VARIABLES DESCRIPTION:   Length of the appointment in minutes.  OPTIONAL.  
VARIABLES: SDECNOTE                     TYPE: Input
 VARIABLES DESCRIPTION:   Appointment comment.  OPTIONAL.  
  
 Prior to patch SD*5.3*715, this field is restricted to 75 characters because
 of CPRS limitations.  After patch 715, the comment is stored in a word
 processing field and the practical limitation is 32K.  
VARIABLES: SDECATID                     TYPE: Input
 VARIABLES DESCRIPTION:   If appointment is a walk-in then set to WALKIN. 
 Otherwise leave null.  
VARIABLES: SDECCR                       TYPE: Input
 VARIABLES DESCRIPTION:   Applies to WALKIN appointments only.  1=print routing
 slip. OPTIONAL.  
VARIABLES: SDMRTC                       TYPE: Input
 VARIABLES DESCRIPTION:   If appointment is for an MRTC, set to TRUE. 
 OPTIONAL.  
VARIABLES: SDDDT                        TYPE: Input
 VARIABLES DESCRIPTION:   Desired date of appointment in external format. If
 missing or invalid, it is set to the date of the appointment.  OPTIONAL.  
VARIABLES: SDREQBY                      TYPE: Input
 VARIABLES DESCRIPTION:   Appointment requested by.  Possible values are
 PROVIDER or PATIENT.  OPTIONAL.  
VARIABLES: SDLAB                        TYPE: Input
 VARIABLES DESCRIPTION:   Date/time of labs in external format.  OPTIONAL.  
VARIABLES: SDEKG                        TYPE: Input
 VARIABLES DESCRIPTION:   Date/time of EKG in external format.  OPTIONAL.  
VARIABLES: PROVIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   Provider.  Pointer to New Person file (#200). 
 OPTIONAL.  
VARIABLES: SDID                         TYPE: Input
 VARIABLES DESCRIPTION:   Extrernal ID.  OPTIONAL.  
VARIABLES: SDAPTYP                      TYPE: Input
 VARIABLES DESCRIPTION:   Requst type.  Format is X | pointer where X="A" for
 APPT, "C" for consult, "E" for EWL or "R" for Recall and pointer is a pointer
 to #409.85 for APPT, to #123 for Consult, to #409.3 for EWL and to #403.5 for
 Recall.  
  
 REQUIRED 
VARIABLES: SDSVCP                       TYPE: Input
 VARIABLES DESCRIPTION:   Service Connected.  Value is either "YES" or "NO". 
 OPTIONAL.  
VARIABLES: SDSVCPR                      TYPE: Input
 VARIABLES DESCRIPTION:   Service connected percentage.  Value is 0-100. 
 OPTIONAL.  
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   Clinic.  Pointer to file #44.  OPTIONAL.  
VARIABLES: SDXRAY                       TYPE: Input
 VARIABLES DESCRIPTION:   Date/time in external format of last x-ray. 
 OPTIONAL.  
VARIABLES: APPTYPE                      TYPE: Input
 VARIABLES DESCRIPTION:   Appointment type.  Pointer to file #409.1. OPTIONAL.  
VARIABLES: EESTAT                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient status.  Values permitted are:
 N,NEW,E,ESTABLISHED.  OPTIONAL.  
VARIABLES: OVB                          TYPE: Input
 VARIABLES DESCRIPTION:   Appointment is an overbook (1=YES, 0=NO).  OPTIONAL.  
VARIABLES: SDPARENT                     TYPE: Input
 VARIABLES DESCRIPTION:   Parent request of an MRTC.  Pointer to #409.85. 
 OPTIONAL.  
VARIABLES: SDEL                         TYPE: Input
 VARIABLES DESCRIPTION:   Patient eligibility.  Pointer to #8.  REQUIRED.  
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   Appointment source.  Permitted values are: GUI,
 VistA, Other.  OPTIONAL.  
  
 NOTE:  This field first appears in patch SD*5.3*715.  
  DATE ACTIVATED: NOV 23, 2022

NUMBER: 7059                            IA #: 7059
  DATE CREATED: APR 25, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: SDEC APPADD                     REMOTE PROCEDURE: SDEC APPADD
 GENERAL DESCRIPTION:   RPC used to add a new appointment for a patient.  
  
 For further information including a description of the inputs and outputs, see
 ICR #7058.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Added 11/17/22, via DTC Integration  Platform (DIP)
 (VASI: 2825) for VA Health Connect Scheduling/WellHive scheduling application
 for the Clinical Contact Centers.  
  DATE ACTIVATED: NOV 23, 2022

NUMBER: 7060                            IA #: 7060
  DATE CREATED: APR 30, 2019            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DIU2
  NAME: DELETE FILES AND SUB-FILES TO BACKOUT PRCA313 FROM IOC
  ID: DIU2
 GENERAL DESCRIPTION:   The project for PRCA*4.5*313 is being cancelled, and
 since the patch is already in production at three IOC sites, the patch needs
 to be backed out of those three sites.  This integration agreement is to allow
 use of a supported fileman API to delete files and sub-files so that they may
 be restored to their pre-patch condition.  This API will be used in the 
 pre-install routine PRCA313P.  
  
 FileMan API being used: 
  
 Deleting Files and Sub-files EN^DIU2: Delete Data Dictionary Reference Type:
 Supported Category: Classic VA FileMan ICR#: 10014 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BACKOUT
KEYWORDS: PRCA313P
COMPONENT/ENTRY POINT: EN
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   One time use only at 3 IOC sites for backing out
 earlier version of PRCA*4.5*313.  
  
 IOC sites: 
   - BAY PINES, FL (#516) 
   - CONNECTICUT HCS (#689) 
   - TAMPA, FL (#673) 
  DATE ACTIVATED: MAY 14, 2019

NUMBER: 7061                            IA #: 7061
  DATE CREATED: APR 30, 2019            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DIK
  NAME: DELETE FIELDS TO BACKOUT PRCA313 FROM IOC
  ID: DIK
 GENERAL DESCRIPTION:   The project for PRCA*4.5*313 is being cancelled, and
 since the patch is already in production at three IOC sites, the patch needs
 to be backed out of those three sites.  This integration agreement is to allow
 use of a supported fileman API to delete fields so that they may be restored
 to their pre-patch condition.  This API will be used in the pre-install 
 routine PRCA313P.  
     
 FileMan API being used: 
     
 Deleting Fields ^DIK: Delete Data Dictionary Reference Type: Supported 
 Category: Classic VA FileMan ICR#: 10014 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BACKOUT
KEYWORDS: PRCA313P
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   One time use only at 3 IOC sites for backing out
 earlier version of PRCA*4.5*313.  
  
 IOC sites: 
   - BAY PINES, FL (#516) 
   - CONNECTICUT HCS (#689) 
   - TAMPA, FL (#673) 
  DATE ACTIVATED: MAY 14, 2019

NUMBER: 7062                            IA #: 7062
  DATE CREATED: MAY 01, 2019            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS MVI ENRICH NEW PERSON
  REMOTE PROCEDURE: XUS MVI ENRICH NEW PERSON
 GENERAL DESCRIPTION:   In support of the Provider Profile Management System
 (PPMS) / Provider Integration Engine (PIE) for Mission Act, the Master Veteran
 Index (MVI) team requests permission to exclusively use the following 
 restricted KERNEL Remote Procedure Call (RPC) [XUS MVI ENRICH NEW PERSON], 
 which will allow MVI to either add a new National Provider type entry to the
 NEW PERSON File (#200) or update select fields with enriched data for an
 existing user entry, identified by their Nation Provider Identifier (NPI)
 value, in the NEW PERSON File (#200) and associated DEA NUMBERS File (#8991.9)
 from the MVI system. See the RPC for a complete list of fields to be updated.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XUS MVI ENRICH NEW PERSON
KEYWORDS: 200
KEYWORDS: VA(200
KEYWORDS: PPMS
KEYWORDS: PIE
KEYWORDS: XUMVIENU
KEYWORDS: XUMVINPA
KEYWORDS: MVI
KEYWORDS: MPI
KEYWORDS: NEW PERSON
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   The Master Veteran Index (MVI) project will use this
 Remote Procedure Call (RPC) to either add an entry to the NEW PERSON File
 (#200) or update an existing entry in the NEW PERSON File (#200) and
 associated DEA NUMBERS File (#8991.9) with enriched data beginning with patch 
 MPI*1.0*130.  
  DATE ACTIVATED: MAY 14, 2019

NUMBER: 7063                            IA #: 7063
  FILE NUMBER: 8992.1                   GLOBAL ROOT: XTV(8992.1
  DATE CREATED: MAY 06, 2019            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: OE/RR Reference to Alert Tracking File (8992.1)
  ID: XTV(8992.1
GLOBAL REFERENCE: XTV(8992.1,D0,0)
FIELD NUMBER: .02                       FIELD NAME: DATE CREATED
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: PKG ID
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: XTV(8992.1,'D')
FIELD NUMBER: .02                       FIELD NAME: DATE CREATED
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: XTV(8992.1,D0,20,D1,0)
FIELD NUMBER: .01                       FIELD NAME: RECIPIENT
  LOCATION: 20;D1;0                     ACCESS: Read w/Fileman
GLOBAL REFERENCE: XTV(8992.1,D0,1)
FIELD NUMBER: 1.01                      FIELD NAME: DISPLAY TEXT
  LOCATION: 1;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: XTV(8992.1,'B')
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: XTV(8992.1,D0,2)
FIELD NUMBER: 2                         FIELD NAME: DATA FOR PROCESSING
  LOCATION: 2;E1,245                    ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: XTV(8992.1,D0,20,D1,3)
FIELD NUMBER: 3                         FIELD NAME: SURROGATE FOR
  LOCATION: 3;0                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: XTV(8992.1,D0,20,'B')
FIELD NUMBER: .01                       FIELD NAME: RECIPIENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   OE/RR utilizes the Alert Tracking File (#8992.1) to
 obtain alert information for OR and TIU alerts for a specified date range
 included with patch OR*3.0*500 Alert Enhancements.  
  
 Revision History: 
  
 Added 7/26/24: Effective with OR*3*561, the following 2 global references were
 added: 
   ^XTV(8992.1,D0,20,D1,3) 
    3        SURROGATE FOR        3;0      Direct Global Read & w/Fileman 
   ^XTV(8992.1,D0,20,'B') 
   .01       RECIPIENT            0;1      Direct Global Read & w/Fileman 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OE/RR
KEYWORDS: ALERT TRACKING
KEYWORDS: 8992.1
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAY 06, 2019

NUMBER: 7064                            IA #: 7064
  DATE CREATED: MAY 06, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDEC08
  NAME: Cancel Appointment API          ID: SDEC08
 GENERAL DESCRIPTION:   Cancelling an appointment impacts several files in all
 cases (e.g., Patient, Location, SDEC Appointment) and others in specific cases
 (e.g., Consult).  This ICR describes the scheduling API that can be used by 
 non-scheduling applications to cancel appointments.  
  
 Note:  Subscribing applications that want to invoke this API using the SDEC
 APPDEL RPC can subscribe to the appropriate controlled ICR (#7065).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: APPDEL
 COMPONENT DESCRIPTION:   APPDEL is the entry point in SDEC08 that is called to
 cancel an appointment and have the data updated in all required files.  
VARIABLES: SDECY                        TYPE: Output
 VARIABLES DESCRIPTION:   SDECY contains the name of the global array which
 stores the results of the cancel appointment operation.  It is in the form of 
  
 ^TMP("SDEC07",$J,i).  For i=0, the header string "T00020ERRORID" is returned. 
         
 If the API call is successful, the next line will contain a null string.  
  
 If the API call is unsuccessful, the next line will contain an error reason.  
VARIABLES: SDECAPTID                    TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the SDEC Appointment file (#409.84).  The
 appointment to be cancelled.    REQUIRED 
VARIABLES: SDECTYP                      TYPE: Input
 VARIABLES DESCRIPTION:   Indicates the source of the cancellation.  There are
 two possible values for this input parameter: 
  
 C = Cancelled by clinic PC = Cancelled by patient 
  
 REQUIRED 
VARIABLES: SDECCR                       TYPE: Input
 VARIABLES DESCRIPTION:   Cancellation reason.  Pointer to the Cancellation
 Reason file (#409.2).  
  
 OPTIONAL 
VARIABLES: SDECNOT                      TYPE: Input
 VARIABLES DESCRIPTION:   Cancellation note.  Limited to 160 characters. 
 OPTIONAL 
VARIABLES: SDECDATE                     TYPE: Input
 VARIABLES DESCRIPTION:   Cancellation date/time in external format.  If blank,
 now is used.  OPTIONAL 
VARIABLES: SDUSER                       TYPE: Input
 VARIABLES DESCRIPTION:   User who cancelled the appointment.  If blank,
 defaults to current user.  OPTIONAL 
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   Application source.  See the set of codes associated
 with field #1 of the Application Events file (#409.94).  If blank, "Other" is
 applied.  OPTIONAL.  
  
 Note:  This field first appears in patch SD*5.3*715.  
VARIABLES: SDF                          TYPE: Input
 VARIABLES DESCRIPTION:   Flag to be passed in by external applications to
 determine whether a cancelled appointment should be re-opened. 
  
 SDF=1 or null (default) - Appointment reopened 
  
 SDF=2                   - Appointment not reopened.  
                           Appointment closed with disposition of 
                           "REMOVED/EXTERNAL APP" 
  
 Note:  This field first appears in patch SD*5.3*745.  
VARIABLES: SDECCMT                      TYPE: Input
 VARIABLES DESCRIPTION:   Optional parameter that contains a list of
 cancellation comment hash tags separated by ^ (e.g., FIRST^SECOND). A hash tag
 is the .01 field of the the SDEC Cancellation Comments file (#409.88).  
  
 Note:  Parameter added with patch SD*5.3*756.  
  DATE ACTIVATED: MAY 04, 2020

NUMBER: 7065                            IA #: 7065
  DATE CREATED: MAY 06, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: SDEC APPDEL                     REMOTE PROCEDURE: SDEC APPDEL
 GENERAL DESCRIPTION:   RPC used to cancel an appointment for a patient.  
  
 For further information including a description of the inputs and outputs, see
 ICR #7064.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VETEXT
 SUBSCRIBING DETAILS:   Added 11/1/21. VEText is working with OCTO/OVAC to
 replace Kiosk hardware with a mobile exp. VEText needs access to this RPC to
 cancel appointments for VETExt appointment reminders and the VSIP project,
 which is web-based solution.  
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Added 11/17/22, via DTC Integration Platform (DIP)
 (VASI: 2825) for VA Health Connect Scheduling/WellHive scheduling application
 for the Clinical Contact Centers.  
  DATE ACTIVATED: NOV 01, 2021

NUMBER: 7066                            IA #: 7066
  DATE CREATED: MAY 07, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDEC25
  NAME: Check-In API                    ID: SDEC25
 GENERAL DESCRIPTION:   Checking in an appointment impacts several files -
 Location, SDEC Appointment. This ICR describes the scheduling API that can be
 used by non-scheduling applications to check in appointments.  
  
 Note:  Subscribing applications that want to invoke this API using the SDEC
 CHECKIN RPC can subscribe to the appropriate controlled ICR (#7067).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CHECKIN
 COMPONENT DESCRIPTION:   CHECKIN is the entry point in SDEC25 that is called
 to check in an appointment and have the data updated in all required files.  
VARIABLES: SDECY                        TYPE: Output
 VARIABLES DESCRIPTION:   SDECY contains the name of the global array which
 stores the results of results of the check in appointment operation.  It is in
 the form of 
         
        ^TMP("SDEC07",$J,i).  For i=0, the header string 
 "T00020ERRORID^T00150MESSAGE" is returned.  
                
        If the API call is successful, the next line will contain a zero. 
         
        If the API call is unsuccessful, the next line will contain an error
 reason.  
VARIABLES: SDECAPTID                    TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the SDEC Appointment file (#409.84).  The
 appointment to be checked in.    REQUIRED 
VARIABLES: SDECCDT                      TYPE: Input
 VARIABLES DESCRIPTION:   Check in date/time in external format or @ to cancel
 check-in.  OPTIONAL.  If blank, the current date/time is used.  
VARIABLES: SDECCC                       TYPE: Input
 VARIABLES DESCRIPTION:   Clinc stop code (pointer to #40.7).  OPTIONAL 
VARIABLES: SDECPRV                      TYPE: Input
 VARIABLES DESCRIPTION:   Appointment provider (pointer to #200).  Used to
 change the original provider associated with the appointment.  OPTIONAL.  
VARIABLES: SDECROU                      TYPE: Input
 VARIABLES DESCRIPTION:   Print routing slip flag (1=yes/0=no).  OPTIONAL.  
VARIABLES: SDECVCL                      TYPE: Input
 VARIABLES DESCRIPTION:   Unused.  
VARIABLES: SDECVFM                      TYPE: Input
 VARIABLES DESCRIPTION:   Unused 
VARIABLES: SDECOG                       TYPE: Input
 VARIABLES DESCRIPTION:   Unused 
VARIABLES: SDECCR                       TYPE: Input
 VARIABLES DESCRIPTION:   Unused 
VARIABLES: SDECPCC                      TYPE: Input
 VARIABLES DESCRIPTION:   Unused 
VARIABLES: SDECWHF                      TYPE: Input
 VARIABLES DESCRIPTION:   Unused 
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   Application source.  See the set of codes associated
 with field #1 of the Application Events file (#409.94).  If blank, "Other" is
 applied.  OPTIONAL.  
  
        Note:  This field first appears in patch SD*5.3*715.  
  DATE ACTIVATED: NOV 01, 2021

NUMBER: 7067                            IA #: 7067
  DATE CREATED: MAY 07, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: SDEC CHECKIN                    REMOTE PROCEDURE: SDEC CHECKIN
 GENERAL DESCRIPTION:   RPC used to check an appointment in.  
  
 For further information including a description of the inputs and outputs, see
 ICR #7066.  
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VETEXT
 SUBSCRIBING DETAILS:   Added 11/1/21 VEText (VETEX) is working with OCTO/OVAC
 on a project to replace kiosk hardware with a mobile experience through a
 web-application.  We need this RPC to check in the patient.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   11/29/21: Added VIA as a Subscriber to ICR 7067. MBAA
 is supporting Somnoware sleep study Application, utilizing VIA services.
 Mobile Applications Scheduling Application Suite is using this RPC through the 
 VistA Integration Adaptor's VIAB namespace, for a new Application under 
 development, planned for VIAB*1.0*23. (VIA Java code released separate from
 VistA patch).  
  DATE ACTIVATED: NOV 01, 2021

NUMBER: 7068                            IA #: 7068
  DATE CREATED: MAY 08, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: SDEC25                       NAME: Check out appointment
  ID: SDEC25
 GENERAL DESCRIPTION:   Checking a patient out for an appointment impacts
 several files - Location, SDEC Appointment. This ICR describes the scheduling
 API that can be used by non-scheduling applications to check out appointments. 
  
 Note:  Subscribing applications that want to invoke this API using the SDEC
 CHECKOUT RPC can subscribe to the appropriate controlled ICR (#7069).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CHECKOUT
 COMPONENT DESCRIPTION:   CHECKOUT is the entry point in SDEC25 that is called
 to check out an appointment and have the data updated in all required files.  
VARIABLES: SDECY                        TYPE: Output
 VARIABLES DESCRIPTION:   SDECY contains the name of the global array which
 stores the results of results of the check in appointment operation.  It is in
 the form of 
                
 ^TMP("SDEC07",$J,i).  For i=0, the header string "T00020ERRORID" is returned.  
                       
 If the API call is successful, the next line will contain a zero.  
  
 If the API call is unsuccessful, the next line will contain an error reason.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient file pointer (#2).  REQUIRED 
VARIABLES: SDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Appointment date/time in external format.  REQUIRED.  
VARIABLES: SDCODT                       TYPE: Input
 VARIABLES DESCRIPTION:   Check-out date/time in external format.  REQUIRED.  
VARIABLES: SDECAPTID                    TYPE: Input
 VARIABLES DESCRIPTION:   Appointment file (#409.84) pointer.  REQUIRED.  
VARIABLES: VPRV                         TYPE: Input
 VARIABLES DESCRIPTION:   Provider (#9000010.06) pointer.  OPTIONAL.  
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   Application source.  See the set of codes associated
 with field #1 of the Application Events file (#409.94).  If blank, "Other" is
 applied.  OPTIONAL.  
         
 Note:  This field first appears in patch SD*5.3*715.  

NUMBER: 7069                            IA #: 7069
  DATE CREATED: MAY 08, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: SDEC CHECKOUT                   REMOTE PROCEDURE: SDEC CHECKOUT
 GENERAL DESCRIPTION:   RPC used to check out an appointment.  
  
 For further information including a description of the inputs and outputs, see
 ICR #7068.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed

NUMBER: 7070                            IA #: 7070
  DATE CREATED: MAY 08, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: SDEC57                       NAME: Available Slots API
  ID: SDEC57
 GENERAL DESCRIPTION:   Returns list of slots set up for a clinic for a date
 range along with their availability.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: APPSLOTS
VARIABLES: SDECY                        TYPE: Output
 VARIABLES DESCRIPTION:   stores name of global array where results are
 returned.  line 0 contains a header line 
  
 T00030DATE^T00030START_TIME^T00030END_TIME^I00010AVAILABILITY 
  
 if the API call fails, line 1 contains -1 ^ error description 
  
 if the API call succeeds, lines 1-n contain: 
  
 date in FM format ^ slot start time (hhmm) ^ slot end time ^ availability code 
  
 availability code = 0-9,j-z corresponding to number of slots available for
 appointments (0-26) 
                   = A-W corresponding to number of slots overbooked (1-23) 
VARIABLES: SDECRES                      TYPE: Input
 VARIABLES DESCRIPTION:   Resource - either pointer to #409.831 or resource
 name (.01 field).  
VARIABLES: SDECSTART                    TYPE: Input
 VARIABLES DESCRIPTION:   Start date of range in external format.  
VARIABLES: SDECEND                      TYPE: Input
 VARIABLES DESCRIPTION:   End date of range in external format.  

NUMBER: 7071                            IA #: 7071
  DATE CREATED: MAY 08, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC APPSLOTS
  REMOTE PROCEDURE: SDEC APPSLOTS
 GENERAL DESCRIPTION:   RPC used to return list of appointment slots for a
 clinic associated with a resource.  For a list of inputs and outputs, see ICR
 #7070.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   Added 9/13/19 for use by VIA to support the Mobile
 Applications (TMP).  
  DATE ACTIVATED: SEP 13, 2019

NUMBER: 7072                            IA #: 7072
  DATE CREATED: MAY 08, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: SDEC25                       NAME: Cancel Appointment Check-Out API
  ID: SDEC25
 GENERAL DESCRIPTION:   Cancels appointment check-out and updates the
 appropriate scheduling files.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CANCKOUT
VARIABLES: SDECY                        TYPE: Output
 VARIABLES DESCRIPTION:   Stores name of global array where results are
 returned.  line 0 contains a header line 
  
 T00020ERRORID 
  
 if the API call fails, line 1 contains error description 
  
 if the API call succeeds, line 1 contains a zero 
VARIABLES: SDECAPTID                    TYPE: Input
 VARIABLES DESCRIPTION:   Appointment file (#409.84) pointer.  REQUIRED.  
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   Application source.  See the set of codes associated
 with field #1 of the Application Events file (#409.94).  If blank, "Other" is
 applied.  OPTIONAL.  
                
 Note:  This field first appears in patch SD*5.3*715.  

NUMBER: 7073                            IA #: 7073
  DATE CREATED: MAY 08, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: SDEC CANCKOUT                   REMOTE PROCEDURE: SDEC CANCKOUT
 GENERAL DESCRIPTION:   RPC used to cancel check out for an appointment.  For a
 list of inputs and outputs, see ICR #7072.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed

NUMBER: 7074                            IA #: 7074
  DATE CREATED: MAY 09, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDEC31
  NAME: No-Show Appointment API         ID: SDEC31
 GENERAL DESCRIPTION:   Marks appointment as no show or cancels no show and
 updates the relevant files.  Also executes the event triggers.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: NOSHOW
VARIABLES: SDECY                        TYPE: Output
 VARIABLES DESCRIPTION:   Stores name of global array where results are
 returned.  line 0 contains a header line 
         
        T00020ERRORID^T0030ERRORTEXT 
         
 if the API call fails, line 1 contains a zero and an error description if the
 API call succeeds, line 1 contains a one 
VARIABLES: SDECAPTID                    TYPE: Input
 VARIABLES DESCRIPTION:   Appointment file (#409.84) pointer.  REQUIRED 
VARIABLES: SDECNS                       TYPE: Input
 VARIABLES DESCRIPTION:   Set to 1 for no show and 0 to cancel no show. 
 REQUIRED 
VARIABLES: USERIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   User (pointer to #200) who entered no show.  OPTIONAL 
 If blank, the current user's DUZ is used.  
VARIABLES: SDECDATE                     TYPE: Input
 VARIABLES DESCRIPTION:   Date/time in external format of the no show. 
 OPTIONAL.  If blank, the date/time is set to now.  
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   Application source.  See the set of codes associated
 with field #1 of the Application Events file (#409.94).  OPTIONAL.  If blank,
 "Other" is applied.  
                       
 Note:  This field first appears in patch SD*5.3*715.  
  DATE ACTIVATED: NOV 17, 2022

NUMBER: 7075                            IA #: 7075
  DATE CREATED: MAY 09, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC NOSHOW
  REMOTE PROCEDURE: SDEC NOSHOW
 GENERAL DESCRIPTION:   RPC used to no show an appointment.  
  
 See ICR #7074 for a description of the input and output parameters.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Added 11/17/22 Accessed via DTC Integration Platform
 (DIP) (VASI: 2825) for VA Health Connect Scheduling/WellHive scheduling
 application Clinical Contact Center users.  
  DATE ACTIVATED: NOV 23, 2022

NUMBER: 7076                            IA #: 7076
  DATE CREATED: MAY 15, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: SDEC02                       NAME: Clinic schedule API
  ID: SDEC02
 GENERAL DESCRIPTION:   Returns appointments scheduled for a set of resources.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CRSCHED
VARIABLES: SDECY                        TYPE: Output
 VARIABLES DESCRIPTION:   Name of the global array where results are returned.  
  
 Line 0 contains a header as follows: 
  
 I00020APPOINTMENTID ^ D00030START_TIME ^ D00030END_TIME ^ D00030CHECKIN ^ 
 D00030AUXTIME ^ I00020PATIENTID ^ T00030PATIENTNAME ^ T00030RESOURCENAME ^ 
 I00005NOSHOW ^ T00020HRN ^ I00005ACCESSTYPEID ^ I00005WALKIN ^ D00030CHECKOUT
 ^ I00020VPROVIDER ^ T00020CANCELLED ^ T00250NOTE ^ T00030DAPTDT ^
 T00030APPTREQTYPE ^ T00030DIEDON ^ T00030EESTAT ^ T00250MULT ^ T00030SDPARENT
 ^ T00050SDLAST ^ T00030SSN ^ T00030DOB ^ T00100SENSITIVE 
  
 The remaining lines return lines of data separated by ^ as follows: 
  
 1. APPOINTMENT ID - pointer to Appointments file (#409.84) 2. START_TIME -
 appointment start date/time (external format) 3. END_TIME - appointment end
 date/time (external format) 4. CHECKIN - check-in date/time (external format) 
 5. AUXTIME - check-in date/time entered (external format) 6. PATIENTID -
 pointer to Patient file (#2) 7. PATIENTNAME - patient's name 8. RESOURCENAME -
 name of resource (from #409.831) 9. NOSHOW - no show date/time (external
 format) 10. HRN - medical record number 11. ACCESSTYPEID - access type
 (pointer to #409.1) 12. WALKIN - appointment is walk-in (y) or not (n) 13.
 CHECKOUT - appointment check-out date/time (external format) 14. VPROVIDER -
 unused 15. CANCELLED - cancellation date/time (external format) 16. NOTE -
 appointment note 17. DAPTDT - desired date of appointment (external format) 
 18. APPTREQTYPE - appointment request type (A=APPT, C=Consult, E=EWL, 
 R=Recall) 19. DIEDON - patient's date of death (FileMan format) 20. EESTAT -
 Patient Status  N=NEW  E=ESTABLISHED 21. MULT   - unused 22. SDPARENT - unused 
VARIABLES: SDECRES                      TYPE: Input
 VARIABLES DESCRIPTION:   List of resources (pointers to #409.831 or resource
 names) separated by |.  REQUIRED 
VARIABLES: SDECSTART                    TYPE: Input
 VARIABLES DESCRIPTION:   Start date (external format).  REQUIRED 
VARIABLES: SDECEND                      TYPE: Input
 VARIABLES DESCRIPTION:   End date (external format).  REQUIRED 
VARIABLES: SDECWKIN                     TYPE: Input
 VARIABLES DESCRIPTION:   Include walk-ins (1) or not (0).  OPTIONAL.  Default
 is 0.  
VARIABLES: MAXREC                       TYPE: Input
 VARIABLES DESCRIPTION:   Maximum number of records to return.  OPTIONAL. 
 Default is 99999.  
VARIABLES: LASTSUB                      TYPE: Input
 VARIABLES DESCRIPTION:   Unused.  

NUMBER: 7077                            IA #: 7077
  DATE CREATED: MAY 15, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: SDEC CRSCHED                    REMOTE PROCEDURE: SDEC CRSCHED
 GENERAL DESCRIPTION:   RPC that returns appointments scheduled for a set of
 resources.  See ICR #7076 for a list of inputs and outputs.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 7078                            IA #: 7078
  DATE CREATED: MAY 16, 2019            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUFILE1
  NAME: RA TAKE AWAY ALL ACCESS TO A (RIS) FILE
  ID: XUFILE1
 GENERAL DESCRIPTION:   VistA Radiology requests the privilege to use the
 XUFILE1 routine to take away all access from all users to the RAD/NUC MED
 REASON [#75.2] file. This is a one-time request and will be included in the
 routine: RAIPS160.  
  
 RAIPS160 will be a post-install routine released as a component of RA*5.0*160. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XU DELETE A FILE RA
KEYWORDS: RA DELETE A RIS FILE XU
COMPONENT/ENTRY POINT: DQ
 COMPONENT DESCRIPTION:   The 'DQ' tag is called when the single file number is
 known and set in the variable: 'XUW'.  
VARIABLES: XUW                          TYPE: Input
 VARIABLES DESCRIPTION:   This variable is set to the file number in which
 access is to be removed for all users.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   VistA Radiology would like to pass in the file number
 which is to be removed from access for all users at all sites.  
  DATE ACTIVATED: MAY 31, 2019

NUMBER: 7079                            IA #: 7079
  GLOBAL ROOT: DD(                      DATE CREATED: JUN 03, 2019
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: SOCIAL WORK FILE DELETION       ID: DD(
 GENERAL DESCRIPTION:   Social Work patch SOW*3.0*65 contains post install
 routine SOW3P65, which will use the VA FileMan API, EN^DIU2, to completely
 remove all SOW files, data, and related data dictionary entries.  
  
 The following files will be removed: 
  
 -SOCIAL WORK CASE (#650) 
  
 -SOCIAL WORK SITE PARAMETERS (#650.1) 
  
 -COST DISTRIBUTION CENTER (#651) 
  
 -RCH (#652) 
  
 -RESOURCES/REFERRALS (#653) 
  
 -SOCIAL WORK PATIENT (#655) 
  
 -SWS ASSESSMENT DATA BASE (#655.2) 
  
 -PSYCHO-SOCIAL PROBLEMS (#655.201) 
  
 -DIRECT SERVICE CATEGORIES (#655.202) 
  
 -PSYCHO-SOCIAL OUTCOMES (#655.203) 
  
 -SWS RESOURCES (#656) 
  
 The following code from SOW3P65 will be used to remove the files: 
  
  S DIU(0)="DST" ;flags to delete data, subfile and templates 
  F SOWFILE=650,650.1,651:1:653,655,655.2:.001:655.203,656 D  ;loop through 
 known social work files 
  .S DIU=$$ROOT^DILFD(SOWFILE),SOWNODE=$$CREF^DILF(DIU) ;set diu=file root and
 sownode=closed file root 
  .I '$$VFILE^DILFD(SOWFILE) Q  ;verify file exists 
  .D EN^DIU2 ;delete file and data in diu 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: File Deletion
SUBSCRIBING PACKAGE: SOCIAL WORK
 SUBSCRIBING DETAILS:   ONE TIME USE 
  
  DATE ACTIVATED: JUN 03, 2019

NUMBER: 7080                            IA #: 7080
  DATE CREATED: MAY 22, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: SDEC50                       NAME: Appointment List for a Patient API
  ID: SDEC50
 GENERAL DESCRIPTION:   Returns a list of appointments for a patient for a date
 range.  List may be all or only ancillary (Lab, X-ray, EKG) appointments.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: FAPPTGET
VARIABLES: SDECY                        TYPE: Output
 VARIABLES DESCRIPTION:   Stores name of global array where results are
 returned.  
  
 Line 0 of the array contains the following header: 
  
 T00020DFN ^ T00020CLINIC_IEN ^ T00030CLINIC_NAME ^ T00020APPT_DATE ^ 
 T00020STATUS ^ T00100ANCTXT ^ T00030CONS ^ T00030IEN ^ T00030APPTYPE_IEN ^ 
 T00030APPTYPE_NAME 
  
 All errors are returned as -1 ^ error text.  
  
 Successful calls populate the remaining lines in the array as follows: 
  
 DFN =          Patient (pointer to #2) CLINIC_IEN =   Clinic (pointer to #44) 
 CLINIC_NAME =  Clinic name (.01 field of file #44) APPT_DATE =    Appointment
 date/time (external format) STATUS =       Appointment status (NO ACTION
 TAKEN, CANCELLED BY PATIENT, 
                etc.) ANCTXT =       Time for ancillary work CONS =        
 Consult (pointer to #123) IEN =          Appointment (pointer to #409.84) 
 APPTYPE_IEN =  Appointment type (pointer to #409.1) APPTYPE_NAME = Appointment
 type name (.01 field of file #409.1) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient (pointer to #2) REQUIRED 
VARIABLES: SDBEG                        TYPE: Input
 VARIABLES DESCRIPTION:   Beginning of date range (external format)  REQUIRED 
VARIABLES: SDEND                        TYPE: Input
 VARIABLES DESCRIPTION:   End of date range (external format)  REQUIRED 
VARIABLES: SDANC                        TYPE: Input
 VARIABLES DESCRIPTION:   Ancillary flag (0=all appointments, 1=ancillary
 appointments only) OPTIONAL.  Default is 0.  

NUMBER: 7081                            IA #: 7081
  DATE CREATED: MAY 22, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: SDEC FAPPTGET                   REMOTE PROCEDURE: SDEC FAPPTGET
 GENERAL DESCRIPTION:   RPC that returns a list of appointments for a patient
 for a date range.  See ICR #7080 for a list of inputs and outputs.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 7082                            IA #: 7082
  DATE CREATED: MAY 30, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: SDEC57
  NAME: Clinic Schedule - Slot Availability API
  ID: SDEC57
 GENERAL DESCRIPTION:   Returns the slot counts for the clinic associated with
 a resource for a date range.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: APPSLOTS
VARIABLES: SDECY                        TYPE: Output
 VARIABLES DESCRIPTION:   Stores name of the global array where results are
 returned.  
  
 Line 0 of the array contains the following header: 
  
 T00030DATE ^ T00030START_TIME ^ T00030END_TIME ^ I00010AVAILABILITY 
  
 All errors are returned as -1^error text.  
  
 Successful calls populate the remaining lines in the array as follows: 
  
 DATE         = Date (FileMan format) START_TIME   = Start time (HHMM format) 
 END_TIME     = End time (HHMM format) AVAILABILITY = Number of available slots
 between start and end time.  
  
 Note: AVAILABILITY is set to null if no slots are available and is set to X if
 clinic availability has been cancelled for the time slot.  
VARIABLES: SDECRES                      TYPE: Input
 VARIABLES DESCRIPTION:   Resource (pointer to #409.831)  REQUIRED 
VARIABLES: SDECSTART                    TYPE: Input
 VARIABLES DESCRIPTION:   Start date (external format)  REQUIRED 
VARIABLES: SDECEND                      TYPE: Input
 VARIABLES DESCRIPTION:   End date (external format)  REQUIRED 

NUMBER: 7083                            IA #: 7083
  DATE CREATED: MAY 30, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: SDEC APPSLOTS                   REMOTE PROCEDURE: SDEC APPSLOTS
 GENERAL DESCRIPTION:   Returns the slot counts for the clinic associated with
 a resource for a date range.  
  
 See ICR #7082 for a list of inputs and outputs.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 7084                            IA #: 7084
  DATE CREATED: JUN 05, 2019            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOBPSUT
  NAME: Electronically Billable Indicator
  ID: PSOBPSUT
 GENERAL DESCRIPTION:   The $$ECME^PSOBPSUT call returns one of two values. An
 'e' is returned if the last fill of the prescription is electronically
 billable, else null is returned.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ECME
COMPONENT/ENTRY POINT: $$ECME
 COMPONENT DESCRIPTION:   This function call accepts the internal entry number
 from the  PRESCRIPTION File (#52) as the input, and returns an 'e' to indicate
 if the last fill of the prescription is electronically billable, else a null 
 is returned.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number from the PRESCRIPTION File
 (#52).  
VARIABLES: $$ECME                       TYPE: Output
 VARIABLES DESCRIPTION:   An 'e' if the last fill is electronically billable,
 null if the last fill is not electronically billable.  
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Virtual Patient Record can call $$ECME^PSOBPSUT to
 determine if the last fill of a prescription is electronically billable.  
  DATE ACTIVATED: JUN 06, 2019

NUMBER: 7085                            IA #: 7085
  DATE CREATED: JUN 26, 2019            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS MVI NEW PERSON BULK GET
  REMOTE PROCEDURE: XUS MVI NEW PERSON BULK GET
 GENERAL DESCRIPTION:   In support of the Electronic Health Record
 Modernization (EHRM), the Master Veteran Index (MVI) team requests permission
 to exclusively use the following restricted KERNEL Remote Procedure Call (RPC)
 [XUS MVI NEW PERSON BULK GET], to allow retrieval of 'Active' NEW PERSON file 
 (#200) data in bulk (large chunks) transfers from each VistA site to the MVI.
 When all 'Active' NEW PERSON file (#200) data has been retrieved for a site,
 MVI will export the results to a flat text file where it will then be imported
 by the Person Service Identity Management (PSIM) system so that it can be
 further evaluated.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XUS MVI NEW PERSON BULK GET
KEYWORDS: 200
KEYWORDS: VA(200
KEYWORDS: EHRM
KEYWORDS: XUMVINPB
KEYWORDS: MVI
KEYWORDS: MPI
KEYWORDS: NEW PERSON
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   The Master Veteran Index (MVI) project will use this
 Remote Procedure Call (RPC) to retrieve 'Active' NEW PERSON file (#200) data
 from VistA systems so that it can be exported to the Person Service Identity
 Management (PSIM) system to be further evaluated beginning with patch
 MPI*1.0*129.  
  DATE ACTIVATED: AUG 02, 2019

NUMBER: 7086                            IA #: 7086
  FILE NUMBER: 3.8                      GLOBAL ROOT: XMB(3.8
  DATE CREATED: JUL 01, 2019            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  NAME: MAIL GROUP REMOTE MEMBER AND DESCRIPTION
  ID: XMB(3.8
 GENERAL DESCRIPTION:   Accounts Receivable needs a ONE-TIME ONLY Integration
 Agreement to allow manuipulation of the data in a mail group entry to add an 
 Outlook mailing list as a remote member and update the mail group's 
 description to warn users not to send PII/PHI to this mail group.  Since no
 utility exists to add a remote member to or edit the description of an entry
 in the mail group file, the following access is requested: 
  
 1. The ability to add a remote member to a mail group. This would be done
 once, in the Post-Install routine RCP349.  
  
 2. The ability to edit the description of a mail group to add text warning
 users not to send PII/PHI to this mail group.  
  
 The following code would be used to accomplish both tasks: 
  
  N FDA,IEN,I,WPDATA 
  D BMES^XPDUTL("Add Outlook email group to RCDPE PAYMENTS EXCEPTIONS mail 
 group") 
  S IEN=$$FIND1^DIC(3.8,,"X","RCDPE PAYMENTS EXCEPTIONS") 
  I 'IEN D  Q 
  . D BMES^XPDUTL("Warning: Could not find RCDPE PAYMENTS EXCEPTIONS mail 
 group. Addresses not added.") 
  ; IA TBD 
  S FDA(3.812,"?+"_I_","_IEN_",",.01)="DNSpayerinquiry@DNS" 
  D UPDATE^DIE(,"FDA") 
  ; Update mail group description to warn against sending PII/PHI 
  S WPDATA(1,0)="*** DO NOT SEND PII/PHI! This Mail Group sends to an Outlook
 email address and" 
  S WPDATA(2,0)="should not be used to send data containing PII/PHI ***" 
  D WP^DIE(3.8,IEN_",",3,"A","WPDATA") 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 7087                            IA #: 7087
  DATE CREATED: JUL 09, 2019
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORWDX                        NAME: VIA USE OF LOCK AND UNLOCK ORWDX
  ID: ORWDX
 GENERAL DESCRIPTION:   The Vista Integration Adapter (VIA) calls the
 LOCK^ORWDX and UNLOCK^ORWDX APIs to lock and unlock a patient record as a new
 order is entered for the patient.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: 2022
KEYWORDS: LOCK
KEYWORDS: UNLOCK
KEYWORDS: ORWDX
KEYWORDS: VIA
COMPONENT/ENTRY POINT: LOCK
 COMPONENT DESCRIPTION:   Locks the specified patient record.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 if lock is successful.  
COMPONENT/ENTRY POINT: UNLOCK
 COMPONENT DESCRIPTION:   Unlocks the patient record.  
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   This ICR is to be used for the cirrhosis study in site
 626 only.  

NUMBER: 7088                            IA #: 7088
  DATE CREATED: JUL 11, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGMTU4
  NAME: DGMTU4 - Annual means test date determination
  ID: DGMTU4
 GENERAL DESCRIPTION:   This function evaluates a means test date that is
 passed in, and checks if the date of the annual means test is greater or equal
 to one year prior to the VFA Start Date of January 1, 2013. The VFA Start Date
 is referenced from MAS PARAMETERS (#43) file in the VFA START DATE (#1205)
 field. This Date is checked against the Discontinue Annual Means Test Renewal
 Point Forward Date.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VFA
KEYWORDS: Veteran Financial Assessment
COMPONENT/ENTRY POINT: $$OLDMTPF
 COMPONENT DESCRIPTION:   
  Input  TESTDATE - Means Test Date 
             
  Output 0 for No 
         1 for Yes 
             
   Checks if the date of the annual means test date is more 
   than 1 year old.  
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  DATE ACTIVATED: JUL 19, 2019

NUMBER: 7089                            IA #: 7089
  DATE CREATED: JUL 12, 2019
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7089
  STATUS: Pending

NUMBER: 7090                            IA #: 7090
  FILE NUMBER: 446.6                    GLOBAL ROOT: PRCT(446.6,
  DATE CREATED: JUL 16, 2019            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: GET SPECIALTY COMMANDS FOR BARCODE PRINT
  ID: PRCT(446.6,
GLOBAL REFERENCE: PRCT(446.6,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PRCT(446.6,D0,1
FIELD NUMBER: .01                       FIELD NAME: AFTER OPEN
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PRCT(446.6,D0,2
FIELD NUMBER: .01                       FIELD NAME: BEFORE EACH LABEL
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PRCT(446.6,D0,3
FIELD NUMBER: .01                       FIELD NAME: AFTER EACH LABEL
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Above PAR requests permission to read the Specialty
 Commands file in order to print Barcode labels with the command lines After
 Open, Before Each Label, and After Each Label.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUL 29, 2019

NUMBER: 7091                            IA #: 7091
  DATE CREATED: JUL 29, 2019
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWUX SYMTAB
  REMOTE PROCEDURE: ORWUX SYMTAB
 GENERAL DESCRIPTION:   Although unusual, the purpose of this agreement is to
 grant the Provider Role Change Graphical User Interface (GUI) access to the
 remote procedure call (RPC) ORWUX SYMTAB. Even though the routine is in the
 same namespace as the Provider Role Change GUI, it is a separate Delphi
 application.  
  STATUS: Active
KEYWORDS: ORWUX
KEYWORDS: SYMTAB
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: AUG 02, 2019

NUMBER: 7092                            IA #: 7092
  DATE CREATED: AUG 01, 2019            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  ROUTINE: IBJTU6                       NAME: IB CLAIM REJECT REVIEW INCOMPLETE
  ID: IBJTU6
 GENERAL DESCRIPTION:   This function checks file #361 and returns a flag that
 indicates whether the bill has a reject message, where the review status is
 not complete.  
  STATUS: Pending
KEYWORDS: CLAIM
KEYWORDS: REJECT
KEYWORDS: BILL
KEYWORDS: REVIEW
COMPONENT/ENTRY POINT: BILLREJ2
VARIABLES: BILL                         TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to an entry in #399, BILL/CLAIMS FILE.  
VARIABLES: REJECT                       TYPE: Output
 VARIABLES DESCRIPTION:   Reject status  blank = not found, 
                0     = not a reject or reject message review status is 2 
                        (REVIEW COMPLETE) 
                1     = reject with review status not complete.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE

NUMBER: 7093                            IA #: 7093
  DATE CREATED: AUG 23, 2019
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7093
  STATUS: Pending

NUMBER: 7094                            IA #: 7094
  DATE CREATED: AUG 23, 2019
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7094
  STATUS: Pending

NUMBER: 7095                            IA #: 7095
  FILE NUMBER: 123.3                    GLOBAL ROOT: GMR(123.3,
  DATE CREATED: SEP 05, 2019
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  NAME: IMAGING SCANS THE REQUEST/CONSULTATION FILE FOR IMAGES
  ID: GMR(123.3,
GLOBAL REFERENCE: GMR(123.3,D0,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the name of the procedure that will be requested
 within CPRS.  
FIELD NUMBER: .05                       FIELD NAME: TYPE OF PROCEDURE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field indicates which type of medicine procedure and
 thus which result file in the Medicine Package will hold results for this
 procedure.  
FIELD NUMBER: .04                       FIELD NAME: CLINICAL PROCEDURE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the CP DEFINITIONS (#702.01) file entry for this
 Clinical Procedure.  
GLOBAL REFERENCE: GMR(123.3,D0,2,
FIELD NUMBER: .01                       FIELD NAME: RELATED SERVICES
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field will indicate which Consult services from the
 REQUEST SERVICES (#123.5) file are responsible for the processing of requests
 for this procedure.  
 GENERAL DESCRIPTION:   The Consult/Request Tracking package provides an
 efficient way for clinicians to order consultations and procedures from other
 providers or services within the VHA system, at their own facility or another 
 facility.  It also provides a framework for tracking consults and procedures
 and reporting the results.  It uses a patient's computerized patient record to
 store information about consult and procedure requests and results.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: MAG*3.0*231
KEYWORDS: REQUEST/CONSULTATION (#123)
KEYWORDS: CLINICAL SPECIALTY DICOM & HL7
KEYWORDS: GMRC PROCEDURE (#123.3)
KEYWORDS: STUDY TRACKER
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   VistA Imaging associates images with CPRS Consult
 Request Tracking Consults and Procedures.  We use a couple of fields in the
 GMRC PROCEDURE (#123.3) file in order to do this.  We use the NAME (#.01)
 field, TYPE OF PROCEDURE (#.05) and the RELATED SERVICES (#123.32) sub-file.  
  
 Updated 2/6/26, effective with patch MAG*3.0*362, Adding field .04 Clinical
 Procedure.  

NUMBER: 7096                            IA #: 7096
  DATE CREATED: SEP 13, 2019            CUSTODIAL PACKAGE: ELECTRONIC SIGNATURE
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XOBE ESIG GET DATA
  REMOTE PROCEDURE: XOBE ESIG GET DATA
 GENERAL DESCRIPTION:   The WebVRAM package needs access to the XOBE ESIG GET
 DATA RPC. This RPC returns electronic signature block-related fields from File
 200 from the home facility tracked by the WebVRAM administrative tools.  
  
 "Kernel understands this ICR was created to track which application is using
 the Kernel resource.   The WebVRAM team has been working with IAM and the
 Kernel team for future official alternatives." 
  STATUS: Active
KEYWORDS: KERNEL
KEYWORDS: ESIG
KEYWORDS: WEBVRAM
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
  DATE ACTIVATED: SEP 20, 2019

NUMBER: 7097                            IA #: 7097
  DATE CREATED: SEP 13, 2019            CUSTODIAL PACKAGE: ELECTRONIC SIGNATURE
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XOBE ESIG IS DEFINED
  REMOTE PROCEDURE: XOBE ESIG IS DEFINED
 GENERAL DESCRIPTION:   The WebVRAM package needs access to the XOBE ESIG IS
 DEFINED RPC. This RPC will support WebVRAM electronic signature processing
 that checks if the electronic signature is defined for the user/visitor.  
  
 "Kernel understands this ICR was created to track which application is using
 the Kernel resource.   The WebVRAM team has been working with IAM and the
 Kernel team for future official alternatives." 
  STATUS: Active
KEYWORDS: KERNEL
KEYWORDS: ESIG
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
  DATE ACTIVATED: SEP 20, 2019

NUMBER: 7098                            IA #: 7098
  DATE CREATED: SEP 13, 2019            CUSTODIAL PACKAGE: ELECTRONIC SIGNATURE
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XOBE ESIG SET CODE
  REMOTE PROCEDURE: XOBE ESIG SET CODE
 GENERAL DESCRIPTION:   The WebVRAM package needs to access the XOBE ESIG SET
 CODE RPC to support saving the electronic signature code on VistA systems that
 the visitor is authorized to access.  
  
 "Kernel understands this ICR was created to track which application is using
 the Kernel resource.   The WebVRAM team has been working with IAM and the
 Kernel team for future official alternatives." 
  STATUS: Active
KEYWORDS: KERNEL
KEYWORDS: ESIG
KEYWORDS: WEBVRAM
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
  DATE ACTIVATED: SEP 20, 2019

NUMBER: 7099                            IA #: 7099
  DATE CREATED: SEP 13, 2019            CUSTODIAL PACKAGE: ELECTRONIC SIGNATURE
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XOBE ESIG SET DATA
  REMOTE PROCEDURE: XOBE ESIG SET DATA
 GENERAL DESCRIPTION:   The WebVRAM package needs access to the XOBE ESIG SET
 DATA RPC. This RPC will support saving the electronic signature block on the
 VistA systems that the user/visitor is authorized to access. The signature
 block comes from the home facility's electronic signature block and is 
 propagated by WebVRAM.  
  
 "Kernel understands this ICR was created to track which application is using
 the Kernel resource.   The WebVRAM team has been working with IAM and the
 Kernel team for future official alternatives." 
  STATUS: Active
KEYWORDS: KERNEL
KEYWORDS: ESIG
KEYWORDS: WEBVRAM
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
  DATE ACTIVATED: SEP 20, 2019

NUMBER: 7100                            IA #: 7100
  DATE CREATED: SEP 13, 2019            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XU REBUILD MENU TREE
  REMOTE PROCEDURE: XU REBUILD MENU TREE
 GENERAL DESCRIPTION:   The WebVRAM package needs access to the XU REBUILD MENU
 TREE RPC.  This RPC will be used to rebuild the menu tree for the WebVRAM
 visitor added to a VistA facility.  
  
 "Kernel understands this ICR was created to track which application is using
 the Kernel resource.   The WebVRAM team has been working with IAM and the
 Kernel team for future official alternatives." 
  STATUS: Active
KEYWORDS: KERNEL
KEYWORDS: WEBVRAM
  DATE ACTIVATED: SEP 20, 2019

NUMBER: 7101                            IA #: 7101
  DATE CREATED: SEP 16, 2019            CUSTODIAL PACKAGE: RPC BROKER
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XWB GET BROKER INFO
  REMOTE PROCEDURE: XWB GET BROKER INFO
 GENERAL DESCRIPTION:   The WebVRAM package needs to get the details of the RPC
 broker for use in the web applications used by WebVRAM users and WebVRAM
 administrative users.  
  
 "Kernel understands this ICR was created to track which application is using
 the Kernel resource.   The WebVRAM team has been working with IAM and the
 Kernel team for future official alternatives." 
  STATUS: Active
KEYWORDS: KERNEL
KEYWORDS: WEBVRAM
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 6/18/25 effective with YS*5.01*260 patch. ClouD 
 application MHA is migrating from VistALink to Cocytus, to communicate with
 VistA. In order for MHA to know how frequently to send the heartbeat, MHA
 requires use of this RPC.  
  DATE ACTIVATED: SEP 20, 2019

NUMBER: 7102                            IA #: 7102
  DATE CREATED: SEP 16, 2019            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS GET CCOW TOKEN
  REMOTE PROCEDURE: XUS GET CCOW TOKEN
 GENERAL DESCRIPTION:   The WebVRAM package needs to access the XUS GET CCOW
 TOKEN RPC to get a CCOW token.  
  
 "Kernel understands this ICR was created to track which application is using
 the Kernel resource.   The WebVRAM team has been working with IAM and the
 Kernel team for future official alternatives." 
  STATUS: Active
KEYWORDS: CCOW
KEYWORDS: KERNEL
KEYWORDS: WEBVRAM
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   WEBG*1*0 
  DATE ACTIVATED: SEP 20, 2019

NUMBER: 7103                            IA #: 7103
  DATE CREATED: SEP 16, 2019            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS CCOW VAULT PARAM
  REMOTE PROCEDURE: XUS CCOW VAULT PARAM
 GENERAL DESCRIPTION:   The WebVRAM package need to access the XUS CCOW VAULT
 PARAM RPC to get the CCOW vault parameters.  
  
 "Kernel understands this ICR was created to track which application is using
 the Kernel resource.   The WebVRAM team has been working with IAM and the
 Kernel team for future official alternatives." 
  STATUS: Active
KEYWORDS: CCOW
KEYWORDS: KERNEL
KEYWORDS: WEBVRAM
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   WEBG*1*0 
  DATE ACTIVATED: SEP 20, 2019

NUMBER: 7104                            IA #: 7104
  DATE CREATED: OCT 02, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGENU
  NAME: External Format of Subgroup     ID: DGENU
 GENERAL DESCRIPTION:   The purpose of this Integration Control Registration is
 to grant Order Entry/Results Reporting access to DGENU for the purposes of
 converting the internal format of the ENROLLMENT SUBGROUP field (#.12) from
 the PATIENT ENROLLMENT file (#27.11) to its external value for display 
 purposes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DGENU
COMPONENT/ENTRY POINT: EXT
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   Subscript in the array defined by the PATIENT
 ENROLLMENT object. For the purposes of OE/RR, this will be SUBGRP.  
VARIABLES: VAL                          TYPE: Input
 VARIABLES DESCRIPTION:   Value of the PATIENT ENROLLMENT object attribute
 names by SUB. In other words, the internal value of the field.  
VARIABLES: Function Value               TYPE: Output
 VARIABLES DESCRIPTION:   This returns the external value of the attributed as
 defined by the PATIENT ENROLLMENT file (#27.11).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Order Entry/Results Reporting needs access to the
 ENROLLMENT SUBGROUP field (#.12) external value in order to display the
 information in the patient inquiry in the Computerized Patient Record System.  
  DATE ACTIVATED: OCT 02, 2019

NUMBER: 7105                            IA #: 7105
  DATE CREATED: OCT 09, 2019
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  ROUTINE: TIUSRVLO                     NAME: FIXDATE TIUSRVLO API
  ID: TIUSRVLO
 GENERAL DESCRIPTION:   FIXDATE^TIUSRVLO changes the array data in the TIUY
 parameter.  It relies on the "INDX" index and data structure created by such
 APIs as CONTEXT^TIUSRVLO and GETCSLT^ORQQCN1 to already exist in the array
 named by the TIUY parameter.  The PARENT parameter is piece 14 of the child 
 note, and the CDATE is the date of the child document.  If the parent document
 exists, and the child date is more recent than the parent documents date, it
 moves the parent documents date stored in piece 3 to piece 17, and stores the
 child's date in piece 3.  It then recursively calls FIXDATE again on the
 parent of the parent, to propogate the most recent child date to the top of
 the tree structure.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIUSRVLO
COMPONENT/ENTRY POINT: FIXDATE
VARIABLES: TIUY
VARIABLES: PARENT
VARIABLES: CDATE
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 7106                            IA #: 7106
  DATE CREATED: OCT 15, 2019
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWU VERSRV
  REMOTE PROCEDURE: ORWU VERSRV
 GENERAL DESCRIPTION:   ORWU VERSRV ICR #7106 is used by WebVRAM to lookup the
 OR CPRS GUI CHART option to get the CPRSChart version on a particular VistA
 System.  
  STATUS: Active
KEYWORDS: CPRS VERSION
KEYWORDS: WebVRAM
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   If a WebVRAM user needs to access CPRS at a particular
 facility, then WebVRAM calls ORWU VERSRV at the facility to determine which
 version of CPRS should be opened for the user.  
  DATE ACTIVATED: OCT 17, 2019

NUMBER: 7107                            IA #: 7107
  DATE CREATED: NOV 14, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPFAA
  NAME: DGPFAA                          ID: DGPFAA
 GENERAL DESCRIPTION:   This documents the use of tags in routine DGPFAA to
 retrieve patient record flags.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETALL
 COMPONENT DESCRIPTION:   This function returns an array of patient record flag
 assignment IENs for a given patient. The returned IEN array may be optionally 
 filtered by Active or Inactive status and by flag category.  
VARIABLES: DGDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to patient in PATIENT (#2) file [required] 
VARIABLES: DGIENS                       TYPE: Both
 VARIABLES DESCRIPTION:   Result array passed by reference [required] Returns
 output array subscripted by the assignment IENs 
VARIABLES: DGSTAT                       TYPE: Input
 VARIABLES DESCRIPTION:   Status filter (0:Inactive,1:Active,"":Both), defaults
 to Both 
VARIABLES: DGCAT                        TYPE: Input
 VARIABLES DESCRIPTION:   Category filter (1:Category I,2:Category II,"":Both), 
 defaults to Both 
VARIABLES: $$GETALL                     TYPE: Output
 VARIABLES DESCRIPTION:   Count of returned IENs 
COMPONENT/ENTRY POINT: GETASGN
 COMPONENT DESCRIPTION:   This function returns a single patient record flag
 assignment in an array format.  
VARIABLES: DGPFIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to patient record flag assignment in PRF
 ASSIGNMENT (#26.13) file 
VARIABLES: DGPFA                        TYPE: Both
 VARIABLES DESCRIPTION:   Result array passed by reference; returns array
 containing assignment record values.  
VARIABLES: $$GETASGN                    TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 on success, 0 on failure 
COMPONENT/ENTRY POINT: FNDASGN
 COMPONENT DESCRIPTION:   This function finds a patient record flag assignment
 record.  
VARIABLES: DGDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to patient in the PATIENT (#2) file 
VARIABLES: DGFLAG                       TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to flag in either the PRF LOCAL FLAG (#26.11)
 file or the PRF NATIONAL FLAG (#26.15) file 
VARIABLES: $$FNDASGN                    TYPE: Output
 VARIABLES DESCRIPTION:   Returns IEN of existing record on success, 0 on
 failure 
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 1/14/21 to support the Suicide High Risk Patient
 Enhancements Project Phase 2 (SHRPE 2.0) with Patch OR*3.0*542, which 
 implements enhanced display information for the Active Patient Record Flag 
 (PRF) displayed in the CPRS application.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   Added 2/18/21 to support Suicide High Risk Patient
 Enhancements Project Phase 2 (SHRPE 2.0), PRCA*4.5*373.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 1/25/23, effective with DSSV*1.0*1 DSS Class 2
 product Document Only 
  DATE ACTIVATED: NOV 22, 2019

NUMBER: 7108                            IA #: 7108
  DATE CREATED: NOV 14, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPFAAH
  NAME: DGPFAAH                         ID: DGPFAAH
 GENERAL DESCRIPTION:   This documents the use of tags in routine DGPFAAH to
 retrieve patient record flag activity.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETHIST
 COMPONENT DESCRIPTION:   Retrieve a single assignment history record 
VARIABLES: DGPFIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN for record in PRF ASSIGNMENT HISTORY (#26.14)
 file 
VARIABLES: DGPFAH                       TYPE: Both
 VARIABLES DESCRIPTION:   Result array passed by reference containing the field
 values 
VARIABLES: $$GETHIST                    TYPE: Output
 VARIABLES DESCRIPTION:   Return 1 on success, 0 on failure 
COMPONENT/ENTRY POINT: GETFIRST
 COMPONENT DESCRIPTION:   This function returns the IEN of the initial history
 record for a given patient record flag assignment.  
VARIABLES: DGPFIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of record in PRF ASSIGNMENT (#26.13) file 
VARIABLES: $$GETFIRST                   TYPE: Output
 VARIABLES DESCRIPTION:   IEN of initial history record on success, or 0 on
 failure 
COMPONENT/ENTRY POINT: GETLAST
 COMPONENT DESCRIPTION:   This function returns the IEN of the most recent
 history record for a given patient record flag assignment.  
VARIABLES: DGPFIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN for record in PRF ASSIGNMENT (#26.13) file 
VARIABLES: $$GETLAST                    TYPE: Output
 VARIABLES DESCRIPTION:   IEN of last history record on success, or 0 on
 failure 
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Effective with Suicide High Risk Patient Enhancements
 Project Phase 2 (SHRPE 2.0), OR*3.0*542.  
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   Added 2/18/21 to support Suicide High Risk Patient
 Enhancements Project Phase 2 (SHRPE 2.0), PRCA*4.5*373.  
  DATE ACTIVATED: NOV 22, 2019

NUMBER: 7109                            IA #: 7109
  DATE CREATED: NOV 26, 2019            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VADPT
  NAME: VADPT                           ID: VADPT
 GENERAL DESCRIPTION:   VADPT is a utility routine designed to provide a
 central point where a programmer can obtain information concerning a patient's
 record.  Supported entry points are provided which will return demographics, 
 inpatient status, eligibility information, etc. This ICR is in addition to ICR
 10061, it does not replace 10061. 
  
 Access to patient information is not limited to using the supported entry 
 points in VADPT.  Integration agreements can be established through the DBA
 between REGISTRATION and other packages to reference information.  
  
 This integration agreement does not document the input and output variables
 for any of the components of VADPT. That documentation is located in the PIMS
 technical manual, section 12.2 CALLABLE ENTRY POINTS IN VADPT, i.e.
 DEMUPD^VADPT. 
  STATUS: Active
COMPONENT/ENTRY POINT: DEMUPD
 COMPONENT DESCRIPTION:   Basic patient demographic information, and the
 patient's Preferred Name, along with VA("BID") and VA("PID").  
  DATE ACTIVATED: NOV 27, 2019

NUMBER: 7110                            IA #: 7110
  DATE CREATED: NOV 27, 2019            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: EDIT SDAM PCE EVENT PROTOCOL
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SDAM PCE EVENT PROTOCOL
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   The protocol, SDAM PCE EVENT is attached to PXK VISIT
 DATA EVENT, its Entry Action is D EN^SDPCE. In patch PX*1*211, the call to
 EN^SDPCE is moved from PXK VISIT DATE EVENT to a direct call in the routine
 EVENT^PXKMAIN. To facilitate and document the move the Description and Entry
 Point of SDAM PCE EVENT need to be edited. This ICR allows PCE to make these
 edits using FILE^DIE as part of the post-init of PX*1.0*211.  
  
 Changes made to the SDAM PCE EVENT protocol by PX*1.0*211: 
  
 NAME: SDAM PCE EVENT                    ITEM TEXT: PROCESS PCE EVENT DATA 
   TYPE: action                          CREATOR: TESTMASTER,USER 
   PACKAGE: SCHEDULING 
  DESCRIPTION:   This protocol is the event handler attached to the PXK VISIT
 DATA EVENT protocol.  
   
  The protocol processes scheduled appointment check out data made available by
 this PCE event point. PCE currently obtains this check out data from MCCR data
 capture pilots and also a manual entry module within the PCE package.  
   
  To allow processing of the other items attached to PXK VISIT DATA EVENT as a
 TaskMan job, the call to EN^SDPCE was moved to EVENT^PXKMAIN in patch 
  PX*1*211.  
   ENTRY ACTION: ;D EN^SDPCE             TIMESTAMP: 56847,61845 
  DATE ACTIVATED: AUG 21, 2024

NUMBER: 7111                            IA #: 7111
  DATE CREATED: DEC 04, 2019
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Routine
  ROUTINE: RARTFLDS
  NAME: RA RETURN COMPUTED FIELD DATA FROM RADIOLOGY RPTS
  ID: RARTFLDS                          STATUS: Pending
  DURATION: Till Otherwise Agreed
KEYWORDS: MAG*3.0*231
KEYWORDS: MAGDSTD2
KEYWORDS: RAD EXAMS W/O VI IMAGES
COMPONENT/ENTRY POINT: RARTFLDS
VARIABLES: RAEXFLD                      TYPE: Input
 VARIABLES DESCRIPTION:   RAEXFLD is set to an abbreviated string to identify
 the data returned.  
  
 Example: 
 --------
 S RAEXFLD="LOC" will return the imaging location of the radiology exam.  
  
 S RAEXFLD="PROC" will return the procedure performed as part of the radiology
 exam.  
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   VistA Imaging calls the routine RARTFLDS to return
 VistA Radiology data specific to a patient care event.  

NUMBER: 7112                            IA #: 7112
  DATE CREATED: DEC 04, 2019
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Other
  NAME: RA SUPERVISOR MENU W/VISTA IMAGING ITEMS ATTACHED
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: MAG*3.0*231
KEYWORDS: Q/R STUDY TRACKER
KEYWORDS: RADIOLOGY STUDY W/IMAGES
KEYWORDS: RADIOLOGY BATCH Q/R RUNS
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   The patch MAG*3.0*231 adds a sub-menu 'Radiology Study
 Tracker Menu'[MAGD RAD STUDY TRACKER] to 'Supervisor Menu' [RA SUPERVISOR].  

NUMBER: 7113                            IA #: 7113
  DATE CREATED: DEC 05, 2019            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RMPRPIU6
  NAME: PIP Stock Issue Update Utility Access
  ID: RMPRPIU6
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call PROSTHETICS routine RMPRPIU6 that
 issues stock to a patient from the Prosthetics Inventory Package (PIP).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
COMPONENT/ENTRY POINT: $$ISS(RMPR60,RMPR11,RMPR5)
VARIABLES: RMPR60                       TYPE: Both
 VARIABLES DESCRIPTION:   Array of data fields for the RECORD OF PROS
 APPLIANCE/REPAIR (#660) file: 
    (all elements are required unless otherwise indicated) 
    RMPR60("PATIENT IEN") - PROSTHETIC PATIENT (#665) IEN        
                            (file 660 field #.02) 
    RMPR60("ISSUE TYPE") - Type of Issue (field #2) 
    RMPR60("QUANTITY") - Number of items issued (field #5) 
    RMPR60("IFCAP ITEM") - IFCAP Item (field #4) 
    RMPR60("VENDOR IEN") - Item Vendor (field #7) 
    RMPR60("SERIAL NUM") - Serial Number (field #9)-optional 
    RMPR60("REQ TYPE") - Request Type (field #11)- 
                         optional-defaults to 11 
    RMPR60("REMARKS") - Comments (field #16)-optional 
    RMPR60("LOT NUM") - Lot Number (field #21)-optional 
    RMPR60("CPT MOD") - CPT modifier string (field #4.7)- 
                        optional 
    RMPR60("COST") - Total value of issue (field #14) 
    RMPR60("CPT IEN") - HCPCS - ^ICPT IEN - (field #4.1) 
    RMPR60("SITE IEN") - PROSTHETIC SITE PARAMETERS file (#669.9) IEN 
    RMPR60("USER") - Initiator (field #27) 
    RMPR60("PAT CAT") - Patient Category (field #62) 
    RMPR60("SPEC CAT") - Special Category (field #63)-optional 
    RMPR60("GROUPER") - AMIS Grouper (field #68) 
    RMPR60("DATE&TIME") - Date and Time Received 
VARIABLES: RMPR11                       TYPE: Both
 VARIABLES DESCRIPTION:   Array of data fields for PROSTHETICS HCPCS ITEM
 MASTER (#661.11) 
          file: 
    RMPR11("STATION") - Station IEN (field #4) 
    RMPR11("HCPCS") - HCPCS code (field #.01) 
    RMPR11("ITEM") - Item number (field #7) 
    RMPR11("UNIT") - Unit of Issue (field #5) 
    RMPR11("DESCRIPTION") - Item Description (field #2) 
    RMPR11("SOURCE") - Source (field #4) 
VARIABLES: RMPR5                        TYPE: Both
 VARIABLES DESCRIPTION:   Array of data fields for PROSTHETIC STOCK LOCATION
 (#661.5) file: 
    RMPR5("IEN") - Location IEN (#661.5) 
VARIABLES: RMPRERR                      TYPE: Output
 VARIABLES DESCRIPTION:   Function Error Code: 
    0 - no problems 
    9 - insufficient stock to issue 
   10 - PIP item is locked 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JAN 13, 2020

NUMBER: 7114                            IA #: 7114
  DATE CREATED: DEC 05, 2019            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RMPRPIUA
  NAME: PIP Scan Barcode Access         ID: RMPRPIUA
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call PROSTHETICS routine RMPRPIUA to
 scan a Prosthetics Inventory Package (PIP) item's barcode and locate the
 record in the PROSTHETIC CURRENT STOCK (#661.7) file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: LPS
COMPONENT/ENTRY POINT: $$SCAN(RMPR7,RMPREXC)
VARIABLES: RMPR7                        TYPE: Both
 VARIABLES DESCRIPTION:   On input, this array contains: 
    RMPR7("STATION") - Station IEN (P4) 
    RMPR7("HCPCS") - HCPCS Code (contained in bar code) 
    RMPR7("DATE&TIME") - DATE&TIME STAMP (contained in bar code) 
  
 On output, this array contains the following fields from the PROSTHETIC
 CURRENT STOCK file (#661.7): 
    RMPR7("IEN") - PROSTHETIC CURRENT STOCK (#661.7) file IEN 
    RMPR7("STATION") - field #4 STATION 
    RMPR7("HCPCS") - field #.01 HCPCS 
    RMPR7("SEQUENCE") - field #2 SEQUENCE 
    RMPR7("HCPCS ITEM") - field #3 HCPCS ITEM 
    RMPR7("LOCATION") - field #5 LOCATION 
    RMPR7("QUANTITY") - field #6 QUANTITY 
    RMPR7("VALUE") - field #7 VALUE 
    RMPR7("UNIT" - field #8 UNIT OF ISSUE 
VARIABLES: RMPREXC                      TYPE: Output
 VARIABLES DESCRIPTION:   Exit Condition: 
    0 -> normal, everything ok 
    1 -> multi-instance but with station match (RMPR7 set) 
    2 -> single instance but with station mis-match (RMPR7 set) 
    3 -> multi-instance and station mis-match (RMPR7 not set) 
VARIABLES: RMPRERR                      TYPE: Output
 VARIABLES DESCRIPTION:   Function Error Code: 
   0  -> no error 
   1  -> null HCPCS input 
   2  -> null Date&Time entered 
   3  -> corrupt file (sequence but no IEN) 
   4  -> corrupt file (ien but no record) 
   5  -> error reading 661.7 
   99 -> no instances found for input HCPCS and Date&Time 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JAN 13, 2020

NUMBER: 7115                            IA #: 7115
  DATE CREATED: DEC 05, 2019            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RMPRPIUV
  NAME: Get Current Stock for Vendors Access
  ID: RMPRPIUV
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call PROSTHETICS routine RMPRPIUV to
 access an array containing vendors, quantity on hand, and unit cost for a
 specified station, location, HCPCS, and item.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: LPS
COMPONENT/ENTRY POINT: $$STOCK(RMPR,RMPRV)
VARIABLES: RMPR                         TYPE: Input
 VARIABLES DESCRIPTION:   Array of data fields with the following elements: 
    RMPR("STATION IEN") - Station IEN (P4) 
    RMPR("LOCATION IEN") - Location IEN (P661.5) 
    RMPR("HCPCS") - HCPCS Code (e.g. - "E0111") 
    RMPR("ITEM") - HCPCS Item Number (eg. - 1) 
VARIABLES: RMPRV                        TYPE: Output
 VARIABLES DESCRIPTION:   Array of vendors: 
   ^-piece 1 - Number of Vendors returned 
   RMPRV(RMPR6("VENDOR IEN")) - 
     ^-piece 1 - Quantity on Hand 
     ^-piece 2 - Unit Cost 
     ^-piece 3 - Vendor 
VARIABLES: RMPRERR                      TYPE: Output
 VARIABLES DESCRIPTION:   Function Error Code: 
   0 - no errors 
   1 - null Station IEN input 
   2 - null Location IEN input 
   3 - null HCPCS Code input 
   4 - null Item input 
   5 - problem with 661.7 file 
   6 - problem with 661.6 file 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JAN 13, 2020

NUMBER: 7116                            IA #: 7116
  DATE CREATED: DEC 06, 2019            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RMPRPIX1
  NAME: PIP HCPCS Item File API Access  ID: RMPRPIX1
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call several entry points in
 PROSTHETICS routine RMPRPIX1 when creating a Prosthetics Inventory Package
 (PIP) stock issue.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: LPS
COMPONENT/ENTRY POINT: $$ETOI(RMPRE,RMPRI)
VARIABLES: RMPRE                        TYPE: Input
 VARIABLES DESCRIPTION:   Array of data fields from the PROSTHETICS HCPCS ITEM
 MASTER (#661.11) including: 
   RMPRE("IEN") - the PROSTHETICS HCPCS ITEM MASTER file (#661.11) IEN 
VARIABLES: RMPRI                        TYPE: Output
 VARIABLES DESCRIPTION:   Array of data fields containing PROSTHETICS HCPCS
 ITEM MASTER file (#661.11) fields in internal format: 
   RMPRI("IEN") - specified PROSTHETICS HCPCS ITEM MASTER file(#661.11) IEN 
   RMPRI("HCPCS") - field #.01 HCPCS 
   RMPRI("ITEM") - field #1 HCPCS ITEM 
   RMPRI("DESCRIPTION") - field #2 DESCRIPTION 
   RMPRI("STATION") - field #3 STATION 
   RMPRI("SOURCE") - field #4 SOURCE 
   RMPRI("UNIT") - field #5 UNIT OF ISSUE 
   RMPRI("ITEM MASTER IEN") - field #7 ITEM MASTER 
VARIABLES: RMPRERR                      TYPE: Output
 VARIABLES DESCRIPTION:   Function Error Code: 
   RMPRERR = 0 - no errors 
           = 1 - error retrieving data from the PROSTHETICS HCPCS ITEM 
                 MASTER file (#661.11) using GETS^DIQ 
COMPONENT/ENTRY POINT: $$GET(RMPR)
VARIABLES: RMPR                         TYPE: Both
 VARIABLES DESCRIPTION:   Input:  
   Array of fields containing: 
     RMPR("IEN") - PROSTHETICS HCPCS ITEM file #661.11 IEN 
  
 Output: 
   Array of data fields from the PROSTHETICS HCPCS ITEM file (#661.11) 
   including: 
     RMPR("IEN") - PROSTHETICS HCPCS ITEM file 661.11 IEN 
     RMPR("HCPCS") - field  #.01 HCPCS 
     RMPR("ITEM") - field #1 HCPCS ITEM 
     RMPR("DESCRIPTION") - field #2 DESCRIPTION 
     RMPR("STATION") - field #3 STATION 
     RMPR("SOURCE") - field #4 SOURCE 
     RMPR("UNIT") - field #5 UNIT OF ISSUE 
     RMPR("HCPCS-ITEM") - field #6 PSAS ITEM 
     RMPR("ITEM MASTER") - field #7 ITEM MASTER 
     RMPR("STATUS") - field #8 STATUS 
VARIABLES: RMPRCRE                      TYPE: Output
 VARIABLES DESCRIPTION:   Function Exit Code: 
   RMPRCRE = 0 - no problems 
           = 1 - problems retrieving data from file 661.11 
                 using GETS^DIQ 
COMPONENT/ENTRY POINT: $$HPACT(RMPR)
VARIABLES: RMPR                         TYPE: Both
 VARIABLES DESCRIPTION:   Input: 
   Array of data fields from the PROSTHETIC HCPCS file (#661.1) including: 
     RMPR("HCPCS") - HCPCS Code 
  
 Output: 
   Array of data fields containing the following fields for all PROSTHETIC 
 HCPCS IENs for the specified HCPCS code: 
     RMPR("IEN") - PROSTHETIC HCPCS file (#661.1 ) IEN 
     RMPR("HCPCS") - field #.01 HCPCS 
     RMPR("SHORT DESC") - field #.02 SHORT NAME 
     RMPR("NEW HCPC IEN") - field #1 NEW HCPCS CODE 
     RMPR("CPT CODE") - field #2 CPT 
     RMPR("STATUS") - field #3 STATUS 
     RMPR("NPPD REPAIR CODE") - field #5 NPPD REPAIR CODE 
     RMPR("NPPD NEW CODE") - field #6 NPPD NEW CODE 
     RMPR("CALC FLAG") - field #9 CALCULATION FLAG 
     RMPR("INV FLAG") - field #10 INVENTORY FLAG 
     RMPR("LAB TIME") - field #11 PRE-DETERMINED LAB TIME 
VARIABLES: RMPRCRE                      TYPE: Output
 VARIABLES DESCRIPTION:   Function Error Code: 
    RMPRCRE = 0 - no problems 
            = 1 - null RMPR("IEN") 
            = 2 - error occurred when retrieving a record from file 
                  661.1 using GETS^DIQ 
COMPONENT/ENTRY POINT: $$HPETOI(RMPRE,RMPRI)
VARIABLES: RMPRE                        TYPE: Input
 VARIABLES DESCRIPTION:   RMPRE - array of external values for PROSTHETIC HCPCS
 (#661.1) file: 
   RMPRE("IEN") - PROSTHETIC HCPCS (#661.1) file IEN 
VARIABLES: RMPRI                        TYPE: Output
 VARIABLES DESCRIPTION:   Array of data fields from the PROSTHETIC HCPCS file
 (#661.1) in internal 
         format including: 
   RMPRI("IEN") - set to the specified PROSTHETIC HCPCS file 
                  (#661.1) IEN 
   RMPRI("NEW HCPC IEN") - field #1 NEW HCPC CODE 
   RMPRI("CPT CODE") - field #2 CPT 
   RMPRI("STATUS") - field #3 STATUS 
   RMPRI("NPPD REPAIR CODE") - field #5 NPPD REPAIR CODE 
   RMPRI("NPPD NEW CODE") - field #6 NPPD NEW CODE 
   RMPRI("CALC FLAG") - field #9 CALCULATION FLAG 
   RMPRI("INV FLAG") - field #10 INVENTORY FLAG 
   RMPRI("LAB TIME") - field #11 PRE-DETERMINED LAB TIME 
VARIABLES: RMPRERR                      TYPE: Output
 VARIABLES DESCRIPTION:   Function Error Code - 
    RMPRERR=0 - no errors 
           =1 - error occurred when retrieving specified PROSTHETIC 
                HCPCS file (#661.1) 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/17/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requests permission to call
 RMPRPIX1 
  DATE ACTIVATED: JAN 13, 2020

NUMBER: 7117                            IA #: 7117
  DATE CREATED: DEC 06, 2019            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RMPRPIX2
  NAME: PIP APIs for Patient 2319 Access
  ID: RMPRPIX2
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call PROSTHETICS routine RMPRPIX2 to
 update the AMIS GROUPER (#7) in the PROSTHETIC SITE PARAMETERS file (#669.9).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: LPS
COMPONENT/ENTRY POINT: $$AMGR
VARIABLES: RMPR699                      TYPE: Input
 VARIABLES DESCRIPTION:   Array of fields used in updating the GROUPER COUNTER
 field (#11) in the PROSTHETIC SITE PARAMETERS file (#669.9): 
  
    RMPR699("IEN") - IEN of PROSTHETIC SITE PARAMETERS file (#669.9) 
                     to be updated 
VARIABLES: RMPRRET                      TYPE: Output
 VARIABLES DESCRIPTION:   Function Error Code: RMPRRET = 0 - normal processing 
         = 1 - error returned from update of file 669.9 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   PROSTHETICS VISION 4 SIGHT II Added 04/22/25, effective
 with PROSTHETICS VISION 4 SIGHT II patch RMPV*1*1, the Prosthetics package
 requires access to the routine RMPRPIX2, component $$AMGR and add component
 $$UPD,.  
  DATE ACTIVATED: JAN 13, 2020

NUMBER: 7118                            IA #: 7118
  DATE CREATED: DEC 06, 2019            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RMPRPIX6
  NAME: PIP PROS INVENTORY TRANSACTIONS API ACCESS
  ID: RMPRPIX6
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call PROSTHETICS routine RMPRPIX6 to
 retrieve information about a specific vendor.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: LPS
COMPONENT/ENTRY POINT: $$GET(RMPR)
VARIABLES: RMPR                         TYPE: Both
 VARIABLES DESCRIPTION:   Array of data fields that relate to the specified
 PROS INVENTORY TRANSACTIONS file (#661.6):  
  
    RMPR("IEN") - input value-PROS INVENTORY TRANSACTIONS file #661.6 IEN 
    RMPR("HCPCS") - input/output value - field #.01 HCPCS 
    RMPR("DATE&TIME") - input/output value - field #2 DATE&TIME STAMP 
    RMPR("DATE") - first "@"-piece of field #2 DATE&TIME STAMP 
    RMPR("TIME") - second "@"-piece of field #2 DATE&TIME STAMP 
    RMPR("SEQUENCE") - field #3 SEQUENCE 
    RMPR("TRAN TYPE") - field #4 TRANSACTION TYPE 
    RMPR("QUANTITY") - field #5 QUANTITY 
    RMPR("VALUE") - field #6 VALUE 
    RMPR("COMMENT") - field #8 COMMENT 
    RMPR("USER") - field #9 USER 
    RMPR("ITEM") - field #11 ITEM 
    RMPR("VENDOR") - field #12 VENDOR 
    RMPR("STATION") - field #13 STATION 
    RMPR("LOCATION") - field #14 LOCATION 
VARIABLES: RMPRRET                      TYPE: Output
 VARIABLES DESCRIPTION:   RMPRRET =0 - successful processing 
         =1 - RMPR("HCPCS") null or RMPRKEY("SEQUENCE") does not exist 
         =2 - RMPR("DATE&TIME") null 
         =3 - Error returned from $$NEXT^RMPRPIXA 
         =4 - RMPRKEY("SEQUENCE") is not equal to 1 
         =5 - Error returned from GETS^DIQ of file 661.6 
COMPONENT/ENTRY POINT: $$VNDIEN(RMPR)
VARIABLES: RMPR                         TYPE: Both
 VARIABLES DESCRIPTION:   Array containing data values from the PROS INVENTORY
 TRANSACTIONS file (#661.6): 
  
   RMPR("IEN") - PROS INVENTORY TRANSACTIONS file (#661.6) IEN - input 
   RMPR("VENDOR IEN") - VENDOR file (#440) IEN - output from PROS 
                        INVENTORY TRANSACTIONS file (#661.6) 
                        field #12 VENDOR 
VARIABLES: RMPRERR                      TYPE: Output
 VARIABLES DESCRIPTION:   Function Error Code: 
         =0 - successful processing 
         =1 - an error occurred 
COMPONENT/ENTRY POINT: $$VNDIEN(RMPR)
COMPONENT/ENTRY POINT: UPD
VARIABLES: RMPR616                      TYPE: Input
 VARIABLES DESCRIPTION:   Transaction array 
VARIABLES: RMPR6111                     TYPE: Input
 VARIABLES DESCRIPTION:   HCPCS array 
VARIABLES: RMPRRET                      TYPE: Output
 VARIABLES DESCRIPTION:   error code returned by function 
         0 - no problems 
         1 - invalid RMPR616("IEN") 
         2 - FM problem with update 
COMPONENT/ENTRY POINT: ETOI
 COMPONENT DESCRIPTION:   convert external to internal form 
VARIABLES: RMPRE                        TYPE: Input
 VARIABLES DESCRIPTION:   array of values from file 661.6 
VARIABLES: RMPRI                        TYPE: Output
 VARIABLES DESCRIPTION:   same as input values w/ some values converted to
 Internal FM format 
VARIABLES: RMPRERR                      TYPE: Output
 VARIABLES DESCRIPTION:   0:success, 1:failure 
COMPONENT/ENTRY POINT: CRE
 COMPONENT DESCRIPTION:   Create a new 661.1 PIP Transaction record 
VARIABLES: RMPR616                      TYPE: Input
 VARIABLES DESCRIPTION:   Transaction array (661.6) (elements mandatory unless
 noted) 
        RMPR616("DATE&TIME") - (optional) usually should not be set 
                               but if it is RMPR616("SEQUENCE") 
                               must also be set 
        RMPR616("SEQUENCE")  - (optional) but see above 
                               should normally be one 
        RMPR616("VENDOR")      - Vendor ien 
        RMPR616("LOCATION")    - Location ien (ptr 661.5) 
        RMPR616("TRAN TYPE")   - Transaction Type code (see 661.6 spec) 
        RMPR616("QUANTITY")    - Quantity 
        RMPR616("VALUE")       - $ Value of transaction 
        RMPR616("COMMENT")     - Comment 
        RMPR616("USER")        - User ien (ptr VA(200,) 
VARIABLES: RMPR616('IEN')               TYPE: Output
 VARIABLES DESCRIPTION:   ien of created Transaction 
VARIABLES: RMPRRET                      TYPE: Output
 VARIABLES DESCRIPTION:   error code returned by function 
                        0 - no problems 
                        1 - FM problems creating 661.6 rec.  
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/23/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires permission to call
 RMPRPIX6, components UPD and ETOI .Added 5/12/25, component CRE.  
  DATE ACTIVATED: JAN 13, 2020

NUMBER: 7119                            IA #: 7119
  DATE CREATED: DEC 06, 2019            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RMPRPIX7
  NAME: PIP PROSTHETIC CURRENT STOCK APIS ACCESS
  ID: RMPRPIX7
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call PROSTHETICS routine RMPRPIX7 to
 read the fields and calculate the total quantity on hand in the PROSTHETIC
 CURRENT STOCK file (#661.7).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: LPS
COMPONENT/ENTRY POINT: $$BAL(RMPR11)
VARIABLES: RMPR11                       TYPE: Input
 VARIABLES DESCRIPTION:   Array of data fields associated with the PROSTHETIC
 CURRENT STOCK file (#661.7): 
  
 RMPR11("STATION") - pointer to INSTITUTION file (#4) RMPR11("LOCATION") -
 pointer to PROSTHETIC STOCK LOCATION 
                      file (#661.5) RMPR11("HCPCS") - pointer to PROSTHETIC
 HCPCS file (#661.1) RMPR11("ITEM") - pointer to PROSTHETIC HCPCS file (#661.1) 
                  ITEM subfile (#661.12) 
VARIABLES: RMUB                         TYPE: Output
 VARIABLES DESCRIPTION:   Total quantity on hand - total of quantity of stock
 for all related PROSTHETIC CURRENT STOCK file (#661.7) records 
COMPONENT/ENTRY POINT: $$ETOI(RMPRE,RMPRI)
VARIABLES: RMPRE                        TYPE: Input
 VARIABLES DESCRIPTION:   Array containing data values from the PROSTHETIC
 CURRENT STOCK file (#661.7) in external format: 
  
 RMPRE("IEN") - PROSTHETIC CURRENT STOCK file (#661.7) IEN 
VARIABLES: RMPRI                        TYPE: Output
 VARIABLES DESCRIPTION:   Array containing data values from the PROSTHETIC
 CURRENT STOCK file (#661.7) in internal format: 
  
 RMPRI("IEN") - points to the PROSTHETIC CURRENT STOCK file (#661.7) 
 RMPRI("HCPCS") - field #.01 HCPCS RMPRI("DATE&TIME") - field #1 DATE&TIME
 STAMP RMPRI("ITEM") - field #3 HCPCS ITEM RMPRI("SEQUENCE") - field #2
 SEQUENCE RMPRI("STATION") - field #4 STATION RMPRI("LOCATION") - field #5
 LOCATION RMPRI("UNIT") - field #8 UNIT OF ISSUE RMPRI("QUANTITY") - field #6
 QUANTITY RMPRI("VALUE") - field #7 VALUE 
VARIABLES: RMPRERR                      TYPE: Output
 VARIABLES DESCRIPTION:   Function Error Code: 
    RMPRERR =0 - successful processing 
            =1 - error retrieving data from file 661.7 using GETS^DIQ 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JAN 13, 2020

NUMBER: 7120                            IA #: 7120
  FILE NUMBER: 661.5                    GLOBAL ROOT: RMPR(661.5,
  DATE CREATED: DEC 06, 2019            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PROSTHETIC STOCK LOCATION FILE ACCESS
  ID: RMPR(661.5,
GLOBAL REFERENCE: RMPR(661.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Stock location name 
FIELD NUMBER: 2                         FIELD NAME: STATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   INSTITUTION file (#4) pointer 
FIELD NUMBER: 3                         FIELD NAME: ADDRESS
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Stock location address 
FIELD NUMBER: 4                         FIELD NAME: STATUS
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Indication that a stock location is active or inactive 
FIELD NUMBER: 5                         FIELD NAME: STATUS CHANGE DATE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The date when the status of a stock location is changed 
FIELD NUMBER: 6                         FIELD NAME: USER
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to the NEW PERSON file (#200) for the user who
 last updated the stock location record 
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) read access to all fields of the
 PROSTHETIC STOCK LOCATION file (#661.5) when creating a Prosthetics Inventory
 Package (PIP) stock issue.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: LPS
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/23/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires information for the
 Prosthetic Stock Location File Access 
  DATE ACTIVATED: JAN 13, 2020

NUMBER: 7121                            IA #: 7121
  FILE NUMBER: 661.7                    GLOBAL ROOT: RMPR(661.7,
  DATE CREATED: DEC 06, 2019            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PROSTHETIC CURRENT STOCK FILE ACCESS
  ID: RMPR(661.7,
GLOBAL REFERENCE: RMPR(661.7,D0,0)
FIELD NUMBER: .01                       FIELD NAME: HCPCS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to the PROSTHETIC HCPCS file (#661.1) 
FIELD NUMBER: 1                         FIELD NAME: DATE&TIME STAMP
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Date and time at which this HCPCS was added to this file 
FIELD NUMBER: 2                         FIELD NAME: SEQUENCE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The same SEQUENCE as in the PROSTHETIC INVENTORY
 TRANSACTION file (#661.6) 
FIELD NUMBER: 3                         FIELD NAME: HCPCS ITEM
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to the ITEM (#661.12) subfile of the PROSTHETIC
 HCPCS file (#661.1) 
FIELD NUMBER: 4                         FIELD NAME: STATION
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to the INSTITUTION file (#4) 
FIELD NUMBER: 5                         FIELD NAME: LOCATION
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to the PROSTHETIC STOCK LOCATION file (#661.5) 
FIELD NUMBER: 6                         FIELD NAME: QUANTITY
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Quantity of stock 
FIELD NUMBER: 7                         FIELD NAME: VALUE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Total dollar value of the stock item held on this record 
FIELD NUMBER: 8                         FIELD NAME: UNIT OF ISSUE
  LOCATION: 0;9                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Pointer to UNIT OF ISSUE file (#420.5) 
GLOBAL REFERENCE: RMPR(661.7,'XHDS')
 GLOBAL DESCRIPTION:   File 661.7 'XHDS' INDEX          Used to look up by
 HCPCS & 
                                  DATE&TIME STAMP & SEQUENCE 
GLOBAL REFERENCE: RMPR(661.7,'XSHIDS')
 GLOBAL DESCRIPTION:   File 661.7 'XSHIDS' index        Used to look up by
 STATION & 
                                  HCPCS & HCPCS ITEM & DATE&TIME 
                                  STAMP & SEQUENCE 
GLOBAL REFERENCE: RMPR(661.7,'XSLHIDS')
 GLOBAL DESCRIPTION:   File 661.7 'XSLHIDS' index       Used to look up by
 STATION & 
                                  LOCATION & HCPCS & HCPCS ITEM 
                                  & DATE&TIME STAMP & SEQUENCE 
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) read access to all fields of the
 PROSTHETIC CURRENT STOCK file (#661.7) when creating a Prosthetics Inventory
 Package (PIP) stock issue.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: LPS
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JAN 13, 2020

NUMBER: 7122                            IA #: 7122
  DATE CREATED: DEC 20, 2019            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: XUJFST1                      NAME: XUJFST1
  ID: XUJFST1
 GENERAL DESCRIPTION:   This Integration Control Registration describes
 Controlled Subscription use of Application Program Interfaces to access data
 in Kernel files.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NEW PERSON
KEYWORDS: LOOKUP
KEYWORDS: LIST
COMPONENT/ENTRY POINT: USERLIST
 COMPONENT DESCRIPTION:   This Application Program Interface (API) will receive
 a list of parameters and return a list of entries from the NEW PERSON file
 (#200) and NAME COMPONENTS file (#20) in an array received from the
 subscribing application.  
VARIABLES: LST                          TYPE: Both
 VARIABLES DESCRIPTION:   Input: Array name that contains the list returned
 from the NEW PERSON file.  [REQUIRED] 
  
 Output: Array (name received) populated with data from the list of NEW PERSON 
 entries returned.  Data returned are the following elements: 
    Station#^DUZ^NEW PERSON Name field (#.01) 
    NAME COMPONENTS Degree field (#6) 
    NAME COMPONENTS Famly (Last) Name field (#1) 
    NAME COMPONENTS Given (First) Name field (#2) 
    NAME COMPONENTS Middle Name field (#3) 
    NAME COMPONENTS Prefix field (#4) 
    NAME COMPONENTS Suffix field (#5) 
    NEW PERSON Service/Section field (#29) 
    NEW PERSON Title field (#8) 
  Errant New Person records are written to the 
   Kernel Error trap and not returned in the 
   (LST) results array.  
VARIABLES: XUZUSRNM                     TYPE: Input
 VARIABLES DESCRIPTION:   Name (partial or complete) to search for in the NEW
 PERSON file.  [OPTIONAL - If not defined, search of the NEW PERSON file will
 begin at the first entry] 
VARIABLES: N                            TYPE: Input
 VARIABLES DESCRIPTION:   The maximum number of entries to list in the LST
 array.  [OPTIONAL - Default 50] 
VARIABLES: KEY                          TYPE: Input
 VARIABLES DESCRIPTION:   A Kernel Security Key.  The NEW PERSON file entries
 returned in the list are screened for this Security Key.  [OPTIONAL - When
 undefined, users are not screened on Kernel Security Key] 
VARIABLES: XUZNODUP                     TYPE: Input
 VARIABLES DESCRIPTION:   Duplicate filter indicator as follows: 
   0 - Return all NEW PERSONs including duplicate 
        names & degrees 
   1 - Only return a single NEW PERSON when 
        multiple users have the same name and 
        degree [OPTIONAL - Default 0] 
VARIABLES: XUZENDNM                     TYPE: Input
 VARIABLES DESCRIPTION:   Name not to exceed in the list returned with the LST
 array from the NEW PERSON file.  (E.G. The end name in the list) [OPTIONAL -
 When not defined, NEW PERSON file will be searched until the end or the number
 of entries in N are listed] 
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION

NUMBER: 7123                            IA #: 7123
  DATE CREATED: JAN 08, 2020            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOCLO1
  NAME: PSOCLO1                         ID: PSOCLO1
 GENERAL DESCRIPTION:   This routine performs Clozapine Order checks. It also
 grants permission to dispense a clozapine marked drug to an eligible clozapine
 patient.  
  
  STATUS: Active
KEYWORDS: CLOZAPINE
KEYWORDS: ORDER
KEYWORDS: CHECK
KEYWORDS: DISPENSE
KEYWORDS: AUTHORIZED
COMPONENT/ENTRY POINT: PSOCLO1
 COMPONENT DESCRIPTION:   
  
VARIABLES: XQY0                         TYPE: Input
 VARIABLES DESCRIPTION:   Data from the zero node of the Option File #19.  
  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN from File #2.  
  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: JAN 24, 2020

NUMBER: 7124                            IA #: 7124
  DATE CREATED: FEB 03, 2020
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMRCCERN
  NAME: Call GMRCCERN from RAO7ROXX - Cerner integration at Spokane
  ID: GMRCCERN
 GENERAL DESCRIPTION:   ****** NOTE:  This ICR is temporary and will be
 cancelled when the HL7 adaptor is no longer in use at any site.  ***** 
  
 Until the Cerner Camm7 app is complete, Cerner EHRM will utilize VistA Imaging
 to display clinical images.  To implement this scheme, it is necessary for
 Cerner to transmit HL7 orders to VistA so they can be processed onto modality
 worklists.  These orders will flow through the VistA multi-threaded listener
 and be picked up by routine RAO7ROXX.  That routine will triage the order
 messages and process those that are for Radiology but will send the remainder
 (Cardiology, Dental, Dermatology, Eye Care) to routine GMRCCERN for
 processing.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CERNER EHRM
KEYWORDS: HL7 ADAPTOR
COMPONENT/ENTRY POINT: PROCESS
VARIABLES: GMRCMSG                      TYPE: Input
 VARIABLES DESCRIPTION:   Array containing HL7 order segments.  
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
 SUBSCRIBING DETAILS:   Routine RAO7ROXX will pass incoming HL7 orders to
 routine GMRCCERN for procesing.  
  DATE ACTIVATED: AUG 20, 2020

NUMBER: 7125                            IA #: 7125
  FILE NUMBER: 26.13                    GLOBAL ROOT: DGPF(26.13
  DATE CREATED: FEB 04, 2020            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DSS APPLICATION ACCESS TO PATIENT FLAG ASSIGNMENT
  ID: DGPF(26.13
GLOBAL REFERENCE: DGPF(26.13,D0
FIELD NUMBER: .03                       FIELD NAME: STATUS
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The following applications pre-read the PRF assignments
 for workflow analysis:  
        Comprehensive Care Coordination (C3) 
        Consult Tracking Manager (CTM) 
        Order Tracking Manager (OTM) 
        Patient Case Manager (PCM) 
        Patient Flow Suite (PFS) 
        Suicide Prevention Manager (SCM).  
  
 In order for this process to work efficiently, reading the global directly is
 necessary.  Utilizing the FileMan reads are not a viable option when 
 considering the type and amount of data that these several RPCs are attempting
 to retrieve.  Because of this, direct read access is requested for field: 
  
      STATUS (#.03) of the PRF ASSIGNMENT (#26.13) file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VENDOR - DOCUMENT STORAGE SYS
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   COMPREHENSIVE CARE COORDINATION               ADDED
 7/20/2021, effective with DSSV*1.0*1 DSS Class 3 product Document Only 
  DATE ACTIVATED: JUL 25, 2022

NUMBER: 7126                            IA #: 7126
  FILE NUMBER: 95.3                     GLOBAL ROOT: DD(95.3,0)
  DATE CREATED: FEB 09, 2020            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DD 95.3 modification
  ID: DD(95.3,0)
 GENERAL DESCRIPTION:   Temporary KILL and reset ~DD(95.3,0,"ID",80). Temporary
 KILL and reset ~DD(95.3,0,"SCR"). Temporary reset $P(^LAB(95.3,0),U,3)  to
 95.3I   or  95.3Is This is a work around for the way KIDS looks up a record
 during the Install Process.  The problem is KIDS uses the .01 field and the
 Identifiers to match an existing record and the incoming record has a
 different value for the Identifier.  The solution is to send the DD with no
 Identifiers and to delete the Identifiers during the Pre-Install process and
 to set the Identifiers back during the Post-Install process.  The same is for
 File Filter set into SCR node.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ID
KEYWORDS: 95.3
KEYWORDS: LAB LOINC
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   For LAB LOINC Update.  
  DATE ACTIVATED: FEB 18, 2020

NUMBER: 7127                            IA #: 7127
  FILE NUMBER: 64.061                   GLOBAL ROOT: DD(64.061,0)
  DATE CREATED: FEB 09, 2020            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DD 64.061 modification
  ID: DD(64.061,0)
 GENERAL DESCRIPTION:   Temporary KILL and reset ~DD(64.061,"ID",8). This is a
 work around for the way KIDS looks up a record during the Install Process. The
 problem is KIDS uses the .01 field and the Identifiers to match an existing
 record and the incoming record has a different value for the 
  Identifier. The solution is to send the DD with no Identifiers and to delete
 the Identifiers during the Pre-Install process and to set the Identifiers back
 during the Post-Install process. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 64.061
KEYWORDS: LB LOINC
SUBSCRIBING PACKAGE: LAB SERVICE
 SUBSCRIBING DETAILS:   LAB LOINC Update.  
  DATE ACTIVATED: FEB 18, 2020

NUMBER: 7128                            IA #: 7128
  FILE NUMBER: 95.3                     GLOBAL ROOT: DD(95.3,0)
  DATE CREATED: FEB 09, 2020            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: DD 95.3 modification            ID: DD(95.3,0)
 GENERAL DESCRIPTION:   Temporary KILL and reset ~DD(95.3,0,"SCR") 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: LAB LOINC
KEYWORDS: SCR

NUMBER: 7129                            IA #: 7129
  FILE NUMBER: 18.12                    GLOBAL ROOT: XOB(18.12
  DATE CREATED: FEB 19, 2020            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: WRITE ACCESS TO WEB SERVER FILE
  ID: XOB(18.12
GLOBAL REFERENCE: XOB(18.12,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: .04                       FIELD NAME: SERVER
  LOCATION: 0;4                         ACCESS: Write w/Fileman
FIELD NUMBER: .06                       FIELD NAME: STATUS
  LOCATION: 0;6                         ACCESS: Write w/Fileman
FIELD NUMBER: .07                       FIELD NAME: DEFAULT HTTP TIMEOUT
  LOCATION: 0;7                         ACCESS: Write w/Fileman
FIELD NUMBER: 1.01                      FIELD NAME: LOGIN REQUIRED
  LOCATION: 1;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 3.01                      FIELD NAME: SSL ENABLED
  LOCATION: 3;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 3.02                      FIELD NAME: SSL CONFIGURATION
  LOCATION: 3;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 3.03                      FIELD NAME: SSL PORT
  LOCATION: 3;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 200                       FIELD NAME: USERNAME
  LOCATION: 200;1                       ACCESS: Write w/Fileman
FIELD NUMBER: 300                       FIELD NAME: PASSWORD
  LOCATION: 300;1                       ACCESS: Write w/Fileman
GLOBAL REFERENCE: XOB(18.12,D0,100,D1
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: .06                       FIELD NAME: STATUS
  LOCATION: 0;6                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   The CPRS (ORDER ENTRY/RESULTS REPORTING) team requests
 read/write access to the WEB SERVER (#18.12) file to add a new entry during
 the OR*3*519 post-install process. The post-install routine process will
 create the new server record entry using UPDATE^DIE and will also create a new
 entry to the AUTHORIZED WEB SERVICES (#100) multiple, WEB SERVICE (#.01)
 field.  
  
 NOTE: This processing is done programmatically to avoid having sites manually
 configure HWSC using the Web Server Manager. This will ensure all sites have
 the same configuration installed correctly. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   In the OR*3*519 post-install process a new entry, PDMP
 SERVER, will be added to the Web Server (#18.12) file using FileMan APIs.  
  DATE ACTIVATED: MAR 20, 2020

NUMBER: 7130                            IA #: 7130
  FILE NUMBER: 101.43                   GLOBAL ROOT: ORD(101.43,
  DATE CREATED: FEB 25, 2020
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ORDERABLE ITEM RADIOLOGY SPECIFIC AND SET FIELD XREF
  ID: ORD(101.43,
GLOBAL REFERENCE: ORD(101.43,'S.XRAY',
FIELD NUMBER: 101.439                   FIELD NAME: SET MEMBERSHIP
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ORD(101.43,D0,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: CODE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ORD(101.43,D0,
FIELD NUMBER: .1                        FIELD NAME: INACTIVATED
  LOCATION: .1,1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ORD(101.43,D0,
FIELD NUMBER: 71.1                      FIELD NAME: CONTRAST MEDIA
  LOCATION: RA;1                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 71.2                      FIELD NAME: PROCEDURE TYPE
  LOCATION: RA;2                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 71.3                      FIELD NAME: IMAGING TYPE
  LOCATION: RA;3                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 71.4                      FIELD NAME: COMMON PROCEDURE
  LOCATION: RA;4                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Radiology patch RA*5*165 needs temporary read access to
 the Orderable Item file (#101.43) to resynchronize radiology procedures and
 orderable items.  Patch RA*5*165 will traverse the set field's S.XRAY cross 
 reference and compare key fields with their counterparts in the RAD/NUC MED
 PROCEDURE file (#71). If they do not match, the OI entry will be updated via
 existing Orderable Item update protocols.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RA*5*165
KEYWORDS: ORDERABLE ITEM
KEYWORDS: ORD(101.43
KEYWORDS: CPRS-RA
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   added 4/14/21 effective with PXRM*2.0*71 
  DATE ACTIVATED: APR 10, 2020

NUMBER: 7131                            IA #: 7131
  FILE NUMBER: 668                      GLOBAL ROOT: RMPR
  DATE CREATED: MAR 03, 2020            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: RMPR GMRC IFC EHRM UPDATE
  ID: RMPR
GLOBAL REFERENCE: RMPR(668,D0,0
FIELD NUMBER: .01                       FIELD NAME: SUSPENSE DATE
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 1                         FIELD NAME: VETERAN
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 3                         FIELD NAME: SUSPENSE FORM
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 8                         FIELD NAME: SUSPENDED BY
  LOCATION: 0;4                         ACCESS: Write w/Fileman
FIELD NUMBER: 9                         FIELD NAME: TYPE OF REQUEST
  LOCATION: 0;8                         ACCESS: Write w/Fileman
FIELD NUMBER: 14                        FIELD NAME: STATUS
  LOCATION: 0;10                        ACCESS: Write w/Fileman
FIELD NUMBER: 17                        FIELD NAME: CANCELLED BY
  LOCATION: 0;13                        ACCESS: Write w/Fileman
FIELD NUMBER: 20                        FIELD NAME: CONSULT
  LOCATION: 0;15                        ACCESS: Write w/Fileman
FIELD NUMBER: 22                        FIELD NAME: DATE RX WRITTEN
  LOCATION: 0;16                        ACCESS: Write w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,2,0
FIELD NUMBER: 4                         FIELD NAME: DESCRIPTION OF ITEM/SERVICE
  LOCATION: 2;0                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,2,D1,0
FIELD NUMBER: .01                       FIELD NAME: DESCRIPTION OF ITEM/SERVICE
  LOCATION: 0;1                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,5
FIELD NUMBER: 18                        FIELD NAME: CANCEL DATE
  LOCATION: 5;1                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,8
FIELD NUMBER: 1.5                       FIELD NAME: PROVISIONAL DIAGNOSIS
  LOCATION: 8;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 1.6                       FIELD NAME: ICD
  LOCATION: 8;3                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,IFC1
FIELD NUMBER: 27                        FIELD NAME: ORDERING PROVIDER
  LOCATION: IFC1;3                      ACCESS: Write w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,1,0
FIELD NUMBER: 11                        FIELD NAME: ACTION DATE
  LOCATION: 0;1                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,1,D1,0
FIELD NUMBER: .01                       FIELD NAME: ACTION DATE
  LOCATION: 0;1                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: RMPR(668,D0,1,D1,1,D2,0
FIELD NUMBER: .01                       FIELD NAME: ACTION NOTE
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   Vista Prosthetics is permitting Consults Request
 Tracking (CRT) to update the PROSTHETICS SUSPENSE file (#668) for incoming
 EHRM PROSTHETICS IFC suspense orders.  
  Revision History: 
    4/30/25-Added ACTION DATE multiple and its associated fields to store 
    comments.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RMPR
KEYWORDS: GMRC
KEYWORDS: IFC
KEYWORDS: EHRM
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Vista Consults Request Tracking (CRT) inbound
 Interfacility Consults (IFC) HL7 processor IN^GMRCIMSG now checks incoming HL7
 messages to determine if they are EHRM Prosthetics messages. If they are EHRM 
 Prosthetics IFC messages, routine GMRCRFC0 is invoked; if they are not EHRM
 Prosthetics IFC messages, IN^GMRCIMSG continues to invoke EN^RMPRFC3.  This
 change is introduced with patch GMRC*3*154.  
  
 Update 4/30/25, effective with GMRC*3*207, added ACTION DATE multiple and its
 associated fields to store comments entered in Cerner Millennium.  
  DATE ACTIVATED: MAR 12, 2020

NUMBER: 7132                            IA #: 7132
  DATE CREATED: MAR 03, 2020            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RMPRFC4
  NAME: RMPRFC4                         ID: RMPRFC4
 GENERAL DESCRIPTION:   EHRM Prosthetics implements a new routine, GMRCRFC0, to
 process incoming Prosthetics Interfacility Consults (IFC) suspense requests.
 This routine is invoked by IFC inbound HL7 processor IN^GMRCIMSG.  
  
 For Discontinue (DC) EHRM actions received, new routine GMRCIFC0 process the
 incoming HL7 message into the PROSTHETIC SUSPENSE file (#668).  
  
 For New (NW) EHRM Prosthetics actions received, new routine GMRCIFC0 invokes
 existing New Order processing routine RMPRFC4 to re-use existing code. This
 Integration Control Registration documents the invocation of ^RMPRFC4
 directly, where previously it was only invoked through calls to ^RMPRFC3.  
  STATUS: Active
KEYWORDS: GMRC
KEYWORDS: IFC
KEYWORDS: PROSTHETICS
KEYWORDS: CONSULTS
COMPONENT/ENTRY POINT: EN
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Consults Request Tracking (CRT) has previously invoked
 EN^RMPRFC4 indirectly via a call to EN^RMPRFC3.  
  DATE ACTIVATED: MAR 12, 2020

NUMBER: 7133                            IA #: 7133
  DATE CREATED: MAR 05, 2020
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MPIFRES
  NAME: GETPAT MPIFRES                  ID: MPIFRES
 GENERAL DESCRIPTION:   This Application Programmer Interface (API) allows
 subscribers to retrieve patient demographic data for a specific DFN.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MPIFRES
KEYWORDS: GETPAT
COMPONENT/ENTRY POINT: GETPAT
 COMPONENT DESCRIPTION:   GETPAT^MPIFRES(DFN,PATARR) This function allows
 retrieval of patient demographic data for a specific DFN value.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN - Internal Entry Number (IEN) of patient in the
 Patient (#2) file.  
VARIABLES: PATARR                       TYPE: Both
 VARIABLES DESCRIPTION:   PATARR - The array that will hold the Patient
 Demographic data for the DFN (Pass by Reference).  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Consults Request Tracking (CRT) will start using this
 Application Programmer Interface (API) to retrieve Patient Demographic data
 for a specific DFN value starting in patch GMRC*3.0*154.  
SUBSCRIBING PACKAGE: AUTOMATED LAB INSTRUMENTS
 SUBSCRIBING DETAILS:   Added 3/4/22, effective with patch LA*5.2*100, the Lab
 Auto-Instrument Package will use this Application Programmer Interface (API)
 to retrieve Patient Demographic data for a specific DFN value.  
  DATE ACTIVATED: JUN 02, 2020

NUMBER: 7134                            IA #: 7134
  DATE CREATED: MAR 05, 2020
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MPIFXMLI
  NAME: GETICN MPIFXMLI                 ID: MPIFXMLI
 GENERAL DESCRIPTION:   This Application Programmer Interface (API) allows
 subscribers to perform an explicit VistA-Side creation of patients.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MPIFXMLI
KEYWORDS: GETICN
COMPONENT/ENTRY POINT: GETICN
 COMPONENT DESCRIPTION:   GETICN^MPIFXMLI(MPIDATA,MPIARR) This function
 supports the VistA-Side creation of patients.  
VARIABLES: MPIDATA                      TYPE: Both
 VARIABLES DESCRIPTION:   MPIDATA - Returns the Integration Control Number
 (ICN) value or -1 if the ICN value was not created (MPIDATA("ICN")). Any error
 text will be captured in the MPIDATA("ERRTXT") array entry. (Pass by
 Reference) 
VARIABLES: MPIARR                       TYPE: Input
 VARIABLES DESCRIPTION:   MPIARR - The array that contains the Patient
 Demographic data for the patient to be created (See GETPAT^MPIFRES). (Pass by
 Reference) 
  
 NOTE: After call to GETPAT^MPIFRES to retrieve 
       Patient Demographic data, MPIARR should 
       be updated to include the following array 
       entries: 
  
       MPIARR(1,"preferredFacilityNumber")= 
          <STATION # where patient to be added> 
       MPIARR(1,"AddType")="ADDPREFTF" 
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Consults Request Tracking (CRT) will start using this
 Application Programmer Interface (API) to perform an explicit VistA-Side
 creation of a patient if NOT currently registered at the requested site 
 starting in patch GMRC*3.0*154.  
SUBSCRIBING PACKAGE: AUTOMATED LAB INSTRUMENTS
 SUBSCRIBING DETAILS:   Added 3/4/22, effective with patch LA*5.2*100, the Lab
 Auto-Instrument Package will use this Application Programming Interface (API)
 to invoke a Cerner system creation of a patient if the patient is currently
 not known to Cerner. The "AddType" is set to ""ProxyAddPatientToCerner".  
  DATE ACTIVATED: JUN 02, 2020

NUMBER: 7135                            IA #: 7135
  DATE CREATED: MAR 09, 2020
  CUSTODIAL PACKAGE: VIRTUAL PATIENT RECORD
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VPRD
  NAME: VPR GET PATIENT DATA XML        ID: VPRD
 GENERAL DESCRIPTION:   This ICR provides the ability to pull patient data from
 VistA by directly calling GET^VPRD. Please refer to the VPR Technical Manual
 for details about input parameters and output data elements. These line tags
 retrieve the requested data from VistA and return it in ^TMP("VPR",$J,n) as
 XML.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GET
SUBSCRIBING PACKAGE: VISTA SYSTEM MONITOR
 SUBSCRIBING DETAILS:   The VistA System Monitor(VSM) collects system and
 business data for use in Capacity Management, Performance Analysis and
 Application Performance Monitoring. Specifically, VSM will use this function
 to provide end user response time data. As the contents of the data is not
 needed, all alpha-numeric text will be replaced by "X" such that no patient
 data will be transmitted from VistA.  
  DATE ACTIVATED: MAR 19, 2020

NUMBER: 7136                            IA #: 7136
  DATE CREATED: MAR 09, 2020
  CUSTODIAL PACKAGE: VIRTUAL PATIENT RECORD
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VPRDJ
  NAME: VPR GET PATIENT DATA JSON       ID: VPRDJ
 GENERAL DESCRIPTION:   This ICR provides the ability to pull patient data from
 VistA by directly calling GET^VPRDJ. Please refer to the VPR Technical Manual
 for details about input parameters and output data elements. These line tags
 retrieve the requested data from VistA and return it in ^TMP("VPR",$J,n) as
 JSON.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GET
SUBSCRIBING PACKAGE: VISTA SYSTEM MONITOR
 SUBSCRIBING DETAILS:   The VistA System Monitor(VSM) collects system and
 business data for use in Capacity Management, Performance Analysis and
 Application Performance Monitoring. Specifically, VSM will use this function
 to provide end user response time data. As the contents of the data is not
 needed, all alpha-numeric text will be replaced by "X" such that no patient
 data will be transmitted from VistA.  
  DATE ACTIVATED: MAR 19, 2020

NUMBER: 7137                            IA #: 7137
  DATE CREATED: MAR 09, 2020            CUSTODIAL PACKAGE: DIETETICS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: FHGMVQAL
  NAME: SEND WEIGHT CHANGE NOTIFICATION TO DIETICIAN
  ID: FHGMVQAL
 GENERAL DESCRIPTION:   The purpose of this ICR is to grant the Vitals package
 privileges to call FHGMVQAL to queue an alert (notification) to the Dietician
 assigned to a Nutrition Location.  
  STATUS: Active
KEYWORDS: FHGMVQAL
COMPONENT/ENTRY POINT: ALERT
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: GMVLOC                       TYPE: Input
 VARIABLES DESCRIPTION:   Patient's Current Location 
SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS
 SUBSCRIBING DETAILS:   Based on a set of weight change thresholds, provided by
 the Nutrition and Food Services Subject Matter Experts, Vitals needs the
 ability to send an alert (notification) to a Dietician. Specifically, Vitals
 will notify the clinician(s) associated with a Nutrition Location when a 
 patient's weight change has exceeded the threshold.  
  DATE ACTIVATED: MAR 10, 2020

NUMBER: 7138                            IA #: 7138
  FILE NUMBER: 3.075                    GLOBAL ROOT: %ZTER(1
  DATE CREATED: MAR 10, 2020            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DIRECT READ OF ERROR LOG FILE
  ID: %ZTER(1
GLOBAL REFERENCE: %ZTER(1,D0,1,0
FIELD NUMBER: .01                       FIELD NAME: ERROR NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The "B" x-ref may also be accessed through direct global
 read.  
FIELD NUMBER: .02                       FIELD NAME: NUMBER OF ERRORS RECORDED
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: %ZTER(1,D0,1,D1,GR
FIELD NUMBER: 3                         FIELD NAME: LAST GLOBAL REFERENCE
  LOCATION: GR;E1,245                   ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: %ZTER(1,D0,1,D1,H
FIELD NUMBER: 2                         FIELD NAME: $H VALUE
  LOCATION: H;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: %ZTER(1,D0,1,D1,I
FIELD NUMBER: 5.01                      FIELD NAME: CURRENT $IO
  LOCATION: I;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5.02                      FIELD NAME: $ZA VALUE
  LOCATION: I;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5.03                      FIELD NAME: $ZB VALUE
  LOCATION: I;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5.04                      FIELD NAME: CURRENT $ZIO
  LOCATION: I;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: %ZTER(1,D0,1,D1,J
FIELD NUMBER: 4.01                      FIELD NAME: JOB NUMBER
  LOCATION: J;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4.02                      FIELD NAME: PROCESS NAME
  LOCATION: J;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4.03                      FIELD NAME: USER NAME
  LOCATION: J;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4.04                      FIELD NAME: UCI~VOL~NODE~BOX
  LOCATION: J;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4.05                      FIELD NAME: JOB NUMBER(ALTERNATE)
  LOCATION: J;5                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: %ZTER(1,D0,1,D1,ZE
FIELD NUMBER: 1                         FIELD NAME: ERROR TEXT
  LOCATION: ZE;E1,245                   ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: %ZTER(1,DO,1,D1,ZV,D2
FIELD NUMBER: .01                       FIELD NAME: VARIABLE NAME
  LOCATION: 0;E1,245                    ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: D
FIELD NUMBER: 1                         FIELD NAME: DATA VALUE
  LOCATION: D;E1,245                    ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: %ZTER(1,D0,1,D1,LINE
 GENERAL DESCRIPTION:   This ICR provides the ability to directly read the
 ERROR LOG file and its sub-files.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTA SYSTEM MONITOR
 SUBSCRIBING DETAILS:   The VistA System Monitor collects system and business
 data for use in Capacity Management, Performance Analysis and Application
 Performance Monitoring. Specifically, VSM will use this ICR to provide
 application error data to Application Performance Monitoring and other 
 interested stakeholders. 
SUBSCRIBING PACKAGE: SURGERY RISK ASSESSMENT
 SUBSCRIBING DETAILS:   Added 07/26/21: SURGERY RISK ASSESSMENT, patch
 SRA*3*8,improves communication and functionality of the Surgical Risk
 Assessment (SRA) Database daily summary/cleanup email to include information
 from the error trap.  As OIT support for SRA, becomes less consistent, this
 daily email becomes more important as it checks a variety of aspects of SRA to 
 determine if there are issues requiring attention. The display in the email
 message sent daily includes the count of all errors for the day and a summary
 of the types of errors. SRA is only installed on one system (FOU).  It is not
 installed at VA Medical Centers.  
  DATE ACTIVATED: MAR 19, 2020

NUMBER: 7139                            IA #: 7139
  FILE NUMBER: 3.077                    GLOBAL ROOT: %ZTER(3.077
  DATE CREATED: MAR 10, 2020            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: DIRECT READ OF ERROR TRAP SUMMARY FILE
  ID: %ZTER(3.077
GLOBAL REFERENCE: %ZTER(3.077,D0,0
FIELD NUMBER: .01                       FIELD NAME: ERROR TEXT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: FIRST DATE/TIME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: MOST RECENT DATE/TIME
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: %ZTER(3.077,D0,4,D1,0
FIELD NUMBER: .01                       FIELD NAME: FREQUENCY DISTRIBUTION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This ICR provides the ability to directly read from the
 ERROR TRAP SUMMARY file.  
  STATUS: Active
SUBSCRIBING PACKAGE: VISTA SYSTEM MONITOR
 SUBSCRIBING DETAILS:   The VistA System Monitor(VSM) collects system and
 business data for use in Capacity Management, Performance Analysis and
 Application Performance Monitoring. Specifically, VSM will use this ICR to
 provide application error data to Application Performance Monitoring and other
 interested stakeholders.  
  DATE ACTIVATED: MAR 19, 2020

NUMBER: 7140                            IA #: 7140
  FILE NUMBER: 230                      GLOBAL ROOT: EDP(230
  DATE CREATED: MAR 11, 2020            CUSTODIAL PACKAGE: EMERGENCY DEPARTMENT
  USAGE: Private                        TYPE: File
  NAME: VIA use of EDIS data (#7140/#7141)
  ID: EDP(230
GLOBAL REFERENCE: EDP(230,'ADST'
FIELD NUMBER: 1.3                       FIELD NAME: DISPOSITION TIME
  ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field is used in the regular "ADST" cross reference
 creation.  
GLOBAL REFERENCE: EDP(230,IEN,0 setting NODE0 local variable
FIELD NUMBER: .02                       FIELD NAME: INSTITUTION
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is used to get the site's Station (#99) field
 of the INSTITUTION (4) file.  
FIELD NUMBER: .06                       FIELD NAME: PATIENT ID
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is used to get the patient IEN.  
GLOBAL REFERENCE: EDP(230,IEN,1 setting NODE1 local variable
FIELD NUMBER: 1.1                       FIELD NAME: COMPLAINT
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1.2                       FIELD NAME: DISPOSITION
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is used to get to the TRACKING CODE (233.1)
 file for that entry.  
FIELD NUMBER: 1.3                       FIELD NAME: DISPOSITION TIME
  ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: EDIS
KEYWORDS: VIA
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VISTA INTEGRATION ADAPTOR (VIA) created a "ADST" cross
 reference on the DISPOSITION TIME (#1.3) field of the ED LOG (230) file.  This
 cross reference is used by VIA for Bed Management Systems [GETACTIVITY] RPC.  
 This code was was added in VIAB*1*11.  

NUMBER: 7141                            IA #: 7141
  FILE NUMBER: 233.1                    GLOBAL ROOT: EDPB(233.1
  DATE CREATED: MAR 11, 2020            CUSTODIAL PACKAGE: EMERGENCY DEPARTMENT
  USAGE: Private                        TYPE: File
  NAME: VIA use of EDIS data (#7140/#7141)
  ID: EDPB(233.1
GLOBAL REFERENCE: EDPB(233.1,IEN,0
FIELD NUMBER: .05                       FIELD NAME: FLAGS
  ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Access to this FLAGS field value is by a Fileman read.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: EDIS
KEYWORDS: VIA
SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR
 SUBSCRIBING DETAILS:   VISTA INTEGRATION ADAPTOR (VIA) created a "ADST" cross
 reference on the DISPOSITION TIME (#1.3) field of the ED LOG (230) file.  This
 cross reference is used by VIA for Bed Management Systems [GETACTIVITY] RPC.  
 This code was was added in VIAB*1*11.  
  
 The access to this TRACKING CODE (233.1) file comes from accessing the
 DISPOSITION (#1.2) field pointer of the ED LOG (230). IA#7140.  
  
 Here, VIA looks at the FLAGS field for the entry to equal "VA".  

NUMBER: 7142                            IA #: 7142
  FILE NUMBER: 8925                     GLOBAL ROOT: TIU(8925,
  DATE CREATED: MAR 18, 2020
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU RE-INDEX VISIT FIELD TRIGGER
  ID: TIU(8925,
GLOBAL REFERENCE: TIU(8925,'V',X,D0)
FIELD NUMBER: .03                       FIELD NAME: VISIT
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: TIU(8925,D0,0)
FIELD NUMBER: .03                       FIELD NAME: VISIT
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 15001                     FIELD NAME: VISIT ID
  LOCATION: 150;1                       ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   This ICR provides read access to the "V" cross
 reference in the TIU DOCUMENT (#8925) file and file access to re-index the
 trigger cross reference of the VISIT (#.03) field of the TIU DOCUMENT (#8925)
 file to update the VISIT ID (#15001) field.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Visit Field Trigger
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: APR 08, 2020

NUMBER: 7143                            IA #: 7143
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: MAR 19, 2020            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ADUPN
  ID: VA(200
GLOBAL REFERENCE: VA(200,D0,205
FIELD NUMBER: 205.5                     FIELD NAME: ADUPN
  LOCATION: 205;5                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: VA(200,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The CPRS (ORDER ENTRY/RESULTS REPORTING) team requests
 read access to the ADUPN field in the New Person (#200) file. The ADUPN field
 (which stores the users' va.gov email address) will be used in the query to
 identify the user initiating the query.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ADUPN
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   This will be used by patch OR*3*519 when making a PDMP
 query. The ADUPN field (which stores the users' va.gov email address) will be
 used in the query to identify the user initiating the query.  Added 10/16/25
 effective with patch OR*3.0*508, CPRS is adding the .01 Name field Read
 w/Fileman.  
  DATE ACTIVATED: MAR 20, 2020

NUMBER: 7144                            IA #: 7144
  DATE CREATED: MAR 23, 2020
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORPDMPHS
  NAME: PDMP HEALTH SUMMARY EXTRACT     ID: ORPDMPHS
 GENERAL DESCRIPTION:   The Health Summary Package desires to set up an
 integration agreement with the Order Entry/Results Reporting Package to
 retrieve Prescription Drug Monitoring Program (PDMP) data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN(.RESULT,DFN,.FILTER)
 COMPONENT DESCRIPTION:   The EN^ORPDMPHS function is used to retrieve a list
 of PDMP queries that were made for a given patient. The results can be
 filtered by query status, date range, and whether data was shared outside of
 the VA.  
VARIABLES: RESULT                       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 PDMP
 queries for a patient that matches the FILTER criteria.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the PATIENT file (#2) 
VARIABLES: FILTER                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional array (passed by reference). Can filter
 extract using the values below. The filters for STATUS and SHARED can include
 more than one value.  Example: FILTER("STATUS")="EXN".  
  
 FILTER("STATUS") - Filters results based off the 
                    following query statuses.  
                    (Optional; Defaults to 
                    "EZCXNAM"). Possible Values: 
                        E: Error Query 
                        Z: Error Report 
                        C: Canceled Query 
                        X: Canceled Report 
                        N: Never Reviewed 
                        A: Auto Created Note 
                        M: Manually Created Note FILTER("DATES")  -
 StartDT:EndDT (Optional; 
                    Defaults to all dates) FILTER("SHARED") - 1/0 (Optional;
 Defaults to 
                    "10") 
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: APR 14, 2020

NUMBER: 7145                            IA #: 7145
  GLOBAL ROOT: DD(                      DATE CREATED: APR 01, 2020
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            NAME: DD GLOBAL READ ACCESS
  ID: DD(
 GENERAL DESCRIPTION:   Above PAR requests permission to perform direct reads
 from the FILE Attribute file. Including all the fields as well as the 'GL' &
 'IX' indexes.  
     
 The 'IX' cross reference index is used to return information faster by using
 the cross references when searching for specific data. 
     ^DD(File#, 0, "IX", Reference, File#, Field#) 
     
 The 'GL' index is used to step through data using the global layout.  
     ^DD(File#, "GL", node, piece, Field#) 
  
  
 Global File & Field may be read and traversed by direct means.  
  
 ^DD(File#, Field#,0)  
       .01 LABEL                     0;1     Direct Read & Fileman Read 
       .2  SPECIFIER                 0;2     Direct Read & Fileman Read 
       .3  POINTER                   0;3     Direct Read & Fileman Read 
       .4  GLOBAL SUBSCRIPT LOCATION 0;4     Direct Read & Fileman Read 
           INPUT TRANSFORM           0;5     Direct Read & Fileman Read 
  
 ^DD(File#, Field#,1,SEQ CROSS-REFERENCE ^DD(File#, Field#,1,SEQ,0) 
        File                         0;1     Direct Read & Fileman Read 
        INDEX                        0;2     Direct Read & Fileman Read 
  
 ^DD(File#, Field#,1,SEQ,1,1) 
        SET STATEMENT                        Direct Read & Fileman Read 
 ^DD(File#, Field#,1,SEQ,1,2) 
        KILL STATEMENT                       Direct Read & Fileman Read 
 ^DD(File#, Field#,1,SEQ,1,3) 
        NO DELETE MESSAGE                    Direct Read & Fileman Read 
 ^DD(File#, Field#,1,SEQ,1,"DT") 
        DATE UPDATED                         Direct Read & Fileman Read 
 ^DD(File#, Field#,1,SEQ,1,"%D") 
        DESCRIPTION                          Direct Read & Fileman Read 
  
 ^DD(File#, Field#,3) 
       .01 'HELP'-PROMPT             0;1     Direct Read & Fileman Read 
  
 ^DD(File#, Field#,21) 
       .01 DATE LAST UPDATED         0;1     Direct Read & Fileman Read 
  
 ^DD(File#, Field#,"DT") 
       .01 DATE LAST UPDATED         0;1     Direct Read & Fileman Read 
  
 Global Location may be read and traversed by direct means.  
    ^DD(File#, "GL", Node, Piece, Field#)                 
  
 Global Indexes may be read and traversed by direct means.  
    ^DD(File#, 0, "IX", Reference, File#, Field#) 
  STATUS: Pending
KEYWORDS: APAR
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   
  
 ADDED 7/25/2022, effective with DSSV*1.1 DSS Class 3 product Document Only 

NUMBER: 7146                            IA #: 7146
  DATE CREATED: APR 09, 2020            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMBANNER
  NAME: CPRS BANNER REMINDER API        ID: PXRMBANNER
 GENERAL DESCRIPTION:   This API returns the status of reminder to be use by
 the CPRS banner and the CPRS information panel functionalities.  
  
 Revision History 
  3/26/25: ICR updated with PXRMBANNER routine with the comment below. The new
 routine will be released with patch PXRM*2.0*87 this is part of the CPRS 33con
 bundle of patches.  
  
  4/16/24: CPRS33 deprecates PXRMCOVID19 routine, replacing it with 
  PXRMBANNER. The only difference between the Routines is the possible 
  error message will not contain the word COVID19. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COVID-19 STATUS
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: CPRS
COMPONENT/ENTRY POINT: STATUS
 COMPONENT DESCRIPTION:   $$STATUS^PXRMBANNER(DFN,REMINDER) DFN is the
 patient's DFN.  REMINDER is the reminder definition IEN or .01.  It returns
 NUM^TEXT, where NUM is the number of the true function finding. If the
 reminder definition is missing NUM is -1. If the status cannot be determined
 NUM is 0.  TEXT is the text that is displayed in the banner. When there is a
 true function finding it is the found text for that function finding.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient's DFN 
VARIABLES: REMINDER                     TYPE: Input
 VARIABLES DESCRIPTION:   Reminder definition IEN or .01.  
COMPONENT/ENTRY POINT: CLICKTEXT
 COMPONENT DESCRIPTION:   This entry point returns for formatted text output of
 the reminder evaluation.  
VARIABLES: SUB                          TYPE: Both
 VARIABLES DESCRIPTION:   SUB is the name of the subscript the output of
 CLICKTEXT entry point should be written to.  
VARIABLES: DEFIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN of the reminder definition from file
 811.9.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN 
VARIABLES: TRUEFF                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the reminder evaluation function finding
 result number to get the formatted output text from.  
VARIABLES:  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   The patient's COVID-19 status is displayed on a banner
 in CPRS.  
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   Added 4/19/23, effective with DSSV*1.0*1 DSS Class 2
 product 
  DATE ACTIVATED: MAR 26, 2025

NUMBER: 7147                            IA #: 7147
  DATE CREATED: APR 15, 2020
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORQOR DETAIL                    REMOTE PROCEDURE: ORQOR DETAIL
 GENERAL DESCRIPTION:   VistA Scheduling Enhancement (VSE) has a need to
 provide the detailed information for a patient's consult orders to VS GUI.  VS
 GUI will pass the order IEN and patient DFN as parameters to retrieve the
 order details.  
  
  
 Input:  ORDIEN ; order identifier 
         DFN    ; patient identifier 
  STATUS: Withdrawn
KEYWORDS: ORWOR
KEYWORDS: VSE
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 7148                            IA #: 7148
  DATE CREATED: APR 23, 2020            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  ROUTINE: ENWOINV                      NAME: IFCAP API: WORK ORDER XREF UPDATE
  ID: ENWOINV
 GENERAL DESCRIPTION:   This integration agreement allows the call to
 ST^ENWOINV associated with Generate PMI Worklists which creates or finds work
 orders for a specified PM worklist and then makes calls to print that
 document. 
  
 ST component will update the Work Order.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
KEYWORDS: APAR
COMPONENT/ENTRY POINT: ST
 COMPONENT DESCRIPTION:   ST component will update the Work Order and cross
 references after a change in Equipment Category, Manufacturer or Location.  
VARIABLES: DA                           TYPE: Used
 VARIABLES DESCRIPTION:   Work Order IEN 
VARIABLES: NO RETURN                    TYPE: Output
 VARIABLES DESCRIPTION:   No return value from this API.  
  
 This module updates the Work Order C, E, F cross references and Fields 
 EQUIPMENT CATEGORY (#21),  MANUFACTURER (#21.9), and LOCATION (#3).  
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 7149                            IA #: 7149
  DATE CREATED: APR 23, 2020            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  ROUTINE: ENEQPMS2                     NAME: IFCAP API: PMWO WORK ORDER LIST
  ID: ENEQPMS2
 GENERAL DESCRIPTION:   This integration agreement allows the call to
 LST2^ENEQPMS2 to identify Work Orders associated with specified PM Work Order. 
 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
KEYWORDS: APAR
COMPONENT/ENTRY POINT: LST2
 COMPONENT DESCRIPTION:   LST2 returns Work Orders associated with specified PM
 Work Order.  
VARIABLES: ENSHKEY                      TYPE: Used
 VARIABLES DESCRIPTION:   Station Key 
VARIABLES: DA                           TYPE: Used
 VARIABLES DESCRIPTION:   Equipment IEN (6914) 
VARIABLES: SE                           TYPE: Used
 VARIABLES DESCRIPTION:   Responsible Shop IEN (6914.04) 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,'ENWL',ENSHKEY,SUB_DA) global contains Work
 Orders associated with the specified PM Work Order.  
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 7150                            IA #: 7150
  DATE CREATED: APR 23, 2020            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  ROUTINE: ENWOCOMP
  NAME: IFCAP API: PMWO WORK ORDER COMPLETED
  ID: ENWOCOMP
 GENERAL DESCRIPTION:   This integration agreement allows the call to
 TEST^ENWOCOMP to check if the Work Orders can be marked completed.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
KEYWORDS: APAR
COMPONENT/ENTRY POINT: TEST
 COMPONENT DESCRIPTION:   TEST checks if the Work Orders can be marked
 completed.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Equipment IEN (6914) 
VARIABLES: NO RETURN                    TYPE: Output
 VARIABLES DESCRIPTION:   No return value from this API.  
  
 If the Work Order meets the Complete criteria, then the Work Order will update
 and the WO will be removed from the active index 'AINC'.  
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 7151                            IA #: 7151
  DATE CREATED: APR 23, 2020            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  ROUTINE: ENFAEIL                      NAME: IFCAP API: FRCMR GENERATE FR DOC
  ID: ENFAEIL
 GENERAL DESCRIPTION:   This integration agreement allows the call to
 $$$$FRCMR^ENFAEIL, used to generate FR Documents without user interaction.
 It's called when a batch of FR Documents are being sent due to a change of CMR
 name or EIL cost center.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
KEYWORDS: APAR
COMPONENT/ENTRY POINT: $$FRCMR
VARIABLES: ENCMRI                       TYPE: Input
 VARIABLES DESCRIPTION:   CMR IEN (6914.1) 
VARIABLES: CNT                          TYPE: Output
 VARIABLES DESCRIPTION:   Number of FR documents sent 
VARIABLES: TMP                          TYPE: Output
 VARIABLES DESCRIPTION:   Optional return value if validation issues are
 encountered then returns  ^TMP($J,'BAD',EEIN,LINE#) = VALIDATION ISSUE 
SUBSCRIBING PACKAGE: ABOVE PAR

NUMBER: 7152                            IA #: 7152
  DATE CREATED: APR 27, 2020            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED
  NAME: DELETE CERNER FIELD FROM THE INSTITUTION FILE
 GENERAL DESCRIPTION:   CERNER field in the INSTITUTION file is no longer used
 and it needs to be removed from the file. This integration agreement is to
 allow use of a supported Fileman API to delete the field .  This API will be
 used in the post-install routine XU8P729.  
  
    FileMan API being used: 
    Deleting Fields ^DIK: Delete Data Dictionary Reference Type: Supported 
    Category: Classic VA FileMan ICR#: 10014 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CERNER
KEYWORDS: INSTITUTION
SUBSCRIBING PACKAGE: KERNEL
 SUBSCRIBING DETAILS:   One time use only for Kernel patch XU*8*729 to remove
 the CERNER field from the INSTITUTION file.  
  DATE ACTIVATED: MAY 04, 2020

NUMBER: 7153                            IA #: 7153
  DATE CREATED: APR 27, 2020
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RAO7ROXV
  NAME: HL7 adaptor error messaging (RAO7ROXV)
  ID: RAO7ROXV
 GENERAL DESCRIPTION:   ****** NOTE:  This ICR is temporary and will be
 cancelled when the HL7 adaptor is no longer in use at any site.  ***** 
  
  
 HL7 adaptor stores error messages about HL7 messages from Cerner in file 
 #79.99 via calls to RAO7ROXV.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CERNER EHRM
KEYWORDS: HL7 ADAPTOR
COMPONENT/ENTRY POINT: ADD2LOG
 COMPONENT DESCRIPTION:   Function to add a log entry in file #79.99.  Returns
 the IEN of file #79.99 if call is successful, 0^error message if not.  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Indicates the severity of the log entry.  ERROR means
 the record could not be processed. WARNING means the record was processed but
 should be reviewed.  DATA DEFAULTED means that a default value was substituted 
 before processing the record.  The sending system should be informed.  
VARIABLES: APPLCATN                     TYPE: Input
 VARIABLES DESCRIPTION:   This field identifies the application that generated
 the log entry.  
VARIABLES: MESSAGE                      TYPE: Input
 VARIABLES DESCRIPTION:   This is a description of the reason for the log
 entry.  It may, for example, refer to an HL7 segment or field.  
VARIABLES: SEVERITY                     TYPE: Input
 VARIABLES DESCRIPTION:   Enter HIGH if the failure requires immediate
 attention, MEDIUM if the failure is important but not critical, LOW if the log
 entry can be researched over time and EH if the log entry is informational
 only.  
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   Use this field to store a description or the source
 for the log entry.  For example, if the log entry resulted from processing of
 an HL7 message, post the message segments here.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   HL7 adaptor code for consults calls RAO7ROXV to record
 HL7 message errors.  
  DATE ACTIVATED: AUG 20, 2020

NUMBER: 7154                            IA #: 7154
  DATE CREATED: APR 28, 2020
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7154
  STATUS: Pending

NUMBER: 7155                            IA #: 7155
  DATE CREATED: APR 29, 2020            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PXRMDESCAPI
  NAME: PXRMDESCAPI returns reminder item descriptions
  ID: PXRMDESCAPI                       STATUS: Pending
  DURATION: Till Otherwise Agreed
KEYWORDS: PXRMDESCAPI
KEYWORDS: 811.9
KEYWORDS: 811.2
KEYWORDS: 811.4
KEYWORDS: 811.5
KEYWORDS: 801
KEYWORDS: 801.1
KEYWORDS: 810.4
COMPONENT/ENTRY POINT: DEF
VARIABLES: SUB                          TYPE: Both
VARIABLES: ITEM                         TYPE: Input
VARIABLES: FIELD                        TYPE: Input
COMPONENT/ENTRY POINT: CF
VARIABLES: SUB                          TYPE: Both
VARIABLES: ITEM                         TYPE: Input
COMPONENT/ENTRY POINT: FFIND
VARIABLES: SUB                          TYPE: Both
VARIABLES: ITEM                         TYPE: Input
VARIABLES: FUNCTNUM                     TYPE: Input
COMPONENT/ENTRY POINT: LIST
VARIABLES: SUB                          TYPE: Both
VARIABLES: ITEM                         TYPE: Input
COMPONENT/ENTRY POINT: OCG
VARIABLES: SUB                          TYPE: Both
VARIABLES: ITEM                         TYPE: Input
COMPONENT/ENTRY POINT: OCR
VARIABLES: SUB                          TYPE: Both
VARIABLES: ITEM                         TYPE: Input
COMPONENT/ENTRY POINT: TAX
VARIABLES: SUB                          TYPE: Both
VARIABLES: ITEM                         TYPE: Input
COMPONENT/ENTRY POINT: TERM
VARIABLES: SUB                          TYPE: Both
VARIABLES: ITEM                         TYPE: Input
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 7156                            IA #: 7156
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100,
  DATE CREATED: APR 29, 2020
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: FileMan access to file #100, field #5 (STATUS)
  ID: OR(100,
GLOBAL REFERENCE: OR(100,D0
FIELD NUMBER: 5                         FIELD NAME: STATUS
  LOCATION: 0;3                         ACCESS: Read w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Need FileMan access to the field #5 (STATUS) to
 determine if an RTC needs to be closed because an appointment has been made or
 the request has been dispositioned using VS GUI.  
  DATE ACTIVATED: MAY 04, 2020

NUMBER: 7157                            IA #: 7157
  DATE CREATED: APR 29, 2020
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORMSD                        NAME: Use of routine ORMSD to close RTCs
  ID: ORMSD                             STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SAVEREC
VARIABLES: RESULT                       TYPE: Input
 VARIABLES DESCRIPTION:   Array containing disposition information used to
 close an RTC.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   A clean up routine is being developed to close RTCs in
 file #100 when the corresponding appointment request in file #409.85 shows
 that they have been scheduled or otherwise dispositioned.  A call to SAVEREC
 in ORMSD will close the RTC in file #100.  

NUMBER: 7158                            IA #: 7158
  FILE NUMBER: 410.2                    GLOBAL ROOT: PRCS(410.2
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  NAME: ERT - CONTROL POINT ACTIVITY    ID: PRCS(410.2
GLOBAL REFERENCE: PRCS(410.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Enterprise Reporting Tool (ERT) requests read access to
 Control Point Activity (#410.2) field NAME (#.01).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7159                            IA #: 7159
  FILE NUMBER: 423                      GLOBAL ROOT: PRCF(423,
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  NAME: ERT - CALM/LOG CODE SHEET       ID: PRCF(423,
GLOBAL REFERENCE: PRCF(423,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ID#
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the code sheet identifier or Calm reference
 number.  
 GENERAL DESCRIPTION:   Enterprise Reporting Tool (ERT) requests read access to
 Calm/Log Code Sheet (#423) field ID# (#.01).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7160                            IA #: 7160
  FILE NUMBER: 6912                     GLOBAL ROOT: ENG('MFG'
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  NAME: ERT - MANUFACTURER LIST FILE    ID: ENG('MFG'
GLOBAL REFERENCE: ENG('MFG',D0,0)
FIELD NUMBER: .01                       FIELD NAME: MFG/DIV
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The original manufacturer of equipment to be accounted
 for by the facility.  
 GENERAL DESCRIPTION:   Enterprise Reporting Tool (ERT) requests read access to
 Manufacturer List File (#6912) field MFG/DIV (#.01).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7161                            IA #: 7161
  FILE NUMBER: 6920                     GLOBAL ROOT: ENG(6920
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Controlled Subscription        TYPE: File
  NAME: ERT - WORK ORDER                ID: ENG(6920
GLOBAL REFERENCE: ENG(6920,D0,0)
FIELD NUMBER: .01                       FIELD NAME: WORK ORDER #
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Identifier of each individual work action.  
 GENERAL DESCRIPTION:   Enterprise Reporting Tool (ERT) requests read access to
 Work Order # File (#6929) field WORK ORDER # (#.01).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7162                            IA #: 7162
  FILE NUMBER: 6911                     GLOBAL ROOT: ENG(6911
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  NAME: ERT - EQUIPMENT CATEGORY        ID: ENG(6911
GLOBAL REFERENCE: ENG(6911,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   A category of devices that receive the same frequencies
 and types of preventive maintenance inspections.  
 GENERAL DESCRIPTION:   Enterprise Reporting Tool (ERT) requests read access to
 EQUIPMENT CATEGORY (#6911) field NAME (#.01).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7163                            IA #: 7163
  FILE NUMBER: 6914.1                   GLOBAL ROOT: ENG(6914.1
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  NAME: ERT - CMR                       ID: ENG(6914.1
GLOBAL REFERENCE: ENG(6914.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Name of CMR.  
 GENERAL DESCRIPTION:   Enterprise Reporting Tool (ERT) requests read access to
 CMR (#6914.1) field NAME (#.01).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7164                            IA #: 7164
  FILE NUMBER: 6914.3                   GLOBAL ROOT: ENG(6914.3
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  NAME: ERT - NX SGL                    ID: ENG(6914.3
GLOBAL REFERENCE: ENG(6914.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ACCOUNT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Standard general ledger account number.  
 GENERAL DESCRIPTION:   Enterprise Reporting Tool (ERT) requests read access to
 NX SGL (#6914.3) field ACCOUNT (#.01).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7165                            IA #: 7165
  FILE NUMBER: 6914.4                   GLOBAL ROOT: ENG(6914.4
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  NAME: ERT - NX BOC                    ID: ENG(6914.4
GLOBAL REFERENCE: ENG(6914.4,D0,0)
FIELD NUMBER: .01
  FIELD NAME: CAPITALIZED BUDGET OBJECT CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   NX BOC coded to Budget Object Code Class 31 
 GENERAL DESCRIPTION:   Enterprise Reporting Tool (ERT) requests read access to
 NX BOC (#6914.4) field CAPITALIZED BUDGET OBJECT CODE (#.01).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7166                            IA #: 7166
  FILE NUMBER: 6914.6                   GLOBAL ROOT: ENG(6914.6
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  NAME: ERT - NX FUND                   ID: ENG(6914.6
GLOBAL REFERENCE: ENG(6914.6,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NX FUND CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Fund code.  
 GENERAL DESCRIPTION:   Enterprise Reporting Tool (ERT) requests read access to
 NX FUND (#6914.6) field NX FUND CODE (#.01).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7167                            IA #: 7167
  FILE NUMBER: 6917                     GLOBAL ROOT: ENCSN(6917
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  NAME: ERT - CATEGORY STOCK NUMBER     ID: ENCSN(6917
GLOBAL REFERENCE: ENCSN(6917,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Ten digit number assigned under the direction of the
 Acquisition and Materiel Management. 
 GENERAL DESCRIPTION:   Enterprise Reporting Tool (ERT) requests read access to
 CATEGORY STOCK NUMBER (#6917) field NAME (#.01).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7168                            IA #: 7168
  FILE NUMBER: 6018.1                   GLOBAL ROOT: ENG(6918.1
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  NAME: ERT - UTILITY SYSTEMS           ID: ENG(6918.1
GLOBAL REFERENCE: ENG(6918.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Abbreviated designation of utility systems commonly
 recongized in Facility Management operations.  
 GENERAL DESCRIPTION:   
  Enterprise Reporting Tool (ERT) requests read access to UTILITY SYSTEMS 
 (#6918.1) field NAME (#.01).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7169                            IA #: 7169
  FILE NUMBER: 6922                     GLOBAL ROOT: DIC(6922
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  NAME: ERT - ENGINEERING SECTION LIST  ID: DIC(6922
GLOBAL REFERENCE: DIC(6922,D0,0)
FIELD NUMBER: .01                       FIELD NAME: ENGINEERING SECTION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Engineering Shop or Receiving Area for electronic work
 orders.  
 GENERAL DESCRIPTION:   
    Enterprise Reporting Tool (ERT) requests read access to ENGINEERING SECTION
 LIST (#6922) field ENGINEERING SECTION (#.01).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7170                            IA #: 7170
  FILE NUMBER: 6928                     GLOBAL ROOT: ENG('SP'
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  NAME: ERT - ENG SPACE                 ID: ENG('SP'
GLOBAL REFERENCE: ENG('SP',D0,0)
FIELD NUMBER: .01                       FIELD NAME: ROOM NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Identifier of a physical location (room).  
 GENERAL DESCRIPTION:   Enterprise Reporting Tool (ERT) requests read access to
 ENG SPACE (#6928) field ROOM NUMBER (#.01). 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT

NUMBER: 7171                            IA #: 7171
  FILE NUMBER: 6929                     GLOBAL ROOT: ENG('EMP'
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: File
  NAME: ERT - ENG EMPLOYEE              ID: ENG('EMP'
GLOBAL REFERENCE: ENG('EMP',D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Name of Engineering Service employee.  
 GENERAL DESCRIPTION:   Enterprise Reporting Tool (ERT) requests read access to
 ENG EMPLOYEE (#6929) field NAME (#.01).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7172                            IA #: 7172
  FILE NUMBER: 442.3                    GLOBAL ROOT: PRCD(442.3
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  NAME: ERT - PURCHASE ORDER STATUS     ID: PRCD(442.3
GLOBAL REFERENCE: PRCD(442.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: SUPPLY STATUS ORDER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: FISCAL STATUS ORDER
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Enterprise Reporting Tool (ERT) requests read access to
 PURCHASE ORDER STATUS (#442.3) fields NAME (#.01), SUPPLY STATUS ORDER (#.02),
 and FISCAL STATUS ORDER (#.03).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7173                            IA #: 7173
  FILE NUMBER: 0                        GLOBAL ROOT: DD(0
  DATE CREATED: MAY 08, 2020            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: ERT - DD READ ACCESS            ID: DD(0
 GENERAL DESCRIPTION:   Enterprise Reporting Tool (ERT) requests read access to
 Data Dictionary file attributes.  
    
 Global File & Field may be read and traversed by direct means.  
     
    ^DD(File#, Field#,0)  
          .01 LABEL                     0;1     Direct Read & Fileman Read 
          .2  SPECIFIER                 0;2     Direct Read & Fileman Read 
          .3  POINTER                   0;3     Direct Read & Fileman Read 
          .4  GLOBAL SUBSCRIPT LOCATION 0;4     Direct Read & Fileman Read 
              INPUT TRANSFORM           0;5     Direct Read & Fileman Read 
  
    ^DD(PFile#,.01) 
                Pfile pointer FILE# from .3 POINTER  
          .01 LABEL                     0;1     Direct Read & Fileman Read 
          .2  SPECIFIER                 0;2     Direct Read & Fileman Read 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ERT
SUBSCRIBING PACKAGE: ENTERPRISE REPORTING TOOL

NUMBER: 7174                            IA #: 7174
  FILE NUMBER: 404.52                   GLOBAL ROOT: SCTM(404.52
  DATE CREATED: MAY 11, 2020            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TEAM POSITION PROVIDER CHANGES
  ID: SCTM(404.52
GLOBAL REFERENCE: SCTM(404.52,'ADP',EFFDT,POS,DA)
 GLOBAL DESCRIPTION:   Use of the ADP index to find position changes for a date
 range.  
 GENERAL DESCRIPTION:   Patch VPR*1*28 will use CREIXN^DDMOD to add a new
 regular 'ADP' index to the POSITION ASSIGNMENT HISTORY (#404.52) file, to sort
 assignments by Effective Date and Team Position. This cross reference will be
 used by VPR to track PCMM team position provider changes to keep VPR and PCMM 
 synchronized.  
        
 This agreement permits the VPR application to create the new index and use it
 in a nightly job to find position assignments that have changed that day.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: DEC 09, 2021

NUMBER: 7175                            IA #: 7175
  DATE CREATED: MAY 13, 2020            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOCLADD
  NAME: YSCL UPDATE PHARMACY PATIENT CLOZAPINE
  ID: PSOCLADD
 GENERAL DESCRIPTION:   Mental Health (YS) Clozapine software invokes
 Outpatient Pharmacy (PSO) API to update the CLOZAPINE REGISTRATION NUMBER
 field (#53) and the CLOZAPINE STATUS field (#54) in the PHARMACY PATIENT file
 (#55) when a new entry is filed in the CLOZAPINE PATIENT LIST file (#603.01)
 via a database trigger x-ref.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: YSCL
KEYWORDS: PSOCL
KEYWORDS: CLOZAPINE
KEYWORDS: NCCC
KEYWORDS: MENTAL HEALTH
KEYWORDS: OUTPATIENT PHARMACY
COMPONENT/ENTRY POINT: TRGR
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient Internal Identifier at the local VAMC.  
VARIABLES: PSOCLOZN                     TYPE: Input
 VARIABLES DESCRIPTION:   The National Clozapine Number sent from the National
 Clozapine Coordinating Center (NCCC) that uniquely identifies each patient's 
 Clozapine registration at each VAMC.  
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Mental Health (YS) invokes Outpatient Pharmacy API
 TRGR^PSOCLADD via mumps trigger x-ref on the CLOZAPINE REGISTRATION NUMBER
 field (#.01) and CLOZAPINE PATIENT field (#1) of the CLOZAPINE PATIENT LIST
 file (#603.01).  
  DATE ACTIVATED: JUN 16, 2020

NUMBER: 7176                            IA #: 7176
  DATE CREATED: MAY 26, 2020            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSJCLOZ
  NAME: PSJCLOZ CLOZAPINE UTILITIES     ID: PSJCLOZ
 GENERAL DESCRIPTION:   API $$ISCLOZ^PSJCLOZ is used to determine if a pharmacy
 order is considered a clozapine order. Clozapine orders require special
 processing as determined by the National Clozapine Coordinating Center (NCCC). 
 
  STATUS: Active
KEYWORDS: CLOZAPINE
KEYWORDS: PHARMACY
COMPONENT/ENTRY POINT: ISCLOZ
 COMPONENT DESCRIPTION:   ISCLOZ is an extrinsic function that returns a zero
 when the input variables are not associated with a clozapine pharmacy order.  
  
 If the input variables are associated with a clozapine pharmacy order, the
 function returns the number 1 and the drug identifier from the DRUG file
 (#50), delimited by a caret, for example, "1^12345". 
VARIABLES: PSGORD                       TYPE: Input
 VARIABLES DESCRIPTION:   PSGORD is the pending order number from the
 NON-VERIFIED ORDERS file (#53.1).  
VARIABLES: ORPSOI                       TYPE: Input
 VARIABLES DESCRIPTION:   ORPSOI is the internal identifier from the local
 Pharmacy Orderable Item file (#50.7).  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN is the internal identifier from the PATIENT file
 (#2) for the patient associated with the pharmacy order.  
VARIABLES: PSGORDNM                     TYPE: Input
 VARIABLES DESCRIPTION:   PSGORDNM is the internal identifier of the pharmacy
 order from the UNIT DOSE sub-file (#55.06) of the Pharmacy Patient file (#55). 
 
VARIABLES: PSGDRG                       TYPE: Input
 VARIABLES DESCRIPTION:   PSGDRG is the internal identifier of the drug of the
 pharmacy order from the DRUG file (#50).  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: JUN 16, 2020

NUMBER: 7177                            IA #: 7177
  FILE NUMBER: 8933.1                   GLOBAL ROOT: XTV(8933.1,
  DATE CREATED: JUN 01, 2020            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PENDING NEW PERSON FIELD UPDATES
  ID: XTV(8933.1,
GLOBAL REFERENCE: XTV(8933.1,
FIELD NUMBER: .02                       FIELD NAME: USER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   USER identifies a specific individual in the NEW PERSON
 (#200) file that has had one or more fields modified on this date.  
GLOBAL REFERENCE: XTV(8933.1,'ACXMIT',
GLOBAL REFERENCE: XTV(8933.1,'B',
 GENERAL DESCRIPTION:   The CLINICAL INFO RESOURCE NETWORK (CIRN) package has a
 monitoring process in routine RGMTMONT that examines/displays the number of 
 messages received, messages processed, messages needing transmission, messages
 transmitted and the current state of the CIRN links, as well as showing the
 number of incoming and outgoing filers running. CIRN will augment this monitor
 processing to also include information on the pending NEW PERSON (#200) field
 updates by looping through and counting the number of pending entries stored
 in the "ACXMIT" X-REF in the NEW PERSON FIELD MONITOR (#8933.1) file that need
 to be transmitted at the time the monitoring process is executed.  
  
      NOTE: "ACXMIT" X-REF entries in file #8933.1 are deleted upon 
            successful transmission of the NEW PERSON (#200) field 
            updates to the Person Service Identity Management (PSIM) 
            system.  
  
 As another aspect of the 'Monitoring' process, CIRN has incorporated a process
 to count the number of outdated and no longer needed NEW PERSON FIELD MONITOR
 (#8933.1) records that will be purged from the file. This process requires
 access to the "B" X-REF on the NEW PERSON FIELD MONITOR (#8933.1) file and the
 USER (#.02) field, which allows CIRN to ensure there are no pending
 transmissions ("ACXMIT" X-REF check) for that User prior to including in the
 'Purge' count.  
  
 Therefore CIRN requests 'Direct Global Read & w/Fileman' for the entire NEW
 PERSON FIELD MONITOR (#8933.1) file to aid in this monitoring process.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XTV(8933.1
KEYWORDS: NEW PERSON FIELD MONITOR
KEYWORDS: XUS IAM NPFM BATCH UPDATE
KEYWORDS: XUS IAM NPFM PURGE
KEYWORDS: XTV(8933.1,'ACXMIT',
KEYWORDS: 8933.1
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
 SUBSCRIBING DETAILS:   The "ACXMIT" X-REF in the NEW PERSON FIELD MONITOR
 (#8933.1) file contains a list of the NEW PERSON (#200) file records that have 
 pending field updates that need to be transmitted to the Person Service
 Identity Management (PSIM) system as part of the Enterprise User Identity
 functionality. CLINICAL INFO RESOURCE NETWORK (CIRN) needs to be able to count
 these pending record updates to display in our current monitoring process.  In
 addition, as another part of this monitoring process CIRN is 
 determining/counting the number of transmitted records in the NEW PERSON FIELD
 MONITOR (#8933.1) file that should be purged if exceeding the allowable
 timeframe.  
  DATE ACTIVATED: JUN 17, 2020

NUMBER: 7178                            IA #: 7178
  DATE CREATED: JUN 03, 2020
  CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: DVBAB REPORTS
  REMOTE PROCEDURE: DVBAB REPORTS       STATUS: Active
  DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: JOINT LEGACY VIEWER
  DATE ACTIVATED: JUN 03, 2020

NUMBER: 7179                            IA #: 7179
  DATE CREATED: JUN 10, 2020
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUCRDD
  NAME: Create TIU Document Definitions
  ID: TIUCRDD
 GENERAL DESCRIPTION:   This API may be used by non-TIU packages to add entries
 to the TIU DOCUMENT DEFINITIONS File # 8925.1.  
  
 Entries allowed are CLASSES, DOCUMENT CLASSES, and TITLES.  This API does not
 support the creation of OBJECTS or COMPONENTS.  
  
 This API is an EXTRINSIC function and returns the IEN of the new entry or 
 0^<description of error>.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 8925.1
KEYWORDS: DOCUMENT DEFINITIONS
COMPONENT/ENTRY POINT: CRDD(NAME,TYPE,STATUS,PARENT,STDTTL)
VARIABLES: NAME                         TYPE: Input
 VARIABLES DESCRIPTION:   Unique NAME (Field #.01) of the entry.  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   TYPE (Field # .04) of the Document Definition.  
  
 Supports:  "CL"  or "CLASS" 
            "DC"  or "DOCUMENT CLASS" 
            "DOC" or "TITLE" 
VARIABLES: STATUS                       TYPE: Input
 VARIABLES DESCRIPTION:   STATUS (Field # .07) 
  
 Supports:   "ACTIVE"   or 11 
             "INACTIVE" or 13 
VARIABLES: PARENT                       TYPE: Input
 VARIABLES DESCRIPTION:   PARENT Document Type (Pointer to File # 8925.1).  
  
 Supports:  IEN of the desired PARENT Document Type  (File # 8925.1)    
            NAME of the desired PARENT Document Type (File # 8925.1) 
VARIABLES: STDTTL                       TYPE: Input
 VARIABLES DESCRIPTION:   VHA ENTERPRISE STANDARD TITLE (Pointer to File #
 8926.1).  
  
 REQUIRED only for new Document Titles.  New titles will be created INACTIVE
 and must be activated manually if omitted.  
  
 Supports: IEN of the desired VHA ENTERPRISE STANDARD TITLE  (File #8926.1) 
           NAME of the desired VHA ENTERPRISE STANDARD TITLE (File #8926.1) 
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 1/31/22, effective with Patch YS*5.01*187, Mental
 Health  will add a new document class, GEC PROGRESS NOTES, with the following
 two titles: PERSONAL CARE SERVICES CASE MIX TOOL PERSONAL CARE SERVICES CASE
 MIX TOOL FOR CONSULT 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 2/26/24, effective with Patch PSO*7*746, the
 Outpatient Pharmacy inbound electronic prescriptions (eRX) project will
 support a new title to be used for documenting the communication from the VA
 Outpatient Pharmacies with the community care providers whenever they have a 
 question about an inbound eRX. Document class: PHARMACY SERVICE (Existing) New
 Document Title: ERX RX CHANGE REQUEST NOTE.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Added 4/15/24, effective with PXRM*2*81, as part of the
 post-setup option, to support Cervical Cancer Screening.  
  DATE ACTIVATED: JUN 11, 2020

NUMBER: 7180                            IA #: 7180
  FILE NUMBER: 230                      GLOBAL ROOT: EDP(230,
  DATE CREATED: JUN 15, 2020            CUSTODIAL PACKAGE: EMERGENCY DEPARTMENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: VPR use of EDP LOG
  ID: EDP(230,
GLOBAL REFERENCE: EDP(230,D0,0)
FIELD NUMBER: .01                       FIELD NAME: LOG ENTRY TIME
  LOCATION: O;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: INSTITUTION
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: PATIENT ID
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: CLOSED
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: TIME IN
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: TIME OUT
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .1                        FIELD NAME: ARRIVAL MODE
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .12                       FIELD NAME: VISIT
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Includes use of the regular 'V' index to find a record by
 Visit# 
FIELD NUMBER: .14                       FIELD NAME: CLINIC
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: PATIENT NAME
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: EDP(230,D0,1)
FIELD NUMBER: 1.1                       FIELD NAME: COMPLAINT
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1.2                       FIELD NAME: DISPOSITION
  LOCATION: 1;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1.3                       FIELD NAME: DISPOSITION TIME
  LOCATION: 1;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1.4                       FIELD NAME: DIAGNOSIS TIME
  LOCATION: 1;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: EDP(230,D0,3)
FIELD NUMBER: 3.5                       FIELD NAME: MD ASSIGNED
  LOCATION: 3;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3.6                       FIELD NAME: NURSE ASSIGNED
  LOCATION: 3;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3.7                       FIELD NAME: RESIDENT ASSIGNED
  LOCATION: 3;7                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: EDP(230,ATI)
GLOBAL REFERENCE: EDP(230,D0,4)
FIELD NUMBER: .01                       FIELD NAME: DISCHARGE DIAGNOSIS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ICD CODE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: PRIMARY
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This IA documents the use of the EDP LOG file by the
 Virtual Patient Record (VPR) application. VPR extracts patient data from VistA
 for sharing with external care partners via InterSystems' HealthShare
 platform.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   Added 12/21/2022, effective with DSSV*1.1 DSS Class 3 
 Product Document Only 
  DATE ACTIVATED: JUL 17, 2020

NUMBER: 7181                            IA #: 7181
  FILE NUMBER: 230                      GLOBAL ROOT: EDP(230,
  DATE CREATED: JUN 16, 2020            CUSTODIAL PACKAGE: EMERGENCY DEPARTMENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: AVPR index on EDP LOG
  ID: EDP(230,
GLOBAL REFERENCE: EDP(230,D0,0)
FIELD NUMBER: .07                       FIELD NAME: CLOSED
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.2                       FIELD NAME: DISPOSITION
  LOCATION: 1;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Virtual Patient Record (VPR) would like to create
 an action index on the EDP LOG (#230) file that would call a VPR API in
 routine VPRENC when a record in the file is closed. The FileMan utility
 CREIXN^DDMOD would be used in a post-init for patch VPR*1*20 to create the
 AVPR index instead of exporting the data dictionary.  
  
 The fields listed here are included in the index for purposes of triggering
 the action. No actual cross reference nodes are created.  
  
 Amended 5/31/22, by adding DISPOSTION Field 1.2 effective with VPR*1*29.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AVPR
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: JUL 17, 2020

NUMBER: 7182                            IA #: 7182
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(D0
  DATE CREATED: JUN 18, 2020            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  NAME: ALLOW IB TO READ ENROLLMENT FIELDS IN THE PATIENT FILE
  ID: DPT(D0
GLOBAL REFERENCE: DPT
FIELD NUMBER: .3012                     FIELD NAME: SC AWARD DATE
  LOCATION: .3;12                       ACCESS: Read w/Fileman
FIELD NUMBER: .3014                     FIELD NAME: EFF. DATE COMBINED SC% EVAL.
  LOCATION: .3;14                       ACCESS: Read w/Fileman
FIELD NUMBER: .3612                     FIELD NAME: ELIGIBILITY STATUS DATE
  LOCATION: .361;2                      ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   To support the MISSION ACT of 2018, global access to
 the PATIENT file (#2) is requested in order to assist in determining whether a
 veteran is eligible to receive a free Urgent Care visit.  Patient Records will
 be identified by the internal entry number (DFN) in file #2, and read using 
 standard FileMan's APIs.   
  
 Integrated Billing needs access to the following 
   PATIENT file (#2) fields: 
      .3012   SC AWARD DATE                    .3;12 
      .3014   EFF. DATE COMBINED SC% EVAL.     .3;14 
      .3612   ELIGIBILITY STATUS DATE          .361;2 
  STATUS: Pending
KEYWORDS: PATIENT FILE
KEYWORDS: FILE 2
KEYWORDS: INTEGRATED BILLING
KEYWORDS: DPT
KEYWORDS: ENROLLMENT FIELDS
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 7183                            IA #: 7183
  FILE NUMBER: 8989.3                   GLOBAL ROOT: XTV(8989.3,1,
  DATE CREATED: JUN 25, 2020            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: NEW PERSON FIELD MONITOR PURGE
  ID: XTV(8989.3,1,
GLOBAL REFERENCE: XTV(8989.3,1,875)
FIELD NUMBER: 875
  FIELD NAME: NEW PERSON FIELD MONITOR PURGE
  LOCATION: 875;1                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The NEW PERSON FIELD MONITOR PURGE field contains the
 number of days that records in the NEW PERSON FIELD MONITOR (#8933.1) file
 should be maintained before they are purged/deleted.  
 GENERAL DESCRIPTION:   The CLINICAL INFO RESOURCE NETWORK (CIRN) package has a
 monitoring process on the NEW PERSON FIELD MONITOR (#8933.1) file to ensure
 that NEW PERSON (#200) updates are being transmitted to the Person Service
 Identity Management (PSIM) system as part of the Enterprise User Identity 
 functionality. As part of this monitoring process, CIRN will need to retrieve
 the NEW PERSON FIELD MONITOR PURGE (#875) value from the KERNEL SYSTEM
 PARAMETERS (#8989.3) file to determine if the NEW PERSON FIELD MONITOR
 (#8933.1) record has exceeded the timeframe so that it can be purged/deleted
 from the file. This will ensure that the NEW PERSON FIELD MONITOR (#8933.1)
 file is maintained at an acceptable size level.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: KERNEL SYSTEM PARAMETERS
KEYWORDS: 8989.3
KEYWORDS: 875
KEYWORDS: NEW PERSON FIELD MONITOR PURGE
KEYWORDS: MVI
KEYWORDS: IAM
KEYWORDS: XTV(8989.3
KEYWORDS: XUS IAM NPFM PURGE
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
 SUBSCRIBING DETAILS:   CLINICAL INFO RESOURCE NETWORK (CIRN) needs to be able
 to retrieve the NEW PERSON FIELD MONITOR PURGE (#875) value from the KERNEL
 SYSTEM PARAMETERS (#8989.3) file to determine which records should be purged 
 from the NEW PERSON FIELD MONITOR (#8933.1) file.  
  DATE ACTIVATED: SEP 17, 2020

NUMBER: 7184                            IA #: 7184
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: JUL 10, 2020            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: RPA NEW PERSON USER ADD         ID: VA(200,
GLOBAL REFERENCE: VA(200,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 1                         FIELD NAME: INITIAL
  LOCATION: 0;2                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: VA(200,D0,1)
FIELD NUMBER: 4                         FIELD NAME: SEX
  LOCATION: 1;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 9                         FIELD NAME: SSN
  LOCATION: 1;9                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: VA(200,D0,5)
FIELD NUMBER: 29                        FIELD NAME: SERVICE/SECTION
  LOCATION: 5;1                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: VA(200,D0,201)
FIELD NUMBER: 201                       FIELD NAME: PRIMARY MENU OPTION
  LOCATION: 201;1                       ACCESS: Write w/Fileman
GLOBAL REFERENCE: VA(200,D0,51,D1,0)
FIELD NUMBER: .01                       FIELD NAME: KEY
  LOCATION: 0;1                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: VA(200,D0,203,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SECONDARY MENU OPTIONS
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   IB Revenue Operations requires the creation of VistA
 user accounts nationally for bot software access to selected IB options for
 automating certain repetitive tasks. These accounts will be created in the NEW
 PERSON file (#200) by Integrated Billing patch IB*2*680 using Supported VA 
 FileMan database server APIs.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: NEW PERSON
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   The post-init routine for patch IB*2*680 will create
 the entries and populate the additional fields using API UPDATE^DIE().  

NUMBER: 7185                            IA #: 7185
  DATE CREATED: JUL 16, 2020            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFHLZCE
  NAME: DBIA7185                        ID: VAFHLZCE
 GENERAL DESCRIPTION:   Below fields from patient file are getting retrieved
 and populated in ZCE segment: 
  
 2.191,.01      CCP LAST UPDATED DATE 2.191,1        COMMUNITY CARE PROGRAM
 CODE 2.191,2        EFFECTIVE DATE 2.191,3        END DATE 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ZCE
KEYWORDS: VAFHLZCE
COMPONENT/ENTRY POINT: $$EN(DFN,VAFSTR,VAFNUM,VAFHLQ,VAFHLFS,VAFZCE)
 COMPONENT DESCRIPTION:   This generic extrinsic function is designed to return
 the HL7 Community Care Eligibility (ZCE) segment.   
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of Patient (#2) file.  
VARIABLES: VAFSTR                       TYPE: Input
 VARIABLES DESCRIPTION:   String of fields requested, separate by commas. If
 not passed, return all data fields.  
VARIABLES: VAFNUM                       TYPE: Input
 VARIABLES DESCRIPTION:   Sequential Number for SET ID (Default=1).  
VARIABLES: VAFHLQ                       TYPE: Input
 VARIABLES DESCRIPTION:   HL7 Null Variable.  
VARIABLES: VAFHLFS                      TYPE: Input
 VARIABLES DESCRIPTION:   HL7 Field Separator.  
VARIABLES: VAFZCE                       TYPE: Output
 VARIABLES DESCRIPTION:   Array to return ZCE segments.  
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  DATE ACTIVATED: DEC 01, 2020

NUMBER: 7186                            IA #: 7186
  FILE NUMBER: 70                       DATE CREATED: JUL 20, 2020
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CONNECT RADIOLOGY EXAM TO VISIT
GLOBAL REFERENCE: RADPT(D0,'DT',D1,'P')
FIELD NUMBER: 27                        FIELD NAME: VISIT
  LOCATION: 70.03;27                    ACCESS: Both R/W w/Fileman
 FIELD DESCRIPTION:   Pointer to Visit file #9000010.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RADIOLOGY EXAM
KEYWORDS: PCE VISIT
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   The PCE utility PXQ PRIMARY PROVIDER REPAIR searches
 for encounters that do not have a primary provider and when one is found tries
 to set the primary provider. In some cases, an occasion of service created by 
 Radiology may not have been linked to the corresponding Radiology Exam, data
 element: 70.03, 27. In this situation, the utility will work to establish the
 link by matching the patient's Exam Date and Time to the Visit Date and Time,
 the Radiology Imaging Location to the Visit's Hospital Location, and the
 Radiology Procedure to one of the Procedures for the occasion of service. If
 all of these conditions are met, it is considered a match and PCE sets data
 element 70.03, 27 to the Visit pointer using FileMan.  
  
 This will be effective with patch PX*1*211.  
  DATE ACTIVATED: JUL 21, 2020

NUMBER: 7187                            IA #: 7187
  FILE NUMBER: 9000001                  DATE CREATED: JUL 22, 2020
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DG ACCESS TO DD(9000001,0,'PT'
GLOBAL REFERENCE: DD(9000001,0,'PT'
 GENERAL DESCRIPTION:   The REGISTRATION package is requesting approval to
 access the list of Files that point to the PATIENT/IHS File by examining
 entries in ^DD(9000001,0,"PT"). The purpose is to identify Patient-related
 Files for the VistA Security Remediation Audit Solution (VAS) in order to
 determine which AUDIT (#1.1) records should be sent to the external archive.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: REGISTRATION
  DATE ACTIVATED: AUG 13, 2020

NUMBER: 7188                            IA #: 7188
  DATE CREATED: JUL 27, 2020            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: YSCLTST5
  NAME: DBIA7188                        ID: YSCLTST5
 GENERAL DESCRIPTION:   This agreement provides the calling program to build
 inpatient clozapine data for transmission.  This ICR is created to document a
 call to INPSND^YSCLRST5, which was released in patch PSJ*5*327.  
  STATUS: Active
KEYWORDS: CLOZAPINE
COMPONENT/ENTRY POINT: INPSND
 COMPONENT DESCRIPTION:   This entry point will gather patient demographic
 data, facility information, inpatient medications and build data in XTMP
 global for transmission.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: AUG 24, 2020

NUMBER: 7189                            IA #: 7189
  DATE CREATED: AUG 04, 2020            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DG MENU OPTIONS FOR BILLING USERS
 GENERAL DESCRIPTION:   The billing users of the [IB OUTPUT PATIENT REPORT
 MENU] menu need access to REGISTRATION menu options [DG OTH FSM ELIG. CHANGE
 REPORT] and [DG OTH FSM DETAIL REPORT]. These reports are developed in DG
 namespace patch DG*5.3*1025. This is to identify patients treated under Other
 Than Honorable authority and get detailed information about these patients.  
  
 Integrated Billing is requesting permission to export the option [DG OTH FSM
 ELIG. CHANGE REPORT] and [DG OTH FSM DETAIL REPORT] in their menu option [IB
 OUTPUT PATIENT REPORT MENU] in patch IB*2*685 and will be using the option.  
  
 This Integration Agreement grants permission to make these REGISTRATION 
 options included in the [IB OUTPUT PATIENT REPORT MENU] menu.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DG OTH FSM ELIG. CHANGE REPORT
 COMPONENT DESCRIPTION:   [DG OTH FSM ELIG. CHANGE REPORT] Former OTH Patient
 Change in Eligibility Report.  
VARIABLES:  
 VARIABLES DESCRIPTION:   Permission to use Option: 
COMPONENT/ENTRY POINT: DG OTH FSM DETAIL REPORT
 COMPONENT DESCRIPTION:   [DG OTH FSM DETAIL REPORT]  Former OTH Patient Detail
 Report 
VARIABLES:  
 VARIABLES DESCRIPTION:   Permission to use Option: 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: SEP 04, 2020

NUMBER: 7190                            IA #: 7190
  FILE NUMBER: 18.02                    GLOBAL ROOT: XOB(18.02
  DATE CREATED: AUG 05, 2020            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS TO THE WEB SERVICE FILE 18.02
  ID: XOB(18.02
GLOBAL REFERENCE: XOB(18.02,B
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This request is for a one time use in patch DG*5.3*1014
 post installation processing.  
  
 Registration requests read access to the WEB SERVICE (#18.02) file. The 
 post-install routine creates a WEB SERVICE record using the supported 
 REGREST^XOBWLIB API, then reads the WEB SERVICE file with the $$GET1^DIQ 
 FileMan API to get the IEN of the WEB SERVICE record. Then in further 
 processing (reference pending ICR-7191) updates the WEB SERVER (#18.12) file,
 AUTHORIZED WEB SERVICES (#100) multiple.  
     
 This processing is done programmatically to avoid having sites manually 
 configure HWSC using the Web Server Manager.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 18.02
KEYWORDS: XOBW
KEYWORDS: WEB SERVICE FILE
SUBSCRIBING PACKAGE: REGISTRATION
  DATE ACTIVATED: OCT 19, 2020

NUMBER: 7191                            IA #: 7191
  FILE NUMBER: 18.12                    GLOBAL ROOT: XOB(18.12
  DATE CREATED: AUG 05, 2020            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ/WRITE ACCESS TO WEB SERVER FILE 18.12
  ID: XOB(18.12
GLOBAL REFERENCE: XOB(18.12,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: SERVER
  LOCATION: 0;4                         ACCESS: Write w/Fileman
FIELD NUMBER: .06                       FIELD NAME: STATUS
  LOCATION: 0;6                         ACCESS: Write w/Fileman
FIELD NUMBER: .07                       FIELD NAME: DEFAULT HTTP TIMEOUT
  LOCATION: 0;7                         ACCESS: Write w/Fileman
FIELD NUMBER: 1.01                      FIELD NAME: LOGIN REQUIRED
  LOCATION: 1;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 3.01                      FIELD NAME: SSL ENABLED
  LOCATION: 3;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 3.02                      FIELD NAME: SSL CONFIGURATION
  LOCATION: 3;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 3.03                      FIELD NAME: SSL PORT
  LOCATION: 3;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 200                       FIELD NAME: USERNAME
  LOCATION: 200;1                       ACCESS: Write w/Fileman
FIELD NUMBER: 300                       FIELD NAME: PASSWORD
  LOCATION: 300;1                       ACCESS: Write w/Fileman
GLOBAL REFERENCE: XOB(18.12,D0,100,D1
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: .06                       FIELD NAME: STATUS
  LOCATION: 0;6                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   The VistA REE (Registration, Eligibility and
 Enrollment) team requests    read/write access to the WEB SERVER (#18.12) file
 to add a new entry during the DG*5.3*1014 post-install process. The
 post-install routine process will create the new server record entry using
 UPDATE^DIE and will also create a new entry to the AUTHORIZED WEB SERVICES
 (#100) multiple, WEB SERVICE (#.01) field.  
     
 NOTE: This processing is done programmatically to avoid having sites manually
 configure HWSC using the Web Server Manager. This will ensure all sites have
 the same configuration installed correctly. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 18.12
KEYWORDS: WEB SERVER FILE
SUBSCRIBING PACKAGE: REGISTRATION
  DATE ACTIVATED: OCT 19, 2020

NUMBER: 7192                            IA #: 7192
  DATE CREATED: AUG 31, 2020            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  ROUTINE: SDM0                         NAME: DETERMINE FOLLOW-UP
  ID: SDM0
 GENERAL DESCRIPTION:   The DSS Electronic Dental Record Manager (EDRM)
 application is creating Dental appointments for the Cerner Millennium
 integration. Millennium sends an SIU^S14 HL7 message when a Veteran checks in
 to the Dental Clinic. The HL7 message allows Dental users to select a VistA
 appointment that matches the Millennium Encounter. The HL7 message also
 contains necessary encounter data to be returned to Millennium when filing
 vital signs, notes and encounter procedures/diagnoses so that the records are 
 applied to the correct Millennium encounter.  
  
 The PTFU API returns the follow-up visit indicator to be filed into the 
 FOLLOW-UP VISIT (#28) field of the APPOINTMENT (#2.98) subfile of the PATIENT
 (#2) file.  
  STATUS: Pending
COMPONENT/ENTRY POINT: $$PTFU(DFN,SC)
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This is the patient DFN.  
VARIABLES: SC                           TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This is the clinic IEN.  
SUBSCRIBING PACKAGE: DENTAL

NUMBER: 7193                            IA #: 7193
  DATE CREATED: AUG 31, 2020            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  ROUTINE: SDM1A                        NAME: NEW APPOINTMENT STATUS
  ID: SDM1A
 GENERAL DESCRIPTION:   The DSS Electronic Dental Record Manager (EDRM)
 application is creating Dental appointments for the Cerner Millennium
 integration. Millennium sends an SIU^S14 HL7 message when a Veteran checks in
 to the Dental Clinic. The HL7 message allows Dental users to select a VistA
 appointment that matches the Millennium Encounter. The HL7 message also
 contains necessary encounter data to be returned to Millennium when filing
 vital signs, notes and encounter procedures/diagnoses so that the records are 
 applied to the correct Millennium Encounter.  
  
 The STATUS API determines the status for the new appointments to be fild into
 the STATUS (#3) field of the APPOINTMENT (#2.98) subfile of the PATIENT (#2)
 file when creating an appointment.  
  STATUS: Pending
COMPONENT/ENTRY POINT: $$STATUS(SDCL,SDINP,SDT)
VARIABLES: SDCL                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This is the clinic IEN.  
VARIABLES: SDINP                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This is the inpatient status of the
 patient.  
VARIABLES: SDT                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Appointment date/time 
SUBSCRIBING PACKAGE: DENTAL

NUMBER: 7194                            IA #: 7194
  FILE NUMBER: 8925                     GLOBAL ROOT: TIU(8925
  DATE CREATED: AUG 31, 2020
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  NAME: TIU DENTAL NOTES                ID: TIU(8925
GLOBAL REFERENCE: TIU(8925,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DOCUMENT TYPE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PATIENT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: PARENT
  LOCATION: 0;6                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: TIU(8925,D0,12)
FIELD NUMBER: 1201                      FIELD NAME: ENTRY DATE/TIME
  LOCATION: 12;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 1202                      FIELD NAME: AUTHOR/DICTATOR
  LOCATION: 12;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 1208                      FIELD NAME: EXPECTED COSIGNER
  LOCATION: 12;8                        ACCESS: Read w/Fileman
FIELD NUMBER: 1212                      FIELD NAME: DIVISION
  LOCATION: 12;12                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: TIU(8925,D0,15)
FIELD NUMBER: 1501                      FIELD NAME: SIGNATURE DATE/TIME
  LOCATION: 15;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 1502                      FIELD NAME: SIGNED BY
  LOCATION: 15;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 1507                      FIELD NAME: COSIGNATURE DATE/TIME
  LOCATION: 15;7                        ACCESS: Read w/Fileman
FIELD NUMBER: 1508                      FIELD NAME: COSIGNED BY
  LOCATION: 15;8                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Electronic Dental Record Manager (EDRM) application
 is creating MDM^T02 HL7 messages for the Cerner Millennium integration. These 
 messages contain signed Dental TIU Notes. Dental is requesting to read 
 discreet data from the TIU DOCUMENT (#8925) file to create the HL7 message.  
  STATUS: Pending
SUBSCRIBING PACKAGE: DENTAL

NUMBER: 7195                            IA #: 7195
  FILE NUMBER: 8925.7                   GLOBAL ROOT: TIU(8925.7
  DATE CREATED: AUG 31, 2020
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  NAME: TIU ADDITIONAL SIGNERS          ID: TIU(8925.7
GLOBAL REFERENCE: TIU(8925.7,D0,0)
FIELD NUMBER: .03                       FIELD NAME: EXPECTED SIGNER
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: COSIGNATURE DATE/TIME
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: ACTUAL COSIGNER
  LOCATION: 0;5                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Electronic Dental Record Manager (EDRM) application
 is creating MDM^T02 HL7 messages for the Cerner Millennium integration. These 
 messages contain signed Dental TIU Notes. Dental is requesting to read 
 discreet data from the TIU MULTIPLE SIGNATURE (#8925.7) file to add signature,
 cosignature, and additional signature information to the HL7 message.  
  STATUS: Pending
SUBSCRIBING PACKAGE: DENTAL

NUMBER: 7196                            IA #: 7196
  FILE NUMBER: 123                      GLOBAL ROOT: GMR
  DATE CREATED: SEP 02, 2020
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  NAME: LOOK UP REQUEST/CONSULTATION DATA
  ID: GMR
GLOBAL REFERENCE: GMR(123,
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: 8                         FIELD NAME: CPRS STATUS
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: LAST ACTION TAKEN
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 17                        FIELD NAME: CLINICALLY INDICATED DATE
  LOCATION: 0;24                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: URGENCY
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .126                      FIELD NAME: REMOTE ORDERING PROVIDER
  LOCATION: 12;6                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 30.1                      FIELD NAME: PROVISIONAL DIAGNOSIS CODE
  LOCATION: 30.1;1                      ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .125                      FIELD NAME: IFC ROLE
  LOCATION: 12;5                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SENDING PROVIDER
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: GMR(123,D0,40,D1,
FIELD NUMBER: 1                         FIELD NAME: ACTIVITY
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: FORWARDED FROM
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: GMR(123,'AC'
 GLOBAL DESCRIPTION:   Used to get the request entry in file #123 based on the
 ORIFN from OE/RR.  
GLOBAL REFERENCE: GMR(123,D0,40,D1,1,
FIELD NUMBER: 5                         FIELD NAME: COMMENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: GMR(123,D0,20,D1,
FIELD NUMBER: .01                       FIELD NAME: REASON FOR REQUEST
  LOCATION: 20;.01                      ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Centralized Scheduling Solution (CSS) project, part
 of the larger EHRM project, requests permission to read data from file #123 as
 detailed below. Patch OR*3.0*520 will be using this ICR.  
  STATUS: Pending
KEYWORDS: CSS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 7197                            IA #: 7197
  DATE CREATED: SEP 03, 2020
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORMCTR
  NAME: UPDATE CONSULT ORDER STATUS FROM SCHEDULING
  ID: ORMCTR
 GENERAL DESCRIPTION:   This agreement allows the new Scheduling routine
 SDMCMAKE (SD*5.3*738) to call the new Order Entry routine ORMCTR (OR*3.0*520)
 at the entry point TRUPDMSG and pass a consult order IEN. The variable CONSID
 is the IEN of a consult order created inside Scheduling and is used to trigger
 an status update via an HLO message for an order from the Centralized
 Scheduling Solution (CSS). This ICR will be used in patch SD*5.3*738.  
  STATUS: Pending
KEYWORDS: SDMCMAKE
KEYWORDS: ORMCTR
COMPONENT/ENTRY POINT: TRUPDMSG
 COMPONENT DESCRIPTION:   Call execution: D TRUPDMSG^ORMCTR(CONSID). 
VARIABLES: CONSID                       TYPE: Input
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 7198                            IA #: 7198
  DATE CREATED: SEP 03, 2020            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Other
  NAME: VDIF access to VA MPI FTL
 GENERAL DESCRIPTION:   VDIF needs to access the FTL (Facility Treatment List)
 for a patient from VA MPI.  
  
 VA MPI note: The only approved business process to use VDIF Patient Registry
 is Cerner HIE.  External VistA apps should be coming to VA MPI directly (not
 proxying through VDIF) and VistA apps should be using the local VAFC LOCAL
 GETCORRESPONDINGIDS RPC.  
  
 This ICR cannot be used by other packages trying to proxy access through VDIF.
 It is not VDIF data to expose and/or approve exposure to. It is VA MPI and
 more importantly IAM IPT technical and business owners to approve the FTL
 access.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: FTL
KEYWORDS: VDIF
KEYWORDS: PATIENT
KEYWORDS: MPI
COMPONENT/ENTRY POINT: FTL list on VDIF
 COMPONENT DESCRIPTION:   A listing of treatment facilities for every patient.  
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   VDIF is granted private access to attain the Facility
 Treatment List (FTL) for a patient from VA MPI.  

NUMBER: 7199                            IA #: 7199
  DATE CREATED: SEP 04, 2020            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: WVRPCVPR
  NAME: WOMEN VET API FOR VPR           ID: WVRPCVPR
 GENERAL DESCRIPTION:   Allow subscriber access for Virtual Patient Record
 (VPR) to the routine BASELINE^WVRPCVPR so that VPR may retrieve preganancy
 status for a patient. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: WVRPCVPR
COMPONENT/ENTRY POINT: BASELINE
VARIABLES: DFN                          TYPE: Input
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: SEP 29, 2020

NUMBER: 7200                            IA #: 7200
  DATE CREATED: SEP 04, 2020            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: WOMEN VET PROTOCOL FOR VPR
 GENERAL DESCRIPTION:   To document Virtual Patient Record's (VPR) use of the
 WV PREGNANCY STATUS CHANGE EVENT protocol.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: WV PREGNANCY STATUS CHANGE
COMPONENT/ENTRY POINT: WV PREGNANCY CHANGE EVENT PROTOCOL
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: SEP 29, 2020

NUMBER: 7201                            IA #: 7201
  DATE CREATED: SEP 04, 2020            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Routine
  ROUTINE: SDMCGAPT                     NAME: APPT CANCELLATION REASON TYPE
  ID: SDMCGAPT
 GENERAL DESCRIPTION:   This agreement allows the routine ORMCCORE to call the
 routine SDMCGAPT to obtain the cancellation reason and type (in external and
 internal format) for a given patient appointment.  
  STATUS: Pending
KEYWORDS: ORMCCORE
COMPONENT/ENTRY POINT: GTCANRSN
VARIABLES: PATIENTIEN,APPTDT            TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN and appoinment date.  
COMPONENT/ENTRY POINT: GTCNRNTP
VARIABLES: PATIENTIEN,APPTDT            TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN and appoinment date.  
VARIABLES: CANREASON                    TYPE: Output
 VARIABLES DESCRIPTION:   This is the cancellation reason.  
VARIABLES: VAL                          TYPE: Output
 VARIABLES DESCRIPTION:   Cancellation reason type in internal format.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 7202                            IA #: 7202
  DATE CREATED: SEP 17, 2020            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBEFSMUT
  NAME: BILLING STATUS API              ID: IBEFSMUT
 GENERAL DESCRIPTION:   This DBIA is for allowing the REGISTRATION package to
 call the EN^IBEFSMUT(DFN,BEGDT,ENDDT,LIST) entry point to return requested
 data elements stored in the INTEGRATED BILLING application. Listed below are 
 the details on accessing this entry point and the data that should be 
 returned.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN(DFN,BEGDT,ENDDT,LIST)
VARIABLES: DFN                          TYPE: Both
 VARIABLES DESCRIPTION:   Internal entry number from the PATIENT file (#2)
 [required] 
VARIABLES: BEGDT                        TYPE: Input
 VARIABLES DESCRIPTION:   EVENT DATE Beginning Date [required] 
VARIABLES: ENDDT                        TYPE: Input
 VARIABLES DESCRIPTION:   EVENT DATE Ending Date [required] 
VARIABLES: LIST                         TYPE: Both
 VARIABLES DESCRIPTION:   Subscript name used in the ^TMP global [required] 
  
  
 EN^IBEFSMUT(DFN,BEGDT,ENDDT,LIST) 
  
 Input: 
   DFN 
   BEGDT 
   ENDDT 
   LIST 
  
 FILE #350 OUTPUT: 
   
 ^TMP($J,LIST,FILENO,DFN,0)=Total entries or -1^NO DATA FOUND 
 ^TMP($J,LIST,FILENO,DATE,DFN,RECCNT)=ACTION TYPE^BILLING GROUP^IEN^BILL 
 NUMBER^RESULTING FROM^TOTAL CHARGE^STATUS^INSTITUTION^CLINIC STOP^USER LAST
 UPDATING 
  
 Where: 
  LIST   = Subscript name used in the ^TMP global 
  FILENO = File #350, this is to distinguish where records coming from 
  DATE   = Event Date (I:350,.17) 
  DFN    = IEN from the PATIENT File(#2) 
  RECCNT = Record counter 
  
 1^2^3^4^5^6^7^8^9^10, where: 
  1 = ACTION TYPE (E;350,.03) 
  2 = BILLING GROUP (I;350.1,.11) 
      Note: NULL is returned if there is no BILLING GROUP 
  3 = IEN from INTEGRATED BILLING file (#350) 
  4 = AR BILL NUMBER (E;350,.11) 
      Note: NULL is returned if there is no AR BILL NUMBER 
  5 = RESULTING FROM (I;350,.04) 
      Note: If RESULTING FROM 2ND ^ piece ":"=350, 
      the format will be: 
      RESULTING FROM;DATE BILLED FROM(I;350,.14): 
      COPAYMENT TIER (I;350,.22) 
  6 = TOTAL CHARGE (E;350,.07) 
  7 = STATUS (E;350,.05) 
  8 = INSTITUTION (IE;350,.13) 
  9 = CLINIC STOP(IE;350,.2) 
      Note: NULL is returned if there is no CLINIC STOP 
  10 = USER LAST UPDATING (E;350,13) 
  
  
 FILE #399 OUTPUT: 
  
 ^TMP($J,LIST,FILENO,DFN,0)=Total entries or -1^NO DATA FOUND 
 ^TMP($J,LIST,FILENO,DATE,DFN,RECCNT)=RATE TYPE^IEN^RATE TYPE NAME^IEN^BILL 
 NUMBER^RESULTING FROM^CHARGES^STATUS 
  
 Where: 
  LIST   = Subscript name used in the ^TMP global 
  FILENO = File #399, this is to distinguish where the records coming from 
  DATE   = Event Date (399,.03) 
  DFN    = IEN from the PATIENT File (#2) 
  RECCNT = Record Counter 
  
 1^2^3^4^5^6^7^8^9^10, where 
  1 = BILL CLASSIFICATION (I;399,.05) 
  2 = RATE TYPE NAME (E;399,.07) 
  3 = IEN from BILL/CLAIMS file (#399) 
  4 = BILL NUMBER (E;399,.01) 
  5 = RESULTING FROM, will be in the format of: 
      
      If inpatient bill, the format will be: 
      BILL TYPE:BILL CLASSIFICATION(E;399,.05) 
      
      Note: BILL TYPE=1 if inpatient bill 
            BILL TYPE=0 if outpatient bill 
            BILL TYPE=3 if Rx bill 
  
      If outpatient bill, the format will be: 
      TYPE (I;399.042,.1):BILL CLASSIFICATION(E;399,.05):BILL TYPE 
  
      If Rx bill, the format will be: 
      BILL TYPE:BEDSECTION(E;399.042,.05):RXIEN (I;362.4,.05): 
      RXNUMBER (E;362.4,.01):RXFILL NUMBER(I;362.4,.1):RXSTATUS(52,100) 
  
  6 = CHARGES 
      Note: 
      If inpatient bill, CHARGES will be extracted in 399,201 
      If outpatient/Rx bill, CHARGES will be extracted in 399.042,.04 
         
  7 = STATUS (E;399,.13) 
  8 = DIVISION(I;399,.22) 
  9 = ENTERED/EDITED BY (E;399,2) 
  10 = PTFIEN (I;399,.08) 
      Note: If inpatient bill, this ^piece contain the PTF ENTRY NUMBER 
            If outpatient bill, this ^piece contain the outpatient 
            encounter IEN 
            Otherwise, NULL is returned.  
  
  
 Example: 
  
  >K ^TMP($J,"TEST") 
  >D EN^IBEFSMUT(7251646,3201016,3201019,"TEST") 
  >ZW ^TMP($J,"TEST") 
  ^TMP(14840,"TEST",350,7251646,0)="-1^NO DATA FOUND" 
  ^TMP(14840,"TEST",399,7251646,0)="-1^NO DATA FOUND" 
  >K ^TMP($J,"TEST") 
  
  >D EN^IBEFSMUT(7251646,3201101,3201201,"TEST") 
  >ZW ^TMP($J,"TEST") 
  ^TMP(14840,"TEST",350,3201130,7251646,1)="PSO SC RX COPAY NEW^ 
  5^3568678^442-K003SK6^350:3568678;3201130:1^$5^CANCELLED^ 
  442-CHEYENNE VA MEDICAL^^USER,ONE" 
  ^TMP(14840,"TEST",350,3201130,7251646,2)="PSO NSC RX COPAY NEW^ 
  5^3568627^442-K003SC3^52:3836390;1:1^$8^BILLED^ 
  442-CHEYENNE VA MEDICAL^^USER,ONE" 
  ^TMP(14840,"TEST",350,7251646,0)=2 
  ^TMP(14840,"TEST",399,3201130,7251646,1)="1^INELIGIBLE^2818792^ 
  K003SJX^1:INPATIENT (MEDICARE PART A)^4626^ 
  ENTERED/NOT REVIEWED^1^USER,ONE^71212" 
  ^TMP(14840,"TEST",399,3201201,7251646,2)="3^INELIGIBLE^2818811^ 
  K003SKG^2:OUTPATIENT VISIT:0^409^ENTERED/NOT REVIEWED^ 
  4^USER,ONE^10501632" 
  ^TMP(14840,"TEST",399,3201201,7251646,3)="3^INELIGIBLE^2818533^ 
  K003SCI^3:PRESCRIPTION:3836389:2911742:0:0^19.87^AUTHORIZED^ 
  1^USER,ONE" 
  >K ^TMP($J,"TEST") 
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   The REGISTRATION package needs to include some data
 elements found in the Integrated Billing Action file (#350) and Bill/Claims
 file (#399) on the following report: 1. Former OTH Patient Eligibility Change
 Report 2. Former OTH Patient Detail Report 3. Presumptive Psychosis
 Reconciliation Report 4. Presumptive Psychosis Detail Report 
  DATE ACTIVATED: FEB 18, 2021

NUMBER: 7203                            IA #: 7203
  DATE CREATED: SEP 21, 2020            CUSTODIAL PACKAGE: VBECS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: VBECRPT                      NAME: DBIA3879-D
  ID: VBECRPT
 GENERAL DESCRIPTION:   The entry point EN^VBECRPT is provided by the Blood
 Bank package to return Blood Bank patient related data for use by CPRS.  This
 data will be used to populate the Blood Bank Report listed under the Reports
 tab.  
  STATUS: Pending
COMPONENT/ENTRY POINT: EN
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 7204                            IA #: 7204
  FILE NUMBER: 18.12                    GLOBAL ROOT: XOB(18.12
  DATE CREATED: OCT 01, 2020            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ WRITE ACCESS TO WEB SERVER FILE
  ORIGINAL NUMBER: 7204                 ID: XOB(18.12
GLOBAL REFERENCE: XOB(18.12,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: .03                       FIELD NAME: PORT
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: .04                       FIELD NAME: SERVER
  LOCATION: 0;4                         ACCESS: Write w/Fileman
FIELD NUMBER: .06                       FIELD NAME: STATUS
  LOCATION: 0;6                         ACCESS: Write w/Fileman
FIELD NUMBER: .07                       FIELD NAME: DEFAULT HTTP TIMEOUT
  LOCATION: 0;7                         ACCESS: Write w/Fileman
FIELD NUMBER: 1.01                      FIELD NAME: LOGIN REQUIRED
  LOCATION: 1;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 3.01                      FIELD NAME: SSL ENABLED
  LOCATION: 3;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 100                       FIELD NAME: AUTHORIZED WEB SERVICES
  LOCATION: 100;0                       ACCESS: Write w/Fileman
GLOBAL REFERENCE: XOB(18.12,D0,100,D1
FIELD NUMBER: .01                       FIELD NAME: WEB SERVICE
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: .06                       FIELD NAME: STATUS
  LOCATION: 0;6                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: XOB(18.12,'B',
 GLOBAL DESCRIPTION:   "B" cross reference used for lookup to determine whether
 to add or edit entry.  
GLOBAL REFERENCE: XOB(18.12,D0,100,'B'
 GLOBAL DESCRIPTION:   Loop to see if service exists to determine whether to
 add or edit.  
 GENERAL DESCRIPTION:   This request is for a one time use in patch
 GMRC*3.0*124 post installation processing.  
     
 GMRC (Consults Decision Support Tool) requests read and write access to the
 WEB SERVER (#18.12) file.  The post-install routine checks if the server
 record exists, then either creates or updates the record using either the
 UPDATE^DIE or FILE^DIE FileMan API calls, respectively.  In addition it adds
 an entry (if it doesn't exist) to the AUTHORIZED WEB SERVICES (#100) multiple,
 WEB SERVICE (#.01) field using the UPDATE^DIE FileMan API.  
     
 This processing is done programmatically to avoid having sites manually 
 configure.  
  
 Revision History: 
  - Added 3/20/25 - This request is for a one time write access in patch
 DVBA*2.7*255 post installation processing.  
        
    CAPRI (Compensation and Pension Record Interchange) requests read and write
 access to the WEB SERVER (#18.12) file.  The post-install routine checks if
 the server record exists, then creates the record using the FILE^DICN FileMan
 API call. In addition it adds an entry (if it doesn't exist) to the AUTHORIZED
 WEB SERVICES (#100) multiple, WEB SERVICE (#.01) field using the UPDATE^DIE
 FileMan API.  
        
    This processing is done programmatically to avoid having sites manually 
 configure.  
  
    The CAPRI routine that uses the HealtheVet Web Service Client uses    
    FIND1^DIC FileMan API to check the web server was installed before 
    proceeding.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XOBW
KEYWORDS: WEB SERVER FILE
KEYWORDS: MISSION ACT
KEYWORDS: DST
KEYWORDS: DECISION SUPPORT TOOL
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Added 11/20/23 effective with patch TIU*1.0*363, for
 Community Care Referrals & Authorization (CCRA) project to create a new web
 service that host a service to provide IP addresses and ports used to update
 the TIUCCRA HL7 Logical Link file. The patch also reads data for this new 
 service. The TIU patch uses FileMan APIs to create the new web service and to
 read the data for the web service.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Added 3/11/25 effective with patch IB*2.0*770, for MCCF
 TAS as part of the Automated Community Care (ACC) Claims Epic project to
 provide one-time read and write access to the WEB SERVER (#18.12) in
 post-install routine IBY770PO. IB will add a WEB SERVER to call the DSS CLAIM
 SCRUBBER.  The post-install routine checks if the server record exists, then
 either creates or updates the record using either FileMan API calls.  
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Added 3/20/25 effective with patch DVBA*2.7*255, for
 AMIE/CAPRI to create a new web service that CAPRI's Exam Management System can
 use to query VBMS's Veteran API. The patch also reads data for this new
 service.  The AMIE patch uses FileMan APIs to create the new web service and
 to read the data for the web service.  
  DATE ACTIVATED: NOV 20, 2023

NUMBER: 7205                            IA #: 7205
  FILE NUMBER: 18.02                    GLOBAL ROOT: XOB(18.02
  DATE CREATED: OCT 01, 2020            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ WRITE ACCESS TO THE WEB SERVICE FILE
  ORIGINAL NUMBER: 7204                 ID: XOB(18.02
GLOBAL REFERENCE: XOB(18.02,'B',
 GLOBAL DESCRIPTION:   Need to determine whether we are adding or editing an
 entry.  
GLOBAL REFERENCE: XOB(18.02,D0,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: .02                       FIELD NAME: TYPE
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: 200                       FIELD NAME: CONTEXT ROOT
  LOCATION: 200;1                       ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   
  
 This request is for a one time use in patch GMRC*3.0*124 post installation 
 processing.  
  
 GMRC (Consult Decision Support Tool) requests read and write access to the WEB
 SERVICE (#18.02) file. The post-install routine creates a WEB SERVICE record.
 Then in further processing (reference ICR-7204) updates the WEB SERVER
 (#18.12) file, AUTHORIZED WEB SERVICES (#100) multiple.  
     
 This processing is done programmatically to avoid having sites manually 
 configure.  
  
 Revision History: 
  - Added 3/20/25: 
   This request is for a one time write access in patch DVBA*2.7*255 post
 installation processing. CAPRI (Compensation and Pension Record Interchange)
 requests read and write access to the WEB SERVICE (#18.02) file. The
 post-install routine creates a WEB SERVICE record. Then in further processing
 (reference ICR- 7204) updates the WEB SERVER (#18.12) file, AUTHORIZED WEB
 SERVICES (#100) multiple. 
    This processing is done programmatically to avoid having sites manually
 configure.  
    The CAPRI routine that uses the HealtheVet Web Service Client uses    
    FIND1^DIC FileMan API to check the web service was installed before 
    proceeding.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XOBW
KEYWORDS: WEB SERVICE FILE
KEYWORDS: MISSION ACT
KEYWORDS: DST
KEYWORDS: DECISION SUPPORT TOOL
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Added 11/20/23 effective with patch TIU*1.0*363, for
 Community Care Referrals & Authorization (CCRA) project to create a new web
 service that host a service to provide IP addresses and ports used to update
 the TIUCCRA HL7 Logical Link file. The patch also reads data for this new 
 service. The TIU patch uses FileMan APIs to create the new web service and to
 read the data for the web service.  
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Added 3/11/35, effective with patch IB*2.0*770, for
 MCCF TAS as part of the Automated Community Care (ACC) Claims Epic project to
 provide one-time read and write access to the WEB SERVICE (#18.02) file in
 post-install routine IBY770PO. IB will add a WEB SERVICE to call the DSS CLAIM 
 SCRUBBER. Then in further processing (reference ICR-7204) updates the WEB 
 SERVER (#18.12) file, AUTHORIZED WEB SERVICES (#100) multiple. The 
 post-install routine checks if the server record exists, then either creates
 or updates the record using either FileMan API calls. 
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Added 3/20/25 effective with patch DVBA*2.7*255, for
 AMIE/CAPRI to create a new web service that CAPRI's Exam Management System can
 use to query VBMS's Veteran API. The patch also reads data for this new
 service. The AMIE patch uses supported HWSC API REGREST^XOBWLIB to create new
 web service and FIND1^DIC FileMan API to read the data for the web service.  
  DATE ACTIVATED: NOV 21, 2023

NUMBER: 7206                            IA #: 7206
  FILE NUMBER: 55.06                    GLOBAL ROOT: PS(
  DATE CREATED: OCT 21, 2020
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: File
  NAME: Clozapine Inpatient Reference   ID: PS(
GLOBAL REFERENCE: PS(55.06
FIELD NUMBER: 19                        FIELD NAME: DATE VERIFIED BY PHARMACIST
  LOCATION: 4;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the date the order was verified by the
 pharmacist.  
 GENERAL DESCRIPTION:   The MENTAL HEALTH (YS) Clozapine module has a need to
 read the DATE VERIFIED BY PHARMACIST field (#19) in the UNIT DOSE multiple
 (#62) (sub-file 55.06) in the PHARMACY PATIENT file (#55) via FileMan. 
  
 This field is not included in the PHARMACY DATA MANAGEMENT (PDM) API's.  When
 the field becomes available via PDM API, the FileMan reference should be
 converted to API call and this ICR should be retired.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: YS
KEYWORDS: PSO
KEYWORDS: CLOZ
KEYWORDS: 55.06
KEYWORDS: PS(55.06
KEYWORDS: MENTAL HEALTH
SUBSCRIBING PACKAGE: MENTAL HEALTH

NUMBER: 7207                            IA #: 7207
  FILE NUMBER: 52.52                    GLOBAL ROOT: PS(
  DATE CREATED: OCT 21, 2020            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  NAME: CLOZAPINE OVERRIDES             ID: PS(
 GENERAL DESCRIPTION:   The MENTAL HEALTH (YS) Clozapine module has a need to
 read the SECOND APPROVING TEAM MEMBER field (#6) in the CLOZAPINE PRESCRIPTION
 OVERRIDES file (#52.52) via FileMan. 
  
 The MENTAL HEALTH (YS) package formerly had access to the file via expired ICR
 DBIA273-D, which was replaced by Pharmacy Data Management API PSO5252. The
 PSO5252 API does not include this field.  
  
 When the field becomes available via Pharmacy API, the FileMan reference 
 should be converted to API call and this ICR should be retired.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: CLOZAPINE
KEYWORDS: OVERRIDES
KEYWORDS: 52.52
KEYWORDS: PS(52.52
SUBSCRIBING PACKAGE: MENTAL HEALTH

NUMBER: 7208                            IA #: 7208
  DATE CREATED: OCT 23, 2020            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGREGEEWS
  NAME: RETRIEVE ENROLLMENT STATUS      ID: DGREGEEWS
 GENERAL DESCRIPTION:   This API will be used to determine if the Patient is
 known to Enrollment System or not by calling E&E Web Service.  
  STATUS: Active
KEYWORDS: EE WEBSERVICE
KEYWORDS: ENROLLMENT STATUS
COMPONENT/ENTRY POINT: EN
VARIABLES: DGKEY                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient full ICN 
VARIABLES: DGREQNAM                     TYPE: Input
 VARIABLES DESCRIPTION:   Requestor Name 
VARIABLES: DGENSTAT                     TYPE: Output
 VARIABLES DESCRIPTION:   Contains the Enrollment Status 
VARIABLES: DGWSHTOE                     TYPE: Output
 VARIABLES DESCRIPTION:   Contains the "Do you Wish to Enroll?" value.  
VARIABLES: DGCOMP                       TYPE: Output
 VARIABLES DESCRIPTION:   Contains the COMPACT Act indicator value (Yes or No) 
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 8/22/23, effective with PX*1.0*235 and
 DG*5.3*1095, which are part of Release 1 of the COMPACT Act project.  
  DATE ACTIVATED: MAR 03, 2021

NUMBER: 7209                            IA #: 7209
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: OCT 26, 2020            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: AMPL USER IDENTIFICATION        ID: VA(200,
GLOBAL REFERENCE: VA(200,DA
FIELD NUMBER: .001                      FIELD NAME: NUMBER
  LOCATION:                             ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the internal entry number of the NEW PERSON File
 (#200).  
 GENERAL DESCRIPTION:   The Advanced Medication Platform (AMPL) application
 requests access the internal entry number of all entries of the NEW PERSON
 File (#200) to use in supported API calls.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: AMPL
SUBSCRIBING PACKAGE: ADVANCED MEDICATION PLATFORM
 SUBSCRIBING DETAILS:   Patch PREA*1*3 exports an option that will be run to
 identify what users will get access to the AMPL application upon rollout to
 each site. Part of that process is to loop on all entries in the NEW PERSON
 File (#200), and use the internal entry number for various API's that are
 already supported.  

NUMBER: 7210                            IA #: 7210
  FILE NUMBER: 63                       GLOBAL ROOT: LR(
  DATE CREATED: NOV 05, 2020            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: LAB DATA RELEASING SITE
  ID: LR(
GLOBAL REFERENCE: LR(D0,'CH',D1,
FIELD NUMBER: .345                      FIELD NAME: RELEASING SITE
  LOCATION: RF;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,'CY',D1,
FIELD NUMBER: .345                      FIELD NAME: RELEASING SITE
  LOCATION: RF;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,'EM',D1,
FIELD NUMBER: .345                      FIELD NAME: RELEASING SITE
  LOCATION: RF;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,'MI',D1,
FIELD NUMBER: .345                      FIELD NAME: RELEASING SITE
  LOCATION: RF;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LR(D0,'SP',D1,
FIELD NUMBER: .345                      FIELD NAME: RELEASING SITE
  LOCATION: RF;1                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This integration agreement grants the subscriber read
 access to all the RELEASING SITE fields in the LAB DATA file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: LAB DATA
KEYWORDS: RELEASING SITE
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   OE/RR displays the potential recipients of the
 PREGNANCY STATUS REVIEW notification via the Determine Recipients for a
 Notification [ORB3 DETERMINE RECIPIENTS] option. When this notification is
 generated by the Clinical Reminders package, the releasing site retrieved from
 the lab result HL7 message is handed off to the Women's Health package to
 generate the list of recipients (ICR #6200 PATIENT'S HEALTHCARE MANAGERS).
 OE/RR needs to hand this same information off to the Women's Health package to 
 properly display the list of recipients.  
  DATE ACTIVATED: NOV 23, 2020

NUMBER: 7211                            IA #: 7211
  DATE CREATED: NOV 30, 2020
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORB3USER                     NAME: ORB3USER APIS
  ID: ORB3USER
 GENERAL DESCRIPTION:   For CPRS v32a development, the GMRA package needs
 access to verify a user is able to receive an alert for a specific
 notification.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORB3USER
KEYWORDS: ONOFF
COMPONENT/ENTRY POINT: ONOFF
 COMPONENT DESCRIPTION:   This Extrinsic function checks the param file to
 determine if a user should receive a notification for a patient.  
VARIABLES: ORN                          TYPE: Input
 VARIABLES DESCRIPTION:   Notification ien from file 100.9 (required) 
VARIABLES: ORBUSER                      TYPE: Input
 VARIABLES DESCRIPTION:   User ien from file 200 (required) 
VARIABLES: ORBPT                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient ien from file 2 (not required) 
VARIABLES: ORBTEAM                      TYPE: Input
 VARIABLES DESCRIPTION:   Processing flag^name for team association with
 ORBUSER (not required) 
VARIABLES: ORNUM                        TYPE: Input
 VARIABLES DESCRIPTION:   Order number to base division params on (not
 required) 
SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING

NUMBER: 7212                            IA #: 7212
  DATE CREATED: DEC 07, 2020            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOBPSU4
  NAME: PSOBPSU4                        ID: PSOBPSU4
 GENERAL DESCRIPTION:   This routine contains a subroutine associated with the
 Bypass 3/4 Day Supply Logic flags in the Prescription file (52) and the Refill
 subfile (52.1) of the Prescription file (52).  
  STATUS: Active
KEYWORDS: FLAG
KEYWORDS: PSOBPSU4
COMPONENT/ENTRY POINT: $$FLAG(PSORX,PSOFILL)
 COMPONENT DESCRIPTION:   This function will return the external value (YES or
 NO) of the Bypass 3/4 Day Supply flag for the given Rx and Fill.  
VARIABLES: PSORX                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the PRESCRIPTION file (#52).  
VARIABLES: PSOFILL                      TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the REFILL multiple (#52.1) in the
 PRESCRIPTION file (#52).  0 represents the original fill of the prescription.  
VARIABLES: $$FLAG                       TYPE: Output
 VARIABLES DESCRIPTION:   The external value (YES or NO) of the Bypass 3/4 Day
 Supply flag.  
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: MAY 05, 2021

NUMBER: 7213                            IA #: 7213
  DATE CREATED: DEC 30, 2020            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOSULB2
  NAME: PSOSULB2                        ID: PSOSULB2
 GENERAL DESCRIPTION:   This routine contains a function, $$EBILLABLE, which
 checks whether a prescription is ebillable (i.e. can be electronically billed
 to a third party payer).  
  STATUS: Active
COMPONENT/ENTRY POINT: $$EBILLABLE(PSORX,PSOFILL)
 COMPONENT DESCRIPTION:   This function will return a '0' if the given Rx/Fill
 is not e-billable.  Otherwise, it will return a '1'.  
VARIABLES: PSORX                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file# 52, Prescription 
VARIABLES: PSOFILL                      TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to sub-file# 52.1, Refill, on file# 52,
 Prescription.  A value should always be passed in for the fill.  For the
 original fill, a value of zero should be passed.  
VARIABLES: $$EBILLABLE                  TYPE: Output
SUBSCRIBING PACKAGE: CMOP
  DATE ACTIVATED: JAN 04, 2021

NUMBER: 7214                            IA #: 7214
  DATE CREATED: JAN 11, 2021            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPFAAH
  NAME: DGPFAAH                         ID: DGPFAAH
 GENERAL DESCRIPTION:   Retrieve list of history IENs for an assignment.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRF
KEYWORDS: OTH
COMPONENT/ENTRY POINT: GETALLDT
VARIABLES: DGPFIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to PRF ASSIGNMENT (#26.13) file (required) 
VARIABLES: DGPFIENS                     TYPE: Both
 VARIABLES DESCRIPTION:   Result array passed by reference (required).  Output
 array subscripted by the assignment IENs 
VARIABLES: $$GETALLDT                   TYPE: Output
 VARIABLES DESCRIPTION:   Count of returned IENs 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   Added 2/18/21 to support Suicide High Risk Patient
 Enhancements Project Phase 2 (SHRPE 2.0), PRCA*4.5*373.  
  DATE ACTIVATED: FEB 02, 2021

NUMBER: 7215                            IA #: 7215
  DATE CREATED: JAN 12, 2021            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LR7OAPKM
  NAME: LR7OAPKM                        ID: LR7OAPKM
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: LOOK
 COMPONENT DESCRIPTION:   Returns the CPRS Screen pointer for a laboratory
 test.  
VARIABLES: LRTST                        TYPE: Input
 VARIABLES DESCRIPTION:   Laboratory Test (File #60 IEN) 
VARIABLES: LRSPEC                       TYPE: Input
 VARIABLES DESCRIPTION:   Specimen (File #61 IEN) 
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   RET(#69.71 IEN)=LR CPRS Parameters Name (#69.71,
 #.01) 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JAN 13, 2021

NUMBER: 7216                            IA #: 7216
  FILE NUMBER: 69.73                    GLOBAL ROOT: LAB(69.73,
  DATE CREATED: JAN 12, 2021            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: File
  NAME: LR AP DIALOG CONFIG             ID: LAB(69.73,
GLOBAL REFERENCE: LAB(69.73,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ALLOW OTHER SPECIMENS
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: RESTRICT MULTIPLE SPECIMEN
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAB(69.73,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: ORDER PROMPT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: HIDE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: REQUIRED
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: DEFAULT
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAB(69.73,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PAGE#
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PAGE NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: HIDE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: REQUIRED
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: RESPONSE ID
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: WP TITLE
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAB(69.73,D0,2,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: PG BLOCK TITLE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: REQUIRED
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: LIST
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: DEFAULT
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAB(69.73,D0,3,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SPECIMEN
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: HIDE FROM DESCRIPTION
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DESCRIPTION POSITION
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAB(69.73,D0,3,D1,2)
FIELD NUMBER: 2.1                       FIELD NAME: COLLECTION SAMPLE HIDE
  LOCATION: 2;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2.2                       FIELD NAME: COLLECTION SAMPLE DEFAULT
  LOCATION: 2;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: LAB(69.73,D0,4)
FIELD NUMBER: 4                         FIELD NAME: PROMPT CHANGE MESSAGE
  LOCATION: 4;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   OE/RR reads and writes from the LR AP DIALOG CONFIG
 file (#69.73) to configure the Delphi forms for CPRS.  
  STATUS: Expired                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JAN 13, 2021

NUMBER: 7217                            IA #: 7217
  FILE NUMBER: 399                      GLOBAL ROOT: DGCR(399
  DATE CREATED: JAN 22, 2021            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA7217
  ID: DGCR(399
GLOBAL REFERENCE: DGCR(399,#,0)
FIELD NUMBER: .08                       FIELD NAME: PTF ENTRY NUMBER
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: .17                       FIELD NAME: PRIMARY BILL
  LOCATION: 0;17                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: DGCR(399,#,S)
FIELD NUMBER: 18                        FIELD NAME: BILL CANCELLED BY
  LOCATION: S;18                        ACCESS: Read w/Fileman
FIELD NUMBER: 19                        FIELD NAME: REASON CANCELLED
  LOCATION: S;19                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This integration agreement allows access to the
 following cross-reference within file 399: 
  
 ^DGCR(399,"C"      use of the "C" cross-reference for patient look-up 
  
 and FileMan access to the fields listed below.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: JAN 22, 2021

NUMBER: 7218                            IA #: 7218
  FILE NUMBER: 350                      GLOBAL ROOT: IB(
  DATE CREATED: JAN 22, 2021            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA7218
  ID: IB(
GLOBAL REFERENCE: IB(D0,0)
FIELD NUMBER: .08                       FIELD NAME: BRIEF DESCRIPTION
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: .09                       FIELD NAME: PARENT CHARGE
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: .1                        FIELD NAME: CANCELLATION REASON
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: .12                       FIELD NAME: AR TRANSACTION NUMBER
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: .18                       FIELD NAME: DATE LAST BILLED
  LOCATION: 0;18                        ACCESS: Read w/Fileman
FIELD NUMBER: .19                       FIELD NAME: IB COPAY TRANSACTION NUMBER
  LOCATION: 0;19                        ACCESS: Read w/Fileman
FIELD NUMBER: .2                        FIELD NAME: CLINIC STOP
  LOCATION: 0;20                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: IB(D0,1)
FIELD NUMBER: 12                        FIELD NAME: DATE ENTRY ADDED
  LOCATION: 1;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: USER LAST UPDATING
  LOCATION: 1;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: DATE LAST UPDATED
  LOCATION: 1;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: IB('AUPD',
 GENERAL DESCRIPTION:   This integration agreement allows FileMan access to the
 fields listed below.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   
  
  
 Modified 8/6/26, effective with patch PRCA*4.5*471.  Added new Index AUPD 
  DATE ACTIVATED: JAN 22, 2021

NUMBER: 7219                            IA #: 7219
  DATE CREATED: JAN 24, 2021
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7219
  STATUS: Pending

NUMBER: 7220                            IA #: 7220
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100
  DATE CREATED: JAN 24, 2021
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: ORDER FILE READ BY CAPRI GUI    ID: OR(100
 GENERAL DESCRIPTION:   CAPRI GUI has the need to read File 100 for upgrade to
 the Order Builder option within the GUI to display information for Patient
 Orders 
  STATUS: Pending
KEYWORDS: CAPRI GUI
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE

NUMBER: 7221                            IA #: 7221
  FILE NUMBER: 340.5                    GLOBAL ROOT: RCRP(340.5
  DATE CREATED: JAN 28, 2021            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: IB ACCESS TO AR REPAYMENT PLAN FILE
  ID: RCRP(340.5
GLOBAL REFERENCE: RCRP(340.5,D0,0
FIELD NUMBER: .01                       FIELD NAME: REPAYMENT PLAN ID
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DEBTOR
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: START DATE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: AMOUNT PER MONTH
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: NO. OF PAYMENTS
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: .11                       FIELD NAME: PLAN AMOUNT OWED
  LOCATION: 0;11                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RCRP(340.5,D0,3,D1,0
FIELD NUMBER: .01                       FIELD NAME: DATE OF PAYMENT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: AMOUNT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TRANSACTION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RCRP(340.5,D0,2,D1,0
FIELD NUMBER: .01                       FIELD NAME: PLAN DUE DATE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PAYMENT MADE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: PAYMENT FORBORNE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This ICR allows Integrated Billing to access data in
 the AR REPAYMENT PLAN file (#340.5) for the following reports: 
  
 1. First Party Follow-up Report [IBJD FOLLOW-UP FIRST PARTY] 
  
 2. Repayment Plan Follow-up Report [IBJD FOLLOW-UP REPAYMENT PLAN] 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: REPAYMENT PLAN
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAY 05, 2021

NUMBER: 7222                            IA #: 7222
  DATE CREATED: FEB 02, 2021            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOERXU9
  NAME: PSOERXU9                        ID: PSOERXU9
 GENERAL DESCRIPTION:   The routine PSOERXU9 has entry points to return a
 pointer to the ERX HOLDING QUEUE file (#52.49) based on a PRESCRIPTION IEN or
 PENDING OUTPATIENT ORDER IEN, return a pointer to the ERX HOLDING QUEUE file 
 (#52.49) based on an ORDER IEN, and return data from the ERX HOLDING QUEUE 
 file (#52.49) based on the ERX HOLDING QUEUE IEN.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSOERXU9
COMPONENT/ENTRY POINT: $$ERXIEN(RXIEN)
 COMPONENT DESCRIPTION:   This entry point returns a pointer to the ERX HOLDING
 QUEUE file (#52.49) based on a PRESCRIPTION IEN or PENDING OUTPATIENT ORDER
 IEN.  
VARIABLES: RXIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Input parameter - PENDING OUTPATIENT ORDERS file
 (#52.41) IEN (e.g., "139839P") or PRESCRIPTION file (#52) IEN (e.g.,
 12930984).  
VARIABLES: $$ERXIEN                     TYPE: Output
 VARIABLES DESCRIPTION:   Pointer to the ERX HOLDING QUEUE file (#52.49) or ""
 (Not an eRx prescription).  
COMPONENT/ENTRY POINT: $$ERXCHK(ORDERIEN)
 COMPONENT DESCRIPTION:   This entry point returns a pointer to the ERX HOLDING
 QUEUE file (#52.49) based on an ORDER IEN.  
VARIABLES: ORDERIEN                     TYPE: Input
 VARIABLES DESCRIPTION:   Input parameter - ORDER (#100) file IEN.  
VARIABLES: $$CHKERX                     TYPE: Output
 VARIABLES DESCRIPTION:   Pointer to the ERX HOLDING QUEUE file (#52.49) or 0
 (Not an eRx prescription).  
COMPONENT/ENTRY POINT: ERXDATA(ERXDATA,ERXIEN)
 COMPONENT DESCRIPTION:   This entry point returns data from the ERX HOLDING
 QUEUE file (#52.49), ERX EXTERNAL PHARMACY file (#52.47), ERX EXTERNAL PERSON
 file (#52.48), and ERX EXTERNAL PATIENT file (#52.46); based on the ERX
 HOLDING QUEUE (#52.49) IEN.  
VARIABLES: ERXIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   Input parameter - ERX HOLDING QUEUE file (#52.49)
 IEN.  
VARIABLES: ERXDATA                      TYPE: Output
 VARIABLES DESCRIPTION:   The ERXDATA array, passed by reference, returns data
 from the ERX HOLDING QUEUE file (#52.49), ERX EXTERNAL PHARMACY file (#52.47),
 ERX EXTERNAL PERSON file (#52.48), and ERX EXTERNAL PATIENT file (#52.46) to
 be used for Controlled Substance reports.  
  
 ERXDATA(1)=null^eRxReceivedDate(FileMan)^eRxDrugName^ 
            VistaDrugIEN^ CSdrugSchedule^ 
            eRxQuantity^eRxRefill^eRxHubID 
 ERXDATA(2)=providerDEA#^null^providerName^providerDUZ 
 ERXDATA(3)=null^provStreet1^provCity^provState^ 
            provZip ERXDATA(4)=patientName^patientDFN 
 ERXDATA(5)=patStreet1^patStreet2^null^patCity^ 
            patState^patZip^patDOB(MM/DD/YYYY) 
SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES
 SUBSCRIBING DETAILS:   Controlled Substance reports require data from the ERX
 HOLDING QUEUE file (52.49).  
  DATE ACTIVATED: FEB 16, 2021

NUMBER: 7223                            IA #: 7223
  DATE CREATED: FEB 04, 2021
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMRCGUIB
  NAME: TIU CALLS TO GMRCGUIB           ID: GMRCGUIB
 GENERAL DESCRIPTION:   The Community Care Referrals and Authorization (CCRA)
 project is sending clinical notes that are to filed with a community care
 consult request. When the notes are filed, a comment is being added to the
 activity log in the consult. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMRCGUIB
COMPONENT/ENTRY POINT: SETDA
 COMPONENT DESCRIPTION:   Returns the next DA value to be used to file a new
 entry in the consult's activity log.  
VARIABLES: GMRCO                        TYPE: Input
 VARIABLES DESCRIPTION:   Contains the internal entry number of the consult in
 the REQUEST/CONSULTATION FILE (#123).  
COMPONENT/ENTRY POINT: SETCOM
 COMPONENT DESCRIPTION:   Files the comment in the consult's activity log.  
VARIABLES: GMRCO                        TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number for the consult in the
 REQUEST/CONSULTATION FILE (#123).  
VARIABLES: COMMENT                      TYPE: Input
 VARIABLES DESCRIPTION:   The free text comment that is to be filed.  
VARIABLES: WHO                          TYPE: Input
 VARIABLES DESCRIPTION:   The user adding the comment. 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   The CCRA TIU filer makes a call to the SETDA^GMRCGUIB
 API to get the DA value for the new comment that is added to the consult when
 filing a new CCRA TIU note.  
  
 The CCRA TIU filer then makes a call to the SETCOM^GMRCGUIB API to file the
 new comment in the consult's activity log.  
  DATE ACTIVATED: MAR 03, 2021

NUMBER: 7224                            IA #: 7224
  DATE CREATED: FEB 04, 2021
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMRCP
  NAME: TIU CALL TO GMRCP               ID: GMRCP
 GENERAL DESCRIPTION:   The Community Care Referrals and Authorization (CCRA)
 project is sending clinical notes that are to filed with a community care
 consult request. When the notes are filed, the CPRS STATUS of the consult is
 reset.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMRCP
COMPONENT/ENTRY POINT: STATUS
 COMPONENT DESCRIPTION:   Set the CPRS STATUS field in the REQUEST/CONSULTATION
 FILE (#123).  
VARIABLES: GMRCSTS                      TYPE: Input
 VARIABLES DESCRIPTION:   The status to set the CPRS STATUS to.  
VARIABLES: GMRCDA                       TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the consult in the
 REQUEST/CONSULTATION FILE (#123).  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   The CCRA TIU filer then makes a call to the
 STATUS^GMRCP API to set the CPRS STATUS field in the REQUEST/CONSULTATION FILE
 (#123).  
  DATE ACTIVATED: MAR 03, 2021

NUMBER: 7225                            IA #: 7225
  DATE CREATED: FEB 11, 2021
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUPREF
  NAME: Calls to TIUPREF                ID: TIUPREF
 GENERAL DESCRIPTION:   This DBIA documents calls to TIUPREF.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIUPREF
KEYWORDS: REQDFLD
COMPONENT/ENTRY POINT: REQDFLD(VAL,ACTION,INPUT)
 COMPONENT DESCRIPTION:   Returns or Saves the Template Required Fields (.21,
 .22, and .23) of the TIU PERSONAL PREFERENCES (#8926) file.  
VARIABLES: VAL                          TYPE: Output
 VARIABLES DESCRIPTION:   The return depends on the ACTION parameter received: 
 IF ACTION = LDPREF THEN: 
   HIGHLIGHT ON^HIGHLIGHT COLOR^NAVIGATION LOCATION 
  
 IF ACTION = SVPREF THEN: 
   1 = Success 
   0 = Failure 
VARIABLES: ACTION                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the action to complete.  It will contain one
 of two values, "LDPREF" or "SVPREF".  These must be sent exactly in order for
 the action to take place.  
VARIABLES: INPUT                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the template required fields preferences to
 be saved.  When ACTION parameter contains LDPREF, then this value must be
 included.  
  
   HIGHLIGHT ON^HIGHLIGHT COLOR^NAVIGATION LOCATION 
  
   HIGHLIGHT ON = 1 (ON) OR 0 (OFF) 
   HIGHLIGHT COLOR = A NUMBER REPRESENTING THE 
     COLOR FOR HIGHLIGHTS 
   NAVIGATION LOCATION = THIS IS THE LOCATION OF 
     THE NAVIGATION CONTROLS USED TO MOVE BETWEEN 
     REQUIRED FIELDS.  
       1 = TOP, 2 = LEFT, 3 = RIGHT, 4 = BOTTOM 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   CPRS (OE/RR) needs to make a call to the
 REQDFLD^TIUPREF routine to set or retrieve the values stored in the USE
 TEMPLATE REQD FLD HLITE (.21), TEMPLATE REQD FLD HLITE COLOR (.22), and
 TEMPLATE REQD FLD NAV LOCATION (.23) fields which are being introduced in CPRS
 32A (OR*3.0*539).  The CPRS GUI uses an RPC to retrieve/save the user
 preferences.  
  DATE ACTIVATED: FEB 19, 2021

NUMBER: 7226                            IA #: 7226
  DATE CREATED: FEB 11, 2021
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Other
  NAME: OR OTH Button Add/Edit Local Message
 GENERAL DESCRIPTION:   Add/Edit Local Messge for OTH Button in CPRS GUI 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: OTH
COMPONENT/ENTRY POINT: OR OTH BTN LOCAL MSG
 COMPONENT DESCRIPTION:   Lookup entry in ^XTV(8989.51,"C","OR OTH BTN LOCAL
 MSG") to retrieve Local Message Text, which is optional.  Once the IEN for the
 entry is found from the lookup, that IEN will be used to retrieve the 20 node
 of the PARAMETER DEFINITION File(#8989.51).  Example: Lookup returns IEN value
 of 1066.  Subsequent lookup in ^XTV(8989.51,1066,20) will return any
 associated text under that multiple entry.  Up to 2 lines of text can be set,
 so a maximum of 2 lines will be returned.  ^XTV(8989.51,IEN,20,1,0) and 
 ^XTV(8989.51,IEN,20,2,0).  
SUBSCRIBING PACKAGE: REGISTRATION

NUMBER: 7227                            IA #: 7227
  DATE CREATED: FEB 12, 2021            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOSIG
  NAME: PSOSIG                          ID: PSOSIG
 GENERAL DESCRIPTION:   This call, provided by Outpatient Pharmacy, will return
 the expanded version of an ADMINISTRATION SCHEDULE. For example, a schedule of
 BID will return TWICE A DAY or a schedule TU will return TUESDAY.  
  STATUS: Active
KEYWORDS: EXPAND
KEYWORDS: EXPANSION
KEYWORDS: SCHEDULE
COMPONENT/ENTRY POINT: SCHE
 COMPONENT DESCRIPTION:   Returns the expanded version of a pharmacy schedule.  
VARIABLES: SCH                          TYPE: Input
 VARIABLES DESCRIPTION:   Schedule. For example, BID 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Returns the expanded schedule 
    Y=$$SCHE^PSOSIG("BID") 
    Y="TWICE A DAY" 
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  DATE ACTIVATED: JUN 07, 2021

NUMBER: 7228                            IA #: 7228
  FILE NUMBER: 350.9                    GLOBAL ROOT: IBE(350.9
  DATE CREATED: FEB 17, 2021            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SHRPE ACTIVATION DATE
  ID: IBE(350.9
GLOBAL REFERENCE: IBE(350.9,D0,70
FIELD NUMBER: 70.02                     FIELD NAME: SHRPE ACTIVATION DATE
  ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the date that legislation was passed to allow
 visit copayment exemption and prescription prorated amount for patients with 
 the High Risk for Suicide flag. 
 GENERAL DESCRIPTION:   Accounts Receivable application needs to read the SHRPE
 activation date stored in the Integrated Billing file (#350.9) to determine
 when copays exemption rules and prorated RX copay amounts for patients with
 the High Risk for Suicide flag become applicable.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SHRPE
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
  DATE ACTIVATED: MAR 09, 2021

NUMBER: 7229                            IA #: 7229
  FILE NUMBER: 26.13                    GLOBAL ROOT: DGPF(26.13
  DATE CREATED: FEB 24, 2021            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DBIA7229
  ID: DGPF(26.13
 GENERAL DESCRIPTION:   ^DGPF(26.13,"C" use of the "C" cross-reference for
 patient look-up.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRF
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 1/14/2022, effective with DSSV*1.0*1 DSS Class 3
 product Document Only 
  DATE ACTIVATED: MAR 12, 2021

NUMBER: 7230                            IA #: 7230
  DATE CREATED: FEB 25, 2021            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: Routine
  ROUTINE: RCRPSTR                      NAME: REPAYMENT PLAN STATUS REPORT
  ID: RCRPSTR
 GENERAL DESCRIPTION:   Integrated Billing needs access to the new Repayment
 Plan Status report [PRCAC PLAN STATUS REPORT] in the Diagnostic Measures
 Follow-up Reports Menu as a replacement to the retired (as of PRCA*4.5*378)
 REPAYMENT PLAN FOLLOW-UP REPORT [IBJD FOLLOW-UP REPAYMENT PLAN].  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: REPORT
KEYWORDS: REPAYMENT
COMPONENT/ENTRY POINT: EN
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 7231                            IA #: 7231
  DATE CREATED: FEB 26, 2021
  CUSTODIAL PACKAGE: ELECTRONIC HEALTH MODERNIZATION
  USAGE: Supported                      TYPE: Routine
  ROUTINE: EHMUHLV                      NAME: CERNER NAK ERROR LOG
  ID: EHMUHLV
 GENERAL DESCRIPTION:   This integration agreement allows other packages to
 call the supported routine ADD2LOG^EHMUHLV.  If any interface that is sending
 messages to/from Cerner receives a NAK, this API will need to be called in
 order to send an email back to Cerner users stating what error occurred.  
  
 Six possible parameters need to be passed in to the API: 
  
 ADD2LOG(TYPE,INTERFACE,MESSAGE,SEVERITY,CIDNUM,SOURCE) 
  
  TYPE (Required) = Severity of the log entry 
   'E' FOR ERROR Record could not be processed 
   'W' FOR WARNING Record was processed but should be reviewed 
   'D' FOR DATA DEFAULTED A default value was substituted before processing 
       the record 
  
   INTERFACE (Required) = Interface that generated the log entry 
  
   MESSAGE (Required) = Reason for log entry 
     (may refer to a segment or field) 
  
   SEVERITY (Required) = Severity of the error 
   'H' FOR HIGH failure requires immediate attention 
   'M' FOR MEDIUM failure is important, but not critical 
   'L' FOR LOW log entry can be researched over time 
   'I' FOR EH log entry is informational only 
  
   CIDNUM (Required) = Cerner ID Number 
  
   SOURCE (Optional) = Source of log entry. Should contain HL7 full message if
 needed 
  STATUS: Under Revision
KEYWORDS: 1605
KEYWORDS: EHMLOG
KEYWORDS: EHMUHLV
COMPONENT/ENTRY POINT: ADD2LOG
 COMPONENT DESCRIPTION:   This will add a log entry to the Cerner-VistA Message
 Log FILE (#1605).  
  
 Returns the pointer to File (#1605) if successful or 0^error message if 
 unsuccessful.  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Severity of the log entry.  
   'E' FOR ERROR              Record could not be processed 
   'W' FOR WARNING            Record was processed but should be reviewed 
   'D' FOR DATA DEFAULTED     A default value was substituted before 
                                processing the record 
VARIABLES: INTERFACE                    TYPE: Input
 VARIABLES DESCRIPTION:   This is a required field and will contain the
 interface that generated the log entry.  
VARIABLES: MESSAGE                      TYPE: Input
 VARIABLES DESCRIPTION:   This is a required field and will contain the reason
 for the log entry (may refer to a segment or a field).  
VARIABLES: SEVERITY                     TYPE: Input
 VARIABLES DESCRIPTION:   This is a required field and contains the severity of
 the error.  
  
  'H' FOR HIGH 
  'M' FOR MEDIUM 
  'L' FOR LOW 
  'I' FOR INFORMATIONAL ONLY 
  
 Enter HIGH if the failure requires immediate attention, MEDIUM if the failure
 is important but not critical, LOW if the log entry can be researched over
 time and INFO if the log entry is informational only.  
VARIABLES: CIDNUM                       TYPE: Input
 VARIABLES DESCRIPTION:   This is a required field that contains the Cerner
 Identification Number.  
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   This field is optional.  Should contain HL7 full
 message if needed.  
  DATE ACTIVATED: MAR 03, 2021

NUMBER: 7232                            IA #: 7232
  DATE CREATED: MAR 04, 2021            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: SCHEDULED ADMISSIONS FILE ENTRY NOTIFIER
 GENERAL DESCRIPTION:   The DG SA FILE ENTRY NOTIFIER protocol will notify
 subscribers when an entry in the SCHEDULED ADMISSION (#41.1) file is created,
 modified, or deleted.  The protocol is fired by a FileMan cross-reference on
 the SCHEDULED ADMISSION file. End-user options that ultimately invoke this
 protocol include: 
  DG SCHED ADMIT CANCEL 
  DG SCHED ADMIT ENTRY 
  DG SCHED ADMIT PURGE 
  
  The following data is available to subscribers: 
   
  ^TMP("DG SA FILE ENTRY NOTIFIER",$J","ACTION")=ACTION 
    ACTION: The action that was taken on the entry. Possible values are 
            "CREATED", "MODIFIED" and "DELETED".  
   
  ^TMP("DG SA FILE ENTRY NOTIFIER",$J,"DATE")=DATE 
    DATE: FileMan date/time (internal format) of when the activity occurred.  
   
  ^TMP("DG SA FILE ENTRY NOTIFIER",$J,"DFN","CURRENT")=DFN 
    DFN: Internal Entry Number (IEN) of the patient in the PATIENT file 
         (#2). This is the patient the entry points to after the change.  
   
  ^TMP("DG SA FILE ENTRY NOTIFIER",$J,"DFN","OLD")=DFN 
    DFN: Internal Entry Number (IEN) of the patient in the PATIENT file 
         (#2). This is the patient the entry pointed to before the change.  
   
  ^TMP("DG SA FILE ENTRY NOTIFIER",$J,"FIELDS",NAME)="" 
    NAME: When the ACTION is "MODIFIED", the "FIELDS" subscript is 
          created. Nodes descendant from the "FIELDS" subscript are the 
          field number of the field(s) that were edited.  
   
  ^TMP("DG SA FILE ENTRY NOTIFIER",$J,"IEN")=IEN 
    IEN: Internal Entry Number (IEN) of the affected entry. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DG SA FILE ENTRY NOTIFIER
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Attached the VPR DGS EVENTS protocol, effective with
 VPR*1*27 
  DATE ACTIVATED: AUG 25, 2021

NUMBER: 7233                            IA #: 7233
  DATE CREATED: MAR 15, 2021            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: VAFCTFU2                     NAME: VAFC LOCAL GETCORRESPONDINGIDS
  ID: VAFCTFU2
 GENERAL DESCRIPTION:   Community Care Referrals and Authorization (CCRA)
 project has been tasked with sending the EDIPI with consult requests
 transmitted to the HealthShare Referral Manager. 
  
 These patient ids will be displayed by HSRM and some, including the EDIPI,
 will be displayed on the printed offline referral form generated by HSRM. They
 are used by community care staff to look-up veteran information on other
 systems.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: CCRA
KEYWORDS: VAFC
KEYWORDS: TFL
COMPONENT/ENTRY POINT: TFL
 COMPONENT DESCRIPTION:   The patient identifier will either be the PATIENT
 file (#2) IEN (aka DFN), Integration Control Number (aka ICN) or the DOD
 Identifier (aka EDIPI).  Following this format: 
      
  
 ID^IDTYPE^AssigningAuthority^AssigningFacility 
      
 Examples: ICN example:   1008520438V882204^NI^USVHA^200M DFN example:  
 100000511^PI^USVHA^500 EDIPI example: 852043888^NI^USDOD^200DOD 
      
 This will return a list of Treating Facilities in this format: 
      
 ID^IDTYPE^AssigningAuthority^AssigningFacility^IDStatus 
      
  Examples: 
  RETURN(1)="27^PI^USVHA^500^H" 
  RETURN(2)="7169806^PI^USVHA^500^A" 
  RETURN(3)="^PI^USVHA^200PS" 
  RETURN(4)="1^NI^USDOD^200DOD^A" 
  RETURN(5)="2^NI^USDOD^200DOD^H" 
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING

NUMBER: 7234                            IA #: 7234
  DATE CREATED: MAR 19, 2021            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: BARCODE PRINT SITE DEFINED LABEL
 GENERAL DESCRIPTION:   Above PAR requests permission to perform the site
 specific label print as defined in ENGINEERING COMPUTER PORT FILE ACCESS
 (#6910.1) fields; 
       BAR CODE EQUIPMENT FORMAT (#3) 
       BAR CODE LOCATION FORMAT (#4) 
       BAR CODE EQUIPMENT DATA (#5) 
       BAR CODE LOCATION DATA (#6) 
  
 The label routines defined in these four fields require that standard 
 processing variables be defined prior to running the routine. The variables
 would be those defined in ENLBL3 and/or ENLBL7.  These variables include; 
       DA         Equipment IEN (#6914) 
       ENEQBC     Label Data 
       ENEQLM     Size Limit 
       ENEQSTA    Station 
       ENEQSTAN   Station Name 
       ENELBLBOT  Label Bottom 
       ENLBLHD    Label Header 
       ENBCIO     IO Device (Printer) 
       ENBCIOS    Device File (#3.5) IEN 
       ENEQBY     Label Format 
  
 Example of Equipment custom label print 
      BAR CODE EQUIPMENT FORMAT - D FORMAT2^ADBWLBL7 
      BAR CODE EQUIPMENT DATA   - D FULL^ADBWLBL7 
  STATUS: Active
KEYWORDS: APAR
KEYWORDS: ABOVE PAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: MAR 31, 2021

NUMBER: 7235                            IA #: 7235
  DATE CREATED: MAR 22, 2021            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCH0A
  NAME: ET DDA Segments for PC Charge and PC Order
  ID: PRCH0A
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call IFCAP APIs for building the DDA
 segment for the Purchase Card Charge and the DDA for the Purchase Card Order. 
 The DDAs are then compared to determine if an ET transaction needs to be
 generated to correct the accounting string for the charge's expense in FMS.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
KEYWORDS: ADVANCED PROSTHETICS ACQ TOOL
COMPONENT/ENTRY POINT: $$DDA4406(PRCA)
 COMPONENT DESCRIPTION:   This component returns the value of the DDA segment  
 for the Purchase Card Charge.  
VARIABLES: PRCA                         TYPE: Input
 VARIABLES DESCRIPTION:   PURCHASE ORDER RECONCILE (440.6) file IEN 
VARIABLES:                              TYPE: Output
 VARIABLES DESCRIPTION:   DDA Segment for Purchase Card Charge 
COMPONENT/ENTRY POINT: $$DDA442(PRCA)
 COMPONENT DESCRIPTION:   This component returns the value of the DDA segment 
 for the Purchase Card Order.  
VARIABLES: PRCA                         TYPE: Input
 VARIABLES DESCRIPTION:   PROCUREMENT & ACCOUNTING TRANSACTIONS (#442) file IEN 
VARIABLES:                              TYPE: Output
 VARIABLES DESCRIPTION:   DDA Segment for Purchase Card Order 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: APR 20, 2021

NUMBER: 7236                            IA #: 7236
  DATE CREATED: MAR 22, 2021            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCH8A
  NAME: AUTO-GENERATE FMS ET-DOCUMENTS  ID: PRCH8A
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRCH8A to 
 auto-generate a Financial Management System (FMS) Expenditure Transfer
 (ET)-document.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ADVANCED PROSTHETICS ACQ TOOL
KEYWORDS: APAT
COMPONENT/ENTRY POINT: ET(.X,PRCFC,PRCID)
 COMPONENT DESCRIPTION:   ET Auto Document 
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   First ^-piece:   IEN of the GENERIC CODE SHEET 
                  STACK #2100.1 entry created 
                  from successful call to the 
                  Generic Code Sheet package 
  
 Second ^-piece:  ET Document ID 
VARIABLES: PRCFC                        TYPE: Input
 VARIABLES DESCRIPTION:   First ^-piece:  PURCHASE CARD ORDER RECONCILE 
                 #440.6 file IEN 
  
 Second ^-piece: PROCUREMENT & ACCOUNTING 
                 TRANSACTIONS #442 file IEN 
  
 Third ^-piece: 
   =1 - if a reconciliation is being done and 
        the expense in FMS should be reassigned 
        from the accounting string sent to FMS 
        in the charge transaction to the budget 
        string of the Purchase Card Order.  Thus, 
        decrease the allocation to the charge's 
        budget string and increase the allo- 
        cation to the PC Order's budget string.  
  
   =2 - if the reconciliation is being removed 
        and the expense should be reassigned to 
        the budget string of the charge trans- 
        action and removed from the PC Order's 
        budget string.  Thus, decrease the allo- 
        cation to the PC Order's budget string 
        and increase the allocation to the 
        charge's budget string.  
VARIABLES: PRCID                        TYPE: Input
 VARIABLES DESCRIPTION:   This parameter is populated for the API call when the
 user is attempting to turn around (regenerate) a rejected ET.  
  
 First ^-piece:  GENERIC CODE SHEET STACK #2100.1 
                 file IEN 
  
 Second ^-piece: ET Document ID (if regenerated) 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: APR 21, 2021

NUMBER: 7237                            IA #: 7237
  FILE NUMBER: 420.3                    GLOBAL ROOT: PRCD(420.3,
  DATE CREATED: MAR 22, 2021            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PRCD FUND/APPROPRIATION CODE FILE ACCESS
  ID: PRCD(420.3,
GLOBAL REFERENCE: PRCD(420.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: FUND
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: REVOLVING FUND
  LOCATION: 0;8                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PRCD(420.3,'B'
 GLOBAL DESCRIPTION:   'B' cross reference - used to look up the file #420.3
 entry 
                       based on FUND (#.01) value 
 GENERAL DESCRIPTION:   The Advanced Prosthetics Acquisition Tool (APAT)
 requests permission to read the PRCD FUND/APPROPRIATION CODE FILE (#420.3)
 file when reconciling purchase card orders.  APAT will look up the Fund entry
 in file #420.3 using the "B" cross reference in order to determine if the fund
 is a revolving fund based on the entry's value in the YES/NO field REVOLVING 
 FUND (#7).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ADVANCED PROSTHETICS ACQ TOOL
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: APR 20, 2021

NUMBER: 7238                            IA #: 7238
  DATE CREATED: APR 01, 2021            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Other
  NAME: IB BILLING CLERK MENU Option
 GENERAL DESCRIPTION:   Communication ICR: The RPA Revenue Operations Project
 developers have created a Robotic solution to replace a specific set of IB
 Clerk option steps to determine whether a patient should be billed.  The RPA
 BOT project was written to utilize exact prompts available to a clerk, 
 starting with the IB BILLING CLERK MENU option, which is the target option for
 this ICR. 
  
 Background for project: The RPA Revenue Operations Project was approved by 
 upper management for two bots to run a script to login (through WebVRAM) and
 then go to specific sites and run a couple IB and Accounts Receivable 
 reporting options.  The output of the first report is stored in a cloud and
 converted to excel as part of the bot processing from the first report run. 
 Then the second option script is run, using the patients in the first report
 output to correct the billing status based on the Service Connected
 information.  
  
 This ICR is a request for IB package developers to communicate with the RPA
 Project Manager (PM) when a patch that changes prompts related to the IB
 BILLING CLERK MENU option is within a month from going to IOC.  This 
 communication will help the RPA PM plan actions to minimize the impact on the
 RPA robotic functionality implemented at a site. The IB developers do not need
 to hold up the IB Agile development (IOC and release) to wait for the RPA BOT
 project to make software changes.  
  
 The IB developers agree to provide the RPA BOT project manager with details
 about what has changed so the RPA BOT Team can assess impact and plan to
 coordinate changes to their product. 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: RPA
KEYWORDS: BOT
KEYWORDS: COMMUNICATION

NUMBER: 7239                            IA #: 7239
  DATE CREATED: APR 01, 2021            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Other
  NAME: IB CANCEL/EDIT/ADD CHARGES Option
 GENERAL DESCRIPTION:   duplicate from 7238 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: RPA
KEYWORDS: BOT
KEYWORDS: Communication ICR

NUMBER: 7240                            IA #: 7240
  DATE CREATED: APR 01, 2021            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: Other
  NAME: RCDMCR6 50-100SC EXMPT RPT Option
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 7241                            IA #: 7241
  DATE CREATED: APR 01, 2021            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: Other
  NAME: RCDMCR7 10-40% COPAY RPT Option
  STATUS: Pending

NUMBER: 7242                            IA #: 7242
  DATE CREATED: APR 06, 2021
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7242
  STATUS: Pending

NUMBER: 7243                            IA #: 7243
  DATE CREATED: APR 07, 2021            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGOTHFSM
  NAME: ACCESS TO THE OTH REPORT        ID: DGOTHFSM
 GENERAL DESCRIPTION:   The INTEGRATED BILLING package needs to run the
 REGISTRATION report implemented as MAIN^DGOTHFSM modified in the patch
 DG*5.3*1047 to display information for INTEGRATED BILLING (IB) users.  This
 report identifies Former Service Members whose Primary Eligibility changed
 from EXPANDED MH CARE NON-ENROLLEE to a new Primary Eligibility with a
 VERIFIED eligibility status. These patients are no longer treated under the
 Other Than Honorable (OTH) authority (VHA Directive 1601A.02). 
  
 This agreement grants the IB menu option Former OTH Patient Eligibility Change
 Report [IB OTH FSM ELIG. CHANGE REPORT] a permission to run MAIN^DGOTHFSM
 entry point that allows IB users to see additional information related to MST
 (Military Sexual Trauma) screening results.  
  
 The new IB menu option Former OTH Patient Eligibility Change Report [IB OTH
 FSM ELIG. CHANGE REPORT] is introduced by the patch IB*2.0*701.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OTH
COMPONENT/ENTRY POINT: MAIN
 COMPONENT DESCRIPTION:   Set IBMST variable to 1 in the ENTRY ACTION field of
 the IB report menu option to allow IB users to see additional information
 related to MST ((Military Sexual Trauma) screening results.  
  
 Listed below are the data elements displayed in the report: 
  PATIENT NAME               File (#2),field (#.01) 
  DATE OF BIRTH              File (#2),field (#.03) 
  PID                        File (#2),field (#.0905) 
  OTH REG DATE               File (#33), subfile(#33.02),field (#.01) 
  NEW ELIGIBILITY CODE       File (#2),field (#.361) 
  CURRENT MST SCREEN STATUS  File (#29.11),field (#3) 
    Note: This column will be displayed only to IB users, not 
          Registration users.  
  SC%                        File (#2),field (#.302) 
  ELIGIBILITY CHANGE DATE    File (#2),field (#.3612) 
  STATION                    File (#4),field (#99) 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: APR 15, 2021

NUMBER: 7244                            IA #: 7244
  DATE CREATED: APR 08, 2021            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XUS MVI NEW PERSON RMTE AUDIT
  REMOTE PROCEDURE: XUS MVI NEW PERSON RMTE AUDIT
 GENERAL DESCRIPTION:   In support of the ongoing work of implementing
 Enterprise User Identity, the Master Veteran Index (MVI) team requests
 permission to exclusively use the following restricted KERNEL Remote Procedure
 Call (RPC) [XUS MVI NEW PERSON RMTE AUDIT] to allow retrieval of the audit
 history for a specific user's record in the NEW PERSON (#200) file at the 
 specified facility for viewing. This retrieved audit information will be used
 to assist in troubleshooting issues with a user's account and for determining
 how/when and ultimately why the record was changed if needed.  This restricted
 RPC is to be used exclusively by the Master Veteran Index (MVI) to
 review/display the requested audit history of a user's record in the NEW
 PERSON (#200) file at a specific facility.  
  
 TAG: AUDIT        ROUTINE: XURNPAUD 
  
 Parameters: 
      PARAM("SourceSystemID") [Required] - Facility Station Number 
      PARAM("SourceID")       [Required] - Individual's DUZ 
      PARAM("BegDate")        [Optional] - Earliest date of Audit records  
                                           to return 
      PARAM("EndDate")        [Optional] - Last date of Audit records to 
                                           return 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XUS MVI NEW PERSON RMTE AUDIT
KEYWORDS: 200
KEYWORDS: VA(200
KEYWORDS: XURNPAUD
KEYWORDS: MVI
KEYWORDS: MPI
KEYWORDS: NEW PERSON
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   The Master Veteran Index (MVI) project beginning with
 patch MPI*1.0*142 will use this Remote Procedure Call (RPC) to remotely
 retrieve the audit data from the AUDIT (#1.1) file at a facility for a
 specific user's record in the NEW PERSON (#200) file so that it can be
 displayed/reviewed.  See associated IA #2602 for KERNEL access to the AUDIT
 (#1.1) file. 
  DATE ACTIVATED: APR 09, 2021

NUMBER: 7245                            IA #: 7245
  DATE CREATED: APR 13, 2021
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORWORB                       NAME: Retrieve XQADATA from an alert
  ID: ORWORB
 GENERAL DESCRIPTION:   Returns XQADATA for a given alert XQAID 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ORWORB
KEYWORDS: GETDATA
COMPONENT/ENTRY POINT: GETDATA
 COMPONENT DESCRIPTION:   Returns a XQADATA for a given alert XQAID 
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   This returns the alert XQADATA as a string.  
VARIABLES: XQAID                        TYPE: Input
 VARIABLES DESCRIPTION:   XQAID is the alert identifier 
VARIABLES: PFLAG                        TYPE: Input
 VARIABLES DESCRIPTION:   If set to 1 then retrieval of data is directly from
 the alert file. Else if set to 0 or not passed in then the retrieval of data
 is from an alert API.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 7246                            IA #: 7246
  DATE CREATED: APR 13, 2021            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: WVALERTR
  NAME: GET RADIOLOGY CASE INFO FROM WOMEN'S HEALTH
  ID: WVALERTR
 GENERAL DESCRIPTION:   This API returns the following information for a given
 IEN from file 790.1.  
  
 Primary Diagnosis Code from Radiology IENS to link to the Radiology entry from
 file 70 that links to the report entry.  Report IEN from file 74 Secondary
 Diagnosis is an array of secondary diagnosis entered when verifying a
 radiology report.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: WV
KEYWORDS: RADCASE
KEYWORDS: WVALERTR
COMPONENT/ENTRY POINT: RADCASE
 COMPONENT DESCRIPTION:   This entry point returns information about the
 Radiology Report based off an IEN from 790.1 
VARIABLES: WVIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN from file 790.1 
VARIABLES: DIAGNS                       TYPE: Output
 VARIABLES DESCRIPTION:   This variable returns the primary diagnostic code for
 the radiology report.  
VARIABLES: WVIENS                       TYPE: Output
 VARIABLES DESCRIPTION:   WVIENS returns the IENS string for the entry in file
 70 in the following format: 
  "CASE,DTE,DFN" 
  
 CASE = Case Number DTE  = FileMan Date Time DFN  = Patient DFN 
VARIABLES: WVRPTIEN                     TYPE: Output
 VARIABLES DESCRIPTION:   This variable returns the IEN for the Radiology
 Report from file 74.  
VARIABLES: WVSECDXS                     TYPE: Output
 VARIABLES DESCRIPTION:   This an array of secondary diagnosis entered when
 verifying a radiology report.  
COMPONENT/ENTRY POINT: RADREP
 COMPONENT DESCRIPTION:   This entry returns the radiology report from file 74
 and information from file 70 in text format in the ^TMP("WV RPT",$J).  
VARIABLES: RPTCASE                      TYPE: Input
 VARIABLES DESCRIPTION:   RPTCASE is the IENS for the entry in file 70 in the
 following format.  
  
 "CASE,DTE,DFN" 
                             
 CASE = Case Number, DTE  = FileMan Date Time,  DFN  = Patient DFN 
VARIABLES: RPTIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN for the Radiology Report from file 74.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: APR 13, 2021

NUMBER: 7247                            IA #: 7247
  DATE CREATED: APR 16, 2021            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMEUT
  NAME: PXRMEUT                         ID: PXRMEUT
 GENERAL DESCRIPTION:   The purpose of this Integration Control Registration is
 to grant Order Entry/Results Reporting access to the ASKYN linetag in the
 routine PXRMEUT.  
  STATUS: Active
KEYWORDS: PXRMEUT
COMPONENT/ENTRY POINT: ASKYN
VARIABLES: DEF                          TYPE: Input
 VARIABLES DESCRIPTION:   Default for the Yes/No prompt. Y for Yes and N for
 No.  
VARIABLES: TEXT                         TYPE: Input
 VARIABLES DESCRIPTION:   Prompt text.  
VARIABLES: RTN                          TYPE: Input
 VARIABLES DESCRIPTION:   Routine to be used for help.  
VARIABLES: HLP                          TYPE: Input
 VARIABLES DESCRIPTION:   Short help.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: NOV 09, 2021

NUMBER: 7248                            IA #: 7248
  DATE CREATED: APR 19, 2021            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRC0G
  NAME: EDIT 2237 RUNNING BALANCE FIELDS
  ID: PRC0G
 GENERAL DESCRIPTION:   This integration agreement allows the Advanced
 Prosthetics Acquisition Tool (APAT) to call IFCAP routine PRC0G during
 purchase card order reconciliation and during the  removal of a reconciliation
 to edit RUNNING BALANCE QUARTER DATE (#449) and RUNNING BALANCE STATUS (#450), 
 if necessary, in the CONTROL POINT ACTIVITY #410 file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ADVANCED PROSTHETICS ACQ TOOL
KEYWORDS: APAT
COMPONENT/ENTRY POINT: ERS410
 COMPONENT DESCRIPTION:   Edit RUNNING BALANCE QUARTER DATE (#449) and RUNNING
 BALANCE STATUS (#450) fields.  
  
 Expected Results: 
   RUNNING BALANCE QUARTER DATE (#449) is calculated and set 
     if null.  
   RUNNING BALANCE STATUS (#450) is set to the appropriate 
     status.  
VARIABLES:                              TYPE: Output
 VARIABLES DESCRIPTION:   RUNNING BALANCE QUARTER DATE (#449) is calculated and
 set if null.  RUNNING BALANCE STATUS (#450) is set to the appropriate status.  
VARIABLES: PRCA                         TYPE: Input
 VARIABLES DESCRIPTION:   First ^-piece:  IEN of file 410 Second ^-piece:
 STATUS CODE ("E", "A", "O", or "C") 
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: MAY 14, 2021

NUMBER: 7249                            IA #: 7249
  DATE CREATED: APR 30, 2021            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFCREL
  NAME: CAREGIVER RELATIONSHIPS         ID: VAFCREL
 GENERAL DESCRIPTION:   The purpose of this Integration Control Registration is
 to grant packages the ability to retrieve patient caregiver relationship
 information.  
  STATUS: Active
KEYWORDS: VAFCREL
KEYWORDS: CAREGIVER
KEYWORDS: RELATIONSHIP
COMPONENT/ENTRY POINT: GET
 COMPONENT DESCRIPTION:   Given a patient data file number (DFN) this
 application programming interface (API) returns a list of Identity and Access
 Management (IAM) Veterans Affairs (VA) Master Patient Index (MPI) Relationship
 records with relationship type, relationship status, relationship status
 change date and relationship type rolecode (which defines direction of the 
 relationship [i.e. Son to Father vs Father to Son or Caregiver to Veteran 
 receiving care vs Veteran receiving care to Caregiver].  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN from the PATIENT file (#2).  
VARIABLES: RETURN                       TYPE: Output
 VARIABLES DESCRIPTION:   The RETURN(0) array will always be returned.  
  
 RETURN(0) - If relationships found for a given DFN, it will contain 1 in the
 1st piece and "RELATIONSHIPS RETURNED" text in 2nd piece 
  
 If no relationships are found for a given DFN, it will contain 0 in the 1st
 piece and "NO RELATIONSHIPS RETURNED" text in 2nd piece.  
  
 If there is an error condition, it will contain -1 in the 1st piece and error
 message text in 2nd piece.  
  
 Examples: 
 ---------
  
 RETURN(0)="1^RELATIONSHIPS RETURNED" 
  
 RETURN(0)="0^NO RELATIONSHIPS RETURNED" 
  
 RETURN(0)="-1^ERROR:Timeout Limit Reached" *** note: timeout limit is 10 
 seconds Possible error conditions: 
  
 RETURN(0)="-1^ERROR:Internal Error" 
  
 RETURN(0)="-1^ERROR:Unknown ID" 
  
  
 RETURN(1-n) - If relationships are found for a given DFN, it will contain the
 list of Relationships in the following format: 
  
 ICN^Relationship Type^Relationship Type Display^Relationship Role 
 Code^Relationship Status^Relationship Status Display^Relationship Status
 Change Date^Assigned Name 
  
 Where there are standardized Relationship Types values defined by the HL7 
 standard they will be used and below is the url to those standard values: 
  
 https://www.hl7.org/fhir/valueset-relatedperson-relationshiptype.html 
  
 Examples: 
 ---------
  
 RETURN(1)="1002345678V123456^CGP^CAREGIVER: 
 PRIMARY^QUAL^ACTIVE^APPROVED^20200220^CAREGIVER, ONE" 
  
 RETURN(2)="1901234590V098766^CGS^CAREGIVER: 
 SECONDARY^QUAL^ACTIVE^APPROVED^20200220^CAREGIVER,TWO" 
  
 RETURN(3)="1002345678V123456^SONC^SON^QUAL^ACTIVE^ACTIVE^20200220^CAREGIVE 
 R,THREE" 
  
 RETURN(4)="1901234590V098766^CGP^CAREGIVER: PRIMARY^QUAL^TERMINATED^BENEFIT
 END DATE^20170220^CAREGIVER,FOUR" 
  
 RETURN(5)="1007879802V000909^SPS^SPOUSE^QUAL^ACTIVE^^ACTIVE^20120301^CAREG 
 IVER,FIVE" 
  
 RETURN(6)="1089022222V123423^BRO^BROTHER^QUAL^ACTIVE^ACTIVE^20111202^CAREG 
 IVER,SIX" 
  DATE ACTIVATED: JAN 27, 2022

NUMBER: 7250                            IA #: 7250
  FILE NUMBER: 3.081                    GLOBAL ROOT: XUSEC(0,
  DATE CREATED: MAY 03, 2021            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: CPRS GUI (OR) SIGN-ON LOG LOOKUP
  ID: XUSEC(0,
 GENERAL DESCRIPTION:   The CPRS GUI requests the ability to do a lookup on the
 SIGN-ON LOG for a current user's SIGN-ON LOG IEN and Field #3 (SIGNOFF TIME).  
  
 To lookup the current SIGN-ON LOG for the user's active CPRS session using the
 following screen based on the user's UCI, Job#, & IP Address: 
  
 S SCR="I $P(^(0),U,8)=UCI,$P(^(0),U,3)=$J,$P(^(0),U,11)=$G(IO(""IP""))" with 
 $$FIND1^DIC("3.081","","Q",DUZ,"CUR",SCR,"ERR").  
  
 To lookup the SIGNOFF TIME (Field #3) for a given session: 
 $$GET1^DIQ("3.081",<IEN>,3,"I") 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: 3.081
KEYWORDS: CPRS
KEYWORDS: OR
KEYWORDS: SIGN-ON
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 7251                            IA #: 7251
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123,
  DATE CREATED: MAY 04, 2021
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: OEHRM Imaging Migration - access to file #123
  ID: GMR(123,
GLOBAL REFERENCE: GMR(123,
FIELD NUMBER: 16                        FIELD NAME: TIU RESULT NARRATIVE
  LOCATION: 0;20                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: ORDERING FACILITY
  LOCATION: 0;21                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   OEHRM is creating Imaging Migration software to
 facilitate the transfer of images from VistA to Millennium.  The software will
 build a central accession number database that identifies all image-holding
 entities - consults and Radiology procedures - and will maintain that file 
 throughout the conversion period.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EHRM
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   The Image Migration load tool is in 2 parts: 1)
 baseline load and 2) on-going maintenance.  
     
 BASELINE LOAD The software scans file #123, extracts the TIU Note pointer from
 field #16 and searches for DICOM images associated with it.  Once found,
 records are added to the Imaging Migration database.  
     
 ON-GOING MAINTENANCE When consults are resulted, the GMRC EVSEND OR protocol
 executes.  A new protocol - EHM CONSULTS - will be added to this parent
 protocol to add or update records in the Imaging Migration database.  This new
 protocol needs to read field #16 (TIU RESULT NARRATIVE) to get the TIU Note 
 pointer (#8925) to link to the consult's images.  
  
 RECORD EXTRACTION The extraction tool scans the Image Migration file.  If the
 record is for a consult, it extracts the patient's DFN from file #123.  
  DATE ACTIVATED: APR 19, 2022

NUMBER: 7252                            IA #: 7252
  DATE CREATED: MAY 04, 2021
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: Routine
  ROUTINE: GMRCIAC2
  NAME: OEHRM Imaging Migration - use of GMRCIAC2
  ID: GMRCIAC2
 GENERAL DESCRIPTION:   When consults are resulted, the GMRC EVSEND OR protocol
 executes.  A new protocol - EHM CONSULTS - will be added to this parent
 protocol to add or update records in the Imaging Migration database.  This new
 protocol needs to call GETDA^GMRIAC2 to extract the IEN of file #123 from the
 incoming HL7 message.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: EHRM
COMPONENT/ENTRY POINT: GETDA
VARIABLES: GMRCORC                      TYPE: Input
 VARIABLES DESCRIPTION:   HL7 ORC segment from field 2 to the end.  
VARIABLES: GMRCORC3                     TYPE: Output
 VARIABLES DESCRIPTION:   IEN in file #123.  
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION

NUMBER: 7253                            IA #: 7253
  FILE NUMBER: 2006.5839                GLOBAL ROOT: MAG(2006.5839,
  DATE CREATED: MAY 04, 2021            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  NAME: OEHRM Imaging Migration - Access to file #2006.5839
  ID: MAG(2006.5839,
GLOBAL REFERENCE: MAG(2006.5839,
FIELD NUMBER: 3                         FIELD NAME: IMAGE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .01                       FIELD NAME: FILE NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ENTRY NUMBER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   OEHRM is creating Imaging Migration software to
 facilitate the transfer of images from VistA to Millennium.  The software will
 build a central accession number database that identifies all image-holding
 entities - consults and Radiology procedures - and will maintain that file 
 throughout the conversion period.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: EHRM
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   The Image Migration load tool is in 2 parts: 1)
 baseline load and 2) on-going maintenance.  
     
 BASELINE LOAD The software scans file #2006.5839 loads the referenced images
 into the Imaging Migration database.  To do this, it needs to extract the FILE 
 NUMBER (field #.01) to check determine that it has a value of 123. It then 
 extracts the consult pointer from field #2 (ENTRY NUMBER) and the image 
 pointer from field #3 (IMAGE).  A record is created in the Image Migraton file
 or an existing record is updated.  
  
 ON-GOING MAINTENANCE When consults are resulted, the GMRC EVSEND OR protocol
 executes.  A new protocol - EHM CONSULTS - will be added to this parent
 protocol to add or update records in the Imaging Migration database.  This new
 protocol needs to access the "C" cross-reference in file #2006.5839 to
 determine if an image exists there for the resulted consult.  

NUMBER: 7254                            IA #: 7254
  FILE NUMBER: 2005                     GLOBAL ROOT: MAG(2005,
  DATE CREATED: MAY 04, 2021            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: OEHRM Imaging Migration - Access to file #2005
  ID: MAG(2005,
GLOBAL REFERENCE: MAG(2005,D0,
FIELD NUMBER: 1                         FIELD NAME: FILEREF
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: PROCEDURE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 14                        FIELD NAME: GROUP PARENT
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: PROCEDURE/EXAM DATE/TIME
  LOCATION: 2;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 60                        FIELD NAME: IMAGE
  LOCATION: PACS;1                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: MAG(2005,D0,4,D1,
FIELD NUMBER: .01                       FIELD NAME: OBJECT GROUP
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   OEHRM is creating Imaging Migration software to
 facilitate the transfer of images from VistA to Millennium.  The software will
 build a central accession number database that identifies all image-holding
 entities - consults and Radiology procedures - and will maintain that file 
 throughout the conversion period.  
  
 Note:  The patch - EHM*1*2 - will not be installed nationally.  It will be
 installed only at sites that are being converted to Cerner.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EHRM
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   The Image Migration load tool is in 2 parts: 1)
 baseline load and 2) on-going maintenance.  
        
 BASELINE LOAD 
  
 Consults: The software scans file #123 and extracts the TIU Note pointer.  It
 then uses the "ADI" cross-reference in file #8925.91 to identify the images
 associated with the consult.  The load extracts data from the fields listed
 below from file #2005 in order to add or update records in the Image Migration
 file (#1606).  
  
 Radiology:  The software scans file #74 and its image multiple in field #2005. 
 For each image pointed to, the load extracts data from the fields listed below
 from file #2005 in order to add or update records in the Image Migration file
 (#1606).  
  
 ON-GOING MAINTENANCE 
  
 Consults: When consults are resulted, the EHM CONSULTS protocol is executed to
 add or update records in the Imaging Migration database.  This new protocol
 needs to read the same fields as does the baseline load into order to add or
 update records in the Image Migration file (#1606).  
  
 Radiology: When Radiology exams are resulted, the EHM RADRPT protocol is 
 executed to add or update records in the Imaging Migration database.  This new
 protocol needs to read the same fields as does the baseline load into order to
 add or update records in the Image Migration file (#1606).  
  DATE ACTIVATED: JUN 15, 2021

NUMBER: 7255                            IA #: 7255
  FILE NUMBER: 2005.61                  GLOBAL ROOT: MAGV(2005.61,
  DATE CREATED: MAY 04, 2021            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  NAME: OEHRM Imaging Migration - Access to file #2005.61
  ID: MAGV(2005.61,
GLOBAL REFERENCE: MAGV(2005.61,D0,
FIELD NUMBER: .03                       FIELD NAME: PROCEDURE TYPE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   OEHRM is creating Imaging Migration software to
 facilitate the transfer of images from VistA to Millennium.  The software will
 build a central accession number database that identifies all image-holding
 entities - consults and Radiology procedures - and will maintain that file 
 throughout the conversion period.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: EHRM
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   The Image Migration load tool is in 2 parts: 1)
 baseline load and 2) on-going maintenance.  
           
 BASELINE LOAD 
     
 Consults: The software scans file #123.  It identifies images associated with
 the consult in the Image file (#2005), the GMRC DICOM Temp List file 
 (#2006.5839) and in the new SOP files (#2005.63, 2005.62, 2005.61).  The load
 extracts data from the fields listed below from the new SOP files in order to
 add or update records in the Image Migration file (#1606).  
     
 Radiology:  The software scans file #74.  It identifies images  associated 
 with the Radiology report in the Image file (#2005) and in the new SOP files
 (#2005.63, 2005.62, 2005.61).  The load extracts data from the fields listed
 below from the new SOP files in order to add or update records in the Image
 Migration file (#1606).  
     
 ON-GOING MAINTENANCE 
     
 Consults: When consults are resulted, the EHM CONSULTS protocol is executed to
 add or update records in the Imaging Migration database.  This protocol needs
 to read the same fields as does the baseline load into order to add or update
 records in the Image Migration file (#1606).  
  
 Radiology: When Radiology exams are resulted, the EHM RADRPT protocol is 
 executed to add or update records in the Imaging Migration database.  This 
 protocol needs to read the same fields as does the baseline load into order to
 add or update records in the Image Migration file (#1606).  

NUMBER: 7256                            IA #: 7256
  FILE NUMBER: 70                       GLOBAL ROOT: RADPT
  DATE CREATED: MAY 04, 2021
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: OEHRM Imaging Migration - Access to file #70
  ID: RADPT
GLOBAL REFERENCE: RADPT(D0,'DT',D1,'P',D2,
FIELD NUMBER: 17                        FIELD NAME: REPORT TEXT
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: RADPT(D0,'DT',D1,
FIELD NUMBER: 3                         FIELD NAME: HOSPITAL DIVISION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   OEHRM is creating Imaging Migration software to
 facilitate the transfer of images from VistA to Millennium.  The software will
 build a central accession number database that identifies all image-holding
 entities - consults and Radiology procedures - and will maintain that file 
 throughout the conversion period.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EHRM
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   When Radiology procedures are resulted, the RA RPT 2.3
 protocol executes.  A new protocol - EHM RADRPT - will be added to this parent 
 protocol to add or update records in the Imaging Migration database.  This 
 protocol parses the HL7 result message and then extracts the pointer to the
 RAD/NUC MED REPORTS file (#74) that is stored in field #17 REPORT TEXT of the
 EXAMINATIONS multiple in the RAD/NUC MED PATIENT file (#70).  It uses the
 pointer to get the case number (ICR #7257) so that it can determine if the
 Radiology case exists in the new SOP files (#2005.6n).  
  DATE ACTIVATED: APR 21, 2022

NUMBER: 7257                            IA #: 7257
  FILE NUMBER: 74                       GLOBAL ROOT: RARPT(
  DATE CREATED: MAY 04, 2021
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: File
  NAME: OEHRM Imaging Migration - Access to file #74
  ID: RARPT(
GLOBAL REFERENCE: RARPT(D0,
FIELD NUMBER: .01                       FIELD NAME: DAY-CASE#
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: REPORT STATUS
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2005                      FIELD NAME: IMAGE
  LOCATION: 2005                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   OEHRM is creating Imaging Migration software to
 facilitate the transfer of images from VistA to Millennium.  The software will
 build a central accession number database that identifies all image-holding
 entities - consults and Radiology procedures - and will maintain that file 
 throughout the conversion period.  
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
KEYWORDS: EHRM
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   The Image Migration load tool is in 2 parts: 1)
 baseline load and 2) on-going maintenance.  
  
 BASELINE LOAD The software scans file #74 for reports with images and loads
 them into the Imaging Migration database.  To do this, it needs to extract the 
 report status (field #5) to check that the report is verified.  It then scans
 the Image multiple (field #2005) to get the data it needs for the baseline
 load.  
  
 A second part of the baseline load scans the New SOP Image Series file 
 (#2005.63).  If the study is Radiology, it needs to get the IEN of the 
 Radiology Report from the "B" cross-reference.  
  
 ON-GOING MAINTENANCE When Radiology procedures are resulted, the RA RPT 2.3
 protocol executes.  A new protocol - EHM RADRPT - will be added to this parent 
 protocol to add or update records in the Imaging Migration database.  This new
 protocol extracts the case number from field #.01 of the RAD/NUC MED REPORTS
 file (#74) so it can check to see if images exist in the new SOP files
 (#2005.6n).  
  
 RECORD EXTRACTION The extraction tool scans the Image Migration file.  If the
 record is from Radiology, it extracts the patient's DFN from file #74.  
  DATE ACTIVATED: JUN 08, 2021

NUMBER: 7258                            IA #: 7258
  DATE CREATED: MAY 06, 2021            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMCALT
  NAME: CHECK SMART ALERTS              ID: PXRMCALT
 GENERAL DESCRIPTION:   The purpose of this integration agreement is to grant
 access to use PXRMCALT to perform special processing for the SMART alerts.
 CPRS v31B released the System for Mammography Results Tracking (SMART) NSR
 20100701 functionality. As part of the changes involved with this NSR, a call
 to ALTDATA^PXRMCALT was implemented in OE/RR functionality released in 
 OR*3*377 and PXRM*2*45. Documentation is being added in OR*3*535 for ICR 7258
 as part of an ICR clean-up effort.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRMCALT
KEYWORDS: ALTDATA
COMPONENT/ENTRY POINT: ALTDATA
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (DFN) for the PATIENT (#2)
 file.  
VARIABLES: ALTID                        TYPE: Input
 VARIABLES DESCRIPTION:   Alert ID.  
VARIABLES: RETURN                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns the computed findings DATA and TEXT arrays
 based off the details associated with the patient's SMART alert. This is
 returned in the RETURN ("DATA") and RETURN ("TEXT") arrays, respectively.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JUN 22, 2023

NUMBER: 7259                            IA #: 7259
  DATE CREATED: MAY 10, 2021            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  NAME: AbandonedDGSEC4 routine         STATUS: Withdrawn

NUMBER: 7260                            IA #: 7260
  DATE CREATED: MAY 11, 2021            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQRRPC SELECT
  REMOTE PROCEDURE: YTQRRPC SELECT
 GENERAL DESCRIPTION:   RPC for Mental Health Check Up Calls for Instrument
 Selection.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 2030
KEYWORDS: Instrument Selection
SUBSCRIBING PACKAGE: MOBILE MHPRO
 SUBSCRIBING DETAILS:   RPC is being provided for Mental Health Checkup for
 Mobile applications.  This is the mobile version of MH Pro.  
  DATE ACTIVATED: MAY 11, 2021

NUMBER: 7261                            IA #: 7261
  DATE CREATED: MAY 11, 2021
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7261
  STATUS: Pending

NUMBER: 7262                            IA #: 7262
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,PS,
  DATE CREATED: MAY 15, 2021            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: PROVIDER CLASS (#53.5) field in the NEW PERSON (#200) file
  ID: VA(200,PS,
GLOBAL REFERENCE: VA(200,PS,
FIELD NUMBER: 53.5                      FIELD NAME: PROVIDER CLASS
  LOCATION: PS;5                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Home Based Primary Care (HBPC - formerly known as
 Hospital Based Home Care) package displays the PROVIDER CLASS (#53.5) field
 from the NEW PERSON (#200) file in the option "Provider File Data Entry". The
 display aids users in ensuring the correct entry is being added as a provider
 for HBPC.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PROVIDER CLASS
KEYWORDS: HBHC
KEYWORDS: HBPC
SUBSCRIBING PACKAGE: HOME BASED PRIMARY CARE
 SUBSCRIBING DETAILS:   Routine HBHCPROV retrieves the PROVIDER CLASS (#53.5)
 field for display to the user.  
  DATE ACTIVATED: JUN 08, 2021

NUMBER: 7263                            IA #: 7263
  FILE NUMBER: 133                      GLOBAL ROOT: SRP(133
  DATE CREATED: MAY 21, 2021            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: File
  NAME: DOC ONLY - COPY OF 2237         ID: SRP(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 mult-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:   This is a DOCUMENT ONLY ICR for Class 3 package, MSCJ
 namespace, for the PICIS interface.  The PICIS/VistA interface is for incoming
 HL7 Surgery requests coming from the PICIS COTS Surgery Scheduling
 application.  MSCJ falls under the Medsphere Systems Corporation package in
 the MSC namespace. MSCJ sub-package 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: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DOCUMENT ONLY
KEYWORDS: PICIS
KEYWORDS: SURGERY SCHEDULING
KEYWORDS: MEDSPHERE SYSTEMS CORPORATION
SUBSCRIBING PACKAGE: MEDSPHERE SYSTEMS CORPORATION

NUMBER: 7264                            IA #: 7264
  DATE CREATED: MAY 21, 2021            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: Routine
  ROUTINE: SROXR1                       NAME: DOC ONLY - Access to SROXR1
  ID: SROXR1
 GENERAL DESCRIPTION:   DOCUMENT ONLY: PICIS Surgery Scheduling Interface is a
 subpackage (MSCJ namespace) within Medshere Systems Corporation (MSC
 namespace). This is a Class 3 ICR for the MSCJ MEDSPHERE PICIS APPLICATIONS
 Package, patch MSCJ*n*n for use of the APIs in the ^SROXR1 routine to
 facilitate scheduling surgeries from the PICIS Surgery Scheduling package. 
 The Routine MSCJSR01 calls the SROXR1 API's to add and delete surgery 
 schedules from the PICIS interface.  API components, AR and KAR in the ^SROXR1
 routine, are used for creating and deleting the "AR" cross references in the
 SURGERY, #130, file for the DATE OF OPERATION, #.09, field.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: DOCUMENT ONLY
KEYWORDS: PICIS
KEYWORDS: SURGERY SCHEDULING
KEYWORDS: MEDSPHERE SYSTEMS CORPORATION
KEYWORDS: MSCJ
COMPONENT/ENTRY POINT: AR
 COMPONENT DESCRIPTION:   The routine MSCJSR01 uses the AR^SROXR1 component to
 create an "AR" cross reference on the "DATE OF OPERATION" field, #.09, in the
 SURGERY, #130, file.  
COMPONENT/ENTRY POINT: KAR
 COMPONENT DESCRIPTION:   The routine MSCJSR01 uses the KAR^SROXR1 component to
 delete an "AR" cross reference on the "DATE OF OPERATION" field, #.09, in the
 SURGERY, #130, file.  
SUBSCRIBING PACKAGE: MEDSPHERE SYSTEMS CORPORATION
 SUBSCRIBING DETAILS:   MSC is the Package Namespace in FORUM's Package File.
 The actual patch is prefixed with the namespace MSCJ.  

NUMBER: 7265                            IA #: 7265
  FILE NUMBER: 8925.91                  GLOBAL ROOT: TIU(8925.91,
  DATE CREATED: MAY 28, 2021
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: OEHRM Imaging Migration - Access to file #8925.91
  ID: TIU(8925.91,
GLOBAL REFERENCE: TIU(8925.91,'ADI'
 GLOBAL DESCRIPTION:   Cross reference by field #.01 DOCUMENT and field #.02
 IMAGE.  
  
 Direct Global Read 
 GENERAL DESCRIPTION:   OEHRM is creating Imaging Migration software to
 facilitate the transfer of images from VistA to Millennium.  The software will
 build a central accession number database that identifies all image-holding
 entities - consults and Radiology procedures - and will maintain that file 
 throughout the conversion period.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EHRM
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   The Image Migration load tool is in 2 parts: 1)
 baseline load and 2) on-going maintenance.  
        
 BASELINE LOAD The software scans file #12 and extracts the TIU Note pointer. 
 It then needs to scan the "ADI" cross-reference in file #8925.91 to identify
 the images associated with the TIU note to determine if any of the images are 
 DICOM.  If they are, a record is added to the Imaging Migration database.  
        
 ON-GOING MAINTENANCE When consults are resulted, the GMRC EVSEND OR protocol
 executes.  A new protocol - EHM CONSULTS - will be added to this parent
 protocol to add or update records in the Imaging Migration database.  This new
 protocol extracts the TIU note pointer and then scans the list of associated 
 images in the "ADI" cross-reference of file #8925.91. 
  DATE ACTIVATED: JUN 09, 2021

NUMBER: 7266                            IA #: 7266
  FILE NUMBER: 391.91                   GLOBAL ROOT: DGCN(391.91,
  DATE CREATED: JUN 01, 2021            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: OEHRM Image Migration - access to file #391.91
  ID: DGCN(391.91,
GLOBAL REFERENCE: DGCN(391.91,
FIELD NUMBER: 11                        FIELD NAME: SOURCE ID
  LOCATION: 2;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: AKEY                      FIELD NAME: Cross-reference
  ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   AKEY cross-reference is a record level key from the
 following fields: 
  
 .01 = PATIENT .02 = INSTITUTION .09 = SOURCE ID TYPE 10  = ASSIGNING AUTHORITY
 (value of interest is "USDOD") 
 GENERAL DESCRIPTION:   OEHRM is creating Imaging Migration software to
 facilitate the transfer of images from VistA to Millennium.  The software will
 build a central accession number database that identifies all image-holding
 entities - consults and Radiology procedures - and will maintain that file 
 throughout the conversion period.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: EHRM
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   The Image Migration software also produces an
 extraction report that can be used by Cerner to verify that all images for a
 site have been migrated.  

NUMBER: 7267                            IA #: 7267
  FILE NUMBER: 2005.62                  GLOBAL ROOT: MAGV(2005.62,
  DATE CREATED: JUN 01, 2021            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  NAME: OEHRM Imaging Migration - Access to file #2005.62
  ID: MAGV(2005.62,
GLOBAL REFERENCE: MAGV(2005.62,D0,
FIELD NUMBER: .02                       FIELD NAME: ACCESSION NUMBER
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: D
  FIELD NAME: Cross-reference on field #.02
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: STUDY DATE/TIME
  LOCATION: 2;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: PROCEDURE REFERENCE
  LOCATION: 6;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   OEHRM is creating Imaging Migration software to
 facilitate the transfer of images from VistA to Millennium.  The software will
 build a central accession number database that identifies all image-holding
 entities - consults and Radiology procedures - and will maintain that file 
 throughout the conversion period.  
  
 Note:  The patch - EHM*1*2 - will not be installed nationally.  It will be
 installed on at sites that are being converted to Cerner.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: EHRM
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   The Image Migration load tool is in 2 parts: 1)
 baseline load and 2) on-going maintenance.  
              
    BASELINE LOAD 
        
 Consults: The software scans file #123.  It identifies images associated with
 the consult in the Image file (#2005), the GMRC DICOM Temp List file 
 (#2006.5839) and in the new SOP files (#2005.63, 2005.62, 2005.61).  The load
 extracts data from the fields listed below from the new SOP files in order to
 add or update records in the Image Migration file (#1606).  
  
 Radiology:  The software scans file #74.  It identifies images  associated 
 with the Radiology report in the Image file (#2005) and in the new SOP files
 (#2005.63, 2005.62, 2005.61).  The load extracts data from the fields listed
 below from the new SOP files in order to add or update records in the Image
 Migration file (#1606).  
        
    ON-GOING MAINTENANCE 
        
 Consults: When consults are resulted, the EHM CONSULTS protocol is executed to
 add or update records in the Imaging Migration database.  This protocol needs
 to read the same fields as does the baseline load into order to add or update
 records in the Image Migration file (#1606).  
  
 Radiology: When Radiology exams are resulted, the EHM RADRPT protocol is 
 executed to add or update records in the Imaging Migration database.  This 
 protocol needs to read the same fields as does the baseline load into order to
 add or update records in the Image Migration file (#1606).  

NUMBER: 7268                            IA #: 7268
  DATE CREATED: JUN 01, 2021
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Other
  NAME: OEHRM - Subscribe to RA RPT 2.3
 GENERAL DESCRIPTION:   OEHRM is creating Imaging Migration software to
 facilitate the transfer of images from VistA to Millennium.  The software will
 build a central accession number database that identifies all image-holding
 entities - consults and Radiology procedures - and will maintain that file 
 throughout the conversion period.  
  
 Note:  The patch - EHM*1*2 - will not be installed nationally.  It will be
 installed on at sites that are being converted to Cerner.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   
  The Image Migration load tool is in 2 parts: 1) baseline load and 2) on-going
 maintenance.  The baseline load creates file #1606 (Image Migration) based on
 the contents of file #74 (RAD/NUC MED REPORTS) when the load is run. 
 Thereafter, file #1606 is added to or updated when Radiology exams are
 resulted.  The protocol EHM RADRPT will be a subscriber to RA RPT 2.3.  When a
 result is posted, EHM RADRPT will identify images associated with the
 Radiology report and post information about them in file #1606.  

NUMBER: 7269                            IA #: 7269
  DATE CREATED: JUN 07, 2021            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: PRCA FP VETERAN CHRG RPT ADD TO DVBA HRC MENUS
 GENERAL DESCRIPTION:   HRC is requesting the addition of the FIRST PARTY
 VETERAN CHARGE REPORT [PRCA FP VETERAN CHRG RPT] OPTION to the following
 DVBA/HRC menus:    
  
 DVBA HRC MENU PHARMACY 
  
 DVBA HRC MENU PHARMACY CC 
  
 DVBA HRC MENU EXTENDED SVCS 
  STATUS: Active
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
  DATE ACTIVATED: JUN 15, 2021

NUMBER: 7270                            IA #: 7270
  FILE NUMBER: 2005.63                  GLOBAL ROOT: MAGV(2005.63,
  DATE CREATED: JUN 15, 2021            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  NAME: OEHRM Imaging Migration - Access to file #2005.63
  ID: MAGV(2005.63,
GLOBAL REFERENCE: MAGV(2005.63,D0,
FIELD NUMBER: 3                         FIELD NAME: MODALITY
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: NUMBER OF SOP INSTANCES
  LOCATION: 4;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: STUDY REFERENCE
  LOCATION: 6;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: C                         FIELD NAME: Cross-reference on field #11
  ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 27                        FIELD NAME: TIU NOTE REFERENCE
  LOCATION: 6;4                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   OEHRM is creating Imaging Migration software to
 facilitate the transfer of images from VistA to Millennium.  The software will
 build a central accession number database that identifies all image-holding
 entities - consults and Radiology procedures - and will maintain that file 
 throughout the conversion period.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: EHRM
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   The Image Migration load tool is in 2 parts: 1)
 baseline load and 2) on-going maintenance.  
  
    BASELINE LOAD 
        
 Consults: The software scans file #123.  It identifies images associated with
 the consult in the Image file (#2005), the GMRC DICOM Temp List file 
 (#2006.5839) and in the new SOP files (#2005.63, 2005.62, 2005.61).  The load
 extracts data from the fields listed below from the new SOP files in order to
 add or update records in the Image Migration file (#1606).  
        
 Radiology:  The software scans file #74.  It identifies images  associated 
 with the Radiology report in the Image file (#2005) and in the new SOP files
 (#2005.63, 2005.62, 2005.61).  The load extracts data from the fields listed
 below from the new SOP files in order to add or update records in the Image
 Migration file (#1606).  
        
    ON-GOING MAINTENANCE 
        
 Consults: When consults are resulted, the EHM CONSULTS protocol is executed to
 add or update records in the Imaging Migration database.  This protocol needs
 to read the same fields as does the baseline load into order to add or update
 records in the Image Migration file (#1606).  
     
 Radiology: When Radiology exams are resulted, the EHM RADRPT protocol is 
 executed to add or update records in the Imaging Migration database.  This 
 protocol needs to read the same fields as does the baseline load into order to
 add or update records in the Image Migration file (#1606).  

NUMBER: 7271                            IA #: 7271
  FILE NUMBER: 130                      GLOBAL ROOT: SRF
  DATE CREATED: JUN 15, 2021            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: File
  NAME: Copy of ICR 103 with Document Only fields
  ID: SRF
 GENERAL DESCRIPTION:   This ICR is created for Document Only purposes to allow
 MSCJ MEDSPHERE PICIS APPLICATIONS Package to be compliant with SAC standards
 requiring FileMan read/write access.  The routine MSCJSR01 performs reads and
 writes to the SURGERY, #130, file using FileMan.  The following FileMan fields
 are accessed in a read/write manner using FileMan APIs.  
  
 The following indented fields (.01, .011, .02, .09. .14, .164, 17, and 50 
 would have been covered in ICR 103, but the Surgery Custodian POC requested
 this Class 3 product's access be defined in it's own ICR. The fields not
 indented would have needed to be added to 103, which was a concern for the
 POC.  
  
  
                 .01 - PATIENT 
                 .011 - IN/OUT-PATIENT STATUS 
     .0155 - CLASSIFICATION ENTERED (Y/N) 
                 .02 - OPERATING ROOM 
     .03 - MAJOR/MINOR 
     .035 - CASE SCHEDULE TYPE 
     .05 - REQ CLEAN OR CONTAMINATED 
                 .09 - DATE OF OPERATION 
     .13 - RESTR & POSITION AIDS 
                 .14 - SURGEON 
     .15 - FIRST ASST 
     .16 - SECOND ASST 
                 .164 - ATTEND SURG 
     .42 - OTHER PROCEDURES 
     1.098 - DATE/TIME R REQUEST MADE 
     1.099 - SURG SCHED PERSON 
     10 - SCHEDULED START TIME 
     11 - SCHEDULED END TIME 
                 17 - CANCEL DATE 
     26 - PRINCIPAL PROCEDURE 
     27 - PLANNED PRIN PROCEDURE CODE 
     36 - REQUESTED 
     37 - ESTIMATED CASE LENGTH 
     38 - REQUEST BLOOD AVAILABILITY 
                 50 - DIVISION 
     55 - INDICATIONS FOR OPERATIONS 
     56 - PRE-ADMISSION TESTING 
  STATUS: Pending
KEYWORDS: DOCUMENT ONLY
KEYWORDS: PICIS
KEYWORDS: MEDSHPERE
KEYWORDS: MSCJ
SUBSCRIBING PACKAGE: MEDSPHERE SYSTEMS CORPORATION
 SUBSCRIBING DETAILS:   This subscription is for MedShere Systems project in
 the MSCJ namespace called MSCJ MEDSPHERE PICIS APPLICATIONS Package.  This is
 a Class III package.  The ICR subscription is documented to allow the MSCJ
 routine to reflect the proper ICR in the routine, which would make the routine 
 compliant with the SAC standard.  
  DATE ACTIVATED: JUN 15, 2021

NUMBER: 7272                            IA #: 7272
  FILE NUMBER: 660                      GLOBAL ROOT: RMPR(660,
  DATE CREATED: JUN 24, 2021            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: File
  NAME: RECORD OF PROS APPLIANCE/REPAIR FILE 660 FILEMAN READS
  ID: RMPR(660,
 GENERAL DESCRIPTION:   Generic database integration agreement for doing
 Fileman READS for ALL fields into Prosthetics file# 660 - RECORD OF PROS
 APPLIANCE/REPAIR.  Use of Fileman APIs $$GET1^DIQ and GETS^DIQ for all fields
 in file 660 and all fields in all subfiles of file 660.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 7273                            IA #: 7273
  DATE CREATED: JUL 15, 2021            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC APPSDGET
  REMOTE PROCEDURE: SDEC APPSDGET
 GENERAL DESCRIPTION:   VTEX will use this as part of the CHECK-IN/KIOSK
 replacement project. VSIP is the Veteran Scheduling InteroPerability web-based
 solution. The SDEC APPSDGET will be used to get the veterans appointments.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active
KEYWORDS: VTEX
KEYWORDS: APPOINTMENT
SUBSCRIBING PACKAGE: VETEXT
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Added 11/17/22, via DTC Integration Platform (DIP)
 (VASI: 2825) for VA Health Connect Scheduling/WellHive scheduling application
 for the Clinical Contact Centers.  
  DATE ACTIVATED: JUL 15, 2021

NUMBER: 7274                            IA #: 7274
  DATE CREATED: JUL 20, 2021
  CUSTODIAL PACKAGE: VA POINT OF SERVICE (KIOSKS)
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VPS GET DFN
  REMOTE PROCEDURE: VPS GET DFN
 GENERAL DESCRIPTION:   VTEX (VEText) is working with OCTO/OVAC to replace
 Kiosk Hardware as part of the Checkin/VSIP project.  VEText is a web-based
 application that will use this RPC as part of the solution being developed
 called VSIP. VEText will use the RPC VPS GET DFN to get information about the
 patient. 
  STATUS: Active
KEYWORDS: VTEX
SUBSCRIBING PACKAGE: VETEXT
  DATE ACTIVATED: AUG 31, 2021

NUMBER: 7275                            IA #: 7275
  DATE CREATED: JUL 20, 2021
  CUSTODIAL PACKAGE: VA POINT OF SERVICE (KIOSKS)
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: VPS GET2 PATIENT DEMOGRAPHIC
  REMOTE PROCEDURE: VPS GET2 PATIENT DEMOGRAPHIC
 GENERAL DESCRIPTION:   VEText is working with OCTO/OVAC to on a project to
 replace VPS Kisk HArdware with a new mobile expierence. VEText needs to use
 VPS GET2 PATIENT DEMOGRAPHIC to get patient information as part of the new
 VSIP project. 
  STATUS: Active
KEYWORDS: VTEX
SUBSCRIBING PACKAGE: VETEXT
  DATE ACTIVATED: SEP 02, 2021

NUMBER: 7276                            IA #: 7276
  DATE CREATED: JUL 23, 2021            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Routine
  ROUTINE: DGENELA                      NAME: COMPACT ACT ELIGIBLE
  ID: DGENELA
 GENERAL DESCRIPTION:   Returns the COMPACT Act Indicator.  
  
 The indicator is '1' (for TRUE) if either of the following conditions is true: 
  
  - Enrollment Category from the patient's current enrollment record is 
    "ENROLLED".  
  - The patient record contains the "COMPACT ACT ELIGIBLE" eligibility 
    code.  
  STATUS: Pending
KEYWORDS: COMPACT ACT
COMPONENT/ENTRY POINT: CAI
 COMPONENT DESCRIPTION:   COMPACT ACT INDICATOR 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN 

NUMBER: 7277                            IA #: 7277
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: AUG 06, 2021            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ PENSION INFORMATION
  ID: DPT(
GLOBAL REFERENCE: DPT(D0,
FIELD NUMBER: .3851                     FIELD NAME: PENSION AWARD EFFECTIVE DATE
  LOCATION: .385;1                      ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   It is the Effective Date that the patient was awarded VA
 Pension Entitlement of Original Award by VBA. This field is optional. But if 
 entered, must be a precise date Month/Date/Year) (00/00/0000). This date
 cannot be a future date. This date also cannot be entered before the veteran's
 16th birthday.  
FIELD NUMBER: .3853                     FIELD NAME: PENSION TERMINATED DATE
  LOCATION: .385;3                      ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The date the Pension was Terminated 
 GENERAL DESCRIPTION:   Accounts Receivable (AR) needs access to the following
 fields in the Patient file via FileMan Utilities in order to determine if any 
 outstanding First Party (i.e. copay) debt can be cancelled due to a Pension
 Award in patch PRCA*4.5*384.  
  
 The fields AR will use are: 
  
     Patient File (#2) fields: 
  
   .3851  - PENSION AWARD EFFECTIVE DATE 
   .3853  - PENSION TERMINATED DATE 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ACCOUNTS RECEIVABLE
KEYWORDS: PENSION
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   Effective with patch PRCA*4.5*384, new field .3853 -
 PENSION TERMINATED DATE was added to this ICR, which allows Facility Revenue
 to create a report to identify Veterans who have Copayments which may be
 eligible for cancellation due a pension award.  The new field, PENSION
 TERMINATED DATE (#.3853), places an end to the cancellation eligibility period
 if the Pension was Terminated.  
  DATE ACTIVATED: MAR 18, 2022

NUMBER: 7278                            IA #: 7278
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123,
  DATE CREATED: AUG 16, 2021
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROSTHETICS ORDERS REPORT
  ID: GMR(123,
GLOBAL REFERENCE: GMR(123,D0,
FIELD NUMBER: .01                       FIELD NAME: FILE ENTRY DATE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: REMOTE CONSULT FILE ENTRY
  LOCATION: 0;22                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TO SERVICE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: CPRS STATUS
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: FEB 04, 2022
KEYWORDS: EHRM
KEYWORDS: OEHRM
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   Prosthetics orders are processed in VistA after
 conversion to Cerner because Millennium lacks the requisite functionality. 
 Orders for prosthetics are entered in Millennium and pass through OpenLink and
 VDIF before being received in VistA.  Neither OpenLink nor VDIF can report HL7 
 errors so orders are lost before reaching VistA.  The Prosthetics Orders 
 Report lists consult orders so they can be matched with Millennium.  
  
 An expiration date was added because this ICR is meant to be temporary. The
 related patch, EHM*1*5, will ideally never need to be installed at converted
 sites. It's intended to identify a problem and get it fixed.  
  DATE ACTIVATED: AUG 17, 2021

NUMBER: 7279                            IA #: 7279
  DATE CREATED: AUG 17, 2021            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: XU EPCS ADD DEA                 REMOTE PROCEDURE: XU EPCS ADD DEA
 GENERAL DESCRIPTION:   TESTING 
  STATUS: Pending
KEYWORDS: EPCS
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS

NUMBER: 7280                            IA #: 7280
  DATE CREATED: AUG 26, 2021
  CUSTODIAL PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
  USAGE: Private                        TYPE: Remote Procedure
  NAME: WEBG ADD/EDIT/DELETE ORDER DIALOG
 GENERAL DESCRIPTION:   Allows the WebVRAM GUI application to add new entry,
 edit and delete entry from the Order Dialog file #101.41 
  
 NAME: WEBG ADD ORDLG TAG: ORDADD                           ROUTINE: WEBGORUT 
 RETURN VALUE TYPE: SINGLE VALUE       AVAILABILITY: RESTRICTED DESCRIPTION:   
  The ICR is still in progress.  
  Allows the WebVRAM application to add new entry to the Order Dialog file 
  #101.41 INPUT PARAMETER: ORDLGDATA              PARAMETER TYPE: LITERAL 
   REQUIRED: YES 
  DESCRIPTION:   
  These are the data fields that need to be set into the Order Dialog file 
  #101.41. Contains the following "^" piece delimited structure: 
   
  ORDLGDATA=p1^p2^p3 
    where: 
    p1 := [required] The external value from the Order Dialog name 
                     (#101.41,.01) 
    p2 := [optional] Display Text (101.41,2) 
    p3 := [optional] Type 
                     If not passed in, the routine will default the type to 
                     "D"ialog 
   
  Example: 
  ORDLGDATA=WEBG OR NEW ORDER DIALOG^Sample Display Text^D 
  
 RETURN PARAMETER DESCRIPTION:   
  Returns a single value in the following format: 
   
  If the adding of entry is successful: 
  RESULT= IEN from the Order Dialog file #101.41^message 
   
  Otherwise, 
  RESULT=-1^error_message 
  
  
  
 NAME: WEBG EDIT ORDLG TAG: EDITORD                          ROUTINE: WEBGORUT 
 RETURN VALUE TYPE: SINGLE VALUE DESCRIPTION:   
  The ICR is still need to be requested.  
  Allows the WebVRAM application to add new entry to the Order Dialog file 
  #101.41 INPUT PARAMETER: ORDLGDATA              PARAMETER TYPE: LITERAL 
   REQUIRED: YES 
  DESCRIPTION:   
  These are the data fields that need to be set into the Order Dialog file 
   #101.41. Contains the following "^" piece delimited structure: 
    
   ORDLGDATA=p1^p2^p3 
     where: 
     p1 := [required] The external value from the Order Dialog name 
                      (#101.41,.01) 
     p2 := [optional] Display Text (101.41,2) 
     p3 := [optional] Type 
   Example: 
   ORDLGDATA=WEBG OR NEW ORDER DIALOG^Sample Display Text^D 
  
 RETURN PARAMETER DESCRIPTION:   
   Return a single value in the following format: 
    
   If the adding of entry is successful: 
   RESULT=1^message 
    
   Otherwise, 
   RESULT=-1^error_message 
  
  
 NAME: WEBG DELETE ORDLG TAG: DELORD                           ROUTINE:
 WEBGORUT RETURN VALUE TYPE: SINGLE VALUE       AVAILABILITY: RESTRICTED 
  DESCRIPTION:   
  The ICR still need to be requested.  
  Allows WebVRAM application to delete/remove an entry from the Order 
  Dialog file #101.41 INPUT PARAMETER: ORDNAME                PARAMETER TYPE:
 LITERAL 
   REQUIRED: YES 
  DESCRIPTION:   
  This is the external value from the Order Dialog file #101.41,.01 
  
 RETURN PARAMETER DESCRIPTION:   
  Return a single value in the following format: 
   
  If successful: 
  RESULT=1^message 
   
  Othwerwise, 
  RESULT=-1^error_message 
  STATUS: Pending

NUMBER: 7281                            IA #: 7281
  FILE NUMBER: 8926.5                   GLOBAL ROOT: TIU(8926.5,
  DATE CREATED: SEP 01, 2021
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU LOINC SERVICE
  ID: TIU(8926.5,
GLOBAL REFERENCE: TIU(8926.5,DO,
FIELD NUMBER: .01                       FIELD NAME: SERVICE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   SERVICE 
 GLOBAL DESCRIPTION:   $$GET1^DIQ is used to retrieve the SERVICE.  
 GENERAL DESCRIPTION:   The Release of Information (ROI) team  would like
 FILEMAN read access to the .01 field of file TIU LOINC SERVICE (#8926.5) to
 determine which Compensation and Pension service is being pointed to by the
 .07 field of file VHA ENTERPRISE STANDARD TITLE (# 8926.1) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU
KEYWORDS: LOINC
KEYWORDS: TIU LOINC SERVICE
KEYWORDS: 8926.5
SUBSCRIBING PACKAGE: RELEASE OF INFORMATION - DSSI
 SUBSCRIBING DETAILS:   Effective with release of DSIR*8.2*15.  
  DATE ACTIVATED: SEP 20, 2021

NUMBER: 7282                            IA #: 7282
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXVRPC1
  NAME: PXVRPC1                         ID: PXVRPC1
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PCE
KEYWORDS: VIMM
COMPONENT/ENTRY POINT: IMAN
 COMPONENT DESCRIPTION:   Returns immunization manufacturer information.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Returned information is stored in ^TMP("PXVLST",$J)). 
 
 Return info format: Field Name^Field Value.  Error format: -1^error message.  
 Alternate array: Caret delimited string with differing internal and external
 values separated by a tilde.  
VARIABLES: PXVLK                        TYPE: Input
 VARIABLES DESCRIPTION:   R:XXX - return entry with ien XXX; M:XXX - return
 entry with MVX code XXX; N:XXX - return entry with imm manufacturer name XXX; 
 S:A   - return list of all active manufacturers; S:I   - return list of all
 inactive manufacturers; S:B   - return list of all manufacturers, active and
 inactive.  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Date for use in determining status -
 defaults to TODAY.  
VARIABLES: PXVI                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) 1 - Return alternate array with internal
 values in delimited string.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 13, 2021

NUMBER: 7283                            IA #: 7283
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXVRPC2
  NAME: PXVRPC2                         ID: PXVRPC2
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
KEYWORDS: PCE
COMPONENT/ENTRY POINT: IMMROUTE
 COMPONENT DESCRIPTION:   Returns Immunization Route Information.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   RESULTS(0)=Count of elements returned (0 if nothing
 found); RESULTS(n)=IEN^Name^HL7 Code^Status (1:Active, 0:Inactive) 
  
 If SITES=1, the sites for a given route will be returned as follows.  
  
 - If only a subset of sites are selectable for a route, that list will be 
 returned in: 
    RESULTS(n+1)=SITE^Site IEN 1 
    RESULTS(n+2)=SITE^Site IEN 2 
    RESULTS(n+x)=SITE^Site IEN x 
  
 - If all sites are selectable for a route, the API will return: 
    RESULTS(n+1)=SITE^ALL 
  
 - If no sites are selectable for a route, the API will return: 
    RESULTS(n+1)=SITE^NONE 
VARIABLES: FILTER                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional; Defaults to "S:B") Filter. Possible values
 are: 
   R:XXX - Return entry with IEN XXX.  
   H:XXX - Return entry with HL7 Code XXX.  
   N:XXX - Return entry with #.01 field equal to XXX 
   S:XY  - Return all entries with a status of X.  
           Possible values of X: 
             A - Active Entries 
             I - Inactive Entries 
             B - Both active and inactive entries 
VARIABLES: SITES                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Controls if the available sites for a give
 route are returned.  
COMPONENT/ENTRY POINT: IMMSRC
 COMPONENT DESCRIPTION:   Returns Immunization Info Source Information.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULTS(0)=Count of elements returned (0 if nothing
 found); RESULTS(n)=IEN^Name^HL7 Code^Status (1:Active, 0:Inactive).  
VARIABLES: FILTER                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional; (Defaults to "S:B"). Possible values are: 
   R:XXX - Return entry with IEN XXX.  
   H:XXX - Return entry with HL7 Code XXX.  
   N:XXX - Return entry with #.01 field equal to XXX 
   S:XY  - Return all entries with a status of X.  
           Possible values of X: 
             A - Active Entries 
             I - Inactive Entries 
             B - Both active and inactive entries 
           Possible values of Y (only applies to file 920.1): 
             A - VA-Administered 
             H - Historical 
COMPONENT/ENTRY POINT: IMMSITE
 COMPONENT DESCRIPTION:   Returns Immunization Admin Site Information.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   RESULTS(0)=Count of elements returned (0 if nothing
 found); RESULTS(n)=IEN^Name^HL7 Code^Status (1:Active, 0:Inactive).  
VARIABLES: FILTER                       TYPE: Input
 VARIABLES DESCRIPTION:   Optional; Defaults to "S:B") Filter. Possible values
 are: 
   R:XXX - Return entry with IEN XXX.  
   H:XXX - Return entry with HL7 Code XXX.  
   N:XXX - Return entry with #.01 field equal to XXX 
   S:XY  - Return all entries with a status of X.  
           Possible values of X: 
             A - Active Entries 
             I - Inactive Entries 
             B - Both active and inactive entries 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 13, 2021

NUMBER: 7284                            IA #: 7284
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXVRPC4
  NAME: PXVRPC4                         ID: PXVRPC4
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
COMPONENT/ENTRY POINT: $$GETUNITS
 COMPONENT DESCRIPTION:   Get the default Dose Units for a given Immunization.  
VARIABLES: IMM                          TYPE: Input
 VARIABLES DESCRIPTION:   (required) Pointer to IMMUNIZATION file #9999999.14.  
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to HOSPITAL LOCATION file (#44).  
COMPONENT/ENTRY POINT: IMMADMCODES
 COMPONENT DESCRIPTION:   Returns Immunization Admin CPT codes.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULT(n) = array of CPT codes to add/delete from
 Visit in format passed to PX SAVE DATA rpc.  
VARIABLES: VISIT                        TYPE: Input
 VARIABLES DESCRIPTION:   Visit IEN 
VARIABLES: PCELIST                      TYPE: Input
 VARIABLES DESCRIPTION:   PCE Array in format passed to PX SAVE DATA rpc
 (Required) 
VARIABLES: RETCPTDEL                    TYPE: Input
 VARIABLES DESCRIPTION:   Should API return other mapped CPT codes (i.e., not
 admin) to delete (Optional) 
COMPONENT/ENTRY POINT: IMMRPC
 COMPONENT DESCRIPTION:   Returns an Immunization entry.  
VARIABLES: RETURN                       TYPE: Output
 VARIABLES DESCRIPTION:   
    ^TMP("PXVIMMRPC",$J,0) 
       1 - Immunization was found. The "1" node will be returned, but the 
           other nodes are optional.  
       -1 - Immunization was not found; no other nodes will be returned.  
    ^TMP("PXVIMMRPC",$J,1) 
       Note: Status (in the 5th piece) is determined as follows: 
         - If DATE is today, the status is based off the Inactive Flag   
           (#.07); 
         - If DATE is different than today, we will look when an update 
           was last made to the Immunization file (based off the Audits).  
           If there have not been any changes since DATE, we will get the 
           status based off the Inactive Flag, otherwise, we will get the 
           status for that date by calling GETSTAT^XTID.  
       1: "IMM" 
       2: #9999999.14 IEN 
       3: Name (#.01) 
       4: CVX Code (#.03) 
       5: Status (1: Active; 0: Inactive) 
       6: Selectable for Historic (#8803) 
       7: Mnemonic (#8801) 
       8: Acronym (#8802) 
       9: Max # In Series (#.05) 
       10: Combination Immunization (Y/N) (#.2) 
       11: Reading Required (#.51) 
       12: Series Required (calculated) 
    ^TMP("PXVIMMRPC",$J,x) 
       1: "VIS" 
       2: #920 IEN 
       3: Name (#920,#.01) 
       4: Edition Date (#920,#.02) 
       5: Edition Status (#920,#.03) 
       6: Language (#920, #.04) 
       7: 2D Bar Code (#100) 
       8: VIS URL (#101) 
    ^TMP("PXVIMMRPC",$J,x) 
       1: "CDC" 
       2: CDC Product Name (#9999999.145, #.01) 
    ^TMP("PXVIMMRPC",$J,x) 
       1: "GROUP" 
       2: Vaccine Group Name (#9999999.147, #.01) 
    ^TMP("PXVIMMRPC",$J,x) 
       1: "SYNONYM" 
       2: Synonym (#9999999.141, #.01) 
    ^TMP("PXVIMMRPC",$J,x) 
       Note: Only active codes (based off PXDATE) are returned.  
       1: "CS" 
       2: Coding System (#9999999.143, #.01) 
       3: Code (#9999999.1431,#.01) 
       4: Variable pointer. e.g., IEN;ICPT( 
       5: Short Description 
    ^TMP("PXVIMMRPC",$J,x) 
       Note: Only active lots for the given division are returned.  
             Also, the Expiration date must be >= PXDATE 
       1: "LOT" 
       2: #9999999.41 IEN 
       3: Lot Number (#9999999.41, #.01) 
       4: Manufacturer (#9999999.04, #.01) 
       5: Expiration Date (#9999999.41, #.09) 
       6: Doses Unused (#9999999.41, #.12) 
       7: Low Supply Alert (#9999999.41, #.15) 
       8: NDC Code (#9999999.41, #.18) 
    ^TMP("PXVIMMRPC",$J,x) 
       Note: Only active contraindications are returned 
       1: "CONTRA" 
       2: #920.4 variable pointer: IEN;PXV(920.4, 
       3: Name (#920.4, #.01) 
       4: Status (1:Active, 0:Inactive) 
       5: Code|Coding System (#920.4, #.02 and .05) 
       6: NIP004 (#920.4, #.04) 
       7: Contraindication/Precaution (#920.4, #.06) 
       8: Allergy-Related (1:Yes, 0:No) 
       9: Default Warn Until Date ("Forever" means it should be forever) 
    ^TMP("PXVIMMRPC",$J,x) 
       1: "DEF" 
       2: Default Route (#920.051, #1302) 
       3: Default Site (#920.051, #1303) 
       4: Default Dose (#920.051, #1312) 
       5: Default Dose Units (#920.051, #1313) 
       6: Default Dose Units (external format) (#920.051, #1313) 
       7: Default Non-Standard Dose Units (#920.051, #1314) 
    ^TMP("PXVIMMRPC",$J,x) 
       1: "DEFC" 
       2: Default Comments (#920.051, #81101) 
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   Immunization status and Codes will be based off this
 date (Optional; Defaults to NOW) 
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   Used to determine Institution (used when filtering
 Lot and Defaults) (Optional) 
    Possible values are: 
      "I:X": Institution (#4) IEN #X 
      "V:X": Visit (#9000010) IEN #X 
      "L:X": Hopital Location (#44) IEN #X If LOC is not passed in OR could not
 make determination based off input, then default to DUZ(2), and if DUZ(2) is
 not defined, default to Default Institution.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 13, 2021

NUMBER: 7285                            IA #: 7285
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXVRPC5
  NAME: PXVRPC5                         ID: PXVRPC5
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
COMPONENT/ENTRY POINT: GETICR
 COMPONENT DESCRIPTION:   Returns entries from the IMM CONTRAINDICATION REASONS
 (#920.4) and IMM REFUSAL REASONS (#920.5) files.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   RESULT(0)=Count of elements returned (0 if nothing
 found) 
  
 For 920.4 Entry: RESULT(n)=IEN;PXV(920.4,^Name^Status (1:Active,
 0:Inactive)^Code|Coding 
           System^NIP004 ^Contraindication/Precaution^Allergy-Related 
           (1:Yes, 0:No)^Default Warn Until Date ("Forever" means it should 
           be forever) 
  
 For 920.5 Entry: RESULT(n)=IEN;PXV(920.5,^Name^Status (1:Active,
 0:Inactive)^HL7 Code^Default Warn Until Date ("Forever" means it should be
 forever) 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   Which file to pull from (Optional; Leave this null to
 pull entries from both files) 
  
 Possible values are: 
   "920.4" - Only return entries from IMM CONTRAINDICATION REASONS (#920.4) 
   "920.5" - Only return entries from IMM REFUSAL REASONS (#920.5) 
VARIABLES: FILTER                       TYPE: Input
 VARIABLES DESCRIPTION:   Filter (Optional; Defaults to "S:A") Possible values
 are: 
    R:X   - Return entry with IEN X (PXFILE must be passed in with this 
            option).  
    C:X^Y - Return entry with Concept Code^Coding System X^Y (used only 
            for #920.4).  
    H:X   - Return entry with HL7 Code X (used only for #920.5).  
    N:X   - Return entry with #.01 field equal to X 
    I:X   - Return all active entries that are selectable for Immunization 
            IEN X.  
    S:A   - Return all active entries.  
    S:I   - Return all inactive entries.  
    S:B   - Return all entries (both active and inactive).  
VARIABLES: INST                         TYPE: Input
 VARIABLES DESCRIPTION:   Institution IEN 
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   Location IEN (If Institution IEN is not passed in,
 the loc will be used to get the institution).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 13, 2021

NUMBER: 7286                            IA #: 7286
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXVRPC8
  NAME: PXVRPC8                         ID: PXVRPC8
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
COMPONENT/ENTRY POINT: GETSKCD
 COMPONENT DESCRIPTION:   Return the CPT code to be used when filing a Skin
 Test Reading.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   An array in the following format: RESULT(n)=Coding
 System (CPT/10D) ^ Code ^ Coding System Abbreviation ^ Coding System
 Nomenclature ^ Code used for P;Placement; R:Reading; B:Both 
VARIABLES: SK                           TYPE: Input
 VARIABLES DESCRIPTION:   Skin Test IEN 
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   Codes will be based off this date.  
COMPONENT/ENTRY POINT: SKLIST
 COMPONENT DESCRIPTION:   Returns a list of V Skin Test entries that have been
 placed within the last x days. The number of days to look back is defined in
 the PXV SK DAYS BACK parameter.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns array in teh following format: 
 RESULT(0)=Count of elements returned (0 if nothing found); RESULT(1)=DATERANGE
 ^ Start Date ^ Stop Date; RESULT(n)=PLACEMENT ^ V Skin Test IEN ^ Skin Test
 IEN ^ Skin Test Name ^ 
     Date/Time of Placement 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
VARIABLES: SK                           TYPE: Input
 VARIABLES DESCRIPTION:   Skin Test IEN (Optional). If passed in, only V Skin
 Test entries for this Skin Test will be returned.  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   Date (Optional; defaults to Today). The system will
 search back x number of days from this date.  
VARIABLES: MAX                          TYPE: Input
 VARIABLES DESCRIPTION:   The max number of entries to return per skin test
 (Optional).  
COMPONENT/ENTRY POINT: SKSITES
 COMPONENT DESCRIPTION:   Returns a list of default sites for skin tests.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns an array (passed by reference) in the
 following format: RESULT(0)=Count of elements returned (0 if nothing found); 
 RESULT(n)=Site IEN (920.3) ^ NAME.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 13, 2021

NUMBER: 7287                            IA #: 7287
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM IMM SHORT LIST
  REMOTE PROCEDURE: PXVIMM IMM SHORT LIST
 GENERAL DESCRIPTION:   NAME: PXVIMM IMM SHORT LIST             TAG: IMMSHORT 
   ROUTINE: PXVRPC4                      RETURN VALUE TYPE: ARRAY 
  DESCRIPTION:   
  Returns a short list of immunizations.  INPUT PARAMETER: FILTER               
  PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Filter (Optional; Defaults to "B") 
  Possible values are: ;               
     "A": Only return active entries 
     "H": Only return entries marked as Selectable for Historic 
     "B": Return both active entries and those marked as Selectable for 
          Historic INPUT PARAMETER: PXDATE                 PARAMETER TYPE:
 LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  Date (optional; defaults to TODAY) 
  Used for determining immunization status (both for filtering and for 
  return value) INPUT PARAMETER: OREXCLUDE              PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 3 
  DESCRIPTION:   
  Should entries defined in ORWPCE EXCLUDE IMMUNIZATIONS be excluded? INPUT
 PARAMETER: LOCATION               PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 4 
  DESCRIPTION:   
  Used when excluding entried listed in ORWPCE EXCLUDE IMMUNIZATIONS. This 
  is the location used when getting the paramater value at the Location 
  level.  
  RETURN PARAMETER DESCRIPTION:   
  PXRTRN(x) 
     Note: Status (in the 5th piece) is determined as follows: 
       - If PXDATE is today, the status is based off the Inactive Flag 
         (#.07) 
       - If PXDATE is different than today, we will look when an update was 
         last made to the Immunization file (based off the Audits). If there 
         have not been any changes since PXDATE, we will get the status 
         based off the Inactive Flag, otherwise, we will get the status for 
         that date by calling GETSTAT^XTID.  
     1: "IMM" 
     2: #9999999.14 IEN 
     3: Name (#.01) 
     4: CVX Code (#.03) 
     5: Status (1: Active; 0: Inactive) 
     6: Selectable for Historic (#8803) 
     7: Mnemonic (#8801) 
     8: Acronym (#8802) 
     9: Active Lot linked to this Immunization? (1:Yes; 0:No) 
  PXRTRN(x) 
     1: "CDC" 
     2: CDC Product Name (#9999999.145, #.01) 
  PXRTRN(x) 
     1: "GROUP" 
     2: Vaccine Group Name  (#9999999.147, #.01) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 21, 2021

NUMBER: 7288                            IA #: 7288
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM IMM DETAILED
  REMOTE PROCEDURE: PXVIMM IMM DETAILED
 GENERAL DESCRIPTION:   NAME: PXVIMM IMM DETAILED               TAG: IMMRPC 
   ROUTINE: PXVRPC4                      RETURN VALUE TYPE: GLOBAL ARRAY 
   WORD WRAP ON: TRUE 
  DESCRIPTION:   
  Returns a detailed Immunization record INPUT PARAMETER: PXIMM                 
 PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Pointer to #9999999.14 (Required) INPUT PARAMETER: PXDATE                
 PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  Immunization status and Codes will be based off this date 
  (Optional; Defaults to NOW) INPUT PARAMETER: PXLOC                  PARAMETER
 TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 3 
  DESCRIPTION:   
  Used to determine Institution, when filtering Lot and Defaults (Optional).  
  Possible values are: 
     "I:X": Institution (#4) IEN #X 
     "V:X": Visit (#9000010) IEN #X 
     "L:X": Hopital Location (#44) IEN #X 
          
  If PXLOC is not passed in OR could not make determination based off input, 
  then default to DUZ(2), and if DUZ(2) is not defined, default to Default 
  Institution.  
  RETURN PARAMETER DESCRIPTION:   
  ^TMP("PXVIMMRPC",$J,0) 
     1:  1 - Immunization was found. The "1" node will be returned, but the 
             other nodes are optional.  
        -1 - Immunization was not found; no other nodes will be returned 
  ^TMP("PXVIMMRPC",$J,1) 
     Note: Status (in the 5th piece) is determined as follows: 
       - If PXDATE is today, the status is based off the Inactive Flag 
         (#.07) 
       - If PXDATE is different than today, we will look when an update was 
         last made to the Immunization file (based off the Audits). If there 
         have not been any changes since PXDATE, we will get the status 
         based off the Inactive Flag, otherwise, we will get the status for 
         that date by calling GETSTAT^XTID.  
     1: "IMM" 
     2: #9999999.14 IEN 
     3: Name (#.01) 
     4: CVX Code (#.03) 
     5: Status (1: Active; 0: Inactive) 
     6: Selectable for Historic (#8803) 
     7: Mnemonic (#8801) 
     8: Acronym (#8802) 
     9: Max # In Series (#.05) 
    10: Combination Immunization (Y/N) (#.2) 
    11: Reading Required (#.51) 
    12: Series Required (calculated) 
  ^TMP("PXVIMMRPC",$J,x) 
     1: "VIS" 
     2: #920 IEN 
     3: Name (#920,#.01) 
     4: Edition Date (#920,#.02) 
     5: Edition Status (#920,#.03) 
     6: Language (#920, #.04) 
     7: 2D Bar Code (#100) 
     8: VIS URL (#101) 
  ^TMP("PXVIMMRPC",$J,x) 
     1: "CDC" 
     2: CDC Product Name (#9999999.145, #.01) 
  ^TMP("PXVIMMRPC",$J,x) 
     1: "GROUP" 
     2: Vaccine Group Name (#9999999.147, #.01) 
  ^TMP("PXVIMMRPC",$J,x) 
     1: "SYNONYM" 
     2: Synonym (#9999999.141, #.01) 
  ^TMP("PXVIMMRPC",$J,x) 
     Note: Only active codes (based off PXDATE) are returned.  
     1: "CS" 
     2: Coding System (#9999999.143, #.01) 
     3: Code (#9999999.1431,#.01) 
     4: Variable pointer. e.g., IEN;ICPT( 
     5: Short Description 
  ^TMP("PXVIMMRPC",$J,x) 
     Note: Only active lots for the given division are returned.  
           Also, the Expiration date must be >= PXDATE 
     1: "LOT" 
     2: #9999999.41 IEN 
     3: Lot Number (#9999999.41, #.01) 
     4: Manufacturer (#9999999.04, #.01) 
     5: Expiration Date (#9999999.41, #.09) 
     6: Doses Unused (#9999999.41, #.12) 
     7: Low Supply Alert (#9999999.41, #.15) 
     8: NDC Code (#9999999.41, #.18) 
  ^TMP("PXVIMMRPC",$J,x) 
     Note: Only active contraindications are returned 
     1: "CONTRA" 
     2: #920.4 variable pointer: IEN;PXV(920.4, 
     3: Name (#920.4, #.01) 
     4: Status (1:Active, 0:Inactive) 
     5: Code|Coding System (#920.4, #.02 and .05) 
     6: NIP004 (#920.4, #.04) 
     7: Contraindication/Precaution (#920.4, #.06) 
     8: Allergy-Related (1:Yes, 0:No) 
     9: Default Warn Until Date ("Forever" means it should be forever) 
  ^TMP("PXVIMMRPC",$J,x) 
     1: "DEF" 
     2: Default Route (#920.051, #1302) 
     3: Default Site (#920.051, #1303) 
     4: Default Dose (#920.051, #1312) 
     5: Default Dose Units (#920.051, #1313) 
     6: Default Dose Units (external format) (#920.051, #1313) 
     7: Default Non-Standard Dose Units (#920.051, #1314) 
  ^TMP("PXVIMMRPC",$J,x) 
     1: "DEFC" 
     2: Default Comments (#920.051, #81101) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 21, 2021

NUMBER: 7289                            IA #: 7289
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM ADMIN SITE
  REMOTE PROCEDURE: PXVIMM ADMIN SITE
 GENERAL DESCRIPTION:   NAME: PXVIMM ADMIN SITE                 TAG: IMMSITE 
   ROUTINE: PXVRPC2                      RETURN VALUE TYPE: ARRAY 
  DESCRIPTION:   
  Returns entries from the IMM ADMINISTRATION SITE (BODY) file (920.3).  INPUT
 PARAMETER: FILTER                 PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Filter. Possible values are: 
     R:XXX - Return entry with IEN XXX.  
     H:XXX - Return entry with HL7 Code XXX.  
     N:XXX - Return entry with #.01 field equal to XXX 
     S:X   - Return all entries with a status of X.  
             Possible values of X: 
                A - Active Entries 
                I - Inactive Entries 
                B - Both active and inactive entries 
   
  Defaults to "S:B".  
  RETURN PARAMETER DESCRIPTION:   
  Returns: 
     PXVRSLT(0)=Count of elements returned (0 if nothing found) 
     PXVRSLT(n)=IEN^Name^HL7 Code^Status (1:Active, 0:Inactive) 
    
  When filtering based off IEN, HL7 Code, or #.01 field, only one entry will 
  be returned in PXVRSLT(1).  
   
  When filtering based off status, multiple entries can be returned. The 
  first entry will be returned in subscript 1, and subscripts will be 
  incremented by 1 for further entries. Entries will be sorted 
  alphabetically.  
   
  If no entries are found based off the filtering criteria, PXVRSLT(0) will 
  equal 0, and there will be no data returned in the subsequent subscripts.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 21, 2021

NUMBER: 7290                            IA #: 7290
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM ICR LIST
  REMOTE PROCEDURE: PXVIMM ICR LIST
 GENERAL DESCRIPTION:   NAME: PXVIMM ICR LIST                   TAG: GETICR 
   ROUTINE: PXVRPC5                      RETURN VALUE TYPE: ARRAY 
  DESCRIPTION:   
  Returns entries from the IMM CONTRAINDICATION REASONS (#920.4) and IMM 
  REFUSAL REASONS (#920.5) files.  INPUT PARAMETER: PXFILE                
 PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Which file to pull from.  
  (Optional; Leave this null to pull entries from both files) 
  Possible values are: 
     "920.4" - Only return entries from IMM CONTRAINDICATION REASONS 
               (#920.4) 
     "920.5" - Only return entries from IMM REFUSAL REASONS (#920.5) INPUT
 PARAMETER: FILTER                 PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  Filter (Optional; Defaults to "S:A") 
  Possible values are: 
     R:X   - Return entry with IEN X (PXFILE must be passed in with this 
             option).  
     C:X^Y - Return entry with Concept Code^Coding System X^Y (used only for 
             #920.4).  
     H:X   - Return entry with HL7 Code X (used only for #920.5).  
     N:X   - Return entry with #.01 field equal to X 
     I:X   - Return all active entries that are selectable for Immunization 
             IEN X.  
     S:A   - Return all active entries.  
     S:I   - Return all inactive entries.  
     S:B   - Return all entries (both active and inactive).  INPUT PARAMETER:
 INST                   PARAMETER TYPE: LITERAL 
   SEQUENCE NUMBER: 3 
  DESCRIPTION:   
  Institution IEN INPUT PARAMETER: LOC                    PARAMETER TYPE:
 LITERAL 
   SEQUENCE NUMBER: 4 
  DESCRIPTION:   
  Location IEN (If Institution IEN is not passed in, the loc will be used 
  to get the institution).  
  RETURN PARAMETER DESCRIPTION:   
  PXRSLT(0)=Count of elements returned (0 if nothing found) 
  For 920.4 Entry: 
     PXRSLT(n)=IEN;PXV(920.4,^Name^Status (1:Active, 0:Inactive)^Code|Coding 
               System^NIP004^Contraindication/Precaution^Allergy-Related 
               (1:Yes, 0:No)^Default Warn Until Date ("Forever" means it 
               should be forever) 
  For 920.5 Entry: 
     PXRSLT(n)=IEN;PXV(920.5,^Name^Status (1:Active, 0:Inactive)^HL7 
               Code^Default Warn Until Date ("Forever" means it should be 
               forever) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 21, 2021

NUMBER: 7291                            IA #: 7291
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM INFO SOURCE
  REMOTE PROCEDURE: PXVIMM INFO SOURCE
 GENERAL DESCRIPTION:   NAME: PXVIMM INFO SOURCE                TAG: IMMSRC 
   ROUTINE: PXVRPC2                      RETURN VALUE TYPE: ARRAY 
  DESCRIPTION:   
  Returns entries from the IMMUNIZATION INFO SOURCE file (920.1).  INPUT
 PARAMETER: FILTER                 PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Filter. Possible values are: 
     R:XXX - Return entry with IEN XXX.  
     H:XXX - Return entry with HL7 Code XXX.  
     N:XXX - Return entry with #.01 field equal to XXX 
     S:X   - Return all entries with a status of X.  
             Possible values of X: 
                A - Active Entries 
                I - Inactive Entries 
                B - Both active and inactive entries 
   
  Defaults to "S:B".  
  RETURN PARAMETER DESCRIPTION:   
  Returns: 
     PXVRSLT(0)=Count of elements returned (0 if nothing found) 
     PXVRSLT(n)=IEN^Name^HL7 Code^Status (1:Active, 0:Inactive) 
    
  When filtering based off IEN, HL7 Code, or #.01 field, only one entry will 
  be returned in PXVRSLT(1).  
   
  When filtering based off status, multiple entries can be returned. The 
  first entry will be returned in subscript 1, and subscripts will be 
  incremented by 1 for further entries. Entries will be sorted 
  alphabetically.  
   
  If no entries are found based off the filtering criteria, PXVRSLT(0) will 
  equal 0, and there will be no data returned in the subsequent subscripts.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 21, 2021

NUMBER: 7292                            IA #: 7292
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM VICR EVENTS
  REMOTE PROCEDURE: PXVIMM VICR EVENTS
 GENERAL DESCRIPTION:   NAME: PXVIMM VICR EVENTS                TAG: GETVICR 
   ROUTINE: PXVRPC5                      RETURN VALUE TYPE: ARRAY 
  DESCRIPTION:   
  Returns "active" entries from the V IMM CONTRA/REFUSAL EVENTS file 
  (#9000010.707) that are related to the given patient and immunization.  
  "Active" is defined as entries where the Event Date and Time is <= 
  PXDATE@24 and the Warn Until Date is null or>= PXDATE.  INPUT PARAMETER: DFN  
                  PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Pointer to file #2.  INPUT PARAMETER: PXVIMM                 PARAMETER TYPE:
 LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  Pointer to #9999999.14.  INPUT PARAMETER: PXDATE                 PARAMETER
 TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 3 
  DESCRIPTION:   
  Used to determine if entry is "active" (Optional; Defaults to TODAY) 
  Possible values are: 
     "L": Return a caret-delimited list of entries.  
     "W": Returns a warning message.  INPUT PARAMETER: PXFORMAT              
 PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 4 
  DESCRIPTION:   
  Format that return array should be returned (Optional; Defaults to "L") 
  Possible values are: 
     "L": Return a caret-delimited list of entries.  
     "W": Returns a warning message.  
  RETURN PARAMETER DESCRIPTION:   
  PXRSLT(0)=Count of elements returned (0 if nothing found) 
  If PXFORMAT="L": 
     PXRSLT(n)="VICR" ^ V IMM Contra/Refusal Events IEN ^ Visit IEN ^ 
               Contra/Refusal variable pointer | Contra/Refusal Name ^ 
               Immunization IEN | Name ^ Warn Until Date ^ D/T Recorded ^ 
               Event D/T ^ Encounter Provider IEN | Name 
     PXRSLT(n)="COM" ^ Comments 
  If PXFORMAT["W": 
     PXRSLT(n)=Warning text 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 21, 2021

NUMBER: 7293                            IA #: 7293
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM IMM MAN
  REMOTE PROCEDURE: PXVIMM IMM MAN
 GENERAL DESCRIPTION:   NAME: PXVIMM IMM MAN                    TAG: IMAN 
   ROUTINE: PXVRPC1                      RETURN VALUE TYPE: GLOBAL ARRAY 
   WORD WRAP ON: TRUE 
  DESCRIPTION:   
  This RPC returns information from the IMM MANUFACTURER file 
  (#9999999.04).  INPUT PARAMETER: FILTER                 PARAMETER TYPE:
 LITERAL 
   MAXIMUM DATA LENGTH: 80               REQUIRED: NO 
   SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  This input parameter is used to specify the IMMUNIZATION LOT file 
  records to be returned. Possible values: 
     R:XXX - return entry with ien XXX 
     M:XXX - return entry with MVX code XXX 
     N:XXX - return entry with imm manufacturer name XXX   
     S:A   - return list of all active manufacturers 
     S:I   - return list of all inactive manufacturers 
     S:B   - return list of all manufacturers, active and inactive 
    
  If this parameter is null, it defaults to "S:B".  INPUT PARAMETER: PXVDATE    
            PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 7                REQUIRED: NO 
   SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  This optional input parameter is used in determining status. Input 
  should be in VA FileMan date format. The default value is the current 
  date.  INPUT PARAMETER: PXVI                   PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 1                REQUIRED: NO 
   SEQUENCE NUMBER: 3 
  DESCRIPTION:   
  This optional input parameter is used to return an alternate array with 
  record data in a caret delimited string. If this parameter is null or 0, 
  the return defaults to the other array.  
     1 - return alternate array with internal values in delimited string 
  RETURN PARAMETER DESCRIPTION:   
  Returns with PXVI not equal to 1: 
     PXVRETRN  - returned information is stored in ^TMP("PXVLST",$J)) 
               - return info format: Data Element Name^Data Element Value 
               -       error format: -1^error message 
   
  For each record returned in the global array, the top value returned will 
  indicate the record number in the array and the total number of records 
  returned, e.g., "RECORD^1 OF 3".  
   
  This RPC returns the internal entry number (IEN) of the record and data 
  in external format from the following data fields in the IMM 
  MANUFACTURER file: 
    - NAME (#.01) 
    - MVX (#.02) 
    - INACTIVE FLAG (#.03) 
    - CDC NOTES (#201) 
    - STATUS (computed by Data Standardization utility) 
   
    Example Global Array Returned: 
    ^TMP("PXVLST",$J,"WYETH-AYERST 1",0)="RECORD^1 OF 1" 
                                   .001)="IEN^55" 
                                    .01)="NAME^WYETH-AYERST" 
                                    .02)="MVX CODE^WA" 
                                    .03)="INACTIVE FLAG^INACTIVE" 
                                    201)="CDC NOTES^became WAL, now owned by 
                                          Pfizer" 
                               "STATUS")="STATUS^INACTIVE" 
   
    Example Global Array Returned if No Records Found: 
    ^TMP("PXVLST",$J,0)="0 RECORDS" 
   
    Example error messages: 
    ^TMP("PXVLST",$J,0)="-1^Invalid input value" 
    ^TMP("PXVLST",$J,0)="-1^Invalid input for manufacturer IEN" 
    ^TMP("PXVLST",$J,0)="-1^Invalid input for MVX code" 
    ^TMP("PXVLST",$J,0)="-1^Invalid input for manufacturer name" 
   
  Returns with PXVI equal to 1: 
     PXVRETRN  - returned information is stored in ^TMP("PXVLST",$J)) 
   
     Each record is a caret-delimited list of values. Within the 
     caret-delimited list, for fields with different internal and external 
     values, both the internal and external values are included, delimited 
     by a tilde (~) as indicated below: 
      Piece# Field# Field Name 
      ------ ------ ----------
      1             IEN             
      2      .01    NAME 
      3      .02    MVX CODE 
      4      .03    INACTIVE FLAG (Internal~External) 
      5      201    CDC NOTES 
      6             STATUS (computed by Data Standardization utility) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 21, 2021

NUMBER: 7294                            IA #: 7294
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM ADMIN ROUTE
  REMOTE PROCEDURE: PXVIMM ADMIN ROUTE
 GENERAL DESCRIPTION:   NAME: PXVIMM ADMIN ROUTE                TAG: IMMROUTE 
   ROUTINE: PXVRPC2                      RETURN VALUE TYPE: ARRAY 
  DESCRIPTION:   
  Returns entries from the IMM ADMINISTRATION ROUTE file (920.2).  INPUT
 PARAMETER: FILTER                 PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Filter. Possible values are: 
     R:XXX - Return entry with IEN XXX.  
     H:XXX - Return entry with HL7 Code XXX.  
     N:XXX - Return entry with #.01 field equal to XXX 
     S:X   - Return all entries with a status of X.  
             Possible values of X: 
                A - Active Entries 
                I - Inactive Entries 
                B - Both active and inactive entries 
   
  Defaults to "S:B".  INPUT PARAMETER: PXVSITES               PARAMETER TYPE:
 LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  Controls if the available sites for a give route are returned.  
  RETURN PARAMETER DESCRIPTION:   
  PXVRSLT(0)=Count of elements returned (0 if nothing found) 
  PXVRSLT(n)=IEN^Name^HL7 Code^Status (1:Active, 0:Inactive) 
   
  If PXVSITES=1, the sites for a given route will also be returned.  
     o If only a subset of sites are selectable for a route, that list will 
       be returned in: 
         PXVRSLT(n+1)=SITE^Site IEN 1 
         PXVRSLT(n+2)=SITE^Site IEN 2 
         PXVRSLT(n+x)=SITE^Site IEN x 
     o If all sites are selectable for a route, the RPC will return: 
         PXVRSLT(n+1)=SITE^ALL 
     o If no sites are selectable for a route, the RPC will return: 
         PXVRSLT(n+1)=SITE^NONE 
  equal 0, and there will be no data returned in the subsequent subscripts.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 21, 2021

NUMBER: 7295                            IA #: 7295
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVSK DEF SITES
  REMOTE PROCEDURE: PXVSK DEF SITES
 GENERAL DESCRIPTION:   NAME: PXVSK DEF SITES                   TAG: SKSITES 
   ROUTINE: PXVRPC8                      RETURN VALUE TYPE: ARRAY 
   AVAILABILITY: SUBSCRIPTION 
  DESCRIPTION:   
  Returns a list of default administration sites for skin tests.  
  RETURN PARAMETER DESCRIPTION:   
  (0)=Count of elements returned (0 if nothing found) 
  (n)=IEN^NAME 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 21, 2021

NUMBER: 7296                            IA #: 7296
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVSK SKIN SHORT LIST
  REMOTE PROCEDURE: PXVSK SKIN SHORT LIST
 GENERAL DESCRIPTION:   NAME: PXVSK SKIN SHORT LIST             TAG: SKSHORT 
   ROUTINE: PXVRPC8                      RETURN VALUE TYPE: ARRAY 
   AVAILABILITY: SUBSCRIPTION 
  DESCRIPTION:   
  Returns one or more entries from the Skin Test file.  INPUT PARAMETER: DATE   
                PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Used for determining skin test status. (Defaults to TODAY).  INPUT PARAMETER:
 FILTER                 PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  Used to filter entries. (Optional; Defaults to "S:A").  
   
  Possible values are: 
     R:X - Return entry with IEN X.  
     N:X - Return entry with #.01 field equal to X 
     S:A - Return all active entries.  
     S:I - Return all inactive entries.  
     S:B - Return all entries (both active and inactive). INPUT PARAMETER:
 OREXCLUDE              PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 3 
  DESCRIPTION:   
  Should entries defined in ORWPCE EXCLUDE SKIN TESTS be excluded? (Used 
  when PXFLTR is set to S:x).  INPUT PARAMETER: LOCATION              
 PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 4 
  DESCRIPTION:   
  Used when excluding entried listed in ORWPCE EXCLUDE SKIN TESTS. This 
  is the location used when getting the paramater value at the Location 
  level.  
  RETURN PARAMETER DESCRIPTION:   
  (0)=Count of elements returned (0 if nothing found) 
  (n)=SK^IEN^NAME^PRINT NAME 
  (n)=CS^Coding System^Code^Variable pointer^Short Description 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 21, 2021

NUMBER: 7297                            IA #: 7297
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVSK V SKIN TEST LIST
  REMOTE PROCEDURE: PXVSK V SKIN TEST LIST
 GENERAL DESCRIPTION:   NAME: PXVSK V SKIN TEST LIST            TAG: SKLIST 
   ROUTINE: PXVRPC8                      RETURN VALUE TYPE: ARRAY 
   AVAILABILITY: SUBSCRIPTION 
  DESCRIPTION:   
  Returns a list of V Skin Test entries that have been placed within the 
  last x days. The number of days to look back is defined in the PXV SK DAYS 
  BACK parameter.  INPUT PARAMETER: DFN                    PARAMETER TYPE:
 LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Only V Skin Test entries for this patient will be returned.  INPUT PARAMETER:
 SKINTEST               PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  Skin Test IEN. If passed in, only V Skin Test entries for this Skin Test 
  will be returned. If not passed in, all V Skin Tests entries will be 
  returned.  INPUT PARAMETER: DATE                   PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 3 
  DESCRIPTION:   
  The system will search back x number of days from this date. Defaults to 
  TODAY.  INPUT PARAMETER: MAX                    PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 4 
  DESCRIPTION:   
  The max number of entries to return per skin test.  
  RETURN PARAMETER DESCRIPTION:   
  (0)=Count of elements returned (0 if nothing found) 
  (1)=DATERANGE^Start Date^Stop Date 
  (n)=PLACEMENT^V Skin Test IEN^Skin Test IEN^Skin Test Name^Date/Time of 
  Placement 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 21, 2021

NUMBER: 7298                            IA #: 7298
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXVIMM ADMIN CODES
  REMOTE PROCEDURE: PXVIMM ADMIN CODES
 GENERAL DESCRIPTION:   NAME: PXVIMM ADMIN CODES                TAG:
 IMMADMCODES 
   ROUTINE: PXVRPC4                      RETURN VALUE TYPE: ARRAY 
  DESCRIPTION:   
  Returns immunization administration CPT codes.  INPUT PARAMETER: VISIT        
          PARAMETER TYPE: LITERAL 
   SEQUENCE NUMBER: 1 INPUT PARAMETER: PCELIST                PARAMETER TYPE:
 LIST 
   REQUIRED: YES                         SEQUENCE NUMBER: 2 INPUT PARAMETER:
 RETCPTDEL              PARAMETER TYPE: LITERAL 
   SEQUENCE NUMBER: 3 
  RETURN PARAMETER DESCRIPTION:   
  PXRSLT(n) = Array of CPT codes to add/delete from Visit in format passed 
  to PX SAVE DATA rpc.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 21, 2021

NUMBER: 7299                            IA #: 7299
  DATE CREATED: SEP 03, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: PX ICE WEB                      REMOTE PROCEDURE: PX ICE WEB
 GENERAL DESCRIPTION:   NAME: PX ICE WEB                        TAG: RPC 
   ROUTINE: PXVWICE                      RETURN VALUE TYPE: GLOBAL ARRAY 
   AVAILABILITY: SUBSCRIPTION            WORD WRAP ON: TRUE 
  DESCRIPTION:   
  Call the ICE web service to get the list of recommended immunizations for 
  a given patient.  
  The RPC takes one parameter, the Patient IEN (DFN).  
  See the RETURN PARAMETER DESCRIPTION for the details on the format of the 
  returned array.  
  There must be at least one entry defined in File 920.75, PX ICE WEB 
  SERVER. If there is more than one entry, then the Site Parameter, PX ICE 
  WEB DEFAULT SERVER, specifies which entry is to be used.  INPUT PARAMETER:
 DFN                    PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Patient DFN INPUT PARAMETER: CACHE                  PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  Use cache? 1=Yes; 0=No (default: 1).  
  RETURN PARAMETER DESCRIPTION:   
  If Unsuccessful: 
     0) = -X^Error Message 
           Note: -X can be one of the following values: 
                  -1: Invalid input 
                  -2: Could not make SOAP call (e.g., URL not populated in 
                      920.75, etc.) 
                  -3: HTTP call returned unsuccessful status code (i.e., 
                      Server returned status code other than 200) 
                  -4: Unable to process incoming message from ICE 
     n) = If SOAP call was unsuccessful, this will be the message returned 
          by the ICE server.  
   
  If Successful: 
    0) = 1 ^ Number of Lines 
    n) = GRP ^ Vaccine Group Name ^ Group/CVX Code Recommended ^ Group/CVX 
         Display Name ^ Earliest Recommended Date ^ Overdue Date ^ Recommend 
         Code ^ Recommend Display Name ^ Doses Remaining 
           1: GRP 
           2: Vaccine Group Name - This is the vaccine group for this 
              recommendation 
           3: Group/CVX Code Recommended - Vaccine or vaccine group 
              recommended. If a specific vaccine is recommended, this will 
              be the CVX code, in the format C:CVX_Code. More commonly, this 
              will be populated with the vaccine group, in the format 
              G:Group_Name 
           4: Group/CVX Display Name - Display Name for CVX/Group in piece 
              #3.  
           5: Earliest Recommended Date 
           6: Overdue Date 
           7: Recommend Code (currently either RECOMMENDED, 
              FUTURE_RECOMMENDED, CONDITIONALLY_RECOMMENDED, or 
              NOT_RECOMMENDED) 
           8: Recommend Display Name 
           9: Doses Remaining 
    n) = RSN ^ Reason Code ^ Reason Display Name 
           Note: This is the reason(s) for the recommendation above.  
           1: RSN 
           2: Reason Code 
           3: Reason Display Name 
    n) = HIST ^ V Immunization IEN ^ Immunization Name ^ Administered CVX 
         Code ^ Admin date/time ^ Dose Number ^ Component CVX Code ^ CVX 
         Display Name ^ Validity Code ^ Validity Display Name 
           1: HIST 
           2: V Immunization IEN (#9000010.11 IEN) 
           3: Immunization Name (#9999999.14, #.01) 
           4: Administered CVX Code (#9999999.14, #.03) 
           5: Admin date/time 
           6: Dose Number 
           7: Component CVX Code (for combination vaccines, this can defer 
              from the CVX administered) 
           8: CVX Display Name 
           9: Validity Code 
          10: Validity Display Name 
    n) = RSN ^ Reason Code ^ Reason Display Name 
           Note: This is the reason(s) why the vaccine is valid, invalid or 
                 accepted. 
           1: RSN 
           2: Reason Code 
           3: Reason Display Name 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: VIMM
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 7300                            IA #: 7300
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: SEP 16, 2021            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: INDIAN SELF IDENTIFICATION CHANGE
  ID: DPT(
GLOBAL REFERENCE: DPT('AINC',
 GENERAL DESCRIPTION:   Integrated Billing (IB) requires read-only access to
 the following cross-reference in the PATIENT (#2) file. It will be used to
 identify any changes in Indian Attestation in order to identify which
 Veteran's need to have their accounts reviewed for the possible cancellation
 of 1st party copayment charges per their Indian Attestation: 
  
   AINC    REGULAR 
             Field:  INDIAN SELF IDENT CHANGE DT/TM  (2,.575) 
       Description:  (Reference ICR#7300) 
                     1)= S ^DPT("AINC",$E(X,1,30),DA)="" 
                     2)= K ^DPT("AINC",$E(X,1,30),DA) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: INDIAN SELF IDENTIFICATION
KEYWORDS: INDIAN ATTESTATION
KEYWORDS: IBINRPT
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: DEC 08, 2021

NUMBER: 7301                            IA #: 7301
  DATE CREATED: SEP 21, 2021
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: GMRA EDIT VERIFIED DATA
 GENERAL DESCRIPTION:   This ICR covers the use of the GMRA EDIT VERIFIED DATA
 extended action protocol, effective with GMRA*4*68. This protocol is triggered
 by Adverse Reaction Tracking when a clinical user with the GMRA-ALLERGY VERIFY
 key edits a previously verified adverse reaction.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ART
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   VPR GMRA EVENTS is the subscribing protocol listener,
 which will be released in a VPR patch after GMRA*4*68 is released. Used to
 update HealthShare SDA if/when verified data is updated in ART.  
  DATE ACTIVATED: SEP 21, 2021

NUMBER: 7302                            IA #: 7302
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  NAME: ENTERED IN ERROR                STATUS: Pending

NUMBER: 7303                            IA #: 7303
  FILE NUMBER: 36                       GLOBAL ROOT: DIC(36,
  DATE CREATED: OCT 15, 2021            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: LIGHTHOUSE INSURANCE COMPANY ICR
  ID: DIC(36,
GLOBAL REFERENCE: DIC(36,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05                       FIELD NAME: INACTIVE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: ALLOW MULTIPLE BEDSECTIONS
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .07
  FIELD NAME: DIFFERENT REVENUE CODES TO USE
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .08                       FIELD NAME: ONE OPT. VISIT ON BILL ONLY
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .12                       FIELD NAME: FILING TIME FRAME
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .13                       FIELD NAME: TYPE OF COVERAGE
  LOCATION: .12;9                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .15                       FIELD NAME: PRESCRIPTION REFILL REV.CODE
  LOCATION: 0;15                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .17                       FIELD NAME: PROFESSIONAL PROVIDER NUMBER
  LOCATION: 0;17                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .18                       FIELD NAME: STANDARD FTF
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .19                       FIELD NAME: STANDARD FTF VALUE
  LOCATION: 0;19                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: REIMBURSE
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: REIMBURSE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .09                       FIELD NAME: AMBULATORY SURG. REV. CODE
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .1                        FIELD NAME: ATTENDING PHYSICIAN ID.
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,.11)
FIELD NUMBER: .111                      FIELD NAME: STREET ADDRESS [LINE 1]
  LOCATION: .11;1                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .112                      FIELD NAME: STREET ADDRESS [LINE 2]
  LOCATION: .11;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .113                      FIELD NAME: STREET ADDRESS [LINE 3]
  LOCATION: .11;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .114                      FIELD NAME: CITY
  LOCATION: .11;4                       ACCESS: Direct Global 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: BILLING COMPANY NAME
  LOCATION: .11;7                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .119                      FIELD NAME: FAX NUMBER
  LOCATION: .11;9                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,.12)
FIELD NUMBER: .121
  FIELD NAME: CLAIMS (INPT) STREET ADDRESS 1
  LOCATION: .12;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .122
  FIELD NAME: CLAIMS (INPT) STREET ADDRESS 2
  LOCATION: .12;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .123
  FIELD NAME: CLAIMS (INPT) STREET ADDRESS 3
  LOCATION: .12;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .124                      FIELD NAME: CLAIMS (INPT) PROCESS CITY
  LOCATION: .12;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .125                      FIELD NAME: CLAIMS (INPT) PROCESS STATE
  LOCATION: .12;5                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .126                      FIELD NAME: CLAIMS (INPT) PROCESS ZIP
  LOCATION: .12;6                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .127                      FIELD NAME: CLAIMS (INPT) COMPANY NAME
  LOCATION: .12;7                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .128
  FIELD NAME: ANOTHER CO. PROCESS IP CLAIMS
  LOCATION: .12;8                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .129                      FIELD NAME: CLAIMS (INPT) FAX
  LOCATION: .12;9                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,.13)
FIELD NUMBER: .131                      FIELD NAME: PHONE NUMBER
  LOCATION: .13;1                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .132                      FIELD NAME: BILLING PHONE NUMBER
  LOCATION: .13;2                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .1311                     FIELD NAME: CLAIMS (RX) PHONE NUMBER
  LOCATION: .13;11                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .133
  FIELD NAME: PRECERTIFICATION PHONE NUMBER
  LOCATION: .13;3                       ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: .134                      FIELD NAME: VERIFICATION PHONE NUMBER
  LOCATION: .13;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .135                      FIELD NAME: CLAIMS (INPT) PHONE NUMBER
  LOCATION: .13;5                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .136                      FIELD NAME: CLAIMS (OPT) PHONE NUMBER
  LOCATION: .13;6                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .137                      FIELD NAME: APPEALS PHONE NUMBER
  LOCATION: .13;7                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .138                      FIELD NAME: INQUIRY PHONE NUMBER
  LOCATION: .13;8                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .139                      FIELD NAME: PRECERT COMPANY NAME
  LOCATION: .13;9                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,.14)
FIELD NUMBER: .141                      FIELD NAME: APPEALS ADDRESS ST. [LINE 1]
  LOCATION: .14;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .142                      FIELD NAME: APPEALS ADDRESS ST. [LINE 2]
  LOCATION: .14;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .143                      FIELD NAME: APPEALS ADDRESS ST. [LINE 3]
  LOCATION: .14;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .144                      FIELD NAME: APPEALS ADDRESS CITY
  LOCATION: .14;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .145                      FIELD NAME: APPEALS ADDRESS STATE
  LOCATION: .14;5                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .146                      FIELD NAME: APPEALS ADDRESS ZIP
  LOCATION: .14;6                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .147                      FIELD NAME: APPEALS COMPANY NAME
  LOCATION: .14;7                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .148                      FIELD NAME: ANOTHER CO. PROCESS APPEALS
  LOCATION: .14;8                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .149                      FIELD NAME: APPEALS FAX
  LOCATION: .14;9                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,.15)
FIELD NUMBER: .151                      FIELD NAME: INQUIRY ADDRESS ST. [LINE 1]
  LOCATION: .15;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .152                      FIELD NAME: INQUIRY ADDRESS ST. [LINE 2]
  LOCATION: .15;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .153                      FIELD NAME: INQUIRY ADDRESS ST. [LINE 3]
  LOCATION: .15;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .154                      FIELD NAME: INQUIRY ADDRESS CITY
  LOCATION: .15;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .155                      FIELD NAME: INQUIRY ADDRESS STATE
  LOCATION: .15;5                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .156                      FIELD NAME: INQUIRY ADDRESS ZIP CODE
  LOCATION: .15;6                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .157                      FIELD NAME: INQUIRY COMPANY NAME
  LOCATION: .15;7                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .158
  FIELD NAME: ANOTHER CO. PROCESS INQUIRIES
  LOCATION: .15;8                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .159                      FIELD NAME: INQUIRY FAX
  LOCATION: .15;9                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,.16)
FIELD NUMBER: .161
  FIELD NAME: CLAIMS (OPT) STREET ADDRESS 1
  LOCATION: .16;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .162
  FIELD NAME: CLAIMS (OPT) STREET ADDRESS 2
  LOCATION: .16;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .163
  FIELD NAME: CLAIMS (OPT) STREET ADDRESS 3
  LOCATION: .16;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .164                      FIELD NAME: CLAIMS (OPT) PROCESS CITY
  LOCATION: .16;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .165                      FIELD NAME: CLAIMS (OPT) PROCESS STATE
  LOCATION: .16;5                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .166                      FIELD NAME: CLAIMS (OPT) PROCESS ZIP
  LOCATION: .16;6                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .167                      FIELD NAME: CLAIMS (OPT) COMPANY NAME
  LOCATION: .16;7                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .168
  FIELD NAME: ANOTHER CO. PROCESS OP CLAIMS
  LOCATION: .16;8                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .169                      FIELD NAME: CLAIMS (OPT) FAX
  LOCATION: .16;9                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,.17)
FIELD NUMBER: .178                      FIELD NAME: ANOTHER CO. PROCESS PRECERTS
  LOCATION: .17;8                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,.18)
FIELD NUMBER: .181                      FIELD NAME: CLAIMS (RX) STREET ADDRESS 1
  LOCATION: .18;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .182                      FIELD NAME: CLAIMS (RX) STREET ADDRESS 2
  LOCATION: .18;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .183                      FIELD NAME: CLAIMS (RX) STREET ADDRESS 3
  LOCATION: .18;3                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .184                      FIELD NAME: CLAIMS (RX) CITY
  LOCATION: .18;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .185                      FIELD NAME: CLAIMS (RX) STATE
  LOCATION: .18;5                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .186                      FIELD NAME: CLAIMS (RX) ZIP
  LOCATION: .18;6                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .187                      FIELD NAME: CLAIMS (RX) COMPANY NAME
  LOCATION: .18;7                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .188
  FIELD NAME: ANOTHER CO. PROCESS RX CLAIMS
  LOCATION: .18;8                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .189                      FIELD NAME: CLAIMS (RX) FAX
  LOCATION: .18;9                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,.19)
FIELD NUMBER: .191
  FIELD NAME: CLAIMS (DENTAL) STREET ADDR 1
  LOCATION: .19;1                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .1911                     FIELD NAME: CLAIMS (DENTAL) PHONE NUMBER
  LOCATION: .19;11                      ACCESS: Both R/W w/Fileman
FIELD NUMBER: .192
  FIELD NAME: CLAIMS (DENTAL) STREET ADDR 2
  LOCATION: .19;2                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .194                      FIELD NAME: CLAIMS (DENTAL) PROCESS CITY
  LOCATION: .19;4                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .195
  FIELD NAME: CLAIMS (DENTAL) PROCESS STATE
  LOCATION: .19;5                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .196                      FIELD NAME: CLAIMS (DENTAL) PROCESS ZIP
  LOCATION: .19;6                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .197                      FIELD NAME: CLAIMS (DENTAL) COMPANY NAME
  LOCATION: .19;7                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .198                      FIELD NAME: ANOTHER CO. PROC DENT CLAIMS
  LOCATION: .19;8                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: .199                      FIELD NAME: CLAIMS (DENTAL) FAX
  LOCATION: .19;9                       ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,3)
FIELD NUMBER: 3.01                      FIELD NAME: TRANSMIT ELECTRONICALLY
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.02                      FIELD NAME: EDI ID NUMBER - PROF
  LOCATION: 3;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.03                      FIELD NAME: BIN NUMBER
  LOCATION: 3;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.04                      FIELD NAME: EDI ID NUMBER - INST
  LOCATION: 3;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.05                      FIELD NAME: LAST EXTRACT DATE FOR TEST
  LOCATION: 3;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.06
  FIELD NAME: MAX NUMBER TEST BILLS PER DAY
  LOCATION: 3;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.07
  FIELD NAME: NUMBER TEST BILLS FOR LAST DT
  LOCATION: 3;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.09                      FIELD NAME: ELECTRONIC INSURANCE TYPE
  LOCATION: 3;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.1                       FIELD NAME: PAYER
  LOCATION: 3;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.13                      FIELD NAME: INS COMPANY LINK TYPE
  LOCATION: 3;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.14                      FIELD NAME: INS COMPANY LINK PARENT
  LOCATION: 3;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.15                      FIELD NAME: EDI ID NUMBER - DENTAL
  LOCATION: 3;15                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,4)
FIELD NUMBER: 4.01
  FIELD NAME: PERF PROV SECOND ID TYPE 1500
  LOCATION: 4;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.02                      FIELD NAME: PERF PROV SECOND ID TYPE UB
  LOCATION: 4;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.03                      FIELD NAME: SECONDARY ID REQUIREMENTS
  LOCATION: 4;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.04                      FIELD NAME: REF PROV SEC ID DEF CMS-1500
  LOCATION: 4;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.05
  FIELD NAME: REF PROV SEC ID REQ ON CLAIMS
  LOCATION: 4;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.06                      FIELD NAME: ATT/REND ID BILL SEC ID PROF
  LOCATION: 4;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.08                      FIELD NAME: ATT/REND ID BILL SEC ID INST
  LOCATION: 4;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.09                      FIELD NAME: PERF PROV CARE UNIT PROMPT
  LOCATION: 4;9                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,6)
FIELD NUMBER: 6.01
  FIELD NAME: EDI INST SECONDARY ID QUAL(1)
  LOCATION: 6;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6.02                      FIELD NAME: EDI INST SECONDARY ID(1)
  LOCATION: 6;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6.03
  FIELD NAME: EDI INST SECONDARY ID QUAL(2)
  LOCATION: 6;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6.04                      FIELD NAME: EDI INST SECONDARY ID(2)
  LOCATION: 6;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6.05
  FIELD NAME: EDI PROF SECONDARY ID QUAL(1)
  LOCATION: 6;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6.06                      FIELD NAME: EDI PROF SECONDARY ID(1)
  LOCATION: 6;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6.07
  FIELD NAME: EDI PROF SECONDARY ID QUAL(2)
  LOCATION: 6;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6.08                      FIELD NAME: EDI PROF SECONDARY ID(2)
  LOCATION: 6;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6.09                      FIELD NAME: PRINT SEC/TERT AUTO CLAIMS
  LOCATION: 6;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6.1                       FIELD NAME: PRINT SEC MED CLAIMS W/O MRA
  LOCATION: 6;10                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,7)
FIELD NUMBER: 7.01                      FIELD NAME: EDI - UMO (278) ID
  LOCATION: 7;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,8)
FIELD NUMBER: 8.01                      FIELD NAME: HPID/OEID
  LOCATION: 8;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.02                      FIELD NAME: CHP/SHP
  LOCATION: 8;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.03                      FIELD NAME: PARENT CHP (HPID)
  LOCATION: 8;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.04                      FIELD NAME: NIF ID
  LOCATION: 8;4                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DIC(36,D0,10,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SYNONYM
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   SYNONYM (Multiple-36.03) 
GLOBAL REFERENCE: DIC(36,D0,13,D1,0)
FIELD NUMBER: .01
  FIELD NAME: PLAN TYPES NO BILL PRV SEC ID
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   PLAN TYPES NO BILL PRV SEC ID (Multiple-36.013) 
GLOBAL REFERENCE: DIC(36,D0,17,D1,0)
FIELD NUMBER: .01                       FIELD NAME: 277EDI ID NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: 277DATE EDI ID NUMBER
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: 277EDI TYPE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: 277EDI ID NUMBER ON FILE
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   277EDI ID NUMBER (Multiple-36.017) 
GLOBAL REFERENCE: DIC(36,D0,AJK1UB)
FIELD NUMBER: 580950.01                 FIELD NAME: COLLECTIONS DOLLAR LIMIT
  LOCATION: AJK1UB;1                    ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Lighthouse requires access to the INSURANCE COMPANY
 file #36 to support the AMCMS/WellHive Insurance Capture initiative.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LIGHTHOUSE

NUMBER: 7304                            IA #: 7304
  FILE NUMBER: 355.3                    GLOBAL ROOT: IBA(355.3,
  DATE CREATED: OCT 15, 2021            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: LIGHTHOUSE GROUP INSURANCE PLAN ICR
  ID: IBA(355.3,
GLOBAL REFERENCE: IBA(355.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: INSURANCE COMPANY
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: IS THIS A GROUP POLICY
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05
  FIELD NAME: IS UTILIZATION REVIEW REQUIRED
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06
  FIELD NAME: IS PRE-CERTIFICATION REQUIRED?
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .08                       FIELD NAME: BENEFITS ASSIGNABLE?
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .09                       FIELD NAME: TYPE OF PLAN
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .1                        FIELD NAME: INDIVIDUAL POLICY PATIENT
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .11                       FIELD NAME: INACTIVE
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: .12
  FIELD NAME: AMBULATORY CARE CERTIFICATION
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .13                       FIELD NAME: PLAN FILING TIME FRAME
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .14                       FIELD NAME: PLAN CATEGORY
  LOCATION: 0;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .15                       FIELD NAME: ELECTRONIC PLAN TYPE
  LOCATION: 0;15                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .16                       FIELD NAME: PLAN STANDARD FTF
  LOCATION: 0;16                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .17                       FIELD NAME: PLAN STANDARD FTF VALUE
  LOCATION: 0;17                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBA(355.3,D0,1)
FIELD NUMBER: 1.03                      FIELD NAME: DATE LAST VERIFIED
  LOCATION: 1;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 1.04                      FIELD NAME: VERIFIED BY
  LOCATION: 1;4                         ACCESS: Write w/Fileman
FIELD NUMBER: 1.05                      FIELD NAME: DATE LAST EDITED
  LOCATION: 1;5                         ACCESS: Write w/Fileman
FIELD NUMBER: 1.06                      FIELD NAME: LAST EDITED BY
  LOCATION: 1;6                         ACCESS: Write w/Fileman
GLOBAL REFERENCE: IBA(355.3,D0,2)
FIELD NUMBER: 2.01                      FIELD NAME: GROUP NAME
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.02                      FIELD NAME: GROUP NUMBER
  LOCATION: 2;2                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBA(355.3,D0,6)
FIELD NUMBER: 6.01                      FIELD NAME: PLAN ID
  LOCATION: 6;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6.02
  FIELD NAME: BANKING IDENTIFICATION NUMBER
  LOCATION: 6;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6.03                      FIELD NAME: PROCESSOR CONTROL NUMBER
  LOCATION: 6;3                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBA(355.3,D0,11,D1,0)
FIELD NUMBER: .01                       FIELD NAME: COMMENTS
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Lighthouse requires access to the GROUP INSURANCE PLAN
 file #355.3 to support the AMCMS/WellHive Insurance Capture initiative.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LIGHTHOUSE

NUMBER: 7305                            IA #: 7305
  FILE NUMBER: 355.32                   GLOBAL ROOT: IBA(355.32,
  DATE CREATED: OCT 15, 2021            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: LIGHTHOUSE PLAN COVERAGE LIMITATIONS ICR
  ID: IBA(355.32,
GLOBAL REFERENCE: IBA(355.32,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PLAN
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: COVERAGE CATEGORY
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: EFFECTIVE DATE
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: COVERAGE STATUS
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBA(355.32,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: COMMENTS
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   LIMITATION COMMENT (Multiple-355.321) 
GLOBAL REFERENCE: IBA(355.32,D0,1)
FIELD NUMBER: 1.01                      FIELD NAME: DATE ENTERED
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.02                      FIELD NAME: ENTERED BY
  LOCATION: 1;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.03                      FIELD NAME: DATE LAST EDITED
  LOCATION: 1;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.04                      FIELD NAME: LAST EDITED BY
  LOCATION: 1;4                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Lighthouse requires access to the PLAN COVERAGE
 LIMITATIONS file #355.32 to support the AMCMS/WellHive Insurance Capture
 initiative.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LIGHTHOUSE

NUMBER: 7306                            IA #: 7306
  FILE NUMBER: 365.12                   GLOBAL ROOT: IBE(365.12
  DATE CREATED: OCT 15, 2021            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: LIGHTHOUSE PAYER FILE ICR       ID: IBE(365.12
GLOBAL REFERENCE: IBE(365.12,D0,0)
FIELD NUMBER: .01                       FIELD NAME: PAYER NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: VA NATIONAL ID
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: CMS NATIONAL ID
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: .04                       FIELD NAME: DATE/TIME CREATED
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: EDI ID NUMBER - PROF
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: EDI ID NUMBER - INST
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: .07                       FIELD NAME: DEACTIVATED
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DATE/TIME DEACTIVATED
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Lighthouse requires access to the PAYER file #365.12 to
 support the AMCMS/WellHive Insurance Capture initiative.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed

NUMBER: 7307                            IA #: 7307
  FILE NUMBER: 2.312                    GLOBAL ROOT: DPT(D0,.312,
  DATE CREATED: OCT 15, 2021            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: LIGHTHOUSE PATIENT INSURANCE TYPE SUBFILE ICR
  ID: DPT(D0,.312,
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: .18                       FIELD NAME: GROUP PLAN
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .2                        FIELD NAME: COORDINATION OF BENEFITS
  LOCATION: 0;20                        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: 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
GLOBAL REFERENCE: DPT(D0,.312,D1,1)
FIELD NUMBER: 1.01                      FIELD NAME: DATE ENTERED
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.02                      FIELD NAME: ENTERED BY
  LOCATION: 1;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.03                      FIELD NAME: DATE LAST VERIFIED
  LOCATION: 1;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.04                      FIELD NAME: VERIFIED BY
  LOCATION: 1;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.05                      FIELD NAME: DATE LAST EDITED
  LOCATION: 1;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.06                      FIELD NAME: LAST EDITED BY
  LOCATION: 1;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.09                      FIELD NAME: SOURCE OF INFORMATION
  LOCATION: 1;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.1
  FIELD NAME: DATE OF SOURCE OF INFORMATION
  LOCATION: 1;10                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.312,D1,2)
FIELD NUMBER: 2.01                      FIELD NAME: SEND BILL TO EMPLOYER
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.015                     FIELD NAME: SUBSCRIBER'S EMPLOYER NAME
  LOCATION: 2;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.02
  FIELD NAME: EMPLOYER CLAIMS STREET ADDRESS
  LOCATION: 2;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.03
  FIELD NAME: EMPLOY CLAIM ST ADDRESS LINE 2
  LOCATION: 2;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.04
  FIELD NAME: EMPLOY CLAIM ST ADDRESS LINE 3
  LOCATION: 2;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.05                      FIELD NAME: EMPLOYER CLAIMS CITY
  LOCATION: 2;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.06                      FIELD NAME: EMPLOYER CLAIMS STATE
  LOCATION: 2;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.07                      FIELD NAME: EMPLOYER CLAIMS ZIP CODE
  LOCATION: 2;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.08                      FIELD NAME: EMPLOYER CLAIMS PHONE
  LOCATION: 2;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.1                       FIELD NAME: EMPLOYMENT STATUS
  LOCATION: 2;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.12                      FIELD NAME: RETIREMENT DATE
  LOCATION: 2;12                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.312,D1,3)
FIELD NUMBER: 3.01                      FIELD NAME: INSURED'S DOB
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.02                      FIELD NAME: INSURED'S BRANCH
  LOCATION: 3;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.03                      FIELD NAME: INSURED'S RANK
  LOCATION: 3;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.04                      FIELD NAME: STOP POLICY FROM BILLING
  LOCATION: 3;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.05                      FIELD NAME: INSURED'S SSN
  LOCATION: 3;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.06                      FIELD NAME: INSURED'S STREET 1
  LOCATION: 3;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.07                      FIELD NAME: INSURED'S STREET 2
  LOCATION: 3;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.08                      FIELD NAME: INSURED'S CITY
  LOCATION: 3;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.09                      FIELD NAME: INSURED'S STATE
  LOCATION: 3;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.1                       FIELD NAME: INSURED'S ZIP
  LOCATION: 3;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.11                      FIELD NAME: INSURED'S PHONE
  LOCATION: 3;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.12                      FIELD NAME: INSURED'S SEX
  LOCATION: 3;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.13                      FIELD NAME: INSURED'S COUNTRY
  LOCATION: 3;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.14
  FIELD NAME: INSURED'S COUNTRY SUBDIVISION
  LOCATION: 3;14                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.312,D1,4)
FIELD NUMBER: 4.01                      FIELD NAME: PRIMARY CARE PROVIDER
  LOCATION: 4;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.02                      FIELD NAME: PRIMARY PROVIDER PHONE
  LOCATION: 4;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.03                      FIELD NAME: PT. RELATIONSHIP - HIPAA
  LOCATION: 4;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.04                      FIELD NAME: EIV AUTO-UPDATE
  LOCATION: 4;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.05                      FIELD NAME: PHARMACY RELATIONSHIP CODE
  LOCATION: 4;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.06                      FIELD NAME: PHARMACY PERSON CODE
  LOCATION: 4;6                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.312,D1,5)
FIELD NUMBER: 5.01                      FIELD NAME: PATIENT ID
  LOCATION: 5;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.02
  FIELD NAME: SUBSCRIBER'S SEC QUALIFIER(1)
  LOCATION: 5;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.03                      FIELD NAME: SUBSCRIBER'S SEC ID(1)
  LOCATION: 5;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.04
  FIELD NAME: SUBSCRIBER'S SEC QUALIFIER(2)
  LOCATION: 5;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.05                      FIELD NAME: SUBSCRIBER'S SEC ID(2)
  LOCATION: 5;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.06
  FIELD NAME: SUBSCRIBER'S SEC QUALIFIER(3)
  LOCATION: 5;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.07                      FIELD NAME: SUBSCRIBER'S SEC ID(3)
  LOCATION: 5;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.08                      FIELD NAME: PATIENT'S SEC QUALIFIER(1)
  LOCATION: 5;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.09                      FIELD NAME: PATIENT'S SECONDARY ID(1)
  LOCATION: 5;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.1                       FIELD NAME: PATIENT'S SEC QUALIFIER(2)
  LOCATION: 5;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.11                      FIELD NAME: PATIENT'S SECONDARY ID(2)
  LOCATION: 5;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.12                      FIELD NAME: PATIENT'S SEC QUALIFIER(3)
  LOCATION: 5;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.13                      FIELD NAME: PATIENT'S SECONDARY ID(3)
  LOCATION: 5;13                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.312,D1,6,D2,0)
FIELD NUMBER: .01                       FIELD NAME: EB NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ELIGIBILITY/BENEFIT INFO
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: COVERAGE LEVEL
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05                       FIELD NAME: INSURANCE TYPE
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: PLAN COVERAGE DESCRIPTION
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .07                       FIELD NAME: TIME PERIOD QUALIFIER
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .08                       FIELD NAME: MONETARY AMOUNT
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .09                       FIELD NAME: PERCENT
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .1                        FIELD NAME: QUANTITY QUALIFIER
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .11                       FIELD NAME: QUANTITY
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .12                       FIELD NAME: AUTHORIZATION/CERTIFICATION
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .13                       FIELD NAME: IN PLAN
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   ELIGIBILITY/BENEFIT (Multiple-2.322) 
GLOBAL REFERENCE: DPT(D0,.312,D1,6,D2,1)
FIELD NUMBER: 1.01                      FIELD NAME: PROCEDURE CODING METHOD
  LOCATION: 1;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.02                      FIELD NAME: PROCEDURE CODE
  LOCATION: 1;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.03                      FIELD NAME: PROCEDURE MODIFIER 1
  LOCATION: 1;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.04                      FIELD NAME: PROCEDURE MODIFIER 2
  LOCATION: 1;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.05                      FIELD NAME: PROCEDURE MODIFIER 3
  LOCATION: 1;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.06                      FIELD NAME: PROCEDURE MODIFIER 4
  LOCATION: 1;6                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.312,D1,6,D2,3)
FIELD NUMBER: 3.01                      FIELD NAME: ENTITY ID CODE
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.02                      FIELD NAME: ENTITY TYPE
  LOCATION: 3;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.03                      FIELD NAME: NAME
  LOCATION: 3;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.04                      FIELD NAME: ENTITY ID
  LOCATION: 3;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.05                      FIELD NAME: ENTITY ID QUALIFIER
  LOCATION: 3;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.06                      FIELD NAME: ENTITY RELATIONSHIP CODE
  LOCATION: 3;6                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.312,D1,6,D2,4)
FIELD NUMBER: 4.01                      FIELD NAME: ADDRESS LINE 1
  LOCATION: 4;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.02                      FIELD NAME: ADDRESS LINE 2
  LOCATION: 4;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.03                      FIELD NAME: CITY
  LOCATION: 4;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.04                      FIELD NAME: STATE
  LOCATION: 4;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.05                      FIELD NAME: ZIP
  LOCATION: 4;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.06                      FIELD NAME: COUNTRY CODE
  LOCATION: 4;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.07                      FIELD NAME: LOCATION
  LOCATION: 4;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.08                      FIELD NAME: LOCATION QUALIFIER
  LOCATION: 4;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.09                      FIELD NAME: SUBDIVISION CODE
  LOCATION: 4;9                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.312,D1,6,D2,5)
FIELD NUMBER: 5.01                      FIELD NAME: PROVIDER CODE
  LOCATION: 5;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.02                      FIELD NAME: REFERENCE ID
  LOCATION: 5;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.03                      FIELD NAME: REFERENCE ID QUALIFIER
  LOCATION: 5;3                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.312,D1,6,D2,8,D3,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DATE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DATE QUALIFIER
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: DATE FORMAT
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   SUBSCRIBER DATES (Multiple-2.3228) 
GLOBAL REFERENCE: DPT(D0,.312,D1,6,D2,6,D3,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: NAME
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: COMMUNICATION QUALIFIER
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: COMMUNICATION NUMBER
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   CONTACT INFORMATION (Multiple-2.3226) 
GLOBAL REFERENCE: DPT(D0,.312,D1,6,D2,6,D3,1)
FIELD NUMBER: 1                         FIELD NAME: COMMUNICATION NUMBER
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.312,D1,6,D2,7,D3,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: BENEFIT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: QUANTITY QUALIFIER
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: SAMPLE SELECTION MODULUS
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05                       FIELD NAME: UNITS OF MEASUREMENT
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: TIME PERIODS
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .07                       FIELD NAME: TIME PERIOD QUALIFIER
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DELIVERY FREQUENCY
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .09                       FIELD NAME: DELIVERY PATTERN
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   HEALTHCARE SERVICES DELIVERY (Multiple-2.3227) 
GLOBAL REFERENCE: DPT(D0,.312,D1,6,D2,9,D3,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PLACE OF SERVICE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DIAGNOSIS
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: QUALIFIER
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05                       FIELD NAME: NATURE OF INJURY CODE
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: NATURE OF INJURY CATEGORY
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .07                       FIELD NAME: NATURE OF INJURY TEXT
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   SUBSCRIBER ADDITIONAL INFO (Multiple-2.3229) 
GLOBAL REFERENCE: DPT(D0,.312,D1,6,D2,10,D3,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: REFERENCE ID
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: REFERENCE ID QUALIFIER
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: DESCRIPTION
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   SUBSCRIBER REFERENCE ID (Multiple-2.32291) 
GLOBAL REFERENCE: DPT(D0,.312,D1,6,D2,11,D3,0)
FIELD NUMBER: .01                       FIELD NAME: SERVICE TYPE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   SERVICE TYPES (Multiple-2.32292) 
GLOBAL REFERENCE: DPT(D0,.312,D1,7)
FIELD NUMBER: 7.01                      FIELD NAME: NAME OF INSURED
  LOCATION: 7;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7.02                      FIELD NAME: SUBSCRIBER ID
  LOCATION: 7;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7.03                      FIELD NAME: SUBSCRIBER ID ROLLBACK
  LOCATION: 7;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 7.04                      FIELD NAME: PATIENT ID ROLLBACK
  LOCATION: 7;4                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.312,D1,8)
FIELD NUMBER: 8.01                      FIELD NAME: REQUESTED SERVICE DATE
  LOCATION: 8;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.02                      FIELD NAME: REQUESTED SERVICE TYPE
  LOCATION: 8;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.03                      FIELD NAME: EB DISPLAY ENTRY
  LOCATION: 8;3                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.312,D1,9,D2,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: REFERENCE ID (GROUP)
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: REF ID QUALIFIER (GROUP)
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: DESCRIPTION
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   GROUP REFERENCE INFORMATION (Multiple-2.3129) 
GLOBAL REFERENCE: DPT(D0,.312,D1,10,D2,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PROVIDER CODE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: PROV REFERENCE ID
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   GROUP PROVIDER INFO (Mulitple-2.332) 
GLOBAL REFERENCE: DPT(D0,.312,D1,11,D2,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DIAGNOSIS CODE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DIAGNOSIS CODE QUALIFIER
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: PRIMARY OR SECONDARY
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   HEALTH CARE CODE INFORMATION (Multiple-2.31211) 
GLOBAL REFERENCE: DPT(D0,.312,D1,12)
FIELD NUMBER: 12.01                     FIELD NAME: MILITARY INFO STATUS CODE
  LOCATION: 12;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.02                     FIELD NAME: MILITARY EMPLOYMENT STATUS
  LOCATION: 12;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.03
  FIELD NAME: MILITARY GOVT AFFILIATION CODE
  LOCATION: 12;3                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.04
  FIELD NAME: MILITARY PERSONNEL DESCRIPTION
  LOCATION: 12;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.05                     FIELD NAME: MILITARY SERVICE RANK CODE
  LOCATION: 12;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.06                     FIELD NAME: DATE TIME PERIOD FORMAT QUAL
  LOCATION: 12;6                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.07                     FIELD NAME: DATE TIME PERIOD
  LOCATION: 12;7                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DPT(D0,.312,D1,13,D2,1)
FIELD NUMBER: .03                       FIELD NAME: COMMENT
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Lighthouse requires access to the Patient Insurance
 Type sub-file #2.312 to support the AMCMS/WellHive Insurance Capture
 initiative.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed

NUMBER: 7308                            IA #: 7308
  FILE NUMBER: 365                      GLOBAL ROOT: IBCN(365,
  DATE CREATED: OCT 15, 2021            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: LIGHTHOUSE IIV RESPONSE FILE ICR
  ID: IBCN(365,
GLOBAL REFERENCE: IBCN(365,D0,0)
FIELD NUMBER: .01                       FIELD NAME: MESSAGE CONTROL ID
  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: .03                       FIELD NAME: PAYER
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: BUFFER ENTRY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: TRANSMISSION QUEUE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: TRANSMISSION STATUS
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .07                       FIELD NAME: DATE/TIME RECEIVED
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DATE/TIME CREATED
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .09                       FIELD NAME: TRACE NUMBER
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .1                        FIELD NAME: RESPONSE TYPE
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .11                       FIELD NAME: DO NOT PURGE
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: .12                       FIELD NAME: INSUR RECORD IEN
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .13                       FIELD NAME: EIV AUTO-UPDATE
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,1)
FIELD NUMBER: 1.02                      FIELD NAME: INSURED DOB
  LOCATION: 1;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.03                      FIELD NAME: INSURED SSN
  LOCATION: 1;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.04                      FIELD NAME: INSURED SEX
  LOCATION: 1;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.08                      FIELD NAME: WHOSE INSURANCE
  LOCATION: 1;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.09                      FIELD NAME: PT RELATIONSHIP TO INSURED
  LOCATION: 1;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.1                       FIELD NAME: SERVICE DATE
  LOCATION: 1;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.11                      FIELD NAME: EFFECTIVE DATE
  LOCATION: 1;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.12                      FIELD NAME: EXPIRATION DATE
  LOCATION: 1;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.13                      FIELD NAME: COORDINATION OF BENEFITS
  LOCATION: 1;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.14                      FIELD NAME: ERROR CONDITION
  LOCATION: 1;14                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.15                      FIELD NAME: ERROR ACTION
  LOCATION: 1;15                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.16                      FIELD NAME: DATE OF DEATH
  LOCATION: 1;16                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.17                      FIELD NAME: CERTIFICATION DATE
  LOCATION: 1;17                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.18                      FIELD NAME: MEMBER ID
  LOCATION: 1;18                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.19                      FIELD NAME: PAYER UPDATED POLICY
  LOCATION: 1;19                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.2                       FIELD NAME: POLICY NUMBER
  LOCATION: 1;20                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: EB NUMBER
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ELIGIBILITY/BENEFIT INFO
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: COVERAGE LEVEL
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05                       FIELD NAME: INSURANCE TYPE
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: PLAN COVERAGE DESCRIPTION
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .07                       FIELD NAME: TIME PERIOD QUALIFIER
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .08                       FIELD NAME: MONETARY AMOUNT
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .09                       FIELD NAME: PERCENT
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .1                        FIELD NAME: QUANTITY QUALIFIER
  LOCATION: 0;10                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .11                       FIELD NAME: QUANTITY
  LOCATION: 0;11                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .12                       FIELD NAME: AUTHORIZATION/CERTIFICATION
  LOCATION: 0;12                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .13                       FIELD NAME: IN PLAN
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   ELIGIBILITY/BENEFIT (Multiple-365.02) 
GLOBAL REFERENCE: IBCN(365,D0,2,D1,1)
FIELD NUMBER: 1.01                      FIELD NAME: PROCEDURE CODING METHOD
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.02                      FIELD NAME: PROCEDURE CODE
  LOCATION: 1;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.03                      FIELD NAME: PROCEDURE MODIFIER 1
  LOCATION: 1;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.04                      FIELD NAME: PROCEDURE MODIFIER 2
  LOCATION: 1;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.05                      FIELD NAME: PROCEDURE MODIFIER 3
  LOCATION: 1;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.06                      FIELD NAME: PROCEDURE MODIFIER 4
  LOCATION: 1;6                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,2,D1,3)
FIELD NUMBER: 3.01                      FIELD NAME: ENTITY ID CODE
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.02                      FIELD NAME: ENTITY TYPE
  LOCATION: 3;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.03                      FIELD NAME: NAME
  LOCATION: 3;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.04                      FIELD NAME: ENTITY ID
  LOCATION: 3;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: ENTITY ID QUALIFIER       FIELD NAME: ENTITY ID QUALIFIIER
  ACCESS: Read w/Fileman
FIELD NUMBER: 3.05                      FIELD NAME: ENTITY ID QUALIFIER
  LOCATION: 3;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.06                      FIELD NAME: ENTITY RELATIONSHIP CODE
  LOCATION: 3;6                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,2,D1,4)
FIELD NUMBER: 4.01                      FIELD NAME: ADDRESS LINE 1
  LOCATION: 4;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.02                      FIELD NAME: ADDRESS LINE 2
  LOCATION: 4;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.03                      FIELD NAME: CITY
  LOCATION: 4;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.04                      FIELD NAME: STATE
  LOCATION: 4;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.05                      FIELD NAME: ZIP
  LOCATION: 4;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.06                      FIELD NAME: COUNTRY CODE
  LOCATION: 4;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.07                      FIELD NAME: LOCATION
  LOCATION: 4;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.08                      FIELD NAME: LOCATION QUALIFIER
  LOCATION: 4;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 4.09                      FIELD NAME: SUBDIVISION CODE
  LOCATION: 4;9                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,2,D1,5)
FIELD NUMBER: 5.01                      FIELD NAME: PROVIDER CODE
  LOCATION: 5;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.02                      FIELD NAME: REFERENCE ID
  LOCATION: 5;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.03                      FIELD NAME: REFERENCE ID QUALIFIER
  LOCATION: 5;3                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,2,D1,6,D2,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: NAME
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: COMMUNICATION QUALIFIER
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   CONTACT INFORMATION (Multiple-365.26) 
GLOBAL REFERENCE: IBCN(365,D0,2,D1,6,D2,1)
FIELD NUMBER: 1                         FIELD NAME: COMMUNICATION NUMBER
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,2,D1,7,D2,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: BENEFIT QUANTITY
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: QUANTITY QUALIFIER
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: SAMPLE SELECTION MODULUS
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05                       FIELD NAME: UNITS OF MEASUREMENT
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: TIME PERIODS
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .07                       FIELD NAME: TIME PERIOD QUALIFIER
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .08                       FIELD NAME: DELIVERY FREQUENCY
  LOCATION: 0;8                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .09                       FIELD NAME: DELIVERY PATTERN
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   HEALTHCARE SERVICES DELIVERY (Multiple-365.27) 
GLOBAL REFERENCE: IBCN(365,D0,2,D1,8,D2,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DATE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DATE QUALIFIER
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: DATE FORMAT
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   SUBSCRIBER DATES (Multiple-365.28) 
GLOBAL REFERENCE: IBCN(365,D0,2,D1,9,D2,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PLACE OF SERVICE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DIAGNOSIS
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: QUALIFIER
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05                       FIELD NAME: NATURE OF INJURY CODE
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: NATURE OF INJURY CATEGORY
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .07                       FIELD NAME: NATURE OF INJURY TEXT
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   SUBSCRIBER ADDITIONAL INFO (Multiple-365.29) 
GLOBAL REFERENCE: IBCN(365,D0,2,D1,10,D2,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: REFERENCE ID
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: REFERENCE ID QUALIFIER
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: DESCRIPTION
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   SUBSCRIBER REFERENCE ID (Multiple-365.291) 
GLOBAL REFERENCE: IBCN(365,D0,2,D1,14,D2,0)
FIELD NUMBER: .01                       FIELD NAME: SERVICE TYPES
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   SERVICE TYPES (Multiple-365.292) 
GLOBAL REFERENCE: IBCN(365,D0,3,D1,0)
FIELD NUMBER: .01                       FIELD NAME: CONTACT PERSON
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: COMMUNICATION QUALIFIER #1
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: COMMUNICATION QUALIFIER #2
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: COMMUNICATION QUALIFIER #3
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   CONTACT PERSON (Multiple-365.03) 
GLOBAL REFERENCE: IBCN(365,D0,3,D1,2)
FIELD NUMBER: 2                         FIELD NAME: COMMUNICATION NUMBER #2
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,3,D1,1)
FIELD NUMBER: 1                         FIELD NAME: COMMUNICATION NUMBER #1
  LOCATION: 1;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,3,D1,3)
FIELD NUMBER: 3                         FIELD NAME: COMMUNICATION NUMBER #3
  LOCATION: 3;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,4)
FIELD NUMBER: 4.01                      FIELD NAME: ERROR TEXT
  LOCATION: 4;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,5)
FIELD NUMBER: 5.01                      FIELD NAME: SUBSCRIBER ADDRESS LINE 1
  LOCATION: 5;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.02                      FIELD NAME: SUBSCRIBER ADDRESS LINE 2
  LOCATION: 5;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.03                      FIELD NAME: SUBSCRIBER ADDRESS CITY
  LOCATION: 5;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.04                      FIELD NAME: SUBSCRIBER ADDRESS STATE
  LOCATION: 5;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.05                      FIELD NAME: SUBSCRIBER ADDRESS ZIP
  LOCATION: 5;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.06                      FIELD NAME: SUBSCRIBER ADDRESS COUNTRY
  LOCATION: 5;6                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.07
  FIELD NAME: SUBSCRIBER ADDRESS SUBDIVISION
  LOCATION: 5;7                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,6,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: ERROR LOCATION
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: REJECT REASON
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: ACTION CODE
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05                       FIELD NAME: LOOP ID
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06                       FIELD NAME: SOURCE
  LOCATION: 0;6                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   REJECT REASONS (Multiple-365.06) 
GLOBAL REFERENCE: IBCN(365,D0,6,D1,1,D2,0)
FIELD NUMBER: .01                       FIELD NAME: ADDITIONAL MSG
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   ADDITIONAL MSGS (Multiple-365.061) 
GLOBAL REFERENCE: IBCN(365,D0,7,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DATE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DATE QUALIFIER
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: LOOP ID
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   SUBSCRIBER DATES (Multiple-365.07) 
GLOBAL REFERENCE: IBCN(365,D0,8)
FIELD NUMBER: 8.01                      FIELD NAME: PT. RELATIONSHIP - HIPAA
  LOCATION: 8;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,9,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: REFERENCE ID (GROUP)
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: REF ID QUALIFIER (GROUP)
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: DESCRIPTION
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   GROUP REFERENCE INFORMATION (Multiple-365.09) 
GLOBAL REFERENCE: IBCN(365,D0,10,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PROVIDER CODE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: PROV REFERENCE ID
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   GROUP PROVIDER INFO (Multiple-365.04) 
GLOBAL REFERENCE: IBCN(365,D0,11,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SEQUENCE
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DIAGNOSIS CODE
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DIAGNOSIS CODE QUALIFIER
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: PRIMARY OR SECONDARY
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   HEALTH CARE CODE INFORMATION (Multiple-365.01) 
GLOBAL REFERENCE: IBCN(365,D0,12)
FIELD NUMBER: 12.01                     FIELD NAME: MILITARY INFO STATUS CODE
  LOCATION: 12;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.02                     FIELD NAME: MILITARY EMPLOYMENT STATUS
  LOCATION: 12;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.03
  FIELD NAME: MILITARY GOVT AFFILIATION CODE
  LOCATION: 12;3                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.04
  FIELD NAME: MILITARY PERSONNEL DESCRIPTION
  LOCATION: 12;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.05                     FIELD NAME: MILITARY SERVICE RANK CODE
  LOCATION: 12;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.06                     FIELD NAME: DATE TIME PERIOD FORMAT QUAL
  LOCATION: 12;6                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12.07                     FIELD NAME: DATE TIME PERIOD
  LOCATION: 12;7                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,13)
FIELD NUMBER: 13.01                     FIELD NAME: NAME OF INSURED
  LOCATION: 13;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13.02                     FIELD NAME: SUBSCRIBER ID
  LOCATION: 13;2                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: IBCN(365,D0,14)
FIELD NUMBER: 14.01                     FIELD NAME: GROUP NAME
  LOCATION: 14;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 14.02                     FIELD NAME: GROUP NUMBER
  LOCATION: 14;2                        ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Lighthouse requires access to the IIV RESPONSE file
 #365 to support the AMCMS/WellHive Insurance Capture initiative.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: LIGHTHOUSE

NUMBER: 7309                            IA #: 7309
  FILE NUMBER: 2101.1                   GLOBAL ROOT: GECS(2101.1
  DATE CREATED: OCT 19, 2021            CUSTODIAL PACKAGE: GENERIC CODE SHEET
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: GENERIC CODE SHEET BATCH TYPE LOOKUP
  ID: GECS(2101.1
GLOBAL REFERENCE: GECS(2101.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Lookup using 'B' cross reference 
GLOBAL REFERENCE: GECS(2101.1,D0,2,D1,0)
FIELD NUMBER: .01                       FIELD NAME: RECEIVING USER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Lookup using 'B' cross reference. The entry sought is
 "XXX".  
FIELD NUMBER: 1                         FIELD NAME: DOMAIN MAIL ROUTER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This holds the queue to which the transactions are sent.  
 GENERAL DESCRIPTION:   IFCAP wants to use VA FileMan API $$FIND1^DIC() to look
 up the FINANCIAL MANAGEMENT BATCH TYPE, look up the RECEIVING USER 'XXX' and
 then use $$GET1^DIQ() to get the value of the DOMAIN MAIL ROUTER to ensure
 that while testing in mirror/test accounts, FMS transactions are sent to the 
 test queue Q-FMT.DNS, rather than the production queue Q-FMS.DNS.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BATCH TYPE
KEYWORDS: DOMAIN ROUTER
SUBSCRIBING PACKAGE: IFCAP
  DATE ACTIVATED: OCT 29, 2021

NUMBER: 7310                            IA #: 7310
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: OCT 20, 2021            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: XUSAP
  NAME: Proxy user for Scheduling/Telehealth
  ID: XUSAP
 GENERAL DESCRIPTION:   The Scheduling/Telehealth Product Line can establish a
 proxy user "VSE,ACHERON". The user will be used by Telehealth Schedulers. The
 user will not have access or verify code.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: Proxy User
COMPONENT/ENTRY POINT: $$CREATE(proxyname,fmac,options)
 COMPONENT DESCRIPTION:   
    VARIABLES:  Input     proxyname 
                            The name of the application proxy 
                             
    VARIABLES:  Input     fmac 
                            The FileMan Access code,DUZ(0), to be associate 
                            with the application proxy 
                             
    VARIABLES:  Input     options 
VARIABLES: PROXYNAME                    TYPE: Input
 VARIABLES DESCRIPTION:   The name of the application proxy user 
VARIABLES: FMAC                         TYPE: Input
 VARIABLES DESCRIPTION:   The FileMan Access code,DUZ(0), to be associate with
 the application proxy 
VARIABLES: OPTIONS                      TYPE: Input
 VARIABLES DESCRIPTION:   Vista options to assigned the to proxy user, can be
 null 
SUBSCRIBING PACKAGE: SCHEDULING

NUMBER: 7311                            IA #: 7311
  DATE CREATED: NOV 04, 2021
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: ORJ                          NAME: RESULTS MANAGEMENT RULES ENGINE
  ID: ORJ
 GENERAL DESCRIPTION:   This integration agreement allows the subscriber to
 call the Results Management Rules Engine. The engine evaluates data specified
 by a set of Clinical Reminders terms and reminder definitions within a rule
 and if it determines that a rule is applicable, will execute the action(s)
 specified by the rule.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN(ORRETURN,ORTYPE,ORDIVISION,ORDFN)
 COMPONENT DESCRIPTION:   Entry point for executing the rules engine.  
VARIABLES: ORRETURN                     TYPE: Output
 VARIABLES DESCRIPTION:   This variable returns a caret-delimited string
 containing the status of the engine post-execution. It is formatted as: 
  
   "STATUS CODE^MESSAGE" 
  
 STATUS 
  CODE    STATUS 
 =====================
   -2     Error executing an action 
   -1     General error 
    0     No valid rules found 
    1     One or more rules were successfully 
          evaluated 
  
 MESSAGE: String containing a description of the 
          error(s). Multiple error messages are 
          separated by "; ".  
VARIABLES: ORTYPE                       TYPE: Input
 VARIABLES DESCRIPTION:   The type of rule(s) to evaluate in internal format.
 Refer to the TYPE field (#2) in the RULES file (#102) for the list of valid
 types.  
VARIABLES: ORDIVISION                   TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number (IEN) of the INSTITUTION file
 (#4) entry to retrieve rules for. If this parameter is null, then only rules
 that are not associated with an institution are evaluated.  
VARIABLES: ORDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the patient's entry in
 the PATIENT file (#2). All rules are evaluated in a specific patient context.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Clinical Reminders will use the rules engine to
 manipulate data returned from a reminder dialog.  

NUMBER: 7312                            IA #: 7312
  DATE CREATED: NOV 08, 2021            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  ROUTINE: PXRMORCH
  NAME: REMINDER ORDER CHECK RULE STATUS CHECK
  ID: PXRMORCH
 GENERAL DESCRIPTION:   This integration agreement allows the subscribing
 package to determine if two reminder definition statuses match. For example,
 the statuses "APPLICABLE" and "DUE SOON" match.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: RULE STATUS MATCH
KEYWORDS: ROC STATUS MATCH
KEYWORDS: REMINDER STATUS MATCH
COMPONENT/ENTRY POINT: $$STATMTCH(REMSTAT,RULESTAT)
 COMPONENT DESCRIPTION:   Determine if two reminder definition statuses match.  
VARIABLES: $$STATMTCH                   TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 if the given statuses match and 0 if the
 given statuses do not match.  
VARIABLES: REMSTAT                      TYPE: Input
 VARIABLES DESCRIPTION:   The reminder definition's evaluation status.  
VARIABLES: RULESTAT                     TYPE: Input
 VARIABLES DESCRIPTION:   The reminder definition status to compare the REMSTAT
 parameter to. Refer to the data dictionary for the DEFINITION EVALUATION
 STATUS field (#31) in the REMINDER ORDER CHECK RULES file (#801.1) for the
 list of acceptable values. Pass acceptable values in internal format.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   With patch OR*3*555, OE/RR will begin using this API as
 part of the Results Management functionality.  

NUMBER: 7313                            IA #: 7313
  DATE CREATED: NOV 09, 2021            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PSO VCC REFILL
  REMOTE PROCEDURE: PSO VCC REFILL
 GENERAL DESCRIPTION:   The purpose of this agreement is to provide Outpatient
 Medication Prescription Refill support for client systems such as the Veteran
 Contact Center (VCC).  
  
 The PSO VCC REFILL remote procedure was delivered originally with patch 
 PSO*7*642, and has been modified, effective with PSO*7*679, to include the
 REFILL SOURCE from which the REFILL request originated (e.g., VCC, and VSE).
 This modified RPC will support new functionality in Scheduling and Lighthouse
 package. CHIP web services will be exposing the refill RPC as an endpoint for
 use by the VistA Scheduling Enhancements (VSE) GUI for Clinical Staff.  Patch
 PSO*7*679 will support that implementation.  
  
 PSO VCC REFILL remote procedure capture: 
  
 The RPC: PSO VCC REFILL performs a refill on an outpatient pharmacy order 
 request. In addition, the RPC will provide the ability in Outpatient Pharmacy
 to store the source of a refill request (eg. VCC, Computerized Patient Record
 System (CPRS), Outpatient Pharmacy) as well as the person making the request -
 if the name is known.  
  
 OUTPUT:  ARRAY                                                           
 Depending on the value of the Return Flag input parameter, either a single 
 code is returned or a code and free text description of the code.  
  
 When the Return Flag input parameter equals 1, then the code and text 
 description will be returned.                                           
 Exception condition when attempting to refill the prescription:         
 ARRAY(0)=0                                                              
 ARRAY(1)=error text on why the prescription was not filled              The
 following is an example of one of several types of exceptions that could be
 returned:                                                        ARRAY(0)=0    
                                                           ARRAY(1)=" Cannot
 refill Rx # 2769331  Rx is in SUSPENDED status" 
   
 Successful refill:                                                      
 ARRAY(0)="1 - Prescription successfully refilled" 
   
 Data validation error which will be one of the following:               
 ARRAY(0)="-3 - Missing or Invalid Prescription Number"                  
 ARRAY(0)="-4 - Missing or Invalid Patient ID"                           
 ARRAY(0)="-5 - Prescription Number does not match to the Patient"       
 ARRAY(0)="-6 - Patient is not assigned an ICN"  (note:  code -6         
                will only be generated when the RETURN FLAG is equal 1)    
   
 When the Return Flag is equal null, then only the code will be returned.  
 Exception condition when attempting to refill the prescription:          
 ARRAY(0)=0                                                              
   
 Successful refill:                                                      
 ARRAY(0)=1 
   
 Data Validation error which will be one of the following:               
 ARRAY(0)=-3                                                              
 ARRAY(0)=-4                                                             
 ARRAY(0)=-5                                                             
  
 INPUT: 
      DFN [REQUIRED] -  Internal Entry Number of the patient record 
                          for the PATIENT file (#2) 
  
      RX# [REQUIRED] -  the external representation of the 
                        prescription number from the PRESCRIPTION 
                        file (#52,.01).  
  
      USER[OPTIONAL] -  USER requesting the refill (free text value) 
     
      REFILL SOURCE [OPTIONAL] - the source system from which the 
                        REFILL request Originated (e.g., VCC, VSE CS, 
                        AUDIOCARE).  If this value is not sent by the 
                        client, the REFILL SOURCE will be reported as 
                        "UNKNOWN".  
  
      RETURN FLAG [OPTIONAL] - Value will be 1 or null.  
                               If = 1 then the RPC will return the numeric 
                               code with text describing the code.  
                               If = null then the RPC will only return the 
                               numeric code (-5, -4, -3, 0, 1) 
  STATUS: Active
KEYWORDS: PSO VCC
KEYWORDS: REFILL
SUBSCRIBING PACKAGE: LIGHTHOUSE
 SUBSCRIBING DETAILS:   Effective with LHS*1*2 using RPC as part of the
 Clinical Health FHIR APIs on the Lighthouse API Platform. 
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Effective with PSO*7*679 
  DATE ACTIVATED: JUL 07, 2022

NUMBER: 7314                            IA #: 7314
  DATE CREATED: NOV 24, 2021            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOCLUTL
  NAME: PSOCLUTL                        ID: PSOCLUTL
 GENERAL DESCRIPTION:   The Mental Health package needs to call
 $$GETREGYS^PSOCLUTL(DFN) to get use frequency from registered cloz auth
 number, otherwise most recently assigned cloz number.  
  
 The Mental Health routine, YSCLTST2, was released in May 2020, effective with
 YS*5.01*166.  This is an after-the-fact ICR documentation.  
  STATUS: Active
KEYWORDS: CLOZAPINE
COMPONENT/ENTRY POINT: $$GETREGYS(DFN)
 COMPONENT DESCRIPTION:   Utility to get file 603.01 IEN currently registered
 to patient in file 55.  
VARIABLES: $$GETREGYS                   TYPE: Output
 VARIABLES DESCRIPTION:   $$GETREGYS returns the file #603.01 (CLOZAPINE
 PATIENT LIST) IEN of the patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Input variable DFN is the IEN for the patient in file
 #2 (PATIENT FILE).  
SUBSCRIBING PACKAGE: MENTAL HEALTH
  DATE ACTIVATED: NOV 26, 2021

NUMBER: 7315                            IA #: 7315
  DATE CREATED: DEC 13, 2021
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: PXRPC SAVE2
  REMOTE PROCEDURE: PXRPC SAVE2
 GENERAL DESCRIPTION:   PXRPC SAVE2 was included in PX*1*217 and distributed
 with CPRS v32b.  This RPC PXRPC SAVE2 is encouraged to be used instead of PX
 SAVE DATA, because it is a more complete solution which includes warnings and
 error information. 
  
 NAME: PXRPC SAVE2                       TAG: SAVE2 
   ROUTINE: PXRPC                        RETURN VALUE TYPE: ARRAY 
   AVAILABILITY: SUBSCRIPTION DESCRIPTION:   
  This is similar to PX SAVE DATA, except this RPC returns error 
  information.  INPUT PARAMETER: PCELIST                PARAMETER TYPE: LIST 
   MAXIMUM DATA LENGTH: 10000            REQUIRED: YES 
   SEQUENCE NUMBER: 1 DESCRIPTION:   
  See PX SAVE DATA.  INPUT PARAMETER: PKGNAME                PARAMETER TYPE:
 LITERAL 
   MAXIMUM DATA LENGTH: 60               REQUIRED: YES 
   SEQUENCE NUMBER: 2 DESCRIPTION:   
  See PX SAVE DATA.  INPUT PARAMETER: SRC                    PARAMETER TYPE:
 LITERAL 
   MAXIMUM DATA LENGTH: 60               REQUIRED: YES 
   SEQUENCE NUMBER: 3 DESCRIPTION:   
  See PX SAVE DATA.  INPUT PARAMETER: VISIT                  PARAMETER TYPE:
 LITERAL 
   MAXIMUM DATA LENGTH: 30               REQUIRED: NO 
   SEQUENCE NUMBER: 4 DESCRIPTION:   
  See PX SAVE DATA.  RETURN PARAMETER DESCRIPTION:   
  See PX SAVE DATA.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 8/30/24, effective with CDSP*1.0*1, Clinical
 Decision Support Platform is requesting subscription to PXRPC SAVE2 to
 facilitate Lung Cancer Screening Platform version2 to achieve its stated
 goals. Lung Cancer Screening Platform version2, or LCSPv2 for short,
 aggregates a robust set of data points to support LCS (Lung Cancer Screening) 
 coordinators in the jobs and tasks they do for tracking patients through Lung
 Cancer Screening. This RPC will be attached to the menu option CDSP RPC
 CONTEXT and the upgraded option will be released in patch CDSP*1.0*1.  
SUBSCRIBING PACKAGE: MEDICAL HEALTH ESCREENING
 SUBSCRIBING DETAILS:   Added 2/5/25, effective with MHE*1*1, to add PXRPC
 SAVE2 Remote Procedure to the MHE RPCS CONTEXT option. This will support
 saving the PCE encounter information before storing the note. The PKGNAME will
 be MHE - MEDICAL HEALTH ESCREENING and the SRC will be MHE ESCREENING.  
SUBSCRIBING PACKAGE: VETEXT
 SUBSCRIBING DETAILS:   Added 2/13/25, effective with VTEX*1*0 to add PXRPC
 SAVE2 to VEText RPC menu context options to support populating PCE data
 relating to encounters for the After Visit Summary (AVS), a minor of VEText.
 The PKGNAME will be VTEX and the SRC will be AVS.  
  DATE ACTIVATED: AUG 30, 2024

NUMBER: 7316                            IA #: 7316
  FILE NUMBER: 391.91                   GLOBAL ROOT: DGCN(391.91,
  DATE CREATED: DEC 16, 2021            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: DGCN(391.91 - GET EDIPI FOR DFN
  ID: DGCN(391.91,
GLOBAL REFERENCE: DGCN(391.91,
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: INSTITUTION
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: SOURCE ID TYPE
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 11                        FIELD NAME: SOURCE ID
  LOCATION: 2;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 12                        FIELD NAME: IDENTIFIER STATUS
  LOCATION: 2;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Treating Facility List where patients have had
 treatment. 
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   IFC processing code needs EDIPI for a DFN so EDIPI can
 be included in HL7 message to Cerner.  Function is in GMRCIUTL: 
  
 EDIPI(DFN) ; p184 
  ;
  ;  Return patient's EDIPI 
  ;
  N INST,EDIPI,TYPE,IEN,X ; 
  ;
  S INST=0,EDIPI="" ; 
  F  S INST=$O(^DGCN(391.91,"AKEY",DFN,INST)) Q:'INST!(EDIPI'="")  S TYPE="" F 
 S TYPE=$O(^DGCN(391.91,"AKEY",DFN,INST,TYPE)) Q:TYPE=""  I 
 $D(^DGCN(391.91,"AKEY",DFN,INST,TYPE,"USDOD")) D  ; 
  . S IEN=0 F  S IEN=$O(^DGCN(391.91,"AKEY",DFN,INST,TYPE,"USDOD",IEN)) Q:'IEN 
 S X=$G(^DGCN(391.91,IEN,2)) I X'="",$P(X,U,3)'="H" S 
 EDIPI=$S(EDIPI="":"",1:EDIPI_U)_$P(X,U,2) ; 
  ;
  Q EDIPI ; 
  ;

NUMBER: 7317                            IA #: 7317
  GLOBAL ROOT: XOB(18.12                DATE CREATED: DEC 16, 2021
  CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: ADD ENTRY TO WEB SERVER FILE (#18.12)
  ID: XOB(18.12
 GENERAL DESCRIPTION:   
  The Registration VAS team requests read/write access to the WEB 
  SERVER (#18.12) file to add a new entry during the DG*5.3*964 
  post-install process. The post-install routine process will create the 
  new server record entry using UPDATE^DIE and will also create a new entry 
  to the AUTHORIZED WEB SERVICES (#100) multiple, WEB SERVICE (#.01) field.  
  
  NOTE: This processing is done programmatically to avoid having sites 
  manually configure HWSC using the Web Server Manager. This will ensure 
  all sites have the same configuration installed correctly.  
      ^XOB(18.12,D0 
        .01      NAME                 0;1      Both R/W w/Fileman 
        .04      SERVER               0;4      Both R/W w/Fileman 
        .06      STATUS               0;6      Both R/W w/Fileman 
        .07      DEFAULT HTTP TIMEOUT 0;7      Both R/W w/Fileman 
        1.01     LOGIN REQUIRED       1;1      Both R/W w/Fileman 
        3.01     SSL ENABLED          3;1      Both R/W w/Fileman 
        3.02     SSL CONFIGURATION    3;2      Both R/W w/Fileman 
        3.03     SSL PORT             3;3      Both R/W w/Fileman 
        200      USERNAME             200;1    Both R/W w/Fileman 
        300      PASSWORD             300;1    Both R/W w/Fileman 
      ^XOB(18.12,D0,100,D1 
        .01      NAME                 0;1      Both R/W w/Fileman 
        .06      STATUS               0;6      Both R/W w/Fileman 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: WEB SERVER
KEYWORDS: VAS
KEYWORDS: VISTA AUDIT SOLUTION
KEYWORDS: REGISTRATION
SUBSCRIBING PACKAGE: REGISTRATION
  DATE ACTIVATED: FEB 04, 2022

NUMBER: 7318                            IA #: 7318
  FILE NUMBER: 355.33                   GLOBAL ROOT: IBA(355.33,
  DATE CREATED: DEC 23, 2021            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: LIGHTHOUSE INSURANCE VERIFICATION PROCESSOR ICR
  ID: IBA(355.33,
GLOBAL REFERENCE: IBA(355.33,D0,0)
FIELD NUMBER: .01                       FIELD NAME: DATE ENTERED
  LOCATION: 0;1                         ACCESS: LAYGO
FIELD NUMBER: .02                       FIELD NAME: ENTERED BY
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: SOURCE OF INFORMATION
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .04                       FIELD NAME: STATUS
  LOCATION: 0;4                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .13                       FIELD NAME: OVERRIDE FRESHNESS
  LOCATION: 0;13                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .18                       FIELD NAME: SERVICE DATE
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20.01                     FIELD NAME: INSURANCE COMPANY NAME
  LOCATION: 20;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20.02                     FIELD NAME: PHONE NUMBER
  LOCATION: 20;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20.03                     FIELD NAME: BILLING PHONE NUMBER
  LOCATION: 20;3                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20.04
  FIELD NAME: PRECERTIFICATION PHONE NUMBER
  LOCATION: 20;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20.05                     FIELD NAME: REIMBURSE?
  LOCATION: 20;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21.01                     FIELD NAME: STREET ADDRESS [LINE 1]
  LOCATION: 21;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21.02                     FIELD NAME: STREET ADDRESS [LINE 2]
  LOCATION: 21;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21.03                     FIELD NAME: STREET ADDRESS [LINE 3]
  LOCATION: 21;3                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21.04                     FIELD NAME: CITY
  LOCATION: 21;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21.05                     FIELD NAME: STATE
  LOCATION: 21;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21.06                     FIELD NAME: ZIP CODE
  LOCATION: 21;6                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 40.01                     FIELD NAME: IS THIS A GROUP POLICY?
  LOCATION: 40;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 40.04                     FIELD NAME: UTILIZATION REVIEW REQUIRED
  LOCATION: 40;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 40.05                     FIELD NAME: PRECERTIFICATION REQUIRED
  LOCATION: 40;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 40.06
  FIELD NAME: AMBULATORY CARE CERTIFICATION
  LOCATION: 40;6                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 40.09                     FIELD NAME: TYPE OF PLAN
  LOCATION: 40;9                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 40.1
  FIELD NAME: BANKING IDENTIFICATION NUMBER
  LOCATION: 40;10                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 40.11                     FIELD NAME: PROCESSOR CONTROL NUMBER
  LOCATION: 40;11                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.01                     FIELD NAME: PATIENT NAME
  LOCATION: 60;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.02                     FIELD NAME: EFFECTIVE DATE
  LOCATION: 60;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.03                     FIELD NAME: EXPIRATION DATE
  LOCATION: 60;3                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.05                     FIELD NAME: WHOSE INSURANCE
  LOCATION: 60;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.08                     FIELD NAME: INSURED'S DOB
  LOCATION: 60;8                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.09                     FIELD NAME: INSURED'S SSN
  LOCATION: 60;8                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.1                      FIELD NAME: PRIMARY CARE PROVIDER
  LOCATION: 60;10                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.11                     FIELD NAME: PRIMARY PROVIDER PHONE
  LOCATION: 60;11                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.12                     FIELD NAME: COORDINATION OF BENEFITS
  LOCATION: 60;12                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.13                     FIELD NAME: INSURED'S SEX
  LOCATION: 60;13                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.14                     FIELD NAME: PT. RELATIONSHIP - HIPAA
  LOCATION: 60;14                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.15                     FIELD NAME: PHARMACY RELATIONSHIP CODE
  LOCATION: 60;15                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 60.16                     FIELD NAME: PHARMACY PERSON CODE
  LOCATION: 60;16                       ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.01                     FIELD NAME: PATIENT ID
  LOCATION: 62;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.02                     FIELD NAME: SUBSCRIBER ADDRESS LINE 1
  LOCATION: 62;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.03                     FIELD NAME: SUBSCRIBER ADDRESS LINE 2
  LOCATION: 62;3                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.04                     FIELD NAME: SUBSCRIBER ADDRESS CITY
  LOCATION: 62;4                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.05                     FIELD NAME: SUBSCRIBER ACCESS STATE
  LOCATION: 62;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.06                     FIELD NAME: SUBSCRIBER ADDRESS ZIP
  LOCATION: 62;6                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.08
  FIELD NAME: SUBSCRIBER ADDRESS SUBDIVISION
  LOCATION: 62;8                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.09                     FIELD NAME: SUBSCRIBER PHONE
  LOCATION: 62;9                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 80.01                     FIELD NAME: INQ SERVICE TYPE CODE 1
  LOCATION: 80;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 90.01                     FIELD NAME: GROUP NAME
  LOCATION: 90;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 90.02                     FIELD NAME: GROUP NUMBER
  LOCATION: 90;2                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 90.03                     FIELD NAME: SUBSCRIBER ID
  LOCATION: 90;3                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 91.01                     FIELD NAME: NAME OF INSURED
  LOCATION: 91;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 40.07
  FIELD NAME: EXCLUDE PREEXISTING CONDITION
  LOCATION: 40;7                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 40.08                     FIELD NAME: BENEFITS ASSIGNABLE
  LOCATION: 40;8                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 62.07                     FIELD NAME: SUBSCRIBER ADDRESS COUNTRY
  LOCATION: 62;7                        ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   Lighthouse requires access to the INSURANCE
 VERIFICATION PROCESSOR file #355.33 to support the AMCMS/WellHive Insurance
 Capture initiative.  
  STATUS: Withdrawn
SUBSCRIBING PACKAGE: LIGHTHOUSE

NUMBER: 7319                            IA #: 7319
  DATE CREATED: JAN 12, 2022
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7319
  STATUS: Pending

NUMBER: 7320                            IA #: 7320
  DATE CREATED: JAN 12, 2022            CUSTODIAL PACKAGE: VISTALINK
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: XOBV TEST UPDATE SECID
  REMOTE PROCEDURE: XOBV TEST UPDATE SECID
 GENERAL DESCRIPTION:   Allow an external application to pass a NEW PERSON IEN
 (file #200) and a secID (file 200, field #205.1) for a given tester to the
 VistA test system.  When invoked, the RPC will apply the passed secID to the
 tester with the IEN that has been passed.  
  
 REMOTE PROCEDURE NAME: XOBV TEST UPDATE SECID  
   TAG: CHGSECID                        ROUTINE: XOBVSECI 
   RETURN VALUE TYPE: SINGLE VALUE      AVAILABILITY: PUBLIC 
   INACTIVE: ACTIVE 
   DESCRIPTION:   
   This RPC allows the SECID for a given tester to be changed.  
   This will only run in a test account.  
  
 INPUT PARAMETER: XOBVNPIEN             PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 18              REQUIRED: YES 
   SEQUENCE NUMBER: 1 
   DESCRIPTION: The IEN of the person in the NEW PERSON (#200) file for 
                whom the SECID will be changed.  
  
 INPUT PARAMETER: XOBVSECID             PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 30              REQUIRED: YES 
   SEQUENCE NUMBER: 2 
   DESCRIPTION: This is the new SECID that will be assigned to the person 
                specified by the XOBVNPIEN parameter.  
  
 RETURN PARAMETER DESCRIPTION:   
   A string: 
    0_"^"_205 node of ^VA(200,XOBVNPIEN) 
      - includes fields 
      - SECID (#205.1) and UNIQUE USER ID (#205.4) 
     or 
    -1_"^"_error message 
  
  
  STATUS: Active
SUBSCRIBING PACKAGE: KERNEL
  DATE ACTIVATED: JAN 27, 2022

NUMBER: 7321                            IA #: 7321
  FILE NUMBER: 433.001                  GLOBAL ROOT: PRCA(433.001
  DATE CREATED: JAN 13, 2022            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Controlled Subscription        TYPE: File
  NAME: PRCA AR SUSPENSION TYPE         ID: PRCA(433.001
GLOBAL REFERENCE: PRCA(433.001,0
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the code for the Suspension Type.  
FIELD NUMBER: .02                       FIELD NAME: DESCRIPTION
  LOCATION: 0;2                         ACCESS: Direct Global Write & w/Fileman
 FIELD DESCRIPTION:   This describes the Suspension Type in more detail.  
FIELD NUMBER: .03                       FIELD NAME: INACTIVE?
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field will be marked Inactive if a suspension type
 is determined to be no longer in use.  
GLOBAL REFERENCE: PRCA(433.001,'B'
 GLOBAL DESCRIPTION:   This is the Cross Reference for the AR Suspension Type
 Codes.  
 GENERAL DESCRIPTION:   Allow external packages access to the fields in the AR
 SUSPENSION TYPE file, #433.001 for reporting filters in Integrated Billing.  
  STATUS: Pending
KEYWORDS: ACCOUNTS RECEIVABLE
KEYWORDS: SUSPENSION TYPE
KEYWORDS: TRANSACTIONS
SUBSCRIBING PACKAGE: INTEGRATED BILLING

NUMBER: 7322                            IA #: 7322
  FILE NUMBER: 123.5                    GLOBAL ROOT: GMR(123.5
  DATE CREATED: JAN 21, 2022
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: SD READ ACCESS TO THE REQUEST SERVICES FILE
  ID: GMR(123.5
GLOBAL REFERENCE: 123.4
FIELD NUMBER: .01                       FIELD NAME: RELATED HOSPITAL LOCATION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the clinic to be used by the Community Care
 Referrals & Authorization (CCRA) when making an appointment.  
 GENERAL DESCRIPTION:   The Scheduling package needs to access the RELATED
 HOSPITAL LOCATION (#123.4) multiple in the REQUEST SERVICES FILE (#123.5) in
 order to make an appointment for a community care consult in the correct
 clinic. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HSRM
KEYWORDS: CCRA
KEYWORDS: RELATED HOSPTIAL LOCATION
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Effective with patch SD*5.3*808, the Community Care
 Referrals & Authorization (CCRA) project makes appointments for community care 
 referral appointments. In order to make the appointment in the correct clinic,
 the CCRA scheduling interface needs to do direct and FileMan reads of the
 RELATED HOSPITAL LOCATION multiple to get the clinic for the appointment.  The
 CCRA scheduling interface uses a loop to get the last entry in the multiple
 and then does a FileMan read to get the name of the last clinic to make sure
 the clinic is a community care clinic.  
  DATE ACTIVATED: JAN 24, 2022

NUMBER: 7323                            IA #: 7323
  DATE CREATED: JAN 28, 2022            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFCAPI
  NAME: VAFCAPI                         ID: VAFCAPI
 GENERAL DESCRIPTION:   The Master Veteran Index (MVI) team has created this
 Application Programming Interface (API) which will allows the adding/updating
 or validation of Sexual Orientation (SO) and Gender Identity Traits of a 
 patient's record in the PATIENT (#2) file.  
  
 Currently the Sexual Orientation (#.025) field multiple and the Sexual 
 Orientation Description (#.0251) field in the PATIENT (#2) file can be 
 added/updated or validated with this API.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SOGI
KEYWORDS: SEXUAL ORIENTATION
KEYWORDS: .025
KEYWORDS: .0251
KEYWORDS: SO
KEYWORDS: VAFCAPI
COMPONENT/ENTRY POINT: $$SOGI(DFN,.ARRAY,UPDATE)
 COMPONENT DESCRIPTION:   To add or update a Sexual Orientation and/or Sexual
 Orientation Description.  
  
 Arguments:   DFN   - pointer to entry in Patient file 
              ARRAY - list of Sexual Orientation related components 
              UPDATE- file or validate Sexual Orientation components 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to entry in the Patient (#2) file (required) 
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   ARRAY("SexOr",n) = code^status^note 
  
   n      - counter for list of sexual orientation(s) traits 
  
  code (required) - will be filed in the SEXUAL ORIENTATION (#.01) field of the
 SEXUAL ORIENTATION (#.025) multiple of the PATIENT (#2) file.  It corresponds
 to the TYPE CODE (#1) field of the SEXUAL ORIENTATION TYPES. (#47.77) file 
  
  status (required) - will be filed in the STATUS (#.02) field of the SEXUAL
 ORIENTATION (#.025) multiple of the PATIENT (#2) file and currently defined as
 'A' (Active), 'I' (Inactive), 'E' (Entered in Error).  
  
  note (optional) - ien from the TIU DOCUMENT (#8925) file.  
  
 ARRAY("SexOrDes") (optional) - will be filed in the SEXUAL ORIENTATION 
 DESCRIPTION (#.0251) field of the PATIENT (#2) file and describes the 'Other'
 sexual orientation.  
VARIABLES: UPDATE                       TYPE: Input
 VARIABLES DESCRIPTION:   
  1 - Sexual Orientation components are filed, otherwise only data validation
 is performed (optional) 
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   
  0 - if update is successful 
  
 -1^error message - if unsuccessful 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Effective with patch PXRM*2.0*78, users in CPRS will be
 able to use Clinical Reminders to add/update or validate the Sexual
 Orientation multiple (#.025) and the Sexual Orientation Description (#.0251)
 in the PATIENT (#2) file.  
  DATE ACTIVATED: FEB 08, 2022

NUMBER: 7324                            IA #: 7324
  FILE NUMBER: 443                      GLOBAL ROOT: PRC(443
  DATE CREATED: JAN 31, 2022            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: REQUEST WORKSHEET FILE ACCESS
  ID: PRC(443
GLOBAL REFERENCE: PRC(443,D0,0
FIELD NUMBER: .01                       FIELD NAME: 2237 TRANSACTION NUMBER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: ACCOUNTABLE OFFICER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: VALIDATION CODE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: ESIG DATE/TIME
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: PURCHASING AGENT
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: DATE ASSIGNED TO PA
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 1.5                       FIELD NAME: CURRENT STATUS
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: CP FUND STATUS
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: TYPE OF REQUEST
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SOURCE OF REQUEST
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: INVENTORY/DISTRIBUTION POINT
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: EXPENDABLE/NONEXPENDABLE
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 3.7                       FIELD NAME: ESIG CODE
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 3.5                       FIELD NAME: VALIDATION VERSION
  LOCATION: 0;14                        ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Above PAR requests permission to read from the REQUEST
 WORKSHEET FILE #443 to validate the WORKSHEET REQUEST has a VALIDATION CODE
 field (#3).  
  
 Above PAR Ad-Hoc Reporting includes the REQUEST WORKSHEET file #443.  Ad-Hoc
 functionality provides the ability to select fields from the file for display
 on user-defined reports.  Ad-Hoc offers only FileMan read access and only if
 the user has permission to view the file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ABOVE PAR
KEYWORDS: APAR
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: FEB 17, 2022

NUMBER: 7325                            IA #: 7325
  DATE CREATED: FEB 02, 2022            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  ROUTINE: IBLHS1                       NAME: DUPLICATE INSURANCE CHECK
  ID: IBLHS1
 GENERAL DESCRIPTION:   This routine provides a duplicate insurance check that
 is used by Lighthouse prior to writing potentially new insurance coverage to
 the Insurance Verification Processor file #355.33.  
  STATUS: Withdrawn
KEYWORDS: IBLHS1
COMPONENT/ENTRY POINT: $$ISDUP(DFN,IBARY)
 COMPONENT DESCRIPTION:   This function compares the input data in the IBARY
 array with other entries in the Insurance Verification Processor file
 (#355.33) for the patient indicated by the DFN parameter. It also compares
 data in the Insurance Type Subfile (#2.312) of the Patient file (#2) for the
 patient.  
  
   Output: 0 if no duplicates are found 
           1 ^ [File # where duplicate found] ^ [IENS array of entry in file] 
   
    example: (1^355.33^12345,) or (1^2.312^2,54321,) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient Internal Entry Number.  
VARIABLES: IBARY                        TYPE: Input
 VARIABLES DESCRIPTION:   An array of required insurance related fields used to
 identify potential duplicate insurance data that already exists either in the
 Patient Insurance Type subfile #2.312 or the Insurance Verification Processor
 file #355.33.  
  
   IBARY(20.01) = INSURANCE COMPANY NAME 
   IBARY(90.02) = GROUP NUMBER 
   IBARY(90.03) = SUBSCRIBER ID 
   IBARY(91.01) = NAME OF INSURED 
   IBARY(60.08) = INSURED'S DOB 
  
 When checking against file #355.33, the fields to compare are: 
   INSURANCE COMPANY NAME (#355.33, 20.01) 
   GROUP NUMBER (#355.33, 90.02) 
   SUBSCRIBER ID (#355.33, 90.03) 
   NAME OF INSURED (#355.33, 91.01) 
   INSURED'S DOB (#355.33, 60.08) 
  
 When checking against file #2.312 by using the API "ALL^IBCNS1", the fields to
 compare are: 
   NAME (#2.312, .01) 
   NEW GROUP NUMBER (#2.312, 21) 
   SUBSCRIBER ID (#2.312, 7.02) 
   NAME OF INSURED (#2.312, 7.01) 
   INSURED'S DOB (#2.312, 3.01) 
SUBSCRIBING PACKAGE: LIGHTHOUSE

NUMBER: 7326                            IA #: 7326
  FILE NUMBER: 100                      GLOBAL ROOT: OR(100
  DATE CREATED: FEB 17, 2022
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: TESTING READ ONLY               ID: OR(100
GLOBAL REFERENCE: OR(100,IEN,0)
FIELD NUMBER: .01                       ACCESS: Read w/Fileman
  STATUS: Pending

NUMBER: 7327                            IA #: 7327
  DATE CREATED: DEC 04, 2023
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXCOMPACT
  NAME: COMPACT ACT                     ID: PXCOMPACT
 GENERAL DESCRIPTION:   Patches DG*5.3*1104 and PX*1.0*240 will allow
 Registration to make decisions on when to prompt for COMPACT Act clinical
 information. For this decision-making process Registration needs to call the
 entry point ASC^PXCOMPACT to determine if the patient is currently in an Acute 
 Suicidal Crisis.  
  
 Registration also needs to be able to add a new entry to the COMPACT ACT 
 EPISODE OF CARE file (#818) for a patient and this is allowed by a call made
 to the ADMIT^PXCOMPACT entry point.  
  
 Other displays needed during the registration process are determined by the
 entry point DISPLAY^PXCOMPACT.  
  
 Registration also needs to be able to use the entry point VISIT^PXCOMPACT to
 set the Episode of Care (EOC) pointer to the PTF file.  
  
 If a new EOC needs to be opened or reopened during a patient transfer, or if
 an EOC needs to be retracted during editing or deletion of a movement, 
 Registration needs to determine the appropriate EOC using $$GETEOC^PXCOMPACT
 and $$GETEOCSEQ^PXCOMPACT, use SETENDDT to close an open outpatient episode,
 and use NEWEOC^PXCOMPACT to create a new episode.  
  
 During an admission, Registration needs to access $$GETIPDT^PXCOMPACT and 
 $$GETSTDT^PXCOMPACT to determine benefit start and end dates.  
  
 Upon a discharge, Registration must use CHGTYPSTAT^PXCOMPACT to change the 
 COMPACT Act benefit from Inpatient to Outpatient.  
  
 During a transfer, Registration must call REOPNEOC^PXCOMPACT to reopen an 
 episode of care for a PTF that is already associated with an episode.  
  
  
 Revision History 
  5/7/24 - Removed FILEMANERR component (moved to new routine) 
  4/25/24 - Removed $$ADMIN Component and hence removed Scheduling package as
 subscriber, since Scheduling only used the $$ADMIN component.  
  7/17/24 - Added $$GETEOC component effective with patches PX*1.0*240 and 
 DG*5.3*1104 
  9/24/24 - Added SETENDDT component effective with patches PX*1.0*240 and 
 DG*5.3*1104 
  10/22/24 - Added RESET component effective with patches PX*1.0*241 and 
  DG*5.3*1117 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COMPACT ACT
COMPONENT/ENTRY POINT: $$ASC
 COMPONENT DESCRIPTION:   Function call returns the Acute Suicidal Crisis flag
 value of a patient's Open COMPACT ACT EPISODE OF CARE file (#818, "N" for No
 or "Y" for Yes.  
      
   Sample Use 
   ----------
   S DFN=xxxxx 
   I $$ASC^PXCOMPACT(DFN)="Y") W !,"Patient is in an Acute Suicidal Crisis!" 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to PATIENT file (#2) 
VARIABLES: Output of function call      TYPE: Output
 VARIABLES DESCRIPTION:   One of 2 valid statuses below: 
     "N" for no 
     "Y" for yes 
COMPONENT/ENTRY POINT: $$DISPLAY
 COMPONENT DESCRIPTION:   Function returns a delimited string of display values
 based on various scenarios of the current state of a patient's COMPACT Act
 Episode of Care.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN.  
VARIABLES: Output of function call      TYPE: Output
 VARIABLES DESCRIPTION:   Below are various scenarios that will be returned
 about the state of a patient's COMPACT Act Episode of Care.  
  
 DISPLAY will contain one of the following groups of information: 
  
 1. If end date exists (episode has ended) and    
    there are no extensions, 
       "COMPACT Act Start Date"^EPISODE START 
        DATE^"End Date"^EPISODE END DATE^"IP     
        Benefit End Date"^INPATIENT BENEFIT END 
        DATE^"OP Benefit end date"^OUTPATIENT 
        BENEFIT END DATE 
  
 2. If end date exists (episode has ended) and 
    an extension exists, 
       "Extension Start Date"^EXTENSION START 
        DATE^"Episode End Date"^EPISODE END DATE 
  
 3. If end date does not exist (episode is 
    ongoing) and there are no extensions, 
       For an inpatient with an INPATIENT BENEFIT 
       END DATE, 
         "COMPACT Act Start Date"^EPISODE START 
          DATE^"Remaining Days"^REMAINING 
          INPATIENT DAYS^"Inpatient Benefit End 
          Date"^INPATIENT BENEFIT END DATE 
       Otherwise, 
          "COMPACT Act Start Date"^EPISODE START 
           DATE^"Remaining Days"^REMAINING 
           INPATIENT DAYS or REMAINING OUTPATIENT 
           DAYS 
  
 4. If end date does not exist (episode is 
    ongoing) and an extension exists, 
       "Extension Start Date"^EXTENSION START 
        DATE^"Remaining Days"^REMAINING INPATIENT 
        DAYS or REMAINING OUTPATIENT DAYS 
COMPONENT/ENTRY POINT: ADMIT
 COMPONENT DESCRIPTION:   This call will add a patient to the COMPACT ACT
 EPISODE OF CARE file (#818) upon admission for COMPACT Act related care.  It
 will also update the pointer in the file #818 to the PTF file (#45) that was
 created during this admission event.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
VARIABLES: STARTDT                      TYPE: Input
 VARIABLES DESCRIPTION:   The clinically determined start date for this Acute
 Suicidal Crisis.  
VARIABLES: ADMIT                        TYPE: Input
 VARIABLES DESCRIPTION:   The Admit type:  "F" = Full admission 
                  "P" = Partial admission 
  
 The ADMIT parameter is used to distinguish between a partial admit 
 (observation) with a value of P or a full admit (admitted to a facility other
 than observation) with a value of F.  It is not required but failure to set
 the parameter will result in the ADMIT process defaulting to a partial admit. 
VARIABLES: PTF                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number of the associated
 PTF file (#45) of this admission movement.  
COMPONENT/ENTRY POINT: VISIT
 COMPONENT DESCRIPTION:   This call will set the pointer to the PTF file (#45)
 in the COMPACT ACT EPISODE OF CARE file (#818) for an inpatient episode or the
 COMPACT ACT EPISODE OF CARE file pointer to the VISIT file (#9000010) for an 
 outpatient episode. It will also set the Treatment Related To flag for the 
 inpatient or outpatient encounter.  
VARIABLES: ENC                          TYPE: Input
 VARIABLES DESCRIPTION:   The Encounter ID (PTF or VISIT IEN).  
VARIABLES: PXTY                         TYPE: Input
 VARIABLES DESCRIPTION:   The benefit type:  "I" = Inpatient 
                    "O" = Outpatient 
VARIABLES: PXEOCNUM                     TYPE: Input
 VARIABLES DESCRIPTION:   The EOC internal entry number for the patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
COMPONENT/ENTRY POINT: $$GETEOC
 COMPONENT DESCRIPTION:   This call will retrieve the Episode of Care number
 assigned to a patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
VARIABLES: GETEOC                       TYPE: Output
 VARIABLES DESCRIPTION:   The EOC number.  
COMPONENT/ENTRY POINT: NEWEOC
 COMPONENT DESCRIPTION:   This call will create a new Episode of Care.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
VARIABLES: PXENC                        TYPE: Input
 VARIABLES DESCRIPTION:   The Encounter ID (PTF or VISIT IEN).  
VARIABLES: PXTY                         TYPE: Input
 VARIABLES DESCRIPTION:   The benefit type:  "I" = Inpatient 
                    "O" = Outpatient 
VARIABLES: PXSTDT                       TYPE: Input
 VARIABLES DESCRIPTION:   The episode start date.  
VARIABLES: PXSRC                        TYPE: Input
 VARIABLES DESCRIPTION:   The episode source.  
COMPONENT/ENTRY POINT: $$GETIPDT
 COMPONENT DESCRIPTION:   This call will retrieve the inpatient benefit end
 date for a patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
VARIABLES: GETIPDT                      TYPE: Output
 VARIABLES DESCRIPTION:   The inpatient benefit end date.  
COMPONENT/ENTRY POINT: $$GETSTDT
 COMPONENT DESCRIPTION:   This call will retrieve the start date of the most
 current episode.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
VARIABLES: GETSTDT                      TYPE: Output
 VARIABLES DESCRIPTION:   The episode start date.  
COMPONENT/ENTRY POINT: CHGTYPSTAT
 COMPONENT DESCRIPTION:   This call will change the patient's benefit type
 between Outpatient and Inpatient and update benefit end dates.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
VARIABLES: PXTY                         TYPE: Input
 VARIABLES DESCRIPTION:   The benefit type to which to change: 
                    "I" = Inpatient 
                    "O" = Outpatient 
VARIABLES: PXCHNGDT                     TYPE: Input
 VARIABLES DESCRIPTION:   The date of the benefit type change.  
COMPONENT/ENTRY POINT: REOPNEOC
 COMPONENT DESCRIPTION:   This call will reopen an inpatient Episode of Care.  
VARIABLES: PXEOCNUM                     TYPE: Input
 VARIABLES DESCRIPTION:   The EOC internal entry number for the patient.  
VARIABLES: PXEOCSEQ                     TYPE: Input
 VARIABLES DESCRIPTION:   The EOC sequence number.  
VARIABLES: STARTDT                      TYPE: Input
 VARIABLES DESCRIPTION:   The episode start date.  
COMPONENT/ENTRY POINT: $$GETEOCSEQ
 COMPONENT DESCRIPTION:   This call will retrieve the current or last Episode
 of Care sequence for a patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
VARIABLES: GETEOCSEQ                    TYPE: Output
 VARIABLES DESCRIPTION:   The EOC sequence number.  
COMPONENT/ENTRY POINT: SETENDDT
 COMPONENT DESCRIPTION:   This call will set an end date and end the current /
 most recent episode of care.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
VARIABLES: PXENDDT                      TYPE: Input
 VARIABLES DESCRIPTION:   The new end date (VA format).  
VARIABLES: PXENDSRC                     TYPE: Input
 VARIABLES DESCRIPTION:   The source of crisis end:  "PA" = Patient 
                            "PR" = Provider 
                            "TE" = Time Expired 
VARIABLES: PXAUTH                       TYPE: Input
 VARIABLES DESCRIPTION:   The person who authorized the crisis end.  
VARIABLES: PXCOMM                       TYPE: Input
 VARIABLES DESCRIPTION:   Other comments about the crisis end.  
COMPONENT/ENTRY POINT: RESET
 COMPONENT DESCRIPTION:   This call will reset the EOC Open/Close flag to 0 and
 set the Benefit Type to null.  
VARIABLES: PXEOCNUM                     TYPE: Input
 VARIABLES DESCRIPTION:   Internal episode of care number.  
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   
  Added 12/04/23 
  
  4/25/24 - Removed $$ADMIN Component and added the following new components
 effective with patches PX*1.0*240 and DG*5.3*1104: 
  VISIT 
  FILEMANERR 
  $$GETEOCSEQ 
  NEWEOC 
  $$GETIPDT 
  $$GETSTDT 
  CHGTYPSTAT 
  REOPNEOC 
  
  5/7/24 - Removed FILEMANERR Component 
  
  7/17/24 - Added $$GETEOC component effective with patches PX*1.0*240 and 
 DG*5.3*1104 
  
  9/24/24 - Added SETENDDT component effective with patches PX*1.0*240 and 
 DG*5.3*1104 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 12/22/23, effective with patches DG*5.3*1104 and
 PX*1.0*240 
  DATE ACTIVATED: OCT 24, 2024

NUMBER: 7328                            IA #: 7328
  DATE CREATED: MAR 04, 2022            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCHEUI
  NAME: VENDOR UEI VALIDATION           ID: PRCHEUI
 GENERAL DESCRIPTION:   This integration agreement grants permission to invoke
 IFCAP APIs used to validate the GSA SAM UEI (Unique Entity Identifier) field
 (#55) in the Vendor file (#440).  
  
  The UEI is a 12-character field. The 12th character is the check digit.  
  The UEI cannot contain the letter O or I and cannot begin with digit 0.  
  STATUS: Active
KEYWORDS: APAR
KEYWORDS: APAT
KEYWORDS: ABOVE PAR
COMPONENT/ENTRY POINT: $$VALIDUEI
 COMPONENT DESCRIPTION:   VALIDUEI checks if input meets UEI formatting rules
 and that 12th character is a valid check digit. This function returns '1' if
 UEI is valid or '0' if not valid.  
VARIABLES: PRCSTR                       TYPE: Input
 VARIABLES DESCRIPTION:   12 character UEI value 
COMPONENT/ENTRY POINT: $$UEICHK
 COMPONENT DESCRIPTION:   UEICHK will calculate the check digit based on the
 initial 11 characters of the alphanumeric UEI value. This function returns the
 check digit.  
VARIABLES: PRCROOT                      TYPE: Input
 VARIABLES DESCRIPTION:   12 character UEI value 
SUBSCRIBING PACKAGE: ABOVE PAR
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: AUG 17, 2022

NUMBER: 7329                            IA #: 7329
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: MAR 14, 2022            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: File
  NAME: OUTPATIENT PHARMACY MEDICATION RECONCILIATION
  ID: PSRX(
GLOBAL REFERENCE: PSRX
FIELD NUMBER: 4                         FIELD NAME: PROVIDER
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: CLINIC
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: DAYS SUPPLY
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: # OF REFILLS
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: MAIL/WINDOW
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 21                        FIELD NAME: LOGIN DATE
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: PHARMACIST
  LOCATION: 2;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 38                        FIELD NAME: FINISHING PERSON
  LOCATION: OR1;5                       ACCESS: Read w/Fileman
FIELD NUMBER: 39.2                      FIELD NAME: PHARMACY ORERABLE ITEM
  LOCATION: OR1;1                       ACCESS: Read w/Fileman
FIELD NUMBER: 114                       FIELD NAME: PATIENT INSTRUCTION
  LOCATION: INS;1                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,1
FIELD NUMBER: 10.1                      FIELD NAME: DISPENSED DATE
  LOCATION: 0;19                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,PI,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PHARMACY INSTRUCTIONS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,INS1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: EXPANDED PATIENT INSTRUCIONS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,6,D1,0)
FIELD NUMBER: .O1                       FIELD NAME: DOSAGE ORDERED
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DISPENSE UNITS PER DOSE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: NOUN
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: DURATION
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: UNITS
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: ROUTE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: SCHEDULE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,PRC,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PROVIDER COMMENTS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,SIG1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: SIG1
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PSRX(D0,IND
FIELD NUMBER: 128                       FIELD NAME: INDICATION FOR USE
  LOCATION: IND;1                       ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This ICR is to support the medication reconciliation 
 feature in COMPREHENSIVE CARE COORDINATION.  Reading from file 52 will allow
 COMPREHENSIVE CARE COORDINATION to display order details for verified
 outpatient orders.  
  STATUS: Active
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 04/07/2022, effective with DSSV 1.1 DSS Class 3
 product - Document Only 
  DATE ACTIVATED: APR 07, 2022

NUMBER: 7330                            IA #: 7330
  FILE NUMBER: 55                       GLOBAL ROOT: PS(55
  DATE CREATED: MAR 14, 2022
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Controlled Subscription        TYPE: File
  NAME: INPATIENT PHARMACY MEDICATION RECONCILIATION
  ID: PS(55
GLOBAL REFERENCE: PS(55,D0,5,0
FIELD NUMBER: .24                       FIELD NAME: PRIORITY
  LOCATION: .2;4                        ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PROVIDER
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: MED ROUTE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: SPECIAL INSTRUCTIONS
  LOCATION: 6;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 26                        FIELD NAME: SCHEDULE
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 28                        FIELD NAME: STATUS
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 42                        FIELD NAME: FREQUENCY (in minutes)
  LOCATION: 2;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 108                       FIELD NAME: ORDERABLE ITEM
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 109                       FIELD NAME: DOSAGE ORDERED
  LOCATION: .2;2                        ACCESS: Read w/Fileman
FIELD NUMBER: 120                       FIELD NAME: DOSE 
  LOCATION: .2;5                        ACCESS: Read w/Fileman
FIELD NUMBER: 121                       FIELD NAME: UNIT
  LOCATION: .2;6                        ACCESS: Read w/Fileman
FIELD NUMBER: 126                       FIELD NAME: REQUESTED DURATION
  LOCATION: 2.5;2                       ACCESS: Read w/Fileman
FIELD NUMBER: 130                       FIELD NAME: CLINIC
  LOCATION: 8;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 141                       FIELD NAME: INDICATION FOR USE
  LOCATION: 18;1                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(55,D0,5,D1,12,0
FIELD NUMBER: .01                       FIELD NAME: PROVIDER COMMENTS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(55,D0,5,D1,1,0
FIELD NUMBER: .01                       FIELD NAME: DISPENSE DRUG
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: INACTIVE DATE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(55,D0,IV,0
FIELD NUMBER: .04                       FIELD NAME: TYPE
  LOCATION: 0;4                         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: .1                        FIELD NAME: REMARKS
  LOCATION: 1;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 31                        FIELD NAME: OTHER PRINT INFO
  LOCATION: 3;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 100                       FIELD NAME: ORDERABLE ITEM
  LOCATION: 2;1                         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: 133                       FIELD NAME: INSTRUCTIONS
  LOCATION: .3;1                        ACCESS: Read w/Fileman
FIELD NUMBER: 134                       FIELD NAME: PRIORITY
  LOCATION: .2;4                        ACCESS: Read w/Fileman
FIELD NUMBER: 136                       FIELD NAME: CLINIC
  LOCATION: DSS;1                       ACCESS: Read w/Fileman
FIELD NUMBER: 151                       FIELD NAME: REQUESTED DURATION
  LOCATION: 2.5;2                       ACCESS: Read w/Fileman
FIELD NUMBER: 152                       FIELD NAME: REQUESTED IV LIMITATION
  LOCATION: 2.5;4                       ACCESS: Read w/Fileman
FIELD NUMBER: 156                       FIELD NAME: INDICATION FOR USE
  LOCATION: 18;1                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(55,D0,IV,D1,5,0
FIELD NUMBER: .01                       FIELD NAME: PROVIDER COMMENTS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(55,D0,IV,D1,AD,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
FIELD NUMBER: .03                       FIELD NAME: BOTTLE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(55,D0,IV,D1,SOL,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 REFERENCE: PS(55,D0,NVA,0
FIELD NUMBER: .01                       FIELD NAME: ORDERABLE ITEM
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DISPENSE DRUG
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DOSAGE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: MEDICATION ROUTE
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: SCHEDULE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: STATUS
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: ORDER NUMBER
  LOCATION: 0;8                         ACCESS: Read w/Fileman
FIELD NUMBER: 8                         FIELD NAME: START DATE
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: DOCUMENTED DATE
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: DOCUMENTED BY
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: CLINIC
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 15                        FIELD NAME: INDICATION FOR USE
  LOCATION: 2;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(55,D0,NVA,D1,DSC,0
FIELD NUMBER: .01                       FIELD NAME: DISCLAIMER
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(55,D0,NVA,D1,1,0
FIELD NUMBER: .01                       FIELD NAME: COMMENTS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(55,D0,5,D1,15,0
FIELD NUMBER: .01                       FIELD NAME: SPECIAL INSTRUCTIONS (LONG)
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(55,D0,IV,D1,10,0
FIELD NUMBER: .01                       FIELD NAME: SPECIAL INSTRUCTIONS (LONG)
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: PS(55,D0,5,D1,4
FIELD NUMBER: 18                        FIELD NAME: VERIFYING PHARMACIST
  LOCATION: 4;3                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This ICR supports the medication reconciliation feature
 in COMPREHENSIVE CARE COORDINATION.  Reading from file 55 will allow
 COMPREHENSIVE CARE COORDINATION to display order details for verified Unit
 Dose, verified IV medications, and Non-VA medications.  
  STATUS: Active
SUBSCRIBING PACKAGE: COMPREHENSIVE CARE COORDINATION
 SUBSCRIBING DETAILS:   ADDED 04/07/2022, effective with DSSV 1.1 DSS Class 3
 product Document Only 
SUBSCRIBING PACKAGE: BAR CODE MED ADMIN
 SUBSCRIBING DETAILS:   Added 9/12/25, effective with PSB*3.0*156 as part of
 the HDSO Sustainment which need to identify the Pharmacist who verified the
 order, field #18 VERIFYING PHARMACIST 

NUMBER: 7331                            IA #: 7331
  DATE CREATED: MAR 16, 2022
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RAO7UTL
  NAME: Setup Rad/Nuc Med HL7 Variable Definition for OE 
  ID: RAO7UTL                           STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   Routine RAO7UTL is used to define HL7 variables in
 preparation for filing a radiology order into the ORDER File (#100). 
VARIABLES: RAHLFS()                     TYPE: Output
 VARIABLES DESCRIPTION:   The HL7 field separator (primary delimiter) and
 empty-field variable (in RAHLFS(0)). 
VARIABLES: RAECH()                      TYPE: Output
 VARIABLES DESCRIPTION:   The HL7 encoding characters (secondary delimiter) and
 encoding-character array. 
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Patch MECH*1.0*1 processes HL7 new-order messages about
 imaging studies performed in the community but not entered through VistA.  In
 order to do this, it needs to invoke Radiology routines and make FileMan calls
 to add entries to the RAD/NUC MED PATIENT File (#70) (for existing VA
 patients), the ORDER File (#100), and the RAD/NUC MED ORDERS File (#75.1). The
 patch then creates an HL7 order-update message that transmits the study's 
 accession number to the sender. ADDED 3/2/2022, effective with MECH*1.0*1 
 Medicom Class 3 product Document Only 
  DATE ACTIVATED: MAR 16, 2022

NUMBER: 7332                            IA #: 7332
  DATE CREATED: MAR 16, 2022
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RAO7NEW
  NAME: Rad/Nuc Med Order File Entry Creation 
  ID: RAO7NEW                           STATUS: Active
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN1
VARIABLES: INPUT                        TYPE: Input
  VARIABLE SEQUENCE NUMBER: 1
 VARIABLES DESCRIPTION:   Formal parameter containing the radiology order IEN. 
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Patch MECH*1.0*1 processes HL7 new-order messages about
 imaging studies performed in the community but not entered through VistA.  In
 order to do this, it needs to invoke Radiology routines and make FileMan calls
 to add entries to the RAD/NUC MED PATIENT File (#70) (for existing VA
 patients), the ORDER File (#100), and the RAD/NUC MED ORDERS File (#75.1). The
 patch then creates an HL7 order-update message that transmits the study's 
 accession number to the sender. ADDED 3/2/2022, effective with MECH*1.0*1 
 Medicom Class 3 product Document Only 
  DATE ACTIVATED: MAR 16, 2022

NUMBER: 7333                            IA #: 7333
  DATE CREATED: MAR 16, 2022
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RAMAG03D
  NAME: Rad/Nuc Med Case Number Utility 
  ID: RAMAG03D
 GENERAL DESCRIPTION:   Function $$CASENUM^RAMAG03D() obtains a case number for
 an exam.  Usage of this function will allow new exams to be filed upon receipt
 of an HL7 message from a commercial image manager for patients on whom imaging
 has been performed by an outside community provider without an order having 
 previously been entered into VistA. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CASENUM
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Patch MECH*1.0*1 processes HL7 new-order messages about
 imaging studies performed in the community but not entered through VistA.  In
 order to do this, it needs to invoke Radiology routines and make FileMan calls
 to add entries to the RAD/NUC MED PATIENT File (#70) (for existing VA
 patients), the ORDER File (#100), and the RAD/NUC MED ORDERS File (#75.1). The
 patch then creates an HL7 order-update message that transmits the study's
 accession number to the sender. ADDED 3/2/2022, effective with MECH*1.0*1 
 Medicom Class 3 product Document Only 
  DATE ACTIVATED: MAR 16, 2022

NUMBER: 7334                            IA #: 7334
  DATE CREATED: APR 01, 2022
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: OR VIMM MENU
 GENERAL DESCRIPTION:   The PCE package requests the following options to be
 added to the Immunization/Skin Test Data Entry parameters [OR VIMM MENU] menu: 
  
   Edit Sequence for Immunization Forms [PXV EDIT SEQUENCE] 
  
   Immunization Default Responses Enter/Edit [PXV EDIT DEFAULT RESPONSES] 
  
   Edit Skin Test Reading CPT Code  [PXV SKIN TEST READING CPT] 
  
 VIMM functionality crosses multiple namespaces, including the OR and PX 
 namespaces. This change provides one menu that has all the options a CAC will
 need to configure VIMM, instead of having to go to multiple places.  
  
 The PCE options will be added to the OR VIMM MENU during the OR*3*405 post 
 installation processing.  
  STATUS: Active
KEYWORDS: OR VIMM MENU
KEYWORDS: PXV EDIT SEQUENCE
KEYWORDS: PXV EDIT DEFAULT RESPONSES
KEYWORDS: PXV SKIN TEST READING CPT
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  DATE ACTIVATED: APR 12, 2022

NUMBER: 7335                            IA #: 7335
  DATE CREATED: APR 18, 2022
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORINDRP
  NAME: OR INDICATION USAGE REPORT      ID: ORINDRP
 GENERAL DESCRIPTION:   Pharmacy Data Management (PDM) requests to make a call
 to EN^ORINDRP that generates Indication Usage Report. This report is mostly
 used by Pharmacists to manage the use of Indications by the provder.  A new
 option, Indication Usage Report [PSS INDICATION USAGE REPORT] will provide the
 Pharmacists the option of generating the Indication Usage Report in the PSS
 namespace.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  DATE ACTIVATED: APR 21, 2022

NUMBER: 7336                            IA #: 7336
  DATE CREATED: APR 21, 2022
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: Routine
  ROUTINE: GMRCIEVT
  NAME: EHRM IO Order Resubmission - GMRCIEVT
  ID: GMRCIEVT                          STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
KEYWORDS: EHRM
COMPONENT/ENTRY POINT: NW
 COMPONENT DESCRIPTION:   Generates and transmits an order HL7 message.  
VARIABLES: GMRCDA                       TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to REQUEST/CONSULTATION file (#123).  
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   When an IFC order is entered at a non-converted site
 and sent to a converted site, if the patient is not registered at the convered
 site, Cerner Millennium sends an acknowledge accpted HL7 message even though 
 Millennium ignores the order.  
  
 The EHM IFC ORDER RESUBMISSION 1.0 build creates a mechanism so that VistA can
 automatically resubmit the order a day later when it is expected that the
 patient will be registered in Cerner Millennium.  This build recognizes IFC
 orders that Cerner ignores and logs them.  A scheduled process scans the log
 and resubmits the orders to Cerner.  To do this, the process calls NW^GMRCIEVT
 to generate and transmit the order again.  

NUMBER: 7337                            IA #: 7337
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123,
  DATE CREATED: APR 21, 2022
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  NAME: EHRM IO Order Resubmission - file #123
  ID: GMR(123,
GLOBAL REFERENCE: GMR(123,D0,40,
FIELD NUMBER: 1                         FIELD NAME: ACTIVITY
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: EHRM
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   When an IFC order is entered at a non-converted site
 and sent to a converted site, if the patient is not registered at the convered
 site, Cerner Millennium sends an acknowledge accpted HL7 message even though 
 Millennium ignores the order.  
  
 The EHM IFC ORDER RESUBMISSION 1.0 build creates a mechanism so that VistA can
 automatically resubmit the order a day later when it is expected that the
 patient will be registered in Cerner Millennium.  This build recognizes IFC
 orders that Cerner ignores and logs them.  A scheduled process scans the log
 and resubmits the orders to Cerner.  To do this, the process calls NW^GMRCIEVT
 to generate and transmit the order again.  Before doing so, the code must set
 the ACTN variable to point to the entry in the REQUEST PROCESSING ACTIVITY
 multiple (field #40) in the REQUEST/CONSULTATION file (#123) that corresponds
 to the ENTERED IN CPRS (1) or CPRS RELEASED ORDER (2) activity (field #1 in
 the multiple) since NW^GMRCIEVT requires that ACTN be set.  

NUMBER: 7338                            IA #: 7338
  DATE CREATED: APR 28, 2022
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RAMAG06
  NAME: Radiology/Nuclear Medicine Report Completion Utility
  ID: RAMAG06
 GENERAL DESCRIPTION:   Function $$COMPLETE^RAMAG06() files report information
 onto a Radiology / Nuclear Medicine examination record and sets the exam
 status to Complete.  Usage of this function will allow new exams to be filed
 upon receipt of an HL7 message from a commercial image manager for patients on 
 whom imaging has been performed by an outside community provider without an
 order having previously been entered into VistA. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: MEDICOM
COMPONENT/ENTRY POINT: COMPLETE
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES

NUMBER: 7339                            IA #: 7339
  DATE CREATED: MAY 16, 2022            CUSTODIAL PACKAGE: LAB SERVICE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: LRAPDLG
  NAME: LRAPDLG                         ID: LRAPDLG
 GENERAL DESCRIPTION:   The Order Entry/Results Reporting package desires to
 set up an integration agreement with the Lab Service package to utilize APIs
 related to Anatomic Pathology (AP) Order Dialogs.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$OK4CPRS
 COMPONENT DESCRIPTION:   Checks if the LAB test is allowed as an AP Dialog in
 CPRS (1=Allowed; 0=Not Allowed).  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   LABORATORY TEST File (#60) IEN.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAY 16, 2022

NUMBER: 7340                            IA #: 7340
  FILE NUMBER: 728.44                   GLOBAL ROOT: ECX(728.44
  DATE CREATED: JUL 01, 2022            CUSTODIAL PACKAGE: EVENT CAPTURE
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SDESUTIL
  ID: ECX(728.44
GLOBAL REFERENCE: ECX(728.44,D0,0)
FIELD NUMBER: 7                         FIELD NAME: NATIONAL CODE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Scheduling package requests permission to look at
 the CLINICS AND STOP CODES (#728.44) file to get the NATIONAL CODE (#7) field. 
  
 The $$CHAR4 function was deployed in Scheduling routine, SDESUTIL, with patch
 SD*5.3*820 and will utilize FileMan calls to retrieve the external value of
 the NATIONAL CODE (#7) field.  
  
 COMPONENT: $$CHAR4 
            Utility to return the external format of the NATIONAL CODE (#7) 
            field from the CLINICS AND STOP CODES (#728.44) file.  
  
 Variables: Input  NAME (#.01) field from the HOSPITAL LOCATION (#44) file.  
  
 Variables: Output NATIONAL CODE (#7) field from the CLINICS AND STOP 
            CODES (#728.44) file in external format.  
  STATUS: Active
KEYWORDS: CHAR4
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: JUL 21, 2022

NUMBER: 7341                            IA #: 7341
  DATE CREATED: JUL 05, 2022            CUSTODIAL PACKAGE: ENGINEERING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ENWOD2
  NAME: PMI WORKLISTS - EQUIPMENT NOTES
  ID: ENWOD2
 GENERAL DESCRIPTION:   Above Par requests permission to call NOTES^ENWOD2 to
 check an Equipment entry's flag situations for display on the PMI Worksheet
 print.  
  
 Returns ENX array and the Number of lines returned.  
  STATUS: Active
KEYWORDS: ABOVE PAR
KEYWORDS: APAR
COMPONENT/ENTRY POINT: NOTES
 COMPONENT DESCRIPTION:   NOTES returns ENX ARRAY 
  ENX(1) Warranty expiration 6914,2 
  ENX(2) Condition code 6914,53 
  ENX(3) Lockout/Tagout 6914 0;5 
  ENX(4)= Deferred PM work order and 
   ENX("WO", ENX("T", ENX(7), ENX(9) 
VARIABLES: EQIEN                        TYPE: Input
 VARIABLES DESCRIPTION:   Equipment IEN 
SUBSCRIBING PACKAGE: ABOVE PAR
  DATE ACTIVATED: JUL 11, 2022

NUMBER: 7342                            IA #: 7342
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123
  DATE CREATED: JUL 19, 2022
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: CCRA READ ACCESS TO THE REQUEST CONSULTATION FILE
  ID: GMR(123
GLOBAL REFERENCE: GMR(123,DA,0
FIELD NUMBER: 2                         FIELD NAME: FROM
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The hospital location that is sending the order.  
 GENERAL DESCRIPTION:   The Community Care Referrals and Authorization (CCRA)
 project wants to use a FileMan read to the FROM Field (2) in the REQUEST
 CONSULTATION FILE (#123). This location will be used to link a CCRA Text 
 Integration Utility (TIU) Note's location to the visit location.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMRC
KEYWORDS: CCRA
KEYWORDS: REQUEST CONSULTATION
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Effective with TIU*1.0*352 
  DATE ACTIVATED: JUL 21, 2022

NUMBER: 7343                            IA #: 7343
  DATE CREATED: JUL 20, 2022            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSJSTSTP
  NAME: PSJSTSTP                        ID: PSJSTSTP
 GENERAL DESCRIPTION:   INPATIENT MEDICATIONS application provides two APIs
 implemented in PSJSTSTP routine: 
  
 STRSTP - calculate standard start date/time, duration, expected first dose,
 stop date/time and to provide information in regards to overriding the stop
 dates by providers if this was set for the orderable item on the system (site)
 level. Data returned by this API is used for purposes of editing quick orders
 and using them in CPRS.  
  
 LIMITS - return system (site) level default 'DAY (nD) or DOSE (nL) LIMIT' 
 value of the orderable item in the PHARMACY ORDERABLE ITEM FILE #50.7.  
  STATUS: Active
KEYWORDS: STRSTP
KEYWORDS: LIMITS
COMPONENT/ENTRY POINT: $$LIMITS(IEN507)
 COMPONENT DESCRIPTION:   Return system (site) level default 'DAY (nD) or DOSE
 (nL) LIMIT' value of the orderable item in the PHARMACY ORDERABLE ITEM FILE
 (#50.7).  
VARIABLES: IEN507                       TYPE: Input
 VARIABLES DESCRIPTION:   this is the internal entry number from the PHARMACY
 ORDERABLE ITEM FILE (#50.7) [REQUIRED] 
VARIABLES: $$LIMITS(IEN507)             TYPE: Output
 VARIABLES DESCRIPTION:   If data is found, then the API returns a string with
 values separated by "^": 
  Piece #1: LIMIT - value of the (#1) DAY (nD) or DOSE (nL) LIMIT field of the
 (#.055) DAY/ DOSE LIMIT multiple entry or the (#.05) DAY (nD) or DOSE (nL)
 LIMIT field of the file (#50.7).  
  Piece #2: CAN PROVIDER OVERRIDE STOP DATE? - value of the (#2) CAN PROVIDER
 OVERRIDE LIMIT? field of the (#.055) DAY/DOSE LIMIT multiple entry.  
  Piece #3: OVERRIDE MESSAGE - value of the (#3) OVERRIDE MESSAGE field of the
 (#.055) DAY/DOSE LIMIT multiple entry. If nothing found, then returns "".  
COMPONENT/ENTRY POINT: $$STRSTP(PSGSHED,OI,PSGORST,PSGDRG)
 COMPONENT DESCRIPTION:   STRSTP calculates standard start date/time, duration,
 expected first dose and stop date/time. It also provides information in
 regards to overriding the stop dates by providers if this was set for the
 orderable item on the system (site) level.  
VARIABLES: PSGSHED                      TYPE: Input
 VARIABLES DESCRIPTION:   PSGSHED - this is the internal entry number from the 
 ADMINISTRATION SCHEDULE FILE (#51.1) [OPTIONAL] 
VARIABLES: OI                           TYPE: Input
 VARIABLES DESCRIPTION:   OI - this is the internal entry number from the
 PHARMACY ORDERABLE ITEM FILE (#50.7) [OPTIONAL] 
VARIABLES: PSGORST                      TYPE: Input
 VARIABLES DESCRIPTION:   PSGORST - this is the order start date. 'NOW' will be
 used as a default value if no start date was provided [OPTIONAL] 
VARIABLES: PSGDRG                       TYPE: Input
 VARIABLES DESCRIPTION:   PSGDRG - this is the internal entry number from the 
 DRUG FILE (#50) [OPTIONAL] 
VARIABLES: $$STRSTP                     TYPE: Output
 VARIABLES DESCRIPTION:   If data is found, then the API returns a string with
 values separated by "^": 
  Piece #1 DEFAULT START DATE/TIME 
  Piece #2 ORDER DURATION (NUMBER OF DAYS ORDER LASTS OR NUMBER OF HOURS ORDER
 LASTS) 
  Piece #3 EXPECTED FIRST DOSE 
  Piece #4 STOP DATE 
  Piece #5 CAN PROVIDER OVERRIDE STOP DATE? 
  Piece #6 OVERRIDE MESSAGE If nothing is found, then returns "".  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: AUG 01, 2022

NUMBER: 7344                            IA #: 7344
  DATE CREATED: JUL 20, 2022
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: EXCLUDE ONETIME SCHEDULE PARAMETERS
 GENERAL DESCRIPTION:   Provide read-only access to the 'PSS EXCLUDE 1TIME
 STRSTP MODS' parameter entries in the PARAMETER file (#8989.5).  
  STATUS: Active
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   The "PSS EXCLUDE 1TIME STRSTP MODS" parameter entries
 store the list of certain admin schedule entries that should be excluded from
 start/stop date modifications. The INPATIENT MEDICATIONS (PSJ) application
 needs this access to perform start/stop dates calculation for inpatient 
 pharmacy orders.  
  DATE ACTIVATED: JUL 29, 2022

NUMBER: 7345                            IA #: 7345
  DATE CREATED: JUL 22, 2022            CUSTODIAL PACKAGE: INPATIENT MEDICATIONS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PSJHLU                       NAME: Calls to PSJHLU - use 2945 instead
  ID: PSJHLU
 GENERAL DESCRIPTION:   *The Inpatient Medications developer requested this ICR
 be withdrawn, and use 2945 instead* 
  
 This DBIA documents calls to PSJHLU.  
  STATUS: Withdrawn
COMPONENT/ENTRY POINT: ENI
 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
 SUBSCRIBING DETAILS:   OE/RR calls ENI.  

NUMBER: 7346                            IA #: 7346
  DATE CREATED: JUL 22, 2022            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFCCRNR
  NAME: VAFCCRNR                        ID: VAFCCRNR
 GENERAL DESCRIPTION:   EHRM MIGRATED FACILITIES FILE (#391.919) Utilities 
  
 8/11/26: Added optional parameter VAFCDCNV to component $$CRNRSITE effective
 with patch DG*5.3*1169 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$CRNRSITE
 COMPONENT DESCRIPTION:   This API accepts a site's Station Number to determine
 via a lookup on the "ACRNR" cross-reference (X-REF) in the EHRM MIGRATED
 FACILITIES (#391.919) file on whether or not that site has migrated to CERNER
 (i.e., Is Cerner Enabled). The API call will return a '1' if the site has
 migrated, else a '0' will be returned. NOTE: If the optional parameter
 VAFCDCNV is set to true (1) then the API call will return the date the site 
 converted as additional '^' delimited data if the site has migrated
 ('1^DateConverted').  
VARIABLES: VAFCSTNUM                    TYPE: Input
 VARIABLES DESCRIPTION:   Station number to check.  
VARIABLES: VAFCDCNV                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) If '1' then also return the date the site 
 was converted to CERNER.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   OE/RR would like to subscribe to this API for patch
 OR*3.0*588. This API will be used by OE/RR to determine if a site has migrated
 to Cerner.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Added 9/20/22, effective with GMRC*3*192 
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   Added 3/13/24 effective with EHM*1*10 which creates an
 HL7 message repository (EHRM HL7 Message #1609) for IFC and PRF messages sent
 to or received from Cerner. Parsing and extracting data from the HL7 message 
 depends on whether the site associated with the placer or filler order number
 is converted or not.  Would like to call $$CRNRSITE^VAFCCRNR to make that
 determination.  
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   Added 3/13/24, effective with RMPR*3*215 which
 introduces a new feature to the Prosthetics Suspense Processing menu by use of
 $$CRNRSITE^VAFCCRNR to make the determination so that non-converted sites will
 not see the new feature until they are converted to Cerner.  
  DATE ACTIVATED: NOV 03, 2022

NUMBER: 7347                            IA #: 7347
  DATE CREATED: JUL 25, 2022
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSEXLST
  NAME: PSSEXLST                        ID: PSSEXLST
 GENERAL DESCRIPTION:   API to check if the ONE-TIME prescription admin
 schedule is excluded from start/stop dates modifications.  
  STATUS: Active
KEYWORDS: CHK1TIME
COMPONENT/ENTRY POINT: CHK1TIME
VARIABLES: $$CHK1TIME                   TYPE: Output
 VARIABLES DESCRIPTION:   Returns: 
  
 0 - if invalid parameters or if admin schedule passed in SCHED is not ONE-TIME
 schedule (i.e. if TYPE OF SCHEDULE (#5) field in the file ADMINISTRATION
 SCHEDULE FILE #(51.1) is not "ONE-TIME"), 
  
 1^Y - if SCHED is ONE-TIME schedule and it is excluded from start/stop 
 override, 
  
 1^N - if SCHED is ONE-TIME schedule and it is NOT excluded from start/stop 
 override.  
VARIABLES: SCHED                        TYPE: Input
 VARIABLES DESCRIPTION:   this is the value of (#.01) NAME field of the
 ADMINISTRATION SCHEDULE FILE (#51.1) [REQUIRED] 
VARIABLES: HOSPLOC                      TYPE: Input
 VARIABLES DESCRIPTION:   this is the internal entry number from the HOSPITAL
 LOCATION FILE (#44) [REQUIRED] 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 8/30/22, effective with OR*3.0*439 
  DATE ACTIVATED: AUG 30, 2022

NUMBER: 7348                            IA #: 7348
  FILE NUMBER: 728.441                  GLOBAL ROOT: ECX(728.441
  DATE CREATED: AUG 04, 2022            CUSTODIAL PACKAGE: EVENT CAPTURE
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDTMPUTL
  NAME: SDTMPUTL                        ID: SDTMPUTL
GLOBAL REFERENCE: ECX(728.441,D0,0)
FIELD NUMBER: 1                         FIELD NAME: SHORT DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The short description for the type of clinic represented
 by this national code.  
 GENERAL DESCRIPTION:   The Scheduling package requests permission to look at
 the NATIONAL CLINIC FILE (#728.441) file to get the SHORT DESCRIPTION (#1)
 field.  
  
 The $$CHAR4DSC function was deployed in Telehealth Management Platform (TMP)
 Scheduling routine, SDTMPUTL, with patch SD*5.3*821 and will utilize FileMan
 calls to retrieve the external value of the SHORT DESCRIPTION (#1) field.  
  STATUS: Active
KEYWORDS: CHAR4
KEYWORDS: DESCRIPTION
COMPONENT/ENTRY POINT: $$CHAR4DSC
 COMPONENT DESCRIPTION:   Utility to return the external format of the SHORT
 DESCRIPTION (#1) 
VARIABLES: CHAR4                        TYPE: Input
 VARIABLES DESCRIPTION:   NATIONAL CODE (#7) field from CLINIC AND STOP CODES
 (#728.44) file  in exernal format.  
VARIABLES: SHORT DESCRIPTION            TYPE: Output
 VARIABLES DESCRIPTION:   (#1) field from the NATIONAL CLINIC FILE (#728.441) 
SUBSCRIBING PACKAGE: SCHEDULING
  DATE ACTIVATED: AUG 16, 2022

NUMBER: 7349                            IA #: 7349
  FILE NUMBER: 101.41                   GLOBAL ROOT: ORD(101.41
  DATE CREATED: AUG 16, 2022
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORQOUTL
  NAME: ORQOUTL                         ID: ORQOUTL
GLOBAL REFERENCE: ORD(101.41,'B'
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The Order Dialog Name. 
GLOBAL REFERENCE: ORD(101.41,D0,6,'D',D1
FIELD NUMBER: .02                       FIELD NAME: POINTER TO ORDER DIA
  LOCATION: 6;2                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This field is the pointer to the Order Dialog for this
 Order Item.  PDM is using this look up to find the record in the Responses
 Multiple for the Orderable Item.  
FIELD NUMBER: .01                       FIELD NAME: ORDER ITEM
  LOCATION: 6;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   PDM uses this field to insure the right entry is
 retrieved by comparing this field to the Schedule file entry.  
GLOBAL REFERENCE: ORD(101.41,D0,0
FIELD NUMBER: 5                         FIELD NAME: DISPLAY GROUP
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   This is the pointer to the DISPLAY GROUP FILE (#100.98)
 that has been defined for this Order Dialog.  
 GENERAL DESCRIPTION:   The original API was released with CPRS 31B and
 modified a little bit in 32B for real time utilities that are using it. The
 31B and 32B structures are as follows: 
  
 FINDQO(RESULT,INPUT,SUB,RETMENU,RETSTRCT) 31B version of the code 
 FINDQO(RESULT,INPUT,SUB,RETMENU,RETSTRCT,SPINNER,SKIPDIS) 32B version of the
 code.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PDM
COMPONENT/ENTRY POINT: FINDQO(RESULT,INPUT,SUB,RETMENU,RETSTRCT,SPINNER,SKIPDIS)
 COMPONENT DESCRIPTION:   CPRS v31B: This API is designed to return all QO of a
 certain type that allows the calling application to review the data.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Result is the output which is returns in ^TMP($J,SUB) 
VARIABLES: INPUT                        TYPE: Input
 VARIABLES DESCRIPTION:   Array of Order Dialogs to search for, for example if
 looking for Outpatients Meds QO you will set it up like INPUTS("PSO OERR")="" 
VARIABLES: SUB                          TYPE: Input
 VARIABLES DESCRIPTION:   Sub is the subscript to return the results in a the
 TMP global.  
VARIABLES: RETMENU                      TYPE: Input
 VARIABLES DESCRIPTION:   RETMENU set to either 0 or 1. If set to 1 will return
 the list of Order Menu and Reminder Dialogs that is using the QO.  
VARIABLES: RETSTRCT                     TYPE: Input
 VARIABLES DESCRIPTION:   RETSTRCT set to either 0 or 1. Will return the QO
 structure in the temp global this is basically a merge of the ORDIALOG array
 into the TMP global. ORDIALOG array is the internal array used by all of OR.  
VARIABLES: SPINNER                      TYPE: Input
 VARIABLES DESCRIPTION:   SPINNER - Used in CPRS 32B version of this API.  Set
 to 1 to write out a spinner as the API is searching for QO. Set to 0 to not
 display a progress spinner.  
VARIABLES: SKIPDIS                      TYPE: Input
 VARIABLES DESCRIPTION:   SKIPDIS - Used in CPRS 32B version of this API.  Set
 to 1 to have the API not return QO that are disabled. Set to 0 to have the API
 return disable QO in the output.  
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  DATE ACTIVATED: AUG 26, 2022

NUMBER: 7350                            IA #: 7350
  DATE CREATED: AUG 18, 2022            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Supported                      TYPE: Routine
  ROUTINE: DGENDBS                      NAME: DG TEMPORARY ADDRESS UPDATE
  ID: DGENDBS
 GENERAL DESCRIPTION:   Use API $$UPD^DGENDBS to update the following temporary
 address fields ln the PATIENT (#2) file.  
  
 TEMPORARY STREET [LINE 1]    (#.1211) TEMPORARY STREET [LINE 2]    (#.1212) 
 TEMPORARY STREET [LINE 3]    (#.1213) TEMPORARY CITY               (#.1214) 
 TEMPORARY STATE              (#.1215) TEMPORARY ZIP CODE           (#.1216) 
 TEMPORARY ADDRESS START DATE (#.1217) TEMPORARY ADDRESS END DATE   (#.1218) 
 TEMPORARY ADDRESS ACTIVE?    (#.12105) TEMPORARY ZIP+4              (#.12112) 
 TEMPORARY ADDRESS COUNTY     (#.12111) TEMPORARY ADDRESS PROVINCE   (#.1221) 
 TEMPORARY ADDRESS POSTAL CODE (#.1222) TEMPORARY ADDRESS COUNTRY     (#.1223) 
  
  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: TEMPORARY
KEYWORDS: ADDRESS
KEYWORDS: UPDATE
COMPONENT/ENTRY POINT: UPD
 COMPONENT DESCRIPTION:   File data into an existing record.  
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   File or sub-file number.  
VARIABLES: DGENDA                       TYPE: Input
 VARIABLES DESCRIPTION:   New name for traditional DA array, with same meaning. 
 
 Pass by reference 
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   Data array to file (pass by reference).  Format:
 DATA(<field #>)=<value> 
  

NUMBER: 7351                            IA #: 7351
  DATE CREATED: AUG 24, 2022            CUSTODIAL PACKAGE: CMOP
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSXRPPL1
  NAME: PSXRPPL1                        ID: PSXRPPL1
 GENERAL DESCRIPTION:   The MCCF EDI TAS project needs to access the $$TRICVANB
 component in PSXRPPL1, effective with PSO*7.0*681. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSXRPPL1
KEYWORDS: TRICARE
KEYWORDS: CHAMPVA
COMPONENT/ENTRY POINT: $$TRICVANB
 COMPONENT DESCRIPTION:   This function will return '1' if the given
 prescription/fill is for a TRICARE or CHAMPVA patient, there is already an
 eT/eC pseudo reject on the prescription, and that reject has been
 closed/resolved.  Otherwise, it will return '0'.  eT and eC are reject codes
 applied to TRICARE/ CHAMPVA prescriptions which the system determines to be
 non-billable prior to any claims being sent.  
VARIABLES: PSXRX                        TYPE: Input
 VARIABLES DESCRIPTION:   PSXRX is a prescription IEN, pointer to file 52
 PRESCRIPTION.  This value is required.  
VARIABLES: PSXRFL                       TYPE: Input
 VARIABLES DESCRIPTION:   PSXRFL is a fill number. <blank> or 0 indicates the
 original fill.  This value is required.  
VARIABLES: $$TRICVANB                   TYPE: Output
 VARIABLES DESCRIPTION:   This function will return '1' if the given
 prescription/fill is for a TRICARE or CHAMPVA patient, there is already an
 eT/eC pseudo reject on the prescription, and that reject has been
 closed/resolved.  Otherwise, it will return '0'.  eT and eC are reject codes
 applied to TRICARE/ CHAMPVA prescriptions which the system determines to be
 non-billable prior to any claims being sent.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: SEP 28, 2022

NUMBER: 7352                            IA #: 7352
  DATE CREATED: AUG 24, 2022            CUSTODIAL PACKAGE: CMOP
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSXRPPL2
  NAME: PSXRPPL2                        ID: PSXRPPL2
 GENERAL DESCRIPTION:   The MCCF EDI TAS project needs to access the $$ECETREJ
 component in PSXRPPL2, effective with PSO*7.0*681. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSXRPPL2
KEYWORDS: TRICARE
KEYWORDS: CHAMPVA
COMPONENT/ENTRY POINT: $$ECETREJ
 COMPONENT DESCRIPTION:   This function returns '1' if the given prescription
 has an open/unresolved eT/eC pseudo reject.  Otherwise, it returns '0'.  eT
 and eC are reject codes applied to TRICARE/CHAMPVA prescriptions which the
 system determines to be non-billable prior to any claims being sent.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   RX is a prescription IEN, pointer to file 52
 PRESCRIPTION.  This value is required.  
VARIABLES: $$ECETREJ                    TYPE: Output
 VARIABLES DESCRIPTION:   This function returns '1' if the given prescription
 has an open/unresolved eT/eC pseudo reject.  Otherwise, it returns '0'.  eT
 and eC are reject codes applied to TRICARE/CHAMPVA prescriptions which the
 system determines to be non-billable prior to any claims being sent.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE
 SUBSCRIBING DETAILS:   Added 5/15/223, effective with BPS*1.0*35, PSO*7.0*702,
 IB*2.0*712, PSS*1.0*260, to call $$ECETREJ^PSXRPPL2 from a BPS routine.  
  DATE ACTIVATED: SEP 28, 2022

NUMBER: 7353                            IA #: 7353
  DATE CREATED: AUG 29, 2022
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORWPCE5
  NAME: GET MAGNITUDE AND UCUM CODE FOR ENTRY
  ID: ORWPCE5
 GENERAL DESCRIPTION:   Provide a way to return if a record for a file contains
 a possible magnitude range and ucum code.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ORWPCE5
COMPONENT/ENTRY POINT: MAGDAT
 COMPONENT DESCRIPTION:   This API takes a refernce to a file and a record
 entry and returns the possible magnitude and ucum for the record entry.  
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   This return a string balue in the format MINIMUM
 VALUE^MAXIMUM VALUE^MAXIMUM DECIMALS^UCUM CODE IEN^INTERNAL PROMPT 
 CAPTION^PROMPT CAPTION TO DISPLAY IN THE CALLING APPLICATION 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Type is the type of data to check can be set to one
 of the following values.  
  
 PED for file 9999999.09 XAM for file 9999999.15 HF for file 9999999.64 SC for
 file 811.2 
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Code is the IEN of the record to check for an
 Magnitude and UCUM value.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS

NUMBER: 7354                            IA #: 7354
  DATE CREATED: AUG 31, 2022            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: DG PTF ICD PROCEDURE NOTIFIER
 GENERAL DESCRIPTION:   The DG PTF ICD PROCEDURE NOTIFIER protocol notifies
 subscribers when an International Classification of Diseases (ICD) procedure
 code is added, modified or removed for entries within the PTF file (#45).  
   
 The following data is available to subscribers: 
   
 ^TMP("DG PTF ICD OP NOTIFIER",$J,"DATE")=DATE 
   DATE: FileMan date/time (internal format) of when the activity occurred.  
   
 ^TMP("DG PTF ICD OP NOTIFIER",$J,"DFN")=DFN 
   DFN: internal entry number of the patient in the PATIENT file (#2).  
   
 ^TMP("DG PTF ICD OP NOTIFIER",$J,TYPE,"IENS")=IENS 
  TYPE: The activity type; possible values are "DISCHARGE", "PROCEDURE", 
        and "SURGERY". "DISCHARGE" codes are from the PROCEDURE series of 
        fields on the 401P node in the PTF (#45) file.  
        "PROCEDURE" codes are from the PROCEDURE CODE series of fields 
        in the 601 sub-file (#45.05) of the PTF file (#45). "SURGERY" codes 
        are from the OPERATION CODE series of fields in the 401 sub-file 
        (#45.01) of the PTF (#45) file.  
   IENS: The internal entry number string identifying the record in which 
         the associated codes are stored.  
   
 ^TMP("DG PTF ICD OP NOTIFIER",$J,TYPE,FIELD,"OLD")=ICDP 
  This is how the field appeared in the file before the change was made.  
  FIELD: This is an abbreviation denoting which field the code came from.  
         The following table should assist in determining which field a 
         code came from: 
         TYPE        FIELD   Field Name 
         -----------------------------------------------------
         DISCHARGE   OPCnn   PROCEDURE nn (nn is a whole number) 
         PROCEDURE   OPCnn   PROCEDURE CODE nn (nn is a whole number) 
         SURGERY     OPCnn   OPERATION CODE nn (nn is a whole number) 
  ICDP: Internal entry number of the procedure code in the ICD OPERATION/ 
        PROCEDURE file (#80.1).  
   
 ^TMP("DG PTF ICD OP NOTIFIER",$J,TYPE,FIELD,"NEW")=ICDP 
  This is how the field appeared in the file after the change was made.  
   
 When a code is added, the "OLD" value will be blank and the "NEW" value will 
 not be. When a code is deleted, the "OLD" value will not be blank and the 
 "NEW" value will be. When a code is changed, both the "OLD" and "NEW" values 
 will not be blank.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DG PTF ICD PROCEDURE EVENT
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   VPR will add a listener VPR PTF OP EVENTS protocol to
 DG PTF ICD PROCEDURE NOTIFIER 
  DATE ACTIVATED: AUG 31, 2022

NUMBER: 7355                            IA #: 7355
  DATE CREATED: SEP 02, 2022            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  ROUTINE: PXRMINTR
  NAME: CLINICAL REMINDERS INPUT TRANSFORMS
  ID: PXRMINTR
 GENERAL DESCRIPTION:   This integration agreement allows the subscribing
 package to validate that data entered by the user conforms to Clinical
 Reminders standards and formats.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: VALID DATE/TIME
KEYWORDS: VALID NAME
COMPONENT/ENTRY POINT: $$VDT(STRING)
 COMPONENT DESCRIPTION:   Determine if the date/time value passed in is valid.  
VARIABLES: STRING                       TYPE: Input
 VARIABLES DESCRIPTION:   The date/time value to validate. This value may be an
 actual date (either in internal FileMan format or external format), a FileMan
 symbolic date or a Clinical Reminders symbolic date.  
VARIABLES: $$VDT                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 if the date/time value is valid or 0 if the
 date/time value is invalid.  
COMPONENT/ENTRY POINT: $$VNAME(STRING)
 COMPONENT DESCRIPTION:   Determine if the name value passed in is valid.  
VARIABLES: STRING                       TYPE: Input
 VARIABLES DESCRIPTION:   The name value to validate. Names do not contain the
 tilde character and only authorized users are allowed to prefix names with
 "VA-" (designating a national component).  
VARIABLES: $$VNAME                      TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 if the name value is valid or 0 if the name
 value is not valid.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   With patch OR*3*555, OE/RR will begin using this API as
 part of the Results Management functionality.  

NUMBER: 7356                            IA #: 7356
  DATE CREATED: SEP 14, 2022
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORACCESS
  NAME: ORACCESS API                    ID: ORACCESS
 GENERAL DESCRIPTION:   ICR 7356 was created to grant access to TIU and PXRM to
 be able to get information regarding whether or not a site was converted to a
 new EHRM, effective with patches OR*3*588, TIU*1*353, PXRM*2*82.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ACCESS
 COMPONENT DESCRIPTION:   This entry point returns an user CPRS write access
 values.  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DUZ 
VARIABLES: GETNOTES                     TYPE: Input
 VARIABLES DESCRIPTION:   Set to 1 to return the missing dependencies only for
 actions. Set to 2 to return a description.  
VARIABLES: NOTES                        TYPE: Output
 VARIABLES DESCRIPTION:   This is variable is populated when GETNOTES variable
 is defined greater than 0.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   This variable returns the user Write Access settings 
VARIABLES: TABNAMES                     TYPE: Output
 VARIABLES DESCRIPTION:   This variable returns CPRS tabs internal and external
 format.  
COMPONENT/ENTRY POINT: ONEHR
 COMPONENT DESCRIPTION:   This function returns a 1 if a site has transition to
 Electronic Health Record (EHR) and a 0 if it has not transition to EHR.  
COMPONENT/ENTRY POINT: TABNAMES
 COMPONENT DESCRIPTION:   Returns array of CPRS Tab names 
VARIABLES: TABS                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns array of CPRS tabs name in the following
 format: 
  
 TABS("INTERNAL NAME")="EXTERNAL NAME" 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: MAR 23, 2023

NUMBER: 7357                            IA #: 7357
  DATE CREATED: SEP 20, 2022
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORUTL
  NAME: TIU CALLS TO ISCLORD API        ID: ORUTL
 GENERAL DESCRIPTION:   TIU is calling $$ISCLORD^ORUTL when building the list
 of patient medications for the TIU medication objects. The call determines if
 a given medication is a "clinic order". Clinic orders are in the CLINIC 
 MEDICATIONS or CLINIC INFUSIONS display groups.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CLINIC ORDER
KEYWORDS: ISCLORD
KEYWORDS: ORUTL
COMPONENT/ENTRY POINT: ISCLORD
 COMPONENT DESCRIPTION:   ISCLORD accepts a return variable and the IEN from
 the ORDER file (#100) as arguments. If the DISPLAY GROUP of the order is found
 to be either CLINIC MEDICATIONS or CLINIC INFUSIONS, the API returns 1 (one), 
 otherwise return 0 (zero).  
VARIABLES: ORY                          TYPE: Input
 VARIABLES DESCRIPTION:   ORY will hold the return value, 0 (zero) or 1 (one).  
VARIABLES: ORIFN                        TYPE: Input
 VARIABLES DESCRIPTION:   ORIFN is the IEN of the order of interest from the
 ORDER file (#100).  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   TIU is calling ISCLORD^ORUTL from LIST^TIULMED 
  DATE ACTIVATED: SEP 20, 2022

NUMBER: 7358                            IA #: 7358
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123,
  DATE CREATED: OCT 12, 2022
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Controlled Subscription        TYPE: File
  NAME: TIU FILEMAN READ ACCESS TO THE REQUEST/CONSULTATION FILE
  ID: GMR(123,
GLOBAL REFERENCE: GMR(123,DA,0
FIELD NUMBER: 8                         FIELD NAME: CPRS STATUS
  LOCATION: O;12                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the current CPRS status of the consult or request
 order. The Action Types which may be taken from the "Select Action: " prompt
 update the status in this file as well as in the Orders File (100).  
 GENERAL DESCRIPTION:   The Community Care Referrals and Authorization (CCRA)
 project wants to use a FileMan read to the CPRS STATUS field (#8) in the 
 REQUEST/CONSULTATION FILE (#123). This field is used to reset the status to
 it's original state once a CCRA note is filed with the consult.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: TIU
KEYWORDS: GMRC
KEYWORDS: CPRS STATUS
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES

NUMBER: 7359                            IA #: 7359
  DATE CREATED: OCT 17, 2022            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  ROUTINE: PXRMLCR
  NAME: CLINICAL REMINDERS PATIENT LIST HELP TEXT
  ID: PXRMLCR
 GENERAL DESCRIPTION:   This integration agreement allows the subscribing
 package to display the help text that Clinical Reminders displays when
 requested by the user while building a patient list.  
  STATUS: Pending
KEYWORDS: REMINDER PATIENT LIST
KEYWORDS: PATIENT LIST
KEYWORDS: HELP TEXT
COMPONENT/ENTRY POINT: HELP(TYPE)
 COMPONENT DESCRIPTION:   Display the requested help text.  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   The type of help to display. Set to 1 for the help
 displayed at the "Okay to overwrite <PATIENT_LIST_NAME>?" prompt, 2 for the
 help displayed at the "Secure list?" prompt, 3 for the help displayed at the
 "Save due patients to a patient list:" prompt and 4 for the help displayed at
 the " 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   With patch OR*3*555, OE/RR will begin using this API as
 part of the Results Management functionality.  

NUMBER: 7360                            IA #: 7360
  DATE CREATED: OCT 27, 2022            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VAFCCRNR
  NAME: CERNER CERT and MOCK API        ID: VAFCCRNR
 GENERAL DESCRIPTION:   Two new APIs were created, by the MPI Team, to support
 multiple CERNER / HealthShare Enterprise Platform (HSEP) CERT and MOCK
 accounts that require multiple station numbers to exist in the Software
 Quality Assurance (SQA) environment.  Patch XWB*1.1*75 and OR*3.0*587 will
 require access to these APIs to appropriately determine to which Cerner domain
 the current VistA instance is connected.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: 200CRNR 200CRNC 200CRNM
COMPONENT/ENTRY POINT: $$GCRNSITE
 COMPONENT DESCRIPTION:   Returns the CERNER Station Number for the VistA
 Instance (ie. '200CRNR' or the SQA defined CERNER Station Number) 
COMPONENT/ENTRY POINT: $$ISCRNPAT
 COMPONENT DESCRIPTION:   Returns '0' (No) or '1' (Yes) if the passed patient
 identifier (DFN) is from CERNER.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient identifier 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 12/9/22, effective with patch OR*3.0*587 
SUBSCRIBING PACKAGE: PROSTHETICS
SUBSCRIBING PACKAGE: AUTOMATED LAB INSTRUMENTS
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Added 12/9/22, effective with patch GMRC*3.0*194 
SUBSCRIBING PACKAGE: RPC BROKER
 SUBSCRIBING DETAILS:   Added 12/9/22, effective with patch XWB*1.1*75 
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Added 12/9/22 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Added 12/9/22, effective with patch IB*2*756 
SUBSCRIBING PACKAGE: MENTAL HEALTH
 SUBSCRIBING DETAILS:   Added 12/9/22, effective with patch YS*5.01*219 
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 12/9/22 
  DATE ACTIVATED: OCT 31, 2022

NUMBER: 7361                            IA #: 7361
  DATE CREATED: NOV 02, 2022            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: MHV VistA Service account using SSOi SAML token
 GENERAL DESCRIPTION:   This ICR is to document the agreement for MHV to use a
 VistA Service account (NPE - Non Person Entity) using SSOi SAML token until
 MHV can transition to the SSOe implementation in VistA.  
  
 Background MHV needs to migrate from VIA to VDIF, due to VIA being
 decommissioned in fall 2022.  
  
 The VistA Infrastructure Shared Services (VISS) team, MHV package, and VistA
 Office Review Board have established steps to accomplish the migration: 
  
 1) Migrate MHV from VIA to VDIF: The goal is to safely tranition from VIA to
 VDIF in a timely manner. To accomplish ths, MHV will temporarily use a VistA
 Service account (NPE) using a SSOi SAML token.  
  
 2) VISS Implement VisA SSOe: The VISS team will enhance the SSOe 
 implementation in VistA to support secure patient login.  
  
 3)MHV Activates the SSOe: MHV Team will switch from the temporary VistA 
 service account to the SSOe implementation in VistA.  
  
 4) VISS Deactivates the temporary VistA service account.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SSOi SAML Token
KEYWORDS: VistA SSOe
SUBSCRIBING PACKAGE: MYHEALTHEVET
  DATE ACTIVATED: DEC 01, 2022

NUMBER: 7362                            IA #: 7362
  DATE CREATED: NOV 15, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC ARCLOSE
  REMOTE PROCEDURE: SDEC ARCLOSE
 GENERAL DESCRIPTION:   This RPC is due to be deprecated in April of 2023.  All
 consumers will need to transition to the appropriate Enterprise Appointment
 Service (EAS) web service to replace this functionality by that time 
  
 Remove a Patient from the Appointment Requested by setting the STATUS to 
 CLOSED and updating the DISPOSITION fields.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   via DTC Integration  Platform (DIP) (VASI: 2825) 
  DATE ACTIVATED: DEC 19, 2022

NUMBER: 7363                            IA #: 7363
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC APPTYPES
  REMOTE PROCEDURE: SDEC APPTYPES
 GENERAL DESCRIPTION:   
  Return all active Appointment types from the APPOINTMENT TYPE file 409.1 
  RETURN PARAMETER DESCRIPTION:   
  Dataset with columns APPTTYPE_IEN and APPTTYPE_NAME 
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825) to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: NOV 23, 2022

NUMBER: 7364                            IA #: 7364
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC ARGET
  REMOTE PROCEDURE: SDEC ARGET
 GENERAL DESCRIPTION:   This RPC retrieves appointment requests.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825) to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers.  
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7365                            IA #: 7365
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC AROPEN
  REMOTE PROCEDURE: SDEC AROPEN
 GENERAL DESCRIPTION:   This RPC is to re-open an appointment request.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825) to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7366                            IA #: 7366
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC ARSET
  REMOTE PROCEDURE: SDEC ARSET
 GENERAL DESCRIPTION:   This RPC is to add a new appointment request or update
 an appointment request.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825) to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7367                            IA #: 7367
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC CANCMT
  REMOTE PROCEDURE: SDEC CANCMT
 GENERAL DESCRIPTION:   This RPC Returns list of cancellation comments (hash
 tag, type and text) from the SDEC CANCELLATION COMMENT file (#409.88).  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825) to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7368                            IA #: 7368
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC CANREAS
  REMOTE PROCEDURE: SDEC CANREAS
 GENERAL DESCRIPTION:   This RPC return entries from the CANCELLATION REASONS
 file.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7369                            IA #: 7369
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC CLINSET
 GENERAL DESCRIPTION:   This RPC Returns CLINIC SETUP PARAMETERS for clinics
 that are active in the HOSPITAL LOCATION file.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7370                            IA #: 7370
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC CSLOTSCH
  REMOTE PROCEDURE: SDEC CSLOTSCH
 GENERAL DESCRIPTION:   This RPC retrieves Assigned Appointment Slot Schedule
 for a resource.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 14, 2022

NUMBER: 7371                            IA #: 7371
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: SDEC EDITAPPT                   REMOTE PROCEDURE: SDEC EDITAPPT
 GENERAL DESCRIPTION:   This RPC will Edit an appointment (only 'note text' and
 appointment length can be edited) 
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7372                            IA #: 7372
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC EP EVENT LOG
  REMOTE PROCEDURE: SDEC EP EVENT LOG
 GENERAL DESCRIPTION:   This RPC Provides Scheduling Expanded Entry Appointment
 Event Log to VSE for displaying in the GUI the VS Gui.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7373                            IA #: 7373
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC GETPRER
  REMOTE PROCEDURE: SDEC GETPRER
 GENERAL DESCRIPTION:   This RPC RETURNS ALL ENTRIES IN THE PREREQUISITE
 MULTIPLE FROM THE SDEC APPT REQUEST FILE 
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7374                            IA #: 7374
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC NEWPERS
  REMOTE PROCEDURE: SDEC NEWPERS
 GENERAL DESCRIPTION:   This RPC return entries from the NEW PERSON table 200
 that are 'active' AND have PROVIDER CLASS defined.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7375                            IA #: 7375
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC PCSTGET
  REMOTE PROCEDURE: SDEC PCSTGET
 GENERAL DESCRIPTION:   This RPC GET patient clinic status for a clinic stop
 for a given time frame - has the patient been seen by the given Clinic Stop
 code in the past 24 months 
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7376                            IA #: 7376
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC REP1GET
  REMOTE PROCEDURE: SDEC REP1GET
 GENERAL DESCRIPTION:   This RPC will GET clinic data for report.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7377                            IA #: 7377
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC RESCE
  REMOTE PROCEDURE: SDEC RESCE
 GENERAL DESCRIPTION:   This RPC Returns all active Clinics/Scheduling
 resources 
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7378                            IA #: 7378
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC RESOURCE
  REMOTE PROCEDURE: SDEC RESOURCE
 GENERAL DESCRIPTION:   This RPC Returns Recordset with ALL RESOURCE names.
 Inactive RESOURCES are NOT filtered out.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7379                            IA #: 7379
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC RESGPUSR
  REMOTE PROCEDURE: SDEC RESGPUSR
 GENERAL DESCRIPTION:   PC Returns ADO Recordset with all ACTIVE GROUP/RESOURCE
 combinations to which user has access based on entries in SDEC RESOURCE USER
 file If SDECDUZ=0 then returns all ACTIVE GROUP/RESOURCE combinations for
 current DUZ If user SDECDUZ possesses the key SDECZMGR then ALL ACTIVE
 resource group names are returned.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 

NUMBER: 7380                            IA #: 7380
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC VVC_APPT
  REMOTE PROCEDURE: SDEC VVC_APPT
 GENERAL DESCRIPTION:   If an appointment is for a VVC clinic, return the URL
 of the VVC Web app.  The NATIONAL entry in the SDEC Settings file (#409.98)
 stores the stop code that identifies a VVC clinic in field #5 (VVC Clinic Stop
 Code).  If the stop code for the clinic associated with the resource scheduled
 for the appointment equals this stop code, the RPC returns the value in field 
 #6 VVC APP URL of the NATIONAL entry in the SDEC Settings file.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7381                            IA #: 7381
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC VVS DELETE ID
  REMOTE PROCEDURE: SDEC VVS DELETE ID
 GENERAL DESCRIPTION:   This RPC deletes the Video Visit ID from the SDEC
 APPOINTMENT (#409.84) file.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7382                            IA #: 7382
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC VVS GET ID
  REMOTE PROCEDURE: SDEC VVS GET ID
 GENERAL DESCRIPTION:   This RPC returns the Video Visit Service (VVS) ID.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7383                            IA #: 7383
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC VVS SAVE ID
  REMOTE PROCEDURE: SDEC VVS SAVE ID
 GENERAL DESCRIPTION:   This RPC saves the VVS appointment ID in the SDEC
 APPOINTMENT (#409.84), field (#2).  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7384                            IA #: 7384
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDECLK LOCK
  REMOTE PROCEDURE: SDECLK LOCK
 GENERAL DESCRIPTION:   This RPC attempts to lock a request record. Request
 records are in one of these files: 
  SDEC APPT REQUEST 
  REQUEST/CONSULTATION 
  SD WAIT LIST 
  RECALL REMINDERS 
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7385                            IA #: 7385
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDECLK UNLOCK
  REMOTE PROCEDURE: SDECLK UNLOCK
 GENERAL DESCRIPTION:   This RPC unlocks the request record that was locked
 using SDECLK LOCK.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7386                            IA #: 7386
  DATE CREATED: NOV 17, 2022            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: SDEC57 OBM
  REMOTE PROCEDURE: SDEC57 OBM
 GENERAL DESCRIPTION:   This RPC will GET overbook status and return message.  
  
 This RPC is due to be deprecated in April of 2023.  All consumers will need to
 transition to the appropriate Enterprise Appointment Service (EAS) web service
 to replace this functionality by that time. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VISTALINK
 SUBSCRIBING DETAILS:   Via DTC Integration  Platform (DIP) (VASI: 2825)to VA
 Health Connect Scheduling/WellHive scheduling application for the Clinical
 Contact Centers. 
  DATE ACTIVATED: DEC 09, 2022

NUMBER: 7387                            IA #: 7387
  FILE NUMBER: 1.71                     GLOBAL ROOT: DIT(1.71,
  DATE CREATED: DEC 07, 2022            CUSTODIAL PACKAGE: 1
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: WORLD TIMEZONES FILE
  ID: DIT(1.71,
GLOBAL REFERENCE: DIT(1.71,
FIELD NUMBER: All                       FIELD NAME: Fields
  ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   Read access using VA FileMan 
 GENERAL DESCRIPTION:   All fields in the WORLD TIMEZONES file (#1.71) are
 available for read access using VA FileMan.  
  STATUS: Active
KEYWORDS: TIMEZONE
  DATE ACTIVATED: DEC 07, 2022

NUMBER: 7388                            IA #: 7388
  DATE CREATED: DEC 09, 2022
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWU
  NAME: API for ORPARAM OVER DATELINE   ID: ORWU
 GENERAL DESCRIPTION:   PX*1*233 needs access to OVERDL^ORWU 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ORPARAM OVER DATELINE
COMPONENT/ENTRY POINT: OVERDL
 COMPONENT DESCRIPTION:   This will get the value of the ORPARAM OVER DATELINE
 parameter.  
VARIABLES: OVERDL                       TYPE: Output
 VARIABLES DESCRIPTION:   This will return the value of the ORPARAM OVER
 DATELINE parameter.  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
  DATE ACTIVATED: DEC 14, 2022

NUMBER: 7389                            IA #: 7389
  DATE CREATED: DEC 14, 2022
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORIMO
  NAME: ORIMO IMOOD                     ID: ORIMO
 GENERAL DESCRIPTION:   This call will return a 1 if the CPRS order is a Clinic
 Order (formerly referred to as Inpatient Medication Orders for Outpatient),
 IMO for short.  
  STATUS: Active
KEYWORDS: ORIMO
KEYWORDS: IMOOD
COMPONENT/ENTRY POINT: IMOOD
VARIABLES: ORDER #                      TYPE: Input
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   Returns a 1 for a Clinic order.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: DEC 15, 2022

NUMBER: 7390                            IA #: 7390
  DATE CREATED: DEC 15, 2022            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMFLST
  NAME: PXRMFLST                        ID: PXRMFLST
 GENERAL DESCRIPTION:   The routine ORVIMM makes a call to DEF^PXRMFLST to look
 for information on the Findings multiple from the Clinical Reminders file. The
 called routine was released to the field in a patch prior to Patch OR*3.0*561.
 This is an "after the fact" clean-up of missing ICR documentation in routines. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DEF
VARIABLES: DEFIEN                       TYPE: Input
VARIABLES: ORITEMS                      TYPE: Output
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: DEC 29, 2022

NUMBER: 7391                            IA #: 7391
  DATE CREATED: DEC 15, 2022            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMLDR
  NAME: PXRMLDR                         ID: PXRMLDR
 GENERAL DESCRIPTION:   The routine ORVIMM makes a call to DEF^PXRMLDR to look
 for information on the Findings multiple from the Clinical Reminders file. The
 called routine was released to the field in a patch prior to Patch OR*3.0*561.
 This is an "after the fact" clean-up of missing ICR documentation in routines. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DEF
VARIABLES: RIEN                         TYPE: Input
VARIABLES: DEFARR                       TYPE: Output
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JAN 03, 2023

NUMBER: 7392                            IA #: 7392
  DATE CREATED: DEC 16, 2022
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWPS
  NAME: ORWPS COVER                     ID: ORWPS
 GENERAL DESCRIPTION:   Returns a list of medications for a patient to display
 on the CPRS Health Summary, Essential Medication List for Review report.  
  STATUS: Active
KEYWORDS: ORWPS
KEYWORDS: COVER
COMPONENT/ENTRY POINT: COVER
VARIABLES: DFN                          TYPE: Input
VARIABLES: RPC                          TYPE: Output
 VARIABLES DESCRIPTION:   Returns the medications list in an array.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
  DATE ACTIVATED: DEC 20, 2022

NUMBER: 7393                            IA #: 7393
  DATE CREATED: DEC 18, 2022            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXAPI
  NAME: PXAPI                           ID: PXAPI
 GENERAL DESCRIPTION:   The routine ORWPCE5 makes a call to GMPARAMS^PXAPI to
 look for information on Measurement parameters from the EDUCATION TOPICS FILE
 or the EXAM FILE or the HEALTH FACTORS FILE. The called routine was released
 to the field in a patch prior to Patch OR*3.0*561. This is an "after the fact"
 clean-up of missing ICR documentation in routines.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GMPARAMS
VARIABLES: FILENUM                      TYPE: Input
VARIABLES: IEN                          TYPE: Input
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JAN 10, 2023

NUMBER: 7394                            IA #: 7394
  DATE CREATED: DEC 18, 2022            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMTAXI
  NAME: PXRMTAXI                        ID: PXRMTAXI
 GENERAL DESCRIPTION:   The routine ORWPCE5 makes a call to TAXLIST^PXRMTAXI to
 look for information on all the defined Taxonomies from the REMINDER TAXONOMY
 FILE.  The called routine was released to the field in a patch prior to Patch 
 OR*3.0*561. This is an "after the fact" clean-up of missing ICR documentation
 in routines.  
  
 The routine ORWPCE5 makes a call to CODELIST^PXRMTAXI to look for information
 on the codes related to a Taxonomy from the REMINDER TAXONOMY FILE. The called
 routine was released to the field in a patch prior to Patch OR*3.0*561. This
 is an "after the fact" clean-up of missing ICR documentation in routines       
               
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: TAXLIST
VARIABLES: TAXLIST                      TYPE: Output
COMPONENT/ENTRY POINT: CODELIST
VARIABLES: IEN                          TYPE: Input
VARIABLES: CODES                        TYPE: Output
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JAN 10, 2023

NUMBER: 7395                            IA #: 7395
  DATE CREATED: DEC 18, 2022            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMDTAX
  NAME: PXRMDTAX                        ID: PXRMDTAX
 GENERAL DESCRIPTION:   The routine ORWPCE5 makes a call to GMPARAMS^PXRMDTAX
 to look for information on the codes related to a Taxonomy from the REMINDER
 TAXONOMY FILE. The called routine was released to the field in a patch prior
 to Patch OR*3.0*561. This is an "after the fact" clean-up of missing ICR 
 documentation in routines.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GMPARAMS
VARIABLES: CODE                         TYPE: Input
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: DEC 29, 2022

NUMBER: 7396                            IA #: 7396
  DATE CREATED: DEC 19, 2022            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMTXCS
  NAME: PXRMTXCS                        ID: PXRMTXCS
 GENERAL DESCRIPTION:   The routine ORWPCE5 makes a call to UIDSEARCH^PXRMTXCS
 to look for information on all Taxonomies that have a coding system code pair
 marked as UID and return all the active, on the encounter date, UID codes from 
 that coding system that are marked as UID in those Taxonomies from the 
 REMINDER TAXONOMY FILE. The called routine was released to the field in a 
 patch prior to Patch OR*3.0*561. This is an "after the fact" clean-up of 
 missing ICR documentation in routines.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: UIDSEARCH
VARIABLES: CODE                         TYPE: Input
VARIABLES: ENCDATE                      TYPE: Input
VARIABLES: CODELIST                     TYPE: Output
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: JAN 10, 2023

NUMBER: 7397                            IA #: 7397
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19
  DATE CREATED: DEC 20, 2022            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: CPRS UPDATE MENU TEXT
  ID: DIC(19
GLOBAL REFERENCE: DIC(19,D0,0)
FIELD NUMBER: 1                         FIELD NAME: MENU TEXT
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   The Computerized Patient Record System (CPRS)
 application needs to be able to update the server version number information
 during patch post installation. There are times when CPRS prefers to not
 export the entire menu option but rather to only update the version number.  
  
 The purpose of this ICR is to grant CPRS the ability to use FileMan to update
 that version number. 
  STATUS: Active
KEYWORDS: MENU TEXT
KEYWORDS: VERSION
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: DEC 20, 2022

NUMBER: 7398                            IA #: 7398
  DATE CREATED: DEC 22, 2022
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXVUTIL
  NAME: PXVUTIL                         ID: PXVUTIL
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ARTAPI
 COMPONENT DESCRIPTION:   Returns a '1' if the immunization contraindication is
 allergy related, otherwise it returns a '0'.  
VARIABLES: CONTRA                       TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to IMM CONTRAINDICATION REASONS file
 (#920.4).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   OR*3*405 needs access to ARTAPI^PXVUTIL to see if an
 immunization contraindication is allergy related.  
  DATE ACTIVATED: DEC 23, 2022

NUMBER: 7399                            IA #: 7399
  DATE CREATED: DEC 22, 2022
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORWPCE2
  NAME: ORWPCE2                         ID: ORWPCE2
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EXCLUDED
 COMPONENT DESCRIPTION:   Returns list of excluded PCE data elements.  
VARIABLES: ORY                          TYPE: Output
 VARIABLES DESCRIPTION:   Rteurns list of excluded elements in the format:
 ORY(#)="internal instance^internal value".  
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   The Visit location (pointer to the HOSPITAL LOCATION
 file (#44)).  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   PCE file to look at. Should be a number from 1-5. 1:
 IMMUNIZATIONS; 2: SKIN TESTS; 3: PATIENT ED; 4: HEALTH FACTORS; 5: EXAM 
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   PX*1*217 needs access to EXCLUDED^ORWPCE2 to see if
 certain immunizations should be excluded based off the ORWPCE EXCLUDE
 IMMUNIZATIONS parameter.  
  DATE ACTIVATED: DEC 27, 2022

NUMBER: 7400                            IA #: 7400
  DATE CREATED: JAN 03, 2023
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7400
  STATUS: Pending

NUMBER: 7401                            IA #: 7401
  DATE CREATED: JAN 03, 2023
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: RAERR
  NAME: DBS RAERR FUNCTION              ID: RAERR
 GENERAL DESCRIPTION:   ISI IMAGING provides a Report Entry function within the
 ISI Rad radiology workstation client application.  When the case of interest
 is selected, Fileman calls are used for fetching exam and report details for
 display in the application; the $$DBS^RAERR function is used to check for
 errors after the calls are made.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ISI RAD
KEYWORDS: ISI*1.1*110 DFN
KEYWORDS: VistARad COTS
COMPONENT/ENTRY POINT: $$DBS
SUBSCRIBING PACKAGE: ISI IMAGING
  DATE ACTIVATED: JAN 10, 2023

NUMBER: 7402                            IA #: 7402
  DATE CREATED: JAN 05, 2023            CUSTODIAL PACKAGE: ISI IMAGING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGJLS2B
  NAME: EXAM LOCK CHECK                 ID: MAGJLS2B
 GENERAL DESCRIPTION:   The ISI Rad Client application is a plug-in replacement
 for VistA Imaging's VistARad client. ISI Rad uses all of the existing VistA
 Imaging Server software (RPC calls, routines, files, etc.) in the same way as 
 VistARad. In some cases, to support new features that VistARad does not have,
 new ISI Server software uses many of the same subroutines and files in the
 same manner as VistARad; session initialization; fetching exam info and image
 info; exam locking; exam list data management; etc.  
  
 ISI Rad ISI*1.1*110 provides a Report Entry Function within the ISI Rad
 radiology workstation client application. When the case of interest is
 selected, the program must determine the current lock status of the exam to
 allow or deny access to report updating by the current user.  
  
 Revision: Added 11/16/23: This ICR was originally set-up for ISI IMAGING to be
 a subscriber to an IMAGING Routine. MAGJ is now excluded from the IMAGING
 package and has been added to the ISI IMAGING package as an additional prefix.
 As a result ISI IMAGING is both the Custodian and Subscriber. Though this ICR
 is no longer needed, the decision was made to leave the ICR in place for
 historical purposes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ISI Rad
KEYWORDS: VistARad
KEYWORDS: VistARad COTS
KEYWORDS: ISI*1.1*110
COMPONENT/ENTRY POINT: CHKLOCK
 COMPONENT DESCRIPTION:   This function returns the initials of the locking
 user, and a truth flag that indicates if the locking user is the same as the
 logon user.  
VARIABLES: RARPT                        TYPE: Input
 VARIABLES DESCRIPTION:   Radiology Report file pointer 
VARIABLES: DAYCASE                      TYPE: Input
 VARIABLES DESCRIPTION:   Radiology accession number 
VARIABLES: XX                           TYPE: Output
 VARIABLES DESCRIPTION:   User Initials ^ Truth flag 
SUBSCRIBING PACKAGE: ISI IMAGING
  DATE ACTIVATED: MAR 03, 2023

NUMBER: 7403                            IA #: 7403
  DATE CREATED: JAN 05, 2023            CUSTODIAL PACKAGE: ISI IMAGING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGJLS3
  NAME: SAVE EXAM LIST DATA             ID: MAGJLS3
 GENERAL DESCRIPTION:   The ISI Rad Client application is a plug-in replacement
 for VistA Imaging's VistARad client. ISI Rad uses all of the existing VistA
 Imaging Server software (RPC calls, routines, files, etc.) in the same way as 
 VistARad. In some cases, to support new features that VistARad does not have,
 new ISI Server software uses many of the same subroutines and files in the
 same manner as VistARad; session initialization; fetching exam info and image
 info; exam locking, exam list data management; etc.  
  
 ISI Rad ISI*1.1*110 provides exams list functions within the ISI Rad radiology
 workstation client application--Favorites exams, and a dynamic query exams
 list. When compiling these lists, this subroutine call is used to save output
 data. 
  
 Revision: Added 11/16/23: This ICR was originally set-up for ISI IMAGING to be
 a subscriber to an IMAGING Routine. MAGJ is now excluded from the IMAGING
 package and has been added to the ISI IMAGING package as an additional prefix.
 As a result ISI IMAGING is both the Custodian and Subscriber. Though this ICR 
 is no longer needed, the decision was made to leave the ICR in place for 
 historical purposes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ISI Rad
KEYWORDS: VistARad
KEYWORDS: VistARad COTS
KEYWORDS: ISI*1.1*110
COMPONENT/ENTRY POINT: SVMAG2A
 COMPONENT DESCRIPTION:   This subroutine saves output for one exam in the
 standardized means for all exams lists.  
  
 Called in processing the pre-existing RPC, MAGJ RADACTIVEEXAMS, for new exam
 lists introduced by ISI Rad.  
VARIABLES: BKGPROC                      TYPE: Input
 VARIABLES DESCRIPTION:   T/F flag indicating List process is Background
 Compile 
VARIABLES: LSTREQ                       TYPE: Input
 VARIABLES DESCRIPTION:   Code indicating list type (e.g., U=Unread) 
VARIABLES: MAGRACNT                     TYPE: Input
 VARIABLES DESCRIPTION:   Holds item counter for storing values for each exam
 visited 
VARIABLES: MAGLST                       TYPE: Input
 VARIABLES DESCRIPTION:   Holds node name in scratch global under which compile
 data is stored 
VARIABLES: RADFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The DFN of the patient for the radiology exam record
 being processed by the calling program.  
VARIABLES: RADTI                        TYPE: Input
 VARIABLES DESCRIPTION:   The inverse date/time for the radiology exam record
 being processed by the calling program.  
VARIABLES: RACNI                        TYPE: Input
 VARIABLES DESCRIPTION:   The specific exam record for the radiology exam
 record being processed by the calling program.  
VARIABLES: RAST                         TYPE: Input
 VARIABLES DESCRIPTION:   Radiology Status code IEN 
VARIABLES: REMONLY                      TYPE: Input
 VARIABLES DESCRIPTION:   T/F flag indicating List process is for Remote vs.
 Local exams 
VARIABLES: STATCHK                      TYPE: Input
 VARIABLES DESCRIPTION:   variable killed to disable checking exam status 
VARIABLES: MAGJACTIVE                   TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,"MAGJACTIVE") - Standard VistARad Exams List
 subsystem compile raw result set (Imaging & Radiology data) stored under this
 node.  
VARIABLES: PIPE3
 VARIABLES DESCRIPTION:   optional parameter; not used by ISI program 
SUBSCRIBING PACKAGE: ISI IMAGING
  DATE ACTIVATED: MAR 08, 2023

NUMBER: 7404                            IA #: 7404
  DATE CREATED: JAN 05, 2023            CUSTODIAL PACKAGE: ISI IMAGING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGJUTL1
  NAME: GET EXAM DATA                   ID: MAGJUTL1
 GENERAL DESCRIPTION:   The ISI Rad CLIENT application is a plug-in replacement
 for VistA Imaging's VistARad client. ISI Rad uses all of the existing VistA
 Imaging SERVER software (RPC calls, routines, files, etc.) in the same way as 
 VistARad. In some cases, to support new features that VistARad does not have,
 new ISI SERVER software uses many of the same subroutines and files in the
 same manner as VistARad: session initialization; fetching Exam info and Image
 info; Exam Locking; Exam List data management; etc. 
  
 ISI Rad ISI*1.1*110 provides features including Report Entry, Notes entry, and
 Exams List functions within the ISI Rad radiology workstation client 
 application. Whenever an exam of interest is being processed for any of these
 functions, this subroutine is called to retrieve all data required to perform
 said function.  
  
 Revision: Added 11/16/23: This ICR was originally set-up for ISI IMAGING to be
 a subscriber to an IMAGING Routine. MAGJ is now excluded from the IMAGING
 package and has been added to the ISI IMAGING package as an additional prefix.
 As a result ISI IMAGING is both the Custodian and Subscriber. Though this ICR 
 is no longer needed, the decision was made to leave the ICR in place for 
 historical purposes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ISI Rad
KEYWORDS: VistARad
KEYWORDS: VistARad COTS
KEYWORDS: ISI*1.1*110
COMPONENT/ENTRY POINT: GETEXAM2
 COMPONENT DESCRIPTION:   This subroutine returns exam details for one exam; it
 is used to retrieve data required to perform all functions within VistARad for
 exams lists and exam update operations.  
  
 Called in processing the pre-existing RPC, MAGJ RADACTIVEEXAMS, for new exam
 lists introduced by ISI Rad. Also called in processing the new RPCs: ISIJ
 FAVORITE, ISIJ LOCK REPORT, ISIJ NOTES, and ISIJ REPORT ENTER 
VARIABLES: RADFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The DFN of the patient for the radiology exam record
 being processed by the calling program 
VARIABLES: RADTI                        TYPE: Input
 VARIABLES DESCRIPTION:   The inverse date/time for the radiology exam record
 being processed by the calling program 
VARIABLES: RACNI                        TYPE: Input
 VARIABLES DESCRIPTION:   The specific exam record for the radiology exam
 record being processed by the calling program.  
VARIABLES: MAGRET                       TYPE: Input
 VARIABLES DESCRIPTION:   T/F indicating exam was/not found 
VARIABLES: MAGRAEX                      TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP($J,"MAGRAEX") - Standard VistARad result set
 (Imaging & Radiology data) stored under this node.  
SUBSCRIBING PACKAGE: ISI IMAGING
  DATE ACTIVATED: MAR 07, 2023

NUMBER: 7405                            IA #: 7405
  DATE CREATED: JAN 05, 2023            CUSTODIAL PACKAGE: ISI IMAGING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGJUTL2
  NAME: IMAGE INFORMATION               ID: MAGJUTL2
 GENERAL DESCRIPTION:   The ISI Rad CLIENT application is a plug-in replacement
 for VistA Imaging's VistARad client. ISI Rad uses all of the existing VistA
 Imaging SERVER software (RPC calls, routines, files, etc.) in the same way as 
 VistARad. In some cases, to support new features that VistARad does not have,
 new ISI SERVER software uses many of the same subroutines and files in the
 same manner as VistARad: session initialization; fetching Exam info and Image
 info; Exam Locking; Exam List data management; etc. 
  
 ISI Rad ISI*1.1*110 provides a Favorites exams list function within the ISI
 Rad radiology workstation client application. When compiling the lists for
 output, this subroutine is called to fetch # of images for the exam, and the
 Date/Time of Image capture for displaying in the list.  
  
 Revision: Added 11/16/23: This ICR was originally set-up for ISI IMAGING to be
 a subscriber to an IMAGING Routine. MAGJ is now excluded from the IMAGING
 package and has been added to the ISI IMAGING package as an additional prefix.
 As a result ISI IMAGING is both the Custodian and Subscriber. Though this ICR 
 is no longer needed, the decision was made to leave the ICR in place for 
 historical purposes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ISI Rad
KEYWORDS: VistARad
KEYWORDS: VistARad COTS
KEYWORDS: ISI*1.1*110
COMPONENT/ENTRY POINT: IMGINFO
 COMPONENT DESCRIPTION:   This subroutine returns selected image information
 for an exam.  
  
 Called in processing the new RPC: ISIJ FAVORITE 
VARIABLES: RARPT                        TYPE: Input
 VARIABLES DESCRIPTION:   Radiology Report file pointer for the radiology exam
 being processed by the calling program 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   # of images ^ Online status ^ Image Date/Time 
SUBSCRIBING PACKAGE: ISI IMAGING
  DATE ACTIVATED: MAR 03, 2023

NUMBER: 7406                            IA #: 7406
  DATE CREATED: JAN 05, 2023            CUSTODIAL PACKAGE: ISI IMAGING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGJUTL3
  NAME: INITIALIZE MAGJOB ARRAY         ID: MAGJUTL3
 GENERAL DESCRIPTION:   The ISI Rad CLIENT application is a plug-in replacement
 for VistA Imaging's VistARad client. ISI Rad uses all of the existing VistA
 Imaging SERVER software (RPC calls, routines, files, etc.) in the same way as 
 VistARad. In some cases, to support new features that VistARad does not have,
 new ISI SERVER software uses many of the same subroutines and files in the
 same manner as VistARad: session initialization; fetching Exam info and Image
 info; Exam Locking; Exam List data management; etc.  
  
 ISI Rad ISI*1.1*110 provides a feature for Notes entry and display within the
 ISI Rad radiology workstation client application; the Notes display is 
 implemented as a subroutine call within the Display radiology Report or 
 Requisition functions. These functions may be called by other Imaging 
 applications (i.e., not VistARad nor ISI Rad). If a non-ISI Rad application
 calls Display radiology Report or Requisition, the program must initialize the
 MAGJOB array.  
  
 Revision: Added 11/16/23: This ICR was originally set-up for ISI IMAGING to be
 a subscriber to an IMAGING Routine. MAGJ is now excluded from the IMAGING
 package and has been added to the ISI IMAGING package as an additional prefix.
 As a result ISI IMAGING is both the Custodian and Subscriber. Though this ICR 
 is no longer needed, the decision was made to leave the ICR in place for 
 historical purposes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ISI Rad
KEYWORDS: VistARad
KEYWORDS: VistARad COTS
KEYWORDS: ISI*1.1*110
COMPONENT/ENTRY POINT: MAGJOBNC
 COMPONENT DESCRIPTION:   This subroutine is called to initialize the MAGJOB
 control array.  
VARIABLES: MAGJOB                       TYPE: Output
 VARIABLES DESCRIPTION:   Array of control values global to VistARad (and ISI
 Rad) 
SUBSCRIBING PACKAGE: ISI IMAGING
  DATE ACTIVATED: MAR 07, 2023

NUMBER: 7407                            IA #: 7407
  DATE CREATED: JAN 05, 2023            CUSTODIAL PACKAGE: ISI IMAGING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MAGJUTL6
  NAME: GET PRINTSET STATUS             ID: MAGJUTL6
 GENERAL DESCRIPTION:   The ISI Rad CLIENT application is a plug-in replacement
 for VistA Imaging's VistARad client. ISI Rad uses all of the existing VistA
 Imaging SERVER software (RPC calls, routines, files, etc.) in the same way as 
 VistARad. In some cases, to support new features that VistARad does not have,
 new ISI SERVER software uses many of the same subroutines and files in the
 same manner as VistARad: session initialization; fetching Exam info and Image
 info; Exam Locking; Exam List data management; etc.  
  
  
 ISI IMAGING ISI*1.1*110 provides a Report Entry function within the ISI Rad
 radiology workstation client application. When the case of interest is 
 selected, the program must retrieve the correct Accession number to use for
 the exam, resolved per the PRINTSET status, with the associated accession
 numbers per the PRINTSET status, so that the report entry session processes
 correctly for all related exams.  
  
 Revision: Added 11/16/23: This ICR was originally set-up for ISI IMAGING to be
 a subscriber to an IMAGING Routine. MAGJ is now excluded from the IMAGING
 package and has been added to the ISI IMAGING package as an additional prefix.
 As a result ISI IMAGING is both the Custodian and Subscriber. Though this ICR 
 is no longer needed, the decision was made to leave the ICR in place for 
 historical purposes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ISI Rad
KEYWORDS: VistARad
KEYWORDS: VistARad COTS
KEYWORDS: ISI*1.1*110
COMPONENT/ENTRY POINT: $$DAYCASE
 COMPONENT DESCRIPTION:   Returns the Accession # (or list of Accession #s if
 PRINTSET) for an input Exam ID.  
VARIABLES: RADFN                        TYPE: Input
 VARIABLES DESCRIPTION:   The DFN of the patient for the radiology exam record
 being processed by the calling program 
VARIABLES: RADTI                        TYPE: Input
 VARIABLES DESCRIPTION:   The inverse date/time for the radiology exam record
 being processed by the calling program 
VARIABLES: RACNI                        TYPE: Input
 VARIABLES DESCRIPTION:   The specific exam record for the radiology exam
 record being processed by the calling program 
VARIABLES: DAYCASE                      TYPE: Output
 VARIABLES DESCRIPTION:   Accession # (or list of Accession #'s if PRINTSET) 
COMPONENT/ENTRY POINT: $$DAYCASE3
 COMPONENT DESCRIPTION:   Returns the Accession # (or list of Accession #'s if
 PRINTSET) for an input Exam ID.  
  
 Called in processing the new RPC: ISIJ REPORT ENTER 
VARIABLES: DAYCASE                      TYPE: Input
 VARIABLES DESCRIPTION:   Radiology accession number 
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   Case ID string (RADFN_U_RADTI_U_RACNI) 
SUBSCRIBING PACKAGE: ISI IMAGING
  DATE ACTIVATED: MAR 07, 2023

NUMBER: 7408                            IA #: 7408
  FILE NUMBER: 2006.63                  GLOBAL ROOT: MAG(2006.63
  DATE CREATED: JAN 05, 2023            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: MAG RAD LIST DATA ELEMENTS (#2006.63)
  ID: MAG(2006.63
GLOBAL REFERENCE: MAG(2006.63,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Field Name for the DATA ELEMENTS 
FIELD NUMBER: 1                         FIELD NAME: ABBREVIATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Abbreviation for the Data Elements 
FIELD NUMBER: 2                         FIELD NAME: COLUMN HEADER
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Name for the Column Header 
FIELD NUMBER: 7                         FIELD NAME: COLUMN TYPE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This indicates to the VistARad Client that the data for
 this column requires special handling for either the Sort or other defined
 needs. No answer, by default, says treat column data as free-text data.
 Defined needs are: Indicate Sort requirements (for Date & Numeric values) 
 Indicate Day/Case Number (used for key in Client App).  
 GENERAL DESCRIPTION:   The ISI Rad CLIENT application is a plug-in replacement
 for VistA Imaging's VistARad client.  ISI Rad uses all of the existing VistA 
 Imaging SERVER software (RPC calls, routines, files, etc.) in the same way as
 VistARad. In some cases, to support new features that VistARad does not have,
 new ISI SERVER software uses many of the same subroutines and files in the
 same manner as VistARad: session initialization; fetching Exam info and Image
 info; Exam Locking; Exam List data management; etc. 
  
 VistA Imaging gives permission to ISI Rad to read and update file MAG RAD LIST
 DATA ELEMENTS (#2006.63), which contains data necessary for the exam list
 subsystem used by VistARad. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ISI Rad
KEYWORDS: VistARad
KEYWORDS: VistARad COTS
KEYWORDS: ISI*1.1*110
SUBSCRIBING PACKAGE: ISI IMAGING
 SUBSCRIBING DETAILS:   VistA Imaging gives permission to ISI Rad to read and
 update file MAG RAD LIST DATA ELEMENTS (#2006.63), which contains data
 necessary for the exam list subsystem used by VistARad.  
  DATE ACTIVATED: MAR 07, 2023

NUMBER: 7409                            IA #: 7409
  FILE NUMBER: 2006.631                 GLOBAL ROOT: MAG(2006.631
  DATE CREATED: JAN 05, 2023            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: MAG RAD LISTS DEFINITION (#2006.631)
  ID: MAG(2006.631
GLOBAL REFERENCE: MAG(2006.631,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Name of List as defined by the user (i.e. Favorites) 
FIELD NUMBER: .03                       FIELD NAME: LIST TYPE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This determines what subset of the exams to display,
 based on the Exam Status value. Choices are: 
  
 U  -- UNREAD Exams only; Exam Status Category= E(xamined) R  -- RECENT Exams;
 Status Categories D(ictated) & T(ranscribed) A  -- ALL Active Exams;
 Categories E, D, & T P  -- PENDING Exams; Category= W(aiting for Exam) N  --
 Newly-Interpreted; NO Category H  -- History List; NO Category I  -- Indexed
 list; NO Category 
  
 List Types N, H and I are for internal use only, and are not available for
 defining reports.  
FIELD NUMBER: .06                       FIELD NAME: ENABLE LIST
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Until the List definition is Enabled, it will not be
 available for use from the VistARad Workstation; this allows you time to
 develop and/or modify list definitions without worrying about end-users
 accessing a fully-defined list. Also, you can retire a list that is no longer
 needed by deleting this field's answer.  
FIELD NUMBER: .07                       FIELD NAME: BUTTON LABEL
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   List name displayed on the GUI application 
GLOBAL REFERENCE: MAG(2006.631,D0,1,0)
FIELD NUMBER: 1                         FIELD NAME: COLUMNS
  LOCATION: 1;0                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Specify output columns here 
GLOBAL REFERENCE: MAG(2006.631,D0,ISI)
FIELD NUMBER: 200                       FIELD NAME: TAG
  LOCATION: ISI;1                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Enter the TAG to be used as the entry point for the
 compile routine. This is only used for List Type "I" exam lists, and is
 required. Code at this routine/tag performs the compile for the list being
 created.  
FIELD NUMBER: 201                       FIELD NAME: ROUTINE
  LOCATION: ISI;2                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Enter the ROUTINE where the tag/entry-point is found.
 This is only used for List Type "I" exam lists. and is required. Code at this 
 routine/tab performs the compile for the list being created.  
 GENERAL DESCRIPTION:   The ISI Rad CLIENT application is a plug-in replacement
 for VistA Imaging's VistARad client. ISI Rad uses all of the existing VistA
 Imaging SERVER software (RPC calls, routines, files, etc.) in the same way as 
 VistARad. In some cases, to support new features that VistARad does not have,
 new ISI SERVER software uses many of the same subroutines and files in the
 same manner as VistARad: session initialization; fetching Exam info and Image
 info; Exam Locking; Exam List data management; etc.  
                         
 VistA Imaging gives permission to ISI Imaging to read and update file MAG RAD
 LISTS DEFINITION (#2006.631), which contains Exams List specification data for
 the exam list subsystem used by VistARad.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ISI Rad
KEYWORDS: VistARad
KEYWORDS: VistARad COTS
KEYWORDS: ISI*1.1*110
SUBSCRIBING PACKAGE: ISI IMAGING
 SUBSCRIBING DETAILS:   ISI Rad ISI*1.1*110  provides some new Exams Lists
 functionality.  Whenever an exam list is being processed, this file is
 referenced to retrieve all data required to make proper use of the
 pre-existing reporting subsystem within the VistARad (and ISI Rad)
 application.  
  DATE ACTIVATED: MAR 07, 2023

NUMBER: 7410                            IA #: 7410
  FILE NUMBER: 2006.69                  GLOBAL ROOT: MAG(2006.69
  DATE CREATED: JAN 05, 2023            CUSTODIAL PACKAGE: IMAGING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: MAG VISTARAD SITE PARAMETERS (#2006.69)
  ID: MAG(2006.69
GLOBAL REFERENCE: MAG(2006.69,D0,1)
FIELD NUMBER: 20                        FIELD NAME: UNREAD LIST PRIORITY SEQ
  LOCATION: 1;E1,245                    ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The Unread lists show a column, PRIORITY, that is
 typically used as a sort item for the list. Four values are possible (from the
 Radiology Exam order, file 75.1).  This field allows the site to define the
 preferred sort ordering for these 4 values.  The default order is: Stat,
 Urgent, Pre-op, Routine To achieve this ordering, the value for this field
 would be specified: S,U,P,R Any sequence of these 4 letters may be defined,
 and then will be used by the list program.  
GLOBAL REFERENCE: MAG(2006.69,D0,ISI)
FIELD NUMBER: 101                       FIELD NAME: ENABLE ASSIGN EXAMS FEATURE?
  LOCATION: ISI;1                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This feature allows an exam to be assigned to a specific
 Radiologist, or Radiology Tech, for interpretation or follow-up.  This feature
 works only if ISI's "Rad Tech Tool" has been installed and configured at the
 site.  
FIELD NUMBER: 102
  FIELD NAME: ENABLE DYNAMIC QUERY FEATURE?
  LOCATION: ISI;2                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The Dynamic Query feature, and all supporting program
 logic and functionality, shall be enabled only if this field has a value =
 "Y".  
FIELD NUMBER: 103                       FIELD NAME: DYNAMIC QUERY RECORD LIMIT
  LOCATION: ISI;3                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   To prevent dynamic query compiles processing very large
 result sets, this value may be defined to abort a query that exceeds the
 number specified here.  
FIELD NUMBER: 104                       FIELD NAME: ENABLE EXAM LIST STATISTICS?
  LOCATION: ISI;4                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   If enabled, this feature counts the frequency of use of
 each of the exam lists.  The data is aggregated weekly by site.  These
 statistics may be viewed by using the PRINT EXAM LIST STATISTICS menu option.  
FIELD NUMBER: 105                       FIELD NAME: ENABLE MANAGER REV-2
  LOCATION: ISI;5                       ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   The Revision-2 modifications remove two obsolete exam
 lists from the Manager's top tab row; in their place the Assigned-UNREAD and 
 Assigned-WAITING tab entries are inserted ("Level-1").  "Level-2" also removes
 the Background compile of RECENT exams from server-side processing, so the
 option "MAGJ SCHED RECENT LIST COMPILE" no longer needs to be defined in
 Taskman.  The obsolete exam lists are "Recent", and "All Active Exams"; these
 are still accessible on the Custom tab, if desired.  
FIELD NUMBER: 106                       FIELD NAME: DYNAMIC QUERY DAYS LIMIT
  LOCATION: ISI;106                     ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Enter a value to limit how many days back the dynamic
 query compile may go.  This will prevent the user from entering a Study From
 Date value earlier than "Today" minus the value you enter here.  
FIELD NUMBER: 107
  FIELD NAME: READY FOR INTERP IMAGING TYPE
  LOCATION: ISI;7                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   In the typical Radiology workflow, dictation/report entry
 occurs for exams after images have been acquired. In some circumstances it is 
 desirable to initiate a report entry session PRIOR to image acquisition. 
 Ultrasound workflow is the notable example for this.  To support this, a 
 reserved EXAMINATION STATUS value must be defined, having a specific VISTARAD
 CATEGORY value, "Ready for Interpretation",  that is defined to enable this
 alternate workflow. This Examination Status value must have an ORDER that
 sequences it between the WAITING FOR EXAM status and the EXAMINED status.
 Enter the IMAGING TYPE value for which you want to enable this feature. This
 must align with the IMAGING TYPE for which the Examination Status value is
 being defined.  
FIELD NUMBER: 108
  FIELD NAME: READY FOR INTERP TRIGGER VALUE
  LOCATION: ISI;8                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   A reserved value defined in the CAMERA/EQUIP/RM file
 should be defined for triggering the Exam Status to advance from the WAITING
 FOR EXAM status to the status defined having the VISTARAD CATEGORY value,
 "Ready for Interpretation".  Enter the reserved CAMERA/EQUIP/RM value here.  
FIELD NUMBER: 109                       FIELD NAME: ENABLE NOTES FEATURE?
  LOCATION: ISI;9                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This feature allows any ISI Rad user to enter and/or view
 notes related to the exam.  These notes are displayed within the ISI Rad
 application only, appended to either the exam Report or Requisition.  
FIELD NUMBER: 110
  FIELD NAME: ENABLE ISIRad DICTATION OPTION
  LOCATION: ISI;10                      ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This option allows the user to select the "ISI Rad"
 Dictation setting, which provides the user a way to manually enter Radiology
 reports in a ISI Rad data entry form. The reports are stored using the
 Radiology HL7 interface. This option works only if the requisite Radiology
 package programs and HL7 configurations have been installed and configured at
 the site.  
 GENERAL DESCRIPTION:   The ISI Rad CLIENT application is a plug-in replacement
 for VistA Imaging's VistARad client. ISI Rad uses all of the existing VistA
 Imaging SERVER software (RPC calls, routines, files, etc.) in the same way as 
 VistARad. In some cases, to support new features that VistARad does not have,
 new ISI SERVER software uses many of the same subroutines and files in the
 same manner as VistARad: session initialization; fetching Exam info and Image
 info; Exam Locking; Exam List data management; etc.  
                        
  
 VistA Imaging gives permission to ISI Imaging to read and update file MAG 
 VISTARAD SITE PARAMETERS (#2006.69), which contains control data for managing
 various logic switches in VistARad (e.g., enable/disable a feature).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ISI Rad
KEYWORDS: VistARad
KEYWORDS: VistARad COTS
KEYWORDS: ISI*1.1*110
SUBSCRIBING PACKAGE: ISI IMAGING
 SUBSCRIBING DETAILS:   VistA Imaging gives permission to ISI Rad to read and
 update file MAG VISTARAD SITE PARAMETERS (#2006.69), which contains control
 data for managing various logic switches in VistARad (e.g., enable/disable a 
 feature).  
  
 ISI Rad ISI*1.1*110 provides some new features, some of which are optional. 
 The application needs to make use of pre-existing mechanisms used by VistARad
 for managing various logic switches in ISI Rad (e.g., enable/disable
 features). 
  DATE ACTIVATED: MAR 07, 2023

NUMBER: 7411                            IA #: 7411
  FILE NUMBER: 440.4                    GLOBAL ROOT: PRC(440.4,
  DATE CREATED: JAN 10, 2023            CUSTODIAL PACKAGE: IFCAP
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MANUFACTURER File Access
  ID: PRC(440.4,
GLOBAL REFERENCE: PRC(440.4,D0,0)
FIELD NUMBER: 1                         FIELD NAME: INACTIVE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Determine if MANUFACTURER is active or inactive 
 GENERAL DESCRIPTION:   The ADVANCED PROSTHETICS ACQUISITION TOOL (APAT)
 requests FileMan read access to the MANUFACTURER (#440.4) file to determine if
 a manufacturer is active or inactive.  Navigation to the MANUFACTURER file
 will use ITEM MASTER (#441) field MANUFACTURER (#25) which points to file
 440.4.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
  DATE ACTIVATED: JAN 10, 2023

NUMBER: 7412                            IA #: 7412
  DATE CREATED: JAN 18, 2023            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: PSO VDEF RDS O13 OP PHARM PPAR VS
 GENERAL DESCRIPTION:   The PSO VDEF RDS O13 OP PHARM PPAR VS protocol is used
 to send HL7 messages to the Health Data Repository (HDR). See the Outpatient
 Pharmacy Technical Manual for message specifications.  
  
 This documents the protocols allowed to subscribe to this event. Supported HL7
 utilities may be used to read the attached message; the message itself and HL7
 application variables may not be altered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   VPR listener is VPR PSO VDEF EVENTS, added with
 VPR*1*30.  
  DATE ACTIVATED: JAN 23, 2023

NUMBER: 7413                            IA #: 7413
  DATE CREATED: JAN 18, 2023            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: PSO VDEF RDS O13 OP PHARM PREF VS
 GENERAL DESCRIPTION:   The PSO VDEF RDS O13 OP PHARM PREF VS protocol is used
 to send HL7 messages to the Health Data Repository (HDR). See the Outpatient
 Pharmacy Technical Manual for message specifications.  
  
 This documents the protocols allowed to subscribe to this event. Supported HL7
 utilities may be used to read the attached message; the message itself and HL7
 application variables may not be altered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   VPR listener is VPR PSO VDEF EVENTS, added with
 VPR*1*30.  
  DATE ACTIVATED: JAN 23, 2023

NUMBER: 7414                            IA #: 7414
  FILE NUMBER: 18.12                    GLOBAL ROOT: XOB(18.12,D0
  DATE CREATED: JAN 20, 2023            CUSTODIAL PACKAGE: WEB SERVICES CLIENT
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: WEB SERVER File (#18.12) access
  ID: XOB(18.12,D0
GLOBAL REFERENCE: XOB(18.12,D0,0
FIELD NUMBER: .04                       FIELD NAME: SERVER
  LOCATION: 0;4                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: XOB(18.12,D0,3
FIELD NUMBER: 3.02                      FIELD NAME: SSL CONFIGURATION
  LOCATION: 3;2                         ACCESS: Direct Global R/W & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PPSN
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
 SUBSCRIBING DETAILS:   Pharmacy Data Management needs read/write access to the
 SERVER (#.04) field and the SSL CONFIGURATION (#3.02) field in the WEB SERVER
 (#18.12) file. PSS*1.0*258's and possibly future patch post-install routines
 will automatically update these fields for the PPSN web server so that sites
 do not need to update them manually.  
  DATE ACTIVATED: JAN 24, 2023

NUMBER: 7415                            IA #: 7415
  FILE NUMBER: 120.88                   GLOBAL ROOT: GMR(120.88
  DATE CREATED: JAN 25, 2023
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: REMOTE ALLERGY COMMENT FILE
  ID: GMR(120.88
GLOBAL REFERENCE: GMR(120.88,'PR',
 GLOBAL DESCRIPTION:   Cross ref by patient and reactant - Direct Global Read 
GLOBAL REFERENCE: GMR(120.88,D0,1
FIELD NUMBER: 1                         FIELD NAME: COMMENT
  ACCESS: Direct Global Read & R/W w/Fileman
 FIELD DESCRIPTION:   A comment entered during order check processing by a
 local user applied to an allergy entered at a remote location/facility.  
 GENERAL DESCRIPTION:   The REMOTE ALLERGY COMMENT file contains locally
 entered comments relating to allergies entered for a patient at a separate
 (remote) facility which OE/RR displays to providers. There will be a direct
 global read of ^GMR(120.88,'PR' to find the last comment, if one exists.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAY 31, 2023

NUMBER: 7416                            IA #: 7416
  FILE NUMBER: 8925.7                   GLOBAL ROOT: TIU(8925.7
  DATE CREATED: FEB 22, 2023
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: IA#7416
  ID: TIU(8925.7
GLOBAL REFERENCE: TIU(8925.7,D0,0)
FIELD NUMBER: .01                       FIELD NAME: TIU Document Number
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: Cosignature Date/Time
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: Actual Cosigner
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Virtual Patient Record (VPR) would like to create
 an action index on the TIU MULTIPLE SIGNATURE (#8925.7) file that would call a
 VPR API in routine VPREVNT when a signer in the file is updated. The FileMan
 utility CREIXN^DDMOD would be used in a post-init for patch VPR*1*31 to create
 the AVPR index instead of exporting the data dictionary. 
  
 In addition to retrieving additional signers, the fields listed here are 
 included in the index for purposes of triggering the action. No actual cross
 reference nodes are created.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AVPR
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: MAR 06, 2023

NUMBER: 7417                            IA #: 7417
  DATE CREATED: FEB 22, 2023
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRPC
  NAME: IMMUNIZATION HL7 CODE LOOKUP    ID: PXRPC
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: IMMSRC
 COMPONENT DESCRIPTION:   Returns the IMMUNIZATION INFO SOURCE (920.1) IEN for
 a given HL7 Code. If no entry was found for the given HL7 code, it will return
 0.  
VARIABLES: HL7                          TYPE: Input
 VARIABLES DESCRIPTION:   The HL7 code (e.g., "00" or "05").  
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 2/22/23.The IZ Gateway (IZG) project, as a part
 of VDIF, will be using IMMSRC^PXRPC to get the Immunization Info Source IEN
 for a given HL7 code. The IEN will be used when calling DATA2PCE to store the 
 immunization data that is sent by the State IISs (Immunization Information
 Systems) via the CDC's IZ Gateway to update the patient's EHR in VistA. This
 will enable VA healthcare providers to view the patient's immunizations that
 were administered at a non-VA facility. 
  DATE ACTIVATED: FEB 22, 2023

NUMBER: 7418                            IA #: 7418
  DATE CREATED: MAR 10, 2023            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: YTQ VERSRV
  REMOTE PROCEDURE: YTQ VERSRV
 GENERAL DESCRIPTION:   YTQ VERSRV ICR #7418 is used by WebVRAM to lookup the
 YS BROKER1 option to get the MENTAL HEALTH CR DLL VERSION on a particular
 VistA system.  
  
 The following is a capture of the YTQ VERSRV Remote Procedure definition: 
  
 NAME: YTQ VERSRV                        TAG: VERSRV 
   ROUTINE: YTQAPI7                      RETURN VALUE TYPE: ARRAY 
   AVAILABILITY: SUBSCRIPTION DESCRIPTION:   
  This procedure allows version checking by using the Option (19) menu 
  text.  
   
  Input: YSB as option name to be checked.  Output: [DATA] vs [ERROR] 
         2= mha3 version 
         3= CR dll version 
         4= mh dll version 
  STATUS: Active
KEYWORDS: MENTAL HEALTH VERSION
KEYWORDS: WebVRAM
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   If a WebVRAM user needs to access the MENTAL HEALTH DLL
 at a particular facility, WebVRAM calls YTQ VERSRV at the facility to
 determine which verision of MENTAL HEALTH should be opened for the user.  
  DATE ACTIVATED: MAR 16, 2023

NUMBER: 7419                            IA #: 7419
  FILE NUMBER: 4.4                      GLOBAL ROOT: XMB(4.4,
  DATE CREATED: MAR 22, 2023            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MAILMAN TIME ZONE FILE ACCESS
  ID: XMB(4.4,
GLOBAL REFERENCE: XMB(4.4,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TIME ZONE NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: XMB(4.4,'B'
 GLOBAL DESCRIPTION:   ^XMB(4.4,'B' 
    File 4.4 'B' cross reference  Used to look up by CODE 
 GENERAL DESCRIPTION:   
  The Advanced Prosthetics Acquisition Tool (APAT) requests access to 
  the MAILMAN TIME ZONE (#4.4) FILE to read CODE and TIME ZONE NAME for the 
  purpose of documenting the accurate timing of local events.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIME ZONE
KEYWORDS: APAT
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   The ADVANCED PROSTHETICS ACQUISITION TOOL (APAT) would
 like to use the "B" cross-reference to look up the CODE.  Field TIME ZONE NAME
 is to be displayed as the associated Time Zone to provide accurate timing of 
 local events.  
SUBSCRIBING PACKAGE: ABOVE PAR
 SUBSCRIBING DETAILS:   Added 7/8/25 effective with DSIY*1.5*6 patch for the
 purpose of documenting the accurate timing of local events.  
  DATE ACTIVATED: MAR 29, 2023

NUMBER: 7420                            IA #: 7420
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: APR 07, 2023            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: EPCS BROKER MENU UPDATE
  ID: VA(200
GLOBAL REFERENCE: VA(200,D0,203,D1
FIELD NUMBER: 203                       FIELD NAME: SECONDARY MENU OPTIONS
  LOCATION: 0;1                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   
  This is a onetime agreement via patch PSO*7.0*545.  
  
  This is for PSO*7*545 only, and will expire when it is released.  
    
  Post install processing looks for users that have a secondary menu option 
  of XU EPCS EDIT DATA (legacy ePCS GUI broker menu) and changes it to 
  PSO EPCS GUI CONTEXT (ePCS GUI 2.0 broker menu).  
  
  Outpatient Pharmacy requests read access to the NEW PERSON (#200) file to 
  search for the option XU EPCS EDIT DATA in the SECONDARY MENU OPTIONS 
  (#200.03) multiple using $$LKOPT^XPDMENU. If the secondary menu XU EPCS 
  EDIT DATA is found in the user's secondary menus, a call is made to 
  $$ACCESS^XQCHK to determine the user's status. If the user is active, 
  then we request write access to change the XU EPCS EDIT DATA secondary 
  menu to PSO EPCS GUI CONTEXT using FileMan API FILE^DIE. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: EPCS
KEYWORDS: XU EPCS EDIT DATA
KEYWORDS: PSO EPCS GUI CONTEXT
KEYWORDS: DEA
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: APR 18, 2023

NUMBER: 7421                            IA #: 7421
  DATE CREATED: APR 10, 2023            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGPROSAD
  NAME: DGPROSAD                        ID: DGPROSAD
 GENERAL DESCRIPTION:   The Master Patient Index (MPI) team has created this
 Application Programming Interface (API) which will allow the creation of a new 
 patient record in the PATIENT (#2) file for a known Integration Control Number
 (ICN) or Department of Defense (DoD) Electronic Data Interchange Personal
 Identifier (EDIPI) combination.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: IFC
KEYWORDS: INTERFACILITY CONSULTS
KEYWORDS: PROSTHETICS
KEYWORDS: CERNER
KEYWORDS: PATIENT
KEYWORDS: DGPROSAD
KEYWORDS: ADD PATIENT
KEYWORDS: DFN
COMPONENT/ENTRY POINT: $$ADD(SRCID,SITE)
 COMPONENT DESCRIPTION:   To add a new record the PATIENT (#2) file.  
  
 Arguments:   SRCID - Fully qualified Patient Identification 
              SITE  - VistA Station Number 
VARIABLES: SRCID                        TYPE: Input
 VARIABLES DESCRIPTION:   String value that denotes the fully qualified
 identification value that uniquely identifies the Patient on the Master
 Patient Index (MPI) system.  (Required) 
  
 For ICN: 
   <FullICN>~USVHA~NI~200M                           For EDIPI: 
   <EDIPI>~USDOD~NI~200DOD 
VARIABLES: SITE                         TYPE: Input
 VARIABLES DESCRIPTION:   String value that denotes the VistA Station Number
 that the patient should be created on.              (Optional - Default is the
 current VistA Site) 
VARIABLES: RET                          TYPE: Output
 VARIABLES DESCRIPTION:   
  1^ICN^Station Number^DFN - if successful -1^<Error Message> - if unsuccessful 
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Effective with patch GMRC*3.0*189, when an
 Inter-Facility Consult (IFC) is received at a VistA from CERNER, the patient's
 demographic information is extracted from the Patient Identification (PID)
 segment in the Health Level Seven (HL7) message to determine if the patient is
 known in the PATIENT (#2) file. If the patient is unknown, then the MPI API
 identified by this Integration Agreement (IA) will be called to create the
 patient at the VistA. The IFC will then be re-sent by the Veterans Data 
 Integration and Federation (VDIF) at a later time allowing the IFC to be
 processed/recorded successfully at the site.  
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   Added 6/17/25, effective with patch RMPR*3*217, when a
 Prosthetics order is received at a converted VistA from CERNER, the patient's
 demographic information is extracted from the Patient Identification (PID)
 segment in the Health Level Seven (HL7) message to determine if the patient is
 known in the PATIENT (#2) file. If the patient is unknown, then the MPI API 
 identified by this Integration Agreement (IA) is called to create the patient
 at the converted VistA.  
  DATE ACTIVATED: APR 12, 2023

NUMBER: 7422                            IA #: 7422
  FILE NUMBER: 1                        GLOBAL ROOT: DIC(
  DATE CREATED: APR 12, 2023            CUSTODIAL PACKAGE: 1
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FILE NUMBER FROM FILE NAME
  ID: DIC(
GLOBAL REFERENCE: DIC('B')
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   There is no supported FileMan API to determine the file
 number from the file name. This ICR allows the use the FileMan API $$FIND1^DIC
 to determine the file number.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FILE NUMBER
KEYWORDS: FILE NAME
KEYWORDS: FILE OF FILES
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: APR 12, 2023

NUMBER: 7423                            IA #: 7423
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: APR 13, 2023            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Add NPE user to NEW PERSON (#200) file
  ID: VA(200,
GLOBAL REFERENCE: VA(200,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: LAYGO
 FIELD DESCRIPTION:   The call $$ADD^VDIUSER will add a new user to file 200 as
 specified here unless the user already exists.  
FIELD NUMBER: 2                         FIELD NAME: ACCESS CODE
  LOCATION: 0;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 11                        FIELD NAME: VERIFY CODE
  LOCATION: .1;2                        ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The verify code needs to be defined before the user can
 log in, even if the user signs in with an STS token.  
FIELD NUMBER: 7.2                       FIELD NAME: VERIFY CODE never expires
  LOCATION: 0;8                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Since this is a non-person entity (NPE) and login is
 always via STS token, this field is set to "Yes".  
FIELD NUMBER: 205.1                     FIELD NAME: SECID
  LOCATION: 205;1                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   The SECID is set to the value appropriate to the
 application and environment type (development, test, SQA, pre-production, or
 production) appropriate to the environment.  
FIELD NUMBER: 205.2                     FIELD NAME: SUBJECT ORGANIZATION
  LOCATION: 205;2                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Set to Department of Veterans Affairs.  
FIELD NUMBER: 205.3                     FIELD NAME: SUBJECT ORGANIZATION ID
  LOCATION: 205;3                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Set to the OID (in URN format) of Department of Veteraans
 Affairs.  
FIELD NUMBER: 205.4                     FIELD NAME: UNIQUE USER ID
  LOCATION: 205;4                       ACCESS: Write w/Fileman
FIELD NUMBER: 205.5                     FIELD NAME: ADUPN
  LOCATION: 205;5                       ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   Set to the ADUPN (VA email address) of the NPE user).  
FIELD NUMBER: 9.5                       FIELD NAME: USER CLASS
  LOCATION: USC3;0                      ACCESS: LAYGO
 FIELD DESCRIPTION:   The value NON-PERSON is added to the USER CLASS multiple
 if it is not already present.  
 GENERAL DESCRIPTION:   This ICR allows VDIF to create new non-person entity
 (NPE) entries in the NEW PERSON file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: NPE
KEYWORDS: USER
KEYWORDS: NEW PERSON
KEYWORDS: CREATE
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
  DATE ACTIVATED: APR 24, 2023

NUMBER: 7424                            IA #: 7424
  DATE CREATED: MAY 02, 2023
  CUSTODIAL PACKAGE: ELECTRONIC HEALTH MODERNIZATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: EHMHL7
  NAME: HL7 MESSAGE REPOSITORY (EHRM HL7 Message #1609)
  ID: EHMHL7
 GENERAL DESCRIPTION:   Effective with patch EHM*1*10, a repository (EHRM HL7
 Message file (#1609)) exists to store HL7 messages that can be used to
 research production issues.  The repository is intended to store only 
 Inter-Facility Consult (IFC) and Patient Record Flags (PRF) HL7 messages 
 exchanged between non-converted VistA sites and Cerner Millennium.  This 
 ensures that the size of the repository is small relative to the total number
 of HL7 messages on any individual VistA.  
  
 In addition to the repository, EHM*1*10 creates Application Programming 
 Interfaces (API) callable by subscribing packages to populate the repository. 
 The patch also supplies options to inquire into the repository and to purge
 records.  
  
 Effective with patch GMRC*3*189, when an IFC is initiated by or received on a
 non-converted VistA site, the order message and all follow-up messages are
 added to the HL7 Message Repository.  
  
 Effective with patch DG*5.3*1091, when a PRF is initiated by or received on a
 non-converted VistA site, the message is added to the HL7 Message Repository.  
  
 Note:  EHM*1*10, GMRC*3*189, DG*5.3*1091 and TIU*1*350 are combined in the IFC
 ORDER/ADDENDUM UPDATES 1.0 build released in IFC_ORDER_ADDENDUM_UPDATES.KID.  
  
 Effective with EHM*1*16, the repository also stores Prosthetics (PSAS) HL7 
 messages exchanged between non-converted VistA sites and Cerner Millennium.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SAVEHL7
 COMPONENT DESCRIPTION:   Usage: $$SAVEHL7(TYPE) 
  
 To add a new record to the EHRM HL7 Message file (#1609).  
  
 Arguments:      TYPE - HL7 message type ("IFC","PRF" or "PSAS") 
  
 The HL7 message is extracted from the standard HL7 array.  
  
 Returns: IEN in file #1609 if successful or 0^error message if not.  
  
 Example: $$SAVEHL7^EHMHL7("IFC") 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Specifies the type of HL7 message.  Valid values are
 "IFC","PRF" or "PSAS".  
COMPONENT/ENTRY POINT: SAVEHL7X
 COMPONENT DESCRIPTION:   Usage: $$SAVEHL7X(NODE,TYPE) 
        
 To add a new record to the EHRM HL7 Message file (#1609) 
  
 Arguments:      NODE - ^TMP node where the HL7 message is stored, i.e., 
 ^TMP(NODE,$J,i)=HL7 segment 
                 TYPE - HL7 message type ("IFC","PRF" or "PSAS") 
  
 Returns: IEN in file #1609 if successful or 0^error message if not.  
  
 Example: $$SAVEHL7X^EHMHL7("HLS","IFC") 
VARIABLES: NODE                         TYPE: Input
 VARIABLES DESCRIPTION:   Specifies the ^TMP node where the HL7 message is
 stored, i.e., ^TMP(NODE,$J,i)=HL7 segment.  
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Specifies the type of HL7 message "IFC","PRF" or
 "PSAS".  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   Patch GMRC*3*189 modifies 2 routines - GMRCIMSG and
 GMRCIUTL - to use the APIs provided by this ICR to record Inter-Facility
 Consult HL7 messages involving Cerner as placer or filler so that production
 questions and issues can be researched and resolved.  
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   Patch DG*5.3*1091 modifies 2 routines - DGPFHLR and
 DGPFHLS - to use the APIs provided by this ICR to record Patient Record Flag
 HL7 messages involving Cerner so that production questions and issues can be
 researched and resolved.  
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   Added 3/6/24, effective with patch RMPR*3*217 adds
 several routines, one of which - RMPRINF0 - uses the API provided by this ICR
 to record HL7 order and order-related messages received from or sent to
 Cerner.  
  DATE ACTIVATED: APR 23, 2025

NUMBER: 7425                            IA #: 7425
  DATE CREATED: MAY 05, 2023
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: GMRCIEHM
  NAME: ADDENDUM RETRACTION HL7 MESSAGING TO CERNER
  ID: GMRCIEHM
 GENERAL DESCRIPTION:   When an addendum belonging to an Inter-Facility Consult
 involving Cerner is deleted, HL7 notification of that event is not transmitted
 to Cerner.  Patch GMRC*3*189 creates a mechanism to correct this.  The patch
 provides an API that can be called which will produce the HL7 message and
 transmit it to Cerner.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: RETRACTD
 COMPONENT DESCRIPTION:   This API generates an HL7 message for an IFC
 indicating that an addendum has been retracted and transmits it to Cerner.  
VARIABLES: GMRCDA                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the REQUEST/CONSULTATION file (#123) 
VARIABLES: TIUDA                        TYPE: Input
 VARIABLES DESCRIPTION:   IEN in the TIU DOCUMENT file (#8925) of the deleted
 addendum.  
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Patch TIU*1*350 modifies 1 routine - TIURD2 - to call
 the API provided by GMRC*3*189 when an addendum is deleted that is linked to
 an IFC that was placed on Cerner and sent to a non-converted VistA site.  

NUMBER: 7426                            IA #: 7426
  DATE CREATED: MAY 05, 2023
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: GMRCIEVT
  NAME: API to determine if an IFC involves Cerner
  ID: GMRCIEVT
 GENERAL DESCRIPTION:   When an addendum belonging to an Inter-Facility Consult
 involving Cerner is deleted, HL7 notification of that event is not transmitted
 to Cerner.  Patch GMRC*3*189 creates a mechanism to correct this.  A GMRC
 function provides an API that can be called to determine if a consult is an
 IFC involving Cerner.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: CNVTD
 COMPONENT DESCRIPTION:   Returns 1 if the IFC is for a converted site and 0
 otherwise.  
VARIABLES: GMRCDA                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the REQUEST/CONSULTATION file (#123) 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   Patch TIU*1*350 modifies 1 routine - TIURD2 - to call
 the API supported by this ICR when an addendum is deleted to determine if the
 IFC involved is linked to an IFC that was placed on Cerner and sent to a
 non-converted VistA site.  

NUMBER: 7427                            IA #: 7427
  DATE CREATED: MAY 16, 2023            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMRPCG
  NAME: PXRMRPCG                        ID: PXRMRPCG
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call the GETFIND^PXRMRPCG routine returning Reminder Dialog entry data.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GETFIND
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAY 17, 2023

NUMBER: 7428                            IA #: 7428
  DATE CREATED: JUN 07, 2023            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOPRKA
  NAME: PSOPRKA                         ID: PSOPRKA
 GENERAL DESCRIPTION:   ORDER ENTRY/RESULTS REPORTING (OE/RR) is allowed to
 utilize the UNPARK^PSOPRKA api in order to complete the unparking of a
 prescription functionality introduced with CPRSv32B and the following patch of 
 PSO*7*712 which will make it available for activation.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: UNPARK
COMPONENT/ENTRY POINT: UNPARK
 COMPONENT DESCRIPTION:   This component allows a Parked prescription to be
 Unparked and available for dispense.  
VARIABLES: PSODA                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the Prescription ien in file #52.  
VARIABLES: PSODFN                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the Patient DFN (file #200 ien).  
VARIABLES: ERRMSG                       TYPE: Output
 VARIABLES DESCRIPTION:   This is the variable array in which any error
 messages are returned relating to why the unpark failed, which includes all
 the existing fill/refill prescription failure messages. The array will contain
 a single error message which may take multiple array lines to express.  
VARIABLES: PSOARR                       TYPE: Output
 VARIABLES DESCRIPTION:   This array variable is used to return a message
 indicating the prescription was Unparked successfully and placed in a Suspense
 status until a specified date.  
VARIABLES: .
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: OCT 16, 2023

NUMBER: 7429                            IA #: 7429
  FILE NUMBER: 350.9                    DATE CREATED: JUL 13, 2023
  CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Insurance Import Enabled Switch
GLOBAL REFERENCE: IBE(350.9
FIELD NUMBER: 54.01                     FIELD NAME: INSURANCE IMPORT ENABLED
  LOCATION: 54;1                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   If this field is set to '1' (YES), the insurance policies
 will be imported related to the background execution of remote query. If this
 field is set to '0' (NO), the insurance policies will NOT be imported in the
 buffer.  
 GENERAL DESCRIPTION:   The Insurance Import Enabled switch lets the background
 job know whether the site is currently allowing insurance to be imported from
 other sites.  
  STATUS: Active
KEYWORDS: INSURANCE IMPORT
KEYWORDS: INSURANCE
KEYWORDS: IMPORT
KEYWORDS: REMOTE INSURANCE QUERY
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   The Register Once process looks at Integrated Billing
 to determine if the insurance import process is enabled or not for the site. 
 If it is enabled, it calls a IB routine to import insurance. (See ICR 4288) 
SUBSCRIBING PACKAGE: NDBI
 SUBSCRIBING DETAILS:   The INSUR process associated with a CBOC moving from
 one parent to another looks at Integrated Billing to determine if the
 insurance import process is enabled or not for the destination site.  If it is
 enabled, it calls a IB routine to import insurance. (See ICR 7473).  
  DATE ACTIVATED: JUL 17, 2023

NUMBER: 7430                            IA #: 7430
  FILE NUMBER: 8989.3                   GLOBAL ROOT: XTV(8989.3
  DATE CREATED: JUL 25, 2023            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: LIFETIME OF A VERIFY CODE
  ID: XTV(8989.3
GLOBAL REFERENCE: XTV(8989.3,D0,
FIELD NUMBER: 214                       FIELD NAME: LIFETIME OF VERIFY CODE
  LOCATION: XUS;15                      ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the number of days that a VERIFY code remains
 valid. After this time the user must choose a new VERIFY code.  
 GLOBAL DESCRIPTION:   This file holds the site parameters for this
 installation of the Kernel. It will have only one entry -- the domain name of
 the installation site.  
GLOBAL REFERENCE: VA(200,D0,.1,
FIELD NUMBER: 11.2
  FIELD NAME: DATE VERIFY CODE LAST CHANGED
  LOCATION: .1;1                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field is triggered by a change in the VERIFY CODE. 
 It is used to determine when the USER must be notified to change their code.  
 GLOBAL DESCRIPTION:   This file contains data on employees, users,
 practitioners, etc.  who were previously in Files 3,6,16 and others.  
 GENERAL DESCRIPTION:   The WebVRAM team would like FileMan read access to the
 LIFETIME OF VERIFY CODE (#214) field of the KERNEL SITE PARAMETERS (#8989.3)
 file to be used in conjunction with the DATE VERIFY CODE LAST CHANGED (#11.2)
 field of the NEW PERSON (#200) file to determine the correct date for when a
 WebVRAM user's VERIFY CODE is set to expire at their home VistA account.  
  
 A new RPC will be released in WEBG*3.0*14 to implement this functionality.  
  STATUS: Active
KEYWORDS: WebVRAM
KEYWORDS: VERIFY CODE
KEYWORDS: WEBG*3*14
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
  DATE ACTIVATED: AUG 10, 2023

NUMBER: 7431                            IA #: 7431
  DATE CREATED: AUG 08, 2023
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORQ12
  NAME: GET AN ORDER STATUS             ID: ORQ12
 GENERAL DESCRIPTION:   This ICR allows Clinical Reminders to retrieve an order
 status name.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GETSTAT
KEYWORDS: ORQ12
COMPONENT/ENTRY POINT: GETSTAT
 COMPONENT DESCRIPTION:   This API accept an Order IEN from file 100. It return
 the order status name.  
VARIABLES: ITEM                         TYPE: Input
 VARIABLES DESCRIPTION:   The order IEN from file 100.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Added 8/8/23, effective with PXRM*2.0*45, PXRMCEOC
 calls the API.  
  DATE ACTIVATED: AUG 10, 2023

NUMBER: 7432                            IA #: 7432
  DATE CREATED: AUG 08, 2023            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: WVAPI                        NAME: WVAPI routine
  ID: WVAPI
 GENERAL DESCRIPTION:   This ICR allows access to the entry points in routine
 WVAPI, effective with  PXRM*2.0*81 and WV*1.0*31   
  STATUS: Under Revision                DURATION: Till Otherwise Agreed
KEYWORDS: WVAPI
COMPONENT/ENTRY POINT: GETLABTM
 COMPONENT DESCRIPTION:   This API returns the value stores in parameter WV
 CERVICAL TERM LINKING.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   This variable contains the values store in the
 parameters WV CERVICAL TERM LINKING.  
COMPONENT/ENTRY POINT: GETRADTM
 COMPONENT DESCRIPTION:   This entry point returns the value stores in
 parameter WV BREAST IMAGE TERM LINKING.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   This variable contains the values store in parameter
 WV BREAST IMAGE TERM LINKING.  
COMPONENT/ENTRY POINT: GETCXUSR
 COMPONENT DESCRIPTION:   This API returns the values stored in parameter WV
 CERVICAL RESULT USERS.  
COMPONENT/ENTRY POINT: LAB
 COMPONENT DESCRIPTION:   This API returns information from file 790.1 for a
 Cervical Test.  
VARIABLES: ACCESSION                    TYPE: Input
 VARIABLES DESCRIPTION:   This variable is the lab accession number.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   This return array contains data stored in file 790.1
 for the passed in lab accession number.  
  
 RESULT("DAS")=IEN from file 790.1 RESULT("PRIMARY RESULT")=PDX, where PDX is
 the primary diagnosis stored in the entry from file 790.1 RESULT("SECONDARY
 RESULT")=SDX, where SDX is the secondary diagnosis stored in the entry from
 file 790.1 RESULT("DATE")=DATE, where DATE is from the DATE OF PROCEDURE field
 for the entry from file 790.1 in external format RESULT("STATUS")=STATUS,
 where STATUS is the entry in file 790.1, set to either CLOSED or OPEN.  
 RESULT("PROCEDURE DATE")=DATE, where DATE is from the DATE OF PROCEDURE field
 for the entry from file 790.1 in FileMan format.  RESULT("REPORT DATE")=DATE,
 where DATE is from the DATE RESULT RECEIVED field for the entry from file
 790.1 in FileMan format.  
COMPONENT/ENTRY POINT: TREATMENT
 COMPONENT DESCRIPTION:   This entry returns the data associated with each
 treatment plan stored in file 790 for the patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient DFN.  
VARIABLES: PLAN                         TYPE: Input
 VARIABLES DESCRIPTION:   This is the type of Treatment Plan to return to the
 calling application. Currently the following treatment plans are available: 
 BREAST CARE CERVICAL CARE 
VARIABLES: DIR                          TYPE: Input
 VARIABLES DESCRIPTION:   DIR is the direction to search. Set to 1 to start
 from the oldest treatment plan. Set to -1 to start from the most recent
 treatment plan.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   This is an array in the following format
 RESULTS(n,SUBSCRIPTS)=VALUE. Where n is an integer index. Subscripts is the
 name of the values that will be return. The possible subscripts are: DATE is
 the date the treatment plan entered into the patient record. The date is in
 FileMan format.  PROCEDURE is a free text field the value returned is the user
 entered next procedure to perform on the patient.  DURATION is a free text
 field the value returned is the user entered amount of time the patient should
 remain on the treatment plan.  FREQUENCY is a free text field the value
 returned is the user entered  how often the procedure should be repeated.  
 RETURN TO SCREENING is the date the user selected when the patient should 
 return to normal screening protocols. The value return is a FileMan date.  
 STATUS is the status of the treatment plan. The possible values are A for 
 Active, E for Entered in Error, and I for Inactive.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
  DATE ACTIVATED: AUG 10, 2023

NUMBER: 7433                            IA #: 7433
  DATE CREATED: AUG 08, 2023
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VSITCK1
  NAME: RETURN THE INSTITUTION ENTRY FOR AN LOCATION
  ID: VSITCK1
 GENERAL DESCRIPTION:   This API returns the corresponding file 4 IEN for the
 passed in location IEN from file 44.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: INS4LOC
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   LOC is the IEN from file 44.  
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
  DATE ACTIVATED: AUG 14, 2023

NUMBER: 7434                            IA #: 7434
  FILE NUMBER: 399.047                  DATE CREATED: AUG 15, 2023
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DELETE LANG NODES
GLOBAL REFERENCE: DD(399.047,.02,.009,1,0)
 GENERAL DESCRIPTION:   The following nodes will be deleted in patch
 IB*2.0*742.  
  
 VALUE K ^DD(399.047,.02,.009,1,0) 
  
 On a previous patch, IB*2.0*727, the VALUE field was given specific detailed
 executable help depending on the corresponding VALUE CODE.  Extraneous data
 nodes in DD's at some sites display a generic message that contradicts the
 executable help.  
  
 (ENTER FROM 1 TO 10 CHARACTERS OF FREE TEXT) 
  
 This patch contains a one-time cleanup in the post install routine IBY742PO.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ONE TIME
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: AUG 16, 2023

NUMBER: 7435                            IA #: 7435
  DATE CREATED: AUG 22, 2023
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXUTLVST
  NAME: Enhanced PCE Encounter Lookup   ID: PXUTLVST
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: FINDVISIT
KEYWORDS: PCE LOOKUP
COMPONENT/ENTRY POINT: FINDVISIT
 COMPONENT DESCRIPTION:   This API will search for existing visits that match
 based off certain criteria. It requires the Visit Date and Time (VDT) and
 Patient (DFN). The Hospital Location is required unless SVC="E". Institution
 (INS), Encounter Type (ENCTYPE), DSS ID (DSS), and Service Category (SVC) are
 optional. If they are passed as NULL, then they are not included in the visit
 matching.  If DSS and INS are passed as "NULL" then the match will be if these
 fields are NULL in the visit file entry.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient (#2) IEN 
VARIABLES: VDT                          TYPE: Input
 VARIABLES DESCRIPTION:   Visit Date and Time 
VARIABLES: HLOC                         TYPE: Input
 VARIABLES DESCRIPTION:   Hospital Location (#44) IEN 
VARIABLES: DSS                          TYPE: Input
 VARIABLES DESCRIPTION:   DSS ID (Clinic Stop (#40.7) IEN) 
VARIABLES: INS                          TYPE: Input
 VARIABLES DESCRIPTION:   Institution (#9999999.06) IEN 
VARIABLES: TYPE                         TYPE: Input
 VARIABLES DESCRIPTION:   Type (one of the set of codes from Visit (#9000010),
 Type (#.03)) 
VARIABLES: SVC                          TYPE: Input
 VARIABLES DESCRIPTION:   Service Category (one of the set of codes from Visit
 (#9000010), Service Category (#.07)) 
VARIABLES: ENCTYPE                      TYPE: Input
 VARIABLES DESCRIPTION:   Encounter Type (one of the set of codes from Visit
 (#9000010), Encounter Type (#15003)) 
VARIABLES: CSVC                         TYPE: Input
 VARIABLES DESCRIPTION:   DATA2PCE^PXAPI can change the input value of Service
 Category depending on if the patient was an inpatient or outpatient on the
 date of the encounter. If there is a possibility the input value of SVC may
 not be correct, pass CSVC=1 to determine if SVC could have been changed and 
 include the changed value in the matching.  
VARIABLES: VISITLIST                    TYPE: Output
 VARIABLES DESCRIPTION:   Passed by reference. The API will return the data in
 VISITLIST, in the following format: 
  
 VISITLIST(0)=-1 - If the API was called incorrectly.  
               0 - If no existing visits matched.  
               N - If it found matching Visits, it will return the number ('N')
 of Visits that were found.              
  
 VISITLIST(N)=Visit_IEN - 'N' is an integer starting at 1, and incremented by 1
 for additional Visits. 'Visit_IEN' is the Visit (#9000010) IEN that was
 matched.  
  
 VISITLIST(N,"A")="" - If this Visit was linked to an appointment, this node
 will be set to the NULL string. Otherwise it won't be defined.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
  DATE ACTIVATED: AUG 23, 2023

NUMBER: 7436                            IA #: 7436
  FILE NUMBER: 130                      GLOBAL ROOT: SRF(
  DATE CREATED: SEP 11, 2023            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: OE/RR SURGERY (#130) FILE ACCESS
  ID: SRF(
GLOBAL REFERENCE: SRF(D0,
FIELD NUMBER: 100                       FIELD NAME: ORDER NUMBER
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   THIS IS THE POINTER TO THE ORDER (#100) FILE.  
 GENERAL DESCRIPTION:   ORDER ENTRY/RESULTS REPORTING IS ACCESSING THE SURGERY
 (#130) FILE TO GATHER THE ORDER NUMBER (#100) FIELD IN ORDER TO DETERMINE THE
 ORDERING PROVIDER FOR NOTIFICATIONS DISPLAYED IN CPRS (COMPUTERIZED PATIENT
 RECORD SYSTEM).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SURGERY
KEYWORDS: CPRS
KEYWORDS: OERR
KEYWORDS: OE/RR
KEYWORDS: 130
KEYWORDS: SRF
KEYWORDS: SRF(
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: SEP 12, 2023

NUMBER: 7437                            IA #: 7437
  DATE CREATED: SEP 07, 2023
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: GMVBMI
  NAME: GMVBMI                          ID: GMVBMI
 GENERAL DESCRIPTION:   The CALBMI entry point provides a consistent and
 accurate calculation of the BMI value for an associated weight measurement.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: BMI
COMPONENT/ENTRY POINT: CALBMI(BMI,DEC)
 COMPONENT DESCRIPTION:   This entry point accepts a weight and returns the
 BMI.  
  
 Example: 
  >S DFN=229,BMI(1)=3100305.09,BMI(2)=178 
   
  >D CALBMI^GMVBMI(.BMI) W BMI 
  24.88 
  >
VARIABLES: BMI                          TYPE: Both
 VARIABLES DESCRIPTION:   BMI is used to pass in the weight information as an
 array by reference: 
   BMI(1) = Date/Time the weight was measured 
   BMI(2) = Weight value 
  
 The resulting BMI value will be returned in the BMI variable itself.  
VARIABLES: DEC                          TYPE: Input
 VARIABLES DESCRIPTION:   The number of decimal places to return in the
 calculated BMI value.  Optional, can be 0, 1, 2 (default), or 3.  
VARIABLES: DFN                          TYPE: Used
 VARIABLES DESCRIPTION:   Patient (#2) file pointer, required 
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
  DATE ACTIVATED: SEP 08, 2023

NUMBER: 7438                            IA #: 7438
  DATE CREATED: OCT 05, 2023
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: COMPACT ACT EOC EDIT ACCESS
 GENERAL DESCRIPTION:   The COMPACT Act EOC Edit [PX COMPACT ACT EOC EDIT]
 option and the COMPACT Act EOC Inpatient Retraction [PX COMPACT EOC IP
 RETRACTION] option will be added to the Supervisor ADT Menu [DG SUPERVISOR
 MENU]. REGISTRATION admissions will need the ability to edit the start and/or
 end date(s) of the Acute Suicidal Crisis from the new COMPACT Act EOC Edit
 option so that this date will be captured per VA policy. The new COMPACT Act
 EOC Inpatient Retraction option will allow an Episode of Care to be retracted 
 if a patient was entered in error or the wrong codes were used. These edits
 will be made based on supporting documentation from the Provider.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COMPACT
KEYWORDS: COMPACT ACT
KEYWORDS: EOC
KEYWORDS: ADT ADMISSIONS
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   ADT Admissions Clerk or HIM Specialist will need the
 ability to edit the start and/or end date(s) of the Acute Suicidal Crisis from
 the new COMPACT Act EOC Edit [PX COMPACT ACT EOC EDIT] option so that this
 date will be captured per VA policy. These edits will be made based on
 supporting documentation from the Provider. Access via Supervisor ADT Menu [DG 
 SUPERVISOR MENU].  
  
 ADT Admissions Clerk or HIM Specialist will need the ability to retract a 
 COMPACT Act Episode of Care (EOC) if the patient was entered in error or the
 wrong codes were used and the error was discovered after discharge.  The new
 COMPACT Act EOC Inpatient Retraction [PX COMPACT EOC IP RETRACTION] option
 allows this retraction. These edits will be made based on supporting
 documentation from the Provider. Access via Supervisor ADT Menu [DG SUPERVISOR
 MENU]. 
  DATE ACTIVATED: OCT 16, 2023

NUMBER: 7439                            IA #: 7439
  DATE CREATED: OCT 13, 2023
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORCSAVE1                     NAME: ORDER BUILD AND SAVE ORDER TEXT
  ID: ORCSAVE1
 GENERAL DESCRIPTION:   ORDTEXT^ORCSAVE1 - Build and save ORDER TEXT from
 ORDIALOG() into ORDER file.  
  
 ORTX^ORCSAVE1 - Build ORDER text from ORDIALOG() to ORTX() array. Does not
 update ORDER.  
  STATUS: Pending                       DURATION: Next Version
  GOOD ONLY FOR VERSION: PSJ*5.0*443
COMPONENT/ENTRY POINT: ORTX
 COMPONENT DESCRIPTION:   Build ORDER text from ORDIALOG() to ORTX() array.
 Does not update ORDER.  
VARIABLES: ORDER                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal file entry to ORDER file.  
VARIABLES: ORTX()                       TYPE: Output
 VARIABLES DESCRIPTION:   Array contining ORDER text.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS

NUMBER: 7440                            IA #: 7440
  DATE CREATED: OCT 13, 2023
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORCSAVE1
  NAME: ORDER BUILD AND SAVE ORDER TEXT
  ID: ORCSAVE1
 GENERAL DESCRIPTION:   ORTX^ORCSAVE1 - Build ORDER text from ORDIALOG() to
 ORTX() array. Does not update ORDER.  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: PSJ*5.0*443
COMPONENT/ENTRY POINT: ORTX
 COMPONENT DESCRIPTION:   Build ORDER text from ORDIALOG() to ORTX() array.
 Does not update ORDER.  
VARIABLES: ORDER                        TYPE: Input
 VARIABLES DESCRIPTION:   Internal file entry to ORDER file.  
VARIABLES: ORTX()                       TYPE: Output
 VARIABLES DESCRIPTION:   Array containing ORDER text.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   One time use, good for version PSJ*5.0*443 
  DATE ACTIVATED: OCT 13, 2023

NUMBER: 7441                            IA #: 7441
  FILE NUMBER: 100.02                   GLOBAL ROOT: ORD(100.02,
  DATE CREATED: OCT 17, 2023
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: NATURE OF ORDER FILE ACCESS
  ID: ORD(100.02,
 GENERAL DESCRIPTION:   
    INPATIENT MEDICATIONS requests one time permission to read the 
    NATURE OF ORDER FILE (#100.02). INPATIENT MEDICATIONS will look up 
    the nature of order in file #100.02 using the "B" cross reference 
    in order to set an order to 'CHANGED' based on the value in the cross 
    reference.  
  
    This is for one time use.  
  
      ^ORD(100.02,'B' 
         'B' cross reference - used to look up the file #100.02 entry 
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: PSJ*5.0*443
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: OCT 19, 2023

NUMBER: 7442                            IA #: 7442
  FILE NUMBER: 100.03                   GLOBAL ROOT: ORD(100.03,
  DATE CREATED: OCT 17, 2023
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ORDER REASON FILE ACCESS
  ID: ORD(100.03,
 GENERAL DESCRIPTION:   
    INPATIENT MEDICATIONS requests one time permission to read the  
    ORDER REASON FILE (#100.03). INPATIENT MEDICATIONS will look up 
    the nature of order in file #100.03 using the "B" cross reference 
    in order to set a discontinued order to 'Entered in Error' based on 
    the value in the cross reference.  
  
    This is for one time use.  
  
      ^ORD(100.03,'B' 
         'B' cross reference - used to look up the file #100.03 entry 
  STATUS: Active
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: OCT 19, 2023

NUMBER: 7443                            IA #: 7443
  DATE CREATED: OCT 19, 2023
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWPT GET FULL ICN
 GENERAL DESCRIPTION:   Following are the details of the ORWPT GET FULL ICN: 
  
 NAME: ORWPT GET FULL ICN                TAG: GETFICN 
   ROUTINE: ORWPT                        RETURN VALUE TYPE: SINGLE VALUE 
   APP PROXY ALLOWED: Yes DESCRIPTION:   
  RPC to return the ICN plus checksum for a given DFN.  INPUT PARAMETER: DFN    
                PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 DESCRIPTION:   
  The patient's internal entry number (IEN) in the PATIENT file (#2).  RETURN
 PARAMETER DESCRIPTION:   
  ORWRSLT is either the patient ICN or, in the event of an error, p1^p2 where
 p1=-1 and p2=the error text. Possible return values for error conditions are
 either -1^UNKNOWN ERROR or the error messages returned by $$GETICN^MPIF001.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ICN
KEYWORDS: IEN
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 10/26/23, effective with CDSP*1*0. Clinical
 Decision Support Platform is developing a Precision Oncology workflow to
 automatically ingest genetic test results into VistA and VistA Imaging. The
 workflow needs to identify patients based on demographic data present in test 
 results. This RPC is used to get the patient's full ICN in order to save the
 test results in VIX (VistA Imaging).  
  DATE ACTIVATED: OCT 26, 2023

NUMBER: 7444                            IA #: 7444
  DATE CREATED: OCT 26, 2023
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWDRA32 LOCTYPE
  REMOTE PROCEDURE: ORWDRA32 LOCTYPE    STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: CRMS VAHC
KEYWORDS: VAHC
KEYWORDS: NHIN
KEYWORDS: DAS
SUBSCRIBING PACKAGE: CUSTOMER RELATIONSHIP MANAGEMENT - SALESFORCE
 SUBSCRIBING DETAILS:   Added 10/26/23, effective with CRMS*1*1, the VA Health
 Connect (VAHC) application is a Salesforce product sharing the CRMS namespace. 
 
 The CRMS VAHC Remote Application includes the CRMS VAHC Option, which includes
 required RPCs. ORWDRA32 LOCTYPE is one of the Remote Procedures included in
 the CRMS VAHC Option. The Remote Application uses Data Access
 Services/National Health Information Network (DAS/NHIN) as the middleware to
 interface with VistA.  
  DATE ACTIVATED: NOV 14, 2023

NUMBER: 7445                            IA #: 7445
  DATE CREATED: NOV 03, 2023
  CUSTODIAL PACKAGE: MRSA INITIATIVE REPORTS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MMRSIPC
  NAME: MMRSIPC Routine                 ID: MMRSIPC
 GENERAL DESCRIPTION:   The MMRS package provides MRSA data reporting for use
 in IPEC reports. Bitscopic has developed a feature in the VEHB BITSCOPIC
 package, VEHB*1.4*1 patch, to extract the MRSA transmission numbers for use in 
 advanced alerting to improve the IPEC reporting process. This functionality
 will be used by staff at Palo Alto and Greater Los Angeles to improve MRSA
 transmission surveillance.  
  
 VEHB BITSCOPIC uses the following components: 
   CLEAN^MMRSIPC: The routine VEHBIPEC uses this component to kill the ^TMP 
 globals used by subsequent calls to ensure there is no data carryover from
 earlier report executions. 
   GETPARAM^MMRSIPC: The routine VEHBIPEC uses this component to load the MMRS
 site parameters into the ^TMP global.  
   PATDAYS^MMRSIPC:The routine VEHBIPEC uses this component to get patient days
 of care and store them in the ^TMP global.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VEHB
KEYWORDS: BITSCOPIC
COMPONENT/ENTRY POINT: CLEAN
COMPONENT/ENTRY POINT: GETPARAM
COMPONENT/ENTRY POINT: PATDAYS
SUBSCRIBING PACKAGE: BITSCOPIC
 SUBSCRIBING DETAILS:   Effective with VEHB*1.4*1 
  DATE ACTIVATED: NOV 20, 2023

NUMBER: 7446                            IA #: 7446
  DATE CREATED: NOV 03, 2023
  CUSTODIAL PACKAGE: MRSA INITIATIVE REPORTS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MMRSIPC2
  NAME: MMRSIPC2 Routine                ID: MMRSIPC2
 GENERAL DESCRIPTION:   The MMRS package provides MRSA data reporting for use
 in IPEC reports. Bitscopic has developed a feature in the VEHB BITSCOPIC
 package, VEHB*1.4*1 patch, to extract the MRSA transmission numbers for use in 
 advanced alerting to improve the IPEC reporting process. This functionality
 will be used by staff at Palo Alto and Greater Los Angeles to improve MRSA
 transmission surveillance.  
  
 VEHB BITSCOPIC uses the following component: 
   GETMOVE^MMRSIPC2: The routine VEHBIPEC uses this component to get patient
 movements and store them in the ^TMP global.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VEHB
KEYWORDS: BITSCOPIC
COMPONENT/ENTRY POINT: GETMOVE
 COMPONENT DESCRIPTION:   Collects ward movements for patients that were
 admitted or discharged in date range.  
SUBSCRIBING PACKAGE: BITSCOPIC
 SUBSCRIBING DETAILS:   Effective with VEHB*1.4*1 
  DATE ACTIVATED: NOV 20, 2023

NUMBER: 7447                            IA #: 7447
  DATE CREATED: NOV 03, 2023
  CUSTODIAL PACKAGE: MRSA INITIATIVE REPORTS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: MMRSIPC3
  NAME: MMRSIPC3 Routine                ID: MMRSIPC3
 GENERAL DESCRIPTION:   The MMRS package provides MRSA data reporting for use
 in IPEC reports. Bitscopic has developed a feature in the VEHB BITSCOPIC
 package, VEHB*1.4*1 patch, to extract the MRSA transmission numbers for use in 
 advanced alerting to improve the IPEC reporting process. This functionality
 will be used by staff at Palo Alto and Greater Los Angeles to improve MRSA
 transmission surveillance.  
  
 VEHB BITSCOPIC uses the following component: 
   GETLABS^MMRSIPC3: The routine VEHBIPEC uses this component to get the
 swabbing rates and MRSA history for the site and store them in the ^TMP
 global.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VEHB
KEYWORDS: BITSCOPIC
COMPONENT/ENTRY POINT: GETLABS
 COMPONENT DESCRIPTION:   Gets all lab data for the report.  
SUBSCRIBING PACKAGE: BITSCOPIC
 SUBSCRIBING DETAILS:   Effective with VEHB*1.4*1 
  DATE ACTIVATED: NOV 20, 2023

NUMBER: 7448                            IA #: 7448
  FILE NUMBER: 104                      GLOBAL ROOT: MMRS(104
  DATE CREATED: NOV 03, 2023
  CUSTODIAL PACKAGE: MRSA INITIATIVE REPORTS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MDRO SITE PARAMETERS FILE 
  ID: MMRS(104
GLOBAL REFERENCE: MMRS(104,D0,0
FIELD NUMBER: .01                       FIELD NAME: DIVISION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the division the parameters are
 defined for.  
 GENERAL DESCRIPTION:   The MMRS package provides MRSA data reporting for use
 in IPEC reports. Bitscopic has developed a feature in the VEHB BITSCOPIC
 package, VEHB*1.4*1 patch, to extract the MRSA transmission numbers for use in 
 advanced alerting to improve the IPEC reporting process. This functionality
 will be used by staff at Palo Alto and Greater Los Angeles to improve MRSA
 transmission surveillance.  
  
 VEHB BITSCOPIC needs acces to file 104, field .01 to support enhanced MRSA
 transmission surveillance reporting.  
                                         
 The routine VEHBIPEC uses FileMan to access site configuration data in order
 to identify which locations to associate the information accumulated via calls
 made to MMRS package routines.  
                                         
 Description for File 104 This file holds the set of parameters which modify
 the operation of the MRSA Program Tools to suit the needs of your site. For
 multi-divisional facilities, each division should have a separate entry in
 this file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VEHB
KEYWORDS: BITSCOPIC
SUBSCRIBING PACKAGE: BITSCOPIC
 SUBSCRIBING DETAILS:   Effective with VEHB*1.4*1 
  DATE ACTIVATED: NOV 20, 2023

NUMBER: 7449                            IA #: 7449
  FILE NUMBER: 104.3                    GLOBAL ROOT: MMRS(104.3
  DATE CREATED: NOV 03, 2023
  CUSTODIAL PACKAGE: MRSA INITIATIVE REPORTS
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MDRO WARD MAPPINGS FILE
  ID: MMRS(104.3
GLOBAL REFERENCE: MMRS(104.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the name of the Geographical Unit.  
FIELD NUMBER: 1                         FIELD NAME: DIVISION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the site that this mapping is defined for.  
FIELD NUMBER: 3                         FIELD NAME: TYPE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Enter the type of care provided to patients on this unit. 
 
FIELD NUMBER: 4                         FIELD NAME: IPEC UNIT ID
  LOCATION: 0;4                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the ID number that identifies this unit in IPEC. 
 This is only for Acute Care and CLC units reported to IPEC. Do NOT assign a
 Unit ID.  
GLOBAL REFERENCE: MMRS(104.3,D0,1,D1,0
FIELD NUMBER: .01                       FIELD NAME: WARD LOCATION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This is the ward that belongs to this geographical
 location. 
 GENERAL DESCRIPTION:   The MMRS package provides MRSA data reporting for use
 in IPEC reports. Bitscopic has developed a feature in the VEHB BITSCOPIC
 package, VEHB*1.4*1 patch, to extract the MRSA transmission numbers for use in 
 advanced alerting to improve the IPEC reporting process. This functionality
 will be used by staff at Palo Alto and Greater Los Angeles to improve MRSA
 transmission surveillance.  
  
 VEHB BITSCOPIC needs acces to file 104.3, fields .01,1,3 4 to support enhanced
 MRSA transmission surveillance reporting.  
  
 The routine VEHBIPEC uses FileMan to access site configuration data in order
 to identify which locations to associate the information accumulated via calls
 made to MMRS package routines.  
  
 Description for File 104.3 This file contains the Ward Mappings for the MDRO
 Program Tools software. Here you will create 'Geographical Units' which
 consist of one or more Ward Locations (from file 42). For purposes of the MDRO
 Program Tools software all Ward Locations belonging to the same Geographical
 unit are one - and any interward transfers between wards belonging to the same 
 geographical unit will be ignored.  
  STATUS: Active
KEYWORDS: VEHB
KEYWORDS: BITSCOPIC
SUBSCRIBING PACKAGE: BITSCOPIC
 SUBSCRIBING DETAILS:   Effective with VEHB*1.4*1 
  DATE ACTIVATED: NOV 20, 2023

NUMBER: 7450                            IA #: 7450
  DATE CREATED: JAN 05, 2024            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Controlled Subscription        TYPE: File
  NAME: READ ACCESS TO PXRMINDX
GLOBAL REFERENCE: PXRMINDX(
 GENERAL DESCRIPTION:   The purpose of this Integration Control Registration
 (ICR) is to grant read-only access to the Clinical Reminders Index.  
  STATUS: Pending
KEYWORDS: PXRMINDX
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING

NUMBER: 7451                            IA #: 7451
  DATE CREATED: JAN 09, 2024
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7451
  STATUS: Pending

NUMBER: 7452                            IA #: 7452
  DATE CREATED: JAN 17, 2024            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: SDEC APPADD                     REMOTE PROCEDURE: SDEC APPADD
 GENERAL DESCRIPTION:   The SwitchLane Periopt application is calling the code
 for the SDEC APPADD RPC in order to schedule dental appointments. 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 01, 2025
KEYWORDS: SDEC APPADD
KEYWORDS: PERIOPT
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   The SwitchLane Periopt application schedules dental
 appointment into VistA by calling the code for the SDEC APPADD RPC.  

NUMBER: 7453                            IA #: 7453
  DATE CREATED: JAN 17, 2024            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: SDEC APPDEL                     REMOTE PROCEDURE: SDEC APPDEL
  STATUS: Pending                       DURATION: Till Otherwise Agreed
  EXPIRATION DATE: JAN 01, 2025
KEYWORDS: PERIOPT
KEYWORDS: SDEC APPDEL

NUMBER: 7454                            IA #: 7454
  DATE CREATED: FEB 01, 2024
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXCOMPACTHL7
  NAME: ACCESS COMPACT ACT DATA FOR HL7 TRANSMISSION
  ID: PXCOMPACTHL7
 GENERAL DESCRIPTION:   Effective with PX*1.0*241 from the COMPACT OHI project,
 to share critical changes to the COMPACT ACT EPISODE OF CARE File #818 to VES
 via a new HL7 segment, ZCA, added to the existing IVM Background Job Full Z07
 HL7 message.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COMPACT ACT
KEYWORDS: HL7
COMPONENT/ENTRY POINT: ZCAAPI
 COMPONENT DESCRIPTION:   This tag returns a set of COMPACT ACT EOC ZCA HL7
 segments in array form for a given patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The patient DFN. This is the internal
 entry number of the patient record in the PATIENT File (#2).  
VARIABLES: FS                           TYPE: Input
 VARIABLES DESCRIPTION:   HL7 field delimiter for ZCA array 
VARIABLES: ZCA                          TYPE: Both
 VARIABLES DESCRIPTION:   Array returned by reference name. If returned array
 $D(array)=0, then there is no Episode of Care data on file for the patient DFN
 requested.  
SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH
  DATE ACTIVATED: OCT 10, 2024

NUMBER: 7455                            IA #: 7455
  DATE CREATED: MAR 25, 2024            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMCLEH
  NAME: CHANGE LOG/EDIT HISTORY APIs    ID: PXRMCLEH
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CHANGE LOG
KEYWORDS: EDIT HISTORY
KEYWORDS: APIs
COMPONENT/ENTRY POINT: CHANGELOG
 COMPONENT DESCRIPTION:   This API is used to add an entry to a CHANGE LOG/EDIT
 HISTORY. It automatically sets the EDIT DATE and EDIT BY fields. The text for
 the word-processing field: DESCRIPTION, is passed in the CLOGTEXT array.  
  
 Usage: 
  D CHANGELOG^PXRMCLEH(CLOGSFN,IEN,.CLOGTEXT) 
VARIABLES: CLOGSFN                      TYPE: Input
 VARIABLES DESCRIPTION:   The subfile number of the CHANGE LOG or EDIT HISTORY.
 It is obtained by calling $$GETCLOGSFN^PXRMCLEH.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the Internal Entry Number of the entry whose
 CHANGE LOG/EDIT HISTORY is being updated.  
VARIABLES: CLOGTEXT                     TYPE: Input
 VARIABLES DESCRIPTION:   This is an array, passed by reference, containing the
 EDIT COMMENTS. It has the format: 
  CLOGTEXT(1)=Line 1 
  CLOGTEXT(2)=Line 2 
  ...
  CLOGTEXT(N)=Line N 
COMPONENT/ENTRY POINT: GETCLOGSFN
 COMPONENT DESCRIPTION:   Given a file number, this extrinsic function returns
 the subfile number of the CHANGE LOG/EDIT HISTORY. If the file does not have a
 CHANGE LOG or EDIT HISTORY, it returns 0.  
  
 Usage: 
  S SFN=$$GETCLOGSFN^PXRMCLEH(FILENUMBER) 
VARIABLES: FILENUMBER                   TYPE: Input
 VARIABLES DESCRIPTION:   The file number of the file whose CHANGE LOG/EDIT
 HISTORY is being updated.  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   PCE STANDARDIZATION 2.0 creates the set of national
 EDUCATION TOPICS, EXAMS, and HEALTH FACTORS. It sets the CLASS to national and
 fills in missing PRINT NAMES, DESCRIPTIONS, and SPONSORS. It removes trailing 
 spaces from the .01 fields and resolves duplicates. When the updates are made,
 they need to be recorded in the CHANGE LOG. The APIs in PXRMCLEH provide a
 standard way to add records to the CHANGE LOG.  
  DATE ACTIVATED: MAR 17, 2025

NUMBER: 7456                            IA #: 7456
  DATE CREATED: MAR 25, 2024            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: WV1031L
  NAME: PATCH 31 POST-INSTALL           ID: WV1031L
 GENERAL DESCRIPTION:   This integration agreement allows the subscribing
 package to execute the post-install code for patch WV*1*31. This code is
 called when a site determines to move ahead with implementing the
 functionality contained in this patch.  
  STATUS: Active                        DURATION: Next Version
  GOOD ONLY FOR VERSION: 1.0
KEYWORDS: POST-INSTALL
KEYWORDS: WV*1*31
KEYWORDS: WV*1.0*31
COMPONENT/ENTRY POINT: POSTPATCH31
 COMPONENT DESCRIPTION:   Activates the patch functionality by initializing a
 series of parameters and linking a set of Clinical Reminder Terms to multiple
 entries in the WV PROCEDURE TYPE file (#790.2).  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Clinical Reminders will utilize this agreement
 exclusively for patch PXRM*2*81. When a site determines that it is ready to
 implement the functionality contained in this patch, the Clinical Applications 
 Coordinator (CAC) will execute option PATCH 81 POST LINK [PXRM POST PATCH 81],
 which calls the application programming interface (API) documented in this
 agreement.  
  DATE ACTIVATED: MAR 26, 2024

NUMBER: 7457                            IA #: 7457
  DATE CREATED: MAR 25, 2024            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMMSG
  NAME: REMINDER MANAGEMENT MAIL GROUP API
  ID: PXRMMSG                           STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: CLINICAL REMINDERS
KEYWORDS: MAIL GROUP
KEYWORDS: API
COMPONENT/ENTRY POINT: MAILGROUP
 COMPONENT DESCRIPTION:   This extrinsic function returns the REMINDER
 MANAGEMENT MAILGROUP from the CLINICAL REMINDERS PARAMETERS file, #800. If no
 mail group is defined it returns NULL.  
  
 Usage: 
  S MAILGROUP=$$MAILGROUP^PXRMMSG 
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   When PCE STANDARDIZATION 2.0 is installed, it will
 produce reports of health factors that were renamed and health factors that
 were repointed so sites will be able to update reports, dashboards, etc. These
 reports will be sent as MailMan messages. The reports need to be delivered to 
 members of the Reminder Management mail group. This API returns the site's
 Reminder Management mail group.  
  DATE ACTIVATED: AUG 14, 2024

NUMBER: 7458                            IA #: 7458
  DATE CREATED: MAR 25, 2024            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMSPED
  NAME: CLINICAL REMINDER SPONSOR IEN API
  ID: PXRMSPED                          STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: REMINDER SPONSOR
KEYWORDS: IEN
COMPONENT/ENTRY POINT: GETSPONSORIEN
 COMPONENT DESCRIPTION:   Return the internal entry number of a sponsor or its
 standard replacement.  If neither is found return 0. If the class of the
 sponsor is not equal to the class of the item whose sponsor is being set,
 return 0.  
  
 Usage: 
  S SPONSORIEN=$$GETSPONSORIEN^PXRMSPED(SPONSOR,CLASS) 
VARIABLES: SPONSOR                      TYPE: Input
 VARIABLES DESCRIPTION:   The sponsor name.  
VARIABLES: CLASS                        TYPE: Input
 VARIABLES DESCRIPTION:   The class (National, Local, or VISN) of the data
 element whose CLASS is being set. It must match the class of the passed
 sponsor. If they do not match, $$GETSPONSORIEN^PXRMSPED returns 0.  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   PCE STANDARDIZATION 2.0 creates the set of national
 EDUCATION TOPICS, EXAMS, and HEALTH FACTORS. When it is installed, it fills in
 missing SPONSORS. This requires the REMINDER SPONSOR internal entry number
 (IEN). This API returns the REMINDER SPONSOR IEN.  
  DATE ACTIVATED: AUG 14, 2024

NUMBER: 7459                            IA #: 7459
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: MAR 24, 2025            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Display Service Connected info on ACC Worklists
  ID: DPT(
GLOBAL REFERENCE: DPT(D0,.373,D1
FIELD NUMBER: .01                       FIELD NAME: SERVICE CONNECTED CONDITIONS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PERCENTAGE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This ICR allows the Automated Community Care (ACC)
 claims initiative to display Service Connected/Special Authority information
 for the purpose of routing claims to the proper worklist. The ACC worklists
 are implemented with IB*2.0*770.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ACC WORKLIST
SUBSCRIBING PACKAGE: INTEGRATED BILLING
  DATE ACTIVATED: MAR 24, 2025

NUMBER: 7460                            IA #: 7460
  DATE CREATED: MAR 26, 2024            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMP67NCUPD
  NAME: PCE NATIONAL CONTENT UPDATE     ID: PXRMP67NCUPD
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: REMINDER EXCHANGE
KEYWORDS: PCE
KEYWORDS: NATIONAL CONTENT
COMPONENT/ENTRY POINT: NATCONTENTCHECK
 COMPONENT DESCRIPTION:   National content check routine, verify that all the
 required national content updates have been installed.  
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Part of PCE STANDARDIZATION 2.0 is to ensure that key
 national content updates have been installed in all site accounts. National
 content updates are installed using Clinical Reminders Exchange functionality.
 To make this functionality available to PCE, so it can be used when PX*1.0*214
 is installed, the required parts of this functionality have been encapsulated
 in PXRMP67NCUPD.  
  
 Usage: 
  D NATCONTENTCHECK^PXRM67NCUPD 
  DATE ACTIVATED: MAY 28, 2024

NUMBER: 7461                            IA #: 7461
  DATE CREATED: APR 11, 2024
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: TIUCROBJ
  NAME: TIU OBJECT CREATION             ID: TIUCROBJ
 GENERAL DESCRIPTION:   This integration agreement enables subscribing packages
 to create both TIU objects as well as the TIU half of TIU/Health Summary
 objects (it DOES NOT create the Health Summary half of TIU/Health Summary
 objects).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU/HS OBJECT CREATION
COMPONENT/ENTRY POINT: $$CROBJ(NAME,ABBR,PNAME,METHOD,POWNER,NSTANDARD)
 COMPONENT DESCRIPTION:   This component will create a TIU object.  
VARIABLES: NAME                         TYPE: Input
 VARIABLES DESCRIPTION:   [Required] Object name.  
VARIABLES: ABBR                         TYPE: Input
 VARIABLES DESCRIPTION:   [Optional; defaults to ""] Object abbreviation.  
VARIABLES: PNAME                        TYPE: Input
 VARIABLES DESCRIPTION:   [Optional; defaults to value passed in NAME
 parameter] Object print name.  
VARIABLES: METHOD                       TYPE: Input
 VARIABLES DESCRIPTION:   [Optional; defaults to ""] Object method to execute.  
VARIABLES: POWNER                       TYPE: Input
 VARIABLES DESCRIPTION:   [Optional; defaults to ""] Object's personal owner.  
 Note: If a personal owner is not specified, the object's class owner is set to
 CLINICAL COORDINATOR.  
VARIABLES: NSTANDARD                    TYPE: Input
 VARIABLES DESCRIPTION:   [Optional; defaults to ""] Whether object is a
 national standard (NSTANDARD=1) or not.  
VARIABLES: $$CROBJ                      TYPE: Output
 VARIABLES DESCRIPTION:   Status of the call: 
  - 1 for successful creation 
  - "0^MESSAGE" for unsuccessful creation; MESSAGE 
    will contain the reason why the object was not 
    created 
COMPONENT/ENTRY POINT: $$CRTIUHS(TIUHSOBJ,TIUSTANDARD)
 COMPONENT DESCRIPTION:   This component creates the TIU half of a TIU/Health
 Summary object.  
VARIABLES: TIUHSOBJ                     TYPE: Input
 VARIABLES DESCRIPTION:   [Required] Name of the Health Summary object to link
 to.  
VARIABLES: TIUSTANDARD                  TYPE: Input
 VARIABLES DESCRIPTION:   [Optional; defaults to ""] Whether object is a
 national standard (TIUSTANDARD=1) or not.  
VARIABLES: $$CRTIUHS                    TYPE: Output
 VARIABLES DESCRIPTION:   Status of the call: 
  - 1 for successful creation 
  - "0^MESSAGE" for unsuccessful creation; MESSAGE 
    will contain the reason why the object was not 
    created 
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Clinical Reminders will use this agreement to create
 TIU object stubs for later conversion into TIU/Health Summary objects.  
  DATE ACTIVATED: APR 12, 2024

NUMBER: 7462                            IA #: 7462
  DATE CREATED: APR 15, 2024            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGCOMPACTELIG
  NAME: COMPACT ACT Administrative Eligibility
  ID: DGCOMPACTELIG
 GENERAL DESCRIPTION:   Patches DG*5.3*1104 and PX*1.0*240 will allow PCE and
 Scheduling to make decisions on when to prompt for COMPACT Act clinical
 information.  For this decision-making process, PCE or Scheduling needs to
 call the entry point ELIG^DGCOMPACTELIG to get and display the patient's
 COMPACT Act administrative eligibility status.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COMPACT ACT
COMPONENT/ENTRY POINT: ELIG
 COMPONENT DESCRIPTION:   Return patient COMPACT Act Administrative Eligibility 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Patient ID (required) 
VARIABLES: RTN                          TYPE: Input
 VARIABLES DESCRIPTION:   Original calling routine (not required) 
VARIABLES: ELIG                         TYPE: Output
 VARIABLES DESCRIPTION:   COMPACT Act Administrative Eligibility: 
   ELIGIBLE 
   NOT ELIGIBLE 
   UNDETERMINED 
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 4/15/24, effective with patches DG*5.3*1104 and
 PX*1.0*240 
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 4/15/24 to call ELIG component in support of
 COMPACT Act functionality in Scheduling.  
  DATE ACTIVATED: MAY 07, 2024

NUMBER: 7463                            IA #: 7463
  DATE CREATED: APR 15, 2024            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGCOMPACT
  NAME: COMPACT Act Treatment Related to Flag in PTF
  ID: DGCOMPACT
 GENERAL DESCRIPTION:   During certain COMPACT Act processing, such as creation
 or retraction of an Episode of Care (EOC), the EOC processing routines in PCE
 sometimes need to access the DGCOMPACT routine to set "Treatment Related To"
 flags in the PTF file (#45).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COMPACT ACT
COMPONENT/ENTRY POINT: SETPTFFLG
 COMPONENT DESCRIPTION:   API to set TRT FOR ACUTE SUICIDAL CRISIS flag (Field
 #79.33) in PTF 101 (File #45) 
     For YES: D SETPTFFLG^DGCOMPACT(DGENC,1) 
     For NO: D SETPTFFLG^DGCOMPACT(DGENC,0) 
     For NULL: D SETPTFFLG^DGCOMPACT(DGENC,"") 
VARIABLES: DGENC                        TYPE: Input
 VARIABLES DESCRIPTION:   Encounter ID (PTF IEN) 
VARIABLES: DGVAL                        TYPE: Input
 VARIABLES DESCRIPTION:   Value to set into flag 
COMPONENT/ENTRY POINT: SETPTFMVMT
 COMPONENT DESCRIPTION:   API to set TREATMENT FOR SUICIDAL CRISIS flag (Field
 #33) in PTF 501 (Sub-File #45.02) 
     For YES: D SETPTFMVMT^DGCOMPACT(DGENC,"Y",DGSEQ) 
     For NO: D SETPTFMVMT^DGCOMPACT(DGENC,"N",DGSEQ) 
     For NULL: D SETPTFMVMT^DGCOMPACT(DGENC,"",DGSEQ) 
VARIABLES: DGENC                        TYPE: Input
 VARIABLES DESCRIPTION:   Encounter ID (PTF IEN) 
VARIABLES: DGVAL                        TYPE: Input
 VARIABLES DESCRIPTION:   Value to set into flag 
VARIABLES: DGSEQ                        TYPE: Input
 VARIABLES DESCRIPTION:   Movement sequence (not required) 
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 4/15/24, effective with Patches DG*5.3*1104 and
 PX*1.0*240 
  DATE ACTIVATED: APR 23, 2024

NUMBER: 7464                            IA #: 7464
  DATE CREATED: APR 15, 2024
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXCOMPACTEOC
  NAME: COMPACT ACT Retract Episode of Care
  ID: PXCOMPACTEOC
 GENERAL DESCRIPTION:   Registration needs to be able to retract a COMPACT Act
 Episode of Care when a patient was entered with the wrong codes or the wrong
 patient was entered.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COMPACT ACT
COMPONENT/ENTRY POINT: RETRACT
 COMPONENT DESCRIPTION:   API to retract a COMPACT Act Episode of Care (EOC) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Patient ID (required) 
VARIABLES: PXENC                        TYPE: Input
 VARIABLES DESCRIPTION:   PTF internal ID (NOT required) - Used for inpatient
 processing 
SUBSCRIBING PACKAGE: REGISTRATION
 SUBSCRIBING DETAILS:   Added 4/15/24, effective with patches DG*5.3*1104 and
 PX*1.0*240 
  DATE ACTIVATED: APR 24, 2024

NUMBER: 7465                            IA #: 7465
  DATE CREATED: APR 16, 2024
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORITUL
  NAME: COORDINATE UPDATES TO CPRS INFORMATION PANELS
  ID: ORITUL
 GENERAL DESCRIPTION:   This ICR allows Clinical Reminder Exchange to notify
 the CPRS Information Panels functionality, when Reminder Exchange is
 installing updates to the National CPRS Information Panels.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: REMINDER EXCHANGE
KEYWORDS: CPRS INFO PANEL
COMPONENT/ENTRY POINT: GETNATIONAL
 COMPONENT DESCRIPTION:   This external function returns the IEN of the
 National CPRS Information Panel.  
COMPONENT/ENTRY POINT: KILLUPDATING
 COMPONENT DESCRIPTION:   This entry point kill the ^XTMP global entry that is
 set in the SETUPDATING entry point.  
COMPONENT/ENTRY POINT: SETUPDATING
 COMPONENT DESCRIPTION:   This entry point set an entry in a ^XTMP global that
 CPRS Information Panel check to disable the Information Panel when an update
 is occurring.  
COMPONENT/ENTRY POINT: KILLNATIONAL
 COMPONENT DESCRIPTION:   This entry point is used to delete the National entry
 from file 101.71.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Added 12/22/25, effective with PXRM*2.0*87 and
 OR*3.0*508 

NUMBER: 7466                            IA #: 7466
  DATE CREATED: APR 16, 2024            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMAPI
  NAME: PXRM APIS FOR CPRS INFORMATION PANELS
  ID: PXRMAPI
 GENERAL DESCRIPTION:   This ICR allows OERR to call into the Clinical Reminder
 Package for data that is needed to support the CPRS Information Panels
 functionality.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CPRS
KEYWORDS: INFORMATION PANELS
KEYWORDS: PXRM
COMPONENT/ENTRY POINT: STATMTCH
 COMPONENT DESCRIPTION:   This is used to determine if a Information Panel,
 Order Check Rule, or a Branching Logic Evaluation Status matches the Reminder
 Definition Evaluation Status. This function returns true following the rules
 outline below: 
  
 RULESTAT="D" then the Reminder Evaluation Status must either be DUE    NOW or
 DUE SOON.  
  
 RULESTAT="A" then the Reminder Evaluation Status cannot be N/A, NEVER,  
 CONTRA, or REFUSED 
  
 RULESTAT="N" then the Reminder Evaluation Status must be either N/A, NEVER,
 CONTRA, or REFUSED.  
  
 If not then the function returns false.  
VARIABLES: REMSTAT                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the Reminder Definition Evaluation Status.  
VARIABLES: RULESTAT                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the status assigned to the CPRS Information
 Panel entry, Reminder Order Check Rule, or the Reminder Dialog Branching Logic
 evaluation.  
COMPONENT/ENTRY POINT: USAGE
 COMPONENT DESCRIPTION:   This function returns the value of the USAGE field
 for the pass in entry IEN from the Reminder Definition file, #811.9.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the entry from file 811.9.  
COMPONENT/ENTRY POINT: ISACTIVE
 COMPONENT DESCRIPTION:   This component checks to see if a reminder entry in
 the file is marked active.  
VARIABLES: FN                           TYPE: Input
 VARIABLES DESCRIPTION:   This is the file number to check the entry against.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the record number to check if it is mark
 inactive.  
COMPONENT/ENTRY POINT: INFOLIST
 COMPONENT DESCRIPTION:   This API returns an array of Reminder Definitions and
 Reminder Terms that can be used in the CPRS Information Panel.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   Array of reminder terms and reminder definition that
 can be used in a CPRS Information Panel. The output format is in this format.  
  
 ARRAY(TYPE.NAME)=IEN 
  
 Where TYPE = RD or RT (RD = Reminder Definition, RT = Reminder Term) NAME = is
 the .01 from the file entry IEN =  the record number in variable pointer
 format: 
        IEN;PXD(811.9, IEN;PXRMD(811.5, 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAR 14, 2025

NUMBER: 7467                            IA #: 7467
  DATE CREATED: APR 19, 2024            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGSEC
  NAME: DGSEC                           ID: DGSEC
 GENERAL DESCRIPTION:   Call to routine DGSEC linetag SETLOG1. This allows the
 Scheduling package to pass in DUZ and DFN; which is needed so that the proxy
 user is not recorded as the user of record.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DGSEC
KEYWORDS: SETLOG1
COMPONENT/ENTRY POINT: SETLOG1
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   From the PATIENT(#2).  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   From the NEW PERSON(#200) file.  
VARIABLES: DG1                          TYPE: Input
 VARIABLES DESCRIPTION:   Inpatient/outpatient 
VARIABLES: DGOPT                        TYPE: Input
 VARIABLES DESCRIPTION:   From the OPTION(#19) file.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   Added 4/9/25, effective with SD*5.3*877. VistA
 Scheduling Enhancements (VSE)calls routine SETLOG1^DGSEC line to allow the
 Scheduling package to pass in DUZ and DFN so the proxy user is not recorded as
 the user of record. The approval is in effect until VSE migrates to the
 existing process of using XUS ESSO VALIDATE (ICR 6295) and providing the 
 actual-user's STS token to authenticate the actual user. Ongoing POAM ID 
 1018541373723 documents the action plan.  
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 4/9/25, effective with web app NUMI v1.6 (no M
 patches involved), VDIF will use functionality to properly update DG Security
 Log file (38.1) within VistA. The approval is in effect until VDIF with NUMI
 migrates to the existing process of using XUS ESSO VALIDATE (ICR 6295) and
 providing the actual-user's STS token to authenticate the actual user.  
  DATE ACTIVATED: APR 09, 2025

NUMBER: 7468                            IA #: 7468
  DATE CREATED: APR 22, 2024            CUSTODIAL PACKAGE: HEALTH SUMMARY
  USAGE: Private                        TYPE: Routine
  ROUTINE: GMTSXPD6
  NAME: INSTALL/UPDATE HEALTH SUMMARY TYPES & OBJECTS
  ID: GMTSXPD6
 GENERAL DESCRIPTION:   This integration agreement allows the subscribing
 package to install and/or update Health Summary Types and Objects.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: INSTALL HEALTH SUMMARY TYPE
KEYWORDS: INSTALL HEALTH SUMMARY OBJECT
KEYWORDS: UPDATE HEALTH SUMMARY TYPE
KEYWORDS: UPDATE HEALTH SUMMARY OBJECTS
COMPONENT/ENTRY POINT: INSDATA(GMTSTAG, GMTSRTN)
 COMPONENT DESCRIPTION:   Install or update a Health Summary type or object.  
  
 The definition of the type or object is contained in a series of line comments
 formatted as follows: 
  
     ;;FILE;FIELD;VALUE 
  
 where FILE is the file number (142 for types and 142.5 for objects), FIELD is
 the field number and VALUE is the value for that field in FileMan external
 format.  
VARIABLES: GMTSTAG                      TYPE: Input
 VARIABLES DESCRIPTION:   Name of the line tag that precedes the source code
 containing the definition for the type or object.  
VARIABLES: GMTSRTN                      TYPE: Input
 VARIABLES DESCRIPTION:   Name of the routine that contains the GMTSTAG line
 tag.  
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   Clinical Reminders will use this agreement to ensure
 that national Health Summary types and objects are installed with the correct
 internal entry number (IEN).  

NUMBER: 7469                            IA #: 7469
  DATE CREATED: MAY 07, 2024
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXCOMPACT1
  NAME: COMPACT ACT ERROR LOGGING       ID: PXCOMPACT1
 GENERAL DESCRIPTION:   Patches  DG*5.3*1104 and PX*1.0*240 will allow
 Registration to log calls to the EE Web Service in the COMPACT ACT TRANSACTION
 LOG File (#33.3).  Registration needs to access the entry point
 FILEMANERR^PXCOMPACT1 to log any data errors during this process.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COMPACT ACT
KEYWORDS: FILEMAN
COMPONENT/ENTRY POINT: FILEMANERR
 COMPONENT DESCRIPTION:   This call will send a MailMan message to the COMPACT
 ACT COORDINATORS mail group when a FileMan error is encountered while filing
 an Episode of Care or logging a COMPACT Act transaction.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient internal entry number.  
VARIABLES: DATA                         TYPE: Input
 VARIABLES DESCRIPTION:   The EOC or Transaction Log file/field location and
 data that failed to file.  
VARIABLES: MSG                          TYPE: Input
 VARIABLES DESCRIPTION:   The error message returned from FileMan.  
SUBSCRIBING PACKAGE: REGISTRATION
  DATE ACTIVATED: MAY 20, 2024

NUMBER: 7470                            IA #: 7470
  DATE CREATED: MAY 14, 2024            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        NAME: sens dgsec4
  STATUS: Pending

NUMBER: 7471                            IA #: 7471
  FILE NUMBER: 8926                     GLOBAL ROOT: TIU(8926,
  DATE CREATED: MAY 23, 2024
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TIU Highlighting Preferences
  ID: TIU(8926,
GLOBAL REFERENCE: TIU(8926,D0,2)
FIELD NUMBER: .21                       FIELD NAME: USE TEMPLATE REQD FLD HLITE
  LOCATION: 2;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .22
  FIELD NAME: TEMPLATE REQD FLD HLITE COLOR
  LOCATION: 2;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .23
  FIELD NAME: TEMPLATE REQD FLD NAV LOCATION
  LOCATION: 2;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   The Dental Record Manager Plus (DRM Plus) application
 is requesting access to TIU preferences fields related to highlighting of
 required fields.  This is to retain consistent behavior and appearance between 
 CPRS and the DRM Plus application as it pertains to provider notes.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DRM Plus
SUBSCRIBING PACKAGE: DENTAL
  DATE ACTIVATED: MAY 23, 2024

NUMBER: 7472                            IA #: 7472
  DATE CREATED: MAY 23, 2024
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXCOMPACTIB
  NAME: COMPACT ACT API for IB          ID: PXCOMPACTIB
 GENERAL DESCRIPTION:   During COMPACT Act processing, Integrated Billing (IB)
 needs to determine whether a given encounter, admission, or patient movement
 is treatment for an acute suicidal crisis. This API allows IB to call PCE for
 this information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: COMPACT ACT
COMPONENT/ENTRY POINT: REQUEST
 COMPONENT DESCRIPTION:   This API allows IB to pass in an IEN for an
 OUTPATIENT ENCOUNTER (#409.68), PTF (#45), or PATIENT MOVEMENT (#405), and
 receive a binary value indicating whether or not the treatment was for an
 acute suicidal crisis.  
VARIABLES: FILENM                       TYPE: Input
 VARIABLES DESCRIPTION:   File number for IEN being passed in IEN 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   
   IEN in file 
VARIABLES: ANS                          TYPE: Output
 VARIABLES DESCRIPTION:   Treatment for acute suicidal crisis? 
    1 - Yes 
    0 - No 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Added 5/23/2024, effective with PX*1.0*241.  
  DATE ACTIVATED: AUG 12, 2024

NUMBER: 7473                            IA #: 7473
  DATE CREATED: JUN 03, 2024            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: IBCNRDV
  NAME: Import Insurance with CBOC Move
  ID: IBCNRDV
 GENERAL DESCRIPTION:   Will initiate a %ZTLOAD call to BACKGND^IBCNRDV to
 retrieve insurance data from sites of record for brunswick cboc patients moved
 from Dublin to Charleston. This move will take place in Oct 2024. This ICR
 should expire 12/31/24. 
  STATUS: Active                        EXPIRATION DATE: DEC 31, 2024
KEYWORDS: INSURANCE QUERY
KEYWORDS: CBOC MOVE
COMPONENT/ENTRY POINT: BACKGND
VARIABLES: IBTYPE                       TYPE: Input
 VARIABLES DESCRIPTION:   = 1   Indicates a background process  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient's DFN at the requesting site. 
VARIABLES: IBDUZ                        TYPE: Input
 VARIABLES DESCRIPTION:   The requesting user's DUZ.  
VARIABLES: Insurance Buffer             TYPE: Output
 VARIABLES DESCRIPTION:   Data is returned in the INSURANCE BUFFER file 355.33. 
 
SUBSCRIBING PACKAGE: NDBI
  DATE ACTIVATED: SEP 05, 2024

NUMBER: 7474                            IA #: 7474
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200
  DATE CREATED: JUN 03, 2024            CUSTODIAL PACKAGE: KERNEL
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: NPI AND EFFECTIVE DATE/TIME
  ID: VA(200
GLOBAL REFERENCE: VA(200,D0,'NPISTATUS',
FIELD NUMBER: .01                       FIELD NAME: EFFECTIVE DATE/TIME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .02                       FIELD NAME: STATUS
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .03                       FIELD NAME: NPI
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: VA(200,D0,'NPI',
FIELD NUMBER: 41.99                     FIELD NAME: NPI
  LOCATION: NPI;1                       ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   The IAM group agrees to conditional approval of this
 ICR request. The condition is that WebVRAM commits in the future to further
 integration with IAM APIs to perform create and update of the remote sites NEW
 PERSON (#200) file record.  
  
 Approval granted pending use of IAM APIs in the future: WebVRAM is requesting
 an ICR to modify the contents of VistA file #200.042 and field #41.99 from
 file #200 with FileMan.  
  
 WebVRAM is a TELEHEALTH application that assists its users with accessing
 VistA areas outside of the main VistA area the user is associated with. 
 WebVRAM copies user profile information from the user's Home VistA area to the
 Remote VistA area they are attempting to access.  A WebVRAM user may only use
 the application to access VistA areas they have been assigned to by their
 business unit.  
  
 The WebVRAM product team was approached by the Pharmacists group in Tennessee
 about the need to use the PDMP Query in CPRS to maintain reporting compliance
 for controlled substances.  In order to use the PDMP Query in CPRS the
 pharmacist / provider is required to have a combination of a valid NPI, NPI
 effective date, and person class.   WebVRAM currently has the ability to
 update the person class at the remote VistA area and would need to update
 field #41.99 from file #200 and file #200.042 to provide the effective date
 for the NPI.  WebVRAM would use the DDR FILER RPC to modify the file contents. 
 
  STATUS: Active
KEYWORDS: NPI
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
 SUBSCRIBING DETAILS:   REQUESTING READ WRITE ACCESS TO EFFECTIVE DATE/TIME
 (#42) SUB FILE AND NPI (#41.99) FIELD OF THE NEW PERSON (#200) FILE.  
  DATE ACTIVATED: JUL 11, 2024

NUMBER: 7475                            IA #: 7475
  DATE CREATED: JUN 05, 2024
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7475
  STATUS: Pending

NUMBER: 7476                            IA #: 7476
  DATE CREATED: JUN 07, 2024
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7476
  STATUS: Pending

NUMBER: 7477                            IA #: 7477
  DATE CREATED: JUN 07, 2024
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7477
  STATUS: Pending

NUMBER: 7478                            IA #: 7478
  DATE CREATED: JUN 07, 2024
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7478
  STATUS: Pending

NUMBER: 7479                            IA #: 7479
  DATE CREATED: JUN 12, 2024            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGSEC4
  NAME: Determine if sensitive record   ID: DGSEC4
 GENERAL DESCRIPTION:   Call to routine SENS^DGSEC4 om order to help determine
 the sensitivity level of a record. Will use this API in order to check if
 record is sensitive, and if user holds DG SENSITIVITY key In order to
 appropriately determine if user request is a sensitive record check.  
  STATUS: Active
KEYWORDS: SENS
KEYWORDS: DGSEC4
COMPONENT/ENTRY POINT: SENS
VARIABLES: DGSENS                       TYPE: Output
 VARIABLES DESCRIPTION:   Return array for results.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   From the PATIENT (#2) file IEN.  
VARIABLES: DGDUZ                        TYPE: Input
 VARIABLES DESCRIPTION:   From the NEW PERSON(#200) file IEN.  
VARIABLES: DDS                          TYPE: Input
 VARIABLES DESCRIPTION:   ScreenMan variable.  
VARIABLES: DGSENFLG                     TYPE: Input
 VARIABLES DESCRIPTION:   If defined, patient record sensitivity not checked.  
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
  DATE ACTIVATED: JUL 01, 2024

NUMBER: 7480                            IA #: 7480
  DATE CREATED: JUN 12, 2024            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: DGAUDIT2
  NAME: Audit patient records at selection
  ID: DGAUDIT2
 GENERAL DESCRIPTION:   Call to routine SELAUD^DGAUDIT2 to allow VistA Web
 Service Layer (VWSL) to audit patient records at their selection. If request
 from VWSL has user reviewing a patient record, will use this API as
 appropriate to audit the records during selection.  
  STATUS: Active
KEYWORDS: DGAUDIT2
KEYWORDS: SELAUD
COMPONENT/ENTRY POINT: SELAUD
VARIABLES: DGVFILNO                     TYPE: Input
 VARIABLES DESCRIPTION:   File number for PATIENT (#2) file.  
VARIABLES: DGVDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   From the PATIENT (#2).  
VARIABLES: REQTYP                       TYPE: Input
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 10/24/24, for VDIF to support NUMI v1.6 patch.
 VDIF needs to call SELAUD^DGAUDIT2 to allow audit of patient records at their
 selection. If a VWSL request has user reviewing a patient record, VDIF will
 leverage functionality as appropriate to ensure records are properly audited.  
  
  DATE ACTIVATED: OCT 24, 2024

NUMBER: 7481                            IA #: 7481
  DATE CREATED: JUN 20, 2024            CUSTODIAL PACKAGE: LIGHTHOUSE
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: LHS CHECK OPTION ACCESS RPC
 GENERAL DESCRIPTION:   The Clinical Decision Support Platform (CDSP) requires
 access to the LHS CHECK OPTION ACCESS Remote Procedure to determine if a user
 has access to a particular option. This access is supported by Shared Support
 Services of CDSP.  
  
 The following is the LHS CHECK OPTION ACCESS Remote Procedure definition: 
  
 NAME: LHS CHECK OPTION ACCESS           TAG: OPT 
   ROUTINE: LHSRPC                       RETURN VALUE TYPE: SINGLE VALUE 
   AVAILABILITY: RESTRICTED              APP PROXY ALLOWED: Yes DESCRIPTION:   
  This RPC uses the Kernel supported API $$ACCESS^XQCHK to verify if a 
  VistA user has access to an option or not.  INPUT PARAMETER: USER             
      PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 20               REQUIRED: YES 
   SEQUENCE NUMBER: 1 DESCRIPTION:   
  This is the user DUZ being checked for option access.  INPUT PARAMETER:
 OPTION                 PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 2 DESCRIPTION:   
  This is either the IEN or the NAME of an option in the OPTION file #19.  
 RETURN PARAMETER DESCRIPTION:   
  The return data is the same as the Kernel API $$ACCESS^XQCHK supported 
  through ICR #10078.  
   
  -1:no such user in the New Person File 
  -2: User terminated or has no access code 
  -3: no such option in the Option File 
  0: no access found in any menu tree the user owns 
   
      All other cases return a 4-piece string stating 
      access ^ menu tree IEN ^ a set of codes ^ key 
   
  O^tree^codes^key: No access because of locks (see XQCODES below) 
    where 'tree' is the menu where access WOULD be allowed 
    and 'key' is the key preventing access 
  1^OpIEN^^: Access allowed through Primary Menu 
  2^OpIEN^codes^: Access found in the Common Options 
  3^OpIEN^codes^: Access found in top level of secondary option 
  4^OpIEN^codes^: Access through a the secondary menu tree OpIEN.  
   
  XQCODES can contain: 
    N=No Primary Menu in the User File (warning only) 
    L=Locked and the user does not have the key (forces 0 in first piece) 
    R=Reverse lock and user has the key (forces 0 in first piece) 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Effective with CDSP*1*1, this RPC is used to determine
 if a user has access to a particular option.  
  DATE ACTIVATED: OCT 07, 2024

NUMBER: 7482                            IA #: 7482
  DATE CREATED: JUN 25, 2024
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORDOTP
  NAME: Attach OR option to PSJU Reports menu
  ID: ORDOTP
 GENERAL DESCRIPTION:   This ICR enables the Opioid Treatment Program (OTP)
 Medication Dispense Report to be available in the Pharmacy package. It is
 called from Unit Dose Medications > Reports > OTP Dispense Report.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ASK
 COMPONENT DESCRIPTION:   This entry point will request a patient, start and
 end dates, and a device. The OTP Medication Dispense Report will then be
 generated.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
  DATE ACTIVATED: AUG 26, 2024

NUMBER: 7483                            IA #: 7483
  FILE NUMBER: 8927                     GLOBAL ROOT: TIU(8927)
  DATE CREATED: JUL 22, 2024
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PSJ FILE ACCESS 8927
  ID: TIU(8927)
GLOBAL REFERENCE: TIU(8927,B,NAME)
GLOBAL REFERENCE: TIU(8927,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: TIU(8927,D0,2,1,0)
FIELD NUMBER: 2                         FIELD NAME: BOILERPLATE TEXT
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Inpatient Medications will need to obtain read access
 to the B cross reference Name field and Boilerplate Text Field in Template
 File (8927). This read access will help determine if the Template Title in
 provider comments exist in the Template File and if it matches the Boilerplate 
 Text.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU(8927
KEYWORDS: 8927
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
 SUBSCRIBING DETAILS:   Effective with PSJ*5.0*443. In order for Inpatient
 Medications to confirm valid Template Titles in provider comments, a look up
 to the TIU Cross Reference field ^TIU(8927,"B",NAME,D0), ^TIU(8927,D0,0), and
 Boilerplate Text Field ^TIU(8927,D0,2,1,0) are needed. Therefore, the
 Inpatient Medications package requires read access via FileMan to the fields 
 referenced above in the TIU Template file.  
  DATE ACTIVATED: JUL 22, 2024

NUMBER: 7484                            IA #: 7484
  FILE NUMBER: 45                       GLOBAL ROOT: DGPT(
  DATE CREATED: AUG 07, 2024            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: TRT FOR ACUTE SUICIDAL CRISIS field in PTF
  ID: DGPT(
GLOBAL REFERENCE: DGPT(D0,70)
FIELD NUMBER: 79.33
  FIELD NAME: TRT FOR ACUTE SUICIDAL CRISIS
  LOCATION: 70;33                       ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The TRT FOR ACUTE SUICIDAL CRISIS field field indicates
 whether the given PTF is associated with an Acute Suicidal Crisis for COMPACT
 Act purposes.  
 GLOBAL DESCRIPTION:   PTF file (#45) associated with the REGISTRATION package 
 GENERAL DESCRIPTION:   In order to process a request from Integrated Billing
 (IB) via the $$REQUEST^PXCOMPACTIB API (Please see ICR #7472), PATIENT CARE
 ENCOUNTER (PCE) needs to be able to check the TRT FOR ACUTE SUICIDAL CRISIS
 field (#79.33) in the PTF file (#45).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: COMPACT ACT
KEYWORDS: PTF
KEYWORDS: ACUTE SUICIDAL CRISIS
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 8/12/24, effective with PX*1.0*241.  

NUMBER: 7485                            IA #: 7485
  FILE NUMBER: 405                      GLOBAL ROOT: DGPM(
  DATE CREATED: AUG 09, 2024            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: PATIENT MOVEMENT POINTER FIELDS
  ID: DGPM(
GLOBAL REFERENCE: DGPM(D0,0)
FIELD NUMBER: .14                       FIELD NAME: ADMISSION/CHECK-IN MOVEMENT
  LOCATION: 0,14                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The ADMISSION/CHECK-IN MOVEMENT field points to the
 parent patient movement associated with the current patient movement.  
FIELD NUMBER: .16                       FIELD NAME: PTF ENTRY
  LOCATION: 0,16                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The PTF ENTRY field points to the PTF associated with the
 current patient movement.  
FIELD NUMBER: .27                       FIELD NAME: VISIT FILE ENTRY
  LOCATION: 0,27                        ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The VISIT FILE ENTRY field points to the entry in the
 VISIT file (#9000010) associated with the patient movement.  
 GLOBAL DESCRIPTION:   PATIENT MOVEMENT file (#405) associated with the
 REGISTRATION package 
 GENERAL DESCRIPTION:   In order to process a request from Integrated Billing
 (IB) via the $$REQUEST^PXCOMPACTIB API (Please see ICR #7472), PATIENT CARE
 ENCOUNTER (PCE) needs to be able to check certain fields in the PATIENT
 MOVEMENT file (#405).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: COMPACT
KEYWORDS: ACUTE SUICIDAL CRISIS
KEYWORDS: PATIENT MOVEMENT
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 8/12/24, effective with PX*1.0*241.  

NUMBER: 7486                            IA #: 7486
  DATE CREATED: AUG 12, 2024            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  NAME: XUS ESSO VALIDATE JWT           REMOTE PROCEDURE: XUS ESSO VALIDATE JWT
 GENERAL DESCRIPTION:   This API/RPC uses either VA Identity and Access
 Management (IAM) or Microsoft EntraID JSON Web Token (JWT) payload attributes
 to authenticate a user.  The type of JSON Web Token (JWT) must be a
 "transparent" token, meaning it must contain a readable header, payload, and
 signature.  This API/RPC will validate the contents and signature of the JSON
 Web Token (JWT).  In addition, the issuer within the JWT payload must match an 
 issuer in the TOKEN VALIDATION DATA (#8981) file on the VistA system which 
 contains valid Identity Providers (IdPs) that are authorized to issue JSON Web
 Tokens (JWTs).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: ESSO
KEYWORDS: XUESSO5
KEYWORDS: JWT
KEYWORDS: AUTHENTICATION
SUBSCRIBING PACKAGE: RPC BROKER
SUBSCRIBING PACKAGE: 1

NUMBER: 7487                            IA #: 7487
  DATE CREATED: AUG 19, 2024            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUP
  NAME: INVOKE DUZ-XUP Non-HL7          ID: XUP
 GENERAL DESCRIPTION:   Temporary solution for Scheduling application, as there
 exists a gap in the RPC Broker and VistALink that cannot meet Scheduling
 needs. A POAM has been created to track this risk.  
  
 RISK: The risk being that Kernel is not part of the validation of user 
 credentials when changing the identity of the user when invoking DUZ-XUP.  
  
 GAP: The gap is the need for Scheduling to share a single connection session,
 initially owned by an approved IAM Service account (non-person, Remote
 Application), with different Scheduling users (persons), by being able to
 change both the user and the Broker context.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AUTHENTICATION
KEYWORDS: AUTHORIZATION
COMPONENT/ENTRY POINT: DUZ(IEN)
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The required input parameter to DUZ^XUP(IEN) is the
 internal entry number into file 200.  This is the user IEN of the user that
 you want to set the DUZ value and DUZ array to.  
VARIABLES: DUZ                          TYPE: Output
 VARIABLES DESCRIPTION:   This procedure returns variable DUZ equal to the
 input parameter.  Also, components of the DUZ array are set-up as well.  
SUBSCRIBING PACKAGE: SCHEDULING
 SUBSCRIBING DETAILS:   See the main description.  Effective with patch
 SD*5.3*886. Scheduling receives RPCs requests from front end applications that
 pass these requests through Acheron (middle tier) which directs the RPC call
 to the appropriate VistA system. Acheron is validated by its Remote
 Application Entry which sets the VistA DUZ array equal to this Remote
 Application Entry. For auditing purposes, Acheron also sends in the DUZ of the
 authenticated user from the front end application who is triggering the RPC
 request. Scheduling needs to reset the local DUZ array equal to the previously
 authenticated front end user so that the updated records in the Scheduling
 files will reflect the actual user who made the updates as opposed to the
 Remote Application Entry for Acheron. 
  DATE ACTIVATED: MAR 19, 2025

NUMBER: 7488                            IA #: 7488
  DATE CREATED: AUG 29, 2024
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  TYPE: Remote Procedure                NAME: ORWPT ID INFO
  REMOTE PROCEDURE: ORWPT ID INFO
 GENERAL DESCRIPTION:   The CDS Platform provides a base infrastructure with
 scalability for other applications to develop on. Teams can build clinical
 applications and register them on the existing SMART on FHIR (SoF) container
 to launch and deploy to VA sites. The platform has several capabilities that 
 facilitate the seamless transfer of patient data between EHR and applications.
 For each application on the platform, the SoF container will launch a SMART on
 FHIR application via URL, sync clinical context with CPRS and handle
 authentication and authorization of users.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Clinical Decision Support Platform is requesting use of
 the RPC ORWPT ID INFO 
    
 Use of this RPC will allow the CDSP Task Manager (TM) APP to accomplish the
 following: TM will use the ID INFO RPC to get the DOB, SSN, and Full name of a 
 patient so that the clinical users of the application can verify they have
 selected the correct patient and we can display the needed information in the
 UI.  

NUMBER: 7489                            IA #: 7489
  DATE CREATED: AUG 30, 2024
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWTPT ATEAMS
  REMOTE PROCEDURE: ORWTPT ATEAMS
 GENERAL DESCRIPTION:   The CDS Platform provides a base infrastructure with
 scalability for other applications to develop on. Teams can build clinical
 applications and register them on the existing SMART on FHIR (SoF) container
 to launch and deploy to VA sites. The platform has several capabilities that 
 facilitate the seamless transfer of patient data between EHR and applications.
 For each application on the platform, the SoF container will launch a SMART on
 FHIR application via URL, sync clinical context with CPRS and handle
 authentication and authorization of users.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 2/14/25, effective with CDSP*1.0*2. This RPC will
 be defined in the CDSP RPC CONTEXT option. Task manager is a team based task
 tracking solution, to facilitate user onboarding. This RPC will be used to
 return a list of teams that the user can subscribe to, for team selection by
 user.  
  DATE ACTIVATED: FEB 14, 2025

NUMBER: 7490                            IA #: 7490
  DATE CREATED: AUG 30, 2024
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: ORWTPT GETTEAM
  REMOTE PROCEDURE: ORWTPT GETTEAM
 GENERAL DESCRIPTION:   The CDS Platform provides a base infrastructure with
 scalability for other applications to develop on. Teams can build clinical
 applications and register them on the existing SMART on FHIR (SoF) container
 to launch and deploy to VA sites. The platform has several capabilities that 
 facilitate the seamless transfer of patient data between EHR and applications.
 For each application on the platform, the SoF container will launch a SMART on
 FHIR application via URL, sync clinical context with CPRS and handle
 authentication and authorization of users.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 2/14/25, effective with CDSP*1.0*2. After a user
 has selected a specific team they are a part of in our application, the ORWTPT 
 GETTEAM RPC is used by the application to  display all the other team members
 to the user. Getting all the team member names will allow one user to onboard
 their entire team at once instead of requiring each user to sign up
 individually. This RPC will be defined in the CDSP RPC CONTEXT option.  
  DATE ACTIVATED: FEB 14, 2025

NUMBER: 7491                            IA #: 7491
  DATE CREATED: AUG 30, 2024
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  TYPE: Remote Procedure                NAME: ORQPT TEAM PATIENTS
  REMOTE PROCEDURE: ORQPT TEAM PATIENTS
 GENERAL DESCRIPTION:   The CDS Platform provides a base infrastructure with
 scalability for other applications to develop on. Teams can build clinical
 applications and register them on the existing SMART on FHIR (SoF) container
 to launch and deploy to VA sites. The platform has several capabilities that 
 facilitate the seamless transfer of patient data between EHR and applications.
 For each application on the platform, the SoF container will launch a SMART on
 FHIR application via URL, sync clinical context with CPRS and handle
 authentication and authorization of users.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Once a user has selected their relevant team, the TM
 application will use the TEAM PATIENT RPC to get a list of patients associated
 with that team. With this, the user will not have to search for each
 individual patient, reducing clinical burden and speeding up their workflow 

NUMBER: 7492                            IA #: 7492
  DATE CREATED: SEP 09, 2024            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOEPUT2
  NAME: PSO EPCS PSDRPH FILER           ID: PSOEPUT2
 GENERAL DESCRIPTION:   The Web Veteran's Health Information Systems and
 Technology Architecture (VistA) Remote Access Management (WebVRAM) application
 requires a Remote Procedure Call (RPC) that allocates and deallocates the
 PSDRPH key to a specific user and logs the event in the XUEPCS PSDRPH AUDIT
 file (#8991.7). The PSO EPCS PSDRPH FILER RPC has been created to allocate and 
 de-allocate and audit the assignment/unassignment of the PSDRPH key.  
  
 Remote Procedure: PSO EPCS PSDRPH FILER 
 ---------------------------------------
 ROUTINE: PSOEPUT2 COMPONENT:  PSDKEY 
  
 DESCRIPTION: The PSDKEY entry point is invoked by the PSO EPCS PSDRPH FILER
 Remote Procedure Call (RPC) to perform allocation and deallocation of the
 PSDRPH key, and log the event in the XUEPCS PSDRPH AUDIT file (#8991.7).  
  
 VARIABLES: PSOSUBJ (Input) The NEW PERSON (#200) file Internal Entry Number
 (IEN) of the user to whom the PSDRPH key is being allocated or deallocated.  
  
 VARIABLES: PSOACTOR (Input) The NEW PERSON (#200) file Internal Entry Number
 (IEN) of the user performing the allocation or deallocation of the PSDRPH key. 
  
 VARIABLES: PSOACTION (Input) A flag indicating the type of action to be taken,
 either "A" to allocate the PSDRPH key, or "D" to deallocate the PSDRPH key.  
  
 VARIABLES: RESULTS (Output) The return value is 1 if the allocation or
 deallocation was successful.  The return value is 0^Error Message Text if the
 allocation or deallocation was unsuccessful.  
  
  Revision History - 
  10/16/24 The WebVRAM and Outpatient Pharmacy development teams are working
 together on the release of the RPC and the WebVRAM GUI changes to invoke the
 RPC. The Pharmacy patch is PSO*7*732 and the WEBG patch is WEBG*3*21. The ICR
 that authorizes Pharmacy's reference to file 8991.7 is #7016. This RPC
 performs the same function as the Allocate/De-Allocate of PSDRPH Key (Audited)
 [PSO EPCS PSDRPH KEY]. WebVRAM's subscription to ICR 7016 is valid only as
 long as ICR 7492 is active.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PSDRPH
COMPONENT/ENTRY POINT: PSDKEY
 COMPONENT DESCRIPTION:   The PSDKEY entry point is invoked by the PSO EPCS
 PSDRPH FILER Remote Procedure Call (RPC) to perform allocation and
 deallocation of the PSDRPH key, and log the event in the XUEPCS PSDRPH AUDIT
 file (#8991.7).  
VARIABLES: PSOSUBJ                      TYPE: Input
 VARIABLES DESCRIPTION:   The NEW PERSON (#200) file Internal Entry Number
 (IEN) of the user to whom the PSDRPH key is being allocated or deallocated.  
VARIABLES: PSOACTOR                     TYPE: Input
 VARIABLES DESCRIPTION:   The NEW PERSON (#200) file Internal Entry Number
 (IEN) of the user performing the allocation or deallocation of the PSDRPH key. 
 
VARIABLES: PSOACTION                    TYPE: Input
 VARIABLES DESCRIPTION:   A flag indicating the type of action to be taken,
 either "A" to allocate the PSDRPH key, or "D" to deallocate the PSDRPH key.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   The return value is 1 if the allocation or
 deallocation was successful. The return value is 0^Error Message Text if the
 allocation or deallocation was unsuccessful.  
SUBSCRIBING PACKAGE: WEB VISTA REMOTE ACCESS MANAGEMENT
  DATE ACTIVATED: OCT 16, 2024

NUMBER: 7493                            IA #: 7493
  FILE NUMBER: 101.22                   GLOBAL ROOT: ORD(101.22,
  DATE CREATED: SEP 13, 2024
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: READ/WRITE ACCESS TO OTP MEDICATION DISPENSE FILE
  ID: ORD(101.22,
GLOBAL REFERENCE: ORD(101.22,D0,0
FIELD NUMBER: .01                       FIELD NAME: PATIENT NAME
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: multiple                  FIELD NAME: OTP DISPENSE RECORD
  LOCATION: 1;0                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is the Opioid Treatment Program dispense record. It
 is a multiple record field that contains patient(s) dispense record
 information.  
GLOBAL REFERENCE: ORD(101.22,D0,1,D1,0
FIELD NUMBER: .01                       FIELD NAME: MEDICATION DATE
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   Enter the date the medication should be taken. For
 example, 03/01/24 
FIELD NUMBER: 2                         FIELD NAME: MEDICATION TYPE
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is the name of the medication being dispensed.  
FIELD NUMBER: 3                         FIELD NAME: DISPENSE DATE/TIME
  LOCATION: 0;3                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is the Date and Time that the medication was
 dispensed.  
FIELD NUMBER: 4                         FIELD NAME: DISPENSE BY NAME
  LOCATION: 0;4                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is the name of the person dispensing the medication. 
 
FIELD NUMBER: 5                         FIELD NAME: DISPENSE BY INITIALS
  LOCATION: 0;5                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is the initials of the person that dispensed the
 medication.  
FIELD NUMBER: 6                         FIELD NAME: DISPENSE ACTION
  LOCATION: 0;6                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This field indicates whether the medication was dispensed
 in Clinic or if it was a Take-Home dose.  
FIELD NUMBER: 7                         FIELD NAME: DISPENSE AMOUNT
  LOCATION: 0;7                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is the dosage of medication being dispensed.  
FIELD NUMBER: 8                         FIELD NAME: INTERFACE RECEIVED DATE/TIME
  LOCATION: 0;8                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is the Date and Time that the interface message was
 received.  
FIELD NUMBER: 9                         FIELD NAME: INTERFACE
  LOCATION: 0;9                         ACCESS: Direct Global R/W & w/Fileman
 FIELD DESCRIPTION:   This is the vendor interface name.  
 GENERAL DESCRIPTION:   The Text Integration Utilities (TIU) Package needs
 read/write access to the OTP Medication Dispense File (#101.22) in support of
 the Methadone Dispense Tracking project.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: OTP
KEYWORDS: ORD(101.22
KEYWORDS: DISPENSE
KEYWORDS: OPIOID
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES

NUMBER: 7494                            IA #: 7494
  FILE NUMBER: 9000010.71               GLOBAL ROOT: AUPNVSC(
  DATE CREATED: SEP 16, 2024
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: READ V STANDARD CODES DATA
  ID: AUPNVSC(
GLOBAL REFERENCE: AUPNVHF(D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  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: .05                       FIELD NAME: CODING SYSTEM
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: PROBLEM LIST ENTRY
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: AUPNVSC(D0,400)
FIELD NUMBER: 400                       FIELD NAME: SOURCE TAXONOMY
  LOCATION: 400;1                       ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: V STANDARD CODES
KEYWORDS: READ
SUBSCRIBING PACKAGE: CLINICAL REMINDERS
 SUBSCRIBING DETAILS:   V STANDARD CODES entries are used as a findings in
 Clinical Reminders.  Therefore, Clinical Reminders needs to read the following
 fields.  
  DATE ACTIVATED: SEP 16, 2024

NUMBER: 7495                            IA #: 7495
  DATE CREATED: SEP 18, 2024            CUSTODIAL PACKAGE: LIGHTHOUSE
  TYPE: Remote Procedure
  NAME: CDSP REQUESTING ACCESS TO LHS CHECK OPTION ACCESS RPC
 GENERAL DESCRIPTION:   Clinical Decision Support Platform is requesting access
 to the Lighthouse RPC LHS CHECK OPTION ACCESS. The CDSP Platform team is
 reuesting this RPC be added to the menu option CDSP RPC CONTEXT to determine
 is a particular user has access to a specific VistA menuu option.  
  
 The Platform team is requesting this access to support future APPs that may
 use the common Clinical Decision Support Platform as a shared service. This
 will also support enhancements to current APPs in the  CDS group of APPs such
 as MedPic, MecCalc, Lung Cancer Screening v2 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   
  

NUMBER: 7496                            IA #: 7496
  DATE CREATED: SEP 27, 2024
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7496
  STATUS: Pending

NUMBER: 7497                            IA #: 7497
  DATE CREATED: SEP 27, 2024            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: MAGT7MA
  NAME: Call MAGT7MA For LAB Data From File 63
  ID: MAGT7MA
 GENERAL DESCRIPTION:   MEDICOM TECHNOLOGIES requests to call $$GETFILE^MAGT7MA
 to get LABORATORY TEST file (#60) data, determine the error status of the lab
 and return FILE("FIELD") fields for the LAB DATA file (#63).  
  STATUS: Active
KEYWORDS: MEDICOM
COMPONENT/ENTRY POINT: GETFILE
 COMPONENT DESCRIPTION:   Get LAB DATA (#63) data and return an error status.  
VARIABLES: LRSS                         TYPE: Input
 VARIABLES DESCRIPTION:   Get specific area for the record in the LABORATORY 
 TEST file (#60): "CY", "EM", or "SP". 
VARIABLES: ERRSTAT                      TYPE: Output
 VARIABLES DESCRIPTION:   If an error status is returned, there is nothing to
 report.  
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES

NUMBER: 7498                            IA #: 7498
  DATE CREATED: OCT 03, 2024
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7498
  STATUS: Pending

NUMBER: 7499                            IA #: 7499
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7499
  STATUS: Pending

NUMBER: 7500                            IA #: 7500
  DATE CREATED: OCT 03, 2024
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: ORDOTP1
  NAME: TIU CALL TO OTP FILER           ID: ORDOTP1
 GENERAL DESCRIPTION:   ORDOTP1 is an API that will update file (#101.22) with
 dispense data from an opioid clinic. ICR 7500 was created to support the
 METHADON DISPENSE TRACKING project, effective with TIU*1.0*360 and
 ORD*3.0*618.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: OTP FILER
KEYWORDS: ORDOTP1
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   EN accepts two parameters.  The first is the patient
 ID and the second is an array that will contain all of the fields and data
 that is required by file #101.22.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   PATIENT ID 
VARIABLES: DSTR                         TYPE: Input
 VARIABLES DESCRIPTION:   ARRAY containing the fields with data that will be
 entered into 101.22 
SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES
 SUBSCRIBING DETAILS:   TIU is calling EN^ORDOTP1 from TIUOTPF 
  DATE ACTIVATED: MAR 12, 2025

NUMBER: 7501                            IA #: 7501
  DATE CREATED: OCT 10, 2024            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: MAGT7SB                      NAME: Get Lab Test Data
  ID: MAGT7SB
 GENERAL DESCRIPTION:   The routine creates the OBR segment for HL7 message to
 DPS and provides a lookup for Lab Test 
  STATUS: Active
KEYWORDS: MEDICOM
COMPONENT/ENTRY POINT: TESTLKUP
 COMPONENT DESCRIPTION:   Returns the lab test ID and lab test text for a 
 specific lab case. If no lab test is found, it returns the IEN of the 
 PROCEDURED FIELD file (#61.5) and the PROCEDURE NAME field (#.01).  
VARIABLES: LABDATA                      TYPE: Input
 VARIABLES DESCRIPTION:   LABDATA is the IEN of the lab in the LAB DATA (#63)
 file.  
VARIABLES: LABTEST                      TYPE: Output
 VARIABLES DESCRIPTION:   Returns the lab test ID and the name of the
 Laboratory test defining the entry.  If no lab test ID is found, it returns
 the IEN of the PROCEDURE FIELD file (#61.5) and the PROCEDURE NAME field
 (#.01).  
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES

NUMBER: 7502                            IA #: 7502
  DATE CREATED: OCT 11, 2024
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: ORQQVI METRIC FIRST PARAMETER
 GENERAL DESCRIPTION:   This integration agreement allows the subscribing
 package to retrieve the value(s) stored in the ORQQVI METRIC FIRST parameter
 via supported calls to the appropriate KERNEL API.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DISPLAY METRIC VITALS
KEYWORDS: METRIC VALUE
KEYWORDS: IMPERIAL VALUE
COMPONENT/ENTRY POINT: ORQQVI METRIC FIRST
 COMPONENT DESCRIPTION:   This parameter controls whether metric values should
 appear before or after imperial values when displaying a patient's vitals.  
  
 Access to this parameter is READ-ONLY.  
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   Health Summary will use this integration agreement with
 components that display vitals to ensure proper formatting. Specifically, this
 parameter is used to determine whether to display metric values before
 imperial values.  
  DATE ACTIVATED: OCT 16, 2024

NUMBER: 7503                            IA #: 7503
  FILE NUMBER: 9002313.03               GLOBAL ROOT: BPSR(
  DATE CREATED: OCT 22, 2024            CUSTODIAL PACKAGE: E CLAIMS MGMT ENGINE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ ACCESS ONLY TO BPS RESPONSES FILE
  ID: BPSR(
 GENERAL DESCRIPTION:   E CLAIMS MGMT ENGINE grants INSURANCE CAPTURE BUFFER
 FileMan Read access to all fields and cross references in the BPS RESPONSES
 (#9002313.03) file.  Direct global read access of all cross-references is
 allowed.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DSIV
KEYWORDS: INSURANCE CAPTURE BUFFER
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
  DATE ACTIVATED: OCT 22, 2024

NUMBER: 7504                            IA #: 7504
  DATE CREATED: OCT 22, 2024            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: MAGDSTA3                     NAME: DICOM Patient Lookup
  ID: MAGDSTA3
 GENERAL DESCRIPTION:   API's and RPC'S for VistA PATIENT lookup routine 
  STATUS: Active
KEYWORDS: MEDICOM
COMPONENT/ENTRY POINT: PATLKUP
 COMPONENT DESCRIPTION:   The call to PATLKUP returns the number of patients
 with the value sent in and an array containing patient data.  
VARIABLES: INPUT                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient value to lookup 
VARIABLES: OUTPUT                       TYPE: Output
 VARIABLES DESCRIPTION:   Data OUTPUT(0)=number of records for i=1:number of
 records returned: DFN^Patient Name^DOB^PID^SEX^DOD^Sensitive 
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES

NUMBER: 7505                            IA #: 7505
  DATE CREATED: NOV 04, 2024            CUSTODIAL PACKAGE: IMAGING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: MAGVIM01
  NAME: Setup Rad/Nuc Med HL7 Output Array Separators
  ID: MAGVIM01
 GENERAL DESCRIPTION:   Patch MECH*1.0*1 gathers patient cases to send to the
 ImageX Application via HL7 messages. This patch calls $$OUTSEP^MAGVIM01 and
 $$STATSEP^MAGVIM01 to get the correct separators for the HL7 messages.  
  STATUS: Active
KEYWORDS: MEDICOM
COMPONENT/ENTRY POINT: OUTSEP
 COMPONENT DESCRIPTION:   The function returns the name value separator for HL7
 output data. 
COMPONENT/ENTRY POINT: STATSEP
 COMPONENT DESCRIPTION:   The function returns the status and result separator
 for HL7 output data.  
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES

NUMBER: 7506                            IA #: 7506
  DATE CREATED: NOV 07, 2024
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXSPECAUTH
  NAME: SPECIAL AUTHORITIES             ID: PXSPECAUTH
 GENERAL DESCRIPTION:   Patch PX*1*244 will release a new SPECIAL AUTHORITIES
 FILE #(820) and a routine of API calls to retrieve information about all the
 special authorities. This Controlled ICR allows subscribers to call these
 APIs.  
  
 The Special Authorities file will define all the currently known Special
 Authorities. This file will facilitate future growth and help minimize
 elaborate software enhancements when adding a new special authority. This file
 contains the business rules for each special authority, e.g. name, code,
 disabled, abbreviation, sequence, default, disabled, visible, Package -
 disabled?, Linked authority behavior rules, Linked Authority, When value is,
 Actions to take.  
  
 See the individual component entries for descriptions and examples of how to
 call the API and what it returns.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SPECIAL AUTHORITY
KEYWORDS: ENVIRONMENTAL
KEYWORDS: INDICATORS
KEYWORDS: SPECIAL AUTHORITIES
COMPONENT/ENTRY POINT: SETARRAY
 COMPONENT DESCRIPTION:   DESCRIPTION Special Authorities definitions and
 optionally full business rules and help text wp field.  
VARIABLES: AR                           TYPE: Output
 VARIABLES DESCRIPTION:   Array to return Special Authority business rules and
 optionally including the full instructions and Help text.  
VARIABLES: FULLSTRUCT                   TYPE: Input
 VARIABLES DESCRIPTION:   Boolean field. One of 2 valid statuses below: 
       0 for no 
       1 for yes 
   
  Example call base rules: D 
  SETARRAY^PXSPECAUTH(.AR,0)   base rules 
   
  Example output: Below showing a sampling of the output. Only the first 
  3 indicators.  Whereas, you would receive all.  
   
  AR("specialAuthorityTypes",10,"abbreviation")="SC" 
  AR("specialAuthorityTypes",10,"code")="SC" 
  AR("specialAuthorityTypes",10,"default")="Unanswered" 
  AR("specialAuthorityTypes",10,"disabled")="false" 
  AR("specialAuthorityTypes",10,"displayName")="Service &Connected Condition" 
  AR("specialAuthorityTypes",10,"id")=1 
  AR("specialAuthorityTypes",10,"sequence")=10 
  AR("specialAuthorityTypes",20,"abbreviation")="CV" 
  AR("specialAuthorityTypes",20,"code")="CV" 
  AR("specialAuthorityTypes",20,"default")="Unanswered" 
  AR("specialAuthorityTypes",20,"disabled")="false" 
  AR("specialAuthorityTypes",20,"displayName")="Combat&Vet (Combat Related)" 
  AR("specialAuthorityTypes",20,"id")=8 
  AR("specialAuthorityTypes",20,"sequence")=20 
   
  
  Example call all rules: D 
  SETARRAY^PXSPECAUTH(.AR,1)  all rules 
   
  AR("specialAuthorityTypes",10,"abbreviation")="SC" 
  AR("specialAuthorityTypes",10,"code")="SC" 
  AR("specialAuthorityTypes",10,"default")="Unanswered" 
  AR("specialAuthorityTypes",10,"description","\",1)="Service-Connected(SC) 
 :"_$c( 13,10) 
  AR("specialAuthorityTypes",10,"description","\",2)="Veterans are eligible for
 medical care for treatment of service-connected"_$c(13,10) 
  AR("specialAuthorityTypes",10,"description","\",3)="(SC) conditions without
 incurring copayment charges or claims against"_$c(13,10) 
  AR("specialAuthorityTypes",10,"description","\",4)="their insurance. See 
 'Help' for additional information."_$c(13,10) 
  AR("specialAuthorityTypes",10,"disabled")="false" 
  AR("specialAuthorityTypes",10,"displayName")="Service &Connected Condition" 
  AR("specialAuthorityTypes",10,"id")=1 
  AR("specialAuthorityTypes",10,"package",1,"excluded")="false" 
  AR("specialAuthorityTypes",10,"package",1,"name")="ORDER ENTRY/RESULTS 
 REPORTING" 
  AR("specialAuthorityTypes",10,"sequence")=10 
  AR("specialAuthorityTypes",10,"valueChangeActions",1,"actions",1)="SetUna 
 nswered " 
  AR("specialAuthorityTypes",10,"valueChangeActions",1,"actions",2)="Disabl e " 
  AR("specialAuthorityTypes",10,"valueChangeActions",1,"linkedSpecialAuthor i
 ties", 1)="AO" 
  AR("specialAuthorityTypes",10,"valueChangeActions",1,"linkedSpecialAuthor i
 ties", 2)="EC" 
  AR("specialAuthorityTypes",10,"valueChangeActions",1,"linkedSpecialAuthor i
 ties", 3)="IR" 
  AR("specialAuthorityTypes",10,"valueChangeActions",1,"whenValueIs")="Yes" 
  AR("specialAuthorityTypes",10,"valueChangeActions",2,"actions",1)="Enable 
 "
  AR("specialAuthorityTypes",10,"valueChangeActions",2,"linkedSpecialAuthor i
 ties", 1)="AO" 
  AR("specialAuthorityTypes",10,"valueChangeActions",2,"linkedSpecialAuthor i
 ties", 2)="EC" 
  AR("specialAuthorityTypes",10,"valueChangeActions",2,"linkedSpecialAuthor i
 ties", 3)="IR" 
  AR("specialAuthorityTypes",10,"valueChangeActions",2,"whenValueIs")="No" 
  AR("specialAuthorityTypes",10,"valueChangeActions",3,"actions",1)="Enable 
 "
  AR("specialAuthorityTypes",10,"valueChangeActions",3,"linkedSpecialAuthor 
 ities", 1)="AO" 
  AR("specialAuthorityTypes",10,"valueChangeActions",3,"linkedSpecialAuthor 
 ities", 2)="EC" 
  AR("specialAuthorityTypes",10,"valueChangeActions",3,"linkedSpecialAuthor 
 ities", 3)="IR" 
  AR("specialAuthorityTypes",10,"valueChangeActions",3,"whenValueIs")="Unan 
 swered" 
  AR("specialAuthorityTypes",20,"abbreviation")="CV" 
  AR("specialAuthorityTypes",20,"code")="CV" 
  AR("specialAuthorityTypes",20,"default")="Unanswered" 
  AR("specialAuthorityTypes",20,"description","\",1)="Combat Veteran 
 (CV):"_$c(13, 10) 
  AR("specialAuthorityTypes",20,"description","\",2)="To receive CV exemption
 the veteran must have served in combat operations"_$c(13,10) 
  AR("specialAuthorityTypes",20,"description","\",3)="after the Gulf War or in
 com bat against a hostile force after November 11,"_$c(13,10) 
  AR("specialAuthorityTypes",20,"description","\",4)="1998. In addition, the
 condition for which the veteran is treated must be"_$c(13,10) 
  AR("specialAuthorityTypes",20,"description","\",5)="related to that combat,
 the veteran must have registered as a combat"_$c(13,10) 
  AR("specialAuthorityTypes",20,"description","\",6)="veteran, and be within
 two y ears of separation from active military"_$c(13,10) 
  AR("specialAuthorityTypes",20,"description","\",7)="service. Finally, the
 condition must not be already considered to be"_$c(13,10) 
  AR("specialAuthorityTypes",20,"description","\",8)="service related or that
 exemption should apply. See 'Help' for additional"_$c(13,10) 
  AR("specialAuthorityTypes",20,"description","\",9)="information."_$c(13,1 0) 
  AR("specialAuthorityTypes",20,"disabled")="false" 
  AR("specialAuthorityTypes",20,"displayName")="Combat &Vet (Combat Related)" 
  AR("specialAuthorityTypes",20,"id")=8 
  AR("specialAuthorityTypes",20,"package",1,"excluded")="true" 
  AR("specialAuthorityTypes",20,"package",1,"name")="PROBLEM LIST" 
  AR("specialAuthorityTypes",20,"sequence")=20 
COMPONENT/ENTRY POINT: $$FINDBYCODE(SACODE)
 COMPONENT DESCRIPTION:   This extrinsic function returns the file #820
 internal entry number (IEN) for this indicator from the SA file (#820) for the
 SA CODE value passed in.  
VARIABLES: SACODE                       TYPE: Input
 VARIABLES DESCRIPTION:   The SA code 
VARIABLES: IEN                          TYPE: Output
 VARIABLES DESCRIPTION:   Example: $$FINDBYCODE^PXSPECAUTH("AO") returns 2.  
COMPONENT/ENTRY POINT: $$FINDBYNAME(NAME)
 COMPONENT DESCRIPTION:   This extrinsic function returns the file #820
 internal entry number (IEN) for this indicator.  
VARIABLES: NAME                         TYPE: Input
 VARIABLES DESCRIPTION:   The Name of the SA.  
VARIABLES:                              TYPE: Output
 VARIABLES DESCRIPTION:   Example: $$FINDBYNAME^PXSPECAUTH("IONIZING RADIATION
 EXPOSURE") returns 3.  
COMPONENT/ENTRY POINT: $$GETDISPLAYNAME(IEN)
 COMPONENT DESCRIPTION:   This extrinsic function returns the display name of
 the Special Authority.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the indicator from file #820.  
VARIABLES:                              TYPE: Output
 VARIABLES DESCRIPTION:   The Special Authority name to be displayed to the
 user.  
  
 Example: $$GETDISPLAYNAME^PXSPECAUTH(8) returns: "Combat &Vet(Combat Related)" 
  
 Note: "&" is the Delphi GUI hot key indication, translate that character to
 NULL for printable or VistA screen media.  
COMPONENT/ENTRY POINT: $$GETVALUE(VALUE)
 COMPONENT DESCRIPTION:   This extrinsic function returns the default value for
 the SA file as JSON.  
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   The internal value for the SA.  
VARIABLES: RETURN                       TYPE: Output
 VARIABLES DESCRIPTION:   The external value for the passed in internal value.  
  
 Example: VALUE="1" then returns "Yes", 
          VALUE="0" then returns "No", 
          all other passed in values returns "Unanswered" 
COMPONENT/ENTRY POINT: $$GETZERO(IEN)
 COMPONENT DESCRIPTION:   This extrinsic function returns the 0 node from file
 #820, which, contains these pieces: NAME ^ CODE ^ DISPLAY NAME ^ SEQ ^
 ABBREVIATION ^ SCHEDULING SEQUENCE DEFAULT SPECIAL AUTHORITY ^DISABLED 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The IEN of the indicator from the SA file.  
VARIABLES:                              TYPE: Output
 VARIABLES DESCRIPTION:   The 0 node as described above.  
  
 Example: $$GETZERO^PXSPECAUTH(8) returns "COMBAT VETERAN^CV^Combat &Vet 
 (Combat Related)^10^CV^^1^^" 
COMPONENT/ENTRY POINT: $$PKGEXCL(SACODE,PKGNAME)
 COMPONENT DESCRIPTION:   This extrinsic function returns 1 if 1 if it is
 excluded 0 if it is not.  
VARIABLES: SACODE                       TYPE: Input
 VARIABLES DESCRIPTION:   The code of the SA in file #820.  
  
 Example: "AO" is Agent Orange 
VARIABLES: PKGNAME                      TYPE: Input
 VARIABLES DESCRIPTION:   The Name of the package found in the PACKAGE file
 (#9.4).  
  
 Example: "PROBLEM LIST" 
VARIABLES:                              TYPE: Output
 VARIABLES DESCRIPTION:   Boolean value: 1 if the package is excluded for the
 SA, 0 if SA is not.  
  
 Example: W $$PKGEXCL^PXSPECAUTH("CV","PROBLEM LIST") will return 1.  
COMPONENT/ENTRY POINT: GETSADEF
 COMPONENT DESCRIPTION:   This API determines which Special Authorities must be
 answered by the end user.  
VARIABLES: INPUTS                       TYPE: Input
 VARIABLES DESCRIPTION:   The inputs are in a subscripted array containing the
 following: 
                             
  INPUTS("patientId")=100840 
  INPUTS("dateTime")=3250423.1458 
  INPUTS("location")=240 
  INPUTS("visitIen")=7456 
  INPUTS("loadStructure")="true" 
                             
 The subscripts patientId and dateTime are required, the others are optional. 
  patientId: the patient's DFN 
  dateTime: the date and time to evaluate the patient for which the 
            Special Authority should be answered.  
                             
 The subscripts location, visitIen, and loadStructure are optional: 
                             
  location is the IEN of the Hospital Location from file #44.  
  visitIen is the IEN from file #9000010.  
VARIABLES: RESULTS                      TYPE: Output
 VARIABLES DESCRIPTION:   The output is a subscripted array defining the order
 in which the special authorities should appear in the application and the
 properties for each item. The code subscript is the code. The default
 subscript indicates if the special authority should have a default value. The
 visible subscript, if set to true, indicates that the special authority must
 be answered; if set to false, the special authority should not be prompted
 for.  
  
 Example output: 
   RESULTS("specialAuthority",1,"code")="SC" 
   RESULTS("specialAuthority",1,"default")="Unanswered" 
   RESULTS("specialAuthority",1,"visible")="true" 
   RESULTS("specialAuthority",2,"code")="CV" 
   RESULTS("specialAuthority",2,"default")="Yes" 
   RESULTS("specialAuthority",2,"visible")="true 
COMPONENT/ENTRY POINT: GETPATSA
 COMPONENT DESCRIPTION:   This API returns whether the Special Authorities
 questions should/can be asked for a patient at a specific date/time. It also
 returns whether the Special Authorities question should have a default value.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The pointer value of the location entry[PR2]  from
 file #2, required.  
VARIABLES: ATM                          TYPE: Input
 VARIABLES DESCRIPTION:   The Encounter Date/Time, required 
VARIABLES: LOC                          TYPE: Input
 VARIABLES DESCRIPTION:   The pointer value of the location entry from file
 #44, optional.  
VARIABLES: PXARRAY                      TYPE: Output
 VARIABLES DESCRIPTION:   This is the result of the call in the following
 format: PXARRAY(CODE)=ASK^DEFAULT 
  
       CODE: The text value from field #2 for the entry from file #820.  
       ASK:  Boolean value (1 or 0), a value of 1 means to ask the Special 
             Authority, a value of 0 means do not ask.  
       DEFAULT: Boolean value (1 or 0), a value of 1 means default to Yes, 
             a value of 0 means default to No. No value means do not 
             set a default.  
COMPONENT/ENTRY POINT: $$ISACTIVECODE
 COMPONENT DESCRIPTION:   This extrinsic function returns 0 if the code cannot
 be found or if the code is inactive. Returns 1 is the code is active.  
VARIABLES: CODE                         TYPE: Input
 VARIABLES DESCRIPTION:   The internal text of the CODE value 
VARIABLES: RETURN                       TYPE: Output
 VARIABLES DESCRIPTION:   Boolean value, returns 1 or 0 
COMPONENT/ENTRY POINT: GETCODE
 COMPONENT DESCRIPTION:   Returns the value in Code field #2 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   The internal IEN for the SA from file 820.  
VARIABLES: Return                       TYPE: Output
 VARIABLES DESCRIPTION:   Return the Code value stored in field #2 
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 11/05/24, effective with patches PX*1*244 and
 OR*3*508. The OERR package will be subscribing to this routine to return all
 the valid authorities and their characteristics.  
  
 Added 11/13/25, effective with patch PX*1.0*244 Component GETPATSA and
 ISACTIVECODE were added and corrected some typo.  
  
 Added 12/05/25, effective with patch PX*1.0*244 Component GETCODE was added 
SUBSCRIBING PACKAGE: PROBLEM LIST
 SUBSCRIBING DETAILS:   Added 6/18/25, effective with patches GMPL*2*58 and 
 OR*3*508. The GMPL package will subscribe to this routine to return all the
 valid authorities and their characteristics.  
  DATE ACTIVATED: APR 28, 2025

NUMBER: 7507                            IA #: 7507
  DATE CREATED: JAN 03, 2025
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7507
  STATUS: Pending

NUMBER: 7508                            IA #: 7508
  DATE CREATED: JAN 03, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Supported                      TYPE: Routine
  ROUTINE: ORY618F                      NAME: TIU Progress Note Build
  ID: ORY618F
 GENERAL DESCRIPTION:   This utility will be used to do a db cleanup of
 Boston's production system.  
  STATUS: Pending

NUMBER: 7509                            IA #: 7509
  DATE CREATED: JAN 16, 2025
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7509
  STATUS: Pending

NUMBER: 7510                            IA #: 7510
  DATE CREATED: JAN 16, 2025
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7510
  STATUS: Pending

NUMBER: 7511                            IA #: 7511
  DATE CREATED: JAN 16, 2025            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Remote Procedure
  NAME: IAM AUTHORIZED REMOTE APPLICATION INTERFACE
 GENERAL DESCRIPTION:   This ICR supports control and security for remote
 applications accessing VistA systems, ensuring that they are approved and
 authorized by the VistA Review Board and managed by Identity and Access
 Management (IAM) Service.  
  STATUS: Pending
KEYWORDS: RPC
KEYWORDS: REMOTE PROCEDURE CALL
KEYWORDS: IAM
KEYWORDS: REMOTE APPLICATION
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX

NUMBER: 7512                            IA #: 7512
  DATE CREATED: JAN 16, 2025
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7512
  STATUS: Pending

NUMBER: 7513                            IA #: 7513
  FILE NUMBER: 75.1                     GLOBAL ROOT: RAO(75.1
  DATE CREATED: JAN 16, 2025
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: File
  NAME: RADIOLOGY ORDER INFORMATION (READ ONLY)
  ID: RAO(75.1
GLOBAL REFERENCE: RAO(75.1,D0,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: PROCEDURE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: TYPE OF IMAGING
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: CATEGORY OF EXAM
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: REQUEST STATUS
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 6                         FIELD NAME: REQUEST URGENCY
  LOCATION: 0;6                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: ORDER
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 9                         FIELD NAME: CONTRACT/SHARING SOURCE
  LOCATION: 0;9                         ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: REASON
  LOCATION: 0;10                        ACCESS: Read w/Fileman
FIELD NUMBER: 11                        FIELD NAME: ORIGINAL REQUEST CHANGED
  LOCATION: 0;11                        ACCESS: Read w/Fileman
FIELD NUMBER: 12                        FIELD NAME: PRE-OP SCHEDULED DATE/TIME
  LOCATION: 0;12                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: PREGNANT
  LOCATION: 0;13                        ACCESS: Read w/Fileman
FIELD NUMBER: 14                        FIELD NAME: REQUESTING PHYSICIAL
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 15                        FIELD NAME: USER ENTERING REQUEST 
  LOCATION: 0;15                        ACCESS: Read w/Fileman
FIELD NUMBER: 16                        FIELD NAME: REQUEST ENTERED DATE/TIME
  LOCATION: 0;16                        ACCESS: Read w/Fileman
FIELD NUMBER: 17                        FIELD NAME: LAST ACTIVITY DATE/TIME
  LOCATION: 0;17                        ACCESS: Read w/Fileman
FIELD NUMBER: 18                        FIELD NAME: PAST VISIT DATE/TIME
  LOCATION: 0;18                        ACCESS: Read w/Fileman
FIELD NUMBER: 19                        FIELD NAME: MODE OF TRANSPORT
  LOCATION: 0;19                        ACCESS: Read w/Fileman
FIELD NUMBER: 20                        FIELD NAME: IMAGING LOCATION
  LOCATION: 0;20                        ACCESS: Read w/Fileman
FIELD NUMBER: 21
  FIELD NAME: DATE DESIRED (not guaranteed)
  LOCATION: 0;21                        ACCESS: Read w/Fileman
FIELD NUMBER: 22                        FIELD NAME: REQUESTING LOCATION
  LOCATION: 0;22                        ACCESS: Read w/Fileman
FIELD NUMBER: 23                        FIELD NAME: SCHEDULED DATE
  LOCATION: 0;23                        ACCESS: Read w/Fileman
FIELD NUMBER: 24                        FIELD NAME: ISOLATION PROCEDURES
  LOCATION: 0;24                        ACCESS: Read w/Fileman
FIELD NUMBER: 26
  FIELD NAME: NATURE OF(NEW) ORDER ACTIVITY
  LOCATION: 0;26                        ACCESS: Read w/Fileman
FIELD NUMBER: 27                        FIELD NAME: CANCEL DESCRIPTION
  LOCATION: 0;27                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RAO(75.1,D0,.1
FIELD NUMBER: 1.1                       FIELD NAME: REASON FOR STUDY
  LOCATION: .1;1                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: RAO(75.1,D0,1
FIELD NUMBER: 25                        FIELD NAME: HOLD DESCRIPTION
  LOCATION: 1;0                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RAO(75.1,D0,'R'
FIELD NUMBER: 9.5                       FIELD NAME: RESEARCH SOURCE
  LOCATION: R;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RAO(75.1,D0,'H'
FIELD NUMBER: 400                       FIELD NAME: CLINICAL HISTORY FOR EXAM
  LOCATION: H;0                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: RAO(75.1,D0,'M',D1,0
FIELD NUMBER: .01                       FIELD NAME: PROCEDURE MODIFIERS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: RAO(75.1,D0,'T',D1,0
FIELD NUMBER: .01                       FIELD NAME: STATUS CHANGE DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: NEW STATUS
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: COMPUTER USER
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: REASON
  LOCATION: 0;4                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RAO(75.1,'AO'
GLOBAL REFERENCE: RAO(75.1,'AS'
GLOBAL REFERENCE: RAO(75.1,'B'
GLOBAL REFERENCE: RAO(75.1,'BDD'
 GENERAL DESCRIPTION:   This file contains the Radiology order information.
 This is different and contains information not found in the Order file (#100). 
 
 Read only from file 75.1 
  STATUS: Active
KEYWORDS: DSS
KEYWORDS: OTM
SUBSCRIBING PACKAGE: DSS OTM RADIOLOGY
 SUBSCRIBING DETAILS:   Added 1/3/25 effective with Patch DSSU*1.1*6 The DSS
 OTM RADIOLOGY package provides a user-friendly methodology as part of the VA
 initiative to enhance its digital transformation efforts.  The DSS OTM
 RADIOLOGY package offers clear visibility into the status of exam and allows 
 Protocolling of exams.  This package also gives quick access to many VistA
 functions from the RADIOLOGY/NUCLEAR MEDICING package.  

NUMBER: 7514                            IA #: 7514
  FILE NUMBER: 75.1                     DATE CREATED: JAN 16, 2025
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: File
  NAME: RADIOLOGY ORDER INFORMATION (WRITE)
GLOBAL REFERENCE: RAO(75.1,D0,0
 GLOBAL DESCRIPTION:   This file contains the Radiology order information. This
 is different and contains information not found in the Order file (#100). 
 Write to file 75.1 
  STATUS: Pending
SUBSCRIBING PACKAGE: DSS OTM RADIOLOGY

NUMBER: 7515                            IA #: 7515
  FILE NUMBER: 70                       GLOBAL ROOT: RADPT(
  DATE CREATED: JAN 16, 2025
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: File
  NAME: RADIOLOGY PATIENT FILE (READ)   ID: RADPT(
 GENERAL DESCRIPTION:   
   RADPT file #70, is the RAD/NUC MED Patient file. In order to interface 
   the VistA Radiology system with any external system, it is necessary 
   to be able to read from to this file.  
  STATUS: Pending
SUBSCRIBING PACKAGE: DSS OTM RADIOLOGY
 SUBSCRIBING DETAILS:   The DSS OTM RADIOLOGY package provides a user-friendly
 methodology as part of the VA initiative to enhance its digital transformation
 efforts.  The DSS OTM RADIOLOGY package offers clear visibility into the
 status of exam and allows Protocolling of exams.  This package also gives
 quick access to many VistA functions from the RADIOLOGY/NUCLEAR MEDICING 
 package.  

NUMBER: 7516                            IA #: 7516
  FILE NUMBER: 70                       GLOBAL ROOT: RADPT(
  DATE CREATED: JAN 16, 2025
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: File
  NAME: RADIOLOGY PATIENT FILE (WRITE)  ID: RADPT(
  STATUS: Pending
SUBSCRIBING PACKAGE: DSS OTM RADIOLOGY

NUMBER: 7517                            IA #: 7517
  DATE CREATED: FEB 24, 2025            CUSTODIAL PACKAGE: PROBLEM LIST
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: GMPLSPECAUTH SPECAUTHDEF
  REMOTE PROCEDURE: GMPLSPECAUTH SPECAUTHDEF
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call this remote procedure to receive a Problem's Special Authorities rules
 and values.  
  STATUS: Active
KEYWORDS: SPECIAL AUTHORITY
KEYWORDS: ENVIRONMENTAL
KEYWORDS: INDICATORS
KEYWORDS: SPECIAL AUTHORITIES
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 02/24/25, effective with patches GMPL*2.0*58 and
 OR*3.0*508. The OERR package will be subscribing to this routine to return all
 the valid authorities and their characteristics that pertain to the problem.  
  DATE ACTIVATED: MAR 12, 2025

NUMBER: 7518                            IA #: 7518
  DATE CREATED: FEB 24, 2025            CUSTODIAL PACKAGE: PROBLEM LIST
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  DBIC APPROVAL STATUS: APPROVED        NAME: GMPLSPECAUTH SAFORPROBLEMS
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call this remote procedure to receive a Problem's Special Authority (SA)
 user answered values and save to the ORDER file (#100) SPECIAL AUTHORITIES
 multiple file (#100.112).  
  
 REMOTE PROCEDURE: Returns an array with JSON elements string for Special
 Authorities (SA).  
  
   Following are the details of the GMPLSPECAUTH SAFORPROBLEMS: 
    
 NAME: GMPLSPECAUTH SAFORPROBLEMS        TAG: SAFORPROBLEMS 
  ROUTINE: GMPLSPECAUTH                 RETURN VALUE TYPE: ARRAY 
  DESCRIPTION:   
  Handle RPC calls and retrieves Special Authorities per patient Problem.  
 INPUT PARAMETER: JSONIN                 PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 
  DESCRIPTION:   
   JSON string passed back for order(s) to save SA answers.  
     
    JSON elements: 
      patientId       = patient unique numeric DFN 
  RETURN PARAMETER DESCRIPTION:   
  JSON return string elements: 
     
    "success" = was value saved?  true/false 
     
    Example: 
     
    {
        "success": true 
    }
  STATUS: Active
KEYWORDS: SPECIAL AUTHORITY
KEYWORDS: ENVIRONMENTAL
KEYWORDS: INDICATORS
KEYWORDS: SPECIAL AUTHORITIES
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAR 12, 2025

NUMBER: 7519                            IA #: 7519
  DATE CREATED: FEB 24, 2025
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: PXSPECAUTH SPECAUTHSTRUCT
  REMOTE PROCEDURE: PXSPECAUTH SPECAUTHSTRUCT
 GENERAL DESCRIPTION:   Patch PX*1.0*244 will release a new SPECIAL AUTHORITIES
 FILE #(820) and a routine of API calls to retrieve information about all the
 special authorities. This Controlled ICR allows subscribers to call these APIs
 to retrieve information from the new file. 
     
 Special Authorities file will define all the previously known as Environmental
 Indicators in a file to allow future growth and to help minimize elaborate
 software enhancements when needing to add a new authority.  This file contains
 the business rules behind each authority, e.g. Name, code, disabled,
 abbreviation, sequence, default, disabled, visible, Package - disabled?,
 Linked authority behavior rules, Linked Authority, When value is, Actions to
 take.  
     
 See individual Component Entry for description and examples of call and 
 returned results.  
  STATUS: Active
KEYWORDS: SPECIAL AUTHORITY
KEYWORDS: SPECIAL AUTHORITIES
KEYWORDS: ENVIRONMENTAL
KEYWORDS: INICATORS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/14/25, effective with patches PX*1.0*244 and
 OR*3.0*508 The OERR package will be subsribing to this routine to return all
 the valid authorities and their characteristics.  

NUMBER: 7520                            IA #: 7520
  DATE CREATED: FEB 27, 2025
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RAMAGRP1                     NAME: RADIOLOGY EXAM ORDER API
  ID: RAMAGRP1
 GENERAL DESCRIPTION:   This ICR provides APIs for the Radiology exam process.  
 It includes logic to create a new order, register an exam and complete the
 exam.  
  STATUS: Pending
KEYWORDS: MEDICOM
COMPONENT/ENTRY POINT: ORDER
 COMPONENT DESCRIPTION:   Order a RADIOLOGY Exam 
VARIABLES: RARESULT                     TYPE: Output
  VARIABLE SEQUENCE NUMBER: 1
 VARIABLES DESCRIPTION:   New Order info returned:  A negative value of the
 first indicates an error (see the RPCSTK^RAERR01 for more details). Otherwise,
 the Results[0] contains IEN of the new order in the RAD/NUC MED ORDERS file
 (#75.1).  
VARIABLES: RADFN                        TYPE: Input
  VARIABLE SEQUENCE NUMBER: 2
 VARIABLES DESCRIPTION:   Patient IEN (DFN) 
VARIABLES: RAMLC                        TYPE: Input
  VARIABLE SEQUENCE NUMBER: 3
 VARIABLES DESCRIPTION:   IEN of imaging location, file #79.1 
VARIABLES: RAPROC                       TYPE: Input
  VARIABLE SEQUENCE NUMBER: 4
 VARIABLES DESCRIPTION:   IEN of procedure, file #71 
VARIABLES: REQDTE                       TYPE: Input
  VARIABLE SEQUENCE NUMBER: 5
 VARIABLES DESCRIPTION:   date requested 
VARIABLES: RACAT                        TYPE: Input
  VARIABLE SEQUENCE NUMBER: 6
 VARIABLES DESCRIPTION:   CATEGORY OF EXAM field #4, file #75.1 
VARIABLES: REQLOC                       TYPE: Input
  VARIABLE SEQUENCE NUMBER: 7
 VARIABLES DESCRIPTION:   IEN of requesting location, file #44 
VARIABLES: REQPHYS                      TYPE: Input
  VARIABLE SEQUENCE NUMBER: 8
 VARIABLES DESCRIPTION:   IEN of requesting physician, file #200 
VARIABLES: REASON                       TYPE: Input
  VARIABLE SEQUENCE NUMBER: 9
 VARIABLES DESCRIPTION:   REASON FOR STUDY field #1.1, file #75.1 
COMPONENT/ENTRY POINT: COMPLETE
 COMPONENT DESCRIPTION:   This component completes the Radiology Exam. It also
 sends required HL7 messages, sends changed order control "XX" to CPRS, but
 does not send VistA alerts regarding the exam status change.  
VARIABLES: RARESULT                     TYPE: Output
  VARIABLE SEQUENCE NUMBER: 1
 VARIABLES DESCRIPTION:   Registered Order information returned:  A negative
 value of the first indicates an error (see the RPCSTK^RAERR01 for more
 details). Otherwise, 0 is returned in the RARESULT(0).  
VARIABLES: RACASE                       TYPE: Input
  VARIABLE SEQUENCE NUMBER: 2
 VARIABLES DESCRIPTION:   Exam/case identifiers:                            
 -^01: IEN of the patient in the file #70   (RADFN) -^02: IEN in the REGISTERED
 EXAMS multiple (RADTI) -^03: IEN in the EXAMINATIONS multiple     (RACNI) 
VARIABLES: RAMSC                        TYPE: Input
  VARIABLE SEQUENCE NUMBER: 3
 VARIABLES DESCRIPTION:   List of this items that define miscellaneous/optional 
 order parameters.  
COMPONENT/ENTRY POINT: REGISTER
 COMPONENT DESCRIPTION:   Registers the RADIOLOGY Exam 
VARIABLES: RARESULT                     TYPE: Output
  VARIABLE SEQUENCE NUMBER: 1
 VARIABLES DESCRIPTION:   Registered Order info returned  A negative value of
 the first indicates an error (see the RPCSTK^RAERR01 for more details).
 Otherwise, 0 is returned in the RARESULT(0).  
VARIABLES: RAOIFN                       TYPE: Input
  VARIABLE SEQUENCE NUMBER: 2
 VARIABLES DESCRIPTION:   IEN in file #75.1 
VARIABLES: EXMDTE                       TYPE: Input
  VARIABLE SEQUENCE NUMBER: 3
 VARIABLES DESCRIPTION:   Exam date -YYYMMDDHHMM format - 202501171245 
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES
 SUBSCRIBING DETAILS:   Added 3/7/2025 effective with Patch MECH 1.0, a Class 2 
 product, requests access to call the routine RAMAGRP1 to create a Radiology
 order, register the Radiology exam, and completes the Radiology exam.  The
 Medicom ImageX app processes HL7 messages about imaging studies performed in
 the community that might not be entered through VistA.  

NUMBER: 7521                            IA #: 7521
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123,
  DATE CREATED: MAR 11, 2025
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Controlled Subscription        TYPE: File
  NAME: CONSULT PROCEDURE ORDER         ID: GMR(123,
GLOBAL REFERENCE: GMR(123,D0
FIELD NUMBER: .02                       FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .05                       FIELD NAME: ORDERING FACILITY
  LOCATION: 0;21                        ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TO SERVICE
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DATE OF REQUEST
  LOCATION: 0;7                         ACCESS: Read w/Fileman
FIELD NUMBER: 20                        FIELD NAME: REASON FOR REQUEST
  LOCATION: 20;0                        ACCESS: Read w/Fileman
GLOBAL REFERENCE: GMR(123,D0,40
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME OF ACTION ENTRY
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3
  FIELD NAME: WHO'S RESPONSIBLE FOR ACTIVITY
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: WHO ENTERED ACTIVITY
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: PREVIOUSLY ASSIGNED TO
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: GMR(123,D0,40,'B'
 GENERAL DESCRIPTION:   Provide access to the order information in
 REQUEST/CONSULTATION File #123.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMR(123
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/22/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires read access to File
 123, fields PATIENT NAME(#.02), ORDERING FACILITY(#.05), TO SERVICE(#1), DATE
 OF REQUEST(#3), REASON FOR REQUEST(#20), DATE/TIME OF ACTION ENTRY(123.02;.01)
 WHO'S RESPONSIBLE FOR ACTIVITY(123.02;3), WHO ENTERED ACTIVITY (123.02;4) and
 PREVIOUSLY ASSIGNED TO(123.02;7) 

NUMBER: 7522                            IA #: 7522
  DATE CREATED: MAR 12, 2025
  CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RAMAGRP2                     NAME: RADIOLOGY EXAM STATUS REQUIREMENTS
  ID: RAMAGRP2
 GENERAL DESCRIPTION:   This ICR provides APIs for the Radiology exam process. 
 It includes logic to register an exam, create a new order, register an exam,
 and complete the exam.  
  STATUS: Active
KEYWORDS: MEDICOM
COMPONENT/ENTRY POINT: EXSTREQ
 COMPONENT DESCRIPTION:   Radiology Exam status requirements 
VARIABLES: RACTION                      TYPE: Input
 VARIABLES DESCRIPTION:   Action that is going to be performed on an exam/case
 record (single character):  C  Complete 
VARIABLES: RAIMGTYI                     TYPE: Input
 VARIABLES DESCRIPTION:   IEN of imaging type, file #79.2 
VARIABLES: RARESULT                     TYPE: Input
 VARIABLES DESCRIPTION:   Exam status requirements info returned: A negative
 value of the first piece indicates an error (see the RPCSTK^RAERR01 for more
 details). Otherwise, exam status requirements are returned in the RARESULT(0). 
 
VARIABLES:  
SUBSCRIBING PACKAGE: MEDICOM TECHNOLOGIES

NUMBER: 7523                            IA #: 7523
  DATE CREATED: MAR 17, 2025            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMFNFT
  NAME: CLINICAL REMINDER TEXT UTILITY API FOR TEXT WITH OBJECTS
  ID: PXRMFNFT
 GENERAL DESCRIPTION:   OE/RR request the ability to display word processing
 field that contains a TIU Patient Data Object in a formatted output.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRM
KEYWORDS: OR
KEYWORDS: TIU
COMPONENT/ENTRY POINT: FNFTXTO
VARIABLES: INDENT                       TYPE: Input
 VARIABLES DESCRIPTION:   This is a number greater than 0. The value set the
 character number where the output start to write out on each line.  
VARIABLES: NIN                          TYPE: Input
 VARIABLES DESCRIPTION:   This is the number of lines of text pass into the
 API.  
VARIABLES: TEXTIN                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the input array that contains the unformatted
 text. The format is TEXTIN(n)="TEXT" 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient dfn 
VARIABLES: VSTR                         TYPE: Input
 VARIABLES DESCRIPTION:   This the Visit string should be "" for most scenario,
 should only be set if loading the object is needed to be based off a specific
 visit.  
VARIABLES: NOUT                         TYPE: Output
 VARIABLES DESCRIPTION:   This is the number of lines returned in the formatted
 text array.  
VARIABLES: TEXTOUT                      TYPE: Output
 VARIABLES DESCRIPTION:   The output array containing the formatted text.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAR 17, 2025

NUMBER: 7524                            IA #: 7524
  DATE CREATED: MAR 17, 2025
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSPGXOR
  NAME: PDM ACCESS FOR PGX ORDER CHECKS VIA CPRS
  ID: PSSPGXOR
 GENERAL DESCRIPTION:   With the implementation of Pharmacogenomic (PGx) order
 checks in MOCHA 3.0, the Computerized Patient Record System (CPRS) will use
 this API to retrieve PGx order check data from both the Health Data Repository
 (HDR) and First Data Bank (FDB) during the medication order entry process
 using a specified internal entry number (IEN) from the DRUG (#50) file for a 
 selected patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PGX(PSSORPT,PSSOLIST,PSSORPKG,PSSORDRG,PSSORDNM,PSSORSUP)
 COMPONENT DESCRIPTION:   This entry point will be used by CPRS to retrieve PGx
 order check data during the medication ordering process.  
VARIABLES: PSSORPT                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the PATIENT
 (#2) file for a selected patient.  
VARIABLES: PSSOLIST                     TYPE: Input
 VARIABLES DESCRIPTION:   This is a string literal used for the sorting and
 processing of TMP globals created by the PSSPGXOR routine.  
VARIABLES: PSSORPKG                     TYPE: Input
 VARIABLES DESCRIPTION:   This parameter serves as a flag to indicate what CPRS
 dialog is calling the linetag: "I" for Inpatient, "O" for Outpatient. The "I"
 is passed in for Inpatient orders and IV orders, the "O" is passed in for
 Outpatient orders and Non-VA orders.  
VARIABLES: PSSORDRG                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number from the DRUG (#50)
 file for the selected orderable item.  
VARIABLES: PSSORDNM                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the associated order number for the
 medication order being processed by CPRS (optional).  
VARIABLES: PSSORSUP                     TYPE: Input
 VARIABLES DESCRIPTION:   This parameter helps determine suppression logic for
 PGx Order Checks in CPRS: "M" to suppress Moderate checks, "H" to suppress
 High checks, and "N" for no suppression.  
COMPONENT/ENTRY POINT: $$BDA(PSSBDAOI,PSSGDAPK)
 COMPONENT DESCRIPTION:   The BDA component processes Free Text dosages in CPRS
 by evaluating drugs linked to an Orderable Item. It identifies the drug that
 offers the most comprehensive pharmacogenomic order check information and
 returns it to the provider.  
VARIABLES: PSSBDAOI                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the internal entry number for a selected item
 from the PHARMACY ORDERERABLE ITEM (#50.7) file.  
VARIABLES: PSSBDAPK                     TYPE: Input
 VARIABLES DESCRIPTION:   This parameter serves as a flag to indicate what CPRS
 dialog is calling the linetag.  
  
 O = Outpatient, U = Unit Dose, I = IV, and X = Non-VA Med.  
VARIABLES: $$BDA                        TYPE: Output
 VARIABLES DESCRIPTION:   IEN^GCNSEQNO^VUID 
  
 Piece 1 is the internal entry number from the DRUG (#50) file.  
  
 Piece 2 is the GCNSEQNO (#11) field from the VA PRODUCT (#50.68) file (if the
 drug is matched to a VA PRODUCT (#50.68) file entry).  
  
 Piece 3 is the VUID (#99.99) field from the VA PRODUCT (#50.68) file (if the
 drug is matched to a VA PRODUCT (#50.68) file entry).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: MAR 20, 2025

NUMBER: 7525                            IA #: 7525
  DATE CREATED: MAR 18, 2025            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Other
  DBIC APPROVAL STATUS: APPROVED
  NAME: ACCESS TO VETERAN THIRD PARTY CHARGE REPORT
 GENERAL DESCRIPTION:   Allow access to the Veteran Third Party Charge Report
 [IB TP VETERAN CHRG RPT].  
  STATUS: Active
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   AR will access the option through the following menus: 
  - DMC Referral Menu 
  - Reports Menu for Accounts Receivable 
  DATE ACTIVATED: MAR 20, 2025

NUMBER: 7526                            IA #: 7526
  DATE CREATED: MAR 19, 2025
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSSPGX
  NAME: PGX GENETIC TEST RESULTS FROM HDR FOR PGX ORDER CHECKS
  ID: PSSPGX
 GENERAL DESCRIPTION:   Pharmacogenomics findings for Inpatient Medications,
 Outpatient Pharmacy, and Order Entry/Results Reporting (CPRS).  
  
 For full input and output details, see the VistA to MOCHA Version 3.0 
 Interface Document, located under the "Pharm: Data Management (PDM)" section
 within the "Clinical" section of the VA Software Document Library (VDL).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PGXOC(PSSBASE,PSSDFN,PSSDRUGS,PSSOUT,PSSPGXPK)
 COMPONENT DESCRIPTION:   This entry point will be used to retrieve PGx genetic
 test interpretation results from the Health Data Repository (HDR) and returns
 Pharmacogenomic (PGx) order check information during the medication ordering
 process.  
VARIABLES: PSSBASE                      TYPE: Input
 VARIABLES DESCRIPTION:   This is used to identify the calling package
 (Inpatient Medications = PSJPGX, Outpatient Pharmacy = PSOPGX, or CPRS =
 ORPGX). It is also used as a subscript for PGx data returned in a TMP global.  
VARIABLES: PSSDFN                       TYPE: Input
 VARIABLES DESCRIPTION:   This is the patient's data file number (DFN).  
VARIABLES: PSSDRUGS                     TYPE: Input
 VARIABLES DESCRIPTION:   This is a dispense drug array populated by the DRUG
 (#50) file.  
VARIABLES: PSSOUT                       TYPE: Output
 VARIABLES DESCRIPTION:   1 for successful (results are stored in
 ^TMP($J,PSSBASE)) 
  
 -1^error message (ex: -1^ERROR #6059: Unable to open TCP/IP socket...) 
VARIABLES: PSSPGXPK                     TYPE: Input
 VARIABLES DESCRIPTION:   This parameter is either an "I" (IV or Inpatient) or
 "O" (Outpatient or NON VA Med) for the dialog in CPRS and is used for PGx
 profile suppression logic.  
SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
  DATE ACTIVATED: APR 21, 2025

NUMBER: 7527                            IA #: 7527
  DATE CREATED: MAR 19, 2025            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PSOOCPGX
  NAME: PSO MED ORDER PROFILE FOR PGX SUPPRESSION
  ID: PSOOCPGX
 GENERAL DESCRIPTION:   Builds a profile of an Outpatient's medication orders
 to be used for PGx Order Checks suppression logic.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PSOOCPGX
COMPONENT/ENTRY POINT: BLD(PSOXDFN,PSOPGXS)
 COMPONENT DESCRIPTION:   This API builds a list of active and recently expired
 Outpatient orders that are used in the suppression logic for Pharmacogenomic
 (PGx) order checks.  
VARIABLES: PSOXDFN                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the Outpatient's data file number (DFN).  
VARIABLES: PSOPGXS                      TYPE: Input
 VARIABLES DESCRIPTION:   This is the amount of days to go back into the
 Outpatient's active medication record. If no value is passed, a default value
 of 120 days is set.  
VARIABLES: TMP($J,"ORDERS",n)           TYPE: Output
 VARIABLES DESCRIPTION:   ^TMP(XXX,"ORDERS",1)= 
 "CNXXX^XXXAXXXX^DRUG#1^XXXXX^IENP;O" 
  
 ^TMP(XXX,"ORDERS",2)= "CNXXX^XXXAXXXX^DRUG#2^XXXXX^IENR;O" 
  
                            
 - 1st piece: VA CLASSIFICATION (#2) from DRUG (#50) file 
  
 - 2nd piece: NATIONAL DRUG FILE ENTRY (#20) from DRUG (#50) file"_A_"PSNDF VA
 PRODUCT NAME ENTRY (#22) from DRUG (#50) file 
  
 - 3rd piece: GENERIC NAME (#.01) from DRUG (#50) file 
  
 - 4th piece: PLACER NUMBER (#.01) from PENDING OUTPATIENT ORDERS (#52.41) file
 *OR* PLACER ORDER # (#39.3) from PRESCRIPTION (#52) file 
  
 - 5th piece: IEN_"P;O" or "R;O" P;O = IEN from PENDING OUTPATIENT ORDERS
 (#52.41) file R;O = IEN from PRESCRIPTION (#52) file 
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  DATE ACTIVATED: APR 21, 2025

NUMBER: 7528                            IA #: 7528
  FILE NUMBER: 100.02                   GLOBAL ROOT: ORD(100.02
  DATE CREATED: MAR 24, 2025
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: NATURE OF ORDER FILE ACCESS     ID: ORD(100.02
 GENERAL DESCRIPTION:   sSTEST4S Test 3 TEST 4 This a test 
  STATUS: Pending                       DURATION: Till Otherwise Agreed

NUMBER: 7529                            IA #: 7529
  FILE NUMBER: 100.02                   GLOBAL ROOT: ORD(100.02
  DATE CREATED: MAR 24, 2025
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: NATURE OF ORDER FILE ACCESS     ID: ORD(100.02
GLOBAL REFERENCE: ORD(100.02
FIELD NUMBER: Multiple                  FIELD NAME: All
  ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Retrieves all data in global ORD(100.02 or Fileman
 100.02 custodial package ORDER ENTRY/RESULTS REPORTING via VETRANS DATA
 INTERGRATION AND FEDERATION VDI 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 7530                            IA #: 7530
  FILE NUMBER: 31                       GLOBAL ROOT: DIC(31,
  DATE CREATED: MAR 25, 2025            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Add New Disability Conditions
  ID: DIC(31,
GLOBAL REFERENCE: DIC(31,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DX CODE
  LOCATION: 0;3                         ACCESS: Write w/Fileman
 GENERAL DESCRIPTION:   This ICR allows new diagnosis codes (DX CODE) and NAME
 fields to be added to the Disability Condition (#31) file.  Implementation of
 patch DG*5.3*1138, provides a mechanism to update the Disability Conditions 
 (#31) file.  When disability conditions (NAME and DX CODE) are encountered
 while parsing inbound HL7 messages, but the codes are missing from the
 Disability Conditions (#31) file, then Registration is authorized to add those
 disability conditions and diagnosis codes to the Disability Conditions (#31)
 file. 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: Disability Conditions
KEYWORDS: Diagnosis Codes
SUBSCRIBING PACKAGE: REGISTRATION
  DATE ACTIVATED: MAR 25, 2025

NUMBER: 7531                            IA #: 7531
  FILE NUMBER: 100.02                   GLOBAL ROOT: ORD(100.02
  DATE CREATED: MAR 26, 2025
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: Private                         ID: ORD(100.02
GLOBAL REFERENCE: ORD(100.02,IEN
FIELD NUMBER: ALL                       FIELD NAME: ALL
  LOCATION: ALL                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Retrieves all data in global ORD(100.02 or Fileman
 100.02 custodial package ORDER ENTRY/RESULTS REPORTING via VETRANS DATA
 INTERGRATION AND FEDERATION VDI 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Calling custodail package ORDER ENTRY/RESULTS REPORTING
 to retrieve all data on Global ORD(100.02 or Fileman 100.02 

NUMBER: 7532                            IA #: 7532
  DATE CREATED: MAR 31, 2025            CUSTODIAL PACKAGE: REGISTRATION
  NAME: WITHDRAWN ICR                   STATUS: Withdrawn
KEYWORDS: WITHDRAWN

NUMBER: 7533                            IA #: 7533
  FILE NUMBER: 59                       GLOBAL ROOT: PS(59
  DATE CREATED: MAR 31, 2025            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  NAME: VCRS                            ID: PS(59
GLOBAL REFERENCE: Multiple
FIELD NUMBER: ALL                       FIELD NAME: ALL
  LOCATION: ALL                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   VDIF API call to retrive all field data from outpatient
 site file 59 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: VDI
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION

NUMBER: 7534                            IA #: 7534
  FILE NUMBER: 57.23                    GLOBAL ROOT: PS(57.23
  DATE CREATED: APR 11, 2025            CUSTODIAL PACKAGE: NATIONAL DRUG FILE
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: OERR VIEW INSTALL VERSION IN FILE 57.23
  ID: PS(57.23
GLOBAL REFERENCE: PS(57.23,D0,0
FIELD NUMBER: 2                         FIELD NAME: INSTALL VERSION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the current version number of the
 last successful Pharmacy Product System - National (PPS-N) Update file that
 was installed.  For example if the last PPS-N Update file installed was 
 PPS_25PRV_26NEW.DAT, this field would contain 26.  
 GENERAL DESCRIPTION:   ORDER ENTRY/RESULTS REPORTING (OERR) wants to access
 the INSTALL VERSION (#2) field of the PPS-N UPDATE CONTROL (#57.23) file as
 part of its Order Check changes in patch OR*3*630. OERR is adding a new ORDER
 CHECK NATIONAL TERM (#860.9) entry to store the VA PRODUCT (#50.68) file
 entries containing a Metformin ingredient. To facilitate maintenance of this 
 National Term entry, OERR wants to automate this process. By utilizing a 
 scheduled task, OERR wishes to inquire to the INSTALL VERSION of the PPS-N 
 UPDATE CONTROL file in order to know when updates have occurred in the drug
 files and thus OERR can run a process to search for new VA PRODUCT entries
 with a Metformin ingredient to add to the National Term.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: INSTALL VERSION
KEYWORDS: PPS-N UPDATE CONTROL
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: APR 11, 2025

NUMBER: 7535                            IA #: 7535
  FILE NUMBER: 123.5                    GLOBAL ROOT: GMR(123.5,
  DATE CREATED: APR 14, 2025
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Access REQUEST SERVICES file (#123.5)
  ID: GMR(123.5,
GLOBAL REFERENCE: GMR(123.5,DA,0
FIELD NUMBER: .01                       FIELD NAME: SERVICE NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: SERVICE USAGE
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 133                       FIELD NAME: IFC REMOTE NAME
  LOCATION: IFC;2                       ACCESS: Read w/Fileman
FIELD NUMBER: 134,.01                   FIELD NAME: IFC SENDING FACILITY
  LOCATION: IFCS,DA(1),0;1              ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Effective with patch RMPR*3*217, when a Prosthetics
 order is received at a converted VistA from CERNER, the service name is
 extracted from the 4th field of the OBR segment (OBR-4) and needs to be
 validated against the REQUEST SERVICES file (#123.5).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   Patch RMPR*3*217 implements a Prosthetics orders
 interface separate from the IFC interface to receive and process orders
 entered in Cerner.  To ensure the accuracy of the incoming order, the patch
 must validate the service name in OBR-4 against the REQUEST SERVICES file
 (#123.5).  
  DATE ACTIVATED: APR 21, 2025

NUMBER: 7536                            IA #: 7536
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123,
  DATE CREATED: APR 15, 2025
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: Populate REQUEST/CONSULTATION file (#123)
  ID: GMR(123,
GLOBAL REFERENCE: GMR(123,DA,
FIELD NUMBER: .01                       FIELD NAME: FILE ENTRY DATE
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05                       FIELD NAME: ORDERING FACILITY
  LOCATION: 0;21                        ACCESS: Write w/Fileman
FIELD NUMBER: .06                       FIELD NAME: REMOTE CONSULT FILE ENTRY
  LOCATION: 0;22                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .1                        FIELD NAME: DISPLAY TEXT OF ITEM ORDERED
  LOCATION: 1.11;1                      ACCESS: Write w/Fileman
FIELD NUMBER: .125                      FIELD NAME: IFC ROLE
  LOCATION: 12;5                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: .126                      FIELD NAME: REMOTE ORDERING PROVIDER
  LOCATION: 12;6                        ACCESS: Write w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TO SERVICE
  LOCATION: 0;5                         ACCESS: Write w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DATE OF REQUEST
  LOCATION: 0;7                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: URGENCY
  LOCATION: 0;9                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: PLACE OF CONSULTATION
  LOCATION: 0;10                        ACCESS: Write w/Fileman
FIELD NUMBER: 8                         FIELD NAME: CPRS STATUS
  LOCATION: 0;12                        ACCESS: Write w/Fileman
FIELD NUMBER: 9                         FIELD NAME: LAST ACTION TAKEN
  LOCATION: 0;13                        ACCESS: Write w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SENDING PROVIDER
  LOCATION: 0;14                        ACCESS: Read w/Fileman
FIELD NUMBER: 13                        FIELD NAME: REQUEST TYPE
  LOCATION: 0;17                        ACCESS: Write w/Fileman
FIELD NUMBER: 14
  FIELD NAME: SERVICE RENDERED AS IN OR OUT
  LOCATION: 0;18                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 15                        FIELD NAME: SIGNIFICANT FINDINGS
  LOCATION: 0;19                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17                        FIELD NAME: CLINCALLY INDICATED DATE
  LOCATION: 0;24                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 20                        FIELD NAME: REASON FOR REQUEST
  LOCATION: 20;0                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 30                        FIELD NAME: PROVISIONAL DIAGNOSIS
  LOCATION: 30;1                        ACCESS: Write w/Fileman
FIELD NUMBER: 30.1                      FIELD NAME: PROVISIONAL DIAGNOSIS CODE
  LOCATION: 30;2                        ACCESS: Write w/Fileman
FIELD NUMBER: 30.2                      FIELD NAME: PROVISIONAL DIAGNOSIS DATE
  LOCATION: 30;3                        ACCESS: Write w/Fileman
FIELD NUMBER: 30.3                      FIELD NAME: PROVISIONAL DIAGNOSIS SYSTEM
  LOCATION: 30;4                        ACCESS: Write w/Fileman
FIELD NUMBER: 80                        FIELD NAME: UNIQUE CONSULT ID
  LOCATION: UCID;1                      ACCESS: Write w/Fileman
FIELD NUMBER: 502                       FIELD NAME: Patient Account Number
  LOCATION: CERNER;3                    ACCESS: Both R/W w/Fileman
FIELD NUMBER: 507                       FIELD NAME: Cerner Ordering Provider
  LOCATION: CERNER1;E1,255              ACCESS: Both R/W w/Fileman
FIELD NUMBER: 508                       FIELD NAME: Cerner Placer Field 2
  LOCATION: CERNER2;E1,255              ACCESS: Both R/W w/Fileman
FIELD NUMBER: 511                       FIELD NAME: OPT IN FOR FINAL STATUS
  LOCATION: CERNER;11                   ACCESS: Write w/Fileman
FIELD NUMBER: 512                       FIELD NAME: PERFORMED DATE/TIME
  LOCATION: CERNER;12                   ACCESS: Write w/Fileman
GLOBAL REFERENCE: GMR(123,DA,40,
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME OF ACTION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .21                       FIELD NAME: REMOTE ENTERING PERSON
  LOCATION: 2;1                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: .22                       FIELD NAME: REMOTE RESPONSIBLE PERSON
  LOCATION: 2;2                         ACCESS: Write w/Fileman
FIELD NUMBER: .23                       FIELD NAME: REMOTE ACTIVITY TIME ZONE
  LOCATION: 2;3                         ACCESS: Write w/Fileman
FIELD NUMBER: .25                       FIELD NAME: REMOTE DATE/TIME OF FILING
  LOCATION: 2;5                         ACCESS: Write w/Fileman
FIELD NUMBER: .32                       FIELD NAME: SENT FROM CERNER SITE
  LOCATION: 3;2                         ACCESS: Write w/Fileman
FIELD NUMBER: .33                       FIELD NAME: CERNER FACILITY SENDING
  LOCATION: 3;3                         ACCESS: Write w/Fileman
FIELD NUMBER: 1                         FIELD NAME: ACTIVITY
  LOCATION: 0;2                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: DATE/TIME OF ACTUAL ACTIVITY
  LOCATION: 0;3                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3
  FIELD NAME: WHO'S RESPONSIBLE FOR ACTIVITY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: WHO ENTERED ACTIVITY
  LOCATION: 0;5                         ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: COMMENT
  LOCATION: 1;0                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: GMR(123,'AIFC',
 GLOBAL DESCRIPTION:   Global read of this cross-reference required.  
 GENERAL DESCRIPTION:   Patch RMPR*3*217 implements a Prosthetics orders
 interface separate from the IFC interface to receive and process orders
 entered in Cerner.  VistA supports Prosthetics operations on converted sites. 
 The new interface creates the files used by VistA Prosthetics and its GUI
 counterparts (e.g., Advanced Prosthetics Acquisition Tool (APAT)).  These
 files include the REQUEST/CONSULTATION file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   Effective with patch RMPR*3*217, when a Prosthetics
 order is received at a converted VistA from CERNER, the new interface creates
 the files needed by legacy VistA and its GUI counterparts. 
  DATE ACTIVATED: APR 30, 2025

NUMBER: 7537                            IA #: 7537
  DATE CREATED: APR 15, 2025            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMDLLB
  NAME: GETLSEQ                         ID: PXRMDLLB
 GENERAL DESCRIPTION:   Returns a list of sequences that should be updated when
 the LINK is applied to the Reminder Dialog.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PXRMDLLB
KEYWORDS: PXRM
COMPONENT/ENTRY POINT: GETLSEQ
 COMPONENT DESCRIPTION:   Returns a list of sequences that should be updated
 when the LINK is applied to the Reminder Dialog.  
  
 LINK is the IEN of the file entry from file 801.48. OUTPUT is return an array
 of SEQUENCE Information. 
  
 If OUTPUT(0) if equal zero, then every instance of the impacted dialog 
 element/group/prompt/forced value should be updated in the dialog. 
  
 If OUTPUT(0) greater than 0 then the format is: 
  
 OUTPUT(x)=#~ The ~ designate a new group of sequences that need to be check. 
  
 OUTPUT(x+1)= CONTAIN SEQUENCE This designate the Sequence the LINK is being
 fired from. If the dialog item in the GUI contains this sequence then the GUI
 will search for the Affected Sequence number to update 
  
 OUTPUT(x+2) =AFFECTED SEQUENCE This designate the Sequence in the dialog that
 should be updated form the CONTAIN SEQUENCE value.  
  
 Example: 
  
 OUTPUT(0)=48 
  
 OUTPUT(1)="1~" 
  
 OUTPUT(2)="2.5.5.2.1.1.5" 
  
 OUTPUT(3)="2.5.5.2.1.1.10" 
  
 OUTPUT(4)="2~" 
  
 OUTPUT(5)="2.5.5.10.2.1.1.5" 
  
 OUTPUT(6)="2.5.5.10.2.1.1.10" 
  
 OUTPUT(7)="3~" 
  
 OUTPUT(8)="2.5.10.5.5.2.1.1.5" 
  
 OUTPUT(9)="2.5.10.5.5.2.1.1.10" 
  
 OUTPUT(10)="4~" 
  
 OUTPUT(11)="2.15.10.5.5.2.1.1.5" 
  
 OUTPUT(12)="2.15.10.5.5.2.1.1.10" 
  
 OUTPUT(13)="5~" 
  
 OUTPUT(14)="50.10.5.5.2.1.1.5" 
  
 OUTPUT(15)="50.10.5.5.2.1.1.10" 
  
 OUTPUT(16)="6~" 
  
 OUTPUT(17)="50.10.5.5.10.2.1.1.5" 
  
 OUTPUT(18)="50.10.5.5.10.2.1.1.10" 
  
 OUTPUT(19)="7~" 
  
 OUTPUT(20)="50.10.5.10.5.5.2.1.1.5" 
  
 OUTPUT(21)="50.10.5.10.5.5.2.1.1.10" 
  
 OUTPUT(22)="8~" 
  
 OUTPUT(23)="50.10.10.5" 
  
 OUTPUT(24)="50.10.10.10" 
  
 OUTPUT(25)="9~" 
  
 OUTPUT(26)="50.10.15.10.5.5.2.1.1.5" 
  
 OUTPUT(27)="50.10.15.10.5.5.2.1.1.10" 
  
 OUTPUT(28)="10~" 
  
 OUTPUT(29)="1.50.2.2.1.1" 
  
 OUTPUT(30)="1.50.2.2.1.2" 
  
 OUTPUT(31)="11~" 
  
 OUTPUT(32)="5.140.10.10.10.5" 
  
 OUTPUT(33)="5.140.10.10.10.10" 
  
 OUTPUT(34)="12~" 
  
 OUTPUT(35)="5.105.20.10.10.5" 
  
 OUTPUT(36)="5.105.20.10.10.10" 
  
 OUTPUT(37)="13~" 
  
 OUTPUT(38)="1.38.1.2.1.1" 
  
 OUTPUT(39)="1.38.1.2.1.2" 
  
 OUTPUT(40)="14~" 
  
 OUTPUT(41)="50.5.2.10.10.5" 
  
 OUTPUT(42)="50.5.2.10.10.10" 
  
 OUTPUT(43)="15~" 
  
 OUTPUT(44)="1.50.2.1.2.2.1.1" 
  
 OUTPUT(45)="1.50.2.1.2.2.1.2" 
  
 OUTPUT(46)="16~" 
  
 OUTPUT(47)="5.140.10.5.2.10.10.5" 
  
 OUTPUT(48)="5.140.10.5.2.10.10.10" 
VARIABLES: LINK                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the file entry from file 801.48 
VARIABLES: RETURN                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns an array of SEQUENCE Information.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
  DATE ACTIVATED: APR 21, 2025

NUMBER: 7538                            IA #: 7538
  FILE NUMBER: 661.7                    GLOBAL ROOT: RMPR(661.7,
  DATE CREATED: APR 17, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: File
  NAME: PROSTHETICS CURRENT STOCK FILE (WRITE ACCESS)
  ID: RMPR(661.7,
GLOBAL REFERENCE: RMPR(661.7,D0,0
FIELD NUMBER: .01                       FIELD NAME: HCPCS
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: DATE&TIME STAMP
  LOCATION: 0;2                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: SEQUENCE
  LOCATION: 0;3                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: HCPCS ITEM
  LOCATION: 0;4                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: STATION
  LOCATION: 0;5                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: LOCATION
  LOCATION: 0;6                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 6                         FIELD NAME: QUANTITY
  LOCATION: 0;7                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 7                         FIELD NAME: VALUE
  LOCATION: 0;8                         ACCESS: Direct Global R/W & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: UNIT OF ISSUE
  LOCATION: 0;9                         ACCESS: Direct Global R/W & w/Fileman
GLOBAL REFERENCE: RMPR(661.7,'XHDS'
GLOBAL REFERENCE: RMPR(661.7,'XSHIDS'
GLOBAL REFERENCE: RMPR(661.7,'XSLHIDS'
 GENERAL DESCRIPTION:   This integration agreement allows the PROSTHETICS
 VISION 4 SIGHT II read and write access to all fields of the PROSTHETIC
 CURRENT STOCK file (#661.7) when creating a Prosthetics Inventory Package
 (PIP) stock issue.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/17/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires access to the
 Prosthetic current stock file 661.7 

NUMBER: 7539                            IA #: 7539
  DATE CREATED: APR 17, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRPCED                     NAME: API FOR RMPRPCED
  ID: RMPRPCED
 GENERAL DESCRIPTION:   This ICR supports the ability to process eyeglass
 orders.  
  STATUS: Active
COMPONENT/ENTRY POINT: DEL
 COMPONENT DESCRIPTION:   Prompts to delete PCE visit 
VARIABLES: RMIE60                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN for file 660 
VARIABLES: RMPRCED                      TYPE: Output
 VARIABLES DESCRIPTION:   0-success 1-failure 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/17/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires access to the
 routine RMPRPCED, component $$DEL 

NUMBER: 7540                            IA #: 7540
  DATE CREATED: APR 17, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRPIYF                     NAME: API FOR RMPRPIYF
  ID: RMPRPIYF
 GENERAL DESCRIPTION:   This ICR supports the ability to process eyeglass
 orders.  
  STATUS: Active
COMPONENT/ENTRY POINT: EXIT
 COMPONENT DESCRIPTION:   Kill variables and exit routine 
VARIABLES: RMPRIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of RECORD OF PROS APPLIANCE/REPAIR file (660) 
COMPONENT/ENTRY POINT: POST
 COMPONENT DESCRIPTION:   Kill variables and exit routine 
VARIABLES: RMPRIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   IEN of RECORD OF PROS APPLIANCE/REPAIR file (660) 
VARIABLES: R1                           TYPE: Input
 VARIABLES DESCRIPTION:   Array of data from RECORD OF PROS APPLIANCE/REPAIR
 file (660) 
VARIABLES: RMPR11                       TYPE: Input
 VARIABLES DESCRIPTION:   Array of data from PROSTHETICS HCPCS ITEM MASTER FILE
 (661.11) 
COMPONENT/ENTRY POINT: DEL1
 COMPONENT DESCRIPTION:   Delete an issue from stock 
VARIABLES: RMPRIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   
  IEN of RECORD OF PROS APPLIANCE/REPAIR file (660) 
VARIABLES:  
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/17/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires access to the
 routine RMPRPIYF, component EXIT 

NUMBER: 7541                            IA #: 7541
  FILE NUMBER: 661.4                    GLOBAL ROOT: RMPR(661.4
  DATE CREATED: APR 17, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: File
  NAME: Access to the HCPCS INVENTORY FILE #661.4
  ID: RMPR(661.4
GLOBAL REFERENCE: RMPR(661.4
FIELD NUMBER: .01                       FIELD NAME: HCPCS
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: HCPCS ITEM
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: STATION
  LOCATION: 0;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: RE-ORDER QUANTITY
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: 5                         FIELD NAME: QUANTITY ON
  LOCATION: 0;5                         ACCESS: Read w/Fileman
FIELD NUMBER: 7                         FIELD NAME: LOCATION
  LOCATION: 0;7                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: RMPR(661.4,'ASLHI'
 GENERAL DESCRIPTION:   This ICR supports the ability to process eyeglass
 orders. 
  STATUS: Active
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/17/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires access to the HCPCS
 inventory file 661.4 

NUMBER: 7542                            IA #: 7542
  DATE CREATED: APR 17, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRPIFD                     NAME: API FOR RMPRPIFD
  ID: RMPRPIFD
 GENERAL DESCRIPTION:   This ICR supports the ability to process eyeglass
 orders. 
  STATUS: Active
COMPONENT/ENTRY POINT: DEL1
 COMPONENT DESCRIPTION:   
  ENTRY POINT TO DELETE AN ISSUE FROM STOCK 
VARIABLES: R1                           TYPE: Input
 VARIABLES DESCRIPTION:   Array of PROS ITEM MASTER file (#661) entries 
VARIABLES: RMPRIEN                      TYPE: Input
 VARIABLES DESCRIPTION:   RECORD OF PROS APPLIANCE/REPAIR IEN 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/17/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires access to the
 routine RMPRPIFD, component DEL1 

NUMBER: 7543                            IA #: 7543
  DATE CREATED: APR 21, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRCPTU                     NAME: API Call to RMPRCPTU
  ID: RMPRCPTU
 GENERAL DESCRIPTION:   DESCRIPTION: This ICR supports the ability to process
 eyeglass orders.  
  STATUS: Active
COMPONENT/ENTRY POINT: CPT
 COMPONENT DESCRIPTION:   Entry point for CPT 
VARIABLES: RDA                          TYPE: Input
 VARIABLES DESCRIPTION:   delimited string containing the following data: 
 rmcphc=PSAS HCPCS                             rmcpty=TYPE OF TRANSACTION       
        rmcpso=SOURCE                           rmcpfi=file used (660,664 or
 664.1) 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/21/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires access to the
 routine RMPRCPTU, component CPT 

NUMBER: 7544                            IA #: 7544
  DATE CREATED: APR 22, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRPIYI                     NAME: API FOR RMPRPIYI
  ID: RMPRPIYI
 GENERAL DESCRIPTION:   This ICR supports the ability to process eyeglass
 orders.  
  STATUS: Active
COMPONENT/ENTRY POINT: LOWBA
 COMPONENT DESCRIPTION:   Print message if inventory balance is low 
VARIABLES: RMUBA                        TYPE: Input
 VARIABLES DESCRIPTION:   PSAS item balance 
VARIABLES: RMIT                         TYPE: Input
 VARIABLES DESCRIPTION:   PSAS item 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/22/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires access to the
 routine RMPRPIYI, component LOWBA 

NUMBER: 7545                            IA #: 7545
  DATE CREATED: APR 25, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPR21                       NAME: API For RMPR21
  ID: RMPR21
 GENERAL DESCRIPTION:   This integration agreement allows PROSTHETICS VISION 4
 SIGHT to reference routine RMPR21 with the understanding that usage of the 
 functionality contained in RMPR21 is not granted.  
  STATUS: Active
COMPONENT/ENTRY POINT: RMPR21
VARIABLES: N/A                          TYPE: Input
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/24/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, requests permission to reference routine RMPR21 with
 the understanding that usage of the functionality contained in RMPR21 is not 
 granted.  

NUMBER: 7546                            IA #: 7546
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: APR 22, 2025            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED
  NAME: READ/WRITE DISCHARGED TO CERNER FIELD
  ID: DPT(
GLOBAL REFERENCE: DPT(DA,
FIELD NUMBER: 9000                      FIELD NAME: DISCHARGED TO CERNER
  LOCATION: CERNER;1                    ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   When set, field #9000 creates the ACERNER
 cross-reference.  The AUTOMATED PATIENT DISCHARGE TOOL directly reads that
 cross-reference to produce its post-discharge list.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   DG*5.3*1128 added the DISCHARGED TO CERNER field
 (#9000) to the PATIENT file (#2) for use by the AUTOMATED PATIENT DISCHARGE
 TOOL (EHM*1*15), a conversion patch.  EHM*1*15 sets field #9000 when a patient
 is automatically discharged from VistA on the night of cutover to the Cerner 
 EHR.  EHM*1*15 also reads the cross-reference on the field to prepare its 
 post-discharge list.  
  DATE ACTIVATED: APR 23, 2025

NUMBER: 7547                            IA #: 7547
  FILE NUMBER: 445                      GLOBAL ROOT: PRCP(445,
  DATE CREATED: APR 22, 2025            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  NAME: GENERIC INVENTORY FILE ACCESS   ID: PRCP(445,
GLOBAL REFERENCE: PRCP(445,D0,0
FIELD NUMBER: .01                       FIELD NAME: INVENTORY POINT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Provides ability to read the GENERIC INVENTORY FILE
 #445 to display the Inventory Point.  
  STATUS: Active
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/22/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires Direct Global Read
 of the .01 field as used by the legacy code.  

NUMBER: 7548                            IA #: 7548
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX
  DATE CREATED: APR 25, 2025            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Field # 100.2 Mail Exemption
  ID: PSRX
GLOBAL REFERENCE: PSRX(
FIELD NUMBER: 100.2                     FIELD NAME: Mail Exemption
  LOCATION: 7;2                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   Read FM for PRESCRIPTION (#52) FILE Mail Exemption
 FIELD 100.2 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Need access to READ data from Prescription File (#52)
 Mail Exemption field 100.2 
  DATE ACTIVATED: APR 25, 2025

NUMBER: 7549                            IA #: 7549
  DATE CREATED: APR 28, 2025            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XMVSM
  NAME: XMVSM APIs                      ID: XMVSM
 GENERAL DESCRIPTION:   The purpose of this Routine is to provide read-only
 APIs returning MailMan operational status.  
  
 The VistA System Monitor (VSM) will use this data to display this operational
 state data in a real-time VistA Operations Dashboard. VSM functionality
 consuming these APIs will initially be deployed via patch KMP*4.0*5.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VistA System Monitor
KEYWORDS: VSM
COMPONENT/ENTRY POINT: $$XMLIST(XMARR)
 COMPONENT DESCRIPTION:   Returns the number of mail messages queued on each
 mail domain, total number of messages queued and the total number of domains
 with queued messages.  
  
 Usage: D XMLIST^XMVSM(.XMARR) 
VARIABLES: XMARR                        TYPE: Both
 VARIABLES DESCRIPTION:   The name of the output array, passed by reference, to
 contain the message counts.  
  
 XMARR("DOMAINS",DOMAIN)=Message Count ^ Device XMARR("TMQUED")=Total messages
 queed XMARR("TOTDOMS")=Total domains with queued messages 
SUBSCRIBING PACKAGE: CAPACITY MANAGEMENT
  DATE ACTIVATED: APR 29, 2025

NUMBER: 7550                            IA #: 7550
  DATE CREATED: APR 28, 2025            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUVSM
  NAME: XUVSM APIs                      ID: XUVSM
 GENERAL DESCRIPTION:   The purpose of this Routine is to provide read-only
 APIs returning KERNEL operational states.  
  
 The VistA System Monitor (VSM) will use this data to display this operational
 state data in a real-time VistA Operations Dashboard. VSM functionality
 consuming these APIs will initially be deployed via patch KMP*4.0*5.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VistA System Monitor
KEYWORDS: VSM
COMPONENT/ENTRY POINT: $$RUNSTATUS()
 COMPONENT DESCRIPTION:   Returns the run status of TaskMan.  
  
 Usage: S Y=$$RUNSTATUS^XUVSM() 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   This API returns a "^" delimited string.  
  
 Piece 1: Text Status. (ex. "Current") Piece 2: Number of seconds behind Piece
 3: Current Timestamp Piece 4: Run Node Timestamp 
COMPONENT/ENTRY POINT: $$STATLIST(XUARR)
 COMPONENT DESCRIPTION:   Returns the TaskMan status list.  
  
 Usage: D $$RUNSTATUS^XUVSM(.XUARR) 
VARIABLES: XUARR                        TYPE: Both
 VARIABLES DESCRIPTION:   A variable passed by reference to contain the output
 data.  
  
 XUARR("LIST",D0,"EXECUTE")=Execution Status XUARR("LIST",D0,"JOBNUM")=Job
 Number XUARR("LIST",D0,"NODE")=Node XUARR("LIST",D0,"STATUS")=Status 
 XUARR("LIST",D0,"TIME")=Current Time XUARR("LIST",D0,"STATMESS")=Text message
 if available 
COMPONENT/ENTRY POINT: $$SCHLIST()
 COMPONENT DESCRIPTION:   Returns task status count by category.  
  
 Usage: S Y=$$SCHLIST^XUVSM() 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Returns a "^" delimited string.  
  
 Piece 1: Number of tasks scheduled Piece 2: Number of tasks late Piece 3:
 Number of seconds late for nearest task 
COMPONENT/ENTRY POINT: $$IOLIST(XUARR)
 COMPONENT DESCRIPTION:   Returns the status on tasks waiting for IO.  
  
 Usage: D $$IOLIST^XUVSM(.XUARR) 
VARIABLES: XUARR                        TYPE: Both
 VARIABLES DESCRIPTION:   XUARR is a variable passed by reference to hold the
 return values.  
  
 XUARR("LASTDEV") XUARR("LASTSCAN") XUARR("TTSKWAIT") 
COMPONENT/ENTRY POINT: $$JOBSWAIT()
 COMPONENT DESCRIPTION:   Returns the number of tasks waiting to execute.  
  
 Usage: S Y=$$JOBSWAIT^XUVSM() 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Y = The number of tasks waiting to execute.  
COMPONENT/ENTRY POINT: $$TASKSRUN()
 COMPONENT DESCRIPTION:   Returns the number of tasks currently running.  
  
 Usage: S Y=$$TASKSRUN^XUVSM() 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Y = the number of tasks currently running.  
COMPONENT/ENTRY POINT: $$SMLIST(XUARR)
 COMPONENT DESCRIPTION:   Returns the status on TaskMan submanagers.  
  
 Usage: D $$SMLIST^XUVSM(.XUARR) 
VARIABLES: XUARR                        TYPE: Both
 VARIABLES DESCRIPTION:   XUARR is a variable passed by reference to hold the
 output values.  
  
 XUARR("SUBMWAIT")= Wait Status   (1:told to wait or 0:OK) 
 XUARR("LIST","D0,"NODE")=Node XUARR("LIST",D0,"COUNT")=Task Count 
 XUARR("LIST",D0,"STATUS")=Current Status  (Stop, Wait or run) 
 XUARR("LIST",D0,"NOSTART")=Start Flag (1="Submanagers Not Starting", 0="OK") 
COMPONENT/ENTRY POINT: $$INSTALL(.XUIN,XUSDAT,XUEDAT)
 COMPONENT DESCRIPTION:   Returns the status on patch installations.  
  
 Usage: D $$INSTALL^XUVSM(.XUIN,XUSDAT,XUEDAT) 
VARIABLES: XUIN                         TYPE: Both
 VARIABLES DESCRIPTION:   A variable passed by reference to hold the output
 values.  
  
 XUIN(IDATE,PATNUM)="" where 
         IDATE =  Patch Install Date 
         PATNUM = Patch Number 
VARIABLES: XUSDAT                       TYPE: Input
 VARIABLES DESCRIPTION:   Start date for search in YYY-MM-DD format.  
VARIABLES: XUEDAT                       TYPE: Input
 VARIABLES DESCRIPTION:   End date for search in YYY-MM-DD format.  
COMPONENT/ENTRY POINT: $$FUT(.ZTCHECK)
 COMPONENT DESCRIPTION:   Returns the status of specified options expected to
 be tasked in the future.  
  
 Usage: D $$FUT^XUVSM(.ZTCHECK) 
VARIABLES: ZTCHECK                      TYPE: Both
 VARIABLES DESCRIPTION:   ZTCHECK is an array passed by reference in the form
 of: 
         ZTCHECK("option to be checked")="Not Scheduled" 
  
 If an option in the input array is found to be scheduled in the future the
 value of "Not Scheduled" will be replace by a "^" string depicting the date
 and time in the future for which the option is tasked.  
SUBSCRIBING PACKAGE: CAPACITY MANAGEMENT
  DATE ACTIVATED: APR 29, 2025

NUMBER: 7551                            IA #: 7551
  DATE CREATED: APR 28, 2025            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: HLVSM
  NAME: HLVSM APIs                      ID: HLVSM
 GENERAL DESCRIPTION:   The purpose of this routine is to provide read-only
 APIs returning HL7 operational status.  
  
 The VistA System Monitor (VSM) will use this data to display this operational
 state data in a real-time VistA Operations Dashboard. VSM functionality
 consuming these APIs will initially be deployed via patch KMP*4.0*5.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VistA System Monitor
KEYWORDS: VSM
COMPONENT/ENTRY POINT: $$GETFILERS(HLDIR,HLARR)
 COMPONENT DESCRIPTION:   Returns the number of IN/OUT filers and the status of
 each.  
  
 Usage: S Y=$$GETFILERS^HLVSM(HLDIR,HLARR) 
VARIABLES: HLDIR                        TYPE: Input
 VARIABLES DESCRIPTION:   "IN" to request status on incoming filers.  "OUT" to
 request status on outgoing filers.  
VARIABLES: HLARR                        TYPE: Both
 VARIABLES DESCRIPTION:   The name of the output array to contain the status of
 each filer. Passed by value.  
  
 Returns an array, subscripted by job number, with a "^" string for each entry. 
  
 HLARR(JOBNUMBER)=STRING where: 
  
 Piece 1: Job Number Piece 2: Last Run Date Piece 3: Stop Flag Piece 4: Request
 Timestamp Piece 5: Error (if any) 
COMPONENT/ENTRY POINT: $$FILERCFG()
 COMPONENT DESCRIPTION:   Returns the number of filers configured.  
  
 Usage: S Y=$$FILERCFG^HLVSM() 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Contains the number of filers configured.  
COMPONENT/ENTRY POINT: $$LMSTAT()
 COMPONENT DESCRIPTION:   Returns the link manager status.  
  
 sS Y=$$LMSTAT^HLVSM() 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Y will contain the status of the Link Manager.  
  
 1: Running 0: Not Running 
COMPONENT/ENTRY POINT: $$CHKSTOP()
 COMPONENT DESCRIPTION:   Returns the HLO System Status.  
  
 Usage: S Y=$$CHKSTOP^HLVSM() 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Y contains the HLO System Status.  
  
 1: Stopped 0: Running 
COMPONENT/ENTRY POINT: $$PROCMAN()
 COMPONENT DESCRIPTION:   Returns the HLO Process Manager Status 
  
 Usage: S Y=$$PROCMAN^HLVSM() 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Y contains the HLO Process Manager status.  
  
 1: Running 0: Stopped 
COMPONENT/ENTRY POINT: $$MPOQ(.HLOQARR)
 COMPONENT DESCRIPTION:   Returns the number of messages pending on the OUT
 queue with a list of message metadata.  
  
 Usage: S Y=$$MPOQ^HLVSM(.HLOQARR) 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   To messages pending on the OUT queue.  
VARIABLES: HLOQARR                      TYPE: Both
 VARIABLES DESCRIPTION:   A variable passed by reference to contain the output
 data.  
  
 HLOQARR("OUT")=Total messages queued HLOQARR("OUT",Link,Queue)=Count per
 Link/queue 
COMPONENT/ENTRY POINT: $$MPSQ(.HLSQARR)
 COMPONENT DESCRIPTION:   Returns the number of messages pending on the
 SEQUENCE queue with a list of message metadata.  
  
 Usage: S Y=$$MPSQ^HLVSM(.HLSQARR) 
VARIABLES: XUSQARR                      TYPE: Both
 VARIABLES DESCRIPTION:   A variable passed by reference to hold the output
 values.  
  
 HLSQARR("OUT")=Total number of messages queued.  
 HLSQARR("OUT",Link,Queue)=Number of messages per link/queue.  
COMPONENT/ENTRY POINT: $$MPAQ(.HLAQARR)
 COMPONENT DESCRIPTION:   Returns the number of messages pending on the
 APPLICATION queue with a list of message metadata.  
  
 Usage: S Y=$$MPAQ^HLVSM(.HLAQARR) 
VARIABLES: HLAQARR                      TYPE: Both
COMPONENT/ENTRY POINT: $$ADD(HLTYPE)
 COMPONENT DESCRIPTION:   Returns the number of messages sent, received, in
 error out, and in error in per requested type.  
VARIABLES: HLTYPE                       TYPE: Input
 VARIABLES DESCRIPTION:   Determines which type of message data will be
 returned. HLTYPE should be one of the following: 
  
      OUT: returns messages sent 
      IN: returns messages received 
      EOUT: returns outbound message errors 
      EIN: returns inbound message errors 
COMPONENT/ENTRY POINT: $$CLPROC(HLDIR)
 COMPONENT DESCRIPTION:   Returns the number of IN or OUT client link
 processes.  
  
 Usage: S Y=$$CLPROC^HLVSM(HLDIR) 
VARIABLES: HLDIR                        TYPE: Input
 VARIABLES DESCRIPTION:   "OUTOING CLIENT LINK":  Returns OUT processes 
 "INCOMING QUEUES": Returns IN processes 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Contains the number of processes returned.  
COMPONENT/ENTRY POINT: $$FILE777()
 COMPONENT DESCRIPTION:   Returns the File 777 record count from ^HLTMP.  
  
 Usage: S Y=$$FILE777^HLVSM() 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Contains the File 777 Record Count from ^HLTMP.  
COMPONENT/ENTRY POINT: $$FILE778()
 COMPONENT DESCRIPTION:   Contains the File 778 Record Count from ^HLTMP.  
  
 Usage: S Y=$$FILE778^HLVSM() 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Contains the File 778 Record Count from ^HLTMP.  
COMPONENT/ENTRY POINT: $$SLM()
 COMPONENT DESCRIPTION:   Returns the currency of the HLO Link Manager.  
  
 Usage: S Y=$$SLM^HLVSM() 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Contains the currency of the HLO Link Manager.  
COMPONENT/ENTRY POINT: $$LSTAT()
 COMPONENT DESCRIPTION:   Returns the HLO Link Manager status.  
  
 Usage: S Y=$$LSTAT^HLVSM() 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Contains the HLO Link Manager status.  
  
 1: Running 0: Stopped 
COMPONENT/ENTRY POINT: $$DLINKS()
 COMPONENT DESCRIPTION:   Returns a list of failing logical links up to 60
 characters in total length.  
  
 Usage: S Y=$$DLINKS^HLVSM() 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   A list of failing links.  
COMPONENT/ENTRY POINT: $$STQUES(HLDIR)
 COMPONENT DESCRIPTION:   Returns the number of stopped In or OUT queues.  
  
 Usage: S Y=$$STQUES^HLVSM(HLDIR) 
VARIABLES: HLDIR                        TYPE: Input
 VARIABLES DESCRIPTION:   IN: incoming queues OUT: outgoing queues 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   The number of stopped queues.  
COMPONENT/ENTRY POINT: GETVIEWS(.HLVARR)
 COMPONENT DESCRIPTION:   Returns a list of Logical Link Views.  
  
 Usage: D GETVIEWS^HLVSM(.HLVARR) 
VARIABLES: HLVARR                       TYPE: Both
 VARIABLES DESCRIPTION:   A variable passed by reference to hold output values. 
  
 HLVARR(VIEW, SORT ORDER, LINNK)="" 
SUBSCRIBING PACKAGE: CAPACITY MANAGEMENT
  DATE ACTIVATED: APR 29, 2025

NUMBER: 7552                            IA #: 7552
  FILE NUMBER: 3.077                    GLOBAL ROOT: %ZTERR(3.077
  DATE CREATED: APR 28, 2025            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: Error Trap Summary
  ID: %ZTERR(3.077
GLOBAL REFERENCE: %ZTER(3.077,D0,0
FIELD NUMBER: .01                       FIELD NAME: ERROR TEXT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1                         FIELD NAME: FIRST DATE/TIME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: MOST RECENT DATE/TIME
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: ROUTINE NAME
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: %ZTER(3.077,D0,4,D1,0
FIELD NUMBER: .01                       FIELD NAME: FREQUENCY DISTRIBUTION
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The purpose of this ICR is to provide error trap
 summary information to the VistA System Monitor.  This data will be stored
 centrally and be available via Dashboards and by specific request to those
 monitoring and managing VistA sites.  
  
 Functionality within the VistA System Monitor consuming this data will be 
 released in patch KMP*4.0*5.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: VistA System Monitor
KEYWORDS: VSM
SUBSCRIBING PACKAGE: CAPACITY MANAGEMENT
  DATE ACTIVATED: APR 29, 2025

NUMBER: 7553                            IA #: 7553
  DATE CREATED: APR 30, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRD1                       NAME: API Call to RMPRD1
  ID: RMPRD1
 GENERAL DESCRIPTION:   This integration agreement allows access to routine
 RMPRD1 to obtain the display date, patient, item, and cost from file 660 for
 eyeglass ordering.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   DISPLAY DATE,PATIENT,ITEM,COST FROM 660 
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN for File #660 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 04/30/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires access to the
 routine RMPRD1, component EN.  

NUMBER: 7554                            IA #: 7554
  DATE CREATED: MAY 02, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRPIYY                     NAME: API FOR RMPRPIYY
  ID: RMPRPIYY
 GENERAL DESCRIPTION:   This integration agreement allows call PROSTHETICS
 routine PORD^RMPRPIYY to provide prompts and barcodes; it will allow users to
 get barcodes for eyeglass ordering.  
  STATUS: Active
COMPONENT/ENTRY POINT: PORD
 COMPONENT DESCRIPTION:   
  Prompts for an open order 
VARIABLES: RMPRSTN                      TYPE: Input
 VARIABLES DESCRIPTION:   Site station number 
VARIABLES: RMPRHCPC                     TYPE: Input
 VARIABLES DESCRIPTION:   HCPCS Code 
VARIABLES: RMPRITM                      TYPE: Input
 VARIABLES DESCRIPTION:   HCPCS Item Number 
VARIABLES: RMPR41                       TYPE: Output
 VARIABLES DESCRIPTION:   Array of HCPCS INVENTORY ORDER AND REORDER (661.41)
 file data 
VARIABLES: RMPREXC                      TYPE: Output
 VARIABLES DESCRIPTION:   Current stock order exit code ('T', 'P', '^') 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 05/02/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires access to the
 routine RMPRPIYY, component PORD 

NUMBER: 7555                            IA #: 7555
  DATE CREATED: MAY 02, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRPIY1                     NAME: API FOR RMPRPIY1
  ID: RMPRPIY1
 GENERAL DESCRIPTION:   This integration agreement allows to call PROSTHETICS
 routine HCPCS3^RMPRPIY1 to display HCPCS and inventory information for
 eyeglass ordering.  
  STATUS: Active
COMPONENT/ENTRY POINT: HCPCS3
 COMPONENT DESCRIPTION:   Display selected HCPCS and item.  
VARIABLES: RMPR1                        TYPE: Input
 VARIABLES DESCRIPTION:   RMPR1('HCPCS') - HCPCS Code - PROSTHETIC HCPCS
 (#661.1) file field HCPCS (#.01) 
  
 RMPR1('SHORT DESC'`) - HCPCS Description - PROSTHETIC HCPCS (#661.1) file 
 field SHORT NAME (#.02) 
VARIABLES: RMPR11                       TYPE: Input
 VARIABLES DESCRIPTION:   RMPR11('ITEM MASTER') - IFCAP Item - PROSTHETICS
 HCPCS ITEM MASTER FILE (#661.11) ITEM MASTER (#7) 
  
 RMPR11('DESCRIPTION') - PIP Item Description - PROSTHETICS HCPCS ITEM MASTER
 FILE (#661.11) DESCRIPTION (#2) 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 05/02/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the Prosthetics package requires access to the
 routine RMPRPIY1, component HCPCS3 

NUMBER: 7556                            IA #: 7556
  DATE CREATED: MAY 02, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRAINQ                     NAME: API CALL TO RMPRAINQ
  ID: RMPRAINQ
 GENERAL DESCRIPTION:   Access to RMPRAINQ to display vehicle of record
 history.  
  STATUS: Active
COMPONENT/ENTRY POINT: DU
 COMPONENT DESCRIPTION:   PRINT AUTO-ADAPTIVE EQUIPMENT 
VARIABLES: RMPRDFN                      TYPE: Input
 VARIABLES DESCRIPTION:   PATIENT IEN 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 05/02/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, requests permission to reference routine RMPRAINQ, 
 component DU, with the understanding that usage of the functionality contained
 in DU^RMPRAINQ is not granted.  

NUMBER: 7557                            IA #: 7557
  DATE CREATED: MAY 02, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRPAT0                     NAME: API TO CALL RMPRPAT0
  ID: RMPRPAT0
 GENERAL DESCRIPTION:   This integration agreement provides the ability to
 display additional demographic data, last movements, clinic enrollments, and
 pending appointments for a patient.  
  STATUS: Active
COMPONENT/ENTRY POINT: RMPRPAT0
 COMPONENT DESCRIPTION:   PATIENT INQUIRY SCREEN FROM MAS 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 05/02/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, requests permission to reference routine RMPRPAT0 
 with the understanding that usage of the functionality contained in RMPRPAT0
 is not granted.  

NUMBER: 7558                            IA #: 7558
  DATE CREATED: MAY 02, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRPAT1                     NAME: API TO CALL RMPRPAT1
  ID: RMPRPAT1
 GENERAL DESCRIPTION:   This integration agreement allows calls to the routine
 RMPRPAT1.  
  STATUS: Active
COMPONENT/ENTRY POINT: ASK1
 COMPONENT DESCRIPTION:   Allows user to choose the 10-2319 screen number to
 display 
VARIABLES: RCNT                         TYPE: Input
 VARIABLES DESCRIPTION:   Assumed in environment 
COMPONENT/ENTRY POINT: HELP
 COMPONENT DESCRIPTION:   Presents the list of 10-2319 screens available to
 display 
VARIABLES: DIR(0)                       TYPE: Input
 VARIABLES DESCRIPTION:   Assumed in environment 
VARIABLES: RCNY                         TYPE: Input
 VARIABLES DESCRIPTION:   Assumed in environment 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 05/02/25, effective with PROSTHETICS VISION 4
 SIGHT II patch RMPV*1*1, the permission to reference routine HELP^RMPRPAT1
 with the understanding that usage of the functionality contained in
 HELP^RMPRPAT1 is not granted .  The API call to the component ASK1 is granted. 
 

NUMBER: 7559                            IA #: 7559
  DATE CREATED: MAY 05, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRPIYK                     NAME: API TO CALL RMPRPIYK
  ID: RMPRPIYK
 GENERAL DESCRIPTION:   This integration agreement allows call PROSTHETICS
 routine RMPRPIYK to display an issue from a stock item. 
  STATUS: Active
COMPONENT/ENTRY POINT: RMPRPIYK
 COMPONENT DESCRIPTION:   Display issue from stock 
VARIABLES: RMPRHISD                     TYPE: Used
 VARIABLES DESCRIPTION:   Historical Data Indicator 
VARIABLES: RMPRNAM                      TYPE: Used
 VARIABLES DESCRIPTION:   Patient Name 
VARIABLES: RMPRSSN                      TYPE: Used
 VARIABLES DESCRIPTION:   Patient SSN 
VARIABLES: R1                           TYPE: Used
 VARIABLES DESCRIPTION:   Array represents the entire file 660 record.  
VARIABLES: R3('D')                      TYPE: Used
 VARIABLES DESCRIPTION:   - 4th piece contains file RECORD OF PROS
 APPLIANCE/REPAIR #660 field TYPE OF TRANSACTION (#2) 
  
 - 6th piece contains file PROS ITEM MASTER #661 field NAME (#.01) 
  
 - 14th piece contains file RECORD OF PROS APPLIANCE/REPAIR #660 field SOURCE
 (#12) 
VARIABLES: RMLACO                       TYPE: Used
VARIABLES: RMLOC                        TYPE: Used
 VARIABLES DESCRIPTION:   file #661.6 field LOCATION (#14) 
VARIABLES: R4('D')                      TYPE: Used
 VARIABLES DESCRIPTION:   - 3rd piece contains file RECORD OF PROS
 APPLIANCE/REPAIR #660 field SPECIAL CATEGORY (#63) 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 5/5/25, effective with PROSTHETICS VISION 4 SIGHT
 II patch RMPV*1*1, the Prosthetics package requires access to the routine
 RMPRPIYK 

NUMBER: 7560                            IA #: 7560
  DATE CREATED: MAY 05, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPOBIL2                     NAME: API TO CALL RMPOBIL2
  ID: RMPOBIL2
 GENERAL DESCRIPTION:   This ICR provides access to the routine RMPOBIL2 for
 Home Oxygen Billing Transaction.  
  STATUS: Active
COMPONENT/ENTRY POINT: 2319
 COMPONENT DESCRIPTION:   DISPLAY HOME OXYGEN ITEMS 
VARIABLES: RMRPDFN                      TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 5/5/25, effective with PROSTHETICS VISION 4 SIGHT
 II patch RMPV*1*1, requests permission to reference routine RMPOBIL2 with the
 understanding that usage of the functionality contained in RMPOBIL2 is not
 granted.  

NUMBER: 7561                            IA #: 7561
  DATE CREATED: MAY 05, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRPAT                      NAME: API CALL TO RMPRPAT
  ID: RMPRPAT
 GENERAL DESCRIPTION:   This integration agreement allows a call to routine
 RMPRPAT to display the first page of a patient's 2319.  
  STATUS: Active
COMPONENT/ENTRY POINT: STAR
 COMPONENT DESCRIPTION:   DISPLAY ADDRESS INFO 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 5/5/25, effective with PROSTHETICS VISION 4 SIGHT
 II patch RMPV*1*1, requests permission to reference routine RMPRPAT with the
 understanding that usage of the functionality contained in RMPRPAT is not
 granted.  

NUMBER: 7562                            IA #: 7562
  DATE CREATED: MAY 05, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRPIYE                     NAME: API CALL TO RMPRPIYE
  ID: RMPRPIYE
 GENERAL DESCRIPTION:   This ICR provides access to the routine RMPRPIYE to
 pull inventory information for eyeglass ordering.  
  STATUS: Active
COMPONENT/ENTRY POINT: SET60
 COMPONENT DESCRIPTION:   Setup RMPR60 -array of data fields for 660 file
 record 
VARIABLES: R1                           TYPE: Input
 VARIABLES DESCRIPTION:   Array of file #660 values 
VARIABLES: RMPR11                       TYPE: Input
 VARIABLES DESCRIPTION:   Array of PROSTHETICS HCPCS ITEM MASTER FILE (661.11)
 file internal values 
VARIABLES: RMDAHC                       TYPE: Input
 VARIABLES DESCRIPTION:   HCPCS CODE 
VARIABLES: RMPR('S')                    TYPE: Input
 VARIABLES DESCRIPTION:   PROSTHETIC SITE PARAMETERS (#669.9) file STATION
 (#1), internal 
VARIABLES: RMPR60                       TYPE: Output
 VARIABLES DESCRIPTION:   array - RECORD OF PROS APPLIANCE/REPAIR (#660) values 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 5/5/25, effective with PROSTHETICS VISION 4 SIGHT
 II patch RMPV*1*1, the Prosthetics package requires access to the routine
 RMPRPIYE, component SET60 

NUMBER: 7563                            IA #: 7563
  DATE CREATED: MAY 05, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRPAT2                     NAME: API TO CALL RMPRPAT2
  ID: RMPRPAT2
 GENERAL DESCRIPTION:   This integration agreement allows a call to PROSTHETICS
 routine RMPRPAT2 to populate the Appliance Transaction display of a patient's 
 10-2319.  
  STATUS: Active
COMPONENT/ENTRY POINT: RMPRPAT2
 COMPONENT DESCRIPTION:   DISPLAY PATIENT ITEM ACTIVITY 
VARIABLES: RMPRDFN                      TYPE: Used
 VARIABLES DESCRIPTION:   
  PROSTHETIC PATIENT (#665) file NAME (#.01) , internal 
VARIABLES: RMPR('STA')                  TYPE: Used
 VARIABLES DESCRIPTION:   PROSTHETIC SITE PARAMETERS (#669.9) file STATION
 (#1), internal 
VARIABLES: RMPRNAM                      TYPE: Used
 VARIABLES DESCRIPTION:   The NAME of the patient 
VARIABLES: RMPRSSN                      TYPE: Used
 VARIABLES DESCRIPTION:   Social Security Number of the patient, internal 
VARIABLES: RMPRDOB                      TYPE: Used
 VARIABLES DESCRIPTION:   The Date of Birth of the patient in FileMan format 
VARIABLES: RMPRCNUM                     TYPE: Used
 VARIABLES DESCRIPTION:   The CLAIM NUMBER of the patient 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 5/5/25, effective with PROSTHETICS VISION 4 SIGHT
 II patch RMPV*1*1, requests permission to reference routine RMPRPAT2 with the
 understanding that usage of the functionality contained in RMPRPAT2 is not
 granted.  

NUMBER: 7564                            IA #: 7564
  DATE CREATED: MAY 06, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRPIU8                     NAME: API TO CALL RMPRPIU8
  ID: RMPRPIU8
 GENERAL DESCRIPTION:   This integration agreement allows call PROSTHETICS
 routine RMPRPIU8 to provide the ability to create a Stock Receipt Transaction
 when processing eyeglass orders.  
  STATUS: Active
COMPONENT/ENTRY POINT: $$REC
 COMPONENT DESCRIPTION:   Prompts for a stock receipt transaction to get
 barcode 
VARIABLES: RMPR6                        TYPE: Input
 VARIABLES DESCRIPTION:   Transaction (661.6) array elements 
      RMPR6("VENDOR")   - Vendor ien 
      RMPR6("QUANTITY") - Receipt Quantity 
      RMPR6("VALUE")    - Total $ value of received qty.  
      RMPR6("COMMENT")  - (optional) comment 
VARIABLES: RMPR11                       TYPE: Input
 VARIABLES DESCRIPTION:   HCPCS Item (661.11) array elements 
      RMPR11("STATION") - Station ien 
      RMPR11("HCPCS")   - HCPCS code 
      RMPR11("ITEM")    - HCPCS Item number 
VARIABLES: RMPR5                        TYPE: Input
 VARIABLES DESCRIPTION:   Location (661.5) array elements...  
      RMPR5("IEN") - Location ien (ptr ^RMPR(661.5,) 
VARIABLES: RMPRUPO                      TYPE: Input
 VARIABLES DESCRIPTION:   flag true=> update, false=> dont update orders 
VARIABLES: RMPR41                       TYPE: Input
 VARIABLES DESCRIPTION:   array for orders 
VARIABLES: RMPRERR                      TYPE: Output
 VARIABLES DESCRIPTION:   Returned by function 
                 0 - no errors 
                19 - problem creating 661.6 rec.  
                29 - problem creating 661.7 rec.  
                39 - problem creating 661.9 rec.  
                49 - problem updating 661.41 orders 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 5/6/25, effective with PROSTHETICS VISION 4 SIGHT
 II patch RMPV*1*1, the Prosthetics package requires access to the routine
 RMPRPIU8, component $$REC 

NUMBER: 7565                            IA #: 7565
  DATE CREATED: MAY 06, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRDP                       NAME: API TO CALL RMPRDP
  ID: RMPRDP
 GENERAL DESCRIPTION:   This integration agreement allows a call routine RMPRDP
 to provide access to Record Pickup and Delivery Charges functionality.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Contains pickup and delivery logic.  
VARIABLES: RMPRDFN                      TYPE: Used
 VARIABLES DESCRIPTION:   PROSTHETIC PATIENT (#665) file NAME (#.01) , internal 
VARIABLES: RMPR('STA')                  TYPE: Used
 VARIABLES DESCRIPTION:   PROSTHETIC SITE PARAMETERS (#669.9) file STATION
 (#1), internal 
VARIABLES: RMPRKILL                     TYPE: Used
 VARIABLES DESCRIPTION:   Indicates whether Prosthetic Disability Codes exist
 for a patient 
VARIABLES: IOM                          TYPE: Used
 VARIABLES DESCRIPTION:   The width of the IO device 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 5/6/25, effective with PROSTHETICS VISION 4 SIGHT
 II patch RMPV*1*1, requests permission to reference routine RMPRDP with the
 understanding that usage of the functionality contained in RMPRDP is not
 granted.  

NUMBER: 7566                            IA #: 7566
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  NAME: VCRS                            STATUS: Withdrawn
  DURATION: Till Otherwise Agreed       EXPIRATION DATE: MAY 28, 2025

NUMBER: 7567                            IA #: 7567
  DATE CREATED: MAY 08, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRPAT5                     NAME: API TO CALL RMPRPAT5
  ID: RMPRPAT5
 GENERAL DESCRIPTION:   This integration agreement allows a call to PROSTHETICS 
 routine RMPRPAT5 to display critical comments and disability codes on the
 patient's 10-2319.  
  STATUS: Active
COMPONENT/ENTRY POINT: DISP
 COMPONENT DESCRIPTION:   Display disability codes 
VARIABLES: RMPRDFN                      TYPE: Used
 VARIABLES DESCRIPTION:   PROSTHETIC PATIENT (#665) file NAME field (#.01) 
VARIABLES: RMPR(665,RMPRDFN,1,0)        TYPE: Used
 VARIABLES DESCRIPTION:   PROSTHETIC DISABILITY CODE (file 665 subfile 665.01
 node 0) 
COMPONENT/ENTRY POINT: NPC
 COMPONENT DESCRIPTION:   Check all disability codes marked deleted 
VARIABLES: RMPRDFN                      TYPE: Used
 VARIABLES DESCRIPTION:   PATIENT DFN (file 2 field #.01) 
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 5/8/25, effective with PROSTHETICS VISION 4 SIGHT
 II patch RMPV*1*1, the Prosthetics package requires access to the routine
 RMPRPAT5, components DISP and NPC.  

NUMBER: 7568                            IA #: 7568
  DATE CREATED: MAY 08, 2025            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RMPRE29                      NAME: API TO CALL RMPRE29
  ID: RMPRE29
 GENERAL DESCRIPTION:   This integration agreement allows a call to PROSTHETICS
 routine RMPRE29 to edit A 2319 entry.  
  STATUS: Active
COMPONENT/ENTRY POINT: TYP1
 COMPONENT DESCRIPTION:   Edit type of transaction 
VARIABLES: RMPRDA                       TYPE: Used
 VARIABLES DESCRIPTION:   IEN for the file RECORD OF PROS APPLIANCE/REPAIR 
VARIABLES: RMPREDT                      TYPE: Used
 VARIABLES DESCRIPTION:   1 indicates that is it an edit.  
SUBSCRIBING PACKAGE: PROSTHETICS VISION 4 SIGHT II
 SUBSCRIBING DETAILS:   Added 5/8/25, effective with PROSTHETICS VISION 4 SIGHT
 II patch RMPV*1*1, the Prosthetics package requires permission to reference
 the routine RMPRE29, with the understanding that usage of the functionality
 contained in RMPRE29 is not granted.  

NUMBER: 7569                            IA #: 7569
  DATE CREATED: MAY 15, 2025            CUSTODIAL PACKAGE: CLINICAL REMINDERS
  USAGE: Private                        TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PXRMPDEM
  NAME: DATE PATIENT TURNS A SPECIFIC AGE
  ID: PXRMPDEM                          STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: WV
KEYWORDS: PXRM
COMPONENT/ENTRY POINT: DFA
 COMPONENT DESCRIPTION:   This routine determines the date the patient turns a
 specified age. The date returned can be in the past or in the future.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The patient's DFN. This argument is required.  
VARIABLES: NGET                         TYPE: Input
 VARIABLES DESCRIPTION:   The number of records to return. This argument is not
 used but must be passed, pass "".  
VARIABLES: BDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The beginning date to search for. This argument is
 not used but must be passed, pass "".  
VARIABLES: EDT                          TYPE: Input
 VARIABLES DESCRIPTION:   The ending date to search for. This argument is not
 used but must be passed, pass "".  
VARIABLES: NFOUND                       TYPE: Output
 VARIABLES DESCRIPTION:   The number of records found. This will be 0 if TEST
 is NULL. It will be 1 if TEST is set to a valid age.  
VARIABLES: TEST                         TYPE: Both
 VARIABLES DESCRIPTION:   As an input, this argument is the age to determine
 the date when the patient will reach that age. Fractional ages are not
 allowed. If TEST is set to a fractional age, the fractional part will be
 ignored. Input example: TEST=40. As an output, TEST(1)=0 if TEST was passed as
 NULL, otherwise TEST(1)=1.  
VARIABLES: DATE                         TYPE: Output
 VARIABLES DESCRIPTION:   The FileMan date the patient turns the specified age
 in DATE(1).  
VARIABLES: VALUE                        TYPE: Output
 VARIABLES DESCRIPTION:   The FileMan date the patient turns the specified age
 in VALUE(1).  
VARIABLES: TEXT                         TYPE: Output
 VARIABLES DESCRIPTION:   If TEST(1)=1, TEXT(1) will be a text string in one of
 the following formats: For dates in the past - TEXT(1)= "Patient was 40 years
 old on 05/01/2024." For dates in the future - TEXT(1)= "Patient will be 40
 years old on 05/01/2026." 
SUBSCRIBING PACKAGE: WOMEN'S HEALTH
  DATE ACTIVATED: MAY 15, 2025

NUMBER: 7570                            IA #: 7570
  DATE CREATED: JUN 04, 2025
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  USAGE: Supported                      TYPE: Routine
  NAME: Add/Update NKA 
 GENERAL DESCRIPTION:   VDIF Custom Writeback Service, VCRS, needs an API to
 safely update the Reaction Assessment field in file 120.86 where appropriate.  
  STATUS: Pending

NUMBER: 7571                            IA #: 7571
  FILE NUMBER: 365.013                  GLOBAL ROOT: IBE(365.013
  DATE CREATED: JUL 01, 2025            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: DSIV X12 FILE 365.013 ACCESS    ID: IBE(365.013
GLOBAL REFERENCE: IBE(365.013,D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: .02                       FIELD NAME: DESCRIPTION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: .03                       FIELD NAME: INACTIVE?
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This agreement allows INSURANCE CAPTURE BUFFER to read
 via FileMan fields needed to be displayed in a list to the user as well as
 filter out entries which are marked as INACTIVE?.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
 SUBSCRIBING DETAILS:   Added 7/1/25, effective with patch DSIV*2.2*16, 
 INSURANCE CAPTURE BUFFER needs to access select fields from the X12 271
 SERVICE TYPE (#365.013) for display and selection.  

NUMBER: 7572                            IA #: 7572
  FILE NUMBER: 869.3                    GLOBAL ROOT: HLCS(869.3,
  DATE CREATED: JUL 21, 2025            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  USAGE: Private                        TYPE: File
  NAME: INCOMING FILER TASK NUMBERS     ID: HLCS(869.3,
GLOBAL REFERENCE: HLCS(869.3,D0,2,D1
FIELD NUMBER: .01                       FIELD NAME: INCOMING FILER TASK NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   The CIRN package has a monitoring process in routine
 RGMTMONT that examines numerous touchpoints such as PROTOCOLS,  OPTIONS and
 other FILE references to ensure that the site is configured appropriately to 
 communicate with the Master Patient Index (MPI). Any problems/issues uncovered
 are transmitted back to the MPI for display during our daily monitoring of the
 VistA sites. CIRN will augment this monitor processing to also include
 information on if the INCOMING FILERS have been started by POSTMASTER, as
 POSTMASTER does not have the required privileges to execute Remote Procedures
 Calls remotely when passed through the XWB2HL7 application programming
 interface.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: HL COMMUNICATION SERVER PARAM
KEYWORDS: HLCS(869.3
KEYWORDS: 869.3
KEYWORDS: HLCS(869.3,1,2,
KEYWORDS: CIRN
KEYWORDS: CIRN MONITOR
KEYWORDS: RGMTMONT
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
 SUBSCRIBING DETAILS:   Added 8/12/25 effective with patch RG*1.0*79 The
 CLINICAL INFO RESOURCE NETWORK (CIRN) package needs to be able to retrieve the
 list of INCOMING FILER TASK NUMBERs (#20) in the HL COMMUNICATION SERVER
 PARAMETERS (#869.3) file to determine the individual that started each task
 process.  

NUMBER: 7573                            IA #: 7573
  FILE NUMBER: 14.4                     GLOBAL ROOT: %ZTSK(
  DATE CREATED: JUL 21, 2025            CUSTODIAL PACKAGE: KERNEL
  USAGE: Private                        TYPE: File
  NAME: USER Starting Task              ID: %ZTSK(
GLOBAL REFERENCE: %ZTSK(D0
FIELD NUMBER: 3                         FIELD NAME: User
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
 GLOBAL DESCRIPTION:   The CIRN package has a monitoring process in routine
 RGMTMONT that examines numerous touchpoints such as PROTOCOLS,  OPTIONS and
 other FILE references to ensure that the site is configured appropriately to 
 communicate with the Master Patient Index (MPI). Any problems/issues uncovered
 are transmitted back to the MPI for display during our daily monitoring of the
 VistA sites. CIRN will augment this monitor processing to also include
 information on if the INCOMING FILERS have been started by POSTMASTER, as
 POSTMASTER does not have the required privileges to execute Remote Procedures
 Calls remotely when passed through the XWB2HL7 application programming
 interface.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TASKS
KEYWORDS: %ZTSK(
KEYWORDS: 14.4
KEYWORDS: CIRN
KEYWORDS: CIRN MONITOR
KEYWORDS: RGMTMONT
SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK
 SUBSCRIBING DETAILS:   Added 8/12/25 effective with patch RG*1.0*79.  The
 CLINICAL INFO RESOURCE NETWORK (CIRN) package needs to be able to retrieve the
 User (#3) in the TASKS (#14.4) file to determine who started the incoming HL7
 filer task process(es) and ensure that it was not POSTMASTER.  

NUMBER: 7574                            IA #: 7574
  DATE CREATED: JUL 23, 2025            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  ROUTINE: XUDSIGVALIDATE
  NAME: Kernel - Add Digital Signature Validation APIs
  ID: XUDSIGVALIDATE
 GENERAL DESCRIPTION:   These Kernel APIs validate XML digital signatures.  
  STATUS: Active                        EXPIRATION DATE: SEP 30, 2027
KEYWORDS: XML
KEYWORDS: SIGNATURE
COMPONENT/ENTRY POINT: $$VALIDATESIG(XMLFILEPATH,PUBLICKEYPATH,IDNAME,IDELEMENT,
.ELAPSEDTIMEMS)
 COMPONENT DESCRIPTION:   The $$VALIDATESIG^XUDSIGVALIDATE extrinsic function
 checks an XML file's digital signature and verifies the signature against a
 given public key.  The function returns whether the XML digital signature is
 valid.  
VARIABLES: XMLFILEPATH                  TYPE: Input
 VARIABLES DESCRIPTION:   (required) The file path of the signed XML document.  
VARIABLES: PUBLICKEYPATH                TYPE: Input
 VARIABLES DESCRIPTION:   (optional) The file path of the public key that
 signed the document. If this parameter is not set, the API will default to
 using the public key in the signed XML document.  
VARIABLES: IDNAME                       TYPE: Input
 VARIABLES DESCRIPTION:   (optional) If an element of the XML document was
 signed, the IdName tells the API to look for attributes with the given name.  
VARIABLES: IDELEMENT                    TYPE: Input
 VARIABLES DESCRIPTION:   (optional) The element that was signed.  
VARIABLES: ELAPSEDTIMEMS                TYPE: Output
 VARIABLES DESCRIPTION:   (optional) The amount of time in milliseconds that
 the API call took to complete.  
VARIABLES: returns                      TYPE: Output
 VARIABLES DESCRIPTION:   Returns: 
  
 Success (1) - The digital signature is valid.  
  
 Failure (0) - The digital signature is invalid, or an error occurred.  
  
 Failure (-1)- The operating system is not supported.  
COMPONENT/ENTRY POINT: $$VERIFYCHAIN(CACERT,XMLFILEPATH,TEMPCERTFILEPATH,CHECKIN
DCA,.CASUBJECT,.CACONTENTS,.ELAPSEDTIMEMS)
 COMPONENT DESCRIPTION:   The $$VERIFYCHAIN^XUDSIGVALIDATE extrinsic function
 checks whether the certificate contained within a signed XML file was signed
 by a specific Certificate Authority (CA).  
VARIABLES: CACERT                       TYPE: Input
 VARIABLES DESCRIPTION:   (required) The file path of the Certificate Authority
 Public key.  
VARIABLES: XMLFILEPATH                  TYPE: Input
 VARIABLES DESCRIPTION:   (required) The file path of the signed XML document.  
VARIABLES: TEMPCERTFILEPATH             TYPE: Both
 VARIABLES DESCRIPTION:   (optional) When the certificate is extracted from the
 XML document specified in the XMLFILEPATH parameter, the certificate is stored
 as a temp file on the server. The TEMPCERTFILEPATH parameter allows the user 
 to specify where the temp file is stored. The only requirement is that the
 path begins with /tmp. If no path is specified, the API writes the file to
 /tmp. If passed by reference and no path is set, TEMPCERTFILEPATH will be set
 to the directory path in /tmp where the file was written to, so that the user
 knows where the file has been stored.  
VARIABLES: CHECKINDCA                   TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Boolean (1 or 0) that determines whether
 the API should search through the certificate bundle provided in CACERT. The
 API will look for a certificate whose Subject equals the Issuer of the
 certificate in the XML document provided in XMLFILEPATH. If there is a match,
 the API will then verify that the CA certificate generated the leaf
 certificate. If so, $$VERIFYCHAIN^XUDSIGVALIDATE will return 1. Otherwise, the
 API will return 0 or -1.  
VARIABLES: CASUBJECT                    TYPE: Output
 VARIABLES DESCRIPTION:   If CHECKINDCA is set to 1, and a CA certificate was
 successfully found a validated, then CASUBJECT will be set to the subject of
 the CA certificate.  
VARIABLES: CACONTENT                    TYPE: Output
 VARIABLES DESCRIPTION:   If CHECKINDCA is set to 1, and a CA certificate was
 successfully found a validated, then CASUBJECT will be set to the contents of
 the CA certificate.  
VARIABLES: ELAPSEDTIMEMS                TYPE: Output
 VARIABLES DESCRIPTION:   (optional) The amount of time in milliseconds that
 the API call took to complete.  

NUMBER: 7575                            IA #: 7575
  DATE CREATED: JUL 23, 2025
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7575
  STATUS: Pending

NUMBER: 7576                            IA #: 7576
  DATE CREATED: JUL 23, 2025
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7576
  STATUS: Pending

NUMBER: 7577                            IA #: 7577
  FILE NUMBER: 820                      GLOBAL ROOT: PXIND(820,
  DATE CREATED: AUG 12, 2025
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: File
  NAME: SPECIAL AUTHORITIES READ VIA CODE FIELD
  ID: PXIND(820,
GLOBAL REFERENCE: PXIND(820,D0
FIELD NUMBER: 3                         FIELD NAME: DISPLAY NAME
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 4                         FIELD NAME: SEQ
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: ABBREVIATION
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: PXIND(820,'C',
 GLOBAL DESCRIPTION:   "C" cross-reference, used to find the IEN of a special
 authority by internal code.  
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to lookup entries in the SPECIAL AUTHORITIES file (#820) via the CODE field
 (#2) C cross-reference and access certain fields for each entry.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROBLEM LIST
 SUBSCRIBING DETAILS:   Added 10/31/25 effective with Patch GMPL*2*58 This data
 will be used by the GMPLSPECAUTH SPECAUTHDEF remote procedure to return the
 fields listed in the ICR for each of the special authorities for a patient to
 the CPRS GUI 

NUMBER: 7578                            IA #: 7578
  DATE CREATED: AUG 28, 2025
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORWTPT GETPTEAM                 REMOTE PROCEDURE: ORWTPT GETPTEAM
 GENERAL DESCRIPTION:   Function returns members of a PCMM team.  The record
 number (IEN) from the TEAM (#404.51) file.  RETURN PARAMETER DESCRIPTION:   
 Array of PCMM team members in the format: member id (IEN of #200 file)^member
 name 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 8/28/25, Effective with CDSP*1*1, this RPC
 provides members of a PCMM team 

NUMBER: 7579                            IA #: 7579
  DATE CREATED: AUG 28, 2025
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORQPT PTEAMPR                   REMOTE PROCEDURE: ORQPT PTEAMPR
 GENERAL DESCRIPTION:   Function returns a list of PCMM teams for a specific
 provider.  The provider number from the NEW PERSON (#200) file.  Uses DUZ if
 not passed in.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 8/28/25, effective with CDSP*1*1, this RPC is
 used to find the PCMM Teams 

NUMBER: 7580                            IA #: 7580
  DATE CREATED: AUG 28, 2025
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Remote Procedure
  NAME: ORQPT PTEAM PATIENTS            REMOTE PROCEDURE: ORQPT PTEAM PATIENTS
 GENERAL DESCRIPTION:   Function returns an array of patients on a PCMM team.  
 The record number from the TEAM (#404.51) file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: CLINICAL DECISION SUPPORT PLATFORM
 SUBSCRIBING DETAILS:   Added 8/28/25 effective with CDSP*1*1, this RPC
 provides an array of patients on a PCMM team 

NUMBER: 7581                            IA #: 7581
  DATE CREATED: AUG 28, 2025            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Remote Procedure
  ROUTINE: PSORPC01                     NAME: PSORPC
  REMOTE PROCEDURE: PSORPC              ID: PSORPC01
 GENERAL DESCRIPTION:   This RPC evaluates the passed option parameter to take
 the associated action on a given prescription or drug.  
  
 RPC^PSORPC01(RESULTS,OPTION,P1,P2,P3,P4,P5,P6) RESULTS: Indicates if the
 option is allowable on the order or drug.  OPTION: PARK, UNPARK, PARKDRG,
 PARKORD P1: IEN of Order or Drug P2: Pickup value (Mail, Clinic, Window) P3:
 Patient DFN P4: Encounter provider P5: Encounter location P6: <reserved> 
  
 PARK: Place this prescription in a Parked state.  UNPARK: Remove this
 prescription from a Parked state.  PARKDRG: Check if this drug is unable to be
 Parked.  PARKORD: Check if the drug associated with a supplied order number is 
 unable to be Parked.  
  
  
 PSORPC was introduced via PSO*7.0*441 as part of the CPRS GUI v32b combined
 build, CPRS_V32B_COMBINED_BUILD_1_0.KID. At this time, PSORPC was added to the
 OR CPRS GUI CHART context option. The need for this ICR was discovered during
 ICR review of the OR CPRS GUI CHART context option for CPRS GUI v33CON,
 OR*3.0*508.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PARK
KEYWORDS: UNPARK
KEYWORDS: PRESCRIPTION
COMPONENT/ENTRY POINT: RPC
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 9/4/25, effective with patch OR*3.0*508 PSORPC
 was introduced via PSO*7.0*441 as part of the CPRS GUI v32b combined build,
 CPRS_V32B_COMBINED_BUILD_1_0.KID. At this time, PSORPC was added to the OR
 CPRS GUI CHART context option. The need for this ICR was discovered during ICR
 review of the OR CPRS GUI CHART context option for CPRS GUI v33CON,
 OR*3.0*508.  

NUMBER: 7582                            IA #: 7582
  DATE CREATED: AUG 29, 2025
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: PXSPECAUTH SPECAUTHSTRUCT
  REMOTE PROCEDURE: PXSPECAUTH SPECAUTHSTRUCT
 GENERAL DESCRIPTION:   Patch PX*1.0*244 will release a new SPECIAL AUTHORITIES
 FILE #(820) and a routine of API calls to retrieve information about all the
 special authorities (previously known as Environmental Indicators). This 
 Controlled ICR allows subscribers to call these APIs to retrieve information
 from the new file. 
       
 The Special Authorities file allows future growth and to help minimize 
 elaborate software enhancements when needing to add a new authority. This file
 contains the business rules behind each authority, e.g. Name, code, disabled,
 abbreviation, sequence, default, disabled, visible, Package - disabled?,
 Linked authority behavior rules, Linked Authority, When value is, Actions to
 take.  
       
 See individual Component Entry for description and examples of call and 
 returned results.  
  STATUS: Active
KEYWORDS: SPECIAL AUTHORITY
KEYWORDS: SPECIAL AUTHORITIES
KEYWORDS: ENVIRONMENTAL
KEYWORDS: INDICATORS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Effective with patches PX*1.0*244 and OR*3.0*508 CPRS
 GUI will use this RPC to return all the valid authorities and their
 characteristics.  

NUMBER: 7583                            IA #: 7583
  DATE CREATED: AUG 29, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU CAN PRINT WORK/CHART COPY
  REMOTE PROCEDURE: TIU CAN PRINT WORK/CHART COPY
 GENERAL DESCRIPTION:   This RPC evaluates whether a user can print a Document,
 and if so, whether the user can print only a Work Copy or may print EITHER a
 Work Copy or a Chart Copy.  Authorization to print is determined by ASU
 Business Rules, and what type of copy by TIU Document Parameter ALLOW CHART
 PRINT OUTSIDE MAS. A user is "in MAS" if they are a member of ASU User Class
 MEDICAL INFORMATION SECTION.  
  STATUS: Active
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/17/25 effective with patch OR*3.0*508 Used by
 CPRS GUI as part of the process to print a TIU document.  
  
 This RPC usage is not new but rather found during ICR review of the OR CPRS
 GUI CHART context option exported in patch OR*3.0*508.  

NUMBER: 7584                            IA #: 7584
  DATE CREATED: SEP 08, 2025            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: SDOERPC                      NAME: SDOERPC LISTVST
  ID: SDOERPC
 GENERAL DESCRIPTION:   This integration agreement enables subscribing packages
 to request a list of encounters for a visit.  
  STATUS: Active
COMPONENT/ENTRY POINT: LISTVST
 COMPONENT DESCRIPTION:   This component returns a list of encounters for a
 given visit.  
VARIABLES: SDOEY                        TYPE: Input
 VARIABLES DESCRIPTION:   Pass by reference, return data location.  
VARIABLES: SDVST                        TYPE: Input
 VARIABLES DESCRIPTION:   Visit Information 
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 9/8/25, effective with patch PX*1.0*244 PCE will
 use this RPC to retrieve encounters for a visit 

NUMBER: 7585                            IA #: 7585
  DATE CREATED: SEP 17, 2025            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: Routine
  ROUTINE: IBCNEUT2                     NAME: DSIV EBSUMMARY
  ID: IBCNEUT2
 GENERAL DESCRIPTION:   This integration agreement allows the Insurance Capture
 Buffer Web (ICBWeb) to call Integrated Billing APIs to obtain summarized 
 information to be displayed as part of the eIV reporting. 
  STATUS: Active
KEYWORDS: ICBWEB
KEYWORDS: INSURANCEM CAPTURE BUFFER
COMPONENT/ENTRY POINT: EBSUMMARY(DFN,RIEN,SOI,ARRAY)
 COMPONENT DESCRIPTION:   This component returns a summary of insurance
 information.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN 
VARIABLES: RIEN                         TYPE: Input
 VARIABLES DESCRIPTION:   IIV RESPONSE (#365) IEN 
VARIABLES: SOI                          TYPE: Input
 VARIABLES DESCRIPTION:   Source of Information 
VARIABLES: ARRAY                        TYPE: Input
 VARIABLES DESCRIPTION:   Array where output will be stored 
VARIABLES: Output ARRAY                 TYPE: Output
 VARIABLES DESCRIPTION:   Insurance summary array 
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
 SUBSCRIBING DETAILS:   Added 9/17/25, effective with patch DSIV*2.2*16, 
 INSURANCE CAPTURE BUFFER needs to access the EBSUMMARY^IBCNEUT2 API for usage
 in their eIV reporting.  

NUMBER: 7586                            IA #: 7586
  DATE CREATED: SEP 24, 2025            CUSTODIAL PACKAGE: PROBLEM LIST
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: GMPLSPECAUTH
  NAME: PROBLEM LIST API FOR SPECIAL AUTHORITIES
  ID: GMPLSPECAUTH
 GENERAL DESCRIPTION:   This integration agreement allows subscribing packages
 to call Problem 
    List API to retrieve information about Special Authority (SA).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SPECIAL AUTHORITY
KEYWORDS: ENVIRONMENTAL
KEYWORDS: INDICATORS
KEYWORDS: SPECIAL AUTHORITIES
COMPONENT/ENTRY POINT: $$SHOWSA
 COMPONENT DESCRIPTION:   This API returns a 0 or 1. If set to 0, the calling
 applications should not prompt or show any SA values. If set to 1, the calling
 applications should show and set SA values. No variables are passed to this
 API.  
COMPONENT/ENTRY POINT: GETNEWSA
 COMPONENT DESCRIPTION:   This API returns the SA values for a given problem.  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number (IEN) of the problem's entry in
 the PROBLEM file (#9000011). This value is required.  
VARIABLES: GMPL1                        TYPE: Input
 VARIABLES DESCRIPTION:   The "1" node in the PROBLEM file (#9000011) for the
 problem. While this value is optional, it is required if the problem's entry
 does not have data in the SPECIAL   AUTHORITIES field (#2).  
VARIABLES: GMPLSA                       TYPE: Output
 VARIABLES DESCRIPTION:   Array of special authorities for the given problem.
 The first-level subscript is one of two values: (1) the abbreviation of the
 applicable special authority or (2) the value "SC|NSC". The value of the
 first- level subscript is either (1) an empty string when the subscript is not 
 "SC|NSC" or (2) "SC" if the patient is service connected or "NSC" if the 
 patient is not service connected.  
    Given the following array contents: 
          GMPLSA("SC|NSC")="SC" 
          GMPLSA("AO")=""                            The SA values for the
 example problem are service connected (SC) and agent orange (AO).  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/6/25, effective with patch OR*3.0*508. OE/RR
 will need to obtain the Problem List Special Authority data 
  
 Updated 12/9/25, effective with patch OR*3.0*508. OE/RR request to add
 component GETNEWSA 
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 12/22/25, effective with patch PX*1*244. PCE
 needs to obtain the Problem List Special Authority data.  

NUMBER: 7587                            IA #: 7587
  DATE CREATED: OCT 07, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU GET DOCUMENT STATUS
  REMOTE PROCEDURE: TIU GET DOCUMENT STATUS
 GENERAL DESCRIPTION:   This RPC is used to retrieve the Status (8925.6 IEN) of
 a TIU DOCUMENT.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIU
KEYWORDS: STATUS
KEYWORDS: 8925.6
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Documenting historical usage of this RPC by CPRS GUI.
 With OR*3.0*508, a review of the RPCs in OR CPRS GUI CHART found several RPCs
 not covered by an ICR.  

NUMBER: 7588                            IA #: 7588
  DATE CREATED: OCT 07, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU GET LINKED PRF NOTES
  REMOTE PROCEDURE: TIU GET LINKED PRF NOTES
 GENERAL DESCRIPTION:   Returns list of SIGNED, LINKED PRF notes for a given
 patient and a given Patient Record Flag (PRF) title.  
  
 INPUT PARAMETER: PTDFN                  PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Patient IEN in Patient file INPUT PARAMETER: TIUTTL                 PARAMETER
 TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  PRF Title IEN in file 8925.1 INPUT PARAMETER: REVORDER              
 PARAMETER TYPE: LITERAL 
   MAXIMUM DATA LENGTH: 1                REQUIRED: NO 
   SEQUENCE NUMBER: 3 
  DESCRIPTION:   
  Optional.  Boolean flag, with 1 indicating to subscript the list of notes 
  in reverse chronological order.  Default is chronological order.  
  RETURN PARAMETER DESCRIPTION:   
     TIUY = # of notes 
     TIUY(InternalNoteDate) = NoteIEN^Action^ExternalNoteDate^Author 
  where Internal Note Date is REFERENCE DATE in file 8925, (or 
  9999999-REFERENCE DATE if REVORDER=1).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRF
KEYWORDS: LINKED
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Documenting historical usage of this RPC by CPRS GUI.
 With OR*3.0*508, a review of the RPCs in OR CPRS GUI CHART found several RPCs
 not covered by an ICR.  

NUMBER: 7589                            IA #: 7589
  DATE CREATED: OCT 07, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU GET PRF ACTIONS             REMOTE PROCEDURE: TIU GET PRF ACTIONS
 GENERAL DESCRIPTION:   This RPC gets the Patient Record Flag History
 Assignments/Actions for a Patient/Title Combination.  
  
 INPUT PARAMETER: TIUTTL                 PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  TIU DOCUMENT DEFINITION (#8925.1) (TITLE) IEN INPUT PARAMETER: DFN            
        PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  Patient Pointer (file 2 IEN) 
  RETURN PARAMETER DESCRIPTION:   
  Returns data in the following format for each Flag Assignment/Action 
   
 FLAG NAME^FLAG IEN^ACTION NAME^ACTION IEN^ACTION DATE I^ACTION DATE E^TIU 
 IEN^CREATED BY SITE 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRF
KEYWORDS: ACTIONS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Documenting historical usage of this RPC by CPRS GUI.
 With OR*3.0*508, a review of the RPCs in OR CPRS GUI CHART found several RPCs
 not covered by an ICR.  

NUMBER: 7590                            IA #: 7590
  DATE CREATED: OCT 07, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU GET PRF TITLE               REMOTE PROCEDURE: TIU GET PRF TITLE
 GENERAL DESCRIPTION:   Returns IEN of the TIU Note Title in file 8925.1 which
 is associated with given flag for given patient.  
  
 INPUT PARAMETER: PTDFN                  PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  Patient IEN in Patient file INPUT PARAMETER: FLAGID                 PARAMETER
 TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  The unique number for a particular Active Record Flag returned by 
  $$GETACT^DGPFAPI.  See IA #3860.  See also GETFLAG^ORPRF.  
  RETURN PARAMETER DESCRIPTION:   
  Returns TIUY = TitleIEN^Title, 
  where Title is the .01 field in file 8925.1 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRF
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Documenting historical usage of this RPC by CPRS GUI.
 With OR*3.0*508, a review of the RPCs in OR CPRS GUI CHART found several RPCs
 not covered by an ICR.  

NUMBER: 7591                            IA #: 7591
  DATE CREATED: OCT 08, 2025
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DSIC XPAR DEL                   REMOTE PROCEDURE: DSIC XPAR DEL
 GENERAL DESCRIPTION:   This RPC will Delete an existing parameter for an
 entity for a specific instance.  
  STATUS: Active
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/8/25, effective with DSSO*2.0 released 4/16/20
 requested to be added as subscribers to RPC DSIC XPAR DEL 

NUMBER: 7592                            IA #: 7592
  DATE CREATED: OCT 08, 2025
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: DSIC USER DEF DIV               REMOTE PROCEDURE: DSIC USER DEF DIV
 GENERAL DESCRIPTION:   This RPC is used by DSS applications for retrieving
 user Division assignments. The assigned Divisions are presented to the user
 for selection if more than one Division has been assigned to the user. If the 
 user has been assigned only one division then the process will assign the user
 the assigned division.  
  STATUS: Active
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/8/25, effective with DSSO*2.0 released 4/16/20
 requested to be added as subscribers to RPC DSIC USER DEF DIV 

NUMBER: 7593                            IA #: 7593
  DATE CREATED: OCT 08, 2025
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: DSIC SEND MAIL MSG              REMOTE PROCEDURE: DSIC SEND MAIL MSG
 GENERAL DESCRIPTION:   This RPC is used by DSS applications for SENDING
 MAILMAN mail messages.  The routine is a wrapper around Standard kernel calls
 to send messages to VistA packages.  
  STATUS: Active
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/8/25, effective with DSSO*2.0 released 4/16/20
 requested to be added as subscribers to RPC DSIC SENT MAIL MSG 

NUMBER: 7594                            IA #: 7594
  DATE CREATED: OCT 17, 2025
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: DSIC SEND ALERT                 REMOTE PROCEDURE: DSIC SEND ALERT
 GENERAL DESCRIPTION:   This RPCs is used by DSS applications for NEW PERSON
 (#200) file accesses. The routine is a wrapper around Standard FILEMAN calls
 to Send Alerts to VistA packages. For DSS packages to do Alert processing 
  STATUS: Active
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/17/25, effective with DSSO*2.0 released 
 4/16/20 requested to be added as subscribers to RPC DSIC SENT ALERT 

NUMBER: 7595                            IA #: 7595
  DATE CREATED: OCT 17, 2025
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DSIC XPAR GET WP                REMOTE PROCEDURE: DSIC XPAR GET WP
 GENERAL DESCRIPTION:   This RPC will return text for a word processing type
 parameter for an entity and instance.  
  STATUS: Active
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/17/25, effective with DSSO*2.0 released 
 4/16/20 requested to be added as subscribers to RPC DSIC XPAR GET WP 

NUMBER: 7596                            IA #: 7596
  DATE CREATED: OCT 17, 2025
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: DSIC XPD PATCH                  REMOTE PROCEDURE: DSIC XPD PATCH
 GENERAL DESCRIPTION:   This RPC is used by DSS applications for retrieving
 data from the INSTALL (#9.7) file. The procedure is a wrapper around Standard
 FILEMAN and KERNEL calls to get dates and other information concerning KIDS
 installs.  
  STATUS: Active
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/17/25, effective with DSSO*2.0 released 
 4/16/20 requested to be added as subscribers to RPC DSIC SENT MAIL MSG 

NUMBER: 7597                            IA #: 7597
  DATE CREATED: OCT 20, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU IDENTIFY CLINPROC CLASS
  REMOTE PROCEDURE: TIU IDENTIFY CLINPROC CLASS
 GENERAL DESCRIPTION:   
  This RPC gets the CLINICAL PROCEDURES TIU Document Definition 
  file (#8925.1) IEN.  
  RETURN PARAMETER DESCRIPTION:   
  A numeric value is returned.  
   
  Either the CLINICAL PROCEDURES TIU Document file (#8925.1) IEN or 0.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CLINICAL PROCEDURES
KEYWORDS: DOCUMENT CLASS
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/20/25: Documenting historical usage of this
 RPC by CPRS GUI. With OR*3.0*508, a review of the RPCs in OR CPRS GUI CHART
 found several RPCs not covered by an ICR.  

NUMBER: 7598                            IA #: 7598
  DATE CREATED: OCT 20, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU ID SURGERY DOC CLASS
 GENERAL DESCRIPTION:   
  This RPC returns the record number of the class identified by the CLNAME 
  parameter in the TIU DOCUMENT DEFINITION file (#8925.1).  INPUT PARAMETER:
 CLNAME                 PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  This is the name (ASCII LITERAL) of the Class for which the calling 
  application needs an IEN.  
  RETURN PARAMETER DESCRIPTION:   
  The value returned will be either a positive integer, corresponding to 
  the record number identifying the class identified by the CLNAME 
  parameter, or zero, indicating that the Surgery interface is not yet 
  implemented in TIU.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SURGERY
KEYWORDS: DOCUMENT CLASS
KEYWORDS: TIUSRVD
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/20/25: Documenting historical usage of this
 RPC by CPRS GUI. With OR*3.0*508, a review of the RPCs in OR CPRS GUI CHART
 found several RPCs not covered by an ICR.  

NUMBER: 7599                            IA #: 7599
  DATE CREATED: OCT 20, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU IS THIS A CLINPROC?
  REMOTE PROCEDURE: TIU IS THIS A CLINPROC?
 GENERAL DESCRIPTION:   This RPC evaluates whether or not a Title is under the
 CLINICAL 
  PROCEDURES Class.  
  
 INPUT PARAMETER: TITLE                  PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  This is the TIU Document file (#8925.1) IEN for the Title selected.  
  RETURN PARAMETER DESCRIPTION:   
  A boolean value is returned.  
  1 = True.  The Title is under CLINICAL PROCEDURES Class.  
  0 = False.  The Title is NOT under the CLINICAL PROCEDURES Class.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CLINICAL PROCEDURES
KEYWORDS: TIUCP
KEYWORDS: DOCUMENT TITLE
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/20/25: Documenting historical usage of this
 RPC by CPRS GUI. With OR*3.0*508, a review of the RPCs in OR CPRS GUI CHART
 found several RPCs not covered by an ICR.  

NUMBER: 7600                            IA #: 7600
  DATE CREATED: OCT 20, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU IS USER A USR PROVIDER
  REMOTE PROCEDURE: TIU IS USER A USR PROVIDER
 GENERAL DESCRIPTION:   This Boolean RPC returns TRUE if the user was a member
 of USR CLASS 
  PROVIDER on the date specified.  INPUT PARAMETER: USER                  
 PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 1 DESCRIPTION:   
  This is the IEN of the user in the NEW PERSON FILE 200.  If no user is 
  specified, DUZ (the current user of the software) is the default.  INPUT
 PARAMETER: DATE                   PARAMETER TYPE: LITERAL 
   REQUIRED: NO                          SEQUENCE NUMBER: 2 DESCRIPTION:   
  This is the date in internal FILEMAN format for which the user's 
  membership in USR CLASS PROVIDER is evaluated.  If no date is received, 
  TODAY is the default. Date must be a strict date; time must NOT be 
  included.  RETURN PARAMETER DESCRIPTION:   
  TRUE is returned if user is an active member of USR CLASS PROVIDER on 
  the given date. If not, FALSE is returned.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: USR CLASS
KEYWORDS: USER CLASS
KEYWORDS: TIUSRVP1
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/31/25 Effective with patch OR*3.0*508
 Documenting historical usage of this RPC by CPRS GUI. With OR*3.0*508, a 
 review of the RPCs in OR CPRS GUI CHART found several RPCs not covered by an
 ICR.  

NUMBER: 7601                            IA #: 7601
  DATE CREATED: OCT 20, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU LINK TO FLAG                REMOTE PROCEDURE: TIU LINK TO FLAG
 GENERAL DESCRIPTION:   This RPC is used to link a Progress Note to a Patient
 Record Flag.  INPUT PARAMETER: TIUIEN                 PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  TIU DOCUMENT IEN (#8925) INPUT PARAMETER: PRFIEN                 PARAMETER
 TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 2 
  DESCRIPTION:   
  Flag IEN (#26.11 or #26.15) INPUT PARAMETER: ACTIENT                PARAMETER
 TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 3 
  DESCRIPTION:   
  PRF Assignment History IEN (#26.14) INPUT PARAMETER: DFN                   
 PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 4 
  DESCRIPTION:   
  Patient IEN (#2) 
  
 RETURN PARAMETER DESCRIPTION: Returns 1 for success or a two-piece error
 message. See $$STOTIU^DGPFAPI2 for details.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PRF
KEYWORDS: PATIENT RECORD FLAG
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/31/25 Effective with patch OR*3.0*508
 Documenting historical usage of this RPC by CPRS GUI. With OR*3.0*508, a 
 review of the RPCs in OR CPRS GUI CHART found several RPCs not covered by an
 ICR.  

NUMBER: 7602                            IA #: 7602
  DATE CREATED: OCT 20, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU LOAD RECORD TEXT            REMOTE PROCEDURE: TIU LOAD RECORD TEXT
 GENERAL DESCRIPTION:   This RPC returns the text (body) of a TIU Note. It is
 based on the TIU 
  LOAD RECORD FOR EDIT RPC.  INPUT PARAMETER: TIUDA                  PARAMETER
 TYPE: LITERAL 
   REQUIRED: YES DESCRIPTION:   
  This is the record number (IEN) in file 8925 for the document to retrieve 
  the body text.  RETURN PARAMETER DESCRIPTION:   
  The return will be in ^TMP("TIUEDIT",$J,"TEXT",n) with the 0 entry being 
  the header of "$TXT". Example return: 
   
       ^TMP("TIUEDIT",12345,"TEXT",0)="$TXT" 
       ^TMP("TIUEDIT",12345,"TEXT",1)="This is the first line of the note!" 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIUSRVR
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/31/25 Effective with patch OR*3.0*508
 Documenting historical usage of this RPC by CPRS GUI. With OR*3.0*508, a 
 review of the RPCs in OR CPRS GUI CHART found several RPCs not covered by an
 ICR.  

NUMBER: 7603                            IA #: 7603
  DATE CREATED: OCT 20, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU LONG LIST CLINPROC TITLES
  REMOTE PROCEDURE: TIU LONG LIST CLINPROC TITLES
 GENERAL DESCRIPTION:   This RPC serves data to a longlist of selectable Titles
 for CLINICAL 
  PROCEDURES.  INPUT PARAMETER: FROM                   PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 DESCRIPTION:   
  This is the reference Title from which the longlist is scrolling.  INPUT
 PARAMETER: DIR                    PARAMETER TYPE: LITERAL 
   SEQUENCE NUMBER: 2 DESCRIPTION:   
  This is the direction in which the longlist is scrolling from the 
  reference Title.  
  RETURN PARAMETER DESCRIPTION:   
  An array is returned.  
   
  This is an array of the 44 nearest titles to that indicated by the user 
  in the direction passed by the longlist component.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIUCP
KEYWORDS: CLINICAL PROCEDURES
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/31/25 Effective with patch OR*3.0*508
 Documenting historical usage of this RPC by CPRS GUI. With OR*3.0*508, a 
 review of the RPCs in OR CPRS GUI CHART found several RPCs not covered by an
 ICR.  

NUMBER: 7604                            IA #: 7604
  DATE CREATED: OCT 20, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU LONG LIST SURGERY TITLES 
  REMOTE PROCEDURE: TIU LONG LIST SURGERY TITLES 
 GENERAL DESCRIPTION:   This RPC serves data to a longlist of selectable TITLES
 for the class 
  named in the CLNAME parameter.  INPUT PARAMETER: FROM                  
 PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 DESCRIPTION:   
  This is the reference title from which the longlist is scrolling.  INPUT
 PARAMETER: DIR                    PARAMETER TYPE: LITERAL 
   SEQUENCE NUMBER: 2 DESCRIPTION:   
  This is the direction in which the longlist is scrolling from the 
  reference title.  INPUT PARAMETER: CLNAME                 PARAMETER TYPE:
 LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 3 DESCRIPTION:   
  This is the name of the class for which titles are being presented.  
  Allowable values are: 
   
  "SURGICAL REPORTS" 
  "PROCEDURE REPORTS (NON-O.R.)" RETURN PARAMETER DESCRIPTION:   
  This is an array of the 44 nearest titles to that indicated by the user 
  in the direction passed by the longlist component.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: SURGERY TITLES
KEYWORDS: TIUSRVD
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/31/25 Effective with patch OR*3.0*508
 Documenting historical usage of this RPC by CPRS GUI. With OR*3.0*508, a 
 review of the RPCs in OR CPRS GUI CHART found several RPCs not covered by an
 ICR.  

NUMBER: 7605                            IA #: 7605
  DATE CREATED: OCT 20, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU NEED TO SIGN?               REMOTE PROCEDURE: TIU NEED TO SIGN?
 GENERAL DESCRIPTION:   Does the current user need to sign this document.  
  
 INPUT PARAMETER: TIUDA                  PARAMETER TYPE: LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 
  DESCRIPTION:   
  The TIU document IEN (#8925) 
  
 RETURN PARAMETER DESCRIPTION: Returns 1 (yes) or 0 (no).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIUSRVA
KEYWORDS: SIGNATURE
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/31/25 Effective with patch OR*3.0*508
 Documenting historical usage of this RPC by CPRS GUI. With OR*3.0*508, a 
 review of the RPCs in OR CPRS GUI CHART found several RPCs not covered by an
 ICR.  

NUMBER: 7606                            IA #: 7606
  DATE CREATED: OCT 20, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: TIU USER INACTIVE?              REMOTE PROCEDURE: TIU USER INACTIVE?
 GENERAL DESCRIPTION:   Evaluates user's DIUSER status and termination status
 when selected.  INPUT PARAMETER: TIUUSR                 PARAMETER TYPE:
 LITERAL 
   REQUIRED: YES                         SEQUENCE NUMBER: 1 DESCRIPTION:   
  This is the IEN of the user in the NEW PERSON file (#200).  RETURN PARAMETER
 DESCRIPTION:   
  1 if the user is inactive, 0 if active.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TIUSRVA
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 10/31/25 Effective with patch OR*3.0*508
 Documenting historical usage of this RPC by CPRS GUI. With OR*3.0*508, a 
 review of the RPCs in OR CPRS GUI CHART found several RPCs not covered by an
 ICR.  

NUMBER: 7607                            IA #: 7607
  FILE NUMBER: 391.919                  GLOBAL ROOT: DGCN(391.919,
  DATE CREATED: OCT 23, 2025            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: Prosthetics Reason for Request Mapping Update
  ID: DGCN(391.919,
GLOBAL REFERENCE: DGCN(391.919,'ACRNR'
FIELD NUMBER: 391.919                   ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   Added 11/3/25 effective with patch RMPR*3*217. This
 patch is a conversion patch that creates a new interface between Prosthetics
 on converted sites and the Federal EHR.  
  
 One feature of the patch is a mechanism for updating the PROSTHETICS REASON
 FOR REQUEST MAPPING file (#666) via MailMan.  A structured email message is
 sent to a mail group on each converted site which invokes a server option to
 add, delete or update file entries.  
  
 The option which creates the structured mail messages needs to determine which
 sites are converted so it can distribute them. To do this it needs to directly
 read the "ACRNR" cross-reference of the EHRM MIGRATED FACILITIES file
 (#391.919).  

NUMBER: 7608                            IA #: 7608
  FILE NUMBER: 4.2                      GLOBAL ROOT: DIC(4.2,
  DATE CREATED: OCT 23, 2025            CUSTODIAL PACKAGE: MAILMAN
  USAGE: Private                        TYPE: File
  NAME: Prosthetics Reason for Request Mapping Update
  ID: DIC(4.2,
GLOBAL REFERENCE: DA,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5.5                       FIELD NAME: STATION
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   Added 12/3/25 effective with patch RMPR*3*217, this is
 a conversion patch that creates a new interface between Prosthetics on
 converted sites and the Federal EHR.  
  
 One feature of the patch is a mechanism for updating the PROSTHETICS REASON
 FOR REQUEST MAPPING file (#666) via MailMan.  A structured email message is
 sent to a mail group on each converted site which invokes a server option to
 add, delete or update file entries.  
  
 The option which creates the structured mail messages needs to determine which
 sites are converted so it can distribute them.  To do this, it scans the
 DOMAIN file (#4.2) and extracts the domain name and station number.  If the
 station number is for a converted site, the process sends a MailMan message to
 a mail group on that site which executes the server option.  
  
 Note: Determination if a site is converted is made using the EHRM MIGRATED
 FACILITIES file (#391.919).  

NUMBER: 7609                            IA #: 7609
  FILE NUMBER: 365.12                   GLOBAL ROOT: IBE(365.12
  DATE CREATED: OCT 23, 2025            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Private                        TYPE: File
  NAME: DSIV PAYER SERVICE DAYS ACCESS  ID: IBE(365.12
GLOBAL REFERENCE: IBE(365.12,D0,1,D1,0
FIELD NUMBER: .01                       FIELD NAME: APPLICATION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: IBE(365.12,D0,1,D1,4
FIELD NUMBER: 4.03                      FIELD NAME: FUTURE SERVICE DAYS
  LOCATION: 4;3                         ACCESS: Read w/Fileman
FIELD NUMBER: 4.04                      FIELD NAME: PAST SERVICE DAYS
  LOCATION: 4;4                         ACCESS: Read w/Fileman
 GENERAL DESCRIPTION:   This agreement allows INSURANCE CAPTURE BUFFER to read
 via FileMan fields needed to display dates to the user for a given PAYER entry 
 assuming an entry is found in the APPLICATION for "EIV".  
  STATUS: Active
SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER
 SUBSCRIBING DETAILS:   Added 10/23/25, effective with patch DSIV*2.2*16, 
 INSURANCE CAPTURE BUFFER needs to access select fields from the PAYER
 (#365.12) file, APPLICATION (#365.121) subfile to be used to calculate dates
 for display.  

NUMBER: 7610                            IA #: 7610
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123
  DATE CREATED: OCT 27, 2025
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  NAME: AVPR Index                      ID: GMR(123
GLOBAL REFERENCE: GMR(123,D0,0)
FIELD NUMBER: .02                       FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9                         FIELD NAME: LAST ACTION TAKEN
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   The Virtual Patient Record (VPR) would like to use the
 'AVPR' action cross reference on the CONSULT REQUEST file #123, LAST ACTION
 TAKEN field #9, to trigger updates to Healthshare when the action taken is 
 'Added Comment'. This cross reference is created in patch GMRC*3.0*217, which
 must be a prerequisite to patch VPR*1*37.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: AVPR
KEYWORDS: VPREVNT
SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD
 SUBSCRIBING DETAILS:   Added 5/8/26 effective with patch VPR*1*37 The Virtual
 Patient Record (VPR) would like to access File #123, PATIENT NAME #.02 and
 LAST ACTION TAKEN field #9.  

NUMBER: 7611                            IA #: 7611
  DATE CREATED: OCT 27, 2025
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DSIC XPAR ADD WP                REMOTE PROCEDURE: DSIC XPAR ADD WP
 GENERAL DESCRIPTION:   This RPC is used by DSS applications to allow the
 addition of a new Word-processing type system parameter.  
  STATUS: Active
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/27/25, effective with DSSO*2.0 released 
 4/16/20 requested to be added as subscribers to RPC DSIC XPAR ADD WP 

NUMBER: 7612                            IA #: 7612
  DATE CREATED: OCT 27, 2025
  CUSTODIAL PACKAGE: VA CERTIFIED COMPONENTS - DSSI
  USAGE: Controlled Subscription        TYPE: Remote Procedure
  NAME: DSIC XPAR ADD                   REMOTE PROCEDURE: DSIC XPAR ADD
 GENERAL DESCRIPTION:   This RPC is used by DSS applications for modifications
 to KERNEL System Parameters. The routine uses standard FILEMAN and KERNEL
 calls to derive results. KERNEL XPAR APIs (Supported ICR #2263) are wrapped by
 this routine 
  STATUS: Active
SUBSCRIBING PACKAGE: ADVANCED PROSTHETICS ACQ TOOL
 SUBSCRIBING DETAILS:   Added 10/27/25, effective with DSSO*2.0 released 
 4/16/20 requested to be added as subscribers to RPC DSIC XPAR ADD 

NUMBER: 7613                            IA #: 7613
  DATE CREATED: NOV 04, 2025
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7613
  STATUS: Pending

NUMBER: 7614                            IA #: 7614
  DATE CREATED: NOV 04, 2025
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7614
  STATUS: Pending

NUMBER: 7615                            IA #: 7615
  DATE CREATED: NOV 04, 2025            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Remote Procedure
  NAME: XU START TLS                    REMOTE PROCEDURE: XU START TLS
 GENERAL DESCRIPTION:   This RPC initializes an existing open connection to
 start using TLS.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TLS
KEYWORDS: ENCRYPT

NUMBER: 7616                            IA #: 7616
  DATE CREATED: NOV 04, 2025            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  ROUTINE: XUTLS                        NAME: TLS Initiation
  ID: XUTLS
 GENERAL DESCRIPTION:   Initialize a server-side OPEN or USE command for TLS
 communication.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TLS
KEYWORDS: INIT
COMPONENT/ENTRY POINT: INIT
 COMPONENT DESCRIPTION:   Initialize a server-side OPEN or USE command for TLS
 communication.  
VARIABLES: COMMAND                      TYPE: Input
 VARIABLES DESCRIPTION:   "OPEN" or "USE" command.  
VARIABLES: DEVICENAME                   TYPE: Input
 VARIABLES DESCRIPTION:   The TCP/IP device being used.  
VARIABLES: TLSCONFIGNAME                TYPE: Input
 VARIABLES DESCRIPTION:   The name of the TLS server configuration.  
VARIABLES: TIMEOUT                      TYPE: Input
 VARIABLES DESCRIPTION:   Timeout (in seconds) for OPEN command 
VARIABLES: SCREEN                       TYPE: Input
 VARIABLES DESCRIPTION:   MUMPS condition to screen whether or not to log 
VARIABLES: LOGGER                       TYPE: Input
 VARIABLES DESCRIPTION:   Logger to call to log messages if the screen
 evaluates to true 
COMPONENT/ENTRY POINT: $$GKSPTLSCN
 COMPONENT DESCRIPTION:   Get Kernel System Parameter "DEFAULT TLS SERVER
 CONFIG." (FILE=8989.3, FIELD=667) 
COMPONENT/ENTRY POINT: INITUP
 COMPONENT DESCRIPTION:   Initialize the already open TCP principal device to
 USE TLS communication.  
COMPONENT/ENTRY POINT: INITOP
 COMPONENT DESCRIPTION:   Initialize the principal device to OPEN TLS
 communication.  

NUMBER: 7617                            IA #: 7617
  DATE CREATED: NOV 06, 2025            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  ROUTINE: XUSUDO                       NAME: Security.SSLConfigs access
  ID: XUSUDO
 GENERAL DESCRIPTION:   These API's give users the ability to check TLS
 configurations in Intersystems IRIS.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: security
KEYWORDS: TLS
COMPONENT/ENTRY POINT: $$ISTLSCLIENTCONF
 COMPONENT DESCRIPTION:   Verify the TLS configuration with name ACONFNAME
 exists and is of type client.  
VARIABLES: ACONFNAME                    TYPE: Input
 VARIABLES DESCRIPTION:   A TLS configuration name.  
COMPONENT/ENTRY POINT: $$ISTLSSERVERCONF
 COMPONENT DESCRIPTION:   Verify the TLS configuration with name ACONFNAME
 exists and is of type server.  
VARIABLES: ACONFNAME                    TYPE: Input
 VARIABLES DESCRIPTION:   A TLS configuration name.  
COMPONENT/ENTRY POINT: $$HASTLSCONF
 COMPONENT DESCRIPTION:   Check to see if ACONFNAME parameter exists in the
 Security.SSLConfigs table.  
VARIABLES: ACONFNAME                    TYPE: Input
 VARIABLES DESCRIPTION:   A TLS configuration name.  
VARIABLES: ACONFTYPE                    TYPE: Output
 VARIABLES DESCRIPTION:   The type (client or server).  

NUMBER: 7618                            IA #: 7618
  DATE CREATED: NOV 25, 2025
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  USAGE: Private                        TYPE: Routine
  ROUTINE: TIUPXAP1                     NAME: TIUPXAP1
  ID: TIUPXAP1
 GENERAL DESCRIPTION:   APIs for TIUPXAP1.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: PROVIDER
COMPONENT/ENTRY POINT: $$PROVIDER
 COMPONENT DESCRIPTION:   Returns 1 if the user was a provider on the given
 date, 0 otherwise.  
VARIABLES: USER                         TYPE: Input
 VARIABLES DESCRIPTION:   The NEW PERSON (#200) IEN.  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   A date (in FileMan format). Used to check if the user
 was a provider on that date.  
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 12/1/25, effective with patch OR*3.0^508. This is
 a pre-existing call to PROVIDER^TIUPXAP1 not covered by an ICR.  

NUMBER: 7619                            IA #: 7619
  FILE NUMBER: 125.11                   GLOBAL ROOT: GMPL(125.11,
  DATE CREATED: NOV 25, 2025            CUSTODIAL PACKAGE: PROBLEM LIST
  USAGE: Private                        TYPE: File
  NAME: PROBLEM SELECTION CATEGORY      ID: GMPL(125.11,
GLOBAL REFERENCE: GMPL(125.11,'C',
 GLOBAL DESCRIPTION:   Read access to the "C" cross-reference.  
GLOBAL REFERENCE: GMPL(125.11,D0,1,D1,0)
FIELD NUMBER: .01                       FIELD NAME: PROBLEM
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: SEQUENCE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DISPLAY TEXT
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .04                       FIELD NAME: ASSOCIATED ICD CODE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: SNOMED CT CONCEPT CODE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .06                       FIELD NAME: SNOMED CT DESIGNATION CODE
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   Access to the PROBLEM SELECTION CATEGORY (#125.11)
 file.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING
 SUBSCRIBING DETAILS:   Added 11/2/25, effective with patch OR*3*508 review
 found read access to file 125.11 needed an ICR.  

NUMBER: 7620                            IA #: 7620
  DATE CREATED: DEC 04, 2025            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGADDUTL                     NAME: EDIT ADDRESS AND CELL PHONE
  ID: DGADDUTL
 GENERAL DESCRIPTION:   This ICR is for editing the patient mailing address,
 temporary address, and cell phone for Outpatient Pharmacy (PSO).  This is used
 by the PSOPAT option to edit patient demographic information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: CELL PHONE
KEYWORDS: MAILING ADDRESS
KEYWORDS: TEMPORARY ADDRESS
COMPONENT/ENTRY POINT: PSOPAT
VARIABLES: DFN                          TYPE: Input
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY
 SUBSCRIBING DETAILS:   Added 12/16/25, effective with patch PSO*7.0*819
 calling component PSOPAT 

NUMBER: 7621                            IA #: 7621
  DATE CREATED: DEC 19, 2025            CUSTODIAL PACKAGE: INTEGRATED BILLING
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: IBINUT1                      NAME: Indian Attestation Data Access 
  ID: IBINUT1
 GENERAL DESCRIPTION:   Routine INDGET^IBINUT1 gathers the needed Indian
 Attestation information to assist Integrated Billing in determining whether a
 copay should be charged based on a Veteran's Indian Attestation Information.  
  STATUS: Active
KEYWORDS: INTEGRATED BILLING
COMPONENT/ENTRY POINT: $$INDGET
 COMPONENT DESCRIPTION:   Gathers the needed Indian Attestation information to
 assist Integrated Billing in determining whether a copay should be charged
 based on a Veteran's Indian Attestation Information.                  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IEN from the Patient file (#2).  
VARIABLES: FUNCTION RETURNS             TYPE: Output
 VARIABLES DESCRIPTION:   Indian Self-Identification Flag (2/.571) Indian
 Self-Identification Start Date (2/.572) Indian Self-Identification End Date
 (2/.574) 
SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE
 SUBSCRIBING DETAILS:   Added 12/19/25 effective with patch PRCA*4.5*462, which
 gathers the needed Indian Attestation information to assist Integrated Billing
 in determining whether a copay should be charged based on a Veteran's Indian
 Attestation Information.  

NUMBER: 7622                            IA #: 7622
  DATE CREATED: DEC 29, 2025            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: Routine
  ROUTINE: XUDSIGVALIDATE
  NAME: Kernel - Add Context Option Remediation Status API
  ID: XUDSIGVALIDATE
 GENERAL DESCRIPTION:   This Kernel API is used to retrieve the SAML
 remediation status of a given context option.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
  EXPIRATION DATE: SEP 30, 2027
KEYWORDS: CONTEXT
KEYWORDS: SAML
KEYWORDS: OPTION
KEYWORDS: REMEDIATED
KEYWORDS: STATUS
COMPONENT/ENTRY POINT: $$GETOPTIONSTATUS(CONTEXTOPTION)
 COMPONENT DESCRIPTION:   The $$GETOPTIONSTATUS^XUDSIGVALIDATE extrinsic
 function returns the SAML remediation status of the provided context option.  
VARIABLES: CONTEXTOPTION                TYPE: Input
 VARIABLES DESCRIPTION:   (required) The name of the context option (in
 uppercase). This name is a pointer to FileMan #19 OPTION.  
VARIABLES: returns                      TYPE: Output
 VARIABLES DESCRIPTION:   Returns: 
                             
 Remediated (1) - The context option is remediated and we expect a valid SAML
 token to access the context option.  
                             
 Not Remediated (0) - The context option is not remediated, or the status is
 unknown,and we do not expect a valid SAML to access the context option.  

NUMBER: 7623                            IA #: 7623
  DATE CREATED: JAN 13, 2026
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7623
  STATUS: Pending

NUMBER: 7624                            IA #: 7624
  DATE CREATED: JAN 13, 2026
  NAME: GIVE THIS DBIA A BETTER NAME THAN DBIA7624
  STATUS: Pending

NUMBER: 7625                            IA #: 7625
  FILE NUMBER: 2                        GLOBAL ROOT: DPT
  DATE CREATED: JAN 13, 2026            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: DATA MIGRATION PATIENT FILE     ID: DPT
  STATUS: Pending
SUBSCRIBING PACKAGE: ONCOLOGY

NUMBER: 7626                            IA #: 7626
  FILE NUMBER: 4                        GLOBAL ROOT: DIC(4
  DATE CREATED: JAN 13, 2026            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: DATA MIGRATION INSTITUTION FILE
  ID: DIC(4                             STATUS: Pending
SUBSCRIBING PACKAGE: ONCOLOGY

NUMBER: 7627                            IA #: 7627
  FILE NUMBER: 4.11                     GLOBAL ROOT: DIC(4.11
  DATE CREATED: JAN 13, 2026            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: DATA MIGRATION AGENCY FILE      ID: DIC(4.11
  STATUS: Pending
SUBSCRIBING PACKAGE: ONCOLOGY

NUMBER: 7628                            IA #: 7628
  FILE NUMBER: 5                        GLOBAL ROOT: DIC(5
  DATE CREATED: JAN 14, 2026            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: DATA MIGRATION STATE FILE       ID: DIC(5
  STATUS: Pending
SUBSCRIBING PACKAGE: ONCOLOGY

NUMBER: 7629                            IA #: 7629
  FILE NUMBER: 5.11                     GLOBAL ROOT: VIC(5.11
  DATE CREATED: JAN 14, 2026            CUSTODIAL PACKAGE: 1
  USAGE: Private                        TYPE: File
  NAME: DATA MIGRATION ZIP CODE FILE    ID: VIC(5.11
  STATUS: Pending
SUBSCRIBING PACKAGE: ONCOLOGY

NUMBER: 7630                            IA #: 7630
  FILE NUMBER: 120.51                   GLOBAL ROOT: GMRD(120.51
  DATE CREATED: JAN 27, 2026
  CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS
  USAGE: Controlled Subscription        TYPE: File
  NAME: READ ABBREVIATION FIELD IN GMRV VITAL TYPE FILE
  ID: GMRD(120.51
GLOBAL REFERENCE: GRMD(120.51,D0,0
FIELD NUMBER: 1                         FIELD NAME: ABBREVIATION
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field contains the abbreviation for this vital type. 
 
 GENERAL DESCRIPTION:   This integration control agreement is a companion to
 agreement #4791. It allows subscribers to read the ABBREVIATION field (#1) in
 the GMRV VITAL TYPE file (#120.51) in preparing to call the GMVHS routine.  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: HEALTH SUMMARY
 SUBSCRIBING DETAILS:   Health Summary will use this agreement to lookup the
 abbreviation for a given vital type for use in calling EN1^GMVHS.  

NUMBER: 7631                            IA #: 7631
  FILE NUMBER: 123                      GLOBAL ROOT: GMR(123,
  DATE CREATED: FEB 09, 2026
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  NAME: Imaging populates REQUEST/CONSULTATION file (#123)
  ID: GMR(123,
GLOBAL REFERENCE: GMR(123,DA,
FIELD NUMBER: .01                       FIELD NAME: FILE ENTRY DATE
  LOCATION: 0;1                         ACCESS: Write w/Fileman
FIELD NUMBER: .02                       FIELD NAME: PATIENT NAME
  LOCATION: 0;2                         ACCESS: Write w/Fileman
FIELD NUMBER: .04                       FIELD NAME: PATIENT LOCATION
  LOCATION: 0;4                         ACCESS: Write w/Fileman
FIELD NUMBER: .05                       FIELD NAME: ORDERING FACILITY
  LOCATION: 0;21                        ACCESS: Write w/Fileman
FIELD NUMBER: 1                         FIELD NAME: TO SERVICE
  LOCATION: 0;5                         ACCESS: Write w/Fileman
FIELD NUMBER: 1.01                      FIELD NAME: CLINICAL PROCEDURE
  LOCATION: 1;1                         ACCESS: Write w/Fileman
FIELD NUMBER: 2                         FIELD NAME: FROM
  LOCATION: 0;6                         ACCESS: Write w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DATE OF REQUEST
  LOCATION: 0;7                         ACCESS: Write w/Fileman
FIELD NUMBER: 4                         FIELD NAME: PROCEDURE/REQUEST TYPE
  LOCATION: 0;8                         ACCESS: Write w/Fileman
FIELD NUMBER: 5                         FIELD NAME: URGENCY
  LOCATION: 0;9                         ACCESS: Write w/Fileman
FIELD NUMBER: 6                         FIELD NAME: PLACE OF CONSULTATION
  LOCATION: 0;10                        ACCESS: Write w/Fileman
FIELD NUMBER: 7                         FIELD NAME: ATTENTION
  LOCATION: 0:11                        ACCESS: Write w/Fileman
FIELD NUMBER: 8                         FIELD NAME: CPRS STATUS
  LOCATION: 0:12                        ACCESS: Write w/Fileman
FIELD NUMBER: 9                         FIELD NAME: LAST ACTION TAKEN
  LOCATION: 0:13                        ACCESS: Write w/Fileman
FIELD NUMBER: 10                        FIELD NAME: SENDING PROVIDER
  LOCATION: 0:14                        ACCESS: Write w/Fileman
FIELD NUMBER: 11                        FIELD NAME: RESULT
  LOCATION: 0;15                        ACCESS: Write w/Fileman
FIELD NUMBER: 12                        FIELD NAME: MODE OF ENTRY
  LOCATION: 0;16                        ACCESS: Write w/Fileman
FIELD NUMBER: 13                        FIELD NAME: REQUEST TYPE
  LOCATION: 0;17                        ACCESS: Write w/Fileman
FIELD NUMBER: 14
  FIELD NAME: SERVICE RENDERED AS IN OR OUT
  LOCATION: 0;18                        ACCESS: Write w/Fileman
FIELD NUMBER: 15                        FIELD NAME: SIGNIFICANT FINDINGS
  ACCESS: Write w/Fileman
FIELD NUMBER: 16                        FIELD NAME: TIU RESULT NARRATIVE
  LOCATION: 0;20                        ACCESS: Write w/Fileman
FIELD NUMBER: 17                        FIELD NAME: CLINICALLY INDICATED DATE
  LOCATION: 0;24                        ACCESS: Write w/Fileman
FIELD NUMBER: 30                        FIELD NAME: PROVISIONAL DIAGNOSIS
  LOCATION: 30;1                        ACCESS: Write w/Fileman
FIELD NUMBER: 80                        FIELD NAME: UNIQUE CONSULT ID
  LOCATION: UCID;1                      ACCESS: Write w/Fileman
FIELD NUMBER: 20                        FIELD NAME: REASON FOR REQUEST
  LOCATION: 123.01;.01                  ACCESS: Write w/Fileman
 GLOBAL DESCRIPTION:   Patch MAG*3.0*362 implements an automatic
 consult/procedure order capability for handling DICOM Point of Care imaging
 devices.  
 GENERAL DESCRIPTION:   Imaging patch MAG*3.0*362 automatically creates
 consult/procedure orders for handling DICOM images from Point of Care devices. 
 
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   Added 3/11/26, effective with patch MAG*3.0*362, when a
 DICOM image for a Point of Care device is processed, a consult or a procedure 
 will be created automatically.  

NUMBER: 7632                            IA #: 7632
  DATE CREATED: FEB 09, 2026            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: Other
  ROUTINE: PSOBPSU1                     NAME: EHM DISCONTINUE RX
  ID: PSOBPSU1
 GENERAL DESCRIPTION:   EHM*1.0*8 will automate the process to discontinue any
 prescription that has been migrated to the Federal Electronic Health Record
 (FEHR) with a status of ACTIVE, SUSPENDED, HOLD, NON-VERIFIED, DRUG
 INTERACTIONS or PROVIDER HOLD and finishing date in the last year.  
  
 This is a one-time run of this patch and takes place AFTER the VistA site has
 been converted to FEHR.  
  
 Files updated with discontinue status information are: 
  
 ^PSRX, ^PS(52.4, ^PS(52.5 
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DISCONTINUE
KEYWORDS: PRESCRIPTONS
KEYWORDS: EHM*1*8
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   Added 2/26/26, effective with EHM*1.0*8. This is a
 one-time run of this patch and takes place AFTER the VistA site has been
 converted to FEHR.  

NUMBER: 7633                            IA #: 7633
  DATE CREATED: FEB 09, 2026            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        NAME: THIS ICR IS WITHDRAWN
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION

NUMBER: 7634                            IA #: 7634
  DATE CREATED: FEB 09, 2026            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PSOCAN1                      NAME: DISC RX PSOCAN1
  ID: PSOCAN1                           STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
KEYWORDS: PRESCRIPTIONS
KEYWORDS: DISCONTINUE
KEYWORDS: PSOCAN1
KEYWORDS: EHM*1*8
COMPONENT/ENTRY POINT: AREC
 COMPONENT DESCRIPTION:   RX Cancel.  
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION

NUMBER: 7635                            IA #: 7635
  DATE CREATED: FEB 09, 2026            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PSOCAN2                      NAME: DISC RX PSOCAN2
  ID: PSOCAN2                           STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
KEYWORDS: PRESCRIPTIONS
KEYWORDS: DISCONTINUE
KEYWORDS: PSOCAN2
KEYWORDS: EHM*1*8
COMPONENT/ENTRY POINT: NVER
 COMPONENT DESCRIPTION:   Put prescription in non-verified status.  
VARIABLES: DA MUST BE DEFINED           TYPE: Used
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION

NUMBER: 7636                            IA #: 7636
  DATE CREATED: FEB 09, 2026            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PSOUTL                       NAME: DISC RX PSOUTL
  ID: PSOUTL                            STATUS: Withdrawn
  DURATION: Till Otherwise Agreed
KEYWORDS: PRESCRIPTIONS
KEYWORDS: DISCONTINUE
KEYWORDS: PSOUTL
KEYWORDS: EHM*1*8
COMPONENT/ENTRY POINT: CHKCMOP
 COMPONENT DESCRIPTION:   Check if an RX is Transmitted/Retransmitted to CMOP
 and send alert mail.  
VARIABLES: RX                           TYPE: Input
 VARIABLES DESCRIPTION:   PRESCRIPTION (#52) IEN.  
VARIABLES: REA                          TYPE: Input
 VARIABLES DESCRIPTION:   Reason DC's "A" = admission, "D" = death.  
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION

NUMBER: 7637                            IA #: 7637
  FILE NUMBER: 52.4                     GLOBAL ROOT: PS(DA,
  DATE CREATED: FEB 10, 2026            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PSOHLSN1                     NAME: DISC RX PSOHLSN1
  ID: PSOHLSN1
GLOBAL REFERENCE: PSRX(DA,
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: PSOHLSN1
KEYWORDS: DISCONTINUE
KEYWORDS: PRESCRIPTIONS
KEYWORDS: EHM*1*8
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Delete refill requests.  
VARIABLES: PSORX                        TYPE: Input
VARIABLES: STAT                         TYPE: Input
VARIABLES: PHARMST                      TYPE: Input
VARIABLES: COM                          TYPE: Input
VARIABLES: 'A'                          TYPE: Input
 VARIABLES DESCRIPTION:   AUTO DC 
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION

NUMBER: 7638                            IA #: 7638
  FILE NUMBER: 52.4                     GLOBAL ROOT: PS(52.4,DA,0
  DATE CREATED: FEB 10, 2026            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Controlled Subscription        TYPE: File
  NAME: DISC RX 52.4                    ID: PS(52.4,DA,0
GLOBAL REFERENCE: PS(52.4,DA,0
FIELD NUMBER: .01                       FIELD NAME: RX#
  LOCATION: 0;1                         ACCESS: Direct Global R/W & w/Fileman
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: DISCONTINUE
KEYWORDS: PRESCRIPTIONS
KEYWORDS: 52.4
KEYWORDS: EHM*1.0*8
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION

NUMBER: 7639                            IA #: 7639
  FILE NUMBER: 409.68                   GLOBAL ROOT: SCE
  DATE CREATED: FEB 20, 2026            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  NAME: SET OUTPATIENT ENCOUNTER CHECK OUT PROCESS COMPLETION
  ID: SCE
GLOBAL REFERENCE: SCE(D0
FIELD NUMBER: .07                       FIELD NAME: CHECK OUT PROCESS COMPLETION
  LOCATION: 409.68,.07                  ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: ENCOUNTER CHECKOUT
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 3/11/26 effective with patch PX*1*250. Camp
 LeJeune, COMPACT Act, and Toxic Exposure Risk Activity are Special Authorities
 (SAs) created by Congress and the ability to capture the encounter
 applicability of these SAs needs to be added to PCE. Patch PX*1*250 implements
 a new API that returns a veteran's Service Connect and Special Authority
 (SC/SA) eligibilities on the date of the encounter. This API includes Camp 
 LeJeune, COMPACT Act, and Toxic Exposure Risk Activity.  
  
 Currently, the status of a PCE encounter (ACTION REQUIRED or CHECKED OUT) is
 determined by Scheduling and stored in the OUTPATIENT ENCOUNTER file. 
 Applications that need to determine the status of an encounter use the API
 $$STATUS^SDPCE.  
  
 Encounter applicability for Camp LeJeune, COMPACT Act, and Toxic Exposure Risk
 Activity can be implemented with the release of PX*1*250 if PCE determines the
 encounter status and causes it to be set in the OUTPATIENT ENCOUNTER file by
 setting CHECK OUT PROCESS COMPLETION.  

NUMBER: 7640                            IA #: 7640
  GLOBAL ROOT: DD('IX'                  DATE CREATED: MAR 03, 2026
  CUSTODIAL PACKAGE: 1                  USAGE: Private
  TYPE: File
  NAME: FIND NEW-STYLE CROSS-REFERENCES AND INDEXES
  ID: DD('IX'                           STATUS: Active
  DURATION: Till Otherwise Agreed
KEYWORDS: NEW-STYLE CROSS-REFERENCE
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 5/19/26, effective with patch PX*1*251 PCE's
 Visit Merge Utility needs to identify all fields that are pointers to the
 Visit file and determine which of those fields point to a specific Visit file
 entry. To make this process efficient and usable, it requires locating and
 reading indexes on those Visit file pointer fields. When the index is created
 by a new-style cross-reference, that information is found in ^DD("IX"). PCE is
 requesting permission to read the following nodes of ^DD("IX"): 
  
  ^DD("IX","B",FILENUM,XREFNUM) 
  ^DD("IX",XREFNUM,11.1,1,0) 
  ^DD("IX",XREFNUM,1) 

NUMBER: 7641                            IA #: 7641
  DATE CREATED: MAR 05, 2026
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: GMRCHL7U                     NAME: Recording Auditing Information
  ID: GMRCHL7U
 GENERAL DESCRIPTION:   Imaging needs to call AUDIT0^GMRCHL7U.  This call is
 made after creating a Consult to record auditing information.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: GMRC HL7
COMPONENT/ENTRY POINT: AUDIT0
VARIABLES: GMRCA                        TYPE: Input
 VARIABLES DESCRIPTION:   1 - Pointer to REQUEST ACTION TYPES file (#123.1) -
 ENTERED IN CPRS 
VARIABLES: GMRCTRLC                     TYPE: Input
 VARIABLES DESCRIPTION:   "NW" - HL7 CONTROL CODE (new) 
VARIABLES: GMRCO                        TYPE: Input
 VARIABLES DESCRIPTION:   GMRCIEN of new consult/procedure 
VARIABLES: GMRCORNP                     TYPE: Input
 VARIABLES DESCRIPTION:   Ordering Provider IEN in ^VA(200) 
VARIABLES: GMRCPLCR                     TYPE: Input
 VARIABLES DESCRIPTION:   Order Placer, person performing the exam, IEN in
 ^VA(200) 
SUBSCRIBING PACKAGE: IMAGING
 SUBSCRIBING DETAILS:   Added 4/8/26, effective with patch MAG*3.0.362.  VistA
 Imaging will be for Point of Care DICOM imaging devices.  They differ from
 traditional DICOM devices for which the order is placed and then the
 examination is performed, for POC DICOM devices, the examination is performed
 first and the order is placed afterwards.  This requires VistA Imaging to 
 create the order when the DICOM images from the devices are processed.  

NUMBER: 7642                            IA #: 7642
  FILE NUMBER: 44                       GLOBAL ROOT: SC(DA,
  DATE CREATED: MAR 10, 2026            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: File
  NAME: Conversion data appointment list
  ID: SC(DA,
GLOBAL REFERENCE: SC(DA,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TYPE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: STOP CODE NUMBER
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1900,.01                  FIELD NAME: APPOINTMENT DATE/TIME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1900,8                    FIELD NAME: DATE APPOINTMENT MADE
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 1900,310                  FIELD NAME: APPOINTMENT CANCELLED?
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   Added 3/12/26, effective with patch EHM*1*20. This
 patch will produce a list of appointments used during conversion to the 
 Federal EHR.  It needs to read data about selected clinics and about 
 appointments scheduled in those clinics.  

NUMBER: 7643                            IA #: 7643
  FILE NUMBER: 409.85                   GLOBAL ROOT: SDEC(409.85
  DATE CREATED: MAR 10, 2026            CUSTODIAL PACKAGE: SCHEDULING
  USAGE: Private                        TYPE: File
  NAME: Conversion data appointment requests
  ID: SDEC(409.85
GLOBAL REFERENCE: SDEC(409.85,DA,
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 8                         FIELD NAME: REQ SPECIFIC CLINIC
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 22                        FIELD NAME: CID/PREFERRED DATE OF APPT
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 23                        FIELD NAME: CURRENT STATUS
  LOCATION: 0;17                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 41                        FIELD NAME: MULTIPLE APPOINTMENT RTC
  LOCATION: 3;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 43.3,.01                  FIELD NAME: CHILD REQUEST
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 43.3,.02                  FIELD NAME: MULT APPTS MADE
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   EHM*1*20 produces a list of return to clinic
 appointment requests used during conversion to the Federal EHR.  It needs to
 read data about selected appointment requests.  

NUMBER: 7644                            IA #: 7644
  FILE NUMBER: 103                      GLOBAL ROOT: ORAM(103,
  DATE CREATED: MAR 10, 2026
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: File
  NAME: Conversion data anti-coagulation patients
  ID: ORAM(103,
GLOBAL REFERENCE: ORAM(103,DA,0
FIELD NUMBER: 4                         FIELD NAME: START DATE
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: STOP DATE
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 15                        FIELD NAME: COMPLEXITY
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   Added 3/16/26, effective with patch EHM*1*20. This
 patch produce a list of patients receiving anti-coagulation therapy used
 during conversion to the Federal EHR.  It needs to read flowsheet data.  

NUMBER: 7645                            IA #: 7645
  FILE NUMBER: 130                      GLOBAL ROOT: SRF(
  DATE CREATED: MAR 10, 2026            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: File
  NAME: Conversion data surgery schedule
  ID: SRF(
GLOBAL REFERENCE: SRF(
FIELD NUMBER: .01                       FIELD NAME: PATIENT
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   EHM*1*20 reads the "AMM" cross-reference of file #130. 
 It extracts the operation room, scheduled start date and time.  From the
 pointer (ien), it extracts the patient.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   Added 3/12/26, effective with patch EHM*1*20. This
 patch will produce a list of surgeries scheduled on or after the date of 
 conversion to the new Federal EHR.  

NUMBER: 7646                            IA #: 7646
  FILE NUMBER: 131.7                    GLOBAL ROOT: SRS(
  DATE CREATED: MAR 10, 2026            CUSTODIAL PACKAGE: SURGERY
  USAGE: Private                        TYPE: File
  NAME: Data conversion surgery schedule
  ID: SRS(
GLOBAL REFERENCE: SRS(DA,0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   Added 3/12/26, effective with patch EHM*1*20. This
 patch will produce a list of surgeries scheduled on or after the date of 
 conversion to the new Federal EHR.  

NUMBER: 7647                            IA #: 7647
  FILE NUMBER: 790                      GLOBAL ROOT: WV(790
  DATE CREATED: MAR 10, 2026            CUSTODIAL PACKAGE: WOMEN'S HEALTH
  USAGE: Private                        TYPE: File
  NAME: Conversion data women's health reports
  ID: WV(790
GLOBAL REFERENCE: WV(790,DA,
FIELD NUMBER: 40                        FIELD NAME: PREGNANCY STATUSES
  LOCATION: 4;0                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 40,6                      FIELD NAME: ENTERED IN ERROR
  LOCATION: 0;6                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 40,21                     FIELD NAME: PREGNANCY STATE
  LOCATION: 2;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 40,44                     FIELD NAME: PREGNANCY END DATE
  LOCATION: 4;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 40,45                     FIELD NAME: REASON PREGNANCY ENDED
  LOCATION: 4;5                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   EHM*1*20 produces two (2) lists: 1) patients who are
 currently pregnant and 2) patients who are post-partum within the last year. 
 They are used during conversion to the new Federal EHR.  

NUMBER: 7648                            IA #: 7648
  FILE NUMBER: 52                       GLOBAL ROOT: PSRX(
  DATE CREATED: MAR 23, 2026            CUSTODIAL PACKAGE: OUTPATIENT PHARMACY
  USAGE: Private                        TYPE: File
  NAME: Conversion data long-acting injections report
  ID: PSRX(
GLOBAL REFERENCE: PSRX(DA,
FIELD NUMBER: 1                         FIELD NAME: ISSUE DATE
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
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: 9                         FIELD NAME: # OF REFILLS
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 26.1                      FIELD NAME: CANCEL DATE
  LOCATION: 3;5                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   Added 4/6/26 effective with patch EHM*1*20. This patch 
 produces a list of patients receiving long-acting injections (LAI).  The list
 is used during conversion to the new Federal EHR.  

NUMBER: 7649                            IA #: 7649
  DATE CREATED: MAR 25, 2026            CUSTODIAL PACKAGE: MASTER PATIENT INDEX
  USAGE: Private                        TYPE: Remote Procedure
  NAME: XUS MVI NEW PERSON FLD MNTR
  REMOTE PROCEDURE: XUS MVI NEW PERSON FLD MNTR
 GENERAL DESCRIPTION:   KERNEL is aware that this RPC has been created as part
 of the Enterprise User Identity Patch XU*8.0*799.  
  
 This private RPC will be used exclusively by the MPI to allow visibility into
 the NEW PERSON FIELD MONITOR (#8933.1) file to enable more active
 troubleshooting/resolution of future issues encountered at sites through the
 viewing/editing of entries. In addition, having the ability to add a Pending
 entry to this file will also allow MPI to automatically update the VistA IDs
 list for the user by removing their terminated and/or disusered historical
 entries.  
  
 This RPC allows execution of the following processes on the NEW PERSON FIELD
 MONITOR (#8933.1) file: 
  
     - Retrieve the First Pending Entry 
     - Retrieve the Last Entry for a DUZ in the file (Regardless of Status) 
     - Retrieve ALL Pending Entries for a DUZ 
     - Flip Requires Transmission Flag for First Pending entry for a DUZ 
     - Flip Requires Transmission Flag for ALL Pending entries for a DUZ 
     - Add a new Pending Record for a DUZ 
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: XUS MVI NEW PERSON FLD MNTR
KEYWORDS: XTV(8933.1
KEYWORDS: NEW PERSON FIELD MONITOR
KEYWORDS: XTV(8933.1,'ACXMIT',
KEYWORDS: 8933.1

NUMBER: 7650                            IA #: 7650
  DATE CREATED: MAR 25, 2026
  CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: PXAPI                        NAME: VISIT DETAIL
  ID: PXAPI
 GENERAL DESCRIPTION:   This ICR allows for a calling application to retrieve
 information from the visit file that can be used to determine if the visit is
 billable.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
KEYWORDS: VISIT DETAIL
KEYWORDS: VISITDETAIL
KEYWORDS: PXAPI
KEYWORDS: SPECIAL AUTHORITIES
COMPONENT/ENTRY POINT: VISITDETAIL
 COMPONENT DESCRIPTION:   This API accepts a visit IEN value. It returns
 information from the visit file to help determine if this visit is billable.  
VARIABLES: VISIT                        TYPE: Input
 VARIABLES DESCRIPTION:   This is the IEN of the visit from the VISIT file,
 #9000010.  
VARIABLES: RESULT                       TYPE: Output
 VARIABLES DESCRIPTION:   The result array returns information from the Visit
 file in internal format : RESULT("DATE/TIME") = VISIT/ADMIT DATE&TIME, field #
 .01 RESULT("PATIENT") = PATIENT NAME, field #.05 RESULT("LOCATION") = LOC. OF
 ENCOUNTER, field #.06 RESULT("SERVICE CATEGORY") = SERVICE CATEGORY, field
 #.07 RESULT("CLINIC STOP") = DSS ID, field #.08 RESULT("SPECIAL AUTHORITIES")
 = The special authorities assigned to the visit. This will contains the
 special authorities assigned on the 800 node or in the 900 multiple released
 with patch PX*1.0*244. The format for the SPECIAL AUTHORITIES for individual
 values is this format.  
  
 RESULT("SPECIAL AUTHORITIES",X,0)=IEN^VALUE X is increment counter, this will
 be a positive value.  IEN is the internal number from file #820 for the
 Special Authorities.  VALUE can be set to 1 for Yes, the Special Authority
 applies to the visit; 0, the Special Authority does not apply to the visit;
 -1, the user has not answer if the Special Authority applies to the visit.  
  
 Example: CPRS33BDEV>D VISITDETAIL^PXAPI(.RESULT,7910) 
  
 CPRS33BDEV>ZW RESULT RESULT("CLINIC STOP")=141 
 RESULT("DATE/TIME")=3260325.105301 RESULT("LOCATION")=500 
 RESULT("PATIENT")=100840 RESULT("SERVICE CATEGORY")="A" RESULT("SPECIAL
 AUTHORITIES")=7 RESULT("SPECIAL AUTHORITIES",1,0)="2^0" RESULT("SPECIAL
 AUTHORITIES",2,0)="8^1" RESULT("SPECIAL AUTHORITIES",3,0)="4^0" 
 RESULT("SPECIAL AUTHORITIES",4,0)="7^1" RESULT("SPECIAL
 AUTHORITIES",5,0)="3^0" RESULT("SPECIAL AUTHORITIES",6,0)="6^-1" 
 RESULT("SPECIAL AUTHORITIES",7,0)="1^1" 

NUMBER: 7651                            IA #: 7651
  DATE CREATED: APR 02, 2026            CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: RCDMCRUT                     NAME: Access to Routine RCDMCRUT
  ID: RCDMCRUT
 GENERAL DESCRIPTION:   The purpose of this API is to provide a way for
 application to calculates the Combined Service Connection (SC) % Effective
 Date for a Veteran.  
  STATUS: Active
COMPONENT/ENTRY POINT: GETEFFDT
VARIABLES: RCDFN                        TYPE: Input
 VARIABLES DESCRIPTION:   Patient DFN 
VARIABLES: RCMIN                        TYPE: Input
 VARIABLES DESCRIPTION:   Minimum Disability %  (File #2,  Sub-File #2.04,
 Field #2) 
VARIABLES: RCMAX                        TYPE: Input
 VARIABLES DESCRIPTION:   Maximum Disability %  (File #2,  Sub-File #2.04,
 Field #2) 
VARIABLES: Effective Date               TYPE: Output
 VARIABLES DESCRIPTION:   Calculated Combined SC % Effective Date 
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Added 4/2/26, effective with patch IB*2.0*807.  
 Integrated Billing (IB) application access to this API to properly calculate
 the Combine SC % Effective Date when determining if a bill should go to the
 veteran or cancelled.              

NUMBER: 7652                            IA #: 7652
  FILE NUMBER: 441                      GLOBAL ROOT: PRC(441,
  DATE CREATED: APR 17, 2026            CUSTODIAL PACKAGE: IFCAP
  USAGE: Controlled Subscription        TYPE: File
  NAME: VDIF Microservice Model         ID: PRC(441,
GLOBAL REFERENCE: PRC(441,
FIELD NUMBER: .01                       FIELD NAME: NUMBER
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: .05                       FIELD NAME: SHORT DESCRIPTION
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: .06
  FIELD NAME: CASE CART/TRAY/INSTRUMENT KIT
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: .08                       FIELD NAME: SYNONYM
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: .1                        FIELD NAME: DESCRIPTION
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1                         FIELD NAME: FCP
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: FSC
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: INC
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5                         FIELD NAME: NSN
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 5.5                       FIELD NAME: NSN VERIFIED
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 6                         FIELD NAME: VENDOR
  ACCESS: Write w/Fileman
FIELD NUMBER: 7                         FIELD NAME: HAZARDOUS MATERIAL
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: LAST VENDOR ORDERED
  ACCESS: Read w/Fileman
FIELD NUMBER: 10                        FIELD NAME: MANDATORY SOURCE
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 12                        FIELD NAME: BOC
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 13                        FIELD NAME: SET/PACK ASSEMBLED BY
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 14                        FIELD NAME: DATE ITEM CREATED
  ACCESS: Read w/Fileman
FIELD NUMBER: 15                        FIELD NAME: CREATED BY
  ACCESS: Read w/Fileman
FIELD NUMBER: 16                        FIELD NAME: INACTIVATED ITEM? 
  ACCESS: Read w/Fileman
FIELD NUMBER: 16.5                      FIELD NAME: REPLACEMENT ITEM
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 17                        FIELD NAME: DATE INACTIVATED 
  ACCESS: Read w/Fileman
FIELD NUMBER: 18                        FIELD NAME: INACTIVATED BY
  ACCESS: Read w/Fileman
FIELD NUMBER: 19                        FIELD NAME: MFG PART NO.
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 19.1                      FIELD NAME: SOURCE MFG PART NO.
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 19.2                      FIELD NAME: MFG PART NO.(C) 
  ACCESS: Read w/Fileman
FIELD NUMBER: 20                        FIELD NAME: FOOD GROUP
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 21                        FIELD NAME: SKU
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 22                        FIELD NAME: DRUG TYPE CODE
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 23                        FIELD NAME: REUSABLE ITEM
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 24                        FIELD NAME: SIC CODE
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 25                        FIELD NAME: MANUFACTURER
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 51                        FIELD NAME: NIF ITEM NUMBER
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 52                        FIELD NAME: PRE_NIF SHORT DESCRIPTION
  ACCESS: Read w/Fileman
FIELD NUMBER: 53                        FIELD NAME: DATE UPDATED BY NIF
  ACCESS: Read w/Fileman
FIELD NUMBER: 54                        FIELD NAME: NIF UPDATE DATE
  ACCESS: Read w/Fileman
FIELD NUMBER: 50                        FIELD NAME: PRE_NIF LONG DESCRIPTION
  ACCESS: Read w/Fileman
 GLOBAL DESCRIPTION:   0 node values for ITEM MASTER at Top-File Level.  
GLOBAL REFERENCE: PRC(441,D0,2,
FIELD NUMBER: .01                       FIELD NAME: VENDOR
  ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: UNIT COST
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.5                       FIELD NAME: UNIT OF PURCHASE
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 1.6                       FIELD NAME: PACKAGING MULTIPLE
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2                         FIELD NAME: CONTRACT
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 2.2                       FIELD NAME: CONTRACT EXP. DATE
  ACCESS: Read w/Fileman
FIELD NUMBER: 2.5                       FIELD NAME: DATE OF UNIT PRICE
  ACCESS: Read w/Fileman
FIELD NUMBER: 3                         FIELD NAME: VENDOR STOCK #
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.1                       FIELD NAME: SOURCE VENDOR STOCK #
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3.2                       FIELD NAME: VENDOR STOCK #(C)
  ACCESS: Read w/Fileman
FIELD NUMBER: 4                         FIELD NAME: NDC
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8                         FIELD NAME: MINIMUM ORDER QTY
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 8.5                       FIELD NAME: MAXIMUM ORDER QTY
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 9                         FIELD NAME: REQUIRED ORDER MULTIPLE
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 10                        FIELD NAME: UNIT CONVERSION FACTOR
  ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   Values that belong to the VENDOR Sub-File 441.01 level
 of ITEM MASTER File.  
GLOBAL REFERENCE: PRC(441,D0,4,
FIELD NUMBER: .01                       FIELD NAME: FCP
  ACCESS: Read w/Fileman
FIELD NUMBER: .5                        FIELD NAME: LONG NAME
  ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: PURCHASE ORDER
  ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: SUBACCOUNT
  ACCESS: Both R/W w/Fileman
FIELD NUMBER: 3                         FIELD NAME: PREFERRED VENDOR
  ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   Values that belong to the 441.03 FCP Sub-File of ITEM
 MASTER File.  
GLOBAL REFERENCE: PRC(441,D0,5,
FIELD NUMBER: .01                       FIELD NAME: SYNONYM
  ACCESS: Both R/W w/Fileman
 GLOBAL DESCRIPTION:   SYNONYM Value for 441.05 SYNONYM Sub-File of ITEM MASTER
 File.  
 GENERAL DESCRIPTION:   This interface does not call FileMan Database Server
 (DBS) APIs directly. All data operations are performed through a service
 managed object class. Read requests are satisfied by the microservice's query
 handlers, which retrieve and materialize Item Master objects from the
 service's data access layer and return API; no direct consumer access to
 underlying FileMan files occurs. Write requests (create/update) are processed
 by command handlers that apply validated business rules in the service layer,
 execute persistence through service side adapters. Concurrency controls,
 validation, and referential integrity are enforced within the service. This
 pattern isolates consumers from FileMan, centralizes business rules, and
 ensures consistent updates.  
  
  
 The proposed integration uses an object class model for Item Master data. 
 Consumers interact only with the service's API endpoints. The service 
 encapsulates all persistence and validation logic.  
  STATUS: Active
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 7/13/26, effective with Object Script Class
 API.RESTOAUTHSAML.  This class will use FileMan APIs to Add, Edit, Delete and
 inactive records for all fields in the  ITEM MASTER(441) file.  
  
 Mechanism: Query handlers load domain objects via the service's data access
 layer.  
  
 Behavior: Read operations do not traverse FileMan from the consumer context.
 The service may employ caching and projections to optimize reads while
 preserving consistency.  
  
 Result: Consumers receive fully materialized Item Master objects shaped by the
 object class.  

NUMBER: 7653                            IA #: 7653
  DATE CREATED: JUL 07, 2026            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGMSTAPI                     NAME: KEEP MST HISTORY FILE IN SYNCH
  ID: DGMSTAPI
 GENERAL DESCRIPTION:   When a V HEALTH FACTORS entry for one of the MST health
 factors is deleted the corresponding entry in the MST HISTORY file should also
 be deleted. To do that PCE needs to call the API DELMST^DGMSTAPI.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DELMST_DGMSTAPI
KEYWORDS: REGISTRATION
KEYWORDS: PCE
COMPONENT/ENTRY POINT: DELMST
VARIABLES: MSTIEN                       TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the entry in the MST HISTORY File (#29.11) 
SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER
 SUBSCRIBING DETAILS:   Added 7/9/26, effective with patch PX*1*250 Entries in
 the MST HISTORY file are added using the API NEWSTAT^DGMSTAPI when the patient
 is given one of the health factors that represent the  'Y', 'N', or 'D' MST
 STATUS: 
  
 29.11,3     MST STATUS        0;3 SET (Required) 
  
          'Y' FOR Yes, Screened reports MST; 
          'N' FOR No, Screened does not report MST; 
          'D' FOR Screened Declines to answer; 
          'U' FOR Unknown, not screened; 

NUMBER: 7654                            IA #: 7654
  DATE CREATED: JUL 14, 2026
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  USAGE: Private                        TYPE: Routine
  ROUTINE: ORDDXA                       NAME: Non-VA meds order cancellation
  ID: ORDDXA                            STATUS: Pending
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: DC
VARIABLES: REC                          TYPE: Output
 VARIABLES DESCRIPTION:   Contains the result of the call to DC^ORWDXA.  
VARIABLES: ORID                         TYPE: Input
 VARIABLES DESCRIPTION:   Order IEN.  Pointer to file #100.  
VARIABLES: REASON                       TYPE: Input
 VARIABLES DESCRIPTION:   Order cancellation reason.  Pointer to ORDER REASON
 file (#100.03).  
SUBSCRIBING PACKAGE: ELECTRONIC HEALTH MODERNIZATION
 SUBSCRIBING DETAILS:   A patient's non-VA meds need to be discontinued
 following conversion to the new Federal EHR.  EHM*1*22 includes code that
 scans these meds and marks them discontinued.  It also needs to cancel the
 order associated with the meds.  
  
 EHM*1*22 needs to call DC^ORWDXA to do so.  

NUMBER: 7655                            IA #: 7655
  FILE NUMBER: 391.91                   GLOBAL ROOT: DGCN(391.91
  DATE CREATED: JUL 24, 2026            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Controlled Subscription        TYPE: File
  NAME: DVBA access to File #391.91     ID: DGCN(391.91
GLOBAL REFERENCE: DGCN(391.91,
FIELD NUMBER: 10                        FIELD NAME: ASSIGNING AUTHORITY
  LOCATION: 2:1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   ASSIGNING AUTHORITY stores a portion of the data used to
 assemble fully qualified identifiers used for either the HL7 v2.4 or v3.0
 standard.  It is based on the Health Level Seven (HL7) standardized table 0363
 and contains the universal ID subcomponent of the assigning authority 
 component in the standard PID-3 identifier.  
GLOBAL REFERENCE: DGCN(391.91,'ASID'
 GENERAL DESCRIPTION:   CAPRI GUI is using EDIPI as an additional replacement
 field for SSNR along with the ICN.  CAPRI would like read access to field 10
 and the ASID xref of File DGCN(391.91).  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE

NUMBER: 7656                            IA #: 7656
  DATE CREATED: AUG 05, 2026            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DG MPI DOD UPDATER              REMOTE PROCEDURE: DG MPI DOD UPDATER
 GENERAL DESCRIPTION:   In support of sites transitioning to Oracle Health
 Millennium, the Master Patient Index (MPI) team requests permission to
 exclusively use this new REGISTRATION RPC [DG MPI DOD UPDATER] to continue to
 give site staff the ability to perform Date of Death entries, edits and/or
 removals. This RPC will ensure operational continuity to prevent a gap in
 functionality at the Veteran Affairs Medical Centers (VAMCs).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DG MPI DOD UPDATER
KEYWORDS: DPT
KEYWORDS: PATIENT
KEYWORDS: DEATH
KEYWORDS: MPI
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   Added 9/10/26, effective with patch MPI*1.0*166 The
 Master Veteran Index (MVI) project beginning with patch MPI*1.0*166 will use
 this Remote Procedure Call (RPC) to remotely update Date of Death fields for a
 patient at a site.  

NUMBER: 7657                            IA #: 7657
  DATE CREATED: AUG 25, 2026
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  USAGE: Private                        TYPE: Remote Procedure
  NAME: RG REM ACTIVITY                 REMOTE PROCEDURE: RG REM ACTIVITY
 GENERAL DESCRIPTION:   To assist with troubleshooting at the Veterans Affairs
 Medical Centers (VAMCs), the Master Patient Index (MPI) team requests
 permission to use the CIRN RPC [RG REM ACTIVITY] to query/retrieve HL7 message
 information from the ADT/HL7 PIVOT (#391.71) file and exception info from the
 CIRN HL7 EXCEPTION LOG (#991.1) file for a selected patient identified by 
 their Integration Control Number (ICN) or Social Security Number (SSN).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RG REM ACTIVITY
KEYWORDS: DPT
KEYWORDS: PATIENT
KEYWORDS: MPI
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   Added 9/10/26, effective with patch MPI*1.0*8.  The
 Master Patient Index (MPI) project beginning with patch MPI*1.0*8 has been
 using this Remote Procedure Call (RPC) to remotely retrieve Health Level Seven
 (HL7) message and exception information for a patient.  

NUMBER: 7658                            IA #: 7658
  DATE CREATED: AUG 25, 2026
  CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK
  USAGE: Private                        TYPE: Remote Procedure
  NAME: RG REMOTE HL7 TASK              REMOTE PROCEDURE: RG REMOTE HL7 TASK
 GENERAL DESCRIPTION:   To assist with troubleshooting at the Veterans Affairs
 Medical Centers (VAMCs), the Master Patient Index (MPI) team requests
 permission to use the CIRN RPC [RG REMOTE HL7 TASK] to query/retrieve
 currently running HL7 tasks for a specific site.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: RG REMOTE HL7 TASK
KEYWORDS: MPI
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   Added 9/10/26, effective with patch MPI*1.0*3 The
 Master Patient Index (MPI) project beginning with patch MPI*1.0*3 has been
 using this Remote Procedure Call (RPC) to remotely retrieve a report of
 currently running Health Level Seven (HL7) tasks at a site.  

NUMBER: 7659                            IA #: 7659
  DATE CREATED: AUG 26, 2026            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Remote Procedure
  NAME: DG UPDATE NAME COMPONENTS
  REMOTE PROCEDURE: DG UPDATE NAME COMPONENTS
 GENERAL DESCRIPTION:   The REGISTRATION (DG) package with the release of patch
 DG*5.3*974 included an RPC [DG UPDATE NAME COMPONENTS] that provided a means
 for retrieving, as well as editing a Patient's Name (Last, First, Middle, and
 Suffix) at a specified Veterans Affairs Medical Center (VAMC).  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: DG UPDATE NAME COMPONENTS
KEYWORDS: DPT
KEYWORDS: PATIENT
KEYWORDS: MPI
KEYWORDS: NAME
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   Added 9/17/26, effective with patch MPI*1.0*125. The
 Master Patient Index (MPI) project beginning with patch MPI*1.0*125 has been
 using this Remote Procedure Call (RPC) to remotely retrieve the Name details
 of a PATIENT record at a site to view/edit as needed to assist with 
 troubleshooting/correcting issues.  

NUMBER: 7660                            IA #: 7660
  DATE CREATED: AUG 26, 2026
  CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA
  USAGE: Private                        TYPE: Remote Procedure
  NAME: MPIF UPDATE NAME COMP FLAG
 GENERAL DESCRIPTION:   The Master Patient Index VistA (MPIF) package with the
 release of patch MPIF*1.0*69 included an RPC [MPIF UPDATE NAME COMP FLAG] that
 provided a means for setting/retrieving the Name Components flag in VistA,
 which controls how names passed in the Health Level Seven (HL7) ADT-A31 update
 messages to VistA are processed.  If the flag is NULL/0 then the name parts
 are filed into the PATIENT file (#2) field (#.01). If the flag is 1 then the
 name parts are filed into the NAME COMPOPNENTS file (#20).  
  STATUS: Withdrawn                     DURATION: Till Otherwise Agreed
KEYWORDS: MPIF UPDATE NAME COMP FLAG
KEYWORDS: DPT
KEYWORDS: PATIENT
KEYWORDS: MPI
KEYWORDS: NAME
SUBSCRIBING PACKAGE: MASTER PATIENT INDEX
 SUBSCRIBING DETAILS:   The Master Patient Index (MPI) project beginning with
 patch MPI*1.0*125 has been using this Remote Procedure Call (RPC) to remotely
 view/set this flag to control how names passsed in the HL7 ADT-A31 messages to 
 VistA are processed.  

NUMBER: 7661                            IA #: 7661
  FILE NUMBER: 162.3                    GLOBAL ROOT: FBAACNH(
  DATE CREATED: SEP 10, 2026            CUSTODIAL PACKAGE: FEE BASIS
  USAGE: Controlled Subscription        TYPE: File
  NAME: Access to The FEE CNH ACTIVITY File(#162.3)
  ID: FBAACNH(
GLOBAL REFERENCE: FBAACNH(DA,
FIELD NUMBER: .01                       FIELD NAME: DATE/TIME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The date and time of this activity (admission, discharge
 or transfer).  
FIELD NUMBER: 1                         FIELD NAME: VETERAN
  LOCATION: 0;2                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The name of the Fee Basis patient associated with this
 activity.  
FIELD NUMBER: 2                         FIELD NAME: ACTIVITY TYPE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Entry into this field indicates whether activity was an
 admission, discharge or transfer.  
FIELD NUMBER: 5                         FIELD NAME: ADMISSION TYPE
  LOCATION: 0;6                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Field populated for activity types of 'admission' only. 
 Indicates the type of admission for veteran.  
FIELD NUMBER: 6                         FIELD NAME: TRANSFER TYPE
  LOCATION: 0;7                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Field is populated for activity type of 'transfer' only. 
 Indicates the type of transfer for each veteran.  
FIELD NUMBER: 7                         FIELD NAME: DISCHARGE TYPE
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Field is populated for activity type of 'discharge' only. 
 Indicates the type of discharge for each veteran.  
FIELD NUMBER: 8                         FIELD NAME: NURSING HOME
  LOCATION: 0;8                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The date and time of this activity (admission, discharge
 or transfer).  
GLOBAL REFERENCE: FBAACNH('AC',
 GENERAL DESCRIPTION:   This ICR will allow READ w/Fileman to access the FEE
 CNH ACTIVITY file #162.3 for fields .01, 1, 2, 8, & 'AC' cross-references.  
  STATUS: Active
SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE
 SUBSCRIBING DETAILS:   Added 9/10/26, effective with DBVA*2.7*258 CAPRI CNH
 reporting will need to READ W/FILEMAN Fields .01,1, 2, 8 and the 'AC'
 cross-reference from file 162.3 Updated 9/11/26,effective with DBVA*2.7*258 
 fields 5, 6, and 7 added to this ICR 

NUMBER: 7662                            IA #: 7662
  FILE NUMBER: 123.6                    GLOBAL ROOT: GMR(123.6,D0
  DATE CREATED: SEP 17, 2026
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: File
  NAME: READ/WRITE IFC MESSAGE LOG (#123.6)
  ID: GMR(123.6,D0
GLOBAL REFERENCE: GMR(123.6,D0,
FIELD NUMBER: .04                       FIELD NAME: CONSULT/REQUEST #
  LOCATION: 0;4                         ACCESS: Read w/Fileman
FIELD NUMBER: .06                       FIELD NAME: INCOMPLETE
  LOCATION: 0;6                         ACCESS: Write w/Fileman
  STATUS: Active                        DURATION: Till Otherwise Agreed
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   Added 9/28/26, effective with patch RMPR*3*217.  The
 VistA Prosthetics interface to the Federal Electronic Health Record (FEHR) was
 created by patch RMPR*3*217.  At the time of cutover, the Advanced Prosthetics
 Acquisition Tool (APAT) Graphical User Interface (GUI), continues to send HL7
 messages using the IFC interface.  Responses to these HL7 messages are
 processed by the VistA Prosthetics interface.  RMPR*3*217 needs to remove the
 INCOMPLETE flag in the IFC Message Log (#123.6) so later messages aren't
 blocked.  

NUMBER: 7663                            IA #: 7663
  DATE CREATED: SEP 24, 2026            CUSTODIAL PACKAGE: PROSTHETICS
  USAGE: Private                        TYPE: Routine
  ROUTINE: RMPRINF0                     NAME: CALL PROSTHETICS INTERFACE
  ID: RMPRINF0
 GENERAL DESCRIPTION:   RMPR*3*217 installs a replacement order and order
 update interface for HL7 messages exchanged between VistA Prosthetics and the
 Federal Electronic Health Record (FEHR) system.  This interface, unlike the
 IFC interface, is multi-division compliant.  
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: FILRACTN
 COMPONENT DESCRIPTION:   Processes actions performed by a filler site on
 Prosthetics orders.  
VARIABLES: ACTION                       TYPE: Input
 VARIABLES DESCRIPTION:   "POST-INIT", "POST-COMPLETE", "POST-OTHER", or
 "CANCEL." 
VARIABLES: GMRCDA                       TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the REQUEST/CONSULTATION file (#123).  
VARIABLES: COMMENTS                     TYPE: Input
 VARIABLES DESCRIPTION:   Array of comments.  
SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING
 SUBSCRIBING DETAILS:   The Advanced Prosthetics Acquisition Tool (APAT) is a
 GUI overlay to VistA Prosthetics developed by DSS.  It calls CMT^GMRCGUIB and 
 SFILE^GMRCGUIB to send HL7 order update messages to the Federal Electronic
 Health Record System (FEHR).  These calls, when made on converted VistAs, fail
 if sent for a secondary division on a multi-division site.  
  
 GMRCGUIB needs to call the new Prosthetics interface implemented by RMPR*3*217
 to fix this failure.  

NUMBER: 7664                            IA #: 7664
  DATE CREATED: SEP 30, 2026            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGPTF                        NAME: PTF Data Form IB ACC Worklist
  ID: DGPTF
 GENERAL DESCRIPTION:   Entry point to invoke the Load/Edit PTF Data [DG PTF
 SCREEN] option from Integrated Billing ACC Claims Worklist [IBACC WL ACC
 CLAIMS WORKLIST] 
  STATUS: Active
COMPONENT/ENTRY POINT: ENACC
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Added 9/30/26, effective with patch IB*2.0*802 

NUMBER: 7665                            IA #: 7665
  DATE CREATED: OCT 01, 2026            CUSTODIAL PACKAGE: MENTAL HEALTH
  USAGE: Controlled Subscription        TYPE: Routine
  ROUTINE: YSCLTST6                     NAME: DBIA7665
  ID: YSCLTST6
 GENERAL DESCRIPTION:   This agreement provides the calling program to build
 outpatient clozapine data for transmission. This ICR is created to document a
 call to ORDSET^YSCLTST6, which was released in patch PSO*7*457.  
  STATUS: Pending
KEYWORDS: CLOZAPINE
COMPONENT/ENTRY POINT: ORDSET
 COMPONENT DESCRIPTION:   This entry point will populate the CPRS order# in the
 XTMP global for transmission.  
SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY

NUMBER: 7666                            IA #: 7666
  DATE CREATED: OCT 14, 2026            CUSTODIAL PACKAGE: REGISTRATION
  USAGE: Private                        TYPE: Routine
  ROUTINE: DGPTFMO1IBACC                NAME: ACC Claims Worklist
  ID: DGPTFMO1IBACC
 GENERAL DESCRIPTION:   Entry point to invoke new DG routine from Integrated
 Billing ACC Claims Worklist [IBACC WL ACC CLAIMS WORKLIST] 
  STATUS: Active
COMPONENT/ENTRY POINT: PTF
SUBSCRIBING PACKAGE: INTEGRATED BILLING
 SUBSCRIBING DETAILS:   Added 10/14/26 effective with patch IB*2.0*802. Calling
 routine DGPTMO1IBACC 

NUMBER: 7667                            IA #: 7667
  DATE CREATED: OCT 24, 2026
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: Routine
  ROUTINE: GMRCUTL1
  NAME: Prosthetics interface calls consult printer
  ID: GMRCUTL1
 GENERAL DESCRIPTION:   PRNT^GMRCUTL1 prints consults upon receipt of an order. 
 
  STATUS: Pending                       DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: PRNT
VARIABLES: GMRCO                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file #123.  
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   The Prosthetics interface needs to call PRNT^GMRCUTL1
 when an order is received from the Federal EHR.  

NUMBER: 7668                            IA #: 7668
  DATE CREATED: OCT 24, 2026
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: Routine
  ROUTINE: GMRCAU
  NAME: Prosthetics interface calls alert text formatter
  ID: GMRCAU                            STATUS: Pending
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: ORTX
VARIABLES: GMRCO                        TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file #123.  
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   The Prosthetics interface calls ORTX^GMRCAU to prepare
 alert text for an order incoming from the Federal EHR.  

NUMBER: 7669                            IA #: 7669
  DATE CREATED: OCT 24, 2026
  CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING
  USAGE: Private                        TYPE: Routine
  ROUTINE: GMRCP
  NAME: Prosthetics interface calls alert notifications
  ID: GMRCP                             STATUS: Pending
  DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: MSG
VARIABLES: GMRCDFN                      TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file #2.  
VARIABLES: GMRCALRM                     TYPE: Input
 VARIABLES DESCRIPTION:   Alert message text.  
VARIABLES: GMRCIFN                      TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file #123.  
VARIABLES: ORN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to file #100.9.  
VARIABLES: FLG                          TYPE: Input
 VARIABLES DESCRIPTION:   Need to get list of service's providers.  
SUBSCRIBING PACKAGE: PROSTHETICS
 SUBSCRIBING DETAILS:   The Prosthetics interface calls MSG^GMRCP to send alert
 notifications when an order is received from the Federal EHR.  

NUMBER: 7670                            IA #: 7670
  FILE NUMBER: 220                      GLOBAL ROOT: DENT(220
  DATE CREATED: NOV 02, 2026            CUSTODIAL PACKAGE: DENTAL
  USAGE: Private                        TYPE: File
  NAME: Dental Patient File 220         ID: DENT(220
GLOBAL REFERENCE: DNET(220,D0
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DENT(220,D0,5
FIELD NUMBER: .01                       FIELD NAME: OTHER FINDINGS/REMARKS
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DENT(220,D0,10
FIELD NUMBER: 70.01                     FIELD NAME: LAST CLASSIFICATION 
  LOCATION: 10;1                        ACCESS: Both R/W w/Fileman
FIELD NUMBER: 70.02                     FIELD NAME: CLASSIFICATION DATE
  LOCATION: 10;2                        ACCESS: Both R/W w/Fileman
GLOBAL REFERENCE: DENT(220,'B'
 GENERAL DESCRIPTION:   This file contains patient information pertinent to the
 Dental  Service.  It points to the Patient file (2).  
  STATUS: Active
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 11/2/26, effective with class edevs.cls v1.0 The
 Electronic Dental Eligibility Verification Solution (DEVS), a micro service
 within the VA will leverage this API.  

NUMBER: 7671                            IA #: 7671
  FILE NUMBER: 228.1                    GLOBAL ROOT: DENT(228.1
  DATE CREATED: NOV 02, 2026            CUSTODIAL PACKAGE: DENTAL
  USAGE: Private                        TYPE: File
  NAME: Dental History File 228.1       ID: DENT(228.1
GLOBAL REFERENCE: DENT(228.1,D0
FIELD NUMBER: .01                       FIELD NAME: RECORD#
  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: .13                       FIELD NAME: DAS PATIENT CATEGORY
  LOCATION: 0;13                        ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This file contains patient information pertinent to the 
 Dental Service.  It points to the Patient file (2).  
  STATUS: Active
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 11/2/26, effective with class EDEVS.cls The
 Electronic Dental Eligibility Verification Solution (DEVS), a micro service
 within the VA will leverage this API.  

NUMBER: 7672                            IA #: 7672
  FILE NUMBER: 220.2                    GLOBAL ROOT: DIC(220.2
  DATE CREATED: NOV 02, 2026            CUSTODIAL PACKAGE: DENTAL
  USAGE: Private                        TYPE: File
  NAME: Dental Classification File 220.2
  ID: DIC(220.2
GLOBAL REFERENCE: DIC(220.2,D0
FIELD NUMBER: .01                       FIELD NAME: CLASSIFICATION
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
 GENERAL DESCRIPTION:   This file contains patient information pertinent to the
 Dental Service.  Contains a field, PATIENT CATEGORY, which is a pointer to the
 DENTAL CLASSIFICATION file (#220.2) 
  STATUS: Active
SUBSCRIBING PACKAGE: VETERANS DATA INTEGRATION AND FEDERATION
 SUBSCRIBING DETAILS:   Added 1/2/26, effective with class edevs.cls  The
 Electronic Dental Eligibility Verification Solution (DEVS), a micro service
 within the VA will leverage this API.  

NUMBER: 10000                           IA #: 10000
  DATE CREATED: APR 08, 1994            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: %DTC
  NAME: Classic FileMan API: Date/Time Manipulation
  ORIGINAL NUMBER: 10000                ID: %DTC
 GENERAL DESCRIPTION:   Date and Time manipulation and Number formating.  
  STATUS: Active
COMPONENT/ENTRY POINT: %DTC
 COMPONENT DESCRIPTION:   Returns the number of days between two dates.  
VARIABLES: X1                           TYPE: Input
 VARIABLES DESCRIPTION:   One date of the required two in VA FileMan format. 
 Required and not returned.  
VARIABLES: X2                           TYPE: Input
 VARIABLES DESCRIPTION:   The other date in VA FileMan format.  Required and
 not returned.  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   The number of days between the two dates.  X2 is
 subtracted from X1.  
VARIABLES: %Y                           TYPE: Output
 VARIABLES DESCRIPTION:   If %Y is equal to 1, the dates have both month and
 day values.  
  
 If %Y is equal to 0, the dates were imprecise and therefore not workable.  
COMPONENT/ENTRY POINT: C
 COMPONENT DESCRIPTION:   Takes a date and adds or subtracts a number of days,
 returning a VA FileMan date and a $H format date.  If time is included with
 the input, it will also be included with the output.  
VARIABLES: X1                           TYPE: Input
 VARIABLES DESCRIPTION:   The date in VA FileMan format to which days are going
 to be added or subtracted.  Required and not returned.  
VARIABLES: X2                           TYPE: Input
 VARIABLES DESCRIPTION:   If positive, the number of days to add.  If negative,
 the number of days to subtrct.  Required and not returned.  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   The resulting date after the operation has been
 performed in VA FileMan format.  
VARIABLES: %H                           TYPE: Output
 VARIABLES DESCRIPTION:   The $H form of the date.  
COMPONENT/ENTRY POINT: NOW
 COMPONENT DESCRIPTION:   Returns the current date/time in VA FileMan and $H
 formats.  
VARIABLES: %                            TYPE: Output
 VARIABLES DESCRIPTION:   VA FileMan date/time down to the second.  
VARIABLES: %H                           TYPE: Output
 VARIABLES DESCRIPTION:   $H date/time.  
VARIABLES: %I(1)                        TYPE: Output
 VARIABLES DESCRIPTION:   The numeric value of the month.  
VARIABLES: %I(2)                        TYPE: Output
 VARIABLES DESCRIPTION:   The numeric value of the day.  
VARIABLES: %I(3)                        TYPE: Output
 VARIABLES DESCRIPTION:   The numeric value of the year.  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   VA FileMan date only.  
COMPONENT/ENTRY POINT: H
 COMPONENT DESCRIPTION:   Converts a VA FileMan date/time to a $H formate
 date/time.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   The date/time in VA FileMan format.  Required and
 returned.  
VARIABLES: %H                           TYPE: Output
 VARIABLES DESCRIPTION:   The same date in $H format.  If the date is
 imprecise, then the first of the month or year is returned.  
VARIABLES: %T                           TYPE: Output
 VARIABLES DESCRIPTION:   The time in $H format, i.e., the number of seconds
 since midnight.  If there is no time, then %T equals zero.  
VARIABLES: %Y                           TYPE: Output
 VARIABLES DESCRIPTION:   The day-of-week as a numeric from 0 to 6, where 0
 means Sunday and 6 means Saturday.  If the date is imprecise, then %Y is equal
 to -1.  
COMPONENT/ENTRY POINT: DW
 COMPONENT DESCRIPTION:   This entry point produces results similar to H^%DTC. 
 The difference is that X is reset to the name of the day of the week - Sunday,
 Monday, etc.  If the date is imprecise, then X is returned equal to null.  
COMPONENT/ENTRY POINT: YMD
 COMPONENT DESCRIPTION:   Converts a $H format date to a VA FileMan date.  
VARIABLES: %H                           TYPE: Both
 VARIABLES DESCRIPTION:   A $H format date/time.  Required and returned.  
VARIABLES: %                            TYPE: Output
 VARIABLES DESCRIPTION:   Time down to the second in VA FileMan format, that
 is, as a decimal.  If %H does not have time, then % equals zero.  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   The date in VA FileMan format.  
COMPONENT/ENTRY POINT: COMMA
 COMPONENT DESCRIPTION:   Formats a number to a string that will separate
 billions, millions, and thousands with commas.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   The number you want to format.  X is required and it
 may be positive or negative.  
VARIABLES: X2                           TYPE: Input
 VARIABLES DESCRIPTION:   The number of decimal digits we want the output to
 have.  If X2 is not defined, two decimal digits are returned.  If X2 is a
 number followed by the dollar sign (e.g., 3$) then a dollar sign will be 
 prefixed to X before it is output.  
VARIABLES: X3                           TYPE: Input
 VARIABLES DESCRIPTION:   The length of the desired output.  If X3 is less than
 the formatted X, X3 will be ignored.  If X3 is not defined, then a length of
 twelve is used.  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   The initial value of X, formatted with commas,
 rounded to the number of decimal digits specified in X2.  If X2 contained a
 dollar sign, then the dollar sign will be next to the leftmost digit.  If X
 was negative, then the returned value of X will be in parentheses.  If X was
 positive, a trailing space will be appended.  If necessary, X will be padded
 with leading spaces so that the length of X will equal the value of the X3
 input variable.  
COMPONENT/ENTRY POINT: S
 COMPONENT DESCRIPTION:   Converts number of seconds since midnight to hours,
 minutes, and seconds as a decimal part of FileMan date.  
VARIABLES: %                            TYPE: Input
 VARIABLES DESCRIPTION:   Number of seconds from midnight (Input).  
  
 Decimal part of FileMan date (Output).  
COMPONENT/ENTRY POINT: YX
 COMPONENT DESCRIPTION:   This entry point takes a $H date and passes back a
 printable date/time.  It also passes back the VA FileMan form of the date and
 time.  
VARIABLES: %H                           TYPE: Both
 VARIABLES DESCRIPTION:   This contains the date and time in $H format which is
 to be converted.  Time is optional.  Required and returned.  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   The date and time (if time has been sent) in external
 format.  Seconds will be included if the input contained seconds.  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   The date in VA FileMan format.  
VARIABLES: %                            TYPE: Output
 VARIABLES DESCRIPTION:   The time as a decimal value inVA FileMan format.  If
 time was not sent, then % will be returned as zero.  
COMPONENT/ENTRY POINT: HELP
 COMPONENT DESCRIPTION:   This entry point displays a help prompt based on %DT
 and %DT(0).  
VARIABLES: %DT                          TYPE: Input
VARIABLES: %DT(0)                       TYPE: Input

NUMBER: 10001                           IA #: 10001
  DATE CREATED: NOV 17, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIO2
  NAME: Classic FileMan API: Internal to External Date
  ORIGINAL NUMBER: 10001                ID: DIO2
 GENERAL DESCRIPTION:   This entry point takes an internal date in the variable
 Y and writes out its external form. 
  STATUS: Active
COMPONENT/ENTRY POINT: DT
 COMPONENT DESCRIPTION:   This entry point takes an internal date in the
 variable Y and writes out its external form. 
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Contains the internal date to be
 converted. If this has five or six decimal places, seconds will automatically
 be written. Y is required and it is not changed. 

NUMBER: 10002                           IA #: 10002
  DATE CREATED: NOV 17, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIEZ
  NAME: Classic FileMan API: Input Template Compilation
  ORIGINAL NUMBER: 10002                ID: DIEZ
 GENERAL DESCRIPTION:   Input template compilation for inproved performance.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Non-interactive input template compilation.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   The name of the routine for the compiled input
 template. 
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   The internal entry number of the input template to be
 compiled. 
VARIABLES: DMAX                         TYPE: Input
 VARIABLES DESCRIPTION:   The maximum size the compiled routines should reach.
 Consider using the $$ROUSIZE^DILF (see DBIA #2054) function to set this
 variable.  
COMPONENT/ENTRY POINT: DIEZ
 COMPONENT DESCRIPTION:   Interactive input template compilation.  
VARIABLES: None

NUMBER: 10003                           IA #: 10003
  DATE CREATED: NOV 13, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: %DT
  NAME: Classic FileMan API: Date/Time Input & Conversion
  ORIGINAL NUMBER: 10003                ID: %DT
 GENERAL DESCRIPTION:   Validate date/time input and convert it to VA FileMan's
 conventional internal format:"YYYMMDD.HHMMSS", where: YYY = number of years
 since 1700 MM = Month number DD = Day number HH = Hour number MM = Minute
 number SS = Seconds number 
  
  STATUS: Active
KEYWORDS: DATE
KEYWORDS: TIME
KEYWORDS: %DT
COMPONENT/ENTRY POINT: %DT
 COMPONENT DESCRIPTION:   Accepts input and validates the input as being the
 correct date and time.  
VARIABLES: %DT                          TYPE: Input
 VARIABLES DESCRIPTION:   A string of alphabetic characters which alter how %DT
 responds. Briefly stated, the acceptable characters are: 
  
  A Ask for date input.  
  E Echo the answer.  
  F Future dates are assumed.  
  I Internalization, assumes the day precedes the month in input.  
  M Only Month and year input is allowed.  
  N Pure Numeric input is not allowed.  
  P Past dates are assumed.  
  R Requires time input.  
  S  Seconds should be returned. 
  T Time input is allowed but not required.  
  X  EXact date (with month and day) is required.  
  
VARIABLES: X                            TYPE: Both
 VARIABLES DESCRIPTION:   X is always returned. It contains either what was
 passed to %DT (in the case where %DT did not contain an A) or what the user
 entered. 
VARIABLES: %DT("A")                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) A prompt which will be displayed prior to
 the reading of the input. Without this variable, the prompt "DATE:" will be
 issued. 
VARIABLES:  
VARIABLES: %DT("B")                     TYPE: Input
 VARIABLES DESCRIPTION:   The default answer to the "DATE:" prompt. It is your
 responsibility to ensure that %DT("B") contains a valid date/time. 
VARIABLES: %DT(0)                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Prevents the input date value from being
 accepted if it is chronologically before, or after, a particular date. 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   %DT always returns the variable Y, which can be one
 of two values: 
  
 Y=-1 The date/time was invalid.  Y=YYYMMDD.HHMMSS The value determined by %DT. 
VARIABLES: DTOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   This is only defined if %DT has timed-out waiting for
 input from the user.  
COMPONENT/ENTRY POINT: DD
 COMPONENT DESCRIPTION:   Converts a FileMan internal date to external.  
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   (Required) This contains the internal date to be
 converted. If this has five or six decimal places, seconds will automatically
 be returned. 
  
 Y is returned as the external form of the date. 
VARIABLES: %DT                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This is only used to force seconds to be
 returned even if Y does not have that resolution. %DT must contain S for this
 to happen. 
  DATE ACTIVATED: SEP 29, 2015

NUMBER: 10004                           IA #: 10004
  DATE CREATED: NOV 16, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIQ                          NAME: Classic FileMan API: Data Display
  ORIGINAL NUMBER: 10004                ID: DIQ
 GENERAL DESCRIPTION:   Provides ways to display data from file entries and
 ways to convert data from one format to another.  
  STATUS: Active
COMPONENT/ENTRY POINT: DT
 COMPONENT DESCRIPTION:   This call converts the date in Y exactly like D^DIQ.
 Unlike D^DIQ, however, it also writes the date after it has been converted.  
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Input: (Required) Contains the internal date to be
 converted. If this has five or six decimal places, seconds are automatically
 returned. 
  
 Output: External form of the date or date/time value, e.g., JAN 01, 1998. 
COMPONENT/ENTRY POINT: Y
 COMPONENT DESCRIPTION:   This entry point converts the internal form of any
 data element to its external form. It works for all FileMan data types, uses
 output transforms, and follows pointer trails to their final resolution. The 
 equivalent Database Server call is $$EXTERNAL^DILFD (see DBIA #2055).  
VARIABLES: Naked Global Reference       TYPE: Input
 VARIABLES DESCRIPTION:   The naked global reference must be at the zero node
 of the data dictionary definition which describes the data [i.e., it must be
 at ^DD(File#,Field#,0)]. 
VARIABLES: Y                            TYPE: Both
 VARIABLES DESCRIPTION:   Input: Set Y to the internal form of the value being
 converted. This is the data that you want to convert to external form.  
  
 Output: The external form of the value. Basically, Y is changed from internal
 to external. 
VARIABLES: C                            TYPE: Input
 VARIABLES DESCRIPTION:   Set C to the second piece of the zero node of the
 data dictionary which defines that element. 
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This entry point displays a range of data elements in
 captioned format, to the current device. 
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The global root of the file.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   (Required) If you are displaying an entry at the top
 level of a file, set DA to the internal entry number of the file entry to
 display.  
  
 If you are editing an entry in a subfile, set up DA as an array, where 
 DA=entry number in the subfile to display, DA(1) is the entry number at the
 next higher file level,...DA(n) is the entry number at the file's top level. 
VARIABLES: DR                           TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Names the global subscript or subscripts
 which are to be displayed by DIQ. If DR contains a colon (:), the range of
 subscripts is understood to be specified by what precedes and follows the
 colon.  Otherwise, DR is understood to be the literal name of the subscript.
 All data fields stored within, and descendent from, the subscript(s) will be 
 displayed, even those which normally have read access security protection.  
VARIABLES: DIQ(0)                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) You can include the following flags in
 this variable to change the display of the entry: 
  
 C To display computed fields.  A To display audit records for the entry.  R To
 display the entry's record number (IEN).  
COMPONENT/ENTRY POINT: D
 COMPONENT DESCRIPTION:   This entry point takes an internal date in the
 variable Y and converts it to its external form. This call is very similar to
 DD^%DT. 
VARIABLES: Y                            TYPE: Input
VARIABLES:                              TYPE: Both
 VARIABLES DESCRIPTION:   Input: (Required) Contains the internal date to be
 converted. If this has five or six decimal places, seconds are automatically
 returned. 
  
 Output: External form of the date or date/time value, e.g., JAN 01, 1998. 

NUMBER: 10005                           IA #: 10005
  DATE CREATED: NOV 17, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DICRW
  NAME: Classic FileMan API: Required Variables
  ORIGINAL NUMBER: 10005                ID: DICRW
 GENERAL DESCRIPTION:   Sets up the required variables of VA FileMan. 
  STATUS: Active
COMPONENT/ENTRY POINT: DT
 COMPONENT DESCRIPTION:   Sets up the required variables of VA FileMan. 
VARIABLES: DUZ                          TYPE: Output
 VARIABLES DESCRIPTION:   Set to zero if it is not already defined. 
VARIABLES: DUZ(0)                       TYPE: Output
 VARIABLES DESCRIPTION:   Set to null if not already defined. If DUZ(0)="@",
 this subroutine will enable terminal break if the operating system supports
 such functionality.  
VARIABLES: IO(0)                        TYPE: Output
 VARIABLES DESCRIPTION:   Set to $I if IO(0) is not defined. Therefore, this
 program should not be called if the user is on a device different from the
 home terminal and IO(0) is undefined.  
VARIABLES: DT                           TYPE: Output
 VARIABLES DESCRIPTION:   Set to the current date, in VA FileMan format. 
VARIABLES: U                            TYPE: Output
 VARIABLES DESCRIPTION:   Set to the Up-arrow (^).  

NUMBER: 10006                           IA #: 10006
  DATE CREATED: NOV 18, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIC
  NAME: Classic FileMan API: File Lookup/Add New Entries
  ORIGINAL NUMBER: 10006                ID: DIC
 GENERAL DESCRIPTION:   Entry point DIC is for general file lookups.  Entry
 point IX if for a single cross reference lookups.  
  STATUS: Active
COMPONENT/ENTRY POINT: DIC
 COMPONENT DESCRIPTION:   Given a lookup value, this entry point searches a
 file and either finds a matching entry, adds an entry, or returns a condition
 indicating that the lookup was unsuccessful.  
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The file number or an explicit global
 root.  
VARIABLES: DIC(0)                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) A string of alphabetic characters which
 alter how DIC responds.  At a minimum this string must be set to null. A
 detailed description of these characters can be found later in this section. 
  
 Flag Short Description : A Ask the entry; if erroneous, ask again.  B Lookup
 only on "B" index of cross-referenced pointed-to files for a match to X. Note:
 this flag is introduced with patch DI*21*29. C Cross reference suppression is
 turned off.  E Echo back information. F Forget the lookup value. I Ignore the
 special lookup program. L Learning a new entry is allowed. M Multiple-index
 lookup allowed. N Internal Number lookup allowed (but not forced).  O Only
 find one entry if it matches exactly.  Q Question erroneous input (with two
 ??).  S Suppresses display of .01 (except B cross reference match).  X EXact
 match required. Z Zero node returned in Y(0) and external form in Y(0,0).  
VARIABLES: X                            TYPE: Both
 VARIABLES DESCRIPTION:   Input: If DIC(0) does not contain an A, then the
 variable X must be defined equal to the value you want to lookup. If the value
 in X has more than one match or partial match, the lookup fails and Y=-1 is
 returned.  
  
 Output: Contains the value of the field where the match occurred. 
VARIABLES: DIC("A")                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) A prompt that is displayed prior to the
 reading of the X input.  
VARIABLES: DIC("B")                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The default answer which is presented to
 the user when the lookup prompt is issued. 
VARIABLES: DIC("S")                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) DIC("S") is a string of MUMPS code that
 DIC executes to screen an entry from selection. DIC("S") must contain an IF
 statement to set the value of $T. 
VARIABLES: DIC("W")                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) A MUMPS command string which is executed
 when DIC displays each of the entries that match the user's input. 
VARIABLES: DIC("DR")                    TYPE: Input
 VARIABLES DESCRIPTION:   When calling DIC with LAYGO allowed, you can specify
 that a certain set of fields will be asked for in the case where the user
 enters a new entry. 
VARIABLES: DIC("P")                     TYPE: Input
 VARIABLES DESCRIPTION:   This variable is needed to successfully add the FIRST
 subentry to a multiple when the descriptor (or header) node of the multiple
 does not exist. 
VARIABLES: DIC("V")                     TYPE: Input
 VARIABLES DESCRIPTION:   If the .01 field is a variable pointer, it can point
 to entries in more than one file. You can restrict the user's ability to input
 entries from certain files by using the DIC("V") variable. 
VARIABLES: DLAYGO                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) If this variable is set equal to the file
 number, then the users will be able to add a new entry to the file whether or
 not they have LAYGO access to the file. 
VARIABLES: DINUM                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This input variable identifies the
 subscript at which the data is to be stored. 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   DIC always returns the variable Y. The variable Y is
 returned with one of these three formats: 
  
 Y=-1 The lookup was unsuccessful.  Y=N^S N is the internal number of the entry
 in the file and S is the value of the .01 field for that entry.  Y=N^S^1 N and
 S are defined as above and the 1 indicates that this entry has just been added
 to the file.  
VARIABLES: Y(0)                         TYPE: Output
 VARIABLES DESCRIPTION:   This variable is only set if DIC(0) contains a Z.
 When the variable is set, it is equal to the entire zero node of the entry
 that was selected. 
VARIABLES: Y(0,0)                       TYPE: Output
 VARIABLES DESCRIPTION:   This variable is also only set if DIC(0) contains a
 Z. When the variable is set, it is equal to the external form of the .01 field
 of the entry. 
VARIABLES: DTOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   This is only defined if DIC has timed-out waiting for
 input from the user.  
VARIABLES: DUOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   This is only defined if the user entered an up-arrow. 
 
COMPONENT/ENTRY POINT: IX
 COMPONENT DESCRIPTION:   This entry point is similar to ^DIC and MIX^DIC1 (see
 DBIA #10007), except on how it uses cross-references to do lookup.  
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   The global root of the file.  
VARIABLES: DIC(0)                       TYPE: Input
 VARIABLES DESCRIPTION:   The lookup parameters as previously described for
 ^DIC. 
VARIABLES: D                            TYPE: Input
 VARIABLES DESCRIPTION:   The cross reference in which to start looking. If
 DIC(0) contains M, then DIC will continue with further cross references. If it
 does not, then the lookup is only on the single cross reference.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   If DIC(0) does not contain an A, then the variable X
 must be defined equal to the value you want to lookup. 
VARIABLES: DIC("A")                     TYPE: Input
 VARIABLES DESCRIPTION:   This set of input variables affects the behavior of
 lookup as previously described for ^DIC.  
VARIABLES: DIC("B")                     TYPE: Input
 VARIABLES DESCRIPTION:   This set of input variables affects the behavior of
 lookup as previously described for ^DIC.  
VARIABLES: DIC("DR")                    TYPE: Input
 VARIABLES DESCRIPTION:   This set of input variables affects the behavior of
 lookup as previously described for ^DIC.  
VARIABLES: DIC("P")                     TYPE: Input
 VARIABLES DESCRIPTION:   This set of input variables affects the behavior of
 lookup as previously described for ^DIC.  
VARIABLES: DIC("S")                     TYPE: Input
 VARIABLES DESCRIPTION:   This set of input variables affects the behavior of
 lookup as previously described for ^DIC.  
VARIABLES: DIC("V")                     TYPE: Input
 VARIABLES DESCRIPTION:   This set of input variables affects the behavior of
 lookup as previously described for ^DIC.  
VARIABLES: DIC("W")                     TYPE: Input
 VARIABLES DESCRIPTION:   This set of input variables affects the behavior of
 lookup as previously described for ^DIC.  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   DIC always returns the variable Y, which can be one
 of the three following formats: 
  
 Y=-1 indicates the lookup was unsuccessful.  Y=N^S N is the Internal Number of
 the entry in the file and S is the value of the .01 field for that entry.  
 Y=N^S^1 N and S are defined as above and the 1 indicates that this entry has
 just been added to the file.  
VARIABLES: Y(0)                         TYPE: Output
 VARIABLES DESCRIPTION:   This variable is only set if DIC(0) contains a Z.
 When it is set, it is equal to the entire zero node of the entry that was
 selected. 
VARIABLES: Y(0,0)                       TYPE: Output
 VARIABLES DESCRIPTION:   This variable is also only set if DIC(0) contains a
 Z. When it is set, it is equal to the external form of the .01 field of the
 entry. 
VARIABLES: DTOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   This is only defined if DIC has timed-out waiting for
 input from the user.  
VARIABLES: DUOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   This is only defined if the user entered an up-arrow. 
 

NUMBER: 10007                           IA #: 10007
  DATE CREATED: NOV 18, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIC1
  NAME: Classic FileMan API: Custom Lookup & File Info. Setup
  ORIGINAL NUMBER: 10007                ID: DIC1
 GENERAL DESCRIPTION:   Entry point DO sets up certain file information.  Entry
 point MIX does multi-index nonstandard order lookup.  
  STATUS: Active
COMPONENT/ENTRY POINT: DO
 COMPONENT DESCRIPTION:   Retrieve's a file's file header node, code to execute
 its identifiers, and its screen (if any), and puts them into local variables
 for use during lookup into a file. 
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   The global root of the file.  
VARIABLES: DIC(0)                       TYPE: Input
 VARIABLES DESCRIPTION:   The lookup parameters as previously described for
 ^DIC (see DBIA #10006).  
VARIABLES: DO                           TYPE: Output
 VARIABLES DESCRIPTION:   File name^file number and specifiers. This is the
 file header node. 
  
 NOTE: Use the letter O, not the number zero, in this variable name. 
VARIABLES: DO(2)                        TYPE: Output
 VARIABLES DESCRIPTION:   File number and specifiers. This is the second ^piece
 of DO. +DO(2) will always equal the file number. 
VARIABLES: DIC("W")                     TYPE: Output
 VARIABLES DESCRIPTION:   This is an executable variable which contains the
 write logic for identifiers. When an entry is displayed, the execution of this
 variable shows other information to help identify the entry. 
VARIABLES: DO("SCR")                    TYPE: Output
 VARIABLES DESCRIPTION:   An executable variable which contains a file's screen
 (if any). The screen is an IF-statement that can screen out certain entries in
 the file. This differs from DIC("S") in that it is used on every lookup
 regardless of input or output; that is, the screen is applied to inquiries and
 printouts as well as lookups. The value for this variable comes from 
 ^DD(+DO(2),0,"SCR") and the specifier "s" must be in DO(2). 
COMPONENT/ENTRY POINT: MIX
 COMPONENT DESCRIPTION:   This entry point is similar to ^DIC and IX^DIC (see
 DBIA #10006) except on how it uses cross-references to do lookup.  
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   The global root of the file.  
VARIABLES: DIC(0)                       TYPE: Input
 VARIABLES DESCRIPTION:   The lookup parameters as previously described for
 ^DIC (see DBIA #10006).  
VARIABLES: D                            TYPE: Input
 VARIABLES DESCRIPTION:   The list of cross references, separated by up-arrows,
 to be searched, e.g., D="SSN^WARD^B". This variable is killed by VA FileMan;
 it is undefined when the MIX^DIC1 call is complete. 
  
 Make sure DIC(0) contains M; otherwise, only the first cross reference in D
 will be used for the lookup.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   If DIC(0) does not contain an A, then the variable X
 must be defined equal to the value you want to look up. 
VARIABLES: DIC("A")                     TYPE: Input
 VARIABLES DESCRIPTION:   This set of input variables affects the behavior of
 lookup as previously described for ^DIC (see DBIA #10006).  
VARIABLES:  
VARIABLES: DIC("B")                     TYPE: Input
 VARIABLES DESCRIPTION:   This set of input variables affects the behavior of
 lookup as previously described for ^DIC (see DBIA #10006).  
VARIABLES: DIC("DR")                    TYPE: Input
 VARIABLES DESCRIPTION:   This set of input variables affects the behavior of
 lookup as previously described for ^DIC (see DBIA #10006).  
VARIABLES: DUC('
VARIABLES: DIC("P")                     TYPE: Input
 VARIABLES DESCRIPTION:   This set of input variables affects the behavior of
 lookup as previously described for ^DIC (see DBIA #10006).  
VARIABLES: DIC("S")                     TYPE: Input
 VARIABLES DESCRIPTION:   This set of input variables affects the behavior of
 lookup as previously described for ^DIC (see DBIA #10006).  
VARIABLES: DIC("V")                     TYPE: Input
 VARIABLES DESCRIPTION:   This set of input variables affects the behavior of
 lookup as previously described for ^DIC (see DBIA #10006).  
VARIABLES: DIC("W")                     TYPE: Input
 VARIABLES DESCRIPTION:   This set of input variables affects the behavior of
 lookup as previously described for ^DIC (see DBIA #10006).  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   DIC always returns the variable Y in one of the three
 following formats: 
  
 Y=-1 Indicates the lookup was unsuccessful.  
  
 Y=N^S N is the Internal Number of the entry in the file and S is the value of
 the .01 field for that entry.  
  
 Y=N^S^1 N and S are defined as above and the 1 indicates that this entry has
 just been added to the file.  
VARIABLES: Y(0)                         TYPE: Output
 VARIABLES DESCRIPTION:   This variable is only set if DIC(0) contains a Z.
 When it is set, it is equal to the entire zero node of the entry that was
 selected. 
VARIABLES: Y(0,0)                       TYPE: Output
 VARIABLES DESCRIPTION:   This variable is also only set if DIC(0) contains a
 Z. When it is set, it is equal to the external form of the .01 field of the
 entry. 
VARIABLES: DTOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   This is only defined if DIC has timed-out waiting for
 input from the user.  
VARIABLES: DUOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   This is only defined if the user entered an up-arrow. 
 

NUMBER: 10008                           IA #: 10008
  DATE CREATED: NOV 17, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DICQ
  NAME: Classic FileMan API: Entry Display For Lookups
  ORIGINAL NUMBER: 10008                ID: DICQ
 GENERAL DESCRIPTION:   Displays the list of entries in a file a user can see.  
  STATUS: Active
COMPONENT/ENTRY POINT: DQ
 COMPONENT DESCRIPTION:   Displays the list of entries in a file a user can
 see.  
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Global root of the file.  
VARIABLES: DIC(0)                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Look-up parameter string (see DBIA
 #10006).  
VARIABLES: DIC("S")                     TYPE: Input
 VARIABLES DESCRIPTION:   Optional screen (see DBIA #10006).  
VARIABLES: D                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Set to "B". 
VARIABLES: DZ                           TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Set to "??". This is set in order to
 prevent VA FileMan from issuing the "DO YOU WANT TO SEE ALL nn ENTRIES?"
 prompt. 

NUMBER: 10009                           IA #: 10009
  DATE CREATED: NOV 17, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DICN
  NAME: Classic FileMan API: Adding New Entries & YES/NO Prompt
  ORIGINAL NUMBER: 10009                ID: DICN
 GENERAL DESCRIPTION:   Can be used for adding new entries to a file.  Or for
 YES/NO prompts.  
  STATUS: Active
COMPONENT/ENTRY POINT: FILE
 COMPONENT DESCRIPTION:   Used for adding new entries to a file or sub-file.  
VARIABLES: DD                           TYPE: Used
 VARIABLES DESCRIPTION:   It is mandatory that you KILL the DD variable prior
 to calling FILE^DICN. 
VARIABLES: DO                           TYPE: Used
 VARIABLES DESCRIPTION:   If DO does not contain the characteristics of the
 file you are adding to, then you should KILL DO so that FILE^DICN can call
 DO^DIC1 to retrieve those characteristics. NOTE: This variable is D with the 
 letter O, not zero. 
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   The global root of the file. 
VARIABLES: DIC(0)                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) A string of alphabetic characters which
 alter how DIC responds.  At a minimum this string must be set to null. The
 characters you can include are: 
  
 E = Echo back information.  F = Prevents saving the entry number of the
 matched entry in the ^DISV global.  Z = Zero node returned in Y(0) and
 external form in Y(0,0). 
VARIABLES: DIC("P")                     TYPE: Input
 VARIABLES DESCRIPTION:   Used when adding subentries in multiples (see DBIA
 #10006). 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   Array of entry numbers (see DBIA #10006). 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Identifies the subscript at which the data
 is to be stored; that is, the internal entry number of the new record, shown
 as follows (This means that DINUM must be a canonic number and that no data
 exists in the global at that subscript location.): 
  
     $D(@(DIC_DINUM_")"))=0 If a record already exists at the DINUM internal
 entry number, no new entry is made. The variable Y is returned equal -1.  
VARIABLES: DIC("DR")                    TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Used to input other data elements at the
 time of adding the entry. If the user does not enter these elements, the entry
 will not be added. The format of DIC("DR") is the same as the variable DR
 described under the discussion of DIE (see DBIA #10018). 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   DIC always returns the variable Y, which can be in
 one of the two following values: 
  
 Y=-1 Indicates the lookup was unsuccessful; no new entry was added.  
  
 Y=N^S^1 N is the internal number of the entry in the file, S is the value of
 the .01 field for that entry, and the 1 indicates that this entry has just
 been added to the file.  
VARIABLES: Y(0)                         TYPE: Output
 VARIABLES DESCRIPTION:   This variable is only set if DIC(0) contains a Z.
 When it is set, it is equal to the entire zero node of the entry that was
 selected.  
VARIABLES: Y(0,0)                       TYPE: Output
 VARIABLES DESCRIPTION:   This variable is also only set if DIC(0) contains a
 Z. When it is set, it is equal to the external form of the .01 field of the
 entry. 
VARIABLES: DTOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   This is only defined if DIC has timed-out waiting for
 input from the user.  
VARIABLES: DUOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   This is only defined if the user entered an up-arrow. 
 
COMPONENT/ENTRY POINT: YN
 COMPONENT DESCRIPTION:   A reader for a YES/NO response.  
VARIABLES: %                            TYPE: Both
 VARIABLES DESCRIPTION:   Input: Determines the default response as follows: 
  
 % = 0 (zero) No default % = 1 YES  % = 2 NO  
  
 Output: The processed user's response. It can be one of the following: 
  
 % = -1 The user entered an ^ (up-arrow).  % = 0 (zero) The user entered <RET>
 when no default was presented OR the user entered a ? (question mark).  % = 1
 The user entered a YES response.  % = 2 The user entered a NO response.  
VARIABLES: %Y                           TYPE: Output
 VARIABLES DESCRIPTION:   The actual text that the user entered. 

NUMBER: 10010                           IA #: 10010
  DATE CREATED: JAN 12, 1995            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIP                          NAME: Classic FileMan API: Print Data
  ORIGINAL NUMBER: 10010                ID: DIP
 GENERAL DESCRIPTION:   Use EN1^DIP to print a range of entries, in columnar
 format. 
  STATUS: Active
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   Fileman 21 provides a new feature.  If a print is
 done and there were no records found to print, it will print the header and a
 message notifying the user that no records were found to print.  
  
 Occasionally, however, this can cause a problem, if the header is a print 
 template.  In this case, at the time the header logic is executed, D0=-1 It
 appears that the logic generated by FileMan for printing regular fields is
 robust enough to handle this situation.  When the print template contained
 code entered by the developer, it has been seen not to work when D0=-1.  
  
 There are two ways to fix this either of which could be done at anytime prior
 to the release of FileMan 21: 
  a) change the logic to use $G so that it will still work with D0=-1 
  b) There is a new input variable that can be set to suppress this feature.  
 When you are setting ithe other input variables to EN1^DIP, if you could S
 DISUPNO=1, the feature would be suppressed and no error would occur.  DISUPNO
 is killed at the end of the print in FileMan 21, but since FM20 doesn't know
 about it, it should probably be NEWed by your code.  
  
 If you use the FLDS input variable to EN1^DIP or a print template to call an
 'M' routine to evaluate and print a value, you must WRITE the value you want
 printed. Examples 1 and 2 below illustrate how this is done.  
  
 Example #1: The routine is called from a Print Template 
 =======================================================
  
 Print Template: NAME: ZZ640A                            DATE CREATED: AUG 13,
 1998@10:21 
   READ ACCESS: @                        FILE: MY PATIENT 
   USER #: 133                           WRITE ACCESS: @ 
   DATE LAST USED: AUG 14, 1998 HEADER (c): MY PATIENT LIST FIRST PRINT FIELD:
 NAME;C1;L22;"PATIENT"// THEN PRINT FIELD: D SSN^MYPROG;X THEN PRINT FIELD: W
 X;C24;R4;"SSN"// COMPILED (c): NO 
  
 Routine Called: MYPROG   ;SFCIOFO/S0 TEST ROUTINE ; 21 Aug 98  2:06 PM SSN     
 ; 
          K VA,VADM S DFN=D0 D ^VADPT 
          S X=$P(VA("PID"),"-",3) 
          Q 
  
 Example of Usage: ZZ640A   ;SFCIOFO/S0 TEST FILEMAN PRINT ; 19 Aug 98  4:03 PM 
          S DIC="^DIZ(640001,",BY=".01",L=0,FR="" 
          S FLDS="[ZZ640A]" 
          D EN1^DIP 
          Q 
  
 Example #2: The routine is called from the FLDS input variable 
 ==============================================================
  
 Routine Called: MYPROG   ;SFCIOFO/S0 TEST ROUTINE ; 21 Aug 98  2:06 PM SSN     
 ; 
          K VA,VADM S DFN=D0 D ^VADPT 
          S X=$P(VA("PID"),"-",3) 
          Q 
  
 Example of Usage: ZZ640A   ;SFCIOFO/S0 TEST FILEMAN PRINT ; 19 Aug 98  4:03 PM 
          S DIC="^DIZ(640001,",BY=".01",L=0,FR="" 
          S FLDS=".01;C1;L22;""PATIENT"",D SSN^MYPROG;X,W X;C24;""SSN""" 
          D EN1^DIP 
          Q 
VARIABLES: L                            TYPE: Input
 VARIABLES DESCRIPTION:   (Required) String that evaluates to zero. 
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Global root or file number, in the usual
 format. 
VARIABLES: FLDS                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The various fields to be printed.  
VARIABLES: BY                           TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The fields by which the data is to be
 sorted. 
VARIABLES: FR                           TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The START WITH: values of the SORT BY
 fields.  
VARIABLES: FR(n)                        TYPE: Input
VARIABLES: TO                           TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The GO TO: values of the SORT BY fields. 
VARIABLES: TO(n)                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) An alternate way to provide the GO TO:
 values of the SORT BY fields. 
VARIABLES: DHD                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The header desired for the output. 
VARIABLES: DIASKHD                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Set to null to prompt user for a header.  
VARIABLES: DIPCRIT                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional)Set to 1 to print SORT criteria on the
 first page of the report.  
VARIABLES: PG                           TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Starting page number.  
VARIABLES: DHIT                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) M code to execute after each entry is
 printed.  
VARIABLES: DIOEND                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) M code to execute after the printout has
 finished.  
VARIABLES: DIOBEG                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) M code to execute before the printout
 starts. 
VARIABLES: DCOPIES                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Number of copies to print (for SDP-type
 devices).  
VARIABLES: IOP                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Name of device to send output to.  
VARIABLES: DQTIME                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Time to print, for queued printing. 
VARIABLES: DIS(0)                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) M code to screen out entries.  
VARIABLES: DIS(n)                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Additional screens, "OR"-ed with each
 other, "AND"-ed with the DIS(0) screen.  
VARIABLES: DISUPNO                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Set to 1 to suppress output when no
 records are found. 
VARIABLES: DISTOP                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Set to 0 to prevent users from stopping
 prints.  
VARIABLES: DISTOP("C")                  TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) M code to execute if a user stops the
 print. 
VARIABLES: BY(0)                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional; Required for BY(0) sorts) Set this
 variable to an open global root. The open global root should be the static
 part of a global; a list of record numbers must be stored at a descendant
 subscript level. 
VARIABLES: L(0)                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional; Required if BY(0) is set to an open global
 root.) 
  
 Use L(0) to specify the number of dynamic subscript levels that exist beyond
 the static global root, including the subscript level containing the list of
 record numbers. The minimum value of L(0) is 1.  
VARIABLES: FR(0,n)                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) To select only a subset of records at a
 given subscript level n, you can use FR(0,n) and/or TO(0,n). For n equal to
 any of the 'n' dynamic sorting subscript levels in the global specified by
 BY(0), you can set FR(0,n) to the sort-from value for that subscript level.  
VARIABLES: TO(0,n)                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This variable contains the ending value
 (the sort-to value) for any of the 'n' dynamic sorting subscripts in the
 global specified by BY(0). 
VARIABLES: DISPAR(0,n)                  TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Like the FR(0,n) and TO(0,n) variables,
 this variable array can be set for any of the 'n' dynamic sorting subscripts
 in the global specified by BY(0). This array allows you to create subheaders
 for the sorting subscripts in the global. 
VARIABLES: DISPAR(0,n,'OUT')            TYPE: Input
 VARIABLES DESCRIPTION:   Note: 'OUT' should be "OUT".  
  
 (Optional) If a literal title is input to DISPAR(0,n) above, then you can also
 enter MUMPS code to transform the value of the subscript from the global
 before it is printed as a subheader. It acts like an output transform. 

NUMBER: 10011                           IA #: 10011
  DATE CREATED: NOV 16, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIWP
  NAME: Classic FileMan API: Word Processing
  ORIGINAL NUMBER: 10011                ID: DIWP
 GENERAL DESCRIPTION:   Call ^DIWP to format and (optionally) output any group
 of text lines. 
  STATUS: Active
COMPONENT/ENTRY POINT: DIWP
 COMPONENT DESCRIPTION:   Before calling ^DIWP, you should kill the global
 ^UTILITY($J,"W"). 
  
 ^DIWP works in two modes (based on whether the DIWF input parameter contains
 "W" or not): 
  
 1.  In ^DIWP's "accumulate" mode, repeated calls to ^DIWP accumulate and 
 format text in ^UTILITY($J,"W"). When you are done accumulating text, to write
 the text to the current device, you should call ^DIWW. ^DIWW writes the
 accumulated text to the current device with the margins you specified in your
 calls to ^DIWP, and then removes the text from ^UTILITY. 
  
 2.  In ^DIWP's "write" mode, if the text added to ^UTILITY($J,"W") by ^DIWP
 causes one or more (that is, n) line breaks, n lines are written to the
 current device (and the remaining partial line is stored in ^UTILITY.) This
 leaves one line of text in ^UTILITY once all calls to ^DIWP are completed. To
 write the remaining line of text to the current device and remove it from
 ^UTILITY, call ^DIWW. 
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   The string of text to be added as input to the
 formatter. The X input string may contain |-windows, as described in the VA
 FileMan User's Manual (e.g., |SETTAB(9,23,44)|). The expressions within the
 windows will be processed as long as they are not context-dependent; that is,
 as long as they do not refer symbolically to database field names. Thus, 
 |TODAY| will cause today's date to be inserted into the formatted text, but 
 |SSN| will be printed out as it stands, because it cannot be interpreted in
 context.  
VARIABLES: DIWL                         TYPE: Input
 VARIABLES DESCRIPTION:   The (integer-valued) left margin for the text. Set
 this to a postive number, 1 or greater. Do not change the value of DIWL if you
 are making repeated calls to ^DIWP to format text.  
VARIABLES: DIWR                         TYPE: Input
 VARIABLES DESCRIPTION:   The (integer-valued) right margin for the text. 
VARIABLES: DIWF                         TYPE: Input
 VARIABLES DESCRIPTION:   A string of format control parameters. If contained
 in DIWF, the parameters have the following effects: 
  
 W If the DIWF parameter contains "W", ^DIWP operates in "write" mode If the
 DIWF parameter does not contain "W", ^DIWP operates in "accumulate" mode. See
 above for the discussion of these two modes. 
  
 When making repeated calls to ^DIWP, don't mix modes; use "write" or 
 "accumulate" mode, but don't switch between them.  
  
 Cn = The text will be formatted in a column width of n, thus overriding the
 value of DIWR.  D = The text will be in double-spaced format.  In The text
 will be indented n columns in from the left margin (DIWL).  N = Each line will
 be printed as it appears in the text (no-wrap). If DIWF contains N, the value
 of DIWR will be ignored.  R = The text will be in right-justified format.  | =
 Word processing windows (material within vertical bars) will not be evaluated.
 The window will print as it exists in the word processing field.  

NUMBER: 10012                           IA #: 10012
  DATE CREATED: NOV 16, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIWF
  NAME: Classic FileMan API: Form Document Print
  ORIGINAL NUMBER: 10012                ID: DIWF
 GENERAL DESCRIPTION:   Designed to use the contents of a word processing field
 as a target document into which data can be inserted at print time.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   This entry point is used when the calling program
 knows which file (document file) contains the desired word processing text to
 be used as a target document. 
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   A file number or a global root. The file identified
 must contain a word processing field. 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   This will be -1 only if the file sent to DIWF in the
 variable DIC does not contain a word processing field. 
COMPONENT/ENTRY POINT: EN2
 COMPONENT DESCRIPTION:   This entry point is used when the calling program
 knows both the document file and the entry within that file which contains the
 desired word processing text to be used as a target document. 
VARIABLES: DIWF                         TYPE: Input
 VARIABLES DESCRIPTION:   The global root at which the desired text is stored.  
VARIABLES: DIWF(1)                      TYPE: Input
 VARIABLES DESCRIPTION:   If the calling program wants to specify which file
 should be used as a source for generating output, the number of that file
 should appear in the variable DIWF(1). Otherwise, the user will be asked the
 "Print from what FILE:" question. 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Y will be -1 if: 
  
 1.  There is no data beneath the root passed in DIWF. 2.  The file passed in
 DIWF(1) could not be found. 
COMPONENT/ENTRY POINT: DIWF
 COMPONENT DESCRIPTION:   To be used for interactive dialogue with the user. 

NUMBER: 10013                           IA #: 10013
  DATE CREATED: DEC 04, 2001            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIK
  NAME: Classic FileMan API: Entry Deletion & File Reindexing
  ORIGINAL NUMBER: 10013                ID: DIK
 GENERAL DESCRIPTION:   Multiple entry points to support entry deletion and
 file reindexing.  
  STATUS: Active
COMPONENT/ENTRY POINT: IXALL
 COMPONENT DESCRIPTION:   Reindexes all cross references for all entries in a
 file. 
VARIABLES: DIK                          TYPE: Input
 VARIABLES DESCRIPTION:   The global root of the file to be indexed. 
COMPONENT/ENTRY POINT: IX
 COMPONENT DESCRIPTION:   Reindexes all cross references of the file for only
 one entry in the file.  
VARIABLES: DIK                          TYPE: Input
 VARIABLES DESCRIPTION:   If you are reindexing an entry at the top level of a
 file, set DIK to the global root of the file.  
  
 If you are reindexing only a subentry, set DIK to the full global root leading
 to the subentry, including all intervening subscripts and the terminating
 comma, up to but not including the ien of the subfile entry to reindex.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   If you are reindexing an entry at the top level of a
 file, set DA to the internal entry number of the file entry to reindex.  
  
 If you are reindexing an entry in a subfile, set up DA as an array, where 
 DA=entry number in the subfile to reindex, DA(1) is the entry number at the
 next higher file level,...DA(n) is the entry number at the file's top level.  
COMPONENT/ENTRY POINT: IX1
 COMPONENT DESCRIPTION:   Reindexes all cross references of the file for only
 one entry in the file.  
VARIABLES: DIK                          TYPE: Input
 VARIABLES DESCRIPTION:   If you are reindexing an entry at the top level of a
 file, set DIK to the global root of the file.  
  
 If you are reindexing a subentry, set DIK to the full global root leading to
 the subentry, including all intervening subscripts and the terminating comma,
 up to but not including the ien of the subfile entry to reindex.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   If you are reindexing an entry at the top level of a
 file, set DA to the internal entry number of the file entry to reindex.  
  
 If you are reindexing an entry in a subfile, set up DA as an array, where 
 DA=entry number in the subfile to reindex, DA(1) is the entry number at the
 next higher file level,...DA(n) is the entry number at the file's top level.  
COMPONENT/ENTRY POINT: DIK
 COMPONENT DESCRIPTION:   Used to delete an entry from a file. 
VARIABLES: DIK                          TYPE: Input
 VARIABLES DESCRIPTION:   The global root of the file from which you want to
 delete an entry. 
  
 If you are deleting a subentry, set DIK to the full global root leading to the
 subentry, including all intervening subscripts and the terminating comma, up
 to but not including the ien of the subfile entry to delete.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   If you are deleting an entry at the top level of a
 file, set DA to the internal entry number of the file entry to delete. 
  
 If you are deleting an entry in a subfile, set up DA as an array, where 
 DA=entry number in the subfile to delete, DA(1) is the entry number at the 
 next higher file level,...DA(n) is the entry number at the file's top level. 
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Reindexes one or more cross references of a field for
 one entry in a file.  
VARIABLES: DIK                          TYPE: Input
 VARIABLES DESCRIPTION:   If you are reindexing an entry at the top level of a
 file, set DIK to the global root of the file.  
  
 If you are reindexing a subentry, set DIK to the full global root leading to
 the subentry, including all intervening subscripts and the terminating comma,
 up to but not including the ien of the subfile entry to reindex.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   If you are reindexing an entry at the top level of a
 file, set DA to the internal entry number of the file entry to reindex.  
  
 If you are reindexing an entry in a subfile, set up DA as an array, where 
 DA=entry number in the subfile to reindex, DA(1) is the entry number at the
 next higher file level,...DA(n) is the entry number at the file's top level.  
VARIABLES: DIK(1)                       TYPE: Input
 VARIABLES DESCRIPTION:   Use the field number (to get all indices) or the
 field number and specific indices of the cross reference. 
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   Reindexes one or more cross references of a field for
 one entry in a file.  It only executes the SET logic of the cross reference. 
VARIABLES: DIK                          TYPE: Input
 VARIABLES DESCRIPTION:   If you are reindexing an entry at the top level of a
 file, set DIK to the global root of the file.  
  
 If you are reindexing a subentry, set DIK to the full global root leading to
 the subentry, including all intervening subscripts and the terminating comma,
 up to but not including the ien of the subfile entry to reindex.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   If you are reindexing an entry at the top level of a
 file, set DA to the internal entry number of the file entry to reindex.  
  
 If you are reindexing an entry in a subfile, set up DA as an array, where 
 DA=entry number in the subfile to reindex, DA(1) is the entry number at the
 next higher file level,...DA(n) is the entry number at the file's top level.  
VARIABLES: DIK(1)                       TYPE: Input
 VARIABLES DESCRIPTION:   Use the field number (to get all cross references) or
 the field number and specific indices of the cross references you want. 
COMPONENT/ENTRY POINT: ENALL
 COMPONENT DESCRIPTION:   Reindexes all entries in a file for the cross
 references on a specific field. 
VARIABLES: DIK                          TYPE: Input
 VARIABLES DESCRIPTION:   If you are reindexing an entries at the top level of
 a file, set DIK to the global root of the file.  
  
 If you are reindexing subentries, set DIK to the full global root leading to
 the subentry, including all intervening subscripts and the terminating comma,
 up to but not including the iens of the subfile entries to reindex.  
VARIABLES: DIK(1)                       TYPE: Input
 VARIABLES DESCRIPTION:   Use the field number (to get all indices) or the
 field number and specific cross references separated by up-arrows.  
VARIABLES: DA(1..n)                     TYPE: Input
 VARIABLES DESCRIPTION:   If you are reindexing entries in a subfile, set up DA
 as an array, where DA(1) is the entry number at the next higher file
 level,...DA(n) is the entry number at the file's top level. Since ENALL^DIK
 reindexes all entries at a given file level, don't set the unsubscripted DA
 node.  
COMPONENT/ENTRY POINT: IX2
 COMPONENT DESCRIPTION:   Executes the KILL logic for only one entry at all
 file levels at or below the one specified in DIK.  
  
 Before calling this entry point, you should be familiar with the effects of
 executing the kill logic of the relevant cross-references (including 
 bulletins, triggers, and MUMPS-type).  
VARIABLES: DIK                          TYPE: Input
 VARIABLES DESCRIPTION:   If you are executing the kill logic for an entry at
 the top level of a file, set DIK to the global root of the file.  
          
 If you are executing the kill logic for a subentry, set DIK to the full global
 root leading to the subentry, including all intervening subscripts and the
 terminating comma, up to but not including the IEN of the subfile entry.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   If you are executing the kill logic for an entry at
 the top level of a file, set DA to the internal entry number of that file
 entry.  
          
 If you are executing the kill logic for an entry in a subfile, set up DA as an
 array, where DA is the entry number in the subfile, DA(1) is the entry number
 at the next higher file level, etc. DA(n) is the entry number at the file's
 top level.  
COMPONENT/ENTRY POINT: IXALL2
 COMPONENT DESCRIPTION:   Executes the KILL logic for all entries in a file.  
  
 Before calling this entry point, you should be familiar with the effects of
 executing the kill logic of the relevant cross-references (including 
 bulletins, triggers, and MUMPS-type).  
  
 NOTE: IXALL^DIK, IXALL2^DIK, ENALL^DIK, ENALL2^DIK, and the Re-Index File 
 option on the Utility Functions menu set the 3rd piece of the 0 node of the
 file's global root (the file header) to the last internal entry number used in
 the file. They set the 4th piece to the total number of entries in the file.  
VARIABLES: DIK                          TYPE: Input
 VARIABLES DESCRIPTION:   If you are executing the kill logic for all entries
 at the top level of a file, set DIK to the global root of the file.  
          
 If you are executing the kill logic for all entries in a subfile only, set DIK
 to the full global root of the subfile 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   If you are executing the kill logic for all entries
 at the top level of a file this variable need not be set.  
          
 If you are executing the kill logic for all entries in a subfile, set up DA as
 an array, where DA(1) is the entry number at the next higher file level, DA(2)
 is the entry number one level above that, etc. DA(n) is the entry number at
 the file's top level.  
COMPONENT/ENTRY POINT: EN2
 COMPONENT DESCRIPTION:   Executes the KILL logic for one or more
 cross-references on a specific field for one entry in a file.  
  
 Before calling this entry point, you should be familiar with the effects of
 executing the kill logic of the relevant cross-references (including 
 bulletins, triggers, and MUMPS-type).  
VARIABLES: DIK                          TYPE: Input
 VARIABLES DESCRIPTION:   If you are executing the kill logic for an entry at
 the top level of a file, set DIK to the global root of the file.  
          
 If you are executing the kill logic for a subentry, set DIK to the full global
 root leading to the subentry, including all intervening subscripts and the
 terminating comma, up to but not including, the IEN of the subfile entry.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   If you are executing the kill logic for an entry at
 the top level of a file, set DA to the internal entry number of that file
 entry.  
          
 If you are executing the kill logic for an entry in a subfile, set up DA as an
 array, where DA is the entry number in the subfile, DA(1) is the entry number
 at the next higher file level, etc. DA(n) is the entry number at the file's
 top level.  
VARIABLES: DIK(1)                       TYPE: Input
 VARIABLES DESCRIPTION:   Set DIK(1) to the field number (to get all
 cross-references defined on that field). For example: 
            
   S DIK(1)=.01 
         
 OR, set DIK(1) to the field number and the names or numbers of specific 
 cross-reference on that field, all separated by up-arrows (^). For example, 
          
   S DIK(1)=".01^B" 
   S DIK(1)=".01^B^C" 
   S DIK(1)=".01^1^2" 
COMPONENT/ENTRY POINT: ENALL2
 COMPONENT DESCRIPTION:   Executes the KILL logic for one or more
 cross-references on a specific field for all entries in a file.  
  
 Before calling this entry point, you should be familiar with the effects of
 executing the kill logic of the relevant cross-references (including 
 bulletins, triggers, and MUMPS-type).  
  
 NOTE: IXALL^DIK, IXALL2^DIK, ENALL^DIK, ENALL2^DIK, and the Re-Index File 
 option on the Utility Functions menu set the 3rd piece of the 0 node of the
 file's global root (the file header) to the last internal entry number used in
 the file. They set the 4th piece to the total number of entries in the file.  
VARIABLES: DIK                          TYPE: Input
 VARIABLES DESCRIPTION:   If you are executing the kill logic for all entries
 at the top level of a file, set DIK to the global root of the file.  
          
 If you are executing the kill logic for all entries in a subfile only, set DIK
 to the full global root of the subfile.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   If you are executing the kill logic for all entries
 at the top level of a file, this variable need not be set.  
          
 If you are executing the kill logic for all entries in a subfile, set up DA as
 an array, where DA(1) is the entry number at the next higher file level, DA(2)
 is the entry number one level above that, etc. DA(n) is the entry number at
 the file's top level.  
VARIABLES: DIK(1)                       TYPE: Input
 VARIABLES DESCRIPTION:   Set DIK(1) to the field number (to get all
 cross-references defined on that field). For example: 
            
   S DIK(1)=.01 
          
 OR, set DIK(1) to the field number and the names or numbers of specific 
 cross-reference on that field, all separated by up-arrows (^). For example, 
          
   S DIK(1)=".01^B" 
   S DIK(1)=".01^B^C" 
   S DIK(1)=".01^1^2" 

NUMBER: 10014                           IA #: 10014
  DATE CREATED: NOV 16, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIU2
  NAME: Classic FileMan API: Data Dictionary Deletion
  ORIGINAL NUMBER: 10014                ID: DIU2
 GENERAL DESCRIPTION:   Used to delete a file's data dictionary and its entry
 in ^DIC in order to properly update a running system. 
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Occasionally you may need to delete a file's data
 dictionary and its entry in ^DIC in order to properly update a running system.
 Use this entry point to do it. 
VARIABLES: DIU                          TYPE: Input
 VARIABLES DESCRIPTION:   The file number or global root.  This must be a
 subfile number when deleting a subfile's data dictionary. 
VARIABLES: DIU(0)                       TYPE: Input
 VARIABLES DESCRIPTION:   Input parameter string that may contain the
 following: 
  
 D DELETE the data as well as the data dictionary.  E ECHO back information
 during deletion.  S SUBFILE data dictionary is to be deleted.  T TEMPLATES are
 to be deleted.  

NUMBER: 10015                           IA #: 10015
  DATE CREATED: NOV 16, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIQ1
  NAME: Classic FileMan API: Data Retrieval
  ORIGINAL NUMBER: 10015                ID: DIQ1
 GENERAL DESCRIPTION:   This entry point retrieves data from a file for a
 particular entry.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This entry point retrieves data from a file for a
 particular entry. Note: The equivalent Database Server calls are GETS^DIQ and
 $$GET1^DIQ (see DBIA #2056).  
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   The file number or global root. 
VARIABLES: DR                           TYPE: Input
 VARIABLES DESCRIPTION:   A string specifying in which you specify the data
 fields to retrieve for the given entry. The DR-string may contain: 
  
 1.  A single number corresponding to the internal number of a field in the 
 file. 2.  A range of field numbers, in the form M:N, where M is the first and
 N the last number of the inclusive range. All fields whose numbers lie within
 this range will be retrieved.  3.  A combination of the above, separated by
 semicolons. If field numbers .01, 1, 2, 4, 10, 11, 12, 13, 14, 15, and 101
 exist for a file, and you want to retrieve the data in these fields, simply
 write: 
     S DR=".01;1;4;10:15;101" 
VARIABLES: DR(subfile_number)           TYPE: Input
 VARIABLES DESCRIPTION:   If you want to retrieve values from fields from a
 subentry in a multiple field, include the top-level field number for the
 multiple in DR. Then, include the multiple's subfield numbers whose values you
 want to retrieve in a node in DR, subscripted by the subfile number. 
  
 See also DA(subfile_number) below for how to specify which subfile entry to
 retrieve.  
  
 For example, if you want to retrieve data from subfields .01 and 7 for 
 subentry 1 from field 4 which defines the multiple 16000.02, then you write: 
  
     S DIC=16000,DR="4",DA=777 
     S DR(16000.02)=".01:7",DA(16000.02)=1 
     D EN^DIQ1 
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   The internal number of the entry from which data is
 to be extracted. 
VARIABLES: DA(subfile_number)           TYPE: Input
 VARIABLES DESCRIPTION:   If you want to retrieve values from fields from a
 subentry in a multiple, set DA to the top-level entry number. Then, include
 the subentry number in a node in DA, subscripted by the subfile number. See
 DR(subfile_number) below for how to specify which fields in the subfile entry
 to retrieve.  
  
 You can descend one or more subfile levels; however, you can only retrieve 
 values for one subentry at any given subfile level. The full path from the top
 level of the file to the lowest-level subfile entry must be fully specified in
 nodes in DR and DA.  
VARIABLES: DIQ                          TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The local array name into which the field
 values will be placed. ^UTILITY("DIQ1",$J, will be used if DIQ is not present.
 This array name should not begin with DI. 
VARIABLES: DIQ(0)                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This variable is used to tell EN^DIQ1
 whether to return internal values, external values, or both. DIQ(0) also
 indicates when null values are not returned. The DIQ(0) string can contain the
 values that follow: 
  
 I return internal values  E return external values  N do not return null
 values  
VARIABLES: ARRAY                        TYPE: Output
 VARIABLES DESCRIPTION:   The format and location of the output from EN^DIQ1
 depends on the status of input variables DIQ and DIQ(0) and on whether or not
 a word processing field is involved. 
  
 DIQ and DIQ(0) undefined 
  
 Output into: 
  
     ^UTILITY("DIQ1",$J,file#,DA,field#)=external value This is for backwards
 compatibility. Each field requested will be defined in the utility global, but
 the value may be null. The only exception to this would be when DA held the
 number of an entry which does not exist. In that case, nothing is returned.
 The values returned are the external, printable values-pointers, sets of
 codes, etc., are resolved; dates are in external format. 
  
 DIQ(0) defined, DIQ undefined 
  
 Output into: 
  
     ^UTILITY("DIQ1",$J,file#,DA,field#,"E")=external value 
     ^UTILITY("DIQ1",$J,file#,DA,field#,"I")=internal value If DIQ(0)["E", the
 external value is returned with a final global subscript of "E". 
  
 If DIQ(0)["I", the internally stored value is returned with a final global 
 subscript of "I". The internal value is the value stored in the file; for 
 example, the record number of the entry in the pointed-to file, not the 
 resolved value of the pointer. Since computed fields store no data, no nodes
 are returned for computed fields. 
  
 If DIQ(0)["N", no nodes are set for either internal or external values if the
 field is null. 
  
 If DIQ(0) contains both "I" and "E", generally two nodes are returned for each
 field: one with the internal value, one with the external value.  However, no
 nodes are produced for the internal value if the field is computed; and no
 nodes are produced at all for null-valued fields if DIC(0)["N". Nodes are
 subscripted as described above. 
  
 DIQ defined 
  
 The output is similar except that the data is stored in the specified local
 array. So if DIQ(0) is not defined, then the output is: 
  
     @(DIQ(file#,DA,field#))=external value If DIQ(0) is defined, then the
 output is: 
  
     @DIQ(file#,DA,field#,"E")=external value 
     @DIQ(file#,DA,field#,"I")=internal value Word Processing Field 
  
 Output from a word processing field will only be an external value. The status
 of DIQ(0) has no effect. If DIQ is not defined, it goes into the global nodes
 that follow: 
  
     ^UTILITY("DIQ1",$J,file#,DA,field#,1) 
     ^UTILITY("DIQ1",$J,file#,DA,field#,2) 
         .
         .
         .
 If DIQ is defined, it goes into: 
  
  
     @DIQ(file#,DA,field#,1)=External Value 1 
     @DIQ(file#,DA,field#,2)=External Value 2 
     @DIQ(file#,DA,field#,3)=External Value 3 
     @DIQ(file#,DA,field#,4)=External Value 4 
         .
         .
         .

NUMBER: 10016                           IA #: 10016
  DATE CREATED: NOV 17, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIM
  NAME: Classic FileMan API: MUMPS Code Validation
  ORIGINAL NUMBER: 10016                ID: DIM
 GENERAL DESCRIPTION:   Checks that code conforms to the 1995 ANSI Standard and
 is also checked against aspects of VHA's Programming Standards and Conventions
 (SAC). 
  STATUS: Active
COMPONENT/ENTRY POINT: DIM
 COMPONENT DESCRIPTION:   Checks that code conforms to the 1995 ANSI Standard
 and is also checked against aspects of VHA's Programming Standards and
 Conventions (SAC). 
VARIABLES: X                            TYPE: Both
 VARIABLES DESCRIPTION:   Input: The line of code to be validated.  
  
 Output: ^DIM either kills X, or leave it unchanged. If $D(X) is zero on return
 from ^DIM, the line of code is invalid. 

NUMBER: 10017                           IA #: 10017
  GLOBAL ROOT: DD('DD')                 CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DD DATE FORMATER                ORIGINAL NUMBER: 10017
  ID: DD('DD')
GLOBAL REFERENCE: DD('DD')
  STATUS: Active

NUMBER: 10018                           IA #: 10018
  DATE CREATED: NOV 17, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIE                          NAME: Classic FileMan API: Edit Data
  ORIGINAL NUMBER: 10018                ID: DIE
 GENERAL DESCRIPTION:   This routine handles input of selected data elements
 for a given file entry. 
  STATUS: Active
COMPONENT/ENTRY POINT: DIE
 COMPONENT DESCRIPTION:   This routine handles input of selected data elements
 for a given file entry. You should use ^DIE only to edit existing records.  
VARIABLES: DIE                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The global root of the file.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   (Required) If you are editing an entry at the top
 level of a file, set DA to the internal entry number of the file entry to be
 edited.  
  
 If you are editing an entry in a subfile, set up DA as an array, where 
 DA=entry number in the subfile to edit, DA(1) is the entry number at the next
 higher file level,...DA(n) is the entry number at the file's top level. 
VARIABLES: DR                           TYPE: Input
 VARIABLES DESCRIPTION:   (Required) A string specifying which data fields are
 asked for the given entry. The fields specified by DR are asked whether or not
 VA FileMan Write access security protection has been assigned to the fields.  
  
 You can include the following in the DR-string: 
  
 Field number Field with Default Value Stuff a Field Value (Validated) Stuff a
 Field Value (Unvalidated) Placeholder for Branching MUMPS Code Combination 
 Input Template 
VARIABLES: DIE("NO")                    TYPE: Input
 VARIABLES DESCRIPTION:   Note the variable name is: DIE("NO^") 
  
 (Optional) Controls the use of the ^ in an edit session. If this variable does
 not exist, unrestricted use of the ^ for jumping and exiting is allowed.  
  
 The variable may be set to one of the following: 
  
 "OUTOK"  Allows exiting and prevents all jumping. "BACK" Allows jumping back
 to a previously edited field and does not allow exiting.  "BACKOUTOK"  Allows
 jumping back to a previously edited field and allows exiting.  "Other value" 
 Prevents all jumping and does not allow exiting.  
VARIABLES: DIDEL                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Overrides the delete access on a file or
 subfile. 
VARIABLES: DTOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   Is set when a time-out has occurred.  

NUMBER: 10019                           IA #: 10019
  DATE CREATED: NOV 17, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIPZ
  NAME: Classic FileMan API: Print Template Compilation
  ORIGINAL NUMBER: 10019                ID: DIPZ
 GENERAL DESCRIPTION:   Print templates can be compiled into MUMPS routines.
 The purpose of this DIPZ code generation is simply to improve overall system
 throughput.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This entry point recompiles a print template without
 user intervention.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   The routine name.  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   The internal number of the template to be compiled. 
VARIABLES: DMAX                         TYPE: Input
 VARIABLES DESCRIPTION:   The maximum size the compiled routines should reach.
 Consider using the $$ROUSIZE^DILF (see DBIA #2054) function to set this
 variable. 
COMPONENT/ENTRY POINT: DIPZ
 COMPONENT DESCRIPTION:   Used for interactive print template compilation.  
VARIABLES: None

NUMBER: 10020                           IA #: 10020
  DATE CREATED: NOV 17, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIPT
  NAME: Classic FileMan API: Print/Sort Template Display
  ORIGINAL NUMBER: 10020                ID: DIPT
  STATUS: Active
COMPONENT/ENTRY POINT: DIBT
 COMPONENT DESCRIPTION:   The Sort Template file contains a computed field
 labeled SORT FIELDS which displays a sort template exactly as it was entered. 
VARIABLES: D0                           TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Set D0 equal to the internal number of the
 template in the Sort Template file. 
COMPONENT/ENTRY POINT: DIPT
 COMPONENT DESCRIPTION:   The Print Template file contains a computed field
 labeled PRINT FIELDS which displays the print template exactly as it was
 entered. 
VARIABLES: D0                           TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Set D0 equal to the internal number of the
 template in the Print Template file. 

NUMBER: 10021                           IA #: 10021
  DATE CREATED: NOV 17, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DID
  NAME: Classic FileMan API: Data Dictionary Listing
  ORIGINAL NUMBER: 10021                ID: DID
 GENERAL DESCRIPTION:   Print/display a file's data dictionary listing.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Print/display a file's data dictionary listing.  
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   Set to the data dictionary number of the file to
 list. 
VARIABLES: DIFORMAT                     TYPE: Input
 VARIABLES DESCRIPTION:   Set to the desired data dictionary listing format.
 Must be one of the following strings: STANDARD BRIEF MODIFIED STANDARD 
 TEMPLATES ONLY GLOBAL MAP CONDENSED 

NUMBER: 10022                           IA #: 10022
  DATE CREATED: NOV 13, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: %RCR                         NAME: Classic FileMan API: Array Moving
  ORIGINAL NUMBER: 10022                ID: %RCR
 GENERAL DESCRIPTION:   This entry point can be used to move arrays from one
 location to another.  The location can be local or global. 
  STATUS: Active
COMPONENT/ENTRY POINT: %XY
VARIABLES: %X                           TYPE: Input
 VARIABLES DESCRIPTION:   The global or array root of an existing array. The
 descendants of %X will be moved. 
VARIABLES: %Y                           TYPE: Output
 VARIABLES DESCRIPTION:   The global or array root of the target array. It
 would be best if this array did not exist before the call. 

NUMBER: 10023                           IA #: 10023
  DATE CREATED: NOV 18, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIB
  NAME: Classic FileMan API: User Controlled Editing
  ORIGINAL NUMBER: 10023                ID: DIB
 GENERAL DESCRIPTION:   Invokes the Enter or Edit File Entries option of VA
 FileMan to edit records in a given file, allowing the user to select which
 fields to edit.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Invokes the Enter or Edit File Entries option of VA
 FileMan to edit records in a given file, allowing the user to select which
 fields to edit.  
VARIABLES: DIE                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The global root of the file, the number of
 the file.  
VARIABLES: DIE('NO')                    TYPE: Input
 VARIABLES DESCRIPTION:   Note: the variable is: DIE("NO^") 
  
 (Optional) Allows the programmer control of the use of the up arrow in an edit
 session. If this variable does not exist, unrestricted use of the up arrow for
 jumping and exiting is allowed. 
  
 The variable may be set to one of the following: 
  
 "OUTOK"  Allows exiting and prevents all jumping. "BACK"  Allows jumping back
 to a previously edited field and does not allow exiting.  "BACKOUTOK"  Allows
 jumping back to a previously edited field and allows exiting.  "Other value" 
 Prevents all jumping and does not allow exiting.  
VARIABLES: DIDEL                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Allows you to override the Delete Access
 on a file or subfile. 

NUMBER: 10024                           IA #: 10024
  DATE CREATED: NOV 18, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DICD                         NAME: Classic FileMan API: Wait Messages
  ORIGINAL NUMBER: 10024                ID: DICD
 GENERAL DESCRIPTION:   Displays standard wait messages.  
  STATUS: Active
COMPONENT/ENTRY POINT: WAIT
 COMPONENT DESCRIPTION:   Displays standard wait messages.  
VARIABLES: None

NUMBER: 10025                           IA #: 10025
  DATE CREATED: NOV 17, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIKZ
  NAME: Classic FileMan API: Cross Reference Compilation
  ORIGINAL NUMBER: 10025                ID: DIKZ
 GENERAL DESCRIPTION:   Compiles cross references into MUMPS routines.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Recompiles a file's cross references without user
 intervention.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   The routine name.  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   The file number of the file for which you want the
 cross references recompiled. 
VARIABLES: DMAX                         TYPE: Input
 VARIABLES DESCRIPTION:   The maximum size the compiled routines should reach.
 Consider using the $$ROUSIZE^DILF (see DBIA # 2054) function to set this
 variable. 
COMPONENT/ENTRY POINT: DIKZ
 COMPONENT DESCRIPTION:   Interactive cross reference complication.  
VARIABLES: None

NUMBER: 10026                           IA #: 10026
  DATE CREATED: NOV 20, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIR                          NAME: Classic FileMan API: Reader
  ORIGINAL NUMBER: 10026                ID: DIR
 GENERAL DESCRIPTION:   DIR is a general purpose response reader that can be
 used to issue a prompt, read input interactively, perform syntax checking on
 the input, issue error messages or help text, and return input in a processed
 form.  Its use is recommended to standardize user dialogue and to eliminate 
 repetitive coding. 
  STATUS: Active
COMPONENT/ENTRY POINT: DIR
 COMPONENT DESCRIPTION:   DIR is a general purpose response reader that can be
 used to issue a prompt, read input interactively, perform syntax checking on
 the input, issue error messages or help text, and return input in a processed
 form.  Its use is recommended to standardize user dialogue and to eliminate 
 repetitive coding. DIR is reentrant: A DIR call may be made from within a DIR
 call. To reenter DIR, use the NEW command to save the DIR array (NEW DIR)
 before setting input variables and making the second call. 
VARIABLES: DIR(0)                       TYPE: Input
 VARIABLES DESCRIPTION:   DIR(0) is the only required input variable. It is a
 three piece variable.  The first character of the first piece must be defined
 (or first 3 characters for DD-type). Additional characters of the first piece
 and the second two pieces are all optional. 
  
 The first character of the first up-arrow piece indicates the type of the 
 input to be read. The second piece describes parameters, delimited by colons,
 to be applied to the input. Examples are maximum length for free text data or
 decimal digits for numeric data. The third piece is executable MUMPS code that
 acts on the input in the same manner as an input transform.  
  
 Piece-1 of DIR(0) (Subsequent Characters are Optional): 
  
 The first up-arrow piece of DIR(0) can contain other parameters that help to
 specify the nature of the input or modify the behavior of the reader.  These
 characters must appear after the character indicating type (or after the field
 number if it is a DD type). They are described below (examples are provided
 later in this section): 
  
 A Indicates that nothing should be appended to the programmer-supplied prompt
 DIR("A"), which is described below. If there is no DIR("A"), then no prompt is
 issued. 
  
 O Indicates that a response is optional. If this is not included, then a null
 response is not allowed. For DD type reads, the O is automatically included if
 the field in question is not a required field. 
  
 X Only applies to the set of codes. Indicates that an exact match is 
 requested. No lowercase to uppercase conversion is to be done. 
  
 B Only applies to a set of codes; indicates that the possible choices are to
 be listed horizontally after the prompt. 
  
 M Only applies to a set of codes and indicates that mixed case input is 
 allowed. Uppercase input, for example, would match a lowercase code. To 
 achieve this matching, do not include the X parameter since that would 
 override the M and require an exact match. 
  
 U Only applies to free text reads. It allows the user response to contain ^
 (up-arrow). A leading up-arrow aborts the read and set DUOUT and DIRUT whether
 or not U is in DIR(0). However, the U allows ^s to be embedded in the user
 response. 
  
 C Only applies to list reads. The values returned in Y and the Y() array are
 compressed. They are not expanded to include each individual number; rather,
 ranges of values are returned using the hyphen syntax. This is similar to the
 format in which the user can enter a ranges of numbers. 
  
 This flag is particularly useful when a user may select many numbers; for 
 example, when decimals are involved. The call is much faster and the 
 possibility of the local symbol table filling up with nodes in the Y() array
 is eliminated. 
  
 Piece-2 of DIR(0) (Optional) 
  
 Qualifying limits on user response are as described in summary table above. 
  
 Piece-3 of DIR(0) (Optional) 
  
 The third piece of DIR(0) is executable MUMPS code that acts like the input
 transform of a field in a data dictionary. The value that was entered by the
 user is contained in the variable X. The code can examine X and, if it is not
 appropriate, should kill X. If X is undefined after the execution of the third
 piece of DIR(0), the reader knows that the input was unacceptable, issues a
 help message, and re-asks for input.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) For DD-type reads only, if DIR("B") is not
 set, you may retrieve a value from the database to display as a default. 
VARIABLES: DIR("A")                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The reader provides a generic default
 prompt for each type, e.g., enter a number, or enter response. 
VARIABLES: DIR("A",#)                   TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) If you want to issue a longer message
 before actually reading the input, you can set the DIR("A",#) array in
 addition to DIR("A"). The #'s must be numeric. 
VARIABLES: DIR("B")                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Set this variable to the default response
 for the prompt issued. 
VARIABLES: DIR("L",#)                   TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Only applies to set-of-codes fields. Lets
 you replace the standard vertical listing of codes that the Reader displays
 with your own listing. 
VARIABLES: DIR("S")                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Use the DIR("S") variable to screen the
 allowable responses for pointer, set of codes, and list/range reads. 
VARIABLES: DIR("T")                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Time-out value to be used in place of
 DTIME. Value is represented in seconds. 
VARIABLES: DIR("?")                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This variable contains a simple help
 prompt which is displayed to the user when one question mark is entered. 
VARIABLES: DIR("?",#)                   TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This array allows the user to display more
 than one line of help when the user types a single question mark. 
VARIABLES: DIR("??")                    TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This variable, if defined, is a two-part
 variable. The first up-arrow piece may contain the name of a help frame. 
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   This is the unprocessed response entered by the user.
 It is always returned.  
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   Y is always defined as the processed output. 
  
 Date The date/time in VA FileMan format.  End-of-page Y=1 for continue (user
 pressed <RET>). Y=0 for exit (the user pressed up-arrow). Y="" for time out
 (the user timed out).  Free-text The data typed in by the user. In this case,
 it is the same as X.  List or range The list of numeric values, delimited by
 commas and ending with a comma. 
  
 If the C flag was not included in the first piece of DIR(0), an expanded list
 of numbers, including each individual number in a range, is returned.  If the
 C flag was included, a compressed list that uses the hyphen syntax to indicate
 a range of numbers is returned. 
  
 Any leading zeros or trailing zeros following the decimal point are removed;
 i.e., only canonic numbers are returned. If the list of returned numbers has
 more than 245 characters, integer-subscripted elements of Y [Y(1), Y(2), etc.]
 contain the additional numbers. Y(0) is always returned equal to Y.  Numeric 
 The canonic value of the number entered by the user; i.e., leading zeros are
 deleted and trailing zeros after the decimal are deleted.  Pointer The normal
 value of Y from a DIC lookup, that is, Internal Entry Number^Entry Name. If
 the lookup was unsuccessful, Y=-1.  Set of Codes The internal value of the
 response. Yes/No Y=1 for yes. Y=0 for no  DD (#,#) The first ^-piece of Y
 contains result of the variable X after it has been passed through the input
 transform of the field specified.  Depending on the data type involved,
 subsequent ^-pieces may contain additional information.  The following list
 summarizes the values of Y upon timeout, up-arrows, or <RET>s for all reads.
 Exceptions are noted. 
  
 Condition Value of Y  Comments Timeout Y=""  -- Up-arrow (^) Y=^ in all cases
 except end-of-page reads.  Y=0 upon end-of-page reads.  -- Double Up-arrow
 (^^)  Y=^^ -- Return Y="" for optional reads (reads allowing a null response). 
 
 Y=-1 for pointer reads. Y=0 for YES/NO type when NO is default. Y=1 for YES/NO
 type when YES is default. Y=1 for end-of-page reads. Y=default  when a default
 is provided other than forYES/NO type questions.  
VARIABLES: Y(0)                         TYPE: Output
 VARIABLES DESCRIPTION:   This is defined for the set of codes, list, pointer,
 date, and Yes/No reads. It is also returned for DD reads when the field has a
 set of codes, pointer, variable pointer, or date data type. 
VARIABLES: DTOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   If the read has timed-out, then DTOUT is defined. 
VARIABLES: DUOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   If the user entered a leading up-arrow, DUOUT is
 defined. 
VARIABLES: DIRUT                        TYPE: Output
 VARIABLES DESCRIPTION:   If the user enters a leading up-arrow, times out, or
 enters a null response, DIRUT is defined. 
VARIABLES: DIROUT                       TYPE: Output
 VARIABLES DESCRIPTION:   If the user entered two up-arrows, DIROUT is defined. 
 
VARIABLES: DIR("PRE")                   TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This variable contains M code that acts as
 a pre-validation transform. It can either change X, in which case the reader
 will proceed as though the new value is what the user entered, or kill X, in
 which case the reader will behave as though the user entered an illegal value. 
 
 DIR("PRE") is executed almost immediately after the READ takes place, just 
 after DTOUT is set if the READ timed out, and before any other checking is 
 done. The only inputs are X and DTOUT, and the only outputs are X and DTOUT.  

NUMBER: 10027                           IA #: 10027
  DATE CREATED: NOV 16, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIS
  NAME: Classic FileMan API: Search File Entries
  ORIGINAL NUMBER: 10027                ID: DIS
 GENERAL DESCRIPTION:   Search option for a specified file.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   You can call the Search File Entries option of VA
 FileMan for a given file when you want the user to be able to specify the
 search criteria. 
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The global root of the file in the form
 ^GLOBAL( or ^GLOBAL(#, or the number of the file. 

NUMBER: 10028                           IA #: 10028
  DATE CREATED: APR 28, 1994            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIWE                         NAME: Classic FileMan API: Text Editing
  ORIGINAL NUMBER: 10028                ID: DIWE
 GENERAL DESCRIPTION:   This routine is used to edit word processing text using
 VA FileMan's editors.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This routine is used to edit word processing text
 using VA FileMan's editors. If the user has established a Preferred Editor,
 through Kernel, that editor is presented for use. VA FileMan's editors expect
 the text to contain only printable ASCII characters.  
VARIABLES: DIC                          TYPE: Input
 VARIABLES DESCRIPTION:   The global root of where the text is located. 
VARIABLES: DWLW                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This variable indicates the maximum number
 of characters that will be stored on a word-processing global node. When the
 user enters text, the input line will not be broken to DWLW-characters until
 after <RET> is pressed. So, if DWLW=40 and the user types 90 characters before 
 pressing <RET>, the text would be stored in three lines in the global. If this
 variable is not set, the default value is 245. This variable is always killed
 by FileMan. 
VARIABLES: DWPK                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This variable determines how lines that
 are shorter than the maximum line length (set by DWLW) are treated by VA
 FileMan. It can be set to 1 or 2. This variable is always killed by FileMan. 
  
 DWPK=1 If the user enters lines shorter than the maximum line length in 
 variable DWLW, the lines will be stored as is; they will not be joined. If 
 lines longer than DWLW are entered, the lines will be broken at word 
 boundaries. 
  
 DWPK=2 If the user types lines shorter than the maximum line length in 
 variable DWLW, the lines will be joined until they get to the maximum length;
 the lines are "filled" to DWLW in length. If the lines are longer than DWLW,
 they will be broken at word boundaries. This is the default used if DWPK is
 not set prior to the EN^DIWE call. 
VARIABLES: DIWEPSE                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) If this variable is defined, before
 entering the Preferred Editor if the Preferred Editor is not the Line Editor,
 the user receives the following prompt: 
  
     Press RETURN to continue or '^' to exit: Set this variable if you want to
 allow the user to read information on the screen before the display is cleared
 by a screen-oriented editor. The variable is always killed by VA FileMan. 
VARIABLES: DIWESUB                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The first 30 characters of this variable
 are displayed within angle brackets (< and >) on the top border of the Screen
 Editor screen.  This variable is killed by VA FileMan. 
VARIABLES: DIWETXT                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The first IOM characters of this variable
 are displayed in high intensity on the first line of the Screen Editor screen.
 This variable is killed by VA FileMan. 
VARIABLES: DDWLMAR                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This variable indicates the initial column
 position of the left margin when the Screen Editor is invoked. The user can
 subsequently change the location of the left margin. This variable is killed
 by VA FileMan. 
VARIABLES: DDWRMAR                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This variable indicates the initial column
 position of the right margin when the Screen Editor is invoked. The user can
 subsequently change the location of the right margin. This variable is killed
 by VA FileMan. 
VARIABLES: DDWRW                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This variable indicates to the Screen
 Editor the line in the document on which the cursor should initially rest.
 This variable has effect only if the user's preferred editor is the Screen
 Editor and applies only when the Screen Editor is first invoked. If the user
 switches from the Screen Editor to another editor, and then back to the Screen 
 Editor, the cursor always rests initially on line 1. 
  
 If this variable is set to "B", the cursor will initially rest at the bottom
 of the document and the value of DDWC described below is ignored.  The default
 value of DDWRW is 1. This variable is killed by VA FileMan. 
VARIABLES: DDWC                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This variable indicates to the Screen
 Editor the initial column position of the cursor. The same restrictions
 described above for DDWRW apply to DDWC.  
  
 If this variable is set to "E", the cursor will initially rest at the end of
 the line defined by DDWRW. The default value of DDWC is 1. This variable is
 killed by VA FileMan. 
VARIABLES: DDWAUTO                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This variable can be set to an interval in
 minutes that the Screen Editor should automatically save the text for the
 user. It can be an integer between 1 and 120. If set to 0, no autosave occurs.
 The setting takes effect for only the current invokation of the Screen Editor 
 and can be changed by the user via the <PF1><PF1>S key sequence. The default
 value of DDWAUTO is 0. This variable is killed by FileMan.  
VARIABLES: DDWTAB                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This variable indicates to the Screen
 Editor the initial tab stop positions. The setting takes effect for only the
 current invokation of the Screen Editor and can subsequently be changed by the
 user via the <PF1><PF1><Tab> key sequence. 
  
 To set individual tab stops, set DDWTAB to a series of numbers separated by
 commas; for example, 
  
     DDWTAB = "4,7,15,20" 
  
 sets tab stops at columns 4, 7, 15, and 20. To set tab stops at repeated 
 intervals after the last stop, or after column 1, type the interval as +n; for
 example, 
  
     DDWTAB = "10,20,+5" 
  
 sets tab stops at columns 10, 20, 25, 30, 35, etc. 
  
 If not passed, the Screen Editor assumes DDWTAB = "+8"; that is, it initially
 sets tab stops at columns 1, 9, 17, 25, etc. This variable is killed by
 FileMan.  
VARIABLES: DWDISABL                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) This variable can be used to disable
 specific Line Editor commands. For example, if DWDISABL contains "P", then the
 Print command in the Line Editor is disabled. This variable is killed by
 FileMan.  
VARIABLES: DDWFLAGS                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Flags to control the behavior of the
 Screen Editor. The possible values are: 
  
 M - Indicates that the Screen Editor should initially be in NO WRAP Mode when
 invoked. 
  
 Q - Indicates that if the user attempts to Quit the editor with <PF1>Q, the
 confirmation message "Do you want to save changes?" is NOT asked.  
  
 R - Indicates that the Screen Editor should initially be in REPLACE mode when
 invoked. 
  
 This variable is killed by FileMan.  

NUMBER: 10029                           IA #: 10029
  DATE CREATED: NOV 16, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIWW
  NAME: Classic FileMan API: Output Last Line of Text
  ORIGINAL NUMBER: 10029                ID: DIWW
 GENERAL DESCRIPTION:   Use ^DIWW to output the remaining text left in
 ^UTILITY($J,"W") by ^DIWP to the current device. The ^DIWW entry point is
 designed to be used in conjunction with the ^DIWP entry point.  
  STATUS: Active
COMPONENT/ENTRY POINT: DIWW
 COMPONENT DESCRIPTION:   Use ^DIWW to output the remaining text left in
 ^UTILITY($J,"W") by ^DIWP to the current device. The ^DIWW entry point is
 designed to be used in conjunction with the ^DIWP entry point.  

NUMBER: 10030                           IA #: 10030
  GLOBAL ROOT: DD(ifn,0,'VR')           CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DD VERSION NODE                 ORIGINAL NUMBER: 10030
  ID: DD(ifn,0,'VR')
GLOBAL REFERENCE: DD(ifn,0,'VR')
 GLOBAL DESCRIPTION:   Read only access.  
           
 This optional node is created during an init at the discretion of the
 developer.  The developer can specify which files should have their version
 numbers updated.  If the developer fails to update the version number, the
 previous version number will remain in this node.  Developers must update this
 node to the current version for nationally supported software.  
  STATUS: Active

NUMBER: 10031                           IA #: 10031
  DATE CREATED: NOV 18, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DDS                          NAME: ScreenMan API: Form Processor
  ORIGINAL NUMBER: 10031                ID: DDS
 GENERAL DESCRIPTION:   You can call this entry point directly from a MUMPS
 routine to invoke the specified form.  
  STATUS: Active
COMPONENT/ENTRY POINT: DDS
 COMPONENT DESCRIPTION:   This routine invokes a ScreenMan form attached to the
 specified file.  ScreenMan automatically uses incremental locks to lock all
 records accessed during an editing session. 
VARIABLES: DDSFILE                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The number or global root of the Primary
 File of the form. 
VARIABLES: DR                           TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The name of the form (an entry in the Form
 file) enclosed in square brackets.  
VARIABLES: DA                           TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The record number of the file entry to
 display or edit. If DA is null or undefined, the form must either contain no
 data dictionary fields or have a Record Selection page, which is the first
 page ScreenMan presents to the user and is where the user can select a record
 from the file.  
VARIABLES: DDSPAGE                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) The Page Number of the first page to
 display to the user. If '$G(DDSPAGE), a page with a Page Number equal to 1
 must exist on the form, and that is the first page ScreenMan presents to the
 user. 
VARIABLES: DDSPARM                      TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) A string of alphabetic characters that
 control ScreenMan's behavior are listed below: 
  
 C Return the variable DDSCHANG=1 if ScreenMan detects that the user saved a
 Change to the database.  E Return Error messages in ^TMP("DIERR",$J), and
 return DIERR if ScreenMan encounters problems when initially trying to load
 the form. If DDSPARM does not contain an "E", ScreenMan prints messages
 directly on the screen, and returns the variable DIMSG equal to null.  S
 Return the variable DDSSAVE=1 if the user pressed <PF1>S or <PF1>E, or entered
 an "Exit" or "Save" command from the Command Line, whether or not any changes
 were actually made on the form.  
VARIABLES: DDSFILE(1)                   TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Contains the subfile number or the global
 root of the subfile. 
VARIABLES: DA(1) ... DA(n)              TYPE: Input
 VARIABLES DESCRIPTION:   The DA array, where DA is the subrecord number at the
 deepest level and DA(n) is the record number at the top level. 
VARIABLES: DDSCHANG                     TYPE: Output
 VARIABLES DESCRIPTION:   $G(DDSCHANG)=1, if the DDSPARM input variable to ^DDS
 contains a "C" and ScreenMan detects that the user saved a change to the
 database. 
VARIABLES: DDSSAVE                      TYPE: Output
 VARIABLES DESCRIPTION:   $G(DDSSAVE)=1, if the DDSPARM input variable to ^DDS
 contains an "S" and the user pressed <PF1>E or <PF1>S, or issued the "Save" or
 "Exit" command from the Command Line. 
VARIABLES: DIMSG                        TYPE: Output
 VARIABLES DESCRIPTION:   $D(DIMSG)>0, if the form could not be loaded, and the
 DDSPARM input variable to ^DDS does not contain an "E". 
VARIABLES: DTOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   $D(DTOUT)>0, if the user times out during the editing
 session. 

NUMBER: 10032                           IA #: 10032
  DATE CREATED: NOV 13, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIAC
  NAME: Classic FileMan API: File Access Determination
  ORIGINAL NUMBER: 10032                ID: DIAC
 GENERAL DESCRIPTION:   Used to determine if a user has access to a file.  
  STATUS: Active
COMPONENT/ENTRY POINT: DIAC
 COMPONENT DESCRIPTION:   Used to determine if a user has access to a file.  
VARIABLES: DIFILE                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The file number of the file on which you
 want to verify file access. 
VARIABLES: DIAC                         TYPE: Both
 VARIABLES DESCRIPTION:   Input: (Required) Use one of the values listed below
 to verify the specified type of file access: 
  
 "RD"  Verify Read access to a specific file. "WR"  Verify Write access to a
 specific file. "AUDIT"  Verify Audit access to a specific file. "DD"  Verify
 DD access to a specific file. "DEL"  Verify Delete access to a specific file. 
 "LAYGO"  Verify LAYGO access to a specific file. 
  
  
 Output: Either 0 or 1.  1 = user has the type of access.  0 = user does not
 have the type of access.  
VARIABLES: %                            TYPE: Output
 VARIABLES DESCRIPTION:   Either a 0 or 1.  
  
 1 = user has the type of access.  0 = user does not have the type of access.  

NUMBER: 10033                           IA #: 10033
  DATE CREATED: NOV 17, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIFGG                        NAME: Other API: Filegram
  ORIGINAL NUMBER: 10033                ID: DIFGG
 GENERAL DESCRIPTION:   Generates a filegram.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Filegram generator.  
VARIABLES: DIFGT                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This variable must equal the internal
 entry number in the Print Template file of the filegram template that defines
 the data to be sent.  
VARIABLES: DIFG("FE")                   TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This variable must equal the internal
 number in the base file of the entry to be sent. 
VARIABLES:  
VARIABLES: DIFG("FUNC")                 TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This variable must equal A, M, L or D. The
 meanings of these codes, which indicate the mode of the filegram, are: 
  
 A ADD (force an add)  M MODIFY  L LAYGO  D DELETE  
VARIABLES: DIFG("FGR")                  TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Set this variable equal to the root of the
 global or local array in which the filegram will be built. The default is 
 ^UTILITY("DIFG",$J, if this variable is not defined.  
VARIABLES: DILC                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) One less than the first subscript to
 generate. Default=0. 
VARIABLES: DITAB                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Initial indentation level for filegram
 text. 
VARIABLES: DIFGER                       TYPE: Output
 VARIABLES DESCRIPTION:   This output variable is defined if an error has
 occurred. Its possible values are: 
  
 A required variable was not passed. A variable's format is invalid. A
 variable's content is invalid. 

NUMBER: 10034                           IA #: 10034
  DATE CREATED: NOV 17, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIFG                         NAME: Other API: Filegram
  ORIGINAL NUMBER: 10034                ID: DIFG
 GENERAL DESCRIPTION:   Used to to install filegrams.  
  STATUS: Active
COMPONENT/ENTRY POINT: DIFG
 COMPONENT DESCRIPTION:   Used to to install filegrams.  
VARIABLES: DIFGLO                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) This variable must be the global root of
 the filegram to be installed. 
VARIABLES: DIADD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) If this variable is defined, a new entry
 will be created in the base file. 
VARIABLES: DINUM                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Entry number in base file at which new
 file entry, if added, will be created.  
VARIABLES: DIFGER                       TYPE: Output
 VARIABLES DESCRIPTION:   This output variable is defined if an error has
 occurred. 
VARIABLES: DIFGY                        TYPE: Output
 VARIABLES DESCRIPTION:   ^DIFG always returns DIFGY. DIFGY can have one of the
 following values: 
  
 DIFGY=-1 Indicates that the lookup on the initial file processed (the base 
 file) was unsuccessful.  
  
 DIFGY=N^F Where N is the internal number of the entry in the base file and F
 is the base file's number.  
  
 DIFGY=N^F^1 Where N and F are defined as above and 1 indicates that a new 
 entry has been added to the base file.  

NUMBER: 10035                           IA #: 10035
  FILE NUMBER: 2                        GLOBAL ROOT: DPT(
  DATE CREATED: SEP 13, 2017            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PATIENT FILE                    ORIGINAL NUMBER: 10035
  ID: DPT(
GLOBAL REFERENCE: DPT(
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .02                       FIELD NAME: SEX
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .03                       FIELD NAME: DATE OF BIRTH
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .05                       FIELD NAME: MARITAL STATUS
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .07                       FIELD NAME: OCCUPATION
  LOCATION: 0;7                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .08                       FIELD NAME: RELIGIOUS PREFERENCE
  LOCATION: 0;8                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .09                       FIELD NAME: SOCIAL SECURITY NUMBER
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .091                      FIELD NAME: REMARKS
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .092                      FIELD NAME: PLACE OF BIRTH [CITY]
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .093                      FIELD NAME: PLACE OF BIRTH [STATE]
  LOCATION: 0;12                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .033                      FIELD NAME: AGE
  LOCATION: COMPUTED                    ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Computed field 
FIELD NUMBER: .14                       FIELD NAME: CURRENT MEANS TEST STATUS
  LOCATION: 0;14                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .096                      FIELD NAME: WHO ENTERED PATIENT
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .097                      FIELD NAME: DATE ENTERED INTO FILE
  LOCATION: 0;16                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.1)
FIELD NUMBER: .1                        FIELD NAME: WARD LOCATION
  LOCATION: .1;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.101)
FIELD NUMBER: .101                      FIELD NAME: ROOM-BED
  LOCATION: .101;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
GLOBAL REFERENCE: DPT(D0,.36)
FIELD NUMBER: .363                      FIELD NAME: PRIMARY LONG ID
  LOCATION: .36;3                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .364                      FIELD NAME: PRIMARY SHORT ID
  LOCATION: .36;4                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.102)
FIELD NUMBER: .102                      FIELD NAME: CURRENT MOVEMENT
  LOCATION: .102;1                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.103)
FIELD NUMBER: .103                      FIELD NAME: TREATING SPECIALTY
  LOCATION: .103;1                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.104)
FIELD NUMBER: .104                      FIELD NAME: PROVIDER
  LOCATION: .104;1                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.1041)
FIELD NUMBER: .1041                     FIELD NAME: ATTENDING PHYSICIAN
  LOCATION: .1041;1                     ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.105)
FIELD NUMBER: .105                      FIELD NAME: CURRENT ADMISSION
  LOCATION: .105;1                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.106)
FIELD NUMBER: .106                      FIELD NAME: LAST DMMS EPISODE NUMBER
  LOCATION: .106;1                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.107)
FIELD NUMBER: .107                      FIELD NAME: LODGER WARD LOCATION
  LOCATION: .107;1                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.108)
FIELD NUMBER: .108                      FIELD NAME: CURRENT ROOM
  LOCATION: .108;1                      ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.35)
FIELD NUMBER: .351                      FIELD NAME: DATE OF DEATH
  LOCATION: .35;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .352                      FIELD NAME: DEATH ENTERED BY
  LOCATION: .35;2                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DPT(D0,.02,
FIELD NUMBER: .01                       FIELD NAME: RACE INFORMATION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.06,
FIELD NUMBER: .01                       FIELD NAME: ETHNICITY INFORMATION
  LOCATION: 0;1                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.13)
FIELD NUMBER: .132                      FIELD NAME: PHONE NUMBER [WORK]
  LOCATION: .13;2                       ACCESS: Read w/Fileman
FIELD NUMBER: .134                      FIELD NAME: PHONE NUMBER [CELLULAR]
  LOCATION: .13;4                       ACCESS: Read w/Fileman
FIELD NUMBER: .133                      FIELD NAME: EMAIL ADDRESS
  LOCATION: .13;3                       ACCESS: Read w/Fileman
GLOBAL REFERENCE: DPT(D0,.109
FIELD NUMBER: .109                      FIELD NAME: EXCLUDE FROM FACILITY DIR
  LOCATION: .109;1                      ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   Denotes whether or not the patient wished to be excluded
 from the Facility Directory for current admission.  This field is only stored
 for current inpatients.  It must NOT be edited as this could affect the
 integrity of many options within PIMS and other packages.  
GLOBAL REFERENCE: DPT(D0,.24)
FIELD NUMBER: .2405                     FIELD NAME: PREFERRED NAME
  LOCATION: .24;5                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The PREFERRED NAME field identifies the name that the
 patient would  prefer to be referenced by during interactions at the medical
 facility.  
 GENERAL DESCRIPTION:   Any nationally released cross-reference on the
 supported fields in this Integration Agreement are "open/supported" for direct
 global reference (as well as reference through VA FileMan).  
  STATUS: Active                        DATE ACTIVATED: JAN 25, 2023

NUMBER: 10036                           IA #: 10036
  DATE CREATED: MAR 07, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGPMLOS                      NAME: DGPMLOS
  ORIGINAL NUMBER: 10036                ID: DGPMLOS
 GENERAL DESCRIPTION:   Obtain length of stay by admission.  
  STATUS: Active
COMPONENT/ENTRY POINT: DGPMLOS
 COMPONENT DESCRIPTION:   
  
 DGPMLOS        Supported call to obtain the length of stay, leave days, pass
 days, and ASIH days for a specific admission.  See documentation included in
 the routine.  
VARIABLES: DGPMIFN                      TYPE: Input
 VARIABLES DESCRIPTION:   IFN of admission movement for which you want LOS to
 be calculated.  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   Total elapsed time^Time on absence^time on pass^time
 ASIH^Length of stay 

NUMBER: 10037                           IA #: 10037
  DATE CREATED: NOV 16, 1999            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DGRPD                        NAME: DGRPD
  ORIGINAL NUMBER: 10037                ID: DGRPD
 GENERAL DESCRIPTION:   Patient Inquiry.  
  STATUS: Active
COMPONENT/ENTRY POINT: DGRPD
 COMPONENT DESCRIPTION:   Routine to display patient inquiry screen(s).  
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Called to perform patient inquiry with DFN already
 known.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal entry number of the PATIENT file (#2) for
 which the patient inquiry should display.  

NUMBER: 10038                           IA #: 10038
  FILE NUMBER: 40.5                     GLOBAL ROOT: HOLIDAY(
  DATE CREATED: OCT 28, 1994            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: HOLIDAY FILE                    ORIGINAL NUMBER: 10038
  ID: HOLIDAY(
GLOBAL REFERENCE: HOLIDAY(...
FIELD NUMBER: All fields                ACCESS: Read w/Fileman
  STATUS: Active

NUMBER: 10039                           IA #: 10039
  FILE NUMBER: 42                       GLOBAL ROOT: DIC(42,
  DATE CREATED: OCT 28, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: WARD LOCATION FILE              ORIGINAL NUMBER: 10039
  ID: DIC(42,
GLOBAL REFERENCE: DIC(42,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: .015                      FIELD NAME: DIVISION
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: DIC(42,D0,44)
FIELD NUMBER: 44
  FIELD NAME: HOSPITAL LOCATION FILE POINTER
  LOCATION: 44;1                        ACCESS: Direct Global Read & w/Fileman
  STATUS: Active                        DATE ACTIVATED: JUN 29, 2009

NUMBER: 10040                           IA #: 10040
  FILE NUMBER: 44                       GLOBAL ROOT: SC(
  CUSTODIAL PACKAGE: SCHEDULING         CUSTODIAL ISC: Albany
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: HOSPITAL LOCATION FILE
  ORIGINAL NUMBER: 10040                ID: SC(
GLOBAL REFERENCE: SC(D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
 FIELD DESCRIPTION:   The "B" x-ref may also be accessed through direct global
 read.  
FIELD NUMBER: 1                         FIELD NAME: ABBREVIATION
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: TYPE
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: INSTITUTION
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2.1                       FIELD NAME: TYPE EXTENSION
  LOCATION: 0;22                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3.5                       FIELD NAME: DIVISION
  LOCATION: 0;15                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,42)
FIELD NUMBER: 42                        FIELD NAME: WARD LOCATION FILE POINTER
  LOCATION: 42;1                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,'OOS')
FIELD NUMBER: 50.01                     FIELD NAME: OCCASION OF SERVICE CLINIC?
  LOCATION: OOS;1                       ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 50.02                     FIELD NAME: OOS CALLING PACKAGE
  LOCATION: OOS;2                       ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC(D0,'I')
FIELD NUMBER: 2505                      FIELD NAME: INACTIVATE DATE
  LOCATION: I;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2506                      FIELD NAME: REACTIVATE DATE
  LOCATION: I;2                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: SC('B')
GLOBAL REFERENCE: SC('AVADPR')
 GENERAL DESCRIPTION:   10/13/26: Cross-ref 'AVADPR' was added 
  STATUS: Active

NUMBER: 10041                           IA #: 10041
  DATE CREATED: APR 03, 2003            CUSTODIAL PACKAGE: SCHEDULING
  CUSTODIAL ISC: Albany                 USAGE: Controlled Subscription
  TYPE: Routine                         ROUTINE: SDACS
  NAME: SDACS                           ORIGINAL NUMBER: 10041
  ID: SDACS                             STATUS: Retired
COMPONENT/ENTRY POINT: EN3
 COMPONENT DESCRIPTION:   Allows other packages to stuff stop codes.  NOTE: for
 a given date you are not allowed to enter more than six 900 type stop codes or
 a total of 15 stop codes.  
VARIABLES: SDUZ                         TYPE: Input
 VARIABLES DESCRIPTION:   If SDUZ is not defined DUZ will be used (User IFN) 
VARIABLES: SDIV                         TYPE: Input
 VARIABLES DESCRIPTION:   Institution file pointer.  
VARIABLES: SDATE                        TYPE: Input
 VARIABLES DESCRIPTION:   Date of visit (yyymmdd) 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Patient IFN.  
VARIABLES: SDC                          TYPE: Input
 VARIABLES DESCRIPTION:   Stop code #'s separated by "^" (not pointer number);
 or SDC="" if no stop codes; can not contain stop code 900 
VARIABLES: SDCTYPE                      TYPE: Input
 VARIABLES DESCRIPTION:   Type of codes.  S for Stop Codes, C for CPT codes, B
 for Both.  
VARIABLES: SDMSG                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) If not set or =0, error msg is suppressed. 
 
 If improperly set or $D(ZTQUEUED), reset to 0.  "S" to print general and Stop
 Code errors.  "C" to print general and CPT errors.  "B" to print all messages 
VARIABLES: SDCPT(x)                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional), use for CPT codes); x=array number from
 1-5.  Format: 900^associated clinic ptr^CPT^CPT^CPT^CPT^CPT where CPT is the 
 procedure code & 900 is the flag for CPT's.  The string must contain at least
 one procedure and not more than 5.  
VARIABLES: SDCLINIC                     TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Pointer to a clinic in file 44.  
VARIABLES: SDOEP                        TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Pointer to the parent Outpatient Encounter
 entry.  
VARIABLES: SDATYPE                      TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Pointer to Appointment Type file 
VARIABLES: SDERR                        TYPE: Output
 VARIABLES DESCRIPTION:   0=successfully updated at least one stop code 1=no
 updating occurred 
SUBSCRIBING PACKAGE: PROSTHETICS        ISC: Birmingham
SUBSCRIBING PACKAGE: LAB SERVICE        ISC: Dallas
SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT
  ISC: Birmingham
SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE
  ISC: Hines
SUBSCRIBING PACKAGE: EVENT CAPTURE      ISC: Birmingham

NUMBER: 10042                           IA #: 10042
  CUSTODIAL PACKAGE: SCHEDULING         CUSTODIAL ISC: Albany
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: SDM
  NAME: SDM                             ORIGINAL NUMBER: 10042
  ID: SDM                               STATUS: Active
COMPONENT/ENTRY POINT: OERR

NUMBER: 10043                           IA #: 10043
  FILE NUMBER: 50                       GLOBAL ROOT: PSDRUG(
  DATE CREATED: JUN 08, 2005
  CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT
  CUSTODIAL ISC: Birmingham             USAGE: Supported
  TYPE: File                            NAME: DRUG FILE
  ORIGINAL NUMBER: 10043                ID: PSDRUG(
GLOBAL REFERENCE: PSDRUG(D0,0)
FIELD NUMBER: .01                       FIELD NAME: GENERIC NAME
  LOCATION: 0;1                         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 EMAIL GROUP 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: Retired                       EXPIRATION DATE: JUN 01, 2006

NUMBER: 10044                           IA #: 10044
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUS
  NAME: XUS                             ORIGINAL NUMBER: 10044
  ID: XUS                               STATUS: Active
COMPONENT/ENTRY POINT: H
 COMPONENT DESCRIPTION:   Programmer Halt 

NUMBER: 10045                           IA #: 10045
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSHSHP
  NAME: XUSHSHP                         ORIGINAL NUMBER: 10045
  ID: XUSHSHP                           STATUS: Active
COMPONENT/ENTRY POINT: DE
 COMPONENT DESCRIPTION:   Decipher any data string 
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Encrypt any data string 
COMPONENT/ENTRY POINT: HASH
 COMPONENT DESCRIPTION:   Hash Electronic Signature 

NUMBER: 10046                           IA #: 10046
  DATE CREATED: APR 05, 2018            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUWORKDY                     NAME: XUWORKDY
  ORIGINAL NUMBER: 10046                ID: XUWORKDY
 GENERAL DESCRIPTION:   Several extrinsic functions for workdays.  To use any
 of the XUWORKDY extrinsic functions, you must make sure that the HOLIDAY file
 (#40.5) is populated with each year's holidays.  This file is distributed
 without data.  Only enter holidays that fall on weekdays.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: WORKDAY
COMPONENT/ENTRY POINT: $$EN
 COMPONENT DESCRIPTION:   Extrinsic function that calculates the number of
 workdays between two given dates (date1, date2).  It returns a positive value
 if date1<date2 and a negative value if date1>date2.  
VARIABLES: date1                        TYPE: Input
 VARIABLES DESCRIPTION:   Starting date in VA FileMan internal format (e.g.
 3180405).  
VARIABLES: date2                        TYPE: Input
 VARIABLES DESCRIPTION:   Ending date in VA FileMan internal format (e.g.
 3180412).  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns the number of workdays in the interval.  
COMPONENT/ENTRY POINT: $$WORKDAY
 COMPONENT DESCRIPTION:   Extrinsic function that checks the given date is a
 workday.  Returns 1 if true and 0 if false.  
VARIABLES: date                         TYPE: Input
 VARIABLES DESCRIPTION:   Date to check in VA FileMan internal format (e.g.
 3180412).  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns 1 if date is a workday and 0 if date is not a
 workday.  
COMPONENT/ENTRY POINT: $$WORKPLUS
 COMPONENT DESCRIPTION:   Extrinsic function that returns the date that is the
 number of working days (offset) from the given date.  The offset can be a
 positive or negative number.  
VARIABLES: date                         TYPE: Input
 VARIABLES DESCRIPTION:   Starting date in VA FileMan internal format (e.g.
 3180412).  
VARIABLES: offset                       TYPE: Input
 VARIABLES DESCRIPTION:   The number of days to offset.  If a positive number,
 will search forward in time.  If a negative number, will search in the past.  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns the date in VA FileMan internal format.  
COMPONENT/ENTRY POINT: XUWORKDY
 COMPONENT DESCRIPTION:   Calling the routine XUWORKDY from the top is
 obsolete.  The extrinsic function, $$EN^XUWORKDY(date1,date2), replaces this
 call.  
  DATE ACTIVATED: APR 09, 2018

NUMBER: 10047                           IA #: 10047
  FILE NUMBER: 3                        GLOBAL ROOT: DIC(3,
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: USER FILE
  ORIGINAL NUMBER: 10047                ID: DIC(3,
GLOBAL REFERENCE: DIC(3,...
FIELD NUMBER: All Fields                ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   All fields are presently supported for READ access. DO
 NOT use for new development, this file is soon to be retired.  
  
 The file may be referenced during conversion utilities to the New Person file. 
 
  STATUS: Active

NUMBER: 10048                           IA #: 10048
  FILE NUMBER: 9.4                      GLOBAL ROOT: DIC(9.4,
  DATE CREATED: OCT 24, 1994            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: PACKAGE FILE                    ORIGINAL NUMBER: 10048
  ID: DIC(9.4,
GLOBAL REFERENCE: DIC(9.4,...
FIELD NUMBER: All Fields                ACCESS: Read w/Fileman
  STATUS: Active

NUMBER: 10049                           IA #: 10049
  FILE NUMBER: 16                       GLOBAL ROOT: DIC(16,
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: File
  NAME: PERSON FILE                     ORIGINAL NUMBER: 10049
  ID: DIC(16,
GLOBAL REFERENCE: DIC(16,...
FIELD NUMBER: All Fields                ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   All fields are presently supported for READ only.  DO NOT
 use for new development as this file is soon to be retired.  
  
 The file may be referenced during conversion utilities to the New Person file. 
 
  STATUS: Retired

NUMBER: 10050                           IA #: 10050
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSESIG
  NAME: XUSESIG                         ORIGINAL NUMBER: 10050
  ID: XUSESIG                           STATUS: Active
COMPONENT/ENTRY POINT: SIG
 COMPONENT DESCRIPTION:   Verify Electronic Signature 

NUMBER: 10051                           IA #: 10051
  DATE CREATED: JUL 29, 2003            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUVERIFY                     NAME: XUVERIFY
  ORIGINAL NUMBER: 10051                ID: XUVERIFY
 GENERAL DESCRIPTION:   Utilities to check access and verify codes.  
  STATUS: Active
COMPONENT/ENTRY POINT: XUVERIFY
 COMPONENT DESCRIPTION:   Verify Access & Verify codes Calling this routine
 from the top gives an interactive request for the users Access and/or Verify
 codes.  
  
 The variables % and %DUZ must be set before running this program   % - may
 equal "A","V" OR both "AV" 
           %DUZ - must equal the users DUZ 
  
 After the program is run % will return -1,0,1,2 
  if %=-1 an "^" was entered  if %=0 an "?" was entered 
  if %=1 the Code typed was correct 
  if %=2 the Code was typed incorrectly 
VARIABLES: %                            TYPE: Both
 VARIABLES DESCRIPTION:   On input % - may equal "A","V" OR both "AV" 
  
 On return 
  if %=-1 an "^" was entered 
  if %=0 an "?" was entered 
  if %=1 the Code typed was correct 
  if %=2 the Code was typed incorrectly 
VARIABLES:  
VARIABLES: %DUZ                         TYPE: Input
 VARIABLES DESCRIPTION:   
  %DUZ - must equal the users DUZ 
COMPONENT/ENTRY POINT: $$CHKAV
 COMPONENT DESCRIPTION:   This entry point accepts a string containing the
 access and verify codes entered by the user, delimited by a semi-colon; the
 pointer to the user in the New Person file #200 is returned if successfully
 validated, otherwise a zero is returned.  Usage  S
 USER=$$CHKAV^XUVERIFY(ACCESS_";"_VERIFY) 
VARIABLES: AVCODE                       TYPE: Input
 VARIABLES DESCRIPTION:   This value is the access and verify codes entered by
 the user, delimited by a semi-colon.  
VARIABLES: $$CHKAV                      TYPE: Output
 VARIABLES DESCRIPTION:   The IEN to file 200 is returned if successful,
 otherwise zero.  

NUMBER: 10052                           IA #: 10052
  DATE CREATED: FEB 08, 2011            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XUSCLEAN                     NAME: XUSCLEAN
  ORIGINAL NUMBER: 10052                ID: XUSCLEAN
  STATUS: Active
COMPONENT/ENTRY POINT: KILL
 COMPONENT DESCRIPTION:   Clear all but Kernel Variables (in Sign-on/Security
 chapter) 
COMPONENT/ENTRY POINT: XUTL
 COMPONENT DESCRIPTION:   Will delete $JOB ($J) subscripted temporary globals
 as follows: 
  
      ^TMP($J) and ^TMP(subscript,$J) 
  
      ^UTILITY($J), and ^UTILITY(subscript,$J) (subscripts ROU, GLO, LRLTR will
 NOT be deleted) 
  
      ^XUTL($J) and ^XUTL(subscript,$J)  (subscripts XQO, XGATR, XGKB will NOT
 be deleted) 
             
      Will also delete ^XUTL("ZISPARAM",$I) and clean up FileMan variables 
 (calls CLEAN^DILF).  
COMPONENT/ENTRY POINT: TOUCH
 COMPONENT DESCRIPTION:   If a task appears to have been running longer than 7
 days, Kernel assumes that it really isn't running anymore and kills off its
 temp global and user stack.  
  
 If your task legitimately runs more than 7 days, your task should call 
 TOUCH^XUSCLEAN once a day to notify Kernel.  This API sets
 ^XUTL("XQ",$J,"KEEPALIVE")=$H.  
  
 If Kernel sees this node, and $H is less than 7 days ago, Kernel will leave 
 your task alone, unless it determines that your task is really dead. If $H is 
 more than 7 days ago, Kernel will assume your task is dead.  
  
 There are no inputs or outputs.  
  
  DATE ACTIVATED: FEB 08, 2011

NUMBER: 10053                           IA #: 10053
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XUSERNEW
  NAME: XUSERNEW                        ORIGINAL NUMBER: 10053
  ID: XUSERNEW                          STATUS: Active
COMPONENT/ENTRY POINT: $$ADD
 COMPONENT DESCRIPTION:   Add New Person File Entry (in Sign-on/Security
 chapter) 

NUMBER: 10054                           IA #: 10054
  FILE NUMBER: 60                       GLOBAL ROOT: LAB(60,
  CUSTODIAL PACKAGE: LAB SERVICE        CUSTODIAL ISC: Dallas
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: LABORATORY TEST FILE
  ORIGINAL NUMBER: 10054                ID: LAB(60,
GLOBAL REFERENCE: LAB(60,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Active

NUMBER: 10055                           IA #: 10055
  FILE NUMBER: 61                       GLOBAL ROOT: LAB(61,
  CUSTODIAL PACKAGE: LAB SERVICE        CUSTODIAL ISC: Dallas
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: TOPOGRAPHY FIELD FILE
  ORIGINAL NUMBER: 10055                ID: LAB(61,
GLOBAL REFERENCE: LAB(61,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Active

NUMBER: 10056                           IA #: 10056
  FILE NUMBER: 5                        GLOBAL ROOT: DIC(5,
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: STATE FILE
  ORIGINAL NUMBER: 10056                ID: DIC(5,
GLOBAL REFERENCE: DIC(5,...
 GLOBAL DESCRIPTION:   The entire file is supported for 'READ' access only.  
  STATUS: Active

NUMBER: 10057                           IA #: 10057
  FILE NUMBER: 5.1                      GLOBAL ROOT: VIC(5.1,
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: COUNTY FILE                     ORIGINAL NUMBER: 10057
  ID: VIC(5.1,
GLOBAL REFERENCE: VIC(5.1,...
FIELD NUMBER: ALL                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Entire file is supported for "READ" access only.  
  STATUS: Active

NUMBER: 10058                           IA #: 10058
  FILE NUMBER: 5.11                     GLOBAL ROOT: VIC(5.11,
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: ZIP CODE FILE                   ORIGINAL NUMBER: 10058
  ID: VIC(5.11,
GLOBAL REFERENCE: VIC(5.11,...
 GLOBAL DESCRIPTION:   The entire file is supported for 'READ' access only.  
  STATUS: Active

NUMBER: 10059                           IA #: 10059
  FILE NUMBER: 6                        GLOBAL ROOT: DIC(6,
  DATE CREATED: JUN 10, 2003
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: File                            NAME: PROVIDER FILE
  ORIGINAL NUMBER: 10059                ID: DIC(6,
GLOBAL REFERENCE: DIC(6,...
FIELD NUMBER: ALL                       ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   All fields are presently supported for READ only.  DO NOT
 use for development, this file is soon to be retired.  
  
 The file may be referenced during conversion utilities to the New Person file. 
 
  STATUS: Retired

NUMBER: 10060                           IA #: 10060
  FILE NUMBER: 200                      GLOBAL ROOT: VA(200,
  DATE CREATED: NOV 09, 2020            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: NEW PERSON FILE                 ORIGINAL NUMBER: 10060
  ID: VA(200,
GLOBAL REFERENCE: Kernel Fields
 GLOBAL DESCRIPTION:   Kernel fields are all other fields not reserved by
 another package.  Read access w/FileMan can be used on the Kernel fields.  
  Top level .01 fields may not point to this file.  
GLOBAL REFERENCE: Fields from other Packages
 GLOBAL DESCRIPTION:   These fields are fully accessible to the creator
 package.  
 GENERAL DESCRIPTION:   Allows Read access to the NEW PERSON file (#200). 
 Access is only given to those fields by Kernel.  The following range of fields
 are owned by other packages and can only be accessed by that package: 
  
  Fields 12-12.9 for HL7             Nodes/X-ref 12 
  Fields 41.97-42 for NPI            Nodes/X-ref 'NPI*' 
  Fields 53-59.9 for Pharmacy        Nodes/X-ref 'PS*', 'TPB' 
  Fields 70-79.9 for Radiology       Nodes/X-ref 'RA*' 
  Fields 100-101.9 for Order Entry   Nodes/X-ref 'ORD*', 101 
  Fields 125-125.9 for Problem List  Nodes/X-ref 125 
  Fields 400-450.9 for IFCAP         Nodes/X-ref 400, 450 
  Fields 500-500.9 for Mailman       Nodes/X-ref 'XM*', 'AXM*', 500 
  Fields 654-654.9 for Social Work   Nodes/X-ref 'SW*', 654 
  Fields 720-725 for DSSM            Nodes/X-ref 'EC*', 'AEC*' 
  Fields 740-749.9 for QA            Nodes/X-ref 'QA*' 
  Fields 910-910.9.9 for Police      Nodes/X-ref 'ESP' 
  STATUS: Active
KEYWORDS: PERSON
KEYWORDS: NEW PERSON

NUMBER: 10061                           IA #: 10061
  DATE CREATED: MAR 07, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VADPT                        NAME: VADPT
  ORIGINAL NUMBER: 10061                ID: VADPT
 GENERAL DESCRIPTION:   VADPT is a utility routine designed to provide a
 central point where a programmer can obtain information concerning a patient's
 record.  Supported entry points are provided which will return demographics, 
 inpatient status, eligibility information, etc.  
  
 Access to patient information is not limited to using the supported entry 
 points in VADPT.  Integration agreements can be established through the DBA
 between REGISTRATION and other packages to reference information.  
  
 This integration agreement does not document the input and output variables
 for any of the components of VADPT except SVC. That documentation is located
 in the PIMS technical manual, section 12.2 CALLABLE ENTRY POINTS IN VADPT.  
  
 Revision History: 
  7/18/24: Added VASV(16) and VASV(17) variables to the SVC component, 
           effective with DG*5.3*1121. 
  3/26/24: Added "; otherwise a ^UNKNOWN is returned)" to the end of 
           VASV(15).  
  8/23/24: Effective with DG*5.3*1121, changed the variable help text for 
           the VAHOW Variable. Included additional examples of how the data 
           will be returned when VAHOW is set to 1.  
  STATUS: Active
COMPONENT/ENTRY POINT: DEM
 COMPONENT DESCRIPTION:   Basic patient demographic information along with
 VA("BID") and VA("PID") 
COMPONENT/ENTRY POINT: OPD
 COMPONENT DESCRIPTION:   Returns other demographics not returned in DEM call.  
COMPONENT/ENTRY POINT: ADD
 COMPONENT DESCRIPTION:   Patient Confidential Mailing, Temporary Mailing, and
 Residential Address Information. If there is no active Temporary Mailing, the
 Mailing Address is returned.  
COMPONENT/ENTRY POINT: ORD
 COMPONENT DESCRIPTION:   Other patient variables 
COMPONENT/ENTRY POINT: IN5
 COMPONENT DESCRIPTION:   More extensive information related to inpatient
 stays.  
COMPONENT/ENTRY POINT: ELIG
 COMPONENT DESCRIPTION:   Patient eligibility information 
COMPONENT/ENTRY POINT: MB
 COMPONENT DESCRIPTION:   Monetary benefits.  
COMPONENT/ENTRY POINT: SVC
 COMPONENT DESCRIPTION:   Returns Service-related information for a patient.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   This required variable is the internal entry number
 in the PATIENT (#2) file.  
VARIABLES: VAHOW                        TYPE: Input
 VARIABLES DESCRIPTION:   This optional variable can be set to a requested 
 format for the output array.  If this variable is not defined or is 0(zero)
 the output array is returned with numeric subscripts. If VAHOW is 1 the output 
 array is returned with alpha subscripts; see "Description o Returns the
 Comprehensive Prevention, Access to Care, and Treatment (COMPACT) indicator
 for enrolled Veterans and non-enrolled Veterans.  
  
 The optional input variable VAHOW can be set to return the data in alpha
 subscripts. The PERSIAN GULF INDICATOR is returned in the "PGI" subscript.  
 For example: VASV("PGI")="0^NO". The PERSIAN GULF LAST CHANGE DATE is returned
 in the "LCD" subscript. For example: VASV("LCD")="3230629^JUN 29,2023" 
VARIABLES: VASV                         TYPE: Output
 VARIABLES DESCRIPTION:   VASV(1)-If the VIETNAM SERVICE INDICATED field is
 YES, a "1" is returned; otherwise, a "0" is returned (e.g., 0).  
                                                      
 VASV(1,1)-If Vietnam Service, the VIETNAM FROM DATE in internal^external 
 format (e.g., 2680110^JAN 10,1968). 
                                                               
 VASV(1,2)-If Vietnam Service, the VIETNAM TO DATE in internal^external format
 (e.g., 2690315^MAR 15,1969). 
                                                                  
 VASV(2)-If the AGENT ORANGE EXPOS. INDICATED field is YES, a "1" is returned;
 otherwise, a "0" is returned (e.g., 0). 
                                                             
 VASV(2,1)-If Agent Orange exposure, the AGENT ORANGE REGISTRATION DATE in
 internal^external format (e.g., 2870513^MAY 13,1987).  
                                                                    
 VASV(2,2)-If Agent Orange exposure, the AGENT ORANGE EXAMINATION DATE in
 internal^external format (e.g., 2871101^NOV 1,1987). 
                                                      
 VASV(2,3)-If Agent Orange exposure, AGENT ORANGE REPORTED TO C.O. date in
 internal^external format (e.g., 2871225^DEC 25,1987).  
                                                         
 VASV(2,4)-If Agent Orange exposure, AGENT ORANGE REGISTRATION # (e.g.,
 123456). 
                                                      
 VASV(2,5)-If Agent Orange exposure, the AGENT ORANGE EXPOSURE LOCATION in
 internal^external format (e.g., V^VIETNAM).  
                                                      
 VASV(3)-If the RADIATION EXPOSURE INDICATED field is YES, a "1" is returned;
 otherwise, a "0" is returned (e.g., 0). 
                                                          
 VASV(3,1)-If Radiation Exposure, RADIATION REGISTRATION DATE in 
 internal^external format (e.g., 2800202^FEB 02,1980). 
                                             
 VASV(3,2)-If Radiation Exposure, RADIATION EXPOSURE METHOD in 
 internal^external format (e.g., T^NUCLEAR TESTING).  
                                                     
 VASV(4)-If the POW STATUS INDICATED field is YES, a "1" is returned; 
 otherwise, a "0" is returned (e.g., 0). 
                                          
 VASV(4,1)-If POW status, POW FROM DATE in internal^external format (e.g.,
 2450319^MAR 19,1945). 
                                                            
 VASV(4,2)-If POW status, POW TO DATE in internal^external format (e.g.,
 2470101^JAN 1,1947). 
                                                      
 VASV(4,3)-If POW status, POW CONFINEMENT LOCATION in internal^external format
 (e.g., 2^WORLD WAR II - EUROPE).                      
                                               
 VASV(5)-If the COMBAT SERVICE INDICATED field is YES, a "1" is returned;
 otherwise, a "0" is returned (e.g., 0).  
                                                       
 VASV(5,1)-If combat service, COMBAT FROM DATE in internal^external format
 (e.g., 2430101^JAN 1,1943).  
                                                          
 VASV(5,2)-If combat service, COMBAT TO DATE in internal^external format (e.g.,
 2470101^JAN 1,1947). 
                                                        
 VASV(5,3)-If combat service, COMBAT SERVICE LOCATION in internal^external
 format (e.g., 2^WORLD WAR II - EUROPE).  
                                                
 VASV(6)-If a SERVICE BRANCH [LAST] field is indicated, a "1" is returned in
 the first piece; otherwise, a "0" is returned (e.g., 0).  
                                                       
 VASV(6,1)-If service branch, BRANCH OF SERVICE field in internal^external
 format (e.g., 3^AIR FORCE). 
                                                     
 VASV(6,2)-If service branch, SERVICE NUMBER field in internal^external format
 (e.g., 123456789). 
                                                      
 VASV(6,3)-If service branch, SERVICE DISCHARGE TYPE in internal^external
 format (e.g., 1^HONORABLE). 
                                              
 VASV(6,4)-If service branch, SERVICE ENTRY DATE in internal^external format
 (e.g., 2440609^JUN 9,1944). 
                                                
 VASV(6,5)-If service branch, SERVICE SEPARATION DATE in internal^external
 format (e.g., 2480101^JAN 1,1948).  
                                               
 VASV(6,6)-If service branch, SERVICE COMPONENT in internal code^external
 format (e.g., R^REGULAR). 
                                             
 VASV(7)-If a SERVICE SECOND EPISODE field is indicated, a "1" is returned;
 otherwise, a "0" is returned (e.g., 0).  
                                                    
 VASV(7,1)-If second episode, BRANCH OF SERVICE field in internal^external
 format (e.g., 3^AIR FORCE). 
                                              
 VASV(7,2)-If second episode, SERVICE NUMBER field in internal^external format
 (e.g., 123456789). 
                                                         
 VASV(7,3)-If second episode, SERVICE DISCHARGE TYPE in internal^external
 format (e.g., 1^HONORABLE). 
                                             
 VASV(7,4)-If second episode, SERVICE ENTRY DATE in internal^external format
 (e.g., 2440609^JUN 9,1944). 
                                         
 VASV(7,5)-If second episode, SERVICE SEPARATION DATE in internal^external
 format (e.g., 2480101^JAN 1,1948).  
                                       
 VASV(7,6)-If second episode, SERVICE COMPONENT in internal^external format
 (e.g., R^REGULAR). 
                                            
 VASV(8)-If a SERVICE THIRD EPISODE field is indicated, a "1" is returned;
 otherwise, a "0" is returned (e.g., 0).  
                                             
 VASV(8,1)-If third episode, BRANCH OF SERVICE field in internal^external
 format (e.g., 3^AIR FORCE).  
                                        
 VASV(8,2)-If third episode, SERVICE NUMBER field in internal^external format
 (e.g., 123456789). 
                                                  
 VASV(8,3)-If third episode, SERVICE DIS-CHARGE TYPE in internal^external
 format (e.g., 1^HONORABLE). 
                                               
 VASV(8,4)-If third episode, SERVICE ENTRY DATE in internal^external format
 (e.g., 2440609^JUN 9,1944). 
                                         
 VASV(8,5)-If third episode, SERVICE SEPARATION DATE in internal^external
 format (e.g., 2480101^JAN 1,1948).  
                                    
 VASV(8,6)-If third episode, SERVICE COMPONENT in internal code^external 
 format.(e.g., R^REGULAR). 
                                          
 VASV(9)-If the CURRENT PH INDICATOR field is YES, a "1" is returned; 
 otherwise, a "0" is returned (e.g., 0). 
                                           
 VASV(9,1)-If the CURRENT PH INDICATOR field is YES, CURRENT PURPLE HEART
 STATUS in internal^external format.(e.g., 2^IN PROCESS).  
                                                
 VASV(9,2)-If the CURRENT PH INDICATOR field is NO, CURRENT PURPLE HEART
 REMARKS in internal^external format (e.g., 5^VAMC).  
                                                          
 VASV(10)-Is either 1 or 0, 1 if there is a value for Combat Vet End Date, 0 if
 not. 
                                                  
 VASV(10,1)-Internal Combat Vet End Date ^external Combat Vet End Date (e.g.,
 3060101^JAN 1, 2006). 
                                                      
 VASV(11)-The number of OIF conflict entries found for the Veteran in the
 SERVICE [OEF OR OIF] (#2.3215) SUB-FILE [n = 1-Total number of OIF conflict
 entries]. 
                                                     
 VASV(11,n,1)-SERVICE LOCATION (#2.3215; .01) internal code=1^external (e.g.,
 1^OIF). Where "n" is the number used to provide a unique number for each OIF
 or a conflict being returned. 
                                                   
 VASV(11,n,2)-OEF/OIF FROM DATE (#2.3215; .02) internal format ^external format
 (e.g., 3060101^JAN 1, 2006). Where "n" is the number used to provide a unique
 number for each OIF conflict being returned.  
                                                               
 VASV(11,n,3)-OEF/OIF TO DATE (#2.3215; .03) internal format ^external format
 (e.g., 3060101^MAR 1, 2006). Where "n" is the number used to provide a unique
 number for each OIF conflict being returned.  
  
 VASV(12)-The number of OEF conflict entries found for the Veteran in the
 SERVICE [OEF OR OIF] #2.3215 SUB-FILE. [n = 1-VASV(12)]. 
                                                   
 VASV(12,n,1)-SERVICE LOCATION (#2.3215; .01) internal code = 2 ^external
 (e.g., 2^OEF). Where "n" is the number used to provide a unique number for
 each OEF conflict being returned. 
                                           
 VASV(12,n,2)-OEF/OIF FROM DATE (#2.3215; .02) internal format ^external format
 (e.g., 3060101^JAN 1, 2006). Where "n" is the number used to provide a unique
 number for each OEF conflict being returned.  
                                                
 VASV(12,n,3)-OEF/OIF TO DATE (#2.3215; .03) internal format ^external format
 (e.g., 3060101^MAR 1, 2006). Where "n" is the number used to provide a unique
 number for each OEF conflict being returned.  
                                          
 VASV(13)-The number of UNKNOWN OEF/OIF conflict entries found for the Veteran
 in the SEVICE [OEF OR OIF] #2.3215 SUB-FILE. [n = 1-VASV(13)].  
                                                      
 VASV(13,n,1)-SERVICE LOCATION (#2.3215; .01) internal CODE = 3^external format
 (e.g., 3^UNKNOWN OEF/OIF). Where "n" is the number used to provide a unique
 number for each UNKNOWN OEF/OIF conflict being returned.  
                                                 
 VASV(13,n,2)-OEF/OIF FROM DATE (#2.3215; .02) internal format ^external format
 (e.g., 3060101^JAN 1, 2006). Where "n" is the number used to provide a unique
 number for each UNKNOWN OEF/OIF conflict being returned.  
                                                  
 VASV(13,n,3)-OEF/OIF TO DATE (#2.3215; .03) internal format ^external format
 (e.g., 3060101^MAR 1, 2006). Where "n" is the number used to provide a unique
 number for each UNKNOWN OEF/OIF conflict being returned.  
                                                    
 VASV(14)-If the PROJ 112/ SHAD field is populated, a "1" is returned; 
 otherwise, a "0" is returned (e.g., 0). 
                                                          
 VASV(14,1)-If the PROJ 112/SHAD field is populated, PROJ 112/SHAD in 
 internal^external format (e.g., 1^YES). 
                                                
 VASV(15)-If the TOXIC EXPOSURE RISK ACTIVITY (TERA) field is populated, TERA
 will be returned in internal^external format (e.g.,1^YES is returned for YES;
 otherwise, a 0^NO is returned for NO; otherwise a ^UNKNOWN is returned).  
  
 VASV(16)-If the PERSIAN GULF INDICATOR (#.32117) field is populated, the 
 stored value will be returned in internal^external format (e.g.,1^YES is 
 returned for YES; a 0^NO is returned for NO; otherwise ^UNKNOWN is returned
 for UNKNOWN).  
  
 VASV(17)-PERSIAN GULF LAST CHANGE DATE (#.32118) field - the date of the last
 change made to the PERSIAN GULF INDICATOR will be returned in 
 internal^external format (e.g.,3230629^JUN 29,2023).  
VARIABLES: VAERR                        TYPE: Output
 VARIABLES DESCRIPTION:   VAERR-The error flag has one of the following values: 
 o 0-No errors encountered. o 1-Error encountered: DFN or ^DPT(DFN,0) is not
 defined.  
COMPONENT/ENTRY POINT: REG
 COMPONENT DESCRIPTION:   Patient registration/disposition information 
COMPONENT/ENTRY POINT: SDE
 COMPONENT DESCRIPTION:   Active clinic enrollment data 
COMPONENT/ENTRY POINT: SDA
 COMPONENT DESCRIPTION:   Returns appointment information for a patient.  
COMPONENT/ENTRY POINT: OERR
 COMPONENT DESCRIPTION:   Will return the demographic and inpatient [INP]
 arrays.  Same as DEM and INP.  
COMPONENT/ENTRY POINT: 1
 COMPONENT DESCRIPTION:   Will return the demographic and inpatient [INP]
 arrays.  Same as DEM and INP.  
COMPONENT/ENTRY POINT: 2
 COMPONENT DESCRIPTION:   Will return the demographic and eligibility arrays.  
 Same as DEM and ELIG.  
COMPONENT/ENTRY POINT: 3
 COMPONENT DESCRIPTION:   Will return the eligibility and inpatient [INP]
 arrays.  Same as ELIG and INP.  
COMPONENT/ENTRY POINT: 4
 COMPONENT DESCRIPTION:   Will return the demographic and address arrays.  Same
 as DEM and ADD.  
COMPONENT/ENTRY POINT: 5
 COMPONENT DESCRIPTION:   Will return the address and inpatient [INP] arrays.  
 Same as INP and ADD.  
COMPONENT/ENTRY POINT: 6
 COMPONENT DESCRIPTION:   Will return the demographic, eligibility and address
 arrays.  Same as DEM, ELIG, and ADD.  
COMPONENT/ENTRY POINT: 7
 COMPONENT DESCRIPTION:   Will return the eligibility and service arrays.  Same
 as ELIG and SVC.  
COMPONENT/ENTRY POINT: 8
 COMPONENT DESCRIPTION:   Will return the eligibility, service and monetary
 arrays.  Same as ELIG, SVC, and MB.  
COMPONENT/ENTRY POINT: 9
 COMPONENT DESCRIPTION:   Will return the demographic, registration, clinic
 enrollment and appointment arrays.  Same as DEM, REG, SDE, and SDA.  
COMPONENT/ENTRY POINT: 10
 COMPONENT DESCRIPTION:   Will return the enrollment and appointment arrays.  
 Same as SDE and SDA.  
COMPONENT/ENTRY POINT: 51
 COMPONENT DESCRIPTION:   Will return the demographic and inpatient [IN5]
 arrays with version 5.0 of MAS.  Same as DEM and IN5.  
COMPONENT/ENTRY POINT: 52
 COMPONENT DESCRIPTION:   Will return the eligibility and inpatient [IN5]
 arrays with version 5.0 of MAS.  Same as ELIG and IN5.  
COMPONENT/ENTRY POINT: 53
 COMPONENT DESCRIPTION:   Will return the address and inpatient [IN5] arrays
 with version 5.0 of MAS.  Same as IN5 and ADD.  
COMPONENT/ENTRY POINT: ALL
 COMPONENT DESCRIPTION:   Will return all arrays supported by this routine. 
 Tag INP will be used to determine inpatient array.  All calls EXCEPT IN5.  
COMPONENT/ENTRY POINT: A5
 COMPONENT DESCRIPTION:   Will return all arrays supported by this routine
 after version 5.0 of the MAS module is up and running.  IN5 will be used to
 determine the inpatient array.  All calls EXCEPT INP.  
COMPONENT/ENTRY POINT: SEL
 COMPONENT DESCRIPTION:   Caller specifies a list of components to execute.  
COMPONENT/ENTRY POINT: INP
 COMPONENT DESCRIPTION:   Inpatient-related information.  
COMPONENT/ENTRY POINT: OAD
 COMPONENT DESCRIPTION:   Address information for next-of-kin, emergency
 contacts, designee, employer, or spouse's employer.  
COMPONENT/ENTRY POINT: PID
 COMPONENT DESCRIPTION:   Returns VA("BID") and VA("PID") variables.  
COMPONENT/ENTRY POINT: KVAR
 COMPONENT DESCRIPTION:   Used to clean-up variables used by VADPT utilities.  
COMPONENT/ENTRY POINT: KVA
 COMPONENT DESCRIPTION:   Same as KVAR^VADPT, but also kills the VA variable
 (and its subcomponents VA("BID") and VA("PID")).  
  
COMPONENT/ENTRY POINT: CAI
 COMPONENT DESCRIPTION:   Will return the Comprehensive Prevention, Access to
 Care, and Treatment (COMPACT) indicator for enrolled Veterans and non-enrolled
 Veterans.  
     
 Indicator is '1' (for TRUE) if: 
   - Enrollment Category from current enrollment record is "ENROLLED".  
     OR 
   - The patient has the "COMPACT ACT ELIGIBLE" eligibility code.  
VARIABLES: VAHOW                        TYPE: Input
  DATE ACTIVATED: AUG 26, 2024

NUMBER: 10062                           IA #: 10062
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VADPT6                       NAME: VADPT6
  ORIGINAL NUMBER: 10062                ID: VADPT6
  STATUS: Active
COMPONENT/ENTRY POINT: PID
 COMPONENT DESCRIPTION:   Returns VA("BID") and VA("PID").  

NUMBER: 10063                           IA #: 10063
  DATE CREATED: APR 20, 1998            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: %ZTLOAD                      NAME: %ZTLOAD
  ORIGINAL NUMBER: 10063                ID: %ZTLOAD
 GENERAL DESCRIPTION:   This routine provides several API's into a task.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
KEYWORDS: TASKMAN
COMPONENT/ENTRY POINT: %ZTLOAD
 COMPONENT DESCRIPTION:   Create & Schedule a task 
COMPONENT/ENTRY POINT: REQ
 COMPONENT DESCRIPTION:   Requeue a Task (in Task Manager chapter) 
COMPONENT/ENTRY POINT: KILL
 COMPONENT DESCRIPTION:   Delete a Task (in Task Manager chapter) 
COMPONENT/ENTRY POINT: ISQED
 COMPONENT DESCRIPTION:   Task Queue Status (in Task Manager chapter) 
COMPONENT/ENTRY POINT: DQ
 COMPONENT DESCRIPTION:   Unschedule a Task (in Task Manager chapter) 
COMPONENT/ENTRY POINT: $$S(msg)
 COMPONENT DESCRIPTION:   Check for Task Stop Request (in Task Manager chapter) 
VARIABLES: msg                          TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Allows you to leave a message for the
 creator of the TaskMan task.  
VARIABLES: $$S                          TYPE: Output
 VARIABLES DESCRIPTION:   Returns: 
  
     * 1-Creator of the task that has asked the task to stop.  
  
     * 0-For all other cases.  
COMPONENT/ENTRY POINT: STAT
 COMPONENT DESCRIPTION:   Task Status (in Task Manager chapter) 
VARIABLES: ZTSK                         TYPE: Both
 VARIABLES DESCRIPTION:   (required) The task number to look up. It must be
 defined on the current volume set.  ZTSK(0) Returns: 
     * 1-Task is defined.  
  
     * 0-Task is not defined.  
  
 ZTSK(1): Numeric status code from 0 to 5 indicating the status of the task.  
  
 ZTSK(2): Status text describing the status of the task. Its value corresponds
 with the status code in ZTSK(1). The possible values and their meanings are as
 follows: 
  
     * ZTSK(1) = 0 and ZTSK(2) = "Undefined" means the task does not exist on
 this volume set.  
  
     * ZTSK(1) = 1 and ZTSK(2) = "Active: Pending" means the task is scheduled,
 waiting for an I/O device, waiting for a volume set link, or waiting for a
 partition in memory.  
  
     * ZTSK(1) = 2 and ZTSK(2) = "Active: Running" means the task has started
 running.  
  
     * ZTSK(1) = 3 and ZTSK(2) = "Inactive: Finished" means the task quit 
 normally after running.  
  
     * ZTSK(1) = 4 and ZTSK(2) = "Inactive: Available" means the task was 
 created without being scheduled or was edited without being rescheduled.  
  
     * ZTSK(1) = 5 and ZTSK(2) = "Inactive: Interrupted" means the task was
 interrupted before it would have quit normally. Causes can include bad data,
 user intervention, hard error, and many other possibilities.  
COMPONENT/ENTRY POINT: $$TM
 COMPONENT DESCRIPTION:   Check if TaskMan is Running.  Usage: S X=$$TM^%ZTLOAD 
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   If TaskMan is running on the current volume set, 1 is
 returned; otherwise 0 is returned.  
COMPONENT/ENTRY POINT: $$PSET(ztsk)
 COMPONENT DESCRIPTION:   Sets a task as persistent.  A task that is marked as
 persistent will be restarted if the Taskmaster finds that the lock on 
 ^%ZTSCH("TASK",tasknumber) has been removed.  This adds the requirement that
 the task only use incremental locks, that the entry in ^%ZTSK(task...  be left
 in place as this will be used to restart the task, and that the task can be
 restarted from the data that is in the ^%ZTSK(task,... global.  
  
 Returns 1 if the flag was set, otherwise returns 0.  
VARIABLES: ZTSK                         TYPE: Input
 VARIABLES DESCRIPTION:   The task number.  
VARIABLES: &
COMPONENT/ENTRY POINT: PCLEAR(ztsk)
 COMPONENT DESCRIPTION:   Clears the persistent flag for a task 
VARIABLES: ztsk                         TYPE: Input
 VARIABLES DESCRIPTION:   (required) The TaskMan task number.  
COMPONENT/ENTRY POINT: $$JOB(ztsk)
 COMPONENT DESCRIPTION:   This extrinsic function returns the job number for a
 running TaskMan task.  
  
 Format: $$JOB^%ZTLOAD(ztsk) 
VARIABLES: ztsk                         TYPE: Input
 VARIABLES DESCRIPTION:   Task Number 
VARIABLES: $$JOB                        TYPE: Output
 VARIABLES DESCRIPTION:   Returns the job number for the specified running
 TaskMan task.  If the specified task is not running, it returns null.  
COMPONENT/ENTRY POINT: DESC
 COMPONENT DESCRIPTION:   This API finds tasks with a specific description.  
VARIABLES: description                  TYPE: Input
 VARIABLES DESCRIPTION:   (required) The TaskMan task description.  
VARIABLES: list                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns a list of task(s) with the specified
 description.  
COMPONENT/ENTRY POINT: $$ASKSTOP(ztsk)
 COMPONENT DESCRIPTION:   This extrinsic function asks TaskMan to stop running
 a specified task. Also, it checks for the ZTNAME variable, and if defined, it
 uses it instead of DUZ to value the STOP FLAG field (#59.1). ZTNAME is
 supported by applications calling this API to indicate the process that asked
 the task to stop.  
VARIABLES: output                       TYPE: Output
 VARIABLES DESCRIPTION:   Returns: 
  
     * 0-"Busy". If it returns "Busy" it could mean that the task is locked,
 someone else is changing it, or TaskMan is starting to run it.  
  
     * 1-"Task missing" or Task "Finished running". If it returns "Task 
 missing" it could mean that it was an incorrect input task number, but it is
 most likely that the task ran and was removed after running.  
  
       If it returns "Finished running" it means that the task was finished
 running before the API request could go through, so the API could not stop an
 already finished task.  
  
     * 2-"Asked to stop" or "Unscheduled". If it returns "Asked to Stop" the
 task has started running and the stop flag has been set, so if the application
 checks ($$S^%ZTLOAD) it should stop.  
  
       If it returns "Unscheduled" it was successful and the task is not 
 scheduled any more.  
COMPONENT/ENTRY POINT: OPTION(option,list)
 COMPONENT DESCRIPTION:   This API finds TaskMan tasks for a specific option.  
VARIABLES: option                       TYPE: Input
 VARIABLES DESCRIPTION:   (required) The name of the specific option.  
VARIABLES: list                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns a list of TaskMan task(s) for the specified
 option.  
COMPONENT/ENTRY POINT: RTN(routine,list)
 COMPONENT DESCRIPTION:   This API finds TaskMan tasks that call a specific
 routine.  
VARIABLES: routine                      TYPE: Input
 VARIABLES DESCRIPTION:   (required) The name of the specific routine called.  
VARIABLES: list                         TYPE: Output
 VARIABLES DESCRIPTION:   Returns a list of TaskMan task(s) that call the
 specified routine.  
COMPONENT/ENTRY POINT: ZTSAVE(strvar,kill)
 COMPONENT DESCRIPTION:   This API stores a string of variables in the ZTSAVE
 array.  
VARIABLES: strvar                       TYPE: Input
 VARIABLES DESCRIPTION:   (required) Sting of variable names to be stored in
 the ZTSAVE array.  
VARIABLES: kill                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) Any positive value will first KILL the
 ZTSAVE array.  
VARIABLES: ZTSAVE                       TYPE: Output
 VARIABLES DESCRIPTION:   Stores the string of input variables in the ZTSAVE
 array.  
  DATE ACTIVATED: JUL 08, 2009

NUMBER: 10064                           IA #: 10064
  DATE CREATED: JAN 31, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XM                           NAME: PROGRAMMER API
  ORIGINAL NUMBER: 10064                ID: XM
 GENERAL DESCRIPTION:   ^XM contains these programmer entry points: 
     
 ^XM is the normal routine programmers invoke to use MailMan directly.  No menu
 item leads to ^XM.  KILL^XUSCLEAN is invoked so only basic Kernel parameters
 survive call.  
  
 EN^XM is the entry action for the top-level interactive MailMan option.  It
 invokes INIT^XMVVITAE to set up the user's MailMan environment.  It invokes
 HEADER^XM to greet the user and inform the user of new messages.  It is
 normally used only in top-level options; other types of uses should invoke the
 individual entry points directly.  
  
 CHECKIN^XM is the entry action for subordinate interactive MailMan options.  
  
 CHECKOUT^XM is the exit action for all interactive MailMan options.  
  
 HEADER^XM greets the user and informs of new messages.  
  
 KILL^XM kills MailMan variables.  
  
 $$NU^XM Returns the number of new messages a user has and may display the
 message: "You have # new messages." 
  
 N1^XM and NEW^XM create a mailbox for a user.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   EN^XM is the entry action for the top-level
 interactive MailMan option.  It invokes INIT^XMVVITAE to set up the user's
 MailMan environment.  It invokes HEADER^XM to greet the user and inform the
 user of new messages.  It is normally used only in top-level options; other
 types of uses should invoke the individual entry points directly.  
  
 Options at other than the top level should not use EN^XM as an entry action. 
 Instead, they should use CHECKIN^XM.  
  
 An example of how EN^XM is used in a top-level option's ENTRY ACTION follows: 
  
 NAME: XMUSER                            MENU TEXT: MailMan Menu 
   TYPE: menu                            CREATOR: BEUSCHEL,GARY 
   HELP FRAME: XMHELP                    PACKAGE: MAILMAN 
   E ACTION PRESENT: YES                 X ACTION PRESENT: YES 
  DESCRIPTION:   This is the main MailMan option menu for normal user 
 interaction.  It allows the user to Send and Receive messages, as well as 
 manage baskets.  
  ITEM: XMNEW                             SYNONYM: NML 
   DISPLAY ORDER: 1 
  ITEM: XMREAD                            SYNONYM: RML 
   DISPLAY ORDER: 2 
  ITEM: XMSEND                            SYNONYM: SML 
   DISPLAY ORDER: 3 
  ITEM: XMSEARCH                          DISPLAY ORDER: 4 
  ITEM: XMASSUME                          DISPLAY ORDER: 5 
  ITEM: XM PERSONAL MENU                  DISPLAY ORDER: 6 
  ITEM: XMOTHER                           DISPLAY ORDER: 7 
  ITEM: XMHELP                            DISPLAY ORDER: 8 
   EXIT ACTION: K XMMENU D CHECKOUT^XM 
   ENTRY ACTION: S XMMENU(0)="XMUSER" D EN^XM 
  
 Notice that XMMENU(0) is set in the entry action.  It doesn't have to be set
 to "XMUSER".  It can be any string.  It is suggested that is be the option
 name.  Setting this variable causes MailMan to check to see if the user
 already has another MailMan session in progress.  If so, the user will be
 notified that s/he won't be able to send mail in any but the primary session. 
 The reason for this is that when a user is creating a message, the message ID
 (XMZ) is stored in the user's mailbox record.  If the user's session aborts
 for some reason, when the user logs on again, MailMan informs the user of the
 unsent message and asks if s/he wishes to continue with it.  There is only one
 field to store the message ID, and that is why only one session may send
 messages.  
COMPONENT/ENTRY POINT: KILL
 COMPONENT DESCRIPTION:   Kill all Mailman variables.  
  
 Usage: D KILL^XM 
COMPONENT/ENTRY POINT: $$NU
 COMPONENT DESCRIPTION:   Returns the number of new messages a user has, and
 may display the message: "You have # new messages." 
  
 Compare to: 
  QMBOX^XMXAPIB, QBSKT^XMXAPIB (DBIA 2723) 
  $$BNMSGCT^XMXUTIL, $$TNMSGCT^XMXUTIL, $$NEWS^XMXUTIL (DBIA 2734) 
  
 Usage: S X=$$NU^XM(FORCE) 
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The user's DUZ.  
VARIABLES: XMDUZ                        TYPE: Used
 VARIABLES DESCRIPTION:   (optional) The user whose mailbox is to be checked. 
 Default is DUZ.  
VARIABLES: FORCE                        TYPE: Input
 VARIABLES DESCRIPTION:   Should the message, "You have <x> new messages." be
 displayed? 
  
 Possible values: 
  
 0 - Display the message only if the user has received new messages since the
 last time the message was displayed.  
  
 1 - Display the message.  
COMPONENT/ENTRY POINT: N1
 COMPONENT DESCRIPTION:   Create a mailbox for a user.  
  
 Compare to: 
  NEW^XM 
  CRE8MBOX^XMXAPIB (DBIA 2723) 
  
 Usage: S XMDUZ=<user's DUZ> D N1^XM 
VARIABLES: XMDUZ                        TYPE: Input
 VARIABLES DESCRIPTION:   The DUZ of the user for whom the mailbox should be
 created.  
VARIABLES: XMZ                          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 variable has
 no effect and shouldn't be used.  
  
 Possible values: 
  
 If '$D(XMZ), then the user may access any message on the system which was ever
 addressed to the user.  
  
 If $D(XMZ), then the user will not be able to access any message addressed to
 the user on the system earlier than today's date, unless it is already in the
 user's mailbox or if someone forwards it to the user.  
COMPONENT/ENTRY POINT: NEW
 COMPONENT DESCRIPTION:   Create a mailbox for a user.  
  
 Compare to: 
  N1^XM 
  CRE8MBOX^XMXAPIB (DBIA 2723) 
  
 Usage: S Y=<user's DUZ> D NEW^XM 
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   The DUZ of the user for whom the mailbox is to be
 created.  
VARIABLES: XMZ                          TYPE: Used
 VARIABLES DESCRIPTION:   See the description for XMZ in entry N1.  
COMPONENT/ENTRY POINT: HEADER
 COMPONENT DESCRIPTION:   Meant to be part of the ENTRY action of the primary
 MailMan option, whether called by itself, or as part of another call, such as
 EN^XM.  
  
 Display user information and greeting upon entry into MailMan.  
COMPONENT/ENTRY POINT: CHECKIN
 COMPONENT DESCRIPTION:   Meant to be part of any subordinate MailMan option's
 ENTRY action.  
  
 Example: 
  
 NAME: XMSEND                            MENU TEXT: Send a Message 
   TYPE: run routine                     CREATOR: BEUSCHEL,GARY 
   HELP FRAME: XM-U-M-SEND               PACKAGE: MAILMAN 
   E ACTION PRESENT: YES                 X ACTION PRESENT: YES 
  DESCRIPTION:   Enables the user to send MailMan messages.  Messages may be 
 sent to other users or groups of users.  The sender of the message may request
 a confirmation message, to be sent to him as each recipient reads the message. 
   EXIT ACTION: D CHECKOUT^XM            ENTRY ACTION: D CHECKIN^XM 
   ROUTINE: SEND^XMJMS                   TIMESTAMP: 53272,53151 
   UPPERCASE MENU TEXT: SEND A MESSAGE 
COMPONENT/ENTRY POINT: CHECKOUT
 COMPONENT DESCRIPTION:   Meant to be part of every MailMan option's EXIT
 action.  
  
 Example: 
  
 NAME: XMSEND                            MENU TEXT: Send a Message 
   TYPE: run routine                     CREATOR: BEUSCHEL,GARY 
   HELP FRAME: XM-U-M-SEND               PACKAGE: MAILMAN 
   E ACTION PRESENT: YES                 X ACTION PRESENT: YES 
  DESCRIPTION:   Enables the user to send MailMan messages.  Messages may be 
 sent to other users or groups of users.  The sender of the message may request
 a confirmation message, to be sent to him as each recipient reads the message. 
   EXIT ACTION: D CHECKOUT^XM            ENTRY ACTION: D CHECKIN^XM 
   ROUTINE: SEND^XMJMS                   TIMESTAMP: 53272,53151 
   UPPERCASE MENU TEXT: SEND A MESSAGE 

NUMBER: 10065                           IA #: 10065
  DATE CREATED: JAN 31, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XMA1B                        NAME: DELETE/SAVE MESSAGE API
  ORIGINAL NUMBER: 10065                ID: XMA1B
 GENERAL DESCRIPTION:   These APIs let you delete a message from a basket
 and/or save it to a basket: 
  - KL^XMA1B   delete a message from a basket (presumes S2 used later) 
  - KLQ^XMA1B  delete a message from a basket and put it in .5=WASTE 
  - S2^XMA1B   save a message to a basket 
  STATUS: Active
COMPONENT/ENTRY POINT: KLQ
 COMPONENT DESCRIPTION:   Delete a message from a basket and put it in the
 WASTE basket.  If the basket we're deleting from is the WASTE basket, just
 delete it.  
   
 This call uses KL^XMA1B to delete the message.  See its writeup in this DBIA
 for more information.  
  
 Compare to DELMSG^XMXAPI (DBIA 2729).  
  
 Usage: S XMDUZ=user's DUZ 
        S XMK=basket IEN 
        S XMZ=message IEN 
        D KLQ^XMA1B 
VARIABLES: XMDUZ                        TYPE: Input
 VARIABLES DESCRIPTION:   The DUZ of the user from whose basket the message is
 to be deleted.  
VARIABLES: XMK                          TYPE: Used
 VARIABLES DESCRIPTION:   (optional) IEN of the basket from which the message
 is to be deleted.  See the writeup for XMK in entry KL^XMA1B in this DBIA for
 more information.  
VARIABLES: XMZ                          TYPE: Input
 VARIABLES DESCRIPTION:   Message IEN in the Message file of the message to be
 deleted.  
COMPONENT/ENTRY POINT: S2
 COMPONENT DESCRIPTION:   Save a message into a basket.  If the message is
 currently in a different basket, you should first delete it from that basket
 (using KL^XMA1B), otherwise you'll end up with the same message in more than
 one basket.  
  
 Compare to MOVEMSG^XMXAPI (DBIA 2729).  
  
 XMKM is killed upon exit.  
   
 Usage: S XMDUZ=user's DUZ 
        S XMKM=basket IEN to save to 
        S XMZ=message IEN 
        D S2^XMA1B 
VARIABLES: XMDUZ                        TYPE: Input
 VARIABLES DESCRIPTION:   DUZ of the user into whose basket the message is to
 be saved.  
VARIABLES: XMKM                         TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the user's basket into which the message is to
 be saved.  
VARIABLES: XMZ                          TYPE: Input
 VARIABLES DESCRIPTION:   Message IEN in the Message file of the message to be
 saved.  
COMPONENT/ENTRY POINT: KL
 COMPONENT DESCRIPTION:   Delete a message from a basket.  The message is not
 put in the WASTE basket.  
  
 If the message is in the specified basket, delete it from there.  
  
 Otherwise, delete the message from the first mail basket in which found.  
  
 If the message is not found in any basket, quit.  
  
 Usage: S XMDUZ=user's DUZ 
        S XMK=basket IEN 
        S XMZ=message IEN 
        D KL^XMA1B 
VARIABLES: XMDUZ                        TYPE: Input
 VARIABLES DESCRIPTION:   DUZ of the user from whose basket the message is to
 be deleted.  
VARIABLES: XMK                          TYPE: Used
 VARIABLES DESCRIPTION:   (optional) IEN of the basket in the user's mailbox
 from which the message is to be deleted.  
  
 If XMK is not supplied, MailMan finds out which basket the message is in.  
  
 If XMK is supplied, MailMan checks to make sure that the message is in that
 basket, and, if not, finds out which basket the message is in.  
VARIABLES: XMZ                          TYPE: Input
 VARIABLES DESCRIPTION:   Message IEN in the Message file of the message to be
 deleted.  

NUMBER: 10066                           IA #: 10066
  DATE CREATED: NOV 02, 1994            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XMA2                         NAME: CREATE A MESSAGE STUB API
  ORIGINAL NUMBER: 10066                ID: XMA2
 GENERAL DESCRIPTION:   The API in this routine is the first step in sending a
 message, when the message text will be loaded directly into the mail global by
 the calling application (rather than being copied from a temporary "build
 site" as with ^XMD). 
  
 This first step is to create a message stub, which is an entry in the Message
 file (3.9), with no text or recipients. 
  
 The next step is to add the text into the text field of the message (DBIA 
 10113). 
  
 Optionally, the next step is to set any special handling fields: 
  S DIE=3.9,DA=XMZ,DR="<field #>////<value>" D ^DIE 
  
  Field #   Value   Causes message to be 
  -------   -----   --------------------
  1.7         P       Priority 
  1.95        y       Closed 
  1.96        y       Confidential 
  1.97        y       Information only 
  
 Example:  To force message 100213 to be priority and closed: 
  S DIE=3.9,DA=100213,DR="1.7////P;1.95////y" D ^DIE 
  
 The final step is to address and send the message, using ENT1^XMD or ENT2^XMD
 (DBIA 10070). 
  STATUS: Active
COMPONENT/ENTRY POINT: GET
 COMPONENT DESCRIPTION:   This entry point should not be used.  Use XMZ^XMA2,
 instead.  
  
 GET^XMA2 functions exactly like XMZ^XMA2, except for one thing.  If it fails,
 it causes the application to halt.  
COMPONENT/ENTRY POINT: XMZ
 COMPONENT DESCRIPTION:   Create a new message stub in the Message file 3.9.  
  
 The SUBJECT field (.01) will be set to XMSUB.  The FROM field (1) will be set
 to XMDUZ. The SENT DATE/TIME field (1.4) will be set to the current date/time,
 in internal FileMan format.  If XMDUZ is a number, and it differs from DUZ,
 then the SENDER field (1.1) will be set to DUZ.  If XMDUZ=.5 and DUZ'=.5, the
 INFORMATION ONLY? field (1.97) will be set to 'y', thus making the stub
 'information only'.  
  
 Compare to CRE8XMZ^XMXAPI (DBIA 2729).  
  
 Usage: D XMZ^XMA2 I XMZ=-1 D error routine 
  
 Note that it is important to check XMZ after the call.  If it equals -1, the
 call has failed.  
VARIABLES: XMSUB                        TYPE: Input
 VARIABLES DESCRIPTION:   The subject of the message.  It is placed in the
 SUBJECT field (.01) of the message stub.  
  
  If it is more than 65 characters, it is truncated to 65 characters.  
  If it is less than 3 characters, "..." is appended to it.  
  Leading and trailing blanks are removed.  
  Any sequence of 3 or more blanks is reduced to 2.  
  Any control characters are removed.  
  Any up-arrows ("^") are encoded as "~U~".  
  
 It may not pattern match 1"R"1.N, or else the call will fail, and XMZ will be
 set to -1.  
VARIABLES: XMDUZ                        TYPE: Used
 VARIABLES DESCRIPTION:   (optional) This is who the message is from.  It will
 be placed in the FROM field (1) of the message stub.  It may be any of the
 following: 
  
  - If zero, null, or not defined, it defaults to DUZ.  
  - The DUZ of the person the message is "From".  If not the same value as DUZ,
 the person indicated by DUZ (the surrogate) will be captured in the SENDER
 field (1.1).  
  - A string from 1 to 70 characters long indicating a ficticious "from", such
 as "PACKAGE XYZ".  (DUZ will NOT be captured in the SENDER field.) 
VARIABLES: XMZ                          TYPE: Output
 VARIABLES DESCRIPTION:   Message IEN in the Message file 3.9, of the new
 message stub.  
  
 If the call fails (usually because it can't get a lock on the Message file),
 XMZ will be set to -1.  
VARIABLES: DUZ                          TYPE: Used
 VARIABLES DESCRIPTION:   The IEN in the NEW PERSON file (200) of the person
 actually creating the message stub.  If null or zero or not defined, it
 defaults to the Postmaster (.5). 

NUMBER: 10067                           IA #: 10067
  DATE CREATED: FEB 07, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XMA21                        NAME: ADDRESSING API
  ORIGINAL NUMBER: 10067                ID: XMA21
 GENERAL DESCRIPTION:   This routine has four APIs to perform address lookup. 
 They are generally used to address messages and bulletins.  Compare them to
 TOWHOM^XMXAPI (DBIA 2729) and TOWHOM^XMXAPIU (DBIA 2774).  
  
 DEST^XMA21  Perform an interactive recipient lookup showing XMDUN 
             as the default for the FIRST recipient 
  
 DES^XMA21   Perform an interactive recipient lookup showing XMMG 
             as the default for the NEXT recipient 
  
 WHO^XMA21   Perform a non-interactive recipient lookup if X is a 
             local name or network address.  
  
 INST^XMA21  Same as WHO^XMA21.  
  
 This one has nothing to do with addressing: 
  
 CHK^XMA21   Check to see if a user is a member of a mail group.  
  STATUS: Active
COMPONENT/ENTRY POINT: DES
 COMPONENT DESCRIPTION:   Perform an interactive recipient lookup, showing XMMG
 as the default for the NEXT recipient.  
  
 The user is prompted for a recipient, with XMMG as the next default recipient. 
 The prompting will continue until the user has finished entering recipients. 
 The recipients are placed in the array XMY.  Unlike DEST^XMA21, the array XMY
 is not killed upon entry to this API.  (It is assumed that XMY already
 contains some valid recipients.) 
  
 Compare to TOWHOM^XMXAPIU (DBIA 2774).  
  
 Usage: S XMDUZ=user's DUZ 
        S XMMG=next default recipient 
        S XMDF="" (if you don't want any addressing restrictions) 
        D DES^XMA21 
        I $D(XMOUT) the user aborted 
VARIABLES: XMDUZ                        TYPE: Input
 VARIABLES DESCRIPTION:   DUZ of the user doing the addressing.  
VARIABLES: XMMG                         TYPE: Used
 VARIABLES DESCRIPTION:   (optional) Name or DUZ of the NEXT default recipient
 to present to the user.  If not supplied, default is XMDUZ.  
VARIABLES: XMDF                         TYPE: Used
 VARIABLES DESCRIPTION:   (optional) If $D(XMDF), then all addressing
 restrictions are waived.  
VARIABLES: XMY                          TYPE: Output
 VARIABLES DESCRIPTION:   Array of recipients chosen by the user.  Any
 recipients already in the array prior to the call will still be there after
 the call.  
  
 XMY(addressee)="" 
VARIABLES: XMOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   If $D(XMOUT), then the user aborted addressing,
 either by ^ or by time-out.  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   If X="^", then the user aborted addressing, either by
 ^, or by time-out.  Otherwise, X="".  
  
 Just ignore this variable and rely on checking XMOUT.  
COMPONENT/ENTRY POINT: INST
 COMPONENT DESCRIPTION:   Perform a non-interactive recipient lookup.  
  
 The recipient (in X) is looked up.  If the lookup is successful, the recipient
 is placed in the array XMY.  The array XMY is not killed upon entry to this
 API.  
  
 Compare to TOWHOM^XMXAPI (DBIA 2729).  
  
 Usage: S XMDUZ=user's DUZ 
        S X=recipient 
        S XMDF="" (if you don't want any addressing restrictions) 
        S XMLOC="" (if you want any error to be written to the output device) 
        D INST^XMA21 
  
 If the call succeeds, 
        Y=addressee info 
        XMY(addressee)="" 
        XMMG=other addressee info 
  
 If the call fails, 
        Y=-1 
        XMMG=error message 
VARIABLES: XMDUZ                        TYPE: Used
 VARIABLES DESCRIPTION:   (optional) DUZ of the user doing the addressing. 
 Default is DUZ.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   local or remote address 
VARIABLES: XMDF                         TYPE: Used
 VARIABLES DESCRIPTION:   If $D(XMDF), all addressing restrictions are waived.  
VARIABLES: XMLOC                        TYPE: Used
 VARIABLES DESCRIPTION:   If $D(XMLOC), any error (in XMMG) is written to the
 output device.  
VARIABLES: XMY                          TYPE: Output
 VARIABLES DESCRIPTION:   If lookup is successful, the addressee is placed in
 array XMY.  The array is not killed upon entry to this call, so anything
 already in XMY prior to the call will still be there after the call.  
  
 XMY(addressee)="" 
VARIABLES: Y                            TYPE: Output
 VARIABLES DESCRIPTION:   If the lookup is successful, Y is 
  for a local address:   DUZ^full name 
  for a remote address:  domain IEN^domain name 
  
 If the lookup fails, Y=-1.  
VARIABLES: XMMG                         TYPE: Output
 VARIABLES DESCRIPTION:   If the lookup is successful, XMMG is 
  for a local address:   "" 
  for a remote address:  "via "_full domain name via which the message will be
 routed.  
  
 If the lookup fails, XMMG contains an error message suitable for printing.  
 (If $D(XMLOC), it will be printed.) 
COMPONENT/ENTRY POINT: WHO
 COMPONENT DESCRIPTION:   This entry point is identical to INST^XMA21.  
COMPONENT/ENTRY POINT: DEST
 COMPONENT DESCRIPTION:   Perform an interactive recipient lookup, showing
 XMDUN as the default for the FIRST recipient.  
  
 The user is prompted for a recipient, with XMDUN as the first default 
 recipient.  The prompting will continue until the user has finished entering
 recipients.  The recipients are placed in the array XMY.  Unlike DES^XMA21,
 the array XMY is killed upon entry to this API.  
  
 Compare to TOWHOM^XMXAPIU (DBIA 2774).  
  
 Usage: S XMDUZ=user's DUZ 
        S XMDUN=first default recipient 
        S XMDF="" (if you don't want any addressing restrictions) 
        D DEST^XMA21 
        I $D(XMOUT) the user aborted 
VARIABLES: XMDUZ                        TYPE: Input
 VARIABLES DESCRIPTION:   DUZ of the user doing the addressing.  
VARIABLES: XMDUN                        TYPE: Used
 VARIABLES DESCRIPTION:   The name or DUZ of the first default recipient.  If
 not supplied, default is XMDUZ.  
VARIABLES: XMDF                         TYPE: Used
 VARIABLES DESCRIPTION:   If $D(XMDF), then all addressing restrictions are
 waived.  
VARIABLES: XMY                          TYPE: Output
 VARIABLES DESCRIPTION:   Array of recipients chosen by the user.  The array is
 killed upon entry to the API, so any recipients already in the array prior to
 the call are gone.  
  
 XMY(addressee)="" 
VARIABLES: XMOUT                        TYPE: Output
 VARIABLES DESCRIPTION:   If $D(XMOUT), then the user aborted addressing,
 either by ^ or by time-out.  
VARIABLES: X                            TYPE: Output
 VARIABLES DESCRIPTION:   If X="^", then the user aborted addressing, either by
 ^, or by time-out.  Otherwise, X="".  
  
 Just ignore this variable and rely on checking XMOUT.  
COMPONENT/ENTRY POINT: CHK
 COMPONENT DESCRIPTION:   Check to see whether XMDUZ is a member of group Y.  
  
 Example: 
  
  >S Y=1,XMDUZ=4 D CHK^XMA21 W $T 
  0  (User is not a member.) 
  
  >S Y=2,XMDUZ=4 D CHK^XMA21 W $T 
  1  (User is a member.) 
VARIABLES: XMDUZ                        TYPE: Input
 VARIABLES DESCRIPTION:   DUZ of the user whose group membership you wish to
 check.  
VARIABLES: Y                            TYPE: Input
 VARIABLES DESCRIPTION:   IEN of the mail group in the MAIL GROUP file (#3.8)
 whose membership you wish to check.  
VARIABLES: $T                           TYPE: Output
 VARIABLES DESCRIPTION:   If $T, then the user is a member; otherwise not.  

NUMBER: 10068                           IA #: 10068
  DATE CREATED: FEB 07, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XMADGO                       NAME: START BACKGROUND DELIVERY TASK
  ORIGINAL NUMBER: 10068                ID: XMADGO
 GENERAL DESCRIPTION:   This routine starts the background mail filer for local
 mail delivery.  
  STATUS: Active
COMPONENT/ENTRY POINT: ZTSK
 COMPONENT DESCRIPTION:   This API starts tasks to deliver mesages in local
 delivery queues.  There are no input variables.  
  
 Usage:  D ZTSK^XMADGO 
  
 It looks at each of the queues to see if there are any messages in them.  If
 there are, it checks to see if there's already a task running for that queue. 
 If there isn't, it starts up a task to deliver messages in that queue.  The
 tasked routine is GO^XMTDL.  
  
 There is no need to start the background filer from here, and, in fact, usage
 of this entry point is not recommended. If, for some reason, the background
 filers aren't running, and they ought to be, the MailMan manager option
 XMMGR-START-BACKGROUND-FILER is the correct way to start them.  (The MailMan
 manager option XMMGR-STOP-BACKGROUND-FILER can be used to stop the filer.) 

NUMBER: 10069                           IA #: 10069
  DATE CREATED: FEB 08, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XMB                          NAME: SEND A BULLETIN API
  ORIGINAL NUMBER: 10069                ID: XMB
 GENERAL DESCRIPTION:   This API sends bulletins and has the following entry
 points: 
  
     ^XMB - Create and send a bulletin in the background (task).  
   EN^XMB - Create and send a bulletin in the foreground (while you wait).  
 BULL^XMB - Interactively select a bulletin, define its parameters, 
            and send it.  
  
 See the MailMan Programmer Manual, Appendix D, Setting up Bulletins, for 
 information on bulletins, how to set them up, and how to create a bulletin 
 cross reference.  
  STATUS: Active
COMPONENT/ENTRY POINT: XMB
 COMPONENT DESCRIPTION:   Create and send a bulletin in the background.  A task
 is created to do this.  XMZ, the IEN of the bulletin created in the MESSAGE
 file (#3.9), is not returned.  Unless you need to know XMZ, this entry point
 is preferred over EN^XMB, because it is faster.  
  
 Compare to TASKBULL^XMXAPI (DBIA 2729).  
  
 Recipients of the bulletin will include any entries in the XMY array that the
 caller has defined and the members of mail groups that are included in the
 definition of the entry in the Bulletin file (#3.6) at the time of delivery. 
 There must be valid recipients or the bulletin will not be delivered.  
  
 Usage: D ^XMB 
  
 Inputs: 
  XMB              - name of Bulletin (in file 3.6) 
  XMB(parameter #) - value to be stuffed into the bulletin for 
                     each parameter. (eg. XMB(1)=data for parameter #1) 
  XMTEXT(line)     - optional text to append to the bulletin 
  XMY(DUZ or name@inst) - optional additional recipients 
  XMDUZ            - optional sender's DUZ 
  XMDT             - optional Date-Time for future delivery 
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   Identity of the user.  The user's IEN in the NEW
 PERSON file.  
VARIABLES: XMB                          TYPE: Input
 VARIABLES DESCRIPTION:   See variable description for EN^XMB.  
  
 XMB is not killed.  
VARIABLES: XMB(                         TYPE: Used
 VARIABLES DESCRIPTION:   (optional) See variable description for EN^XMB.  
  
 XMB array is not killed.  
VARIABLES: XMBTMP                       TYPE: Used
 VARIABLES DESCRIPTION:   (optional) See variable description for EN^XMB.  
VARIABLES: XMDF                         TYPE: Used
 VARIABLES DESCRIPTION:   (optional) See variable description for EN^XMB.  
VARIABLES: XMDT                         TYPE: Used
 VARIABLES DESCRIPTION:   (optional) Date or date/time in the future when the
 bulletin should be sent.  Default is NOW.  Must be in a format which FileMan
 can understand.  
VARIABLES: XMDUZ                        TYPE: Input
 VARIABLES DESCRIPTION:   The user's DUZ or free text.  This is from whom the
 bulletin will appear to be. 
VARIABLES: XMTEXT                       TYPE: Used
 VARIABLES DESCRIPTION:   (optional) See variable description for EN^XMB.  
VARIABLES: XMY                          TYPE: Used
 VARIABLES DESCRIPTION:   (optional) See variable description for EN^XMB.  
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Create and send a bulletin in the foreground, i.e.
 while you wait.  The delivery will happen in the background.  XMZ, the IEN of
 the bulletin created in the MESSAGE file (#3.9), is returned. 
  
 Compare to SENDBULL^XMXAPI (DBIA 2729). 
  
 The recipients of the bulletin will include any entries in the XMY array that
 the caller has defined and the members of mail groups that are included in the
 definition of the entry in the Bulletin file (#3.6) at the time of delivery. 
 There must be valid recipients or the bulletin will not be delivered.  
  
 Usage: D EN^XMB 
  
 Inputs: 
  XMB              - name of Bulletin (in file 3.6) 
  XMB(parameter #) - value to be stuffed into the bulletin for 
                     each parameter. (eg. XMB(1)=data for parameter #1) 
  XMTEXT(line)     - optional text to append to the bulletin 
  XMY(DUZ or name@inst) - optional additional recipients 
  XMDUZ            - optional sender's DUZ 
  
 Outputs: 
  XMZ              - message number 
VARIABLES: DUZ                          TYPE: Used
 VARIABLES DESCRIPTION:   (optional) The identity of the user.  The user's IEN
 in the NEW PERSON file.  Default is .5, the POSTMASTER.  
VARIABLES: XMDUZ                        TYPE: Used
 VARIABLES DESCRIPTION:   (optional) The user's DUZ or free text.  This is from
 whom the bulletin will appear to be.  Default is DUZ.  
VARIABLES: XMB(                         TYPE: Used
 VARIABLES DESCRIPTION:   If the bulletin has parameters, this must be an array
 containing the parameters to insert into the bulletin.  
  
  XMB(1) = parameter 1 
  XMB(2) = parameter 2 
  etc.  
  
 XMB is killed upon successful completion of this API.  
VARIABLES: XMBTMP                       TYPE: Used
 VARIABLES DESCRIPTION:   (optional) If $D(XMBTMP), then MailMan will not
 initialize (kill) the ^TMP addressee global, because it contains bulletin
 addressees set prior to calling this API. 
VARIABLES: XMDF                         TYPE: Used
 VARIABLES DESCRIPTION:   (optional) If $D(XMDF) all addressing restrictions
 are waived.  
VARIABLES: XMTEXT                       TYPE: Used
 VARIABLES DESCRIPTION:   (optional) The open root of an array containing
 additional text to append to the bulletin.  The array must be compatible with
 FileMan word processing APIs.  
  
 XMTEXT is killed upon successful completion of this API.  
VARIABLES: XMY                          TYPE: Used
 VARIABLES DESCRIPTION:   (optional) Array of addressees, in addition to the
 mail groups already defined in the bulletin, to which to send the bulletin. 
  
  XMY(addressee A)="" 
  XMY(addressee B)="" 
  etc.  
  
 XMY is killed upon successful completion of this API.  
VARIABLES: XMB                          TYPE: Both
 VARIABLES DESCRIPTION:   The full name of the bulletin.  It must be the
 complete name in the correct case.  
  
 If the bulletin is not found, XMB will be set to -1.  
  
 XMB is killed upon successful completion of this API.  
VARIABLES: XMZ                          TYPE: Output
 VARIABLES DESCRIPTION:   The IEN in the MESSAGE file (3.9) of the bulletin.  
COMPONENT/ENTRY POINT: BULL
 COMPONENT DESCRIPTION:   Manually create and send a bulletin.  MailMan
 interactively takes the user through the selection, creation, and sending of a
 bulletin.  
  
 DUZ and XMDUZ must already be defined.  

NUMBER: 10070                           IA #: 10070
  DATE CREATED: FEB 19, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XMD                          NAME: SEND / FORWARD A MESSAGE API
  ORIGINAL NUMBER: 10070                ID: XMD
 GENERAL DESCRIPTION:   Contains the following APIs related to creating,
 sending, and/or forwarding messages: 
  
  ^XMD      create, address, and send a message 
  EN1^XMD   add text to a message, address it, and send it 
  ENL^XMD   add text to a message 
  ENT^XMD   interactive create, address, and send a message 
  ENT1^XMD  forward a message 
  ENT2^XMD  forward a message and prompt user for more recipients 
  
 See the MailMan Programmer Manual, Appendix B, Efficient Use of the API, for
 some suggestions on how to efficiently create huge messages used for data
 transfer.  
  
 I/O variables for the various APIs: 
  
 DUZ     (in, optional) User's DUZ.  This is who is actually sending the 
 message.  If DUZ is not defined, it defaults to the Postmaster (.5).  
  
 XMDUZ   (in, optional) User's DUZ or free text.  This is from whom the message
 will appear to be.  If it is not defined, it defaults to DUZ.  If it is free
 text, it must not be more than 70 characters. 
  
 XMSUB   (in) Subject of the message.  Must be from 3 to 65 characters long.  
 If it is less than 3 characters, then "..." will be appended to it.  If it is
 more than 65 characters, it will be truncated. 
  
 XMTEXT  (in) The root of the array, in open format, which contains the text of
 the message.  The array may be a local or global variable, and it must be in a
 format acceptable to FileMan word-processing APIs. 
  
 XMSTRIP (in, optional) Characters that should be stripped from the text of the
 message.  Default is none.  
  
 XMDF    (in, optional) If $D(XMDF), addressing restrictions are waived: 
         - ignore 'domain closed' 
         - ignore 'keys required for domain' 
         - ignore 'may not forward to domain' 
         - ignore 'may not forward priority mail to mail groups' 
         - ignore 'message length restrictions to remote addressees' 
  
 XMMG    (in, optional) If XMY is not supplied and the process is not queued,
 XMMG may be used as the default for the first 'send to:' prompt.  
         (out) Contains an error message if an error occurs.  Otherwise, 
 undefined.  
  
 XMZ     (in) Message IEN in MESSAGE file (3.9) of message to be forwarded or
 altered.  
         (out) Message IEN in Message file (3.9) of message created/sent.  
  
 XMY(    (in) Addressee array.  May contain any of the following: 
   User's DUZ, or enough of user's name for a positive ID 
        eg: XMY(1301)="" or XMY("lastname,firs")="" 
   G.group name (enough for positive ID) 
        eg: XMY("G.MY GROUP")="" 
   S.server name (enough for positive ID) 
        eg: XMY("S.YOUR SERVER OPTION")="" 
   D.device name (enough for positive ID) 
        eg: XMY("D.MY PRINTER")="" 
  
 You may prefix each addressee (except devices and servers) by: 
   I: for 'information only' recipient (may not reply) 
        eg: XMY("I:1301")="" or XMY("I:lastname,firs")="" 
   C: for 'copy' recipient (not expected to reply) 
        eg: XMY("C:1301")="" or XMY("C:lastname,firs")="" 
   L@datetime: for when (in future) to send to this recipient (datetime may be
 anything accepted by FileMan) 
        eg: XMY("L@25 DEC@0500:1301")="" or XMY("L@1 JAN:lastname,firs")="" 
         or XMY("L@2981225.05:1301")="" 
  (may combine IL@datetime:  or  CL@datetime:) 
  
 To delete recipient, prefix with - 
        eg: XMY(-1301)="" or XMY("-lastname,firs")="" 
  
 Append "@<sitename>" for any addressees at another site: 
        eg: XMY("I:G.group@site.DNS")="" 
         or XMY("lastname,firs@site.DNS")="" 
         or XMY("6102@site.DNS")="" 
  
 If the sender (XMDUZ) is a recipient, you may specify the basket in the 
 sender's mailbox to which the message should be delivered.  
        eg: XMY(XMDUZ,0)=5 (basket IEN) 
         or XMY(XMDUZ,0)="MY BASKET" (full basket name) 
  
 If SHARED,MAIL is a recipient, you may specify the basket in SHARED,MAIL's 
 mailbox to which the message should be delivered.  
        eg: XMY(.6,0)=5 (basket IEN) 
         or XMY(.6,0)="MY BASKET" (full basket name) 
  
 If SHARED,MAIL is a recipient, you may specify the date on which the message
 should be deleted from SHARED,MAIL's mailbox, 
        eg: XMY(.6,"D")=<date> (any date recognized by FileMan) 
  
 Sample XMY entries: 
  
        XMY("USER,LOCAL")="" Addressed to a local user, whose name is
 USER,LOCAL.  
  
        XMY("G.MAIL_GROUP)="" Addressed to a local mail group, whose name is in
 the MAIL GROUP file.  
  
        XMY("LAST,FIRST@domain_name")="" Addressed to a user, at the site named
 domain_name.  LAST,FIRST must be in the NEW PERSON file at that site.  If the
 local system domain name is domain_name, it will be a local recipient. 
  
        XMY("G.MAIL_GROUP@domain_name")="" Addressed to a mail group, at the
 site named domain_name.  MAIL_GROUP must be found in the MAIL GROUP file at
 that site.  
  
        XMY("D.DEVICE@domain_name")="" Addressed to a device, at the site named
 domain_name.  DEVICE must be found in the DEVICE file at that site.  
  
        XMY("S.OPTION@domain_name")="" Addressed to an option, at the site
 named domain_name.  OPTION must be found in the OPTION file at that site.  
  
        XMY("INFO:MAIL_GROUP@domain_name")="" Addressed to a mail group at a
 remote site.  The message will be delivered "information only" to that group,
 meaning that they will not be able to reply to it.  
  STATUS: Active
COMPONENT/ENTRY POINT: XMD
 COMPONENT DESCRIPTION:   Create and send a new message.  If no recipients are
 defined (in XMY), and '$D(ZTQUEUED), then prompt for them.  Addressing
 restrictions are automatically waived, so there is no need to set XMDF. 
  
 Compare to SENDMSG^XMXAPI (DBIA 2729).  
  
 Usage: 
  Set up the input variables 
  D ^XMD 
  Check the output variables 
  
 More extensive definitions of the I/O variables can be found in the General
 Description. 
  
 Core input variables: 
  DUZ     (optional) User DUZ.  
  XMDUZ   (optional) Message is from other than DUZ.  
  XMSUB   Message subject.  
  XMTEXT  Message text.  
  XMY     (optional) Message addressees.  If none, and '$D(ZTQUEUED), the user
 will be prompted for them.  If none, and $D(ZTQUEUED), the message will be
 created, but it won't be sent, and XMMG will not be defined.  
  
 Additional input variables: 
  DIFROM  (optional) Specifically for FileMan package 
  XMMG    (optional) If there are no recipients in XMY, and the job is running
 in the foreground, XMMG may contain the default recipient presented to the
 user.  If XMMG is not defined, then the default recipient is the user, as
 defined by XMDUZ.  
  XMROU   (optional) Array of routines to be loaded in a PackMan message.  For
 each routine, set XMROU(x)="", where x is the routine name.  
  XMSTRIP (optional) Characters to be removed from the message text 
  
 Output variables: 
  XMMG    This is the variable which the calling program should check to see 
 whether or not the call was successful.  If XMMG is undefined, then the call
 was successful.  If the call failed, then XMMG contains the error message.  
  XMZ     If the call was successful, then XMZ is the message IEN of the 
 message which was created.  If the call failed, then XMZ is unchanged or 
 undefined.  
  
 Variables killed upon exit: 
  If the call is successful, XMSUB, XMTEXT, XMY, XMSTRIP, XMMG will be killed. 
 If the call fails, those variables may or may not be killed, except for XMMG,
 which will contain an error message.  
  
 WARNING: If calling XMD in a Pre-init or Post-init, you MUST NEW DIFROM prior
 to the call or your message will NOT be delivered.  
COMPONENT/ENTRY POINT: ENT1
 COMPONENT DESCRIPTION:   Forward a message.  Addressing restrictions are
 automatically waived, so there is no need to set XMDF.  
  
 Compare to FWDMSG^XMXAPI (DBIA 2729).  
  
 Usage: 
  Set up the input variables 
  D ENT1^XMD 
  
 More extensive definitions of the I/O variables can be found in the General 
 Description.  
  
 Input variables: 
  DUZ     (optional) User DUZ.  
  XMDUZ   (optional) Message is forwarded by other than DUZ.  
  XMY     Addressees to forward to 
  XMZ     Message IEN in MESSAGE file (3.9), of message to forward.  
  
 Output variables: 
  None.  
  
 Variables killed upon exit: 
  XMDUZ,XMY 
COMPONENT/ENTRY POINT: ENT2
 COMPONENT DESCRIPTION:   Forward a message.  If '$D(ZTQUEUED), prompt for
 additional recipients, whether or not any are already defined.  
  
 Usage: 
  Set up the input variables 
  D ENT2^XMD 
  
 More extensive definitions of the I/O variables can be found in the General 
 Description.  
  
 Input variables: 
  DUZ     (optional) User DUZ.  
  XMDUZ   (optional) Message is forwarded by other than DUZ.  
  XMDF    (optional) If $D(XMDF), all addressing restrictions are waived.  
  XMY     (optional) Addressees to forward to.  If '$D(ZTQUEUED) (job running
 in the foreground), the user will be prompted for additional recipients.  
  XMZ     Message IEN in MESSAGE file (3.9), of message to forward.  
  
 Output variables: 
  None.  
  
 Variables killed upon exit: 
  XMDUZ,XMY 
COMPONENT/ENTRY POINT: ENT
 COMPONENT DESCRIPTION:   Place this entry point in an interactive option for
 the process to send a message.  It can be put onto many menus.  It is the same
 as XMSEND, the Send a Message option.  It requires that the Entry Action and
 Exit Action be specified.  Set up the option as follows: 
  
 Entry Action:  S XMMENU(0)=<name of the menu option> 
  
 Routine:       ENT^XMD 
  
 Exit Action:   K XMMENU D CHECKOUT^XM 
  
 Compare to SENDMSG^XMXAPIU (DBIA 2774).  
  
 Input Variables: 
  DUZ   User's DUZ 
  
 Output Variables: 
  none 
COMPONENT/ENTRY POINT: ENL
 COMPONENT DESCRIPTION:   Add text to an existing message.  
  
 Usage: 
  Set up the input variables 
  D ENL^XMD 
  
 More extensive definitions of the I/O variables can be found in the General
 Description. 
  
 Core input variables: 
  DUZ     User DUZ.  
  XMTEXT  Message text.  
  XMZ     Message IEN in the MESSAGE file (3.9).  
  
 Additional input variables: 
  XMSTRIP (optional) Characters to be removed from the message text 
  
 Output variables: 
  none 
  
 Variables killed upon exit: 
  XMSTRIP 
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   Add text to a message, and address it and send it. 
 If no recipients are defined (in XMY), and '$D(ZTQUEUED), then prompt the user
 for them.  
  
 Usage: 
  Set up the input variables 
  D EN1^XMD 
  
 More extensive definitions of the I/O variables can be found in the General
 Description. 
  
 Core input variables: 
  DUZ     User DUZ.  
  XMTEXT  Message text.  
  XMY     (optional) Message addressees.  If none, and '$D(ZTQUEUED), the user
 will be prompted for them.  If none, and $D(ZTQUEUED), the message will be
 created, but it won't be sent, and XMMG will not be defined.  
  XMZ     Message IEN in the MESSAGE file (3.9).  
  
 Additional input variables: 
  DIFROM  (optional) Specifically for FileMan package 
  XMMG    (optional) If there are no recipients in XMY, and the job is running
 in the foreground, XMMG may contain the default recipient presented to the
 user.  If XMMG is not defined, then the default recipient is the user, as
 defined by DUZ.  
  XMROU   (optional) Array of routines to be loaded in a PackMan message.  For
 each routine, set XMROU(x)="", where x is the routine name.  
  XMSTRIP (optional) Characters to be removed from the message text 
  
 Output variables: 
  none 
  
 Variables killed upon exit: 
  XMTEXT, XMY, XMSTRIP, XMMG 

NUMBER: 10071                           IA #: 10071
  DATE CREATED: FEB 19, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XMPG                         NAME: GLOBAL PACKMAN MESSAGE API
  ORIGINAL NUMBER: 10071                ID: XMPG
 GENERAL DESCRIPTION:   This routine contains the following API: 
  
 ENT^XMPG - Create and send a PackMan message with globals 
  STATUS: Active
COMPONENT/ENTRY POINT: ENT
 COMPONENT DESCRIPTION:   Create and send a PackMan message with any number of
 local or global data arrays.  If no recipients are defined, the message will
 be created, but it won't be sent anywhere.  Addressing restrictions are waived
 (it's as if you set XMDF).  (To create and send a PackMan message with
 routines in it, use ^XMD).  
  
 Usage: D ENT^XMPG 
  
 Inputs: 
  DUZ         Sender 
  XMSUB       Subject 
  XMY         Recipients 
  XMTEXT      A semi-colon separated list of open roots 
  
 Outputs: 
  XMZ         Message Number 
  
 Example: 
  K XMZ,XMMG ; It's a good idea to kill these or new them 
  S XMSUB="Demo",XMY(DUZ)="",XMTEXT="LOCAL(;^TMP($J,""A""," 
  D ENT^XMPG I '$D(XMZ) W *7,!,"*** Packman message NOT created." 
  
 Note:  Only the variables that are necessary for the entry point should exist. 
 If other XM namespaced variable exists, results may not be predictable.  If
 XMTEXT does not point to valid packman data, the data may not be successfully
 transferred in its entirety. 
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The user's DUZ.  The user's IEN in the NEW PERSON
 file (200).  
VARIABLES: XMDUZ                        TYPE: Used
 VARIABLES DESCRIPTION:   (optional) The DUZ of the person from whom the
 message should appear to be. Default is DUZ.  
VARIABLES: XMSUB                        TYPE: Input
 VARIABLES DESCRIPTION:   The subject of the message.  Must be 3-65 characters. 
 
VARIABLES: XMTEXT                       TYPE: Input
 VARIABLES DESCRIPTION:   A semi-colon (;) delimited string of the open roots
 of arrays and globals to be loaded into the PackMan message.  
VARIABLES: XMY                          TYPE: Used
 VARIABLES DESCRIPTION:   (optional) Recipients to whom to send the PackMan
 message.  
  
 XMY(addressee)="" 
  
 XMY is killed upon successful completion of this API.  
VARIABLES: TMP("XMP",$J,                TYPE: Used
 VARIABLES DESCRIPTION:   (optional) If you wish to place any message text in
 the PackMan message to be read by any of the recipients, place it under
 ^TMP("XMP",$J), as follows: 
  
  ^TMP("XMP",$J,1,0)="Hi! Here are the globals" 
  ^TMP("XMP",$J,2,0)="for our project" 
         etc.  
  
 ^TMP("XMP",$J) is killed upon successful completion of this API.  
VARIABLES: DIFROM                       TYPE: Used
 VARIABLES DESCRIPTION:   (optional) Specifically for FileMan or KIDS packages. 
 
VARIABLES: XMZ                          TYPE: Output
 VARIABLES DESCRIPTION:   If the API is successful, message IEN in the MESSAGE
 file (3.9) of the Packman message which was created. 
  
 If the API is not successful, it's unchanged or undefined. 
  
 It's important, therefore, that XMZ be newed or killed before this API is 
 called. 
VARIABLES: XMMG                         TYPE: Output
 VARIABLES DESCRIPTION:   If the API is successful, it's unchanged or
 undefined.  
  
 If the API is not successful, it contains an error message.  
  
 It's important, therefore, that XMMG be newed or killed before this API is 
 called.  

NUMBER: 10072                           IA #: 10072
  DATE CREATED: FEB 06, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XMA1C                        NAME: SERVER MESSAGE API
  ORIGINAL NUMBER: 10072                ID: XMA1C
 GENERAL DESCRIPTION:   This API deals with server messages: 
  - REMSBMSG^XMA1C  remove a message from a server basket 
  - SETSB^XMA1C     put a message into a server basket 
  
 Server messages are usually placed in one of the Postmaster's server baskets
 (using SETSB^XMA1C) upon receipt of the message, and deleted from the basket
 (using REMSBMSG^XMA1C) upon successful processing of the message by the
 application to which the server belongs.  See the Kernel Systems Manual for
 more information on servers.  
  STATUS: Active
COMPONENT/ENTRY POINT: SETSB
 COMPONENT DESCRIPTION:   Put a message in a server basket.  
  
 Servers may use this entry point to put messages into a Postmaster server 
 basket to protect the message from automatic purges.  TaskMan uses it to place
 server messages in a server basket if the server SAVE REQUEST field in the
 OPTION file is 1.  A server might use this entry point if the message cannot
 be processed immediately (and SAVE REQUEST was not 1) or if the server wishes
 to pass the message to another server.  
  
 As long as the message is in a server basket, MailMan will not purge it.  
  
 Compare to PUTSERV^XMXAPI (DBIA 2729).  
  
 Usage: S XMXX=full server basket name, beginning with "S." 
        S XMZ=message IEN 
        D SETSB^XMA1C 
VARIABLES: XMXX                         TYPE: Input
 VARIABLES DESCRIPTION:   Full name of the server basket, preceded by "S.",
 into which the message should be put.  Note that the server basket name is the
 same as the server option name.  
VARIABLES: XMZ                          TYPE: Input
 VARIABLES DESCRIPTION:   Message IEN in the Message file of the message to be
 put into the server basket.  
COMPONENT/ENTRY POINT: REMSBMSG
 COMPONENT DESCRIPTION:   Remove a message from a server basket.  
  
 When the application which uses the server basket has finished processing a
 message in that basket, it should remove the message from the server basket. 
 Otherwise, the message will stay forever.  MailMan will not purge any message
 which is in a server basket.  
  
 Upon exit, the following variables are killed: XMKD, XMZ, XMDUZ, XMK, XMSER 
  
 Compare to ZAPSERV^XMXAPI (DBIA 2729).  
  
 Usage: S XMSER=full server name, beginning with "S." 
        S XMZ=message IEN 
        D REMSBMSG^XMA1C 
VARIABLES: XMSER                        TYPE: Input
 VARIABLES DESCRIPTION:   Full name of the server basket, preceded by "S.",
 from which the message is to be removed.  Note that the server basket name is
 the same as the server option name.  
VARIABLES: XMZ                          TYPE: Input
 VARIABLES DESCRIPTION:   Message IEN in the Message file of the server message
 to be removed.  

NUMBER: 10073                           IA #: 10073
  DATE CREATED: FEB 19, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XMS3
  NAME: MAILMAN: Message Body Access, including Servers
  ORIGINAL NUMBER: 10073                ID: XMS3
 GENERAL DESCRIPTION:   ^XMS3 contains the following application programmer
 entry point: 
  
      REC^XMS3 to obtain the next line in a message 
  STATUS: Active
COMPONENT/ENTRY POINT: REC
 COMPONENT DESCRIPTION:   D REC^XMS3 delivers the lines of a message one at a
 time.  It is functionally equivalent to X XMREC, except that it can be used by
 programs that are not servers.  
  
  
 This entry point is NOT RECOMMENDED.  Use of DBIA 1283 provides equivalent 
 capabilities today and more flexibility for the future.  
VARIABLES: XMZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The internal number of the message to be processed.  
VARIABLES: XMPOS                        TYPE: Input
 VARIABLES DESCRIPTION:   The number of the last line read (or null).  
VARIABLES: XMPOS                        TYPE: Output
 VARIABLES DESCRIPTION:   The number of the "next" line in the message; if no
 further lines, XMPOS="" 
VARIABLES: XMER                         TYPE: Output
 VARIABLES DESCRIPTION:   0 unless no lines greater than XMPOS, then -1 
VARIABLES: XMRG                         TYPE: Output
 VARIABLES DESCRIPTION:   line XMPOS of message XMZ 

NUMBER: 10074                           IA #: 10074
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XQH
  NAME: XQH                             ORIGINAL NUMBER: 10074
  ID: XQH                               STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Display Help Frames (in Menu Manager chapter) 
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   Display Help Frames (in Menu Manager chapter) 

NUMBER: 10075                           IA #: 10075
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19,
  DATE CREATED: MAR 01, 2011            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: OPTION FILE                     ORIGINAL NUMBER: 10075
  ID: DIC(19,
GLOBAL REFERENCE: DIC(19,
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
FIELD NUMBER: 1                         FIELD NAME: MENU TEXT
  LOCATION: 0;2                         ACCESS: Read w/Fileman
FIELD NUMBER: 3.5                       FIELD NAME: DESCRIPTION
  LOCATION: WP-DIC(19,D0,1,             ACCESS: Read w/Fileman
FIELD NUMBER: 2                         FIELD NAME: OUT OF ORDER MESSAGE
  LOCATION: 0;3                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: DIC(19,D0,"RPC",
FIELD NUMBER: .01                       FIELD NAME: RPC
  LOCATION: 0;1                         ACCESS: Both R/W w/Fileman
  STATUS: Active                        DATE ACTIVATED: MAR 01, 2011

NUMBER: 10076                           IA #: 10076
  FILE NUMBER: 200                      GLOBAL ROOT: XUSEC(
  DATE CREATED: DEC 08, 1994            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: XUSEC GLOBAL                    ORIGINAL NUMBER: 10076
  ID: XUSEC(
GLOBAL REFERENCE: XUSEC(KEY,DUZ)
 GLOBAL DESCRIPTION:   XUSEC(KEY,DUZ) is supported for "Read Access" by all.  
 Write access is limited to keys in assigned namespace only.  
  
 Access is not allowed to ^XUSEC(0,...  
  STATUS: Active

NUMBER: 10077                           IA #: 10077
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XQ92
  NAME: XQ92                            ORIGINAL NUMBER: 10077
  ID: XQ92                              STATUS: Active
COMPONENT/ENTRY POINT: NEXT
 COMPONENT DESCRIPTION:   Restricted Times Check (in menu Manager chapter) 

NUMBER: 10078                           IA #: 10078
  DATE CREATED: FEB 03, 1999            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XQCHK                        NAME: XQCHK
  ORIGINAL NUMBER: 10078                ID: XQCHK
  STATUS: Active
COMPONENT/ENTRY POINT: OP
 COMPONENT DESCRIPTION:   Current Option Check (in Menu Manager chapter) 
COMPONENT/ENTRY POINT: $$ACCESS
 COMPONENT DESCRIPTION:   This extrinsic function is used to find out if a user
 has access to a particular option.  
  
           W $$ACCESS(DUZ,Option IEN) returns: 
       
       -1:no such user in the New Person File 
       -2: User terminated or has no access code 
       -3: no such option in the Option File 
       0: no access found in any menu tree the user owns 
       
           All other cases return a 4-piece string stating 
           access ^ menu tree IEN ^ a set of codes ^ key 
       
       O^tree^codes^key: No access because of locks (see XQCODES below) 
         where 'tree' is the menu where access WOULD be allowed 
         and 'key' is the key preventing access 
       1^OpIEN^^: Access allowed through Primary Menu 
       2^OpIEN^codes^: Access found in the Common Options 
       3^OpIEN^codes^: Access found in top level of secondary option 
       4^OpIEN^codes^: Access through a the secondary menu tree OpIEN.  
       
       XQCODES can contain: 
         N=No Primary Menu in the User File (warning only) 
         L=Locked and the user does not have the key (forces 0 in first piece) 
         R=Reverse lock and user has the key (forces 0 in first piece) 
       
  
VARIABLES: DUZ                          TYPE: Input
 VARIABLES DESCRIPTION:   The users DUZ.  
VARIABLES: option                       TYPE: Input
 VARIABLES DESCRIPTION:   This can be the option name or option IEN.  

NUMBER: 10079                           IA #: 10079
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XQDATE
  NAME: XQDATE                          ORIGINAL NUMBER: 10079
  ID: XQDATE                            STATUS: Active
COMPONENT/ENTRY POINT: XQDATE
 COMPONENT DESCRIPTION:   Current Date/Time (in Menu Manager chapter) 

NUMBER: 10080                           IA #: 10080
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XQH4
  NAME: XQH4                            ORIGINAL NUMBER: 10080
  ID: XQH4                              STATUS: Active
COMPONENT/ENTRY POINT: ACTION
 COMPONENT DESCRIPTION:   Print Help Frames (in Menu Manager chapter) 

NUMBER: 10081                           IA #: 10081
  DATE CREATED: DEC 08, 1999            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XQALERT                      NAME: XQALERT
  ORIGINAL NUMBER: 10081                ID: XQALERT
  STATUS: Active
KEYWORDS: ALERTS
COMPONENT/ENTRY POINT: DELETE
 COMPONENT DESCRIPTION:   Clear Obsolete Alerts (in Tools chapter) 
COMPONENT/ENTRY POINT: DELETEA
 COMPONENT DESCRIPTION:   Clear Obsolete Alerts (in Tools chapter) 
COMPONENT/ENTRY POINT: SETUP
 COMPONENT DESCRIPTION:   The new SETUP1 entry point should be used instead of
 this entry point since it returns an indicator of success or failure on
 setting up the specified alert.  In new work this entry point should NOT be
 used, Create Alerts (in Tools chapter) 
COMPONENT/ENTRY POINT: PATIENT
COMPONENT/ENTRY POINT: GETACT
 COMPONENT DESCRIPTION:   Return need variables for specific alert.  
COMPONENT/ENTRY POINT: USER
 COMPONENT DESCRIPTION:   Returns current alerts for the user in an array.  
COMPONENT/ENTRY POINT: USERDEL
 COMPONENT DESCRIPTION:   Delete undesired alerts for a user.  
COMPONENT/ENTRY POINT: SETUP1
 COMPONENT DESCRIPTION:   This entry point should be used instead of SETUP. 
 This entry point is called as a function and Returns a string beginning with 1
 if successful, 0 if not successful.  If successful the second piece is the IEN
 in the Alert Tracking File and the third piece is the value of XQAID.  If not 
 successful XQALERR is defined and contains reason for failure.  
COMPONENT/ENTRY POINT: ACTION
 COMPONENT DESCRIPTION:   This entry point can be used to have the action for a
 specific alert for the user executed.  The alert ID for the desired alert is
 passed as an argument.  
  DATE ACTIVATED: JUL 29, 2009

NUMBER: 10082                           IA #: 10082
  FILE NUMBER: 80                       GLOBAL ROOT: ICD9(
  DATE CREATED: AUG 07, 1996            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: File                            NAME: ICD DIAGNOSIS FILE
  ORIGINAL NUMBER: 10082                ID: ICD9(
GLOBAL REFERENCE: ICD9(D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 3                         FIELD NAME: DIAGNOSIS
  LOCATION: 0;3                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: MAJOR DIAGNOSTIC CATEGORY
  LOCATION: 0;5                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9.5                       FIELD NAME: USE ONLY WITH SEX
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 100                       FIELD NAME: INACTIVE FLAG
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 102                       FIELD NAME: INACTIVE DATE
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ICD9(D0,1
FIELD NUMBER: 10                        FIELD NAME: DESCRIPTION
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This will enable access to all fields on the 0-node,
 and the description of the ICD Diagnosis codes.  
  
 Read access is permitted via FileMan and Direct Reads.  The entire 0-node of
 the ^ICD9(D0 may be read into a local variable.  
  
 Also, the "BA" cross-reference on field .01 may be used to find the code 
 reference.  
  
 Direct read of the "ACT" cross-reference will also be permitted.  
  STATUS: Retired                       EXPIRATION DATE: NOV 15, 2008

NUMBER: 10083                           IA #: 10083
  FILE NUMBER: 80.1                     GLOBAL ROOT: ICD0(
  DATE CREATED: AUG 07, 1996            CUSTODIAL PACKAGE: DRG GROUPER
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: File                            NAME: ICD OPERATION/PROCEDURE FILE
  ORIGINAL NUMBER: 10083                ID: ICD0(
GLOBAL REFERENCE: ICD0(D0,0)
FIELD NUMBER: .01                       FIELD NAME: CODE NUMBER
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER:  
FIELD NUMBER: 4                         FIELD NAME: OPERATION/PROCEDURE
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 9.5                       FIELD NAME: USE ONLY WITH SEX
  LOCATION: 0;10                        ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 100                       FIELD NAME: INACTIVE FLAG
  LOCATION: 0;9                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 102                       FIELD NAME: INACTIVE DATE
  LOCATION: 0;11                        ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ICD0(D0,1)
FIELD NUMBER: 10                        FIELD NAME: DESCRIPTION
  LOCATION: 1;1                         ACCESS: Direct Global Read & w/Fileman
 GENERAL DESCRIPTION:   This will enable users to read the 0- and 1- nodes
 directly, reading the main fields of the ICD OPERATION/PROCEDURE FILE.  The
 0-node may be read in its entirety into a local variable.  The fields may be 
 accessed by direct reads of the global, or by FileMan reads.  
  
 Also, the "BA" cross-reference may be used to find the code reference.  
  
 Direct read of the "ACT" cross-reference will also be permitted.  
  STATUS: Retired                       EXPIRATION DATE: NOV 15, 2008

NUMBER: 10084                           IA #: 10084
  FILE NUMBER: 81                       GLOBAL ROOT: ICPT(
  DATE CREATED: APR 01, 2003            CUSTODIAL PACKAGE: CPT/HCPCS CODES
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: File                            NAME: CPT FILE
  ORIGINAL NUMBER: 10084                ID: ICPT(
GLOBAL REFERENCE: ICPT(D0,0)
FIELD NUMBER: .01                       FIELD NAME: CPT CODE
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 2                         FIELD NAME: SHORT NAME
  LOCATION: 0;2                         ACCESS: Direct Global Read & w/Fileman
FIELD NUMBER: 5                         FIELD NAME: INACTIVE FLAG
  LOCATION: 0;4                         ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ICPT(D0,D
FIELD NUMBER: 50                        FIELD NAME: DESCRIPTION
  LOCATION: D                           ACCESS: Direct Global Read & w/Fileman
GLOBAL REFERENCE: ICPT(B,
 GLOBAL DESCRIPTION:   Cross-reference on .01 field.  
 GENERAL DESCRIPTION:   
  ***Note:  This reference has been replaced by the Supported calls 
  ***  found in DBIAs 1995, 1996, 1997.  
  
  *** THIS WILL BE INACTIVATED AS OF 6/1/2000, AND SHOULD NOT BE USED.  
  *** ALL DIRECT REFERENCES TO THE CPT (#81) FILE MUST BE REPLACED 
  *** WITH THE SUPPORTED CALLS NOTED ABOVE.  
                                   
  
 This will enable users to directly read the 0-node of the CPT file (^ICPT) 
 into a local variable, for access to all fields therein.  
  
 Direct reference of the "B" cross-reference will also be permitted.  
  
 Direct read of the "ACT" cross-reference will also be permitted.  
  
 In addition, the "D"-nodes may be directly read, for access to the 
 description.  
  
 Access is available by direct read or FileMan read, as well as by retrieval of
 the 0-node, for CPT information retrieval.  
  
  
 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  
      N O T I C E !!!!!!!! 
  
 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  
 This IA will be retired as of June 2000 ! Use instead:  IAs 2815 and 2816 
  STATUS: Retired                       EXPIRATION DATE: JUN 01, 2000

NUMBER: 10085                           IA #: 10085
  CUSTODIAL PACKAGE: IFCAP              CUSTODIAL ISC: Washington
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: PRCPUSA
  NAME: PRCPUSA                         ORIGINAL NUMBER: 10085
  ID: PRCPUSA                           STATUS: Active
  EXPIRATION DATE: JAN 01, 1995
COMPONENT/ENTRY POINT: PRCPUSA
 COMPONENT DESCRIPTION:   PRCPUSA - UTILITY PROGRAM TO UPDATE INTERNAL USAGE
 HISTORY FROM VARIABLES 
  
   THIS IS A UTLIITY PROGRAM THAT CAN BE CALLED BY ANY SYSTEM THAT WISHES TO
 USE THEIR OWN PROGRAMS FOR SOME FUNCTIONS THAT WOULD AFFECT THE INVENTORY 
 LEVEL, BUT WISH TO USE THE GENERAL INVENTORY/DISTRIBUTION SYSTEM FOR OTHER 
 INVENTORY FUNCTIONS.  
  
 *** THE FOLLOWING VARIABLES ARE EXPECTED *** 
  
 PRCP("I")=RECORD NUMBER OF THE INVENTORY POINT TO BE UPDATED (TOP LEVEL ON 
 FILE 445) 
  
 PRCP("ITEM")=POINTER TO ITEM MASTER FILE (441) 
  
 PRCP("QTY")=QUANTITY TO AFFECT INVENTORY. NOTE: A PLUS QTY.WILL BE ADDED, A 
 MINUS WILL BE SUBTRACTED.  
  
 PRCP("TYP")=CODE INDICATING TYPE OF TRANSACTION 
  'RC'=RECEIVING  'R'=NORMAL DISTRIBUTION 'C'=CALL-IN DISTRIBUTION 'U'=IN-HOUSE
 OR PATIENT USAGE 'A'=MANUAL ADJUSTMENT TO INVENTORY 
  
 PRCP("COM")=THIS FIELD IS OPTIONAL.  IF PROVIDED, IT IS A FREE TEXT COMMENT 
 (1-80 CHAR.) EXPLAINING THE INVENTORY TRANSACTION.  
  
  
 **NOTE** SUCCESSFUL UPDATE WILL KILL ALL 'PRCP' VARIABLES.  UNSUCCESSFUL WILL
 LEAVE ALL VARIABLES AND ERROR MESSAGE IN 'X'.  

NUMBER: 10086                           IA #: 10086
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: %ZIS
  NAME: %ZIS                            ORIGINAL NUMBER: 10086
  ID: %ZIS                              STATUS: Active
COMPONENT/ENTRY POINT: %ZIS
 COMPONENT DESCRIPTION:   Standard device call 
COMPONENT/ENTRY POINT: HOME
 COMPONENT DESCRIPTION:   Return 'HOME' device characteristics 
COMPONENT/ENTRY POINT: HLP1
 COMPONENT DESCRIPTION:   Display Brief Help 
COMPONENT/ENTRY POINT: HLP2
 COMPONENT DESCRIPTION:   Display Help Frames 
COMPONENT/ENTRY POINT: $$REWIND
 COMPONENT DESCRIPTION:   Rewind Sequential tape devices 

NUMBER: 10087                           IA #: 10087
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  ROUTINE: %ZIS9                        NAME: %ZIS9
  ORIGINAL NUMBER: 10087                ID: %ZIS9
  STATUS: Retired
COMPONENT/ENTRY POINT: %ZIS9
 COMPONENT DESCRIPTION:   Obsolete and will be removed after May '92.  

NUMBER: 10088                           IA #: 10088
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: %ZISS
  NAME: %ZISS                           ORIGINAL NUMBER: 10088
  ID: %ZISS                             STATUS: Active
COMPONENT/ENTRY POINT: KILL
 COMPONENT DESCRIPTION:   Kill Screen Parameters 
COMPONENT/ENTRY POINT: ENS
 COMPONENT DESCRIPTION:   Collect Screen Parameters 
COMPONENT/ENTRY POINT: ENDR
 COMPONENT DESCRIPTION:   Collect Screen Parameters 
COMPONENT/ENTRY POINT: GKILL
 COMPONENT DESCRIPTION:   Kill Graphic Parameters 
COMPONENT/ENTRY POINT: GSET
 COMPONENT DESCRIPTION:   Collect Graphic Parameters 

NUMBER: 10089                           IA #: 10089
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: %ZISC
  NAME: %ZISC                           ORIGINAL NUMBER: 10089
  ID: %ZISC                             STATUS: Active
COMPONENT/ENTRY POINT: %ZISC
 COMPONENT DESCRIPTION:   Close the device Prefered close logic over X
 ^%ZIS("C").  
VARIABLES: IO('C')                      TYPE: Input
 VARIABLES DESCRIPTION:   Set to null.  Close the current device even if it is
 the primary device.  Optional.  

NUMBER: 10090                           IA #: 10090
  FILE NUMBER: 4                        GLOBAL ROOT: DIC(4,
  DATE CREATED: OCT 24, 1994            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: INSTITUTION FILE                ORIGINAL NUMBER: 10090
  ID: DIC(4,
GLOBAL REFERENCE: DIC(4,...
FIELD NUMBER: ENTIRE FILE               ACCESS: Read w/Fileman
  STATUS: Active

NUMBER: 10091                           IA #: 10091
  FILE NUMBER: 4.3                      GLOBAL ROOT: XMB(1,
  DATE CREATED: JUN 23, 1999            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: MAILMAN SITE PARAMETERS         ORIGINAL NUMBER: 10091
  ID: XMB(1,
GLOBAL REFERENCE: XMB(1,D0,'XUS')
FIELD NUMBER: 217                       FIELD NAME: DEFAULT INSTITUTION
  LOCATION: XUS;17                      ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   The field is used to define the default institution for
 the local site.  Developers may get this data directly from the file.  The
 entry is a pointer to file 4, Institution, and is the 17th piece of 
 ^XMB(1,1,"XUS").  
  STATUS: Active

NUMBER: 10092                           IA #: 10092
  CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING
  CUSTODIAL ISC: Salt Lake City         USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: Routine                      NAME: Routine
  ORIGINAL NUMBER: 10092                ID: Routine
  STATUS: Active
COMPONENT/ENTRY POINT: ORVOM
 COMPONENT DESCRIPTION:   Export utility for distributing package-specific
 protocols.  Requires entries in the Order Parameters File.  (Available for use
 till DIFROM incorporates this functionality) 

NUMBER: 10093                           IA #: 10093
  FILE NUMBER: 49                       GLOBAL ROOT: DIC(49,
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: SERVICE/SECTION FILE
  ORIGINAL NUMBER: 10093                ID: DIC(49,
GLOBAL REFERENCE: DIC(49,...
FIELD NUMBER: All fields                ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Write access if authorized through local IRM.  
  STATUS: Active

NUMBER: 10094                           IA #: 10094
  CUSTODIAL PACKAGE: TOOLKIT            CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XTFN
  NAME: XTFN                            ORIGINAL NUMBER: 10094
  ID: XTFN                              STATUS: Active
COMPONENT/ENTRY POINT: COS
COMPONENT/ENTRY POINT: DTR
COMPONENT/ENTRY POINT: EXP
COMPONENT/ENTRY POINT: LN
COMPONENT/ENTRY POINT: LOG
COMPONENT/ENTRY POINT: PI
COMPONENT/ENTRY POINT: PWR
COMPONENT/ENTRY POINT: RTD
COMPONENT/ENTRY POINT: SD
COMPONENT/ENTRY POINT: SIN
COMPONENT/ENTRY POINT: SQRT
COMPONENT/ENTRY POINT: TAN

NUMBER: 10095                           IA #: 10095
  CUSTODIAL PACKAGE: TOOLKIT            CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XTKERMIT
  NAME: XTKERMIT                        ORIGINAL NUMBER: 10095
  ID: XTKERMIT                          STATUS: Active
COMPONENT/ENTRY POINT: SEND
 COMPONENT DESCRIPTION:   
          ;To call from outside on KERMIT 
          ;set XTKDIC = fileman type global root, 
          ;DWLC = last current data node 
          ;Return DWLC = last data node, XTKDIC is killed.  
          ;Optional 
          ;set XTKMODE = 0 to send/receive in Image mode (no conversion) 
          ;    1 to send/receive in DATA mode (just convert control char) 
          ;    2 to send/receive as TEXT (FM word-processing).  
          ;Text mode sends a CR after each global node 
          ;     makes a new global node for each CR received.  
          ;XTKMODE = 2 would be normal for most DHCP applications.  
COMPONENT/ENTRY POINT: RECEIVE
 COMPONENT DESCRIPTION:   
          ;To call from outside on KERMIT 
          ;set XTKDIC = fileman type global root, 
          ;DWLC = last current data node 
          ;Return DWLC = last data node, XTKDIC is killed.  
          ;Optional 
          ;set XTKMODE = 0 to send/receive in Image mode (no conversion) 
          ;    1 to send/receive in DATA mode (just convert control char) 
          ;    2 to send/receive as TEXT (FM word-processing).  
          ;Text mode sends a CR after each global node 
          ;     makes a new global node for each CR received.  
          ;XTKMODE = 2 would be normal for most DHCP applications.  

NUMBER: 10096                           IA #: 10096
  GLOBAL ROOT: %ZOSF(                   CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: Z OPERATING SYSTEM FILE         ORIGINAL NUMBER: 10096
  ID: %ZOSF(
 GENERAL DESCRIPTION:   All nodes exported by Kernel are useable.  
  STATUS: Active

NUMBER: 10097                           IA #: 10097
  DATE CREATED: JUN 29, 1999            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: %ZOSV                        NAME: %ZOSV
  ORIGINAL NUMBER: 10097                ID: %ZOSV
 GENERAL DESCRIPTION:   This routine is OS specific, and provides a interface
 to OS functions.  
  STATUS: Active
COMPONENT/ENTRY POINT: GETENV
 COMPONENT DESCRIPTION:   Display Environment Information (in Tools chapter) 
COMPONENT/ENTRY POINT: T0
 COMPONENT DESCRIPTION:   Start RT Measure (in Tools chapter) 
COMPONENT/ENTRY POINT: T1
 COMPONENT DESCRIPTION:   Stop RT Measure (in Tools chapter) 
COMPONENT/ENTRY POINT: LOGRSRC
COMPONENT/ENTRY POINT: $$LGR
 COMPONENT DESCRIPTION:   Get last global reference 
COMPONENT/ENTRY POINT: $$EC
 COMPONENT DESCRIPTION:   Get error code.  
COMPONENT/ENTRY POINT: SETNM(name)
 COMPONENT DESCRIPTION:   This entry point is just a parameter passing version
 of SETENV^%ZOSV.  It only has meaning on DSM for VMS system, otherwise it just
 quits.  
VARIABLES: name                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a 1--15 char name to be given to the process
 at the VMS level. 
COMPONENT/ENTRY POINT: SETENV
 COMPONENT DESCRIPTION:   It only has meaning on DSM for VMS system, otherwise
 it just quits.  It sets the VMS process name.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   This is a 1-15 char name to be given to the process
 at the VMS level.  
COMPONENT/ENTRY POINT: $$ACTJ
 COMPONENT DESCRIPTION:   Returns the number of active jobs in the scope of
 this process.  The same as ^%ZOSF("ACTJ").  
COMPONENT/ENTRY POINT: $$AVJ
 COMPONENT DESCRIPTION:   Returns a best effort on the number of available
 jobs. The number of new jobs that could be started.  The same as
 ^%ZOSF("AVJ").  
COMPONENT/ENTRY POINT: $$VERSION([flag])
 COMPONENT DESCRIPTION:   Use $$VERSION^%ZOSV([flag]) to return the Mumps
 system version number or name.  
  
 In days of old, the Mumps implementation was both the Mumps language and the
 operating system.  That is why in old documentation it is referred to as the
 OS.  
VARIABLES: flag                         TYPE: Input
 VARIABLES DESCRIPTION:   [optional] If you pass a value of 1, the Mumps system
 name is returned instead of the version number.  Note that the name is as
 defined by the Mumps vendor and doesn't necessarily correspond with the OS
 name stored in ^%ZOSF("OS").  
VARIABLES: return                       TYPE: Output
 VARIABLES DESCRIPTION:   The Mumps system version number or name depending on
 optional first parameter.  
COMPONENT/ENTRY POINT: $$OS
 COMPONENT DESCRIPTION:   This function returns the underlying operating system
 such as VMS, UNIX or NT.  It is only fully developed for Cache/OpenM system.  
 See ICR 3522 for more details.  
  DATE ACTIVATED: JUL 06, 2009

NUMBER: 10098                           IA #: 10098
  CUSTODIAL PACKAGE: NEW PERSON         CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Other
  DBIC APPROVAL STATUS: APPROVED        NAME: see Veterans Administration
  ORIGINAL NUMBER: 10098                STATUS: Active

NUMBER: 10099                           IA #: 10099
  DATE CREATED: FEB 08, 1996
  CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING
  CUSTODIAL ISC: Salt Lake City         USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: GMRADPT                      NAME: GMRADPT
  ORIGINAL NUMBER: 10099                ID: GMRADPT
 GENERAL DESCRIPTION:   This integration agreement documents a data extract
 utility which allows other packages to gather adverse reaction data about a
 patient for use in the calling package.  
  STATUS: Active
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   **NOTE: New subscribers of this agreement should use
 the EN2 component.  Existing subscribers should make changes to use the EN2
 component instead of this component as the EN2 component returns more data.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The Internal Entry Number (IEN) of the patient in the
 PATIENT file (#2).  
VARIABLES: GMRA                         TYPE: Input
 VARIABLES DESCRIPTION:   This GMRA variable is optional. The default value is
 "0^0^111" which means return "all reactions (allergic/non-allergic)^all data
 (verified or non verified)^all food, drug and other type reactions".  
  
 GMRA must be in the format A^B^C 
         if A = 0 return all reactions 
                  (allergic/non-allergic).  
                1 return allergies only.  
                2 return non-allergies only.  
            B = 0 return all data (verified or 
                  non-verified).  
                1 return only verified data.  
                2 return only non-verified data.  
            C = X_Y_Z 
                where X, Y, and Z are either 0 or 
                1.  1 would mean to return an 
                Adverse Reaction of that particular 
                type, and zero means do not return 
                an Adverse Reaction of that type.  
                X is for TYPE=OTHER 
                Y is for TYPE=FOOD 
                Z is for TYPE=DRUG.  
                E.g., 001 (return drug only), 111 
                (returns all types), and 010 
                (returns food only).  
VARIABLES: GMRAL                        TYPE: Output
 VARIABLES DESCRIPTION:   The GMRAL variable and GMRAL array are returned as
 output.  
  
 GMRAL = 1 if the patient has an Adverse Reaction 
         0 if the patient has no known Adverse 
           Reaction 
         null if the patient has not been asked 
              about Adverse Reaction 
  
 GMRAL(PTR TO File #120.8) = A^B^C^D^E^F^G^H^I 
     where A = Pointer to Patient file.  
           B = Free text of the causative agent.  
          *C = Type of reaction, where D is drug, F 
               is food, and O is other.  
           D = 1 if the Adverse Reaction has been 
                 verified 
               0 if the Adverse Reaction has not 
                 been verified 
           E = 0 if this is an allergic reaction 
               1 if this is not an allergic 
                 reaction 
         **F = the mechanism of reaction in the 
               format: 
               External format;Internal format 
               (ALLERGY;0, PHARMACOLOGIC;2, 
               UNKNOWN;U).  
           G = Type of reaction.  
                 D = drug 
                DF = drug/food 
               DFO = drug/food/other 
                DO = drug/other 
                 F = food 
                FO = food/other 
                 O = other 
           H = the mechanism of reaction in the 
               format: 
               External format;Internal format 
               (ALLERGY;A, PHARMACOLGIC;P, 
               UNKNOWN;U) 
           I = variable pointer to the causative 
               agent returned in piece B 
  GMRAL(PTR TO File #120.8,"S",COUNT) = S 
     where COUNT = number 1 to number of 
     signs/symptoms for this reaction.  
               S = a sign/symptom for this reaction 
                   in the format: 
                   External format;Internal format 
  
   * NOTE: This piece will no longer be supported 
           after 9/1/97, please use piece G.  
  ** NOTE: This piece will no longer be supported 
           after 9/1/97, please use piece H.  
COMPONENT/ENTRY POINT: EN2
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   The Internal Entry Number (IEN) of the patient in the
 PATIENT file (#2).  
VARIABLES: GMRA                         TYPE: Input
 VARIABLES DESCRIPTION:   An optional parameter specifying the types of
 reactions to return. This is formatted as a caret-delimited string with five
 pieces: 
  Piece   Criteria 
 ==================================================
  1       Allergies, Non-Allergies, or Both 
          0 (Default) for both 
          1 for allergies only 
          2 for non-allergies only 
  2       Verified, Non-Verified, or Both 
          0 (Default) for both 
          1 for verified data only 
          2 for non-verified data only 
  3       Reaction Type 
          Three digit number where each digit is 
          either a one or a zero. Default value is 
          "111". If the digit is a one, return 
          reactions of that type. If the digit is 
          a zero, do not return reactions of that 
          type.  
           Digit  Reaction Type 
          =====================
           1      OTHER 
           2      FOOD 
           3      DRUG 
  4       Reaction Documentation Site Type 
          0 (Default) for locally documented 
            reactions only 
          1 for locally and remotely documented 
            reactions 
  5       Entered in Error Reactions 
          0 (Default) to exclude reactions entered 
            in error 
          1 to include reactions entered in error 
VARIABLES: GMRAL                        TYPE: Output
 VARIABLES DESCRIPTION:   GMRAL = Empty string if the patient is not 
         assessed 
         0 if the patient has no known adverse 
           reactions 
         1 if the patient has an adverse reaction GMRAL(PTR)=Caret-delimited
 string 
   PTR - for local reactions, the IEN in the 
         PATIENT ALLERGIES file (#120.8) and for 
         remote reactions, "R" followed by the 
         reaction's number in the 
         ^XTMP("ORRDI","ART",DFN) global (DFN is 
         the patient's internal entry number in the 
         PATIENT file, #2).  
   Caret-delimited string: 
   Piece   Value 
   ==================================================
    1      Internal format of the PATIENT field 
           (#.01) in the PATIENT ALLERGIES file 
           (#120.8) 
    2      REACTANT field (#.02) in the PATIENT 
           ALLERGIES file (#120.8) 
    3      Not supported; use piece seven 
    4      Internal format of the VERIFIED field 
           (#19) in the PATIENT ALLERGIES file 
           (#120.8) 
    5      Allergy or Non-Allergy 
           1 for allergy 
           0 for non-allergy 
    6      Not supported; use piece eight 
    7      Internal format of the ALLERGY TYPE 
           field (#3.1) in the PATIENT ALLERGIES 
           file (#120.8) 
    8      MECHANISM field (#17) in the PATIENT 
           ALLERGIES file (#120.8) 
           The first semi-colon piece is the 
           external format and the second semi- 
           colon piece is the internal format.  
    9      Internal format of the GMR ALLERGY field 
           (#1) in the PATIENT ALLERGIES file 
           (#120.8) 
    10     OBSERVED/HISTORICAL field (#6) in the 
           PATIENT ALLERGIES file (#120.8) 
           The first semi-colon piece is the 
           external format and the second semi- 
           colon piece is the internal format.  
 GMRAL(PTR,"O",COUNT)=Caret-delimited string 
   COUNT - starts at one for the first 
           observation and increments by one 
           for subsequent observations 
   Caret-delimited string: 
   For those pieces that contain sub-fields, the 
   sub-fields are separated by ";".  
   Piece   Value 
   ==================================================
    1      SEVERITY field (#14.5) in the ADVERSE 
           REACTION REPORTING file (#120.85) 
           Sub-Field 1: External format 
           Sub-Field 2: Internal format 
    2      DATE/TIME OF EVENT field (#.01) in the 
           ADVERSE REACTION REPORTING file 
           (#120.85) 
           Sub-Field 1: External format 
           Sub-Field 2: Internal format GMRAL(PTR,"S",COUNT)=Caret-delimited
 string 
   COUNT - starts at one for the first sign or 
           symptom and increments by one for 
           subsequent signs or symptoms 
   Caret-delimited string: 
   For those pieces that contain sub-fields, the 
   sub-fields are separated by ";".  
   Piece   Value 
   ==================================================
    1      REACTION sub-field (#.01) in the 
           REACTIONS field (#10) in the PATIENT 
           ALLERGIES file (#120.8) 
           Sub-Field 1: External format 
           Sub-Field 2: Internal format 
    2      DATE ENTERED sub-field (#.01) in the 
           REACTIONS field (#10) in the PATIENT 
           ALLERGIES file (#120.8) 
           Sub-Field 1: External format 
           Sub-Field 2: Internal format GMRAL(PTR,"ERROR")=DATE/TIME ENTERED IN
 ERROR 
                    field (#23) in the PATIENT 
                    ALLERGIES file (#120.9) 
                    Sub-Field 1: External format 
                    Sub-Field 2: Internal format 
   NOTE: The sub-fields are separated by ";".  
         Only reactions documented at the local 
         site (PTR is all numeric) will have the 
         "ERROR" node defined.  GMRAL(PTR,"SITE")=Caret-delimited string 
   The site the documented this reaction.  
   NOTE: Only reactions documented at a remote site 
         (PTR will begin with "R") will have the 
         "SITE" node defined.  
   Caret-delimited string: 
   Piece   Value 
   ==================================================
    1      IEN in the INSTITUTION file (#4) 
    2      NAME field (#.01) in the INSTITUTION 
           file (#4) 
    3      STATION NUMBER field (#99) in the 
           INSTITUTION file (#4) 
  DATE ACTIVATED: MAY 20, 2019

NUMBER: 10100                           IA #: 10100
  FILE NUMBER: 730                      GLOBAL ROOT: ECC(730,
  CUSTODIAL PACKAGE: EVENT CAPTURE      USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: NATIONAL SERVICE FILE           ORIGINAL NUMBER: 10100
  ID: ECC(730,
GLOBAL REFERENCE: ECC(730,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Direct Global Read & w/Fileman
  STATUS: Active

NUMBER: 10101                           IA #: 10101
  DATE CREATED: MAR 07, 1994            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XQOR                         NAME: XQOR
  ORIGINAL NUMBER: 10101                ID: XQOR
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This is the main routine for navigating protocols. 
 The routine processes the initial protocol and the subordinate protocols. 
 This processing of subordinate protocols happens according to the type of
 protocol and the navigation variables that get set along the way.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   Identifies the initial protocol that EN^XQOR should
 process.  X should be in variable pointer format.  For example,
 X="1234;ORD(101," would cause the processing to start with the protocol that
 has an internal entry number of 1234.  
  
 An alternative to using variable pointer format is to set X equal to the name
 or number of the protocol and DIC equal to the number or global reference of
 the file you are working in (generally the Protocol file (101)).  
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   This entry point is identical to EN^XQOR, except that
 the entry and exit actions of the initial protocol are not executed.  This
 entry point provides backwards compatibility with the way Kernel 6 processed
 protocols that were defined in the Option file.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   See description for EN^XQOR.  
COMPONENT/ENTRY POINT: MSG(PROTOCOL,.MSGTEXT)
 COMPONENT DESCRIPTION:   This entry point is used to enable HL7 messaging
 through the XQOR unwinder.  
VARIABLES: PROTOCOL                     TYPE: Input
 VARIABLES DESCRIPTION:   The name of the protocol the HL7 message will be
 associated with.  
VARIABLES: MSGTEXT                      TYPE: Input
 VARIABLES DESCRIPTION:   The array containing the HL7 message.  

NUMBER: 10102                           IA #: 10102
  DATE CREATED: MAR 07, 1994            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XQORM1                       NAME: XQORM1
  ORIGINAL NUMBER: 10102                ID: XQORM1
  STATUS: Active
COMPONENT/ENTRY POINT: DISP
 COMPONENT DESCRIPTION:   If you have replaced the standard help by setting
 XQORM("??"), the menu selections may be displayed from you help code by
 calling DISP^XQORM1 with X="?" 
  
 DISP^XQORM1 should only be called from within the code used by XQORM("??").  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   Must be "?".  

NUMBER: 10103                           IA #: 10103
  DATE CREATED: NOV 27, 2000            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XLFDT                        NAME: XLFDT
  ORIGINAL NUMBER: 10103                ID: XLFDT
 GENERAL DESCRIPTION:   Several date/time API's.  
  STATUS: Active
KEYWORDS: DATE
COMPONENT/ENTRY POINT: $$HTFM(x,y)
 COMPONENT DESCRIPTION:   To change a date from $H format to VA FileMan format. 
  
  arguments:  x  $H date (in quotes) 
              y  1 (optional) to return the date portion only (no seconds) 
COMPONENT/ENTRY POINT: $$FMTH(x,y)
 COMPONENT DESCRIPTION:   To change a date from VA FileMan format to $H format. 
  
  arguments:  x  FileMan date 
              y  1 (optional) to return the date portion only (no seconds) 
COMPONENT/ENTRY POINT: $$HTE(x,y)
 COMPONENT DESCRIPTION:   To change a date in $H format to an external format 
  
  arguments:  x  $H date (in quotes) 
              y  see FMTE(x,y) for alternate values 
COMPONENT/ENTRY POINT: $$FMTE(x,y)
 COMPONENT DESCRIPTION:   To change a date in VA FileMan format to an external
 format.  
COMPONENT/ENTRY POINT: $$DOW(x,y)
 COMPONENT DESCRIPTION:   To change a date in VA FileMan format to the
 corresponding day of the week.  
COMPONENT/ENTRY POINT: $$HDIFF(x1,x2,x3)
 COMPONENT DESCRIPTION:   To calculate the difference between two dates in $H
 format.  
COMPONENT/ENTRY POINT: $$FMDIFF(x1,x2,x3)
 COMPONENT DESCRIPTION:   To calculate the difference between two dates in VA
 FileMan format.  x3 also serves as an argument 
  1, return difference in days 
  2, return difference in seconds 
  3, return difference in DD HH:MM:SS format 
COMPONENT/ENTRY POINT: $$HADD(x,d,h,m,s)
 COMPONENT DESCRIPTION:   To add days, hours, minutes, and seconds to a date in
 $H format (to x) 
COMPONENT/ENTRY POINT: $$FMADD(x,d,h,m,s)
 COMPONENT DESCRIPTION:   To add days, hours, minutes, and seconds to a
 date/time in VA FileMan format (to x).  
COMPONENT/ENTRY POINT: $$DT
 COMPONENT DESCRIPTION:   Returns current date in FileMan format.  
COMPONENT/ENTRY POINT: $$NOW
 COMPONENT DESCRIPTION:   Returns current date/time in FileMan format.  
COMPONENT/ENTRY POINT: $$FMTHL7(fm_date/time)
 COMPONENT DESCRIPTION:   To change a date from VA FileMan format to HL7 format
 including the time offset.  
  
 W $$FMTHL7^XLFDT(3001127.1525)  => 200011271525-0800 
COMPONENT/ENTRY POINT: $$HL7TFM(HL7 date/time[,Local/UTC])
 COMPONENT DESCRIPTION:   To change a date from HL7 format to VA FileMan
 format.  W $$HL7TFM^XLFDT("200011271525-0700") => 3001127.1525 
  
 The optional second parameter controls if any time offset is applied to the
 time. If a time offset is included then time offset can be applied to give UTC
 time or the local time offset from the Mailman Time Zone file can be used to
 give Local time.  
  
 To get UTC time W $$HL7TFM^XLFDT("200011271525-0700","U") => 3001127.2225 
  
 To get Local time in PST.  W $$HL7TFM^XLFDT("200011271525-0700","L") =>
 3001127.1425 
COMPONENT/ENTRY POINT: $$SCH(schedule,lasttime,futureflag)
 COMPONENT DESCRIPTION:   This API decodes a schedule to give the next time in
 the schedule.  See the Kernel Library documentation for more detail on the
 schedule string.  The return value is a FileMan format date/time.  
VARIABLES: schedule                     TYPE: Input
 VARIABLES DESCRIPTION:   This is a string that describes the schedule.  From
 the Kernel Library Doc.  
  
         nS      add n seconds to base_date 
         nH      add n hours to base_date 
         nD      add n days to base_date 
         nM      add n months to base_date 
         $H;$H;$H        List of $H dates 
         nM(list)        complex month increment ie: 1M(15,L) 
                 dd[@time]               day of month ie: 12 
                 nDay[@time]     day of week in month  ie: 1M 
                                         first monday 
                 Day 
                 L                       last day of month 
                 LDay                    ie: LW   last wednesday of month 
  
         Day[@time]...  
                 Day 
                 D = weekday 
                 E = weekend 
  
         Day =   M monday 
                 T tuesday 
                 W wednesday 
                 R thursday 
                 F friday 
                 S saturday 
                 U sunday 
VARIABLES: lasttime                     TYPE: Input
 VARIABLES DESCRIPTION:   This is the last date/time (or base time) for the
 schedule. The next date/time is figured from this point in time. It can be in
 FileMan format e.g. 3011018.08 or in $H format e.g. 58730,28800.  
VARIABLES: futureflag                   TYPE: Input
 VARIABLES DESCRIPTION:   This flag, if set to 1, will check that the returned
 date/time is greater than the current date/time.  
COMPONENT/ENTRY POINT: $$SEC(FM or $H value)
 COMPONENT DESCRIPTION:   This entry point will convert either a FM or $H value
 to the number of seconds since the start for $H.  W $$SEC^XLFDT(3021118.1347)
 =>> 5108536020 
COMPONENT/ENTRY POINT: $$%H(seconds)
 COMPONENT DESCRIPTION:   This entry point converts the output of $$SEC^XLFDT
 back to a $H value.  
  
 W $$%H^XLFDT(5108536020) =>> 59126,49620 
COMPONENT/ENTRY POINT: $$TZ()
 COMPONENT DESCRIPTION:   This entry point returns the Time Zone offset from
 UTC.  
  
 For Pacific standard time: W $$TZ^XLFDT =>> -0800 
COMPONENT/ENTRY POINT: $$FR(x)
 COMPONENT DESCRIPTION:   Checks x (FileMan date/time) is within the approved
 range.  Returns 0 if x is approved, 1 if x is out of range.  
VARIABLES: x                            TYPE: Input
 VARIABLES DESCRIPTION:   Internal format of FileMan date/time 

NUMBER: 10104                           IA #: 10104
  DATE CREATED: JUL 30, 2001            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XLFSTR                       NAME: XLFSTR
  ORIGINAL NUMBER: 10104                ID: XLFSTR
  STATUS: Active
COMPONENT/ENTRY POINT: $$UP(x)
 COMPONENT DESCRIPTION:   To convert the string in x to all uppercase letters.  
COMPONENT/ENTRY POINT: $$LOW(x)
 COMPONENT DESCRIPTION:   To convert the string in x to all lowercase letters.  
COMPONENT/ENTRY POINT: $$STRIP(x,y)
 COMPONENT DESCRIPTION:   To strip all instances of character y in string x.  
COMPONENT/ENTRY POINT: $$REPEAT(x,y)
 COMPONENT DESCRIPTION:   To repeat the value of x for y number of times.  
COMPONENT/ENTRY POINT: $$INVERT(x)
 COMPONENT DESCRIPTION:   To invert the order of characters in a string.  
COMPONENT/ENTRY POINT: $$REPLACE(in,spec)
 COMPONENT DESCRIPTION:   Uses a Multi character $TRanslate to replace
 specified strings.  
COMPONENT/ENTRY POINT: $$LJ(s,i,p)
 COMPONENT DESCRIPTION:   Left Justify 
COMPONENT/ENTRY POINT: $$RJ(s,i,p)
 COMPONENT DESCRIPTION:   Right Justify 
COMPONENT/ENTRY POINT: $$CJ(s,i,p)
 COMPONENT DESCRIPTION:   Center Justify 
COMPONENT/ENTRY POINT: $$TRIM(s,f,c)
 COMPONENT DESCRIPTION:   $$TRIM^XLFSTR(s[,"[L][R]"][,char]).  This call will
 trim spaces or other char from the left, right or both sides of a input
 string.  Examples: W "["_$$TRIM^XLFSTR("  A B C  ")_"]" => [A B C] W
 "["_$$TRIM^XLFSTR("//A B C//",,"/")_"]" => [A B C] W "["_$$TRIM^XLFSTR("//A B
 C//","L","/")_"]" => [A B C//] W "["_$$TRIM^XLFSTR("//A B C//","r","/")_"]" =>
 [//A B C] 
VARIABLES: s                            TYPE: Input
 VARIABLES DESCRIPTION:   This is the string to be worked on.  
VARIABLES: f                            TYPE: Input
 VARIABLES DESCRIPTION:   This is an optional flag variable and can have a
 value of "L" to trim characters from the left/beginning of the string.  A
 value of "R" will trim characters from the right/end of the string.  Or it can
 have "LR" to trim both ends.  If this value is not sent it defaults to "LR".  
VARIABLES: c                            TYPE: Input
 VARIABLES DESCRIPTION:   This optional input defaults to a space, It can be
 set to trim another character from the input string.  
COMPONENT/ENTRY POINT: $$TITLE(x)
 COMPONENT DESCRIPTION:   Converts a string x into TITLE CASE format (first
 letter of each word is uppercase).  
  DATE ACTIVATED: AUG 07, 2017

NUMBER: 10105                           IA #: 10105
  CUSTODIAL PACKAGE: KERNEL             CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XLFMTH
  NAME: XLFMTH                          ORIGINAL NUMBER: 10105
  ID: XLFMTH                            STATUS: Active
COMPONENT/ENTRY POINT: $$ABS(%X)
 COMPONENT DESCRIPTION:   Returns the absolute value of the number in %X.  
COMPONENT/ENTRY POINT: $$MIN(%1,%2)
 COMPONENT DESCRIPTION:   Returns the minimum value comparing the number in %1
 with the number in %2.  
COMPONENT/ENTRY POINT: $$MAX(%1,%2)
 COMPONENT DESCRIPTION:   Returns the maximum value comparing the number in %1
 with the number in %2.  
COMPONENT/ENTRY POINT: $$LN(%X)
 COMPONENT DESCRIPTION:   Natural Log 
COMPONENT/ENTRY POINT: $$EXP(%X)
 COMPONENT DESCRIPTION:   To return e to the %X power.  
COMPONENT/ENTRY POINT: $$PWR(%X,%Y)
 COMPONENT DESCRIPTION:   To raise %X to the %Y power.  
COMPONENT/ENTRY POINT: $$LOG(%X)
 COMPONENT DESCRIPTION:   Log base 10 
COMPONENT/ENTRY POINT: $$TAN(%X)
 COMPONENT DESCRIPTION:   Tangent in radians 
COMPONENT/ENTRY POINT: $$SIN(%X)
 COMPONENT DESCRIPTION:   Sine in radians 
COMPONENT/ENTRY POINT: $$COS(%X)
 COMPONENT DESCRIPTION:   Cosine in radians 
COMPONENT/ENTRY POINT: $$DTR(%X)
 COMPONENT DESCRIPTION:   Degrees to radians 
COMPONENT/ENTRY POINT: $$RTD(%X)
 COMPONENT DESCRIPTION:   Radians to degrees 
COMPONENT/ENTRY POINT: $$PI()
 COMPONENT DESCRIPTION:   Returns Pi 
COMPONENT/ENTRY POINT: $$E()
 COMPONENT DESCRIPTION:   Returns e 
COMPONENT/ENTRY POINT: $$SQRT(%X)
 COMPONENT DESCRIPTION:   Square root 
COMPONENT/ENTRY POINT: $$SD(%s1,%s2,%n)
 COMPONENT DESCRIPTION:   Standard Deviation 
COMPONENT/ENTRY POINT: $$TANDEG(X,PR)
 COMPONENT DESCRIPTION:   Tangent in degrees 
COMPONENT/ENTRY POINT: $$SINDEG(X,PR)
 COMPONENT DESCRIPTION:   Sine in degrees 
COMPONENT/ENTRY POINT: $$COSDEG(X,PR)
 COMPONENT DESCRIPTION:   Cosine in degrees 
COMPONENT/ENTRY POINT: $$DMSDEC(X,PR)
 COMPONENT DESCRIPTION:   Degrees:min:sec to decimal 
COMPONENT/ENTRY POINT: $$DECDMS(X,PR)
 COMPONENT DESCRIPTION:   Decimal to degrees:min:sec 
COMPONENT/ENTRY POINT: $$CSCDEG(X,PR)
 COMPONENT DESCRIPTION:   cosecant in degrees 
COMPONENT/ENTRY POINT: $$CSC(X,PR)
 COMPONENT DESCRIPTION:   Cosecant in radians 
COMPONENT/ENTRY POINT: $$SECDEG(X,PR)
 COMPONENT DESCRIPTION:   Secant in degrees 
COMPONENT/ENTRY POINT: $$SEC(x,pr)
 COMPONENT DESCRIPTION:   Secant in radians 
COMPONENT/ENTRY POINT: $$COTDEG(X,PR)
 COMPONENT DESCRIPTION:   Cotangent in degrees 
COMPONENT/ENTRY POINT: $$COT(X,PR)
 COMPONENT DESCRIPTION:   Cotangent in radians 
COMPONENT/ENTRY POINT: $$ASINDEG(X,PR)
 COMPONENT DESCRIPTION:   Arc-tangent in degrees 
COMPONENT/ENTRY POINT: $$ASIN(X,PR)
 COMPONENT DESCRIPTION:   Arc-sine in radians 
COMPONENT/ENTRY POINT: $$ACOSDEG(X,PR)
 COMPONENT DESCRIPTION:   Arc-cosine in degrees 
COMPONENT/ENTRY POINT: $$ACOS(X,PR)
 COMPONENT DESCRIPTION:   Arc-cosine in radians 
COMPONENT/ENTRY POINT: $$ATANDEG(X,PR)
 COMPONENT DESCRIPTION:   Arc-tangent in degrees 
COMPONENT/ENTRY POINT: $$ATAN(X,PR)
 COMPONENT DESCRIPTION:   Arc-tangent in radians 
COMPONENT/ENTRY POINT: $$ACOTDEG(X,PR)
 COMPONENT DESCRIPTION:   Arc-cotangent in degrees 
COMPONENT/ENTRY POINT: $$ACOT(X,PR)
 COMPONENT DESCRIPTION:   Arc-cotangent in radians 
COMPONENT/ENTRY POINT: $$ASECDEG(X,PR)
 COMPONENT DESCRIPTION:   Arc-secant in degrees 
COMPONENT/ENTRY POINT: $$ASEC(X,PR)
 COMPONENT DESCRIPTION:   Arc-secant in radians 
COMPONENT/ENTRY POINT: $$ACSCDEG(X,PR)
 COMPONENT DESCRIPTION:   Arc-cosecant in degrees 
COMPONENT/ENTRY POINT: $$ACSC(X,PR)
 COMPONENT DESCRIPTION:   Arc-cosecant in radians 

NUMBER: 10106                           IA #: 10106
  CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: HLFNC                        NAME: HLFNC
  ORIGINAL NUMBER: 10106                ID: HLFNC
  STATUS: Active
COMPONENT/ENTRY POINT: $$FMDATE
 COMPONENT DESCRIPTION:   Extrinsic function call $$FMDATE^HLFNC(X), converts
 HL7 date, date/time, or time to VA FileMan format.  X required.  
COMPONENT/ENTRY POINT: $$FMNAME
 COMPONENT DESCRIPTION:   Extrinsic function call $$FMNAME^HLFNC(X), converts
 name in HL7 format to a name in DHCP format.  X required.  HLECH (HL7 encoding
 characters) must be defined before calling.  
COMPONENT/ENTRY POINT: $$HLADDR
 COMPONENT DESCRIPTION:   Extrinsic function call $$HLADDR^HLFNC(AD,GL),
 converts address information in DHCP format to HL7 format.  AD & GL required.  
 HLECH (HL7 encoding characters) must be defined before calling.  
COMPONENT/ENTRY POINT: $$HLDATE
 COMPONENT DESCRIPTION:   Extrinsic function call $$HLDATE^HLFNC(X,Y), date
 &/or time from VA FileMan format to HL7.  X required, Y optional.  
COMPONENT/ENTRY POINT: $$HLNAME
 COMPONENT DESCRIPTION:   Extrinsic function call $$HLNAME^HLFNC(X), converts a
 name in DHCP format (e.g., lastname,firstname) to HL7 format.  X required.  
 HLECH (HL7 encoding characters) must be defined before calling.  
COMPONENT/ENTRY POINT: $$HLPHONE
 COMPONENT DESCRIPTION:   Extrinsic function call $$HLPHONE^HLFNC(X,B,C),
 converts a phone number from DHCP format to HL7.  X requred, B & C optional.  
COMPONENT/ENTRY POINT: $$M10
 COMPONENT DESCRIPTION:   Extrinsic function call $$M10^HLFNC(X), calculates
 checksum using the M10 algorithm.  HLECH (HL7 encoding characters) required, X
 required.  
COMPONENT/ENTRY POINT: $$M11
 COMPONENT DESCRIPTION:   Extrinsic function call $$M10^HLFNC(X), calculates
 checksum using the M11 algorithm.  HLECH (HL7 encoding characters) required, X
 required.  
COMPONENT/ENTRY POINT: $$UPPER
 COMPONENT DESCRIPTION:   Extrinsic function call $$UPPER^HLFNC(X), converts
 lower to uppercase.  X required.  

NUMBER: 10107                           IA #: 10107
  CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: HLFNC1                       NAME: HLFNC1
  ORIGINAL NUMBER: 10107                ID: HLFNC1
  STATUS: Active
COMPONENT/ENTRY POINT: $$BHS
 COMPONENT DESCRIPTION:   Extrinsic function call
 $$BHS^HLFNC1(HLMTN,HLSEC,HLMSA), builds HL7 Batch Header (BHS) segment.  HLMTN
 and all variables created by INIT^HLTRANS are required.  HLSEC & HLMSA are
 optional.  
COMPONENT/ENTRY POINT: $$HLFLDS
 COMPONENT DESCRIPTION:   Extrinsic function call $$HLFLDS^HLFNC1(APP,SEG),
 returns HL7 fields used for a specified HL7 segment.  APP & SEG required.  
COMPONENT/ENTRY POINT: $$MSH
 COMPONENT DESCRIPTION:   Extrinsic function call $$MSH^FLFNC1(HLMTN,HLSEC),
 builds an HL7 Message Header (MSH) segment.  HLMTN and all variables created
 by INIT^HLTRANS are required.  HLSEC optional.  

NUMBER: 10108                           IA #: 10108
  DATE CREATED: OCT 05, 2001            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: HLTF                         NAME: HLTF
  ORIGINAL NUMBER: 10108                ID: HLTF
  STATUS: Active
COMPONENT/ENTRY POINT: FILE
 COMPONENT DESCRIPTION:   Creates an entry to track delivery of an HL7 message. 
 No input variables.  HLDA, HLDT, HLDT1 are output variables.  
COMPONENT/ENTRY POINT: CREATE
 COMPONENT DESCRIPTION:   Use this call to create a message stub for the batch
 message and reserve a batch message id. If you are creating a batch of HL7
 messages (more than one), your application processing routine should: 
  
   1. Call INIT^HLFNC2 to initialize variables.  
   2. Call CREATE^HLTF to create a message stub for the batch message.  
   3. Create and store each message that will be in the batch (requires 
      calls to INIT^HLFNC2 and MSH^HLFNC2).  
   4. Transmit the completed batch message using GENERATE^HLMA.  
  
 If you are sending only one HL7 message (i.e., you're not sending a batch 
 message), don't call this entry point. For single messages, VISTA HL7 creates
 the MSH segment for you.  
  
   Usage CREATE^HLTF(.HLMID,.MTIEN,.HLDT,.HLDT1) 
VARIABLES: HLMID                        TYPE: Both
 VARIABLES DESCRIPTION:   The variable in which to return the batch message ID. 
 
VARIABLES: MTIEN                        TYPE: Output
 VARIABLES DESCRIPTION:   The parameter in which to return the IEN of the
 message stub in the HL7 Message Text file (#772).  
VARIABLES: HLDT                         TYPE: Both
 VARIABLES DESCRIPTION:   The parameter in which to return the message
 date/time in VA FileMan format.  
VARIABLES: HLDT1                        TYPE: Output
 VARIABLES DESCRIPTION:   The parameter in which to return the message
 date/time in HL7 format.  

NUMBER: 10109                           IA #: 10109
  CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: HLTRANS                      NAME: HLTRANS
  ORIGINAL NUMBER: 10109                ID: HLTRANS
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Sends a single HL7 message.  
  Required input:  HLMTN, HLSDATA local array (or ^TMP("HLS")), and all 
                   INIT^HLTRANS created variables.  
  Optional input:  HLSEC 
  Output variables:  HLERR, only if an error occurs.  
COMPONENT/ENTRY POINT: EN1
 COMPONENT DESCRIPTION:   Same as EN^HLTRANS, except no MSH is created.  
COMPONENT/ENTRY POINT: INIT
 COMPONENT DESCRIPTION:   Initializes basic variables for HL7 message creation. 
 
  Required input:  HLNDAP 
  Output variables:  HLDA, HLDAN, HLDAP, HLDT, HLDT1, HLECH, HLFS, HLNDAP, 
                   HLNDAP0, HLPID, HLQ, HLVER.  HLERR if any error.  
                   HLNDAP reset to internal entry number if HLNDAP was 
                   originally an application name.  
COMPONENT/ENTRY POINT: KILL
 COMPONENT DESCRIPTION:   Kills all variables created by INIT^HLTRANS.  

NUMBER: 10110                           IA #: 10110
  FILE NUMBER: 770                      GLOBAL ROOT: HL(770,'B',
  CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: HL7 NON-DHCP APPLICATION PARAMETER
  ORIGINAL NUMBER: 10110                ID: HL(770,'B',
GLOBAL REFERENCE: HL(770,'B'
 GLOBAL DESCRIPTION:   The "B" cross-reference may be checked.  Pre-approved
 entries may be added to the file.  
 GENERAL DESCRIPTION:   File 770 may be accessed only during package post 
 initialization.  The creation of new entries must be cleared through the HL7
 development team.  New entries may be added with a call to FILE^DICN and a
 call to IX1^DIK.  
  STATUS: Active

NUMBER: 10111                           IA #: 10111
  FILE NUMBER: 3.8                      GLOBAL ROOT: XMB(3.8,
  DATE CREATED: JAN 23, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: MAILMAN: Maintenance of Mail Groups
  ORIGINAL NUMBER: 10111                ID: XMB(3.8,
GLOBAL REFERENCE: XMB(3.8,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Read access through DIC.  May be pointed to.  If pointed
 to, name should be gotten by using $$GET1^DIQ.  In exporting packages, if
 pointers are used, any exported records should have the Mail Group pointers
 purged before export.  Free Text fields, with an input transform that checks
 via DIC, can also be used to then store the Mail Group name.  Note that this
 permits reliable export of records that include a predefined Mail Group.  
  
 A programmer API for most tasks is defined in DBIA 1146    MAILMAN: Groups:
 Access and Modification      XMBGRP 
  STATUS: Active

NUMBER: 10112                           IA #: 10112
  DATE CREATED: MAR 07, 1994            CUSTODIAL PACKAGE: REGISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VASITE                       NAME: VASITE
  ORIGINAL NUMBER: 10112                ID: VASITE
 GENERAL DESCRIPTION:   See in routine documentation.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: $$SITE
 COMPONENT DESCRIPTION:   SITE(DATE,DIV)  ; 
         ;    -Output= Institution file pointer^Institution name^station 
         ;     number with suffix 
         ;
         ;    -Input (optional) date for division, if undefined will use DT 
         ;    -      (optional) medical center division=pointer in 40.8 
COMPONENT/ENTRY POINT: $$PRIM(DATE)
 COMPONENT DESCRIPTION:   
  - returns medical center division of primary medical center division 
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   This is an optional variable.  If date is not passed
 in DT will be used.  
COMPONENT/ENTRY POINT: $$NAME(DATE)
 COMPONENT DESCRIPTION:   This entry point returns the new name of integrated
 medical centers found in the INTEGRATION NAME (#17000) FIELD in the STATION
 NUMBER (TIME SENSITIVE) (#389.9) file.  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   DATE = File Manager date (Optional). If date not
 defined, today's date will be used.  
COMPONENT/ENTRY POINT: $$ALL(DATE)
 COMPONENT DESCRIPTION:   Returns all possible station numbers 
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   Optional.  If DATE is undefined, then date will be
 today.  
VARIABLES: $$ALL                        TYPE: Output
 VARIABLES DESCRIPTION:   
  -1 if none exist from the date specified 
  1 if one or more exists 
VARIABLES: VASITE                       TYPE: Output
 VARIABLES DESCRIPTION:   
  VASITE(station number)=station number 

NUMBER: 10113                           IA #: 10113
  FILE NUMBER: 3.9                      GLOBAL ROOT: XMB(3.9,
  DATE CREATED: FEB 20, 1995            CUSTODIAL PACKAGE: MAILMAN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: MAILMAN: Message Text - Direct Entry
  ORIGINAL NUMBER: 10113                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 Write & w/Fileman
 FIELD DESCRIPTION:   The supported references for MailMan include the ability
 for all DHCP packages to enter text directly into the word processing field of
 a message.  Such a reference would be to: 
  
    ^XMB(3.9,message#,2,line#,0) 
  
 The way to use this has been documented in MailMan documentation under the
 topic of 'Efficient Use of the [MailMan] Programmer Interface'.  
FIELD NUMBER: 1                         FIELD NAME: FROM
  LOCATION: 0;2                         ACCESS: Read w/Fileman
GLOBAL REFERENCE: XMB(3.9,D0,2,0)
FIELD NUMBER: 3                         FIELD NAME: TEXT
  LOCATION: 2;0                         ACCESS: Write w/Fileman
 FIELD DESCRIPTION:   If you put lines into the global, you must define the
 "zero" node with: 
  
        ^3.92^#lines^#lines^date 
 GENERAL DESCRIPTION:   Summary 
  
 Sites complain about the way their machines seems to slow down considerably
 when Austin DPC transmissions are created.  Large messages may be created in a
 more efficient way than is being used by most applications.  Since all DHCP
 sites are mandated to migrate to Kernel 7.1 by 12/01/93, all applications can
 now use this method of creating a message.  
  
  
 Technical Background 
  
 The simplest approach is probably the one people are using.  It is pretty 
 straight forward: 
  
   Load the text of a message into an array 
   Set a couple of variables 
   D ^XMD 
  
 With short messages, this is also fairly efficient if a local array is used. 
 However, when a large message is built, it usually must be stored in a global
 array.  Then, MailMan must read it and re-write it.  This effectively doubles
 the amount of work the system must do to compile the text of the message.  The
 killing of the temporary global array built to store the data passed to the
 MailMan programmer interface eats up additional resources.  
  
 So why not write the text of the message (the data) directly into the message,
 especially now that it is possible and that all the entry points have been
 made available and are documented?  Examine the examples on the following
 lines.  
  Example 
  
 The following steps assume that the standard variables already exist in the
 partition from either Log-on or because the job is a TaskMan task.  
  
 Step 1  --  Create a Message with No Text 
  
 S XMSUB="LARGE DATA TRANSMISSION";     Initialize Subject S XMDUZ="Application
 X"          ;     Sender D GET^XMA2                       ;     Call Create
 Message Module 
                                                         See Note 1 below! I
 XMZ<1 G RETRY        ;       Abort or retry, if returned value <1 
  
  
 Step 2  --  Put Text into Message 
        F L=1:1 S X=$$data^routine Q:X="stop value"  S ^XMB(3.9,XMZ,2,L,0)=X 
        S ^XMB(3.9,XMZ,2,0)="^3.92^"_L_"^"_L_"^"_DT 
  
  
 Step 3  --  Deliver Message to Recipients 
  
 S XMDUN="SENDER,LARGEMESSAGE"; A Sender can be free text or you can 
                              ;       Leave the variable undefined and the 
                              ;       message will appear to be from the 
                              ;       user who was logged on.  S XMY
 ("XXX@Q-AUSTIN_'Q'_DOMAIN")=""  ;  Remote Recipient S XMY(234567)=""           
  ;   Individual as a recipient S XMY(234567)="basket name"  ;   Individual as
 a recipient in a basket .  
 .
 .
 D ENT^XMD  ;                           Call for MailMan Delivery 
  
 The message will now be delivered.  This may not happen immediately because
 the job of delivery the message is passed off to a 'background filer'.  
  
 ------------------------------------------------------------------------
  
 Note 1:        In versions of MailMan previous to Kernel Version 7, Step 1 may
 occasionally fail!  The interface, upon failing, will cause the job to halt. 
 Because some applications require that a message be created as a result of a
 background task, a new entry point has been created for Kernel 7 that will not
 cause the process to be halted.  It will instead pass back to the caller an
 indication of success (XMZ>0) or failure (XMZ<1).  The use of this new entry
 point is illustrated below.  IT IS RECOMMENDED that all applications that use
 the GET^XMA2entry point migrate to the XMZ^XMA2 entry point unless the
 developers (being aware of the potential problem) decide otherwise.  If XMZ=-1
 condition is not checked, this large message creation technique will stuff
 data into ^XMTS(3.9,-1.  This may lead to other problems later on! 
  
  
 Note 2:        There is a way to tell MailMan to run silently via remote 
 domain when ENT1^XMD is called with the XMY("XXX@DOMAIN") set. If the XMCHAN
 or ZTQUEUED variables are set, MailMan is usually silent.  MailMan is silent
 when ZTQUEUED is present because it is a background job.  However, DO NOT set
 the ZTQUEUED variable yourself! If anyone other than TaskMan ever sets
 ZTQUEUED, the whole intent of the variable is lost.  Callers to the MailMan
 API functions and callable entry points should set XMCHAN to ensure silent
 operation.  Be sure to kill XMCHAN when completed.  
  STATUS: Active

NUMBER: 10114                           IA #: 10114
  FILE NUMBER: 3.5                      GLOBAL ROOT: %ZIS(1,
  DATE CREATED: AUG 04, 2020            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            NAME: DEVICE FILE
  ORIGINAL NUMBER: 10114                ID: %ZIS(1,
GLOBAL REFERENCE: %ZIS(1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Field .01 - Name, is supported for read only. 
 Applications may point to the Device file.  The name must be passed to %ZIS
 through ION, and the name may be found by:  S X="`ien",DIC=3.5,DIC(0)="" D
 ^DIC S ION=$P(Y,U,2) Likewise, EN^DIQ1 may also be used to retrieve the text
 for ION.  In a future version or patch, %ZIS will be enhanced to accept the 
 accent grav _ ien.  
GLOBAL REFERENCE: %ZIS(1,D0,'TYPE')
FIELD NUMBER: 2                         FIELD NAME: TYPE
  LOCATION: TYPE;1                      ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field indicates the general type of a device on the
 network. Please refer to the DEVICE (#3.5) file data dictionary and the TYPE
 (#2) field for the current device types available.  
GLOBAL REFERENCE: %ZIS(1,D0,'SUBTYPE')
FIELD NUMBER: 3                         FIELD NAME: SUBTYPE
  LOCATION: SUBTYPE;1                   ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   This field identifies the type of terminal. Terminal
 names should be in following format: 
  
  "C-"   for video terminals 
  "PK-"  for printers with keyboards 
  "P-"   for printers without keyboards 
  "M-"   for modems 
  STATUS: Active
KEYWORDS: DEVICE (#3.5)
KEYWORDS: DEVICE TYPE
KEYWORDS: DEVICE SUBTYPE

NUMBER: 10115                           IA #: 10115
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  ROUTINE: LIST MANAGER                 NAME: LIST MANAGER
  ORIGINAL NUMBER: 10115                ID: LIST MANAGER
  STATUS: Active
COMPONENT/ENTRY POINT: PROTOCOLS for List Manager
 COMPONENT DESCRIPTION:   The following are generic actions in the PROTOCOL
 file. They may be attached to any application defined Protocol menu specified. 
 
 *      VALM DOWN A LINE Move down a line.  
  ________________________________________________________
 *      VALM UP ONE LINE Move up a line         
 ________________________________________________________
 *      VALM FIRST SCREEN This action will display the first screen.  
 ________________________________________________________
 *      VALM LAST SCREEN The action will display the last items.  
 ________________________________________________________
 *      VALM NEXT SCREEN This action will allow the user to view the next
 screen of entries, if any exist.  
 ________________________________________________________
 *      VALM PREVIOUS SCREEN This action will allow the user to view the
 previous screen of entries, if any exist.  
 ________________________________________________________
 *      VALM PRINT LIST This action allows the user to print the entire list of
 entries currently being displayed.  
 ________________________________________________________
 *      VALM PRINT SCREEN This action allows the user to print the current List
 Manager display screen.  The header and the current portion of the list are
 printed.  
 ________________________________________________________
 *      VALM REFRESH This actions allows the user to re-display the current
 screen.  
 ________________________________________________________
 *      VALM SEARCH LIST Finds text in list of entries.  
 ________________________________________________________
 *      VALM TURN ON/OFF MENUS This toggles the menu of actions to be
 displayed/not displayed automatically. 
 ________________________________________________________
 *      VALM GOTO PAGE This protocol will allow the user to move to any page in
 the list.  
 ________________________________________________________
 *      VALM RIGHT This protocol will allow the user to move the screen to the
 right if the List Template is set up for a width of more then 80 characters.  
 ________________________________________________________
 *      VALM LEFT This protocol will allow the user to move the screen to the
 left if the List Template is set up for a width of more then 80 characters.  
 ________________________________________________________
 *      VALM QUIT This protocol can be used as a generic 'quit' action.  
 ________________________________________________________
 *      VALM HIDDEN ACTIONS This menu protocol contains all the above action
 protocols. The developer will usually specify this protocol as the 'Hidden
 Menu' protocol in the List Template set up.  The Workbench will automatically
 designate this protocol as the 'Hidden Menu' protocol when a List Template is
 initially created.  
 ________________________________________________________

NUMBER: 10116                           IA #: 10116
  DATE CREATED: SEP 21, 2021
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VALM1                        NAME: VALM1
  ORIGINAL NUMBER: 10116                ID: VALM1
  STATUS: Active
COMPONENT/ENTRY POINT: $$SETSTR
 COMPONENT DESCRIPTION:   *      $$SETSTR^VALM1(STRING, DEST, COLUMN, LENGTH) 
 This extrinsic function will setup a string for display.  Once the string has
 been set up for display, it would be set in the local variable or global
 specified in the list template. (e.g.  S  ^TMP("SDAM",$J,SDLN)=X) 
  
 INPUT: STRING := string to insert DEST   := destination string COLUMN        
 := insert @ col. X LENGTH := clear # of chars (length) 
  
 OUTPUT: [returned] := <string> 
  
 Example: >S X=$$SETSTR^VALM1("This","",10,4) W !,X 
  
          This >S X=$$SETSTR^VALM1("is",X,20,2) W !,X 
  
          This      is >S X=$$SETSTR^VALM1("an",X,30,2) W !,X 
          This      is        an >S X=$$SETSTR^VALM1("example.",X,40,8) W !,X 
          This      is        an        example.  
COMPONENT/ENTRY POINT: INSTR
 COMPONENT DESCRIPTION:   *      INSTR^VALM1(STRING, COLUMN, ROW, LENGTH,
 ERASE) This sub-routine will insert text on display screen at the row and 
 column specified.  
  
 INPUT: STRING         := string to insert COLUMN         := X coordinate ROW   
 := Y coordinate LENGTH := clear # of characters ERASE  := erase chars first 
COMPONENT/ENTRY POINT: FLDUPD
 COMPONENT DESCRIPTION:   *      FLDUPD^VALM1(STRING, FIELD, ENTRY) This
 sub-routine updates a specific field of a specified list entry on the display
 screen. The field name must match a field defined in the CAPTION LINE COLUMNS
 multiple of the LIST TEMPLATE file.  
  
 INPUT: STRING  := string to insert FIELD   := col. name ENTRY   := line # in
 list 
COMPONENT/ENTRY POINT: $$SETFLD
 COMPONENT DESCRIPTION:   *      $$SETFLD^VALM1(STRING, VARIABLE, FIELD) This
 sub-routine inserts the STRING at the column where the specific field starts
 in the VARIABLE string. The FIELD name must match a field defined in the
 CAPTION LINE COLUMNS multiple of the LIST TEMPLATE file.  
  
 INPUT: STRING   := string to insert VARIABLE := destination string FIELD    :=
 col. name 
  
 OUTPUT: [returned] := <string> 
COMPONENT/ENTRY POINT: CLEAR
 COMPONENT DESCRIPTION:   *      CLEAR^VALM1 This will change the screen from
 screen mode to the full scrolling region and clear the screen.  
  
 This call will also turn off the following: *      underline *      high
 intensity *      reverse video *      blinking 
  
        Use this call in programmers' mode during development to clean up the
 screen after an error occurs.  
COMPONENT/ENTRY POINT: FULL
 COMPONENT DESCRIPTION:   *      FULL^VALM1 This sets the screen to the full
 scrolling region.  
COMPONENT/ENTRY POINT: PAUSE
 COMPONENT DESCRIPTION:   *      PAUSE^VALM1 This will pause the screen.  The
 call uses a ^DIR call with DIR(0) set to "E" for end of page.  The prompt will
 look like: Type <Enter> to continue or '^' to exit: 
  
 WARNING: This API DOES NOT NEW any of the Reader variables (such as DIR), 
 which may lead to unexpected behavior. For a safer API, consider using 
 WAIT^VALM1.  
COMPONENT/ENTRY POINT: $$UPPER
 COMPONENT DESCRIPTION:   *      $$UPPER^VALM1(STRING) This will convert a
 string from lower case to upper case.  
  
 INPUT: STRING := string to convert 
  
 OUTPUT: [returned] := <string> 
COMPONENT/ENTRY POINT: $$LOWER
 COMPONENT DESCRIPTION:   *      $$LOWER^VALM1(STRING) This extrinsic function
 will convert a string from upper case to lower case.  It parses the string,
 using a space, comma and a '/',  It starts with the second character after
 each delimiter.  
  
 INPUT: STRING := string to convert 
  
 OUTPUT: [returned] := <string> 
  
  
 Example: 
        S X="PATIENT,ONE AND/OR PATIENT,TWO" 
  
        S X=$$LOWER^VALM1(X) 
  
        W X 
        Patient,One And/Or Patient,Two 
  
        If your line of text contains many consecutive spaces, it is 
         often faster to execute this function as you build each portion 
         the line, instead of after the line has been completely built.  
COMPONENT/ENTRY POINT: RANGE
 COMPONENT DESCRIPTION:   *      RANGE^VALM1 This sub-routine will allow the
 user to change a date range.  
  
 INPUT: DATE RANGE LIMIT field List Template file.  VALMB := default beginning
 date {optional} 
  
 OUTPUT: VALMBEG := beginning date in FM date format VALMEND := ending date in
 FM date format 
COMPONENT/ENTRY POINT: $$FDATE
 COMPONENT DESCRIPTION:   *      $$FDATE^VALM1(Y) This extrinsic function
 returns a date in 'mm/dd/yy' format.  (e.g.  12/12/92) 
  
 INPUT: Y := FM date/time format 
  
 OUTPUT: [returned] := formatted date only 
COMPONENT/ENTRY POINT: $$FDTTM
 COMPONENT DESCRIPTION:   *      $$FDTTM^VALM1(Y) This extrinsic function
 returns a date/time in 'mm/dd/yy@hh:mm' format.  (e.g. 12/12/92@09:00) 
  
 INPUT: Y := FM date/time format 
  
 OUTPUT: [returned] := formatted date and time 
COMPONENT/ENTRY POINT: $$FTIME
 COMPONENT DESCRIPTION:   *      $$FTIME^VALM1(Y) This extrinsic function
 returns a date/time in the 'mmm dd, yyyy@hh:mm' format.  (e.g. DEC 12,
 1992@09:00) 
  
 INPUT: Y := FM date format OUTPUT: [returned] := formatted date only 
COMPONENT/ENTRY POINT: $$NOW
 COMPONENT DESCRIPTION:   *      $$NOW^VALM1 This extrinsic date/time function
 returns the value of 'NOW' in external format.  
  
 INPUT: none OUTPUT: [returned] := value of 'now' in $$FTIME^VALM1 format (e.g.
 Mar 06, 1993 11:15:29) 
COMPONENT/ENTRY POINT: WAIT
 COMPONENT DESCRIPTION:   *      WAIT^VALM1 This will pause the screen with an
 end of page call to the FileMan Reader. The user is prompted with "Enter
 RETURN to continue".  
  
 NOTE: This is a safer API than PAUSE^VALM1 as all Reader variables are NEWed.  

NUMBER: 10117                           IA #: 10117
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VALM10                       NAME: VALM10
  ORIGINAL NUMBER: 10117                ID: VALM10
  STATUS: Active
COMPONENT/ENTRY POINT: FLDTEXT
 COMPONENT DESCRIPTION:   *      FLDTEXT^VALM10(LINE, FIELD, STRING) This
 sub-routine inserts the text STRING at the column where the specific field
 starts in a LINE in the list array.  
  
 The FIELD name must match a field defined in the CAPTION LINE COLUMNS multiple
 of the LIST TEMPLATE file.  
  
 INPUT: LINE   := line number FIELD  := column. name STRING := string to insert 
COMPONENT/ENTRY POINT: SET
 COMPONENT DESCRIPTION:   *      SET^VALM10(LINE, STRING, ENTRY#) This
 sub-routine will set the LINE in the array equal to the text STRING. If the
 List Template does not define an ARRAY NAME, then this call must be used to
 build lines in the array.  
  
 INPUT: LINE   := line number STRING := string to for array line ENTRY# :=
 entry number associated with the line(if 
            passed, then line will also be indexed for use by the 
            EN^VALM2 selection utility.) [optional] 
COMPONENT/ENTRY POINT: CNTRL
 COMPONENT DESCRIPTION:   *      CNTRL^VALM10(LINE, COLUMN, WIDTH, ON, OFF,
 SAVE) This subroutine allows the developer to indicate video attributes for 
 text in a list.  
  
 INPUT: LINE           := line number COLUMN                 := column where
 code should be invoked WIDTH          := how many columns should the code be
 in effect for ON             := beginning control sequence OFF            :=
 ending control sequence SAVE           := 1 to save control sequence for later
 use 
                        otherwise 0 [optional] 
COMPONENT/ENTRY POINT: KILL
 COMPONENT DESCRIPTION:   *      KILL^VALM10(LINE) This subroutine deletes
 video attributes. If LINE is not defined then all video attributes for a List
 Template will be deleted. If LINE is defined then only the attributes for that
 line are deleted.  
  
 INPUT: LINE   := line number 
COMPONENT/ENTRY POINT: SAVE
 COMPONENT DESCRIPTION:   *      SAVE^VALM10(LINE) This subroutine saves the
 current video attributes for the indicated line.  
  
 INPUT: LINE   := line number 
COMPONENT/ENTRY POINT: RESTORE
 COMPONENT DESCRIPTION:   *      RESTORE^VALM10(LINE) This subroutine restores
 the video attributes that have been saved for the indicated line.  
  
 This subroutine does not re-write the line to the screen. The subroutine
 WRITE^VALM(LINE) should be used to actually write the line.  
  
 INPUT: LINE   := line number 
COMPONENT/ENTRY POINT: SELECT
 COMPONENT DESCRIPTION:   *      SELECT^VALM10(LINE, MODE) This subroutine will
 highlight/unhighlight a line in the list. The call will set up or delete the
 proper video controls and then 'writes' the line to the screen.  
  
 The 'line' passed to this call must currently be displayed on the screen.  
  
  
 INPUT: LINE   :=      line number MODE   :=      1 to highlight 
                0 to unhighlight and restore to original state 
COMPONENT/ENTRY POINT: WRITE
 COMPONENT DESCRIPTION:   *      WRITE^VALM10(LINE) This subroutine will
 re-write the line to the screen.  
  
 INPUT: LINE   := line number 
COMPONENT/ENTRY POINT: FLDCTRL
 COMPONENT DESCRIPTION:   *      FLDCTRL^VALM10(LINE, FIELD, ON, OFF, SAVE) 
 This subroutine will set up the appropriate video control sequences for a LINE
 in the list array based on the DEFAULT VIDEO ATTRIBUTES in the CAPTION LINE
 definition for the template.  
  
 If FIELD is passed, then only the video attributes defined for that field will
 be set up.  
  
 If ON is defined, then code in ON will be used for the video attributes 
 instead of the default.  
  
 If OFF is defined, then code in OFF will be used for the video attributes
 instead of the default.  
  
 INPUT: LINE   := line number FIELD  := column name [optional] ON     :=
 beginning control sequence [optional] OFF    := ending control sequence
 [optional] SAVE   := 1 to save control sequence for later use 
           otherwise 0 [optional] 
COMPONENT/ENTRY POINT: CLEAN
 COMPONENT DESCRIPTION:   *      CLEAN^VALM10 This subroutine will kill the
 data and video control arrays associated with the active List template.  
  
 This call is commonly used to kill the array related data before re- building
 the array.  
COMPONENT/ENTRY POINT: MSG
 COMPONENT DESCRIPTION:   *      MSG^VALM10(MESSAGE) This call allows the
 developer to immediately post a message to the 'message window' located in the
 lower frame bar of the List Manager display screen.  
  
 INPUT: MESSAGE        := Text up to 50 characters.  OUTPUT: [none] 
  
 To turn off the custom message and re-display List Manager's standard message,
 make a call to MSG^VALM10 with the null string as the message[e.g. D
 MSG^VALMSG("")].  
  
 To display a custom message when List Manager re-displays the screen after an
 action is performed, set the variable VALMSG to the desired message text.  

NUMBER: 10118                           IA #: 10118
  CUSTODIAL PACKAGE: LIST MANAGER       CUSTODIAL ISC: Albany
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VALM
  NAME: VALM                            ORIGINAL NUMBER: 10118
  ID: VALM                              STATUS: Active
COMPONENT/ENTRY POINT: CHGCAP
 COMPONENT DESCRIPTION:   *      CHGCAP^VALM(FIELD, LABEL) This sub-routine
 will change a label on caption header for a field defined in CAPTION LINE
 COLUMNS multiple in the List Template file.  INPUT: FIELD  := column name 
 LABEL  := text for column header 
COMPONENT/ENTRY POINT: SHOW
 COMPONENT DESCRIPTION:   *      SHOW^VALM This call MUST be executed in the
 HEADER field of a protocol menu entry in the PROTOCOL file if the protocol is
 used in the PROTOCOL field in the LIST TEMPLATE file.  
  
 This code will properly display the list of actions to the user in the action
 area of the list screen.  
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   EN^VALM(<List Template Name>) 
    Description: Main entry point to envoke an instance of a List Template.  
  
      Parameter: <List Template Name> 
                 Name of a List Template as it appears in the LIST 
                 TEMPLATE file (#409.61) 

NUMBER: 10119                           IA #: 10119
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VALM2                        NAME: VALM2
  ORIGINAL NUMBER: 10119                ID: VALM2
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   *      EN^VALM2(VALMNOD,OPTIONS) This sub-routine is
 a generic selector that can be used within an action call.  
  
 INPUT : VALMNOD        := variable  in XQORNOD(0) format - See Order Entry 
                   documentation.  
  
 OPTIONS                := selection options 
                     * if it contains an 'O' then selection is optional.  
                        Otherwise, the user must make a selection or enter 
                        an up-arrow.  
                      * if it contains a 'S', the user can only select one 
                        entry. Otherwise, the user can select more than 
                        one item.  
  
 OUTPUT: VALMY() := array with select entries as subscripts 
  
 In order to use this call, the List Manager ENTRY CODE will need to set up the
 @VALMAR@("IDX") index array. For more information on setting up this array,
 see the section on 'Setting Up a List Template - MUMPS Code Edit.'.> 

NUMBER: 10120                           IA #: 10120
  CUSTODIAL PACKAGE: LIST MANAGER       CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: VALM4
  NAME: VALM4                           ORIGINAL NUMBER: 10120
  ID: VALM4                             STATUS: Active
COMPONENT/ENTRY POINT: RE
 COMPONENT DESCRIPTION:   *      RE^VALM4 This call will re-display the list
 header and list areas for the active list application.  
  
 This call is often used to display the results of a change an action has 
 caused before passing control back to the List Manager. (Normally, the 
 developer set VALMBCK="R" and then returns control to the List Manager.) 

NUMBER: 10122                           IA #: 10122
  CUSTODIAL PACKAGE: TOOLKIT            CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: Routine
  DBIC APPROVAL STATUS: APPROVED        ROUTINE: XTLKKWL
  NAME: XTLKKWL                         ORIGINAL NUMBER: 10122
  ID: XTLKKWL                           STATUS: Active
COMPONENT/ENTRY POINT: XTLKKWL
 COMPONENT DESCRIPTION:   Developers can perform any supported VA Fileman calls
 on files configured for MTLU. To ignore the special lookup routine, XTLKDICL,
 be sure that DIC(0) includes an "I." Alternatively, multi-term look-ups can be
 performed on any VA Fileman file, even if it has not been configured for
 primary use by MTLU. Using the programmer API, the lookup can be performed
 using any index contained within the file, such as a Fileman KWIC
 cross-reference.  
  
 Input routine: XTLKKWL 
  
 Required variables: (XTLKGBL, XTLKKSCH("GBL"))=global root (same as DIC) 
                     XTLKKSCH("DSPLY")=Display routine (ie, DGEN^XTLKKWLD) 
                     XTLKKSCH("INDEX")=Cross-reference to use 
                     XTLKX=User input 
  
 Optional variable:  XTLKSAY=1 or 0 (If 1, mtlu will display details during 
                                        lookup) 
                     XTLKHLP=Executable code to display custom help 

NUMBER: 10123                           IA #: 10123
  DATE CREATED: MAY 10, 1994
  CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES
  CUSTODIAL ISC: Salt Lake City         USAGE: Supported
  TYPE: Other                           DBIC APPROVAL STATUS: APPROVED
  NAME: CWAD                            ORIGINAL NUMBER: 10123
 GENERAL DESCRIPTION:   The following information is from patch GMRP*2.5*22,
 which describes how this supported reference is used.  
  
 A letter from the Regional Director, Western Region, dated January 25, 1994, 
 subject:  Use of Electronic Mail for Patient Flagging System Among VA 
 Facilities, requested a utility for flagging and disseminating critical 
 patient information.  This patch is to inform all sites that such a mechanism
 is available within DHCP.  This patch corrects the problem of the (A)llergy
 warning being indicated in the CWAD display when the patient has 'No Known
 Allergies'.  The variable GMRPHOLD (Supported Reference #10123) will now be
 supported by Progress Notes.  If set, this variable will force the user to
 enter a carriage return after the CWAD display.  This is designed to be used
 when an application clears the screen after a patient lookup.  
  
 In response to:  E3R #3056 dtd Oct 5, 1993 
                  NOIS: PROG DEN CWAD  dtd Mar 3, 1994 
  
 Through the Progress Notes Application, sites are able to implement a warning 
 system which notifies users of specific patient conditions.  The system is 
 called CWAD.  The acronym stands for: 
  
                    "C" RISIS NOTES 
                    CLINICAL "W"ARNINGS 
                    "A"LLERGIES 
                    ADVANCED "D"IRECTIVES 
  
 To Implement the CWAD Warning System: 
 ************************************
 To implement the CWAD alert system, the variable "GMRPEN" must be set as an 
 Entry Action for a particular option.  It may not be appropriate for the CWAD
 alerts to be displayed for certain applications.  Which options the CWAD is
 implemented with is entirely at the sites' discretion.  The following example
 uses the MAS Registration Menu.  This is not to say your site must implement
 the CWAD for this option; this is for demonstration purposes only.  It will
 work with any menu or option your site deems appropriate.  
  
 D P^DI 
  
 Select OPTION:  1  ENTER OR EDIT FILE ENTRIES 
  
 INPUT TO WHAT FILE:  OPTION// EDIT WHICH FIELD:ALL//ENTRY ACTION THEN EDIT 
 FIELD:EXIT ACTION 
  
 Select OPTION NAME: DG REGISTRATION MENU    Registration Menu ENTRY ACTION: S
 (GMRPEN,GMRPHOLD)=1 EXIT ACTION: K GMRPEN,GMRPHOLD Select OPTION NAME: Select
 OPTION: 
 >
 Once the variable is initialized the Warnings will be displayed upon patient
 look-up.  
  
 Select PATIENT NAME:  HOOD,ROBIN  03-04-33   112233444  ACTIVE DUTY 
  
                       C: 07/01/93   11:53 
                       W: 07/11/93   10:57 
                       A: Known allergies 
                       D: 10/09/93   10:18 
  
 Types of Warnings: 
 *****************
  
 The following are for illustration purposes only.        
  
    CRISIS                    CAUTION:  Patient may be homicidal.  
  
    CLINICAL WARNING          Patient is HIV positive.  
  
    ALLERGY/ADVERSE REACTION  Allergy/Reaction:  Ampicillin 
  
    ADVANCE DIRECTIVE         DO NOT RESUSCITATE:  Patient has 
                               Advanced Directive filed in Volume 
                               6 of his medical record.          
  
 To Enter Warnings into the CWAD System: 
 **************************************
  
 With the exception of Allergies, Warnings are entered directly through the 
 Progress Notes application.  
  
 1.  In order for a progress note to be recognized as a Warning, the TITLE of a
 note must be linked to one of the following notes types.  
     
     a.  CRISIS 
     b.  CLINICAL WARNING 
     c.  ADVANCED DIRECTIVES (IMPLEMENTATION OF) 
  
 The TITLE narrative is at the discretion of the site.  The important thing to 
 understand is that the TITLE must be tied to one of the above TYPES.  TITLES 
 with the same name as the above TYPES were exported with Progress Notes 2.5 
 already linked together but since the TITLE file is controlled by the site it
 is possible your site may have them configured differently.  
  
 *NOTE:  Allergy information should be entered through the Allergy Tracking 
 System.  
  
 2.  Once the TITLE is linked with the a warning TYPE, the user may then enter 
 the Progress Note Option.  Using the Entry of Progress Note option, select the
 appropriate title and proceed to enter the warning.  The note must then be
 signed.  
  
 3.  After signature, the note becomes active on the CWAD Warning System.  
   
 How to Access the CWAD Warnings: 
 *******************************
  
 1.  If the user is assigned the Progress Notes User Menu, the Patient Warning 
 (CWAD) Display option [GMRPNCW] may be accessed from that menu.  If the user 
 is not assigned this menu it may be assigned as a secondary menu option. It
 would be convenient to the user to make the synonym CWAD.  
   
 2.  When a Warning(s) is displayed, review of the warning can be done by 
 entering CWAD at any option select prompt.  A review screen will be displayed
 from which the user can select the warning(s) they wish to view.  
      
 After implementation of the CWAD display you may find that the display flashes
 by before the user can read it.  This can be corrected by setting the variable
 GMRPHOLD, in addition to GMRPEN, in the entry action of the desired
 menu/option.  GMRPHOLD must also be killed in the exit action.  WARNING:  Do
 not arbitrarily set the variable GMRPHOLD in the entry action without first
 checking to see if the option clears does clear the screen after the patient
 lookup.  The user may be inconvenienced with an unecessary carriage return.  
  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: GMRPNCW
 COMPONENT DESCRIPTION:   GMRPNCW is a routine that is called at ENPAT from the
 MAS patient lookup routine ^DGSEC to allow the display of CWAD information.  
VARIABLES: GMRPHOLD                     TYPE: Input
 VARIABLES DESCRIPTION:   The GMRPHOLD variable is used in conjunction with
 GMRPEN (#10121), which enables the CWAD brief display immediately after any
 patient lookup.  GMRPHOLD should be defined if it is desired to issue a
 carriage return after the brief CWAD display.  Since one of the recommended
 uses for this variable is in an Entry Action, applications using this variable
 should take care to NEW it as not to impact the sites defined implementation.  
VARIABLES: GMRPEN                       TYPE: Input
 VARIABLES DESCRIPTION:   This variable is used to enable the display of the
 presence of any patient Crises, Warnings, Alerts, or advanced Directives on
 file.  The actual CWADs through an appropriately assigned menu option. 
 Applications needing to display the CWAD indication on patient lookup may set 
 this variable.  

NUMBER: 10130                           IA #: 10130
  FILE NUMBER: 61.1                     GLOBAL ROOT: LAB(61.1,
  CUSTODIAL PACKAGE: LAB SERVICE        CUSTODIAL ISC: Dallas
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: MORPHOLOGY FIELD FILE
  ORIGINAL NUMBER: 10130                ID: LAB(61.1,
GLOBAL REFERENCE: LAB(61.1,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Active

NUMBER: 10131                           IA #: 10131
  FILE NUMBER: 61.2                     GLOBAL ROOT: LAB(61.2,
  CUSTODIAL PACKAGE: LAB SERVICE        CUSTODIAL ISC: Dallas
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: ETIOLOGY FIELD FILE
  ORIGINAL NUMBER: 10131                ID: LAB(61.2,
GLOBAL REFERENCE: LAB(61.2,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Active

NUMBER: 10132                           IA #: 10132
  FILE NUMBER: 61.3                     GLOBAL ROOT: LAB(61.3,
  CUSTODIAL PACKAGE: LAB SERVICE        CUSTODIAL ISC: Dallas
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: FUNCTION FIELD FILE
  ORIGINAL NUMBER: 10132                ID: LAB(61.3,
GLOBAL REFERENCE: LAB(61.3,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Active

NUMBER: 10133                           IA #: 10133
  FILE NUMBER: 61.4                     GLOBAL ROOT: LAB(61.4,
  CUSTODIAL PACKAGE: LAB SERVICE        CUSTODIAL ISC: Dallas
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DISEASE FIELD FILE
  ORIGINAL NUMBER: 10133                ID: LAB(61.4,
GLOBAL REFERENCE: LAB(61.4,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Active

NUMBER: 10134                           IA #: 10134
  FILE NUMBER: 61.5                     GLOBAL ROOT: LAB(61.5,
  CUSTODIAL PACKAGE: LAB SERVICE        CUSTODIAL ISC: Dallas
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: PROCEDURE FIELD FILE
  ORIGINAL NUMBER: 10134                ID: LAB(61.5,
GLOBAL REFERENCE: LAB(61.5,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Active

NUMBER: 10135                           IA #: 10135
  FILE NUMBER: 61.6                     GLOBAL ROOT: LAB(61.6,
  CUSTODIAL PACKAGE: LAB SERVICE        CUSTODIAL ISC: Dallas
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: OCCUPATION FIELD FILE
  ORIGINAL NUMBER: 10135                ID: LAB(61.6,
GLOBAL REFERENCE: LAB(61.6,D0,0)
FIELD NUMBER: .01                       FIELD NAME: NAME
  LOCATION: 0;1                         ACCESS: Read w/Fileman
  STATUS: Active

NUMBER: 10136                           IA #: 10136
  FILE NUMBER: 771                      GLOBAL ROOT: HL(771,
  DATE CREATED: MAR 19, 2025            CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: HL7 APPLICATION PARAMETER       ORIGINAL NUMBER: 10136
  ID: HL(771,
 GENERAL DESCRIPTION:   The creation of new entries must be cleared through
 Technical Integration by sending review materials to icrs@va.gov.  New entries
 may be exported using KIDS.  
  STATUS: Active                        DATE ACTIVATED: MAR 19, 2025

NUMBER: 10137                           IA #: 10137
  FILE NUMBER: 771.3                    GLOBAL ROOT: HL(771.3,
  CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: HL7 SEGMENT NAME FILE           ORIGINAL NUMBER: 10137
  ID: HL(771.3,
GLOBAL REFERENCE: HL(771.3,'B'
 GLOBAL DESCRIPTION:   The "B" cross-reference may be checked.  Pre-approved
 entries may be added to the file.  
 GENERAL DESCRIPTION:   File 771.3 may be accessed only during package post 
 initialization.  The creation of new entries must be cleared through the HL7
 development team.  New entries may be added with a call to FILE^DICN and a
 call to IX1^DIK.  
  STATUS: Active

NUMBER: 10138                           IA #: 10138
  FILE NUMBER: 772                      GLOBAL ROOT: HL(772,
  CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: HL7 TRANSMISSION FILE           ORIGINAL NUMBER: 10138
  ID: HL(772,
GLOBAL REFERENCE: HL(772,D0,'IN',D1,
FIELD NUMBER: 200                       FIELD NAME: INCOMING MESSAGE TEXT
  LOCATION: IN;0                        ACCESS: Read w/Fileman
 FIELD DESCRIPTION:   Applications may loop through this global to process
 incoming HL7 messages.  Supported for read access only.  
 GENERAL DESCRIPTION:   Files 770, 771, and 771.3 may be accessed only during
 package post initialization.  The creation of new entries must be cleared
 through the HL7 development team.  New entries may be added with a call to 
 FILE^DICN and a call to IX1^DIK.  
  STATUS: Active

NUMBER: 10139                           IA #: 10139
  DATE CREATED: MAR 07, 1994
  CUSTODIAL PACKAGE: VETERANS ADMINISTRATION
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: VAFADDR                      NAME: VAFADDR
  ORIGINAL NUMBER: 10139                ID: VAFADDR
 GENERAL DESCRIPTION:   See in routine documentation.  
  STATUS: Active
COMPONENT/ENTRY POINT: ZIPIN
 COMPONENT DESCRIPTION:   Input transform for zip code fields to allow 5 digit
 zip or ZIP+4 to be entered.  
COMPONENT/ENTRY POINT: ZIPOUT
 COMPONENT DESCRIPTION:   Output transform to display zip code in zip code in
 12345 or 12345-6789 format.  

NUMBER: 10140                           IA #: 10140
  DATE CREATED: MAR 07, 1994            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XQORM                        NAME: XQORM
  ORIGINAL NUMBER: 10140                ID: XQORM
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This entry point handles the display of and selection
 from a menu.  Note that this routine processes a single menu only.  This is
 the call EN^XQOR uses to obtain menu selections.  The caller is responsible to 
 handle any selections from the menu that are returned in the Y array.  If you
 want navigation to the selected items handled for you, use the EN^XQOR entry
 point.  The menus handled by this routine are the multiple selection, multiple
 column menus that are typical in OE/RR.  
VARIABLES: XQORM                        TYPE: Input
 VARIABLES DESCRIPTION:   A variable pointer to the menu that should be
 displayed, e.g. XQORM="1234;ORD(101," 
VARIABLES: XQORM(0)                     TYPE: Input
 VARIABLES DESCRIPTION:   A string of flags that control the display and
 prompting of the menu.  numeric  Maximum number of selections allowed.  A      
  Prompt for a selection from the menu D        Display the menu.  
VARIABLES: Y()                          TYPE: Output
 VARIABLES DESCRIPTION:   This array contains the items that the user selected
 from the menu.  
COMPONENT/ENTRY POINT: XREF
 COMPONENT DESCRIPTION:   Menus are compiled into the XUTL global.  This should
 happen automatically.  If you need to force a menu to recompile, XREF^XQORM
 can be used to do that.  
VARIABLES: XQORM                        TYPE: Input
 VARIABLES DESCRIPTION:   Variable pointer to the protocol which should be
 recompiled.  

NUMBER: 10141                           IA #: 10141
  DATE CREATED: APR 11, 1994            CUSTODIAL PACKAGE: KERNEL
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XPDUTL                       NAME: XPDUTL
  ORIGINAL NUMBER: 10141                ID: XPDUTL
 GENERAL DESCRIPTION:   The routine XPDUTL contains multiple calls to support
 the Kernel Installation and Distribution System.  All of the calls can only be 
 used in the context of the KIDS software, during the installation of software,
 unless noted differently in the describitions that follow.  
  
 The following calls can be used anywhere during the install process: 
 $$VERSION(X) ;X=package name or package namespace 
          ;Returns the current Version number 
        ** This call can be used outside of KIDs ** 
  
 $$VER(X) ;X=Build name from Build file or Install file 
          ;Returns version number 
  
 $$PKG(X) ;X=Build name from Build file or Install file 
          ;Returns package name 
  
 $$PATCH(X) ;X=Patch from Install file, (aaaa*nn.nn*nnn) 
          ;Return 1 if patch X was installed, 0 if not installed 
        ** This call can be used outside of KIDs ** 
  
 $$LAST(X,Y,Z) ;X=Package name or namespace, Y=Version (optional, current if
 not supplied), Z=1 released patch (optional, last released patch) 
             ;Returns Last Patch and Date applied to a package 
             ;PATCH will include Seq # if a released patch is last 
             ;PATCH #^DATE,  ("nnn^yyymmdd" or "nnn Seq #nn^yyymmdd") 
             ;-1 will be returned if either Package or Version do not exist 
             ;   or No patches have been applied 
        ** This call can be used outside of KIDs ** 
  
 $$INSTALDT(X,.Y) ;X=Name from Install file, variable passed by reference 
             ;Returns all installs for X in Install file 
             ;Return array in Y, Y=number of records in array 
             ;Y(internal date/time) = TEST # ^ SEQ # 
        ** This call can be used outside of KIDs ** 
  
 The following function can only be used in the Environment Check Routine 
 $$RTNUP(X,Y) ;X=routine name, Y= 1-delete, 2-skip 
        ;changes the install action of a routine to delete or skip 
        ;Returns 1 if successfull, 0 for failure 
  
  
 The following calls can be used during the Pre-Install or Post-Install 
  routines: $$PRODE(XPDN,XPD) ;XPDN=protocol name, XPD=1-enable, 0-disable 
        ;enable/disable protocols 
        ;Returns 1 if successfull, 0 for failure 
  
 $$OPTDE(XPDN,XPD) ;XPDN=option name, XPD=1-enable, 0-disable 
        ;enable/disable options 
        ;Returns 1 if successfull, 0 for failure 
  
 MES(X) ;X=message or an array passed by reference 
        ;write message to Install file 
  
 BMES(X) ;X=message or an array passed by reference 
        ;add blank line before writing message to Install file 
  
 $$NEWCP(XPD,XPDC,XPDP) ;XPD=check point name, XPDC=call back, XPDP=parameters 
        ;create new check point 
        ;Returns ien of check point, 0 for error 
  
 $$UPCP(XPD,XPDP) ;XPD=check point name or ien, XPDP=parameters 
        ;update check point 
        ;Returns ien of check point, 0 for error 
  
 $$COMCP(XPD) ;XPD=check point name or ien 
        ;complete check point 
        ;Returns date/time of completion, 0 for error 
  
 $$VERCP(XPD) ;XPD=check point name or ien 
        ;verify check point, returns 1=completed, 0=not 
        ;Returns 1 for completed, 0 for not completed, -1 for doesn't exist 
  
 $$PARCP(XPD,XPDF) ;XPD=check point name or ien, XPDF="PRE" if you want a 
        ;Pre-Install check point while your in the Post-Install routine 
        ;Returns parameters of check point 
  
 $$CURCP(XPDF) ;XPDF flag - 0=externel, 1=internal 
        ;Returns current check point 
  
  
  STATUS: Active
KEYWORDS: KIDS
COMPONENT/ENTRY POINT: $$VERSION(PKG)
 COMPONENT DESCRIPTION:   Returns the current version number for the given
 package 
VARIABLES: PKG                          TYPE: Input
 VARIABLES DESCRIPTION:   Package namespace or name 
COMPONENT/ENTRY POINT: $$PATCH(PATCH)
 COMPONENT DESCRIPTION:   Returns 1 if the given patch exist and 0 if it
 doesn't exist 
VARIABLES: PATCH                        TYPE: Input
 VARIABLES DESCRIPTION:   Patch name from Install file, format=AAAA*NN.NN*NNN 
COMPONENT/ENTRY POINT: $$VER(NAME)
 COMPONENT DESCRIPTION:   Returns the version number for the given Build name 
VARIABLES: NAME                         TYPE: Input
 VARIABLES DESCRIPTION:   Build name from Build file or Install file 
COMPONENT/ENTRY POINT: $$PKG(NAME)
 COMPONENT DESCRIPTION:   Returns the Package name or namespace for the given
 Build name 
VARIABLES: NAME                         TYPE: Input
 VARIABLES DESCRIPTION:   Build name from Build file or Install file 
COMPONENT/ENTRY POINT: $$RTNUP(RTN,ACT)
 COMPONENT DESCRIPTION:   Changes the install action of a routine to delete at
 site or skip this routine.  This can only be used during the Environment
 Check.  Returns 1 if successfull, or 0 for failure.  
VARIABLES: RTN                          TYPE: Input
 VARIABLES DESCRIPTION:   Routine name 
VARIABLES: ACT                          TYPE: Input
 VARIABLES DESCRIPTION:   Action for the routine.  1=Delete at site,  2=Skip
 this routine 
COMPONENT/ENTRY POINT: $$PRODE(PROT,ACT)
 COMPONENT DESCRIPTION:   Enable or Disable the given protocol during the
 Pre-Install or Post-Install routine.  
VARIABLES: PROT                         TYPE: Input
 VARIABLES DESCRIPTION:   Protocol name 
VARIABLES: ACT                          TYPE: Input
 VARIABLES DESCRIPTION:   1 = Enable this Protocol 0 = Disable this Protocol 
COMPONENT/ENTRY POINT: $$OPTDE(OPT,ACT)
 COMPONENT DESCRIPTION:   Enable or Disable the given option during the
 Pre-Install or Post-Install routine.  
VARIABLES: OPT                          TYPE: Input
 VARIABLES DESCRIPTION:   Option name 
VARIABLES: ACT                          TYPE: Input
 VARIABLES DESCRIPTION:   1 = Enable this Option 0 = Disable this Option 
COMPONENT/ENTRY POINT: MES(X)
 COMPONENT DESCRIPTION:   Writes the message X to the Install file.  Can used
 during the Pre-Install or Post-Install routines.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X can be a string or an array.  Each line of the
 array will be a seperate line in the message. If X is an array, it must be
 passed by reference.  
COMPONENT/ENTRY POINT: BMES(X)
 COMPONENT DESCRIPTION:   Write a blank line before the message X is written to
 the Install file.  Can used during the Pre-Install or Post-Install routines.  
VARIABLES: X                            TYPE: Input
 VARIABLES DESCRIPTION:   X can be a string or an array.  Each line of the
 array will be a seperate line in the message. If X is an array, it must be
 passed by reference.  
COMPONENT/ENTRY POINT: $$NEWCP(CP,CB,PARM)
 COMPONENT DESCRIPTION:   Create a new check point.  This can only be used in
 the Pre-Install and Post-Install routines.  
VARIABLES: CP                           TYPE: Input
 VARIABLES DESCRIPTION:   Check Point name.  
VARIABLES: CB                           TYPE: Input
 VARIABLES DESCRIPTION:   Call Back, this is the TAG^ROUTINE you want exeucted
 for the given Call Back.  
VARIABLES: PARM                         TYPE: Input
 VARIABLES DESCRIPTION:   This is a value that can be used to track the
 progress of your checkpoint.  
COMPONENT/ENTRY POINT: $$UPCP(CP,PARM)
 COMPONENT DESCRIPTION:   Update a check point with a new parameter value. 
 This can only be used in the Pre-Install and Post-Install routines.  
VARIABLES: CP                           TYPE: Input
 VARIABLES DESCRIPTION:   Check Point name you want to update 
VARIABLES: PARM                         TYPE: Input
 VARIABLES DESCRIPTION:   Value you want to save for the given check point.  
COMPONENT/ENTRY POINT: $$COMCP(CP)
 COMPONENT DESCRIPTION:   Complete a check point.  This can only be used in the
 Pre-Install and Post-Install routines. Return the date/time of completion, or 
 0 for error.  
VARIABLES: CP                           TYPE: Input
 VARIABLES DESCRIPTION:   Check Point name you want to complete.  
COMPONENT/ENTRY POINT: $$VERCP(CP)
 COMPONENT DESCRIPTION:   Verify a check point, returns 1 if complete.  This
 can only be used in the Pre-Install and Post-Install routines.  
VARIABLES: CP                           TYPE: Input
 VARIABLES DESCRIPTION:   Check point name you want to verify.  
COMPONENT/ENTRY POINT: $$PARCP(CP,FLAG)
 COMPONENT DESCRIPTION:   Returns the patameters for the given check point
 name.  The Flag is used only if you want to get the parameters from a
 'Pre-Install' check point while your in the Post-Install routine.  
VARIABLES: CP                           TYPE: Input
 VARIABLES DESCRIPTION:   Check Point name 
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   FLAG is optional, it is set to 'PRE' if you are in
 the Post-Install routine and you want a 'Pre-Install' check point.  
COMPONENT/ENTRY POINT: $$CURCP(FLAG)
 COMPONENT DESCRIPTION:   Returns the current Check Point that in process.  
VARIABLES: FLAG                         TYPE: Input
 VARIABLES DESCRIPTION:   This is used to determine if the current check point
 should be return in external or internal format.  0 = external, 1 = internal.  
COMPONENT/ENTRY POINT: $$LAST(PKG,VER,REL)
 COMPONENT DESCRIPTION:   Returns the Patch # and Date of the last patch
 applied to a package 
  
  
VARIABLES: PKG                          TYPE: Input
 VARIABLES DESCRIPTION:   The Package name as stored in the Package File (#9.4) 
  
VARIABLES: VER                          TYPE: Input
 VARIABLES DESCRIPTION:   The version of the Package, optional, current version
 will be used if not supplied 
  
VARIABLES: REL                          TYPE: Input
 VARIABLES DESCRIPTION:   A flag, optional, when set to 1, will only return the
 last released patch.  Available in patch XU*8*559.  
  
  
COMPONENT/ENTRY POINT: $$INSTALDT(INSTALL, .RESULT)
 COMPONENT DESCRIPTION:   Returns an array of all the installs in the Install
 file, #9.7, for INSTALL.  The array is formatted as RESULT(internal
 date/time)= TEST # ^ SEQ #.  
  
  
  
VARIABLES: INSTALL                      TYPE: Input
 VARIABLES DESCRIPTION:   The name of the entry in the Install file (#9.7) 
  
VARIABLES: RESULT                       TYPE: Both
 VARIABLES DESCRIPTION:   Array name, passed by reference, that will contain
 the results.  
   It will look like:  RESULT(internal date/time) = TEST # ^ SEQ #.  
   The variable RESULT will be equal to the number of records in the array.  
  
  DATE ACTIVATED: MAY 23, 2013

NUMBER: 10142                           IA #: 10142
  DATE CREATED: APR 11, 1994            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DDIOL                        NAME: Classic FileMan API: Loader
  ORIGINAL NUMBER: 10142                ID: DDIOL
 GENERAL DESCRIPTION:   Designed as a replacement for simple WRITE statements
 in any part of the data dictionary that has a programming 'hook', such as
 executable help. 
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   Used as a replacement for simple WRITE statements in
 part of the data dictionary, such as executable help.  
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) If there is just one line of text to
 output, it can be passed in the first parameter.  
VARIABLES: .ARRAY                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) If there is more than one line of text to
 output, stored in a local array, then the first parameter of the call is the
 name of the local array passed by reference and that contains string or
 numeric literals, where: 
     ARRAY(1) = string 1 
     ARRAY(2) = string 2 ...  
     ARRAY(n) = string n 
VARIABLES: GLOBAL_ROOT                  TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) An alternate way to pass the text to the
 call is in a global root. In that case, the first parameter is null, and the
 second parameter contains the name of the global root that contains string or
 numeric literals, where: 
     @GLOBAL_ROOT@(1,0) = string 1 
     @GLOBAL_ROOT@(2,0) = string 2 ...  
     @GLOBAL_ROOT@(n,0) = string n or 
  
     @GLOBAL_ROOT@(1) = string 1 
     @GLOBAL_ROOT@(2) = string 2 ...  
     @GLOBAL_ROOT@(n) = string n 
VARIABLES: FORMAT                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Formatting instructions controlling how
 the string is written or placed in the array. You can specify: One or more new
 lines before the string (!, !!, !!!, etc.) Horizontal position of string (?n) 
 FORMAT can be any number of "!" characters optionally followed by "?n", where
 n is an integer expression. The default FORMAT is "!".  
  
 This parameter can only be used when call format (1) is used to pass a single
 string or numeric literal to EN^DDIOL. 

NUMBER: 10143                           IA #: 10143
  DATE CREATED: APR 11, 1994            CUSTODIAL PACKAGE: TOOLKIT
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XLFMSMT                      NAME: XLFMSMT
  ORIGINAL NUMBER: 10143                ID: XLFMSMT
  STATUS: Active
COMPONENT/ENTRY POINT: WEIGHT(val,from,to)
 COMPONENT DESCRIPTION:   Weight Measurement 
COMPONENT/ENTRY POINT: LENGTH(val,from,to)
 COMPONENT DESCRIPTION:   Length Measurement 
COMPONENT/ENTRY POINT: VOLUME(val,from,to)
 COMPONENT DESCRIPTION:   Weight Measurement 
COMPONENT/ENTRY POINT: BSA(ht,wt)
 COMPONENT DESCRIPTION:   Body surface area 
COMPONENT/ENTRY POINT: TEMP(val,from,to)
 COMPONENT DESCRIPTION:   Temperature measurement 

NUMBER: 10144                           IA #: 10144
  DATE CREATED: APR 11, 1994            CUSTODIAL PACKAGE: TOOLKIT
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XLFHYPER                     NAME: XLFHYPER
  ORIGINAL NUMBER: 10144                ID: XLFHYPER
  STATUS: Active
COMPONENT/ENTRY POINT: $$SINH(X,PR)
COMPONENT/ENTRY POINT: $$COSH(X,PR)
COMPONENT/ENTRY POINT: $$TANH(X,PR)
COMPONENT/ENTRY POINT: $$CSCH(X,PR)
COMPONENT/ENTRY POINT: $$SECH(X,PR)
COMPONENT/ENTRY POINT: $$COTH(X,PR)
COMPONENT/ENTRY POINT: $$ASINH(X,PR)
COMPONENT/ENTRY POINT: $$ACOSH(X,PR)
COMPONENT/ENTRY POINT: $$ATANH(X,PR)
COMPONENT/ENTRY POINT: $$ACOTH(X,PR)
COMPONENT/ENTRY POINT: $$ASECH(X,PR)
COMPONENT/ENTRY POINT: $$ACSCH(X,PR)

NUMBER: 10145                           IA #: 10145
  DATE CREATED: APR 12, 1994            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: IBCNS1
  NAME: IBCNS1                          ORIGINAL NUMBER: 10145
  ID: IBCNS1                            STATUS: Retired
COMPONENT/ENTRY POINT: $$INSURED(DFN,date)
 COMPONENT DESCRIPTION:   This extrinsic function is the quickest way to
 determine if a patient has active billable insurance without returning any of
 the insurance data.  For billing purposes, a patient is only considered
 insured if he has an entry in the INSURANCE TYPE sub-file that meets the
 following five conditions: 
      
 1. The insurance company is active.  2. The insurance company will reimburse
 the government.  (If your site tracks Medicare coverage of patients, the entry
 in the INSURANCE COMPANY file (#36) should be set to not reimburse.) 3. The
 effective date is before the date of care.  4. The expiration date is after
 the date of care. (Treat no entry in the EFFECTIVE DATE and EXPIRATION DATE
 fields as from the beginning of time to the end of time.) 5. The insurance is
 not an indemnity plan.  
  
 Output:  - 1 if insured or 0 if not insured 
  
 Example  - Programmers can use this extrinsic variable to make process 
 determinations when knowing if a patient is insured is needed but knowing the 
 specific policy is not needed: 
           
            I $$INSURED^IBCNS1(DFN,DT) D SET ; only add ins. pts.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   (required) the internal number of the patient in the
 patient file 
VARIABLES: date                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional)  the date to check to see if the patient
 is insured.  
COMPONENT/ENTRY POINT: ALL(DFN,var,flag,date,COB sequence flag)
 COMPONENT DESCRIPTION:   Output: It will return the 0, 1, and 2 nodes for each
 entry in the INSURANCE TYPE sub-file and the 0 node from the GROUP INSURANCE
 PLAN file (#355.3) in a 2 dimensional array, Array(x, node) and, optionally, a
 3 dimensional array, Array("S",COB sequence #,x) that cross references the
 array Array by COB sequence number. The array element Array(0) will be defined
 to the count of entries.  In Array (x, node) x will be the internal entry in
 the INSURANCE TYPE sub-file and node will be 0,1,2 or 355.3. The GROUP NAME 
 and NUMBER fields have been moved to the GROUP INSURANCE PLAN file (#355.3),
 but since many programmers are used to looking for this data on the 0th node
 from the INSURANCE TYPE sub-file, the current value from 355.3 is put back
 into the respective pieces of the 0th node.  In Array("S",COB sequence #,x) x
 is the same as in Array(x,node) and COB sequence is the value of the
 COORDINATION OF BENEFITS field (or 0 if the field is null).  This cross
 reference is returned only if the COB sequence flag is set to 1.  
      
 Programmers should kill the input variable prior to making this call.  
           
 The code for this call looks something like the following: 
                K IBINS 
                D ALL^IBCNS1(DFN,"IBINS",1,IBDT) I $G(IBINS(0)) D LIST 
          or    D ALL^IBCNS1(DFN,"^TMP($J)",1,DT) I $G(^TMP($J,0)) D....  
          or    D ALL^IBCNS1(DFN,"IBINS",1,IBDT,1) I $O(IBINS("S",0)) 
                  I $D(IBINS("S")) S COB="" F  S COB=$O(IBINS("S",COB)) 
                    Q:COB=""  S X=0 F  S X=$O(IBINS("S",COB,X)) Q:'X  
                    S DATA=$G(IBINS(X,0)) D ...; for COB sequence order 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   (required) the internal number of the patient in the
 patient file 
VARIABLES: var                          TYPE: Input
 VARIABLES DESCRIPTION:   the name of the variable you wish to have the data
 returned in.  This may be either a local or global variable.  
VARIABLES: flag                         TYPE: Input
 VARIABLES DESCRIPTION:   (Optional), you can ask for only active insurance
 information by putting a "1" or "2".  If the value of the active flag is 1,
 then the active insurance will be determined as in the call to ACTIVE^IBCNS1. 
 If the value is 2 then insurance companies with a will not reimburse flag will
 be included, but the other screens remain in effect.This is primarily to
 retrieve Medicare policies when it is desirable to include them in active
 policies, 
VARIABLES: date                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional, and only used if the active flag is set)
 The date for the insurance to be active on (the default is "today").  
VARIABLES: COB sequence flag            TYPE: Input
 VARIABLES DESCRIPTION:   (optional)  You can ask for a cross reference of the
 array entries to be returned by COB sequence # if you pass a 1 for this data. 
 If this variable is set to 1, an additional array (Array("S",COB sequence
 #,x)="") is returned to the calling routine.  This array works like a cross 
 reference of Array(x,node) so information on patient policies can be retrieved
 easily in COB sequence # order.  If the entry does not have a defined COB
 sequence #, the value for that entry's COB sequence # is returned as 0.  If
 this flag is not passed or is passed as something other than 1, the array
 Array("S",COB sequence #) is not returned.  
COMPONENT/ENTRY POINT: $$INSTYP(DFN,DATE)
 COMPONENT DESCRIPTION:   This function identifies the type of insurance that a
 patient has on a specific date.  The function will determine the primary
 policy which is effective on the given date, and return a code which 
 identifies the major category of the policy plan type.  If the patient has no
 insurance coverage on the specified date, the function returns a null value.  
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   Pointer to the patient in the PATIENT (#2) file. 
 This required variable specifies the patient for which insurance coverage is 
 being requested.  
VARIABLES: DATE                         TYPE: Input
 VARIABLES DESCRIPTION:   This optional variable specifies the date on which
 the insurance coverage must be effective.  If this date is not specified, the 
 current date is used as the default value.  
VARIABLES: CODE                         TYPE: Output
 VARIABLES DESCRIPTION:   This value returned by the function is a code which
 represents the major category of the patient's primary policy plan type.  The 
 following codes are returned: 
  
    null       No insurance coverage on the effective date 
    1          MAJOR MEDICAL 
    2          DENTAL 
    3          HMO 
    4          PPO 
    5          MEDICARE 
    6          MEDICAID 
    7          CHAMPUS 
    8          WORKMANS COMP 
    9          INDEMNITY 
   10          PRESCRIPTION 
   11          MEDICARE SUPPLEMENTAL 
   12          ALL OTHER 
  
 MAJOR MEDICAL is the default value returned by the function (ie, the patient
 has insurance coverage on the effective date, but the major category of the
 policy plan type cannot be determined).  

NUMBER: 10146                           IA #: 10146
  DATE CREATED: APR 12, 1994            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         ROUTINE: IBCNS
  NAME: IBCNS                           ORIGINAL NUMBER: 10146
  ID: IBCNS                             STATUS: Retired
COMPONENT/ENTRY POINT: DISP
 COMPONENT DESCRIPTION:   This tag can be called to do the standard insurance
 display.  This display is used extensively in registration and billing.  The
 variable DFN must be defined to the current patient.  Using this tag will keep
 your displays current when the package developers update them or make other
 data dictionary changes.  
  
           Example:  S DFN=$P(X,U,2) D DISP^IBCNS ;patient ins. display 
COMPONENT/ENTRY POINT: $$GRP
 COMPONENT DESCRIPTION:   Return group name/group policy 
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   (required) the internal number of an entry in the
 Group Insurance Plan file (#355.3) 
VARIABLES: value                        TYPE: Output
 VARIABLES DESCRIPTION:   The value returned by this function is the group name
 or group number, if both group NUMBER if neither 'Individual PLAN'.  

NUMBER: 10147                           IA #: 10147
  DATE CREATED: APR 12, 1994            CUSTODIAL PACKAGE: INTEGRATED BILLING
  CUSTODIAL ISC: Albany                 USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: IBARXEU                      NAME: IBARXEU
  ORIGINAL NUMBER: 10147                ID: IBARXEU
  STATUS: Active
COMPONENT/ENTRY POINT: DISP(DFN,date,lns,act)
 COMPONENT DESCRIPTION:   Output:  -  The lines are written to the current
 device.  
  
 Example: -  The following are example of how to use this call.  D
 DISP^IBARXEU(DFN) ; write current exemption status D
 DISP^IBARXEU(DFN,date,2,1) ; write 2 lines of exemption status on specific 
 date, if unknown, no display 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   (required) the internal number of the patient in the
 patient file^ 
VARIABLES: date                         TYPE: Input
 VARIABLES DESCRIPTION:   (optional) the date the programmer is requesting
 exemption information for. The default is today.  
VARIABLES: lns                          TYPE: Input
 VARIABLES DESCRIPTION:   Number of lines - (optional) The number of lines to
 print.  A whole number value from 1-3.  The lines are 1. the current exemption
 status, 2. the exemption reason, and 3 the date of the last test.  
VARIABLES: act                          TYPE: Input
 VARIABLES DESCRIPTION:   Unknown Action (optional) - If the exemption status
 has never been determined the programmer can suppress any printing of
 information.  This may be useful when displaying information of new patients.  
COMPONENT/ENTRY POINT: RXST(DFN,date)
 COMPONENT DESCRIPTION:   Output: 1.   Piece 1 - the exemption status, 1 = exem
 |t, 0 = non-exempt 2.   Piece 2 - the standard text used when displayingthe
 exemption status. (i.e. EXEMPT or NON-EXEMPT) 3.   Piece 3 - the exemption
 reason code 4.   Piece 4 - the exemption reason text 5.   Piece 5 - the date
 of the last income test.  
      
 Example - This can be used in determining a patients exemption status and in 
 writing messages.  
  
                S X=$$RXST^IBARXEU(DFN,DT) 
                W !,"Patient is ",$P(X,"^",2),"  -  ",$P(X,"^",4) 
                D:+X NOCOPAY D:'+X COPAY 
                Q 
VARIABLES: DFN                          TYPE: Input
 VARIABLES DESCRIPTION:   DFN - (required) the internal number of the patient
 in the patient file 
VARIABLES: date                         TYPE: Input
 VARIABLES DESCRIPTION:   Date - (optional) the date the programmer is
 requesting exemption information for.  The default is today.  

NUMBER: 10148                           IA #: 10148
  DATE CREATED: NOV 22, 2004            CUSTODIAL PACKAGE: LEXICON UTILITY
  CUSTODIAL ISC: Salt Lake City         USAGE: Supported
  TYPE: Routine                         ROUTINE: GMPTU
  NAME: GMPTU                           ORIGINAL NUMBER: 10148
  ID: GMPTU                             STATUS: Retired
COMPONENT/ENTRY POINT: $$ICDONE(IEN)
 COMPONENT DESCRIPTION:   Returns:  Either 1) the first ICD code linked to the
 expression or 2) Null (if there are no ICD codes linked to the expression).  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   Internal Entry Number of an expression (term)
 contained in the Expressions File (^GMP(757.01)).  
COMPONENT/ENTRY POINT: $$ICD(IEN)
 COMPONENT DESCRIPTION:   Returns:  Either 1) a string of all ICD codes  linked
 to the expression (separated by a  semicolon, i.e., ICD;ICD;ICD) or 2) Null
 (if there are no ICD codes linked to the expression).  
VARIABLES: IEN                          TYPE: Input
 VARIABLES DESCRIPTION:   IEN - Internal Entry Number of an expression
 contained in the Expression file (^GMP(757.01)).  

NUMBER: 10149                           IA #: 10149
  DATE CREATED: JUN 24, 1994            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DDSVAL                       NAME: ScreenMan API: Form Utilities
  ORIGINAL NUMBER: 10149                ID: DDSVAL
 GENERAL DESCRIPTION:   $$GET - This extrinsic function retrieves data from a
 data dictionary field.  PUT - Stuffs data into form-only fields.  
  STATUS: Active
COMPONENT/ENTRY POINT: $$GET
 COMPONENT DESCRIPTION:   This extrinsic function retrieves data from a data
 dictionary field. 
  
 Text for a word processing field is moved into a global array, and 
 $$GET^DDSVAL returns the closed root of that array. The array has the same 
 format as a FileMan word processing field. 
  
 Computed fields in FileMan files cannot be retrieved. To retrieve the value of
 a computed field defined on the form, use the $$GET^DDSVALF.  
  
 Format $$GET^DDSVAL(FILE,[.]RECORD,FIELD,.ERROR,FLAGS) 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The global root or number of the file or
 subfile. At the field level, the local variable DIE contains the current
 global root. 
VARIABLES: [.]RECORD                    TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The internal entry number or an array of
 internal entry numbers. This parameter has the same form as the DA array. At
 the field level, the local array DA contains the current array of internal
 entry numbers. 
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The field name or number, or a relational
 expression that follows a forward pointer (e.g., POINTER:FIELD). 
VARIABLES: .ERROR                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) $D(ERROR)>1, if the function call fails. 
VARIABLES: FLAGS                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Controls whether the internal or external
 form is returned, as shown below (the I and E flags have no effect if FIELD is
 a word processing field): 
  
 I Return the Internal form of the data. (Default)  E Return the External form
 of the data.  
COMPONENT/ENTRY POINT: PUT
 COMPONENT DESCRIPTION:   This procedure stuffs data into a data dictionary
 field as part of ScreenMan's transaction. The data passed to this procedure is
 filed in the database only when the user explicitly saves changes. 
  
 Format PUT^DDSVAL(FILE,[.]RECORD,FIELD,VALUE,.ERROR,FLAGS) 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The global root or number of the file or
 subfile. At the field level, the local variable DIE contains the current
 global root. 
VARIABLES: [.]RECORD                    TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The internal entry number or an array of
 internal entry numbers. This parameter has the same form as the DA array. At
 the field level, the local array DA contains the current array of record
 numbers. 
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The field name or number. 
VARIABLES: VALUE                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The value to stuff into the data
 dictionary field. If FLAGS (described below) does not contain an "I", the
 value must be in the form of a valid, unambiguous user response.  
  
 If FIELD is a word processing field, VALUE must be the closed root of the 
 array that contains the text. The subscripts of the nodes below the root must
 be positive numbers, though they need not be integers, and there can be gaps
 in the sequence. The text must be in these nodes or in the 0 node descendent
 from these nodes.  
  
 If FIELD is a multiple field, VALUE determines the subrecord to display to the
 user as a default for selection. It is not a value that is ever filed.  VALUE
 can be "FIRST", "LAST", or the specific internal entry number of the subrecord
 to display. "FIRST" indicates that the subrecord with the lowest internal
 entry number should be displayed, and "LAST" indicates that the subrecord with
 the highest internal entry number should be displayed. 
VARIABLES: .ERROR                       TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) $D(ERROR)>1, if the procedure call fails. 
VARIABLES: FLAGS                        TYPE: Input
 VARIABLES DESCRIPTION:   Indicates whether VALUE is in internal or external
 form, as shown below: 
  
 A Append new word processing text to the current text. This flag can be used
 only when stuffing text into word a processing field. If the A flag is not
 sent, the current word processing text is completely erased before the new
 text is added.  I VALUE is in Internal form; it is not validated.  E VALUE is
 in External form. (Default)  (Optional) The I and E flags have no effect when
 FIELD is a word processing field. 

NUMBER: 10150                           IA #: 10150
  DATE CREATED: JUN 24, 1994            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DDSUTL                       NAME: ScreenMan API: Form Utilities
  ORIGINAL NUMBER: 10150                ID: DDSUTL
 GENERAL DESCRIPTION:   Help Messages: HLP, MSG; Refresh Screen: REFRESH;
 Run-Time Field Status: REQ, UNED Utilities.  
  STATUS: Active
COMPONENT/ENTRY POINT: HLP()
 COMPONENT DESCRIPTION:   This procedure prints messages in the Command Area. 
  
 Formats HLP^DDSUTL(STRING) HLP^DDSUTL(.STRING) 
VARIABLES: STRING                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The message to print in the Command Area. 
VARIABLES: .STRING                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) An array of messages to print in the
 Command Area. STRING(1), STRING(2), ..., STRING(n) each contain a line of
 text. 
COMPONENT/ENTRY POINT: MSG()
 COMPONENT DESCRIPTION:   This procedure prints Data Validation messages on a
 separate screen. 
  
 Formats MSG^DDSUTL(STRING) MSG^DDSUTL(.STRING) 
VARIABLES: STRING                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The message to print in the Command Area. 
VARIABLES: .STRING                      TYPE: Input
 VARIABLES DESCRIPTION:   (Required) An array of messages to print in the
 Command Area. STRING(1), STRING(2), ..., STRING(n) each contain a line of
 text. 
COMPONENT/ENTRY POINT: REFRESH
 COMPONENT DESCRIPTION:   This entry point repaints all pages on the screen. 
  
 You can use this entry point only within a ScreenMan form, and only in: 
  
 Field level Pre Action Field level Post Action Field level Branching Logic 
 Field level Data Validation Format REFRESH^DDSUTL 
VARIABLES: None
COMPONENT/ENTRY POINT: REQ()
 COMPONENT DESCRIPTION:   This procedure changes the REQUIRED property of a
 field on the form. 
  
 Format REQ^DDSUTL(FIELD,BLOCK,PAGE,VALUE,IENS) 
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The Field Order number, Caption, or Unique
 Name of the 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 give the REQUIRED property,
 listed as follows:  "" Restore the REQUIRED property to the value defined in
 the Block file.  0 Make the field not required.  1 Make the field required.  
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: UNED()
 COMPONENT DESCRIPTION:   This procedure changes the DISABLE EDITING property
 of a field on the form. 
  
 Format UNED^DDSUTL(FIELD,BLOCK,PAGE,VALUE,IENS) 
VARIABLES: FIELD                        TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The Field Order number, Caption, or Unique
 Name of the 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 give the DISABLE EDITING
 property, shown below: 
  
 "" Restore the DISABLE EDITING property to the value as defined in the Block
 file.  0 Enable editing, and allow the user to navigate to the field.  1
 Disable editing, and prevent the user from navigating to the field.  2 Disable
 editing, but allow the user to navigate to the field.  
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: 10151                           IA #: 10151
  DATE CREATED: JUN 24, 1994            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: DIAXU                        NAME: Extract Tool API
  ORIGINAL NUMBER: 10151                ID: DIAXU
 GENERAL DESCRIPTION:   The Extract Tool lets you move or copy records from one
 VA FileMan file to another; a typical use is to archive records. 
  STATUS: Active
COMPONENT/ENTRY POINT: EN
 COMPONENT DESCRIPTION:   This entry point extracts data specified in the
 extract template for a single entry, and moves that data to a destination
 file. 
VARIABLES: DIAXF                        TYPE: Both
 VARIABLES DESCRIPTION:   Input: (Required) The number of the file that
 contains the source entry.  
  
 Output: Not killed upon exit.  
VARIABLES: DIAXT                        TYPE: Both
 VARIABLES DESCRIPTION:   Input: (Required) The extract template name enclosed
 in brackets in the source file that contains specifications of data to be
 extracted.  
  
 Output: Not killed upon exit.  
VARIABLES: DIAXDEL                      TYPE: Both
 VARIABLES DESCRIPTION:   Input: (Optional) This variable, if defined, tells
 the program to delete the source entry. If not defined, the source entry is
 unchanged.  
  
 Output: Not killed upon exit.  
VARIABLES: DIAXDA                       TYPE: Output
 VARIABLES DESCRIPTION:   Internal entry number of entry created in the
 destination file. In addition to DIAXDA, 
  
   ^TMP("DIAXU",$J,"RESULT",DIAXF,DIAXFE)=DIAXDA is returned.  
VARIABLES: DIAXNTC                      TYPE: Output
 VARIABLES DESCRIPTION:   No longer returned. For batch processing of extracts,
 you should use the EXTRACT^DIAXU entry point instead of this one.  
VARIABLES: DIAXFE                       TYPE: Both
 VARIABLES DESCRIPTION:   Input: (Required) Internal entry number of the source
 entry from which data will be extracted.  
  
 Output: Not killed upon exit.  
VARIABLES: DIERR                        TYPE: Output
 VARIABLES DESCRIPTION:   Contains the following two ^-pieces of information: 
  
 Number of errors generated during the call Total number of lines of the error
 messages 
  
 In addition, the following "RESULT","ERR" node is returned: 
  
   ^TMP("DIAXU",$J,"RESULT","ERR",file#,ien) 
VARIABLES: TMP("DIERR",$J,...           TYPE: Output
 VARIABLES DESCRIPTION:   Errors information is returned in ^TMP("DIERR",$J),
 in the same format error information is returned for DBS calls. 
COMPONENT/ENTRY POINT: EXTRACT()
 COMPONENT DESCRIPTION:   Entry point for extracting data are: 
  
 More than one record can be extracted in a call. Subrecords can be extracted
 as individual transactions. Previously, an entire record including all
 subrecords had to be extracted as a single entity. DBS-style error reporting
 is used. 
  
 Format D EXTRACT^DIAXU(FILE,SOURCE,EXTRACT_TEMPLATE,FLAGS,.SCREENS, 
   .FILING_LEVEL,TARGET_ROOT,MSG_ROOT) 
VARIABLES: FILE                         TYPE: Input
 VARIABLES DESCRIPTION:   (Required) File number of source file.  
VARIABLES: SOURCE                       TYPE: Input
 VARIABLES DESCRIPTION:   (Required) Can be 1 of 2 formats: IEN: The record
 number of a single record, at the top level of the file, to extract. Search
 template name: The name of a search template, in brackets, that contains
 SEARCH results (a list of record numbers). For example, S
 SOURCE="[TEMPLATE_NAME]" 
VARIABLES: EXTRACT_TEMPLATE             TYPE: Input
 VARIABLES DESCRIPTION:   (Required) The name of the Extract Template, in
 brackets, containing what fields to move.  
VARIABLES: FLAGS                        TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) A string of characters to modify the
 behavior of the Extract tool. Permissible characters in the string are: D
 Tells the extract tool to delete source records if they were moved 
 successfully. Note that deletion is only done for entire (top-level) records.
 Subrecords are not individually deleted, even if they are individually
 extracted. 
VARIABLES: .SCREENS                     TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Local array containing screen(s) to apply
 to subrecords at various subrecord levels. The screens determine whether to
 move individual subrecords at a given level or not. 
VARIABLES: .FILING_LEVEL                TYPE: Input
 VARIABLES DESCRIPTION:   (Optional) Local array you can use to tell the
 Extract tool to file subrecords as individual transactions, at one or more
 subfile levels. The default filing mode is to file an entire record, including
 all subrecords, as a single transaction. 
VARIABLES: TARGET_ROOT                  TYPE: Both
 VARIABLES DESCRIPTION:   Input: (Optional) Array that should receive the
 results generated during the extract tool process. This must be a closed array
 reference and can be either local or global.  If you do not pass this
 parameter, the results are returned in ^TMP("DIAXU",$J). 
  
 Output: One "RESULT" node is returned for each record extracted (or attempted
 to be extracted). 
VARIABLES: MSG_ROOT                     TYPE: Both
 VARIABLES DESCRIPTION:   Input: (Optional) Array that should receive error
 messages generated during the extract tool process. This must be a closed
 array reference and can be either local or global.  If you do not pass this
 parameter, error messages are returned in ^TMP("DIERR",$J).  
  
 Output: Error messages are returned in MSG_ROOT("DIERR") (if the MSG_ROOT 
 input parameter is passed) or ^TMP("DIERR",$J) (if no array is specified).  
 Errors are returned in DBS-style format.  
VARIABLES: DIERR                        TYPE: Output
 VARIABLES DESCRIPTION:   This variable is returned if an error condition
 occurred. It contains two ^-pieces of information: Number of errors generated
 during the call Total number of lines of the error messages Associated error
 messages are stored, DBS-style, in MSG_ROOT. 

NUMBER: 10152                           IA #: 10152
  GLOBAL ROOT: DD('ROU')                DATE CREATED: DEC 23, 1994
  CUSTODIAL PACKAGE: 1                  CUSTODIAL ISC: San Francisco
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: DD('ROU')
  ID: DD('ROU')
GLOBAL REFERENCE: DD('ROU')
 GLOBAL DESCRIPTION:   Read only access.  
 GENERAL DESCRIPTION:   ^DD("ROU") - the default maximum routine size used by
 FileMan when compiling input and print templates, and cross-references.  
  STATUS: Active

NUMBER: 10153                           IA #: 10153
  DATE CREATED: JAN 11, 1995            CUSTODIAL PACKAGE: TOOLKIT
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: Routine                         DBIC APPROVAL STATUS: APPROVED
  ROUTINE: XTLKMGR                      NAME: MTLU LOOKUPS/FILE MANAGEMENT
  ID: XTLKMGR
 GENERAL DESCRIPTION:   Procedure calls for MTLU.  
  STATUS: Active                        DURATION: Till Otherwise Agreed
COMPONENT/ENTRY POINT: SY(xtlk1,xtlk2,xtlk3)
 COMPONENT DESCRIPTION:   Add terms and synonyms to the Local Synonym
 file(8984.3).  
VARIABLES: XTLK1                        TYPE: Input
 VARIABLES DESCRIPTION:   Associated file 
VARIABLES: XTLK2                        TYPE: Input
 VARIABLES DESCRIPTION:   term 
VARIABLES: XTLK3                        TYPE: Input
 VARIABLES DESCRIPTION:   Synonym (or optional array for multiple synonymns per
 term).  For example: SYN(1)=<first synonym>, SYN(2)=<2nd synonym> 
VARIABLES: XTLKER(1,filename)           TYPE: Output
 VARIABLES DESCRIPTION:   File not defined in the Local Lookup file (8984.4) 
VARIABLES: XTLKER(2,term)               TYPE: Output
 VARIABLES DESCRIPTION:   The term could not be added.  
VARIABLES: XTLKER(3,synonym)            TYPE: Output
 VARIABLES DESCRIPTION:   Synonym could not be added.  
COMPONENT/ENTRY POINT: K(xtlk1,xtlk2,xltk3)
 COMPONENT DESCRIPTION:   Add keywords to the LOCAL KEYWORD file (8984.1).  
VARIABLES: XTLK1                        TYPE: Input
 VARIABLES DESCRIPTION:   Associated file 
VARIABLES: XTLK2                        TYPE: Input
 VARIABLES DESCRIPTION:   code in associated file 
VARIABLES: XLTK3                        TYPE: Input
 VARIABLES DESCRIPTION:   keyword 
VARIABLES: XTLKER(1,filename)           TYPE: Output
 VARIABLES DESCRIPTION:   File not defined in the LOCAL LOOKUP file (8984.4) 
VARIABLES: XTLKER(2,code)               TYPE: Output
 VARIABLES DESCRIPTION:   the code is not in the associated file.  
VARIABLES: XTLKER(3,synonym)            TYPE: Output
 VARIABLES DESCRIPTION:   The keyword could not be added.  
COMPONENT/ENTRY POINT: L(xtlk1,xtlk2,xtlk3,xtlk4)
 COMPONENT DESCRIPTION:   Define a file in the LOCAL LOOKUP file (8984.4).
 Adding the target file here does not automatically place the special look-up
 routine, ^XTLKDICL, in the file's Data Dictionary. since use of this routine
 is at the discretion of the developer, it should be manually added via the
 Edit File option under VA Fileman's Utilities Menu.  
VARIABLES: XTLK1                        TYPE: Input
 VARIABLES DESCRIPTION:   filename or number 
VARIABLES: XTLK2                        TYPE: Input
 VARIABLES DESCRIPTION:   application-specific display protocol (optional) 
VARIABLES: XLTK3                        TYPE: Input
 VARIABLES DESCRIPTION:   MTLU index to use for look-ups 
VARIABLES: XTLK4                        TYPE: Input
 VARIABLES DESCRIPTION:   variable pointer prefix 
VARIABLES: XTLKER(1,filename)           TYPE: Output
 VARIABLES DESCRIPTION:   file could not be added 
COMPONENT/ENTRY POINT: DSH(xtlk1,xtlk2)
 COMPONENT DESCRIPTION:   Delete shortcuts from the LOCAL SHORTCUT file
 (8984.2) 
VARIABLES: XTLK1                        TYPE: Input
 VARIABLES DESCRIPTION:   filename 
VARIABLES: XTLK2                        TYPE: Input
 VARIABLES DESCRIPTION:   leave undefined to delete all shortcuts for a given
 target file or pass in an array for selected shortcuts.  
COMPONENT/ENTRY POINT: DSY(xtlk1,xtlk2)
 COMPONENT DESCRIPTION:   Delete synonyms from the LOCAL SYNONYM file (8984.3) 
VARIABLES: XTLK1                        TYPE: Input
 VARIABLES DESCRIPTION:   filename 
VARIABLES: XTLK2                        TYPE: Input
 VARIABLES DESCRIPTION:   Leave undefined to delete all synonyms for a given
 target file or pass in an array for selected synonyms.  
COMPONENT/ENTRY POINT: DK(xtlk1,xtlk2)
 COMPONENT DESCRIPTION:   Delete keywords from the LOCAL KEYWORD file (8984.1) 
VARIABLES: XTLK1                        TYPE: Input
 VARIABLES DESCRIPTION:   filename 
VARIABLES: XTLK2                        TYPE: Input
 VARIABLES DESCRIPTION:   Leave undefined to delete all keywords for a given
 target file or pass in an array for selected keywords.  
COMPONENT/ENTRY POINT: DLL(xtlk1)
 COMPONENT DESCRIPTION:   Delete an entry from the LOCAL LOOKUP FILE (8984.4) 
VARIABLES: XTLK1                        TYPE: Input
 VARIABLES DESCRIPTION:   associated filename or number 
VARIABLES: XTLKER(1,filename)           TYPE: Output
 VARIABLES DESCRIPTION:   file is not in the LOCAL LOOKUP file (8984.4) 
VARIABLES: XTLKER(2)                    TYPE: Output
 VARIABLES DESCRIPTION:   Entries exist for keywords, shortcuts or synonyms for
 the associated file.  These must be deleted first.  
COMPONENT/ENTRY POINT: LKUP(fil,xtlkx,xtlksay,xtlkhlp,xtlkmore)
 COMPONENT DESCRIPTION:   This is a general lookup facility for MTLU. The
 target file must be defined in the LOCAL LOOKUP file, but the routine
 ^XTLKDICL does not have to be defined in the target file's DD.  
VARIABLES: FIL                          TYPE: Input
 VARIABLES DESCRIPTION:   target file (must be defined in the LOCAL LOOKUP
 file, 8984.4) 
VARIABLES: XTLKX                        TYPE: Input
 VARIABLES DESCRIPTION:   word or phrase to use in the look-up 
VARIABLES: XTLKSAY                      TYPE: Input
 VARIABLES DESCRIPTION:   <OPTIONAL>set to -1, 0 or 1 (default). 0=minimal
 display, -1=NO screen writes are performed, 1 or null=normal display. The
 purpose of XTLKSAY is to control the degree of output to the screen, not the
 amount of file information displayed. If screen displays are turned off, MTLU
 matches can be processed by checking the count in ^TMP("XTLKHITS",$J).  
 ^TMP("XTLKHITS",$J,x)=IEN of the entry in the target file. Remember to kill
 this node after processing.  
VARIABLES: XTLKHLP                      TYPE: Input
 VARIABLES DESCRIPTION:   <OPTIONAL>executable M code to display
 application-specific help 
VARIABLES: XTLKMORE                     TYPE: Input
 VARIABLES DESCRIPTION:   <OPTIONAL>if set to '1' and there are no MTLU
 matches, the search will continue using all available Fileman
 cross-references. At this point, it will be a simple FileMan look-up and
 display (default=1).  
  
 NOTE: If XTLKSAY=-1, then XTLKMORE is ignored.  
COMPONENT/ENTRY POINT: SH(xtlk1,xtlk2,xtlk3)
 COMPONENT DESCRIPTION:   Populate the MTLU Shortcuts file (8984.2).  
VARIABLES: XTLK1                        TYPE: Input
 VARIABLES DESCRIPTION:   Associated file 
VARIABLES: XTLK2                        TYPE: Input
 VARIABLES DESCRIPTION:   code in associated file 
VARIABLES: XTLK3                        TYPE: Input
 VARIABLES DESCRIPTION:   shortcut 
VARIABLES: XTLKER(2,xtlk2)              TYPE: Output
 VARIABLES DESCRIPTION:   error-code in associated file did not exist.  
VARIABLES: XTLKER(3,xtlk3)              TYPE: Output
 VARIABLES DESCRIPTION:   error-shortcut could not be added.  

NUMBER: 10154                           IA #: 10154
  FILE NUMBER: 0                        GLOBAL ROOT: DD(file,field,0)
  DATE CREATED: DEC 17, 1997            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: DESCRIPTOR BLOCK                ID: DD(file,field,0)
GLOBAL REFERENCE: piece 2
 GENERAL DESCRIPTION:   The 2nd piece of ^DD(filenumber,fieldnumber,0) is used
 in the "File Header" piece 2.  This may be referenced since no FM APIs exist
 yet to return this information.  
  STATUS: Active

NUMBER: 10155                           IA #: 10155
  FILE NUMBER: 0                        GLOBAL ROOT: DD(file,field,0)
  DATE CREATED: FEB 03, 1998            CUSTODIAL PACKAGE: 1
  CUSTODIAL ISC: San Francisco          USAGE: Supported
  TYPE: File                            DBIC APPROVAL STATUS: APPROVED
  NAME: SET OF CODES                    ID: DD(file,field,0)
GLOBAL REFERENCE: piece 3
 GENERAL DESCRIPTION:   The 3rd piece of ^DD(filenumber,fieldnumber,0) is used
 in the call to Y^DIQ.  This may be referenced since no FM APIs exist yet to
 return this field for input to the supported call Y^DIQ.  
  STATUS: Active

NUMBER: 10156                           IA #: 10156
  FILE NUMBER: 19                       GLOBAL ROOT: DIC(19,
  DATE CREATED: MAY 31, 2006            CUSTODIAL PACKAGE: KERNEL
  USAGE: Supported                      TYPE: File
  DBIC APPROVAL STATUS: APPROVED        NAME: OPTION FILE
  ID: DIC(19,
 GENERAL DESCRIPTION:   Exporting, deleting, updating Options by Namespace via
 KIDS is permitted.  Linking menu options from other packages requires IAs
 between the packages whose options are being "linked".  
  STATUS: Active





Select OPTION: 
ICRA>

